Abstract:
The present invention provides an improved wireless communication device capable of detecting the presence of an external device and dynamically updating its communication abilities to facilitate communication with the external device. The wireless communication device, upon detecting a wired or wireless connection from an external device, queries the external device to obtain summary profile information about the external device. The wireless device next formulates a query comprising at least a portion of the summary profile information and sends the query to a remote server to request an appropriate communication interface. The remote server responds with the appropriate communication interface. Upon receipt of the interface, the wireless communication device installs the interface and then proceeds to establish communication with the external device.

Description:
RELATED APPLICATIONS  
       [0001]    This application is a continuation in part application of U.S. patent application Ser. No. 10/665,962, filed on Sep. 18, 2003, which is a continuation in part of U.S. patent application Ser. No. 09/917,026, filed on Jul. 26, 2001, of U.S. patent application Ser. No. 09/916,900, filed on Jul. 26, 2001, and of U.S. patent application Ser. No. 09/916,460, filed on Jul. 26, 2001, which are hereby incorporated by reference.  
         [0002]    This application is also related to U.S. application Ser. No. unknown entitled “System and Method for Interchangeable Modular Hardware Components for Wireless Communication Devices” and to U.S. application Ser. No. ______ unknown entitled “Modular Software Components for Wireless Communication Devices ”, which are filed concurrently herewith. Additionally, this application is related to U.S. application Ser. No. 09/927,131, filed on Aug. 10, 2001; to U.S. application Ser. No. 09/969,305, filed on Oct. 2, 2001; to U.S. application Ser. No. 09/970,188, filed on Oct. 3, 2001; to U.S. application Ser. No. 09/972,519, filed on Oct. 5, 2001; to U.S. application Ser. No. 10/206,780, filed on Jul. 25, 2002; to U.S. application Ser. No. 10/206,781, filed on Jul. 25, 2002; and to U.S. application Ser. No. 10/206,516, filed on Jul. 25, 2002, which are hereby incorporated by reference. 
     
    
     
       FIELD OF THE INVENTION  
         [0003]    The present invention generally relates to the field of wireless communications and more particularly relates to dynamic interfaces between wireless communication devices and external devices coupled via a wireless or physical connection.  
         BACKGROUND OF THE INVENTION  
         [0004]    Conventional wireless communication devices typically become isolated computing platforms once they are deployed (i.e., sold to a consumer). Consumers typically must bring the wireless communication device (also referred to herein as “wireless device,” “handset,” and “mobile device”) to a service station for upgrades to the operating system or any integral software application such as a phonebook.  
           [0005]    Additionally, if the consumer wants to replace a hardware component of a wireless communication device, the wireless device must be brought into a service station. Generally, hardware replacements are prohibitively expensive if the wireless device is not broken and under warranty. Even so, when a wireless device under warranty has a hardware component replaced, the new component is merely a working version of the component being replaced. Thus, when a consumer purchases a wireless communication device, the consumer is locked into the physical configuration of the wireless device for the life of the wireless communication device.  
           [0006]    An additional drawback of conventional wireless communication devices is that new external devices, such as digital cameras, are limited to the specific, proprietary device that is offered by the manufacturer of the handset. Thus, a consumer&#39;s choice of external devices that enhance a wireless communication device is severely limited. Therefore, what is needed is a system and method that overcomes these significant problems found in the conventional systems as described above.  
         SUMMARY OF THE INVENTION  
         [0007]    Conventional wireless communication devices are isolated computing platforms. External devices that are connected to a wireless communication device after it has been deployed are limited to a set of specific, proprietary devices that the manufacturer has enabled during the design and construction of the wireless communication device. The present invention provides an improved wireless communication device that can detect the presence of an external device and dynamically update its communication interface to facilitate communication with the external device.  
           [0008]    Upon detecting a connection from an external device, either by a direct physical link, direct wireless link, or remote wireless link, the wireless communication device obtains summary information about the external device. If a communication interface for the external device is not already present in the wireless communication device, the wireless device sends a portion of the external device&#39;s summary information to a remote interface server and requests the appropriate interface. Upon receipt of the interface, the wireless communication device installs the interface and then proceeds to establish communication with the external device. 
       
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0009]    The details of the present invention, both as to its structure and operation, may be gleaned in part by study of the accompanying drawings described below, in which like reference numerals refer to like parts.  
         [0010]    [0010]FIG. 1 is a high level block diagram illustrating an example wireless communication network.  
         [0011]    [0011]FIG. 2A is a block diagram illustrating an example direct physical connection between a wireless communication device and an external device.  
         [0012]    [0012]FIG. 2B is a block diagram illustrating an example direct wireless connection between a wireless communication device and an external device.  
         [0013]    [0013]FIG. 2C is a block diagram illustrating an example remote wireless connection between a wireless communication device and an external device.  
         [0014]    [0014]FIG. 3A is a block diagram illustrating an example representation of data in persistent storage on a wireless communication device.  
         [0015]    [0015]FIG. 3B is a block diagram illustrating components of an example wireless communication device.  
         [0016]    [0016]FIG. 3C is a block diagram illustrating an example operation code library and corresponding runtime instruction set.  
         [0017]    [0017]FIG. 3D is a block diagram illustrating an example set of runtime instructions.  
         [0018]    [0018]FIG. 4 is a flow diagram illustrating an example process for obtaining summary information from an external device.  
         [0019]    [0019]FIG. 5 is a flow diagram illustrating an example process for requesting interface software from a remote server.  
         [0020]    [0020]FIG. 6 is a flow diagram illustrating an example process for installing interface software.  
         [0021]    [0021]FIG. 7 is flow diagram illustrating an example process for initializing an external device.  
         [0022]    [0022]FIG. 8 is a block diagram illustrating an exemplary wireless communication device that may be used in connection with the various embodiments described herein.  
         [0023]    [0023]FIG. 9 is a block diagram illustrating an exemplary computer system as may be used in connection with various embodiments described herein. 
     
    
     DETAILED DESCRIPTION  
       [0024]    Certain embodiments as disclosed herein provide for a wireless communication device and method for dynamically recognizing and interfacing with an external device. For example, one method as disclosed herein allows for a wireless communication device to recognize the presence of an external device via a wired or wireless communication link. Upon recognition, the wireless communication device queries the external device to obtain summary profile information about the device. The wireless communication device then queries a server over a wireless communication network and receives a response comprising an interface to facilitate communication between the devices.  
         [0025]    After reading this description it will become apparent to one skilled in the art how to implement the invention in various alternative embodiments and alternative applications. However, although various embodiments of the present invention will be described herein, it is understood that these embodiments are presented by way of example only, and are not limitations. As such, this detailed description of various alternative embodiments should not be construed to limit the scope or breadth of the present invention as set forth in the appended claims.  
         [0026]    [0026]FIG. 1 is a high level block diagram illustrating an example wireless communication network  10 . The illustrated wireless communication network  10  comprises a plurality of wireless communication devices  20  and  30 , each with a corresponding external device  22  and  32 , respectively. The network wireless communication network  10  additionally comprises a plurality of base stations  40  and  42  that are coupled by an interface server  60  over a network  50 . The base stations  40  and  42  communicatively link the handsets  20  and  30  to the interface server  60 . The interface server  60  is also coupled with a data storage area  70 .  
         [0027]    In the illustrated embodiment, the connection between external device  22  and handset  20  is a direct physical connection  24 . External devices can also be coupled with handsets via a wireless link such as a direct wireless link  34  or a remote wireless link  36  between external device  32  and handset  30 . In one embodiment, the direct physical connection  24  can be a hardwired physical connection between the handset  20  and the external device  22 , for example a serial cable or a wired network connection. Alternatively, the direct wireless connection  34  can employ local networking protocol or bluetooth or infrared. External device  32  may also be connected to handset  30  through a remote wireless connection  36  that links the devices via a base station such as base station  42 . Additionally, external device  32  can also be connected to handset  30  through a remote wireless connection  36  that links the devices via a network such as the internet or network  50 .  
         [0028]    Wireless communication device  20  can be any sort of device with the ability to communicate within the wireless communication network  10 . For example, wireless communication device  20  may be a cell phone, a personal digital assistant (“PDA”), a laptop computer, wristwatch, or any other device configured for wireless communication. Wireless communication devices may also be referred to herein as “handsets” or “mobile phones” or “mobile devices”.  
         [0029]    Base station  40  is preferably configured to communicate over-the-air with a plurality of wireless communication devices and includes a transceiver (not shown) that converts the over-the-air communications to wired communications that travel over network  50 . Preferably, network  50  is a private network operated by a wireless carrier. Network  50  provides the infrastructure for handoffs between base stations such as base station  40  and  42 . Additionally, network  50  provides the communication link between various applications, services, and other computer based servers such as interface server  60 .  
         [0030]    Network  50  may also serve as the conduit for connections to other networks (not pictured) such as an Integrated Services Digital Network (“ISDN”), Public Switched Telephone Network (“PSTN”), Public Land Mobile Network (“PLMN”), Packet Switched Public Data Network (“PSPDN”), and the Internet, just to name a few.  
         [0031]    Interface server  60  can be implemented as a single computer or as a plurality of servers logically arranged to provide dynamic instruction sets to mobile devices and to execute dynamic instruction sets received from mobile devices. In the illustrated embodiment, interface server  60  is coupled with a data storage area  70  that preferably houses a plurality of executable interfaces and a set of server operation codes, handset operation codes and executable instructions corresponding to the server operation codes. The features of a general purpose computer that may implement the interface server  60  are later described with respect to FIG. 9. The function of the interface server  60  is preferably to receive requests from a handset and respond to those requests by providing the handset with an executable interface that the handset can use to communicate with the external device.  
         [0032]    [0032]FIG. 2A is a block diagram illustrating an example direct physical connection  84  between a wireless communication device  80  and an external device  82 . The direct physical connection  84  can be made through a standard or proprietary cable that connects to both the external device  82  and the handset  80 . Alternatively, the direct physical connection  84  may be achieved by a coupling of the handset  80  and the external device such that no actual cable is employed and the resulting coupled devices become an integral unit.  
         [0033]    [0033]FIG. 2B is a block diagram illustrating an example direct wireless connection  85  between a wireless communication device  86  and an external device  88 . The direct wireless connection  85  can be made through a variety of wireless links such as bluetooth, infrared, or the 802.11 and 802.15 families of wireless communication.  
         [0034]    [0034]FIG. 2C is a block diagram illustrating an example remote wireless connection between a wireless communication device  90  and an external device  98 . The remote wireless connection may comprise a link  96  between the external device  98  and a base station  94  and also a link  92  between the handset  90  and the base station  94 . There may also be interstitial networks and base stations (not shown). The remote wireless connection may be established using conventional wireless communication protocols or remote wireless networking protocols such as the 802.11 and 802.15 families of wireless communication.  
         [0035]    [0035]FIG. 3A is a block diagram illustrating an example representation of data in persistent storage  240  on a wireless communication device  20 ,  30 . The general features of wireless communication device  20 ,  30  that allow it to function as such are later described with respect to FIG. 8. In the illustrated embodiment, the operating system  100  is resident in persistent storage  240 . The operating system  100  preferably comprises the fundamental executable program or programs that allow the device to function. In addition to the operating system  100 , application data  110  and user interface  120  are in persistent storage  240 . The application data  110  preferably comprises the user information and application information that an application needs to function or that an application uses to provide its service.  
         [0036]    The user interface  120  may comprise both the executable user interface application and the user interface data that is used by the application. In an alternative embodiment, the user interface application portion may be included as part of the operating system and the user interface  120  may comprise ancillary user data or custom data or other data usable by the user interface application or the user. The persistent storage area  240  additionally comprises one or more device drivers such as device driver  130 , device driver  132 , all the way up to device driver n. These device drivers are preferably executable applications that facilitate communication between the handset and another device, or possibly between the core handset and an integral device such as the display, keypad, speaker, microphone, or earphones, just to name a few.  
         [0037]    Additionally shown as part of the persistent storage  240  are a series of software applications or modules such as applications  140 ,  142 ,  144 ,  146 , and on up to application n. As illustrated, a large number of applications may be resident as part of the persistent storage  240 . The only limit on the number of applications that can be stored in persistent storage  240  is the physical limit of the storage  240 .  
         [0038]    [0038]FIG. 3B is a block diagram illustrating components of data  240  of an example wireless communication device  20 ,  30 . In the illustrated embodiment, the data  240  has a number of applications  242  comprising an external device detector  200  and a runtime engine  230 . Other data elements  244 , which may be included in the application data  110  as illustrated in FIG. 3A, comprise a server operation code (“opcode”) library  210 , handset opcode library  220 , and runtime instructions  260 .  
         [0039]    The external device detector  200  is preferably configured to determine when an external device has been physically connected to the handset  20 ,  30 , or when an external device is attempting a connection to the handset  20 ,  30  via a wireless link. Additionally, the external device detector  200  is preferably capable of detecting pilot signals or other broadcast wireless signals to determine if an external device is within proximity of the handset such than a connection can be made. The external device detector  200  can be implemented as a combination of electromechanical and software components to carry out the detection function.  
         [0040]    Continuing with FIG. 3B, the handset opcode library  220  preferably includes the universe of operation codes that represent each function or executable code segment that the handset can be instructed to execute by the interface server  60 , illustrated in FIG. 1. Advantageously, handset opcode library  220  includes the operation codes that serve as place holders for the actual executable machine code functions or code segments. As such, the handset opcode library  220  preferably contains a list of all available operation codes that correspond to each and every function that can be executed by the handset  20 ,  30 .  
         [0041]    Similarly, the server opcode library  210  preferably includes the universe of operation codes that represent each server side function or executable code segment. Advantageously, server opcode library  210  may only include the operation codes for the actual executable machine code functions or code segments, which do not reside on the wireless communication device  20 . As such, the server opcode library  220  contains a list of all the operation codes for each available server function that can be executed by the interface server  60  on behalf of the handset  20 ,  30 . In the preferred embodiment, the number of available server functions can well exceed the number of available handset functions because the interface server  60  does not suffer from the minimal resources typically found on mobile devices such as, for example, cell phones and PDAs.  
         [0042]    Runtime engine  230  is preferably configured to process dynamic instructions sets. One example of a dynamic instruction set is a set of instructions to install a communication interface. The processing of dynamic instruction sets includes translation of opcodes into executable instruction sets and execution of those instruction sets. For example, a set of handset opcodes may be received from the interface server  60 . The processing of dynamic instruction sets also includes compilation of opcodes and corresponding data for delivery to the interface server  60 . Preferably, runtime engine  230  can be launched by wireless communication device  20 ,  30  on an as needed basis so that it runs only when necessary and consumes a minimal amount of system resources (e.g. memory, CPU cycles, etc.) on the handset  20 ,  30 .  
         [0043]    [0043]FIG. 3C is a block diagram illustrating an example handset operation code library  220  and corresponding runtime instruction set  260 . The handset opcode library  220  and runtime instruction set  260  are preferably housed in the data storage area  240  of the handset  20 ,  30 . In one embodiment, the executable instructions in the runtime instruction set  260  correspond in a one-to-one relationship with the opcodes contained in the handset opcode library  220 . Alternatively, a single opcode in the handset opcode library  220  may correspond to a sequence of instructions in the runtime instructions  260 .  
         [0044]    [0044]FIG. 3D is a block diagram illustrating an example set of runtime instructions  260 . In the illustrated embodiment, any number of executable instructions can be included in runtime instructions  260 , from instruction  1  through instruction n. Optimally, a large number of functions are available in runtime instructions  260  and yet consume very little resources (e.g. persistent memory) of the handset  20 ,  30 .  
         [0045]    [0045]FIG. 4 is a flow diagram illustrating an example process for obtaining summary information from an external device. Initially, in step  300 , the handset detects a connection from an external device. The connection can be detected over a wired or wireless link. Upon detecting a connection, the handset determines if the connection was initiated by a user, as shown in step  302 . For example, the user may press a sequence of keys or issue spoken commands to instruct the handset that a new device is connected. In one embodiment, if the connection is user initiated, summary device information is provided to the handset directly from the user. In such an embodiment, the handset next stores the summary device information in step  304 .  
         [0046]    Alternatively, if the detection was not user initiated, then the handset next formulates a query for the external device, as illustrated in step  306 . The query can advantageously conform to a standard protocol or it may be a proprietary protocol. Once the query is formulated, the handset sends the query to the external device in step  308 . In step  310 , the handset determines if a valid response was received from the external device. If there was no response or the response was invalid, the handset can return to step  306  and reformulate the query and proceed to query the external device again. Advantageously, the handset may cycle through a variety of known query formats and protocols until a valid response is received. Once a valid response is received that preferably includes summary profile information about the external device, the handset stores the summary profile information, as shown in step  304 .  
         [0047]    [0047]FIG. 5 is a flow diagram illustrating an example process for requesting interface software from a remote server. Initially, in step  320  the runtime engine is launched. Once the runtime engine is running, the engine can compile a set of server opcodes, as shown in step  322 . The set of server opcodes may be obtained from a background process running on the wireless device. Alternatively, the server opcode set may be obtained from a process running on the wireless device under the direction of a user. The compiled set of server opcodes preferably causes the server to reply with an executable interface for the particular external device that is connected to the handset.  
         [0048]    For example, the wireless device detects a connection from an external device. The external device is queried and summary profile information is obtained. A server opcode set is compiled instructing the server to provide the handset with an executable interface for the external device so that the handset may communicate with the external device. In such as case, the result is a server opcode set generated by the runtime engine, as shown in step  322 .  
         [0049]    Once the server opcode set has been generated, the runtime engine includes the summary information for the external device in the data payload that corresponds to the server opcode set. For example, the runtime engine may fetch the summary profile data from persistent or volatile memory, or execute an instruction that returns the data needed. Once the data has been obtained, the run time engine next inserts the data into the server opcode set, as illustrated in step  324 . One simple way to achieve this is to append the data payload to the server opcode set in a single data packet.  
         [0050]    Once the data payload has been combined with the server opcode set, then the runtime engine sends the server opcode set with the corresponding data payload to the server, as shown in step  326 . After the server opcode set and data payload has been sent, the runtime engine may be terminated to free up resources on the wireless device, as illustrated in step  328 .  
         [0051]    [0051]FIG. 6 is a flow diagram illustrating an example process for installing interface software on a wireless communication device. Initially, in step  330 , the wireless device receives a set of handset opcodes. The set of handset opcodes can be received via an over-the-air communication link, for example a link with a wireless communication network. Preferably, the opcodes are optimized to minimize the amount of data sent over-the-air. Additionally, a data payload can be included with the set of opcodes received by the handset.  
         [0052]    In step  332 , the wireless device launches its runtime engine to process the handset opcode set. As illustrated in step  334 , the runtime engine parses the handset opcode set and then extracts the data payload in step  336 . If no data payload exists, then this step can be skipped. If a data payload does exist, then the resulting data can be stored in an available portion of volatile memory for later use. Next, the runtime engine obtains the executable instructions that correspond to the opcodes in the handset opcode set as shown in step  338 . These instructions can be obtained from the remote runtime instructions set stored in persistent storage on the data storage area of the handset.  
         [0053]    Once the executable instructions corresponding to the opcodes in the handset opcode set have been obtained, the runtime engine executes the instructions, as illustrated in step  340 . When the instructions are being executed, any necessary data to be operated on can be obtained from volatile memory where the data payload is stored. Alternatively, or additionally, any necessary data to be operated on may be obtained as the result of an executed instruction.  
         [0054]    For example, the data payload may comprise the interface needed by the handset to communicate with the external device. Additionally, one or more of the opcodes in the handset opcode set preferably correspond to one or more executable instructions for storing the data payload in persistent memory on the handset. In this example, once the data payload comprising the interface is stored in persistent memory, the handset may thereafter communicate with the device using the executable interface. Alternatively, the data payload may replace a portion of persistent memory that contains an outdated interface for the particular external device. Thus, the handset opcode set and data payload operate on the wireless device to install a new interface for the external device. Additional opcodes and instructions may also be employed to configure the new interface once it has been installed, if necessary.  
         [0055]    Once the instruction set has been executed in its entirety by the runtime engine, the runtime engine can be terminated, as shown in step  342 . Advantageously, the runtime engine may be launched and terminated so that it only runs when necessary. This saves system resources on the wireless device, for example it may save volatile memory space and CPU cycles. Once the interface for the external device has been installed and configured for use, the handset may begin communicating with the external device, as illustrated in step  346 .  
         [0056]    [0056]FIG. 7 is flow diagram illustrating an example process for initializing an external device. Initially, in step  350 , the handset uses the new interface to send a setup request to the external device. Next, in step  352 , the handset receives a response from the external device. In one embodiment the response may comprise more comprehensive profile information about the device. For example, the response may provide the handset with additional information relating to the communication interface such as the interface version or other information to make communication between the devices more efficient.  
         [0057]    Alternatively, the response may be an indication of an unsuccessful attempt to initialize the external device, as determined in step  354 . If the setup request received a response indicating that the setup was unsuccessful, the handset returns to step  350  and sends another setup request. In one embodiment, the handset may cycle through various setup requests until a request that is formatted correctly is provided to the external device. For example, the various setup requests may conform to different versions of the interface. Accordingly, the particular setup request that receives a successful response may advantageously provide the handset with important information about the version of the firmware that is installed on the external device, the capabilities of the external device, and other information about to the external device. Once a successful response is received from the external device, as determined in step  354 , the handset may proceed to exchange information with the external device as shown in step  356 .  
         [0058]    [0058]FIG. 8 is a block diagram illustrating an exemplary wireless communication device  450  that may be used in connection with the various embodiments described herein. For example, the wireless communication device  450  may be used in conjunction with a handset or PDA network device or as a part of a sensor node in a wireless mesh network. However, other wireless communication devices and/or architectures may also be used, as will be clear to those skilled in the art.  
         [0059]    In the illustrated embodiment, wireless communication device  450  comprises an antenna  452 , a multiplexor  454 , a low noise amplifier (“LNA”)  456 , a power amplifier (“PA”)  458 , a modulation circuit  460 , a baseband processor  462 , a speaker  464 , a microphone  466 , a central processing unit (“CPU”)  468 , a data storage area  470 , and a hardware interface  472 . In the wireless communication device  450 , radio frequency (“RF”) signals are transmitted and received by antenna  452 . Multiplexor  454  acts as a switch, coupling antenna  452  between the transmit and receive signal paths. In the receive path, received RF signals are coupled from a multiplexor  454  to LNA  456 . LNA  456  amplifies the received RF signal and couples the amplified signal to a demodulation portion of the modulation circuit  460 .  
         [0060]    Typically modulation circuit  460  will combine a demodulator and modulator in one integrated circuit (“IC”). The demodulator and modulator can also be separate components. The demodulator strips away the RF carrier signal leaving a base-band receive audio signal, which is sent from the demodulator output to the base-band processor  462 .  
         [0061]    If the base-band receive audio signal contains audio information, then base-band processor  462  decodes the signal and converts it to an analog signal. Then the signal is amplified and sent to the speaker  464 . The base-band processor  462  also receives analog audio signals from the microphone  466 . These analog audio signals are converted to digital signals and encoded by the base-band processor  462 . The base-band processor  462  also codes the digital signals for transmission and generates a base-band transmit audio signal that is routed to the modulator portion of modulation circuit  460 . The modulator mixes the base-band transmit audio signal with an RF carrier signal generating an RF transmit signal that is routed to the power amplifier  458 . The power amplifier  458  amplifies the RF transmit signal and routes it to the multiplexor  454  where the signal is switched to the antenna port for transmission by antenna  452 .  
         [0062]    The baseband processor  462  is also communicatively coupled with the central processing unit  468 . The central processing unit  468  has access to a data storage area  470 . The central processing unit  468  is preferably configured to execute instructions (i.e., computer programs or software) that can be stored in the data storage area  470 . Computer programs can also be received from the baseband processor  462  and stored in the data storage area  470  or executed upon receipt. Such computer programs, when executed, enable the wireless communication device  450  to perform the various functions of the present invention as previously described.  
         [0063]    In this description, the term “computer readable medium” is used to refer to any media used to provide executable instructions (e.g., software and computer programs) to the wireless communication device  450  for execution by the central processing unit  468 . Examples of these media include the data storage area  470 , microphone  466  (via the baseband processor  462 ), antenna  452  (also via the baseband processor  462 ), and hardware interface  472 . These computer readable mediums are means for providing executable code, programming instructions, and software to the wireless communication device  450 . The executable code, programming instructions, and software, when executed by the central processing unit  468 , preferably cause the central processing unit  468  to perform the inventive features and functions previously described herein.  
         [0064]    The central processing unit is also preferably configured to receive notifications from the hardware interface  472  when new devices are detected by the hardware interface. Hardware interface  472  can be a combination electromechanical detector with controlling software that communicates with the CPU  468  and interacts with new devices.  
         [0065]    [0065]FIG. 9 is a block diagram illustrating an exemplary computer system  550  that may be used in connection with the various embodiments described herein. For example, the computer system  550  may be used in conjunction with a remote server configured to process server opcode sets and create and send handset opcode sets. However, other computer systems and/or architectures may be used, as will be clear to those skilled in the art.  
         [0066]    The computer system  550  preferably includes one or more processors, such as processor  552 . Additional processors may be provided, such as an auxiliary processor to manage input/output, an auxiliary processor to perform floating point mathematical operations, a special-purpose microprocessor having an architecture suitable for fast execution of signal processing algorithms (e.g., digital signal processor), a slave processor subordinate to the main processing system (e.g., back-end processor), an additional microprocessor or controller for dual or multiple processor systems, or a coprocessor. Such auxiliary processors may be discrete processors or may be integrated with the processor  552 .  
         [0067]    The processor  552  is preferably connected to a communication bus  554 . The communication bus  554  may include a data channel for facilitating information transfer between storage and other peripheral components of the computer system  550 . The communication bus  554  further may provide a set of signals used for communication with the processor  552 , including a data bus, address bus, and control bus (not shown). The communication bus  554  may comprise any standard or non-standard bus architecture such as, for example, bus architectures compliant with industry standard architecture (“ISA”), extended industry standard architecture (“EISA”), Micro Channel Architecture (“MCA”), peripheral component interconnect (“PCI”) local bus, or standards promulgated by the Institute of Electrical and Electronics Engineers (“IEEE”) including IEEE 488 general-purpose interface bus (“GPIB”), IEEE 696/S-100, and the like.  
         [0068]    Computer system  550  preferably includes a main memory  556  and may also include a secondary memory  558 . The main memory  556  provides storage of instructions and data for programs executing on the processor  552 . The main memory  556  is typically semiconductor-based memory such as dynamic random access memory (“DRAM”) and/or static random access memory (“SRAM”). Other semiconductor-based memory types include, for example, synchronous dynamic random access memory (“SDRAM”), Rambus dynamic random access memory (“RDRAM”), ferroelectric random access memory (“FRAM”), and the like, including read only memory (“ROM”).  
         [0069]    The secondary memory  558  may optionally include a hard disk drive  560  and/or a removable storage drive  562 , for example a floppy disk drive, a magnetic tape drive, a compact disc (“CD”) drive, a digital versatile disc (“DVD”) drive, etc. The removable storage drive  562  reads from and/or writes to a removable storage medium  564  in a well-known manner. Removable storage medium  564  may be, for example, a floppy disk, magnetic tape, CD, DVD, etc.  
         [0070]    The removable storage medium  564  is preferably a computer readable medium having stored thereon computer executable code (i.e., software) and/or data. The computer software or data stored on the removable storage medium  564  is read into the computer system  550  as electrical communication signals  578 .  
         [0071]    In alternative embodiments, secondary memory  558  may include other similar means for allowing computer programs or other data or instructions to be loaded into the computer system  550 . Such means may include, for example, an external storage medium  572  and an interface  570 . Examples of external storage medium  572  may include an external hard disk drive or an external optical drive, or and external magneto-optical drive.  
         [0072]    Other examples of secondary memory  558  may include semiconductor-based memory such as programmable read-only memory (“PROM”), erasable programmable read-only memory (“EPROM”), electrically erasable read-only memory (“EEPROM”), or flash memory (block oriented memory similar to EEPROM). Also included are any other removable storage units  572  and interfaces  570 , which allow software and data to be transferred from the removable storage unit  572  to the computer system  550 .  
         [0073]    Computer system  550  may also include a communication interface  574 . The communication interface  574  allows software and data to be transferred between computer system  550  and external devices (e.g. printers), networks, or information sources. For example, computer software or executable code may be transferred to computer system  550  from a network server via communication interface  574 . Examples of communication interface  574  include a modem, a network interface card (“NIC”), a communications port, a PCMCIA slot and card, an infrared interface, and an IEEE 1394 fire-wire, just to name a few.  
         [0074]    Communication interface  574  preferably implements industry promulgated protocol standards, such as Ethernet IEEE 802 standards, Fiber Channel, digital subscriber line (“DSL”), asynchronous digital subscriber line (“ADSL”), frame relay, asynchronous transfer mode (“ATM”), integrated digital services network (“ISDN”), personal communications services (“PCS”), transmission control protocol/Internet protocol (“TCP/IP”), serial line Internet protocol/point to point protocol (“SLIP/PPP”), and so on, but may also implement customized or non-standard interface protocols as well.  
         [0075]    Software and data transferred via communication interface  574  are generally in the form of electrical communication signals  578 . These signals  578  are preferably provided to communication interface  574  via a communication channel  576 . Communication channel  576  carries signals  578  and can be implemented using a variety of communication means including wire or cable, fiber optics, conventional phone line, cellular phone link, radio frequency (RF) link, or infrared link, just to name a few.  
         [0076]    Computer executable code (i.e., computer programs or software) is stored in the main memory  556  and/or the secondary memory  558 . Computer programs can also be received via communication interface  574  and stored in the main memory  556  and/or the secondary memory  558 . Such computer programs, when executed, enable the computer system  550  to perform the various functions of the present invention as previously described.  
         [0077]    In this description, the term “computer readable medium” is used to refer to any media used to provide computer executable code (e.g., software and computer programs) to the computer system  550 . Examples of these media include main memory  556 , secondary memory  558  (including hard disk drive  560 , removable storage medium  564 , and external storage medium  572 ), and any peripheral device communicatively coupled with communication interface  574  (including a network information server or other network device). These computer readable mediums are means for providing executable code, programming instructions, and software to the computer system  550 .  
         [0078]    In an embodiment that is implemented using software, the software may be stored on a computer readable medium and loaded into computer system  550  by way of removable storage drive  562 , interface  570 , or communication interface  574 . In such an embodiment, the software is loaded into the computer system  550  in the form of electrical communication signals  578 . The software, when executed by the processor  552 , preferably causes the processor  552  to perform the inventive features and functions previously described herein.  
         [0079]    Various embodiments may also be implemented primarily in hardware using, for example, components such as application specific integrated circuits (“ASICs”), or field programmable gate arrays (“FPGAs”). Implementation of a hardware state machine capable of performing the functions described herein will also be apparent to those skilled in the relevant art. Various embodiments may also be implemented using a combination of both hardware and software.  
         [0080]    While the particular dynamic interface software for wireless communication devices herein shown and described in detail is fully capable of attaining the above described objects of this invention, it is to be understood that the description and drawings presented herein represent a presently preferred embodiment of the invention and are therefore representative of the subject matter which is broadly contemplated by the present invention. It is further understood that the scope of the present invention fully encompasses other embodiments that may become obvious to those skilled in the art and that the scope of the present invention is accordingly limited by nothing other than the appended claims.