Page 1
2015 LNPA Technical Requirements Document
1. TRD OVERVIEW, INTRODUCTION, and FRS Section 1
1.1 STATEMENT:
TRD Introduction and Purpose 
Pursuant to the Telecommunications Act of 1996, the Federal Communications Commission (FCC) has adopted a 
succession of orders implementing Local Number Portability (LNP), which allows consumers to change service providers 
for telecommunications services at the same location without changing their telephone numbers. Currently, LNP is 
enabled in the seven United States former Regional Bell Operating Company (RBOC) service areas or regions, including 
their related Territories (each a "Region" and collectively, the "Regions") through seven databases, one in each Region, 
collectively referred to as the Number Portability Administration Center/Service Management System (NPAC/SMS). Each 
Regional database is operated and administered by a Local Number Portability Administrator (LNPA), neutral and 
independent from Telecommunications Carriers. A separate Master Agreement governs the operation and administration 
of the NPAC/SMS by the LNPA in each of the seven Regions and specifies the terms and conditions for providing 
NPAC/SMS services (referred to as the "Services"). 
All Master Agreements in all Regions are managed by the North American Portability Management LLC (NAPM LLC), and 
all Master Agreements in all Regions expire on June 30, 2015. The FCC has delegated authority to its advisory 
committee, the North American Numbering Council (NANC), working in consultation with the NAPM LLC, to implement a 
vendor selection process, for the next-generation NPAC/SMS in all Regions, to commence at the expiration of the current 
Master Agreements. This vendor selection process includes issuance of a Request For Information (RFI) and a 
subsequent Request For Proposal (RFP) and will culminate in the selection of the LNPA in each of the seven Regions. The 
purpose of the NANC is to advise the Commission and to make recommendations, reached through consensus, that foster 
efficient and impartial number administration. The NANC, a diverse body with consumer, state government, and industry 
representatives, has established an LNPA Selection Working Group (SWG) to oversee the selection process of the LNPA.
See Order, WC Docket No. 09-109 and CC Docket No. 95-116, DA 11-883, (adopted May 16, 2011) for process 
information and the respective roles of the FCC, NANC, and NAPM LLC. During this process, options for replacement 
and/or enhancement of the current NPAC/SMS in all Regions may be considered. 
The purpose of the RFP is to provide each prospective RFP vendor (referred to as a Respondent or a Bidder) with an 
opportunity to demonstrate how its proposal satisfies the requirements of the RFP and will benefit 
Telecommunications Carriers and other qualified parties who will be Users of the NPAC/SMS and who rely upon the 
NPAC/SMS for the rating, routing, and billing of calls, law enforcement and other parties who may be granted certain 
limited and special access to NPAC/SMS data for other permissible purposes, and ultimately consumers. Each Respondent 
is instructed to answer all questions in as concise and complete a manner as possible, and in many instances, the 
Respondent is provided with an opportunity to elaborate on its answers. 
The RFP includes this Technical Requirements Document (TRD) survey that identifies both the technical requirements 
describing the requisite technical capability of any proposal and the required obligations of an LNPA to administer the 
NPAC/SMS(s). Although great care has been taken to ensure the accuracy of the TRD and other reference documents, it 
is the Respondent's responsibility to ensure that any response to a specific NPAC/SMS technical requirement contained 
herein is based on the latest NPAC/SMS Functional Requirements Specification (FRS) and other reference documents as 
currently published and made available to the industry. FRS Rel 3.4.1 (a) was used in creating the TRD FRS sections. 
Each technical document (FRS, IIS, GDMO, ASN 1.0) has its own glossary, abbreviations, figures and tables. 
The Local Number Portability Administration Working Group (LNPA WG) is a public industry forum that determines what 
technical capabilities are to be implemented in the NPAC/SMS. Information about this subcommittee of the NANC is 
found at http://www.npac.com. All respondents to the TRD survey are encouraged to attend the LNPA WG, during and 
after their submission(s). 
Page 2
The NAPM LLC has authorized one of its Advisory Committees, the Future of NPAC Subcommittee (hereafter referred to 
as the FoNPAC), to project manage the RFP process, including the solicitation and evaluation of responses to this TRD 
survey and to utilize the Iastaฎ SmartSource SRMฎ Tool to gather, evaluate, and weigh all responses to this TRD 
survey as part of the LNPA selection process. The LNPA selection process is expected to conclude on or about March 
2013. 
Thank you in advance for your participation in the RFP process. 
1.2 STATEMENT:
Vendor TRD Response Instructions 
As part of responding to this TRD survey, Respondents will be required to respond to each requirement as indicated, as 
well as answer a series of questions in more detail. The detailed question section is at the end of this TRD survey called, 
"TRD Detailed Response." 
ท If the Respondent would like to explain any answers, please do so in the "TRD Detailed Response" section. 
ท If the Respondent would like to suggest improvements or additional enhancements, please do so in the "TRD 
Detailed Response" section. 
RFP survey Section 9 on Service Level Requirements supersedes any and all corresponding Service Level 
Requirements documented in this TRD survey or in the FRS. 
1.3* QUESTION:
Backwards Compatibility Requirement 
In responding to the requirements in this TRD, all Respondents submitting bids MUST indicate and highlight any and all 
areas of functionality in their proposal that will not remain Interface and Functional Backwards Compatible. 
Backward Compatibility Definitions 
There are three areas of Backwards Compatibility. These are defined below: 
ท Pure Backwards Compatibility - means that interface specification has NOT been modified and therefore, no 
recompile is necessary. Also, no behavior on the NPAC/SMS has been modified to provide any change to the 
previously existing functionality accessible over the interface. 
ท Interface and Functional Backwards Compatibility - means that the interface may have been modified, however 
the changes are such that no action is required for the Service Provider to remain backward compatible.
However, any new functionality is optionally implemented, and would require a recompile and possibly functional 
software changes by the Service Provider to access the newly defined features over the interface. Also, no 
changes may be made to any existing interface functionality that will require modifications to SOA and/or LSMS 
platforms. 
ท Re-Compile Only Backwards Compatibility - means that the interface has been modified, however the changes are 
such that only a recompile is necessary to remain backward compatible. Any new functionality is optionally 
implemented by accessing the newly defined features over the interface. Also, no NPAC/SMS software changes 
may be made to any existing interface functionality that will require source code modifications to SOA and/or 
LSMS platforms.
Page 3
The objective is that all implementations resulting from this bidding process remain Interface and Functional Backwards 
Compatible, to the extent possible.
Has the Respondent agreed to this requirement to indicate any and all areas of their responses that WILL 
NOT remain at least "Interface and Functional Backwards Compatible"? Please answer "YES" or "NO". 
(Note: The FoNPAC will assume that all responses include backwards compatibility unless indicated otherwise.) 
(no answer)
Yes
No
1.4* QUESTION:
Treatment of Subsequent NANC Change Orders 
By submitting a bid to this RFP, Respondent understands and agrees that any NANC Change Orders implemented in the 
NPAC/SMS subsequent to the submission of their bid, or scheduled for implementation prior to the turn-up of the next-
generation NPAC/SMS, MUST be incorporated into their proposed NPAC/SMS platform and ready for implementation at 
turn-up. 
(no answer)
Agree
Disagree
1.5* QUESTION:
TRD FRS Section 1: Introduction 
The FRS defines the functional requirements of the NPAC/SMS enabling LNP. 
This introduction gives an overview of NPAC/SMS functionality. It is intended to prepare the Respondent for the detailed 
TRD FRS sections that follow. Consult the applicable detailed sections in the FRS or the NPAC/SMS Interoperable 
Interface Specification (IIS), Guidelines for the Definition of Managed Objects (GDMO), and Abstract Syntax 
Notation One (ASN.1) for more detailed information. www.napmllc.org/pages/NPACRFP/NPACRFP_refdocs.aspx
Has the Respondent read, understood, and incorporated the FRS Section 1 concepts into Respondent's 
proposal? 
(no answer)
Yes
No
Page 4
2. TRD FRS Section 2: BUSINESS PROCESS FLOWS
2.1*QUESTION:
TRD FRS Section 2: Business Process Flows 
The process flows in Section 2 of the FRS indicate how the NPAC/SMS is used by the Service Providers in business 
processes associated with LNP. Specific requirements generated by the process flows are included in the appropriate FRS 
sections. 
The process flows supported by the NPAC/SMS are: 
1. Service Provisioning 
2. Service Disconnection 
3. Service Repair 
4. Conflict and Conflict Resolution 
5. Disaster Recovery and Backup 
6. Service Order Cancellation 
7. Audit Requests 
8. Report Requests 
9. Data Administration Requests 
Please note the following are the specific requirements listed in Section 2 of the FRS and are currently outside the scope 
of the NPAC/SMS: 
1. Interactions between Service Providers (CN2-1.1.1) 
2. Service Provider network change activities (CN2-1.3.1) 
3. Service Provider's network change validation activities (CN2-1.5.1) 
4. Service Provider's repair activities (CN2-3.3.1) 
5. Service Provider's conflict resolution activities (CN2.4.2.1)
Has the Respondent read, understood, and incorporated these concepts into Respondent's proposal? 
(no answer)
Yes
No
3. TRD FRS Section 3: NPAC DATA ADMINISTRATION
3.1*QUESTION:
TRD FRS Section 3: NPAC Data Administration 
The NPAC/SMS manages the ported TN information associated with Service Provider portability for the LNP service. This 
section describes the high level requirements associated with managing ported telephone numbers from an operations 
perspective.
Page 5
TRD FRS Section 3: Sub Section 3.1: 
The required Data Models are described in detail in the FRS document Section 3.1: 
 3.1.1: Data Type Legend
 3.1.2: NPAC Customer Data Model 
 3.1.3: Subscription Version Data Model 
 3.1.4: Network Data Model 
Does the Respondent's proposal adhere to these exact Data Models and has Respondent read, understood, 
and incorporated these concepts into Respondent's proposal? 
(no answer)
Yes
No
3.2*QUESTION:
TRD FRS Section 3: Sub Section 3.2: NPAC Personnel Functionality 
The FRS Section 3.2 requirements describe the functionality required by the NPAC/SMS to support the daily operation of 
the Regional LNP SMS support staff. These requirements define the high level functionality required by the system with 
the specifics of each requirement defined in more detail in FRS Sections 4 and 5.  
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
R3-3: Create NPA-NXX data for a Service Provider
R3-6.2: Mass Update Filter Usage 
R3-7.2: Administer Mass update on one or more selected Subscription Versions 
R3-7.3: Mass Update Selection Criteria 
R3-7.4: Mass Update Service Provider Id 
R3-7.7: Mass Update Error Processing 
R3-7.8: Mass Update Exception Report 
RR3-254: Validation of LATA ID Errors on Mass Updates 
R3-7.9: Mass Update Required Entry of Service Provider ID
R3-13: NPAC/SMS mass change update capability to the Local SMS 
RR3-254: Validation of LATA ID Errors on Mass Updates
RR3-550: Mass Update Pending and Active Subscription Versions – DPC-SSN Field-level Data Validation 
RR3-551: Mass Update Pending and Active Subscription Versions – Validation of DPC-SSNs for Mass Update 
RR3-552: Mass Update Pending and Active Number Pool Blocks – DPC-SSN Field-level Data Validation 
RR3-552.5: Mass Update Pending and Active Number Pool Blocks – Validation of DPC-SSNs for Mass Update 
RR3-708: Mass Update - Notifications for Pseudo-LRN Updates
Page 6
(no answer)
Yes
No
3.2.1*QUESTION:
TRD FRS Section 3: Sub Section 3.2.1: Block Holder, Mass Update 
The FRS Section 3.2.1 requirements describe the functionality required by the NPAC/SMS to support Block Holder Mass 
Updates. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-210: Block Holder Information Mass Update – Update Fields
RR3-211: Block Holder Information Mass Update – Block Intersection Rejection 
RR3-212: Block Holder Information Mass Update – Block Status Validation 
RR3-213: Block Holder Information Mass Update – Download to EDR Local SMS 
RR3-214: Block Holder Information Mass Update – Download to non-EDR Local SMS 
RR3-215: Block Holder Information Mass Update – Download of SVs of Type POOL to non-EDR Local SMS 
(no answer)
Yes
No
3.2.2 STATEMENT:
TRD FRS Section 3: Sub Section 3.2.2: Service Provider ID (SPID) Migration Update 
This FRS section defines how the NPAC/SMS supports modification of Service Provider ID on Local Number Portability 
information. Two options are available, 1.) an on-line self-service feature is available using the LTI that can be used by 
Service Provider Personnel optionally in lieu of spreadsheets submitted via e-mail to NPAC Personnel, and 2.) an interface 
message enhancement allows NPA-NXX ownership changes to be sent via a CMIP message. NPAC Personnel generate 
Selection Input Criteria SPID Migration Update Request Files (SIC-SMURF) to all Service Providers (as a primary means of 
update by those that do not support the interface message to update their databases, and as a backup means of update 
for those that do support the interface message). Additionally, SIC-SMURFs are used even by Service Providers that 
support the interface message when the migration involves NPA-NXX-Xs and/or LRNs. SIC-SMURFs are placed in all 
Service Providers' Secure FTP sites at the beginning of a maintenance window; updates are performed independently off-
line during the maintenance window by each Service Provider to its own databases. 
 
3.2.2.1* QUESTION:
TRD FRS Section 3: Sub Section 3.2.2.1: SPID Migration Updates and Processing 
Page 7
With functionality in NANC 323, SIC-SMURFs are generated by NPAC Personnel and distributed (via Secure FTP) to all 
Service Providers. SPID Migrations may be performed as defined in sections 3.2.2.2 and 3.2.2.3. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-255: SPID Migration Update - OpGUI Entry
RR3-256: SPID Migration Update - Generation of SIC-SMURF Files 
RR3-257: SPID Migration Update - NPAC/SMS Processing of Requested Data 
RR3-258: SPID Migration Update - Suppression of Notifications 
RR3-259: SPID Migration Update - NPAC/SMS Processing of Requested Data Based on Status 
RR3-260: SPID Migration Update - SIC-SMURF File Names
RR3-261: SPID Migration Update - SIC-SMURF File Formats 
RR3-262: SPID Migration Update - SIC-SMURF NPA-NXX File Processing - Update NPA-NXX Network Data 
RR3-709: SPID Migration Update - SIC-SMURF NPA-NXX File Processing - Update SV Data for Pseudo-LRN Records 
RR3-710: SPID Migration Update - SIC-SMURF NPA-NXX File Processing - Update Block Data for Pseudo-LRN Records 
RR3-264: SPID Migration Update - SIC-SMURF LRN File Processing - Update LRN Data 
RR3-265: SPID Migration Update - SIC-SMURF LRN File Processing - Update Block Data 
RR3-266: SPID Migration Update - SIC-SMURF-LRN File Processing - Update SV Data 
RR3-267: SPID Migration Update - SIC-SMURF NPA-NXX-X File Processing - Update NPA-NXX-X 
RR3-268: SPID Migration Update - Maximum Level of Granularity 
RR3-269: SPID Migration Update - Minimum Level of Granularity 
RR3-274: SPID Migration Update - Exclusion of Data During Recovery 
RR3-275: SPID Migration Update - Rejection for 'pending-like' Number Pool Blocks or Subscription Versions 
RR3-276: Update SPID on Messages Queued for Recovery 
RR3-277: SPID Migration Update - Consistency Check Across Network Data and LRN 
(no answer)
Yes
No
 
3.2.2.2*QUESTION:
TRD FRS Section 3: Sub Section 3.2.2.2 Requirements 
The FRS Section 3.2.2.2 requirements address how online GUI functionality allows a Service Provider to perform self-
service on entry of SPID Migrations. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-553: Regional SPID Migration Online Functionality Indicator - Tunable Parameter 
RR3-554: Regional SPID Migration Online Functionality Indicator - Tunable Parameter Default 
RR3-555: Regional SPID Migration Online Functionality Indicator - Tunable Parameter Modification 
RR3-556: SPID Migration Blackout Dates - GUI Entry By NPAC Personnel 
RR3-557: SPID Migration Blackout Dates - Displaying in the GUI 
RR3-558: SPID Migration Last Scheduling Date - Tunable Parameter
RR3-559: SPID Migration Last Scheduling Date - Tunable Parameter Default 
RR3-560: SPID Migration Last Scheduling Date - Tunable Parameter Modification 
RR3-561: SPID Migration Entry Restriction - Last Scheduling Date - Service Provider Personnel 
RR3-562: SPID Migration Update - Migration Summary Information 
RR3-563: SPID Migration Update - GUI Availability/Selection function for Service Provider and NPAC Personnel 
Page 8
RR3-564: SPID Migration Update - Available Migration Window Minimum - Tunable Parameter 
RR3-565: SPID Migration Update - Available Migration Window Minimum - Reject 
RR3-566: SPID Migration Update - NPAC Personnel Scheduling SPID Migrations to Any Migration Date in the Future 
RR3-567: SPID Migration Update - Available Migration Window Minimum - Tunable Parameter Default 
RR3-568: SPID Migration Update - Available Migration Window Minimum - Tunable Parameter Modification 
RR3-569: SPID Migration Update - GUI Entry by Service Provider and NPAC Personnel 
RR3-570: SPID Migration Update - GUI Entry by Service Provider and NPAC Personnel - Required Fields 
RR3-571: SPID Migration Update - Generation of SPID Migration Name 
RR3-572: SPID Migration Update - GUI Modification by Service Provider Prior to Other Service Provider Concurrence or 
NPAC Personnel Confirmation 
RR3-573: SPID Migration Update - GUI Cancellation by Service Provider Prior to NPAC Personnel Confirmation 
RR3-574: SPID Migration Update - GUI Error for Double Booking 
RR3-575: SPID Migration Update - GUI Concurrence by Service Provider and NPAC Personnel 
RR3-576: SPID Migration Creation by "migrating-from" and "migrating-to" SPIDs 
RR3-577: SPID Migration Update - GUI Entry Service Provider - Confirmation by NPAC Personnel 
RR3-578: SPID Migration Update - Confirmation by NPAC Personnel Required 
RR3-579: SPID Migration Update - Reject by NPAC Personnel 
RR3-580: SPID Migration Update - Service Providers Viewing Migrations 
RR3-581: SPID Migration Update - Service Providers Viewing Their Own Migrations 
RR3-583: SPID Migration Creation - Disallowing Scheduling of Two SPID Migrations with the same "Migrating-From" and 
"Migrating-To" SPID to the same Maintenance Day 
RR3-584: SPID Migration Email List - Tunable Parameter 
RR3-585: SPID Migration Email List - Tunable Parameter Default 
RR3-586: SPID Migration Email List - Tunable Parameter Modification 
RR3-587: SPID Migration E-mail due to NPAC Personnel Operations 
RR3-588: SPID Migration E-mail to "migrating-from" and "migrating-to" Service Providers 
RR3-589: SPID Migration Update - GUI Cancellation by NPAC Personnel on behalf of Service Provider 
RR3-590: SPID Migration Update - GUI Modification by NPAC Personnel of Scheduled SPID Migration 
RR3-591: SPID Migration Update - GUI Execution by NPAC Personnel of Scheduled SPID Migration 
RR3-592: SPID Migration Update - GUI Execution by NPAC Personnel - Notification to Local SMS and SOA 
RR3-593: SPID Migration Update - Pending-Like SVs and NPBs Cleaned Up 
RR3-594: Completed SPID Migration Retention - Tunable Parameter 
RR3-595: Completed SPID Migration Retention - Tunable Parameter Default 
RR3-596: Completed SPID Migration Retention - Tunable Parameter Modification 
RR3-597: Completed SPID Migration Retention - Housekeeping Purge 
RR3-598: Cancelled SPID Migration Retention - Tunable Parameter 
RR3-599: Cancelled SPID Migration Retention - Tunable Parameter Default 
RR3-600: Cancelled SPID Migration Retention - Tunable Parameter Modification 
RR3-601: Cancelled SPID Migration Retention - Housekeeping Purge 
RR3-602: SPID Migration Update - Quota Management 
RR3-603: SPID Migration Update - Quota Management - Quota Exceeded Rejection for Service Provider Personnel 
RR3-604: SPID Migration Update - Quota Management - Quota Exceeded Warning for NPAC Personnel 
RR3-605: SPID Migration Update - Quota Management - Quota Exceeded Warning Content 
RR3-606: SPID Migration Update - Migration Quota Tunable Parameter 
RR3-607: SPID Migration Update - Migration Quota Tunable Parameter Default 
RR3-608: SPID Migration Update - Migration Quota Tunable Parameter Modification 
RR3-609: SPID Migration Update - All Regions Migration Quota Tunable Parameter 
RR3-610: SPID Migration Update - All Regions Migration Quota Tunable Parameter Default 
RR3-611: SPID Migration Update - All Regions Migration Quota Tunable Parameter Modification 
RR3-612: SPID Migration Update - SV Quota Tunable Parameter 
RR3-613: SPID Migration Update - SV Quota Tunable Parameter Default 
RR3-614: SPID Migration Update - SV Quota Tunable Parameter Modification 
RR3-615: Maintenance Window Day of the Week - Tunable Parameter 
RR3-616: Maintenance Window Day of the Week - Tunable Parameter Default 
RR3-617: Maintenance Window Day of the Week - Tunable Parameter Modification 
RR3-618: Maintenance Window Start Time Hour - Tunable Parameter 
RR3-619: Maintenance Window Start Time Hour - Tunable Parameter Default 
RR3-620: Maintenance Window Start Time Hour - Tunable Parameter Modification 
Page 9
RR3-621: Preliminary SPID Migration SMURF Files Lead Time - Tunable Parameter 
RR3-622: Preliminary SPID Migration SMURF Files Lead Time - Tunable Parameter Default 
RR3-623: Preliminary SPID Migration SMURF Files Lead Time - Tunable Parameter Modification 
RR3-624: Generation of Preliminary SMURF files 
RR3-625: Generation of Final SMURF files 
RR3-626: Offline-Only SPID Migration Flag 
RR3-627: SPID Migration Suspended Status 
RR3-628: Suspended SPID Migrations - No Automatic Online Migration 
RR3-629: Suspended SPID Migrations - No Manual Online Migration 
RR3-630: SPID Migration Suspension/Un-suspension - No Quota Change 
RR3-631: Automatic suspension when pre-migration validations fail 
RR3-632: SPID Migration - Secure FTP Site Directory Structure 
RR3-632.5: SPID Migration - Secure FTP Site Subdirectory - Service Provider Tunable 
RR3-633: SPID Migration - Secure FTP Site Date Subdirectory - Service Provider Indicator Default 
RR3-634: SPID Migration - Secure FTP Site Date Subdirectory - Service Provider Indicator Modification 
RR3-711: SPID Migration -Service Provider GUI Login Restriction 
RR3-712: SPID Migration - Pseudo-LRN Indicator 
RR3-762: SPID Migration Update - Online-to-Offline Restriction Window - Tunable Parameter 
RR3-763: SPID Migration Update - Online-to-Offline Restriction Window - Tunable Parameter Default 
RR3-764: SPID Migration Update - Online-to-Offline Restriction Window - Tunable Parameter Modification 
RR3-765: SPID Migration Update - SPID Migration Date Restriction Window - Tunable Parameter 
RR3-766: SPID Migration Update - SPID Migration Date Restriction Window - Tunable Parameter Default 
RR3-767: SPID Migration Update - SPID Migration Date Restriction Window - Tunable Parameter Modification 
(no answer)
Yes
No
 
3.2.2.3*QUESTION:
TRD FRS Section 3: Sub Section 3.2.2.3: SPID Migration Interface Messages 
The FRS Section 3.2.2.3 requirements address interface messages for code-only migrations that are sent to Service 
Providers that support the feature. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-635: Service Provider SOA Automated SPID Migration Indicator 
RR3-636: Service Provider SOA Automated SPID Migration Indicator Default 
RR3-637: Service Provider SOA Automated SPID Migration Indicator Modification 
RR3-638: Service Provider SOA Automated SPID Migration Indicator Usage 
RR3-639: Service Provider LSMS Automated SPID Migration Indicator 
RR3-640: Service Provider LSMS Automated SPID Migration Indicator Default 
RR3-641: Service Provider LSMS Automated SPID Migration Indicator Modification 
RR3-642: Service Provider LSMS Automated SPID Migration Indicator Usage 
RR3-643: Service Provider Secure FTP SMURF File in lieu of missed SPID Migration Transactions 
RR3-644: Online SPID Migration Lead Time - Tunable Parameter 
RR3-645: Online SPID Migration Lead Time - Tunable Parameter Default 
RR3-646: Online SPID Migration Lead Time - Tunable Parameter Modification 
RR3-647: Online SPID Migration - Database Updates 
Page 10
(no answer)
Yes
No
 
3.2.2.4*QUESTION:
TRD FRS Section 3: Sub Section 3.2.2.4: SPID Migration Reports 
Does the Respondent's proposal fully comply with the requirement below in time to meet the published 
implementation date? 
RR3-648: SPID Migration Reports – Post-Migration SV and NPB Count Report 
(no answer)
Yes
No
3.3*QUESTION:
TRD FRS Section 3: Sub Section 3.3: System Functionality 
The FRS Section 3.3 requirements address system functionality related to offline batch downloads, online network 
downloads, notifications, LATA ID association and validation, and NPAC SMS record ID inventory. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date?
R3-8: Off-line batch updates for Local SMS Disaster Recovery 
R3-9: NPAC/SMS download of network data to the Local SMS and SOA 
RR3-66: Number Pool NPA-NXX-X Holder Information - NPAC/SMS download of network data to the SOA or Local SMS 
RR3-67.1: Number Pool NPA-NXX-X Holder Information - NPAC/SMS download via SOA and/or Local SMS Interface of 
NPA-NXX-X allocation to the Service Providers 
R3-10: NPAC/SMS notification of NPA-NXX availability to the Service Providers 
R3-11: NPAC/SMS notification of LRNs and Service Provider data by Service Provider 
RR3-67.2: Number Pool NPA-NXX-X Holder Information - NPAC/SMS download via Web Bulletin Board of NPA-NXX-X 
allocation to the Service Providers 
RR3-278: LATA ID Information Source 
RR3-279: Association of LATA ID with NPA-NXXs 
RR3-280: Association of LATA ID with LRNs 
RR3-439: Validation of LATA ID for NPA-NXX Creates 
RR3-440: Validation of LATA ID for LRN Creates 
RR3-649: NPAC/SMS Record ID Inventory - Maximum Value Rollover 
RR3-650: NPAC/SMS Record ID Inventory - Mechanism 
RR3-651: NPAC/SMS Record ID Inventory - Adding Available ID Values 
RR3-652: NPAC/SMS Record ID Inventory - Skipping Un-Available ID Values 
RR3-653: NPAC/SMS Record ID Inventory - Issuing new ID Values 
RR3-654: NPAC/SMS Record ID Inventory - Skipping ID Value of Zero 
Page 11
(no answer)
Yes
No
3.4*QUESTION:
TRD FRS Section 3: Sub Section 3.4: Additional Requirements 
The FRS Section 3.4 requirements address additional requirements related to addition, validation, deletion and 
downloading of NPA NXX data and LRNs. FTP site info, clock synchronization, database extract file creation, input 
restrictions, first usage effective dates, and timestamps are also covered in section 3.4. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RX3-1.1.1: Service Provider NPA-NXX Data Addition 
RX3-1.1.2: Service Provider NPA-NXX Data Effective Date Validation 
RX3-1.2: Service Provider LRN Data Addition 
RX3-3.1: Service Provider NPA-NXX Data Deletion 
RX3-3.2: Service Provider LRN Data Deletion 
RR3-1: Service Provider Download Indicator 
RR3-2: Service Provider Download Indicator 
R3-14: Bulk Database Extracts 
R3-15: Secure FTP Site for Database Extracts 
R3-16: Database Extract File Creation 
R3-17: Scope of Database Extract File Creation 
RR3-3: NPAC/SMS Input Restrictions 
RR3-4: Create LRN data for a Service Provider 
RR3-15: NPAC Clock Synchronization 
RR3-474: NPA-NXX Availability - First Usage Effective Date Window - Tunable Parameter 
RR3-475: NPA-NXX Availability - First Usage Effective Date Window - Tunable Parameter Default 
RR3-476: NPA-NXX Availability - First Usage Effective Date Window - Tunable Parameter Modification 
RR3-477: NPA-NXX- Live TimeStamp 
RR3-478: Region Supports First Usage Effective Date Indicator 
RR3-479: Region Supports First Usage Effective Date Modification 
RR3-480: Region Supports First Usage Effective Date Indicator - Default Value 
(no answer)
Yes
No
3.4.1*QUESTION:
TRD FRS Section 3: Sub Section 3.4.1: Valid NPA-NXXs in a Region Data Validations 
The FRS Section 3.4.1 requirements address data validations for NPAs and NPA NXXs for each NPAC region. 
Page 12
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-441: Valid NPAs for each NPAC Region 
RR3-442: Maintaining List of Valid NPAs for Each NPAC Region 
RR3-443: Updating List of Valid NPAs for Each NPAC Region 
RR3-444: Rejection of NPA-NXXs that Do Not Belong to a Valid NPA for the NPAC Region 
RR3-445: Regional NPAC NPA Edit Flag Indicator 
RR3-446: Regional NPAC NPA Edit Flag Indicator Modification 
RR3-447: Regional NPAC NPA Edit Flag Indicator - Default Value 
RR3-448: Valid NPA-NXXs for 859 KY Exception 
RR3-449: Maintaining List of Valid NPA-NXXs for 859 KY Exception 
RR3-450: Updating List of Valid NPAs for 859 KY Exception 
RR3-451: Rejection of NPA-NXXs that Do Not Belong to a Valid NPA for the 859 KY Exception 
(no answer)
Yes
No
3.4.2*QUESTION:
TRD FRS Section 3: Sub Section 3.4.2: NPA-NXX Modification 
The following requirements address modification of NPA NXX data. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-655: Regional NPA-NXX Modification Flag Indicator - Tunable Parameter 
RR3-656: Regional NPA-NXX Modification Flag Indicator - Tunable Parameter Default 
RR3-657: Regional NPA-NXX Modification Flag Indicator - Tunable Parameter Modification 
RR3-658: Modify NPA-NXX data for a Service Provider 
RR3-659: NPAC/SMS download of network data to the Local SMS and SOA - Modification 
RR3-660: Service Provider NPA-NXX Data Modification 
RR3-661: Modification of NPA-NXX - Effective Date Modification from OpGUI 
RR3-662: Modification of NPA-NXX - Effective Date versus Current Date 
RR3-663: Modification of NPA-NXX - New Effective Date versus No Pending SVs or Scheduled NPA-NXX-Xs/Number Pool 
Blocks 
RR3-664: Modification of NPA-NXX - Validation Error 
RR3-665: Service Provider SOA NPA-NXX Modification Flag Indicator 
RR3-666: Service Provider SOA NPA-NXX Modification Flag Indicator Default 
RR3-667: Service Provider SOA NPA-NXX Modification Flag Indicator Modification 
RR3-668: Service Provider LSMS NPA-NXX Modification Flag Indicator 
RR3-669: Service Provider LSMS NPA-NXX Modification Flag Indicator Default 
RR3-670: Service Provider LSMS NPA-NXX Modification Flag Indicator Modification
RR3-671: Modification of NPA-NXX - Service Provider SOA NPA-NXX Modification Flag Indicator set to FALSE 
RR3-672: Modification of NPA-NXX - Service Provider SOA NPA-NXX Modification Flag Indicator set to TRUE 
RR3-673: Modification of NPA-NXX - Service Provider LSMS NPA-NXX Modification Flag Indicator set to FALSE 
RR3-674: Modification of NPA-NXX - Service Provider LSMS NPA-NXX Modification Flag Indicator set to TRUE 
RR3-675: Service Provider SOA NPA-NXX Modify BDD File Indicator 
RR3-676: Service Provider SOA NPA-NXX Modify BDD File Indicator Default 
RR3-677: Service Provider SOA NPA-NXX Modify BDD File Indicator Modification 
Page 13
RR3-678: Service Provider LSMS NPA-NXX Modify BDD File Indicator 
RR3-679: Service Provider LSMS NPA-NXX Modify BDD File Indicator Default 
RR3-680: Service Provider LSMS NPA-NXX Modify BDD File Indicator Modification 
(no answer)
Yes
No
3.4.3*QUESTION:
TRD FRS Section 3: Sub Section 3.4.3: Valid NPA-NXXs for each Service Provider 
The following requirements allow for maintaining valid OCN and NPA NXX lists for each SPID. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-681: Valid NPA-NXXs for each SPID 
RR3-682: Maintaining List of Valid NPA-NXXs for each SPID 
RR3-683: Updating List of Valid NPA-NXXs for each SPID 
RR3-684: Valid OCNs for each SPID 
RR3-685: Maintaining List of Valid OCNs for each SPID 
RR3-686: Updating List of Valid OCNs for each SPID 
RR3-687: Rejection of NPA-NXXs that Do Not Belong to the OCN/SPID 
RR3-688: Regional NPAC NPA-NXX Ownership Edit Flag Indicator 
RR3-689: Regional NPAC NPA-NXX Ownership Edit Flag Indicator Modification 
RR3-690: Regional NPAC NPA-NXX Ownership Edit Flag Indicator - Default Value 
RR3-691: Rejection of NPA Split for an NPA-NXX that Does Not Belong to the OCN/SPID 
(no answer)
Yes
No
3.4.4*QUESTION:
TRD FRS Section 3: Sub Section 3.4.4: Pseudo-LRN in a Region Data Validations 
The following requirements provide for the proper use of Pseudo-LRNs in the NPAC/SMS. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-713: LRN Record – Pseudo-LRN value in the NPAC/SMS 
RR3-714: LRN Record – Pseudo-LRN restriction in the NPAC/SMS 
RR3-715: LRN Record – Pseudo-LRN query in the NPAC/SMS 
RR3-716: Region Supports Pseudo-LRN Indicator 
Page 14
RR3-717: Region Supports Pseudo-LRN Modification 
RR3-718: Region Supports Pseudo-LRN Indicator – Default Value 
(no answer)
Yes
No
3.5*QUESTION:
TRD FRS Section 3: Sub Section 3.5: NPA Splits Requirements 
Section 3.5 defines NPA Split functionality within the NPAC/SMS. The primary means of processing NPA Split information 
within the NPAC/SMS is through automated and regular processing of NPA Split Load Flat Files from industry source data.
In the event of an 'emergency' there is a manual process by which authorized NPAC personnel may enter required NPA 
Split information in order to initiate appropriate processing. This manual process is reserved for only 'back-up or 
emergency' situations as deemed by industry and NPAC representatives. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RN3-1: NPA Split Permissive Dialing 
RN3-2: NPA Split 
RN3-3: NPA Split Permissive Dialing Cleanup 
RR3-281: NPA Split - Load File from Industry Source Data 
RR3-282: NPA Split - Load File from Industry Source Data During Housekeeping Process 
RR3-283: NPA Split - Load File from Industry Source Data Processing Results 
RR3-284: NPA Split - Load File from Industry Source Data, Reject existing new NPA-NXX 
RR3-285: NPA Split - Load File from Industry Source Data, Generate new NPA-NXX 
RR3-286: NPA Split - Load File from Industry Source Data, Delete new NPA-NXX 
RR3-287: NPA Split - NPA Split Load Flat File Exception Report with An Existing New NPA-NXX 
RR3-288: NPA Split - Load File from Industry Source Data, Verifying Old and New NPA-NXX 
RR3-289: NPA Split - Load File from Industry Source Data, Pushing Out PDP Start Date 
RR3-290: NPA Split - Load File from Industry Source Data, Pulling In PDP Start Date 
RR3-291: NPA Split - Load File from Industry Source Data, Error Modifying PDP Start Date with Existing Subscription 
Versions 
RR3-292: NPA Split - Load File from Industry Source Data, Complete Processing of File 
RR3-293: NPA Split - Load File from Industry Source Data, Re-Processing of File 
RR3-294: NPA Split - Load File from Industry Source Data, Error Modifying PDP Start Date for NPA Split Already in 
Progress 
RR3-295: NPA Split - Load File from Industry Source Data, Adding an NXX to an Existing Split 
RR3-296: NPA Split - Load File from Industry Source Data Information on the Web 
AN3-4.1: NPA Split Information Source 
AN3-4.2: NPAC Personnel Manual NPA Split Request 
RN3-4.1: NPA Split - NPA-NXX existence prior to the NPA Split 
FRS Section 3: Sub Section 3.5: Requirement RN3-4.2: NPA Split - New NPA-NXX existence prior to the NPA Split - Error 
RR3-436: NPA Split -Old NPA-NXX non-existence prior to the NPA Split - Error 
RR3-437: NPA Split - New NPA-NXX Creation 
RN3-4.6: NPA Split - NPA-NXX involved in one NPA Split Validation 
RR3-297: NPA Split - NPA Split Load Flat File Exception Report with New NPA-NXX Already Involved in NPA Split 
RN3-4.7: NPA Split - No Active Subscription Versions in the new NPA-NXX 
RN3-4.8: NPA Split - No Active Subscription Versions in the new NPA-NXX - Error 
RN3-4.9: NPA Split - Prevention of NPA-NXX Deletion 
Page 15
RN3-4.11: NPA Split - No modification of LRN data
RN3-4.12: NPA Split - Exception Processing for Subscription Versions that exist in the New and Old NPA-NXX 
RN3-4.13: NPA Split - No Modification of Filter Data 
RN3-4.14: NPA Split - Audit Processing 
RN3-4.15: NPA Split - Entering of Split Data 
RN3-4.16: NPA Split - Modification of End Date of Permissive Dialing Date 
RR3-438: NPA Split - Modification of Start Date of Permissive Dialing Date 
RN3-4.17: NPA Split - Removal of NPA-NXX during Permissive Dialing 
RN3-4.18: NPA Split - Removal of NPA-NXX during Permissive Dialing - Subscription Version Processing 
RN3-4.20: NPA Split - Removal of NPA Split Information prior to NPA Split 
RN3-4.21: NPA Split - Removal of NPA Split Information after Permissive Dialing Period End Date 
RN3-4.22: NPA Split - No Broadcast of Subscription Version Modification 
RN3-4.23: NPA Split - Retention of Subscription Version Id 
RN3-4.24: NPA Split - Update of Subscription Versions at the Beginning of Permissive Dialing 
RN3-4.25: NPA Split - Old NPA-NXX involved in one NPA Split Validation 
RN3-4.26: NPA Split - Old NPA-NXX involved in one NPA Split Validation - Error 
RR3-298: NPA Split - NPA Split Load Flat File Exception Report with Old NPA-NXX Already Involved in NPA Split 
RN3-4.27: NPA Split - Validation of the Permissive Dialing Period
RN3-4.28: NPA Split - Old NPA-NXX and New NPA-NXX Ownership Validation 
RR3-299: NPA Split - NPA Split Load Flat File Exception Report with Mismatched SPIDs for Old and New NPA-NXX 
RN3-4.30: NPA Split - Creation of a Subscription Version during the Permissive Dialing Period 
RN3-4.31: NPA Split - Current and Pending NPA Split Report 
RN3-4.32: NPA Split - NPA Split History Report 
RR3-219: NPA Splits - Deletion of Old NPA-NXX at the end of permissive dialing 
(no answer)
Yes
No
3.5.1*QUESTION:
TRD FRS Section 3: Sub Section 3.5.1: NPA-NXX-X, NPA Splits 
The following requirements address Number Pools and NPA-NXX-X information. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date?
RR3-31: NPA Splits and the Number Pool NPA-NXX-X Information - New NPA Split Automatic Create of New NPA-NXX-X 
RR3-32: NPA Splits and the Number Pool NPA-NXX-X Information - New NPA Split Error Message if New NPA-NXX-X 
Already Exists 
RR3-300: NPA Split - NPA Split Load Flat File Exception Report with Already Existing New NPA-NXX-X 
RR3-33: NPA Splits and the Number Pool NPA-NXX-X Information - New NPA Split Field Values for Automatic Add of New 
NPA-NXX-X 
RR3-34: NPA Splits and the Number Pool NPA-NXX-X Information - New NPA Split, Skip Block and Subscription Version 
Create 
RR3-35: NPA Splits and the Number Pool NPA-NXX-X Information - NXX Removal from NPA Split prior to the end of PDP 
RR3-36.1: NPA Splits and the Number Pool NPA-NXX-X Information - Addition of an NPA-NXX-X scheduled for an NPA 
Split 
RR3-36.2: NPA Splits and the Number Pool NPA-NXX-X Information - New Addition of an NPA-NXX-X scheduled for an 
NPA Split With an Error Message 
RR3-36.3: NPA Splits and the Number Pool NPA-NXX-X Information - Addition of an NPA-NXX-X currently in Permissive 
Page 16
Dialing in an NPA Split 
RR3-37.1: NPA Splits and the Number Pool NPA-NXX-X Information - Modification of an NPA-NXX-X scheduled for an NPA 
Split 
RR3-37.2: NPA Splits and the Number Pool NPA-NXX-X Information - New Modification of an NPA-NXX-X scheduled for an 
NPA Split With an Error Message 
RR3-37.3: NPA Splits and the Number Pool NPA-NXX-X Information - Modification of an NPA-NXX-X involved in an NPA 
Split 
RR3-38.1: NPA Splits and the Number Pool NPA-NXX-X Information - Deletion of an NPA-NXX-X involved in an NPA Split 
RR3-38.2: NPA Splits and the Number Pool NPA-NXX-X Information - New Deletion of an NPA-NXX-X scheduled for an 
NPA Split With an Error Message 
RR3-38.3: NPA Splits and the Number Pool NPA-NXX-X Information - Deletion of an NPA-NXX-X involved in an NPA Split 
RR3-39: NPA Splits and the Number Pool NPA-NXX-X Information - Broadcast of Addition or Deletion of NPA-NXX-X Split 
Data 
RR3-40: NPA Splits and the Number Pool NPA-NXX-X Information - Deletion of Old NPA-NXX-X at the end of permissive 
dialing 
(no answer)
Yes
No
3.5.2*QUESTION:
TRD FRS Section 3: Sub Section 3.5.2: Block Holder, NPA Splits 
The following requirements address NPA Splits and Block Holder information. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-41: NPA Splits and the Number Pooling Block Holder Information – Recognition of Both Old NPA and New NPA 
RR3-42: NPA Splits and the Number Pooling Block Holder Information – NXX Removal from Split 
RR3-43: NPA Splits and the Number Pool Block Holder Information – Addition of a Block involved in an NPA Split 
RR3-44: NPA Splits and the Number Pool Block Holder Information – Addition of a Block for an NPA-NXX involved in an 
NPA Split 
RR3-45: NPA Splits and the Number Pool Block Holder Information – Broadcast of a Block Create for an NPA-NXX involved 
in an NPA Split 
RR3-46: NPA Splits and the Number Pool Block Holder Information – Modification of a Block for an NPA-NXX involved in 
an NPA Split 
RR3-47: NPA Splits and the Number Pool Block Holder Information – Broadcast of a Block Modify Active for an NPA-NXX 
involved in an NPA Split 
RR3-48: NPA Splits and the Number Pool Block Holder Information – De-pooling of the Block during PDP 
RR3-49: NPA Splits and the Number Pool Block Holder Information – Mass Update that includes one or more Blocks for an 
NPA-NXX involved in an NPA Split 
RR3-50: NPA Splits and the Number Pool Block Holder Information – Broadcast of a Mass Update that includes one or 
more Blocks for an NPA-NXX involved in an NPA Split 
RR3-218: NPA Splits and the Number Pool Block Holder Information – Broadcast of Subscription Versions for an NPA-NXX 
involved in an NPA Split 
Page 17
(no answer)
Yes
No
3.6 STATEMENT:
TRD FRS Section 3: Sub Section 3.6: NPA-NXX Filter Management Requirements 
The FRS Section 3.6 requirements address NPAC/SMS Filter Management that allows for NPAC personnel and/or Service 
Providers to add, delete and query NPA and NPA NXX filters to manage information that is broadcast to a given Local 
SMS.
3.6.1* QUESTION:
TRD FRS Section 3: Sub Section 3.6.1: NPA-NXX Level Filters 
The following requirements address creation, deletion and querying of NPA-NXX level filters. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-5: Create Filtered NPA-NXX for a Local SMS 
RR3-6: Delete Filtered NPA-NXX for a Local SMS 
RR3-7: Query Filtered NPA-NXXs for a Local SMS 
RR3-8: Query Filtered NPA-NXXs - NPA-NXX Not Provided 
RR3-9: Query Filtered NPA-NXXs - NPA-NXX Provided 
RR3-768: Delete Filtered NPA-NXX - Deletion of NPA-NXX 
(no answer)
Yes
No
3.6.2* QUESTION:
TRD FRS Section 3: Sub Section 3.6.2: NPA Level Filters 
The following requirements address the creation, deletion and querying of NPA level filters. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-692: Create Filtered NPA for a Local SMS - Existing NPA-NXX not Required 
RR3-692.5: Create Filtered NPA for a Local SMS and SOA - Delete Subordinate NPA-NXXs 
RR3-693: Filtered NPA Behavior for a Local SMS 
Page 18
RR3-694: Delete Filtered NPA for a Local SMS 
RR3-695: Filtered NPA Behavior - Overlap Allowed 
RR3-696: Create Filtered NPA-NXX for a Local SMS - NPAC Personnel - Existing NPA-NXX Not Required 
(no answer)
Yes
No
3.7* QUESTION:
TRD FRS Section 3: Sub Section 3.7: Business Hour and Days Requirements 
The FRS Section 3.7 requirements are related to definition and processing of long, medium and short business hours and 
days for operations involving business time calculation including holidays. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date?
RR3-10: Business Hours and Days 
RR3-229: Short Business Days Tunable Parameter 
RR3-230: Short Business Days Tunable Parameter - Default Value 
RR3-231: Short Business Days Tunable Parameter - Valid Values 
RR3-232: Short Business Days Tunable Parameter - Modification 
RR3-498: Medium Business Days Tunable Parameter 
RR3-499: Medium Business Days Tunable Parameter - Default Value 
RR3-500: Medium Business Days Tunable Parameter - Valid Values 
RR3-501: Medium Business Days Tunable Parameter - Modification 
RR3-233: Long Business Days Tunable Parameter 
RR3-234: Long Business Days Tunable Parameter - Default Value 
RR3-235: Long Business Days Tunable Parameter - Valid Values 
RR3-236: Long Business Days Tunable Parameter - Modification 
RR3-12.1: Business Day Duration - Tunable Parameter 
RR3-12.2: Business Day Duration - Tunable Parameter Modification 
RR3-12.3: Short Business Day Duration - Tunable Parameter Default 
RR3-502: Medium Business Day Duration - Tunable Parameter Default 
RR3-12.4: Long Business Day Duration - Tunable Parameter Default 
RR3-13.1: Business Day Start Time - Tunable Parameter 
RR3-13.2: Business Day Start Time - Tunable Parameter Modification 
RR3-13.3: Short Business Day Start Time - Tunable Parameter Default 
RR3-503: Medium Business Day Start Time - Tunable Parameter Default 
RR3-13.4: Long Business Day Start Time - Tunable Parameter Default 
RR3-14: Business Holidays 
(no answer)
Yes
No
Page 19
3.8 STATEMENT:
TRD FRS Section 3: Sub Section 3.8: Notifications 
The FRS Section 3.8 requirements are related to TN range notification indicators, SP Concurrence notification indicators, 
SOA notifications, Attribute value change notifications, and Attribute flag indicators. 
3.8.1* QUESTION:
TRD FRS Section 3: Sub Section 3.8.1: TN Range : Notification Indicator 
The following requirements address notification indicators for TN ranges. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-237: NPAC Customer TN Range : Notification Indicator
RR3-238: NPAC Customer TN Range : Notification Indicator - Default 
RR3-239: NPAC Customer TN Range : Notification Indicator - Modification 
(no answer)
Yes
No
3.8.2* QUESTION:
TRD FRS Section 3: Sub Section 3.8.2: Customer No New Concurrence : Notification Indicator 
The following requirements address notification indicators when new provider concurrence is not provided. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-240: NPAC Customer No New SP Concurrence Notification Indicator 
RR3-241: NPAC Customer No New SP Concurrence Notification Indicator - Default 
RR3-242: NPAC Customer No New SP Concurrence Notification Indicator - Modification 
RR3-243: Subscription Version Information - Suppress Notification when Service Provider No New SP Concurrence 
Notification Indicator is False 
RR3-244: Subscription Version Information - Send Notification when Service Provider No New SP Concurrence Notification 
Indicator is True 
(no answer)
Yes
No
Page 20
3.8.3* QUESTION:
TRD FRS Section 3: Sub Section 3.8.3: SOA Notification Priority 
The following requirements address SOA notification priority elements. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-245: SOA Notification Priority Tunable Parameter 
RR3-246: SOA Notification Priority Based on Attributes 
RR3-247: SOA Notification Priority Tunable Parameter based on Old or New Service Provider Status 
RR3-248: SOA Notification Priority Tunable Parameter - Valid Values 
RR3-249: SOA Notification Priority Tunable Parameter - Default Value 
RR3-250 : Modifying the SOA Notification Priority Tunable Parameter Value 
RR3-251: SOA Notification Priority Processing 
RR3-252: SOA Notification Priority Tunable Parameter -Value Equal to NONE 
RR3-253: Processing of SOA Notification Queues 
(no answer)
Yes
No
3.8.4* QUESTION:
TRD FRS Section 3: Sub Section 3.8.4: TN and Number Pool Block In Notifications 
The following requirements address notifications related to TN and Number Pool Blocks. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-452: Subscription Version Status Attribute Value Change - Send TN 
RR3-453: Subscription Version Attribute Value Change - Send TN 
RR3-454: Number Pool Block Status Attribute Value Change - Send NPA-NXX-X
RR3-455: Number Pool Block Attribute Value Change - Send NPA-NXX-X 
RR3-456: Subscription Version TN Attribute Flag Indicator 
RR3-457: Modification of Subscription Version TN Attribute Flag Indicator 
RR3-458: Subscription Version TN Attribute Flag Indicator Default Value 
FRS Section 3: Sub Section 3.8.4: Requirement RR3-459: Number Pool Block NPA-NXX-X Attribute Flag Indicator 
RR3-460: Modification of Number Pool Block NPA-NXX-X Attribute Flag Indicator 
RR3-461: Number Pool Block NPA-NXX-X Attribute Flag Indicator Default Value 
(no answer)
Yes
No
Page 21
3.9 STATEMENT:
TRD FRS Section 3: Sub Section 3.9: Service Provider Support Indicators 
The FRS Section 3.9 requirements define service provider tunable features that indicate if a service provider system 
supports optional data functionality defined as part of NANC 399. 
3.9.1* QUESTION:
TRD FRS Section 3: Sub Section 3.9.1: SV Type and Alternative SPID Indicators 
The following requirements address indicators for SV Type and Alternative SPID. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-484: Service Provider SOA SV Type Edit Flag Indicator 
RR3-485: Service Provider SOA SV Type Edit Flag Indicator Default 
RR3-486: Service Provider SOA SV Type Edit Flag Indicator Modification 
RR3-487: Service Provider LSMS SV Type Edit Flag Indicator 
RR3-488: Service Provider LSMS SV Type Edit Flag Indicator Default 
RR3-489: Service Provider LSMS SV Type Edit Flag Indicator Modification 
RR3-490: Service Provider SOA Alternative SPID Edit Flag Indicator 
RR3-491: Service Provider SOA Alternative SPID Edit Flag Indicator Default 
RR3-492: Service Provider SOA Alternative SPID Edit Flag Indicator Modification 
RR3-493: Service Provider LSMS Alternative SPID Edit Flag Indicator 
RR3-494: Service Provider LSMS Alternative SPID Edit Flag Indicator Default 
RR3-495: Service Provider LSMS Alternative SPID Edit Flag Indicator Modification 
RR3-504: Service Provider SOA Last Alternative SPID Edit Flag Indicator 
RR3-505: Service Provider SOA Last Alternative SPID Edit Flag Indicator Default 
RR3-506: Service Provider SOA Last Alternative SPID Edit Flag Indicator Modification 
RR3-507: Service Provider LSMS Last Alternative SPID Edit Flag Indicator 
RR3-508: Service Provider LSMS Last Alternative SPID Edit Flag Indicator Default 
RR3-509: Service Provider LSMS Last Alternative SPID Edit Flag Indicator Modification 
(no answer)
Yes
No
3.9.2* QUESTION:
TRD FRS Section 3: Sub Section 3.9.2: Alternative-End User Location and Alternative Billing ID Indicators 
The following requirements define service provider tunable features that indicate if a service provider system supports 
optional data functionality defined as part of NANC 436. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
Page 22
RR3-510: Service Provider SOA Alt-End User Location Value Edit Flag Indicator 
RR3-511: Service Provider SOA Alt-End User Location Value Edit Flag Indicator Default 
RR3-512: Service Provider SOA Alt-End User Location Value Edit Flag Indicator Modification 
RR3-513: Service Provider SOA Alt-End User Location Type Edit Flag Indicator 
RR3-514: Service Provider SOA Alt-End User Location Type Edit Flag Indicator Default 
RR3-515: Service Provider SOA Alt-End User Location Type Edit Flag Indicator Modification 
RR3-516: Service Provider SOA Alt-Billing ID Edit Flag Indicator 
RR3-517: Service Provider SOA Alt-Billing ID Edit Flag Indicator Default 
RR3-518: Service Provider SOA Alt-Billing ID Edit Flag Indicator Modification 
(no answer)
Yes
No
3.9.3* QUESTION:
TRD FRS Section 3: Sub Section 3.9.3: URI Indicators 
The following requirements define service provider tunable features that indicate if a service provider system supports 
optional data functionality defined for URIs. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-519: Service Provider SOA Voice URI Edit Flag Indicator 
RR3-520: Service Provider SOA Voice URI Edit Flag Indicator Default 
RR3-521: Service Provider SOA Voice URI Edit Flag Indicator Modification 
RR3-522: Service Provider LSMS Voice URI Edit Flag Indicator 
RR3-523: Service Provider LSMS Voice URI Edit Flag Indicator Default 
RR3-524: Service Provider LSMS Voice URI Edit Flag Indicator Modification 
RR3-525: Service Provider SOA MMS URI Edit Flag Indicator 
RR3-526: Service Provider SOA MMS URI Edit Flag Indicator Default 
RR3-527: Service Provider SOA MMS URI Edit Flag Indicator Modification 
RR3-528: Service Provider LSMS MMS URI Edit Flag Indicator 
RR3-529: Service Provider LSMS MMS URI Edit Flag Indicator Default 
RR3-530: Service Provider LSMS MMS URI Edit Flag Indicator Modification 
RR3-531: Service Provider SOA SMS URI Edit Flag Indicator 
RR3-532: Service Provider SOA SMS URI Edit Flag Indicator Default 
RR3-533: Service Provider SOA SMS URI Edit Flag Indicator Modification 
RR3-534: Service Provider LSMS SMS URI Edit Flag Indicator 
RR3-535: Service Provider LSMS SMS URI Edit Flag Indicator Default 
RR3-536: Service Provider LSMS SMS URI Edit Flag Indicator Modification 
(no answer)
Yes
No
3.9.4* QUESTION:
Page 23
TRD FRS Section 3: Sub Section 3.9.4: Medium Timers Support Indicators 
The following requirements define service provider tunable features that indicate if a service provider system supports 
simple port medium timer functionality defined as part of NANC 440 and 441. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-537: Medium Timers Support Indicator 
RR3-538: Medium Timers Support Indicator Default 
RR3-539: Medium Timers Support Indicator Modification 
(no answer)
Yes
No
3.9.5* QUESTION:
TRD FRS Section 3: Sub Section 3.9.5: Pseudo-LRN Support Indicators 
The following requirements define service provider tunable features that indicate if a service provider system 
supports Pseudo-LRN functionality. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-719: Service Provider SOA Pseudo-LRN 
RR3-720: Service Provider SOA Pseudo-LRN Indicator Default 
RR3-721: Service Provider SOA Pseudo-LRN Indicator Modification 
RR3-722: Service Provider LSMS Pseudo-LRN Indicator 
RR3-723: Service Provider LSMS Pseudo-LRN Indicator Default 
RR3-724: Service Provider LSMS Pseudo-LRN Indicator Modification 
RR3-725: Service Provider SOA Pseudo-LRN Notification Indicator 
RR3-726: Service Provider SOA Pseudo-LRN Notification Indicator Default 
RR3-727: Service Provider SOA Pseudo-LRN Notification Indicator Modification 
RR3-728: Service Provider Low-Tech Interface Pseudo-LRN Support Flag Indicator 
RR3-729: Provider Low-Tech Interface Pseudo-LRN Support Flag Indicator Default 
RR3-730: Service Provider Low-Tech Interface Pseudo-LRN Support Flag Indicator Modification 
RR3-731: Service Provider SOA Force Pseudo-LRN BDD Indicator 
RR3-732: Service Provider SOA Force Pseudo-LRN BDD Indicator Default 
RR3-733: Service Provider SOA Force Pseudo-LRN BDD Indicator Modification 
RR3-734: Service Provider LSMS Force Pseudo-LRN BDD Indicator 
RR3-735: Service Provider LSMS Force Pseudo-LRN BDD Indicator Default 
RR3-736: Service Provider LSMS Force Pseudo-LRN BDD Indicator Modification 
(no answer)
Yes
No
Page 24
3.10* QUESTION:
TRD FRS Section 3: Sub Section 3.10: Multiple Service Provider IDs per SOA Association Requirements 
The FRS Section 3.10 requirements define the management of primary and associated Service Provider IDs per SOA 
association. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-16 : Addition of NPAC Customer Associated Service Provider Information 
RR3-17: Deletion of NPAC Customer Associated Service Provider Information 
RR3-18: NPAC Customer Associated Service Provider Information - SPID validation 
RR3-19 : NPAC Customer Associated Service Provider Information - Associated SPID 
A3-5 : Associated Service Provider Multiple Service Provider Ids 
RR3-20: NPAC Customer Associated Service Provider Information - Validation Error 
RR3-21: NPAC Deletion of Service Provider Validation 
RR3-22 : Association Rejection for Associated Service Provider Id 
RR3-23 : Associated Service Provider Id Use over a Primary Service Provider Id Association 
RR3-24: Validation of Old and New/Current for Associated Service Provider Id 
RR3-25: Use of Primary Service Provider Key List 
RR3-26: Notifications for Associated Service Providers 
C3-1: Associated Service Provider Notification Aggregation 
RR3-27: Filters for Associated Service Providers 
RR3-28: Associated Service Provider and Primary Service Provider messages 
RR3-29: Recovery for an Associated Service Provider 
(no answer)
Yes
No
3.11 STATEMENT:
TRD FRS Section 3: Sub Section 3.11: Bulk Data Download Functionality 
The FRS Section 3.11 requirements describe Bulk Data Download functionality supported by the NPAC/SMS. The NPAC 
can generate files for Network Data (including SPID, LRN, NPA-NXX and NPA-NXX-X), and Subscription Versions 
(including Number Pool Blocks). The NPAC/SMS also has the ability to process Bulk Data Download Response files from 
Service Providers. Separate SOA and LSMS Indicators for a Service Provider are available. 
3.11.1* QUESTION:
TRD FRS Section 3: Sub Section 3.11.1: Bulk Data Download Functionality - General 
The following requirements address general Bulk Data Download functionality. 
Page 25
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-220: Bulk Data Download File Creation 
RR3-221: Bulk Data Download - File Naming Convention 
RR3-222: Bulk Data Download - File Format 
RR3-223: Bulk Data Download - Selection Criteria for File Creation 
RR3-697: Bulk Data Download - Separate SOA and LSMS Indicators 
(no answer)
Yes
No
3.11.2* QUESTION:
TRD FRS Section 3: Sub Section 3.11.2: Network Data, Bulk Data Download 
The following requirements address network data information related to bulk data downloads.
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-224: Bulk Data Download - Required Selection Criteria for Network Data File Generation 
RR3-301: Network Data Information Bulk Download File Creation - Selection Criteria 
RR3-302: Network Data Information Bulk Download File Creation - All Network Data or Latest View of Network Data 
Activity Choice 
RR3-303: Network Data Information Bulk Download File Creation - Data in All Network Data Choice 
RR3-304: Network Data Information Bulk Download File Creation - Data in Latest View of Network Data Activity Choice 
RR3-305: Network Data Information Bulk Download File Creation - Time Range Fields 
RR3-306: Network Data Information Bulk Download File Creation - Time Range Fields and Network Data Data Model 
RR3-307: Network Data Information Bulk Download File Creation - Selection Criteria Combinations 
RR3-308: Network Data Information Bulk Data Download - Network Data Results 
RR3-309: Network Data Information Bulk Data Download - Network Data Results Sort Order 
RR3-310: Network Data Information Bulk Data Download - Filters for Network Data 
RR3-311: Network Data Information Bulk Data Download - Secure FTP Sub-Directory 
RR3-481: Service Provider Data Information Bulk Data Download - Support for Service Provider Type Data 
(no answer)
Yes
No
3.11.3* QUESTION:
TRD FRS Section 3: Sub Section 3.11.3: Subscription Version, Bulk Data Download 
The following requirements address subscription version information related to bulk data downloads. 
Page 26
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-225: Bulk Data Download -Required Selection Criteria for Subscription Data File Generation 
RR3-312: Subscription Version Information Bulk Download File Creation - Selection Criteria 
RR3-313: Subscription Version Information Bulk Download File Creation - Active/Disconnect Pending/Partial Failure 
Subscription Versions Only or Latest View of Subscription Version Activity Choice 
RR3-314: Subscription Version Information Bulk Download File Creation - Data in Active/Disconnect Pending/Partial 
Failure Subscription Versions Only Choice 
RR3-315: Subscription Version Information Bulk Download File Creation - Data in Latest View of Subscription Version 
Activity Choice 
RR3-316: Subscription Version Information Bulk Download File Creation - Time Range Fields 
RR3-317: Subscription Version Information Bulk Download File Creation - Time Range Fields and SV Data Model 
RR3-318: Subscription Version Information Bulk Download File Creation - TN Range Fields 
RR3-319: Subscription Version Information Bulk Download File Creation - Selection Criteria Combinations 
RR3-320: Subscription Version Information Bulk Data Download - Subscription Version Results 
RR3-321: Subscription Version Information Bulk Data Download - Subscription Version Results Sort Order 
RR3-322: Subscription Version Information Bulk Data Download - Filters for Subscription Versions 
RR3-323: Subscription Version Information Bulk Data Download - EDR LSMSs 
RR3-227: Bulk Data Download - Secure FTP Sub-Directory 
RR3-324: Bulk Download File Creation - Pooled Subscription Versions Filtered for EDR Local SMS 
RR3-737: Subscription Version Bulk Download File Creation for SOA - Pseudo-LRN Inclusion 
RR3-738: Subscription Version Bulk Download File Creation for LSMS - Pseudo-LRN Inclusion 
(no answer)
Yes
No
3.11.4* QUESTION:
TRD FRS Section 3: Sub Section 3.11.4: NPA-NXX-X Holder, Bulk Data Download 
The following requirements address NPA-NXX-X holder information related to bulk data downloads. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-116: Number Pool NPA-NXX-X Holder Information Bulk Download File - Separate File containing all NPA-NXX-X Data 
RR3-117: Number Pool NPA-NXX-X Holder Information Bulk Download File - Filters for NPA-NXX-X Data 
RR3-118: Number Pool NPA-NXX-X Holder Information Bulk Download File - Secure FTP Sub-Directory 
RR3-739: Number Pool NPA-NXX-X Holder Information Bulk Download File Creation for SOA - Pseudo-LRN Inclusion 
RR3-740: Number Pool NPA-NXX-X Holder Information Bulk Download File Creation for LSMS - Pseudo-LRN Inclusion 
(no answer)
Yes
No
Page 27
3.11.5* QUESTION:
TRD FRS Section 3: Sub Section 3.11.5: Block Holder, Bulk Data Downloads 
The following requirements address Number Pool Block holder information related to bulk data downloads.
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-198: Number Pool Block Holder Information Bulk Download File Creation - Blocks 
RR3-199: Number Pool Block Holder Information Bulk Download File Creation - Selection Criteria 
RR3-200.1: Number Pool Block Holder Information Bulk Download File Creation - Active and Partial Failure Blocks Only or 
Latest View of Block Activity Choice 
RR3-200.2: Number Pool Block Holder Information Bulk Download File Creation - Data in Active Blocks Only Choice 
RR3-200.3: Number Pool Block Holder Information Bulk Download File Creation - Data in Latest View of Block Activity 
Choice 
RR3-201.1: Number Pool Block Holder Information Bulk Download File Creation - Time Range Fields 
RR3-201.2: Number Pool Block Holder Information Bulk Download File Creation - Time Range Fields and Block Data Model 
RR3-202: Number Pool Block Holder Information Bulk Download File Creation - Block Range Fields 
RR3-203: Number Pool Block Holder Information Bulk Download File Creation - Selection Criteria Combinations 
RR3-204: Number Pool Block Holder Information Bulk Data Download - Block Results 
RR3-205: Number Pool Block Holder Information Bulk Data Download - Block Results Sort Order 
RR3-206: Number Pool Block Holder Information Bulk Data Download - Filters for Blocks 
RR3-207: Number Pool Block Holder Information Bulk Data Download - Secure FTP Sub-Directory 
RR3-741: Number Pool Block Holder Information Bulk Download File Creation for SOA - Pseudo-LRN Inclusion 
RR3-742: Number Pool Block Holder Information Bulk Download File Creation for LSMS - Pseudo-LRN Inclusion 
(no answer)
Yes
No
3.11.6* QUESTION:
TRD FRS Section 3: Sub Section 3.11.6: Notifications, Bulk Data Download 
The following requirements address notifications related to bulk data downloads. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-462: Notification BDD Selection Criteria Fields 
RR3-463: Notification BDD Required Selection Criteria 
RR3-464: Notification BDD File Name 
RR3-465: Notification BDD Time Range 
RR3-466: Notification BDD Results 
RR3-467: Notification BDD Sort Order 
RR3-468: Notification BDD Filters 
RR3-469: Notification BDD Secure FTP Sub-Directory 
RR3-540: Notification BDD Service Provider Timer Type Business Hours Attributes Indicator 
RR3-541: Notification BDD Service Provider Timer Type Business Hours Attributes Indicator Default 
RR3-542: Notification BDD Service Provider Timer Type Business Hours Attributes Indicator Modification 
Page 28
(no answer)
Yes
No
3.11.7* QUESTION:
TRD FRS Section 3: Sub Section 3.11.7: Bulk Data Download Response Files 
The following requirements address bulk data download response files. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-325: File Name Format for Service Provider BDD Response File 
RR3-326: File Contents for Service Provider BDD Response File 
RR3-327: Complete File Processing for Service Provider BDD Response File 
RR3-328: Processing of the Service Provider BDD Response File for Subscription Versions 
RR3-329: Removing a Service Provider from a Subscription Version Failed SP List 
RR3-330: Processing of the Service Provider BDD Response File for Number Pooling Blocks 
RR3-331: Removing a Service Provider from a Number Pooling Block Failed SP List 
RR3-332: Service Provider Not Found on the Failed SP List 
RR3-333: Validation of SPID in the Service Provider BDD Response File Against SPID of the Secure FTP Directory 
(no answer)
Yes
No
3.12 STATEMENT:
TRD FRS Section 3: Sub Section 3.12: NPA-NXX-X Information 
The FRS Section 3.12 requirements define how the NPAC/SMS provides a mechanism to indicate whether a Service 
Provider supports receiving the NPA-NXX-X data, by downloading this data to their SOA via the SOA to NPAC/SMS 
Interface, using the Number Pooling NPA-NXX-X and LSMS EDR indicators.
3.12.1* QUESTION:
TRD FRS Section 3: Sub Section 3.12.1: NPA-NXX-X Download Indicator Management 
The following requirements address management of NPA-NXX-X download indicators. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
Page 29
RR3-52: NPAC Customer SOA NPA-NXX-X Indicator 
RR3-53: NPAC Customer SOA NPA-NXX-X Indicator - Default 
RR3-54: NPAC Customer SOA NPA-NXX-X Indicator - Modification 
RR3-55: NPAC Customer LSMS NPA-NXX-X Indicator 
RR3-56: NPAC Customer LSMS NPA-NXX-X Indicator - Default 
RR3-57: NPAC Customer LSMS NPA-NXX-X Indicator - Modification 
RR3-58: NPAC Customer LSMS EDR Indicator 
RR3-59: NPAC Customer LSMS EDR Indicator - Default 
RR3-60: NPAC Customer LSMS EDR Indicator - Modification 
(no answer)
Yes
No
3.12.2* QUESTION:
TRD FRS Section 3: Sub Section 3.12.2: NPA-NXX-X Holder Information 
The following requirements address Number Pool Block NPA-NXX-X Holder information. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-61: Number Pool NPA-NXX-X Holder Information - NPAC Personnel OpGUI 
RR3-62: Number Pool NPA-NXX-X Holder Information - Service Provider Request 
RR3-63: Number Pool NPA-NXX-X Holder Information - NPA-NXX Validation 
RR3-65: Number Pool NPA-NXX-X Holder Information - Duplicate NPA-NXX-X Validation 
RR3-68: Number Pool NPA-NXX-X Holder Information - Service Provider Local SMS NPA-NXX-X Indicator Download of 
NPA-NXX-X Object 
RR3-69: Number Pool NPA-NXX-X Holder Information - Service Provider Local SMS NPA-NXX-X Indicator Suppression of 
Download of NPA-NXX-X Object
RR3-743: Number Pool NPA-NXX-X Holder Information - Service Provider Local SMS Pseudo-LRN Indicator Download of 
NPA-NXX-X Object 
RR3-70: Number Pool NPA-NXX-X Holder Information - Filters for NPA-NXX-X Download to the Local SMS 
RR3-71: Number Pool NPA-NXX-X Holder Information - Service Provider SOA NPA-NXX-X Indicator Download of NPA-NXX-
X Object 
RR3-72: Number Pool NPA-NXX-X Holder Information - Service Provider SOA NPA-NXX-X Indicator Suppression of 
Download of NPA-NXX-X Object
RR3-744: Number Pool NPA-NXX-X Holder Information - Service Provider SOA Pseudo-LRN Indicator Download of NPA-
NXX-X Object 
RR3-73: Number Pool NPA-NXX-X Holder Information - Filters for NPA-NXX-X Download to the SOA 
RR3-74: Number Pool NPA-NXX-X Holder Information - Validation Error 
(no answer)
Yes
No
3.12.3* QUESTION:
Page 30
TRD FRS Section 3: Sub Section 3.12.3: NPA-NXX-X Holder, NPAC Scheduling/Re-Scheduling of Block 
Creation 
The following requirements address NPA-NXX-X block holder scheduling and re-scheduling of block creations. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-75.1: Number Pool NPA-NXX-X Holder Information -OpGUI Entry Field for NPAC or SOA Origination 
RR3-75.2: Number Pool NPA-NXX-X Holder Information -OpGUI Entry Mechanism for Immediate or Scheduled Block 
Creation 
RR3-75.3: Number Pool NPA-NXX-X Holder Information -OpGUI Entry Field for Scheduled Date/Time 
RR3-76.1: Number Pool NPA-NXX-X Holder Information -Default for Scheduled Date/Time Entry Field 
RR3-76.2: Number Pool NPA-NXX-X Holder Information -Scheduled Date/Time Entry Field Validation 
RR3-77: Number Pool NPA-NXX-X Holder Information -Use of Scheduled Date/Time and NPAC Origination Entry Fields 
RR3-78: Number Pool NPA-NXX-X Holder Information - Routing Data for NPAC Origination 
RR3-79.1: Number Pool NPA-NXX-X Holder Information - Routing Data Field Level Validation 
RR3-79.2: Number Pool NPA-NXX-X Holder Information - Routing Data LRN Validation 
RR3-80.1: Number Pool NPA-NXX-X Holder Information - Modification of Block Create Event 
RR3-80.2: Number Pool NPA-NXX-X Holder Information - Modification of Scheduled Date/Time for Block Create Event 
RR3-80.3: Number Pool NPA-NXX-X Holder Information - Modification of Routing Data for Block Create Event 
RR3-81.1: Number Pool NPA-NXX-X Holder Information - Re-schedule of NPAC Initiated Block Create 
RR3-81.2: Number Pool NPA-NXX-X Holder Information - Re-schedule of Block Create Scheduling Options 
RR3-81.3: Number Pool NPA-NXX-X Holder Information - Re-schedule of Block Create Immediate Execution Edit Check 
RR3-82.1: Number Pool NPA-NXX-X Holder Information - Reject Re-schedule Based on Status 
RR3-82.2: Number Pool NPA-NXX-X Holder Information - Reject Re-schedule Based on Existing Block Create Event 
RR3-82.3: Number Pool NPA-NXX-X Holder Information - Validation Error for Schedule/Re-Schedule of Block Create Event 
RR3-83.1: Number Pool NPA-NXX-X Holder Information - Error Message for Pending-Like No-Active SVs during Block 
Create 
RR3-83.2: Number Pool NPA-NXX-X Holder Information - Pending-Like No-Active SVs Report Output Destinations 
RR3-83.3: Number Pool NPA-NXX-X Holder Information - Pending-Like No-Active SVs Report Output Destinations for 
Multiple Destinations 
RR3-83.4: Number Pool NPA-NXX-X Holder Information - Output Destination for Pending-Like No-Active SVs 
(no answer)
Yes
No
3.12.4* QUESTION:
TRD FRS Section 3: Sub Section 3.12.4: NPA-NXX-X Holder, Addition 
The following requirements address addition of Number Pooling NPA-NXX-X holder information. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-84: Addition of Number Pooling NPA-NXX-X Holder Information - Required Fields 
RR3-85: Addition of Number Pooling NPA-NXX-X Holder Information - SPID Validation 
Page 31
RR3-86: Addition of Number Pooling NPA-NXX-X Holder Information - Check for Pending-Like No-Active SVs 
RR3-87: Addition of Number Pooling NPA-NXX-X Holder Information - Check for Pending-Like Port-To-Original SVs 
RR3-88.1: Addition of Number Pooling NPA-NXX-X Holder Information - Error Message for Pending-Like No-Active SVs and 
Pending-Like Port-To-Original SVs 
RR3-88.2: Addition of Number Pooling NPA-NXX-X Holder Information -Pending-Like No-Active SVs and Pending-Like Port-
To-Original SVs Report Selection of Output Destinations 
RR3-88.3: Addition of Number Pooling NPA-NXX-X Holder Information -Pending-Like No-Active SVs and Pending-Like Port-
To-Original SVs Report Output Destinations for Multiple Destinations 
RR3-89: Addition of Number Pooling NPA-NXX-X Holder Information - Output Destination for Pending-Like No-Active SVs 
and Pending-Like Port-To-Original SVs 
RR3-482: Number Pooling NPA-NXX-X Holder Information Effective Date - Validation upon Addition 
RR3-745: Addition of Number Pooling NPA-NXX-X Holder Information - Active-LRN Number Pool Block Check for Pseudo-
LRN SVs 
RR3-93: Addition of Number Pooling NPA-NXX-X Holder Information Effective Date - OpGUI Default 
RR3-94: Addition of Number Pooling NPA-NXX-X Holder Information - Successful Validation 
(no answer)
Yes
No
3.12.5* QUESTION:
TRD FRS Section 3: Sub Section 3.12.5: NPA-NXX-X Holder, Modification 
The following requirements address modification of Number Pooling NPA-NXX-X holder information. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-95: Modification of Number Pool NPA-NXX-X Holder Information - Effective Date Modification from OpGUI 
RR3-96: Modification of Number Pool NPA-NXX-X Holder Information - Effective Date versus Current Date 
RR3-97: Modification of Number Pool NPA-NXX-X Holder Information - Effective Date Update to Scheduled Block Create 
RR3-483: Modification of Number Pool NPA-NXX-X Holder Information Effective Date - Validation 
RR3-746: Number Pool NPA-NXX-X Holder Information - Pseudo-LRN Indicator 
RR3-101: Modification of Number Pooling NPA-NXX-X Holder Information - Successful Validation 
(no answer)
Yes
No
3.12.6* QUESTION:
TRD FRS Section 3: Sub Section 3.12.6: NPA-NXX-X Holder, Deletion 
The following requirements address deletion of Number Pooling NPA-NXX-X holder information. 
Page 32
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-102: Deletion of Number Pool NPA-NXX-X Holder Information - NPA-NXX-X Data 
RR3-103: Deletion of Number Pool NPA-NXX-X Holder Information - Single NPA-NXX-X at a time from OpGUI 
RR3-104: Deletion of Number Pooling NPA-NXX-X Holder Information - Check for Pending-Like With Active POOL SVs 
RR3-105: Deletion of Number Pooling NPA-NXX-X Holder Information - Check for Port-to-Original SVs 
RR3-106: Deletion of Number Pooling NPA-NXX-X Holder Information - Check for non-Active Block 
RR3-107: Deletion of Number Pooling NPA-NXX-X Holder Information - Check for Sending SVs 
RR3-108.1: Deletion of Number Pooling NPA-NXX-X Holder Information - Error Message for Pending-Like With Active 
POOL SVs and Pending-Like Port-To-Original SVs 
RR3-108.2: Deletion of Number Pooling NPA-NXX-X Holder Information -Pending-Like With Active POOL SVs and Pending-
Like Port-To-Original SVs Report Selection of Output Destinations 
RR3-108.3: Deletion of Number Pooling NPA-NXX-X Holder Information -Pending-Like With Active POOL SVs and Pending-
Like Port-To-Original SVs Report Output Destinations for Multiple Destinations 
RR3-109: Deletion of Number Pooling NPA-NXX-X Holder Information - Output Destination for Pending-Like and Active 
POOL SVs and Pending-Like Port-To-Original SVs 
RR3-110: Deletion of Number Pool NPA-NXX-X Holder Information - Block and Subscription Version Data Dependency 
RR3-111: Deletion of Number Pool NPA-NXX-X Holder Information - NPA-NXX-X Dependency 
RR3-112: Deletion of Number Pool NPA-NXX-X Holder Information - NPA-NXX-X With an Associated Block Create 
Scheduled Event 
(no answer)
Yes
No
3.12.7* QUESTION:
TRD FRS Section 3: Sub Section 3.12.7: NPA-NXX-X Holder, First Port Notification 
The following requirements address First Port Notification of Number Pooling NPA-NXX-X holder information. 
Does the Respondent's proposal fully comply with the requirement below in time to meet the published 
implementation date? 
RR3-228: Number Pool NPA-NXX-X Holder information Notification of First Port 
(no answer)
Yes
No
3.12.8* QUESTION:
TRD FRS Section 3: Sub Section 3.12.8: NPA-NXX-X Holder, Query 
Page 33
The following requirements address querying of Number Pooling NPA-NXX-X holder information. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-113: Query of Number Pool NPA-NXX-X Holder Information - NPAC Personnel and Service Provider Personnel 
RR3-114: Query of Number Pool NPA-NXX-X Holder Information - Return of Queried Data 
RR3-115: Query of Number Pool NPA-NXX-X Holder Information - Return of Queried Data to NPAC Personnel Only 
RR3-747: Query of NPA-NXX-X Holder Information for Pseudo-LRN - Service Provider Personnel - SOA Interface 
RR3-748: Query of NPA-NXX-X Holder Information for Pseudo-LRN - Service Provider Personnel - LSMS Interface 
RR3-749: Query NPA-NXX-X Holder Information for Pseudo-LRN - Service Provider Personnel - LTI 
(no answer)
Yes
No
3.13 STATEMENT:
TRD FRS Section 3: Sub Section 3.13: Block Information 
The FRS Section 3.13 requirements define how the NPAC/SMS provides a mechanism to create, activate, modify, delete, 
query and validate pooled block records.
3.13.1 STATEMENT:
TRD FRS Section 3: Sub Section 3.13.1: Version Status 
This section includes a Number Pool Block Version Status Interaction diagram and descriptions that are described in 
further detail in the FRS document Section 3.13.1. 
3.13.2* QUESTION:
TRD FRS Section 3: Sub Section 3.13.2: Block Holder, General 
The following requirements address general Number Pool Block holder information. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-119: Number Pool Block Holder Information - NPAC Personnel OpGUI 
RR3-120: Number Pool Block Holder Information - NPAC Customer EDR Indicator Download of Block Object 
RR3-121: Number Pool Block Holder Information - NPAC Customer EDR Indicator Download of SVs 
RR3-122: Number Pool Block Holder Information - NPAC Customer EDR Indicator For Requests But Not Retries 
RR3-123: Number Pool Block Holder Information - Data Integrity for Block and Pooled Subscription Versions 
Page 34
RR3-124: Number Pool Block Holder Information - Service Provider Validation 
RR3-125: Number Pool Block Holder Information - SPID Validation 
RR3-126: Number Pool Block Holder Information - NPA-NXX-X Data Validation 
RR3-127: Number Pool Block Holder Information - NPA-NXX-X Effective Date 
RR3-128: Number Pool Block Holder Information - LRN Validation 
RR3-334: Validation of LATA ID for Number Pool Block Creates 
RR3-335: Validation of LATA ID for Number Pool Block Modifies 
RR3-129: Number Pool Block Holder Information - Duplicate Block Validation 
RR3-130: Number Pool Block Holder Information - SOA Origination Values 
RR3-750: Number Pool Block Holder Information - Service Provider Tunable Value of TRUE for Pseudo-LRN Request 
RR3-751: Number Pool Block Holder Information - Service Provider Validation for Pseudo-LRN Request of NPA-NXX 
Ownership 
RR3-752: Number Pool Block Holder Information - Type Validation for Pseudo-LRN and Active-LRN Request 
RR3-753: Number Pooling Block Holder Information - Broadcast of Block Data to EDR Local SMS for Pseudo-LRN 
RR3-754; Number Pooling Block Holder Information - Broadcast of Subscription Version Data to non-EDR Local SMS for 
Pseudo-LRN 
RR3-131: Number Pool Block Holder Information - Validation Error 
RR3-132: Number Pooling Block Holder Information -Update Notification 
RR3-133: Number Pooling Block Holder Information -Update Notification Suppression 
RR3-134: Number Pooling Block Holder Information - Failed SP List Update for Block for EDR Local SMS 
RR3-135: Number Pooling Block Holder Information - Failed SP List Update for Subscription Versions for non-EDR Local 
SMS 
RR3-136: Number Pooling Block Holder Information - Failed SP List Sent to Block Holder 
RR3-137.1: Number Pooling Block Holder Information - Synchronization of Block Status and Subscription Version Status 
RR3-137.2: Number Pooling Block Holder Information - Synchronization of Block Status and Subscription Version Status 
for Block Creation 
RR3-137.3: Number Pooling Block Holder Information - Synchronization of Block Status and Subscription Version Status 
for Block Modification 
RR3-137.4: Number Pooling Block Holder Information - Synchronization of Block Status and Subscription Version Status 
for Block Deletion 
RR3-138.1: Number Pooling Block Holder Information - Synchronization of Block Failed SP List and Subscription Version 
Failed SP List 
RR3-138.2: Number Pooling Block Holder Information - Synchronization of Block Failed SP List and Subscription Version 
Failed SP List for Block Creation, Modification, or Deletion 
RR3-139: Number Pooling Block Holder Information - Synchronization of Block Failed SP List and Subscription Version 
Failed SP List for the last failed Subscription Version in the 1K Block 
RR3-140: Number Pooling Block Holder Information - Synchronization of Block Failed SP List and Subscription Version 
Failed SP List for the Block 
RR3-141.1: Number Pooling Block Holder Information - Unique Error Message for Partial Failure or Failed Status Update 
to a Block for Block Activation Requests Initiated by NPAC Personnel 
RR3-141.3: Number Pooling Block Holder Information - Unique Error Message for Active Status With a Failed SP List 
Update to a Block 
RR3-141.4: Number Pooling Block Holder Information - Unique Error Message for Old Status With a Failed SP List Update 
to a Block 
RR3-142.1: Number Pooling Block Holder Information - Block Broadcast Monitoring Mechanism 
RR3-142.2: Number Pooling Block Holder Information - Block Broadcast Monitoring Mechanism Completion 
RR3-143: Number Pool Block Holder Information - Filters for Blocks
(no answer)
Yes
No
3.13.3* QUESTION:
Page 35
TRD FRS Section 3: Sub Section 3.13.3: Block Holder, Addition 
The following requirements address addition of Number Pool Block holder information. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-144: Addition of Number Pooling Block Holder Information 
RR3-145: Addition of Number Pool Block Holder Information - Rejected from LSMS 
RR3-146: Addition of Number Pooling Block Holder Information - Required Data 
RR3-147: Addition of Number Pooling Block Holder Information - Check for pending-like SVs for NPAC Personnel 
RR3-148: Addition of Number Pooling Block Holder Information - Error Message to SOA for pending-like SVs 
RR3-149: Addition of Number Pooling Block Holder Information - Field-level Data Validation 
RR3-698: Addition of Number Pooling Block Holder Information -DPC-SSN Field-level Data Validation 
RR3-699: Addition of Number Pooling Block Holder Information - Validation of DPC-SSNs for Number Pool Block Creates 
RR3-150: Addition of Number Pooling Block Holder Information - Broadcast of Block Data 
RR3-151: Addition of Number Pooling Block Holder Information - Activation Broadcast Complete Timestamp Update 
RR3-152: Addition of Number Pooling Block Holder Information - Status Update 
RR3-153: Addition of Number Pooling Block Holder Information - Failed SP List Update 
RR3-496: Activate Number Pool Block - Send Number Pool Block SV Type Data to Local SMSs 
RR3-497: Activate Number Pool Block - Send Alternative SPID to Local SMSs 
RR3-543: Activate Number Pool Block - Send Last Alternative SPID to Local SMSs 
RR3-544: Activate Number Pool Block - Send Alt-End User Location Value to Local SMSs 
RR3-545: Activate Number Pool Block - Send Alt-End User Location Type to Local SMSs 
RR3-546: Activate Number Pool Block - Send Alt-Billing ID to Local SMSs 
RR3-547: Activate Number Pool Block - Send Voice URI to Local SMSs 
RR3-548: Activate Number Pool Block - Send MMS URI to Local SMSs 
RR3-549: Activate Number Pool Block - Send SMS URI to Local SMSs 
RR3-755: Activate Number Pool Block - Send Notification of Activation of Pseudo-LRN Record 
(no answer)
Yes
No
3.13.4* QUESTION:
TRD FRS Section 3: Sub Section 3.13.4: Block Holder, Modification 
The following requirements address modification of Number Pool Block holder information. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-154: Block's SOA Origination Indicator - NPAC Personnel OpGUI 
RR3-155: Block's SOA Origination Indicator - Suppress Broadcast 
RR3-156: Block's SOA Origination Indicator - Suppress Creation When False 
RR3-157: Modification of Number Pooling Block Holder Information - Routing Data 
RR3-158: Modification of Number Pool Block Holder Information - Rejected from LSMS 
RR3-159: Modification of Number Pooling Block Holder Information - SPID Validation 
Page 36
RR3-160: Modification of Number Pooling Block Holder Information - Selection Criteria 
RR3-161: Modification of Number Pooling Block Holder Information - Current status and Failed SP List 
RR3-700: Modify Number Pool Block - DPC-SSN Field-level Data Validation 
RR3-701: Modify Number Pool Block - Validation of DPC-SSNs for Number Pool Block Modifies 
RR3-756: Number Pool Block Holder Information - Service Provider Tunable Value of TRUE for Pseudo-LRN Request 
RR3-162: Modification of Number Pooling Block Holder Information - Sending Status Update 
RR3-163: Modification of Number Pooling Block Holder Information - Broadcast of Block Data 
RR3-164: Modification of Number Pooling Block Holder Information - Modify Broadcast Complete Timestamp Update 
RR3-165: Modification of Number Pooling Block Holder Information -Status Update 
RR3-166: Modification of Number Pooling Block Holder Information - Failed SP List Update 
RR3-757: Modify Number Pool Block - Send Notification of Modification of Pseudo-LRN Record 
(no answer)
Yes
No
3.13.5* QUESTION:
TRD FRS Section 3: Sub Section 3.13.5: Block Holder, Deletion 
The following requirements address deletion of Number Pool Block holder information. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-169: Deletion of Number Pool Block Holder Information - NPAC 
RR3-170: Deletion of Number Pool Block Holder Information - SOA 
RR3-171: Deletion of Number Pool Block Holder Information - Rejected from LSMS 
RR3-172: Deletion of Number Pool Block Holder Information - LTI 
RR3-173: Deletion of Number Pooling NPA-NXX-X Holder Information - Sending Status Update to Block 
RR3-174: Deletion of Number Pool NPA-NXX-X Holder Information - Broadcast of Block Data 
RR3-175: Deletion of Number Pooling Block Holder Information - Disconnect Complete Timestamp Update 
RR3-176: Deletion of Number Pooling NPA-NXX-X Holder Information - Status Update to Block 
RR3-177: Deletion of Number Pooling NPA-NXX-X Holder Information - Failed SP List Update 
RR3-758: Deletion of Number Pool Block Holder Information - Send Notification of Disconnect of Pseudo-LRN Record 
(no answer)
Yes
No
3.13.6* QUESTION:
TRD FRS Section 3: Sub Section 3.13.6: Block Holder, Query 
The following requirements address querying of Number Pool Block holder information. 
Page 37
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-180: Query of Number Pool Block Holder Information - NPAC Personnel 
RR3-181: Query of Number Pool Block Holder Information - Service Provider Personnel 
RR3-182: Query of Number Pool Filtered Block Holder Information - Query Block 
RR3-759: Query of Number Pool Block Holder Information for Pseudo-LRN - Service Provider Personnel - SOA Interface 
RR3-760: Query of Number Pool Block Holder Information for Pseudo-LRN - Service Provider Personnel - LSMS Interface 
RR3-761: Query of Number Pool Block Holder Information for Pseudo-LRN - Service Provider Personnel - LTI 
(no answer)
Yes
No
3.13.7* QUESTION:
TRD FRS Section 3: Sub Section 3.13.7: Block Holder, Default Routing Restoration 
The following requirements address default routing restoration information in the Number Pool Block holder information. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-183: Number Pool Block Holder Information Use of Number Pool Default Routing Information – Existing Block 
RR3-184: Number Pool Block Holder Information Use of Number Pool : Notification of TN Re-assignment – During De-
Pooling 
(no answer)
Yes
No
3.13.8* QUESTION:
TRD FRS Section 3: Sub Section 3.13.8: Block Holder, Re-Send 
The following requirements address re-sending of Number Pool Block holder information. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-185: Re-Send of Number Pool Block Holder Information - Filters for Blocks 
RR3-186.1: Re-Send of Number Pooling Block Holder Information - NPAC Personnel OpGUI Single Block 
RR3-186.2: Re-Send of Number Pooling Block Holder Information - NPAC Personnel OpGUI One or All Service Providers 
RR3-187: Re-Send of Number Pooling Block Holder Information - Use of EDR Indicator for Re-Send data 
RR3-188: Re-Send of Number Pooling Block Holder Information - Re-Send to EDR Local SMS 
RR3-189: Re-Send of Number Pooling Block Holder Information - Re-Send to non-EDR Local SMS 
Page 38
RR3-190: Re-Send of Number Pooling Block Holder Information - Failed Block Status Set to Sending 
RR3-191: Re-Send of Number Pooling Block Holder Information - Partial Failure Block Status Set to Sending 
RR3-192: Re-Send of Number Pooling Block Holder Information - Sending Status Update to Active Block 
RR3-193: Re-Send of Number Pooling Block Holder Information - Sending Status Update to Old Block 
RR3-194: Re-Send of Number Pool Block Holder Information - Broadcast of Block Data 
RR3-195: Re-Send of Number Pooling Block Holder Information - Update to Failed SP List 
RR3-196: Re-Send of Number Pooling Block Holder Information -Status Update to Block after Re-Send 
RR3-197: Re-Send of Number Pooling Block Holder Information - Failed SP List Update 
RR3-472: Number Pool Block Failed SP List - Exclusion of a Service Provider from Resend 
RR3-473: Number Pool Block Failed SP List - Logging of an Excluded Service Provider 
(no answer)
Yes
No
3.14* QUESTION:
TRD FRS Section 3: Sub Section 3.14: Linked Action Replies 
The FRS Section 3.14 requirements define tunable parameters that enable Linked Action Replies to be sent to Service 
Provider systems that support this functionality, during recovery. The actual Linked Reply functionality is discussed 
specifically within the Recovery section. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-336: NPAC Customer SOA Linked Replies Indicator 
RR3-337: NPAC Customer SOA Linked Replies Indicator - Default 
RR3-338: NPAC Customer SOA Linked Replies Indicator - Modification 
RR3-339: NPAC Customer Local SMS Linked Replies Indicator 
RR3-340: NPAC Customer Local SMS Linked Replies Indicator - Default 
RR3-341: NPAC Customer Local SMS Linked Replies Indicator - Modification 
RR3-342: Service Provider and Network Data Linked Replies Blocking Factor - Tunable Parameter 
RR3-343: Service Provider and Network Data Linked Replies Blocking Factor - Tunable Parameter Default 
RR3-344: Service Provider and Network Data Linked Replies Blocking Factor - Tunable Parameter Modification 
RR3-345: Subscription Data Linked Replies Blocking Factor - Tunable Parameter 
RR3-346: Subscription Data Linked Replies Blocking Factor - Tunable Parameter Default 
RR3-347: Subscription Data Linked Replies Blocking Factor - Tunable Parameter Modification 
RR3-348: Notification Data Linked Replies Blocking Factor - Tunable Parameter 
RR3-349: Notification Data Linked Replies Blocking Factor - Tunable Parameter Default 
RR3-350: Notification Data Linked Replies Blocking Factor - Tunable Parameter Modification 
RR3-430: Number Pool Block Data Linked Replies Blocking Factor - Tunable Parameter 
RR3-431: Number Pool Block Data Linked Replies Blocking Factor - Tunable Parameter Default 
RR3-432: Number Pool Block Data Linked Replies Blocking Factor - Tunable Parameter Modification 
RR3-351: Service Provider and Network Data Maximum Linked Recovered Objects - Tunable Parameter 
RR3-352: Service Provider and Network Data Maximum Linked Recovered Objects - Tunable Parameter Default 
RR3-353: Service Provider and Network Data Maximum Linked Recovered Objects - Tunable Parameter Modification 
RR3-354: Subscription Data Maximum Linked Recovered Objects - Tunable Parameter 
RR3-355: Subscription Data Maximum Linked Recovered Objects - Tunable Parameter Default 
RR3-356: Subscription Data Maximum Linked Recovered Objects - Tunable Parameter Modification 
RR3-357: Notification Data Maximum Linked Recovered Notifications - Tunable Parameter 
RR3-358: Notification Data Maximum Linked Recovered Notifications - Tunable Parameter Default 
Page 39
RR3-359: Notification Data Maximum Linked Recovered Notifications - Tunable Parameter Modification 
RR3-433: Number Pool Block Data Maximum Linked Recovered Objects - Tunable Parameter 
RR3-434: Number Pool Block Data Maximum Linked Recovered Objects - Tunable Parameter Default 
RR3-435: Number Pool Block Data Maximum Linked Recovered Objects - Tunable Parameter Modification 
(no answer)
Yes
No
3.15 STATEMENT:
TRD FRS Section 3: Sub Section 3.15: GTT Validation Processing by the NPAC/SMS 
The FRS Section 3.15 requirements describe how the NPAC/SMS performs a variety of GTT validation for Subscription 
Versions and Number Pool Blocks in an effort to support SS7 signaling guidelines for Local Number Portability. Some GTT 
validation occurs based on regional tunables that reflect inter-Service Provider service level agreements, while other 
validations occur globally regardless of any tunable setting. 
3.15.1* QUESTION:
TRD FRS Section 3: Sub Section 3.15.1: Sub System Number (SSN) Edit Flag Indicator 
The following requirements address Sub System Number Edit flag indicators related to DPC/SSN edits. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-360: DPC/SSN Edits - CLASS SSN Edit Flag Indicator 
RR3-361: DPC/SSN Edits - LIDB SSN Edit Flag Indicator 
RR3-362: DPC/SSN Edits - CNAM SSN Edit Flag Indicator 
RR3-363: DPC/SSN Edits - ISVM SSN Edit Flag Indicator 
RR3-364: DPC/SSN Edits - WSMSC SSN Edit Flag Indicator 
RR3-365: DPC/SSN Edits - CLASS SSN Edit Flag Indicator - OpGUI Modification 
RR3-366: DPC/SSN Edits - LIDB SSN Edit Flag Indicator - OpGUI Modification 
RR3-367: DPC/SSN Edits - CNAM SSN Edit Flag Indicator - OpGUI Modification 
RR3-368: DPC/SSN Edits - ISVM SSN Edit Flag Indicator - OpGUI Modification 
RR3-369: DPC/SSN Edits - WSMSC SSN Edit Flag Indicator - OpGUI Modification 
RR3-370: DPC/SSN Edits - CLASS SSN Edit Flag Indicator Default 
RR3-371: DPC/SSN Edits - LIDB SSN Edit Flag Indicator Default 
RR3-372: DPC/SSN Edits - CNAM SSN Edit Flag Indicator Default 
RR3-373: DPC/SSN Edits - ISVM SSN Edit Flag Indicator Default 
RR3-374: DPC/SSN Edits - WSMSC SSN Edit Flag Indicator Default
RR3-375: DPC/SSN Edits - CLASS SSN Rejection for Non-Zero Value 
RR3-376: DPC/SSN Edits - LIDB SSN Rejection for Non-Zero Value 
RR3-377: DPC/SSN Edits - CNAM SSN Rejection for Non-Zero Value 
RR3-378: DPC/SSN Edits - ISVM SSN Rejection for Non-Zero Value 
RR3-379: DPC/SSN Edits - WSMSC SSN Rejection for Non-Zero Value 
Page 40
(no answer)
Yes
No
3.15.2* QUESTION:
TRD FRS Section 3: Sub Section 3.15.2: Global GTT Validations 
The following requirements address global GTT validations. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-380: Subscription Version - Verify CLASS SSN when CLASS DPC is populated 
RR3-381: Subscription Version - Verify LIDB SSN when LIDB DPC is populated 
RR3-382: Subscription Version - Verify CNAM SSN when CNAM DPC is populated 
RR3-383: Subscription Version - Verify ISVM SSN when ISVM DPC is populated 
RR3-384: Subscription Version - Verify WSMSC SSN when WSMSC DPC is populated 
RR3-385: Subscription Version - Verify CLASS DPC when CLASS SSN is populated 
RR3-386: Subscription Version - Verify LIDB DPC when LIDB SSN is populated 
RR3-387: Subscription Version - Verify CNAM DPC when CNAM SSN is populated 
RR3-388: Subscription Version - Verify ISVM DPC when ISVM SSN is populated 
RR3-389: Subscription Version - Verify WSMSC DPC when WSMSC SSN is populated 
RR3-390: Number Pool Block - Verify CLASS SSN when CLASS DPC is populated 
RR3-391: Number Pool Block - Verify LIDB SSN when LIDB DPC is populated 
RR3-392: Number Pool Block - Verify CNAM SSN when CNAM DPC is populated 
RR3-393: Number Pool Block - Verify ISVM SSN when ISVM DPC is populated 
RR3-394: Number Pool Block - Verify WSMSC SSN when WSMSC DPC is populated 
RR3-395: Number Pool Block - Verify CLASS DPC when CLASS SSN is populated 
RR3-396: Number Pool Block - Verify LIDB DPC when LIDB SSN is populated 
RR3-397: Number Pool Block - Verify CNAM DPC when CNAM SSN is populated 
RR3-398: Number Pool Block - Verify ISVM DPC when ISVM SSN is populated 
RR3-399: Number Pool Block - Verify WSMSC DPC when WSMSC SSN is populated 
RR3-400: DPC/SSN Edits - CLASS validation failure 
RR3-401: DPC/SSN Edits - LIDB validation failure 
RR3-402: DPC/SSN Edits - CNAM validation failure 
RR3-403: DPC/SSN Edits - ISVM validation failure 
RR3-404: DPC/SSN Edits - WSMSC validation failure 
RR3-405: DPC/SSN Edits - CLASS DPC and SSN Required Data for Modification 
RR3-406: DPC/SSN Edits - LIDB DPC and SSN Required Data for Modification 
RR3-407: DPC/SSN Edits - CNAM DPC and SSN Required Data for Modification 
RR3-408: DPC/SSN Edits - ISVM DPC and SSN Required Data for Modification 
RR3-409: DPC/SSN Edits - WSMSC DPC and SSN Required Data for Modification 
RR3-410: DPC/SSN Edits - CLASS DPC and SSN Required Data for Mass Update
RR3-411: DPC/SSN Edits - LIDB DPC and SSN Required Data for Mass Update 
RR3-412: DPC/SSN Edits - CNAM DPC and SSN Required Data for Mass Update 
RR3-413: DPC/SSN Edits - ISVM DPC and SSN Required Data for Mass Update 
RR3-414: DPC/SSN Edits - WSMSC DPC and SSN Required Data for Mass Update 
RR3-415: Subscription Version - Verify All Routing Data When Modifying Non-GTT Data 
RR3-416: Subscription Version - Verify All Routing Data When Modifying CLASS Data 
RR3-417: Subscription Version - Verify All Routing Data When Modifying LIDB Data 
RR3-418: Subscription Version - Verify All Routing Data When Modifying CNAM Data 
Page 41
RR3-419: Subscription Version - Verify All Routing Data When Modifying ISVM Data 
RR3-420: Subscription Version - Verify All Routing Data When Modifying WSMSC Data 
RR3-421: Number Pool Block - Verify All Routing Data When Modifying Non-GTT Data 
RR3-422: Number Pool Block - Verify All Routing Data When Modifying CLASS Data 
RR3-423: Number Pool Block - Verify All Routing Data When Modifying LIDB Data 
RR3-424: Number Pool Block - Verify All Routing Data When Modifying CNAM Data 
RR3-425: Number Pool Block - Verify All Routing Data When Modifying ISVM Data 
RR3-426: Number Pool Block - Verify All Routing Data When Modifying WSMSC Data 
RR3-427: Subscription Version - Verify All Routing Data When Activating a Subscription Version 
RR3-428: Number Pool Block - Verify All Routing Data When Activating a Number Pool Block 
RR3-429: DPC/SSN Edits - Errors on DPC and SSN Required Data for Mass Update 
(no answer)
Yes
No
3.16* QUESTION:
TRD FRS Section 3: Sub Section 3.16: Low-Tech Interface DPC-SSN Validation Processing by the 
NPAC/SMS 
These FRS Section 3.16 requirements describe how the NPAC/SMS performs DPC-SSN validation for Subscription Versions 
and Number Pool Blocks that are submitted via the Low-Tech Interface or NPAC Administrative Interface. This validation 
occurs based on regional tunables. These edits ensure that values specified are valid according to the Service Provider 
DPC source data. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR3-702: Regional LTI DPC-SSN Validation Indicator - Tunable Parameter 
RR3-703: Regional LTI DPC-SSN Validation Indicator - Tunable Parameter Default 
RR3-704: Regional LTI DPC-SSN Validation Indicator - Tunable Parameter Modification 
RR3-705: DPC-SSN Entries Information Source for LTI or NPAC Personnel entries 
RR3-706: DPC-SSN Entries Information Maintenance 
RR3-707: DPC-SSN Entries Information - Multiple Entries 
(no answer)
Yes
No
4. TRD FRS Section 4: SERVICE PROVIDER DATA ADMINISTRATION
Page 42
4.1* QUESTION:
TRD FRS Section 4: Sub Section 4.1: Service Provider Data Administration and Management 
Service Provider Data Administration functions allow NPAC personnel to receive and record data needed to identify 
authorized LNP Service Providers. The Service Provider data indicates the LNP Service Providers and includes location, 
contact name, security, routing, and network interface information. 
Service Provider Administration supports functionality to manage Service Provider data. There can be only one instance 
of Service Provider data for a specific LNP Service Provider. 
Does the Respondent's proposal fully comply with the requirement below in time to meet the published 
implementation date? 
AR1-1: Service Provider ID 
(no answer)
Yes
No
4.1.1* QUESTION:
TRD FRS Section 4: Sub Section 4.1.1: User Functionality 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
R4-1: Create Service Providers 
R4-2: Modify Service Providers 
R4-3: Delete Service Providers 
R4-4: View of Service Provider Data 
R4-5.1: View List of Service Provider Subscriptions 
R4-5.2: Authorized Service Providers View Their Own Data 
RX4-2: Authorized Service Providers Modify Their Own Data 
RR4-4.1: Broadcast NPAC Customer Names 
(no answer)
Yes
No
4.1.2 STATEMENT:
TRD FRS Section 4: Sub Section 4.1.2: System Functionality 
Page 43
This section describes NPAC/SMS functionality required to support the NPAC personnel requests described in the above 
section. The following specifies user requests and lists the NPAC/SMS functionality needed to support those requests. 
 
4.1.2.1* QUESTION:
TRD FRS Section 4: Sub Section 4.1.2.1: Service Provider Data Creation 
NPAC personnel can request that Service Provider data be created in the NPAC/SMS. The functionality described below 
enables a new instance of Service Provider data for a Service Provider to be created, provided that no other Service 
Provider data exists for the Service Provider. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
R4-6: New Service Provider ID 
R4-7.1: Examine for Duplicate Service Provider ID 
R4-7.2: Error notification of Duplicate Service Provider 
R4-8: Service Provider Data Elements 
R4-9: Service Provider data validation 
R4-10: Notification of successful add for new Service Provider 
R4-11: Failure notification of Service Provider creation 
RR4-9: Service Provider Type SOA Indicator 
RR4-10: Service Provider Type SOA Indicator Default 
RR4-11: Service Provider Type SOA Indicator Modification 
RR4-12: Service Provider Type LSMS Indicator 
RR4-13: Service Provider Type LSMS Indicator Default 
RR4-14: Service Provider Type LSMS Indicator Modification 
RR4-15: Service Provider Type Attribute Modification Restriction 
(no answer)
Yes
No
 
4.1.2.2* QUESTION:
TRD FRS Section 4: Sub Section 4.1.2.2: Service Provider Data Modification 
NPAC personnel and the SOA to NPAC/SMS interface and the NPAC/SMS to Local SMS interface can request that Service 
Provider data be modified in the NPAC/SMS. The functionality described below enables the user to modify data for the 
Service Provider. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
R4-13: Service Provider Key selection for modifying Service Provider data 
R4-14: Error notification of invalid Service Provider ID or Name during Modify 
R4-15.1: Modify restrictions on Service Provider data - Service Providers 
R4-15.2: Modify restrictions on Service Provider data - NPAC Operations Personnel 
Page 44
R4-16: Re-validation of Service Provider data after Modify 
R4-17: Modify Validation Error Message 
(no answer)
Yes
No
 
4.1.2.3* QUESTION:
TRD FRS Section 4: Sub Section 4.1.2.3: Delete Service Provider Data 
NPAC personnel can request that the Service Provider data be deleted. Deleted Service Provider data will be written to a 
history file. The functionality described below enables a user to delete data for the Service Provider. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
R4-20: Service Provider key for delete 
R4-21: Error Message for Delete key search 
R4-22.1: No Subscription Versions during Service Provider Delete 
R4-22.2: Subscription during Service Provider Delete 
R4-22.3: Service Provider subscription restrictions during Network Data Delete. 
(no answer)
Yes
No
4.1.3 STATEMENT:
TRD FRS Section 4: Sub Section 4.1.3: Service Provider Queries 
The query functionality discussed in this section will give users the ability to view Service Provider and Subscription data. 
A user may not be able to modify a particular data item because they do not have the proper security permissions, 
therefore the data is made available via NPAC/SMS for read only purposes. 
4.1.3.1* QUESTION:
TRD FRS Section 4: Sub Section 4.1.3.1: User Functionality 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
R4-24.1: Display of Service Provider ID and related subscription data 
R4-24.2: Display of LRN and related subscription data 
R4-24.3: Display of NPA-NXX and related subscription data 
Page 45
(no answer)
Yes
No
 
4.1.3.2* QUESTION:
TRD FRS Section 4: Sub Section 4.1.3.2: System Functionality 
The following specifies NPAC/SMS functionality needed to support the user requests described above in TRD FRS Section 
4: Sub Section 4.1.3. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
R4-25: Service Provider as Key for queries 
R4-26.1: Error message for unknown Service Provider during a query 
R4-26.2: Results returned to Service Provider during a query 
R4-27: Service Provider Query Types 
R4-28: Service Provider Information Message during query 
RR4-16: Service Provider Data Information Service Provider Query - Support for Service Provider Type Data 
(no answer)
Yes
No
4.1.4* QUESTION:
TRD FRS Section 4: Sub Section 4.1.4: Service Provider Accepted SPID List 
Pseudo-LRN functionality allows a Service Provider to specify the list of SPID (including their own) that they wish to 
receive pseudo-LRN records in a download from the NPAC/SMS. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR4-17: Add SPID to Pseudo-LRN Accepted SPID List by NPAC Personnel on behalf of a Service Provider 
RR4-18: Delete SPID from Pseudo-LRN Accepted SPID List by NPAC Personnel on behalf of a Service Provider 
RR4-19: Query SPID from Pseudo-LRN Accepted SPID List by NPAC Personnel on behalf of a Service Provider 
(no answer)
Yes
No
Page 46
4.2* QUESTION:
TRD FRS Section 4: Sub Section 4.2: Additional Requirements 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RN4-1: Service Provider Network Data Addition/Deletion 
RR4-1: Removal of Service Provider with Respect to LRNs 
RR4-2: Removal of Service Provider with Respect to NPA-NXXs 
RR4-3.1: Removal of NPA-NXX - Subscription Version Check 
RR4-3.2: Removal of NPA-NXX - NPA-NXX-X Check 
RR4-4.2.1: Removal of LRN - Subscription Version Check 
RR4-4.2.2: Removal of LRN - Block Check 
RR4-5: Duplicate NPA-NXX Validation 
RR4-6: Duplicate NPA-NXX Validation - Error Processing 
RR4-7: Duplicate LRN Validation 
RR4-8: Duplicate LRN Validation - Error Processing 
(no answer)
Yes
No
5. TRD FRS Section 5 SUBSCRIPTION MANAGEMENT
5.1* QUESTION:
TRD FRS Section 5: Sub Section 5.1: Subscription Version Management 
Subscription Management functions allow NPAC personnel and SOA to NPAC/SMS interface users to specify data needed 
for ported numbers. The subscription data indicates how local number portability should operate to meet subscribers' 
needs. These functions will be accessible to authorized service providers via an interface (i.e., the SOA to NPAC SMS 
interface) from their operations systems to the NPAC/SMS and will also be accessible to (and performed by) NPAC 
personnel. 
Subscription Management supports functionality to manage multiple versions of subscription data. See Section 5.1.1, 
Subscription Version Management, for more details on the different states of a version. 
Does the Respondent's proposal fully comply with these requirements below in time to meet the published 
implementation date? 
RN5-1: Subscription Version Status - Only One Per Subscription 
RN5-2: Subscription Version Status - Only One Active Version 
RN5-3: Subscription Version Status - Multiple Old/Canceled 
RR5-113: TN Range Notification Information - Service Provider TN Range Notification Indicator Sending of TN Range 
Notifications 
RR5-114: TN Range Notification Information - Service Provider TN Range Notification Indicator Suppression of TN Range 
Notifications 
Page 47
AR5-3: Changing of TN Range Notification Indicator while Notifications are Queued 
RR5-115: TN Range Notification Information - Single TN Range Notifications 
RR5-116: TN Range Notification Information - Breakup of TN Range Notifications 
RR5-173: TN Range Notification Information - Breakup of TN Range Notifications 
(no answer)
Yes
No
5.1.1 STATEMENT:
TRD FRS Section 5: Sub Section 5.1.1: Subscription Version Management 
Subscription Version management provides functionality to manage multiple time sensitive views of subscription data. 
This section addresses version management for LNP and the user and system functionality needed for subscription 
administration. In this context a version may be defined as time sensitive subscription data. 
At any given time, a Subscription Version in the SMS can have one of several statuses (e.g., active, old) and may change 
status depending on results of different SMS processes (e.g., modification, activation). This section describes the different 
statuses that a version can have and the SMS processes that can change the status. This section also discusses 
functionality and data that is needed for Subscription Management. 
 
5.1.1.1* QUESTION:
TRD FRS Section 5: Sub Section 5.1.1.1: Version Status 
This section references Subscription Version Status Interaction Descriptions and Diagrams. (Figure 5-1 and Table 5-1) 
Does the Respondent's proposal fully comply with these requirements below in time to meet the published 
implementation date? 
R5 1.1: Subscription Version Statuses 
R5-2.1: Old Subscription Retention - Tunable Parameter 
R5-2.2: Old Subscription Retention - Tunable Parameter Modification 
R5-2.3: Old Subscription Retention - Tunable Parameter Default 
R5-3.1: Cancel-Pending Subscription Retention - Tunable Parameter 
R5-3.2: Cancel-Pending Subscription Retention - Tunable Parameter Modification 
R5-3.3: Cancel-Pending Subscription Retention - Tunable Parameter Default 
R5-3.4: Cancel-Conflict Subscription Retention - Tunable Parameter 
R5-3.5: Cancel-Conflict Subscription Retention - Tunable Parameter Modification 
R5-3.6: Cancel-Conflict Subscription Retention - Tunable Parameter Default 
RR5-1.1: Pending Subscription Retention - Tunable Parameter 
RR5-1.2: Pending Subscription Retention - Tunable Parameter Modification 
RR5-1.3: Pending Subscription Retention - Tunable Parameter Default 
RR5-1.4: Pending Subscription Retention - Tunable Parameter Expiration 
R5-5: Subscription Versions Creation for TN Ranges 
R5-6: Subscription Administration Transaction Logging 
RR5-182: Create/Modify Subscription Version - Medium Timers - Timer Type 
RR5-183: Create/Modify Subscription Version - Medium Timers - Business Type 
Page 48
(no answer)
Yes
No
5.1.2 STATEMENT:
TRD FRS Section 5: Sub Section 5.1.2: Subscription Administration Requirements 
 
5.1.2.1* QUESTION:
TRD FRS Section 5: Sub Section: 5.1.2.1: User Functionality 
Does the Respondent's proposal fully comply with these requirements below in time to meet the published 
implementation date? 
R5-7: Creating a Subscription Version 
RR5-55: Create Pending Provider Port - NPAC Personnel or Service Provider After Block Activation 
R5 8.1: Modifying a Subscription Version 
R5-9: Activating a Subscription version 
R5-10.1: Setting a Subscription Version to Conflict 
R5-10.2: Subscription Version Conflict Status Rule 
R5-11: Disconnecting a Subscription Version 
R5-12: Canceling a Subscription Version 
R5-13: Querying a Subscription Version 
RR5-197: Create Subscription Version - Validation of DPC-SSNs for Subscription Version Creates 
(no answer)
Yes
No
5.1.2.2 STATEMENT:
TRD FRS Section 5: Sub Section 5.1.2.2: System Functionality 
This section describes NPAC/SMS functionality required to support NPAC personnel and SOA to NPAC/SMS interface user 
requests defined in the above section. 
 
5.1.2.2.1* QUESTION:
TRD FRS Section 5: Sub Section 5.1.2.2.1: Subscription Version Creation 
Page 49
This section provides the requirements for the Subscription Version Create functionality, which is executed upon the user 
requesting to create a Subscription Version. 
Does the Respondent's proposal fully comply with these requirements in time to meet the published 
implementation date? 
RR5-3: Create Subscription Version - Notify NPA-NXX First Usage 
RR5-53: Create Subscription Version - Notify NPA-NXX First Usage of a New NPA-NXX involved in an NPA Split 
RR5-120: Validation of LATA ID for Subscription Version Creates 
RR5-130: Create "Porting to Original" Subscription Version - New Service Provider ID and Code Holder Match 
RR5-162: Addition of Subscription Version Due Date - Validation 
(no answer)
Yes
No
 
5.1.2.2.1.1* QUESTION:
TRD FRS Section 5: Sub Section 5.1.2.2.1.1: Subscription Version Creation - Inter-Service Provider Ports 
This section provides the Subscription Version Creation requirements for performing an Inter-Service Provider port of a 
TN. There are two types of Inter-Service Provider ports: A port of a TN to a new Service Provider from the Old, or a 
"porting to original" port. A "porting to original" port implies that all porting data will be removed from the Local SMSs 
and the TN will revert to the default routing, which ultimately results in the TN returning to the original "donor" Service 
Provider. 
Does the Respondent's proposal fully comply with these requirements in time to meet the published 
implementation date?
R5-14: Create Subscription Version - Old Service Provider Input Data 
R5-15.1: Create "Inter-Service Provider Port" Subscription Version - New Service Provider Input Data 
R5-15.2: Create "Inter-Service Provider porting to original" Subscription Version - New Service Provider Input Data 
R5-16: Create Inter-Service Provider (non-PTO) Subscription Version - New Service Provider Optional input data 
RR5-179: Create Inter-Service Provider PTO Subscription Version - New Service Provider Data Attributes - Rejected 
R5-18.1: Create Subscription Version - Field-level Data Validation 
R5-18.2: Create Subscription Version - Due Date Consistency Validation 
R5-18.4: Create Subscription Version - Ported TN NPA-NXX Validation 
RR5-119: Subscription Version - Due Date Validation for Second/Concurrence Create Message for a Subscription 
Version Inter-Service Provider Port 
R5-18.5: Create Subscription Version - Service Provider ID Validation 
R5-18.6: Create Subscription Version - LRN Validation 
R5-18.7: Create Subscription Version - Originating Service Provider Validation 
R5-18.8: Create Subscription Version - Duplicate Authorization Validation 
R5-18.9: Create Subscription Version - Service Provider ID Validation 
R5-18.10: Create Subscription Version - Status Change Cause Code Validation 
R5 19.1: Create Subscription Version - Old Service Provider ID Validation 
R5-19.2: Create Subscription Version - Old Service Provider ID Validation - No Active Subscription Version 
R5-19.3: Create Subscription Version - Timer Type Selection 
R5-19.4: Create Subscription Version - Timer Type Selection - Mismatch 
R5-19.5: Create Subscription Version - Business Hours and Days Selection 
R5-19.6: Create Subscription Version - Business Hours and Days Selection - Mismatch 
Page 50
R5-20.1: Create Subscription Version - Validation Failure Notification 
R5-20.2: Create Subscription Version - Validation Failure - No Update 
R5-20.3: Create Subscription Version - Validation Failure - No Create 
R5-20.4: Create Subscription Version - Validation Success - Update Existing 
R5-20.5: Create Subscription Version - Validation Success - Create New 
R5-21.1: Initial Concurrence Window - Tunable Parameter 
R5-21.2: Initial Concurrence Window - Tunable Parameter Modification 
R5-21.3: Long Initial Concurrence Window - Tunable Parameter Default 
R5-21.4: Short Initial Concurrence Window - Tunable Parameter Default 
R5-21.6: Create Subscription Version - Set to Pending 
R5-21.7: Create Subscription Version - Notify User Success 
RR5-2.1: Create Subscription Version - Set to Conflict 
RR5-2.2: Create Subscription Version - Set Conflict Timestamp 
RR5-2.3: Create Subscription Version - Conflict Notification 
RR5-2.4: Cause Code in Conflict Notification - Creation 
R5-22: Create Subscription Version - Initial Concurrence Window Tunable Parameter Expiration 
R5-23.1: Final Concurrence Window - Tunable Parameter 
R5-23.2: Final Concurrence Window Tunable - Tunable Parameter Modification 
R5-23.3: Long Final Concurrence Window Tunable - Tunable Parameter Default 
RR5-52: Short Final Concurrence Window Tunable - Tunable Parameter Default 
RR5-117: New Service Provider Final Create Window Expiration Notification 
RR5-118: New Service Provider Final Create Window Expiration Notification - Sending of Cause Code 
RR5-56: Create Inter-Service Provider Regular Port and Port-to-Original Port - NPAC and SOA After NPA-NXX-X Creation 
RR5-57: Create Intra- or Inter-Service Provider Port-to-Original Subscription Version - After Block Activation 
RR5-198: Create "Inter-Service Provider Port" Subscription Version - DPC-SSN Field-level Data Validation 
R5 23.5: Activation without Old Service Provider Authorization 
R5-23.6: Activation without Old Service Provider Authorization - Time restriction 
RR5-23.3: Old Service Provider Final Concurrence Timer Expiration Notification - Old SP 
RR5-184: Old Service Provider Final Concurrence Timer Expiration Notification - New SP 
(no answer)
Yes
No
 
5.1.2.2.1.2* QUESTION:
TRD FRS Section 5: Sub Section 5.1.2.2.1.2: Subscription Version Creation - Intra-Service Provider Ports 
This section provides the Subscription Version Creation requirements for performing an Intra-Service Provider port of a 
TN. An Intra-Service Provider port of a TN is when a TN is ported to a new location within the current Service Provider 
network (i.e., the routing data is modified, but the Service Provider remains the same). A "port to original" for an Intra-
Service Provider port should be handled by submission of an Intra-Service Provider "port to original" subscription version 
request to the NPAC/SMS. 
Does the Respondent's proposal fully comply with these requirements in time to meet the published 
implementation date?
Page 51
RR5-4: Create "Intra-Service Provider Port" Subscription Version - Current Service Provider Input Data 
RR5-122: Create "Intra-Service Provider porting to original Port" Subscription Version - New Service Provider Input Data 
RR5-5: Create "Intra-Service Provider Port" (non-PTO) Subscription Version - Current Service Provider Optional Input 
Data 
RR5-180: Create "Intra-Service Provider Port" (PTO) Subscription Version - Current Service Provider Data Attributes -
Rejected 
RR5-6.1: Create "Intra-Service Provider Port" Subscription Version - Field-level Data Validation 
RR5-6.2: Create "Intra-Service Provider Port" Subscription Version - New and Old Service Provider ID Match 
RR5-6.4: Create "Intra-Service Provider Port" Subscription Version - Ported TN NPA-NXX Validation 
RR5-6.5: Create "Intra-Service Provider Port" Subscription Version - LRN Validation 
RR5-6.6: Create "Intra-Service Provider Port" Subscription Version - Duplicate Authorization Validation 
RR5-6.7: Create "Intra-Service Provider Port" Subscription Version - Old Service Provider ID Validation 
RR5-6.8: Create "Intra-Service Provider Port" Subscription Version - No Active Version 
RR5-6.9: Create "Intra-Service Provider Port" Subscription Version - Old Service Provider ID Validation - No Active 
Subscription Version 
RR5-7.1: Create "Intra-Service Provider Port" Subscription Version - Validation Failure Notification 
RR5-7.2: Create "Intra-Service Provider Port" Subscription version - Validation Failure - No Create 
RR5-8: Create "Intra-Service Provider Port" Subscription version - Set to Pending 
RR5-9: Create "Intra-Service Provider Port" Subscription version - Notify User of Creation 
RR5-58: Create Intra-Service Provider Port - NPAC Personnel After NPA-NXX-X Creation 
RR5-59: Create Intra-Service Provider Port - SOA After NPA-NXX-X Creation 
RR5-121: Create Intra-Service Provider Port-to-Original Port - NPAC and SOA After NPA-NXX-X Creation 
RR5-218: No Create for Non-Active TN - NPAC Personnel or Service Provider while Block contains a Failed SP List 
RR5-185: Create Intra-Service Provider Port - Medium Timers 
RR5-199: Create "Intra-Service Provider Port" Subscription Version - DPC-SSN Field-level Data Validation 
RR5-203: Create "Intra-Service Provider Port" Subscription Version - Service Provider Tunable Value of TRUE for Pseudo-
LRN Request 
RR5-204: Create "Intra-Service Provider Port" Subscription Version - Rejection of Pseudo-LRN Request for Active Inter- or 
Intra-Subscription Version with Active LRN 
RR5-205: Create "Intra-Service Provider Port" Subscription Version - Rejection of Pseudo-LRN Request for NPA-NXX-X 
RR5-206: Create "Intra-Service Provider Port" Subscription Version - Notify User of Creation of Pseudo-LRN Record 
(no answer)
Yes
No
 
5.1.2.2.2* QUESTION:
TRD FRS Section 5: Sub Section 5.1.2.2.2: Subscription Version Modification 
This section provides the requirements for the Subscription Version Modification functionality, which is executed upon the 
user requesting modification of the Subscription Version. 
Does the Respondent's proposal fully comply with these requirements in time to meet the published 
implementation date?
RR5-123: Validation of LATA ID for Subscription Version Modifies 
R5-25: Modify Subscription Version - Invalid Version Status Notification 
Page 52
RR5-200: Modify "Inter-Service Provider Port" Subscription Version - DPC-SSN Field-level Data Validation 
RR5-201: Modify "Intra-Service Provider Port" Subscription Version - DPC-SSN Field-level Data Validation 
RR5-202: Modify Subscription Version - Validation of DPC-SSNs for Subscription Version Creates 
RR5-207: Modify "Intra-Service Provider Port" Subscription Version - Service Provider Tunable Value of TRUE for Pseudo-
LRN Request 
(no answer)
Yes
No
 
5.1.2.2.2.1* QUESTION:
TRD FRS Section 5: Sub Section 5.1.2.2.2.1: Modification of a Pending or Conflict Subscription Version 
Does the Respondent's proposal fully comply with these requirements in time to meet the published 
implementation date?
R5-26: Modify Subscription Version - Version Identification 
RR5-186: Modify Subscription Version - New Service Provider - Medium Timers 
R5-27.1: Modify Subscription Version - New Service Provider Data Values 
R5-27.2: Modify "porting to original" Subscription Version - New Service Provider Data Values 
RR5-187: Modify Subscription Version - Old Service Provider - Medium Timers 
R5-27.3: Modify Subscription Version - Old Service Provider Data Values 
R5-27.4: Old Service Provider authorization Flag Modification to False 
R5-28: Modify (non-PTO) Subscription Version - New Service Provider Optional input data 
RR5-181: Modify (PTO) Subscription Version - New Service Provider Optional input data 
R5-29.1: Modify Subscription Version - Field-level Data Validation 
RR5-163: Modification of Subscription Version Due Date - Validation 
R5-29.3: Modify Subscription Version - LRN Validation 
R5-29.4: Modify Subscription Version - Originating Service Provider Validation 
R5-29.5: Modify Subscription Version - Status Change Cause Code Validation 
RR5-188: Modify Subscription Version - Medium Timers - Timer Type Change 
RR5-189: Modify Subscription Version - Medium Timers - Restart T1 Timer 
R5 30.1: Modify Subscription Version - Validation Failure Notification 
R5-30.2: Modify Subscription Version - Validation Error Processing 
R5-31.3: Modify Subscription Version - Successful Modification Notification 
RR5-208: Modify "Intra-Service Provider Port" Subscription Version - Send Notification of Modification of Active Pseudo-
LRN Record 
RR5-10.1: Modify Subscription Version - Set Conflict Timestamp 
RR5-10.2: Modify Subscription Version - Conflict Notification 
RR5-10.3: Modify Subscription Version - Cause Code in Notification 
(no answer)
Yes
No
 
5.1.2.2.2.2* QUESTION:
Page 53
TRD FRS Section 5: Sub Section 5.1.2.2.2.2: Modification of an Active/Disconnect Pending Subscription 
Version 
Does the Respondent's proposal fully comply with these requirements in time to meet the published 
implementation date?
RR5-136: Modify Active Subscription Version with a Failed-SP List - Invalid Request Notification 
RR5-11: Modify Active/Disconnect-Pending Subscription Version - Service Provider Owned 
R5-35: Modify Active Subscription Version - Version Identification 
R5-36: Modify Active Subscription Version - Input Data 
R5-37: Active Subscription Version - New Service Provider Optional input data. 
R5-38.1: Modify Active Subscription Version - Field-level Data Validation 
R5-38.2: Modify Active Subscription Version - LRN Validation 
RR5-124: Modify Disconnect Pending Subscription Version - Input Data 
RR5-125: Modify Disconnect Pending Subscription Version - Field-level Data Validation 
RR5-126: Modify Disconnect Pending Subscription Version - Valid Dates for CDD and ERD 
RR5-127: Modify Disconnect Pending Subscription Version - Version Identification 
RR5-128: Modify Disconnect Pending Subscription Version - Rejection for Empty CDD 
R5-39.1: Modify Active/Disconnect Pending Subscription Version - Validation Failure Notification 
R5-39.2: Modify Active/Disconnect Pending Subscription Version - Validation Error Processing 
R5 40.1: Modify Active Subscription Version - Broadcast Date/Time Stamp 
R5-40.3: Modify Active Subscription Version - Modification Success User Notification 
R5-40.4: Modify Active Subscription Version - Broadcast complete Time Stamp 
R5 41: Activation Of A Modified Subscription Version 
RR5-129: Activation Of A Modified Disconnect Pending Subscription Version when ERD is Modified to Current Date 
RR5-41.1: Broadcast Modified Active Subscription - Local SMS Identification 
RR5-41.2: Broadcast Modified Active Subscription - Send to Local SMSs 
RR5-41.3: Broadcast Modified Active Subscription - Set to Sending 
RR5-41.4: Modify Active Subscription Version - Return Status 
RR5 41.5: Modify Active Subscription Activation Retry Attempts - Tunable Parameter 
RR5-41.6: Modify Active Subscription Activation Retry Interval - Tunable Parameter 
RR5-41.7: Modify Active Subscription Version Failure Retry 
RR5-41.8: Modify Active Subscription Version Failure - Status Sending 
RR5-41.9: Modify Active Subscription Version Failure - Local SMS Identification 
RR5-41.10: Subscription Version Activation - Resend to Failed Local SMSs 
RR5-41.11: Modify Active Subscription Version - Failed Local SMS Notification Current Service Provider 
(no answer)
Yes
No
5.1.2.2.3 STATEMENT:
TRD FRS Section 5: Sub Section 5.1.2.2.3: Subscription Version Conflict 
This section provides the requirements for the functionality to place a Subscription Version in to conflict and remove it 
from conflict 
 
5.1.2.2.3.1* QUESTION:
TRD FRS Section 5: Sub Section 5.1.2.2.3.1: Placing Subscription Version in Conflict 
Page 54
Does the Respondent's proposal fully comply with these requirements in time to meet the published 
implementation date?
R5-42: Conflict Subscription Version - Version Identification 
R5-43.1: Conflict Subscription Version - Invalid Status Notification 
R5-43.2: Conflict Subscription Version - No Cause Code Notification 
RR5-42.1: Conflict Subscription Version - Old Service Provider Number Restriction 
RR5-42.2: Conflict Subscription Version - Conflict Restriction Window 
RR5-50: Conflict Subscription Version - Conflict Restriction Window- Old Service Provider 
RR5-51: Conflict Subscription Version - Conflict Restriction Rules for Old Service Provider 
AR5-2: Conflict Restriction Window Tunable due date value 
RR5-42.3: Conflict Subscription Version - Conflict Restriction Window Tunable 
RR5-42.4: Conflict Subscription Version - Conflict Restriction Window Tunable Default 
RR5-42.5: Conflict Subscription Version - Short Timer Usage 
R5-44.1: Conflict Subscription Version - Set Status to Conflict 
R5-44.2: Conflict Subscription Version - Set Conflict Date and Time 
R5-44.3: Conflict Subscription Version - Successful Completion Message 
R5-45.1: Conflict Expiration Window - Tunable Parameter 
R5-45.2: Conflict Expiration Window - Tunable Parameter Default 
R5-45.3: Conflict Expiration Window - Tunable Parameter Modification 
R5-45.4: Conflict Subscription Version - Set to Cancel 
R5-45.5: Conflict Subscription Version - Set Cancellation Date Timestamp 
R5-45.6: Conflict Subscription Version - Inform Service Providers of Cancel Status 
(no answer)
Yes
No
 
5.1.2.2.3.2* QUESTION:
TRD FRS Section 5: Sub Section 5.1.2.2.3.2: Removing a Subscription Version from Conflict 
Does the Respondent's proposal fully comply with these requirements in time to meet the published 
implementation date?
R5-46: Conflict Resolution Subscription Version - Version Identification 
R5-47: Conflict Resolution Subscription Version - Invalid Status Notification 
R5-50.1: Conflict Resolution Subscription Version - Set Status 
R5-50.2: Conflict Resolution Subscription Version - Status Message 
RR5-12.1: Conflict Resolution Subscription Version - Inform Both Service Providers of Pending Status 
RR5-12.3: Conflict Resolution New Service Provider Restriction Tunable Parameter 
RR5-12.4: Long Conflict Resolution New Service Provider Restriction - Tunable Parameter Default 
RR5-12.5: Conflict Resolution New Service Provider Restriction Tunable Parameter Modification 
RR5-12.6: Short Conflict Resolution New Service Provider Restriction - Tunable Parameter Default 
RR5-14: Conflict Resolution Acknowledgment - Update Conflict Resolution Date and Time Stamp 
RR5-137: Conflict Resolution Subscription Version - Restriction for Cause Code Values 
RR5-138: Conflict Resolution Subscription Version -Conflict Resolution New Service Provider Restriction Tunable 
Application 
RR5-139: Conflict Resolution Subscription Version - Restricted Cause Code Notification 
RR5-168: Regional Prevent Conflict Resolution 50/51 Tunable 
RR5-169: Regional Prevent Conflict Resolution 50/51 Tunable Default 
RR5-170: Regional Prevent Conflict Resolution 50/51 Tunable Modification 
Page 55
(no answer)
Yes
No
 
5.1.2.2.4* QUESTION:
TRD FRS Section 5: Sub Section 5.1.2.2.4: Subscription Version Activation 
This section provides the requirements for the Subscription Version Activation functionality, which is executed upon the 
NPAC personnel or SOA to NPAC/SMS interface user requesting to activate a Subscription Version.
Does the Respondent's proposal fully comply with these requirements in time to meet the published 
implementation date? 
R5-51.1: Activate Subscription Version - Version Identification 
R5-51.2: Activate Subscription Version - Broadcast Complete Date and Time Stamp 
RR5-21: Activate "porting to original" Subscription Version 
RR5-22: Activate Subscription Version - Set Activation Received Timestamp 
R5-52: Activate Subscription Version - Invalid Status Notification 
R5-53.1: Activate Subscription Version - Validation 
R5-53.2: Activate Subscription Version Validation Error Message 
R5-53.3: Activate Subscription Version - Validate Due Date 
RR5-209: Activate "Intra-Service Provider Port" Subscription Version - Service Provider Tunable Value of TRUE for 
Pseudo-LRN Request 
R5-55: Activate Subscription Version - Local SMS Identification 
R5-57.1: Activate Subscription Version - Send to Local SMSs 
RR5-210: Activate Subscription Version - Local SMS Identification - Pseudo-LRN 
R5-57.2: Activate Subscription Version - Set to Sending 
R5-57.3: Activate Subscription Version - Date and Time Stamp 
R5-58.1: Local SMS Activation message logging 
R5-58.2: Local SMS Activation Log Retention Period - Tunable Parameter 
R5-58.3: Local SMS Activation Log Retention Period - Tunable Parameter Modification 
R5-58.4: Local SMS Activation Log Retention Period - Tunable Parameter Default
R5-58.5: Local SMS Activation Message Log - Viewing 
R5-59.1: Activate Subscription Version - Set Status of Current to Active 
R5-59.2: Activate Subscription Version - Set Status of Previous to Old 
R5-60.1: Subscription Activation Retry Attempts - Tunable Parameter 
R5-60.2: Subscription Activation Retry Interval - Tunable Parameter 
R5-60.3: Subscription Activation Retry Attempts - Tunable Parameter Modification 
R5-60.4: Subscription Activation Retry Interval - Tunable Parameter Modification 
R5-60.5: Subscription Activation Retry Attempts - Tunable Parameter Default 
R5-60.6: Subscription Activation Retry Interval - Tunable Parameter Default 
R5-60.7: Subscription Version Activation Failure Retry 
R5-60.8: Subscription Version Activation Failure - After Retries 
R5-60.9: Subscription Version Activation Failure - Status Sending 
R5-60.10: Subscription Version Activation Failure - Local SMS Identification 
R5-60.11: Subscription Version Activation Failure - Set Status to Partial Failure 
R5-60.12: Subscription Version Partial Activation Failure - Set Status of Previous to Old 
R5 61.1: Subscription Version Activation - Set Status to Failure 
R5-61.2: Subscription Version Activation Subscription Version - Failure Notification 
R5-61.3: Subscription Version Activation - Resend to Failed Local SMSs 
RR5-22.1: Subscription Version Activation - Failed Local SMS Notification - Both Service Providers 
Page 56
RR5-22.2: Subscription Version Activation - Failed Local SMS Notification - Current Service Provider 
RR5-60: Activate Intra-Service Provider Port - After NPA-NXX-X Creation and Prior to the Existence of the Block 
RR5 219: Activate Subscription Version - Pending SV with no underlying Pooled or Ported SV
RR5-211: Activate "Intra-Service Provider Port" Subscription Version - Send Notification of Activation of Pseudo-LRN 
Record 
RR5-61: Activate Port-to-Original Subscription Version - Broadcast of Subscription Data Creation 
RR5-62: Activate Port-to-Original Subscription Version - Broadcast of Subscription Data Deletion 
RR5-171: Activate Subscription Version - Send SV Type Data to Local SMSs 
RR5-172: Activate Subscription Version - Send Alternative SPID to Local SMSs 
RR5-190: Activate Subscription Version - Send Last Alternative SPID to Local SMSs 
RR5-191: Activate Subscription Version - Send Alt-End User Location Value to Local SMSs 
RR5-192: Activate Subscription Version - Send Alt-End User Location Type to Local SMSs 
RR5-193: Activate Subscription Version - Send Alt-Billing ID to Local SMSs 
RR5-194: Activate Subscription Version - Send Voice URI to Local SMSs 
RR5-195: Activate Subscription Version - Send MMS URI to Local SMSs 
RR5-196: Activate Subscription Version - Send SMS URI to Local SMSs 
(no answer)
Yes
No
 
5.1.2.2.5* QUESTION:
TRD FRS Section 5: Sub Section 5.1.2.2.5: Subscription Version Disconnect 
This section provides the requirements for the Subscription Version Disconnect functionality, which is executed upon the 
NPAC personnel or SOA to NPAC/SMS interface user requesting to have a Subscription Version disconnected. 
Does the Respondent's proposal fully comply with these requirements in time to meet the published 
implementation date?
R5-62: Disconnect Subscription Version - Version Identification 
RR5-23.1: Disconnect Subscription Version - Required Input Data 
RR5-23.2: Disconnect Subscription Version - Optional Input Data 
RN5-10: Disconnect Subscription Version - Invocation by Current Service Provider 
R5-63: Disconnect Subscription Version - Invalid Status Notification 
R5-64.1: Disconnect Subscription Version - Cancel Other Version Notification 
RR5-212: Disconnect "Intra-Service Provider Port" Subscription Version - Service Provider Tunable Value of TRUE for 
Pseudo-LRN Request 
RR5-24: Disconnect Subscription Version -Set to Disconnect Pending 
RR5-25.1: Disconnect Subscription Version - Disconnect Pending Status Notification 
RR5-25.2: Disconnect Subscription Version - Customer Disconnect Date Notification 
R5 65.1: Disconnect Subscription Version -Immediate Broadcast 
R5-65.2: Disconnect Subscription Version - Deferred Broadcast 
R5-65.4: Disconnect Subscription Version - Broadcast Interface Message to Local SMSs 
RR5-213: Disconnect Subscription Version - Local SMS Identification - Pseudo-LRN 
R5-65.5: Disconnect Subscription Version - Disconnect Broadcast Date and Time Stamp 
R5-65.6: Disconnect Subscription Version - Set to Sending 
R5-66.2: Disconnect Subscription Version Complete - Set Disconnect Complete Date 
R5-66.3: Disconnect Subscription Version Complete - Set Disconnect to Old
R5-66.4: Disconnect Subscription Version Complete - Status Update of SV 
RR5-214: Disconnect "Intra-Service Provider Port" Subscription Version - Send Notification of Disconnect of Pseudo-LRN 
Page 57
Record 
R5-67.1: Disconnect Subscription Version - Set Status to Active 
R5-67.2: Disconnect Pending Subscription Version - Failure Notification 
R5-67.3: Disconnect Subscription Version - Resend Disconnect Requests to All Local SMSs 
R5-68.1: Disconnect Subscription Version - Subscription Disconnect Retry Attempts - Tunable Parameter 
R5-68.2: Disconnect Pending Subscription Version - Subscription Disconnect Retry Attempts - Tunable Parameter Default 
R5-68.3: Disconnect Subscription Version - Subscription Disconnect Retry Interval - Tunable Parameter 
R5-68.4: Disconnect Subscription Version - Subscription Disconnect Retry Interval - Tunable Parameter Default 
R5-68.5: Disconnect Subscription Version - Retry Processing 
R5-68.6: Disconnect Subscription Version - Sending Status during Retries 
R5-68.7: Disconnect Subscription Version - Retry Failed 
R5-68.8: Disconnect Subscription Version - Failure Notification after Retries Complete 
R5-68.9: Disconnect Subscription Version - Set to Old 
R5-68.10: Disconnect Subscription Version - Resend Disconnect Requests to Failed Local SMSs 
RR5-63: Disconnect Subscription Version or Port-To-Original - Pooled Number Block Default Routing Restoration 
RR5-64: Disconnect Subscription Version - Customer Disconnect Date Notification for Pooled Number 
RR5-65: Disconnect Subscription Version - Broadcast of Subscription Data Creation 
RR5-66: Disconnect Subscription Version - Broadcast of Subscription Data Deletion 
RR5-67.1: Disconnect Subscription Version - Updates to the Status for Disconnect 
RR5-67.2: Disconnect Subscription Version - Setting of the Status for Disconnected SV 
RR5-67.3: Disconnect Subscription Version - Setting of the Status for Newly Created SV 
RR5-68.1: Disconnect Subscription Version - Updates to the Status for Port-to-Original 
RR5-68.2: Disconnect Subscription Version - Setting of the Status for Port-to-Original SV 
RR5-68.3: Disconnect Subscription Version - Setting of the Status for Port-to-Original SV that was active prior to the PTO 
activation request 
RR5-68.4: Disconnect Subscription Version - Setting of the Status for Port-to-Original for Newly Created SV 
RR5-69: Disconnect Subscription Version - Updates to the Failed SP List for Disconnect 
RR5-70: Disconnect Subscription Version - Updates to the Failed SP List for Port-To-Original 
(no answer)
Yes
No
 
5.1.2.2.6* QUESTION:
TRD FRS Section 5: Sub Section 5.1.2.2.6: Subscription Version Cancellation 
This section provides the requirements for the Subscription Version Cancellation functionality (including "un-do" of a 
'cancel-pending' Subscription Version), which is executed upon the NPAC personnel or SOA to NPAC/SMS interface user 
requesting to cancel a Subscription Version. 
Does the Respondent's proposal fully comply with these requirements in time to meet the published 
implementation date? 
RR5-26.1: Cancel Subscription Version - Inform Both Service Providers of Cancel Pending Status 
R5-69: Cancel Subscription Version - Version Identification 
R5-70: Cancel Subscription Version - Invalid Status Notification 
RR5-27: Cancel Subscription Version - Validate Service Provider 
Page 58
R5 71.2: Cancel Subscription Version - Set Cancellation Date and Time Stamp 
R5-71.3: Cancel Subscription Version- Set to Cancel Old Service Provider only 
R5-71.4: Cancel Subscription Version- Set to Cancel New Service Provider only 
R5-71.5: Cancel Subscription version- Error on Cancellation 
R5-71.6: Cancel Subscription Version- Set Pending subscription version to Cancel Pending Status Inter-Service Provider 
port 
R5-71.8: Cancel Subscription Version- Set Conflict Subscription to Cancel New Service Provider only 
R5-71.9: Cancel Subscription Version - Rejection of Old Service Provider Conflict Cancellation 
R5-71.10: Cancel Subscription Version- Set Disconnect Pending subscription version to Active 
R5-71.11: Cancel Subscription Version- Set to Cancel Status - Intra-Service Provider port 
RR5-28.1: Cancel Subscription Version - Set to Cancel After Service Provider Acknowledge 
RR5-29.1: Cancel Subscription Version - Inform Both Service Providers of Cancel Status 
RR5-29.2: Cancel Subscription Version - Inform Current Service Provider of Cancel Status 
RR5-30: Cancel Subscription Version Acknowledgment - Update Old Service Provider Date and Time Stamp 
RR5-31: Cancel Subscription Version Acknowledgment - Update New Service Provider Date and Time Stamp 
RR5-32.1: Cancellation-Initial Concurrence Window - Tunable Parameter 
RR5-32.2: Cancellation-Initial Concurrence Window - Tunable Parameter Modification 
RR5-32.3: Long Cancellation-Initial Concurrence Window - Tunable Parameter Default 
RR5-32.4: Short Cancellation-Initial Concurrence Window - Tunable Parameter Default 
RR5-33.1: Cancellation-Final Concurrence Window - Tunable Parameter 
RR5-33.2: Cancellation-Final Concurrence Window Tunable Parameter Modification 
RR5-33.3: Long Cancellation-Final Concurrence Window - Tunable Parameter Default 
RR5-33.4: Short Cancellation-Final Concurrence Window - Tunable Parameter Default 
RR5-34: Cancellation-Initial Concurrence Window - Tunable Parameter Expiration 
RR5-35.1: Cancellation-Final Concurrence Window - Tunable Parameter Expiration New Service Provider 
RR5-35.2: Cancellation-Final Concurrence Window - Tunable Parameter Expiration Old Service Provider 
RR5-36.1: Cancel Subscription Version - Cause Code for New SP Timer Expiration 
RR5-36.2: Cancel Subscription Version - Inform Service Providers of Conflict Status 
RR5-165: Regional Automatic Conflict Cause Code Tunable 
RR5-166: Regional Automatic Conflict Cause Code Tunable Default 
RR5-167: Regional Automatic Conflict Cause Code Tunable Modification 
(no answer)
Yes
No
 
5.1.2.2.6.1*
QUESTION:
TRD FRS Section 5: Sub Section 5.1.2.2.6.1: Un-Do a "Cancel Pending" Subscription 
Does the Respondent's proposal fully comply with these requirements in time to meet the published 
implementation date? 
RR5-143: Un-Do a Cancel-Pending Subscription Version - Notification 
RR5-144: Un-Do a Cancel-Pending Subscription Version - Request Data 
RR5-164: Un-Do a Cancel-Pending Subscription Version - New Status Specified Error 
RR5-145: Un-Do a Cancel-Pending Subscription Version - Version Status Error 
RR5-147: Un-Do a Cancel-Pending Subscription Version - Timestamp 
Page 59
RR5-149: Un-Do a Cancel-Pending Subscription Version - Missing Cancel Error 
RR5-150: Un-Do a Cancel-Pending Subscription Version - Status Change 
(no answer)
Yes
No
 
5.1.2.2.7* QUESTION:
TRD FRS Section 5: Sub Section 5.1.2.2.7: Subscription Version Resend 
This section provides the requirements for the Subscription Version resend functionality, which is executed upon the 
NPAC personnel requesting to resend a Subscription Version. 
Does the Respondent's proposal fully comply with these requirements in time to meet the published 
implementation date? 
RR5-38.1.1: Resend Subscription Version - Identify Subscription Version 
RR5-38.1.2: Resend Subscription Version - Identify Multiple Subscription Versions 
RR5-38.2: Resend Subscription Version - Input Data 
RR5-38.3: Resend Subscription Version - Error Message 
RR5-38.4: Resend Subscription Version - Activation Request 
RR5-38.5: Resend Subscription Version - Disconnect Request 
RR5-38.6: Resend Subscription Version - Failed or Partial Failure 
RR5-38.7: Resend Subscription Version - Standard Activation Processing 
RR5-38.8: Resend Subscription Version - Standard Disconnect Processing 
RR5-38.9: Resend Subscription Version - Modify Active Request 
RR5-38.10: Resend Subscription Version - Standard Modify Active Processing 
RR5-71: Re-Send of Number Pooling Subscription Version Information - NPAC Personnel OpGUI 
RR5-72: Re-Send of Number Pooling Subscription Version Information - Subscription Versions sent to discrepant non-EDR 
Local SMS 
RR5-73: Re-Send of Number Pooling Subscription Version Information - Sending Status Update to Failed Subscription 
Versions for Block Activation 
RR5-74: Re-Send of Number Pooling Subscription Version Information - Sending Status Update to Partial failure 
Subscription Versions for Block Activation 
RR5-75: Re-Send of Number Pooling Subscription Version Information - Sending Status Update to Active Subscription 
Version for Block Modification or Deletion 
RR5-76: Re-Send of Number Pooling Subscription Version Information - Sending Status Update to Old Subscription 
Version for Block Deletion 
RR5-77: Re-Send of Number Pooling Subscription Version Information - Update to Failed SP List 
RR5-78: Re-Send of Number Pooling Subscription Version Information -Status Update to Subscription Version after Re-
Send 
RR5-79: Re-Send of Number Pooling Subscription Version Information -Failed SP List Update to Subscription Version after 
Re-Send 
RR5-80: Re-Send of Subscription Version Information - Disconnect or Port-To-Original of a TN within a Pooled 1K Block 
RR5-81.1: Re-Send of Subscription Version Information - Disconnect TN within a Pooled 1K Block to EDR Local SMS 
RR5-81.2: Re-Send of Subscription Version Information - Disconnect TN within a Pooled 1K Block to non-EDR Local SMS 
RR5-82.1: Re-Send of Subscription Version Information -Port-To-Original TN within a Pooled 1K Block to EDR Local SMS 
RR5-82.2: Re-Send of Subscription Version Information -Port-To-Original TN within a Pooled 1K Block to non-EDR Local 
SMS 
RR5-151: Subscription Version Failed SP List - Exclusion of a Service Provider from Resend 
RR5-152: Subscription Version Failed SP List - Logging of an Excluded Service Provider 
Page 60
(no answer)
Yes
No
5.1.3 STATEMENT:
TRD FRS Section 5: Sub Section 5.1.3: Subscription Queries 
This section provides the requirements for the Subscription Version Query functionality, which is executed upon the user 
requesting a query of a Subscription Version (R5-13). 
 
5.1.3.1* QUESTION:
TRD FRS Section 5: Sub Section 5.1.3.1: User Functionality 
Does the Respondent's proposal fully comply with these requirements in time to meet the published 
implementation date? 
R5-72: Query Subscription Version - Request 
RR5-215: Query of Subscription Versions for Pseudo-LRN - Service Provider Personnel - SOA Interface 
RR5-216: Query of Subscription Versions for Pseudo-LRN - Service Provider Personnel - LSMS Interface 
RR5-217: Query of Subscription Versions for Pseudo-LRN - Service Provider Personnel - LTI 
(no answer)
Yes
No
5.1.3.2* QUESTION:
TRD FRS Section 5: Sub Section 5.1.3.2: System Functionality 
The following requirements specify the NPAC/SMS query functionality defined above. 
Does the Respondent's proposal fully comply with these requirements in time to meet the published 
implementation date?
R5-73: Query Subscription Version - Version Identification 
R5-74.1: Query Subscription Version - Status Supplied 
R5-74.2: Query Subscription Version - Return All Subscription Versions for Ported TN 
R5-74.3: Query Subscription Version - Output Data - SOA 
R5-74.4: Query Subscription Version - Output Data - LSMS 
RR5-153: Subscription Version Query - Sort Order 
Page 61
R5-75: Query Subscription Version -No Data Found 
RN5-4: Query Subscription Version - Retrieve Data, Modification Not Allowed 
RN5-5: Query Subscription Version - Retrieve Data Based on Single Ported TN Only 
RN5-6: Query Subscription Version - View for Any Ported TN 
RR5-39: Query Subscription Version - View Old, Partial Failure, Disconnect Pending, Canceled or Active Only 
RR5-174: NPAC/SMS shall return all Subscription Versions 
RR5-175: Service Provider subscription query 
RR5-40: Query Subscription Version - Online Records Only 
RR5-83: Query Subscription Version - LNP Type of POOL 
RR5-154: Subscription Version Query - Maximum Subscription Version Query by the SOA 
RR5-155: Subscription Version Query - Maximum Subscription Version Query by the LSMS 
RR5-176: Count of subscription information during a query 
RR5-177: Service Provider subscription query options 
RR5-178: Error Message for Service Provider subscription query 
RR5-156: Service Provider SOA SV Query Indicator 
RR5-157: Service Provider SOA SV Query Indicator Default 
RR5-158: Service Provider SOA SV Query Indicator Modification 
RR5-159: Service Provider LSMS SV Query Indicator 
RR5-160: Service Provider LSMS SV Query Indicator Default 
RR5-161: Service Provider LSMS SV Query Indicator Modification 
(no answer)
Yes
No
5.1.4 STATEMENT:
TRD FRS Section 5: Sub Section 5.1.4: Subscription Version Processing for National Number Pooling 
This section details the functional requirements for user interaction (either NPAC Personnel or Service Provider Personnel 
via their SOA and/or LSMS to NPAC/SMS interface) with the NPAC/SMS to appropriately operate in the National Number 
Pooling environment. 
5.1.4.1* QUESTION:
TRD FRS Section 5: Sub Section 5.1.4.1: Subscription Version, General 
The following requirements outline the basic NPAC/SMS processing requirements for subscription versions in a National 
Number Pooling environment. 
Does the Respondent's proposal fully comply with these requirements in time to meet the published 
implementation date? 
RR5-84: Number Pooling Subscription Version Information - Reject Messages 
RR5-85: Number Pooling Subscription Version Information - Suppression of Notifications 
RR5-85.5: Number Pooling Subscription Version Information - Disconnect Notifications to Donor Service Provider 
RR5-86: Number Pooling Subscription Version Information - Filters for "Pooled Number" Subscription Versions 
RR5-87: Number Pooling Subscription Version Information - Broadcast of Subscription Data 
Page 62
RR5-88: Number Pooling Subscription Version Information - Failed SP List Update for Block 
RR5-89: Number Pooling Subscription Version Information - Data Integrity for Pooled Subscription Versions and Block 
(no answer)
Yes
No
 
5.1.4.2* QUESTION:
TRD FRS Section 5: Sub Section 5.1.4.2: Subscription Version, Addition for Number Pooling 
The following section outlines the NPAC/SMS functional requirements for processing pooled subscription version 
additions. Subscription versions with LNP Type set to POOL are created when a Number Pool Block is activated. 
Does the Respondent's proposal fully comply with these requirements in time to meet the published 
implementation date? 
RR5-90: Addition of Number Pooling Subscription Version Information - Subscription Data 
RR5-91: Addition of Number Pooling Subscription Version Information - Create "Pooled Number" Subscription Version 
RR5-92: Addition of Number Pooling Subscription Version Information Create "Pooled Number" Subscription Version -
Bypass of Existing Subscription Versions 
RR5-93: Addition of Number Pooling Subscription Version Information Create "Pooled Number" Subscription Version - Set 
to Sending 
RR5-94: Addition of Number Pooling Subscription Version Information - Status Update 
RR5-95: Addition of Number Pooling Subscription Version Information - Failed SP List 
RR5-220: Addition of Number Pooling Subscription Version Information - Create "Pooled Number" Subscription Version -
Status Rollup to Active with empty Failed SP List 
(no answer)
Yes
No
5.1.4.3* QUESTION:
TRD FRS Section 5: Sub Section 5.1.4.3: Subscription Version, Block Create Validation of Subscription 
Versions 
The following requirements define validation processing on behalf of the NPAC/SMS once a Number Pool Block has been 
activated. 
Does the Respondent's proposal fully comply with these requirements in time to meet the published 
implementation date? 
RR5-96: Block Create Validation of Subscription Versions - Subscription Version Completion Check 
RR5-97: Block Create Validation of Subscription Versions - First Time Execution of Subscription Version Completion Check 
RR5-98: Block Create Validation of Subscription Versions - Subscription Version Create for Missing TNs 
Page 63
RR5-99: Block Create Validation of Subscription Versions - Subscription Version Broadcast to non-EDR Local SMS 
RR5-100: Block Create Validation of Subscription Versions - Block Status Update 
RR5-101: Block Create Validation of Subscription Versions - Block Failed SP List Update 
RR5-102: Block Create Validation of Subscription Versions - Subscription Version Logging 
(no answer)
Yes
No
 
5.1.4.4* QUESTION:
TRD FRS Section 5: Sub Section 5.1.4.4: Subscription Version, Modification for Number Pooling 
Does the Respondent's proposal fully comply with these requirements in time to meet the published 
implementation date? 
RR5-103: Modification of Number Pooling Subscription Version Information - Subscription Data 
RR5-104: Modification of Number Pooling Subscription Version Information - Status Update to Sending 
RR5-105: Modification of Number Pooling Subscription Version Information - Status Update 
RR5-106: Modification of Number Pooling Subscription Version Information - Failed SP List 
(no answer)
Yes
No
 
5.1.4.5* QUESTION:
TRD FRS Section 5: Sub Section 5.1.4.5: Subscription Version, Deletion for Number Pooling 
Does the Respondent's proposal fully comply with these requirements in time to meet the published 
implementation date?
RR5-107: Deletion of Number Pooling Subscription Version Information - Sending Status Update to Subscription Versions 
RR5-108: Deletion of Number Pooling Subscription Version Information - Broadcast of Subscription Version Data 
RR5-109: Deletion of Number Pooling Subscription Version Information - Status Update to Subscription Versions 
RR5-110: Deletion of Number Pooling Subscription Version Information - Failed SP List 
(no answer)
Yes
No
 
5.1.4.6* QUESTION:
Page 64
TRD FRS Section 5: Sub Section 5.1.4.6: Subscription Version, Block Delete Validation Subscription 
Versions 
Does the Respondent's proposal fully comply with these requirements in time to meet the published 
implementation date? 
RR5-111: Block Delete Validation of Subscription Versions - Ensure no Subscription Versions with LNP Type POOL 
(no answer)
Yes
No
6. TRD FRS Section 6: NPAC/SMS INTERFACES
6.1 STATEMENT:
TRD FRS Section 6: Sub Section 6.1: SOA to NPAC/SMS Interface 
The SOA to NPAC/SMS Interface is a CMIP-based, mechanized interface to the NPAC/SMS. The SOA interface supports 
the Service Provider's Service Order Administration (SOA) systems. This interface is referred to as the SOA to NPAC/SMS 
interface.  This interface supports two-way communications between service providers SOA systems and the NPAC/SMS. 
6.2 STATEMENT:
TRD FRS Section 6: Sub Section 6.2: NPAC/SMS to LSMS Interface 
The LSMS to NPAC/SMS Interface is a CMIP-based, mechanized interface to the NPAC/SMS.  The LSMS interface supports 
the Service Provider's Local Service Management System (LSMS). This interface is referred to as the NPAC/SMS to LSMS 
interface. This interface support two-way communications between the service providers LSMS and the NPAC/SMS. 
6.3* QUESTION:
TRD FRS Section 6: Sub Section 6.3: Interface Transactions 
The CMIP protocol provides for six types of transactions over the interface (Reference: ISO 9595 and 9596). They are: 
ท Create 
ท Delete 
ท Set 
ท Get 
ท M-Action 
Page 65
ท Event Report 
Does the Respondent's proposal fully comply with the requirement below in time to meet the published 
implementation date? 
R6-22: Manager-agent relationship of interface transactions. 
(no answer)
Yes
No
6.4* QUESTION:
TRD FRS Section 6: Sub Section 6.4: Interface and Protocol Requirements 
While it is expected that dedicated links will be used for the interfaces, switched connections should also be 
supported. Reliability and availability of the links will be essential and high capacity performance will be needed. 
Does the Respondent's proposal fully comply with the requirement below in time to meet the published 
implementation date? 
R6-23: Open interfaces 
(no answer)
Yes
No
6.4.1* QUESTION:
TRD FRS Section 6: Sub Section 6.4.1: Protocol Requirements 
Does the Respondent's proposal fully comply with these requirements below, in time to meet the published 
implementation date?
R6-24: Interface protocol stack 
R6-25: Multiple application associations 
(no answer)
Yes
No
6.4.2* QUESTION:
Page 66
TRD FRS Section 6: Sub Section 6.4.2: Interface Performance Requirements 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
R6-26: Interface availability 
R6-27: Interface Reliability 
R6-28.1: SOA to NPAC/SMS interface transaction rates - sustained 
R6-28.2: SOA to NPAC/SMS interface transaction rates - peak 
RR6-107: SOA to NPAC/SMS interface transaction rates - total bandwidth
RR6-108: NPAC/SMS to Local SMS interface transaction rates - sustained 
RR6-109: NPAC/SMS to Local SMS interface transaction rates - total bandwidth 
(no answer)
Yes
No
6.4.3* QUESTION:
TRD FRS Section 6: Sub Section 6.4.3: Interface Specification Requirements 
Does the Respondent's proposal fully comply with these requirements below in time to meet the published 
implementation date? 
R6-30.1: Interface specification 
R6-30.2: Interface specification identification 
R6-35: NPAC/SMS Interoperable Interface Specification extensibility 
RR6-1: Acknowledgment of a Cancel Pending for a Subscription Version 
RR6-2: Acknowledgment of a Conflict Resolution for a Subscription Version 
RR6-3: Deferred Disconnect of a Subscription Version 
RR6-4: Cancel Request Notification 
RR6-5: Conflict Resolution Request Notification 
(no answer)
Yes
No
6.4.4* QUESTION:
TRD FRS Section 6: Sub Section 6.4.4: Request Restraints Requirements 
Does the Respondent's proposal fully comply with these requirements below in time to meet the published 
implementation date? 
Page 67
RR6-8: Tunable Parameter Number of Aggregated Download Records 
RR6-9: Download Time Tunable Parameter to Restricted Time Range 
RR6-13: Queries Constrained by NPA-NXX 
RR6-14: Subscription Version Resynchronization Filter Usage 
(no answer)
Yes
No
6.4.5* QUESTION:
TRD FRS Section 6: Sub Section 6.4.5: Application Level Errors Requirements 
Does the Respondent's proposal fully comply with these requirements below in time to meet the published 
implementation date? 
RR6-110: NPAC/SMS Application Level Errors 
RR6-111: NPAC/SMS Application Level Error Details 
RR6-112: NPAC/SMS Application Level Error Details in soft format 
RR6-113: SOA Action Application Level Errors Indicator
RR6-114: SOA Action Application Level Error Indicator Default 
RR6-115: SOA Action Application Level Errors Indicator Modification 
RR6-116: LSMS Action Application Level Errors Indicator 
RR6-117: LSMS Action Application Level Errors Indicator Default 
RR6-118: LSMS Action Application Level Errors Indicator Modification 
RR6-119: LSMS Application Level Errors Indicator 
RR6-193: SOA Non-Action Application Level Errors Indicator 
RR6-194: SOA Non-Action Application Level Errors Indicator Default 
RR6-195: SOA Non-Action Application Level Errors Indicator Modification 
RR6-196: LSMS Non-Action Application Level Errors Indicator 
RR6-197: LSMS Non-Action Application Level Errors Indicator Default 
RR6-198: LSMS Non-Action Application Level Errors Indicator Modification 
(no answer)
Yes
No
6.5* QUESTION:
TRD FRS Section 6: Sub Section 6.5: NPAC SOA Low-tech Interface Requirements 
The NPAC SOA Low-tech Interface supports the request functionality of the SOA to NPAC/SMS interface. 
Does the Respondent's proposal fully comply with these requirements below in time to meet the published 
implementation date? 
Page 68
RX6-2.1: NPAC SOA Low-tech Interface 
RX6-2.2: SOA to NPAC/SMS Create Subscription Versions administration requests via an NPAC SOA Low-tech Interface 
RX6-2.3: SOA to NPAC/SMS Cancel Subscription Versions administration requests via an NPAC SOA Low-tech Interface 
RX6-2.4: SOA to NPAC/SMS Modify Subscription Versions administration requests via an NPAC SOA Low-tech Interface 
RX6-2.5: SOA to NPAC/SMS Query Subscription Versions administration requests via an NPAC SOA Low-tech Interface 
RX6-2.6: SOA to NPAC/SMS Activate Subscription Versions administration requests via an NPAC SOA Low-tech Interface 
RX6-2.7: SOA to NPAC/SMS Disconnect Subscription Versions administration requests via an NPAC SOA Low-tech 
Interface 
RR6-189: SOA to NPAC/SMS Un-Do Cancel-Pending Subscription Version administration requests via an NPAC SOA Low-
tech Interface
RX6-3: SOA to NPAC/SMS audit requests 
RR6-35: SOA to NPAC/SMS Number Pool Block Create Request via the SOA Low-tech Interface 
RR6-36: SOA to NPAC/SMS Number Pool Block Modify Request via the SOA Low-tech Interface 
RX6-4: NPAC/SMS Notification Handling 
(no answer)
Yes
No
6.6* QUESTION:
TRD FRS Section 6: Sub Section 6.6: CMIP Request Retry Requirements 
Does the Respondent's proposal fully comply with these requirements below in time to meet the published 
implementation date? 
RR6-15: SOA Retry Attempts - Tunable Parameter  
RR6-16: SOA Retry Interval - Tunable Parameter 
RR6-17: SOA Retry Attempts - Tunable Parameter Modification 
RR6-18: SOA Retry Interval - Tunable Parameter Modification 
RR6-19: SOA Retry Attempts - Tunable Parameter Default 
RR6-20: SOA Retry Interval - Tunable Parameter Default 
RR6-21: SOA Activation Failure Retry 
RR6-22: LSMS Retry Attempts - Tunable Parameter 
RR6-23: LSMS Retry Interval - Tunable Parameter 
RR6-24: LSMS Retry Attempts - Tunable Parameter Modification 
RR6-25: LSMS Retry Interval - Tunable Parameter Modification 
RR6-26: LSMS Retry Attempts - Tunable Parameter Default 
RR6-27: LSMS Retry Interval - Tunable Parameter Default 
RR6-28: LSMS Activation Failure Retry 
(no answer)
Yes
No
6.7* QUESTION:
Page 69
TRD FRS Section 6: Sub Section 6.7: Recovery Requirements 
The following requirements define the Recovery functionality supported by the NPAC/SMS to SOA interface and 
NPAC/SMS to LSMS interface.
Does the Respondent's proposal fully comply with these requirements below in time to meet the published 
implementation date? 
RR6-84: Linked Replies Information - Sending Linked Replies During Recovery 
RR6-85: Linked Replies Information - Service Provider SOA Linked Replies Indicator Sending of Linked Replies 
RR6-86: Linked Replies Information - Service Provider SOA Linked Replies Indicator Sending of Non-Linked Replies 
RR6-87: Linked Replies Information - Service Provider Local SMS Linked Replies Indicator Sending of Linked Replies 
RR6-88: Linked Replies Information - Service Provider Local SMS Linked Replies Indicator Sending of Non-Linked Replies 
RR6-122: SWIM Recovery Tracking 
RR6-123: Service Provider SOA SWIM Recovery Indicator 
RR6-124: Service Provider SOA SWIM Recovery Indicator Default 
RR6-125: Service Provider SOA SWIM Recovery Indicator Modification 
RR6-126: SOA SWIM Maximum Tunable 
RR6-127: SOA SWIM Maximum Tunable Default 
RR6-128: SOA SWIM Maximum Tunable Modification 
RR6-129: Service Provider LSMS SWIM Recovery Indicator 
RR6-130: Service Provider LSMS SWIM Recovery Indicator Default 
RR6-131: Service Provider LSMS SWIM Recovery Indicator Modification 
RR6-190: LSMS SWIM Maximum Tunable 
RR6-191: LSMS SWIM Maximum Tunable Default 
RR6-192: LSMS SWIM Maximum Tunable Modification 
RR6-199: Service Provider SOA SPID Recovery Indicator 
RR6-200: Service Provider SOA SPID Recovery Indicator Default 
RR6-201: Service Provider SOA SPID Recovery Indicator Modification 
RR6-202: Service Provider LSMS SPID Recovery Indicator 
RR6-203: Service Provider LSMS SPID Recovery Indicator Default 
RR6-204: Service Provider LSMS SPID Recovery Indicator Modification 
RR6-205: Service Provider SOA Cancel-Pending-to-Conflict Cause Code Tunable 
RR6-206: Service Provider SOA Cancel-Pending-to-Conflict Cause Code Tunable Default 
RR6-207: Service Provider SOA Cancel-Pending-to-Conflict Cause Code Tunable Modification 
RR6-208: Service Provider LSMS Cancel-Pending-to-Conflict Cause Code Tunable 
RR6-209: Service Provider LSMS Cancel-Pending-to-Conflict Cause Code Tunable Default 
RR6-210: Service Provider LSMS Cancel-Pending-to-Conflict Cause Code Tunable Modification 
(no answer)
Yes
No
6.8* QUESTION:
TRD FRS Section 6: Sub Section 6.8: Out-Bound Flow Control Requirements 
The following requirements define the Out-Bound Flow Control functionality. 
Does the Respondent's proposal fully comply with these requirements below in time to meet the published 
implementation date? 
Page 70
RR6-148: Out-Bound Flow Control Upper Threshold Tunable 
RR6-149: Out-Bound Flow Control Upper Threshold Tunable Default 
RR6-150: Out-Bound Flow Control Upper Threshold Tunable Modification 
RR6-151: Out-Bound Flow Control Lower Threshold Tunable 
RR6-152: Out-Bound Flow Control Lower Threshold Tunable Default 
RR6-153: Out-Bound Flow Control Lower Threshold Tunable Modification 
(no answer)
Yes
No
6.9* QUESTION:
TRD FRS Section 6: Sub Section 6.9: Roll-Up Activity and Abort Behavior Requirements 
The following requirements define the Roll-up Activity and Abort Behavior functionality. 
Does the Respondent's proposal fully comply with these requirements below in time to meet the published 
implementation date? 
RR6-154: Roll-Up Activity-Single Tunable 
RR6-155: Roll-Up Activity-Single Tunable Default 
RR6-156: Roll-Up Activity-Single Tunable Modification 
RR6-157: Roll-Up Activity Timer Expire SVRange Tunable 
RR6-158: Roll-Up Activity Timer Expire SVRange Tunable Default 
RR6-159: Roll-Up Activity Timer Expire SVRange Tunable Modification 
RR6-160: Abort Processing Behavior Upper Threshold Tunable 
RR6-161: Abort Processing Behavior Upper Threshold Tunable Default 
RR6-162: Abort Processing Behavior Upper Threshold Tunable Modification 
(no answer)
Yes
No
6.10* QUESTION:
TRD FRS Section 6: Sub Section 6.10: NPAC Monitoring of SOA and LSMS Associations Requirements 
The following requirements define the NPAC Monitoring of SOA and LSMS Association functionality. 
Does the Respondent's proposal fully comply with these requirements below in time to meet the published 
implementation date? 
RR6-163: NPAC/SMS Monitoring of SOA and Local SMS Connections via a Application Level Heartbeat 
RR6-164: NPAC/SMS-to-SOA Application Level Heartbeat Indicator 
RR6-165: NPAC/SMS-to-SOA Application Level Heartbeat Indicator Default 
RR6-166: NPAC/SMS-to-SOA Application Level Heartbeat Indicator Modification 
Page 71
RR6-167: NPAC/SMS-to-Local SMS Application Level Heartbeat Indicator 
RR6-168: NPAC/SMS-to- Local SMS Application Level Heartbeat Indicator Default 
RR6-169: NPAC/SMS-to- Local SMS Application Level Heartbeat Indicator Modification 
RR6-170: NPAC/SMS Application Level Heartbeat Tunable Parameter 
RR6-171: NPAC/SMS Application Level Heartbeat Tunable Parameter Usage 
RR6-172: NPAC/SMS Application Level Heartbeat Tunable Parameter Default 
RR6-173: NPAC/SMS Application Level Heartbeat Tunable Parameter Modification 
RR6-174: NPAC/SMS Application Level Heartbeat Timeout Tunable Parameter 
RR6-175: NPAC/SMS Application Level Heartbeat Timeout Tunable Parameter Usage 
RR6-176: NPAC/SMS Application Level Heartbeat Timeout Tunable Parameter Default 
RR6-177: NPAC/SMS Application Level Heartbeat Timeout Tunable Parameter Modification 
(no answer)
Yes
No
6.11* QUESTION:
TRD FRS Section 6: Sub Section 6.11: Separate SOA Channel for Notifications Requirements 
The following requirements define the Separate SOA Channel for Notifications functionality. 
Does the Respondent's proposal fully comply with these requirements below in time to meet the published 
implementation date? 
RR6-178: SOA Notification Channel Service Provider Indicator 
RR6-179: SOA Notification Channel Service Provider Indicator - Default 
RR6-180: SOA Notification Channel Service Provider Indicator - Modification 
RR6-182: Separate Association for the Notification Function From different NSAPs 
RR6-183: Security Management of Multiple SOA Associations of Different Association Functions 
RR6-184: Sending of SOA Notifications when Notification Channel is Active 
RR6-185: Separate Notification Channel during Recovery 
RR6-186: Treatment of Multiple Associations when there is an Intersection of Association Function 
(no answer)
Yes
No
6.12* QUESTION:
TRD FRS Section 6: Sub Section 6.12: Maintenance Window Timer Behavior Requirements 
The following requirements define the Maintenance Window Timer Behavior. 
Does the Respondent's proposal fully comply with these requirements below in time to meet the published 
implementation date? 
Page 72
RR6-187: NPAC Maintenance Windows - Timer Update Tool 
RR6-188: NPAC Maintenance Windows - Timer Update Tool - Affected Timers 
(no answer)
Yes
No
7. TRD FRS Section 7: SECURITY
7.1 STATEMENT:
TRD FRS Section 7: Sub Section 7.1: Security Overview 
In addition to the general security requirements based on the user interface paradigm, there are requirements for the 
security on an OSI application-to-application interface (such as the one specified in Section 6, NPAC/SMS Interfaces, for 
the SMS to SMS and SMS to SOA interfaces). 
7.2* QUESTION:
TRD FRS Section 7: Sub Section 7.2: Identification Requirements 
The NPAC will accept only authorized NPAC customers through interface connections, and among NPAC customers, the 
NPAC will make appropriate limitations on their actions (for example, letting only old or new Service Providers view a 
pending record). The NPAC will only accept authorized customer user IDs. However, the NPAC will make no distinction 
among an NPAC customer's employees; the NPAC customer and their systems must control individual NPAC customer 
employee actions. 
A user identification is a unique, auditable representation of the user's identity within the system. The NPAC/SMS requires 
all system users, both individuals and remote machines, to be uniquely identified to support individual accountability over 
the NPAC Administrative and NPAC SOA Low-tech Interfaces. 
Does the Respondent's proposal fully comply with these requirements below in time to meet the published 
implementation date? 
R7-1: Unique User Identification Codes - Individuals 
R7-2: Assigned Userid Identification 
R7-3: Current Active User List Maintenance 
R7-4: User Invoked Processes 
R7-5.1: Userids, Unused - Disabling 
R7-5.2: Unused Userid Disable Period - Tunable Parameter 
R7-5.3: Unused Userid Disable Period - Tunable Parameter Modification 
R7-5.4: Unused Userid Disable Period - Tunable Parameter Default 
R7-6.1: Userids, Disabled - Reinstatement 
R7-6.2: Userids - Deletion 
R7-7: Userids - Temporary Disabling 
R7-8: Userids, Disabled - Automatic Reactivation 
Page 73
R7-9.1: Userids - One Active Login 
R7-9.2: Second Login Attempt 
(no answer)
Yes
No
7.3* QUESTION:
TRD FRS Section 7: Sub Section 7.3: Authentication 
The identity of all NPAC/SMS system users, both individuals and remote machines, must be verified or authenticated to 
enter the system, and to access restricted data or transactions over the NPAC Administrative and NPAC SOA Low-Tech 
Interfaces. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
R7-10: User Authentication 
R7-12: Authentication Data Protection 
(no answer)
Yes
No
7.3.1* QUESTION:
TRD FRS Section 7: Sub Section 7.3.1: Password Requirements 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
R7-13: Passwords - Non-shared 
R7-14: Passwords - Userid Unique 
R7-15: Passwords - One-Way Encrypted 
R7-16: Passwords, Encrypted - Privileged Users Access Control 
R7-18: Passwords, Entry - Automatic Clear Text Suppression 
R7-19: Passwords - Network Transmission Clear Text Suppression 
R7-20: Passwords - Non-Null 
R7-21: Passwords - User-Changeable 
R7-22: Passwords - Reset Capability 
R7-23.1: Passwords - Aging Enforcement 
R7-23.2: Password Aging Default 
R7-24.1: Passwords - Expiration Notification 
R7-24.2: Passwords - Expiration Notification Default 
R7-24.3: Passwords - Require User to Enter New Password 
R7-25.1: Passwords - Non-Reusable 
R7-25.2: Password Reuse Default 
R7-26.1: Passwords - Minimum Structure Standard #1 
Page 74
R7-26.2: Passwords - Associated Userid 
R7-27.1: Password Generator 
R7-27.2: Passwords, System Generated - Attack Resistant 
R7-27.3: Passwords, System Generated - Random 
(no answer)
Yes
No
7.4 STATEMENT:
TRD FRS Section 7: Sub Section 7.4: Access Control 
Access to the NPAC/SMS and other resources will be limited to those users that have been authorized for that specific 
access right. 
7.4.1* QUESTION:
TRD FRS Section 7: Sub Section 7.4.1: System Access Requirements 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
R7-28.1: System Access - Individuals
R7-28.2: System Access - Remote Machines 
R7-29.1: System Access, User Information - Entry 
R7-29.2: System Access, User Information - Modification 
R7-31: System Access, Login - Trusted Communication 
R7-32.1: System Access - Disconnect User 
R7-32.2: Non-use Disconnect Tunable Parameter 
R7-33.1: System Access - User Authentication Failure 
R7-33.2: Incorrect Login Exit Default 
R7-34: System Access, User Authentication Failure - Notification 
R7-35.1: System Access - Login Process I/O Port Restart 
R7-35.2: Login Process Restart Default 
R7-36: System Access, User Authentication Failure - Userid Non-Suspension 
R7-37: System Access, User Authentication Procedure - Entry 
R7-38: System Access, User Authentication Procedure Entry - Error Feedback 
R7-39: System Access, User Authentication Procedure Entry - Time Parameters 
R7-40.1: System Access, User Authentication Procedure Entry - Method 
R7-40.2: System Access, User Authentication Procedure Entry - Location 
R7-41: System Access, User Authentication Procedure Entry - SSL VPN Limitations 
R7-42.1: System Access - Network Basis 
R7-42.2: System Access - Per-Port Basis 
R7-43.1: System Access, Network Authentication 
R7-43.2: Internet Access 
R7-43.3: SSL VPN Access 
R7-44: System Access - Secure Logoff Procedures 
R7-46: System Access, Unauthorized Use Message - Specifiable 
Page 75
R7-47.1: System Access, Unauthorized Use Message - Specifiable (Warning) 
R7-47.2: Advisory Warning Message Default 
R7-48.1: System Access - User's Last Successful Access 
R7-48.2: System Access - User's Unsuccessful Access Attempts 
R7-49.1: System Access, Security Administration - Authorize Users 
R7-49.2: System Access, Security Administration - Revoke Users 
R7-50.1: System Access, Security Administration - Adding Users 
R7-50.2: System Access, Security Administration - Deleting Users 
(no answer)
Yes
No
7.4.2* QUESTION:
TRD FRS Section 7: Sub Section 7.4.2: Resource Access 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
R7-51: Data Access for Authorized Users 
R7-52: Service Provider Data Protected 
R7-53.1: Authorized User Access to Software 
R7-53.2: Authorized User Access to Transactions 
R7-53.3: Authorized User Access to Data 
R7-54.1: Access Control of Executable Software 
R7-55: Access Control of Resources 
R7-56: User ID and System ID 
R7-57: Resource Access to Users 
R7-58: Resource Access Denied to Users 
R7-60: Only NPAC Personnel Can Modify User Access 
R7-61: Removal of User Access Rights 
(no answer)
Yes
No
7.5* QUESTION:
TRD FRS Section 7: Sub Section 7.5: Data and System Integrity 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
R7-63: Identify Originator of System Resources 
R7-64: Identify Originator of Information Received Across Communication Channels 
R7-65.1: Monitor System Resources 
Page 76
R7-65.2: Detect Error Conditions 
R7-65.3: Detect Communication Errors 
R7-65.4: Detect Link Outages 
R7-66.1: Rule Checking on Update 
R7-66.2: Handling of Duplicate Inputs 
R7-66.3: Check Return Status 
R7-66.4: Validate Inputs 
R7-66.5: Transaction Serialization 
R7-67: Database Integrity Checking 
(no answer)
Yes
No
7.6 STATEMENT:
TRD FRS Section 7: Sub Section 7.6: Audit 
7.6.1* QUESTION:
TRD FRS Section 7: Sub Section 7.6.1: Audit Log Generation Requirements 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
R7-68.1: Security Audit Log for After the Fact Investigation 
R7-68.2: Security Audit Data Availability 
R7-68.3: Security Audit Data Archived 
R7-69: User Identification Retained 
R7-70: Protection of Security Audit Log Access 
R7-71.2: NPAC Personnel Delete Security Audit Log 
R7-72: Security Audit Control Protected 
R7-73.1: Log Invalid User Authentication Attempts 
R7-73.2: Log NPAC/SMS End User Logins 
R7-73.3: Log NPAC Personnel Activities 
R7-73.4: Log Unauthorized Data Access 
R7-73.5: Log Unauthorized Transaction Access 
R7-74: No Disable of Security Auditing 
R7-75: Security Audit Record Contents 
R7-76.1: Recorded Login Attempts 
(no answer)
Yes
No
Page 77
7.6.2* QUESTION:
TRD FRS Section 7: Sub Section 7.6.2 : Reporting and Intrusion Detection Requirements 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
R7-77.1: Exception Reports on Data Items 
R7-77.2: Exception Reports on Users 
R7-77.3: Exception Reports on Communication Failures 
R7-77.4: Summary Reports on Data Items 
R7-77.5: Summary Reports on Users 
R7-77.6: Summary Reports on Communication Failures 
R7-77.7: Detailed Reports on Data Items 
R7-77.8: Detailed Reports on Users 
R7-77.9: Detailed Reports on Communication Failures 
R7-78: Review User Actions 
R7-79.1: Monitor Network Address 
R7-80.1: Real-time Security Monitor 
R7-80.2: Security Event Notification 
(no answer)
Yes
No
7.7* QUESTION:
TRD FRS Section 7: Sub Section 7.7: Continuity of Service 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
R7-81: System Made Unavailable by Service Provider 
R7-82: Detect Service Degrading Conditions 
R7-83: System Recovery After Failure 
R7-84.1: Software Backup Procedures 
R7-84.2: Data Backup Procedures 
R7-84.3: Software Restoration Procedures 
R7-84.4: Data Restoration Procedures 
R7-85.1: Software Version Number (Installed) 
R7-85.2: Software Version Number 
(no answer)
Yes
No
Page 78
7.8* QUESTION:
TRD FRS Section 7: Sub Section 7.8: Software Vendor 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
R7-86: Software Development Methodology 
R7-87: Bypass of Security 
R7-88: Documented Entry 
(no answer)
Yes
No
7.9 STATEMENT:
TRD FRS Section 7: Sub Section 7.9: OSI Security Environment 
7.9.1 STATEMENT:
TRD FRS Section 7: Sub Section 7.9.1: Threats 
Attacks against the NPAC/SMS may be perpetrated in order to achieve any of the following: 
1. Denial of service to a customer by placing wrong translation information in the SMS 
2. Denial of service to a customer by preventing a valid message from reaching the SMS 
3. Disrupting a carrier's operations by having numerous spurious calls (to users who are not clients of that carrier) 
directed to that carrier 
4. Switching customers to various carriers without their consent 
5. Disrupting the functioning of the NPAC/SMS by swamping it with spurious messages 
7.9.2* QUESTION:
TRD FRS Section 7: Sub Section 7.9.2: Security Services 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
R7-89: Authentication 
R7-90: Data Origin Authentication 
R7-91.1: Detection of Message Replay 
R7-91.2: Deletion of a Message 
R7-91.3: Modification of a Message 
R7-91.4: Delay of a Message 
Page 79
R7-92: Non-repudiation of Origin 
R7-93: Access Control 
(no answer)
Yes
No
7.9.3 STATEMENT:
TRD FRS Section 7: Sub Section 7.9.3: Security Mechanisms 
 
7.9.3.1* QUESTION:
TRD FRS Section 7: Sub Section 7.9.3.1: Encryption 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
R7-94.1: Public Key Crypto System (PKCS) 
R7-95: RSA Encryption Modulus Size 
(no answer)
Yes
No
 
7.9.3.2* QUESTION:
TRD FRS Section 7: Sub Section 7.9.3.2: Authentication 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
R7-96: Digital Signature Algorithm 
R7-97: Authenticator Contents 
R7-98: Authenticator in Access Control Field 
R7-99.1: Subsequent Messages Contain Access Control Field 
R7-99.2: Separate Counter for Association Sequence Numbers 
R7-99.3: Increment Sequence Numbers 
(no answer)
Yes
No
Page 80
 
7.9.3.3* QUESTION:
TRD FRS Section 7: Sub Section 7.9.3.3: Integrity and Non-Repudiation 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
R7-100.1: Security Field 
R7-100.2: Security Field Syntax 
R7-102: Notifications in Confirmed Mode 
(no answer)
Yes
No
 
7.9.3.4* QUESTION:
TRD FRS Section 7: Sub Section 7.9.3.4: Access Control 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
R7-104: Responsible for Access Control 
R7-105.2: Generalized Time - Valid Message Timeframe 
RR7-3: Generalized Time - Departure Time Threshold Tunable Parameter 
RR7-4: Generalized Time - Departure Time Threshold Tunable Parameter Default 
(no answer)
Yes
No
 
7.9.3.5* QUESTION:
TRD FRS Section 7: Sub Section 7.9.3.5: Audit Trail 
Does the Respondent's proposal fully comply with the requirement below in time to meet the published 
implementation date? 
R7-106: Log Contents 
Page 81
(no answer)
Yes
No
 
7.9.3.6* QUESTION:
TRD FRS Section 7: Sub Section 7.9.3.6: Key Exchange 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
R7-107.1: Lists of Keys 
R7-107.2: Keys in Electronic Form 
R7-107.4: Key List Exchange 
R7-107.5: Remote Key List Exchange 
R7-108.1: Remote Reception Acknowledgment 
R7-108.2: Acknowledgment Contents 
R7-108.3: Phone Confirmation 
R7-110.1: List Encryption Keys 
R7-110.3: List Encryption Keys (Unique Numbering of Keys) 
R7-111.1: New Encryption Key Can Be Chosen 
R7-111.2: Keys Not Reused 
R7-111.3: Compromised Keys 
R7-111.4: Key Change Once Per Year 
R7-111.5: Key Size Increase Per Year 
R7-111.6: Per Service Provider Application Basis 
R7-111.7: NPAC Key Change Algorithm 
R7-111.8: Service Provider Key Marked Used/Invalid 
RR7-1: Load Key List 
RN7-1: Authenticator Contents - Individual System Clock Accuracy 
RN7-2: Authenticator Contents - Zero Sequence Number 
(no answer)
Yes
No
8. TRD FRS Section 8: AUDIT ADMINISTRATION
8.1*
QUESTION:
TRD FRS Section 8: Sub Section 8.1: Overview 
Page 82
Does the Respondent's proposal fully comply with the requirement below in time to meet the published 
implementation date? 
A8-1: Service Provider Audits Issued Immediately 
(no answer)
Yes
No
8.2* QUESTION:
TRD FRS Section 8: Sub Section 8.2: Service Provider User Functionality 
Does the Respondent's proposal fully comply with these requirements below in time to meet the published 
implementation date? 
RR8-19: Service Provider Audit Request – Required Information 
R8-3: Service Providers Specify Audit Scope 
(no answer)
Yes
No
8.3* QUESTION:
TRD FRS Section 8: Sub Section 8.3: NPAC User Functionality Requirements 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR8-20: NPAC Personnel Audit Request – Required Information 
R8-61: Specify an Immediate Audit Request 
R8-9: NPAC Personnel Specify Audit Scope 
R8-10: NPAC Personnel Status of Audit Request 
R8-11: Audit Progress Indicators 
R8-12: NPAC Personnel Cancel of an Audit 
(no answer)
Yes
No
8.4* QUESTION:
TRD FRS Section 8: Sub Section 8.4: System Functionality Requirements 
Page 83
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
R8-15.1: NPAC Personnel View of ALL Audit Requests 
R8-15.2: Mechanized SOA Interface Obtain Audit Requests 
R8-15.3: Send Audit Results to Originating SOA 
R8-16.1: Flow of Audit Execution
R8-17.1: Compare NPAC/SMS Subscription Versions to Service Provider Subscription Versions 
R8-17.2: Add TNs to Service Provider Subscription Versions 
R8-17.3: Modify Erroneous TNs 
R8-17.4: Delete Discrepant TNs from Service Provider Subscription Versions 
R8-19: Record Audit Results in an Audit Log 
RR8-4: Skip Subscription Versions with a Status of Sending 
RR8-5: Report No Discrepancies Found in Audit Results for Skipped Subscription Versions 
RR8-21: Audit for Support of SV Type 
RR8-22: Audit for Support of Alternative SPID 
RR8-26: Audit for Support of Last Alternative SPID 
RR8-27: Audit for Support of Voice URI 
RR8-28: Audit for Support of MMS URI 
RR8-29: Audit for Support of SMS URI 
(no answer)
Yes
No
8.5* QUESTION:
TRD FRS Section 8: Sub Section 8.5: Audit Report Management Requirements 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
R8-20: Service provider Audit Retrieval 
R8-21.1: Generate an Audit Report 
R8-21.2: Audit Report Contents 
R8-23.1: NPAC Personnel View an In-progress Audit Report 
R8-22: NPAC Personnel Generate and View an Audit Report 
R8-23.2: Service Providers View Results of Audits They Have Requested 
R8-25: NPAC Personnel Specify Time Audit Results Retained 
(no answer)
Yes
No
8.6* QUESTION:
TRD FRS Section 8: Sub Section 8.6: Additional Requirements 
Page 84
Does the Respondent's proposal fully comply with the requirement below in time to meet the published 
implementation date? 
RX8-1: Valid Audit Statuses 
(no answer)
Yes
No
8.7* QUESTION:
TRD FRS Section 8: Sub Section 8.7: Database Integrity Sampling 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR8-1: Random Sampling of Active Subscription Versions 
RR8-2.1: Data Integrity Sample Size - Tunable Parameter 
RR8-2.2: Data Integrity Sample Size - Tunable Parameter Modification 
RR8-2.3: Data Integrity Sample Size - Tunable Parameter Default 
RR8-3.1: Data Integrity Frequency - Tunable Parameter 
RR8-3.2: Data Integrity Frequency - Tunable Parameter Modification 
RR8-3.3: Data Integrity Frequency - Tunable Parameter Default 
(no answer)
Yes
No
8.8* QUESTION:
TRD FRS Section 8: Sub Section 8.8: Audit Processing in a Number Pool Environment Requirements 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR8-6: Audit Processing for All Subscription Versions in a Number Pooling Environment 
RR8-7: Audit Discrepancy and Results Notifications for Pooled Number Subscription Versions to Requesting SOA 
RR8-8: Audit Discrepancy and Results Notifications for Pooled Number Subscription Versions for Audited TNs 
RR8-9: Audit Status Attribute Value Change Notification Send for Pooled Number Blocks 
RR8-10: Audit Attribute Value Change Notification Send for Pooled Number Blocks 
RR8-11: Audit for Pooled Numbers and Block to EDR Local SMS 
RR8-12: Audit Response – Ignore missing SVs for Pooled Ports at EDR Local SMS 
RR8-13: Audit Response – Delete erroneous SVs for Pooled Ports at EDR Local SMS 
RR8-14: Audit Response – Compare NPAC/SMS Block to Service Provider Block at EDR Local SMS 
RR8-15: Audit Response – Block Missing from EDR Local SMS 
RR8-16: Audit Response – Block Discrepant at EDR Local SMS 
Page 85
RR8-17: Audit Response – Extra Block at EDR Local SMS 
RR8-18: Audit Processing – Skipping In-Progress Blocks 
(no answer)
Yes
No
8.9* QUESTION:
TRD FRS Section 8: Sub Section 8.9: Audit Processing in a Pseudo-LRN Environment Requirements 
The Audit processing that is described in this section deals with all Subscription Versions and Number Pool Blocks in a 
pseudo-LRN environment. Audit processing in a pseudo-LRN environment will use the information in the Service 
Provider’s profile (NPAC Customer LSMS Pseudo-LRN Indicator) to determine whether to send a query for a TN/TN 
Range and/or Number Pool Block. 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR8-30: Audit of Pseudo LRN Subscription Versions-Query all LSMSs. 
RR8-31: Audit of Pseudo LRN Subscription Version-Roll up Query results only for supporting LSMS. 
RR8-32: Audit of Pseudo LRN Number Pool Block query all LSMSs. 
RR8-33: A1Audit of Pseudo LRN Number Pool Block- Roll up query results only for supporting LSMS. 
RR8-34: Audit of Pseudo LRN Subscription Version Send Audit results to Originating SOA. 
RR8-35: Audit of Pseudo LRN Number Pool Block- Send Audit results to Originating SOA. 
RR8-36: Add/Modify /Delete TNs to Service Provider Pseudo LRN Subscription Versions. 
(no answer)
Yes
No
9. TRD FRS Section 9: REPORTS
9.1 STATEMENT:
TRD FRS Section 9: Sub Section 9.1: Overview 
The NPAC/SMS must support scheduled and ad hoc report generation for selectable reports. The report generation 
service shall create output report files according to specified format definitions, and distribute reports to output devices as 
requested. A report distribution service shall be used to distribute report files to selected output devices. Authorized 
NPAC personnel can request reports from active database, history logs, error logs, traffic measurements, usage 
measurements, and performance reports. 
Page 86
9.2* QUESTION:
TRD FRS Section 9: Sub Section 9.2: National Number Pooling Reports Requirements 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
R9-1: NPAC Personnel Report Selection 
R9-2: NPAC Personnel Selection of Output Destination 
R9-3: NPAC Personnel Re-print of Reports 
R9-4: NPAC Personnel Create Customized Reports 
R9-5: NPAC Personnel Define Scope and Filtering 
R9-6: Service Providers Receive Reports on Their Activities 
RX9-1: Service and Network Data Reports 
RX9-2: Service Provider Reports 
RX9-3: Subscription Data Reports 
RX9-4: System Reports 
RX9-5: Security Reports 
RX9-6: Log File Reports 
RX9-7: Audit Reports 
RX9-8: Regularly Scheduled Reports 
RR9-1: Data Integrity Report - Database Sample Report 
RR9-39: Pseudo-LRN Data in Reports - Service Provider Personnel 
RR9-40: Pseudo-LRN Data in Reports - NPAC Personnel 
(no answer)
Yes
No
9.3* QUESTION:
TRD FRS Section 9: Sub Section 9.3: System Functionality Requirements 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
R9-9: Verification of User Privileges 
R9-10: Support of On-Line Fire Transfer 
R9-11: Transaction History Log 
R9-12.1: Error Log - Transaction Errors 
R9-12.2: Error Log - Transmission Errors 
(no answer)
Yes
No
Page 87
9.3.1* QUESTION:
TRD FRS Section 9: Sub Section 9.3.1: National Number Pooling Reports Requirements 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR9-2: Pooled Number Reports - Query functions 
RR9-3: Pooled Number Reports - Block Holder Default Routing Report Data Elements 
RR9-4: Pooled Number Reports - Block Holder Default Routing Report Page Break 
RR9-7: Pooled Number Reports - OpGUI Report Generation 
RR9-8: Pooled Number Reports - Block Holder Default Routing Report 
RR9-9: Pooled Number Reports - Active-Like TNs in a NPA-NXX-X Report 
RR9-10: Pooled Number Reports - Active-Like TNs in a NPA-NXX-X Report Data Elements 
RR9-11: Pooled Number Reports - Pending-Like No-Active and Pending-Like Port-to-Original Subscription Versions Report 
RR9-12: Pooled Number Reports - Pending-Like No-Active and Pending-Like Port-to-Original Subscription Versions Report 
Data Elements 
RR9-13: Pooled Number Reports - Pending-Like No-Active and Pending-Like Port-to-Original Subscription Versions Report 
Sort Priority 
RR9-14: Pooled Number Reports - Pending-Like No-Active and Pending-Like Port-to-Original Subscription Versions Report 
Page Break 
RR9-15: Pooled Number Reports - Pending-Like With Active POOL Subscription Versions Report 
RR9-16: Pooled Number Reports - Pending-Like With Active POOL Subscription Versions Report Data Elements 
RR9-17: Pooled Number Reports - Pending-Like With Active POOL Subscription Versions Report Sort Priority 
RR9-18: Pooled Number Reports - Pending-Like With Active POOL Subscription Versions Report Page Break 
(no answer)
Yes
No
9.3.2* QUESTION:
TRD FRS Section 9.3: Sub Section 9.3.2: Cause Code Reports Requirements 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR9-19: Logging Cause code usage by SPID Reporting 
RR9-20: Cause Code Usage Log Report via OpGUI 
RR9-21: Cause Code Usage Log Report Monthly Generation 
RR9-22: Cause Code Usage Log Report Sort Criteria 
RR9-23: Cause Code Usage Log Report Selection Criteria 
RR9-24: Cause Code Usage Log Report Display 
(no answer)
Yes
No
Page 88
9.3.3* QUESTION:
TRD FRS Section 9: Sub Section 9.3.3: Resend Excluded Service Provider Report Requirements 
Does the Respondent's proposal fully comply with the requirements below in time to meet the published 
implementation date? 
RR9-25: Subscription Version Failed SP List - Excluded Service Provider Log Data Availability for the Excluded Service 
Provider Report 
RR9-26: Subscription Version Failed SP List - Resend Excluded Service Provider Report by Current SPID via OpGUI 
RR9-27: Subscription Version Failed SP List - Resend Excluded Service Provider Report by Current SPID Request 
RR9-28: Subscription Version Failed SP List - Resend Excluded Service Provider Report by Current SPID Request Sort 
Criteria 
RR9-29: Subscription Version Failed SP List -Resend Excluded Service Provider Report by Excluded SPID via OpGUI 
RR9-30: Subscription Version Failed SP List - Resend Excluded Service Provider Report by Excluded SPID Request 
RR9-31: Subscription Version Failed SP List -Resend Excluded Service Provider Report by Excluded SPID Request Sort 
Criteria 
RR9-32: Number Pool Block Failed SP List - Excluded Service Provider Log Data Availability for the Excluded Service 
Provider Report 
RR9-33: Number Pool Block Failed SP List -Resend Excluded Service Provider Report by Current SPID/Blockholder SPID 
via OpGUI 
RR9-34: Number Pool Block Failed SP List - Resend Excluded Service Provider Report Request by Current 
SPID/Blockholder SPID 
RR9-35: Number Pool Block Failed SP List - Resend Excluded Service Provider Report by Current SPID/Blockholder SPID 
Request Sort Criteria 
RR9-36: Number Pool Block Failed SP List -Resend Excluded Service Provider Report by Excluded SPID via OpGUI 
RR9-37: Number Pool Block Failed SP List - Resend Excluded Service Provider Report by Excluded SPID Request 
RR9-38: Number Pool Block Failed SP List -Resend Excluded Service Provider Report by Excluded SPID Request Sort 
Criteria 
(no answer)
Yes
No
10. TRD FRS Section 10: PERFORMANCE AND RELIABILITY
10.1* QUESTION:
TRD FRS Section 10: Sub Section 10.1: Availability and Reliability 
This section defines the reliability, availability, performance and capacity requirements for the NPAC/SMS. The NPAC/SMS 
will be designed for high reliability, including fault tolerance and data integrity features, symmetrical multi processing 
capability, and allow for economical and efficient system expansion. 
Does the Respondent's proposal fully comply with these requirements in time to meet the published 
implementation date? 
Page 89
R10-1: System Availability 
R10-2: System Reliability 
R10-3: Unscheduled Downtime 
R10-4: Mean Time to Repair for Unscheduled Downtime 
R10-5: Scheduled Downtime 
AR10-1: Scheduled Downtime 
R10-6.1: Communication Link Monitoring 
R10-6.2: Detecting Communication Link Failures 
R10-7: Detecting Single Bit Data Transmission Errors 
R10-8: Continue Transaction Processing After Downtime 
R10-9.1: Self Checking Logic 
R10-9.2: Continuous Hardware Checking 
R10-9.3: Duplexing of Hardware 
R10-9.4: Transparent Hardware Fault Tolerance 
R10-10.1: Service Provider Notification of System Unavailability 
R10-10.2: System Availability Notification Method 
R10-10.3: System Availability Notification Contents 
R10-11: Updates Highest Priority 
R10-12.1: Tolerance to Communication Link Outages 
R10-12.2: Alternate routing 
R10-13.1: Switch to Backup or Disaster Recovery Machine 
R10-13.2: Time to Switch Machines 
R10-13.3: Total Disaster Recovery 
R10-13.4: Full Functionality Restored 
R10-14: Reports on Reliability 
(no answer)
Yes
No
10.2* QUESTION:
TRD FRS Section 10: Sub Section 10.2: Capacity and Performance 
Does the Respondent's proposal fully comply with these requirements in time to meet the published 
implementation date? 
R10-16: Capacity 
R10-18: History File Data Storage 
R10-19: Broadcast Update Response Time 
R10-20: Request/Transaction Response Time 
R10-21: Future System Growth 
(no answer)
Yes
No
Page 90
10.3* QUESTION:
TRD FRS Section 10: Sub Section 10.3: Requirements Not Given a Unique ID 
Does the Respondent's proposal fully comply with these requirements in time to meet the published 
implementation date? 
RN10-2: Return to the Primary Machine SOA Notification 
RN10-3: Return to the Primary Machine Local SMS Notification 
RN10-4: Database Sync after Return to the Primary Machine 
(no answer)
Yes
No
11. TRD FRS Section 11: BILLING
11.1* QUESTION:
TRD FRS Section 11: Sub Section 11.1: User Functionality 
Does the Respondent's proposal fully comply with the requirements below, in time to meet the published 
implementation date? 
R11-1: Toggling the Generation of Usage Measurements 
A11-2: Accounting Measurements Will Not Degrade the Basic System Performance 
(no answer)
Yes
No
11.2* QUESTION:
TRD FRS Section 11: Sub Section 11.2: System Functionality 
Does the Respondent's proposal fully comply with the requirements below, in time to meet the published 
implementation date? 
Page 91
R11-2: Generating Usage Measurements for NPAC Resources 
R11-3: Generating Usage Measurements for Allocated Connections 
R11-4: Generating Usage Measurements for Allocated Mass Storage 
R11-5: Generating Usage Measurements for the Number of Messages Processed by type
R11-6: Generating Usage Measurements for the Number of Messages Downloaded 
R11-8: Generating Detailed Usage Measurement Reports 
R11-9: Billing Report Types 
R11-10: Full Billing Report 
R11-11: Billing Report Creation by NPAC Personnel 
R11-12: Billing Report Creation by Service Provider 
R11-13: NPAC Personnel Billing Report Destination 
R11-14: Service provider Billing Report Destination 
R11-15: NPAC Personnel Only can Access Billing System 
(no answer)
Yes
No
12. TRD Detailed Response
12.1* QUESTION:
Please attach a SUMMARY document explaining how the Respondent's proposal addresses the requirements defined in 
this TRD survey, and explain in detail any differences and suggested areas of improvement (as an example, reduction of 
BDD processing time), or enhancements which may affect the NPAC/SMS implementation, ensuring the Respondent's 
proposal will not interfere with or degrade any porting/pooling activities.
This summary document should also be used to include an explanation of any "No" responses. 
Attachments:
Attach a file to this answer