IMPLEMENTING GENERIC CELL GLOBAL IDENTITY FOR UNLICENSED MOBILE ACCESS

FIELD OF THE DISCLOSURE

The disclosures made herein relate generally to wireless telecommunications methodologies and systems and, more particularly, to implementing generic cell global identity for unlicensed mobile access.

BACKGROUND

Unlicensed Mobile Access (UMA) technology provides access to Global System for Mobile Communication (GSM) and General Packet Radio Service (GPRS) services over unlicensed spectrum technologies. Examples of such unlicensed spectrum technologies include, but are not limited to, Bluetooth wireless solutions and wireless fidelity (WiFi) wireless solutions. By deploying UMA technology, service providers allow wireless subscribers to roam and handover between cellular networks and unlicensed cellular networks using dual-mode mobile GSM/GPRS and UMA-enabled handsets, PDAs and the like. As such, UMA technology provides for wireless subscribers to engage in UMA network access sessions.

Billing options give a service provider flexibility to charge UMA usage in different patterns. By using Cell Global Identity (CGI) based billing solution, these patterns are reflected in UMA CGI and passed to a Mobile Services Switching Center (MSC) so that a billing system at the MSC will be able to apply the appropriate billing option for each usage pattern.

Standalone UMA network architecture, which is currently offered by Alcatel-Lucent, allows UMA functionality to be cost-effectively integrated into legacy core networks. In a standalone UMA network access session, UMA CGI needs to encapsulate both GSM location information as well as UMA billing information. However, for such a standalone UMA network implementation, there is no known solution for allowing UMA CGI to encapsulate both GSM location information and UMA billing information. Although it is known that two associated CGIs (i.e., UMA Registration CGI and UMA Billing CGI) can be used for encapsulating both GSM location information and UMA

billing information in next generation networks (NGNs), such a solution does not work with standalone UMA network architecture. For example, implementation of such a two- CGI solution can result in calls being rejected by a MSC handling such calls. Therefore, a solution for allowing both GSM location information and UMA billing information to be encapsulated during a standalone UMA network access session would be advantageous, desirable, and useful.

SUMMARY OF THE DISCLOSURE

Embodiments of the present invention allow both GSM location information and UMA billing information to be encapsulated during a standalone UMA network access session. More specifically, embodiments of the present invention provide for a one-CGI based UMA (i.e., UMA Generic CGI) in which there is a single UMA CGI having GSM location information and UMA billing information encapsulated therein. Such a single UMA CGI is used in UMA network access session processes such as, for example, Registration procedure, Location Update procedure and normal UMA calls. To this end, a single UMA CGI in accordance with the present invention is constructed by using a GSM Edge Radio Access Network (GERAN) CGI as the base and adding extra information relating to UMA billing information.

The objectives for a single UMA CGI in accordance with the present invention include providing alternative to existing two CGI approach (UMA Registration CGI and UMA Billing CGI) by using only one UMA CGI, being flexible enough to adapt to individual customer needs and specific network situations, and minimizing the impact for existing MSC and maintenance overhead involved. Furthermore, a single UMA CGI in accordance with the present invention is advantageous in that it preserves GERAN mobile location information, contains UMA billing option to facilitate billing in core networks, provides an uniform and consistent way to construct/use/share UMA CGI in all UMA network nodes (including the Mobile Station) Captures billing information and GSM location information in one CGI, reduces location updates thereby saving valuable bandwidth of MSC and HLR, allows law enforcement agencies and emergency centers track down on the MS, and supports billing system by providing a UMA billing category. In one embodiment of the present invention, a method for causing GSM location information and UMA billing information to be encapsulated in a single CGI structural element during a standalone UMA network access session comprises a plurality of operations. An operation is performed for providing a GERAN CGI structural element containing location information of a MS serving a subscriber device during a standalone UMA network access session. An operation is performed for manipulating the MS

location information for reducing an amount of MS location information holding space of the GERAN CGI structural element occupied by the MS location information such that a portion of the MS location information holding space becomes unused. An operation is performed for occupying at least a portion of the unused portion of the MS location information holding space with UMA billing information.

In another embodiment of the present invention, a method for causing GSM location information and UMA billing information to be encapsulated in a single CGI structural element during a standalone UMA network access session comprises a plurality of operations. An operation is provided for applying at least one algorithm to location information of a MS serving a subscriber device during a standalone UMA network access session for causing at least one of compressing, re-aligning and repackaging the MS location information whereby an amount of MS location information holding space of a GERAN CGI structural element occupied by the MS location information is reduced such that a portion of the MS location information holding space becomes unused. An operation is performed for inserting UMA billing information into at least a portion of the unused portion of the MS location information holding space.

In still another embodiment of the present invention, a server or gateway is capable of causing GSM location information and UMA billing information to be encapsulated in a single CGI structural element during a standalone UMA network access session. The server or gateway is configured for: (i) providing a GERAN CGI structural element containing location information of a Mobile Station (MS) serving a subscriber device during a standalone UMA network access session, (ii) manipulating the MS location information for reducing an amount of MS location information holding space of the GERAN CGI structural element occupied by the MS location information such that a portion of the MS location information holding space becomes unused, and (iii) occupying at least a portion of the unused portion of the MS location information holding space with UMA billing information.

These and other objects, embodiments, advantages and/or distinctions of the present invention will become readily apparent upon further review of the following specification, associated drawings and appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a method in accordance with an embodiment of the present invention, which causes GSM location information and UMA billing information to be encapsulated in a single CGI structural element during a standalone UMA network access session FIG. 2 shows a GERAN Location Area Identity (LAI) in accordance with the 3GPP TS 24.008 (i.e., 3 ^rd Generation Partnership Project Technical Specification 24.008) FIG. 3 shows a GERAN CGI structural element corresponding to the GERAN Location Area Identity (LAI) of FIG. 2.

FIG. 4 shows a single UMA CGI structural element in accordance with an embodiment of the present invention.

DETAILED DESCRIPTION OF THE DRAWING FIGURES

FIG. 1 shown a method 100 in accordance with an embodiment of the present invention. The method 100 causes GSM location information and UMA billing information to be encapsulated in a single CGI structural element during a standalone UMA network access session (i.e., also referred to herein as standalone UMA CGI functionality or as generic CGI). The method 100 accomplishes such encapsulation using a GERAN CGI as the base CGI structural element and adding extra information relating to UMA billing information to the GERAN CGI. The method 100 includes an operation 105 for providing a GERAN CGI structural element containing location information of a MS serving a subscriber device during a standalone UMA network access session. The MS location information includes Location Area Identification (LAI) information and Cell Identity (CID) information. In response to the GERAN CGI structural element being provided, an operation 110 is performed for manipulating the MS location information for reducing an amount of MS location information holding space of the GERAN CGI structural element occupied by the MS location information such that a portion of the MS location information holding space becomes unused. In one embodiment, the operation of manipulating the MS location information preferably includes applying at least one network- specific algorithm to the MS location information for causing the MS location information to the compressed, re-aligned and/or repackaged. After such manipulation is performed, an operation 115 is performed for occupying at least a portion of the unused portion of the MS location information holding space with UMA billing information. In one embodiment, the operation of occupying the unused portion of the holding space with UMA billing information preferably includes inserting the UMA billing information into at least a portion of the unused portion of the MS location information holding space. Thus, in view of the disclosure of the method 100, a skilled person will appreciate that a method for causing GSM location information and UMA billing information to be encapsulated in a single CGI structural element during a standalone UMA network access session can include an operation for applying at least one algorithm to location information of a Mobile Station (MS) serving a subscriber device during a standalone

UMA network access session for causing at least one of compressing, re-aligning and repackaging the MS location information whereby an amount of MS location information holding space of a GSM Edge Radio Access Network (GERAN) Cell Global Identity (CGI) structural element occupied by the MS location information is reduced such that a portion of the MS location information holding space becomes unused, and an operation for inserting UMA billing information into at least a portion of the unused portion of the MS location information holding space.

Furthermore, in view of the disclosures made herein, a skilled person will appreciate that a server or gateway can be configured for carrying out a method in accordance with an embodiment of the present invention. As such, such a server or gateway configured in accordance with the present invention will be capable of causing GSM location information and UMA billing information to be encapsulated in a single CGI structural element during a standalone UMA network access session. In order for single UMA CGI in accordance with the present invention to properly function in a network, various network entities can require certain modification from a conventional or standard structure. Many of these modifications are configuration changes such that no implementation logic will be affected. With respect to the MSC (Mobile Services Switching Center), for example, it may be necessary to configure UMA handover CGI and to configure emergency call routing for UMA CGI. With respect to the GGW (GPRS Gateway), for example, it may be necessary to configure each LUPS (Logical UNC Packet Switch) with a correct UMA RAI (Routing Area Identification). With respect to the UMA databases, for example, it may be necessary to configure correct database table / table entries to support UMA billing options. With respect to functionality required by LEAs (Law Enforcement Agencies), for example, it may be necessary to add capability to retrieve GSM CGI from UMA CGI. With respect to the backend office billing systems, for example, it may be necessary to add capability to retrieve billing options from UMA CGI.

Referring now to FIG. 2, a GERAN Location Area Identity (LAI) 200 in accordance with the 3GPP TS 24.008 (i.e., 3 ^rd Generation Partnership Project Technical Specification 24.008) is shown. The Location Area Identity (LAI) 200 includes MCC (Mobile Country Code) content, MNC (Mobile Network Code) content, and LAC (Location Area Code)

content. As shown in FIG. 3, a GERAN CGI structural element 300 is the concatenation of the LAI 200 (i.e., the MCC, MNC, and LAC content thereof) and the Cell Identity (CID). Referring to FIG. 4, a single UMA CGI structural element 400 in accordance with an embodiment of the present invention is shown. The UMA CGI structural element 400 is the CGI that, during a standalone UMA network access session, is returned to a corresponding mobile device returned in the URR Registration Accept message, sent to MSC during location update, and sent to MSC in a Complete Layer 3 message. The single UMA CGI 400 is based on the GERAN CGI structural element, 300 but with UMA billing information encapsulated therein. To add the UMA billing information to the GERAN CGI structural element 300, one or more algorithms to compress or realign/re-package GERAN MS location information (i.e., the LAI content) for created unused bits or bytes within the GERAN CGI structural element. UMA billing information is then inserted into these unused into these bits or bytes. In one embodiment, the one or more algorithms are tailored to customer-specific network configurations. Typically, a GERAN CGI structural element includes 7 bytes: 3 bytes for MCC/MNC, 2 for LAC, and 2 for CID. As can be seen in FIGS. 3 and 4, byte-wise, the GERAN CGI structural element 300 and the single UMA CGI 400 are the same size. With regard to generating UMA billing information, at registration time for a UMA session, an Unlicensed Network Controller (UNC) will assess information relating to billing for each mobile subscriber (MS). Examples of such assessed information include, but are not limited to, International Mobile Subscriber Identity (EVISI) information, GSM CGI information, Access Point (AP) information, UMA subscriber profile information, etc. In one specific instance of assess such information, UNC verifies the information provided by a MS against provisioned data in various UMA databases after which a billing option is derived and is ready for use by UNC-CS in main CGI construction phase. Each time a new billing option is defined, new UMA database tables may be needed and new processing logic in UNC is likely needed. Examples of such UMA databases include, but are not limited to, a UMA Access Point database, a UMA CGI database, a UMA Subscriber database, a UMA Zone database, a UMA Service Type database, and the like. To this end, in implementing standalone UMA CGI functionality in accordance with the present invention, an administrator entity will work with service

providers to define various UMA billing options for different usage patterns. After which, UMA databases will be appropriately provisioned and proper processing logic for billing options will be added to UNC.

Presented now are examples of algorithm structures configured for allowing UMA billing information to occupy all or some of an unused portion of MS location information holding space of a GERAN CGI. In view of these examples and the disclosures made herein, as skilled person may contemplate other algorithm structures suitably configured for allowing UMA billing information to occupy all or some of an unused portion of MS location information holding space of a GERAN CGI.

EXAMPLE 1

In this example, UMA CGI construction uses finite number of UMA LACs per logical UNC for billing purposes and uses UMA CID to encapsulate location information in GSM CGI. Specific aspects of algorithms providing for such UMA CGI construction include:

During UMA Registration time, UNC-CS acquires UMA billing option (from UMA DB procedures) and GSM CGI (if available).

UNC-CS performs the following:

If GSM LAI is available and is in UNC_AUTHORIZED_LAI_LIST (implies MCC/MNC option 1), use GSM MCC/MNC as UMA MCC/MNC, record NODEID (logical UNC) for the entry; use CGI_OPTION_NUMBER 0, NODEID in previous step and UMA billing option to search UNC_ONE_CGI_UMA_LAC table, use the resulting UMA LAC; if GsmCgiLacUsageMask is 0 (GSM CID is flat), use GSM CID as UMA CID; else if sum of used bits in GsmCgiLacUsageMask (assume n) and GsmCgiCidUsageMask (assume m) <= 16 (don't need mapping table), construct UMA CID as follows: put the n meaningful bits of GSM LAC in n MSBs of UMA CID and put the m meaningful bits of GSM CID in next m MSBs of UMA CID; else if sum of used bits in GsmCgiLacUsageMask and GsmCgiCidUsageMask > 16 (need mapping table), find UMA CID by looking up

UNC-ONE-CGLUMA-CID-MAPPING table using CGI_OPTION_NUMBER 0, GSM

MCC/MNC, GSM LAC and GSM CID; search UNC_ONE_CGI_RAC_M APPING table using GSM LAI and GSM RAC (if available) and obtain UMA RAC (Routing Area Code); and use UMA LAI and UMA RAC to find LUPS

Else if GSM LAI is available but not in UNC_AUTHORIZED_LAI_LIST (and

UmaOneCgiMccMncOption indicates option 2), location information in GSM

MCC/MNC needs to be preserved: randomly select NODEID (logical UNC), then find default UMA LAI for this logical UNC in UNC_AUTHORIZED_LAI_LIST, use UMA MCC and MNC from this default

UMA LAI; use CGI_OPTION_NUMBER 0, the NODEID number in previous step and UMA billing option to search UNC_ONE_CGI_UMA_LAC table, use the resulting UMA LAC; search UNC_ONE_CGI_RAC_M APPING table using the GSM LAI and GSM RAC (if available) and obtain UMA RAC; find UMA CID by looking up UNC_ONE_C GIJJM A_CID_M APPING table using

CGI_OPTION_NUMBER 0 and GSM CGI; and use UMA LAI and UMA RAC to find LUPS;

Else if GSM LAI is not available or GSM LAI is available but not in UNC_AUTHORIZED_LAI_LIST(and UmaOneCgiMccMncOption indicates option 1): randomly select NODEID (logical UNC), then find default UMA LAI for this logical

UNC in UNC_AUTHORIZED_LAI_LIST, use UMA MCC and MNC from this default

UMA LAI; use CGI_OPTION_NUMBER 0, the NODEID number in previous step and UMA billing option to search UNC_ONE_CGI_UMA_LAC table, use the resulting UMA LAC; search UNC_ONE_CGI_RAC_MAPPING table using this UMA LAI and GSM RAC (if available) and obtain UMA RAC; use UMA LAI and UMA RAC to find LUPS; if SgsnAcceptSameCgiFromTwoNse is 1, use the default UMA CID 0x0000 for this LUPS (billing is taken care of by UMA LAC); and

if SgsnAcceptSameCgiFromTwoNse is 0, construct default UMA CID by putting LUPS number in 5 LSB (Least Significant Byte) of an empty CID (0x0000).

EXAMPLE 2

In this example, UMA CGI construction uses fixed UMA LACs per logical UNC and uses UMA CID to encapsulate location information in GSM CGI as well as billing options. Specific aspects of algorithms providing for such UMA CGI construction include: During UMA Registration time, UNC-CS acquires UMA billing option (from UMA DB procedures) and GSM CGI (if available); and

UNC-CS performs the following:

If GSM LAI is available and is in UNC_AUTHORIZED_LAI_LIST (implies MCC/MNC option 1): use GSM MCC/MNC as UMA MCC/MNC, record NODEID (logical UNC) for the entry; use CGI_OPTION_NUMBER 1, the NODEID number in previous step to search

UNC_ONE_CGI_UMA_LAC table, use the resulting UMA LAC if sum of used bits in GsmCgiLacUsageMask (assume n), GsmCgiCidUsageMask (assume m) and Num_Billing_Bits (see Prepare Number of Billing Bits Needed, assume k) <= 16 (don't need mapping table), construct UMA CID as follows: put the n meaningful bits of GSM LAC in n MSBs of UMA CID; put the m meaningful bits of

GSM CID in next m MSBs of UMA CID; put billing option in k LSBs of UMA CID; else if sum of used bits in GsmCgiLacUsageMask, GsmCgiCidUsageMask and Num_Billing_Bits > 16 (need mapping table), find UMA CID by looking up

UNC-ONE-CGLUMA-CID-MAPPING table using CGI_OPTION_NUMBER 1, GSM

MCC/MNC, GSM LAC, GSM CID and billing option; search UNC_ONE_CGI_RAC_M APPING table using GSM LAI and GSM RAC (if available) and obtain UMA RAC; and use UMA LAI and UMA RAC to find LUPS ;

Else if GSM LAI is available but not in UNC_AUTHORIZED_LAI_LIST (and

UmaOneCgiMccMncOption indicates option 2), location information in GSM

MCC/MNC needs to be preserved:

Randomly select NODEID (logical UNC), then find default UMA LAI for this logical UNC in AUTHORIZED_LAI_LIST, use UMA MCC and MNC from this default UMA

LAI; use CGI_OPTION_NUMBER 1 and the NODEID number in previous step to search

UNC_ONE_CGI_UMA_LAC table, use the resulting UMA LAC; search UNC_ONE_CGI_RAC_MAPPING table using this GSM LAI and GSM RAC (if available) and obtain UMA RAC; find UMA CID by looking up UNC_ONE_C GIJJM A_CID_M APPING table using

CGI_OPTION_NUMBER 1, GSM CGI and billing option; use UMA LAI and UMA RAC to find LUPS

Else if GSM LAI is not available or GSM LAI is available but not in UNC_AUTHORIZED_LAI_LIST (and UmaOneCgiMccMncOption indicates option 1):

Randomly select NODEID (logical UNC), then find default UMA LAI for this logical

UNC in UNC_AUTHORIZED_LAI_LIST, use UMA MCC and MNC from this default

UMA LAI; use CGI_OPTION_NUMBER 1, the NODEID number in previous step to search UNC_ONE_CGI_UMA_LAC table, use the resulting UMA LAC ; search ONE_CGI_RAC_MAPPING table using this UMA LAI and GSM RAC (if available) and obtain UMA RAC; use UMA LAI and UMA RAC to find LUPS; if SgsnAcceptSameCgiFromTwoNse is 1, construct default UMA CID by putting billing option in Num_Billing_Bits LSB of an empty CID (OxOOOO), starting from the 6 ^th LSB ; and if SgsnAcceptSameCgiFromTwoNse is 0, construct default UMA CID by putting LUPS number in 5 LSB of an empty CID (0x0000), and billing option in next

Num_Billing_Bits LSB of the CID.

EXAMPLE 3

In this example, UMA CGI construction reuses GSM LAC as UMA LAC and uses UMA

CID to encapsulate location information in GSM CID as well as billing options. Specific aspects of algorithms providing for such UMA CGI construction include: During UMA Registration time, UNC-CS acquires UMA billing option (e.g., from UMA

DB procedures) and GSM CGI (i.e., if available); and

UNC-CS performs the following:

If GSM LAI is available and is in UNC_AUTHORIZED_LAI_LIST (implies MCC/MNC option 1): use GSM LAI as UMA LAI, record NODEID (logical UNC) for the entry; if sum of used bits in GsmCgiCidUsageMask (assume m) and Num_Billing_Bits

(Prepare number of billing bits needed, assume k) <= 16 (don't need mapping table), construct UMA CID as follows (since UMA LAC is equal to GSM LAC, UMA CID could not collide with existing UMA CID): copy the m meaningful bits of GSM CID to UMA CID and put billing option in k vacant bits of UMA CID (start from LSB); else if sum of used bits in GsmCgiCidUsageMask and Num_Billing_Bits > 16 (need mapping table), find UMA CID by looking up UNC.ONE.CGIJJMA.CID.MAPPING table using CGI_OPTION_NUMBER 2, GSM MCC/MNC, GSM CID and billing option; search UNC_ONE_CGI_RAC_M APPING table using GSM LAI and GSM RAC (if available) and obtain UMA RAC; and use UMA LAI and UMA RAC to find LUPS;

Else if GSM LAI is available but not in UNC_AUTHORIZED_LAI_LIST (and

UmaOneCgiMccMnc Option indicates option 2), location information in GSM

MCC/MNC needs to be preserved; Randomly select NODEID (logical UNC), then find default UMA LAI for this logical

UNC in UNC_AUTHORIZED_LAI_LIST, use this default UMA LAI; search UNC_ONE_CGI_RAC_M APPING table using the GSM LAI and GSM RAC (if available) and obtain UMA RAC; find UMA CID by looking up UNC_ONE_C GIJJM A_CID_M APPING table using CGI_OPTION_NUMBER 2, GSM CGI and billing option; and use UMA LAI and UMA RAC to find LUPS;

Else if GSM LAI is not available or If GSM LAI is available but not in UNC_AUTHORIZED_LAI_LIST (and UmaOneCgiMccMncOption indicates option 1); Randomly select NODEID (logical UNC), then find default UMA LAI for this logical UNC in UNC_AUTHORIZED_LAI_LIST, use this default UMA LAI; search UNC_ONE_CGI_RAC_MAPPING table using this UMA LAI and GSM RAC (if available) and obtain UMA RAC; use UMA LAI and UMA RAC to find LUPS; if SgsnAcceptSameCgiFromTwoNse is 1, construct default UMA CID by putting billing option in Num_Billing_Bits LSB of an empty CID (0x0000), starting from the 6 ^th LSB; and if SgsnAcceptSameCgiFromTwoNse is 0, construct default UMA CID by putting LUPS number in 5 LSB of an empty CID (0x0000), and billing option in next Num_Billing_Bits LSB of the CID.

Referring now to instructions processible by a data processing device, it will be understood from the disclosures made herein that methods, processes and/or operations adapted for carrying out standalone UMA CGI functionality as disclosed herein are tangibly embodied by computer readable medium having instructions thereon that are configured for carrying out such functionality. In one specific embodiment, the instructions are tangibly embodied for carrying out the method 100 of FIG. 1 and/or the CGI modifying functionality of FIGS. 2-4 disclosed above. The instructions may be accessible by one or more data processing devices from a memory apparatus (e.g. RAM, ROM, virtual memory, hard drive memory, etc), from an apparatus readable by a drive unit of a data processing system (e.g., a diskette, a compact disk, a tape cartridge, etc) or both. Accordingly, embodiments of computer readable medium in accordance with the present invention include a compact disk, a hard drive, RAM or other type of storage apparatus that has imaged thereon a computer program (i.e., instructions) adapted for carrying out standalone UMA CGI functionality in accordance with the present invention. In the preceding detailed description, reference has been made to the accompanying drawings that form a part hereof, and in which are shown by way of illustration specific embodiments in which the present invention may be practiced. These embodiments, and

certain variants thereof, have been described in sufficient detail to enable those skilled in the art to practice embodiments of the present invention. It is to be understood that other suitable embodiments may be utilized and that logical, mechanical, chemical and electrical changes may be made without departing from the spirit or scope of such inventive disclosures. To avoid unnecessary detail, the description omits certain information known to those skilled in the art. The preceding detailed description is, therefore, not intended to be limited to the specific forms set forth herein, but on the contrary, it is intended to cover such alternatives, modifications, and equivalents, as can be reasonably included within the spirit and scope of the appended claims.