1、 ETSI TS 103 202-2 V1.1.1 (2015-12) Core Network and Interoperability Testing (INT); GTPv2-C Conformance Testing for S11 Interface; (3GPPTMRelease 10); Part 2: Test Suite Structure and Test Purposes (TSS Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which
2、is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/ipr.etsi.org). 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 ETS
3、I 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 Core Network and Interoperability Testing (INT). The present document is part 2 of a m
4、ulti-part deliverable. Full details of the entire series can be found in part 1 2. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Draf
5、ting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 103 202-2 V1.1.1 (2015-12)6 1 Scope The present document provides the Test Suite Structure (TSS) and Test Purposes (TP) for the tes
6、t specifications for the GTPv2-C protocol on the S11 interface as specified in ETSI TS 129 274 1 in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 4 and ETSI ETS 300 406 5. 2 References 2.1 Normative references References are either spe
7、cific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not
8、 found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for t
9、he application of the present document. 1 ETSI TS 129 274 (V10.14.0): “Universal Mobile Telecommunications System (UMTS); LTE; 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 (3GPP TS 29.274 version 10.14.0 Releas
10、e 10)“. 2 ETSI TS 103 202-1: “Core Network and Interoperability Testing (INT); GTPv2-C Conformance Testing for S11 Interface; (3GPP Release 10); Part 1: Protocol Implementation Conformance Statement (PICS)“. 3 ISO/IEC 9646-1: “Information technology - Open Systems Interconnection - Conformance testi
11、ng methodology and framework - Part 1: General concepts“. 4 ISO/IEC 9646-7: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements“. 5 ETSI ETS 300 406: “Methods for testing and Specification (MTS); Proto
12、col and profile conformance testing specifications; Standardization methodology“. 6 ETSI TS 123 401 : “LTE; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access (3GPP TS 23.401)“. 7 ETSI TS 124 301: “Universal Mobile Telecommunicati
13、ons System (UMTS); LTE; Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 (3GPP TS 24.301)“. 8 ETSI TS 123 007: “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Restoration procedures (3GPP TS 23.007)“. 9 ETSI TS
14、 123 402: “Universal Mobile Telecommunications System (UMTS); LTE; Architecture enhancements for non-3GPP accesses (3GPP TS 23.402)“. 10 ETSI TS 123 216: “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Single Radio Voice Call Continuity
15、 (SRVCC); Stage 2 (3GPP TS 23.216)“. 11 ETSI TS 123 203: “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Policy and charging control architecture (3GPP TS 23.203)“. ETSI ETSI TS 103 202-2 V1.1.1 (2015-12)7 2.2 Informative references Ref
16、erences are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While
17、any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. Not applic
18、able. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ETSI TS 129 274 1 and the following apply: Abstract Test Method (ATM): Refer to ISO/IEC 9646-1 3. Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 3. Implementation Un
19、der Test (IUT): Refer to ISO/IEC 9646-1 3. Test Purpose (TP): Refer to ISO/IEC 9646-1 3. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in ETSI TS 129 274 1 and the following apply: AMBR Aggregate Maximum Bit Rate APN Access Point Name APN-NI Access Point Name Ne
20、twork Identifier APN-OI Access Point Name Operator Identifier ARP Allocation and Retention Priority AS Access Stratum CDMA Code Division Multiple Access CN Core Network CS Circuit SwitchedDL Downlink eNB E-UTRAN NodeB EPC Evolved Packet Core EPS Evolved Packet System E-UTRAN Evolved UTRAN FQ-CSID Fu
21、lly Qualified PDN Connection Set Identifier FQ-TEID Fully Qualified Tunnel Endpoint Identifier GBR Guaranteed Bit Rate GERAN GSM/EDGE Radio Access Network GPRS General Packet Radio Service GSM Global System for Mobile Communications GTP GPRS Tunneling Protocol GTP-U GPRS Tunneling Protocol-User plan
22、e GTPv2-C GPRS Tunneling Protocol Version2-Control-plane GW Gateway HLR Home Location Register HO Handover HRPD High Rate Packet Data HSS Home Subscriber Server ETSI ETSI TS 103 202-2 V1.1.1 (2015-12)8 ID Identifier IE Information Element IETF Internet Engineering Task Force IMSI International Mobil
23、e Subscriber Identity IP Internet Protocol IP-CAN IP IP-Connectivity Access Network LTE Long Term Evolution MEI Mobile Equipment Identity MME Mobility Management Entity NAS Non Access Stratum Non-GBR Non-Guaranteed Bit Rate OAM Operation and Maintenance PCC Policy and Charging Control PCRF Policy an
24、d Charging Rules Function PDN Packet Data Network PDN-GW PDN-GateWay PDP Packet Date Protocol PMIP Proxy Mobile IP QCI Quality of Service Class Indicator QoS Quality of Service RRC Radio Resource Control S1 S1-Interface S1-AP S1-Application Part SGSN Serving GPRS Support Node S-GW Serving Gateway SN
25、 Sequence Number SRVCC Single Radio Voice Call Continuity TAD Traffic Aggregate Description TAI Tracking Area Identity TEID Tunnel End Point Identifier TFT Traffic Flow Template TP Test Purpose TSS Test Suite Structure UDP User Datagram Protocol UE User Equipment UE-AMBR UE-Aggregate Maximum Bit Rat
26、e UL Uplink UMTS Universal Mobile Telecommunication System UP User Plane UTRAN UMTS Terrestrial Radio Access Network 4 Test configurations 4.1 Introduction This clause lists the test equipment necessary to perform the test cases detailed in the present document, along with the network configurations
27、 required to execute all test cases included in the present document. ETSI ETSI TS 103 202-2 V1.1.1 (2015-12)9 4.2 Network or Bearer modification procedure as per Figure 19, from step 2 to 11, or as per Figure 20, from step 2 to 9; or Dedicated bearer deactivation procedure as per Figure 14, from st
28、ep 2 to 9. Comments: Messages 1, 2, and 5 are common for architecture variants with GTP-based S5/S8 and PMIP-based S5/S8. The messages identified as (A) differ in the case that PMIP-based S5/S8 is employed and is defined in ETSI TS 123 402 9. The Bearer Resource Command Procedure allows the UE to re
29、quest for a modification of bearer resources (e.g. allocation or release of resources) for one traffic flow aggregate with a specific QoS demand. Alternatively, the procedure allows the UE to request for the modification of the packet filters used for an active traffic flow aggregate, without changi
30、ng QoS. If accepted by the network, the request invokes either the Dedicated Bearer Activation Procedure, the Bearer Modification Procedure or a dedicated bearer is deactivated using the PDN-GW Initiated Bearer Deactivation Procedure. The deactivation procedure is used by the UE when the UE already
31、has a PDN connection with the PDN-GW. A UE can send a subsequent Request Bearer Resource Modification Message before the previous procedure is completed. ETSI ETSI TS 103 202-2 V1.1.1 (2015-12)17 5.2.3.4 Bearer Resource Failure Indication Procedure TP_TM_04 Standards Reference: ETSI TS 129 274 1, cl
32、ause 7.2.6 PICS item: Summary: Bearer Resource Failure Indication Procedure. Test purpose: A Bearer Resource Failure Indication shall be sent by the PDN-GW to an S-GW and forwarded to the MME to indicate failure of the UE requested bearer resource allocation procedure or UE requested bearer resource
33、 modification procedure. Test Procedure: 1) CORE, RAN, and one UE available. A simulation platform may be necessary to emulate the PDN-GW. 2) MME is configured with the GTP Tunnel Parameter. 3) S-GW is configured with the GTP Tunnel Parameter. 4) Verify IP connectivity between the two nodes. 5) The
34、resources or the memory in the PDN-GW are limited via the OAM interface in order to trigger the Bearer Resource Failure Indication. 6) Attach the UE. 7) The user changes the application being used on the UE. For example, the user changes the application being used on the UE from web browsing to FTP.
35、 Expected Results: 1) Verify that the MME sends a Bearer Resource Command to the S-GW. S-GW sends it to the PDN-GW (Simulation tool). 2) Verify that the PDN-GW sends back the Bearer Resource Failure Indication with cause value. 3) Verify that the S-GW sends the Bearer Resource Failure Indication to
36、the MME. Expected Message Flow: MME BEARER RESOURCE COMMAND S-GW BEARER RESOURCE FAILURE INDICATION Comments: Using an actual S-GW, the PDN-GW should be configured through the OAM interface to force it to send back a cause value of “No resources available“ or “No memory available“. Possible cause va
37、lues are: - “No resources available“. - “No memory available“. - “User authentication failed“. - “System failure“. - “Semantic error in the TAD operation“. - “Syntactic error in the TAD operation“. - “Semantic errors in packet filter(s)“. - “Syntactic errors in packet filter(s)“. - “Mandatory IE inc
38、orrect“. - “Mandatory IE missing“. - “Conditional IE missing“. - “Invalid message format“. - “Collision with network initiated request“. - “Invalid length“. - “Service denied“. If the requested QoS is not granted (i.e. the requested QoS cannot be accepted or resources could not be allocated) the PDN
39、-GW sends a Bearer Resource Failure Indication (with a cause indicating the reason why the request failed or was rejected) message, which is delivered to the UE. ETSI ETSI TS 103 202-2 V1.1.1 (2015-12)18 5.2.3.5 Delete Session Request Procedure TP_TM_05 Standards Reference: ETSI TS 129 274 1, clause
40、s 7.2.9.1, 7.2.10.1 ETSI TS 123 401 6, clause 5.3.8.2 PICS item: Summary: Delete Session Request Procedure. Test purpose: Check the exchange of Delete Session Request/Response after NAS Detach Request. Test Procedure: 1) EPC, RAN, and one UE is required. 2) MME is configured with GTP Tunnel Paramete
41、r. 3) S-GW is configured with the GTP Tunnel Parameter. 4) Verify IP connectivity between the two nodes. 5) UE attaches to network. 6) Switch off the UE to trigger the Detach procedure. Expected Results: 1) Verify that the MME sends the Delete Session Request to the S-GW. 2) Verify that the S-GW for
42、wards the Delete Session Request to the PDN-GW. 3) Verify that the PDN-GW sends back the Delete Session Response. 4) Verify that the S-GW sends the Delete Session Response to the MME. Possible cause values in the Delete Session Response are: - “Request accepted“. - “Context not found“. - “Mandatory
43、IE incorrect“. - “Conditional IE missing“. - “Invalid message format“. - “Unexpected repeated IE“. The cause value is used to inform the MME about the status of the Detach procedure. Expected Message Flow: (A) UE eNodeB MME Serving GW PDN GW PCRF 1. Detach Request 2. Delete Session Request 6. Delete
44、 Session Request 7. Delete Session Response 3. Delete Session Response 11. Detach Accept HSS SGSN 4. Detach Notification 5. Delete Session Request 9. Delete Session Response 10. Detach Ack 12. Signalling Connection Release 8. PCEF Initiated IP-CAN Session Termination g3Comments: For a PMIP-based S5/
45、S8, procedure steps (A) are defined in ETSI TS 123 402 9. Steps 6, 7 and 8 concern GTP based S5/S8. Only if the UE is on the MME will send the Detach Accept message in response to the Detach Request message. ETSI ETSI TS 103 202-2 V1.1.1 (2015-12)19 5.2.3.6 Delete Bearer Request Procedure TP_TM_06 S
46、tandards Reference: ETSI TS 129 274 1, clauses 7.2.9.2, 7.2.10.2 ETSI TS 123 401 6, clause 5.4.4 PICS item: Summary: Delete Bearer Request Procedure. Test purpose: Check the exchange of Delete Bearer Request/Response as part of the PDN-GW initiated bearer deactivation procedure. Test Procedure: 1) E
47、PC, RAN, and one UE available. 2) OAM access to PDN-GW database is required to modify QoS parameters. 3) MME is configured with the GTP Tunnel Parameter. 4) S-GW is configured with the GTP Tunnel Parameter. 5) Verify IP connectivity between two nodes. 6) UE attaches to network and is in the ECM-CONN
48、ECTED state. 7) Change a local QoS parameter for this UE. Expected Results: 1) Verify that the PDN-GW sends the Delete Bearer Request to the S-GW. 2) Verify that the S-GW forwards the Delete Bearer Request to the MME. 3) Verify that the MME sends back to the S-GW the Delete Bearer Response. 4) Verif
49、y that the S-GW sends the Delete Bearer Response to the PDN-GW. 5) Verify that the MME sends the Delete Bearer Response to the S-GW. Expected Message Flow: (A) 3b. Delete Bearer Request MME Serving GW PDN GW PCRF 5. RRC Connection Reconfiguration 2. Delete Bearer Request 6a. RRC Connection Reconfiguration complete 6b. Deactivate Bearer Response eNodeB UE 1. IP-CAN Session Modification 3a. Delete Bearer Request SGSN 7a. Direct Transfer 4b. Deactivate Bearer Request 4a. Detach Request 8b. Delete Bearer Response 8a. Delete Bearer Response
