Abstract:
A wireless communication device includes a first storage unit, a second storage unit, an operating unit, and a control unit. The first storage unit further includes a plurality of separate storage areas corresponding to a plurality of program codes, respectively. The second storage unit is used to execute the plurality of program codes. The operating unit is configured to issue instructions to turn on power and to start up an application. The control unit is configured to load, on receipt of the instructions from the operating unit, at least one program code required to start up the application from the first storage unit into the second storage unit. The control unit is also configured to execute the at least one program code to start up the application. The at least one program code is included in the plurality of program codes.

Description:
BACKGROUND OF THE INVENTION  
       [0001]     1. Field of the Invention  
         [0002]     The present invention relates to a wireless communication device and a system startup method for this apparatus.  
         [0003]     Priority is claimed on Japanese Patent Application No. 2005-218647, filed Jul. 28, 2005, the contents of which are incorporated herein by reference.  
         [0004]     2. Description of the Related Art  
         [0005]     All patents, patent applications, patent publications, scientific articles, and the like, which will hereinafter be cited or identified in the present application, will hereby be incorporated by reference in their entirety in order to describe more fully the state of the art to which the present invention pertains.  
         [0006]     In wireless communication devices that have a wireless communication function such as, for example, mobile telephones, system programs and data and the like are stored in a ROM (read only memory) that generally uses a NOR flash memory. The NOR flash memory can accept for random accesses. An MPU (micro processing unit) is configured to directly read contents that are stored in the NOR flash memory and to execute commands or instructions and further to acquire data and the like. When this system is started up, it is normal for initialization processing to be performed in the sequence of hardware initialization, memory check and initialization, and then initialization of each module. After this initialization processing sequence has ended, the system changes to a wait screen and enters an application startup stand-by state. Because of this, increasing the size of the system program increases the time that is required for initialization, resulting in that the application startup also takes a considerable length of time. This applies considerable stress to a user when the user has turned on the power and wishes to execute an application immediately.  
         [0007]     Moreover, a flash memory having greater capacity and a lower price is being increasingly demanded for memory in order to store software and data and the like as the size of mobile telephone software, for example, system programs and applications, has increased. Consequently, the use of NAND flash memory instead of NOR flash memory is attractive. This NAND flash memory has the features of having large capacity and a low price, while also having fast access speeds and a small device size. Conversely, it has the defect of not allowing random access, and program codes and data cannot be used unless the contents of the NAND) flash memory are first loaded into RAM (random access memory). In addition, when the system is being started up, after the contents of the NAND flash memory have thus been loaded into RAM, the same initialization processing as is performed for NOR flash memory is performed. As a result, the problem arises that an even longer time is required for startup than when NOR flash memory is used.  
         [0008]     Because the scale of software has become even larger as mobile telephones have become funished with even greater functionality, shortening this system startup time has become an extremely pressing problem. For example, if the digital camera function of mobile telephones is considered, then it can be seen that the differentiation of functions between mobile telephones and modern digital cameras is gradually disappearing and the same startup time as is normal in modern digital cameras is demanded in mobile telephones. In order to solve such problems, a method is disclosed in Japanese Unexamined Patent Application, First Publication, No. 2000-322264 in which program code for various system programs and applications and the like is stored in storage areas in ROM that have been allocated for the respective program codes. Based on information tables that show the priority sequence when the relevant program code is being loaded, loading is performed in sequence starting from the program code that requires the fast response.  
         [0009]     However, when power is turned on, the user must determine this order of response, namely, which application is to be started up from among a plurality of applications, and this changes in accordance with the usage requirements of the user. In the conventional technology, the program code loading sequence, namely, which application is to be started up is fixed, so that there is little flexibility and the needs of the user are not satisfied. In view of the defects in a fixed system startup such as those in the conventional technology, the present invention provides a wireless communication device and a system startup method for this device that are highly usable and that enable applications required by a user to be given precedence during startup.  
         [0010]     In view of the above, it will be apparent to those skilled in the art from this disclosure that there exists a need for an improved device and/or method. This invention addresses this need in the art as well as other needs, which will become apparent to those skilled in the art from this disclosure.  
       SUMMARY OF THE INVENTION  
       [0011]     In accordance with a first aspect of the present invention, a wireless communication device may comprise a first storage unit, a second storage unit, an operating unit, and a control unit. The first storage unit may include a plurality of separate storage areas corresponding to a plurality of program codes, respectively. The second storage unit is used to execute the plurality of program codes. The operating unit can be configured to issue instructions to turn on power and to start up an application. The control unit can be configured to load, on receipt of the instructions from the operating unit, at least one program code required to start up the application from the first storage unit into the second storage unit. The control unit can also be configured to execute the at least one program code to start up the application. The at least one program code is included in the plurality of program codes.  
         [0012]     Preferably, when the control unit detects that the started application has ended, the control unit can load at least one unloaded program code from the first storage unit into the second storage unit. The at least one unloaded program code is included in the plurality of program codes.  
         [0013]     Preferably, the wireless communication device may further comprise a load detecting device that detects a load in the control unit. In this case, the control unit can also be configured to load at least one unloaded program code from the first storage unit into the second storage unit based on a load created by processing the started application. The at least one unloaded program code is included in the plurality of program codes. The at least one unloaded program code may comprise a program code that is required for wireless communication functions.  
         [0014]     In accordance with a second aspect of the present invention, a system startup method for a wireless communication device may comprise loading at least one program code into a storage unit, and executing the at least one program code as loaded to start up the application. The at least one program code can be loaded into the storage unit on receipt of instructions to turn on power and to start up an application. The at least one program code is required to start up the application. The storage unit is used to execute the at least one program code.  
         [0015]     Preferably, when the started application has ended, at least one unloaded program code can be loaded into the storage unit.  
         [0016]     Preferably, the at least one unloaded program code can be loaded into the storage unit, based on a load created by processing the started application.  
         [0017]     Preferably, the at least one unloaded program code may comprise a program code that is required for wireless communication functions.  
         [0018]     In accordance with the present invention, when turning on the power, priority can be given to first starting up an application desired by a user. As a result, the startup time is shortened and improved convenience can be achieved.  
         [0019]     These and other objects, features, aspects, and advantages of the present invention will become apparent to those skilled in the art from the following detailed descriptions taken in conjunction with the accompanying drawings, illustrating the embodiments of the present invention. 
     
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0020]     Referring now to the attached drawings which form a part of this original disclosure:  
         [0021]      FIG. 1  is a block diagram illustrating a configuration of a mobile communication terminal in accordance with an embodiment of the present invention;  
         [0022]      FIG. 2  is a view illustrating a configuration of program code areas for modules and applications of a ROM included in a wireless communication device of  FIG. 1  in accordance with the embodiment of the present invention;  
         [0023]      FIG. 3  is a view illustrating a configuration of program code areas in accordance with a comparative example;  
         [0024]      FIG. 4  is a view illustrating a typical example of a startup information table in accordance with the embodiment of the present invention;  
         [0025]      FIG. 5  is a flowchart illustrating an application startup processing flow after power is turned on in accordance with a comparative example;  
         [0026]      FIG. 6  is a flowchart illustrating an application startup processing flow after power is turned on in accordance with the embodiment of the present invention; and  
         [0027]      FIG. 7  is a flowchart illustrating another application startup processing flow after power is turned on in accordance with the modified embodiment of the present invention. 
     
    
     DETAILED DESCRIPTION OF THE INVENTION  
       [0028]     An embodiment of the present is described below with reference made to the drawings. Examples of wireless communication devices include mobile telephones, car navigation devices and personal computers (PC) that incorporate a wireless communication function, and personal digital assistants (PDA) and the like, however, in the present embodiment, a description is given using a mobile communication terminal as an example of a wireless communication device. Moreover, the mobile communication terminal illustrated in this description has various applications such as, for example, a wireless communication function, an email function, a digital camera function, and a digital broadcast reception function for television and radio and the like. Note that, in the description below, a comparison is made with an example in which the program code is split between a modern code area  71  that stores program code for drivers, UI, and communication related modules and the like and an application code area  72  that stores program code for other applications and is then stored in a first storage device, for example, ROM.  
         [0029]      FIG. 1  is a block diagram illustrating a configuration of a mobile communication terminal in accordance with an embodiment of the present invention. As is shown in the drawing, this mobile communication terminal is formed by a wireless communication unit  1 , a key input unit  2 , for example, an operating unit, a display unit  3 , a speaker unit  4 , a camera unit  5 , a control unit  6 , for example, a control device, ROM  7 ,for example, a first storage device, and RAM  8 , for example, a second storage device.  
         [0030]     The wireless communication unit  1  performs wireless communication with mobile communication base stations under the control of the control unit  6  using a predetermined communication format such as, for example, a code division multiple access (CDMA) format. The key input unit  2  is formed by a dial key, function keys, a power on key, and dedicated application startup keys. Operating information for these keys is output to the control unit  6  as operating signals. Note that the dedicated application startup keys instruct that power is turned on and that the relevant applications is started up, and are individually provided in accordance with the respective applications with which the mobile communication terminal is equipped. For example, a dedicated key corresponding to the startup of the digital camera function and a dedicated key corresponding to the startup of the digital broadcast reception function are provided. Note that it is also possible for application startup and power on to not be dedicated application startup keys but to be formed so as to double with other keys.  
         [0031]     The display unit  3  is, for example, a liquid crystal display or an organic EL display and displays various messages, telephone numbers, or images and the like based on display signals that are input from the control unit  6 . The speaker unit  4  outputs speech or sound to the outside based on audio signals that are input from the control unit  6 . The camera unit  5  is, for example, a charge coupled device (CCD) camera, and, under the control of the control unit  6 , outputs image signals of photographed images to the control unit  6 .  
         [0032]     The control unit  6  controls the overall operation of the mobile communication terminal based on a predetermined control program that has been stored in advance in the ROM  7 , on operating signals that are input from the key input unit  2 , and on the communication state of the wireless communication unit  1 . In addition, if the control unit  6  detects as part of a characteristic control processing that is based on the aforementioned control program that, when the power was OFF, one of the above described dedicated application startup keys has been pressed for a fixed time, then the power is turned ON and the program code of the application that corresponds to the pressed key as well as the program code of the module that is required to start up the relevant application are loaded into the ROM  7  from the RAM  8 , and the respective program codes that have been loaded are executed and the application is started up. Note that this application startup processing is described below in detail.  
         [0033]     The ROM  7  is, for example, NAND flash memory, and stores ahead of time control programs to be executed by the control unit  6 .  FIG. 2  is a view illustrating a configuration of program code areas for modules and applications of a ROM included in a wireless communication device of  FIG. 1  in accordance with the embodiment of the present invention. As is shown in  FIG. 2 , the ROM  7  independently stores in their respective individual storage areas the program code for control programs, namely, for “Boot”, “LCD Driver”, “EV-DO”, “1x”, “Browser”, “Camera”, and “Game”. Note that this “1x” indicates a cdma 2000 1x format, while “EV-DO” indicates a cdma2000 1x EV-DO format, which is an extension format of the cdma2000 1x format.  
         [0034]      FIG. 3  is a view illustrating a configuration of program code areas in accordance with a comparative example. The ROM  7  is divided into a modern code area  71  and an application code area  71 . The program code is stored in the ROM  7  in two separate areas, namely, the modern code area  71  and the application code area  72 . In the modern code area  7   1 , program codes for drivers, UT, communication related modules and the like are stored. In the application code area  72 , other program codes for other applications are stored. In this example, the program code inside the ROM  7  is divided into two code groups and it is not possible to load the program code of each module individually into the RAM  8 . Namely, because the program code of each module is a single block in the modern code area  71 , when the power is turned ON, the entirety of the program code in the modern code area  71  is loaded into the RAM  8 , and it is necessary to execute the relevant loaded program code and perform initialization processing. However, in the present embodiment, as is shown in  FIG. 2 , because the program codes are stored independently in respective individual storage areas in the ROM  7 , it is possible to load each module or application individually in the RAM  8 .  
         [0035]      FIG. 4  is a view illustrating a typical example of a startup information table in accordance with the embodiment of the present invention. Furthermore, the ROM  7  also stores a startup information table such as that shown in  FIG. 4  that shows the dedicated application startup keys, the applications that correspond to the relevant dedicated key, and the program code for the startup modules and applications that are required to start up that application. The RAM  8  is used as a working area that is used to execute the program code loaded from the ROM  7 .  
         [0036]     Next, a description will be given of the application startup processing when the power is turned on in the mobile communication terminal, specifically, the control unit  6 , which has the above described structure.  
         [0037]     Firstly, to provide a comparison, a description will be given of the application startup processing of an example in which, as is shown in  FIG. 3 , the program code is separated between a modern section and an application section and stored. Note that the mobile communication terminal in this example has different methods for storing program code as is shown in  FIG. 3 , and while no dedicated application startup key is provided, the remainder of the component elements are the same as those of the present embodiment.  
         [0038]      FIG. 5  is a flowchart illustrating an application startup processing flow after power is turned on in accordance with a comparative example. Firstly, if the power on key is pressed for a fixed time by a user, the control unit  6  determines that this is a command to turn on the power and turns on the power of the mobile communication terminal (step S 1 ). The control unit  6  then starts up a Boot loader; for example, the program that is executed first when the power is turned on and that loads all of the program code that is stored in the ROM  7  in the RAM  8  (step S 2 ). As a result of the Boot loader starting up, all of the program code that is stored in the ROM  7  is loaded into the RAM  8  (step S 3 ). The control unit  6  then performs system initialization processing (step S 4 ) and, once this initialization processing has ended, a wait screen is displayed on the display unit  3  (step S 5 ).  
         [0039]     Next, the control unit  6  determines whether or not an application start command has been made based on an operation of the key input unit by the user (step S 6 ). If the result of this determination is YES, namely, if an application start command has been made, the program code for that application that has been loaded into the RAM  8  is executed, and the relevant application is started up (step S 7 ). If, however, the result of the determination in step S 6  is NO, namely, if an application start command has not been made, the waiting state is maintained until a start command is received.  
         [0040]     In this manner, in the startup processing for an application that is performed when the power is turned on in the example shown in  FIG. 3 , because all of the program code that is stored in the ROM  7  is loaded into the RAM  8  and initialization processing is performed for the entire system, an extremely long time lapses before application startup preparations are complete.  
         [0041]     Based on this, a description will now be given using the flowchart shown in FIG.  6 .  FIG. 6  is a flowchart illustrating an application startup processing flow after power is turned on in accordance with the embodiment of the present invention. Firstly, if the power on key or a dedicated application startup key is pressed by a user for a fixed time, the control unit  6  determines that this is a power on command and the power of the mobile communication terminal is turned on (step S 10 ), and the Boot loader is started up (step S 11 ). The control unit  6  then determines the cause of the startup, for example, whether the power on key has been pressed or whether a dedicated application startup key has been pressed (step S 12 ).  
         [0042]     In this step S 12 , if it is determined that a dedicated application startup key has been pressed, for example, if the result of the determination is NO, the control unit  6  reads the startup information table (see  FIG. 4 ) that is stored in the ROM  7  (step S 13 ), and, based on this startup information table, determines the application that corresponds to this dedicated application startup key that has been pressed by the user and also the modules that are required for the startup of the relevant application (step S 14 ). The program code for the modules required for application startup is then loaded from the ROM  7  into the RAM  8  (step S 15 ).  
         [0043]     Next, the control unit  6  executes the program code of the modules that are required for the application startup which has been loaded into the RAM  8 , and performs the initialization processing that is required for the application startup (step S 16 ). When the initialization processing that is required for the application startup has ended, the control unit  6  loads the program code for the application from the ROM  7  into the RAM  8 , executes the program code of the relevant application and starts up the application that has been commanded by the user (step S 17 ).  
         [0044]     The control unit  6  then executes the application in accordance with the operation of the key input unit  2  by the user (step S 18 ), and determines whether or not there has been a command from the user to end the application via an operation of the key input unit  2  (step S 19 ). If the result of the determination in step S 19  is NO, namely, if there is no command to end the application, the routine returns to the processing of step S 18 . If, however, the result of the determination in step S 19  is YES, namely, if there is a command to end the application, the control unit  6  ends the application (step S 20 ), loads all of the program code of the unloaded modules from the ROM  7  into the RAM  8  (step S 21 ), executes all of the program code of these unloaded modules, and performs initialization processing for any uninitialized modules (step  822 ). When the initialization processing for the uninitialized modules has ended, the control unit  6  causes the wait screen to be displayed on the display unit  3 , and enters a waiting state (step S 23 ). Note that the “unloaded modules” referred to here indicates programs that relate to wireless communication functions in order for the device to operate as a conventional communication device. If, however, in step S 12 , it is determined that the cause of the startup was simply the fact that the power on key was pressed, namely, only the power was turned on, for example, if the result of the determination in step S 12  is YES, then the control unit  6  proceeds to the processing of step S 21 .  
         [0045]     As described above, in accordance with this mobile communication terminal, by pressing a dedicated application startup key when turning on the power, priority is given to first loading the modules, for example, program codes that are required for the application desired by the user. As a result, the startup time is shortened and the improved convenience can be achieved.  
         [0046]     As is described above, in the present embodiment, when a command is received to start up an application or to turn on the power of a device, precedence is given to loading program code that is required for the commanded application over program code that is required for wireless communication functions in order for the device to operate conventionally as a wireless communication device.  
         [0047]     Note that the present invention is not limited to the above described embodiment and modified examples such as those described below, for example, can be considered.  
         [0048]     In the above described embodiment, a description is given of when a mobile communication terminal is used as a wireless communication device, however, the present invention is not limited to this.  
         [0049]      FIG. 7  is a flowchart illustrating another application startup processing flow after power is turned on in accordance with the modified embodiment of the present invention. In the above described embodiment, in step S 19  shown in  FIG. 6 , a determination is made as to whether or not an end application command has been received from a user via the operation of the key input unit  2 . However, as shown in  FIG. 7 , the process of step S 24  can be performed instead of the above-described processes of steps S 19  and S 20  shown in  FIG. 6 . The control unit  6  determines whether or not it is in a low load state for a fixed period of time, and if it is in a low load state, to then load all of the program code of the unloaded modules from the ROM  7  into the RAM  8 . In this case, a program, for example, a load detecting device to detect the load state of the control unit  6  is stored in the ROM  7  and the load state of the control unit  8  is monitored as a result of this program being executed.  
         [0050]     While preferred embodiments of the invention have been described and illustrated above, it should be understood that these are exemplary of the invention and are not to be considered as limiting. Additions, omissions, substitutions, and other modifications can be made without departing from the spirit or scope of the present invention. Accordingly, the invention is not to be considered as limited by the foregoing description and is only limited by the scope of the appended claims,