EP1245105B1 - Error reporting in a mobile telecommunications network - Google Patents

Error reporting in a mobile telecommunications network Download PDF

Info

Publication number
EP1245105B1
EP1245105B1 EP00972892A EP00972892A EP1245105B1 EP 1245105 B1 EP1245105 B1 EP 1245105B1 EP 00972892 A EP00972892 A EP 00972892A EP 00972892 A EP00972892 A EP 00972892A EP 1245105 B1 EP1245105 B1 EP 1245105B1
Authority
EP
European Patent Office
Prior art keywords
error
entity
error message
interface
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
EP00972892A
Other languages
German (de)
English (en)
French (fr)
Other versions
EP1245105A1 (en
Inventor
Fredrik Berg
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of EP1245105A1 publication Critical patent/EP1245105A1/en
Application granted granted Critical
Publication of EP1245105B1 publication Critical patent/EP1245105B1/en
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic

Definitions

  • the present invention relates to error reporting in a mobile telecommunications network. More particularly, the invention relates to error reporting in the Iu User Plane (UP) between a Universal Mobile Telecommunications Network (UMTS) core network and a UMTS Terrestrial Radio Access Network (UTRAN).
  • UP Iu User Plane
  • UMTS Universal Mobile Telecommunications Network
  • UTRAN UMTS Terrestrial Radio Access Network
  • FIG. 1 illustrates schematically a part of a Universal Mobile Telecommunications System (UMTS) network.
  • the network includes a core network part 1, which may be a network handling voice calls using UMTS Mobile-services Switching Centres (UMSCs) or may be a data network such as a General Packet Radio Service (GPRS) network including Serving GPRS Support Nodes (SGSNs).
  • UMSCs and SGSNs are indicated generally with the reference numeral 2.
  • a subscriber or User Equipment (UE) 3 is coupled to the core network 1 via an access network 4 referred to as a Universal Terrestrial Radio Access Network (UTRAN). More particularly, the UMSCs/SGSNs 2 are connected to Radio Network Controllers (RNCs) 5,6 of the UTRAN 4 over an interface referred to as the Iu interface.
  • RNCs Radio Network Controllers
  • Each RNC 5 forms part of a Radio Network Subsystem (RNSs) 7,8 which also comprises a set of Base Transceiver Stations 9 referred to in UMTS terminology as Node B's.
  • the interface between a RNC 5,6 and a Node B 9 is known as the Iub interface.
  • a Node B 9 provides the connection point for a UE 3 to the UTRAN 4, and the interface between the Node B 9 and the UE 3 is known as the Uu interface.
  • the RNS (RNS 7 in Figure 1 ) which connects a UE 3 to the core network 1 at any given time is referred to as the Serving RNS (SRNS) for that particular UE 3.
  • SRNS Serving RNS
  • FIG. 2 illustrates in very general terms the bearer structure used by UTRAN to carry user data between the UE 3 and the core network 1.
  • the responsible UMSC or SGSN 2 instructs the UTRAN 4 to establish a logical connection between the UMSC or SGSN 2 and the UE 3.
  • This logical connection is referred to as a Radio Access Bearer (RAB).
  • RAB Radio Access Bearer
  • the established RAB inherits requirements of the requested UMTS service, e.g. Quality of Service, etc.
  • the RNC 5,6 establishes user plane connections with the core network 1 (i.e. UMSC or SGSN 2) and with the UE 3.
  • the connection between the RNC 5,6 and the core network 1 is referred to as the Iu bearer whilst the connection between the RNC 5,6 and the UE 3 is referred to as the Radio Bearer (RB).
  • Both of these bearers represent further logical channels, with the RNC performing a mapping between them.
  • the bearers themselves are mapped onto appropriate traffic channels for transmission over the respective interfaces (Iu and Uu).
  • the Iu bearer In addition to carrying user data, the Iu bearer carries related control information between the UTRAN and the core network. Work is currently ongoing under the auspices of the European Telecommunications Standards Institute (ETSI) to specify the Iu User Plane (UP) protocol for carrying this control information.
  • ETSI European Telecommunications Standards Institute
  • UP User Plane
  • the specification is referred to as 25.415 and the current version is version 3.0.0 (1999-10).
  • the current version of the Iu UP protocol does not deal with error handling, i.e. it does not provide for an "abnormal event" procedure. It is acknowledged that such a procedure is necessary to deal with errors such as might occur, for example, during a call initialisation stage.
  • ETSI will define as part of the 25.415 recommendation a set of error types, together with an Iu UP Packet Data Unit (PDU) format for conveying error messages between Iu entities (in the UTRAN and in the core network).
  • PDU Packet Data Unit
  • an error message may pass through one or more intermediate entities on its journey between the originating entity and the terminating entity.
  • a potential problem with such a solution is that an entity receiving an error message may not know the source of an error message, even though it might know the error type and the identity of the last entity in the transmission path.
  • a method of reporting errors in a mobile telecommunications network comprising a core network and a UMTS Terrestrial Radio Access Network (UTRAN), the method comprising:
  • error messages are sent between a UMTS Mobile Switching Centre (UMSC) of the core network and a Radio Network Controller (RNC) of the UTRAN.
  • UMSC UMTS Mobile Switching Centre
  • RNC Radio Network Controller
  • the error message may be sent between two RNCs, via the core network.
  • the error message may be generated at either an Iu User Plane protocol instance or at an upper layer entity of the UMSC/RNC.
  • the message may be sent over the lu interface to either an Iu User Plane protocol instance or upper layer entity of the receiving UMSC/RNC.
  • the message may be sent to a peer entity, over the Iu interface, via respective Iu User Plane protocol instances at the sending and receiving nodes (where the term "node" identifies either a UMSC or an RNC).
  • the error message may be sent to an upper layer entity of the same node, as well as over the Iu interface.
  • the error message is incorporated into an abnormal event frame for sending over the Iu interface.
  • the frame is constructed at the Iu interface of the node where the error message is generated. More preferably, the frame contains an error type identifier ("cause value") and said distance counter.
  • a mobile telecommunications network comprising a core network and a UMTS Terrestrial Radio Access Network (UTRAN) each comprising a number of nodes communicating over an Iu interface with nodes of the other network, wherein each node comprises:
  • a typical UMTS network has been described above with reference to Figure 1 , whilst the UTRAN bearer structure employed in such a network has been described with reference to Figure 2 .
  • the Iu bearer illustrated in Figure 2 terminates in the RNC and UMSC at so-called Iu User Plane protocol instances.
  • Each of the Iu User Plane protocol instances communicate with upper layers of the same node, and in addition make use of a number of Iu UP functions.
  • Errors in the Iu User Plane can be classified as 'syntactical errors', 'semantical errors' or 'other errors'.
  • a field in a message is defined to be syntactically incorrect if the field contains an unknown value defined as "reserved", or if its value part violates syntactic rules given in the specification of the value part.
  • a message is defined to have semantically incorrect contents if it contains unexpected information which, possibly dependent on the state of the receiver, is in contradiction to the resources of the receiver and/or to the procedural part. Errors that are not seen as syntactical or semantical are defined as other errors. These errors include repeated failures of some procedures (e.g. Initialisation) and some error situations outside the Iu UP (e.g. initialisation failure at transcoder).
  • Error handling in the Iu User Plane is handled by an "abnormal event" procedure.
  • This procedure makes use of an Iu UP frame which is sent over the Iu interface and which is referred to as an "abnormal event” frame.
  • the abnormal event frame is illustrated in Figure 3 and contains a 'Cause value' which identifies the type of the error.
  • the abnormal event frame also contains a field termed 'Error distance' which identifies the distance (from the receiving entity) to the entity reporting the abnormal event.
  • the 'Error distance' is 0 when the error is originally sent.
  • the 'Error distance' is incremented by one.
  • the Error distance comprises two bits, and the four possible values are defined as follows:
  • An abnormal event procedure can be triggered at an RNC or UMSC by; an error detected by one of the Iu UP functions (e.g. received frame format unknown), a request made by upper layers (e.g. Initialisation failure in transcoder), or an abnormal event frame sent over the Iu UP.
  • an error detected by one of the Iu UP functions e.g. received frame format unknown
  • a request made by upper layers e.g. Initialisation failure in transcoder
  • an error is detected within an Iu UP function
  • one of the following actions is taken depending on the type of the error: (1) the error is reported to the upper layers (e.g. upper layer report to operation and maintenance level); (2) an abnormal event frame is sent over the Iu UP; (3) an abnormal event frame is sent over the Iu UP and the error is reported to the upper layers; or (4) no action is taken.
  • the upper layers e.g. upper layer report to operation and maintenance level
  • an abnormal event frame is sent over the Iu UP
  • an abnormal event frame is sent over the Iu UP and the error is reported to the upper layers
  • no action is taken.
  • an abnormal event frame should be sent over the Iu interface indicating the appropriate error type.
  • an Iu-Status-Indication indicating the abnormal event is sent from there to the upper layers.
  • FIG. 4 shows this "external" error case where the abnormal event procedure is originally triggered by an Iu-UP-Status-Request.
  • the abnormal event procedure acts on the received message by sending an abnormal event frame over the Iu interface.
  • the reception of an abnormal event frame triggers an abnormal event procedure there, and an Iu-UP-Status-Indication is sent to the associated upper layers.
  • the handling is symmetrical over the Iu UP protocol.
  • Figure 5 below shows an "internal" error case where the abnormal event procedure is originally triggered by an Iu UP function associated with an Iu User Plane protocol instance.
  • the abnormal event procedure acts on this message by sending an abnormal event frame over the Iu interface.
  • the reception of the abnormal event frame triggers a further abnormal event procedure, and an Iu-UP-Status-Indication is sent to the upper layers from the peer Iu User Plane protocol instance.
  • the handling is symmetrical over the Iu UP protocol.
  • a code may be incorporated which identifies the source of the error.
  • a code 0 may indicate that the error originating entity is an upper layer at a peer node (an application error)
  • a code 1 may indicate that the error originating entity is an Iu UP protocol instance at a peer node (an Iu UP function error)
  • a code 2 may indicate that the error originating entity is an Iu UP protocol instance at the same node as the destination entity (again an Iu UP function error).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Small-Scale Networks (AREA)
EP00972892A 1999-12-02 2000-11-07 Error reporting in a mobile telecommunications network Expired - Lifetime EP1245105B1 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
GB9928546A GB2357010B (en) 1999-12-02 1999-12-02 Error reporting in a mobile telecommunications network
GB9928546 1999-12-02
PCT/EP2000/011011 WO2001041394A1 (en) 1999-12-02 2000-11-07 Error reporting in a mobile telecommunications network

Publications (2)

Publication Number Publication Date
EP1245105A1 EP1245105A1 (en) 2002-10-02
EP1245105B1 true EP1245105B1 (en) 2008-07-30

Family

ID=10865609

Family Applications (1)

Application Number Title Priority Date Filing Date
EP00972892A Expired - Lifetime EP1245105B1 (en) 1999-12-02 2000-11-07 Error reporting in a mobile telecommunications network

Country Status (13)

Country Link
US (1) US6785243B2 (zh)
EP (1) EP1245105B1 (zh)
JP (1) JP4571364B2 (zh)
CN (1) CN1201543C (zh)
AR (1) AR026908A1 (zh)
AT (1) ATE403322T1 (zh)
AU (1) AU775808B2 (zh)
DE (1) DE60039716D1 (zh)
GB (1) GB2357010B (zh)
MY (1) MY121508A (zh)
PL (1) PL355536A1 (zh)
TW (1) TW494664B (zh)
WO (1) WO2001041394A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FI109753B (fi) * 2000-01-14 2002-09-30 Nokia Corp Tietoliikennejärjestelmä, jolla on parannettu vikasieto
FR2827110B1 (fr) * 2001-07-09 2005-06-24 Cit Alcatel Procede de traitement d'appels umts dans un reseau de transmission de paquets, et noeud pour reseau umts, pour la mise en oeuvre de ce procede
US8977284B2 (en) 2001-10-04 2015-03-10 Traxcell Technologies, LLC Machine for providing a dynamic data base of geographic location information for a plurality of wireless devices and process for making same
ATE453304T1 (de) * 2005-05-25 2010-01-15 Ericsson Telefon Ab L M Paketeinteilung in einem funkzugangssystem
US7729299B2 (en) * 2007-04-20 2010-06-01 Cisco Technology, Inc. Efficient error response in a video conferencing system
US8699412B2 (en) 2009-01-05 2014-04-15 Qualcomm Incorporated Method and apparatus for cell barring in a wireless communication system

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5325524A (en) * 1989-04-06 1994-06-28 Digital Equipment Corporation Locating mobile objects in a distributed computer system
AU664864B2 (en) * 1991-10-01 1995-12-07 Broadcom Corporation A radio frequency local area network
JPH118877A (ja) * 1997-06-17 1999-01-12 Nec Commun Syst Ltd 移動体通信方式
JP3094957B2 (ja) * 1997-06-30 2000-10-03 日本電気株式会社 移動通信システムの上り選択サイトダイバーシチにおける無線基地局受信データ伝送システム
US6374303B1 (en) * 1997-11-17 2002-04-16 Lucent Technologies, Inc. Explicit route and multicast tree setup using label distribution
US6119170A (en) * 1997-12-29 2000-09-12 Bull Hn Information Systems Inc. Method and apparatus for TCP/IP multihoming on a host system configured with multiple independent transport provider systems
KR100318940B1 (ko) * 1998-04-17 2002-04-22 윤종용 이동통신시스템에서의호장애시재접속방법
US7715837B2 (en) * 2000-02-18 2010-05-11 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for releasing connections in an access network

Also Published As

Publication number Publication date
GB2357010A (en) 2001-06-06
MY121508A (en) 2006-01-28
US6785243B2 (en) 2004-08-31
CN1201543C (zh) 2005-05-11
AU1146001A (en) 2001-06-12
AR026908A1 (es) 2003-03-05
DE60039716D1 (de) 2008-09-11
ATE403322T1 (de) 2008-08-15
CN1402928A (zh) 2003-03-12
PL355536A1 (en) 2004-05-04
JP4571364B2 (ja) 2010-10-27
EP1245105A1 (en) 2002-10-02
GB2357010B (en) 2003-09-24
GB9928546D0 (en) 2000-02-02
WO2001041394A1 (en) 2001-06-07
US20020128005A1 (en) 2002-09-12
AU775808B2 (en) 2004-08-19
JP2003516040A (ja) 2003-05-07
TW494664B (en) 2002-07-11

Similar Documents

Publication Publication Date Title
EP1232667B1 (en) Srns relocation in a umts network
EP1051870B1 (en) Method for connection reconfiguration in cellular radio network
US5664004A (en) Support of multiplicity of radio interfaces over an interface between a base station system and a mobile switch
JP2006518122A (ja) 通信システムのためのルーティング手順
US11706665B2 (en) Enhanced handling on 5G QoS operations
EP1379097A1 (en) Method of furnishing illegal mobile equipment user information
US7792525B2 (en) Method for activating recordings of events concerning terminals and equipment therefor
KR100971067B1 (ko) 셀룰러 통신 시스템의 무선 베어러 관리
US20070178901A1 (en) Distributed base station controller
EP1245105B1 (en) Error reporting in a mobile telecommunications network
US8116272B2 (en) Method for dealing with the packet domain gateway support node errors
KR100346344B1 (ko) 통신 시스템에서 트랜스코더의 스위칭시 동기를 제공하기 위한 방법 및 장치
US20060046724A1 (en) Soft handoff management
KR20020091953A (ko) 무선패킷서비스 터널링 프로토콜에서 터널을 감시하는 방법
GB2369002A (en) Mobility management in a UMTS network
EP1352533B1 (en) Interconnecting core network nodes in a telecommunication network
KR20000075163A (ko) 이동 통신 시스템에서 이종 교환국과 접속하는 무선 엑세스 네트워크의 운영 방법
EP2139251B1 (en) Method for reporting that a cell does not support an uplink high-order modulation and apparatus thereof
GB2354908A (en) Redirection of active communication from one radio network controller to another

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

AK Designated contracting states

Kind code of ref document: A1

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

AX Request for extension of the european patent

Free format text: AL;LT;LV;MK;RO;SI

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

Owner name: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)

17Q First examination report despatched

Effective date: 20070810

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): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REF Corresponds to:

Ref document number: 60039716

Country of ref document: DE

Date of ref document: 20080911

Kind code of ref document: P

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

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

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20081110

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20081230

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

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080730

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080730

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

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080730

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

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080730

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

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

Ref country code: MC

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20081130

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

26N No opposition filed

Effective date: 20090506

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

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20081130

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20081107

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20081130

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

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20081107

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080730

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

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20081031

REG Reference to a national code

Representative=s name: MARKS & CLERK (LUXEMBOURG) LLP, LU

Ref country code: DE

Ref legal event code: R082

Ref document number: 60039716

Country of ref document: DE

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

Ref legal event code: R081

Ref document number: 60039716

Country of ref document: DE

Owner name: IDTP HOLDINGS, INC., WILMINGTON, US

Free format text: FORMER OWNER: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL), STOCKHOLM, SE

REG Reference to a national code

Ref country code: FR

Ref legal event code: TP

Owner name: IDTP HOLDINGS, INC., US

Effective date: 20160125

REG Reference to a national code

Ref country code: NL

Ref legal event code: PD

Owner name: IDTP HOLDINGS, INC.; US

Free format text: DETAILS ASSIGNMENT: VERANDERING VAN EIGENAAR(S), OVERDRACHT; FORMER OWNER NAME: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)

Effective date: 20151030

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

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 19

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

Ref country code: NL

Payment date: 20191127

Year of fee payment: 20

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

Ref country code: FR

Payment date: 20191128

Year of fee payment: 20

Ref country code: IT

Payment date: 20191122

Year of fee payment: 20

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

Ref country code: DE

Payment date: 20191230

Year of fee payment: 20

Ref country code: GB

Payment date: 20191128

Year of fee payment: 20

REG Reference to a national code

Ref country code: DE

Ref legal event code: R071

Ref document number: 60039716

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: MK

Effective date: 20201106

REG Reference to a national code

Ref country code: GB

Ref legal event code: PE20

Expiry date: 20201106

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