AWARD
70 -- Internet-based TRS Telephone Numbering Directory
- Notice Date
- 9/11/2008
- Notice Type
- Award Notice
- NAICS
- 541512
— Computer Systems Design Services
- Contracting Office
- Federal Communications Commission, Office of the Managing Director, Contracts and Purchasing Center, 445 12th Street, SW, Washington, District of Columbia, 20554
- ZIP Code
- 20554
- Solicitation Number
- 08000022
- Archive Date
- 9/16/2008
- Point of Contact
- Arnett A. Rogiers,, Phone: 202-418-1973
- E-Mail Address
-
arnett.rogiers@fcc.gov
- Small Business Set-Aside
- N/A
- Award Number
- PUR08000449
- Award Date
- 9/8/2008
- Awardee
- NeuStar, 46000 Center Oak Plaza, Sterling, Virginia 20166, United States
- Award Amount
- $1,541,000.00
- Description
- The Contractor will be responsible for providing and operating a system meeting all of the objectives of this solicitation. The contract covers the implementation period beginning with Contract award and ending December 31, 2008, and the operation for 12 months thereafter, with two additional 12-month option renewal periods or any parts thereof to be exercised at the discretion and best interest of the Government. Specific requirements for the key tasks include the following: •Information to be provisioned in a central database. Connectivity between Internet-based TRS and the telephone network cannot be achieved simply by assigning telephone numbers to Internet-based TRS users, because the networks upon which the Internet portions of Internet-based TRS operate ultimately require Internet Protocol (IP) addresses rather than NANP telephone numbers for routing. In order to allow calling as described above to be appropriately routed and completed, a central Numbering Directory database must be created for mapping the telephone number assigned to an Internet-based TRS user to an appropriate endpoint identifier. The FCC has found that a Uniform Resource Identifier (URI) is the appropriate endpoint identifier to link to each ten-digit phone number and to maintain in the central database. For VRS users the URI includes the user’s video terminal endpoint IP address, and for IP Relay Service users the URI contains information which can subsequently be resolved to an IP address (e.g., a fully qualified domain name and user identifier for instant message access). The FCC anticipates that shortly following initial availability the Numbering Directory will be populated with as many as two hundred thousand such entries, increasing to as many as a million in the first three years. •Means for Provisioning to the Central Database. Every provider of Internet-based TRS is required to provide Internet-based TRS users with the capability to register with that Internet-based TRS provider as a “default provider” and provide or port for that user a NANP telephone number. Such registration is required to allow an Internet-based TRS provider to take steps to associate the Internet-based TRS user’s telephone number with the URI information needed for call routing and completion. (Independent from the central Numbering Directory described herein, a 10-digit telephone number assigned to a user will also support the Internet-based TRS provider’s local provisioning of telephone-network-based 911 services.) The information in the central database linking an Internet-based TRS user’s assigned 10-digit phone number and the user’s URI information is entered into the database by the user’s default provider. Only that default provider will have permissions to create and update the central database record associated with the assigned ten-digit number. Because Internet-based TRS providers are not required to offer all Internet-based TRS services, an Internet-based TRS user may register with different TRS providers for different Internet-based TRS services. For example, a user could be assigned a ten-digit phone number by the user’s default provider for IP Relay Service and the same user could be assigned a different ten-digit phone number by a different provider acting as the user’s default VRS provider. The FCC anticipates that as many as twenty Internet-based TRS provider entities will require secure access for testing and initial operational access to the database, and that this number may increase or decrease over time. •Authorized Access to the Central Database. By default, all of an end user’s inbound and outbound calls will be routed through the Internet-based TRS user’s default provider, which may have a local copy of the URI information needed for call routing and completion. However, a deaf, hard of hearing or speech-impaired party or a hearing party can affirmatively select among any Internet-based TRS providers on a call-by-call basis. When a calling party does select an Internet-based TRS provider other than the default provider, the selected provider consults the Numbering Directory entry for the ten-digit number being called to determine the appropriate routing information. Access to the Numbering Directory is thus restricted to Internet-based TRS providers making queries on a call-by-call basis over secure connections. Any download of multiple records to an Internet-based TRS provider in a single transaction is restricted to those records for which the Internet-based TRS provider has provisioning responsibility. •Local Number Portability. Consistent with Local Number Portability, an Internet-based TRS user may select and register with a new default provider at any time and have his 10-digit number ported to that provider. In conjunction with porting the number to a new default provider, the restricted access to the central database record associated with that ten-digit number is shifted to the new default provider and the old default provider is advised to purge any local copy of the mapping between ten-digit number and URI, and to consult the central database for that number thereafter. •Additional Security Considerations. The numbering directory will be accessible at two or more geographically and network-topologically diverse locations and protected from network intrusions that threaten reliable and secure operation. Other operational responsibilities include appropriate repair and replacement plans for any components likely to sustain damage or experience degraded operating efficiency. •Reporting and Data Retention. In addition to normal records management associated with such systems, the system should provide the FCC with access to reports specific to the Numbering Directory services. For example, although the FCC does not anticipate that Internet-based TRS users will have an incentive to register with multiple default providers and receive multiple phone numbers for the same service, the system should be capable of reporting instances where multiple 10-digit phone numbers are linked to a common URI. The system should also be capable of reporting instances where a 10-digit NANP phone number is assigned to a device for which the end-point IP address is in an IP address range not normally allocated to the geographic regions of the U.S. or its possessions. Data retention is only required for operational restoration and for reporting such as describe above over periods not to exceed three months; there is no requirement for long-term data archiving. •System Design and Operations Documentation. System design documents, data dictionaries, technical procedures, and other documents in support of the Numbering Directory system will become the property of the FCC and must be kept up-to-date and available to the FCC. Standard operational and maintenance procedure documents also become the property of the FCC and must be kept up-to-date and available to the FCC.
- Web Link
-
FedBizOpps Complete View
(https://www.fbo.gov/?s=opportunity&mode=form&id=aa98f897e3d26ba0d1b6e5953d0120fd&tab=core&_cview=1)
- Record
- SN01667050-W 20080913/080911224722-aa98f897e3d26ba0d1b6e5953d0120fd (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |