Core Network and Interoperability Testing (INT); Message Waiting Indication (MWI) using IP Multimedia (IM) Core Network (CN) subsystem; Conformance Test Specification (3GPP™ Release 12); Part 2: Test Suite Structure and Test Purposes (TSS&TP)

RTS/INT-00154-2

General Information

Status
Published
Publication Date
27-Jun-2018
Current Stage
12 - Completion
Due Date
19-Jun-2018
Completion Date
28-Jun-2018
Ref Project

Buy Standard

Standard
ETSI TS 102 891-2 V4.1.1 (2018-06) - Core Network and Interoperability Testing (INT); Message Waiting Indication (MWI) using IP Multimedia (IM) Core Network (CN) subsystem; Conformance Test Specification (3GPP™ Release 12); Part 2: Test Suite Structure and Test Purposes (TSS&TP)
English language
21 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

ETSI TS 102 891-2 V4.1.1 (2018-06)






TECHNICAL SPECIFICATION
Core Network and Interoperability Testing (INT);
Message Waiting Indication (MWI) using
IP Multimedia (IM) Core Network (CN) subsystem;
Conformance Test Specification (3GPP™ Release 12);
Part 2: Test Suite Structure and Test Purposes (TSS&TP)

---------------------- Page: 1 ----------------------
2 ETSI TS 102 891-2 V4.1.1 (2018-06)



Reference
RTS/INT-00154-2
Keywords
conformance, MWI, SIP, testing, 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 2018.
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 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 102 891-2 V4.1.1 (2018-06)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 5
3 Definitions and abbreviations . 6
3.1 Definitions . 6
3.2 Abbreviations . 6
4 Test Suite Structure (TSS) . 6
4.0 Table of Test suite Structure. 6
4.1 Configuration . 6
5 Test Purposes (TP) . 8
5.1 Introduction . 8
5.1.1 TP naming convention . 8
5.1.2 Test strategy . 8
5.1.3 Reference column "MWI reference" . 8
5.2 Invocation and operation . 8
5.2.1 Actions at the UE . 8
5.2.2 Actions at the AS . 12
History . 21


ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 102 891-2 V4.1.1 (2018-06)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables 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 covering the Conformance Test Specification of Message
Waiting Indication (MWI) using IP Multimedia (IM) Core Network (CN) subsystem, as identified below:
Part 1: "Protocol Implementation Conformance Statement (PICS)";
Part 2: "Test Suite Structure and Test Purposes (TSS&TP)";
Part 3: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)
proforma specification".
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: 4 ----------------------
5 ETSI TS 102 891-2 V4.1.1 (2018-06)
1 Scope
The present document specifies the Test Suite Structure and Test Purposes (TSS&TP) of the Message Waiting
Indication (MWI) service, based on 3GPP stage three Protocol Description of the MWI service, based on stage one and
two of the ISDN MWI supplementary services.
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 124 606: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; Message Waiting Indication (MWI) using IP
Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.606
Release 12) ".
[2] ETSI TS 102 891-1: "Core Network and Interoperability Testing (INT); Message Waiting
Indication (MWI) using IP Multimedia (IM) Core Network (CN) subsystem; Conformance Test
Specification (3GPP™ Release 12); Part 1: Protocol Implementation Conformance Statement
(PICS)".
[3] IETF RFC 3842: "A Message Summary and Message Waiting Indication Event Package for the
Session Initiation Protocol (SIP)".
[4] IETF RFC 3265: "Session Initiation Protocol (SIP)-Specific Event Notification".
[5] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 1: General concepts".
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.
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 102 891-2 V4.1.1 (2018-06)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ETSI TS 124 606 [1] and the following
apply:
Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [5].
Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [5].
PICS pro forma: Refer to ISO/IEC 9646-1 [5].
point of control and observation: Refer to ISO/IEC 9646-1 [5].
Protocol Implementation Conformance Statement (PICS): Refer to ISO/IEC 9646-1 [5].
System Under Test (SUT): Refer to ISO/IEC 9646-1 [5].
Test Purpose (TP): Refer to ISO/IEC 9646-1 [5].
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI TS 124 606 [1] and the following apply:
ATS Abstract Test Suite
IUT Implementation Under Test
PICS Protocol Implementation Conformance Statement
SUT System Under Test
TP Test Purpose
TSS Test Suite Structure
TSS&TP Test Suite Structure and Test Purposes
4 Test Suite Structure (TSS)
4.0 Table of Test suite Structure
Table 1: Test Suite Structure (TSS)
UserEquipment
  MWI_U01_xxx
Network
AS_ServedUser MWI_N01_xxx

4.1 Configuration
The scope of the present document is to test the signalling and procedural aspects of the stage 3 requirements as
described in ETSI TS 124 606 [1]. The stage 3 description respects the requirements to several network entities and also
to requirements regarding to end devices. Therefore several interfaces (reference points) are addressed to satisfy the test
of the different entities.
Therefore to test the appropriate entities the configurations below are applicable:
Testing of the Application Server: This entity is responsible to perform the service. Hence the ISC interface is the
appropriate access point. Figure 1 points to this.
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 102 891-2 V4.1.1 (2018-06)

Figure 1: Applicable interface to test AS functionalities
If the ISC interface is not accessible it is also applicable to perform the test of the AS using any NNI (Mw, Mg, Mx)
interface (consider figure 2). In case only the Gm interface is accessible this shall be used instead. In this case, be aware
that the verification of several requirements is impeded.

Figure 2: Applicable interfaces to test using the (generic) NNI interface
Figure 3 illustrates the usage of any NNI interface.
Testing of User Equipment: There are several requirements regarding to the end devices. Therefore a special
configuration appears.

Figure 3: Applicable configuration to test the User Equipment
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 102 891-2 V4.1.1 (2018-06)
5 Test Purposes (TP)
5.1 Introduction
5.1.1 TP naming convention
TPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional references
are added to identify the actual test suite and whether it applies to the network or the user (see table 2).
Table 2: TP identifier naming convention scheme
Identifier: __
= supplementary service: e.g. "MWI"
= type of IUT: U User - equipment
N Network
= group 2 digit field representing group reference according to TSS
= 3 digit sequential number (001-999)

5.1.2 Test strategy
As the base standard ETSI TS 124 606 [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 102 891-1 [2]. The criteria applied include
the following:
• whether or not a test case can be built from the TP is not considered.
5.1.3 Reference column "MWI reference"
The column "MWI reference" makes reference to ETSI TS 124 606 [1], except where explicitly stated otherwise.
5.2 Invocation and operation
5.2.1 Actions at the UE
TSS TP MWI reference Selection expression
UserEquipment MWI_U01_001 4.7.2.1 PICS 4.5.1/1 AND
PICS 4.6.1/1
Test purpose:
Initial subscription for a public user identity using the public service identity

Ensure that the user equipment is able to subscribe to the MWI service. A SUBSCRIBE message is sent. The Request
line contains the public service identity of the MA. The Event header is set to 'message-summary', the Expires header
is set to a proper value, Accept header is set to 'application/simple-message-summary'.
SIP header: SUBSCRIBE sip: public service identity@server SIP/2.0
   Event: message-summary
   Expires:
   Accept: application/simple-message-summary
Comments:
User Equipment Test Equipment

SUBSCRIBE
 200 OK (SUBSCRIBE)

ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 102 891-2 V4.1.1 (2018-06)
TSS TP MWI reference Selection expression
UserEquipment MWI_U01_003 4.7.2.1, PICS 4.5.1/1
3.6/[3]
Test purpose:
Re-Subscription before subscription is expired

Ensure that the user equipment is able to re-subscribe the current subscription before the subscription expires. A
SUBSCRIBE message is sent. The Event header is set to 'message-summary', the Expires header is set to a proper
value, Accept header is set to 'application/simple-message-summary'. The Call-ID is equal to the Call-ID of the initial
subscription.
SIP header: SUBSCRIBE
   Event: message-summary
   Expires: 500
   Accept: application/simple-message-summary
Comments:
User Equipment Test Equipment
 SUBSCRIBE

200 OK (SUBSCRIBE)
Before subscription expires
 SUBSCRIBE

200 OK (SUBSCRIBE)

TSS TP MWI reference Selection expression
UserEquipment MWI_U01_004 4.7.2.1, PICS 4.5.1/1
3.6/[3]
Test purpose:
Subscription after re-subscription fails

Ensure that the user equipment is able to subscribe to the MWI service after a re-subscription failed. A SUBSCRIBE
message is sent. The Event header is set to 'message-summary', the Expires header is set to a proper value, Accept
header is set to 'application/simple-message-summary'.
SIP header: SUBSCRIBE 1
   Event: message-summary
   Expires: 500
   Accept: application/simple-message-summary
  SUBSCRIBE 2
   Call-ID:
   Event: message-summary
   Expires: 500

   Accept: application/simple-message-summary
Comments:
User Equipment Test Equipment
 SUBSCRIBE

200 OK (SUBSCRIBE)
Before subscription expires
 SUBSCRIBE 1

500

 SUBSCRIBE 2

200 OK (SUBSCRIBE)

ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 102 891-2 V4.1.1 (2018-06)
TSS TP MWI reference Selection expression
UserEquipment MWI_U01_005 4.7.2.1, PICS 4.5.1/1
3.1.4.3/[4]
Test purpose:
Unsubscribe from MWI service

Ensure that the user equipment is able to unsubscribe the current subscription. A SUBSCRIBE message is sent. The
Event header is set to 'message-summary', the Expires header is set to zero, Accept header is set to
'application/simple-message-summary'. The Call-ID is equal to the Call-ID of the initial subscription.
SIP header: SUBSCRIBE 2
   Event: message-summary
   Expires: 0
   Accept: application/simple-message-summary
Comments:
User Equipment Test Equipment
 SUBSCRIBE 1
 200 OK (SUBSCRIBE)

SUBSCRIBE 2
 200 OK (SUBSCRIBE)

TSS TP MWI reference Selection expression
UserEquipment MWI_U01_006 4.7.2.1, PICS 4.5.1/1
IETF RFC 3842 [3] 3.9
Test purpose:
Reception of status information after subscription

Upon receipt of a valid NOTIFY request after subscription, the user equipment accepts the information and sends a
200 OK response [4].
SIP header: NOTIFY
   Event: message-summary
   Subscription-State: active
   Content-Type: application/simple-message-summary

   Messages-Waiting: yes
   Message-Account: sip:served_user@Server
   Voice-Message: 4/1 (2/0)
   Video-Mess
...

Questions, Comments and Discussion

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