EP3211861A1 - Electric power system - Google Patents

Electric power system Download PDF

Info

Publication number
EP3211861A1
EP3211861A1 EP16193035.9A EP16193035A EP3211861A1 EP 3211861 A1 EP3211861 A1 EP 3211861A1 EP 16193035 A EP16193035 A EP 16193035A EP 3211861 A1 EP3211861 A1 EP 3211861A1
Authority
EP
European Patent Office
Prior art keywords
client
service request
server
response
time
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.)
Granted
Application number
EP16193035.9A
Other languages
German (de)
French (fr)
Other versions
EP3211861B1 (en
Inventor
Jae-Hong CHA
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.)
LS Electric Co Ltd
Original Assignee
LSIS Co Ltd
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 LSIS Co Ltd filed Critical LSIS Co Ltd
Publication of EP3211861A1 publication Critical patent/EP3211861A1/en
Application granted granted Critical
Publication of EP3211861B1 publication Critical patent/EP3211861B1/en
Not-in-force legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/56Provisioning of proxy services
    • H04L67/562Brokering proxy services
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05FSYSTEMS FOR REGULATING ELECTRIC OR MAGNETIC VARIABLES
    • G05F1/00Automatic systems in which deviations of an electric quantity from one or more predetermined values are detected at the output of the system and fed back to a device within the system to restore the detected quantity to its predetermined value or values, i.e. retroactive systems
    • G05F1/66Regulating electric power
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/12Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks

Definitions

  • the present invention relates to a communication apparatus in an electric power system and a communication method for the same and, more particularly, a communication apparatus in an electric power system which is capable of announcing, to a client, a reason for no response from a server as a data processing time is longer than a timeout time of the client and proposing a solution to handle the situation and a communication method for the same.
  • An electric power system includes a supervisory control and data acquisition (SCADA), an energy management system (EMS), and a distribution management system (DMS). These systems store values acquired from a device in a real time database (RTDB) of a server. A client performs alarm processing, data processing, control processing and history processing, using the values stored in the RTDB of the server.
  • SCADA supervisory control and data acquisition
  • EMS energy management system
  • DMS distribution management system
  • the request-response communication is implemented by a 3 Tier architecture of Requester-Broker-Replier.
  • Fig. 1 illustrates configuration of client-server communication in a typical 3 Tier architecture.
  • Client-server communication of the 3 Tier architecture may include a requester 110, a broker 120 and a replier 130.
  • the requester 110 which is usually implemented in the client, requests a service and is provided with the service from the replier 130.
  • the replier 130 which is usually implemented in the server, processes the request for the service from the requester 110 and sends a response to the requester 110.
  • the broker 120 serves to relay messages between the requester 110 and the replier 130.
  • the requester 110 may set a timeout for the message.
  • the timeout is a waiting time for which a response is awaited. That is, the timeout represents duration from the time at which a request is made by the requester 110 to the time at which a response is made by the replier 130.
  • the requester 110 performs a next operation without waiting for the response anymore. That is, when asynchronous communication is performed, the requester 110 transmits a service request again, considering that the previous service request has failed.
  • a communication apparatus in an electric power system includes a communication unit operative to communicate with a client and server included in the electric power system to relay a service request received from the client to the server and relay a response to the service request received from the server to the client, a comparison/determination unit operative to compare a timeout time taken for the client to wait for the response to the service request with a processing time taken for the server to process the service request, and a controller operative to control the communication unit and the comparison/determination unit and to announce to the client that the processing time is longer than the timeout time when the processing time is longer than the timeout time.
  • an electric power control system includes a client operative to transmit a service request to a communication apparatus and receive a response to the service request processed by the server via the communication apparatus; and a communication apparatus operative to relay the service request received from the client to the server, relay the response to the service request received from the server to the client, compare a timeout time taken for the client to wait for the response to the service request with a processing time taken for the server to process the service request, and announce to the client that the processing time is longer than the timeout time when the processing time is longer than the timeout time, and a server operative to process the service request received from the communication apparatus and transmit the response to the service request to the communication apparatus.
  • a method for performing communication by a communication apparatus in an electric power system includes receiving a service request from a client and relaying the same to a server; receiving, from the server, a response to the service request; comparing a timeout time taken for the client to wait for the response to the service request with a processing time taken for the server to process the service request; and announcing to the client that the processing time is longer than the timeout time in relaying the response to the client when the processing time is longer than the timeout time.
  • the broker compares the times and announces, to the user, a reason for failing to send a response to the request to the requester, using a log file or message. Thereby, the time taken to analyze the cause may be reduced.
  • Fig. 2 is a block diagram illustrating configuration of a communication apparatus according to an embodiment of the present invention.
  • a communication apparatus 200 may be included in an electric power system 400.
  • the electric power system 400 will be described in detail with reference to Fig. 6 later.
  • the communication apparatus 200 may include a communication unit 210, a comparison/determination unit 220 and a controller 230.
  • the communication unit 210 may communicate with a client 240 and a server 250, which are included in the electric power system 400.
  • Schemes used by the communication unit 210 to communicate with the client 240 and the server 250 may include various wired/wireless communication schemes.
  • the communication unit 210 may perform wired communication with the client 240 and server 250 via a cable, wire or power line which connects the communication unit 210 to the client 240 and server 250, or perform wireless communication including short-range communication, wireless LAN communication, mobile communication and data communication.
  • the communication unit 210, the client 240 and server 250 may configure client-server communication of the 3 Tier architecture.
  • Client-server communication of the 3 Tier architecture will be described with reference to Fig. 6 later.
  • the communication unit 210 may relay a service request received from the client 240 to the server 250, and relay, to the client 240, a response received from the server 250 in response to the service request.
  • the service request may contain a frame field for a timeout time.
  • the timeout time may be a time for which the client 240 waits for a response to the service request.
  • the response to the service request may contain a frame field for a processing time.
  • the processing time may be a time to process the service request.
  • the frame field for the timeout time will be described in detail with reference to Fig. 3 , and the frame field for the processing time will be described in detail with reference to Fig. 4 later.
  • the comparison/determination unit 220 may compare the timeout time for which the client 240 waits for a response to the service request with the processing time for which the server 250 processes the service request.
  • the comparison/determination unit 220 may compare the timeout time with the processing time to determine whether the processing time is longer than the timeout time.
  • the comparison/determination unit 220 may include a calculation block for performing the operation of addition (+) and/or subtraction (-).
  • the comparison/determination unit 220 may determine a delay time between the timeout time and the time at which a response to the service request is made.
  • controller 230 may control the communication unit 210 and the comparison/determination unit 220 to operate.
  • the controller 230 may announce to the client 240 that the processing time is longer than the timeout time.
  • the controller 230 may control the communication unit 210 to transmit, to the client 240, a message containing a frame field indicating that the processing time is longer than the timeout time.
  • the message containing the frame field indicating that the processing time is longer than the timeout time will be described with reference to Fig. 5 later.
  • the controller 230 may generate a log file for recording the information indicating that the processing time is longer than the timeout time.
  • the log file is a record of operation of the system.
  • the log file may include all records related to operation of the system including a system operation record, change of the system condition, switch selection, details about an input/output device, data input through a control console, and the condition of the system when the system is stopped or the cause of the stopping.
  • a log file for details of the event may be generated or the details may be automatically recorded in the log file present in the system.
  • the controller 230 may control the communication unit 210 to transmit, to the client 240, a message indicating that the timeout time should be adjusted based on the delay time.
  • Figs. 3 to 5 illustrate frame configuration of messages that a communication apparatus transmits/receives to/from a client and server according to an embodiment of the present invention.
  • Fig. 3 shows a service request message 310 transmitted from the client 240.
  • the service request message 310 may include a header field 311, a request data field 312, a timeout field 313, and a reserved field 314.
  • the header field 311 may include information necessary for routing and delivery of the service request message 310.
  • the request data field 312 includes information about a service request which the client 240 sends to the server 250.
  • the timeout field 313 includes information about a time for which the client 240 waits for a response to the service request.
  • the Reserved field 314 is a field reserved in preparation for an unexpected event.
  • the service request message 310 which the client 240 transmits to the communication apparatus 200 contains the timeout field 313. Thereby, the communication apparatus 200 and the server 250 may recognize the timeout time of the client 240 from the service request message 310.
  • Fig. 4 shows a response message 320 for the service request transmitted from the server 250.
  • the response message 320 may include a header field 321, a response data field 322, a server processing time field 323 and a reserved field 324
  • the header field 321 includes information necessary for routing and delivery of the response message 320 corresponding to the service request.
  • the response data field 322 includes information about a response to the service request of the client 240 processed by the server 250.
  • the server processing time field 323 includes information about time taken for the server 250 to process the service request of the client 240.
  • the reserved field 324 is a field reserved in preparation for an unexpected event.
  • the response message 320 for the service request transmitted from the server 250 to the communication apparatus 200 contains the server processing time field 323. Thereby, the communication apparatus 200 and the client 240 receiving the response message 320 for the service request may recognize the processing time of the server 250 through the message.
  • Fig. 5 shows response messages 330 and 340 for a service request transmitted from the communication apparatus 200 to the client 240.
  • the communication apparatus 200 may announce to the client 240 that the processing time is longer than the timeout time.
  • the communication apparatus 200 may add a fail reason frame 325 indicating a reason for failure of a service response to the response message 320.
  • the response messages 330 and 340 transmitted to the client 240 in response to the service request may include a header field 321, a response data field 322, a fail reason frame field 325 and a reserved field 324.
  • the server processing time field 323 may or may not be included.
  • the fail reason frame field 325 may include a reason for failure of a service response. For example, if the processing time of the server 250 is longer than the timeout time of the client 240, the fail reason frame field 325 is set to 1. If the processing time of the server 250 is shorter than or equal to the timeout time of the client 240, the fail reason frame field 325 is set to 0.
  • the response messages 330 and 340 transmitted from the communication apparatus 200 to the client 240 in response to the service request contain the fail reason frame field 325.
  • the client 240 receiving the response messages 330 and 340 for the service request may recognize the reason for failure of the service request.
  • the client 240 may recognize that a response to the service request has not been received for the reason that the processing time of the server 250 is longer than the timeout time of the client 240 rather than for the reason of a communication error, by analyzing the messages.
  • Fig. 6 illustrates configuration of client-server communication in a 3 Tier architecture in an electric power system according to an embodiment of the present invention.
  • the electric power system 400 may include a client 240, a communication apparatus 200 and a server 250.
  • the client 240 transmits a service request to the communication apparatus 200, and receives a response to the service request processed by the server 250 via the communication apparatus 200.
  • the communication apparatus 200 may relay the service request received from the client 240 to the server 250, and relay, to the client 240, the response to the service request received from the server 250.
  • the communication apparatus 200 may compare a timeout time for which the client 240 waits for the response to the service request with a processing time for which the server 250 processes the service request. If the processing time is longer than the timeout time, the communication apparatus 200 may announce to the client 240 that the processing time is longer than the timeout time.
  • the server 250 may process the service request received from the communication apparatus 200, and transmit a response to the service request to the communication apparatus 200.
  • the electric power system 400 described above may perform client-server communication in the 3 Tier architecture.
  • the client-server communication model of the 3 Tier architecture is proposed to address an issue raised in the client-server communication model of the 2 Tier architecture, which maintains a one-to-one service relationship between the client and the server.
  • the 3 Tier architecture has a middle tier dedicated to application processing, and the client request all services to the middle tier.
  • the middle tier communicates with a final server such as a database server, and then delivers a result of communication to the client.
  • the client-server communication model of the 3 Tier architecture is configured as follows.
  • the 3 Tier architecture is advantageous in terms of service scalability, stability and efficiency, and is thus suitable for a high-capacity service.
  • a request from the client is not directly delivered to the server in the 3 Tier architecture. Accordingly, load to the server does not increase in proportion to the number of clients.
  • the client 240 is a requester corresponding to Tier 1.
  • the communication apparatus 200 is a broker corresponding to Tier 2
  • the server 250 is a replier corresponding to Tier 3.
  • an observation function is added to the broker 200. Thereafter, if the data processing time of the replier 250 is longer than the timeout time of the requester 240, the broker 200 announces to the requester 240 that the data processing time is longer than the timeout time.
  • the broker 200 announces the reason to the user through a log file or message.
  • the requester 240 When transmitting a message for a service request, the requester 240 delivers a timeout time to the broker 200 through the message.
  • the broker 200 is provided with a Thread having a separate observation function. Thereby, the broker 200 stores the timeout time of the requester 240 as stored in the requester 240, and then relays a received message to the replier 250.
  • the replier 250 measures the data processing time from the moment at which the replier 250 receives the message, and sends a response message containing a frame field for the data processing time to the broker 200.
  • the replier 250 measures the data processing time from the moment at which the replier 250 receives the message.
  • the timeout time of the requester 240 is counted from the time at which a data request is made, and thus the processing time is not synchronized with the start time of the timeout time. Accordingly, to allow the broker 200 to compare the data processing time with the timeout time, the replier 250 adds the duration from the time at which the requester 240 makes a request to the time at which the request is delivered to the replier 250 to the data processing time of the replier 250, and then transmit the data processing time to the broker 200.
  • the broker 200 compares the data processing time in the message received from the replier 250 with the registered timeout time of the requester 250 which is to be transmitted. If the timeout time is shorter than the data processing time, the broker 200 announces a reason for transmission failure to the user through a log file or message.
  • Failure of response to the service request may occur for various reasons. According to this embodiment, if a response is not issued for the waiting time of the requester 240 simply because the data processing time of the replier 250 is long, this information may be presented and a solution may be proposed.
  • Fig. 7 illustrates a procedure of communication among a communication apparatus, a client and a server in an electric power system according to an embodiment of the present invention.
  • the client 240 When the client 240 makes a service request, the client 240 adds a timeout frame field to a service request message (S501).
  • the client 240 transmits the service request message containing the timeout frame field to the communication apparatus 200 to make a service request to the communication apparatus 200 (S502).
  • the communication apparatus 200 Upon receiving the service request from the client and 240, the communication apparatus 200 relays the service request to the server 250 (S503)
  • the server 250 processes the service request of the client 240 (S504).
  • the server 250 After processing the service request, the server 250 adds a data processing time frame field to a response message for the service request (S505). To this end, the server 250 measures the data processing time from the moment at which the server 250 receives the service request. Then, the server 250 adds a frame field for the data processing time to a response message for the request and sends the response message to the communication apparatus 200.
  • the server 250 transmits a response to the service request to the communication apparatus 200 (S506).
  • the communication apparatus 200 determines whether the timeout time is shorter than the data processing time. If the timeout time is shorter than the data processing time, the communication apparatus 200 adds an alarm field indicating this information to the response message for the service request (S507).
  • the communication apparatus 200 relays the response to the service request to the client 240 (S508).
  • Fig. 8 illustrates a procedure of communication of a communication apparatus in an electric power system according to an embodiment of the present invention.
  • the communication apparatus 200 receives a service request from the client 240 and relays the same to the server 250 (S601).
  • the communication apparatus 200 receives a response to the service request from the server 250 (S602).
  • the communication apparatus 200 compares the timeout time for which the client 240 waits for the response to the service request with a processing time for which the server 250 processes the service request (S603).
  • the communication apparatus 200 Upon determining that the processing time is longer than the timeout time (S604-Yes), the communication apparatus 200 delivers the response to the service request to the client 240, announcing that the processing time is longer than the timeout time (S605).
  • the communication apparatus 200 may transmit, to the client 240, a message indicating that the processing time is longer than the timeout time.
  • the communication apparatus 200 may generate a log file in which information indicating that the processing time is longer than the timeout time is recorded.
  • the communication apparatus 200 may relay the response to the service request to the client 240, announcing that processing of the service request has failed (S606).
  • the client 240 may distinguish between a case where the response to the service request fails to be received because the processing time is longer than the timeout time and a case where processing of the service request fails because there is a problem with a router or application. Further the client 240 may take a proper action according to each situation.
  • the broker compares the times and announces, to the user, a reason for failing to send a response to the request to the requester through a log file or message. Thereby, the time taken to analyze the cause may be reduced.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Physics & Mathematics (AREA)
  • Power Engineering (AREA)
  • Electromagnetism (AREA)
  • General Physics & Mathematics (AREA)
  • Radar, Positioning & Navigation (AREA)
  • Automation & Control Theory (AREA)
  • Remote Monitoring And Control Of Power-Distribution Networks (AREA)
  • Computer And Data Communications (AREA)
  • Telephonic Communication Services (AREA)
  • Debugging And Monitoring (AREA)

Abstract

Disclosed herein is an electric power control system (400) including a communication apparatus (200), a server (250), and a client (240), wherein the communication apparatus includes a communication unit (210) operative to communicate with the client and server included in the electric power system to relay the service request received from the client to the server and relay the response to the service request received from the server to the client, a comparison/determination unit (220) operative to compare a timeout time taken for the client to wait for the response to the service request with a processing time taken for the server to process the service request, and a controller (230) operative to control the communication unit and the comparison/determination unit and to announce to the client that the processing time is longer than the timeout time when the processing time is longer than the timeout time.

Description

    BACKGROUND 1. Technical Field
  • The present invention relates to a communication apparatus in an electric power system and a communication method for the same and, more particularly, a communication apparatus in an electric power system which is capable of announcing, to a client, a reason for no response from a server as a data processing time is longer than a timeout time of the client and proposing a solution to handle the situation and a communication method for the same.
  • 2. Description of the Related Art
  • An electric power system includes a supervisory control and data acquisition (SCADA), an energy management system (EMS), and a distribution management system (DMS). These systems store values acquired from a device in a real time database (RTDB) of a server. A client performs alarm processing, data processing, control processing and history processing, using the values stored in the RTDB of the server.
  • In the communication architecture of an application constituting the electric power system, the request-response communication is implemented by a 3 Tier architecture of Requester-Broker-Replier.
  • Fig. 1 illustrates configuration of client-server communication in a typical 3 Tier architecture.
  • Client-server communication of the 3 Tier architecture may include a requester 110, a broker 120 and a replier 130.
  • The requester 110, which is usually implemented in the client, requests a service and is provided with the service from the replier 130.
  • The replier 130, which is usually implemented in the server, processes the request for the service from the requester 110 and sends a response to the requester 110.
  • The broker 120 serves to relay messages between the requester 110 and the replier 130.
  • In transmitting a message, the requester 110 may set a timeout for the message. The timeout is a waiting time for which a response is awaited. That is, the timeout represents duration from the time at which a request is made by the requester 110 to the time at which a response is made by the replier 130.
  • If there is no response within the timeout time, the requester 110 performs a next operation without waiting for the response anymore. That is, when asynchronous communication is performed, the requester 110 transmits a service request again, considering that the previous service request has failed.
  • If the data processing time of the replier 130 is longer than the timeout time set by the requester 110, and thus a response cannot be sent, there is no way for the requester 110 to recognize this situation. Thereby, the requester 110 cannot recognize the cause of failure of the request.
  • SUMMARY
  • It is an aspect of the present invention to provide a communication apparatus in an electric power system which has a 3 Tier communication architecture including a requester, a broker and a replier and is capable of announcing, through a message or a log file, a reason for the replier to fail to send a response to the requester as a data processing time of the replier is longer than a timeout time of the requester, by providing a separate observation function to the broker and proposing a solution to handle the situation and a communication method for the same.
  • Objects of the proposed embodiments are not limited to the aforementioned objects, and other objects which are not mentioned above will become apparent to those having ordinary skill in the art upon examination of the following description.
  • In accordance with one aspect of the present invention, a communication apparatus in an electric power system includes a communication unit operative to communicate with a client and server included in the electric power system to relay a service request received from the client to the server and relay a response to the service request received from the server to the client, a comparison/determination unit operative to compare a timeout time taken for the client to wait for the response to the service request with a processing time taken for the server to process the service request, and a controller operative to control the communication unit and the comparison/determination unit and to announce to the client that the processing time is longer than the timeout time when the processing time is longer than the timeout time.
  • In accordance with another aspect of the present invention, an electric power control system includes a client operative to transmit a service request to a communication apparatus and receive a response to the service request processed by the server via the communication apparatus; and a communication apparatus operative to relay the service request received from the client to the server, relay the response to the service request received from the server to the client, compare a timeout time taken for the client to wait for the response to the service request with a processing time taken for the server to process the service request, and announce to the client that the processing time is longer than the timeout time when the processing time is longer than the timeout time, and a server operative to process the service request received from the communication apparatus and transmit the response to the service request to the communication apparatus.
  • In accordance with another aspect of the present invention, a method for performing communication by a communication apparatus in an electric power system includes receiving a service request from a client and relaying the same to a server; receiving, from the server, a response to the service request; comparing a timeout time taken for the client to wait for the response to the service request with a processing time taken for the server to process the service request; and announcing to the client that the processing time is longer than the timeout time in relaying the response to the client when the processing time is longer than the timeout time.
  • According to embodiments of the present invention, when a data processing time of a replier is longer than a timeout time set by a requester in the 3 Tier architecture of Requester-Broker-Replier, the broker compares the times and announces, to the user, a reason for failing to send a response to the request to the requester, using a log file or message. Thereby, the time taken to analyze the cause may be reduced.
  • BRIEF DESCRIPTION OF THE DRAWINGS
    • Fig. 1 illustrates configuration of client-server communication in a typical 3 Tier architecture.
    • Fig. 2 is a block diagram illustrating configuration of a communication apparatus according to an embodiment of the present invention.
    • Figs. 3 to 5 illustrate frame configuration of messages that a communication apparatus transmits/receives to/from a client and server according to an embodiment of the present invention.
    • Fig. 6 illustrates configuration of client-server communication in a 3 Tier architecture in an electric power system according to an embodiment of the present invention.
    • Fig. 7 illustrates a procedure of communication among a communication apparatus, a client and a server in an electric power system according to an embodiment of the present invention.
    • Fig. 8 illustrates a procedure of communication of a communication apparatus in an electric power system according to an embodiment of the present invention.
    DETAILED DESCRIPTION
  • Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. It should be understood that the present invention is not limited to the following embodiments, and that the embodiments are provided for illustrative purposes only. It will be appreciated by those skilled in the art that various substitutions, modifications and variations can be made in the present invention without departing from the scope of the present invention.
  • Although the terms used in this specification are selected, as much as possible, from general terms that are widely used at present, terms that are arbitrarily selected by the applicant may be used in a particular case. In this case, meanings of these terms are disclosed in corresponding description parts of the invention. Accordingly, it should be noted that the present invention should be understood based on practical meanings of the terms rather than on the names of the terms. In the following description, the term "include" should not be understood as pre-excluding possibility of existence of constituents or steps other than the constituents or steps disclosed herein.
  • Fig. 2 is a block diagram illustrating configuration of a communication apparatus according to an embodiment of the present invention.
  • According to an embodiment of the present invention, a communication apparatus 200 may be included in an electric power system 400. The electric power system 400 will be described in detail with reference to Fig. 6 later.
  • The communication apparatus 200 may include a communication unit 210, a comparison/determination unit 220 and a controller 230.
  • The communication unit 210 may communicate with a client 240 and a server 250, which are included in the electric power system 400.
  • Schemes used by the communication unit 210 to communicate with the client 240 and the server 250 may include various wired/wireless communication schemes. Specifically, the communication unit 210 may perform wired communication with the client 240 and server 250 via a cable, wire or power line which connects the communication unit 210 to the client 240 and server 250, or perform wireless communication including short-range communication, wireless LAN communication, mobile communication and data communication.
  • In this case, the communication unit 210, the client 240 and server 250 may configure client-server communication of the 3 Tier architecture. Client-server communication of the 3 Tier architecture will be described with reference to Fig. 6 later.
  • The communication unit 210 may relay a service request received from the client 240 to the server 250, and relay, to the client 240, a response received from the server 250 in response to the service request.
  • The service request may contain a frame field for a timeout time. The timeout time may be a time for which the client 240 waits for a response to the service request. The response to the service request may contain a frame field for a processing time. The processing time may be a time to process the service request. The frame field for the timeout time will be described in detail with reference to Fig. 3, and the frame field for the processing time will be described in detail with reference to Fig. 4 later.
  • The comparison/determination unit 220 may compare the timeout time for which the client 240 waits for a response to the service request with the processing time for which the server 250 processes the service request.
  • Specifically, the comparison/determination unit 220 may compare the timeout time with the processing time to determine whether the processing time is longer than the timeout time. To this end, the comparison/determination unit 220 may include a calculation block for performing the operation of addition (+) and/or subtraction (-).
  • If the processing time is longer than the timeout time, the comparison/determination unit 220 may determine a delay time between the timeout time and the time at which a response to the service request is made.
  • As described above, the controller 230 may control the communication unit 210 and the comparison/determination unit 220 to operate.
  • If the processing time is longer than the timeout time, the controller 230 may announce to the client 240 that the processing time is longer than the timeout time.
  • According to an embodiment, the controller 230 may control the communication unit 210 to transmit, to the client 240, a message containing a frame field indicating that the processing time is longer than the timeout time. The message containing the frame field indicating that the processing time is longer than the timeout time will be described with reference to Fig. 5 later.
  • According to another embodiment, the controller 230 may generate a log file for recording the information indicating that the processing time is longer than the timeout time.
  • The log file is a record of operation of the system. The log file may include all records related to operation of the system including a system operation record, change of the system condition, switch selection, details about an input/output device, data input through a control console, and the condition of the system when the system is stopped or the cause of the stopping. When a corresponding event occurs, a log file for details of the event may be generated or the details may be automatically recorded in the log file present in the system.
  • Once the comparison/determination unit 220 determines the delay time from the timeout time to the time at which a response to the service request is made by comparing the timeout time with the processing time, the controller 230 may control the communication unit 210 to transmit, to the client 240, a message indicating that the timeout time should be adjusted based on the delay time.
  • Figs. 3 to 5 illustrate frame configuration of messages that a communication apparatus transmits/receives to/from a client and server according to an embodiment of the present invention.
  • Fig. 3 shows a service request message 310 transmitted from the client 240. Specifically, the service request message 310 may include a header field 311, a request data field 312, a timeout field 313, and a reserved field 314.
  • The header field 311 may include information necessary for routing and delivery of the service request message 310.
  • The request data field 312 includes information about a service request which the client 240 sends to the server 250.
  • The timeout field 313 includes information about a time for which the client 240 waits for a response to the service request.
  • The Reserved field 314 is a field reserved in preparation for an unexpected event.
  • Referring to Fig. 3, the service request message 310 which the client 240 transmits to the communication apparatus 200 contains the timeout field 313. Thereby, the communication apparatus 200 and the server 250 may recognize the timeout time of the client 240 from the service request message 310.
  • Fig. 4 shows a response message 320 for the service request transmitted from the server 250. Specifically, the response message 320 may include a header field 321, a response data field 322, a server processing time field 323 and a reserved field 324
  • The header field 321 includes information necessary for routing and delivery of the response message 320 corresponding to the service request.
  • The response data field 322 includes information about a response to the service request of the client 240 processed by the server 250.
  • The server processing time field 323 includes information about time taken for the server 250 to process the service request of the client 240.
  • The reserved field 324 is a field reserved in preparation for an unexpected event.
  • Referring to Fig. 4, the response message 320 for the service request transmitted from the server 250 to the communication apparatus 200 contains the server processing time field 323. Thereby, the communication apparatus 200 and the client 240 receiving the response message 320 for the service request may recognize the processing time of the server 250 through the message.
  • Fig. 5 shows response messages 330 and 340 for a service request transmitted from the communication apparatus 200 to the client 240. When the communication apparatus 200 determines that the processing time of the service request in the server 250 is longer than the timeout time of the client 240, the communication apparatus 200 may announce to the client 240 that the processing time is longer than the timeout time. Specifically, as shown in Fig. 4, upon receiving the response message 320 for the service request from the server 250, the communication apparatus 200 may add a fail reason frame 325 indicating a reason for failure of a service response to the response message 320.
  • In this case, the response messages 330 and 340 transmitted to the client 240 in response to the service request may include a header field 321, a response data field 322, a fail reason frame field 325 and a reserved field 324. In some embodiments, the server processing time field 323 may or may not be included.
  • The fail reason frame field 325 may include a reason for failure of a service response. For example, if the processing time of the server 250 is longer than the timeout time of the client 240, the fail reason frame field 325 is set to 1. If the processing time of the server 250 is shorter than or equal to the timeout time of the client 240, the fail reason frame field 325 is set to 0.
  • The other frame fields 321, 322, 323 and 324 have already been described above with reference to Fig. 4, and thus the description thereof will not be given below.
  • Referring to Fig. 5, the response messages 330 and 340 transmitted from the communication apparatus 200 to the client 240 in response to the service request contain the fail reason frame field 325. Thereby, the client 240 receiving the response messages 330 and 340 for the service request may recognize the reason for failure of the service request. For example, the client 240 may recognize that a response to the service request has not been received for the reason that the processing time of the server 250 is longer than the timeout time of the client 240 rather than for the reason of a communication error, by analyzing the messages.
  • Fig. 6 illustrates configuration of client-server communication in a 3 Tier architecture in an electric power system according to an embodiment of the present invention.
  • According to an embodiment, the electric power system 400 may include a client 240, a communication apparatus 200 and a server 250.
  • The client 240 transmits a service request to the communication apparatus 200, and receives a response to the service request processed by the server 250 via the communication apparatus 200.
  • The communication apparatus 200 may relay the service request received from the client 240 to the server 250, and relay, to the client 240, the response to the service request received from the server 250.
  • In this case, the communication apparatus 200 may compare a timeout time for which the client 240 waits for the response to the service request with a processing time for which the server 250 processes the service request. If the processing time is longer than the timeout time, the communication apparatus 200 may announce to the client 240 that the processing time is longer than the timeout time.
  • The server 250 may process the service request received from the communication apparatus 200, and transmit a response to the service request to the communication apparatus 200.
  • The electric power system 400 described above may perform client-server communication in the 3 Tier architecture.
  • The client-server communication model of the 3 Tier architecture is proposed to address an issue raised in the client-server communication model of the 2 Tier architecture, which maintains a one-to-one service relationship between the client and the server.
  • The 3 Tier architecture has a middle tier dedicated to application processing, and the client request all services to the middle tier. The middle tier communicates with a final server such as a database server, and then delivers a result of communication to the client.
  • Specifically, the client-server communication model of the 3 Tier architecture is configured as follows.
    • Tier 1 is a client responsible for a user interface. Tier 1 is also called a requester.
    • Tier 2 is an application processing server. Tier 2 corresponds to a broker.
    • Tier 3 is a server such as a database server that performs a final function. Tier 3 corresponds to a replier.
  • The 3 Tier architecture is advantageous in terms of service scalability, stability and efficiency, and is thus suitable for a high-capacity service. In addition, a request from the client is not directly delivered to the server in the 3 Tier architecture. Accordingly, load to the server does not increase in proportion to the number of clients.
  • In Fig. 6, the client 240 is a requester corresponding to Tier 1. The communication apparatus 200 is a broker corresponding to Tier 2, the server 250 is a replier corresponding to Tier 3.
  • According to this embodiment, an observation function is added to the broker 200. Thereafter, if the data processing time of the replier 250 is longer than the timeout time of the requester 240, the broker 200 announces to the requester 240 that the data processing time is longer than the timeout time.
  • If there is no response to a request from the requester 240 within the timeout time, this may be because there is a problem with a router or application, or the processing time is long in the replier 250. In the former case, the requester 240 needs to send the service request again. In the latter case, on the other hand, the response to the request has failed not because a problem has occurred but because the data processing time of the replier 250 is longer than the timeout time of the requester 240 registered in the broker 200. Accordingly, the broker 200 announces the reason to the user through a log file or message.
  • To this end, communication is performed between the requester 240, broker 200 and replier 250 according to a procedure described below.
  • When transmitting a message for a service request, the requester 240 delivers a timeout time to the broker 200 through the message.
  • The broker 200 is provided with a Thread having a separate observation function. Thereby, the broker 200 stores the timeout time of the requester 240 as stored in the requester 240, and then relays a received message to the replier 250.
  • The replier 250 measures the data processing time from the moment at which the replier 250 receives the message, and sends a response message containing a frame field for the data processing time to the broker 200.
  • The replier 250 measures the data processing time from the moment at which the replier 250 receives the message. The timeout time of the requester 240 is counted from the time at which a data request is made, and thus the processing time is not synchronized with the start time of the timeout time. Accordingly, to allow the broker 200 to compare the data processing time with the timeout time, the replier 250 adds the duration from the time at which the requester 240 makes a request to the time at which the request is delivered to the replier 250 to the data processing time of the replier 250, and then transmit the data processing time to the broker 200.
  • The broker 200 compares the data processing time in the message received from the replier 250 with the registered timeout time of the requester 250 which is to be transmitted. If the timeout time is shorter than the data processing time, the broker 200 announces a reason for transmission failure to the user through a log file or message.
  • Failure of response to the service request may occur for various reasons. According to this embodiment, if a response is not issued for the waiting time of the requester 240 simply because the data processing time of the replier 250 is long, this information may be presented and a solution may be proposed.
  • Fig. 7 illustrates a procedure of communication among a communication apparatus, a client and a server in an electric power system according to an embodiment of the present invention.
  • When the client 240 makes a service request, the client 240 adds a timeout frame field to a service request message (S501).
  • The client 240 transmits the service request message containing the timeout frame field to the communication apparatus 200 to make a service request to the communication apparatus 200 (S502).
  • Upon receiving the service request from the client and 240, the communication apparatus 200 relays the service request to the server 250 (S503)
  • The server 250 processes the service request of the client 240 (S504).
  • After processing the service request, the server 250 adds a data processing time frame field to a response message for the service request (S505). To this end, the server 250 measures the data processing time from the moment at which the server 250 receives the service request. Then, the server 250 adds a frame field for the data processing time to a response message for the request and sends the response message to the communication apparatus 200.
  • The server 250 transmits a response to the service request to the communication apparatus 200 (S506).
  • In this case, the communication apparatus 200 determines whether the timeout time is shorter than the data processing time. If the timeout time is shorter than the data processing time, the communication apparatus 200 adds an alarm field indicating this information to the response message for the service request (S507).
  • The communication apparatus 200 relays the response to the service request to the client 240 (S508).
  • Fig. 8 illustrates a procedure of communication of a communication apparatus in an electric power system according to an embodiment of the present invention.
  • The communication apparatus 200 receives a service request from the client 240 and relays the same to the server 250 (S601).
  • In response to the service request, the communication apparatus 200 receives a response to the service request from the server 250 (S602).
  • The communication apparatus 200 compares the timeout time for which the client 240 waits for the response to the service request with a processing time for which the server 250 processes the service request (S603).
  • Upon determining that the processing time is longer than the timeout time (S604-Yes), the communication apparatus 200 delivers the response to the service request to the client 240, announcing that the processing time is longer than the timeout time (S605).
  • According to an embodiment, the communication apparatus 200 may transmit, to the client 240, a message indicating that the processing time is longer than the timeout time.
  • According to an embodiment, the communication apparatus 200 may generate a log file in which information indicating that the processing time is longer than the timeout time is recorded.
  • On the other end, upon determining that the processing time is shorter than or equal to the timeout time (S604-No), the communication apparatus 200 may relay the response to the service request to the client 240, announcing that processing of the service request has failed (S606).
  • Thereby, the client 240 may distinguish between a case where the response to the service request fails to be received because the processing time is longer than the timeout time and a case where processing of the service request fails because there is a problem with a router or application. Further the client 240 may take a proper action according to each situation.
  • According to embodiments of the present invention, when a data processing time of the replier is longer than a timeout time set by the requester in the 3 Tier architecture of Requester-Broker-Replier, the broker compares the times and announces, to the user, a reason for failing to send a response to the request to the requester through a log file or message. Thereby, the time taken to analyze the cause may be reduced.
  • Exemplary embodiments of the present invention have been described in detail with reference to the accompanying drawings. However, the present invention is not limited to the exemplary embodiments, and modifications and variations can be made thereto without departing from the technical idea of the present invention. For example, specific constituents disclosed in the embodiments of the present invention may be changed. It should be understood that such changes and related applications are within the scope of the present invention defined by the accompanying claims.

Claims (5)

  1. An electric power control system (400) comprising:
    a communication apparatus (200);
    a server (250) operative to process a service request received from the communication apparatus (200) and transmit a response to the service request to the communication apparatus (200); and
    a client (240) operative to transmit the service request to the communication apparatus (200) and receive the response to the service request processed by the server (250) via the communication apparatus (200),
    wherein the communication apparatus (200) comprises:
    a communication unit (210) operative to communicate with the client (240) and server (250) included in the electric power system (400) to relay the service request received from the client (240) to the server (250) and relay the response to the service request received from the server (250) to the client (240);
    a comparison/determination unit (220) operative to compare a timeout time taken for the client (240) to wait for the response to the service request with a processing time taken for the server (250) to process the service request; and
    a controller (230) operative to control the communication unit (210) and the comparison/determination unit (220) and to announce to the client (240) that the processing time is longer than the timeout time when the processing time is longer than the timeout time.
  2. The electric power system according claim 1, wherein the service request contains a frame field for the timeout time,
    wherein the response to the service request contains a frame field for the processing time.
  3. The electric power system according claim 1, wherein the controller (230) controls the communication unit (210) to transmit, to the client (240), a message containing a frame field indicating that the processing time is longer than the timeout time.
  4. The electric power system according claim 1, wherein the controller (230) generates a log file for recording content indicating that the processing time is longer than the timeout time.
  5. The electric power system according claim 1, wherein the comparison/determination unit (220) determines a delay time of the response to the service request from the timeout time by comparing the timeout time with the processing time,
    wherein the controller (230) controls the communication unit (210) to transmit, to the client (240), a message for instructing adjustment of the timeout time based on the delay time.
EP16193035.9A 2016-02-26 2016-10-10 Electric power system Not-in-force EP3211861B1 (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR1020160023695A KR102476831B1 (en) 2016-02-26 2016-02-26 Communication apparatus in electric power system and communicating method of thereof

Publications (2)

Publication Number Publication Date
EP3211861A1 true EP3211861A1 (en) 2017-08-30
EP3211861B1 EP3211861B1 (en) 2018-12-26

Family

ID=57460301

Family Applications (1)

Application Number Title Priority Date Filing Date
EP16193035.9A Not-in-force EP3211861B1 (en) 2016-02-26 2016-10-10 Electric power system

Country Status (5)

Country Link
US (1) US10310533B2 (en)
EP (1) EP3211861B1 (en)
KR (1) KR102476831B1 (en)
CN (1) CN107135245B (en)
ES (1) ES2710806T3 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110324250A (en) * 2018-03-29 2019-10-11 阿里巴巴集团控股有限公司 Information push method, equipment and system

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH08249261A (en) 1995-03-08 1996-09-27 Mitsubishi Electric Corp Message management system
KR100608590B1 (en) * 2003-09-16 2006-08-03 삼성전자주식회사 Network device to enable the service support according to quality of service, network system and method using this
JP2007058477A (en) * 2005-08-24 2007-03-08 Hitachi Ltd Data communication system and data communication method
CN101202446A (en) * 2007-06-25 2008-06-18 耿华 Method and system for delayed processing active electric power filter
US8924961B2 (en) 2008-10-29 2014-12-30 Dell Products L.P. Virtual machine scheduling methods and systems
CN101697551A (en) * 2009-11-05 2010-04-21 华北电力大学(保定) Networked power telecontrol communication method
US8576698B2 (en) * 2009-12-10 2013-11-05 Alcatel Lucent Connectivity fault management timeout period control
CN101951327B (en) * 2010-07-02 2014-04-30 中兴通讯股份有限公司 iSCSI network system and network fault detection method
KR101375133B1 (en) 2013-03-21 2014-03-17 주식회사 퓨전소프트 Mobile sns intergrated gateway
US9135454B2 (en) 2013-05-31 2015-09-15 Alcatel Lucent Systems and methods for enabling searchable encryption

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Industrial networks - Wireless communication network and communication profiles - WirelessHART", IEC 62591:2016, IEC, 3, RUE DE VAREMBÉ, PO BOX 131, CH-1211 GENEVA 20, SWITZERLAND, 30 January 2016 (2016-01-30), pages 1 - 1043, XP082002766 *

Also Published As

Publication number Publication date
US20170248982A1 (en) 2017-08-31
US10310533B2 (en) 2019-06-04
ES2710806T3 (en) 2019-04-26
CN107135245A (en) 2017-09-05
CN107135245B (en) 2020-05-08
KR20170101029A (en) 2017-09-05
EP3211861B1 (en) 2018-12-26
KR102476831B1 (en) 2022-12-13

Similar Documents

Publication Publication Date Title
CN110012083B (en) Data transmission method, server and data transmission device
CN101317407B (en) Method and system for delivering messages in a communication system
EP2599271B1 (en) Instant messaging using multiple instances of a client
CN110049134B (en) Customer service chat method, customer service chat device, customer service end, server and storage medium
EP3160172A1 (en) Method and device for short messaging service intercommunication
CN111917562B (en) Broadcast message forwarding method, device, equipment and storage medium
CN102387028A (en) Network system, network management server, and OAM test method
CN104539510B (en) A kind of information transmission system and method based on multi-protocols
CN111431790B (en) Instant messaging method, device, system and storage medium
JP4633842B2 (en) Notification system and method using messenger
EP3211861B1 (en) Electric power system
US10536401B2 (en) Communication device, communication system and communication method
CN111741006B (en) Discrete acquisition gateway and implementation method thereof
EP3171565B1 (en) Methods, devices and system for netconf hello packets interaction
CN106961475B (en) Remote disk sharing method and sharing system based on NBD
JP2012015629A (en) Application monitoring method of communication system
EP3232646A1 (en) Apparatus for relaying data transmission in scada system
CN109921933B (en) Information processing method and network security equipment
CN110661697A (en) Message synchronization method, device, readable storage medium, electronic device and system
CN113204440B (en) Message sending method, device, electronic equipment and storage medium
KR20170086933A (en) Publisher and subscriber in electric power system
CN108270814A (en) A kind of method of data synchronization and device
JP2009290605A (en) Relay device, relay method and monitor
KR101511338B1 (en) Device for aggregating data, device for managing data and system for aggregating data
US20130188636A1 (en) Communication terminal and communication method

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

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN PUBLISHED

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20170925

RBV Designated contracting states (corrected)

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20180124

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20180626

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAJ Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR1

GRAL Information related to payment of fee for publishing/printing deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR3

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

GRAR Information related to intention to grant a patent recorded

Free format text: ORIGINAL CODE: EPIDOSNIGR71

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

INTC Intention to grant announced (deleted)
INTG Intention to grant announced

Effective date: 20181114

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

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

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1082996

Country of ref document: AT

Kind code of ref document: T

Effective date: 20190115

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602016008648

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: ES

Ref legal event code: FG2A

Ref document number: 2710806

Country of ref document: ES

Kind code of ref document: T3

Effective date: 20190426

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

Ref country code: NO

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

Ref country code: LT

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

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

Ref country code: LV

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

Ref country code: HR

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

Ref country code: BG

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

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20181226

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

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

Ref country code: AL

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

Ref country code: SE

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

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

Ref country code: RS

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

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1082996

Country of ref document: AT

Kind code of ref document: T

Effective date: 20181226

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

Ref country code: NL

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

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

Ref country code: PL

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

Ref country code: CZ

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

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

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

Ref country code: EE

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

Ref country code: SM

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

Ref country code: SK

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

Ref country code: RO

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

Ref country code: IS

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

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602016008648

Country of ref document: DE

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

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

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

Ref country code: FR

Payment date: 20190906

Year of fee payment: 4

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

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

Ref country code: DE

Payment date: 20190905

Year of fee payment: 4

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

Ref country code: SI

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

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

Ref country code: ES

Payment date: 20191105

Year of fee payment: 4

Ref country code: IT

Payment date: 20191031

Year of fee payment: 4

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

Ref country code: TR

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

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 FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181226

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

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

Ref country code: CH

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

Effective date: 20191031

Ref country code: LU

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

Effective date: 20191010

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20191031

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 NON-PAYMENT OF DUE FEES

Effective date: 20191031

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

Ref country code: IE

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

Effective date: 20191010

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602016008648

Country of ref document: DE

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

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

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20201010

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

Ref country code: FR

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

Effective date: 20201031

Ref country code: HU

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

Effective date: 20161010

Ref country code: DE

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

Effective date: 20210501

Ref country code: MT

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

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 NON-PAYMENT OF DUE FEES

Effective date: 20201010

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

Ref country code: IT

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

Effective date: 20201010

REG Reference to a national code

Ref country code: ES

Ref legal event code: FD2A

Effective date: 20220120

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 NON-PAYMENT OF DUE FEES

Effective date: 20201011

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

Ref country code: MK

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