Title of Invention	A METHOD FOR PROVIDING ACCESS TO A LOCAL RADIO ACCESS NETWORK
Abstract	Systems and methods for determining the home network carrier associated with a mobile station and authorizing the provision of services to the mobile station using centralized storage of mobile station and home network information. In one embodiment, when a roaming mobile station attempts to access services, identifying information for the mobile station is used by a local server to query a centralized DNS server that stores a mapping of mobile station identifying information to corresponding home networks. The centralized DNS server returns an identification of the home network of the roaming mobile user, and the home network then determines whether to grant or deny the mobile station access to the local network. The mobile station identifying information may comprise an MSID such as an MIN, IRM or IMSI, which may serve as part of the address for the query to the centralized DNS server.

Title of Invention

A METHOD FOR PROVIDING ACCESS TO A LOCAL RADIO ACCESS NETWORK

Abstract

Systems and methods for determining the home network carrier associated with a mobile station and authorizing the provision of services to the mobile station using centralized storage of mobile station and home network information. In one embodiment, when a roaming mobile station attempts to access services, identifying information for the mobile station is used by a local server to query a centralized DNS server that stores a mapping of mobile station identifying information to corresponding home networks. The centralized DNS server returns an identification of the home network of the roaming mobile user, and the home network then determines whether to grant or deny the mobile station access to the local network. The mobile station identifying information may comprise an MSID such as an MIN, IRM or IMSI, which may serve as part of the address for the query to the centralized DNS server.

Full Text	SYSTEMS AND METHODS FOR HOME CARRIER DETERMINATION USING A CENTRALIZED SERVER Claim of Priority under 35 U.S.C §119 [0001] The present Application for Patent claims priority to Provisional Application No. 60/503,194 entitled "Using the DNS for Home Carrier Determination Based on the MSE> Prefix'* filed September 15, 2003, assigned to the assignee hereof and hereby expressly incorporated by reference herein. > BACKGROUND Field [0002] The present invention relates generally to wireless communication systems, and more specifically to a method for determining the home network carrier of a roaming mobile station that is attempting to access a local network. Background [0003] As the proliferation of wireless devices increases, mobile users often find themselves requesting services from service providers other than their home network providers, i.e. home network carriers. The industry has kept up with this situation by putting in place roaming agreements to provide mobile users with services while outside of their home areas. The local networks then each maintain information (e.g., in look-up tables) that can be used to identify which home networks are associated with roaming users, and which home networks are covered by the different roaming agreements. [0004] When mobile users need service in areas outside the limits of their home networks, they contact a local network to request service. The request often includes a user name and password that is provided by the home network. This user name and password may, for example, be a publicly available user name that is common to many, if not all, users within the same home network carrier. Upon receiving the request from the mobile user, the local network uses its locally stored information to determine which of the home networks is associated with the user and whether, based on that association, the user should be granted the requested services. This may include checking the user name and password in the user's request for service against the authorization information stored with the home network's information. [0005] This arrangement necessities not only the initial expense of setting up the local storage of the information for all of the home networks, but also the recurring expense of maintaining the information in each of the local networks. For instance, when the information associated with carrier A changes (e.g., the status of roaming agreements, user names, passwords, etc.,) this information must be updated in each of the local networks, in case a user associated with network A roams in an area associated with one of the local networks. Delays or errors in the process of updating the network information can cause denials of service to mobile users that otherwise should have been granted access to the local network. This results in frustrated mobile users and lost revenue for both the local network carrier and the home network carrier. [0006] It is clear that the difficulties of maintaining the same home network information in each of the local networks are made worse by scaling. If there are more home networks, there is more information that has to be maintained at each local network. If there are more local networks, the difficulties of keeping the information in all of the local networks are exacerbated. (It may be noted that a given network may be considered a local network or a home network, depending upon the association of the respective networks with particular mobile users.) [0007] There is therefore a need in the art for systems and methods for authorizing access by roaming mobile users to a local network that does not suffer from the drawbacks of conventional systems and methods. SUMMARY [0008] Embodiments disclosed herein address the above stated needs by providing systems and methods for determining the home network carrier associated with a mobile station and authorizing the provision of services to the mobile station. Broadly speaking, this is accomplished by centralizing the home network information that is conventionally stored in each of the local networks. The local networks then access the centrally stored information, rather than accessing the locally stored and maintained information, in order to authorize access by roaming users to local services. [0009] One embodiment comprises a method implemented in a local server, such as a RADIUS server or VLR. The method includes receiving a request by a mobile station for roaming access to a local network, accessing a remote centralized server to identify the home network associated with the mobile station, and granting or denying access by the mobile station to the local network based at least in part upon which home network is associated with the mobile station. [0010] Another embodiment comprises a method implemented in a centralized server such as a DNS server, wherein the method includes maintaining a central database containing information associating home networks with mobile stations, coupling the central database to several local servers, receiving a query from one of the local servers identifying a first mobile station that wishes to access a local network associated with the local server, and identifying a home network associated with the first mobile station. [0011] Another embodiment comprises a local server associated with a local network. The local server is configured to receive a request by a mobile station for roaming access to the local network, access a remote centralized server to determine which home network is associated with the mobile station, and grant or deny access by the mobile station to the local network based upon the identity of the home network associated with the mobile station. [0012] Yet another embodiment comprises a central server configured to maintain a central database with information mapping home networks to mobile stations, receive queries from local servers, where the queries include information identifying the mobile stations requesting access to the local networks associated with the corresponding local servers, and identify home networks associated with the mobile stations identified in the queries. [0013] Numerous additional alternative embodiments are also possible. BRIEF DESCRIPTION OF THE DRAWINGS [0014] Various aspects and features of the invention are disclosed by the following detailed description and the references to the accompanying drawings, wherein: [0015] FIG. 1 is a schematic diagram of a prior art wireless local network; [0016] HG. 2 is a schematic diagram of a local wireless network in communication with a remote centralized server of one embodiment of the present invention; [0017] FIG. 3 is a schematic diagram of a local wireless network in communication with a remote centralized server of an alternate embodiment of the present invention; [0018] FIG. 4A-4D is a schematic diagram of data bit array captured from a mobile station ID used to construct a query for the remote centralized server of one embodiment of the present invention; and [0019] FIG. 5 is a schematic diagram of a plurality of local carriers in communication with the remote centralized server of one embodiment of the present invention. [0020] While the invention is subject to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and the accompanying detailed description. It should be understood, however, that the drawings and detailed description are not intended to limit the invention to the particular embodiments which are described. DETAILED DESCRIPTION [0021] One or more embodiments of the invention are described below. It should be noted that these and any other embodiments described below are exemplary and are intended to be illustrative of the invention rather than limiting. [0022] As described herein, various embodiments of the invention comprise systems and methods for determining the home network carrier associated with a mobile station and authorizing the provision of services to the mobile station. Broadly speaking, this is accomplished by centralizing the home network information that is conventionally stored in each of the local networks. The local networks then access the centrally stored information, rather than accessing the locally stored and maintained iirformation, in order to authorize access by roaming users to local services. [0023] In one embodiment, a roaming mobile user attempts to access local services (e.g., internet access) by communicating with a packet data serving node via a radio access network (e.g., a CDMA wireless communication system.) The packet data serving node communicates a request to an authentication server to obtain authorization to provide the requested services to the roaming user. The mobile user's request for services includes information identifying the user's mobile device. This identifying information is communicated to the authentication server, which queries a remote centralized server to determine the home network associated with the mobile user. The remote centralized server returns a response that identifies the user's home network (e.g., a home network carrier domain name.) This home network information is then used by the authentication server to determine whether the mobile user should be granted access to the requested services. [0024] Referring to FIGURE 1, a schematic diagram of a roaming wireless mobile station in communication with a prior art local network system is shown. In this conventional system, a user of mobile station 110, while roaming, may wish to access the local network to obtain service (e.g., internet access.) Mobile station 110 communicates via radio access network (RAN) 115 to establish a communication link with a packet data service node (PDSN) 130. Once the communication link has been established, a username/password 120 is communicated to PDSN 130 using a password authentication protocol (PAP.) This is done so that the user can be authenticated by PDSN 130 prior to providing services to mobile station 110. [0025] PDSN 130 generates a remote authentication dial-in user service (RADIUS) request 140 and forwards the request to local RADIUS server 150, which authenticates the username/password. The local RADIUS server 150 includes a database 155. Database 155 stores information on those home networks for which roaming users may attempt to access services via the local network. This information normally includes tables or other information for identifying the home networks associated with roaming mobile stations that have requested access to the local network. [0026] After local RADIUS server 150 has determined with which home network mobile station 110 is associated, it can be determined whether or not mobile station 110 should be given access to the requested services. This is done by comparing the username/password provided by mobile station 110 to a username/password associated with the home network. The home network's username/password may be stored in RADIUS server 150, or RADIUS server 150 can formulate a query and forward the query to a home RADIUS server (not shown) associated with the home network of mobile station 110. [0027] Based on the comparison of usernames/passwords, RADIUS server 150 authenticates mobile station 110. Whether the username/password is authenticated by the local RADIUS server 150 or the home RADIUS server, a RADIUS access accept message 160 is then forwarded to PDSN 130. PDSN 130, in response to the RADIUS access accept message, forwards a PAP acknowledgement 170 to mobile station 110. Mobile station 110 is then allowed access to the requested services. [0028] During the above described process, a failure at the PPP level or a delay in response from PDSN 130, local RADIUS server 150 or the home RADIUS server will result in a denial of service for mobile station 110. [0029] The prior art, as described above, requires that each local RADIUS server 150 maintain a database (or some other data structure) containing information for numerous other networks, particularly for every other carrier with which the local network is partnered. As pointed out above, this arrangement is expensive in terms of additional overhead, maintenance of both the equipment and the data contained within the database, and so on. [0030] It may be useful before proceeding to describe the various embodiments of the invention to define a number of terms. These terms include: BS — base station; CDG - CDMA Development Group; CDMA - code division multiple access; DNS - domain name system; HLR — home locator register; IMSI - international mobile subscriber identity; IRM — international roaming MIN; MIN - mobile identification number; MS — mobile station; MSC — mobile switching center; MSID -- mobile station ID; PAP — password authentication protocol; PDSN - packet data serving node; RADIUS — remote authentication dial-in user service; RAN - radio access network; VLR — visitor locator register. [0031] It should be noted that mobile stations may include any wireless device capable of accessing the radio access network, such as a personal digital assistant (PDA,) notebook computer, cellular telephone, 2-way communication devices, pager or the like (this list is intended to be exemplary and not exhaustive). A person of ordinary skill in the art will appreciate and understand that many other devices can access the RAN or be adapted to access the RAN and still fall within the scope and teachings of the several embodiments of the present invention. Furthermore, the type of system in which the MS operates is not limited, and may include CDMA, TDMA, GSM or other types of wireless communication systems. [0032] Service or services that may be requested by the mobile station may include either voice or data packet type services, such as but not limited to voice transmissions, voice mail, e-mail, text messaging, instant messaging, internet access, telephony, streaming audio, streaming video, online games, Internet radio and so on. [0033] Referring to FIGURE 2, a schematic diagram of a roaming wireless mobile station in communication with a local network system in accordance with one embodiment of the invention is shown. The reader should note that reference numerals, 110, 115,120,130, 140, 150,160 and 170 correspond to the identically numbered items in Fig. 1. [0034] In this embodiment, MS 110 again communicates with PDSN 130 via RAN 115. PDSN 130, in turn, communicates with local RADIUS server 150. At this point, the configuration of the system begins to diverge from the system of FIGURE 1. Rather than having a local database in which the home network information is stored, local RADIUS server 150 is coupled to a remote, centralized server that stores this information. When the information is needed by local RADIUS server 150, a request is sent to the remote, centralized server, which then responds with the information. In FIGURE 2, the remote, centralized server consists of CDG DNS server 250. Local RADIUS server 150 is coupled to the CDG DNS server 250 through a local DNS server 220 and the normal internet DNS hierarchy 240. [0035] In one embodiment, the home network information stored by the remote, centralized server consists of a mapping from the MSID prefix of a MS (which is requesting access to the local network's services) to the MS's home network name. The RADIUS 150 server utilizes the Mobile Station ID (MSID), which can be a Mobile Identification Number (MIN), International Roaming MIN (IRM), or International Mobile Subscriber Identity (IMSI), to determine the MS's home network for voice services. For example, the first six digits of a MIN can be mapped to a carrier name. In the embodiment of FIGURE 2, the MSBD-to-home-network mapping table is stored and maintained centrally in a DNS server under the authority of a single organization. [00361 It should be noted that the remote, centralized server need not consist of a single server or database, but can be a distributed database or server system, depending on the size and the needs of the system. For instance, the remote centralized database can be mirrored to multiple primary or secondary sites to provide back-up capacity, server redundancy, or increased performance in the event that a primary server fails or has reduced performance due to high traffic conditions. It is anticipated that the remote centralized server (e.g. CDG DNS server) will consist of less than the number of local RADIUS servers that access the home network information. [0037] It should also be noted that, although the centrally maintained server depicted in FIGURE 2 is under the authority of CDG (the CDMA Development Group,) this need not be the case in other embodiments. The central server may be maintained by other entities that may include standards organizations within the industry, commercial enteiprises, non-profit organizations, or even individuals. References herein to CDG (e.g., "CDG DNS server" and "cdg.org") should therefore be construed broadly to refer to any such entity that maintains a central server or server system in accordance with the present disclosure. [0038] References to other terms in the present disclosure should also be construed broadly, unless otherwise specified herein. For example, references to "PAP" should be construed to teach the use of any suitable authentication protocol (e.g., PAP, CHAP, etc.,) rather than a single, specific protocol. Similarly, references to "RADIUS" servers should be construed to cover various different types of remote or roaming access (e.g., VLR) severs, and references to "MSID" should be construed to cover various types of identifying information corresponding to the described roaming devices. [0039] In one embodiment, the roaming MS 110 desires Internet access and sends the publicly available username and password (provided to the MS by its home network) via PAP to the local serving network for authorization. The MSID for MS 110 is communicated to the PDSN 130 when a connection is established between the MS 110 and the PDSN 130. The PDSN 130 sends RADIUS Access-Request 140 to the local RADIUS server 150. The RADIUS Access-Request 140 contains the MS's username, password, and MSID. [0040] The local RADIUS server 150 sends a DNS Query 210 to a local DNS server 220. In this embodiment, the local DNS server 220 is a generic server utilized simply to manage connections and transmissions to and from the internet DNS hierarchy 240. Local DNS server 220 transmits DNS Query 230 to Internet DNS hierarchy 240 which provides links to CDG DNS server 250. The DNS query 230 is forwarded to the DNS server 250, which, in this case, is maintained by CDG. [0041] If the DNS server 250 has the mapping from the MSID prefix to a home network's domrin name, the DNS server 250 returns a DNS Response 260 containing the home network's domain name. In some embodiments, the local RADIUS and DNS servers may cache the MSEMo-home-network mapping provided via the DNS Response. The caching of this information may enable the system to more quickly determine whether or not to authorize future access requests by eliminating the time required for the DNS query and response. The caching of the home network information may be retained and discarded in accordance with any suitable caching policy. [0042] Upon receiving the DNS Response, the local RADIUS server 150 can determine whether or not to authorize access by the MS 110 in several ways. For instance, in one embodiment, local RADIUS server 150 compares the home network identified in the DNS Response with a set of locally stored roaming agreements. Each of the roaming agreements identifies a corresponding home network with which the local serving network has an agreement to provide roaming services. If the home network identified in the DNS Response is included among the home networks with which the local serving network has roaming agreements, then the local RADIUS server will authorize the MS to access requested services in accordance with the respective roaming agreement. The roaming agreements may authorize access by all users associated with the respective home network, or they may require that appropriate usernames/passwords be provided by the users. If appropriate, the local RADIUS server 150 sends the RADIUS Access-Accept 160 to the PDSN 130, which then sends the PAP Acknowledgement to the MS 110. [0043] In another embodiment, rather than comparing the home network identified in the DNS Response with the home networks for which there are roaming agreements, the local RADIUS server can simply contact a RADIUS server for the home network. If the RADIUS server for the home network approves authorization; of the access requested by the MS, a corresponding response will be provided to the local RADIUS server. The local RADIUS server will then authorize the requested access by the MS. [0044] It should be noted that these two methods for determining, based on the identification of the home network associated with the MS, whether to grant access to the MS can also be combined in other embodiments. In one possible embodiment, after receiving the DNS Response from the CDG DNS server, the local RADIUS server may attempt one method, and then the other. For example, the local RADIUS server may first determine whether the home network is included among the networks with which the local network has roaming agreements. If there is a roaming agreement with the home network, then access is authorized. If there is no roaming agreement with the home network, then the local RADIUS server contacts the RADIUS server of the home network to determine whether access should be authorized. If the home RADIUS server approves authorization, the local RADIUS server sends an authorization response to the PDSN. If the home RADIUS server does not approve authorization, the local RADIUS server sends a response to the PDSN denying access. [0045] In a further embodiment, if the MS 110 desires voice services, the process to authenticate the MS 110 and determine the MS home carrier is essentially the same as described above for Internet access (i.e. data packet service). In referring to Fig. 3 the reader should note that only the differences between the method described for voice services, depicted by Fig. 3, and Internet access as depicted in Kg. 2 will be discussed. [0046] The MS 110 access request is made to mobile switching center (MSC) 320 which formulates and transmits a visitor locator register (VLR) query 330 to VLR 340. VLR 340 receives the MS's MSID 310 and formulates a DNS query which is transmitted to the CDG DNS server 250 which responds with the domain name of the carrier, (i.e. the home carrier of the MS). VLR 340 then formulates and transmits a home locator register (HLR) query 350 to HLR 360. HLR 360 is associated with the home carrier of MS 110 identified by CDG DNS server 250. HLR 360 transmits an HLR response 370 to VLR 340, which in turn transmits a VLR response 380 to MS 110. In this embodiment the DNS server 250 and VLR 320 may cache the DNS server response also. [0047] In all other aspects the embodiments of the present invention depicted by Figs. 2 and 3 are essentially the same. [0048] As noted above, the serving network's RADIUS server formulates a DNS query based on the MSID and receives a DNS response containing MS's home network information. The MSID is normally transmitted by the MS to the PDSN, so it is conveniently captured and utilized to for forming queries to determine the home network carrier. The first several bits of a MSID usually can be associated with a carrier and are captured by PDSN 130 and utilized to formulate a query to be forwarded to local RADIUS server 150. [0049] If the MSID consists of a MIN, the first 6 digits can be associated with a carrier, and the first digit is defined to be between 2 and 9. For the IRM, the first 4 digits can be associated with a carrier, and the first digit is defined to be either 0 or 1. For the IMSI, the first 5 digits can be associated with a carrier. [0050] Figs. 4A-4D depict a schematic diagram of the mobile station 110 MSID parsed into several digit arrays for inclusion in the DNS query as described above. MSID Array 410 of Fig. 4A depicts a generic array, wherein bD depicts the first digit captured of the mobile station 110 MSID and bi the i-th digit of the MSID. Reference numeral 420 represents an array of captured digits where the order of the digits are reversed for inclusion in the DNS query. In this scenario, the DNS query will take the form of bj... bn msid.cdg.org with respect to array 410 and bn... ty msid.cdg.org with respect to array 420 (where cdg.org is simply an exemplary domain name at which the DNS server resides.) [0051] Fig. 4B is a schematic diagram of a MSID capture array 430 for a MIN, wherein the DNS query name takes the form of b6.b5.b4-b3-b2-b1.min.cdg.org, where bi is the i-th bit of the MIN. [0052] Fig. 4C is a schematic diagram of a MSID capture array 450 for a IMSI, wherein the DNS query name takes the form of b5.b4.b3.b2.b1.imsi.cdg.org, where bi is the i-th bit of the IMSI. [0053] Fig. 4D is a schematic diagram of a MSID capture array 470 for a IMSI, wherein the DNS query name takes the form 0fb4.b3.b2-b1.irm.cdg.org, where bi is the i-th bit of the IRM. [0054] In an alternate embodiment the DNS name can be formed as b1b2b3b4b5b6.min.cdg.org (see Fig. 4B reference 440), b1b2b3b4.inn.cdg.org, (see Fig. 4C reference 460) and b1b2b3b4b5.imsi.cdg.org (see Fig. 4D referende 480) for MIN, IRM, and IMSI, respectively. [0055] The DNS query is forwarded through the DNS hierarchy to the DNS server authorized by cdg.org. The DNS server contains the MSID-to-Home_Network mapping in the form of DNS resource records. If the MSID prefix bits are resolved to a home network, the DNS server replies with a DNS Response that contains the domain name of the home network. For example, if the IRM prefix bits are 1918, the name in the DNS Query is 8.1.9.1.irm.cdg.org received. The DNS server has a resource record mapping 8.1.9.1 inn to kddi.com, which is the domain name of KDDI owning the IRM prefix 1918. Thus, the DNS Response contains kddi.com. [0056] Fig. 5 is a schematic diagram of multiple local carriers 510, 520 and 530 formulating and forwarding domain name requests to CDG DNS server 550 via the Internet 540. This figure serves to illustrate the consolidation of the home network information in a centralized server. If any of the home network information needs to be updated, the new data can simply be stored in the CDG DNS server 550. There is no need to update data in each of local networks 510, 520 and 530. When it is necessary for any of these local networks to access the home network information to identify the home network associated with a particular MS, the information is retrieved from the CDG DNS server 550 via an appropriate DNS query. [0057] It should be noted that numerous variations may be made in the embodiments described above without departing from the scope of the invention as detailed in the claims below. Some of these variations are mentioned above. For instance, upon receiving the identification of a home network associated with a MS, the local RADIUS server may examine locally stored roaming agreements or contact a RADIUS server associated with the home network to determine whether or not to authorize local network access by the MS. Another variation involves the use of usernames/passwords to authorize access by the MS. It may or may not be necessary to use these usernames/passwords, and if they are used, they may consist of unique or non-unique usernames/passwords. Yet another variation relates to the identification of the MS for purposes of further identifying the corresponding home network. The description of the foregoing embodiments points out the potential use of MIN, IRM or IMSIMSID information, but other types of information could alternatively be used to identify the MS. A number of variations of the DNS queries based on these different types of identifying information are also described above. These examples are similarly intended to be illustrative of the possible variations and wide scope of the various embodiments of the invention. It should therefore be noted that variations which are not explicitly included in the present disclosure will nevertheless be apparent to persons of skill in the art upon reading this disclosure and are therefore considered to be within the scope of the disclosure and the claims below. [0058] Although not discussed in detail above, it should be noted that the functionality described above may be implemented in the servers described above by providing suitable programs that are executed in the respective processing subsystems of these devices. These program instructions are typically embodied in a storage medium that is readable by the respective processing subsystems. Exemplary storage media may include RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage media known in the art Such a storage medium embodying program instructions for implementing the functionality described above comprises an alternative embodiment of the invention. [0059] Those of skill in the art would understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof. [0060] Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention. [0061] The various illustrative logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. [0062] The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal. [0063] The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein. CLAIMS What is claimed is: 1. A method comprising: receiving a request by a mobile station for roaming access to a local network; accessing a remote centralized server to determine a home network associated with the mobile station; and granting or denying access by the mobile station to the local network based at least in part upon the determination of the home network associated with the mobile station. 2. The method of claim 1, wherein the method is implemented in a local remote authentication dial-in user service (RADIUS) server. 3. The method of claim 1, wherein the method is implemented in a visitor locator register (VLR). 4. The method of claim 1, wherein accessing the remote centralized server comprises querying a centralized domain name server (DNS). 5. The method of claim 4, wherein querying the centralized DNS comprises formatting a query for delivery to the centralized DNS, wherein the query includes identifying information associated with the mobile station. 6. The method of claim 5, wherein the identifying information comprises a mobile station ID (MSID). 7. The method of claim 6, wherein the MSID is selected from the group consisting of: a mobile identification number (MIN); an international roaming MIN (IRM), and an international mobile subscriber identity (IMSI). 8. The method of claim 1, further comprising determining whether the home network associated with the mobile station is among one or more networks for which corresponding mobile station users have authorization via a roaming agreement to access the local network. 9. The method of claim 1, further comprising querying a remote RADIUS server associated with the home network associated with the mobile station to determine whether the mobile station is authorized to access the local network. 10. The method of claim 1, further comprising caching information received in response to accessing the remote centralized server. 11. A method comprising: maintaining a central database containing information regarding home networks and associations of the home networks with mobile stations; coupling the central database to a plurality of local servers; receiving a query from one of the plurality of local servers, wherein the query includes identifying information associated with a first mobile station requesting access to a local network associated with the local server; and identifying a home network associated with the first mobile station. 12. The method of claim 11, wherein the information regarding home networks and associations of the home networks with mobile stations comprises a mapping of identifying information associated with one or more mobile stations to one or more home networks associated with the one or more mobile stations. 13. The method of claim 12, wherein the mapping of identifying information associated with the mobile stations to the home networks comprises a mapping of mobile station IDs (MSIDs) to home networks. 14. The method of claim 13, wherein the MSIDs arc selected from the group consisting of: mobile identification numbers (MBSfs); international roaming MINs (IRMs), and international mobile subscriber identities (IMSIs). 15. The method of claim 11, further comprising: receiving queries from one or more additional local servers, wherein the queries include identifying information associated with one or more additional mobile stations requesting access to one or more additional local networks associated with the additional local servers; and identifying one or more additional home networks associated with the additional mobile stations. 16. An apparatus comprising: a local server associated with a local network, wherein the local server is configured to receive a request by a mobile station for roaming access to the local network, access a remote centralized server to determine a home network associated with the mobile station, and grant or deny access by the mobile station to the local network based at least in part upon the determination of the home network associated with the mobile station. 17. The apparatus of claim 16, wherein the local server comprises a remote authentication dial-in user service (RADIUS) server. 18. The apparatus of claim 16, wherein the local server comprises a visitor locator register (VLR). 19. The apparatus of claim 16, wherein the local server is configured to generate a domain name server (DNS) query and to transmit the query to a centralized DNS. 20. The apparatus of claim 19, wherein the local server is configured to formatting the DNS query to include identifying information associated with the mobile station. 21. The apparatus of claim 20, wherein the identifying information comprises a mobile station ID (MSID). 22. The apparatus of claim 21, wherein the MSID is selected from the group consisting of: a mobile identification number (MIN); an international roaming MIN (IRM), and an international mobile subscriber identity (IMSI). 23. The apparatus of claim 16, wherein the local server further comprises a local storage configured to store roaming agreement information and wherein the local server is configured to determine whether the home network associated with the mobile station is among one or more networks for which corresponding mobile station users have authorization via a roaming agreement to access the local network. 24. The apparatus of claim 16, wherein the local server is coupled to a remote RADIUS server associated with the home network associated with the mobile station and wherein the local server is configured to query the remote RADIUS server to determine whether the mobile station is authorized to access the local network. 25. The apparatus of claim 16, wherein the local server further comprises a local storage configured to cache information received in response to accessing the remote centralized server. 26. An apparatus comprising: a central server configured to maintain a central database containing information regarding home networks and associations of the home networks with mobile stations, receive queries from a plurality of local servers, wherein each of the queries includes identifying information associated with a mobile station requesting access to a corresponding local network associated with the corresponding local server, and identify home networks associated with the mobile stations identified in the queries. 27. The apparatus of claim 26, wherein the central server is configured to store a mapping of identifying information associated with one or more mobile stations to one or more home networks associated with the one or more mobile stations. 28. The apparatus of claim 27, wherein the mapping of identifying information associated with the mobile stations to the home networks comprises a mapping of mobile station IDs (MSIDs) to home networks. 29. The apparatus of claim 28, wherein the MSIDs are selected from the group consisting of: mobile identification numbers (MINs); international roaming MINs (IRMs), and international mobile subscriber identities (IMSIs).

Full Text

SYSTEMS AND METHODS FOR HOME CARRIER DETERMINATION
USING A CENTRALIZED SERVER
Claim of Priority under 35 U.S.C §119
[0001] The present Application for Patent claims priority to Provisional Application No.
60/503,194 entitled "Using the DNS for Home Carrier Determination Based on the MSE>
Prefix'* filed September 15, 2003, assigned to the assignee hereof and hereby expressly
incorporated by reference herein. >
BACKGROUND Field
[0002] The present invention relates generally to wireless communication systems, and more
specifically to a method for determining the home network carrier of a roaming mobile station that is attempting to access a local network.
Background
[0003] As the proliferation of wireless devices increases, mobile users often find themselves
requesting services from service providers other than their home network providers, i.e. home network carriers. The industry has kept up with this situation by putting in place roaming agreements to provide mobile users with services while outside of their home areas. The local networks then each maintain information (e.g., in look-up tables) that can be used to identify which home networks are associated with roaming users, and which home networks are covered by the different roaming agreements.
[0004] When mobile users need service in areas outside the limits of their home networks,
they contact a local network to request service. The request often includes a user name and password that is provided by the home network. This user name and password may, for example, be a publicly available user name that is common to many, if not all, users within the same home network carrier. Upon receiving the request from the mobile user, the local network uses its locally stored information to determine which of the home networks is associated with the user and whether, based on that association, the user should be granted the requested services. This may include checking the user name and password in the user's

request for service against the authorization information stored with the home network's information.
[0005] This arrangement necessities not only the initial expense of setting up the local storage
of the information for all of the home networks, but also the recurring expense of maintaining the information in each of the local networks. For instance, when the information associated with carrier A changes (e.g., the status of roaming agreements, user names, passwords, etc.,) this information must be updated in each of the local networks, in case a user associated with network A roams in an area associated with one of the local networks. Delays or errors in the process of updating the network information can cause denials of service to mobile users that otherwise should have been granted access to the local network. This results in frustrated mobile users and lost revenue for both the local network carrier and the home network carrier.
[0006] It is clear that the difficulties of maintaining the same home network information in
each of the local networks are made worse by scaling. If there are more home networks, there is more information that has to be maintained at each local network. If there are more local networks, the difficulties of keeping the information in all of the local networks are exacerbated. (It may be noted that a given network may be considered a local network or a home network, depending upon the association of the respective networks with particular mobile users.)
[0007] There is therefore a need in the art for systems and methods for authorizing access by
roaming mobile users to a local network that does not suffer from the drawbacks of conventional systems and methods.
SUMMARY
[0008] Embodiments disclosed herein address the above stated needs by providing systems
and methods for determining the home network carrier associated with a mobile station and authorizing the provision of services to the mobile station. Broadly speaking, this is accomplished by centralizing the home network information that is conventionally stored in each of the local networks. The local networks then access the centrally stored information, rather than accessing the locally stored and maintained information, in order to authorize access by roaming users to local services.
[0009] One embodiment comprises a method implemented in a local server, such as a
RADIUS server or VLR. The method includes receiving a request by a mobile station for

roaming access to a local network, accessing a remote centralized server to identify the home network associated with the mobile station, and granting or denying access by the mobile station to the local network based at least in part upon which home network is associated with the mobile station.
[0010] Another embodiment comprises a method implemented in a centralized server such as
a DNS server, wherein the method includes maintaining a central database containing information associating home networks with mobile stations, coupling the central database to several local servers, receiving a query from one of the local servers identifying a first mobile station that wishes to access a local network associated with the local server, and identifying a home network associated with the first mobile station.
[0011] Another embodiment comprises a local server associated with a local network. The
local server is configured to receive a request by a mobile station for roaming access to the local network, access a remote centralized server to determine which home network is associated with the mobile station, and grant or deny access by the mobile station to the local network based upon the identity of the home network associated with the mobile station.
[0012] Yet another embodiment comprises a central server configured to maintain a central
database with information mapping home networks to mobile stations, receive queries from local servers, where the queries include information identifying the mobile stations requesting access to the local networks associated with the corresponding local servers, and identify home networks associated with the mobile stations identified in the queries.
[0013] Numerous additional alternative embodiments are also possible.
BRIEF DESCRIPTION OF THE DRAWINGS
[0014] Various aspects and features of the invention are disclosed by the following detailed
description and the references to the accompanying drawings, wherein:
[0015] FIG. 1 is a schematic diagram of a prior art wireless local network;
[0016] HG. 2 is a schematic diagram of a local wireless network in communication with a
remote centralized server of one embodiment of the present invention;
[0017] FIG. 3 is a schematic diagram of a local wireless network in communication with a
remote centralized server of an alternate embodiment of the present invention;

[0018] FIG. 4A-4D is a schematic diagram of data bit array captured from a mobile station ID
used to construct a query for the remote centralized server of one embodiment of the present invention; and
[0019] FIG. 5 is a schematic diagram of a plurality of local carriers in communication with
the remote centralized server of one embodiment of the present invention.
[0020] While the invention is subject to various modifications and alternative forms, specific
embodiments thereof are shown by way of example in the drawings and the accompanying detailed description. It should be understood, however, that the drawings and detailed description are not intended to limit the invention to the particular embodiments which are described.
DETAILED DESCRIPTION
[0021] One or more embodiments of the invention are described below. It should be noted
that these and any other embodiments described below are exemplary and are intended to be illustrative of the invention rather than limiting.
[0022] As described herein, various embodiments of the invention comprise systems and
methods for determining the home network carrier associated with a mobile station and authorizing the provision of services to the mobile station. Broadly speaking, this is accomplished by centralizing the home network information that is conventionally stored in each of the local networks. The local networks then access the centrally stored information, rather than accessing the locally stored and maintained iirformation, in order to authorize access by roaming users to local services.
[0023] In one embodiment, a roaming mobile user attempts to access local services (e.g.,
internet access) by communicating with a packet data serving node via a radio access network (e.g., a CDMA wireless communication system.) The packet data serving node communicates a request to an authentication server to obtain authorization to provide the requested services to the roaming user. The mobile user's request for services includes information identifying the user's mobile device. This identifying information is communicated to the authentication server, which queries a remote centralized server to determine the home network associated with the mobile user. The remote centralized server returns a response that identifies the user's home network (e.g., a home network carrier domain name.) This home network

information is then used by the authentication server to determine whether the mobile user should be granted access to the requested services.
[0024] Referring to FIGURE 1, a schematic diagram of a roaming wireless mobile station in
communication with a prior art local network system is shown. In this conventional system, a user of mobile station 110, while roaming, may wish to access the local network to obtain service (e.g., internet access.) Mobile station 110 communicates via radio access network (RAN) 115 to establish a communication link with a packet data service node (PDSN) 130. Once the communication link has been established, a username/password 120 is communicated to PDSN 130 using a password authentication protocol (PAP.) This is done so that the user can be authenticated by PDSN 130 prior to providing services to mobile station 110.
[0025] PDSN 130 generates a remote authentication dial-in user service (RADIUS) request
140 and forwards the request to local RADIUS server 150, which authenticates the username/password. The local RADIUS server 150 includes a database 155. Database 155 stores information on those home networks for which roaming users may attempt to access services via the local network. This information normally includes tables or other information for identifying the home networks associated with roaming mobile stations that have requested access to the local network.
[0026] After local RADIUS server 150 has determined with which home network mobile
station 110 is associated, it can be determined whether or not mobile station 110 should be given access to the requested services. This is done by comparing the username/password provided by mobile station 110 to a username/password associated with the home network. The home network's username/password may be stored in RADIUS server 150, or RADIUS server 150 can formulate a query and forward the query to a home RADIUS server (not shown) associated with the home network of mobile station 110.
[0027] Based on the comparison of usernames/passwords, RADIUS server 150 authenticates
mobile station 110. Whether the username/password is authenticated by the local RADIUS server 150 or the home RADIUS server, a RADIUS access accept message 160 is then forwarded to PDSN 130. PDSN 130, in response to the RADIUS access accept message, forwards a PAP acknowledgement 170 to mobile station 110. Mobile station 110 is then allowed access to the requested services.

[0028] During the above described process, a failure at the PPP level or a delay in response
from PDSN 130, local RADIUS server 150 or the home RADIUS server will result in a denial of service for mobile station 110.
[0029] The prior art, as described above, requires that each local RADIUS server 150
maintain a database (or some other data structure) containing information for numerous other networks, particularly for every other carrier with which the local network is partnered. As pointed out above, this arrangement is expensive in terms of additional overhead, maintenance of both the equipment and the data contained within the database, and so on.
[0030] It may be useful before proceeding to describe the various embodiments of the
invention to define a number of terms. These terms include:
BS — base station;
CDG - CDMA Development Group;
CDMA - code division multiple access;
DNS - domain name system;
HLR — home locator register;
IMSI - international mobile subscriber identity;
IRM — international roaming MIN;
MIN - mobile identification number;
MS — mobile station;
MSC — mobile switching center;
MSID -- mobile station ID;
PAP — password authentication protocol;
PDSN - packet data serving node;
RADIUS — remote authentication dial-in user service;
RAN - radio access network;
VLR — visitor locator register.
[0031] It should be noted that mobile stations may include any wireless device capable of
accessing the radio access network, such as a personal digital assistant (PDA,) notebook computer, cellular telephone, 2-way communication devices, pager or the like (this list is intended to be exemplary and not exhaustive). A person of ordinary skill in the art will appreciate and understand that many other devices can access the RAN or be adapted to access the RAN and still fall within the scope and teachings of the several embodiments of the

present invention. Furthermore, the type of system in which the MS operates is not limited, and may include CDMA, TDMA, GSM or other types of wireless communication systems.
[0032] Service or services that may be requested by the mobile station may include either
voice or data packet type services, such as but not limited to voice transmissions, voice mail, e-mail, text messaging, instant messaging, internet access, telephony, streaming audio, streaming video, online games, Internet radio and so on.
[0033] Referring to FIGURE 2, a schematic diagram of a roaming wireless mobile station in
communication with a local network system in accordance with one embodiment of the invention is shown. The reader should note that reference numerals, 110, 115,120,130, 140, 150,160 and 170 correspond to the identically numbered items in Fig. 1.
[0034] In this embodiment, MS 110 again communicates with PDSN 130 via RAN 115.
PDSN 130, in turn, communicates with local RADIUS server 150. At this point, the configuration of the system begins to diverge from the system of FIGURE 1. Rather than having a local database in which the home network information is stored, local RADIUS server 150 is coupled to a remote, centralized server that stores this information. When the information is needed by local RADIUS server 150, a request is sent to the remote, centralized server, which then responds with the information. In FIGURE 2, the remote, centralized server consists of CDG DNS server 250. Local RADIUS server 150 is coupled to the CDG DNS server 250 through a local DNS server 220 and the normal internet DNS hierarchy 240.
[0035] In one embodiment, the home network information stored by the remote, centralized
server consists of a mapping from the MSID prefix of a MS (which is requesting access to the local network's services) to the MS's home network name. The RADIUS 150 server utilizes the Mobile Station ID (MSID), which can be a Mobile Identification Number (MIN), International Roaming MIN (IRM), or International Mobile Subscriber Identity (IMSI), to determine the MS's home network for voice services. For example, the first six digits of a MIN can be mapped to a carrier name. In the embodiment of FIGURE 2, the MSBD-to-home-network mapping table is stored and maintained centrally in a DNS server under the authority of a single organization.
[00361 It should be noted that the remote, centralized server need not consist of a single server
or database, but can be a distributed database or server system, depending on the size and the needs of the system. For instance, the remote centralized database can be mirrored to multiple primary or secondary sites to provide back-up capacity, server redundancy, or increased

performance in the event that a primary server fails or has reduced performance due to high traffic conditions. It is anticipated that the remote centralized server (e.g. CDG DNS server) will consist of less than the number of local RADIUS servers that access the home network information.
[0037] It should also be noted that, although the centrally maintained server depicted in
FIGURE 2 is under the authority of CDG (the CDMA Development Group,) this need not be the case in other embodiments. The central server may be maintained by other entities that may include standards organizations within the industry, commercial enteiprises, non-profit organizations, or even individuals. References herein to CDG (e.g., "CDG DNS server" and "cdg.org") should therefore be construed broadly to refer to any such entity that maintains a central server or server system in accordance with the present disclosure.
[0038] References to other terms in the present disclosure should also be construed broadly,
unless otherwise specified herein. For example, references to "PAP" should be construed to teach the use of any suitable authentication protocol (e.g., PAP, CHAP, etc.,) rather than a single, specific protocol. Similarly, references to "RADIUS" servers should be construed to cover various different types of remote or roaming access (e.g., VLR) severs, and references to "MSID" should be construed to cover various types of identifying information corresponding to the described roaming devices.
[0039] In one embodiment, the roaming MS 110 desires Internet access and sends the
publicly available username and password (provided to the MS by its home network) via PAP to the local serving network for authorization. The MSID for MS 110 is communicated to the PDSN 130 when a connection is established between the MS 110 and the PDSN 130. The PDSN 130 sends RADIUS Access-Request 140 to the local RADIUS server 150. The RADIUS Access-Request 140 contains the MS's username, password, and MSID.
[0040] The local RADIUS server 150 sends a DNS Query 210 to a local DNS server 220. In
this embodiment, the local DNS server 220 is a generic server utilized simply to manage connections and transmissions to and from the internet DNS hierarchy 240. Local DNS server 220 transmits DNS Query 230 to Internet DNS hierarchy 240 which provides links to CDG DNS server 250. The DNS query 230 is forwarded to the DNS server 250, which, in this case, is maintained by CDG.
[0041] If the DNS server 250 has the mapping from the MSID prefix to a home network's
domrin name, the DNS server 250 returns a DNS Response 260 containing the home

network's domain name. In some embodiments, the local RADIUS and DNS servers may cache the MSEMo-home-network mapping provided via the DNS Response. The caching of this information may enable the system to more quickly determine whether or not to authorize future access requests by eliminating the time required for the DNS query and response. The caching of the home network information may be retained and discarded in accordance with any suitable caching policy.
[0042] Upon receiving the DNS Response, the local RADIUS server 150 can determine
whether or not to authorize access by the MS 110 in several ways. For instance, in one embodiment, local RADIUS server 150 compares the home network identified in the DNS Response with a set of locally stored roaming agreements. Each of the roaming agreements identifies a corresponding home network with which the local serving network has an agreement to provide roaming services. If the home network identified in the DNS Response is included among the home networks with which the local serving network has roaming agreements, then the local RADIUS server will authorize the MS to access requested services in accordance with the respective roaming agreement. The roaming agreements may authorize access by all users associated with the respective home network, or they may require that appropriate usernames/passwords be provided by the users. If appropriate, the local RADIUS server 150 sends the RADIUS Access-Accept 160 to the PDSN 130, which then sends the PAP Acknowledgement to the MS 110.
[0043] In another embodiment, rather than comparing the home network identified in the
DNS Response with the home networks for which there are roaming agreements, the local RADIUS server can simply contact a RADIUS server for the home network. If the RADIUS server for the home network approves authorization; of the access requested by the MS, a corresponding response will be provided to the local RADIUS server. The local RADIUS server will then authorize the requested access by the MS.
[0044] It should be noted that these two methods for determining, based on the identification
of the home network associated with the MS, whether to grant access to the MS can also be combined in other embodiments. In one possible embodiment, after receiving the DNS Response from the CDG DNS server, the local RADIUS server may attempt one method, and then the other. For example, the local RADIUS server may first determine whether the home network is included among the networks with which the local network has roaming agreements. If there is a roaming agreement with the home network, then access is

authorized. If there is no roaming agreement with the home network, then the local RADIUS server contacts the RADIUS server of the home network to determine whether access should be authorized. If the home RADIUS server approves authorization, the local RADIUS server sends an authorization response to the PDSN. If the home RADIUS server does not approve authorization, the local RADIUS server sends a response to the PDSN denying access.
[0045] In a further embodiment, if the MS 110 desires voice services, the process to
authenticate the MS 110 and determine the MS home carrier is essentially the same as described above for Internet access (i.e. data packet service). In referring to Fig. 3 the reader should note that only the differences between the method described for voice services, depicted by Fig. 3, and Internet access as depicted in Kg. 2 will be discussed.
[0046] The MS 110 access request is made to mobile switching center (MSC) 320 which
formulates and transmits a visitor locator register (VLR) query 330 to VLR 340. VLR 340 receives the MS's MSID 310 and formulates a DNS query which is transmitted to the CDG DNS server 250 which responds with the domain name of the carrier, (i.e. the home carrier of the MS). VLR 340 then formulates and transmits a home locator register (HLR) query 350 to HLR 360. HLR 360 is associated with the home carrier of MS 110 identified by CDG DNS server 250. HLR 360 transmits an HLR response 370 to VLR 340, which in turn transmits a VLR response 380 to MS 110. In this embodiment the DNS server 250 and VLR 320 may cache the DNS server response also.
[0047] In all other aspects the embodiments of the present invention depicted by Figs. 2 and 3
are essentially the same.
[0048] As noted above, the serving network's RADIUS server formulates a DNS query based
on the MSID and receives a DNS response containing MS's home network information. The MSID is normally transmitted by the MS to the PDSN, so it is conveniently captured and utilized to for forming queries to determine the home network carrier. The first several bits of a MSID usually can be associated with a carrier and are captured by PDSN 130 and utilized to formulate a query to be forwarded to local RADIUS server 150.
[0049] If the MSID consists of a MIN, the first 6 digits can be associated with a carrier, and
the first digit is defined to be between 2 and 9. For the IRM, the first 4 digits can be associated with a carrier, and the first digit is defined to be either 0 or 1. For the IMSI, the first 5 digits can be associated with a carrier.

[0050] Figs. 4A-4D depict a schematic diagram of the mobile station 110 MSID parsed into
several digit arrays for inclusion in the DNS query as described above. MSID Array 410 of Fig. 4A depicts a generic array, wherein bD depicts the first digit captured of the mobile station 110 MSID and bi the i-th digit of the MSID. Reference numeral 420 represents an array of captured digits where the order of the digits are reversed for inclusion in the DNS query. In this scenario, the DNS query will take the form of bj... bn msid.cdg.org with respect to array 410 and bn... ty msid.cdg.org with respect to array 420 (where cdg.org is simply an exemplary domain name at which the DNS server resides.)
[0051] Fig. 4B is a schematic diagram of a MSID capture array 430 for a MIN, wherein the
DNS query name takes the form of b6.b5.b4-b3-b2-b1.min.cdg.org, where bi is the i-th bit of the MIN.
[0052] Fig. 4C is a schematic diagram of a MSID capture array 450 for a IMSI, wherein the
DNS query name takes the form of b5.b4.b3.b2.b1.imsi.cdg.org, where bi is the i-th bit of the IMSI.
[0053] Fig. 4D is a schematic diagram of a MSID capture array 470 for a IMSI, wherein the
DNS query name takes the form 0fb4.b3.b2-b1.irm.cdg.org, where bi is the i-th bit of the IRM.
[0054] In an alternate embodiment the DNS name can be formed as b1b2b3b4b5b6.min.cdg.org
(see Fig. 4B reference 440), b1b2b3b4.inn.cdg.org, (see Fig. 4C reference 460) and b1b2b3b4b5.imsi.cdg.org (see Fig. 4D referende 480) for MIN, IRM, and IMSI, respectively.
[0055] The DNS query is forwarded through the DNS hierarchy to the DNS server authorized
by cdg.org. The DNS server contains the MSID-to-Home_Network mapping in the form of DNS resource records. If the MSID prefix bits are resolved to a home network, the DNS server replies with a DNS Response that contains the domain name of the home network. For example, if the IRM prefix bits are 1918, the name in the DNS Query is 8.1.9.1.irm.cdg.org received. The DNS server has a resource record mapping 8.1.9.1 inn to kddi.com, which is the domain name of KDDI owning the IRM prefix 1918. Thus, the DNS Response contains kddi.com.
[0056] Fig. 5 is a schematic diagram of multiple local carriers 510, 520 and 530 formulating
and forwarding domain name requests to CDG DNS server 550 via the Internet 540. This figure serves to illustrate the consolidation of the home network information in a centralized server. If any of the home network information needs to be updated, the new data can simply be stored in the CDG DNS server 550. There is no need to update data in each of local

networks 510, 520 and 530. When it is necessary for any of these local networks to access the home network information to identify the home network associated with a particular MS, the information is retrieved from the CDG DNS server 550 via an appropriate DNS query.
[0057] It should be noted that numerous variations may be made in the embodiments
described above without departing from the scope of the invention as detailed in the claims below. Some of these variations are mentioned above. For instance, upon receiving the identification of a home network associated with a MS, the local RADIUS server may examine locally stored roaming agreements or contact a RADIUS server associated with the home network to determine whether or not to authorize local network access by the MS. Another variation involves the use of usernames/passwords to authorize access by the MS. It may or may not be necessary to use these usernames/passwords, and if they are used, they may consist of unique or non-unique usernames/passwords. Yet another variation relates to the identification of the MS for purposes of further identifying the corresponding home network. The description of the foregoing embodiments points out the potential use of MIN, IRM or IMSIMSID information, but other types of information could alternatively be used to identify the MS. A number of variations of the DNS queries based on these different types of identifying information are also described above. These examples are similarly intended to be illustrative of the possible variations and wide scope of the various embodiments of the invention. It should therefore be noted that variations which are not explicitly included in the present disclosure will nevertheless be apparent to persons of skill in the art upon reading this disclosure and are therefore considered to be within the scope of the disclosure and the claims below.
[0058] Although not discussed in detail above, it should be noted that the functionality
described above may be implemented in the servers described above by providing suitable programs that are executed in the respective processing subsystems of these devices. These program instructions are typically embodied in a storage medium that is readable by the respective processing subsystems. Exemplary storage media may include RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage media known in the art Such a storage medium embodying program instructions for implementing the functionality described above comprises an alternative embodiment of the invention.

[0059] Those of skill in the art would understand that information and signals may be
represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0060] Those of skill would further appreciate that the various illustrative logical blocks,
modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
[0061] The various illustrative logical blocks, modules, and circuits described in connection
with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
[0062] The steps of a method or algorithm described in connection with the embodiments
disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An

exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.
[0063] The previous description of the disclosed embodiments is provided to enable any
person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

CLAIMS What is claimed is:
1. A method comprising:
receiving a request by a mobile station for roaming access to a local network; accessing a remote centralized server to determine a home network associated with the
mobile station; and granting or denying access by the mobile station to the local network based at least in
part upon the determination of the home network associated with the mobile
station.
2. The method of claim 1, wherein the method is implemented in a local remote
authentication dial-in user service (RADIUS) server.
3. The method of claim 1, wherein the method is implemented in a visitor locator register
(VLR).
4. The method of claim 1, wherein accessing the remote centralized server comprises
querying a centralized domain name server (DNS).
5. The method of claim 4, wherein querying the centralized DNS comprises formatting a
query for delivery to the centralized DNS, wherein the query includes identifying information
associated with the mobile station.
6. The method of claim 5, wherein the identifying information comprises a mobile station
ID (MSID).
7. The method of claim 6, wherein the MSID is selected from the group consisting of: a
mobile identification number (MIN); an international roaming MIN (IRM), and an
international mobile subscriber identity (IMSI).

8. The method of claim 1, further comprising determining whether the home network
associated with the mobile station is among one or more networks for which corresponding
mobile station users have authorization via a roaming agreement to access the local network.
9. The method of claim 1, further comprising querying a remote RADIUS server
associated with the home network associated with the mobile station to determine whether the
mobile station is authorized to access the local network.
10. The method of claim 1, further comprising caching information received in response to
accessing the remote centralized server.
11. A method comprising:
maintaining a central database containing information regarding home networks and associations of the home networks with mobile stations;
coupling the central database to a plurality of local servers;
receiving a query from one of the plurality of local servers, wherein the query includes identifying information associated with a first mobile station requesting access to a local network associated with the local server; and
identifying a home network associated with the first mobile station.
12. The method of claim 11, wherein the information regarding home networks and
associations of the home networks with mobile stations comprises a mapping of identifying
information associated with one or more mobile stations to one or more home networks
associated with the one or more mobile stations.
13. The method of claim 12, wherein the mapping of identifying information associated
with the mobile stations to the home networks comprises a mapping of mobile station IDs
(MSIDs) to home networks.
14. The method of claim 13, wherein the MSIDs arc selected from the group consisting of:
mobile identification numbers (MBSfs); international roaming MINs (IRMs), and international
mobile subscriber identities (IMSIs).

15. The method of claim 11, further comprising:
receiving queries from one or more additional local servers, wherein the queries
include identifying information associated with one or more additional mobile stations requesting access to one or more additional local networks associated with the additional local servers; and
identifying one or more additional home networks associated with the additional mobile stations.
16. An apparatus comprising:
a local server associated with a local network, wherein the local server is configured to receive a request by a mobile station for roaming access to the local network, access a remote centralized server to determine a home network associated with the
mobile station, and grant or deny access by the mobile station to the local network based at least in part
upon the determination of the home network associated with the mobile
station.
17. The apparatus of claim 16, wherein the local server comprises a remote authentication
dial-in user service (RADIUS) server.
18. The apparatus of claim 16, wherein the local server comprises a visitor locator register
(VLR).
19. The apparatus of claim 16, wherein the local server is configured to generate a domain
name server (DNS) query and to transmit the query to a centralized DNS.
20. The apparatus of claim 19, wherein the local server is configured to formatting the
DNS query to include identifying information associated with the mobile station.
21. The apparatus of claim 20, wherein the identifying information comprises a mobile
station ID (MSID).

22. The apparatus of claim 21, wherein the MSID is selected from the group consisting of:
a mobile identification number (MIN); an international roaming MIN (IRM), and an
international mobile subscriber identity (IMSI).
23. The apparatus of claim 16, wherein the local server further comprises a local storage
configured to store roaming agreement information and wherein the local server is configured
to determine whether the home network associated with the mobile station is among one or
more networks for which corresponding mobile station users have authorization via a roaming
agreement to access the local network.
24. The apparatus of claim 16, wherein the local server is coupled to a remote RADIUS
server associated with the home network associated with the mobile station and wherein the
local server is configured to query the remote RADIUS server to determine whether the
mobile station is authorized to access the local network.
25. The apparatus of claim 16, wherein the local server further comprises a local storage
configured to cache information received in response to accessing the remote centralized
server.
26. An apparatus comprising:
a central server configured to
maintain a central database containing information regarding home networks and associations of the home networks with mobile stations,
receive queries from a plurality of local servers, wherein each of the queries includes identifying information associated with a mobile station requesting access to a corresponding local network associated with the corresponding local server, and
identify home networks associated with the mobile stations identified in the queries.

27. The apparatus of claim 26, wherein the central server is configured to store a mapping
of identifying information associated with one or more mobile stations to one or more home
networks associated with the one or more mobile stations.
28. The apparatus of claim 27, wherein the mapping of identifying information associated
with the mobile stations to the home networks comprises a mapping of mobile station IDs
(MSIDs) to home networks.
29. The apparatus of claim 28, wherein the MSIDs are selected from the group consisting
of: mobile identification numbers (MINs); international roaming MINs (IRMs), and
international mobile subscriber identities (IMSIs).

Documents:

871-CHENP-2006 AMENDED PAGES OF SPECIFICATION 14-08-2012.pdf

871-CHENP-2006 AMENDED CLAIMS 14-08-2012.pdf

871-CHENP-2006 EXAMINATION REPORT REPLY RECEIVED 14-08-2012.pdf

871-CHENP-2006 FORM-1 14-08-2012.pdf

871-CHENP-2006 FORM-3 14-08-2012.pdf

871-CHENP-2006 OTHER PATENT DOCUMENT 14-08-2012.pdf

871-CHENP-2006 POWER OF ATTORNEY 14-08-2012.pdf

871-CHENP-2006 CORRESPONDENCE OTHERS 21-02-2012.pdf

871-CHENP-2006 CORRESPONDENCE OTHERS.pdf

871-CHENP-2006 FORM 18.pdf

871-CHENP-2006 FORM 3.pdf

871-chenp-2006-abstract.pdf

871-chenp-2006-assignement.pdf

871-chenp-2006-claims.pdf

871-chenp-2006-correspondnece-others.pdf

871-chenp-2006-description-complete.pdf

871-chenp-2006-drawings.pdf

871-chenp-2006-form 1.pdf

871-chenp-2006-form 26.pdf

871-chenp-2006-form 3.pdf

871-chenp-2006-form 5.pdf

871-chenp-2006-pct.pdf

« Previous Patent

Next Patent »

Patent Number

253752

Indian Patent Application Number

871/CHENP/2006

PG Journal Number

34/2012

Publication Date

24-Aug-2012

Grant Date

22-Aug-2012

Date of Filing

13-Mar-2006

Name of Patentee

QUALCOMM INCORPORATED

Applicant Address

5775 Morehouse Drive, San Diego, CA 92121

Inventors:

#	Inventor's Name	Inventor's Address
1	NASIELSKI, John, Wallace	8719 Elford Court, San Diego, CA 92129
2	HSU, Raymond, T., S.	17775 Pennacook Court, San Diego, CA 92127

PCT International Classification Number

H04Q7/38

PCT International Application Number

PCT/US2004/030103

PCT International Filing date

2004-09-13

PCT Conventions:

#	PCT Application Number	Date of Convention	Priority Country
1	60/503,194	2003-09-15	U.S.A.