ATIS 1000053-2014 Emergency Telecommunications Service (ETS) Profile and Tests for IP Network-to-Network Interconnection.pdf

《ATIS 1000053-2014 Emergency Telecommunications Service (ETS) Profile and Tests for IP Network-to-Network Interconnection.pdf》由会员分享，可在线阅读，更多相关《ATIS 1000053-2014 Emergency Telecommunications Service (ETS) Profile and Tests for IP Network-to-Network Interconnection.pdf（79页珍藏版）》请在麦多课文档分享上搜索。

1、ATIS-1000053 Revision of ATIS-1000053 September 2012 Technical Report on Emergency Telecommunications Service (ETS) Profile and Tests for IP Network-to-Network Interconnection Alliance for Telecommunications Industry Solutions Approved August 2014 Abstract Emergency Telecommunications Service (ETS)

2、will be supported on IP Network-to-Network interconnections. There is a need to test and verify the ETS requirements relevant to IP Network-to-Network interconnection. This Technical Report provides ETS profile and tests for IP Network-to-Network interconnection. Foreword The Alliance for Telecommun

3、ication Industry Solutions (ATIS) serves the public through improved understanding between providers, customers, and manufacturers. The Packet Technologies and Systems Committee (PTSC) develops and recommends standards and technical reports related to services, architectures, and signaling, in addit

4、ion to related subjects under consideration in other North American and international standards bodies. PTSC coordinates and develops standards and technical reports relevant to telecommunications networks in the U.S., reviews and prepares contributions on such matters for submission to U.S. ITU-T a

5、nd U.S. ITU-R Study Groups or other standards organizations, and reviews for acceptability or per contra the positions of other countries in related standards development and takes or recommends appropriate actions. The mandatory requirements are designated by the word shall and recommendations by t

6、he word should. Where both a mandatory requirement and a recommendation are specified for the same criterion, the recommendation represents a goal currently identifiable as having distinct compatibility or performance advantages. The word may denotes a optional capability that could augment the stan

7、dard. The standard is fully functional without the incorporation of this optional capability. Suggestions for improvement of this document are welcome. They should be sent to the Alliance for Telecommunications Industry Solutions, PTSC, 1200 G Street NW, Suite 500, Washington, DC 20005. At the time

8、of consensus on this document, PTSC, which was responsible for its development, had the following leadership: M. Dolly, PTSC Chair AT however, additional work will be required to develop actual test scripts based on the test scenarios, configurations and protocol suites presented. 7. It is understoo

9、d that test SIP device endpoint E.164 addresses will need to be exchanged prior to testing. SIP URIs converted from TEL URI format will be used to convey the E164 addresses. (See ATIS-1000009 for example URIs.) 8. IPv4 is assumed unless otherwise stated. 9. The term “Provider” is used to generically

10、 represent all types of parties. 2 Normative References The following standards contain provisions which, through reference in this text, constitute provisions of this Standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agree

11、ments based on this Standard are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. 2.1 ATIS References ATIS-1000038 ATIS-1000038, Technical Parameters for IP Network to Network Interconnection Release 1.0, August 2010.1ATIS-1000039 ATIS-

12、1000039, Testing Configuration for IP Network to Network Interconnection Release 1.0, August 2010.21This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005. 3 ATIS-1000040 ATIS-1000040, Protocol Suite Profile

13、for IP Network to Network Interconnection Release 1.0, August 2010.3ATIS-1000041 ATIS-1000041, Test Suites for IP Network to Network Interconnection Release 1.0, August 2010.4ATIS-1000010 ATIS-1000010.2006 (R2011), Support of Emergency Telecommunications Service in IP Networks, 2006.5ATIS-1000023 AT

14、IS-1000023.2013, ETS Phase 1 Network Element Requirements for a NGN Based Deployments, 2013.6ATIS-1000011 ATIS-1000011, ETS Packet Priority for IP NNI Interfaces - Use of Existing DiffServ Per Hop Behaviors.7ATIS-1000020 ATIS-1000020, ETS Packet Priority for IP NNI Interfaces - Requirements for a Se

15、parate Expedited Forwarding Mechanism.8ATIS-1000049 ATIS-1000049, Standard for End-to-End NGN GETS Call Flows.92.2 IETF References IETF RFC 4412 Communications Resource Priority for the Session Initiation Protocol (SIP), February 2006102.3 Informative References ATIS-1000009 ATIS-1000009.2006 (R2011

16、), IP Network To Network Interface (NNI) Standard for VoIP.112This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005. 3This document is available from the Alliance for Telecommunications Industry Solutions (A

17、TIS), 1200 G Street N.W., Suite 500, Washington, DC 20005. 4This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005. 5This document is available from the Alliance for Telecommunications Industry Solutions (ATI

18、S), 1200 G Street N.W., Suite 500, Washington, DC 20005. 6This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005. 7This document is available from the Alliance for Telecommunications Industry Solutions (ATIS)

19、, 1200 G Street N.W., Suite 500, Washington, DC 20005. 8This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005. 9This document is available from the Alliance for Telecommunications Industry Solutions (ATIS),

20、1200 G Street N.W., Suite 500, Washington, DC 20005. 10This document is available from the Internet Engineering Task Force (IETF). 11This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005. 4 3 Definitions, Ac

21、ronyms, 2. SIP Signaling Port; and 3. Media Port. This set of ports and the basic network configurations are identified in the previous section. The information required to specify a test configuration is therefore reduced to the specification of these logical ports for voice services. The complete

22、specification of these ports includes the protocol profiles and the selectable parameters and their values as specified during interconnection negotiation between providers. These port configuration parameters are documented in ATIS-100040 and ATIS-100041. The values of the fixed and selectable para

23、meters will be specified by the providers per service agreement, which will finalize the actual design of the configuration for each test. 5 Technical Parameters 5.1 Introduction Support for the technical parameters for basic voice services described in ATIS-1000038 and for the ETS parameters listed

24、 in Table 2 is a precursor for testing of ETS voice services. 5.2 Technical Parameters Described in ATIS-1000038 Table 5.1 provides a list of the technical parameters described in ATIS-1000038 and indicates whether the technical parameter is also applicable for ETS testing. 8 Table 5. 1 - Protocol P

25、arameters from ATIS-1000038 ATIS-1000038 Text Section ATIS-1000038 Technical Parameter Description Applicability for ETS Testing 5.1 Signaling Parameters 5.1.1 Manufacturer/Type Yes 5.1.2 Software Version Yes 5.1.3 IP Address(es) As a transport mechanism by the Media Server Control Markup Language (

26、MSCML) protocol; and As a transport mechanism by the Media Server Markup Language (MSML) protocol. 8.3.1.2.1 Purpose Verify that Service Providers provide priority treatment of an ETS call that utilizes the SIP INFO method. 8.3.1.2.2 Test Setup or (2) Reset the received ets resource value to the def

27、ault resource value for requests sent into the network (Requirement 3100) AND to verify that the ets value inserted by the NE has a default value and that the default value is configurable. (Requirement B100): a. Reset the NE and note the default ets resource value. b. Configure the RPH capability o

28、f the NE to enabled. c. Configure the default ets resource value to be unique within the test configuration. d. Configure the NNI interfaces to use the ets resource value received across an IP NNI interface in requests it sends into the network. e. Execute the call procedure described in Test Case 1

29、-1. f. Configure the NNI interfaces to reset the received ets resource value to the default resource value for requests sent into the network. g. Execute the call procedure described in Test Case 1-1. 25 5. To verify that the NE is configurable to accept or reject a SIP INVITE with the ets RPH and a

30、 normal (non-ETS-DN) destination number on a per interface basis, the default should be to reject the SIP INVITE (Requirement 3200, B400): a. Reset the NE and note the value of the reject SIP INVITE capability. b. Configure the RPH capability of the NE to enabled. c. Configure the NE to reject a SIP

31、 INVITE with the ets RPH and a normal (non-ETS-DN) destination number. d. Initiate the call procedure described in Test Case 1-1 for a GETS-AN call that contains a normal (non-ETS-DN) destination number. e. Configure the NE to accept a SIP INVITE with the ets RPH and a normal (non-ETS-DN) destinatio

32、n number. f. Execute the call procedure described in Test Case 1-1 for a GETS-AN call that contains a normal (non-ETS-DN) destination number. 8.3.1.5.3 Observable Results All Service Provider A NEs should have interfaces used to configure query parameters values. The SIP message formats will be capt

33、ured and analyzed for the NNI legs of the calls. The Layer 2 and Layer 3 markings for the signaling messages will be captured and analyzed for the NNI legs of the calls. 8.3.1.5.4 Pass/Fail Criteria To pass this test case, the following criteria shall be met: Test Step 1: a. All of Service Provider

34、As NEs should provide management interfaces used to configure and query parameter values. Test Step 2: a. The default value for the SIP RPH capability should be disabled. b. Service Provider As default ets value can be configured to a unique value for the test configuration. c. Service Provider As S

35、IP RPH capability should be configured to disabled. d. Service Provider A propagates SIP messages between the UNI and NNI with the SIP RPH value unchanged. e. Service Provider As SIP RPH capability should be configured to enabled. f. Service Provider A propagates SIP messages between the UNI and NNI

36、 with the SIP RPH ets value mapped to its configured default value. Test Step 3: a. The default value for the resource-priority option tag with the Require header field capability should be disabled. b. Service Provider As SIP RPH capability should be configured to enabled. c. Service Provider As re

37、source-priority option tag with the Require header field capability can be configured to disabled. d. Service Provider A rejects the SIP INVITE that contains the Require header field (and the SIP RPH value ets.0 wps.y), sending a 420 (Bad Extension) response with an 26 “Unsupported: resource-priorit

38、y”. Note that the 420 response should not contain the ets RPH header. e. Service Provider As resource-priority option tag with the Require header field capability can be configured to enabled. f. The SIP INVITE message originated by Service Provider A contains the Require header field with the resou

39、rce-priority option tag. Test Step 4: a. The ets resource initializes to a default value. Note the value. b. Service Provider As SIP RPH capability can be configured to enabled. c. The ets resource default value can be configured. d. The NNI and UNI interfaces are configured to use the received ets

40、resource value. e. The SIP messages originated by Service Provider A at the UNI and NNI contain the RPH with ets resource value set to the value in received messages. f. The NNI and UNI interfaces are configured to use the default ets resource value. g. The SIP messages originated by Service Provide

41、r A at the UNI and NNI contain the RPH with ets resource value set to the default. Test Step 5: a. The SIP INVITE capability default value is to reject a SIP INVITE with the ets RPH and a normal (non-ETS-DN) destination number. b. Service Provider As SIP RPH capability can be configured to enabled.

42、c. Service Provider A can be configured to reject a SIP INVITE with the ets RPH and a normal (non-ETS-DN) destination number. d. Service Provider A rejects the SIP INVITE that contains the ets RPH and a normal (non-ETS-DN) destination number, sending a 403 (Forbidden) response with two reason header

43、 fields: (1) a 417 (RPH header) code for SIP; and (2) a Reason Header Q.850 value of 21 (call rejected). Note that the 403 response should not contain the ets RPH header. e. Service Provider A can be configured to accept a SIP INVITE with the ets RPH and a normal (non-ETS-DN) destination number. f.

44、Service Provider A accepts the call as a priority call and signals accordingly. (Note that following the initial SIP INVITE message, messages received from the direction of the call originator will contain RPHs only if the upstream equipment also considers the call a priority call.) This test verifies the following requirements: Requirement Document Requirement Number Refer to Appendix ATIS-1000010 3 A.1 ATIS-1000023 100, 300, 900, 1300, 3100, 3200, B100, B400 A.2 ATIS-1000011 A.3 ATIS-1000020 A.3