Section 251.14 - VoIP Positioning Center Operator Minimum Requirements(a) Purpose. The purpose of this rule is to establish minimum requirements for VoIP Positioning Center (VPC) Operators providing or facilitating the providing of 9-1-1 service using a dynamic Automatic Location Identification (ALI) solution. This rule is intended to provide the end-users of IP-enabled voice service providers (VSPs) with a consistent level of 9-1-1 service that is more comparable to wireline E9-1-1 service.(b) Applicability. This rule is applicable to VPC Operators providing or facilitating the providing of 9-1-1 service to VSP end-users whose voice service is either fixed or nomadic, but non-mobile. Nomadic service is service that an end-user can access from any broadband connection. This rule provides the minimum standards for a VPC Operator to implement 9-1-1 service requirements.(c) Registration. A VPC Operator shall register with the Commission and provide written notice to each 9-1-1 Entity in whose region or territory they provide VPC service. Registration is a prerequisite to accessing a 9-1-1 Entity's Network and 9-1-1 Database, for obtaining 9-1-1 Entity approval to obtain pseudo automatic number identifications (pANIs), and for accessing dedicated 9-1-1 trunking, as applicable. Registration shall be made on a form provided by Commission staff and includes:(3) Name of 9-1-1 Entity in whose region or territory the VPC Operator provides service;(4) Name and contact information of its VSP customers;(5) Whether the VPC Operator collects or remits 9-1-1 service fees on behalf of any of its VSP customers' end-users.(d) Service Plan. A VPC Operator shall submit to the Commission a service plan consisting of the pANIs obtained from the North America Numbering Plan Administrator and the Emergency Service Number (ESN) assignment associated with each pANI.(e) Certification. A VPC Operator shall annually, and upon request by the Commission or a 9-1-1 Entity, update and certify the accuracy of its registration information.(f) Coordination with 9-1-1 Entity. Upon request from the Commission or a 9-1-1 Entity in whose region or territory a VPC Operator provides service, the VPC Operator shall coordinate with the Commission or requesting 9-1-1 Entity to ensure compliance with this rule and the proper provisioning of 9-1-1 service.(g) VPC Operator Minimum Requirements in Providing 9-1-1 Service. A VPC Operator shall: (1) use the current Master Street and Address Guide (MSAG) of each 9-1-1 Entity in whose region or territory the Operator provides 9-1-1 service to:(A) validate end-user ALI;(B) assign wireline ESNs from Emergency Services Query Key (ESQK) pools created for such purpose; and(C) use the correct ESQK pool in order to enable displaying valid English Language Translations (ELTs) matching the assigned wireline ESN;(2) accept delta MSAG files in a manner consistent with the standard current format of initial MSAG files to maintain the MSAG for near real-time validation purposes;(3) provide a pANI shell record containing the Automatic Number Information (ANI) and ALI associated with the 9-1-1 call;(4) provide the equivalent of MSAG-validated routing with associated wireline ESN, including the appropriate National Emergency Number Association (NENA) Class of Service (COS) code provided by its VSP and used by the 9-1-1 Entity in its region or territory. The foregoing requires VPC Operator to request from its VSP customers that they convey the correct COS codes for the VSPs' end-users;(5) provide its VSP customer's NENA Company ID in the Company ID field in the ALI record associated with each 9-1-1 call. VPC Operator's NENA Company ID should be identified by the pANI. In areas where the 9-1-1 Database supports using two NENA Company IDs, the two Company IDs shall be populated as provided in NENA standard 02-010; and(6) not use fictitious data in the pANI shell record associated with each 9-1-1 call.(h) MSAG validation and ALI Discrepancies. A VPC Operator shall address MSAG validation errors and ALI discrepancies within three (3) business days of notification by a 9-1-1 Entity. A VPC Operator shall verify that referred MSAG validation and ALI discrepancies have been resolved and provide written notice to the notifying 9-1-1 Entity. (1) A VPC shall obtain prior approval from the notifying 9-1-1 Entity before resolving a validation or discrepancy using an address translation or alias. A notifying 9-1-1 Entity shall use its best efforts to approve/deny requests for translations or aliases within three (3) business days of receipt of a request from a VPC Operator.(2) A VPC shall refer questions about a 9-1-1 Entity's MSAG to the appropriate 9-1-1 Entity. If the VPC Operator does not receive a response within three (3) business days, it shall escalate the issue to the 9-1-1 Entity or a representative of the appropriate MSAG authority.(i) ESQKs. Upon request from a 9-1-1 Entity, a VPC Operator will provide a listing of ESQKs used in the requesting 9-1-1 Entity's region or territory and a description of the standard period of aging and re-use cycle of ESQKs (e.g., how long ESQK information for the 9-1-1 call remains visible for call transfers).(j) Conversion and Deletion of Static 9-1-1 ALI Records. A VPC Operator whose VSP customer has static 9-1-1 ALI records in the 9-1-1 Database shall notify in writing its customer and the 9-1-1 Entity when conversion from the static protocol is complete to enable the VSP to initiate removal of all affected static records from the 9-1-1 Database.(k) Records and Information. To the extent permitted by RSA 222(g), a VPC Operator will, upon request from the Commission or a 9-1-1 Entity, provide records and information described by that section or timely forward the request to all affected VSPs and provide notice to the Commission or the requesting 9-1-1 Entity. Records and information submitted in response to a request shall be kept confidential in accordance with RSA 222(g) and Health and Safety Code § RSA 771.061, and used for purposes of enhancing the provisioning of 9-1-1 service or emergency notification service.1 Tex. Admin. Code § 251.14
The provisions of this §251.14 adopted to be effective May 1, 2013, 37 TexReg 8449