[go: up one dir, main page]

WO2000074412A1 - Procede et appareil de telechargement dans un equipement terminal radioelectrique - Google Patents

Procede et appareil de telechargement dans un equipement terminal radioelectrique Download PDF

Info

Publication number
WO2000074412A1
WO2000074412A1 PCT/SE2000/001015 SE0001015W WO0074412A1 WO 2000074412 A1 WO2000074412 A1 WO 2000074412A1 SE 0001015 W SE0001015 W SE 0001015W WO 0074412 A1 WO0074412 A1 WO 0074412A1
Authority
WO
WIPO (PCT)
Prior art keywords
software
version
radio terminal
current version
capability
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/SE2000/001015
Other languages
English (en)
Inventor
Hans Hall
Michael Eriksson
Gunnar Forsgren
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Priority to AU49688/00A priority Critical patent/AU4968800A/en
Priority to DE10084626T priority patent/DE10084626T1/de
Priority to JP2001500583A priority patent/JP2003501907A/ja
Publication of WO2000074412A1 publication Critical patent/WO2000074412A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1415—Saving, restoring, recovering or retrying at system level
    • G06F11/1433—Saving, restoring, recovering or retrying at system level during software upgrading
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/72406—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by software upgrading or downloading
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H04W8/245—Transfer of terminal data from a network towards a terminal

Definitions

  • the invention is concerned with a method and apparatus of downloading software into a radio terminal, e.g. a mobile phone, and more particularly it is concerned with remotely upgrading of software.
  • Radio terminals are typically programmed with two pieces of the software, a first piece is hard coded in a programmable read only memory (PROM) and a second, upgradable piece is loaded into flash Programmable Read Only Memory (flash- PROM).
  • PROM programmable read only memory
  • flash- PROM flash Programmable Read Only Memory
  • the cellular telephone of this document includes two memories for storing software with one memory storing the current software and the second memory available for downloading new software.
  • the cellular telephone also includes a controller for loading the received software into the cellular telephone and for performing a checksum on the new software to control the process for downloading the new software into the phone. If the calculated checksum does not match the transmitted checksum, a retransmission of the new software is carried out.
  • the radio terminal In some situations it is extremely important that the radio terminal, especially if it is a mobile phone, is functioning, e.g. in situations of emergency calls fort the user's security.
  • the software therefore has to be very robust.
  • the so t jajg) ⁇ downloaded over a wireless or other network, and updated in the radio terminal, it is possible that a new version contains bugs and will perhaps not start properly or even not start at all. This might be the case when the software is written by a third party.
  • the software could be quite advanced, so it could be hard to tell, from a programmer's view, when the application really has been started, even if a checksum process for the downloading process itself has been carried out.
  • the checksum only controls if the program sent from the server still is in the same form when received by the radio terminal. If the program has bugs at the server, the same bugs are transferred to the radio terminal.
  • One object of the invention is a method and apparatus with which the user always knows if the current software in the radio terminal is functioning.
  • Another object of the invention is a method and apparatus of downloading and installing software into the radio terminal in such a way that the above object is fulfilled.
  • the method of the invention is therefore mainly characterized in that the capability of functioning of the current version of the software in the radio terminal is determined.
  • a possible existence of a new version of the software is then notified before or after said determination.
  • another version is selected to be downloaded. If according to said determination, the current version of the software does not work, another version of the software will be downloaded.
  • the current version of the software is preferably stored if it is a working version accordingl#. ⁇ S _ determination.
  • the selected version of the software is downloaded into the radio terminal to be the current version if there according to said determination or said notifying is a reason thereto.
  • the capability of functioning of the version of the software is then tested.
  • the current version might be the one which was in the terminal in the beginning, when the terminal was turned on, it can be another version or it can be a new version.
  • the result of said test is indicated in such a form that the capability of functioning of said tested version of the software can be determined.
  • the invention also covers the methods, wherein the step of notifying the existence of a new version is excluded as well as methods wherein this step is a necessary step.
  • One version can alternatively also be tested more than once, before another version is installed.
  • the apparatus of the invention is mainly characterized by means for determination the capability of functioning of the current version of the software in the radio terminal, notifying a possible existence of a new version of the software, selecting another version of software to be downloaded to replace the current version, storing the current version of the software, downloading another version of the software into the radio terminal to be the current version, testing the capability of functioning of the actual current version of the software, and of indicating the result of said test in such a form that the capability of functioning of said tested version of the software can be determined.
  • downloading means both remotely downloading and installing and reinstalling and reloading from another memory.
  • current version means the active version of software in the terminal. The other versions stored are inactive. It is pointed out that when a new version is available it is not necessary to download it immediately. If it is downloaded it is not necessary to start it immediately and it can be done later on, for example the next time the terminal is turned on.
  • the new version of the software can be a later version qfK g. software, a better version or an improved version. The idea is that the possible existence of a "new" version is notified so that it would be possible to download some version wished which is not already stored in the terminal.
  • the first thing that preferably is done is to determine if the current version of the software is functioning.
  • the determination can be done by identifying the presence or absence of an indicator that shows the software situation, and has been inserted in the terminal.
  • the indicator can be the result of said test, which is indicated by the presence or absence of a special indicator that can be handled by an object in the program.
  • the sign can be a persistent object. If the object exists, it is known that the previous boot for downloading a new version of the software or the installing of another version failed. Such an embodiment is also possible, wherein the absence of the sign means that the current version does not work. A version that is supposed to work is then installed and the method can be repeated immediately or later until the result of the test shows that the current version of the terminal is working. The method can also be repeated the next time the radio terminal is turned on, preferably each time the terminal is turned on.
  • Said other version of the software can be an earlier stored older version, preferably the foregoing version used.
  • the number of versions to be stored is selected by deleting one or more of the older versions, preferably according as new versions are installed.
  • Said other version selected to be downloaded can be a new version of the software if such a new version exist according to said notifying.
  • the other version of the software selected to be downloaded is an earlier stored older version, if the current active version is not working according to said determination and if there is no new version or the new version is not wished to be installed. If the persistent object exists when the system is booted up (or in the alternative embodiment, does not exist), it is a sign of that something went wrong the last time. As explained above, a working version is then installed to be the current version or the version is tested at least once more.
  • said other version of the software to be installed as the current version can be a basic version stored in ROM or can be downloaded from the manufacturer's server if none of the stored older versions or the current version works. In some embodiments, there might be an option that the basic version can always be installed, if wished.
  • the result of said test is indicated by the presence or absence of a special indicator to show the software situation in the mobile phone by means of which indication the capability of functioning of the current version of the software in the mobile phone is notified.
  • the indicator is removed, when according to the test, a working version of the software has been started.
  • said indicator is updated every time the functionality test is carried out to show the number of tests performed or to identify the current version of the software.
  • the other version of software selected to be downloaded can be selected on the basis of the updated indicator. If the indicator for example shows that the test has been carried out many times, it may be advisable to reload a basic version of the software.
  • the existing object is updated to give information of number of tests performed, of the actual version of the software etc. It can be decided in forward how many times a program shall be tested before another or a basio version shall be installed. If the indicator shows up more thaii ⁇ -ft ⁇ , it usually indicates that something else is wrong and in that case it might be preferable to install the basic first version mentioned above already in this stage. Something might for example have gone wrong when the program was stored in the memory. In case of a third party code, another program might have destroyed the actual version. The copying of files in the radio terminal is a further possible reason. It can therefore also be advisable to test the same program more than once before installing an earlier version or the basic version.
  • Said special indicator can be made in such a form that the actual version of the software can be identified and it can be in form of an ordinary file.
  • Each checkpoint can for example be a critical point per thread in the software or per terminal resource in the software that has to be passed.
  • a resource can be a network, a file system, sound, etc. Other alternatives are also possible and they are chosen depending on the program.
  • a checkpoint counter can be used for counting the checkpoints passed, the number of passed checkpoints can be checked, and the special sign can be deleted or updated if the number of checkpoints in the counter is equal to the number of checkpoints to be passed.
  • the current version can be stored by packing it with a compressing program to reduce the amount of space required on the phone, for example the zip program.
  • the problem with knowing whether a new version of the software has successfully started is thus solved in the invention by having an indicator, that either exists or not, depending on the functionality of the software.
  • the indicator will be deleted if the new version has started or in an alternative embodiment, is retained if the new version has started.
  • the radio terminal of the invention can be a computer or a mobile phone or the like.
  • Figure 1 illustrates a schematic view of an apparatus for downloading software into a radio terminal
  • FIG. 2 is a general flow scheme of the invention.
  • Figure 3 is a flow scheme of two examples of a procedure in accordance with the invention.
  • Figure 4 is a more detailed example of an embodiment of the invention.
  • Figure 5 is a detailed example of steps 5,8 and 9 of figure 2
  • FIG 1 there is illustrated an example of an apparatus for remotely downloading software into a radio terminal 10.
  • An update server processor 11 communicates with a network 12, which has a wireless communication link 13 to the radio terminal 10.
  • New versions of software are sent from the update server processor 11 via the network 12 and the wireless communication link 13 to the. radio terminal 10 through the antenna 14.
  • the terminal 10 in figure 1 contains a transceiver 15, a controller 16, a first memory 17 and a second memory 18.
  • the downloading of software from the update server 11 to the radio terminal 10 is carried out through the antenna 14 via the controller 15 to one of the memories.
  • the update server processor 11 can transmit a message to the radio terminal 10 under control of controller 16, which can either choose to download the new version or not in accordance with the invfefttft_ ⁇ 2
  • controller 16 can either choose to download the new version or not in accordance with the invfefttft_ ⁇ 2
  • the availability of new versions of software can also be known for the radio terminal 10 so that the radio terminal 10 ask the update server 11 about the existence of a new version.
  • the downloading itself is usually carried out by means of messages between server processor 11 and radio terminal 10.
  • the update processor 11 can also send older versions of the software to the radio terminal 10 in accordance with the invention.
  • a checkpoint counter can be used for counting the checkpoints passed, the number of passed checkpoints can be checked, and a special indicator can be created, deleted or updated in dependence of the number of checkpoints in the counter being equal to the number of checkpoints to be passed.
  • FIG 2 there is presented a detailed embodiment of the invention by means of a flow scheme.
  • One way of proceeding in the invention is by following the unbroken arrows. Alternative ways of proceeding are indicated with dotted arrows.
  • the alternatives can be selected in accordance with predefined criteria.
  • the method is carried out each time the terminal is turned on in accordance with reference number 1.
  • the first thing to do is to check if the current version of the software is a working version as indicated with step 2 in the figure.
  • This determination is in accordance with figure 1 carried out by means of the indication of a test result, the test having been carried out in accordance with step 8 and the indication in accordance with step 9 explained below.
  • the changing of information between the indication of the test result of step 9 and the checking of step 2 is indicated with a two-way arrow 3.
  • the indication of the test result can be performed in many ways. It can be a sign in form of a persistent object that is an ordinary file.
  • Step 4a can now be carried out, according to which another version that is supposed to work is installed. This version might be an earlier stored working version of the software or it can even be a basic version stored in ROM or it can even be downloaded from the server of the manufacturer. If the current version appears not to work, it can also be tested once more in steps 8 and 9. This alternative way is presented with a dotted arrow in the figure.
  • step 9 If the current version in accordance with the test result presentation of step 9 is a working version considered in step 2, then, it is in step 4b of figure 2 checked if there is a new version existing.
  • the alternative of not checking for a new version is indicated with a dotted arrow, and in that case the current version is started as indicated in step 5.
  • the capability of functioning of the current version is tested as indicated in step 8 when the software is started in accordance with checkpoints set in the program.
  • the first step in the invention is to download the new version, which then is started and tested and the test result is indicated as is described.
  • step 8 If there is no new* version (or it is not downloaded), the current version is started as indicated in step 5, and tested, as indicated in step 8.
  • step 6 If there is a new version, the current version is in figure 2 stored in step 6 and the new version is downloaded in step 7.
  • a functionality test is performed in connection with starting up as indicated in steps 5 and 8.
  • the capability of functioning of the downloaded or installed version of the software is tested as indicated in step 8 by setting a number of checkpoints the software should pass to start up correctly as a working version.
  • a checkpoint counter can be used for counting the checkpoints passed, the number of passed checkpoints can be checked, and the special sign can be deleted or updated if the number of checkpoints in the counter is equal to the number of checkpoints to be passed.
  • step 9 The result of the test is indicated in step 9 in such a form that the capability of functioning of a current version of the software always can be determined. Therefore, the result of said test is indicated by the presence or absence of a special indicator or sign to show the software situation in the terminal by means of which indication the capability of functioning of the current version of the software in the terminal is notified.
  • a new downloaded version or an installed version is tested in step 8 in connection with the starting of the program. There are, however, checkpoints embedded, and if these checkpoints are not passed, it shall appear in the presentation of the test result.
  • Figure 3 is a detailed flow scheme of two examples of how the method of the invention might proceed. It has to be pointed out that the downloading procedure depends on how the software in the terminal works and on the availability of new versions why the example is not intended to restrict the invention in anyway, but is shown for illustrating purposes only.
  • the terminal is turned on in accordance with reference number 100.
  • the' indication of the test result is performed in form of a persistent object, the existence of which shows that the current version of the software in the terminal is not working.
  • step 200 shows in the first example shown in figure 3 that the object exists, which means that something went wrong in the previous boot of the software.
  • Step 400 al can now be carried out, according to which another version that is supposed to work is installed.
  • This version might be an earlier stored working Ve_ftt ⁇ 0 of the software or it can even be a basic version stored in ROM or it can even be downloaded from the server of the manufacturer.
  • the downloaded version is started in step 500 whereby a new persistent object is created.
  • step 800:2 the downloaded version is tested and, since the test is passed, the persistent object is deleted in step 900:2.
  • step 200 the absence of a persistent object in the second example causes the program to execute step 400 b, whereby it is now checked if there is a new version existing. Since there is a new version, the current version is stored in step 600 and the new version is stored in step 700 to be the current version. The new version is started in step 800:1 hereby a persistent object is created and a number of checkpoints to be passed is set. In step 900:1, the new version is tested. As this version did not start up correctly, actions are taken in step 400:a2 to remedy the fault by for example by going to step 400al and by proceeding as was explained in the first example.
  • the user of the terminal may conclude, from an improper program behaviour, that something is wrong and restart the terminal by first turning it off and immediately thereafter turning it on again which effectively means to turn to step 100.
  • the program execution is terminated and control is handed over to the kernel whereby the number of passed checkpoints may be checked. Automatic actions may then be executed in response to a mismatch between the preset counter value and the number of passed checkpoints.
  • a low level interrupt in step 800, whereby the kernel may detect that the program execution has stopped or entered into a loop.
  • the kernel may then, in step 400 :a2, execute automatic actions to remedy the fault, e.g. restart the program execution from step 200.
  • the kernel can take control, the automatic actions in case of a faulty program can be varied.
  • the kernel may indicate to the user that a program error has been detected but that certain functions will be allowed.
  • the user may, e.g., be allowed to manage a local calendar whereas a network connection may not be allowed.
  • the kernel may determine which functions of the program that are working from an analysis of data compiled from the checkpoints having been passed.
  • figure 4 there is shown a detailed example of an embodiment of the invention.
  • the different steps corresponding to the steps of figure 2 have been indicated with corresponding reference numbers as in figure 2, except that in this embodiment, the upper indexes ' and " and "' is used to indicate this special embodiment.
  • Lower indexes a, b, c have been used to indicate alternative ways.
  • the different steps in themselves have been earlier explained in the text, and the intention with this figure is to show an example of an implementation of the invention.
  • the terminal is turned on in step 1 ' .
  • the existence of a new version is notified in step 4b'. If there is a new version, the current version is moved in step 6'. (If the current version is a working version it is stored, otherwise it is deleted).
  • the new version is loaded in step T and started in step 5a'. In connection with the starting there is created an object in step 9b' to indicate passing of the test performed in step 8'. The passing of the test is notified in step 2b' .
  • a restart according to step lb' is carried out if the test is not passed. In that case the capability of functioning of the current version is notified in step 2'.
  • step 2 if an object exist, it is notified in step 2" if this is the second try of booting the software. (This can be notified by updating the object in such a way in every test not being passed).
  • a basic version is reloaded in step 4a' , if in step 2" , it was notified that this was the second try of booting.
  • step 2 If step 2" showed that this was not the second try, it is notified in step 2'", if an old current version exists e.g. as indicated by the second memory 18 in figure 1 being loaded. This can be notified for example with creating an own object for this purpose. If this is the case, the old version is reloaded in step 4" and started and tested in step 5c' also comprising the creation of a new object. The passing of the test is notified in step 2c'. If the test is passed, the object is deleted in step 9d' and the current software version can be used.
  • step 2c' If it was notified in step 2c', that the test was not passed, the current object is updated in step 9e' to indicate in a subsequent execution of step 2", a second try. A restart, manual or automatical, is thereafter carried out in step lb'. If according to step 2'", there is no older working version, the basic version is reloaded in step 4a'. Program execution then. proceeds from steps 5b', 9b' by testing the reloaded basic version.
  • step 2' If according to step 2', there is no object, it means that the current version is working and it is starte " d in steps 5b'.
  • An object is created in step 9a', which is deleted in step 9c' if the test according to step 8a' is passed, after which the program is ready for use.
  • step lb' If the test is not passed in step 2a', a restart is carried out in step lb'.
  • step 4b' If there is no new version of software available according to step 4b', the next step is 2', which is explained above.
  • Figure 5 is a detailed example of a functionality test performed for the current software in the terminal in connection with the starting in step 5.
  • An object 52 is created in step 51 A.
  • the functionality of the version of the software is tested by setting a number of checkpoints Cl, C2, C3 called checkpoint 1, checkpoint 2 and checkpoint 3 in figure 5, the software should pass to start up correctly as a working version.
  • the number of checkpoints to be passed is defined in step 5 IB and stored in step 53 in the object 52.
  • the number of checkpoints can vary, but for illustrative purposes, there are three indicated in figure 5.
  • the number of checkpoints is contained in the program and copied to the object 52 at an early, phase of program execution.
  • Each checkpoint can for example be a critical point per thread in the software that has to be passed. In figure 5, only one thread is described. Other alternatives are also possible and they are chosen depending on the program.
  • a checkpoint counter 54 can be used in the object for counting the checkpoints passed, and each time a checkpoint is passed, the counter number is increased by one. In figure 5, there has been illustrated the case, wherein all three checkpoints has been passed.
  • the number of checkpoints passed is compared to the defined amount in step 55, and if the number of checkpoints defined in the object is equal to the number of checkpoints passed according to the counter, the test is passed as indicated by ⁇ tep'96' and the software is ready for use. If the number defined in the object is not equal to the number of checkpoints passed, in this embodiment, the old object is updated in step 57 or a new object is created.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Stored Programmes (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Information Transfer Between Computers (AREA)
  • Telephonic Communication Services (AREA)

Abstract

L'invention concerne un procédé de téléchargement de logiciel dans un équipement terminal radioélectrique possédant au moins deux exemplaire du logiciel, dont un est exploité comme la version courante. La capacité de fonctionnement de la version courante du logiciel de l'équipement terminal radioélectrique est déterminée lorsque le terminal est mis en marche. Une autre version du logiciel est téléchargée si l'existence d'une nouvelle version est signalée ou si la version courante ne fonctionne pas. Si la version courante fonctionne, elle est stockée avant le téléchargement d'une nouvelle version. La capacité de fonctionnement d'une version courante du logiciel est testée avant utilisation. Le résultat du test est présenté sous une forme permettant de déterminer la capacité de fonctionnement de la version testée du logiciel. L'invention porte également sur un équipement terminal radioélectrique comprenant un moyen permettant la mise en oeuvre du procédé de l'invention.
PCT/SE2000/001015 1999-05-26 2000-05-19 Procede et appareil de telechargement dans un equipement terminal radioelectrique Ceased WO2000074412A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
AU49688/00A AU4968800A (en) 1999-05-26 2000-05-19 Method and apparatus of downloading into a radio terminal
DE10084626T DE10084626T1 (de) 1999-05-26 2000-05-19 Verfahren und Anordnung zum Downloaden in ein Funkendgerät
JP2001500583A JP2003501907A (ja) 1999-05-26 2000-05-19 無線端末へのダウンロード方法及び装置

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
SE9901904-4 1999-05-26
SE9901904A SE516806C2 (sv) 1999-05-26 1999-05-26 Sätt för inladdning av programvara i en radioterminal, såsom en mobiltelefon, och tillhörande radioterminal

Publications (1)

Publication Number Publication Date
WO2000074412A1 true WO2000074412A1 (fr) 2000-12-07

Family

ID=20415736

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2000/001015 Ceased WO2000074412A1 (fr) 1999-05-26 2000-05-19 Procede et appareil de telechargement dans un equipement terminal radioelectrique

Country Status (6)

Country Link
JP (1) JP2003501907A (fr)
CN (1) CN1147190C (fr)
AU (1) AU4968800A (fr)
DE (1) DE10084626T1 (fr)
SE (1) SE516806C2 (fr)
WO (1) WO2000074412A1 (fr)

Cited By (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001067785A3 (fr) * 2000-03-04 2001-12-27 Motorola Inc Architecture de systeme de communication et procede pour commander le telechargement de donnees vers des equipements d'abonnes
WO2002063903A3 (fr) * 2000-12-21 2002-11-21 Nokia Corp Procede et appareil de gestion d'applications et de donnees dans un dispositif mobile
EP1253793A3 (fr) * 2001-04-27 2003-03-19 Siemens Information and Communication Networks S.p.A. Système de communication à interface configurable pour une unité périphérique et procédé de configuration de cette interface
EP1235447A3 (fr) * 2001-02-26 2003-04-23 Kabushiki Kaisha Toshiba Appareil de communication radio et sa procédé de qualification
EP1217856A3 (fr) * 2000-12-20 2003-05-02 Telecom Italia Lab S.p.A. Appareil pour la sélection aléatoire d'opérateur de téléphonie mobile et procédure pour téléphones cellulaires
GB2388497A (en) * 2002-03-27 2003-11-12 Nec Corp Mobile communication terminal able to download and store additional dictionaries for temporary or permanent use
WO2003010663A3 (fr) * 2001-07-26 2003-12-24 Kyocera Wireless Corp Systeme et procede pour la gestion de telechargement de logiciel systeme de dispositif de communications sans fil, en conditions d'exploitation
EP1395074A1 (fr) * 2002-08-30 2004-03-03 Siemens Aktiengesellschaft Méthode de fonctionnement d'un terminal dans un système de communication par radio, système de communication par radio, terminal et unité de confirmation dans un système de communication par radio
US6918108B2 (en) 2001-07-26 2005-07-12 Kyocera Wireless Corp. System and method for field diagnosis of wireless communications device system software
EP1560446A1 (fr) * 2004-01-27 2005-08-03 Research In Motion Limited Procédé et dispositif pour actualiser une mémoire non-volatile sur un dispositif sans fil en vérifiant et comparant un élément d'identification spécifique mémorisé dans cette mémoire avec une identification de logiciel
EP1560447A1 (fr) * 2004-01-27 2005-08-03 Research In Motion Limited Procédé et dispositif pour actualiser une mémoire non-volatile sur un dispositif sans fil en vérifiant et comparant un élément d'identification spécifique mémorisé dans cette mémoire avec une identification de logiciel
US6961537B2 (en) 2001-08-10 2005-11-01 Kyocera Wireless Corp. System and method for peer-to-peer handset communication
US7027806B2 (en) 2001-07-26 2006-04-11 Kyocera Wireless, Corp. System and method for field downloading a wireless communications device software code section
GB2425193A (en) * 2005-04-14 2006-10-18 Nec Technologies Method for updating the software in a processor unit
US7159214B2 (en) 2001-07-26 2007-01-02 Kyocera Wireless Corp. System and method for compacting field upgradeable wireless communication device software code sections
US7184759B2 (en) 2001-07-26 2007-02-27 Kyocera Wireless Corp. Modular software components for wireless communication devices
US7184793B2 (en) 2001-07-26 2007-02-27 Kyocera Wireless Corp. System and method for over the air area code update
US7197302B2 (en) 2001-07-26 2007-03-27 Kyocera Wireless Corp. System and method for interchangeable modular hardware components for wireless communication devices
US7200389B2 (en) 2001-07-26 2007-04-03 Kyocera Wireless Corp. Dynamic interface software for wireless communication devices
US7222340B2 (en) 2004-01-27 2007-05-22 Research In Motion Limited Software-delivered dynamic persistent data
US7254386B2 (en) 2001-08-10 2007-08-07 Kyocera Wireless Corp. System and method for improved security in handset reprovisioning and reprogramming
US7328007B2 (en) 2001-07-26 2008-02-05 Kyocera Wireless Corp. System and method for organizing wireless communication device system software
US7359698B2 (en) 2003-09-08 2008-04-15 Kyocera Wireless Corp. Systems and methods for enhanced over-the-air programming
US7386846B2 (en) 2001-07-26 2008-06-10 Kyocera Wireless Corp. System and method for the management of wireless communications device system software downloads in the field
US7743115B2 (en) * 2002-02-27 2010-06-22 Motorola, Inc. Software content downloading methods in radio communication networks
US8418162B2 (en) 2004-01-27 2013-04-09 Research In Motion Limited Network delivered dynamic persistent data
JP2016219033A (ja) * 2001-04-03 2016-12-22 クゥアルコム・インコーポレイテッドＱｕａｌｃｏｍｍ Ｉｎｃｏｒｐｏｒａｔｅｄ 無線ネットワークにわたってネットワークが開始するアプリケーションプログラムのアンインストール方法および装置
US9554268B2 (en) 2001-07-26 2017-01-24 Kyocera Corporation System and method for updating persistent data in a wireless communications device

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4459905B2 (ja) * 2003-12-22 2010-04-28 テレフオンアクチーボラゲット エル エム エリクソン（パブル） 無線機器の無線伝送によるソフトウェアのダウンロードと更新
WO2006000122A1 (fr) * 2004-06-23 2006-01-05 Zte Corporation Procede de mise en concordance de version sur systeme de communications mobiles
JP2008299709A (ja) * 2007-06-01 2008-12-11 Nec Corp ファームウェア更新システム、ネットワーク接続機器、ファームウェア更新方法及びプログラム
CN102014419A (zh) * 2009-09-09 2011-04-13 苏州工业园区科升通讯有限公司 采用终端手机进行2g与3g网络测试的方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5155837A (en) * 1989-03-02 1992-10-13 Bell Communications Research, Inc. Methods and apparatus for software retrofitting
EP0767426A1 (fr) * 1995-10-05 1997-04-09 Siemens Aktiengesellschaft Procédé pour la programmation d'un appareil
WO1997016938A1 (fr) * 1995-10-30 1997-05-09 Nokia Telecommunications Oy Amelioration du logiciel pour telephones mobiles
DE19741703A1 (de) * 1997-09-22 1999-04-01 Siemens Ag Verfahren zum Laden von Betriebssoftware sowie Mobiltelefon hierfür
US5956481A (en) * 1997-02-06 1999-09-21 Microsoft Corporation Method and apparatus for protecting data files on a computer from virus infection

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5155837A (en) * 1989-03-02 1992-10-13 Bell Communications Research, Inc. Methods and apparatus for software retrofitting
EP0767426A1 (fr) * 1995-10-05 1997-04-09 Siemens Aktiengesellschaft Procédé pour la programmation d'un appareil
WO1997016938A1 (fr) * 1995-10-30 1997-05-09 Nokia Telecommunications Oy Amelioration du logiciel pour telephones mobiles
US5956481A (en) * 1997-02-06 1999-09-21 Microsoft Corporation Method and apparatus for protecting data files on a computer from virus infection
DE19741703A1 (de) * 1997-09-22 1999-04-01 Siemens Ag Verfahren zum Laden von Betriebssoftware sowie Mobiltelefon hierfür

Cited By (41)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001067785A3 (fr) * 2000-03-04 2001-12-27 Motorola Inc Architecture de systeme de communication et procede pour commander le telechargement de donnees vers des equipements d'abonnes
GB2359908B (en) * 2000-03-04 2004-09-15 Motorola Inc Communication system architecture and method of controlling data download to subscriber equipment
EP1217856A3 (fr) * 2000-12-20 2003-05-02 Telecom Italia Lab S.p.A. Appareil pour la sélection aléatoire d'opérateur de téléphonie mobile et procédure pour téléphones cellulaires
WO2002063903A3 (fr) * 2000-12-21 2002-11-21 Nokia Corp Procede et appareil de gestion d'applications et de donnees dans un dispositif mobile
EP1235447A3 (fr) * 2001-02-26 2003-04-23 Kabushiki Kaisha Toshiba Appareil de communication radio et sa procédé de qualification
JP2016219033A (ja) * 2001-04-03 2016-12-22 クゥアルコム・インコーポレイテッドＱｕａｌｃｏｍｍ Ｉｎｃｏｒｐｏｒａｔｅｄ 無線ネットワークにわたってネットワークが開始するアプリケーションプログラムのアンインストール方法および装置
EP1253793A3 (fr) * 2001-04-27 2003-03-19 Siemens Information and Communication Networks S.p.A. Système de communication à interface configurable pour une unité périphérique et procédé de configuration de cette interface
WO2003010663A3 (fr) * 2001-07-26 2003-12-24 Kyocera Wireless Corp Systeme et procede pour la gestion de telechargement de logiciel systeme de dispositif de communications sans fil, en conditions d'exploitation
US7386846B2 (en) 2001-07-26 2008-06-10 Kyocera Wireless Corp. System and method for the management of wireless communications device system software downloads in the field
WO2003012639A3 (fr) * 2001-07-26 2003-12-24 Kyocera Wireless Corp Systeme et procede permettant de compacter des parties de code d'un logiciel de dispositif de communication sans fil presentant une possibilite d'extension en clientele
WO2003010664A3 (fr) * 2001-07-26 2003-12-24 Kyocera Wireless Corp Systeme et procede permettant de mettre a jour des donnes persistantes dans un dispositif de communications sans fil
KR100913658B1 (ko) * 2001-07-26 2009-08-24 키오세라 와이어리스 코포레이션 현장 업그레이드형 무선 통신 장치 소프트웨어 코드 섹션치밀화 시스템 및 방법
US7200389B2 (en) 2001-07-26 2007-04-03 Kyocera Wireless Corp. Dynamic interface software for wireless communication devices
US6918108B2 (en) 2001-07-26 2005-07-12 Kyocera Wireless Corp. System and method for field diagnosis of wireless communications device system software
US7542758B2 (en) 2001-07-26 2009-06-02 Kyocera Wireless Corp. Field downloading of wireless device software
EP1973035A1 (fr) * 2001-07-26 2008-09-24 Kyocera Wireless Corp. Système et procédé pour la gestion du dispositif de communication sans fil pour les téléchargement de logiciel dans le champ
WO2003010662A3 (fr) * 2001-07-26 2003-12-24 Kyocera Wireless Corp Systeme et procede de telechargement sur le terrain d'une section de code de logiciel de dispositif de communications hertziennes
US9554268B2 (en) 2001-07-26 2017-01-24 Kyocera Corporation System and method for updating persistent data in a wireless communications device
US7027806B2 (en) 2001-07-26 2006-04-11 Kyocera Wireless, Corp. System and method for field downloading a wireless communications device software code section
US7328007B2 (en) 2001-07-26 2008-02-05 Kyocera Wireless Corp. System and method for organizing wireless communication device system software
US7143407B2 (en) 2001-07-26 2006-11-28 Kyocera Wireless Corp. System and method for executing wireless communications device dynamic instruction sets
US7159214B2 (en) 2001-07-26 2007-01-02 Kyocera Wireless Corp. System and method for compacting field upgradeable wireless communication device software code sections
US7184759B2 (en) 2001-07-26 2007-02-27 Kyocera Wireless Corp. Modular software components for wireless communication devices
US7184793B2 (en) 2001-07-26 2007-02-27 Kyocera Wireless Corp. System and method for over the air area code update
US7197302B2 (en) 2001-07-26 2007-03-27 Kyocera Wireless Corp. System and method for interchangeable modular hardware components for wireless communication devices
US7359699B2 (en) 2001-08-10 2008-04-15 Kyocera Wireless Corp. System and method for peer-to-peer handset communication
US6961537B2 (en) 2001-08-10 2005-11-01 Kyocera Wireless Corp. System and method for peer-to-peer handset communication
US7254386B2 (en) 2001-08-10 2007-08-07 Kyocera Wireless Corp. System and method for improved security in handset reprovisioning and reprogramming
US7743115B2 (en) * 2002-02-27 2010-06-22 Motorola, Inc. Software content downloading methods in radio communication networks
GB2388497A (en) * 2002-03-27 2003-11-12 Nec Corp Mobile communication terminal able to download and store additional dictionaries for temporary or permanent use
GB2388497B (en) * 2002-03-27 2005-11-16 Nippon Electric Co Mobile communication terminal
WO2004021724A1 (fr) * 2002-08-30 2004-03-11 Siemens Aktiengesellschaft Procede pour faire fonctionner un terminal dans un systeme de communication radio, systeme de communication radio, terminal et unite de confirmation pour systeme de communication radio
EP1395074A1 (fr) * 2002-08-30 2004-03-03 Siemens Aktiengesellschaft Méthode de fonctionnement d'un terminal dans un système de communication par radio, système de communication par radio, terminal et unité de confirmation dans un système de communication par radio
US7359698B2 (en) 2003-09-08 2008-04-15 Kyocera Wireless Corp. Systems and methods for enhanced over-the-air programming
EP1560447A1 (fr) * 2004-01-27 2005-08-03 Research In Motion Limited Procédé et dispositif pour actualiser une mémoire non-volatile sur un dispositif sans fil en vérifiant et comparant un élément d'identification spécifique mémorisé dans cette mémoire avec une identification de logiciel
EP1560446A1 (fr) * 2004-01-27 2005-08-03 Research In Motion Limited Procédé et dispositif pour actualiser une mémoire non-volatile sur un dispositif sans fil en vérifiant et comparant un élément d'identification spécifique mémorisé dans cette mémoire avec une identification de logiciel
US7222340B2 (en) 2004-01-27 2007-05-22 Research In Motion Limited Software-delivered dynamic persistent data
US8418162B2 (en) 2004-01-27 2013-04-09 Research In Motion Limited Network delivered dynamic persistent data
US8677341B2 (en) 2004-01-27 2014-03-18 Blackberry Limited Software-delivered dynamic persistent data
GB2425193A (en) * 2005-04-14 2006-10-18 Nec Technologies Method for updating the software in a processor unit
GB2425193B (en) * 2005-04-14 2007-10-17 Nec Technologies Method of software updating and related device

Also Published As

Publication number Publication date
CN1147190C (zh) 2004-04-21
AU4968800A (en) 2000-12-18
SE9901904L (sv) 2000-11-27
SE516806C2 (sv) 2002-03-05
DE10084626T1 (de) 2002-05-16
JP2003501907A (ja) 2003-01-14
SE9901904D0 (sv) 1999-05-26
CN1364390A (zh) 2002-08-14

Similar Documents

Publication Publication Date Title
WO2000074412A1 (fr) Procede et appareil de telechargement dans un equipement terminal radioelectrique
US7275153B2 (en) Booting and boot code update system using boot strapper code to select between a loader and a duplicate backup loader
US6615404B1 (en) Method and apparatus for downloading software into an embedded-system
EP2229625B1 (fr) Mise à jour du micrologiciel d'un dispositif électronique
US7971199B1 (en) Mobile device with a self-updating update agent in a wireless network
US8196130B2 (en) Tri-phase boot process in electronic devices
US20040123282A1 (en) Mobile handset with a fault tolerant update agent
EP1271311A2 (fr) Mise à jour de logiciel d'un dispositif en réseau
EP1639468A2 (fr) Equipement de reseau et procede de controle du demarrage d'un tel equipement
CN111562934A (zh) 一种基于热补丁的软件系统升级方法、终端及存储介质
KR100986487B1 (ko) 고장 허용 갱신 에이전트를 구비한 모바일 핸드세트
JP4482029B2 (ja) 無線基地局および無線基地局の運用方法
CN111273928B (zh) 一种自升级的bootloader设计方法
JP2005284902A (ja) 端末装置、その制御方法及び制御プログラム、ホスト装置、その制御方法及び制御プログラム、遠隔更新システム、方法及びプログラム
US11768669B2 (en) Installing application program code on a vehicle control system
EP3087478B1 (fr) Procédé de mise à jour d'un micrologiciel sur un dispositif à faible mémoire
US20250315248A1 (en) Remote Software Updates with Storage Repartition
US20250175245A1 (en) Device recovery based on operational trust
CN118672569B (zh) 一种易维护高可靠嵌入式系统软件构建方法及存储介质
KR20010007066A (ko) 소프트웨어를 내장 시스템으로 다운로드하기 위한 방법 및장치
CN116719681A (zh) 一种故障测试系统及测试方法
KR20020065186A (ko) 셀룰러 시스템에서 업데이트 실패시 부터코드의 복구방법
CN115599405A (zh) 一种基于docker的扩展服务管理方法及相关装置
JP2005228225A (ja) メモリカードアダプタ
CN115185958A (zh) 射频参数更新系统

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
ENP Entry into the national phase

Ref document number: 2001 500583

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 008107912

Country of ref document: CN

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

RET De translation (de og part 6b)

Ref document number: 10084626

Country of ref document: DE

Date of ref document: 20020516

WWE Wipo information: entry into national phase

Ref document number: 10084626

Country of ref document: DE

122 Ep: pct application non-entry in european phase