This application is a reissue of U.S. Pat. No. 10,555,158, which issued on Feb. 4, 2020 and is entitled “Enhancements to Serving a User Equipment in a Visited Country in a Mobile Communication System, which was a National Phase Entry under 35 U.S.C. § 371 of International Application No. PCT/EP2017/050587, which has an International filing date of Jan. 12, 2017, which claims priority to European Patent Application No. 16305032.1, filed Jan. 14, 2016, the entire contents of each of which are hereby incorporated herein by reference in their entireties for all purposes.
Descriptions of mobile networks and systems can be found in the literature, such as in particular in Technical Specifications published by standardization bodies such as for example 3GPP (3rd Generation Partnership Project).
An example of 3GPP mobile system is EPS (Evolved Packet System). In a system such as EPS, a User Equipment UE has access to a an EPS network providing communication services (including providing IP connectivity). The EPS network comprises a Core Network called EPC (Evolved Packet Core) that can be accessed not only by 3GPP access, but also by non-3GPP access. A typical example of non-3GPP access, which will be considered more particularly in the following, is WLAN access.
WLAN access to EPC is specified in particular in 3GPP TS 23.402 and 3GPP TS 24.302. In the case of untrusted WLAN access, an IPsec tunnel is established between the UE and an evolved Packet Data Gateway ePDG, to ensure that the UE and the network can communicate in a secure way. The procedure for selection of an ePDG by the UE is specified in particular in 3GPP TS 23.402 and 3GPP TS 24.302.
It is important that an appropriate ePDG is selected for untrusted WLAN access to EPC. As recognized by the inventors and as will be explained with more detail later, the procedure for selection of an ePDG by the UE, as currently specified, needs to be improved.
In particular, there is a need to improve the selection of a ePDG in a country a User Equipment UE is located.
There is also a need to improve the determination of the local emergency numbers in a country a User Equipment UE is located.
More generally, there is a need for enhancements to serving a User Equipment UE in a visited country in a mobile communication system.
Embodiments of the present invention in particular address such needs.
The present invention generally relates to mobile communication networks and systems.
These and other objects are achieved, in one aspect, in some embodiments, by a User Equipment UE, configured to:
These and other objects are achieved, in another aspect, in some embodiments, by a User Equipment UE, configured to:
These and other objects are achieved, in another aspect, in some embodiments, by a User Equipment UE, configured to:
These and other objects are achieved, in another aspect, in some embodiments, by a DNS Server, configured to:
These and other objects are achieved, in another aspect, in some embodiments, by a DNS Server, configured to:
These and other objects are achieved, in another aspect, in some embodiments, by a DNS Server, configured to:
These and other objects are achieved, in another aspect, in some embodiments, by a method for selection of an evolved packet data gateway in a country a User Equipment UE is located, comprising at least one step performed by at least one of a thus configured UE or DNS server.
These and other objects are achieved, in another aspect, in some embodiments, by a DNS Server, configured to:
These and other objects are achieved, in another aspect, in some embodiments, by a P-CSCF, configured to:
These and other objects are achieved, in another aspect, in some embodiments, by a method for the determination of the local emergency numbers in a country a User Equipment UE is located, comprising at least one step performed by at least one of a thus configured P-CSCF or DNS server.
Some embodiments of apparatus and/or methods in accordance with embodiments of the present invention are now described, by way of example only, and with reference to the accompanying drawings, in which:
When a WLAN capable UE is attached via 3GPP access to a 3GPP RPLMN (HPLMN or VPLMN), it is specified according to TS 23.402 clause 4.5.4 (see version v13.4.0) that the UE selects an ePDG in that RPLMN or in its HPLMN.
When the UE is not attached via 3GPP access to a 3GPP PLMN, it is specified that the UE shall select an ePDG in the country it is located in by constructing a corresponding Operator Identifier FQDN (with MCC and MNC as specified in TS 23.003). But a condition is that the selected PLMN shall be in the “ePDG selection information” (see 4.5.4.4 bullet 2)a)), which does not include all the PLMNs that have roaming agreements for untrusted WLAN with the UE's HPLMN but only the mandatory and preferred PLMNs (i.e. the local PLMNs for which the HPLMN has decided it is mandatory or preferred that the UE selects an ePDG in that PLMN). That “ePDG selection information” has been previously provided to the UE by its HPLMN.
For Lawful Interception, local country regulation authorities may mandate that a UE in the country must select an ePDG in that country. In that case the algorithm to select an ePDG must remain independent from information from other countries. This includes not relying on the “ePDG selection information” because this information is provided by the HPLMN (and may contradict the requirement to select an ePDG in the visited country).
Another use case when the UE must select an ePDG in the same country it is located in is for emergency calls via WiFi when the UE is not attached to any 3GPP PLMN.
In some embodiments:
The UE is assumed to be able to determine the country it is located in. The idea is to enable a WLAN capable UE to get via new additional information in the ePDG selection information and/or via one or more DNS queries, a list of “local” PLMN's (i.e. PLMN's that are in the country the UE is located in) which have roaming agreements for untrusted WLAN access with the UE's HPLMN i.e. that own one or more ePDGs that can authenticate and authorize UE(s) from the HPLMN of the UE.
The DNS servers are public (accessible from anywhere on the Internet).
With the knowledge of local PLMN's having roaming agreements for untrusted WLAN access with the UE's HPLMN, the UE can attempt to establish an IPSec tunnel per TS 24.302 subclause 7.2.2 to an ePDG that is operated by one of these PLMN's.
Three alternatives, referred to as Alternative 1, Alternative 2, Alternative 3, may be distinguished.
Embodiments and/or aspects of the invention related to these different alternatives may be described in the following way.
One alternative is to extend the attributes of each PLMN in the ePDG selection info “mandatory, preferred” with “not preferred”. This allows knowing which PLMNs have roaming agreements with the UE's HPLMN.
In this alternative, either the UE already knows the list of MCCs of the country it is located in, or it needs to query a public DNS to get the full list of PLMNs (MCC and MNC) of the country. The corresponding DNS records are managed by a central administration.
The input is a FQDN which includes the MCC (or one of the MCCs) of the country the UE is located in. The output is the list of the identities of the PLMN's of the country (MCC and MNC). The Resource Record is a NAPTR record.
Then the UE attempts to establish an IPSec tunnel per TS 24.302 subclause 7to an ePDG that is operated by any PLMN in the above list only if the PLMN is configured in the ePDG selection Info.
This alternative implies dependence from the HPLMN because ePDG Selection Info is provided by the HPLMN, but it avoids a subsequent DNS query as in alternative 2. If—due to misconfiguration—a PLMN is not provided by the HPLMN in the ePDG selection info, the UE will just not attempt to select ePDG in that PLMN, but it does not harm because the UE will not attempt to select an ePDG in its HPLMN.
Similar to alternative 1 but the ePDG selection info is not enhanced with “not preferred”. In this case, the UE does not know all the roaming agreements since the ePDG selection info does not contain the “non-preferred PLMNs”.
The UE first queries a public DNS to get the list of local PLMNs (MCC and MNC) of the country exactly as in alternative 1 but even if it knows all the MCCs of the country.
There is a need for a second set of (DNS) queries to keep only the list of local PLMN's that have roaming agreements for untrusted WLAN access with the UE's HPLMN (so as to prune out the local PLMN that haven't such agreement within the list of PLMN retrieved by the first query of alternative 1).
This second set of queries corresponds to DNS queries targeting a FQDN which includes:
The output of the each DNS query on each local PLMN is
Another alternative is for the UE to directly query a DNS that returns the list of PLMNs which have a roaming agreement for untrusted WLAN with the UE's HPLMN.
The input of the DNS is a FQDN which includes:
The output of the DNS is a list of the identities (MCC and MNC) of the PLMNs of the country that have roaming agreements for untrusted WLAN access with the UE's HPLMN. That list can be ordered.
This feature is e.g. to be used
or for emergency calls via WLAN.
Embodiments and/or aspects of the invention related to these different alternatives may further be described in the following way.
When a WLAN capable UE can determine the country it is located in and either the UE is attempting to make an emergency call via WiFi or the UE has received instructions that in the country where it is currently camping it shall only use ePDG that are located in the country, and if the UE is not attached via 3GPP access to a 3GPP PLMN (or if the UE has failed to be served by an ePDG of the RPLMN that serves it over 3GPP access), the UE selects an ePDG in a PLMN in this country as follows:
As a first alternative:
3GPP TS 23.003 provides an informative annex D “Applicability and use of the “0.3gppnetwork.org” domain name” that can be used to construct a FQDN. A rule of this annex is that a DNS managed by an operator identified by mnc<MNC>.mcc<MCC> can be reached by an UE by using a FQDN with the form “<service_id>.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org”. Hence, a public DNS that is not managed by a specific operator should use another form.
As an example for that alternative, the input FQDN to be used for the DNS query would have the form “mcc<MCC>.local-plmn.pub.3gppnetwork.org”, the public DNS server returning a list of “mnc<MNC>.mcc<MCC>.local-plmn.pub.3gppnetwork.org” output FQDNs.
Note that in case multiple MCC values may correspond to the local country, the MCC value in an output FQDN could have a different value than the MCC value in the input FQDN.
An example of information used for ePDG selection by a UE, in embodiments related to the first alternative, is illustrated in
As a second alternative,
An example of information used for ePDG selection by a UE, in embodiments related to the second alternative, is illustrated in
As a third alternative, the UE selects an ePDG in a PLMN in the country it is located in as follows:
TS 23.003 provides an informative annex D “Applicability and use of the “0.3gppnetwork.org” domain name” that can be used to construct a FQDN. As an example, in that third alternative, the FQDN would have the form “hmnc<MNC>.hmcc<MCC>.mcc<MCC>.lcepdg.pub.3gppnetwork.org”, where the service is local country ePDG (lcepdg), the MCC of the country the UE is located in is mcc, and the UE's HPLMN is hmcc plus hmnc.
The DNS is configured with a list of local PLMN in the country identified by “mcc” the UE's HPLMN has WLAN roaming agreements with. Until successful IPSec tunnel establishment with an ePDG, for each of the local PLMN in the list:
As an implementation example for the third alternative, the UE fetches the NAPTR record associated with “hmnc<MNC>.hmcc<MCC>.mcc<MCC>.lcepdg.pub.3gppnetwork.org.” The DNS NAPTR information it gets is a set of NAPTR records:
The DNS resolver in the UE then needs to pick an Operator Identifier FQDN and issues a DNS lookup towards that new domain in order to find an ePDG of the corresponding local PLMN.
An example of information used for ePDG selection by a UE, in embodiments related to the third alternative, is illustrated in
For all alternatives, a fair usage of the PLMN (s) in the list can be achieved by the DNS providing the list of local PLMNs using NAPTR records having the same order and same preference (per RFC 34.03 definitions), and the DNS resolver in the UE randomly choosing between the PLMNs for which an IPSec tunnel establishment has not been successfully attempted. Another possibility is that the DNS provides a list of local PLMNs in a random or round robin order and that the UE always start with the first PLMN in the list.
Another need to fulfill is related with a P-CSCF (as defined in 3GPP 23.228) in a Home PLMN (HPLMN) that for IMS services needs to serve an UE located a Visited PLMN (VPLMN) of another country (this scenario is studied as part of S8 Home Routed studies in the FS_V8 SID documented in TR 23.749). In that case the P-CSCF in the HPLMN needs to determine whether session signaling initiated by the UE in the VPLMN targets an emergency number defined in that VPLMN (for example the emergency numbers related with child or women abuse may vary from country to country).
When the session signaling initiated by the UE in the VPLMN targets an emergency number defined in that VPLMN, the P-CSCF in HPLMN has to redirect the UE towards selecting a P-CSCF for emergency services in the VPLMN.
For the purpose of detecting whether session signaling initiated by the UE in the VPLMN targets an emergency number defined in that VPLMN, the P-CSCF could be locally configured with the list of emergency numbers associated with each country of a VPLMN with which it has roaming agreements.
This would be cumbersome to manage.
Another simpler solution would be where the P-CSCF takes the MCC of the VPLMN (where the UE is located) to build a specific FQDN associated with the emergency numbers in that country and issues a DNS record request to get the list of the emergency numbers in that country.
As another aspect of the invention, in some embodiments, the P-CSCF tries to get a list of local emergency numbers (i.e. a list of emergency numbers in the country the UE is located in) by performing a DNS query on an input FQDN containing “mcc<MCC>” (of the PLMN where the UE is camping) to a public NAPTR DNS server that returns a list of such emergency numbers; The domain of the input FQDN does not correspond to an individual operator as the corresponding DNS record is likely not to be managed by an individual operator (could be managed by GSMA like the NAPTR record of the public DNS server that returns a list of FQDN that each contains a “mnc<MNC>.mcc<MCC>” of a local PLMN).
The P-CSCF is not assumed to retrieve this list each time an UE registers or issues session related signaling as it may cache the DNS record received as part of DNS look-up
Various aspects and/or embodiments of the invention include (though not being limited to) following aspects and/or embodiments.
Some aspects are related to a User Equipment UE.
Various embodiments may be provided, including (though not being limited to) following embodiments, which may be taken alone or in combination, according to various combinations.
In an embodiment said UE is configured to:
In an embodiment said UE is configured to:
In an embodiment said UE is configured to:
In an embodiment said UE is configured to:
In an embodiment said UE is configured to:
In an embodiment, said UE is configured to:
In an embodiment, said UE is configured to:
In an embodiment, said UE is configured to:
In an embodiment, said UE is configured to:
In an embodiment, said UE is configured to:
In an embodiment, said UE is configured to:
In an embodiment, said UE is configured to:
In an embodiment, said UE is configured to:
In an embodiment, said UE is configured to:
In an embodiment, said UE is configured to:
Other aspects are related to DNS Server(s).
Various embodiments may be provided, including (though not being limited to) following embodiments, which may be taken alone or in combination, according to various combinations.
In an embodiment, a DNS Server is configured to:
In an embodiment, a DNS Server is configured to:
In an embodiment, a DNS Server is configured to:
In an embodiment, a DNS Server is configured to:
Other aspects are related to a method for selection of an evolved packet data gateway in a country a User Equipment UE is located, comprising at least one step performed by at least one of a thus configured UE or DNS server.
Other aspects are related to a DNS Server.
Various embodiments are provided, including:
In an embodiment, said DNS Server is configured to:
Other aspects are related to a P-CSCF.
Various embodiments are provided, including:
In an embodiment, said P-CSCF is configured to:
Other aspects are related to method for the determination of the local emergency numbers in a country a User Equipment UE is located, comprising at least one step performed by at least one of a thus configured P-CSCF or DNS server.
Referring now to
A person of skill in the art would readily recognize that steps of various above-described methods can be performed by programmed computers. Herein, some embodiments are also intended to cover program storage devices, e.g., digital data storage media, which are machine or computer readable and encode machine-executable or computer-executable programs of instructions, wherein said instructions perform some or all of the steps of said above-described methods. The program storage devices may be, e.g., digital memories, magnetic storage media such as a magnetic disks and magnetic tapes, hard drives, or optically readable digital data storage media. The embodiments are also intended to cover computers programmed to perform said steps of the above-described methods.
Number | Date | Country | Kind |
---|---|---|---|
16305032 | Jan 2016 | EP | regional |
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/EP2017/050587 | 1/12/2017 | WO |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2017/121812 | 7/20/2017 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
8706084 | Qiang | Apr 2014 | B2 |
9867098 | Kwok | Jan 2018 | B2 |
20070213050 | Jiang | Sep 2007 | A1 |
20080186903 | Hedberg et al. | Aug 2008 | A1 |
20090156253 | Shi et al. | Jun 2009 | A1 |
20100054222 | Rune | Mar 2010 | A1 |
20110261787 | Bachmann et al. | Oct 2011 | A1 |
20120260927 | Liu | Oct 2012 | A1 |
20120322412 | Qiang | Dec 2012 | A1 |
20120322413 | Haddad et al. | Dec 2012 | A1 |
20140079049 | Friman et al. | Mar 2014 | A1 |
20140153559 | Roeland | Jun 2014 | A1 |
20140366898 | Monsees et al. | Dec 2014 | A1 |
20150334644 | Kim et al. | Nov 2015 | A1 |
20160295386 | Faccin | Oct 2016 | A1 |
20170005914 | Edge | Jan 2017 | A1 |
20170188398 | Youn | Jun 2017 | A1 |
20180091967 | Gupta | Mar 2018 | A1 |
Number | Date | Country |
---|---|---|
101622895 | Jan 2010 | CN |
102752830 | Oct 2012 | CN |
102960031 | Mar 2013 | CN |
107637160 | Jan 2018 | CN |
2 194 686 | Jun 2010 | EP |
2012510755 | May 2012 | JP |
2317646 | Feb 2008 | RU |
2375846 | Dec 2009 | RU |
WO 2007016447 | Feb 2007 | WO |
WO 2007016447 | Feb 2007 | WO |
WO-2012096603 | Jul 2012 | WO |
WO-2012168146 | Dec 2012 | WO |
WO 2014129794 | Aug 2014 | WO |
WO-2015003125 | Jan 2015 | WO |
WO 2016161404 | Oct 2016 | WO |
WO 2016161404 | Oct 2016 | WO |
Entry |
---|
Office Action for Philippine Application No. 1/2018/501513 dated May 6, 2022, 4 pages. |
Notice of Allowance for Indonesian Application No. PID201805197 dated Jan. 21, 2022, 4 pages. |
3GPP TS 23.003 V13.4.0, 3rd Generation Partnership Project; Technical Group Core Network and Terminals; Numbering, addressing and identification (Release 13), 3GPP TS 23.003 V13.4.0, Dec. 17, 2015, 19.4.2.9 Section, 100 pages. |
3GPP TS 24.234 V12.2.0, 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 3GPP System to Wireless Local Area Network (WLAN) interworking; WLAN User Equipment (WLAN UED) to network protocols; Stage 3 (Release 12) (Mar. 2015) 40 pages. |
Additional ePDG selection considerations and corrections, 3GPP TSG-CT WG1395bis, C1-160125, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Jan. 6, 2016. |
Corrections to ePDG selection procedure, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, S2-154188 (Nov. 2015), 5 pages. |
Discussion on ePDG selection in support of Lawful Interception, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Verizon (C1-154346) Nov. 2015) 3 pages. |
ePDG selection enhancements related to LI requirements, S2-160185, Alcatel-Lucent, 3GPP TSG-SA WG2#113 S2-160185, Jan. 19, 2016, 4 pages. |
ePDG Selection, C1-151936, 3GPP TSG CT WG1 Meeting #92, Qualcomm Incorporated (May 2015), 4 pages. |
LS on ePDG Selection Versus LI Requirements, TSG SA Meeting #SP-70, SP-150831 (Dec. 2015), 2 pages. |
Reply LS on ePDG Selection, C1-154059, SAE-LI, 3GPP TSG-CT WG1 Meeting #95 (Nov. 2015) 2 pages. |
Support For VPLMN Provided WLAN Service Providers, Research In Motion Ltd., UK, S2-132423 (Jul. 2013), 10 pages. |
Visiting network configuration for ePDG selection, C1-154347, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, 3GPP TSG-CT WG1 Meeting #95 (Nov. 2015) 9 pages. |
Office Action for Canadian Application No. 3,011,195 dated Apr. 15, 2019, 4 pages. |
Office Action for Canadian Application No. 3,011,195 dated Sep. 21, 2020, 3 pages. |
Office Action for Chinese Application No. 201780016502.5 dated May 29, 2020, including Search Report dated May 22, 2020, 11 pages. |
Decision to Grant for Chinese Application No. 201780016502.5 dated Jan. 25, 2021, 3 pages. |
Extended European Search Report for European Application No. 20169433.8 dated May 28, 2020, 10 pages. |
First Examination Report for Indian Application No. 201817030325 dated Apr. 30, 2020, 7 pages. |
Office Action for Indonesian Application No. PID 2018 05197 dated Aug. 9, 2019, 4 pages. |
Office Action for Indonesian Application No. PID201805197 dated Aug. 6, 2021, 4 pages. |
International Search Report for Application No. PCT/EP2017/050587 dated Jul. 14, 2017, 8 pages. |
Office Action for Japanese Application No. 2018-536780 dated Jun. 28, 2019, 6 pages. |
Search Report for Japanese Application No. 2018-536780 dated Jun. 20, 2019, 19 pages. |
Written Opinion for Japanese Application No. 2018-536780 dated Dec. 6, 2019, 6 pages. |
Decision to Grant for Japanese Application No. 2018-536780 dated Apr. 27, 2020, 5 pages. |
Office Action for Japanese Application No. 2020-118280 dated Sep. 21, 2021, 4 pages. |
Decision to Grant for Japanese Application No. 2020-118280 dated Apr. 19, 2022, 5 pages. |
Office Action for Malaysian Application No. PI 2018001284 dated Apr. 12, 2021, 3 pages. |
Office Action for Mexican Application No. MX/a/2018/008666 dated Feb. 27, 2020, 5 pages. |
Office Action for Philippine Application No. 1/2018/501513 dated Dec. 7, 2021, 4 pages. |
Decision to Grant for Russian Application No. 2018125956/08 dated Nov. 18, 2019, 11 pages. |
Decision to Grant and Search Report for Russian Application No. 2020101744/08 dated Sep. 18, 2020, 14 pages. |
Office action for Singapore Application No. 11201805984Q dated Dec. 20, 2019, 7 pages. |
Notice of Eligibility for Grant for Singapore Application No. 11201805984Q dated Dec. 28, 2020, 5 pages. |
Office Action for Singapore Application No. 10202102016W dated Apr. 27, 2022, 6 pages. |
Office Action for U.S. Appl. No. 16/069,746 dated Feb. 27, 2019. |
Notice of Allowance for U.S. Appl. No. 16/069,746 dated Sep. 20, 2019. |
Office Action for U.S. Appl. No. 16/718,968 dated Jan. 21, 2020. |
Notice of Allowance for U.S. Appl. No. 16/718,968 dated May 20, 2020. |
Notice of Allowance for U.S. Appl. No. 16/718,968 dated Aug. 11, 2020. |
Office Action for Vietnamese Application No. 1-2018-03359 dated Sep. 20, 2018, 2 pages. |
Office Action for Mexican Application No. MX/a/2021/001047 dated Feb. 16, 2022, 5 pages. |
Alcatel-Lucent et al., “FQDN for ePDG Selection (for non-emergency bearer services)”, 3GPP TSG CT4 Meeting #70bis, C4-151712, (Oct. 12-16, 2015), 3 pages. |
Extended European Search Report for European Application No. 22206196.2 dated Feb. 22, 2023, 10 pages. |
Hearing Notice for Indian Application No. 201817030325 dated Nov. 7, 2023, 2 pages. |
Notice of Allowance for Malaysia Application No. PI 2018001284 dated Sep. 5, 2023, 1 page. |
Notice of Allowance for Philippine Application No. Jan. 2018/501513 dated Sep. 13, 2022, 2 pages. |
Notice of Issuance for Mexico Application No. MX/a/2018/008666 dated Nov. 13, 2020, 6 pages. |
Notice of Issuance for Mexico Application No. MX/a/2021/001047 dated Aug. 22, 2022, 6 pages. |
Office Action for Brazil Application No. BR112018014343-0 dated Oct. 27, 2023, 8 pages. |
Office Action for Chinese Application No. 202110375601.0 dated Oct. 19, 2023, 10 pages. |
Rogers Communications, “ePDG Selection When UE Is Not Attached Via 3GPP Access”, 3GPP TSG-SA2 Meeting #112, S2-153826, (Nov. 16-20, 2015), 3 pages. |
U.S. Appl. No. 16/069,746, filed Jul. 12, 2018, U.S. Pat. No. 10,555,158, Patented. |
U.S. Appl. No. 16/718,968, filed Dec. 18, 2019, U.S. Pat. No. 10,848,950, Patented. |
Office Action for Brazilian Application No. BR112018014343-0 dated Feb. 19, 2024, 6 pages. |
Notice of Allowance for Vietnamese Application No. 1-2018-03359 dated Mar. 27, 2024, 2 pages. |
Office Action for Singapore Application No. 10202102016W dated Apr. 15, 2024, 4 pages. |
International Preliminary Report on Patentability and Written Opinion dated Jul. 17, 2018, issued in corresponding International Application No. PCT/EP2017/050587. |
Alcatel-Lucent et al; “Additional ePDG selection considerations and corrections”, 3GPP Draft; C1-160125, XP051049057. |
Alcatel-Lucent et al; “Visiting network configuration for ePDG selection”, 3GPP Draft; C1-154347, XP050997671. |
Schulzrinne Columbia U B Rosen Marconi H: “Emergency Services for Internet Telephony Systems; draft-schulzrinne-sipping-emergency-arch-00.txt”, Feb. 8, 2004, XP015035061. |
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on S8 Home Routing Architecture for VoLTE (Release 14)”, 3GPP Standard; 3GPP TR 23.749, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre ; 650, Route Des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, (Dec. 1, 2015), vol. SA WG2, No. 1.0.0, pp. 1-30, XP051046310 [YD] 19 * pp. 11, 12. |
Alcatel-Lucent et al, “How P-CSCF can detect emergency numbers in a VPLMN”, vol. SA WG2, No. Saint Kitts, KN; Jan. 25, 2016-Jan. 29, 2016, (Jan. 17, 2016), 3GPP Draft; S2-160120 S8HR EN in a VPLMN V0.0, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre ; 650, Route Des Lucioles; F-06921 Sophia-Antipolis Cedex ; France, URL: http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/SA2/Docs/, (Jan. 17, 2016), XP051059776 [XP] 18-20 * p. 1 *. |
Alcatel-Lucent et al, “ePDG selection enhancements for the support of Lawful Interception”, vol. SA WG2, No. Saint Kitts and Nevis, KN; Jan. 25, 2016-Jan. 29, 2016, (Jan. 19, 2016), 3GPP Draft; S2-160186-CR23402R13 EPDG Selection_V2, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre ; 650, Route Des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, URL: http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_113_St_Kitts/Docs/, (Jan. 19, 2016), XP051072088 [XP] 1-17. |
Office Action for European Application No. 16305032.1 dated May 21, 2019. |
Office Action for European Application No. 16305032.1 dated Jun. 25, 2018. |
Extended European Search Report for European Application No. 16305032.1 dated Oct. 19, 2016. |
Partial European Search Report for European Application No. 16305032.1 dated Jul. 8, 2016. |
Russian Office Action and Search Report dated Mar. 1, 2019 issued in corresponding Russian Application No. 2018125956/08(041056) (with translation). |
Decision of Intent to Grant European Application No. 16305032.1 dated Oct. 29, 2019. |
Number | Date | Country | |
---|---|---|---|
Parent | 16069746 | Jan 2017 | US |
Child | 17665081 | US |