System and method for application to peer messaging in a communication network

Abstract

Disclosed is a system (202) and a method (400) for Application to Peer (A2P) messaging in a communication network (100). The system (202) includes a diameter interfacing unit (308) and a Session Initiation Protocol (SIP) interfacing unit (310). The diameter interfacing unit (308) receives an A2P message associated with a user account in the communication network (100) and triggers a Mobile Network Portability (MNP) server (214) to determine whether or not the user account corresponds to a client service provider in the communication network (100). Thereafter, the Session Initiation Protocol (SIP) interfacing unit (310) attempts a transmission of the A2P message through a SIP interface, based on a determination that the user account corresponds to a service provider other than the client service provider, in the communication network (100).

Description

SYSTEM AND METHOD FOR APPLICATION TO PEER MESSAGING IN A COMMUNICATION NETWORKTECHNICAL FIELD

[0001] The embodiments of the present disclosure generally relate to the field of wireless communication networks. More particularly, the present disclosure relates to a system and a method for Application to Peer (A2P) messaging in a communication network.BACKGROUND OF THE INVENTION

[0002] The subject matter disclosed in the background section should not be assumed or construed to be prior art merely because of its mention in the background section. Similarly, any problem statement mentioned in the background section or its association with the subject matter of the background section should not be assumed or construed to have been previously recognized in the prior art.

[0003] Contemporary telecommunication systems are Third Generation Partnership Project (3GPP) compliant and follow communication protocols provided by the 3 GPP standards of telecommunication. These communication systems typically rely on Session Initiation Protocol (SIP) interface communications for Application to Peer (A2P) messaging internally to the network (i.e., communication with subscribers of a service provider) and Mobile Application Protocol (MAP) interface communications for messaging externally to the network (i.e., communication with subscribers of other service providers). As the users of telecommunication services use different service providers, the number of A2P requests using MAP interface communication channel is much higher than those using SIP interface communication channel. This results in over exhaustion of resources at the MAP interface and keeps them occupied with traffic. With an increase in the number oftelecom users, the burden on MAP interface is increasing, which is resulting in failure of the A2P messaging.

[0004] In view of the abovementioned broad problem, there is a need for a technical solution that can reduce the burden on the MAP interface and tackle the increasing count of A2P messaging failure.SUMMARY

[0005] The following embodiments present a simplified summary in order to provide a basic understanding of some aspects of the disclosed invention. This summary is not an extensive view, and it is not intended to identify key / critical elements or to delineate the scope thereof. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.

[0006] According to an embodiment of the present disclosure, a method for Application to Peer (A2P) messaging in a communication network is presented. The method includes receiving, from a computer-implemented application by a diameter interfacing unit at an Internet Protocol Short Message Gateway (IPSMGW), an A2P message associated with a user account in the communication network. The method further includes determining, by a Mobile Network Portability (MNP) server, whether the user account corresponds to a client service provider in the communication network. Furthermore, the method includes attempting, by a Session Initiation Protocol (SIP) interfacing unit at the IPSMGW, a transmission of the A2P message through a SIP interface, based on a determination that the user account corresponds to a service provider other than the client service provider, in the communication network.

[0007] In some aspects of the present disclosure, for determining whether the user account corresponds to a client service provider, the method includes transmitting,by the diameter interfacing unit at the IPSMGW, a MNP request to the MNP server, wherein the MNP request enables the MNP server to determine whether a domain associated with the user account is configured at the computer-implemented application. The domain configured at the computer-implemented application indicates that the user account corresponds to the client service provider. Moreover, the domain not configured at the computer-implemented application indicates that the user account corresponds to the service provider other than the client service provider, in the communication network.

[0008] In some aspects of the present disclosure, , upon attempting the transmission of the A2P message for the user account, corresponding to the service provider other than the client service provider, through the SIP interface, the method includes determining, by a processing unit at the IPSMGW, whether the attempt for transmission of the A2P message, for the user account corresponding to the service provider other than the client service, succeeded or failed through the SIP interface. Moreover, the method includes transmitting, by a Mobile Application Part (MAP) interfacing unit at the IPSMGW, the A2P message through a MAP interface, based on the determination that the attempt for transmission of the A2P message through the SIP interface failed.

[0009] In some aspects of the present disclosure, in response to the determination that the user account corresponds to the client service provider, the method includes transmitting, by the diameter interfacing unit at the A2P-IPSMGW, a query to a Home Subscriber Server (HSS). Moreover, the method includes attempting, by the SIP interfacing unit at the A2P-IPSMGW, a transmission of the A2P message through the SIP interface, based on a successful transmission of the query to the HSS.

[0010] In some aspects of the present disclosure, upon attempting the transmission of the A2P message, for the user account corresponding to the client service provider, through the SIP interface, the method includes determining, by the processing unit at the IPSMGW, whether the attempt for transmission of the A2Pmessage, for the user account corresponding to the client service provider, succeeded or failed through the SIP interface. Moreover, the method includes transmitting, by the MAP interfacing unit at the IPSMGW, the A2P message through the MAP interface, based on the determination that the attempt for transmission of the A2P message through the SIP interface failed.

[0011] In some aspects of the present disclosure, the A2P message is an automated text message generated by the computer-implemented application for one or more user accounts in the communication network.

[0012] According to another embodiment of the present disclosure, an Application to Peer (A2P) messaging system in a communication network is provided. The A2P messaging system includes a diameter interfacing unit and a Session Initiation Protocol (SIP) interfacing unit. The diameter interfacing unit is configured to receive, from a computer-implemented application, an A2P message associated with a user account in the communication network. The SIP interfacing unit is configured to attempt a transmission of the A2P message through a SIP interface, based on a determination that the user account corresponds to a service provider other than the client service provider, in the communication network. A Mobile Network Portability (MNP) server determines whether the user account corresponds to a client service provider in the communication network.

[0013] According to yet another embodiment of the present disclosure, computerprogram product for Application to Peer (A2P) messaging in a communication network is provided. The computer-program product comprising computerexecutable instructions that are stored on a non-transitory computer-readable medium and that, when executed by at least one processor performs operations. The operations include receiving, from a computer-implemented application, an A2P message associated with a user account in the communication network. Moreover, the operations include determining whether the user account corresponds to a client service provider in the communication network. Furthermore, the operations include attempting a transmission of the A2P message through a SIP interface, based on adetermination that the user account corresponds to a service provider other than the client service provider, in the communication network.BRIEF DESCRIPTION OF DRAWINGS

[0014] Various embodiments disclosed herein will become better understood from the following detailed description when read with the accompanying drawings. The accompanying drawings constitute a part of the present disclosure and illustrate certain non-limiting embodiments of inventive concepts disclosed herein. Further, components and elements shown in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. For the purpose of consistency and ease of understanding, similar components and elements are annotated by reference numerals in the exemplary drawings.

[0015] FIG. 1 is a block diagram illustrating a communication network, in accordance with an embodiment of the present disclosure.

[0016] FIG. 2 is a block diagram illustrating exemplary components of a core network of the communication network, in accordance with an embodiment of the present disclosure.

[0017] FIG. 3 is a block diagram that illustrates exemplary components of an Internet Protocol Messaging Gateway (IPSMGW) of the core network, in accordance with an embodiment of the present disclosure.

[0018] FIG. 4 illustrates a flow chart that depicts a method for Application to Peer (A2P) messaging in the communication network, in accordance with an embodiment of the present disclosure.LIST OF REFERENCE NUMERALSThe following list is provided for convenience and in support of the drawing figures and as part of the text of the specification, which describe innovations by reference to multiple items. Items not listed here may nonetheless be part of a given embodiment. For better legibility of the text, a given reference number is recited near some, but not all, recitations of the referenced item in the text. The same reference number may be used with reference to different examples or different instances of a given item. The list of reference numerals is as follows:100 - Communication network102 - Core network104 - Nodes106 - Devices202 - IPSMGW204 - EMS206 - STP208 - DRA210 - HSS212 - Database(s)214 - MNP216 - Internal ESME(s)218 - Policy Server300 - Application Console302 - Communication Interface304 - Processing Circuitry306 - Gateway Memory307 - First Communication Bus308 - Diameter Interfacing Unit310 - SIP Interfacing Unit312 - Processing Unit314 - MAP Interfacing Unit316 - Notification Unit317 - Second Communication Bus318 - Data Repository320 - Instructions Repository400 - Method for A2P messaging402-420 - Operational Blocks of Method 400DETAILED DESCRIPTION OF THE INVENTION

[0019] Inventive concepts of the present disclosure will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of one or more embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Further, the one or more embodiments disclosed herein are provided to describe the inventive concept thoroughly and completely, and to fully convey the scope of each of the present inventive concepts to those skilled in the art. Furthermore, it should be noted that the embodiments disclosed herein are not mutually exclusive concepts. Accordingly, one or more components from one embodiment may be tacitly assumed to be present or used in any other embodiment.

[0020] The following description presents various embodiments of the present disclosure. The embodiments disclosed herein are presented as teaching examples and are not to be construed as limiting the scope of the present disclosure. The present disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, including the exemplary design and implementation illustrated and described herein, but may be modified, omitted, or expanded upon without departing from the scope of the present disclosure.

[0021] The following description contains specific information pertaining to embodiments in the present disclosure. The detailed description uses the phrases “in some embodiments” which may each refer to one or more or all of the same or different embodiments. The term “some” as used herein is defined as “one, or morethan one, or all.” Accordingly, the terms “one,” “more than one,” “more than one, but not all” or “all” would all fall under the definition of “some.” In view of the same, the terms, for example, “in an embodiment” refers to one embodiment and the term, for example, “in one or more embodiments” refers to “at least one embodiment, or more than one embodiment, or all embodiments.”

[0022] The term “comprising,” when utilized, means “including, but not necessarily limited to;” it specifically indicates open-ended inclusion in the so-described one or more listed features, elements in a combination, unless otherwise stated with limiting language. Furthermore, to the extent that the terms “includes,” “has,” “have,” “contains,” and other similar words are used in either the detailed description, such terms are intended to be inclusive in a manner similar to the term “comprising.”

[0023] In the following description, for the purposes of explanation, various specific details are set forth to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features.

[0024] The description provided herein discloses exemplary embodiments only and is not intended to limit the scope, applicability, or configuration of the present disclosure. Rather, the foregoing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing any of the exemplary embodiments. Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it may be understood by one of the ordinary skilled in the art that the embodiments disclosed herein may be practiced without these specific details.

[0025] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As usedherein the description, the singular forms "a", "an", and "the" include plural forms unless the context of the invention indicates otherwise.

[0026] The terminology and structure employed herein are for describing, teaching, and illuminating some embodiments and their specific features and elements and do not limit, restrict, or reduce the scope of the present disclosure. Accordingly, unless otherwise defined, all terms, and especially any technical and / or scientific terms, used herein may be taken to have the same meaning as commonly understood by one having ordinary skill in the art.

[0027] Various aspects of the present disclosure provide a system and a method for Application to Peer (A2P) messaging in a communication network. The system provides a solution to communication traffic in the traditional A2P messaging systems by sending the A2P message through Session Initiation Protocol (SIP) interface when a Mobile Application Protocol (MAP) request failure is detected, thereby reducing the communication traffic via the MAP interface. In some aspects of the present disclosure, the system provides a task load balancing between components of the communication network by diverting task load of an overutilized component to another component which is under-utilized.

[0028] Embodiments of the present disclosure will be described below in detail with reference to the accompanying drawings. FIG. 1 through FIG. 4, discussed below, and the one or more embodiments used to describe the principles of the present disclosure are by way of illustration only and should not be construed in any way to limit the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged system or device.

[0029] FIG. 1 is a block diagram illustrating operating environment of a communication network 100, in accordance with an embodiment of the present disclosure. As illustrated in FIG. 1, the communication network 100 may include acore network 102 (hereinafter interchangeably referred to and designated as ‘the network 102’) coupled with a plurality of nodes includingNode 104-1 throughNode 104-N and configured to facilitate a secured communication among the plurality of nodes (collectively referred to as the “nodes 104”, and individually referred to as the “node 104”, hereinafter). In some aspects of the present disclosure, the Nodes 104 may be coupled to the core network 102 through a load balancer (not shown) that enables distribution of processing load of the nodes 104 to the core network 102.

[0030] In an embodiment, each of the nodes are configured to be coupled with one or more user devices 106-1, 106-2, 106-3, 106-4, through 106-(N-l), 106-N (collectively referred to and designated as the “user devices 106”, and individually referred to as the “user device 106”, hereinafter). In one aspect, the core network 102 may establish a secured communication between the one or more user devices 106 associated with the plurality of nodes 104. In another aspect, the core network 102 may establish a secured communication between the one or more user devices 106 associated with the same node 104.

[0031] In an exemplary embodiment, the core network 102 may effectively establish a secured communication between the user device 106-1 and the user device 106-2, where the user device 106-1 and the user device 106-2 both are coupled with the Node 104-1. In another embodiment, the core network 102 may establish a secured communication between the user device 106-2 and the user device 106-N with equal effectiveness, where the user device 106-2 is coupled with the Node 104-1 and the user device 106-N is coupled with the Node 104-N.

[0032] In an exemplary embodiment, the core network 102 (also, referred to as ‘network 102’, herein) may be configured as an application server and may be communicably operational or may be integrated with a user device 106 via a network coupled with a server. The core network 102 may pertain to 5G servicebased architecture and may be configured to interconnect distinct networksassociated with the architecture. Therefore, the core network 102 may provide a path for the exchange of information between one or more of the networks, and corresponding subnetworks.

[0033] Although FIG. 1 illustrates one example of the communication network 100, various changes may be made to FIG. 1. For example, the communication network 100 may include any number of nodes and / or user devices 106 in any suitable arrangement, without deviating from the scope of the present disclosure. Further, various components in FIG. 1 may be combined, further subdivided, or omitted and additional components may be added according to particular needs.

[0034] FIG. l is a block diagram that illustrates exemplary components of the core network 102, in accordance with an embodiment of the present disclosure. As presented in FIG. 2, the core network 102 may include multiple Network Functions (NFs). Each NF may be deployed in the form of a data processing node within the communication network 100, configured to perform data processing and / or data storage operations to enable the overall functionality of Application to Peer (A2P) messaging, as discussed in the present disclosure. According to the exemplary embodiment presented through FIG. 2, the NFs may include an Internet Protocol Messaging Gateway (IPSMGW) 202 specifically configured for A2P messaging, an Element Management System (EMS) 204, a Signal Transfer Point (STP) 206, a Diameter Routing Agent (DRA) 208, a Home Subscriber Server (HSS) 210, database(s) 212, a Mobile Network Portability (MNP) 214 (hereinafter interchangeably referred to and designated as ‘MNP server 214’), External Short Messaging Entities (ESME) 216, and a policy server 218.

[0035] Preferably, the operation(s) for A2P messaging in the communication network 100 are performed by the IPSMGW 202 supported by the various other entities of the core network 102 as presented herein. As presented in FIG. 2, the IPSMGW 202 may be connected to the EMS 204 via a REST Application Protocol Interface (API), the STP 206 via a Signaling and Transport (SIGTRAN) interface,the DRA208 via a diameter Sh interface, database(s) 212 via Transportation Control Protocol (TCP) interface(s), MNP 214 via a Session Initiation Protocol (SIP) interface, and with the ESME 216 via a Short Message Peer-Peer (SMPP) interface. The DRA 208 may further be coupled to the HSS 210 via the diameter Sh interface. The diameter Sh interface may be configured to communicate User-Data-request (UDR) and User-Data- Answer (UDA) commands between the IPSMGW 202 and the HSS 210 via the DRA 208.

[0036] The EMS 204 may be configured to manage network elements within the core network 102. Specifically, the EMS 204 may provide an Input-Output (VO) interface for a user to provide input(s) for configuration of the IPSMGW 202 for receiving messaging requests and amending run-time. The STP 206 may be configured for initiating, maintaining, modifying, and terminating real-time communications sessions between Internet Protocol (IP) devices. Specifically, the STP 206 may be connected to a Mobile Application Port (MAP) interface that is configured to send A2P message(s) to the peer. Particularly, each of the A2P message(s) is an automated text message generated by the computer-implemented application for one or more user accounts in the communication network.

[0037] The DRA 208 may be configured to couple the HSS 210 with the IPSMGW 202. The HSS 210 may be configured to send a query (e.g., ‘sh-query’) to determine traffic at the SIP interface. Preferably, the database(s) 212 may include a Cassandra database to store data and instructions associated with the IPSMGW 202. The database(s) 212 may further include a Redis database to store data and instructions associated with the A2P messaging.

[0038] The MNP 214 may be configured to retain information associated with a user account while switching a network provider. Particularly the MNP 214 may be configured to enable the A2P message to be transmitted to the peer via the SIP interface. The ESME 216 may be a server configured to host an external application that connects to the IPSMGW 202 to engage in the sending or receiving of the A2Pmessages. In some aspects of the present disclosure, the ESME 216 may be configured to host a computer-application running hosted on an application console 300 (as shown in FIG. 3) of the IPSMGW 202. The IPSMGW 202 may further be supported by the policy server 218 configured to generate and provide operational policies for the IPSMGW 202 to enable A2P messaging.

[0039] In operation, the IPSMGW 202 may be configured to receive an application to peer (A2P) message to be transmitted to the peer. The A2P message comprises information of the peer to send the A2P message and a message content. The IPSMGW 202 may further be configured to generate a Mobile Network Portability (MNP) request based on the A2P message for the MNP 214. Furthermore, the IPSMGW 202 may be configured to receive a response of the MNP request from the MNP 214 for determining whether a domain associated with the peer is configured at an application end (i.e., through the computer-implemented application hosted at the application console 300 of the IPSMGW 202).

[0040] In an exemplary scenario, when the domain is configured at the application end the IPSMGW 202 may be configured to send a query to the peer via the Home Subscriber Server (HSS) 210. The IPSMGW 202 may further be configured to determine whether an acknowledgement for delivery of the query to the peer is received. In response to the reception of the acknowledgement, the IPSMGW 202 may be configured to transmit the A2P message to the peer via the SIP interface. The IPSMGW 202 may further be configured to determine whether the A2P message is delivered to the peer via the SIP. In another exemplary scenario, when the A2P message delivery fails via the SIP interface, the IPSMGW 202 may be configured to initiate delivery of the A2P message via the MAP interface. In yet another exemplary scenario, when the A2P messaging fails via the MAP interface, the IPSMGW 202 may be configured to transmit the A2P message to the peer via the SIP again.

[0041] Although FIG. 2 illustrates one example of the core network 102, various changes may be made to FIG. 2. For example, the core network 102 may include any number of components, where various components of the core network 102 (as presented in FIG. 2) may be combined, further subdivided, or omitted and additional components may be added according to particular needs.

[0042] FIG. 3 is a block diagram that illustrates exemplary components of the IPSMGW 202, in accordance with an embodiment of the present disclosure. Particularly, the IPSMGW may be configured as (hereinafter interchangeably referred to and designated) an Application to Peer (A2P) messaging system 202. The IPSMGW 202 may include a communication interface 302, processing circuitry 304 and a gateway memory 306 coupled to each other by way of a first communication bus 307.

[0043] The communication interface 302 may be configured to enable the IPSMGW 202 to communicate with various other entities of the communication network 100 via the core network 102. Examples of the communication interface 302 may include, but are not limited to, a MODEM, a network interface such as an Ethernet card, a communication port, and / or a Personal Computer Memory Card International Association (PCMCIA) slot and card, an antenna, a radio frequency (RF) transceiver, amplifier(s), a tuner, oscillator(s), a digital signal processor, a coder-decoder (CODEC) chipset, a Subscriber Identity Module (SIM) card, and a local buffer circuit. It will be apparent to a person of ordinary skill in the art that the communication interface 302 may include any device and / or apparatus capable of providing wireless or wired communications between the IPSMGW 202 and various other entities of the core network 102.

[0044] The processing circuitry 304 may include processor(s) (comprising data processing engines) configured with suitable logic, instructions, circuitry, interfaces, and / or codes for executing operations of various operations performed by the IPSMGW 202. Examples of the processing circuitry 304 may include, butare not limited to, an Application Specific Integrated Chip (ASIC) processor, a RISC processor, a CISC processor, a Field Programmable Gate Array (FPGA), and the like. According to an exemplary embodiment, the processing circuitry 304 may include a diameter interfacing unit 308, a Session Initiation Protocol (SIP) interfacing unit 310, a processing unit 312, a Mobile Application Part (MAP) interfacing unit 314. In some aspects of the present disclosure, the processing circuitry 304 may further include a notification unit 316. Various components of the processing circuitry 304 may be coupled to each other by way of a second communication bus 317.

[0045] The diameter interfacing unit 308 may be configured to receive an A2P message associated with a user account in the communication network from the computer-implemented application hosted by the application console 300. More particularly, the A2P message may be shared with the diameter interfacing unit 308 via the ESME 216. Specifically, the ESME 216 may be configured as an application end server configured to host a computer-application running, in absence of the application console 300 at the IPSMGW 202 (or as back-up, when the resource(s) of the application console 300 are over-utilized). The A2P message may include an identifier of an account (i.e., related to a subscriber / user or a user device 106, in the communication network 100) for transmission of the A2P message to the user device 106. The diameter interfacing unit 308 may trigger the MNP server 214 to determine whether the user account corresponds to a client service provider in the communication network 100 or not. Specifically, the client service provider may be a service provider associated with the computer-implemented application for A2P messaging in the communication network.

[0046] For example, when the computer-implemented application is operated and / or regulated by service provider ‘A’ in the communication network and if the user account (or the subscriber) is identified being associated with the service provider ‘A’, then the MNP server 214 may identify the user account being associated with the client service provider. In another scenario of the same example,when the client service provider is ‘A’ in the communication network 100 and the user account is associated with another service provider ‘B’ in the communication network 100 and not ‘A’, then the MNP server 214 may identify the user account not being associated with the client service provider.

[0047] Preferably, for determining whether the user account corresponds to the client service provider, the diameter interfacing unit 308 may be configured to transmit a MNP request to the MNP server 214 that triggers the MNP server 214 to fetch details of a domain associated with the user account. Moreover, based on the details of the domain, the MNP server 214 may determine whether a domain associated with the user account is configured at the computer-implemented application. Particularly, the domain configured at the computer-implemented application indicates that the user account corresponds to the client service provider. Moreover, the domain not configured at the computer-implemented application indicates that the user account corresponds to the service provider other than the client service provider, in the communication network.

[0048] The SIP interfacing unit 310 may be configured to attempt a transmission of the A2P message through a SIP interface, based on a determination that the user account corresponds to a service provider other than the client service provider, in the communication network 100. Upon attempting the transmission of the A2P message for the user account, corresponding to the service provider other than the client service provider, through the SIP interface, the processing unit 312 may be configured to determine whether the attempt for transmission of the A2P message, for the user account corresponding to the service provider other than the client service, succeeded or failed through the SIP interface. Moreover, the MAP interfacing unit 314 may be configured to the A2P message through a MAP interface, based on the determination that the attempt for transmission of the A2P message through the SIP interface failed.

[0049] In response to the determination that the user account corresponds to the client service provider, the diameter interfacing unit 308 may be configured totransmit a query (e.g., sh-query) to the Home Subscriber Server (HSS) 210. Typically, the query is framed using a "Document Selector Key" which specifies a type of data being requested by the diameter interfacing unit 308 and / or the identifier of the user device 106. The query to the HSS 210 may enable the HSS 210 to fetch occupancy details of the SIP interface for the A2P message transmission. Preferably, a successful transmission of the query to the HSS 210 indicates that the SIP interface may be available for transmission of the A2P message. Moreover, an unsuccessful transmission of the query to the HSS 210 may indicate unavailability (or occupancy) of the SIP interface for transmission of the A2P message. The SIP interfacing unit 310 may be configured to attempt the transmission of the A2P message to the user account through the SIP interface, based on the successful transmission of the query to the HSS 210.

[0050] Upon attempting the transmission of the A2P message, for the user account corresponding to the client service provider, through the SIP interface, the processing unit 312 may be configured to determine whether the attempt for transmission of the A2P message, for the user account corresponding to the client service provider, succeeded or failed through the SIP interface. The MAP interfacing unit 314 may be configured to the A2P message through the MAP interface, based on the determination that the attempt for transmission of the A2P message through the SIP interface failed.

[0051] In some aspects of the present disclosure, the notification unit 316 may be configured to generate notification(s) for each event associated with the operations of the IPSMGW 202. Examples of the events may include, but are not limited to, determination that the user account corresponds to the client service provider in the communication network 100 or not, determination that the domain associated with the user account is configured at the computer-implemented application or not, determination whether the transmission of the A2P message through the SIP interface succeeded or failed, etc.

[0052] Various components of the processing circuitry 304 are presented to illustrate the functionality driven by the IPSMGW 202. It will be apparent to a person having ordinary skill in the art that various engines in the processing circuitry 304 are for illustrative purposes and not limited to any specific combination of hardware circuitry and / or software.

[0053] The gateway memory 306 may be configured to store logic, instructions, circuitry, interfaces, and / or codes of the processing circuitry 304 for executing various operations of the IPSMGW 202. Aspects of the present disclosure are intended to include and / or otherwise cover any type of the data associated with the IPSMGW 202, without deviating from the scope of the present disclosure. Examples of the gateway memory 306 may include but are not limited to, a ROM, a RAM, a flash memory, a removable storage drive, a HDD, a solid-state memory, a magnetic storage drive, a PROM, an EPROM, and / or an EEPROM.

[0054] In some aspects of the present disclosure, the gateway memory 306 may be segregated into multiple repositories that may be configured to store a specific type of data. In the exemplary embodiment as presented through FIG. 3, the gateway memory 306 includes data repository 318 and an instructions repository. The data repository 318 may be configured to store data object(s) corresponding to various operations of the processing circuitry 304. The instructions repository 320 may be configured to store instructions and / or codes for operations performed by the various components of the IPSMGW 202.

[0055] In an embodiment of the present disclosure, the instructions repository 320 may be configured as a non-transitory storage medium. Examples of the instructions repository 320 configured as the non-transitory storage medium includes hard drives, solid-state drives, flash drives, Compact Disk (CD), Digital Video Disk (DVD), and the like. Aspects of the present disclosure are intended to include or otherwise cover any type of non-transitory storage medium as the instructions repository 320, without deviating from the scope of the present disclosure. As willbe appreciated, any such computer program instructions stored in the instructions repository 320 may be executed by one or more computer processors, including without limitation a general-purpose computer or special purpose computer, or other programmable processing apparatus to produce a machine, such that the computer program instructions which execute on the computer processor(s) or other programmable processing apparatus create means for implementing the function(s) specified.

[0056] It will be apparent to a person of ordinary skill in the art that the repositories in the gateway memory 306 are presented based on the functionality of the IPSMGW 202 and are not limited to those disclosed. The gateway memory 306 may have any configuration, combination and / or count of repositories without deviating from the scope of the present disclosure.

[0057] Although FIG. 3 illustrates one example of the IPSMGW 202, various changes may be made to FIG. 3, without deviating from the scope of the present disclosure. Further, the IPSMGW 202 may include any number of components in addition to those shown in FIG.3 without deviating from the scope of the present disclosure. Further, various components in FIG. 3 may be combined, further subdivided, or omitted and additional components may be added according to particular needs.

[0058] FIG. 4 illustrates a flow chart that depicts a method 400 for A2P messaging in the communication network 100, in accordance with an exemplary embodiment of the present disclosure. The method 400 includes operational steps as presented by way of blocks 402 through 420, as presented below.

[0059] At block 402, the IPSMGW 202 may receive the A2P message from the computer implemented application via the ESME 216. The A2P message may include the identifier of the user device 106 comprising information of the user device 106 to send the A2P message.

[0060] At block 404, the IPSMGW 202 may generate the MNP request for the MNP server 214 based on the identifier of the user device 106 in the A2P message. The MNP request may enable the MNP server 214 to determine whether the user account corresponds to the client service provider in the communication network 100.

[0061] In some aspects of the present disclosure, for determining whether the user account corresponds to a client service provider, the MNP server 214 may determine whether the domain associated with the user account is configured at the computer- implemented application. The domain configured at the computer-implemented application indicates that the user account corresponds to the client service provider whereas the domain not configured at the computer-implemented application indicates that the user account corresponds to the service provider other than the client service provider, in the communication network 100.

[0062] At block 406, when the domain associated with the user device 106 is configured at the computer-implemented application, the method 400 proceeds to block 408. Else, the method 400 proceeds to block 416.

[0063] At block 408, the IPSMGW 202 may generate and send the query (e.g., sh- query) to the HSS 210.

[0064] At block 410, when the query to the HSS 210 is found successful (e.g., an acknowledgement is received from the HSS 210 in response to the query), the method 400 proceeds to block 412. Else the method 400 halts.

[0065] At block 412, the IPSMGW 202 may attempt to transmit the A2P message to the peer via the SIP interface.

[0066] At block 414, the IPSMGW 202 may determine whether the A2P message is delivered to the peer via the SIP interface. When the IPSMGW 202 determines that the A2P message was delivered via the SIP interface, the method 400 halts. Elsewhen the IPSMGW 202 determines that the delivery of the A2P message failed via the SIP interface, the method 400 proceeds to block 416.

[0067] At block 416, the IPSMGW 202 may send the MAP request to the MAP interface via the STP 206. The MAP request corresponds to an access to transmit the A2P message through the MAP interface.

[0068] At block 418, the IPSMGW 202 may determine whether an acknowledgement is received from the MAP interface in response to the MAP request. The second acknowledgement corresponds to the successful MAP request. Particularly, the failure of the MAP request may depict that the MAP interface is over occupied to utilize resources for sending the A2P message to the peer at the time of the MAP request. When the IPSMGW 202 determines that the MAP request failed, the method 400 falls back to block 412. Else when the IPSMGW 202 determines that the MAP request was successful and the acknowledgement to the MAP request was received, the method 400 proceeds to block 420.

[0069] At block 420, the IPSMGW 202 may attempt to transmit the A2P message to the peer via the MAP interface.

[0070] Now, referring to the technical abilities and operational advantageous effect of the present disclosure, operational advantages that may be provided by one or more embodiments. The technical advantages of the present disclosure can be derived through the various components of the system 202 and the method 400 for A2P messaging in the communication network 100. Particularly, the system 202 provides an alternative communication channel (in the form of SIP interface) when a A2P message failure is determined form the MAP interface, and vice-versa. Thus, the system 202 enables A2P messaging using SIP interface instead of an MAP interface over-burdened by traffic being used for A2P messaging.

[0071] Those skilled in the art will appreciate that the methodology described herein in the present disclosure may be carried out in other specific ways than those set forth herein in the above disclosed embodiments without departing from essential characteristics and features of the present invention. The above-described embodiments are therefore to be construed in all aspects as illustrative and not restrictive.

[0072] The drawings and the forgoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, orders of processes described herein may be changed and are not limited to the manner described herein. Any combination of the above features and functionalities may be used in accordance with one or more embodiments.

[0073] In the present disclosure, each of the embodiments has been described with reference to numerous specific details which may vary from embodiment to embodiment. The foregoing description of the specific embodiments disclosed herein may reveal the general nature of the embodiments herein that others may, by applying current knowledge, readily modify and / or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications are intended to be comprehended within the meaning of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and is not limited in scope.

Claims

We Claim:

1. A method (400) for Application to Peer (A2P) messaging in a communication network (100), the method (400) comprising: receiving, from a computer-implemented application by a diameter interfacing unit (308) at an Internet Protocol Short Message Gateway (IPSMGW) (202), an A2P message associated with a user account in the communication network (100); determining, by a Mobile Network Portability (MNP) server (214), whether the user account corresponds to a client service provider in the communication network (100); and attempting, by a Session Initiation Protocol (SIP) interfacing unit (310) at the IPSMGW (202), a transmission of the A2P message through a SIP interface, based on a determination that the user account corresponds to a service provider other than the client service provider, in the communication network (100).

2. The method (400) as claimed in claim 1, wherein, for determining whether the user account corresponds to a client service provider, the method (400) comprising: transmitting, by the diameter interfacing unit (308) at the IPSMGW (202), a MNP request to the MNP server (214), wherein the MNP request enables the MNP server (214) to determine whether a domain associated with the user account is configured at the computer-implemented application, wherein the domain configured at the computer-implemented application indicates that the user account corresponds to the client service provider, and the domain not configured at the computer-implemented application indicates that the user account corresponds to the service provider other than the client service provider, in the communication network (100).

3. The method (400) as claimed in claim 1, wherein, upon attempting the transmission of the A2P message for the user account, corresponding to the serviceprovider other than the client service provider, through the SIP interface, the method (400) comprising: determining, by a processing unit (312) at the IPSMGW (202), whether the attempt for transmission of the A2P message, for the user account corresponding to the service provider other than the client service, succeeded or failed through the SIP interface; and transmitting, by a Mobile Application Part (MAP) interfacing unit (314) at the IPSMGW (202), the A2P message through a MAP interface, based on the determination that the attempt for transmission of the A2P message through the SIP interface failed.

4. The method (400) as claimed in claim 3, wherein, in response to the determination that the user account corresponds to the client service provider, the method (400) comprising: transmitting, by the diameter interfacing unit (308) at the IPSMGW (202), a query to a Home Subscriber Server (HSS (210)); and attempting, by the SIP interfacing unit (310) at the IPSMGW (202), a transmission of the A2P message through the SIP interface, based on a successful transmission of the query to the HSS (210).

5. The method (400) as claimed in claim 4, wherein, upon attempting the transmission of the A2P message, for the user account corresponding to the client service provider, through the SIP interface, the method (400) comprising: determining, by the processing unit (312) at the IPSMGW (202), whether the attempt for transmission of the A2P message, for the user account corresponding to the client service provider, succeeded or failed through the SIP interface; and transmitting, by the MAP interfacing unit (314) at the IPSMGW (202), the A2P message through the MAP interface, based on the determination that the attempt for transmission of the A2P message through the SIP interface failed.

6. The method (400) as claimed in claim 1, wherein the A2P message is an automated text message generated by the computer-implemented application for one or more user accounts in the communication network (100).

7. An Application to Peer (A2P) messaging system (202) in a communication network (100), the system comprising: a diameter interfacing unit (308) configured to receive, from a computer- implemented application, an A2P message associated with a user account in the communication network (100); and a Session Initiation Protocol (SIP) interfacing unit (310) configured to attempt a transmission of the A2P message through a SIP interface, based on a determination that the user account corresponds to a service provider other than the client service provider, in the communication network (100), wherein a Mobile Network Portability (MNP) server determines whether the user account corresponds to a client service provider in the communication network (100).

8. The A2P messaging system (202) as claimed in claim 7, wherein for determining whether the user account corresponds to a client service provider, the diameter interfacing unit (308) is configured to: transmit a MNP request to the MNP server (214), wherein the MNP request enables the MNP server (214) to determine whether a domain associated with the user account is configured at the computer-implemented application, wherein the domain configured at the computer-implemented application indicates that the user account corresponds to the client service provider, and the domain not configured at the computer-implemented application indicates that the user account corresponds to the service provider other than the client service provider, in the communication network (100).

9. The A2P messaging system (202) as claimed in claim 7, further comprising a processing unit (312) and a Mobile Application Part (MAP) interfacing unit (314), wherein, upon attempting the transmission of the A2P message for the user account,corresponding to the service provider other than the client service provider, through the SIP interface: the processing unit (312) is configured to determine whether the attempt for transmission of the A2P message, for the user account corresponding to the service provider other than the client service, succeeded or failed through the SIP interface; and the MAP interfacing unit (314) is configured to transmit the A2P message through a MAP interface, based on the determination that the attempt for transmission of the A2P message through the SIP interface failed.

10. The A2P messaging system (202) as claimed in claim 9, wherein, in response to the determination that the user account corresponds to the client service provider: the diameter interfacing unit (308) is configured to transmit a query to a Home Subscriber Server (HSS) (210); and the SIP interfacing unit (310) is configured to attempt a transmission of the A2P message through the SIP interface, based on a successful transmission of the query to the HSS (210).

11. The A2P messaging system (202) as claimed in claim 10, wherein, upon attempting the transmission of the A2P message, for the user account corresponding to the client service provider, through the SIP interface: the processing unit (312) is configured to determine whether the attempt for transmission of the A2P message, for the user account corresponding to the client service provider, succeeded or failed through the SIP interface; and the MAP interfacing unit (314) is configured to transmit the A2P message through the MAP interface, based on the determination that the attempt for transmission of the A2P message through the SIP interface failed.

12. The A2P messaging system (202) as claimed in claim 7, wherein the A2P message is an automated text message generated by the computer-implemented application for one or more user accounts in the communication network (100).

113. A computer-program product for Application to Peer (A2P) messaging in a communication network (100), the computer-program product comprising computer-executable instructions that are stored on a non-transitory computer- readable medium and that, when executed by at least one processor performs operations comprising: receiving, from a computer-implemented application, an A2P message associated with a user account in the communication network (100); determining whether the user account corresponds to a client service provider in the communication network (100); and attempting a transmission of the A2P message through a SIP interface, based on a determination that the user account corresponds to a service provider other than the client service provider, in the communication network (100).

Images