System and method for field downloading a wireless communication device software code section

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 updating code sections in the system software of a wireless communication device in the field, via an airlink interface.

2. Description of the Related Art

It is not uncornmon 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.

One example conventional system for configuring software in a telecommunication device is described in US 5,771,386 (DE 19,502,728) ("Baumbauer"). Baumbauer relates to a telecommunication device having software that includes several separately compilable program units. To reduce the time necessary for manufacturing the device and the time necessary for implementing software changes, Baumbauer teaches that the program units each have a header which contains addresses (Ap1, Ap2, Ad) used for addressing procedures and/or data combined in the program units. Furthermore, a catalogue that contains references for addressing the headers of the program units is provided. The catalogue is available to all the loaded program units. Within the framework of the manufacture of the telecommunication device, the predefined program units need not be linked when the software of the telecommunication device is implemented.

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.

<b>SUMMARY OF THE INVENTION</b>

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.

Accordingly, a method as defined in claim 1 has been provided for updating system software stored in the memory of a wireless communications device. The method comprises: forming the system software into a first plurality of symbol libraries including a code section address table, a symbol offset address table, a symbol accessor code, a patch library, and read-write data for a plurality of symbol libraries; arranging the code section address table, the symbol offset address table, the symbol accessor code, the patch library, the read-write data, and the symbol accessor code address into a patch manager code section; storing system software for the wireless device in a plurality of current code sections; receiving new code sections via a wireless communications device air interface; storing new code sections in a memory file system section; identifying current code sections for updating; replacing current code sections with new code sections to form updated system software for the wireless device; and, executing the updated system software.

In some aspects of the invention, receiving new code sections includes receiving a new patch manager code section; and, replacing current code sections with new code sections to form updated system software for the wireless device includes replacing a current patch manger code section with the new patch manager code section. Additional details of the above-described method for updating wireless device system software, and a wireless device system for updating system software as defined in claim 17 are presented in detail below.

<b>BRIEF DESCRIPTION OF THE DRAWINGS</b>

<ul id="ul0001" list-style="none" compact="compact"><li>Fig. 1 is a schematic block diagram of the overall wireless device software maintenance system.</li><li>Fig. 2 is a schematic block diagram of the software maintenance system, highlighting the installation of instruction sets via the airlink interface.</li><li>Fig. 3 is a schematic block diagram illustrating the present invention system for updating system software in a wireless communications device.</li><li>Fig. 4 is a schematic block diagram of the wireless device memory.</li><li>Fig. 5 is a table representing the code section address table of Fig. 3.</li><li>Fig. 6 is a detailed depiction of symbol library one of Fig. 3, with symbols.</li><li>Fig. 7 is a table representing the symbol offset address table of Fig. 3.</li><li>Figs. 8a through 8c are flowcharts illustrating the present invention method for updating system software in a wireless communications device memory.</li></ul>

<b>DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS</b>

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.

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 or patch maker instruction sets (PMIS) 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 PMIS 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, remain 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. As shown in the figure, code section n and the patch manager code sections are 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 instructions sets or programs, referred to herein as patch maker instruction set (PMIS). The PMIS code section 200 is transported to the wireless device 104 in the same manner as the above-described system software code sections. PMIS code sections are initially stored in the FSS 110. A PMIS code section is typically a binary file that may be visualized as compiled instructions to the handset. A PMIS 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 PMIS could perform the following operations: <i>IF RF CAL JTEM IS LESS THAN X</i><i>EXECUTE INSTRUCTION</i><i>ELSE</i><i>EXECUTE INSTRUCTION</i>

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

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.

PMIS is a very powerful runtime instruction engine. The handset can execute any instruction delivered to it through the PMIS environment. This mechanism may be used to support RF calibrations and PRI updates. More generally, PMIS 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. PMIS can also record data needed to diagnose software problems. PMIS can launch newly downloaded system applications for data analysis, debugging, and fixes. PMIS 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. PMIS can provide memory compaction algorithms for use by the wireless device.

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 me 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 system for updating system software 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 manager 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 <i>n</i>th memory block 404, and the patch manager code section (308) in the <i>p</i>th 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 <i>m</i> (316) starts at the start of code section n 322 (Fig. 3). The patch manager code section starts at <i>p</i>th 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 software structure 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 3 (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 located 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 2 (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 software structure 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 software structure 300 further comprises a read-write volatile memory 114, typically random access memory (RAM). The read-write data 330, code section address table 326, the symbol offset address table 328, the symbol accessor code 332, and the symbol accessor code address 334 are loaded into the read-write volatile memory 114 from the patch manager section for access during execution of the system software. As is well known, the access times for code stored in RAM is significantly less than the access to a nonvolatile memory such as Flash.

Returning to Fig. 3, it can be noted that the symbol libraries need not necessarily fill the code sections into which they are arranged, although the memory blocks are sized to exactly accommodate the corresponding code sections stored within. Alternately stated, each of the second plurality of code sections has a size in bytes that accommodates the arranged symbol libraries, and each of the contiguously addressed memory blocks have a size in bytes that accommodates corresponding code sections. For example, code section one (302) may be a 100 byte section to accommodate a symbol library having a length of 100 bytes. The first memory block would be 100 bytes to match the byte size of code section one. However, the symbol library loaded into code section 1 may be smaller than 100 bytes. As shown in Fig. 3, code section one (302) has an unused section 340, as symbol library one (310) is less than 100 bytes. Thus, each of the second plurality of code sections may have a size larger than the size needed to accommodate the arranged symbol libraries. By "oversizing" the code sections, larger updated symbol libraries can be accommodated.

As seen in Fig. 3, the system 300 includes a patch symbol library, which will be referred to herein as patch library 336, to arrange new code sections in the code storage section with the current code sections. The arrangement of new code sections with current code sections in the code storage section forms updated executable system software. The patch manager 336 not only arranges new code sections in with the current code sections, it also replaces code sections with updated code sections.

Returning to Fig. 4, the file system section 110 of memory 108 receives new code sections, such as new code section 450 and updated patch manager code section 452. The file system section also receives a first patch manager instruction set (PMIS) 454 including instructions for arranging the new code sections with the current code sections. As seen in Fig. 1, an airlink interface 150 receives new, or updated code sections, as well as the first PMIS. Although the airlink interface 150 is being represented by an antenna, it should be understood that the airlink interface would also include an RF transceiver, baseband circuitry, and demodulation circuitry (not shown). The file system section 110 stores the new code sections received via the airlink interface 150. The patch library 336, executing from read-write volatile memory 114, replaces a first code section in the code storage section, code section n (306) for example, with the new, or updated code section 450, in response to the first PMIS 454. Typically, the patch manager code section 308 is replaced with the updated patch manager code section 452. When code sections are being replaced, the patch library 336 over-writes the first code section, code section n (306) for example, in the code storage section 112 with the updated code sections, code section 450 for example, in the file system section 110. In the extreme case, all the code sections in code storage section 112 are replaced with updated code sections. That is, the FSS 110 receives a second plurality of updated code sections (not shown), and the patch library 336 replaces the second plurality of code sections in the code storage section 112 with the second plurality of updated code sections. Of course, the FSS 110 must be large enough to accommodate the second plurality of updated code sections received via the airlink interface.

As noted above, the updated code sections being received may include read-write data code sections, code section address table code sections, symbol libraries, symbol offset address table code sections, symbol accessor code sections, or a code section with a new patch library. All these code sections, with their associated symbol libraries and symbols, may be stored as distinct and independent code sections. Then each of these code sections would be replaced with a unique updated code section. That is, an updated read-write code section would be received and would replace the read-write code section in the code storage section. An updated code section address table code section would be received and would replace the code section address table code section in the code storage section. An updated symbol offset address table code section would be received and would replace the symbol offset address table code section in the code storage section. An updated symbol accessor code section would be received and would replace the symbol accessor code section in the code storage section. Likewise, an updated patch manager code section (with a patch library) would be received and would replace the patch manager code section in the code storage section.

However, the above-mentioned code sections are typically bundled together in the patch manager code section. Thus, the read-write code section in the code storage section is replaced with the updated read-write code section from the file system section 110 when the patch manager code section 308 is replaced with the updated patch manager code section 450. Likewise, the code section address table, the symbol offset address table, the symbol accessor code sections, as well as the patch library are replaced when the updated patch manager code section 450 is installed. The arrangement of the new read-write data, the new code section address table, the new symbol offset address table, the new symbol accessor code, and the new patch library as the updated patch manager code section 450, together with the current code sections in the code storage section, forms updated executable system software. When the file system section 110 receives an updated symbol accessor code address, the patch manager replaces the symbol accessor code address in the first location in memory with updated symbol accessor code address. As noted above, the first location in memory 334 is typically in the patch manager code section (see Fig. 3). ,

Figs. 8a through 8c are flowcharts illustrating the present invention method for updating system software in a wireless communications device memory. Although the method is depicted as a sequence of numbered steps for clarity, no order should be inferred from the numbering unless explicitly stated. The method begins at Step 800. Step 802 forms the system software into a first plurality of symbol libraries, each symbol library comprising at least one symbol. Further, forming system software into a first plurality of symbol libraries includes each symbol library comprising symbols having related functionality. Step 804 arranges the first plurality of symbol libraries into a second plurality of code sections. Step 806 stores system software for the wireless device in a plurality of current code sections. Step 808 receives a new code section via a wireless communications device air interface. Step 810 arranges the new code section with current code sections to form updated system software for the wireless device. Step 812 executes the updated system software. In some aspects of the invention, Step 809 identifies a first code section for updating. Then, arranging new code section with current code sections in Step 810 includes replacing the first code section with the new code section. Executing the updated system software in Step 812 includes using the new code section in executing the updated system software. When Step 806 stores system software for the wireless device in a second plurality of current code sections and a second plurality of updated code sections are received in Step 808, then Step 810 includes replacing the second plurality of current code sections with the second plurality of updated code sections, and Step 812 uses the second plurality of updated code sections in executing the updated system software.

In some aspects, forming system software into a first plurality of symbol libraries in Step 802 includes forming read-write data for a plurality of symbol libraries. Then, arranging the first plurality of symbol libraries into a second plurality of code sections in Step 804 includes arranging the read-write data in a shared read-write code section. Receiving a new code section in Step 808 includes receiving an updated read-write code section, and identifying a first code section for updating in Step 809 includes identifying the read-write code section. Arranging the new code section with current code sections to form updated system software in Step 810 includes replacing the read-write code section with the updated read-write code section. Executing the updated system software in Step 812 includes using the updated read-write code section in executing of the updated system software. In some aspects of the invention, arranging the first plurality of symbol libraries into a second plurality of code sections in Step 804 includes starting symbol libraries at the start of code sections. Storing system software for the wireless device in a plurality of current code sections in Step 806 includes storing the start of code sections at corresponding start addresses. Then, a further step, Step 807a maintains a code section address table cross-referencing code section identifiers with corresponding start addresses.

In some aspects of the invention, arranging the first plurality of symbol libraries into a second plurality of code sections in Step 804 includes arranging each symbol to be offset from its respective code section start address. Then, a further step, Step 807b maintains a symbol offset address table cross-referencing symbol identifiers with corresponding offset addresses, and corresponding code section identifiers.

Arranging the first plurality of symbol libraries into a second plurality of code sections in Step 804 includes substeps. Step 804a arranges the code section address table in a first table code section, Step 804b arranges the symbol offset address table in a second table code section. Receiving an updated code section in Step 808 includes receiving an updated first table code section and an updated second table code section. Arranging the new code section with current code sections to form updated system software in Step 810 includes replacing the first table code section with the updated first table code section, and the second table code section with the updated second table code section. Executing the updated system software in Step 812 includes using the updated first table code section and updated second table code section in executing the updated system software.

In some aspects of the invention forming system software into a first plurality of symbol libraries in Step 802 includes forming a patch library, or patch symbol library. Arranging the first plurality of symbol libraries into a second plurality of code sections in Step 804 includes arranging a patch library into a patch manager code section. Arranging the new code section with current code sections to form updated system software for the wireless device includes substeps. Step 810a accesses the patch manager code section. Step 810b invokes the patch library to store the new code section. Invoking the patch library to store the new code section in Step 810b typically includes invoking the patch library to over-write the first code section with the new code section.

In some aspects, Step 808a, after receiving the new code section in Step 808, stores the new code section in a memory file system section. Arranging the new code section with current code sections to form updated system software in Step 810 includes invoking the patch library to over-write the first code section with the new code section stored in the memory file system section.

In other aspects of the invention, receiving a new code section in Step 808 includes receiving an updated patch manager code section. Arranging the new code section with current code sections to form updated system software in Step 810 includes replacing the patch manager code section with the updated patch manager code section. Executing the updated system software in Step 812 includes using the updated patch manager code in executing the updated system software.

Typically, Step 804 includes arranging read-write data, the code section address table, and the symbol offset address table in the patch manager code section. Then, receiving an updated patch manager code section in Step 808 includes receiving an updated symbol offset address table, an updated code section address table, and updated read-write data. In some aspects of the invention forming system software into a first plurality of symbol libraries in Step 802 includes forming a symbol accessor code, and arranging the first plurality of symbol libraries into a second plurality of code sections in Step 804 includes arranging the symbol accessor code in the patch manager code section. Then, a further step, Step 806a stores the symbol accessor code address at a first location in memory. Executing the updated system software in Step 812 includes substeps. Step 812a loads a third plurality of symbol libraries into read-write volatile memory, typically RAM. It should be understood that not all the symbol libraries in the patch manager code section are necessarily loaded in the read-write volatile memory. Further, symbol libraries in other code sections besides the patch manager code section can be loaded into the read-write volatile memory. Step 812b, in response to referencing the first location in memory, accesses the symbol accessor code. Step 812c invokes the symbol accessor code to calculate the address of a sought symbol using a corresponding symbol identifier. Invoking the symbol accessor code to calculate the address of the sought symbol includes accessing the code section address table and the symbol offset address table to calculate the address of the sought symbol. Step 812d accesses the third plurality of symbol libraries from RAM.

Typically, receiving an updated patch manager code section in Step 808 includes receiving an updated symbol accessor code. Replacing the patch manager code section with the updated patch manager code section in Step 810 includes replacing the symbol accessor code with updated symbol accessor code. Then, executing the updated system software in Step 812 includes using the updated symbol accessor code in executing the updated system software.

Some aspects of the invention include further steps. Step 808b receives an updated symbol accessor code address. Step 808c stores the updated symbol accessor code address in the file system section. Step 810c replaces the symbol accessor code address in the first location in memory with updated symbol accessor code address from the file system section. Then, executing the updated system software in Step 812 includes using the updated symbol accessor code address in executing the updated system software.

Typically, arranging the first plurality of symbol libraries into a second plurality of code sections in Step 804 includes arranging the symbol accessor code address in the patch manager code section. Then, replacing the symbol accessor code address in the first location in memory with updated symbol accessor code address from the file system section in Step 810c includes replacing the symbol accessor code address in the patch manager code section with the updated symbol accessor code address in an updated patch manager code section. In some aspects, Step 812a loads the read-write data, the code section address table, the symbol offset address table, the patch library, symbol accessor code, and a symbol accessor code address from the patch manager code section into read-write volatile memory. Step 812d accesses the read-write data, the code section address table, the symbol offset address table, patch library, the symbol accessor code, and the symbol accessor code address from the read-write volatile memory.

Storing the start of code sections at corresponding start addresses in Step 806 includes substeps. Step 806b creates a second plurality of contiguously addressed memory blocks. Step 806c identifies each memory block with a corresponding code section. Step 806d stores code sections in the identified memory blocks.

In some aspects; arranging the first plurality of symbol libraries into a second plurality of code sections in Step 804 includes arranging a third plurality of symbol libraries in a first code section. Identifying each memory block with a corresponding code section in Step 806c includes identifying a first memory block with the first code section. Storing code sections in the identified memory blocks in Step 806d includes storing the third plurality of symbol libraries in the first memory block. Receiving a new code section in Step 808 includes receiving an updated first code section with third plurality of symbol libraries arranged within. Then, arranging the new code section with current code sections to form updated system software for the wireless device in Step 810 includes overwriting the first code section in the first memory block with an updated first code section.

In other aspects, arranging the first plurality of symbol libraries into a second plurality of code sections in Step 804 includes arranging a first symbol library in a first code section. Identifying each memory block with a corresponding code section in Step 806c includes identifying a first memory block with the first code section. Storing code sections in the identified memory blocks in Step 806d includes storing the first symbol library in the first memory block Receiving a new code section in Step 808 includes receiving an updated first code section with first symbol library arranged within. Then, arranging the new code section with current code sections to form updated system software for the wireless device in Step 810 includes overwriting the first code section in the first memory block with an updated first code section.

Arranging the first plurality of symbol libraries into a second plurality of code sections in Step 804 includes sizing the code sections to accommodate arranged symbol libraries. Then, creating a second plurality of contiguously addressed memory blocks in Step 806b includes sizing memory blocks to accommodate corresponding code sections. Alternately, arranging the first plurality of symbol libraries into a second plurality of code sections in Step 804 includes sizing the code sections to accommodate sizes larger than the arranged symbol libraries.

A system and method have been provided for an updateable system software structure for use in a wireless communications device. The system is easily updateable because of the arrangement of symbol libraries in code sections, with tables to access the start addresses of the code sections in memory and the offset addresses of symbols in the symbol libraries. Although a few examples of these library arrangements and cross-referencing tables have been given for a display function, the present invention is not limited to just these examples. Other variations and embodiments of the invention will occur to those skilled in the art.