WO2003032156A2 - Verfahren zum aktuellhalten von software auf verschiedenen endgeräten - Google Patents
Verfahren zum aktuellhalten von software auf verschiedenen endgeräten Download PDFInfo
- Publication number
- WO2003032156A2 WO2003032156A2 PCT/DE2002/003726 DE0203726W WO03032156A2 WO 2003032156 A2 WO2003032156 A2 WO 2003032156A2 DE 0203726 W DE0203726 W DE 0203726W WO 03032156 A2 WO03032156 A2 WO 03032156A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- software
- terminal
- pal
- sof
- pec
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
- G06F9/4856—Task life-cycle, e.g. stopping, restarting, resuming execution resumption being on a different machine, e.g. task migration, virtual machine migration
- G06F9/4862—Task life-cycle, e.g. stopping, restarting, resuming execution resumption being on a different machine, e.g. task migration, virtual machine migration the task being a mobile agent, i.e. specifically designed to migrate
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Definitions
- the invention relates to a method for keeping software up-to-date on various end devices which are connected to a communication network via which they can communicate with one another.
- Modern users generally have various devices such as personal computers, for example desktop and / or laptop computers, mobile radio devices, handheld computers, etc.
- devices such as personal computers, for example desktop and / or laptop computers, mobile radio devices, handheld computers, etc.
- software programs for the management of data run on the devices listed, for example relating to contact information or appointment records of the user.
- a new entry in the diary software of his handheld computer for example, now makes it necessary for a user to use a relatively complex procedure to access all of his additional devices on which he also wants to use the latest version of this data bring up to date.
- the devices are usually to be connected to one another via interfaces which usually differ from device to device. It is also advantageous if the same software runs on the devices to be compared in order to make the update process simple and unproblematic.
- a disadvantage of this procedure, as practice shows, is that on the one hand the constantly necessary update process is perceived as tedious by many users and these updates are therefore often carried out only irregularly, which often leads to different data records on the different devices.
- the different devices run under different operating systems, with different software programs for the user. Work on a contact data record, for example, so that the update process is made even more difficult and information is often lost when the data is compared.
- Communication network is transmitted to the second terminal, and
- the latest software status is simply transferred to another desired device, where software corresponding to the software running on the original device is provided with the current status and then continues to run in the last status. It is particularly advantageous if the software corresponding to the software on the first terminal is transferred from the storage location to the second terminal on the second terminal.
- a software server is used as the storage location of the software, which is connected to the communication network.
- the software is stored on this centrally or is generated on request and can be transferred to the desired end device if required.
- the storage device of the software is the terminal on which the software was originally stored expires, is used. In this way, independence from a central server is achieved when changing between two end devices.
- step a the software state is packaged in a message which is transmitted to the second terminal.
- agent software is used as software.
- Such software has special properties which are explained in detail in the description below. Because of these properties, agents are particularly suitable for use in the method according to the invention.
- the message also contains the storage location of the software, from where the software is then transferred to the desired new terminal.
- the message contains at least the name of the main class and the location of the agent's class definitions.
- the class definitions are compiled JAVA code.
- the code of each class is usually saved in a separate class file. It is there in a standardized binary form that can be read by any interpreter.
- the interpreter When the program is started, the interpreter translates the class file into computer-specific machine code and generates the program. Whenever he has to create a new class, he gets its definition from its location.
- the main class is the class from which an interpreter can find the paths to all classes that he needs to create the agent step by step.
- the request may be made by the second terminal via the communication network to the first terminal, where it is transmitted to the software, and the software then takes the appropriate steps for a transfer to the new terminal ,
- a unique address of the terminal, to which the software and the software status is to be transferred is transmitted to the software so that it is also reliably transferred to the correct destination.
- This address can either already be saved or can be entered by the user.
- an IP address of the end device is used as the address.
- the software already stored on the software server is then transferred to the end device - or, in the case of agent software, the software is generated and transferred to the end device -, the stored software status is also transferred, and provide the software with this so that it can continue to run in the most current state.
- JAVA is used as the runtime environment.
- the software used in connection with the invention can in principle be any software, such as word processing, etc.
- the invention is particularly advantageous to use, for example, if the software is software for realizing voice connections and / or data connections, since in this case a connection can be transferred without interrupting the connection between two terminals.
- FIGS. 3 and 4 a system for carrying out a method according to the invention in connection with a voice-over-IP connection of a user's terminal equipment to a remote station
- Fig. 5 shows the life cycle of a
- FIGS. 1 and 2 show a first simple example for keeping software sof or software states current on several end devices PEC, PAL.
- a user has, for example, a desktop computer PEC and, on the other hand, also a handheld device PAL.
- PAL handheld device
- each of these devices PAL, PEC no longer runs its own software for a specific application, such as for contact management, which is then used on each of the devices PEC for each new or changed entry.
- PAL would have to be adjusted again on the other device, but the user "only" has an executable software application for the respective specific application, which is transferred between the individual devices PEC, PAL on request.
- the software sof in question is stored in the switched-off state of the terminals PEC, PAL on a software server SSE in a memory device SSD assigned to it. If the user now puts his desktop computer PEC into operation, a request to the software server SSE is transmitted either by a corresponding input by the user or automatically, and the desired software sof, such as contact management, is sent to the desktop in the last updated state -Computer PEC transmitted.
- a communication network NET is naturally also to be understood as the case that, for example, the server is connected to a fixed network, while one or more of the terminals are connected to a mobile radio network, for example, and the connection is then established via this network.
- a corresponding request is simply transmitted to the desktop computer PEC and the software sof is transmitted to the handheld PAL via the communication network NET.
- agent software In an advantageous embodiment of the invention, the so-called agent technology is used, as will be explained in more detail below.
- the software running on an end device is then "agent programs".
- agent software In the rest of the text, the terminology is usually used that the respective software is agent software.
- this agent software is made up of there are several “agents", a master agent and one or more slave agents. These can communicate with the master agent and are intended for the execution of special tasks, while the master agent, among other things, handles the communication "to the outside", so that from the outside the software also appears as "only” software.
- an agent can move itself or be moved by another agent or an agent platform.
- the request to transfer the software and the software status to another device is usually made by entering the software - or in the agent picture in the master agent - on the device on which the software is currently running.
- the request is made from the outside, for example by input on another terminal, for example into another agent, which then brings the correspondingly desired agent from the desired terminal to the requesting terminal.
- the master agent After the requested software (the master agent) has received the requests, it then initiates the necessary steps for its migration to the other end device.
- the communication itself is preferably carried out via the Internet NET; the TCP / IP protocol (“Transmission Control Protocol / Internet Protocol”) is used as the transmission protocol for the software sof.
- the software sof is received on the desktop computer after the request has been received stopped in its current state with all its parameters, settings etc. ("frozen") and transmitted in this state to the second terminal PAL, where it then continues in the last current state.
- a software agent is a program that accepts an order and carries it out independently or performs user-defined tasks autonomously.
- Mobile software agents are programs in the form of autonomous objects migrate around a network of heterogeneous computers - typically intranets or parts of the Internet - and perform services or perform tasks on behalf of a user.
- a software agent thereby decides autonomously due loka- 1er circumstances whether, when and where they want to migrate, if necessary.
- the dynamic process status of the software agent at certain stable program points is frozen by the agent system at the request of the software agent and packaged together with context information and a variable data part in a message to be sent.
- the process status is thawed again and the agent continues seamlessly at the point where it was interrupted.
- the strong migration the dynamic process status of the software agent is frozen by the agent system at any program point and packed together with context information and a variable data part in a message to be sent.
- the process status is thawed again and the agent continues seamlessly at the point where it was interrupted.
- a software agent interacts with the respective local environment - the agent system that currently houses it, and can also cooperate with other locally available or remote software agents.
- a software agent can communicate with his client residing at another location, for example to deliver intermediate results or to request new data and instructions.
- the latter is a rather rare event, since software agents are conceptually able to act largely autonomously.
- the technology on which the software agents are based is described in US Pat. No. 5,603,031 and EP 0 634 719.
- the following documents have also been presented to the public in connection with software agents: “Walter Brenner, Rüdiger Zarnekow, Hartmut Wittig: Intelligent software agents. Fundamentals and Applications, Springer Verlag Berlin, 1998 ";” Stan Franklin, Art Gaesser: Is it an Agent, or just a Program? A Taxonomy for Autonomous Agents.
- the clone now represents an exact copy of the original, and in this way it is reliably ensured that no information, settings, etc. are lost during transmission.
- the only prerequisite for the functioning of the invention is that the end devices used have the same runtime environment for the agent software, so that it can run on the different devices, and the same agent platform is also necessary.
- the well-known JAVA is used as the runtime environment.
- the agents are usually JAVA programs themselves and require JAVA everywhere as a runtime environment.
- JAVA programs themselves and require JAVA everywhere as a runtime environment.
- standardized interfaces of their platforms are necessary, through which they can interact.
- Java is an object-oriented programming language developed by Sun for Internet applications. Java is similar to the C ++ programming language, but does not use its processor-specific adjustments. It is used to create platform-independent applets application parts that only require an interpreter and certain browsers, such as Netscape Navigator, Oracle PowerBrowser, Mosaic from Spyglass and Sun Hot Java. Java supports, among other things, text, hypertext, graphics, audio and animation functions.
- Agents are complete applications and only require the interpreter and not a browser.
- the entire software in its most current state is transferred from one device PEC to another device PAL of the user.
- the software will end its service on the original device at the latest when the software starts to run on the “new” device.
- the software can also run in parallel on several devices of one user, but not in the same software state.
- the software status cannot be exchanged between running programs. It makes sense, however, that the software will only ever run on one device per user.
- the software status of the software sof is in turn transmitted via the Internet NET to the software server SSE and in its storage device SSD in the most current status stored.
- the software itself is not stored on the agent server SSE, since the class definition of the respective agents is stored there anyway and the agent itself can easily be generated again if a corresponding requirement is met.
- the software server SSE naturally also offers a runtime environment for software agents.
- a user can, for example, create a desired software agent - within the limits provided by the provider - using such a software agent server SSE via the Internet NET via a corresponding website.
- the contact management mentioned above is again mentioned, which the user creates according to certain criteria - for example, which basic entries should be present, such as name, address, phone numbers, etc. Data can usually also be entered here.
- the “finished” software agent is then transferred via the Internet to the respective end device of the user, where it is executed, transferred, etc., as already described above.
- FIGS. 3 and 4 Another specific exemplary embodiment of the invention is illustrated with reference to FIGS. 3 and 4 in connection with Internet telephony (VoIP, “Voice over Internet Protocol”).
- VoIP Internet telephony
- the reference numerals (numbers) in brackets () each refer to FIG. 5.
- the agent sof is created (1); At this point, the agent also receives all user information, such as settings, information about previous calls, and "Movement History", which contains the addresses of all computers on which the agent has already run, so that they can be conveniently listed in the future
- the agent sof is then transferred to the user's desktop PEC (2), where it then runs, and from then on the agent sof, which in this case is a communication program , able to connect to or accept another terminal if desired by the user.
- the call parameters are negotiated in a first step with the counterpart CLI via a signaling protocol sip (3).
- the agent sof communicates with another agent sof or a communication application on the client computer CLI.
- the communication as shown in FIG. 3 takes place via a proxy server PRO using the "Session Initiation Protocol" (SIP) sip
- SIP Session Initiation Protocol
- IETF Internet Engineering Task Force
- SIP protocol is functionally comparable to the H.323 protocol and can set up, change and terminate interactive communication services.
- the SIP information can be transported via TCP or UDP ("User Datagram Protocol").
- SIP has an open internet-based structure and enables CLASS features ("Custom Local Area Signaling Service") such as the transmission of the identity of the caller or call forwarding in IP-based networks.
- SIP is responsible for call signaling, user localization and registration. The quality of service, directory access and the session procedures are adopted by other protocols.
- connection protocol rtp for example the RTP protocol ("Real Time Protocol").
- RTP protocol was developed by the Audio-Video Transport Group of the IETF and is part of H.323 on the application layer and can network-based video or handle audio communication. To differentiate the media, RTP differentiates between different coding formats so that the transmitted data can be used regardless of the application.
- the Real Time Protocol (RTP) is based on an end-to-end connection and supports multicast as well as unicast connections.
- the protocol uses a time stamp that is specified by the respective RTP profile.
- the RTP header has a 32-bit data field "Synchronization Source Identifier" ( ⁇ SRC).
- ⁇ SRC Synchronization Source Identifier
- CSRC Content Source Identifier
- the communication agent sof follows him when prompted for the new terminal PAL.
- a special sequence of events must occur so that the communication is not interrupted during this migration of the agent until the initialization routines have expired.
- the agent sof copies itself to the new PAL device and takes all necessary steps (searching for audio and video devices, such as a sound card, camera, etc., testing the devices found, preparing and occupying the communication ports such as SIP or RTP ports) so that the signaling can be switched.
- the original agent remains on the first terminal PEC until this has been successfully done and maintains the connection with the remote terminal CLI.
- the new agent sof ie the clone of the original agent
- the new terminal PAL (5) After the new agent sof, ie the clone of the original agent, has completed its initialization, it transfers the ongoing call to the new terminal PAL (5).
- the old agent ends his Service, and the new agent sof, which is an identical copy of the old agent, continues the services and the call. In this way, interruptions in the connection can be reliably prevented.
- the new agent transfers the ongoing conversation to himself using a SIP message (REINVITE) to the other party. He then terminates the "old” agent, who then only ensures that the "old” slaves are also terminated.
- REINVITE SIP message
- the desktop computer PEC is no longer involved in the communication; this now runs directly from the handheld computer PAL to the remote terminal CLI, as if communication had been started directly between the two terminals PAL, CLI.
- the signaling of the “new” agent with the corresponding software of the remote station CLI takes place again, for example, via the SIP protocol, and the subsequent transmission of data as part of the communication then takes place, for example, via the RTP - Protocol as explained above instead.
- the software status is sent back to the agent server SSE, (7) the agent is destroyed and the last, current agent status is stored on the agent server (8).
- a uniform runtime environment such as JAVA
- complete independence from the end device is achieved.
- the only requirement is that the corresponding runtime environment for the software agents can run on the end device.
- the respective agents can then be easily transferred between a wide variety of end devices and, in particular, also run on these.
- the same software can therefore run on a wide variety of devices, such as personal computers (PC), PocketPC, handheld PCs, mobile devices, etc.
- the network layer protocol is in usually uses the Internet Protocol, the connection to the IP network can be stationary or mobile (wireless).
- the invention furthermore makes it possible in a simple manner to carry out administration of telephone books, address lists and other records or settings on any personal device Changes are then valid for all personal devices.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Information Transfer Between Computers (AREA)
- Computer And Data Communications (AREA)
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/491,526 US20040237078A1 (en) | 2001-10-04 | 2002-10-01 | Method for updating software in different terminals |
BR0213061-0A BR0213061A (pt) | 2001-10-04 | 2002-10-01 | Processo para a atualização de software em diversos equipamentos terminais |
EP02774441A EP1438658A2 (de) | 2001-10-04 | 2002-10-01 | Verfahren zum aktuellhalten von software auf verschiedenen endgeräten |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE10148875A DE10148875A1 (de) | 2001-10-04 | 2001-10-04 | Verfahren zum Aktuellhalten von Software auf verschiedenen Endgeräten |
DE10148875.0 | 2001-10-04 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2003032156A2 true WO2003032156A2 (de) | 2003-04-17 |
WO2003032156A3 WO2003032156A3 (de) | 2003-12-31 |
Family
ID=7701318
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/DE2002/003726 WO2003032156A2 (de) | 2001-10-04 | 2002-10-01 | Verfahren zum aktuellhalten von software auf verschiedenen endgeräten |
Country Status (6)
Country | Link |
---|---|
US (1) | US20040237078A1 (de) |
EP (1) | EP1438658A2 (de) |
CN (1) | CN1564979A (de) |
BR (1) | BR0213061A (de) |
DE (1) | DE10148875A1 (de) |
WO (1) | WO2003032156A2 (de) |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7839987B1 (en) | 2001-11-01 | 2010-11-23 | Callwave, Inc. | Methods and systems for creating a dynamic call log and contact records |
US7818734B2 (en) * | 2005-01-21 | 2010-10-19 | Callwave, Inc. | Methods and systems for transferring data over a network |
US7965825B1 (en) | 2005-05-02 | 2011-06-21 | Callwave, Inc. | Methods and systems for transferring voice messages and faxes over a network |
JP4548307B2 (ja) * | 2005-10-31 | 2010-09-22 | ソニー株式会社 | 分離型処理装置及びそのソフトウエアの版更新方法 |
US8121626B1 (en) | 2006-06-05 | 2012-02-21 | Callwave, Inc. | Method and systems for short message forwarding services |
US8601460B2 (en) * | 2007-07-25 | 2013-12-03 | International Business Machines Corporation | Systems and methods for firmware cloning |
WO2010082077A1 (en) * | 2009-01-19 | 2010-07-22 | Telefonaktiebolaget L M Ericsson (Publ) | Mobile specialized software code update |
US20120144056A1 (en) * | 2009-08-12 | 2012-06-07 | Nederlandse Organisatie Voor Toegepast- Natuurwetenschappelijk Onderzoek Tno | Dynamic RTCP Relay |
US8938518B2 (en) * | 2012-01-16 | 2015-01-20 | International Business Machines Corporation | Transferring applications and session state to a secondary device |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6161193A (en) * | 1998-03-18 | 2000-12-12 | Lucent Technologies Inc. | Methods and apparatus for process replication/recovery in a distributed system |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6167253A (en) * | 1995-01-12 | 2000-12-26 | Bell Atlantic Network Services, Inc. | Mobile data/message/electronic mail download system utilizing network-centric protocol such as Java |
US6614781B1 (en) * | 1998-11-20 | 2003-09-02 | Level 3 Communications, Inc. | Voice over data telecommunications network architecture |
US6529504B1 (en) * | 1999-06-02 | 2003-03-04 | Sprint Communications Company, L.P. | Telecommunications service control point interface |
DE10014390C2 (de) * | 2000-03-23 | 2002-02-21 | Siemens Ag | Hochverfügbares Rechnersystem und Verfahren zur Umschaltung von Bearbeitungsprogrammen eines hochverfügbaren Rechnersystems |
-
2001
- 2001-10-04 DE DE10148875A patent/DE10148875A1/de not_active Withdrawn
-
2002
- 2002-10-01 BR BR0213061-0A patent/BR0213061A/pt not_active IP Right Cessation
- 2002-10-01 WO PCT/DE2002/003726 patent/WO2003032156A2/de not_active Application Discontinuation
- 2002-10-01 EP EP02774441A patent/EP1438658A2/de not_active Withdrawn
- 2002-10-01 US US10/491,526 patent/US20040237078A1/en not_active Abandoned
- 2002-10-01 CN CNA028197542A patent/CN1564979A/zh active Pending
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6161193A (en) * | 1998-03-18 | 2000-12-12 | Lucent Technologies Inc. | Methods and apparatus for process replication/recovery in a distributed system |
Non-Patent Citations (4)
Title |
---|
BHARAT K A ET AL: "Migratory applications" UIST '95. 8TH ANNUAL SYMPOSIUM ON USER INTERFACE SOFTWARE AND TECHNOLOGY. PROCEEDINGS OF THE ACM SYMPOSIUM ON USER INTERFACE SOFTWARE AND TECHNOLOGY. PITTSBURGH, PA, NOV. 14 - 17, 1995, ACM SYMPOSIUM ON USER INTERFACE SOFTWARE AND TECHNOLOGY, NEW YOR, 14. November 1995 (1995-11-14), Seiten 133-142, XP002186049 ISBN: 0-89791-709-X * |
CHU H, KURAKAKE S: "Roam (ResOurce-aware Application Migration) System" PROCEEDINGS OF THE 5TH WORLD MULTI-CONFERENCE ON SYSTEMICS, CYBERNETICS, AND INFORMATICS (SCI 2001), [Online] 22. - 25. Juli 2001, XP002254765 Orlando, Florida, USA Gefunden im Internet: <URL:http://www.csie.ntu.edu.tw/~hchu/pape rs/roam_sci2001.pdf> [gefunden am 2003-09-17] * |
MILOJICIC D S ET AL: "Process migration" ACM COMPUTING SURVEYS, SEPT. 2000, ACM, USA, Bd. 32, Nr. 3, Seiten 241-299, XP002254767 ISSN: 0360-0300 * |
NAKAJIMA T, AIZU H: "A Toolkit for Building Migratory Continuous Media Applications" PROCEEDINGS OF THE 8TH INTERNATIONAL WORKSHOP ON NETWORK AND OPERATING SYSTEMS SUPPORT FOR DIGITAL AUDIO AND VIDEO (NOSSDAV 98), [Online] 8. - 10. Juli 1998, XP002254766 Cambridge, UK Gefunden im Internet: <URL:http://www.cl.cam.ac.uk/Research/SRG/ nossdav98/papers/nossdav98-038.ps.gz> [gefunden am 2003-09-17] * |
Also Published As
Publication number | Publication date |
---|---|
US20040237078A1 (en) | 2004-11-25 |
BR0213061A (pt) | 2004-09-28 |
DE10148875A1 (de) | 2003-04-24 |
EP1438658A2 (de) | 2004-07-21 |
WO2003032156A3 (de) | 2003-12-31 |
CN1564979A (zh) | 2005-01-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
DE60014234T2 (de) | System und Verfahren zum Ermöglichen von Fehlertolerante Systeme | |
DE102004053597B4 (de) | Verfahren zum automatischen Erzeugen und/oder Steuern einer Telekommunikations-Konferenz mit einer Vielzahl von Teilnehmern, Telekommunikations-Konferenz-Endgerät und Telekommunikations-Konferenz-Servereinrichtung | |
DE60132232T2 (de) | Servicefähige technologie | |
DE102005016587B4 (de) | Verfahren zum Bilden einer gemeinsamen Kommunikationssitzung, Verfahren zum Bilden einer ersten Kommunikationssitzung und einer zweiten Kommunikationssitzung aus einer gemeinsamen Kommunikationssitzung und Kommunikationssitzungs-Steuerungs-Server | |
DE602004009947T2 (de) | Netzwerkentität zur verbindung von sip-endpunkten verschiedener fähigkeiten | |
WO2017093014A1 (de) | Verfahren zur industriellen kommunikation über tsn | |
DE102006031080A1 (de) | Verfahren und Kommunikationsendgerät zum Bereitstellen von VoIP | |
DE60304100T2 (de) | Erzwingung eines Zeitpunktes zur Trennung einer Kommmunikationsverbindung mit schnurlosen Endgeräten mit transienten Netzwerkadressen | |
EP1438658A2 (de) | Verfahren zum aktuellhalten von software auf verschiedenen endgeräten | |
DE10345051B4 (de) | Verfahren zum Aufbau einer Kommunikationsverbindung in einem direkt kommunizierenden Kommunikationsnetzwerk | |
WO2012084249A1 (de) | Verfahren zur integration von funktionen eines telekommunikationsnetzes in ein datennetz | |
DE60214399T2 (de) | Endgeräte, die so ausgelegt sind, dass sie als relaisserver zum verteilen von paketen in einem client-server-netzwerk wirken | |
EP1330139B1 (de) | Aufbau einer Kommunikationsverbindung zwischen einem Mobilfunk-Kommunikationsendgerät und einem gemäss des IP Protokolls arbeitenden Kommunikationsendgerät | |
EP2340641B1 (de) | Übertragen von ticker-information im multimediabereich | |
EP1853046B1 (de) | Verfahren zum Aufbau einer Kommunikationsverbindung in einem direkt kommunizierenden Kommunikationsnetzwerk | |
DE102006002434B3 (de) | Verfahren und Server zum Herstellen einer Kommunikationsverbindung zwischen Kommunikationsendgeräten | |
DE10148873B4 (de) | Verfahren zum Realisieren eines Verbindungsaufbaus zwischen über ein Kommunikationsnetzwerk verbindbaren Endgeräten | |
EP3959850B1 (de) | Verfahren zum bereitstellen von verbindungsherstellungsdaten sowie anordnung mit einer mehrzahl von kommunikationsservern und einem vermittler | |
EP1661357B1 (de) | Verfahren und vorrichtung zum umgang mit änderungen der netzwerkadresse bei mobiler datenübertragung | |
EP1452041B1 (de) | Verfahren und netzvorrichtung zum bereitstellen von insbesondere personalisierten kommunikationsdiensten in einem kommunikationssystem | |
DE60207056T2 (de) | System und Verfahren zur Datenteilung von einem WAP-Endgerät | |
EP2375852B1 (de) | Kommunikationsendgerät und Verfahren zur Datenübertragung zwischen einem Kommunikationsendgerät und einem Kommunikationssystem in einem Datennetz | |
WO2012076034A1 (de) | Verfahren zur überwachung eines kommunikationssystems | |
WO2007028701A1 (de) | Verfahren zum gezielten blockieren von diensten in einem ip multimedia subsystem | |
EP1833192A1 (de) | Übergabe des Zugriffs auf eine serverbasierte Anwendungssitzung an ein Kommunikationsendgerät |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A2 Designated state(s): BR CN |
|
AL | Designated countries for regional patents |
Kind code of ref document: A2 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FR GB GR IE IT LU MC NL PT SE SK TR |
|
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) | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2002774441 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 10491526 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 20028197542 Country of ref document: CN |
|
WWP | Wipo information: published in national office |
Ref document number: 2002774441 Country of ref document: EP |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: 2002774441 Country of ref document: EP |