This application is a 371 of PCT/EP2012/065970, filed Aug. 15, 2012, the disclosure of which is fully incorporated herein by reference.
The present invention relates to methods and apparatus for determining relationships in heterogeneous networks. More particularly, the invention relates to methods and apparatus for automatically determining when an area covered by an Access Point of a Wi-Fi Radio Access Network overlaps with a cell of a 3GPP RAN, such as a UTRAN or EUTRAN.
Data traffic in mobile telecommunications networks is continually increasing. Consequently, operators are employing heterogeneous access networks that utilise multiple radio access technologies (RATs) in order to provide greater capacity, particularly in high traffic areas and areas that otherwise have poor network coverage.
Typically, the radio access technologies utilised as part of these heterogeneous access networks include Universal Terrestrial Radio Access Network (UTRAN), Evolved UTRAN (EUTRAN), and Wi-Fi/WLAN (Wireless Local Area Network). In this regard, both the UMTS and LTE standards are defined by the 3rd Generation Partnership Project (3GPP), whilst the Wi-Fi/WLAN standards are defined by the Institute of Electrical and Electronics Engineers (IEEE). However, one problem that arises when attempting to make use of heterogeneous networks that combine both 3GPP RANs and Wi-Fi RANs/WLANs is that the network operator cannot easily establish how the coverage of the cells of a 3GPP RAN (i.e. provided by a Node B/eNode B) relates to the coverage provided by the Access Points (AP) of a Wi-Fi RAN/WLAN. For example,
It would therefore be desirable to provide a mechanism by which the relationships between the cells of a 3GPP RAN and the coverage area of the APs of a Wi-Fi RAN could be determined automatically. However, the 3GPP and Wi-Fi technologies are part of separate domains that use different management systems, different paradigms, different identities etc., such that there are no mechanisms that allow a 3GPP RAN and a Wi-Fi RAN to associate with one another in this way.
It is therefore an object of the present invention to provide methods and apparatus for automatically determining when an area covered by an Access Point (AP) of a Wi-Fi Radio Access Network (RAN) overlaps with a cell of a 3GPP RAN, such as a UTRAN or EUTRAN.
According to a first aspect there is provided a method of enabling automatic determination of when an area covered by an Access Point (AP) of a Wi-Fi Radio Access Network (RAN) overlaps with a cell of a 3GPP RAN. The method comprises, at an entity of the Wi-Fi RAN, obtaining a 3GPP identifier related to a user terminal that is attached to the Wi-Fi RAN and an identifier for an AP of the Wi-Fi RAN to which the terminal is attached. The entity then generates and sends a Location Service Request including the 3GPP identifier to a Location Services (LCS) Server associated with the 3GPP RAN, receiving a Location Service Response from the LCS Server that includes information identifying a cell of the 3GPP RAN in which the user terminal is located, and causes storage of an association between the identified Wi-Fi AP and the identified 3GPP cell.
The method may further comprise configuring the Wi-Fi entity to function as a LCS Client of the LCS Server.
The Location Service Request may indicate that an identifier of the 3GPP cell is required. The Location Service Response may include an identifier of the 3GPP cell.
The step of causing storage of an association between the identified Wi-Fi AP and the identified 3GPP cell may comprise storing the association at the entity of the Wi-Fi RAN. It may then be determined that the area covered by the Wi-Fi AP overlaps with the identified 3GPP cell if the number of stored associations between the identified Wi-Fi AP and the identified 3GPP cell exceeds a threshold. Alternatively, it may be determined that the area covered by the Wi-Fi AP overlaps with the identified 3GPP cell upon the generation and storage of an association between the identified Wi-Fi AP and the identified 3GPP cell.
The method may further comprise, at the Wi-Fi entity, recording an indication of the time at which an association is generated, and, if a further association between the Wi-Fi AP and the identified 3GPP cell is not generated within a specified time period, cancelling the association between the Wi-Fi AP and the identified 3GPP cell
The association between the identified Wi-Fi AP and the identified 3GPP cell may be stored in overlap information identifying one or more APs of the Wi-Fi RAN that may overlap with one or more cells of the 3GPP RAN.
Alternatively, the step of causing storage of an association between the identified Wi-Fi AP and the identified 3GPP cell may comprise sending the association for storage at a further entity.
The Wi-Fi entity may generate and send a Location Service Request upon receipt of a 3GPP identifier associated with the user terminal. The Wi-Fi entity may receive an attachment notification from a Wi-Fi Access Controller, the notification including the 3GPP identifier associated with the user terminal.
The Wi-Fi entity may be a Wi-Fi Access Controller. The Wi-Fi entity may then obtain the 3GPP identifier during authentication of the user terminal in the Wi-Fi RAN.
The 3GPP identifier may be an International Mobile Subscriber Identity (IMSI) associated with the user terminal. The user terminal may be authenticated using any one of Extensible Authentication Protocol Method for Global System for Mobile Communications Subscriber Identity Modules, EAP-SIM, and Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement, EAP-AKA.
According to a second aspect there is provided a method of operating a Location Services (LCS) Server associated with a 3GPP Radio Access Network (RAN). The method comprises receiving a Location Service Request from an LCS Client within a Wi-Fi RAN, the Location Service Request including a 3GPP identifier related to a user terminal. The method further comprises determining that the LCS Server should respond to the Location Service Request with location information identifying a cell of the 3GPP RAN in which the user terminal is located, obtaining location information identifying a cell of the 3GPP RAN, and generating and sending a Location Service Response to the LCS Client within the Wi-Fi RAN, the Location Service Response including the information identifying a cell of the 3GPP RAN.
The step of determining that the LCS Server should respond to the Location Service Request with location information identifying a cell of the 3GPP RAN may comprise determining that the Location Service Request includes an indication that the LCS Server should respond with location information identifying a cell of the 3GPP RAN.
Alternatively, the step of determining that the LCS Server should respond to the Location Service Request with location information identifying a cell of the 3GPP RAN may comprises obtaining an identifier for the LCS Client from the Location Service Request, and determining that the identified LCS Client requires location information identifying a cell of the 3GPP RAN.
According to a third aspect there is provided an entity of a Wi-Fi Radio Access Network (RAN) configured to enable automatic determination of when an area covered by an Access Point (AP) of the Wi-Fi RAN overlaps with a cell of a 3GPP RAN. The entity comprises:
The entity may be configured to function as a LCS Client of the LCS Server.
The processor may be configured to generate a Location Service Request that indicates that an identifier of a 3GPP cell is required. The receiver may be configured to receive a Location Service Response that includes an identifier of the 3GPP cell.
The entity may further comprise a memory configured to store the association between the identified Wi-Fi AP and the identified 3GPP cell, and the processor may be configured to cause storage of an association between the identified Wi-Fi AP and the identified 3GPP cell by storing the association in the memory. The processor is may be further configured to determine that the area covered by the Wi-Fi AP overlaps with the identified 3GPP cell if the number of stored associations between the identified Wi-Fi AP and the identified 3GPP cell exceeds a threshold. Alternatively, the processor may be further configured to determine that the area covered by the Wi-Fi AP overlaps with the identified 3GPP cell upon the storage of an association between the identified Wi-Fi AP and the identified 3GPP cell.
The processor may be further configured to record an indication of the time at which an association is generated, and to cancel the association between the Wi-Fi AP and the identified 3GPP cell if a further association between the Wi-Fi AP and the identified 3GPP cell is not generated within a specified time period.
The memory may be configured to store the association between the identified Wi-Fi AP and the identified 3GPP cell in overlap information identifying one or more APs of the Wi-Fi RAN that may overlap with one or more cells of the 3GPP RAN.
Alternatively, the processor may be configured to cause storage of an association between the identified Wi-Fi AP and the identified 3GPP cell by sending the association for storage at a further entity.
The processor may be configured to generate a Location Service Request upon receipt of a 3GPP identifier associated with the user terminal.
The receiver may be configured to receive an attachment notification from a Wi-Fi Access Controller, the notification including the 3GPP identifier associated with the user terminal.
Alternatively, the entity may be a Wi-Fi Access Controller. The receiver may then be configured to receive the 3GPP identifier during authentication of the user terminal in the Wi-Fi RAN. The processor may be further configured to authenticate the user terminal using any one of Extensible Authentication Protocol Method for Global System for Mobile Communications Subscriber Identity Modules (EAP-SIM) and Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA), such that the 3GPP identifier is an International Mobile Subscriber Identity (IMSI) associated with the user terminal.
According to a fourth aspect there is provided a Location Services (LCS) Server associated with a 3GPP Radio Access Network (RAN) and configured to provide location information to a Wi-Fi RAN. The LCS Server comprises:
The processor may be configured to determine that the LCS Server should respond to the Location Service Request with location information identifying a cell of the 3GPP RAN by determining that the Location Service Request includes an indication that the LCS Server should respond with location information identifying a cell of the 3GPP RAN.
Alternatively, the processor may be configured to determine that the LCS Server should respond to the Location Service Request with location information identifying a cell of the 3GPP RAN by obtaining an identifier for the LCS Client from the Location Service Request, and determining that the identified LCS Client requires location information identifying a cell of the 3GPP RAN.
Some embodiments of the present invention will now be described in detail with reference to the accompanying drawings, in which:
There will now be described a method of automatically determining when an area covered by an Access Point (AP) of a Wi-Fi Radio Access Network (RAN) overlaps with a cell of a 3GPP RAN, such as a UTRAN or EUTRAN. The method involves introducing a Location Services (LCS) Client into the Wi-Fi RAN, wherein an LCS Client is an entity defined by the 3GPP Location Service (LCS) specifications. In this regard, the 3GPP Location Service (LCS) specifications define the mechanisms that support 3GPP mobile location services, and an LCS Client is an entity that interacts with an LCS Server for the purpose of obtaining location information for a device/user terminal (e.g. a user equipment (UE) or station (STA).
The Wi-Fi entity implementing the LCS Client functionality is configured to obtain a 3GPP identifier associated with a user terminal that has associated with/is attached to the Wi-Fi RAN and an identifier for an AP of the Wi-Fi RAN to which the terminal is associated/attached. In this regard, a 3GPP identifier is an identifier that can be used by an LCS Server to identify the user terminal within the 3GPP RAN. For example, this 3GPP identifier could be the International Mobile Subscriber Identity (IMSI) associated with the user terminal. The Wi-Fi entity/LCS Client is further configured to generate and send a Location Service Request including the 3GPP identifier to a LCS Server associated with the 3GPP RAN, and to receive a Location Service Response from the LCS Server that includes location information identifying a cell of the 3GPP RAN in which the user terminal is located. This location information can therefore be used by the Wi-Fi entity/LCS Client to determine if the identified Wi-Fi AP and the identified 3GPP cell overlap. The Wi-Fi entity/LCS Client is yet further configured to create/generate and store an association between the identified Wi-Fi AP and the identified 3GPP cell, as a result of the Location Service Response.
The 3GPP identifier associated with the user terminal can be obtained during the authentication of the user terminal to the Wi-Fi RAN. For example, if the Wi-Fi entity implementing the LCS Client functionality is the Wi-Fi AC that also implements authentication for the Wi-Fi AP, then the Wi-Fi entity/LCS Client will receive an IMSI from the user terminal during the authentication process, provided that the user terminal is authenticated using either Extensible Authentication Protocol Method for Global System for Mobile Communications Subscriber Identity Modules, (EAP-SIM) or Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA). As an alternative example, if the LCS Client functionality is provided by a standalone Wi-Fi entity, then the Wi-Fi entity/LCS Client can be configured to receive a message from the Wi-Fi AC notifying the Wi-Fi entity/LCS Client that a user terminal has associated with/attached to a Wi-Fi AP and has been authenticated. This notification message can then include an identifier for the Wi-Fi AP and an IMSI associated with the user terminal.
The Wi-Fi entity/LCS Client can be configured to generate a Location Service Request that includes an explicit indication that an identifier for a 3GPP cell is required in the location information provided in the Location Service Response. Alternatively, the Location Service Request could merely identify the LCS Client that generated the Location Service Request, and the LCS Server could be configured to recognise that this LCS Client requires that an identifier for a 3GPP cell is provided in the location information provided in the Location Service Response. For example, the LCS Server could be configured with a list of LCS Clients that require the location information includes a 3GPP cell identifier.
Upon receipt of the Location Service Response, the Wi-Fi entity/LCS Client can use the location information included in the Location Service Response to determine if the area covered by the identified Wi-Fi AP overlaps with the identified 3GPP cell. To do so, the Wi-Fi entity/LCS Client generates and stores an association between the identified Wi-Fi AP and the 3GPP cell identified in the Location Service Response. The Wi-Fi entity/LCS Client can then be configured to use the stored associations to determine if the identified Wi-Fi AP overlaps with the identified 3GPP cell. For example, the Wi-Fi entity/LCS Client can be configured to determine that the area covered by the identified Wi-Fi AP overlaps with the identified 3GPP cell once a single association between the identified Wi-Fi AP and the identified 3GPP cell has been generated as a result of a Location Service Response. Alternatively, the Wi-Fi entity/LCS Client can be configured to only determine that the area covered by the identified Wi-Fi AP overlaps with the identified 3GPP cell once the number of associations between the identified Wi-Fi AP and the identified 3GPP cell exceeds a threshold. In this case, the requirement that the number of associations must exceed a threshold prevents the Wi-Fi entity/LCS Client from determining that there is an overlap as result of a spurious association (e.g. that could occur due to a change in the layout of the cells of the 3GPP RAN, or due to a change in the radio environment).
In addition, the Wi-Fi entity/LCS Client can be configured to record an indication of the time at which an association between an identified Wi-Fi AP and an identified 3GPP cell is generated. The Wi-Fi entity/LCS Client can be configured to cancel or delete this association if a further association between the identified Wi-Fi AP and the identified 3GPP cell is not generated within a specified time period. By way of example, if the Wi-Fi entity/LCS Client generates a first association following the receipt of a Location Service Response from an LCS Server, the Wi-Fi entity/LCS Client could be configured to cancel or delete that first association if a second association relating to the same Wi-Fi AP and 3GPP cell as the first association is not generated within an hour of the generation of the first association.
When the Wi-Fi entity/LCS Client determines that the area covered by a Wi-Fi AP overlaps with the a 3GPP cell, the Wi-Fi entity/LCS Client can be configured to store an association between the Wi-Fi AP and the 3GPP cell in overlap information. This overlap information therefore identifies one or more APs of the Wi-Fi RAN that may overlap with one or more cells of the 3GPP RAN, and can be used to relate the activity within the Wi-Fi RAN with that of the 3GPP RAN. For example, this overlap information could be distributed for use in performing load steering between the two RANs, or to correlate statistics between the two RANs. For example, this overlap information could be distributed to either or both of the Wi-Fi and 3GPP systems for use when implementing load steering or statistics correlation. Alternatively, this overlap information could be distributed to a functional entity that is capable of communicating with both the 3GPP RAN and the Wi-Fi RAN. For example, such a functional entity could be located in the Operational Support System (OSS) of the network provider.
In order to implement the methods described above the standards that are relevant to the provision of location services should be updated. For example, the 3GPP specifications defining the location services should be updated accordingly, and the Mobile Location Protocol (MLP), defined by the Open Mobile Alliance (OMA), could be extended so as to provide for the inclusion of the 3GPP cell identifier in the location information sent in the Location Service Response message. In addition, MLP could also be extended to provide for the inclusion of an indication/request in a Location Service Request that the location information should include information identifying the cell.
The methods and apparatus described above provide a relatively straightforward mechanism by which the relationships between the cells of a 3GPP RAN and the coverage area of the APs of a Wi-Fi RAN can be determined automatically.
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. 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. For example, in the illustrated example signalling flow diagrams described above, only those messages and headers that are of particular relevance are shown. Those skilled in the art will be aware those messages and headers that have not been included in this illustration. In addition, whilst the above described embodiments specifically relate to heterogeneous networks comprised of at least a 3GPP RAN and a Wi-Fi RAN, the principles of the methods described herein are equally applicable to heterogeneous networks that comprise other radio access technologies; such as cdmaOne and CDMA2000.
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/EP2012/065970 | 8/15/2012 | WO | 00 | 11/10/2015 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2014/026715 | 2/20/2014 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
6259923 | Lim | Jul 2001 | B1 |
7764660 | Verma | Jul 2010 | B2 |
7831216 | Yenney | Nov 2010 | B1 |
7899451 | Hu | Mar 2011 | B2 |
7962152 | Buerger | Jun 2011 | B2 |
8099109 | Altman | Jan 2012 | B2 |
8301161 | Li | Oct 2012 | B2 |
8379558 | Lohtia | Feb 2013 | B2 |
8478299 | Chatterjee | Jul 2013 | B2 |
8635335 | Raleigh | Jan 2014 | B2 |
8639266 | Zelinka | Jan 2014 | B2 |
8644818 | Okmyanskiy | Feb 2014 | B1 |
8660574 | Edge | Feb 2014 | B2 |
8676118 | Sheynblat | Mar 2014 | B2 |
8682350 | Altman | Mar 2014 | B2 |
8805401 | Kosolobov | Aug 2014 | B2 |
8983433 | Torres | Mar 2015 | B2 |
9031580 | Alizadeh-Shabdiz | May 2015 | B2 |
9143891 | Choi | Sep 2015 | B2 |
9143920 | Do | Sep 2015 | B2 |
9386408 | Edge | Jul 2016 | B2 |
9462412 | Ramachandran | Oct 2016 | B1 |
9510256 | Krishna | Nov 2016 | B2 |
9538496 | Sheynblat | Jan 2017 | B2 |
9585088 | Hanson | Feb 2017 | B2 |
20040033803 | Varonen | Feb 2004 | A1 |
20040203914 | Kall | Oct 2004 | A1 |
20040259546 | Balachandran | Dec 2004 | A1 |
20050232189 | Loushine | Oct 2005 | A1 |
20050239461 | Verma | Oct 2005 | A1 |
20050272424 | Gallagher | Dec 2005 | A1 |
20050272440 | Li | Dec 2005 | A1 |
20060094446 | Duan | May 2006 | A1 |
20060133319 | Kant | Jun 2006 | A1 |
20060245406 | Shim | Nov 2006 | A1 |
20070123215 | Wang | May 2007 | A1 |
20080076425 | Khetawat | Mar 2008 | A1 |
20080133336 | Altman | Jun 2008 | A1 |
20080139218 | Duan | Jun 2008 | A1 |
20080227468 | Niska | Sep 2008 | A1 |
20080248813 | Chatterjee | Oct 2008 | A1 |
20080293431 | Buerger | Nov 2008 | A1 |
20090023453 | Hu | Jan 2009 | A1 |
20090059829 | Bachmann | Mar 2009 | A1 |
20090075625 | Jackson | Mar 2009 | A1 |
20090253440 | Edge | Oct 2009 | A1 |
20090262733 | Olson | Oct 2009 | A1 |
20100046406 | Annamalai | Feb 2010 | A1 |
20100323700 | Bachmann | Dec 2010 | A1 |
20110051665 | Huang | Mar 2011 | A1 |
20110159862 | Jackson | Jun 2011 | A1 |
20110250903 | Huang | Oct 2011 | A1 |
20110250906 | Siomina | Oct 2011 | A1 |
20110320588 | Raleigh | Dec 2011 | A1 |
20120108258 | Li | May 2012 | A1 |
20120184288 | Kosolobov | Jul 2012 | A1 |
20120202517 | Edge | Aug 2012 | A1 |
20120220314 | Altman | Aug 2012 | A1 |
20120297055 | Raleigh | Nov 2012 | A9 |
20120322412 | Qiang | Dec 2012 | A1 |
20130077482 | Krishna | Mar 2013 | A1 |
20130115956 | Ewert | May 2013 | A1 |
20130252635 | Zheng | Sep 2013 | A1 |
20130281110 | Zelinka | Oct 2013 | A1 |
20140094142 | Torres | Apr 2014 | A1 |
20140141804 | Zelinka | May 2014 | A1 |
20140192643 | Kalapatapu | Jul 2014 | A1 |
20140206390 | Edge | Jul 2014 | A1 |
20140282883 | Chan | Sep 2014 | A1 |
20140335823 | Heredia | Nov 2014 | A1 |
20140364101 | Do | Dec 2014 | A1 |
20150023341 | Zhao | Jan 2015 | A1 |
20150117411 | Jeong | Apr 2015 | A1 |
20150133160 | Sheynblat | May 2015 | A1 |
20150163680 | Valliappan | Jun 2015 | A1 |
20150189557 | Touati | Jul 2015 | A1 |
20150195771 | Hurtta | Jul 2015 | A1 |
20150296478 | Rasanen | Oct 2015 | A1 |
20150334644 | Kim | Nov 2015 | A1 |
20150365790 | Edge | Dec 2015 | A1 |
20160069984 | Nylander | Mar 2016 | A1 |
20160094977 | Nylander | Mar 2016 | A1 |
20160105780 | Hooker | Apr 2016 | A1 |
20160205557 | Tuupola | Jul 2016 | A1 |
20160226886 | Steiner | Aug 2016 | A1 |
20160234726 | Nuggehalli | Aug 2016 | A1 |
20160258766 | Felemban | Sep 2016 | A1 |
20160261986 | Nord | Sep 2016 | A1 |
20160286357 | Edge | Sep 2016 | A1 |
20160316031 | Diem | Oct 2016 | A1 |
20170034650 | Shah | Feb 2017 | A1 |
20170078846 | Sheynblat | Mar 2017 | A1 |
Number | Date | Country |
---|---|---|
2007121331 | Oct 2007 | WO |
Entry |
---|
3GPP, TSG-SA # 16, Tdoc SP-020379, Cover Page for TR 23.871 v 2.1.0, Jun. 14, 2002. |
3GPP TS 23.032 V10.0.0; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Universal Geographical Area Description (GAD) (Release 10); Mar. 2011. |
3GPP TS 23.271 V10.2.0; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Functional stage 2 description of Location Services (LCS) (Release 10); Mar. 2011. |
Number | Date | Country | |
---|---|---|---|
20160069984 A1 | Mar 2016 | US |