Method and system for routing an offnet call

Abstract

The present disclosure relates to a method and a system for routing an offnet call The disclosure encompasses receiving, an offnet call request comprising a set of headers; analysing, a list of selection combinations associated with group of MGCFs; determining, a target group of MGCF from the group of MGCFs based on matching of the list of selection combinations with the set of headers; identifying, a first MGCF from the target group of MGCF; transmitting, to the first MGCF, the offnet call request; receiving, from the first MGCF, failure responses associated with the offnet call request; identifying, in an event of receiving from the first MGCF at least a predefined number of failure responses for the offnet call request, a second MGCF from the target group of MGCF; and routing the offnet call associated with the offnet call request to the identified second MGCF.

Description

METHOD AND SYSTEM FOR ROUTING AN OFFNET CALLFIELD OF THE DISCLOSURE

[0001] Embodiments of the present disclosure generally relate to the field of wireless communication systems. More particularly, embodiments of the present disclosure relate to methods and systems for routing an offnet call.BACKGROUND

[0002] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.

[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth-generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.

[0004] Further, over the period various solutions have been developed to improve the performance of communication devices and to enable flexibility in offnet call routing. However, there are still certain challenges with existing solutions. The existing solution faced a technical problem related to offnet calls between two different operators connected via the media gateway control function (MGCF). Although operators sign ND As specifying how these offnet calls should be terminated at the point of interconnection (POI), the varying requirements of different operatorsat the POI necessitated different MGCF selection options within the network but still face various challenges in enabling flexibility in offnet call routing. For offnet calls, the border gateway control function (BGCF) is responsible for selecting the suitable MGCF. However, the existing solution supports only a single MGCF selection based on the routable number (RN) of the calling party. This posed a challenge as operators often had multiple MGCFs within the same circle and required the MGCF selection to be based on different parameters or headers of the received INVITE request. As a result, the solution lacked the flexibility to adapt to varying requirements and lacked granular control over MGCF selection. Additionally, in cases where multiple MGCFs were present, the prior solution lacked appropriate mechanisms for load balancing and weighted selection between these MGCFs. This deficiency impacts the overall performance and efficient resource utilization of the network. Consequently, the technical problem in the prior solution revolved around accommodating diverse MGCF selection options, ensuring proper load balancing, and weighted selection when multiple MGCFs existed in the network.

[0005] The aforementioned limitation resulted in suboptimal resource allocation and potential performance bottlenecks, as the network is unable to distribute the load evenly among the available MGCFs. Consequently, this inefficiency affects call quality, scalability, and overall network performance. Furthermore, the absence of comprehensive monitoring and management capabilities within the prior solution impeded efficient troubleshooting and maintenance. The existing solutions lacked robust tools to monitor MGCF performance, identify potential issues, and implement corrective measures on time which led to prolonged downtime, reduced service availability, and increased operational costs.

[0006] Thus, there exists an imperative need in the art for a technical solution that aims to address at least the above-mentioned technical issues by routing an offnet call efficiently and effectively.SUMMARY

[0007] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.

[0008] An aspect of the present disclosure may relate to a method for routing an offnet call. The method includes receiving, by a transceiver unit at a Breakout Gateway Control Function(BGCF), an offnet call request, wherein the offnet call request comprises a set of headers. Next, the method includes analysing, by an analysis unit at the BCGF, a list of selection combinations associated with one or more groups of Media Gateway Control Functions (MGCFs). Next, the method includes determining, by a processing unit at the BGCF, a target group of MGCF from the one or more groups of MGCFs based on matching of the list of selection combinations with the set of headers. Next, the method includes identifying, by an identification unit at the BGCF, a first MGCF from the target group of MGCF associated with the offnet call request. Next, the method includes transmitting, by the transceiver unit from the BGCF, to the first MGCF, the offnet call request. Next, the method includes receiving, by the transceiver unit at the BGCF, from the first MGCF, one or more failure responses associated with the offnet call request. Next, the method includes identifying, by the identification unit at the BGCF, in an event of receiving from the first MGCF at least a predefined number of failure responses for the offnet call request, a second MGCF from the target group of MGCF associated with the offnet call request. Thereafter, the method includes routing, by a routing unit at the BGCF, to the second MGCF, the offnet call associated with the offnet call request to the identified second MGCF.

[0009] In an exemplary aspect of the present disclosure, the offnet call is received by a user associated with a second network from a user associated with a first network.

[0010] In an exemplary aspect of the present disclosure, the offnet call is established between two different networks belonging to different service providers.

[0011] In an exemplary aspect of the present disclosure, each group of MGCF of the one or more groups of MGCFs is associated with at least one selection combination from the list of selection combinations, and wherein each selection combination from the list of selection combinations is based on one or more headers from the set of headers in the offnet call request.

[0012] In an exemplary aspect of the present disclosure, the first MGCF is identified based on at least one of a predefined MGCF priority and a predefined MGCF weightage associated with each MGCF from the target group of MGCF.

[0013] In an exemplary aspect of the present disclosure, the second MGCF is identified from the target group of MGCF based on at least one of a predefined MGCF priority associated with the second MGCF and a predefined MGCF weightage associated with the second MGCF in the target group.

[0014] In an exemplary aspect of the present disclosure, the method further comprises blacklisting, by the processing unit, the first MGCF for a predefined time period based on the predefined number of failure responses.

[0015] Another aspect of the present disclosure may relate to a system for routing an offnet call. The system comprises a Breakout Gateway Control Function (BGCF). The BGCF comprises a transceiver unit configured to receive an offnet call request, wherein the offnet call request comprises a set of headers; an analysis unit configured to analyse a list of selection combinations associated with one or more groups of Media Gateway Control Functions (MGCFs); a processing unit configured to determine a target group of MGCF from the one or more groups of MGCFs based on matching of the list of selection combinations with the set of headers; an identification unit configured to identify a first MGCF from the target group of MGCF associated with the offnet call request; the transceiver unit is further configured to transmit to the first MGCF, the offnet call request; the transceiver unit is further configured to receive, from the first MGCF, one or more failure responses associated with the offnet call request; the identification unit is further configured to identify, in an event of receiving from the first MGCF at least a predefined number of failure responses for the offnet call request, a second MGCF from the target group of MGCF associated with the offnet call request; and a routing unit configured to route to the second MGCF, the offnet call associated with the offnet call request to the identified second MGCF.

[0016] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for routing an offnet call, the instructions include executable code which, when executed by one or more units of a system, causes: a transceiver unit to receive an offnet call request, wherein the offnet call request comprises a set of headers; an analysis unit to analyse a list of selection combinations associated with one or more group of Media Gateway Control Functions (MGCFs); a processing unit to determine a target group of MGCF from the one or more group of MGCFs based on matching of the list of selection combinations with the set of headers; an identification unit to identify a first MGCF from the target group of MGCF associated with the offnet call request; the transceiver unit to transmit to the first MGCF, the offnet call request; the transceiver unit to receive from the first MGCF, one or more failure responses associated with the offnet call request; the identification unit to identify, in an event of receiving from the first MGCF at least a predefined number of failure responses for the offnet call request, a second MGCF from the target group of MGCF associated with the offnet call request;and a routing unit to route to the second MGCF, the offnet call associated with the offnet call request to the identified second MGCF.OBJECTS OF THE INVENTION

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

[0018] It is an object of the present disclosure to provide a system and a method for enabling flexibility in offnet call routing.

[0019] It is another object of the present disclosure to provide a solution that detects a negative response i.e., a failure response based on the offnet call request received by the first MGCF.

[0020] It is yet another object of the present disclosure to provide a solution that identifies a second MGCF from the target MGCF group based on a detection of the negative response i.e., the failure response.

[0021] It is yet another object of the present disclosure to provide flexibility in the selection of an MGCF from the multiple MGCFs defined in an MGCF group.

[0022] It is yet another object of the present disclosure to control load distribution by the BGCF.

[0023] It is yet another object of the present disclosure to facilitate the selection mechanism for pre-testing of a new MGCF that needs to be added to the network.DETAILED DESCRIPTION

[0024] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Also, the embodiments shown in thefigures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.

[0025] FIG. 1 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented, in accordance with exemplary implementations of the present disclosure.

[0026] FIG. 2 illustrates an exemplary block diagram of a system for routing an offnet call, in accordance with exemplary implementations of the present disclosure.

[0027] FIG. 3 illustrates a method flow diagram for routing an offnet call, in accordance with exemplary implementations of the present disclosure.

[0028] FIG. 4 illustrates a process flow diagram for routing an offnet call, in accordance with exemplary implementations of the present disclosure.

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

[0030] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter may 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.

[0031] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling descriptionfor implementing an exemplary embodiment. It should be understood that various changes may be made to the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0032] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.

[0033] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure.

[0034] The word “exemplary” and / or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the 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.

[0035] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein the processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a (Digital Signal Processing) DSP core, a controller, a microcontroller, Application Specific 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 systemaccording to the present disclosure. More specifically, the processor or processing unit is a hardware processor.

[0036] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and / or computing device or equipment, capable of implementing the features of the present disclosure. The user equipment / device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from at least one of a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.

[0037] As used herein, “storage unit” or “memory unit” refers to a machine or 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.

[0038] As used herein “interface” or “user interface” refers to a shared boundary across which two or more separate components of a system exchange information or data. The interface may also be referred to as a set of rules or protocols that define the communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.

[0039] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a micro-controller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.

[0040] As used herein the “transceiver unit” includes at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information, or a combination thereof between units / components within the system and / or connected with the system.

[0041] As used herein, offnet calls refer to telephone calls made between two different networks belonging to different operators or service providers. These operators are typically connected to each other through a point of interconnection (POI) and utilize the services of a media gateway control function (MGCF) for call termination. Offnet calls involve communication between users subscribed to different operators' networks, allowing them to establish voice connections outside their respective network boundaries. The patent specification may focus on specific aspects, technologies, or improvements related to the offnet call handling, routing, termination, interconnectivity, or other relevant areas in the field of telecommunications.

[0042] As used herein, a Breakout Gateway Control Function (BGCF) refers to a control function responsible or configured to manage the routing of calls and messages from one network to another network. In an exemplary implementation, the BGCF is responsible for routing calls or messages from a private network to a public network.

[0043] As discussed in the background section, the current known solutions for enabling an offnet call routing have several shortcomings such as the reliance on a single MGCF selection based on the routable number of the calling party, limited the solution's flexibility in accommodating operators with multiple MGCFs and diverse POI requirements. This lack of adaptability hindered seamless offnet call termination and interoperability between different operators. Additionally, the absence of comprehensive load balancing and weighted selection mechanisms between multiple MGCFs resulted in suboptimal resource utilization and potential congestion issues. Furthermore, the prior solution lacked robust monitoring and management capabilities, impeding timely troubleshooting and maintenance activities.

[0044] The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by disclosing an innovative solution for Media Gateway Control Function (MGCF) selection, health monitoring of MGCF and network, and traffic distribution in telecommunication networks. The solution leverages various headers received in an INVITE request, including the 'P-Access-network-information' header, caller's identity and / ordomain in the 'P-Asserted-Identity' header, caller's identity and / or domain in the 'From' header, callee's identity and / or domain in the 'To' header, and ‘tgrp’ along with trunk-context. These headers are used individually or in combination to determine the most suitable MGCF for managing a specific call, ensuring efficient call routing and optimal resource utilization. Further, the proposed solution also introduces support for multiple MGCFs by maintaining a well- organized list of MGCFs that cater to specific requirements. This enables load balancing and scalability within the network, allowing for better distribution of call traffic across available MGCF resources. Further, as disclosed by the present disclosure to maintain uninterrupted service delivery, the system includes robust health monitoring mechanisms for MGCFs. It incorporates both active and pro-active monitoring approaches. Further, active monitoring regularly checks the operational status of MGCFs, ensuring prompt detection of any anomalies. Pro-active monitoring may employ a predictive algorithm to anticipate potential failures and take proactive measures to prevent service disruptions. By monitoring the health of MGCFs, the system minimizes service impact and provides a reliable call-handling infrastructure. Additionally, the solution implements traffic distribution based on the priority and weightage assigned to each MGCF. By configuring specific priority levels and weightage against each MGCF, the system intelligently distributes call traffic, ensuring that calls are routed to the most suitable MGCF based on predefined rules. This dynamic traffic distribution optimizes resource utilization and enhances overall network performance, delivering an improved telecommunication experience.

[0045] FIG. 1 illustrates an exemplary block diagram of a computing device

[0100] (also referred to herein as a computer system

[0100] ) 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

[0100] may also implement a method for routing an offnet call utilising the system. In another implementation, the computing device

[0100] itself implements the method for routing the offnet call using one or more units configured within the computing device

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

[0046] The computing device

[0100] may include a bus

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

[0104] or processing unit coupled with a bus

[0102] for processing information. The hardware processor

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

[0100] may also include a main memory

[0106] , such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus

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

[0104] , The main memory

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

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

[0104] , render the computing device

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

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

[0108] or other static storage device coupled to the bus

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

[0104] ,

[0047] A storage device

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

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

[0100] may be coupled via the bus

[0102] to a display

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

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

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

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

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

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

[0112] , This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.

[0048] The computing device

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

[0100] causes or programs the computing device

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

[0100] in response to the processor

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

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

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

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

[0106] causes the processor

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

[0049] The computing device

[0100] also may include a communication interface

[0118] coupled to the bus

[0102] , The communication interface

[0118] provides a two-way datacommunication coupling to a network link

[0120] that is connected to a local network

[0122] , For example, the communication interface

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

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

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

[0050] The computing device

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

[0120] , and the communication interface

[0118] , In the Internet example, a server

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

[0128] , the Internet Service Provider (ISP)

[0126] , the Host

[0124] , the local network

[0122] and the communication interface

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

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

[0110] , or other nonvolatile storage for later execution.

[0051] The computing device

[0100] encompasses a wide range of electronic devices capable of processing data and performing computations. Examples of computing device

[0100] include, but are not limited only to, personal computers, laptops, tablets, smartphones, servers, and embedded systems. The devices may operate independently or as part of a network and can perform a variety of tasks such as data storage, retrieval, and analysis. Additionally, computing device

[0100] may include peripheral devices, such as monitors, keyboards, and printers, as well as integrated components within larger electronic systems, showcasing their versatility in various technological applications.

[0052] As used herein, an offnet call may happen between the two different networks belonging to different operators or service providers. These operators or service providers are connected to each other via a media gateway control function (MGCF).

[0053] As used herein, a media gateway control function (MGCF) may connect two different networks such as IP multimedia subsystem (IMS) and public switching telephone networks (PSTN). In other words, the MGCF is a key component in telecommunication networks to facilitate the transition from traditional circuit-switched networks to packet-switched networks.

[0054] As used herein, an IMS network refers to an Internet Protocol (IP) Multimedia Subsystem (IMS) network that provides an architectural framework for delivering IP-based multimedia services. For example, the IMS network is majorly used for interactive services like Voice over New Radio (VoNR), Video Conferencing, and the like over IP networks. IMS network enables secure and reliable multimedia communications between diverse devices across diverse networks. Furthermore, the IMS network provides a unified infrastructure and common mechanisms for controlling, manipulating, routing, and managing sessions. The IMS architecture includes a plurality of components. The plurality of components includes but is not limited to application servers, Home Subscriber Server (HSS), a Call Session Control Function (CSCF), a Signalling Gateway (SGW), a Media Gateway Control Function (MGCF), a Media Resource Functions (MRF), User Data Repository (UDR), a Breakout Gateway Control Function (BGCF), IP Network, and Public Switched Telephone Network.

[0055] The application servers are applications providing services, such as telephone call control, call continuity, conference calling, and supplementary service configuration. The HSS is the master database that maintains all user profile information used to authenticate and authorize subscribers. The Call Session Control Function (CSCF) is configured for controlling sessions between endpoints (referred to as terminals) and applications. The User Data Repository (UDR) is configured to store user-related information. The Breakout Gateway Control Function (BGCF) is configured to determine the network for routing calls to the public switched telephone networks (PSTN). The signalling Gateway (SGW) is responsible for bridging the traditional Public Switched Telephone Network (PSTN) with an IP -based IMS network. The function of SGW includes but is not limited to protocol conversion, network interworking, signalling transport, security, load balancing, and traffic management. The Media Gateway Control Function (MGCF) is configured to control media gateway (MGW) and to facilitate communication between IP -based IMS networks and circuit- switched networks such as public switched telephone networks (PSTN). The Media Resource Functions (MRF) provides media-related tasks and services (e.g., playing media, and announcements) to the user. The IP network uses internet protocol for communication between user devices. The Gateway in the IMS network acts as a bridge between the IMS network and other networks, such as PSTN, and mobile networks. The PSTN integration in the IMS network is an integration for ensuring interoperability between the traditional telephony services and model IP -based services.

[0056] As used herein, a breakout gateway control function (BGCF) may determine the network where PSTN breakouts occur. When a user initiates a call or communication session thatinvolves both IMS and PSTN, the BGCF may perform routing of the signalling appropriately by selecting the MGCF.

[0057] As used herein, session initiation protocol (SIP) is a signalling protocol used for setting up, maintaining, and tearing down multimedia communication sessions such as voice and video calls over the Internet.

[0058] Referring to FIG. 2, an exemplary block diagram of a system

[0200] for routing an offnet call, is shown, in accordance with the exemplary implementations of the present disclosure. The system

[0200] comprises at least one breakout gateway control function (BGCF)

[0202] , The breakout gateway control function (BGCF)

[0202] comprises at least one transceiver unit

[0204] , at least one analysis unit

[0206] , at least one processing unit

[0208] , at least one identification unit

[0210] , and at least one routing unit

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

[0200] are assumed to be connected to each other unless otherwise indicated below. As shown in the figures all units shown within the system should also be assumed to be connected to each other. Also, in FIG. 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. In an implementation, the system

[0200] may reside in a server or a network entity. In another implementation, the system

[0200] may be present in a user device to implement the features of the present disclosure. The system

[0200] may be a part of the user device / or may be independent of but in communication with the user device (may also be referred to herein as a UE). In yet another implementation, the system

[0200] may reside partly in the server / network entity and partly in the user device.

[0059] The system

[0200] is configured for routing the offnet call, with the help of the interconnection between the components / units of the system

[0200] , The system

[0200] includes the breakout gateway control function (BGCF)

[0202] , To route the offnet call, the BGCF

[0202] includes a transceiver unit

[0204] configured to receive an offnet call request, wherein the offnet call request includes a set of headers. The transceiver unit

[0204] of the system

[0200] may receive the offnet call request. The offnet call request comprises an invite request associated with the offnet call, wherein the invite request at least comprises the set of headers. In a non-limiting implementation of the present disclosure, the header information may comprise at least one of the ‘P-Access-network-information’ header, caller’s identity and / or domain in the ‘P-Asserted- Identity’ header, caller’s identity and / or domain in the ‘From’ header, Callee’s identity and / or domain in the ‘To’ header, trunk group (tgrp) along with trunk-context. The offnet call isestablished between two different networks belonging to different service providers. The first network may include but is not limited to, Internet Protocol Multimedia Subsystem (IMS) network, and the second network may include, but is not limited to, Public Switch Telephone Network (PSTN).

[0060] In an exemplary aspect, the P-Access-Network-Information header is a private header used in a session initiation protocol (SIP) to convey information about the access network. It may include details associated with the type and identity of the access network.

[0061] In an exemplary aspect, the P-Asserted-Identity header is a SIP header used to convey the identity of the user device (operated by a user) and who is authenticated and authorized by the network.

[0062] In an exemplary aspect, the trunk group (tgrp) parameter is used to specify a trunk group in telephone communication. As used herein, trunk groups are collections of circuits or channels that are used to connect two switching systems (e.g., network components to route calls or data from one point to another point). The trunk group enables the routing of multiple calls through a single pathway. As used herein, the trunk context refers to a framework or an environment where the trunk groups operate. Trunk context includes the configurations, policies, and rules to manage and use the trunk groups.

[0063] The BGCF

[0202] of the system

[0200] further includes an analysis unit

[0206] configured to analyse a list of selection combinations associated with one or more groups of media gateway control functions (MGCFs). The analysis unit

[0206] may analyse the list of selection combinations associated with the one or more groups of MGCFs. In an exemplary implementation, each of the one or more groups of MGCFs is associated with at least one selection combination from the list of selection combinations, wherein each selection combination from the list of selection combinations is based on one or more headers from the set of headers in the offnet call request. The list of selection combinations may be based on the different headers’ information such as (e.g., P- Access-network-information’ header, caller’s identity, and / or domain in the ‘P- Asserted-Identity’ header), a list of serving MGCFs, traffic load distribution and weightage of MGCF, healthy and active MGCFs.

[0064] The BGCF

[0202] of the system

[0200] further comprises a processing unit

[0208] configured to determine a target group of MGCF from the one or more groups of MGCFs based on a matching of the list of selection combinations with the set of headers. The processing unit

[0208] may determine the target group of MGCF from the one or more groups of MGCFs based on matching the list of selection combinations with the set of headers. As used herein, the target group refers to a group of MGCFs eligible and capable of managing the offnet calls, wherein the eligibility is determined based on the matching of the list of selection combinations with the set of headers. In an exemplary aspect, there may be different MGCF groups such as MGCF group 1, MGCF group 2, and MGCF group 3 in the network. As used herein, the MGCF groups correspond to a group or cluster of one or more MGCFs available in the IMS network. The processing unit

[0208] may determine the target group such as MGCF group 1 based on matched selection combinations, such as serving MGCF for specific requested service calls, traffic load, weightage of MGCF, healthy and active MGCFs, and header information. Thus, the list of selection combinations associated with one or more groups of Media Gateway Control Functions (MGCF) comprises different strategies or configurations to select and manage MGCF instances in the communication network. For example, a particular MGCF from a group of MGCFs may be determined based on the header information available in the offnet call request, based on the traffic handling capability of the MGCF, based on the region or location of the request, and the like.

[0065] The BGCF

[0202] of the system

[0200] further comprises an identification unit

[0210] configured to identify the first MGCF from the target group of MGCF associated with the offnet call request. Further, the identification unit

[0210] may identify the first MGCF from the target group of MGCF associated with the offnet call request. In an exemplary implementation of the present disclosure, the first MGCF is identified from the target group of MGCF at the BGCF

[0202] based on at least one of a predefined MGCF priority and a predefined MGCF weightage associated with each MGCF from the target group of MGCF. Further, the second MGCF is identified from the target group of MGCF based on at least one of a predefined MGCF priority associated with the second MGCF and a predefined MGCF weightage associated with the second MGCF in the target group. In an exemplary aspect, the weightage and priority are predefined by the network administrator or an authorised person. In an exemplary aspect, the weightage and priority are customized and changed dynamically based on traffic load and demand. The identification unit

[0210] may send information about the identified first MGCF from the target group of MGCF to the processing unit

[0208] and transmitter unit

[0204] for further processing. In an exemplary aspect, each group may have pre-defined numbers of MGCFs, such as 10 MGCF. In an exemplary aspect, the number of MGCFs in a group may increase or decrease based on network requirements.

[0066] The transceiver unit

[0204] of the BGCF

[0202] is further configured to transmit to the first MGCF, the offnet call request. Based on the received information of the identified firstMGCF from the target MGCF group, the transceiver unit

[0204] may transmit the offnet call request to the first MGCF.

[0067] The transceiver unit

[0204] is further configured to receive from the first MGCF, one or more failure responses associated with the offnet call request. After transmitting the offnet call request to the first MGCF, the transceiver unit

[0204] may receive one or more failure responses associated with the offnet call request from the first MGCF. In an implementation, the transceiver unit

[0204] at the BGCF

[0202] may receive one or more failure responses, or negative responses or no response due to such as, but not limited to, any network issues, unavailability of the selected MGCF, not in service of the selected MGCF and the like.

[0068] The BGCF

[0202] of the system

[0200] further comprises the identification unit

[0210] , The identification unit

[0210] is further configured to identify, in an event of receiving from the first MGCF at least a predefined number of failure responses for the offnet call request, a second MGCF from the target group of MGCF associated with the offnet call request. After receiving a failure / negative response or no response, the identification unit

[0210] may identify the second MGCF from the target group of MGCF associated with the offnet call request. The second MGCF may be identified after receiving from the first MGCF, the at least predefined number of failure responses for the offnet call request. In an implementation, the processing unit

[0208] may process the one or more failure responses for the offnet call request from the first MGCF. After receiving the predefined number of failure responses for the offnet call request, the processing unit

[0208] may trigger the identification unit

[0210] for identifying the second MGCF from the target group of MGCF. The processing unit

[0208] may trigger the identification unit

[0210] after the predefined number of failure responses crosses or reaches a pre-defined threshold value, which is set by the network administrator. In an implementation, the processing unit

[0208] is further configured to blacklist the first MGCF for a predefined time based on receiving the predefined number of failure responses.

[0069] The BGCF

[0202] of the system

[0200] further comprises a routing unit

[0212] configured to route to the second MGCF, the offnet call associated with the offnet call request. Thereafter, the routing unit

[0212] may route the offnet call associated with the offnet call request to the second MGCF in the network based on identifying the second MGCF from the target group of MGCF.

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

[0071] Referring to FIG. 3, an exemplary method flow diagram

[0300] for routing an offnet call, in accordance with exemplary implementations of the present disclosure is shown. In an implementation, the method

[0300] is performed by the system

[0200] , Further, in an implementation, the system

[0200] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 3, the method

[0300] starts at step

[0302] ,

[0072] At step

[0304] , the method

[0300] , as disclosed by the present disclosure, comprises receiving, by a transceiver unit

[0204] at a Breakout Gateway Control Function (BGCF)

[0202] , an offnet call request, wherein the offnet call request comprises a set of headers. The method

[0300] implemented by the transceiver unit

[0204] at the BGCF

[0202] of the system

[0200] may receive the offnet call request. The offnet call request comprises an invite request associated with the offnet call, wherein the invite request at least comprises a set of headers. As used herein, the header refers to crucial information or key information in a message required to process, manage, or route the message (e.g., invite request message). In an implementation of the present disclosure, the set of headers or header information may comprise at least one of the ‘P-Access-network-information’ header, caller’s identity and / or domain in the ‘P-Asserted-Identity’ header, caller’s identity and / or domain in the ‘From’ header, callee’s identity and / or domain in the ‘To’ header, trunk group (tgrp) along with trunk-context. In an implementation of the present disclosure, the offnet call is received by a user associated with a second network from a user associated with a first network. The offnet call is established between two different networks belonging to different service providers. The first network may be such as, but not limited to, an IMS network, and the second network may be, such as, but not limited to, a PSTN network.

[0073] Next, at step

[0306] , the method

[0300] as disclosed by the present disclosure comprises analysing, by an analysis unit

[0206] at the BCGF

[0202] , a list of selection combinations associated with one or more groups of Media Gateway Control Functions (MGCFs). The method

[0300] implemented by the analysis unit

[0206] at the BCGF

[0202] may analyse the list of selection combinations associated with the one or more groups of Media Gateway Control Functions (MGCFs). In an exemplary implementation of the present disclosure, each of the one or more groups of MGCFs is associated with at least one selection combination from the list of selection combinations, and wherein each selection combination from the list of selection combinations is based on one or more headers from the set of headers in the offnet call request. The list of selection combinations may be based on the different header’s information such as (e.g., the ‘P-Access- network-information’ header, caller’s identity, and / or domain in the ‘P-Asserted-Identity’ header), the list of serving MGCFs, traffic load distribution and weightage of MGCF, healthy and active MGCFs.

[0074] Next, at step

[0308] , the method

[0300] as disclosed by the present disclosure comprises determining, by a processing unit

[0208] at the BGCF

[0202] , a target group of MGCF from the one or more groups of MGCFs based on matching of the list of selection combinations with the set of headers. The method

[0300] implemented by the processing unit

[0208] at the BGCF

[0202] may determine the target group of MGCF from the one or more groups of MGCFs based on matching the list of selection combinations with the set of headers. In an exemplary aspect, there may be different MGCF groups such as MGCF group 1, MGCF group 2, and MGCF group 3 in the network. The processing unit

[0208] may determine a target group such as MGCF group 1 based on matched selection combinations such as serving MGCF for specific requested service calls, traffic load, weightage of MGCF, healthy and active MGCFs, and header information.

[0075] Next, at step

[0310] , the method

[0300] , as disclosed by the present disclosure, comprises identifying, by an identification unit

[0210] at the BGCF

[0202] , a first MGCF from the target group of MGCF associated with the offnet call request. The method

[0300] implemented by the identification unit

[0210] at the BGCF

[0202] may identify the first MGCF from the target group of MGCF associated with the offnet call request. In an exemplary implementation of the present disclosure, the first MGCF is identified from the target group of MGCF at the BGCF

[0202] based on at least one of a predefined MGCF priority and a predefined MGCF weightage associated with each MGCF from the target group of MGCF. Further, the second MGCF is identified from the target group of MGCF based on at least one of a predefined MGCF priority associated with the second MGCF and a predefined MGCF weightage associated with the second MGCF in the target group. As used herein, MGCF priority refers to a level of importance assigned to MGCF within a network. The MGCF priority determines the order in which the MGCF is used for call handling or call routing. As used herein, MGCF weightage refers to the weight assigned to the MGCF tomanage the load or network traffic. The MGCF weightage determines the proportion of traffic managed by each MGCF in the network. In an exemplary aspect, the weightage and priority are predefined by a network administrator or an authorised person. In an exemplary aspect, the weightage and priority are customized and changed dynamically based on traffic load and demand. The identification unit

[0210] may send information related to the identified first MGCF from the target group of MGCF to the processing unit

[0208] and transmitter unit

[0204] for further processing. In an exemplary aspect, each group may have pre-defined numbers of MGCF s, such as, but not limited to, ten MGCFs. In an exemplary aspect, the number of MGCFs in a group may increase or decrease based on network requirements.

[0076] Next, at step

[0312] , the method

[0300] , as disclosed by the present disclosure, comprises transmitting, by the transceiver unit

[0204] from the BGCF

[0202] , to the first MGCF, the offnet call request. Further, the transceiver unit

[0204] from the BGCF, based on the received information of the identified first MGCF from the target MGCF group, may transmit the offnet call request to the first MGCF.

[0077] Next, at step

[0314] , the method

[0300] , as disclosed by the present disclosure, comprises receiving, by the transceiver unit

[0204] at the BGCF

[0202] , from the first MGCF, one or more failure responses associated with the offnet call request. The method

[0300] implemented by the transceiver unit

[0204] at the BGCF

[0202] may receive one or more failure responses associated with the offnet call request from the first MGCF. In an implementation, the transceiver unit

[0204] at the BGCF

[0202] may receive one or more failure responses or negative responses, or no response due to such as, but not limited to, any network issues, unavailability of the selected MGCF, not in service of the selected MGCF and the like. As used herein, the failure response refers to an indication (via a message) that the selected MGCF encountered an issue or failure while attempting to manage services (e.g., call routing) in the network.

[0078] Next, at step

[0316] , the method

[0300] , as disclosed by the present disclosure, comprises identifying, by the identification unit

[0210] at the BGCF

[0202] , in an event of receiving from the first MGCF at least a predefined number of failure responses for the offnet call request, a second MGCF from the target group of MGCF associated with the offnet call request. After receiving a failure / negative response or no response, the identification unit

[0210] may identify the second MGCF from the target group of MGCF associated with the offnet call request in the event of receiving from the first MGCF at least a predefined number of failure responses for the offnet call request. In an implementation, the processing unit

[0208] may process the one or more failure responses for the offnet call request received from the first MGCF. After receiving the predefinednumber of failure responses for the offnet call request, the processing unit

[0208] may trigger the identification unit

[0210] for identifying the second MGCF from the target group of MGCF. The processing unit

[0208] may trigger the identification unit

[0210] after the predefined number of failure responses crosses or reaches a pre-defined threshold value, which is set by a network administrator. In an implementation, the processing unit

[0208] is further configured to blacklist the first MGCF for a predefined time based on the predefined number of failure responses.

[0079] Next, at step

[0318] , the method

[0300] , as disclosed by the present disclosure, comprises automatic routing, by a routing unit

[0212] at the BGCF

[0202] , to the second MGCF, the offnet call associated with the offnet call request to the identified second MGCF. Thereafter, the method

[0300] implemented by the routing unit

[0212] at the BGCF

[0202] may route the offnet call associated with the offnet call request to the second MGCF in the network based on identifying the second MGCF from the target group of MGCF. In an exemplary implementation, the steps from

[0304] to

[0318] are executed automatically to perform automatic routing of the offnet call minimizing the manual intervention.

[0080] Thereafter, the method

[0300] terminates at step

[0320] ,

[0081] FIG. 4 illustrates a process flow

[0400] diagram for routing an offnet call, in accordance with exemplary implementations of the present disclosure. In an exemplary aspect, the process flow

[0400] is implemented by the system

[0200] ,

[0082] At step S2, different combinations for MGCFs selection are configured for BGCF

[0202] , In an exemplary aspect, the combinations may correspond to the selection of header information (e.g., ‘P-Access-network-information’ header, caller’s identity, and / or domain in the ‘P-Asserted-Identity’ header), weightage, priority, healthy and active number of MGCF.

[0083] At step S4, MGCF groups are defined with multiple MGCF’s with their priority & weightage. In an exemplary aspect, each group may have a pre-configured number of MGCFs, such as, but not limited to, ten MGCFs. In an exemplary aspect, each group may have a similar number or a different number of MGCFs.

[0084] At step S6, the offnet call is received at the BGCF

[0202] , A user connected to a first network may call another user, wherein another user is connected to the second network. The first and second networks are different networks.

[0085] At step S8, checking of the best match combination is performed. In an implementation, when the offnet call is received at BGCF

[0202] , the BGCF

[0202] checks the best match combination for the selection of MGCF. The best match combination may be based on call request, INVITE request, and header information, which may serve the request.

[0086] At step S10, the selection of the MGCF from MGCF group 1 is performed. In an implementation, the BGCF

[0202] then selects one MGCF, based on the priority and weightage of the MGCF, from the best match MGCF group. The BGCF

[0202] then forwards the request to the selected MGCF. If there is no response from the selected MGCF and further multiple failures are observed from the same MGCF then the MGCF may be blacklisted by the BGCF

[0202] , and no further request may be sent to that MGCF until the blacklist time expires. Then, the BGCF

[0202] may send a request to the next MGCF in the same MGCF group. In an exemplary aspect, if a new MGCF is to be added, it can be added to the existing MGCF group list to start sending the traffic. Further, if a new MGCF is to be pre-tested, then by defining the MGCF selection combination based on the test numbers, this can be easily achieved.

[0087] At step S12, the selection of the MGCF from MGCF group 2 is performed. The BGCF

[0202] may select the MGCF from the MGCF group 2 if MGCF group 1 is unable to serve the offnet call request.

[0088] At step S14, the selection of the MGCF from MGCF group 3 is performed. The BGCF

[0202] may select the MGCF from the MGCF group 3 if MGCF group 2 is unable to serve the offnet call request.

[0089] In an exemplary aspect, the BGCF

[0202] may perform the same process for the MGCF group 2 and MGCF group 3, as performed for MGCF group 1 in step 10.

[0090] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for routing an offnet call, the instructions include executable code which, when executed by one or more units of a system, causes: a transceiver unit

[0204] of the system to receive an offnet call request, wherein the offnet call request comprises a set of headers. Further, the instruction when executed causes an analysis unit

[0206] of the system to analyse a list of selection combinations associated with one or more group of Media Gateway Control Functions (MGCFs). Further, the instruction when executed causes a processing unit

[0208] of the system todetermine a target group of MGCF from the one or more group of MGCFs based on matching of the list of selection combinations with the set of headers. Further, the instruction when executed causes an identification unit to identify a first MGCF from the target group of MGCF associated with the offnet call request. Further, the instruction when executed causes the transceiver unit

[0204] of the system to transmit to the first MGCF, the offnet call request. Further, the instruction when executed causes the transceiver unit

[0204] of the system to receive from the first MGCF, one or more failure responses associated with the offnet call request. Further, the instruction when executed causes the identification unit

[0210] of the system to identify, in an event of receiving from the first MGCF at least a predefined number of failure responses for the offnet call request, a second MGCF from the target group of MGCF associated with the offnet call request. Further, the instruction when executed causes a routing unit

[0212] of the system to route to the second MGCF, the offnet call associated with the offnet call request to the identified second MGCF.

[0091] As is evident from the above, the present disclosure provides a technically advanced solution for enabling flexibility in the offnet call routing. The present solution for MGCF selection, based on flexibility and the ability to define multiple MGCFs in an MGCF group, represents a significant technical advancement in telecommunication networks. This solution introduces a new level of flexibility by allowing the selection mechanism to consider multiple MGCFs for call handling. It provides ease in adding or removing MGCFs from the network, enabling network administrators to efficiently manage and scale their infrastructure based on demand. This technical effect facilitates network expansion, upgrades, and maintenance without disrupting ongoing services, resulting in improved network management efficiency. Moreover, the solution grants full control of load distribution to the Border Gateway Control Function (BGCF). This technical advancement empowers network operators to dynamically allocate call traffic among multiple MGCFs, optimizing resource utilization and ensuring a balanced distribution of workload. By effectively managing the distribution of call traffic, the system improves call handling efficiency, reduces congestion, and enhances overall network performance. Additionally, the selection mechanism's ability to pre-test new MGCFs before adding them to the network offers a valuable technical effect. Network administrators can easily evaluate the performance and compatibility of new MGCFs without impacting existing services. This streamlined testing process enables efficient integration of new MGCFs into the network and ensures seamless service transitions.

[0092] In summary, the present solution's technical advancements, including flexibility in MGCF selection, the ability to define multiple MGCFs in an MGCF group, ease in adding or removing MGCFs from the network, and load distribution control by the BGCF, provide tangibletechnical effects. These effects encompass improved scalability, enhanced network management, optimized resource utilization, efficient integration of new MGCFs, and overall enhancement of telecommunication service quality and performance.

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

Claims

I / We Claim:

1. A method for routing an offnet call, the method comprising: receiving, by a transceiver unit [204] at a Breakout Gateway Control Function (BGCF) [202], an offnet call request, wherein the offnet call request comprises a set of headers; analysing, by an analysis unit [206] at the BCGF [202], a list of selection combinations associated with one or more groups of Media Gateway Control Functions (MGCFs); determining, by a processing unit [208] at the BGCF [202], a target group of MGCF from the one or more groups of MGCFs based on matching of the list of selection combinations with the set of headers; identifying, by an identification unit [210] at the BGCF [202], a first MGCF from the target group of MGCF associated with the offnet call request; transmitting, by the transceiver unit [204] from the BGCF [202], to the first MGCF, the offnet call request; receiving, by the transceiver unit [204] at the BGCF [202], from the first MGCF, one or more failure responses associated with the offnet call request; identifying, by the identification unit [210] at the BGCF [202], in an event of receiving from the first MGCF at least a predefined number of failure responses for the offnet call request, a second MGCF from the target group of MGCF associated with the offnet call request; and routing, by a routing unit [212] at the BGCF [202], to the second MGCF, the offnet call associated with the offnet call request to the identified second MGCF.

2. The method as claimed in claim 1, wherein the offnet call is received by a user associated with a second network from a user associated with a first network.

3. The method as claimed in claim 1, wherein the offnet call is established between two different networks belonging to different service providers.

4. The method as claimed in claim 1, wherein each group of MGCF of the one or more group of MGCFs is associated with at least one selection combination from the list of selection combinations, and wherein each selection combination from the list of selection combinations is based on one or more headers from the set of headers in the offnet call request.

5. The method as claimed in claim 1, wherein the first MGCF is identified based on at least one of a predefined MGCF priority and a predefined MGCF weightage associated with each MGCF from the target group of MGCF.

6. The method as claimed in claim 1, wherein the second MGCF is identified from the target group of MGCF based on at least one of a predefined MGCF priority associated with the second MGCF and a predefined MGCF weightage associated with the second MGCF in the target group.

7. The method as claimed in claim 1, wherein the method comprises blacklisting, by the processing unit [208], the first MGCF for a predefined time period based on the predefined number of failure responses.

8. A system for routing an offnet call, the system comprising: a Breakout Gateway Control Function (BGCF) [202] comprising: a transceiver unit [204] configured to receive an offnet call request, wherein the offnet call request comprises a set of headers; an analysis unit [206] configured to analyse a list of selection combinations associated with one or more groups of Media Gateway Control Functions (MGCFs); a processing unit [208] configured to determine a target group of MGCF from the one or more groups of MGCFs based on matching of the list of selection combinations with the set of headers; an identification unit [210] configured to identify a first MGCF from the target group of MGCF associated with the offnet call request; the transceiver unit [204] is further configured to transmit to the first MGCF, the offnet call request; the transceiver unit [204] is further configured to receive, from the first MGCF, one or more failure responses associated with the offnet call request; the identification unit [210] is further configured to identify, in an event of receiving from the first MGCF at least a predefined number of failure responses for the offnet call request, a second MGCF from the target group of MGCF associated with the offnet call request; and a routing unit [212] configured to route to the second MGCF, the offnet call associated with the offnet call request to the identified second MGCF.

9. The system as claimed in claim 8, wherein the offnet call is received by a user associated with a second network from a user associated with a first network.

10. The system as claimed in claim 8, wherein the offnet call is established between two different networks belonging to different service providers.

11. The system as claimed in claim 8, wherein each group of MGCF of the one or more group of MGCFs is associated with at least one selection combination from the list of selection combinations, and wherein each selection combination from the list of selection combinations is based on one or more headers from the set of headers in the offnet call request.

12. The system as claimed in claim 8, wherein the first MGCF is identified from the target group of MGCF at the BGCF [202] based on at least one of a predefined MGCF priority and a predefined MGCF weightage associated with each MGCF from the target group of MGCF.

13. The system as claimed in claim 8, wherein the second MGCF is identified from the target group of MGCF based on at least one of a predefined MGCF priority associated with the second MGCF and a predefined MGCF weightage associated with the second MGCF in the target group.

14. The system as claimed in claim 8, wherein the processing unit [208] is further configured to blacklist the first MGCF for a predefined time period based on the predefined number of failure responses.

15. A non-transitory computer-readable storage medium storing instruction for routing an offnet call, the storage medium comprising executable code which, when executed by one or more units of a system, causes: a transceiver unit [204] to receive an offnet call request, wherein the offnet call request comprises a set of headers; an analysis unit [206] to analyse a list of selection combinations associated with one or more group of Media Gateway Control Functions (MGCFs); a processing unit [208] to determine a target group of MGCF from the one or more group of MGCFs based on matching of the list of selection combinations with the set of headers;an identification unit [210] to identify a first MGCF from the target group of MGCF associated with the offnet call request; the transceiver unit [204] to transmit to the first MGCF, the offnet call request; the transceiver unit [204] to receive from the first MGCF, one or more failure responses associated with the offnet call request; the identification unit [210] to identify, in an event of receiving from the first MGCF at least a predefined number of failure responses for the offnet call request, a second MGCF from the target group of MGCF associated with the offnet call request; and a routing unit [212] to route to the second MGCF, the offnet call associated with the offnet call request to the identified second MGCF.

Images