System and method for efficiently handling retransmission requests in an IP multimedia subsystem (IMS) network

Abstract

The present disclosure relates to systems and methods for efficiently handling retransmission requests in an IP Multimedia Subsystem (IMS) network The method [400] encompasses receiving a request associated with a subscriber. The method encompasses extracting a metadata associated with the subscriber from the received request. The method [400] encompasses mapping the received request and the extracted metadata associated with the subscriber storing the mapped request and the metadata associated with the subscriber in a data collection system [214]. The data collection system [214] comprises at least two map data structures, and matching metadata associated with subsequent request associated with the subscriber with the metadata associated with the subscriber stored in the data collection system [214]. The method [400] encompasses rejecting the subsequent request based on a positive matching of the subsequent request associated with the subscriber with the metadata associated with the subscriber stored in the data collection system [214].

Description

SYSTEM AND METHOD FOR EFFICIENTLY HANDLING RETRANSMISSION REQUESTS IN AN IP MULTIMEDIA SUBSYSTEM (IMS) NETWORKFIELD OF THE DISCLOSURE

[0001] The present disclosure relates generally to the field of wireless communication systems. In particular, the present disclosure relates to IP Multimedia Subsystem (IMS) networks. More particularly, the present disclosure relates to a system and method for efficiently handling retransmission requests in an IP Multimedia Subsystem (IMS) network.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. The third Generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.

[0004] Traditional systems may struggle with the simultaneous receipt of identical register requests or retransmitted messages with the same headers. These redundant requests can significantly increase application processing times, impacting system performance and efficiency. Systems without an efficient way to handle retransmissions may end up wasting valuableresources. For instance, running extra timers to manage repeated register requests can use up computational resources that could be better utilized elsewhere. Existing systems that do not effectively manage duplicated or retransmitted messages may face scalability issues. As the volume of requests increases, the system's ability to process them efficiently may decrease. The inability to identify and reject repeated transmission requests could lead to the unnecessary handling of identical requests, reducing the system's overall efficiency and potentially delaying the processing of unique requests. Current methods do not have an efficient data management system to handle the volume of incoming requests. This could lead to a rapid filling of storage space, affecting the performance of the system and making it prone to errors or slowdowns.

[0005] Therefore, in light of 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 dynamic retransmission control for optimized application processing in IP Multimedia Subsystem (IMS) networks.OBJECTS OF DISCLOSURE

[0007] Some of the objects of the present disclosure, which at least one implementation disclosed herein satisfies are listed herein below.

[0008] It is an object of the present disclosure to provide a system and method for efficiently handling retransmission requests in Internet Protocol Multimedia Subsystem (IMS) networks.

[0009] It is an object of the present disclosure to provide a solution that enhance the processing efficiency of an Internet Protocol Multimedia Subsystem (IMS) network by effectively managing and controlling redundant or repeated register requests.

[0010] It is an object of the present disclosure to provide a solution that optimize resource usage by eliminating the need to run extra timers for handling retransmissions thereby saving computational resources.

[0011] It is an object of the present disclosure to provide a solution that improves the overall scalability of the IMS network, and efficiently handle retransmissions by identifying and rejecting repeated register requests.

[0012] It is yet another object of the present disclosure to provide a solution that introduce a dynamic dual-map data management system for handling incoming requests.SUMMARY OF DISCLOSURE

[0013] 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.

[0014] A first aspect of the present disclosure is related to a method for efficiently handling retransmission requests in an IP Multimedia Subsystem (IMS) network. The method comprises receiving, by a transceiver unit associated with an Internet Protocol short message gateway (IPSMGW), a request associated with a subscriber. Further, the method encompasses extracting, by an extraction unit associated with the IPSMGW, a metadata associated with the subscriber from the received request. Further, the method comprising mapping, by a mapping unit associated with the IPSMGW, the received request and the extracted metadata associated with the subscriber. Further, the method comprising storing, by a storage unit associated with the IPSMGW, the mapped request and the metadata associated with the subscriber in a data collection system, the data collection system comprises at least two map data structures. Thereafter, the method comprising matching, by a comparator unit associated with the IPSMGW, a metadata associated with a subsequent request associated with the subscriber with the metadata associated with the subscriber stored in the data collection system. Thereafter, the method comprises rejecting, by a processing unit associated with the IPSMGW, the subsequent request based on a positive matching of the subsequent request associated with the subscriber with the metadata associated with the subscriber stored in the data collection system.

[0015] According to another aspect of the present disclosure, the method further comprises verifying, by the processing unit, a validity of a sender phone number and a recipient phone number by cross-referencing an authorized numbers database.

[0016] According to another aspect of the present disclosure, the metadata associated with the subscriber at least comprises a header and a Mobile Station International Subscriber Directory Number (MSISDN).

[0017] According to another aspect of the present disclosure, the method further comprises purging, by the processing unit, contents of a first map in the data collection system once a second map is full and preparing the first map for new incoming requests.

[0018] According to another aspect of the present disclosure, the request is any or a combination of one or more messages and one or more registration requests.

[0019] According to another aspect of the present disclosure, the method further comprises generating, by the processing unit, an alert acknowledging receipt of the one or more messages by a recipient.

[0020] According to another aspect of the present disclosure, the method further comprises transmitting, by the transceiver unit, the alert acknowledging receipt to a sender.

[0021] According to another aspect of the present disclosure, the method further comprises deleting, by the processing unit, a stored data corresponding to each of the one or more messages from the map data structure after a successful transmission to the recipient.

[0022] According to another aspect of the present disclosure, each of the handling of the retransmission requests in the IP Multimedia Subsystem (IMS) network is performed by the IP short message gateway (IPSMGW).

[0023] Another aspect of the present disclosure relates to a system for efficiently handling retransmission requests in an IP Multimedia Subsystem (IMS) network. The system comprises at least a transceiver unit, an extraction unit, a mapping unit, a storage unit, a comparator unit, and a processing unit, associated with an IP short message gateway (IPSMGW), connected to each other. The transceiver unit is configured to receive, a request associated with a subscriber. The extraction unit is configured to extract, a metadata associated with the subscriber from the received request. The mapping unit is configured to map, the received request and the extracted metadata associated with the subscriber. Further, the storage unit is configured to store, the mapped request and the metadata associated with the subscriber in a data collection system, the data collection systemcomprises at least two map data structures. The comparator unit is configured to match, a metadata associated with a subsequent request, associated with the subscriber, with the metadata associated with the subscriber stored in the data collection system. Furthermore, the processing unit is configured to reject, the subsequent request based on a positive matching of the subsequent request associated with the subscriber with the metadata associated with the subscriber stored in the data collection system.

[0024] Another aspect of the present disclosure relates to a non-transitory computer readable storage medium storing one or more instructions for efficiently handling retransmission requests in an IP Multimedia Subsystem (IMS) network. The one or more instructions comprises executable code which when executed by one or more units of a system, causes the one or more units to perform certain functions. The one or more instructions when executed further causes a transceiver unit of the system to receive a request associated with a subscriber. The one or more instructions when executed further causes an extraction unit of the system to extract a metadata associated with the subscriber from the received request. The one or more instructions when executed further causes a mapping unit of the system to map the received request and the extracted metadata associated with the subscriber. The one or more instructions when executed further causes a storage unit of the system to store the mapped request and the metadata associated with the subscriber in a data collection system, the data collection system comprises at least two map data structures. The one or more instructions when executed further causes a comparator unit of the system to match a metadata associated with a subsequent request, associated with the subscriber, with the metadata associated with the subscriber stored in the data collection system. The one or more instructions when executed further causes a processing unit of the system to reject the subsequent request based on a positive matching of the subsequent request associated with the subscriber with the metadata associated with the subscriber stored in the data collection system.BRIEF DESCRIPTION OF DRAWINGS

[0025] 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 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 bythose skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.

[0026] FIG.1 illustrates a system architecture of internet protocol (IP) short message gateway clusters, in accordance with exemplary implementations of the present disclosure.

[0027] FIG.2 illustrates an exemplary block diagram of a system for efficiently handling retransmission requests in an IP Multimedia Subsystem (IMS) network, in accordance with exemplary implementations of the present disclosure.

[0028] FIG.3 illustrates an exemplary block diagram of a system architecture for efficiently handling retransmission requests in an IP Multimedia Subsystem (IMS) network, in accordance with exemplary implementations of the present disclosure.

[0029] FIG.4 illustrates an exemplary method flow diagram indicating the process for efficiently handling retransmission requests in an IP Multimedia Subsystem (IMS) network, in accordance with exemplary implementations of the present disclosure.

[0030] 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.

[0031] The foregoing shall be more apparent from the following more detailed description of the disclosure.DETAILED DESCRIPTION

[0032] 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 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 of the present disclosure are described below, asillustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.

[0033] The ensuing description provides exemplary implementations only, and is 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 of the disclosure as set forth.

[0034] 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 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 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.

[0035] 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 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.

[0036] 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. A process is terminated when its operations are completed but could have additional steps not included in a figure.

[0037] The word “exemplary” and / or “demonstrative” is used herein to mean 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 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.

[0038] 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 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 Energy, Near Field Communication, Z-Wave, Wireless Fidelity (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 the art for implementation of the features of the present disclosure.

[0039] 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 special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, 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.

[0040] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.

[0041] 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 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.

[0042] Radio Access Technology (RAT) refers to the technology used by mobile devices / user equipment (UE) to connect to a cellular network. The RAT 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 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 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.

[0043] As used herein “gNodeB” (gNB) refers to the base station component in 5G (fifth generation) wireless networks. It is an essential element of the Radio Access Network (RAN) responsible for transmitting and receiving wireless signals to and from user devices, such as smartphones, tablets, and Internet of Things (loT) devices. In 5G networks, there are similar components in other generations of wireless networks. Here are a few examples of base stations in other generations of wireless networks such as a Base Transceiver Station (BTS), NodeB,eNodeB, and an Access Point (AP). The Base Transceiver Station (BTS) exists in 2G (second generation) networks and serves as the base station responsible for transmitting and receiving wireless signals. It connects mobile devices to the cellular network infrastructure. Further, NodeB exists in 3G (third generation) networks and refers to the base station component that enables wireless communication. It facilitates the transmission and reception of signals between user devices and the network. Also, eNodeB exists in 4G (fourth generation) LTE (Long-Term Evolution) networks. The eNodeB serves as the base station. It supports high-speed data transmission, low latency, and improved network capacity. In addition, the Access Point (AP) exists in Wi-Fi networks. The Access Point functions as a central hub that enables wireless devices to connect to a wired network. It provides a wireless interface for devices to access the network and facilitates communication between them. The examples illustrate the base station components in different generations of wireless networks, such as BTS in 2G, NodeB in 3G, eNodeB in 4G LTE, and gNodeB in 5G. Each component plays a crucial role in facilitating wireless connectivity and communication between user devices and the network infrastructure.

[0044] As discussed in the background section, traditional systems may struggle with the simultaneous receipt of identical register requests or retransmitted messages with the same headers. These redundant requests can significantly increase application processing time, thus impacting system’s performance and efficiency. Systems without an efficient way to handle retransmission requests that processes identical register requests or retransmitted messages, may end up wasting valuable resources by way of running extra timers to manage repeated register requests. This further uses up computational resources that could be better utilized elsewhere. Existing systems fail to effectively manage duplicated or retransmitted messages and may also face scalability issues. As the volume of requests increases, the system's ability to process them efficiently may also decrease. Therefore, the inability of a system to identify and reject repeated transmission requests could lead to the unnecessary handling of identical requests, thereby reducing the system's overall efficiency and potentially delaying the processing of unique requests. Furthermore, since the current methods might not have an efficient data management system to handle the volume of incoming requests, this could lead to a rapid filling of storage space, impacting the system performance and making it prone to errors or slowdowns.

[0045] To overcome the problems discussed above, the present disclosure provides a solution comprising a dynamic retransmission control for optimized application processing in an IP Multimedia Subsystem (IMS) network. The present disclosure addresses these issues by using a system with multiple maps which reduces processing time, conserve resources, improvesscalability, and optimizes retransmission handling in the IMS networks. The present disclosure provides a solution that maps a subsequent request or message associated with a subscriber and then determining whether said subsequent request is a redundant request. Thereafter, based upon the determination, the present disclosure enables rejection of the redundant request and prevents initiation of an extra timer for the redundant request. The present disclosure further discloses storing new register requests or messages in a second map of the multiple map system upon a first map reaching a storage limit. The present disclosure further discloses removing data from the first map, continuing the storing of new requests or messages in the second map, and enabling a continuous cyclical data management process, upon the second map reaching the storage limit.

[0046] Hereinafter, exemplary implementations of the present disclosure will be described with reference to the accompanying drawings.

[0047] FIG. 1 illustrates an exemplary architecture diagram

[0100] of an Internet Protocol Short Message Gateway (IPSMGW)

[0102] , for optimising a short message service (SMS) barring service is built, in accordance with exemplary implementations of the present disclosure. The architecture diagram

[0100] of the IPSMGW

[0102] comprising an Element Management System (EMS)

[0104] , a Signalling Transfer Point (STP)

[0106] , a Serving-Call Session Control Function (SCSCF)

[0112] , a F5 Load Balancer

[0126] , a Diameter Routing Agent (DRA)

[0132] , a Short Message Peer-to-Peer (SMPP)

[0120] , an SMPP Charging Point (CP)

[0128] , a Mobile Number Portability (MNP)

[0130] , an Online Charging System (OCS)

[0134] , a Home Subscriber Server (HSS)

[0136] , a Service Capability Exposure Function (SCEF)

[0138] , a Mobility Management Entity (MME)

[0140] , a Database

[0114] , a Transmission Control Protocol (TCP)

[0118] , a Mobile Application Part (MAP)

[0110] , a Representational State Transfer (REST)

[0108] , and a Session Initiation Protocol (SIP)

[0116] , Also, all the components / units of the system

[0100] are assumed to be connected to each other unless otherwise indicated below.

[0048] IPSMGW (IP Short Message Gateway)

[0102] : A network element responsible for handling and routing Short Message Service (SMS) messages over IP networks.

[0049] EMS (Element Management System)

[0104] : A software system used for managing and monitoring network elements or devices within a telecommunications network.

[0050] STP (Signalling Transfer Point)

[0106] : A network node used in the SS7 (Signalling System No. 7) telecommunications protocol to route signalling messages between signalling endpoints.

[0051] SCSCF (Serving-Call Session Control Function)

[0112] : A core component in IMS (IP Multimedia Subsystem) networks responsible for session control and call processing.

[0052] F5 Load Balancer

[0126] : A device or software component that evenly distributes incoming network traffic across multiple servers to optimize resource utilization, reliability, and performance.

[0053] DRA (Diameter Routing Agent)

[0132] : A network element responsible for routing Diameter

[0124] protocol messages within telecommunications networks, often used in IMS and LTE networks.

[0054] SMPP (Short Message Peer-to-Peer)

[0120] : A protocol used in the telecommunications industry for exchanging SMS messages between Short Message Service Centres (SMSCs) and SMS application systems.

[0055] SMPP CP (SMPP Charging Point)

[0128] : A network element responsible for charging and billing functions within a telecommunications network.

[0056] MNP (Mobile Number Portability)

[0130] : A service that allows mobile phone users to retain their phone numbers when switching between different service providers.

[0057] OCS (Online Charging System)

[0134] : A system used for real-time charging and billing of telecommunications services, such as voice calls, data usage, and SMS messages.

[0058] HSS (Home Subscriber Server)

[0136] : A core component in LTE and IMS networks that stores subscriber-related information, such as user profiles, authentication data, and service subscriptions.

[0059] SCEF (Service Capability Exposure Function)

[0138] : A component in IMS networks that exposes network capabilities to application servers, enabling the creation of innovative multimedia services.

[0060] MME (Mobility Management Entity)

[0140] : A key component in LTE networks responsible for managing the mobility of mobile devices, including tracking their location and handling handovers between base stations.

[0061] Database

[0114] : A structured collection of data organized for efficient storage, retrieval, and management. The structured collection of data comprises a map data structure.

[0062] TCP (Transmission Control Protocol)

[0118] : A reliable, connection-oriented protocol used for transmitting data over networks.

[0063] MAP (Mobile Application Part)

[0110] : A protocol used in cellular networks for communication between various network elements, such as HLRs (Home Location Registers) and VLRs (Visitor Location Registers).

[0064] REST (Representational State Transfer)

[0108] : An architectural style for designing networked applications, commonly used in web services development.

[0065] SIP (Session Initiation Protocol)

[0116] : 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

[0116] allows devices to establish communication sessions and negotiate the parameters of the session, such as codecs, media types, and session duration.

[0066] FIG. 2 illustrates an exemplary block diagram of a system

[0200] for efficiently handling retransmission requests in an IP Multimedia Subsystem (IMS) network, in accordance with exemplary implementations of the present disclosure. The system

[0200] comprises at least one transceiver unit

[0202] , at least one extraction unit

[0204] , at least one mapping unit

[0206] , at least one storage unit

[0208] , at least one comparator unit

[0210] , and at least one processing unit

[0212] , All of the components as shown in the block diagram are connected to each other. All of the components as mentioned in the block diagram lies within the system

[0200] and shall be considered to be interconnected with each other. Also, in Fig. 2 only a few units are shown, however, the system

[0200] may comprise multiple such units or the system

[0200] may comprise any such numbers of said units, as required to implement the features of the present disclosure. The system

[0200] may in communication with the user device (may also referred herein as a UE). The present disclosure further discloses that the system

[0200] may reside in a server and / or a network entityand the system

[0200] and may also reside partly in the server / network entity. The retransmission requests may refer to the requests for the retransmission of data packets which were not successfully received or were lost during transmission of the message. The IMS network is a framework which is used to deliver multimedia services over Internet Protocol networks. The transceiver unit

[0202] may be a device capable of transmission and reception of data and / or signals. The extraction unit

[0204] may be a processor capable of extracting a target data from a set of data. The mapping unit

[0206] may be a processor capable of mapping one or more data and / or data fields with other data and / or data fields. The storing unit

[0208] may be a memory device or memory unit capable of storing information in a desired format. The comparator unit

[0210] may be a processor capable of comparing one more set of data with each other. The processing unit

[0212] may be a processor capable of producing an output based on an input.

[0067] The present disclosure further discloses that each of the handling of the retransmission requests in the IP Multimedia Subsystem (IMS) network is performed by the IP short message gateway (IPSMGW)

[0102] ,

[0068] The transceiver unit

[0202] , associated with the Internet Protocol Short Message Gateway (IPSMGW)

[0102] , is configured to receive a request associated with a subscriber. The request associated with a subscriber may be any or a combination of one or more messages and one or more registration requests from the subscriber. The subscriber could be a user device or another node in the network trying to subscribe to the IPSMGW

[0102] , The one or more messages may refer to a message containing distinct content or data in multiple parts or sections. The one or more registration requests may be a request for registering the subscriber to the IMS network or the IPSMGW

[0102] , The processing unit

[0212] is further configured to generate an alert acknowledging receipt of the one or more messages by a recipient. The alert acknowledging receipt may be an acknowledgement / confirmation that the one or more messages have been received by the recipient of the one or more messages. The recipient may be the subscriber to which the one or more messages has been sent.

[0069] The present disclosure further discloses that the transceiver unit

[0202] is further configured to transmit the alert acknowledging receipt to a sender. The sender may be the subscriber who is sending the one or more messages to the recipient.

[0070] The present disclosure further discloses that the processing unit

[0212] is further configured to delete a stored data corresponding to each of the one or more messages from the map datastructure after a successful transmission to the recipient. The successful transmission may refer to an event where the alert acknowledging receipt has been successfully sent by the recipient to the sender.

[0071] The extraction unit

[0204] connected at least to the transceiver unit

[0202] , Further, the extraction unit

[0204] associated with the IPSMGW

[0102] is configured to extract a metadata associated with the subscriber from the received request. The present disclosure further discloses that the metadata associated with the subscriber at least comprises a header and a Mobile Station International Subscriber Directory Number (MSISDN). The said metadata associated with the subscriber may also contain one or more data fields associated with the subscriber along with the header and the Mobile Station International Subscriber Directory Number (MSISDN). The header may refer to a “via header” (known in the art), which identifies a path of the transaction for routing the one or more messages and the one or more registration requests. The MSISDN may be a unique identifier associated with each user device worldwide and may be correlated with a mobile number associated with said user device.

[0072] The present disclosure further discloses that the processing unit

[0212] may also be further configured to verify a validity of a sender phone number and a recipient phone number by crossreferencing an authorized numbers database. The validity may refer to existence of the sender phone number or the recipient phone number within the authorized numbers database. The sender phone number may refer to a phone number or a MSISDN of a subscriber or a user device sending the request. The receiver phone number may refer to a phone number or a MSISDN of a subscriber or a user device to whom the message is being sent. An authorised numbers database may refer to a database comprising information of all registered MSISDNs that are authorised or permitted to access services or resources within a telecommunication network.

[0073] Further, the mapping unit

[0206] associated with the IPSMGW

[0102] is configured to map the received request and the extracted metadata associated with the subscriber. For mapping the received request and the extracted metadata, a key and a value are paired with each other. After the pairing of the key and the value, a key-value pair is stored in the storage unit

[0208] , The key may be the header and the MSISDN. The value may be the one or more messages and may also be a timestamp for the one or more registration requests.

[0074] Further, the storage unit

[0208] associated with the IPSMGW

[0102] is configured to store the mapped request and the metadata associated with the subscriber in a data collection system

[0214] , The data collection system

[0214] may refer to a setup comprising at least two map data structures for collecting a data. The at least two map data structures may, for example, be a relational map data structure, and a non-relational map data structure. The non-relational map data structure may include key-value, graph, documents, column-based structures, etc.

[0075] The processing unit

[0212] is further configured to purge contents of a first map in the data collection system

[0214] once a second map is full and preparing the first map for new incoming requests. The first map may refer to one of the map data structures from the data collection system

[0214] , and the second map may also refer to another map data structure from the data collection system

[0214] , In a scenario, when the second map reaches its maximum capacity or storage limit, the contents of the first map are removed or deleted to manage storage resources efficiently by freeing up space in the first map. The new incoming requests may refer to the requests which may come in future from other subscribers. This ensures that the system

[0200] can continue to receive and process the new requests, even when the first map is full. This continuous, cyclical data management ensures efficient handling of the incoming requests, enabling smooth and optimized operation of the IMS network. This dynamic management of data between the two maps allows the system

[0200] to effectively handle high volumes of incoming requests without overloading its storage capacity.

[0076] The present disclosure further discloses that the transceiver unit

[0202] may be further configured to receive a subsequent request associated with the subscriber and then the extraction unit

[0204] may be further configured to extract a metadata associated with the subsequent request. The subsequent request may be the request associated with the subscriber which is retransmitted due to packet loss or non-receipt of data packets. The subsequent request may also be another request sent by the subscriber. The metadata associated with the subsequent request may at least comprises the header and the Mobile Station International Subscriber Directory Number (MSISDN).

[0077] Furthermore, the comparator unit

[0210] associated with the IPSMGW

[0102] is configured to match the metadata associated with the subsequent request, associated with the subscriber, with the metadata associated with the subscriber stored in the data collection system

[0214] , Further, a result of the matching of the metadata associated with the subsequent request and the metadata associated with the subscriber may be one of a positive matching or a negative matching. The positive matching shows that the metadata associated with the subsequent request and the metadataassociated with the subscriber are same. The negative matching shows that the metadata associated with the subsequent request and the metadata associated with the subscriber are not same.

[0078] Thereafter, the processing unit

[0212] associated with the IPSMGW

[0102] is configured to reject the subsequent request based on the positive matching of the subsequent request associated with the subscriber, and the metadata associated with the subscriber stored in the data collection system

[0214] , Due to the positive matching of the metadata associated with the subsequent request and the metadata associated with the subscriber showing that the same request has been retransmitted thereby being redundant, the system

[0200] rejects it. This rejection helps in preventing the unnecessary processing of repeated requests. It also stops the initiation of an extra timer, which is typically used to handle retransmissions, thus saving system resources. The subsequent request may also be stored in the data collection system

[0214] ,

[0079] The system architecture

[0200] may also be configured for dynamic retransmission control for optimized application processing in the IMS network.

[0080] In an example, an Internet Protocol Multimedia Subsystem (IMS) network handles millions of register requests or messages daily. These requests originate from multiple senders and contain unique headers and Mobile Station International Subscriber Directory Number (MSISDN). At time Tl, the system

[0200] receives a register request from Sender A with Headerl and MSISDN1. The system

[0200] stores the details of Headerl and MSISDN1 in the first map of the data collection system

[0214] , Now, at time T2, the system

[0200] receives another register request from Sender A with the header, say Headerl and the MSISDN, say MSISDN1. The system

[0200] compares these details with the existing entries in the first map. Since the details match with a previous request, the system

[0200] identifies this as a redundant request. It then rejects this request and prevents the initiation of an extra timer for it, thus saving system resources. If the first map reaches its storage limit at time T3. Now, any new request (say a register request from Sender B with Header2 and MSISDN2) will be stored in the second map of the data collection system

[0214] , At time T4, if the second map reaches its storage limit, the system

[0200] removes the data from the first map (for example, details of Sender A’ s request). The system

[0200] continues to store new requests in the second map, such as a new request from Sender C with Header3 and MSISDN3. This cycle keeps repeating, ensuring continuous, efficient handling of incoming requests.

[0081] FIG.3 illustrates an exemplary method flow diagram

[0300] for efficiently handling retransmission requests in an IP Multimedia Subsystem (IMS) network, in accordance withexemplary implementations of the present disclosure. At step 1, a sender

[0302] sends one or more messages / registration requests to the IPSMGW

[0102] , Then at step 2, the IPSMGW

[0102] may check if the one or more messages / registration requests are a retransmitted request, and if the one or more messages / registration requests are same as earlier request from the sender

[0302] i.e., it is identified by the IPSMGW

[0102] as the retransmitted request, then at step 3, the one or more messages / registration requests are rejected.

[0082] Referring to FIG. 4 an exemplary method flow diagram

[0400] , for efficiently handling retransmission requests in an IP Multimedia Subsystem (IMS) network, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method

[0400] is performed by the server. The retransmission requests may refer to the requests for the retransmission of data packets which were not successfully received or were lost during transmission of a message. The IMS network is a framework which is used to deliver multimedia services over Internet Protocol networks. The method

[0400] may also be performed by the system

[0200] , The present disclosure further discloses that the handling of the retransmission requests in the IMS network is performed by the IPSMGW

[0102] , As shown in FIG. 4, the method

[0400] begins at step

[0402] ,

[0083] At step

[0404] , the method

[0400] comprises receiving, by a transceiver unit

[0202] associated with an Internet Protocol short message gateway (IPSMGW)

[0102] , a request associated with a subscriber. The request associated with a subscriber may be any or a combination of one or more messages and one or more registration requests from the subscriber. The subscriber could be a user device or another node in the network trying to subscribe to the IPSMGW

[0102] , The one or more messages may refer to a message containing distinct content or data in multiple parts or sections. The one or more registration requests may be a request for registering the subscriber to the IMS network or the IPSMGW

[0102] , The present disclosure further discloses generating, by the processing unit

[0212] , an alert acknowledging receipt of the one or more messages by a recipient. The alert acknowledging receipt may be an acknowledgement / confirmation that the one or more messages have been received by the recipient of the one or more messages. The recipient may be the subscriber to which the one or more messages has been sent.

[0084] The present disclosure further discloses transmitting, by the transceiver unit

[0202] , the alert acknowledging receipt to a sender. The sender may be the subscriber who is sending the one or more messages to the recipient.

[0085] The present disclosure further discloses deleting, by the processing unit

[0212] , a stored data corresponding to each of the one or more messages from the map data structure after a successful transmission to the recipient. The successful transmission may refer to an event where the alert acknowledging receipt has been successfully sent by the recipient to the sender.

[0086] At step

[0406] , the method

[0400] comprises extracting, by an extraction unit

[0204] associated with the IPSMGW

[0102] , a metadata associated with the subscriber from the received request. The present disclosure further discloses that the metadata associated with the subscriber at least comprises a header and a Mobile Station International Subscriber Directory Number (MSISDN). The said metadata associated with the subscriber may also contain one or more data fields associated with the subscriber along with the header and the Mobile Station International Subscriber Directory Number (MSISDN). The header may refer to a “via header” (known in the art), which identifies a path of the transaction for routing the one or more messages and the one or more registration requests. The MSISDN may be a unique identifier associated with each user device worldwide and may be correlated with a mobile number associated with said user device.

[0087] The present disclosure further discloses verifying, by the processing unit

[0212] , a validity of a sender phone number and a recipient phone number by cross-referencing an authorized numbers database. The validity may refer to existence of the sender phone number or the recipient phone number within the authorized numbers database. The sender phone number may refer to a phone number or a MSISDN of a subscriber or a user device sending the request. The receiver phone number may refer to a phone number or a MSISDN of a subscriber or a user device to whom the message is being sent. An authorised numbers database may refer to a database comprising information of all registered MSISDNs that are authorised or permitted to access services or resources within a telecommunication network.

[0088] At step

[0408] , the method

[0400] further comprises mapping, by a mapping unit

[0206] associated with the IPSMGW

[0102] , the received request and the extracted metadata associated with the subscriber. For mapping the received request and the extracted metadata, a key and a value are paired with each other. After the pairing of the key and the value, a key -value pair is stored in the storage unit

[0208] , The key may be the header and the MSISDN. The value may be the one or more messages and may also be a timestamp for the one or more registration requests.

[0089] At step

[0410] , the method

[0400] further comprises storing, by a storage unit

[0208] associated with the IPSMGW

[0102] , the mapped request and the metadata associated with thesubscriber in a data collection system

[0214] , The data collection system

[0214] may refer to a setup comprising at least two map data structures for collection of data. The data collection system

[0214] may refer to a setup comprising at least two map data structures for collecting a data. The at least two map data structures may for example, be a relational map data structure, and a non-relational map data structure. The non-relational map data structure may include key-value, graph, documents, column-based structures, etc.

[0090] The method

[0400] further comprises purging, by the processing unit

[0212] , contents of a first map in the data collection system

[0214] once a second map is full and preparing the first map for new incoming requests. The first map may refer to one of the map data structures from the data collection system

[0214] , and the second map may also refer to another map data structure from the data collection system

[0214] , In a scenario, when the second map reaches its maximum capacity or storage limit, the contents of the first map are removed or deleted to manage storage resources efficiently by freeing up space in the first map. The new incoming requests may refer to the requests which may come in future from other subscribers. This ensures that the system

[0200] can continue to receive and process the new requests, even when the first map is full. This continuous, cyclical data management ensures efficient handling of the incoming requests, enabling smooth and optimized operation of the IMS network. This dynamic management of data between the two maps allows the system

[0200] to effectively handle high volumes of incoming requests without overloading its storage capacity.

[0091] The present disclosure further discloses receiving, by the transceiver unit

[0202] , a subsequent request associated with the subscriber and then extracting, by the extraction unit

[0204] , a metadata associated with the subsequent request. The subsequent request may be the request associated with the subscriber which is retransmitted due to packet loss or non-receipt of data packets. The subsequent request may also be another request sent by the subscriber. The metadata associated with the subsequent request may at least comprises the header and the Mobile Station International Subscriber Directory Number (MSISDN).

[0092] At step

[0412] , the method

[0400] comprises matching, by a comparator unit

[0210] associated with the IPSMGW

[0102] , the metadata associated with the subsequent request associated with the subscriber, with the metadata associated with the subscriber stored in the data collection system

[0214] , Further, a result of the matching of the metadata associated with the subsequent request and the metadata associated with the subscriber may be one of a positive matching or a negative matching. The positive matching shows that the metadata associated with the subsequent requestand the metadata associated with the subscriber are same. The negative matching shows that the metadata associated with the subsequent request and the metadata associated with the subscriber are not same.

[0093] At step

[0414] , the method

[0400] further comprises rejecting, by a processing unit

[0212] associated with the IPSMGW

[0102] , the subsequent request based on the positive matching of the subsequent request associated with the subscriber, and the metadata associated with the subscriber stored in the data collection system

[0214] , Due to the positive matching of the metadata associated with the subsequent request and the metadata associated with the subscriber showing that the same request has been retransmitted thereby being redundant, the system

[0200] rejects it. This rejection helps in preventing the unnecessary processing of repeated requests. It also stops the initiation of an extra timer, which is typically used to handle retransmissions, thus saving system resources. The subsequent request may also be stored in the data collection system

[0214] ,

[0094] Thereafter, at step

[0416] , the method

[0400] is terminated.

[0095] FIG. 5 illustrates an exemplary block diagram of a computing device

[0500] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an implementation, the computing device

[0500] may also implement a method

[0400] for efficiently handling retransmission requests in an IP Multimedia Subsystem (IMS) network by utilising the system

[0200] , In another implementation, the computing device

[0500] itself implements the method

[0200] for efficiently handling retransmission requests in an IP Multimedia Subsystem (IMS) network using one or more units configured within the computing device

[0500] , wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.

[0096] The computing device

[0500] may include a bus

[0502] or other communication mechanism for communicating information, and a hardware processor

[0504] coupled with bus

[0502] for processing information. The hardware processor

[0504] may be, for example, a general-purpose microprocessor. The computing device

[0500] may also include a main memory

[0506] , such as a random-access memory (RAM), or other dynamic storage device

[0510] , coupled to the bus

[0502] for storing information and instructions to be executed by the processor

[0504] , The main memory

[0506] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor

[0504] , Such instructions, when stored in non-transitory storage media accessible to the processor

[0504] , render the computing device

[0500] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device

[0500] further includes a read only memory (ROM)

[0508] or other static storage device

[0510] coupled to the bus

[0502] for storing static information and instructions for the processor

[0504] ,

[0097] A storage device

[0510] , such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus

[0502] for storing information and instructions. The computing device

[0500] may be coupled via the bus

[0502] to a display

[0512] , 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

[0514] , including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus

[0502] for communicating information and command selections to the processor

[0504] , Another type of user input device may be a cursor controller

[0516] , such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor

[0504] , and for controlling cursor movement on the display

[0512] , The 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 the device to specify positions in a plane.

[0098] The computing device

[0500] 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

[0500] causes or programs the computing device

[0500] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device

[0500] in response to the processor

[0504] executing one or more sequences of one or more instructions contained in the main memory

[0506] , Such instructions may be read into the main memory

[0506] from another storage medium, such as the storage device

[0510] , Execution of the sequences of instructions contained in the main memory

[0506] causes the processor

[0504] 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.

[0099] The computing device

[0500] also may include a communication interface

[0518] coupled to the bus

[0502] , The communication interface

[0518] provides a two-way data communication coupling to a network link

[0520] that is connected to a local network

[0522] , For example, the communication interface

[0518] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to acorresponding type of telephone line. As another example, the communication interface

[0518] 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

[0518] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.

[0100] The computing device

[0500] can send messages and receive data, including program code, through the network(s), the network link

[0520] and the communication interface

[0518] , In the Internet example, a server

[0530] might transmit a requested code for an application program through the Internet

[0528] , the ISP

[0526] , a host

[0524] , the local network

[0522] and the communication interface

[0518] , The received code may be executed by the processor

[0504] as it is received, and / or stored in the storage device

[0510] , or other non-volatile storage for later execution.

[0101] Further, the present disclosure discloses a non-transitory computer readable storage medium storing one or more instructions for efficiently handling retransmission requests in an IP Multimedia Subsystem (IMS) network. The one or more instructions comprise executable code which when executed by one or more units of a system

[0200] , causes the one or more units of the system

[0200] to perform certain functions. The one or more instructions when executed causes a transceiver unit

[0202] of the system

[0200] to receive a request associated with a subscriber. The one or more instructions when executed further causes an extraction unit

[0204] of the system

[0200] to extract a metadata associated with the subscriber from the received request. The one or more instructions when executed further causes a mapping unit

[0206] of the system

[0200] to map the received request and the extracted metadata associated with the subscriber. The one or more instructions when executed further causes a storage unit

[0208] of the system

[0200] to store the mapped request and the metadata associated with the subscriber in a data collection system

[0214] of the system

[0200] , the data collection system

[0214] of the system

[0200] comprises at least two map data structures. The one or more instructions when executed further causes a comparator unit

[0210] of the system

[0200] to match a metadata associated with a subsequent request associated with the subscriber with the metadata associated with the subscriber stored in the data collection system

[0214] of the system

[0200] , The one or more instructions when executed further causes a processing unit

[0212] of the system

[0200] to reject the subsequent request based on a positive matching of the subsequent request associated with the subscriber with the metadata associated with the subscriber stored in the data collection system

[0214] of the system

[0200] ,

[0102] As is evident from the above the present disclosure provides a technically advanced solution for dynamic retransmission control for optimized application processing in IMS networks. Further, the present disclosure discloses a technically advanced solution that is designed to enhance the efficiency of processing in IMS networks by focusing on dynamic retransmission control, it effectively manages repeated register requests, streamlining operations within the Internet Protocol Multimedia Subsystem (IMS) network. The solution of the present disclosure optimizes resource usage by eliminating the need for additional timers, ultimately saving computational resources. Moreover, it addresses scalability concerns by providing a solution that improves the overall scalability of the IMS network. Additionally, the system

[0200] efficiently handles retransmissions by identifying and rejecting redundant requests, leading to a reduction in unnecessary processing and a boost in system performance. Further, the solution of the present disclosure discloses a dynamic dual-map data management system for handling incoming requests, ensuring the system operates smoothly even when handling large volumes of data.

[0103] While considerable emphasis has been placed herein on the disclosed implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.

[0104] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components / units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are encompassed within the scope of the present disclosure.

Claims

I / We Claim:

1. A method [400] for efficiently handling retransmission requests in an IP Multimedia Subsystem (IMS) network, comprising the steps of: receiving, by a transceiver unit [202] associated with an Internet Protocol short message gateway (IPSMGW) [102], a request associated with a subscriber; extracting, by an extraction unit [204] associated with the IPSMGW [102], a metadata associated with the subscriber from the received request; mapping, by a mapping unit [206] associated with the IPSMGW [102], the received request and the extracted metadata associated with the subscriber; storing, by a storage unit [208] associated with the IPSMGW [102], the mapped request and the metadata associated with the subscriber in a data collection system [214], the data collection system [214] comprises at least two map data structures; matching, by a comparator unit [210] associated with the IPSMGW [102], a metadata associated with a subsequent request associated with the subscriber with the metadata associated with the subscriber stored in the data collection system [214]; and rejecting, by a processing unit [212] associated with the IPSMGW [102], the subsequent request based on a positive matching of the subsequent request associated with the subscriber with the metadata associated with the subscriber stored in the data collection system [214],2. The method [400] as claimed in claim 1, the method further comprises verifying, by the processing unit [212], a validity of a sender phone number and a recipient phone number by cross-referencing an authorized numbers database.

3. The method [400] as claimed in claim 1, wherein the metadata associated with the subscriber at least comprises a header and a Mobile Station International Subscriber Directory Number (MSISDN).

4. The method [400] as claimed in claim 1, the method further comprises purging, by the processing unit [212], contents of a first map in the data collection system [214] once a second database is full and preparing the first map for new incoming requests.

5. The method [400] as claimed in claim 1, wherein the request is any or a combination of one or more messages and one or more registration requests.

6. The method [400] as claimed in claim 5, wherein the method [400] comprises generating, by the processing unit [212], an alert acknowledging receipt of the one or more messages by a recipient.

7. The method [400] as claimed in claim 6, wherein the method [400] comprises transmitting, by the transceiver unit [202], the alert acknowledging receipt to a sender.

8. The method [400] as claimed in claim 6, wherein the method [400] comprises deleting, by the processing unit [212], a stored data corresponding to each of the one or more messages from the map data structure after a successful transmission to the recipient.

9. The method [400] as claimed in claim 1, wherein the handling of the retransmission requests in the IP Multimedia Subsystem (IMS) network is performed by the IP short message gateway (IPSMGW) [102],10. A system [200] for efficiently handling retransmission requests in an IP Multimedia Subsystem (IMS) network, comprising: a transceiver unit [202] associated with an internet protocol short message gateway (IPSMGW) [102], configured to receive, a request associated with a subscriber; an extraction unit [204] connected at least to the transceiver unit [202], wherein the extraction unit [204] is configured to extract, a metadata associated with the subscriber from the received request; a mapping unit [206] connected at least to the extraction unit [204], wherein the mapping unit [206] is configured to map, the received request and the extracted metadata associated with the subscriber; a storage unit [208] connected at least to the mapping unit [206], wherein the storage unit [208] is configured to store, the mapped request and the metadata associated with the subscriber in a data collection system [214], the data collection system [214] comprises at least two map data structures; a comparator unit [210] connected at least to the storage unit [208], wherein the comparator unit [210] is configured to match, a metadata associated with a subsequent request, associated with the subscriber, with the metadata associated with the subscriber stored in the data collection system [214]; and a processing unit [212] connected at least to the comparator unit [210], wherein the processing unit [212] is configured to reject, the subsequent request based on a positive matching of the subsequent request associated with the subscriber with the metadata associated with the subscriber stored in the data collection system [214],11. The system [200] as claimed in claim 10, wherein the processing unit [212] is configured to verify a validity of a sender phone number and a recipient phone number by crossreferencing an authorized numbers database.

12. The system [200] as claimed in claim 10, wherein the metadata associated with the subscriber at least comprises a header and a Mobile Station International Subscriber Directory Number (MSISDN).

13. The system [200] as claimed in claim 10, wherein the processing unit [212] is configured to purge contents of a first map in the data collection system [214] once a second map is full and preparing the first map for new incoming requests.

14. The system [200] as claimed in claim 10, wherein the request is any or a combination of one or more messages and one or more registration requests.

15. The system [200] as claimed in claim 14, wherein the processing unit [212] is configured to generate an alert acknowledging receipt of the one or more messages by a recipient.

16. The system [200] as claimed in claim 15, wherein the transceiver unit [202] is configured to transmit the alert acknowledging receipt to a sender.

17. The system [200] as claimed in claim 15, wherein the processing unit [212] is configured to delete a stored data corresponding to each of the one or more messages from the map data structure after a successful transmission to the recipient.

18. The system as claimed in claim 10, wherein each of the handling of the retransmission requests in the IP Multimedia Subsystem (IMS) network is performed by the IP short message gateway (IPSMGW) [102],19. A non-transitory computer readable medium storing one or more instructions, the one or more instructions comprises executable code, which when executed by one or more units of a system, causes: a transceiver unit [202] of the system [200] to receive a request associated with a subscriber; an extraction unit [204] of the system [200] to extract a metadata associated with the subscriber from the received request; a mapping unit [206] of the system [200] to map the received request and the extracted metadata associated with the subscriber; a storage unit [208] of the system [200] to store the mapped request and the metadata associated with the subscriber in a data collection system, the data collection system comprises at least two map data structures; a comparator unit [210] of the system [200] to match a metadata associated with a subsequent request associated with the subscriber with the metadata associated with the subscriber stored in the data collection system; a processing unit [212] of the system [200] to reject the subsequent request based on a positive matching of the subsequent request associated with the subscriber with the metadata associated with the subscriber stored in the data collection system.

Images