Messaging service
10547572 ยท 2020-01-28
Assignee
Inventors
Cpc classification
H04M3/42008
ELECTRICITY
H04L63/0407
ELECTRICITY
H04L51/02
ELECTRICITY
H04W12/02
ELECTRICITY
H04L51/224
ELECTRICITY
H04L51/42
ELECTRICITY
H04L51/046
ELECTRICITY
International classification
H04M3/53
ELECTRICITY
Abstract
A method is provided for allocating a messaging mailbox located in a communications network to a user. The method performs the following actions in a messaging mailbox management device: receiving from a communication terminal, via the communications network, a request for a messaging mailbox, the request including user identification information, the identification information being different from a contact identifier of the user that can be reached on a communications network of a telecommunications operator to which the user subscribes; recording the received identification information in association with a messaging mailbox identifier; and sending a message in reply to the request, via the communications network, to the communication terminal. The message includes the messaging mailbox identifier.
Claims
1. A method comprising: allocating on the fly a messaging mailbox located in a communications network to a user, wherein allocating comprises the following actions performed by a messaging mailbox management device: receiving from a communication terminal of a user unknown by said messaging mailbox management device, via the communications network, a request for a messaging mailbox, said request comprising only one user identification information, said identification information being different from an email of said user and from a contact identifier of said user that can be reached on a communications network of a telecommunications operator to which the user has subscribed, recording said only one received identification information in association with a messaging mailbox identifier selected by the messaging mailbox management device from a plurality of messaging mailbox identifiers stored in a memory of said messaging mailbox management device, corresponding, respectively, to unallocated messaging mailboxes, without receiving any contact identifier of the user that can be reached on a communications network, and sending a message in reply to the request for a messaging mailbox without a previous configuration by the user in said messaging mailbox management device, via the communications network, to the communication terminal, said message comprising the messaging mailbox identifier.
2. The method according to claim 1, wherein, the user being a service provider, said only one user identification information contained in the request is an identifier of the service provider.
3. The method according to claim 1, wherein, the user is a user of a service provider that owns said communication terminal, while also having a main contact identifier and a secondary contact identifier which have been previously recorded in association in said communication terminal, the main contact identifier being reachable on a communications network of a telecommunications operator to which the user has subscribed, and the secondary contact identifier being different from any contact identifier that can be reached on a communications network of a telecommunications operator to which the user has subscribed, and said only one user identification information contained in the request is an identifier of the service provider and an identifier of the user.
4. The method according to claim 1, comprising: receiving from the communication terminal, via the communications network, a request for the configuration of a profile of the messaging mailbox associated with said messaging mailbox identifier, the request comprising the identifier of the messaging mailbox, returning to the communication terminal, via the communications network, a reply containing a messaging mailbox profile configuration form to be completed by the user, receiving in return from the communication terminal, via the communications network, a reply containing the completed messaging mailbox profile configuration form, said form containing a main contact identifier of the user, and parameterizing the messaging mailbox, using information contained in the form and said main contact identifier of the user.
5. The method according to claim 1, further comprising: processing a deposition of a message by a user, called a depositing user, in a messaging mailbox that has been previously allocated to a user, called an owner user, according to the act of allocating, wherein processing the deposition comprises, after the owner user has provided the depositing user with a secondary contact identifier recorded previously, in the messaging mailbox management device, in association with a messaging mailbox identifier allocated to the owner user, said secondary contact identifier being different from any contact identifier that can be reached on a communications network of a telecommunications operator to which the owner user has subscribed, the following actions are performed in the messaging mailbox management device: intercepting a communication made by a communication terminal of the depositing user, called a depositing terminal, this communication having been directed to said secondary contact identifier, routing the communication to the messaging mailbox, using the identifier of the messaging mailbox corresponding to the secondary contact identifier of the owner user, receiving the message deposited by the depositing terminal in the messaging mailbox corresponding to the messaging mailbox identifier allocated to the owner user, and sending a notification of said message deposition to a main contact identifier of the owner user which has previously been recorded in the messaging mailbox management device, in association with the secondary contact identifier and the messaging mailbox identifier allocated to the owner user, said main contact identifier being reachable on a communications network of a telecommunications operator to which the owner user has subscribed.
6. A messaging mailbox management device, comprising: a non-transitory computer readable medium; and a processing circuit, which is arranged to allocate on the fly to a user a messaging mailbox located in a communications network, wherein the processing circuit is also arranged to: receive from a communication terminal of a user unknown by said messaging mailbox management device, via the communications network, a request for a messaging mailbox, said request comprising only one user identification information, said identification information being different from an email of said user and from a contact identifier of said user that can be reached on a communications network of a telecommunications operator to which the user has subscribed, record in the non-transitory computer-readable medium said only one received identification information in association with a messaging mailbox identifier selected by the messaging mailbox management device from a plurality of messaging mailbox identifiers stored in a memory of said messaging mailbox management device, corresponding, respectively, to unallocated messaging mailboxes, without receiving any contact identifier of the user that can be reached on a communications network, and send a message in reply to the request for a messaging mailbox without a previous configuration by the user in said messaging mailbox management device, via the communications network, to the communication terminal, said message comprising the messaging mailbox identifier.
7. The device according to claim 6, wherein the processing circuit is also arranged to process the deposition of a message by a user, called a depositing user, in a messaging mailbox which has previously been allocated to a user called an owner user, the owner user having previously provided the depositing user with a secondary contact identifier recorded previously in the messaging mailbox management device, in association with a messaging mailbox identifier allocated to the owner user, said secondary contact identifier being different from any contact identifier that can be reached on a communications network of a telecommunications operator to which the owner user has subscribed, said processing circuit also being arranged to: intercept a communication made by a communication terminal of the depositing user, called the depositing terminal, this call having been directed to said secondary contact identifier, route the communication to the messaging mailbox, using the identifier of the messaging mailbox corresponding to the secondary contact identifier of the owner user, receive the message deposited by the depositing terminal in the messaging mailbox corresponding to the messaging mailbox identifier allocated to the owner user, and send a notification of said message deposition to a main contact identifier of the owner user which has previously been recorded in the messaging mailbox management device, in association with the secondary contact identifier and the messaging mailbox identifier allocated to the owner user, said main contact identifier being reachable on a communications network of a telecommunications operator to which the owner user has subscribed.
8. A non-transitory computer-readable recording medium on which is recorded a computer program comprising instructions in program code for performing a messaging mailbox allocation method when said program is run on a messaging mailbox management device, wherein the instructions configure the messaging mailbox management device to perform acts comprising: allocating on the fly a messaging mailbox located in a communications network to a user, wherein allocating comprises: receiving from a communication terminal of a user unknown by said messaging mailbox management device, via the communications network, a request for a messaging mailbox, said request comprising only one user identification information, said identification information being different from an email of said user and from a contact identifier of said user that can be reached on a communications network of a telecommunications operator to which the user has subscribed, recording said only one received identification information in association with a messaging mailbox identifier selected by the messaging mailbox management device from a plurality of messaging mailbox identifiers stored in a memory of said messaging mailbox management device, corresponding, respectively, to unallocated messaging mailboxes, without receiving any contact identifier of the user that can be reached on a communications network, and sending a message in reply to the request for a messaging mailbox without a previous configuration by the user in said messaging mailbox management device, via the communications network, to the communication terminal, said message comprising the messaging mailbox identifier.
9. The non-transitory computer-readable recording medium according to claim 8, wherein the instructions further configure the messaging mailbox management device to perform acts comprising: processing a deposition of a message by a user, called a depositing user, in a messaging mailbox that has been previously allocated to a user, called an owner user, according to the act of allocating, wherein processing the deposition comprises, after the owner user has provided the depositing user with a secondary contact identifier recorded previously, in the messaging mailbox management device, in association with a messaging mailbox identifier allocated to the owner user, said secondary contact identifier being different from any contact identifier that can be reached on a communications network of a telecommunications operator to which the owner user subscribes, the following actions are performed in the messaging mailbox management device: intercepting a communication made by a communication terminal of the depositing user, called a depositing terminal, this communication having been directed to said secondary contact identifier, routing the communication to the messaging mailbox, using the identifier of the messaging mailbox corresponding to the secondary contact identifier of the owner user, receiving the message deposited by the depositing terminal in the messaging mailbox corresponding to the messaging mailbox identifier allocated to the owner user, and sending a notification of said message deposition to a main contact identifier of the owner user which has previously been recorded in the messaging mailbox management device, in association with the secondary contact identifier and the messaging mailbox identifier allocated to the owner user, said main contact identifier being reachable on a communications network of a telecommunications operator to which the owner user has subscribed.
Description
BRIEF DESCRIPTION OF THE DRAWINGS
(1) Other characteristics and advantages will be apparent from reading the embodiments described with reference to the drawings, in which:
(2)
(3)
(4)
(5)
(6)
(7)
DETAILED DESCRIPTION OF A FIRST EMBODIMENT
(8)
(9) The system comprises a communication terminal Tt, called the owner terminal, which can establish a communication with a messaging mailbox management device DGBM, via a communications network RC1.
(10) In the illustrated example, the network RC1 is an extended network WAN (Wide Area Network), such as the internet.
(11) The owner terminal Tt is, for example, a communications server belonging to an owner user Ut, such as a service provider which offers, for example, to support a national or international voluntary initiative, for example a campaign against world hunger, a cancer prevention campaign, sponsorship of a charitable association, or the like. For this purpose, the communications server Tt is adapted to receive messages of support from calling users. These messages may be voice, text or multimedia messages, depending on the type of terminals owned by these users. To avoid using an excessively large number of staff to reply to these messages in a synchronous manner, and/or to avoid disclosing their personal contact identifiers (such as a telephone number), the service provider allocates a messaging mailbox to the communications server Tt, as described below.
(12) In a known way, the server Tt comprises hardware and/or software resources, particularly a processing circuit CT1 for establishing communications with the messaging mailbox management device, the processing circuit CT1 containing a processor PROC1 controlled by a computer program PG1.
(13) On initialization, the code instructions of the computer program PG1 are, for example, loaded into a RAM memory, denoted MR1, before being executed by the processing circuit CT1.
(14) The communications server Tt mainly comprises: a communication interface COM10, adapted to exchange messages, according to the HTTP protocol (HyperText Transfer Protocol), for example, with the messaging mailbox management device DGBM, via the communications network RC1, a storage module MST1, for example a database, containing: one or more main contact identifiers ICP.sub.t, such as the mobile telephone number, the fixed line number, the IP address or the permanent email address of the service provider, said identifiers having been assigned to it by one or more telecommunications operators to which the service provider Ut has subscribed, identification information IDU.sub.t of the service provider, for example its name or a service identifier ID.sub.s.
(15) The communication interface COM10 and the storage module MST1 are controlled by the processor PROC1 of the processing circuit CT1.
(16) According to the invention, a messaging mailbox identifier IDM.sub.j is first recorded, in association with the main contact identifier or identifiers ICP.sub.t and the identification information IDU.sub.t of the service provider Ut, in the memory MST1 of the server Tt.
(17) The messaging mailbox identifier IDM.sub.j is, optionally, also recorded in association with a secondary contact identifier ICS.sub.j of the service provider in the memory MST1 of the server Tt. For this purpose, the secondary contact identifier ICS.sub.j is shown in broken lines in
(18) The secondary contact identifier ICS.sub.j is designed to receive communications from calling users wishing to support the voluntary initiative. It may be, for example, a fixed or mobile telephone number NT.sub.j, and/or an email address @EM.sub.j, and/or an address URL.sub.j for accessing Web content, for example a URL (Uniform Resource Locator) link, or the like. The secondary contact identifier is never a contact identifier by means of which the service provider Ut can be reached via a communications network of a telecommunications operator to which the service provider subscribes. As described in a later part of the description, the secondary contact identifier ICS.sub.j is first assigned by the messaging mailbox management device DGBM to the service provider Ut, in association with a messaging mailbox identifier IDM.sub.j.
(19) The validity of the secondary contact identifier ICS.sub.j preferably has a duration which is equal, for example, to the duration of subscription to the messaging service according to the invention, which itself is equal, in the illustrated example, to the duration of the support for the voluntary initiative. In a variant, the secondary contact identifier ICS.sub.j has a predetermined duration fixed in advance by the administrator of the messaging mailbox management device DGBM.
(20) The messaging mailbox management device DGBM is a platform installed in the communications network RC1, which is designed, according to the invention, so that: it allocates, at the request of the owner terminal Tt, via the communications network RC1, a messaging mailbox associated with a unique messaging mailbox identifier IDM.sub.j, it processes any request to deposit messages sent to the messaging mailbox corresponding to the messaging mailbox identifier IDM.sub.j.
(21) In a known way, the messaging mailbox management device DGBM comprises hardware and/or software resources, particularly a processing circuit CT2 for allocating to the service provider Tt a messaging mailbox located in the communications network RC1, and for processing the deposition of a message by a user in the messaging mailbox corresponding to the messaging mailbox identifier IDM.sub.j, the processing circuit CT2 containing a processor PROC2 controlled by a computer program PG2.
(22) On initialization, the code instructions of the computer program PG2 are, for example, loaded into a RAM memory, denoted MR2, before being executed by the processing circuit CT2.
(23) The messaging mailbox management device DGBM mainly comprises: a first communication interface COM20 which operates, for example, according to the HTTP communications protocol, and which is adapted: to exchange messages, via the communications network RC1, with the communication interface COM10 of the communications server Tt of the service provider Ut, to send messages to a communication interface COM30 of a message deposition notification server, identified by the reference NOT in
(24) According to the invention, the messaging mailbox management device DGBM comprises a server SP, of the proxy type for example, which comprises a storage module MST2, for example a database, containing a plurality of messaging mailbox identifiers IDM.sub.1, IDM.sub.2, . . . , IDM.sub.j, . . . , IDM.sub.K, associated respectively with the messaging mailboxes BM.sub.1, BM.sub.2, . . . , BM.sub.j, . . . , BM.sub.K.
(25) Each of the messaging mailbox identifiers IDM.sub.1, IDM.sub.2, . . . , IDM.sub.j, . . . , IDM.sub.K is also associated, respectively, with: a corresponding main contact identifier ICP.sub.1, ICP.sub.2, . . . , ICP.sub.t, . . . , ICP.sub.K of a corresponding owner user, a corresponding secondary contact identifier ICS.sub.1, ICS.sub.2, . . . , ICS.sub.j, . . . , ICS.sub.K of a corresponding owner user Ut.
(26) In the messaging system of
(27) It should be noted that, even though the message deposition notification server NOT is not hosted in the messaging mailbox management device DGBM in the embodiment shown in
(28) In fact, in a variant embodiment, the messaging mailbox management device DGBM could indeed host the message deposition notification server NOT.
(29) The communication interfaces COM20, COM21 and COM22, the storage module MST2, and the messaging mailboxes BM.sub.1, BM.sub.2, . . . , BM.sub.j, . . . , BM.sub.K are controlled by the processor PROC2 of the processing circuit CT2.
(30) With reference to
(31) The messaging mailbox allocation method is then executed as follows:
(32) In S1, the messaging mailbox management device DGBM receives on its communication interface COM20, from the server Tt, via the communications network RC1, a request for a messaging mailbox which contains an identifier IDU.sub.t of the service provider Ut, as previously stored in the storage memory MST1 of the service provider Ut of
(33) In the illustrated example, the request is of the HTTP type and is sent from the communication interface COM10 of the server Tt of the service provider Ut. This request is sent, either via a dedicated software application which has been previously downloaded to the server Tt, or via an intermediate web server located in the communications network RC1.
(34) In S2, the messaging mailbox management device DGBM records the received identifier IDU.sub.t in the storage memory MST2, in association with a messaging mailbox identifier IDM.sub.j selected from a plurality of messaging mailbox identifiers IDM.sub.1, IDM.sub.2, . . . , IDM.sub.j, . . . , IDM.sub.K stored in the memory MST2 of messaging mailbox management device DGBM, corresponding, respectively, to unallocated messaging mailboxes BM.sub.1, BM.sub.2, . . . , BM.sub.j, . . . , BM.sub.K.
(35) In S3, the messaging mailbox management device DGBM, using the communication interface COM20, replies to the service provider's server Tt, via the communications network RC1, by sending a reply to the request received in S1, said reply containing the selected messaging mailbox identifier IDM.sub.j.
(36) On completion of this operation, a messaging mailbox BM.sub.j is allocated to the service provider Ut.
(37) In S4, the messaging mailbox management device DGBM receives on its communication interface COM20, from the server Tt, via the communications network RC1, a request for configuration of the messaging mailbox BM.sub.j, said configuration request containing the identifier IDM.sub.j of the messaging mailbox BM.sub.j.
(38) In the illustrated example, the request is of the HTTP type and is sent from the communication interface COM10 of the server Tt of the service provider Ut. This request is sent, either via a dedicated software application which has been previously downloaded to the server Tt, or via an intermediate web server located in the communications network RC1.
(39) In S5, the messaging mailbox management device DGBM, using the communication interface COM20, replies to the service provider's server Tt, via the communications network RC1, by sending a reply to the request received in S4, said reply containing a messaging mailbox profile configuration form to be completed by the service provider Ut.
(40) In S6, the messaging mailbox management device DGBM receives on its communication interface COM20, from the server Tt, via the communications network RC1, a message containing the completed messaging mailbox profile configuration form.
(41) According to an exemplary embodiment, the configuration form consists of one or more web pages, on which the user Ut enters or ticks, in particular, the following information: the message format types to be received: voice, SMS, MMS, MP3, MP4, JPEG, etc., the desired main contact identifier ICP.sub.t for receiving notifications of the deposition of messages recorded in the messaging mailbox BM.sub.j, the desired type of message deposition notification: text (SMS, push, email, URL, etc.) or voice (special dial tone).
(42) According to the above information, the user Ut selects at least one secondary contact identifier ICS.sub.j offered in the form, of the type described above in the description.
(43) The user Ut is also able to access a server (not shown in
(44) In S7, the messaging mailbox management device DGBM parameterizes the messaging mailbox BM.sub.j in accordance with the information contained in the received form, and associates the main contact identifier ICP.sub.t, in the storage memory MST2, with the messaging mailbox identifier IDM.sub.j.
(45) On completion of this parameterization operation, the messaging mailbox BM.sub.j is ready to record any message deposited by a depositing user Ud.
(46) With reference to
(47) In a preliminary step, the service provider Ut has communicated to the depositing user Ud the secondary contact identifier ICS.sub.j assigned to him by the messaging mailbox management device DGBM, so that the depositing user Ud can reach this contact identifier and deposit his message there. Depending on the communication capabilities of the communication terminal Td of the depositing user Ud, the service provider Ut communicates the telephone number NT.sub.j and/or the email address @EM.sub.j and/or the web address URL.sub.j to the depositing user Ud. According to an exemplary embodiment, these secondary contact identifier or identifiers ICS.sub.j are, for example, communicated to the depositing user Ud on a web page for supporting the voluntary initiative of the service provider Ut, available on the service provider's website.
(48) In S100, the messaging mailbox management device DGBM receives a communication on one of its communication interfaces COM20, COM21 or COM22 from the terminal Td of a depositing user Ud, via the communications network RCd to which the terminal Td is attached.
(49) If, for example, the depositing user makes a voice call from his terminal Td to the telephone number NT.sub.j, the communication is received on the communication interface COM21.
(50) If, for example, the depositing user sends an SMS call from his terminal Td to the telephone number NT.sub.j, the communication is received on the communication interface COM22.
(51) If, for example, the depositing user Ud sends an email from his terminal Td to the address @EM.sub.j, this communication is received on the communication interface COM20.
(52) If, for example, the depositing user Ud clicks on the web address URL.sub.j contained in the web page for supporting the voluntary initiative, this communication is also received on the communication interface COM20.
(53) In S101, the received communication is routed to the messaging mailbox BM.sub.j, using the messaging mailbox identifier IDM.sub.j recorded in the storage module MST2 in association with the secondary contact identifier ICS.sub.j of the owner user Ut.
(54) In S102, after the launch of the welcome message, which may be of the visual or voice type, depending on the type of message to be deposited, the message deposited by the depositing terminal Td is received in the messaging mailbox BM.sub.j.
(55) Depending on the communication capabilities of the depositing terminal Td, the message may, for example, contain audio or text data, images, video, multimedia, or other data.
(56) In a known way, the deposited message is associated with identification information of the depositing user Ud, such as his name, his telephone number, his email address, a pseudonym, or other information.
(57) In S103, the messaging mailbox management device DGBM transmits to the interface COM30 of the message deposition notification server NOT, by means of its communication interface 20, via the communications network RC1, a message indicating that a message has been deposited in S102 in association with the main contact identifier ICP.sub.t of the service provider Ut and the type of message notification previously selected by the user Ut during the configuration of his messaging mailbox.
(58) In S104, the message deposition notification server NOT then sends a message containing the notification of the deposition of said message directly to the main contact identifier ICP.sub.t of the server Tt.
(59) Depending on the type of message deposition notification selected previously by the user Ut during the configuration of his messaging mailbox, and by way of non-limiting examples: the notification is an SMS message or a voice call with a special dial tone, which is received on a fixed or mobile telephone number forming the main contact identifier ICP.sub.t of the server Tt, in which case said SMS or said call may directly contain the message deposited by the depositing user Ud, or may contain a voice menu for consulting the message deposited by the depositing user, the notification is an email received at the email address forming the main contact identifier ICP.sub.t of the server Tt, in which case said email may directly contain the message deposited by the depositing user Ud, or may contain a URL link for accessing the message in the messaging mailbox BM.sub.j, the notification is a notification of the push or USSD (Unstructured Supplementary Service Data) type, or of the URL type, received on the IP address forming the main contact identifier ICP.sub.t of the server Tt, in which case the push or USSD notification may directly contain the message deposited by the depositing user Ud, or alternatively contain a URL link for accessing the message in the messaging mailbox BM.sub.j, and the URL notification provides direct access to the message in the messaging mailbox BM.sub.j.
(60) According to the messaging mailbox allocation method and the message deposition processing method described above, communications between the communication terminal Tt, the messaging mailbox management device and the notification server NOT may be secured by well-known authentication and encoding mechanisms.
(61) The messaging mailbox BM.sub.j may, on the other hand, be deleted after a predetermined time interval recorded in the messaging mailbox management device DGBM, or at the request of the user Ut to the messaging mailbox management device, said request containing the messaging mailbox identifier IDM.sub.j.
DETAILED DESCRIPTION OF A SECOND EMBODIMENT
(62) A description will now be given, with reference to
(63) For the sake of clarity in
(64) The system comprises a communication terminal Tt, called the owner terminal, which can establish a communication with a messaging mailbox management device DGBM, via a communications network RC1.
(65) The system comprises a communication terminal Tt, called the owner terminal, which can establish a communication with a messaging mailbox management device DGBM, via a communications network RC1.
(66) In the illustrated example, the network RC1 is an extended network WAN (Wide Area Network), such as the internet.
(67) In the illustrated example, the terminal Tt may equally well be a mobile telephone comprising a SIM card having a unique subscriber identifier called an IMSI (International Mobile Subscriber Identity). In a known way, this identifier is used to identify the terminal Tt in the communications network RCt to which it is attached, that is to say the network to which the user Ut of the terminal Tt has subscribed. In the illustrated example, the network RCt is of a mobile type, such as a GSM (Global System for Mobile communications), UMTS (Universal Mobile Telecommunications System), LTE (Long Term Evolution) network, or other type. The identifier IMSI is associated with a main contact identifier MSISDN, denoted as ICP.sub.t, which is the telephone number used to reach the terminal Tt.
(68) Evidently, this example is not limiting. Thus, according to another example, the terminal Tt is, for example, a fixed telephone attached to a PABX (Private Automatic Branch Exchange).
(69) Depending on the type of communications network RCt, the main contact identifier ICP.sub.t of the terminal Tt could be different from a telephone number. For example, it could be an email address, an IP address, a WebRTC (Web Real-Time Communication) identifier, an instant messaging identifier, or another type.
(70) The terminal Tt can establish a communication, via a communications management server DGC, with a communication terminal Td, which also has a main contact identifier. This server DGC contains a platform installed in the network which is designed so that: it processes any communication made by the terminal Tt from its main contact identifier ICP.sub.t to the terminal Td, and, conversely, it processes any communication made by the communication terminal Td from its main contact identifier to the terminal Tt.
(71) In the illustrated example, the terminal Td is a mobile telephone attached to a mobile communications network RCd. However, the terminal Td may equally well be a fixed telephone attached to a switched telecommunications network.
(72) According to another example which is not shown, the communications networks RCt and RCd may form a single communications network belonging to a single telecommunications operator.
(73) Additionally, in the present description, the term communication is taken to mean a conventional voice call or any other communication session of the data and/or audio and/or video type made by the terminal Tt to the terminal Td, or, conversely, by the terminal Td to the terminal Tt.
(74) According to the second embodiment, the terminal Tt also has a secondary contact identifier ICS.sub.j which has been previously assigned to it by a service provider (not shown), to which the user Ut has subscribed, as part of an anonymity protection service offered by this service provider and administered by the communication management platform DGC. As explained above in the description, this type of anonymity protection service is offered when the user wishes, for example, to place an announcement on a dedicated internet site for this purpose, such as a small ads site, a dating site, a personal or professional social network, or the like.
(75) In the illustrated embodiment, the secondary contact identifier ICS.sub.j is chosen from a pool of secondary call identifiers managed by the communication management platform DGC.
(76) In the illustrated example, the secondary contact identifier ICS.sub.j is a fixed or mobile telephone number NT.sub.j. However, in a variant, depending on the type of communication that can be made by the terminal Tt, the secondary contact identifier ICS.sub.j is, for example, an email address @EM.sub.j and/or an address URL.sub.j for accessing web content, for example a URL (Uniform Resource Locator) link. The secondary contact identifier is never a contact identifier by means of which the user Ut can be reached via a communications network of a telecommunications operator to which the service provider subscribes. The secondary contact identifier ICS.sub.j is designed to receive communications from users calling the user Ut. As described in a later part of the description, the secondary contact identifier ICS.sub.j is first assigned by the messaging mailbox management device DGBM of the communication management platform DGC, in association with a messaging mailbox identifier IDM.sub.j.
(77) The validity of the secondary contact identifier ICS.sub.j preferably has a duration which is equal, for example, to the duration of subscription to the messaging service according to the invention, which is itself equal, in the illustrated example, to the duration of the anonymity protection service offered by the service provider. In a variant, the secondary contact identifier ICS.sub.j has a predetermined duration fixed in advance by the administrator of the messaging mailbox management device DGBM.
(78) The secondary contact identifier ICS.sub.j has, for example, been assigned in connection with the deposition of an announcement on a dedicated website administered by a service provider. In the context of a website dedicated to private individuals, the announcement may be, for example, an advertisement for the sale of goods or services, deposited by the user Ut. In the context of a social network, it may be, for example, an announcement describing the personal or professional career of the user Ut. In the context of a communication service dedicated to a business, it may be, for example, an announcement deposited by the user Ut who is an employee of the business, to be made available to the user Ud who is also an employee of the business.
(79) According to one embodiment, the communication management platform DGC comprises hardware and/or software resources, particularly a processing circuit CT1 for providing communication management between the terminal Tt and the terminal Td, the processing circuit CT1 containing a processor PROC1 controlled by a computer program PG1.
(80) On initialization, the code instructions of the computer program PG1 are, for example, loaded into a RAM memory, denoted MR1, before being executed by the processing circuit CT1.
(81) The communication management platform DGC mainly comprises: a first communication interface COM10 which is adapted to exchange messages using the HTTP protocol, for example, with: the messaging mailbox management device DGBM via the communications network RC1, the terminal Tt, via the network RCt and/or RC1 or any other suitable network, a service provider to which the user UTt has subscribed, a second communication interface COM11 which is adapted to communicate with the terminals Tt and Td, and which, in the illustrated example, is a communication interface adapted to send or receive voice calls, a third communication interface COM12 which is adapted to communicate with the terminals Tt and Td, and which, in the illustrated example, is a communication interface adapted to send or receive SMS (Short Message Service) text messages, or MMS (Multimedia Messaging Service) multimedia messages, a profile manager GP adapted to manage the profile of the user Ut of the terminal Tt, a storage module MST1, for example a database, linked to the profile manager GP and containing: one or more main contact identifiers ICP.sub.t, such as the mobile telephone number, the fixed line number, the IP address or the permanent email address of the user Ut, said identifiers having been assigned to it by one or more telecommunications operators to which the user Ut subscribes, identification information IDU.sub.t of the user Ut, such as his name, his pseudonym, and an identifier ID.sub.A of the announcement that the user Ut has deposited with the service provider.
(82) The communication interfaces COM10, COM11 and COM12, the storage module MST1, and the profile manager GP are controlled by the processor PROC1 of the processing circuit CT1.
(83) According to the invention, a messaging mailbox identifier IDM.sub.j is first recorded in the memory MST1 of the communication management platform DGC, in association with: the main contact identifier or identifiers ICP.sub.t, the identification information IDU.sub.t of the user Ut, a secondary contact identifier ICS.sub.j of the user Ut.
(84) The profile manager GP is connected to a switching centre CMT which is adapted to process the path of the communication made from the terminal Tt to the terminal Td, and vice versa.
(85) The switching centre CMT is well known. In the illustrated example, it is, for example, a mobile switching centre MSC (Mobile Switching Centre) of a mobile telecommunications network. According to another embodiment in which the terminal Tt is of a fixed type, the switching centre CMT could be a local exchange of a fixed telecommunications network. It should be noted that, in the fixed telecommunications network, the local exchange handles local calls between subscribers of the same exchange, together with incoming and outgoing traffic with other exchanges.
(86) The switching centre CMT is characterized by two main functions.
(87) The first main function is a call control function, corresponding to the central function of a telephone exchange. This function uses various operations such as the decoding of address information and the routing of telephone calls from a calling terminal to a called terminal. This function is associated with certain call functions such as: call queuing, call forwarding to a messaging system operated by the messaging mailbox management device DGBM, when the called terminal Tt is hung up, a special tone indicating to a calling user Ud that the user Ut is already on line or cannot be reached.
(88) This first function also processes the signalling level established during the communication between the two terminals, that is to say the level corresponding to the signalling of the messages exchanged via the various entities of the communications network.
(89) The second main function is a media function, for processing the whole media portion of the communication between the two terminals. This function corresponds to the media level of the processing of the text and/or audio and/or image/video data exchanged between the two terminals during the communication.
(90) It should be noted that, although the profile manager GP and the switching centre CMT are both hosted in the communication management platform DGC in the embodiment shown in
(91) In fact, in a variant embodiment, the communication management platform DGC could contain only the profile manager GP, the switching centre CMT being hosted at another location in the network while still being connected functionally to the profile manager GP.
(92) The messaging mailbox management device DGBM is a platform installed in the communications network RC1, which is designed, according to the invention, so that: it allocates, at the request of the communication management platform DGC, via the communications network RC1, a messaging mailbox associated with a unique messaging mailbox identifier IDM.sub.j, and it processes any request to deposit messages sent to the messaging mailbox corresponding to the messaging mailbox identifier IDM.sub.j.
(93) In a known way, the messaging mailbox management device DGBM comprises hardware and/or software resources, particularly a processing circuit CT2 for allocating to the user Ut a messaging mailbox located in the communications network RC1, and for processing the deposition of a message by a user Ud in the messaging mailbox corresponding to the messaging mailbox identifier IDM.sub.j, the processing circuit CT2 containing a processor PROC2 controlled by a computer program PG2.
(94) On initialization, the code instructions of the computer program PG2 are, for example, loaded into a RAM memory, denoted MR2, before being executed by the processing circuit CT2.
(95) The messaging mailbox management device DGBM mainly comprises: a first communication interface COM20 which operates, for example, according to the HTTP communications protocol, and which is adapted: to exchange messages, via the communications network RC1, with the communication interface COM10 of the communication management platform DGC, to send messages to a communication interface COM30 of a message deposition notification server, identified by the reference NOT in
(96) According to the invention, the messaging mailbox management device DGBM comprises a server SP, of the proxy type for example, which comprises a storage module MST2, for example a database, containing a plurality of messaging mailbox identifiers IDM.sub.1, IDM.sub.2, . . . , IDM.sub.j, . . . , IDM.sub.K, associated respectively with the messaging mailboxes BM.sub.1, BM.sub.2, . . . , BM.sub.j, . . . , BM.sub.K.
(97) Each of the messaging mailbox identifiers IDM.sub.1, IDM.sub.2, . . . , IDM.sub.j, . . . , IDM.sub.K is also associated, respectively, with: a corresponding main contact identifier ICP.sub.1, ICP.sub.2, . . . , ICP.sub.t, . . . , ICS.sub.K of a corresponding owner user, a corresponding secondary contact identifier ICS.sub.1, ICS.sub.2, . . . , ICS.sub.t, . . . , ICS.sub.K of a corresponding owner user.
(98) In the messaging system of
(99) It should be noted that, even though the message deposition notification server NOT is not hosted in the messaging mailbox management device DGBM in the embodiment shown in
(100) In fact, in a variant embodiment, the messaging mailbox management device DGBM could indeed host the message deposition notification server NOT.
(101) The communication interfaces COM20, COM21 and COM22, the storage module MST2, and the messaging mailboxes BM.sub.1, BM.sub.2, . . . , BM.sub.j, . . . , BM.sub.K are controlled by the processor PROC2 of the processing circuit CT2.
(102) With reference to
(103) Before this method is executed, the user Ut has subscribed, notably in the course of depositing an announcement on a dedicated website, to an anonymity protection service administered by the communication management platform DGC linked to the service provider which administers the dedicated website. Following this subscription, the user Ut has communicated his main contact identifier or identifiers ICP.sub.t to the platform DGC, together with his identification information IDU.sub.t, which have been recorded in the storage memory MST1 of the platform DGC, in association with one or more secondary contact identifiers ICS.sub.j assigned by the platform DGC to the user Ut.
(104) According to the invention, during this subscription, the user Ut has also selected, in association with the secondary contact identifier or identifiers ICS.sub.j, a messaging option offered by the platform DGC.
(105) The messaging mailbox allocation method is then executed as follows:
(106) In S1, the messaging mailbox management device DGBM receives on its communication interface COM20, from the platform DGC, via the communications network RC1, a request for a messaging mailbox which contains an identifier IDP of the platform DGC, together with an identifier IDU.sub.t of the user Ut, as previously stored in the storage memory MST1 of the platform DGC.
(107) In the illustrated example, the request is of the HTTP type and is sent from the communication interface COM10 of the platform DGC. This request is sent, either via a dedicated software application which has been previously downloaded to the platform DGC, or via an intermediate web server located in the communications network RC1.
(108) In S2, the messaging mailbox management device DGBM records, in the storage memory MST2, the received identifier IDU.sub.t, in association with a messaging mailbox identifier IDM.sub.j selected from a plurality of messaging mailbox identifiers IDM.sub.1, IDM.sub.2, . . . , IDM.sub.j, . . . , IDM.sub.K stored in the memory MST2 of the messaging mailbox management device DGBM and corresponding, respectively, to unallocated messaging mailboxes BM.sub.1, BM.sub.2, . . . , BM.sub.j, . . . , BM.sub.K, and corresponding to the identifier IDP of the communication management platform DGC offering the anonymity protection service.
(109) In S3, the messaging mailbox management device DGBM, using the communication interface COM20, replies to the communication management platform DGC, via the communications network RC1, by sending a reply to the request received in S1, said reply containing the selected messaging mailbox identifier IDM.sub.j.
(110) On completion of this operation, a messaging mailbox BM.sub.j is allocated to the user Ut of the terminal Tt, via the communication management platform DGC.
(111) In S4, the messaging mailbox management device DGBM receives on its communication interface COM20, from the communication management platform DGC, via the communications network RC1, a request for configuration of the messaging mailbox BM.sub.j, said configuration request containing the identifier IDM.sub.j of the messaging mailbox BM.sub.j.
(112) In the illustrated example, the request is of the HTTP type and is sent from the communication interface COM10 of the platform DGC. This request is sent, either via a dedicated software application which has been previously downloaded to the platform DGC, or via an intermediate web server located in the communications network RC1.
(113) In S5, the messaging mailbox management device DGBM, using the communication interface COM20, replies to the platform DGC, via the communications network RC1, by sending a reply to the request received in S4, said reply containing a messaging mailbox profile configuration form to be completed by the user Ut of the terminal Tt.
(114) In S6, the communication management platform DGC, using its communication interface COM10, retransmits the configuration form for the messaging mailbox BM.sub.j to the terminal Tt via the communications networks RC1 and RCt.
(115) In S7, the communication management platform DGC receives on its communication interface COM10, from the terminal Tt, via the communications networks RC1 and RCt, a message containing the completed messaging mailbox profile configuration form.
(116) In S8, the messaging mailbox management device DGBM receives on its communication interface COM20, from the platform DGC, via the communications network RC1, a message containing the completed messaging mailbox profile configuration form.
(117) According to an exemplary embodiment, the configuration form consists of one or more web pages, on which the user Ut enters or ticks, in particular, the following information: the message format types to be received: voice, SMS, MMS, MP3, MP4, JPEG, etc., the desired main contact identifier ICP.sub.t for receiving notifications of the deposition of messages recorded in the messaging mailbox BM.sub.j, the desired type of message deposition notification: text (SMS, push, email, URL, etc.) or voice (special dial tone).
(118) According to the above information, the user Ut selects at least one secondary contact identifier ICS.sub.j, which has previously been recorded in the platform DGC.
(119) The user Ut is also able to access a server (not shown in
(120) In S9, the messaging mailbox management device DGBM parameterizes the messaging mailbox BM.sub.j in accordance with the information contained in the received form, and associates the main contact identifier ICP.sub.t, in the storage memory MST2, with the messaging mailbox identifier IDM.sub.j.
(121) On completion of this parameterization operation, the messaging mailbox BM.sub.j is ready to record any message deposited by a depositing user Ud.
(122) With reference to
(123) In a preliminary step, the communication management platform DGC has communicated a secondary contact identifier ICS.sub.j to the owner user Ut, and the owner user Ut has activated the call forwarding option to the messaging system BM.sub.j which is offered by the communication management platform DGC linked to the service provider who administers the website dedicated to the deposition of the announcement.
(124) Also during this preliminary step, the depositing user Ud has become aware of the secondary contact identifier ICS.sub.j, either because the owner user Ut has communicated it to him beforehand, or because the depositing user Ud is interested in the announcement deposited by the owner user Ut on the service provider's website, and has made a note of the secondary contact identifier ICS.sub.j associated with this announcement.
(125) The secondary contact identifier ICS.sub.j communicated to the depositing user Ud may be the telephone number NT.sub.j, the email address @EM.sub.j and/or the web address URL.sub.j, which the depositing user Ud selects according to the communication capacities of the communication terminal Td owned by him at the moment when a communication is made, via the communications network RCd to which he belongs, to the owner terminal Tt.
(126) In S100, the communication made by the depositing terminal Td is received by the switching centre CMT, via one of the communication interfaces COM10, COM11, COM12 of the platform DGC, according to the type of communication made by the depositing terminal Td.
(127) The switching centre CMT, which knows the secondary contact identifier ICS.sub.j associated with the main contact identifier ICP.sub.t of the owner terminal Tt, then identifies this communication as a first branch of the communication that can be established between the depositing terminal Td and the owner terminal Tt.
(128) In S101, the switching centre CMT sends a request to the profile manager GP for the supply of the main contact identifier ICP.sub.t of the owner terminal Tt, which has been previously recorded in association with the secondary contact identifier ICS.sub.j in the storage module MST1 of the platform DGC.
(129) In S102, in reply to the request, the profile manager GP sends a message containing the main contact identifier ICP.sub.t of the terminal Tt to the switching centre CMT.
(130) The exchanges between the switching centre CMT and the profile manager GP are, for example, in accordance with the SIP protocol.
(131) On receipt of this message, in S103, the switching centre CMT initiates a communication to the main contact identifier ICP.sub.t of the terminal Tt, from the main contact identifier of the depositing terminal Td. The switching centre CMT then identifies this communication as a second branch of the communication to be established between the terminal Td and the terminal Tt.
(132) If the terminal Tt does not reply to the communication initiated at S103, for example because the owner user Ut does not wish to pick up the phone, or because he is already on line, or because his terminal Tt cannot be reached, the communication to the secondary contact identifier ICS.sub.j is routed in S104 to the messaging mailbox management device DGBM, via the communications network RC1, by means of one of the communication interfaces COM10, COM11, COM12, according to the type of communication that has been made by the depositing terminal Td.
(133) In S105, the messaging mailbox management device DGBM receives the communication routed on one of its communication interfaces COM20, COM21 or COM22, according to the type of communication initiated by the depositing terminal Td.
(134) If, for example, the depositing user makes a voice call from his terminal Td to the telephone number NT.sub.j, the communication is received on the communication interface COM21.
(135) If, for example, the depositing user Ud sends an SMS call from his terminal Td to the telephone number NT.sub.j, the communication is received on the communication interface COM22.
(136) If, for example, the depositing user Ud sends an email from his terminal Td to the address @EM.sub.j, this communication is received on the communication interface COM20.
(137) If, for example, the depositing user Ud clicks on the web address URL.sub.j contained in the announcement deposited by the owner user Ut, this communication is also received on the communication interface COM20.
(138) In S106, the received communication is routed to the messaging mailbox BM.sub.j, using the messaging mailbox identifier IDM.sub.j recorded in the storage module MST2 in association with the secondary contact identifier ICS.sub.j of the owner user Ut.
(139) In S107, after the launch of the welcome message, which may be of the visual or voice type, depending on the type of message to be deposited, the message deposited by the depositing terminal Td is received in the messaging mailbox BM.sub.j.
(140) Depending on the communication capabilities of the depositing terminal, the message may, for example, contain audio or text data, images, video, multimedia, or other data.
(141) In a known way, the deposited message is associated with identification information of the depositing user Ud, such as his name, his telephone number, his email address, a pseudonym, or other information.
(142) In S108, the messaging mailbox management device DGBM transmits to the interface COM30 of the message deposition notification server NOT, by means of its communication interface COM20, via the communications network RC1, a message indicating that a message has been deposited in S107 in association with the main contact identifier ICP.sub.t of the user Ut and the type of message notification previously selected by the user Ut during the configuration of his messaging mailbox.
(143) In S109, the message deposition notification server NOT then sends a message containing the notification of the deposition of said message directly to the main contact identifier ICP.sub.t of the user Ut.
(144) Depending on the type of message notification selected previously by the user Ut during the configuration of his messaging mailbox, and by way of non-limiting examples: the notification is an SMS message or a voice call with a special dial tone, which is received on a fixed or mobile telephone number forming the main contact identifier ICP.sub.t of the terminal Tt, in which case said SMS or said call may directly contain the message deposited by the depositing user Ud, or may contain a voice menu for consulting the message deposited by the depositing user, the notification is an email received at the email address forming the main contact identifier ICP.sub.t of the terminal Tt, in which case said email may directly contain the message deposited by the depositing user Ud, or may contain a URL link for accessing the message in the messaging mailbox BM.sub.j, the notification is a notification of the push, USSD, or URL type, received on the IP address forming the main contact identifier ICP.sub.t of the terminal Tt, in which case the push or USSD notification may directly contain the message deposited by the depositing user Ud, or alternatively contain a URL link for accessing the message in the messaging mailbox BM.sub.j, and the URL notification providing direct access to the message in the messaging mailbox BM.sub.j.
(145) According to the messaging mailbox allocation method and the message deposition processing method described above, communications between the communication terminal Tt, the messaging mailbox management device DGBM and the notification server NOT may be secured by well-known authentication and encoding mechanisms.
(146) The messaging mailbox BM.sub.j may, on the other hand, be deleted after a predetermined time interval recorded in the messaging mailbox management device DGBM, or at the request of the user Ut to the messaging mailbox management device, via the communication management platform DGC, said request containing the messaging mailbox identifier IDM.sub.j.
(147) An exemplary embodiment of the present disclosure overcome drawbacks of the aforementioned prior art.
(148) It goes without saying that the embodiments described above have been provided purely for guidance and in a non-limiting way, and numerous modifications may easily be made by those skilled in the art without departing from the scope of the invention.