Presentation is loading. Please wait.

Presentation is loading. Please wait.

ECRIT IETF 62 (March 2005)draft-arai-ecrit-japan-req1 Emergency Call Requirements for IP Telephony Services in Japan draft-arai-ecrit-japan-req Hideki.

Similar presentations


Presentation on theme: "ECRIT IETF 62 (March 2005)draft-arai-ecrit-japan-req1 Emergency Call Requirements for IP Telephony Services in Japan draft-arai-ecrit-japan-req Hideki."— Presentation transcript:

1 ECRIT IETF 62 (March 2005)draft-arai-ecrit-japan-req1 Emergency Call Requirements for IP Telephony Services in Japan draft-arai-ecrit-japan-req Hideki Arai &Motoharu Kawanishi arai859@oki.comkawanishi381@oki.com Oki Electric Industry Co., Ltd.

2 ECRIT IETF 62 (March 2005) draft-arai-ecrit-japan-req 2 Background Requirements shown in this draft are based on the draft report from the Ministry of Internal Affairs and Communications (MIC). http://www.soumu.go.jp/joho_tsusin/eng/Releases/Telecommunications/news050128_7.html This report focuses on VoIP especially, because the IP telephony service with E.164 number has spread rapidly as an alternative to PSTN telephone. Video, text, data etc. are still further study. Citizen’s point of view: Emergency call of IP telephony services should be equivalent to the traditional emergency call, 110 for the police, 118 for the coast guard, and 119 for fire and ambulance. Emergency call acceptance organization’s point of view: It should be easy to migrate from the existing system to IP telephony system. And IP telephony environment should provide the same functionalities as the PSTN environment.

3 ECRIT IETF 62 (March 2005) draft-arai-ecrit-japan-req 3 PSTN Traditional Emergency Call Local Exchange Office Subscriber Local Exchange Office Police Fire & Ambulance Coast Guard 52 offices Approx. 900 offices 11 offices ISDN ISDN or Analog leased line *: To acquire the reporter’s address, each office has also lines for data communication with operators. Translating dialed 11x into the telephone number of the correct office that covers the area where the reporter resides Presenting reporter’s address based on caller-ID. Acquiring reporter’s caller-ID and address from the operator if the reporter called by CLIR (*) Getting emergency call to correct office Presenting and acquiring geographical location information The highest priority must be given to emergency calls Taking priority over all other calls Keeping call connection unless the office terminated the call Keeping connection Allowing offices to acquire caller-ID even if the reporter called by CLIR CLIP or acquiring caller-ID

4 ECRIT IETF 62 (March 2005) draft-arai-ecrit-japan-req 4 Assumed Network Model Two types of network configuration  Emergency call reception office is connected to IP network via PSTN using existing emergency line, and  Connected directly to IP telephony network via a new IP line But VoIP only at this stage Subscriber PSTN Subscriber Office *: Each office uses another line (e.g. IP-VPN) for acquiring the geographical location information of the reporter from an operator. IP network IP network PSTN modelAll IP model

5 ECRIT IETF 62 (March 2005) draft-arai-ecrit-japan-req 5 IP Telephony Requirements for Emergency Messages in Japan (1) Connection to ECRO  PSTN: Voice thru ISDN, and GLI thru wide area ethernet.  All IP: Voice thru VoIP network, and GLI thru wide area ethernet immediately and thru the same network as Voice in the not-too- distant future. Getting Emergency Message to Correct ECRO  Emergency call MUST be got to the correct ECRO, which covers where the reporter is present.  Emergency call MUST be redirected to an alternative facility that the organization designates as an alternative reception office, in case the original ECRO could not do its duty due to a disaster etc.  Information for identifying the operator who can provide the reporter’s subscription information MUST be presented to ECRO.

6 ECRIT IETF 62 (March 2005) draft-arai-ecrit-japan-req 6 IP Telephony Requirements for Emergency Messages in Japan (2) “Keeping connection” and “Reversing call”  Emergency call MUST NOT be terminated unless ECRO terminated it, even though the reporter hung up.  Reporter’s terminal MUST be rung up from ECRO if ECRO intends to resume the conversation with the reporter during “keeping connection” would be activated. Presenting and Acquiring Calling Line Identification  Reporter’s caller-ID MUST be presented to ECRO unless the reporter dials the restriction code followed with “11x”.  ECRO MUST be allowed to acquire the caller-ID even though the reporter dialed with the restriction code.

7 ECRIT IETF 62 (March 2005) draft-arai-ecrit-japan-req 7 IP Telephony Requirements for Emergency Messages in Japan (3) Presenting and Acquiring Geographical Location Information  GLI that the reporter is present MUST be presented to ECRO.  GLI MUST consist of Fixed IP-phone: subscriber’s name, address, address code and telephone number Portable/Mobile IP-phone: subscriber’s name, place of dispatch information, telephone number, and mobile-use or not. Priority over other calls  Emergency call MUST have priority over all other calls in any case. Preventing spoofing  Operator MUST prevent a malicious call pretending the place of dispatch.


Download ppt "ECRIT IETF 62 (March 2005)draft-arai-ecrit-japan-req1 Emergency Call Requirements for IP Telephony Services in Japan draft-arai-ecrit-japan-req Hideki."

Similar presentations


Ads by Google