[go: up one dir, main page]

EP1250817B1 - Kommunikationsnetz - Google Patents

Kommunikationsnetz Download PDF

Info

Publication number
EP1250817B1
EP1250817B1 EP01900523A EP01900523A EP1250817B1 EP 1250817 B1 EP1250817 B1 EP 1250817B1 EP 01900523 A EP01900523 A EP 01900523A EP 01900523 A EP01900523 A EP 01900523A EP 1250817 B1 EP1250817 B1 EP 1250817B1
Authority
EP
European Patent Office
Prior art keywords
service
application
nodes
registration server
network
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.)
Expired - Lifetime
Application number
EP01900523A
Other languages
English (en)
French (fr)
Other versions
EP1250817A2 (de
Inventor
Richard John Mellish Kett
Jeremy Roger Mason
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
British Telecommunications PLC
Original Assignee
British Telecommunications PLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by British Telecommunications PLC filed Critical British Telecommunications PLC
Priority to EP01900523A priority Critical patent/EP1250817B1/de
Publication of EP1250817A2 publication Critical patent/EP1250817A2/de
Application granted granted Critical
Publication of EP1250817B1 publication Critical patent/EP1250817B1/de
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q3/00—Selecting arrangements
    • H04Q3/0016—Arrangements providing connection between exchanges
    • H04Q3/0029—Provisions for intelligent networking
    • H04Q3/0054—Service creation techniques

Definitions

  • the present invention relates to a communications network, and in particular to a registration server and to other components implementing a programmable interface to resources in such a network.
  • IN intelligent network
  • the control logic and various network resources required to implement advanced services are tightly integrated with the communications network, and in general are intended to be run under the control of the network operator.
  • Such an approach allows robust large-scale applications to be implemented.
  • the architecture tends to be relatively inflexible, so that developing and deploying new services can be time-consuming.
  • it can be difficult to make network resources available to service providers other than the network operator, while maintaining the security and integrity of the network.
  • a network including an API as described above has been developed by the present applicant in conjunction with other members of the Parlay Organisation.
  • the Parlay Organisation has published a specification for the API together with resources to aid implementation.
  • An overview of the Parlay API is contained in the document " Parlay API Business Benefits White Paper", Parlay Organisation, 11 June 1999, Published at www.parlay.org. Versions 1.2 and 2 of the Parlay API specification are also available from the same site.
  • a registration server is used to control access by edge-of-network service applications to components in the network that provide service resources.
  • the registration server may be used to carry out an authentication process in which the identity of a service application, and the authority of the owner of that application to access network resources, is checked, for example, using a digital signature, and a database listing authorised users of the network.
  • the registration server may also be used for the process of discovery, in which, in response to a request from a service application, the registration server provides details of available network resources. Subsequently, the registration server registers a service application with one or more services resources. This may be done by communicating to the service application the logical identity and physical address of a service manager object on a particular service node and/or communicating to the service manager object data identifying the corresponding service application.
  • XP002139802 discloses a communications network including service nodes providing service resources, service applications requesting service resources and running on a service applications platform, and a registration server.
  • WO 97 36430 A discloses a service provisioning methodology whereby a service creation environment outputs a logic representation for a service and the logic representation is processed at an execution environment thereby providing the service to subscribers.
  • a method of operating a communications network including one or more service nodes, a registration server arranged to control access by service applications to the one or more service nodes, and a platform remote from the registration server running one or more communications service applications, the method including:
  • the present invention provides a method of implementing an API in a communications network that is better able to support applications requiring a high degree of resilience. This is achieved by amending the implementation of the API so that the process of registration is no longer limited to creating one-to-one bindings between service applications and service nodes, but instead allows several instances of a service application to be registered with a node and or several different nodes to be registered with one service application.
  • a communications network comprises an access network 1 and a core network 2.
  • Customer terminals 3a, 3b are connected to the access network 1.
  • Service provider platforms 4a, 4b are also connected to the access network 1.
  • a registration server 5 is connected to the network and, as is further described below, is used in implementing an API (application programmers interface) to network resources.
  • Those network resources include a number of service nodes 6a, 6b, 6c, each of which includes a respective gateway GW1, GW2, GW3.
  • the service nodes include hardware and software for running for example, number translation applications, interactive voice recognition and messaging services.
  • the term "service node” is used here broadly to denote a node used in running a service application, and is not limited to nodes at edge-of-network locations.
  • FIG. 2 shows in further detail the architecture of one of the service resource nodes.
  • the service node is a platform known as the network intelligence platform (NIP). It includes a number of communications servers (CS) that terminate network signalling, in this example signalling system number 7 (SS7) common channel signalling.
  • a global data server (GDS) monitors signalling rates and collects call statistics.
  • Transaction servers (TS) implement the basic service control functions required by the service node.
  • An overload control server (OCS) implements overload control protection both for the service node and for components downstream from the service node. For example, the OSC may initiate call-gapping when an overload condition is detected.
  • the overload control server and transaction servers are connected to a common high-speed bus.
  • the gateway supports a number of instances of service manager objects that allocate the resources of the different components within the service node to a particular service application.
  • the different servers making up the service node may each be implemented on a respective UNIX workstation.
  • the different servers communicate via high speed optical fibre (FDDI) local area networks (LANS) 21, 22.
  • FDDI optical fibre
  • LSS local area networks
  • the communications network implements an application programmers interface (API) between applications running at the edge of the network in the so-called “enterprise domain” and the network components used to implement the services in the network operator domain.
  • API application programmers interface
  • the interface is that defined in the Parlay API specification.
  • FIG. 4 shows in further detail the interfaces between components of the network implementing the Parlay interface.
  • the interface is object-oriented and is implemented using two categories of interface: firstly, service interfaces and secondly, framework interfaces.
  • the service interfaces of applications access to the capabilities of the network.
  • the framework interfaces provide a surround for the service interfaces.
  • the framework interface implements processes of authentication, discovery and registration.
  • the framework objects in the network domain communicate with client FW objects in the user domain.
  • these direct interfaces 4.2 are normally only accessed after an application has signed-on via the framework interface 4.1.
  • objects implementing the framework FW reside on the registration server 5.
  • the client applications and client FW run on the service provider platforms 4a, 4b.
  • the Parlay services including the gateways are embodied in the service nodes 6a, 6b, 6c.
  • a Parlay authentication object is instantiated on the registration server and provides an authentication interface that enables mutual authentication of the registration server and the client application.
  • the application returns an identifying code to the registration server.
  • the registration server includes a database of recognised applications. The registration server performs a look-up on the application ID and may also retrieve a cryptographic key specific to the application.
  • each single service agreement created using the Parlay interface has linked a single gateway to a single client application.
  • the interface is modified to link multiple gateways to multiple client applications under a single service agreement.
  • a Parlay-supported end user service it is possible for a Parlay-supported end user service to be resilient against gateway or client application failure.
  • Each service manager residing in a gateway is given the capability to forward initial event notifications, for example notification of an incoming call, to available client applications using a distribution algorithm, for example a round-robin algorithm.
  • the client application support layer is able to invoke initial session requests. For example, a request to create a call, to one of a number of available gateways using a distribution algorithm.
  • the framework FW now includes a polling mechanism to detect the current state of the gateways that support a registered service. Detection of a failed gateway may be used to trigger an alarm. The availability of each of the gateways serving the client application is reported to the client framework. When a restored gateway is detected, after an outage, the framework requests the instantiation of a new service manager and posts a reference to the new service manager to the client FW.
  • the client FW implements a polling mechanism that detects the current state of client applications.
  • Detection of a failed client application may be used to trigger an alarm.
  • the availability of each of the client applications is reported to the framework FW.
  • the client FW communicates to the new client application a full list of references to the service managers.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer And Data Communications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Telephonic Communication Services (AREA)

Claims (7)

  1. Verfahren zum Betreiben eines Kommunikationsnetzes mit einem oder mehreren Dienstknoten (6a, 6b, 6c), einem Registrierungsserver (5), der dazu angeordnet ist, den Zugriff durch Dienstanwendungen (4a, 4b) auf den einen oder die mehreren Dienstknoten zu steuern, und einer von dem Registrierungsserver entfernten Plattform, auf der eine oder mehrere Kommunikations-Dienstanwendungen laufen, mit:
    a) Verteilen von Daten identifizierenden Dienstressourcen, die an dem oder jedem mit dem Kommunikationsnetz verbundenen Dienstknoten verfügbar sind;
    b) Kommunizieren einer Anfrage auf Zugriff durch zumindest eine der Dienstanwendungen, die auf der Plattform laufen, auf zumindest einige der in Schritt (a) identifizierten Dienstressourcen an den Registrierungsserver;
    c) als Antwort auf die Anfrage von Schritt (b), Ausführen einer Dienstvereinbarung am Registrierungsserver, die Zugriff durch die Dienstanwendung auf den einen oder die mehreren Dienstknoten gestattet, die die angefragten Dienstressourcen bereitstellen;
    d) anschließend Binden der Dienstanwendung an den einen oder die mehreren Dienstknoten;
    dadurch gekennzeichnet, dass in Schritt (c) die Dienstvereinbarung mehrere Beispiele der Dienstanwendung spezifiziert und/oder mehrere Dienstknoten spezifiziert und dass Schritt (d) zumindest einen der folgenden einschließt:
    (i) Binden mehrerer Beispiele der Dienstanwendung an den einen oder die mehreren Dienstknoten; und/oder
    (ii) Binden zumindest eines Beispiels der Dienstanwendung an mehrere Dienstknoten.
  2. Verfahren nach Anspruch 1, wobei, wenn Schritt (d) das Binden mehrerer Beispiele der Dienstanwendung an den zumindest einen Dienstknoten einschließt, das Verfahren weiterhin das Verteilen aufeinander folgender anfänglicher Ereignisbenachrichtigungen zwischen den mehreren Beispielen der Dienstanwendung beinhaltet.
  3. Verfahren nach Anspruch 1 oder 2, mit dem Registrieren mehrerer Dienstknoten mit dem zumindest einen Beispiel der Dienstanwendung, wobei das Verfahren das Verteilen aufeinander folgender anfänglicher Sitzungsanfragen zwischen den mehreren Dienstknoten einschließt.
  4. Verfahren nach irgendeinem der vorhergehenden Ansprüche, weiterhin mit einem vom Registrierungsserver ausgeführten Schritt des wiederholten Abrufens mehrerer im Registrierungsserver registrierter Dienstknoten und des Kommunizierens von Beispielsdaten, die irgendeine Änderung der Verfügbarkeit der Dienstknoten angeben, an die oder jede auf der Plattform laufende Dienstanwendung.
  5. Verfahren nach irgendeinem der vorhergehenden Ansprüche, wobei, wenn mehrere Dienstanwendungsbeispiele im Registrierungsserver registriert sind, das Verfahren weiterhin das wiederholte Abrufen jedes der mehreren im Registrierungsserver registrierten Dienstanwendungsbeispiele und das Kommunizieren von Daten, die irgendeine Änderung der Verfügbarkeit der Dienstanwendungsbeispiele angeben, an den oder jeden Dienstknoten umfasst.
  6. Kommunikationsnetz mit einem oder mehreren Dienstknoten (6a, 6b, 6c), einem Registrierungsserver (5), der zum Steuern des Zugriffs durch Dienstanwendungen (4a, 4b) auf den einen oder die mehreren Dienstknoten angeordnet ist, und einer vom Registrierungsserver entfernten Plattform, auf der eine oder mehrere Kommunikations-Dienstanwendungen laufen, angeordnet ist, wobei das Netz weiterhin dazu angeordnet ist, gemäß allen Schritten des Verfahrens nach irgendeinem der vorhergehenden Ansprüche zu arbeiten.
  7. Registrierungsserver (5), der zum Gebrauch in einem Kommunikationsnetz nach Anspruch 6 ausgelegt ist, mit:
    Mitteln zum Empfangen von Anfragen nach Zugriff durch zumindest eine der auf der Plattform laufenden Dienstanwendungen auf zumindest einige Dienstressourcen, die auf dem oder jedem mit dem Kommunikationsnetz verbundenen Dienstknoten verfügbar sind;
    Mitteln zum Ausführen einer Dienstvereinbarung in Antwort auf eine empfangene Anfrage nach dem Zugriff, wobei die Dienstvereinbarung den Zugriff durch die Dienstanwendung auf den einen oder die mehreren Dienstknoten gestattet, die die angefragten Dienstressourcen bereitstellen; und
    Mitteln zum Binden der Dienstanwendung an den einen oder die mehreren Dienstknoten;
    wobei die Dienstvereinbarung mehrere Beispiele der Dienstanwendung spezifiziert und/oder mehrere Dienstknoten spezifiziert, und dadurch gekennzeichnet, dass das Bindungsmittel zumindest einen der folgenden durchführt: (i) Binden mehrerer Beispiele der Dienstanwendung an den einen oder die mehreren Dienstknoten, und/oder (ii) Binden zumindest eines Beispiels der Dienstanwendung an mehrere Dienstknoten.
EP01900523A 2000-01-24 2001-01-12 Kommunikationsnetz Expired - Lifetime EP1250817B1 (de)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP01900523A EP1250817B1 (de) 2000-01-24 2001-01-12 Kommunikationsnetz

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
EP00300480A EP1120979A1 (de) 2000-01-24 2000-01-24 Kommunikationsnetz
EP00300480 2000-01-24
EP01900523A EP1250817B1 (de) 2000-01-24 2001-01-12 Kommunikationsnetz
PCT/GB2001/000121 WO2001054424A2 (en) 2000-01-24 2001-01-12 Communications network

Publications (2)

Publication Number Publication Date
EP1250817A2 EP1250817A2 (de) 2002-10-23
EP1250817B1 true EP1250817B1 (de) 2010-11-24

Family

ID=8172659

Family Applications (2)

Application Number Title Priority Date Filing Date
EP00300480A Withdrawn EP1120979A1 (de) 2000-01-24 2000-01-24 Kommunikationsnetz
EP01900523A Expired - Lifetime EP1250817B1 (de) 2000-01-24 2001-01-12 Kommunikationsnetz

Family Applications Before (1)

Application Number Title Priority Date Filing Date
EP00300480A Withdrawn EP1120979A1 (de) 2000-01-24 2000-01-24 Kommunikationsnetz

Country Status (6)

Country Link
US (1) US7660903B2 (de)
EP (2) EP1120979A1 (de)
JP (3) JP2003520533A (de)
CA (1) CA2397114C (de)
DE (1) DE60143512D1 (de)
WO (1) WO2001054424A2 (de)

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002048858A2 (en) * 2000-12-15 2002-06-20 Nokia Corporation Method and system for acces in open service architecture
US7246349B2 (en) * 2001-08-31 2007-07-17 Telefonaktiebolaget Lm Ericsson (Publ) Migration support mechanism in open service and open mobile architecture
EP1310928B1 (de) * 2001-11-08 2005-10-26 Siemens Aktiengesellschaft Verfahren zum Ermöglichen und Durchführen einer Geldzahlung unter Nutzung eines Kommunikationsnetzes
US7610404B2 (en) * 2002-05-22 2009-10-27 Cast Iron Systems, Inc. Application network communication method and apparatus
US8296433B2 (en) * 2002-05-22 2012-10-23 International Business Machines Corporation Virtualization method and apparatus for integrating enterprise applications
US20040234060A1 (en) * 2003-03-31 2004-11-25 Nokia Corporation Method and system for deactivating a service account
US8321590B2 (en) * 2003-05-22 2012-11-27 International Business Machines Corporation Application network communication
US7734691B2 (en) * 2003-12-18 2010-06-08 International Business Machines Corporation Providing collaboration services to a wireless device
US20050249190A1 (en) * 2004-05-06 2005-11-10 Oliver Birch Using a CCXML service node to provide call processing functionality for a parlay gateway
US8135836B2 (en) * 2005-11-30 2012-03-13 Alcatel Lucent Tie resolution in application load level balancing
US7975138B2 (en) * 2007-07-18 2011-07-05 Oracle International Corporation Systems and methods for mutually authenticated transaction coordination messages over insecure connections
US9544202B2 (en) 2013-08-29 2017-01-10 Oracle International Corporation Dynamic assignment and enforcement of application-driven per-connection service level agreements
US9497088B2 (en) 2013-08-29 2016-11-15 Oracle International Corporation Method and system for end-to-end classification of level 7 application flows in networking endpoints and devices
US10471348B2 (en) 2015-07-24 2019-11-12 Activision Publishing, Inc. System and method for creating and sharing customized video game weapon configurations in multiplayer video games via one or more social networks
EP3723347B1 (de) * 2019-04-12 2022-10-12 ServiceNow, Inc. Schnittstelle zur unterstützung der integration mit anbietern cloud-basierter dienste
US11263201B2 (en) 2019-04-12 2022-03-01 Servicenow, Inc. Interface for supporting integration with cloud-based service providers
US10719503B1 (en) 2019-05-02 2020-07-21 Servicenow, Inc. Interface for supporting integration with cloud-based service providers

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6044205A (en) * 1996-02-29 2000-03-28 Intermind Corporation Communications system for transferring information between memories according to processes transferred with the information
US5329619A (en) * 1992-10-30 1994-07-12 Software Ag Cooperative processing interface and communication broker for heterogeneous computing environments
JP2755117B2 (ja) * 1993-08-30 1998-05-20 日本電気株式会社 インテリジェントネットワークシステム
US5862325A (en) * 1996-02-29 1999-01-19 Intermind Corporation Computer-based communication system and method using metadata defining a control structure
EP0888695B1 (de) * 1996-03-22 2004-02-18 Nortel Networks Limited Dienstlogikübertragbarkeit durch definition der ausführungsumgebungsschnittstelle in einem intelligenten netz
US5862331A (en) * 1996-06-21 1999-01-19 Sun Microsystems, Inc. Name service system and method for automatic updating on interconnected hosts
US5991790A (en) * 1996-07-01 1999-11-23 Sun Microsystems, Inc. Generation and delivery of signals in a two-level, multithreaded system
DE69732221T2 (de) * 1997-04-14 2006-03-30 Alcatel Verfahren zum Anbieten von einem Dienst an Fernmeldenetzbenutzern
JPH11308337A (ja) * 1998-04-24 1999-11-05 Tokyo Electric Power Co Inc:The 分散協調型ネットワーク
US6341351B1 (en) * 1998-05-07 2002-01-22 Banctec, Inc. Method for communicating and controlling transactions between unsecured parties
US6539427B1 (en) * 1999-06-29 2003-03-25 Cisco Technology, Inc. Dynamically adaptive network element in a feedback-based data network
US6202159B1 (en) * 1999-06-30 2001-03-13 International Business Machines Corporation Vault controller dispatcher and methods of operation for handling interaction between browser sessions and vault processes in electronic business systems
US6556544B1 (en) * 1999-10-22 2003-04-29 Nortel Networks Limited Method and system for provisioning network resources for dynamic multicast groups
US7120694B2 (en) * 1999-10-22 2006-10-10 Verizon Laboratories Inc. Service level agreements and management thereof
US6873609B1 (en) * 1999-11-02 2005-03-29 Ipwireless, Inc. Use of internet WEB technology for wireless internet access
US6874011B1 (en) * 2000-07-31 2005-03-29 Cisco Technology, Inc. Scalable IP-based notification architecture for unified messaging
US6925493B1 (en) * 2000-11-17 2005-08-02 Oblicore Ltd. System use internal service level language including formula to compute service level value for analyzing and coordinating service level agreements for application service providers

Also Published As

Publication number Publication date
CA2397114C (en) 2010-09-28
JP2003520533A (ja) 2003-07-02
US7660903B2 (en) 2010-02-09
CA2397114A1 (en) 2001-07-26
EP1120979A1 (de) 2001-08-01
JP2012090281A (ja) 2012-05-10
JP2014090446A (ja) 2014-05-15
JP5726991B2 (ja) 2015-06-03
WO2001054424A2 (en) 2001-07-26
EP1250817A2 (de) 2002-10-23
WO2001054424A3 (en) 2002-03-14
US20020194336A1 (en) 2002-12-19
DE60143512D1 (de) 2011-01-05

Similar Documents

Publication Publication Date Title
JP5726991B2 (ja) 通信網
CN1649324B (zh) 操作带有代理的开放api网络的方法和装置
EP1221236B1 (de) System zur bereitstellung vor diensten
US6201862B1 (en) Method for providing at least one service to users of a telecommunication network, service control facility and server node
US6317428B1 (en) Method of providing a service to users of a telecommunication network, service control facility, and processing node
MXPA01003975A (es) Metodo y aparato para proporcionar servicios de procesamiento de llamadas en tiempo real en una red inteligente.
CA2315038A1 (en) Architecture independent application invocation over a telephony network
US5615351A (en) Method and system for correlating usage data in a distributed architecture
US6266406B1 (en) Method for communicating between a service switching exchange of a telecommunication network and service control facility
US20020087693A1 (en) Method and system for distributing service functionality
EP0873029A1 (de) Service Control Point Schnittstelle
Waddington et al. Specifying QoS for multimedia communications within distributed programming environments
WO2000022788A1 (en) Management of path selection in a communications network
AU759043B2 (en) Processing platform
Berg et al. CORBA and intelligent network (IN) interworking
JP2000165453A (ja) デ―タネットワ―クとサ―ビスネットワ―クの間のゲ―トウェイ
US6744855B1 (en) Service control platform
Boujemaa et al. Introducing CORBA in intelligent networks
Breugst et al. Marine-Flexible service provision and configuration in a MAT/DOT-based B-IN
AU1137100A (en) Management of path selection in a communications network

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: 20020704

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR

RBV Designated contracting states (corrected)

Designated state(s): DE FR GB

17Q First examination report despatched

Effective date: 20080428

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 FR GB

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REF Corresponds to:

Ref document number: 60143512

Country of ref document: DE

Date of ref document: 20110105

Kind code of ref document: P

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: 20110825

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 60143512

Country of ref document: DE

Effective date: 20110825

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 16

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 17

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 18

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20191219

Year of fee payment: 20

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20191224

Year of fee payment: 20

Ref country code: DE

Payment date: 20191218

Year of fee payment: 20

REG Reference to a national code

Ref country code: DE

Ref legal event code: R071

Ref document number: 60143512

Country of ref document: DE

REG Reference to a national code

Ref country code: GB

Ref legal event code: PE20

Expiry date: 20210111

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF EXPIRATION OF PROTECTION

Effective date: 20210111