APCS SIR Sect L Att L.8 Amend 3.xlsx
XLSX spreadsheet 887 KB Posted
- Attached to
- National Airspace System (NAS) A/G Protocol Converter (APC) System Federal contract opportunity
- Solicitation number
- 693KA8-22-R-00004
View the file
Other files for this federal contract opportunity
Show all 50
National Airspace System (NAS) A/G Protocol Converter (APC) System has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
J.1.1
| Instructions: Column P must be completed for all requirements. Column O must be completed for all requirements marked YES in Column P. Column Q must be completed for all requirements marked YES in Column P and highlighted in yellow. | |||||||||||||||||
| REQ. ID | REQ. Document | SPEC. PAR. #. | SPEC. PAR. TITLE | DESCRIPTION OF REQUIREMENT | REQUIREMENT TYPE | VERIFICATION METHOD (VM) | CONOPS | TEST APPROACH | VERIFICATION DOCUMENT(S) | MET AT CONTRACT AWARD (Yes/No)? | ESTIMATED VERIFICATION TIME (hh:mm) | ||||||
| iFAT | FAT | System | SAT | PAT | Post-ISD | ||||||||||||
| J.1.1 | 3.1.a | Functional Requirements | The APC System must support implementation of Analog Transport Preplanned Engineering Change, as defined in section 1.1, without any impact to ongoing ATC operations on the APC System. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.b | Functional Requirements | The APC System must support implementation of LLR-APC Preplanned Engineering Change, as defined in section 1.1, without any impact to ongoing ATC operations on the APC System. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.c | Functional Requirements | The APC System must support implementation of IPv6 Preplanned Engineering Change, as defined in section 1.1, without any impact to ongoing ATC operations on the APC System. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.a | VoIP VCS Application (Local Legacy Radios) | The LLR-APC must translate between ED-137 VoIP interface and analog interface (voice and signaling) of legacy local radios. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.b | VoIP VCS Application (Local Legacy Radios) | The LLR-APC must meet the requirements for interfacing with legacy local radios in accordance with section 3.2.1 of the APC to Analog Radio Control Systems Interface Requirements Document (IRD). | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.c | VoIP VCS Application (Local Legacy Radios) | The LLR-APC must meet the requirements for interfacing with VoIP VCSs in accordance with ED-137C, Volume 1 per Clarification Matrix in Section 7 of this specification. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.d | VoIP VCS Application (Local Legacy Radios) | The LLR-APC must provide controls to limit the concurrent VoIP VCS SIP sessions allowed at the Network interface from one to a minimum of twelve. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.e | VoIP VCS Application (Local Legacy Radios) | The LLR-APC must provide access controls to designate which VoIP VCSs can establish SIP sessions with the LLR-APC. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.1.1.a | Push-to-Talk (PTT) | The LLR-APC must provide, upon reception of ED-137 message for PTT Main TX, a PTT signal to local main transmitter. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.1.1.b | Push-to-Talk (PTT) | The LLR-APC must internally generate ED-137 message for PTT confirmation for local main transmitter. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.1.1.c | Push-to-Talk (PTT) | The LLR-APC must provide, upon reception of ED-137 message for PTT Standby TX, a PTT signal to local standby transmitter. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.1.1.d | Push-to-Talk (PTT) | The LLR-APC must internally generate ED-137 message for PTT confirmation for local standby transmitter. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.1.1.e | Push-to-Talk (PTT) | The LLR-APC must provide, upon reception of ED-137 message for PTT Release Main TX, a PTT Release signal to local main transmitter. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.1.1.f | Push-to-Talk (PTT) | The LLR-APC must internally generate ED-137 message for PTT Release confirmation for local main transmitter. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.1.1.g | Push-to-Talk (PTT) | The LLR-APC must provide, upon reception of ED-137 message for PTT Release Standby TX, a PTT Release signal to local standby transmitter. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.1.1.h | Push-to-Talk (PTT) | The LLR-APC must internally generate ED-137 message for PTT Release confirmation for local standby transmitter. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.1.2.a | Main / Standby Selection | The LLR-APC must, upon reception of ED-137 message for main transmitter selection, provide voice and signaling for local main transmitter selection. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.1.2.b | Main / Standby Selection | The LLR-APC must internally generate local main transmitter confirmation message (ED-137). | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.1.2.c | Main / Standby Selection | The LLR-APC must, upon reception of ED-137 message for standby transmitter selection, provide voice and signaling for local standby transmitter selection. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.1.2.d | Main / Standby Selection | The LLR-APC must internally generate local standby transmitter confirmation message (ED-137). | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.1.2.e | Main / Standby Selection | The LLR-APC must, upon reception of ED-137 message for main receiver selection, provide voice and signaling for local main receiver selection. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.1.2.f | Main / Standby Selection | The LLR-APC must internally generate local main receiver confirmation message (ED-137). | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.1.2.g | Main / Standby Selection | The LLR-APC must, upon reception of ED-137 message for standby receiver selection, provide voice and signaling for local standby receiver selection. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.1.2.h | Main / Standby Selection | The LLR-APC must internally generate local standby receiver confirmation message (ED-137). | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.1.3.a | Squelch Break (SQB) | The LLR-APC must, when available, accept SQB signal from local main receiver and provide ED-137 message for Main RX SQB. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.1.3.b | Squelch Break (SQB) | The LLR-APC must, when available, accept SQB signal from local standby receiver and provide ED-137 message for Standby RX SQB. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.1.3.c | Squelch Break (SQB) | The LLR-APC must provide the option to internally generate SQB signals from selected receiver. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.1.3.d | Squelch Break (SQB) | The LLR-APC must utilize VOX circuits described in section 3.2.1.10 to internally generate SQB signaling. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.2.a | LLR-APC Radio Control Access to Local Legacy Radios | The LLR-APC must accept radio control from up to 6 VoIP VCS control sites. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.2.b | LLR-APC Radio Control Access to Local Legacy Radios | The LLR-APC must provide radio control PTT preemption of the lower and equal priority control sites for up to six VoIP VCSs. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.2.c | LLR-APC Radio Control Access to Local Legacy Radios | The LLR-APC must, in the event of a loss of communications with one or more control sites, maintain communications with remaining operational control sites. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.2.1.a | Non-Priority Mode | The LLR-APC must, when control facilities have equal priority, provide a transmit voice path and PTT confirmation to that facility from which the PTT arrives first. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.2.1.b | Non-Priority Mode | The LLR-APC must, when control facilities have equal priority, only allow one facility at a time to have control of the radios; subsequently, lockout the remaining control facilities, i.e., block the voice transmit path, PTT/PTT release, and M/S transmitter/receiver select capabilities of the remaining control facilities. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.2.1.c | Non-Priority Mode | The LLR-APC must, when in “non-priority mode”, provide receive voice path continuously to all the control facilities. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.2.1.d | Non-Priority Mode | The LLR-APC must, when in “non-priority mode” and upon release of PTT by the control facility that issued the PTT in progress, transmit a PTT release confirmation message to that control facility and terminate the lockout condition for the other control facilities. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.2.1.e | Non-Priority Mode | The LLR-APC must, when in “non-priority mode” and upon release of PTT by the control facility that issued the PTT in progress, permit any previously blocked control facility, attempting to PTT, to acquire transmitter(s) without requiring the facility to release and reactivate PTT. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.2.2.a | Prioritized Mode | The LLR-APC must arbitrate radio access permissions to all the connected control facilities based on their PTT priority levels. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.2.2.b | Prioritized Mode | The LLR-APC must, in an ED-137 multi-level PTT priority scheme (i.e., Test, Normal, Priority, and Emergency), permit the higher PTT priority facility to override the lower PTT priority control facility with respect to communicating on the frequency to which those control facilities have access. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.2.2.c | Prioritized Mode | The LLR-APC must provide a transmit voice path and PTT confirmation to the controlling facility when a controller at that facility asserts PTT. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.2.2.d | Prioritized Mode | The LLR-APC must, when PTT is active at a lower priority facility and a PTT signal is received from a higher priority facility, release the lower priority facility’s PTT control and lockout that facility while PTT is active from the higher priority facility. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.2.2.e | Prioritized Mode | The LLR-APC must, when in “prioritized mode”, provide receive voice path continuously to all the control facilities. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.2.2.f | Prioritized Mode | The LLR-APC must, when in “prioritized mode” and upon release of PTT by the control facility that issued the PTT in progress, transmit a PTT release confirmation message to that control facility and terminate the lockout condition for the other control facilities. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.1.2.2.g | Prioritized Mode | The LLR-APC must, when in “prioritized mode” and upon release of PTT by the control facility that issued the PTT in progress, permit any previously blocked control facility, attempting to PTT, to acquire transmitter(s) without requiring the facility to release and reactivate PTT. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.2.a | Legacy VSBP Application (Local IP Radios) | The LLR-APC must translate between VSBP analog interface (voice and signaling) and ED-137 VoIP interface of IP local radios. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.2.b | Legacy VSBP Application (Local IP Radios) | The LLR-APC must meet the requirements for interfacing with VSBP in accordance with section 3.2.2 of the APC to Analog Radio Control Systems Interface Requirements Document (IRD). | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.2.c | Legacy VSBP Application (Local IP Radios) | The LLR-APC must meet the requirements for interfacing with VoIP radios in accordance with ED-137C, Volume 1 per Clarification Matrix in Section 7 of this specification. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.2.1.1.a | Push-to-Talk (PTT) | The LLR-APC must translate PTT signal received from the VSBP and provide associated PTT Main TX messages (ED-137) to the LLR-APC VoIP Interface. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.2.1.1.b | Push-to-Talk (PTT) | The LLR-APC must translate PTT Release signal received from the VSBP and provide associated PTT Release Main TX messages (ED-137) to the LLR-APC VoIP Interface | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.2.1.2.a | Main Radio Selection | The LLR-APC must translate Main transmitter select signal received from the VSBP and provide the associated Main transmitter selection messages (ED-137) to the LLR-APC VoIP Interface. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.1.2.1.2.b | Main Radio Selection | The LLR-APC must translate Main receiver select signal received from the VSBP and provide the associated Main receiver selection messages (ED-137) to the LLR-APC VoIP Interface. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.a | L-APC Functions | The L-APC must translate between analog interfaces (voice and signaling) of Legacy VCS and analog protocol to R-APC. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.b | L-APC Functions | The L-APC must translate between VoIP VCS interface (ED-137) and analog protocol to R-APC. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.c | L-APC Functions | The L-APC must translate between analog interfaces (voice and signaling) of Legacy VCS and VoIP interface (ED-137). | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.2.d | L-APC Functions | The L-APC must meet the requirements for interfacing with the Legacy VCSs in accordance with sections 3.2.3, 3.2.4, 3.2.5, 3.2.6 and 3.2.7 of the APC to Analog Radio Control Systems IRD. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.2.e | L-APC Functions | The L-APC must meet the requirements for interfacing with VoIP VCSs in accordance with ED-137C, Volume 1 per Clarification Matrix in Section 7 of this specification. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.f | L-APC Functions | The L-APC must meet the requirements for interfacing with R-APC VoIP port in accordance with ED-137C, Volume 1 per Clarification Matrix in Section 7 of this specification. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.2.g | L-APC Functions | The L-APC must provide controls to limit the concurrent VoIP VCS SIP sessions allowed at the L-APC network interface from one to a minimum of twelve. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.h | L-APC Functions | The L-APC must provide access controls to designate which VoIP VCSs can establish SIP sessions with the L-APC. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.i | L-APC Functions | The L-APC must, for separate Main/Standby radio interfaces to a local legacy VCS (Terminal ATC Facilities), preclude switching the M/S radio interfaces to match the R-APC radio selection of M/S radios when another control site (L-APC or VoIP VCS) causes the selection to change at the R-APC. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.2.j | L-APC Functions | The L-APC must, when it supports Back-Up Emergency Communications (BUEC), utilize ED-137 protocol to notify connected VoIP VCSs whenever the L-APC BUEC resource is selected. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.k | L-APC Functions | The L-APC must provide an option to block F2 audio if both F1 and F2 PTT are active. | ||||||||||||||
| Note: This feature will prevent unwanted uplink audio distortion if F1 and F2 uplink audio are the same and are fed by two separate interfaces from a Legacy VCS. | Functional Requirements | ||||||||||||||||
| J.1.1 | 3.1.2.1.a | L-APC Analog Protocol Functions | The L-APC must support an analog protocol for interfacing with the R-APC. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.b | L-APC Analog Protocol Functions | The L-APC must provide an interface (channel) to the R-APC that supports the capability to transmit and receive voice and radio control signals for up to two A/G frequencies over a single four-wire voice grade transmission path. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.c | L-APC Analog Protocol Functions | The L-APC must permit control over any of the two analog channel frequencies one at a time. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.d | L-APC Analog Protocol Functions | The L-APC must permit control of the two analog channel frequencies simultaneously. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.e | L-APC Analog Protocol Functions | The L-APC must provide monitoring, maintenance, and configuration of the R-APC over the same single four-wire voice grade interface used for voice and radio control signals. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.f | L-APC Analog Protocol Functions | The L-APC must permit communication on both frequencies (F1 and F2) simultaneously with audio summing for each analog channel. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.g | L-APC Analog Protocol Functions | The L-APC must meet the requirements for interfacing with the R-APC in accordance with section 3.2.2 of the APC to Analog Radio Control Systems IRD. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.h | L-APC Analog Protocol Functions | The L-APC must provide three pass-through RS-232 ports per section 3.2.2.2 of the APC to Analog Radio Control Systems IRD to support the transport of remote monitoring and control data. Note: The remote monitoring and control data is external of the APC System and the RS-232 pass-through function is only provided when Analog Protocol is utilized between the L-APC and R-APC. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.1.a | L-APC Analog Protocol Operational Configurations | The L-APC must, as shown in Figure 3-3, support the APC “Separated TX and RX Configuration” (analog protocol) in which the L-APC communicates with two separate R-APCs. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.1.b | L-APC Analog Protocol Operational Configurations | The L-APC must, as shown in Figure 3-3, support the APC option for switched backup trunks for each of the two active trunks to the two R-APCs utilized in the “Separated TX and RX Configuration” (analog protocol). | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.1.c | L-APC Analog Protocol Operational Configurations | The L-APC must, as shown in Figure 3-3, support the APC “Primary and Backup Configuration” (analog protocol) in which the L-APC utilizes a Primary and Backup trunk to communicate with a single R-APC. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.1.d | L-APC Analog Protocol Operational Configurations | The L-APC must support the APC option to automatically or manually switch between primary and hot backup trunk communications to the R-APC in the “Primary and Backup Configuration” (analog protocol). | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.1.e | L-APC Analog Protocol Operational Configurations | The L-APC must, for the “Primary and Backup Configuration” (analog protocol), maintain a hot backup trunk with audio only being placed on the active trunk. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.1.f | L-APC Analog Protocol Operational Configurations | The L-APC must support the APC option to disable the backup trunk interface in the APC “Primary and Backup Configuration” (analog protocol). | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.1.g | L-APC Analog Protocol Operational Configurations | The L-APC must, as shown in Figure 3-3, support the APC “Dual Control Configuration” (analog protocol) in which two separate control sites (L-APCs) communicate with the same R-APC. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.1.h | L-APC Analog Protocol Operational Configurations | The L-APC must, as shown in Figure 3-3, support the APC option for a switched backup trunk for the active trunk to the R-APC utilized in the “Dual Control Configuration” (analog protocol). | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.1.i | L-APC Analog Protocol Operational Configurations | The L-APC must, as shown in Figure 3-3, be configurable to support two active and two back-up four-wire trunk interfaces to the R-APC for analog protocol operational configurations. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.1.j | L-APC Analog Protocol Operational Configurations | The L-APC must preclude automatically switching to a failed trunk in a “Primary / Backup Configuration” (analog protocol). | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.1.k | L-APC Analog Protocol Operational Configurations | The L-APC must preclude automatically switching to a looped trunk in a “Primary and Backup Configuration” (analog protocol). | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.1.l | L-APC Analog Protocol Operational Configurations | The L-APC must, in the APC "Primary and Backup Configuration"(analog protocol), prevent TX and RX Main/Standby selection on the frequency of any actively keyed transmitters. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.1.m | L-APC Analog Protocol Operational Configurations | The L-APC must, in the APC “Separated TX and RX Configuration” (analog protocol), prevent TX and RX Main/Standby selection on the frequency of any actively keyed transmitters. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.2.a | L-APC Recovery from Analog Communications Path Failure | The L-APC must detect communication path failures on primary and backup analog communication paths to the R-APC (if a backup path is available). | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.2.b | L-APC Recovery from Analog Communications Path Failure | The L-APC must, in the event of analog communication path failures to the R-APC, automatically re-establish communications over an alternate analog communications path when available, in less than or equal to six seconds. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.2.c | L-APC Recovery from Analog Communications Path Failure | The L-APC must provide the option to manually switch between analog communication paths to the R-APC. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.2.d | L-APC Recovery from Analog Communications Path Failure | The L-APC must adopt the operator-selected state in effect prior to analog communication path failure to the R-APC, in less than or equal to three seconds, following the re-establishment of communications without operator intervention. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.2.e | L-APC Recovery from Analog Communications Path Failure | The L-APC must, in the case of analog communication path interruption with the R-APC exceeding three seconds, release all confirmation signals. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.2.f | L-APC Recovery from Analog Communications Path Failure | The L-APC must, if no alternate analog communication path has been configured to the R-APC, prohibit either automatic or manual switching to a non-existing transmission path. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.2.g | L-APC Recovery from Analog Communications Path Failure | The L-APC must, in the event of analog communication path failure to the R-APC adopt a timer of less than 6 seconds before attempting to switch to another path, if after the first attempt the L-APC fails to “lock” to the R- APC. Note: The L-APC timer will need to be configured as necessary (different than R-APC) to ensure the ability to enter a locked state. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.2.h | L-APC Recovery from Analog Communications Path Failure | The L-APC must, in the event of analog communication path failures to the R-APC, automatically re-establish communications over the same communications path upon availability, in less than or equal to 6 seconds, when no alternate communications path is provided. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.2.i | L-APC Recovery from Analog Communications Path Failure | The L-APC must, for an analog transmission path interruption with the R-APC exceeding three seconds, provide an option to terminate all SIP sessions between the L-APC and all VoIP VCSs, until the APC analog transmission path is restored. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.3.a | L-APC Analog Protocol Encoding and Decoding of Radio Control and Voice Signals | The L-APC must encode and decode data messages to and from the R-APC over a single four-wire voice grade transmission path. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.3.b | L-APC Analog Protocol Encoding and Decoding of Radio Control and Voice Signals | The L-APC must verify all analog protocol control messages to the R-APC with transmitted error check sequence bits to ensure command integrity. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.3.c | L-APC Analog Protocol Encoding and Decoding of Radio Control and Voice Signals | The L-APC must combine voice and data for simultaneous transmission to the R-APC over a single four-wire voice grade transmission path. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.3.d | L-APC Analog Protocol Encoding and Decoding of Radio Control and Voice Signals | The L-APC must transmit and receive analog protocol data messages to and from the R-APC using modem (modulator/demodulator) operating in the 2500 to 3000 Hz frequency band. Note: This is what the legacy RCE currently supports and it may not be the final requirement for the APC. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.3.e | L-APC Analog Protocol Encoding and Decoding of Radio Control and Voice Signals | The L-APC must low pass filter voice signals and transmit them to the R-APC in the 300 to 2500 Hz frequency band. Note: This is what the legacy RCE currently supports and it may not be the final requirement for the APC. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.a | L-APC Radio Control Functions (Analog Protocol) | The L-APC must, per section 3.1.2.1.4.1, encode analog protocol for the Legacy VCS radio control signals defined in section 3.2.4 (Voltage Interface) of the APC to Analog Radio Control Systems IRD for up to two A/G frequencies associated with an APC channel and then transmit them to the R-APC. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.b | L-APC Radio Control Functions (Analog Protocol) | The L-APC must, per section 3.1.2.1.4.1, decode analog protocol for the radio confirmation signals received from the R-APC for up to two A/G frequencies associated with an APC channel and provide them to the Legacy VCS as confirmation signals defined in section 3.2.4 (Voltage Interface) of the APC to Analog Radio Control Systems IRD. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.c | L-APC Radio Control Functions (Analog Protocol) | The L-APC must, per section 3.1.2.1.4.1, encode analog protocol for the Legacy VCS radio control signals defined in section 3.2.5 (Contact Closure Interface) of the APC to Analog Radio Control Systems IRD for up to two A/G frequencies associated with an APC channel and then transmit them to the R-APC. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.d | L-APC Radio Control Functions (Analog Protocol) | The L-APC must, per section 3.1.2.1.4.1, decode analog protocol for the radio confirmation signals received from the R-APC for up to two A/G frequencies associated with an APC channel and provide them to the Legacy VCS as confirmation signals defined in section 3.2.5 (Contact Closure Interface) of the APC to Analog Radio Control Systems IRD. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.e | L-APC Radio Control Functions (Analog Protocol) | The L-APC must, per section 3.1.2.1.4.1, encode analog protocol for the Legacy VCS PTT/PTT Release signal as defined in section 3.2.6 (BUEC Interface) of the APC to Analog Radio Control Systems IRD for A/G frequency associated with an APC channel and then transmit it to the R-APC. Note: All other BUEC signals defined in section 3.2.6 of the APC to Analog Radio Control Systems IRD are only utilized at the Legacy VCS/ L-APC interface. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.f | L-APC Radio Control Functions (Analog Protocol) | The L-APC must, per section 3.1.2.1.4.1, encode analog protocol for the VoIP VCS radio control messages defined in ED-137C, Volume 1 for up to two A/G frequencies associated with an APC channel and then transmit them to the R-APC. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.g | L-APC Radio Control Functions (Analog Protocol) | The L-APC must, per section 3.1.2.1.4.1, decode analog protocol for the confirmation signals received from the R-APC for up to two frequencies associated with an APC channel and provide them to the VoIP VCS as radio confirmation messages defined in ED-137C, Volume 1. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.1.1.a | Push-to Talk (PTT) | The L-APC must apply analog protocol encoding for up to two independent PTT signals (F1 and F2) received from the Legacy VCS and transmit them over the four-wire voice grade transmission path to the R-APC. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.1.1.b | Push-to Talk (PTT) | The L-APC must apply analog protocol encoding for up to two independent PTTs received from the VoIP VCS message (ED-137) and transmit them over the four-wire voice grade transmission path to the R-APC. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.1.1.c | Push-to Talk (PTT) | The L-APC must decode analog protocol for up to two independent PTT confirmation signals received from the R-APC over the four-wire voice grade transmission path and provide associated PTT confirmation signals to the Legacy VCS. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.1.1.d | Push-to Talk (PTT) | The L-APC must decode analog protocol for up to two independent PTT confirmation signals received from the R-APC over the four-wire voice grade transmission path and provide associated PTT confirmations in a message (ED-137) to the VoIP VCS. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.1.1.e | Push-to Talk (PTT) | The L-APC must apply analog protocol encoding for up to two independent PTT Release signals received from the Legacy VCS and transmit them over the four-wire voice grade transmission path to the R-APC. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.1.1.f | Push-to Talk (PTT) | The L-APC must apply analog protocol encoding for up to two independent PTT Releases received from the VoIP VCS message (ED-137) and transmit them over the four-wire voice grade transmission path to the R-APC. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.1.1.g | Push-to Talk (PTT) | The L-APC must decode analog protocol for up to two independent PTT Release confirmation signals received from the R-APC over the four-wire voice grade transmission path and provide associated PTT Release confirmation signals to the Legacy VCS. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.1.1.h | Push-to Talk (PTT) | The L-APC must decode analog protocol for up to two independent PTT Release confirmation signals received from the R-APC over the four-wire voice grade transmission path and provide associated PTT Release confirmations in a message (ED-137) to the VoIP VCS. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.1.2.a | Main / Standby Radio Selection | The L-APC must apply analog protocol encoding for up to two independent M/S transmitter select signals received from the Legacy VCS and transmit them over the four-wire voice grade transmission path to the R-APC. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.1.2.b | Main / Standby Radio Selection | The L-APC must apply analog protocol encoding for up to two independent M/S transmitter select commands received from the VoIP VCS message (ED-137) and transmit them over the four-wire voice grade transmission path to the R-APC. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.1.2.c | Main / Standby Radio Selection | The L-APC must decode analog protocol for up to two independent M/S transmitter select confirmation signals received from the R-APC over the four-wire voice grade transmission path and provide associated M/S transmitter select confirmations to both the Legacy VCS and up to six VoIP VCSs. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.1.2.d | Main / Standby Radio Selection | The L-APC must apply analog protocol encoding for up to two independent M/S receiver select signals received from the Legacy VCS and transmit them over the four-wire voice grade transmission path to the R-APC. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.1.2.e | Main / Standby Radio Selection | The L-APC must apply analog protocol encoding for up to two independent M/S receiver select commands received from the VoIP VCS message (ED-137) and transmit them over the four-wire voice grade transmission path to the R-APC. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.1.2.f | Main / Standby Radio Selection | The L-APC must decode analog protocol for up to two independent M/S receiver select confirmation signals received from the R-APC over the four-wire voice grade transmission path and provide associated M/S receiver select confirmations to both the Legacy VCS and up to six VoIP VCSs. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.1.3.a | Remote Receiver Mute | The L-APC must apply analog protocol encoding for up to two independent receiver mute signals received from the Legacy VCS and transmit them over the four-wire voice grade transmission path to the R-APC. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.1.3.b | Remote Receiver Mute | The L-APC must apply analog protocol encoding for up to two independent receiver mute commands received from the VoIP VCS message (ED-137) and transmit them over the four-wire voice grade transmission path to the R-APC. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.1.3.c | Remote Receiver Mute | The L-APC must decode analog protocol for up to two independent receiver mute confirmation signals received from the R-APC over the four-wire voice grade transmission path and provide associated receiver mute confirmations to the Legacy VCS and up to six VoIP VCSs. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.1.3.d | Remote Receiver Mute | The L-APC must apply analog protocol encoding for up to two independent receiver unmute signals received from the Legacy VCS and then transmit them over the four-wire voice grade transmission path to the R-APC. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.1.3.e | Remote Receiver Mute | The L-APC must apply analog protocol encoding for up to two independent receiver unmute commands received from the VoIP VCS message (ED-137) and transmit them over the four-wire voice grade transmission path to the R-APC. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.1.3.f | Remote Receiver Mute | The L-APC must decode analog protocol for up to two independent receiver unmute confirmation signals received from the R-APC over the four-wire voice grade transmission path and provide associated receiver unmute confirmations to both the Legacy VCS and up to six VoIP VCSs. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.1.3.g | Remote Receiver Mute | The L-APC must provide the option for muting the APC analog channel receive path during active PTT. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.1.4.a | Squelch Break (SQB) | The L-APC must decode analog protocol for up to two independent SQB signals received from the R-APC over the four-wire voice grade transmission path and provide associated SQB indications to both the Legacy VCS and up to six VoIP VCSs. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.1.4.b | Squelch Break (SQB) | The L-APC must provide the option to internally generate SQB signal and provide associated SQB indications in a message (ED-137) to the VoIP VCS. Note: This option allows for the L-APC to locally generate SQB signal, versus waiting for delayed, independent SQB signals from R-APC via the analog protocol. The delay in receiving SQB signals from R-APC, via the analog protocol, may result in voice clipping, due to ED-137 not passing audio to VoIP VCS until arrival of SQB signal from R-APC. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.1.4.c | Squelch Break (SQB) | The L-APC must utilize VOX circuits described in section 3.2.1.10 to internally generate SQB signaling. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.1.4.1.5.a | Automatic Gain Control (AGC) | The L-APC must decode analog protocol for up to two independent AGC signals received from the R-APC over the four-wire voice grade transmission path and provide associated AGC values in a Signal Quality Information (SQI) message (ED-137) to the VoIP VCS. Note: Legacy VCS does not utilize AGC voltage, but VoIP VCS could use it for Best Signal Selection (BSS). | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.2.a | L-APC VoIP Functions for Legacy VCS | The L-APC must support a separated TX and RX configuration (IP Transport) in which the L-APC communicates with two separate R-APCs, where one R-APC supports transmitters, and another R-APC supports receivers. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.2.2.1.a | L-APC Radio Control Functions (VoIP) | The L-APC must, per section 3.1.2.2.1.1, translate the Legacy VCS radio control signals defined in section 3.2.4 (Voltage Interface) of the APC to Analog Radio Control Systems IRD and provide associated command in a message (ED-137) to the L-APC VoIP Interface. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.2.2.1.b | L-APC Radio Control Functions (VoIP) | The L-APC must, per section 3.1.2.2.1.1, translate the radio confirmation messages (ED-137) received from the L-APC VoIP Interface and provide them to the Legacy VCS as confirmation signals defined in section 3.2.4 (Voltage Interface) of the APC to Analog Radio Control Systems IRD. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.2.2.1.c | L-APC Radio Control Functions (VoIP) | The L-APC must, per section 3.1.2.2.1.1, translate the Legacy VCS radio control signals defined in section 3.2.5 (Contact Closure Interface) of the APC to Analog Radio Control Systems IRD and provide associated command in a message (ED-137) to the L-APC VoIP Interface. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.2.2.1.d | L-APC Radio Control Functions (VoIP) | The L-APC must, per section 3.1.2.2.1.1, translate the radio confirmation messages (ED-137) received from the L-APC VoIP Interface and provide them to the Legacy VCS as confirmation signals defined in section 3.2.5 (Contact Closure Interface) of the APC to Analog Radio Control Systems IRD. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.2.2.1.e | L-APC Radio Control Functions (VoIP) | The L-APC must, per section 3.1.2.2.1.1.1, translate the Legacy VCS PTT/PTT Release signal defined in section 3.2.6 (BUEC Interface) of the APC to Analog Radio Control Systems IRD and provide associated command in a message (ED-137) to the L-APC VoIP Interface. Note: All other BUEC signals defined in section 3.2.6 of the APC to Analog Radio Control Systems IRD are only utilized at the Legacy VCS/ L-APC interface. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.2.2.1.1.1.a | Push-to-Talk (PTT) | The L-APC must translate up to two independent PTT signals (F1 and F2) received from the Legacy VCS and provide associated PTTs in a message (ED-137) to the L-APC VoIP Interface. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.2.2.1.1.1.b | Push-to-Talk (PTT) | The L-APC must translate up to two independent PTT confirmations in a message (ED-137) received from the L-APC VoIP Interface and provide associated PTT confirmation signals to the Legacy VCS. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.2.2.1.1.1.c | Push-to-Talk (PTT) | The L-APC must translate up to two independent PTT Release signals (F1 and F2) received from the Legacy VCS and provide associated PTT Releases in a message (ED-137) to the L-APC VoIP Interface. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.2.2.1.1.1.d | Push-to-Talk (PTT) | The L-APC must translate up to two independent PTT Release confirmations in a message (ED-137) received from the L-APC VoIP Interface and provide associated PTT Release confirmation signals to the Legacy VCS. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.2.2.1.1.2.a | Main / Standby Radio Selection | The L-APC must translate up to two independent M/S transmitter select signals received from the Legacy VCS and provide the associated M/S transmitter selection in a message (ED-137) to the L-APC VoIP Interface. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.2.2.1.1.2.b | Main / Standby Radio Selection | The L-APC must translate up to two independent M/S transmitter confirmations in a message (ED-137) received from the L-APC VoIP Interface and provide associated M/S transmitter confirmation signals to the Legacy VCS. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.2.2.1.1.2.c | Main / Standby Radio Selection | The L-APC must translate up to two independent M/S receiver select signals received from the Legacy VCS and provide the associated M/S receiver selection in a message (ED-137) to the L-APC VoIP Interface. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.2.2.1.1.2.d | Main / Standby Radio Selection | The L-APC must translate up to two independent M/S receiver confirmations in a message (ED-137) received from the L-APC VoIP Interface and provide associated M/S receiver confirmation signals to the Legacy VCS. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.2.2.1.1.3.a | Remote Receiver Mute | The L-APC must translate up to two independent receiver mute signals received from the Legacy VCS and provide the associated receiver mute selection in a message (ED-137) to the L-APC VoIP Interface. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.2.2.1.1.3.b | Remote Receiver Mute | The L-APC must translate up to two independent receiver mute confirmations in a message (ED-137) received from the L-APC VoIP Interface and provide associated receiver mute confirmation signals to the Legacy VCS. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.2.2.1.1.3.c | Remote Receiver Mute | The L-APC must translate up to two independent receiver unmute signals received from the Legacy VCS and provide the associated receiver unmute selection in a message (ED-137) to the L-APC VoIP Interface. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.2.2.1.1.3.d | Remote Receiver Mute | The L-APC must translate up to two independent receiver unmute confirmations in a message (ED-137) received from the L-APC VoIP Interface and provide associated receiver unmute confirmation signals to the Legacy VCS. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.2.2.1.1.3.e | Remote Receiver Mute | The L-APC must provide the option for muting the APC receive audio path during active PTT. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.2.2.1.1.4.a | Squelch Break | The L-APC must translate up to two independent SQBs in a message (ED-137) received from the L-APC VoIP Interface and provide associated SQB signals to the Legacy VCS. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.2.3.a | L-APC Radio Control Access to R-APC (Analog Port) Between Legacy VCS and VoIP VCS Users | The L-APC must simultaneously accept radio control signals from a single Legacy VCS and up to 6 VoIP VCS control sites. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.3.b | L-APC Radio Control Access to R-APC (Analog Port) Between Legacy VCS and VoIP VCS Users | The L-APC must provide radio control PTT preemption of the lower and equal priority control sites for a single Legacy VCS and up to 6 VoIP VCSs. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.3.c | L-APC Radio Control Access to R-APC (Analog Port) Between Legacy VCS and VoIP VCS Users | The L-APC must support both Legacy VCS and VoIP VCS connections. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.3.d | L-APC Radio Control Access to R-APC (Analog Port) Between Legacy VCS and VoIP VCS Users | The L-APC must simultaneously support both Legacy VCS and VoIP VCS connections. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.3.e | L-APC Radio Control Access to R-APC (Analog Port) Between Legacy VCS and VoIP VCS Users | The L-APC must provide radio control preemption of the lower and equal priority control sites for simultaneous VCS connections. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.3.f | L-APC Radio Control Access to R-APC (Analog Port) Between Legacy VCS and VoIP VCS Users | The L-APC must, in the event of a loss of communications with one or more control sites, maintain communications with remaining operational control sites. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.3.1.a | Non-Priority Mode | The L-APC must, when control facilities have equal priority, provide a transmit voice path and PTT confirmation to that facility from which the PTT arrives first. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.3.1.b | Non-Priority Mode | The L-APC must, when control facilities have equal priority, only allow one facility at a time to have control of the radios; subsequently, lockout the remaining control facilities, i.e., block the voice transmit path, PTT/PTT release, and M/S transmitter/receiver select capabilities of the remaining control facilities. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.3.1.c | Non-Priority Mode | The L-APC must, when in “non-priority mode”, provide receive voice path continuously to all the control facilities. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.3.1.d | Non-Priority Mode | The L-APC must, when in “non-priority mode” and upon release of PTT by the control facility that issued the PTT in progress, transmit a PTT release confirmation message to that control facility and terminate the lockout condition for the other control facilities. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.3.1.e | Non-Priority Mode | The L-APC must, when in “non-priority mode” and upon release of PTT by the control facility that issued the PTT in progress, permit any previously blocked control facility, attempting to PTT, to acquire transmitter(s) without requiring the facility to release and reactivate PTT. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.3.1.f | Non-Priority Mode | The L-APC must, when in “non-priority mode”, provide the option for the Legacy VCS to override PTT of all VoIP VCSs, regardless of which control facility arrives first. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.3.2.a | Prioritized Mode | The L-APC must arbitrate radio access permissions to all the connected control facilities based on their PTT priority levels. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.3.2.b | Prioritized Mode | The L-APC must, in an ED-137 multi-level PTT priority scheme (i.e., Test, Normal, Priority, and Emergency), permit the higher PTT priority facility to override the lower PTT priority control facility with respect to communicating on the frequency(ies) to which those control facilities have access. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.3.2.c | Prioritized Mode | The L-APC must provide a transmit voice path and PTT confirmation to the controlling facility when a controller at that facility asserts PTT. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.3.2.d | Prioritized Mode | The L-APC must, when PTT is active at a lower priority facility and a PTT signal is received from a higher priority facility, release the lower priority facility’s PTT control and lockout that facility while PTT is active from the higher priority facility. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.3.2.e | Prioritized Mode | The L-APC must, when in “prioritized mode”, provide receive voice path continuously to all the control facilities. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.3.2.f | Prioritized Mode | The L-APC must, when in “prioritized mode” and upon release of PTT by the control facility that issued the PTT in progress, transmit a PTT release confirmation message to that control facility and terminate the lockout condition for the other control facilities. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.3.2.g | Prioritized Mode | The L-APC must, when in “prioritized mode” and upon release of PTT by the control facility that issued the PTT in progress, permit any previously blocked control facility, attempting to PTT, to acquire transmitter(s) without requiring the facility to release and reactivate PTT. | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.2.3.2.h | Prioritized Mode | The L-APC must, when in “prioritized mode”, provide the option for the Legacy VCS to override all ED-137 VoIP PTT priorities (i.e., Test, Normal, Priority, and Emergency). | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.3.a | R-APC Functions | The R-APC must translate between analog protocol with L-APC and analog interfaces (voice and signaling) for up to eight Legacy Radios (four Transmitters M/S and four Receivers M/S). | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.3.b | R-APC Functions | The R-APC must translate between ED-137C VoIP and analog interfaces (voice and signaling) for up to eight Legacy Radios. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.3.c | R-APC Functions | The R-APC must meet the requirements for interfacing with legacy radios in accordance with section 3.2.9 of the APC to Analog Radio Control Systems IRD. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.3.d | R-APC Functions | The R-APC must translate between ED-137C VoIP protocol and eight ED-137C VoIP interfaces for up to eight VoIP Radios. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.3.e | R-APC Functions | The R-APC must provide eight individual Ethernet ports to support connections for up to eight VoIP Radios. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.3.f | R-APC Functions | The R-APC must meet the requirements for interfacing with VoIP control sites in accordance with ED-137C, Volume 1 per Clarification Matrix in Section 7 of this specification. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.3.g | R-APC Functions | The R-APC must meet the requirements for interfacing with VoIP radios in accordance with ED-137C Volume 1 per Clarification Matrix in Section 7 of this specification. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.3.h | R-APC Functions | The R-APC must provide controls to limit the concurrent VoIP control site SIP sessions allowed at the network interface from one to a minimum of twelve. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.3.i | R-APC Functions | The R-APC must provide access controls to designate which VoIP control sites can establish SIP sessions with the R-APC. | Functional Requirements | |||||||||||||
| J.1.1 | 3.1.3.j | R-APC Functions | The R-APC must simultaneously support up to two analog L-APC control sites and up to six VoIP control sites (simultaneous analog L-APC and VoIP control site connections). | Functional Requirements | P | ||||||||||||
| J.1.1 | 3.1.3.k | R-APC Functions | The R-APC must, for the control sites defined in requirement 3.1.3j, prevent TX and RX Main/Standby selection on the frequency of any actively keyed transmitters. | Functional Requirements |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .