EP1082652A2 - Modification de la fonctionnalite d'un terminal mobile dans un reseau radio - Google Patents

Modification de la fonctionnalite d'un terminal mobile dans un reseau radio

Info

Publication number
EP1082652A2
EP1082652A2 EP99930020A EP99930020A EP1082652A2 EP 1082652 A2 EP1082652 A2 EP 1082652A2 EP 99930020 A EP99930020 A EP 99930020A EP 99930020 A EP99930020 A EP 99930020A EP 1082652 A2 EP1082652 A2 EP 1082652A2
Authority
EP
European Patent Office
Prior art keywords
terminal
code
program
network
programs
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.)
Withdrawn
Application number
EP99930020A
Other languages
German (de)
English (en)
Inventor
Adam Aquilon
Stefan Willehadson
Hans Hall
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
Publication of EP1082652A2 publication Critical patent/EP1082652A2/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/303—Terminal profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/306—User profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]

Definitions

  • the present invention relates to service provisioning, and in particular to service provisioning to handheld or portable terminals in wireless network.
  • a method of changing the functionality of a mobile terminal connected by a wireless connection in a network said functionality being implemented as programs in a prograrnming language for which the source code may be compiled to an intermediary code, said intermediary code being executable and verifiable, comprising the following steps:
  • an apparatus for providing programs in a network comprising hosts and several different types of terminals, at least some of said terminals being connected by wireless connections, said programs being implemented in a programming language for which the source code may be compiled to an inter- mediary code, said intermediary code being executable and verifiable, and interpreted or translated to a machine code: said apparatus comprising:
  • - memory means for storing programs in the form of machine code, in such a way that they can be executed in at least one of the types of client terminals in the net- work.
  • - means for transferring a program, in the form of machine code, to at least one client terminal.
  • said apparatus also comprises at least one translator for the intermediary code, said translator being adapted to at least one hardware and software environment used by terminals in the network.
  • the method also comprises the step of translating said program using said at least one translator in the host before storing them.
  • Programs may be downloaded to a terminal automatically or on a request from the user of the terminal.
  • the appropriate program variant to be downloaded to the terminal is determined on the basis of the type of terminal, for example, on the basis of an identity code of the terminal.
  • a portable terminal adapted to wireless communication comprising a core, arranged to receive programs and/or program parts in the form of machine code, and to install the received programs during operation.
  • the portable terminal may be arranged to provide the user with information about the dependency tree of the available programs.
  • the portable terminal may also be arranged to inform the appropriate node in the network about its type and the subscription type with which it is currently operating, and other information, such as its current battery status.
  • the portable terminal also receives and interprets information about whether or not a program or program block should be stored in the portable terminal.
  • Java The most common language of the above mentioned kind today is Java. Other examples are LISP, SmallTalk and Erlang.
  • the source code of a Java program is not compiled to form machine code for a certain type of processor, but to short pseudo- instructions for a virtual machine, "byte code".
  • byte code When a program is to be executed, the byte code is typically downloaded to the te ⁇ ninal on which it is to run and then translated into machine code for said terminal.
  • a program written in an interpreted language such as Java, can be executed in any kind of computer that has a translator or an interpreter for the language.
  • Java is primarily used in Internet applications, but the advantages of interpreted lan- guages also make them feasible for use in cellular networks. Java programs are usually smaller than corresponding machine code programs and are therefore suitable for mobile terminals, in which the memory space available is limited. An increasing number of mobile terminals support Java applications.
  • One main advantage of the present invention is that it enables a division of the responsibility for carrying out the different functions involved in changing the functionality of a device.
  • a software manufacturer can be responsible for developing the source code of the program and for compiling the source code into byte code.
  • the manufacturer of a mobile terminal can be responsible for translating the byte code into machine code and the network operator can be responsible for the transfer of the machine code to the terminals on which it is to be run.
  • the last two points are useful for all portable devices, and especially for portable devices that can communicate with a wireless network of some kind, which will be able to utilize all types of services offered by the network. Also, upgrading the software by downloading new programs will be easy, so that the te ⁇ ninal will not become obsolete as the functions are upgraded or new services are developed. This will also make it easier to change from one operator to the other, in which case the service package of the new operator will replace the old package. It is also perceivable to let the services provided by a mobile operator change according to, for ex- ample, the time of day, the error status of the base stations in the area, the availability of Internet-related services, etc.
  • Figure 1 is a simplified view of a network in which the solution according to the in- vention is applied.
  • Figure 2 is a more complete view of a network in which the solution according to the invention is applied.
  • Figure 3 is a flow chart of the procedure of making a new service available in the network according to the invention.
  • Figure 4 is a flow chart of the procedure of downloading a new service to a terminal automatically according to the invention.
  • Figure 5 is a flow chart of the procedure of downloading a new service to a terminal on a user's request according to the invention.
  • Figure 6 is an overview of how the responsibility may be divided between different participants according to the invention.
  • FIG. 1 is a simplified view of a network in which the solution according to the invention is applied.
  • a portable terminal 1 is connected, via an air interface to a mo- bile network, through a base station 3.
  • the base station is connected to a control unit 5, which is in turn connected to a network (not shown).
  • the control unit 5 controls the base stations, and performs resource allocation functions and other functions such as switching functions in the mobile telecommunications network.
  • the control unit 5 there is a program provisioning unit 9.
  • the control unit 5 is connected to one or more hardware vendors' hosts 7, in turn connected to hosts 8, for example belonging to software vendors.
  • the software vendors' hosts 8 are used for producing the source code and for compiling the source code into byte code.
  • each hardware vendor's host 7 comprises one or more translators 11 for at least the terminal types of the particular hardware vendor.
  • test activities will normally be carried out in ways known in the art.
  • the translating function may be carried out in the program provisioning unit 9, in which case the program provisioning unit must comprise at least one translator 11.
  • the program provisioning unit 9 comprises a number of programs 13, 15. Each pro- gram exists in a number of variants, 13a, 13b, 13c, 15a, 15b, 15c, translated by different translators 11 to be executable in different types of terminals 1.
  • control unit 5 comprises a selection unit comprising logic for dete ⁇ nining the appropriate variant 13a, 13b, 13c, 15a, 15b, 15c of the program 13, 15 to be transmitted to the terminal 1.
  • a selection unit 17 is shown in the program provisioning unit.
  • Figure 2 is a more extensive representation of a network in which the solution ac- cording to the invention is implemented.
  • the network may comprise several networks, for example, a telecommunications network 21 and a data network 23, such as the Internet.
  • the telecommunications network 21 is a cellular telecommunications network.
  • the telecommu- nications network 21 comprises one or more communication units 25, such as base stations, connected to the network through control nodes 26 controlling the function of the communication units 25 and possibly other functions, such as switching functions in the network.
  • the communication units 25 are adapted to wireless communication with terminals 27 in the network.
  • the data network 23 also comprises a number of terminals 29, 31, some of which 29 are used to provide programs in the form of source code or byte code. Others 31 may retrieve programs that are made available according to the invention.
  • the control nodes 26 also comprise the programs to be downloaded to the terminals 27 in the cellular network 21.
  • the translated versions of the programs are downloaded to the control nodes 26 and stored there.
  • the programs may also be downloaded to the control node 26 as byte code, translated in the control node 26 and stored there as machine code.
  • the programs may also be downloaded to the control node 26 and stored as byte code. In the latter case, the byte code must be translated to machine code when the program is to be downloaded to a terminal.
  • any terminal 27, 31 connected to any of the networks 21, 23 can also download programs from any host 25, 29 in any of the networks, provided the functions required to do so are available in the terminal 27, 29, 31 or in the network.
  • a selection unit 33 is shown in each control node 26.
  • the selec- tion unit 33 comprises logic for selecting the appropriate variant of a program to be transmitted to a terminal 27. If translated programs are stored, the selection unit may also comprise have access to a list of the appropriate variant of a program for each terminal type and/or subscription. If the byte code is stored and the program translated when it is to be transmitted, the selection unit may comprise or have access to a list specifying which translator should be used for transmission to a particular terminal type and/or subscription. The list may of course also state that a particular terminal type and/or subscription should not receive any variant of a particular program.
  • FIG. 3 is a flow chart of the steps taken to make a new program available in the network.
  • Step S31 The source code of the service program is written, in Java or another interpreted language.
  • Step S32 The source code produced in step S31 is compiled to produce byte code. This step will normally include security checks, error detection, function testing, debugging, and so on.
  • Step S33 The byte code produced in step S32 is downloaded to the server on which it should be stored. This step will normally also include security checks.
  • Step S34 The service programs are translated by each of the translators available. If the service programs are not to be run on all types of terminals, of course, they only have to be translated by the relevant translators.
  • Step S35 The machine code resulting from step S34 are stored in a place from which it can be downloaded to portable terminals or other devices. If the storage space of the control node 26 is limited, it may not be feasible to store several different translated versions of the program. In this case, program may be stored in the form of byte code. The translation of the byte code then takes place when it is downloaded to the terminal, that is, steps S34 and S35 are not needed. Of course, it will be possible to interpret the programs before they are downloaded to the server on which they are to be stored, that is, to change the order of steps S33 and S34.
  • Figure 4 is a flowchart of the steps performed when a service is to be automatically downloaded to a portable device.
  • Step S41 The system informs the user that it may be desirable to download a program and requests an acknowledgement. This may be, for example, because a new program, or a new version of a program has been made available, or because the user selects a function that requires a program that is not found in the user's terminal.
  • Step S42 The user accepts or denies the downloading of the new program version.
  • Step S43 If the user accepts the downloading, the appropriate program variant for the terminal type is selected and the program is downloaded. End of procedure.
  • FIG. 5 is a flowchart of the steps performed when a service is to be downloaded to a portable terminal on request of a user for execution or storing of a program.
  • Step S51 The user initiates a connection between the device to which the pro- gram should be downloaded and the server on which the program is located. This may be done in any way known in the art, through an air interface or a wired connection.
  • Step S52 The type of terminal is determined. This is preferably done automatically by the system, but if necessary, the user may specify the type of terminal.
  • Step S53 If appropriate, the user selects the program or programs to be downloaded.
  • Step S54 The appropriate variant and version of the program or programs selected in step S53 is identified and downloaded. If the programs are stored as byte code in the server, they must also be translated by the appropriate translator when being downloaded. End of procedure.
  • the programs may be temporarily stored in the terminal and discarded once they have been executed, or the programs may be stored in the terminal.
  • steps S43 and S54 the selection of the appropriate program variant may be carried out in the communication unit, or this information may be retrieved from the vendor of the terminal or the software vendor.
  • the programs, and the appropriate variant of each program, that may be downloaded to a particular terminal may be dete ⁇ nined in dependence of the type of terminal and the type of subscription.
  • Information about the type of subscription is found on a chip in the telephone, and is always communicated to the base station when a connection is to be set up.
  • This chip for example, the SIM card in GSM, is normally removable and may inserted in a number of different terminals. Thus, the type of terminal cannot be determined from the information on the chip. Different terminal types may, however, be able to run different programs, and require different variants of programs, even if the sub- scription type is the same.
  • the terminal type may be determined both automatically and by manual identification. In the latter case, for example, each terminal type may be assigned an identification number, which is entered every time a program is to be downloaded. In a preferred embodiment, the terminal type is determined using an identity code of the terminal, which is a unique number identifying a wireless terminal. In GSM, for example the International Mobile Station Equipment Identity (IMEI) might be used. This number (IMEI) is stored in every mobile terminal and should in this case be transmitted by the mobile terminal to the network to indicate the variant of a program that whould be received. It would also be possible to define a number of terminal types and enable every teraiinal to inform the system about its terminal type.
  • IMEI International Mobile Station Equipment Identity
  • information about the requirements of each series of terminals must be supplied from the manufacturers of the terminals and stored in each host, or retrieved from the manufacturer each time it is needed.
  • This information may have the form of a specification of the translator that should be used for each terminal type.
  • the translator may be provided by the terminal manufacturer, in which case the appropriate translator only has to be identified. If the terminal manufacturer does not provide the translator, the requirements on the translator must be specified in detail.
  • the programs to be downloaded may also be determined in dependence of other factors, such as the cell identity, the operator, the date or the time of the day.
  • Automatic downloading of programs may be used, for example, in the following situations:
  • the program associated with this service may be downloaded without the user being explicitly informed first.
  • Certain programs may be automatically downloaded in dependence of the location, the time of the day, the operator, etc.
  • the user should be possible for the user to stop the download- ing of software, if he/she does not want to receive new software. This may happen, for example because of lack of time or because the battery is low.
  • the downloading may also be stopped automatically, for example, if the battery is low.
  • the transmission of programs from the host to the terminal may be made according to existing protocols for data transmission in the system concerned.
  • GSM Global Packet Radio Service
  • GPRS Global Packet Radio Service
  • AMPS Advanced Mobile Phone Service
  • CDPD Cellular Digital Packet Data
  • the latter protocol also comprises functions for suspending data communication when a voice call is attempted.
  • the transfer of the program to the mobile terminal may be carried out in any available channel.
  • a traffic channel may be used.
  • data may be transmitted according to circuit switched protocols or according to packet switched protocols, such as GPRS in a GSM system.
  • packet switched protocols such as GPRS in a GSM system.
  • high-speed connections involving more than one traffic channel may be used, for example High-Speed Circuit- Switched Data (HSCSD) in GSM. This will make the transfer of the program faster but will probably only be feasible at times when the traffic load in the network is low.
  • HCSD High-Speed Circuit- Switched Data
  • Broadcasting may be used when the same program is to be transferred to several mobile terminals at the same time.
  • control information must be added to let the mobile terminals know which terminal types are to receive the program, and each terminals must comprise logic to be able to determine whether or not the program is intended for this particular terminal.
  • the program parts to be stored in this way may be selected by the subscriber or by a node in the network, but preferably by both in cooperation.
  • each program or program part may be marked, to signify if it should be stored in the mobile terminal from a system point of view, for example, to save bandwidth.
  • knowledge of the state of the terminal is also needed. Therefore, it is usually not feasible to store these program parts automatically, without giving the subscriber a chance to interrupt.
  • the subscriber is to delete a program or a program part, he/she must be given information about the dependency tree, that is, what other programs or programs part use the program or program part to be deleted, in order to decide if the program or program part should really be deleted.
  • the mobile terminal should therefore contain functions enabling the subscriber to determine whether or not a specific program or program part should be stored, and for how long, and providing the information needed by the subscriber to make a decision.
  • Figure 6 illustrates the division of the responsibilities for providing the programs according to the invention.
  • a service provider 101 provides the appropriate source code, or byte code. To do this, the service provider 101 must know the desired functionality of the service to be provided. Detailed information about the software and hardware environment provided in the terminals is not needed, but basic knowledge about, for example, the capacity of a terminal may be useful.
  • a terminal manufacturer 103 provides the terminals and, usually, a translator for the programming language, adapted for the terminals he provides.
  • the terminal manufacturer 103 must have knowledge about the programming language used. There may of course be several service providers and terminal manufacturers.
  • a network operator 105 is responsible for a mobile network 107 and for providing the services to subscribers 109 in the network 107.
  • the responsibilities may be divided between the service provider 101, the terminal provider 103 and the network operator 105 in a number of different ways.
  • the service provider 101 may provide byte code to the terminal manufacturer 103, as indicated by the arrow 111.
  • the terminal manufacturer 103 then translates the byte code to machine code using the appropriate translators for the terminals he provides, and provides this machine code to the network operator 105 through a transport network 113, such as the Internet, as indicated by an arrow 115.
  • the machine code could be provided in any way known in the art, for example, by means of a direct connection or on a floppy disk, or CD-ROM.
  • Another way of dividing the responsibilities would be for the service provider 101 to provide the byte code directly to the network operator 105, through the transport network 113, as indicated by an arrow 117.
  • the terminal manufacturer 103 could provide the translator to the network operator 105, and the network operator 105 could translate the byte code into machine code.
  • the machine code could be stored in a memory 119 and provided to the subscriber 109 through the cellular network 107 when desired, as indicated by an arrow 121.
  • the service provider 101 could deliver the source code instead of the byte code, but it is normally not desirable to deliver source code.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)
  • Information Transfer Between Computers (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Computer And Data Communications (AREA)
  • Communication Control (AREA)

Abstract

La fonctionnalité de dispositifs radio portables peut être changée par la fourniture de programmes écrits dans une langue, p.ex. le javanais, produisant un code intermédiaire vérifiable (code multiplet). Le code intermédiaire est traduit en code machine dans un noeud du réseau avant d'être transféré au dispositif radio dans lequel il doit être exécuté. Plusieurs variantes de codes machine de chaque programme, traduits à l'aide de traducteurs destinés à différents types de terminaux, peuvent exister. Cela permet d'utiliser le même code source pour différents types de terminaux et de répartir, entre les fournisseurs de logiciels, les fournisseurs de terminaux et les exploitants réseau, les responsabilités d'exécution des différentes fonctions comprises dans le changement de la fonctionnalité d'un dispositif, notamment le développement d'un code source du programme, la compilation du code source en code multiplet, la traduction du code multiplet en code machine et le transfert du code machine aux terminaux dans lesquels il doit être exécuté.
EP99930020A 1998-05-28 1999-05-26 Modification de la fonctionnalite d'un terminal mobile dans un reseau radio Withdrawn EP1082652A2 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
SE9801897A SE514762C2 (sv) 1998-05-28 1998-05-28 Förfarande, anordning och portabel terminal för programvarunedladdning i ett trådlöst näverk samt sådant telekommunikationsnät
SE9801897 1998-05-28
PCT/SE1999/000892 WO1999061983A2 (fr) 1998-05-28 1999-05-26 Modification de la fonctionnalite d'un terminal mobile dans un reseau radio

Publications (1)

Publication Number Publication Date
EP1082652A2 true EP1082652A2 (fr) 2001-03-14

Family

ID=20411500

Family Applications (1)

Application Number Title Priority Date Filing Date
EP99930020A Withdrawn EP1082652A2 (fr) 1998-05-28 1999-05-26 Modification de la fonctionnalite d'un terminal mobile dans un reseau radio

Country Status (6)

Country Link
EP (1) EP1082652A2 (fr)
CN (1) CN1309787A (fr)
AU (1) AU4664099A (fr)
CA (1) CA2333119A1 (fr)
SE (1) SE514762C2 (fr)
WO (1) WO1999061983A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10824410B2 (en) 2016-11-23 2020-11-03 Beijing Xiaomi Mobile Software Co., Ltd. Method and equipment for executing a file

Families Citing this family (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7836395B1 (en) * 2000-04-06 2010-11-16 International Business Machines Corporation System, apparatus and method for transformation of java server pages into PVC formats
WO2002015527A2 (fr) * 2000-08-11 2002-02-21 Zucotto Wireless, Inc. Interface pour appareil de communication et procede de decouverte d'appareils distants
BE1014409A3 (nl) * 2001-10-02 2003-10-07 Acunia Nv Werkwijze en netwerkingsysteem voor het beschikbaar stellen van diensten.
ES2198198B1 (es) * 2002-01-29 2005-05-01 Airtel Movil, S.A. Sistema de personalizacion de las aplicaciones de una tarjeta sim o usim de un terminal movil.
DE10216853A1 (de) * 2002-04-16 2003-10-30 Siemens Ag Telekommunikationsmodul mit einem System-Datenverarbeitungsmittel zum Ausführen mindestens einer Telekommunikationsaktivität
US20040221021A1 (en) * 2003-04-30 2004-11-04 Domer Jason A. High performance managed runtime environment application manager equipped to manage natively targeted applications
KR100548368B1 (ko) * 2003-07-03 2006-02-02 엘지전자 주식회사 휴대단말기의 동적 자바푸시 장치 및 방법
US7546594B2 (en) * 2003-12-15 2009-06-09 Microsoft Corporation System and method for updating installation components using an installation component delta patch in a networked environment
KR100643268B1 (ko) * 2004-01-17 2006-11-10 삼성전자주식회사 자바 가상 머신의 성능을 향상시키는 방법 및 상기 방법에의해 동작되는 시스템
US7676448B2 (en) 2004-03-12 2010-03-09 Microsoft Corporation Controlling installation update behaviors on a client computer
US7853609B2 (en) 2004-03-12 2010-12-14 Microsoft Corporation Update distribution system architecture and method for distributing software
EP1797732B1 (fr) * 2004-10-05 2010-06-09 Research In Motion Limited Diagnostic, essai, installation d'application et mise a jour d'un dispositif mobile a partir d'une page web
DE102005062513A1 (de) * 2005-12-27 2007-06-28 Vodafone Holding Gmbh Verfahren zum Konfigurieren eines netzwerkeingebundenen Datenverarbeitungsgeräts sowie netzwerkeingebundenes Datenverarbeitungsgerät
EP1916598A1 (fr) * 2006-10-23 2008-04-30 Nagravision S.A. Méthode de chargement et de gestion d'une application dans un équipement mobile
EP2760244A1 (fr) * 2010-07-13 2014-07-30 Nokia Solutions and Networks Oy Optimisation dynamique de ressources de réseau radio basée sur le type d'équipement utilisateur eyant smartphone
US10565014B2 (en) * 2017-12-05 2020-02-18 Western Digital Technologies, Inc. Data processing offload using in-storage code execution

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5694601A (en) * 1989-09-28 1997-12-02 Sterling Software, Inc. Portable and dynamic distributed applications architecture

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4667290A (en) * 1984-09-10 1987-05-19 501 Philon, Inc. Compilers using a universal intermediate language
US6131159A (en) * 1992-05-08 2000-10-10 Paradyne Corporation System for downloading programs
JPH06309204A (ja) * 1993-04-20 1994-11-04 Matsushita Electric Ind Co Ltd データ処理方法及びその装置
US5541986A (en) * 1993-07-27 1996-07-30 Bell Communications Research, Inc. Method and system for automated telecommunications service script consolidation and downloading
US5666293A (en) * 1994-05-27 1997-09-09 Bell Atlantic Network Services, Inc. Downloading operating system software through a broadcast channel
EP0767426B1 (fr) * 1995-10-05 2014-01-01 Gigaset Communications GmbH Procédé pour la programmation d'un appareil

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5694601A (en) * 1989-09-28 1997-12-02 Sterling Software, Inc. Portable and dynamic distributed applications architecture

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
IBM CORP.: "Cellular telephone with Over-The-Air Software Download Capability", IBM TECHNICAL DISCLOSURE BULLETIN, vol. 41, no. 1, January 1998 (1998-01-01), pages 263, XP000772100 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10824410B2 (en) 2016-11-23 2020-11-03 Beijing Xiaomi Mobile Software Co., Ltd. Method and equipment for executing a file

Also Published As

Publication number Publication date
SE514762C2 (sv) 2001-04-23
SE9801897L (sv) 1999-11-29
CN1309787A (zh) 2001-08-22
SE9801897D0 (sv) 1998-05-28
CA2333119A1 (fr) 1999-12-02
WO1999061983A3 (fr) 2000-02-03
WO1999061983A2 (fr) 1999-12-02
AU4664099A (en) 1999-12-13

Similar Documents

Publication Publication Date Title
EP1082652A2 (fr) Modification de la fonctionnalite d'un terminal mobile dans un reseau radio
KR100584443B1 (ko) 소프트웨어 콤포넌트 다운로드 관리 기능을 가지는 이동 단말기와 그 방법
EP1362491B1 (fr) Demarrage d'une session internet sur des dispositifs de telecommunication cellulaire personnels, et protocole de personnalisation pour ce faire
KR100817387B1 (ko) 양방향 통신 및 동적 명령 세트 실행 시스템 및 방법
CN1270254C (zh) 通信系统中能力协商信息的更新
US8572597B2 (en) Apparatus and method for performing an over-the-air software update in a dual processor mobile station
KR100883556B1 (ko) 이동 전화 네트워크의 데이터를 처리하고 전송하는 방법및 마이크로칩 탑재 시스템
JP3464760B2 (ja) 加入者識別モジュールによって制御される移動端末に所定のアイテムリストをダウンロードするための改良された方法及びコマンド、加入者識別モジュール及び移動端末
WO2005079144A2 (fr) Systeme automatique de configuration d'un appareil mobile et procede dans un reseau de communication mobile
WO2009133472A2 (fr) Procédé et système destinés à l’exécution d’applications dans les réseaux de télécommunication sans fil
WO1997044975A1 (fr) Procede et dispositif pour acceder a une pluralite de reseaux de communication
CN106961339B (zh) 实现定向流量的方法及系统
US7200385B1 (en) Selection of service implementation
FI111318B (fi) Sovellusten käyttö tietoliikennejärjestelmässä
JP2006506721A (ja) 端末およびチップ・カード内に展開するアプリケーションのロード方法
EP1111506A1 (fr) Méthode et dispositif pour la détermination d'un environnement de traitement
EP2356805B1 (fr) Méthode et système pour la gestion de service des stations mobiles
EP1435743A1 (fr) Téléchargement des scripts d'application sur un terminal mobile par SMS
US20050177696A1 (en) Over the air memory allocation modification
CN114422972A (zh) 数据交互方法、系统、装置及存储介质
KR20020004032A (ko) 사용자 중심의 무선 인터넷 서비스 제공방법 및 장치
KR20100018213A (ko) 사업자간 무선 인터넷 접속 호환성 유지 방법 및 이를이용한 이동통신단말기

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20001207

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): DE GB

RIN1 Information on inventor provided before grant (corrected)

Inventor name: HALL, HANS

Inventor name: WILLEHADSON, STEFAN

Inventor name: AQUILON, ADAM

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)

17Q First examination report despatched

Effective date: 20070509

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20070920