FE (Functional Element): Difference between revisions

Content deleted Content added
Changes to match Tom's table
Changes to match Tom's table
Line 18:
|-
| Bridge || Bridges (also referred to as "conference bridge" or "conference server") are used in NG9-1-1 to transfer calls and conduct conferences. These have a SIP signaling interface to create and maintain conferences and media mixing capability. Conference Servers MUST be multimedia-capable (voice, video, text). In some deployments, all emergency calls are answered at a “Conference-Aware UA” which acts as a B2BUA until/unless a transfer or conference is needed, in which case it becomes the "Conference Bridge". When calls are "answered at a bridge" and when calls are forwarded by a bridge, the bridge generates an EIDD. {{NGCS}} {{EIDD}}
 
 
|-
| Collaboration || A Functional Element that provides for collaborative communications among agents, both within and between agencies. From NENA/APCO-REQ-001.1.1-2016 {{PSAP}} {{EIDD}}
|-
|Conference Server (or Conference Aware UA)
|Conference Servers are used in NG9-1-1 to transfer calls and conduct conferences. These have a SIP signaling interface to create and maintain conferences and media mixing capability. Conference Servers MUST be multimedia capable (voice, video, text).  In some deployments, all emergency calls are answered at a “Conference Aware UA” which acts as a B2BUA until/unless a transfer or conference is needed, in which case it becomes the Conference Server.
 
|-
|DNS
|All elements connected to the ESInet must have local DNS resolvers to translate hostnames they receive to IP addresses.
|-
| [[ECRF (Emergency Call Routing Function)]] || The routing database in NG9-1-1 which takes location (in civic or geo forms) and a “Service URN” and returns a route in the form of a URI to the next hop in the path the call should take. The ECRF is an instance of a LoST (RFC 5222) server. {{NGCS}}
|-
| EIDD Endpoint FE || This is an FE used by entities outside of the PSAP and Core Services to exchange EIDDs with intra-ESInet entities. {{EIDD}}
 
|-
| [[ESRP (Emergency Services Routing Proxy)]] || The ESRP is an instance of a SIP Proxy Server; an intermediary which routes calls. Note that an ESRP contains a Policy Routing Function, but the PRF is not a separate FE. {{NGCS}}
 
|-
| [[FG (Forest Guide)|FG (Forest Guide)]] || A Forest Guide is a specialized form of an ECRF used by a state ECRF to resolve a query outside the state. The Forest Guide is a national resource that is aware of all state ECRFs as well as other forest guides. {{NGCS}}
|-
| [[GCS (Geocode Service)]] || An NG9-1-1 service providing geocoding and reverse-geocoding. {{NGCS}}
|-
| IDX (Incident Data eXchange) || An EIDD coalescing function that provides a consolidated agency view of the current state of an incident by combining EIDDs generated by multiple constituent FEs within a PSAP. An IDX is usually the source of EIDDs for entities outside the PSAP. Another use is an element that combines EIDDs from multiple agencies working an incident to form an overall incident state. From NENA/APCO-REQ-001.1.1-2016 {{EIDD}} {{PSAP}}
|-
| IMR (Interactive Media Response) System || An automatic multimedia call answering function that can play (multimedia) prompts, accept input (via DTMF or other forms) and record media. A multimedia form of IVR (Interactive Voice Response). {{PSAP}}
|-
|Incident Record Handling || A Functional Element responsible for creation and/or handling of Incident records. NENA/APCO-REQ-001.1.1-2016 {{EIDD}} {{PSAP}}
|-
| [[LIS (Location Information Server)]] || A database that stores locations of endpoints. A LIS can provide Location-by-Reference, or Location-by-Value, and, if the latter, in geodetic or civic forms. A LIS can be queried by an endpoint for its own location, or, in some circumstances, by another entity for the location of an endpoint. The LIS is also the entity that provides the dereferencing service, exchanging a location reference for a location value. {{NGCS}}
Line 43 ⟶ 50:
|- LNG (Legacy Network Gateway) || An NG9-1-1 Functional Element that provides an interface between an un-upgraded legacy origination network and the NGCS. Note that an LNG contains a Location Interworking function (LIF), a Protocol Interworking Function (PIF) and an NG9-1-1 Interworking Function (NIF), but the LIF, PIF and NIF are not separate FEs. {{NGCS}}
|-
|[[LNG (Legacy Network Gateway)]] || An NG9-1-1 Functional Element that provides an interface between an un-upgraded legacy origination network and the NGCS.  Note that an LNG contains a Location Interworking function (LIF), a Protocol Interworking Function (PIF) and an NG9-1-1 Interworking Function (NIF), but the LIF, PIF and NIF are not separate FEs. {{NGCS}}
|-
| Logging Service || An event and media logger. The Logging Service accepts log event records and media streams in a standardized form, stores them, and provides a standardized retrieval function for these records. {{PSAP}} {{NGCS}} {{EIDD}}
Line 59 ⟶ 66:
| [[Policy Store]] || A database that holds policy rules. {{PSAP}} {{NGCS}}
|-
| [[PSAP (Public Safety Answering Point)]] || Public Safety Answering Point (PSAP): An entity responsible for receiving 9-1-1 calls and processing those calls according to a specific operational policy. A PSAP is considered a single FE within the context of the NGCS, but of course, would be constructed of multiple FEs within the PSAP. {{PSAP}}
|-
| SR (Selective Router) || The Central Office switch that provides the tandem switching of 9-1-1 calls. It controls delivery of the voice call with ANI to the PSAP and provides Selective Routing, Speed Calling, Selective Transfer, Fixed Transfer, and certain maintenance functions for each PSAP.<br />
Also known as Enhanced 9-1-1 Control Office, E9-1-1 Tandem
|-
| Management Console || A Functional Element that supports general management functions for the PSAP. It also sends and receives Discrepancy Reports on behalf of the PSAP. From NENA/APCO-REQ-001.1.1-2016 {{EIDD}} {{PSAP}}
|-
| RDS (Responder Data Services) || A Functional Element that enables near real-time wireless data transmissions between PSAPs and emergency responder devices. This includes transmitting dispatch information, creating new Incidents, updating active and closed Incidents. The Responder Data Services FE can support the transmission and receipt of media or a reference (i.e. URL) to that media. From NENA/APCO-REQ-001.1.1-2016 {{EIDD}} {{PSAP}}
|-
| Call Handling || The Call Handling Functional Element is concerned with the details of the management of calls. It handles all communication from the caller. From NENA/APCO-REQ-001.1.1-2016 {{EIDD}} {{PSAP}}
|-
| Dispatch System || A Functional Element used to assign appropriate resources (emergency responders) to an incident, monitor the response and relay relevant information. Tracks and logs all transactions associated with the emergency response. From NENA/APCO-REQ-001.1.1-2016 {{EIDD}} {{PSAP}}
 
|-
| Collaboration[[MIS (Management Information System)]] || AThe MIS Functional Element that provides forreporting collaborativeservices communicationsbased amongon agents,data bothcollected withinfrom and between agenciesFEs. From NENA/APCO-REQ-001.1.1-2016 {{PSAPEIDD}} {{EIDDPSAP}}
|-
| [[MISRMS (ManagementRecords InformationManagement System)]] || TheA MISdatabase Functionalholding Elementhistorical providesrecords reportingof servicesincidents basedand onother dataPSAP collectedrecords. from FEsFrom NENA/APCO-REQ-001.1.1-2016 {{EIDD}} {{PSAP}}
|-
| [[RMSRadio (RecordsInterface Management System)]] || A databasegateway holdingbetween historicala recordsradio of incidentssystem and the other PSAPFEs records.in {{EIDD}}a PSAP. {{PSAP}}
 
|-
|Time Server
| Radio Interface || A gateway between a radio system and the other FEs in a PSAP. {{PSAP}}
|The ESInet must provide an NTP service for time-of-day information. The service may have a hardware clock, or may be synchronized to another NTP time service provided that there are sufficient backups so that if the ESInet is isolated from its time source, it can provide local time. Time accuracy must be within 1 ms of true time. Agencies may have their own time server, which may have a hardware clock if it is more accurate than syncing the server to the ESInet time server. 
|-}
[[Category:Glossary]]
[[Category:Proposed Draft]]|}|}