Stay organized with collections
Save and categorize content based on your preferences.
A partner endpoint refers to the partner-owned and partner-operated
infrastructure that receives user emergency location information from ELS. ELS
supports these protocols for reporting location information and additional
emergency information to endpoints:
Types of endpoint
ELS supports these protocols for reporting location information and additional
emergency information to endpoints:
HTTPS: The partner endpoint is a standard HTTPS server capable of
receiving POST requests. ELS information is encoded as name-value pairs in each
POST request. See ELS HTTPS Specification.
SMS: The partner endpoint is a phone number (short code or long code)
capable of receiving SMS messages. SMS messages can be sent as regular SMS
or Data SMS. See ELS SMS Specification.
Both of the transmission protocols comply with the ETSI
AML standard, but can be extended by adding additional
fields and capabilities, as described in this documentation.
Why use both
Each of the transmission protocols described earlier has advantages and
disadvantages. Android strongly recommends using both protocols simultaneously,
with basic matching on phone number or IMEI, to gain the benefits of both. For
more on the ideal way to combine both formats, see EENA
webinar.
Security considerations
Regardless of the endpoint type, consider security. Endpoints must be resilient
to distributed denial-of-service (DDoS) and other kinds of attacks, and may be
required to undergo a Google security audit prior to deployment.
Compliance
Android's implementation of AML should comply with the latest published ETSI
AML standard and with the relevant regulation (such as,
Delegated Regulation (EU) 2019/320). For any questions
or concerns about compliance testing, contact your test lab. Google can only
support specific questions about testing and compliance directly from certified
testing laboratories.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-10-31 UTC."],[[["\u003cp\u003eA partner endpoint is partner-owned infrastructure that receives user emergency location information from ELS using HTTPS or SMS protocols.\u003c/p\u003e\n"],["\u003cp\u003eELS supports HTTPS and SMS protocols, allowing for the transmission of emergency location and additional user information.\u003c/p\u003e\n"],["\u003cp\u003eAndroid recommends implementing both HTTPS and SMS protocols for enhanced reliability and redundancy.\u003c/p\u003e\n"],["\u003cp\u003ePartner endpoints must be secure and resilient to attacks like DDoS, potentially requiring a Google security audit before deployment.\u003c/p\u003e\n"],["\u003cp\u003eGoogle's ELS implementation aims to comply with the latest ETSI AML standard and relevant regulations like Delegated Regulation (EU) 2019/320.\u003c/p\u003e\n"]]],["ELS (Emergency Location Service) sends user emergency location data to partner endpoints via HTTPS or SMS protocols. HTTPS uses POST requests with name-value pairs, while SMS sends regular or data SMS messages. These protocols comply with the ETSI AML standard but can be extended. Using both protocols is recommended for redundancy. Endpoints must be secure and may undergo Google security audits. The implementation complies with the latest ETSI AML standards and relevant regulations.\n"],null,["A partner endpoint refers to the partner-owned and partner-operated\ninfrastructure that receives user emergency location information from ELS. ELS\nsupports these protocols for reporting location information and additional\nemergency information to endpoints:\n\nTypes of endpoint\n\nELS supports these protocols for reporting location information and additional\nemergency information to endpoints:\n\n- **HTTPS** : The partner endpoint is a standard HTTPS server capable of receiving POST requests. ELS information is encoded as name-value pairs in each POST request. See [ELS HTTPS Specification](/android/els/reference/http-spec).\n- **SMS** : The partner endpoint is a phone number (short code or long code) capable of receiving SMS messages. SMS messages can be sent as regular SMS or Data SMS. See [ELS SMS Specification](/android/els/reference/sms-spec).\n\nBoth of the transmission protocols comply with the [ETSI\nAML](https://www.etsi.org/standards#page=1&search=AML&title=1&etsiNumber=1&content=1&version=0&onApproval=1&published=1&withdrawn=1&historical=1&isCurrent=1&superseded=1&startDate=1988-01-15&harmonized=0&keyword=&TB=&stdType=&frequency=&mandate=&collection=&sort=1) standard, but can be extended by adding additional\nfields and capabilities, as described in this documentation.\n| **Key Term:** For this service, ELS refers to Google's implementation of the [ETSI\n| AML](https://www.etsi.org/standards#page=1&search=AML&title=1&etsiNumber=1&content=1&version=0&onApproval=1&published=1&withdrawn=1&historical=1&isCurrent=1&superseded=1&startDate=1988-01-15&harmonized=0&keyword=&TB=&stdType=&frequency=&mandate=&collection=&sort=1) standard, which complies with but may extend or augment published standards.\n\nWhy use both \n\nEach of the transmission protocols described earlier has advantages and\ndisadvantages. Android strongly recommends using both protocols simultaneously,\nwith basic matching on phone number or IMEI, to gain the benefits of both. For\nmore on the ideal way to combine both formats, see [EENA\nwebinar](https://www.youtube.com/watch?v=D6ZAsJvmrkg).\n\nSecurity considerations\n\nRegardless of the endpoint type, consider security. Endpoints must be resilient\nto distributed denial-of-service (DDoS) and other kinds of attacks, and may be\nrequired to undergo a Google security audit prior to deployment.\n\nCompliance\n\nAndroid's implementation of AML should comply with the latest published [ETSI\nAML standard](https://www.etsi.org/standards#page=1&search=AML&title=1&etsiNumber=1&content=1&version=0&onApproval=1&published=1&withdrawn=1&historical=1&isCurrent=1&superseded=1&startDate=1988-01-15&harmonized=0&keyword=&TB=&stdType=&frequency=&mandate=&collection=&sort=1) and with the relevant regulation (such as,\n[Delegated Regulation (EU) 2019/320](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:OJ.L_.2019.055.01.0001.01.ENG)). For any questions\nor concerns about compliance testing, contact your test lab. Google can only\nsupport specific questions about testing and compliance directly from certified\ntesting laboratories."]]
