ETSI TS 102 027-2 V4.1.1 (2006-07)
2022/8/16
Read ETSI TS 102 027 TS series 系列阅读笔记之:
ETSI TS 102 027-2 V4.1.1 (2006-07)
Methods for Testing and Specification (MTS);
Conformance Test Specification for SIP (IETF RFC 3261);
Part 2: Test Suite Structure and Test Purposes (TSS&TP)
看起来，就是列举了测试套件结构以及所有的测试目的，可以用来指导设计测试案例.
1 Scope
The present document provides a Test Suite Structure and Test Purposes (TSS&TP) for the Session Initiation Protocol
(SIP) implementation in compliance with the relevant requirements specified in RFC 3261 [1].
本文档提供 SIP 协议实现一致性测试套件结构以及测试目的。
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ATS Abstract Test Suite
CE Call Establishment
CR Call Release
I Invalid
IUT Implementation Under Test
MG MessaGing
O inOpportune
OE Originating Endpoint
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
PR PRoxy
RD ReDirect server
RG ReGistration
RR RegistraR
RT RegistranT
SIP Session Initiation Protocol
SM Session Modification
TE Terminating Endpoint
TP Test Purpose
TR TRansport
TSS Test Suite Structure
UA User Agent
V Valid
4 Test Suite Structure (TSS)
4.1.1 SIP Entities
Four kinds of entities are considered successively as IUT:
• User Agent behaving as client or Server.
• Registrar.
• Proxy (outbound and simple proxy).
• Redirect server.
本文档考虑四种实体：UAC/UAS, Registrar, Proxy, Redirect server.
4.1.3 System under test
In SIP, a client can either sends its request directly to the Request-URI or to its outbound proxy. It can also ask for
SIP URL to a redirect server before sending its request. Test purpose will apply depending of the current tested
configuration.
Three kinds of session have been considered in the present document:
• Call using a proxy.
• Direct call with no proxy.
• Call using a redirect server.
本文档考虑三种会话。
4.2 Overview of the Test Suite Structure
The Test Suite Structures is based on SIP entities and assumptions as described in clause 4.1.2.
Figure 2 shows the Test Suite Structure (TSS).
Last Sub groups may be
表里列出了测试结构, Test group 主要分为三类：Valid behaviour, Invalid behaviour, InOpportune behaviour.
5 Test Purposes (TP)
5.1.1 TP naming convention
Table 1: TP identifier naming convention scheme
Identifier: <protocol>_<main functionality>_<role>_<functionality>_<type>_<nn>
这里表1详细讲了 Test Purpose 的命名规范，比如我根据表1的描述可以举一个例子：SIP_RG_RT_V_001 类似这种。
5.1.2 State Definitions during a call
For more clarity and consistency, states defined in figures 5 to 8 in RFC 3261 [1], have been reused in the wording of
test purposes.
call state 定义沿用 RFC 3261 里的表述。
5.1.3 TP structure
Each test purpose is decomposed in seven keywords.
• The TPId gives a unique identifier to each test purpose.
• "Status" specifies, when a test purpose is optional, the selection condition according to RFC 3261 [1] PICS
document. It specifies also when is set to "Recommended" that the requirement appears in RFC 3261 [1] with
a "SHOULD" statement. The group status applies to all test purposes belonging to this group. When no status
is specified, mandatory shall be assumed.
• "Ref." outlines the references in RFC 3261 [1] used to create the test purpose.
• "Purpose" describes the objective of the test.
每一个 Test Purpose / TP 可以分解为 7 个关键字。
-- 为啥这里只解释了4个??
TPId： TP identifier
Status: 说明是必需还是可选；如果测试是可选的，这里阐述了选择这个测试的条件，一般会引用一个或几个 PICS 表项
Ref.: 引用了 RFC 3261 哪里
Purpose: objective, 详细测试目的
5.2 Test Purposes for Registration
5.2.1 Registrant
Group selection: Registration being listed as an option, the test purpose is applicable if the SUT is declared as
supporting periodic registration and can behave as User Agent.
Status: PICS: A.1/1 and A.2/1
测试注册服务是可选的，只有当 SUT 声明了支持注册，这时才适用此测试。
具体选择条件: PICS A.1/1 and A.2/1 这两个声明了支持。
-- 这里指向 TS 102 027-1 里的这两个 PICS 表项, 也就是 SUT 对协议内容是否实现的声明。
5.2.1.1 Valid Behaviour
正确行为测试组：下面是一些正确行为的 TP, 只拷贝几个有代表性的。
TPId: SIP_RG_RT_V_001
Status: Mandatory
Ref: RFC 3261 [1] section 10.2.
Purpose: Ensure that the IUT, in order to be registered, sends a REGISTER request to its registrar, without
user name in the Request-URI and with a SIP-URI as request-URI.
TPId: SIP_RG_RT_V_003
Status: PICS: A.3/1.1
表明当 IUT 声明支持 PICS A.3/1.1, 即 Configured registrar address 时，需要测试当前 TP.
Ref: RFC 3261 [1] section 10.2.6.
表明测试时参考这里，这个其实从 PICS 里也能看出来，都是一样的。
Purpose: Ensure that the IUT, in order to be registered, sends a REGISTER request to its pre-configured
registrar address and without username.
TPId: SIP_RG_RT_V_011
Status: Mandatory AND PICS: A.3/4
Ref: RFC 3261 [1] section 10.2.
Purpose: Ensure that the IUT having sent a REGISTER request, will increment the CSeq value by one in the
next new REGISTER request with the same Call-ID.
TPId: SIP_RG_RT_V_012
Status: Recommended AND PICS: A.3/4
Ref: RFC 3261 [1] section 10.2.4.
Purpose: Ensure that the IUT, already registered, sends at least one REGISTER request, during the shortest
lifetime indicated in the Expires parameter of Contact addresses of the Success (200 OK) response
it has received, using the same Call-ID as in the previous REGISTER request.
5.2.1.2 Timers
计时器测试组
TPId: SIP_RG_RT _TI_001
Status: Mandatory
Ref: RFC 3261 [1] annex A and section 17.1.2.2.
Purpose: If an unreliable transport is used, ensure that the IUT, having sent a REGISTER request, repeats its
request after timer E set to T1 value expires.
5.2.2 Registrar
Group selection: IUT is a Registrar
Status: PICS: A.1/2
REGISTER message can be received either on unicast or multicast address, depending of IUT ability (PICS: A.63/4 or
A.63/5)
5.2.2.1 Valid Behaviour
TPId: SIP_RG_RR_V_001
Status: Mandatory
Ref: RFC 3261 [1] section 10.3.
Purpose: Ensure that the IUT on receipt of a REGISTER and without user name in the Request-URI, sends
a Success (200 OK) response, containing all current bindings listed in the Contact header, with the
expires parameter for each Contact value.
5.2.2.2 Invalid Behaviour
不正确行为测试组
TPId: SIP_RG_RR_I_001
Status: Mandatory
Ref: RFC 3261 [1] section 10.3.
Purpose: Ensure that the IUT on receipt of a REGISTER request including a To header from which the
extracted address-of-record is not valid for the domain in the Request-URI, sends a Request
Failure (404 Not Found) response.
5.2.2.3 Inopportune Behaviour
TPId: SIP_RG_RR_O_001
Status: Mandatory
Ref: RFC 3261 [1] section 10.3.
Purpose: Ensure that the IUT when a binding already registered, on receipt of a REGISTER request
including a Contact header set to * and an Expires header set to zero, and Call-ID is the same as
the stored Call-ID value and CSeq is equal to the stored CSeq value of that binding, does not
remove that binding and sends a Success (200 OK) response.
5.3 Test Purposes for Call Control
Ref: RFC 3261 [1] section 1.4.4.
5.3.1 Originating Endpoint
Group selection: IUT is an User Agent.
Status: PICS: A.1/1
主叫端呼叫控制测试组
5.3.1.1 Call establishment
呼叫建立测试组
Group selection: IUT can behave as a User Agent client to establish a call.
Status: PICS: A.16/1.1
5.3.1.1.1 Valid Behaviour
正确行为测试组
TPId: SIP_CC_OE_CE_V_001
Status: Mandatory
Ref: RFC 3261 [1] section 8.1.1.
Purpose: Ensure that the IUT, to establish a call sends an INVITE request including at least To, From,
CSeq, Call-ID, Max-Forwards, Contact and Via headers.
5.3.1.1.2 Timers
计时器测试组
TPId: SIP_CC_OE_CE_TI_001
Status: Mandatory
Ref: RFC 3261 [1] annex A and section 17.1.1.1.
Purpose: If an unreliable transport (UDP) is used, ensure that the IUT, when an INVITE client transaction is
in the Calling state repeats its INVITE request on the timeout condition of timer A set with a value
of T1.
TPId: SIP_CC_OE_CE_TI_002
Status: Recommended
Ref: RFC 3261 [1] annex A and section 17.1.1.1.
Purpose: If a reliable transport (TCP) is used, ensure that the IUT, when an INVITE client transaction is in
the Calling state does not repeat its INVITE request on the timeout condition of timer A set with a
value of T1.
5.3.1.2 Call release
5.3.1.3 Session modification
5.3.2 Terminating Endpoint
被叫端呼叫控制测试组
Group selection: IUT is an User Agent.
Status: PICS: A.1/1
5.3.2.1 Call establishment
5.3.2.2 Call release
5.3.2.3 Session modification
5.3.3 Proxy
代理服务器测试组
Group selection: IUT is a Proxy
Status: PICS: A.1/3
5.3.3.1 Message processing
5.3.3.1.1 Request
5.3.3.1.2 Response
5.3.3.2 Transaction
5.3.3.2.1 Client
5.3.3.2.2 Server
5.3.4 Redirect Server
重定向服务器测试组
GroupSelection: IUT is a Redirect Server.
Status: PICS: A.1/4
5.3.4.1 Call establishment
5.3.4.2 Call release
5.4 Test Purposes for Querying for capabilities
5.4.1 Originating Endpoint
Group Selection: IUT is an User Agent that can ask for capabilities.
Status: PICS: A.49/1 AND A.1/1
5.4.2 Terminating Endpoint
Group Selection: IUT is an User Agent that can answer to capabilities request.
Status: PICS: A.1/1 AND A.49/2
5.4.3 Proxy
Group Selection: IUT is a Proxy
Status: PICS: A.1/3
5.5 Test Purposes for Messaging
5.5.1 Registrant
Group selection: Registration being listed as an option, the test purpose is applicable if the SUT is declared as
supporting periodic registration and can behave as User Agent.
Status: PICS: A.1/1 AND A.2/1
5.5.2 Registrar
GroupSelection: IUT is a Registrar
Status: PICS: A.1/2
5.5.3 Originating Endpoint
Group Selection: IUT can behave as a User Agent client to establish a call.
Status: PICS: A.1/1 AND PICS: A.16/1.1
5.5.4 Terminating Endpoint
Group Selection: IUT can behave as a User Agent server to establish a call.
Status: PICS: A.1/1 AND A.16/1.2
5.5.5 Proxy
Group Selection: IUT is a Proxy
Status: PICS: A.1/3
5.5.6 Redirect server
GroupSelection: IUT is a Redirect Server.
Status: PICS: A.1/4 AND A.114/1
Read ETSI TS 102 027 TS series 系列阅读笔记之:
ETSI TS 102 027-2 V4.1.1 (2006-07)
Methods for Testing and Specification (MTS);
Conformance Test Specification for SIP (IETF RFC 3261);
Part 2: Test Suite Structure and Test Purposes (TSS&TP)
看起来，就是列举了测试套件结构以及所有的测试目的，可以用来指导设计测试案例.
1 Scope
The present document provides a Test Suite Structure and Test Purposes (TSS&TP) for the Session Initiation Protocol
(SIP) implementation in compliance with the relevant requirements specified in RFC 3261 [1].
本文档提供 SIP 协议实现一致性测试套件结构以及测试目的。
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ATS Abstract Test Suite
CE Call Establishment
CR Call Release
I Invalid
IUT Implementation Under Test
MG MessaGing
O inOpportune
OE Originating Endpoint
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
PR PRoxy
RD ReDirect server
RG ReGistration
RR RegistraR
RT RegistranT
SIP Session Initiation Protocol
SM Session Modification
TE Terminating Endpoint
TP Test Purpose
TR TRansport
TSS Test Suite Structure
UA User Agent
V Valid
4 Test Suite Structure (TSS)
4.1.1 SIP Entities
Four kinds of entities are considered successively as IUT:
• User Agent behaving as client or Server.
• Registrar.
• Proxy (outbound and simple proxy).
• Redirect server.
本文档考虑四种实体：UAC/UAS, Registrar, Proxy, Redirect server.
4.1.3 System under test
In SIP, a client can either sends its request directly to the Request-URI or to its outbound proxy. It can also ask for
SIP URL to a redirect server before sending its request. Test purpose will apply depending of the current tested
configuration.
Three kinds of session have been considered in the present document:
• Call using a proxy.
• Direct call with no proxy.
• Call using a redirect server.
本文档考虑三种会话。
4.2 Overview of the Test Suite Structure
The Test Suite Structures is based on SIP entities and assumptions as described in clause 4.1.2.
Figure 2 shows the Test Suite Structure (TSS).
Last Sub groups may be
表里列出了测试结构, Test group 主要分为三类：Valid behaviour, Invalid behaviour, InOpportune behaviour.
5 Test Purposes (TP)
5.1.1 TP naming convention
Table 1: TP identifier naming convention scheme
Identifier: <protocol>_<main functionality>_<role>_<functionality>_<type>_<nn>
这里表1详细讲了 Test Purpose 的命名规范，比如我根据表1的描述可以举一个例子：SIP_RG_RT_V_001 类似这种。
5.1.2 State Definitions during a call
For more clarity and consistency, states defined in figures 5 to 8 in RFC 3261 [1], have been reused in the wording of
test purposes.
call state 定义沿用 RFC 3261 里的表述。
5.1.3 TP structure
Each test purpose is decomposed in seven keywords.
• The TPId gives a unique identifier to each test purpose.
• "Status" specifies, when a test purpose is optional, the selection condition according to RFC 3261 [1] PICS
document. It specifies also when is set to "Recommended" that the requirement appears in RFC 3261 [1] with
a "SHOULD" statement. The group status applies to all test purposes belonging to this group. When no status
is specified, mandatory shall be assumed.
• "Ref." outlines the references in RFC 3261 [1] used to create the test purpose.
• "Purpose" describes the objective of the test.
每一个 Test Purpose / TP 可以分解为 7 个关键字。
-- 为啥这里只解释了4个??
TPId： TP identifier
Status: 说明是必需还是可选；如果测试是可选的，这里阐述了选择这个测试的条件，一般会引用一个或几个 PICS 表项
Ref.: 引用了 RFC 3261 哪里
Purpose: objective, 详细测试目的
5.2 Test Purposes for Registration
5.2.1 Registrant
Group selection: Registration being listed as an option, the test purpose is applicable if the SUT is declared as
supporting periodic registration and can behave as User Agent.
Status: PICS: A.1/1 and A.2/1
测试注册服务是可选的，只有当 SUT 声明了支持注册，这时才适用此测试。
具体选择条件: PICS A.1/1 and A.2/1 这两个声明了支持。
-- 这里指向 TS 102 027-1 里的这两个 PICS 表项, 也就是 SUT 对协议内容是否实现的声明。
5.2.1.1 Valid Behaviour
正确行为测试组：下面是一些正确行为的 TP, 只拷贝几个有代表性的。
TPId: SIP_RG_RT_V_001
Status: Mandatory
Ref: RFC 3261 [1] section 10.2.
Purpose: Ensure that the IUT, in order to be registered, sends a REGISTER request to its registrar, without
user name in the Request-URI and with a SIP-URI as request-URI.
TPId: SIP_RG_RT_V_003
Status: PICS: A.3/1.1
表明当 IUT 声明支持 PICS A.3/1.1, 即 Configured registrar address 时，需要测试当前 TP.
Ref: RFC 3261 [1] section 10.2.6.
表明测试时参考这里，这个其实从 PICS 里也能看出来，都是一样的。
Purpose: Ensure that the IUT, in order to be registered, sends a REGISTER request to its pre-configured
registrar address and without username.
TPId: SIP_RG_RT_V_011
Status: Mandatory AND PICS: A.3/4
Ref: RFC 3261 [1] section 10.2.
Purpose: Ensure that the IUT having sent a REGISTER request, will increment the CSeq value by one in the
next new REGISTER request with the same Call-ID.
TPId: SIP_RG_RT_V_012
Status: Recommended AND PICS: A.3/4
Ref: RFC 3261 [1] section 10.2.4.
Purpose: Ensure that the IUT, already registered, sends at least one REGISTER request, during the shortest
lifetime indicated in the Expires parameter of Contact addresses of the Success (200 OK) response
it has received, using the same Call-ID as in the previous REGISTER request.
5.2.1.2 Timers
计时器测试组
TPId: SIP_RG_RT _TI_001
Status: Mandatory
Ref: RFC 3261 [1] annex A and section 17.1.2.2.
Purpose: If an unreliable transport is used, ensure that the IUT, having sent a REGISTER request, repeats its
request after timer E set to T1 value expires.
5.2.2 Registrar
Group selection: IUT is a Registrar
Status: PICS: A.1/2
REGISTER message can be received either on unicast or multicast address, depending of IUT ability (PICS: A.63/4 or
A.63/5)
5.2.2.1 Valid Behaviour
TPId: SIP_RG_RR_V_001
Status: Mandatory
Ref: RFC 3261 [1] section 10.3.
Purpose: Ensure that the IUT on receipt of a REGISTER and without user name in the Request-URI, sends
a Success (200 OK) response, containing all current bindings listed in the Contact header, with the
expires parameter for each Contact value.
5.2.2.2 Invalid Behaviour
不正确行为测试组
TPId: SIP_RG_RR_I_001
Status: Mandatory
Ref: RFC 3261 [1] section 10.3.
Purpose: Ensure that the IUT on receipt of a REGISTER request including a To header from which the
extracted address-of-record is not valid for the domain in the Request-URI, sends a Request
Failure (404 Not Found) response.
5.2.2.3 Inopportune Behaviour
TPId: SIP_RG_RR_O_001
Status: Mandatory
Ref: RFC 3261 [1] section 10.3.
Purpose: Ensure that the IUT when a binding already registered, on receipt of a REGISTER request
including a Contact header set to * and an Expires header set to zero, and Call-ID is the same as
the stored Call-ID value and CSeq is equal to the stored CSeq value of that binding, does not
remove that binding and sends a Success (200 OK) response.
5.3 Test Purposes for Call Control
Ref: RFC 3261 [1] section 1.4.4.
5.3.1 Originating Endpoint
Group selection: IUT is an User Agent.
Status: PICS: A.1/1
主叫端呼叫控制测试组
5.3.1.1 Call establishment
呼叫建立测试组
Group selection: IUT can behave as a User Agent client to establish a call.
Status: PICS: A.16/1.1
5.3.1.1.1 Valid Behaviour
正确行为测试组
TPId: SIP_CC_OE_CE_V_001
Status: Mandatory
Ref: RFC 3261 [1] section 8.1.1.
Purpose: Ensure that the IUT, to establish a call sends an INVITE request including at least To, From,
CSeq, Call-ID, Max-Forwards, Contact and Via headers.
5.3.1.1.2 Timers
计时器测试组
TPId: SIP_CC_OE_CE_TI_001
Status: Mandatory
Ref: RFC 3261 [1] annex A and section 17.1.1.1.
Purpose: If an unreliable transport (UDP) is used, ensure that the IUT, when an INVITE client transaction is
in the Calling state repeats its INVITE request on the timeout condition of timer A set with a value
of T1.
TPId: SIP_CC_OE_CE_TI_002
Status: Recommended
Ref: RFC 3261 [1] annex A and section 17.1.1.1.
Purpose: If a reliable transport (TCP) is used, ensure that the IUT, when an INVITE client transaction is in
the Calling state does not repeat its INVITE request on the timeout condition of timer A set with a
value of T1.
5.3.1.2 Call release
5.3.1.3 Session modification
5.3.2 Terminating Endpoint
被叫端呼叫控制测试组
Group selection: IUT is an User Agent.
Status: PICS: A.1/1
5.3.2.1 Call establishment
5.3.2.2 Call release
5.3.2.3 Session modification
5.3.3 Proxy
代理服务器测试组
Group selection: IUT is a Proxy
Status: PICS: A.1/3
5.3.3.1 Message processing
5.3.3.1.1 Request
5.3.3.1.2 Response
5.3.3.2 Transaction
5.3.3.2.1 Client
5.3.3.2.2 Server
5.3.4 Redirect Server
重定向服务器测试组
GroupSelection: IUT is a Redirect Server.
Status: PICS: A.1/4
5.3.4.1 Call establishment
5.3.4.2 Call release
5.4 Test Purposes for Querying for capabilities
5.4.1 Originating Endpoint
Group Selection: IUT is an User Agent that can ask for capabilities.
Status: PICS: A.49/1 AND A.1/1
5.4.2 Terminating Endpoint
Group Selection: IUT is an User Agent that can answer to capabilities request.
Status: PICS: A.1/1 AND A.49/2
5.4.3 Proxy
Group Selection: IUT is a Proxy
Status: PICS: A.1/3
5.5 Test Purposes for Messaging
5.5.1 Registrant
Group selection: Registration being listed as an option, the test purpose is applicable if the SUT is declared as
supporting periodic registration and can behave as User Agent.
Status: PICS: A.1/1 AND A.2/1
5.5.2 Registrar
GroupSelection: IUT is a Registrar
Status: PICS: A.1/2
5.5.3 Originating Endpoint
Group Selection: IUT can behave as a User Agent client to establish a call.
Status: PICS: A.1/1 AND PICS: A.16/1.1
5.5.4 Terminating Endpoint
Group Selection: IUT can behave as a User Agent server to establish a call.
Status: PICS: A.1/1 AND A.16/1.2
5.5.5 Proxy
Group Selection: IUT is a Proxy
Status: PICS: A.1/3
5.5.6 Redirect server
GroupSelection: IUT is a Redirect Server.
Status: PICS: A.1/4 AND A.114/1
浙公网安备 33010602011771号