Over-the-air (OTA) device provisioning in broadband wireless networks

CROSS-REFERENCE TO RELATED APPLICATIONS

0001This application claims priority under 35 U.S.C. §119e to co-pending U.S. application Ser. No. 60/858,195 entitled “Over-the-air (OTA) Device Provisioning In Broadband Wireless Networks” and filed by the instant inventors on Nov. 8, 2006.

BACKGROUND OF THE INVENTION

0002There is ongoing interest in developing and deploying mobile networks which may facilitate transfer of information at broadband rates. These networks are colloquially referred to herein as broadband wireless access (BWA) networks and may include networks operating in conformance with one or more protocols specified by the 3^rdGeneration Partnership Project (3GPP) and its derivatives or the Institute for Electrical and Electronic Engineers (IEEE) 802.16 standards (e.g., IEEE 802.16-2005), although the embodiments discussed herein are not necessarily so limited. IEEE 802.16 compliant BWA networks are sometimes referred to as WiMAX networks, an acronym that stands for Worldwide Interoperability for Microwave Access, which is a certification mark for products that pass conformity and interoperability tests for the IEEE 802.16 standards.

0003It is predicted that many different device types may be enabled by mobile broadband wireless technologies. Such devices may include notebooks, ultra mobile PC (UMPC), and other consumer electronics such as MP3 players, digital cameras, etc. A mobile broadband service provider would therefore require a dynamic over-the-air (OTA) provisioning solution to activate and enable subscriptions for all these device types.

BRIEF DESCRIPTION OF THE DRAWING

0004Aspects, features and advantages of the present invention will become apparent from the following description of the invention in reference to the appended drawing in which like numerals denote like elements and in which:

0005<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram for an Over-The-Air (OTA) Provisioning Network Architecture according to various embodiments of the invention;

0006<figref idref="DRAWINGS">FIG. 2</figref> is a flow diagram for OTA Provisioning according to another aspect of the invention;

0007<figref idref="DRAWINGS">FIG. 3</figref> is a signaling diagram for MS-Triggered Provisioning according to further aspects of the invention;

0008<figref idref="DRAWINGS">FIG. 4</figref> is a signaling diagram for Network-Triggered Provisioning according to various aspects of the invention;

0009<figref idref="DRAWINGS">FIG. 5</figref> is a flow diagram for a Device Locking Process according to yet another aspect of the invention; and

0010<figref idref="DRAWINGS">FIG. 6</figref> is a flow diagram for a Subscriber Locking Process according to various embodiments;

DETAILED DESCRIPTION OF THE INVENTION

0011While the following detailed description may describe example embodiments of the present invention in relation to wireless networks utilizing orthogonal frequency division multiplexing (OFDM) or Orthogonal Frequency Division Multiple Access (OFDMA) modulation, the embodiments of present invention are not limited thereto and, for example, can be implemented using other multi-carrier or single carrier spread spectrum techniques such as direct sequence spread spectrum (DSSS), frequency hopping spread spectrum (FHSS), code division multiple access (CDMA) and others. While example embodiments are described herein in relation to broadband wireless access for wireless metropolitan area networks (WMANs) such as WiMAX networks, the invention is not limited thereto and can be applied to other types of wireless networks where similar advantages may be obtained. Such networks specifically include, but are not limited to, wireless local area networks (WLANs), wireless personal area networks (WPANs) and/or wireless wide area networks (WWANs) such as cellular networks and the like.

0012The following inventive embodiments may be used in a variety of applications including transmitters and receivers of a mobile wireless radio system. Radio systems specifically included within the scope of the present invention include, but are not limited to, network interface cards (NICs), network adaptors, base stations, access points (APs), gateways, bridges, hubs and satellite radiotelephones. Further, the radio systems within the scope of the invention may include satellite systems, personal communication systems (PCS), two-way radio systems, global positioning systems (GPS), two-way pagers, personal computers (PCs) and related peripherals, personal digital assistants (PDAs), personal computing accessories and all existing and future arising systems which may be related in nature and to which the principles of the inventive embodiments could be suitably applied.

0013In conventional cellular communication models, a communication device (e.g. a cell phone or network interface card (NIC)) is typically manufactured for a specific service provider (SP), which in turn sells the device to end users. Service providers operate network infrastructure and provide wireless access to subscribers. At the time of sale, a device is typically set up for accessing the service provider's network, which is referred to as “provisioning.” This conventional model is thus predicated on the service provider's control of manufactured equipment which may be used in its wireless network(s) as well as provisioning these devices for the user at the point of sale (POS).

0014However, in anticipation of many different types of equipment, such as those mentioned previously, being used in broadband wireless access (BWA) networks (such as WiMAX networks) a service provider is less likely to have complete control over the manufacture of all devices which may potentially be used in its BWA network. Furthermore, since this wide variety of devices may be made available by many different vendors a POS provisioning approach may not be adequate. Accordingly, a dynamic over-the-air (OTA) provisioning approach is likely needed to enable these devices to communicate over a service provider's BWA network. Accordingly, embodiments of the present invention propose solutions for dynamic OTA provisioning suitable for various device types (e.g., with or w/o keyboard, universal integrated circuit card (UICC), etc.) to be used in BWA networks. Embodiments of the present invention preferably utilize BWA device technology which is certified by a standardizing body such as the WiMAX Forum Networking Group although the invention is not so limited. Two key issues for service provider's providing BWA service may involve: (i) identifying whether a device is compliant with standards and protocols used in its network (referred to as “device certification”) and (ii) identifying whether a user of a BWA-enabled device is authorized (or “provisioned”) to use the service provider's network.

0015Referring to <figref idref="DRAWINGS">FIG. 1</figref>, according to one exemplary network architecture <b>100</b> for BWA OTA provisioning may include a service provider network having a core network <b>101</b> and one or more radio access networks (RANs) <b>102</b>.

0016A mobile station (MS) <b>105</b>, for example a subscriber station using protocols compatible with the IEEE) 802.16 standards (e.g., IEEE 802.16-2005 Amendment), may access a service provider's core network <b>101</b> via a radio link with a base station (BS) (e.g. BS <b>110</b>, <b>111</b>) in the SP's RAN <b>102</b>. In certain example implementations, communications with MS <b>105</b> via RAN <b>102</b> may be facilitated via one or more access service network gateways (ASN-GWs) <b>115</b> although the inventive embodiments are not limited to this specific type of network implementation. ASN-GW <b>115</b> (or other similar type of network node) acts as an interface between the SPs core network <b>101</b> and its RANs <b>102</b>. Thus ASN-GW may be connected to a plurality of base stations <b>110</b>, <b>111</b> and may function as a type of BS controller and/or mobile switching center (MSC) to facilitate handover control and other functions for RAN <b>102</b>, although the embodiments are not so limited.

0017In certain embodiments network <b>100</b> may further include an authentication, authorization and accounting (AAA) server <b>120</b>, subscriber repository <b>125</b> and provisioning server <b>130</b>. In certain embodiments subscriber repository <b>125</b> may actually comprise one or more entities such as a lightweight directory access protocol (LDAP) server, a home location register (HLR), a home subscriber server (HSS) and/or other entity. An optional billing engine (not shown) may also be included in service provider's core network <b>101</b>. Network <b>100</b> may further include a certificate authority (CA) <b>135</b> and/or connections to 3^rdparty servers for tracking information as explained in more detail in the embodiments below.

0018Referring to <figref idref="DRAWINGS">FIG. 2</figref>, an OTA certification and provisioning process <b>200</b> will be explained in regard to the example network architecture <b>100</b> of <figref idref="DRAWINGS">FIG. 1</figref>. In certain embodiments herein, a non-provisioned device (e.g., MS <b>105</b>), may attempt to connect <b>205</b> with the service provider's network. Initially, the service provider should determine <b>210</b>, <b>215</b> if the device is a certified compliant device. To this end, in one example implementation, at the point of manufacturing (POM), a WiMAX device (e.g., MS <b>105</b>) may be preset with a medium access control (MAC) address and if it passes a WiMAX Forum or other type of certification process it may also be given a cryptographic digital certificate that is stored in a tamper-resistant device memory in MS <b>105</b>. A network access identification (NAI) (e.g., MAC@wimax.org) driven from the device MAC address may present the device identity when MS <b>105</b> attempts to connect to the service provider's network. This digital certificate may be used to verify (e.g., via certificate authority <b>135</b>) that the device complies with any required standards. If <b>215</b> the device is not a certified device, certification/provisioning process <b>200</b> may be terminated <b>220</b> and, optionally, the user notified that the device is not certified.

0019If certificate authority <b>135</b> identifies <b>215</b> MS <b>105</b> as a certified device, the service provider (e.g., via AAA server <b>120</b> and subscriber repository <b>125</b>) may next determine <b>225</b> whether MS <b>105</b> has been provisioned. If <b>225</b> MS <b>105</b> has previously been provisioned, network access is authorized <b>230</b> and the user may proceed with normal BWA access through the service provider network.

0020If <b>225</b> however, it is determined MS <b>105</b> has yet been provisioned, for example AAA server <b>120</b> will notice that there is no record of any subscriber for MS <b>105</b> in repository <b>125</b>, AAA server <b>120</b> may request ASN Gateway <b>115</b>, for example via an AAA Accept Message, to hot-line <b>235</b> MS <b>105</b> to provisioning server <b>130</b>. AAA server <b>120</b> may also allocate an Internet Protocol (IP) address to this non-provisioned device. ASN-GW <b>115</b> will then hot-line <b>235</b> the device based on the R<b>6</b> Path ID and device's source IP address. Through the hot-lining process <b>235</b>, MS <b>105</b> is directed to, and only able to access, provisioning server <b>130</b>.

0021After hot-lining MS <b>105</b> to provisioning server <b>130</b>, a provisioning process e.g., steps <b>240</b>, <b>245</b> can be initiated either by MS <b>105</b> (refer to example signaling of <figref idref="DRAWINGS">FIG. 3</figref>) or the network (refer to the example signaling of <figref idref="DRAWINGS">FIG. 4</figref>). The provisioning process allows the subscriber of MS <b>105</b> to create an account with the service provider network and may include, among other things, provisioning server <b>130</b> receiving <b>240</b> device credentials and device identification and an exchange <b>245</b> of any other information and/or software with MS <b>105</b> which the service provider may deem necessary to activate a subscriber account <b>250</b>.

0022For example, during the provisioning process, various parameters may be exchanged <b>240</b>, <b>245</b> including, but not limited to, platform capability/type, service providers preferred roaming partners list, provisioning agent client download or branding graphic user interface (GUI)) application software downloads (e.g. voice over IP (VoIP), voice on demand (VoD) software), network configuration files (e.g. common management information protocol (CMIP), dynamic host configuration protocol (DHCP)), device lock parameters (referred to in <figref idref="DRAWINGS">FIG. 5</figref>), NAI/password, etc.

0023During or after the device provisioning process, provisioning server <b>120</b> creates and/or activates <b>250</b> the new user account in subscriber database(s) (e.g., repository <b>125</b>) and billing system(s) of the service provider's network. Once MS <b>105</b> is provisioned, it may be required to perform device and/or user authentication at the next network re-entry.

0024In one example implementation, provisioning server <b>120</b> may communicate with MS's <b>105</b> provisioning agent using simple web browser technology, e.g., simple object access protocol (SOAP)/hyper transfer text protocol secure socket (HTTPS), open mobile alliance device management (OMA-DM) protocols, or other proprietary protocols.

0025Referring to <figref idref="DRAWINGS">FIGS. 3</figref> an example signaling process <b>300</b> is shown for provisioning a mobile device (e.g., MS <b>105</b>; <figref idref="DRAWINGS">FIG. 1</figref>) in a broadband wireless access network where the provisioning is triggered by the device. The example of <figref idref="DRAWINGS">FIG. 3</figref> represents a call flow <b>300</b> for provisioning an example device which is minimally pre-provisioned at the POM/ point-of-sale (POS) (for example category-<b>2</b> and/or category-<b>3</b> devices).

0026When a new BWA-enabled device (mobile station-MS) is out of the box and a user tries to access <b>305</b> the service provider's wireless network (e.g., WiMAX network), it may perform channel acquisition and initial ranging as in step-<b>1</b>. Next capability negotiations may be exchanged with the BS as in steps <b>2</b>-<b>6</b>. Upon successful capability negotiations, a device authorization/certification process <b>310</b> may be performed. In one example non-limiting embodiment, the network asks the identity of the MS (e.g., using an extensible authentication protocol (EAP) ID request (REQ or RQ) as in steps <b>7</b>-<b>8</b>). The MS may respond (RSP or RP) with its EAP ID, for example an NAI as discussed above, back to the Authenticator and the home AAA as in steps <b>9</b>-<b>11</b>. The EAP transport layer security (TLS) authentication of the MS-provided NAI (i.e., device certification) occurs in step <b>12</b>. In step <b>13</b>, there may be an optional verification of the MS certification with a <b>3</b>rd party certificate authority server and/or other 3^rdparty servers.

0027Once the device has been certified/authenticated, the home AAA server may realize that the MS is an off the shelf new device trying to connect to the network enforce a hot lining policy for this MS as in step <b>14</b>. In one embodiment, the hot lining policy enforcement will happen at the authenticator client residing in the ASN-GW and the EAP procedure as shown in steps <b>15</b>-<b>17</b> may be completed.

0028Subsequently, if desired, a data link layer security process, network registration and service flow process <b>312</b> may next be performed. In one embodiment using 802.16 (e.g., 802.16-2005 amendment) protocols, a data encryption exchange, as shown in steps <b>18</b>-<b>19</b>, may occur in which the MS obtains a transport encryption key (TEK) from the BS and in steps <b>20</b>-<b>24</b> the MS registers with the network. In steps <b>25</b>-<b>26</b>, a MAC connection for the initial service flow (e.g., a basic connection identifier (CID)) for the MS may established over the wireless link and in step <b>27</b> an IP connection may be established wherein the MS obtains a point-of-attachment (POA) IP address.

0029In an MS triggered hotlining process <b>315</b>, if the MS tries to send some traffic to the BS as in step <b>28</b> (this could be management traffic or data traffic like traffic to some website), the activity may be trapped at the ASN-GW and the user is hotlined to the provisioning server as in steps <b>29</b> and <b>30</b>. An MS provisioning process <b>320</b>, similar to that previously discussed may then be performed as shown in step <b>31</b>. Optionally, provisioning process <b>320</b> may include relaying provisioning information (e.g., accounting or registration information) to some 3rd party servers as shown in step <b>32</b>. In step <b>33</b>, the fully provisioned MS may be allowed to enter the network again using full network entry procedures <b>325</b> in which steps similar to 1-11 may be repeated.

0030Referring to <figref idref="DRAWINGS">FIG. 4</figref>, a signaling process <b>400</b> similar to that of <figref idref="DRAWINGS">FIG. 3</figref> may alternatively be used in which the hotlining process <b>415</b> to the provisioning server is triggered by the network instead of triggered via activity by the mobile station. The specific signaling discussed in reference to <figref idref="DRAWINGS">FIGS. 3 and 4</figref> are provided merely as examples for specific implementations. Accordingly, other signaling may be used that may vary from that discussed herein which may depend on the type of broadband wireless access network as well as network design preferences.

0031Turning to <figref idref="DRAWINGS">FIG. 5</figref>, in certain embodiments, a service provider may desire an MS to be locked to the service provider during or after activation/provisioning.

0032This is referred to herein as device locking. Device locking can be achieved by forcing the device to connect only to the host operator's preferred list of partners or preferred roaming list (PRL). An example device locking process <b>500</b> is shown in <figref idref="DRAWINGS">FIG. 5</figref> and may generally include, during or after the provisioning process(es) discussed above, storing <b>510</b> a PRL list in a module of the mobile device and activating <b>520</b> device locking by setting a device lock key (which may be performed by the network during provisioning). Thereafter, the device will not allow <b>530</b> a user to provision in a service provider network which is not associated with the PRL, at least while the device lock key is valid.

0033When the device enters the network, the device will perform mutual authentication <b>540</b> using operator provisioned credentials. If <b>545</b> the credentials are not valid for the network the device is entering, the device will be denied <b>550</b> access. If <b>545</b> however, the credentials are valid for the network the device is entering, the device will be given <b>560</b> access to the network.

0034Alternatively or in addition, referring to <figref idref="DRAWINGS">FIG. 6</figref>, a service provider may require a subscriber to be locked to single device after activation. This is referred to herein as “subscriber locking.” In other words, through subscriber locking, a user cannot use its user credentials on other provisioned devices. An exemplary process <b>600</b> for subscriber locking can be achieved by linking <b>610</b> the user identity to the device identity at the provisioning phase (e.g., <b>320</b>; <figref idref="DRAWINGS">FIGS. 3 and 4</figref>). In this embodiment, the network access ID (NAI) required from the mobile station for network authentication may be set <b>620</b> to include the device identification (e.g., device MAC address) as well as the user identity (e.g., user name). In one example implementation, the NAI used by the mobile station for network access might be similar to “MAC_address.user_name(at)networkdomain.”

0035The service provider can then verify <b>630</b> if the user identity in the received NAI matches the pre-set device identity for this user. In this case, the authentication process only succeeds <b>640</b> if <b>635</b> the match of user ID and device ID is positive, hence enforcing subscriber locking. If <b>635</b> no match is found, the mobile station may be denied <b>650</b> access.

0036Example advantages of the inventive embodiments presented herein may include a device-agnostic solution that can apply to handheld, notebook, ultra mobile PCs (UMPCs) and/or other BWA-enabled consumer electronics. Moreover, the inventive embodiments may allow the use of multiple provisioning protocols including simple web browser access, SOAP/HTTPS, and/or OMA-DM among others. Embodiments of the present invention may allow for provisioning (U)SIM and non-(U)SIM devices and enables non-provisionable devices to be directed to a welcome page for on-off access to host service provider. By using the method(s) and systems of the inventive embodiments, a service provider can seamlessly certify and provision a BWA-enabled device having a generic SKU over-the-air and activate a user account the first time the device connects.

0037Unless contrary to physical possibility, the inventors envision the embodiments described herein: (i) may be performed in any sequence and/or in any combination; and (ii) the components of respective embodiments may be combined in any manner.

0038Although there have been described example embodiments of this novel invention, many variations and modifications are possible without departing from the scope of the invention. Accordingly the inventive embodiments are not limited by the specific disclosure above, but rather should be limited only by the scope of the appended claims and their legal equivalents.