HK1073035B - Dynamic loading and creation of functional objects in a wireless device - Google Patents

Description

Dynamic loading and creation of functional objects in a wireless device

Reference to related applications

This application claims priority to U.S. provisional patent application serial No. 60/292051, filed on month 5 and 18 of 2001, and is incorporated herein by reference in its entirety.

Background

I. Field of the invention

The present invention relates to handheld wireless communication devices, and more particularly, to wireless communication devices having preloaded static objects and user-installed dynamic objects. The apparatus includes various initiators that require execution of an object by submitting a unique object-ID to an object manager, whereupon the object manager identifies the requested object, its entry point, and object class, and then activates the requested object.

Description of the related Art

Wireless telephones are becoming increasingly popular today. As the demand for wireless services increases, manufacturers respond to this to meet the demand and provide wireless telephones with ever smaller sizes and ever improving functionality. The long term functions of the radiotelephone include user operated menus for setting ring volume/tone, using vibration patterns, saving telephone numbers in memory, etc. Moreover, many wireless telephones include internal programs to perform computing tasks such as voice recognition, video games, diagnostics, network communications, and the like.

In addition to these internal functions, engineers from QUALCOMM corporation have anticipated that next generation wireless phones will enable users to download new programs themselves from remote servers over wireless links and install those programs themselves on local phones. One challenge in this field is to have a phone circuit that is small, economical and powerful enough to enable its subcomponents to launch static applications (internal to the phone), as well as dynamic applications that are downloaded by the user.

Summary of The Invention

Broadly, the present invention relates to a wireless communication device that is preloaded with various static objects and wirelessly downloads and installs certain dynamic objects as directed by a user. The apparatus includes various initiators that require execution of an object by submitting a unique object-ID to an object manager, which then identifies the requested object, its entry point, and object class, and activates the requested object accordingly.

More specifically, the apparatus includes a telephone module having a plurality of static objects mounted within circuitry of the telephone module. Each static Object is associated with a unique Object ID (Object-ID). Each static object has an entry point that is a preferred address or other starting point for activating the object. The phone module includes a static object table that relates the object ID, entry point, and entry category of each static object. The object category specifies whether the object is a program, a file to be opened, a web service to be activated, a menu to be displayed, or the like.

The phone module includes a plurality of object enablers, such as a user interface, one or more drivers, and a main controller, as many more are needed. The phone module also includes an object manager for managing static and dynamic objects. According to one function, the object manager downloads one or more dynamic objects over a wireless link at the direction of a user. The object manager assigns a unique object ID to each dynamic object and also provides for dynamic object handlers that determine the entry point and object class of each dynamic object as needed in the future. According to another function, the object manager supervises the activation of static and dynamic objects. Initially, the object manager receives a request from an object initiator to activate an object. Each request includes an object ID that uniquely identifies the requested object. In response to each request, the object manager references an object ID against at least one of the dynamic object handler and the static object table to identify the entry point of the requested object and its object class. The object manager then activates the requested object in a manner appropriate to the entry point and object type identified.

The object manager may be operative to consult the dynamic object handler before consulting the static object table so that the dynamic program associated with the object ID is found before (among other things) any static programs. This enables the user to download dynamic objects to effectively replace static objects even though the static objects are still built into the circuitry of the phone module.

The above-described features may be implemented in many different forms. For example, the present invention may be implemented to provide a method to manage static and dynamic objects in a wireless communication device. In another embodiment, the invention may be implemented to provide an apparatus, such as a wireless communication apparatus or a radiotelephone module therein. In yet another embodiment, the invention is implemented to provide a signal-bearing medium tangibly embodying a program of machine-readable instructions executable by a digital data processing apparatus to manage static and dynamic objects within a wireless communications apparatus. Another embodiment relates to a logic circuit having a plurality of interconnected conductive elements for managing static and dynamic objects within a wireless communication device.

The present invention provides a number of unique advantages to the user. In short, since the present invention applies similar processing to static (built-in) objects and dynamic (user-downloaded) objects, the static and dynamic objects can be processed and activated with the same mechanism, thus reducing circuit complexity. Furthermore, by comparing the requested user ID to the installed dynamic objects and then to the static objects only if they do not match the dynamic objects, the present invention allows the user to download dynamic objects to effectively replace static objects with the same object ID. The invention is also advantageous in that the object ID can be flexibly associated with a plurality of different objects, such as: a program to be run, a file to be opened, a network association to be made, a menu to be displayed, or a variety of other actions to be taken. The present invention also provides a number of other advantages and benefits, as will become apparent from the following description.

Brief Description of Drawings

Fig. 1A is a block diagram of a wireless communication device according to the present invention.

Fig. 1B is a block diagram of the hardware components and interconnections of a radiotelephone module according to the invention.

Fig. 2 is a block diagram of a digital data processing apparatus according to the present invention.

Fig. 3 illustrates an exemplary signal-bearing medium according to the present invention.

FIG. 4 is a flow diagram of a sequence of operations for managing static and dynamic objects in accordance with the present invention.

FIG. 5 is a flow diagram of a sequence of operations for releasing an activated object in accordance with the present invention.

Detailed Description

The features, nature, and advantages of the present invention will become more apparent from the detailed description set forth below when taken in conjunction with the drawings.

Hardware component and interconnect

Wireless communication device

One aspect of the present invention relates to a wireless communication device that may be embodied with various hardware components and interconnections, one example of which is described with reference to handset 150 of fig. 1A. The handset 150 includes a speaker 152, a microphone 154, a keypad 159, a display 166, an antenna 156, and handset circuitry 158. The handset circuitry 158 includes portions 160, 164. Portion 160 is used to conduct two-way wireless communications between a remote party and a user via transceiver 162 in accordance with speaker 152 and microphone 154. For example, portion 160 may have various commercially available conventional circuitry for wireless telephones.

Portion 164 is referred to as a "wireless telephone module" and includes static and dynamic modules that can be selectively activated to perform various tasks. The wireless telephony module 164 includes an object manager that responds to requests from various initiators to activate static and/or dynamic objects. That is, the initiator submits a unique object ID to the object manager, which then identifies the requested object, its entry point, and object class, and then appropriately activates the requested object.

Wireless telephone module

Fig. 1B illustrates the radiotelephone module 164 in more detail. As described in detail below, a module may have logic circuits, one or more instruction execution processors, or a combination thereof. In an exemplary embodiment, the module 164 includes a flash image 102, a host controller 120, and a Random Access Memory (RAM) 104. The illustrated host controller 120 includes an Application Specific Integrated Circuit (ASIC).

Considering the module 164 more specifically, and without any limitation, the image 102 comprises a static image fixed in flash memory. The image 102 includes a plurality of static objects 106, various dynamic objects 110, an object manager 114, a user interface 116, and various drivers 118. Static object 106 comprises a program ("function object") that is fixed within the circuitry of module 164 and is not changed or deleted by the user of the telephone handset. In other words, the static object 106 is built into the device 150 and is available when the device 150 is first powered up. Each static object 106 includes an action of one of several predefined "object classes," which define an action type, such as: (1) performing a calculation, (2) opening a file, (3) activating a web service, such as opening a suite, (4) displaying a menu, (5) performing a calculation, or (6) taking other actions, as will be apparent to those of ordinary skill in the art having the benefit of this disclosure, although not specifically described. Each static object is associated with a unique object ID, which in the exemplary embodiment comprises a 32-bit binary number. Each static object also has an "entry point," which comprises a predefined point within the program order of the static object, for launching the static object. For example, the entry point may include a memory address within the image 102.

The static object table 108 is associated with the static objects 106. The table 108 lists the object ID and entry point for each static object 106. Table 1 below shows an example of the static object table 108. Although table 108 is illustrated and referenced without limitation, one of ordinary skill will recognize that table 108 may also be implemented with a linked list or other useful data structure.

TABLE 1

Object ID	Object classes	Entry point
			1111 1111 1111 11111111 1111 1111 1111	MeterCalculation program	Address 09A7
1111 1010 1101 00011111 1010 1011 1000	Opening a file	Address A395
			1001 1101 0111 11011000 1001 0110 1011	Opening a network device	Address F373
1111 1111 1111 11111111 1111 1111 1111	Display menu	Address 882B
			... (more)	... (more)	... (more)

The static object table 108 has the modules 164 fabricated thereon.

Like the static object 106, the dynamic object 110 also includes program sequences. However, dynamic objects 110 are not fixed within the circuitry of module 164, but are added and deleted by the cell phone user, discussed in detail below. As with the static objects, each dynamic object includes an action that belongs to one of the predetermined object classes, each dynamic object is associated with a unique object ID, and each static object has an entry point that includes a predefined point within the program sequence of the static object for launching the static object.

The dynamic object handler 112 is associated with the dynamic object 108. The processor 112 includes a mechanism to find an entry point and an object class for the requested dynamic object based on the object ID of the dynamic object. In one embodiment, the structure of the processor 112 may be one of the various forms described above (e.g., table, linked list, etc.) in connection with the static object table 108.

The image 102 also includes a plurality of object initiators. The initiator includes different entities of the module 164 that may need to access the static and dynamic objects 106, 110 to perform tasks. The initiator includes a user interface 116, one or more drives 118, a master controller 120, and any required components. Further, there may be one or more remote actuators that are not located within the module 164 or the device 150. For example, the remote initiator may communicate wirelessly with the device 150 via a network connection, the internet, a telephone connection, or other link.

The user interface 116 includes a software program that manages the exchange of data between the input devices operated by the user of the handset and the components of the module 164, including the object manager 114, the master controller 120, etc. For example, the user interface 116 may manage the use and appearance of menus presented on the display 116. Depending on the functionality of the device 150, the driver 118 comprises a software program that interacts with the specific device or software of the handset 150 and contains some specific knowledge about whether the device or software interface uses the driver. The main controller 120 comprises the highest processing entity that controls all operations of the telephone handset 150. In one embodiment, host controller 120 includes an ASIC.

As described above, image 102 also includes object manager 114. The manager 114 comprises a processing entity (e.g., logic or executable program) for managing the activation of the static and dynamic objects 106, 110. In addition, object manager 114 manages user-initiated downloads and deletions of dynamic objects 110. Also, as described in detail below, the object manager 114 creates and/or updates the static object table 108 and the dynamic object handler 112.

Another component of module 164 is RAM 104. The object manager 114 uses the RAM 104 when the static and dynamic objects 106, 110 are activated, i.e., by loading the objects 106, 110 into the RAM 104.

Exemplary digital data processing apparatus

As described above, the objects 106, 110, the user interface 116, the driver 118, the object manager 114, and the main controller 120 may be implemented in various forms in consideration of size, cost, and the like. Depending on the application, none, some, or all of these features may be implemented with one or more digital data processing apparatus, as exemplified by the hardware components and interconnections of digital data processing apparatus 200 of FIG. 2.

The apparatus 200 includes a processor 202, such as a microprocessor or other processor, coupled to a memory 204. In this example, the memory 204 includes fast access memory 206 and non-volatile memory 208. The fast access memory 206 may include RAM and may be used to store programming instructions that are executed by the processor 202. For example, the non-volatile memory 208 may include one or more data storage disks, such as a "hard disk," a tape drive, or any other suitable storage device. The device 200 also includes an input/output 210, such as a line, bus, cable, electromagnetic link, or any device that enables the processor 202 to exchange data with other hardware external to the device 200.

While the above description is specific, those of ordinary skill in the art, having benefit of the present disclosure, will appreciate that the above described apparatus may be implemented in a machine of different construction without departing from the scope of the present invention. For particular example, one of the components 206, 208 may be eliminated; moreover, the memory 204 may be provided on the processor 202, or even provided external to the apparatus 200.

Logic circuit

In contrast to the digital data processing apparatus described above, various embodiments of the present invention implement one or more of the items 106, 110, 114, 116, 118, 120 using logic circuitry rather than computer-executed instructions. Depending on the particular requirements of the application in the areas of speed, expense, tooling costs, etc., the logic may be implemented by an application specific integrated circuit ("ASIC") constructed with thousands of tiny integrated transistors. Such an ASIC may be implemented in CMOS, TTL, VLSI, or other suitable structures. Other alternatives include digital signal processing chips ("DSPs"), discrete circuits ("such as resistors, capacitors, diodes, inductors, and transistors"), field programmable gate arrays ("FPGAs"), programmable logic arrays ("PLAs"), and so forth.

Operation of

Having described the structural features of the present invention, the operational aspects of the present invention will now be described. As described above, the operational aspects of the present invention generally include an apparatus for executing a dynamic object having a preloaded static object and a user-installed dynamic object, wherein in response to each initiator requesting execution of the object by submitting a unique object ID to an object manager, the object manager identifies the requested object, its entry point, and object class, and then activates the requested object. While the present invention is broadly applicable to a variety of computing devices, the described features are most applicable to handheld wireless communication devices and the following description will emphasize, without limitation, such application of the invention.

Signal-bearing medium

In one embodiment, one or more of the components 106, 110, 114, 116, 118, 120 comprise a sequence of machine-executed programs, which may be embodied in various forms of signal-bearing media. In the context of fig. 2, the signal-bearing medium may comprise, for example: memory 204 or another signal-bearing medium, such as a data storage diskette 300 (FIG. 3), directly or indirectly accessible by the processor 202. Whether contained in the memory 206, diskette 300, or elsewhere, the instructions may be stored on a variety of machine-readable data storage media. Some examples include direct access storage (e.g., a conventional "hard disk," a redundant array of inexpensive disks ("RAID"), or another direct access storage device ("DASD")), serial access storage such as magnetic or optical tape, electrical read-only memory (e.g., ROM, EPROM, or EEPROM), optical storage (e.g., CD-ROM, WORM, DVD, digital optical tape), paper "punch" cards, or other suitable signal-bearing media including analog or digital transmission media and analog and wireless communication links. In an illustrative embodiment of the present invention, the machine-readable instructions may comprise software object code compiled from a "C" language or the like.

Logic circuit

In contrast to the signal-bearing media discussed above, operational aspects of the present invention may be implemented using logic circuitry in addition to or instead of processor-executed instructions. In this embodiment, logic is implemented within one or more of the items 106, 110, 114, 116, 118, 120. As mentioned above, the logic circuit may be implemented with many different types of circuits.

Total sequence of operation

FIG. 4 illustrates a sequence 400 for managing static and dynamic objects according to an exemplary embodiment of the invention. For simplicity of illustration, and without any limitation, the example of FIG. 4 is described in the context of the components described above in FIGS. 1A-1B, 2, and 3.

Sequence 400 begins at step 402, for example, when a user (not shown) powers on device 150. In step 404, the object manager 114 performs various initialization operations to allow for future use of the static and dynamic objects 106, 110. For example, the object manager 114 constructs the static object table 108 to reflect the characteristics of the static object 106, as shown in Table 1 above. Also in step 404, the object manager 114 takes appropriate action to construct, format, generate or initialize the dynamic object handler 112 according to the data structures used to implement the handler 112. For example, the object manager 114 may investigate the dynamic objects 110 and then populate the processors 112 with the object ID, object class, and entry point of the installed dynamic objects 110.

After step 404, the object manager 114 processes any user requests to download and install dynamic objects. For example, the master controller 120 may activate the transceiver 162 to download the requested dynamic object from a remote server according to user instructions entered via the keypad 159 of the device 150. The object manager 114 installs the downloaded object by storing it within the image 102 and also updates the dynamic object handler 112 to identify the newly downloaded dynamic object. The updating of the dynamic object handler 112 includes assigning a unique object ID and identifying the class and entry point of the object. Object manager 114 may also be invoked to uninstall one or more dynamic objects 110, for example, via a keypad or other user-initiated command.

In step 408, the object manager 114 determines whether any object initiator has submitted a request to activate one of the static or dynamic objects 106 or 110. Preferably, each such request includes only the object IDs of the three requested objects. Moreover, the initiator does not need to know whether the requested object is static 106 or dynamic 110. When an activation request is received, step 408 proceeds to step 410, where the object manager 114 determines whether the requested object corresponds to any of the static objects 106 or the dynamic objects 110. That is, the object manager 114 consults the processor 112 and the static object table 108 to determine whether the requested object ID is found therein. In one example, the object manager 114 (step 410) first consults the processor 112 and then consults the table 108 only if the processor 112 does not list the requested object. This arrangement is advantageous because it facilitates updating of static objects by users downloading dynamic objects having the same object ID — effectively ignoring outdated static objects 108 because the processor 112 is consulted first and then the table 108 is consulted.

Following step 410, step 412 determines whether the requested object ID is found in the processor 112 or the table 108. If not, object manager 114 issues an error message 414 to host controller 120, display 166, or other destination. If the requested object ID is found by processor 122, object manager 414 takes appropriate action to determine the entry point and object class of the requested object (step 418). If the processor is implemented with a program, step 418 runs the processor 112 program by loading the program into RAM 104. Then in step 416, object manager 144 uses the processor 112 program (which is running) to find the entry point (step 416) and object class (420) of the requested object. In contrast to the above, if step 412 does not find the requested object ID in the processor 112, but instead finds the object ID in the static object table 108, the object manager 114 consults the table 108 to learn the entry point (step 416) and object class of the object (step 420).

Following step 420, whether performed for dynamic objects or static objects, object manager 114 loads the requested object into RAM 104 and takes appropriate action to execute the object according to the object class and entry point (step 422).

Releasing objects

Fig. 5 shows a sequence 500 for releasing blocked resources upon completion of an object when the object is activated according to fig. 4. For simplicity of illustration, and without limitation, the example of FIG. 5 is described in terms of the component environment described above in FIGS. 1A-1B, 2, and 3.

The sequence 500 begins at step 502, where step 502 is repeatedly executed, such as in response to a periodic timer, a non-periodic event, a hardware interrupt, or other repetitive trigger. The sequence 500 may be repeated for all objects or for each object that has been activated. In the present discussion, step 500 is performed for each object that is activated, referred to as the "current" object. In step 504, object manager 114 determines whether the current object has been released. The release of objects may be determined based on various criteria, such as the completion of the order of the objects. If the current object has not been released, object manager 114 waits (step 506) and retries (step 504) at a later time.

When the current object is released, if the current object is a static object, step 504 proceeds to step 512. In step 512, the object manager 114 frees resources allocated to the current object (step 512), such as by unloading the current object from RAM 104. After step 512, routine 500 terminates (step 514).

Conversely, if the current object is a dynamic object, object manager 114 determines whether processor 112 has been released (step 508). If processor 112 has not been released, object manager 114 waits (step 510) and retries (step 508) later. When the handler is released (step 508), object manager 114 releases the resources allocated to the current object (step 512). For example, the object manager 114 may offload a current object and its processor from the RAM 104. After step 512, the routine 500 terminates (step 514).

OTHER EMBODIMENTS

While the foregoing disclosure shows a number of illustrative embodiments of the invention, it will be apparent to those skilled in the art that various changes and modifications can be made herein without departing from the scope of the invention as defined by the appended claims. Furthermore, although elements of the invention may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. In addition, one of ordinary skill will recognize that the order of operation may be presented in a certain order for purposes of illustration and priority, but the invention provides variations beyond this certain order.

Claims (9)

1. A method for operating a wireless communication device, comprising:

providing a plurality of static objects fixed within the device circuitry, each static object being associated with a unique object ID, each static object having a predefined entry point and object class;

providing a static object table relating to an object ID, an entry point and an object class of each static object;

providing a plurality of object launchers including at least one user interface, one or more drives, and a master controller;

upon indication by a user of the device, operating the device to wirelessly download one or more dynamic objects, assign a unique object ID to each dynamic object, and confirm an entry point and an object class of each dynamic object using a dynamic object handler;

managing activation of static and dynamic objects, comprising:

receiving requests from an object initiator to activate an object, each request including an object ID;

performing an activation operation according to each request, comprising: the entry point and the object class of the requested object are identified with respect to at least one of the dynamic object handler and the static object table referencing the object ID, and the requested object is activated using the identified entry point and object class.

2. The method of claim 1, wherein each request to activate an object includes an object ID.

3. The method of claim 1, wherein the activating operation comprises:

the object ID is first referenced to the dynamic object handler, and

if so, identifying an entry point for the requested object with the dynamic object handler and activating the object at the identified entry point;

if not, a static object table is used to identify the entry point of the requested object and the object is activated at the identified entry point.

4. The method of claim 1, wherein the operations further comprise:

upon each activation of the wireless telephone module, a static object table and a dynamic object handler are constructed.

5. A radiotelephone module comprising:

a plurality of static objects fixed within the modular circuit, each static object being associated with a unique object ID, each static object having a predefined entry point and object type, wherein the entry point and object type of each static object are associated by a static object table;

a plurality of object launchers including at least one user interface, one or more drivers, and a master controller;

an object manager configured to:

operating the device to wirelessly download one or more dynamic objects in accordance with a user indication, assigning a unique object ID to each dynamic object, and using the dynamic object handler to identify an entry point and an object class for each dynamic object;

managing activation of static and dynamic objects, comprising:

receiving requests from an object initiator to activate an object, each request including an object ID;

performing an activation operation according to each request, comprising: the object ID is referenced relative to at least one of the dynamic object handler and the static object table to identify an entry point and an object class of the requested object, and the requested object is activated using the identified entry point and object class.

6. The module of claim 5, wherein the object manager is structured such that activating comprises:

the object ID is first referenced to the dynamic object handler, and

if so, identifying an entry point for the requested object with the dynamic object handler and activating the object at the identified entry point;

if not, a static object table is used to identify the entry point of the requested object and the object is activated at the identified entry point.

7. The module of claim 5, wherein the object manager is further structured to:

a static object table and a dynamic object handler are prepared in response to each boot procedure of the wireless telephone module.

8. The module of claim 5, wherein:

each object has an associated object class;

the static objects are additionally associated with an object ID and a category of each static object;

constructing an object manager such that:

performing an operation of preparing the dynamic object handler such that the dynamic object handler is additionally used to confirm the object class of the dynamic object;

the activating operation further includes: referencing the object ID against at least one of the dynamic object handler and the static object table to identify an object class of the requested object;

the operation of activating the requested object is performed according to the object class of the requested object.

9. A wireless communications apparatus, comprising:

a speaker;

a microphone;

an antenna and a transceiver;

built-in circuitry coupled to the speaker, microphone and transceiver, the circuitry for effecting two-way wireless communication between the remote party and the user with the speaker/microphone through the transceiver, the circuitry further comprising a wireless telephone module including:

a plurality of static objects fixed within the modular circuit, each static object being associated with a unique object ID, each static object having a predefined entry point and object class;

a static object table associated with the object ID and entry point of each static object;

a plurality of object launchers including at least one user interface, one or more drivers, and a master controller;

the object manager is configured to:

operating the device to wirelessly download one or more dynamic objects, assign a unique object ID to each dynamic object, and prepare the dynamic object handler to confirm an entry point and an object class of each dynamic object, as directed by a device user;

managing activation of static and dynamic objects, comprising:

receiving requests from an object initiator to activate an object, each request including an object ID;

performing an activation operation according to each request, comprising: the object ID is referenced relative to at least one of the dynamic object handler and the static object table to identify an entry point and an object class of the requested object, and the requested object is activated using the identified entry point and object class.