Network directed system selection for cellular and PCS enhanced roaming

[0002] This patent application is a Continuation of U.S. patent application Ser. No. 08/695,352, filed Aug. 9, 1996 (issued as U.S. Pat. No. 6,058,309 on May 2, 2000), co pending, claims priority thereto pursuant to 35 U.S.C. 102, and which is hereby incorporated by reference in its entirety.

[0003] The present invention relates to enhanced roaming of mobile stations in cellular and PCS systems. This invention offers a subscriber the ability to use his/her wireless phone or handset, on its most desirable roaming system in any geographic location, without concern for different service providers or air interface technologies. Intelligence in the network (most particularly at the Home Location Register, HLR), as specified in this invention, will always direct the mobile to access and acquire the most favorable system whenever the subscriber is roaming outside his/her home service market.

[0004] One of the most important and distinguishing features of wireless communications is the ability of the mobile station to roam between systems. While roaming, a mobile station typically will select a system made available by a cellular provider in the geographic area where the subscriber is roaming based on its custom system selection method, which emphasizes finding a system (any system) for service. The draw back of this prior approach is that the mobile station does not have any knowledge whether the selected system is the most desirable system, in the sense of whether a more preferred system in a given market (geographic location) may exist for providing better service in terms of roaming rate and compatible services. This makes roaming between systems a big concern from the end user's perspective, which in the past has directly impacted the growth of the wireless market.

[0005] With the introduction of PCS, at any given geographical location, there could eventually be eight wireless systems providing services. Two of them would of course be cellular A-side and B-side service providers at the 800 MHz range. The other six are new comers (Blocks A, B, C, D, E, and F) operating at the 1.9 GHz spectrum. In addition, there are two other factors that have contributed to further confusing the roaming situation even further:

[0006] 1) In this growing market place, more and more preferred roaming agreements will be established between different service providers in different geographic markets. Considering the fact that today, there are 306 Metropolitan Service Areas MSAs and 428 Rural Service Areas RSAs (each MSA or RSA having 2 cellular operators), and 543 MTAs (Major Trading Area) and BTAs (Basic Trading Area). Each region or area may have up to 6 PCS operators. Because of this large number of operators in the US, the number and level of preferred roaming agreements could soon become overwhelming. With the enactment of the US Telecommunications Act in 1996, more and more alliances and mergers of service providers in the market place are predicted. This creates further confusion to the mobile station as to how it can select a system while roaming having a preferred agreement with its home service provider.

[0007] 2) With the auction of the PCS spectrum, some service providers now own different segments of the air spectrum in different geographic locations. It is then imperative for mobile stations to be able to access systems provided by the same service provider in different geographic markets to get preferred rates and to preserve the services that the subscriber has with its home base system.

[0008] In short, competition in wireless services and service provider's desire to offer seamless roaming will make the wireless market place more dynamic and vibrant, which in turn impacts the mobile station's ability to select a favorable system. It is the purpose of this invention to develop a new method, which relies on the intelligence in the network (particularly the Home Location Register, HLR), to guide the mobile station to a preferred cellular provider in any market into which it roams.

[0009] In Cellular mobile operation, the mobile station is programmed by either the operator or the end user to scan the spectrum in a pre-defined sequence to find the home service system. For example, if a mobile's home system is provided by a B-side operator, the mobile station will always scan the B-side channels first when it is turned on, NO MATTER WHERE THE MOBILE IS. If a B-side service provider is not available in the geographic market into which the mobile station has roamed, then, depending upon the pre-defined sequence, the mobile may scan the A-side, or indicate that no service is available in that particular market. It was not heretofore defined in either the standards or in the mobile custom scanning method, for the mobile station to intelligently look for a preferred system that is going to provide the mobile the best service, in terms of the roaming charge, and other factors.

[0010] In PCS communications, the way the mobile acquires a system is even more complicated because of the fact that there are up to 6 different. spectrums available, and there are multiple air interfaces. Also, because of the fact that there are microwave interference sources within the PCS spectrum, the frequencies (channel numbers) of pilot channels are not even specified in the standards. For example, in CDMA, there is only a list of candidate channels for the mobile to scan. Given the standardized CDMA system acquisition time of up to 15 seconds to acquire a pilot channel, it is highly impractical for the mobile to scan on its own trying to find the best system in a particular geographic location (i.e., a foreign market).

[0011] Even though today the CDMA community is trying to define a handset solution to enhanced roaming, based on pre-programmed sequence of scanning by the service providers, it may not work well at all because of the limited precious mobile station memory. Given the overwhelming number of cellular and PCS systems in service, it is hard to imagine how the mobile will be able to be programmed with information as to preferred systems in all markets. Furthermore, due to the dynamic nature of the wireless market, a handset solution will require periodic updating to provide needed preferred system information. But, updating the list in the mobile has to be originated by the mobile. Considering the fact that the mobile user will have no easy way of knowing that any change in the market place has occurred, this will create nuisance to both the service providers and the end users and is likely to result in unneeded update requests from roaming mobile stations.

[0012] In this invention, we describe a network based solution for the purpose of enhanced roaming, namely, the Network Directed System Selection (NDSS) approach. The Network Directed System Selection feature is a network capability that provides a network based mechanism for a service provider, based on various customer and service provider specified criteria, to automatically direct a user to a desired system. The desired system could be any system available to the subscriber unit, regardless of frequency band (cellular A/B or PCS bands A/B/C/D/E/F) or technology (analog or digital).

[0013] The Network Directed System Selection (NDSS) feature consists of features that allow a cellular or PCS service subscriber to register upon a preferred system while they are roaming (i.e., outside of their home system) without any manual intervention by the subscriber. NDSS allows a subscriber unit to be automatically directed by their home service provider to a suggested system, regardless of the frequency band (e. g. cellular A/B or PCS bands A/B/C/D/E/F), and be compatible to the air interfaces supported by the terminal. The NDSS feature also allows a network operator to control access to systems to facilitate testing, load control, and service quality control. For example, when a customer registers on a system, the network may direct the user from that system to another system. The subscriber unit may then remain on the system until power down, or until directed back to the original system by a subsequent message from the NDSS feature, or until handed off to another system. NDSS also allows the subscriber to suppress or desuppress the feature.

[0014] FIG. 1 illustrates a typical example of the intersystem message flow required for an NDSS scenario in which the mobile station (MS) roams from one system to another and initiates the initial registration and validation process, and while registering with the visited system, it is directed by its home service provider to a preferred roaming system.

[0015] FIG. 2 illustrates a typical example of the intersystem message flow required to support authentication as the MS initiates the initial registration, and while being authenticated, it is directed by its home service provider to a preferred roaming system.

[0016] FIGS. 3 and 4 are examples of the flow charts that illustrate how the HLR searches the Enhanced Roaming System List (ERSL) and decides on a preferred system for the MS.

[0017] FIG. 1 illustrates the intersystem message flow required for a Network Directed Systems Selection NDSS scenario in which a mobile station MS roams from one system to another and initiates the initial registration and validation process, and while registering with the newly visited system, it is directed by its home service provider to an alternative but preferred roaming system. The individual steps of the message flow are described in detail as follows:

[0018] a. The MS determines that a new serving system has been entered and a registration is needed. Registration may also be needed if the mobile station is first turned on while physically located in the geographic area served by a new serving system. When either of these events occurs, the MS attempts to register with a new serving system (Mobile Switching Center MSC-2).

[0019] b. The new serving MSC (MSC-2) includes a computer (not illustrated but associated therewith) which receives a registration notice REGNOT from the MS via MSC-2 and queries the visiting location register VLR (VLR-2) for the mobile switching center MSC-2. This register VLR-2 contains information pertaining to all the mobile stations which are visiting the geographic area served by MSC-2.

[0020] c. If the MS is not listed in the VLR-2, a registration notice REGNOT is sent to the Home Location Register HLR, maintained by the home service provider, and its coupled computer (not illustrated) for the MS. The Home Location Register contains information pertaining to the type of service subscribed to by the MS and the status of the subscriber account. Note that the RegistrationNotification response from the VLR to the MSC is contingent upon the response received from the HLR.

[0021] d. If the HLR and its coupled computer determine that another system is preferable, MSC-2 is NDSS capable, and the subscriber has not suppressed the NDSS override of the handset's system selection procedure, the HLR and its associated computer send a registration response message (regnot) to the serving system (VLR-2 and its associated computer) indicating an NDSS operation request and specifying the REDIRECT_RECORD and RETURN_IF_FAIL fields. The REDIRECT_RECORD identifies the preferred system in the geographical region of the MS and any necessary parameters for connecting to that system. The RETURN_IF_FAIL field is a two bit field and has several functions. The data in this field functions to instruct the MS to do one of several things. 1. If connection to the preferred service provider (MSC-3) cannot be established, the MS may attempt to reestablish connection with MSC-2. In this case, the field value in binary is 01. 2. Reinitialize communication according to the logic for the MS. In this case, the field value in binary is 10. 3. If the preferred service provider cannot be contacted, then avoid contact with MSC-2 and attempt to access to any other system according to the logic in the MS. In this case, the field value in binary is 11. A-binary field value of 00 is not defined and reserved for possible future alternative use.

[0022] The computer associated with the HLR may choose not to send mobile station service profiles in regnot because the service provided by MSC-2 may not be involved if the preferred provider is subsequently connected to by the mobile station MS. The service profiles comprise parameters which identify the types of functions subscribed to by the user of the mobile station MS. Failing to send these parameters with the redirection message may also be done to reduce the communication load between the “home” system and the remote service provider system. The computer associated with the HLR also may not perform location updating in the HLR since MSC-2 is not authorized for service. Such location updating in the HLR is deferred until the servicing remote provider is coupled to the MS.

[0023] e. VLR-2 and its associated computer, upon receipt of the regnot message specifying an NDSS operation, removes all record of the MS in VLR-2 if RETURN_IF_FAIL binary value is either 10 or 11.

[0024] f. The MSC-2 and its associated computer then sends a Service Redirection message to the mobile station MS, to provide the mobile station information about the preferred system (MSC-3) and the RETURN_IF_FAIL field specification. The Service Redirection message may be sent to the mobile station MS over either the control channel, traffic channel, paging channel or through SMS (Short Message Service).

[0025] g. Upon receipt of the Service Redirection message, the MS scans and finds the specified preferred system (MSC-3) and performs registration.

[0026] h. The preferred serving MSC (MSC-3) sends a REGNOT to its VLR (VLR-3) and its associated computer.

[0027] i. If the MS is not found in the VLR-3, the computer associated with VLR-3 sends a REGNOT to the HLR associated with the MS. Note that the RegistrationNotification response from the VLR-3 to the MSC-3 is contingent upon the response received from the HLR.

[0028] j. If the MS was previously registered elsewhere, the HLR sends a REGCANC (registration cancel) to the previously visited system including a computer associated with VLR (VLR-1). The computer associated with this VLR, upon receipt of the cancellation message, essentially removes all record of the MS from its memory.

[0029] k. The computer associated with VLR-1 also sends a REGCANC to the previously visited MSC (MSC-1). That MSC, upon receipt of the cancellation message, essentially removes all record of the MS from its memory.

[0030] l. MSC-1 sends a registration canceled message (regcanc) to the computer associated with VLR-1.

[0031] m. The computer associated with VLR-1 sends a regcanc message to the HLR.

[0032] n. If the computer associated with the HLR determines that the MS can be granted service by the preferred provider in the geographic region where MS is currently located, the computer associated with the HLR sends a registration message (regnot) to the computer associated with VLR-3. This notice will include the parameters indicating the types of services subscribed to by the MS.

[0033] o. The computer associated with the VLR-3 forwards the regnot message to MSC-3.

[0034] p. MSC-3 sends the Registration Accepted Order to the MS.

[0035] FIG. 2 illustrates the intersystem message flow required to support a roaming MS that has moved from one geographic area where support is provided by one mobile switching center to a second geographic area supported by a second mobile switching center. As a further complication to this situation, authentication is requested as the MS initiates the initial registration, and while being authenticated, it is directed by its home service provider to a preferred roaming system located in the second geographic area. The individual steps of the message flow are described in detail below for this situation:

[0036] a. The MS determines from the Overhead Message Train (OMT) that the geographic coverage area of a new serving system has been entered and that the mobile service provider in this geographic area requires authentication on all system accesses (AUTH=1). The Random Number (RAND) to be used for authentication may also be obtained by the MS at this time. If it is not, a zero value is used by the MS as prescribed by TR-45 Authentication.

[0037] The MS executes the CAVE algorithm with circuitry in the MS using the shared secret data part A SSD-A currently stored in the MS, electronic serial number ESN, an encoded mobile identification number MIN1 and the random number RAND value to produce a registration Authentication Result (AUTHR).

[0038] b. The MS registers at the new Serving Mobile Switching Center (MSC-2), providing its MIN, ESN, AUTHR, CallHistoryCount (COUNT), and a signature RANDC derived from the RAND used to compute AUTHR.

[0039] c. The computer (not shown) associated with the MSC-2 verifies RANDC supplied by the MS and generates the appropriate value of RAND for incorporation in an AUTHREQ message which is recorded in the new Serving VLR (VLR-2).

[0040] d. The computer associated with MSC-2 and VLR-2 forwards the AUTHREQ message to the computer system (not shown) associated with the Home Location Register HLR for the MS.

[0041] e. If the computer associated with the HLR determines that another system is preferable, MSC-2 is NDSS capable, and the subscriber has not suppressed the NDSS override of the handset's system selection procedure, the computer associated with the HLR sends an authreq message to the new serving system computer associated with MSC-2 and VLR-2 indicating an NDSS operation request and specifying the REDIRECT_RECORD and RETURN_IF_FAIL fields in the manner discussed with respect to FIG. 1.

[0042] f. The computer associated with VLR-2, upon receipt of the authreq message specifying an NDSS operation, essentially removes all record of the MS from its memory if RETURN_IF_FAIL is disabled. If RETURN_IF_FAIL is enabled, the computer associated with VLR-2 may keep the authentication data related to this MS in the VLR-2 for a certain amount of time, in case the MS fails to find the re-directed system and registers again with authentication parameters within this period of time.

[0043] g. The MSC-2 sends a Service Redirection message to the mobile station MS, to provide the mobile station information about the preferred system (MSC-3) and the RETURN_IF_FAIL field specification. The Service Redirection message may be sent to the mobile station MS over either the control channel, traffic channel, paging channel or through SMS (Short Message Service).

[0044] h. Upon receipt of the Service Redirection message, the MS scans and finds the specified preferred system (MSC-3) and performs registration.

[0045] The MS determines from the Overhead Message Train (OMT) that the geographic coverage area of a new serving system has been entered and that the mobile service provider in this geographic area requires authentication on all system accesses (AUTH=1). The Random Number (RAND) to be used for authentication may also be obtained by the MS at this time. If it is not, a zero value is used by the MS as prescribed by TR-45 Authentication.

[0046] The MS executes the CAVE algorithm with circuitry in the MS using the shared secret data part A SSD-A currently stored in the MS, electronic serial number ESN, an encoded mobile identification number MIN1 and the random number RAND value to produce a registration Authentication Result (AUTHR).

[0047] i. The MS registers at the preferred Serving MSC (MSC-3), providing its MIN, ESN, AUTHR, CallHistoryCount (COUNT), and RANDC derived from the RAND used to compute AUTHR.

[0048] j. The computer (not shown) associated with the MSC-3 verifies RANDC supplied by the MS and generates the appropriate value of RAND for incorporation in an AUTHREQ message which is recorded in the new Serving VLR (VLR-2).

[0049] k. The computer associated with VLR-3 forwards the AUTHREQ to the computer associated with the HLR for the MS.

[0050] l. The computer associated with the HLR forwards the AUTHREQ to its Authentication Center AC which may comprise another programmed computer of may be the computer associated with the HLR itself.

[0051] m-p. If SSD is presently shared with another system, the computer associated with the AC shall perform validation of the MS as described in Section 5.4.8 (Authentication with sharing of SSD) of IS-41-C and go on to Step-a1 below.

[0052] Otherwise, the computer associated with the AC verifies the MIN and ESN reported by the MS. The computer associated with the AC then executes the CAVE algorithm using the SSD-A currently stored, ESN, MIN1 and the RAND value to produce a registration Authentication Result (AUTHR).

[0053] The computer associated with the AC verifies that the AUTHR received from the MS matches its CAVE results.

[0054] The computer associated with the AC then verifies that the COUNT received from the MS is consistent with the value currently stored at the AC.

[0055] q. The computer at the AC sends an authentication confirmed message, authreq, to the computer associated with the HLR. The authreq may include SSD and directives to issue a Unique Challenge, to update the MS SSD or to update the MS COUNT according to AC/HLR local administrative practices. These update procedures are described in Sections 5.4.6, 5.4.7, and 5.4.9 of IS-41-C. Alternatively, the authreq may include DenyAccess.

[0056] r. The computer at the HLR forwards the authentication confirmed message authreq to the computer associated with VLR-3.

[0057] s. the computer associated with VLR-3 forwards the authreq to the MSC-3.

[0058] t. Following successful authentication of the MS, MSC-3 sends a REGNOT to the computer associated with VLR-3.

[0059] u. The computer associated with VLR-3 forwards the REGNOT to the computer associated with HLR.

[0060] v. If the MS was previously registered in another system, the computer associated with HLR sends a registration cancellation message REGCANC to the old Serving VLR (VLR-1).

[0061] w. The computer associated with VLR-1 forwards the REGCANC to the old Serving MSC (MSC-1).

[0062] x. MSC-1 returns a regcanc to the computer associated with VLR-1.

[0063] y. The computer associated with VLR-1 returns a regcanc to the HLR.

[0064] z. The computer associated with the HLR records the new location of the MS in its local memory and responds to the REGNOT with a regnot message that includes the information requested by the computer associated by the VLR-3.

[0065] a1. The computer associated with VLR-3 forwards the regnot to MSC-3.

[0066] b1. MSC-3 sends the Registration Accepted Order to the MS.

[0067] FIGS. 3 and 4 are flow charts that illustrate how the HLR searches the Enhanced Roaming System List (ERSL) and decides on a preferred system for the MS. Those of skill in the art will recognize that other approaches may be employed to perform this function of identifying the preferred service provider in the geographic region where a given MS is roaming.

[0068] The following table presents a data structure for the Enhanced Roaming System List(ERSL) for CDMA and Analog air interface technologies. This structure employs MSCID as the main index for scanning the list. NID can be used with MSCID if available. It is understood that similar tables for different air interface technologies are derivatives of this table, and should be recognized as such.

[0069] Note:

[0070] a. Redirect_Parameter differs according to the access: technology of the serving system. For example, if the serving system is a CDMA system, its REDIRECT_RECORD will be as follows (refer to CDAM for the definitions of the fields):

[0071] b. If the serving system is an analog system, its REDIRECT_RECORD will be as follows (refer to CDMA for the definition of the fields):

[0072] Note that SYS_ORDERING should be set to either ‘System A only’ or ‘System B only’ based on the corresponding system.

[0073] c. ROAMING_INDICATION can be sent to the MS for Enhanced Roaming Display purposes. Support of this feature is optional. ROAMING_INDICATION should be as follows:

[0074] The following presents a structure of the service redirection message. A service redirection message SerRed is sent from a remote mobile switching center, such as MSC-2 of FIG. 1, to the mobile station MS, with redirection record and parameters for instructing the mobile station to attempt to register or originate a call at the mobile switching center of a preferred service provider. The service redirection message can be sent on the Control Channel, Paging Channel, Forward Traffic Channel, or via Short Message Service (SMS).

[0075] When the remote mobile switching center sends a Service Redirection Message on the Forward Traffic Channel, it preferably uses the following variable-length message format:

[0076] MSG_TYPE—Message type.

[0077] The base station sets this field to ‘00010000’.

[0078] ACK_SEQ—Acknowledgement sequence number.

[0079] The base station sets this field to the MSG_SEQ field from the most recently received Access Channel message requiring an acknowledgement from the mobile station addressed by this message.

[0080] MSG_SEQ—Message sequence number.

[0081] The base station sets this field to the acknowledgement sequence number for this message.

[0082] ACK_REQ—Acknowledgement required indicator.

[0083] If the mobile station is to acknowledge this message, the base station sets this field to ‘1’. If the mobile station is not to acknowledge this message, the base station sets this field to ‘0’.

[0084] ENCRYPTION—Message encryption indicator.

[0085] RETURN_IF_FAIL—Return if fail indicator.

[0086] The base station sets this field to ‘1’ if the mobile station is required to return to the system from which it is being redirected upon failure to obtain service using the redirection criteria specified in this message. Otherwise, the base station sets this field to ‘0’.

[0087] SHUN—Shun indicator.

[0088] The base station sets this field to ‘1’ if the mobile station is required to select, using its custom system selection process, a system other than the system from which it is being redirected upon failure to obtain service using the redirection criteria specified in this message. Otherwise, the base station sets this field to ‘0’.

[0089] REDIRECT_TYPE—Redirect indicator.

[0090] The base station sets the field to the REDIRECT_TYPE value shown in table below to correspond to the desired redirection type.

[0091] RESERVED—Reserved bits.

[0092] The base station sets this field to ‘0000’.

[0093] The base station shall include one occurrence of the following record:

[0094] RECORD_TYPE—Redirection record type.

[0095] The base station sets the field of the RECORD_TYPE to the value shown in the table below which corresponds to the type of redirection type specified by this record.

[0096] RECORD_LEN—Redirection record length.

[0097] If RECORD_TYPE equals to ‘00000000’, the base station sets this field to ‘00000000’. Otherwise, the base station sets this field to the number of octets in the type-specific fields of this redirection record.

[0098] Type-specific fields—Redirection record type-specific fields.

[0099] The base station shall include type-specific fields based on the RECORD_TYPE of this redirection record.

[0100] If RECORD_TYPE is equal to ‘00000000’, the base station shall not include the type-specific fields.

[0101] If RECORD_TYPE is equal to ‘00000001’, the base station shall include the following fields:

[0102] EXPECTED_SID—Expected SID.

[0103] If the base station is redirecting the mobile station to a specific system, the base station sets this field to the SID of that system. Otherwise, the base station sets this field to 0.

[0104] IGNORE_CDMA—Ignore CDMA Available indicator.

[0105] The base station sets this field to ‘1’ to indicate that the mobile station is to ignore the CDMA Capability Message on the analog system to which it is being redirected. The base station sets this field to ‘0’ to indicate that the mobile station may discontinue service on the system to which it is being redirected if the mobile station receives a CDMA Capability Message with CDMA_AVAIL equal to ‘1’, and the preferred mode of the mobile station is CDMA.SYS_ORDERING—System ordering. The base station sets this field to the SYS_ORDERING value shown in the table below corresponding to the order in which the mobile station is to attempt to obtain service on an analog system.

[0106] RESERVED—Reserved bits.

[0107] The base station sets this field to ‘00000’.

[0108] If RECORD_TYPE is equal to ‘00000010’, the base station shall include the following fields:

[0109] BAND_CLASS—Band class.

[0110] The base station sets this field to the CDMA band class, as specified in TSB58.

[0111] EXPECTED_SID—Expected SID.

[0112] If the base station is redirecting the mobile station to a specific system, the base station sets this field to the SID of that system. Otherwise, the base station sets this field to 0.

[0113] EXPECTED_NID—Expected NID.

[0114] If the base station is redirecting the mobile station to a specific network, the base station set this field to the NID of that network. Otherwise, the base station sets this field to 65535.

[0115] RESERVED—Reserved bits.

[0116] The base station sets this field to ‘0000’.

[0117] NUM_CHANS—Number of CDMA Channels.

[0118] The base station sets this field to the number of occurrences of the CDMA_CHAN field in this record.

[0119] CDMA_CHAN—CDMA Channel number.

[0120] For each CDMA Channel on which the mobile station is to attempt to acquire a CDMA system, the base station shall include one occurrence of this field specifying the associated CDMA Channel number.

[0121] RESERVED—Reserved bits.

[0122] The base station shall add reserved bits as needed in order to make the length of the record equal to an integer number of octets. The base station sets these bits to ‘0’.

[0123] When the base station sends a Service Redirection Message on the Paging Channel, it preferrably will use the following variable-length message format:

[0124] VALID_ACK—Valid acknowledgement indicator.

[0125] To acknowledge the most recently received Access Channel message from the mobile station, the base station sets this field to ‘1’. If this message does not acknowledge the most recently received Access Channel message from the mobile station, the base station sets this field to ‘0’.

[0126] ADDR_TYPE—Address type.

[0127] ADDR_LEN—Address field length.

[0128] ADDRESS—Mobile station address.

[0129] All definitions of other fields are the same as those in the service redirection message on the Traffic Channel.

[0130] The above description has been directed to describing the invention in terms of the drawings which are illustrative of the preferred embodiment of the invention, those of skill in this art will recognize that various changes in form can be made without departing from the spirit and scope of the invention as defined in the following claims.