tech-invite   World Map
3GPP     Specs     Glossaries     UICC       T+       IETF     RFCs     Groups     SIP     ABNFs       Search     Home
Top        in Index        Prev        Next

TR 22.871 (SA1)
Study on non-voice emergency services

|   ToC   |   3GPP‑Page   |   Help   |

(W-zip) V11.3.0    2011/10    29 p.


Rapporteur:  Dr. Williams, David Hugh
See also:  –


Non-voice communication such as text messages and instant messaging via wireless devices has been very successful and continues to expand. Many consumers assume that they can utilize these types of non-voice communications as mechanisms to communicate with emergency services whenever emergency assistance is required. Such mechanisms currently do not exist. The Emergency Services community has a desire to have multimedia emergency services supported with the same general characteristics as emergency voice calls.

Currently, TS 22.101 service requirements for emergency calls (with or without the IP Multimedia Core Network) are limited to voice media. The Non-Voice Emergency Services is intended to be an end-to-end citizen to authority communications. The Non-Voice Emergency Services could support the following examples of non-voice communications to an emergency services network:
  • Session based text messages (which does not include SMS) from citizen to emergency services
  • Session based and session-less instant messaging type sessions with emergency services
  • Multi-media (e.g., pictures, video clips) transfer to emergency services either during or after other communications with emergency services
  • Real-time video session with emergency services.
In addition to support the general public, this capability would facilitate emergency communications to emergency services by individuals with special needs (e.g., hearing impaired citizens).

NOVES does not preclude the support of specialized emergency services and devices designed for the special needs communities. The requirements defined for the support of specialized emergency services and devices for the special needs communities may differ from the NOVES requirements.

NOVES as defined in this TR focuses on Next Generation Network (NGN) technology and does not include legacy messaging services, such as Short Messaging Service (SMS). In addition, NOVES only supports human initiated devices.

Note:  While text messaging is expected to remain popular, the underlying technology will shift from legacy SMS to IP-enabled messaging (including various forms of instant messaging (IM)) to support NOVES. Increasingly, both smart phones and feature phones support multiple technologies for text messaging. It is important not to confuse a specific underlying technology such as SMS with functionality such as text messaging.

Non Voice Emergency Services will be applicable to GPRS (GERAN, UTRAN) and to EPS (GERAN, UTRAN, E UTRAN and non-3GPP).


 

Here        Top        None        None        Next
part:    1     2

 

 

1   Scope   Word-p. 8
2   References
3   Definitions, symbols and abbreviations
4   Use cases
4.1   Use case 1 Session Based Text Message to Emergency Services
4.2   Use case 2 Multimedia Telephony communication with real time text to Emergency services
4.3   Use case 3 Emergency Communication to PSAP with the Addition of Media
4.4   Use case 4 Delayed Transmission of Media of an Emergency Situation Associated with Voice Communications to a PSAP      Up
4.5   Use case 5 Transmission of Media in a Non-Voice Interaction with a PSAP
4.6   Use case 6 Communication with PSAP when voice is inappropriate   Word-p. 15
4.7   Use case 7 Menu / Short Cut service
4.8   Use case 8 Texting application communication to emergency services with one-way RTT   Word-p. 17
4.9   Use case 9. Differentiating Emergency Experiences and Adding Media to a Text-Initiated Emergency Call      Up
4.10   Use case 10 Multimedia Telephony communication mainly in Sign Language to Emergency services   Word-p. 20

Up        Top        ToC