System and method for executing wireless communications device dynamic instruction sets Number:7,143,407 from the United States Patent and Trademark Office (PTO) owispatent A system and method are provided for executing dynamic instruction sets in a wireless communications device. The method comprises: forming the system software into symbol libraries, each symbol library comprising symbols having related functionality; arranging the symbol libraries into code sections in a code storage section nonvolatile memory; executing system software; receiving a patch manager run time instruction (PMRTI) or dynamic instruction sets, including conditional operation code and data items, in a file system section nonvolatile memory; calling a run-time library from a first code section; processing the patch manager run time instruction operation code; operating on system data and system software; and, in response to operating on the system data and system software, controlling the execution of the system software.<H communications, instruction, System, and, meth, 7143407.html, Patent, pto, 7143407

Title: System and method for executing wireless communications device dynamic instruction sets

Abstract: A system and method are provided for executing dynamic instruction sets in a wireless communications device. The method comprises: forming the system software into symbol libraries, each symbol library comprising symbols having related functionality; arranging the symbol libraries into code sections in a code storage section nonvolatile memory; executing system software; receiving a patch manager run time instruction (PMRTI) or dynamic instruction sets, including conditional operation code and data items, in a file system section nonvolatile memory; calling a run-time library from a first code section; processing the patch manager run time instruction operation code; operating on system data and system software; and, in response to operating on the system data and system software, controlling the execution of the system software.

Patent Number: 7,143,407 Issued on 11/28/2006 to Rajaram, et al.

Inventors: Rajaram; Gowri (San Diego, CA), Kaplan; Diego (San Diego, CA)
Assignee: Kyocera Wireless Corp. (San Diego, CA)

Appl. No.: 09/927,131

Filed: August 10, 2001

Current U.S. Class: 717/173 ; 455/419; 717/178

Current International Class: G06F 9/44 (20060101); G06F 9/445 (20060101); H04M 3/00 (20060101)

Field of Search: 717/173,106,172,171,178 455/419 714/31 711/15 709/248,224,204 465/419 705/50,28

References Cited [Referenced By]

U.S. Patent Documents


5046082	September 1991	Zicker et al.
5337255	August 1994	Seidel et al.
5400389	March 1995	Niiyama et al.
5481706	January 1996	Peek
5507009	April 1996	Grube et al.
5600823	February 1997	Sherer et al.
5673317	September 1997	Cooper
5699275	December 1997	Beasley et al.
5715462	February 1998	Iwamoto et al.
5734904	March 1998	Kanamori et al.
5771386	June 1998	Baumbauer
5784537	July 1998	Suzuki et al.
5790856	August 1998	Lillich
5835778	November 1998	Yoshihara
5920826	July 1999	Metso et al.
5930704	July 1999	Kay
5938766	August 1999	Anderson et al.
5960356	September 1999	Alperovich et al.
5974312	October 1999	Hayes et al.
6018543	January 2000	Blois et al.
6023620	February 2000	Hansson
6138009	October 2000	Birgerson
6138153	October 2000	Collins, III et al.
6247065	June 2001	Greenspan et al.
6272333	August 2001	Smith
6275694	August 2001	Yoshida et al.
6415266	July 2002	Do
6442660	August 2002	Henerlau et al.
6457174	September 2002	Kuroda et al.
6460070	October 2002	Turek et al.
6493871	December 2002	McGuire et al.
6498789	December 2002	Honda
6549770	April 2003	Marran
6622017	September 2003	Hoffman
6633759	October 2003	Kobayashi
6643506	November 2003	Criss et al.
6754894	June 2004	Costello et al.
6785541	August 2004	Martin
2001/0000538	April 2001	Kowaguchi
2001/0051519	December 2001	Shirai
2001/0054161	December 2001	Wooddruff
2002/0019973	February 2002	Hayashida
2002/0026634	February 2002	Shaw
2002/0065041	May 2002	Lunsford et al.
2002/0072359	June 2002	Moles et al.
2003/0060189	March 2003	Minear et al.
2005/0064847	March 2005	Kirbas et al.

Foreign Patent Documents


19502728	Aug., 1996	DE
19543843	May., 1997	DE
19580133	May., 1999	DE
0459344	Dec., 1991	EP
0889405	Jan., 1999	EP
0918420	May., 1999	EP
1014263	Jun., 2000	EP
2800963	May., 2001	FR
2227584	Aug., 1990	GB
2349485	Nov., 2000	GB
WO 9300633	Jan., 1993	WO
WO 98/09208	Mar., 1998	WO
WO 9922325	May., 1999	WO
WO 0073912	Dec., 2000	WO
WO 0074412	Dec., 2000	WO

Other References

International Search Report (ISR): PCT/ISA/210 for International Application No. PCT/IB02/02866, ISR dated Aug. 9, 2003, 4 pages. cited by other .
Guiagoussou et al., "Implementation of a Diagnostic and Troubleshooting Mulit-Agent System for Cellular Networks", Int'l J Network Mgmnt., pp. 221-237, Aug. 1999. cited by other.

Primary Examiner: Zhen; Wei
Assistant Examiner: Chow; Chih-Ching

Parent Case Text

RELATED APPLICATIONS

This application is a continuation-in-part of U.S. application Ser. No. 09/917,026, filed Jul. 26, 2001; of U.S. application Ser. No. 09/916,460, filed Jul. 26, 2001; and of U.S. application Ser. No. 09/916,900, filed Jul. 26, 2001. Additionally, this application is related 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; and to U.S. application Ser. No. 09/972,519, filed on Oct. 5, 2001.

RELATED APPLICATIONS

This application relates to the following U.S. patent applications, which are assigned to the assignee of the present application Ser. Nos.: 09/916,900; 09/916,460; 09/917,026; 09/969,305; 09/970,188; 09/972,519; 10/206,780; 10/206,516; 10/206,781; 10/665,962; 10/848,939; 10/848,940; and 10/848,941.

Claims

We claim:

1. In a wireless telephone, a method for executing dynamic instruction sets, the method comprising: forming the system software into symbol libraries, each symbol library comprising symbols having related functionality; arranging the symbol libraries into code sections; executing system software on the wireless telephone, the system software for establishing an air interface connection with a wireless service provider; receiving dynamic instructions sets comprising patch manager run time instructions (PMRTIs) having operation codes and data items, using the air interface connection; launching a run-time engine on the wireless telephone, including use of a run-time library from a first code section; processing the received dynamic instruction sets using the run-time engine, including extracting data items responsive to the operation codes; operating on system data and system software using at least the operation codes and the data items in a manner responsive to the operation codes, using the run-time engine; and, executing the system data and system software as operated on by the run-time engine.

2. The method of claim 1 further comprising: following the processing of the dynamic instruction sets, deleting dynamic instruction sets.

3. The method of claim 1 wherein processing dynamic instruction sets includes processing instructions in response to mathematical and logical operations.

4. The method of claim 1 wherein arranging the symbol libraries into code sections includes starting symbol libraries at the start of code sections and arranging symbols to be offset from their respective code section start addresses; the method further comprising: storing the start of code sections at corresponding start addresses; maintaining a code section address table cross-referencing code section identifiers with corresponding start addresses; and, maintaining a symbol offset address table cross-referencing symbol identifiers with corresponding offset addresses, and corresponding code section identifiers.

5. The method of claim 4 wherein receiving the patch manager run time instruction includes receiving symbol identifiers; the method further comprising: locating symbols corresponding to the received symbol identifiers by using the code section address table and symbol offset address table; wherein performing a sequence of operations in response to the operation code includes: when the located symbols are data items, extracting the data; and, when the located symbols are instructions, executing the symbols.

6. The method of claim 1 wherein processing dynamic instruction sets includes: accessing system data stored in a second code section in the file system section; analyzing the system data; creating updated system data; wherein operating on system data and system software includes replacing the system data in the second section with the updated system data; and, wherein executing the system software includes using the updated system data in the execution of the system software.

7. The method of claim 1 further comprising: storing a plurality of code sections in a code storage section nonvolatile memory; wherein processing dynamic instruction sets includes: accessing system data stored in a third code section in the code storage section; analyzing the system data; creating updated system data; wherein operating on the system data and system software includes replacing the system data in the third code section with the updated system data; and, wherein executing the system software includes using the updated system data in the execution of the system software.

8. The method of claim 1 further comprising: storing a plurality of code sections in a code storage section nonvolatile memory; loading read-write data into volatile memory; wherein processing dynamic instruction sets includes: accessing the read-write data in volatile memory; analyzing the read-write data; creating updated read-write data; wherein operating on the system data and system software includes replacing the read-write data in volatile memory with the updated read-write data; and, wherein executing the system software includes using the updated read-write data in the execution of the system software.

9. The method of claim 1 wherein processing dynamic instruction sets includes: in response to the operation code, monitoring the execution of the system software; collecting performance data; storing the performance data; and, Wherein operating on the system data and system software includes using the performance data in the evaluation of system software.

10. The method of claim 9 further comprising: transmitting the stored data via an airlink interface.

11. The method of claim 1 further comprising: storing a plurality of code sections in a code storage section nonvolatile memory; wherein receiving patch manager run time instructions includes receiving a new code section; wherein operating on the system data and system software includes adding the new code section to the code storage section; and, wherein executing the system software includes using the new code section in the execution of the system software.

12. The method of claim 11 wherein receiving a new code section includes receiving an updated code section; and, wherein operating on the system data and system software includes replacing a fourth code section in the code storage section with the updated code section.

13. In a wireless telephone, a method for executing dynamic instruction sets, the method comprising: forming system software for the wireless telephone into symbol libraries, each symbol library comprising symbols having related functionality; arranging the symbol libraries into code sections in a code storage section nonvolatile memory in the wireless telephone; executing system software on the wireless telephone; receiving a patch manager run time instruction (PMRTI), including conditional operation code and data items, in a file, system section nonvolatile memory in the wireless telephone; calling a run-time library from a first code section of the code storage section arranged in the wireless telephone; processing the patch manager run time instruction operation code using a run-time engine on the wireless telephone; operating on system data and system software using the PMRTI and the run-time library; and, in response to operating on the system data and system software, controlling the execution of the system software.

14. A wireless telephone, including a dynamic instruction set execution computer system, comprising: an airlink interface for establishing an air interface communication with a wireless service provider to receive dynamic instruction sets; executable system software and wireless telephone system data differentiated into symbol libraries, each symbol library comprising symbols having related functionality, arranged into code sections and including a run-time library arranged in a first code section in a storage area of the wireless telephone; the received dynamic instruction sets for operating on the wireless telephone system data and the system software, the dynamic instructions including operation codes and data items, and wherein the dynamic instruction sets are organized in a patch manager run time instruction (PMRTI); and, a run-time engine operating on the wireless telephone for processing the received dynamic instruction sets, thereby affecting the execution of the system software thereafter.

15. The wireless telephone apparatus of claim 14 wherein the run-time engine processes the received dynamic instruction sets to perform mathematical and logical operations.

16. The wireless telephone apparatus of claim 15 further comprising: a file system section nonvolatile memory for receiving the dynamic instruction sets.

17. The wireless telephone apparatus of claim 16 further comprising: an interface through which the dynamic instruction sets are received into the file system section, wherein the interface is selected from the group including airlink, radio frequency (RF) hardline, installable memory module, infrared, and logic port interfaces.

18. The wireless telephone apparatus of claim 15 further comprising: a code storage section nonvolatile memory for storing code sections.

19. The wireless telephone apparatus of claim 15 wherein the run-time engine reads the dynamic instruction set operation code and performs a sequence of operations in response to the operation code.

20. The wireless telephone apparatus of claim 19 wherein the run-time engine captures the length of a dynamic instruction set to determine if data items are included, extracts the data items from the dynamic instruction set, and uses the extracted data in performing the sequence of operations responsive to the operation code.

21. The wireless telephone apparatus of claim 20 wherein the symbol libraries are arranged to start at the start of code sections and symbols are arranged to be offset from their respective code section start addresses; wherein a code storage section includes start addresses corresponding to code section start addresses; the computer system further comprising: a code section address table cross-referencing code section identifiers with corresponding start addresses in the code storage section; and, a symbol offset address table cross-referencing symbol identifiers with corresponding offset addresses, and corresponding code section identifiers.

22. The wireless telephone apparatus of claim 19 wherein the dynamic instruction set includes symbol identifiers; and, wherein the run-time engine locates symbols corresponding to the received symbol identifiers using the code section address table and symbol offset address table, extracts data when the located symbols are data items, and executes the symbols when the located symbols are instructions.

23. The wireless telephone apparatus of claim 19 wherein the system data is stored in a second code section in the file system section; wherein the run-time engine accesses system data, analyzes the system data, creates updated system data, and replaces the system data in the second code section with the updated system data in response to the operation code; and, wherein the system software is controlled to execute using the updated system data.

24. The wireless telephone apparatus of claim 19 wherein the system data is stored in a third code section in the code storage section; wherein the run-time engine accesses system data, analyzes the system data, creates updated system data, and replaces the system data in the third code section with the updated system data in response to the operation code; and, wherein the system software is controlled to execute using the updated system data.

25. The wireless telephone apparatus of claim 19 further comprising: a volatile memory to accept read-write data; wherein the run-time engine accesses the read-write data, analyzes the read-write data, creates updated read-write data, and replaces the read-write data in the volatile memory with the updated read-write data in response to the operation code; and, wherein the system software is controlled to execute using the updated read-write data in volatile memory.

26. The wireless telephone apparatus of claim 19 wherein the run-time engine monitors the execution of the system software, collects performance data, and stores the performance data in the file system section in response to the operation code; and, wherein the system software is controlled to execute by collecting the performance data for evaluation of the system software.

27. The wireless telephone apparatus of claim 26 wherein the run-time engine accesses the performance data from the file system section and transmits the performance data via an airlink interface in response to the operation code.

28. The wireless telephone apparatus of claim 19 wherein the file system section receives a patch manager run time instruction including a new code section; wherein the run-time engine adds the new code section to the code storage section in response to the operation code; and, wherein the system software is controlled to execute using the new code section.

29. The wireless telephone apparatus of claim 28 wherein the file system section receives a patch manager run time instruction including an updated code section; wherein the run-time engine replaces a fourth code section in the code storage section with the updated code section in response to the operation code; and, wherein the system software is controlled to execute using the updated code section.

30. A wireless telephone, including a dynamic instruction set execution computer system, comprising: an airlink interface for establishing an air interface communication with a wireless service provider; executable system software and wireless telephone system data in a storage area of the wireless telephone differentiated into code sections with symbol libraries arranged within; patch manager run time instructions (PMRTIs) organized as dynamic instruction sets with operation code and data items for operating on the wireless telephone system data and the system software and a run-time engine which processes the PMRTIs thereafter affecting the execution of the system software; a file system section nonvolatile memory in a storage area of the wireless telephone for receiving the patch manager run time instructions; and, a run-time library arranged in a first code section for processing the dynamic instruction sets.

Description

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention generally relates to wireless communications devices and, more particularly, to a system and method for executing dynamic instructions sets with the system software of a wireless communication device in the field.

2. Description of the Related Art

It is not uncommon to release software updates for phones that are already in the field. These updates may relate to problems found in the software once the phones have been manufactured and distributed to the public. Some updates may involve the use of new features on the phone, or services provided by the service provider. Yet other updates may involve regional problems, or problems associated with certain carriers. For example, in certain regions the network layout of carriers may impose airlink interface conditions on the handset that cause the handset to demonstrate unexpected behavior such as improper channel searching, improper call termination, improper audio, or the like.

The traditional approach to such updates has been to recall the wireless communications device, also referred to herein as a wireless device, phone, telephone, or handset, to the nearest carrier retail/service outlet, or to the manufacturer to process the changes. The costs involved in such updates are extensive and eat into the bottom line. Further, the customer is inconvenienced and likely to be irritated. Often times, the practical solution is to issue the customer new phones.

The wireless devices are used in a number of environments, with different subscriber services, for a number of different customer applications. Therefore, even if the software of a wireless device can be upgraded to improve service, it is unlikely that the upgrade will provide a uniform improvement for all users.

It would be advantageous if wireless communications device software could be upgraded cheaply, and without inconvenience to the customer.

It would be advantageous if wireless communications device software could be upgraded without the customer losing the use of their phones for a significant period of time.

It would be advantageous if wireless communications device software could be updated with a minimum of technician service time, or without the need to send the device into a service facility.

It would be advantageous if the wireless device system software could be differentiated into code sections, so that only specific code sections of system software would need to be replaced, to update the system software. It would be advantageous if these code sections could be communicated to the wireless device via the airlink.

It would be advantageous if the code section updates could be made uniquely for each wireless communications device based upon that device's circumstances.

It would be advantageous if the wireless device could monitor the performance of the wireless device system software, collect performance data, and transmits the data to a system central collection depot for analysis.

SUMMARY OF THE INVENTION

Wireless communications device software updates give customers the best possible product and user experience. An expensive component of the business involves the recall of handsets to update the software. These updates may be necessary to offer the user additional services or to address problems discovered in the use of the phone after it has been manufactured. The present invention makes it possible to practically upgrade handset software in the field, via the airlink interface. More specifically, the present invention permits the wireless communication device to execute dynamic instruction sets. These dynamic instruction sets permit the wireless device to "intelligently", or conditionally upgrade the system software and system data. Further, the dynamic instruction sets permit the wireless device to monitor system software performance, and transmit the performance data for analysis.

Accordingly, a method is provided for executing dynamic instruction sets in a wireless communications device. The method comprises: forming the system software into symbol libraries, each symbol library comprising symbols having related functionality; arranging the symbol libraries into code sections in a code storage section nonvolatile memory; executing system software; receiving a patch manager run time instruction (PMRTI) or dynamic instruction sets, including conditional operation code and data items, in a file system section nonvolatile memory; calling a run-time library from a first code section; processing the patch manager run time instruction operation code; operating on system data and system software; and, in response to operating on the system data and system software, controlling the execution of the system software.

Additional details of the above-described method for executing dynamic instruction sets, and a system for executing dynamic instruction sets are provided below.

BRIEF DESCRIPTION OF THE DRAWING

FIG. 1 is a schematic block diagram of the overall wireless device software maintenance system.

FIG. 2 is a schematic block diagram of the software maintenance system, highlighting the installation of instruction sets via the airlink interface.

FIG. 3 is a schematic block diagram illustrating the present invention system for executing dynamic instruction sets in a wireless communications device.

FIG. 4 is a schematic block diagram of the wireless device memory.

FIG. 5 is a table representing the code section address table of FIG. 3.

FIG. 6 is a detailed depiction of symbol library one of FIG. 3, with symbols.

FIG. 7 is a table representing the symbol offset address table of FIG. 3.

FIG. 8 is a depiction of the operation code (op-code) being accessed by the run-time engine.

FIG. 9 is a more detailed depiction of the first operation code of FIG. 8.

FIGS. 10a and 10b are flowcharts illustrating the present invention method for executing dynamic instruction sets in a wireless communications device.

FIG. 11 is a flowchart illustrating an exemplary dynamic instruction set operation.

FIG. 12 is a flowchart illustrating another exemplary dynamic instruction set operation.

FIG. 13 is a flowchart illustrating a third exemplary dynamic instruction set operation.

FIG. 14 is a flowchart illustrating a fourth exemplary dynamic instruction set operation.

FIG. 15 is a flowchart illustrating a fifth exemplary dynamic instruction set operation.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Some portions of the detailed descriptions that follow are presented in terms of procedures, steps, logic blocks, codes, processing, and other symbolic representations of operations on data bits within a wireless device microprocessor or memory. These descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. A procedure, microprocessor executed step, application, logic block, process, etc., is here, and generally, conceived to be a self-consistent sequence of steps or instructions leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated in a microprocessor based wireless device. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like. Where physical devices, such as a memory are mentioned, they are connected to other physical devices through a bus or other electrical connection. These physical devices can be considered to interact with logical processes or applications and, therefore, are "connected" to logical operations. For example, a memory can store or access code to further a logical operation, or an application can call a code section from memory for execution.

It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussions, it is appreciated that throughout the present invention, discussions utilizing terms such as "processing" or "connecting" or "translating" or "displaying" or "prompting" or "determining" or "displaying" or "recognizing" or the like, refer to the action and processes of in a wireless device microprocessor system that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the wireless device memories or registers or other such information storage, transmission or display devices.

FIG. 1 is a schematic block diagram of the overall wireless device software maintenance system 100. The present invention system software organization is presented in detail below, following a general overview of the software maintenance system 100. The general system 100 describes a process of delivering system software updates and instruction sets (programs), and installing the delivered software in a wireless device. System software updates and patch manager run time instructions (PMRTI), that are more generally known as instruction sets or dynamic instruction sets, are created by the manufacturer of the handsets. The system software is organized into symbol libraries. The symbol libraries are arranged into code sections. When symbol libraries are to be updated, the software update 102 is transported as one or more code sections. The software update is broadcast to wireless devices in the field, of which wireless communications device 104 is representative, or transmitted in separate communications from a base station 106 using well known, conventional air, data or message transport protocols. The invention is not limited to any particular transportation format, as the wireless communications device can be easily modified to process any available over-the-air transport protocol for the purpose of receiving system software and PMRTI updates.

The system software can be viewed as a collection of different subsystems. Code objects can be tightly coupled into one of these abstract subsystems and the resulting collection can be labeled as a symbol library. This provides a logical breakdown of the code base and software patches and fixes can be associated with one of these symbol libraries. In most cases, a single update is associated with one, or at most two, symbol libraries. The rest of the code base, the other symbol libraries, remains unchanged.

The notion of symbol libraries provides a mechanism to deal with code and constants. The read-write (RW) data, on the other hand, fits into a unique individual RW library that contains RAM based data for all libraries.

Once received by the wireless device 104, the transported code section must be processed. This wireless device over-writes a specific code section of nonvolatile memory 108. The nonvolatile memory 108 includes a file system section (FSS) 110 and a code storage section 112. The code section is typically compressed before transport in order to minimize occupancy in the FSS 110. Often the updated code section will be accompanied by its RW data, which is another kind of symbol library that contains all the RW data for each symbol library. Although loaded in random access volatile read-write memory 114 when the system software is executing, the RW data always needs to be stored in the nonvolatile memory 108, so it can be loaded into random access volatile read-write memory 114 each time the wireless device is reset. This includes the first time RW data is loaded into random access volatile read-write memory. As explained in more detail below, the RW data is typically arranged with a patch manager code section.

The system 100 includes the concept of virtual tables. Using such tables, symbol libraries in one code section can be patched (replaced), without breaking (replacing) other parts of the system software (other code sections). Virtual tables execute from random access volatile read-write memory 114 for efficiency purposes. A code section address table and symbol offset address table are virtual tables.

The updated code sections are received by the wireless device 104 and stored in the FSS 110. A wireless device user interface (UI) will typically notify the user that new software is available. In response to UI prompts the user acknowledges the notification and signals the patching or updating operation. Alternately, the updating operation is performed automatically. The wireless device may be unable to perform standard communication tasks as the updating process is performed. The patch manager code section includes a non-volatile read-write driver symbol library that is also loaded into random access volatile read-write memory 114. The non-volatile read-write driver symbol library causes code sections to be overwritten with updated code sections. The patch manager code section includes the read-write data, code section address table, and symbol offset address table, as well a symbol accessor code and the symbol accessor code address (discussed below). Portions of this data are invalid when updated code sections are introduced, and an updated patch manager code sections includes read-write data, a code section address table, and a symbol offset address table valid for the updated code sections. Once the updated code sections are loaded into the code storage section 112, the wireless device is reset. Following the reset operation, the wireless device can execute the updated system software. It should also be understood that the patch manager code section may include other symbol libraries that have not been discussed above. These other symbol libraries need not be loaded into read-write volatile memory 114.

FIG. 2 is a schematic block diagram of the software maintenance system 100, highlighting the installation of instruction sets via the airlink interface. In addition to updating system software code sections, the maintenance system 100 can download and install dynamic instructions sets, programs, or patch manager instruction sets (PMIS), referred to herein as patch manager run time instructions (PMRTI). The PMRTI code section 200 is transported to the wireless device 104 in the same manner as the above-described system software code sections. PMRTI code sections are initially stored in the FSS 110. A PMRTI code section is typically a binary file that may be visualized as compiled instructions to the handset. A PMRTI code section is comprehensive enough to provide for the performance of basic mathematical operations and the performance of conditionally executed operations. For example, an RF calibration PMRTI could perform the following operations:

IF RF CAL ITEM IS LESS THAN X

EXECUTE INSTRUCTION

ELSE

EXECUTE INSTRUCTION

A PMRTI can support basic mathematical operations, such as: addition, subtraction, multiplication, and division. As with the system software code sections, the PMRTI code section may be loaded in response to UI prompts, and the wireless device must be reset after the PMRTI is loaded into code storage section 112. Then the PMRTI section can be executed. If the PMRTI code section is associated with any virtual tables or read-write data, an updated patch manager code section will be transported with the PMRTI for installation in the code storage section 112. Alternately, the PMRTI can be kept and processed from the FSS 110. After the handset 104 has executed all the instructions in the PMRTI section, the PMRTI section can be deleted from the FSS 110. Alternately, the PMRTI is maintained for future operations. For example, the PMRTI may be executed every time the wireless device is energized.

PMRTI is a very powerful runtime instruction engine. The handset can execute any instruction delivered to it through the PMRTI environment. This mechanism may be used to support RF calibrations. More generally, PMRTI can be used to remote debug wireless device software when software problems are recognized by the manufacturer or service provider, typically as the result of user complaints. PMRTI can also record data needed to diagnose software problems. PMRTI can launch newly downloaded system applications for data analysis, debugging, and fixes. PMRTI can provide RW data based updates for analysis and possible short term fix to a problem in lieu of an updated system software code section. PMRTI can provide memory compaction algorithms for use by the wireless device.

In some aspects of the invention, the organization of the system software into symbol libraries may impact the size of the volatile memory 114 and nonvolatile memory 108 required for execution. This is due to the fact that the code sections are typically larger than the symbol libraries arranged in the code sections. These larger code sections exist to accommodate updated code sections. Organizing the system software as a collection of libraries impacts the nonvolatile memory size requirement. For the same code size, the amount of nonvolatile memory used will be higher due to the fact that code sections can be sized to be larger than the symbol libraries arranged within.

Once software updates have been delivered to the wireless device, the software maintenance system 100 supports memory compaction. Memory compaction is similar to disk de-fragmentation applications in desktop computers. The compaction mechanism ensures that memory is optimally used and is well balanced for future code section updates, where the size of the updated code sections are unpredictable. The system 100 analyzes the code storage section as it is being patched (updated). The system 100 attempts to fit updated code sections into the memory space occupied by the code section being replaced. If the updated code section is larger than the code section being replaced, the system 100 compacts the code sections in memory 112. Alternately, the compaction can be calculated by the manufacturer or service provider, and compaction instructions can be transported to the wireless device 104.

Compaction can be a time consuming process owing to the complexity of the algorithm and also the vast volume of data movement. The compaction algorithm predicts feasibility before it begins any processing. UI prompts can be used to apply for permission from the user before the compaction is attempted.

In some aspects of the invention, all the system software code sections can be updated simultaneously. A complete system software upgrade, however, would require a larger FSS 110.

FIG. 3 is a schematic block diagram illustrating the present invention dynamic instruction set execution in a wireless communications device. The system 300 comprises a code storage section 112 in memory 108 including executable wireless device system software differentiated into a plurality of current code sections. Code section one (302), code section two (304), code section n (306), and a patch manager code section 308 are shown. However, the invention is not limited to any particular number of code sections. Further, the system 300 further comprises a first plurality of symbol libraries arranged into the second plurality of code sections. Shown are symbol library one (310) arranged in code section one (302), symbol libraries two (312) and three (314) arranged in code section two (304), and symbol library m (316) arranged in code section n (306). Each library comprises symbols having related functionality. For example, symbol library one (310) may be involved in the operation of the wireless device liquid crystal display (LCD). Then, the symbols would be associated with display functions. As explained in detail below, additional symbol libraries are arranged in the patch manger code section 308.

FIG. 4 is a schematic block diagram of the wireless device memory. As shown, the memory is the code storage section 112 of FIG. 1. The memory is a writeable, nonvolatile memory, such as Flash memory. It should be understood that the code sections need not necessarily be stored in the same memory as the FSS 110. It should also be understood that the present invention system software structure could be enabled with code sections stored in a plurality of cooperating memories. The code storage section 112 includes a second plurality of contiguously addressed memory blocks, where each memory block stores a corresponding code section from the second plurality of code sections. Thus, code section one (302) is stored in a first memory block 400, code section two (304) in the second memory block 402, code section n (306) in the nth memory block 404, and the patch manager code section (308) in the pth memory block 406.

Contrasting FIGS. 3 and 4, the start of each code section is stored at corresponding start addresses in memory, and symbol libraries are arranged to start at the start of code sections. That is, each symbol library begins at a first address and runs through a range of addresses in sequence from the first address. For example, code section one (302) starts at the first start address 408 (marked with "S") in code storage section memory 112. In FIG. 3, symbol library one (310) starts at the start 318 of the first code section. Likewise code section two (304) starts at a second start address 410 (FIG. 4), and symbol library two starts at the start 320 of code section two (FIG. 3). Code section n (306) starts at a third start address 412 in code storage section memory 112 (FIG. 4), and symbol library m (316) starts at the start of code section n 322 (FIG. 3). The patch manager code section starts at pth start address 414 in code storage section memory 112, and the first symbol library in the patch manager code section 308 starts at the start 324 of the patch manager code section. Thus, symbol library one (310) is ultimately stored in the first memory block 400. If a code section includes a plurality of symbol libraries, such as code section two (304), the plurality of symbol libraries are stored in the corresponding memory block, in this case the second memory block 402.

In FIG. 3, the system 300 further comprises a code section address table 326 as a type of symbol included in a symbol library arranged in the patch manager code section 308. The code section address table cross-references code section identifiers with corresponding code section start addresses in memory.

FIG. 5 is a table representing the code section address table 326 of FIG. 3. The code section address table 326 is consulted to find the code section start address for a symbol library. For example, the system 300 seeks code section one when a symbol in symbol library one is required for execution. To find the start address of code section one, and therefore locate the symbol in symbol library one, the code section address table 326 is consulted. The arrangement of symbol libraries in code sections, and the tracking of code sections with a table permits the code sections to be moved or expanded. The expansion or movement operations may be needed to install upgraded code sections (with upgraded symbol libraries).

Returning to FIG. 3, it should be noted that not every symbol library necessarily starts at the start of a code section. As shown, symbol library three (314) is arranged in code section two (304), but does not start of the code section start address 320. Thus, if a symbol in symbol library three (314) is required for execution, the system 300 consults the code section address table 326 for the start address of code section two (304). As explained below, a symbol offset address table permits the symbols in symbol library three (314) to be located. It does not matter that the symbols are spread across multiple libraries, as long as they are retained with the same code section.

As noted above, each symbol library includes functionally related symbols. A symbol is a programmer-defined name for locating and using a routine body, variable, or data structure. Thus, a symbol can be an address or a value. Symbols can be internal or external. Internal symbols are not visible beyond the scope of the current code section. More specifically, they are not sought by other symbol libraries, in other code sections. External symbols are used and invoked across code sections and are sought by libraries in different code sections. The symbol offset address table typically includes a list of all external symbols.

For example, symbol library one (310) may generate characters on a wireless device display. Symbols in this library would, in turn, generate telephone numbers, names, the time, or other display features. Each feature is generated with routines, referred to herein as a symbol. For example, one symbol in symbol library one (310) generates telephone numbers on the display. This symbol is represented by an "X", and is external. When the wireless device receives a phone call and the caller ID service is activated, the system must execute the "X" symbol to generate the number on the display. Therefore, the system must locate the "X" symbol.

FIG. 6 is a detailed depiction of symbol library one (310) of FIG. 3, with symbols. Symbols are arranged to be offset from respective code section start addresses. In many circumstances, the start of the symbol library is the start of a code section, but this is not true if a code section includes more than one symbol library. Symbol library one (310) starts at the start of code section one (see FIG. 3). As shown in FIG. 6, the "X" symbol is located at an offset of (03) from the start of the symbol library and the "Y" symbol is located at an offset of (15). The symbol offset addresses are stored in a symbol offset address table 328 in the patch manager code section (see FIG. 3).

FIG. 7 is a table representing the symbol offset address table 328 of FIG. 3. The symbol offset address table 328 cross-references symbol identifiers with corresponding offset addresses, and with corresponding code section identifiers in memory. Thus, when the system seeks to execute the "X" symbol in symbol library one, the symbol offset address table 328 is consulted to locate the exact address of the symbol, with respect to the code section in which it is arranged.

Returning to FIG. 3, the first plurality of symbol libraries typically all include read-write data that must be consulted or set in the execution of these symbol libraries. For example, a symbol library may include an operation dependent upon a conditional statement. The read-write data section is consulted to determine the status required to complete the conditional statement. The present invention groups the read-write data from all the symbol libraries into a shared read-write section. In some aspects of the invention, the read-write data 330 is arranged in the patch manager code section 308. Alternately (not shown), the read-write data can be arranged in a different code section, code section n (306), for example.

The first plurality of symbol libraries also includes symbol accessor code arranged in a code section to calculate the address of a sought symbol. The symbol accessor code can be arranged and stored at an address in a separate code section, code section two (304), for example. However, as shown, the symbol accessor code 332 is arranged and stored at an address in the patch manager code section 308. The system 300 further comprises a first location for storage of the symbol accessor code address. The first location can be a code section in the code storage section 112, or in a separate memory section of the wireless device (not shown). The first location can also be arranged in the same code section as the read-write data. As shown, the first location 334 is stored in the patch manager code section 308 with the read-write data 330, the symbol offset address table 328, the code section address table 326, and the symbol accessor code 332, and the patch library (patch symbol library) 336.

The symbol accessor code accesses the code section address table and symbol offset address tables to calculate, or find the address of a sought symbol in memory. That is, the symbol accessor code calculates the address of the sought symbol using a corresponding symbol identifier and a corresponding code section identifier. For example, if the "X" symbol in symbol library one is sought, the symbol accessor is invoked to seek the symbol identifier (symbol ID) "X_1", corresponding to the "X" symbol (see FIG. 7). The symbol accessor code consults the symbol offset address table to determine that the "X_1" symbol identifier has an offset of (03) from the start of code section one (see FIG. 6). The symbol accessor code is invoked to seek the code section identifier "CS_1", corresponding to code section one. The symbol accessor code consults the code section address table to determine the start address associated with code section identifier (code section ID) "CS_1". In this manner, the symbol accessor code determines that the symbol identifier "X_1" is offset (03) from the address of (00100), or is located at address (00103).

The symbol "X" is a reserved name since it is a part of the actual code. In other words, it has an absolute data associated with it. The data may be an address or a value. The symbol identifier is an alias created to track the symbol. The symbol offset address table and the code section address table both work with identifiers to avoid confusion with reserved symbol and code section names. It is also possible that the same symbol name is used across many symbol libraries. The use of identifiers prevents confusion between these symbols.

Returning to FIG. 1, the system 3