FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR OPTIMISING AN IP SHORT MESSAGE GATEWAY (IPSMGW) MESSAGING SERVICE”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR OPTIMISING AN IP SHORT MESSAGE GATEWAY (IPSMGW) MESSAGING SERVICE
FIELD OF INVENTION
[0001] Embodiments of the present disclosure generally relate to network performance management systems. More particularly, embodiments of the present disclosure relate to method and system for optimising an IP short message gateway (IPSMGW) messaging service.
BACKGROUND
[0002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. The third generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless

communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
[0004] In a communication network, usually when user A sends an SMS to user B, a request is received at a one or more first IP Short Message Gateway (IPSMGW) side. From the one or more first IPSMGW site, a MNP request is shared to get details about the User B such as operator details etc. Upon fetching operator details of the User B, a Diameter request is shared to DRA to confirm the amount to be charged for the SMS delivery and execute the charge. After this, an SRI request is shared by the one or more first IPSMGW confirm to a global title (GT) to a terminal IPSMGW to fetch the GT. This GT is shared back to the one or more first IPSMGW and upon fetching the GT, a Mobile Terminated (MT) request to share the SMS is shared by the one or more first IPSMGW to the user B via a SIP-Delivery. An Acknowledgement of the SMS is shared back to the one or more first IPSMGW and then to the User A. However, the terminal IPSMGW is not aware as to which of the one or more first IPSMGW the GT is to be delivered, leading to failure in the SMS Delivery.
[0005] Further, over the period of time various solutions have been developed that attempt to improve the performance of the communication devices, particularly for improving the SMS delivery within a communication network. However, there are certain challenges with existing solutions which do not provide an optimal solution for the SMS delivery such as in case, an IPSMGW of a vendor receives a message from a first UE, or a mobile originated (MO) request over SIP, then in that case, the IPSMGW is required to send the message to SMSC of another vendor and the SMSC forwards the message to a second UE over a Mobile Application Part (MAP), and there is a requirement for both IPSMGW as well as SMSC for supporting SIP and MAP configurations. Further, another challenge with existing solutions was that the overall traffic on the network is not efficiently managed.

[0006] Thus, there exists an imperative need in the art for an improved and optimised messaging service and the IPSMGW within a communication network to allow an improvement in the SMS Delivery, which the present disclosure aims to address.
SUMMARY
[0007] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.
[0008] An aspect of the present disclosure may relate to a method for optimising an IP short message gateway (IPSMGW) messaging service. The method comprising receiving, by a transceiver unit from a first user associated with a first network, a short message service (SMS) request comprising one or more SMS request parameters. The method further comprises initiating, by a processing unit from one or more first IPSMGW associated with the first user, a mobile number portability (MNP) request associated with the second user. The method further comprises initiating, by the processing unit to a Diameter Routing Agent (DRA) associated with the first user, a diameter request, wherein the diameter request is at least a charge request associated with the SMS request based on at least the MNP request. The method further comprises initiating, by the processing unit from the one or more first IPSMGW associated with the first user to at least one second IPSMGW associated with a second user, a Send Routing Information (SRI) request based on at least the diameter response of the diameter request. The method further comprises receiving, by the processing unit at the one or more first IPSMGW, a routing information based on the SRI response of the SRI request. The method further comprises initiating, by the processing unit from the one or more first IPSMGW via a target protocol associated with the first network, a mobile terminated (MT) request associated with the SMS request based on at least the

routing information. The method further comprises delivering, by the processing unit from the first user to the second user, an SMS message associated with the SMS request based on initiating the mobile terminated (MT) request from the one or more first IPSMGW via the target protocol.
[0009] In an exemplary aspect of the present disclosure, the method further comprises validating, by a validation unit, at least one of an SMS service validity associated with the first user and one or more SMS request parameters validity based on the SMS request.
[0010] In an exemplary aspect of the present disclosure, the method further comprises transmitting, by the transceiver unit to the one or more first IP Short Message Gateway (IPSMGW) associated with the first user, the SMS request based on at least one of a positive SMS service validity associated with the SMS service validity and a positive SMS request parameters validity associated with the one or more SMS request parameters validity.
[0011] In an exemplary aspect of the present disclosure, the MNP request associated with the second user is based on at least one of the positive SMS service validity and the positive SMS request parameters validity, wherein the MNP request is at least an operator detail request associated with the second user, and a Location Routing Number (LRN) request associated with the second user.
[0012] In an exemplary aspect of the present disclosure, the method further comprises receiving, at the one or more first IPSMGW from a Short Message Service Centre SMSC (Front-End), the routing information based on the SRI response, wherein the routing information comprises at least one target first IPSMGW from the one or more first IPSMGW.
[0013] In an exemplary aspect of the present disclosure, the IPSMGW and the SMSC (Front-End) are integrated to optimise the IPSMGW messaging service.

[0014] In an exemplary aspect of the present disclosure, the target protocol is at least one of a Session Initiation Protocol (SIP) or a Mobile Application Part (MAP).
[0015] In an exemplary aspect of the present disclosure, the method further comprises receiving at the one or more first IPSMGW, an acknowledgement based on delivering the SMS message from the first user to the second user.
[0016] In an exemplary aspect of the present disclosure, the SMS service validity associated with the first user is determined based on a prestored service data associated with the first user, and wherein the one or more SMS request parameters validity based on the SMS request is determined based on at least the prestored service data and a predefined set of SMS service rules associated with at least the first network.
[0017] Another aspect of the present disclosure may relate to a system for optimising an IP short message gateway (IPSMGW) messaging service. The system comprises a transceiver unit and a processing unit connected to each other. The transceiver unit is configured to receive, from a first user associated with a first network, a short message service (SMS) request comprising one or more SMS request parameters. The processing unit is configured to initiate, from the one or more first IPSMGW associated with the first user, a mobile number portability (MNP) request associated with the second user. The processing unit is further configured to initiate, to a Diameter Routing Agent (DRA) associated with the first user, a diameter request, wherein the diameter request is at least a charge request associated with the SMS request based on at least the MNP request. The processing unit is further configured to initiate, from the one or more first IPSMGW associated with the first user to at least one second IPSMGW associated with a second user, a Send Routing Information (SRI) request based on at least the diameter request. The processing unit is further configured to receive, at the one or more first IPSMGW, a routing information based on the SRI response. The processing unit is further

configured to initiate, from the one or more first IPSMGW via a target protocol associated with the first network, a mobile terminated (MT) request associated with the SMS request based on at least the routing information. The processing unit is further configured to deliver, from the first user to the second user, an SMS message associated with the SMS request based on initiating the mobile terminated (MT) request from the one or more first IPSMGW via the target protocol.
[0018] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for optimising an IP short message gateway (IPSMGW) messaging service, the instructions include executable code which, when executed by one or more units of a system, causes: a transceiver unit of the system to receive, from a first user associated with a first network to a second user, a short message service (SMS) request comprising one or more SMS request parameters; a processing unit of the system to initiate, from the one or more first IPSMGW associated with the first user, a mobile number portability (MNP) request associated with the second user; the processing unit of the system to initiate, to a Diameter Routing Agent (DRA) associated with the first user, a diameter request, wherein the diameter request is at least a charge request associated with the SMS request based on at least the MNP request; the processing unit of the system to initiate, from the one or more first IPSMGW associated with the first user to at least one second IPSMGW associated with the a second user, a Send Routing Information (SRI) request based on at least the diameter request. Further, the instructions include executable code which, when executed by one or more units of a system causes the processing unit of the system to receive, at the one or more first IPSMGW, a routing information based on the SRI response; the processing unit of the system to initiate, from the one or more first IPSMGW via a target protocol associated with the first network, a mobile terminated (MT) request associated with the SMS request based on at least the routing information; the processing unit of the system to deliver, from the first user to the second user, an SMS message associated with the SMS request based on initiating the mobile

terminated (MT) request from the one or more first IPSMGW via the target protocol.
OBJECTS OF THE INVENTION
[0019] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0020] It is an object of the present disclosure to provide a system and a method for optimising an Internet Protocol Short Messaging Service (IPSMGW) messaging service.
[0021] It is an object of the present disclosure to provide a system and a method for improved SMS delivery within a communication network to allow an improvement in the SMS Delivery.
[0022] It is another object of the present disclosure to provide a solution that provides time-efficient delivery of SMS.
[0023] It is yet another object of the present disclosure to provide a solution for optimal delivery of the SMS.
DESCRIPTION OF THE DRAWINGS
[0024] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system

according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components. 5
[0025] FIG. 1 illustrates a system architecture of an IP short message gateway (IPSMGW) clusters, in accordance with exemplary implementations of the present disclosure.
10 [0026] FIG. 2 illustrates an exemplary block diagram of a computing device upon
which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
[0027] FIG. 3 illustrates an exemplary block diagram of a system for optimising an
15 IP short message gateway (IPSMGW) messaging service, in accordance with
exemplary implementations of the present disclosure.
[0028] FIG. 4 illustrates a method flow diagram indicating the process for
optimising an IP short message gateway (IPSMGW) messaging service in
20 accordance with exemplary implementations of the present disclosure.
[0029] The foregoing shall be more apparent from the following more detailed description of the disclosure.
25 DETAILED DESCRIPTION
[0030] In the following description, for the purposes of explanation, various
specific details are set forth in order to provide a thorough understanding of
embodiments of the present disclosure. It will be apparent, however, that
30 embodiments of the present disclosure may be practiced without these specific
details. Several features described hereafter may each be used independently of one
9

another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.
5 [0031] The ensuing description provides exemplary embodiments only, and is not
intended to limit the scope, applicability, or configuration of the disclosure. Rather,
the ensuing description of the exemplary embodiments will provide those skilled in
the art with an enabling description for implementing an exemplary embodiment.
It should be understood that various changes may be made in the function and
10 arrangement of elements without departing from the spirit and scope of the
disclosure as set forth.
[0032] Specific details are given in the following description to provide a thorough
understanding of the embodiments. However, it will be understood by one of
15 ordinary skill in the art that the embodiments may be practiced without these
specific details. For example, circuits, systems, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
20 [0033] Also, it is noted that individual embodiments may be described as a process
which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process
25 is terminated when its operations are completed but could have additional steps not
included in a figure.
[0034] The word “exemplary” and/or “demonstrative” is used herein to mean
serving as an example, instance, or illustration. For the avoidance of doubt, the
30 subject matter disclosed herein is not limited by such examples. In addition, any
aspect or design described herein as “exemplary” and/or “demonstrative” is not
10

necessarily to be construed as preferred or advantageous over other aspects or
designs, nor is it meant to preclude equivalent exemplary structures and techniques
known to those of ordinary skill in the art. Furthermore, to the extent that the terms
“includes,” “has,” “contains,” and other similar words are used in either the detailed
5 description or the claims, such terms are intended to be inclusive—in a manner
similar to the term “comprising” as an open transition word—without precluding any additional or other elements.
[0035] As used herein, a “processing unit” or “processor” or “operating processor”
10 includes one or more processors, wherein processor refers to any logic circuitry for
processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a Digital Signal Processing (DSP) core, a controller, a microcontroller, Application Specific
15 Integrated Circuits, Field Programmable Gate Array circuits, any other type of
integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
20
[0036] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device
25 or equipment, capable of implementing the features of the present disclosure. The
user equipment/device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may
30 contain at least one input means configured to receive an input from at least one of
11

a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.
[0037] As used herein, “storage unit” or “memory unit” refers to a machine or
5 computer-readable medium including any mechanism for storing information in a
form readable by a computer or similar machine. For example, a computer-readable
medium includes read-only memory (“ROM”), random access memory (“RAM”),
magnetic disk storage media, optical storage media, flash memory devices or other
types of machine-accessible storage media. The storage unit stores at least the data
10 that may be required by one or more units of the system to perform their respective
functions.
[0038] As used herein “interface” or “user interface refers to a shared boundary
across which two or more separate components of a system exchange information
15 or data. The interface may also be referred to a set of rules or protocols that define
communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
20 [0039] All modules, units, components used herein, unless explicitly excluded
herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller,
25 Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array
circuits (FPGA), any other type of integrated circuits, etc.
[0040] As used herein the transceiver unit include at least one receiver and at least
one transmitter configured respectively for receiving and transmitting data, signals,
30 information, or a combination thereof between units/components within the system
and/or connected with the system.
12

[0041] As discussed in the background section, the current known solutions have
several shortcomings. The present disclosure aims to overcome the above-
mentioned and other existing problems in this field of technology by providing
5 method and system of optimising an IP short message gateway (IPSMGW)
messaging service. The SMS message is received at IPSMGW, then it sends the
MNP (mobile number portability) query and after it is successful, the IPSMGW
sends the charging request and after successful charging, the IPSMGW receives the
routing information of the message based on SRI response to the SRI request, then
10 the IPSMGW sends the message to the target IPSMGW via target protocol (i.e. via
SIP or MAP).
[0042] FIG. 1 illustrates an exemplary architecture diagram of an Internet Protocol Short Message Gateway (IPSMGW), in which the system for optimising a short
15 message service (SMS) barring service is built, in accordance with exemplary
implementations of the present disclosure. The architecture diagram [100] of the IPSMGW [102] comprising an Element Management System (EMS) [104], a Signalling Transfer Point (STP) [106], a Serving-Call Session Control Function (SCSCF) [112], a Load Balancer [126], a Diameter Routing Agent (DRA) [132], a
20 Short Message Peer-to-Peer (SMPP) [120], an SMPP Charging Point (CP) [128], a
Mobile Number Portability (MNP) server [130], an Online Charging System (OCS) [134], a Home Subscriber Server (HSS) [136], a Service Capability Exposure Function (SCEF) [138], a Mobility Management Entity (MME) [140], a Database [114], a Transmission Control Protocol (TCP) [118], a Mobile Application Part
25 (MAP) [110], a Representational State Transfer (REST) [108], and a Session
Initiation Protocol (SIP) [122]. Also, all of the components/ units of the system [100] are assumed to be connected to each other unless otherwise indicated below.
[0043] IPSMGW (IP Short Message Gateway) [102]: A network element
30 responsible for handling and routing Short Message Service (SMS) messages over
IP networks.
13

[0044] EMS (Element Management System) [104]: A software system used for managing and monitoring network elements or devices within a telecommunications network. 5
[0045] STP (Signalling Transfer Point) [106]: A network node used in the SS7 (Signalling System No. 7) telecommunications protocol to route signalling messages between signalling endpoints.
10 [0046] SCSCF (Serving-Call Session Control Function) [112]: A core component
in IMS (IP Multimedia Subsystem) networks responsible for session control and call processing.
[0047] Load Balancer [126]: A device or software component that evenly
15 distributes incoming network traffic across multiple servers to optimize resource
utilization, reliability, and performance.
[0048] DRA (Diameter Routing Agent) [132]: A network element responsible for
routing Diameter protocol messages within telecommunications networks, often
20 used in IMS and LTE networks.
[0049] SMPP (Short Message Peer-to-Peer) [120]: A protocol used in the telecommunications industry for exchanging SMS messages between Short Message Service Centres (SMSCs) and SMS application systems. 25
[0050] SMPP CP (SMPP Charging Point) [128]: A network element responsible for charging and billing functions within a telecommunications network.
[0051] MNP (Mobile Number Portability) [130]: A service that allows mobile
30 phone users to retain their phone numbers when switching between different service
providers.
14

[0052] OCS (Online Charging System) [134]: A system used for real-time charging and billing of telecommunications services, such as voice calls, data usage, and SMS messages. 5
[0053] HSS (Home Subscriber Server) [136]: A core component in LTE and IMS networks that stores subscriber-related information, such as user profiles, authentication data, and service subscriptions.
10 [0054] SCEF (Service Capability Exposure Function) [138]: A component in IMS
networks that exposes network capabilities to application servers, enabling the creation of innovative multimedia services.
[0055] MME (Mobility Management Entity) [140]: A key component in LTE
15 networks responsible for managing the mobility of mobile devices, including
tracking their location and handling handovers between base stations.
[0056] Database [114]: A structured collection of data organized for efficient
storage, retrieval, and management. The database [114] is connected with the
20 IPSMGW [102], the IPSMGW [102] stores and retrieves the information at the
database [114]. The connection between the IPSMGW [102] and the database [114] is done via transmission control protocol (TCP) [118].
[0057] TCP (Transmission Control Protocol) [118]: A reliable, connection-oriented
25 protocol used for transmitting data over networks.
[0058] MAP (Mobile Application Part) [110]: A protocol used in cellular networks for communication between various network elements, such as HLRs (Home Location Registers) and VLRs (Visitor Location Registers). 30
15

[0059] REST (Representational State Transfer) [108]: An architectural style for designing networked applications, commonly used in web services development.
[0060] SIP (Session Initiation Protocol) [116]: SIP is a signalling protocol used for
5 initiating, maintaining, and terminating real-time sessions in IP-based
communication networks. It is commonly used for voice and video calls, instant messaging, and multimedia conferencing over the Internet. SIP allows devices to establish communication sessions and negotiate the parameters of the session, such as codecs, media types, and session duration.
10
[0061] FIG. 2 illustrates an exemplary block diagram of a computing device [200] (also referred to herein as a computer system [200]) upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an implementation, the computing
15 device [200] may also implement a method for optimising an IP short message
gateway (IPSMGW) messaging service utilising the system. In another implementation, the computing device [200] itself implements the method for optimising the IP short message gateway (IPSMGW) messaging service using one or more units configured within the computing device [200], wherein said one or
20 more units are capable of implementing the features as disclosed in the present
disclosure.
[0062] The computing device [200] may include a bus [202] or other communication mechanism for communicating information, and a hardware
25 processor [204] coupled with bus [202] for processing information. The hardware
processor [204] may be, for example, a general-purpose microprocessor. The computing device [200] may also include a main memory [206], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [202] for storing information and instructions to be executed by the processor [204]. The
30 main memory [206] also may be used for storing temporary variables or other
intermediate information during execution of the instructions to be executed by the
16

processor [204]. Such instructions, when stored in non-transitory storage media
accessible to the processor [204], render the computing device [200] into a special-
purpose machine that is customized to perform the operations specified in the
instructions. The computing device [200] further includes a read only memory
5 (ROM) [208] or other static storage device coupled to the bus [202] for storing static
information and instructions for the processor [204].
[0063] A storage device [210], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [202] for storing information and
10 instructions. The computing device [200] may be coupled via the bus [202] to a
display [212], such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device [214], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the
15 bus [202] for communicating information and command selections to the processor
[204]. Another type of user input device may be a cursor controller [216], such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [204], and for controlling cursor movement on the display [212]. This input device typically has two degrees
20 of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow
the device to specify positions in a plane.
[0064] The computing device [200] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware,
25 and/or program logic which in combination with the computing device [200] causes
or programs the computing device [200] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device [200] in response to the processor [204] executing one or more sequences of one or more instructions contained in the main memory [206]. Such
30 instructions may be read into the main memory [206] from another storage medium,
such as the storage device [210]. Execution of the sequences of instructions
17

contained in the main memory [206] causes the processor [204] to perform the process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions. 5
[0065] The computing device [200] also may include a communication interface [218] coupled to the bus [202]. The communication interface [218] provides a two-way data communication coupling to a network link [220] that is connected to a local network [222]. For example, the communication interface [218] may be an
10 integrated services digital network (ISDN) card, cable modem, satellite modem, or
a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface [218] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such
15 implementation, the communication interface [218] sends and receives electrical,
electromagnetic, or optical signals that carry digital data streams representing various types of information.
[0066] The computing device [200] can send messages and receive data, including
20 program code, through the network(s), the network link [220] and the
communication interface [218]. In the Internet example, a server [230] might
transmit a requested code for an application program through the Internet [228], the
ISP [226], the local network [222], the host [224] and the communication interface
[218]. The received code may be executed by the processor [204] as it is received,
25 and/or stored in the storage device [210], or other non-volatile storage for later
execution.
[0067] Referring to FIG. 3, an exemplary block diagram of a system [300] for
optimising an IP short message gateway (IPSMGW) messaging service, is shown,
30 in accordance with the exemplary implementations of the present disclosure. The
system [300] comprises at least one transceiver unit [302], at least one processing
18

unit [304], and at least one validation unit [306]. Also, all of the components/ units
of the system [300] are assumed to be connected to each other unless otherwise
indicated below. As shown in the figures all units shown within the system should
also be assumed to be connected to each other. Also, in FIG. 3, only a few units are
5 shown, however, the system [300] may comprise multiple such units or the system
[300] may comprise any such numbers of said units, as required to implement the
features of the present disclosure. In another implementation, the system [300] may
reside in a server or a network entity like IPSMGW or SMSC. In yet another
implementation, the system [300] may reside partly in the server/ network entity
10 and partly in the user device. The IPSMGW messaging service is a service which
facilitates the exchange of a short message service (SMS) such as a short text messages over an Internet Protocol (IP) network.
[0068] The system [300] is configured for optimising the IP short message gateway
15 (IPSMGW) messaging service with the help of the interconnection between the
components/units of the system [300].
[0069] The transceiver unit [302] of the system [300] is configured to receive from a first user associated with a first network, a short message service (SMS) request
20 comprising one or more SMS request parameters. The first user may be a user
device or a subscriber who is sending a message to a second user which may be another user device or another subscriber or a network entity. The first network may refer to a telecom network or a communication network including the network entities between the communication channel of the first user and the second user.
25 The SMS request may be a request for sending a message to the second user. The
one or more SMS request parameters, such as an action parameter, a username parameter, a password parameter, and an SMS originator parameter, are associated with the SMS request. Further, the one or more SMS request parameters may have a predefined possible value in a predefined manner based on the SMS request, such
30 as the action parameter having the predefined possible value, i.e., a send message
19

value, and the username parameter having the predefined value, which is a string value having a maximum length of 16 characters.
[0070] The present disclosure further discloses that messages can be marked as
5 spam depending on the message signature, total messages sent within a
configurable duration, blocked keywords, blacklisting, etc. The present disclosure supports dynamic filtering of messages based on regulatory guidelines and messages sent by subscribers not registered as telemarketers etc.
10 [0071] Further, the processing unit [304] of the system [300] is configured to
initiate, from one or more first IPSMGW associated with the first user, a mobile number portability (MNP) request associated with the second user. The one or more first IPSMGW may refer to the IPSMGW associated with the first user and/or the first network where the first user may be connected with the one or more first
15 IPSMGW. The second user may refer to the service provider or the operator
associated with the first user. The MNP request is sent to an MNP server/database [130], to check the operator/domain of Party B (SMS receiving entity) and to determine whether the Party B has ported the mobile number. The MNP server upon receiving the MNP query, looks up Party B using B’s MSISDN (phone number) in
20 its database, and return LRN to the IPSMGW.
[0072] Further, the processing unit [304] of the system [300] is configured to initiate, to a Diameter Routing Agent (DRA) [132] associated with the first user, a diameter request [124], wherein the diameter request [124] is at least a charge
25 request associated with the SMS request based on at least the MNP request. The
DRA may be a network element responsible for facilitating the routing and management of diameter protocol messages within a network such as the 3G or the 4G (LTE) network, thereby ensuring that the messages are routed among the correct elements in a network. The diameter protocol messages may be used for
30 implementing one of an authentication, an authorisation, and an accounting
function in the network. The diameter request [124] may be a request containing
20

the information and attributes related to authentication, authorisation, and
accounting as part of the diameter protocol. The charge request may be the request
comprising charge details such as billing charge or a fee, associated with the SMS
request and the MNP request. The charge details may be the charges such as billing
5 charges or fees, associated with providing the services for SMS and MNP by the
service provider. The DRA [132] can route the diameter request [124] to the OCS [134] for the charge request. The OCS [134] based on the diameter request [124] and the charge request can then determine the charges and billing information for the user based on the services used by the user. The charges applicable for SMS and
10 MNP may also be provided by the OCS [134] based on the DRA [132]. Further, the
OCS [134] also verifies the subscription of the user, if it allows sending SMS or additional charges are required to be applied and then authorizes the delivery of the SMS based on the account balance or credit limits of the user. The diameter messages carry routing information in order to ensure delivery of the messages.
15
[0073] Further, as disclosed by the present disclosure, the processing unit [304] of the system [300] is configured to initiate, from the one or more first IPSMGW associated with the first user to at least one second IPSMGW associated with the second user, a Send Routing Information (SRI) request based on at least a diameter
20 response of the diameter request [124]. The at least one second IPSMGW may be
the IPSMGW at which the second user may be connected with the at least second IPSMGW. The SRI request may be a type of diameter message used within the diameter protocol request for receiving routing information of the user. The diameter response is the response to the diameter request [124]. The diameter
25 response may contain the information and attributes related to the authentication,
the authorisation, and the accounting as part of the diameter protocol. The diameter response may also be a response received from the OCS [134] which indicates whether the charge request was successful or not successful due to a reason. The reason may be due to unsubscribed service or may also be due to insufficient
30 balance. The response may also indicate successful charging based on the DRA
[132].
21

[0074] Further, the processing unit [304] of the system [300] is configured to
receive, at the one or more first IPSMGW, a routing information based on an SRI
response of the SRI request. The routing information may be the information
relating to the routing of the messages such as a user profile, a subscription details,
5 a service restriction and an authentication parameter from a home subscriber server
(HSS) and/or a subscriber profile repository associated with the network. The SRI
response is the response to the SRI request initiated from the one or more first
IPSMGW. The SRI response is the type of diameter message used within the
diameter protocol and comprises information for receiving routing information of
10 the user.
[0075] Further, as disclosed herein, the processing unit [304] of the system [300] is
configured to initiate, from the one or more first IPSMGW via a target protocol
associated with the first network, a mobile terminated (MT) request associated with
15 the SMS request based on at least the routing information. The MT request refers
to a message sent from a mobile SMS provider system to a subscriber’s mobile phone i.e., the message is terminated at the mobile phone of the subscriber’s mobile phone.
20 [0076] Further, as disclosed by the present disclosure, the target protocol is at least
one of a Session Initiation Protocol (SIP) or a Mobile Application Part (MAP).
[0077] The present disclosure provides that the IPSMGW [102] is also responsible for performing the functions of a Short Message Service Centre (SMSC). The
25 SMSC is responsible for handling and routing messages such as short message
services over the 2G/3G networks. Therefore, the present disclosure provides a solution that provides that the IPSMGW [102] and the SMSC are integrated and supports the functionalities of both the SIP and the MAP. The integration of the IPSMGW and the SMSC as disclosed in the present disclosure helps in balancing
30 the load between the SIP and the MAP by initiating the MT request via the target
22

protocol. The integration of IPSMGW [102] with the SMSC also helps in
supporting the short message service in 2G/3G networks via the MAP. The
integration of the IPSMGW [102] with the SMSC also helps in cases where the
IPSMGW [102] is to be used for signalling IP messages over the SIP. Additionally,
5 to reduce the load of IPSMGW [102] for sending the SMS using the SIP, some of
the SMS(s) are sent over the MAP via the integrated SMSC of the IPSMGW [102]. This helps in optimizing the message service of the IPSMGW [102]. The selection of target domain is based on the operating entity or a network entity or a service provider associated with the messaging service. In case, the operating entity of the
10 message receiver is same as the operating entity of a sender of the SMS, then the
target protocol may be the SIP. However, in case the operating entity of the receiver of the message is different i.e. not same, then in that case the target protocol may be the MAP. Hence, for initiating the MT request via the target protocol the operating entity is required to be analysed. For checking whether the operating
15 entity is same or different, the MNP request sent to the MNP server/ database [130]
is analysed for determination of the operator/domain of the mobile number. The analysis of the LRN helps in determination of the operating entity.
[0078] Further, as disclosed herein, the processing unit [304] of the system [300] is
20 configured to deliver, from the first user to the second user, an SMS message
associated with the SMS request based on initiating the mobile terminated (MT) request from the one or more first IPSMGW via the target protocol. The SMS message may be the message which the first user is trying to send to the second user. 25
[0079] Further, the system [300] further comprises the validation unit [306]
connected at least to the processing unit [304], the validation unit [306] is
configured to validate at least one of a SMS service validity associated with the first
user and one or more SMS request parameters validity based on the SMS request.
30 The SMS service validity may refer to the validity of the SMS services for the first
user and the second user, which may also check for the validity of the mobile
23

numbers associated with each of the first user and the second user. The validity of
the SMS services may be a check performed by the validation unit [306] to validate
that the users are allowed to use the SMS services. The one or more SMS request
parameters validity may refer to the validity of the SMS request based on certain
5 SMS request parameters.
[0080] The SMS service validity associated with the first user is determined based on a prestored service data associated with the first user, and wherein the one or more SMS request parameters validity based on the SMS request is determined
10 based on at least the prestored service data and a predefined set of SMS service
rules associated with at least the first network. The SMS service validity is determined based on the prestored service data, wherein the prestored service data may refer to a Home Location Register (HLR) which stores the information related the subscribers i.e., the first user and the second user. The predefined set of SMS
15 service rules may refer to a SMS service rules which may be preset based on the
needs and requirements of the service provider or operators.
[0081] Further, the transceiver unit [302] of the system [300] is further configured to transmit to the one or more first IPSMGW associated with the first user, the SMS
20 request based on at least one of a positive SMS service validity associated with the
SMS service validity and a positive SMS request parameters validity associated with the one or more SMS request parameters validity. The positive SMS service validity may refer to a positive response of the validation of the SMS service validity indicating a success, i.e., the SMS service is valid for the particular user.
25 The positive SMS service validity may also refer to the positive response of the
validation of the one or more SMS request parameters that indicates a success based on the predefined set of SMS service rules, i.e., the SMS request is valid.
[0082] Further, as disclosed by the present disclosure, the MNP request associated
30 with the second user is based on at least one of the positive SMS service validities
and the positive SMS request parameters validity, wherein the MNP request is at
24

least an operator detail request associated with the second user, and a Location
Routing Number (LRN) request associated with the second user. The operator
details request may be the request or a query which is made for retrieving the
information associated with the network operator or the network service provider
5 of the second user. The LRN request may refer to a request seeking the LRN. The
LRN may refer to a response to the LRN request and may comprise of a ten-digit number used for routing calls and messages used for number portability feature and identifies the new location of a ported subscriber.
10 [0083] Further, the transceiver unit [302] of the system [300] is further configured
to receive, at the one or more first IPSMGW from a Short Message Service Centre SMSC (Front-End), the routing information based on the SRI response, wherein the routing information comprises at least one target first IPSMGW from the one or more first IPSMGW. The SMSC (Front-End) may refer to the user interface or
15 application which allows administrators or the network operators to interact with a
SMSC system. Further, the SMSC system facilitates configuration, managing, and monitoring of the SMS messaging services that are provided by the SMSC. The SMSC is a core component of mobile network which is responsible for facilitation of sending, receiving, and routing of the SMS messages. The target IPSMGW may
20 be the terminating IPSMGW at which the SMS message is received, and associated
with the second user.
[0084] The present disclosure further discloses that the IPSMGW and the SMSC (Front-End) may also be integrated to optimise the IPSMGW messaging service. 25
[0085] Furthermore, the transceiver unit [302] of the system [300] is further
configured to receive, at the one or more first IPSMGW, an acknowledgement
based on delivering the SMS message from the first user to the second user. The
acknowledgement may be a message or an indication showing that the SMS
30 message has been successfully delivered.
25

[0086] Referring to FIG. 4, an exemplary method flow diagram [400] for
optimising an IP short message gateway (IPSMGW) messaging service, in
accordance with exemplary implementations of the present disclosure is shown. In
an implementation the method [400] is performed by the system [300]. Further, in
5 an implementation, the system [300] may be present in a server device to implement
the features of the present disclosure. The IPSMGW messaging service is a service which facilitates the exchange of short text messages (SMS) over the Internet Protocol networks.
10 [0087] Also, as shown in FIG. 4, the method [400] starts at step [402].
[0088] Next, at step [404], the method [400] comprises receiving, by a transceiver unit [302] from a first user associated with a first network, a short message service (SMS) request comprising one or more SMS request parameters. The first user may
15 be a user device or a subscriber who is sending a message to a second user which
may be another user device or another subscriber or a network entity. The first network may refer to a telecom network or communication network including network entities between the communication channel of the first user and the second user. The SMS request may be a request for sending a message to the second
20 user. The one or more SMS request parameters, such as an action parameter, a
username parameter, a password parameter, and an SMS originator parameter, are associated with the SMS request. Further, the one or more SMS request parameters may have a predefined possible value in a predefined manner based on the SMS request, such as the action parameter having the predefined possible value, i.e., a
25 send message value, and the username parameter having the predefined value,
which is a string value having a maximum length of 16 characters.
[0089] The present disclosure further discloses that messages can be marked as
spam depending on the message signature, total messages sent within a
30 configurable duration, blocked keywords, blacklisting, etc. The present disclosure
26

supports dynamic filtering of messages based on regulatory guidelines and messages sent by subscribers not registered as telemarketers etc.
[0090] At step [406], the method [400] comprises initiating, by a processing unit
5 [304] from one or more first IPSMGW associated with the first user, a mobile
number portability (MNP) request associated with the second user. The one or more first IPSMGW may refer to the IPSMGW associated with the first user and/or the first network where the first user may be connected with the one or more first IPSMGW. The second user may refer to the service provider or the operator
10 associated with the first user. The MNP request is sent to an MNP server/database
[130], to check the operator/domain of Party B (SMS receiving entity) and to determine whether the Party B has ported the mobile number. The MNP server upon receiving the MNP query, looks up Party B using B’s MSISDN (phone number) in its database, and return LRN to the IPSMGW.
15
[0091] At step [408], the method [400] comprises initiating, by the processing unit [304] to a Diameter Routing Agent (DRA) [132] associated with the first user, a diameter request [124], wherein the diameter request [124] is at least a charge request associated with the SMS request based on at least the MNP request. The
20 DRA may be a network element responsible for facilitating the routing and
management of diameter protocol messages within a network such as the 3G or the 4G (LTE) network, thereby ensuring that the messages are routed among the correct elements in a network. The diameter protocol messages may be used for implementing one of an authentication, an authorisation, and an accounting
25 function in the network. The diameter request [124] may be a request containing
the information and attributes related to authentication, authorisation, and accounting as part of the diameter protocol. The charge request may be the request comprising charge details such as billing charge or a fee, associated with the SMS request and the MNP request. The charge details may be the charges such as billing
30 charges or fees, associated with providing the services for SMS and MNP by the
service provider. The DRA [132] can route the diameter request [124] to the OCS
27

[134] for the charge request. The OCS [134] based on the diameter request [124]
and the charge request can then determine the charges and billing information for
the user based on the services used by the user. The charges applicable for SMS and
MNP may also be provided by the OCS [134] based on the DRA [132]. Further, the
5 OCS [134] also verifies the subscription of the user, if it allows sending SMS or
additional charges are required to be applied and then authorizes the delivery of the SMS based on the account balance or credit limits of the user. The diameter messages carry routing information in order to ensure delivery of the messages.
10 [0092] At step [410], the method [400] comprises initiating, by the processing unit
[304] from the one or more first IPSMGW associated with the first user to at least one second IPSMGW associated with a second user, a Send Routing Information (SRI) request based on at least a diameter response of the diameter request [124]. The at least one second IPSMGW may be the IPSMGW at which the second user
15 may be connected with the at least second IPSMGW. The SRI request may be a
type of diameter message used within the diameter protocol request for receiving routing information of the user. The diameter response is the response to the diameter request [124]. The diameter response may contain the information and attributes related to the authentication, the authorisation, and the accounting as part
20 of the diameter protocol. The diameter response may also be a response received
from the OCS [134] which indicates whether the charge request was successful or not successful due to a reason. The reason may be due to unsubscribed service or may also be due to insufficient balance. The response may also indicate successful charging based on the DRA [132].
25
[0093] At step [412], the method [400] comprises receiving, by the processing unit
[304] at the one or more first IPSMGW, a routing information based on an SRI
response of the SRI request. The routing information may be the information
relating to the routing of the messages such as a user profile, a subscription details,
30 a service restriction and an authentication parameter from a home subscriber server
28

(HSS) and/or a subscriber profile repository associated with the network. The SRI
response is the response to the SRI request initiated from the one or more first
IPSMGW. The SRI response is the type of diameter message used within the
diameter protocol and comprises information for receiving routing information of
5 the user.
[0094] At step [414], the method [400] comprises initiating, by the processing unit
[304] from the one or more first IPSMGW via a target protocol associated with the
first network, a mobile terminated (MT) request associated with the SMS request
10 based on at least the routing information. The MT request refers to a message sent
from a mobile SMS provider system to a subscriber’s mobile phone i.e., the message is terminated at the mobile phone of the subscriber’s mobile phone.
[0095] The target protocol is at least one of a Session Initiation Protocol (SIP) or a
15 Mobile Application Part (MAP).
[0096] The present disclosure provides that the IPSMGW [102] is also responsible for performing the functions of a Short Message Service Centre (SMSC). The SMSC is responsible for handling and routing messages such as short message
20 services over the 2G/3G networks. Therefore, the present disclosure provides a
solution that provides that the IPSMGW [102] and the SMSC are integrated and supports the functionalities of both the SIP and the MAP. The integration of the IPSMGW and the SMSC as disclosed in the present disclosure helps in balancing the load between the SIP and the MAP by initiating the MT request via the target
25 protocol. The integration of IPSMGW [102] with the SMSC also helps in
supporting the short message service in 2G/3G networks via the MAP. The integration of the IPSMGW [102] with the SMSC also helps in cases where the IPSMGW [102] is to be used for signalling IP messages over the SIP. Additionally, to reduce the load of IPSMGW [102] for sending the SMS using the SIP, some of
30 the SMS(s) are sent over the MAP via the integrated SMSC of the IPSMGW [102].
29

This helps in optimizing the message service of the IPSMGW [102]. The selection
of target domain is based on the operating entity or a network entity or a service
provider associated with the messaging service. In case, the operating entity of the
message receiver is same as the operating entity of a sender of the SMS, then the
5 target protocol may be the SIP. However, in case the operating entity of the receiver
of the message is different i.e. not same, then in that case the target protocol may
be the MAP. Hence, for initiating the MT request via the target protocol the
operating entity is required to be analysed. For checking whether the operating
entity is same or different, the MNP request sent to the MNP server/ database [130]
10 is analysed for determination of the operator/domain of the mobile number. The
analysis of the LRN helps in determination of the operating entity.
[0097] At step [416], the method [400] comprises delivering, by the processing unit
[304] from the first user to the second user, an SMS message associated with the
15 SMS request based on initiating the mobile terminated (MT) request from the one
or more first IPSMGW via the target protocol. The SMS message may be the message which the first user is trying to send to the second user.
[0098] The present disclosure further discloses that the method [400] further
20 comprises validating, by a validation unit [306], at least one of an SMS service
validity associated with the first user and one or more SMS request parameters
validity based on the SMS request. The SMS service validity may refer to the
validity of the SMS services for the first user and the second user, which may also
check for the validity of the mobile numbers associated with each of the first user
25 and the second user. The validity of the SMS services may be a check performed
by the validation unit [306] to validate that the users are allowed to use the SMS services. The one or more SMS request parameters validity may refer to the validity of the SMS request based on certain SMS request parameters.
30 [0099] The SMS service validity associated with the first user is determined based
on a prestored service data associated with the first user, and wherein the one or
30

more SMS request parameters validity based on the SMS request is determined
based on at least the prestored service data and a predefined set of SMS service
rules associated with at least the first network. The SMS service validity is
determined based on the prestored service data, wherein the prestored service data
5 may refer to a Home Location Register (HLR) which stores the information related
the subscribers i.e., the first user and the second user. The predefined set of SMS service rules may refer to a SMS service rules which may be preset based on the needs and requirements of the service provider or operators.
10 [0100] The present disclosure further discloses that the method further comprises
transmitting, by the transceiver unit [302] to the one or more first IP Short Message Gateway (IPSMGW) associated with the first user, the SMS request based on at least one of a positive SMS service validity associated with the SMS service validity and a positive SMS request parameters validity associated with the one or more
15 SMS request parameters validity. The positive SMS service validity may refer to a
positive response of the validation of the SMS service validity indicating a success, i.e., the SMS service is valid for the particular user. The positive SMS service validity may also refer to the positive response of the validation of the one or more SMS request parameters that indicates a success based on the predefined set of SMS
20 service rules, i.e., the SMS request is valid.
[0101] The MNP request associated with the second user is based on at least one of the positive SMS service validity and the positive SMS request parameters validity, wherein the MNP request is at least an operator detail request associated with the
25 second user, and a Location Routing Number (LRN) request associated with the
second user. The operator details request may be the request or a query which is made for retrieving the information associated with the network operator or the network service provider of the second user. The LRN request may refer to a request seeking the LRN. The LRN may refer to a response to the LRN request and may
30 comprise of a ten-digit number used for routing calls and messages used for number
portability feature and identifies the new location of a ported subscriber.
31

[0102] The present disclosure further discloses that the method [400] further
comprises receiving, at the one or more first IPSMGW from a Short Message
Service Centre SMSC (Front-End), the routing information based on the SRI
5 response, wherein the routing information comprises at least one target first
IPSMGW from the one or more first IPSMGW. The SMSC (Front-End) may refer
to the user interface or application which allows administrators or the network
operators to interact with a SMSC system. Further, the SMSC system facilitates
configuration, managing, and monitoring of the SMS messaging services that are
10 provided by the SMSC. The SMSC is a core component of mobile network which
is responsible for facilitation of sending, receiving, and routing of the SMS messages. The target IPSMGW may be the terminating IPSMGW at which the SMS message is received, and associated with the second user.
15 [0103] The present disclosure further discloses that the IPSMGW and the SMSC
(Front-End) may be integrated to optimise the IPSMGW messaging service.
[0104] The present disclosure further discloses that the method further comprises
receiving at the one or more first IPSMGW, an acknowledgement based on
20 delivering the SMS message from the first user to the second user. The
acknowledgement may be a message or an indication showing that the SMS message has been successfully delivered.
[0105] Thereafter, at step [418], the method [400] is terminated. 25
[0106] Referring to FIG. 5, an exemplary call flow diagram displaying a method [500] for optimising an IP short message gateway (IPSMGW) messaging service, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method [500] is performed by the system [300]. Further,
32

in an implementation, the system [300] may be present in a server device to implement the features of the present disclosure. The IPSMGW messaging service is a service which facilitates the exchange of short text messages (SMS) over the Internet Protocol networks. 5
[0107] Initially, at step 1, the method [500] comprises receiving, by a transceiver unit [302] from a first user [502] associated with a first network, a short message service (SMS) request comprising one or more SMS request parameters. The first user [502] may be a user device or a subscriber who is sending a message to a
10 second user [504] which may be another user device or another subscriber or a
network entity. The first network may refer to a telecom network or communication network including network entities between the communication channel of the first user [502] and the second user [504]. The SMS request may be a request for sending a message to the second user [504]. The one or more SMS request parameters, such
15 as an action parameter, a username parameter, a password parameter, and an SMS
originator parameter, are associated with the SMS request. Further, the one or more SMS request parameters may have a predefined possible value in a predefined manner based on the SMS request, such as the action parameter having the predefined possible value, i.e., a send message value, and the username parameter
20 having the predefined value, which is a string value having a maximum length of
16 characters.
[0108] The present disclosure further discloses that messages can be marked as
spam depending on the message signature, total messages sent within a
25 configurable duration, blocked keywords, blacklisting, etc. The present disclosure
supports dynamic filtering of messages based on regulatory guidelines and messages sent by subscribers not registered as telemarketers etc.
[0109] Next, at step 2, the method [500] comprises initiating, by a processing unit
30 [304] from one or more first IPSMGW [506] associated with the first user [502], a
mobile number portability (MNP) request associated with the second user [504].
33

The one or more first IPSMGW [506] may refer to the IPSMGW associated with
the first user [502] and/or the first network where the first user [502] may be
connected with the one or more first IPSMGW [506]. The second user [504] may
refer to the service provider or the operator associated with the first user [502]. The
5 MNP request is sent to an MNP server/database [130], to check the operator/domain
of Party B (SMS receiving entity) and to determine whether the Party B has ported the mobile number. The MNP server upon receiving the MNP query, looks up Party B using B’s MSISDN (phone number) in its database, and return LRN to the IPSMGW.
10
[0110] Then, at step 3, the method [500] comprises initiating, by the processing unit [304] to a Diameter Routing Agent (DRA) [132] associated with the first user [502], a diameter request [124], wherein the diameter request [124] is at least a charge request associated with the SMS request based on at least the MNP request.
15 The DRA may be a network element responsible for facilitating the routing and
management of diameter protocol messages within a in a network such as the 3G or the 4G (LTE) network, thereby ensuring that the messages are routed among the correct elements in a network. The diameter protocol messages may be used for implementing one of: an authentication, an authorisation, and an accounting
20 function in the network. The diameter request [124] may be a request containing
the information and attributes related to authentication, authorisation, and accounting as part of the diameter protocol. The charge request may be the request comprising charge details such as billing charge or a fee, associated with the SMS request and the MNP request. The charge details may be the charges such as billing
25 charges or fees, associated with providing the services for SMS and MNP by the
service provider. The DRA [132] can route the diameter request [124] to the OCS [134] for the charge request. The OCS [134] based on the diameter request [124] and the charge request can then determine the charges and billing information for the user based on the services used by the user. The charges applicable for SMS and
30 MNP may also be provided by the OCS [134] based on the DRA [132]. Further, the
OCS [134] also verifies the subscription of the user, if it allows sending SMS or
34

additional charges are required to be applied and then authorizes the delivery of the SMS based on the account balance or credit limits of the user. The diameter messages carry routing information in order to ensure delivery of the messages.
[0111] At step 4, the method [500] comprises initiating, by the processing unit [304] from the one or more first IPSMGW [506] associated with the first user [502] to at least one second IPSMGW [508] associated with a second user [504], a Send Routing Information (SRI) request based on at least a diameter response of the diameter request [124]. The at least one second IPSMGW [508] may be the IPSMGW at which the second user [504] may be connected with the at least second IPSMGW [508]. The SRI request may be a type of diameter message used within the diameter protocol request for receiving routing information of the user. The diameter response is the response to the diameter request [124]. The diameter response may contain the information and attributes related to authentication, authorisation, and accounting as part of the diameter protocol. The diameter response may also be a response received from the OCS [134] which indicates whether the charge request was successful or not successful due to a reason. The reason may be due to unsubscribed service or may also be due to insufficient balance. The response may also indicate successful charging based on the DRA [132].
[0112] At step 5, the method [500] comprises receiving, by the processing unit [304] at the one or more first IPSMGW [506], a routing information based on an SRI response of the SRI request. The routing information may be the information relating to the routing of the messages such as a user profile, a subscription details, a service restriction and an authentication parameter from a home subscriber server (HSS) and/or a subscriber profile repository associated with the network. The SRI response is the response to the SRI request initiated from the one or more first IPSMGW [506]. The SRI response is the type of diameter message used within the

diameter protocol and comprises information for receiving routing information of the user.
[0113] At step 6, the method [500] comprises initiating, by the processing unit [304] from the one or more first IPSMGW [506] via a target protocol associated with the first network, a mobile terminated (MT) request associated with the SMS request based on at least the routing information. The MT request refers to a message sent from a mobile SMS provider system to a subscriber’s mobile phone i.e., the message is terminated at the mobile phone of the subscriber’s mobile phone.
[0114] The target protocol is at least one of a Session Initiation Protocol (SIP) or a Mobile Application Part (MAP).
[0115] The present disclosure provides that the IPSMGW [102] is also responsible for performing the functions of a Short Message Service Centre (SMSC). The SMSC is responsible for handling and routing messages such as short message services over the 2G/3G networks. Therefore, the present disclosure provides a solution that provides that the IPSMGW [102] and the SMSC are integrated and supports the functionalities of both the SIP and the MAP. The integration of the IPSMGW and the SMSC as disclosed in the present disclosure helps in balancing the load between the SIP and the MAP by initiating the MT request via the target protocol. The integration of IPSMGW [102] with the SMSC also helps in supporting the short message service in 2G/3G networks via the MAP. The integration of the IPSMGW [102] with the SMSC also helps in cases where the IPSMGW [102] is to be used for signalling IP messages over the SIP. Additionally, to reduce the load of IPSMGW [102] for sending the SMS using the SIP, some of the SMS(s) are sent over the MAP via the integrated SMSC of the IPSMGW [102]. This helps in optimizing the message service of the IPSMGW [102]. The selection of target domain is based on the operating entity or a network entity or a service provider associated with the messaging service. In case, the operating entity of the

message receiver is same as the operating entity of a sender of the SMS, then the target protocol may be the SIP. However, in case the operating entity of the receiver of the message is different i.e. not same, then in that case the target protocol may be the MAP. Hence, for initiating the MT request via the target protocol the operating entity is required to be analysed. For checking whether the operating entity is same or different, the MNP request sent to the MNP server/ database [130] is analysed for determination of the operator/domain of the mobile number. The analysis of the LRN helps in determination of the operating entity.
[0116] At step 7, the method [500] comprises delivering, by the processing unit [304] from the first user [502] to the second user [504], an SMS message associated with the SMS request based on initiating the mobile terminated (MT) request from the one or more first IPSMGW [506] via the target protocol. The SMS message may be the message which the first user [502] is trying to send to the second user [504].
[0117] The present disclosure further discloses that the method [500] further comprises validating, by a validation unit [306], at least one of an SMS service validity associated with the first user [502] and one or more SMS request parameters validity based on the SMS request. The SMS service validity may refer to the validity of the SMS services for the first user [502] and the second user [504], which may also check for the validity of the mobile numbers associated with each of the first user [502] and the second user [504]. The validity of the SMS services may be a check performed by the validation unit [306] to validate that the users are allowed to use the SMS services. The one or more SMS request parameters validity may refer to the validity of the SMS request based on certain SMS request parameters.
[0118] The SMS service validity associated with the first user [502] is determined based on a prestored service data associated with the first user [502], and wherein the one or more SMS request parameters validity based on the SMS request is determined based on at least the prestored service data and a predefined set of SMS

service rules associated with at least the first network. The SMS service validity is determined based on the prestored service data, wherein the prestored service data may refer to a Home Location Register (HLR) which stores the information related the subscribers i.e., the first user [502] and the second user [504]. The predefined set of SMS service rules may refer to a SMS service rules which may be preset based on the needs and requirements of the service provider or operators.
[0119] The present disclosure further discloses that the method [500] further comprises transmitting, by the transceiver unit [302] to the one or more first IP Short Message Gateway (IPSMGW) [506] associated with the first user [502], the SMS request based on at least one of a positive SMS service validity associated with the SMS service validity and a positive SMS request parameters validity associated with the one or more SMS request parameters validity. The positive SMS service validity may refer to a positive response of the validation of the SMS service validity indicating a success, i.e., the SMS service is valid for the particular user. The positive SMS service validity may also refer to the positive response of the validation of the one or more SMS request parameters that indicates a success based on the predefined set of SMS service rules, i.e., the SMS request is valid.
[0120] The MNP request associated with the second user [504] is based on at least one of the positive SMS service validity and the positive SMS request parameters validity, wherein the MNP request is at least an operator detail request associated with the second user [504], and a Location Routing Number (LRN) request associated with the second user [504]. The operator details request may be the request or a query which is made for retrieving the information associated with the network operator or the network service provider of the second user [504]. The LRN request may refer to a request seeking the LRN. The LRN may refer to a response to the LRN request and may comprise of a ten-digit number used for routing calls and messages used for number portability feature and identifies the new location of a ported subscriber.

[0121] The present disclosure further discloses that the method [500] further comprises receiving, at the one or more first IPSMGW [506] from a Short Message Service Centre SMSC (Front-End), the routing information based on the SRI response, wherein the routing information comprises at least one target first IPSMGW from the one or more first IPSMGW [506]. The SMSC (Front-End) may refer to the user interface or application which allows administrators or the network operators to interact with a SMSC system. Further, the SMSC system facilitates configuration, managing, and monitoring of the SMS messaging services that are provided by the SMSC. The SMSC is a core component of mobile network which is responsible for facilitation of sending, receiving, and routing of the SMS messages. The target IPSMGW may be the terminating IPSMGW at which the SMS message is received, and associated with second user [504].
[0122] The present disclosure further discloses that the IPSMGW and the SMSC (Front-End) may be integrated to optimise the IPSMGW messaging service.
[0123] The present disclosure further discloses that the method further comprises receiving at the one or more first IPSMGW [506], an acknowledgement based on delivering the SMS message from the first user [502] to the second user [504]. The acknowledgement may be a message or an indication showing that the SMS message has been successfully delivered.
[0124] Thereafter, the method [500] is terminated.
[0125] The present disclosure further discloses a non-transitory computer readable storage medium storing one or more instructions for optimising an IP short message gateway (IPSMGW) messaging service, the one or more instructions include executable code which, when executed by one or more units of a system, causes the one or more units to perform certain functions. The instructions when executed causes a transceiver unit [302] of the system [300] to receive, from a first user

associated with a first network to a second user, a short message service (SMS) request comprising one or more SMS request parameters. The instructions when executed further causes a processing unit [304] of the system [300] to initiate, from the one or more first IPSMGW associated with the first user, a mobile number portability (MNP) request associated with the second user. The instructions when executed further causes the processing unit [304] of the system [300] to initiate, to a Diameter Routing Agent (DRA) associated with the first user, a diameter request [124], wherein the diameter request [124] is at least a charge request associated with the SMS request based on at least the MNP request. The instructions when executed further causes the processing unit [304] of the system [300] to initiate, from the one or more first IPSMGW associated with the first user to at least one second IPSMGW associated with the a second user, a Send Routing Information (SRI) request based on at least the diameter request [124]. The processing unit [304] of the system [300] to receive, at the one or more first IPSMGW, a routing information based on the SRI response; the processing unit [304] of the system [300] to initiate, from the one or more first IPSMGW via a target protocol associated with the first network, a mobile terminated (MT) request associated with the SMS request based on at least the routing information; the processing unit [304] of the system [300] to deliver, from the first user to the second user, an SMS message associated with the SMS request based on initiating the mobile terminated (MT) request from the one or more first IPSMGW via the target protocol.
[0126] As is evident from the above, the present disclosure provides a technically advanced solution for optimising an IP short message gateway (IPSMGW) messaging service. The present solution allows an improvement in the SMS Delivery and provides an optimal solution for the SMS delivery, efficient management of the overall traffic, time-efficient delivery of SMS, reduced failure of the delivery of SMS. The present disclosure enables formation of a balance of the load between SIP and MAP. The present disclosure provides information to the operators that have not migrated their network to LTE, or operators that use 2G/3G roaming partners to complete their network coverage, and to support subscribers

with devices that do not yet support LTE IMS and VoLTE capability. Further, the present disclosure enables integration of IPSMGW with SMSC and helps in supporting legacy 2G/3G networks (MAP), where IPSMGW is the evolution of the SMSC, to signal IP messages over SIP. Additionally, the present disclosure further reduces load of IPSMGW for sending SMS such as by using SIP and some of the SMSs are sent over MAP via integrated SMSC optimizing IPSMGW.
[0127] While considerable emphasis has been placed herein on the disclosed implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.
[0128] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.

We Claim:
1. A method for optimising an IP short message gateway (IPSMGW)
messaging service, the method comprising:
- receiving, by a transceiver unit [302] from a first user associated with a first network, a short message service (SMS) request comprising one or more SMS request parameters;
- initiating, by a processing unit [304] from one or more first IPSMGW associated with the first user, a mobile number portability (MNP) request associated with a second user;
- initiating, by the processing unit [304] to a Diameter Routing Agent (DRA) associated with the first user, a diameter request [124], wherein the diameter request [124] is at least a charge request associated with the SMS request based on at least the MNP request;
- initiating, by the processing unit [304] from the one or more first IPSMGW associated with the first user to at least one second IPSMGW associated with a second user, a Send Routing Information (SRI) request based on at least a diameter response of the diameter request [124];
- receiving, by the processing unit [304] at the one or more first IPSMGW, a routing information based on an SRI response of the SRI request;
- initiating, by the processing unit [304] from the one or more first IPSMGW via a target protocol associated with the first network, a mobile terminated (MT) request associated with the SMS request based on at least the routing information; and
- delivering, by the processing unit [304] from the first user to the second user, an SMS message associated with the SMS request based on initiating the mobile terminated (MT) request from the one or more first IPSMGW via the target protocol.
2. The method as claimed in claim 1, further comprises validating, by a
validation unit [306], at least one of an SMS service validity associated with

the first user and one or more SMS request parameters validity based on the SMS request.
3. The method as claimed in claim 2, further comprises transmitting, by the transceiver unit [302] to the one or more first IP Short Message Gateway (IPSMGW) associated with the first user, the SMS request based on at least one of a positive SMS service validity associated with the SMS service validity and a positive SMS request parameters validity associated with the one or more SMS request parameters validity.
4. The method as claimed in claim 3, wherein the MNP request associated with the second user is based on at least one of the positive SMS service validity and the positive SMS request parameters validity, wherein the MNP request is at least an operator detail request associated with the second user, and a Location Routing Number (LRN) request associated with the second user.
5. The method as claimed in claim 1, further comprises receiving, at the one or more first IPSMGW from a Short Message Service Centre SMSC (Front-End), the routing information based on the SRI response, wherein the routing information comprises at least one target first IPSMGW from the one or more first IPSMGW.
6. The method as claimed in claim 5, wherein the IPSMGW and the SMSC (Front-End) are integrated to optimise the IPSMGW messaging service.
7. The method as claimed in claim 1, wherein the target protocol is at least one of a Session Initiation Protocol (SIP) or a Mobile Application Part (MAP).
8. The method as claimed in claim 1, further comprises receiving at the one or more first IPSMGW, an acknowledgement based on delivering the SMS message from the first user to the second user.

9. The method as claimed in claim 3, wherein the SMS service validity associated with the first user is determined based on a prestored service data associated with the first user, and wherein the one or more SMS request parameters validity based on the SMS request is determined based on at least the prestored service data and a predefined set of SMS service rules associated with at least the first network.
10. A system [300] for optimising an IP short message gateway (IPSMGW) messaging service, the system [300] comprises:

- a transceiver unit [302], configured to receive, from a first user associated with a first network, a short message service (SMS) request comprising one or more SMS request parameters; and
- a processing unit [304] connected at least to the transceiver unit [302], the processing unit [304] is configured to:

• initiate, from one or more first IPSMGW associated with the first user, a mobile number portability (MNP) request associated with a second user,
• initiate, to a Diameter Routing Agent (DRA) associated with the first user, a diameter request [124], wherein the diameter request [124] is at least a charge request associated with the SMS request based on at least the MNP request,
• initiate, from the one or more first IPSMGW associated with the first user to at least one second IPSMGW associated with a second user, a Send Routing Information (SRI) request based on at least the diameter request [124],
• receive, at the one or more first IPSMGW, a routing information based on an SRI response,
• initiate, from the one or more first IPSMGW via a target protocol associated with the first network, a mobile terminated (MT)

request associated with the SMS request based on at least the routing information, and • deliver, from the first user to the second user, an SMS message associated with the SMS request based on initiating the mobile terminated (MT) request from the one or more first IPSMGW via the target protocol.
11. The system [300] as claimed in claim 10, wherein the system [300] further comprises a validation unit [306] connected at least to the processing unit [304], the validation unit [306] is configured to validate at least one of a SMS service validity associated with the first user and one or more SMS request parameters validity based on the SMS request.
12. The system [300] as claimed in claim 11, wherein the transceiver unit [302] is further configured to transmit, to the one or more first IPSMGW associated with the first user, the SMS request based on at least one of a positive SMS service validity associated with the SMS service validity and a positive SMS request parameters validity associated with the one or more SMS request parameters validity.
13. The system [300] as claimed in claim 12, wherein the MNP request associated with the second user is based on at least one of the positive SMS service validity and the positive SMS request parameters validity, wherein the MNP request is at least an operator detail request associated with the second user, and a Location Routing Number (LRN) request associated with the second user.
14. The system [300] as claimed in claim 10, wherein the transceiver unit [302] is further configured to receive, at the one or more first IPSMGW from a Short Message Service Centre SMSC (Front-End), the routing information

based on the SRI response, wherein the routing information comprises at least one target first IPSMGW from the one or more first IPSMGW.
15. The system [300] as claimed in claim 14, wherein the IPSMGW and SMSC (Front-End) are integrated to optimise the IPSMGW messaging service.
16. The system [300] as claimed in claim 10, wherein the target protocol is at least one of a Session Initiation Protocol (SIP) or a Mobile Application Part (MAP).
17. The system [300] as claimed in claim 10, wherein the transceiver unit [302] is further configured to receive, at the one or more first IPSMGW, an acknowledgement based on delivering the SMS message from the first user to the second user.
18. The system [300] as claimed in claim 12, wherein the SMS service validity associated with the first user is determined based on a prestored service data associated with the first user, and wherein the one or more SMS request parameters validity based on the SMS request is determined based on at least the prestored service data and a predefined set of SMS service rules associated with at least the first network.