Method and message server for conveying messages in a telecommunications network

• US 20040053629A1
• Filed: 07/01/2003
• Published: 03/18/2004
• Est. Priority Date: 01/08/2001
• Status: Abandoned Application

• Current Assignee: bmd wireless AG (West Corporation)
• Original Assignee: bmd wireless AG (West Corporation)
• Inventors: Woog, Mark A., Rueger, Brian P.
• Application Number:
  US10/250,425
• Publication Number:
  US 20040053629A1
• Time in Patent Office: Days
• US Class Current: 455/466
• CPC Class Codes: H04L 51/06 Message adaptation to terminal or network requirements
• CPC Class Codes: H04L 51/066 Format adaptation, e.g. format conversion or compression
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• CPC Class Codes: H04L 61/4557 Directories for hybrid networks, e.g. including telephone numbers
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 88/184 Messaging devices, e.g. message centre
• CPC Class Codes: H04W 92/02 Inter-networking arrangements

Abstract

The method, message server and the telecommunications network allow to convey messages, particularly short messages, originating in a mobile telecommunications network such as the GSM system and terminating at a recipient application or a related service in an IP-network not using the standards of said mobile telecommunications network. The inventive telecommunications network comprises a message server (WAMS) through which messages arriving at a first service centre (SC2) can be routed to a second service centre (SC1) which is connected to the recipient application or the related service. According to the inventive method a virtual mobile station number is established as the address for the recipient application, to which the entire community of short message mobile stations MS can originate messages as it would originate them towards a real mobile station MS.

Claims

1. A method for conveying messages, particularly short messages, originating in a mobile telecommunications network such as a GSM, TDMA, CDMA or 3G (MMS) system and terminating at a recipient application (ESME, PC1, PC2, . . . ) or a related service in a network such as an IP-network which is not using the standards of said mobile telecommunications network comprising the steps of

a) providing a message server (WAMS) using signalling functions, such as the functions of the Signalling System Number 7, according to the standards of said mobile telecommunications network;

b) providing a database (HLRx) in said message server (WAMS) comprising routing information to said recipient application (ESME, PC1, PC2, . . . ) or the related service;

c) providing a switching function (MSCx) for transferring messages according to retrieved routing information;

d) an originating mobile station (MS) selecting an address of said message server (WAMS) as destination address which corresponds to a recipient application (ESME, PC1, PC2, . . . );

e) transmitting the message from the mobile station via a first service centre (SC2)to the message server (WAMS);

f) retrieving routing information from the database (HLRx, TB) based on the provided destination address and

g) forwarding the message by means of the switching function (MSCx) in the message server (WAMS) to the recipient application (ESME, PC1, PC2, . . . ) or the related service, or to a location accessible by the recipient application (ESME, PC1, PC2, . . . ) or the related service.

2. Method according to claim 1, wherein the message server (WAMS),

a) forwards messages via a service center (SC1) to recipient applications (ESME, PC1, PC2, . . . ),

b) terminates messages in a protocol stack comprising the layers of the signalling system and the short messaging system of the mobile telecommunications network (PLMN) and then stores the extracted contents, such as the user data of a protocol data unit SMS-DELIVER, in a storage facility (HLRx, TB, HD, DBMS) which contents are then, directly or via a proxy server, forwarded to or retrieved by the recipient applications (ESME, PC1, PC2, . . . ),

c) terminates messages in a protocol stack comprising the layers of the signalling system and the short messaging system of the mobile telecommunications network (PLMN) and then pushes the extracted contents, such as the user data of a protocol data unit SMS-DELIVER directly or via a proxy server to the recipient applications (ESME, PC1, PC2, . . . ) or

d) forwards messages to recipient applications hosted and/or operating within the message server (WAMS).

3. Method according to claim 1 or 2, wherein the message server (WAMS), comprising a gateway function (GW-FUNCTION),

a) in a first protocol stack terminates messages received from the mobile communications network and/or

b) in a second protocol stack terminates messages received from external short message entities (ESME, PC1, PC2, . . . );

operating in a different network, such as an IP-network;

thereby extracting the contents of the messages, which then, across the complementing second or first protocol stack, are transferred to their destinations;

or which are stored and then retrieved by addressed short message entities (ESME, PC1, PC2, . . . ).

4. Method according to claim 1, 2 or 3, wherein the message server (WAMS), acting as short message service center, transfers messages between

a) short message entities, such as mobile stations (SME, MS1, MS2, . . . ) internal to the mobile telecommunications network (PLMN);

b) short message entities (ESME, PC1, PC2, . . . ), such as recipient applications in an IP-network, external to the mobile telecommunications network (PLMN); and

c) in both directions between internal short message entities (SME, MS1, MS2, . . . ) and external short message entities (ESME, PC1, PC2, . . . )

and further, as enhanced short message service center, transfers messages from internal short message entities (SME, MS1, MS2, . . . ) to external short message entities (ESME, PC1, PC2, . . . ) by means of destination addresses of virtual mobile stations that correspond to recipient applications (ESME, PC1, PC2, . . . ).

5. Method according to one of the claims 1 to 4, comprising the steps of

a) an originating mobile station (MS) selecting an address of said message server (WAMS) as destination address which corresponds to a recipient application;

b) transmitting the message to a first service centre (SC2)in the mobile telecommunications network;

c) the first service centre (SC2) using a related gateway function (GMSC) for retrieving routing information from the database (HLRx) of the message server (WAMS) based on the provided destination address and

d) forwarding the message through the switching function (MSCx) in the message server (WAMS) to a second service centre (SC1) hosting the recipient application or the related service.

6. Method according to one of the claims 1 to 5, wherein numbers of virtual mobile stations, having preferably the format of a standardised E.164 address number, are assigned as destination addresses to the recipient applications (ESME, PC1, PC2, . . . ) in order to access the message server (WAMS) or its elements (HLRx, MSCx) or wherein the message server (WAMS), acting as service center, is accessed by means of a given E.164 number.

7. Method according to one of the claims 1 to 6, wherein the information, such as the virtual mobile station number, used to access the message server (WAMS) or its functions (HLRx, MSCx) is originally provided in the user data or the signalling data, particularly as the originating address, of a former message sent by the recipient application (ESME, PC1, PC2, . . . ) or a related service.

8. Method according to one of the claims 1 to 7, wherein the message server (WAMS) handles the recipient applications (ESME, PC1, PC2, . . . ) or the related services as virtual mobile stations with the database (HLRx) of the message server (WAMS) containing at least

a) a Mobile Station International ISDN Number MSISDN serving as the virtual mobile station number related to the recipient application or the related service,

b) the International Mobile Station Identity IMSI corresponding to said Mobile Station International ISDN Number (MSISDN),

c) the address, such as an E.164 address, of the service centre (SC1) linked to the recipient application or the related service,

d) the address and preferably address type of the recipient application or the related service.

9. Method according to claim 8, in which

a) the first service centre (SC2) or the related gateway function (GMSC) uses the Mobile Station International ISDN Number MSISDN for retrieving the International Mobile Station Identity IMSI and the address of the switching function (MSCx) from the database (HLRx) of the message server (WAMS) preferably by means of a SEND-ROUTING-INFO-FOR-SM query,

b) the first service centre (SC2) or the related gateway function (GMSC) forwards the message to the switching function (MSCx) of the message server (WAMS) and

c) the switching function (MSCx) retrieves the address of the recipient application or the related service as well as the address of the service centre (SC1) linked to the recipient application or the related service and submits the message preferably with an SMS-SUBMIT event instead of an SMS-DELIVER event to the addressed service centre (SC1) and

d) the addressed service centre (SC1) based on routing information stored in a database forwards the message to the recipient application or a related service.

10. Method according to one of the claims 1 to 9, in which the database (HLRx) of the message server (WAMS), comprising routing information, is maintained by an operator (OP;

SP) of a service provider such as the service provider SP related to said application and service; and

/or in which transactions performed by said message server (WAMS) are counted and reported.

11. Message server (WAMS) for conveying messages, particularly short messages, originating in a mobile telecommunications network such as the GSM system and terminating at a recipient application (ESME, PC1, PC2, . . . ) or a related service in a network such as an IP-network which is not using the standards of said mobile telecommunications network, said message server (WAMS)

a) using signalling functions, such as the functions of the Signalling System Number 7, according to the standards of said mobile telecommunications network;

b) comprising a database (HLRx) containing routing information to said recipient application (ESME, PC1, PC2, . . . ) or the related service;

c) comprising a switching function (MSCx) for forwarding the message to the recipient application (ESME, PC1, PC2, . . . ) or the related service, or to a location accessible by the recipient application (ESME, PC1, PC2, . . . ) or the related service and

d) comprising a control unit (WAMSC) through which an operator can access and update at least said database (HLRx).

12. Message server (WAMS) according to claim 11, comprising a gateway function (GW-FUNCTION) with

a) a first protocol stack designed to terminate messages received from the mobile communications network and/or

b) a second protocol stack designed to terminate messages received from external short message entities (ESME, PC1, PC2, . . . );

operating in a different network, such as an IP-network;

in order to extract the contents of the received messages, which then, across the complementing second or first protocol stack are transferred to their destinations;

or which are stored and then retrieved by addressed short message entities (ESME, PC1, PC2, . . . ).

13. Message server (WAMS) according to claim 12, wherein the gateway function (GW-FUNCTION) comprises a protocol stack with the layers of the signalling system and the short messaging system of the mobile telecommunications network (PLMN) on one side and with the protocol stack used by the external short message entities (ESME, PC1, PC2, . . . ) comprising

a) layers of a network protocol such as TCP/IP;

b) a layer of a data transport protocol such as HTTP, SMTP, FTP, NNTP, SNMP; and

c) a layer of a data protocol such as XML, ASN.1, derivatives thereof.

14. Message server (WAMS) according to claim 11, 12 or 13, designed as short message service center, capable of transferring messages between

a) short message entities, such as mobile stations (SME, MS1, MS2, . . . ) internal to the mobile telecommunications network (PLMN);

b) short message entities, such as recipient applications (ESME, PC1, PC2, . . . ) in an IP-network, external to the mobile telecommunications network (PLMN); and

c) in both directions between internal short message entities (SME, MS1, MS2, . . . ) and external short message entities (ESME, PC1, PC2, . . . )

and further designed to transfer messages from internal short message entities (SME, MS1, MS2, . . . ) to external short message entities (ESME, PC1, PC2, . . . ) by means of destination addresses of virtual mobile stations incorporated in the message server (WAMS) that correspond to recipient applications (ESME, PC1, PC2, . . . ).

15. Message server (WAMS) according to one of the claims 11 to 14, comprising at least one storage facility (HLRx, TB, HD, DBMS) such as a random access memory, a hard-disk a Storage Area Network (SAN), or a database managed by a high level application;

designed to store routing information and/or terminated messages or extracted content, such as the user data of a protocol data unit SMS-DELIVER.

16. Message server (WAMS) according to one of the claims 11 to 15, wherein storage facility (HLRx, TB, HD, DBMS) is accessible by recipient applications (ESME, PC1, PC2, . . . ) or a proxy server in order to retrieve received messages or contents.

17. Message server (WAMS) according to one of the claims 11 to 16, hosting recipient applications.

18. Message server (WAMS) according to one of the claims 11 to 17, in which the database (HLRx) contains at least

a) the Mobile Station International ISDN Number MSISDN related to the recipient application or the related service,

b) the International Mobile Station Identity IMSI corresponding to said Mobile Station International ISDN Number MSISDN,

c) the address, such as an E.164 address, of the service centre (SC1) linked to the recipient application or the related service,

d) the address and preferably address type of the recipient application or the related service.

19. Message server (WAMS) according to one of the claims 11 to 18, in which the database (HLRx) operates according to the specification of a home location register (HLR) of a GSM system and in which the switching function (MSCx) operates according to the specification of a mobile services switching centre (MSC) of a GSM system.

20. Telecommunications network for conveying messages, particularly short messages, originating in a mobile telecommunications network such as the GSM system and terminating at a recipient application or a related service in a network not using the standards of said mobile telecommunications network, comprising a message server (WAMS) according to one of the claims 11 to 19, through which messages arriving at a first service centre (SC2) can be routed to the recipient application or the related service.

21. Telecommunications network according to claim 20, wherein the message server (WAMS) is designed as short message service center, capable of transferring messages between

a) short message entities, such as mobile stations (SME, MS1, MS2, . . . ) internal to the mobile telecommunications network (PLMN);

b) short message entities (ESME, PC1, PC2, . . . ), such as recipient applications in an IP-network, external to the mobile telecommunications network (PLMN); and

c) in both directions between internal short message entities (SME, MS1, MS2, . . . ) and external short message entities (ESME, PC1, PC2, . . . );

and wherein the message server (WAMS) is further designed to transfer messages from internal short message entities (SME, MS1, MS2, . . . ) to external short message entities (ESME, PC1, PC2, . . . ) by means of destination addresses of virtual mobile stations incorporated in the message server (WAMS) that correspond to recipient applications (ESME, PC1, PC2, . . . ).