Emergency calls
In some examples, a device detects a calling identifier received as part of initiating a call matches an emergency identifier, the emergency identifier associated with information from which to derive a Uniform Resource Name (URN). The device detects that the device is attached to or registered a first network different from a second network, where the second network configured the emergency identifier. In response to detecting that the device is attached to or registered the first network different from the second network, the device includes a Session Initiation Protocol (SIP) Uniform Resource Identifier (URI) in a Session Initiation Protocol (SIP) INVITE message to be transmitted.
1. A method of a user equipment (UE), comprising:
receiving, at the UE, an Extended Local Emergency Number List from a first Public Land Mobile Network (PLMN);
detecting, by the UE, an emergency number;
deriving, by the UE, a Uniform Resource Name (URN) from the Extended Local Emergency Number List, the URN associated with the emergency number;
detecting, at the UE, that the UE is attached to or registered with a second PLMN different from the first PLMN; and
in response to the detecting that the UE is attached to or registered with the second PLMN different from the first PLMN, including, by the UE, a particular Session Initiation Protocol (SIP) Uniform Resource Identifier (URI) in a Session Initiation Protocol (SIP) INVITE message.
2. The method of claim 1 , wherein the SIP URI is included in a header or a body of the SIP INVITE message.
3. The method of claim 1 , wherein the second PLMN is used to request an emergency service identified by the emergency number.
4. The method of claim 1 , wherein the Extended Local Emergency Number List is included within an Extended Emergency Number List (EENL) Information Element (IE).
5. The method of claim 4 , wherein the EENL IE is received from a network node that is part of the first PLMN.
6. The method of claim 4 , wherein the EENL IE is provisioned via receipt of at least one of a TRACKING AREA UPDATE ACCEPT message, an ATTACH ACCEPT message, or a REGISTRATION ACCEPT message.
7. The method of claim 1 , wherein the detecting that the UE is attached to or registered with the second PLMN different from the first PLMN is based on comparing a PLMN code of the second PLMN with a PLMN code of the first PLMN.
8. The method of claim 1 , wherein the detecting that the UE is attached to or registered with the second PLMN different from the first PLMN is based on determining that the second PLMN is not an equivalent PLMN of the first PLMN.
9. The method of claim 1 , wherein the detecting that the UE is attached to or registered with the second PLMN different from the first PLMN is based on detecting that the second PLMN is unknown.
10. The method of claim 1 , wherein the Extended Local Emergency Number List includes the URN.
11. The method of claim 1 , further comprising:
determining, by the UE, whether the UE is emergency registered with a PLMN; and
transmitting the SIP INVITE message including the particular SIP URI, in response to the determining.
12. The method of claim 1 , further comprising matching the URN derived from the Extended Local Emergency Number List to one or more well-known URNs that include the URN.
13. The method of claim 12 , wherein the including of the particular SIP URI in the SIP INVITE message is responsive to the matching.
14. A user equipment (UE) comprising:
at least one hardware processor configured to:
receive an Extended Local Emergency Number List from a first Public Land Mobile Network (PLMN);
detect an emergency number;
derive a Uniform Resource Name (URN) from the Extended Local Emergency Number List, the URN associated with the emergency number;
detect that the UE is attached to or registered with a second PLMN different from the first PLMN; and
in response to the detecting that the UE is attached to or registered with the second PLMN different from the first PLMN, include a particular Session Initiation Protocol (SIP) Uniform Resource Identifier (URI) in a Session Initiation Protocol (SIP) INVITE message to be transmitted by the UE.
15. The UE of claim 14 , wherein the SIP URI is included in a header or a body of the SIP INVITE message.
16. The UE of claim 14 , wherein the detecting that the UE is attached to or registered with the second PLMN different from the first PLMN is based on comparing a PLMN code of the second PLMN with a PLMN code of the first PLMN.
17. The UE of claim 14 , wherein the detecting that the UE is attached to or registered with the second PLMN different from the first PLMN is based on determining that the second PLMN is not an equivalent PLMN of the first PLMN.
18. The UE of claim 14 , wherein the detecting that the UE is attached to or registered with the second PLMN different from the first PLMN is based on detecting that the second PLMN is unknown.
19. A non-transitory machine-readable medium comprising instructions that upon execution cause a user equipment (UE) to:
receive an Extended Local Emergency Number List from a first Public Land Mobile Network (PLMN);
detect an emergency number;
derive a Uniform Resource Name (URN) from the Extended Local Emergency Number List, the URN associated with the emergency number;
detect that the UE is attached to or registered with a second PLMN different from the first PLMN; and
in response to the detecting that the UE is attached to or registered with the second PLMN different from the first PLMN, include a particular Session Initiation Protocol (SIP) Uniform Resource Identifier (URI) in a Session Initiation Protocol (SIP) INVITE message to be transmitted by the UE.
20. The non-transitory machine-readable medium of claim 19 , wherein the SIP URI is included in a header or a body of the SIP INVITE message.