End to End Functional Capability Test Specification for Inter-PLMN GPRS and LTERoaming Official Document IR.3

Transcription

1 Title End to End Functional Capability Test Specification for Inter-PLMN GPRS and LTERoaming Official Document IR.3 Version 5,0 Date: 26-May-11 Antitrust Notice The information contain herein is in full compliance with the GSM Association s antitrust compliance policy. Document History Version Brief Description Date IREG Doc GPRS 23/99 with changes according 4 th Meeting of IREG GPRS for Ad-Hoc prediscussion 6/22/ First draft of document for IREG GPRS group discussion (5th Meeting) 8/6/ Second draft of document for IREG GPRS group discussion (6th Meeting) 11/29/ IREG Doc GPRS 23/99 with changes according 6 th Meeting of IREG GPRS 12/14/ Modifications from comments send by Introduction of Operator Control of Service test cases IREG Doc IR35 with changes according 7th Meeting of IREG GPRSCharging-Information/Operator Control of Service Test 2/1/2000 3/3/ A new test case added in Chapter /24/ Charging information added, ODB test cases modified. 3/1/ Charging impacts, chapter 2.2 item no. 6 updated. Final modifications before IREG#38 3/3/ Modified for IREG 38 approval 3/14/ Approved by IREG 38 subject to addition of Appendix A and B 3/15/ Appendix A and B completed 3/29/ Approved at Plenary 43. PL Doc 36/00 Rev 1 4/28/ IREG Doc GPRS 35/00 with changes according 9 th Meeting of IREG GPRS 6/23/ Changes/Clarification towards the meaning of the APN-Network-Identifier: APN-Network-ID defines to which external network the GGSN is connected to 8/30/ IREG Doc GPRS 57/00 (CR) with changes according to 11th Meeting of IREG GPRS 9/5/ Approved and revised document after IREG#39 for discussion on 1th Packet-WP-Meeting 11/23/ Modifications from comments according 1th IREG Packet-WP-GPRS (GSM NA IREG WG Suggested changes to IR35) 1/5/ Separation of optional test cases in a separate Annex 3/1/ Modifications from comments according 3rd IREG- Packet-Meeting (Creation of S-CDRs) 8/21/ Modified document for presentation on the IREG-#41-Meeting Approved and revised document after IREG#41 10/17/ Modifications from comments /experiences made by Vodafone-D2:Restructuring of test results; table-format; Removal of test-cases; chapter B1.2.7 and B1.2.8; (See also CR-003) Changes according 8th Meeting of IREG Packet 3/18/ Approved and revised document after IREG#42 3/20/2002

2 3.3.0 CR-004_Hutchison-3G, IREG-Doc 068_02 Approved and revised document after IREG# CR NTT-DoCoMo, IREG-Doc 092/02, Additional requirement of operator control of service. CR NTT-DoCoMo, IREG-Doc 093/02, The prohibition 8/20/2002 2/11/ Reorganization of document according IREG-IR35-Ad-Hoc-Meeting, Düsseldorf 10/1/ Changed IR35 from Word to EXCEL within GSMA Open Connectivity project 9/2/ LTE Roaming added to IR35 1/27/ Add the provision of roaming scenarios where LTE and 2G/3G co-exist. 5/26/ INTRODUCTION 1.1 Scope of Document This document is the specification of IREG End-to-end Functional Capability tests relating to the international roaming of a Mobile Station subscribed to packet switched data services, belonging to a home PLMN (a), to and within a visited PLMN (b). Throughout this document, GPRS refers to GPRS Release 97/98 (i.e. 2.5G). Throughout this document, LTE/EPC, and LTE+2G/3G Co-existence refers to Release8. The tests specified here do not replace the End-to-end Functional Capability tests for Inter-PLMN Roaming [see Stage 4: IREG PRD IR24], because not every roamer will be subscribed to a packet switched data service. This document represents rather an extension to the IR24 tests. The tests should be done after successful Stage 4 testing. Whilst it is expected that packet switched data-roaming will be a bilateral activity between two PLMNs, please note that this document is written in a unidirectional context. Hence Roaming is taking place by a MS1(a) to VPLMN(b) only. There is no reference to a Mobile Station MS1(b) visiting PLMN(a). To complete IREG End-to-end Functional Capability tests for bilateral roaming, it is necessary to perform the tests in this document twice: the second time the real identities of PLMN (a) and PLMN (b) are swapped. IREG Document PRD IR23 defines the scope and purpose of each stage of testing. This document does not cover: SCCP testing. [See Stage 2: IREG PRD IR25] SCTP/UDP/IP testing. Exchange of PLMN numbering, addressing and routeing data. [See Stage 3: IREG PRD IR23] Testing of Transferred Account Procedure, billing applications and any inter-plmn financial -statement; [see TADIG PRD TD06]. However the production of a Toll Ticketing file, for use in the TADIG Stage 3 testing is included. Definition of operation and maintenance procedures such as contact points for fault reporting and notification of planned works. [See Stage 3: IREG PRD IR23] IR24 International Roaming testing. [See Stage 4: IREG PRD IR24] IREG Document PRD IR88 defines the LTE roaming and LTE+2G/3G co-existence guidelines. 1.2 Abbreviations Term Definition 2.5G GPRS Release 97/98 2.5G SGSN Release 97/98 SGSN APN Access Point Name BSSAP+ Base Station System Application Part + BSS Base Station Subsystem DNS EPC EPS FTP Domain Name System Evolved Packet Core Evolved Packet System File Transfer Protocol

3 G-CDR Gateway GPRS Support Node Call Detail Record GGSN Gateway GPRS Support Node GMSC Gateway Mobile Services Switching Centre HLR Home Location Register HSS Home Subscriber Server HPLMN Home PLMN HTTP Hypertext Transport Protocol IP Internet Protocol ISP Internet Service Provider LTE Long Term Evolution M-CDR Mobility Management - Call Detail Record MM Mobility Management MME Mobility Management Entity MMSC Multimedia Messaging Service Centre MS Mobile Station MSx(b) indicates that the MS subscription is MSC Mobile Services PLMN(b) Switching Centre PCRF Policy and Charging Rules Function PDP Packet Data Protocol, e.g., IP or X.25 PLMN Public Land Mobile Network PLMN(a) P-GW PDN GateW ay RAI Routing Area Identity SAE System Architecture Evolution SCTP Stream Control Transmission Protocol S-CDR Serving GPRS Support Node Call Detail Record SGSN Serving GPRS Support Node S-GW Serving GateW ay SMS Short Message Service SMS-SC Short Message Service Centre UDP User Datagram Protocol VMSC VLR W AP 1.3 Objective of Tests Visited Mobile Services Switching Centre Visitor Location Register GW W AP Gateway The fundamental objective of this testing is to confirm the capability of packet switched data services which users will receive when roaming from their Home PLMN(a) to PLMN(b). Consequently the tests are restricted to top-level capability testing. There is no provocative or inopportune behaviour testing. Not all possible services should be tested. In addition to the handling of the tests itself the collection/comparison of charging information respective the generation of charging detailed records (CDR) is described. The overall objective of the tests is to confirm that functionality and features of data services, which are already known to operate correctly within each separate PLMN, will also operate correctly for Inter-PLMN roaming. The tests described here do not replace the international roaming tests described in IR24. They represent a completion of IR24 tests regarding packet switched data features. The test cases in Chapter 2 and Chapter 19 are first of all mandatory. However they can/should only be done if the technical prerequisites are given for both involved networks under test. 1.4 Strategy for Testing

4 In order to maximize the efficiency of testing, the test cases have been drawn up so as to minimize the requirement for simultaneous joint activity by both PLMN (a) and PLMN (b). This concerns mainly the administration of mobile subscriber data in the HLR/HSS. Accordingly, the program of testing forms three distinct components. HPLMN(a) issues pre-programmed SIMs (see chapter 4.3) and programmes HLR/HSS PLMN(b) performs tests PLMN(b) and HPLMN(a) discuss results 1.5 Prerequisites Prerequisites for GPRS only testing: Towards a first introduction of GPRS following prerequisites are assumed: GPRS mobile stations supporting the network operation modes in VPLMN(b).(Note: Class-C-Mobiles can be used for testing however IMSI-/GSM-procedures are not in scope but covered in IREG- IR24) The HLR contains GPRS subscription data and routing information (PDP type (S), PDP address (S), APN (S), and VPLMN address allowed). These subscription data are permanent data in the HLR and have to be inserted for the tests. The HLR is accessible from the SGSN via the Gr interface. For roaming MSs, the HLR is in a different PLMN than the current SGSN. The SGSN is updated with new GPRS subscription data with the Insert Subscriber Data procedure. IMSI is the primary key to the GPRS subscription data stored in the HLR. There may be several sets of GPRS subscription data per IMSI. HLR GPRS Subscription Data: Field IMSI MSISDN SGSN Number SGSN Address SMS Parameters MS Purged for GPRS MNRG GGSN-list Description IMSI is the main reference key. The basic MSISDN of the MS. The SS7 number of the SGSN currently serving this MS. The IP address of the SGSN currently serving this MS. SMS-related parameters, e.g., operator-determined barring. Indicates that the MM and PDP contexts of the MS are deleted from the SGSN. Indicates that the MS is not reachable through an SGSN, and that the MS is marked as not reachable for GPRS at the SGSN and possibly at the GGSN. The GSN number and optional IP address pair related to the GGSN that shall be contacted when activity from the MS is detected and MNRG is set. The GSN number shall be either the number of the GGSN or the protocol-converting GSN as described in the subclause "MAP-based GGSN HLR Signalling" and "GTP and MAP-based GGSN HLR Signalling". Each IMSI contains zero or more of the following PDP context subscription records: PDP Context Identifier Index of the PDP context. PDP Type PDP Address QoS Profile Subscribed VPLMN Address Allowed Access Point Name PDP type, e.g., PPP or IP. PDP address, IP or X.121 address. This field shall be empty if dynamic addressing is allowed. The quality of service profile subscribed. QoS Profile Subscribed is the default level if a particular QoS profile is not requested. Specifies whether the MS is allowed to use the APN in the domain of the HPLMN only, or additionally the APN in the domain of the VPLMN. A label according to DNS naming conventions describing the access point to the external packet data network. In case of W ild Card APN this field shall be filled with *

5 3. Towards GPRS no supplementary services are invoked. 4. The Gi-Interface is implemented in HPLMN(a) and VPLMN(b) 5. The Gp-Interface is implemented (Inter-PLMN connection) 6. SGSN/GGSN-access to DNS-Functionality 7. Configuration of the test environment for transparent or non-transparent access to Intranet/ISP (The key point for the access of an Intranet or an ISP infrastructure is the APN-Network-Identifier. This can be sent by mobile during PDP-context activation or can be set by default by the SGSN. The APN-Network Identifier defines to which external network the GGSN is connected. This means in detail the interface of the GGSN to an external network. This external interface at the GGSN is connected to the infrastructure providing Intranet functionality (e.g. local HTTP-Server) or to a kind of Serverfarm providing ISP functionality (HTTP-Server, Proxy- Server or FTP-Server with connection to the external Internet). This mechanism will provide the physical path to the Intranet/ISPfunctionality. However each operator has to make sure that the APN-resolution algorithms are implemented correctly in his SGSN according GSM and Annex A of TS Dynamic Address allocation for access to Intranet/ISP Prerequisites for LTE only testing: Towards a first introduction of LTE/EPC following prerequisites are assumed: 1. LTE mobile stations supporting the network operation modes in VPLMN(b). 2. The HSS contains LTE subscription data and routing information (PDN type, PDN address, APN, and VPLMN address allowed). These subscription data are permanent data in the HSS and have to be inserted for the tests. The HSS is accessible from the MME via the S6a interface. For roaming UEs, the HSS is in a different PLMN than the current MME. The MME is updated with new EPS subscription data with the Insert Subscriber Data procedure. IMSI is the primary key to the EPS subscription data stored in the HSS. There may be several sets of HSS subscription data per IMSI. HSS EPS Subscription Data: Field IMSI MSISDN IMEI / IMEISV MME Address MME Capabilities MS PS Purged from EPC ODB parameters Access Restriction EPS Subscribed Charging Charactericstics Trace Reference Trace Type OMC Identity Subscribed-UE-AMBR APN-OI- Replacement RFSP Index URRP-MME Description IMSI is the main reference key. The basic MSISDN of the UE (Presence of MSISDN is optional). International Mobile Equipment Identity - Software Version Number The IP address of the MME currently serving this MS. Indicates the capabilities of the MME with respect to core functionality e.g. regional access restrictions. Indicates that the EMM and ESM contexts of the UE are deleted from the MME. Indicates that the status of the operator determined barring ODB parameters Indicates that the status of the operator determined barring Indicates the access restriction subscription information. The charging characteristics for the MS, e.g. normal, prepaid, flat-rate, and/or hot billing subscription. Identifies a record or a collection of records for a particular trace. Indicates the type of trace, e.g. HSS trace, and/or MME/ Serving GW / PDN GW trace. Identifies the OMC that shall receive the trace record(s). The Maximum Aggregated uplink and downlink MBRs to be shared across all Non-GBR bearers according to the subscription of the user. Indicates the domain name to replace the APN OI when constructing the PDN GW FQDN upon which to perform DNS queries. This replacement applies for all the APNs in the subscriber's profile. An index to specific RRM configuration in the E-UTRAN UE Reachability Request Parameter indicating that UE activity notification from MME has been requested by the HSS.

6 Each subscription profile contains one or more PDN subscription contexts: Context Identifier PDN Address PDN Type Access Point Name (APN) EPS subscribed QoS profile Subscribed- APN-AMBR EPS PDN Subscribed the Charging Characteristics VPLMN Address Allowed PDN GW identity PDN GW Allocation Type PLMN of PDN GW Index of the PDN subscription context. Indicates subscribed IP address(es). Indicates the subscribed PDN Type (IPv4, IPv6, IPv4v6) A label according to DNS naming conventions describing the access point to the packet data network (or a wildcard). The bearer level QoS parameter values for that APN's default bearer (QCI and ARP). The maximum aggregated uplink and downlink MBRs to be shared across all Non-GBR bearers, which are established for this APN. The charging characteristics of this PDN Subscribed context for the MS, e.g. normal, prepaid, flatrate, and/or hot billing subscription. The charging characteristics is associated with this APN. Specifies whether for this APN the UE is allowed to use the PDN GW in the domain of the HPLMN only, or additionally the PDN GW in the domain of the VPLMN. The identity of the PDN GW used for this APN. The PDN GW identity may be either an FQDN or an IP address. The PDN GW identity refers to a specific PDN GW. Indicates whether the PDN GW is statically allocated or dynamically selected by other nodes. A statically allocated PDN GW is not changed during PDN GW selection. Identifies the PLMN in which the dynamically selected PDN GW is located List of APN - PDN GW ID relations (for PDN subscription context with wildcard APN): APN - P GW relation #n The APN and the identity of the dynamically allocated PDN GW of a PDN connection that is authorised by the PDN subscription context with the wildcard APN. The PDN GW identity may be 3. S8 interface is implemented in HPLMN(a) and VPLMN(b) 4. S9 interface is implemented in HPLMN(a) and VPLMN(b) (when PMIP is used on S8) 6. MME and vpcrf(if PMIP is used) has access to DNS functionality 7. Configuration of the test environment for transparent or non-transparent access to Intranet/ISP (The key point for the access of an Intranet or an ISP infrastructure is the APN-Network-Identifier. This can be sent by mobile during Initial Attach or can be set by default by the MME. The APN-Network Identifier defines to which external network the P-GW is connected. This means in detail the interface of the P-GW to an external network. This external interface at the P-GW is connected to the infrastructure providing Intranet functionality (e.g. local HTTP-Server) or to a kind of Serverfarm providing ISP functionality (HTTP-Server, Proxy-Server or FTP-Server with connection to the external Internet). This mechanism will provide the physical path to the Intranet/ISP-functionality. However each operator has to make sure that the APN-resolution algorithms are implemented correctly in his MME accordingly 8. Dynamic Address allocation for access to Intranet/ISP Prerequisites for LTE+2G/3G Co-existence - 2G/3G access towards PGW using Gp- or S8- Interface testing: The following prerequisites are assumed: 1. LTE and GPRS user equipment (UE) supporting the network operation modes in VPLMN(b). 2. HSS contains EPS subscription data for LTE roaming. Prerequisites are same as described in the table "Prerequisies for LTE testing" above. 3. The HSS/HLR contains GPRS and EPS subscription data and routing information (PDP/PDN type (S), PDP/PDN address (S), APN (S), and VPLMN address allowed) for 2G/3G roaming. These subscription data are permanent data in the HSS/HLR and have to be inserted for the tests. The HSS/HLR is accessible from the SGSN via the Gr interface. For roaming UEs, the HSS/HLR is in a different PLMN than the current SGSN. The SGSN is updated with new GPRS and EPS subscription data with the Insert Subscriber Data procedure. IMSI is the primary key to the GPRS subscription data stored in the HSS/HLR. There may be several sets of GPRS and EPS subscription data per IMSI. If Gn/Gp interface is used for 2G/3G roaming, the subscription information stored in HSS/HLR for 2G/3G roaming is defined in "Prerequisites for GPRS only roaming" table above.

7 If S4/S8 interfaces are used for 2G/3G roaming, the subscription information stored in HSS/HLR for 2G/3G roaming is defined below "HSS GPRS Subscription Data" table. HSS GPRS Subscription Data: Field IMSI MSISDN SGSN Number SGSN Address Subscribed Charging Characteristics Trace Reference Trace Type OMC Identity SMS Parameters MS Purged for GPRS MNRG GGSN-list GPRS-CSI MG-CSI APN-OI Replacement ODB for PS parameters Access Restriction Description IMSI is the main reference key. The basic MSISDN of the MS. The SS7 number of the SGSN currently serving this MS. The IP address of the SGSN currently serving this MS. The charging characteristics for the MS e.g. normal, prepaid, flat-rate, and /or hot billing subscription Identifies a record or a collection of records for a particular trace Indicates the type of trace, e.g. MSC/BSS trace, HLR trace, and/or SGSN/GGSN/BSS trace Identifies the OMC that shall receive the trace record(s) SMS-related parameters, e.g. operator-determined barring Indicates that the MM and PDP contexts of the MS are deleted from the SGSN. Indicates that the MS is not reachable through an SGSN, and that the MS is marked as not reachable for GPRS at the SGSN and possibly at the GGSN. The GSN number and optional IP address pair related to the GGSN that shall be contacted when activity from the MS is detected and MNRG is set. The GSN number shall be either the number of the GGSN or the protocol-converting GSN as described in the subclause "MAP-based GGSN HLR Signalling" and "GTP and MAP-based GGSN HLR Signalling". Optional GPRS CAMEL Subscription information, see TS Optional Mobility Management for GPRS CAMEL subscription information, see TS Indicates the domain name to replace the APN-OI when constructing the GGSN FQDN upon which to perform a DNS resolution. This replacement applies for all the APNs in the subscribers' profile. Indicates that the status of the opeartor determined barring for packet oriented services Indicates the access restriction subscription information (Note, the access restriction applies to both packet and circuit oriented services) IMEI International Mobile Equipment Identity SVN Software Version Number RFSP Index An index to specific RRM configuration in the UTRAN/GERAN Each IMSI contains zero or more of the following PDP context subscription records: PDP Context Identifier Index of the PDP context. PDP Type PDP type, e.g., PPP or IP (IPv4, IPv6, IPv4v6) PDP Address Access Point Name QoS Profile Subscribed VPLMN Address Allowed PDP Context Charging Characteristics EPS subscribed QoS profile APN-AMBR P-GW Address PDP address, e.g., and IP address. This field shall be empty if dynamic addressing is allowed. A label according to DNS naming conventions describing the access point to the external packet data network. The quality of service profile subscribed. QoS Profile Subscribed is the default level if a particular QoS profile is not requested. Specifies whether the MS is allowed to use the APN in the domain of the HPLMN only, or additionally the APN in the domain of the VPLMN. The charging characteristics of this PDP Bearer Context e.g. normal, prepaid, flat-rate and/or hot billing The EPS bearer level QoS parameter values for that APN's default bearer (QCI and ARP) the maximum aggregated uplink and downlink MBR values to be shared across all Non-GBR EPS bearers, which are established for this APN The address currently used for the P-GW supporting this APN

8 3. Towards GPRS no supplementary services are invoked. 4. The SGi-Interface is implemented in HPLMN(a) and VPLMN(b) 5. The Gp-Interface or S8-Interface is implemented (Inter-PLMN connection) 6. SGSN/PGW-access to DNS-Functionality 7. Configuration of the test environment for transparent or non-transparent access to Intranet/ISP (The key point for the access of an Intranet or an ISP infrastructure is the APN-Network-Identifier. This can be sent by mobile during PDP-context activation or can be set by default by the SGSN. The APN-Network Identifier defines to which external network the PGW is connected. This means in detail the interface of the PGW to an external network. This external interface at the PGW is connected to the infrastructure providing Intranet functionality (e.g. local HTTP-Server) or to a kind of Serverfarm providing ISP functionality (HTTP-Server, Proxy-Server or FTP-Server with connection to the external Internet). This mechanism will provide the physical path to the Intranet/ISP-functionality. However each operator has to make sure that the APN-resolution algorithms are implemented correctly in his SGSN according 3GPP TS and Annex A of 3GPP TS Dynamic Address allocation for access to Intranet/ISP 1.6 Equipment requirements User equipment User Equipment for GPRS Testing The Equipment described in this Section is necessary for undertaking the test cases described in Section 2. (a) Two Mobile Equipments supplied by VPLMN(b). (The Mobile Stations should be in minimum class C-GPRS Mobile Stations however class A- and B-Mobiles can be used also) (b) Two GPRS compatible SIMs supplied by HPLMN(a). The supply of additional SIMs may be agreed by the HPLMN(a) and VPLMN(b), typically for the purposes of: i) Spare cards in case of failure ii) Allocation from different HLRs (c) It shall be possible to specify what types of Mobile Equipments are supplied for testing between operator agreement (HPLMN (a) and VPLMN (b)). User Equipment for LTE/EPC Testing: The Equipment described in this Section is necessary for undertaking the test cases described in Section 2 and 19. (a) Two User Equipments supplied by VPLMN(b). (b) Two LTE compatible USIMs supplied by HPLMN(a). The supply of additional USIMs may be agreed by the HPLMN(a) and VPLMN(b), typically for the purposes of: i) Spare cards in case of failure ii) Allocation from different HSSs (c) It shall be possible to specify what types of User Equipments are supplied for testing between operator agreement (HPLMN (a) and VPLMN (b)) Test Equipment Test equipment for GPRS only Testing: (a) The availability of a CCITT # 7 tester able to decode SCCP, TCAP, MAP, BSSAP+ is highly advisable, but not strictly necessary for these tests. However it is essential for any analysis of test case failures. (b) The availability of a Gi and Gp interface IP testing and monitoring equipment is highly advisable. (c) Sample files and applications for data transfer testing. Test equipment for LTE/EPC only Testing: (a) The availability of a SGi, S6a, S8 and S9 interface IP testing and monitoring equipment is highly advisable. (b) Sample files and applications for data transfer testing. Test equipment for LTE+2G/3G Co-existence (2G/3G access towards PGW using Gp- or S8- Interface) Testing: (a) The availability of a CCITT # 7 tester able to decode SCCP, TCAP, MAP is highly advisable, but not strictly necessary for these tests. However it is essential for any analysis of test case failures. (b) The availability of a SGi, Gp, S8 and S4 interface IP testing and monitoring equipment is highly advisable. (c) Sample files and applications for data transfer testing.

9 2. TEST CASES for GPRS and LTE - overview The test cases are divided in three groups: 1) GPRS-attachment and -detachment, LTE-attachement and -detachment 2) Services /PDP-Context Activation/EPS Bearer Establishment 3) MAP/DiameterTests Each operator has to make sure that the APN-resolution algorithms are implemented correctly in his SGSN according to GSM and Annex A of 3GPP TS for GPRS, and in MME according to 3GPP TS for LTE. The test configuration for GPRS is shown below. It is anticipated that it may be necessary to monitor both signalling messages and IP packet data on the Network Entity interfaces shown in the diagram. However this is not a firm requirement for this test specification. The test configuration for LTE/EPC (GTP based) is shown below

10 The test configuration for LTE/EPC (PMIP based) is shown below The test configuration for LTE and 2G/3G Co-exisitence Roaming is shown below. See GSMA PRD IR.88 for the details of roaming scenarios.

11 2.1 GPRS-Attachment GPRS-Attach of MS1(a) in VPLMN(b) (GPRS Attach only) Charging aspects: Preconditios: Action: Result: Comments: Opening of a M-CDR Charging parameters to collect/compare: 1) IMSI/MSISDN of the MS 2) IMEI of the ME, if available 3) Timestamp when GPRS-Attach is done (The M-CDR is closed after GPRS-Detach MS1(a) contains SIM of HPLMN(a) No valid NM contexts are established for MS1(a). HLR(a) record contains basic service information including GPRS substription data. Power-up MS1(a) and perform GPRS Attach only on VPLMN(b). Check MM contexts in MS1(a) and SGSN(b) for the IMSI/P-TMSI /MSISDN of MS1(a). Successful result if MS1(a) is in READY state (2.5G) Successful result if valid MM contexts are established in the MS1(a) and SGSN(b). This test case confirms operation of Insert Subscriber Data procedures after GPRS-Attach only. It checks the support of relevant MAP operations, TCAP processes and SCCP addressing.

12 2.2 Services (Intranet-/ISP-Access, WAP, MMS) / PDP-Context Activation Charging aspects: M-CDR is already open (GPRS-Attach) Opening of S-CDR and G-CDR by PDP-context-activation (The S-CDR and G-CDR are closed after PDPcontext-deactivation) Charging parameters to collect/compare: (S-CDR and G-CDR) 1) IMSI/MSISDN of the MS 2) IMEI of the ME, if available 3) Access Point Name 4) Timestamp when PDP-context-activation is done 5) Timestamp when downloading of pre-defined file is started 6) Size of total down- and uplink data towards download of predefined file (The volume of the predefined file to be transferred has to create in minimum 11/2 S-CDR. How to create this S-CDR and the amount of data to be transferred is operator dependent) 7) Timestamp when PDP-context-deactivation is done Intranet-/ISP-Access of MS1(a) in VPLMN(b) using home GGSN (user provides Network- ID and no Operator-ID and is not allowed to use visited GGSN), HTTP-WEB-Browsing

13 Preconditions: Action: Result: Action: Result: Comments: MS1(a) is GPRS-Attached in VPLMN(b). (MS in STANDBY or READY state for 2.5G) No valid PDP contexts are established in the MS1(a). PDP context subscription record(s) exists in HLR(a) where PDP type (S) = PDP type (R). One PDP context subscription record exists in HLR(a) where APN(S) = APN(R). VPLMN not allowed for selected PDP context subscription records. MS1(a) performs Activate PDP Context Request. PDP type (R) is sent by MS1(a). A PDP Address is not sent by MS1(a) and is not present in a PDP context subscription record. (Dynamic address allocation) APN (R) (Network-ID, no Operator-ID) is sent by MS1(a). Pre-defined file is requested/transferred from External Network (Network-ID) to MS1(a) by accessing HTTP-server over WEB-browsing. SGSN(b) receives APN(R) sent by MS1(a). SGSN(b) selects PDP context subscription record (APN(S ), APN(S)=(APN(R)) and sets selection mode parameter to subscribed. SGSN interrogates DNS-Functionality with selected APN with appended HPLMN APN-Operator-ID Selected APN is translated to a GGSN(a)-Address in the HPLMN(a). SGSN(b) returns an Activate PDP Context Accept message to the MS1(a) including PDP type and PDP address. Valid PDP contexts are established in the MS1(a). Connection to Network specified by APN(Network-ID) is established. Pre-defined file is successfully transferred at an agreed quality (data rate) with no errors after using HTTP-Service. MS1(a) performs Deactivate PDP Context Request. PDP-Context is deactivated This test case confirms PDP context activation/deactivation towards a home GGSN(a) with: APN(R) is not empty; (Network-ID, no Operator-ID) Setting of APN (Operator-ID) by subscription for HPLMN(a) (APN(S)). Setting up IP-tunnel connections (GTP, IP, UDP/TCP) Root address lookup and dynamic address allocation. If the PDP context activation procedure fails or if the SGSN returns an Activate PDP Context Reject (Cause, PDP Configuration Options) message, then the user may attempt another activation to the same APN up to a maximum number of attempts.

14 2.2.2 WAP access of MS1(a) in VPLMN(b) using home GGSN (user provides Network-ID and no Operator-ID and is not allowed to use visited GGSN), WAP-Browsing Preconditions: Actions: Result: Action: Result: Comments: MS1(a) is GPRS-Attached in VPLMN(b). (MS in STANDBY or READY state for 2.5G) No valid PDP contexts are established in the MS1(a). PDP context subscription record(s) exists in HLR(a) where PDP type (S) = PDP type (R). One PDP context subscription record exists in HLR(a) where APN(S) = APN(R). VPLMN not allowed for selected PDP context subscription records. MS1(a) performs Activate PDP Context Request. PDP type (R) is sent by MS1(a). A PDP Address is not sent by MS1(a) and is not present in a PDP context subscription record. (Dynamic address allocation) APN (R) (Network-ID, no Operator-ID) is sent by MS1(a). Pre-defined file is requested/transferred from External Network (Network-ID) to MS1(a) by accessing WAP-server over WAP-browsing SGSN(b) receives APN(R) sent by MS1(a). SGSN(b) selects PDP context subscription record (APN(S ), APN(S)=(APN(R)) and sets selection mode parameter to subscribed. SGSN interrogates DNS-Functionality with selected APN with appended HPLMN APN-Operator- ID. Selected APN is translated to a GGSN(a)-Address in the HPLMN(a). SGSN(b) returns an Activate PDP Context Accept message to the MS1(a) including PDP type and PDP address. Valid PDP contexts are established in the MS1(a). Connection to Network specified by APN(Network-ID) is established. Pre-defined file is successfully transferred at an agreed quality (data rate) with no errors after using WAP-Service. MS1(a) performs Deactivate PDP Context Request. PDP-Context is deactivated This test case confirms PDP context activation/deactivation towards a home GGSN(a) with: APN(R) is not empty; (Network-ID, no Operator-ID) Setting of APN (Operator-ID) by subscription for HPLMN(a) (APN(S)). Setting up IP-tunnel connections (GTP, IP, UDP/TCP) Root address lookup and dynamic address allocation. If the PDP context activation procedure fails or if the SGSN returns an Activate PDP Context Reject (Cause, PDP Configuration Options) message, then the user may attempt another activation to the same APN up to a maximum number of attempts.

15 2.2.3 MMS with MS1(a), MS2(a) in VPLMN(b) using home GGSN and MMSC Charging aspects: M-CDR is already open (GPRS-Attach) S-CDR is already open (PDP-context-activation) Charging parameters to collect/compare: (M-CDR and S-CDR) 1) IMSI/MSISDN of the MS 2) IMEI of the ME, if available 3) Timestamp when MMS is send by MS1(a) (S-CDR) 4) Timestamp when MMS is fetched by MS2(a) (S-CDR) 5) Amount of total data DL / UL transfer MS1(a) & MS2(a) 6) MMS APN (S-CDR) Preconditions: Action: Result: Comments: MMS-MO/MT is provisioned MS1(a) and MS2(a) are registered in VPLMN(b). Use MS1(a) to transmit a Multimedia Message to MS2(a) via the Home MMSC Await delivery of Multimedia Message to MS2(a) Check contents of Multimedia Message with those transmitted Successful result if Multimedia Message is correctly delivered. If delivery report is requested, check that it is correctly delivered. This test case confirms correct operation of mobile-originated/terminated MMS routing and transfer over GPRS radio channels Intranet-/ISP-Access of UE1(a) in VPLMN(b) using home PGW over Gp-interface (user provides Network-ID and no Operator-ID and is not allowed to use visited GGSN), HTTP-WEB- Browsin Preconditions: Action: UE1(a) is GPRS-Attached in VPLMN(b). (UE in STANDBY or READY state for 2.5G) No valid PDP contexts are established in the UE1(a). PDP context subscription record(s) exists in HSS(a) where PDP type (S) = PDP type (R). One PDP context subscription record exists in HSS(a) where APN(S) = APN(R). VPLMN not allowed for selected PDP context subscription records. UE1(a) performs Activate PDP Context Request. PDP type (R) is sent by UE1(a). A PDP Address is not sent by UE1(a) and is not present in a PDP context subscription record. (Dynamic address allocation) APN (R) (Network-ID, no Operator-ID) is sent by UE1(a). Pre-defined file is requested/transferred from External Network (Network-ID) to UE1(a) by accessing HTTP-server over WEB-browsing.

16 Result: Action: Result: Comments: SGSN(b) receives APN(R) sent by UE1(a). SGSN(b) selects PDP context subscription record (APN(S ), APN(S)=(APN(R)) and sets selection mode parameter to subscribed. SGSN interrogates DNS-Functionality using procedures defined in 3GPP TS with selected APN with appended HPLMN APN-Operator-ID Selected APN is translated to a PGW-Address in the HPLMN(a). SGSN(b) returns an Activate PDP Context Accept message to the UE1(a) including PDP type and PDP address. Valid PDP contexts are established in the UE1(a). Connection to Network specified by APN(Network-ID) is established. Pre-defined file is successfully transferred at an agreed quality (data rate) with no errors after using HTTP-Service. UE1(a) performs Deactivate PDP Context Request. PDP-Context is deactivated This test case confirms PDP context activation/deactivation towards a home PGW(a) with: APN(R) is not empty; (Network-ID, no Operator-ID) Setting of APN (Operator-ID) by subscription for HPLMN(a) (APN(S)). Setting up IP-tunnel connections (GTP, IP, UDP/TCP) Root address lookup and dynamic address allocation. If the PDP context activation procedure fails or if the SGSN returns an Activate PDP Context Reject (Cause, PDP Configuration Options) message, then the user may attempt another activation to the same APN up to a maximum number of attempts Intranet-/ISP-Access of UE1(a) in VPLMN(b) using visited SGW and home PGW over S8- interface (user provides Network-ID and no Operator-ID and is not allowed to use visited GGSN), HTTP-WEB-Browsing Preconditions: Action: Result: UE1(a) is GPRS-Attached in VPLMN(b). (UE in STANDBY or READY state for 2.5G) No valid EPS Bearers are established in the UE1(a). EPS Bearer subscription record(s) exists in HSS(a) where PDN type (S) = PDN type (R). One PDN context subscription record exists in HSS(a) where APN(S) = APN(R). VPLMN not allowed for selected EPS Bearer context subscription records. UE1(a) performs Activate PDP Context Request. PDP type (R) is sent by UE1(a). A PDN Address is not sent by UE1(a) and is not present in a EPS Bearer context subscription record. (Dynamic address allocation) APN (R) (Network-ID, no Operator-ID) is sent by UE1(a). Pre-defined file is requested/transferred from External Network (Network-ID) to MS1(a) by accessing HTTP-server over WEB-browsing. SGSN(b) receives APN(R) sent by UE1(a). SGSN(b) selects EPS Bearer subscription record (APN(S ), APN(S)=(APN(R)) and sets selection mode parameter

17 Action: Result: Comments: to subscribed. SGSN interrogates DNS-Functionality using procedures defined in 3GPP TS with selected APN with appended HPLMN APN-Operator-ID Selected APN is translated to a SGW-Address in the VPLMN(b) and PGW- Address in the HPLMN(a). SGSN(b) returns an Activate PDP Context Accept message to the UE1(a) including PDN type and PDN address. Valid EPS Bearer contexts are established in the UE1(a). Connection to Network specified by APN(Network-ID) is established. Pre-defined file is successfully transferred at an agreed quality (data rate) with no errors after using HTTP-Service. UE1(a) performs Deactivate PDP Context Request. EPS Bearer Context is deactivated.this test case confirms EPS Bearer context activation/deactivation towards a visited SGW(b) and home PGW(a) with: APN(R) is not empty; (Network-ID, no Operator-ID) Setting of APN (Operator-ID) by subscription for HPLMN(a) (APN(S)). Setting up IP-tunnel connections (GTP, IP, UDP/TCP) Root address lookup and dynamic address allocation. If the EPS Bearer context activation procedure fails or if the SGSN returns an Activate PDP Context Reject (Cause, PDP Configuration Options) message, then the user may attempt another activation to the same APN up to a maximum number of attempts. 2.3 MAP-Tests (SMS, Location Cancellation, GPRS-Barring) Mobile originated and terminated SMS (MS1(a) GPRS-Attached only / MS2(a) GPRS- Attached only) Charging aspects: Preconditions: Action: Action: Result: Comments: M-CDR is already open (GPRS-Attach) S-CDR is already open (PDP-context-activation) Charging parameters to collect/compare: (M-CDR and S-CDR) 1) IMSI/MSISDN of the MS 2) IMEI of the ME, if available 3) Timestamp when GPRS-Attach of MS2(a) is done (M-CDR) 4) Timestamp when SMS is send (S-CDR) 5) Timestamp when SMS is received (S-CDR) 6) Timestamp when GPRS-Detach of MS1(a) and MS2(a) is done (M-CDR) 7) SMS-SC-Number (S-CDR) SMS-MO/MT is provisioned in HLR subscription including GPRS subscription data. MS1(a) and MS2(a) are registered in VPLMN(b). Use MS1(a) to transmit a 160 character Short Message to MS2(a) via the Home Country SMS - Service Centre with Message Waiting priority selected. Await delivery of Short Message to MS2(a) Check contents of Short Message with those transmitted. Successful result if Short Message is correctly delivered to MS2(a). This test case confirms correct operation of mobile-originated/terminated SMS routing and transfer over GPRS radio channels including Message Waiting and Note MS Present procedures. Message flow: Mobile originated and terminated SMS transfer over GPRS channels

18 2.3.2 Location cancellation for MS1(a)-GPRS Subscription held in VPLMN(b) Preconditions: Action: Result: Comments: SGSN(b) in VPLMN(b) contains GPRS-subscription information of MS1(a) and PDP-context for MS1(a) is activated. HPLMN(a) personal deletes MS1(a) GPRS-subscription from HLR(a) either using HLR`s Man-Machine Interface not via Administrative Data Centre (ADC) input to HLR(a). Successful result if SGSN(b) and GGSN(a) or GGSN(b) record for MS1(a) has been erased and PDP-Context for MS1(a) has been deactivated. This test case confirms that the Cancel Location between HLR(a) and SGSN(b) procedure and PDP Context Deactivation initiated by the network operates correctly. HLR-Initiated Detach Procedure (reference 3GPP TS23.060) The HLR-Initiated Detach procedure is initiated by the HLR. The HLR uses this procedure for operator determined purposes to request the removal of a subscriber's MM and PDP contexts at the SGSN

19 2.3.3 Operator Determined Barring for all MS initiated PDP context activatons of MS1(a). Preconditions: Action: Result: Comments: SGSN(b) in VPLMN(b) contains subscription information of MS1(a). HPLMN(a) personnel activates ODB for MS initiated PDP context activation for MS1(a) from HLR(a) either using HLR`s Man-Machine Interface or via Administrative Data Centre (ADC) input to HLR(a). Check SGSN(b) for records of MS1(a). Try to make a PDP-context-activation from MS1(a) and try to send a SMS from MS1(a). Successful result if SGSN(b) record for MS1(a) contains ODB information and no PDP-context-activation and SMS-mobile originated attempts are successful. This test case confirms that the ODB procedure for outgoing calls operates correctly G S M A - SPECIFIC TESTS LTE Attach and Detach Charging aspects: Charging parameters to collect/compare: 1) IMSI/MSISDN of the UE 2) IMEI of the UE, if available 3) Timestamp when LTE-Initial-Attach with EPS bearer establishment is done 4) Access Point Name 5) Timestamp when total down- and uplink data started 6) Size of total down- and uplink data during the EPS bearer establishment 7) Timestamp when LTE Detach is done 8) LTE-detach Preconditions: Action: Expected Result: UE1(a) contains USIM of HPLMN(a). No valid EMM contexts are established for UE1(a). HSS(a) record contains basic service information including EPS subscription data. No valid PDN connectivity are established in the UE1(a). One EPS bearer context subscription record exists in HSS(a) where APN(S) = APN(R). VPLMN not allowed for selected EPS context subscription records. Power-up UE1(a) and perform LTE Attach only on VPLMN(b). Check EMM contexts in UE1(a) and MME(b) for the IMSI/GUTI /MSISDN of MS1(a). A PDN Address is not sent by UE1(a) and is not present in a EPS context subscription record. (Dynamic address allocation) APN (R) (Network-ID, no Operator-ID) is sent by UE1(a). PDN connectivity establishment should be tested LTE-detach procedure should be tested Successful result if UE1(a) is in EMM-REGISTERED and ECM-CONNECTED state Successful result if valid EMM contexts are established in the UE1(a) and MME(b).

20 Comments: Successful result if PDN Connectivity towards the default APN is established. Successful result if LTE-detach for UE1(a) is completed. This test case confirms operation of Insert Subscriber Data procedures after LTE-Attach only. It checks the support of relevant Diameter operations Message-flow: LTE-Attach (including PDN connectivity establishment) procedure Message-flow: UE requested LTE-Detach

21 LTE Cancel Location Charging aspects: Preconditions: Action: Expected Result: Comments: none MME(b) in VPLMN(b) contains EPS-subscription information of UE1(a) and PDN connectivity for UE1(a) is activated. HPLMN(a) personnel deletes UE1(a) EPS-subscription from HSS(a) either using HSS`s Man-Machine Interface not via Administrative Data Centre (ADC) input to HSS(a). If GTP is used for S8, successful result if records in MME(b), SGW(b), PGW(a) and hpcrf(a) for UE1(a) has been erased and PDN connectivity for UE1(a) has been deactivated. If PMIP is used for S8, successful result if records in MME(b), SGW(b), PGW(a), vpcrf(b) and hpcrf(a) for UE1(a) has been erased and PDN connectivity for UE1(a) has been deactivated. This test case confirms that the Cancel Location between HSS(a) and MME(b) and Detach initiated by the network" operate correctly. Message-flow: LTE Cancel Location

22 LTE Operator Determined Barring Charging aspects: Preconditions: Action: Expected Result: Comments: None UE1(a) is attached to VPLMN(b) and has a PDN connectivity. MME(b) in VPLMN(b) contains subscription information of UE1(a). HPLMN(a) personnel activates ODB for PDN connectivity for UE1(a) from HSS(a) either using HSS`s Man- Machine Interface or via Administrative Data Centre (ADC) input to HSS(a). Check MME(b) for records of UE1(a). Try to make a LTE-attach from UE1(a) and send attach request from UE1(a). Successful result if MME(b) record for UE1 (a) contains ODB information, attach request is rejected and no PDN connectivity establishment are successful. Message-flow: LTE Operator Determined Barring

23 G S M A -SPEC. TEST CASE HEADER (not in use now) Charging aspects: Preconditions: Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1 Action: Detail Text 2 / Action- field in General TC Expected Result: Detail Text 3 (Result) Comments: Detail Text 4 Detail Text 5 Take the space, whatever you require to decribe the test case by inserting additional lines! G S M A - SPEC. TEST CASE HEADER (not in use now) Charging aspects: Preconditions: Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1 Action: Detail Text 2 / Action- field in General TC Expected Result: Detail Text 3 (Result) Comments: Detail Text 4 Detail Text 5 Take the space, whatever you require to decribe the test case by inserting additional lines! G S M A -SPEC. TEST CASE HEADER (not in use now) Charging aspects: Preconditions: Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1 Action: Detail Text 2 / Action- field in General TC Expected Result: Detail Text 3 (Result) Comments: Detail Text 4 Detail Text 5 Take the space, whatever you require to decribe the test case by inserting additional lines! G S M A -SPEC. TEST CASE HEADER (not in use now) Charging aspects: Preconditions: Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1 Action: Detail Text 2 / Action- field in General TC Expected Result: Detail Text 3 (Result) Comments: Detail Text 4 Detail Text 5 Take the space, whatever you require to decribe the test case by inserting additional lines! G S M A -SPEC. TEST CASE HEADER (not in use now) Charging aspects: Preconditions: Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1 Action: Detail Text 2 / Action- field in General TC Expected Result: Detail Text 3 (Result) Comments: Detail Text 4

24 Detail Text 5 Take the space, whatever you require to decribe the test case by inserting additional lines! G S M A -SPEC. TEST CASE HEADER (not in use now) Charging aspects: Preconditions: Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1 Action: Detail Text 2 / Action- field in General TC Expected Result: Detail Text 3 (Result) Comments: Detail Text 4 Detail Text 5 Take the space, whatever you require to decribe the test case by inserting additional lines! G S M A -SPEC. TEST CASE HEADER (not in use now) Charging aspects: Preconditions: Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1 Action: Detail Text 2 / Action- field in General TC Expected Result: Detail Text 3 (Result) Comments: Detail Text 4 Detail Text 5 Take the space, whatever you require to decribe the test case by inserting additional lines! 20.1 O P E R A T O R - SPECIFIC TESTS O P E R A T O R - SPEC. TEST CASE HEADER Charging aspects: Preconditions: Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1 Action: Detail Text 2 / Action- field in General TC Expected Result: Detail Text 3 (Result) Comments: Detail Text 4 Detail Text 5 Take the space, whatever you require to decribe the test case by inserting additional lines! O P E R A T O R - SPEC. TEST CASE HEADER Charging aspects: Preconditions: Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1 Action: Detail Text 2 / Action- field in General TC Expected Result: Detail Text 3 (Result) Comments: Detail Text 4 Detail Text 5 Take the space, whatever you require to decribe the test case by inserting additional lines! O P E R A T O R - SPEC. TEST CASE HEADER

25 Charging aspects: Preconditions: Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1 Action: Detail Text 2 / Action- field in General TC Expected Result: Detail Text 3 (Result) Comments: Detail Text 4 Detail Text 5 Take the space, whatever you require to decribe the test case by inserting additional lines! O P E R A T O R - SPEC. TEST CASE HEADER Charging aspects: Preconditions: Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1 Action: Detail Text 2 / Action- field in General TC Expected Result: Detail Text 3 (Result) Comments: Detail Text 4 Detail Text 5 Take the space, whatever you require to decribe the test case by inserting additional lines! O P E R A T O R - SPEC. TEST CASE HEADER Charging aspects: Preconditions: Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1 Action: Detail Text 2 / Action- field in General TC Expected Result: Detail Text 3 (Result) Comments: Detail Text 4 Detail Text 5 Take the space, whatever you require to decribe the test case by inserting additional lines! O P E R A T O R - SPEC. TEST CASE HEADER Charging aspects: Preconditions: Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1 Action: Detail Text 2 / Action- field in General TC Expected Result: Detail Text 3 (Result) Comments: Detail Text 4 Detail Text 5 Take the space, whatever you require to decribe the test case by inserting additional lines! O P E R A T O R - SPEC. TEST CASE HEADER Charging aspects: Preconditions: Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1 Action: Detail Text 2 / Action- field in General TC Expected Result: Detail Text 3 (Result) Comments: Detail Text 4 Detail Text 5 Take the space, whatever you require to decribe the test case by inserting additional lines!