FR3007927A1 - DEPOSIT AND CONSULTATION OF MESSAGES BY USERS OF SOCIAL NETWORKS - Google Patents

Abstract

The invention relates to a method of depositing a message from a social network user U1, said user depositing, to one or more users U2, U4 of a social network, said user recipients. The message is delivered in a message box associated with an idcom2 telephone line, idcom4 associated with a social network user identifier, assigned in the social network to the recipient user, sent with the message filing request. The destination user U2, U4 receives a notification of the deposit of the message, comprising a social network user identifier idps1 assigned to the depositing user. The recipient user of the message consults the message from the mailbox. When viewing the message, the social network user identifier assigned to the user depositing idps1 is returned to the recipient user. A reply message can be filed for each message posted or viewed.

Description

Technical Field The present invention relates both to the field of social networks, accessible for example via the Internet type computer network and multimedia messaging services. STATE OF THE ART Social networks on the Internet network allow its users to form groups of contacts, constituted for example by friends, family members, persons sharing the same interests or professional knowledge, etc. To this end, they provide their users with services and tools for exchanging content and information, such as, for example, photos, attendance reports, news information, etc. These exchange services are accessible. via adapted user interfaces. Among these exchange services, there are different services for transmitting one or more messages to one or more users of the social network. These messages are accessible and searchable via a web page of the social network. In the case of a "public" message, the message is viewable by users other than the recipient user of the message, via a page associated with the message recipient user, sometimes called the "wall" of this user. In the case of a "private" message, the message will only be viewable by the recipient user of the message, in a web page displaying his private messages.

In both cases, it is necessary to have access to the computer network underlying this social network (the Internet, in general) to file and / or consult such messages, or even to create a user account with of the social network for the filing and / or consultation of "private" messages. This represents a constraint for the users and restricts the access to the service of deposit and / or consultation of messages to the only equipped users and / or the only moments where these users have the adapted equipments. The invention offers a solution that overcomes all or part of the disadvantages of the state of the art. According to a first aspect, the invention relates to a method for consulting a message and, correspondingly, a method of processing a message consultation request, a network entity implementing the method of processing a request for consultation of a message. message and a terminal implementing the message consultation method. The user at the origin of the message consultation request is a social network user, referred to here as a consultant user. The user who requested the delivery of the message is also a social network user, referred to here as a user who files. The consultation method comprises: a step of sending a request for consultation of at least one message deposited at the request of a user of a social network, said user depositing, in a mailbox of a line telephone whose identification is memorized in association with a social network user identifier of a social network user, said consulting user, for at least a first message deposited, a reception and retrieval step, by the terminal, a social network user identifier assigned to the user depositing in a social network and at least a portion of the content of the first message. The method of processing a message consultation request comprises: a step of receiving, from a terminal, a request for consultation of at least one message deposited on request by a user of a network; social, said user depositor, in a mailbox of a telephone line whose identification is stored in association with a social network user identifier of a social network user, said user consultant, - for at least a first message deposited in said mailbox, a step of sending to said terminal a social network user identifier of the user depositing the first message and at least part of the content of the first message, said sending triggering a rendering by the terminal of said social network user identifier and the portion of the content. A network entity implements the method of processing the message consultation request. This network entity comprises: - a receiving module, from a terminal, a request for consultation of at least one message deposited on request of a user of a social network, said user depositing, in a box of a telephone line whose identification is stored in association with a social network user identifier of a social network user, said consulting user, - a module for sending to said terminal of a user identifier social network of the user depositing the first message and at least a portion of the content of the first message, a said sending triggering a restitution by the terminal of said social network user ID and part of the content. A terminal communicates with this network entity to send the message lookup request. This terminal includes - a module for sending a request for consultation of at least one message deposited on request of a user of a social network, said user depositor, in a mailbox of a telephone line including a identification is stored in association with a social network user identifier of a social network user, said consulting user, - a module for receiving and retrieving, by the terminal, an assigned social network user identifier to the user depositing in a social network and at least part of the content of the first message.

The invention allows a message consultation between social network users through a mailbox of a telephone line, without the need for users to first share their identifications of telephone lines. Only the social network identifiers of the different users are required to implement such message consultation. Indeed, during the consultation of the message, it is the social network user identifier of the user depositant is used, and not necessarily the identification of his telephone line, as is usually the case for messages dropped in the phone line mailboxes. In addition, it is the social network identifier of the consulting user that is used to identify the telephone line whose mailbox will be used for posting the message. The recipient user of the message therefore no longer needs to connect to the social network to be able to receive messages from users with whom he is related in the social network. He can consult these messages directly in his mailbox, and this while benefiting from a logic of user identification that is that of the social network. Thus it combines the opportunities that are provided by the social network in terms of contact with other users and those of a messaging system, as proposed by the telephone line operators, in terms of ease of access and consultation. Regarding the relationship existing in the social network between the user and the user viewing the message, different embodiments are possible. In one embodiment of the method of processing or consultation request, the social network user identifier of the user filing is an identifier under which the user depositor is known to the user consulting in the social network and or the user's social network user identifier of the consulting user is an identifier under which the consulting user is known to the user depositing in the social network. In one embodiment of the method of processing or consultation request, the user's social network user identifier is an identifier, for example a pseudonym, not disclosing the actual identity of the user filing and / or the social network user identifier of the consulting user is an identifier, for example a pseudonym, not disclosing the real identity of the consulting user. In one embodiment of the method of processing or consultation request, the identification of the telephone line is stored in association with a social network user identifier assigned to the consulting user, under which the consulting user is known. of the user depositing in the social network.

In one embodiment of the method of processing or requesting the consultation, the identification of the telephone line is declared by the consulting user in social network user profile data of that consulting user which is not accessible to the user. the user depositing through the social network. Thus an entirely anonymized message repository can take place between a user who is a subscriber and one or more recipient users who will consult the message: the real identity of the users is never disclosed, only the identifiers of social network users being transmitted when message submission and its subsequent notification. In the case where the first message has been filed for several recipients, a particular embodiment of the consultation method is provided. In this embodiment, in which the first message has also been deposited in a mailbox of another telephone line whose identification is stored in association with a social network user identifier of a social network user, said recipient user, the method comprises a step of reception and retrieval by the terminal of a social network user identifier of the recipient user.

In the case where several messages are deposited in the mailbox, several embodiments are possible. In one embodiment, the message consultation request is for viewing a plurality of messages to be successively delivered in an order specified by the consulting user, and the method includes, for each message of said plurality of messages processed in accordance with the specified order, a step of reception and retrieval by the terminal of a social network user identifier of the user depositing this message and at least part of the content of this message. In one embodiment, a message deposited in said mailbox is stored in association with a user's social network user identifier of the user and with a social network user identifier of at least one recipient user of this message. In one embodiment, the method comprises a step of identifying at least one message deposited in said mailbox by a user whose social network user identifier is indicated by the consulting user. In one embodiment, the method comprises a step of identifying at least one message deposited in said mailbox to a recipient user whose social network user identifier is indicated by the consulting user. Thus the selection of the messages that will be consulted can be made on the basis of user ID of social networks that are stored in association with the messages deposited. This is particularly convenient for the consulting user and also makes it possible to avoid having to communicate information other than the social network user identifiers of the users concerned by a message being accessed. Anonymity can thus be preserved insofar as these identifiers of social network users can be pseudonyms that do not disclose the real identity of the users. According to a second aspect, the invention relates to a response message deposit request method and, correspondingly, to a method of processing a request for the filing of a response message, a network entity implementing the method of processing a response message. request for filing response message and a terminal implementing the response message filing request method. The response message is deposited in response to an earlier message, said first message, accessed by means of a method, an entity or a terminal according to the first aspect of the invention.

In particular, the previous message has been the subject of a request for consultation, formulated by means of a consultation method according to the first aspect of the invention and / or treated by means of a method of processing a message consultation request according to the first aspect of the invention. The method of processing a request to deposit a response message comprises - a step of receiving a request to deposit a second message, in response to the first message, - a step of identifying at least one message a second telephone line associated with the social network user identifier assigned to the user depositing the first message, - a step for triggering, for at least one said second identified telephone line, a depot of said second message in a box of messaging associated with the identified second telephone line and sending a notification of deposit of said second message to at least one terminal associated with the identified second telephone line, the notification comprising a social network user identifier assigned to the second telephone line; user who requested the submission of the second message.

The request method for filing a response message comprises: - a step of sending a request for deposit of a second message, in response to the first message, said initiating filing request, for a second associated telephone line the social network user identifier assigned to the user depositing the first message, a depot of the second message in a mailbox associated with the second telephone line, and a sending of a deposit notification of the second message at the destination at least one terminal associated with the second telephone line, the notification comprising a social network user identifier assigned to the user who has requested the deposit of the second message.

A network entity implements the method of processing the response message filing request. This network entity comprises: a module for receiving a request for depositing a second message, in response to the first message, a module for identifying at least one second telephone line associated with the user identifier. social network assigned to the user depositing the first message, - a module for triggering, for at least one said second identified telephone line, a depot of said second message in a mailbox associated with the identified second telephone line and a transmission of a notification of deposit of said second message to at least one terminal associated with the identified second telephone line, the notification comprising a social network user identifier assigned to the user having requested the filing of the second message.

A terminal communicates with this network entity to send the response message filing request. This terminal comprises: a module for sending a request for the deposit of a second message, in response to the first message, said request for filing a response message that triggers, for a second telephone line associated with the identifier of social network user assigned to the user depositing the first message, depositing the second message in a mailbox associated with the second telephone line and sending a notification of the second message to at least one terminal associated with the second telephone line, the notification comprising a social network user identifier assigned to the user who has requested the deposit of the second message. The invention thus makes it possible to implement a response mechanism to a message deposited in a telephone line mailbox by means of a method, a network entity and / or a terminal according to a first aspect of the invention. The identifiers of social network users are once again used to identify the telephone line of the recipient user of the reply message and to notify this recipient user, in particular on the user having requested the deposit of the message. Answer. The invention thus allows a message and reply filing between social network users through a mailbox, without the need for users to first share their identifications of telephone lines. Only the social network identifiers of the different users are required to perform this message submission. Regarding the identification of the recipients of the reply message, the response message processing method comprises in one embodiment: a step of sending social network user identifiers for each social network user who is either the user depositing the first message, ie a user receiving the first message, - a step of receiving selection information, identifying the recipient user (s) of the second message from the user depositing the first message and the user or users recipients of the first message. Here again, the identifiers of social network users can be used to proceed with the identification of the recipients of a response message to be dropped. This is particularly convenient when the users know each other only through their social network identifiers and have no knowledge of the real identity and / or a telephone line on which a social network user could be contacted. In one embodiment, the method of processing a response message deposit request includes: - a step of receiving a request to deposit a third message, in response to the second message, - a step of identification of at least one third telephone line associated with the social network user identifier assigned to the user depositing the second message, - a step for triggering, for at least one said third identified telephone line, a depot of said third message in a mailbox associated with the identified third telephone line and sending a notification of deposit of said third message to at least one terminal associated with the identified third telephone line, the notification comprising a user identifier of social network assigned to the user who requested the submission of the third message. Thus, the response message deposit mechanism is recursively applicable for depositing a response message to an earlier response message. According to one embodiment, the method of processing a response message filing request includes - a step of identifying a message that is a response message to the first message or whose first message is a response message a step of sending information to the terminal to indicate a possibility of consulting the identified message, a step of sending to the terminal of a social network user identifier of the user depositing the identified message. , triggering a restitution by the terminal of said social network user identifier. In order to enrich the message consultation possibilities, it is possible to detect the presence of a response message or a message prior to the message consulted and to propose to the consulting user to consult it also. Each device according to the invention (network or terminal entity) is designed to implement one or more of the first and second aspects of the invention. In addition, the various embodiments which have been presented for the methods or devices are combinable with each other for the implementation of the first and second aspects of the invention.

According to a preferred implementation, the different steps of a method according to the first and / or second aspect of the invention are implemented by a software or computer program. The invention thus relates to a software or program, capable of being executed by a computer or a data processor, this software / program comprising instructions for controlling the execution of the steps of a method according to the first and / or second aspect of the invention. These instructions are intended to be stored in a memory of a computing device, loaded and then executed by a processor of this computing device. This software / 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 form what other form is desirable. The computing device can be implemented by one or more physically distinct machines and generally presents the architecture of a computer, including at least some of the constituents of such an architecture: data memory (s), processor (s), communication bus, hardware interface (s) for connecting this computing device to a network or other equipment, user interface (s), etc. The computer device (network or terminal entity) which implements the various steps of a method according to the first and / or second aspect of the invention is thus provided with the following means: storage means, in particular a memory, for the storing program instructions designed to control the execution of the steps of the concerned method of the data processing means, in particular a data processor, capable of executing the stored program instructions in order to implement the steps of the method concerned. This computing device (network or terminal entity) which implements the different steps of a method according to the first and / or second aspect of the invention further comprises means for implementing the different steps of the various embodiments of the invention. these processes. These means are software modules (software) and / or hardware (hardware). In this context, the term "module" corresponds in this document to a software component, to a hardware component or to a set of hardware and / or software components, able to implement a function or a set of functions, according to what which is described below for the module concerned. The invention also relates to an information carrier readable by a data processor, and comprising instructions of one of the programs mentioned above. The information carrier may be any entity capable of storing such a program. The invention will be better understood on reading the description which follows, given by way of example and with reference to the accompanying drawings. Fig. 1 shows a communication system according to an embodiment of the present invention. FIG. 2 is a simplified flowchart of an embodiment of an initial configuration phase, prior to the implementation of the message depositing method or the response message depositing method. FIG. 3 is a simplified flowchart of an embodiment of the message depositing request method, implemented on the user terminal side, and of the method of processing a message deposit request, implemented on the mail server side. and / or service platform.

FIG. 4 is a simplified flowchart of an embodiment of the message consultation method, implemented on the user terminal side, and of the method of processing a message consultation request, implemented on the mail server side and / or service platform. FIG. 5 is a simplified flowchart of an embodiment of the response message deposit request method, implemented on the user terminal side, and of the method for processing a response message deposit request implemented. server side and / or service platform. In this document, the term 'social network' refers to any type of social network implemented via a telecommunications network, for example via the Internet network. Such a social network includes communities of people who exchange through a communication infrastructure, implemented by one or more computer servers, for example by one or more Web servers. People establish or declare links between them, on the basis of various criteria, such as personal affinities, or proximities of professional career, or similar centers of interests, etc ... for example, the social network based on Facebook ®, Twitter ®, Viadeo ®, Linkedln®, etc. ... By terminal, any communication device with a user interface and able to establish a communication through a network telecommunication. In the remainder of the description, the following notions will be used: a "depositing user" is a user who formulates / initiates a request to deposit a message; a "recipient user" is a user who is intended for a message filed by a filing user; there may be one or more recipients of the same message; - A "user consultant" is a user who formulates / initiates a request to view a message: it may be a user depositing this message or a user receiving this message.

Figure 1 - Communication System Figure 1 schematically shows a SYS communication system according to an embodiment of the present invention. This SYS communication system is articulated around several telecommunication networks, interconnected with each other: an extended network (WAN), for example the Internet network; a mobile telephone network RM, for example a GSM (Global System for Mobiles) network, UMTS (Universal Mobile Telecommunications System), LTE (Long Term Evolution), etc .; this network is interconnected with the Internet network RI so that compatible terminals (3G or 4G terminals in particular) with Internet access, can access this Internet network RI via the mobile network RM; a fixed telephony RF network, for example a switched telephone network (PSTN). - a VoIP (Voice over IP) VoIP telephony network, using or not the technical infrastructures of the IN and RM networks.

This communication system also includes: - An SRS social network server, accessible through the Internet network RI, for management, access to a social network RS and the implementation of communications within this social network RS ; - A PFS messaging platform associated with the social network RS, providing a message storage service accessible through the Internet network RI, accessible in particular by any terminal connected to the Internet network RI; An SMGM messaging server for the mobile network RM, accessible from a terminal connected to the mobile RF network; - An SMGF mail server for the fixed RF network, accessible from a terminal connected to the fixed network RF. An SMGV messaging server for the VoIP network RV, accessible from a terminal connected to the VoIP network RV; A plurality of communication terminals T1, T2, T3, T4 used respectively by users U1, U2, U3, U4. It is assumed here that the users U1, U2, U3, U4 are all users of the social network RS: each of these users has a user account, registered with the social network server SRS. In addition, the user U1 has a terminal TA, type personal computer (PC, personal computer) for access to the Internet network RI and social network RS.

The terminals T1, T2, T3, T4 Each of the communication terminals T1, T2, T3, T4 is associated with at least one telephone line, referenced respectively L1, L2, L3, L4. By telephone line, is meant here any telecommunication line suitable for the establishment of a communication, that this communication is audio and / or videophone and / or textual, established via a mobile and / or fixed communication network, established in mode package or in circuit mode, etc. As a purely illustrative example, it is assumed that: the terminal T1 is a fixed telephone connected to the fixed network RF, associated with a fixed telephone line L1, wired, identified by a fixed telephone number: the terminal T1 is designed to establish a circuit-mode telephone communication through the fixed RF network; the terminal T2 is a mobile telephone connected to the mobile network RM in circuit mode, associated with a mobile telephone line L2, identified by a mobile telephone number, (in general, this number is a MSISDN number): the terminal T2 is designed to establish a circuit-mode telephone communication through the mobile network RM; the terminal T3 is a mobile telephone connected to the mobile network RM in circuit mode, associated with a mobile telephone line L3, identified by a mobile telephone number (generally this number is a MSISDN number): the terminal T3 is designed to establish a circuit-mode telephone communication through the mobile network RM; the terminal T4 is a mobile telephone connected to the mobile network RM in circuit mode, associated with a mobile telephone line L4, identified by a mobile telephone number (in general, this number is an MSISDN number, Mobile Station International Subscriber Directory Number) : the terminal T4 is designed to establish a circuit mode telephone communication through the mobile network RM; the T4 terminal is also a dual-mode telephone, equipped with a Wi-fi interface and associated with a VoIP telephone line, capable of establishing a voice over IP (Voice over IP) packet telephone through the Internet network, the mobile network RM and / or Wi-fi cells access to one of these two networks. SMGF, SMGM, SMGV network messaging servers A messaging service is offered in the RF fixed network. This messaging service is for example a network messaging service. The messages and mailboxes of the various telephone lines of the fixed network are managed and stored by the SMGF mail server. The messages managed by this messaging service are most often audio messages, or even text, the latter being searchable in voice form. The messages deposited can be consulted by a user by establishing, by means of a terminal associated with the telephone line, a telephone connection with the SMGF message server. The content of the message is then transmitted to the terminal in the form of a telephone audio stream.

Alternatively, the messages and the mailbox of a telephone line of the fixed network RF can be managed and stored by a fixed telephone answering machine, connected to the telephone line, and located for example at the home of the user subscribed to this line telephone.

A messaging service is also available in the RM mobile network. This messaging service is for example a network messaging service. The messages and mailboxes of the various telephone lines of the fixed network are managed and stored by the SMGM mail server. The messages handled by this messaging service are audio, text and / or video messages. Here too, the messages deposited can be consulted by a user by establishing, by means of a terminal associated with the telephone line, a telephone connection with the SMGF messaging server. The content of the message is then transmitted to the terminal in the form of a telephone audio stream. A messaging service is also available in the VoIP RV network. This messaging service is for example a network messaging service: the messages and mailboxes of the various telephone lines of the fixed network are managed and stored by the SMGV mail server. The messages handled by this messaging service are audio, text, and / or video messages. For the implementation of the message consultation method, each of the SMGF, SMGM, SMGV mail servers is in charge of receiving and processing a message consultation request, the transmission of the information associated with this message and the reception and processing of a possible request for response to a message consulted. The social network SRS server The social network SRS server implements a social network service for one or more social networks. In the example described here, the social network is accessible through the Internet network IN: a user connects to this social network by loading on his terminal a Web page, corresponding to a given URL, forming part of the Web domain of the network social. The SRS social network server behaves like any web server: it transmits a Web page to each terminal following a Web request sent by this terminal to this server.

The SRS social network server is responsible for controlling access to the social network. In particular, the social network SRS server controls access to the social network from authentication data entered by the user in a web page. The authentication data of a user comprises a social network user identifier (for example, an email address of this user), and at least one user authentication data (for example an associated password). at its email address): this authentication data is stored by the social network server SRS. In practice, any type of identifier that uniquely identifies a user account of a person using a social network is used for the implementation of the invention. In general, it is a reference defined by the user at the time of the creation of his user account. This reference can be an email address, a string of characters and / or an image, photo, etc. It is assumed in the remainder of the description that the users U1, U2, U3 and U4 respectively use social network user identifiers denoted id1, id2, id3 and id4. Each social network user also defines at least one pseudonym, or borrowing identifier, under which this user will be known in the social network by the other users with whom this user enters communication through the social network. This pseudonym can be an alphanumeric character string and / or an image, a photo, etc. This pseudonym is a social network user identifier that can be used for the implementation of the various methods described in this document. The advantage of using this nickname is that it anonymizes the exchanges of this user with other users of the social network: the true identity of the user is not deductible from this pseudonym alone. Likewise, the email address of this user or his telephone number, or more generally his telephone or postal address or e-mail addresses, are not deductible from this pseudonym alone. In the remainder of this document, we will therefore speak about this pseudonym, anonymized identifier of social network user. It is assumed that the users U1, U2, U3 and U4 use the pseudonyms idpsl, idps2, idps3 and idps4, respectively.

Unlike identifiers idl, id2, id3, id4 which are unique - in the sense that a user account and only one is identified by one of these identifiers - the pseudonyms may not be unique within a given social network: it it is sometimes possible for a pseudonym to be used by several users. The distinction between the different users of the same pseudonym can be made for example on the basis of an image (photo) or information that they publish on themselves in association with their pseudonym. The social network SRS server is also responsible for storing, in an associated DB database, the profile data and other parameters associated with the users registered with the social network service. In the profile data are public data and private data: the public data made available to other users who come into contact with this user, in order to inform these other users about the user's personality, his professional profile or his tastes, etc. While private data is not transmitted or accessed by another user of the social network. Private data is however used by the social network server SRS for the implementation of different services. Among the private data, the social network server SRS notably stores for each user who wishes it, a telephone line identification to be used for the filing of message intended for this user. This telephone line identification must be present for each recipient user of a message, and preferably for each user depositing a message, in order to allow a user who is the recipient of a message from that user to request the filing of a response message to this message. The PFS messaging platform The PFS messaging platform associated with the social network RS is accessible via the Internet network RI by a terminal or server connected to the Internet network RI. This PFS messaging platform implements a service of recording and depositing messages. In the case where the user depositing the message and / or the user receiving this message remains anonymous because he is identified during the consultation or the posting of a message by a pseudonym not disclosing his real identity, the service implemented by the PFS messaging platform is an anonymized message repository service. These messages will also be anonymized during their consultation. The user depositing the message and / or the recipient user of this message is in this case known to other users only by an anonymized user identifier of social network, including its pseudonym. In particular, the identification of the telephone line of a recipient or depositor user is never disclosed to other users with whom he exchanges messages by one of the methods described in this document. For the implementation of the method of processing a message deposit request (whether for an initial message, or even for a message to reply to an initial / prior message deposited via this PFS messaging platform) , the PFS messaging platform is in charge of receiving and processing a message deposit request, the recording of the message and the information associated with this message and the ordering of the different SMGF, SMGM, SMGV mail servers. who will deliver the message in one or more mailboxes.

Figure 2 - Configuration of the user profile Identification of the telephone line - Step 200 In the context of the implementation of the invention, the social network server SRS is designed to store (step 200), in the database DB, in the private data stored for a user, in association with an identifier of a user in the social network, an identification of at least one telephone line. This telephone line identification can be used to deposit, in the mailbox associated with this telephone line, a message intended for this user. Since telephone line identification is part of the private data of a given user, it is not known to the users who come into contact with him through the social network. This private data is a subset of his user profile, a kind of "private" profile of the user. Each user of the social network can declare, by means of a terminal connected to the Internet network RI, an identification of one or more telephone lines to be stored in the private data of his social network user profile. For this purpose, a web page accessible in the social network RS and provided by the social network server SRS, is loaded by a web browser executed by the terminal. The user then enters (step 200) the identification of the telephone line and requests the registration of this identification in the private data of his social network user profile. Each telephone line identification entered is then transmitted in step 200 by the user's terminal to the social network server SRS, to be stored in the database DB associated with this social network server SRS.

Such a telephone line identifier may be an identifier associated with a communication terminal in a communication network to which this terminal accesses. This identifier serves to identify the communication terminal in the communication network considered when establishing a communication with this communication terminal. Such an identifier may be a telephone number in a mobile or fixed network, or an IP address in a Voice over IP network. In some cases, a telephone line identifier may be associated with a plurality of communication terminals. This is particularly the case of terminals that are connected to a home gateway of a home network and they are several to be declared to receive a call to the same phone number. In this case, the gateway is able to notify a telephone call that it receives to any of the terminals thus declared. It is assumed in the remainder of the description that the users U1, U2, U3 and U4 each provided at least one telephone line identification, associated with their social network user identifier idpsl, idps2, idps3 and idps4 and / or idl. , id2, id3, id4: the identification of these phone lines are noted idcoml, idcom2, idcom3 and idcom4. It is further assumed that the U4 user has provided the social network SRS server with a second idcom4bis-rated telephone line. Telephone line selection rule - Step 210 When several telecommunication lines are defined for the same social network user identifier, the social network SRS server selects a telephone line based on at least one selection criterion. The social network server SRS is also designed to store (step 210), in a database DB associated with this server, in the private data of the profile of a social network user, in association with a user's identifier. in the social network, a telephone line selection rule defined from one or more selection criteria.

A first example of selection criterion is a defined criterion relating to at least one time slot: according to the time range during which a message deposit request is received, it will be a particular telephone line that will be chosen or else another telephone line. For example, for weekend message delivery requests, the private phone line will be selected. While for other requests, the professional phone line will be selected. A second example selection criterion is a criterion defined relative to the link existing in the social network between the user depositing a message and the user receiving this message. For example, if the relationship between these two users is professional in nature, then the chosen phone line will be a business phone line. On the other hand, if both users are declared as friends in the social network then the private phone line will be chosen.

By generalizing, each user having provided an identification of several telephone lines to be used for the message repository can thus define at least one criterion for selecting a telephone line. For this purpose, a web page accessible in the social network RS and provided by the social network server SRS, is loaded by a web browser executed by the user's terminal. The user then enters the parameters of one or more selection criteria, thereby defining a selection rule. Then the user requests the recording of these parameters in the private data of his social network user profile. Each parameter of a selection criterion is then transmitted during step 210 by the user's terminal to the social network server SRS, to be stored in a database DB associated with this social network server SRS. The selection criterion or criteria are, for example, dependent on the user receiving the message to be deposited and / or the user depositing the message to be deposited, the time range for filing the message, the geographical location of the recipient user, and / or the depositor of the message to be deposited, the link in the social network between the recipient user and / or the user depositing the message to be deposited, etc. A default phone line can also be designated by the user. Figure 3 - Method of depositing message. Various Embodiments of a Message Repository Request Method, Implemented by a User's Terminal, and a Method for Processing a Message Repository Request, Implemented by One or More Entities networks among the social network SRS server, the PFS messaging platform and / or the SMGF, SMGM, SMGV messaging servers are described with reference to Figure 3. Formulation of the message filing request - Steps 300 and 310 - First Embodiment with Prior Call Establishment Request In a first embodiment, the message repository request follows a call establishment request between a calling, calling user and at least one called user, selected from social network users. In case of non-response of at least one called user referred to in the call setup request, the message store request is sent automatically (step 300) by the network entity that processes the call setup request. phone, send for processing for example to the PFS messaging platform or directly to a mail server. In this first embodiment, the social network user identifiers of the users receiving the message to be dropped are obtained by the PFS messaging platform or the mail server: they correspond to the social network user identifiers provided with the request. of call set-up for which a non-response from the user has been detected. Formulation of the Message Deposit Request - Steps 300 and 310 - Second embodiment without prior call setup request. In a second embodiment, a user filing, wishing to file a message, formulates (step 300) expressly a message deposit request by using a message deposit request service to formulate his message deposit request. Information on the message deposit request is also transmitted, after, before or with the message deposit request or as constituent data of the message deposit request. The message store request and associated information is sent (step 310) from a user's terminal to the network entity that processes the message submission request: social network SRS server, PFS messaging platform, or one of the SMGF, SMGM, SMGV mail servers. This information contains in particular a social network user identifier of each recipient user of the message to be deposited and a social network user identifier of the filing user.

Several variants of this second embodiment are presented below. In a first variant of this second embodiment, the message depot request service is integrated into a social network service managed by the social network server SRS.

The settling user connects via his terminal to the social network server SRS to formulate his message submission request and provide the necessary information about the recipient user (s) and the message content. For example, the depositing user connects to a social web page and formulates his request using this web page. In particular, it selects (step 310) the users who are recipients of the message and / or enters the requested information: pseudonym of the recipient users, pseudonym of the depositing user to use to deposit the message, and optionally the content of the message to be deposited. .

In this first variant of this second embodiment, the web page used for the formulation of the message deposit request contains, for example, user search tools in the social network. For example, it is presented (step 310) to the user depositing a list of users of the social network to propose to this user to select one or more users in this list of users. This list of users includes for example all users connected with the user depositing through the social network, regardless of the nature of the link, or all users connected with the user depositing through the social network for which the link with the submitting user meets a defined criteria, or all users meeting a user-defined search criteria, etc. Thus a search engine of a user in the social network can be made available on the web page used to define a message deposit request. When the social network user identifier provided by the user filing for one of the message recipient users is not unique (in the case of a pseudonym used by several users), the social network server SRS has a unique social network user identifier that identifies each of the contacts chosen as recipients of the message by the submitting user and can therefore unambiguously identify those recipient users. The social network user identifiers of the users chosen by the user depositing as the recipient users of the message to be deposited are transmitted during the step 310 of the user's terminal to the social network server SRS.

In this first variant of this second embodiment, the information accompanying the message filing request, as formulated by the submitting user, contains at least: for the user depositing, a social network user identifier ( idpsl, for example for the user U1) under which the user depositing (U1) is known to the recipient users (the pseudonym, in general); for each recipient user, a social network user identifier (idps2, for example for the user U2) under which this recipient user (U2) is known to the user depositing (the pseudonym, in general). The information accompanying the message submission request will then be provided to the mail server that will deliver the message, to be stored in association with the content of the message. Additional information is then obtained by the social network server SRS to perform the processing of the message deposit request, for example: for the user filing, a telephone line identification (idcom1, for example for the user U1 ) stored in association with the social network user identifier provided in the message submission request, and, optionally, a unique social network user identifier (id1, for example for the user U1); for each recipient user, a telephone line identification (idcom2, for example for the user U2) stored in association with the social network user identifier provided in the message deposit request, and, optionally, an identifier unique user of social network (id2, for example for the user U2).

In this first variant of this second embodiment, the social network server SRS receives the message depot request and the information that accompanies it and transmits the request to the PFS messaging platform for processing. Step 330 of processing this message filing request is described in more detail below. This additional information will also be provided to the mail server that will be filing the message, to be stored in association with the content of the message, in particular to process a possible request for response to the message to be filed. In a second variant of this second embodiment, the message deposit request service is performed outside the social network. It is for example implemented by means of a Web page of an SRW Web server, managing a Web domain separate from that of the social network. It can be a web server, providing a message depot service for users of one or more social networks. This SRW Web server is then connected via the Internet network RI to the PFS messaging platform, in order to transmit to this platform a message deposit request formulated by a user via a web page.

Alternatively, instead of using an SRW Web server, the user who wishes to post a message loads a software application on his terminal: this application is designed to communicate over the Internet network RI with the PFS messaging platform platform to transmit to this platform a message filing request formulated by a user.

In this second variant of this second embodiment, the depositor user therefore connects to the PFS messaging platform by means of a terminal, by using a software application on his terminal or via an intermediate SRW Web server, then this user formulates his message deposit request. For example, it enters the requested information: pseudonym of the recipient users, pseudonym of the depositing user to use to deposit the message, and optionally the content of the message to be deposited. The identification of the social network in which the pseudonyms are defined may also be requested when the application and the SRW web server are used for several social networks. In this second variant of this second embodiment, the web page or the software application used for the formulation of the message filing request may also contain user search tools in one or more social networks. As in the first embodiment, it is proposed to the applicant user to select one or more users in a list of users of the social network. The PFS messaging platform or the SRW web server used for the formulation of the message deposit request will be in this second embodiment connected to the social network server SRS or to an associated database DB in order to have access to a list of users of the social network and to constitute a list of users of the social network to present to the user depositor.

When the social network user identifier provided by the user filing for one of the recipients of the message is not unique (in the case of a pseudonym used by several users), the user's authentication data depositor in the social network will then be requested from the user depositor, and then transmitted by the PFS messaging platform to the social network server SRS for identification of this user depositor. It will then be possible to identify users of the social network who are in contact with this user depositing in the social network and identify in a non-unique way the recipient users selected by this user, even if asked to the user to specify are choice if several users of the same pseudonym are in contact with the user depositing via the social network. The social network user identifiers of the users chosen by the user depositing as the recipient users of the message to be deposited are transmitted during the step 310 of the user's terminal to the PFS messaging platform. In this second variant of this second embodiment, the information accompanying the message deposit request, as formulated by the applicant user, contains at least: for the user depositing, a social network user identifier ( idpsl, for example for the user U1) under which the user depositing (U1) is known to the recipient users (the pseudonym, in general); for each recipient user, a social network user identifier (idps2, for example for the user U2) under which this recipient user (U2) is known to the user depositing (the pseudonym, in general). The PFS messaging platform is designed to communicate with the social network SRS server, or a DB database associated with that server, for additional information, including phone line IDs for which message repositories will be ordered. through the PFS messaging platform.

This additional information contains: for the filing user, a telephone line identification (idcoml, for example for the user U1) stored in association with the social network user identifier provided in the message deposit request, and, optionally, a unique social network user identifier (id1, for example for the user U1); for each recipient user, a telephone line identification (idcom2, for example for the user U2) stored in association with the social network user identifier provided in the message deposit request, and, optionally, a unique identifier user of social network (id2, for example for the user U2). In this second variant of this second embodiment, when the SRW intermediate web server or the application receives the message deposit request and the information that accompanies it, he / she transmits all this data to the PFS messaging platform for processing of the message filing request by this platform. Step 330 of processing this message filing request is described in more detail below. This additional information will also be provided to the mail server that will be filing the message, to be stored in association with the content of the message, in particular to process a possible request for response to the message to be filed.

In a third variant of this second embodiment, the message store request service is integrated into a messaging service of a telephone network operator. The user connects to this service by means of a telephone terminal. Unlike the first and second embodiments described above, where the PFS messaging platform receives and processes the message deposit request, it is here directly a SMGF, SMGM or SMGV mail server which receives the request for the deposit of the message. message and deals with it. The depositing user connects via his terminal to the mail server to formulate his message deposit request and provide the necessary information on the recipient user (s) and the message content.

For example, the depositing user connects to a voice server that is part of the mail server and then vocally provides the requested information: pseudonym of the recipient users, pseudonym of the depositing user to be used to deposit the message, voice content of the message to be submitted. The identification of the social network in which the pseudonyms are defined may also be requested.

The voice server then queries the social network server SRS or an associated database DB to identify, among the users of the social network who are in relation with the user depositing, the one or those whose pseudonym, as stored in the profile user, after vocalisation sounds like the one spoken by the user. The voice server then returns a voice stream containing the vocalized pseudonym (s) for which a similarity has been found. Then the user validates his choice of recipient user by confirming or reversing, for example by pressing a key, causing for example a DTMF signal transmission, or by pronouncing key words ("yes" or "no"). In this third variant of this second embodiment, the information accompanying the message deposit request, as formulated by the submitting user, contains at least: for the user depositing, a social network user identifier ( idpsl, for example for the user U1) under which the user depositing (U1) is known to the recipient users (the pseudonym, in general); for each recipient user, a social network user identifier (idps2, for example for the user U2) under which this recipient user (U2) is known to the user depositing (the pseudonym, in general).

The social network user identifiers of the users finally chosen by the user depositing as the addressee users of the message to be deposited are obtained at step 310 by the mail server. In this third variant of this second embodiment, the mail server that receives the message deposit request and the information that accompanies it, directly processes the message deposit request, without going through the PFS messaging platform. When the social network user identifier provided by the user filing for one of the recipients of the message is not unique (in the case of a pseudonym used by several users), the user's authentication data depositor in the social network will then be requested from the user depositor, and then transmitted to the social network server SRS for identification of this user depositor. It will then be possible to identify users of the social network who are in contact with this user depositing in the social network and identify in a non-unique way the recipient users selected by this user, even if asked to the user to specify are choice if several users of the same pseudonym are in contact with the submitting user.

The SMGF, SMGM or SMGV mail server will therefore have to interrogate, directly or via the PFS messaging platform, the social network SRS server or an associated DB database, in order to obtain information on the identifications of the telephone lines stored in memory. associating with each social network user identifier used in the message delivery request, in particular to identify the mailbox or boxes that will store the message to be dropped. This following information, obtained by the SMGF, SMGM or SMGV mail server for processing the message deposit request, thus contains: - for the depositing user, a telephone line identification (idcoml, for example for the user U1) stored in association with the social network user identifier provided in the message submission request, and, optionally, a unique social network user identifier (id1, for example for the user U1); for each recipient user, a telephone line identification (idcom2, for example for the user U2) stored in association with the social network user identifier provided in the message deposit request, and, optionally, a unique identifier user of social network (id2, for example for the user U2). This additional information will be stored in association with the content of the message, in particular to process a possible request for response to the message to be filed.

In this third variant of this second embodiment, it is therefore a mail server that receives and processes the message deposit request and the information that accompanies it. Step 330 of processing this message filing request is described in more detail below.

Saving the content of the message to be deposited - Step 320 The network entity (either the PFS messaging platform or an SMGF, SMGM or SMGV mail server) which receives and processes the message deposit request is in charge of obtaining the messages. data of the content of the message to be deposited as well as the information to be recorded in association with this message to be deposited. The information to be recorded includes in particular a social network user identifier of the user depositing the message to be deposited and a social network user identifier of the user or recipients of the message to be deposited. This information is provided in textual or vocal form, or even in the form of an image, to the SMGF, SMGM or SMGV mail server which makes the message deposit: it will be used to notify the recipient user (s) of the message delivery message. The additional information, to be registered in association with this message to be dropped (telephone line identifications, and, optionally, the social network user's unique identifiers and), are provided as a string to the SMGF, SMGM mail server. or SMGV which performs the message repository. This additional information is not known to the user and / or the recipient of the message and they are not accessible: they are stored by the mail server without ever being communicated to a user.

The message content recording step 320 may be performed, before or after or simultaneously with the steps 300 and 310 of formulating the message deposit request and sending the information that accompanies it. Regarding the recording of the content (text, voice or visual) of the message, several embodiments are possible.

In a first embodiment, usable when the network entity that receives the message deposit request is the PFS messaging platform, the message content is stored in a memory of the user's terminal and a data file incorporating this content is transmitted by this terminal to the social network SRS server which retransmits it to the PFS messaging platform, or is transmitted by this terminal directly to the PFS messaging platform. In a second embodiment, particularly suitable when the network entity is a SMGF, SMGM or SMGV mail server, the data of the message content is generated on the terminal (for example, with a microphone and sound capture software). ), the stream of captured data is transmitted in real time to this network entity to be registered by this network entity in a memory of this network entity.

Reception and Processing of the Message Deposit Request - Step 330 The network entity that receives a message submission request is the social network SRS server and / or the PFS messaging platform and / or a SMGM mail server, SMGF and SMGV. These network entities may in particular cooperate to perform this processing. This network entity receives a request to deposit a message intended for at least one recipient user, a social network user, who is identified by means of at least one social network user identifier accompanying the message filing request. The applicant user is also identified by means of a social network user identifier. This network entity also obtains, for each recipient user of the message to be dropped, an identification of at least one telephone line associated with this social network user identifier, for example by querying the social network server SRS. For each recipient user, the identified telephone line is a telephone line whose identification has been stored in association with a social network user identifier assigned to the recipient user concerned. When several telephone lines are stored in association with a social network user identifier assigned to a recipient user, the identified telephone line is selected, for example by the social network server SRS, among these different telephone lines according to minus a selection rule defined by the relevant social network user and stored by the social network server SRS. This selection rule for example uses a criterion relating to the link in the social network between the filing user and the recipient user concerned. In another example, this criterion is a criterion relating to the user depositing the message. In step 340, the message is placed in a mailbox associated with the telephone line thus identified.

Are stored in association with the message deposited, the following information: - for the user depositing, a social network user identifier (idps1, for example for the user U1) under which the user depositor (U1) is known recipient users (the pseudonym, in general) and a telephone line identification (idcom1, for example), stored in association with this social network user ID; for each recipient user, a social network user identifier (idps2, for example for the user U2) under which this recipient user (U2) is known to the filing user (the pseudonym, in general) as well as a telephone line identification (idcom2, for example), stored in association with this social network user identifier. The information stored in association with the message deposited may optionally contain: for the user depositing, his unique social network user identifier (id1, for example for the user U1); for each recipient user, his unique social network user identifier (id2, for example for the user U2). Finally, a notification of deposit of the message is sent to at least one terminal associated with the identified telephone line, the notification comprising a social network user identifier assigned to the filing user: the user identifier of The social network that is sent in the notification is the one under which the filing user is known to the recipient users in the social network (usually this is his nickname). In the embodiments where it is a mail server that receives the message deposit request, this SMGM, SMGF and SMGV mail server itself files the message in the mailbox identified by the associated telephone line. and recording the provided data in association with the message to be deposited. In embodiments where the social network SRS server receives the message submission request, it transmits this request to the PFS messaging platform with all information necessary for its processing: network user credentials social network, and an identification of the telephone lines concerned. The PFS messaging platform then processes the message deposit request, as in the case described below, where it is the PF that receives the message deposit request.

In embodiments where the PFS messaging platform receives the message submission request, this PFS messaging platform is designed to require the message to be mailed to a mail server and to communicate with the different servers. SMGM, SMGF and SMGV network messaging services, for remotely controlling the functions of these messaging servers, in particular the functions of message storage and data recording in association with the messages deposited. The SMGM, SMGF and SMGV network messaging servers each have a control interface for this purpose, making it possible to remotely control certain functions of these messaging servers, in particular the functions of message storage and data recording in association with the posted messages. This control interface is for example a programming software interface (API, Application Programming Interface), for example carried out as a Web service.

This control interface can also be implemented by a coupling module, integrating a modem for receiving telephone call notifications and establishing a telephone link. In a known manner, for the circuit-mode telephone lines, the telephone number of the telephone line of the destination user is composed so as to establish a telephone connection with the network messaging server of this telephone line. Via this telephone link, DTMF commands and / or a telephone stream can then be transmitted to control a record by the mail server of a message in the mailbox of the specified telephone line from the dialed telephone number.

In other network messaging services, a telephone link is established with the mail server by dialing a telephone number dedicated to the messaging service. Then the telephone number of the recipient's telephone line is dialed to select the recipient's message box. Finally, the message is saved in the inbox of this recipient user by sending the message data via the telephone link thus established. In the case of a network voice mail, the message is recorded in the network mail server, in the phone line mailbox: the recorded message can then be listened to by establishing a telephone connection with this network mail server and listening to the audio stream transmitted through this telephone link. In the case of a fixed answering machine, the message is recorded in the answering machine and the return of the message can be triggered by command entry on this answering machine. In other network messaging services, for example the VoIP network RV, a link is established with the mail server, then an identification of the telephone line concerned by the message deposit to be performed is transmitted via the link thus established.

Whatever the technology used by the network messaging services, the PFS messaging platform is connected to these SMGM, SMGF and SMGV mail servers and is designed to command the posting of a message to at least one of these mail servers by using command interfaces of these servers. The PFS messaging platform is also designed to transmit to these mail servers, either in the actual content of the message (in voice, text and / or visual form), or as data to be stored in association with the content of the message, the social network user identifier of the user depositing the message and the social network user identifier of the user (s) receiving the message: these social network user identifiers will be used in particular to notify the user (s) of the message recipient users of the message repository.

This information includes in particular a social network user identifier of each of these users, for example the pseudonym of each of these users. This information will then be used for the notification of the deposit of the message in a mailbox and / or for the return of the message and / or for the response to a message deposited. When the pseudonyms of the depositing and receiving users of a deposited message are unique and make it possible to identify each one a social network user in a non-unique way, it is not necessary to memorize in addition, in association with the deposited message, a unique identifier for each of these users. If not, a unique social network user ID will be stored in addition to each user's nickname to make future access to information on each of these users possible, for example by querying the social network SRS server. : in particular to obtain from this unique identifier a telephone line identification declared by a social network user in the data of his user profile, for a telephone line to be used for the message deposit. In one embodiment, when the receiving mail server of the message to be stored is not designed to store information on the user depositing a message other than a telephone number of the user depositing the PFS messenger voices the pseudonym of the depositing user (or even that of the recipient user) and generates an audio message content integrating both the message itself and an introduction to this message containing the social network user identifier in vocalized form. This introduction is for example a sentence of the type "message from X" and / or "message to Y", where X, Y are respectively the pseudonyms of the depositing and receiving users. The audio message content thus constituted is intended to be returned in its entirety to each recipient user. The PFS messaging platform is also designed to transmit to these mail servers, as data to be stored in association with the content of the message, the telephone line identification associated with the filing user and a telephone line identification associated with the message server. each recipient user, and, optionally, the unique social network user identifier of the user depositing the message and the unique social network user identifier of the recipient user (s) of the message. In addition, in order to allow the PFS messaging platform to process a request to deposit a response message, in response to a message which it processed the filing request, the PFS messaging platform stores for each request of message store (or response message), the following information: - the social network user identifier of the user depositing the message and the social network user identifier of the user or recipients of the message, the telephone line identification associated with the filing user and a telephone line identification associated with each recipient user, and, optionally, the unique social network user identifier of the user depositing the message and the unique social network user ID of the recipient user (s) of the message.

Notification of Message Delivery in a Message Box - Step 350 The SMGM, SMGF and SMGV network messaging servers each have a notification module for notifying each recipient user of a message of the posting of this message in the message box. associated with a telephone line. In a known manner, this notification usually results in the case of a mobile network by the triggering of a telephone call on the associated telephone line (call of a voice mail server, which proposes the consultation of the message or messages deposited) and / or by sending a message, for example by sending a short message (SMS, Short Message Service) to the terminal or one of the terminals associated with the telephone line. In the case of a fixed answering machine, the notification usually results in a light signal on the answering machine to signal the recording of a new message in this answering machine. In the message depositing method according to the invention, it is furthermore intended to inform the recipient user of a message on the identity of the filing user and / or other possible recipients of the message deposited by means of a social network user identifier associated with respectively one of these users. The social network user identifier may be included in voice form in a voice notification and / or in the actual content of the message if this message is a voice message. As an alternative or in addition, this social network user identifier can also be sent in text form in the message deposit notification when this notification is a text format notification (SMS in particular). Other notification methods are also applicable, for example application notifications, received and processed by a dedicated software application implemented on the receiving terminal of the notification. In addition, or as an alternative to a notification sent by the SMGM, SMGF and SMGV network messaging server, the PFS service platform sends a notification to at least one terminal associated with the telephone line of each user receiving the message. This message is for example a short message service (SMS) with an identification of this PFS service platform (for example, a specific short number identifying the entity issuing the message and / or a commercial name of the service of deposit of message embedded in the body of the short message) and / or message content which indicates the identifiers of the depositing and / or receiving users. For example, the body of the short message contains the following sentence: "The orange messaging service notifies you that a message from" idpsl "is being delivered to your inbox; call 888 to view this message ».

Exemplary embodiment of the message depositing method The user filing U1 formulates a request to deposit a message M1 for destination users U2 and U4. For this purpose, the user U1 connects to a specific web page of the social network RS: the user U1 uses his terminal TA and establishes by means of this terminal TA a connection with the social network server SRS. The terminal TA receives a web page that it displays on a screen of this terminal TA. This page includes a list of users of the social network, preferably users known to the user U1 and / or in relation to this user U1 through the social network: these users are identified in this list by their pseudonym. The user U1 selects the addressee users of the message to be dropped: in this case the users U2 and U4, which U1 knows under their pseudonym idps2 and idps4. Then the user U1 composes the message M1 to be dropped. This message may be a text message that the user U1 enters on his terminal TA in the web page that is displayed on this terminal. This message can also be a pre-recorded audio and / or video file on this terminal that the user U1 selects by means of an interface element (button, menu, etc.) displayed in the web page that is displayed on this terminal. terminal. Alternatively, the user records a text, voice and / or video message on his terminal TA.

Then the user U1 validates the message deposit request: the user U1 clicks for example on a button or hyperlink that is presented in the web page displayed on the terminal TA to trigger the sending and processing of the request for message deposit. The social network SRS server then triggers the transmission of the message submission request to the PFS messaging platform.

This message submission request contains a social network user identifier (in this case, idpsl) of the user depositing U1 and a social network user identifier for each of the destination users U2 and U4 (in this example). occurrence, idps2 and idps4). The message submission request is further accompanied by the content of the message to be deposited or is followed by a transmission of this content. This content is in textual, audio and / or video form, or any combination of these forms, depending on the possibilities of the mail server to store the message M1. The PFS messaging platform interrogates the social network SRS server to obtain, for each user receiving the message, an associated telephone line identification from the social network user identifier contained in the message deposit request. The social network SRS server then transmits to the PFS messaging platform the idcom2 and idcom4 telephone line identifiers stored in association with the idps2 etidps4 social network user identifiers respectively. It is therefore assumed here that a selection rule, defined by the U4 user, has caused the social network server SRS to select the idcom4 telephone line identifications rather than idcom4bis.

Alternatively, instead of the PFS messaging platform querying the social network SRS server, the social network SRS server provides these phone line identifications to the PFS messaging platform as soon as it receives the request formulation. message store and forward them to the PFS messaging platform. The PFS messaging platform then connects to the mail server of the idcom2 telephone line, that is to say the SMGM mail server. If the receiving mail server of the message to be dropped accepts only certain forms of message, the PFS messaging platform converts the content of the message into a form accepted by the receiving mail server. For example, if this mail server only accepts voicemails, the text messages will be voiced and the video content of the message to be dropped will be deleted. Finally, the PFS messaging platform orders the filing of a message with the SMGM mail server, in the mailbox associated with the idcom2 phone line. The SMGM mail server stores the message M1, in particular the content of this message, and memorizes in association the following information: for the user depositing U1, a social network user identifier (idpsl) under which the user depositing U1 is known to recipient users, a telephone line identification (idcom1), stored in association with this social network user identifier, and optionally a unique social network user identifier (id1); for each recipient user U2, U4, a social network user identifier (idps2, idps4) under which these recipient users are known to the filing user, a telephone line identification (idcom2, idcom4) stored in association with this social network user identifier, and optionally a unique social network user identifier (id2, id4). The SMGM mail server then sends a message deposit notification to the T2 phone associated with the idcom2 line: this notification results in a call from the voice server of the mobile network messaging RM. The voice message transmitted by the voice server contains in voice form the social network user identifier of the user depositing U1, or even that of the other destination user U4. In an alternative, the PFS messaging platform sends, in addition to the notification sent by the mail server, a notification message in the form of, for example, a short message service (SMS) containing in textual form the user identifier. of the user's U1 user network, or even that of the other U4 recipient user. For example, the body of the short message contains the following sentence: "The orange messaging service notifies you that you have sent a message from" idpsl "to your inbox, - dial 888 to view this message". Then the PFS messaging platform connects to the mail server of the idcom4 telephone line, i.e., the SMGM mail server.

If the receiving mail server of the message to be dropped accepts only certain forms of message, the PFS messaging platform converts the content of the message into a form accepted by the receiving mail server. For example, if this mail server only accepts voicemails, the text messages will be voiced and the video content of the message to be dropped will be deleted. Then the PFS messaging platform orders the posting of a message to the SMGM mail server in the mailbox associated with the idcom4 phone line. The SMGM mail server sends a message deposit notification to the T4 phone associated with the idcom4 line: this notification results in a call from the voice server of the mobile network messaging RM. The voice message transmitted by the voice server contains in voice form the social network user identifier of the user depositing U1, or even that of the other destination user U2. The user U4 is notified in the same way as the user U2.

Figure 4 - Consultation of a message filed Various embodiments of a message consultation request method, implemented by a user's terminal, and a method for processing a message consultation request implemented by one or more network entities among the social network SRS server, the PFS messaging platform and / or the SMGF, SMGM, SMGV messaging servers are described with reference to FIG. of a consulting user - Step 400 A user receiving a message can, in a known manner, consult and / or listen and / or view the content of the message that is deposited in his mailbox.

A message consultation request is formulated (step 400) by the user and received (step 400) by a network messaging server or a fixed answering machine. When the message is deposited with answering machine storing the messages of a mailbox of a telephone line, the consultation of the message is performed by using this answering machine, for example actuation of a dedicated key, triggering the return of all stored messages (or only messages not yet viewed) in this answering machine. When the message is deposited with a network messaging server, the consultation of the message requires the establishment of a communication link between this network messaging server and a terminal. If the network messaging server is for voice mail for a telephone line, the communication link will be a telephone link and a two-way audio stream will be transmitted through this communication link between the messaging server and the terminal used to establish the link. Communication. If the network messaging server is a webmail for a VoIP telephone line, the communication link may be an IP link and an audio stream will be transmitted through this communication link to the terminal used to establish the communication link. In the context of the invention, the messages being memorized in association with a social network user identifier for the user depositing the message and for the recipient user or users of the message, new message consultation possibilities are offered to the users. users. These new possibilities concern in particular the possibility of selecting messages to be consulted and / or of defining the order in which the selected messages will be restored.

The social network user identifiers of the depositing or recipient users stored with a message may in particular serve as criteria for selecting or sorting messages facilitating the consultation of the messages. For example, the user has interaction means (telephone keys triggering a sending of DTMF signals to a voice mail server, or user interface elements in a web page for a web server triggering the sending of messages). a Web request, or even a button on an answering machine, etc.), with the mail server to formulate and specify its message consultation request by selecting the message or messages it wishes to consult. For this purpose, the user may have to provide, with his request for consultation, a social network user identifier used to identify the message or messages subject to the request for consultation and / or the order in which these messages must be presented to the consulting user. According to a first example, the message consultation request concerns at least one message submitted by a social network user whose social network user identifier is specified by the social network user from which the message consultation request originates. According to a second example, the message consultation request concerns a plurality of messages to be restored successively according to an order specified by the social network user from which the message consultation request originates. The specified order may indicate, for example, that the messages will be sorted based on the user's social network user identifier of the requesting user, in alphabetical order of identifier. According to a third example, the message consultation request concerns at least one message intended for a social network user whose social network user identifier is specified by the social network user from which the request for consultation of the social network user originates. message. All combinations of these different examples are conceivable. Consequently, following the establishment of the communication link with the mail server, this mail server receives a message consultation request from a terminal of a consulting user and identifies on the basis of this request at least a message filed by or intended for this consulting user, by means of a message filing method and / or by means of a response method to a message as described in this document. The mail server then proceeds to the return of at least part of the content of at least one identified message.

When the consultation request relates to a plurality of messages, and a restitution order has been specified by the user, the mail server performs the return of these messages in the specified order.

For this purpose, the messaging server sends to the terminal of the consulting user, via the established communication link, a data stream containing at least part of the content of at least one of the messages of said plurality of messages in accordance with at the specified order. The terminal receives the data stream and proceeds to the local rendering of the sound, video and / or text contained in this data stream. Restitution of social network user identifiers - Step 410 In addition, when consulting a message filed with a SMGM, SMGF and SMGV network messaging server, it is furthermore intended to inform the recipient user a message about the identity of the submitting user and / or other possible recipients of this message by means of the social network user identifier (s) stored in association with the message (s) subject of the request consultation. This social network user identifier may be a pseudonym of this user depositing and / or recipient so as not to disclose the real identity of this user depositor and / or recipient. For this purpose, the messaging server transmits to the terminal of the consulting user, through the established communication link, the social network user identifier of the submitting user and / or the recipient user or users. each message. The terminal receives the data stream and proceeds to the local retrieval of this or these social network user identifiers. If a social network user identifier is transmitted to the user's terminal in text form, this identifier can simply be displayed on the terminal of the consulting user or be vocalized. If a social network user identifier is transmitted to the terminal of the consulting user in voice and / or visual form, this terminal can simply return the audio and video content it receives in order to restore this or these identifiers. social network user for the consulting user. In one embodiment, so that the message storing solution is compatible with the existing messaging systems, each social network user identifier can be included in voice form in the voice content of the recorded message and then be restored. with the content of this message, for example before the content itself of this message.

The fact of informing the recipient user of a message on the identity, in the social network, of the user filing and / or recipient allows a message relationship between these users through a box of messaging, without these users having previously needed to exchange their telephone numbers and without prior authorization being required from these users to share these phone numbers.

The telephone line identifications that are stored with a message are, however, never transmitted to a user who is the recipient or depositor of a message while viewing the message and intended only for processing a possible request for the filing of a reply message. Finally, all or part of the message consulted is transmitted to the terminal of the consulting user to be returned by this terminal (step 420).

FIG. 5 - Deposit of an answer message to an earlier message Various embodiments of a method for requesting a response message depot, implemented by a user's terminal, and a method for processing a message an answer message filing request, implemented by one or more network entities among the social network SRS server, the PFS messaging platform and / or the SMGF, SMGM, SMGV messaging servers, are described by reference to FIG. 2. Each recipient user U2, U4 of a message M1 deposited by a user U1, said initial message, may decide to reply to this message M1 after having consulted this message, or even before having consulted this message. As a result, the steps of the method of requesting a response to a message and those of the method of processing a request for filing a response to a message are implemented before or after consulting a message. In addition, the message consultation method described above is also applicable to message response messages: each response message can be consulted according to the message consultation method described with reference to FIG. 4.

Request for deposit of a reply message to an earlier message - Step 500 and 510 To formulate a request to deposit an answer message to an earlier message (that this previous message is an initial message, that is to say say a first message of a series of messages that is not the response of any message, or a message of response to a message), the recipient user U2 or U4 connects by means of a terminal to either the server of messaging from which the previous message was deposited, either directly to the PFS messaging platform. This user formulates (step 500 and 510) then, by means of his terminal, a request for the filing of a reply message, in a manner identical to that described above with regard to FIG. 3 for a request to deposit a message. initial message. Steps 500 and 510 therefore respectively include the characteristics of steps 300 and 310 described above. Finally, a request to send a response message is sent to step 510 from a user terminal to a network entity (PFS messaging platform or one of the SMGF, SMGM, SMGV mail servers) for processing. Information about the response message submission request is also transmitted after, before or with the response message submission request or as constituent data of the response message filing request. This information is used to identify the recipient user (s) of the response message to be filed among the recipient user (s) of the previous message and the user depositing the previous message. Unlike an initial message repository where the user can choose any recipient (see step 310), the user requesting to file a response message selects (step 510) from the users depositing and receiving the previous message, those who will be receiving the response message, for example from a list of users that is provided to him in a web page or user interface of an application or from a menu that is presented to him by the voice server who receives this request. In addition, when several messages have been stored in a mailbox of the consulting user, the consulting user will have to select the message to which he wishes to reply. By default, it is the last message consulted or the message being consulted which will be selected as the previous message for which a response message is to be deposited.

The network entity (either the PFS messaging platform, or an SMGF, SMGM or SMGV mail server) that receives and processes the response message filing request is in charge of obtaining the data of the message content to be dropped as well as as the information to be recorded in association with this message to be deposited. The information to be recorded includes a social network user identifier of the user depositing the response message to be dropped, and secondly, a social network user identifier of the user (s) receiving the response message to be deposited. . This information is provided in text or voice form to the PFS messaging platform. When the message to be deposited is a response to a previous message, the information to be recorded in association with this message to be deposited can be deduced from the information recorded with the previous message. For example, if the user U2 asks to deposit a response message to a previous message M1 filed by the user U1 to the user U2 and U4, the user identifiers of the user depositing this message of answer is the identifier of the user U2 registered in association with the message M1 and the identifiers of the recipient users are the identifiers of the users U1 and U4 registered in association with the message M1. As in the case of the filing of an initial message, described with reference to FIG. 3, the network entity that receives and processes the message deposit request in response to an initial message proceeds to the identification of a telephone line associated with a social network user identifier assigned to the user depositing the initial message.

In particular, the identified telephone line is a telephone line whose identification has been stored in social network user profile data in association with a social network user identifier assigned to the recipient user concerned. When multiple telephone lines are stored in association with a social network user identifier assigned to a recipient user, the identified telephone line is selected from among these different telephone lines according to a selection rule. This selection rule for example uses a criterion relating to the link in the social network between the user depositing the response message and the recipient user concerned. In another example, this selection rule uses a criterion relating to the user depositing the message. Submission of the reply message - Steps 520 to 540 Then the message is deposited in a mailbox associated with the identified telephone line. The filing of a response message is implemented in the same manner as the filing of an initial message, as described with reference to FIG. 3, in steps 320 to 340. In the embodiments where a server of message that receives the request to deposit the response message, this SMGM, SMGF and SMGV mail server itself proceeds to the filing of the message in the mailbox identified by the associated telephone line and the recording of the data provided in association with the message to drop. In embodiments where the PFS messaging platform receives the request for the delivery of the response message, this PFS messaging platform is designed to require the message to be mailed to a messaging server and to communicate with the messages. different SMGM, SMGF and SMGV network messaging servers, in order to remotely control, as already described for the case of the filing of an initial message, the functions of these messaging servers, in particular the functions of message storage and registration of data in association with the messages deposited. In all these embodiments, is memorized, in association with the deposited message, a social network user identifier of the user and / or the recipient user or users. It should be noted that if the previous message was intended for several recipient users, the reply message to this previous message may be intended only for the user depositing the previous message and not for the other recipient users, or only for some of the recipient users. In this case, the user requesting the filing of a response message provides an identification of the recipient user (s) of his message to reply. By default, all other recipients of the previous message will also receive the reply message as well as the user of the previous message. In addition, because it is a repository of a response message to an existing prior message, a stamp is stored by the PFS messaging platform and / or by the mail server in association with the message. response to indicate that this response message is a response message to an earlier message and / or to identify the previous message. A message identifier is for example stored with each message deposited, representative of a possible previous message whose message is a reply, this identifier taking a specific value when the message is not a response message.

Thus, when a request for consultation of the reply message is received, it is possible to identify the previous message whose response message is a response and to propose to the consulting user of the reply message to also consult the previous message. even if the mailbox storing the previous message and the reply message is not the same. A stamp may also be stored by the PFS messaging platform and / or by the messaging server in association with the previous message to signify that a response message has been filed for this prior message and / or to identify at least one message response filed later. Thus, when a request for consultation of the previous message is received, it is possible to determine whether a response message has been filed and, if so, to propose to the consulting user of the previous message to also consult the response message. .

Notification of the filing of the response message - Step 550 After recording the response message and the associated information, the recipient user (s) of the response message are notified of the filing of this response message. The method described above for step 350 of notification of deposit of an initial message applies identically to the case of the notification of the deposit of a response message. In the response message depositing method according to the invention, it is in particular intended to inform the recipient user of a message on the identity of the submitting user and / or other possible recipients of the reply message. deposited by means of a social network user identifier associated with one of these users respectively.

The social network user identifier may be included in voice form in a voice notification and / or in the actual content of the message if this message is a voice message. As an alternative or in addition, this social network user identifier can also be sent in text form in the message deposit notification when this notification is a text format notification (SMS in particular). Other notification methods are also applicable.

When the user depositing a response message is identified from an anonymized identifier of social network user, his real identity is not communicated to the users of this message. In addition, the reply message deposit notification may contain information on the fact that the message being posted is a reply message and / or one or more information about the previous message (date and time of the message, user depositing and / or recipient users) whose response message is an answer. Successive replies to an initial message The message depositing method just described can be used several times, recursively to deposit a response message to a response message. For issues of limitations of message storage resources, the number of levels of response messages to a given initial message may be limited.

At each request to send a response message, the network entity that receives the request identifies a telephone line associated with a social network user identifier assigned to each receiving social network user of the response message, and then requests the submission of the response message, in a mailbox associated with the identified telephone line and sending a notification of deposit of the message to at least one terminal associated with the identified telephone line. When a user requests to file a response message to a previous message, he can specify what is the previous message for which he wants to proceed with the filing of response message. In particular, if several response messages have been successively filed for the same initial message, whether in direct response to this initial message or in response to a response message of this initial message, the user can select a message among those where it is either the filing user or the receiving user. For this purpose, a graphical interface can be proposed to allow it an intuitive visualization of the succession of the response messages. Or, there may be provided a voice server that presents the user with the various options and asks the user to select one by pressing a key of the terminal used for the request for filing response message. In one embodiment, the notification of the deposit of a response message informs each recipient user of this response message on the various possibilities of consulting messages that are proposed to him: - either to consult a single particular message, chosen by the recipient user, among these various messages present in his mailbox; or to consult a particular message among these different messages, then to consult the message or messages of response to this message; or to consult a single particular message among these different messages, then to consult the messages of response to this message and it iteratively until the last level of response - to consult a single particular message among these different messages, then to view all messages posted after this particular message; - either to consult all the messages coming from a particular user and / or of which one is the recipient, - or to navigate the different messages to listen to the messages in the order that suits him.

Exemplary embodiment of the message look-up method and the response message deposit method It is assumed by way of example that a message M1 has been deposited by the user U1 in several mailboxes of several user recipients U2, U4. . The message M1 is stored in association with: the identifiers id1, idpsl, idcoml for the user U1, user depositor, identifiers id2, idps2, idcom2 for the user U2, user addressee, the identifiers id4, idps4, idcom4 for the user U4 user, recipient user. In the case of a response from the user U2 to a message M1 filed by the user U1, the response is stored as message M2 (M1) in the user's mailbox U1 according to one of the message deposit methods described above. The message M2 (M1) is searchable by the user U1 from his mailbox. Optionally, the message M2 (M1) deposited by the user U2 can also be consulted by the user U2 from his own mailbox, that is to say the message box in which the message M1 has been deposited. . The message M2 is stored in association with: the identifiers id1, idps1, idcom1 for the user U1, recipient user, the identifiers id2, idps2, idcom2 for the user U2, user depositor, the identifiers id4, idps4, idcom4 for the user U4 user, recipient user. Similarly, in the case of a response from the user U4 to a message M1 filed by the user U1, the response is stored as message M4 (M1) in the user's mailbox U1 according to one of the methods of message depot described above. The message M4 (M1) is viewable by the user U1 from his mailbox. Optionally, the message M4 (M1) is viewable by the user U4 from his own mailbox. The message M4 is stored in association with: the identifiers id1, idps1, idcom1 for the user U1, recipient user, the identifiers id2, idps2, idcom2 for the user U2, user addressee, id4, idps4, idcom4 identifiers for the user U4 user, user depositing.

In one embodiment, when the initial message M1 has several destination users U2 and U4, the response message M2 (M1) can be consulted by all the destination users U2, U4 of the initial message M1, each of the recipient users being able to consult the message M2 (M1) from his own mailbox. For example, the user U4 is the recipient user of the response message M2 (M1), as is the user U1.

As an alternative, the user U2 can specify during the request to deposit the response message M2 (M1) that only certain users receiving the initial message M1 will receive in their mailbox the response message M2 (M1).

Claims (21)

REVENDICATIONS1. A consultation method comprising for a terminal: a step of sending (400) a request for consultation of at least one message deposited at the request of a user of a social network, said user depositing, in a box of messaging of a telephone line whose identification is memorized in association with a social network user identifier of a social network user, said consulting user, - for at least one first message filed, a reception and retrieval step (410, 420) by the terminal of a social network user identifier assigned to the user depositing in a social network and at least a portion of the content of the first message. 2. The consultation method according to claim 1, in the user's social network user identifier is an identifier under which the user depositor is known to the user consulting in the social network and / or the The user's social network user identifier is an identifier under which the consulting user is known to the user depositing in the social network. 3. A consultation method according to claim 1 or 2, wherein the user's social network user identifier is an identifier, for example a pseudonym, not disclosing the actual identity of the user depositing and / or the social network user identifier of the consulting user is an identifier, for example a pseudonym, not disclosing the real identity of the consulting user. 4. A consultation method according to any one of the preceding claims, wherein an identification of the telephone line is stored in association with a social network user identifier assigned to the consulting user, under which the consulting user is known. of the user depositing in the social network. A consultation method according to any one of the preceding claims, wherein the identification of the telephone line is declared by the consulting user in this user's social network user profile data which is not accessible. to the user depositing through the social network. 6. The consultation method according to claim 1, wherein the first message has also been deposited in a mailbox of another telephone line whose identification is stored in association with a social network user identifier of a user. social network, said recipient user, the method comprising a step of reception and retrieval by the terminal of a social network user identifier of the recipient user. 7. The consultation method according to claim 1, wherein the consultation request message is for consulting a plurality of messages to be restored successively in an order specified by the consulting user, the method comprising, for each message of said plurality of messages processed in accordance with the specified order, a step of reception and retrieval by the terminal of a social network user identifier of the user depositing this message and at least part of the content of this message. 8. A method of processing a message consultation request, the method comprising: a reception step (400), originating from a terminal, of a request for consultation of at least one message deposited on request of a user of a social network, said user depositor, in a mailbox of a telephone line whose identification is stored in association with a social network user identifier of a social network user, said user consultant for at least one first message deposited in said mailbox, a step of sending (410, 420) to said terminal a social network user identifier of the user depositing the first message and at least one a part of the content of the first message, said sending triggering a return by the terminal of said social network user identifier and the portion of the content. A method of processing a message lookup request according to claim 1, wherein a message dropped in said mailbox is stored in association with a user's social network user identifier and an identifier. social network user of at least one user of this message. The method of processing a message consultation request according to claim 9, comprising a step of identifying at least one message deposited in said mailbox by a user whose social network user identifier is a user. indicated by the consulting user. 11. A method of processing a message consultation request according to claim 9 or 10, comprising a step of identifying at least one message deposited in said mailbox to a recipient user including a login identifier. Social network user is indicated by the consulting user. A method of processing a message consultation request according to any one of the preceding claims, the method comprising - a step of identifying a message which is a response message to the first message or whose first message is a response message, - a step of sending information to the terminal to signal a possibility of consulting the identified message, - a step of sending to the terminal of a social network user identifier of the user depositor of the identified message, triggering a return by the terminal of said social network user identifier. 13. A method of processing a request to deposit a response message, the method comprising - a processing phase, by means of a method of processing a message consultation request according to any of the claims. 8 to 12, a request for consultation of a first message filed, at the request of a social network user, said user depositor, to a social network user, said recipient user in a mailbox of a telephone line, - a step of receiving (510) a request to deposit a second message, in response to the first message, - a step of identifying (530) at least one second telephone line associated with the social network user identifier assigned to the user depositing the first message, - a step for triggering, for at least one said second identified telephone line, a depot (540) of said second message in a box message associated with the identified second telephone line and sending (550) a notification of deposit of said second message to at least one terminal associated with the identified second telephone line, the notification comprising a network user identifier assigned to the user who requested the submission of the second message. A method of processing a response message submission request according to claim 13 comprising: - a step of sending social network user identifiers for each social network user who is either the user of the first message, a user receiving the first message, - a step of receiving a selection information, identifying the recipient user (s) of the second message among the user depositing the first message and the recipient user (s) of the first message. A method of processing a request for response message depot according to claim 13 or 14, comprising - a step of receiving a request to store a third message, in response to the second message, - a step of identifying at least one third telephone line associated with the social network user identifier assigned to the user filing the second message, a step for triggering, for at least one said third identified telephone line, a depot of said third message in a mailbox associated with the identified third telephone line and sending a notification of deposit of said third message to at least one terminal associated with the identified third telephone line, the notification comprising a user identifier of a social network assigned to the user who has requested the posting of the third message. 16. A method of depositing a response message, the method comprising - a consultation phase, by means of a message consultation method according to any one of claims 1 to 7, of a first message deposited, on request of a social network user, said user depositor, to a social network user, said recipient user, in a mailbox of a telephone line, - a step of sending (510) a request for deposit of a second message, in response to the first message, said initiating filing request, for a second telephone line associated with the social network user identifier assigned to the user depositing the first message, a repository ( 540) of the second message in a mailbox associated with the second telephone line and a sending (550) of a filing notification of the second message to at least one terminal associated with the second telephone line, the notification comprising a social network user identifier assigned to the user having requested the posting of the second message. 17. Recording medium readable by a data processor on which is recorded a program comprising program code instructions for performing the steps of a method according to one of the preceding claims. 18. Terminal comprising - a module for sending (400) a request for consultation of at least one message deposited at the request of a user of a social network, said user depositing, in a mailbox of a phone line whose identification is stored in association with a social network user identifier of a social network user, said consulting user, - a reception and retrieval module (410, 420), by the terminal, of a social network user identifier assigned to the user depositing in a social network and at least a portion of the content of the first message. Terminal according to claim 18, comprising a sending module (510) for a request for the deposit of a second message, in response to the first message, said request for filing a response message that triggers, for a second line. telephone associated with the social network user identifier assigned to the user depositing the first message, a depot (540) of the second message in a mailbox associated with the second telephone line and a sending (550) of a deposit notification of the second message to at least one terminal associated with the second telephone line, the notification comprising a social network user identifier assigned to the user having requested the repository of the second message. 20. Network entity, comprising: - a reception module (400), from a terminal, a request for consultation of at least one message deposited on request of a user of a social network, said user depositing, in a mailbox of a telephone line whose identification is stored in association with a social network user identifier of a social network user, said consulting user, - a sending module (410, 420 ) to said terminal of a social network user identifier of the user depositing the first message and at least part of the content of the first message, a said sending triggering a restitution by the terminal of said network user identifier social and part of the content. Network entity according to claim 20, comprising: - a module (510) for receiving a request for the deposit of a second message, in response to the first message; - an identification module (530) of at least a second telephone line associated with the social network user identifier assigned to the user depositing the first message, - a module for triggering, for at least one said second identified telephone line, a repository (540) of said second message in a mailbox associated with the identified second telephone line and a sending (550) of a notification of deposit of said second message to at least one terminal associated with the identified second telephone line, the notification comprising a user identifier assigned to the user who requested the second message.