10 PDU functional definitions and contents

3GPP48.018Base Station System (BSS) - Serving GPRS Support Node (SGSN)BSS GPRS protocol (BSSGP)General Packet Radio Service (GPRS)Release 17TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

10.1 General Structure Of A PDU

Refer to General Structure Of A PDU/3GPP TS 48.016 [16].

10.2 PDU functional definitions and contents at RL and BSSGP SAPs

10.2.1 DL-UNITDATA

This PDU is sent to the BSS to transfer an LLC-PDU across the radio interface to an MS.

PDU type: DL-UNITDATA

Direction: SGSN to BSS

Table 10.2.1: DL-UNITDATA PDU contents

Information element	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI (current)	TLLI/11.3.35	M	V	4
QoS Profile (note 1)	QoS Profile/11.3.28	M	V	3
PDU Lifetime	PDU Lifetime/11.3.25	M	TLV	4
MS Radio Access Capability (note 2)	MS Radio Access Capability/11.3.22	O	TLV	7-?
Priority (note 3)	Priority/11.3.27	O	TLV	3
DRX Parameters (note 11)	DRX Parameters/11.3.11	O	TLV	4
IMSI (note 14)	IMSI/11.3.14	O	TLV	5-10
TLLI (old)	TLLI/11.3.35	O	TLV	6
PFI	PFI/11.3.42	O	TLV	3
LSA Information	LSA Information/11.3.19	O	TLV	7-?
Service UTRAN CCO	Service UTRAN CCO/11.3.47	O	TLV	3
Subscriber Profile ID for RAT/Frequency priority (note 5)	Subscriber Profile ID for RAT/Frequency priority/11.3.105	O	TLV	3
Redirection Indication (note 6)	Redirection Indication/11.3.112	O	TLV	3
Redirection Completed (note 7)	Redirection Completed/11.3.113	O	TLV	3
Unconfirmed send state variable (note 9)	Unconfirmed send state variable/11.3.114	C	TLV	4
SCI (note 10)	SCI/ 11.3.116	O	TLV	3
GGSN/P-GW location (note 10)	GGSN/P-GW location/11.3.117	O	TLV	3
eDRX Parameters (note 11)	eDRX Parameters/11.3.122	O	TLV	3
Coverage Class	Coverage Class/11.3.124	O	TLV	3
Old Routing Area Identification (note 12)	Old Routing Area Identification/11.3.127	O	TLV	8
Attach Indicator (note 13)	Attach Indicator/11.3.128	O	TLV	3
SGSN Group Identity (note 15)	SGSN Group Identity/11.3.131	C	TLV	5
Additional P-TMSI (note 15)	Additional P-TMSI/11.3.132	C	TLV	6
UE Usage Type (note 15)	UE Usage Type/11.3.133	C	TLV	3
Alignment octets	Alignment octets/11.3.1	O	TLV	2-5
LLC-PDU (note 4)	LLC-PDU/11.3.15	M	TLV	2-?
Initial LLC-PDU (note 8)	LLC-PDU/11.3.15	O	TLV	2-?
Timing Advance Request	Timing Advance Request/11.3.140	O	TLV	3
Enhanced Coverage Additional Information	Enhanced Coverage Additional Information/11.3.141	O	TLV	3
NOTE 1: Some attributes of the QoS Profile shall be discarded if the PFI field is present and corresponds to a known PFC in the BSS. NOTE 2: The field shall be present if there is valid MS Radio Access Capability information known by the SGSN; the field shall not be present otherwise. NOTE 3: The priority field shall be discarded if the PFI field is present and corresponds to a known PFC in the BSS for which the ARP field was received. NOTE 4: The LLC-PDU Length Indicator may be zero. NOTE 5: This IE may be included if available in the SGSN. If the Service UTRAN CCO IE is present with the value of "shall not" the Service UTRAN CCO IE takes precedence over this IE. NOTE 6: This IE shall be included if Redirect Attempt flag was present in UL-UNITDATA and the CN requests rerouting by the BSC to another CN operator. NOTE 7: This IE shall be included if Redirect Attempt flag was present in UL-UNITDATA and the redirection is completed. NOTE 8: The initial Layer 3 Information received from MS. Only present when Redirection Indication is present. NOTE 9: Contains the value of the V(U) as defined in 3GPP TS 44.064 [12] if Redirection Indication IE is present. NOTE 10: These IEs are included when the SGSN supports the SIRUG feature and the received GTP-U packet contained the SCI IE. NOTE 11: If the SGSN has valid eDRX Parameters for a TLLI it shall include the eDRX Parameters IE (see sub-clause 6.1) in which case the DRX Parameters IE shall not be included. NOTE 12: This IE is only included when Redirection Indication is present and the SGSN supports CS/PS coordination enhancements. NOTE 13: This IE indicates a GPRS attach request from the MS. It may only be included if Redirection Indication is present and the SGSN supports CS/PS coordination enhancements. NOTE 14: This IE is included if the IMSI was retrieved unencrypted from the MS and the SGSN supports Dedicated Core Networks. NOTE 15: This IE is included if the SGSN supports Dedicated Core Networks and is included when the “Redirection Indication” IE is present.

10.2.2 UL-UNITDATA

This PDU transfers an MS’s LLC-PDU and its associated radio interface information across the Gb-interface.

PDU type: UL-UNITDATA

Direction: BSS to SGSN

Table 10.2.2: UL-UNITDATA PDU content

Information element	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	V	4
QoS Profile	QoS Profile/11.3.28	M	V	3
Cell Identifier (note 5)	Cell Identifier/11.3.9	M	TLV	10
PFI	PFI/11.3.42	O	TLV	3
LSA Identifier List	LSA Identifier List/11.3.18	O	TLV	3-?
Redirect Attempt Flag (Note 3)	Redirect Attempt Flag/11.3.111	O	TLV	3
IMSI (note 2)	IMSI/11.3.14	O	TLV	5-10
Unconfirmed send state variable (note 4)	Unconfirmed send state variable/11.3.114	O	TLV	4
Selected PLMN ID (note 5)	Selected PLMN ID/11.3.118	O	TLV	5
Coverage Class (note 7)	Coverage Class/11.3.124	O	TLV	3
Exception Report Flag (note 6)	Exception Report Flag/11.3.126	O	TLV	3
Selected Operator (note 8, 9)	PLMN Identity/11.3.129	O	TLV	5
CS Registered Operator (note 8, 10)	PLMN Identity/11.3.129	O	TLV	5
SGSN Group Identity (note 11)	SGSN Group Identity /11.3.131	O	TLV	5
UE Usage Type (note 11)	UE Usage Type/11.3.133	O	TLV	3
DCN-ID (note 12)	DCN-ID/11.3.134	O	TLV	4
Alignment octets	Alignment octets/11.3.1	O	TLV	2-5
LLC-PDU (note 1)	LLC-PDU/11.3.15	M	TLV	2-?
MultilaterationTiming Advance (note 13)	MultilaterationTiming Advance/11.3.137	O	TLV	4
MS Sync Accuracy (note 13)	MS Sync Accuracy/11.3.138	O	TLV	3
BTS Reception Accuracy Level (note 13)	BTS Reception Accuracy Level/11.3.139	O	TLV	3
NOTE 1: The LLC-PDU Length Indicator may be zero. NOTE 2: IMSI shall be included if available and if Redirect Attempt Flag is present. NOTE 3: This element indicates that the core network shall respond with either Redirection Indication IE or Redirection Completed IE in DL_UNITDATA NOTE 4: Unconfirmed send state variable shall be included if received in the previous DL_UNITDATA. NOTE 5: Selected PLMN ID shall be included in the case of a mobile station supporting network sharing when a foreign TLLI or a random TLLI is included in the UL-UNIDATA PDU; in such a case the Common PLMN ID shall be included within the Cell Identifier IE. NOTE 6: The exception report flag shall be included a) if the UL-UNITDATA PDU contains an LLC PDU sent by the MS using an uplink EC TBF established in response to an EC PACKET CHANNEL REQUEST message indicating high priority (i.e. an exception report). b) if the UL-UNITDATA PDU contains an LLC PDU sent by the MS using an uplink EC TBF established in response to an EC PACKET DOWNLINK ACK/NACK message including channel request and indicating high priority(i.e. an exception report). NOTE 7: The values indicated by this IE are the uplink and downlink coverage classes used by the mobile station in the access request initiating the transmission of the LLC-PDU included in the UL-UNITDATA PDU. NOTE 8: Only one of these two optional IEs shall be present in the message. NOTE 9: This IE indicates the BSS selected CN operator. It is only included if the BSS supports CS/PS coordination enhancements. NOTE 10: This IE is included if the BSS supports CS/PS coordination enhancements and if the mobile station is served by one of the shared CN operators in the CS domain. Note 11: This IE is included if the BSS supports Dedicated Core Networks or if it supports MS assisted Dedicated Core Network selection and is included if the “Redirect Attempt Flag” IE is present. Note 12: This IE is included if provided by the MS, see 3GPP TS 44.060 [22] and if the LLC PDU contains an intial LLC PDU. It shall not be included if the SGSN Group Identity is included. Note 13: This IE is included if the BSS receives a page response sent using a RLC data block that includes the “MS Transmission Offset” and “MS Sync Accuracy” parameters (see 3GPP TS 44.018 [25] and 3GPP TS 44.060 [22]).

10.2.3 RA-CAPABILITY

This PDU informs the BSS of the new Radio Access Capability of an MS.

PDU type: RA-CAPABILITY

Direction: SGSN to BSS

Table 10.2.3: RA-CAPABILITY PDU content

Information element	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
MS Radio Access Capability	MS Radio Access Capability/11.3.22	M	TLV	7-?

10.2.4 (void)

10.2.5 DL-MBMS-UNITDATA

This PDU is sent to the BSS to transfer an LLC-PDU across the radio interface.

PDU type: DL-MBMS-UNITDATA

Direction: SGSN to BSS

Table 10.2.5: DL-MBMS-UNITDATA PDU contents

Information element	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
PDU Lifetime	PDU Lifetime/11.3.25	M	TLV	4
TMGI	TMGI/ 11.3.77	M	TLV	3-8
MBMS Session Identity	MBMS Session Identity/ 11.3.71	O	TLV	3
Alignment octets	Alignment octets/11.3.1	O	TLV	2-5
LLC-PDU	LLC-PDU/11.3.15	M	TLV	3-?

10.2.6 UL-MBMS-UNITDATA

This PDU transfers an LLC-PDU for an MBMS session across the Gb-interface.

PDU type: UL-MBMS-UNITDATA

Direction: BSS to SGSN

Table 10.2.6: UL-MBMS-UNITDATA PDU contents

Information element	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TMGI	TMGI/ 11.3.77	M	TLV	3-8
MBMS Session Identity	MBMS Session Identity/ 11.3.71	O	TLV	3
Alignment octets	Alignment octets/11.3.1	O	TLV	2-5
LLC-PDU (note 1)	LLC-PDU/11.3.15	M	TLV	2-?
NOTE: The LLC-PDU Length Indicator shall be zero in this version of the specifications.

10.3 PDU functional definitions and contents at GMM SAP

10.3.1 PAGING PS

This PDU indicates that a BSS shall initiate the packet paging procedure for an MS within a group of cells.

PDU type: PAGING-PS

Direction: SGSN to BSS

Table 10.3.1: PAGING PS PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
IMSI	IMSI/11.3.14	M	TLV	5 -10
DRX Parameters (note 3)	DRX Parameters/11.3.11	O	TLV	4
BVCI (note 1)	BVCI/11.3.6	C	TLV	4
Location Area (note 1)	Location Area/11.3.17	C (note 2)	TLV	7
Routeing Area (note 1)	Routeing Area/11.3.31	C (note 2)	TLV	8
BSS Area Indication (note 1)	BSS Area Indication/11.3.3	C	TLV	3
PFI	PFI/11.3.42	O	TLV	3
ABQP	ABQP/11.3.43	O	TLV	13-?
QoS Profile	QoS Profile/11.3.28	M	TLV	5
P-TMSI	TMSI/11.3.36	O	TLV	6
eDRX Parameters (note 3)	eDRX Parameters/11.3.122	O	TLV	3
Coverage Class	Coverage Class/11.3.124	O	TLV	3
Enhanced Coverage Additional Information	Enhanced Coverage Additional Information /11.3.141	O	TLV	3
Cell Identifier (note 4)	Cell Identifier/11.3.9	O	TLV	10
MS Radio Access Capability (note 5)	MS Radio Access Capability/11.3.22	O	TLV	7-?
Paging Attempt Information (note 6)	Paging Attempt Information/11.3.125	O	TLV	3
NOTE 1: One and only one of the conditional IEs shall be present. No repeated instances of the conditional IEs are permissible (e.g. one and only one Location Area shall be present). NOTE 2: When network sharing is supported, the PLMN included in the Location Area/ Routeing Area elements can be either the Common PLMN or an Additional PLMN (see 3GPP TS 44.018 [25]). NOTE 3: If the SGSN has valid eDRX Parameters for a TLLI it shall include the eDRX Parameters IE in which case the DRX Parameters IE shall not be included. For the case where PSM is enabled with eDRX and the Active timer is running the SGSN shall always include the negotiated eDRX value in the eDRX Parameters IE. NOTE 4: The cell identity for the cell where the Coverage Class was reported by the MS shall be included if available at the SGSN. NOTE 5: The field shall be present if there is valid MS Radio Access Capability information for the MS known by the SGSN; the field shall not be present otherwise. NOTE 6: The field shall be present if the SGSN is paging a MS due to a positioning event.

10.3.2 PAGING CS

This PDU indicates that a BSS shall initiate a circuit-switched paging procedure for an MS within a group of cells.

PDU type: PAGING-CS

Direction: SGSN to BSS

Table 10.3.2: PAGING CS PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
IMSI	IMSI/11.3.14	M	TLV	5 -10
DRX Parameters	DRX Parameters/11.3.11	M	TLV	4
BVCI (note 1)	BVCI/11.3.6	C	TLV	4
Location Area (note 1)	Location Area/11.3.17	C (note 3)	TLV	7
Routeing Area (note 1)	Routeing Area/11.3.31	C (note 3)	TLV	8
BSS Area Indication (note 1)	BSS Area Indication/11.3.3	C	TLV	3
TLLI	TLLI/11.3.35	O	TLV	6
Channel needed (note 2)	Channel needed/11.3.10	O	TLV	3
eMLPP-Priority (note 2)	eMLPP-Priority/11.3.12	O	TLV	3
TMSI (note 2)	TMSI/11.3.36	O	TLV	6
Global CN-Id (note 2)	Global CN-Id/11.3.69	O	TLV	7
NOTE 1: One and only one of the conditional IEs shall be present. No repeated instances of the conditional IEs are permissible (e.g. one and only one Location Area shall be present). NOTE 2: These fields are provided by the MSC via the Gs-Interface. NOTE 3: When network sharing is supported, the PLMN included in the Location Area/ Routeing Area elements can be either the Common PLMN or an Additional PLMN (see 3GPP TS 44.018 [25]).

10.3.3 RA-CAPABILITY-UPDATE

This PDU requests that the SGSN send an MS’s current Radio Access capability or IMSI to the BSS.

PDU type: RA-CAPABILITY-UPDATE

Direction: BSS to SGSN

Table 10.3.3: RA-CAPABILITY-UPDATE PDU content

Information element	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
Tag	Tag/11.3.34	M	TLV	3

10.3.4 RA-CAPABILITY-UPDATE-ACK

This PDU provides the BSS with an MS’s current Radio Access capability and IMSI.

PDU type: RA-CAPABILITY-UPDATE-ACK

Direction: SGSN to BSS

Table 10.3.4: RA-CAPABILITY-UPDATE-ACK PDU content

Information element	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
Tag	Tag/11.3.34	M	TLV	3
IMSI (note)	IMSI/11.3.14	C	TLV	5 -10
RA-Cap-UPD-CAUSE	RA-Cap-UPD-CAUSE/11.3.30	M	TLV	3
MS Radio Access Capability	MS Radio Access Capability/11.3.22	C	TLV	7-?
NOTE: If RA-Cap-UPD-CAUSE is not set to "OK", then neither the MS Radio Access Capability nor the IMSI shall be present. Otherwise, the IMSI shall be present.

10.3.5 RADIO-STATUS

This PDU indicates that an exception condition related to the radio interface has occurred.

PDU type: RADIO-STATUS

Direction: BSS to SGSN

Table 10.3.5: RADIO-STATUS PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI (note)	TLLI/11.3.35	C	TLV	6
TMSI (note)	TMSI/11.3.36	C	TLV	6
IMSI (note)	IMSI/11.3.14	C	TLV	5-10
Radio Cause	Radio Cause/11.3.29	M	TLV	3
NOTE: One and only one of the conditional IEs shall be present.

10.3.6 SUSPEND

This PDU indicates that an MS wishes to suspend its GPRS service.

PDU type: SUSPEND

Direction: BSS to SGSN

Table 10.3.6: SUSPEND PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
Routeing Area	Routeing Area/11.3.31	M	TLV	8

10.3.7 SUSPEND-ACK

This PDU positively acknowledges the reception of a SUSPEND PDU for an MS.

PDU type: SUSPEND-ACK

Direction: SGSN to BSS

Table 10.3.7: SUSPEND-ACK PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
Routeing Area	Routeing Area/11.3.31	M	TLV	8
Suspend Reference Number	Suspend Reference Number/11.3.33	M	TLV	3

10.3.8 SUSPEND-NACK

This PDU negatively acknowledges the reception of a SUSPEND PDU for an MS.

PDU type: SUSPEND-NACK

Direction: SGSN to BSS

Table 10.3.8: SUSPEND-NACK PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
Routeing Area	Routeing Area/11.3.31	M	TLV	8
Cause	Cause/11.3.8	O	TLV	3

10.3.9 RESUME

This PDU indicates that an MS wishes to RESUME its GPRS service.

PDU type: RESUME

Direction: BSS to SGSN

Table 10.3.9: RESUME PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
Routeing Area	Routeing Area/11.3.31	M	TLV	8
Suspend Reference Number	Suspend Reference Number/11.3.33	M	TLV	3

10.3.10 RESUME-ACK

This PDU positively acknowledges the reception of a RESUME PDU for an MS.

PDU type: RESUME-ACK

Direction: SGSN to BSS

Table 10.3.10: RESUME-ACK PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
Routeing Area	Routeing Area/11.3.31	M	TLV	8

10.3.11 RESUME-NACK

This PDU negatively acknowledges the reception of a RESUME PDU for an MS.

PDU type: RESUME-NACK

Direction: SGSN to BSS

Table 10.3.11: RESUME-NACK PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
Routeing Area	Routeing Area/11.3.31	M	TLV	8
Cause	Cause/11.3.8	O	TLV	3

10.3.12 DUMMY PAGING PS

This PDU indicates that a BSS shall calculate the time until the next paging occasion for the MS indicated in the message.

PDU type: DUMMY-PAGING-PS

Direction: SGSN to BSS

Table 10.3.12: DUMMY PAGING PS PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
IMSI	IMSI/11.3.14	M	TLV	5 -10
Routeing Area	Routeing Area/11.3.31	O	TLV	8
eDRX Parameters	eDRX Parameters/11.3.122	O	TLV	3

10.3.13 DUMMY PAGING PS RESPONSE

This PDU provides the SGSNwith the time until the next paging occasion for the MS indicated in the message.

PDU type: DUMMY-PAGING-PS-RESPONSE

Direction: BSS to SGSN

Table 10.3.13: DUMMY PAGING PS RESPONSE PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
IMSI	IMSI/11.3.14	M	TLV	5 -10
Time Until Next Paging Occasion	Time Until Next Paging Occasion/11.3.123	M	TLV	4

10.3.14 PAGING PS REJECT

This PDU indicates that a BSS has determined the nominal paging group of the MS occurs too far into the future.

PDU type: PAGING-PS-PDU

Direction: BSS to SGSN

Table 10.3.14: PAGING PS REJECT PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
IMSI	IMSI/11.3.14	M	TLV	5 -10
P-TMSI (note 1)	TMSI/11.3.36	O	TLV	6
Time Until Next Paging Occasion	Time Until Next Paging Occasion/11.3.123	M	TLV	4
NOTE 1: Included if present in the corresponding PAGING-PS PDU.

10.3.15 MS REGISTRATION ENQUIRY

This PDU allows the BSS to request registration information for a given mobile station. It is used in MOCN and GWCN configurations for network sharing.

PDU type: MS-REGISTRATION-ENQUIRY

Direction: BSS to SGSN

Table 10.3.15: MS REGISTRATION ENQUIRY PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
IMSI	IMSI/11.3.14	M	TLV	5-10
MME Query	MME Query/11.3.130	O	TLV	3

10.3.16 MS REGISTRATION ENQUIRY RESPONSE

This PDU is sent to the BSS to provide registration information for a given mobile station. It is used in MOCN and GWCN configurations for network sharing.

PDU type: MS-REGISTRATION-ENQUIRY-RESPONSE

Direction: SGSN to BSS

Table 10.3.16: MS REGISTRATION ENQUIRY RESPONSE PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
IMSI	IMSI/11.3.14	M	TLV	5-10
PS Registered Operator (note 1)	PLMN Identity/11.3.129	O	TLV	5
NOTE 1: This IE identifies the serving CN operator for the mobile station associated to the IMSI. Omitting this IE from the message has the significance of no serving CN operator for the mobile station (IMSI).

10.4 PDU functional definitions and contents at NM SAP

10.4.1 FLUSH-LL

This PDU informs a BSS that an MS has moved from one cell to another.

PDU type: FLUSH-LL

Direction: SGSN to BSS

Table 10.4.1: FLUSH-LL PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
BVCI (old)	BVCI/11.3.6	M	TLV	4
BVCI (new)	BVCI/11.3.6	O	TLV	4
NSEI (new)	NSEI/11.3.48	O (note)	TLV	4
NOTE: NSEI (new) is included if the SGSN supports "Inter-NSE re-routing" or "LCS Procedures" and the old NSE supports the "Inter-NSE re-routing" or "LCS Procedures" and the cell change is an Inter-NSE cell change within a routing area.

10.4.2 FLUSH-LL-ACK

This PDU indicates that LLC-PDU(s) buffered for an MS in the old cell have been either deleted or transferred to the new cell within the routing area.

PDU type: FLUSH-LL-ACK

Direction: BSS to SGSN

Table 10.4.2: FLUSH-LL-ACK PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
Flush Action	Flush Action/11.3.13	M	TLV	3
BVCI (new)	BVCI/11.3.13	C (note 1)	TLV	4
Number of octets affected	Number of octets affected/11.3.41	M	TLV	5
NSEI (new)	NSEI/11.3.48	C (note 2)	TLV	4
NOTE 1: BVCI (new) is included only if Flush action indicated that LLC-PDUs are transferred. NOTE 2: NSEI (new) is included only if BVCI(new) is included and NSEI (new) is received in the FLUSH-LL PDU.

10.4.3 LLC-DISCARDED

This PDU indicates that a number of buffered LLC-PDUs in a cell for an MS have been deleted inside the BSS (because of PDU Lifetime expiration or radio outage for example). The LLC frames and the related octets deleted by the BSS as a consequence of a FLUSH-LL procedure (see sub-clause 8.1) shall not be reported a second time by means of an LLC-DISCARDED PDU.

PDU type: LLC-DISCARDED

Direction: BSS to SGSN

Table 10.4.3: LLC-DISCARDED PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
LLC Frames Discarded	LLC Frames Discarded/11.3.16	M	TLV	3
BVCI	BVCI/11.3.6	M	TLV	4
Number of octets deleted	Number of octets affected/11.3.41	M	TLV	5
PFI (note)	PFI/11.3.42	O	TLV	3
NOTE: The PFI may be provided in case the PFC flow control feature is negotiated. It corresponds to the Packet Flow Identifier of the PFC for which LLC frames have been discarded.

10.4.4 FLOW-CONTROL-BVC

This PDU informs the flow control mechanism at an SGSN of the status of a BVC’s maximum acceptable SGSN to BSS throughput on the Gb interface.

PDU type: FLOW-CONTROL-BVC

Direction: BSS to SGSN

Table 10.4.4: FLOW-CONTROL-BVC PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
Tag	Tag/11.3.34	M	TLV	3
BVC Bucket Size	BVC Bucket Size/11.3.5	M	TLV	4
Bucket Leak Rate	Bucket Leak Rate/11.3.4	M	TLV	4
Bmax default MS	Bmax default MS/11.3.2	M	TLV	4
R_default_MS	R_default_MS/11.3.32	M	TLV	4
Bucket_Full Ratio	Bucket_Full Ratio/11.3.46	C	TLV	3
BVC Measurement	BVC Measurement/11.3.7	O	TLV	4
Flow Control Granularity (note)	Flow Control Granularity/11.3.102	O	TLV	3
NOTE: The Flow Control Granularity shall be provided in case the Gigabit Interface feature is negotiated.

10.4.5 FLOW-CONTROL-BVC-ACK

This PDU informs the flow control mechanism at the BSS that the SGSN has received the FLOW-CONTROL-BVC PDU indicated by the Tag.

PDU type: FLOW-CONTROL-BVC-ACK

Direction: SGSN to BSS

Table 10.4.5: FLOW-CONTROL-BVC-ACK PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
Tag	Tag/11.3.34	M	TLV	3

10.4.6 FLOW-CONTROL-MS

This PDU informs the flow control mechanism at an SGSN of the status of an MS’s maximum acceptable SGSN to BSS throughput on the Gb interface.

PDU type: FLOW-CONTROL-MS

Direction: BSS to SGSN

Table 10.4.6: FLOW-CONTROL-MS PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
Tag	Tag/11.3.34	M	TLV	3
MS Bucket Size	MS Bucket Size/11.3.21	M	TLV	4
Bucket Leak rate	Bucket Leak rate/11.3.4	M	TLV	4
Bucket_Full Ratio	Bucket_Full Ratio/11.3.46	C	TLV	3
Flow Control Granularity (note)	Flow Control Granularity/11.3.102	O	TLV	3
NOTE: The Flow Control Granularity shall be provided in case the Gigabit Interface feature is negotiated.

10.4.7 FLOW-CONTROL-MS-ACK

This PDU informs the flow control mechanism at the BSS that the SGSN has received the FLOW-CONTROL-MS PDU indicated by the TLLI and the Tag.

PDU type: FLOW-CONTROL-MS-ACK

Direction: SGSN to BSS

Table 10.4.7: FLOW-CONTROL-MS-ACK PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
Tag	Tag/11.3.34	M	TLV	3

10.4.8 BVC-BLOCK

This PDU indicates that the contained BVC shall be blocked at the recipient entity.

PDU type: BVC-BLOCK

Direction: BSS to SGSN

Table 10.4.8: BVC-BLOCK PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
BVCI	BVCI/11.3.6	M	TLV	4
Cause	Cause/11.3.8	M	TLV	3

10.4.9 BVC-BLOCK-ACK

This PDU acknowledges that a BVC has been blocked.

PDU type: BVC-BLOCK-ACK

Direction: SGSN to BSS

Table 10.4.9: BVC-BLOCK-ACK PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
BVCI	BVCI/11.3.6	M	TLV	4

10.4.10 BVC-UNBLOCK

This PDU indicates that the identified BVC shall be unblocked at the recipient entity.

PDU type: BVC-UNBLOCK

Direction: BSS to SGSN

Table 10.4.10: BVC-UNBLOCK PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
BVCI	BVCI/11.3.6	M	TLV	4

10.4.11 BVC-UNBLOCK-ACK

This PDU acknowledges that a BVC has been unblocked.

PDU type: BVC-UNBLOCK-ACK

Direction: SGSN to BSS

Table 10.4.11: BVC-UNBLOCK-ACK PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
BVCI	BVCI/11.3.6	M	TLV	4

10.4.12 BVC-RESET

This PDU indicates that BVC initialisation is required, e.g. because of a BVC failure.

PDU type: BVC-RESET

Direction: SGSN to BSS, BSS to SGSN

Table 10.4.12: BVC-RESET PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
BVCI	BVCI/11.3.6	M	TLV	4
Cause	Cause/11.3.8	M	TLV	3
Cell Identifier (note 1)		C	TLV	10
Feature bitmap (note 2)	Feature bitmap/11.3.45	O	TLV	3
Extended Feature Bitmap (note 3)	Extended Feature Bitmap/11.3.84	O	TLV	3
NOTE 1: The Cell Identifier IE is mandatory in the BVC-RESET PDU sent from BSS to SGSN in order to reset a BVC corresponding to a PTP functional entity. The Cell Identifier IE shall not be used in any other BVC-RESET PDU. NOTE 2: The Feature bitmap is only sent in a BVC-RESET PDU related to the signalling BVC. Absence of this IE implies no optional features are available over the NSE. NOTE 3: The Extended Feature Bitmap is only sent in a BVC-RESET PDU related to the signalling BVC.

10.4.13 BVC-RESET-ACK

This PDU indicates that BVC initialisation has been executed.

PDU type: BVC-RESET-ACK

Direction: BSS to SGSN, SGSN to BSS

Table 10.4.13: BVC-RESET-ACK PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
BVCI	BVCI/11.3.6	M	TLV	4
Cell Identifier (note 1)		C	TLV	10
Feature bitmap (note 2)	Feature bitmap/11.3.45	O	TLV	3
Extended Feature Bitmap (note 3)	Extended Feature Bitmap/11.3.84	O	TLV	3
NOTE 1: The Cell Identifier IE is mandatory in the BVC-RESET-ACK PDU sent from BSS to SGSN in response to reset a BVC corresponding to a PTP functional entity. The Cell Identifier IE shall not be used in any other BVC-RESET-ACK PDU. NOTE 2: The Feature bitmap is only sent in a BVC-RESET-ACK PDU related to the signalling BVC. Absence of this IE implies no optional features are available over the NSE. NOTE 3: The Extended Feature Bitmap is only sent in a BVC-RESET-ACK PDU related to the signalling BVC.

10.4.14 STATUS

This PDU indicates that an exception condition occurred.

PDU type: STATUS

Direction: SGSN to BSS, BSS to SGSN

Table 10.4.14: STATUS PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
Cause	Cause/11.3.8	M	TLV	3
BVCI	BVCI/11.3.6	C	TLV	4
PDU In Error (note)	PDU In Error/11.3.24	O	TLV	3-?
NOTE: This is the whole PDU (starting with the [PDU type]) within which an error was detected. This PDU may be truncated if it exceeds the information carrying capacity of the underlying network service.

10.4.14.1 Static conditions for BVCI

The "BVCI" IE shall be included when the "Cause" IE is set to one of the following values:

a) "BVCI blocked";

b) "BVCI unknown";

and shall not be included otherwise.

10.4.15 SGSN-INVOKE-TRACE

This PDU indicates that the BSS shall begin the production of a trace record for an MS.

PDU type: SGSN-INVOKE-TRACE

Direction: SGSN to BSS

Table 10.4.15: SGSN-INVOKE-TRACE PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
Trace Type	Trace Type/11.3.38	M	TLV	3
Trace Reference	Trace Reference/11.3.37	M	TLV	4
Trigger Id	Trigger Id/11.3.40	O	TLV	4-24
Mobile Id	Mobile Id/11.3.20	O	TLV	3-10
OMC Id	OMC Id/11.3.23	O	TLV	4-24
TransactionId	TransactionId/11.3.39	O	TLV	4

10.4.16 DOWNLOAD-BSS-PFC

This PDU requests a SGSN to initiate a CREATE-BSS-PFC procedure.

PDU type: DOWNLOAD-BSS-PFC

Direction: BSS to SGSN

Table 10.4.16: DOWNLOAD-BSS-PFC PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
PFI	PFI/11.3.42	M	TLV	3

10.4.17 CREATE-BSS-PFC

This PDU allows the SGSN to request that a BSS create or modify a BSS Packet Flow Context.

PDU type: CREATE-BSS-PFC

Direction: SGSN to BSS

Table 10.4.17: CREATE-BSS-PFC PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
IMSI	IMSI/11.3.14	O (note 4)	TLV	5 -10
PFI	PFI/11.3.42	M	TLV	3
PFT	GPRS Timer/11.3.44	M	TLV	3
ABQP	ABQP/11.3.43	M	TLV	13-?
Service UTRAN CCO	Service UTRAN CCO/11.3.47	O	TLV	3
MS Radio Access Capability	MS Radio Access Capability/11.3.22	O (note 1)	TLV	7-?
Allocation/Retention Priority	Priority/11.3.27	O	TLV	3
T10	GPRS Timer/11.3.44	C (note 2)	TLV	3
Inter RAT Handover Info	Inter RAT Handover Info/11.3.94	O (note 3)	TLV	3-?
E-UTRAN Inter RAT Handover Info	E-UTRAN Inter RAT Handover Info/11.3.104	O (note 3)	TLV	3-?
Subscriber Profile ID for RAT/Frequency priority (note 5)	Subscriber Profile ID for RAT/Frequency priority/11.3.105	O	TLV	3
NOTE 1: This Information Element shall be present if there is valid MS Radio Access Capability information known by the SGSN. NOTE 2: This information element shall be present if the Allocation/Retention Priority IE is present and if queuing is allowed for the PFC. NOTE 3: This information element shall be present if available in the SGSN. NOTE 4: This information element shall be present if the IMSI is available in the SGSN. NOTE 5: This IE may be included if available in the SGSN. If the Service UTRAN CCO IE is present with the value of "shall not" the Service UTRAN CCO IE takes precedence over this IE.

10.4.18 CREATE-BSS-PFC-ACK

This PDU allows the BSS to acknowledge a request from the SGSN for the creation or modification of a BSS Packet Flow Context.

PDU type: CREATE-BSS-PFC-ACK

Direction: BSS to SGSN

Table 10.4.18: CREATE-BSS-PFC-ACK PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
PFI	PFI/11.3.42	M	TLV	3
ABQP	ABQP/11.3.43	M	TLV	13-?
Cause	Cause/11.3.8	O	TLV	3

10.4.19 CREATE-BSS-PFC-NACK

This PDU allows the BSS to Nack a request from the SGSN for the creation of a BSS Packet Flow Context.

PDU type: CREATE-BSS-PFC-NACK

Direction: BSS to SGSN

Table 10.4.19: CREATE-BSS-PFC-NACK PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
PFI	PFI/11.3.42	M	TLV	3
Cause	Cause/11.3.8	M	TLV	3

10.4.20 MODIFY-BSS-PFC

This PDU allows the BSS to request a modification of a BSS Packet Flow Context.

PDU type: MODIFY-BSS-PFC

Direction: BSS to SGSN

Table 10.4.20: MODIFY-BSS-PFC PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
PFI	PFI/11.3.42	M	TLV	3
ABQP	ABQP/11.3.43	M	TLV	13-?

10.4.21 MODIFY-BSS-PFC-ACK

This PDU allows the SGSN to acknowledge a modification to a BSS Packet Flow Context.

PDU type: MODIFY-BSS-PFC-ACK

Direction: SGSN to BSS

Table 10.4.21: MODIFY-BSS-PFC-ACK PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
PFI	PFI/11.3.42	M	TLV	3
PFT	GPRS Timer/11.3.44	M	TLV	3
ABQP	ABQP/11.3.43	M	TLV	13-?

10.4.22 DELETE-BSS-PFC

This PDU allows the SGSN to request that a BSS delete a BSS Packet Flow Context.

PDU type: DELETE-BSS-PFC

Direction: SGSN to BSS

Table 10.4.22: DELETE-BSS-PFC PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
PFI	PFI/11.3.42	M	TLV	3

10.4.23 DELETE-BSS-PFC-ACK

This PDU allows the BSS to acknowledge a request for the deletion of a BSS Packet Flow Context.

PDU type: DELETE-BSS-PFC-ACK

Direction: BSS to SGSN

Table 10.4.23: DELETE-BSS-PFC-ACK PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
PFI	PFI/11.3.42	M	TLV	3

10.4.24 FLOW-CONTROL-PFC

This PDU provides the SGSN with flow control information regarding one or more PFC(s) of a given Mobile Station.

PDU type: FLOW-CONTROL-PFC

Direction: BSS to SGSN

Table 10.4.24: FLOW-CONTROL-PFC PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
Tag	Tag/11.3.34	M	TLV	3
MS Bucket Size	MS Bucket Size/11.3.21	O	TLV	4
Bucket Leak rate	Bucket Leak rate/11.3.4	O	TLV	4
Bucket_Full Ratio	Bucket_Full Ratio/11.3.46	O	TLV	3
PFC flow control parameters	PFC flow control parameters/11.3.68	M	TLV
Flow Control Granularity (note)	Flow Control Granularity/11.3.102	O	TLV	3
NOTE: The Flow Control Granularity shall be provided in case the Gigabit Interface feature is negotiated.

10.4.25 FLOW-CONTROL-PFC-ACK

This PDU informs the flow control mechanism at the BSS that the SGSN has received the FLOW-CONTROL-PFC PDU indicated by the TLLI and the Tag.

PDU type: FLOW-CONTROL-PFC-ACK

Direction: SGSN to BSS

Table 10.4.25: FLOW-CONTROL-PFC-ACK PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
Tag	Tag/11.3.34	M	TLV	3

10.4.26 DELETE-BSS-PFC-REQ

This PDU allows the BSS to inform the SGSN that the BSS Packet Flow Context cannot be supported anymore

PDU type: DELETE-BSS-PFC-REQ

Direction: BSS to SGSN

Table 10.4.26: DELETE-BSS-PFC-REQ PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
PFI	PFI/11.3.42	M	TLV	3
Cause	Cause/11.3.8	M	TLV	3

10.4.27 PS-HANDOVER-REQUIRED

This PDU initiates the allocation of resources in the target system for an MS.

PDU type: PS-HANDOVER-REQUIRED

Direction: BSS to SGSN

Table 10.4.27: PS-HANDOVER-REQUIRED PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
Cause	Cause/11.3.8	M	TLV	3
Source Cell Identifier	Cell Identifier/11.3.9	M	TLV	10
Target Cell Identifier (note 2)	Cell Identifier/11.3.9	C	TLV	10
Source BSS to Target BSS Transparent Container (note 1)	Source BSS to Target BSS Transparent Container/11.3.79	C	TLV	10-?
Target RNC Identifier (note 2) (note 3)	RNC Identifier/11.3.87	C	TLV	10
Source to Target Transparent Container (note 1)	Source to Target Transparent Container/11.3.85	C	TLV	3-?
Active PFCs List	Active PFCs List/11.3.95c	M	TLV	3-?
Target eNB identifier (note 2) (note 3)	eNB Identifier/11.3.103	C	TLV	3-n
Reliable Inter RAT Handover Info (note 4)	Reliable Inter RAT Handover Info/11.3.107	C	TLV	3
CSG Identifier (note 5)	CSG Identifier/11.3.109	C	TLV	7
TAC (note 6)	Tracking Area Code/11.3.110	C	TLV	5
NOTE 1: One and only one of these two conditional IEs shall be present depending on the target RAT as specified in subclause 8a.4.
NOTE 2: One and only one of these three conditional IEs shall be present depending on the target RAT as specified in subclause 8a.4.
NOTE 3: In case of PS handover to E-UTRAN, the Target RNC Identifier IE (carrying the Corresponding RNC-ID) may be present as an alternative to the Target eNB identifier IE.
NOTE 4: This IE shall be present when the target cell is a GERAN cell.
NOTE 5: This IE shall be present when the target cell is a CSG or hybrid cell.
NOTE 6: This IE shall be present when the target cell is a E-UTRAN CSG or hybrid cell.

10.4.28 PS-HANDOVER-REQUIRED-ACK

This PDU indicates that resources have been allocated in the target system and that the BSS may initiate the channel change attempt for the corresponding MS.

PDU type: PS-HANDOVER-REQUIRED-ACK

Direction: SGSN to BSS

Table 10.4.28: PS-HANDOVER-REQUIRED-ACK PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
List of set-up PFCs	List of set-up PFCs/11.3.83	M	TLV	3-?
Target BSS to Source BSS Transparent Container (note)	Target BSS to Source BSS Transparent Container/11.3.80	C	TLV	3-?
Target to Source Transparent Container (note)	Target to Source Transparent Container/11.3.86	C	TLV	3-?
NOTE: One and only one of these two conditional IEs shall be present depending on the target RAT as specified in subclause 8a.4.

10.4.29 PS-HANDOVER-REQUIRED-NACK

This PDU informs the source BSS about failed resource allocation in the target system.

PDU type: PS-HANDOVER-REQUIRED-NACK

Direction: SGSN to BSS

Table 10.4.29: PS-HANDOVER-REQUIRED-NACK PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
Cause	Cause/11.3.8	M	TLV	3

10.4.30 PS-HANDOVER-REQUEST

This PDU initiates the allocation of resources for one or more PFCs in the target BSS for an MS.

PDU type: PS-HANDOVER-REQUEST

Direction: SGSN to BSS

Table 10.4.30: PS-HANDOVER-REQUEST PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
IMSI	IMSI/11.3.14	M	TLV	5-10
Cause	Cause/11.3.8	M	TLV	3
Source Cell Identifier (note 1)	Cell Identifier/11.3.9	C	TLV	10
Source RNC Identifier (note 1)	RNC Identifier/11.3.87	C	TLV	10
Target Cell Identifier	Cell Identifier/11.3.9	M	TLV	10
Source BSS to Target BSS Transparent Container	Source BSS to Target BSS Transparent Container/11.3.79	M	TLV	7-?
PFCs to be set-up list	PFCs to be set-up list/11.3.82	M	TLV	22-?
NAS container for PS Handover	NAS container for PS Handover/11.3.81	O	TLV	3-?
Service UTRAN CCO	Service UTRAN CCO/11.3.47	O	TLV	3
Subscriber Profile ID for RAT/Frequency priority (note 2)	Subscriber Profile ID for RAT/Frequency priority /11.3.105	O	TLV	3
Reliable Inter RAT Handover Info (note 3)	Reliable Inter RAT Handover Info/11.3.107	C	TLV	3
NOTE 1: In case of PS handover from GERAN or UTRAN, one and only one of these two conditional IEs shall be present depending on the source RAT. In case of PS handover from E-UTRAN, neither of these two conditional IEs shall be present. NOTE 2: This IE may be included if available in the SGSN. If the Service UTRAN CCO IE is present with the value of "shall not" the Service UTRAN CCO IE takes precedence over this IE. NOTE 3: This IE shall be included if sent by the source BSS.

10.4.31 PS-HANDOVER-REQUEST-ACK

This PDU acknowledges the successful allocation of resources in the target BSS.

PDU type: PS-HANDOVER-REQUEST-ACK

Direction: BSS to SGSN

Table 10.4.31: PS-HANDOVER-REQUEST-ACK PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
List of set-up PFCs	List of set-up PFCs/11.3.83	M	TLV	3-?
Target BSS to Source BSS Transparent Container	Target BSS to Source BSS Transparent Container/11.3.80	M	TLV	3-?

10.4.32 PS-HANDOVER-REQUEST-NACK

This PDU informs the SGSN about failed resource allocation in the target BSS.

PDU type: PS-HANDOVER-REQUEST-NACK

Direction: BSS to SGSN

Table 10.4.32: PS-HANDOVER-REQUEST-NACK PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
Cause	Cause/11.3.8	M	TLV	3

10.4.33 PS-HANDOVER-COMPLETE

This PDU informs the SGSN about successful channel change for an MS.

PDU type: PS-HANDOVER-COMPLETE

Direction: BSS to SGSN

Table 10.4.33: PS-HANDOVER-COMPLETE PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
IMSI	IMSI/11.3.14	M	TLV	5-10
Target Cell Identifier (note 1)	Cell Identifier/11.3.9	O	TLV	10
Request for Inter RAT Handover Info (note 2)	Request for Inter RAT Handover Info/11.3.106	O	TLV	3
NOTE 1: The Target Cell Identifier IE is included only for optimised Intra-BSS PS Handover. NOTE 2: This IE shall be included if the BSS supports inter-RAT PS handover to UTRAN.

10.4.34 PS-HANDOVER-CANCEL

This PDU cancels the handover for an MS.

PDU type: PS-HANDOVER-CANCEL

Direction: BSS to SGSN

Table 10.4.34: PS-HANDOVER-CANCEL PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
Cause	Cause/11.3.8	M	TLV	3
Source Cell Identifier	Cell Identifier/11.3.9	M	TLV	10
Target Cell Identifier (note 1)	Cell Identifier/11.3.9	C	TLV	10
Target RNC Identifier (note 1) (note 2)	RNC Identifier/11.3.87	C	TLV	10
Target eNB Identifier (note 1) (note 2)	eNB Identifier/11.3.103	C	TLV	3-n
NOTE 1: One and only one of these three conditional IEs shall be present depending on the target RAT as specified in subclause 8a.7.
NOTE 2: In case of PS handover to E-UTRAN, the Target RNC Identifier IE (carrying the Corresponding RNC-ID) may be present as an alternative to the Target eNB identifier IE.

10.4.35 PS-HANDOVER-COMPLETE-ACK

This PDU provides to the BSS the Inter RAT Handover Info IE. It is sent only if requested by the BSS.

PDU type: PS-HANDOVER-COMPLETE-ACK

Direction: SGSN to BSS

Table 10.4.35: PS-HANDOVER-COMPLETE-ACK PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
Inter RAT Handover Info	Inter RAT Handover Info/11.3.94	M (note 1)	TLV	3-?
E-UTRAN Inter RAT Handover Info	E-UTRAN Inter RAT Handover Info/11.3.104	O (note 1)	TLV	3-?
NOTE 1: Only Inter RAT Handover Info IE shall be present in the message. E-UTRAN Inter RAT Handover Info IE was defined in an earlier version of the protocol and shall not be used.

10.4.36 OVERLOAD

This PDU informs the BSS that the SGSN sending the PDU is in an overload situation and the signalling traffic to the SGSN should be reduced.

PDU type: OVERLOAD

Direction: SGSN to BSS

Table 10.4.36: OVERLOAD PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
Priority Class Indicator	Priority Class Indicator/11.3.118	M	TLV	3

10.5 PDU functional definitions and contents at LCS SAP

10.5.1 PERFORM-LOCATION-REQUEST

This PDU allows the SGSN to request the BSS to perform a location procedure for the target MS.

PDU type: PERFORM-LOCATION-REQUEST

Direction: SGSN to BSS

Table 10.5.1: PERFORM-LOCATION-REQUEST PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
IMSI	IMSI/11.3.14	M	TLV	5-10
DRX Parameters (note 1)	DRX Parameters/11.3.11	O	TLV	4
BVCI (PCU-PTP)	BVCI/11.3.6	M	TLV	4
NSEI (PCU-PTP)	NSEI/11.3.48	M	TLV	4-?
Location Type	Location Type/11.3.53	M	TLV	3-?
Cell Identifier	Cell Identifier/11.3.9	M	TLV	10
LCS Capability (note 2)	LCS Capability/11.3.59	O	TLV	3-?
LCS Priority	LCS Priority/11.3.57	O	TLV	3-?
LCS QoS	LCS QoS/11.3.50	O	TLV	3-?
LCS Client Type (note 3)	LCS Client Type/11.3.51	C	TLV	3-?
Requested GPS Assistance Data (note 4)	Requested GPS Assistance Data/11.3.52	O	TLV	3-?
IMEI (note 5)	IMEI/11.3.91	O	TLV	10
GANSS Location Type	GANSS Location Type / 11.3.100	C	TLV	3
Requested GANSS Assistance Data (note 6)	Requested GANSS Assistance Data/11.3.99	O	TLV	3-?
eDRX Parameters (note 7)	eDRX Parameters/11.3.122	O	TLV	3
Coverage Class	Coverage Class/11.3.124	O	TLV	3
MS Radio Access Capability (note 8)	MS Radio Access Capability/11.3.22	O	TLV	7-?
MultilaterationTiming Advance (note 9)	MultilaterationTiming Advance/11.3.137	O	TLV	4
MS Sync Accuracy (note 9)	MS Sync Accuracy/11.3.138	O	TLV	3
BTS Reception Accuracy Level (note 9)	BTS Reception Accuracy Level/11.3.139	O	TLV	3
MTA Access Security Required (note 10)	MTA Access Security Required/11.3.142	O	TLV	3
NOTE 1: This IE is present if the SGSN has valid DRX Parameters for the TLLI. NOTE 2: This IE is present if the SGSN has received the information from the MS. NOTE 3: This IE is present if the location type indicates a request for a location estimate and is optional otherwise. NOTE 4: This IE is present if GPS assistance data is requested. NOTE 5: The IMEI could be sent in addition to the IMSI for the purpose of allowing correlation between the two identities. NOTE 6 This IE is present if GANSS assistance data is requested. NOTE 7: If the SGSN has valid eDRX Parameters for a TLLI it shall include the eDRX Parameters IE in which case the DRX Parameters IE shall not be included. NOTE 8: The field shall be present if there is valid MS Radio Access Capability information for the MS known by the SGSN; the field shall not be present otherwise. NOTE 9: The IE shall be present if it was received for a given MS no more than 5 seconds prior to sending the PERFORM-LOCATION-REQUEST PDU to the BSS for that MS; the field shall not be present otherwise. Note 10: The IE is included if SGSN does not support LLC security and decides to request the use of MTA Access Security (MTA Access Security method or the BSS Duplication Detection method may be indicated).

10.5.2 PERFORM-LOCATION-RESPONSE

This PDU allows the BSS to respond to the SGSN after the completion of the location procedure.

PDU type: PERFORM-LOCATION-RESPONSE

Direction: BSS to SGSN

Table 10.5.2: PERFORM-LOCATION-RESPONSE PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
BVCI (PCU-PTP)	BVCI/11.3.6	M	TLV	4
Location Estimate (note 1)	Location Estimate/11.3.54	C	TLV	3-?
Positioning Data	Positioning Data/11.3.55	O	TLV	3-?
Deciphering Keys (note 2)	Deciphering Keys/11.3.56	C	TLV	3-?
LCS Cause (note 3)	LCS Cause/11.3.58	O	TLV	3-?
Velocity Data	Velocity Data/11.3.96	O	TLV	3-?
GANSS Positioning Data	GANSS Positioning Data / 11.3.101	O	TLV	3-?
MTA Sequence	MTA Sequence/11.3.143	O	TLV	7-?
MTA Signature	MTA Signature/11.3.144	O	TLV	6
NOTE 1: This IE is present if the location of the target MS was requested and the procedure succeeded. NOTE 2: This IE is present if the deciphering keys were requested and the procedure succeeded. NOTE 3: This IE is present if the procedure failed.

10.5.3 PERFORM-LOCATION-ABORT

This PDU allows the SGSN to request the BSS to ABORT the LCS procedure.

PDU type: PERFORM-LOCATION-ABORT

Direction: SGSN to BSS

Table 10.5.3: PERFORM-LOCATION-ABORT PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
BVCI (PCU-PTP)	BVCI/11.3.6	M	TLV	4
LCS Cause	LCS Cause/11.3.58	M	TLV	3-?

10.5.4 POSITION-COMMAND

This PDU allows the BSS to request the SGSN to perform the position command procedure.

PDU type: POSITION-COMMAND

Direction: BSS to SGSN

Table 10.5.4: POSITION-COMMAND PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
BVCI (PCU-PTP)	BVCI/11.3.6	M	TLV	4
RRLP Flags	RRLP Flags/11.3.60	M	TLV	3
RRLP APDU	RRLP APDU/11.3.49	M	TLV	3-?
Multilateration Timer	Multilateration Timer/11.3.136	O	TLV	3
Timing Advance Request	Timing Advance Request/11.3.140	O	TLV	3

10.5.5 POSITION-RESPONSE

This PDU allows the SGSN to respond to the position command request procedure.

PDU type: POSITION-RESPONSE

Direction: SGSN to BSS

Table 10.5.5: POSITION-RESPONSE PDU content

Information elements	Type / Reference	Presence	Format	Length
PDU type	PDU type/11.3.26	M	V	1
TLLI	TLLI/11.3.35	M	TLV	6
BVCI (PCU-PTP)	BVCI/11.3.6	M	TLV	4
RRLP Flags a)	RRLP Flags/11.3.60	C	TLV	3
RRLP APDU a)	RRLP APDU/11.3.49	C	TLV	3-?
LCS Cause b)	LCS Cause/11.3.58	O	TLV	3-?
a) This IE is present if the procedure succeeded. b) This IE is present if the procedure failed.