FR3062543A1 - METHOD FOR UPDATING A BLACK REFERENCE LIST ASSOCIATED WITH AT LEAST ONE USER - Google Patents

Abstract

This method of updating a reference blacklist associated with at least one user, said method being able to be implemented by a device of a network, said method comprising: a reception step (E10), via said network, a first message comprising data representative of at least one identifier associated with at least one communication solution, said at least one identifier having been selected by said at least one user; and - a step (E40) of updating said reference blacklist from said data of said first message; said reference blacklist being used to filter any communication sent by a caller and to said at least one user if the caller ID is included in said reference blacklist.

Description

Holder (s):

ORANGE Limited company.

O Extension request (s):

® Agent (s): CABINET BEAU DE LOMENIE.

® METHOD FOR UPDATING A BLACK REFERENCE LIST ASSOCIATED WITH AT LEAST ONE USER.

FR 3 062 543 - A1 (57) This method for updating a reference black list associated with at least one user, said method being able to be implemented by equipment of a network, said method comprising:

a step (E10) of receiving, via said network, a first message comprising data representative of at least one identifier associated with at least one communication solution, said at least one identifier having been selected by said at least one user; and

- a step (E40) of updating said reference black list from said data of said first message;

said reference black list being used to filter any communication sent by a caller and intended for said at least one user if the identifier of the caller is included in said reference black list.

E10

E40

Invention background

The invention relates to the general field of telecommunications.

It relates more particularly to the field of filtering communications.

Currently, many communication solutions are offered to users: telephony, videoconferencing, SMS / MMS, electronic messaging, instant messaging, online social networks, solutions for sharing personal content (for example images), etc.

These solutions are used in different contexts and can be implemented by different types of terminals: phones, smartphones (smartphones), computers, tablets, etc.

Each of these communication solutions can be associated for a given terminal with a black list of identifiers managed by the user, such a list being used to filter any communication intended for this terminal and the caller's identifier of which is included in the blacklist.

When a user decides to block all communication from a contact on all his terminals, he must add all the identifiers of this contact in all the black lists associated with the communication solutions implemented by his various terminals, which can be long and tedious.

Subject and summary of the invention

The present invention responds in particular to this problem by proposing, according to a first aspect, a method for updating a reference black list associated with a user.

This method can be implemented by equipment of a communication network, called "central equipment". It comprises :

a step of receiving, via this network, a first message comprising data representative of identifiers associated with communication solutions, these identifiers having been selected by the user; and a step of updating the reference blacklist from the data of the first message;

the reference black list being used to filter any communication sent by a caller and intended for the user if the caller's identifier is included in the reference black list.

Correlatively, the invention also relates to equipment of a communication network, this equipment called "central equipment" comprising:

a module for receiving, via this network, a first message comprising data representative of identifiers associated with communication solutions, these identifiers having been selected by a user; and a module for updating the identifiers of a reference blacklist associated with the user from data from the first message;

the reference black list being used to filter any communication sent by a caller and intended for this user if the caller's identifier is included in the reference black list.

An identifier associated with a communication solution corresponds to an identifier used by a user to send or receive a communication via this communication solution.

For example, an identifier associated with a telephony solution corresponds to a telephone number.

The invention therefore relates to a method and equipment allowing a user to update only a single black list, called a reference list, to filter communications intended for a user.

This equipment is called "central equipment" in that it allows centralized management of a reference black list.

In a particular embodiment, the central equipment can consist of a server.

In this embodiment, this server can for example be part of a cloud network (“Cloud” in English) forming part of the general knowledge of a person skilled in the art of networks.

In a particular embodiment, the identifiers included in the reference black list are of at least two different types.

The identifiers included in the reference black list can for example be of the following types: telephone number, email addresses, identifier used on an online social network, etc.

Each type of identifier can be associated with one or more communication solutions.

For example, a telephone number can be associated with a telephony and / or messaging solution, for example of the SMS type, an email address can be associated with an electronic messaging solution or with a voice over IP solution, and a identifier used on an online social network can be associated with this online social network.

For the purposes of the invention, to say that the reference black list includes different types of identifiers is to say that this list is associated with different communication solutions, in other words that it can be used to filter compliant communications to these different communication solutions.

In a particular embodiment, the data representative of the identifiers and included in the first message includes these identifiers and the updating of the reference black list comprises:

adding one or more of these identifiers to the reference blacklist;

and / or a deletion of one or more of these identifiers from the reference black list.

In other words, the identifiers selected by the user and included in the first message can be added to or removed from the reference blacklist.

In a particular embodiment, the data representative of the identifiers and included in the first message includes information associated with these identifiers, and the updating of the reference black list comprises:

adding one or more of this information to the reference blacklist;

removal of one or more of these items from the reference blacklist.

The reference black list can indeed include, for each identifier that it contains, information or metadata associated with this identifier, for example a first name of a user using this identifier, a name of this user, a social network name online, etc.

This information can be added or deleted when updating the reference blacklist.

In a particular embodiment, the central equipment comprises:

a module for selecting one or more target list management devices, these devices being connected to the network and configured to manage one or more target black lists associated with the user; and a module for sending to this or these target list management devices via the network a second message comprising data representative of the reference black list;

this target list management equipment being selected if it comprises one or more devices which can access one or more target black lists associated with the user and being configured to update these target black lists from the data of the second message, each of these target black lists being used to filter any communication sent by a caller and intended for the user if the caller's identifier is included in the target black list.

Advantageously, the modifications made to the reference list during its updating can be passed on to one or more target black lists, such a target black list being used to filter communications intended for the user and whose caller is included in the target blacklist.

In a particular embodiment, the central equipment is a server and the target list management equipment are terminals allowing the user to access a service offered by this server.

The nature of the target list management equipment will be detailed later.

According to a second aspect, the invention also relates to a method for supervising the updating of a reference list.

This process can be implemented by equipment, and includes:

a step of detecting an event; and a step of selecting and sending to a device called "central equipment" selected, via a network and upon detection of the event, a first message comprising data representative of identifiers associated with communication solutions, these identifiers having been selected by a user, the central equipment being selected if it is configured to update, on reception of the first message, identifiers of a reference black list from the data of the first message, the black list is used to filter any communication sent by a caller to the user if the caller's identifier is included in the reference blacklist.

Correlatively, the invention also relates to equipment for supervising the updating of a reference list, comprising:

an event detection module; and a selection and sending module making it possible to send a first message comprising representative data of identifiers associated with communication solutions to a so-called “central equipment” device selected, via a network and upon detection of the event. , these identifiers having been selected by the user, the central equipment being selected if it is configured to update, on reception of the first message, identifiers of the reference black list from the data of the first message, the reference blacklist being used to filter any communication sent by a caller and intended for the user if the caller's identifier is included in the reference blacklist.

In a particular embodiment, this supervision equipment is a user terminal, and the identifiers whose representative data are included in the first message are selected by the user on this terminal.

For example, if the user wishes to add an identifier to the reference blacklist, he can enter this identifier on his terminal (this entry then corresponds to the selection of this identifier by the user), and this identifier will then be sent to the first message to be added to the reference blacklist.

In the case where the user's terminal has its own black list, the modifications made to the reference black list may possibly and as already described, be reflected in this black list. This black list is then a target black list within the meaning of the invention.

In a particular embodiment, the event corresponds to an action by the user associated with the selection of identifiers by this user.

For example, this event can correspond to the aforementioned entry.

In a particular embodiment:

the supervision equipment is a terminal;

the central equipment is a server offering a service; and the event corresponds to a request to register the terminal to access this service.

According to a third aspect, the invention relates to a target list management method.

This method can be implemented by target list management equipment, and comprises:

a step of reception, via a network, of a message ("second message within the meaning of the invention") sent by a piece of equipment from the network called "central equipment", this message comprising data representative of a reference black list associated with a user, this reference black list being used to filter any communication sent by a caller and intended for a user if the caller's identifier is included in the reference black list; and at least one step of accessing at least one target black list and updating this target black list from the data of this message, a target black list being used to filter any communication sent by a caller and to destination of the user if the caller ID is included in the target blacklist.

Correspondingly, the invention also relates to target list management equipment, comprising:

a module for receiving, via a network, a second message sent by a central equipment, this second message comprising data representative of a reference black list, this reference black list aimed at filtering communications associated with identifiers included in this reference blacklist and issued to a user; and devices capable of accessing target black lists and configured to update these target black lists from the data of the second message, the target black lists making it possible to filter communications associated with identifiers included in these target black lists and transmitted to user destination.

In a particular embodiment, the target list management equipment is a user terminal, and the target black lists make it possible to filter communications sent to this terminal.

Alternatively, the target list management equipment can be a gateway, for example a home gateway, or a server.

In a particular embodiment in which the target list management equipment is a gateway configured to manage a target black list, this gateway can be located in flow interruption between a calling terminal and a terminal of the user receiving this communication, this communication being filtered if the identifier of the calling terminal is included in this target black list.

In a particular embodiment, each of the devices of the target list management equipment:

- is associated with a communication solution;

is configured to access one of the target black lists, this target black list being associated with this communication solution; and is configured to access and update the target black list from data of the second message representative of the reference black list, this data being associated with the communication solution.

As a reminder, the second message includes data representative of the reference black list, for example identifiers included in this reference black list and possibly information associated with these identifiers.

In this embodiment, a device of the equipment manages a single target blacklist associated with a communication solution, and retrieves the data of the second message associated with this communication solution, for example the identifiers specific to this communication solution and information associated with it. The target blacklist is then an incomplete image of the reference blacklist.

The device can for example add or delete these identifiers in / from the target black list it manages, as well as the information associated with them.

For example, the device can manage a black list associated with a telephony solution and therefore comprising identifiers of the telephone number type, and recover in the second message the identifiers of this type as well as any information associated with them.

According to a fourth aspect, the invention relates to a system comprising:

supervisory equipment for updating a reference list as mentioned above, this equipment being configured to send a first message via a network to a central equipment, the supervision equipment, the first message and the 'central equipment being as defined above;

this central equipment, configured to send a second message via the network to at least one target list management equipment, this second message and this or these target list management equipment (s) being as defined above; and this or these target list management equipment (s).

In a particular embodiment, the different steps of the methods for updating a reference black list, for supervising the updating of a reference black list and for managing the target list are determined by instructions for computer programs.

Consequently, the invention also relates to computer programs on information carriers, these programs being capable of being implemented by a computer, these programs respectively comprising instructions adapted to the implementation of the three methods such as mentioned above.

These programs 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 desirable form.

The invention also relates to information supports readable by a computer, and respectively comprising instructions of computer programs as mentioned above.

Each of these information carriers can be any entity or device capable of storing the program. For example, each of these supports may include a storage means, such as a ROM, for example a CD ROM or a microelectronic circuit ROM, or also a magnetic recording means, for example a hard disk.

On the other hand, each of these information carriers can be a transmissible carrier such as an electrical or optical signal, which can be routed via an electrical or optical cable, by radio or by other means. The programs according to the invention can in particular be downloaded from a network of the Internet type.

Alternatively, each of these information carriers can be an integrated circuit in which the corresponding program is incorporated, the circuit being adapted to execute or to be used in the execution of the corresponding method.

Brief description of the figures

Other characteristics and advantages of the invention will appear on reading the following description, made with reference to the accompanying drawings in which:

Figures 1 shows a system according to the invention;

FIG. 2 represents a device for supervising the updating of a reference black list in accordance with the invention;

Figure 3 shows a system according to the invention;

FIG. 4 represents a central device according to the invention;

FIG. 5 represents a target list management equipment in accordance with the invention;

FIG. 6 represents an example of a reference black list as defined in the invention;

FIG. 7 represents the main steps of a method for updating a reference black list according to the invention;

FIG. 8 represents the main steps of a method for supervising the updating of a reference black list in accordance with the invention;

FIG. 9 represents the main steps of a target list management method according to the invention;

FIGS. 10 and 11 represent interfaces of equipment for supervising the updating of a reference black list in accordance with the invention; and FIG. 12 represents an item of equipment whose structure is shared by:

o equipment for supervising the updating of a black list in accordance with the invention;

o central equipment according to the invention; and o target list management equipment according to the invention.

detailed description

FIG. 1 represents a SYS system according to the invention.

This SYS system comprises a TX1 / SRVX1 equipment for supervising the updating of a reference black list, a central equipment SRV0 included in a RES network and RX1, GTW, SRV1 equipment for managing the target list, each of these equipment being in accordance with the invention.

The RES network can for example be a cloud network, or the Internet network.

As a variant, the RES network is an ad-hoc network.

The TX1 / SRVX1 equipment can consist of a user's TX1 terminal, for example a telephone, a smartphone, a computer, a tablet, etc.

As a variant, the equipment TX1 / SRVX1 can be an SRVX1 server.

This TX1 / SRVX1 equipment is shown in Figure 2 and includes:

a DETECT event detection module; and a selection and sending module ENV2 making it possible to send to the selected central equipment SRV0, via the network RES and upon detection of the event, a first message MESS1 comprising data representative of identifiers associated with solutions for communication, these identifiers having been selected by the user, the central equipment SRVO being selected if it is configured to update, on reception of the first message MESS1, the identifiers of a black list of reference LREF associated with the user from the data of the first MESS1 message.

The TX1 / SRVX1 equipment can implement the different steps of a process for supervising the updating of a reference black list according to the invention shown in FIG. 7.

This method comprises a step F10 of detecting an event, and a step F40 of sending to the central equipment SRVO, via the network and upon detection of the event, identifiers selected by the user to update the reference blacklist.

In a particular embodiment:

the supervision TX1 / SRVX1 equipment is a user terminal TX1; the central equipment SRVO is a server offering a service; and the event corresponds to a request to register the terminal TX1 to access this service.

In an implementation scenario of the invention, a user of the terminal TX1 can choose to register his terminal TX1 with a service offered by the server SRVO.

This request can be made in the form of a sending of a message to the SRVO server, comprising the characteristics of the terminal TX1, that is to say its name and its type.

The terminal TX1 can include one or more local black lists making it possible to block incoming communications on this terminal TX1.

These local black lists include identifiers selected by the user and make it possible to block any incoming communication on the terminal TX1 and of which the caller is one of these identifiers.

In the case where the terminal TX1 has local black lists, the above-mentioned message can correspond to the message MESS1 and also include all the identifiers included in the local black lists of the terminal TX1.

The message MESS1 can also include information associated with these identifiers or metadata (name, first name, etc.) included in the local black lists of the terminal TX1.

The identifiers and their associated information included in the MESS1 message can be used for updating the LREF reference list by the SRVO server: they can for example be added to the LREF reference list.

For example, within the framework of the SOAP protocol (“Simple Object Access Protocol” in English), the message MESS1 sent during a request to add a terminal TX1 to the service offered by the SRVO server can be as follows:

<? xmi version = 1.0?>

<soap: Enveiope xmins: soap = http: //schemas.xmisoap.org/soap/enveiope/ soap: encodingStyie = http: //schemas.xmisoap.org/soap/encoding/>

<soap: Body>

<AddDevice>

<Device xsi: type = ”nsl: DeviceDescription>

<deviceNamexsi: type = xsd: string> xxxxx </deviceName>

<deviceType xsi: type = xsd: enum> Computer / Smartphone / RTC phone / VoIP phone </deviceType>

<deviceBiackiist xsi: type = nsl: DeviceBlacklistType>

<biackiisted_item>

<biackiisted_item_firstName xsi: type- xsd: string> xxxx </blacklisted_item_firstName> <blacklisted_item_lastName xsi: type = xsd: string ''> xxxx </blacklisted_itemJastName> <biackiisted_item_phoneNumberxsi:

type = xsd: string> xxxx </blacklistedJtem_phoneNumber>

<blacklisted_item_mailAddress xsi:

type = xsd: string> xxxx </blacklisted_item_mailAddress>

<blacklisted_item_socialNetworkName xsi:

type = xsd: string> xxxx </blacklisted_item_socialNetworkName>

<blacklisted_item_socialNetworkContactName xsi: type = xsd: string> xxxx </blacklisted_item_socialNetworkContactName>

</biackiisted_item>

<biackiisted_item>

</biackiisted_item>

<biackiisted_item>

</biackiisted_item>

</deviceBiackiist>

</Device>

</AddDevice>

</ soap: Body>

</ soap: Enveiope>

In the previous code, the terminal TX1 is represented by the <Device> tag.

This TX1 terminal has the following characteristics:

a name, represented by the <deviceName> tag, which is a Text field; a type, represented by the <deviceType> tag, which is a field whose value is to be chosen from a list (computer, smartphone, VoIP phone, PSTN phone, etc.); and a list, represented by the <deviceBlacklist> tag, which is a field of type "DeviceBlacklistType".

This list contains a series of elements represented by the <blacklisted_item> tag. Each of its elements represents a contact and its different associated identifiers, used by different communication solutions. An element is therefore characterized by Text type fields, namely:

a first name, represented by the tag <blacklistedJtem_firstName>;

a last name, represented by the tag <blacklisted_item_lastName> Text; a phone number, represented by the <blacklisted_item_phoneNumber> tag;

an e-mail address, represented by the <blacklisted_item_mailAddress> tag; an online social network name, represented by the tag <blacklisted_item_ socialNetworkName>; and / or an identifier used on the social network previously named, represented by the tag <blacklisted_item_ socialNetworkContactName.

Furthermore, the message MESS1 can be sent by an agent, for example an application or a program executed by the terminal TX1.

One role of this agent is to collect the identifiers in the local black lists and / or their associated information and to transmit them via a MESS1 message to the SERVO server.

In the particular case where the identifiers retrieved are identifiers of the e-mail address type, as most e-mail solutions use the vCard format (RFC 6350 and 6868) to store contacts, this agent can be configured to read files from this format in a local black list and send the SERVO server the identifiers associated with these contacts in the form of email addresses so that they can be used to update the reference black list.

In a particular embodiment, the detected event is associated with the selection by the user of the identifiers whose representative data are included in the first message MESS1.

For example, if the equipment TX1 / SRVX1 corresponds to a terminal TX1, this terminal ΊΓΧ1 can be as shown in FIG. 10 and include a touch screen displaying an interface INT1.

This interface INT1 comprises, for example, INFOS information of a contact (for example a first name and a surname), and an identifier ID of this contact associated with a communication solution.

For example, the identifier ID corresponds to a telephone number and is associated with a telephony solution.

This ID identifier could also correspond to an email address associated with an email solution.

If the user wishes to select this ID identifier to add it to the reference blacklist, the INT1 interface offers a BLK1 button that can be activated by the user.

Pressing the user on the BLK1 button then triggers the sending of a MESS1 message comprising the ID identifier as well as INFOS information associated with this ID identifier to the central server SRV0 and aimed at adding this ID identifier and possibly this information INFO in the LREF reference list.

The sending of the message MESS1 can, as in the case of a request for registration for the service, be carried out by an agent, for example an application or a program implemented by the terminal TX1.

The detected event here corresponds to a user press on the BLK1 button.

The message MESS1 sent by the terminal TX1 to the server SRV0 can be, in general and always within the framework of the SOAP protocol, in the following form:

<? xm! version = 1.0?>

<soap: Enve! ope xmlns: soap = http: //schemas.xmlsoap.org/soap/envelope/ soap: encodingStyle = http: //schemas.xmlsoap.org/soap/encoding/> <soap: Body>

<AddBlacklistedItem>

<Blacklist xsi: type = nsl: DeviceBlacklist>

<blacklisted_item>

<blacklisted_item_firstName xsi: type = xsd: string> xxxx </biackiisted_item_firstName> <b! acklisted_item_iastName xsi: type = xsd: string> xxxx </blacklisted_item_lastName> <blacklisted_item_phoneNumberxsi:

type- xsd: string ''> xxxx </biackiisted_item_phoneNumber>

<blacklisted_item_mailAddress xsi:

type = ”xsd: string ''> xxxx </blacklisted_item_mailAddress>

<blacklisted_item_socialNetworkName xsi:

type = ”xsd: string”> xxxx </blacklisted_item_socialNetworkName>

<blacklisted_item_socialNetworkContactName xsi:

type = xsd: string> xxxx </blacklisted_item_socialNetworkContactName>

</biackiisted_item>

</ B! Acklist>

</AddBlacklistedItem>

</ soap: Body>

</ soap: Enveiope>

Here, the <AddBlacklistedItem> tag tells the SRVO server to add the characteristic elements of the element represented by the <BlacklistedItem> tag, this element representing a contact.

These characteristic elements include identifiers associated with this contact (a phone number represented by the tag <blacklisted_item_phoneNumber>, an email address represented by the tag <blacklisted_item_mailAddress>, an identifier used on a social network, represented by the tag <blacklisted_item_ socialNetworkContactName> ) and associated information (a first name, represented by the tag <blacklisted_item_firstName>, a surname, represented by the tag <blacklisted_item_lastName>, an online social network name, represented by the tag <blacklisted_item_ socialNetworkName>) .

If the user wishes to remove the ID identifier from the reference black list, he can uncheck the BLK1 button.

Pressing the user on the BLK1 button then triggers the sending of a MESS1 message also comprising the ID identifier as well as INFOS information associated with this ID identifier to the central SRVO server but this time aiming to delete this identifier ID and this information INFOS from the LREF reference list.

The detected event also corresponds here to a user press on the BLK1 button.

The message MESS1 sent by the terminal TX1 to the server SRVO can be, always within the framework of the SOAP protocol, of the following form:

<? xmi version = 1.0?>

<soap: Enveiope xmlns: soap = http: //schemas.xmlsoap.org/soap/envelope/ soap: encodingStyle = http: //schemas.xmlsoap.org/soap/encoding/>

<soap: Body>

<DeleteBlacklistedItem>

<Blacklist xsi: type = nsl: DeviceBlackiist>

<blacklisted_item>

<blacklisted_item_firstName xsi: type = xsd: string> xxxx </blacklisted_item_firstName>

<blacklisted_item_lastName xsi: type = xsd: string> xxxx </blacklisted_item_lastName>

<blacklisted_item_phoneNumberxsi:

type = xsd: string> xxxx </blacklisted_item_phoneNumber>

<blacklisted_item_mailAddress xsi: type-xsd: string> xxxx </blacklisted_item_mailAddress>

<blacklisted_item_socialNetworkName xsi:

type = xsd: string> xxxx </blacklisted_item_socialNetworkName>

<blacklisted_item_socialNetworkContactName xsi: type = xsd: string> xxxx </blacklistedJtem_socialNetworkContactName>

</blacklisted_item>

</Blacklist>

</DeleteBlacklistedItem>

</ soap: Body>

</ soap: Enve! ope>

Here, the <DeleteBlacklistedItem> tag tells the SRV / GTW network equipment to delete the characteristic elements of the element represented by the <BlacklistedItem> tag, this element representing a contact.

These characteristic elements include identifiers associated with this contact and information associated with it, represented in the message MESS1 by tags similar to those used in the message sent when identifiers are added.

In another example, the TX1 / SRVX1 equipment corresponds to an SRVX1 server.

This example applies in particular to communication solutions such as email, an online social network, a solution for sharing personal content, etc.

These communication solutions can be in the form of an application or a program implemented in a user's terminal or, alternatively, in the form of an internet service to which this terminal can access.

In this case, these communication solutions can integrate application programming interfaces (API for “Application Programming Interface” in English) allowing the user to add or delete identifiers in the LREF reference list.

These application programming interfaces are implemented by the SRVX1 server.

For example, a communication solution can integrate an application programming interface enabling an INT_API interface as shown in FIG. 11 to be displayed on a terminal screen.

If the communication solution is in the form of an application, this interface can correspond to a specific interface displayed by the application.

If the communication solution is in the form of an internet service, this interface can correspond to a specific web page of a site providing access to this internet service.

This INT.API interface can include ADD means (such as a text input area) already present in the prior art allowing an identifier of a contact to be entered so that this contact is blocked via the communication solution (and therefore added to a blacklist stored on a server).

The INT_API interface can also include a BLK2 button allowing the user to trigger the sending by the SRVX1 server of the first MESS1 message including the identifier to the central SRVO server, so that the latter adds it to the reference blacklist. LREF.

Equivalent means, not shown, can similarly enable a message MESS1 comprising an identifier to be sent to remove an identifier from the LREF reference list.

Here, the SRVX1 server implementing the application programming interface detects an event within the meaning of the invention when the user presses the BLK2 button on the INT_API interface.

The message MESS1 comprising data representative of identifiers selected by the user is received by the central equipment SRVO of the system SYS.

This central SRVO equipment can be as shown in FIG. 4 and can include:

a module REC1 for receiving, via the network RES, a first message MESS1 comprising data representative of identifiers associated with communication solutions, these identifiers having been selected by the user;

a module MAJ for updating the identifiers of a reference black list associated with the user from the data of the first message MESS1, the reference black list LREF being used to filter communications intended for the user if the caller ID is included in this LREF reference blacklist;

- a SEL module for selecting target list management equipment, connected to the RES network and capable of managing target black lists; and a module ENVI for sending to this equipment SRV1, GTW, RX1 via the network RES of a second message MESS2 comprising data representative of the reference black list LREF;

the equipment SRV1, GTW, RX1 being selected if they include devices which can access target black lists LC1, LC2 and configured to update the target black list from the data of the second message MESS2, the target black lists LC1, LC2 for filtering communications sent by callers whose identifiers are included in these target blacklists and intended for the user.

This central SRVO equipment can implement the steps of a method for updating a reference black list as shown in FIG. 8.

The central SRVO equipment can consist of an SRVO server or alternatively a terminal.

The reference blacklist can be constructed as shown in Figure 6.

It can be stored in the central SRVO equipment or alternatively in a separate device communicating with the central SRVO equipment.

It can include identifiers of different types: NUM telephone numbers, MAIL e-mail addresses, identifiers on an online social network RS, etc.

Each identifier can be associated in the list with a SURNAME name, with a NAME first name of a contact. Several identifiers can be associated with a single name and / or first name if these identifiers correspond to one and the same contact.

An identifier of the type used by an online social network can also be associated with the name of the online social network RS_NAME on which it is used.

On reception during a step E10 represented in FIG. 8 of the first message MESS1 sent by the equipment TX1 / SRVX1, the central equipment SRVO updates during a step E40 the identifiers of the reference list LREF.

This update may consist of adding and / or deleting from the LREF reference list one or more identifiers whose representative data are included in the message MESS1.

Once the LREF reference list has been updated, the central equipment SRVO determines equipment for managing the target list SRV1, GTW, RX1 and sends them a second message MESS2 comprising data representative of the LREF reference list.

This data may include identifiers included in the LREF reference list as well as information associated with these identifiers.

This second message is sent via the RES network if the SRV1, GTW, RX1 devices are connected to this RES network.

In a particular embodiment, the central SRVO equipment is a server offering a service, the management equipment SRV1, GTW, RX1 are terminals, for example user terminals, and these terminals are determined by the equipment. central SRVO if they are registered with this service.

The message MESS2 comprising data representative of the reference list LREF is received by the equipment SRV1, GTW, RX1 for managing the target list included in the system SYS.

This equipment SRV1, GTW, RX1 can for example comprise a server SRV1, a gateway (for example domestic) GTW, and a terminal RX1.

These items of equipment SRV1, GTW, RX1 are each able to implement the steps of a target list management method as shown in FIG. 9.

These devices SRV1, GTW, RX1 are each as shown in FIG. 5, and may each include:

a module REC2 for receiving, via the network RES, a second message MESS2 transmitted by a central equipment TX, SRVO, this second message MESS2 comprising data representative of a black list of reference LREF, this black list of reference LREF aiming filtering communications associated with identifiers included in this black LREF reference list and sent to a user; and

- AGI, AG2 devices that can access target black lists LC1, LC2 and configured to update the target black lists LC1, LC2 from the data of the second message MESS2, the target black lists LC1, LC2 being used to filter any communication whose caller ID is included in the target black lists LC1, LC2 and sent to the user.

On reception during a step G10 represented in FIG. 8 of the second message MESS2 sent by the central equipment SRVO, devices AGI, AG2 of each of the items of equipment SRV1, GTW, RX1 update during a step G50 of the target black lists LC1, LC2 from the data of this second message MESS2.

This update may consist of adding and / or deleting one or more identifiers whose representative data are included in the message MESS2 in the target black lists LC1, LC2.

The target black lists LC1, LC2 can be stored locally on the SRV1, GTW, RX1 equipment or, as a variant, on remote devices which the SRV1, GTW, RX1 equipment can access.

One of the SRV1, GTW, RX1 management devices may be an SRV1 server associated with a communication solution implemented in part on a network, such as an electronic messaging solution, an online social network or a sharing solution. personal content.

This communication solution can be associated with a target blacklist of the user, comprising identifiers and making it possible to block communications made via this communication solution and associated with these identifiers.

For example, an electronic messaging type communication solution can be associated with a target black list containing email addresses. Email messages sent from these email addresses to the user will then be blocked.

In the case where the communication solution is implemented by the network, this solution can integrate an application programming interface implemented by the SRV1 server and making it possible to receive the message MESS2 and update the target blacklist of the communication solution from the data of the MESS2 message.

One of the items of equipment SRV1, GTW, RX1 can also consist of an SRV1 gateway, for example a domestic gateway.

This SRV1 gateway may include a target blacklist updated from the data of the MESS2 message.

In a particular embodiment, the updating of the target black list aims at ensuring that this target black list is identical to the reference black list LREF.

It can be located when there is a flow interruption between a terminal sending a communication and a user terminal receiving the communication.

In this case, if the target black list includes the identifier of the caller who is the source of this communication, then the gateway filters this communication.

One of the devices SRV1, GTW, RX1 for managing the target list can also consist of a terminal RX1 of the user.

This terminal RX1 can comprise several target lists LC1, LC2 making it possible to block communications intended for this terminal RX1 and which can be updated from the data of the message MESS2.

In a particular embodiment, each of the AGI, AG2 devices of the SRV1, GTW, RX1 equipment:

is associated with a communication solution;

- is configured to access a target black list LC1 among the target black lists LC1, LC2, the target black list LC1 being associated with the communication solution; and

- is configured to update the target black list LC1 from data from the second message MESS2 representative of the reference black list LREF, this data being associated with this communication solution.

For example, if one of the devices SRV1, GTW, RX1 is a terminal RX1 of a user, this terminal can comprise two target black lists LC1, LC2, each one being associated with a communication solution SCI, SC2, and can also include two devices AGI, AG2 corresponding to agents, for example two applications or two programs allowing respectively to modify each of the target black lists LC1 and LC2.

The agent AGI will update the list LC1 from the data of the message MESS2 associated with the communication solution SCI, and the agent AG2 will update the list LC2 from the data of the message MESS2 associated with the communication solution SC2 .

For example, if the list LC1 is associated with a telephony solution and includes identifiers of the telephone number type, then the agent AGI updates the list LC1 from the telephone numbers included in the message MESS2, for example by adding or removing them from the LC1 target list.

If the LC2 list is associated with an electronic messaging solution and includes identifiers of the email address type, then the agent AG2 updates the LC2 list from the email addresses included in the MESS2 message, for example by adding them or removing from target list LC2. To do this, the AG2 agent can transcribe the email addresses in Vcard format.

In a particular embodiment represented in FIG. 3, equipment TX1, TX2, TX3, SRVX1, SRVX2 for supervising the updating of a reference list can also consist of equipment for managing the target list RX1, RX2 , RX3, SRV1, SRV2.

In this embodiment, the SYS system comprises for example three terminals TX1 / RX1, TX2 / RX2, TX3 / RX3, and two servers SRV1 / SRVX1, SRV2 / SRVX2 capable on the one hand of sending, upon detection of an event , a first message MESS1 comprising identifiers selected by the user and aiming to update a black list of LREF reference and on the other hand able to receive a message MESS2 comprising data representative of the LREF reference list to update target lists.

Each of these pieces of equipment can therefore initiate an update of the LREF reference list but also update one or more target lists from the LREF reference list.

Furthermore, the SYS system can comprise a GTW gateway, for example a domestic gateway, connected to the RES network and to which two user TX2 / TX2, TX3 / RX3 terminals can be connected by WiFi.

This gateway can play the role of equipment for managing a target list and include a target list LC updated on reception of the message MESS2 comprising data representative of the reference list LREF.

When the TX2 / TX2 and / or TX3 / RX3 terminals are connected to the GTW gateway, this gateway can also transfer (for example in the form of a message similar to the MESS2 message) data representative of the target list it contains to these TX2 / TX2 and / or TX3 / RX3 terminals.

The TX2 / TX2 and / or TX3 / RX3 terminals can then update their own target lists LC2, LC3 from this data.

Claims (14)

1. Equipment (SRVO) of a network (RES), called "central equipment", this equipment comprising: a module (REC1) for receiving, via said network (RES), a first message (MESS1) comprising data representative of at least one identifier (ID1, ID2, ID3) associated with at least one communication solution, said at least one identifier (ID1, ID2, ID3) having been selected by at least one user; a module (MAJ) for updating the identifiers of a reference black list (LREF) associated with said user from said data of said first message (MESS1); said reference black list (LREF) being used to filter any communication sent by a caller and intended for said at least one user if the identifier of the caller is included in said reference black list. 2. Equipment according to claim 1, in which said identifiers included in said reference black list (LREF) are of at least two different types (NUM, MAIL, RS). 3. Equipment according to claim 1 or 2, wherein said data representative of said at least one identifier (ID1, ID2, ID3) comprises said at least one identifier (ID1, ID2, ID3) and wherein said updating of said list reference black (LREF) includes: adding said identifiers (ID1, ID2, ID3) to said reference black list (LREF); and / or a deletion of said identifiers (ID1, ID2, ID3) from said reference black list (LREF). 4. Equipment according to any one of claims 1 to 3, comprising: a module (SEL) for selecting at least one target list management equipment (SRV1, GTW, RX1), said target list management equipment being connected to said network (RES) and configured to manage at least one black list target (LC1, LC2) associated with said user; and a module (ENVI) for sending to said at least one target list management equipment (SRV1, GTW, RX1), via said network (RES), of a second message (MESS2) comprising data representative of said list reference black (LREF); said at least one target list management equipment (SRV1, GTW, RX1) being selected if it comprises at least one device (AGI, AG2) which can access said at least one target black list (LC1, LC2) associated with said user and configured to update said target blacklist (LC1, LC2) from said data of said second message (MESS2), said at least one target blacklist (LC1, LC2) being used to filter any communication emitted by a caller and to destination of said at least one user if the identifier of the caller is included in said target list. 5. Method for updating a reference black list (LREF) associated with at least one user, said method being able to be implemented by network equipment (SRVO) of a network (RES), said method comprising: a step (E10) of receiving, via said network (RES), a first message (MESS1) comprising data representative of at least one identifier (ID1, ID2, ID3) associated with at least one communication solution, said at least one identifier (ID1, ID2, ID3) having been selected by said at least one user; and a step (E40) of updating said reference black list (LREF) from said data of said first message (MESS1); said reference black list (LREF) being used to filter any communication sent by a caller and intended for said at least one user if the caller's identifier is included in said reference black list. 6. Equipment (TX1, SRVX1) for supervising the updating of a reference list (LREF), comprising: a detection module (DETECT) of at least one event; and a selection and sending module (ENV2) making it possible to send a selected so-called "central equipment" (SRVO), via a network (RES) and on detection of said at least one event, a first message (MESS1) comprising data representative of at least one identifier (ID1, ID2, ID3) associated with at least one communication solution, said at least one identifier (ID1, ID2, ID3) having been selected by said at least one user, said equipment central (SRVO) being selected if it is configured to update, on receipt of said first message (MESS1), identifiers of a reference black list (LREF) associated with said user from said data of said first message (MESS1 ), said reference black list (LREF) being used to filter any communication sent by a caller and intended for said at least one user if the caller's identifier is included in said reference black list nce. 7. Equipment according to claim 6, wherein said event corresponds to an action of said at least one user, said action being associated with said selection of said at least one identifier (ID1, ID2, ID3) by said at least one user. 8. Method for supervising the updating of a reference list (LREF), said method being able to be implemented by equipment (TX1, SRVX1), said method comprising: a step of detecting (F10) an event; and a step of selecting and sending (F40) to a so-called “central equipment” device (SRVO) selected, via a network (RES) and on detection of said event, of a first message (MESS1) comprising data representative of '' at least one identifier (ID1, ID2, ID3) associated with at least one communication solution, said at least one identifier (ID1, ID2, ID3) having been selected by said at least one user, said central equipment (SRVO) being selected if it is configured to update, on receipt of said first message (MESS1), identifiers of a reference black list (LREF) associated with said user from said data of said first message (MESS1), said black list of reference (LREF) being used to filter any communication sent by a caller and intended for said at least one user if the identifier of the caller is included in said reference blacklist. 9. Target list management equipment (SRV1, GTW, RX1), comprising: a module (REC2) for receiving, via a network, a message (MESS2) sent by an equipment of said network, called "central equipment" (SRVO), said message (MESS2) comprising data representative of a black list of reference (LREF) associated with a user, said reference black list (LREF) being used to filter at least one communication sent by a caller and intended for said at least one user if the identifier of the caller is included in said list reference black; and at least one device (AGI, AG2) configured to access and update at least one target blacklist (LC1, LC2) associated with said user from said data of said message (MESS2), said at least one target blacklist (LC1 , LC2) being used to filter any communication sent by a caller and intended for said at least one user if the identifier of the caller is included in said target blacklist. 10. Equipment (SRV1, GTW, RX1) according to claim 9, in which each of said devices (AGI, AG2) of said equipment (SRV1, GTW, RX1): - is associated with a communication solution; - is configured to access a target black list (LC1) from among said target black lists (LC1, LC2), said target black list (LC1) being associated with said communication solution; and is configured to access and update said target black list (LC1) from data of said message (MESS2) representative of said reference black list (LREF), said data being associated with said communication solution. 11. Target list management method that can be implemented by equipment (SRV1, GTW, RX1), said method comprising: a step (G10) of reception, via a network, of a message (MESS2) transmitted by an equipment of said network, called "central equipment" (SRVO), said message (MESS2) comprising data representative of a black list of reference (LREF) associated with a user, said reference black list (LREF) being used to filter at least one communication sent by a caller and intended for at least one user if the caller's identifier is included in said reference blacklist; and at least one step (G50) of accessing at least one target black list (LC1, LC2) associated with said user and updating said target black list (LC1, LC2) from said data of said message (MESS2), said at least one target black list (LC1, LC2) being used to filter any communication sent by a caller and intended for said at least one user if the identifier of the caller is included in said target black list. 12. System (SYS) comprising: equipment (TX1, SRVX1) for supervising the updating of a reference list (LREF) according to claim 6 or 7, said equipment (TX, SRVX1) being configured to send a first message via a network (RES) (MESS1) to a central equipment (SRVO) according to claim 4; said central equipment (SRVO), this central equipment (SRVO) being configured to send a second message (MESS2) via said network (RES) to at least one equipment (SRV1, GTW, RX1) for managing the target list according to claim 9 or 10; and said at least one target list management equipment (SRV1, GTW, RX1). 13. Computer program (PG) comprising instructions for the execution of the steps of the method for updating a reference black list (LREF) according to claim 5, when said program is executed by a computer. 14. Recording medium (SUP) readable by a computer on which a computer program is recorded comprising instructions for the execution of the steps of the method for updating a reference black list (LREF) according to claims 5. 1/3 SYS I_______________I