ETSI TS 102 111-1 V1.1.1 (2002-09)

SLOVENSKI STANDARD
01-januar-2005
Storitve in protokoli za napredna omrežja (SPAN) – Preskušanje integracije
omrežja s splošno radijsko storitvijo s paketiranimi podatki (GPRS) in omrežij z
internetnim protokolom (IP) – 1. del: Zgradba preskušalnega niza in namen
preskušanja (TSS&TP)
Services and Protocols for Advanced Networks (SPAN); Network Integration Testing
between General Packet Radio Service (GPRS) and Internet Protocol (IP) Networks;
Part 1: Test Suite Strucutre and Test Purposes (TSS&TP)
Ta slovenski standard je istoveten z: TS 102 111-1 Version 1.1.1
ICS:
33.040.01 Telekomunikacijski sistemi Telecommunication systems
na splošno in general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

Technical Specification
Services and Protocols for Advance Network (SPAN);
Network Integration Testing between
General Packet Radio Service (GPRS)
and Internet Protocol (IP) Networks
Part 1: Test Suite Structure and Test purposes (TSS&TP)

2 ETSI TS 102 111-1 V1.1.1 (2002-09)

Reference
DTS/SPAN-130306-1
Keywords
IP, GPRS, 3GPP, NIT, TSS&TP, testing
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, send your comment to:
editor@etsi.fr
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2002.
All rights reserved.
TM TM TM
DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members.
TM
TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI TS 102 111-1 V1.1.1 (2002-09)
Contents
Intellectual Property Rights.4
Foreword.4
Introduction .4
1 Scope.5
2 References.5
3 Definitions and abbreviations.6
3.1 Definitions related to conformance testing.6
4 Abbreviations.6
5 Numbering Scheme.7
5.1 Examples.8
6 Test Suite Structure (TSS).8
7 Test configurations and test procedures .9
7.1 User Plane for UMTS.9
7.2 Control Plane.10
7.3 PDP Context Activation Procedure .11
7.3.1 Successful Network-Requested PDP Context Activation Procedure.12
8.1 PDP context activation .13
8.1.1 GPRS R99 to external PDP network.13
8.1.1.1 Successful.13
8.1.1.1.1 Application models.18
8.1.2 GPRS R98 to external PDP network.53
8.2 Basic GPRS scenarios .61
8.2.1 Successful.61
8.2.1.1 Activate Secondary PDP Context Request.61
8.2.1.2 Modify PDP Context Request.63
8.2.1.3 PDP context deactivation .64
8.2.1.3.1 PDP context deactivation initiated by the UE .64
8.2.1.3.2 PDP context deactivation initiated by the network.66
8.2.1.4 Unsuccessful.67
8.2.1.4.1 Activate PDP Context Request-unsuccessful .67
8.2.1.4.2 Activate Secondary PDP Context Request-unsuccessful .70
8.2.1.4.3 PDP Context Modification - unsuccessful.75
Annex A (normative): Other testings .79
A.1 Session Management Tests .79
A.2 Gi/Gn Interfaces Interoperability Tests.85
A.3 Performance Tests.89
Annex B (informative): Traffic models based on applications.90
B.1 FTP application model .90
B.2 HTTP application model .94
B.3 H.323 application model (Netmeeting) .100
B.4 SIP application model .102
Annex C (informative): Bibliography.103
History .104
ETSI
4 ETSI TS 102 111-1 V1.1.1 (2002-09)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Services and Protocols for
Advanced Networks (SPAN).
The present document was developed by EURESCOM P1106 as Deliverable 2 Volume 4 and made freely and publicly
available to ETSI TC SPAN for publication.
The present document is part 1 of a multi-part deliverable covering the Network Integration Testing between GPRS and
IP Networks, as identified below:
Part 1: "Test Suite Structure and Test Purposes (TSS&TP)";
Part 2: "Abstract Test Suite (ATS), Implementation Conformance Statement (ICS) and partial Implementation
eXtra Information for Testing (PIXIT) proformas";
Introduction
The present document contains the Test Suite Structure and Test Purposes (TSS&TP) for Network Integration Testing
for the European PLMN, covering Network Integration Testing (NIT) between GPRS and non managed IP Networks.
ETSI
5 ETSI TS 102 111-1 V1.1.1 (2002-09)
1 Scope
The present document specifies the Test Suite Structure and Test Purposes for Network Integration Testing to verify the
overall compatibility between GPRS (UMTS, GSM Phase 2+) and IP Networks. The objective is to verify the level of
international or national end-to-end support of GPRS services.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
[1] ETSI TS 124 008: Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Mobile radio interface layer 3 specification, Core Network
protocols - Stage 3 (3G TS 24.008)".
[2] ETSI TS 100 940: Digital cellular telecommunications system (Phase 2+); Mobile radio interface
layer 3 specification (GSM 04.08)".
[3] ISO/IEC 9646-1: "Information Technology-OSI Conformance Testing Methodology and
Framework, Part 1: General Concepts".
[4] ETSI TS 125 323: "Universal Mobile Telecommunications System (UMTS); Packet Data
Convergence Protocol (PDCP) specification (3GPP TS 25.323)".
[5] ETSI TS 129 060: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); General Packet Radio Service (GPRS); GPRS Tunnelling
Protocol (GTP) across the Gn and Gp interface (3GPP TS 29.060)".
[6] ETSI TS 125 322: "Universal Mobile Telecommunications System (UMTS); Radio Link Control
(RLC) protocol specification (3GPP TS 25.322)".
[7] ITU-T Recommendation I.361: "B-ISDN ATM layer specification".
[8] ETSI TS 125 321: "Universal Mobile Telecommunications System (UMTS); Medium Access
Control (MAC) protocol specification (3GPP TS 25.321)".
[9] ETSI TS 123 040: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Technical realization of Short Message Service (SMS)
(3GPP TS 23.040)".
[10] ETSI TS 125 413: "Universal Mobile Telecommunications System (UMTS); UTRAN Iu interface
RANAP signalling (3GPP TS 25.413)".
[11] ETSI TS 123 121: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Architecture Requirements for release 99
(3GPP TS 23.121)".
[12] ETSI TS 123 107: "Universal Mobile Telecommunications System (UMTS); Quality of Service
(QoS) concept and architecture (3GPP TS 23.107)".
[13] ITU-T Recommendation H.323: "Packet-based multimedia communications systems".
ETSI
6 ETSI TS 102 111-1 V1.1.1 (2002-09)
3 Definitions and abbreviations
3.1 Definitions related to conformance testing
Abstract Test Case (ATC): Refer to ISO/IEC 9646-1 [3].
Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [3].
Implementation Under Test(IUP): Refer to ISO/IEC 9646-1 [3].
lower tester: Refer to ISO/IEC 9646-1 [3].
Implementation Conformance Statement (ICS) proforma: Refer to ISO/IEC 9646-1 [3].
Implementation eXtra Information for Testing (IXIT) proforma: Refer to ISO/IEC 9646-1 [3].
Point of Control and Observation (PCO): Refer to ISO/IEC 9646-1 [3].
Protocol Implementation Conformance Statement (PICS): Refer to ISO/IEC 9646-1 [3].
Protocol Implementation eXtra Information for Testing (PIXIT): Refer to ISO/IEC 9646-1 [3].
System Under Test (SUT): Refer to ISO/IEC 9646-1 [3].
Test Purpose (TP): Refer to ISO/IEC 9646-1 [3].
4 Abbreviations
For the purpose of the present document the following abbreviations apply:
ATS Abstract Test Suite
BS Base Station
BSC Base Station Controller
BSC Base Station Controller
BSS Base Station Sub-system
BSS Base Station System
GSM Global System for Mobile Communication
GW Gateway
HLR Home Location Register
IMSI International Mobile Subscriber Identity
IP Internet Protocol
MS Mobile Station
MS Mobile Subscriber
MSC Mobile Switching Center
MT Mobile Terminal
MT Mobile Terminated
NIT Network Integration Testing
PDP Packet Data Protocol
PIXIT Protocol Implementation eXtra Information for Testing
PLMN Public Land Mobile Network
PPP Point to Point Protocol
QoS Quality of Service
RADIUS Remote Authentication Dial In User Service
SCCP Signaling Connection and Control Part
SGSN Serving GPRS Support Node
SMS Short Message Service
SS Supplementary Service
TC Test Case
TCP/IP Transmission Control Protocol/Internet Protocol
TP Test Plant
ETSI
7 ETSI TS 102 111-1 V1.1.1 (2002-09)
TSS Test Suite Structure
TSS&TP Test Suite Structure and Test Purposes
UDP User Datagram Protocol
UMTS Universal Mobile Telecommunications System
UTRAN UMTS Terrestrial Radio Access Network
5 Numbering Scheme
• Pos. 1: Network of the A-Subscriber.
• Pos. 2: Network of the B-Subscriber.
• Pos. 3: Network of the C-Subscriber.
• Pos. 4: Network of the D-Subscriber.
• Pos. 5: Network of the E-Subscriber.
The following Network Codes apply:
_: No such network used (used e.g. for C-Subscriber in successful A to B Calls)
(underscore makes it easier to read the name)
G: GSM (w/HCSCD & GPRS)
U: UTRAN (UMTS)
N: IP Network
(Extensions will be added when needed)
• Pos. 6 and 7: Bearer- or Teleservice involved.
xx: defined per PIXIT value
Packet Services
GI: GPRS (IP)
NT: IP Network TCP
NU: IP Network UDP
• Pos. 8 and 9:
__: No Supplementary Services Involved/Successful
_U: No Supplementary Services Involved/Unsuccessful
• Pos. 10 to 25: YYYY Name of individual Test Group (if needed).
• Pos. Last two positions XX Number of individual Test Purpose.
Short description Name of individual Test Group
A_PDP_CR_GEN ACTIVATE PDP CONTEXT REQUEST General
A_PDP_CR_INTE ACTIVATE PDP CONTEXT REQUEST Interactive class
A_PDP_CR_BC_C ACTIVATE PDP CONTEXT REQUEST Background class
A_PDP_STR_C ACTIVATE PDP CONTEXT REQUEST Streaming class
A_PDP_CON_C
ACTIVATE PDP CONTEXT REQUEST Conversational class
ACTIVATE PDP CONTEXT REQUEST General for Rel.98
A_PDP_CR_GENxx_R98
A_SPDP_CR Activate Secondary PDP context Request
M_PDP_CR Modify PDP Context Request
D_PDP_CR Deactivate PDP Context Request

ETSI
8 ETSI TS 102 111-1 V1.1.1 (2002-09)
5.1 Examples
1 2 3 4 5 6 7 8 9 10 11 12 13 14 14 15 17 18 19 20 21 19 20
G N _ _ _ G I _ _ A _ P D P _ C R _ G E N X X

6 Test Suite Structure (TSS)
Packet
Services
GPRS 99 to Control Plane PDP context activation Successful GPRS GN__GI_A_PDP_C

ext. Network General R_GENxx
Control Plane +
Application
Successful GPRS GN__GI_A_PDP_C
Interactive class R_INTExx
Successful GPRS GN__GI_A_PDP_C
Background class R_BC_Cxx
Successful GPRS GN__GI_A_PDP_S
Streaming class TR_Cxx
Successful GPRS GN__GI_A_PDP_C
Conversational ON_Cxx
class
GPRS 98 to Control Plane PDP context activation Successful GPRS GN__GI_A_PDP_C

external PDP General R_GENxx_R98xx
network
GPRS Activate GN__GI_A_PDP_Ax
Basic GPRS scenario PDP context x
GPRS 99 General – Successful Accept

Activate GN__GI_A_SPDP_
Secondary PDP CRxx
context Request
Modify PDP GN___GI
Context Request M_PDP_CR xx
Deactivate PDP GN__GI_D_PDP_
Context Request CRxx
GPRS Activate GN__GI_U_A_PDP_
Basic GPRS scenario - PDP context Axx
Unsuccessful Accept
Activate GN__GI_U_A_SPDP
Secondary PDP
_CRxx
context Request
PDP Context GN__GI_UM_PD_PD
modification P
Xx
ANNEX A
GPRS 99 – Session GN__GI_SM_xx
Session Management
Management, Tests
Interface
Interoperability,
Performance
Interface GN__GI_II_xx
Interoperability
Performance GN__GI_PM_xx
Tests
ETSI
9 ETSI TS 102 111-1 V1.1.1 (2002-09)
7 Test configurations and test procedures
7.1 User Plane for UMTS
MS-GGSN
Application
E.g., IP, E.g., IP,
PPP, PPP,
OSP OSP
Relay Relay
PDCP PDCP GTP-U GTP-U GTP-U GTP-U
RLC RLC UDP/IP UDP/IP UDP/IP UDP/IP
MAC MAC AAL5 AAL5 L2 L2
L1 L1 ATM ATM L1 L1
Uu Iu-PS Gn Gi
MS UTRAN 3G-SGSN 3G-GGSN
Legend:
Packet Data Convergence Protocol (PDCP): This transmission functionality maps higher-level
characteristics onto the characteristics of the underlying radio-interface protocols. PDCP provides protocol
transparency for higher-layer protocols. PDCP supports e.g., IPv4, PPP, OSP, and IPv6. Introduction of
new higher-layer protocols shall be possible without any changes to the radio-interface protocols. PDCP
provides protocol control information compression. PDCP is specified in TS 125 323 [4].
NOTE: Unlike in GPRS, user data compression is not supported in UMTS, because the data compression
efficiency depends on the type of user data, and because many applications compress data before
transmission. It is difficult to check the type of data in the PDCP layer, and compressing all user data
requires too much processing.
GPRS Tunnelling Protocol for the user plane (GTP-U): This protocol tunnels user data between
UTRAN and the 3G-SGSN, and between the GSNs in the backbone network. All PDP PDUs shall be
encapsulated by GTP. GTP is specified in TS 129 060 [5].
UDP/IP: These are the backbone network protocols used for routeing user data and control signalling.
Asynchronous Transfer Mode (ATM): The information to be transmitted is divided into fixed-size cells
(53 octets), multiplexed, and transmitted. ATM is specified in ITU-T Recommendation I.361 [7]. [FFS: add
AAL5 description.]
Radio Link Control (RLC): The RLC protocol provides logical link control over the radio interface. There
may be several simultaneous RLC links per MS. Each link is identified by a Bearer Id. RLC is defined in
TS 125 322 [6].
Medium Access Control (MAC): The MAC protocol controls the access signalling (request and grant)
procedures for the radio channel. MAC is specified in TS 125 321 [8].

Figure 1: User Plane for UMTS
ETSI
10 ETSI TS 102 111-1 V1.1.1 (2002-09)

7.2 Control Plane
MS-SGSN for GPRS
GMM/SM GMM/SM
LLC LLC
Relay
RLC BSSGP
RLC BSSGP
MAC
MAC Network Network
Service Service
GSM RF GSM RF L1bis L1bis
Um Gb
MS BSS 2G-SGSN
Legend:
GPRS Mobility Management and Session Management (GMM/SM): This protocol supports mobility
management functionality such as GPRS attach, GPRS detach, security, routeing area update, location
update, PDP context activation, and PDP context deactivation, as described in clauses "Mobility
Management Functionality" and "PDP Context Activation, Modification, and Deactivation Functions".

Figure 2: Control Plane MS-2G-SGSN
MS-SGSN for UMTS
GMM / GMM /
SM / SMS SM / SMS
Relay
RRC RRC RANAP RANAP
RLC RLC SSCCP CCP
Signalling Signalling
MAC MAC
Bearer Bearer
AAL5 AAL5
L1 L1
ATM ATM
Uu Iu-Ps
MS RNS 3G SGSN
Legend:
UMTS Mobility Management and Session Management (GMM/SM): GMM supports mobility
management functionality such as attach, detach, security, and routeing area update, as described in
clause "Mobility Management Functionality". SM supports PDP context activation and PDP context
deactivation, as described in clause "PDP Context Activation, Modification, and Deactivation Functions".
SMS supports the mobile-originated and mobile-terminated short message service described in TS 123
040 [9].
Radio Access Network Application Protocol (RANAP): This protocol encapsulates and carries higher-
layer signalling, handles signalling between the 3G-SGSN and UTRAN, and manages the GTP
connections on the Iu interface. RANAP is specified in TS 125 413[10]. The layers below RANAP are
defined in TS 123 121 [11].
Radio Link Control (RLC): The RLC protocol offers logical link control over the radio interface for the
transmission of higher layer-signalling messages and SMS. RLC is defined in 3G TS 25.322.

Figure 2a: Control Plane MS-3G-SGSN
ETSI
11 ETSI TS 102 111-1 V1.1.1 (2002-09)
7.3 PDP Context Activation Procedure
MS BSS 2G-SGSN 2G-GGSN
1. Activate PDP Context Request
C1
2. Security Functions
4. Invoke Trace
5. Create PDP Context Request
5. Create PDP Context Response
6. BSS Packet Flow Context Procedures
C2
7. Activate PDP Context Accept

Figure 3: PDP Context Activation Procedure for GPRS
MS UTRAN 3G-SGSN 3G-GGSN
1. Activate PDP Context Request
C1
3. Radio Access Bearer Setup
4. Invoke Trace
5. Create PDP Context Request
5. Create PDP Context Response
C2
7. Activate PDP Context Accept

Figure 4: PDP Context Activation Procedure for UMTS
ETSI
12 ETSI TS 102 111-1 V1.1.1 (2002-09)
7.3.1 Successful Network-Requested PDP Context Activation Procedure
MS SGSN HLR GGSN
1. PDP PDU
2. Send Routeing Info for GPRS
2. Send Routeing Info for GPRS Ack
3. PDU Notification Request
3. PDU Notification Response
4. Request PDP Context Activation
5. PDP Context Activation procedure

Figure 5: Successful Network-Requested PDP Context Activation Procedure
ETSI
13 ETSI TS 102 111-1 V1.1.1 (2002-09)
8.1 PDP context activation
8.1.1 GPRS R99 to external PDP network
8.1.1.1 Successful
GSM ref. to:
GN___GI
A_PDP_CR_GEN 01 TS 124 008 [1] clauses 6.1.1 and
6.1.3.1.1
TSS reference: GPRS R99 to external PDP network/PDP context activation/successful/ACTIVATE
PDP CONTEXT REQUEST
GSM selection BS 70
criteria:
IP selection criteria: None
Test purpose: If the UE is attached, then the Detach Request is originated from the UE indicating
"GPRS detach without switching off". The network responds with a Detach Accept after
completing the security mode procedures. A PDP context activation is then requested by
the user. The PS attach (ATTACH REQUEST) is then indirectly caused by a requested
PDP context activation. The SS returns the ATTACH ACCEPT message to the UE. Now
session management can proceed with PDP context activation.
On receipt of the ACTIVATE PDP CONTEXT REQUEST message an ACTIVATE PDP
CONTEXT ACCEPT is returned by the SS with the same requested QoS.
The GGSN may further restrict QoS Negotiated given its capabilities and the current
load. If the QoS offered by the network is acceptable to the mobile, then upon receipt of
the ACTIVATE PDP CONTEXT ACCEPT message the MS shall initiate establishment of
the logical link with the offered QoS.
An external IP application is started defined with PIXIT values.
Ensure that the PDP PDU transfer with the offered parameters is performed correctly.
Verify if the requested QoS parameters in the ACTIVATE PDP CONTEXT ACCEPT
message are kept on the routed PDP PDUs.
GSM parameter
QoS Requested:
values: PDP type organization: PCO_ID
PDP type number value: PDP_TNV_ID (PIXIT)
Reliability class: RC_IDreq (PIXIT)
Delay class: DC_IDreq (PIXIT)
Precedence class: PC_IDreq (PIXIT)
Peak throughput: PT_IDreq (PIXIT)
Mean throughput: MT_IDreq (PIXIT)
Delivery of erroneous SDU: DoeSDU_IDreq (PIXIT)
Delivery order: DO_IDreq (PIXIT)
Traffic class: TC_IDreq (PIXIT)
Maximum SDU size: M_SDU_S_IDreq(PIXIT)
Maximum bit rate for uplink: MBRFU_IDreq (PIXIT)
Maximum bit rate for downlink: MBRFD_IDreq (PIXIT)
Residual Bit Error Rate: RBER_IDreq (PIXIT)
SDU error ratio: SDU_ER_IDreq (PIXIT)
Traffic handling priority: THP_IDreq (PIXIT)
Transfer delay: TD_IDreq (PIXIT)
Guaranteed bit rate for uplink: GBRU_ IDreq (PIXIT)
Guaranteed bit rate for downlink: BRD_IDreq (PIXIT)
IP application Application name: IP_APLIC (PIXIT)
parameter values:
Application parameters values : IP_PAR 1 to .IP_PAR 3 (PIXIT)
ETSI
14 ETSI TS 102 111-1 V1.1.1 (2002-09)
Comments: PDP context activation shall initiate PS Attach by the UE to establish a GMM context,
when the UE is PS Detached.
In order to request a PDP context activation, the UE sends an ACTIVATE PDP
CONTEXT REQUEST message to the network, enters the state PDP-ACTIVE-
PENDING and starts timer T3380. The message contains the selected NSAPI, PDP
type, requested QoS and, if the UE requests a static address, the PDP address.
If the QoS offered by the network is the same as the QoS requested by the UE, then
upon receipt of the message ACTIVATE PDP CONTEXT ACCEPT the UE shall stop
timer T3380.
In GSM, the MS shall initiate establishment of the logical link for the LLC SAPI indicated
by the network with the offered QoS and selected radio priority level if no logical link has
been already established for that SAPI.
In UMTS, both the network and the MS shall store the LLC SAPI and the radio priority in
the PDP context.
A UE, which is capable of operating in both GSM and UMTS, shall use a valid LLC SAPI,
while a UE which is capable of operating only in UMTS shall indicate the LLC SAPI value
as "LLC SAPI not assigned" in order to avoid unnecessary value range checking and
any other possible confusion in the network.

Expected sequence
Step Direction Message Comments
UE SS
1  DETACH REQUEST Only sent if the UE attaches at power-up, if
not go to step 3.
Detach is performed by the UE using MMI
or AT Commands
2 DETACH ACCEPT SS sends Detach Accept message.
3 UE Initiate a context activation

4 ATTACH REQUEST Request attach

5 ATTACH ACCEPT Accept attach
6 ACTIVATE PDP CONTEXT Request a PDP context activation
REQUEST
7 ACTIVATE PDP CONTEXT Accept the PDP context activation
ACCEPT
Values for PDP type organization:
VA_01 PCO_ID: PPP for use with IP PDP type
VA_02 PCO_ID: OSP:IHOSS PDP type
Values for PDP type number value:
VA_01 PDP_TO_ID: IETF allocated address
PDP_TNV_ID : IPv4 address
VA_02 PDP_TO_ID: IETF allocated address
PDP_TNV_ID: IPv6 address
Values for Reliability class
VA_01 RC_IDreq: Acknowledged GTP, LLC, and RLC;
Protected data
VA_02 RC_IDreq: Unacknowledged GTP; Acknowledged LLC
and RLC, Protected data
VA_03 RC_IDreq: Unacknowledged GTP and LLC;
Acknowledged RLC, Protected data
VA_04 RC_IDreq: Unacknowledged GTP, LLC, and RLC,
Protected data
VA_05 RC_IDreq: Unacknowledged GTP, LLC, and RLC,
Unprotected data
Values for QoS – Delay class
VA_01 DC_IDreq: Delay class 1
VA_02 DC_IDreq: Delay class 2
VA_03 DC_IDreq: Delay class 3
VA_04 DC_IDreq: Delay class 4
Values for QoS – Precedence class
VA_01 PC_IDreq: High priority
VA_02 PC_IDreq: Normal priority
VA_03 PC_IDreq: Low priority
ETSI
15 ETSI TS 102 111-1 V1.1.1 (2002-09)
Values for QoS – Peak Throughput
VA_01 PT_IDreq: Up to 1 000 octet/s
VA_02 PT_IDreq: Up to 2 000 octet/s
VA_03 PT_IDreq: Up to 4 000 octet/s
VA_04 PT_IDreq: Up to 8 000 octet/s
VA_05 PT_IDreq: Up to 16 000 octet/s
VA_06 PT_IDreq: Up to 32 000 octet/s
VA_07 PT_IDreq: Up to 64 000 octet/s
VA_08 PT_IDreq: Up to 128 000 octet/s
VA_09 PT_IDreq: Up to 256 000 octet/s
Values for QoS – Mean throughput
VA_01 MT_IDreq: 100 octet/h
VA_02 MT_IDreq: 200 octet/h
VA_03 MT_IDreq: 500 octet/h
VA_04 MT_IDreq: 1000 octet/h
VA_05 MT_IDreq: 2000 octet/h
VA_06 MT_IDreq: 5000 octet/h
VA_07 MT_IDreq: 10 000 octet/h
VA_08 MT_IDreq: 20 000 octet/h
VA_09 MT_IDreq: 50 000 octet/h
VA_10 MT_IDreq: 100 000 octet/h
VA_11 MT_IDreq: 200 000 octet/h
VA_12 MT_IDreq: 500 000 octet/h
VA_13 MT_IDreq: 1 000 000 octet/h
VA_14 MT_IDreq: 2 000 000 octet/h
VA_15 MT_IDreq: 5 000 000 octet/h
VA_16 MT_IDreq: 10 000 000 octet/h
VA_17 MT_IDreq: 20 000 000 octet/h
VA_18 MT_IDreq: 50 000 000 octet/h
Values for QoS – Delivery of erroneous SDU
VA_01 DoeSDU_IDreq: Erroneous SDU are delivered ("yes")
VA_02 DoeSDU_IDreq: Erroneous SDU are not delivered ("no")
Values for QoS – Delivery order
VA_01 DO_IDreq: With delivery order ("yes")
VA_02 DO_IDreq: Without SDU are not delivered ("no")
Values for QoS – Traffic class
VA_01 TC_IDreq: Streaming class
VA_02 TC_IDreq: Interactive class
VA_03 TC_IDreq: Background class
Values for QoS – Maximum SDU size
VA_01 M_SDU_S_IDreq:10 octets
VA_02 M_SDU_S_IDreq:20 octets
VA_03 M_SDU_S_IDreq:40 octets
VA_04 M_SDU_S_IDreq:80 octets
VA_05 M_SDU_S_IDreq:160 octets
VA_06 M_SDU_S_IDreq:320 octets
VA_07 M_SDU_S_IDreq:640 octets
VA_08 M_SDU_S_IDreq:1280 octets
VA_09 M_SDU_S_IDreq:1 500 octets
VA_10 M_SDU_S_IDreq:1502 octets
VA_11 M_SDU_S_IDreq:1510 octets
VA_12 M_SDU_S_IDreq:1520 octets
Values for QoS – Maximum bit rate for uplink
VA_01 MBRFU_IDreq: Subscribed the maximum bit rate for
uplink
VA_02 MBRFU_IDreq: 1 kbps
VA_03 MBRFU_IDreq: 2 kbps
VA_04 MBRFU_IDreq: 8 kbps
VA_05 MBRFU_IDreq: 16 kbps
VA_06 MBRFU_IDreq: 32 kbps
VA_07 MBRFU_IDreq: 63 kbps
VA_08 MBRFU_IDreq: 64kbps
VA_09 MBRFU_IDreq: 564 kbps
VA_10 MBRFU_IDreq: 576 kbps
VA_11 MBRFU_IDreq: 8640kbps
ETSI
16 ETSI TS 102 111-1 V1.1.1 (2002-09)
Values for Maximum bit rate for downlink
VA_01 MBRFD_IDreq: Subscribed the maximum bit rate for
downlink
VA_02 MBRFD_IDreq: 1 kbps
VA_03 MBRFD_IDreq: 2 kbps
VA_04 MBRFD_IDreq: 8 kbps
VA_05 MBRFD_IDreq: 16 kbps
VA_06 MBRFD_IDreq: 32 kbps
VA_07 MBRFD_IDreq: 63 kbps
VA_08 MBRFD_IDreq: 64kbps
VA_09 MBRFD_IDreq: 564 kbps
VA_10 MBRFD_IDreq: 576 kbps
VA_11 MBRFD_IDreq: 8640kbps
Values for Residual Bit Error Rate
-2
VA_01
RBER_IDreq: 5 * 10
-2
VA_02
RBER_IDreq: 1 * 10
-3
VA_03
RBER_IDreq: 5 * 10
-3
VA_04
RBER_IDreq: 4 * 10
-3
VA_05
RBER_IDreq: 1 * 10
-4
VA_06
RBER_IDreq: 1 * 10
-5
VA_07
RBER_IDreq: 1 * 10
-6
VA_08
RBER_IDreq: 1 * 10
-8
VA_09
RBER_IDreq: 6 * 10
Values for QoS – SDU error ratio
-2
VA_01
SDU_ER_IDreq: 1 * 10
-3
VA_02
SDU_ER_IDreq: 7 * 10
-3
VA_03
SDU_ER_IDreq: 1 * 10
-4
VA_04
SDU_ER_IDreq: 1 * 10
-5
VA_05
SDU_ER_IDreq: 1 * 10
-6
VA_06
SDU_ER_IDreq: 1 * 10
Values for QoS – Traffic handling priority
VA_01 THP_IDreq: Priority level 1
VA_02 THP_IDreq: Priority level 2
VA_03 THP_IDreq: Priority level 3
Values for Transfer delay
VA_01 TD_IDreq: 10 ms
VA_02 TD_IDreq: 20 ms
VA_03 TD_IDreq: 30 ms
VA_04 TD_IDreq: 40 ms
VA_05 TD_IDreq: 50 ms
VA_06 TD_IDreq: 60 ms
VA_07 TD_IDreq: 70 ms
VA_08 TD_IDreq: 80 ms
VA_09 TD_IDreq: 90 ms
VA_10 TD_IDreq: 100 ms
VA_11 TD_IDreq: 120 ms
VA_12 TD_IDreq: 150 ms
VA_13 TD_IDreq: 200 ms
VA_14 TD_IDreq: 300 ms
VA_15 TD_IDreq: 400 ms
VA_16 TD_IDreq: 500 ms
VA_17 TD_IDreq: 600 ms
VA_18 TD_IDreq: 700 ms
VA_19 TD_IDreq: 800 ms
VA_20 TD_IDreq: 900 ms
VA_21 TD_IDreq: 950 ms
VA_22 TD_IDreq: 1000 ms
VA_23 TD_IDreq: 2000 ms
VA_24 TD_IDreq: 3000 ms
VA_25 TD_IDreq: 4100 ms
ETSI
17 ETSI TS 102 111-1 V1.1.1 (2002-09)
Guaranteed bit rate for uplink
VA_02 GBRU_ IDreq: 1 kbps
VA_03 GBRU_ IDreq: 2 kbps
VA_04 GBRU_ IDreq: 8 kbps
VA_05 GBRU_ IDreq: 16 kbps
VA_06 GBRU_ IDreq: 32 kbps
VA_07 GBRU_ IDreq: 63 kbps
VA_08 GBRU_ IDreq: 64kbps
VA_09 GBRU_ IDreq: 564 kbps
VA_10 GBRU_ IDreq: 576 kbps
VA_11 GBRU_ IDreq: 8 640kbps
Guaranteed bit rate for downlink
VA_02 GBRD_ IDreq: 1 kbps
VA_03 GBRD_ IDreq: 2 kbps
VA_04 GBRD_ IDreq: 8 kbps
VA_05 GBRD_ IDreq: 16 kbps
VA_06 GBRD_ IDreq: 32 kbps
VA_07 GBRD_ IDreq: 63 kbps
VA_08 GBRD_ IDreq: 64kbps
VA_09 GBRD_ IDreq: 564 kbps
VA_10 GBRD_ IDreq: 576 kbps
VA_11 GBRD_ IDreq: 8 640kbps
ETSI
18 ETSI TS 102 111-1 V1.1.1 (2002-09)
8.1.1.1.1 Application models
Interactive class; Applications: HTTP, FTP
GN___GI GSM ref. to:
A_PDP_CR_ TS 124 008 [1] clauses 6.1.1 and
INTE_ 01 6.1.3.1.1
TSS reference: GPRS R99 to external PDP network/PDP context activation/successful/ACTIVATE
PDP CONTEXT REQUEST
GSM selection BS 70
criteria:
IP selection criteria:
None
Test purpose: Ensure that the Requested PDP Context Activation procedure allows the GGSN to route
PDP PDUs between the SGSN and the external PDP network, and to start charging. The
GGSN may further restrict QoS Negotiated given its capabilities and the current load. If
the QoS offered by the network is acceptable to the mobile, then upon receipt of the
ACTIVATE PDP CONTEXT ACCEPT message the MS shall initiate establishment of the
logical link with the offered QoS
Ensure that the network can support the "Packet data protocol address"
parameters requested by the MS with the ACTIVATE PDP CONTEXT REQUEST
message.
Ensure that the PDP PDU transfer with the offered parameters is performed correctly.
Verify if the requested QoS parameters in the ACTIVATE PDP CONTEXT ACCEPT
message are kept on the routed PDP PDUs.
GSM parameter
QoS Requested:
values: PDP type organization: IETF allocated address
PDP type number value: PDP_TNV_ ID
Reliability class: 5 (Unacknowledged GTP, LLC, and RLC, Unprotected data)
Delay class: Delay class 2
Precedence class: Low priority
Peak throughput: Up to 16 000 octet/s (128 kbit/s)
Mean throughput: 50 000 000 octet/h (111,1 kbit/s)
Delivery of erroneous SDU: Erroneous SDU are not delivered ("no")
Delivery order: With delivery order ("yes")
Traffic class: Interactive class
Maximum SDU size: 1 500 octets
Maximum bit rate for uplink: 64 kbps
Maximum bit rate for downlink: 64 kbps
-3
Residual Bit Error Rate: 4 * 10
-3
SDU error ratio: 10
Traffic handling priority: Priority level 2
Transfer delay: *
Guaranteed bit rate for uplink: *
Guaranteed bit rate for downlink: *
IP parameter values:
IP Address: GPRS_A_IP_ADD (PIXIT); GPRS_B_IP_ADD (PIXIT)
Comments: If the UE is attached, then the Detach Request is originated from the UE indicating
"GPRS detach without switching off". The network responds with a Detach Accept after
completing the security mode procedures. A PDP context activation is then requested by
the user. The PS attach (ATTACH REQUEST) is then indirectly caused by a requested
PDP context activation. The SS returns the ATTACH ACCEPT message to the UE. Now
session management can proceed with PDP context activation.
On receipt of the ACTIVATE PDP CONTEXT REQUEST message an ACTIVATE PDP
CONTEXT ACCEPT is returned by the SS with the same requested QoS.

Values for test purpose GN___GI 01
VA_01 PDP_TO_ID: IETF allocated address
PDP_TNV_ID: IPv4 address
VA_02 PDP_TO_ID: IETF allocated address
PDP_TNV_ID: IPv6 address
ETSI
19 ETSI TS 102 111-1 V1.1.1 (2002-09)
GN___GI GSM ref. to:
A_PDP_CR_ INTE 02 TS 124 008 [1] clauses 6.1.1 and
6.1.3.1.1
TS 123 107 [12], clause 9.1.2.2
TSS reference: GPRS R99 to external PDP network/PDP context activation/successful/ACTIVATE
PDP CONTEXT REQUEST
GSM selection BS 70
criteria:
IP selection criteria:
Test purpose: Ensure that the Requested PDP Context Activation procedure allows the GGSN to route
PDP PDUs between the SGSN and the external PDP network, and to start charging. The
GGSN may further restrict QoS Negotiated given its capabilities and the current load. If
the QoS offered by the network is acceptable to the mobile, then upon receipt of the
ACTIVATE PDP CONTEXT ACCEPT message the MS shall initiate establishment of the
logical link with the offered QoS.
Ensure that the network can support the "QoS – "Maximum SDU size" parameter coded
as M_SDU_S_IDreq. The bit rate for uplink and downlink and Peak Throughput are
defined with the parameters MBRFU_IDreq, MBRFD_IDreq and PT_IDreq. The user
data rate on the bearer is equal with the Maximum bit rate for uplink and Maximum Bit
Rate for downlink. The user data SDU size on the bearer is defined as M_SDU_S_P.
Ensure that the PDP PDU transfer with the offered parameters is performed correctly.
Verify if the requested QoS parameters in the ACTIVATE PDP CONTEXT ACCEPT
message are kept on the routed PDP PDUs.
GSM parameter OoS Requested:
values: PDP type organization: IETF allocated address
PDP type number value: PIXIT
Reliability class: 5 (Unacknowledged GTP, LLC, and RLC, Unprotected data)
Delay class: Delay class 2
Precedence class: Low priority
Peak throughput: PT_IDreq
Mean throughput: 50 000 000 octet/h (111,1 kbit/s)
Delivery of erroneous SDU: Erroneous SDU are not delivered ("no")
Delivery order: With delivery order ("yes")
Traffic class: Interactive class
Maximum SDU size: M_SDU_S_IDreq
Maximum bit rate for uplink: MBRFU_IDreq
Maximum bit rate for downlink: MBRFD_IDreq
-3
Residual Bit Error Rate: 4 * 10
-3
SDU error ratio: 10
Traffic handling priority: Priority level 2
Transfer delay: * (value is ignored)
Guaranteed bit rate for uplink: * (value is ignored)
Guaranteed bit rate for downlink: * (value is ignored)
IP parameter values: IP Address: GPRS_A_IP_ADD (PIXIT); GPRS_B_IP_ADD (PIXIT)
Comments: If the UE is attached, then the Detach Request is originated from the UE indicating
"GPRS detach without switching off". The network responds with a Detach Accept after
completing the security mode procedures. A PDP context activation is then requested by
the user. The PS attach (ATTACH REQUEST) is then indirectly caused by a requested
PDP context activation. The SS returns the ATTACH ACCEPT message to the UE. Now
session management can proceed with PDP context activation.
On receipt of the ACTIVATE PDP CONTEXT REQUEST message an ACTIVATE PDP
CONTEXT ACCEPT is returned by the SS with the same requested QoS.

Values for QoS – maximum SDU size
VA_01 PT_IDreq: 8 000 octets (64 kbps)
MBRFU_IDreq: 32 kbps
MBRFD_IDreq: 32 kbps
M_SDU_S_IDreq: 1 500 octets
M_SDU_S_P: 1 500 octets
VA_02 PT_IDreq: 8 000 octet/s (64 kbps)
MBRFU_IDreq: 32 kbps
MBRFD_IDreq: 32 kbps
M_SDU_S_IDreq:1 502 octets
M_SDU_S_P: 1 502 octets
ETSI
20 ETSI TS 102 111-1 V1.1.1 (2002-09)
Values for QoS – maximum SDU size
VA_03 PT_IDreq: 8 000 octet/s (64 kbps)
MBRFU_IDreq: 32 kbps
MBRFD_IDreq: 32 kbps
M_SDU_S_IDreq:1 520 octets
M_SDU_S_P: 1 520 octets
GN___GI GSM ref. to:
A_PDP_CR_ INTE 03 TS 124 008 [1] clauses 6.1.1 and
6.1.3.1.1
TS 123 107 [12], clause 9.1.2.2
TSS reference: GPRS R99 to external PDP network/PDP context activation/successful/ACTIVATE
PDP CONTEXT REQUEST
GSM selection BS 70
criteria:
IP selection criteria:
Test purpose: Ensure that the Requested PDP Context Activation procedure allows the GGSN to route
PDP PDUs between the SGSN and the external PDP network, and to start charging. The
GGSN may further restrict QoS Negotiated given its capabilities and the current load. If
the QoS offered by the network is acceptable to the mobile, then upon receipt of the
ACTIVATE PDP CONTEXT ACCEPT message the MS shall initiate establishment of the
logical link with the offered QoS
Ensure that the network can support the "Maximum Bit Rate for uplink and Maximum
Bit Rate for downlink" parameter coded as MBRFU_IDreq and MBRFD_IDreq. The
user data rate on the bearer is equal with the Maximum Bit Rate for uplink and Maximum
Bit Rate for downlink. The user data SDU size on the bearer is defined as M_SDU_S_P.
Ensure that the PDP PDU transfer with the offered parameters is performed correctly.
Verify if the requested QoS parameters in the ACTIVATE PDP CONTEXT ACCEPT
message are kept on the routed PDP PDUs.
GSM parameter QoS Requested:
values: PDP type organization: IETF allocated address
PDP type number value: IPv4 address
Reliability class: 5 (Unacknowledged GTP, LLC, and RLC, Unprotected data)
Delay class: Delay class 2
Precedence class: Low priority
Peak throughput: PT_IDreq
Mean throughput: 50 000 000 octet/h (111,1 kbit/s)
Delivery of erroneous SDU: Erroneous SDU are not delivered ("no")
Delivery order: With delivery order ("yes")
Traffic class: Interactive class
Maximum SDU size: 1 500 octets
Maximum bit rate for uplink: MBRFU_IDreq
Maximum bit rate for downlink: MBRFD_IDreq
-3
Residual Bit Error Rate: 4 * 10
-3
SDU error ratio: 10
Traffic handling priority: Priority level 2
Transfer delay: * (value is ignored)
Guaranteed bit rate for uplink: * (value is ignored)
Guaranteed bit rate for downlink: * (value is ignored)
IP parameter values: IP Address: GPRS_A_IP_ADD (PIXIT);
...