Core Network and Interoperability Testing (INT); S1AP Conformance Testing for the S1-MME interface; (3GPPTM Release 13); Part 2: Test Suite Structure (TSS) and Test Purposes (TP)

DTS/INT-00135-2

General Information

Status
Published
Publication Date
19-Jul-2017
Current Stage
12 - Completion
Due Date
18-Jul-2017
Completion Date
20-Jul-2017
Ref Project

Buy Standard

Standard
ETSI TS 103 497-2 V1.1.1 (2017-07) - Core Network and Interoperability Testing (INT); S1AP Conformance Testing for the S1-MME interface; (3GPPTM Release 13); Part 2: Test Suite Structure (TSS) and Test Purposes (TP)
English language
90 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

ETSI TS 103 497-2 V1.1.1 (2017-07)






TECHNICAL SPECIFICATION
Core Network and Interoperability Testing (INT);
S1AP Conformance Testing for the S1-MME interface;
(3GPP™ Release 13);
Part 2: Test Suite Structure (TSS) and Test Purposes (TP)

---------------------- Page: 1 ----------------------
2 ETSI TS 103 497-2 V1.1.1 (2017-07)



Reference
DTS/INT-00135-2
Keywords
conformance, S1AP, TSS&TP

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
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (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
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2017.
All rights reserved.

TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members.
GSM® and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI TS 103 497-2 V1.1.1 (2017-07)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 7
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 7
4 Test configurations . 7
4.1 Introduction . 7
4.2 Test configuration using the S1-MME interface . 8
5 Test Suite Structure (TSS) and Test Purposes (TP) . 9
5.1 Test Suite Structure . 9
5.1.1 TP naming convention . 9
5.1.2 Test strategy . 9
5.1.3 TP structure . 9
5.2 Test Purposes . 10
5.2.1 PICS references . 10
5.2.2 S1_MME interface . 10
5.2.2.1 eNB Role . 10
5.2.2.1.1 Test selection . 10
5.2.2.1.2 E-RAB management group . 11
5.2.2.1.3 Context management group . 26
5.2.2.1.4 Handover signalling group . 35
5.2.2.1.5 Paging group . 42
5.2.2.1.6 NAS transport group . 42
5.2.2.1.7 Management group . 43
5.2.2.1.8 S1 CDMA 2000 tunnelling group. 45
5.2.2.1.9 UE capability info indication group . 46
5.2.2.1.10 Trace group . 46
5.2.2.1.11 Location reporting group . 47
5.2.2.1.12 Warning message transmission group . 49
5.2.2.1.13 eNB direct information transfer group . 50
5.2.2.1.14 MME direct information transfer group . 50
5.2.2.1.15 eNB configuration transfer group . 51
5.2.2.1.16 MME configuration transfer group . 51
5.2.2.1.17 LPPa transport group . 51
5.2.2.1.18 Unknown, Unforseen and Erroneous Protocol Data group . 52
5.2.2.2 MME Role. 57
5.2.2.2.1 Test selection . 57
5.2.2.2.2 E-RAB management group . 58
5.2.2.2.3 Context management group . 63
5.2.2.2.4 Handover signalling group . 67
5.2.2.2.5 Paging group . 77
5.2.2.2.6 NAS transport group . 77
5.2.2.2.7 Management group . 78
5.2.2.2.8 S1 CDMA 2000 tunnelling group. 81
5.2.2.2.9 UE capability info indication group . 81
5.2.2.2.10 Trace group . 82
5.2.2.2.11 Location reporting group . 83
5.2.2.2.12 Warning message transmission group . 84
5.2.2.2.13 eNB direct information transfer group . 84
ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 103 497-2 V1.1.1 (2017-07)
5.2.2.2.14 MME direct information transfer group . 85
5.2.2.2.15 eNB configuration transfer group . 85
5.2.2.2.16 MME configuration transfer group . 85
5.2.2.2.17 LPPa transport group . 85
5.2.2.2.18 Unknown, Unforseen and Erroneous Protocol Data group . 86
History . 90

ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 103 497-2 V1.1.1 (2017-07)
Intellectual Property Rights
Essential patents
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 (https://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 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.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
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 multi-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 Drafting 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

---------------------- Page: 5 ----------------------
6 ETSI TS 103 497-2 V1.1.1 (2017-07)
1 Scope
The present document provides the Test Suite Structure (TSS) and Test Purposes (TP) for the test specification for the
S1AP protocol on the S1-MME interface as specified in ETSI TS 136 413 [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 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
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
https://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 the application of the present document.
[1] ETSI TS 136 413 (V13.4.0): "LTE; Evolved Universal Terrestrial Radio Access Network
(E-UTRAN); S1 Application Protocol (S1AP) (3GPP TS 36.413 version 13.4.0 Release 13)".
[2] ETSI TS 103 497-1: "Core Network and Interoperability Testing (INT); S1AP Conformance
Testing for the S1-MME interface; (3GPPTM Release 13); Part 1: Protocol Implementation
Conformance Statement (PICS)".
[3] ISO/IEC 9646-1: "Information technology -- Open Systems Interconnection -- Conformance
testing 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); Protocol and profile
conformance testing specifications; Standardization methodology".
[6] ETSI TS 123 203: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal
Mobile Telecommunications System (UMTS); LTE; Policy and charging control architecture
(3GPP TS 23.203)".
[7] ETSI TS 125 413: "Universal Mobile Telecommunications System (UMTS); UTRAN Iu interface
Radio Access Network Application Part (RANAP) signalling (3GPP TS 25.413)".
[8] ETSI TS 148 018: "Digital cellular telecommunications system (Phase 2+) (GSM); General Packet
Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN); BSS
GPRS protocol (BSSGP) (3GPP TS 48.018)".
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 103 497-2 V1.1.1 (2017-07)
2.2 Informative references
References 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
referenced document (including any amendments) applies.
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 not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
Not applicable.
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ETSI TS 136 413 [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 Under 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 136 413 [1] and the following apply:
TP Test Purpose
TSS Test Suite Structure
4 Test configurations
4.1 Introduction
Test purposes of the present document address the VoLTE functional entities eNB and MME that are accessible via the
standardized S1-MME interface.
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 103 497-2 V1.1.1 (2017-07)
4.2 Test configuration using the S1-MME interface
The S1-MME interface is located between the eNB and the MME.
SUT or
TS or
(TS)
(SUT)
S1-MME
eNB
MME

Figure 1: Test configuration CF_S1-MME
SUT or
TS or
(TS)
(SUT)
source eNB
S1-MME
MME
S1-MME
target eNB

Figure 2: Test configuration CF_2S1-MME
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 103 497-2 V1.1.1 (2017-07)
5 Test Suite Structure (TSS) and Test Purposes (TP)
5.1 Test Suite Structure
5.1.1 TP naming convention
TPs are numbered, starting at 01, within each group. Groups are organized according to the TSS.
Table 1: TP identifier naming convention scheme
Identifier: ___
= Test Purpose: fixed to "TP"
Interface or protocol: S1AP
= type of IUT: ENB or MME
= group RAB E-RAB Management procedures
CMP Context Management procedures
HAS Handover Signalling
PAG Paging
NAS NAS transport
MNP Management procedures
STP S1 CDMA2000 Tunnelling Procedures
UEC UE Capability Info Indication
TRP Trace Procedures
LRP Location Reporting Procedures
WTP Warning Message Transmission Procedures
EIT eNB Direct Information Transfer
MIT MME Direct Information Transfer
ECT eNB Configuration Transfer
MCT MME Configuration Transfer
LPP LPPa transport
ERR Unknown, Unforseen and Erroneous Protocol Data

= sequential number (01 to 99)

5.1.2 Test strategy
As the base specification in ETSI TS 136 413 [1] contains no explicit requirements for testing, the TPs were generated
as a result of an analysis of the base standard and the PICS specification ETSI TS 103 497-1 [2].
5.1.3 TP structure
Each TP has been written in a manner which is consistent with all other TPs. The intention of this is to make the TPs
more readable and checkable. A particular structure has been used which is illustrated in Table 2. Table 2 should be
read in conjunction with any TP, i.e. please use a TP as an example to facilitate the full comprehension of Table 2.
ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 103 497-2 V1.1.1 (2017-07)
Table 2: Structure of a single TP
TP part Text Example
Header see Table 1
clause 8.2.1.1
A.2/3
Summary Short free text description of the test objective Verify that the IUT can successfully
process all mandatory IEs in a E-
RAB_SETUP_REQUEST received due
to establishment-RAB management
procedure.
Configuration Test configuration as described in clause 4.2 CF_S1-MME
Initial Free text description of the condition that the IUT has
condition reached before the test purpose applies.
(optional)
Start point Ensure that the IUT in the Handover Preparation

see ETSI TS 136 413 [1], clause 8.1 having sent a HANDOVER_REQUIRED
and/or further actions before stimulus
if the action is sending/receiving
  see below for message structure
Stimulus , see below for message structure on receipt of a
HANDOVER_COMMAND (see note 2)
or
Reaction . sends, saves, does, etc.
if the action is sending
  see below for message structure
, etc.
Message Message exchange, etc. (see note 2)
structure

a) containing a(n) IE (see note 4)
b) indicating
and back to a) or b) (see note 3)
NOTE 1: Text in italics will not appear in TPs and text between <> is filled in for each TP and may differ from one
TP to the next.
NOTE 2: All messages are considered as "valid and compatible" unless otherwise specified in the test purpose.
This includes the presence of all mandatory IEs as specified in ETSI TS 136 413 [1].
NOTE 3: An IE can be embedded into another IE. This is expressed by indentations, e.g. if Message1 contains IE1
and IE2 where IE1 has IE3 embedded this will be expressed like this:
sends/receives Message 1
 containing IE1
  containing IE3
  indicating .
 containing IE2
  indicating .
NOTE 4: IE value fields used for e.g. identification or address should be equal in the scope of TP if not stated
otherwise.

5.2 Test Purposes
5.2.1 PICS references
All PICS items referred to in this clause are as specified in ETSI TS 103 497-1 [2] unless indicated otherwise by
another numbered reference. PICS items are only meant for test selection, therefore only PICS items with status
optional or conditional are explicitly mentioned.
5.2.2 S1_MME interface
5.2.2.1 eNB Role
5.2.2.1.1 Test selection
The IUT takes the role of the eNB; PICS A.2/1.
ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 103 497-2 V1.1.1 (2017-07)
5.2.2.1.2 E-RAB management group
TP_S1AP_ENB_RAB_01 Standards Reference: PICS item:
st
Clauses 8.2.1.2 (1 dashed line in PICS A.3/1.1
th
5 dashed list) and
9.1.3.1 and 9.1.3.2
Summary: Verify that the IUT can successfully process all mandatory IEs in an
E-RAB_SETUP_REQUEST received due to E-RAB management procedure and
send E-RAB_SETUP_RESPONSE with successfully established E-RABs included in
the E-RAB_Setup_List IE
Configuration:
CF_S1-MME
Test purpose:
Ensure that the IUT
on receipt of an E-RAB_SETUP_REQUEST
 containing an MME_UE_S1AP_ID
 containing an eNB_UE_S1AP_ID
 containing an E-RAB_to_be_Setup_List
  containing an E-RAB_to_be_Setup Item 1
  containing an E-RAB_ID
  containing an E-RAB_Level_QoS_Parameters
   containing QCI
   indicating value 5
  containing a Transport_Layer_Address
  containing a GTP-TEID
  containing a NAS-PDU
sends an E-RAB_SETUP_RESPONSE
 containing an MME_UE_S1AP_ID
 containing an eNB_UE_S1AP_ID
 containing an E-RAB_Setup_List
  containing an E-RAB_Setup Item 1
  containing an E-RAB_ID
  containing a Transport_Layer_Address
  containing a GTP-TEID
Comments:


ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 103 497-2 V1.1.1 (2017-07)
TP_S1AP_ENB_RAB_02 Standards Reference: PICS item:
nd
Clauses 8.2.1.2 (2 dashed line in PICS A.3/1.1
th
5 dashed list) and
9.1.3.1 and 9.1.3.2
Summary:
Verify that the IUT after receiving an E-RAB_SETUP_REQUEST with failed E-RAB
sends an E-RAB_SETUP_RESPONSE with E-RAB_Failed_to_Setup_List
Configuration: CF_S1-MME
Test purpose: Ensure that the IUT
on receipt of an E-RAB_SETUP_REQUEST
 containing an MME_UE_S1AP_ID
 containing an eNB_UE_S1AP_ID
 containing an E-RAB_to_be_Setup_List
  containing an E-RAB_to_be_Setup Item 1
  containing an E-RAB_ID
   indicating value A
  containing an E-RAB_Level_QoS_Parameters
  containing a Transport_Layer_Address
  containing a GTP-TEID
  containing a NAS-PDU
  containing an E-RAB_to_be_Setup Item 2(not acceptable data for eNB)
  containing an E-RAB_ID
   indicating value B(different to value A)
  containing an E-RAB_Level_QoS_Parameters
   containing QCI
   indicating not supported QCI value(255)
  containing a Transport_Layer_Address
  containing a GTP-TEID
  containing a NAS-PDU
sends an E-RAB_SETUP_RESPONSE
 containing an MME_UE_S1AP_ID
 containing an eNB_UE_S1AP_ID
 containing an E-RAB_Setup_List
  containing an E-RAB_Setup Item 1
  containing an E-RAB_ID
   indicating value A
  containing a Transport_Layer_Address
  containing a GTP-TEID
 containing an E-RAB_Failed_to_Setup_List
  containing an E-RAB_List Item 1
  containing an E-RAB_ID
   indicating value B
  containing a Cause
   indicating 'not-supported-QCI-value'
Comments:


ETSI

---------------------- Page: 12 ----------------------
13 ETSI TS 103 497-2 V1.1.1 (2017-07)
TP_S1AP_ENB_RAB_03 Standards Reference: PICS item:
rd
Clauses 8.2.1.2 (3 numbered list) PICS A.3/1.1.1
and 9.1.3.1 and 9.1.3.2
Summary: Verify that the IUT if it is interacted with handover preparation procedure sends
E-RAB_SETUP_RESPONSE with appropriate cause value and continue with
handover preparation procedure
Configuration: CF_S1-MME
Test purpose: Ensure that the IUT
on receipt of an E-RAB_SETUP_REQUEST
 containing an MME_UE_S1AP_ID
 containing an eNB_UE_S1AP_ID
 containing an E-RAB_to_be_Setup_List
  containing an E-RAB_to_be_Setup Item 1
  containing an E-RAB_ID
  containing an E-RAB_Level_QoS_Parameters
  containing a Transport_Layer_Address
  containing a GTP-TEID
  containing a NAS-PDU
sends an E-RAB_SETUP_RESPONSE
 containing an MME_UE_S1AP_ID
 containing an eNB_UE_S1AP_ID
 containing an E-RAB_Failed_to_Setup_List
  containing an E-RAB_List Item 1
  containing an E-RAB_ID
  containing a Cause
   indicating 'S1 intra system Handover triggered' or
   indicating 'S1 inter system Handover triggered' or
   indicating 'X2 Handover triggered'
sends a HANDOVER_REQUIRED
 containing an MME_UE_S1AP_ID
 containing an eNB_UE_S1AP_ID
 containing a Handover_Type
  indicating LTEtoUTRAN
 containing a Cause
 containing a Target ID
 containing a Source_to_Target_Transparent_Container
  containing a Source RNC_to_Target RNC_Transparent_Container
  indicating a UE History Information
Comments:


ETSI

---------------------- Page: 13 ----------------------
14 ETSI TS 103 497-2 V1.1.1 (2017-07)
TP_S1AP_ENB_RAB_04 Standards Reference: PICS item:
Clauses 8.2.1.4 ¶ 1, PICS A.3/1.1
9.1.3.1 and 9.1.3.2
ETSI TS 123 203 [6], Table 6.1.7
Summary: Verify that the IUT on receipt of an E-RAB_SETUP_REQUEST message containing
an E-RAB Level QoS Parameters IE which contains a QCI IE indicating a GBR
bearer and which does not contain the GBR QoS Information IE sends an
E-RAB_SETUP_RESPONSE with failed E-RAB
Configuration:
CF_S1-MME
Test purpose:
Ensure that the IUT
on receipt of an E-RAB_SETUP_REQUEST
 containing an MME_UE_S1AP_ID
 containing an eNB_UE_S1AP_ID
 containing an E-RAB_to_be_Setup_List
  containing an E-RAB_to_be_Setup Item 1
  containing an E-RAB_ID
  containing an E-RAB_Level_QoS_Parameters
   containing QCI
   indicating GBR bearer
   not containing GBR QoS Information
  containing a Transport_Layer_Address
  containing a GTP-TEID
  containing a NAS-PDU
sends an E-RAB_SETUP_RESPONSE
 containing an MME_UE_S1AP_ID
 containing an eNB_UE_S1AP_ID
 containing an E-RAB_Failed_to_Setup_List
  containing an E-RAB_List Item 1
  containing an E-RAB_ID
  containing a Cause
   indicating an appropriate cause value
Comments:

ETSI

---------------------- Page: 14 ----------------------
15 ETSI TS 103 497-2 V1.1.1 (2017-07)
TP_S1AP_ENB_RAB_05 Standards Reference: PICS item:
Clauses 8.2.1.4 ¶ 2, PICS A.3/1.1
9.1.3.1 and 9.1.3.2
Summary: Verify that the IUT on receipt of an E-RAB_SETUP_REQUEST message containing
several E-RABs set to the same value sends an E-RAB_SETUP_RESPONSE with
failed E-RABs
Configuration: CF_S1-MME
Test purpose: Ensure that the IUT
on receipt of an E-RAB_SETUP_REQUEST
 containing an MME_UE_S1AP_ID
 containing an eNB_UE_S1AP_ID
 containing an E-RAB_to_be_Setup_List
  containing an E-RAB_to_be_Setup Item 1
  containing an E-RAB_ID
   indicating value A
  containing an E-RAB_Level_QoS_Parameters
  containing a Transport_Layer_Address
  containing a GTP-TEID
  containing a NAS-PDU
  containing an E-RAB_to_be_Setup Item 2
  containing an E-RAB_ID
   indicating value A
  containing an E-RAB_Level_QoS_Parameters
  containing a Transport_Layer_Address
  containing a GTP-TEID
  containing a NAS-PDU
sends an E-RAB_SETUP_RESPONSE
 containing an MM
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.