SAP Patent Pricing and a Transport Management System

Size: px
Start display at page:

Download "SAP Patent Pricing and a Transport Management System"

Transcription

1 (19) (11) EP B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: Bulletin 08/ (1) Int Cl.: G06F 9/44 (06.01) G06F 9/44 (06.01) (21) Application number: 06.9 (22) Date of filing: (4) Method and computer system for effecting software maintenance in a software system landscape Rechnersystem und Verfahren zum Bewirken von Softwarewartung in einer Softwaresystemlandschaft Procédé et système informatique de maintenance logicielle dans un environnement de système logiciel (84) Designated Contracting States: AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PL PT RO SE SI SK TR (43) Date of publication of application: Bulletin 06/18 (73) Proprietor: SAP AG Walldorf (DE) (72) Inventors: Demuth, Michael Rauenberg (DE) Schulz, Volker Dr Heppenheim (DE) Stegmüller, Herbert Bruchsal (DE) (74) Representative: Sparing Röhl Henseler Patentanwälte European Patent Attorneys Rethelstrasse Düsseldorf (DE) (6) References cited: US-A US-A US-A US-A US-B IBM PUBLICATION CENTER: "Tivoli Software Distribution User s Guide 4.1 (GC )" INTERNET DISCLOSURE, 01, XP PATENT ABSTRACTS OF JAPAN vol. 00, no. 26, 1 July 02 ( ) & JP A (NEC CORP), 28 September 01 ( ) EP B1 Note: Within nine months of the publication of the mention of the grant of the European patent in the European Patent Bulletin, any person may give notice to the European Patent Office of opposition to that patent, in accordance with the Implementing Regulations. Notice of opposition shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention). Printed by Jouve, 7001 PARIS (FR)

2 1 EP B1 2 Description [0001] This invention relates generally to servicing of a software system landscape, and more particularly to a method for effecting software maintenance in a software system landscape and to a computer system. [0002] Complex software like applicant s SAP R/3 Release 4. (SAP) requires customization, i.e. selection of predefined functionality, and adaptation, i.e. addition of or amendment to functionality, as well as other servicing like program and data updates, cf. "SAP System Landscape Optimization" by A. Schneider-Neureither (Ed.), SAP Press, 04, ISBN , and "SAP R/3 Anderungs- und Transportmanagement" by Metzger and Röhrs, Galileo Press GmbH, Bonn, Germany, 4th reprint 04, ISBN X. [0003] Before such servicing may be performed, however, it has to be assured that the customizations, adaptations, program and data updates etc. are free of errors and integrate flawlessly into the software and data environment. In a factory for instance servicing errors are bound to result in costly workflow disruptions due to software malfunction or data corruption. Apart from the servicing side, other use of the software like training of new or inexperienced users may also result in a disruption of the productive system. [0004] Such complex software may therefore be implemented in form of separate logical systems that together form a system landscape. A typical implementation of the aforementioned SAP software for instance may, cf. Fig. 1, comprise a development system 1 for customizing and development work, a quality assurance system 2 for testing functionality using representative test data, a training system 3 for training new users, and several productive systems 4, e.g. each for a different factory, for actual productive use. Other or additional users and systems may be defined according to the particular requirements. [000] The logical systems are identical in large parts, function autonomously and may be run on a single computer. The quality assurance system 2 for example resembles the productive system 4 in that it provides all the functionality, its present data and additionally special test data. New customization settings or adaptations may thus be thoroughly tested in the quality assurance system 2 without jeopardizing the productive system 4. Likewise, the training system 3 resembles the productive system 4 in that it provides some of the functionality and special test data. A new user using the training system 3 may thus become accustomed to the functionality and observe the effect of his actions, albeit without disturbing the productive system 4. [0006] A transport management system connects the logical systems and serves to forward software services between systems of the system landscape via logical transport paths. A service may for example be approved in the development system 1 for export. It will then be forwarded to an input buffer of the quality assurance system 2. Import into the quality assurance system 2 is approved manually by an operator. Once the service has been imported into the quality assurance system 2, it will automatically be forwarded to an import buffer of the training system 3 and the productive systems 4 where it will be imported following manual approval by an operator. [0007] The operator is in charge of manually effecting the servicing. This requires an analysis of the system landscape layout, of the route that each service takes through the system landscape, project status switches in each system that define the respective system s changeability options, attributes in each service that define properties of the service etc. Import of services and other tasks are performed based on this analysis. [0008] This process is time consuming and bears the risk of errors. For example, care has to be taken to import services into a system in the correct order as illustrated by Fig. 2a and Fig. 2b. An original version 1 of the software and data is first modified by a first service 2, resulting in modified version 3, and subsequently by a second service 4, resulting in modified version, cf. Fig. 2a. However, if the second service 4 is imported before the first service 2, the original version 1 is changed into modified version 6 by the second service 4 and subsequently into modified version 7 by the first service 2, cf. Fig. 2b. The modified versions and 7 differ and the version 7 will not perform as intended. [0009] In view of the fact that an SAP R/3 implementation may comprise dozens of systems and require thousands of services per month during phases of change, the operator time required becomes considerable as does the risk for errors to occur. [00] Known from US-A is a computer system which is so configured as to be divided into a control system and an information system. The control system and the information system are connected via a transmission path. A centralized management of development and maintenance is performed by a software management system. [0011] Known from US-B is a software automatic distribution system for distributing software to machines arranged hierarchically at several levels, the software automatic distribution system comprising alternate machine information storage means for storing alternate machine information to distribute software to the alternate machine corresponding to a second machine if software distribution results in failure when software is distributed from a first machine to the second machine and software distribution means for distributing software based on the alternate machine information corresponding to the second machine read from the alternate machine information storage means if software distribution results in failure when software is distributed from the first machine to the second machine. [0012] It is therefore an object of the present invention to provide a method that overcomes these disadvantag- 2

3 3 EP B1 4 es. [0013] A further object of the invention is to provide a method that allows for an automated and centralized management of regular software maintenance. [0014] It is also an object of the present invention to provide a computer system with a software system landscape that overcomes the disadvantages of the prior art. [001] A further object of the invention is to provide a computer system that allows for an automated and centralized management of regular software maintenance. [0016] In one aspect of the invention, a method is provided according to claim 1. [0017] In a further aspect of the invention, a computer system is provided according to claim 7. [0018] In a still further aspect of the invention, a computer program product is provided according to claim 12. [0019] The invention thus provides for an automated generation of a hot fix instance with all tasks that are required for effecting a preliminary software service. The complexity is considerably reduced as the operator merely needs to approve automatically generated tasks. [00] Further embodiments of the invention are inferable from the following description and the claims. Fig. 1 shows a system landscape of the prior art. Fig. 2 illustrates a preliminary and a regular software service according to the prior art. Fig. 3 illustrates a system landscape according to the invention. Fig. 4 shows a preferred embodiment of the hardware of a computer system according to the invention. Fig. illustrates a list of tasks associated to system role types. Fig. 6 illustatres a maintenance instance. [0021] The embodiment shown in Fig. 3 illustrates an SAP R/3 Release 4. system landscape 0 with separate logical systems 1 that are here divided into a global part 2, e.g. at a main development a,d production facility, and local parts 3a, 3b, 3c, e.g. at other production facilities. [0022] The global part 2 preferably comprises at least a development system 1a for customizing and development work, a quality assurance system 1b for testing functionality using representative test data, and a productive system 1c for actual productive use. [0023] The local part 3a comprises a development system 1d for customizing and development work of local adaptations to SAP, e.g. to meet [0024] different legal requirements if part 3a is located in a different country than the global part 2. The local part 3a further comprises a quality assurance system 1 e for testing functionality using representative test data, a training system 1f for training new users, and a productive system 1g for actual productive use. [002] The local part 3b comprises a development system 1 h, a quality assurance system 1 j and a productive system 1 k, but no training system. The local part 3c is a two system landscape comprising a development system 1l and a productive system 1m only. [0026] The system landscape may be different according to the actual requirements. Fewer or more, different or differently connected or grouped systems 1 may be defined as needed. [0027] The logical systems 1 are identical in large parts and function autonomously. The quality assurance system 1 j for example resembles the productive system 1 k in that it provides all the functionality, its present data and additionally special test data. New customization settings or adaptations may thus be thoroughly tested in the quality assurance system 1j without jeopardizing the productive system 1 k. [0028] Each system 1 comprises an import buffer 4 for buffering incoming software services and means for communication with a central system 7. A transport management system connects the logical systems 1 and serves to route software services across the system landscape via logical directional transport paths 6. A service may for example relate to customization of a system 1, i.e. a selection of predefined functionality in the system 1, or an adaptation of a system 1, i.e. an addition of or amendment to functionality, or to program and data updates or the like. Transport tracks are provided that each define one or more particular routes for software services along the transport paths through the system landscape. A transport track may for example define the route from system 1 a through systems 1 b, 1 h, 1 j to system 1 k. Another transport track may define the route from system 1 d through systems 1e, 1f to system 1g. Transport tracks with branches may also be provided, e.g. from system 1 a to system 1 b and then in a first branch to system 1c and in a second branch to systems 1l, 1m. There may be more than one transport track per system landscape, each transport track being assigned to a project context like a development project for the local part 3a only or a documentation project for the global part 2 only etc. [0029] The systems 1 of each part 2, 3a, 3b, 3c and the central system 7 may be located and simultaneously executed in a single computer, but are preferably distributed across separate hardware. Preferably, the global part 2 and the local parts 3a, 3b, 3c each run on physically separate computer systems, which themselves may comprise different computers. [00] A preferred implementation of the local part 3a may comprise, cf. Fig. 4, a data base layer 1 for storing and retrieving business data like a factory inventory, employee data, sales figures etc. The data base layer 1 comprises one or more data base servers 2 and four data bases 3, one for each of the systems 1 d, 1 e, 1 f and 1 g. [0031] Connected to the data base layer 1 by a suit- 3

4 EP B1 6 able network 4, e.g. a LAN, is an application layer for execution of the software of the systems 1 d, 1 e, 1f and 1 g. The application layer comprises one or more application servers 6. [0032] Finally, connected to the application layer by a suitable network 7, e.g. a LAN, is a presentation layer 8 for the graphical user interface (GUI). The presentation layer 8 preferably comprises dumb terminals 9, Personal Computers 4 and/or wireless access devices 411 like PDAs. [0033] Each system 1 has associated therewith a system role which defines the respective system s function within the landscape. The system 1 a, 1 b and 1 c for example, have the roles "development system in the global part", "quality assurance system in the global part" and "productive system in the global part", respectively. The systems 1l and 1 m have the roles "development system in the local part 3c" and "productive system in the local part 3c", respectively. The other systems 1 have corresponding roles. In SAP, the system roles are typically defined in the Solution Manager for Implementation. [0034] According to the invention, system role types are provided. System role types may comprise the follwing: D Source systems: Transport requests comprising a software service are generated in a system of this type, usually a development system. O Follow-on system: A transport request is imported into a system of this type and forwarded to at least one other system. P Target system: A transport request is imported into a system of this type but not forwarded. Target systems are typically productive systems. R Postprocessing system: If the landscape comprises both a development and a maintenance system, any maintenance request must be fed back to the development system. This is not usually possible with a transport request because the objects in the maintenance system have a different status than the objects in the development system. A special manual procedure is required instead. [003] In the embodiment of Fig. 3 the development systems 1 a, 1 h, 1 d and 1 are of system role type D, the productive systems 1 c, 1k, 1 g and 1 m are of system role type P and the systems 1 b, 1 j, 1 e and 1 f between the development systems and the productive systems are of the system role type O. Other and/or additional system types may be provided. [0036] Tasks are assigned to system role types. The tasks may be marked as compulsory and may comprise the following: for type D: generate transport request with a software service - effect the software service - release transport request for forwarding for type O: - import transport request - notify quality management and await release for type P: - import transport request - notify quality management and await release - generate new maintenance instance - lock present maintenance instance - release new maintenance instance for type R: - inform operator [0037] In the example of Fig. a list 00 contains for the system role type D a task 01 to logon to a remote system, a task 02 to create a transport request for a software service, a task 03 to execute the software service in the remote system, and a task 04 to release the transport request to the system landscape. For the system role type O the list 00 comprises a task 0 to logon to a remote system, a task 06 import a software service and a task 07 to notify the users of the system about the import. For the system role type P the list 00 comprises a task 08 to logon to a remote system, a task 09 to halt a part of the system, a task to import a software service and a task 11 to resume the halted part of the system. Other and/or additional tasks as well as attributes like "compulsory" may be provided. For example, a task to collectively import software services, a task to check certain system properties, a task to check the status of a different system and, if the status indicates a first state, importing a software service, and if the status indicates a second state, not importing a software service but scheduling a new check at a different point in time, a task to check the interdependencies of software services in the buffer and to reorder them to avoid the problem illustrated by Fig. 2, etc. [0038] Based on the transport tracks, the system role types and the list 00, a maintenance instance is automatically generated preferably in the central system 7. The maintenance instance contains all tasks that are required for the periodic maintenance of the landscape. The tasks of a maintenance instance may be displayed, executed, managed, analyzed and documented from the central system 7 by suitable software, e.g. SAP s Schedule Manager. For that purpose, the tasks may provide spool lists, statuses, application logs, job logs etc. to the central system 7 or generate that information in the central system 7. [0039] The maintenance instance preferably has a hi- 4

5 7 EP B1 8 erarchical structure. The top level contains one entry per transport track. The next level contains one entry per system role type, preferably even in case that no system of corresponding type is defined. The next level contains one entry per system role, preferably only if this role is used by a system. The lowest level contains the tasks for each system. [00] An exemplary maintenance instance 600 is illustrated in Fig. 6 and has here a structure that is hierarchically grouped according to transport track 601, system role types 602, system roles 603, systems 604 and finally tasks 60. The tasks are associated to particular systems. The grouping allows to block and unblock groups of tasks. Preferably, the maintenance instance may be locked so that no further task may be performed in the locked maintenance system. [0041] According to the method of the invention, system roles and system role types are provided, the systems of the system landscape are associated to the system roles and a list of tasks is associated to system role types. At least one transport track is provided that defines a route for transport requests through a group of systems in a particular order and specifies one source system in which software services are permitted, adjacent interconnected systems, and at least one end or target system. A maintenance instance is generated from the system role types, the list and the transport tracks, the maintenance instance defining tasks for effecting a software service in a maintenance interval. This involves analyzing the transport tracks to identify the affected systems, analyzing the systems to identify their system roles, analyzing the system roles to identify their type, and compiling tasks for the affected systems according to the list. The tasks of the maintenance instance are then performed and may require authorization by the operator. The operator does not need to consider the system landscape and the transport tracks and other information to compile the tasks, but merely has to authorize steps of the maintenance instance. Preferably tasks of one level may only be executed once the tasks of the superior levels are released. At the end of the maintenance instance, when all tasks have been performed, i.e. all systems of the transport track have been serviced, the maintenance instance is locked and a new maintenance instance is generated and released for execution at the next maintenance interval. Claims 1. A method for effecting software maintenance in a software system landscape (0) comprising a central control system (7) and a plurality of logical systems (1) interconnected by logical transport paths (6), each logical system (1) having associated therewith one of a plurality of system roles, the method comprising the steps of: providing system role types, each system role type comprising a group of system roles; providing an association of tasks to system role types; providing a transport track; each software service relating to at least one of the code and the data of at least one system (1) in the landscape (0); generating automatically a maintenance instance (600) preferably in the central system (7) from the system role types, the association and the transport tracks, the maintenance instance (600) defining tasks for effecting a software service in a maintenance interval; characterized by the transport track defining a route for software services through a group of systems (1) subsequently and specifying one source system in which software services are permitted, adjacent interconnected systems, and at least one target system; wherein the step of generating the maintenance instance (600) involves analyzing the transport tracks to identify the affected systems (1), analyzing the systems (1) to identify their system roles, analyzing the system roles to identify their type, and compiling tasks for the affected systems (1) according to a list (00) which contains tasks for the different system role types; and carrying out the tasks in the respective affected system (1) after logon to the system (1). 2. The method of claim 1, wherein the maintenance instance (600) is generated with hierarchy levels. 3. The method of claim 2, wherein the hierarchy levels are generated to include a transport track level (601), a system role type level (602) below the transport track level (601), a system role level (603) below the system role type level (602), a system level (604) below the system role level (603) and a task level (60) below the system level (604). 4. The method of one of the claims 1 to 3, wherein as a system role type one of the group of source system, follow-on system, target system or postprocessing system is used.. The method of one of the claims 1 to 4, wherein the maintenance instance (600) is locked when it is completed and a new maintenance instance (600) is generated. 6. The method of one of the claims 1 to, wherein the tasks in the respective system (1) are executed from the central system (7).

6 9 EP B1 7. A computer system comprising: a central control system (7); a plurality of logical systems (1), each logical system (1) having associated therewith one of a plurality of system roles; logical transport paths (6) that interconnect the logical systems (1) to form a software system landscape (0); system role types, each system role being of a system role type; an association of tasks to system role types; a software service relating to at least one of the code and the data of at least one system (1) in the landscape (0); and a transport track; a maintenance instance (600) being automatically generated from the system role types, the association and the transport tracks, the maintenance instance (600) defining tasks for effecting a software service in a maintenance interval; characterized by the transport track being adapted to define a route for software services through a group of systems (1) subsequently and specifies one source system in which software services are permitted, adjacent interconnected systems, and at least one target system; wherein the generating of the maintenance instance (600) involves analyzing the transport tracks to identify the affected systems (1), analyzing the systems (1) to identify their system roles, analyzing the system roles to identify their type, and compiling tasks for the affected systems (1) according to a list (00) which contains tasks for the different system role types; and the computer system being adapted to carry out the tasks in the respective affected system (1) after logon to the system (1). 8. The system of claim 7, wherein the maintenance instance (600) comprises hierarchy levels. 9. The system of claim 8, wherein the hierarchy levels include a transport track level (601), a system role type level (602) below the transport track level (601), a system role level (603) below the system role type level (602), a system level (604) below the system role level (603) and a task level (60) below the system level (604).. The system of one of the claims 7 to 9, wherein the system role types comprise one of the group of source system, follow-on system, target system or postprocessing system. 11. The system of one of the claims 7 to, wherein the tasks in the respective system are executable from the central system (7). 12. A computer program product comprising on a storage medium a computer code that upon execution on a computer system performs the method according to one of the claims 1 to 6. Patentansprüche 1. Verfahren zum Ausführen einer Software-Wartung in einer Software-Systemlandschaft (0), die ein zentrales Steuersystem (7) und mehrere logische Systeme (1), die durch logische Transportpfade (6) miteinander verbunden sind, umfasst, wobei jedem logischen System (1) eine von mehreren Systemfunktionen zugeordnet ist, wobei das Verfahren die folgenden Schritte umfasst: Bereitstellen von Systemfunktion-Typen, wobei jeder Systemfunktion-Typ eine Gruppe von Systemfunktionen enthält; Bereitstellen einer Zuordnung von Aufgaben zu Systemfunktion-Typen; Bereitstellen eines Transportwegs; wobei jeder Software-Dienst mit dem Code und/ oder den Daten wenigstens eines Systems (1) in der Landschaft (0) in Beziehung steht; automatisches Erzeugen einer Wartungsinstanz (600) vorzugsweise in dem zentralen System (7) aus den Systemfunktion-Typen, der Zuordnung und den Transportwegen, wobei die Wartungsinstanz (600) Aufgaben zum Ausführen eines Software-Dienstes in einem Wartungsintervall definiert; dadurch gekennzeichnet, dass der Transportweg eine Route für Software-Dienste durch eine Gruppe von aufeinander folgenden Systemen (1) definiert und ein Quellsystem, in dem Software-Dienste zugelassen sind, miteinander verbundene benachbarte Systeme, und wenigstens ein Zielsystem spezifiziert; wobei der Schritt des Erzeugens der Wartungsinstanz (600) das Analysieren der Transportwege, um die betroffenen Systeme (1) zu identifizieren, das Analysieren der Systeme (1), um ihre Systemfunktionen zu identifizieren, das Analysieren der Systemfunktionen, um ihren Typ zu identifizieren, und das Kompilieren von Aufgaben für die betroffenen Systeme (1) in Übereinstimmung mit einer Liste (00), die Aufgaben für die verschiedenen Systemfunktion- Typen enthält, umfasst; und die Aufgaben in dem jeweiligen betroffenen System (1) nach dem Einloggen in das System 6

7 11 EP B1 12 (1) ausgeführt werden. 2. Verfahren nach Anspruch 1, wobei die Wartungsinstanz (600) mit Hierarchieniveaus erzeugt wird. 3. Verfahren nach Anspruch 2, wobei die Hierarchieniveaus so erzeugt werden, dass sie ein Transportweg-Niveau (601), ein Systemfunktion-Typ-Niveau (602) unter dem Transportweg-Niveau (601), ein Systemfunktion-Niveau (603) unter dem Systemfunktion-Typ-Niveau (602), ein System-Niveau (604) unter dem Systemfunktion-Niveau (603) und ein Aufgaben-Niveau (60) unter dem System-Niveau (604) enthalten. 4. Verfahren nach einem der Ansprüche 1 bis 3, wobei ein System aus der Gruppe, die aus Quellsystem, Folgesystem, Zielsystem und Nachverarbeitungssystem besteht, als ein Systemfunktion-Typ verwendet wird.. Verfahren nach einem der Ansprüche 1 bis 4, wobei die Wartungsinstanz (600) verriegelt wird, wenn sie abgeschlossen ist, und eine neue Wartungsinstanz (600) erzeugt wird. 6. Verfahren nach einem der Ansprüche 1 bis, wobei die Aufgaben in dem jeweiligen System (1) von dem zentralen System (7) ausgeführt werden. 7. Computersystem, das umfasst: ein zentrales Steuersystem (7); mehrere logische Systeme (1), wobei jedem logischen System (1) eine von mehreren Systemfunktionen zugeordnet ist; logische Transportpfade (6), die die logischen Systeme (1) miteinander verbinden, um eine Software-Systemlandschaft (0) zu bilden; Systemfunktion-Typen, wobei jede Systemfunktion von einem Systemfunktion-Typ ist; eine Zuordnung von Aufgaben zu Systemfunktion-Typen; einen Software-Dienst, der mit dem Code und/ oder den Daten wenigstens eines Systems (1) in der Landschaft (0) in Beziehung steht; und einen Transportweg; wobei eine Wartungsinstanz (600) aus den Systemfunktion-Typen, der Zuordnung und den Transportwegen automatisch erzeugt wird, wobei die Wartungsinstanz (600) Aufgaben zum Ausführen eines Software-Dienstes in einem Wartungsintervall definiert; dadurch gekennzeichnet, dass der Transportweg ausgelegt ist, um eine Route für Software-Dienste durch eine Gruppe von aufeinander folgenden Systemen (1) zu definieren und ein Quellsystem, in dem Software- Dienste zugelassen sind, miteinander verbundene benachbarte Systeme, und wenigstens ein Zielsystem zu spezifizieren; wobei das Erzeugen der Wartungsinstanz (600) das Analysieren der Transportwege, um die betroffenen Systeme (1) zu identifizieren, das Analysieren der Systeme (1), um ihre Systemfunktionen zu identifizieren, das Analysieren der Systemfunktionen, um ihren Typ zu identifizieren, und das Kompilieren von Aufgaben für die betroffenen Systeme (1) in Übereinstimmung mit einer Liste (00), die Aufgaben für die verschiedenen Systemfunktion-Typen enthält, umfasst; und das Computersystem ausgelegt ist, um die Aufgaben in dem jeweiligen betroffenen System (1) nach dem Einloggen in das System (1) auszuführen. 8. System nach Anspruch 7, wobei die Wartungsinstanz (600) Hierarchieniveaus enthält. 9. System nach Anspruch 8, wobei die Hierarchieniveaus ein Transportweg-Niveau (601), ein Systemfunktion-Typ-Niveau (602) unter dem Transportweg- Niveau (601), ein Systemfunktion-Niveau (603) unter dem Systemfunktion-Typ-Niveau (602), ein System-Niveau (604) unter dem Systemfunktion-Niveau (603) und ein Aufgaben-Niveau (60) unter dem System-Niveau (604) enthalten.. System nach einem der Ansprüche 7 bis 9, wobei die Systemfunktion-Typen ein System aus der Gruppe enthalten, die aus Quellsystem, Folgesystem, Zielsystem und Nachverarbeitungssystem besteht. 11. System nach einem der Ansprüche 7 bis, wobei die Aufgaben in dem jeweiligen System von dem zentralen System (7) ausführbar sind. 12. Computerprogrammprodukt, das in einem Speichermedium Computercode enthält, der bei Ausführung in einem Computersystem das Verfahren nach einem der Ansprüche 1 bis 6 ausführt. Revendications 1. Procédé permettant de réaliser une maintenance logicielle dans un paysage système logiciel (0) comprenant un système de commande central (7) et une pluralité de systèmes logiques (1) interconnectés par des chemins de transport logiques (6), chaque système logique (1) étant associé à un rôle système d une pluralité de rôles système, le procédé comprenant les étapes consistant à : 7

8 13 EP B1 14 fournir des types de rôles système, chaque type de rôle système comprenant un groupe de rôles système ; fournir une association de tâches aux types de rôles système ; fournir une piste de transport ; chaque service logiciel concernant au moins l un des codes et données d au moins un système (1) du paysage (0) ; générer automatiquement une instance de maintenance (600) de préférence dans le système central (7) à partir des types de rôles système, de l association et des pistes de transport, l instance de maintenance (600) définissant des tâches permettant de réaliser un service logiciel dans un intervalle de maintenance ; caractérisé en ce que : la piste de transport définit un itinéraire pour les services logiciels par le biais d un groupe de systèmes (1) par la suite et spécifie un système source dans lequel les services logiciels sont autorisés, des systèmes interconnectés adjacents, et au moins un système cible ; dans lequel l étape consistant à générer l instance de maintenance (600) implique l analyse des pistes de transport pour identifier les systèmes affectés (1), l analyse des systèmes (1) pour identifier leurs rôles système, l analyse des rôles système pour identifier leur type, et la compilation de tâches pour les systèmes affectés (1) en fonction d une liste (00) qui contient des tâches pour les différents types de rôles système, et réaliser les tâches dans le système affecté respectif (1) après une ouverture de session sur le système (1). 2. Procédé selon la revendication 1, dans lequel l instance de maintenance (600) est générée avec des niveaux hiérarchiques. 3. Procédé selon la revendication 2, dans lequel les niveaux hiérarchiques sont générés pour inclure un niveau de piste de transport (601), un niveau de type de rôle système (602) inférieur au niveau de piste de transport (601), un niveau de rôle système (603) inférieur au niveau de type de rôle système (602), un niveau de système (604) inférieur au niveau de rôle système (603) et un niveau de tâche (60) inférieur au niveau de système (604) Procédé selon l une quelconque des revendications 1 à 3, dans lequel en tant que type de rôle système, un élément du groupe composé d un système source, d un système de suivi d article, d un système cible et d un système de post-traitement est utilisé.. Procédé selon l une quelconque des revendications 1 à 4, dans lequel l instance de maintenance (600) est verrouillée lorsqu elle est terminée et une nouvelle instance de maintenance (600) est générée. 6. Procédé selon l une quelconque des revendications 1 à, dans lequel les tâches du système respectif (1) sont exécutées à partir du système central (7). 7. Système informatique comprenant : un système de commande central (7) ; une pluralité de systèmes logiques (1), chaque système logique (1) étant associé à un rôle système d une pluralité de rôles système ; des chemins de transport logiques (6) qui sont interconnectés avec les systèmes logiques (1) pour former un paysage système logiciel (0) ; des types de rôles système, chaque rôle système étant d un type de rôle système ; une association de tâches avec des types de rôles système ; un service logiciel lié à au moins l un des codes et données d au moins un système (1) du paysage (0) ; et une piste de transport ; une instance de maintenance (600) étant générée automatiquement à partir des types de rôles système, de l association et des pistes de transport, l instance de maintenance (600) définissant des tâches permettant de réaliser un service logiciel dans un intervalle de maintenance ; caractérisé en ce que : la piste de transport est conçue pour définir un itinéraire pour les services logiciels par le biais d un groupe de systèmes (1) par la suite et spécifie un système source dans lequel les services logiciels sont autorisés, des systèmes interconnectés adjacents et au moins un système cible ; dans lequel la génération de l instance de maintenance (600) implique l analyse des pistes de transport pour identifier les systèmes affectés (1), l analyse des systèmes (1) pour identifier leurs rôles système, l analyse des rôles système pour identifier leur type, et la compilation des tâches pour les systèmes affectés (1) en fonction d une liste (00) qui contient des tâches pour les différents types de rôles système ; et le système informatique étant conçu pour réaliser les tâches dans le système affecté 8

9 1 EP B1 16 respectif (1) après ouverture de session sur le système (1). 8. Système selon la revendication 7, dans lequel l instance de maintenance (600) comprend des niveaux hiérarchiques. 9. Système selon la revendication 8, dans lequel les niveaux hiérarchiques incluent un niveau de piste de transport (601), un niveau de type de rôle système (602) inférieur au niveau de piste de transport (601), un niveau de rôle système (603) inférieur au niveau de type de rôle système (602), un niveau de système (604) inférieur au niveau de rôle système (603) et un niveau de tâche (60) inférieur au niveau de système (604). 1. Système selon l une quelconque des revendications 7 à 9, dans lequel les types de rôles système comprennent un élément du groupe système source, système de suivi d article, système cible ou système de post-traitement. 11. Système selon l une quelconque des revendications 7 à, dans lequel les tâches du système respectif peuvent être exécutées à partir du système central (7) Produit de programme informatique comprenant sur un support de stockage un code informatique qui, lorsqu il est exécuté sur un système informatique, réalise le procédé selon l une quelconque des revendications 1 à

10 EP B1

11 EP B1 11

12 EP B1 12

13 EP B1 13

14 EP B1 14

15 EP B1 REFERENCES CITED IN THE DESCRIPTION This list of references cited by the applicant is for the reader s convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard. Patent documents cited in the description US A [00] US B1 [0011] Non-patent literature cited in the description SAP System Landscape Optimization. SAP Press, 04 [0002] METZGER ; RÖHRS. SAP R/3 Anderungs- und Transportmanagement. Galileo Press GmbH, 04 [0002] 1

(51) Int Cl.: B29C 41/20 (2006.01) F21S 4/00 (2006.01) H05K 3/28 (2006.01)

(51) Int Cl.: B29C 41/20 (2006.01) F21S 4/00 (2006.01) H05K 3/28 (2006.01) (19) TEPZZ 68698B_T (11) EP 2 68 698 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 18.11.201 Bulletin 201/47 (21) Application number: 11808612.3

More information

*EP001173363B1* EP 1 173 363 B1 (19) (11) EP 1 173 363 B1 (12) EUROPEAN PATENT SPECIFICATION

*EP001173363B1* EP 1 173 363 B1 (19) (11) EP 1 173 363 B1 (12) EUROPEAN PATENT SPECIFICATION (19) Europäisches Patentamt European Patent Office Office européen des brevets *EP001173363B1* (11) EP 1 173 363 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of

More information

TEPZZ_768 7_B_T EP 1 768 371 B1 (19) (11) EP 1 768 371 B1 (12) EUROPEAN PATENT SPECIFICATION. (51) Int Cl.: H04M 19/04 (2006.01)

TEPZZ_768 7_B_T EP 1 768 371 B1 (19) (11) EP 1 768 371 B1 (12) EUROPEAN PATENT SPECIFICATION. (51) Int Cl.: H04M 19/04 (2006.01) (19) TEPZZ_768 7_B_T (11) EP 1 768 371 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 1.01.2014 Bulletin 2014/03 (1) Int Cl.: H04M 19/04 (2006.01)

More information

(51) Int Cl.: G05F 3/26 (2006.01) G05F 3/24 (2006.01)

(51) Int Cl.: G05F 3/26 (2006.01) G05F 3/24 (2006.01) (19) Europäisches Patentamt European Patent Office Office européen des brevets (11) EP 1 280 033 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 31.0.2006

More information

(51) Int Cl.: G06F 13/38 (2006.01) G06F 1/16 (2006.01)

(51) Int Cl.: G06F 13/38 (2006.01) G06F 1/16 (2006.01) (19) TEPZZ 9777B_T (11) EP 2 97 77 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 1.07.1 Bulletin 1/29 (1) Int Cl.: G06F 13/38 (06.01) G06F 1/16 (06.01)

More information

(51) Int Cl.: H04L 9/32 (2006.01) G09C 1/00 (2006.01) G06F 21/33 (2013.01) H04L 29/06 (2006.01)

(51) Int Cl.: H04L 9/32 (2006.01) G09C 1/00 (2006.01) G06F 21/33 (2013.01) H04L 29/06 (2006.01) (19) TEPZZ Z48B_T (11) EP 2 2 048 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 13.0. Bulletin / (21) Application number: 1179238.6 (22) Date of

More information

(51) Int Cl.: G06F 1/00 (2006.01)

(51) Int Cl.: G06F 1/00 (2006.01) (19) (11) EP 0 972 234 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 0.09.07 Bulletin 07/36 (21) Application number: 98913219.6 (22) Date of filing:

More information

(51) Int Cl.: H04W 4/14 (2009.01)

(51) Int Cl.: H04W 4/14 (2009.01) (19) (12) EUROPEAN PATENT SPECIFICATION (11) EP 2 184 897 B1 (4) Date of publication and mention of the grant of the patent: 14.03.12 Bulletin 12/11 (21) Application number: 087774.3 (22) Date of filing:

More information

(51) Int Cl.: H04M 3/50 (2006.01)

(51) Int Cl.: H04M 3/50 (2006.01) (19) TEPZZ_Z48_64B_T (11) EP 1 048 164 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 07.01.1 Bulletin 1/02 (21) Application number: 9893133.0 (22)

More information

(51) Int Cl.: H04N 7/16 (2011.01)

(51) Int Cl.: H04N 7/16 (2011.01) (19) TEPZZ_796 89B_T (11) EP 1 796 389 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 04.03.1 Bulletin 1/ (1) Int Cl.: H04N 7/16 (11.01) (21) Application

More information

(51) Int Cl.: G06F 21/24 (2006.01)

(51) Int Cl.: G06F 21/24 (2006.01) (19) (12) EUROPEAN PATENT SPECIFICATION (11) EP 1 674 960 B1 (45) Date of publication and mention of the grant of the patent: 05..2011 Bulletin 2011/40 (51) Int Cl.: G06F 21/24 (2006.01) (21) Application

More information

(51) Int Cl.: H05K 1/02 (2006.01)

(51) Int Cl.: H05K 1/02 (2006.01) (19) (11) EP 1 229 767 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 20.01.2010 Bulletin 2010/03 (1) Int Cl.: H0K 1/02 (2006.01) (21) Application

More information

(51) Int Cl.: H04L 29/06 (2006.01) G06F 9/445 (2006.01) G06F 13/00 (2006.01)

(51) Int Cl.: H04L 29/06 (2006.01) G06F 9/445 (2006.01) G06F 13/00 (2006.01) (19) TEPZZ_7486_6B_T (11) EP 1 748 616 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 03.09.2014 Bulletin 2014/36 (1) Int Cl.: H04L 29/06 (2006.01)

More information

(51) Int Cl.: G10L 15/26 (2006.01)

(51) Int Cl.: G10L 15/26 (2006.01) (19) TEPZZ Z 8B_T (11) EP 2 023 338 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 28.0.14 Bulletin 14/22 (1) Int Cl.: GL /26 (06.01) (21) Application

More information

(51) Int Cl.: H04L 29/06 (2006.01) H04L 12/22 (2006.01)

(51) Int Cl.: H04L 29/06 (2006.01) H04L 12/22 (2006.01) (19) (11) EP 0 998 091 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 31.01.07 Bulletin 07/0 (1) Int Cl.: H04L 29/06 (06.01) H04L 12/22 (06.01) (21)

More information

(51) Int Cl.: G06F 21/00 (2006.01) H04L 29/06 (2006.01)

(51) Int Cl.: G06F 21/00 (2006.01) H04L 29/06 (2006.01) (19) TEPZZ_8Z_7 _B_T (11) EP 1 801 721 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 16.06. Bulletin /24 (1) Int Cl.: G06F 21/00 (06.01) H04L 29/06

More information

(51) Int Cl.: G06F 17/30 (2006.01)

(51) Int Cl.: G06F 17/30 (2006.01) (19) TEPZZ 7 _B_T (11) EP 1 127 321 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 03.04.13 Bulletin 13/14 (21) Application number: 99948341. (22)

More information

The Advantialer and Its Advantages

The Advantialer and Its Advantages (19) TEPZZ Z B_T (11) EP 2 0 113 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 16.09.1 Bulletin 1/38 (21) Application number: 07809477.8 (22) Date

More information

(51) Int Cl.: H04L 12/56 (2006.01)

(51) Int Cl.: H04L 12/56 (2006.01) (19) (11) EP 1 779 90 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 28.12.11 Bulletin 11/2 (21) Application number: 0783482.2 (22) Date of filing:

More information

(51) Int Cl.: G06F 11/20 (2006.01)

(51) Int Cl.: G06F 11/20 (2006.01) (19) TEPZZ 66_ B_T (11) EP 2 366 13 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 13.0.201 Bulletin 201/20 (21) Application number: 08878183.6 (22)

More information

(51) Int Cl.: H04L 12/00 (2006.01)

(51) Int Cl.: H04L 12/00 (2006.01) (19) (11) EP 2 119 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 14.12.11 Bulletin 11/0 (21) Application number: 0789037.9 (22) Date of filing: 14.12.07

More information

(51) Int Cl.: G01C 21/36 (2006.01)

(51) Int Cl.: G01C 21/36 (2006.01) (19) TEPZZ_ 678B_T (11) EP 1 26 78 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent:.09.14 Bulletin 14/37 (1) Int Cl.: G01C 21/36 (06.01) (21) Application

More information

(51) Int Cl.: G08G 1/14 (2006.01) G07B 15/02 (2006.01) G10L 15/28 (2006.01)

(51) Int Cl.: G08G 1/14 (2006.01) G07B 15/02 (2006.01) G10L 15/28 (2006.01) (19) (12) EUROPEAN PATENT SPECIFICATION (11) EP 1 862 986 B1 (4) Date of publication and mention of the grant of the patent: 14.07. Bulletin /28 (1) Int Cl.: G08G 1/14 (06.01) G07B 1/02 (06.01) GL 1/28

More information

(51) Int Cl. 7 : G03G 15/00

(51) Int Cl. 7 : G03G 15/00 (19) Europäisches Patentamt European Patent Office Office européen des brevets *EP001179B1* (11) EP 1 17 9 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the

More information

(51) Int Cl.: G06F 9/455 (2006.01) G06F 9/50 (2006.01)

(51) Int Cl.: G06F 9/455 (2006.01) G06F 9/50 (2006.01) (19) TEPZZ 6987 B_T (11) EP 2 698 711 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 0.08.1 Bulletin 1/32 (21) Application number: 118777.8 (22) Date

More information

TEPZZ 5Z _9_B_T EP 2 502 191 B1 (19) (11) EP 2 502 191 B1 (12) EUROPEAN PATENT SPECIFICATION

TEPZZ 5Z _9_B_T EP 2 502 191 B1 (19) (11) EP 2 502 191 B1 (12) EUROPEAN PATENT SPECIFICATION (19) TEPZZ Z _9_B_T (11) EP 2 02 191 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 17.06.1 Bulletin 1/2 (21) Application number: 787872.0 (22) Date

More information

(51) Int Cl.: G06F 17/30 (2006.01)

(51) Int Cl.: G06F 17/30 (2006.01) (19) (11) EP 1 426 877 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent:.09. Bulletin /37 (1) Int Cl.: G06F 17/ (06.01) (21) Application number: 026013.7

More information

TEPZZ_9 6Z46B_T EP 1 926 046 B1 (19) (11) EP 1 926 046 B1 (12) EUROPEAN PATENT SPECIFICATION. (51) Int Cl.:

TEPZZ_9 6Z46B_T EP 1 926 046 B1 (19) (11) EP 1 926 046 B1 (12) EUROPEAN PATENT SPECIFICATION. (51) Int Cl.: (19) TEPZZ_9 6Z46B_T (11) EP 1 926 046 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 21.08.13 Bulletin 13/34 (1) Int Cl.: G06F 19/00 (11.01) (21)

More information

(51) Int Cl.: H04N 7/15 (2006.01) H04N 7/18 (2006.01)

(51) Int Cl.: H04N 7/15 (2006.01) H04N 7/18 (2006.01) (19) TEPZZ_4967ZZB_T (11) EP 1 496 700 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 1.01.14 Bulletin 14/03 (1) Int Cl.: H04N 7/1 (06.01) H04N 7/18

More information

(51) Int Cl.: G06F 17/30 (2006.01)

(51) Int Cl.: G06F 17/30 (2006.01) (19) (11) EP 1 6 23 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 2.11.09 Bulletin 09/48 (1) Int Cl.: G06F 17/ (06.01) (21) Application number: 014696.1

More information

(51) Int Cl.: H04L 29/06 (2006.01)

(51) Int Cl.: H04L 29/06 (2006.01) (19) (11) EP 2 07 816 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 04.0.11 Bulletin 11/18 (21) Application number: 07804833.7 (22) Date of filing:

More information

(51) Int Cl.: H04L 12/24 (2006.01)

(51) Int Cl.: H04L 12/24 (2006.01) (19) (12) EUROPEAN PATENT SPECIFICATION (11) EP 1 487 11 B1 (4) Date of publication and mention of the grant of the patent: 01.07.09 Bulletin 09/27 (1) Int Cl.: H04L 12/24 (06.01) (21) Application number:

More information

(56) References cited:

(56) References cited: (19) (12) EUROPEAN PATENT SPECIFICATION (11) EP 1 371 26 B1 (4) Date of publication and mention of the grant of the patent: 21.01.09 Bulletin 09/04 (21) Application number: 02711612.8 (22) Date of filing:

More information

EP 1 976 249 B1 (19) (11) EP 1 976 249 B1 (12) EUROPEAN PATENT SPECIFICATION

EP 1 976 249 B1 (19) (11) EP 1 976 249 B1 (12) EUROPEAN PATENT SPECIFICATION (19) (11) EP 1 976 249 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 11.03.09 Bulletin 09/11 (1) Int Cl.: H04M 1/72 (06.01) G06F 9/44 (06.01) H04W

More information

(51) Int Cl.: G06F 17/00 (2006.01) G06F 11/20 (2006.01)

(51) Int Cl.: G06F 17/00 (2006.01) G06F 11/20 (2006.01) (19) Europäisches Patentamt European Patent Office Office européen des brevets (11) EP 1 388 08 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 29.11.06

More information

(51) Int Cl.: H04L 12/24 (2006.01)

(51) Int Cl.: H04L 12/24 (2006.01) (19) TEPZZ_8_9Z96B_T (11) EP 1 819 096 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 24..12 Bulletin 12/43 (21) Application number: 0818628.9 (22)

More information

(51) Int Cl.: C08K 5/523 (2006.01) C08K 5/521 (2006.01) C08K 5/52 (2006.01) C08G 64/00 (2006.01)

(51) Int Cl.: C08K 5/523 (2006.01) C08K 5/521 (2006.01) C08K 5/52 (2006.01) C08G 64/00 (2006.01) (19) Europäisches Patentamt European Patent Office Office européen des brevets (11) EP 0 78 966 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 01.03.06

More information

(51) Int Cl.: H04L 9/24 (2006.01) G06Q 10/00 (2012.01)

(51) Int Cl.: H04L 9/24 (2006.01) G06Q 10/00 (2012.01) (19) TEPZZ_4Z 68ZB_T (11) EP 1 2 680 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 01.04.1 Bulletin 1/14 (21) Application number: 02741722.9 (22)

More information

(51) Int Cl.: G06F 21/53 (2013.01)

(51) Int Cl.: G06F 21/53 (2013.01) (19) TEPZZ 4_4 B_T (11) EP 2 41 43 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 17.12.14 Bulletin 14/1 (1) Int Cl.: G06F 21/3 (13.01) (21) Application

More information

(51) Int Cl.: G06F 1/00 (2006.01)

(51) Int Cl.: G06F 1/00 (2006.01) (19) TEPZZ_4 Z4ZB_T (11) EP 1 433 040 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 11.11.201 Bulletin 201/46 (21) Application number: 0277267.9

More information

(51) Int Cl.: H04L 9/32 (2006.01) H04B 7/00 (2006.01) A61N 1/37 (2006.01)

(51) Int Cl.: H04L 9/32 (2006.01) H04B 7/00 (2006.01) A61N 1/37 (2006.01) (19) TEPZZ_4977B_T (11) EP 1 49 77 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent:.12.14 Bulletin 14/0 (21) Application number: 03723989.4 (22) Date

More information

(51) Int Cl.: H04B 3/23 (2006.01)

(51) Int Cl.: H04B 3/23 (2006.01) (19) (11) EP 0 983 638 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 21.03.12 Bulletin 12/12 (21) Application number: 989232.7 (22) Date of filing:

More information

*EP000961991B1* EP 0 961 991 B1 (19) (11) EP 0 961 991 B1 (12) EUROPEAN PATENT SPECIFICATION

*EP000961991B1* EP 0 961 991 B1 (19) (11) EP 0 961 991 B1 (12) EUROPEAN PATENT SPECIFICATION (19) Europäisches Patentamt European Patent Office Office européen des brevets *EP000961991B1* (11) EP 0 961 991 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of

More information

(51) Int Cl.: H04L 12/58 (2006.01)

(51) Int Cl.: H04L 12/58 (2006.01) (19) (11) EP 1 628 448 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 21.11.07 Bulletin 07/47 (1) Int Cl.: H04L 12/8 (06.01) (21) Application number:

More information

(51) Int Cl.: H04L 12/26 (2006.01)

(51) Int Cl.: H04L 12/26 (2006.01) (19) TEPZZ 84 8B_T (11) EP 2 84 338 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 23.09.1 Bulletin 1/39 (1) Int Cl.: H04L 12/26 (06.01) (21) Application

More information

(51) Int Cl.: H04L 12/24 (2006.01) G06F 9/445 (2006.01)

(51) Int Cl.: H04L 12/24 (2006.01) G06F 9/445 (2006.01) (19) (12) EUROPEAN PATENT SPECIFICATION (11) EP 1 978 672 B1 (4) Date of publication and mention of the grant of the patent: 01.09. Bulletin /3 (1) Int Cl.: H04L 12/24 (06.01) G06F 9/44 (06.01) (21) Application

More information

TEPZZ 87_546A T EP 2 871 546 A2 (19) (11) EP 2 871 546 A2 (12) EUROPEAN PATENT APPLICATION. (51) Int Cl.: G05B 19/05 (2006.01)

TEPZZ 87_546A T EP 2 871 546 A2 (19) (11) EP 2 871 546 A2 (12) EUROPEAN PATENT APPLICATION. (51) Int Cl.: G05B 19/05 (2006.01) (19) TEPZZ 87_46A T (11) EP 2 871 46 A2 (12) EUROPEAN PATENT APPLICATION (43) Date of publication: 13.0.1 Bulletin 1/ (1) Int Cl.: G0B 19/0 (06.01) (21) Application number: 14188238.1 (22) Date of filing:

More information

(51) Int Cl. 7 : H04B 7/185, H04B 1/40. (56) References cited: WO-A-00/03494

(51) Int Cl. 7 : H04B 7/185, H04B 1/40. (56) References cited: WO-A-00/03494 (19) Europäisches Patentamt European Patent Office Office européen des brevets *EP001363412B1* (11) EP 1 363 412 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of

More information

(51) Int Cl.: H04L 29/06 (2006.01)

(51) Int Cl.: H04L 29/06 (2006.01) (19) TEPZZ Z9 96 B_T (11) EP 2 093 962 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 19.12.12 Bulletin 12/1 (21) Application number: 08800984.0 (22)

More information

(51) Int Cl.: H04L 29/06 (2006.01) H04M 3/56 (2006.01) H04M 3/44 (2006.01) H04L 12/18 (2006.01)

(51) Int Cl.: H04L 29/06 (2006.01) H04M 3/56 (2006.01) H04M 3/44 (2006.01) H04L 12/18 (2006.01) (19) TEPZZ Z9 79B_T (11) EP 2 091 179 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 17.12.14 Bulletin 14/1 (21) Application number: 07817029.7 (22)

More information

(51) Int Cl.: G06F 9/46 (2006.01) H04L 12/56 (2006.01)

(51) Int Cl.: G06F 9/46 (2006.01) H04L 12/56 (2006.01) (19) (11) EP 1 611 23 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 21.0.08 Bulletin 08/21 (21) Application number: 0471948.2 (22) Date of filing:

More information

(51) Int Cl.: H04N 1/19 (2006.01) H04N 3/15 (2006.01) H04N 9/04 (2006.01)

(51) Int Cl.: H04N 1/19 (2006.01) H04N 3/15 (2006.01) H04N 9/04 (2006.01) (19) (12) EUROPEAN PATENT SPECIFICATION (11) EP 1 417 829 B1 (45) Date of publication and mention of the grant of the patent: 08.04.2009 Bulletin 2009/15 (21) Application number: 02751534.5 (22) Date of

More information

(51) Int Cl.: G06F 13/42 (2006.01)

(51) Int Cl.: G06F 13/42 (2006.01) (19) TEPZZ 67487_B_T (11) EP 2 674 871 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 04.03.201 Bulletin 201/ (1) Int Cl.: G06F 13/42 (2006.01) (21)

More information

(51) Int Cl.: H04L 12/46 (2006.01) H04L 29/14 (2006.01) H04L 29/12 (2006.01)

(51) Int Cl.: H04L 12/46 (2006.01) H04L 29/14 (2006.01) H04L 29/12 (2006.01) (19) (11) EP 1 342 344 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 03.06.09 Bulletin 09/23 (21) Application number: 019639.0 (22) Date of filing:.08.01

More information

(51) Int Cl.: G06F 11/14 (2006.01) G06F 17/30 (2006.01)

(51) Int Cl.: G06F 11/14 (2006.01) G06F 17/30 (2006.01) (19) TEPZZ_97799B_T (11) EP 1 97 799 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 06.0. Bulletin /19 (1) Int Cl.: G06F 11/14 (06.01) G06F 17/ (06.01)

More information

(51) Int Cl.: H04M 3/42 (2006.01) H04Q 3/00 (2006.01)

(51) Int Cl.: H04M 3/42 (2006.01) H04Q 3/00 (2006.01) (19) (11) EP 1 696 646 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 07.03.12 Bulletin 12/ (1) Int Cl.: H04M 3/42 (06.01) H04Q 3/00 (06.01) (21)

More information

(51) Int Cl.: H04Q 7/22 (2006.01) (56) References cited:

(51) Int Cl.: H04Q 7/22 (2006.01) (56) References cited: (19) Europäisches Patentamt European Patent Office Office européen des brevets (12) EUROPEAN PATENT SPECIFICATION (11) EP 1 2 414 B1 (4) Date of publication and mention of the grant of the patent:.08.06

More information

(51) Int Cl.: G08B 21/02 (2006.01) H04M 11/04 (2006.01)

(51) Int Cl.: G08B 21/02 (2006.01) H04M 11/04 (2006.01) (19) Europäisches Patentamt European Patent Office Office européen des brevets (11) EP 1 224 642 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 1.03.06

More information

(51) Int Cl.: H04L 12/46 (2006.01)

(51) Int Cl.: H04L 12/46 (2006.01) (19) (11) EP 1 892 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 19.12.07 Bulletin 07/1 (21) Application number: 0374778. (22) Date of filing: 09.09.03

More information

(51) Int Cl. 7 : G06F 11/22

(51) Int Cl. 7 : G06F 11/22 (19) Europäisches Patentamt European Patent Office Office européen des brevets *EP00084463B1* (11) EP 0 844 63 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of

More information

(51) Int Cl.: G06F 11/14 (2006.01) G06F 12/08 (2006.01)

(51) Int Cl.: G06F 11/14 (2006.01) G06F 12/08 (2006.01) (19) TEPZZ 488949B_T (11) EP 2 488 949 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 07.0.14 Bulletin 14/19 (21) Application number: 76367.4 (22)

More information

TEPZZ_965577B_T EP 1 965 577 B1 (19) (11) EP 1 965 577 B1 (12) EUROPEAN PATENT SPECIFICATION. (51) Int Cl.: H04M 3/523 (2006.01)

TEPZZ_965577B_T EP 1 965 577 B1 (19) (11) EP 1 965 577 B1 (12) EUROPEAN PATENT SPECIFICATION. (51) Int Cl.: H04M 3/523 (2006.01) (19) TEPZZ_9677B_T (11) EP 1 96 77 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent:.04.14 Bulletin 14/18 (1) Int Cl.: H04M 3/23 (06.01) (21) Application

More information

(56) References cited:

(56) References cited: (19) (12) EUROPEAN PATENT SPECIFICATION (11) EP 1 04 B1 (4) Date of publication and mention of the grant of the patent: 26.12.07 Bulletin 07/2 (21) Application number: 03742391.0 (22) Date of filing: 02.07.03

More information

(51) Int Cl.: G06Q 10/00 (2006.01)

(51) Int Cl.: G06Q 10/00 (2006.01) (19) (11) EP 1 69 282 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 2.03.09 Bulletin 09/13 (21) Application number: 048.1 (22) Date of filing: 29.11.04

More information

(51) Int Cl.: H04M 3/51 (2006.01)

(51) Int Cl.: H04M 3/51 (2006.01) (19) TEPZZ_976 B_T (11) EP 1 976 2 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 18.03.1 Bulletin 1/12 (1) Int Cl.: H04M 3/1 (06.01) (21) Application

More information

TEPZZ 65Z79 A_T EP 2 650 793 A1 (19) (11) EP 2 650 793 A1. (12) EUROPEAN PATENT APPLICATION published in accordance with Art.

TEPZZ 65Z79 A_T EP 2 650 793 A1 (19) (11) EP 2 650 793 A1. (12) EUROPEAN PATENT APPLICATION published in accordance with Art. (19) TEPZZ 65Z79 A_T (11) EP 2 650 793 A1 (12) EUROPEAN PATENT APPLICATION published in accordance with Art. 153(4) EPC (43) Date of publication: 16.10.2013 Bulletin 2013/42 (21) Application number: 12818771.3

More information

(51) Int Cl.: H04L 29/12 (2006.01)

(51) Int Cl.: H04L 29/12 (2006.01) (19) (11) EP 1 4 260 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent:.09.08 Bulletin 08/37 (1) Int Cl.: H04L 29/12 (06.01) (21) Application number:

More information

(51) Int Cl.: G06F 9/445 (2006.01)

(51) Int Cl.: G06F 9/445 (2006.01) (19) TEPZZ_649648B_T (11) EP 1 649 648 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 1..14 Bulletin 14/42 (21) Application number: 0476769.8 (22)

More information

(51) Int Cl.: H04L 29/06 (2006.01)

(51) Int Cl.: H04L 29/06 (2006.01) (19) Europäisches Patentamt European Patent Office Office européen des brevets (11) EP 1 146 711 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 13.09.06

More information

(51) Int Cl.: H04L 29/08 (2006.01) H04L 29/06 (2006.01)

(51) Int Cl.: H04L 29/08 (2006.01) H04L 29/06 (2006.01) (19) TEPZZ_897 6B_T (11) EP 1 897 336 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 12.08.1 Bulletin 1/33 (21) Application number: 06779738.1 (22)

More information

(51) Int Cl.: H04L 29/06 (2006.01) H04Q 7/24 (2006.01) H04L 12/66 (2006.01)

(51) Int Cl.: H04L 29/06 (2006.01) H04Q 7/24 (2006.01) H04L 12/66 (2006.01) (19) (11) EP 1 314 291 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent:..07 Bulletin 07/41 (21) Application number: 0194907.2 (22) Date of filing: 06.07.01

More information

(51) Int Cl.: G05B 19/05 (2006.01)

(51) Int Cl.: G05B 19/05 (2006.01) (19) (11) EP 1 291 74 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent:.06.07 Bulletin 07/2 (1) Int Cl.: G0B 19/0 (06.01) (21) Application number: 078479.9

More information

(51) Int Cl.: H04W 8/16 (2009.01) H04L 29/12 (2006.01) H04W 8/18 (2009.01)

(51) Int Cl.: H04W 8/16 (2009.01) H04L 29/12 (2006.01) H04W 8/18 (2009.01) (19) TEPZZ 474_77B_T (11) EP 2 474 177 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 0.11.14 Bulletin 14/4 (21) Application number: 747648.3 (22)

More information

(51) Int Cl. 7 : F16K 11/044, F16K 11/04

(51) Int Cl. 7 : F16K 11/044, F16K 11/04 (19) Europäisches Patentamt European Patent Office Office européen des brevets *EP0078182B1* (11) EP 1 078 182 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of

More information

TEPZZ 9 Z5A_T EP 2 922 305 A1 (19) (11) EP 2 922 305 A1. (12) EUROPEAN PATENT APPLICATION published in accordance with Art.

TEPZZ 9 Z5A_T EP 2 922 305 A1 (19) (11) EP 2 922 305 A1. (12) EUROPEAN PATENT APPLICATION published in accordance with Art. (19) TEPZZ 9 ZA_T (11) EP 2 922 A1 (12) EUROPEAN PATENT APPLICATION published in accordance with Art. 13(4) EPC (43) Date of publication: 23.09.1 Bulletin 1/39 (21) Application number: 1386446.2 (22) Date

More information

(51) Int Cl.: H04L 29/06 (2006.01) H04M 15/00 (2006.01)

(51) Int Cl.: H04L 29/06 (2006.01) H04M 15/00 (2006.01) (19) TEPZZ 7Z 74 B_T (11) EP 2 702 742 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent:.04. Bulletin /16 (21) Application number: 1171674.6 (22) Date

More information

(51) Int Cl.: H04L 12/26 (2006.01) H04L 12/24 (2006.01)

(51) Int Cl.: H04L 12/26 (2006.01) H04L 12/24 (2006.01) (19) TEPZZ 4 686 B_T (11) EP 2 426 862 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 12.08.1 Bulletin 1/33 (21) Application number: 769368.1 (22)

More information

Europaisches Patentamt European Patent Office Office europeen des brevets (11) EP 0 219 886 B2

Europaisches Patentamt European Patent Office Office europeen des brevets (11) EP 0 219 886 B2 Europaisches Patentamt European Patent Office Office europeen des brevets (11) EP 0 219 886 B2 (12) NEW EUROPEAN PATENT SPECIFICATION (45) Date of publication and mention (51) Int CI.6: G07G 1/12 of the

More information

(51) Int Cl.: G01S 7/52 (2006.01)

(51) Int Cl.: G01S 7/52 (2006.01) (19) (11) EP 0 92 48 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 18.08. Bulletin /33 (1) Int Cl.: G01S 7/2 (06.01) (21) Application number: 993172.3

More information

(51) Int Cl.: G04B 19/08 (2006.01)

(51) Int Cl.: G04B 19/08 (2006.01) (19) (11) EP 1 988 432 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 0.10.2011 Bulletin 2011/40 (21) Application number: 0771278.9 (22) Date of filing:

More information

TEPZZ_ 8_69B_T EP 1 338 169 B1 (19) (11) EP 1 338 169 B1 (12) EUROPEAN PATENT SPECIFICATION

TEPZZ_ 8_69B_T EP 1 338 169 B1 (19) (11) EP 1 338 169 B1 (12) EUROPEAN PATENT SPECIFICATION (19) TEPZZ_ 8_69B_T (11) EP 1 338 169 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 27.03.13 Bulletin 13/13 (21) Application number: 01997179. (22)

More information

(51) Int Cl.: H04L 12/66 (2006.01)

(51) Int Cl.: H04L 12/66 (2006.01) (19) (12) EUROPEAN PATENT SPECIFICATION (11) EP 1 73 43 B1 (4) Date of publication and mention of the grant of the patent: 18.01.12 Bulletin 12/03 (21) Application number: 02792. (22) Date of filing: 26.12.02

More information

EP 2 492 881 A2 (19) (11) EP 2 492 881 A2 (12) EUROPEAN PATENT APPLICATION. (43) Date of publication: 29.08.2012 Bulletin 2012/35

EP 2 492 881 A2 (19) (11) EP 2 492 881 A2 (12) EUROPEAN PATENT APPLICATION. (43) Date of publication: 29.08.2012 Bulletin 2012/35 (19) (12) EUROPEAN PATENT APPLICATION (11) EP 2 492 881 A2 (43) Date of publication: 29.08.2012 Bulletin 2012/35 (51) Int Cl.: G08B 13/16 (2006.01) G08B 25/08 (2006.01) (21) Application number: 12386006.6

More information

(51) Int Cl.: H04L 29/06 (2006.01) (56) References cited:

(51) Int Cl.: H04L 29/06 (2006.01) (56) References cited: (19) (11) EP 1 4 48 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 06.08.08 Bulletin 08/32 (21) Application number: 02776379.6 (22) Date of filing:..02

More information

(51) Int Cl.: B61K 9/12 (2006.01)

(51) Int Cl.: B61K 9/12 (2006.01) (19) (11) EP 2 001 722 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 21.12.11 Bulletin 11/1 (21) Application number: 077926.6 (22) Date of filing:

More information

(51) Int Cl.: G06F 12/14 (2006.01) G06F 17/00 (2006.01) H04M 1/66 (2006.01) G06F 1/00 (2006.01)

(51) Int Cl.: G06F 12/14 (2006.01) G06F 17/00 (2006.01) H04M 1/66 (2006.01) G06F 1/00 (2006.01) (19) Europäisches Patentamt European Patent Office Office européen des brevets (11) EP 1 221 098 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 07.06.06

More information

(51) Int Cl.: B65D 1/26 (2006.01) B31B 43/00 (2006.01) B65D 1/34 (2006.01) B21D 22/20 (2006.01) B21D 51/18 (2006.01)

(51) Int Cl.: B65D 1/26 (2006.01) B31B 43/00 (2006.01) B65D 1/34 (2006.01) B21D 22/20 (2006.01) B21D 51/18 (2006.01) (19) TEPZZ 4779ZZB_T (11) EP 2 477 900 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 12.08.20 Bulletin 20/33 (21) Application number: 776.8 (22)

More information

Title (fr) SOURCE IONIQUE INTERNE DOUBLE POUR PRODUCTION DE FAISCEAU DE PARTICULES AVEC UN CYCLOTRON

Title (fr) SOURCE IONIQUE INTERNE DOUBLE POUR PRODUCTION DE FAISCEAU DE PARTICULES AVEC UN CYCLOTRON Title (en) A TWIN INTERNAL ION SOURCE FOR PARTICLE BEAM PRODUCTION WITH A CYCLOTRON Title (de) DOPPELTE INTERNE IONENQUELLE FÜR PARTIKELSTRAHLHERSTELLUNG MIT EINEM ZYKLOTRON Title (fr) SOURCE IONIQUE INTERNE

More information

(51) Int Cl.: H04L 29/02 (2006.01) H04L 12/801 (2013.01)

(51) Int Cl.: H04L 29/02 (2006.01) H04L 12/801 (2013.01) (19) TEPZZ 7 48ZB_T (11) EP 2 72 480 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 03.12.2014 Bulletin 2014/49 (21) Application number: 11784039.7

More information

(51) Int Cl.: H04L 9/08 (2006.01)

(51) Int Cl.: H04L 9/08 (2006.01) (19) (11) EP 1 3 44 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 17..07 Bulletin 07/42 (1) Int Cl.: H04L 9/08 (06.01) (21) Application number: 0321967.0

More information

(51) Int Cl.: G06F 9/50 (2006.01) G06F 9/48 (2006.01)

(51) Int Cl.: G06F 9/50 (2006.01) G06F 9/48 (2006.01) (19) TEPZZ Z4878B_T (11) EP 2 048 78 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent:.04.13 Bulletin 13/ (1) Int Cl.: G06F 9/0 (06.01) G06F 9/48 (06.01)

More information

(51) Int Cl.: H04L 29/06 (2006.01) H04L 29/12 (2006.01)

(51) Int Cl.: H04L 29/06 (2006.01) H04L 29/12 (2006.01) (19) TEPZZ_8 Z _9B_T (11) EP 1 8 319 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 17.06.1 Bulletin 1/2 (21) Application number: 08163. (22) Date

More information

(51) Int Cl.: H04L 9/32 (2006.01)

(51) Int Cl.: H04L 9/32 (2006.01) (19) Europäisches Patentamt European Patent Office Office européen des brevets (11) EP 1 17 038 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 19.07.06

More information

(51) Int Cl.: H01M 8/04 (2006.01)

(51) Int Cl.: H01M 8/04 (2006.01) (19) (11) EP 1 791 20 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 12.09.2012 Bulletin 2012/37 (1) Int Cl.: H01M 8/04 (2006.01) (21) Application

More information

TEPZZ_57 7_9B_T EP 1 573 719 B1 (19) (11) EP 1 573 719 B1 (12) EUROPEAN PATENT SPECIFICATION

TEPZZ_57 7_9B_T EP 1 573 719 B1 (19) (11) EP 1 573 719 B1 (12) EUROPEAN PATENT SPECIFICATION (19) TEPZZ_7 7_9B_T (11) EP 1 73 719 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent:.11.13 Bulletin 13/47 (21) Application number: 0277098.3 (22) Date

More information

(51) Int Cl.: B62M 7/12 (2006.01) B62M 23/02 (2006.01)

(51) Int Cl.: B62M 7/12 (2006.01) B62M 23/02 (2006.01) (19) (11) EP 1 810 918 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 18.11.2009 Bulletin 2009/47 (1) Int Cl.: B62M 7/12 (2006.01) B62M 23/02 (2006.01)

More information

(51) Int Cl.: H04L 1/00 (2006.01) H04L 1/18 (2006.01)

(51) Int Cl.: H04L 1/00 (2006.01) H04L 1/18 (2006.01) (19) TEPZZ_ 4 48B_T (11) EP 1 34 348 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 17.12.14 Bulletin 14/1 (1) Int Cl.: H04L 1/00 (06.01) H04L 1/18

More information

(51) Int Cl.: G10L 19/00 (2006.01) H04L 1/20 (2006.01)

(51) Int Cl.: G10L 19/00 (2006.01) H04L 1/20 (2006.01) (19) Europäisches Patentamt European Patent Office Office européen des brevets (11) EP 1 317 72 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent:.08.06

More information

(51) Int Cl.: H04L 29/12 (2006.01) H04L 29/06 (2006.01) H04M 7/00 (2006.01)

(51) Int Cl.: H04L 29/12 (2006.01) H04L 29/06 (2006.01) H04M 7/00 (2006.01) (19) TEPZZ_94_6Z6B_T (11) EP 1 941 606 B1 (12) EUROPEAN PATENT SPECIFICATION (45) Date of publication and mention of the grant of the patent: 03.12.2014 Bulletin 2014/49 (21) Application number: 06817404.4

More information

(51) Int Cl.: H04L 12/58 (2006.01) H04L 29/06 (2006.01)

(51) Int Cl.: H04L 12/58 (2006.01) H04L 29/06 (2006.01) (19) TEPZZ_986 8 B_T (11) EP 1 986 382 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 19.02.14 Bulletin 14/08 (1) Int Cl.: H04L 12/8 (06.01) H04L

More information