Sign In to Follow Application
View All Documents & Correspondence

System And Method For Consolidating Distributed Multipart Messages In Ipsmgw Clusters

Abstract: The present invention relates to a system and method for consolidating distributed multipart messages in IPSMGW clusters. The disclosure encompasses a receiving unit [202] receiving a first part of a multipart message transmitted by a sender. The corresponding set of data is stored in a database [104] by a first storing unit [206A]. In an event one or more subsequent parts of the multipart message are received at a second IPSMGW [102B] having a second IP address: a querying unit [208] querying the database [104] to locate the set of data associated. A second storing unit [206B] storing the set of data corresponding to the one or more subsequent parts into the database [104]. A consolidation unit [210] consolidates by arranging each part of the multipart message. [FIG. 4]

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
15 July 2023
Publication Number
03/2025
Publication Type
INA
Invention Field
COMPUTER SCIENCE
Status
Email
Parent Application

Applicants

Jio Platforms Limited
Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.

Inventors

1. Vikash Agrawal
Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.

Specification

FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“SYSTEM AND METHOD FOR CONSOLIDATING DISTRIBUTED MULTIPART MESSAGES IN IPSMGW
CLUSTERS”
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.

SYSTEM AND METHOD FOR CONSOLIDATING DISTRIBUTED MULTIPART MESSAGES IN IPSMGW CLUSTERS
FIELD OF THE DISCLOSURE
[0001] The present disclosure relates generally to the field of wireless communication systems. In particular, the present disclosure relates to message delivery in an Internet Protocol Short Message Gateway (IPSMGW) cluster environment. More particularly, the present disclosure relates to system and method for consolidating distributed multipart messages in IPSMGW clusters.
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 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 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. 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] Existing challenges in the art of handling multipart messages in Internet Protocol (IP) Short Message Gateway (IPSMGW) clusters within an IP Multimedia Subsystem (IMS) network are significant and can lead to inefficiencies and potential failures in message delivery. One of the primary problems is the fragmented handling of multipart messages, where different parts of the same message are received by separate IPSMGWs within a cluster. This fragmentation complicates the reassembly of the message and can result in inconsistent message delivery, with parts of the message arriving at the recipient at different times or in the wrong order. Existing resource inefficiencies are also a concern. Without a centralized mechanism for managing multipart messages, redundant processing and storage can occur across multiple IPSMGWs, which can strain network resources and increase operational costs. Additionally, the complexity of tracking multipart messages across several IPSMGWs poses challenges in troubleshooting and ensuring reliable message delivery. Existing risks of message loss are notable. If one part of a multipart message is received and processed by one IPSMGW while another part is lost or fails to be delivered, the entire message may become incomplete or undeliverable, leading to the loss or delay of critical information. Moreover, as the volume of multipart messages increases, existing scalability concerns may arise, as the challenges associated with fragmented handling and resource inefficiency can become more pronounced, potentially impacting the scalability of the messaging infrastructure.
[0005] Therefore, considering the foregoing discussion, there exists a need to overcome the aforementioned drawbacks.

[0006] Thus, there exists an imperative need in the art to provide a method and system for consolidating distributed multipart messages in IPSMGW clusters.
OBJECTS OF THE PRESENT DISCLOSURE
[0007] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0008] It is an object of the present disclosure to provide a system and method for consolidating distributed multipart messages in IPSMGW clusters.
[0009] It is another object of the present disclosure to provide a system and method for consolidating distributed multipart messages in IPSMGW clusters that ensures the efficient reassembly of multipart messages, regardless of which IPSMGW within the cluster receives each part of the message.
[0010] It is another object of the present disclosure to provide a system and method for consolidating distributed multipart messages in IPSMGW clusters that minimizes the risk of message failure, ensuring that all parts of a multipart message are delivered to the recipient as intended.
[0011] It is another object of the present disclosure to provide a system and method for consolidating distributed multipart messages in IPSMGW clusters that reduces resource inefficiency by centralizing the management of multipart messages, thus minimizing redundant processing and storage across multiple IPSMGWs.
[0012] It is another object of the present disclosure to provide a system and method for consolidating distributed multipart messages in IPSMGW clusters that simplifies the tracking and troubleshooting of multipart messages, enhancing the reliability of message delivery.

[0013] It is another object of the present disclosure to provide a system and method for consolidating distributed multipart messages in IPSMGW clusters that addresses the risk of message loss, ensuring that all parts of a multipart message are received and processed correctly.
[0014] It is another object of the present disclosure to provide a system and method for consolidating distributed multipart messages in IPSMGW clusters that is scalable, capable of handling increasing volumes of multipart messages without compromising efficiency or reliability.
[0015] It is yet another object of the present disclosure to provide a system and method for consolidating distributed multipart messages in IPSMGW clusters that improves the overall user experience by ensuring the timely and accurate delivery of multipart messages.
SUMMARY OF THE DISCLOSURE
[0016] 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.
[0017] According to an aspect of the present disclosure, a method for consolidating multipart messages is disclosed. The method includes receiving, by a receiving unit via a first IPSMGW having a first IP address, a first part of a multipart message transmitted by a sender over an IP Multimedia Subsystem (IMS) network. The method further includes storing, by a first storing unit via the first IPSMGW, a set of data corresponding to the first part of the multipart message into a database. in an event one or more subsequent parts of the multipart message are received at a

second IPSMGW having a second IP address the method further includes querying, by a querying unit via the second IPSMGW, the database to locate the set of data associated with the first IP address. The method further includes storing, by a second storing unit via the second IPSMGW, the set of data corresponding to the one or more subsequent parts into the database and associating the set of data with the first IP address of the first IPSMGW. Upon receiving all parts of the multipart message or upon expiration of a pre-set time period, the method further includes consolidating, by a consolidation unit via the first IPSMGW, by arranging each part of the multipart message.
[0018] In an aspect, the method comprises formatting, by a formatting unit via the first IPSMGW, the consolidated multipart message into a single short message service (SMS) message compliant with the SMS over IMS standard.
[0019] In an aspect, the method comprises generating, by a generating unit, an alert acknowledging receipt of the multipart message by the recipient.
[0020] In an aspect, the alert acknowledging receipt is transmitted back to the sender via the first IPSMGW.
[0021] In an aspect, the database stores a key value pair, wherein a message identifier (ID) represents a key and the IP address of the IPSMGW represents a value of the key value pair.
[0022] In an aspect, the message identifier (ID) is used for querying the database, the message ID is a unique ID for the multipart message
[0023] In an aspect, the method further comprises deleting, by a processing unit, stored data corresponding to the multipart message from the database after successful transmission to the recipient.

[0024] In an aspect, the consolidation of each part of the multipart message comprises checking, by the processing unit, at least one of a checksum, and a hash validation of each part of the multipart message to ensure data integrity.
[0025] In an aspect, the pre-set time period is adjustable based on one of a network condition or a usage pattern.
[0026] In an aspect, consolidation by arranging each part of the multipart message is based according to at least one of a sequence number and a timestamp associated with the multipart message.
[0027] In an exemplary aspect, the method further comprises transmitting, by a transmitting unit via the first IPSMGW, the consolidated multipart message to a recipient.
[0028] Another aspect of the present disclosure provides a system for consolidating multipart messages. The system includes a receiving unit configured to receive, via a first IPSMGW having a first IP address, a first part of a multipart message transmitted by a sender over an IP Multimedia Subsystem (IMS) network. The system includes a first storing unit configured to store via the first IPSMGW, a set of data corresponding to the first part of the multipart message into a database. The system further includes a querying unit configured to query, via the second IPSMGW, the database to locate the set of data associated with the first IP address. The system further includes a second storing unit configured to store via the second IPSMGW, the set of data corresponding to the one or more subsequent parts into the database and associating the set of data with the first IP address of the first IPSMGW. The system further includes a consolidation unit configured to consolidate via the first IPSMGW, by arranging each part of the multipart message.

[0029] According to another aspect of the present disclosure, a user equipment
(UE) for consolidating multipart messages is disclosed. The UE comprising: a
processor configured to: send multi-part message to a first IPSMGW having a first
IP address, wherein a consolidated multipart message is received at a recipient, and
5 wherein the multipart message is consolidated based on: storing, via the first
IPSMGW, a set of data corresponding to a first part of the multipart message into a database; in an event one or more subsequent parts of the multipart message are received at a second IPSMGW having a second IP address: querying, via the second IPSMGW, the database to locate the set of data associated with the first IP address;
10 and storing, via the second IPSMGW, the set of data corresponding to the one or
more subsequent parts into the database, and associating the set of data with the first IP address of the first IPSMGW; upon receiving all parts of the multipart message or upon expiration of a pre-set time period, consolidating, via the first IPSMGW, by arranging each part of the multipart message according to a sequence
15 number within the multipart message.
[0030] Yet another aspect of the present disclosure provides a non-transitory computer-readable storage medium storing instruction for consolidating multipart messages, the storage medium comprising executable code which, when executed
20 by one or more units of a system, causes: a receiving unit to receive, via a first
IPSMGW having a first IP address, a first part of a multipart message transmitted by a sender over an IP Multimedia Subsystem (IMS) network; a first storing unit to store via the first IPSMGW, a set of data corresponding to the first part of the multipart message into a database [104]; in an event one or more subsequent parts
25 of the multipart message are received at a second IPSMGW having a second IP
address: a querying unit to query, via the second IPSMGW, the database to locate the set of data associated with the first IP address; and a second storing unit to store via the second IPSMGW, the set of data corresponding to the one or more subsequent parts into the database, and associating the set of data with the first IP
30 address of the first IPSMGW; upon receiving all parts of the multipart message or
8

upon expiration of a pre-set time period, a consolidation unit to consolidate via the first IPSMGW, by arranging each part of the multipart message.
BRIEF DESCRIPTION OF DRAWINGS
5
[0031] 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,
10 emphasis instead being placed upon clearly illustrating the principles of 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 appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to
15 implement such components.
[0032] FIG.1 illustrates an exemplary block diagram of a system architecture for IP short message gateway (IPSMGW) clusters, in accordance with exemplary embodiments of the present disclosure. 20
[0033] FIG.2 illustrates an exemplary block diagram of a system for consolidating distributed multipart messages in IP Short Message Gateway (IPSMGW) clusters, in accordance with exemplary embodiments of the present disclosure.
25 [0034] FIG.3 illustrates an exemplary block diagram of a system architecture for
consolidating distributed multipart messages in IP short message gateway clusters, in accordance with exemplary embodiments of the present disclosure.
[0035] FIG.4 illustrates an exemplary method flow diagram indicating the process
30 for consolidating distributed multipart messages in IP Short Message Gateway
9

(IPSMGW) clusters, in accordance with exemplary embodiments of the present disclosure.
[0036] FIG. 5 illustrates an exemplary block diagram of a computing device upon
5 which an embodiment of the present disclosure may be implemented.
[0037] FIG. 6 illustrates an exemplary block diagram of a user equipment [UE] for consolidating distributed multipart messages in IP Short Message Gateway (IPSMGW) clusters. 10
[0038] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION
15
[0039] 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 embodiments of the present disclosure may be practiced without these specific
20 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 embodiments of
25 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.
[0040] The ensuing description provides exemplary embodiments only, and is not
30 intended to limit the scope, applicability, or configuration of the disclosure. Rather,
10

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
arrangement of elements without departing from the spirit and scope of the
5 disclosure as set forth.
[0041] 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 invention. These terms are not
10 intended to limit the scope of the invention or imply any specific functionality or
limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The invention 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
15 of the invention as defined herein.
[0042] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these
20 specific details. For example, circuits, systems, networks, processes, and other
components may be shown as components in block diagram form in order not to obscure the embodiments 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 embodiments.
25
[0043] 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 can be performed in parallel or
30 concurrently. In addition, the order of the operations may be re-arranged. A process
11

is terminated when its operations are completed but could have additional steps not included in a figure.
[0044] The word “exemplary” and/or “demonstrative” is used herein to mean
5 serving as an example, instance, or illustration. For the avoidance of doubt, the
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
10 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 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.
15
[0045] As used herein, an “electronic device”, or “portable electronic device”, or “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
20 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, 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
25 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, 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
30 the art for implementation of the features of the present disclosure.
12

[0046] Further, the user device may also comprise a “processor” or “processing
unit” includes processing unit, wherein processor refers to any logic circuitry for
processing instructions. The processor may be a general-purpose processor, a
5 special purpose processor, a conventional processor, a digital signal processor, a
plurality of microprocessors, one or more microprocessors in association with a
DSP core, a 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,
10 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.
[0047] As portable electronic devices and wireless technologies continue to improve and grow in popularity, the advancing wireless technologies for data
15 transfer are also expected to evolve and replace the older generations of
technologies. In the field of wireless data communications, the dynamic 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),
20 and more such generations are expected to continue in the forthcoming time.
[0048] 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
25 stations, which are responsible for providing the wireless connection. Further, each
RAT has its own set of protocols and standards for communication, which define 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
30 (Universal Mobile Telecommunications System), LTE (Long-Term Evolution),
13

and 5G. The choice of RAT depends on a variety of factors, including the network
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
5 resources.
[0049] As discussed in the background section, existing challenges in the art of handling multipart messages in Internet Protocol Short Message Gateway (IPSMGW) clusters within an IP Multimedia Subsystem (IMS) network are
10 significant and can lead to inefficiencies and potential failures in message delivery.
One of the primary problems is the fragmented handling of multipart messages, where different parts of the same message are received by separate IPSMGWs within a cluster. This fragmentation complicates the reassembly of the message and can result in inconsistent message delivery, with parts of the message arriving at
15 the recipient at different times or in the wrong order. Existing resource
inefficiencies are also a concern. Without a centralized mechanism for managing multipart messages, redundant processing and storage can occur across multiple IPSMGWs, which can strain network resources and increase operational costs. Additionally, the complexity of tracking multipart messages across several
20 IPSMGWs poses challenges in troubleshooting and ensuring reliable message
delivery. Existing risks of message loss are notable. If one part of a multipart message is received and processed by one IPSMGW while another part is lost or fails to be delivered, the entire message may become incomplete or undeliverable, leading to the loss or delay of critical information. Moreover, as the volume of
25 multipart messages increases, existing scalability concerns may arise, as the
challenges associated with fragmented handling and resource inefficiency can become more pronounced, potentially impacting the scalability of the messaging infrastructure.
14

[0050] The present disclosure provides a method and system for consolidating
distributed multipart messages in Internet Protocol (IP) Short Message Gateway
(IPSMGW) clusters, effectively addressing the challenges and problems in the
existing art. By introducing a mechanism for coordinating the reception, storage,
5 and consolidation of multipart messages across different IPSMGWs, the present
disclosure ensures that all parts of a multipart message are received and processed at the same IPSMGW, thereby eliminating the issue of fragmented handling. This approach ensures consistent message delivery, with all parts of the message arriving at the recipient in the correct order and without delay. Furthermore, the present
10 disclosure reduces resource inefficiencies by centralizing the management of
multipart messages. By storing and consolidating message parts in a single IPSMGW, redundant processing and storage across multiple IPSMGWs are minimized, leading to more efficient use of network resources and reduced operational costs. The use of a database, such as a but not limited to a Redis
15 database, for storing message parts and associating them with a unique identifier
ensures efficient tracking and retrieval of message parts, simplifying troubleshooting and enhancing the reliability of message delivery. The present disclosure also addresses the risk of message loss by ensuring that all parts of a multipart message are consolidated at a single IPSMGW before delivery to the
20 recipient. This reduces the likelihood of incomplete or undeliverable messages due
to lost or unprocessed parts. Additionally, the system's ability to adjust the pre-set time period for message consolidation based on network conditions or usage patterns further enhances the scalability and adaptability of the messaging infrastructure.
25
[0051] It would be appreciated by the person skilled in the art that the present disclosure provides a comprehensive solution to the problems in the art by ensuring efficient, reliable, and consistent handling of multipart messages in IPSMGW clusters, thereby improving the overall performance and user experience of the
30 messaging system.
15

[0052] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.
5 [0053] FIG.1 illustrates an exemplary block diagram of a system architecture [100]
of IP short message gateway (IPSMGW) clusters, in accordance with exemplary embodiments of the present disclosure. As shown in FIG.1, the architecture diagram of IPSMGW comprising an Element Management System (EMS) [108], a Signalling Transfer Point (STP) [110], a Serving-Call Session Control Function
10 (SCSCF) [106], IP short message gateway (IPSMGW) [102], a Database [104],
Load Balancer [112a, 112b], a Diameter Routing Agent (DRA) [114], a Short Message Peer-to-Peer (SMPP) Charging Point (CP) [116], a Mobile Number Portability (MNP) [118], an Online Charging System (OCS) [120], a Home Subscriber Server (HSS) [122], a Service Capability Exposure Function (SCEF)
15 [124] and a Mobility Management Entity (MME) [126], which communicate with
each–other via a set of protocols such as, via a Transmission Control Protocol (TCP), a Mobile Application Part (MAP), a Representational State Transfer (REST), SIP (Session Initiation Protocol), Short Message Peer-to-Peer (SMPP) and Diameter Protocol. Further, as shown in FIG.1, the units/components uses Ro, Sh
20 & S6c, T4 and SGd interfaces for communication between them. Also, all of the
components/ units of the system architecture [100] are assumed to be connected to each other unless otherwise indicated below.
[0054] EMS (Element Management System) [108]: A software system used for
25 managing and monitoring network elements or devices within a
telecommunications network.
[0055] STP (Signalling Transfer Point) [110]: A network node used in the SS7
(Signalling System No. 7) telecommunications protocol to route signalling
30 messages between signalling endpoints.
16

[0056] SCSCF (Serving-Call Session Control Function) [106]: A core component in IMS (IP Multimedia Subsystem) networks responsible for session control and call processing. 5
[0057] Load Balancer [112]: A device or software component that evenly distributes incoming network traffic across multiple servers to optimize resource utilization, reliability, and performance.
10 [0058] DRA (Diameter Routing Agent) [114]: A network element responsible for
routing Diameter protocol messages within telecommunications networks, often used in IMS and LTE networks.
[0059] SMPP (Short Message Peer-to-Peer): A protocol used in the
15 telecommunications industry for exchanging SMS messages between Short
Message Service Centres (SMSCs) and SMS application systems.
[0060] CP (Charging Point): A network element responsible for charging and billing functions within a telecommunications network. 20
[0061] MNP (Mobile Number Portability) [118]: A service that allows mobile phone users to retain their phone numbers when switching between different service providers.
25 [0062] OCS (Online Charging System) [120]: A system used for real-time
charging and billing of telecommunications services, such as voice calls, data usage, and SMS messages.
17

[0063] HSS (Home Subscriber Server) [122]: A core component in LTE and IMS networks that stores subscriber-related information, such as user profiles, authentication data, and service subscriptions.
5 [0064] SCEF (Service Capability Exposure Function) [124]: A component in
IMS networks that exposes network capabilities to application servers, enabling the creation of innovative multimedia services.
[0065] MME (Mobility Management Entity) [126]: A key component in LTE
10 networks responsible for managing the mobility of mobile devices, including
tracking their location and handling handovers between base stations.
[0066] Database [104]: A structured collection of data organized for efficient storage, retrieval, and management. 15
[0067] TCP (Transmission Control Protocol): A reliable, connection-oriented protocol used for transmitting data over networks.
[0068] MAP (Mobile Application Part): A protocol used in cellular networks for
20 communication between various network elements, such as HLRs (Home Location
Registers) and VLRs (Visitor Location Registers).
[0069] REST (Representational State Transfer): An architectural style for designing networked applications, commonly used in web services development. 25
[0070] SIP (Session Initiation Protocol): SIP is a signalling protocol used for 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
18

establish communication sessions and negotiate the parameters of the session, such as codecs, media types, and session duration.
[0071] IPSMGW (IP Short Message Gateway) [102]: A network element
5 responsible for handling and routing Short Message Service (SMS) messages over
IP networks.
[0072] FIG.2 illustrates an exemplary block diagram of a system [200] for consolidating distributed multipart messages in IP Short Message Gateway
10 (IPSMGW) clusters, in accordance with exemplary embodiments of the present
disclosure. As shown in FIG. 2, the system [200] comprises a Receiving Unit [202], a Transmitting Unit [204], a first Storing Unit [206A], a second Storing Unit [206B], a Querying Unit [208], a Consolidation Unit [210], a Formatting Unit [212], a Generating Unit [214] and a Processing Unit [216], wherein all the
15 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. 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. In an
20 embodiment, the system [200] may be incorporated in IPSMGW [102].
[0073] The system [200] comprises the receiving unit [202] configured to receive, via a first IPSMGW [102A] having a first IP address, a first part of a multipart message transmitted by a sender over an IP Multimedia Subsystem (IMS) network.
25 The receiving unit [202] is responsible for initial reception of the multipart message.
When a sender transmits a multipart message over the IMS network, the message is divided into multiple parts (for example three) for efficient transmission or network restriction. For example - The first part of this multipart message is received by the first IPSMGW [102A] having a unique first IP address.
30
19

[0074] The system [200] comprises the first storing unit [206A] communicatively
coupled to the receiving unit [202]. The first storing unit [206A] is configured to
store, via the first IPSMGW [102A], a set of data corresponding to the first part of
the multipart message into a database [104]. The set of data includes not only the
5 content of the message part but also metadata associated with the message. The
metadata may include the sender's details, timestamp, and any sequence information. The database [104] acts as the central memory unit, maintaining a record of each message part of the multipart message.
10 [0075] The system [200] comprises the querying unit [208] communicatively
coupled to the first storing unit [206A]. The querying unit [208] is configured to query, via the second IPSMGW [102B], the database [104] to locate the set of data associated with the first IP address. In an exemplary aspect, a message identifier (ID) is used for querying the database [104], the message ID is a unique ID for the
15 multipart message. In an exemplary aspect, the message identifier (ID) corresponds
to subscriber identity such as but not limited to international mobile subscriber identity (IMSI), subscription permanent identifier (SUPI) etc. As used herein, IMSI is an internationally standardized unique number to identify a mobile subscriber. The IMSI consists of a Mobile Country Code (MCC), a Mobile Network Code
20 (MNC) and a Mobile Station Identification Number (MSIN). Further used herein,
SUPI is a unique identifier used to represent a subscriber's permanent identity in a 5G network. It replaces the IMSI used in 4G networks and is designed to provide enhanced privacy and security features. In an event where one or more subsequent parts of the multipart message are received at the second IPSMGW [102B] that has
25 a different IP address (such as second IP address) than the first IPSMGW [102A].
In such cases, the querying unit [208] performs a search within the database [104] to find the set of data corresponding to the first part of the message, which was stored by the first storing unit [206A] and is associated with the first IP address of the first IPSMGW [102A]. By identifying the set of data, the system ensures that
30 all subsequent parts of the multipart message received at the second IPSMGW
20

[102B] are correctly associated with the first part of the message, enabling effective consolidation and delivery of the complete message. This mechanism addresses the problem of message failures that occur when different parts of the same message are processed by different IPSMGWs within a cluster. 5
[0076] The system [200] comprises the second storing unit [206B] communicatively coupled to the querying unit [208]. The second storing unit [206B] is configured to store, via the second IPSMGW [102B], the set of data corresponding to the one or more subsequent parts of the multipart message into the
10 database [104] and associating the set of data with the first IP address of the first
IPSMGW [102A]. Once the querying unit [208] has identified the first IP address associated with the initial part (such as first part) of the multipart message, the second storing unit [206B] stores the subsequent parts of the multipart message in the database [104] with this same IP address. The association enables the system
15 [200] to correctly consolidate all parts of the multipart message at the first
IPSMGW [102A], thereby preventing message failures that can occur when different parts of the multipart message are processed by different IPSMGWs within a cluster.
20 [0077] The system [200] comprises the consolidation unit [210] communicatively
coupled to the first storing unit [206A] and the second storing unit [206B]. The consolidation unit [210] is configured to consolidate via the first IPSMGW [102A], by retrieving from the database [104] and arranging each part of the multipart message according to a sequence number or timestamp within the multipart
25 message. Upon receiving all parts of the multipart message or upon expiration of a
pre-set time period. In an exemplary aspect, the pre-set time period is adjustable based on one of a network condition or a usage pattern. For example, in a scenario where the network experiences high traffic and congestion, the system can extend the pre-set time period to ensure that all parts of a multipart message are received
30 and consolidated correctly. Conversely, in a less congested network environment
21

or during periods of low usage, the time period can be shortened to speed up message delivery.
[0078] The consolidation unit [210] by ensuring that the various parts of the
5 multipart message, which may have been received and stored at different
IPSMGWs, are brought together and arranged in the correct order based on their
sequence numbers. The ordered arrangement facilitates in reconstructing the
original message accurately. Once the consolidation process is complete, the
multipart message is reassembled into its intended form, ready for final
10 transmission to the recipient. The ability to consolidate multipart messages
efficiently and accurately ensures the integrity and reliability of message delivery within the IMS network.
[0079] The system [200] comprises the transmitting unit [204] communicatively
15 coupled to the consolidation unit [210]. The transmitting unit [204] is configured to
transmit, via the first IPSMGW [102A], the consolidated multipart message to a
recipient. The transmitting unit [204] takes the consolidated multipart message,
which has been organized and verified by the consolidation unit [210] and sends it
through the first IPSMGW [102A] to the intended recipient. The transmission is
20 carried out over the IP Multimedia Subsystem (IMS) network, utilizing the
established communication protocols to ensure secure and reliable delivery of the
message. The transmitting unit [204] is responsible for the final delivery of the
reassembled multipart message, ensuring that the recipient receives the multipart
message in its entirety and in the correct order, thereby solving the problem of
25 message failure when parts of the same message are received at different IPSMGWs
within a cluster.
[0080] The system [200] comprises the formatting unit [212] communicatively
coupled to the consolidation unit [210]. The formatting unit [212] is configured to
30 format, via the first IPSMGW [102A], the consolidated multipart message into a
22

single short message service (SMS) message compliant with the SMS over IMS
standard. The formatting process takes into account the sequence, timestamp and
structure of the message parts, transforming them from a multipart format into a
standard SMS format, which is accepted across by recipient devices and network
5 carriers thereby facilitates in maintaining consistency and reliability in the delivery
of SMS messages, particularly when originating from a complex IMS environment. The formatting unit [212] facilitates in providing a seamless end-user experience, ensuring that the message is received as intended by the sender, without any loss of content or context.
10
[0081] The system [200] comprises the generating unit [214] configured to generate an alert acknowledging receipt of the multipart message by the recipient. Once the consolidated multipart message is transmitted by the first IPSMGW [102A] and successfully delivered, the generating unit [214] initiates an
15 acknowledgment process. The acknowledgement process involves sending a
notification back to the original sender, confirming that their message has been received by the intended recipient. The alert facilitates in providing a closed-loop communication, ensuring the sender is informed of the delivery status, which is particularly important in systems where message delivery confirmation is required
20 for transactional integrity, user experience, or regulatory compliance. The alert is
routed back through the same first IPSMGW [102A], maintaining consistency in the communication path and leveraging the existing infrastructure to provide a reliable and traceable acknowledgment mechanism.
25 [0082] The system [200] comprises the processing unit [216], which is configured
to delete stored data corresponding to the multipart message from the database [104] after successful transmission to the recipient. Post-transmission, it is essential that the data footprint of the completed transaction is minimized to prevent unnecessary storage consumption and to mitigate any potential risks of data
30 breaches or privacy concerns. Furthermore, the processing unit [216] performs
23

integrity checks by performing validations on each part of the multipart message.
The processing unit [216] verify the checksum or compute hash validations for each
message segment. The verification process is a safeguard that ensures the data’s
integrity has been maintained throughout its journey from sender to recipient. If any
5 discrepancies are detected during this process, the system can take predefined
actions to address them, which might include requesting a retransmission of the message part or alerting a system administrator. Thus, the processing unit [216] not only enhances the operational efficiency of the system but also fortifies the trustworthiness of the communication process within the IMS network.
10
[0083] FIG.3 illustrates an exemplary block diagram of a network architecture [300] for consolidating distributed multipart messages in IP short message gateway clusters, in accordance with exemplary embodiments of the present disclosure. As shown in FIG. 3, the netowrk architecture [300] comprises a first IPSMGW [102A],
15 a second IPSMGW [102B], a third IPSMGW [102C], and a multipart message
sender [302], 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. Also, in FIG. 3 only a few units/modules are shown, however, the network architecture [300] may comprise multiple such units or the
20 network architecture [300] may comprise any such numbers of said units, as
required to implement the features of the present disclosure.
[0084] As shown in FIG. 3, the multipart message sender [302] sends a multipart
message to a recipient/another user/receiving party via system [200]. Further, the
25 first IPSMGW [102A] having a first IP address, configured to receive a first part of
a multipart message transmitted by the multipart message sender [302] over an Internet Protocol Multimedia Subsystem (IMS) network.
[0085] Further, the network architecture [300] comprises a database [104]
30 communicatively linked to the first IPSMGW [102A], wherein the first IPSMGW
24

[102A] is configured to store a fist set of data corresponding to the first part of the
multipart message into the database [104], associating the stored data with the first
IP address. In an exemplary aspect, the database [104] may be present in the system
[200]. In another exemplary aspect, the database [104] may be present outside and
5 communicatively coupled with the system [200]. In an implementation, the first
part of the message is written into the database [104], such as, but not limited to, a Redis database. The set of data is stored in association with the IP address of the first IPSMGW [102A]. The IP address serves as an identifier for the IPSMGW that received the first part of the multipart message.
10
[0086] Furthermore, the network architecture [300] comprises the second IPSMGW [102B] having a second IP address within the same cluster, configured to query the database [104] to locate data associated with the first IP address in the event a subsequent part of the multipart message is received at the second IPSMGW
15 [102B], and to write the data corresponding to the subsequent part into the database
[104], associating the data with the first IP address of the first IPSMGW [102A]. In an implementation, the second IPSMGW [102B] reads the data associated with the IP address of the first IPSMGW [102A] from the database [104] such as, Redis database.
20
[0087] Subsequently, the network architecture [300] comprising a consolidation unit [210] within the system [200], configured to consolidate all parts of the multipart message based on the associated data retrieved from the database [104], ensuring that each part is arranged according to its sequence number within the
25 multipart message. Once all parts of the multipart message have been received and
their data written into the database [104] under the IP address of the first IPSMGW [102A], these parts are consolidated. In an embodiment, the consolidation process occurs at the system [200] and ensures that all parts of the message are unified in the correct order, forming a complete and coherent message.
30
25

[0088] Thereafter, the network architecture [300] comprises a transmitting unit
[204] within the system [200], configured to transmit the consolidated multipart
message to the intended recipient/another user/receiving party. Finally, the
consolidated multipart message is sent to the intended recipient from the first
5 IPSMGW [102A]. This ensures the recipient receives the full, correctly ordered
message, even though its parts were initially received by different IPSMGWs within the cluster.
[0089] In an exemplary aspect, the system [200] may be communicatively coupled
10 externally in IPSMGWs cluster. In another exemplary aspect, the system [200] may
be partially present in any IPSMGWs of the cluster and partially communicatively coupled externally. In another exemplary aspect, the system [200] may be present in any IPSMGWs of the cluster.
15 [0090] In an exemplary aspect, when the first IPSMGW (IPSM-1) receives the
initial part of a multipart message, it assigns a unique message identifier (ID) and stores its own IP address in the database [104] using the message ID as the key. Subsequent parts of the multipart message, received by other IPSMGW instances, query the database to retrieve the IP address of the IPSMGW where the first part
20 was received. Instead of storing these subsequent parts locally, these IPSMGW
instances forward all received parts to the first IPSMGW (IPSM-1) using the retrieved IP address. The first IPSMGW then consolidates all parts of the multipart message. Once all parts are gathered, the first IPSMGW processes the complete message and routes it to the recipient.
25
[0091] For example, a sender, User, who is sending a long text message that gets divided into three parts (Part A, Part B, and Part C) due to its length. User sends his long text, and it's divided into three parts. Part A is received by IPSMGW1 in the cluster. IPSMGW1 verifies User's number and the recipient's number, let's say it's
30 Mary's number, for validity. After verification, IPSMGW1 writes the data of Part
26

A into a database (such as Redis). The database [104] stores a key-value pair, where
the message identifier (ID) represents the key, and the IP address of the IPSMGW
represents the value. The key-value pair enables efficient querying and retrieval of
data. The message identifier (ID) is unique for each multipart message and is used
5 to locate the corresponding IP address in the database. For example, an entry in the
database might look like:

Message ID IP
998700000_123 10.32.5.8
10 [0092] In this case, "998700000_123" is the unique message ID, and "10.32.5.8" is
the IP address of the IPSMGW that received the first part of the multipart message. The structure ensures that all parts of the multipart message can be accurately consolidated and delivered to the recipient.
15 [0093] In an alternative embodiment, the database may use a subscriber ID, such
as IMSI (International Mobile Subscriber Identity) or SUPI (Subscription Permanent Identifier), as the key instead of the message identifier. The system associate multipart messages with subscribers, thereby enhancing the flexibility and scalability of the messaging service. The database entry in such a case might look
20 like:

Subscriber ID IP
IMSI_310150123 10.32.5.8
[0094] Here, "IMSI_310150123" is the unique subscriber ID, and "10.32.5.8" is the
25 IP address of the IPSMGW.
27

[0095] Now, due to various reasons like load balancing, Part B is received by
IPSMGW2, and Part C is received by IPSMGW3. Rather than processing these
parts independently, IPSMGW2 and IPSMGW3 refer to the Redis database.
IPSMGW2 and IPSMGW3 read the data, using message identifier (ID), from the
5 database (such as Redis database). Further, they write the data of Part B and Part C,
respectively, into the database, associating them with the IP address of IPSMGW1. Furthermore, all parts of User's long text message (Part A, Part B, and Part C) are now stored in the database associated with its IP address. IPSMGW1 consolidates these parts into the complete message. Finally, IPSMGW1 sends the consolidated
10 long text message to Mary. From Mary's perspective, she receives a single,
complete, and coherent text message from User. Through this method, even if a multipart message is initially received by different IPSMGWs within a cluster, the message is effectively consolidated and delivered in its entirety via same IPSMGW, improving the overall reliability and efficiency of the message delivery process.
15
[0096] Referring to FIG. 4 an exemplary method flow diagram [400] indicating the process for consolidating distributed multipart messages in IP Short Message Gateway (IPSMGW) clusters is disclosed, in accordance with exemplary embodiments of the present invention is shown. In an implementation the method
20 [400] is performed by the system [200]. As shown in FIG. 4, the method [400] starts
at step [402].
[0097] At step 404, the method [400] encompasses receiving, by a receiving unit [202] via a first IPSMGW [102A] having a first IP address, a first part of a multipart
25 message transmitted by a sender over an IP Multimedia Subsystem (IMS) network.
The receiving unit [202] is responsible for initial reception of the multipart message. When a sender transmits a multipart message over the IMS network, the message is divided into multiple parts (for example three) for efficient transmission. For example - The first part of this multipart message is received by the first IPSMGW
30 [102A] having a unique first IP address.
28

[0098] At step 406, the method [400] encompasses storing, by a first storing unit
[206A] via the first IPSMGW [102A], a set of data corresponding to the first part
of the multipart message into a database [104]. The set of data includes not only the
5 content of the message part but also metadata associated with the message. The
metadata may include the sender's details, timestamp, and any sequence information. The database [104] acts as the central memory unit, maintaining a record of each message part of the multipart message.
10 [0099] At step 408, the method [400] querying, by a querying unit [208] via the
second IPSMGW [102B], the database [104] to locate the set of data associated with the first IP address. In an exemplary aspect, a message identifier (ID) is used for querying the database [104]. The message ID is a unique ID for the multipart message. In an exemplary aspect, the message identifier (ID) may correspond to
15 subscriber identity such as but not limited to international mobile subscriber identity
(IMSI), subscription permanent identifier (SUPI) etc. In an event where one or more subsequent parts of the multipart message are received at the second IPSMGW [102B] that has a different IP address (such as second IP address) than the first IPSMGW [102A]. In such cases, the querying unit [208] performs a search within
20 the database [104] to find the set of data corresponding to the first part of the
message, which was stored by the first storing unit [206A] and is associated with the first IP address of the first IPSMGW [102A]. By identifying the set of data, the system ensures that all subsequent parts of the multipart message received at the second IPSMGW [102B] are correctly associated with the first part of the message,
25 enabling effective consolidation and delivery of the complete message. This
mechanism addresses the problem of message failures that occur when different parts of the same message are processed by different IPSMGWs within a cluster.
[0100] At step 410, the method [400] encompasses storing, by a second storing unit
30 [206B] via the second IPSMGW [102B], the set of data corresponding to the one
29

or more subsequent parts into the database [104], and associating the set of data
with the first IP address of the first IPSMGW [102A]. Once the querying unit [208]
has identified the first IP address associated with the initial part (such as first part)
of the multipart message, the second storing unit [206B] stores the subsequent parts
5 of the multipart message in the database [104] with this same IP address. The
association enables the system [200] to correctly consolidate all parts of the multipart message at the first IPSMGW [102A], thereby preventing message failures that can occur when different parts of the multipart message are processed by different IPSMGWs within a cluster.
10
[0101] At step 412, the method [400] encompasses consolidating, by a consolidation unit [210] via the first IPSMGW [102A], by arranging each part of the multipart message according to a sequence number within the multipart message. Upon receiving all parts of the multipart message or upon expiration of a
15 pre-set time period. The consolidation unit [210] by ensuring that the various parts
of the multipart message, which may have been received and stored at different IPSMGWs, are brought together and arranged in the correct order based on their sequence numbers. The ordered arrangement facilitates in reconstructing the original message accurately. Once the consolidation process is complete, the
20 multipart message is reassembled into its intended form, ready for final
transmission to the recipient. The ability to consolidate multipart messages efficiently and accurately ensures the integrity and reliability of message delivery within the IMS network.
25 [0102] The method [400] further encompasses transmitting, by a transmitting unit
[204] via the first IPSMGW [102A], the consolidated multipart message to a recipient. The transmitting unit [204] takes the consolidated multipart message, which has been organized and verified by the consolidation unit [210] and sends it through the first IPSMGW [102A] to the intended recipient. The transmission is
30 carried out over the IP Multimedia Subsystem (IMS) network, utilizing the
30

established communication protocols to ensure secure and reliable delivery of the
message. The transmitting unit [204] is responsible for the final delivery of the
reassembled multipart message, ensuring that the recipient receives the multipart
message in its entirety and in the correct order, thereby solving the problem of
5 message failure when parts of the same message are received at different IPSMGWs
within a cluster.
[0103] Further, the method [400] comprises formatting, by a formatting unit [212] via the first IPSMGW [102A], the consolidated multipart message into a single
10 short message service (SMS) message compliant with the SMS over IMS standard.
The formatting process takes into account the sequence and structure of the message parts, transforming them from a multipart format into a standard SMS format, which is universally accepted across devices and network carriers thereby facilitates in maintaining consistency and reliability in the delivery of SMS messages,
15 particularly when originating from a complex IMS environment. The formatting
unit [212] facilitates in providing a seamless end-user experience, ensuring that the message is received as intended by the sender, without any loss of content or context.
20 [0104] Furthermore, the method [400] comprises generating, by a generating unit
[214], an alert acknowledging receipt of the multipart message by the recipient. Once the consolidated multipart message is transmitted by the first IPSMGW [102A] and successfully delivered, the generating unit [214] initiates an acknowledgment process. The acknowledgement process involves sending a
25 notification back to the original sender, confirming that their message has been
received by the intended recipient. The alert facilitates in providing a closed-loop communication, ensuring the sender is informed of the delivery status, which is particularly important in systems where message delivery confirmation is required for transactional integrity, user experience, or regulatory compliance. The alert is
30 routed back through the same first IPSMGW [102A], maintaining consistency in
31

the communication path and leveraging the existing infrastructure to provide a reliable and traceable acknowledgment mechanism.
[0105] The method [400] further comprises deleting, by a processing unit [216],
5 stored data corresponding to the multipart message from the database [104] after
successful transmission to the recipient. Post-transmission, it is essential that the data footprint of the completed transaction is minimized to prevent unnecessary storage consumption and to mitigate any potential risks of data breaches or privacy concerns. Furthermore, the processing unit [216] performs integrity checks by
10 performing validations on each part of the multipart message. The processing unit
[216] verify the checksum or compute hash validations for each message segment. The verification process is a safeguard that ensures the data’s integrity has been maintained throughout its journey from sender to recipient. If any discrepancies are detected during this process, the system can take predefined actions to address
15 them, which might include requesting a retransmission of the message part or
alerting a system administrator. Thus, the processing unit [216] not only enhances the operational efficiency of the system but also fortifies the trustworthiness of the communication process within the IMS network.
20 [0106] The method terminates at step [414].
[0107] FIG. 5 illustrates an exemplary block diagram of a computing device (also, referred to herein as computer system [500]) upon which an embodiment of the present disclosure may be implemented. In an implementation, the computing
25 device implements the method for consolidating distributed multipart messages in
IPSMGW clusters using the system [200]. In another implementation, the computing device itself implements the method for provisioning and registration of a network node by using one or more units configured within the computing device, wherein said one or more units are capable of implementing the features as
30 disclosed in the present disclosure.
32

[0108] The computing device [500] may include a bus [502] or other
communication mechanism for communicating information, and a processor [504]
coupled with bus [502] for processing information. The processor [504] may be, for
5 example, a general-purpose microprocessor. The 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
10 during execution of the instructions to be executed by the 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
15 storage device coupled to the bus [502] for storing static information and
instructions for the processor [504].
[0109] 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
20 instructions. The computing device [500] may be coupled via the bus [502] to a
display [512], such as a cathode ray tube (CRT), for displaying information to a computer user. An input device [514], including alphanumeric and other keys, may be coupled to the bus [502] for communicating information and command selections to the processor [504]. Another type of user input device may be a cursor
25 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 inputs 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 the device to specify positions in a plane.
30
33

[0110] The computing device [500] may implement the techniques described
herein using customized hard-wired logic, one or more Application-Specific
Integrated Circuits (ASICs) or Field Programmable Gate Arrays (FPGAs),
firmware and/or program logic which in combination with the computing device
5 [500] causes or programs the computing device [500] to be a special-purpose
machine. According to one embodiment, 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
10 medium, such as the storage device [510]. Execution of the sequences of
instructions contained in the main memory [506] causes the processor [504] to perform the process steps described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions.
15 [0111] 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 a modem to provide a data
20 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, electromagnetic or optical signals that carry digital data streams
25 representing various types of information.
[0112] The computing device [500] can send messages and receive data, including
program code, through the network(s), the network link [520] and the communication
interface 518. In the Internet example, a server [530] might transmit a requested code for
30 an application program through the Internet [528], the Internet Service Provider (ISP)
[526], the local network [522], host [524] and the communication interface [518]. The
34

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.
[0113] The computing device [500] encompasses a wide range of electronic devices
5 capable of processing data and performing computations. Examples of computing device
[500] include, but are not limited only to, personal computers, laptops, tablets,
smartphones, servers, and embedded systems. The devices may operate independently or
as part of a network and can perform a variety of tasks such as data storage, retrieval, and
analysis. Additionally, computing device [500] may include peripheral devices, such as
10 monitors, keyboards, and printers, as well as integrated components within larger electronic
systems, showcasing their versatility in various technological applications.
[0114] FIG. 6 illustrates an exemplary block diagram of a user equipment [UE]
[602] for consolidating distributed multipart messages in IP Short Message
15 Gateway (IPSMGW) clusters.
[0115] As illustrated, the present disclosure provides the UE [602] for
consolidating distributed multipart messages in IP Short Message Gateway
(IPSMGW) clusters. This is a vital component in the communication process,
20 particularly for ensuring the integrity of multipart messages sent across an IMS
network. The UE includes a processor [602A] and a memory [602B], for controlling the transmission and consolidation of multipart messages.
[0116] The processor [602A] is configured to According to another aspect of the
25 present disclosure, a user equipment (UE) for consolidating distributed multipart
messages in IP Short Message Gateway (IPSMGW) clusters is disclosed. The UE
comprising: a processor configured to: send multi-part message to a first IPSMGW
having a first IP address, wherein a consolidated multipart message is received at a
recipient, and wherein the multipart message is consolidated based on: storing, via
30 the first IPSMGW, a set of data corresponding to a first part of the multipart
35

message into a database; in an event one or more subsequent parts of the multipart
message are received at a second IPSMGW having a second IP address: querying,
via the second IPSMGW, the database to locate the set of data associated with the
first IP address; and storing, via the second IPSMGW, the set of data corresponding
5 to the one or more subsequent parts into the database, and associating the set of data
with the first IP address of the first IPSMGW; upon receiving all parts of the multipart message or upon expiration of a pre-set time period, consolidating, via the first IPSMGW, by arranging each part of the multipart message according to a sequence number within the multipart message. An aspect of the present disclosure
10 provides a non-transitory computer-readable storage medium storing instruction for
consolidating multipart messages, the storage medium comprising executable code which, when executed by one or more units of a system, causes: a receiving unit [202] to receive, via a first IPSMGW [102A] having a first IP address, a first part of a multipart message transmitted by a sender over an IP Multimedia Subsystem
15 (IMS) network; a first storing unit [206A] to store via the first IPSMGW [102A], a
set of data corresponding to the first part of the multipart message into a database [104]; in an event one or more subsequent parts of the multipart message are received at a second IPSMGW [102B] having a second IP address: a querying unit [208] to query, via the second IPSMGW [102B], the database [104] to locate the
20 set of data associated with the first IP address; and a second storing unit [206B] to
store via the second IPSMGW [102B], the set of data corresponding to the one or more subsequent parts into the database [104], and associating the set of data with the first IP address of the first IPSMGW [102A]; upon receiving all parts of the multipart message or upon expiration of a pre-set time period, a consolidation unit
25 [210] to consolidate via the first IPSMGW [102A], by arranging each part of the
multipart message.
[0117] By introducing a mechanism for coordinating the reception, storage, and
consolidation of multipart messages across different IPSMGWs, the present
30 disclosure ensures that all parts of a multipart message are received and processed
36

at the same IPSMGW, thereby eliminating the issue of fragmented handling. This
approach ensures consistent message delivery, with all parts of the message arriving
at the recipient in the correct order and without delay. Furthermore, the present
disclosure reduces resource inefficiencies by centralizing the management of
5 multipart messages. By storing and consolidating message parts in a single
IPSMGW, redundant processing and storage across multiple IPSMGWs are minimized, leading to more efficient use of network resources and reduced operational costs. The use of a database, such as a Redis database, for storing message parts and associating them with a unique identifier ensures efficient
10 tracking and retrieval of message parts, simplifying troubleshooting and enhancing
the reliability of message delivery. The present disclosure also addresses the risk of message loss by ensuring that all parts of a multipart message are consolidated at a single IPSMGW before delivery to the recipient. This reduces the likelihood of incomplete or undeliverable messages due to lost or unprocessed parts.
15 Additionally, the system's ability to adjust the pre-set time period for message
consolidation based on network conditions or usage patterns further enhances the scalability and adaptability of the messaging infrastructure.
[0118] Further, in accordance with the present disclosure, it is to be acknowledged
20 that the functionality described for the various the 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
25 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.
30 [0119] While considerable emphasis has been placed herein on the disclosed
embodiments, it will be appreciated that many embodiments can be made and that
37

many changes can be made to the embodiments without departing from the principles of the present disclosure. These and other changes in the embodiments 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.

We Claim:
1. A method for consolidating multipart messages, the method comprising the
steps of:
receiving, by a receiving unit [202] via a first IPSMGW [102A] having a first IP address, a first part of a multipart message transmitted by a sender over an IP Multimedia Subsystem (IMS) network;
storing, by a first storing unit [206A] via the first IPSMGW [102A], a set of data corresponding to the first part of the multipart message into a database [104];
in an event one or more subsequent parts of the multipart message are received at a second IPSMGW [102B] having a second IP address:
querying, by a querying unit [208] via the second IPSMGW
[102B], the database [104] to locate the set of data associated with the
first IP address; and
storing, by a second storing unit [206B] via the second IPSMGW
[102B], the set of data corresponding to the one or more subsequent
parts into the database [104], and associating the set of data with the
first IP address of the first IPSMGW [102A]; and
upon receiving all parts of the multipart message or upon expiration of a pre-set time period, consolidating, by a consolidation unit [210] via the first IPSMGW [102A], by arranging each part of the multipart message.
.
2. The method as claimed in claim 1, wherein the method comprises formatting, by a formatting unit [212] via the first IPSMGW [102A], the consolidated multipart message into a single short message service (SMS) message compliant with the SMS over IMS standard.
3. The method as claimed in claim 1, wherein the method comprises generating, by a generating unit [214], an alert acknowledging receipt of the multipart message by a recipient.

4. The method as claimed in claim 3, wherein the alert acknowledging receipt is transmitted back to the sender via the first IPSMGW [102A].
5. The method as claimed in claim 1, wherein the database [104] stores a key value pair, wherein a message identifier (ID) represents a key and the IP address of the IPSMGW represents a value of the key value pair.
6. The method as claimed in claim 5, wherein the message identifier (ID) is used for querying the database [104], the message ID is a unique ID for the multipart message.
7. The method as claimed in claim 3, further comprises deleting, by a processing unit [216], stored data corresponding to the multipart message from the database [104] after successful transmission to the recipient.
8. The method as claimed in claim 1, wherein the consolidation of each part of the multipart message comprises checking, by a processing unit [216], at least one of a checksum, and a hash validation of each part of the multipart message to ensure data integrity.
9. The method as claimed in claim 1, wherein the pre-set time period is adjustable based on one of a network condition or a usage pattern.
10. The method as claimed in claim 1, wherein consolidation by arranging each part of the multipart message is based according to at least one of a sequence number and a timestamp associated with the multipart message.
11. The method as claimed in claim 1, transmitting, by a transmitting unit [204] via the first IPSMGW [102A], the consolidated multipart message to a recipient.
12. A system for consolidating multipart messages, the system comprising:
a receiving unit [202] configured to receive, via a first IPSMGW [102A] having a first IP address, a first part of a multipart message transmitted by a sender over an IP Multimedia Subsystem (IMS) network;

a first storing unit [206A] configured to store via the first IPSMGW [102A], a set of data corresponding to the first part of the multipart message into a database [104];
in an event one or more subsequent parts of the multipart message are received at a second IPSMGW [102B] having a second IP address:
a querying unit [208] configured to query, via the second IPSMGW [102B], the database [104] to locate the set of data associated with the first IP address;
a second storing unit [206B] configured to store via the second IPSMGW [102B], the set of data corresponding to the one or more subsequent parts into the database [104], and associating the set of data with the first IP address of the first IPSMGW [102A]; and upon receiving all parts of the multipart message or upon expiration of a pre-set time period, a consolidation unit [210] configured to consolidate via the first IPSMGW [102A], by arranging each part of the multipart message.
13. The system as claimed in claim 12, wherein the system comprises a formatting unit [212] configured to format, via the first IPSMGW [102A], the consolidated multipart message into a single short message service (SMS) message compliant with the SMS over IMS standard.
14. The system as claimed in claim 12, wherein the system comprises a generating unit [214] configured to generate an alert acknowledging receipt of the multipart message by a recipient.
15. The system as claimed in claim 14, wherein the alert acknowledging receipt is transmitted back to the sender via the first IPSMGW [102A].
16. The system as claimed in claim 12, wherein the database [104] stores a key value pair, wherein a message identifier (ID) represents a key of the key value pair and the IP address of the IPSMGW represents a value of the key value pair.

17. The system as claimed in claim 16, wherein the message identifier (ID) is used for querying the database [104], the message ID is a unique ID for the multipart message.
18. The system as claimed in claim 14, comprises a processing unit [216] configured to delete stored data corresponding to the multipart message from the database [104] after successful transmission to4.
19. The system as claimed in claim 12, wherein for the consolidation of each part of the multipart message, a processing unit [216] is configured to check at least one of a checksum, and a hash validation of each part of the multipart message to ensure data integrity.
20. The system as claimed in claim 12, wherein the pre-set time period is adjustable based on one of a network condition or a usage pattern.
21. The system as claimed in claim 12, wherein consolidation by arranging each part of the multipart message is based according to at least one of a sequence number and a timestamp associated with the multipart message.
22. The system as claimed in claim 12, wherein a transmitting unit [204] via the first IPSMGW [102A] is configured to transmit the consolidated multipart message to a recipient.
23. A user equipment (UE) [602] for consolidating multipart messages, the UE [602] comprising:
a processor [602A] configured to:
send multi-part message to a first IPSMGW [102A] having a first IP address, wherein a consolidated multipart message is received at a recipient, and wherein the multipart message is consolidated based on:
storing, via the first IPSMGW [102A], a set of data corresponding to a first part of the multipart message into a database [104];
in an event one or more subsequent parts of the multipart message are received at a second IPSMGW [102B] having a second IP address:

querying, via the second IPSMGW [102B], the database [104] to locate the set of data associated with the first IP address;
storing, via the second IPSMGW [102B], the set of data corresponding to the one or more subsequent parts into the database [104], and associating the set of data with the first IP address of the first IPSMGW [102A]; and
upon receiving all parts of the multipart message or upon expiration of a pre-set time period, consolidating, via the first IPSMGW [102A], by arranging each part of the multipart message according to a sequence number within the multipart message.
24. The UE [602] as claimed in claim 23, wherein the processor [602A] is configured to transmit, via the first IPSMGW [102A], the consolidated multipart message to a recipient.

Documents

Application Documents

# Name Date
1 202321047789-STATEMENT OF UNDERTAKING (FORM 3) [15-07-2023(online)].pdf 2023-07-15
2 202321047789-PROVISIONAL SPECIFICATION [15-07-2023(online)].pdf 2023-07-15
3 202321047789-FORM 1 [15-07-2023(online)].pdf 2023-07-15
4 202321047789-FIGURE OF ABSTRACT [15-07-2023(online)].pdf 2023-07-15
5 202321047789-DRAWINGS [15-07-2023(online)].pdf 2023-07-15
6 202321047789-FORM-26 [18-09-2023(online)].pdf 2023-09-18
7 202321047789-Proof of Right [10-10-2023(online)].pdf 2023-10-10
8 202321047789-ORIGINAL UR 6(1A) FORM 1 & 26)-011223.pdf 2023-12-08
9 202321047789-FORM-5 [12-07-2024(online)].pdf 2024-07-12
10 202321047789-ENDORSEMENT BY INVENTORS [12-07-2024(online)].pdf 2024-07-12
11 202321047789-DRAWING [12-07-2024(online)].pdf 2024-07-12
12 202321047789-CORRESPONDENCE-OTHERS [12-07-2024(online)].pdf 2024-07-12
13 202321047789-COMPLETE SPECIFICATION [12-07-2024(online)].pdf 2024-07-12
14 202321047789-FORM 3 [02-08-2024(online)].pdf 2024-08-02
15 Abstract-1.jpg 2024-08-16
16 202321047789-Request Letter-Correspondence [16-08-2024(online)].pdf 2024-08-16
17 202321047789-Power of Attorney [16-08-2024(online)].pdf 2024-08-16
18 202321047789-Form 1 (Submitted on date of filing) [16-08-2024(online)].pdf 2024-08-16
19 202321047789-Covering Letter [16-08-2024(online)].pdf 2024-08-16
20 202321047789-CERTIFIED COPIES TRANSMISSION TO IB [16-08-2024(online)].pdf 2024-08-16