US 7,894,847 B2Grant
Activation of mobile computing device
Issue Date:2011-02-22
•16 Claims
•7 Drawing Sheets
Abstract
A mobile computing device has a memory and a processing device. The memory has network settings for compatibility with a plurality of different wireless carriers. The processing device is configured to obtain network settings for a particular carrier from the memory based on an account ID and to activate the mobile computing device with the carrier based on the network settings and the ID.
Metadata
Assignee
- Palm, Inc.
Inventor
- Brian Gerald Kuhn
Application Information
Application Number:US 11/218,346
Filing Date:2005-08-31
Priority Date:2000-12-07
Art Unit:2617
Classifications
IPC:
H04M1/00
Patent Drawings (7 sheets)
Description
CROSS REFERENCE TO RELATED APPLICATION
[0001] This application is a Continuation of U.S. application Ser. No. 11/218,346 filed Aug. 31, 2005, which is a Continuation of U.S. application Ser. No. 09/732,076 filed Dec. 7, 2000, now U.S. Pat. No. 6,961,567. This application is related to U.S. patent application Ser. No. 09/732,066, filed Dec. 7, 2000 and titled “USER INTERFACE TECHNIQUE FOR SELECTION AND ACTIVATION OF WIRELESS SERVICES FROM AMONG MULTIPLE TRANSPORT CARRIERS”, which is hereby incorporated by reference.
[0002] This application is related to U.S. patent application Ser. No. 09/732,066, filed on the Dec. 7, 2000, entitled “User Interface Technique for Selection and Activation of Wireless Services from Among Multiple Transport Carriers”, by inventors Craig Skinner, William Shu-woon Wong, and Brian G. Kuhn, the entire disclosure of which is incorporated herein by reference.
COPYRIGHT NOTICE
[0003] A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
BACKGROUND OF THE INVENTION
[0004] 1. Field of the Invention
[0005] The present invention generally relates to wireless networks and, more particularly, to wireless network activation with carriers and registration with service providers.
[0006] 2. Discussion of Background
[0007] The wireless communication revolution is bringing fundamental changes to data networking and telecommunication, and is making integrated networks a reality. By freeing the user from the cord, personal communications networks, wireless local area networks (LAN's), and mobile radio networks and cellular systems harbor the promise of fully distributed mobile computing and communications, any time, anywhere. Numerous wireless services are also maturing and are poised to change the way and scope of communication.
[0008] Many manufacturers have begun to incorporate wireless technologies into a new kind of computer—the personal digital assistant (PDA). A PDA is a computer that is small enough to be held in the hand of a user. A PDA runs personal information management applications such as an address book, a daily organizer, and electronic notepads. These applications make people's lives easier.
[0009] FIG. 1 shows a basic configuration of a popular PDA brand, the Palm™ 10. However, the Palm™ 10 is much more than a simple PDA. This small, slim, device, about the size of your wallet, can hold 6000 addresses, 5 years of appointments, 1500 to-do items, 1500 memos, 200 e-mail messages, and can run many different software applications.
[0010] The front panel of the Palm™ 10 is a large liquid crystal display (“LCD”) 11, which is touch-sensitive and allows a user to enter and manipulate data. By using a stylus (not shown) to interact with the touch-sensitive screen, a user may easily navigate through a host of various software applications. A stylus is used to interact with information on a screen in much the same way a mouse is used with a desktop personal computer. The display device also includes a Graffiti™ writing section 12 for tracing alphanumeric characters as input.
[0011] Regarding wireless connectivity, a given wireless network typically has many different carriers for the same network type. For example, Bell South™ and Rogers AT&T™ are wireless carriers that both run Mobitex™ networks. Further, many wireless computers are manufactured to be compatible with a particular network type, carrier, and/or service provider.
[0012] Unfortunately, problems arise when a consumer, manufacturer, or provider later desires the computer to be compatible with another network or another carrier. Integrated within the computer's architecture, may be an operating system that allows a user to connect with a specific carrier and/or service provider. For example, applications that allow connectivity with a specific carrier, such as BellSouth™, may be written to a read-only memory (ROM) of the PDA. Such a framework makes it difficult to later make the PDA compatible with another carrier or with another type of network.
[0013] The PDA that is compatible with only BellSouth™ can not be taken to Europe to be compatible with a French carrier, much less a wireless network in France. Thus, the manufacturer that builds the PDA that is compatible with BellSouth™ will have to build a different PDA to be compatible with a French carrier, and another device for Australia, and another for Japan, etc.
[0014] While a PDA may be manufactured for a regional carrier and/or service provider, wireless networks naturally provide users with extended computing capabilities and mobility. Users are able to move about, carrying their computers with them and maintaining uninterrupted communication with their servers. Wireless networks should be able to allow users to turn on their computers almost anywhere in the world, to establish access to their home servers, and to retrieve their files and email. Such mobility, however, is difficult with commonly available wireless technology.
[0015] Consequently, the implementation of wireless networks presents new problems. Unfortunately, classical communication theory and wired network models does not efficiently solve these new problems.
BRIEF DESCRIPTION OF THE DRAWINGS
[0016] The present invention will be readily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, like reference numerals designate like structural elements.
[0017] FIG. 1 shows a basic configuration of a popular PDA brand, the Palm™.
[0018] FIG. 2 is a block diagram of selected components of a computer that includes wireless network technology, in accordance with one embodiment of the present invention.
[0019] FIG. 3 is a block diagram of the architecture for the generic activation and registration framework (GARF), in accordance with one embodiment of the present invention.
[0020] FIG. 4 shows a high-level flowchart for a method of managing network activation with a carrier and registration with a service provider, in accordance with one embodiment of the present invention.
[0021] FIG. 5A shows a more detailed flowchart for a method of managing network activation with a carrier and registration with a service provider, in accordance with one embodiment of the present invention.
[0022] FIG. 5B is a continuation of the flowchart of FIG. 5A , in accordance with one embodiment of the present invention.
DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0023] An invention is disclosed for a system and method for managing network activation with a carrier and registration with a service provider. Numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be understood, however, to one skilled in the art, that the present invention may be practiced without some or all of these specific details.
[0024] It has been recognized that what is needed is a framework for providing broader compatibility with wireless networks. Broadly speaking, an exemplary embodiment fills these needs by providing a system and method for managing wireless network activation with a carrier and for handling registration with a service provider. It should be appreciated that the exemplary embodiment can be implemented in numerous ways, including as a process, an apparatus, a system, a device or a method. Several inventive embodiments are described below.
[0025] In one embodiment, a method is provided for managing network activation with a carrier and registration with a service provider. The method comprises: determining a network activation status with a carrier; if not activated, performing network activation procedures; determining a registration status with a service provider; if not registered, sending a request to a server of the service provider for a registration file configured to gather user registration information; receiving the registration file from the server; and executing the registration file.
[0026] In another embodiment, a generic framework is provided for network activation and registration. The framework comprises: a generic driver device configured to manage network activation procedures and registration procedures; and a plug-in device configured to initiate registration procedures based on commands received from the driver, wherein the plug-in device is tailored to a particular service provider.
[0027] In still another embodiment, the framework is provided wherein the plug-in device includes an address to a registration file configured to gather user registration information for the particular service provider.
[0028] Advantageously, an exemplary embodiment provides a generic framework for activation and registration. The generic framework can be configured to be compatible with multiple carriers and/or service providers for any language. The generic framework can also be used for multiple wireless network types. No longer does a personal computer have to be manufactured to be compatible with individual carriers, particular service providers, or specific networks. Easily installable plug-in devices can be tailored to each carrier, service provider, or network type. Accordingly, carriers can readily make themselves compatible with a given personal computer without having to change the personal computer's ROM to fit the particular carrier, service provider, or network type. Thus, a generalized infrastructure is put in place to bring new carriers and personal computers online substantially quicker.
[0029] The invention encompasses other embodiments of a method, an apparatus, and a computer-readable medium, which are configured as set forth above and with other features and alternatives.
General Overview
[0030] FIG. 2 is a block diagram of selected components of a computer 100 that includes wireless network technology, in accordance with one embodiment of the present invention. The computer 100 includes a processing device 110, for executing applications and an operating system of the computer 100, a memory device 120 for storing the operating system, data, and applications (including plug-in executable files).
[0031] A display screen 130 is provided (preferably a touch sensitive screen) for display of operating system prompts, buttons, icons, application screens, and other data, and for providing user inputs via tapping or touching (or drawing in the Graffiti™ area) via a stylus or other touch mechanism. Hardware interface 135 connects to physical hard buttons and switches located on a body of the computer 100 and provides signals to applications running on the processing unit 110.
[0032] A bus 155 carries data and commands to/from the processing unit 110 from/to other devices within the computer 100. For example, user applications running on the computer 100 may be stored in the memory device 120. The user applications send application screens and other data outputs to display screen 130 for display via the bus 155. User inputs (Graffiti™ area drawing, or tap selection, for example) are detected by the screen 130 and sent to the processing unit 110 via the bus 155.
[0033] A mobile radio device 140 (part of the wireless technology in the computer 100) provides connectivity to a wireless network (not shown). The mobile radio device 140 is configured to detect inbound network transactions from the network directed toward the mobile radio device 140. For example, the inbound network transaction may be a page notification that is sent to a pager device executing on the processing unit 110.
[0034] In the embodiment of FIG. 2 , the computer 100 is illustrated as a personal digital assistant (PDA). A PDA is a handheld computer such as a Palm™, Palm III™, or Palm V™, or Palm VII™ organizers, manufactured by Palm, Inc. Other embodiments of the invention can include Windows CE™ and Visor™ handheld computers, other handheld computers, other personal digital assistants (PDAs), desktop computers, laptop computers, workstations, or mainframes.
[0035] The Palm™ and its operating environment are used herein to illustrate various aspects of the present invention. However, it should be understood that the present invention may be practiced on other devices, including other Palm™ models, PDA's, computer devices, personal computers, notebooks, etc.
General Overview Of Generic Activation And Registration Framework
[0036] FIG. 3 is a block diagram of the architecture for the generic activation and registration framework (the “GARF”) 200, in accordance with one embodiment of the present invention. The GARF is a system for providing network activation and registration in a network that may have multiple carriers and/or service providers.
[0037] The GARF 200 provides a driver device 202 that generally controls network activation and registration procedures for the computer 100. Networking applications that may be tailored for a specific carrier or service provider are not included in the driver device. Rather, a plug-in device 204 (or multiple plug-in devices) may be installed in the computer 100. A plug-in device 204 includes hardware and/or software specifically tailored for a particular carrier and service provider. Through a given plug-in device 204, the computer 100 can communicate with a carrier and service provider that is intended for that plug-in device 204. For example, a driver device 202 may communicate with a provider's web server 206 with assistance from the plug-in device 204. Additionally, the provider's web server 206 can send a registration file 208 to the driver device 202, which can then launch the registration file 208 in the computer 100. The registration file 208 is an executable file configured to allow the computer 100 to be compatible with a particular carrier and/or service provider.
[0038] The GARF 200 allows manufacturers to build a computer 100 for operation in wireless networks of any verbal language. For example, a generic driver device 202 may be built that is nonspecific to any particular verbal language. The plug-in device 204, on the other hand, may then be configured to be language specific. If France, for instance, has three different service providers that operate the same way in the French language, the GARF 200 allows one computer 100 to communicate with all three service providers. In another embodiment, the plug-in device 204 is generically built such that the computer 100 is generically operable in any wireless network of any verbal language.
Overview of Driver Device
[0039] The driver device 202 is hardware, software, or combination thereof, that is configured to manage procedures of the GARF 200. In one embodiment, the driver device 202 includes an icon on the display screen 130 for a user to select. Selection of the icon launches GARF 200 procedures, including activating a wireless network with a carrier and handling user registration with a service provider. BellSouth™, used with Palm VII™, is an example of a carrier. Palm.Net™, used with Palm VII™, is an example of a service provider. Palm.Net™ currently resells BellSouth™ services for use with Palm VII™.
[0040] In one embodiment, the driver device 202 is an executable application that a user will launch upon their first interaction with a wireless capable computer 100. The driver device 202 will drive the configuration of the computer 100 to obtain wireless connectivity, as well as perform the tasks required to obtain an account and/or identity with a particular carrier and/or service provider. In one example, the driver device 202 may be launched by applications such as Clipper™ (used in the Palm™ operating system) when wireless connectivity has not yet been established for the computer 100.
[0041] A feature of the GARF 200 is the ability for a user to step through a number of screens in order to provide personal data to a wireless service provider, such as Palm.Net™. This setup process involves a number of steps, including retrieving the appropriate screen(s), entering user information, submitting the information to the driver device, writing the personal data in memory, and submitting the data to the service provider.
[0042] The driver device 202 is responsible for maintaining the system features (via the plug-in device 204). As an example, the Palm™ operating system requires certain system maintenance to ensure successful network transactions with the carrier and service provider. The driver device 202 accomplishes its tasks by launching a plug-in device 204 to activate the network on the device (and to display location/carrier specific user interfaces and error messages). The driver device 202 can also call upon a registration file 208, which in turn may be configured to execute registration procedures on the computer 100. The driver device 202 exposes and calls upon application program interfaces (API's) in both the plug-in device and the registration file 208.
[0043] The driver device 202 is not tailored to a specific carrier and/or service provider. Rather, the driver device 202 is generic to various carriers and/or service providers in a given wireless network. For example, the driver device 202 may be generally operable in all networks in France, but the internal components are not programmed to handle communications with one specific carrier and/or service provider. In one embodiment, the driver device 202 is built into the memory device 120 or, more specifically, into a read-only memory (ROM) portion of the memory device 120.
[0044] In one embodiment, communications from the provider's web server 206 to the driver device 202 are handled in a protocol that includes Hypertext Transfer Protocol (HTTP) over Transmission Control Protocol/Internet Protocol (TCP/IP). Communications from the driver device 202 to the carrier are handled in a protocol that includes Hypertext Transfer Protocol (HTTP) over Compressed Transfer Protocol (CTP), or the carrier's own network protocol is used. Another embodiment handles communications with File Transfer Protocol (FTP) over TCP/IP. Other types of TCP/IP-based protocols may alternatively be used to communicate. The present invention is not limited to the specific protocols disclosed herein.
[0045] In an alternative embodiment, deactivation of the carrier and de-registration of the service provider can occur. A computer 100 is deactivated when the computer 100 is no longer enabled to communicate in the wireless network. A computer 100 is de-registered when the computer 100 no longer has an account with a service provider. Deactivation or de-registration can occur in at least the following two ways: some external process (outside of the computer 100) can be invoked to execute deactivation or de-registration; or the plug-in device 204 can be explicitly prompted to execute deactivation or de-registration.
[0046] To deactivate/de-register a computer 100, the driver device 202 searches through all plug-in devices 204 in the computer 100. If no plug-in devices 204 are found, deactivation is complete because without a plug-in device, a computer 100 is not network activated. In searching for plug-in devices 204, the computer 100 determines which network plug-in device is responsible for deactivation. The driver device 202 launches the found plug-in with a deactivation code. Note that the deactivation code must be accompanied by appropriate parameters to denote the desired plug-in device for deactivation. If the plug-in device also contains the service provider's registration (or de-registration) set of codes, the driver device 202 must determine whether to launch the plug-in device 204 with a “de-register” code first. In one embodiment, the deactivation code is called by a registration file 208 that is in the process of deactivating a component of service.
Overview of Plug-in Device
[0047] The plug-in device 204 is hardware, software, or combination thereof, that allows the computer 100 to be compatible with a particular carrier and particular service provider. In a preferred embodiment, the plug-in device 204 is an interface between software (e.g., wireless browser application) and hardware (e.g., mobile radio device 140) in the computer 100.
[0048] The plug-in device 204 may be configured to assist in establishing activation and registration, by executing functions such as the following: setting system features for the network activation upon resetting of the GARF 200; network activation/deactivation with a particular carrier and registration/de-registration with a particular service provider; maintenance of account identification for a particular carrier and a particular service provider; and initiating appropriate user interfaces during error conditions.
[0049] In a preferred embodiment, the plug-in device has the following two primary purposes upon launch by the driver device 202: (1) activate the computer 100 on a wireless network; and (2) register the computer 100 with a service provider such as Palm.Net™, thereby allowing the computer 100 to utilize the service provider's wireless services. The purpose of the GARF 200 is to perform common procedures in the wireless network. The plug-in device 204 is the component of the GARF 200 that contains differences for a particular mobile radio device 140, a particular carrier, and a particular service provider, among other things. In one embodiment, the plug-in device 204 is an executable file that is easily installable into memory of the computer 100.
[0050] A plug-in device 204 is responsible for network activation and registration, setting system features, and updating the memory state of the computer 100 according to the network being activate. In one embodiment, the plug-in device 204 is tailored for a particular carrier and particular service provider. BellSouth™ is an example of a carrier. Palm.net™ is an example of a service provider. The carrier and service provider, in turn, operate in a particular type of network. Mobitex™ is an example of a wireless packet data network. Other examples of a network include a cell phone network, a digital personal communications service (PCS) network, and a global system for mobile communications (GSM) network. Thus, the plug-in is further configured to be compatible with the network in which the particular carrier operates.
[0051] As a secondary function, the plug-in device 204 provides error and warning code user interfaces, which are tailored to a particular verbal language (e.g., French, English, German, Spanish).
[0052] In another embodiment, the plug-in device 204 is designed to be compatible with multiple carriers and service providers in a given network. For example, the plug-in device 204 may be multiplexed to receive a call from the driver device 202, and the plug-in device 204 may then switch between different carriers, depending on the call. In still another embodiment, multiple, different plug-in devices 204 may be installed in the computer 100, for example, to allow the user to have a choice of various carriers and/or service providers. In yet another embodiment, a general plug-in device 204 is provided, for example, a plug-in device compatible with an English language wireless network covering all of North America. Alternatively, a more specific plug-in device 204 may be installed to handle carriers and service providers, for example, in just the western United States.
[0053] Further, the different plug-in devices 204 may be configured to be compatible with each other. Regardless of the particular configuration of the plug-in devices 204, however, a plug-in device 204 is a component that can be readily redesigned after a computer 100 has been manufactured. Such flexibility of a plug-in device 204 is useful because hardware and software components in a computer 100 may be entrenched within the computer's operating system (e.g., the ROM). Thus, the plug-in device 204 provides a component for the computer 100 that facilitates changing the computer's compatibility for different carriers and/or service providers.
[0054] Regarding commands that the driver device 202 sends to the plug-in device 204, a plug-in device 204 is preferably designed to handle certain predefined launch codes from the driver device 202. Table 1 below contains examples of launch codes that may be used in the Palm™ operating system.
[0055]
Overview of Auxiliary Screen Flow
| TABLE 1 | ||
|---|---|---|
| Examples Of Launch Codes That Driver Device 202 May | ||
| Include In A Command Sent To Plug-In Device 204 | ||
| PLUGIN_TYPE | Return a wireless network or | |
| service provider, or both to | ||
| the caller-noting the type of | ||
| plug-in | ||
| WN_RESET | Set any system features needed | |
| for network stack of device | ||
| release | ||
| SP_RESET | Set any system features needed | |
| for service provider | ||
| CK_WN_ACTIVATE | Check system feature and memory | |
| values (when system features may | ||
| not be correct) to determine | ||
| (true or false) if the wireless | ||
| network is active | ||
| WN_ACTIVATE | Configure a device so that it | |
| is able to effectively | ||
| communicate on the network | ||
| WN_DEACTIVATE | Perform a wireless network | |
| deactivation | ||
| CK_SP_REGISTER | Check system features and | |
| database entries (when system | ||
| features may not be correct) | ||
| to determine (true or false) | ||
| if the service provider has | ||
| been registered with. If the | ||
| service provider has not been | ||
| successfully registered with, | ||
| this call will return false, | ||
| with an optional parameter of | ||
| a URL. The URL can then be | ||
| used by the driver to retrieve | ||
| a registration file 208. | ||
| SP_DEACTIVATE | Remove any system features, | |
| database entries, or flash | ||
| values utilized by the service | ||
| provider to denote successful | ||
| registration. | ||
| SP_COMPLETE | Perform any service-provider- | |
| centric flash/system feature/ | ||
| database entry activity that | ||
| denotes the FINAL step of | ||
| activation and registration | ||
| SP_FAIL | Perform any service-provider- | |
| specific cleanup activity that | ||
| must be performed to return | ||
| the state of the device to | ||
| normal | ||
Overview of Auxiliary Screen Flow
[0056] In order to create and provision accounts with a given service provider, the service provider most-likely wants to collect data about the user. Such data may include name, address, account identifier, password, etc.
[0057] The auxiliary screen flow of the GARF 200 involves downloading and executing a registration file 208 from the provider's web server 206. A registration file 208 is preferably an executable file configured to be executed as-is on the computer 100. (In the Palm™ operating system, an executable file is commonly referred to as a “PRC”.) The registration file 208 renders a set of dialogs (or “screens”) to collect user registration data. The registration file has a calling convention and an expected set of results. The driver device 202 can then control procedures to set up the account for the user.
[0058] In other words, in order to collect user information for service provider registration, the driver device 202 has the ability to dynamically query (i.e., download) a server of the provider for the registration file 208. The registration file 208 is preferably kept as minimal in size as possible so as not to unduly delay the user's experience. As an example, the plug-in device sends a uniform resource locator (URL), or address, to the driver device 202. The driver device 202 in turn sends a request to the provider's web server 206 to retrieve the registration file 208 located at the URL. Once retrieved, the registration file 208 may be executed on the computer 100 to collect user registration data. In one embodiment, execution of the registration file 208 involves communicating directly with the web, without first going through the driver device 202.
[0059] The registration file 208 should be a temporary executable file configured to delete itself after its operations have been performed (i.e., after registration is complete). The registration file 208 should exit execution successfully (or with a failure error) directly to the driver device 202, so that any cleaning-up or processing by the computer 100 may resume. In other words, the registration file 208 should not leave the computer 100 in an unstable state. In one embodiment, the registration file 208 uses Compressed Transfer Protocol (CTP) calls. The registration file 208 may be configured to utilize error and warning user interfaces contained within the plug-in device 204. In a preferred embodiment, the registration file 208 is configured to utilize error and warning user interfaces contained within the registration file 208 itself.
[0060] The registration file 208 can be configured dynamically by the service provider. For example, if the service provider changes its rate plan, the registration file 208 can readily be changed to accommodate the new rate plan. The new rate plan can then be displayed to the user when the registration file 208 is downloaded and executed on the computer 100. Note that the registration file 208 resides outside of computer 100 (at provider's web server 206, for example) before the registration file 208 is downloaded and executed by the driver device 202.
Overview of Provider's Web Server
[0061] In a preferred embodiment, the provider's web server 206 is accessible via a communication network. Examples of a communication network include a local area network (LAN), a wide area network (WAN), the global packet-switched network known as the “Internet” or the “World Wide Web” (web). The web server 206 provides the registration files 208 of the auxiliary screen flow, as well as any other logic to be used from within the executable file. In one example, the provider's web server 206 is accessible via the Internet through Palm™ Web Clipping Proxy Servers. HTTP is the proxiable protocol handled by Web Clipping Proxy Servers.
[0062] As discussed above with reference to the auxiliary screen flow, the plug-in device 204 may return a URL to the driver device 202. The URL is then sent as a request to the provider's web server 206. That URL returns one static registration file 208 for the auxiliary screen flow. Accordingly, the service provider preferably carves some space from its file system directory to store the screens for the execution of the registration file 208.
Process Overview
[0063] FIG. 4 shows a high-level flowchart for a method of managing network activation with a carrier and registration with a service provider, in accordance with one embodiment of the present invention. The method starts in step 301 where a network activation status is determined. It may be determined, for example, that a wireless network for the mobile radio device 140 is enabled, but the computer 100 is not activated with a carrier. In such a case, the computer 100 will perform network activation procedures in step 302.
[0064] In step 303, registration status with a service provider is determined. If the computer 100 is not registered, a request will be sent to a server of a service provider in step 304. This request preferably contains an address to a registration file 208 configured to gather user registration information. The registration file is received from the server in step 306. In step 308, the registration file 208 is executed on the computer 100. Execution of the registration file 208 involves gathering registration information from the user. In another embodiment, the method further includes returning the gathered data to the server to complete network activation.
[0065] In one embodiment, the method steps of FIG. 4 are managed by the driver device 202. As discussed above with reference to FIG. 3 , the driver device will drive the configuration process to obtain wireless network activation, as well as perform the tasks required to obtain an account and/or identity with a particular service provider.
[0066] FIG. 5A and FIG. 5B , collectively, show a more detailed flowchart for a method of managing network activation with a carrier and registration with a service provider, in accordance with one embodiment of the present invention. The method starts in step 402 where a driver device 202 in the computer 100 is launched. For example, the driver device 202 may include a user-selectable icon on the display screen 130 of the computer 100, as discussed above with reference to FIG. 3 . Upon selection of the icon, the driver device 202 is launched, thereby starting procedures of the GARF 200.
[0067] In step 404, the plug-in device 204 is launched to check for network activation with a carrier. As discussed above with reference to FIG. 3 , the computer 100 may contain multiple, different plug-in devices 204. In a preferred embodiment, the driver device 202 scans for all of the plug-in devices 204 by searching the computer 100 for devices that match a particular file type. Accordingly, when a plug-in device 204 is designed, the plug-in device 204 should be designed to match a predetermined type that is searchable by the driver device 202. In one embodiment, the driver device 202 makes a call to each and every plug-in device 204 and checks for network activation in each.
[0068] As an example of step 404, the driver device 202 sends a “check wireless network activation” command (e.g., CK_WN_ACTIVATE) to a plug-in device 204 that has information on whether the computer 100 is network activated. “Network activated” means that the computer is capable of communicating in the network (e.g., Mobitex™) provided by the carrier (e.g., BellSouth™). Accordingly, a given wireless network can have multiple, different carriers operating in the given wireless network type. In a preferred embodiment, the computer 100 is manufactured to be network activated by having the mobile radio device 140 and appropriate network components built into the operating system of the computer 100. If the computer 100 is not network activated, a plug-in device 204 is launched in step 405 to activate the network with the computer 100. The launched plug-in device handles the activation process. If network activation fails, an error is returned to the driver device 202, an appropriate error message is displayed, and the method is done.
[0069] Assuming the computer 100 is appropriately network activated, a plug-in device 204 is launched to check for registration with a service provider in step 406. “Device” registration means that the computer 100 has an account with a service provider in the wireless network. In an alternative embodiment, “user” registration means that the user of the computer 100 has an account with the service provider. In another embodiment, both the device and the user may be registered with the service provider, and the account with the service provider contains information specific to both the user and the particular device (i.e., computer 100). In this description, “device” registration and “user” registration may be used interchangeably to refer generally to account registration with a service provider.
[0070] In decision operation 408, it is determined if the device is registered with a service provider. In other words, it is determined if an account exists with a service provider in the given wireless network. If the device is registered, a plug-in device is launched in step 410 with an error to indicate the device is already registered. For example, a dialog screen (e.g., “Already Activated”) is displayed to indicate to the user that the computer 100 has previously been registered with Palm.Net™.
[0071] However, if the device is not registered, an address to a registration file 208 is received from the plug-in device 204 in step 412. For example, the plug-in device 204 may have a URL for a registration file 208, as discussed above with reference to FIG. 3 . In one embodiment, this registration file 208 is located on a provider's web server 206. The registration file 208 is an executable file configured to gather registration information from the user. The plug-in device 204 sends the registration file's URL to the driver device 202 upon determining that the computer 100 is not registered with the particular service provider.
[0072] In step 414, a request is sent to a server of the service provider for the registration file 208. For example, as discussed above with reference to FIG. 3 , the driver device 202 sends an HTTP request to a web server of the service provider. The HTTP request includes the registration file's URL. Communications with the provider's web server 206 may include procedures for encrypting data, connecting with the web server, and sending the URL to the web server. Information that may be imbedded in the URL includes the following: carrier identification, the type of verbal language (e.g., English or French) in which the computer 100 is operating, screen resolution of the display screen 130, and other environmental information of the computer 100.
[0073] In step 416, the registration file 208 is received from the server. For example, upon receiving the HTTP request from the driver device 202, the web server directs the registration file 208 to be returned to the computer 100.
[0074] The method continues in FIG. 5B with launching the registration file 208 in step 418. For example, as discussed above with reference to FIG. 3 , an auxiliary screen flow is downloaded from the web and is executed on the computer 100. Launching the registration file starts in decision operation 420, where it is determined if an account is to be setup with the particular service provider. For example, the registration file 208 displays a dialog on the display screen 130 to query the user if an account is to be setup. If an account is not to be setup, a “Cancel” screen is displayed in step 422 and the method is done. For example, the user may select a “Cancel” icon that initiates cancellation procedures of the registration process.
[0075] If an account is to be setup, registration information is then received from the user in step 424. For example, dialog screens are displayed during execution of the registration file 208 for the user to respond to registration queries. These dialog screens may query the user for some of the following information: username, alternative username, password, password question, password answer, first name, last name, email address, gender, birthday, and mailing address. The computer 100 receives the corresponding user-inputted information.
[0076] After user registration is received, it is determined in decision operation 426 if registration is to be confirmed or cancelled. For example, a dialog screen appears to query the user of whether to “confirm” or to “cancel” the registration process with the service provider. If registration is to be cancelled, the registration process is ceased and control is returned to the driver device 202 in step 440.
[0077] However, if registration is to be confirmed, the data gathered by the registration file 208 in step 424 is returned to the provider's web server 206 to complete network registration in step 428. For example, the registration file 208 sends the gathered account data to the driver device 202, which in turn sends the gathered account data to the provider's web server 206.
[0078] In decision operation 430, it is determined if registration is acceptable to the service provider. For example, upon receiving the account data, the service provider responds in approval or denial of registration. Registration may be unacceptable for the following reasons: insufficient information (e.g., no username provided by the user), or invalid information (e.g., a password that is too short or a username that is already in existence). If registration is not acceptable, an “Error” screen is displayed in step 436. The user will be queried whether to retry. If the user does not want to retry registration, control is returned to the driver device 202 in step 440. However, if the user does want to retry, the method returns to step 418 where the registration file 208 is reset and launched.
[0079] On the other hand, if registration is acceptable, a “Done” screen is displayed in step 432. For example, the registration file 208 launches the done screen to indicate to the user that registration is acceptable and confirmed with the service provider. In step 434, a user identification is received from the provider's web server 206. For example, the web server returns an identification code that uniquely identifies the computer 100 and/or the user for future logons with the service provider.
[0080] In one example, the identification code is accompanied by an HTTP cookie for the computer 100 to store in a cookie jar in the computer 100. An HTTP cookie, in this context, is a text file that contains registration information necessary for logons with the service provider. A cookie jar is a memory location in the computer 100 for storing HTTP cookies. The HTTP cookie may be retrieved from the cookie jar during future logons. The HTTP cookie will allow for quick and easy logons, that is, when the user logs onto the same service provider using the same computer 100.
[0081] If for some reason the user identification is not properly received from the provider's web server 206, error messages are displayed and the computer 100 retries to get the user identification from the provider's web server 206.
[0082] In step 440, control of network setup procedures is returned to the driver device 202. Success or failure parameters from the registration process are also returned to the driver device 202. Registration completion operations are then performed in step 442. For example, the driver device 202 may send success commands to a plug-in device 204, which will in turn initiate displaying of successful completion screens. Alternatively, the driver device 202 may send failure commands to a plug-in device 204, which will in turn initiate displaying of cancellation screens. Upon performing the completion operations, the method is then done.
System And Method Implementation
[0083] Portions of the present invention may be conveniently implemented using a conventional general purpose or a specialized digital computer or microprocessor programmed according to the teachings of the present disclosure, as will be apparent to those skilled in the computer art.
[0084] Appropriate software coding can readily be prepared by skilled programmers based on the teachings of the present disclosure, as will be apparent to those skilled in the software art. The invention may also be implemented by the preparation of application specific integrated circuits or by interconnecting an appropriate network of conventional component circuits, as will be readily apparent to those skilled in the art.
[0085] The present invention includes a computer program product which is a storage medium (media) having instructions stored thereon/in which can be used to control, or cause, a computer to perform any of the processes of the present invention. The storage medium can include, but is not limited to, any type of disk including floppy disks, mini disks (MD's), optical discs, DVD, CD-ROMS, micro-drive, and magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, DRAMs, VRAMs, flash memory devices (including flash cards), magnetic or optical cards, nanosystems (including molecular memory ICs), RAID devices, remote data storage/archive/warehousing, or any type of media or device suitable for storing instructions and/or data.
[0086] Stored on any one of the computer readable medium (media), the present invention includes software for controlling both the hardware of the general purpose/specialized computer or microprocessor, and for enabling the computer or microprocessor to interact with a human user or other mechanism utilizing the results of the present invention. Such software may include, but is not limited to, device drivers, operating systems, and user applications. Ultimately, such computer readable media further includes software for performing the present invention, as described above.
[0087] Included in the programming (software) of the general/specialized computer or microprocessor are software modules for implementing the teachings of the present invention, including, but not limited to, identifying plug-in devices, requesting registration file downloads, launching registration processes, and transferring registration data to service providers, according to processes of the present invention.
[0088] In the foregoing specification, the invention has been described with reference to specific embodiments thereof. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of the invention. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.
Claims
What is claimed is:
1. A mobile computing device, comprising:
a memory comprising network settings for compatibility with a plurality of different wireless carriers; and
a processing device configured to obtain network settings for a particular carrier from the memory based on an account ID and to activate the mobile computing device with the carrier based on the network settings and the ID, wherein the account ID identifies the mobile computing device or a user of the mobile computing device, wherein the network settings for compatibility with a plurality of different wireless carriers are stored in a read-only memory (ROM) portion of the memory, wherein the processing device is configured to obtain an account associated with the account ID from the particular carrier, wherein the account comprises a user name and password.
2. The mobile computing device of claim 1, wherein the memory further comprises carrier-specific user interface setting and the processing device is configured to display a carrier-specific user interface based on a particular carrier associated with the account ID.
3. The mobile computing device of claim 1, further comprising a display, wherein the processing device is configured to obtain the network settings in response to a user launching an executable application using the display.
4. The mobile computing device of claim 3, wherein the user launches the executable application via a user-selectable icon on the display.
5. The mobile computing device of claim 1, wherein the network settings are built into the operating system of the mobile computing device.
6. The mobile computing device of claim 1, wherein the processing device is configured to update the memory according to a network associated with the carrier on which the mobile computing device is activated.
7. The mobile computing device of claim 1, wherein the network settings are for compatibility with a plurality of different wireless carriers using a global system for mobile communications (GSM) network.
8. The mobile computing device of claim 1, wherein the processing device is configured to receive a choice of carriers from a user and to obtain the network settings based on the choice.
9. A mobile computing device, comprising:
a memory comprising network settings for compatibility with a plurality of different wireless carriers, wherein the network settings are stored in a read-only memory portion of the memory; and
a processing device configured to obtain an account associated with an account ID from a particular carrier, the account comprising a user name and password, wherein the account ID identifies the mobile computing device or a user of the mobile computing device, the processing circuit further configured to activate the mobile computing device on a network using the network settings, to deactivate the mobile computing device on the network, and to activate the mobile computing device on a second network using network settings associated with the account ID.
10. The mobile computing device of claim 9, wherein the network settings are for compatibility with a plurality of different wireless carriers using a global system for mobile communications (GSM) network.
11. The mobile computing device of claim 9, wherein the mobile computing device is a handheld device.
12. A mobile computing device, comprising:
a memory comprising network settings for making the mobile computing device able to communicate in a plurality of different wireless carrier networks, wherein the network settings for compatibility with a plurality of different wireless carriers are stored in a read-only memory portion of the memory; and
a processing device configured to obtain network settings for a particular carrier network from the memory based on an identifier and to make the mobile computing device able to communicate in the carrier network based on the network settings and the identifier, wherein the identifier identifies the mobile computing device or a user of the mobile computing device, wherein the identifier is associated with an account comprising a user name and password.
13. The mobile computing device of claim 12, wherein the processing device is configured to update the memory according to a network associated with the carrier on which the mobile computing device is activated.
14. The mobile computing device of claim 13, wherein the processing device is configured to operate an address book and a daily organizer.
15. The mobile computing device of claim 14, wherein the network settings are for compatibility with a plurality of different wireless carriers using a global system for mobile communications (GSM) network.
16. The mobile computing device of claim 15, wherein the processing device is configured to obtain the account associated with the identifier from the carrier network.
Patent Citations (156)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4779081(A) | 1988-10-01 | Nakayama et al. | Applicant |
| US4788675(A) | 1988-11-01 | Jones et al. | Applicant |
| US5010547(A) | 1991-04-01 | Johnson et al. | Applicant |
| US5012219(A) | 1991-04-01 | Henry | Applicant |
| US5075684(A) | 1991-12-01 | DeLuca | Applicant |
| US5134719(A) | 1992-07-01 | Mankovitz | Applicant |
| US5303393(A) | 1994-04-01 | Noreen et al. | Applicant |
| US5359317(A) | 1994-10-01 | Gomez et al. | Applicant |
| US5394140(A) | 1995-02-01 | Wong et al. | Applicant |
| US5430436(A) | 1995-07-01 | Fennell | Applicant |
| US5485505(A) | 1996-01-01 | Norman et al. | Applicant |
| US5612682(A) | 1997-03-01 | DeLuca et al. | Applicant |
| US5621784(A) | 1997-04-01 | Tiedemann, Jr. et al. | Applicant |
| US5650776(A) | 1997-07-01 | Mitchell et al. | Applicant |
| US5705995(A) | 1998-01-01 | Laflin et al. | Applicant |
| US5758069(A) | 1998-05-01 | Olsen | Applicant |
| US5787365(A) | 1998-07-01 | Rivero et al. | Applicant |
| US5819173(A) | 1998-10-01 | Lawrence et al. | Applicant |
| US5839054(A) | 1998-11-01 | Wright et al. | Applicant |
| US5850599(A) | 1998-12-01 | Seiderman | Applicant |
| US5859419(A) | 1999-01-01 | Wynn | Applicant |
| US5892900(A) | 1999-04-01 | Ginter et al. | Applicant |
| US5903852(A) | 1999-05-01 | Schaupp, Jr. et al. | Applicant |
| US5956636(A) | 1999-09-01 | Lipsit | Applicant |
| US5958006(A) | 1999-09-01 | Eggleston et al. | Applicant |
| US6000000(A) | 1999-12-01 | Hawkins et al. | Applicant |
| US6009409(A) | 1999-12-01 | Adler et al. | Applicant |
| US6035212(A) | 2000-03-01 | Rostoker et al. | Applicant |
| US6044403(A) | 2000-03-01 | Gerszberg et al. | Applicant |
| US6047066(A) | 2000-04-01 | Brown et al. | Applicant |
| US6108727(A) | 2000-08-01 | Boals et al. | Applicant |
| US6124799(A) | 2000-09-01 | Parker | Applicant |
| US6141010(A) | 2000-10-01 | Hoyle | Applicant |
| US6157630(A) | 2000-12-01 | Adler et al. | Applicant |
| US6157814(A) | 2000-12-01 | Hymel et al. | Applicant |
| US6175860(B1) | 2001-01-01 | Gaucher | Applicant |
| US6208853(B1) | 2001-03-01 | Lo Vasco et al. | Applicant |
| US6216112(B1) | 2001-04-01 | Fuller et al. | Applicant |
| US6223030(B1) | 2001-04-01 | Van Den Heuvel et al. | Applicant |
| US6240185(B1) | 2001-05-01 | Van Wie et al. | Applicant |
| US6253326(B1) | 2001-06-01 | Lincke et al. | Applicant |
| US6259405(B1) | 2001-07-01 | Stewart et al. | Applicant |
| US6282421(B1) | 2001-08-01 | Chatterjee et al. | Applicant |
| US6292833(B1) | 2001-09-01 | Liao et al. | Applicant |
| US6300946(B1) | 2001-10-01 | Lincke et al. | Applicant |
| US6301666(B1) | 2001-10-01 | Rive | Applicant |
| US6343318(B1) | 2002-01-01 | Hawkins et al. | Applicant |
| US6360272(B1) | 2002-03-01 | Lincke et al. | Applicant |
| US6397246(B1) | 2002-05-01 | Wolfe | Applicant |
| US6397259(B1) | 2002-05-01 | Lincke et al. | Applicant |
| US6425087(B1) | 2002-07-01 | Osborn et al. | Applicant |
| US6430603(B2) | 2002-08-01 | Hunter | Applicant |
| US6453371(B1) | 2002-09-01 | Hampson et al. | Applicant |
| US6457134(B1) | 2002-09-01 | Lemke et al. | Applicant |
| US6480762(B1) | 2002-11-01 | Uchikubo et al. | Applicant |
| US6490445(B1) | 2002-12-01 | Holmes | Applicant |
| US6493327(B1) | 2002-12-01 | Fingerhut | Applicant |
| US6519470(B1) | 2003-02-01 | Rydbeck | Applicant |
| US6523124(B1) | 2003-02-01 | Lunsford et al. | Applicant |
| US6526275(B1) | 2003-02-01 | Calvert | Examiner |
| US6539101(B1) | 2003-03-01 | Black | Applicant |
| US6549773(B1) | 2003-04-01 | Linden et al. | Applicant |
| US6560640(B2) | 2003-05-01 | Smethers | Applicant |
| US6564056(B1) | 2003-05-01 | Fitzgerald | Applicant |
| US6564104(B2) | 2003-05-01 | Nelson et al. | Applicant |
| US6581025(B2) | 2003-06-01 | Lehman | Applicant |
| US6587684(B1) | 2003-07-01 | Hsu et al. | Applicant |
| US6590588(B2) | 2003-07-01 | Lincke et al. | Applicant |
| US6591098(B1) | 2003-07-01 | Shieh et al. | Applicant |
| US6591288(B1) | 2003-07-01 | Edwards et al. | Applicant |
| US6594482(B1) | 2003-07-01 | Findikli et al. | Applicant |
| US6594484(B1) | 2003-07-01 | Hitchings, Jr. | Examiner |
| US6600743(B1) | 2003-07-01 | Lee et al. | Examiner |
| US6603969(B1) | 2003-08-01 | Vuoristo et al. | Examiner |
| US6622017(B1) | 2003-09-01 | Hoffman | Applicant |
| US6628928(B1) | 2003-09-01 | Crosby et al. | Applicant |
| US6628934(B2) | 2003-09-01 | Rosenberg et al. | Applicant |
| US6636489(B1) | 2003-10-01 | Fingerhut | Applicant |
| US6636502(B1) | 2003-10-01 | Lager et al. | Examiner |
| US6675165(B1) | 2004-01-01 | Rothschild | Applicant |
| US6675202(B1) | 2004-01-01 | Perttunen | Applicant |
| US6675204(B2) | 2004-01-01 | De Boor et al. | Applicant |
| US6681259(B1) | 2004-01-01 | Lemilainen et al. | Examiner |
| US6686838(B1) | 2004-02-01 | Rezvani et al. | Applicant |
| US6694428(B2) | 2004-02-01 | Lemke et al. | Applicant |
| US6701521(B1) | 2004-03-01 | McLlroy et al. | Applicant |
| US6704295(B1) | 2004-03-01 | Tari et al. | Applicant |
| US6732176(B1) | 2004-05-01 | Stewart et al. | Examiner |
| US6745011(B1) | 2004-06-01 | Hendrickson et al. | Applicant |
| US6745029(B2) | 2004-06-01 | Lahtinen et al. | Applicant |
| US6795710(B1) | 2004-09-01 | Creemer | Applicant |
| US6816725(B1) | 2004-11-01 | Lemke et al. | Applicant |
| US6829560(B2) | 2004-12-01 | Lehman | Applicant |
| US6829596(B1) | 2004-12-01 | Frazee | Applicant |
| US6829704(B2) | 2004-12-01 | Zhang et al. | Applicant |
| US6874017(B1) | 2005-03-01 | Inoue et al. | Applicant |
| US6880048(B1) | 2005-04-01 | Lemke | Applicant |
| US6885877(B1) | 2005-04-01 | Ozaki et al. | Applicant |
| US6961567(B1) | 2005-11-01 | Kuhn | Applicant |
| US6983375(B2) | 2006-01-01 | Zhang et al. | Applicant |
| US6996407(B2) | 2006-02-01 | Taniguchi | Applicant |
| US7010296(B2) | 2006-03-01 | Sakai et al. | Examiner |
| US7010603(B2) | 2006-03-01 | Martin et al. | Examiner |
| US7024464(B1) | 2006-04-01 | Lusher et al. | Applicant |
| US7089036(B2) | 2006-08-01 | Prise | Applicant |
| US7103370(B1) | 2006-09-01 | Creemer | Applicant |
| US7266369(B2) | 2007-09-01 | Moles et al. | Applicant |
| US7266379(B2) | 2007-09-01 | Blight et al. | Applicant |
| US7286251(B2) | 2007-10-01 | Tomida et al. | Applicant |
| US7359516(B1) | 2008-04-01 | Skinner et al. | Examiner |
| US7366702(B2) | 2008-04-01 | David | Applicant |
| US7378771(B2) | 2008-05-01 | LeBlanc et al. | Applicant |
| US7387771(B1) | 2008-06-01 | Kratz | Applicant |
| US7536190(B1) | 2009-05-01 | Creemer | Applicant |
| US7538771(B2) | 2009-05-01 | Nakamura et al. | Applicant |
| US7555571(B1) | 2009-06-01 | Skinner | Applicant |
| US2001/0044310(A1) | 2001-11-01 | Lincke | Applicant |
| US2001/0047272(A1) | 2001-11-01 | Frietas et al. | Applicant |
| US2002/0045457(A1) | 2002-04-01 | Taniguchi | Applicant |
| US2002/0073046(A1) | 2002-06-01 | David | Applicant |
| US2002/0082049(A1) | 2002-06-01 | Prise | Examiner |
| US2002/0085577(A1) | 2002-07-01 | Kim | Applicant |
| US2002/0152400(A1) | 2002-10-01 | Zhang et al. | Applicant |
| US2002/0161990(A1) | 2002-10-01 | Zhang et al. | Applicant |
| US2002/0177438(A1) | 2002-11-01 | Sakai et al. | Applicant |
| US2003/0013434(A1) | 2003-01-01 | Rosenberg et al. | Applicant |
| US2003/0050046(A1) | 2003-03-01 | Conneely et al. | Applicant |
| US2003/0055912(A1) | 2003-03-01 | Martin et al. | Examiner |
| US2003/0162533(A1) | 2003-08-01 | Moles et al. | Applicant |
| US2004/0254827(A1) | 2004-12-01 | Hind et al. | Applicant |
| US2005/0009514(A1) | 2005-01-01 | Mathews et al. | Applicant |
| US2005/0021458(A1) | 2005-01-01 | Rowe | Applicant |
| US2006/0030306(A1) | 2006-02-01 | Kuhn | Applicant |
| US2006/0116507(A1) | 2006-06-01 | Oppermann et al. | Applicant |
| US2007/0169084(A1) | 2007-07-01 | Frank et al. | Applicant |
| US2007/0178899(A1) | 2007-08-01 | Kuhn | Applicant |
| US2007/0203844(A1) | 2007-08-01 | Kuhn et al. | Applicant |
| US2008/0003994(A1) | 2008-01-01 | Skinner | Applicant |
| US2009/0005039(A1) | 2009-01-01 | Kuhn | Applicant |
| US2009/0076906(A1) | 2009-03-01 | Kansal et al. | Applicant |
| US2010/0022240(A1) | 2010-01-01 | Skinner | Applicant |
| US2010/0120407(A1) | 2010-05-01 | Kuhn | Applicant |
| US2010/0120428(A1) | 2010-05-01 | Kuhn | Applicant |
| US2010/0165938(A1) | 2010-07-01 | Kuhn et al. | Applicant |
| US2010/0169217(A1) | 2010-07-01 | Kuhn et al. | Applicant |
| EP464988(A2) | 1992-01-01 | Applicant | |
| EP464988(A3) | 1992-01-01 | Applicant | |
| EP820206(B1) | 1998-01-01 | Applicant | |
| EP825791(A1) | 1998-02-01 | Applicant | |
| EP862104(A2) | 1998-09-01 | Applicant | |
| EP1551193 | 2005-07-01 | Applicant | |
| WO99/55066(A1) | 1999-10-01 | Applicant | |
| WO1/65411(A1) | 2001-09-01 | Applicant | |
| WO2005/022375(A1) | 2005-03-01 | Applicant | |
| WO2006/055716(A1) | 2006-05-01 | Applicant | |
| WO2007/070510(A2) | 2007-06-01 | Applicant |
Non-Patent Literature (35)
- International Search Report and Written Opinion of the International Searching Authority for International Application No. PCT/US2006/047358; mailed Oct. 1, 2007; 15 pages.Applicant
- “Initial Provisioning of a Cellular Device over the Air”, IBM Technical Disclosure Bulletin, Jun. 1995, vol. 38, No. 6, Jul. 1, 1995 (pp. 201-202).Applicant
- U.S. Appl. No. 09/850,940, filed May 8, 2001, Applicant: Kuhn et al.; Title: “Activation Key for a Wireless-Enabled Device”; Amendment and Reply dated Sep. 1, 2006.Applicant
- U.S. Appl. No. 11/646,177, filed Dec. 27, 2006, Applicant: Kuhn; Title: Generic Activation and Registration Framework for Wireless Devices; Preliminary Amendment dated Dec. 27, 2006.Applicant
- U.S. Appl. No. 11/646,182, filed Dec. 27, 2006, Applicant: Kuhn; Title: “Activation Key for a Wireless Enabled Device”; Preliminary Amendment dated Dec. 27, 2006.Applicant
- “Initial Provisioning of a Cellular Device over the Air”, IBM Technical Disclosure Bulletin, Jun. 1995, vol. No. 38, Issue No. 6, pp. 201-202, Jul. 1, 1995.Applicant
- U.S. Appl. No. 09/732,066, filed Dec. 7, 2000, Craig S. Skinner.Applicant
- U.S. Appl. No. 11/484,184, filed Jul. 10, 2006, Skinner.Applicant
- U.S. Appl. No. 60/954,022, filed Aug. 6, 2007, Swift et al.Applicant
- U.S. Appl. No. 12/473,177, filed May 27, 2009, Skinner.Applicant
- Office Action for U.S. Appl. No. 09/850,940, date mailed Jul. 16, 2007, 9 pages.Applicant
- Office Action for U.S. Appl. No. 11/484,184, date mailed Jul. 17, 2007, 7 pages.Applicant
- Office Action for U.S. Appl. No. 11/484,184, date mailed Sep. 27, 2007, 3 pages.Applicant
- Office Action for U.S. Appl. No. 12/133,281, date mailed Mar. 2, 2009, 9 pages.Applicant
- Protest for U.S. Appl. No. 09/794,082, filed Feb. 24, 2004.Applicant
- Response to Office Action for U.S. Appl. No. 09/850,940, date mailed Oct. 17, 2007, 12 pages.Applicant
- Response to Office Action for U.S. Appl. No. 11/484,184, date mailed Oct. 30, 2007, 19 pages.Applicant
- Response to Office Action for U.S. Appl. No. 11/484,184, date mailed Sep. 17, 2007, 8 pages.Applicant
- Notice of Allowance for U.S. Appl. No. 11/484,184, date mailed May 13, 2009, 6 pages.Applicant
- Office Action for U.S. Appl. No. 11/646,177, mail date Nov. 20, 2009, 10 pages.Applicant
- Office Action for U.S. Appl. No. 12/133,281, mail date Sep. 17, 2009, 9 pages.Applicant
- Office Action for U.S. Appl. No. 09/850,940, mail date Mar. 18, 2008, 11 pages.Applicant
- Office Action for U.S. Appl. No. 11/646,182, mail date Mar. 10, 2010, 14 pages.Applicant
- Office Action for U.S. Appl. No. 12/133,281, mail date Mar. 16, 2010, 8 pages.Applicant
- Office Action for U.S. Appl. No. 11/774,508, mail date Mar. 19, 2010, 11 pages.Applicant
- Office Action for U.S. Appl. No. 09/850,940, mail date Apr. 12, 2010, 17 pages.Applicant
- Office Action for U.S. Appl. No. 12/691,470, mail date Apr. 26, 2010, 9 pages.Applicant
- Office Action for U.S. Appl. No. 12/473,177, mail date May 11, 2010, 7 pages.Applicant
- Office Action for U.S. Appl. No. 11/646,177, mail date Jun. 22, 2010, 8 pages.Applicant
- Office Action for U.S. Appl. No. 12/691,930, mail date Jun. 23, 2010, 9 pages.Applicant
- Office Action for U.S. Appl. No. 11/774,508, mail date Jul. 19, 2010, 10 pages.Applicant
- Office Action for U.S. Appl. No. 12/133,281, mail date Aug. 12, 2010, 8 pages.Applicant
- Office Action for U.S. Appl. No. 11/646,182, mail date Aug. 31, 2010, 14 pages.Applicant
- Office Action for U.S. Appl. No. 12/646,750, mail date Sep. 20, 2010, 12 pages.Applicant
- Office Action for U.S. Appl. No. 11/774,508, mail date Sep. 27, 2010, 11 pages.Applicant