System and method for managing communication requests in a network

Abstract

The present disclosure provides a system and method for managing the volume of communication requests in a network. The system may include a network device that may be operable to communicate with an Internet Protocol Multimedia Subsystem (IMS) server and a Centralized Data Layer (CDL) server. The network device may receive a communication request from a user device via the IMS server. The network device may send the communication request and a set of information to the CDL server. The CDL server may evaluate the admission of the communication request originating from the user device. The evaluation may ascertain whether the number of communication requests within or between circles may exceed a predefined limit. Based on the evaluation, if the predefined limit may not be exceeded, then the CDL server may provide an indication of admission of the communication request received from the user device.

Description

[Technical field]

[0001] Reservation of Rights Portions of the disclosure of this patent document contain material that is subject to intellectual property rights, including, but not limited to, copyright, design, trademark, integrated circuit (IC) layout design, and / or trade dress protection, belonging to JPL (Jio Platforms Limited) or its affiliates (hereinafter referred to as the Owner). The Owner has no objection to anyone copying this patent document or this patent disclosure to the extent that it appears in a Patent and Trademark Office patent application or records, but otherwise reserves all rights. All rights to such intellectual property are fully reserved by the Owner.

[0002] FIELD OF THE DISCLOSURE Embodiments of the present disclosure relate generally to systems and methods for regulating traffic for voice communications in a wireless communication network. More specifically, the present disclosure relates to systems and methods for managing communication demands in a network that are efficient and control the number of calls within a particular Closed User Group (CUG). [Background technology]

[0003] The following description of related art is intended to provide background information regarding the field of the present 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 understood that this section is not intended as an admission of prior art, but is merely intended to enhance the reader's understanding of the present disclosure.

[0004] Quality of service in wireless communication networks is a challenging problem since multiple radio channels for voice communication mobility are utilized by multiple users. Furthermore, a communication network can be considered as having multiple cells with unidirectional links, each cell having a limited bandwidth. For example, when a new call is made in a cell, one of the channels assigned to the cell's base station is used for communication between the mobile user and the base station. If all channels assigned to this base station are in use, the call attempt is blocked and assumed to be dropped.

[0005] Once a new call acquires a channel, the call will remain on the channel until either the call is completed within the cell or the mobile station (user) moves out of the cell. Once the call is completed, the channel is released and available to serve another call. When a mobile user requests service, the request may be granted or denied based on the success of the handoff established by the mobile station. If the handoff initiation is not successful, a forced termination or "call drop off" may be generated. In general, a call drop may cause adverse effects to the user. Therefore, an efficient system may be needed to combat the identified problems associated with conventional systems.

[0006] Therefore, there is a need in the art to provide systems and methods that can alleviate problems associated with the prior art.

[0007] Object of the invention Some of the objectives of the present disclosure that are met by at least one embodiment herein are set forth below.

[0008] An object of the present disclosure is to provide a system and method for using a Business Telephony Application Server (BTAS) to provide Session Initiation Protocol (SIP) trunking and Internet Protocol (IP) Centrex services to customers.

[0009] It is an object of the present disclosure to provide a system and method for using a BTAS to provide supplementary services to customers, such as closed user groups (CUGs), short code dialing, and conferencing.

[0010] It is an object of the present disclosure to provide a system and method using a BTAS that uses call admission control (CAC) services to simultaneously control several calls in a particular CUG.

[0011] An object of the present disclosure is to provide a system and method using BTAS that uses circle-based CAC with a centralized data layer (CDL) server that maintains accounts for several calls in the circle-based CAC.

[0012] It is an object of the present disclosure to provide a system and method for using a BTAS with a circle-based CDL to meet circle-specific data access requirements.

[0013] It is an object of the present disclosure to facilitate effective and improved management of traffic volumes relating to communication requests.

[0014] An objective of the present disclosure is to create a network service to facilitate an economical and next generation based system and method that can eliminate network congestion or overload caused by excess traffic, thus improving the efficiency and quality of service.

[0015] It is an object of the present disclosure to facilitate systems and methods that can make it possible to manage the volume of communication requests within or between multiple circles. Summary of the Invention

[0016] This section is provided to introduce certain objects and aspects of the disclosure in a simplified form that are further described in the Detailed Description below. This Summary is not intended to identify key features or the scope of the claimed subject matter.

[0017] In one aspect, the present disclosure relates to a system for establishing one or more connections. The system may include one or more processors operatively coupled with a business telephony application server (BTAS). The one or more processors may be coupled with a memory storing instructions executed by the one or more processors. The one or more processors may receive one or more communication requests from one or more user devices via a communication network. The one or more communication requests may be based on one or more input parameters. The one or more processors may send the one or more communication requests to a centralized data layer (CDL) server via the communication network. The CDL server may be configured to approve the received one or more communication requests based on one or more predefined rules. The one or more processors may receive the approved one or more communication requests from the CDL server via the communication network. The one or more processors may establish one or more connections between the one or more user devices and the BTAS based on the approved one or more communication requests.

[0018] In one embodiment, the one or more processors may be configured to process one or more communication requests and enable one or more service chain logic executions associated with the one or more communication requests.

[0019] In one embodiment, the one or more processors may be configured to manage faults, configurations, and performance associated with one or more communication requests.

[0020] In one embodiment, the one or more processors may be configured to store one or more database clusters and update changes associated with one or more communication requests in the one or more database clusters.

[0021] In one embodiment, the one or more processors may be configured to debug one or more database clusters associated with one or more communication requests.

[0022] In one embodiment, a CDL server may be configured with one or more call admission control (CAC) services to handle one or more communication requests.

[0023] In one embodiment, the CDL server may be configured with either or a combination of circle-based call admission control (CAC) services and centralized CAC services for handling one or more communication requests.

[0024] In one embodiment, the one or more input parameters may include at least one of an enterprise identification (ID), a closed user group (CUG) ID, a call admission control (CAC) policy, and one or more channels used by the CAC policy.

[0025] In one embodiment, the one or more predefined rules of the CDL server may be based on one or more validations from an external server. The external server may be configured to validate one or more input parameters associated with one or more user devices.

[0026] In one embodiment, the CDL server may be configured with a timer to record one or more communication requests from one or more user devices and send one or more communication requests to an external server for one or more verifications.

[0027] In one embodiment, the one or more CAC services may include at least one CAC cluster to process one or more communication requests.

[0028] In one aspect, the present disclosure relates to a method for establishing one or more connections. The method may include receiving, by one or more processors, one or more communication requests from one or more user devices over a communication network. The one or more processors may be operatively coupled to a Business Telephony Application Server (BTAS). The one or more communication requests may be associated with one or more input parameters. The method may include sending, by the one or more processors, the one or more communication requests to a CDL server over the communication network. The CDL server may be configured to approve the one or more communication requests based on one or more predefined rules. The method may include receiving, by the one or more processors, the approved one or more communication requests from the CDL server over the communication network. The method may include establishing, by the one or more processors, one or more connections between the one or more user devices and the BTAS based on the approved one or more communication requests.

[0029] In one embodiment, the method may include processing, by one or more processors, one or more communication requests and enabling one or more service chain logic executions associated with the one or more communication requests.

[0030] In one embodiment, a method may include managing, by one or more processors, faults, configurations, and performance associated with one or more communication requests.

[0031] In one embodiment, the method may include storing, by one or more processors, one or more database clusters and updating, in the one or more database clusters, changes associated with one or more communication requests.

[0032] In one embodiment, the method may include debugging, by one or more processors, one or more database clusters associated with the one or more communication requests.

[0033] In one aspect, the present disclosure relates to a user equipment (UE) for establishing one or more connections. The UE may include one or more processors operably coupled to one or more processors in a system. The one or more processors may be coupled to a memory storing instructions executed by the one or more processors to cause the UE to transmit one or more communication requests to the one or more processors over a communication network. The one or more processors may be operably coupled to a BTAS, and the one or more processors may be configured to receive one or more communication requests from the UE. The one or more processors may transmit the one or more communication requests to a CDL server over the communication network. The CDL server may be configured to approve the one or more communication requests based on one or more predefined rules. The one or more processors may receive the approved one or more communication requests from the CDL server over the communication network. The one or more processors may establish one or more connections between the UE and the BTAS based on the approved one or more communication requests.

[0034] In one aspect, a non-transitory computer-readable medium may include a processor having executable instructions that may cause the processor to receive one or more communication requests from one or more user devices over a communication network. The one or more communication requests may be based on one or more input parameters. The processor may send the one or more communication requests to a centralized data layer (CDL) server over the communication network. The CDL server (104) may be configured to approve the received one or more communication requests based on one or more predefined rules. The processor may receive the approved one or more communication requests from the CDL server over the communication network. The processor may establish one or more connections between the one or more user devices and a business telephony application server (BTAS) based on the approved one or more communication requests.

[0035] The accompanying drawings, which are incorporated herein and form a part of this disclosure, depict exemplary embodiments of the disclosed method and system, in which like reference numbers refer to the same parts throughout the different drawings. The components in the drawings are not necessarily drawn to scale, emphasis instead being placed on clearly illustrating the principles of the present disclosure. Some figures may use block diagrams to illustrate components and may not represent the internal circuitry of each component. Those skilled in the art will appreciate that the disclosure of such drawings includes disclosure of electrical or electronic components, or circuits commonly used to implement such components. [Brief description of the drawings]

[0036] [Figure 1A] 1 illustrates an exemplary network architecture (100) in which or with which the system of the present disclosure may be implemented, according to one embodiment of the present disclosure. [Figure 1B] 1 illustrates an exemplary high-level system architecture (150) of the proposed system, according to one embodiment of the present disclosure. [Figure 2A]1 shows an exemplary block diagram (200) of the proposed system, according to one embodiment of the present disclosure. [Figure 2B] 2 illustrates an exemplary system architecture (250) of a proposed Business Telephony Application Server (BTAS) according to one embodiment of the present disclosure. [Figure 3A] 3 illustrates an exemplary centralized data layer (CDL) framework (300, 330) according to one embodiment of the present disclosure. [Figure 3B] 3 illustrates an exemplary centralized data layer (CDL) framework (300, 330) according to one embodiment of the present disclosure. [Figure 4] 4 illustrates an exemplary representation of a CDL framework (400) according to one embodiment of the present disclosure. [Diagram 5] 5 illustrates an example representation (500) of a circle-based CDL framework, according to one embodiment of the present disclosure. [Figure 6] 6 shows an exemplary sequence diagram of a method (600) for implementing the proposed mechanism according to one embodiment of the present disclosure. [Figure 7] 7 illustrates an example sequence diagram of a method (700) for CDL processing multiple calls according to one embodiment of the present disclosure. [Figure 8] 8 illustrates an exemplary computer system (800) in which or with which the proposed system may be implemented according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0037] The above will become more apparent from the following more detailed description of the present disclosure.

[0038] In the following description, for the purpose of explanation, various specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure. However, it will be apparent that the embodiments of the present invention can be practiced without those specific details. Each of the several features described below can be used alone or in any combination with other features. Individual features may not be able to address all of the above problems, or may address only some of the above problems. Some of the above problems may not be fully addressed by any of the features described herein.

[0039] The following description provides exemplary embodiments only and is not intended to limit the scope, applicability, or configuration of the present disclosure. Rather, the following description of exemplary embodiments provides those skilled in the art with an effective description for implementing the exemplary embodiments. It should be understood that various changes can be made in the function and arrangement of elements without departing from the spirit and scope of the present disclosure as described.

[0040] In the following description, specific details are given to provide a thorough understanding of the embodiments. However, it will be apparent to one skilled in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order to avoid obscuring the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.

[0041] It should also be noted that the particular embodiments may be described as a process that is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe operations as a sequential process, many of the operations may be performed in parallel or simultaneously. Additionally, the order of operations may be rearranged. A process terminates when its operations are completed, but there may be additional steps not included in the diagram. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination may correspond to a return of the function to the calling function or to the main function.

[0042] The words "exemplary" and / or "illustrative" are 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. Moreover, any aspect or design described herein as "exemplary" and / or "demonstrative" should not necessarily be construed as preferred or advantageous over other aspects or designs, nor is it meant to exclude equivalent exemplary structures and techniques known to those skilled in the art. Moreover, to the extent that the terms "includes," "has," "contains," and other similar terms are used in either the detailed description or the claims, such terms are intended to be inclusive in the same manner as the term "comprising" as an open transitional term, without excluding any additional or other elements.

[0043] References throughout this specification to "one embodiment" or "an embodiment" or "an instance" or "one instance" mean that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment of the disclosure. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification do not necessarily all refer to the same embodiment. Furthermore, particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0044] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms unless the context indicates otherwise. It is to be further understood that the terms "comprise" and / or "comprising" as used herein specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.

[0045] Various embodiments throughout the disclosure will now be described in more detail with reference to FIGS.

[0046] FIG. 1A illustrates an example network architecture (100) in which or with which the proposed system may be implemented according to one embodiment of the present disclosure.

[0047] As shown in the network architecture (100) of FIG. 1A, the present disclosure relates to a system for controlling the traffic volume of communication requests within a network. In one embodiment, the network architecture (100) may include a network device (102) (hereinafter interchangeably referred to as a Business Telephony Application Server, or BTAS server (102)) that may be configured to facilitate managing the volume of communication requests from user devices (110) over a communication network (112). Although a single user device (110) is shown for simplicity, it should be understood that the user device (110) may include multiple user devices (110). The BTAS server (102) may be integrated with an Internet Protocol Multimedia Subsystem (IMS) server (106) (also interchangeably referred to as an IMS or IMS core). The IMS (106) may include, but is not limited to, a third generation (3G) network, a fourth generation (4G) network, a fifth generation (5G) network, a wireless fidelity (Wi-Fi) network, any other wireless network, or a combination thereof. Furthermore, the IMS server (106) may be accessed via a communication network (112). In one embodiment, the user device (110) may be connected to a centralized data layer (CDL) server or framework (104) via the communication network (112). The CDL server (104) may access information stored across different physical hosts in multiple or different circles / clusters to manage the volume of communication requests coming in via the BTAS server (102).

[0048] The user devices (110) may include, but are not limited to, mobile phones, laptops, and the like. Additionally, the user devices (110) may include smartphones, virtual reality (VR) devices, augmented reality (AR) devices, general purpose computers, desktops, personal digital assistants, tablet computers, and mainframe computers. Additionally, input devices for receiving input from a user, such as touch pads, touch-enabled screens, electronic pens, and the like, may be used. Those skilled in the art will appreciate that the user devices (110) may not be limited to the mentioned devices and various other devices may be used.

[0049] The communications network (112) may include at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or any combination thereof, of one or more messages, packets, signals, waves, voltage or current levels, any combination thereof, etc. The communications network (112) may also include, by way of example and not limitation, one or more of a wireless network, a wired network, the Internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad-hoc network, an infrastructure network, a public switched telephone network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or any combination thereof.

[0050] Although Figure 1A illustrates exemplary components of network architecture (100), in other embodiments, network architecture (100) may include fewer components, different components, differently arranged components, or additional functional components than those illustrated in Figure 1A. Additionally or alternatively, one or more components of network architecture (100) may perform functions described as being performed by one or more other components of network architecture (100).

[0051] FIG. 1B illustrates an exemplary high-level system architecture (150) of the proposed system, according to one embodiment of the present disclosure.

[0052] 1B, a communications network (112) (designated in FIG. 1A) may be provided to multiple entities or enterprises, such as enterprise 1 (154-1), enterprise 2 (154-2), enterprise 3 (154-3), and enterprise 4 (154-4) (collectively referred to as enterprises 154). As shown in FIG. 1B, each enterprise, i.e., enterprise 1 (154-1), enterprise 2 (154-2), enterprise 3 (154-3), and enterprise 4 (154-4), may be aided in the communications network (112) via an E-SBC (156-1), E-SBC (156-2), E-SBC (156-3), and E-SBC (156-4), respectively.

[0053] The IMS server (106 in FIG. 1A) may include one or more modules or components that may perform one or more functions. For example, the IMS server (106) may include a Serving Call Session Control Function module (S-CSCF) (158), an Interrogating Call Session Control Function module (I-CSCF) (162), and a Proxy Call Session Control Function module (P-CSCF) (152). In another example, other application servers may include a Mobile Number Portability (MNP) server (124) that may provide number portability to the user device (110).

[0054] With reference to components related to the IMS server (106), the S-CSCF module (158) may be the primary node in the IMS server (106) responsible for session control. In one embodiment, a list of subscribers may be assigned to each S-CSCF module (158) at IMS registration time to facilitate routing of Session Initiation Protocol (SIP) messages. In operation, the S-CSCF module (158) may enable downloading of subscriber profiles from the Home Subscriber Server (HSS) (120) at IMS registration time. The I-CSCF module (162) may be a key element in the IMS server (106) and may enable routing of any request from multiple S-CSCF modules in the network (112) to the appropriate S-CSCF module (158). The I-CSCF module (162) may also query the HSS (120) to obtain the address of the associated S-CSCF module (158) for further processing of the SIP initiation request. The P-CSCF module (152) may perform general functions such as onward routing of registration and session requests to the correct node in the communications network (112), updating the S-CSCF module (158), maintaining a secure connection with the user device (110), and other such functions. In an exemplary embodiment, the Telephony Application Server (TAS) (160) and the BTAS (102) may be integrated with one or more functional components for a SIP-based application server. The SIP application server may be built with features for enterprise 4 (154-4).

[0055] In addition, as shown in FIG. 1B, a breakout gateway control function (BGCF) module (118), a media gateway control function module (MGCF) (122), and an interconnection border control function module (IBCF) (116) may also be included with specific functions. In a typical implementation, the BGCF module (118) may provide routing call signaling to and from the most appropriate S-CSCF module (158). In this implementation, the BGCF module (118) may route calls from the BTAS (102) to manage the volume of communication requests. In general, the MGCF module (122) may be a SIP endpoint that may interface with a security gateway (SGW) and may also control resources in the media gateway (MGW) (130). The IBCF module (116) may also enable border control between various service provider networks, thus providing BTAS-enabled IMS network security with respect to signaling information. The IMS server (106) may also include a Multimedia Resource Function (MRF) module (126), which may be responsible for performing various processing tasks on media streams associated with a particular service in coordination with other components of the IMS server (106). Additionally, as shown in FIG. 1B, a BTAS-IMS based implementation may be associated with a Point of Interconnect (POI) (134), which may be a physical interface between media gateways of various service providers or enterprises via time division multiplexing (TDM).

[0056] FIG. 2A illustrates an example block diagram (200) of the proposed system, according to one embodiment of the present disclosure.

[0057] Referring to FIG. 2A, the business telephony application server (BTAS) (102) may include one or more processors (202), which may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuits, and / or any device that processes data based on operational instructions. Among other functions, the one or more processors (202) may be configured to fetch and execute computer-readable instructions stored in a memory (204) of the BTAS (102). The memory (204) may be configured to store one or more computer-readable instructions or routines in a non-transitory computer-readable storage medium, which may be fetched and executed to create or share data packets via a network service. The memory (204) may include any non-transitory storage device, including, for example, a volatile memory, such as a random access memory (RAM), or a non-volatile memory, such as an erasable programmable read-only memory (EPROM), flash memory, and the like.

[0058] In one embodiment, the BTAS (102) may include an interface (206). The interface (206) may include various interfaces, such as interfaces for data input / output (I / O) devices, storage devices, etc. The interface (206) may also provide a communication path to one or more components of the system BTAS (102). Examples of such components include, but are not limited to, a processing engine (208), a database (210), a session manager (SM) (212), an operations and administration (OAM) manager (214), a provisioning agent (PA) (216), a database manager (DM) (218), a troubleshooting manager (TM) (220), and a CDL agent (230).

[0059] The processing engine (208) may be implemented as a combination of hardware and programming (e.g., programmable instructions) to implement one or more functions of the processing engine (208). In the examples described herein, such a combination of hardware and programming may be implemented in a number of different ways. For example, the programming of the processing engine (208) may be processor-executable instructions stored in a non-transitory machine-readable storage medium, and the hardware of the processing engine (208) may include processing resources (e.g., one or more processors) to execute such instructions. In this example, the machine-readable storage medium may store instructions that, when executed by the processing resources, implement the processing engine (208). In such an example, the BTAS (102) may include a machine-readable storage medium that stores instructions and the processing resources to execute the instructions, or the machine-readable storage medium may be separate but accessible to the BTAS (102) and the processing resources. In another example, the processing engine (208) may be implemented by electronic circuitry.

[0060] In one embodiment, the one or more processors (202) may receive a communication request from one or more user devices (110) over the communication network (112). The one or more communication requests may be based on one or more input parameters. The input parameters may include, but are not limited to, an enterprise identification (ID), a closed user group (CUG) ID, a call admission control (CAC) policy, and one or more channels used by the CAC policy.

[0061] In one embodiment, the one or more processors (202) may send one or more communication requests to a centralized data layer (CDL) server (104) over the communication network (112). The CDL server (104) may be configured to approve the received one or more communication requests based on one or more predefined rules. A CDL agent (230) may be configured in the CDL server (104) to approve the received one or more communication requests based on one or more predefined rules.

[0062] In one embodiment, the one or more processors (202) may receive one or more communication requests via a session manager (212) and process the one or more communication requests. The one or more processors (202) may store the one or more communication requests in a database (210), and a database manager (DM) (218) may be configured to manage the database (210). The one or more processors (202) may enable one or more service chain logic executions associated with the one or more received communication requests.

[0063] In one embodiment, the one or more processors (202) may be configured to manage faults, configurations, and performance associated with one or more received communication requests via a provisioning agent (PA) (216) and a troubleshooting manager (220).

[0064] In one embodiment, the one or more processors (202) may be configured to store one or more database clusters in a database (210) and to update changes associated with one or more received communication requests in the one or more database clusters via a PA (216).

[0065] In one embodiment, the one or more processors (202) may be configured to debug one or more database clusters via an open code protocol accelerator module (OAM) manager (214) associated with one or more received communication requests.

[0066] FIG. 2B illustrates an example system architecture (250) of the proposed BTAS, according to one embodiment of the present disclosure.

[0067] As shown in FIG. 2B, the BTAS (102) may be integrated or coupled with various hardware / software components or servers to enable one or more functions for managing the volume of communication requests. The BTAS (102) may be integrated with an IMS server (254) (formerly the IMS (106) in FIG. 1A) to enable communication processing for a user device (252) (formerly the user device (110) in FIG. 1A). In an exemplary embodiment, the BTAS (102) may be integrated with the IMS server (254) to establish and control communication connections via network protocols including, but not limited to, the Session Initiation Protocol (SIP). Because communication may also involve the use of media in one or more forms, the BTAS (102) may be integrated with a Multimedia Resource Function (MRF) (258) via the SIP / Media Server Markup Language (MSML) protocol. The BTAS (102) may interface with an enterprise provisioning server (EPS) (260) via the representational state transfer (REST) ​​protocol to enable provisioning of service data.

[0068] In an exemplary embodiment, the BTAS (102) may be integrated or coupled with other components / services such as Mobile Number Portability (MNP) (270) via SIP to enable number portability dipping. In another exemplary embodiment, the BTAS (102) and the Evolution Packet System (EPS) (260) may be independently integrated or coupled with an Element Management System (EMS) (256) via REST. The EMS (256) may exchange messages regarding five key aspects via the REST protocol, including hardware and software implementations for managing Fault, Configuration, Accounting, Performance, and Security (FCAPS) functions, and may use HyperText Transfer Protocol (HTTP) to transport messages. The EMS (256) may provide a foundation for implementing an Operations Support System (OSS) or Business Support System (BSS) based architecture that allows service providers to meet customer needs, for example, for rapid deployment of services, quality of service requirements, and other such services. The EMS (256) may interface with the OSS / BSS (262) via the REST protocol to enable a northbound interface for the FCAPS data of the BTAS / EPS. The term northbound interface may refer to an interface that allows a particular component of a network to communicate with a higher-level component. Furthermore, the OSS / BSS (262) may interface with the EPS (260) via the REST protocol to manage service data management requests. Furthermore, the EPS (260) may be connected to the OSS / BSS (262) via the F5 (264), and the F5 (264) may communicate with the OSS / BSS (262) via REST.

[0069] Additionally, as shown in FIG. 2B, the BTAS (102) may be integrated or coupled with a Diameter Routing Agent (DRA) (268) via the Diameter protocol, which may be a standard protocol for authentication, authorization, and accounting information in IMS server-based networks. The DRA may be a functional element that may provide real-time routing functionality to ensure that messages are routed between the correct elements in the network. The integration of the BTAS (102) with the DRA (268) may enable integration with an Online Charging System (OCS) (272) to facilitate Ro charging. The OCS (272) may be a system that allows a service provider to charge users or customers in real-time based on service usage, and Ro charging may relate to a protocol that allows triggers to generate charging events. In one embodiment, the BTAS (102) may also be integrated with components related to a Customized Caller Ring Tone (CRBT) Server (266) to enable personalized ring tone (RBT) during the communication establishment phase. For example, this may primarily relate to ring tones that may be played while connecting the user device (252) with the entity device.

[0070] 3A and 3B show an exemplary CDL framework (300, 330) according to one embodiment of the present disclosure.

[0071] According to the BTAS deployment architecture (300) shown in FIG. 3A, multiple clusters may be used to serve the traffic of a single circle, for example, multiple clusters may serve the traffic of circle 1. Furthermore, each of the circles may have its own single CDL implementation, which may be in a super core. As shown in FIG. 3A, the CDL framework (302) may be implemented on a "client-server" communication model. As further shown in FIG. 3A, application clusters, such as application cluster 1 (306-1), application cluster 2 (306-2), and application cluster 3 (306-3), may communicate with respective CDL servers residing on physical blades 1.6 (304-1, 304-2, 403-3). Physical blades 1.6 (304-1, 304-2, 304-3) may communicate with the CDL framework (302) using a common data access / read / write protocol.

[0072] As shown in FIG. 3B, one or more services, such as service A, service B, and service C, associated with the CDL server (308) may be integrated with the CDL agent (312). The services, i.e., service A, service B, and service C, may communicate with the CDL agent (312) using Transmission Control Protocol (TCP) as a transport protocol (310). The CDL agent (312) may select one of the CDL server destination IPs based on the service routing requirements. In an exemplary embodiment, the CDL server (308) may be responsible for interfacing with the CDL framework (302) and may respond to data access requests received from the CDL agent (312).

[0073] In another embodiment, the CDL agent (312) and the CDL server (308) may function primarily as a backbone to carry information between services that reside on both the client and server side, respectively. To take advantage of the CDL framework (302), a new service may need to register itself with the CDL client and the CDL server so that the CDL framework (302) can properly route data access requests / responses to the correct service modules.

[0074] FIG. 4 illustrates an example representation (400) of a CDL framework, according to one embodiment of the present disclosure.

[0075] With reference to FIG. 4, a CDL agent (420) in application cluster 1 and a CDL agent (422) in application cluster N may connect to CDL servers (1, 2...N) (416) via a TCP connection. In one embodiment, the CDL agents and CDL servers (1, 2...N) may communicate with each other via a communication model using their own predefined header body format. The header may be fixed in size and may include one or more important information fields. This may be required for routing data access requests and responses. Furthermore, the body may be variable in size and may depend on the service type corresponding to various data access request types. In one embodiment, the CDL agent may calculate a hash value of the data accessibility request to one of the CDL servers based on service-specific delivery logic (418). In this regard, each of the CDL server instances may have a virtual IP (414) to receive requests from multiple CDL agents. As an example, service A in the CDL agent may require insert, update, delete, and data access operation indications, which may have variable body size requirements. Service data may be transported between the CDL agent and the CDL server in the form of buffers and may be encoded / decoded by the service layer.

[0076] In an exemplary embodiment, CDL servers (1,2...N) may be deployed across blade clusters (1,2...N). In one example, a single-blade implementation may be appropriate for functional lab testing, but without high availability (HA) (process restart functionality may be present). In another example, a two-blade implementation may be appropriate for functional lab testing with HA, and may be recommended for field deployments where the number of BTAS clusters may be small (e.g., less than three (<3)) or for BTAS at disaster recovery (DR) sites. In one example, a six-blade implementation may be appropriate for field deployments where the number of BTAS clusters may be three or more.

[0077] For example, consider an implementation applicable to a particular location that may include four BTAS clusters, each of which may include two management blades, for a total of eight blades. This may be used to create a CDL cluster for the BTAS traffic of a particular location. For example, to create a six-blade CDL cluster, six blades may be chosen from a pool of eight available blades, ensuring that the CDL cluster management blades may reside not only in the chassis but also in different BTAS clusters. This may be done to enable chassis-level redundancy of the CDL management blades. In this example, the four BTAS clusters for application services that desire a centralized data access framework may use a CDL cluster created specifically for the traffic of the particular location. In this way, each of the BTAS circles may have one exclusive CDL cluster created for that location.

[0078] In one embodiment, each CDL cluster may include modules such as, for example, a logger manager, a system manager, and a CDL manager, as well as other such processes. For example, the logger manager may be responsible for managing application log activity and may reside on each CDL cluster blade. In another example, the system manager may be responsible for handling OAM related activity of the system and may reside only on the management blade of the cluster. In another example, the CDL manager may be responsible for handling CDL data access related requests and may reside only on the payload blade of the CDL cluster. In an exemplary embodiment, typical process and blade layouts for one blade (single), two blade (dual), and six blade CDL clusters may be as shown in Tables 1-3 below. In this example, the layout may also capture the virtual IP requirements of the system manager and CDL manager processes. [Table 1] [Table 2] [Table 3]

[0079] In an exemplary embodiment, a CDL cluster may be created to meet circle-specific centralized data access requirements and may be referred to as a circle-specific CDL cluster. This implementation may enable client application services to have a centralized view of data at the circle level. For example, a service may use a CDL framework with a circle-specific CDL cluster configuration. In an alternative embodiment, there may be other requirements where a client application service may require centralized data access across different circles. For example, a centralized service may be required across a country. This implementation may be referred to as a centralized CDL cluster.

[0080] FIG. 5 illustrates an example representation (500) of a circle-based CDL framework, according to one embodiment of the present disclosure.

[0081] The CDL servers shown in FIG. 5 may be cluster applications that belong to a particular cluster corresponding to each circle, for example, Circle A (502) and Circle B (504) may belong to Application Cluster 1 and Application Cluster 2, respectively. For simplicity, only two circles (Circle A and Circle B) are illustrated, but it should be understood that the implementation is applicable across various other circles. In an exemplary embodiment, when an enterprise's presence is distributed across different circles, the call admission control (CAC) service may require the implementation of centralized data access. In one embodiment, to meet this requirement, the deployment shown in FIG. 5 may be used, where a CDL cluster may be created in one of the circles, but all other circle-specific CDL clusters (belonging to Circle A 502 and Circle B 504) may communicate with the CDL agent (510). In one embodiment, each circle-specific CDL cluster at the circle level (502 and / or 504) may also include a CDL agent internally configured to communicate with the CDL agent (510). In one example, the CDL cluster installation configuration and output directory folders may be configured in different locations so that it may not interfere with the functioning of existing BTAS or EPS clusters. In an exemplary embodiment, the CDL client library may be embedded inside the BTAS session manager by default and may further include a CDL manager process. In an alternative exemplary embodiment, the OAM and CDL manager may function in a 2N and N+M redundancy model to accommodate any process or blade level failure, and each active OAM and CDL manager may require a virtual IP. Each CDL agent may contact the active CDL manager using the virtual IP.

[0082] FIG. 6 illustrates an exemplary sequence diagram of a method (600) for implementing the proposed mechanism according to one embodiment of the present disclosure.

[0083] As shown in Figure 6, the method (600) mainly describes the key steps used by the BTAS (102) in managing communication requests from a user device / user equipment (UE) (110) that may or may not be allowed based on an evaluation performed by the CDL server (104).

[0084] At step 610: The communication request sent by the UE 110 may be forwarded to the BTAS (102) via a component of the IMS, namely the S-CSCF 602.

[0085] In step 612: Based on the communication request, the BTAS (102) may forward the communication request to the CDL server (104) along with a set of information, such as an endpoint identifier (EID), a CUG ID, a CAC policy, maximum allowed channel limits, and other such information.

[0086] In step 614: the CDL server (104) may evaluate the request to check whether the communication may be allowed. In an exemplary embodiment, the evaluation may be performed by checking whether the total number of communication requests, such as calls (within one circle or between different circles), exceeds a predefined limit. Based on the evaluation, if the predefined limit is not exceeded, then the CDL server (104) may send a response including an indication of permission. In one example, the CDL server (104) may also send a token with an indication of permission to identify the allowed communication as a criterion. If no response may be received from the CDL server (104) within a predefined duration, then the communication may be considered as allowed.

[0087] In steps 616 and 618: If communication is allowed or if there is no response from the CDL server (104) within a predefined duration, an invitation may be sent from the BTAS (102) to the term I-CSCF (604).

[0088] In step 620: the term ICSCF (604) may communicate with the user device UE (110) to initiate communication by sending a communication request. The call mode may be indicated as the SIP response code 180.

[0089] In step 622: The term ICSCF (604) may send a SIP response code of 200 to the UE (110).

[0090] In step 624: The UE (110) may send a message, ie, "goodbye," to the BTAS (102).

[0091] In step 626: the BTAS (102) may send a communication request including a set of information, such as an EID, a CUG ID, a CAC policy, and a maximum limit of allowed channels, to the CDL server (104) along with the token received in step 614.

[0092] In step 628: the BTAS (102) may send a "goodbye" to the term ICSCF (604).

[0093] In step 630: The term ICSCF (604) may send a SIP response code of 200 to the UE (110).

[0094] In one embodiment, the communication request may be derived based on an original request from the UE (110). The original request may indicate a requirement for the UE (110) to establish communication with at least one entity device of the same CUG in the enterprise. The set of information may include, but is not limited to, an identification or enterprise identification (ID) for the enterprise, a CUG ID, a CAC policy, a maximum number of allowed communications / channels, and a predefined limit, and other such information. Various other types of information may also be within the scope of this disclosure. In an example embodiment, the CAC may facilitate control over the number of communication requests that may need to be processed simultaneously in a particular CUG or all CUGs. The communication request may be managed based on various CAC policies, including, but not limited to, a circle-based CAC policy and a centralized CAC policy. A circle-based CAC policy may be applicable when an enterprise or CUG belongs to one circle. A centralized CAC policy may be applicable when an enterprise or CUG belongs to multiple circles. Various other CAC policies may also be within the scope of this disclosure.

[0095] In an exemplary embodiment, if the maximum number of allowed channels is not violated, then the communication request may be allowed and added to the existing pool. Furthermore, if the communication request is allowed, a response may be sent back to the BTAS (102) from the CDL server (104) indicating that the communication has been allowed.

[0096] In an alternative embodiment, if the maximum number of allowed channels is violated, then an acknowledgment may be sent back to the BTAS (102) indicating that the communication is not allowed. The centralized CAC policy may be required to include a count of parallel or simultaneous communications (such as ongoing calls) that are initiated in various circles upon receiving a communication request with a set of information at the CDL server (104). A timer configured as "RT_CDL_CENTRLSD_DATA_REFRESH_TIM" may be initiated by the CDL server of each circle for each company / CUG with the CAC policy. The timer may define a duration having a predefined value. After expiry of the duration, the CDL server of the circle may send a message to the CDL cluster, the first message may include details regarding the ongoing simultaneous calls in that circle, company ID, CUG ID, and other such details. Upon receiving the first message by the CDL cluster, an evaluation may be performed by the CDL cluster. For example, the CDL cluster may sum the value of the received simultaneous calls to a "cumulative count" that may have been maintained after receiving messages from other circles with the same company and CUG. Based on this evaluation, the CDL cluster may send a second message to the CDL server, where the second message may include the cumulative count stored by the CDL server. In this manner, the CDL server may evaluate whether the communication request may be allowed or not based on the cumulative count obtained from the CDL cluster. Furthermore, if the communication request is not allowed or is disconnected, a trigger may be sent to the CDL servers in the circle, which may then delete the call entry made at the call initiation. In an alternative embodiment, if no response is received from the CDL server within a configured time interval (e.g., configured in the parameter "RT_AS_CAC_WAIT_TIMER"), then the communication may continue or may be considered allowed by the BTAS (102).

[0097] FIG. 7 illustrates an example sequence diagram of a method (700) for CDL processing multiple calls according to one embodiment of the present disclosure.

[0098] In step 718: The UE may send an invite to SCSCF-1 (706) via BTAS-1 (702).

[0099] At step 720: SCSCF-1 (706) may send an invitation to BTAS-1 (702).

[0100] At step 722: BTAS-1 (702) may send an invitation to SCSCF-1 (706).

[0101] At step 724: SCSCF-1 (706) may send an invitation to B Party 1 (704).

[0102] In step 726: B Party 1 (704) may send SIP Code 180 to SCSCF-1 (706).

[0103] In step 728: SCSCF-1 (706) may send SIP code 180 to BTAS-1 (702).

[0104] At step 730: BTAS-1 (702) may send the call details to the CDL (710), and the CDL (710) may update the call details.

[0105] In step 732: BTAS-1 (702) may send a SIP code to SCSCF-1 (706).

[0106] In step 734: The SCSCF-1 (706) may send a SIP code 180 to the UE.

[0107] In step 736: C-Party (716) may send an invitation to SCSCF-2 (714).

[0108] At step 738: SCSCF-2 (714) may send an invitation to BTAS-2 (712).

[0109] At step 740: BTAS-2 (702) may retrieve the call details and send them to the CDL (710). The CDL (710) may retrieve the call details and respond with the call details.

[0110] At step 742: The CDL (710) may send the call details to BTAS-2 (712). BTAS-2 (712) may modify the invitation and forward the invitation to B-Party-1 (704) or B-Party-2 (708).

[0111] At step 744: BTAS-2 (712) may send an invitation to SCSCF-2 (714).

[0112] In step 746: SCSCF-2 (714) may send an invitation to SCSCF-1 (706).

[0113] In step 748: SCSCF-1 (706) may send an invitation to BTAS-1 (702).

[0114] In step 750: C Party (716) may send a "2XX" in response to the invitation sent by BTAS-1 (702).

[0115] In step 752, the C party (716) may send a SIP code 200 to the SCSCF-2 (714).

[0116] At step 754: SCSCF-2 (714) may send a SIP code 200 to BTAS-2 (712).

[0117] In step 756: BTAS-2 (712) may send SIP code 200 back to SCSCF-2 (714).

[0118] In step 758: SCSCF-2 (714) may send a SIP code 200 to SCSCF-1 (706).

[0119] In step 760: SCSCF-1 (706) may send SIP code 200 to BTAS-1 (702) and delete the call details.

[0120] In step 762: BTAS-1 (702) may delete the call details of B-Party-1 (704) or B-Party-2 (708) and send it to the CDL (710).

[0121] In step 764: BTAS-1 (702) may send a SIP code 200 to SCSCF-1 (706).

[0122] In step 766: The SCSCF-1 (706) may send a SIP code 200 to the UE.

[0123] FIG. 8 illustrates an example computer system (800) in which or with which the proposed system may be implemented according to an embodiment of the present disclosure.

[0124] As shown in FIG. 8, the computer system (800) may include an external storage device (810), a bus (820), a main memory (830), a read-only memory (840), a mass storage device (850), a communication port (860), and a processor (870). Those skilled in the art will appreciate that the computer system (800) may include more than one processor and communication port. The processor (870) may include various modules associated with the embodiments of the present disclosure. The communication port (860) may be any of an RS-232 for use with a modem-based dial-up connection, a 10 / 100 Ethernet port, a 1 Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or any other existing or future port. The communication port (860) may be chosen depending on the network, such as a local area network (LAN), a wide area network (WAN), or any network to which the computer system (800) is connected.

[0125] In one embodiment, main memory (830) may be a random access memory (RAM) or any other dynamic storage device commonly known in the art. Read-only memory (840) may be any static storage device, such as, but not limited to, a programmable read only memory (PROM) chip for storing static information, such as, for example, boot-up or basic input / output system (BIOS) instructions for processor (870). Mass storage device (850) may be any current or future mass storage solution that can be used to store information and / or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid state drives (e.g., Universal Serial Bus (USB) and / or Firewire interfaces).

[0126] In one embodiment, the bus (820) may communicatively couple the processor (870) to other memory, storage, and communication blocks and may be, for example, a Peripheral Component Interconnect (PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), USB, etc. for connecting expansion cards, drives, and other subsystems as well as other buses, such as a Front Side Bus (FSB), that connect the processor (870) to the computer system (800).

[0127] In another embodiment, operator and management interfaces, such as a display, keyboard, and cursor control devices, may also be coupled to the bus (820) to support direct operator interaction with the computer system (800). Other operator and management interfaces may be provided through a network connection connected through a communications port (860). The components described above are intended only to illustrate various possibilities. The exemplary computer system (800) described above should in no way limit the scope of the present disclosure.

[0128] Although considerable emphasis has been placed herein on the preferred embodiments, it will be understood that many embodiments can be made and that many modifications can be made to the preferred embodiments without departing from the principles of the present disclosure. These and other modifications in the preferred embodiments of the present disclosure will be apparent to those skilled in the art from the present disclosure herein, and it is to be clearly understood that the foregoing description is not intended to limit the present disclosure, but is instead provided by way of illustration only.

[0129] Advantages of the Invention The present disclosure provides a system and method for using a Business Telephony Application Server (BTAS) to provide Session Initiation Protocol (SIP) trunking and Internet Protocol (IP) Centrex services to customers.

[0130] An advantage of the present disclosure is to provide a system and method that uses a BTAS to provide supplementary services to customers, such as closed user groups (CUGs), short code dialing, and conferencing.

[0131] An advantage of the present disclosure is to provide a system and method using a BTAS that uses call admission control (CAC) services to simultaneously control several calls in a particular CUG.

[0132] An advantage of the present disclosure is to provide a system and method with BTAS that uses circle-based CAC with a centralized data layer (CDL) server that maintains accounts for several calls in the circle-based CAC.

[0133] An advantage of the present disclosure is to provide a system and method that uses a BTAS with a circle-based CDL to meet circle-specific data access requirements.

[0134] An advantage of the present disclosure is that it facilitates effective and improved management of traffic volumes related to communication requests.

[0135] An advantage of the present disclosure is to facilitate an economical and next generation based system and method that can eliminate network congestion or overload caused by excess traffic, thus creating network services to improve efficiency and quality of service.

[0136] An advantage of the present disclosure is that it facilitates a system and method that can enable managing the volume of communication requests within or between multiple circles.

Claims

1. A system (100) for establishing one or more connections, comprising: One or more processors (202) operatively coupled to a business telephony application server (BTAS) (102), the one or more processors (202) coupled to a memory (204), the memory (204), when executed by the one or more processors (202), causing the one or more processors (202) to: receiving one or more communication requests from one or more user devices (110) over a communications network (112), the one or more communication requests being based on one or more input parameters; transmitting the one or more communication requests via the communication network (112) to a Centralized Data Layer (CDL) server (104), the CDL server (104) being configured to approve the received one or more communication requests based on one or more predefined rules; receiving the approved communication request or requests from the CDL server (104) via the communication network (112); establishing the one or more connections between the one or more user devices (110) and a BTAS (102) based on the approved one or more communication requests; the one or more processors (202) storing instructions for causing the one or more processors to The system (100).

2. 2. The system of claim 1, wherein the one or more processors are configured to process the received one or more communication requests and enable one or more service chain logic executions associated with the received one or more communication requests.

3. The system of claim 1 , wherein the one or more processors are configured to manage faults, configurations, and performance associated with the received one or more communication requests.

4. 2. The system of claim 1, wherein the one or more processors are configured to store one or more database clusters and to update changes in the one or more database clusters associated with the received one or more communication requests.

5. 5. The system of claim 4, wherein the one or more processors are configured to debug the one or more database clusters associated with the received one or more communication requests.

6. 2. The system (100) of claim 1, wherein the CDL server (104) is configured with one or more call admission control (CAC) services to process the received one or more communication requests.

7. 2. The system of claim 1, wherein the CDL server is configured with one or a combination of a circle-based call admission control (CAC) service and a centralized CAC service to process the received one or more communication requests.

8. 2. The system (100) of claim 1, wherein the one or more input parameters include at least one of an enterprise identification (ID), a closed user group (CUG) ID, a call admission control (CAC) policy, and one or more channels used by the CAC policy.

9. 2. The system (100) of claim 1, wherein the one or more predefined rules of the CDL server (104) are based on one or more validations from an external server, the external server being configured to validate the one or more input parameters associated with the one or more user devices (110).

10. 10. The system of claim 9, wherein the CDL server is configured with a timer to record the one or more communication requests from the one or more user devices and to transmit the one or more communication requests to the external server for the one or more verifications.

11. The system (100) of claim 6, wherein the one or more CAC services comprise at least one CAC cluster for processing the one or more communication requests.

12. 1. A method for establishing one or more connections, comprising: receiving, by one or more processors (202) operatively coupled to a business telephony application server (BTAS) (102), one or more communication requests from one or more user devices (110) over a communication network (112), the one or more communication requests being associated with one or more input parameters; transmitting, by the one or more processors (202), the one or more communication requests over the communication network (112) to a Centralized Data Layer (CDL) server (104), wherein the CDL server (104) is configured to approve the one or more communication requests based on one or more predefined rules; receiving, by the one or more processors (202), the approved one or more communication requests from the CDL server (104) via the communication network (112); establishing, by the one or more processors (202), the one or more connections between the one or more user devices (110) and the BTAS (102) based on the approved one or more communication requests; The method comprising:

13. 13. The method of claim 12, comprising processing, by the one or more processors (202), the one or more communication requests and enabling one or more service chain logic executions associated with the one or more communication requests.

14. The method of claim 12, comprising managing, by the one or more processors (202), faults, configurations, and performance associated with the one or more communication requests.

15. 13. The method of claim 12, further comprising storing, by the one or more processors (202), one or more database clusters and updating changes associated with the one or more communication requests in the one or more database clusters.

16. 16. The method of claim 15, further comprising debugging, by the one or more processors (202), the one or more database clusters associated with the one or more communication requests.

17. A User Equipment (UE) (110) for establishing one or more connections, comprising: One or more processors communicatively coupled to one or more processors in a system, the one or more processors coupled to a memory, the memory, when executed by the one or more processors, providing to the UE: causing said one or more processors (202) to transmit one or more communication requests over a communications network (112); the one or more processors storing instructions; Equipped with The one or more processors (202) are operatively coupled to a Business Telephony Application Server (BTAS), the one or more processors comprising: receiving the one or more communication requests from the UE (110); sending the one or more communication requests via the communication network (112) to a Centralized Data Layer (CDL) server (104), the CDL server (104) being configured to approve the one or more communication requests based on one or more predefined rules; receiving the approved communication request or requests from the CDL server (104) via the communication network (112); establishing the one or more connections between the UE (110) and the BTAS (102) based on the approved one or more communication requests; The user equipment (UE) (110) is configured to perform the following:

18. 1. A non-transitory computer readable medium comprising a processor having executable instructions, the processor comprising: receiving one or more communication requests from one or more user devices (110) over a communications network (112), the one or more communication requests being based on one or more input parameters; transmitting the one or more communication requests via the communication network (112) to a Centralized Data Layer (CDL) server (104), the CDL server (104) being configured to approve the received one or more communication requests based on one or more predefined rules; receiving the approved communication request or requests from the CDL server (104) via the communication network (112); establishing one or more connections between the one or more user devices (110) and a Business Telephony Application Server (BTAS) (102) based on the approved one or more communication requests; The non-transitory computer-readable medium.

Images