GB2473038A

GB2473038A - A method of processing multiple message formats using a single identifier

Info

Publication number: GB2473038A
Application number: GB0915042A
Authority: GB
Inventors: Thorsten Trapp; Ralph Eric Kunz
Original assignee: Tyntec Ltd
Current assignee: Tyntec Ltd
Priority date: 2009-08-28
Filing date: 2009-08-28
Publication date: 2011-03-02
Anticipated expiration: 2029-08-28
Also published as: GB2473038B; GB0915042D0; WO2011023818A1

Abstract

A method of processing multiple message formats by assigning a single identifier, independent of the message format, per customer. The messages are received at a plurality of receivers and passed on to service providers by a single central platform, comprising a central server and central database. Message formats may be SMS, MMS, Voice call, video call, VoIP or Instant Messenger.

Description

Title: A method and apparatus for handling a message addressed to a single identifier

Cross-Reference to Related Application

[001] None.

Field of the Invention

[002] The field of invention relates to a method and apparatus for the handling of a multi-protocol message for an application. Tn particular, the field of the invention relates a method and apparatus for the handling of a message using one of a plurality of message formats with a unique identifier.

Background of the Invention

[003] Mobile telecommunications networks have become increasingly ubiquitous.

These allow a user to use a mobile station -such as a mobile telephone or a PDA -to communicate with others on the same mobile telecommunications network, on other mobile telecommunications networks or on fixed line networks. Increasingly the mobile telecommunications networks are being used to transfer data and instant messaging (TM) as well as voice.

[004] Initially, the data transfer was carried out using SMS messages. The SMS messages were designed to transmit a small amount of data such as short unformatted text messages over the network of a single mobile telecommunications networks operator. Each one of the mobile stations within the mobile telecommunications network is assigned a home Short Message Service Centre (SMS-C) which handles the SMS messaging for that mobiles station or user. As is known in the art, the SMS message is sent to the home SMS-C of the user originating the message. In order to route the SMS message to the intended recipient, a request for routing information is normally sent by the SMS-C to a Home Location Register (HLR) which contains information for the mobile station to which the SMS message is to be sent. The HLR supplies the required routing information to the SMS-C which then transmits the SMS message to the Visitor Location Register (VLR)i'Mobile Switching Centre (MSC) to which the intended recipient is connected. This procedure is described in the ETSI TS 100 974.

[005] The SMS message can also be sent to applications, such as computer application or databases. For example UK Patent Application No 2415577 (Yoomedia PLC) teaches an SMS-C which is provided with an application interface. The application is assigned, according to the teachings of this patent application, with what is known as a "short number" comprising a reduced number of digits compared to a usual format for the mobile numbers. Tn the example taught in the application the SMS-C was programmed to recognise the short numbers when they are received in the header of an SMS message so that the message is forwarded to the application interface rather than being routed across the mobile telecommunications network.

[006] Initially the application interfaces were intended to host proprietary applications for the networks of the network operators. The success of SMS messaging has meant that network operators now allow either an application from third parties to be directly connected to the application interfaces or for connections between the SMS-C and the Internet (or a proprietary network).

[007] In more recent developments, more than one network operator has adopted the same short code for the same application so that it becomes immaterial to which mobile telecommunications network the mobile station sending the SMS message is connected. In Germany, for example, common short numbers have been adopted by all of the four major mobile telecommunications networks to allow, for example, voting in television programmes. The mobile station connected to any of the four major mobile telecommunications networks can send an SMS message to the SMS-C responsible for the major mobile telecommunications network using the common short number. Each of the SMS-Cs will intercept the SMS message, recognise that is to be passed to a specified application via an application interface and will pass the SMS message to the application.

[008] European Patent Application No. EP 1 662 812 (Empower Tnteractive Group Ltd.) teaches a method for routing SMS messages to an application through a plurality of message delivery points in the same mobile telecommunications network. This has the advantage that the routing of the SMS messages can be changed to ensure that the load on the mobile telecommunications network is balanced.

[009] The teachings of the above patent applications rely on the use of a special common short number to identify those SMS messages which need to be "removed" from the usual message delivery service and treated in a different manner by forwarding them to an application. There is, however, a major restriction on the use of the common short numbers -their number is limited. Tn particular attempts to establish "international" common short numbers have foundered either on the unwillingness of some network operators to collaborate through fear of losing business (or lacking the appropriate software) or by the fact that the proposed numbers have been previously occupied.

[0010] In addition to SMS messages, mobile telecommunications networks nowadays carry data using several other protocols, for example MMS which uses an IP protocol. To use short codes also for this MMS service a special handling procedure is needed -similar to enabling SMS reception on short codes as mentioned above. In this case, it is in the MMSC of the mobile telecommunications network operator. To take one example, sending an MMS to a common short number designed for the receipt of a SMS message will -unless special software has been installed -lead to an error message or simply "get lost" as a receiver receiving the messages sent by the MMS protocol will generally not have been programmed with the common short number. There is therefore a need to develop a system which can take and receive messages in a variety of formats without the need to worry about which number is accessed.

[0011] The European patent application EP 1 601 146 (France Telecom) discloses a system for forwarding an email message to a recipient. The recipient is identified by its telephone number. The system includes the step of identifying the email address of the recipient associated with the telephone number.

[0012] The US patent US 6,625,258 (Nortel Networks Ltd.) describes a virtual assistant system. A profile services uniquely identifies each subscriber and provides contact information for the subscriber.

[0013] The France Telecom patent application and the Nortel Networks patent both teach systems for uniquely identifying a subscriber.

[0014] The international patent application WO 03/021900 (R. Agarwal et al.) teaches a system and a method which enable a first user to communicate in multiple telecommunications formats with a second user identified by a single user identifier, such as a telephone number or conventional e-mail address. A provider associated with the unified messaging server (UMS) identifies the format and can change the format. The provider transmits the message as a real time connection or as a non-real time connection.

To allow the exchange of messages also between more than one of the above mentioned UMS, the UMS must be directly connected with each other. The UMS defined in this patent application does not have the capability of being invoked from a different network which does not have a UMS server or does not have a UMS interconnection.

[0015] The UMS systems of the Agarwal patent application have the capability to handle messages using different type of formats, identify the format, and forward the message to the recipient in either the same format or another format.

[0016] The US patent application US 2006/0025 164 (Wang) also describes a Unified Message Service. Tn the system of the Wang patent, calls/messages are sent to a unified message service system node. The unified message service system node in turn forwards the call to a fixed/mobile phone, may send a fax, and may send SMS/instant messages to the intended recipient.

[0017] Another example of such Unified Message Service system is also disclosed in the German patent publication DE 101 21 705 (Web.DE AG).

[0018] The UMS systems of the prior art have different receivers capable of handling messages received in SMS and voice formats. The Agarwal, Wang or Web.DE patent applications disclose a centralized management of all incoming messages, using a single identifier for the incoming messages. Tn these prior art systems, the user needs to have subscribed to such a system, and all messages sent by the user are first received at a messaging server, which forwards the message to the intended recipient.

[0019] The applications accessed through the application interface can often only handle messages sent in a particular format. For example, an application connected to an SMS-C through the Internet will generally expect to see a message using the Internet Protocol.

[0020] Such attempts at the conversion of messages from one protocol to another are known in the past. A simple example is that which converts SMS messages sent to a fixed line number to voice messages. This is carried out by intercepting in the SMS-C any SMS message addressed to a fixed line number and passing this intercepted SMS message to a separate server. In the separate server the addressed fixed line number is first tested to see whether it has the capability to receive messages in an SMS format. If that is the case, then the SMS message is sent via the fixed line to the addressed telephone number. In the event, however, that the addressed fixed line number cannot accept the message in SMS format, the SMS message is converted to a voice message and the addressed fixed line number is rung and the intercepted message -as a voice message -is conveyed to a listener. This is disclosed in the article "BT trials mobile SMS to voice landline" by John Leyden published 8th January 2004 in the Register (URL: http://www.theregister.co.uk/2004'01/08/bt_ trials mobile sms/ accessed on 29 March 2006).

[0021] This solution to the delivery of SMS messages to the fixed line number is a useful tool. However, it cannot be generalised to the conversion of all types of protocols into other protocols.

[0022] US Patent Application US 2003/0104827 (Moran et al) discloses a method in which an SMS message is converted to an e-mail for transfer to another wireless access point. This is used to allow the delivery of SMS message to another wireless network in which there is no opportunity to exchange the SMS messages directly. It does not disclose, however, the passage of the SMS message in either SMS format or in e-mail format to an application.

[0023] There therefore remains a need for a system which can accept messages in any one of a multiple number of protocols and supply these to an application in the required protocol.

[0024] There is further a need for providing a universal number for the acceptance of messages in any one of a multiple number of protocols.

[0025] There is furthermore a need for allowing access to the same application using a number of different numbers.

[0026] There is further a need for providing a system which can be accessed by different networks (national or international).

Summary of the Invention

[0027] These and other objects of the invention are solved by providing a method for the handling of a message addressed to a single identifier for forwarding to a service provider, wherein the message uses one of a plurality of message formats. The method comprises: receiving the message at a receiving one of a plurality of receivers in one or more of a plurality of telecommunications networks, wherein the message uses one of a plurality of message formats, the one of the plurality of message formats being independent of the single identifier, wherein the message is received at different ones of the plurality of receivers in accordance with the one of the plurality of message formats, passing the message from the receiving one of the plurality of receivers to a central platform, wherein the central platform is connected to more than one of the plurality of receivers; informing the service provider about the message and forwarding the message from the central platform to the customer if the service provider accepts the message, wherein the single identifier is chosen from a plurality of identifiers provided to the central platform by the one or more telecommunications networks, the single identifier being assigned to a customer.

[0028] The message may be forwarded either in the one of the plurality of message formats or in another one of plurality of message formats.

[0029] The central platform may use an IP network protocol for forwarding the message.

[0030] The single identifier may be a MSTSDN according to the ITU-T E.164 Standard or a NANP (North American Numbering Plan) Standard or any other numbering format routable in international telecommunications network.

[0031] The single identifier may define an application that is to be addressed by or connected with the network communication.

[0032] The network communication may be a voice call, such as a PSTN, 3G or GSM communication, a video call, especially but not limited to H.324rn (3GPP) (see http://de.wikipedia.org/wikil3g-h.334.m; accessed on 27 August 2009), or a data communication in form of a message. The format may be selected from one of the formats consisting of PSTN Circuit switched Voice, SMS, MMS, VoIP, and Instant Messenger (e.g. XMPP as defined in RFC 3920) but is not limited thereto.

[0033] The method may further comprise terminating the protocol at one of the plurality of the receivers and passing the network communication from the terminating one of the plurality of the receivers to the central platform using a transport protocol. Thereby, transparent and non-transparent modes can be used and mixed.

[0034] An apparatus is also disclosed for the handling of a message addressed to a single identifier for forwarding to a service provider, wherein the message uses one of a plurality of message formats. The apparatus comprises a plurality of receivers for receiving the message, different ones of the plurality of receivers being configured to receive the message in different ones of the plurality of message formats, at least two of the plurality of receivers being connected to different ones of a telecommunications network, a central platform connected to the plurality of receivers; and a connection to the service provider for informing the service provider about the message and for forwarding the message from the central platform to the service provider if the service provider accepts the message. The single identifier is chosen from a plurality of identifiers provided to the central platform by the one or more telecommunications networks, the single identifier being assigned to a customer.

[0035] The apparatus may be adapted to forward the message either in the one of the plurality of message formats or in another one of plurality of message formats.

[0036] The central platform may be adapted to forward the message using an IP network protocol.

[0037] A protocol terminator at at least one of the plurality of receivers may be used to for terminating.

[0038] A network device may be provided for transmitting the network communication from the one of the plurality of receivers to the central platform using a transport protocol.

[0039] The connection to the customer for forwarding the message from the central platform to the customer may be adapted for handling a plurality of codecs.

[0040] A system with a central platform comprising a central database and a central server is also disclosed.

[0041] The central database preferably comprises settings associated to the single identifier, the central platform being adapted to choose one of the plurality of codecs depending on the settings.

[0042] The system is adapted to handle connections using transport protocol

Description of the Figures

Fig. 1 shows a customer edge of a telecommunications network according to the state of the art.

Fig. 2 shows a customer edge of a telecommunications network according to the invention.

Fig. 3 shows an embodiment of a central platform according to the invention Fig. 4 shows a workflow for the receipt of a message using a single identifier according to the invention.

Detailed Description of the Invention

[0043] Fig. 1 shows a telecommunications network 5 as known in the art. The telecommunications network 5 is suitable for both voice and data transmission and can operate with a number of different protocols as will be explained below. The telecommunications network has a media gate way (MGW) 10 which receives communication items in the form of standard Public Switched Telephone Number (PSTN) telephone call or a voice over IP (VOIP) communication. In prior art systems, a PSTN identifier, such as a telephone number, may be used for addressing both the PSTN telephone call and the VOIP communication. Prior art systems may also employ a different identifier, such as an additional telephone number or a user name for a VOTP communication.

[0044] The communication item is terminated at the MGW 10 and redirected or further transmitted to a central platform 30 using another protocol. For example, an incoming PSTN telephone call is received at MGW 10 and redirected to the central platform using the IP protocol.

[0045] It should be noted that the MGW 10 can receive communications items using other protocols such as the H324m protocol which is used, for example, for 3G-Video calls.

[0046] The MGW 10 is typically installed at a location managed and run by an operator of a PSTN network or VoIP service. The central platform 30 is typically located at a site of a service provider which offers the unified access to cross network reception and processing of multi protocol communication services. The central platform 30 is connected to the MGW 10 through fixed telecommunication lines which may or may not be part of a PSTN network or the Internet. Dedicated telecommunications lines may also be used in the event that a high degree of security is required. The central platform 30 will direct the communication item received from the MGW 10 to, for example, a customer system 40.

The customer system is a suitable telecommunications device which can process the communication item.

[0047] Fig. 2 shows the telecommunications networks 5 and 50 according to the invention. The telecommunications network 50 comprises in this aspect of the invention a second receiver 12 and a second MGW 11. The second receiver 12 will be, for example, a Home Location Register (HLR) and Visitor Location Register (VLR)/Mobile Switching Centre (MSC) for receiving communication items in yet a further format. In the example shown in Fig.2 the second receiver 12 is connected to a mobile telecommunications network. This mobile telecommunications network 50 uses, for example, the SS7 protocol for the reception of SMS messages over the mobile telecommunications network 50. The SMS messages can not be handled by the second MGW 11.

[0048] The second receiver 12 receives the communication item via SS7 MAP and transfers the communication item via a transport protocol, for example IP, to the central platform 30 from where the communications item is further transferred to the customer system 40. The transfer of the communications item from the central platform 30 to the customer system 40 is carried out using, for example, the IP protocol.

[0049] The telecommunications network 50 shown in Fig 2 also comprises in this aspect of the invention a third receiver 13 besides the MGW 11 and the HLR/MSC 12. The third receiver 13 will be, for example an instant messaging server for receiving communication items in a further format. In this example shown in Fig.2 the third receiver 13 is connected to public internet and uses, for example, the XMPP protocol (as defined in RFC 3920) for the reception of instant messages. The instant messages can not be handled by the second MGW 11 or the HLR/MSC 12.

[0050] The third receiver 13 receives the communication item via IP and transfers the communication item via a transport protocol, for example IP, to the central platform 30 from where the communications item is further transferred to the customer system 40. The transfer of the communications item from the central platform 30 to the customer system is carried out using, for example, the TP protocol.

[0051] Each of the communication items received by either the first MGW 10 or the second MGW 11 or the second receiver 12 uses a single identifier for identifiying the customer system 40 to be reached. For the third receiver 13 the single identifier must be expanded by @server.name' in the XMPP example (where "server.name" is a place holder for the real domain name of the XMPP server). The single identifier may be a MSISDN number (as defined by the ITU-T El 64 standard) or a number assigned under the North American Numbering Plan (NANP) of the customer or any other numbering format routable in international telecommunications network. This is advantageous as it means that the customer needs to only provide a single number to its potential customers for communications purposes. So, for example, a company advertising its products can give a single hotline number reachable by all forms of telecommunications. A consumer can chose to dial the number from his or her mobile telephone and the call will be received and terminated at the second receiver 12, converted to a first type of transport protocol and passed to the central platform 30 from which the call is passed to the customer system 40 (possibly via a second type of transport protocol). The consumer could also send a text message to the second receiver 12 where the text message is terminated according to ETSI TS 100 974 and transferred via the first type of transport protocol to the central platform 30 and then to the customer system 40. If the consumer uses a telecommunication device connected to the PSTN, then the call is received and terminated at the first MGW 10 and the second MGW 11 and transmitted via a third type of transport protocol (which could be the same as the first type of transport protocol) to the central platform 30 and thence to the customer system 40.

[0052] Another type of use case would be voting in a television programme. Currently it is necessary to allocate different telephone numbers for voice calls and SMS messages.

Using the invention a single number could be allocated. Viewers of the television programme could chose to vote, for example for candidate one, by either texting the message to a number of the format 07624 80070 -1 (or alternatively 0044 7624 80070-1 if an international dialling code is introduced) or dialling exactly the same number. If the dialled number was made over the PSTN then the communications item is received at the MGW 11, passed to the central platform 30 and then to the customer system 40. The customer system 40 will have a counter counting the number of communications items received in total. Tt should be noted that in this case the communication item is not a voice message but a message indicating a vote for candidate 1 even though the communications item is initially transmitted over the PSTN. If the viewer using a mobile telephone to dial the number 07624-80070-1 then the communications item will be carried over the international telecommunications network to the first receiver 11 where the communications item is received and terminated and passed from the first receiver 11 to the central platform 30 and finally to the customer system 40 where the vote is recorded at the counter. Similarly an SMS message could be sent to exactly the same number and will be received at the second receiver 12 before being passed to the central platform 30 and the customer system 40 and counted. The counter at the customer system 40 records all of the communications items received at the MGW 11 and/or the second receiver 12 and counts the communications items as votes for the candidate one. This scenario is not limited to the communication items initiated in the network 50 but also applicable for the communication items initiated in any one of the other telecommunications network having interconnection with the telecommunications network 50. Further the central platform 30 can have multiple connections to different ones of the network 50 or the network 5 and aggregates all telecommunications items passed through via a receiver to the attached customer systems 40. The exchange format is determined by the suitable protocol for each communication and on a mutual agreement on the customer and its provider for the unified access to the cross network reception and processing of multi protocol communication services.

[0053] It is important to note that communications items sent in different formats may be received by different ones of the receivers (i.e. the MGW 11 or the second receiver 12).

The transfer to the central platform 30 can be made using the same format but is more likely to be made in a common format (e.g. carried via the IP format). Some of the receivers may be able to accept multiple protocols. Other ones of the receivers will only accept a single type of protocol. The MGW 11 and the second receiver 12 are shown in Fig. 2 as being separate units. However, there is nothing to stop them being incorporated on the same computer server.

[0054] There are different outputs from the operator to a central platform 30, as shown in Fig. 3. A first output (SMS output) is for SMS messages. A second output (fax/voice output) is for voice/fax messages. A fax switch is connected to the voice/fax messages to separate voice messages and faxes. There could also be further units connected to the output from the operator. Examples of such further units include units for handling 3G calls or video calls.

[0055] Fig. 3 shows the central platform 30 according to one aspect of the disclosure.

[0056] The central platform 30 includes a central server 300 and a central database 310 connected to the central server 300. The central server 300 has connections 322 and 323 to the receiver 10 of the telecommunications network 5 and connections 324, 325 and 326 to the receivers 11, 12, 13 of the telecommunications network 50. The central server 300 has also a connection 340 to the customer system 40.

[0057] The central server 300 manages the plurality of identifiers provided by the telecommunication networks 5, 50. A unique single identifier is assigned to a customer and is chosen from the plurality of identifiers. The telecommunications networks 5, 50 may be located in different countries and the identifiers provided by the telecommunications networks 5, 50 may include numbers comprising country code.

[0058] The identifiers are preferably a MSISDN identifiers according to the ffU-T E. 164 or NANP Standard. The identifier could be of any other numbering format routable in international telecommunications network.

[0059] The identifiers are stored in the central database 310 along with other features and reach lists.

[0060] The central database 310 also stores settings associated with the identifiers or with the different telecommunications networks 5, 50 or operators.

[0061] The central server 300 can chose an appropriate codec to use depending on the settings stored in the central database 310. The appropriate codec to be used may be chosen on a number of factors including call quality and bandwidth capacity. Non-limiting examples the appropriate codecs include a G7-1 1 codec or a G7-29B codec.

[0062] Although the system of this disclosure has been described with respect to two telecommunication networks 5, 50, the present system is not limited to two telecommunication networks 5, 50 and a plurality of the telecommunication networks 5, 50 can be connected to the central platform 300. It will be understood that the telecommunication networks 5, 50 connected to the central platform 300 may be from different countries and of different types. The central platform 300 is adapted to operate over multiple operators and countries.

[0063] A method for the receipt of the message addressed to a single identifier for forwarding to the customer is described with reference to figure 4.

[0064] The user wishing to contact the customer may use the single identifier assigned to the customer. The single identifier is preferably a MSISDN according to the ITU-T E.164 or NANP Standard.

[0065] The message can be sent using a plurality of message formats, including SMS, MMS, Voice Call, Video Call, VoTP or Tnstant Messenger.

[0066] The SMS message formats use a signalling protocol. The Voice/Fax/Video message formats use a TDM protocol. The MMS message formats use IP signalling.

[0067] In this aspect, the user wishes to call the customer, at step 100. The message is received at the second receiver 12 of the telecommunication networks 50. The second receiver 12 is the one receiver of the telecommunication networks 50 that is adapted to receive the communication item in the call format (step 200).

[0068] The second receiver 12 first accepts an incoming call/message request as Tnitial Address Message (lAM) which includes the destination message number. The second receiver 12 identifies this destination message number as the single identifier number for the customer. The second receiver passes 12 the message to the central platform 30, at step 300.

[0069] The central server 300 of the central platform 30 converts the incoming call request in the form of SS7-IAM as a session initiation protocol (SIP) request (using the RFC 3398 standard -see http://tools.ietf.org/htm1/rfc3398; accessed on 27 August 2009) to the customer system 40 (including destination number and, if known, caller number), at step 400.

[0070] The customer system 40 accepts the SIP-Request and decides whether to accept the incoming call request to the destination number or not. The customer system 40 answers the central server 300 via a further SIP message. This further SIP message may be either busy, hang up or accept call. If the incoming call is to be accepted the further SIP message includes any settings for handling the incoming call. These settings may include the appropriate codec for handling the incoming call. For example, the customer system 40 may have established that the codec using least bandwidth be used. The use of this codec would reduce cost associated with handling the incoming call, but at expense of call quality. On the other hand, the codec providing best call quality can be specified which would increase the amount of the bandwidth required for handling the incoming call.

[0071] If the customer system 40 accepts the message, the central server 300 passes an acceptance to the second receiver 12 which then accepts the incoming call, encodes the incoming call with the appropriate code and passes the encoded incoming call message is passed to the customer system 40 where the incoming call is handled (step 600).

[0072] There are a number of different manners in which the customer system 40 could handle the incoming call. SMS could be displayed in mail system. Voice call could ring on computer. The incoming call (in this case a voice call) could be passed directly to a regular telephone, a mobile telephone or a computer. The incoming call could be stored as WAV file and sent to a mail system or the incoming call could be passed to a voice box (as governed by RFC 3666). If the incoming message were not the voice call, but the SMS message, then the SMS message could be sent to a regular email system or passed to a mobile telephone for display to the user. Similarly if the incoming message were a fax message, then the incoming message could be passed the email system as an email or PDF fax or even using text-to-speech technology passed to the telephone of the user. It will be appreciated that other combinations of handling the incoming message by the customer system 40 are possible.

[0073] In the specific aspect discussed above, the incoming message is forwarded to the customer system 40, the connection using an lIP protocol. The SMS messages may be transferred using SMPP/SIP protocol. The voice messages may be transferred using VoTP protocol. The fax messages may be transferred using TDM protocol, and the video calls using a combination of VoIP and Video over IP protocols.

[0074] It will be noted that the incoming message may be forwarded to the customer either in the same format as the format used by the caller or in another format. The customer may have indicated preferences for receiving message in preferred communication format. In other words, the apparatus may act as a transcoder which may transcode one communication protocol into another communication protocol.

[0075] Tt will be understood from the above description that the service provider can have access to multiple operators in multiple countries. This allows choice of the communication networks which may be used. The choice can be made on economic (e.g. cost), accessibility or quality criteria. The apparatus of the present disclosure can be understood as a multiple protocol receiver that manages a number of connected systems and networks, centrally.

[0076] The above description of the illustrated embodiments of the invention is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Whilst specific embodiments of, and examples for, the invention are described herein for illustrative purposes, various equivalent modifications are possible within the scope of the invention as those skilled in the relevant art will recognise. Accordingly it is not intended that the scope of the invention in any way be limited by the above description, but instead be determined entirely by reference to the claims.

Claims

Claims 1. A method for handling a message addressed to a single identifier for forwarding to a service provider, wherein the message uses one of a plurality of message formats, comprising: -receiving the message at a receiving one of a plurality of receivers in one or more of a plurality of telecommunications networks, wherein the message uses one of a plurality of message formats, the one of the plurality of message formats being independent of the single identifier, wherein the message is received at different ones of the plurality of receivers in accordance with the one of the plurality of message formats; -passing the message from the receiving one of the plurality of receivers to a central platform, wherein the central platform is connected to more than one of the plurality of receivers -informing the service provider about the message; and -forwarding the message from the central platform to the service provider if the service provider accepts the message, wherein the single identifier is chosen from a plurality of identifiers provided to the central platform by the one or more telecommunications networks, the single identifier being assigned to a customer.
2. The method of claim 1, the message is forwarded either in the one of the plurality of message formats or in another one of plurality of message formats.
3. The method of any one of the above claims, wherein the central platform uses an IP network protocol for forwarding the message.
4. The method of any one of the above claims, wherein the handling of the message comprises at least one of accepting the message, refusing the message, and establishing settings for acceptance of the message.
5. The method of any one of the above claims, wherein the single identifier is a MSTSDN according to the TTU-T E. 164 or NAINP Standard or any other numbering format routable in international telecommunications network.
6. The method of any one of the above claims, wherein the single identifier identifies an application.
7. The method of any one of the above claims, wherein the message format is selected from one of the formats consisting of SMS, MMS, Voice Call, Video Call, VoIP or Instant Messenger.
8. The method of any one of the above claims further comprising: -terminating the protocol at one of the plurality of the receivers and passing the message from the terminating one of the plurality of the receivers to the central platform using a transport protocol.
9. The method of any one of the above claims ftirther comprising forwarding the message to at least one of a mailbox, a mobile station and an email client.
10. An apparatus for handling of a message addressed to a single identifier for forwarding to a service provider, wherein the message uses one of a plurality of message formats, comprising: -a plurality of receivers for receiving the message, different ones of the plurality of receivers being configured to receive the message in different ones of the plurality of message formats, at least two of the plurality of receivers being connected to different ones of a telecommunications network, -a central platform connected to the plurality of receivers; and -a connection to the service provider for informing the service provider about the message and forwarding the message from the central platform to the service provider if the service provider accepts the message, wherein the single identifier is chosen from a plurality of identifiers provided to the central platform by the one or more telecommunications networks, the single identifier being assigned to a customer.
11. The apparatus of claim 10, wherein the apparatus is adapted to forward the message either in the one of the plurality of message formats or in another one of plurality of message formats
12. The apparatus of one of claims 10 or 11, wherein the central platform is adapted to forward the message using an IP network protocol
13. The apparatus of one of claims 10 to 12, wherein the single identifier is a MSTSDN according to the fFU-T E.164 or NANP Standard or any other numbering format routable in international telecommunications network.
14. The apparatus of one of claims 10 to 13, further comprising a protocol terminator at at least one of the plurality of receivers, wherein the protocol terminator terminates the protocol at the at least one of the plurality of receivers.
15. The apparatus of one of claims 10 to 14, further comprising a network device for transmitting the message from the one of the plurality of receivers to the central platform using a transport protocol.
16. The apparatus of one of claims 10 to 15, wherein the single identifier identifies the application to be run on receipt of the message.
17. The apparatus of one of claims 10 to 16, wherein the connection to the service provider for forwarding the message from the central platform to the customer is adapted for handling a plurality of codecs.
18. The apparatus of one of claims 10 to 17, wherein at least one of the plurality of receivers is adapted to encode the message using one of a plurality of codecs.
19. The apparatus of one of claims 10 to 18, wherein the central platform comprises a central database and a central server.
20. The apparatus of claim 19, wherein the central database comprises settings associated to the single identifier, the central platform being adapted to specify one of the plurality of codecs depending on the settings.
21. The apparatus of one of claims 10 to 20, further comprising at least one of a mailbox, a mobile station and an email client connected to the service provider.
22. A system for handling a message addressed to a single identifier for forwarding to a service provider, wherein the message uses one of a plurality of message formats, the central platform comprising a central server adapted to be connected to a plurality of receivers for receiving the message, different ones of the plurality of receivers being configured to receive different ones of the messages in different ones of the plurality of message formats, at least two of the plurality of receivers being connected to different ones of a telecommunications network, a connection to the customer for informing the customer about the message and forwarding the message from the central platform to the customer if the customer accepts the message; and a central database connected to the central server, wherein the single identifier is chosen from a plurality of identifiers provided to the central platform by the one or more telecommunications networks, the single identifier being assigned to the customer.
23. The system of claim 22, wherein the central database comprises settings associated to the single identifier, the central platform being adapted to choose one of the plurality of codecs depending on the settings.
24. The system of one of claims 22 or 23, wherein the connection to the customer for forwarding the message from the central platform to the customer is adapted for handling a plurality of codecs.
25. The system of one of claims 21 to 24, wherein the system is adapted to handle connections using a transport protocol.
26. The system of one of claims 21 to 25, wherein at least one of the plurality of receivers is adapted to accept the message in a fax format and a voice format and forwards the message over different ones of the connection to the central server.