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 in a first network different from a second network, where the second network configured the emergency identifier. In response to detecting that the device is in the first network different from the second network, the device includes a URN, urn:service:sos, in a Session Initiation Protocol (SIP) INVITE message to be transmitted.
1. A method of a user equipment (UE), comprising:
detecting, at the UE, that a calling identifier, received as part of initiating a call by the UE, matches a first emergency identifier, the first emergency identifier associated with information related to a Uniform Resource Name (URN);
detecting, at the UE, that the UE is in a second network different from a first network, wherein the first emergency identifier is configured by the first network; and
in response to the detecting that the UE is in the second network different from the first network, including, by the UE, a particular URN, urn:service:sos, in a Session Initiation Protocol (SIP) INVITE message to be transmitted by the UE.
2. The method of claim 1 , wherein the second network is used to request an emergency service identified by the first emergency identifier.
3. The method of claim 1 , further comprising receiving, by the UE, the first emergency identifier from the first network.
4. The method of claim 1 , wherein the first emergency identifier associated with the information related to the URN is included within a first Extended Emergency Number List (EENL) Information Element (IE).
5. The method of claim 4 , wherein the first EENL IE is received from a network node that is part of the first network.
6. The method of claim 4 , wherein the first 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 second network does not provision a second emergency identifier associated with the information related to the URN.
8. The method of claim 1 , wherein the second network is a second Public Land Mobile Network (PLMN), and the first network is a first PLMN.
9. The method of claim 8 , wherein detecting that the UE is in the second PLMN different from the first PLMN is based on one or more of:
comparing a PLMN code of the second PLMN with a PLMN code of the first PLMN, or
determining that the second PLMN is not an equivalent PLMN of the first PLMN.
10. The method of claim 1 , further comprising receiving, by the UE, the information related to the URN.
11. The method of claim 10 , wherein the information related to the URN includes the URN.
12. The method of claim 1 , wherein the first emergency identifier and the information related to the URN is one or more of:
received in an Extended Emergency Number List (EENL) Information Element, or
received from a memory, a Universal Integrated Circuit Card (UICC), an application on a UICC, a Universal Subscriber Identity Module (USIM), and an Internet Protocol (IP) Multimedia System Identity Module (ISIM).
13. The method of claim 1 , wherein the detecting that the UE is in the second network different from the first network is based on detecting that the second network is unknown.
14. The method of claim 1 , further comprising:
determining, by the UE, whether the UE is emergency registered with a network; and
transmitting the SIP INVITE message including the particular URN, urn:service:sos, in response to the determining.
15. A user equipment (UE) comprising:
a hardware processor configured to:
detect that a calling identifier, received as part of initiating a call by the UE, matches a first emergency identifier, the first emergency identifier associated with information related to a Uniform Resource Name (URN);
detect that the UE is in a second network different from a first network, wherein the first emergency identifier is configured by the first network; and
in response to the detecting that the UE is in the second network different from the first network, include a particular URN, urn:service:sos, in a Session Initiation Protocol (SIP) INVITE message to be transmitted by the UE.
16. The UE of claim 15 , wherein the first emergency identifier associated with the information related to the URN is included within a first Extended Emergency Number List (EENL) Information Element (IE).
17. The UE of claim 16 , wherein the first EENL IE is received from a network node that is part of the first network.
18. The UE of claim 16 , wherein the first 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.
19. The UE of claim 15 , wherein the second network does not provision a second emergency identifier associated with information related to the URN.
20. A non-transitory machine-readable medium comprising instructions that upon execution cause a user equipment (UE) to:
detect that a calling identifier, received as part of initiating a call by the UE, matches a first emergency identifier, the first emergency identifier associated with information related to a Uniform Resource Name (URN);
detect that the UE is in a second network different from a first network, wherein the first emergency identifier is configured by the first network; and
in response to the detecting that the UE is in the second network different from the first network, include a particular URN, urn:service:sos, in a Session Initiation Protocol (SIP) INVITE message to be transmitted by the UE.