WO2007026095A1

WO2007026095A1 - Event supervision device and method

Info

Publication number: WO2007026095A1
Application number: PCT/FR2006/050815
Authority: WO
Inventors: Ivan Lovric; Christophe Tourneret
Original assignee: France Telecom
Priority date: 2005-08-29
Filing date: 2006-08-28
Publication date: 2007-03-08

Abstract

The invention relates to an event supervision device and method. The proxy device (100) can be placed in cut-through configuration between a client device (60) and a server device (50) in a telecommunications network. The inventive device comprises: means for establishing a socket (S13-60:1) with the client device (60) and a socket (S50:1-7) with the server device (50); means for interconnecting said sockets (S13-60:1, S50:1-7) such as to establish a channel (C50-60) for the communication of data packets in the network between the client device (60) and the server device (50); means for detecting at least one first event (EV1) contained in a data packet received on one of the sockets (S50:1-7); and means for sending at least one data packet comprising at least one second event (EV2), which is obtained from the first event (EV1), to at least one other socket (S13-60:1). The invention also relates to the use of said device in a computer telephony integration application.

Description

Device and method for event supervision

Background of the invention

The invention relates to a method for monitoring events transmitted by a server device to a client device in a telecommunication network, and a proxy device (or event relay) for implementing this method.

The invention applies in a preferred but nonlimiting manner, to supervise events transmitted by a PABX (switch) to bands. This supervision method can be achieved using a proxy or event relay adapted for computer telephony coupling.

At present, PBXs transmit and receive events to manage all telephony parameters (queues, phones, users, ...). CTI (Telephony-Computing Coupling) software is capable of generating events from a PABX or receiving them. This software is able to analyze the telephone events so that the user can have an interaction of these events with his computer. Conversely, an action on the computer will also have an action on the PABX via CTI software.

For example: a customer calls a green number to which the PABX is connected. The customer's call is first transferred to a queue that plays a voice message "please wait, you will be put in touch with an advisor". The call is then transferred to one of the call center of the board, which has the effect of ringing his phone. At the same time, the CTI software finds that the counselor's phone is ringing and that the calling customer's number is 0123456789. The software (otherwise known as the banner) then instructs the call center's computer to display the customer record corresponding to the number 0123456789, which has the effect of displaying a certain amount of information on the screen that will be useful to the call center to interact with the customer. It can be seen that the development of CTI banners represents a costly investment for companies that do not support changes in technical architectures or functional changes. The invention consists of an event proxy that can be placed in the technical and functional architecture to capture and modify the CTI events in order to avoid carrying out additional developments on the strips.

CTI's current architectures are client-server architectures and three-tier architectures.

In client-server architecture, there are currently two types of bands for the CTI:

- proprietary CTI headbands sold by equipment manufacturers manufacturing PABX, and

- CTI banners sold by CTI specialists who can operate with different PBXs.

FIG. 1A diagrammatically shows a CTI environment, in client-server architecture, in which:

the server is a switch 10; and

- the customer is a proprietary CTI 20 banner sold by the manufacturer of the PABX 10.

The dotted and referenced frame 5 represents the office of the call center on which there is a computer not shown which includes the banner CTI 20 and telephone 2 of the call center.

In the case of proprietary CTI headbands, these headbands installed in the remote advisor's computer can be customized (adapted) to match the needs of the company having purchased the CTI software suite from the equipment manufacturer.

Fig. 1B shows a CTI environment in which the CTI banner 20 can operate with different PBXs.

In the case of the CTI headband sold by the CTI specialist, these head bands can be customized to match the needs of the company that purchased the CTI specialist CTI software suite.

In this figure, there is referenced 11 a CTI specialist event translator, placed between the PABX 10 and the strip 20.

In three-tier architecture, there are also two types of CTI software headers: - proprietary CTI headbands sold by equipment manufacturers manufacturing PABX,

- CTI banners sold by CTI specialists who can operate with different PBXs.

In the case of proprietary headbands, these headbands installed in an application server can be customized (adapted) to match the needs of the company that purchased the CTI software suite from the OEM.

Such a CTI environment is not shown in the figures. It is very similar to the environment of Figure IA, with the difference that the CTI banner is not installed in the remote controller computer, but in an application server that can be accessed by a browser installed on the computer of the call center.

In the case of headbands sold by CTI specialists, these headbands can be customized to match the needs of the company that purchased the CTI specialist CTT software suite.

This CTI environment is not shown in the figures. It is similar to the CTI environment of Figure IB, with the difference that the CTI banner is not installed in the remote controller computer, but in an application server that can be accessed by a browser installed in the computer of the telephone advisor.

In FIG. 1C, there is shown another current architecture of client-server CTI in which:

the server 30 is constituted by a gatekeeper; and

client 40 a voice over IP gateway.

The voice over IP gateway 40 allows communication between voice over IP terminals 4, of the local network 3, to access terminals of the public network 1.

In this example, the gatekeeper 30 and the gateway 40 communicate through a common protocol. This communication protocol may be in accordance with the H225 protocol.

It is recalled that the H225 standard is a sub-standard of the H323 standard defined by I ¹ ITU-T, the H323 standard describing a set of protocols used in packet multimedia data transmission and in particular for the voice of the IP. Specifically, the H225 sub-standard allows the management of calls, namely the establishment and control and termination of type H323 calls. It is based on the User Datagram Protocol (UDP) as detailed in RFC 768 (Request For Comment).

Gatekeeper 50 and voice over IP gateway 60 may also conform to the H245 sub-standard and communicate according to the Transmission Control Protocol (TCP).

It is recalled that the H245 sub-standard, defined by the H323 standard, offers a control channel used for the negotiation of the common codecs and for the management of the media streams.

In the prior art, the heavy developments made to customize the bands in both client-server architecture and three-thirds are not very scalable. Any functional evolution, technical (change of PABX, see the simple installation of a patch on the PABX) makes inevitable the redevelopment of the bands, which induces a high cost in software often prohibitive for the companies. Sometimes, the redevelopment of the banners is impossible following the departure of the people having developed these bands.

For example, it is impossible to operate the custom CTI banner for Alpha with PABX Beta. Indeed, the events sent by the PABX differ depending on the brand, both in terms of the names of certain events and certain parameters.

An example of a functional change that can not be redeveloped is to go from free mode to reservation mode during an outbound call. In free mode, a controller generates calls to clients without verifying that agents are available, which causes clients to hang up if the controller has failed to connect them to a call center. In reservation mode, the controller initiates a call to an agent to reserve it before making an outgoing call to a client. Thus, if a customer picks up, the transfer to the reserved televisor will be guaranteed. Such a functional evolution necessarily requires a modification of the banner.

The present invention makes it possible to overcome or, at the very least, to reduce these disadvantages, in particular to preserve the developments already made on CTI banners while giving the company the opportunity to evolve its functional or technical architecture.

Obiet and summary of the invention

According to a first aspect, the invention relates to a proxy device that can be placed in flux cutoff between at least one client device and at least one server device in a telecommunications network.

This device comprises:

means for establishing a socket with the client device;

means for establishing a socket with the server device;

means for interconnecting these sockets so as to establish a network-level data packet communication channel between the client device and the server device,

means for detecting at least a first event included in a data packet received on one of said sockets; and

means for sending at least one data packet comprising at least one second event, obtained from the first event, in at least one other of said sockets.

Correlatively, the invention relates to a method for monitoring events transmitted by a server device to a client device in a telecommunications network.

This process comprises:

a step of establishing a socket between the client device and a proxy device placed between the client device and the server;

a step of establishing a socket between the proxy device and the server device;

a step of interconnecting the sockets so as to establish a communication channel of data packets at the network level between the client device and the server device,

a step of detecting at least one first event included in a data packet received on one of the sockets; and

a step of sending at least one data packet comprising at least one second event, obtained from the first event, in at least one other of the sockets.

The proxy device serves as an interface between the client device and the server device, so as to adapt the flow between the two devices and make them interoperable by modifying the messages of the communication protocols.

In the context of the invention, a "communication channel" is also called "tunnel".

The term "proxy" is a general term used in computer science to designate a service that automatically replaces or competes with another. English translates as "proxy", "delegate", which gives the idea. It is within the scope of the invention a software element that will automatically add a function to a service and in a completely transparent manner for its user. It works automatically, by interception of data, and it is impossible to circumvent it. For the adjective event: the program is on standby, waiting for external stimuli, to which it reacts. It is therefore the program that reacts to the interactions between the PBX and the telephone banner. Therefore, the event proxy is a program product placed in the architecture to capture and modify the CTI events that pass between the PABX and the banner.

The event proxy according to the invention can be placed between the banner and the PABX or between the banner and the event translator. It is capable of capturing and modifying events on the fly, so that operation compatible with existing bands is preserved despite a change in technical or functional architecture.

Moreover, the invention also solves the problems of interoperability between applications and hardware by adapting and modifying the messages of the communication protocols.

In client-server architecture, the event proxy can be placed in different places depending on whether it is an OEM or CTI specialist banner.

In the case of the proprietary CTI strips sold by the manufacturers manufacturing the PABXs, the proxy is inserted between the PABX and the CTI banner.

In the case of CTI banners sold by CTI specialists, the proxy can be inserted between the event translator and the CTI banner or between the PABX and the event translator. In three-tier architecture, the event proxy can be placed in different locations depending on whether it is an OEM or CTI specialist banner.

In the case of proprietary CTI strips sold by the equipment manufacturers, the event proxy can be intercalated between the PABX and the application server.

In the case of CTI banners sold by CTI specialists, the event proxy can be interposed between the PABX and the event translator.

The event proxy can thus be interposed between the event translator and the application server.

The invention can be implemented in outbound call centers to enable national campaigns where previously only local campaigns were possible due to restrictions of existing applications.

In this context of use, the event proxy operates simultaneously in several modes mentioned above (CTI banner sold by CTI specialists in client-server architecture and in three-thirds). This is due to the fact that two applications of the information system (PROCAP and RFORCE) with two separate bands appear simultaneously on the computer of the call center.

The event proxy is set up with two internal tunnels inserted between each of the CTI (Tserver Gamma) specialist event translators and each of the CTI bands.

In a particular embodiment, the proxy device according to the invention comprises means for interconnecting two established sockets with two client devices so as to establish a data packet communication channel at the network level between these client devices;

means for detecting at least one first event included in a data packet received on one of the sockets; and

means for sending at least one data packet comprising at least one second event, obtained from the first event, in the other of the sockets.

This particular embodiment makes it possible in particular to establish a communication channel between two CTI bands. So, when a first CTI header sends a disconnect event to the proxy event, it sends the event "disconnection in progress" to the second banner that displays this message on the screen.

In a particular embodiment, the proxy device according to the invention comprises means for storing an event with a view to its subsequent processing.

In a particular embodiment, the supervision method according to the invention comprises:

a step of determining at least one treatment to bring to said first event; and depending on the result of the determining step:

a step of performing the treatment; or

a step of transferring the received data packet to the recipient of this packet.

Its role is to capture and modify if necessary the CTI events for each of the tunnels.

In a particular embodiment, the various steps of the supervision method are determined by instructions of computer programs.

Consequently, the invention also relates to a computer program on an information medium, this program being capable of being implemented in a computer, this program comprising instructions adapted to the implementation of the steps of a suspension method as described above.

This program can use any programming language, and be in the form of source code, object code, or intermediate code between source code and object code, such as in a partially compiled form, or in any other form desirable shape.

The invention also relates to a computer-readable information medium, comprising instructions of a computer program as mentioned above.

The information carrier may be any entity or device capable of storing the program. For example, the medium may comprise storage means, such as a ROM, for example a CD ROM or a microelectronic circuit ROM, or a means magnetic recording, for example a floppy disk or a hard disk.

On the other hand, the information medium may be a transmissible medium such as an electrical or optical signal, which may be conveyed via an electrical or optical cable, by radio or by other means. The program according to the invention can be downloaded in particular on an Internet-type network

Alternatively, the information carrier may be an integrated circuit in which the program is incorporated, the circuit being adapted to execute or to be used in the execution of the method in question.

Brief description of the drawings

Other features and advantages of the present invention will emerge from the description given below, with reference to the accompanying drawings which illustrate an embodiment having no limiting character. In the figures:

FIGS. 1A to 1C represent CTI environments known from the prior art;

FIG. 2 represents a proxy device according to the invention in a particular embodiment; and

FIG. 3 represents, in flowchart form, the main steps of a supervision method according to the invention in a particular embodiment.

Figure 2 schematically shows a supervision device 100 according to the invention.

The proxy device 100 can be implemented from a system or a terminal of a different nature, allowing the implementation of the steps of the method according to the invention.

In the example described here, this proxy device has the hardware architecture of a conventional computer.

It comprises in particular a processor 101, a read-only memory 102 of the ROM type, a random access memory 103 of the RAM type and a hard disk 106.

ROM type ROM is a recording medium on which a computer program is recorded according to the invention, this computer program comprising instructions for implementing the supervision method whose flowchart is given in FIG.

In the exemplary embodiment described here, the proxy device 100 comprises sixteen ports referenced 1 to 16.

It also comprises communication means 104 which enable it to send and receive data on each of the ports 1 to 16.

For this purpose, the communication means 104 comprise a set of pins pi pi ₆ , each of these pins being connected to a port 1 to 16.

For the sake of clarity, the links between the p-pins and the ports of the proxy device 100 are not shown in FIG.

The proxy device 100 serves as an interface between at least one client device and at least one server device. The proxy device 100 can be placed between two applications or two devices that communicate with each other by messages. The client device 60 and the server device 30 may be of different types, for example a computer telephone coupling strip, a voice over IP gateway, a switch, an event translator, a gatekeeper, etc.

In the example described here, we will assume that the proxy device 100 is placed in flux cutoff between:

a client, referenced 60, constituted by a voice over IP gateway adapted to communicate in accordance with the H245 protocol in TCP; and

a server, referenced 30, constituted by a gatekeeper adapted to implement the H225 protocol.

The proxy device according to the invention allows interoperability between these two devices. Specifically, it performs the following functions;

adapt the length of the UDP packets sent by the server 30;

- modify the content of the H323 set up event to prepare the H245 session;

- Remove the message "PROGRESS" sent to the client 60, the receipt of this message generating, if its format is not correct, a break in the IP dial-up call. Following these operations of readjusting the H323 negotiation by the proxy device 100 according to the invention, the establishment of the telephone calls by the gatekeeper 30, controlled by the voice over IP gateway 60, is carried out without having recourse to code changes or re-settings of this equipment.

According to the invention, the proxy device 100 comprises means for establishing, during a step E5, sockets with the voice over IP gateway 60.

A socket can be defined as a communication socket that allows the combination of a client address and a port number to establish a connection between a client and a server.

We will use the following notation: S _p iN: p2 socket established from the port pi of the proxy device 100 to the port p2 of the entity N; SN: _P 2- _P I socket established from the port p2 of the entity N to the port pi of the proxy device 100; and CNI-N2 channel from the N entity to the N2 entity.

In the example described here, the proxy device 100 establishes;

a first socket Si ₃ -60: i between the port 13 of the proxy device 100 and a port 1 of the gateway 60; and

a socket S _{60: 2} -i ₄ between a port 2 of the gateway 60 and the port 14 of the proxy device 100.

The proxy device 100 also comprises means for establishing, during this same step E5, sockets with the gatekeeper 30. In the embodiment described here, it establishes:

an S ₃ o _: i-7 socket between a port 1 of the gatekeeper 30 and the port 7 of the proxy device 100; and

an Ss- ₃ o: 2 socket between the port 8 of the proxy device 100 and a port 2 of the gatekeeper 30.

The proxy device 100 according to the invention is adapted to interconnect sockets.

In the example described here, it is considered that the proxy device 100 interconnects, during this same step E5, the socket S ₃₀ : i- ₇ and the socket Si ₃ -60: i to establish a packet communication channel. data at the network level between the gatekeeper 30 and the voice over IP gateway 60, gateway 30 to gateway 60. This channel is referenced C3 ₀ - ₆₀ in FIG.

Similarly, the proxy device 100 establishes a second communication channel C _{_60-30} between the gatekeeper 30 and gateway VoIP gateway 60 in the direction 60 to 30 doorman.

This socket and channel establishment step E5 is followed by an ElO step during which the proxy device 30 seeks to detect events received on one of its sockets.

In the exemplary embodiment described here, the events detected by the proxy device 100 are previously specified in a configuration file 105 stored in the hard disk 106.

In the exemplary embodiment described here, when an event is detected, the proxy device 100 according to the invention implements a step E20 for analyzing a code of the event.

Then, during a step E30, the proxy device 100 decides, depending on the configuration file 105, whether this event should be processed or not.

If the event is not to be processed, the data packet received at step ElO is transferred, in a step E40, to its recipient.

If the event is to be processed, the result of the test E30 is positive and this test is followed by a step E50 during which the proxy device 100 according to the invention chooses the treatment to be performed.

In the embodiment described here, several treatments are possible.

For example, during a step E62, an event may be stored in an event file 107 on the hard disk 106 for further processing.

For example, following the installation of a new interactive voice server, the ANI field of the EventRinging event is changed. This field contains the number of the IVR instead of the customer number, which leads to an erroneous data report.

The proxy device 100 of the invention stores the EventRinging event while waiting to receive the EventAttachedDataChanged event that contains the caller's number. It then replaces the caller's number in the EventRinging event stored in the event file 107 before transmitting it to the banner which then makes the correct file.

The processing chosen in step E50 may also be a deletion, in which case a deletion step E64 is implemented.

For example, installing a new version of the PABX software generates an EventPartyChanged event on every incoming call that a CTI header can not interpret. The event proxy according to the invention suppresses this event so that no error message appears on the banner.

During the step E50, the processing choice can also be to modify this event, in which case a modification step E66 is implemented.

For example, changing a switch affects the information that is passed when a client makes a hidden call. The ANI field is blank, whereas it was previously set to "0000000000". The event proxy 100 according to the invention replaces the blank with "0000000000" so that the operation of the CTI strip remains correct.

In the embodiment described here, the proxy only modifies the events that could not be properly interpreted by the banner and, therefore, that would not allow a correct operation of the banner (for reminder, the code of the banner is not not touched thanks to the event proxy). Example when booking an agent, the event "Event-Ringing" does not contain the phone number of the customer but the name of the T-Server, which is of no use for the call center. It is necessary to modify this event by including the phone number of the customer as soon as it is online, so that the customer records go back in Rforce and Procap.

The modification can be carried out by a program (for example Java) which works at the level of the frames, according to a predetermined method, in particular the key / value method. For example, change the value of the key "GSW_PHONE".

The processing chosen in step E50 may also consist of transferring the detected event at step E10 into a data packet to another entity (client or server). In the preferred embodiment described here, it is then tested, during a step E70, whether another treatment is to be performed.

An example of how the event proxy works during the agent reservation is as follows: in a first step, the proxy will check that the frame contains a single event. If it does not, it splits the frame into elementary events.

When the callback reservation call is issued by the system, the proxy receives two events: "EventRinging" and "EventEstablished" in the Rforce and Procap tunnels. At this level, the Rforce and Procap banners must not go back to the record, because we do not have an online client yet. These events are stored and deleted by the proxy. The Rforce and Procap banners have not seen the arrival of these two events blocked by the proxy. As a result, no form is uploaded when booking the agent. Customer records should appear on the call center screen only when a customer is online.

Thus, in general, if other treatments are to be performed, the E70 test is followed by step E50 already described, during which the new treatment to be performed.

If no further processing is to be performed, the E70 test is followed by an ElO step of detecting the next event received on one of the sockets.

The commented configuration file for this example of use of the invention is as follows:

##############################

# Event Proxy

# Authors Ivan Lovric, Christophe Tourneret

# Version of July 27, 2005

##############################

# Number of destination sites to 2 because we have 2 types of CTI headers to manage simultaneously

number of sites = 2 ##############################

# Type 0: application 0: CTI PROCAP banner

Type_0 = 0

##############################

# The CTI PROCAP header points to a 0 input of the event proxy listening on TCP port 6020

listen_port_0 = 6020

##############################

# After processing and editing events, messages are returned to the event translator

CTI specialist #: Tserver Gamma dedicated to Procap *

destination_host_0_ = 10.183.37.18 destination_port_0 = 6010

##############################

# TransferAgentProcap class inbound and outbound whose role is to modify events

# issued or received by the CTI Procap banner

transfer_class_in_0 = com.intermediary.socketproxy.handler. TransferAgentProcap transfer_class_out_0 = com.intermediary.socketproxy.handle r.TransferAgentProcap

##############################

# Maximum number of clients that can connect to this Event Proxy entry is at one

# because PROCAP works in three-tiers

NbMaxTunnels 0 = 1 ##############################

# Type 1: application 1: CTI header RFORCE Type_l = l

##############################

# The CTI RFORCE header points to an event proxy entry 1 that listens on TCP port 6500

listen_port_l = 6500

##############################

# of the CTI specialist: Tserver Gammé dedicated to RForce

destination_host_l = 10.183.37.16 destination_port_l = 6510

##############################

# Incoming and outgoing TransferAgentRFroce classes whose role is to modify events

# issued or received by CTI RForce banner

transfer_class_in_l = com.intermediary.socketproxy.handler. TransferAgentRForce transfer_class_out_l = com.intermediary.socketproxy.handle r.TransferAgentRForce

##############################

# Maximum number of clients that can connect to this event proxy entry is 800

# because RFORCE works as a client-server and 800 callers are likely to connect

# simultaneously NbMaxTunnels 1 = 800 In the usage example, interactions between applications are made possible by the event proxy. Thus, when the agent activates in RFORCE (READY mode), an "AgentReady" event is automatically passed to the PROCAP application to maintain consistency between the two applications even though the PROCAP and RFORCE CTIs do not use the same PBX.

In the exemplary embodiment described here, two communication channels C20-40 and C4 _0-2 _{0 are also established} between a CTI band 20 and a voice over IP gateway conforming to the protocol H225 in UDP.

These channels are established by interconnecting;

a socket S20: i- ₉ between a port 1 of the strip 20 and the port 9 of the proxy 100;

a socket Sn- ₄ : i established between the port 11 of the proxy 100 and a port 1 of the VoIP gateway 40; and

a socket Sio-2 _O : 2 between the port 10 of the proxy 100 and a port 2 of the strip 20 and a socket Si ₂ - ₄₀ : 2 between the port 12 of the proxy 100 and a port 2 of the voice-over-IP gateway 40.

According to the invention, the proxy device 100 is adapted to detect the events included in a data packet received on one of these sockets, and to determine, according to the event file 107, the processing to be performed on this EV event ₃ .

In particular, a processing may consist in sending a data packet comprising a second event in one of the sockets established with another client device.

In general, the proxy device 100 according to the invention implements the algorithm described in FIG. 3, as soon as it detects an event, whether it is received in a socket established with a server or in a server. socket established with a client.

As soon as an event is detected (step E10), the proxy device 100 according to the invention determines (step E30) whether or not to handle this event and, if it is the case, chooses the treatment to be performed (step E50) and performs this processing (steps E62, E64, E66 and E68).

If an event requires several treatments (determination of step E70), these different treatments are performed.

The proxy device 100 may therefore comprise a number X of different server devices and a number Z of client devices for each of these server devices. The server devices are defined to allow connections to client devices.

The means of the invention make it possible to establish at least one socket, compatible and independent of the communication protocol used. Sockets are also intercommunicating, that is, an event arriving on one socket may generate one or more events as input or output on other sockets, even in the case of different server devices.

Claims

A proxy device (100) which can be placed in a flow-off between at least one client device (60) and at least one server device (50) in a telecommunications network, the device comprising:

means for establishing a socket (Si ₃ - ₆ o: i) with said client device (60);

means for establishing a socket (S _50: i- ₇ ) with said server device (50);

- means for interconnecting said sockets (Si3-60: i, S _50: i-7) so as to establish a communication channel (C50-60) of data packets at the network layer between said client device (60) and said server device (50);

means for detecting at least one first event (EVi) included in a data packet received on one of said sockets (S _50: i-7); and

means for sending at least one data packet comprising at least one second event (EV ₂ ), obtained from said first event (EVi), in at least one other of said sockets (Si ₃ -60: i)

2. Proxy device (100) according to claim 1 characterized in that it comprises:

- means for interconnecting two sockets (S ₂ _o: ig, S12-40 .2) established with client devices (20, 40) so as to establish a communication channel (C _2O -4o) of data packets at network between these client devices (20, 40);

means for detecting at least one first event (EV ₃ ) included in a data packet received on one of said sockets (S20: i- ₉ ); and

means for sending at least one data packet comprising at least one second event (EV ₄ ), obtained from said first event (EV3), in the other of said sockets (Si ₂ -40: 2).

3. Proxy device according to claim 1 or 2, characterized in that it comprises means (106) for storing said first event (EVl) for subsequent processing.

A method for monitoring events transmitted by a server device to a client device in a telecommunications network, the method comprising:

a step (E5) for establishing a socket (Si ₃ - ₆₀ : i) between said client device (60) and a proxy device (100) placed between said client device (60) and said server (50);

a step (E5) of establishing a socket (S _50: i- ₇ ) between said proxy device (100) and said server device (50);

a step of interconnecting said sockets (Si ₃ - ₆₀ : i, S50 _: i-7) so as to establish a communication channel (C ₅₀ - ₆₀ ) of data packets at the network level between said client device (60) and said server device (50);

a step (ElO) of detecting at least one first event (EVi) included in a data packet received on one of said sockets (Ssoii _? ); and

a step (E68) of sending at least one data packet comprising at least one second event (EV ₂ ), obtained (E66) from said first event (EVi), in at least one other of said sockets (Si ₃ -

60: l) -

5. Supervision method according to claim 4, characterized in that it comprises:

a step (E30) of determining at least one treatment to be applied to said first event (EV1); and depending on the result of said determining step:

a step (E62, E64, E66, E68) of performing said processing; or

a step (E40) of transferring said received data packet to the recipient of this packet.

A computer program comprising instructions for performing the steps of the supervisory method according to claim 4 or 5 when said program is executed by a computer.

7. Computer-readable recording medium on which is recorded a computer program including instructions for carrying out the steps of the supervisory method according to claim 4 or 5.