System and method for managing network traffic in a communication network

Abstract

Disclosed is a system (300) and a method (400) for managing network traffic in a communication network (100). The method (400) includes receiving a registration request corresponding to network service(s) for a user account and retrieving a service ID from the registration request. The method (400) further includes determining whether an entry corresponding to the service ID is present in a cache memory (222) of the communication network (100). Furthermore, the method (400) includes determining, based on the presence of the entry corresponding to the service ID in the cache memory (222), whether a delivery status report procedure is conducted for the user account corresponding to the network service(s). Moreover, the method (400) includes generating, based on the determination that the delivery status report procedure is not conducted for the user account corresponding to the network service(s), a Call Detail Record (CDR) for the registration request.

Description

SYSTEM AND METHOD FOR MANAGING NETWORK TRAFFIC IN A COMMUNICATION NETWORKTECHNICAL FIELD

[0001] The embodiments of the present disclosure generally relate to the field of wireless communication networks. More particularly, the present disclosure relates to a system and a method for managing registration requests for network services in a communication network.BACKGROUND OF THE INVENTION

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

[0003] In the evolving telecommunication landscape, efficient Short Message Service (SMS) delivery is essential for mobile network operators. Traditional systems use components such as the Internet Protocol Short Message Gateway (IPSMGW) and the Short Message Service Center (SMSC) to handle SMS routing and delivery. This segmented approach generally results in increased latency, higher computational complexity, and more instances of potential system errors. The IPSMGW plays a critical role in collecting and forwarding SMS data from Internet protocol management Subsystem (IMS) users. However, the IPSMGW faces computational challenges for Anti- Spam checks, Mobile Number Portability (MNP) queries, and charging triggers, which add to processing time and increase network load. Additionally, frequent registrations and re-registration requests increase ATM traffic on the communication network that further straining network resources and impacting system performance. Typically, the service request registration and re-registration occur after every hour,which requires an Any-Time-Modifi cation (ATM) request corresponding to the service requested by a user account to be generated and communicated to the IMS network, which further increases utilization of network resources and adds to the network traffic.

[0004] In view of the abovementioned broad problem, with the rise the IMS networks, there is a growing need for an integrated solution to streamline the process of handling communication services in a network without extensively exhausting the network resources.SUMMARY

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

[0006] According to an embodiment of the present disclosure, a method for managing network traffic in a communication network is provided. The method includes receiving, from a user device by an Internet Protocol Short Message Gateway (IPSMGW), a registration request corresponding to a registration of a user account associated with the user device for at least one network service of a plurality of network services in the communication network. The method further includes determining, by a front-end (FE) server, whether the registration request is a re-registration request for the user account. Furthermore, the method includes determining, by the FE server based on the determination that the registration request is the re-registration request for the user account, whether a delivery status report is present or absent for the user account corresponding to the at least one network service. Furthermore, the method includes generating, by the FE server based on the determination that the delivery statusreport is absent for the user account corresponding to the at least one network service, a Call Detail Record (CDR) for the registration request to manage the network traffic.

[0007] In some aspects of the present disclosure, the registration request comprises a service Identifier (service ID) associated with the at least one network service. Moreover, the front-end determines that the registration request received is the reregistration request for the user account, when a record corresponding to the service ID is present in a cache memory of the front-end.

[0008] In some aspects of the present disclosure, the service ID comprises at least one of a first identifier associated with the user account, a second identifier associated with the user device, and at least one identifier associated with the at least one network service.

[0009] In some aspects of the present disclosure, the FE server determines that the registration request received is a new registration request for the user account based on the determination that the record corresponding to the service ID is absent in the cache memory. Moreover, the FE server generates a registration entry for the at least one network service corresponding to the user account.

[0010] In some aspects of the present disclosure, based on the determination that the delivery status report is present for the user account corresponding to the at least one network service, the method includes generating, by the IPSMGW, an Any-Time- Modification (ATM) request for the at least one network service. The ATM request initiates re-registration of the at least one network service through a Mobile Application Part (MAP) interface.

[0011] In some aspects of the present disclosure, the presence of the delivery status report for the user account corresponding to the at least one network service indicates a historical occurrence of a delivery status report procedure for the user accountcorresponding to the at least one network service. Moreover, the absence of the delivery status report for the user account corresponding to the at least one network service indicates a historical non-occurrence of the delivery status report procedure for the user account corresponding to the at least one network service.

[0012] In some aspects of the present disclosure, the delivery status report procedure corresponds to a historical instance of failure of the registration request for the user account for the at least one network service.

[0013] According to another embodiment of the present disclosure, a system to manage network traffic in a communication network is provided. The system includes an Internet Protocol Short Message Gateway (IPSMGW) and a front-end (FE) server. The Internet Protocol Short Message Gateway (IPSMGW) is configured to receive a registration request corresponding to a registration of a user account associated with the user device for at least one network service of a plurality of network services in the communication network. The FE server is configured to determine whether the registration request is a re-registration request for the user account. Moreover, the FE server is configured to determine, based on based on the determination that the registration request is the re-registration request for the user account, whether a delivery status report is present or absent for the user account corresponding to the at least one network service. Furthermore, the FE server is configured to generate, based on the determination that the delivery status report is absent for the user account corresponding to the at least one network service, a Call Detail Record (CDR) for the registration request to manage the network traffic.

[0014] According to yet another embodiment of the present disclosure, a computerprogram product for managing network traffic in a communication network is provided. The computer-program product includes computer-executable instructions that are stored on a non-transitory computer-readable medium and that, when executedby at least one processor performs operations. The operations include receiving from a user device a registration request corresponding to a registration of a user account associated with the user device for at least one network service of a plurality of network services in the communication network. The operations further include determining whether the registration request is a re-registration request for the user account. Furthermore, the operations include determining, based on the determination that the registration request is the re-registration request for the user account, whether a delivery status report is present or absent for the user account corresponding to the at least one network service. Furthermore, the operations include generating, based on the determination that the delivery status report is absent for the user account corresponding to the at least one network service, a Call Detail Record (CDR) for the registration request to manage the network traffic.BRIEF DESCRIPTION OF DRAWINGS

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

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

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

[0018] FIG. 3 is a block diagram illustrating exemplary components of a system to manage network traffic in the communication network, in accordance with an exemplary embodiment of the present disclosure.

[0019] FIG. 4 illustrates a flowchart that depicts a method for managing the network traffic in the communication network, in accordance with an embodiment of the present disclosure.LIST OF REFERENCE NUMERALSThe following list is provided for convenience and in support of the drawing figures and as part of the text of the specification, which describe innovations by reference to multiple items. Items not listed here may nonetheless be part of a given embodiment. For better legibility of the text, a given reference number is recited near some, but not all, recitations of the referenced item in the text. The same reference number may be used with reference to different examples or different instances of a given item. The list of reference numerals is as follows:100 - Communication network102 - Core network104 - Nodes106 - Devices202 - IPSMGW204 - EMS206 - STP208 - DRA210 - HSS212 - Database(s)214 - MNP216 - SMPP Server(s)218 - I / S-CSCF220 - Front End (FE) Server222 - Cache224 - OCS300 - System for managing traffic in communication network302 - Communication Interface304 - Memory Unit306 - Communication Bus308 - Gateway Interface310 - Gateway Memory312 - Gateway Processor314 - FE Interface316 - FE Memory318 - FE Processor320 - Instructions Memory400 - Method for managing traffic in communication network402-416 - Operational Blocks of Method 400DETAILED DESCRIPTION OF THE INVENTION

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

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

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

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

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

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

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

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

[0028] Aspects of the present disclosure provide a system and method for managing network traffic in a communication network. Specifically, the system manages the network traffic by managing registration requests for user account(s) corresponding to network service(s) in a communication network. The system provides management of traffic in the communication network by handling registration requests corresponding to the network service(s) requested by the user account(s). In some aspects of the present disclosure, the system facilitates identification of data entries in a cache memory corresponding to re-registration requests and suppresses ATM requests corresponding to the re-registration requests, thereby reducing the computational complexity and traffic on the communication network. In some other aspects of the present disclosure, the system further enables identifying data entries corresponding to a historical event of a registration request failure corresponding to the network service(s). In response, the system initiates ATM request(s) for re-registration of the network service(s).

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

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

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

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

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

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

[0035] FIG. 2 is a block diagram that illustrates exemplary components of the core network 102, in accordance with an embodiment of the present disclosure. As presented in FIG. 2, the core network 102 may include multiple Network Functions (NFs). Each NF may be deployed in the form of a data processing node within the communication network 100, configured to perform data processing and / or data storage operations to contribute to the overall functionality as discussed through the present disclosure.

[0036] According to the exemplary embodiment presented through FIG. 2, the NFs may include an Internet Protocol Messaging Gateway (IPSMGW) 202, an Element Management System (EMS) 204, a Signal Transfer Point (STP) 206, Diameter Routing Agents (DRAs) 208 (presented by way of first DRA 208-1 and second DRA 208-2), a Home Subscriber Server (HSS) 210, database(s) 212, a Mobile Network Portability (MNP) 214, Short Message Peer-Peer (SMPP) servers 216, and a Call Session Control Function (CSCF) 218, a Front-End (FE) server 220 (hereinafter interchangeably referred to as FE 220) coupled with a cache memory 222 (hereinafter interchangeably referred to as ‘cache 222’), and an Online Charging System (OCS) 224. The first DRA208-1 may couple the IPSMGW 202 with the HSS 210, and the second DRA 208-2 may couple the IPSMGW 202 with the OCS 224.

[0037] Preferably, the operation(s) of are performed by the IPSMGW 202 and FE server 220, supported by the various other entities of the core network 102 as presented herein. As presented in FIG. 2, the IPSMGW 202 may be connected to the EMS 204 via a REST Application Protocol Interface (API), the STP 206 via a Signaling and Transport (SIGTRAN) interface, the first DRA 208-1 via a diameter Sh interface, database(s) 212 via a Transportation Control Protocol (TCP) interface(s), MNP 214 via a Session Initiation Protocol (SIP) interface, and with the SMPP server(s) 216 via a SMPP interface. The first DRA 208-1 may be coupled to the HSS 210 via the diameter Sh interface.

[0038] The diameter Sh interface may enable communication of User-Data-request (UDR) and User-Data-Answer (UDA) commands between the IPSMGW 202 and the HSS 210 via the first DRA 208-1. The IPSMGW 202 may further be coupled to the second DRA 208-2 via a diameter RO interface. The second DRA 208-2 may be coupled with the OCS 224 via the diameter RO interface. Moreover, the IPSMGW 202 may be coupled with the CSCF 218 via the SIP interface. The CSCF 218 may further be coupled with the user device(s) 106 via the SIP interface.

[0039] The EMS 204 may be configured to manage network elements within the core network 102. Specifically, the EMS 204 may provide an Input-Output (I / O) interface for a user to provide input(s) for configuration of the IPSMGW 202 for receiving registration requests and amending run-time. The STP 206 may be configured for initiating, maintaining, modifying, and terminating real-time communications sessions between Internet Protocol (IP) devices. Specifically, the STP 206 may be connected to a Mobile Application Port (MAP) interface that is configured to send an Any-Time- Modification (ATM) request.

[0040] The first DRA 208-1 may be configured to couple the HSS 210 with the IPSMGW 202. The HSS 210 may be configured to send an Sh-query to determine traffic at the SIP interface. Preferably, the database(s) 212 may include a Cassandra database to store data and instructions associated with the IPSMGW 202. The data stored in the database(s) 212 may correspond to protocols, code(s), and / or rules for operation(s) performed by the IPSMGW 202 corresponding to the registration request(s) for the network service(s). The MNP 214 may be configured to retain information associated with the user account while switching a network provider (or a geographical handover of network provider). The SMPP server(s) 216 may be configured to host an external application that connects to the IPSMGW 202 to engage in the sending and / or receiving of the registration request.

[0041] The CSCF 218 may be configured to process SIP signaling. Typically, the CSCF 218 may provide session control rules for terminals and applications using the IMS network. In some aspects of the present disclosure, the CSCF 218 may be configured as a network element in the communication network 100 to store, forward, convert and deliver Short Message Service (SMS). The CSCF 218 may be coupled with the user device 106 via the SIP interface and may provide session-control service(s) to the user device 106. Examples of the session-control service(s) may include secure routing of SIP messages, monitoring of SIP sessions, communicating with the policy architecture to support media authorization, and the like.

[0042] The FE server 220 may be configured to receive input(s) and / or render output(s) corresponding to data related to registration of network service(s) to and / or from the cache memory 222. Particularly, the registration request may be communicated to the cache memory 222, that can be viewed and / or retrieved at an I / O interface (shown later in FIG. 3 as FE interface 314) of the FE 220. In some aspects of the present disclosure, the cache memory 222 may be an integral part of the IPSMGW 202 or may beconnected in proximity to the IPSMGW 202, which enables extraction and storage of registration request data in the cache memory 222 at a latency lower than usual. The OCS 224 may be configured to determine protocol(s), policies, and / or rules for determining charges related to the network service(s). Moreover, the OCS 224 may be configured to manage account balance, recharge(s), and / or and operation(s) corresponding to network service(s) associated with the user account.

[0043] In operation, the IPSMGW 202 may be configured to receive a registration request corresponding to a network service associated with the user account from the CSCF 218. The IPSMGW 202 may further be configured to retrieve a service ID from the registration request. Furthermore, the IPSMGW 202 may be configured to send the service ID to the FE 220 connected to the cache memory 222. In some aspects of the present disclosure, the service ID may be retrieved in an unstructured format, which makes it difficult for the FE 220 to identify the type of service(s). In such a scenario, the IPSMGW 202 may be configured to parse the service ID into a structured format understandable by the FE 220. The FE 220 may be configured to check the cache memory 222 for an entry corresponding to the service ID. The FE 220 may further be configured to determine whether the entry corresponding to the service ID is present in the cache memory 222. In response to a determination by the FE 220 that the entry corresponding to the service ID is absent in the cache memory 222, the IPSMGW 202 may be configured to register the network service based on the registration request. The IPSMGW 202 may further be configured to determine whether a Report-SM is conducted for the service ID, in response to the determination of a presence of the entry for the service ID in the cache memory 222. In response to the determination that the Report-SM is conducted for the entry, the IPSMGW 202 may be configured to initiate an Any-Time-Modification (ATM) request over the MAP interface. Moreover, in response to a determination that the Report-SM is not conducted for the entry, theIPSMGW 202 may be configured to suppress the ATM request and generate a Call Detail Record (CDR) with the indication of the suppression of the ATM request.

[0044] Although FIG. 2 illustrates one example of the core network 102 utilized for managing the network traffic in the communication network 100, various changes may be made to FIG. 2, without deviating from the scope of the present disclosure. In another embodiment of the present disclosure, several entities of the core network 102 may be encapsulated in a single enclosure, for example, the cache 222 and the FE 220 may be structurally deployed as a single entity. In another example, the cache 222 and the FE 220 may be integral parts of the IPSMGW 202. Moreover, the core network 102 may include any number of components in addition to those shown in FIG.2 without deviating from the scope of the present disclosure. Further, various components of the core network 102 (as shown in FIG. 2) may be combined, further subdivided, or omitted and additional components may be added according to particular needs.

[0045] FIG. 3 is a block diagram illustrating exemplary components of a system 300 to manage network traffic in the communication network 100, in accordance with an exemplary embodiment of the present disclosure. The system 300 may include the IPSMGW 202, the FE server 220, a communication interface 302, and a memory unit 304. Various entities of the system 300 may be communicatively coupled to each other by a communication bus 306. The IPSMGW 202 may include a gateway interface 308, a gateway memory 310, and a gateway processor 312. Similarly, the FE server 220 may include FE interface 314, FE memory 316, and FE processor 318. Moreover, the memory unit 304 may include the cache 222 and instructions memory 320.

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

[0047] The gateway memory 310 may be configured to store code(s), instruct! on(s), and data corresponding to the operations of the IPSMGW 202. Similarly, the FE memory 316 may be configured to store code(s), instruction(s), and data corresponding to the operations of the FE server 220. Moreover, the memory unit 304 may include code(s), instruction(s), and data corresponding to the operations of the system 300. Examples of the memory units (cumulatively referring to the memory unit 304, the gateway memory 310, and the FE memory 316) may include but are not limited to, a ROM, a RAM, a flash memory, a removable storage drive, a HDD, a solid-state memory, a magnetic storage drive, a PROM, an EPROM, and / or an EEPROM. Aspects of the present disclosure are intended to include or otherwise cover any type of storage medium as memory units, without deviating from the scope of the present disclosure.

[0048] Particularly, the memory unit 304 may include the instructions memory 320 and the cache 222. The instructions memory 320 configured to store computer program instructions and / or codes for operation(s) of various components of the system 300. For example, the instructions memory 320 may be configured to store computerprogram instructions corresponding to the operation(s) performed by the various components of the system 300 for managing the network traffic in the communication network 100. In an embodiment of the present disclosure, the instructions memory 320 may be configured as a non-transitory storage medium. Examples of the instructions memory 320 configured as the non-transitory storage medium includes hard drives, solid-state drives, flash drives, Compact Disk (CD), Digital Video Disk (DVD), and the like. Aspects of the present disclosure are intended to include or otherwise cover any type of non-transitory storage medium as the instructions memory 320, without deviating from the scope of the present disclosure. As will be appreciated, any such computer program instructions stored in the instructions memory 320 may be executed by one or more computer processors, including without limitation a general-purpose computer or special purpose computer, or other programmable processing apparatus to produce a machine, such that the computer program instructions which execute on the computer processor(s) or other programmable processing apparatus create means for implementing the function(s) specified.

[0049] The cache 222 may be configured to store critical information / data corresponding to the operations of the system, that may be required to be retrieved in real-time (without significant delay). For example, the cache 222 may be configured to store service Identifier (ID) of network service(s) rendered by service providing vender(s) to user(s) (e.g., subscriber(s) or user account(s)) in the communication network 100.

[0050] The gateway processor 312 may include processing circuitry configured with suitable logic, instructions, interfaces, and / or codes that enable the IPSMGW 202 to execute computational operations(s) for a variety of functionalities driven through the IPSMGW 202. Similarly, the FE processor 318 may include processing circuitry configured with suitable logic, instructions, interfaces, and / or codes that enable the FE server 220 to execute computational operations(s) for a variety of functionalities driventhrough the FE server 220. Examples of the processors (cumulatively referring to the gateway processor 312 and the FE processor 318) may include, but are not limited to, an Application Specific Integrated Chip (ASIC) processor, a RISC processor, a CISC processor, a Field Programmable Gate Array (FPGA), and the like. Aspects of the present disclosure are intended to include or otherwise cover any processing unit as the processors, without deviating from the scope of the present disclosure.

[0051] Particularly, the IPSMGW 202 may be configured to receive the registration request corresponding to a registration of a user account associated with the user device 106 for at least one network service of the multiple network services in the communication network 100. Examples of the network services in the communication network 100 may include, but are not limited to, voice calling network services and Short Messaging Service(s) (SMS), subscriber policy counter status (identification and alteration) services and advertising application services (e.g., management of spending limit, spending-status-notification, session details etc.), broadband and / or optical fiber network service(s) (e.g., immediate account debit, event based account debit with reservations, session based account debit with reservations, account refund, account balance query, etc.), network service(s) related to external account recharging, network service(s) related to determination of tariff for a given event or service (e.g., one-time or recurrent charges), network service(s) related to service providing operator's postprocessing operations, and / or online data and multimedia services. Preferably, aspects of the present disclosure are intended to include or otherwise cover any service associated with the functionality of the entities in the core network 102 as ‘the network services’ without deviating from the scope of the present disclosure.

[0052] Typically, the registration request may correspond to access for a user account for accessing network service(s) in the communication network 100. Moreover, the registration request includes a service ID that defines the network service(s) being requested by the user account for registration. For example, in a hypothetical scenarioa registration request with service ID ‘30’ from user account ABC001 may relate to requesting to access ‘data communication service’ by the user account ABC001, whereas a service ID ‘20’ corresponds to access to SMS service. The FE server 220 may be configured to determine whether the registration request is a re-registration request for the user account. Preferably, the registration request comprises a service Identifier (service ID) associated with the at least one network service.

[0053] The FE 220 may be configured to determine that the registration request received is the re-registration request for the user account, when a record corresponding to the service ID is present in the cache memory 222. Additionally, the FE server 220 may also be configured to determine that the registration request received is a new registration request for the user account based on the determination that the record corresponding to the service ID is absent in the cache memory 222. The FE server 220 may also be configured to generate a registration entry for the at least one network service corresponding to the user account, to be stored in the cache 222 for reference. Preferably, the registration request may be tagged with the service ID. The FE 220 may trigger the cache memory 222 to fetch record(s) (e.g., data entry) corresponding to the service ID. In response to the trigger, the cache memory 222 may search for the data entry labelled with the service ID and may render the data entry if present in the cache memory 222. When such a data entry is absent in the cache memory 222, the cache memory 222 may notify the FE server 220 about the absence of the record(s) corresponding to the registration request, and the FE server 220 may identify the registration request as the new registration request for the network service(s) corresponding to the requesting user account.

[0054] In some aspects of the present disclosure, the service ID may include at least one of a first identifier associated with the user account, a second identifier associated with the user device, and at least one identifier associated with the at least one network service.

[0055] Moreover, the FE server 220 may be configured to determine, based on based on the determination that the registration request is the re-registration request for the user account, whether a delivery status report is present or absent for the user account corresponding to the at least one network service. Furthermore, the FE server 220 may be configured to generate, based on the determination that the delivery status report is absent for the user account corresponding to the at least one network service, a Call Detail Record (CDR) for the registration request to manage the network traffic. Traditionally, the ATM request is initiated over the MAP interface, as per the existing telecom standards. With increasing count of user accounts and diversified network services in the communication network, overwhelming the MAP interface. Generation of the CDR for registration of network service(s) for the user account suppresses the need of triggering ATM requests over the MAP interface, thereby results in task-load balancing for registration of network service(s) for user account(s) in the communication network 100.

[0056] Preferably, the presence of the delivery status report for the user account corresponding to the at least one network service indicates a historical occurrence of a delivery status report procedure for the user account corresponding to the at least one network service. Moreover, the absence of the delivery status report for the user account corresponding to the at least one network service indicates a historical nonoccurrence of the delivery status report procedure for the user account corresponding to the at least one network service. In some aspects of the present disclosure, the delivery status report procedure corresponds to a historical instance of failure of the registration request by the user account for the at least one network service. Preferably, the delivery status report procedure may be a report-SM procedure and may correspond to a historical instance of a failure of a past registration request by the user account for the network service(s).

[0057] Based on the determination that the delivery status report is present for the user account corresponding to the at least one network service, the IPSMGW 202 may be configured to generate the ATM request for the at least one network service. The ATM request initiates re-registration of the at least one network service through a Mobile Application Part (MAP) interface.

[0058] Although FIG. 3 illustrates one example of the system 300 for managing the network traffic in the communication network 100, various changes may be made to FIG. 3, without deviating from the scope of the present disclosure. Further, the system 300 may include any number of components in addition to those shown in FIG.3 without deviating from the scope of the present disclosure. Further, various components in FIG. 3 may be combined, further subdivided, or omitted and additional components may be added according to particular needs.

[0059] FIG. 4 illustrates a flow chart that depicts a method 400 for managing the network traffic in the communication network 100, in accordance with an exemplary embodiment of the present disclosure. The method 400 presents a set of operational steps by way of blocks 402 through 416, as presented hereinbelow.

[0060] At block 402, the IPSMGW 202 may receive the registration request from the user device 106 corresponding to the registration of the user account associated with the user device 106 for the network service(s). The registration request may include the service ID associated with the network service(s).

[0061] At block 404, the IPSMGW 202 may retrieve the service ID for the network service(s) corresponding to the user account from the registration request. In some aspects of the present disclosure, the service ID may include at least one of the first identifier associated with the user account, the second identifier associated with theuser device, and the identifier(s) associated with the network service(s) requested for the user account. In some other aspects of the present disclosure, the service ID may comprise information of an identity of the user device 106 (e.g., a device-ID), information of the network service(s) (e.g., type(s) of the network service(s)), and other parameters associated with the user device 106 (e.g., information of location of the user device 106 and the like).

[0062] At block 406, the FE server 220 may check the cache memory 222 for the entry corresponding to the service ID. In some aspects of the present disclosure, the service ID may be retrieved in an unstructured format. In such a scenario, the core network 102 may parse the service ID into a structured format.

[0063] At block 408, the FE server 220 may determine whether the registration request is the re-registration request for the user account. Specifically, the FE server 220 may determine whether the entry corresponding to the service ID is present in the cache memory 222, which means an earlier registration of the network service(s) for the user account already exists in the cache memory 222. When the registration request is the re-registration request for the user account (i.e., the entry is present in the cache memory 222), the method 400 proceeds to block 412. Else, when the registration request is a new registration request for the user account (i.e., the entry is absent in the cache memory 222), the method 400 proceeds to block 410.

[0064] At block 410, the IPSMGW 202 may register the network service(s) based on the registration request. The IPSMGW 202 may further generate the registration entry for the registration request corresponding to the access of the network service(s) for the user account to be stored in the cache memory 222. In some aspects of the present disclosure, to register the network service(s), the IPSMGW 202 may generate the ATM request to initiate registration of the network service(s) for the user account throughthe MAP interface, based on the contents of the service ID derived from the registration request.

[0065] At block 412, the FE server 220 may determine whether a delivery status report is present or absent for the user account corresponding to the network service(s) (i.e., the Report-SM entry is present / absent in the cache memory 222 corresponding to the service ID). Specifically, the FE server 220 may determine whether the delivery status report procedure is conducted for the user account corresponding to the network service(s). The Report-SM entry (or the delivery status report procedure) corresponds to the historical instance of the failure of the past registration request by the user account for the network service(s).

[0066] Specifically, the Report-SM entry may include data generated by the system 300 when the network service(s) fail (e.g., the Report-SM entry is generated and stored in the database(s) 212 when a messaging service failed). When the FE server 220 determines that the delivery status report (i.e., the Report-SM entry) is present for the user account corresponding to the network service(s), the method 400 proceeds to block 414. Else, when the FE server 220 determines that the delivery status report (i.e., the Report-SM entry) is absent for the user account corresponding to the network service(s), the method 400 proceeds to block 416.

[0067] At block 414, the IPSMGW 202 may initiate the ATM request over the MAP interface corresponding to the registration request for registration of the network service(s) associated with the user account. Particularly, the ATM request initiates the re-registration of the network service(s) for the user account through the MAP interface.

[0068] At block 416, the FE server 220 may generate the CDR for the registration request based on the determination that the delivery status report (the Report-SM entry)is absent for the user account for the network service(s). In an exemplary scenario, the network service(s) may be related to voice communication service (such as voice call). In such scenario, absence of the delivery status report indicates that the request for registration of the voice communication service for the user account has been received for the first time (and is not a re-registration request following a similar request failed in the past). Therefore, the FE server 220 may generate the CDR for the registration request corresponding to a first-time registration request for the voice communication service(s) for the user account.

[0069] Referring to the technical abilities and advantageous effect of the present disclosure, operational advantages that may be provided by one or more embodiments are presented herein. These include the system 300 and the method 400 for managing the network traffic in the communication network 100 by reducing the count of queries corresponding to registration and re-registration of network service(s) for the user account. Typically, the IMS networks undergo re-registration process which requires ATM requests to be generated and processed every hour. The system 300 provides storage of entries (through the cache 222) corresponding to registration requests, that can be accessed to avoid generation of ATM requests when a re-registration query is received for the same user account, which reduces the computational and storage burden on the communication network 100, and thus enhances the overall performance and efficiency of the IMS network. Traditionally, the ATM request is initiated over the MAP interface, as per the existing telecom standards. With increasing count of user accounts and diversified network services in the communication network, overwhelming the MAP interface. Generation of the CDR for registration of network service(s) for the user account suppresses the need of triggering ATM requests over the MAP interface, thereby results in task-load balancing for registration of network service(s) for user account(s) in the communication network 100.

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

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

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

Claims

We Claim:

1. A method (400) for managing network traffic in a communication network (100), the method (400) comprising: receiving, from a user device (106) by an Internet Protocol Short Message Gateway (IPSMGW) (202), a registration request corresponding to a registration of a user account associated with the user device (106) for at least one network service of a plurality of network services in the communication network (100); determining, by a front-end (FE) server (220), whether the registration request is a re-registration request for the user account; determining, by the FE server (220) based on the determination that the registration request is the re-registration request for the user account, whether a delivery status report is present or absent for the user account corresponding to the at least one network service; and generating, by the FE server (220) based on the determination that the delivery status report is absent for the user account corresponding to the at least one network service, a Call Detail Record (CDR) for the registration request to manage the network traffic.

2. The method (400) as claimed in claim 1, wherein: the registration request comprises a service Identifier (service ID) associated with the at least one network service; and the front-end determines that the registration request received is the reregistration request for the user account, when a record corresponding to the service ID is present in a cache (222) memory.

3. The method (400) as claimed in claim 2, wherein the service ID comprises at least one of a first identifier associated with the user account, a second identifierassociated with the user device (106), and at least one identifier associated with the at least one network service.

4. The method (400) as claimed in claim 2, wherein: the FE server (220) determines that the registration request received is a new registration request for the user account based on the determination that the record corresponding to the service ID is absent in the cache (222) memory; and the FE server (220) generates a registration entry for the at least one network service corresponding to the user account.

5. The method (400) as claimed in claim 1, wherein, based on the determination that the delivery status report is present for the user account corresponding to the at least one network service, the method (400) comprising: generating, by the IPSMGW (202), an Any-Time-Modification (ATM) request for the at least one network service, wherein the ATM request initiates re-registration of the at least one network service through a Mobile Application Part (MAP) interface.

6. The method (400) as claimed in claim 5, wherein: the presence of the delivery status report for the user account corresponding to the at least one network service indicates a historical occurrence of a delivery status report procedure for the user account corresponding to the at least one network service; and the absence of the delivery status report for the user account corresponding to the at least one network service indicates a historical non-occurrence of the delivery status report procedure for the user account corresponding to the at least one network service.

7. The method (400) as claimed in claim 6, wherein the delivery status report procedure corresponds to a historical instance of failure of the registration request for the user account for the at least one network service.

8. A system (300) to manage network traffic in a communication network (100), the system (300) comprising: an Internet Protocol Short Message Gateway (IPSMGW) (202) configured to receive a registration request corresponding to a registration of a user account associated with the user device (106) for at least one network service of a plurality of network services in the communication network (100); and a front-end (FE) server (220) coupled to the IPSMGW (202), wherein the FE server (220) is configured to: determine whether the registration request is a re-registration request for the user account; determine, based on based on the determination that the registration request is the re-registration request for the user account, whether a delivery status report is present or absent for the user account corresponding to the at least one network service; and generate, based on the determination that the delivery status report is absent for the user account corresponding to the at least one network service, a Call Detail Record (CDR) for the registration request to manage the network traffic.

9. The system (300) as claimed in claim 8, wherein: the registration request comprises a service Identifier (service ID) associated with the at least one network service; andthe front-end determines that the registration request received is the reregistration request for the user account, when a record corresponding to the service ID is present in a cache (222) memory.

10. The system (300) as claimed in claim 9, wherein the service ID comprises at least one of a first identifier associated with the user account, a second identifier associated with the user device (106), and at least one identifier associated with the at least one network service.

11. The system (300) as claimed in claim 9, wherein: the FE server (220) determines that the registration request received is a new registration request for the user account based on the determination that the record corresponding to the service ID is absent in the cache (222) memory; and the FE server (220) generates a registration entry for the at least one network service corresponding to the user account.

12. The system (300) as claimed in claim 8, wherein, based on the determination that the delivery status report is present for the user account corresponding to the at least one network service, the IPSMGW (202) is configured to generate an Any-Time- Modification (ATM) request for the at least one network service, wherein the ATM request initiates re-registration of the at least one network service through a Mobile Application Part (MAP) interface.

13. The system (300) as claimed in claim 12, wherein: the presence of the delivery status report for the user account corresponding to the at least one network service indicates a historical occurrence of a delivery status report procedure for the user account corresponding to the at least one network service; and the absence of the delivery status report for the user account corresponding to the at least one network service indicates a historical non-occurrence of the deliverystatus report procedure for the user account corresponding to the at least one network service.

14. The system (300) as claimed in claim 13, wherein the delivery status report procedure corresponds to a historical instance of failure of the registration request by the user account for the at least one network service.

15. A computer-program product for managing network traffic in a communication network (100), the computer- program product comprising computer-executable instructions that are stored on a non-transitory computer-readable medium and that, when executed by at least one processor performs operations comprising: receiving, from a user device (106), a registration request corresponding to a registration of a user account associated with the user device (106) for at least one network service of a plurality of network services in the communication network (100); determining whether the registration request is a re-registration request for the user account; determining, based on the determination that the registration request is the reregistration request for the user account, whether a delivery status report is present or absent for the user account corresponding to the at least one network service; and generating, based on the determination that the delivery status report is absent for the user account corresponding to the at least one network service, a Call Detail Record (CDR) for the registration request to manage the network traffic.

Images