Control of PLMN messaging services in IP domains

FIELD OF THE INVENTION

0001The invention relates to messaging.

PRIOR ART DISCUSSION

0002Messaging services in PLMN domains have reached significant levels of usage amongst mobile subscribers. The Short Message Service (SMS) originated in GSM networks and has spread to many different network technologies, now being found in ANSI-41 TDMA and CDMA networks and has also been deployed in Japanese PDC networks. This growth has been driven by subscriber demand for messaging services, providing a means of communication between individuals and groups that was not available previously. With the advent of 2.5G and 3G network technologies, there is now significant interest in extending the range of messaging services beyond the boundaries of the mobile networks by providing inter-operability with packet data network (PDN) domains. The internet domain has seen massive growth in recent years with the numbers of users contactable via internet addresses increasing significantly each year. Furthermore, mobility of internet users is increasingly supported by Mobile IP protocols, allowing an individual user to be contactable at the same internet address irrespective of the geographic location where they connect to the internet.

0003This invention is directed towards providing a control and transport entity that enables implementation of an integrated messaging service, providing the means for origination, transport and delivery of messages between PLMN and PDN domains (fixed and mobile).

SUMMARY OF THE INVENTION

0004According to the invention, there is provided a gateway comprising: <ul id="ul0001" list-style="none"><li id="ul0001-0001" num="0000"><ul id="ul0002" list-style="none"><li id="ul0002-0001" num="0005"> an interface to a packet network, </li><li id="ul0002-0002" num="0006"> an interface to a mobile network, and </li><li id="ul0002-0003" num="0007"> a processor for performing protocol translation for messages communicating between packet and mobile networks connected to the interfaces. </li></ul></li></ul>

0008In one embodiment, the processor comprises a presence management function for detecting and maintaining presence information in the packet network, and for mapping a presence state to a form used in the mobile network.

0009In another embodiment, the presence management function functions as a Session Initiation Protocol (SIP) registrar.

0010In a further embodiment, the presence management function comprises an interface for accessing an external SIP registrar in an IP network.

0011In one embodiment, said interface maintains a cache of SIP entries.

0012In another embodiment, the presence management function stores user device capabilities, and the protocol translation function selects a message delivery protocol based on device capabilities.

0013In a further embodiment, the processor further comprises a message routing function for routing a message having a mobile network address format to a user in a packet network.

0014In one embodiment, the routing function converts a mobile network format address to a packet network format address.

0015In another embodiment, the routing function routes a single message from one network to multiple addresses in another network.

0016In a further embodiment, the routing function interfaces with packet network broadcast services.

0017In one embodiment, the gateway comprises an interface for emulating a mobile network entity such as an SME or an SMSC.

0018In another embodiment, the emulation capability of the interface allows operation of the gateway without re-configuration of a conventional mobile network.

0019In a further embodiment, the interface extracts a URL from message text, provides a deferred acknowledgement, and notifies an SMSC of a mobile network that a user in the IP domain has become active.

0020In one embodiment, the processor comprises a message delivery management function for extending a store and forward delivery capability to the IP domain.

0021In another embodiment, the presence management function notifies an entity in a network if a subscriber enters the domain of another network.

0022In a further embodiment, the presence management function notifies the entity if the subscriber is the intended recipient of a message awaiting delivery.

0023In one embodiment, the notification signal specifies in a dynamic manner search criteria for the network entity ranging from a direct match criterion to a partial match criterion.

0024In another embodiment, the gateway comprises means for modifying a message in a network entity such as an SMSC to charge its destination address.

0025In another aspect, the invention provides a method for communicating between a mobile network and a packet network comprising the steps of: <ul id="ul0003" list-style="none"><li id="ul0003-0001" num="0000"><ul id="ul0004" list-style="none"><li id="ul0004-0001" num="0026"> a mobile device in the mobile network transmitting a message with a mobile network address of a gateway as defined above and an embedded destination packet network user address; </li><li id="ul0004-0002" num="0027"> an entity of the mobile network routing the message to an interface of the gateway; and </li><li id="ul0004-0003" num="0028"> the gateway receiving the message at the interface, stripping out the destination packet network address, and routing the message to the packet network user with the packet network address. </li></ul></li></ul>

0029In one embodiment, the packet network address is in a Session Initiation Protocol format.

0030In another embodiment, the gateway maintains a table associating the packet network addresses with a mobile-network-standard address for the packet network user, and for a subsequent message the mobile network user includes only a mobile network standard address and the gateway retrieves the packet network address from the table.

0031In a further embodiment, the gateway binds to at least one mobile network entity for communication of messages.

DETAILED DESCRIPTION OF THE INVENTION

BRIEF DESCRIPTION OF THE DRAWINGS

0032The invention will be more clearly understood from the following description of some embodiments thereof, given by way of example only with reference to the accompanying drawings in which:

0033<figref idref="DRAWINGS">FIG. 1</figref> is a schematic diagram illustrating interaction between a PLMN messaging domain, a control entity between the PLMN and IP domains and a messaging-enabled IP domain;

0034<figref idref="DRAWINGS">FIG. 2</figref> is a diagram illustrating a signalling flow for SMS originating in the PLMN and terminating in the PDN; and

0035<figref idref="DRAWINGS">FIG. 3</figref> is a diagram illustrating a signalling flow for an SMS originating in the PDN domain and terminating in the PLMN domain.

DESCRIPTION OF THE EMBODIMENTS

0036The invention provides an IP to PLMN Gateway (IPG) node <b>1</b> for controlling the delivery of common PLMN-based messaging services (for example, SMS, Cell Broadcast) to users in IP domains (for example, users with fixed internet addresses or users currently active on a Wireless LAN). The IP domain users may be fixed or mobile. The mobile subscribers will generally be capable of roaming between the PLMN and the IP Domains. Two forms of roaming exist: (1) Home PLMN (HPLMN) subscriber roaming, where the PLMN mobile subscriber roams into the IP domain owned by the PLMN operator, and (2) Visited PLMN (VPLMN) subscriber roaming, where a PLMN mobile subscriber ‘roaming’ in another PLMN (using existing inter-PLMN roaming agreements) roams into the IP Domain of the Visited PLMN.

0037Extending the reach of messaging services from PLMN's to IP domains therefore creates a wider community of messaging users and removes the mobile handset as the sole originating or terminating device for mobile messaging. For example, a mobile subscriber may wish to send a message to another user who may not be contactable via a mobile handset but may be present in a packet data domain, such as Wireless LAN or fixed internet. Similarly, an internet user may wish to originate a message for delivery to a mobile subscriber on their handset.

0038The PDN messaging communities may assume a number of different forms. A community in one PDN Domain could be the set of users in an airport connected to a Wireless LAN hotspot (e.g. 802.11, HiperLAN), while another community could be ‘fixed’ subscribers of an interactive TV domain. All such PDN domains could be part of a single greater PDN domain from the perspective of the PLMN or equally they could be considered as separate PDN domains.

0039The invention is described in the context of a GSM PLMN and an IP-based PDN. However, the invention is equally applicable to alternative mobile network technologies such as CDMA, IDMA, PDC and UMTS, as well as in PDN technologies beyond IP-based networks.

0040The IP-to-PLMN Gateway (IPG) node enables the extension of the PLMN messaging domain into IP domains such as fixed internet and Wireless LAN networks. The IPG node <b>1</b> comprises an IP transport interface <b>2</b> connected to a Session Initiation Protocol (SIP) user agent (UA) <b>3</b>, in turn connected to a message delivery function <b>4</b>. The function <b>4</b> is connected to both a protocol translation function <b>5</b> and to a presence management function <b>6</b>. An SME interface <b>7</b> is connected on one side to the interface <b>2</b> and on the other side to the presence management function <b>6</b> and to a message routing address management function <b>8</b>. The nodes also comprises a billing function <b>10</b>.

0041The IPG implements a set of control and transport functions that allow messaging services and formats common in the PLMN domain to be suitably adapted for origination or delivery in the IP domain. An advantageous element of the invention is that all of the enhanced service functions in the PLMN (for example, store and forward, message waiting and alert functions) are carried over into the messaging service available in the IP domain. The IPG ensures that no modification of the existing message service equipment in the PLMN is necessary for a fully functional messaging service in the IP domain. However, the invention also provides for extensions to the standard interfaces between the IPG node and the messaging platforms to allow for optimised delivery of messaging services in the IP domain. A further aspect of the invention is that it can be applied to all PLMN technologies supporting messaging services (for example, Short Message Service, Cell Broadcast, Multimedia Messaging, Instant Messaging) and any IP domain (for example fixed or mobile internet). An implementation of the invention in the context of a GSM PLMN and fixed network IP domain is described below, and illustrated for a Short Messaging Service.

0042In a GSM network, the Short Messaging Service is provided by a Short Message Service Centre (SMSC) network element. The SMSC communicates with other elements in the PLMN (such as HLR's, VLR's, MSC's) by means of an Interworking Gateway MSC (I-GMSC). In addition, the SMSC provides an application interface that allows service developers to bind an application to the SMSC. An example of such an interface protocol is the Short Message Peer-to-Peer (SMPP) protocol specified by the SMS Forum. Within the PLMN domain, the SMSC may receive a short message (SM) from an external application via SMPP addressed to a particular mobile subscriber MSISDN. The SMSC stores the SM in an internal store and then requests routing information from the HLR for the mobile subscriber. If routing information is received, it indicates the current serving MSC/VLR for the mobile subscriber. The SMSC submits the SM to the serving MSC/VLR for delivery to the mobile subscriber. If delivery is successful, the SMSC marks the SM as delivered in the message store. If delivery is not successful (perhaps because the mobile subscriber is not contactable in the serving network), the SMSC will attempt delivery at a later time (it may set a message waiting flag in the HLR so the SMSC is alerted if the subscriber becomes active in a network, or it may schedule the message for a retried delivery attempt according to an internal retry algorithm).

0043The IPG node <b>1</b> incorporates all required functional elements that allow the full range of messaging capabilities from the PLMN to be offered in the IP domain. In the embodiment of the invention illustrated in <figref idref="DRAWINGS">FIG. 1</figref>, the main functional entities in the IPG node <b>1</b> are: <ul id="ul0005" list-style="none"><li id="ul0005-0001" num="0000"><ul id="ul0006" list-style="none"><li id="ul0006-0001" num="0044"> (a) Short Message Entity (SME) interface <b>7</b> to the SMSC in the PLMN, </li><li id="ul0006-0002" num="0045"> (b) subscriber presence management <b>6</b>, </li><li id="ul0006-0003" num="0046"> (c) protocol translation <b>5</b>, </li><li id="ul0006-0004" num="0047"> (d) message delivery management <b>4</b>, </li><li id="ul0006-0005" num="0048"> (e) message routing and address management <b>8</b>, </li><li id="ul0006-0006" num="0049"> (f) billing and charging management <b>10</b>, </li><li id="ul0006-0007" num="0050"> and these functional entities are tailored according to the requirements of each particular embodiment of the invention. For example, in the current embodiment of the invention the SME interface <b>7</b> to the SMSC is based on the SMPP protocol. Subscriber presence management, protocol translation and message delivery management are based on the Session Initiation Protocol (SIP). </li></ul></li></ul>

0051Referring to <figref idref="DRAWINGS">FIG. 1</figref>, an end-to-end description of a short messaging service between the PLMN and IP domains is provided below.

0000PLMN-Origination/IP Termination:

0052A mobile subscriber MS uses a GSM PLMN to originate an SMS towards another user known to the mobile subscriber. The mobile subscriber is aware that the recipient does not use a mobile handset but can receive SMS on their fixed internet service via a SIP URL when they are connected to the network. The mobile subscriber specifies a destination MSISDN corresponding to the IPG's SME interface <b>7</b> and specifies the user's SIP URL as a text field in the message. When the mobile subscriber sends the message it is received by the SMSC in the PLMN, which routes the message to the SME interface <b>7</b> of the IPG node <b>1</b>. The. SME interface <b>7</b> extracts the destination SIP URL from the message text and presents this information to the subscriber presence management function <b>6</b>. The SMPP format of the message is submitted to the message routing entity <b>8</b> and protocol translation entity <b>5</b>, where the message is converted to a format suitable for delivery over SIP. The presence management function <b>6</b> uses SIP Proxy and SIP Registrar entities to determine the current status of the destination user. If it is determined that the user is connected to the IP domain, the properly formatted SM is submitted to the message delivery management function <b>4</b> for delivery. Message delivery is attempted using the SIP User Agent <b>3</b>, which communicates with a peer SIP User Agent <b>20</b> on the destination user's device. If the message is successfully delivered to the destination user this status is returned via the SME interface <b>7</b> to the SMSC. If the message is not delivered, the message delivery management function <b>4</b> may set a message waiting flag for the destination user. If the user connects to the IP domain, this presence is detected via the presence management function <b>6</b> and a notify signal is sent to the SMSC in the PLMN, prompting it to attempt delivery of the SM via the SME interface <b>7</b> once more. Thus the full functionality of the SMS service in the PLMN is carried over into the IP domain. The billing and charging management function <b>10</b> is invoked to provide the billing function for the IPG node <b>1</b>. To support a pre-paid billing model, a pre-delivery credit check may be invoked to check the user's credit balance before the message delivery attempt is initiated If the credit check returns a positive indication, the message-delivery is attempted and the appropriate charge deducted from the user's account for a successful delivery. For a post-paid billing model, a CDR (call detail record) event is produced for both successful and unsuccessful delivery attempts. The CDR event contains all relevant information such as originating address, destination address, and delivery status that may be used to produce subscriber billing information.

0000IP-Origination/PLMN Termination:

0053A user in the IP domain <b>9</b> initiates SM to a mobile subscriber in the PLMN domain, addressed via a SIP URL containing the mobile subscriber's MSISDN. The message is submitted via the SIP User Agent <b>20</b> on the user's device, which routes the message based on the standard SIP URL mechanism to the SIP user agent <b>3</b> in the IPG node <b>1</b>. At the IPG node <b>1</b> the SIP user agent <b>3</b> processes the URL to derive the mobile subscriber's MSISDN. The SM is passed to the protocol translator <b>5</b> where it is converted to an SMPP format, with the mobile subscriber's MSISDN as the destination address. The re-formatted message is forwarded to the SME interface <b>7</b>, which submits it over SMPP to the SMSC in the PLMN. At this point, an acknowledgement for the message submission may be returned to the user in the IP domain via the SIP user agent <b>3</b>. Further processing of the SM delivery is handled entirely within the PLMN domain using the standard SMS functionality. For message delivery in this direction, the subscriber presence and message delivery management functional entities <b>6</b> and <b>4</b> are not used.

0054The billing and charging management function <b>10</b> is able to support a range of billing models for the service, including charge or no-charge for delivery of terminating messages, charge or no-charge for origination of a message, and pre- and post-paid models. For a pre-paid billing model, the message delivery or message origination function is suspended while the billing and charging function performs a credit query against a subscriber. If the credit check is positive, the delivery or origination function is resumed. If the credit check is negative, the delivery or origination function is cancelled and a credit recharge option may be presented to the subscriber instead. In all cases, the billing and charging function <b>10</b> records CDR events for message submission and delivery attempts. These CDR events may be processed to generate subscriber billing information for post-paid subscribers, or may be used simply for audit and reconciliation purposes in a pre-paid billing model.

0000Other Addressing Formats for the IP Domain:

0055Other addressing formats may be used to specify the address of a user in the IP domain and are implemented by the PG node <b>1</b>. Some examples of the alternative addressing formats supported by the IPG are given below. <ul id="ul0007" list-style="none"><li id="ul0007-0001" num="0000"><ul id="ul0008" list-style="none"><li id="ul0008-0001" num="0056"> MSISDN-like address—a non-PLMN user receives an MSISDN-like address: </li><li id="ul0008-0002" num="0057"> MSISDN-like element in SIP URL—a non-PLMN user receives an MSISDN-like address and this is incorporated into a SIP URL: </li><li id="ul0008-0003" num="0058"> ‘Real’ MSISDN in SIP URL—a PLMN user may opt to receive messages in an IP domain and their PLMN MSISDN may be incorporated into a SIP URL for this purpose: </li><li id="ul0008-0004" num="0059"> Group addresses comprising MSISDN-like or group ‘name’ elements—this addressing format is used for point-to-multipoint services. </li><li id="ul0008-0005" num="0060"> Geographic or area addresses comprising MSISDN-like or location ‘name’ elements—this addressing format is used for broadcast services. </li><li id="ul0008-0006" num="0061"> SIP URL representing a PLMN user—this form of address is used as the destination address of a PLMN user when a SM is being originated by an IP user. The PLMN user's real MSISDN is usually embedded in the SIP URL. </li></ul></li></ul>

0062These addressing formats may be processed by the IPG node <b>1</b> to support direct addressing of users in the IP domain from the PLMN domain, such as enabling a PLMN user to invoke the ‘Reply’ function when a message has been received from a user in the IP domain.

0063A more detailed description of the functions implemented in each of the functional entities is provided below.

0000SME Interface <b>7</b>

0064This functional entity is responsible for ensuring communication between the IPG node <b>1</b> and the SMSC in the PLMN. In the current embodiment of the invention, communication between the SMSC and the IPG is ensured using the SMPP protocol. In addition to protocol handling, the SME interface <b>7</b> also incorporates specific functions that allow the IPG node <b>1</b> to appear to the SMSC as though it were a standard PLMN SME. These include: <ul id="ul0009" list-style="none"><li id="ul0009-0001" num="0000"><ul id="ul0010" list-style="none"><li id="ul0010-0001" num="0065"> Extraction of the SIP URL from the message text </li><li id="ul0010-0002" num="0066"> Deferred acknowledgement to a message submitted for delivery from the SMSC </li><li id="ul0010-0003" num="0067"> Ability to generate a notify signal to alert the SMSC that a user in the IP domain has become active (i.e. presence has been detected). <br /> Subscriber Presence Management Function <b>6</b></li></ul></li></ul>

0068This functional entity is responsible for detecting and maintaining the presence status of users in the IP domain. In this embodiment, these capabilities are based on the mechanisms defined within the SIP protocol, i.e. it functions as a SIP Registrar and is capable of processing the SIP REGISTER messages sent by the SIP user agent <b>20</b> in the IP domain. In this case, the IPG node <b>1</b> stores the SIP-URI and IP address of the ‘registered’ user.

0069It is possible that a SIP Registrar is already present in the IP network domain. In this case the presence management entity <b>6</b> queries the SIP Registrar to determine presence information for the IP domain user whenever required for a message delivery attempt. In order to reduce communications overhead with the external SIP Registrar, the function <b>6</b> incorporates a SIP registry cache which stores presence information for a configurable period, thus avoiding repetitive queries to the SIP Registrar. In the event of a message delivery failure due to absence of the IP domain user, the SIP Registry Cache entry for the user is automatically removed.

0000Protocol Translation

0070This entity provides the translation between the signalling protocols used in the PLMN and the protocol used in the IP domain. In the current embodiment of the invention, the SIP protocol is used for delivery of messaging services in the IP domain. Communication with the PLMN domain is performed using SMPP and the protocol translation entity performs the conversion to/from the SMPP and SIP protocols.

0071In general the IP domain protocol used to terminate a message will be determined by the capabilities of the user device addressed in the message ‘destination address’ parameter. The IPG node <b>1</b> will select the message delivery protocol based on the user device capabilities. The user agent device capabilities will be transmitted to the IPG during user registration in the IP Domain. These user agent profiles will be stored by the IPG presence function.

0000Message Delivery Management <b>4</b>

0072This functional entity is responsible for ensuring that the store and forward messaging delivery model from the PLMN domain is extended to the IP domain. When a message is received from the PLMN domain for delivery to the IP domain, the IPG attempts delivery using the selected IP domain protocol. Message delivery using the SIP protocol is described below for the current embodiment of the invention.

0073When a message is received from the PLMN via the SME interface <b>7</b> the message delivery management entity <b>4</b> receives the message after it has been converted to a SIP format by the protocol translation entity <b>5</b> and the destination address (SIP URL) in the IP domain has been extracted. The delivery entity may first check the presence of the user in the IP domain by submitting a query to the SIP Registrar function. If the user is present, the current contact address of the user may be returned by the SIP Registrar. Alternatively, the delivery entity may attempt to resolve the SIP URL by another means such as via DNS or through an internal query using a proprietary protocol. The delivery entity <b>4</b> generates a SIP MESSAGE request properly formatted for delivery of the message to the user. Depending on the delivery protocol in use, the SIP MESSAGE may carry the message within its payload, or alternatively a SIP INVITE request may be used to establish a session with the user in which the message will be transferred using an appropriate session protocol. Assuming direct delivery using the SIP MESSAGE request, if a contact address has already been resolved, the SIP MESSAGE can be sent directly via the SIP User Agent within the IPG. Alternatively, the SIP MESSAGE can be submitted via a SIP Proxy, which takes responsibility for resolving the current contact address for the user. If the message is successfully delivered to the user, a positive acknowledgement is received by the delivery entity in the form of a 200 OK response. This status information is then returned to the SMSC in the PLMN via the SME interface <b>7</b>, where the message can be marked as delivered.

0074If the transfer of the message fails (due to resource restrictions, network problems or because the user agent is not registered), then the delivery entity <b>4</b> sets a Message Waiting Data (MWD) flag for the UAC within the PG, storing the address of the originating SMSC. Multiple SMSC addresses may be stored against a single UAC, each representing a source SMSC where messages awaiting delivery to the UAC are stored. At a subsequent time, when the user registers in the IP domain, the IPG node <b>1</b> detects that the MWD flag has been set for the user. The delivery entity generates an SMPP ‘Notify’ message to be sent to all SMSC addresses stored within the user's MWD flag. The notify message is used by the SMSC's to trigger a new delivery attempt for any messages awaiting delivery to the user in the IP domain. The retried messages are received by the IPG node <b>1</b>, which then proceeds with the delivery to the now-registered UAC as previously described.

0075This invention specifies an enhanced implementation of the ‘notify’ message which allows the SMSC and the IPG node <b>1</b> to cooperate to optimise delivery attempts to users in the IP domain even if a direct address has not been allocated for the user. Also, the presence management function <b>6</b> can determine if a subscriber with messages‘waiting’ becomes present in the IP domain, and notify the SMSC. An enhanced notify message contains the SIP URL of the destination user. When received by the SMSC, the enhanced notify mechanism implemented at the SMSC scans the waiting messages for the IPG node <b>1</b> and extracts only those messages which match the notified SIP URL. The criteria for a ‘match’ to the notified SIP URL may be modified in a dynamic way, for example an exact match may be required, or a partial match on the domain, or some part of the domain may be sufficient. In an alternative embodiment of the invention, the notify message itself may contain an element specifying the required matching criteria on a per-notification basis.

0000Message Routing and Address Management <b>8</b>

0076This functional entity ensures that messages are routed appropriately between the PLMN and IP domains. It also provides a capability for assigning a PLMN-compatible address to an IP domain address (e.g. SIP URL), thereby allowing a user in the PLMN domain to address the IP domain user directly using an MSISDN-like address. With this capability, the invention allows direct messaging between users in the PLMN and IP domains, for example a user in the PLMN domain can use the ‘Reply’ function to respond to a message received from a user in the IP domain. Operation of the principal addressing formats supported by the IPG node <b>1</b> is described below.

00001. User in IP Domain is Addressed using a SIP URL:

0077When a PLMN user sends a message to a user in the IP domain they are required to enter the SIP URL in a special text field in the body of the message while entering a well-known MSISDN as the destination address, which ensures the message is routed to the IPG node <b>1</b>. When the message is received by the IPG node <b>1</b>, the SIP URL is extracted from the message and forwarded to the address management entity <b>8</b>. The SIP URL is checked to see Whether it has been assigned an MSISDN-like address from the range of MSISDN numbers specified by the IPG node <b>1</b> when it bound to the SMSC. If no MSISDN-like number has been allocated, the address management entity <b>8</b> selects a free MSISDN from the IPG range and creates an association with the SIP URL that is stored in the IPG. Once assigned, this MSISDN-like number may be used as a direct address for the IP user with respect to the PLMN domain. If the message delivery attempt to the SIP URL is successful, a delivery receipt can be generated using the MSISDN-like number as the originating address. When received by the PLMN subscriber, this address can be as a direct destination address for the IP user, removing the need to specify a SIP URL in the message text in future messages. When the IPG receives a message for an P user using the MSISDN-like direct address, the address management entity <b>8</b> retrieves the SIP URL automatically from the IPG tables to complete the delivery in the IP domain.

0078In the event of a message delivery failure, the IPG node <b>1</b> replaces the original (IPG) destination address with the newly assigned MSISDN-like destination address in the copy of the message stored in the SMSC. Future retries of the message then use the MSISDN-like address as the destination address. If the MWD flag is set for the IP user, the ‘notify’ message sent to the SMSC contains the MSISDN-like address, thus automatically triggering retries only for the specified subscriber.

00002. User in IP Domain is addressed using an MSISDN-like Address:

0079In this case, a provisioning interface in the IPG node <b>1</b> is used to create an association in the internal table between the MSISDN-like address and the SIP URL used for delivery in the IP domain. With this addressing mode, the user in the PLMN domain must be informed of the MSISDN-like address of the user in the IP domain, but is not required to know the associated SIP URL.

00003. User in IP Domain has MSISDN-like Element in the SIP URL Address:

0080In this case, the IPG node <b>1</b> is configured to extract the MSISDN-like element from the SIP URL and, conversely, to re-create the original SIP URL from the MSISDN-like address.

00004. User in IP Domain has ‘real’ MSISDN Element in the SIP URL Address:

0081To enable this type of addressing, the IPG automatically creates a prefix for the real MSISDN to ensure that it falls within the range of MSISDN-like addresses specified when the PG binds to the SMSC. A user in the PLMN domain may specify the SIP URL in a text field of the message or may be informed of the special prefix to use when addressing the PLMN subscriber in the IP domain. In either case, the address management entity automatically carries out the address conversion function as required between the PLMN and IP domains.

00005. User in PLMN Domain has ‘real’ MSISDN Element in the SIP URL Address:

0082This type of addressing is used to allow an IP user to originate a SM for delivery to a PLMN subscriber. The IPG automatically processes the SIP URL to extract the real MSISDN information and this is then used as the destination address to forward the message into the PLMN domain.

0000Billing and Charging Management <b>10</b>

0083This functional entity is responsible for management of billing and charging elements in the node <b>1</b>. The important functions performed by this entity include: <ul id="ul0011" list-style="none"><li id="ul0011-0001" num="0000"><ul id="ul0012" list-style="none"><li id="ul0012-0001" num="0084"> Generation of CDR events related to the origination, and delivery of messaging for subscribers in the IP domain. </li><li id="ul0012-0002" num="0085"> Management of a charging interface to an external pre-paid system that handles pre-paid billing for the IPG. </li><li id="ul0012-0003" num="0086"> Where a pre-paid credit query is supported by the external pre-paid system, this entity is capable of suspending a message origination or delivery attempt until a response to the credit query has been received. Based on the response received, it is capable of either resuming or cancelling the delivery or origination attempt. </li></ul></li></ul>

0087These functional entities may be replaced or modified to adapt the invention for control or delivery of other messaging services such as point-to-multi-point, broadcast, or multi-media messaging. The SME interface <b>7</b> would be replaced by a message broadcast entity for a broadcast service, or by an interface to an MMSC for a multi-media service. Similarly, the protocol translation, subscriber presence management, and message delivery management entities would be replaced or modified according to the protocols selected for use for a particular service. The message routing and address management entity <b>8</b> would be extended to incorporate address management for group and geographic address type. For example, a broadcast message may be addressed to a geographic location identified by a location ‘name’. The address management entity <b>8</b> would convert this name into a list of Broadcast SIP URL's, which would be further resolved via a SIP proxy into well-defined broadcast IP subnet addresses, which would route the broadcast message to specific WLAN base stations covering the specified geographic location.

0000Illustration of SM Service Terminating in an IP Domain from a PLMN User:

0088The message flow for this service is illustrated in <figref idref="DRAWINGS">FIG. 2</figref> where a direct address for the user in the IP domain has been used by the PLMN user. The IPG node <b>1</b> functioning as an SME ‘Binds’ to the PLMN SMSC on behalf of a block of routing numbers which are allocated as direct addresses to users in the IP domain. The direct addresses may therefore be specified in an MSISDN-like format.

0089When the Mobile Station(MS) submits the SMS to the SMSC, it is routed to the IPG node <b>1</b> based as the destination address in the message matches the range specified for the IPG node <b>1</b>. The IPG node <b>1</b> receives the DELIVER_SM from the SMSC and the destination address contained in the DELIVER_SM is translated to a SIP URL for the IP user using address management entity. The SIP URL is resolved to an IP Address either using a DNS query or the message may be routed via a SIP Proxy/Registrar. The IPG creates a SIP MESSAGE request from the SMPP DELIVER_SM message and delivers the SMS to the destination user encapsulated in the SIP MESSAGE.

0090The successful receipt of the SIP MESSAGE request by the UAC is indicated to the IPG on receipt of the <b>200</b> OK response. The IPG translates this <b>200</b> OK to an SMPP DELIVER_SM_ack response that is sent to the SMSC.

0000Illustration of SM Service Terminating in a PLMN Domain from an IP User:

0091The message flow for this service is illustrated in <figref idref="DRAWINGS">FIG. 3</figref>. When a SIP UAC requests to send an SMS to a PLMN subscribe, the PLMN subscribers’ SIP URL domain name is resolved to the IP address of the IPG either by a DNS lookup or the message is routed via a SIP Proxy. The SIP MESSAGE request is forwarded to the IPG functioning as a SIP UAS.

0092The IPG node <b>1</b> receives the SIP MESSAGE and passes it to the IPG SMPP translator. The SIP MESSAGE request is translated to an SMPP Submit_SM message, and the PLMN user's MSISDN is extracted from the SIP URL by the address management entity. The IPG acting as an SME forwards the Submit_SM to the SMSC. The SMS-GMSC queries the PLMN HLR for the subscriber's serving MSC, creates the FSM and then forwards the SMS to the serving MSC for delivery to the MS.

0093Some additional detail relevant to the implementation of the IPG node <b>1</b> is described below.

0094Communication between the IPG node <b>1</b> and the SMSC is based on the standard SMPP protocol specified by the SMS Forum. In order to provide enhanced capabilities for the control of messaging in an IP domain, communication may use some extensions to the standard SMPP operations, with associated modifications to the SMPP protocol modules on the IPG node <b>1</b> and in the SMSC. In particular, the extended protocol definition allows the IPG node <b>1</b> modify a message in the SMSC message store to change the destination address on the message to a direct address assigned to a user in the IP domain.

0095The IPG node <b>1</b> is deployed in the network as a highly available and scaleable node. It may be configured as a multi-node cluster, in which individual nodes may service different MSISDN-like ranges assigned to users in the IP domain. The nodes may also operate as active/standby pairs or in a N+M redundant configuration to provide high availability configurations for network operators. If an active node should fail, a standby node or an available redundant node can be switched into the cluster in place of the failed node. A robust data-sharing mechanism is implemented to allow the newly activated node to access the associations between SIP URL's and MSISDN-like addresses that were previously created by the failed node.

0096In a minimum configuration, the IPG may be deployed as a single node with the ability to dynamically switch in additional nodes to meet increasing capacity demands. For a minimum high-availability configuration, the IPG node <b>1</b> is deployed as a dual-node cluster operating in active/standby node.

0097The IPG node <b>1</b> also provides a billing interface that is suitable for both post-paid and pre-paid operation. For post-paid operation, the IPG node <b>1</b> produces CDR event records for each message submission, delivery attempt and delivery reports. For pre-paid operation, the IPG implements a charging interface that can be adapted to communicate with a pre-paid billing system. The charging interface and the message delivery entity in the IPG are designed to perform a pre-delivery credit check on a subscriber's account before invoking a delivery attempt if this operation is supported by the pre-paid billing system.

0098It will be appreciated that the invention provides a mechanism that ensures that the full capabilities of messaging in the PLMN domain can be delivered to users in the IP domain. While this has been illustrated for SMS service in the above description, the invention can also be applied in a similar manner to other messaging services such as instant messaging, multi-media messaging, and message broadcast services. The IPG can be re-configured for delivery of a different message type by implementing an appropriate interface module to the appropriate messaging server in the PLMN domain, for example Instant Messaging server, Multi-media server, etc. In addition, the node <b>1</b> may be suitably configured to operate successfully with a range of network technologies both in the PLMN domain and in the packet data domain.

0099The invention is not limited to the embodiments described but may be varied in construction and detail.