EP2036247B1 - Automatische detektion von agenten - Google Patents
Automatische detektion von agenten Download PDFInfo
- Publication number
- EP2036247B1 EP2036247B1 EP07730220A EP07730220A EP2036247B1 EP 2036247 B1 EP2036247 B1 EP 2036247B1 EP 07730220 A EP07730220 A EP 07730220A EP 07730220 A EP07730220 A EP 07730220A EP 2036247 B1 EP2036247 B1 EP 2036247B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- telecommunication network
- cds
- manager
- agents
- directory service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
- 238000001514 detection method Methods 0.000 title description 14
- 238000000034 method Methods 0.000 claims description 14
- 230000007246 mechanism Effects 0.000 claims description 9
- 230000001413 cellular effect Effects 0.000 claims description 6
- 238000003780 insertion Methods 0.000 claims 3
- 230000037431 insertion Effects 0.000 claims 3
- 239000003795 chemical substances by application Substances 0.000 description 29
- 230000008901 benefit Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 238000010200 validation analysis Methods 0.000 description 2
- 239000013543 active substance Substances 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 239000013256 coordination polymer Substances 0.000 description 1
- 239000011159 matrix material Substances 0.000 description 1
- 230000010076 replication Effects 0.000 description 1
- 230000003362 replicative effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/085—Retrieval of network configuration; Tracking network configuration history
- H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
- H04L41/0856—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information by backing up or archiving configuration information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/04—Network management architectures or arrangements
- H04L41/046—Network management architectures or arrangements comprising network management agents or mobile agents therefor
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
Definitions
- the invention concerns a method, a telecommunication network, and a central directory service element for managing components of the telecommunication network.
- a telecommunications network is usually composed of different types of agents NE (which agents could also e.g. be "Network Elements” here).
- An operator uses a Manager EM (which Manager could e.g. be an "Element Manager” here) to manage these agents.
- Manager EM which Manager could e.g. be an "Element Manager” here
- the operator has to carry cut some steps for configuring the agent on the manager like providing the address of the NE for communication, the user information to access the NE and so on.
- the operator also has to go through a few steps to configure the Manager on the Agent. These steps may vary depending on the type of the agent. Great care has to be taken while performing the administration since any mistake would mean more time will be spent on correcting it. Some times it is also required to configure the same agent on more than one managers.
- agents in the telecommunications network need not be supplied by the same vendor. Vendors of agents usually provide their own Manager System to manage their NEs. The way these administrative steps have to be carried out on each of these Managers might differ significantly. This introduces additional overhead for the operator since he has to work on different Manager Systems.
- FI9901022A describes a "Agent connecting method in telecommunications network". This solution only allows a Agent to connect to a Network Management system whereas the proposed solution allows a connection to be established from the Network Management system to the NE also.
- US 2005/03883 A1 discloses manager application which may be established in one of the end nodes.
- An agent application may be independent from the manager application.
- the manager application may maintain a current list of active agent applications and may use the list to manage the agent applications in the end nodes.
- US 2002/161883 A1 discloses a system performing a registration operation.
- An agent may register with the discovery manager by placing an XML file in an agent directory in the discovery database.
- the network manager may read through the agent directory and may generate a matrix of available capabilities and existing dependencies by parsing the registration files of the various agent.
- the proposed solution allows automatic detection of Agents (NE) and Managers (EMs).
- NE Agents
- EM Managers
- the CDS stores information about all the Agents (NE) and the Managers (EM) available in the network. Any new NE which comes into the network can retrieve the list of managers EMs from the CDS and initiate the process of automatic detection with the help of the CDS.
- a new EM can also get the list of NEs available in the network from the CDS and trigger the process of automatic detection.
- the automatic detection of the NE or the EM can be made more reliable by introducing a handshake procedure between the NE and the EM.
- FIG. 1 shows the architecture of the proposed system.
- the difference of this architecture from the existing Network Management Framework is the addition of the central directory service (CDS) and a handshake procedure between the NE and the EM.
- CDS central directory service
- the architecture of the CDS and the handshake mechanism is explained in the following sections.
- the central directory service is a directory containing information about all the Agents and Manager systems within the network.
- the CDS provides interfaces through all protocols supported by the different NEs and EMs. Thus NEs and EMs can access the same information using their native protocol itself.
- An object model which outlines the data that will be contained in the CDS and the operations that can be performed on the CDS is described.
- the CDS Since the CDS is a single source of information about the network, a failure in the CDS can affect the normal functioning of the network. It should be possible to have a redundant CDS in order to prevent such a situation.
- the data contained in the CDS does not change very dynamically hence replicating the data on another CDS should be easy using any existing technique for replication.
- the redundant CDS can take over. Different means exist using which the redundant CDS can learn about the failure of the primary CDS. For example, The redundant CDS can know about the failure if the broadcastSelf() notification is not received for a predefined interval.
- the NE and the EM can communicate with each other. But when the EM does not want to manage a NE or when a NE does not want to be managed by an EM, there has to be some mechanism to undo the automatic detection. This can be achieved by introducing a mechanism which will enable the NE to communicate its willingness to be managed by the EM and the EMs willingness to manage the NE. This can either be achieved automatically or through manual intervention by the operator. This mechanism is referred to as the handshake between the NE and the EM.
- the CDS maintains a list of all NEs and EMs that are currently available in the network. It periodically sends the "broadcastSelf" notification to all the NEs and the EMs. Any new NE or EM which is introduced into the network should register itself with the CDS giving all the required details. Two different cases exist, which are explained below
- the following example of a handshake mechanism is considered for explaining the two cases.
- the EM sends a task to the NE after it completes the administration.
- the NE sends a notification to the Manager after sending the response to the task.
- For the handshake to complete the EM should have successfully executed the task and should also have received the notification from the NE. If the task fails or if the notification is not received from the NE by the EM, it does not administer the NE. If the NE does not receive a task from the EM for a predefined period, it does not administer the EM.
- the EM retries the task a few times before giving up.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Mobile Radio Communication Systems (AREA)
- Multi Processors (AREA)
- Debugging And Monitoring (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Claims (13)
- Telekommunikationsnetz, das Folgendes umfasst:erste Agenten (NE),erste Manager (EM) zum Konfigurieren erster Agenten (NE), undwenigstens ein zentrales Verzeichnisdienstelement (CDS), das einen Speicher zum Speichern von Informationen über die ersten Agenten (NE) und die ersten Manager (EM) umfasst,wobei dann, wenn ein zweiter Manager (EM) in das Telekommunikationsnetz eingefügt wird, der zweite Manager (EM) konfiguriert ist, sich selbst in das wenigstens eine zentrale Verzeichnisdienstelement (CDS) einzutragen, unddas wenigstens eine zentrale Verzeichnisdienstelement (CDS) konfiguriert ist, um wenigstens teilweise die gespeicherten Informationen über die ersten Agenten (NE) und die ersten Manager (EM) zu verwenden, falls ein zweiter Agent (NE) oder ein zweiter Manager (EM) in das Telekommunikationsnetz eingefügt wird, undwobei dann, wenn ein zweiter Manager (EM) in das Telekommunikationsnetz eingefügt wird, das zentrale Verzeichnisdienstelement (CDS) konfiguriert ist, um eine Meldung über das Einfügen des zweiten Managers (EM) zu allen ersten Agenten (NEs) rundzusenden, die dafür geeignet sind, von dem eingefügten zweiten Manager (EM) verwaltet zu werden; unddie ersten Agenten (NEs), die die Meldung empfangen, konfiguriert sind, um Informationen über den zweiten Manager (EM) aus dem zentralen Verzeichnisdienstelement (CDS) abzurufen, und konfiguriert sind, den zweiten Manager (EM) automatisch unter Verwendung der abgerufenen Informationen zu administrieren; undwobei das Telekommunikationsnetz ein zellulares mobiles Telekommunikationsnetz ist.
- Telekommunikationsnetz nach Anspruch 1, dadurch gekennzeichnet, dass
dann, wenn der zweite Agent (NE) in das Telekommunikationsnetz eingefügt wird, das zentrale Verzeichnisdienstelement (CDS) eine Liste von ersten Managern (EM) in dem Telekommunikationsnetz für den zweiten Agenten (NE) zur Verfügung stellt. - Telekommunikationsnetz nach einem der vorhergehenden Ansprüche, dadurch gekennzeichnet, dass
dann, wenn der zweite Agent (NE) in das Telekommunikationsnetz eingefügt wird, das zentrale Verzeichnisdienstelement (CDS) Informationen betreffend diesen zweiten Agenten (NE) für alle oder einige der ersten Manager (EM) im Telekommunikationsnetz zur Verfügung stellt. - Telekommunikationsnetz nach Anspruch 3, dadurch gekennzeichnet, dass das zentrale Verzeichnisdienstelement (CDS) Informationen betreffend diesen zweiten Agenten (NE) für alle ersten Manager (EM) im Telekommunikationsnetz, die zum Verwalten dieses zweiten Agenten (NE) geeignet sind, zur Verfügung stellt.
- Telekommunikationsnetz nach Anspruch 3 oder 4, dadurch gekennzeichnet, dass wenigstens einer der ersten Manager (EM) den eingefügten zweiten Agenten (NE) zur Konfiguration kontaktiert.
- Telekommunikationsnetz nach den Ansprüchen 3 bis 5, dadurch gekennzeichnet, dass
wenigstens einer der ersten Manager (EM) den zweiten Agenten (NE) konfiguriert, insbesondere durch Bereitstellen wenigstens für den zweiten Agenten (NE) der Adresse, die von dem zweiten Agenten (NE) zur Kommunikation verwendet werden soll. - Telekommunikationsnetz nach Anspruch 1, dadurch gekennzeichnet, dass danach der zweite Manager (EM) alle oder einige der ersten Agenten (NE) in dem Telekommunikationsnetz kontaktiert.
- Telekommunikationsnetz nach einem der vorhergehenden Ansprüche, dadurch gekennzeichnet, dass das zentrale Verzeichnisdienstelement (CDS) ein Objektmodell verwendet.
- Telekommunikationsnetz nach einem der vorhergehenden Ansprüche, dadurch gekennzeichnet, dass das Telekommunikationsnetz einen Handshake-Mechanismus umfasst, der von dem zentralen Verzeichnisdienstelement (CDS) unterstützt wird, zum Ermöglichen der Kommunikation zwischen dem ersten Agenten (NE) oder ersten Manager und dem zweiten Manager (EM) oder dem zweiten Agenten (NE) in dem Telekommunikationsnetz.
- Telekommunikationsnetz nach einem der vorhergehenden Ansprüche, dadurch gekennzeichnet, dass
für Sicherungszwecke das Telekommunikationsnetz ein redundantes zentrales Verzeichnisdienstelement (CDS) mit den Informationen, die in dem zentrale Verzeichnisdienstelement (CDS) gespeichert sind, umfasst. - Telekommunikationsnetz nach einem der vorhergehenden Ansprüche,
dadurch gekennzeichnet, dass das zentrale Verzeichnisdienstelement (CDS) und/oder das redundante zentrale Verzeichnisdienstelement (CDS) eine getrennte Einheit oder ein Teil irgendeines anderen Elements in einer hierarchischen Struktur von Agenten und Managern ist. - Zentrales Verzeichnisdienstelement (CDS) für ein Telekommunikationsnetz nach einem der vorhergehenden Ansprüche, wobei das zentrale Verzeichnisdienstelement (CDS) einen Speicher zum Speichern von Informationen über die ersten Agenten (NE) und die ersten Manager (EM) umfasst, wobei
dann, wenn ein zweiter Agent (NE) oder ein zweiter Manager (EM) in das Telekommunikationsnetz eingefügt wird, das zentrale Verzeichnisdienstelement (CDS) konfiguriert ist, um die ersten Agenten (NE) oder die ersten Manager (EM) des Telekommunikationsnetzes zu benachrichtigen, und
dann, wenn der zweite Manager (EM) in das Telekommunikationsnetz eingefügt wird und sich selbst in dem zentrale Verzeichnisdienstelement (CDS) einträgt, das zentrale Verzeichnisdienstelement (CDS) konfiguriert ist, eine Benachrichtigung über das Einfügen des zweiten Managers (EM) an alle ersten Agenten (NEs) rundzusenden, die geeignet sind, von dem zweiten Manager (EM) verwaltet zu werden, und
das zentrale Verzeichnisdienstelement (CDS) konfiguriert ist, um Informationen über den zweiten Manager (EM) auf Anfrage von den ersten Agenten (NE) zur Verfügung zu stellen, wobei die Informationen über den zweiten Manager (EM) von den ersten Agenten (NEs) verwendet werden, um den zweiten Manager (EM) automatisch zu administrieren, und
wobei das Telekommunikationsnetz ein zellulares mobiles Telekommunikationsnetz ist. - Verfahren zum Konfigurieren von Komponenten (NE, EM) eines Telekommunikationsnetzes, wobei das Telekommunikationsnetz erste Agenten (NE), erste Manager (EM) zum Konfigurieren der ersten Agenten (NE) und wenigstens ein zentrale Verzeichnisdienstelement (CDS), das Informationen über die ersten Agenten (NE) und diese ersten Manager (EM) speichert, wobei das Verfahren Folgendes umfasst:dann, wenn ein zweiter Agent (NE) oder ein zweiter Manager (EM) in das Telekommunikationsnetz eingefügt wird, der zweite Agent (NE) oder Manager (EM) sich selbst in das wenigstens eine zentrale Verzeichnisdienstelement (CDS) einträgt und das zentrale Verzeichnisdienstelement (CDS) die ersten Manager (EM) oder die ersten Agenten (NE) benachrichtigt,und dann, wenn ein zweiter Manager (EM) in das Telekommunikationsnetz eingefügt wird, das zentrale Verzeichnisdienstelement (CDS) eine Benachrichtigung über das Einfügen des zweiten Managers (EM) zu allen ersten Agenten (NEs), die von dem zweiten Manager (EM) verwaltet werden können, rundsendet unddas zentrale Verzeichnisdienstelement (CDS) Informationen über den zweiten Manager (EM) auf Anfrage von den ersten Agenten (NEs) zur Verfügung stellt, wobei diese Informationen über den zweiten Manager (EM) von den ersten Agenten (NEs) verwendet werden, um den zweiten Manager (EM) automatisch zu administrieren,wobei das Telekommunikationsnetz ein zellulares mobiles Telekommunikationsnetz ist.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
IN606KO2006 | 2006-06-19 | ||
PCT/EP2007/056010 WO2007147799A2 (en) | 2006-06-19 | 2007-06-18 | Automatic detection of agents |
Publications (2)
Publication Number | Publication Date |
---|---|
EP2036247A2 EP2036247A2 (de) | 2009-03-18 |
EP2036247B1 true EP2036247B1 (de) | 2013-02-27 |
Family
ID=38722614
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP07730220A Ceased EP2036247B1 (de) | 2006-06-19 | 2007-06-18 | Automatische detektion von agenten |
Country Status (4)
Country | Link |
---|---|
US (1) | US8219682B2 (de) |
EP (1) | EP2036247B1 (de) |
CN (1) | CN101485142B (de) |
WO (1) | WO2007147799A2 (de) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2036247B1 (de) * | 2006-06-19 | 2013-02-27 | Nokia Siemens Networks GmbH & Co. KG | Automatische detektion von agenten |
US8776086B1 (en) | 2012-03-08 | 2014-07-08 | Emc Corporation | Agent management framework |
Family Cites Families (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5185860A (en) * | 1990-05-03 | 1993-02-09 | Hewlett-Packard Company | Automatic discovery of network elements |
US5909549A (en) | 1996-11-12 | 1999-06-01 | International Business Machines Corporation | Network management system wherein the managed device reestablishes a connection to a management station after detecting a broken connection |
JP3206644B2 (ja) * | 1997-08-11 | 2001-09-10 | 日本電気株式会社 | ネットワーク管理方式 |
US6496859B2 (en) * | 1998-11-25 | 2002-12-17 | Xerox Corporation | System for network device location |
US6633909B1 (en) * | 1999-09-23 | 2003-10-14 | International Business Machines Corporation | Notification method that guarantees a system manager discovers an SNMP agent |
US7406515B1 (en) * | 2000-06-27 | 2008-07-29 | Aspect Communications | System and method for automated and customizable agent availability and task assignment management |
US20020161883A1 (en) * | 2001-04-30 | 2002-10-31 | David Matheny | System and method for collecting, aggregating, and coalescing network discovery data |
US7515546B2 (en) | 2001-12-19 | 2009-04-07 | Alcatel-Lucent Canada Inc. | Method and apparatus for automatic discovery of network devices with data forwarding capabilities |
US20040010510A1 (en) * | 2002-07-10 | 2004-01-15 | Timo Hotti | Method and system for database synchronization |
EP1383276B1 (de) * | 2002-07-18 | 2007-09-19 | Telefonaktiebolaget LM Ericsson (publ) | Verwaltungssystem umd Methode zur Erbringung von Abonnementdienstleistungen |
WO2004093384A1 (en) * | 2003-04-04 | 2004-10-28 | Computer Associates Think, Inc. | Method and system for discovery of remote agents |
US7768946B2 (en) * | 2003-04-07 | 2010-08-03 | Nokia Corporation | Resource determination in IP-based networks |
US7421488B2 (en) * | 2003-08-14 | 2008-09-02 | International Business Machines Corporation | System, method, and computer program product for centralized management of an infiniband distributed system area network |
US7756958B2 (en) * | 2003-09-20 | 2010-07-13 | International Business Machines Corporation | Intelligent discovery of network information from multiple information gathering agents |
KR100701383B1 (ko) * | 2004-04-07 | 2007-03-28 | 엘지전자 주식회사 | 홈 네트워크에서의 복수의 관리기기간의 관리정보를동기화시키는 방법과 그 방법을 위한 홈 네트워크 시스템 |
EP2176767A1 (de) * | 2005-06-14 | 2010-04-21 | Patrice Guichard | Schutzverfahren und -einrichtung für daten und ein computersystem |
EP2036247B1 (de) * | 2006-06-19 | 2013-02-27 | Nokia Siemens Networks GmbH & Co. KG | Automatische detektion von agenten |
US7778189B2 (en) * | 2006-06-30 | 2010-08-17 | Nokia Corporation | Maintaining an existing connection between nodes |
-
2007
- 2007-06-18 EP EP07730220A patent/EP2036247B1/de not_active Ceased
- 2007-06-18 US US12/308,655 patent/US8219682B2/en not_active Expired - Fee Related
- 2007-06-18 CN CN2007800228552A patent/CN101485142B/zh not_active Expired - Fee Related
- 2007-06-18 WO PCT/EP2007/056010 patent/WO2007147799A2/en active Application Filing
Also Published As
Publication number | Publication date |
---|---|
WO2007147799A2 (en) | 2007-12-27 |
US8219682B2 (en) | 2012-07-10 |
US20100299412A1 (en) | 2010-11-25 |
CN101485142B (zh) | 2013-03-27 |
CN101485142A (zh) | 2009-07-15 |
EP2036247A2 (de) | 2009-03-18 |
WO2007147799A3 (en) | 2008-02-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6968553B1 (en) | Element manager common gateway architecture system and method | |
EP1267518B1 (de) | Verfahren und Vorrichtung zum Verwalten von mehreren Netzwerkgeräten | |
RU2378784C2 (ru) | Устройство и способ управления сетью на основе простого протокола управления сетью (snmp) | |
US8145789B1 (en) | Method providing a single console control point for a network device cluster | |
US7113989B2 (en) | Command line interface processor | |
US6349333B1 (en) | Platform independent alarm service for manipulating managed objects in a distributed network management system | |
US7730180B1 (en) | Resolving multiple master node conflict in a DDB | |
US7130899B1 (en) | Robust indication processing | |
US6922705B1 (en) | Access-method-independent exchange with communication request | |
US8149725B2 (en) | Methods, systems, and computer program products for a hierarchical, redundant OAM&P architecture for use in an IP multimedia subsystem (IMS) network | |
US8069229B2 (en) | Topology static zones | |
US20030177412A1 (en) | Methods, apparatus and computer programs for monitoring and management of integrated data processing systems | |
US7937716B2 (en) | Managing collections of appliances | |
US20020013846A1 (en) | Apparatus, methods, and computer program products for transactional support of network management operations | |
US20060235968A1 (en) | Command line interface processor | |
WO2005069544A1 (en) | Automatic update system and method for using a meta mib | |
US7660882B2 (en) | Deploying network element management system provisioning services | |
US7853676B1 (en) | Protocol for efficient exchange of XML documents with a network device | |
EP2036247B1 (de) | Automatische detektion von agenten | |
WO1999034557A1 (en) | Method and system for software version management in a network management system | |
US8122114B1 (en) | Modular, dynamically extensible, and integrated storage area network management system | |
Cisco | Release Notes for Cisco Info Center Release 1.2 | |
Cisco | Cisco Network Order Manager Introduction | |
US20030140273A1 (en) | Method and apparatus for fault tolerant persistency service on network device | |
Reddy et al. | Managing Heterogeneous Networks Using NETCONF |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20090119 |
|
AK | Designated contracting states |
Kind code of ref document: A2 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC MT NL PL PT RO SE SI SK TR |
|
AX | Request for extension of the european patent |
Extension state: AL BA HR MK RS |
|
17Q | First examination report despatched |
Effective date: 20090506 |
|
DAX | Request for extension of the european patent (deleted) | ||
RBV | Designated contracting states (corrected) |
Designated state(s): DE GB |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): DE GB |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602007028700 Country of ref document: DE Effective date: 20130425 |
|
RAP2 | Party data changed (patent owner data changed or rights of a patent transferred) |
Owner name: NOKIA SOLUTIONS AND NETWORKS GMBH & CO. KG |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
26N | No opposition filed |
Effective date: 20131128 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602007028700 Country of ref document: DE Effective date: 20131128 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20140618 Year of fee payment: 8 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20140619 Year of fee payment: 8 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R081 Ref document number: 602007028700 Country of ref document: DE Owner name: NOKIA SOLUTIONS AND NETWORKS GMBH & CO. KG, DE Free format text: FORMER OWNER: NOKIA SIEMENS NETWORKS GMBH & CO. KG, 81541 MUENCHEN, DE Effective date: 20140731 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R119 Ref document number: 602007028700 Country of ref document: DE |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20150618 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20160101 Ref country code: GB Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20150618 |