Attachment 1 - Statement of Work.pdf

STATEMENT OF WORK

TITLE: Interworking Function

LAB REQUESTING ITEM(S): Communications Technology Laboratory, Public Safety Communications Research (PSCR)

I. BACKGROUND INFORMATION

NIST PSCR has a requirement for one (1) Interworking Function (IWF) with the capability to interconnect commercial P25 LMR systems to LTE mission-critical (MC) servers. The IWF will communicate to the P25 system through the standardized P25 inter-RF subsystem interface (ISSI) and via the interfaces IWF-1, IWF-2 and IWF-3 as defined by the third-generation partnership project (3GPP). The IWF will be a scalable solution (up through network-grade) as a 3GPP compliant module. Through this procurement NIST will obtain one (1) IWF to interconnect the Motorola P25 system owned by PSCR.

The ISSI is an open interface specified by the Telecommunication Industry Association (TIA) as the means to interconnect P25 RF subsystems (RFSS) to provide and extend the communication area. TSB-102.BACC-B provides an overview of ISSI. TIA-102.BACA-B and its addendums define the messages and procedures used on ISSI.

3GPP TS 23.283 describes the architecture to support the interworking between the MC system and the P25 system while TS 29.379 specifies the call control protocols.

The IWF will appear to be a P25 RFSS on the ISSI interface and translate both control messages and payload to the 3GPP side (and vice versa).

II. SCOPE

NIST requires the Contractor to design and develop the Interworking Function. The Contractor may take exception to any of the following requirements as long as an explanation is provided as to why the Contractor would not be compliant with the specification item. The Contractor may also provide separate cost information for items that the Contractor does not believe are necessary for the IWF or that will increase the cost significantly.

The Contractor shall maintain all intellectual property rights to all products developed under this contract.

The Government plans to have the IWF software run on either a PSCR owned Dell PowerEdge 730 server hardware or on hardware supplied by the Contractor. The Contractor shall use whichever hardware is deemed proper by NIST for deployment. The Contractor shall install all software and hardware at the PSCR laboratory in Boulder, Colorado. PSCR will provide space in the laboratory, servers running virtual machines, network connections, VPN connection for Contractor development and debug, ISSI connection from the P25 system, and connections to the MC server.

The Contractor will be permitted to perform development of the IWF while connected to, and making use of, the PSCR equipment intended to work with the IWF.

III. SPECIFICATIONS

A. The Contractor shall deliver one (1) IWF which will enable interoperability between P25

LMR and LTE systems with the following features:

1. Implementation of IWF-1, IWF-2, and IWF-3 interface operation to the 3GPP system per 3GPP release 16 specifications.

2. Implementation of ISSI termination to the P25 system per TIA 102 specifications

(current version as of contract award date).

3. Ability to provide group, private and emergency communication between P25 trunked systems and 3GPP mission-critical systems using voice and data.

4. The IWF shall be provide the controlling role for group calls and private calls. The controlling role serves as the group home, managing the floor and tracking group affiliations.

5. The IWF shall be provide the participating role for group calls and private calls. The participating role serves as the user home, checking user authorizations and forwarding signaling and media between the controlling role and clients.

6. The IWF shall provide a non-controlling role for temporary group calls involving groups from multiple mission-critical push-to-talk (MCPTT) systems. The non-controlling role serves as the controlling role for a constituent group of a regroup and coordinates with the controlling server of the temporary group.

7. The IWF performing the participating role shall serve an originating LMR user.

8. The IWF performing the participating role shall serve a terminating LMR user.

9. The IWF shall provide the participating role and controlling role for the same group session.

10. The IWF shall provide the participating role and non-controlling role for the same group session.

11. The IWF shall provide key management functions for encrypted communications.

12. The IWF shall support all the functional connectivity models described in TS 29.379 section 5.2.

13. The IWF shall provide performing floor control.

14. The IWF shall handle emergency calls, emergency alerts and imminent peril calls.

15. The IWF shall support transcoding between AMBE on the P25 interface and AMR- WB on the 3GPP interface.

16. The IWF shall support MCData short data service.

17. The IWF shall provide a security gateway when transcoding and encrypting is required.

18. The IWF representing an LMR user shall support simultaneous interworked calls for the same LMR user.

19. The IWF shall provide the location of the current talking user.

20. The IWF shall support information flows for LMR security transport and LMR key management messages.

21. The IWF shall support 250 private calls and 500 group calls simultaneously.

22. The IWF shall support 10000 active 3gpp clients and 10000 active P25 clients simultaneously.

B. Support

1. Support shall be provided for a minimum of five (5) years.

2. Support shall include training, debugging, and troubleshooting.

3. Support shall include assistance with integration with 3GPP compliant components and P25 compliant components.

4. Telephone and email support shall be provided including points-of-contacts.

5. Support shall be available during PSCR business hours. See below for details.

6. All software updates and releases shall be provided for the duration of the contract.

IV. DELIVERY

Final software submission to support all specifications shall be delivered for acceptance no later than one (1) year after receipt of order (ARO). Earlier software submissions are encouraged.

Following acceptance, software licenses and support will be delivered as shown in Section VII, Deliverables, below.

V. PERFORMANCE REQUIREMENT

Through inspection and basic tests, PSCR personnel will verify that the software performs as expected prior to acceptance and final payment.

VI. GENERAL INFORMATION

Media Inquiries: The Contractor employee shall not respond to any media inquiries. Any inquiries from the media shall be immediately relayed to the TPOC, COR, and/or CO. There shall be no interviews, comments, or any other response without the knowledge and approval of the NIST Director.

NIST Business Hours: Normal business is conducted between 8:30am and 5:00pm MST, Monday through Friday except Federal Holidays.

VII. DELIVERABLES

The Contractor shall deliver an IWF with the following components:

Qty Item Due/POP

1 Interworking Function One (1) year ARO

1 Software License and Support Year 1 Acceptance plus one (1) year

1 Software License and Support Year 2 Expiration of year 1 plus one (1) year

1 Software License and Support Year 3 Expiration of year 2 plus one (1) year

1 Software License and Support Year 4 Expiration of year 3 plus one (1) year

1 Software License and Support Year 5 Expiration of year 4 plus one (1) year

B. Support