1 / 240

NENA i3 Requirements

NENA i3 Requirements. Signaling 0100-0100.

varden
Download Presentation

NENA i3 Requirements

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NENA i3 Requirements

  2. Signaling 0100-0100 • Session initiation (call) signaling for IP connected callers shall initially be SIP based. Other protocols are permitted if they are interworked to SIP for presenting to the PSAP. PSAPs shall not be required to accept IP calls sing any protocol other than SIP. The architecture shall permit future evolution to future protocols. • Done i3 Requirement

  3. Signaling 0200-0100 • Signaling shall be supportable over UDP and TCP with or without TLS security. PSAP policy shall govern what of these transport mechanisms are acceptable to it. • Can be done • Psapd doesn’t support TLS yet. i3 Requirement

  4. Signaling 0300-0100 • Abandoned calls shall be captured, with location (if available) and call back address for presentation to the call taker. • Done i3 Requirement

  5. Signaling 0400-0100 • Tracking and Tracing Facilities for all calls must be provided. These include all routing entities as well as all signaling entities. • Done i3 Requirement

  6. Signaling 0500-0100 • Each element in the i3 solution shall maintain call detail records that can be accessed by management systems to develop call statistics in real time. • Done i3 Requirement

  7. Signaling 0600-0100 • The PSAP shall be able to control disconnect. • Done i3 Requirement

  8. Signaling 0700-0100 • The i3 system must harmonize with international specifications to permit local determination of emergency call number (i.e. 9-1-1, 1-1-2) • Can be done • Using LUMP i3 Requirement

  9. Signaling 0800-0100 • Mechanisms must be provided to route calls to areas not served by E9-1-1 to an appropriate PSTN telephone number • Done • Calls can be routed to the PSTN if there is a gateway. i3 Requirement

  10. Signaling 0900-0100 • Each element of the i3 system shall provide congestion controls • Can be done i3 Requirement

  11. Signaling 1000-0100 • It shall be possible to determine the complete call chain of a call, including the identity of each signaling element in the path, and the reason it received the call (Call History). • Done • The call chain can be inferred from SIP Via header. i3 Requirement

  12. Signaling 1100-0100 • Support must be provided to accept calls from selective routers (possibly through suitable gateways), including CAMA and ISDN interfaces • Done • if hardware is provided i3 Requirement

  13. Signaling 1200-0100 • When defining the solution, consideration must be given to POTS users placing emergency calls through gateways to IP based systems • Done i3 Requirement

  14. Signaling 1300-0100 • Support must be provided to accept calls from end offices and MSCs where selective routers are no longer provided, including SS7, CAMA and ISDN interfaces • Done • if hardware is provided i3 Requirement

  15. Signaling 1400-0100 • Call setup time (dialing of last digit to ring at the PSAP), under expected peak load shall be less than 2 seconds. If CAMA signaling is in the path, then an additional 7 seconds is permitted. • Done i3 Requirement

  16. Signaling 1500-0100 • Voice Activity Detection shall be disabled for emergency calls. • Done • SIPc uses RAT4 which can turn on/off the silence suppression. i3 Requirement

  17. Media 0100-0100 • PSAPs shall accept voice, video and text media streams on RTP transport • Done i3 Requirement

  18. Media 0200-0100 • PSAPs shall support existing TDD devices including direct detection and demodulation of tones as well as via tone detection and demodulation at an intermediate VoIP gateway • Done • Needs no additional works i3 Requirement

  19. Media 0300-0100 • PSAPs shall have facilities to detect and react to silent calls • Done i3 Requirement

  20. Media 0400-0100 • It shall be possible for PSAPs to supply ringback media to callers • Done • SIP sends a 180 ringing response i3 Requirement

  21. Media 0500-0100 • It shall be possible for PSAPs to accept additional media (e.g. images) from callers without tearing down the call. • Can be done i3 Requirement

  22. Media 0600-0100 • The i3 solution shall specify a minimal (e.g. DiffServe) QoS mechanism for use for media presented to or originated from the PSAP • Can be done i3 Requirement

  23. Media 0700-0100 • i3 elements which originate media shall have media loopback mechanisms. • Can be done i3 Requirement

  24. Location 0100-0100 • Calls using VoIP or subsequent methods are expected to supply location with the call • Done i3 Requirement

  25. Location 0200-0100 • PSAPS shall accept location as civic and/or geo specified • Done i3 Requirement

  26. Location 0300-0100 • The format for location shall be PIDF-LO • Done i3 Requirement

  27. Location 0400-0100 • All representations of location shall include the ability to carry altitude. This requirement does not imply altitude is always used or supplied • Done i3 Requirement

  28. Location 0500-0100 • Altitude shall be provided if available. • Done i3 Requirement

  29. Location 0600-0100 • The Preferred coordinate basis (i.e. WGS-84) • Done i3 Requirement

  30. Location 0700-0100 • Implications of multiple Location Objects • Undefined behavior • This is standardization issue. i3 Requirement

  31. Location 0800-0100 • No assumption shall be made that the entity presenting the call to the PSAP has any knowledge of, or control over the provider of location. The location provider may be independent of all other service providers handling the call • Done i3 Requirement

  32. Location 0900-0100 • The location source shall be identified and should be Authenticated. • Done • Authentication is not required i3 Requirement

  33. Location 1000-0100 • Systems which deploy external LISs that use keys shall provide intermediaries to query the LIS and supply the PSAP with location. The PSAP is not expected to query a LIS with a key in order to determine location. • Out of scope i3 Requirement

  34. Location 1100-0100 • PSAPs shall have the ability to requery for a location update. • Can be done i3 Requirement

  35. Location 1200-0100 • PSAPs shall have the ability to subscribe to an automatic location update event for a particular call • Can be done i3 Requirement

  36. Location 1300-0100 • Empty in the TID i3 Requirement

  37. Location 1400-0100 • PSAPs shall be able to make use of fall-back location information when measurement based location determination mechanisms fail. Examples include tower/Access Point location, last known fix, etc • Done • No additional works needed i3 Requirement

  38. Location 1500-0100 • PSAPs must be made aware when fall back location information was used to route a call • Done • No additional works needed i3 Requirement

  39. CallBack 0100-0100 • Calls to 9-1-1 shall supply a call back address (URI) with the call • Done i3 Requirement

  40. CallBack 0200-0100 • Calls must provide both a permanent address that reaches the caller and, if different, a temporary address to immediately reconnect to the caller if the call is dropped • Done i3 Requirement

  41. AddInfo 0100-0100 • Additional information may be available to the call taker based on the location of the caller, see section 4.2.1 • Done • PIDF-LO can have additional information i3 Requirement

  42. AddInfo 0200-0100 • Additional information may be available to the call taker based on the owner of the structure, see section 4.2.1 • Done • PIDF-LO i3 Requirement

  43. AddInfo 0300-0100 • Additional information may be available to the call taker based on the tenant of the structure, see section 4.2.1 • Done • PIDF-LO i3 Requirement

  44. AddInfo 0400-0100 • Where a vehicle is involved, additional information may be available, see section 4.2.1 • Done • PIDF-LO i3 Requirement

  45. AddInfo 0500-0100 • Additional information may be available based on the Address of Record (AoR) of the caller. In this context, AoR equates to the caller • Done i3 Requirement

  46. AddInfo 0600-0100 • Consideration should be given to permitting users to have domain independent mechanisms to supply information related to the caller • Done i3 Requirement

  47. 3rdParty 0100-0100 • 3rd party originated calls should be fully supported in the i3 solution • To all 3rd party requirements, there is no difference between a normal sos call and a call from 3rd party. i3 Requirement

  48. 3rdParty 0200-0100 • PSAPs should receive an indication with the call that it is a 3rd party call • Done i3 Requirement

  49. 3rdParty 0300-0100 • All parties The PSAP should receive the identities of all other parties in the call. This may need to be specific to an operator in a 3rd party call center • Done i3 Requirement

  50. 3rdParty 0400-0100 • The call should include callback information for both the caller and the 3rd party such that the PSAP can recreate the call if it is dropped. • Done i3 Requirement

More Related