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 TRANSMITTING A MESSAGE TO A TARGET USER”
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 TRANSMITTING A MESSAGE TO A
TARGET USER
FIELD OF THE DISCLOSURE
5
[0001] The present disclosure relates generally to the field of communication network. More particularly, the present disclosure relates to methods and systems for transmitting a message to a target user.
10 BACKGROUND
[0002] The following description of 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
15 disclosure. However, it should be appreciated that this section be used only to
enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
[0003] Wireless communication technology has rapidly evolved over the past few
20 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. Third Generation
25 (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
30 connect multiple devices simultaneously. With each generation, wireless
2

communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
[0004] Nowadays, telecom operators are working hard to enhance the network
5 capabilities and to efficiently handle the messaging or Short Message Services
(SMS) services in Long Term Evolution (LTE) and 5G networks.
[0005] In general, the major task of routing the messages associated with applications (such as domain based, bank services and the like) to peer or peer to
10 applications is performed via a Mobile Application Part (MAP) protocol in a
communication network. However, due to the increase in the number of mobile users and traffic, routing the messages on a single protocol leads to an inefficient handling of traffic which results in delay in transmission of message or failure of the delivery of messages to the end users. In addition, it also affects the privacy and
15 security involved in the transmission of messages or SMS messages from
application to peers or vice versa.
[0006] Hence, in view of these and other existing limitations, there arises an
imperative need to provide an efficient solution to overcome the above-mentioned
20 limitations and to provide a method and system for transmitting a message to a
target user and to allow efficient and quick handling of application-based messages related traffic in Radio Access Network such as 4G or 5G network.
SUMMARY OF THE DISCLOSURE
25
[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.
30
3

[0008] An aspect of the present disclosure may relate to a method for transmitting
a message to a target user. The method comprises receiving, by a transceiver unit at
an A2P-IP short message gateway (A2P-IPSMGW), a message request associated
with a target user. The method further comprises transmitting, by the transceiver
5 unit from the A2P-IPSMGW to a mobile number portability server (MNP server),
a mobile number portability request (MNP request) based on the message request. The method further comprises receiving, by the transceiver unit at the A2P-IPSMGW from the MNP server, a mobile number portability response (MNP response) comprising at least a target domain based on the MNP request. The
10 method further comprises determining, by a determination unit at the A2P-
IPSMGW, a domain status based on at least the target domain and a set of pre-stored domains, wherein the domain status is at least one of a positive domain status and a negative domain status. The method further comprises transmitting, by the transceiver unit from the A2P-IPSMGW, a User Data Repository (UDR) request
15 based on the positive domain status. The method further comprises receiving, by
the transceiver unit at the A2P-IPSMGW, a user data associated with the target user based on the UDR request. The method further comprises transmitting, by the transceiver unit from the A2P-IPSMGW via a Session Initiation Protocol (SIP), the message to the target user associated with the message request based on the user
20 data and the target domain.
[0009] In an exemplary aspect of the present disclosure, the message request associated with the target user is received at the A2P-IPSMGW via an External Short Messaging Entity (ESME).
25
[0010] In an exemplary aspect of the present disclosure, the method further comprises validating, by a validation unit, at least a mobile number associated with the target user based on one or more validation techniques, wherein the mobile number associated with the target user is extracted from the message request.
30
4

[0011] In an exemplary aspect of the present disclosure, the positive domain status is determined in an event the target domain is a successful match with at least one of a pre-stored domain from the set of pre-stored domains.
5 [0012] In an exemplary aspect of the present disclosure, the negative domain status
is determined in an event the target domain is an unsuccessful match with each of the pre-stored domain from the set of pre-stored domains.
[0013] Another aspect of the present disclosure may relate to a system for
10 transmitting a message to a target user. The system comprises at least a transceiver
unit, and a determination unit connected to each other. The transceiver unit is configured to receive, at an A2P-IP short message gateway (A2P-IPSMGW), a message request associated with the target user. The transceiver unit is further configured to transmit, from the A2P-IPSMGW to a mobile number portability
15 server (MNP server), a mobile number portability request (MNP request) based on
the message request. The transceiver unit is further configured to receive, at the A2P-IPSMGW from the MNP server, a mobile number portability response (MNP response) comprising at least a target domain based on the MNP request. The determination unit is further configured to determine, at the A2P-IPSMGW, a
20 domain status based on at least the target domain and a set of pre-stored domains,
wherein the domain status is at least one of a positive domain status and a negative domain status. The transceiver unit is further configured to transmit, from the A2P-IPSMGW, a User Data Repository (UDR) request based on the positive domain status. The transceiver unit is further configured to receive, at the A2P-IPSMGW, a
25 user data associated with the target user based on the UDR request. The transceiver
unit is further configured to transmit, from the A2P-IPSMGW via a Session Initiation Protocol (SIP), the message to the target user associated with the message request based on the user data and the target domain.
30 [0014] Yet another aspect of the present disclosure may relate to a non-transitory
computer readable storage medium storing instructions for transmitting a message
5

to a target user , the non-transitory computer readable storage medium comprising
executable code which, when executed by one or more units of a system, causes the
one or more units of the system to: receive, by a transceiver unit of the system at an
A2P-IP short message gateway (A2P-IPSMGW), a message request associated with
5 the target user; transmit, by the transceiver unit of the system from the A2P-
IPSMGW to a mobile number portability server (MNP server), a mobile number portability request (MNP request) based on the message request; receive, by the transceiver unit of the system at the A2P-IPSMGW from the MNP server, a mobile number portability response (MNP response) comprising at least a target domain
10 based on the MNP request; determine, by a determination unit of the system at the
A2P-IPSMGW, a domain status based on at least the target domain and a set of pre-stored domains, wherein the domain status is at least one of a positive domain status and a negative domain status; transmit, by the transceiver unit of the system from the A2P-IPSMGW, a User Data Repository (UDR) request based on the positive
15 domain status; receive, at the A2P-IPSMGW, a user data associated with the target
user based on the UDR request; and transmit, by the transceiver unit of the system from the A2P-IPSMGW via a Session Initiation Protocol (SIP), the message to the target user associated with the message request based on the user data and the target domain.
20
OBJECTS OF THE DISCLOSURE
[0015] Some of the objects of the present disclosure, which at least one
25 implementation disclosed herein satisfies are listed herein below.
[0016] It is an object of the present disclosure to provide a system and a method for transmitting a message to a target user.
30 [0017] It is another object of the present disclosure to provide a solution for
receiving a message request associated with the target user, transmitting a mobile
6

number portability request (MNP request) based on the message request, and receiving at the A2P-IPSMGW from the MNP server, a mobile number portability response (MNP response) comprising at least a target domain based on the MNP request. 5
[0018] It is another object of the present disclosure to provide a solution for determining a domain status based on the target domain and a set of pre-stored domains, and transmitting a User Data Repository (UDR) request based on the positive domain status.
10
[0019] It is another object of the present disclosure to provide a solution for receiving a user data associated with the target user based on the UDR request and transmitting the message to the target user associated with the message request based on the user data and the target domain.
15
[0020] It is another object of the present disclosure to provide a solution for efficient handling of application-based traffic and domain-based traffic.
[0021] It is another object of the present disclosure to provide a system and a
20 method for efficient handling of domain-based traffic or application-based traffic in
a communication network.
BRIEF DESCRIPTION OF DRAWINGS
25 [0022] The accompanying drawings, which are incorporated herein, and constitute
a part of this disclosure, illustrate exemplary implementations 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
30 the present disclosure. Some drawings may indicate the components using block
diagrams and may not represent the internal circuitry of each component. It will be
7

appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
5 [0023] FIG. 1 illustrates an exemplary block diagram representation of 5th
generation core (5GC) network architecture.
[0024] FIG. 1A illustrates an exemplary block diagram representation of an IPSMGW A2P architecture. 10
[0025] FIG.2 illustrates an exemplary block diagram of a system [200] for transmitting a message to a target user, in accordance with exemplary implementations of the present disclosure.
15 [0026] FIG. 3 illustrates an exemplary method [300] flow diagram illustrating a
process for transmitting a message to a target user, in accordance with exemplary implementations of the present disclosure.
[0027] FIG. 3A illustrates an exemplary call flow diagram [300A] illustrating a
20 process for transmitting a message to a target user, in accordance with exemplary
implementations of the present disclosure.
[0028] FIG. 4 illustrates a non-limiting exemplary scenario signal flow diagram
[400] illustrating routing of messages based on domain, in accordance with
25 exemplary implementations of the present disclosure.
[0029] FIG.5 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. 30
8

[0030] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION
5
[0031] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of implementations of the present disclosure. It will be apparent, however, that implementations of the present disclosure may be practiced without these specific
10 details. Several features described hereafter can each be used independently of one
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. Some of the problems discussed above might not be fully addressed by any of the features described herein. Example implementations
15 of the present disclosure are described below, as illustrated in various drawings in
which like reference numerals refer to the same parts throughout the different drawings.
[0032] The ensuing description provides exemplary implementations only, and is
20 not intended to limit the scope, applicability, or configuration of the disclosure.
Rather, the ensuing description of the exemplary implementations will provide
those skilled in the art with an enabling description for implementing an exemplary
implementation. It should be understood that various changes may be made in the
function and arrangement of elements without departing from the spirit and scope
25 of the disclosure as set forth.
[0033] It should be noted that the terms "mobile device", "user equipment", "user
device", “communication device”, “device” and similar terms are used
interchangeably for the purpose of describing the disclosure. These terms are not
30 intended to limit the scope of the disclosure or imply any specific functionality or
limitations on the described implementations. The use of these terms is solely for
9

convenience and clarity of description. The disclosure is not limited to any particular type of device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the disclosure as defined herein. 5
[0034] Specific details are given in the following description to provide a thorough
understanding of the implementations. However, it will be understood by one of
ordinary skill in the art that the implementations may be practiced without these
specific details. For example, circuits, systems, networks, processes, and other
10 components may be shown as components in block diagram form in order not to
obscure the implementations in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the implementations.
15 [0035] Also, it is noted that individual implementations 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 can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged.
20 A process is terminated when its operations are completed but could have additional
steps not included in a figure.
[0036] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the
25 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 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
30 “includes,” “has,” “contains,” and other similar words are used in either the detailed
description or the claims, such terms are intended to be inclusive—in a manner
10

similar to the term “comprising” as an open transition word—without precluding any additional or other elements.
[0037] As used herein, an “electronic device”, or “portable electronic device”, or
5 “user device” or “communication device” or “user equipment” or “device” refers
to any electrical, electronic, electromechanical and computing device. The user device is capable of receiving and/or transmitting one or parameters, performing function/s, communicating with other user devices and transmitting data to the other user devices. The user equipment may have a processor, a display, a memory,
10 a battery and an input-means such as a hard keypad and/or a soft keypad. The user
equipment may be capable of operating on any radio access technology including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For instance, the user equipment may include, but not limited to, a mobile phone, smartphone,
15 virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-
purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.
20 [0038] Further, the user device may also comprise a “processor” or a “processing
unit”, wherein processor refers to any logic circuitry for processing instructions. The processor may be 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
25 controller, a microcontroller, Application Specific 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 is a hardware processor.
30
11

[0039] As portable electronic devices and wireless technologies continue to
improve and grow in popularity, the advancing wireless technologies for data
transfer are also expected to evolve and replace the older generations of
technologies. In the field of wireless data communications, the dynamic
5 advancement of various generations of cellular technology are also seen. The
development, in this respect, has been incremental in the order of second generation (2G), third generation (3G), fourth generation (4G), and now fifth generation (5G), and more such generations are expected to continue in the forthcoming time.
10 [0040] Radio Access Technology (RAT) refers to the technology used by mobile
devices/ user equipment (UE) to connect to a cellular network. It refers to the specific protocol and standards that govern the way devices communicate with base stations, which are responsible for providing the wireless connection. Further, each RAT has its own set of protocols and standards for communication, which define
15 the frequency bands, modulation techniques, and other parameters used for
transmitting and receiving data. Examples of RATs include GSM (Global System for Mobile Communications), CDMA (Code Division Multiple Access), UMTS (Universal Mobile Telecommunications System), LTE (Long-Term Evolution), and 5G. The choice of RAT depends on a variety of factors, including the network
20 infrastructure, the available spectrum, and the mobile device's/device's capabilities.
Mobile devices often support multiple RATs, allowing them to connect to different types of networks and provide optimal performance based on the available network resources.
25 [0041] As used herein, Radio Access Network (RAN) node includes, but not
limited to, gNodeB or gNB, macro, indoor small cell (IDSC), outdoor small cell (ODSC), mm wave and the like.
[0042] As discussed in the background section, there is a problem in handling the
30 traffic of messages transmitted or received at the network level. A single protocol
i.e., MAP is used for the major and overall routing of the application messages
12

(messages from application to peer or messages from peer to application) to the end terminal. For instance, conventionally, the MAP is used for handling the message traffic associated with the local subscriber or operator as well as for handling the message traffic associated with various domains and applications. 5
[0043] The present disclosure aims to overcome the problem associated with handling of application based or domain-based traffic at the network by routing the domain-based traffic using SIP protocol. The present disclosure routes the traffic via two different protocols based on the domain of the messages or data. 10
[0044] Hereinafter, exemplary implementations of the present disclosure will be described with reference to the accompanying drawings.
[0045] FIG. 1 illustrates an exemplary block diagram representation of 5th
15 generation core (5GC) network architecture, in accordance with exemplary
implementation of the present disclosure. As shown in FIG. 1, the 5GC network
architecture [100] includes a user equipment (UE) [102], a radio access network
(RAN) [104], an access and mobility management function (AMF) [106], a Session
Management Function (SMF) [108], a Service Communication Proxy (SCP) [110],
20 an Authentication Server Function (AUSF) [112], a Network Slice Specific
Authentication and Authorization Function (NSSAAF) [114], a Network Slice
Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a
Network Repository Function (NRF) [120], a Policy Control Function (PCF) [122],
a Unified Data Management (UDM) [124], an application function (AF) [126], a
25 User Plane Function (UPF) [128], a data network (DN) [130], wherein all the
components are assumed to be connected to each other in a manner as obvious to
the person skilled in the art for implementing features of the present disclosure.
[0046] The User Equipment (UE) [102] interfaces with the network via the Radio
30 Access Network (RAN) [104]; the Access and Mobility Management Function
(AMF) [106] manages connectivity and mobility, while the Session Management
13

Function (SMF) [108] administers session control; the service communication
proxy (SCP) [110] routes and manages communication between network services,
enhancing efficiency and security, and the Authentication Server Function (AUSF)
[112] handles user authentication; the Network Slice Specific Authentication and
5 Authorization Function (NSSAAF) [114] for integrating the 5G core network with
existing 4G LTE networks i.e., to enable Non-Standalone (NSA) 5G deployments, the Network Slice Selection Function (NSSF) [116], Network Exposure Function (NEF) [118], and Network Repository Function (NRF) [120] enable network customization, secure interfacing with external applications, and maintain network
10 function registries respectively; the Policy Control Function (PCF) [122] develops
operational policies, and the Unified Data Management (UDM) [124] manages subscriber data; the Application Function (AF) [126] enables application interaction, the User Plane Function (UPF) [128] processes and forwards user data, and the Data Network (DN) [130] connects to external internet resources;
15 collectively, these components are designed to enhance mobile broadband, ensure
low-latency communication, and support massive machine-type communication, solidifying the 5GC as the infrastructure for next-generation mobile networks.
[0047] Radio Access Network (RAN) [104] is the part of a mobile
20 telecommunications system that connects user equipment (UE) [102] to the core
network (CN) and provides access to different types of networks (e.g., 5G network). It consists of radio base stations and the radio access technologies that enable wireless communication.
25 [0048] Access and Mobility Management Function (AMF) [106] is a 5G core
network function responsible for managing access and mobility aspects, such as UE registration, connection, and reachability. It also handles mobility management procedures like handovers and paging.
30 [0049] Session Management Function (SMF) [108] is a 5G core network function
responsible for managing session-related aspects, such as establishing, modifying,
14

and releasing sessions. It coordinates with the User Plane Function (UPF) for data forwarding and handles IP address allocation and QoS enforcement.
[0050] Service Communication Proxy (SCP) [110] is a network function in the 5G
5 core network that facilitates communication between other network functions by
providing a secure and efficient messaging service. It acts as a mediator for service-based interfaces.
[0051] Authentication Server Function (AUSF) [112] is a network function in the
10 5G core responsible for authenticating UEs during registration and providing
security services. It generates and verifies authentication vectors and tokens.
[0052] Network Slice Specific Authentication and Authorization Function
(NSSAAF) [114] is a network function that provides authentication and
15 authorization services specific to network slices. It ensures that UEs can access only
the slices for which they are authorized.
[0053] Network Slice Selection Function (NSSF) [116] is a network function
responsible for selecting the appropriate network slice for a UE based on factors
20 such as subscription, requested services, and network policies.
[0054] Network Exposure Function (NEF) [118] is a network function that exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications. 25
[0055] Network Repository Function (NRF) [120] is a network function that acts as a central repository for information about available network functions and services. It facilitates the discovery and dynamic registration of network functions.
15

[0056] Policy Control Function (PCF) [122] is a network function responsible for policy control decisions, such as QoS, charging, and access control, based on subscriber information and network policies.
5 [0057] Unified Data Management (UDM) [124] is a network function that
centralizes the management of subscriber data, including authentication, authorization, and subscription information.
[0058] Application Function (AF) [126] is a network function that represents
10 external applications interfacing with the 5G core network to access network
capabilities and services.
[0059] User Plane Function (UPF) [128] is a network function responsible for
handling user data traffic, including packet routing, forwarding, and QoS
15 enforcement.
[0060] Data Network (DN) [130] refers to a network that provides data services to user equipment (UE) in a telecommunications system. The data services may include but are not limited to Internet services, private data network related services.
20
[0061] Short Message Service Function (SMSF) [132] refers to a network function that supports the transfer of Short Message Service (SMS) over a Non-Access Stratum (NAS). Further, SMSF [132] may be connected to the Short Message Service- Gateway Mobile Switching Centre - Internet Protocol Short Message
25 Gateway (SMS-GMSC/IPSMGW) router via one or more standardized interfaces.
[0062] Referring to FIG. 1A, an exemplary block diagram representation of an
IPSMGW A2P architecture [100A], in accordance with exemplary implementation
of the present disclosure. As shown in FIG. 1A, the IPSMGW A2P architecture
30 [100A] includes a signal transfer point (STP) [102A], an element management
system (EMS) [104A], a diameter routing agent (DRA) [106A], a home subscriber
16

server (HSS) [108A], a database A, [110A], a database B [112A], a mobile number portability database (MNP DB) [114A], and an internal external short message entity (Internal ESME) [116A].
5 [0063] The IPSMGW A2P [118A] is an IPSMGW specially for messaging services
from an application to a peer or peer to application such as the target user [302A].
[0064] The Signal Transfer Point (STP) [102A] is a node in an SS7 network that routes signalling messages based on their destination point code in the SS7 network.
10 The STP [102A] is connected with the IPSMGW A2P [118A] via a SS7 Sigtran
protocol. The SIGTRAN is a protocol used for transport of signalling protocols over Internet Protocol (IP), and are an extension of the SS7 protocol family. The SS7 Sigtran supports the same application and call management paradigms as SS7 but uses an Internet Protocol (IP) transport called Stream Control Transmission
15 Protocol (SCTP).
[0065] The element management system (EMS) [104A] refers to systems and
applications for managing various network elements (NE) in the
telecommunications network. The EMS [104A] utilizes a Representational State
20 Transfer (REST) type of web services and systems for easily communicating with
each other.
[0066] The diameter routing agent (DRA) [106A] may be an element in a 3G or 4G (such as long-term evolution (LTE)) network that provides real-time routing
25 capabilities which ensures that the messages are routed among the correct elements
withing a network. The DRA [106A] utilizes a diameter SH interface for interacting with the Application server and the HSS [108A] and may communicate via diameter protocol. The HSS [108A] also communicates with the DRA [106A] via diameter SH, and the DRA [106A] communicates with the IPSMGW A2P [118A] of the
30 application using the diameter SH interface.
17

[0067] The home subscriber server (HSS) [108A] may refer to as the main subscriber database that is used within the IP Multimedia Subsystem (IMS) for providing details of the subscribers to other entities within the network.
5 [0068] The database A [110A] may refer to a data storage system that leverages a
distributed architecture for high availability and reliability. The Database A [110A] may utilize the transmission control protocol (TCP) for communication between the IPSMGW A2P [118A] and the database A [110A].
10 [0069] The database B [112A] may be an in-memory storage with NoSQL
key/value store that is used primarily as an application cache or quick-response database. The Database B [112A] may utilize the transmission control protocol (TCP) for communication between the IPSMGW A2P [118A] and the database B [110A].
15
[0070] The mobile number portability database (MNP DB) [114A] may refer to a database maintained by each Mobile Number Portability Service provider in electronic form that holds the details of all ported mobile numbers in its zone, along with the complete history of all transactions relating to the porting of such numbers.
20 The MNP DB communicates with the IPSMGW A2P [118A] via a session initiation
protocol (SIP)
[0071] The internal external short message entity (Internal ESME) [116A] is an
application within the IPSMGW A2P architecture [100A] that connects to a Short
25 Message Service Centre (SMSC) to engage in the sending or receiving of SMS
messages. The internal ESME communicates via SMPP (short message peer-to-peer protocol) that is a telecommunications industry protocol for exchanging SMS messages over the Internet.
30 [0072] Referring to Figure 2, an exemplary block diagram of a system [200] for
transmitting a message to a target user [302A] (shown in Fig. 3A), in accordance
18

with the exemplary implementations of the present disclosure. The system [200]
comprises at least one transceiver unit [202], a determination unit [204], and a
validation unit [206] connected with one or more components configured to
implement the feature of the present disclosure. Also, all of the components/ units
5 of the system [200] are assumed to be connected to each other unless otherwise
indicated below. Also, in Fig. 2 only a few units are shown, however, the system [200] may comprise multiple such units or the system [200] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system [200] may be present at a
10 network level to implement the features of the present disclosure. In an
implementation, the system [200] may reside in a server or a network entity. The message may refer to an incoming message at a network entity which may be but not limited to a request for porting a mobile number to a different service provider and an action message such as wakeup message, triggering messages, alerts, etc.
15 The target user [302A] may be but not limited to the user or subscriber which is
trying to port the mobile number. The transceiver unit [202] may be a device capable of transmission and reception of data and/or signals. The determination unit [204] may be a processor capable of determining a domain status based on processing some input data. The validation unit [206] may be a processor capable
20 of validating a mobile number based on processing some input data.
[0073] The system [200] is configured for transmitting the message to the target user [302A], with the help of the interconnection between the components/units of the system [200].
25
[0074] In order to transmit the message to the target user [302A], the transceiver unit [202] of the system [200] is configured to receive, at an Application to Peer – Internet Protocol short message gateway (A2P-IPSMGW), a message request associated with the target user [302A]. The IPSMGW may be an IP Multimedia
30 System (IMS) Application Server which handles Session Initiation Protocol (SIP)
based messaging services for IMS subscribers. The A2P IPSMGW [118A] may
19

refer to an IPSMGW specially for messaging services from an application to a peer or peer to application such as the target user [302A]. The message request may refer to a request sent by a user equipment (UE) or a subscriber related to porting of mobile number by the target user [302A]. 5
[0075] Further, the present disclosure discloses that the message request associated with the target user [302A] may also be received at the A2P-IPSMGW [118A] via an External Short Messaging Entity (ESME) [402] (shown in Fig. 4). The ESME [402] may be an external application that connects to a Short Message Service
10 Centre (SMSC) to engage in the sending or receiving of SMS messages. It may be
noted that the abovementioned example is only exemplary and in no manner should be construed to limit the scope of the present disclosure. Further, any other examples of the ESME [402] for receiving the message request at the A2P-IPSMGW [118A] may be received via a machine type communication (MTC) and
15 a mobile internet of things (mIoT) technology as well. All such examples would
also be covered within the scope of the present subject matter.
[0076] Further, the transceiver unit [202] is configured to transmit, from the A2P-IPSMGW [118A] to a mobile number portability server (MNP server) [304A], a
20 mobile number portability request (MNP request) based on the message request.
The Mobile number portability (MNP) is a service that allows the user / subscriber to change the service provider and keep the same mobile number. The MNP server [304A] is a server which is responsible for handling the MNP service. The MNP request is sent to the MNP sever to obtain a domain of receiving party for
25 transmitting the message.
[0077] Further, the transceiver unit [202] is configured to receive, at the A2P-
IPSMGW [118A] from the MNP server [304A], a mobile number portability
response (MNP response) comprising at least a target domain based on the MNP
30 request. The MNP response is a response to the request made regarding MNP. The
20

target domain may refer to the public land mobile network (PLMN), a location of operator, or a network technology of target user [302A].
[0078] Further, the determination unit [204] is configured to determine, at the A2P-
5 IPSMGW [118A], a domain status based on at least the target domain and a set of
pre-stored domains, wherein the domain status is at least one of a positive domain
status and a negative domain status. The domain status may refer to an availability
status regarding the target domain in a set of pre-stored domains. The positive
domain status refers to the positive availability of the target domain, and the
10 negative domain status refers to the non-availability of the target domain. The set
of pre-stored domains may refer to a list of pre-stored domains wherein the pre-
stored domains may contain information of the service providers.
[0079] Further, the present disclosure discloses that the positive domain status is
15 determined in an event the target domain is a successful match with at least one of
a pre-stored domain from the set of pre-stored domains. The event that the target domain is a successful match may refer to the situation where the target domain is present in the set of pre-stored domains which results in a match.
20 [0080] Further, the negative domain status is determined in an event the target
domain is an unsuccessful match with each of the pre-stored domain from the set of pre-stored domains. The event the target domain is an unsuccessful match may refer to the situation where the target domain is not present in the set of pre-stored domains.
25
[0081] Further, the transceiver unit [202] may also be configured to transmit, from the A2P-IPSMGW [118A], a User Data Request (UDR) based on the positive domain status. The UDR may be a database of clients storing information associated with customers such as services available for them, QoS parameters, etc. The UDR
30 request may be a request seeking information from the UDR sent by IPSMGW to
HSS via DRA over the diameter. The IPSMGW receives a user data response in
21

response to the UDR which contains the information of context/profile information of other party.
[0082] Further, the transceiver unit [202] may also be configured to receive, at the
5 A2P-IPSMGW [118A], a user data associated with the target user [302A] based on
the UDR request. The user data may be the information stored within the UDR related to the target user [302A].
[0083] Further, the transceiver unit [202] may also be configured to transmit, from
10 the A2P-IPSMGW [118A] via a Session Initiation Protocol (SIP), the message to
the target user [302A] associated with the message request based on the user data and the target domain. The Session Initiation Protocol (SIP) is a signalling protocol used for initiating, maintaining, and terminating communication sessions that include voice, video and messaging applications.
15
[0084] Further, in an implementation of the present solution as disclosed herein, the system [200] may further comprise the validation unit [206] configured to validate at least a mobile number associated with the target user [302A] based on one or more validation techniques, wherein the mobile number associated with the target
20 user [302A] is extracted from the message request. The Mobile Number means the
Mobile Subscriber Integrated Services Digital Network (MSISDN) mobile or cellular phone number, which is associated with a subscriber identity module (SIM) card at the time of activation. The one or more validation techniques can include anti-spam function such as checking whether the sender and originator is valid
25 (valid-sender valid-originator), checking quantity of the SMS for a duration for
checking SMS flooding, and checking service and billing information for both users i.e. the sender and the receiver of the message.
[0085] Further, in a non-limiting exemplary scenario implementation of the present
30 solution the system [200] is configured for handling of traffic and routing of traffic
based on domain, with the help of the interconnection between the
22

components/units of the system [200]. The present disclosure routes the domain specific traffic associated with one or more application over SIP protocol so that both the protocols such as MAP and short message peer-to-peer protocol (SMPP) can be used to efficiently handle the domain based and non-domain-based traffic. 5
[0086] The system [200] is configured to perform the below-mentioned steps to control domain traffic related to message services:
[0087] At first, an application to peer message is received at an A2P-IPSMGW
10 [118A].
[0088] Next, the mobile number associated with the peer (the target user [302A]) is validated.
15 [0089] Next, an MNP request is sent to the MNP (Mobile Number Portability)
server [304A] (shown in Fig. 3A] against MNP query after successful validation of the mobile number associated with the peer. The MNP request is sent to the MNP server [304A] to obtain target user [302A] domain, and then check the existence of the target domain (specified domain) (in the MNP query) in a domain map which
20 may be stored within the domain database [404], or may also be stored in the storage
unit of the A2P-IPSMGW [118A]. The domain database [404] is maintained at the network level.
[0090] Next, a request is sent to the UDR to deliver the message over the SIP
25 protocol in case the specified domain is found in the domain database [404].
[0091] Finally, the message is delivered to the receiver [406] (shown in Fig. 4) over the SIP protocol.
30 [0092] Thus, the present disclosure routes the message traffic over SIP protocol in
an event the requested domain is identified or found in the domain database. Local
23

traffic or peer to peer message traffic is sent over the MAP protocol to optimise and handle the traffic.
[0093] The storage unit and the domain database are configured to store data
5 associated with implementation of the features of the present disclosure.
[0094] Referring to FIG. 3, an exemplary method flow diagram [300], for transmitting a message to a target user [302A], in accordance with exemplary implementations of the present disclosure is shown. In an implementation the
10 method [300] is performed by the system [200]. As shown in Figure 3, the method
[300] starts at step [302]. The message may refer to an incoming message at a network entity which may be, but not limited to, a request for porting a mobile number to a different service provider and an action message such as wakeup message, triggering messages, alerts, etc. The target user [302A] may refer to the
15 user or subscriber which is trying to port the mobile number.
[0095] At step [304], the method [300] as disclosed by the present disclosure comprises receiving, by a transceiver unit [202] at an Application to Peer – Internet Protocol (A2P-IP) short message gateway (A2P-IPSMGW) [118A], a message
20 request associated with the target user [302A]. The IPSMGW may be an IP
Multimedia System (IMS) Application Server which handles Session Initiation Protocol (SIP) based messaging services for IMS subscribers. The A2P IPSMGW [118A] may refer to an IPSMGW specially for messaging services from an application to a peer or peer to application such as the target user [302A]. The
25 message request may refer to a request sent by a user equipment (UE) or a
subscriber related to the porting by the target user [302A]. The transceiver unit [202] may be a device capable of transmission and reception of data and/or signals.
[0096] Further, the present disclosure further discloses that the message request
30 associated with the target user [302A] may also be received at the A2P-IPSMGW
[118A] via an External Short Messaging Entity (ESME) [402]. The ESME [402]
24

may be an external application that connects to a Short Message Service Centre
(SMSC) to engage in the sending or receiving of SMS messages. It may be noted
that the abovementioned example is only exemplary and in no manner should be
construed to limit the scope of the present disclosure. Further, any other examples
5 of the ESME [402] for receiving the message request at the A2P-IPSMGW [118A]
may be received via a machine type communication and a mobile internet of things technology as well.
[0097] Next, at step [306], the method [300] as disclosed by the present disclosure
10 comprises transmitting, by the transceiver unit [202] from the A2P-IPSMGW
[118A] to a mobile number portability server (MNP server [304A]), a mobile
number portability request (MNP request) based on the message request. The
Mobile number portability (MNP) is a service that allows the user / subscriber to
change the service provider and keep the same mobile number. The MNP server
15 [304A] is a server which is responsible for handling the MNP service. The MNP
request is sent to the MNP sever to obtain a domain of receiving party for transmitting the message.
[0098] Next, at step [308], the method [300] as disclosed by the present disclosure
20 comprises receiving, by the transceiver unit [202] at the A2P-IPSMGW [118A]
from the MNP server [304A], a mobile number portability response (MNP
response) comprising at least a target domain based on the MNP request. The MNP
response is a response to the request made by the user/subscriber regarding MNP.
The target domain refers to the public land mobile network (PLMN), a location of
25 operator, or a network technology of target user [302A].
[0099] Next, at step [310], the method [300] as disclosed by the present disclosure
comprises determining, by a determination unit [204] at the A2P-IPSMGW [118A],
a domain status based on at least the target domain and a set of pre-stored domains,
30 wherein the domain status is at least one of a positive domain status and a negative
domain status. The domain status may refer to a status regarding availability
25

regarding the domain of the target domain in a set of pre-stored domains. The
positive domain status refers to the positive availability of the target domain, and
the negative domain status refers to the non-availability of the target domain. The
set of pre-stored domains may refer to a list of pre-stored domain wherein the pre-
5 stored domains may contain information of the service providers. The
determination unit [204] may be a processor capable of determining a domain status
based on processing some input data.
[0100] Further, the present disclosure further discloses that the positive domain
10 status is determined in an event the target domain is a successful match with at least
one of a pre-stored domain from the set of pre-stored domains. The event the target domain is a successful match may refer to the situation where the target domain is present in the set of pre-stored domains which results in a match.
15 [0101] Furthermore, in an implementation of the of present solution as disclosed
herein, the negative domain status is determined in an event the target domain is an unsuccessful match with each of the pre-stored domain from the set of pre-stored domains. The event the target domain is an unsuccessful match may refer to the situation where the target domain is not present in the set of pre-stored domains.
20
[0102] Next, at step [312], the method [300] as disclosed by the present disclosure comprises transmitting, by the transceiver unit [202] from the A2P-IPSMGW [118A], a User Data Request (UDR) based on the positive domain status. The UDR may be a database of clients storing information associated with customers such as
25 services available for them, QoS parameters, etc. The UDR request may be a request
seeking information from the UDR sent by IPSMGW to HSS via DRA over the diameter. The IPSMGW receives a user data response in response to the UDR which contains the information of context/profile information of other party.
30 [0103] Next, at step [314], the method [300] as disclosed by the present disclosure
comprises receiving, by the transceiver unit [202] at the A2P-IPSMGW [118A], a
26

user data associated with the target user [302A] based on the UDR request. The user data may be the information stored within the UDR related to the target user [302A].
[0104] Next, at step [316], the method [300] as disclosed by the present disclosure
5 comprises transmitting, by the transceiver unit [202] from the A2P-IPSMGW
[118A] via a Session Initiation Protocol (SIP), the message to the target user [302A]
associated with the message request based on the user data and the target domain.
The Session Initiation Protocol (SIP) is a signalling protocol used for initiating,
maintaining, and terminating communication sessions that include voice, video and
10 messaging applications.
[0105] Further, in an implementation of the of present solution as disclosed herein, the method further comprises validating by a validation unit [206] at least a mobile number associated with the target user [302A] based on one or more validation
15 techniques, wherein the mobile number associated with the target user [302A] is
extracted from the message request. The Mobile Number means the Mobile Subscriber Integrated Services Digital Network (MSISDN) mobile or cellular phone number, which is associated with a subscriber identity module (SIM) card at the time of activation. The one or more validation techniques can include anti-spam
20 function such as checking whether the sender and originator is valid (valid-sender
valid-originator), checking quantity of the SMS for a duration for checking SMS flooding, and checking service and billing information for both users i.e. the sender and the receiver of the message.
25 [0106] Thereafter, the method [300] terminates at step [318].
[0107] Referring to FIG. 3A, an exemplary call flow diagram [300A], for
transmitting a message to a target user [302A], in accordance with exemplary
implementations of the present disclosure is shown. In an implementation the
30 method [300A] is performed by the system [200].
27

[0108] The message may refer to an incoming message at a network entity which
may be, but not limited to, a request for porting a mobile number to a different
service provider and an action message such as wakeup message, triggering
messages, alerts, etc. The target user [302A] may refer to the user or subscriber
5 which is trying to port the mobile number.
[0109] At step 1, the method [300A] as disclosed by the present disclosure comprises receiving, by a transceiver unit [202] at an Application to Peer – Internet Protocol (A2P-IP) short message gateway (A2P-IPSMGW) [118A], a message
10 request associated with the target user [302A]. The IPSMGW may be an IP
Multimedia System (IMS) Application Server which handles Session Initiation Protocol (SIP) based messaging services for IMS subscribers. The A2P IPSMGW [118A] may refer to an IPSMGW specially for messaging services from an application to a peer or peer to application such as the target user [302A]. The
15 message request may refer to a request sent by a user equipment (UE) or a
subscriber related to the porting by the target user [302A]. The transceiver unit [202] may be a device capable of transmission and reception of data and/or signals.
[0110] Further, the present disclosure further discloses that the message request
20 associated with the target user [302A] may also be received at the A2P-IPSMGW
[118A] via an External Short Messaging Entity (ESME) [402] over short message
peer-to-peer protocol (SMPP). The ESME [402] may be an external application that
connects to a Short Message Service Centre (SMSC) to engage in the sending or
receiving of SMS messages. It may be noted that the abovementioned example is
25 only exemplary and in no manner should be construed to limit the scope of the
present disclosure. Further, any other examples of the ESME [402] for receiving the message request at the A2P-IPSMGW [118A] may be received via a machine type communication and a mobile internet of things technology as well.
30 [0111] Next, at step 2, the method [300A] as disclosed by the present disclosure
comprises transmitting, by the transceiver unit [202] from the A2P-IPSMGW
28

[118A] to a mobile number portability server (MNP server [304A]), a mobile
number portability request (MNP request) based on the message request. The
Mobile number portability (MNP) is a service that allows the user / subscriber to
change the service provider and keep the same mobile number. The MNP server
5 [304A] is a server which is responsible for handling the MNP service. The MNP
request is sent to the MNP sever to obtain a domain of receiving party for transmitting the message.
[0112] Next, at step 3, the method [300A] as disclosed by the present disclosure
10 comprises receiving, by the transceiver unit [202] at the A2P-IPSMGW [118A]
from the MNP server [304A], a mobile number portability response (MNP
response) comprising at least a target domain based on the MNP request. The MNP
response is a response to the request made by the user/subscriber regarding MNP.
The target domain refers to the public land mobile network (PLMN), a location of
15 operator, or a network technology of target user [302A].
[0113] Next, at step 4, the method [300A] as disclosed by the present disclosure comprises determining, by a determination unit [204] at the A2P-IPSMGW [118A], a domain status based on at least the target domain and a set of pre-stored domains,
20 wherein the domain status is at least one of a positive domain status and a negative
domain status. The domain status may refer to a status regarding availability regarding the domain of the target domain in a set of pre-stored domains. The positive domain status refers to the positive availability of the target domain, and the negative domain status refers to the non-availability of the target domain. The
25 set of pre-stored domains may refer to a list of pre-stored domain wherein the pre-
stored domains may contain information of the service providers. The determination unit [204] may be a processor capable of determining a domain status based on processing some input data.
30 [0114] Further, the present disclosure further discloses that the positive domain
status is determined in an event the target domain is a successful match with at least
29

one of a pre-stored domain from the set of pre-stored domains. The event the target domain is a successful match may refer to the situation where the target domain is present in the set of pre-stored domains which results in a match.
5 [0115] Furthermore, in an implementation of the of present solution as disclosed
herein, the negative domain status is determined in an event the target domain is an unsuccessful match with each of the pre-stored domain from the set of pre-stored domains. The event the target domain is an unsuccessful match may refer to the situation where the target domain is not present in the set of pre-stored domains.
10
[0116] Next, at step 5, the method [300A] as disclosed by the present disclosure comprises transmitting, by the transceiver unit [202] from the A2P-IPSMGW [118A], a User Data Request (UDR) to Home subscriber server (HSS) based on the positive domain status. The HSS may be a database of clients storing information
15 associated with customers such as services available for them, QoS parameters, etc.
The UDR request may be a request seeking information sent by the IPSMGW to the HSS via DRA over the diameter. The IPSMGW receives a user data answer (UDA) in response to the UDR which contains the information of context/profile information of other party. The UDR request may be sent to the HSS.
20
[0117] Next, at step 6, the method [300A] as disclosed by the present disclosure comprises receiving, by the transceiver unit [202] at the A2P-IPSMGW [118A], a user data associated with the target user [302A] based on the UDR request. The user data may be the information stored within the UDR related to the target user [302A].
25 The user data may be received by the A2P-IPSMGW [118A] from the HSS.
[0118] Next, at step 7, the method [300A] as disclosed by the present disclosure
comprises transmitting, by the transceiver unit [202] from the A2P-IPSMGW
[118A] via a Session Initiation Protocol (SIP), the message to the target user [302A]
30 associated with the message request based on the user data and the target domain.
The Session Initiation Protocol (SIP) is a signalling protocol used for initiating,
30

maintaining, and terminating communication sessions that include voice, video and messaging applications.
[0119] Further, in an implementation of the of present solution as disclosed herein,
5 the method further comprises validating by a validation unit [206] at least a mobile
number associated with the target user [302A] based on one or more validation techniques, wherein the mobile number associated with the target user [302A] is extracted from the message request. The Mobile Number means the Mobile Subscriber Integrated Services Digital Network (MSISDN) mobile or cellular
10 phone number, which is associated with a subscriber identity module (SIM) card at
the time of activation. The one or more validation techniques can include anti-spam function such as checking whether the sender and originator is valid (valid-sender valid-originator), checking quantity of the SMS for a duration for checking SMS flooding, and checking service and billing information for both users i.e. the sender
15 and the receiver of the message.
[0120] Thereafter, the method [300A] is terminated.
[0121] Now, referring to FIG. 4 illustrates a non-limiting exemplary scenario
20 signal flow diagram [400] illustrating routing of messages, in accordance with
exemplary implementations of the present disclosure. The present disclosure also
relates to a method for routing the message from application to peer and peer to
application over the SIP protocol. The method [400] includes the step of receiving,
from the ESME [402] via a short message peer-to-peer protocol [SMPP], an
25 application to peer message at the A2P-IP SMGW [118A].
[0122] Then the method [400] may also include validating the requested mobile number using the validation process.
30 [0123] Next step includes sending an MNP request to the MNP server [304A]
against an MNP query after successful validation of the mobile number. The MNP
31

request is sent to the MNP server [304A] to obtain target user [302A] domain, and
then check the existence of the target domain (specified domain) (in the MNP
query) in a domain map which may be stored within the domain database [404] or
may also be stored in the storage unit for the A2P-IPSMGW [118A]. The domain
5 database [404] is maintained by the Network Management team at the network
level.
[0124] Next step includes sending a request to the UDR to deliver the message over the SIP protocol in case the specified domain is found in the domain database [404]. 10
[0125] Next step includes delivering of message to the receiver [406] over the SIP protocol.
[0126] Thus, the present disclosure routes the message traffic over SIP protocol in
15 an event the requested domain in identified or found in the domain database [404].
Local traffic or peer to peer message traffic is sent over the MAP protocol to optimise and handle the traffic.
[0127] The storage unit and the domain database are configured to store data
20 associated with implementation of the features of the present disclosure.
[0128] Fig. 5 illustrates an exemplary block diagram of a computing device [500] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an
25 implementation, the computing device [500] may also implement the method [400]
for transmitting a message to a target user [302A] by utilising the system [200]. In another implementation, the computing device [500] itself implements the method [400] for transmitting a message to a target user [302A] using one or more units configured within the computing device [500], wherein said one or more units are
30 capable of implementing the features as disclosed in the present disclosure.
32

[0129] The computing device [500] may include a bus [602] or other
communication mechanism for communicating information, and a hardware
processor [504] coupled with bus [502] for processing information. The hardware
processor [504] may be, for example, a general-purpose microprocessor. The
5 computing device [500] may also include a main memory [506], such as a random-
access memory (RAM), or other dynamic storage device, coupled to the bus [502] for storing information and instructions to be executed by the processor [504]. The main memory [506] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the
10 processor [504]. Such instructions, when stored in non-transitory storage media
accessible to the processor [504], render the computing device [500] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [500] further includes a read only memory (ROM) [508] or other static storage device coupled to the bus [502] for storing static
15 information and instructions for the processor [504].
[0130] A storage device [510], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [502] for storing information and instructions. The computing device [500] may be coupled via the bus [502] to a
20 display [512], 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 [514], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [502] for communicating information and command selections to the processor
25 [504]. Another type of user input device may be a cursor controller [516], such as a
mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [504], and for controlling cursor movement on the display [512]. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow
30 the device to specify positions in a plane.
33

[0131] The computing device [500] may implement the techniques described
herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware
and/or program logic which in combination with the computing device [500] causes
or programs the computing device [500] to be a special-purpose machine.
5 According to one implementation, the techniques herein are performed by the
computing device [500] in response to the processor [504] executing one or more
sequences of one or more instructions contained in the main memory [506]. Such
instructions may be read into the main memory [506] from another storage medium,
such as the storage device [510]. Execution of the sequences of instructions
10 contained in the main memory [506] causes the processor [504] 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.
15 [0132] The computing device [500] also may include a communication interface
[518] coupled to the bus [502]. The communication interface [518] provides a two-way data communication coupling to a network link [520] that is connected to a local network [522]. For example, the communication interface [518] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or
20 a modem to provide a data communication connection to a corresponding type of
telephone line. As another example, the communication interface [518] 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 implementation, the communication interface [518] sends and receives electrical,
25 electromagnetic or optical signals that carry digital data streams representing
various types of information.
[0133] The computing device [500] can send messages and receive data, including
program code, through the network(s), the network link [520] and the
30 communication interface [518]. In the Internet example, a server [530] might
transmit a requested code for an application program through the Internet [528], the
34

ISP [526], the local network [522], the host [524] and the communication interface [518]. The received code may be executed by the processor [504] as it is received, and/or stored in the storage device [510], or other non-volatile storage for later execution. 5
[0134] Further, an aspect of the present disclosure relates to a non-transitory computer readable storage medium storing instructions for transmitting a message to a target user [302A], the non-transitory computer readable storage medium comprising executable code which, when executed by one or more units of a
10 system, causes the one or more units of the system to: receive, by a transceiver unit
of the system at an A2P-IP short message gateway (A2P-IPSMGW) [118A], a message request associated with the target user [302A]; transmit, by the transceiver unit of the system from the A2P-IPSMGW [118A] to a mobile number portability server (MNP server [304A]), a mobile number portability request (MNP request)
15 based on the message request; receive, by the transceiver unit of the system at the
A2P-IPSMGW [118A] from the MNP server [304A], a mobile number portability response (MNP response) comprising at least a target domain based on the MNP request; determine, by a determination unit of the system at the A2P-IPSMGW [118A], a domain status based on at least the target domain and a set of pre-stored
20 domains, wherein the domain status is at least one of a positive domain status and
a negative domain status; transmit, by the transceiver unit of the system from the A2P-IPSMGW [118A], a User Data Repository (UDR) request based on the positive domain status; receive, at the A2P-IPSMGW [118A], a user data associated with the target user [302A] based on the UDR request; and transmit, by the
25 transceiver unit of the system from the A2P-IPSMGW [118A] via a Session
Initiation Protocol (SIP), the message to the target user [302A] associated with the message request based on the user data and the target domain.
[0135] As is evident from the above, the present disclosure provides a technically
30 advanced solution for transmitting a message to a target user [302A] based on a
domain and for handling of traffic related to domain specific messages or SMS.
35

Thus, in view of the above disclosure, the A2P-IP SMGW node connected with the
system [200] efficiently handles the domain specific traffic over SIP protocol. Thus,
present disclosure enables the efficient and smooth functioning of the network to
handle the message traffic by routing the message traffic over MAP or SIP protocol
5 based on the requested domain. Therefore, sending a message over SIP on the basis
of domain increase the performance of the network. In addition, the processing task by the CPU further reduces due to division of the protocols based on the traffic.
[0136] While considerable emphasis has been placed herein on the disclosed
10 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
15 and non-limiting.
[0137] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various the components/units can be implemented interchangeably. While specific embodiments may disclose a
20 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
25 functionality described herein, are considered to be encompassed within the scope
of the present disclosure.
36

We Claim:
1. A method for transmitting a message to a target user [302A], the method
comprising:
- receiving, by a transceiver unit [202] at an Application to Person – Internet
5 Protocol short message gateway (A2P-IPSMGW) [118A], a message
request associated with the target user [302A];
- transmitting, by the transceiver unit [202] from the A2P-IPSMGW [118A]
to a mobile number portability server (MNP server [304A]), a mobile
number portability request (MNP request) based on the message request;
10 - receiving, by the transceiver unit [202] at the A2P-IPSMGW [118A] from
the MNP server [304A], a mobile number portability response (MNP response) comprising at least a target domain based on the MNP request;
- determining, by a determination unit [204] at the A2P-IPSMGW [118A], a
domain status based on at least the target domain and a set of pre-stored
15 domains, wherein the domain status is at least one of a positive domain
status and a negative domain status;
- transmitting, by the transceiver unit [202] from the A2P-IPSMGW [118A],
a User Data Request (UDR) based on the positive domain status;
- receiving, by the transceiver unit [202] at the A2P-IPSMGW [118A], a user
20 data associated with the target user [302A] based on the UDR request; and
- transmitting, by the transceiver unit [202] from the A2P-IPSMGW [118A]
via a Session Initiation Protocol (SIP), the message to the target user [302A]
associated with the message request based on the user data and the target
domain.
25
2. The method as claimed in claim 1, wherein the message request associated
with the target user [302A] is received at the A2P-IPSMGW [118A] via an
External Short Messaging Entity (ESME) [402].

3. The method as claimed in claim 1, further comprises validating, by a
validation unit [206], at least a mobile number associated with the target user
[302A] based on one or more validation techniques, wherein the mobile
number associated with the target user [302A] is extracted from the message
5 request.
4. The method as claimed in claim 1, wherein the positive domain status is
determined in an event the target domain is a successful match with at least
one of a pre-stored domain from the set of pre-stored domains.
10
5. The method as claimed in claim 1, wherein the negative domain status is
determined in an event the target domain is an unsuccessful match with each
of the pre-stored domain from the set of pre-stored domains.
15 6. A system [200] for transmitting a message to a target user [302A], the system
comprises:
- a transceiver unit [202], wherein the transceiver unit [202] is configured to:
• receive, at an application to peer – internet protocol (A2P-IP) short
message gateway (A2P-IPSMGW) [118A], a message request
20 associated with the target user [302A],
• transmit, from the A2P-IPSMGW [118A] to a mobile number portability
server (MNP server [304A]), a mobile number portability request (MNP
request) based on the message request,
• receive, at the A2P-IPSMGW [118A] from the MNP server [304A], a
25 mobile number portability response (MNP response) comprising at least
a target domain based on the MNP request; and
- a determination unit [204] connected to at least the transceiver unit [202],
wherein the determination unit [204] is configured to:
• determine, at the A2P-IPSMGW [118A], a domain status based on at
30 least the target domain and a set of pre-stored domains, wherein the

domain status is at least one of a positive domain status and a negative domain status;
wherein the transceiver unit [202] is further configured to:
• transmit, from the A2P-IPSMGW [118A], a User Data Repository
5 (UDR) request based on the positive domain status,
• receive, at the A2P-IPSMGW [118A], a user data associated with the target user [302A] based on the UDR request, and
• transmit, from the A2P-IPSMGW [118A] via a Session Initiation Protocol (SIP), the message to the target user [302A] associated with the
10 message request based on the user data and the target domain.
7. The system [200] as claimed in claim 6, wherein the message request
associated with the target user [302A] is received at the A2P-IPSMGW
[118A] via an External Short Messaging Entity (ESME) [402]. 15
8. The system [200] as claimed in claim 6, further comprising a validation unit
[206] configured to validate, at least a mobile number associated with the
target user [302A] based on one or more validation techniques, wherein the
mobile number associated with the target user [302A] is extracted from the
20 message request.
9. The system [200] as claimed in claim 6, wherein the positive domain status is determined in an event the target domain is a successful match with at least one of a pre-stored domain from the set of pre-stored domains.
10. The system [200] as claimed in claim 6, wherein the negative domain status is determined in an event the target domain is an unsuccessful match with each of the pre-stored domain from the set of pre-stored domains.