EP2005646A1

EP2005646A1 - Module, method and computer programme for generating messages

Info

Publication number: EP2005646A1
Application number: EP07731845A
Authority: EP
Inventors: Cédric CHARBONNIER
Original assignee: France Telecom SA
Current assignee: Orange SA
Priority date: 2006-04-12
Filing date: 2007-03-29
Publication date: 2008-12-24
Also published as: FR2900016A1; WO2007116169A1

Abstract

The invention concerns a generator of messages (2), for a telecommunication system, comprising: an interface with at least one service provider (3); an interface with at least one message routing point (8) for transmitting messages to users (U1, U2, U3) according to a specific messaging mode; a database (24) of groups of message models, at least one group being identified by a group identifier; means for, upon reception of a request (R1) from a third party indicating a group identifier and a user identifier, for determining, based on said identifiers, a message model from the model database and a message format associated with a messaging mode; means for generating a message (M1) based on the determined message model and format and for transmitting same at the routing point to the user (U1) identified in the request.

Description

MODULE, METHOD AND GENERATING COMPUTER PROGRAM

FROM MESSAGES

The present invention relates to the field of message generation in telecommunications networks, which messages are generated by third parties, for example service providers and sent to users.

Generally, each service provider has a message generation system comprising software modules of two types. In such a system, a module of a first type determines the content of the message and the mode of messaging retained to convey the message to the user. Modules of a second type, each dedicated to a messaging mode, then manage the transmission of messages over telecommunications networks, via the media respectively adapted for messaging modes, for users.

Among the known messaging modes is for example the short message service, also called "short message service" or SMS, in which a written message between 70 and 160 characters (depending on languages) is sent to the user's terminal. connected to a mobile network. Another standard messaging mode is the multimedia messaging service, also called "multimedia messaging service" or MMS, in which an image or a written message embellished with multimedia data is sent to the terminal of the user connected to a mobile network. There are still other modes of messaging, for example the email or email service in which the message is sent via the Internet to the user's mailbox, or the instant messenger service, etc.

Thus, these systems held by its service providers, must include a second type of module for each messaging mode used, which is expensive, especially during an evolution related to an existing messaging mode or during the introduction a new messaging mode. In addition, each provider wishing to adapt the message according to the specificities of the users has to deal with these aspects in his message generation system.

According to a first aspect, the invention proposes a message generation module for a telecommunication system, comprising:

an interface with at least one service provider;

an interface with at least one message routing point for transmitting messages to users in accordance with a given messaging mode; a storage base for groups of message templates, at least one group being identified by a group identifier;

means adapted for, after receiving a request from a service provider indicating a group identifier and a user identifier, determining a message template in the storage database and an associated message format a messaging mode based at least on the user identifier and the message group identifier;

means for generating a message based at least on the determined message pattern and format and for transmitting it to the message routing point for routing the generated message in the given messaging mode to the message delivery point; user identified in the request.

Such a module is therefore particularly well suited to the generation of messages by a plurality of service providers and to a plurality of users, which are personalized both according to the sending service provider and the recipient user.

The content of the message, ie the meaning or the meaning of the content of the message to be brought to the attention of the user, is decided by the service provider and is designated by message generation module by the group identifier. Then an adaptation of the content of the message is carried out according to user-specific data, for example the language of expression of the content of the message and / or the messaging mode used. Only the message generation module accesses the user-specific data, which indicates specificities related to the messages to be sent to each of these users. This provision makes it possible on the one hand to preserve the confidentiality of this data, by not giving access to the service providers themselves and on the other hand to have a single base to keep up to date with the user data, for the plurality of service providers.

Taking into account a new messaging format is further simplified since the necessary adaptations can be limited to the single message generation module for all service providers.

The opening of new services requiring the sending of messages to the users is also facilitated, since the main task to allow the creation and sending of messages is limited to the definition of at least one message template group and of the associated identifier.

In one embodiment, a message group includes multiple message templates corresponding to the same translated content in respective different languages. The module is adapted to determine a language based on the identifier of the user indicated in the request. The message is generated according to the model in said language thus determined.

Thus, the service provider does not have to define in which language the messages must be expressed to each of the users, who nevertheless receive messages according to their wishes, as specified in the user data accessible by the generation module. messages from the user ID.

In one embodiment, the message generation module is adapted to interface with a plurality of message delivery points capable of transmitting messages in accordance with respective messaging modes. The message generation module is adapted to determine, according to at least the identifier of the user indicated in the request, a format among a plurality of formats, each format being associated with one of said messaging modes. The generated message is a message to format thus determined and is transmitted to the routing point of messages suitable for transmission in accordance with the messaging mode associated with the determined format.

Thus the service provider merely indicates which is the group of message templates and the recipient user. The messaging mode that will ultimately be used to transmit the message is determined based on user data, for example preferences expressed by the user.

Advantageously, the format is determined according to information relating to the user indicating a mode of mail currently preferred by the user. This information is for example of the type "presence notification" used in instant messaging services and which indicate the availability, the mood, the means of communication currently preferred by users. In one embodiment of the invention, a message template of a group comprises at least one generic parameter. The module according to the invention is then adapted to, following the reception of a request from a service provider indicating in addition a value for this generic parameter, to generate a message in which the generic parameter has been replaced by the indicated value.

The messages generated from the templates can therefore be supplemented with data mastered by the service provider and which were not owned at the time of message template definition, or which are regularly updated data. According to a second aspect, the invention proposes a method of generating messages in a message generation module for a telecommunication system, comprising:

an interface with at least one service provider;

an interface with at least one message routing point for transmitting messages to users in accordance with a given messaging mode;

a storage base for groups of message models, at least one group being identified by a group identifier. The method comprises the following steps:

after receiving a request from a service provider indicating a group identifier and a user identifier, determining, based at least on the user identifier and the group identifier, a message template in the storage base and a message format associated with a messaging mode;

generate a message based at least on the message model and the determined format;

- Transmit the generated message to the message routing point for routing to the user identified in the request, in the given messaging mode.

According to a third aspect, the invention proposes a computer program that can be installed in a message generation module for a telecommunication system. The message generation module comprises:

an interface with at least one service provider;

an interface with at least one message routing point for transmitting messages to users in accordance with a given messaging mode; a message template group storage base, at least one group being identified by a group identifier.

The program according to the invention comprises instructions for implementing the steps of a method according to the second aspect of the invention during execution of the program by means of processing the message generation module.

Other features and advantages of the invention will become apparent on reading the description which follows. This is purely illustrative and should be read with reference to the accompanying drawings, in which: FIG. 1 shows a system embodying an embodiment of the invention; FIG. 2 represents part of the contents of the storage base of the system represented in FIG. 1, FIG. 1 shows a system 1 in one embodiment of the invention, which comprises an interface message generation module 2 input to a plurality of service providers and an output interface to a plurality of routing points messages. In Figure 1, two service providers 3, 4 and three routing points 6, 7, 8 are shown. The service provider 3 is the "Fournix" provider and the service provider 4 is the "Urmix" provider.

Each message delivery point is an entry point of a separate messaging service, adapted to forward messages received by the routing points to users, indicated in headers of these messages.

In the embodiment considered, the routing point 6 is an SMSC, responsible for transmitting SMS-type messages to users connected to a mobile network 9 via their portable terminals (three of which are represented: 11, 12, 13).

The mobile network 9 is of type GPRS ("General Packet Radio Service").

The routing point 7 is an MMSC, responsible for transmitting MMS messages to users connected to the mobile network 9, which through their personal assistants or PDAs (three of which are represented: 14, 15, 16) .

The routing point 8 is an electronic messaging device implementing the SMTP / POP protocols, able to transfer the emails messages to electronic mail servers, allowing the retrieval of messages by users connected to the Internet network 10, by the intermediate of their computers (three of which are represented: 18, 19, 20).

These routing points support a number of tasks, such as managing message queues, causing message storage when the recipient is absent, and so on.

The message generation module 2 comprises a request processing block 21, a message management block 23, a block 26, a memory zone 25 for storing a history relating to the messages sent and a block of memorization of message templates 24.

The request processing block 21 is connected to a set of databases BDD, storing data relating to the users U1, U2, U3, ... One, each identified by an identifier I D1M ₁ IDU_2, IDU_3, ... IDU_n.

For example, the set of databases BDD stores in particular preferences indicated by the users, such as the preferred written communication language, the preferred messaging mode, the addresses of the users for the different modes of messaging, etc.

Thus, for the user U1, the data stored in the base BDD indicate that his preferred communication language is English, and that his preferred mode of mail is email. For the user U2, his preferred communication language as stored in the database BDD is French, his preferred mode of messaging is the SMS. For the user U3, the preferred communication language stored in the BDD database is French, the preferred messaging mode is the preferred messaging mode indicated in the database storing the presence notifications of the instant messenger.

Groups of messages are stored in the message template storage block 24.

Each group of messages is identified by an IDG_x group ID. Each message group has one or more message templates.

For example, with reference to FIG. 2, the group IDG_n comprises two message models: Mn (French), Mn (English). The "French" and "English" languages are subsequently represented by "FR" and "GB" respectively.

The model Mn (FR) corresponds to the text "a new service is proposed by Fournix: connect on fournix.com", The model Mn (GB) corresponds to the text "a new service is offered by Foumix: connect to the site fournix.com".

The two models Mn (GB) and Mn (FR) therefore correspond to the same content expressed in different languages. The IDG_p group has two message templates:

Mp (French) (X, Y) ₁ Mp (English) (X, Y).

The "French" and "English" languages are subsequently represented by "FR" and "GB" respectively.

The models Mp (FR) (X, Y) and Mp (GB) (X, Y) correspond to the same content expressed in different languages.

X and Y are generic parameters, whose value is to be informed later.

The IDG_k group has a message template: Mk (Z). The model Mk (Z) corresponds to the following content: "a reduction of Z is granted to you on your Fournix invoice".

Z is a generic parameter, the value of which is to be entered later.

The administration block 26 allows operators to make additions, deletions, modifications relative to the message templates stored in the storage block 24.

The operation of the service generation module is described below with reference to FIGS. 1 and 2.

The service provider "Fournix" 3 sends a request R1 to the message generation module 2. The request R1 commands the sending of a message to the user U1. This message is intended to warn the user U1 of the opening of a new service proposed by Fournix.

The request R1 contains in this example the identifier of the service provider 3 IDfournix, the identifier of the user U1 IDLM, the identifier of the messaging mode, in this case IDM_email identifying the email, retained by the provider and the user. ID of an IDG_n group.

The request processing block 21 receives the request R1. It consults the memory block 24 of message templates and thus determines that you message template group IDG_n has two message templates depending on the language of expression of the content (French or English).

The messaging mode is specified by the service provider 3 in the request R1, via the identifier IDM_email: it is about the electronic mail.

Since the language of the message to be sent is not specified in the request R1, the request processing block 21 sends to the set of databases BDD a request to know the preferred communication language of the identified user U1. by IDlM and the email address of this user. The database BDD sends a response to the request processing block 21, indicating that the preferred language of the user U1 identifier IDU_1 is English and indicating the email address of this user. The request processing block 21 then writes a request R1bis intended for the message management block 23, comprising the elements necessary to enable it to select a message template from the message templates of the group identified by IDG_n in the request R1 received by the message generation module 2, and to enable it to send in the specified messaging mode, a message corresponding to this message template selected to the user identified in the request R1.

The request processing block 21 thus completes the request R1 as a function of data specific to the user so as to allow the selection of a message template and the generation of a message comprising as skeleton the message template selected in the document. desired format.

Thus, the request R1bis comprises the following elements: the message template group identifier IDG_n, the identifier of the service provider

SDfournix, the identifier of the user IDU-1 and his email address, the selected mail mode: email identified by the identifier IDM_email, the language of expression of the content of the message: English.

On receipt of this request R1bis, the message management block 23 selects in the group of message templates IDG_n of the storage block 24, the message template in English, Mn (GB). Then the message management block 23 makes a copy of the selected message model Mn (GB), informs the address of the recipient of the message with the email address of the user U1 and the address of the sender of the message with that of Fournix. The mode of messaging indicated in the request R1 bis being the email, the message handling block 23 makes the necessary adaptations on the message thus constituted, to make it conform to the format of the email messages. He thus obtains an M1 message, in a format adapted for electronic mail, whose content is "ready for delivery".

The selected messaging mode being the electronic mail, the message management block 23 sends M1 to the SMTP / POP server 8, for the latter to e-mail it in the mailbox of the user LM, where this The latter will be able to consult it via his computer 17.

The message management block 23 then updates the history 25 by indicating the sending of the message M1.

In one embodiment, when the message generation module 2 receives a message from one of the routing points, for example the server 8, the message management block

23 determines whether the message received follows a message previously sent by the message management block to the point of routing.

Then, if it is indeed a message M 'that follows a message M previously sent by the message generation module 2, the relevant elements that are contained in M', for example an acknowledgment of delivery to recipient of the message M sent by the module or a response from the user, are extracted by the message management block

23. These elements, as well as the data enabling identification of the initial message M, are then sent to the service provider for whom the message M had been sent.

Thus, the message generation module 2 performs session management on behalf of the service providers. Service Provider 4, Urmix, is a manager of access rights to users' personal data. It is thus frequently required to notify users of the access of third parties to data (for example to the credit of the current account, to postal or electronic coordinates) concerning these users.

In the example now described, the service provider 4 sends a request R2 to the message generation module 2. The request R2 commands the sending of a message to the user U2. This message is intended to warn the U2 user that a third party, the online shopping service "ServAchat", has requested access to his personal data and indicating the credit of his current account.

The request R2 contains the identifier of the service provider 4 IDurmix, the identifier of the user U2 IDU_2, the value "ServAchat" intended to fill in the parameter X, the value "debit of the current account" intended to fill in the parameter Y and the ID of an IDG_n message template group.

Similar to what has been previously described, the request processing block 21 receives the request R2, consults the message template storage block 24 and thus determines that the message template group IDG_n has two message templates. Each model corresponds to a language of expression of the same content among the French and English languages. In addition each of these models is expressed according to two generic parameters X and Y.

The language of the message to be sent and the messaging mode to be used are not specified in the request R2, the request processing block 21 sends to the set of databases BDD a request to know the language of communication U2 user preferred identifier identified by IDU_2, U2's preferred messaging mode and that user's address for this preferred messaging mode. The database BDD sends a response to the request processing block 21, indicating that the preferred language of the U2 user identifier IDUJ2 is French, the preferred messaging mode is the SMS, identifier IDM_SMS and indicating him the mobile phone number of this user U2.

The request processing block 21 then writes a request R2bis intended for the message management block 23, comprising the following elements: the message template group identifier IDG_p, the IDurmix service provider identifier, the identifier of the IDU-2 user and his mobile phone number, the chosen messaging mode: SMS, identified by IDM_SMS, the language of expression of the message content: French, the value "ServAchat" intended for the generic parameter X and the value "Current account credit" for the generic parameter Y.

Upon receipt of this request R2bis, the message management block 23 selects in the group of message templates IDG_p, the message template in French language, Mp (FR) (X, Y). It makes a copy of this selected message template, replaces the X and Y generic parameters with the values specified in the T2bis query, and thus obtains a message whose content is "the ServicePurchase service wanted to access your Credit account attribute: OKAY ? "

Then the message handling block 23 fills the number of the recipient of the message with that of the user U2 indicated in the request R2bis and the number of the issuer of the message with the number of the service provider Urmix. It makes the necessary adaptations on the message thus formed so that it conforms to the format of the SMS messages, and obtains the message M2 thus ready to be transmitted.

The chosen messaging mode being SMS messaging, the message management block 23 sends the message M2 to the SMSC 6, so that it sends it on the mobile network 9 to the user U2, via his telephone. mobile 11.

The message management block 23 then updates the history 25 by indicating the sending of the message M2. Subsequently a message M2 'from the SMSC 6, indicating that the message M2 has been sent to the user U2 is received by the message management block 23, which determines that the message M2' received follows the message M2 previously sent. The evidence that this shipment was These elements, together with the data for identifying the initial message M2, are then sent to the Urmix 4 service provider.

Then another message from the SMSC 6, from the user U2 indicating that the user U2 agrees to allow access of the service ServAchat current account credit information, is received by the management block messages 23, which determines that this message received follows the message M2 previously sent. The elements indicating the agreement of the user U2 are extracted by the message management block 23. These elements, as well as the data enabling identification of the initial message M2, are then sent to the service provider 4, which goes to Using this data, do the necessary to let the Service BuyPak access the credit data of the current account of the user U2.

In another example, the service provider 3 sends an R3 request to the message generation module 2, which commands the sending of a message to a user group comprising the users U1, U2 and

U3. This message is intended to warn users that a 15% discount is given on their bill.

The request R3 contains the identifier of the service provider 3 IDfournix, the user identifier U1, U2 and U3 IDLM, IDU_2 and IDU_3, the value "15%" intended to fill in the parameter Z and the identifier of a group of message templates, IDG_k.

As seen previously, the request processing block 21 receives the request R3, consults the block 24 for storing message templates and thus determines that the message template group IDG_k comprises a message template. The model is expressed according to a generic parameter Z.

The request processing block 21 sends to the set of databases BDD a request to know the elements that are not specified in the request R3 and which are necessary for the generation and sending of messages, c that is, the preferred messaging mode of U1, U2, U3 and the addresses or numbers of the users U1, U2, U3 in their preferred messaging mode. The database BDD sends a response to the request processing block 21, indicating that the preferred messaging mode of U1 is the email and providing the email address of the user U2. The answer also specifies that U2's preferred messaging mode is the SMS and provides the mobile phone number of the user U2. The answer finally indicates that the preferred messaging mode of U3 depends on its presence information handled by the instant messaging service.

The processing block 21 then requires from the set of databases BDD what is the mail mode currently indicated in the presence information for the user U3.

The response from the BDD indicates that it is MMS messaging and provides it with the mobile phone number of the user U3.

The request processing block 21 then writes three requests

R3bisa, R3bisb and R3bisc for the message management block 23, each comprising the following elements: the IDG_k message template group identifier, the IDservix service provider identifier, the value

"15%" for the generic parameter Z.

The request R3bisa also contains the identifier of the user U1 IDU-

1, its email address and the identifier of the chosen mail mode: IDM_email.

The request R3bisb furthermore contains the identifier of the user U2 IDU-

2, its mobile number and the identifier of the chosen mail mode: IDM_SMS.

The request R3bisc also contains the identifier of the user U3 IDU-3, his mobile number and the identifier of the chosen mail mode:! DM_MMS.

On receipt of each of these requests R3bisa, R3bisb and R3bisc, the message management block 23 selects in the group of message templates IDG_k. It makes a copy of this message template, replaces the generic parameter Z with the value of "15%" indicated in the requests R3bisa, R3bisb, R3bisc and thus obtains three respective messages M3a, M3b, M3c whose content is "a reduction 15% is granted to you on your Fournix invoice ", Then the message management block 23 fills the address of the recipient of the message M3a with the email address of the user U1 indicated in the request R3bisa, informs the number of the recipient of the message M3b with that of the user U2 indicated in the request R3bisb and finally informs the number of the recipient of the message M3a with that of the user U3 indicated in the request R3bisc. It also informs the "issuer" field of the messages with the corresponding coordinates of the service provider 3.

The message management block 23 makes the necessary adaptations on the messages thus formed so that they conform to the format of the courier modes respectively retained, to obtain the messages M3a, M3b and M3c thus ready to be transmitted.

The mode of messaging retained for the message M3a being the electronic mail, the message management block 23 then sends the message M3a to the server 8, so that the latter transmits it on the Internet network 10 to the user LM, by the intermediate of his computer 17.

The messaging mode chosen for the message M3b being SMS messaging, the message management block 23 sends the message M3b to the SMSC 6, so that the latter transmits it on the mobile network 9 to the user U2, via from his mobile phone 11.

The messaging mode selected for the message M3c being the MMS message, the message management block 23 sends the message M3c to the MMSC 4, so that the latter transmits it on the mobile network 9 to the user U3, via 16. The message management block 23 then updates the history 25 by indicating the sending of messages M3a, M3b and M3c.

Subsequent receipt of each of M3a \ M3b 'and M3c' messages from the server 8, SMSC 6 and MMSC 7, respectively indicating that messages M3a, M3b and M3c have been sent respectively to the user LM, to the user U2 and the user U3, the message management block 23 determines that each of these received messages follows one of the three messages M3a, M3b and M3c previously sent, Then elements indicating that the sending of the message M3a was performed are extracts from the message M3a 'by the message management block 23 and are sent, as well as the data making it possible to identify the initial message M3a, to the service provider 3.

Likewise, such elements and data respectively relating to the message M3b and the message M3c are sent to the service provider 3.

The adaptations necessary to make the copies of the models conform to a format associated with a mode of messaging relate for example to the type of coding (for example, for the SMS, each character must be coded on 7 bits whereas for the email and the SMS characters are interpreted), on the location of the "issuer" and "recipient" fields.

The value of the variables in the examples described above is sent by the service provider in his request. In another embodiment, it could be identified by a value identifier by means of which the request processing block 24 could extract from the set of databases BDD the actual value corresponding to this value identifier.

All the steps performed above by the message generation module 2 are, in one embodiment of the invention, implemented by the execution, on the message generation module processing means, of the message generation module. a computer program. Thus the message generation module makes it possible centrally to create and send messages to users. The message template is a frame structuring the generated message.

The sent messages are customized by the module according to the intended users. Indeed, the language of the message and / or the format are chosen from several languages or formats by the message generation module based on personal data relating to the user of the message. Access to this data is limited to the generation module. When a service provider wishes to send messages of a new type, it is sufficient that he defines a group of message templates with a content possibly declined in several languages and / or with or without generic parameters.

Claims

A message generation module (2) for a telecommunication system, comprising:

an interface with at least one service provider (3);

an interface with at least one message routing point (8) for transmitting messages to users (U1, U2, U3) according to a given messaging mode; a storage base (24) for groups of message templates, at least one group being identified by a group identifier (IDG_n), and

means for, after receiving a request (R1) from a service provider indicating a group identifier and a user identifier, determining a message template (Mn (GB)) in the database storage and a message format associated with a messaging mode based at least on the user identifier and the group identifier;

means for generating a message (M1) according to at least the message template and the determined format and for transmitting it to the message routing point for routing the generated message, in the given messaging mode, to the user (U 1) identified in the request (R1).

2. Message generation module (2) according to the preceding claim, wherein a message group comprises several message templates corresponding to the same translated content in respective different languages, and wherein the module is adapted to determine a language in according to the identifier of the user indicated in the request, and wherein the message is generated according to the model in said language thus determined.

Message generation module (2) according to claim 1 or claim 2, adapted to interface with a plurality of message routing points (6, 7, 8) capable of transmitting messages in accordance with respective messaging, wherein the module is adapted to determine, based on at least the identifier of the user indicated in the request, one of a plurality of formats, each format being associated with one of said messaging modes; and wherein the message generated is a message in the format thus determined and transmitted to the message routing point suitable for transmission in accordance with the messaging mode associated with the determined format.

The message generation module (2) according to any one of the preceding claims, wherein the format is determined based on user information indicating an email mode currently preferred by the user.

Message generation module (2) according to any one of the preceding claims, wherein a message template of a group comprises at least one generic parameter (X, Y), said module being adapted for, following the receiving a request from a service provider further indicating a value for said generic parameter, generating a message (M2) in which the generic parameter has been replaced by said value.

A method of generating messages in a message generation module (2) for a telecommunication system, said module comprising: a storage base (24) for groups of message templates, at least one group being identified by a group identifier (IDG_n);

an interface with at least one service provider (3);

an interface with at least one message routing point (8) for transmitting messages to users

(U 1, U 2, U 3) in accordance with a given messaging mode; the method comprising the following steps:

- following the receipt of a request (R1) from a service provider indicating a group identifier and a user identifier, determine, based at least on the user identifier and the identifier group, a message template (Mn (GB)) in the storage base and a message format associated with a messaging mode;

generating a message (M1) based at least on the message model and the determined format; transmit the generated message to the message routing point for routing to the user identified in the request, in the given messaging mode.

7. Method according to claim 6, a message group comprising several message templates corresponding to the same translated content in respective different languages, comprising a step of determining a language according to the identifier of the user indicated in the request, the message being generated according to the model in said language thus determined.

A method according to claim 6 or claim 7, the message generation module (2) being adapted to interface with a plurality of routing points (6, 7, 8) of messages capable of transmitting messages in accordance with respective messaging modes, the method further comprising the steps of: determining a format according to at least the identifier of the user indicated in the request, from among a plurality of formats, each format being associated with one of said messaging modes, the message generated being a message to said format thus determined; selecting the message routing point suitable for transmission according to the messaging mode associated with the determined format, the message generated being transmitted to the said routing point selected for routing to the user identified in the request.

9. Method according to any one of claims 6 to 8, at least one message template of a group comprising at least one generic parameter (X, Y), according to which in the generated message (M2), the generic parameter will have has been replaced by a value for said generic parameter, indicated in the request (R2) received from a service provider (4).

Computer program adapted to be installed in a message generation module (2) for a telecommunication system, said module comprising: a storage base (24) of groups of message templates, at least one group being identified by a group identifier (IDG_n);

an interface with at least one service provider (3);

an interface with at least one message routing point (8) for transmitting messages to users (U 1, U 2, U 3) in accordance with a given messaging mode; said program comprising instructions for implementing the steps of a method according to any one of claims 6 to 9 during execution of the program by processing means of said message generating module.