5.1.1 Voice Services (VS) (L.34.1.4.6; C.2.2.1) The offeror shall describe each of the optional services offered. Table L.34.1-4 shows the Transport/IP/Optical Services that shall be optional to offer. Tables J.9.1.1.2 (b) Technical Stipulated Requirements for Optional IP-Based Services and J.9.1.1.3 (b) Technical Narrative Requirements for Optional IP-Based Services identify the stipulated and narrative requirements, respectively, that shall apply exclusively to optional services. The offeror shall describe all optional Transport/IP/Optical Services offered to include: 5.1.1.1 Satisfying the Service Requirements (L.34.1.4.6 (c)) A technical description of how the service requirements (e.g., capabilities, features, interfaces) are satisfied for all proposed optional services. 5.1.1.1.1 Capabilities (L.34.1.4.6 (c)) Sprint knows the Federal Government has a large community of voice users throughout the U.S. public sector Sprint Voice VPN Network and also conducts a considerable amount Provides Private Network of business with U.S. citizens, private Benefits without the Associated Cost and Management sector firms, and foreign entities. Sprint Requirements. voice services support voice calls whether Highly reliable, proven, and redundant voice network initiated from on-net locations or from offnet locations after verification of in less than 200 milliseconds Automatic network restoration authorization code, to be connected to all SONET design on-net and off-net locations by direct Intelligent switching and call routing station-to station dialing. Standardized technical and Sprint is proud to offer the Government services platform 99.99% Availability the most advanced voice services in the A self-healing network industry today. We recognize that the Existing voice services exceed Government network is a complex system Government requirements. of national service centers, mainframes, computer telephony integration, outbound traffic and people. Sprint will continue to serve the Government by capitalizing on our current strategic partnership with GSA, which has grown Page 147 March 5, 2007
increasingly strong over the last 16 years. XXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXX We understand through first hand experience the Governments expectations. Over the years, Sprint has kept the Government on the leading edge of technology through a steady stream of innovations and contract modifications designed to match network capabilities to the evolving needs of the user community. Sprint understands that the mission is to be responsive to user requirements and political conditions while simultaneously managing communication costs. Sprint Voice VPN services provide the Government private network features without the cost and management requirements of a private network. Figure 5.1.1-1 depicts the Voice VPN features and architecture. Figure 5.1.1-1. Voice VPN Architecture and Features XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXX Page 148 March 5, 2007
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXX Sprint voice capabilities are compliant with the requirements as outlined in C.2.2.1.1.4. These capabilities are described in Table 5.1.1-1. Table 5.1.1-1. Voice Capabilities Component Uniform Numbering Plan Network Intercept Voice Quality ITU G.711 Capability Sprint will provide the Government with a Uniform Numbering Plan/Dial plan which includes support of Unique Directory, Public Network Address, Agency specific private 700 numbers, Transparency and interconnectivity, Originating and terminating on-net calls, and Contractor network specific numbers as specified in C.2.2.1.1.4. Sprint will support network intercept messages for possible problems which may occur, such as disconnected number, time out during dialing, network congestion, denial of access because the caller is not in the specified area code, denial of access to off-net or non-domestic calls, and other related conditions to include denial of access to features. Sprint will provide voice quality equal to 64 kbps PCM in accordance with ITU G.711. 5.1.1.1.2 Features (L.34.1.4.6 (c)) Sprint voice features are compliant with the requirements as outlined in C.2.2.1.2.1. The voice features are presented in Table 5.1.1-2. Table 5.1.1-2. Voice Features Component Agency-Recorded Message Announcements Authorization Codes/Calling Cards Call Tracing Feature These are an existing Sprint service on FTS2001 and will be offered on the Networx program. The Sprint Networx offering complies with the requirements of C.2.2.1.2.1. Sprint Call Control features provide increased network control by validating each caller s ability to complete a call as dialed. Call Control is available from Off-Net and On-Net locations and on VPN FONCARDSM calls. The Sprint Networx offering complies with the requirements of C.2.2.1.2.1. Sprint will comply with all Voice Service (VS) authorization code/calling card capabilities, including speed dialing using abbreviated dial codes. XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXX Call Tracing is currently supported by the Sprint security department and will be for Networx. Page 149 March 5, 2007
Component Call Screening for Users Internal Agency Accounting Codes Feature Call screening is available from switched and dedicated on-net locations and on VPN FONCARD calls providing user station and trunk group capabilities. Sprint COS features and functions include: COS information is associated with the user, the station, or the trunk group Sprint has over 200 classes of service that may be assigned to each user, station, trunk group, or FONCARD. COS is determined from the ANI, authorization code, traveling COS, or trunk group The COS derived from an authorization code will take precedence over that derived from other means Access restrictions include but are not limited to access to toll free and 900 calls, access to off-net calling, access to other Government networks, access to non-us calling, and access to other than specified NPA/NXXs Feature restrictions allow or restrict access to network features by users or groups of users Time of day, day of week and day of year restrictions are possible and are executable on a per station, per location and per authorization code (overriding the COS of the calling station) basis. Traveling Classmarks are supported. Sprint will support the traveling class mark feature when used in conjunction with a dedicated on-net location. The electronic tandem network emulation allows the DMS-250 to accept the class mark in the following two formats: called number + TCOS and 1 + called number + TCOS. The traveling class mark value must be in the range of 0-7, and no other class of service can be used with the traveling class mark class of service. The traveling class mark will define the calling characteristics and restrictions of the call. Code Block Sprint Call Control service will provide increased network control by validating each caller s ability to complete a call as dialed. Call Control will be available from switched and dedicated on-net locations and on VPN FONCARD calls. Calls can be screened for unauthorized users, stations and trunks. The call control feature will block NPAs, NPA-NXX pairs, and both domestic and international calls to certain numbers. Codes can also be used to override assigned classes of service at dedicated on-net locations. Sprint intercept message will alert the user that their call is being barred due to call type. An example: Your organization does not allow this type of call. Accounting codes enable Agencies to allocate and track calls by division, individual, or any other category desired. For calls involving an NETWORX Calling Card or originating station with a special COS, Sprint will provide the capability to enter additional (up to a maximum Page 150 March 5, 2007
Component Off-Net Information Calls Operator Services Support for Government travel cards Suppression of Calling Number Delivery Feature of eight) digits to identify internal Agency accounting codes for the call. The accounting codes will become part of the CDRs with no additional processing. Sprint supports the requirement for calls to be charged to an authorization code rather than the originating station. The call detail record for such calls will reflect all relevant data for the calls including the internal Agency authorization code. Such calls will not be charged to the originating station. Sprint will support the requirements for Off-Net information calls as specified in C.2.2.1.2.1 (7). Sprint will provide the Government with full-service long distance operator assistance, in English and Spanish. When needed, the Sprint operator will contact an offshore operator for assistance in additional language support for acceptance of charges or desired party for person-to-person to complete a call. Language assistance is provided by an in-country operator for over 300 countries and locations around the world. Operators are available to assist TDD/TTY and other users encountering difficulties while using the service. XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXX Users will not receive a busy tone when calling for operator services. Calls to operators will be answered within five rings 90 percent of the time. Sprint operators will be available to assist users encountering dialing difficulties while using Sprint services and will remain on the line until the call has been connected. XXXXXXXXXXXXXXXXXXXXXXXXXXXXX Sprint currently provides this service on FTS2001 and will continue to provide it for Networx. 5.1.1.1.3 Interfaces (L.34.1.4.6 (c)) Sprint will support/provide all of the User-to-network interfaces at the Agency SDPs listed in Table 5.1.1-3 unless marked Not Proposed. Page 151 March 5, 2007
Table 5.1.1-3. UNI Types and Features UNI Type Interface Type and Standard 1 Analog Line: Two-Wire (Std: Telcordia SR TSV-002275) 2 Analog Line: Four-Wire (Std: Telcordia SR-TSV-002275) 3 Analog Trunk: Two-Wire (Std: Telcordia SR-TSV-002275) 4 Analog Trunk: Four-Wire (Std: Telcordia SR-TSV-002275) 5 Analog Trunk: Four-Wire (Std: Telcordia SR-TSV-002275) 6 Digital Trunk: T1 (Std: Telcordia SR TSV-002275 and ANSI T1.102/107/403) 7 Digital Trunk: ISDN PRI T Reference Point (Std: ANSI T1.607 and 610) 8 Digital: T3 Channelized (Std: Telcordia GR-499 CORE) 9 (Non-US) Digital Trunk: E1 Channelized (Std: ITU-TSS G.702) 10 Optical: SONET OC-1 (Std: ANSI T1.105 and 106) (Optional) Not Proposed Payload Data Rate or Bandwidth Signaling Type 4 khz Bandwidth Line-Loop Signaling 4 khz Bandwidth Line-Loop Signaling 4 khz Bandwidth Trunk-Loop Signaling (loop and ground start) 4 khz Bandwidth Trunk Wink Start Signaling 4 khz Bandwidth Trunk-E&M Signaling Up to 1.536 Mbps T1 Robbed-Bit Signaling Up to 1.536 Mbps ITU-TSS Q.931 Up to 43.008 Mbps Up to 1.92 Mbps 49.536 Mbps SS7 SS7, T1 Robbed-Bit Signaling SS7, E1 Signaling 11 Electrical: SONET STS-1 (Std: ANSI T1.105 and 106) (Optional) Not Proposed 49.536 Mbps SS7 12 (Non-US) Digital: E3 Channelized (Std: ITU- TSS G.702) Up to 30.72 Mbps SS7, E1 Signaling 13 Digital Line: ISDN BRI S and T Reference Point (Std: ANSI T1.607 and 610) Up to 128 Kbps (2x64 Kbps) ITU-TSS Q.931 Page 152 March 5, 2007
5.1.1.2 Quality of Services (L.34.1.4.6 (d)) A description of the quality of the services with respect to the performance metrics specified in Section C.2 Technical Requirements for each proposed optional service, and other performance metrics used by the offeror. Sprint will meet or exceed all of the stated acceptable quality levels (AQLs) detailed in RFP Section C.2. Availability (POP-to-POP). Sprint will meet the stated KPI of 99.95 percent. XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXX Availability (SDP-to-SDP). Sprint will meet the stated KPI of 99.5 percent for routine circuits and 99.95 percent for critical circuits. Time to Restore. Sprint will meet the time to restore KPI for event requiring dispatch and will meet the time to restore KPI for events not requiring dispatch. Grade of Service. Sprint will meet the GOS. 5.1.1.3 Exceeding the Specified Service Requirements (L.34.1.4.6 (e)) If the offeror proposes to exceed the specified service requirements (e.g., capabilities, features, interfaces), a description of the attributes and value of the proposed service enhancements. Sprint will exceed KPIs and AQLs as described in Section 5.1.1.2 above. 5.1.1.4 Experience Delivering Services (L.34.1.4.6 (f)) A description of the offeror s experience (including major subcontractors) with delivering each proposed optional service. Sprint provided voice services for both FTS2000 and FTS2001. Sprint learned through first hand experience Government expectations from its network provider. Over the years, Sprint has kept the Government on the leading edge of technology through a steady stream of innovations and contract modifications designed to match network capabilities to the evolving needs of the user community. Page 153 March 5, 2007
5.1.1.5 Ensuring Service Quality and Reliability (L.34.1.4.6 (g)) A description of the characteristics and performance of the access arrangements that will connect to the offeror s backbone network(s) to ensure service quality and reliability. A description of how the performance is consistent with industry best practices. Please see Section 4.2.1 for a description on ensuring service quality and reliability. 5.1.1.6 Testing and Verifying Services (L.34.1.4.6 (h)) A description of the offeror s approach to perform verification of individual services delivered under the contract, in particular the testing procedures to verify acceptable performance and Key Performance Indicator (KPI)/Acceptable Quality Level (AQL) compliance. Measuring KPIs For POP-to-POP availability Sprint will measure this performance metric on a monthly basis from the results of the Network Operations report for DMS unavailability. For SDP-to-POP availability Sprint will follow the formula defined in the RFP for Availability. Sprint will track and total all customer-reported outages for an Agency during the past month not caused by the customer. For time to restore with or without dispatch KPI, Sprint will utilize trouble ticket outage information for each incident to determine the time to restore parameter. For the GOS KPI for routine services SDP-to-SDP, Sprint will calculate the GOS for each Agency through the Erlang B methodology and P tables. The calculation will be performed on the total calculated blocked calls. For the GOS KPI for routine POP-to-POP services, Sprint will utilize the internal networks IMT GOS report which details the GOS for calls between Sprint voice switches. For the GOS KPI for critical SDP-to-SDP services, Sprint will calculate the GOS for each Agency through the Erlang B methodology and P tables. The calculation will be performed on the total calculated blocked calls. Page 154 March 5, 2007
For the GOS KPI for critical POP-to-POP services Sprint will utilize the internal networks IMT GOS report which details the GOS for calls between Sprint voice switches. Monitoring KPIs The Sprint network is managed by several management and control centers located in geographically diverse locations throughout the U.S. In addition, there are back-up facilities for each control center. The various centers manage and control the Sprint network as follows: Continually monitor the network to ensure traffic flow is optimal in load and design Respond to unusual traffic conditions by using pre-planned traffic control programs or direct human modifications of routing algorithms Analyze network traffic statistics to determine usage, potential weak spots, and the need for additional equipment and/or facilities Ensure that required translation routing tables are added, changed, or deleted. Capacity Planning Using off-peak routes greatly reduces the chances of a call being blocked by a congested route. Capacity planning of the voice network is achieved by reviewing Dynamic Controlled Routing (DCR) node stats daily for traffic increases, decreases, and overflows. DCR is an automated processor that monitors all Intermachine Trunks (IMTs) and allocates traffic among switch pairs in a manner to meet the changing traffic loads of congested routes. DCR will recommend off-peak trunk pairs to complete traffic from congested routes. Any switch exceeding a Grade of Service (GoS) of four calls blocked per 1,000 callers in an hour will be analyzed for port augmentation. XXXXX Page 155 March 5, 2007
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXX Sprint also collects Call Detail Records (CDRs) and Operational Measurements (OMs) for reporting purposes, and then creates reports to enable internal and external customers to monitor their traffic. If problems are identified, Sprint uses both CDR and OM data to help drill down into the issues in either the network or on a customer trunk. The data helps pinpoint problem locations so that the appropriate groups can be brought together to correct the problem. Traffic Analysis Capacity Planning reviews Nodestat, DCR, Operational Measurement (OM) reports, and ODS Operation Measurements daily to analyze overflowing or congested IMT routes. Since Jan of 2001, Capacity Planning IMT Servicing added 119,265 IMT ports to the DMS-250 network on an average of 127 IMT ports per day to maintain a uniform Grade of Service (GoS) of less then five calls blocked per 1,000 callers. U.S. Voice Network Testing Sprint uses three SOTAS REO-1000 transponders that place calls to LEC 105-type responders in 170 cities, each in a different LATA. The calls are placed daily from Sprint offices in New York, Chicago, and Los Angeles over equal access connections. The test calls encounter the same conditions that the Agencies would encounter on calls to the same areas. The transponders test continuously every day over the Sprint network. Page 156 March 5, 2007
Sprint tests each city randomly 45 times each quarter. A figure of merit is calculated for each test call, based on the far-to-near 1004 Hz loss and C- Message noise measurements of the SOTAS REO-1000 transponder, a model developed at Bell Laboratories. A very high-quality connection will have a loss from 7 to 9 db with a C-Message noise reading of about 12 db, resulting in a figure of merit from 82.7 to 85.6. The higher the figure of merit is the better the connection quality. The SOTAS REO-1000 also indicates the average Call Setup Time (CST) for each city and is accurate to the nearest 0.1 second. The lower the CST, the quicker the line rings on the terminating end. Not all calls result in far-tonear figures. A call may encounter busy, no answer, or fast busy. Calls may also terminate early because of responder or path problems. Because the Sprint connection appraisal system is designed to simulate end-to-end connections, the terminal device is connected to an ordinary two-wire business line. For this reason, XXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXX 5.1.1.7 Ensuring Quality of Time-Sensitive Traffic (L.34.1.4.6 (i)) A description of the approach to ensure the quality of time-sensitive traffic (e.g. voice quality, video quality, video lipsynch) under different traffic patterns and load conditions on the offeror s network. The Sprint Voice offering is traditional circuit-switched service that provides 56/64 Kbps for each voice call. Calls will not contend with other applications for bandwidth as they would in a converged data, voice, and video IP solution. The question of time-sensitive traffic applies to converged IP network circuits, not circuit-switched circuits. Page 157 March 5, 2007
Sprint engineers the voice backbone network to provide a grade of service equal to P.005, which is equal to 1 call per 200 receiving a busy signal. 5.1.1.8 Providing Integrated Access to Customer Application Support Locations (L.34.1.4.6 (j)) A description of the approach for providing integrated access to locations that support customer applications with different performance requirements (e.g., voice, data, and video). To address the capabilities for Integrated Access services, Sprint provides an Agency with an integrated communications platform that takes advantage of changes in technology that eliminates separate networks. An example would be an Agency location that currently has separate access lines to support voice and data services to a location. Sprint provides a channelized T-1 to the location that allows the 24 channels on the T-1 to be separated for voice and data requirements. This could result in Agencies benefiting in lower access costs (see Figure 5.1.1-2). As Agencies are moving to an IP-centric environment for economic reasons, new technologies and capabilities, equipment life cycle limits, strained networks, and the desire to maintain a single converged network continue to drive change. With more fiber available in more locations, optical Figure 5.1.1-2. Integrated Access Integrated access results in additional savings for Agencies. Page 158 March 5, 2007
level connectivity (OC-3, OC-12, etc) is being delivered to more of the larger Agency locations providing some of these locations with all voice, video, and data services delivered over a single connection resulting in true convergence of services. Government Furnished Property (GFP) would have to be compliant and certified to work on the Sprint network to ensure that the equipment does not affect network performance. Sprint has a rigorous certification policy to verify that all equipment connected to the network performs as required so that no customer or network integrity is affected. Sprint supports WLNAA access arrangements as outlined in RFP Section C.2.16.2.1.1.4. 5.1.1.9 Incorporating Future Infrastructure Enhancements and Emerging Services (L.34.1.4.6 (k)) A description of the approach for incorporating into the offeror s network, infrastructure enhancements and emerging services that the offeror believes are likely to become commercially available in the timeframe covered by this acquisition, including a discussion of potential problems and solutions. Sprint has a methodical approach to incorporating infrastructure enhancements and emerging services. The FTS2000 and FTS2001 programs demonstrate our proven capabilities in introducing and managing new and enhanced services driven by Federal Agency needs as they become available. In order to maintain industry leadership, Sprint continuously develops new and enhances existing capabilities and services. Sprint proposes to continue our excellent record of accomplishment of introducing services to the Networx contract. We also propose a Networx Technology Council to customize a Networx technology refresh plan to Government needs and routinely add new and emerging services to the Networx contract. Additional details about the Technology Council are provided in the Technology Plan. Page 159 March 5, 2007
The Sprint Technology Research and Sprint Team Laboratories Development (TR&D) team is responsible Supporting Networx for researching, developing, and delivering Sprint Technical Integration Centers (STICs): STIC labs new and emerging technologies for the are one of several ways that Sprint tests new technologies nationwide network in the form of products, Sprint Solutions Laboratory: features, and functionality. TR&D also Provides a test and verification environment for Government defines the Sprint Network Evolution Plan and other customers (NEP) that defines the overall Sprint XXXXXXXXXXXXXX architecture, and specific Technology XXXXXXXXXXXXX XXXXXXXXXXXXX Evolution Plans (TEPs) that plan the XXXXXXXX XXXXXXX evolution of specific technologies and components of the overall network architecture. Sprint thoroughly tests technologies before implementation to verify effectiveness and mitigate risk. We have several laboratories available to support new and emerging services. Sprint and our team members have several lab facilities to test technologies before deployment, and to develop and verify solutions with the involvement of our Government customers The Technology Development Process (TDP) is an integrated development and implementation process used by the TR&D organization to introduce new technology evolution, products, or services. As shown in Figure 5.1.1-3, the TDP is a comprehensive process that guides ideas from ideation through execution. Once infrastructure enhancements and emerging services are ready for use, we work with the GSA to ensure Federal Agencies are able to take advantage of them through an Additional Offering contract modification. Page 160 March 5, 2007
Figure 5.1.1-3. The Sprint Technology Development Process The Sprint detailed technology development process ensures that infrastructure enhancements and emerging services are developed, tested, and made available to Federal Agencies via the Networx contract. Potential problems associated with infrastructure enhancements are largely addressed by proper planning and customer involvement. XXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXX All technology Sprint has been a leader in upgrades follow a detailed implementation creating advanced wireline and wireless process to mitigate risk. Sprint works closely with capabilities and valueadded mobility and vendor partners to develop and evaluate emerging managed-service solutions. We also built security technology. These well established our SprintLink, Peerless IP relationships allow us to convey requirements to and original ATM networks to meet Government needs. Page 161 March 5, 2007
the vendors directly during their product development process. This provides the vendors with an opportunity to release products that meet or exceed Sprint requirements. Sprint thoroughly evaluates potential technology enhancements within its labs. Once selected, we design and implement enhancements according to detailed plans. If planning cannot address an unforeseen problem, network upgrades use back-off plans to reverse changes and allow operations to return to the baseline configuration. 5.1.1.10 Approach to Network Convergence (L.34.1.4.6 (l)) A description of the approach for network convergence. In particular, describe how the approach ensures service quality over the converged network for data, voice, video, and multimedia. The Sprint approach to convergence is to evolve its network to an accessagnostic, all IP-packet infrastructure as illustrated in Figure 5.1.1-4 with CoS functionality capable of supporting advanced applications and services. The marketplace regards our approach to convergence as industry leading. Being in the unique position of having already merged local, long distance, wireless, and data operating units, Sprint now addresses the challenges that our competitors will be facing in the future. Facilitating convergence is a natural outcome of the integrated target state network described earlier in Section 4.3.2.2.3. Merging data packet switching technology with voice telephony signaling and call-processing intelligence allows us to consolidate traditionally separate long distance voice, IP, and data overlay networks to provide new and differentiated integrated communications services to the Federal Government. The IP networks continue to evolve for greater efficiency, reliability, and security. All traffic is transported, whenever feasible, on an IP packet network. We reduce legacy circuit-switched long distance and local voice traffic by migrating TDM infrastructure to VoIP. We support services such as frame relay and ATM via an IP-enabled multi-service edge platform, allowing the Page 162 March 5, 2007
Figure 5.1.1-4. The Sprint Access-Agnostic, Wireless/Wireline Convergence Strategy Our approach to convergence delivers data, voice, video, and multimedia services over IP core networks designed to provide service quality regardless of location or the access method used. core to focus on the high-performance switching, signaling, and control functions required to meet service class bandwidth and Quality of Service (QoS) requirements. The result is high-performance, efficient IP platforms that enable reduced operating costs, and service interworking potential. Such architecture facilitates Agencies meeting FEA objectives by shifting focus away from specific stove-piped technologies and network transport options to the performance and interoperability objectives met by leveraging a converged, standards-based IP architecture. It is important to note that our approach to convergence transcends the core IP networks; we achieve convergence via an integrated all-ip Page 163 March 5, 2007
architecture that includes access methodologies. This area in particular is one in which Sprint offers considerable value to the Government. Owning a unique mix of assets, Sprint is developing a truly integrated wireless wire-line network. The key to achieving convergence is merging packet switching technology, in this case IP, and signaling and control functions to support data, voice, video, and multimedia needs regardless of whether this information is carried via a wireless or wireline network. Sprint s Networx offering allows Federal Agencies to deploy applications usable regardless of user location or the technology used to access the network. The key benefit is that the Government can focus more time and resources on protecting and delivering services to constituents, consistent with FEA objectives, than supporting the network infrastructure, which Sprint will manage completely. Our Next-Generation Signaling and Control architecture, described earlier in Section 4.3.2, facilitates wireless/wireline convergence. One enabling technology of this architecture plane is the IP Multimedia Subsystem. IMS facilitates, and indeed has been identified by numerous standards bodies such as 3GPP, 3GPP2, and ITU as the prescribed approach by which to build, converged IP-based data, voice, video, and multimedia services. The IMS cornerstones are the use of: 1. SIP to control all sessions (e.g., calls) to easily support IP streaming voice and video services, 2. A Home Subscriber Service (HSS) to store all customer profile and eventually support the convergence service information, and 3. A Policy Distribution Function (PDF), which allows IMS service control to request high QoS connectivity, services from network providers. All three together allow subscribers with qualified profiles to per call request the IP connection QoS necessary to provide service quality. Page 164 March 5, 2007
This approach to service quality across the converged network is consistent with established Sprint network engineering principles. We have always been an advocate of core networks engineered for congestion avoidance, rather than congestion management with feature/functionality and policy enforcement on the edge. As Sprint converges more services onto an IP infrastructure, having networks designed for congestion avoidance will assume greater importance. Our engineering objective is to provide 100 percent packet delivery from network edge to network edge with negligible jitter. We implement mechanisms to ensure QoS at the edge of the network, facing the customer, where the greatest likelihood for contention for bandwidth re-sources is to occur. This method gives Federal Agencies the flexibility to customize the prioritization and usage of their bandwidth to meet their needs. Traffic types identified by Agencies as priority traffic are prioritized as such, whether it is data, voice, video, and multimedia traffic. The flexibility to adjust prioritization, via IMS service control or other available methods, over an efficient network designed for congestion avoidance, allows Federal Agencies to maximize the benefits of our convergence and service quality approach. 5.1.1.11 Supporting and Ensuring Interoperability between IP and PSTN (L.34.1.4.6 (m)) A description of the approach to support and ensure interoperability between Internet Protocol (IP) networks and the Public Switched Telephone Network (PSTN), including the approach to map between IP and PSTN addresses. Sprint supports interoperability between IP networks and the PSTN immediately via our Networx VoIPTS offering, and in the future by leveraging our ongoing Electronic Numbering (ENUM) efforts. Interoperability between IP and the PSTN is critical for any large VoIP deployment to be successful. Sprint knows that this is especially true for Federal Agencies. Our experience with the FTS2000 and 2001 contracts provides visibility into the large volume Page 165 March 5, 2007
of voice traffic handled by the Agencies. As a trusted partner, we also know that many Agencies have wrestled with the VoIP migration business case given the aggressive pricing available through GSA. Agencies will migrate to VoIP on different schedules, and the Government will need to communicate with its constituents easily --especially given the FEA objectives for delivering services to the public in a citizen-centric manner. Therefore, IP-PSTN interoperability is critical today and will be well into the future. The PSTN consists of two primary parts: signaling and transport. For a VoIP call, signaling is used between the caller and called parties to determine if the call can be established. If the two end parties agree to the call, an IP packet flow is set up between the two end points using IP addresses agreed to by the end parties. Session Initiation Protocol (SIP), an IETF standard for VoIP signaling, uses logical addresses (e.g., Governmentparnter@sprint.com) or IP addresses (e.g., 10.20.1.3), while the PSTN uses telephone numbers (e.g., 202-555-1234). The VoIP logical end address traditionally determines the called party IP address by using a DNS server. Today, PSTN to VoIP interworking between PSTN and IP end points relies on a Media Gateway Controller (MGC) for signaling and a Media Gateway (MG) for transport. As a call passes through the MG, voice connections in the form of VoIP flows and DS-0 TDM connections are converted at the Media Gateway. This occurs in conjunction with the conversion of VoIP SIP signaling to and from PSTN SS7 signaling in the MGC. IP addresses to and from PSTN numbers are typically provisioned at a given MGC. Sprint supports interoperability with the PSTN or with Agency User-to- Network Interfaces (UNIs) using the current capabilities of our VoIP service offerings. We provide network-based media gateway solutions for VoIP access to the PSTN, Agency WANs, or Agency TDM networks. By leveraging Page 166 March 5, 2007
a network-based capability, the Government will have interoperability between PSTN and IP endpoints while reducing expenditures resulting from Agency-funded technology upgrades. These gateway solutions support a variety of configurations and signaling protocols. More details on our solution appear in Section 5.2.3, Voice over IP Transport. Sprint also provides a plan for scalable interoperability that will become a standard throughout the telecommunications industry. We plan to deploy a new DNS service called Electronic Numbering (ENUM) over the next couple of years. The primary function of ENUM is to resolve SIP end point addresses using traditional PSTN telephone numbers. Doing so removes the need for MGCs to provision fixed translation databases. ENUM deployments facilitate IP-PSTN interoperability and enable the Sprint Team to meet the needs of our Government customers continually. Our strategy for ENUM is multi-tiered. Consistent with our industry leadership in standards and best practices development described in Sections 4.1.3 and 4.4.3, Sprint is forming an ENUM Tier 1 limited liability corporation (ENUM LLC) with other Inter Exchange Carriers (IXCs) and LECs throughout the industry. The members of ENUM LLC will use the same DNS structure for Tier 1 ENUM services, therefore supporting the interoperability sought by GSA. The LLC has also received the delegation from the Country Code 1 countries (USA, Canada, Mexico, Jamaica, etc.) to operate as their data structure and ENUM service for Tier 1. Tier 1 is a database structure that takes the ENUM number and then points to the Tier 2 ENUM servers. Tier 2 services are where customer data is housed and operated by each provider to serve individual ENUM customers. Sprint is currently planning Tier 2 interfaces and data structures so that we can offer Tier 2 services to Federal Agencies. We will work with GSA so that Networx customers receive Page 167 March 5, 2007
the benefits of our ENUM efforts through a contract modification when commercially available. 5.1.1.12 Approach to IPv4-to-IPv6 Migration (L.34.1.4.6 (n)) A description of the approach for IPv4-to-IPv6 migration. XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 5.1.1.13 Satisfying NS/EP Basic Functional Requirements (L.34.1.4.6 (o)) A description of the offeror s approach to satisfy each NS/EP basic functional requirement listed in Section C.5.2.2.1.1. Table 5.1.1-4 indicates current NS/EP capabilities as related to the 14 functional requirements. Table 5.1.1-4. Voice Services Approach to Meet NS/EP Requirements NS/EP Requirement Sprint Approach 1. Enhanced Priority Treatment As contracted and directed by the NCS, priority for NS/EP Voice and data services voice traffic and low speed data is provided by Sprint s supporting NS/EP missions implementation of GETS and WPS. Use of NS/EP should be provided services is managed and controlled by the NCS. preferential treatment over other traffic. 2. Secure Networks Networks must have protection against corruption of, or unauthorized access to, traffic and control, including expanded encryption techniques and user authentication, as appropriate. Consistent with best commercial practices, Sprint has taken every possible measure to protect physical and proprietary corporate resources from any threat that might impact the reliability/availability of Sprint network services to our customers. These measures extend to our customer services and address threats from both within and external to Sprint. Included are a variety of access, authentication, and authorization measures applicable to both customers and Sprint personnel. With heightened concerns about Security and the Global Economy, Sprint has developed the Multi-Tier Security Profiles (MTSP) initiative. MTSP provides four baseline levels of embedded security, which can be tailored to individual customer needs and security requirements. Sprint MTSP provides all services necessary for the Government to satisfy its worldwide telecommunications and information technology and security requirements. Page 168 March 5, 2007
NS/EP Requirement Sprint Approach 3. Non-Traceability Selected Networx voice VPN services accommodate suppression users must be able to use of automatic number identification (ANI) for selected NS/EP services without risk of users. usage being traced (i.e., without risk of user or location being identified). 4. Restorability Should a service disruption occur, voice and data services must be capable of being reprovisioned, repaired, or restored to required service levels on a priority basis. 5. International Connectivity Voice and data services must provide access to and egress from international carriers. Sprint meets SLAs for reliability and restoration of both voice and data services. Sprint fully complies with the TSP system for priority provisioning (i.e., installation of new circuits), restoration of previously provisioned circuits, and priority level or design change of circuits, including coordination with local access providers. Sprint will fully comply with any future TSP replacement system. Sprint provides significant international voice and data coverage using its own network resources. We have agreements with international carriers around the world for the full scope of Networx required services. Sprint voice services provide access to and egress from international carriers. As a Sprint customer, GSA can be confident that our industry-leading SLAs are fully backed by Sprint and its global partners. 6. Interoperability Voice and Sprint is committed to addressing Networx requirements data services must for interoperability. Interoperability will exist at contract interconnect and interoperate award between GETS and Networx at facilities with with other government or dedicated access to the Sprint network. Sprint will work private facilities, systems, and with the Government to define requirements and networks which will be development necessary to interoperate with other identified after contract networks and systems. award. 7. Mobility The ability of voice and data infrastructure to support transportable, redeployable, or fully mobile voice and data communications (i.e. Personal Communications Service (PCS), cellular, satellite, high frequency (HF) radio). 8. Nationwide Coverage Voice and data services must be readily available to support the national security leadership and inter- and intra- Agency emergency operations, wherever they are located. Sprint is rapidly becoming the foremost vendor of wireless mobility services. With its recently completed merger with Nextel, Sprint is uniquely positioned to offer Networx a variety of wireless and land mobile radio (LMR) solutions that not only satisfy priority calling requirements but also provide FIPs compliant encrypted transmission. Sprint wireline voice, data, and video services are generally accessible throughout the United States through POPs in more than 720 locations. Please see Appendix B and C for Domestic and International POPs. Page 169 March 5, 2007
NS/EP Requirement Sprint Approach 9. Survivability/Endurability The total digital, fiber-optic transmission network has been Voice and data services must designed to ensure network efficiency, exceptional growth be robust to support surviving capacity, and operational survivability. The network has users under a broad range of been designed with a high degree of robustness to ensure circumstances, from the that it can survive traffic surges and specific plant failures widespread damage of a such as cable cuts. It also includes extensive performance natural or manmade disaster monitoring systems and control systems that manage up to and including nuclear problems as they occur. war. In our voice network, the implementation of Dynamically Controlled Routing (DCR) makes every switch in the Sprint network a candidate tandem if direct routes between switches are unavailable or congested.. The bottom line is, as transmission technology advances to higher speeds with better performance, or changes in switching technology improves performance and reliability, as Sprint moves to Next Generation Networks, Networx will move with and benefit from these changes as well. 10. Voice Band Service The service must provide voice band service in support of presidential communications. Sprint has supported presidential communications on both FTS2000 and FTS2001 and GETS. Sprint will continue to support presidential communications on Networx, GETS and WPS. 11. Broadband Service Per the Networx RFP, this requirement is not applicable to VS. 12. Scalable Bandwidth Per the Networx RFP, this requirement is not applicable to VS. 13. Affordability The service must leverage network capabilities to minimize cost (e.g., use of existing infrastructure, commercial offthe-shelf (COTS) technologies, and services). 14. Reliability/Availability Services must perform consistently and precisely according to their design requirements and specifications, and must be usable with high confidence. Sprint provided Networx voice, data, and video services are COTS based on existing Sprint infrastructure and as such, inherently minimize costs to provide the best value possible to Networx customers. The Sprint transport equipment has logic at the site to reverse the flow of traffic and restore service in milliseconds without having to send data to a central processor for analysis and decisions. This survivability gives Sprint greater flexibility for maintenance and maintains high availability. Sprint is continuing to install SONET on the fiber rings in its network leveraging its investment and endorsing its original vision of a 100 percent digital, fiber-optic network with powerful ring architecture. Sprint has deployed 567 OC48 SONET rings and 19 OC192 SONET rings. Additional NS/EP detail appears in Section 4.5.1 of this volume. Page 170 March 5, 2007
5.1.1.14 Protecting SS7 Signaling Systems and Satellite Command Links (L.34.1.4.6 (p)) A description of how the offeror s approach will satisfy the requirements in Section C.5.2.5 for protection of SS7 signaling systems and satellite command links (if employed). Sprint provides physical protection of SS7 links against external intrusion, manufactured and environmental stresses, as described in NCS TIB 87-24 and NCS-TIB 93-9. Specifically, SS7 links operate on fiber optic cables that are either buried a minimum 42 inches below ground or protected in hardened conduit to traverse areas where trenching is not possible. Cable facilities terminate in hardened, secure bunkers normally located well away from heavily populated areas. In fact, many of the features of the Sprint SS7 network meet or exceed the hardening requirements of stress Level 2 as specified in NCS TIB 87-24. In addition, the use of dedicated administrative network connections and terminal equipment accessible only by authorized personnel using access privileges and controls prevents electronic intrusion into the SS7 network. Satellite services provided for Networx are equipped with encrypted command and control links meeting Government requirements unless otherwise directed (per NTISSP-1). This allows selective use in NS/EP applications. 5.1.1.15 Assuring Service in the National Capital Region (L.34.1.4.6 (q)) A description of how the network architecture will satisfy the requirements in Section C.5.2.7 for assured service in the National Capital Region, if applicable. Sprint has provided assured service features within its network since the original FTS2000 contract. Today, Sprint meets the following conditions: Users experience two percent or less blocking for access and one-half percent or less blocking for transport under PSN overload conditions. This assumes an undamaged Sprint network; we understood that there Page 171 March 5, 2007
would be appropriate adjustments in the requirements in areas where damage occurred. XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXX Assured service involves an end-to-end management and design process. Components include customer premises equipment, access and egress arrangements, inter-exchange network, and network management and control. Details on these components, i.e., access, network and egress, which Sprint can control to achieve the stated requirements will be in Part B of our NS/EP Functional Requirements Plan (FRIP) and will constitute the Sprint Assured Service Plan. 5.1.1.16 Meeting Section 508 Provisions (L.34.1.4.6 (r)) A description of the offeror s approach for providing the capabilities needed to meet Section 508 provisions for each of the proposed optional services identified in Section C.6.4. Sprint provides the capabilities for supporting Section 508 requirements related to Electronic Information Technology (EIT) from a technical operations perspective as noted in the ancillary Voluntary Product Accessibility Templates (VPAT) documentation. Sprint strives for compliance by meeting the standards criteria or equivalent facilitation. The VPATs cover all aspects of Sprint product and services capabilities ranging from software to hardware, web information, functional capability, and documentation. The completed supporting VPAT documentation is noted in Volume 1, Appendix A. Page 172 March 5, 2007
5.1.1.17 Impact of Delivery of Optional Services on the Network Architecture (L.34.1.4.6 (s)) A description of how the delivery of any optional services would impact the network architecture (e.g., security, quality and reliability, performance). The Sprint network is a robust service delivery platform using circuitswitched services to support voice. The services proposed will have no impact on the network architecture. This is described in Table 5.1.1-5. Table 5.1.1-5 Voice Services Impact on Network Architecture Network Architecture Component Reasons for No Impact Security Callers are isolated from the command and control functions of the network. The callers are permitted only to traverse the routing paths established by the Agency. Quality and Reliability Quality and reliability will be identical to the Voice Services described in Section 5.1.1. Performance Voice is a core service provided by Sprint commercially. Voice services use circuit switched paths through the Local Exchange Carriers and the Sprint network. Dedicated processors in the DSM-250 network switches and the SS7 network control all routing and call connections. 5.1.1.18 Optimizing the Engineering of Services (L.34.1.4.6 (t)) A description of the offeror s approach for optimizing the engineering of IP-Based and optical services. The voice services offered in this section are traditional circuit switched based services not IP based services. Sprint currently carries a significant percentage of the existing FTS2001 circuit switched voice traffic load on its network and can accommodate additional traffic when the Government transitions to the Networx contract. Page 173 March 5, 2007