ETSI TS 101 553-1 V2.1.1 (2016-09)

ETSI TS 101 553-1 V2.1.1 (2016-09)






TECHNICAL SPECIFICATION
Core Network and Interoperability Testing (INT);
Testing of the IBCF requirements;
(3GPP Release 12);
Part 1: Protocol Implementation Conformance
Statement (PICS)

---------------------- Page: 1 ----------------------
2 ETSI TS 101 553-1 V2.1.1 (2016-09)



Reference
RTS/INT-00133-1
Keywords
IBCF, PICS, SIP, testing
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

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

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

Important notice
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.

© European Telecommunications Standards Institute 2016.
All rights reserved.

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

---------------------- Page: 2 ----------------------
3 ETSI TS 101 553-1 V2.1.1 (2016-09)
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 . 8
3 Definitions, symbols and abbreviations . 8
3.1 Definitions . 8
3.2 Symbols . 8
3.3 Abbreviations . 8
4 Conformance to this PICS proforma specification . 9
5 PICS proforma for ETSI TS 124 229 . 9
5.0 Introduction . 9
5.1 Guidance for completing the PICS proforma . 9
5.2 Purposes and structure . 9
5.3 Abbreviations and conventions . 10
5.4 Instructions for completing the PICS proforma. 10
6 Identification of the implementation . 11
6.0 Introduction . 11
6.1 Date of the statement . 11
6.2 Implementation Under Test (IUT) identification . 11
6.3 System Under Test (SUT) identification . 11
6.4 Product supplier . 11
6.5 Client (if different from product supplier) . 12
6.6 PICS contact person . 13
6.7 Global statement of conformance . 13
7 Statement of conformance to ETSI TS 124 229 and ETSI TS 129 165 . 13
7.1 Roles . 13
7.2 IBCF capabilities . 14
Annex A (informative): Bibliography . 20
History . 21

ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 101 553-1 V2.1.1 (2016-09)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (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.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Core Network and Interoperability
Testing (INT).
The present document is part 1 of a multi-part deliverable covering the Testing of the IBCF requirements, as identified
below:
Part 1: "Protocol Implementation Conformance Statement (PICS)";
Part 2: "Test Suite Structure and Test Purposes (TSS&TP)".
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 101 553-1 V2.1.1 (2016-09)
1 Scope
The present document covers the Protocol Implementation Conformance Statement of testing the IBCF requirements.
The focus is the Ic interface as the interconnection point between two network operators.
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 229: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; IP multimedia call control protocol based on Session
Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3
(3GPP TS 24.229 Release 9)".
[2] ETSI TS 129 165: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; Inter-IMS Network to Network Interface (NNI)
(3GPP TS 29.165 Release 9)".
[3] IETF RFC 3261: "SIP: Session Initiation Protocol".
[4] ETSI TS 124 407: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; TISPAN; PSTN/ISDN simulation services;
Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR);
Protocol specification (3GPP TS 24.407 Release 8)".
[5] ETSI TS 124 508: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; PSTN/ISDN simulation services Terminating
Identification Presentation (TIP) and Terminating Identification Restriction (TIR); Protocol
specification (3GPP TS 24.508 Release 8)".
[6] ETSI TS 124 505: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; TISPAN; PSTN/ISDN simulation services:
Conference (CONF); Protocol specification (3GPP TS 24.505 Release 8)".
[7] ETSI TS 124 406: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; TISPAN; PSTN/ISDN simulation services; Message
Waiting Indication (MWI): Protocol specification (3GPP TS 24.406 Release 8)".
[8] ETSI TS 124 410 (V8.0.0): "Digital cellular telecommunications system (Phase 2+); Universal
Mobile Telecommunications System (UMTS); TISPAN; NGN Signalling Control Protocol;
Communication HOLD (HOLD) PSTN/ISDN simulation services; Protocol specification (3GPP
TS 24.410 version 8.0.0 Release 8)".
[9] ETSI TS 124 411: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; TISPAN; PSTN/ISDN simulation services:
Anonymous Communication Rejection (ACR) and Communication Barring (CB); Protocol
specification (3GPP TS 24.411 Release 8)".
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 101 553-1 V2.1.1 (2016-09)
[10] ETSI TS 124 516: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; TISPAN; PSTN/ISDN simulation services;
Malicious Communication Identification (MCID); Protocol specification
(3GPP TS 24.516 Release 8)".
[11] ETSI TS 124 529: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; TISPAN; PSTN/ISDN simulation services: Explicit
Communication Transfer (ECT); Protocol specification (3GPP TS 24.529 Release 8)".
[12] ETSI TS 124 454: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; TISPAN; PSTN/ISDN simulation services; Protocol
specification Closed User Group (CUG) (3GPP TS 24.454 Release 8)".
[13] ETSI TS 123 002: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; Network architecture (3GPP TS 23.002 Release 9)".
[14] ETSI TS 123 228: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; IP Multimedia Subsystem (IMS); Stage 2
(3GPP TS 23.228 Release 9)".
[15] IETF RFC 4244: "An Extension to the Session Initiation Protocol (SIP) for Request History
Information".
[16] IETF RFC 3325: "Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity
within Trusted Networks".
[17] ETSI TS 129 658: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; SIP Transfer of IP Multimedia Service Tariff
Information; Protocol specification (3GPP TS 29.658)".
[18] ETSI TS 129 162: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; Interworking between the IM CN subsystem and IP
networks (3GPP TS 29.162)".
[19] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 1: General concepts".
[20] ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 7: Implementation Conformance Statements".
[21] IETF RFC 4412: "Communications Resource Priority for the Session Initiation Protocol (SIP)".
[22] IETF RFC 5626: "Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)".
[23] IETF RFC 6442: "Location Conveyance for the Session Initiation Protocol".
[24] IETF RFC 6086: "Session Initiation Protocol (SIP) INFO Method and Package Framework".
[25] IETF RFC 3911: "The Session Initiation Protocol (SIP) "Join" Header".
[26] IETF RFC 5393: "Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP)
Forking Proxies".
[27] IETF RFC 4028: "Session Timers in the Session Initiation Protocol (SIP)".
[28] IETF RFC 3265: "Session Initiation Protocol (SIP)-Specific Event Notification".
[29] IETF RFC 5373: "Requesting Answering Modes for the Session Initiation Protocol (SIP)".
[30] IETF RFC 6809: "Mechanism to Indicate Support of Features and Capabilities in the Session
Initiation Protocol (SIP)".
[31] IETF RFC 3455: "Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP)
for the 3rd-Generation Partnership Project (3GPP)".
[32] IETF RFC 7433: "A Mechanism for Transporting User-to-User Call Control Information in SIP".
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 101 553-1 V2.1.1 (2016-09)
[33] IETF RFC 5002: "The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)".
[34] IETF RFC 5502: "The SIP P-Served-User Private-Header (P-Header) for the 3GPP IP Multimedia
(IM) Core Network (CN) Subsystem".
[35] IETF RFC 6050: "A Session Initiation Protocol (SIP) Extension for the Identification of Services".
[36] IETF RFC 5009: "Private Header (P-Header) Extension to the Session Initiation Protocol (SIP) for
Authorization of Early Media".
[37] IETF RFC 4457: "The Session Initiation Protocol (SIP) P-User-Database Private-Header (P-
Header)".
[38] IETF RFC 3841: "Caller Preferences for the Session Initiation Protocol (SIP)".
[39] IETF RFC 5360: "A Framework for Consent-Based Communications in the Session Initiation
Protocol (SIP)".
[40] IETF RFC 4964: "The P-Answer-State Header Extension to the Session Initiation Protocol for the
Open Mobile Alliance Push to Talk over Cellular".
[41] IETF RFC 7316: "The Session Initiation Protocol (SIP) P-Private-Network-Indication Private
Header (P-Header)".
[42] IETF RFC 5318: "The Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header
(P-Header)".
[43] IETF RFC 3327: "Session Initiation Protocol (SIP) Extension Header Field for Registering Non-
Adjacent Contacts".
[44] IETF RFC 6794: "A Framework for Session Initiation Protocol (SIP) Session Policies".
[45] IETF RFC 3262: "Reliability of Provisional Responses in the Session Initiation Protocol (SIP)".
[46] IETF RFC 3326: "The Reason Header Field for the Session Initiation Protocol (SIP)".
[47] IETF RFC 3892: "The Session Initiation Protocol (SIP) Referred-By Mechanism".
[48] IETF RFC 4488: "Suppression of Session Initiation Protocol (SIP) REFER Method Implicit
Subscription".
[49] IETF RFC 3515: "The Session Initiation Protocol (SIP) Refer Method".
[50] IETF RFC 3891: "The Session Initiation Protocol (SIP) "Replaces" Header".
[51] IETF RFC 3311: "The Session Initiation Protocol (SIP) UPDATE Method".
[52] IETF RFC 3428: "Session Initiation Protocol (SIP) Extension for Instant Messaging".
[53] IETF RFC 3608: " Session Initiation Protocol (SIP) Extension Header Field for Service Route
Discovery During Registration ".
[54] IETF RFC 7329: "A Session Identifier for the Session Initiation Protocol (SIP) ".
[55] IETF RFC 3903: "Session Initiation Protocol (SIP) Extension for Event State Publication".
[56] IETF RFC 5839: "An Extension to Session Initiation Protocol (SIP) Events for Conditional Event
Notification".
[57] IETF RFC 4538: "Request Authorization through Dialog Identification in the Session Initiation
Protocol (SIP)".
[58] IETF RFC 2976: "The SIP INFO Method".
[59] IETF RFC 3323: "A Privacy Mechanism for the Session Initiation Protocol (SIP)".
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 101 553-1 V2.1.1 (2016-09)
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, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in [1] to [21] and the following apply:
Back-to-Back User Agent (B2BUA): As given in IETF RFC 3261 [3].
NOTE: In addition, for the usage in the IM CN subsystem, a SIP element being able to handle a collection of "n"
User Agents (behaving each one as UAC and UAS, according to SIP rules), which are linked by some
application logic that is fully independent of the SIP rules.
PICS proforma: document, in the form of a questionnaire, which when completed for an implementation or system
becomes a PICS
Protocol ICS (PICS): ICS for an implementation or system claimed to conform to a given protocol specification
Protocol Implementation Conformance Statement (PICS): statement made by the supplier of an implementation or
system claimed to conform to a given protocol specification, stating which capabilities have been implemented
roaming: UE is in a geographic area that is outside the serving geographic area of the home IM CN subsystem
topology hiding: limiting the amount of topology information given to external parties
3.2 Symbols
For the purposes of the present document, the symbols given in [1] to [21] apply.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in [1] to [21] and the following apply:
ACR Anonymous Communication Rejection
AOC Advice Of Charge
B2BUA Back-to-Back User Agent
CB Communication Barring
CCBS Call Completion on Busy Subscriber
CCNR Call Completion on No Reply
CDIV Communication DIVersion
CN Core Network
CONF Conference using IP Multimedia (IM) Core Network (CN) subsystem
CUG Closed User Group
CW Communication Waiting
ECT Explicit Communication Transfer
HOLD Communication Hold
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 101 553-1 V2.1.1 (2016-09)
IBCF Interconnect Border Control Function
ICS Implementation Conformance Statement
IM IP Multimedia
IMS IP Multimedia Subsystem
IMS-ALG IMS Application Level Gateway
INT Core Network and Interoperability Testing
IP Internet Protocol
IUT Implementation Under Test
MCID Mallicious Call IDentification
MIME Multipurpose Internet Mail Extensions
MWI Message Waiting Indication
OIP/OIR Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR)
PICS Protocol ICS
SIP Session Initiation Protocol
SUT System Under Test
TCP Transmission Control Protocol
TIP/TIR Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR)
using IP Multimedia (IM) Core Network (CN) subsystem
TS Technical Specification
UAC User Agent Client
UAS User Agent Server
UDP User Datagram Protocol
UE User Equipment
4 Conformance to this PICS proforma specification
If it claims to conform to the present document, the actual PICS proforma to be filled in by a supplier shall be
technically equivalent to the text of the PICS proforma given in clause 4, and shall preserve the numbering/naming and
ordering of the proforma items.
A PICS which conforms to the present document shall be a conforming PICS proforma completed in accordance with
the guidance for completion given in clause 5.1.
5 PICS proforma for ETSI TS 124 229
5.0 Introduction
Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that
users of the present document may freely reproduce the PICS proforma in clause 7 so that it can be used for its intended
purposes and may further publish the completed PICS.
5.1 Guidance for completing the PICS proforma
5.2 Purposes and structure
The purpose of this PICS proforma is to provide a mechanism whereby a supplier of an implementation of the
requirements defined in ETSI TS 124 229 [1] may provide information about the implementation in a standardized
manner.
The PICS proforma is subdivided into clauses for the following categories of information:
• guidance for completing the PICS proforma;
• identification of the implementation;
• global statement of conformance;
ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 101 553-1 V2.1.1 (2016-09)
• roles;
• IBCF capabilities.
5.3 Abbreviations and conventions
The PICS proforma contained in this annex is comprised of information in tabular form in accordance with the
guidelines presented in ISO/IEC 9646-7 [20].
Item column
The item column contains a number which identifies the item in the table.
Item description column
The item description column describes in free text each respective item (e.g. parameters, timers, etc.). It implicitly
means "is supported by the implementation?".
Status column
The following notations, defined in ISO/IEC 9646-7 [20], are used for the status column:
m mandatory - the capability is required to be supported.
o optional - the capability may be supported or not.
n/a not applicable - in the given context, it is impossible to use the capability.
o.i qualified optional - for mutually exclusive or selectable options from a set. "i" is an integer which
identifies an unique group of related optional items and the logic of their selection which is
defined immediately following the table.
ci conditional - the requirement on the capability ("m", "o", "x" or "n/a") depends on the support of
other optional or conditional items. "i" is an integer identifying an unique conditional status
expression which is defined immediately following the table.
Reference column
The reference column makes reference to ETSI TS 124 229 [1], except where explicitly stated otherwise.
Support column
The support column shall be filled in by the supplier of the implementation. The following common notations, defined
in ISO/IEC 9646-7 [20], are used for the support column:
Y or y supported by the implementation.
N or n not supported by the implementation.
N/A, n/a or - no answer required (allowed only if the status is n/a, directly or after evaluation of a conditional
status).
5.4 Instructions for completing the PICS proforma
The supplier of the implementation shall complete the PICS proforma in each of the spaces provided. In particular, an
explicit answer shall be entered, in each of the support or supported column boxes provided, using the notation
described in clause 5.3.
If necessary, the supplier may provide additional comments in space at the bottom of the tables or separately.
More detailed instructions are given at the beginning of the different clauses of the PICS proforma.
ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 101 553-1 V2.1.1 (2016-09)
6 Identification of the implementation
6.0 Introduction
Identification of the Implementation Under Test (IUT) and the system in which it resides (the System Under Test
(SUT)) should be filled in so as to provide as much detail as possible regarding version numbers and configuration
options.
The product supplier information and client information should both be filled in if they are different.
A person who can answer queries regarding information supplied in the ICS should be named as the contact person.
6.1 Date of the statement
.
6.2 Implementation Under Test (IUT) identification
IUT name:
.
.
IUT version:
.
6.3 System Under Test (SUT) identification
SUT name:
.
.
Hardware configuration:
.
.
.
Operating system:
.
6.4 Product supplier
Name:
.
ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 101 553-1 V2.1.1 (2016-09)
Address:
.
.
.
...