Network selection scheme using a roaming broker (RB)
Summary by NHIP
Network selection via roaming broker
The method sends network advertisement information to a broker node and receives a redirect message containing a better-suited network combination. This additional combination is customized based on the device's location and determined by querying a database with defined network relationship information.
Claim Score by NHIP
Abstract
A network selection scheme operable in a network environment having one or more radio access networks (RANs), one or more core networks (CNs), and one or more service networks (SNs). Upon obtaining identity information of a particular network combination, a wireless user equipment (UE) device is operable to register with a roaming broker (RB), whereby additional information may be provided to the device for facilitating appropriate network selection.

Term
Term ended
Expired 28 April 2025, 1.4 years ago.
- Priority and filed
- Granted
- Expired
- Today
18 claims: 6 independent, 12 dependent
- 1A network selection method operating at a wireless user equipment (UE) device, comprising:sending, to a broker node in a network that is wirelessly available, network advertisement information including identity information relating to a plurality of network combinations, each network combination comprising at least a radio access network (RAN) and one of a core network (CN) and a service network (SN) disposed in an interconnected arrangement;responsive to said sending, receiving a redirect message comprising identity information regarding an additional network combination for providing service with respect to said wireless UE device, wherein said additional network combination comprises at least a RAN and one of a CN and an SN that is determined to be better suited to said wireless UE device than said particular network combination initially selected by said wireless UE device and is customized based on the wireless UE device's location, based on querying a database having network relationship information defined for said wireless UE device;and receiving background scan timing information for use with each wireless technology supported by said wireless UE device.
- 3A network selection system operating in a wireless user equipment device, the system comprising:means, responsive to selecting a particular network combination, for sending network advertisement information including identity information relating to a plurality of network combinations to a broker node, each of said network combinations comprising at least a radio access network (RAN) and one of a core network (CN) and a service network (SN) disposed in an interconnected arrangement;means for receiving, from said broker node, an additional network combination comprising at least a RAN and one of a CN and an SN for providing service to said wireless UE device, wherein said additional network combination has been selected with regard to service relationship data that is provisioned on said broker node regarding RANs, CNs and SNs that have a relationship with a home network of said UE device and customized based on said wireless UE device's location;means for receiving background scan timing information for use with each wireless technology supported by the UE device;and means for choosing one of said particular network combination and said additional network combination;wherein each of said means is embodied in a persistent storage module of said UE device.
- 5A wireless user equipment (UE) device, comprising:a logic module operable to obtain identity information of a particular network combination available in a location area, said particular network combination selected from a plurality of network combinations, each combination comprising at least a radio access network (RAN) and one of a core network (CN) and a service network (SN) disposed in an interconnected arrangement;a logic module operable to transmit said identity information to a roaming broker (RB) disposed in said network environment upon registration therewith, said registration including transmission of an indication relating to particular services that said wireless device would like to use;a logic module operable to receive background scan timing information for use with each wireless technology supported by said UE device;and a network selection logic module operable to select one of said particular network combination and an additional network combination provided by said RB via a redirect message, said redirect message including identity information of said additional network combination, wherein said additional network combination is determined to be better suited to said wireless UE device, based on service relationship data regarding RANs, CNs and SNs that have a relationship with a home network of said UE device, than said particular network combination initially selected by said wireless UE device.
- 12Broadest claimClaim Score 39, average(NHIP)A network selection method operating on a wireless user equipment device, comprising:obtaining identity information of a particular network combination selected from a plurality of network combinations, each comprising at least a radio network (RAN) and one of a core network (CN) and a service network (SN) disposed in an interconnected arrangement;registering with a roaming broker (RB), said registering including transmission of an indication relating to particular services that said wireless UE device would like to use;providing said identity information to said RB;selecting one of said particular network combination and an additional network combination received from said RB via a redirect message, wherein said additional network combination is determined to be better suited to said wireless UE device, based on querying a database having service relationship data regarding RANs, CNs and SNs that have a relationship with a home network of said UE device, than said particular network combination initially selected by said wireless UE device and is customized based on said wireless UE device's location;and receiving background scan timing information at said wireless UE device for use with each wireless technology supported by said UE device.
- 15Software, embodied in a tangible, non-transitory storage module on a wireless user equipment device, that when executed facilitates network selection, said software comprising:logic for sending identity information relating to a plurality of network combinations discovered by said UE device, each network combination being identified as a combination of respective identification codes comprising at least a radio access network (RAN) and one of a core network (CN) and a service network (SN) disposed in an interconnected arrangement;logic for receiving a redirect message at said wireless UE device, said redirect message including identity information of an additional network combination, wherein said additional network combination comprises a RAN and one of a CN and an SN and is determined to be better suited to said wireless UE device than a network combination initially selected by said wireless UE device based on network relationship information for said wireless UE device and is customized based on said wireless UE device's location;and logic for receiving background scan timing information at said wireless UE device for use with each wireless technology supported by said UE device.
- 16A wireless user equipment device comprising:means for sending network advertisement information to a roaming broker node in a network that is wirelessly accessible, said network advertisement information including identity information relating to a plurality of network combinations, each being identified as a combination of respective identification codes, said combination comprising at least a radio access network (RAN) and one of a core network (CN) and a service network (SN) disposed in an interconnected arrangement;means for receiving a redirect message from said roaming broker node, said redirect message including identity information of an additional network combination that comprises a RAN and one of a CN and an SN, is customized based on said wireless UE device's location and is determined to be better suited to said wireless UE device, with respect to service relationship data relating to RANs, CNs and SNs that have a service agreement with a home network associated with said wireless UE device, than a particular network combination initially selected by said wireless UE device, wherein each of said means comprises software embodied in a persistent storage module;and means for receiving background scan timing information at said wireless UE device for use with each wireless technology supported by the UE device.
Independent claims6
57 paragraphs in 5 sections, as filed
CROSS-REFERENCE TO RELATED APPLICATION(S)
This application discloses subject matter related to the subject matter disclosed in the following commonly owned co-pending U.S. patent application(s): “SYSTEM AND METHOD FOR PROVIDING NETWORK ADVERTISEMENT INFORMATION VIA A NETWORK ADVERTISEMENT BROKER (NAB),” filed Apr. 28, 2005 herewith, in the name(s) of: Adrian Buckley, Paul Carpenter, Nicholas P. Alfano, and Andrew Allen Ser. No. 11/116,470; each of which is hereby incorporated by reference in their entirety.
FIELD OF THE DISCLOSURE
The present patent disclosure generally relates to communication networks. More particularly, and not by way of any limitation, the present patent application is directed to a network selection scheme using a brokering entity such as a roaming broker (RB).
BACKGROUND
When a wireless network is deployed, there is a need to broadcast an identifier such that a wireless user equipment (UE) device wishing to obtain service can identify the wireless network. In a typical implementation, a single broadcast identifier is provided. However, where the constituent radio access network (RAN), core network (CN) and service network (SN) are segmented and individually identified, such a technique becomes woefully inadequate.
BRIEF DESCRIPTION OF THE DRAWINGS
A more complete understanding of the embodiments of the present patent application may be had by reference to the following Detailed Description when taken in conjunction with the accompanying drawings wherein:
<figref idrefs="DRAWINGS">FIG. 1</figref> depicts a generalized network environment wherein an embodiment of the present patent disclosure may be practiced;
<figref idrefs="DRAWINGS">FIG. 2</figref> depicts an exemplary embodiment of a network environment where a wireless user equipment (UE) device is operably disposed for acquiring network advertisement information in accordance with the teachings of the present patent disclosure;
<figref idrefs="DRAWINGS">FIG. 3</figref> depicts an exemplary database structure provided as part of a network advertisement broker (NAB) in accordance with the teachings of the present patent disclosure;
<figref idrefs="DRAWINGS">FIG. 4</figref> depicts an exemplary message flow diagram of the present patent disclosure for acquiring network advertisement information according to one embodiment;
<figref idrefs="DRAWINGS">FIG. 5</figref> depicts an exemplary message flow diagram of the present patent disclosure for acquiring network advertisement information according to another embodiment;
<figref idrefs="DRAWINGS">FIG. 6</figref> is a flowchart associated with a method of the present patent disclosure;
<figref idrefs="DRAWINGS">FIG. 7</figref> depicts an exemplary database structure that may be provided as an operated-based list, a user-based list or an enterprise-based list for configurably setting network selection preferences and prohibitions according to the teachings of the present patent disclosure;
<figref idrefs="DRAWINGS">FIGS. 8A and 8B</figref> depict exemplary database structures for facilitating network selection by a wireless UE device;
<figref idrefs="DRAWINGS">FIG. 9</figref> depicts an exemplary database structure provided as part of a roaming broker (RB) node in accordance with the teachings of the present patent disclosure;
<figref idrefs="DRAWINGS">FIG. 10</figref> depicts an exemplary message flow diagram of the present patent disclosure for interacting with an RB node according to one embodiment;
<figref idrefs="DRAWINGS">FIG. 11</figref> is a flowchart associated with another method of the present patent disclosure; and
<figref idrefs="DRAWINGS">FIG. 12</figref> depicts a block diagram of an embodiment of a wireless UE device operable to acquire network advertisement information and perform network selection according to the teachings of the present patent disclosure.
DETAILED DESCRIPTION OF THE DRAWINGS
A network selection scheme is provided for operation in a network environment having one or more radio access networks (RANs), one or more core networks (CNs), and one or more service networks (SNs). Upon obtaining identity information of a particular network combination, a wireless user equipment (UE) device is operable to register with a roaming broker (RB), whereby additional information may be provided to the device for facilitating appropriate network selection.
In one embodiment, the present disclosure is directed to a network selection method operable in a network environment having one or more RANs, one or more CNs, and one or more SNs, comprising: obtaining identity information of a particular network combination by a wireless UE device; obtaining an Internet Protocol (IP) address of a roaming broker (RB) by the wireless UE device; transmitting network advertisement information to the RB by the wireless UE device upon registration therewith; determining by the RB if an additional network combination is more suitable to the wireless UE device; responsive to the determining, providing a redirect message to the wireless UE device, the redirect message including identity information of the additional network combination; and selecting one of the particular network combination and the additional network combination for obtaining service by the wireless UE device.
In another embodiment, the present disclosure is directed to a network selection system operable in a network environment having one or more RANs, one or more CNs, and one or more SNs, comprising: means associated with a wireless UE device for obtaining identity information of a particular network combination and for obtaining an IP address of a roaming broker (RB) disposed in the network environment; means for transmitting network advertisement information to the RB by the wireless UE device upon registration therewith; means associated with the RB for determining if an additional network combination is more suitable to the wireless UE device; means, operable responsive to the determining, for providing a redirect message to the wireless UE device, the redirect message including identity information of the additional network combination; and means associated with the wireless UE device for selecting one of the particular network combination and the additional network combination for obtaining service by the wireless UE device.
In a still further embodiment, the present disclosure is directed to a wireless UE device, comprising: a logic module operable to obtain identity information of a particular network combination available in a location area; a logic module operable to transmit network advertisement information to a roaming broker (RB) disposed in the network environment upon registration therewith; and a logic module operable to select one of the particular network combination and an additional network combination provided by the RB via a redirect message, wherein the RB includes service logic for determining if the additional network combination is more suitable to the wireless UE device, the redirect message including identity information of the additional network combination.
A system and method of the present patent disclosure will now be described with reference to various examples of how the embodiments can best be made and used. Like reference numerals are used throughout the description and several views of the drawings to indicate like or corresponding parts, wherein the various elements are not necessarily drawn to scale. Referring now to the drawings, and more particularly to <figref idrefs="DRAWINGS">FIG. 1</figref>, depicted therein is an exemplary generalized network environment <b>100</b> wherein an embodiment of the present patent disclosure may be practiced. A user equipment (UE) device <b>102</b> may comprise any portable computer (e.g., laptops, palmtops, or handheld computing devices) or a mobile communications device (e.g., cellular phones or data-enabled handheld devices capable of receiving and sending messages, web browsing, et cetera), or any enhanced personal digital assistant (PDA) device or integrated information appliance capable of email, video mail, Internet access, corporate data access, messaging, calendaring and scheduling, information management, and the like, that is preferably operable in one or more modes of operation and in a number of frequency bands. For example, UE device <b>102</b> may operate in the cellular telephony band frequencies as well as Wireless Local Area Network (WLAN) bands. Further, other bands in which the UE device could operate wirelessly may comprise Wi-Max bands or one or more satellite bands. By way of illustration, the network environment <b>100</b> is envisioned as two broad categories of communication spaces capable of providing service to UE device <b>102</b> wherein acquisition of network advertisement information may be accomplished in accordance with the teachings set forth herein. In wide area cellular network (WACN) space <b>104</b>, there may exist any number of Public Land Mobile Networks (PLMNs) that are operable to provide cellular telephony services which may or may not include packet-switched data services. Depending on the coverage area(s) and whether the user is roaming, WACN space <b>104</b> can include a number of home networks <b>110</b> (i.e., home PLMNs or HPLMNs, or equivalent HPLMNs or EHPLMNs), visited networks (i.e., VPLMNs) <b>112</b>, each with appropriate infrastructure such as Home Location Register (HLR) nodes <b>115</b>, Mobile Switching Center (MSC) nodes <b>116</b>, and the like. Since the WACN space <b>104</b> may also include a General Packet Radio Service (GPRS) network that provides a packet radio access for mobile devices using the cellular infrastructure of a Global System for Mobile Communications (GSM)-based carrier network, a Serving GPRS Support Node (SGSN) <b>114</b> is exemplified therein. Additionally, by way of generalization, the PLMNs of the WACN space <b>104</b> may comprise radio access and core networks selected from the group comprising Enhanced Data Rates for GSM Evolution (EDGE) networks, Integrated Digital Enhanced Networks (IDENs), Code Division Multiple Access (CDMA) networks, Time Division Multiple Access (TDMA) networks, Universal Mobile Telecommunications System (UMTS) networks, or any 3<sup>rd </sup>Generation Partnership Project (3GPP)-compliant network (e.g., 3GPP or 3GPP2), all operating with well known frequency bandwidths and protocols.
Further, UE device <b>102</b> is operable to obtain service from an access network (AN) space <b>106</b> that is connected to the WACN space <b>104</b>. In one implementation, the AN space <b>106</b> includes one or more generic access networks (GANs) <b>118</b> as well as any type of wireless LAN (WLAN) arrangements <b>120</b>, both of which may be generalized as any wireless AN that is operable to provide access services between UE device <b>102</b> and a PLMN core network using a broadband Internet Protocol (IP)-based network. WLAN arrangements <b>120</b> provide short-range wireless connectivity to UE device <b>102</b> via access points (APs) or “hot spots,” and can be implemented using a variety of standards, e.g., IEEE 802.11b, IEEE 802.11a, IEEE 802.11g, HiperLan and HiperLan II standards, Wi-Max standard, OpenAir standard, and the Bluetooth standard.
In one embodiment, interfacing between the WACN and AN spaces may be effectuated in accordance with certain standards. For instance, GAN <b>118</b> may be interfaced with one or more PLMNs using the procedures set forth in the 3GPP TR 43.901 and 3GPP TS 43.xxx documents as well as related documentation. Likewise, WLAN <b>120</b> may be interfaced with at least one PLMN core using the procedures set forth in the 3GPP TS 22.234, 3GPP TS 23.234 and 3GPP TS 24.234 documents as well as related documentation, and may therefore be referred to as an Interworking WLAN (I-WLAN) arrangement.
Based on the foregoing, it should be recognized that the service infrastructure of the network environment <b>100</b> may be generalized into three broad segments: one or more radio access network (RANs) (which can include cellular band technologies as well as WLAN technologies), one or more core networks (CNs), and one or more service network (SNs). Depending on network ownership arrangements and service-level agreements, each RAN may support one or more CNs, each of which in turn may support one or more SNs. Such combinations of infrastructure equipment across multiple owners is sometimes used to create Mobile Virtual Network Operators (MVNOs). The teachings of the present patent disclosure are equally applicable to MVNOs as to PLMNs. Since each RAN, CN, or SN may be provided with its own network identifier (ID code), and further because of the numerous RAN-CN-SN combinations available in the network environment <b>100</b>, traditional broadcasting of a single broadcast identifier for providing network advertisement information becomes unworkable.
To formalize the teachings of the present disclosure, reference is now taken to <figref idrefs="DRAWINGS">FIG. 2</figref> wherein an exemplary embodiment of a network environment <b>200</b> is shown that is a more concrete subset of the generalized network environment <b>100</b> illustrated in <figref idrefs="DRAWINGS">FIG. 1</figref>. As depicted, wireless UE device <b>102</b> is operably disposed for acquiring network advertisement information from a RAN segment <b>202</b> that is coupled to a CN segment <b>204</b> which in turn is coupled to an SN segment <b>206</b>. Three RANs are illustrative: RAN-<b>1</b><b>208</b>-<b>1</b>, RAN-<b>2</b><b>208</b>-<b>2</b> and RAN-<b>3</b><b>208</b>-<b>3</b>, which are identified with the network codes MANC<b>1</b>, MANC<b>2</b> and MANC<b>3</b>, respectively. The CN segment <b>204</b> is also illustrated with three CNs: CN-<b>1</b><b>210</b>-<b>1</b> (having an ID code of MCNC<b>1</b>), CN-<b>2</b><b>210</b>-<b>2</b> (having an ID code of MCNC<b>2</b>) and CN-<b>3</b><b>210</b>-<b>3</b> (having an ID code of MCNC<b>3</b>). Likewise, the SN segment <b>206</b> is illustrated with SN-<b>1</b><b>212</b>-<b>1</b> (having an ID code of MSNC<b>1</b>), SN-<b>2</b><b>212</b>-<b>2</b> (having an ID code of MSNC<b>2</b>) and SN-<b>3</b><b>212</b>-<b>3</b> (having an ID code of MSNC<b>3</b>).
By way of example, RAN-<b>1</b><b>208</b>-<b>1</b> is operable to support connectivity to two CNs, CN-<b>1</b><b>210</b>-<b>1</b> and CN-<b>2</b><b>210</b>-<b>2</b>. In similar fashion, RAN-<b>2</b><b>208</b>-<b>2</b> supports three CNs and RAN-<b>3</b><b>208</b>-<b>3</b> supports only one CN. Each CN supports connectivity to one or more SNs: e.g., CN-<b>3</b><b>210</b>-<b>3</b> connects to SN-<b>2</b><b>212</b>-<b>2</b> as well as SN-<b>3</b><b>212</b>-<b>3</b>. Given the interconnectivity of the RAN/CN/SN segments, several combinations of identification codes may be obtained for purposes of uniquely identifying the various RAN-CN-SN combinations that the wireless UE device <b>102</b> can potentially discover and select from. For instance, with a suitable Mobile Country Code (MCC) being included, the three ID code combinations associated with RAN-<b>1</b><b>208</b>-<b>1</b> are: <ul><li id="ul0001-0001" num="0000"><ul><li id="ul0002-0001" num="0027">[MCC.MANC<b>1</b>.MCNC<b>1</b>.MSNC<b>1</b>];</li><li id="ul0002-0002" num="0028">[MCC.MANC<b>1</b>.MCNC<b>1</b>.MSNC<b>2</b>]; and</li><li id="ul0002-0003" num="0029">[MCC.MANC<b>1</b>.MCNC<b>2</b>.MSNC<b>2</b>].</li></ul></li></ul>
Likewise, the ID code combinations associated with RAN-<b>2</b><b>208</b>-<b>2</b> are: <ul><li id="ul0003-0001" num="0000"><ul><li id="ul0004-0001" num="0031">[MCC.MANC<b>2</b>.MCNC<b>1</b>.MSNC<b>1</b>];</li><li id="ul0004-0002" num="0032">[MCC.MANC<b>2</b>.MCNC<b>1</b>.MSNC<b>2</b>];</li><li id="ul0004-0003" num="0033">[MCC.MANC<b>2</b>.MCNC<b>2</b>.MSNC<b>2</b>];</li><li id="ul0004-0004" num="0034">[MCC.MANC<b>2</b>.MCNC<b>3</b>.MSNC<b>2</b>]; and</li><li id="ul0004-0005" num="0035">[MCC.MANC<b>2</b>.MCNC<b>3</b>.MSNC<b>3</b>].</li></ul></li></ul>
The two ID code combinations associated with RAN-<b>3</b><b>208</b>-<b>3</b> are: [MCC.MANC<b>3</b>.MCNC<b>3</b>.MSNC<b>2</b>] and [MCC.MANC<b>3</b>.MCNC<b>3</b>.MSNC<b>2</b>]. As will be described in detail hereinbelow, a number of options are available for providing the applicable network ID code information to the UE device <b>102</b> either in an initial scan procedure (i.e., when the device is not registered on any networks) or in a background scan procedure (i.e. when the device is registered on a network).
Further, a network advertisement broker (NAB) entity <b>214</b> is disposed in the network environment <b>200</b> that is operable as a depository of various RAN-CN-SN ID code combinations as well as information relating to supported services, capabilities, et cetera, on a network-by-network basis. For instance, a database structure associated with NAB <b>214</b> can contain RAN IDs, CN IDs to which each RAN is connected, services supported by each RAN, other access networks supported or operated by a RAN (i.e., which could be any radio technology such as 3GPP, 3GPP2, or any IEEE-based WLAN, as alluded to in the foregoing discussion), and the like, any or all of which information may be updated periodically or as needed. Additionally, depending on implementation, NAB <b>214</b> may be associated with a RAN, a CN, or an SN, or in any combination thereof. In a still further embodiment, NAB <b>214</b> may be provided as a third-party entity accessible via a public packet-switched Internet Protocol (IP) network portion <b>216</b>, e.g., the Internet.
Another brokering entity <b>218</b>, referred to as a roaming broker (RB), is also disposed in the network environment <b>200</b> for providing additional capabilities with respect to optimizing network selection by the UE device, particularly where roaming is involved. As will be seen in detail hereinbelow, one or more database structures associated with RB <b>218</b> may be provisioned with service relationship data and service status data pertaining to the networks that have direct or indirect visitor service arrangements with the UE device's home networks. Appropriate service logic provided at RB <b>218</b> may accordingly be executed for purposes of adapting network selection based on input forwarded by the UE device <b>102</b>. Similar to the NAB implementation, RB <b>218</b> may be associated with a home network or a visited network, including a RAN, a CN, or an SN, or in any combination thereof. In a still further embodiment, RB <b>218</b> may be provided as a third-party entity accessible via a public packet-switched Internet Protocol (IP) network portion <b>220</b>, e.g., the Internet.
Referring now to <figref idrefs="DRAWINGS">FIG. 3</figref>, depicted therein is an exemplary database structure <b>300</b> provided as part of a NAB entity in accordance with the teachings of the present patent disclosure. Based on the scope of coverage of the database as well as any third-party commercial arrangements, the database structure <b>300</b> may be provisioned with the data pertaining to a fairly large number of RANs. Reference numeral <b>302</b> refers to one or more RANs identified by their RAN ID codes. Services supported by each RAN are identified in column <b>304</b>. For example, RAN-<b>1</b> is operable to support High Speed Datalink Packet Access (HSDPA), EDGE, and the like. Cross-relationship or interoperability of a particular RAN with other access networks is indicated in column <b>306</b>. As illustrated, RAN-<b>1</b> interoperates with additional RANs, RAN-X, RAN-Y, and RAN-Z, as well as WLANs, WLAN-A and WLAN-C. Reference numeral <b>308</b> refers to the core networks supported by each particular RAN identified in column <b>302</b>. Reference numeral <b>310</b> refers to the various services supported by each CN, such as, e.g., IP Multimedia Subsystem (IMS), Presence, Push-to-Talk over Cellular (PoC), and the like.
In accordance with the teachings of the present patent disclosure, at least three options are available for providing network advertisement information (i.e., information indicating which networks and network combinations are available to a wireless device): <ul><li id="ul0005-0001" num="0000"><ul><li id="ul0006-0001" num="0041">Broadcast on a per RAN basis. In this option, existing broadcast messages may be expanded or additional broadcast messages be created to carry the combinations of network ID codes.</li><li id="ul0006-0002" num="0042">Broadcast all available networks and network combinations via a beacon channel which may be provided by a third-party, e.g., a public body, a consumer group, etc.</li><li id="ul0006-0003" num="0043">Provided via querying a NAB entity.</li></ul></li></ul>
<figref idrefs="DRAWINGS">FIG. 4</figref> depicts an exemplary message flow diagram of the present patent disclosure for acquiring network advertisement information according to one embodiment where advertisement messages are broadcast from RANs. One or more RANs <b>404</b> are operable to broadcast information via associated control channels over the air interface <b>402</b>. In one arrangement, the RAN nodes <b>404</b> may comprise Base Transceiver Station (BTS) nodes deployed in various cellular networks. Reference numerals <b>406</b>-<b>1</b> through <b>406</b>-N refer to the control channel messages that are broadcast by the network nodes at a designated repetition rate. In one implementation, the broadcast information may include network ID code combination information (i.e., identity information), capability information, adjacent cell information, among other types of information. UE <b>102</b> is operable to read the broadcast information over the air interface <b>402</b> and based at least in part upon the received advertisement information, appropriate network selection may be carried out which may be mediated through application of such preferences and prohibitions as may be configured by the subscriber, network operators, and the like.
In one implementation, the various RAN-CN-SN ID code combinations may be transmitted in their entirety. That is, each RAN-CN-SN ID code combination is completely resolved and transmitted explicitly. For example, each of the three combinations [MCC.MANC<b>1</b>.MCNC<b>1</b>.MSNC<b>1</b>]; [MCC.MANC<b>1</b>.MCNC<b>1</b>.MSNC<b>2</b>]; and [MCC.MANC<b>1</b>.MCNC<b>2</b>.MSNC<b>2</b>] provided in association with RAN-<b>1</b> of <figref idrefs="DRAWINGS">FIG. 2</figref> may be broadcast by RAN-<b>1</b> in complete form. In another implementation, each CN may advertise all SN ID codes it supports. For instance, the [MCC.MANC<b>1</b>.MCNC<b>1</b>.MSNC<b>1</b>:MSNC<b>2</b>] combination format indicates that both MSNC<b>1</b> and MSNC<b>2</b> are supported by the CN identified by MCNC<b>1</b>.
As alluded to before, for each network there is a corresponding broadcast message that defines the services that are available. In one aspect, UE <b>102</b> can also request the services information by transmitting a particular ID code combination (e.g., [MCC.MANC<b>1</b>.MCNC<b>1</b>.MSNC<b>2</b>]) to the appropriate network node to obtain such information. Additionally, the ID code information as well as the services information may be provided to the individual RANs by one or more NABs for broadcasting.
<figref idrefs="DRAWINGS">FIG. 5</figref> depicts an exemplary message flow diagram of the present patent disclosure for acquiring network advertisement information according to another embodiment. As before, UE <b>102</b> is operable to read broadcast messages over the air interface <b>402</b> from the individual RANs. Using such applicable selection filters (e.g., positive filters (i.e., preferences) as well as negative filters (i.e., prohibitions)) as may be configured on the device, a particular RAN may be selected (block <b>506</b>). Thereafter, the device/user is authenticated by engaging in an authentication mechanism <b>508</b> with an Authentication, Authorization and Accounting (AAA) server <b>504</b>. Upon successful authentication, the RAN is operable to permit the device to contact a suitable NAB, e.g., NAB <b>214</b>, using the NAB's IP address. In one implementation, the IP address may be obtained via a Fully Qualified Domain Name (FQDN) query initiated by the device, wherein the FQDN is constructed using the RAN's a Mobile Country Code (MCC) and Mobile Network Code (MNC). In another implementation, the AAA server <b>504</b> may provide the IP address or FQDN. Reference numerals <b>510</b> and <b>512</b> refer to a IP address request via FQDN query to a domain name server (DNS) <b>502</b> and the response therefrom. Once the NAB's IP address is available to UE device <b>102</b>, it then contacts NAB <b>214</b> via a request message <b>514</b> and obtains the requisite NAB information via a reply <b>516</b>. As part the request message <b>514</b>, UE device <b>102</b> may include any or all of the following data: subscriber ID (e.g., International Mobile Subscriber Identity (IMSI) which is constructed as [MCC] [MNC] [MIN] in GSM, where [MCC] identifies the country that the subscriber is from, [MNC] identifies the PLMN network, and [MIN] is the unique ID that identifies the wireless UE device), network ID, (e.g., Cell Global Identification (CGI) or System Identification (SID)), network IDs of other networks, location information of the wireless UE device (e.g., Global Positioning System or GPS coordinates), media access control (MAC) addresses of available access points, and MAC address of the wireless UE device.
As part of the reply message <b>516</b>, NAB <b>214</b> is operable to transmit the stored RAN-CN-SN ID information as well as the services and capabilities associated therewith. Based on the geographic location information of the wireless UE device, the NAB information may be appropriately customized. Upon receipt of the requisite information, the wireless UE device <b>102</b> may store it locally.
<figref idrefs="DRAWINGS">FIG. 6</figref> is a flowchart associated with an embodiment of the method described hereinabove. At block <b>602</b>, the wireless UE device is operable to scan for available RANs including WLANs in one or more frequency bands and in one or more radio access technologies, depending on the device configuration, et cetera. For example, it is possible to configure the wireless UE device for a number of technology modes that are used, wherein the configuration information may be stored as an elementary file (EF) structure on a Subscriber Identity Module (SIM) card or Removable User Identity Module (RUIM) card operable with the device and/or as part of a managed object information tree. Other removable memory forms may include compact Flash, secure SD, et cetera. In another embodiment, such data could be stored in a fixed memory module integrated with the device. Additionally, the device configuration data may be modified by the network operator via an Over the Air (OTA) mechanism such as Short Message Service (SMS), Cell Broadcast, Multimedia Broadcast/Multicast Service (MBMS), or Unstructured Supplementary Service Data (USSD). In a still further embodiment, it may be possible for the subscriber to modify the device configuration data.
Given the diversity of the exemplary network environment <b>100</b> described earlier with respect to <figref idrefs="DRAWINGS">FIG. 1</figref>, it is envisaged that scanning may be effectuated in a frequency band in which at least one of the following technologies is operating: GERAN (without EDGE), GERAN (with EDGE), an IDEN network, a CDMA/CDMA2000/TDMA network, a UMTS network, and so on. Additionally, scanning may be effectuated in a frequency band compliant with a WLAN standard selected from: IEEE 802.11b standard, IEEE 802.11a standard, IEEE 802.11g standard, HiperLan standard, HiperLan II standard, Wi-Max standard, OpenAir standard, and Bluetooth standard. Further, the UE device includes logic for selecting a RAN based at least in part upon the network information obtained via scanning. Thereafter, an authentication mechanism using AAA is employed for authenticating the device and subscriber (block <b>604</b>). The IP address of suitable NAB is obtained using, e.g., FQDN (block <b>606</b>). Subsequently, the NAB is contacted using the IP address obtained in block <b>606</b>, whereupon appropriate network advertisement information including services/capabilities information may be obtained from the NAB. As alluded to previously, such information may be customized based on the geographic location of the device, for example. These operations are illustrated in blocks <b>608</b> and <b>610</b>.
<figref idrefs="DRAWINGS">FIG. 7</figref> depicts an exemplary database structure <b>700</b> that may be provided as an operated-based list, a user-based list or an enterprise-based list, or any combination thereof, for configurably setting network selection preferences and prohibitions according to one aspect of the present patent disclosure. In one embodiment, the database structure <b>700</b> is configured as an operator-defined network list that specifies a plurality of network IDs which should be considered as preferred networks in one or more radio access technologies, wherein the network IDs are populated by the operator. In another embodiment, the database structure <b>700</b> may be configured as one or more user network lists, with one list per user using the wireless UE device, for example. Each such list may be accessed by the users upon identifying themselves to the device, wherein the contents of the list (i.e., network IDs) are populated by the respective users. In yet another embodiment, the database structure <b>700</b> may be configured as a list of network IDs that are preferred by an enterprise owning the wireless devices for the benefit of its employee-users.
Irrespective of the particular configuration, the database structure <b>700</b> defines a plurality of radio access technologies, e.g., EDGE technology <b>702</b>A, WLAN technology <b>702</b>B, and UMTS technology <b>702</b>C, wherein a number of RAN IDs are provided for each technology. As illustrated in <figref idrefs="DRAWINGS">FIG. 7</figref>, column <b>704</b>A identifies multiple RAN IDs for the EDGE technology, each RAN supporting one or more core networks identified in corresponding column <b>706</b>A. Likewise columns <b>704</b>B/<b>706</b>B and columns <b>704</b>C/<b>706</b>C are provided for the WLAN and UMTS technologies respectively. As one skilled in the art may appreciate, the various IDs can be Service Set IDs (SSIDs) (for WLAN), SIDs (for IS-95 and IS-136), or [MCC,MNC] combinations (for GSM).
Similar to the network preference lists set forth above, an analogous database structure may be provided that identifies one or more networks that are forbidden for use. Such a list of prohibited networks may be configured as, for example, an operator-barred RAN list (i.e., specified by an operator), enterprise-barred RAN list (i.e., specified by an enterprise), operator-barred CN list (i.e., specified by an operator), and enterprise-barred CN list (i.e., specified by an enterprise).
In addition to one or more of the embodiments and configurations of the database structures identifying network preferences and prohibitions, one or more home network lists (including equivalent home networks) may be provided for facilitating network selection in conjunction with a network entity such as RB <b>218</b> (shown in <figref idrefs="DRAWINGS">FIG. 2</figref>). As is well known, each of the wide area cellular PLMNs may be arranged as a number of cells, with each cell having sectors (e.g., typically three 120-degree sectors per base station (BS) or cell). Each individual cell is provided with a CGI parameter to identify them. A group of cells is commonly designated as a Location Area (LA) and may be identified by an LA Identifier (LAI). At the macro level, the PLMNs may be identified in accordance with the underlying cellular technology. For example, as alluded to before, GSM-based PLMNs may be identified by an identifier comprised of a combination of MCC and MNC. The CDMA/TDMA-based PLMNs may be identified by a SID parameter and/or a Network Identification (NID) parameter. Regardless of the cellular infrastructure, all cells broadcast the macro level PLMN identifiers such that a wireless device (e.g., UE device <b>102</b>) wishing to obtain service can identify the wireless network.
Additionally, a subscriber is also given a unique identifier which can vary depending on the underlying cellular infrastructure and may be constructed at least in part from some of the parametrics that are used in constructing the network identifiers. In GSM, for example, the subscriber's IMSI parameter is constructed as [MCC] [MNC][MIN].
For purposes of illustration, the embodiments of home network identifiers of the present patent disclosure will be particularly exemplified in reference to GSM networks, although it should be appreciated that the teachings set forth herein may be applied mutatis mutandis in other cellular networks as well. <figref idrefs="DRAWINGS">FIGS. 8A and 8B</figref> depict exemplary database structures which may be provided with a UE device for facilitating network selection in conjunction with an RB entity according to one embodiment. Reference numeral <b>800</b>A refers to a basic database structure that comprises a list of [MCC] <b>802</b>A and [MNC] <b>802</b>B combinations that may be identified as being the same networks. In the case of equivalent networks, the [MCC] [MNC] combinations may identify a set of EHPLMNs for the IMSI associated with the subscriber. Reference numerals <b>804</b>, <b>806</b> and <b>808</b> refer to three exemplary networks, wherein networks <b>804</b> and <b>806</b> share the same [MCC], i.e., [ABC], and networks <b>804</b> and <b>808</b> share the same [MNC] (i.e., [XYZ]). In one exemplary embodiment, the data structure <b>800</b>A may be stored on a SIM/RUIM card of the device. In another embodiment, the data structure <b>800</b>A could be stored in a fixed memory module integrated with the wireless UE device.
Reference numeral <b>800</b>B refers to an enhanced database structure where additional information may be provided for facilitating network selection. A Master [MCC][MNC] column <b>820</b> identifies the [MCC] and [MNC] combinations that match the IMSI's [MCC]/[MNC] part (i.e., Master Home PLMN). A network name column <b>822</b> identifies the master network by name. A home network (EHPLMN) column <b>824</b> includes a list of home networks for each of the Master [MCC] [MNC] pairs. In one implementation, the [MCC] [MNC] combinations identifying the home networks may be provided in a priority order. For example, a positional priority may be implemented wherein an [MCC] [MNC] combination at the top has a higher priority over the one below it, or an [MCC] [MNC] combination to the left has a higher priority over the one to the right. An explicit priority ranking may also be provided wherein an indicator indicating the priority of the PLMN is appended to the database structure <b>800</b>B. For instance, a value of [0] may indicate the highest priority. Where there is no priority indicator stored, all PLMNs have equal priority. An indicium column <b>825</b> is provided for uniquely identifying each PLMN listed in the home network list <b>824</b>, wherein the indicium may comprise a unique identity name that can include some reference to the Master [MCC] [MNC] pair or the network name associated therewith. As before, the data structure <b>800</b>B may be provided as part of a removable card or within a storage module integrated with the wireless UE device.
In one implementation, the wireless UE device is operable upon power-up to determine the capability of the SIM/RUIM card that has been inserted into it. If the wireless device discovers that the SIM/RUIM card contains a list of EHPLMNs, the device uses the list for subsequent network selection operations. If the SIM/RUIM card does not contain a list of PLMNs, the wireless device is operable to read the IMSI of the subscriber. Thereafter, if the wireless device is provided with stored home network lists in its memory for the [MCC] [MNC] pairs of the IMSI, the stored PLMN database may then be used to find the list of HPLMNs associated with a particular IMSI. Otherwise, the wireless UE device is operable to perform network scanning and discovery procedures as currently specified.
Given that there are a number of lists that could be used in the radio part, appropriate intelligence or logic may be provided as part of the wireless UE device in order to resolve priority among various radio access technologies, preferences and prohibitions. Where the wireless device is operable in multiple modes (i.e., different technologies), a particular mode may be designated as its primary operating mode (highest priority). Secondary and tertiary operating modes may be accorded lower priorities accordingly. Again, it is envisaged that the operating modes may be configured or reconfigured dynamically, based on operator-defined criteria, subscriber-defined criteria, or enterprise-defined criteria. Some exemplary parameters used in controlling the operating mode may be: device location information (e.g., GPS information), SSIDs, SIDs, [MCC,MNC] combinations, cell IDs, and the like. Additionally, certain override criteria may be provided for operators, enterprises or subscribers (i.e., for hard set). In one implementation, the interaction of these parameters defines when a particular technology takes either primary, secondary, or tertiary operating mode. Each defined parameter may be provisioned with a flag associated therewith, indicating whether the defined condition has to occur in order to set an operating mode. For example, consider that the wireless UE device discovers a specific cell ID upon performing an initial scan. It is assumed that the subscriber has defined the condition that if a home SSID is found in this cell, WLAN is to be set as the primary operating mode. Accordingly, the device's primary mode would be set to WLAN in this particular cell provided the home SSID has been found, and the secondary mode may be set to GSM.
In addition to the provisioning of various preferred and barred network lists (which can be device-centric, network-centric, or subscriber-centric), each country has its own regulatory requirements as to which list should take precedence. An enterprise company for instance may forbid access to a public WLAN access point that operates in the vicinity of the company's premises. Moreover, certain device logic may be necessary for specifying the scanning behavior as well, since there may be a number of bands on per-technology basis in which the device is capable of scanning. Additional details regarding list order prioritization and scanning procedures may be found in the following commonly owned co-pending U.S. patent application entitled “SYSTEM AND METHOD FOR PROVIDING NETWORK ADVERTISEMENT INFORMATION VIA A NETWORK ADVERTISEMENT BROKER (NAB),” filed Apr. 28, 2005 herewith Ser. No. 11/116,470 and cross-referenced hereinabove.
<figref idrefs="DRAWINGS">FIG. 9</figref> depicts an exemplary database structure <b>900</b> provided as part of an RB node (e.g., RB <b>218</b> in <figref idrefs="DRAWINGS">FIG. 2</figref>) in accordance with the teachings of the present patent disclosure. Reference numeral <b>902</b> refers to a column of networks that have direct visitor relationships to one or more home networks (including equivalent home networks) defined for a wireless UE device and/or subscriber. In other words, the networks identified in column <b>902</b> are visited networks that provide roaming services to the home networks. As illustrated, these visited networks may comprise just the access networks (e.g., access networks identified as [MCCb.MANCc] and [MCCd.MANCa]) as well as network combinations that can include CNs and SNs. Column <b>904</b> identifies access networks having with relationships with the visited core networks identified in column <b>902</b>. Column <b>906</b> provides status information with respect to indicating whether the identified radio/core network combinations are known to be operational. For instance, a service status flag such as “ON” or “OFF” may be provided to indicate if a particular network combination (e.g., a RAN/CN combination) is in service or not. Additionally, column <b>908</b> of the RB database structure provides services and capabilities supported on the visited networks that are identified in column <b>902</b>.
As set forth previously, various network preferences and barred lists (which may be embodied as the database structure <b>700</b> shown in <figref idrefs="DRAWINGS">FIG. 7</figref>) can be provisioned both in the device as well as in a network node in accordance with the teachings of the present disclosure for effectuating network selection. Provisioning of such lists in a wireless UE device facilitates initial discovery and selection of a particular network combination (i.e., a RAN/CN combination), whereupon the device may query a network entity such as the RB node that includes one or more network selection lists for additional information. <figref idrefs="DRAWINGS">FIG. 10</figref> depicts an exemplary message flow diagram for interacting with an RB node according to one embodiment. Upon obtaining network advertisement information (either by monitoring broadcast control channels of individual RANs, or via a beacon channel, or by contacting NAB <b>214</b>), UE <b>102</b> is operable to select a particular network combination in accordance with a preconfigured selection logic (block <b>1002</b>). Thereafter, an FQDN query <b>1004</b> may be forwarded to DNS <b>502</b> in order to obtain an IP address of RB <b>218</b> via a response <b>1006</b>. Alternatively, a previously cached IP address may be obtained for contacting RB <b>218</b>. Additionally or alternatively, there may be a suitable AAA-based authentication mechanism in place similar to the UE-NAB interaction scheme described previously. Irrespective of how the IP address is obtained, UE <b>102</b> registers with RB <b>218</b> using a registration message <b>1008</b> which includes transmitting various pieces of information such as: identity information of the particular RAN/CN used for accessing RB <b>218</b>, network advertisement information obtained from NAB <b>214</b>, identity information and capability information of each network combination discovered by UE <b>102</b>, location data of UE <b>102</b> (e.g., GPS coordinates), MAC) addresses of available WLAN access points or hot spots, MAC address and capabilities of UE <b>102</b>, and services that UE <b>102</b> wants to use. Responsive to the received information from UE <b>102</b>, appropriate service logic <b>1010</b> provided at RB <b>218</b> determines if the particular network combination initially selected by UE <b>102</b> at block <b>1002</b> is the optimal network. A redirect message <b>1012</b> may be generated by RB <b>218</b> toward UE <b>102</b>, which includes identity information of a more suitable network combination if so determined. The redirect message <b>1012</b> may instruct the device to change access networks, core networks, etc. In addition, various pieces of capabilities information and additional network ID information may be transmitted by RB <b>218</b> which the device may want to use later. The RB may also signal back different background scan timers for each technology the wireless device supports. These actions are exemplified in <figref idrefs="DRAWINGS">FIG. 10</figref> by way of signaling messages <b>1014</b> and <b>1016</b>, respectively.
Referring now to <figref idrefs="DRAWINGS">FIG. 11</figref>, shown therein is a flowchart associated with the method described above. At block <b>1102</b>, identity information of a particular RAN/CN network combination is obtained by the wireless UE device. Thereafter, the IP address of applicable RB node is obtained (block <b>1104</b>). Upon registration with the RB node using the IP address, network discovery and advertisement information is transmitted to the RB node (block <b>1106</b>). As pointed out in the foregoing, various additional pieces of information may be transmitted also. A determination is made at the RB node if an additional network or a network combination is more suitable to the wireless device. Responsive to the determination, a redirect message including the additional network's ID information and/or network capability and services information is returned to the wireless device (block <b>1108</b>). In one embodiment, the information provided by the RB node may be customized based on the wireless device's geographic location. Responsive to the received information, the wireless device employs appropriate logic to select the additional RAN/CN or the previous network combination for obtaining service (block <b>1110</b>).
<figref idrefs="DRAWINGS">FIG. 12</figref> depicts a block diagram of an embodiment of a wireless device <b>1200</b> operable to acquire network advertisement information and perform network selection according to the teachings of the present patent disclosure. It will be recognized by those skilled in the art upon reference hereto that although an embodiment of UE <b>102</b> may comprise an arrangement similar to one shown in <figref idrefs="DRAWINGS">FIG. 12</figref>, there can be a number of variations and modifications, in hardware, software or firmware, with respect to the various modules depicted. Accordingly, the arrangement of <figref idrefs="DRAWINGS">FIG. 12</figref> should be taken as illustrative rather than limiting with respect to the embodiments of the present patent disclosure. A microprocessor <b>1202</b> providing for the overall control of UE <b>1200</b> is operably coupled to a communication subsystem <b>1204</b> which includes transmitter/receiver (transceiver) functionality for effectuating multi-mode communications over a plurality of bands. By way of example, a wide area wireless Tx/Rx module <b>1206</b> and a wireless AN Tx/Rx module <b>1208</b> are illustrated. Although not particularly shown, each Tx/Rx module may include other associated components such as one or more local oscillator (LO) modules, RF switches, RF bandpass filters, A/D and D/A converters, processing modules such as digital signal processors (DSPs), local memory, etc. As will be apparent to those skilled in the field of communications, the particular design of the communication subsystem <b>1204</b> may be dependent upon the communications networks with which the UE device is intended to operate. In one embodiment, the communication subsystem <b>1204</b> is operable with both voice and data communications.
Microprocessor <b>1202</b> also interfaces with further device subsystems such as auxiliary input/output (I/O) <b>1218</b>, serial port <b>1220</b>, display <b>1222</b>, keyboard <b>1224</b>, speaker <b>1226</b>, microphone <b>1228</b>, random access memory (RAM) <b>1230</b>, a short-range communications subsystem <b>1232</b>, and any other device subsystems generally labeled as reference numeral <b>1233</b>. To control access, a SIM/RUIM interface <b>1234</b> is also provided in communication with the microprocessor <b>1202</b>. In one implementation, SIM/RUIM interface <b>1234</b> is operable with a SIM/RUIM card having a number of key configurations <b>1244</b> and other information <b>1246</b> such as identification and subscriber-related data as well as one or more SSID/PLMN lists and filters described in detail hereinabove.
Operating system software and other control software may be embodied in a persistent storage module (i.e., non-volatile storage) such as Flash memory <b>1235</b>. In one implementation, Flash memory <b>1235</b> may be segregated into different areas, e.g., storage area for computer programs <b>1236</b> as well as data storage regions such as device state <b>1237</b>, address book <b>1239</b>, other personal information manager (PIM) data <b>1241</b>, and other data storage areas generally labeled as reference numeral <b>1243</b>. Additionally, appropriate network discovery/selection logic <b>1240</b> may be provided as part of the persistent storage for executing the various procedures, NAB information acquisition techniques, and network selection mechanisms set forth in the preceding sections. Logic for effectuating appropriate DNS queries, authentication, and NAB/RB queries is also exemplified as a logic module <b>1245</b>. Associated therewith is a storage module <b>1238</b> for storing the SSID/PLMN lists, selection/scanning filters, capability indicators, et cetera, also described in detail hereinabove.
In view of the teachings set forth herein, the various logic blocks of UE device <b>1200</b> should be understood as comprising at least the following: a logic module operable to obtain identity information of a particular network combination available in a geographic location; a logic module operable to transmit network advertisement information to an RB node disposed in the network environment upon registration therewith; and a logic module operable to select one of the particular network combination and an additional network or network combination provided by the RB via a redirect message, wherein the RB includes service logic for determining if the additional network or network combination is more suitable to the wireless UE device <b>1200</b>, the redirect message including identity information of the additional network/combination.
It is believed that the operation and construction of the embodiments of the present patent application will be apparent from the Detailed Description set forth above. While the exemplary embodiments shown and described may have been characterized as being preferred, it should be readily understood that various changes and modifications could be made therein without departing from the scope of the present invention as set forth in the following claims.
Contents5
13 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13
Every citation, both waysCites: the store holds 57 of 58
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US8510822B2 | Cited by | United States of America | Search report |
| US12367031B2 | Cited by | United States of America | Applicant |
| US2011237271A1 | Cited by | United States of America | Pre-grant |
| US11765052B1 | Cited by | United States of America | Applicant |
| US12418850B2 | Cited by | United States of America | Applicant |
| US9253589B2 | Cited by | United States of America | Search report |
| US10452654B2 | Cited by | United States of America | Applicant |
| US12225623B2 | Cited by | United States of America | Applicant |
| US8185109B2 | Cited by | United States of America | Search report |
| US2011173105A1 | Cited by | United States of America | Pre-grant |
| US11129123B2 | Cited by | United States of America | Applicant |
| US9934271B2 | Cited by | United States of America | Search report |
| US2008311907A1 | Cited by | United States of America | Pre-grant |
| US9119139B2 | Cited by | United States of America | Applicant |
| US10034260B2 | Cited by | United States of America | Applicant |
| US2012203763A1 | Cited by | United States of America | Pre-grant |
| US8165584B2 | Cited by | United States of America | Search report |
| US2013237148A1 | Cited by | United States of America | Pre-grant |
| US9155033B2 | Cited by | United States of America | Applicant |
| US2010107237A1 | Cited by | United States of America | Pre-grant |
| WO0105174A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| WO03096578A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| EP1104975A2 | Cites | European Patent Office (EPO) | Applicant |
| EP1213941A2 | Cites | European Patent Office (EPO) | Applicant |
| CA1270742A | Cites | Canada | Applicant |
| CN1430840A | Cites | China | Applicant |
| US2002101858A1 | Cites | United States of America | Applicant |
| US2002119774A1 | Cites | United States of America | Search report |
| US2002178118A1 | Cites | United States of America | Applicant |
| US2003017828A1 | Cites | United States of America | Applicant |
| US2003120541A1 | Cites | United States of America | Applicant |
| US2003142641A1 | Cites | United States of America | Search report |
| WO2004014862A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| WO2004047476A1 | Cites | World Intellectual Property Organization (WIPO) | Search report |
| WO2004047476A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| US2004110523A1 | Cites | United States of America | Search report |
| WO2005002140A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| WO2005027557A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| US2006246889A1 | Cites | United States of America | Applicant |
| US2008032736A1 | Cites | United States of America | Applicant |
| US2009222566A1 | Cites | United States of America | Applicant |
| GB2352586A | Cites | United Kingdom | Applicant |
| US5027388A | Cites | United States of America | Applicant |
| US5420914A | Cites | United States of America | Applicant |
| US5594949A | Cites | United States of America | Search report |
| US5623535A | Cites | United States of America | Search report |
| US5659601A | Cites | United States of America | Applicant |
| US5701585A | Cites | United States of America | Search report |
| US5862480A | Cites | United States of America | Search report |
| US5953665A | Cites | United States of America | Search report |
| US6044141A | Cites | United States of America | Search report |
| US6044249A | Cites | United States of America | Search report |
| US6167250A | Cites | United States of America | Applicant |
| US6285868B1 | Cites | United States of America | Search report |
| US6347091B1 | Cites | United States of America | Search report |
| US6349099B1 | Cites | United States of America | Search report |
| US6360097B1 | Cites | United States of America | Search report |
| US6385454B1 | Cites | United States of America | Search report |
| US6385460B1 | Cites | United States of America | Applicant |
| US6405038B1 | Cites | United States of America | Applicant |
| US6477372B1 | Cites | United States of America | Search report |
| US6501951B2 | Cites | United States of America | Search report |
| US6522735B1 | Cites | United States of America | Applicant |
| US6608832B2 | Cites | United States of America | Search report |
| US6611516B1 | Cites | United States of America | Search report |
| US6625451B1 | Cites | United States of America | Applicant |
| US6690929B1 | Cites | United States of America | Applicant |
| US6728267B1 | Cites | United States of America | Applicant |
| US6741848B2 | Cites | United States of America | Applicant |
| US6769000B1 | Cites | United States of America | Applicant |
| US6795708B1 | Cites | United States of America | Applicant |
| US6901257B2 | Cites | United States of America | Search report |
| US6950655B2 | Cites | United States of America | Search report |
| US6985733B2 | Cites | United States of America | Search report |
| US7079499B1 | Cites | United States of America | Applicant |
| US7151938B2 | Cites | United States of America | Search report |
| US7209709B2 | Cites | United States of America | Applicant |
| European Search Report; European Patent Office; Sep. 2, 2005; 5 pages. | Non-patent | – | Applicant |
| European Search Report in EP Application No. 05252665.4; European Patent Office; Sep. 13, 2005; 6 pages. | Non-patent | – | Applicant |
| European Search Report in EP Application No. 07120521.5; European Patent Office; Dec. 19, 2007; 4 pages. | Non-patent | – | Applicant |
| European Examination Report Application No. 05252665.4; European Patent Office; Mar. 30, 2006; 3 pages. | Non-patent | – | Applicant |
| European Examination Report Application No. 07120521.5; European Patent Office; Aug. 6, 2008; 2 pages. | Non-patent | – | Applicant |
| EPO Search Report in EP Application No. 09151437.2; European Patent Office; Apr. 8, 2009; 5 pages. | Non-patent | – | Applicant |
| Canadian Office Action; Application No. 2,545,035; Canadian Intellectual Property Office; Feb. 26, 2010, 4 pages. | Non-patent | – | Applicant |
| Chinese Office Action; Application No. 200610077263.8; State Intellectual Property Office of People's Republic of China; Mar. 2, 2010; 3 pgs. | Non-patent | – | Applicant |
| AU Examination Request, Application No. 2006201729, Australian IPO, Jan. 6, 2010, 2 pgs. | Non-patent | – | Applicant |
| AU Examination Request, Application No. 2006201730, Australian IPO, Nov. 10, 2009, 4 pgs. | Non-patent | – | Applicant |
| CA Office Action, Application No. 2545032, Canadian IPO, Oct. 21, 2008, 2 pgs. | Non-patent | – | Applicant |
| CN Office Action, Application No. 200610072642, Chinese IPO, Dec. 24, 2010, 9 pgs. | Non-patent | – | Applicant |
| EP Examination Report, Application No. 05252666.2, European Patent Office, Apr. 21, 2008, 5 pgs. | Non-patent | – | Applicant |
| EP Examination Report, Application No. 07120521.5, European patent Office, Apr. 7, 2009, 4 pgs. | Non-patent | – | Applicant |
| 3GPP, TR 31.905, V 4.4.0, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Vocabulary for 3GPP Specifications (Release 4), Oct. 2001, 48 pgs. | Non-patent | – | Applicant |
| TW Office Action, Application No. 095115179, Taiwanese IPO, Mar. 10, 2011, 2 pgs. | Non-patent | – | Applicant |
| TW Office Action, Application No. 095115180, Taiwanese IPO, Feb. 25, 2011, 2 pgs. | Non-patent | – | Applicant |
| TW Search Report, Application No. 095115179, Taiwanese IPO, Feb. 1, 2011, 1 pg. | Non-patent | – | Applicant |
| TW Search Report, Application No. 095115180, Taiwanese IPO, Feb. 22, 2011, 1 pgs. | Non-patent | – | Applicant |
| US Office Action, U.S. Appl. No. 11/116,470, USPTO, Apr. 15, 2008, 12 pgs. | Non-patent | – | Applicant |
| US Office Action, U.S. Appl. No. 11/116,470, USPTO, Oct. 17, 2008, 11 pgs. | Non-patent | – | Applicant |
| US Office Action, U.S. Appl. No. 11/116,470, USPTO, Mar. 5, 2009, 6 pgs. | Non-patent | – | Applicant |
| US Office Action, U.S. Appl. No. 11/116,470, USPTO, Aug. 12, 2009, 6 pgs. | Non-patent | – | Applicant |
3 members in 1 office
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 11646105 | United States of America | A | |
| US20050116461 | – | – | – |
Members3
| Document | Office | Kind | |
|---|---|---|---|
| US2006245392A1 | United States of America | A1 | |
| US8060084B2This record | United States of America | B2 | |
| US2012040666A1 | United States of America | A1 |
141 transactions on the USPTO file
Allowed after 6 non-final rejections, 5 final rejections, 5 RCEs and 1 appeal.
- Non-final rejections
- 6
- Final rejections
- 5
- RCEs
- 5
- Appeals
- 1
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Email NotificationEML_NTR | EML_NTR | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Payment of Maintenance Fee, 12th Year, Large EntityM1553 | M1553 | |
| Payment of Maintenance Fee, 8th Year, Large EntityM1552 | M1552 | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Miscellaneous Communication to ApplicantMM327 | MM327 | |
| Reasons for AllowanceEX.R | EX.R | |
| Miscellaneous Communication to Applicant - No Action CountM327 | M327 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Reasons for AllowanceEX.R | EX.R | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Amendment/Argument after Notice of AppealAP/A | AP/A | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Notice of Appeal FiledN/AP | N/AP | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Correspondence Address ChangeC.ADB | C.ADB | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR |
9 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Maintenance fee paymentMAFP | MAFP | |
| Maintenance fee paymentMAFP | MAFP | |
| Fee paymentFPAY | FPAY | |
| AssignmentAS | AS | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS |
Numbers
- Publication
- 08060084
- Publication, DOCDB
- 8060084
- Publication, EPODOC
- US8060084
- Application
- 11116461
- Application, DOCDB
- 11646105
- Application, EPODOC
- US20050116461
Titles
- English
- Network selection scheme using a roaming broker (RB)
Patent term adjustment
- A delay
- +107 daysthe office missed an examination deadline
- Applicant delay
- −274 days
- Net adjustment
- 0 days
Classification
- CPC, 1
- H04W48/16
- IPC, 2
- H04W4 00
- H04W48 16
- USPC, 11
- 455432100
- 370310200
- 370322000
- 370328000
- 455422100
- 455426200
- 455432200
- 455434000
- 455435100
- 455435200
- 455436000