ATIS 0500009-2006 High Level Requirements for End-to-End Functional Testing.pdf

1、 ESIF TECHNICAL REPORT ATIS-0500009 High Level Requirements for End-to-End Functional Testing ATIS-0500009 1 2 3 4 5 6 7 8 ATIS is a technical planning and standards development organization that is committed to rapidly developing and promoting technical and operations standards for the communicatio

2、ns and related information technologies industry worldwide using a pragmatic, flexible and open approach. Over 1,100 participants from more than 350 communications companies are active in ATIS 22 industry committees, and its Incubator Solutions Program. www.atis.org. 9 10 11 12 13 14 Revision Histor

3、y ATIS-0500009 High Level Requirements for End-to-End Functional Testing Version Date Changes 1.0 4-5-2006 Initial Release 1.1 12-5-2006 Revised document number 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 ATIS-0500009: High Level Requirements for End-to-End Functional Testing is an ATIS

4、 standard developed by the following committee(s) under the ATIS User Interface functional group: The Emergency Services Interconnection Forum (ESIF), Subcommittee G Published by The Alliance for Telecommunications Industry Solutions (ATIS) 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright

5、 2006 by Alliance for Telecommunications Industry Solutions All rights reserved. No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher. For information contact ATIS at (202) 628-6380. ATIS is o

6、nline at: http:/www.atis.org. 34 35 36 Printed in the United States of America. iiATIS-0500009 TABLE OF CONTENTS 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 1 Introduction1 1.1 Scope .1 1.2 Acknowledgements 1 1.3 Referenc

7、es .1 2 Definitions2 2.1 Acronyms3 3 General4 3.1 Purpose 4 3.2 End-to-End Functional Testing Concept.4 4 Test Scope.6 4.1 Test Area6 4.2 Tested System Elements6 4.3 Call Routing6 4.4 Data Delivery6 4.5 Non-Standard Call Scenarios .7 5 Testing Structure .8 5.1 System Testing.8 5.2 Field Testing.8 6

8、Responsibilies and Pre-Requisites 9 6.1 Wireless Carrier9 6.2 PSAP Authority.9 6.3 MPC/GMLC/ALI10 7 Equipment Requirements 10 7.1 Network Equipment 10 7.2 Subscriber Equipment 10 8 Test Preparation 10 8.1 Test Plan and Schedule11 8.2 PSAP Authority Notification/Participation11 8.3 MPC/GMLC Support.1

9、1 8.4 Field Test Resources11 9 Test Conduct .11 9.1 General.11 9.2 System Testing.12 9.3 Field Testing.14 9.4 Data Collection .15 9.5 Data Validation .16 9.6 Test Acceptance.16 10 Documentation of Results 16 10.1 Testing Documents.16 Appendix A Sample Forms 18 Test Summaries and Certification: 18 Te

10、st Data Worksheets:19 iiiATIS-0500009 1 INTRODUCTION 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 The United States Federal Communications Commission has established accuracy requirements for network and handset based l

11、ocation solutions for Enhanced 9-1-1 emergency call services. These requirements can be found in the Commissions Third Report and Order, adopted September 15, 1999. The Emergency Services Interconnection Forum (ESIF) identified the need for industry accepted methodologies for testing the accuracy pe

12、rformance and end-to-end functionality of Wireless E9-1-1 Phase 2 systems, both for initial assessment testing as well as ongoing maintenance testing. Requirements for accuracy testing methodologies were addressed in ATIS Standard ATIS-0500001, released in May of 2004. This document addresses method

13、ologies for testing the end-to-end functionality of both Phase 1 and Phase 2 Wireless E9-1-1 systems other than accuracy. A subsequent document will in turn address maintenance testing. This document neither recommends nor imposes a specific test methodology, but rather provides a common frame of re

14、ference that individual stakeholders can use to validate the end-to-end functionality of a Phase 1 or Phase 2 E9-1-1 integrated network and provides a set of minimum requirements for individual test methodologies. Every possible effort has been made to ensure that these requirements remain technolog

15、y neutral. Per current ESIF Operating Guidelines, due process has been followed in the creation of this document, and development has been open for participation within the bounds of ESIF. 1.1 Scope This document focuses on providing a set of minimum requirements for the “End-to-End Functional Testi

16、ng” of Wireless E9-1-1 deployments. These procedures are applicable to both Phase 1 and Phase 2 deployments, where appropriate. 1.2 Acknowledgements Study Group G would like to thank its members for their active participation and contribution to the creation of this document. 1.3 References 1 Enhanc

17、ed Wireless 911 Phase 2 J-STD-036-B Telecommunications Industry Association and Alliance for Telecommunications Industry Solutions June 2005 2 High Level Requirements for Accuracy Testing Methodologies ATIS Standard ATIS-0500001 Alliance for Telecommunications Industry Solutions May 2004 3 Emergency

18、 Services Interconnection Forum (ESIF) Wireless E911 Phase II Readiness Package (ATIS/ESIF 001) Alliance for Telecommunications Industry Solutions January 29, 2003 4 Revision of the Commissions Rules To Ensure Compatibility with Enhanced 911 Emergency Calling Systems, CC Docket No. 94-102, Order, (C

19、ity of Richardson 1ATIS-0500009 Order). See also 47 C.F.R. 20.18(j). Federal Communications Commission, USA Oct. 10, 2001 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 5 Revision of the Commissions Rules to Ensure

20、Compatibility with 911 Emergency Calling Systems, CC Docket No. 94-102, Order on Reconsideration, FCC 02-318 (City of Richardson Reconsideration Order). Federal Communications Commission, USA Nov. 26, 2002 6 Revision of the Commissions Rules to Ensure Compatibility with 911 Emergency Calling Systems

21、, CC Docket No. 94-102, Memorandum Opinion and Order, FCC 03-262 Federal Communications Commission, USA Nov. 3, 2003 7 Near Term Issues for Emergency / E9-1-1 Services, Final Report Network Reliability and Interoperability Council VII (NRIC VII), Focus Group 1A December 2005 2 DEFINITIONS This secti

22、on offers a few definitions found to be important to maintain a common vocabulary throughout the creation of this document. Accuracy Testing Accuracy testing, whether through empirical and/or predictive test methods, consists of generating location data to gauge the accuracy performance of the syste

23、m. Location data, typically significant in volume, involves the location infrastructure of the carriers network. The primary objective is to verify location accuracy and correct any location system errors. Limiting the test to the carriers location network minimizes impact to the rest of the Phase 2

24、 network and maximizes the capability of the carriers to optimize their system. Functionality Testing (End to End) Functionality testing consists of testing the delivery of the location data from the carrier to the PSAP. The objective of this testing activity is to ensure interoperability between th

25、e carrier and the Emergency Service Network. This testing activity requires tight coordination among the involved parties, which normally includes the Emergency Service Network, the carrier and the technology vendors. Maintenance Testing Maintenance testing may be conducted after a system has been t

26、urned up with the Emergency Service Network. Like all network systems, maintenance testing will be conducted as needed to ensure functionality and performance. This testing activity may include functionality and/or accuracy testing and the participation of the Emergency Service Network may or may no

27、t be required. Maintenance testing can be a condensed version of the original accuracy and functionality testing. pANI The pseudo automatic number assigned to identify and an emergency call. Includes both ESRD and ESRK. PSAP Authority The entity having responsibility for PSAP operations and function

28、. This may be a local, regional or state level organization. 2ATIS-0500009 Jurisdictional PSAP 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 The PSAP having primary jurisdictional responsibility for a given l

29、ocation. Routing PSAP Wireless network coverage areas and position determining systems do not typically align exactly with PSAP jurisdictional areas. The Routing PSAP is the PSAP to which a call from a given location is routed based on wireless system coverage factors and position determination capa

30、bilities, and may or may not be the same as the jurisdictional PSAP. Initial Deployment (Phase 1 and Phase 2) Deployment of Phase 1 or Phase 2 wireless location capability by a Wireless Service Provider (WSP) that has not previously deployed in a PSAP jurisdiction within the 911- Entitys region. Pha

31、se 2 Response A response shall be classified as Phase 2 when the MPC/GMLC provides the estimated location of the caller regardless of accuracy (Class of Service displayed at the PSAP should be WPH2). Cell sites with a sufficiently limited coverage radius may also be considered Phase 2. Phase 1 Respo

32、nse A response shall be classified as Phase 1 when the location delivered is based on the cell/sector from which the call originated. The Class of Service displayed at the PSAP should be either “WRLS” (no Phase 2 location capability exists), or “WPH1” (Phase 2 capability exists but the specific call

33、er location could not be determined). Cell sites with a sufficiently limited coverage radius may also be considered Phase 2. Note: Class of Service displays may vary among 9-1-1 system service providers and are not controlled directly by the wireless carrier. Roamer A subscriber handset that has loc

34、al service outside the WSPs local serving area, but within the United States. International Roamer A subscriber handset that has local service outside of the United States. Uninitialized Handset A handset that is not subscribed to any wireless service. 2.1 Acronyms AFLT Advanced Forward Link Trilate

35、ration AGPS Assisted GPS ALI Automatic Location Identification ANSI American National Standards Institute AOA Angle of Arrival E9-1-1 Enhanced 911 Emergency Service ESRD Emergency Services Routing Digits ESRK Emergency Services Routing Key ESME Emergency Services Messaging Entity ESNE Emergency Serv

36、ices Network Entity GMLC Gateway Mobile Location Center 3ATIS-0500009 GPS Global Positioning System 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 GSM Global System for Mobile Communications MPC Mobile Positioning Center MSC Mobil

37、e Switching Center pANI Pseudo Automatic Number Identification PDE Position Determining Equipment PSAP Public Safety Answering Point RF Radio Frequency S/R Selective Router SMLC Serving Mobile Location Center TDOA Time Difference of Arrival U-TDOA Uplink TDOA 3 GENERAL 3.1 Purpose The overall goal o

38、f end-to-end testing is to assess the level of functionality provided by wireless 911 systems with respect to Federal Communications Commission (FCC) requirements to deliver 911 Automatic Location Identification (ALI) information accurately and within specified time constraints. These suggested proc

39、edures verify that the routing PSAP is receiving wireless 911 calls in an appropriate manner. End-to-end testing is not focused on location accuracy performance as compared to FCC accuracy requirements. It is focused instead on the delivery function. Any party wishing to perform Phase 2 accuracy tes

40、ting should refer to ESIF Technical Report ATIS-0500001, “High Level Requirements for Accuracy Testing Methodologies”. The framework contained herein can be used for both End-to-End Functional Testing or in conjunction with Maintenance Testing as defined in ATIS-0500007. This framework can also be u

41、sed as a reference on how the integrated E9-1-1 architecture performs under different scenarios, with different phones and capabilities, and utilizing different location technologies. 3.2 End-to-End Functional Testing Concept The objective of End-to-End Functional Testing is to validate call routing

42、 and data delivery from each active cell site/sector in the PSAP jurisdiction. In addition to this, optional tests as outlined in Section 4.5 can be executed based upon PSAP requests. End-to-End Functional Testing assumes that this is the WSPs initial attempt to implement either Phase 1 or Phase 2 s

43、ervice over the entire PSAP coverage area or that portion of a PSAPs coverage area served by the wireless carrier. Subsequent testing conducted in conjunction with wireless carrier system expansion (but not a Phase 2 upgrade) is covered under the guidelines for Maintenance Testing referenced above.

44、Figures 3-1 and 3-2 show the high-level network architecture for End-to-End Functional Testing. A carriers network interconnects to a PSAP CPE via direct trunking or through the LEC Selective Router and the Emergency Services Message Entity (ESME), which contains various LEC or stand alone ALI datab

45、ases, protocol converters, etc. 4ATIS-0500009 1 2 3 Figure 3-1: High Level Architecture for End-to-End Testing (ANSI-41 Networks) 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Figure 3-2: High Level Architecture for End-to-End Testing (GSM Networks) The end-to-end concept contained herein highlights two impor

46、tant aspects of E9-1-1 call processing: 1) Call routing and 2) Data delivery. Call routing validates that the emergency call is delivered to the appropriate PSAP without noticeable delay. Data Delivery validates that the data provided by the Carrier Network is sent quickly and accurately to the PSAP

47、 CPE. Since there are multiple interconnected networks that can modify and interact with the data that is sent from the carrier network, end-to-end testing will validate that all interconnected networks are passing the correct data without additional latency. The ultimate objective of this testing a

48、ctivity is to ensure full interoperability between the carriers Wireless Service Providers Network and the Emergency Services Network. End-to-end testing activity thus requires cooperation and coordination amongst the 5ATIS-0500009 involved parties, which normally includes the Emergency Service Netw

49、ork (including the PSAP), the Carrier and ESME. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 4 TEST SCOPE 4.1 Test Area The test area must include all cell sectors from which the PSAP has requested and/or agreed to accept call routing. The carrier shall determine where to make 911 calls within each cell site/sector. 4.2 Tested System Elements All elements of the E9-1-1 location and call routing system shall be tested, either comprehensively or on a sample basis as described in this document. This shall include PDE, SMLC, MSC, GMLC