FORM 2
THE PATENTS ACT, 1970
(39 OF 1970)
&
5 THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
10
“METHOD AND SYSTEM FOR ROUTING AN OFFNET
CALL”
15
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr.
Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat,
India.
20
The following specification particularly describes the invention and the manner in
which it is to be performed.
2
METHOD AND SYSTEM FOR ROUTING AN OFFNET CALL
FIELD OF THE DISCLOSURE
5 [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
10
[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
15 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
20 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
25 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
3
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
5 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 NDAs specifying how these offnet calls should
10 be terminated at the point of interconnection (POI), the varying requirements of
different operators at 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
15 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.
20 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,
25 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
30 distribute the load evenly among the available MGCFs. Consequently, this
4
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
5 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
10 solution that aims to address at least the above-mentioned technical issues by
routing an offnet call efficiently and effectively.
SUMMARY
15 [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.
20 [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
25 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
30 group of MGCF associated with the offnet call request. Next, the method includes
5
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
5 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.
10
[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.
15 [00010] In an exemplary aspect of the present disclosure, the offnet call is
established between two different networks belonging to different service
providers.
[00011] In an exemplary aspect of the present disclosure, each group of
20 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.
25 [00012] 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.
[00013] In an exemplary aspect of the present disclosure, the second MGCF
30 is identified from the target group of MGCF based on at least one of a predefined
6
MGCF priority associated with the second MGCF and a predefined MGCF
weightage associated with the second MGCF in the target group.
[00014] In an exemplary aspect of the present disclosure, the method further
5 comprises blacklisting, by the processing unit, the first MGCF for a predefined time
period based on the predefined number of failure responses.
[00015] Another aspect of the present disclosure may relate to a system for
routing an offnet call. The system comprises a Breakout Gateway Control Function
10 (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
15 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
20 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
25 offnet call request to the identified second MGCF.
[00016] Yet another aspect of the present disclosure may relate to a nontransitory computer readable storage medium storing instructions for routing an
offnet call, the instructions include executable code which, when executed by one
30 or more units of a system, causes: a transceiver unit to receive an offnet call request,
7
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
5 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
10 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.
15
OBJECTS OF THE INVENTION
[00017] Some of the objects of the present disclosure, which at least one
embodiment disclosed herein satisfies are listed herein below.
20
[00018] It is an object of the present disclosure to provide a system and a
method for enabling flexibility in offnet call routing.
[00019] It is another object of the present disclosure to provide a solution that
25 detects a negative response i.e., a failure response based on the offnet call request
received by the first MGCF.
[00020] 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
30 of the negative response i.e., the failure response.
8
[00021] 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.
5 [00022] It is yet another object of the present disclosure to control load
distribution by the BGCF.
[00023] 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
10 network.
DETAILED DESCRIPTION
[00024] The accompanying drawings, which are incorporated herein, and
15 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 the figures are
20 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.
25
[00025] 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.
9
[00026] FIG. 2 illustrates an exemplary block diagram of a system for routing
an offnet call, in accordance with exemplary implementations of the present
disclosure.
5 [00027] FIG. 3 illustrates a method flow diagram for routing an offnet call,
in accordance with exemplary implementations of the present disclosure.
[00028] FIG. 4 illustrates a process flow diagram for routing an offnet call,
in accordance with exemplary implementations of the present disclosure.
10
[00029] The foregoing shall be more apparent from the following more
detailed description of the disclosure.
DETAILED DESCRIPTION
15
[00030] In the following description, for the purposes of explanation, various
specific details are set forth in order to provide a thorough understanding of
embodiments of the present disclosure. It will be apparent, however, that
embodiments of the present disclosure may be practiced without these specific
20 details. Several features described hereafter 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.
25 [00031] 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 description for implementing an exemplary
embodiment. It should be understood that various changes may be made to the
10
function and arrangement of elements without departing from the spirit and scope
of the disclosure as set forth.
[00032] Specific details are given in the following description to provide a
5 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.
10
[00033] 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
15 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.
[00034] The word “exemplary” and/or “demonstrative” is used herein to
20 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
25 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.
30
11
[00035] 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
5 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
10 functionality that enables the working of the system according to the present
disclosure. More specifically, the processor or processing unit is a hardware
processor.
[00036] As used herein, “a user equipment”, “a user device”, “a smart-user15 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
20 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
25 such unit(s) which are required to implement the features of the present disclosure.
[00037] 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 computer30 readable medium includes read-only memory (“ROM”), random access memory
12
(“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.
5
[00038] 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
10 one or more units with each other, which also includes the methods, functions, or
procedures that may be called.
[00039] All modules, units, components used herein, unless explicitly
excluded herein, may be software modules or hardware processors, the processors
15 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 microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable
Gate Array circuits (FPGA), any other type of integrated circuits, etc.
20
[00040] 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.
25
[00041] 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
30 termination. Offnet calls involve communication between users subscribed to
13
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
5 telecommunications.
[00042] 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
10 implementation, the BGCF is responsible for routing calls or messages from a
private network to a public network.
[00043] As discussed in the background section, the current known solutions
for enabling an offnet call routing have several shortcomings such as the reliance
15 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
20 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.
25 [00044] 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 'P30 Access-network-information' header, caller's identity and/or domain in the 'PAsserted-Identity' header, caller's identity and/or domain in the 'From' header,
14
callee's identity and/or domain in the 'To' header, and ‘tgrp’ along with trunkcontext. 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
5 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
10 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
15 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
20 traffic distribution optimizes resource utilization and enhances overall network
performance, delivering an improved telecommunication experience.
[00045] FIG. 1 illustrates an exemplary block diagram of a computing device
[100] (also referred to herein as a computer system [100]) upon which the features
25 of the present disclosure may be implemented in accordance with exemplary
implementation of the present disclosure. In an implementation, the computing
device [100] may also implement a method for routing an offnet call utilising the
system. In another implementation, the computing device [100] itself implements
the method for routing the offnet call using one or more units configured within the
15
computing device [100], wherein said one or more units are capable of
implementing the features as disclosed in the present disclosure.
[00046] The computing device [100] may include a bus [102] or other
5 communication mechanism for communicating information, and a hardware
processor [104] or processing unit coupled with a bus [102] for processing
information. The hardware processor [104] may be, for example, a general-purpose
microprocessor. The computing device [100] may also include a main memory
[106], such as a random-access memory (RAM), or other dynamic storage device,
10 coupled to the bus [102] for storing information and instructions to be executed by
the processor [104]. The main memory [106] also may be used for storing
temporary variables or other intermediate information during execution of the
instructions to be executed by the processor [104]. Such instructions, when stored
in non-transitory storage media accessible to the processor [104], render the
15 computing device [100] into a special-purpose machine that is customized to
perform the operations specified in the instructions. The computing device [100]
further includes a read only memory (ROM) [108] or other static storage device
coupled to the bus [102] for storing static information and instructions for the
processor [104].
20
[00047] A storage device [110], such as a magnetic disk, optical disk, or
solid-state drive is provided and coupled to the bus [102] for storing information
and instructions. The computing device [100] may be coupled via the bus [102] to
a display [112], such as a cathode ray tube (CRT), Liquid Crystal Display (LCD),
25 Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for
displaying information to a computer user. An input device [114], including
alphanumeric and other keys, touch screen input means, etc. may be coupled to the
bus [102] for communicating information and command selections to the processor
[104]. Another type of user input device may be a cursor controller [116], such as
30 a mouse, a trackball, or cursor direction keys, for communicating direction
16
information and command selections to the processor [104], and for controlling
cursor movement on the display [112]. 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.
5
[00048] The computing device [100] 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
[100] causes or programs the computing device [100] to be a special-purpose
10 machine. According to one implementation, the techniques herein are performed by
the computing device [100] in response to the processor [104] executing one or
more sequences of one or more instructions contained in the main memory [106].
Such instructions may be read into the main memory [106] from another storage
medium, such as the storage device [110]. Execution of the sequences of
15 instructions contained in the main memory [106] causes the processor [104] 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.
20 [00049] The computing device [100] also may include a communication
interface [118] coupled to the bus [102]. The communication interface [118]
provides a two-way data communication coupling to a network link [120] that is
connected to a local network [122]. For example, the communication interface
[118] may be an integrated services digital network (ISDN) card, cable modem,
25 satellite modem, or a modem to provide a data communication connection to a
corresponding type of telephone line. As another example, the communication
interface [118] 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 [118]
17
sends and receives electrical, electromagnetic, or optical signals that carry digital
data streams representing various types of information.
[00050] The computing device [100] can send messages and receive data,
5 including program code, through the network(s), the network link [120], and the
communication interface [118]. In the Internet example, a server [130] might
transmit a requested code for an application program through the Internet [128], the
Internet Service Provider (ISP) [126], the Host [124], the local network [122] and
the communication interface [118]. The received code may be executed by the
10 processor [104] as it is received, and/or stored in the storage device [110], or other
non-volatile storage for later execution.
[00051] The computing device [100] encompasses a wide range of electronic
devices capable of processing data and performing computations. Examples of
15 computing device [100] 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 [100]
may include peripheral devices, such as monitors, keyboards, and printers, as well
20 as integrated components within larger electronic systems, showcasing their
versatility in various technological applications.
[00052] As used herein, an offnet call may happen between the two different
networks belonging to different operators or service providers. These operators or
25 service providers are connected to each other via a media gateway control function
(MGCF).
[00053] As used herein, a media gateway control function (MGCF) may
connect two different networks such as IP multimedia subsystem (IMS) and public
30 switching telephone networks (PSTN). In other words, the MGCF is a key
18
component in telecommunication networks to facilitate the transition from
traditional circuit-switched networks to packet-switched networks.
[00054] As used herein, an IMS network refers to an Internet Protocol (IP)
5 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
10 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
15 (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.
[00055] The application servers are applications providing services, such as
20 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
25 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
30 limited to protocol conversion, network interworking, signalling transport, security,
load balancing, and traffic management. The Media Gateway Control Function
19
(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,
5 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
10 services.
[00056] 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 that involves both IMS and PSTN, the BGCF may perform
15 routing of the signalling appropriately by selecting the MGCF.
[00057] 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.
20
[00058] Referring to FIG. 2, an exemplary block diagram of a system [200]
for routing an offnet call, is shown, in accordance with the exemplary
implementations of the present disclosure. The system [200] comprises at least one
breakout gateway control function (BGCF) [202]. The breakout gateway control
25 function (BGCF) [202] comprises at least one transceiver unit [204], at least one
analysis unit [206], at least one processing unit [208], at least one identification unit
[210], and at least one routing unit [212]. Also, all of the components/ units of the
system [200] 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
30 assumed to be connected to each other. Also, in FIG. 2 only a few units are shown,
however, the system [200] may comprise multiple such units, or the system [200]
20
may comprise any such numbers of said units, as required to implement the features
of the present disclosure. In an implementation, the system [200] may reside in a
server or a network entity. In another implementation, the system [200] may be
present in a user device to implement the features of the present disclosure. The
5 system [200] 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 [200] may reside partly in the server/ network
entity and partly in the user device.
10 [00059] The system [200] is configured for routing the offnet call, with the
help of the interconnection between the components/units of the system [200]. The
system [200] includes the breakout gateway control function (BGCF) [202]. To
route the offnet call, the BGCF [202] includes a transceiver unit [204] configured
to receive an offnet call request, wherein the offnet call request includes a set of
15 headers. The transceiver unit [204] of the system [200] 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 nonlimiting implementation of the present disclosure, the header information may
comprise at least one of the ‘P-Access-network-information’ header, caller’s
20 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 is established between
two different networks belonging to different service providers. The first network
may include but is not limited to, Internet Protocol Multimedia Subsystem (IMS)
25 network, and the second network may include, but is not limited to, Public Switch
Telephone Network (PSTN).
[00060] In an exemplary aspect, the P-Access-Network-Information header
is a private header used in a session initiation protocol (SIP) to convey information
21
about the access network. It may include details associated with the type and
identity of the access network.
[00061] In an exemplary aspect, the P-Asserted-Identity header is a SIP
5 header used to convey the identity of the user device (operated by a user) and who
is authenticated and authorized by the network.
[00062] In an exemplary aspect, the trunk group (tgrp) parameter is used to
specify a trunk group in telephone communication. As used herein, trunk groups
10 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,
15 and rules to manage and use the trunk groups.
[00063] The BGCF [202] of the system [200] further includes an analysis
unit [206] configured to analyse a list of selection combinations associated with one
or more groups of media gateway control functions (MGCFs). The analysis unit
20 [206] 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
25 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.
30
22
[00064] The BGCF [202] of the system [200] further comprises a processing
unit [208] 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 [208] may determine the target group of
5 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
10 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 [208] 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
15 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
20 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.
[00065] The BGCF [202] of the system [200] further comprises an
25 identification unit [210] configured to identify the first MGCF from the target group
of MGCF associated with the offnet call request. Further, the identification unit
[210] 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 [202]
30 based on at least one of a predefined MGCF priority and a predefined MGCF
23
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.
5 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 [210] may send information about the identified first MGCF
from the target group of MGCF to the processing unit [208] and transmitter unit
10 [204] for further processing. In an exemplary aspect, each group may have predefined 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.
[00066] The transceiver unit [204] of the BGCF [202] is further configured
15 to transmit to the first MGCF, the offnet call request. Based on the received
information of the identified first MGCF from the target MGCF group, the
transceiver unit [204] may transmit the offnet call request to the first MGCF.
[00067] The transceiver unit [204] is further configured to receive from the
20 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
[204] may receive one or more failure responses associated with the offnet call
request from the first MGCF. In an implementation, the transceiver unit [204] at the
BGCF [202] may receive one or more failure responses, or negative responses or
25 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.
[00068] The BGCF [202] of the system [200] further comprises the
identification unit [210]. The identification unit [210] is further configured to
30 identify, in an event of receiving from the first MGCF at least a predefined number
24
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 [210] may identify
the second MGCF from the target group of MGCF associated with the offnet call
5 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 [208] 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
10 unit [208] may trigger the identification unit [210] for identifying the second MGCF
from the target group of MGCF. The processing unit [208] may trigger the
identification unit [210] 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 [208] is further configured to blacklist the
15 first MGCF for a predefined time based on receiving the predefined number of
failure responses.
[00069] The BGCF [202] of the system [200] further comprises a routing unit
[212] configured to route to the second MGCF, the offnet call associated with the
20 offnet call request. Thereafter, the routing unit [212] 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.
[00070] Further, in accordance with the present disclosure, it is to be
25 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
30 as limiting the scope of the present disclosure. Consequently, alternative
25
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.
5 [00071] Referring to FIG. 3, an exemplary method flow diagram [300] for
routing an offnet call, in accordance with exemplary implementations of the present
disclosure is shown. In an implementation, the method [300] is performed by the
system [200]. Further, in an implementation, the system [200] may be present in a
server device to implement the features of the present disclosure. Also, as shown in
10 FIG. 3, the method [300] starts at step [302].
[00072] At step [304], the method [300], as disclosed by the present
disclosure, comprises receiving, by a transceiver unit [204] at a Breakout Gateway
Control Function (BGCF) [202], an offnet call request, wherein the offnet call
15 request comprises a set of headers. The method [300] implemented by the
transceiver unit [204] at the BGCF [202] of the system [200] 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
20 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
25 ‘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
30 may be, such as, but not limited to, a PSTN network.
26
[00073] Next, at step [306], the method [300] as disclosed by the present
disclosure comprises analysing, by an analysis unit [206] at the BCGF [202], a list
of selection combinations associated with one or more groups of Media Gateway
5 Control Functions (MGCFs). The method [300] implemented by the analysis unit
[206] at the BCGF [202] 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
10 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
15 of serving MGCFs, traffic load distribution and weightage of MGCF, healthy and
active MGCFs.
[00074] Next, at step [308], the method [300] as disclosed by the present
disclosure comprises determining, by a processing unit [208] at the BGCF [202], a
20 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 [300]
implemented by the processing unit [208] at the BGCF [202] 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,
25 there may be different MGCF groups such as MGCF group 1, MGCF group 2, and
MGCF group 3 in the network. The processing unit [208] 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.
30
27
[00075] Next, at step [310], the method [300], as disclosed by the present
disclosure, comprisesidentifying, by an identification unit [210] at the BGCF [202],
a first MGCF from the target group of MGCF associated with the offnet call request.
The method [300] implemented by the identification unit [210] at the BGCF [202]
5 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 [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. Further, the second
10 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
15 call handling or call routing. As used herein, MGCF weightage refers to the weight
assigned to the MGCF to manage 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
20 priority are customized and changed dynamically based on traffic load and demand.
The identification unit [210] may send information related to the identified first
MGCF from the target group of MGCF to the processing unit [208] and transmitter
unit [204] for further processing. In an exemplary aspect, each group may have predefined numbers of MGCFs, such as, but not limited to, ten MGCFs. In an
25 exemplary aspect, the number of MGCFs in a group may increase or decrease based
on network requirements.
[00076] Next, at step [312], the method [300], as disclosed by the present
disclosure, comprises transmitting, by the transceiver unit [204] from the BGCF
30 [202], to the first MGCF, the offnet call request. Further, the transceiver unit [204]
28
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.
5 [00077] Next, at step [314], the method [300], as disclosed by the present
disclosure, comprises 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. The method [300] implemented by the transceiver unit [204] at the BGCF
[202] may receive one or more failure responses associated with the offnet call
10 request from the first MGCF. In an implementation, the transceiver unit [204] at the
BGCF [202] 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
15 MGCF encountered an issue or failure while attempting to manage services (e.g.,
call routing) in the network.
[00078] Next, at step [316], the method [300], as disclosed by the present
disclosure, comprises identifying, by the identification unit [210] at the BGCF
20 [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. After receiving a failure/negative
response or no response, the identification unit [210] may identify the second
MGCF from the target group of MGCF associated with the offnet call request in
25 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 [208]
may process the one or more failure responses for the offnet call request received
from the first MGCF. After receiving the predefined number of failure responses
for the offnet call request, the processing unit [208] may trigger the identification
30 unit [210] for identifying the second MGCF from the target group of MGCF. The
processing unit [208] may trigger the identification unit [210] after the predefined
29
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 [208]
is further configured to blacklist the first MGCF for a predefined time based on the
predefined number of failure responses.
5
[00079] Next, at step [318], the method [300], as disclosed by the present
disclosure, comprises automatic 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. Thereafter, the method [300] implemented by the routing
10 unit [212] at the BGCF [202] 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 [304] to [318] are executed automatically to perform automatic routing of the
offnet call minimizing the manual intervention.
15
[00080] Thereafter, the method [300] terminates at step [320].
[00081] FIG. 4 illustrates a process flow [400] diagram for routing an offnet
call, in accordance with exemplary implementations of the present disclosure. In an
20 exemplary aspect, the process flow [400] is implemented by the system [200].
[00082] At step S2, different combinations for MGCFs selection are
configured for BGCF [202]. In an exemplary aspect, the combinations may
correspond to the selection of header information (e.g., ‘P-Access-network25 information’ header, caller’s identity, and/or domain in the ‘P-Asserted-Identity’
header), weightage, priority, healthy and active number of MGCF.
[00083] At step S4, MGCF groups are defined with multiple MGCF’s with
their priority & weightage. In an exemplary aspect, each group may have a pre30 configured number of MGCFs, such as, but not limited to, ten MGCFs. In an
30
exemplary aspect, each group may have a similar number or a different number of
MGCFs.
[00084] At step S6, the offnet call is received at the BGCF [202]. A user
5 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.
[00085] At step S8, checking of the best match combination is performed. In
10 an implementation, when the offnet call is received at BGCF [202], the BGCF [202]
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.
15 [00086] At step S10, the selection of the MGCF from MGCF group 1 is
performed. In an implementation, the BGCF [202] then selects one MGCF, based
on the priority and weightage of the MGCF, from the best match MGCF group. The
BGCF [202] 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
20 MGCF then the MGCF may be blacklisted by the BGCF [202], and no further
request may be sent to that MGCF until the blacklist time expires. Then, the BGCF
[202] 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 pre25 tested, then by defining the MGCF selection combination based on the test
numbers, this can be easily achieved.
[00087] At step S12, the selection of the MGCF from MGCF group 2 is
performed. The BGCF [202] may select the MGCF from the MGCF group 2 if
30 MGCF group 1 is unable to serve the offnet call request.
31
[00088] At step S14, the selection of the MGCF from MGCF group 3 is
performed. The BGCF [202] may select the MGCF from the MGCF group 3 if
MGCF group 2 is unable to serve the offnet call request.
5
[00089] In an exemplary aspect, the BGCF [202] may perform the same
process for the MGCF group 2 and MGCF group 3, as performed for MGCF group
1 in step 10.
10 [00090] 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 [204] of the system to receive an offnet call
request, wherein the offnet call request comprises a set of headers. Further, the
15 instruction when executed causes an analysis unit [206] 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 [208] of the system to determine a target group of MGCF from the
one or more group of MGCFs based on matching of the list of selection
20 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 [204] of the system to transmit to the first MGCF, the
offnet call request. Further, the instruction when executed causes the transceiver
25 unit [204] 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 [210] 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
30 associated with the offnet call request. Further, the instruction when executed
32
causes a routing unit [212] of the system to route to the second MGCF, the offnet
call associated with the offnet call request to the identified second MGCF.
[00091] As is evident from the above, the present disclosure provides a
5 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
10 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
15 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
20 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
25 ensures seamless service transitions.
[00092] 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
30 distribution control by the BGCF, provide tangible technical effects. These effects
33
encompass improved scalability, enhanced network management, optimized
resource utilization, efficient integration of new MGCFs, and overall enhancement
of telecommunication service quality and performance.
5 [00093] 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
10 be understood that the foregoing descriptive matter to be implemented is illustrative
and non-limiting.
34
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
5 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
10 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
15 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
20 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
25 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.
35
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
5 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.
10 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
15 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,
20 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:
25 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);
36
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
5 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;
10 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
15 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.
20 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
25 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
30 the target group of MGCF at the BGCF [202] based on at least one of a
37
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
5 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
10 configured to blacklist the first MGCF for a predefined time period based on
the predefined number of failure responses.