INTERNET PROTOCOL MULTIMEDIA SUBSYSTEM EMERGENCY CALLS FOR ROAMING USER EQUIPMENTS

Abstract

A method of operating a user equipment (“UE”) to handle an internet protocol multimedia subsystem (“IMS”) emergency call can include sending a session initiation protocol (“SIP”) REGISTER request relating to an emergency registration to a proxy call session control function (“P-CSCF”) of an IMS network. The method can further include, responsive to sending the SIP REGISTER request, receiving a response from the P-CSCF. The method can further include, responsive to receiving the response, performing an action based on the response.

Claims

1. A method of operating a user equipment (“UE”) to handle an internet protocol multimedia subsystem (“IMS”) emergency call, the method comprising: sending a session initiation protocol (“SIP”) REGISTER request relating to an emergency registration to a proxy call session control function (“P-CSCF”) of an IMS network; responsive to sending the SIP REGISTER request, receiving a response from the P-CSCF; and responsive to receiving the response, performing an action based on the response.

2. The method of claim 1, wherein the IMS emergency call comprises an unauthenticated IMS emergency call, wherein receiving the response comprises receiving an error response, and wherein performing the action comprises, responsive to receiving the error response, sending a SIP INVITE request relating to an unauthenticated IMS emergency call to the P-CSCF

3. The method of claim 2, wherein the SIP INVITE request comprises an indication of an internet protocol (“IP”) address of the UE.

4. The method of claim 1, wherein the IMS emergency call comprises an authenticated IMS emergency call, wherein receiving the response comprises receiving a 200 OK response including a telephone (“TEL”) and/or a SIP uniform resource identifier (“URI”) for the UE, and wherein performing the action comprises, responsive to receiving the 200 OK response, making the IMS emergency call.

5. The method of claim 4, wherein the 200 OK response includes the SIP URI for the UE, wherein the SIP URI is based on a mobile network code (“MNC”), a mobile country code (“MCC”), and global E.164 number conversion of a mobile subscriber integrated services digital network number (“MSISDN”), and wherein the SIP URI is of the form: “[E.164 number]@ims.mnc[MNC].mcc[MCC].3gppnetwork.org”

6. The method of claim 4, wherein the SIP REGISTER request comprises an indication of an internet protocol (“IP”) address of the UE.

7. The method of claim 1, wherein the UE is roaming on the IMS network, wherein the UE and the P-CSCF are part of a visited public land mobile network (“VPLMN”), and wherein the UE is separate and distinct from the P-CSCF.

8. A user equipment (“UE”) configured to handle an internet protocol multimedia subsystem (“IMS”) emergency call, the UE comprising: a transceiver configured to communicate with an IMS network comprising a proxy call session control function (“P-CSCF”); a processor; and a memory coupled to the processor and having instructions stored therein that are executable by the processor to cause the UE to perform operations comprising: sending a session initiation protocol (“SIP”) REGISTER request relating to an emergency registration to the P-CSCF; responsive to sending the SIP REGISTER request, receiving a response from the P-CSCF; and responsive to receiving the response, performing an action based on the response.

9. The UE of claim 8, wherein the IMS emergency call comprises an unauthenticated IMS emergency call, wherein receiving the response comprises receiving an error response, and wherein performing the action comprises, responsive to receiving the error response, sending a SIP INVITE request relating to an unauthenticated IMS emergency call to the P-CSCF

10. The UE of claim 9, wherein the SIP INVITE request comprises an indication of an internet protocol (“IP”) address of the UE.

11. The UE of claim 8, wherein the IMS emergency call comprises an authenticated IMS emergency call, wherein receiving the response comprises receiving a 200 OK response including a telephone (“TEL”) and/or a SIP uniform resource identifier (“URI”) for the UE, and wherein performing the action comprises, responsive to receiving the 200 OK response, making the IMS emergency call.

12. The UE of claim 11, wherein the 200 OK response includes the SIP URI for the UE, wherein the SIP URI is based on a mobile network code (“MNC”), a mobile country code (“MCC”), and global E.164 number conversion of a mobile subscriber integrated services digital network number (“MSISDN”), and wherein the SIP URI is of the form: “[E.164 number]@ims.mnc[MNC].mcc[MCC].3gppnetwork.org”

13. The UE of claim 11, wherein the SIP REGISTER request comprises an indication of an internet protocol (“IP”) address of the UE.

14. The UE of claim 8, wherein the UE is roaming on the IMS network, wherein the UE and the P-CSCF are part of a visited public land mobile network (“VPLMN”), and wherein the UE is separate and distinct from the P-CSCF.

15. A non-transitory computer-readable medium having instructions stored therein that are executable, by a processor of a user equipment (“UE”) configured to handle an internet protocol multimedia subsystem (“IMS”) emergency call, to cause the UE to perform operations comprising: sending a session initiation protocol (“SIP”) REGISTER request relating to an emergency registration to a proxy call session control function (“P-CSCF”) of an IMS network; responsive to sending the SIP REGISTER request, receiving a response from the P-CSCF; and responsive to receiving the response, performing an action based on the response.

16. The non-transitory computer-readable medium of claim 15, wherein the IMS emergency call comprises an unauthenticated IMS emergency call, wherein receiving the response comprises receiving an error response, and wherein performing the action comprises, responsive to receiving the error response, sending a SIP INVITE request relating to an unauthenticated IMS emergency call to the P-CSCF

17. The non-transitory computer-readable medium of claim 16, wherein the SIP INVITE request comprises an indication of an internet protocol (“IP”) address of the UE.

18. The non-transitory computer-readable medium of claim 15, wherein the IMS emergency call comprises an authenticated IMS emergency call, wherein receiving the response comprises receiving a 200 OK response including a telephone (“TEL”) and/or a SIP uniform resource identifier (“URI”) for the UE, wherein performing the action comprises, responsive to receiving the 200 OK response, making the IMS emergency call, and wherein the SIP REGISTER request comprises an indication of an internet protocol (“IP”) address of the UE.

19. The non-transitory computer-readable medium of claim 18, wherein the 200 OK response includes the SIP URI for the UE, wherein the SIP URI is based on a mobile network code (“MNC”), a mobile country code (“MCC”), and global E.164 number conversion of a mobile subscriber integrated services digital network number (“MSISDN”), and wherein the SIP URI is of the form: “[E.164 number]@ims.mnc[MNC].mcc[MCC].3gppnetwork.org”

20. The non-transitory computer-readable medium of claim 15, wherein the UE is roaming on the IMS network, wherein the UE and the P-CSCF are part of the of a visited public land mobile network (“VPLMN”), and wherein the UE is separate and distinct from the P-CSCF.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0036] FIG. 1 is a signalling diagram according to an embodiment;

[0037] FIG. 2 is a signalling diagram according to a further embodiment;

[0038] FIG. 3 is a signalling diagram according to a yet further embodiment;

[0039] FIG. 4 is a flowchart of a method of operating a P-CSCF;

[0040] FIG. 5 is a flowchart of an alternative method of operating a P-CSCF;

[0041] FIG. 6 is a flowchart of a method of operating a PCRF;

[0042] FIG. 7 is a flowchart of a method of operating a UE;

[0043] FIG. 8 is a schematic diagram of a P-CSCF;

[0044] FIG. 9 is a schematic diagram of an alternative P-CSCF;

[0045] FIG. 10 is a schematic diagram of a PCRF; and,

[0046] FIG. 11 is a schematic diagram of a UE.

DETAILED DESCRIPTION

[0047] In order to provide the identity of a roaming UE making an emergency call to the PSAP where no SIP interconnect with the UE's HPLMN exists, methods are proposed below to use the IP address of the UE to identify the UE sufficiently for an authenticated IMS emergency call to take place. Each of these methods relies on the network being able to trust the IP address of the UE, and may therefore be improved by the use of an IP address verification procedure such as that disclosed in WO2013/091735.

[0048] While the methods are intended for use where no SIP interconnect exists between the HPLMN and the VPLMN, it will be appreciated that they could also be used where such a SIP interconnect exists, e.g. as a fallback to conventional methods in case communication with a node of the HPLMN fails.

[0049] A first method is shown in FIG. 1. This method relates to the case where the UE attempts to make an unauthenticated IMS emergency call.

[0050] The UE sends a SIP INVITE to the P-CSCF. The SIP INVITE is for an unauthenticated IMS emergency call (e.g. containing an SOS URN in the recipient field). The P-CSCF retrieves the IP address of the UE from the SIP INVITE (for example, the source IP of the IP packet carrying the SIP INVITE request). The PCSCF then sends an AAA request to the PCRF, including the IP address, indicating that the request relates to an emergency call, and requesting other identities for the UE.

[0051] The PCRF sends a resource allocation request (RAR) to the PGW, which reserves resources for the emergency call and sends a resource allocation answer (RAA) to the PCRF. The PCRF uses the IP address of the UE to look up other identities for the UE, for example the IMSI, IMEI, and MSISDN of the UE registered with the IP-CAN. The PCRF includes these identities in an AAA response to the P-CSCF.

[0052] The P-CSCF uses the received identities to create a TEL and/or SIP URI for the UE. The process of creating the SIP URI will be explained in more detail later. The P-CSCF then sends the SIP INVITE to the E-CSCF, adding the URI for the UE into the “P-asserted-identity” field and thus providing the asserted identity of subscriber at the UE. The E-CSCF then proceeds to handle the emergency call as in current standards.

[0053] In this way, the PSAP is provided with a TEL and/or SIP URI which can be used to contact the UE, even in the case where the UE makes an unauthenticated IMS emergency call.

[0054] In this case, there is little disadvantage to a UE making an unauthenticated emergency call rather than an authenticated emergency call, and so the UE may be configured to respond to a failed attempt at emergency registration by immediately making an unauthenticated emergency call. The error response sent by the P-CSCF when the registration fails may indicate that the UE should do this.

[0055] Signalling for the second method is shown in FIG. 2. This method relates to the case where the UE is performing an emergency registration in order to make an authenticated IMS emergency call.

[0056] The UE sends a SIP REGISTER request to the P-CSCF, indicating that it is an emergency registration. The P-CSCF determines that no home network is available for the UE, either because it is aware that no SIP interconnect exists for the UE's HPLMN, or following a failure to contact the S-CSCF of the UE's HPLMN. The P-CSCF retrieves the IP address of the UE from the SIP REGISTER (for example, the source IP of the IP packet carrying the SIP INVITE request). The PCSCF then sends an AAA request to the PCRF, including the IP address, indicating that the request relates to an emergency call, and requesting other identities for the UE.

[0057] The PCRF uses the IP address of the UE to look up other identities for the UE, for example the IMSI, IMEI, and MSISDN of the UE registered with the IP-CAN. The PCRF includes these identities in an AAA response to the P-CSCF.

[0058] The P-CSCF uses the received identities to create a TEL and/or SIP URI for the UE. The process of creating the URI will be explained in more detail later. The P-CSCF includes the URI in the P-associated-URI field of a 200 OK response sent to the UE in response to the SIP REGISTER.

[0059] In order for this method to work, the UE must accept the 200 OK response without receiving the 410 response which would normally precede it when registering with the IMS. Also, the UE should accept the 200 OK response without requiring authentication of the P-CSCF or that an IPSec secure association is set up, as both of these procedures require data that is held in the HPLMN. Given that this procedure is only to be used in an emergency, it is anticipated that the lack of security is acceptable in this case.

[0060] Once the UE has received the 200 OK response, it is registered with the IMS, and can make the emergency call as in current standards (except that as no IPSec secure association is set up, the signalling will not be encrypted under that association).

[0061] The signalling for the third method is shown in FIG. 3. The third method is similar to the second method, except that the registration is performed at the E-CSCF or S-CSCF of the VPLMN, rather than at the P-CSCF. After constructing the TEL and/or SIP URI, the P-CSCF sends the SIP REGISTER request to the E/S-CSCF, and includes the TEL and/or SIP URI for the UE (e.g. the IMSI, IMEI, and MSISDN). The E/S-CSCF sends a 200 OK message with P-Associated-URI fields containing the URIs received from the P-CSCF, to the UE via the P-CSCF. Alternatively, the P-CSCF may send the SIP REGISTER request to the E-CSCF prior to constructing the TEL and/or SIP URI, and the E-CSCF will return a 200 OK message without any user identity in the P-Associated-URI fields. The P-CSCF then constructs the TEL and/or SIP URI and inserts the TEL and/or SIP URI into the P-Associated-URI fields of the 200 OK response before sending the 200 OK response to the UE. As a further alternative, the P-CSCF may provide the other identities for the UE to the E-CSCF in the SIP REGISTER message, and the E-CSCF may construct the TEL and/or SIP URI and insert it into the P-Associated-URI fields of a 200 OK response sent to the UE via the P-CSCF. Depending on the identities of the UE received from the PCRF, a valid TEL or SIP URI may be constructed for the UE in a variety of ways.

[0062] As a first option, if the MSISDN and IMSI of the UE are available, the MNC and MCC codes can be extracted from the IMSI, and the MSISDN can be converted into a global E.164 number. This can be used to construct a SIP URI for the UE of the form “[E.164]@ims.mnc[MNC].mcc[MCC].3gppnetwork.org”. For example, if the MSISDN is 12125551212, and the IMSI is 234150999999999 then the SIP URI will be sip:+12125551212@ims.mnc015.mcc234.3gppnetwork.org;user=phone.

[0063] As a second option, if the MSISDN and the IMSI of the UE are available, the MNC and MCC codes can be extracted from the IMSI, and the MSISDN can be converted into a global E.164 number. The P-CSCF can then map the MNC and MCC codes onto a domain name using a mapping table which has previously been provided to the P-CSCF, and form a SIP URI using the global E.164 number and the domain name. For example, if the MSISDN is 12125551212, the IMSI is 234150999999999 and mapping table contains “ims.HPLMNoperator.com” for mnc==015 and mcc==234, then the SIP URI will be sip:+12125551212@ims.HPLMNoperatorcom;user=phone.

[0064] As a third option, if only the IMSI is available, the P-CSCF can create a temporary IMPU for the UE based on the IMSI, as described in 3GPP TS 23.003 v 13.1.0, subclause 13.4B. The temporary IMPU is a SIP URI constructed in the form “[IMSI]@ims.mnc[MNC].mcc[MCC].3gppnetwork.org”. For example, if the IMSI is 234150999999999, then the temporary IMPU will be sip:23415099999999@ ims.mnc015.mcc234.3gppnetwork.org.

[0065] A TEL URI may be constructed directly from the MSISDN.

[0066] Each of these options provides an identity which the PSAP can use to contact the UE if required, and which is sufficient to allow the UE to attach to the P-CSCF for the second or third methods presented above.

[0067] FIG. 4 is a flowchart showing a method of operating a P-CSCF. The P-CSCF receives (S101) a SIP INVITE request from the UE relating to an unauthenticated emergency call. The P-CSCF then determines (S102) an IP address of the UE, and sends (S103) an identity query to the PCRF indicating the IP address and requesting other identifiers for the UE. The P-CSCF receives (S104) one or more identifiers from the P-CSCF, and constructs (S105) a TEL and/or SIP URI for the UE on the basis of at least one of the identifiers. The P-CSCF then inserts (S106) the URI into the SIP INVITE request, and sends (S106) the SIP INVITE request to a PSAP.

[0068] FIG. 5 is a flowchart showing a method of operating a P-CSCF. The P-CSCF receives (S201) a SIP REGISTER request from the UE relating to an emergency registration. The P-CSCF determines (S202) an IP address of the UE and sends (S203) an identity query to the PCRF indicating the IP address and requesting other identifiers for the UE. The P-CSCF receives (S204) one or more identifiers from the PCRF, and obtains (S205) a TEL and/or SIP URI on the basis of at least one of the identifiers. The P-CSCF then sends (S206) a 200 OK response to the UE, including the TEL and/or SIP URI for the UE.

[0069] FIG. 6 is a flowchart showing a method of operating a PCRF for handling an emergency IMS call. The PCRF receives (S301) an identity request comprising an IP address for a UE from a P-CSCF. The PCRF maps (S302) the IP address of the UE to one or more other identifiers of the UE and sends (S303) the other identifiers to the P-CSCF.

[0070] FIG. 7 is a flowchart showing a method of operating a UE. The UE sends (S401) a SIP REGISTER request to the P-CSCF of a visited PLMN. In response, the UE receives (S402) an error response from the P-CSCF. The UE then sends (S403) a SIP INVITE request relating to an unauthenticated IMS emergency call to the P-CSCF.

[0071] FIG. 8 is a schematic diagram of an apparatus configured to operate as a P-CSCF (100). The apparatus comprises a first transceiver (101), a second transceiver (102), a third transceiver (103), and an unauthenticated emergency call processor (104). The first transceiver (101) is configured to communicate with a roaming UE. The second transceiver (102) is configured to communicate with a PCRF. The third transceiver (103) is configured to communicate with a PSAP. The unauthenticated emergency call processor (104) is configured to: [0072] receive, from the UE via the first transceiver, a session initiation protocol, SIP, INVITE request relating to an unauthenticated emergency call; [0073] determine an IP address of the UE; [0074] send an identity query to the PCRF via the second transceiver, indicating the IP address of the UE and requesting other identifiers of the UE; [0075] receive one or more other identifiers of the UE from the PCRF via the second transceiver; [0076] construct a TEL and/or SIP uniform resource identifier, URI, for the UE on the basis of at least one of the other identifiers; [0077] insert the URI into the SIP INVITE request;

[0078] send a second SIP INVITE request to the PSAP, via the third transceiver.

[0079] FIG. 9 is a schematic diagram of an apparatus configured to operate as a P-CSCF (200). The apparatus comprises a first transceiver (201), a second transceiver (202), and an emergency registration request processor (203). The first transceiver (201) is configured to communicate with a roaming UE. The second transceiver (202) is configured to communicate with a PCRF. The emergency registration request processor (203) is configured to: [0080] receive, from the UE via the first transceiver, a session initiation protocol, SIP, REGISTER request relating to an emergency registration; [0081] determine an IP address of the UE; [0082] send an identity query to the PCRF via the second transceiver, indicating the IP address of the UE and requesting other identifiers of the UE; [0083] receive one or more other identifiers of the UE from the PCRF via the second transceiver;

[0084] obtain a TEL and/or SIP uniform resource identifier, URI, for the UE on the basis of at least one of the other identifiers; [0085] send a 200 OK response to the UE in response to the SIP REGISTER request via the second transceiver, the 200 OK response including the URI.

[0086] FIG. 10 is a schematic diagram of an apparatus configured to operate as a PCRF (300). The apparatus comprises a transceiver (301) and an identity request processor (302). The transceiver (301) is configured to communicate with a P-CSCF. The identity request processor (302) is configured to: [0087] receive an identity request from the P-CSCF via the transceiver, the identity request comprising an IP address for a user equipment, UE; [0088] map the IP address of the UE to one or more other identifiers of the UE; [0089] send the other identifiers to the P-CSCF via the transceiver.

[0090] FIG. 11 is a schematic diagram of an apparatus configured to operate as a UE (400). The apparatus comprises a transceiver (401) and an emergency call processor (402). The transceiver (401) is configured to communicate with an IMS network comprising a P-CSCF, wherein the UE is roaming on the IMS network. The emergency call processor (402) is configured to: [0091] send a SIP REGISTER request relating to an emergency registration to the P-CSCF via the transceiver; [0092] receive an error response from the P-CSCF via the transceiver; [0093] send a SIP INVITE request relating to an unauthenticated emergency call to the P-CSCF via the transceiver.

[0094] The methods described above may be implemented by a computer program which, when run on an apparatus, causes the apparatus to perform the method.

[0095] Although the invention has been described in terms of preferred embodiments as set forth above, it should be understood that these embodiments are illustrative only and that the claims are not limited to those embodiments. Those skilled in the art will be able to make modifications and alternatives in view of the disclosure which are contemplated as falling within the scope of the appended claims. Each feature disclosed or illustrated in the present specification may be incorporated in the invention, whether alone or in any appropriate combination with any other feature disclosed or illustrated herein.