Method and apparatus for provisioning and activation of an embedded module in an access terminal of a wireless communication system

[0001] This application claims priority to U.S. Provisional Application No. 60/512,595 filed Oct. 17, 2003, entitled “Provisioning and Activation for Embedded Modules,” by Nikolai Leung et al., which is incorporated herein by reference in its entirety.

[0002] This application also claims priority to U.S. Provisional Application No. 60/568,198 filed May 4, 2004, entitled “Provisioning and Activation for CDMA Modules Embedded in Mobile Computing device,” by Nikolai Leung, which is incorporated herein by reference in its entirety.

[0003] 1. Field

[0004] The present invention relates generally to communications and, more specifically, to provisioning and activation of an embedded module in an access terminal in a wireless communication system.

[0005] 2. Background

[0006] With the proliferation of wireless communication capability in a wide variety of applications, many laptop computers and other computing devices, require cellular or other wireless access. The wireless functions are provided by a module located within the laptop or other computing device. Such wireless access is through a service provider or carrier. The service provider or carrier requires provisioning and activation of the embedded device for wireless access to ensure payment for services, avoid fraudulent uses and provide accounting and billing information. Typically, when a user purchases a cellular phone, the phone is provisioned and activated at the point of purchase or by over-the-air (OTA) provisioning. Point of purchase service provisioning is not convenient for computing devices with embedded modules, as the modules are not typically accessible in a store selling computing devices. Further, the point of purchase of the computing device is not typically capable of providing provisioning and activation, and would force the user to take the computing device to another store for provisioning and activation.

[0007] There is a need therefore, for a method and apparatus of provisioning and activating a module, used for wireless communication, within a computing or other device, such as a laptop computer. Further, there is a need to allow over-the-air provisioning (OTA) and authentication of such devices.

[0008] Embodiments disclosed herein address the above stated needs by a method for provisioning a wireless communication module. The method includes initiating an over-the-air service and provisioning procedure from a mobile computing device embedded with a wireless communication module. A request is received at the mobile computing device for provisioning information from a carrier using the over-the-air service and provisioning procedure. Confirmation is received at the mobile communication device of provisioning from the carrier via the over-the-air service and provisioning procedure.

[0009] In another aspect of the present invention, a user interface application for a mobile computing device is provided. The user interface application is configured to initiate a signal to an embedded module to connect a packet data service option for a wireless network. The application is further configured to initiate a web browser on the mobile communication device and direct the browser to the wireless network server once a packet data secession is established and the mobile communication device is assigned an IP address.

[0016] The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments. All of the embodiments described in this Detailed Description are exemplary embodiments provided to enable persons skilled in the art to make or use the invention and not to limit the scope of the invention which is defined by the claims.

[0017] Referring to FIG. 1, a wireless communication system 100 is shown according to one embodiment of the present invention. A wireless subscriber station, referred to herein as an access terminal (AT) 105, may be mobile or stationary, and may communicate with one or more wireless base stations 110. The access terminal 105 transmits and receives data packets through the one or more base stations 110 to a base station controller (BSC) 115. The base stations 110 and base station controller 115 are parts of a network called an access network. An access network transports data packets between multiple access terminals 105. The access network may be further connected to additional networks outside the access network, such as a packet data serving network (PDSN) 125, and the Internet 130, and may transport data packets between each access terminal 105 and such outside networks.

[0018] The communication link through which the access terminal 105 sends signals to the base stations 110 is called a reverse link. The communication link through which a base station 110 sends signals to an access terminal 105 is called a forward link. An access terminal 105 that has established an active traffic channel connection with one or more base stations 110 is called an active access terminal, and is said to be in a traffic state. An access terminal 105 that is in the process of establishing an active traffic channel connection with one or more base stations 110 is said to be in a connection setup state.

[0019] An access terminal 105 may be any data device that communicates through a wireless channel or, alternatively, may communicate through a wired channel (e.g, using fiber optic or coaxial cables). In accordance with the illustrated embodiment, the access terminal 105 takes the form of a mobile computing device, such as a laptop computer, for example, that is configured with a wireless communication module for enabling wireless communication with the base stations 110. The access terminal 105 may further take the form of a number of types of other devices including, but not limited to, a PC card, external or internal modem, wireless phone, PDA, and the like.

[0020] According to one embodiment, each of the access terminals 105 is configured with an embedded module 120, which may take the form of a mobile station modem (MSM). The embedded module 120 receives communication signals from the base station 110 on the forward link and transmits communication signals to the base station 110 on the reverse link.

[0021] FIG. 2 illustrates a procedure whereby the manufacture of the module 120 pre-provisions the supported subscription profiles for each service provider (i.e., wireless operator) into the module 120 before shipping it to the vendor of the access terminal 105. Once the module 120 has been embedded in the access terminal 105, the user clicks on the selected operator's subscription application that was pre-provisioned by the manufacture of the module 120, which commands the module 120 to use the associated subscription profile for originating a packet data session with the particular service provider (i.e., operator).

[0022] Updating of the subscription profile within the module 120 may be needed if the subscription parameters for an operator change before the module 120 has been activated. This may be accomplished without removing the embedded module 120 from the access terminal 105, and may be achieved in one of two ways. First, the vendor of the access terminal 105 may temporarily load an application on to the access terminal 105 that preloads into the module 120 an updated subscription profile for the particular service provider (operator). Alternatively, the access terminal 105 vendor may connect a subscription profile loading tool through the access terminal's USB port, for example, to update the subscription profile on the module 120.

[0023] FIG. 3 illustrates a procedure whereby the access terminal 105 contains a stored subscription application of the operator, which retains the subscription profile specific to that wireless operator. When the user selects the subscription application for the selected operator via the access terminal 105, the selected application downloads the profile into the module 120 and commands the module 120 to start a packet data session with the selected wireless operator. This method provides a convenient means for the operator to update its subscription profile if needed. The operator updates the profile in the subscription application and provides this to the access terminal 105 vendor. Before shipping a unit, the access terminal 105 vendor preloads the operator's most recent application on the access terminal 105 or may provide the subscription application on an accompanying CD-ROM that is provided when the user purchases the access terminal 105 from the vendor.

[0024] To support a “generic” module 120 (i.e., applicable to more than one service provider (operator), the mobile station modem (MSM) would need to support multiple operator subscription profiles. If the preloaded subscription profiles illustrated in FIG. 2 are used, it would be desirable for the MSM to support the following:

• • [0025] Multiple subscription profiles in NV RAM that are preloaded by the module 120 vendor.
  • [0026] An interface that allows the subscription application to indicate to the MSM which subscription profile to use.
  • [0027] An interface to a subscription-profile-loading-application on the access terminal 105 or an interface to a loading tool connected through the access terminal's 105 USB interface. These can be used by the access terminal vendor if it is necessary to update preloaded profiles in a module 120 already embedded in an access terminal without removing the module 120.

[0028] If the application download procedure illustrated in FIG. 3 is used, then it would be desirable for the MSM to support an interface that allows the subscription application to download the subscription parameters into NV RAM. If a module PIN-lock mechanism is used to secure shipped modules 120, the MSM would perform the following:

• • [0029] MSM locks the module for mobile-initiated wireless communication network access until the correct PIN is entered.
  • [0030] MSM provides an interface to a access terminal application (e.g., via NDIS for Windows Operating Systems) to allow entry of PIN.
  • [0031] MSM computes the PIN based on a predefined function of a unique module parameter provisioned via OTAPA (e.g., PIN=hash of MIN).
  • [0032] To prevent brute force PIN attacks from an application on the access terminal, the MSM can restrict the number of PIN attempts and/or monotonically extend the time between successive PIN attempts each time one fails. For security, if the number of allowable attempts is exceeded, the MSM would have to be re-provisioned via OTAPA to accept new PIN attempts.

[0033] If the function for computing the PIN is going to be operator-defined (e.g., particular hash function of particular OTAPA parameter), the MSM would need to support this operator-definable-feature. The function definition would be pre-preloaded into the module 120 as part of the operator's subscription profile.

[0034] As previously discussed, the module 120 can be embedded in the access terminal 105 before the access terminal 105 is sold to the user. The module 120 can be embedded in the access terminal 105 during manufacture or at the point of sale. A subscription application is preloaded on the access terminal 105 by the access terminal vendor or is provided on an installation CD.

[0035] FIG. 4 illustrates signaling flow for setting up over-the-air parameter administration (OTAPA) provisioning of an embedded module 120 within the access terminal 105. At step 401, the user starts the subscription application, which instructs the module 120 to initiate a subscription to the wireless communication provider at step 403. The module 120 uses a subscription profile, which includes default parameters needed for initiating the call on the wireless communication network. At step 405 the module 120 initiates the call using the module's electronic serial number (ESN) and a mobile identification number (MIN) based on a hashing function using the module's ESN. The radio access network allows the packet data session to connect even if the MIN is not that of a subscribed module 120. At step 407, the module's ESN is communicated to the PDSN 125 in the Radio Packet Connection Setup Airlink Record sent via the A11 interface over a wireless communication channel. At step 409, the module 120 establishes an IP call and uses the preloaded default network access identifier (NAI) (e.g. [esn]@ subscribe.vzw.com in the Verizon network, for example) and password to authenticate itself to the PDSN 125 via Challenge Handshake Authentication Protocol (CHAP). The PDSN 125 accepts these default authentication parameters and provides the module 120 an IP address, X. Since the default parameters indicate that the user has not yet subscribed, the PDSN 125 limits the traffic from this user to only the operator's subscription web server. At step 411, the PDSN 125 instructs the provisioning Authentication Authorization and Accounting (AAA) server to generate a record for the module 120, including the default Network Address Identifier (NAI), ESN, and IP address assigned by the PDSN 125 to the module 120. Having the NAI include the ESN of module 120 produces unique NAI's, which is useful if the provisioning AAA server is organizing its records based on the NAI. This prevents the provisioning AAA server from overwriting records when multiple modules are attempting to subscribe for service at approximately the same time.

[0036] Once the access terminal subscription application determines that an IP address has been assigned to the access terminal 105, the application launches a standard web browser on the access terminal at step 413. The application directs the browser to the subscription server's URL or IP address where a webpage presents the user with various subscription plans. The browser uses standard Internet e-commerce security protocols to authenticate the subscription server (e.g., digital certificates signed by VeriSign) and exchange encrypted financial information.

[0037] At step 415, once the user has selected a subscription plan, the web server uses the IP address from the current IP transaction with the user's web browser on the access terminal 105 to determine the ESN of the module 120. The web server queries the provisioning AAA server for the ESN of the module based on IP address X. The web server's request for the ESN needs to be made while the HTTP transaction with the user is still active so that the PDSN 125 keeps IP address X assigned to the module 120. The Provisioning AAA server searches its records keying off of IP address X to determine the ESN of the module 120. If an ESN is located, then this is returned to the web server at step 417. Once the web server has obtained the ESN information, it can query the user to enter their credit and account information. This is provided by the user over a secure HTTPS/SSL link to the web server in step 419. Once the user's credit information has been verified, the web server indicates the ESN of the module 120 to the Over-the-Air Service Provisioning Function (OTAF) at step 421. Once the module 120 is able to receive an OTAPA call, the OTAF uses the ESN to contact and provision the module 120 at step 423. It will be appreciated that in an alternative embodiment, OTASP can be used in step 423. Once the subscription application has been notified that step 411 has been completed, the application commands the module 120 to make an OTASP call when the module 120 is within wireless communication network coverage.

[0038] To support the generic module 120, the MSM would support multiple operator subscription profiles. As described in steps 403, 405, and 409 in FIG. 4, the un-provisioned wireless communication module 120 needs a set of parameters that allow it to acquire a radio traffic channel for subscription purposes. The module also needs PDSN 125 authentication parameters to obtain access through the PDSN 125 to the subscription server. Since these sets of parameters are different across operators, a generic module 120 would need to support different sets of subscription parameters, referred to here as subscription profiles. Each subscription profile would contain the following sets of parameters:

[0039] Parameters needed to acquire radio traffic channel

• • [0040] Frequencies
  • [0041] PRL (Preferred Roaming List)
  • [0042] ESN hashing function to produce default MIN

[0043] PDSN authentication parameters

• • [0044] Default NAI (e.g. [esn]@subscribe.vzw.com)
  • [0045] Default Password

[0046] Service parameters that can not be provisioned Over-the-Air

• • [0047] For example, RSA Public Key for Verizon's Dynamic Mobile IP Key Update (DMU) Procedures

[0048] This last set of parameters is included in the subscription profile since it can not be provisioned via OTA procedures.

[0049] In another embodiment, the user of the access terminal 105 can request subscription over a wireline connection. In this embodiment, the user of the access terminal 105 uses a wireline Internet connection to connect the access terminal 105 to the wireless communication service provider and perform the activation process via a wired connection. Also, since the server can not establish a direct and secure IP connection to the MSM over wireline, there is no secure way for the server to automatically obtain the ESN of the module 120. Automated methods would be open to a virus/worm providing a different ESN to the server.

[0050] Wireline subscription may be useful as a back-up method for special cases where the subscriber has access to a wireline connection and is willing to manually provide the module ESN to the subscription website. For example, a company's IT department can use this method to subscribe multiple mobile computing device—embedded modules 120.

[0051] FIG. 5 illustrates a method, which uses communication from the user's browser to be sent directly to the module 120, and serves as a proxy and passes this information through its secure link to the subscription server. The MSM 120 serves as an HTTP proxy to allow the HTML traffic from the subscription server to be displayed on the user's browser at the access terminal 105. At step 501, the user launches an application/link on the browser on the access terminal 105. At step 503, the access terminal 105 connects to the MSM and indicates which operator webserver to contact using HTTP/TCP/IP. At step 505, the MSM connects to the operator's server using HTTP/TCP/IP. At step 507, the MSM relays HTTP traffic between the access terminal 105 and MSM stack and the MSM and subscription server stack. At step 509, the subscription server authenticates the webserver and establishes a HTTP/SSL/TCP/IP secession and the MSM establishes a HTTP/TCP/IP secession with the access terminal 105. At step 511, the user enters credit information on the access terminal 105. At step 513, the subscription server requests the ESN of the module 120. At step, 515 the MSM 120 sends the ESN of the module 120 to the subscription server.

[0052] FIG. 6 illustrates another embodiment, where the user's browser on the access terminal 105 establishes a secure end-to-end HTTPS/SSL/TCP/IP session with the subscription server tunneled through the MSM's VPN connection. This end-to-end session allows the browser to authenticate the subscription server and secure any user credit information being sent. At step 601, the user launches an application/link on the browser on the access terminal 105. At step 603, the browser running on the access terminal 105 connects to the MSM and indicates which operator webserver to contact using HTTP/TCP/IP. At step 605, the MSM connects to the operator's server using a voice privacy network (VPN) connection. At step 607, HTTP/TCP/IP traffic is tunneled through the MSM VPN connection between the access terminal 105 and the subscription server. At step 609, the subscription server authenticates the webserver and establishes a HTTP/SSL/TCP/IP secession tunneled through the MSM VPN connection between the access terminal 105 and the subscription server. At step 611, the user enters credit information on the access terminal 105. At step 613, the subscription server requests the ESN of the module 120. At step 615, the MSM 120 sends the ESN of the module 120 to the subscription server.

[0053] The various illustrative logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0054] The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

[0055] The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.