Emergency Telecommunication Services: Indian Requirements

1. Emergency Telecommunication Services: Indian Requirements Company: NEC Corporation Purpose: Discussion and Approval GISFI#12, March 2013

2. Abstract • Input document to GISFI draft TR (GISFI_CSeON_201212318) on Emergency Telecommunication Services Doc number: GISFI_CSeON_201303362 • This document describes the Indian requirements and issues to be addressed to standardize and implement ETS services. Propose to approve this document as input to the TR on ETS. GISFI#12, March 2013

3. Outline • Emergency Telecom Services in India • National Numbering Plan • Location Tracking and Caller Identification Issues • Emergency Calls without Subscriber Identity Module • Location and Ownership of Public Service Access Points • Local Language Support and Social Inclusion • National Security Implications • Proposal GISFI#12, March 2013

4. Emergency Telecom Services in India • Clause 29.1 of UAS license to the service providers: • “The licensee shall provide independently or through mutually agreed commercial agreements with other service providers, all public utility services including TOLL FREE services such as police, fire, ambulance, railways/ road/Air accident enquiry, police control, disaster management etc. While providing emergency services such as police, fire, ambulance etc. it shall be delivered to the control room of concerned authority for the area from where call is originated”. • India’s National Telecom Policy 2012 • “To facilitate an institutional framework to establish nationwide Unified Emergency Response Mechanism by providing nationwide single access number for emergency services.” • “To create appropriate regulatory framework for provision of reliable means of public communication by Telecom Service Providers during disasters.” UAS license: http://www.auspi.in/policies/UASL.pdf NTP 2012: www.dot.gov.in/ntp/NTP-06.06.2012-final.pdf GISFI#12, March 2013

5. National Numbering Plan • National Numbering Plan, 2003 from Govt. of India: • Use ‘100’, ‘101’ and ‘102’ for Police, Fire and Ambulance services • ‘107X’ for emergency information • 1056 Emergency Medical Services (Toll free in local area) • 108 Emergency Disaster Management Services (Toll free in local area) • Eight major categories of 3 digit emergency numbers + subcategories having 4th digit to dial • Overlapping numbers for similar services • Difficult to remember large number of Emergency contacts for different purposes • Multiple agency coordination difficult task National number plan : http://www.dot.gov.in/numbering_plan/nnp2003.pdf Standardisation requirement : Nationwide single number for integrated emergency services in line with NNP GISFI#12, March 2013

6. Location Tracking and Caller Identification Issues • DoT mandate on LBS for Indian mobile operator (this should apply to ETS too) • Urban areas need to implement LBS with accuracy of 30% in less than 50 metres • 60% in less than 100 metres and • 80% in less than 300 metres • Currently only Cell ID available • Low penetration of GPS makes network based positioning mandatory • Overhead associated with transfer of caller identification & location information in real time • Confidentiality issues : Access of personal contact information and location through centralized database maintained by the government or third party agency. • Standards compatible location tracking solutions in case of SMS, data calls, SIM-less emergency calls etc. Standardisation requirement : LBS technology on all cellular networks (GSM/CDMA/3G/LTE) GISFI#12, March 2013

7. Emergency Calls without Subscriber Identity Module • Issues with inactive or no SIM in emergency calls: • Non-traceability of location details • Lack of subscriber details • Unavailability of call back numbers to verify the origin of the call • SIM-less emergency calls barred in various countries. Ex : Australia, Europe • Need of central database of IMEI, MSISDN. Issues of privacy and secrecy of subscribers • Support for Standard GSM emergency number 112 • Support for redirection to national emergency numbers Standardisation requirement : Handling emergency calls from SIM-less or locked mobile phones GISFI#12, March 2013

8. Location and Ownership of Public Service Access Points Current routing of Emergency Calls in India GISFI#12, March 2013

9. Location and Ownership of Public Service Access Points • Issue of location and ownership of third party PSAPs • Call routing methods • IUC and UASL charges to operators • Operation and maintenance of networks • Centralized or distributed PSAPs • Survivability • Load balancing • Service continuity Standardisation requirement : PSAP architecture and interfaces to PSTN, PLMN networks GISFI#12, March 2013

10. Local Language Support • Adult literacy rate in India is 74% • Six Indian states account for about 70% of all illiterates in India: Uttar Pradesh, Bihar, Madhya Pradesh, Rajasthan, Andhra Pradesh and West Bengal • Languages to offer ETS services • Official languages Hindi and English alone not feasible • Regional language support required • Third party conferencing services for language translation to be provisioned with PSAP Standardisation requirement : Language translation standards for ETS services. Emergency alerts in Indian language GISFI#12, March 2013

11. Social Inclusion • Non voice emergency services • For hearing and speech impaired citizens • Support for text-only emergency communication • Provision of separate/dedicated access code for differently abled people. EX: 106 in Australia • Ongoing standardization work at ETSI – EMTEL on Non voice emergency services Standardisation requirement : Standards for text based emergency call, ETS services GISFI#12, March 2013

12. National Security Implications • Priority treatment for national security and emergency preparedness (NS/EP) organizations in face of national security threat. • Centralized response systems can be vulnerable to: 1. Attacks – Physical or application software related (virus, malware, denial of service, hacking etc) 2. Network failures due to infrastructure damage, power failures, software/hardware problems etc. 3. Congestion - Call overload due to sudden surge created in event of disasters. 4. Hoax calls to generate panic and misdirect the emergency response systems • Standardize the interconnectivity and emergency service provisioning across technologies and operators • DoT guideline for SIM cards issued to foreign citizen : “Any mobile connection issued to a foreigner should not have a validity beyond the validity of the visa.” Also this period cannot exceed 3 months. • Need to differentiate between emergency services provided to Indian and Foreign nationals Standardisation requirement : Security standards for PSAPs, interconnectivity and end-to-end service provisioning GISFI#12, March 2013

13. National eGovernance Plan • Govt. of India has notified 166 as single number access for all non-emergency government services • NeGP standards being evolved for Mobile Service Delivery, Localization of services, support for local languages etc. • Mobile Apps for m-Governance hosted by DeITY • Some applications include support for automated dialing for single emergency response phone number. Ex: Rakshak* mobile app Ref: * http://apps.mgov.gov.in/descp.do?appid=274&action=0 Standardisation requirement : Common requirements of service amongst NeGP and proposed single number ETS access need to be identified and mapped GISFI#12, March 2013

14. Summary of Standardization Requirements • Nationwide single number for integrated emergency services in line with NNP 2013 • LBS technology on all cellular networks (GSM/CDMA/3G/LTE) • Handling emergency calls from SIM-less or locked mobile phones • PSAP architecture and interfaces to PSTN, PLMN networks • Language translation standards for ETS services. Emergency alerts in Indian language • Standards for text based emergency call, ETS services • Security standards for PSAPs, interconnectivity and end-to-end service provisioning • Common requirements of service amongst NeGP and proposed single number ETS access need to be identified and mapped GISFI#12, March 2013

15. Thank you GISFI#12, March 2013