WO2025099774A1

WO2025099774A1 - System and method to rollout a toll-free number

Info

Publication number: WO2025099774A1
Application number: PCT/IN2024/052216
Authority: WO
Inventors: Aayush Bhatnagar; Birendra SINGH BISHT; Harbinder PAL SINGH; Sandeep Gupta; Smrithy Sivakumar; Md Kashif Eqbal; Gagandeep Singh
Original assignee: Jio Platforms Ltd
Current assignee: Jio Platforms Ltd
Priority date: 2023-11-09
Filing date: 2024-11-09
Publication date: 2025-05-15
Anticipated expiration: 2026-05-09

Abstract

The present disclosure envisages a system (108) and a method (600) to rollout a toll- free number in a network (106) The method (600) comprises receiving, by a receiving unit (118), at least one call associated with a toll-free number from an originating circle. The method (600) comprises providing, by a processing unit (116), a configuration of the at least one toll-free number to at least one Business Telephony Application Server (BTAS) (124) of the originating circle. The method (600) comprises converting, by the processing unit (116), the at least one toll-free number from a first format to a second format and the method (600) comprises terminating, by the processing unit (116), the at least one call comprising the converted toll-free number towards the at least one BTAS (124) of the originating circle.

Description

SYSTEM AND METHOD TO ROLLOUT A TOLL-FREE NUMBER

RESERVATION OF RIGHTS

[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, Integrated Circuit (IC) layout design, and/or trade dress protection, belonging to JIO PLATFORMS LIMITED or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.

FIELD OF THE DISCLOSURE

[0002] The present disclosure relates generally to the field of wireless communication networks. More particularly, the present disclosure relates to a system and a method to rollout a toll-free number in a network.

DEFINITION

[0003] As used in the present disclosure, the following terms are generally intended to have the meaning as set forth below, except to the extent that the context in which they are used to indicate otherwise.

[0004] The expression “Session Initiation Protocol (SIP)” used hereinafter in the specification refers to a signaling protocol used for initiating, maintaining, and terminating real-time sessions that include voice, video, and messaging applications. SIP is a fundamental protocol in IP -based communication networks.

[0005] The expression “Internet Protocol (IP)” used hereinafter in the specification refers to a set of rules governing the data format sent over the internet or other networks. The IP is the principal communications protocol in the Internet Protocol Suite for relaying datagrams across network boundaries. [0006] The expression “Public Switched Telephone Network (PSTN)” used hereinafter in the specification refers to the traditional circuit-switched telephone network that provides the infrastructure and services for public telecommunication.

[0007] The expression “Integrated Services Digital Network (ISDN)” used hereinafter in the specification refers to a set of communication standards for the digital transmission of voice, video, data, and other network services over the traditional circuits of the PSTN.

[0008] The expression “Internet Protocol Multimedia Subsystem (IMS)” used hereinafter in the specification refers to an architectural framework for delivering IP multimedia services. The IMS provides a standardized, modular framework for managing and delivering multimedia applications over IP networks.

[0009] The expression “Proxy-Call Session Control Function (P-CSCF)” used hereinafter in the specification refers to a critical component in an IP-IMS architecture. The P-CSCF is responsible for acting as the first contact point for the User Equipment (UE) in the IMS network, handling signaling, and managing call control functions.

[0010] The expression “Serving-Call Session Control Function (S-CSCF)” used hereinafter in the specification refers to a central node in the IMS architecture that performs session control, service invocation, and maintains user session states. The S- CSCF is pivotal in handling and routing SIP requests.

[0011] The expression “Breakout Gateway Control Function (BGCF)” used hereinafter in the specification refers to a function within the IMS network that determines the appropriate network for routing a call when the destination is not in the IMS network, usually to the PSTN.

[0012] The expression “Media Resource Function (MRF)” used hereinafter in the specification refers to a network entity that provides media-related functions, such as playing announcements, mixing audio streams, or managing multimedia conferences within the IMS network. [0013] The expression “Telephony Application Server (TAS)” used hereinafter in the specification refers to a server within the IMS network that handles telephony applications and services. The TAS refers to a server that encompasses various types of telephony servers, including those used for voice, video, and messaging services. The TAS handles features like call routing, call forwarding, voicemail, and conferencing. The TAS provides all essential call processing services. The services include digit analysis, call setup, call waiting, call forwarding, conference calling, call termination and additional multimedia functions.

[0014] The expression “Business Telephony Application Server (BTAS)” used hereinafter in the specification refers to a specific type of TAS that is tailored for business telephony applications. The BTAS typically handles features like call routing, call forwarding, voicemail, and conferencing. The BTAS is often deployed in enterprise networks or carrier networks to provide a range of business communication services.

[0015] The expression “Border Gateway Function (BGF)” used hereinafter in the specification refers to a network element that facilitates the interconnection between different networks, typically controlling media traffic that traverses the borders of those networks, such as between IP and PSTN networks.

[0016] The expression “Application Server (AS)” used hereinafter in the specification refers to a server that hosts and executes applications and services, handling specific functions such as multimedia messaging, conferencing, or any other specialized service within the network.

[0017] The expression “Session Description Protocol (SDP)” used hereinafter in the specification refers to a format for describing multimedia communication sessions for session announcement, invitation, and initiation. The SDP is widely used in the SIP to convey information about media streams. [0018] The expression “SIP Uniform Resource Identifier (SIP URI)” used hereinafter in the specification refers to an identifier used in the Session Initiation Protocol (SIP) to specify a particular user or service in a network. The SIP URI functions similarly to an email address in SIP communications.

[0019] The expression “Telephone Uniform Resource Identifier (TEL URI),” used hereinafter in the specification, refers to a URI scheme used to identify a telephone number. The TEL URI is used in communications to represent a phone number in a format that various network elements can interpret.

[0020] The expression “DID number” used hereinafter in the specification refers to a Direct Inward Dialing number that allows callers to directly reach a specific phone within an organization without going through a central switchboard.

[0021] The expression “toll-free number” used hereinafter in the specification refers to a telephone number that allows callers to dial a specific number without incurring any charges. Toll-free numbers are typically used by businesses and organizations to provide a convenient and accessible way for customers to contact them.

[0022] The expression “originating circle” used hereinafter in the specification refers to a geographical region or area from where a phone call originates. In the context of telecommunications networks, it typically corresponds to a specific geographical area within a country or region, often defined by a local access network or exchange.

[0023] The expression “VoLTE (Voice over Long-Term Evolution)” used hereinafter in the specification refers to a technology that allows voice calls to be carried over LTE cellular networks.

[0024] The expression “on-net call” used hereinafter in the specification refers to a phone call made between two subscribers within the same mobile network operator. [0025] The expression “off-net call” used hereinafter in the specification refers to a phone call made between subscribers of different mobile network operators.

BACKGROUND

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

[0027] Wireless communication technology has rapidly evolved over the past few decades. The first generation of wireless communication technology was analog technology that offered only voice services. Further, when the second-generation (2G) technology was introduced, text messaging and data services became possible. The third-generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized wireless communication with faster data speeds, improved network coverage, and security. Currently, the fifth-generation (5G) technology is being deployed, with even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. The sixth generation (6G) technology promises to build upon these advancements, pushing the boundaries of wireless communication even further. While the 5G technology is still being rolled out globally, research and development into the 6G are rapidly progressing, with the aim of revolutionizing the way we connect and interact with technology.

[0028] Telecommunications service providers receive calls from customers and route the calls to the appropriate destinations. For example, a call placed from a customer of a first local communications service provider to another region supported by a second local communications service provider is routed to a long-haul communications carrier for communication between the two local communications service providers. Similarly, calls to toll-free telephone numbers (e.g., 1800 numbers) are routed to a toll-free service provider or interexchange carrier for routing to the appropriate communications service providers that service the toll-free telephone numbers.

[0029] Communications service providers provide toll-free numbers to their customers or to contact sales or service customer representatives. Most larger communications service providers generally have thousands of toll-free telephone numbers. However, the traditional techniques for establishing or configuring a new toll-free number in the communication network are difficult and cumbersome. Further, the traditional techniques fail to efficiently route the toll-free numbers in the communication network.

[0030] Hence, there is a need for a system and a method that efficiently rollout a toll-free number in the communication network.

SUMMARY OF THE DISCLOSURE

[0031] In an exemplary embodiment, the present disclosure relates to a method to rollout a toll-free number in a network. The method comprises receiving at least one call associated with a toll-free number from an originating circle by a receiving unit, providing a configuration of the at least one toll-free number to at least one Business Telephony Application Server (BTAS) of the originating circle by a processing unit, converting the at least one toll-free number from a first format to a second format by the processing unit and terminating the at least one call comprising the converted toll- free number towards the at least one BTAS of the originating circle by the processing unit.

[0032] In an embodiment, the first format is a Telephone (Tel) universal resource identifier (URI) format, and the second format is a session initiation protocol (SIP) URI format. [0033] In an embodiment, the at least one call includes at least one of an on-net call, a Voice over Long Term Evolution (VoLTE) call, and an off-net call.

[0034] In an embodiment, the conversion of the at least one toll-free number from the first format to the second format is performed either by the at least one BTAS of the originating circle or at least one Media Gateway Control Function (MGCF) of the originating circle.

[0035] In an embodiment, the at least one BTAS modifies the at least one converted toll-free number to a Direct Inward Dialing (DID) number.

[0036] In an exemplary embodiment, the present disclosure relates to a system to rollout a toll-free number in a network. The system comprises a receiving unit configured to receive at least one call associated with a toll-free number from an originating circle, a memory and a processing unit coupled with the receiving unit to receive the at least one call associated with the toll-free number from the originating circle and is further coupled with the memory to execute a set of instructions stored in the memory. The processing unit is configured to provide a configuration of the at least one toll-free number to at least one Business Telephony Application Server (BTAS) of the originating circle, convert the at least one toll-free number from a first format to a second format and terminate the at least one call comprising the converted toll-free number towards the at least one BTAS of the originating circle.

[0037] In an exemplary embodiment, the present disclosure relates to a user equipment (UE) communicatively coupled with a network. The coupling includes steps of receiving at least one call associated with a toll-free number from an originating circle by a receiving unit, providing a configuration of the at least one toll-free number to at least one Business Telephony Application Server (BTAS) of the originating circle by a processing unit, converting the at least one toll-free number from a first format to a second format by the processing unit and terminating the at least one call comprising the converted toll-free number towards the at least one BTAS of the originating circle by the processing unit. [0038] In another exemplary embodiment, the present disclosure relates to a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method to rollout a toll-free number in a network. The method includes receiving at least one call associated with a toll-free number from an originating circle by a receiving unit, providing a configuration of the at least one toll- free number to at least one Business Telephony Application Server (BTAS) of the originating circle by a processing unit, converting the at least one toll-free number from a first format to a second format by the processing unit and terminating the at least one call comprising the converted toll-free number towards the at least one BTAS of the originating circle by the processing unit.

[0039] The foregoing general description of the illustrative embodiments and the following detailed description thereof are merely exemplary aspects of the teachings of this disclosure and are not restrictive.

OBJECTIVES OF THE DISCLOSURE

[0040] Some of the objectives of the present disclosure, which at least one embodiment herein satisfies, are as follows:

[0041] An objective of the present disclosure is to provide a system and a method that provides an efficient routing of a toll-free number in a communication network.

[0042] Another objective of the present disclosure is to provide the system and the method that provides a seamless rollout of Business Telephony Application Server (BTAS) toll-free number service in the communication network.

[0043] Other objectives and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.

BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING [0044] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.

[0045] FIG. 1A illustrates an exemplary network architecture to rollout a toll- free number in a network, in accordance with an embodiment of the present disclosure.

[0046] FIG. IB illustrates an exemplary block diagram of the system to rollout the toll-free number in the network, in accordance with an embodiment of the present disclosure.

[0047] FIG. 1C illustrates an exemplary system architecture to rollout the toll- free number in the network, in accordance with an embodiment of the present disclosure.

[0048] FIG. 2 illustrates another exemplary system architecture to rollout the toll-free number in the network, in accordance with an embodiment of the present disclosure.

[0049] FIG. 3 illustrates an exemplary flow diagram of a method to rollout the toll-free number in the network, in accordance with an embodiment of the present disclosure.

[0050] FIG. 4 illustrates another exemplary flow diagram of the method to rollout the toll-free number in the network, in accordance with an embodiment of the present disclosure. [0051] FIG. 5 illustrates a computer system in which or with which the embodiments of the present disclosure may be implemented.

[0052] FIG. 6 illustrates another exemplary flow diagram of the method to rollout the toll-free number in the network, in accordance with an embodiment of the present disclosure.

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

LIST OF REFERENCE NUMERALS

100A - Network Architecture

102-1, 102-2... 102-N - Plurality of Users

104-1, 104-2... 104-N, 202 - Plurality of User Equipments (UEs)

106 - Network

108 - System

100B - Block Diagram

HO - Processor(s)

112 - Memory

114 - Plurality of Interfaces

116 - Processing unit

118 - Receiving unit

120 - Database

100C - System architecture

122, 224 - Provisioning server 124-1, 124-2, 124-3, 124-N, 222 - Business Telephony Application Server (BTAS)

200 - System architecture

204 - IP Multimedia Subsystem (IMS) network

206 - Mobile Number Portability (MNP)

208 - Online Charging System (OCS)

210 - Diameter Routing Agent (DRA)

212 - Caller Ring Back Tones (CRBT)

214 - Media Resource Function (MRF)

216 - Element Management System (EMS)

218 - Operations Support Systems (OSS) / Business Support Systems (BSS)

220 - Load balancer

300, 400, 600 - Flow Diagram

301- Proxy Call Session Control Function (P-CSCF)

303- Serving Call Session Control Function (S-CSCF)

305- Telephony Application Server (TAS)

307- Interconnection Border Control Function (IBCF)

500 - Computer System

510 - External Storage Device

520 - Bus

530 - Main Memory 540 - Read-Only Memory

550 - Mass Storage Device

560 - Communication Ports

570 - Processor

DETAILED DESCRIPTION

[0054] In the following description, for the purposes of explanation, various specific details are set forth to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein. Example embodiments of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.

[0055] 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 in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

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

[0057] Also, it is noted that individual 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 the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. 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 can correspond to a return of the function to the calling function or the main function.

[0058] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive like the term “comprising” as an open transition word without precluding any additional or other elements.

[0059] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0060] The terminology used herein is to describe embodiments only and is not intended to be limiting the disclosure. As used herein, the singular forms “a” “an”, and “the” are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any combinations of one or more of the associated listed items. It should be noted that the terms “mobile device”, “user equipment”, “user device”, “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The invention is not limited to any device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.

[0061] As used herein, an “electronic device” or “portable electronic device” or “user device” or “communication device” or “user equipment” or “device” refers to any electrical, electronic, electromechanical, and computing device. The user device can receive and/or transmitting one or parameters, performing function/s, communicating with other user devices, and transmitting data to the other user devices. The user equipment may have a processor, a display, a memory, a battery, and an input-means such as a hard keypad and/or a soft keypad. The user equipment may be capable of operating on any radio access technology including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For instance, the user equipment may include, but not limited to, a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.

[0062] Further, the user device may also comprise a “processor” or “processing unit” includes processing unit, wherein processor refers to any logic circuitry for processing instructions. The processor may be a general -purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor is a hardware processor.

[0063] As portable electronic devices and wireless technologies continue to improve and grow in popularity, the advancing wireless technologies for data transfer are also expected to evolve and replace the older generations of technologies. In the field of wireless data communications, the dynamic advancement of various generations of cellular technology are also seen. The development, in this respect, has been incremental in the order of second generation (2G), third generation (3G), fourth generation (4G), and now fifth generation (5G), and more such generations are expected to continue in the forthcoming time.

[0064] Radio Access Technology (RAT) refers to the technology used by mobile devices/ user equipment (UE) to connect to a cellular network. It refers to the specific protocol and standards that govern the way devices communicate with base stations, which are responsible for providing the wireless connection. Further, each RAT has its own set of protocols and standards for communication, which define the frequency bands, modulation techniques, and other parameters used for transmitting and receiving data. Examples of RATs include GSM (Global System for Mobile Communications), CDMA (Code Division Multiple Access), UMTS (Universal Mobile Telecommunications System), LTE (Long-Term Evolution), and 5G. The choice of RAT depends on a variety of factors, including the network infrastructure, the available spectrum, and the mobile device's/device's capabilities. Mobile devices often support multiple RATs, allowing them to connect to several types of networks and provide optimal performance based on the available network resources.

[0065] While considerable emphasis has been placed herein on the components and component parts of the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiment as well as other embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be interpreted merely as illustrative of the disclosure and not as a limitation.

[0066] As the wireless technologies are advancing, there is a need to cope up with the 5G requirements and deliver a prominent level of service to the customers. Service providers provide toll free numbers to its customers or to contact sales or service customer representatives. Most larger telecommunications service providers have generally thousands of toll-free telephone numbers. However, the traditional techniques for establishing or configuring a new toll-number in the communication network is a difficult and cumbersome process. Further, the traditional techniques fail to route the toll-free numbers in the communication network efficiently.

[0067] The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing an improved system and a method to efficiently rollout a toll-free number in the communication network.

[0068] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings. [0069] The various embodiments throughout the disclosure will be explained in more detail with reference to FIG. 1 A - FIG. 6.

[0070] FIG. 1A illustrates an exemplary network architecture (100A) to rollout a toll-free number in a network (106), in accordance with an embodiment of the present disclosure.

[0071] As illustrated in FIG. 1A, the network architecture (100A) may include one or more user equipments (UEs) (104-1, 104-2... 104-N) associated with one or more users (102-1, 102-2... 102-N) in an environment. A person of ordinary skill in the art will understand that one or more users (102-1, 102-2... 102-N) may collectively referred to as the users (102). Similarly, a person of ordinary skill in the art will understand that one or more UEs (104-1, 104-2... 104-N) may be collectively referred to as the UE (104). Although only three UE (104) are depicted in FIG. 1A, however, any number of the UE (104) may be included without departing from the scope of the ongoing description.

[0072] In an embodiment, the UE (104) may include smart devices operating in a smart environment, for example, an Internet of Things (loT) system. In such an embodiment, the UE (104) may include, but are not limited to, smartphones, smart watches, smart sensors (e.g., mechanical, thermal, electrical, magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart television (TV), computers, smart security system, smart home system, other devices for monitoring or interacting with or for the users (102) and/or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the UE (104) may include, but not limited to, intelligent, multisensing, network-connected devices, which may integrate seamlessly with each other and/or with a central server or a cloud-computing system or any other device that is network-connected. [0073] Additionally, in some embodiments, the UE (104) may include, but not limited to, a handheld wireless communication device (e.g., a mobile phone, a smartphone, a phablet device, and so on), a wearable computer device (e.g., a headmounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and/or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the UE (104) may include, but are not limited to, any electrical, electronic, electromechanical, or equipment, or a combination of one or more of the above devices, such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device, wherein the UE (104) may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user (102) or the entity such as touchpad, touch-enabled screen, electronic pen, and the like. A person of ordinary skill in the art will appreciate that the UE (104) may not be restricted to the mentioned devices and various other devices may be used.

[0074] Referring to FIG. 1A, the UE (104) may communicate with the system (108) through the network (106) for sending or receiving various types of data. In an embodiment, the network (106) may include at least one of a 5G network, 6G network, or the like. The network (106) may enable the UE (104) to communicate with other devices in the network architecture (100A) and/or with the system (108). The network (106) may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network (106) may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like. [0075] In an embodiment, the network (106) may include, by way of example but not limitation, 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 a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network (106) may also include, by way of example but not limitation, one or more of a radio access network (RAN), a wireless network, a wired network, an 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 some combination thereof.

[0076] In an embodiment, the UE (104) is communicatively coupled with the network (106). The network (106) may receive a connection request from the UE (104). The network (106) may send an acknowledgment of the connection request to the UE (104). The UE (104) may transmit a plurality of signals in response to the connection request.

[0077] Although FIG. 1A shows exemplary components of the network architecture (100A), in other embodiments, the network architecture (100 A) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 1A. Additionally, or alternatively, one or more components of the network architecture (100 A) may perform functions described as being performed by one or more other components of the network architecture (100A).

[0078] FIG. IB illustrates an exemplary block diagram (100B) of the system (108) to rollout the toll-free number in the network (106), in accordance with an embodiment of the present disclosure.

[0079] Referring to FIG. IB, in an embodiment, the system (108) may include one or more processor(s) (110), a memory (112), a plurality of interface(s) (114), a processing unit (116), a receiving unit (118) and a database (120). The one or more processor(s) (110) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (110) may be configured to fetch and execute computer-readable instructions stored in the memory (112) of the system (108). The memory (112) 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 over a network service. The memory (112) may include any non-transitory storage device including, for example, volatile memory such as random-access memory (RAM), or non-volatile memory such as erasable programmable read only memory (EPROM), flash memory, and the like.

[0080] In an embodiment, the interface(s) (114) may include a variety of interfaces, for example, interfaces for data input and output devices (RO), storage devices, and the like. The interface(s) (114) may facilitate communication through the system (108). The interface(s) (114) may also provide a communication pathway for one or more components of the system (108). Examples of such components include, but are not limited to, a processing unit (116) and a database (120).

[0081] The processing unit (116) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing unit (116). In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing unit (116) may be processor-executable instructions stored on a non-transitory machine -readable storage medium and the hardware for the processing unit (116) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine -readable storage medium may store instructions that, when executed by the processing resource, implement the processing unit (116). In such examples, the system may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system and the processing resource. In other examples, the processing unit (116) may be implemented by electronic circuitry. In an embodiment, the database (120) includes data that may be either stored or generated as a result of functionalities implemented by any of the components of the processor (110) or the processing unit (116).

[0082] In an embodiment, the receiving unit (118) is configured to receive at least one call associated with a toll-free number from an originating circle. The originating circle is a geographical region or area from where a phone call originates. In the context of telecommunications networks, it typically corresponds to a specific geographical area within a country or region, often defined by a local access network or exchange.

[0083] In an embodiment, a processing unit (116) may be interchangeably coupled with the receiving unit ( 118) to receive the at least one call associated with the toll-free number from the originating circle and is further coupled with the memory (112) to execute a set of instructions stored in the memory (112).

[0084] In an aspect, the memory (112) is configured to store the data received from the users (102). The program instructions include a program that implements a provisioning server to rollout a toll-free number in the communication network, in accordance with an embodiment of the present disclosure and may implement other embodiments described in this specification. The memory (112) may be configured to store preprocessed data, and a predefined set of parameters according to which the toll- free number is rolled out in the network (106), in accordance with an embodiment of the present disclosure. The memory (112) may include any computer-readable medium known in the art including, for example, volatile memory, such as Static Random Access Memory (SRAM) and Dynamic Random Access Memory (DRAM) and/or nonvolatile memory, such as Read Only Memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes [0085] The processing unit (116) may be configured to fetch and execute computer-readable instructions stored in the memory (112). The processing unit (116) may be configured to execute a sequence of instructions to rollout a toll-free number in the network (106), which may be embodied in a program or software. The instructions can be directed to the processing unit (116), which may subsequently program or otherwise be configured to implement the methods of the present disclosure. In some examples, the processing unit (116) is configured to control and/or communicate with large databases, perform high-volume transaction processing, and generate reports from large databases. The processing unit (116) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions.

[0086] In an aspect, the system (108) is configured to provide, by the processing unit (116), a configuration of at least one toll-free number to at least one Business Telephony Application Server (BTAS). The configuration of the at least one toll-free number is likely managed through the processing unit (116) and the database (120) that stores configuration data for all toll-free numbers. The processing unit (116) holds essential settings, such as routing rules, announcement preferences, and agent assignments, for at least one toll-free number. Once the configuration data is stored, it is distributed to the at least one BTAS in the originating circle. This distribution can occur through network management protocols or direct data transfers. Upon receiving the configuration, the at least one BTAS may update the internal databases and routing tables to reflect the newly provisioned toll-free number and its associated settings. The system (108) may also support real-time updates, enabling changes to toll-free number configurations to be quickly propagated to the at least one BTAS, ensuring timely and accurate adjustments.

[0087] In an aspect, the processing unit (116) is configured to convert the toll- free number in at least one originating call from a first format to a second format. In an embodiment, the first format may be a Telephone (Tel) URI (Universal Resource Identifier) format, while the second format is a Session Initiation Protocol (SIP) URI format. To convert a toll-free number from the Tel URI format to the SIP URI format, the processing unit first extracts the toll-free number from the Tel URI, which typically begins with the ‘tel: prefix’. The processing unit then removes the prefix to isolate the actual number. Next, the processing unit constructs the SIP URI by appending the extracted number to a predefined SIP domain. The converting of the toll-free number is performed either by the at least one BTAS or at least one Media Gateway Control Function (MGCF) of an originating circle.

[0088] In an aspect, the system (108) further includes an aspect where the conversion of the toll-free number is performed by either the at least one BTAS (124) or at least one Media Gateway Control Function (MGCF) of the originating circle. For the at least one VoLTE call and the at least one on-net call, the at least one BTAS (124) is responsible for converting the toll-free number from the Tel URI format to the SIP URI format, whereas, for the at least one off-net call, the conversion is handled by the at least one MGCF. This distinction in conversion responsibilities ensures that each type of call is handled by the network element, optimizing resource usage and call quality.

[0089] In an aspect, the system (108) is capable of handling various types of calls, including at least one of an on-net call, a Voice over Long-Term Evolution (VoLTE) call, and an off-net call. The flexibility to process different call types is key to ensuring the system (108) can manage toll-free calls in diverse scenarios. For instance, the at least one VoLTE calls may require specific handling due to the nature of IP-based networks. In contrast, the at least one on-net and the at least one off-net calls involve interactions within the same network or between different networks, respectively.

[0090] In an aspect, for the at least one VoLTE and the at least one on-net call, the at least one BTAS (124) converts the toll-free number, whereas for the at least one off-net calls, the at least one MGCF performs the conversion. This distribution of tasks between the at least one BTAS and the at least one MGCF enhances ability of the system (108) to handle toll-free numbers across different network environments, ensuring efficient call routing based on the specific requirements of each call type.

[0091] In another embodiment, the at least one BTAS (124) is also configured to modify the converted toll-free number into a Direct Inward Dialing (DID) number. The processing unit is configured to modify the converted toll-free number into the DID number by transforming the toll-free number into a format that adheres to local DID numbering conventions. The process includes adjusting the number's structure to meet specific digit length and prefix requirements, which may involve replacing the toll-free prefix (such as 800 or 888) with the DID prefix based on local regulations. Additionally, the toll-free number is normalized to remove any non-numeric characters, ensuring it aligns with the standard format expected by the private branch exchange (PBX) system. The processing unit updates call routing settings to ensure that incoming calls to the newly assigned DID number are directed to the correct internal extension or department within the organization’s PBX system. This integration enhances call management by allowing direct access to specific lines, streamlining communication processes, and ensuring that callers reach the intended recipient efficiently. This modification is essential for calls that need to be routed to specific extensions or departments within an organization, providing more targeted call delivery. The transformation of a toll-free number into a DID number allows businesses to maintain flexibility in call handling and ensures that toll-free calls can be efficiently directed to the internal destinations.

[0092] In an aspect, the processing unit (116) is configured to terminate the converted toll-free number towards the at least one BTAS (124) of the originating circle. This termination step involves directing the call to the at least one BTAS (124), where it can be further processed and routed within the network (106). The termination ensures that the toll-free number, once converted, reaches the intended destination within the originating circle for proper call completion. [0093] Referring to FIG. 1C, an exemplary system architecture (100C) to rollout the toll-free number in the network (106), in accordance with an embodiment of the present disclosure.

[0094] In an aspect, a provisioning server (122) may provide a configuration of a toll-free number to at least one Business Telephony Application Server (BTAS) (124- 1, 124-2, 124-3, 124-N). A person of ordinary skill in the art will understand that at least one BTAS (124-1, 124-2, 124-3... 124-N) may collectively referred to as the BTAS (124) or at least one BTAS (124). The at least one BTAS (124) is responsible for configuring and managing toll-free numbers. In an embodiment, BTAS-circle-1 (124-1) may be associated with an originating circle-1, BTAS-circle-2 (124-2) may be associated with an originating circle-2, BTAS-circle-3 (124-3) may be associated with originating circle-3, BTAS-circle-N (124-N) may be associated with an originating circle-N. In an embodiment, the originating circle may include a single BTAS. In another embodiment, the originating circle may include one or more BTAS that are logically connected with each other. In another embodiment, the one or more logically connected BTAS either represents one or more different enterprises or may represent a same enterprise.

[0095] In an aspect, the at least one BTAS of an originating circle may convert the toll-free number in an originating call from a first format to a second format by adding the same circle domain when the originating call may be at least one on-net originated call. In an aspect, the at least one BTAS may serve as the origination leg for an incoming call.

[0096] The toll-free number is provisioned in the at least one BTAS of the originating circle. For example, if the toll-free number is “100-200-300,” it is provisioned in every BTAS (124) across all originating circles, including BTAS (124- 1), BTAS (124-2), BTAS (124-3), up to BTAS (124-N). In an example, BTAS (124-1) corresponds to the originating circle (124-1), BTAS (124-2) corresponds to the originating circle (124-2), and so forth. In another scenario, when a call is originated at the originating circle BTAS (124-1), the call is terminated within at the BTAS (124- 1) which is the same originating circle, eliminating the need to route the call to another BTAS and then back to the originating BTAS (124-1).

[0097] In an embodiment, two logically connected BTAS (124) that may also be referred to as BTAS instances (124) may represent either the same enterprise or different enterprises. The two logically connected BTAS (124) belong to a same originating circle. The configuration enables a common toll-free number to serve as a bridge between users across different enterprises, allowing seamless connectivity. For instance, BTAS (124-1) and BTAS (124-2) could be associated with two different enterprises, each using the common toll-free number “100-200-300” to route specific calls. The setup allows users from either enterprise to connect by the toll-free number, while the BTAS instances (124) ensure that the calls are directed to the correct destination.

[0098] In an aspect, at least one media gateway control function (MGCF) of the originating circle may convert the toll-free number from a first format to a second format when the originating call may be at least one off-net originated call.

[0099] In an aspect, the at least one BTAS of the originating circle may convert the toll-free number from the first format to the second format when the originating call may be at least one voice-over LTE (VoLTE) originated call. In an aspect, the first format may be a Telephone (Tel) URI (Universal Resource Identifier) format. In an aspect, the second format may be a SIP URI format.

[00100] In an aspect, the at least one BTAS may modify the toll-free number to a direct inward dialing (DID) number. In an aspect, the at least one BTAS may terminate the originating call towards at least one BTAS of the originating circle (same circle) only. In an aspect, the at least one BTAS may serve as a termination leg for the incoming call.

[00101] In an aspect, the rest of the incoming calls may flow similarly to the call forward scenario in the communication network. [00102] Thus, the present invention may provide the system (108) to rollout a toll-free number in the communication network in which the at least one BTAS may configure any new toll-free number at BTAS servers. The present disclosure may allow calls originating from any circle for a toll-free number to be served by the at least one BTAS of the same circle. Thus, the present invention may provide an efficient session initiation protocol (SIP) signaling routing of the toll-free number. Further, services of any new toll-free number may be easily and seamlessly rolled out globally.

[00103] Referring to FIG. 2, another exemplary system architecture (200) to rollout the toll-free number in the network (106), in accordance with an embodiment of the present disclosure is shown.

[00104] A Session initiation protocol (SIP) enables voice and video communication over the internet. The SIP handles the signalling and control of multimedia sessions. The SIP uses a text-based message format that can be extended and customized to suit different needs and scenarios. The SIP message includes a request line or a status line, followed by a set of headers and an optional message body. The request line or status line indicates a method, a universal resource identifier (URI), and a protocol version. The set of headers provides additional information about the sender, the receiver, the session, and the message. The message body can contain session description protocol (SDP) or other data types. The SDP defines the media formats, codecs, and parameters for each session.

[00105] For example, when a call is initiated by a user A (calling party) through a user equipment, a user equipment of a user B (receiving party) receives an INVITE message (not shown in FIG. 2). After receiving the invite message, the user equipment of the user B rings. In the SIP, a response titled as “180 Ringing” is configured to notify the calling party that the call has been initiated and assure the calling party that the receiving party has received the INVITE message. A multiple SIP messages are exchanged between the user A and the user B during a signalling plane, and a data plane. During the signalling plane, once all the messages are successfully transferred from the user A to the user B party, then a call is established between the user A to the user B. As these multiple SIP messages are being exchanged in the signalling plane, it is the responsibility of the at least one BTAS (124) to pass on successfully all the messages from the user A to the user B.

[00106] All the SIP messages are independent and when the invite message is received by the at least one BTAS (124), and the at least one BTAS (124) executes a service logic as per user management module (UMM) configured logic. The UMM manages user accounts, permissions, and access to services and resources within the network. The at least one BTAS (124) will send the INVITE message to the user B. Post the processing of the INVITE message, the at least one BTAS (124) receives other messages from other users intended to connect over the network. In an example, the at least one BTAS (124) may receive a plurality of messages in parallel.

[00107] The diameter interface connects network elements to enable essential service provider network functions such as authentication, online and offline billing, and policy and charging. A REST interface allows the different network elements to exchange information securely over the network.

[00108] As shown in FIG. 2, the system architecture (200) includes a user equipment UE (202) (analogous to the UE (104)), and an IMS network (204). The system architecture (200) may include a number of components (modules) such as an operational support system (OSS)/ business support system (BSS) (218), an element management system (EMS) (216), a media resource function (MRF) (214), a caller ring back tones (CRBT) (212) service, a diameter routing agent (DRA) (210), an online charging system (OCS) (208), a mobile number portability (MNP) module (206), a provisioning server (224) (analogous to UE (104)), and a Business telephony application server (BTAS) (222) (analogous to at least one BTAS (124)).

[00109] The UE (202) is connected to the IMS network (204) via the Session Initiation Protocol (SIP) to manage and control multimedia communication sessions. The SIP enables voice and video communication over the Internet. The SIP handles the signaling and control of multimedia sessions. The SIP uses a text-based message format that can be extended and customized to suit different needs and scenarios. The SIP message includes a request line or a status line, followed by a set of headers and an optional message body. The request line or status line indicates a method, a universal resource identifier (URI), and a version of the protocol. The set of headers provides additional information about the sender, the receiver, the session, and the message. The message body can contain session description protocol (SDP) or other data types. The SDP defines the media formats, codecs, and parameters for each session.

[00110] For example, when a call is initiated by a user A (calling party) through a user equipment, a user equipment of a user B (receiving party) receives an INVITE message (not shown in FIG. 2). After receiving the invite message, the user equipment of the user B rings. In SIP, a response titled as "180 Ringing" is configured to notify the calling party that the call has been initiated and assure the calling party that the receiving party has received the INVITE message. Multiple SIP messages are exchanged between the user A and the user B during a signaling plane, and during a data plane. During the signaling plane, once all the messages are successfully transferred from the user A to the user B party, then a call is established between the user A to the user B. As these multiple SIP messages are being exchanged in the signaling plane, it is the responsibility of the BTAS (222) to pass on successfully all the messages from the user A to the user B.

[00111] All the SIP messages are independent and when the invite message is received by the BTAS (222), and the BTAS (222) executes a service logic as per user management module (UMM) configured logic. The UMM is a tool used to manage user accounts, permissions, and access to services and resources within the network. The BTAS (222) may send the INVITE message to the user B. Post the processing of the INVITE message, the BTAS (222) receives other messages from other users intended to connect over the network. In an example, the BTAS (222) receives a plurality of messages in parallel. In an aspect, the BTAS (222) is a multi-threaded application [00112] The OSS (218) is configured to manage network operations and maintenance. The BSS (218) is configured to handle billing, customer management, and revenue assurance. The OSS/BSS (218) is essential for telecom service providers to manage their operations, deliver services to customers, and generate revenue. In an aspect, the provisioning server (224) may be connected to the OSS/BSS (218) via a load balancer (220). In an example, the load balancer (220) is configured to offer gateway and management solutions. In an embodiment the load balancer (220) may be a F5 module. In an example, the load balancer (220) is connected to the OSS/BSS (218) via RESTful APIs (REST).

[00113] The EMS (216) includes various systems and applications for managing the plurality of network elements (NE) on a network element-management layer (NEL). The EMS (216) is configured to manage one or more of a specific type of communications network element. The EMS (216) manages the functions and capabilities within each NE but does not manage the traffic between different NEs in the network (106). The EMS (216) provides a foundation to implement operations support system (OSS) architectures that enable service providers to meet customer needs for rapid deployment of new services, as well as to meet stringent quality of service (QoS) requirements. The EMS (216) is connected to the BTAS (222), provisioning server (224) and the OSS/BSS (218) via RESTful APIs (Rest).

[00114] The MRF (214) is configured to provide virtualization of networks to its network providers. The MRF (214) provides media services like announcements, tones, and conferencing for VoLTE, Wi-Fi calling, and fixed VoIP solutions. The MRF (214) is connected to the BTAS (222) via the SIP and Media Server Markup Language (MSML) to facilitate the control and management of media resources during call sessions.

[00115] The CRBT (212) service is configured to replace a standard audio clip with a clip selected by the user. Thus, CRBT (212) is a customizable ringtone or music that a subscriber may subscribe to replace the default ring back tone when the subscriber is called. The CRBT (212) service can be supported by different mobile network infrastructures including the circuit- switched GSM networks and IP multimedia networks such as IMS. By utilizing the CRBT (212) service, telecom companies can improve customer satisfaction and loyalty. The CRBT (212) and the BTAS (222) are connected via the SIP to manage and control the delivery of ring-back tones to callers during call setup.

[00116] The DRA (210) is a functional element in a 3G or 4G (such as LTE) network that provides real-time routing capabilities to ensure that messages are routed among the correct elements in the network (106). The DRA (210) and the Telephony Application Server (TAS) are connected via a Diameter protocol to manage and route authentication, authorization, and accounting (AAA) messages for telephony services.

[00117] The OCS (208) is a centralized platform that allows a service provider to charge a user for services in real-time. The OCS (208) handles the subscriber's account balance, rating, charging transaction control and correlation. With the OCS (208), the telecom operator ensures that credit limits are enforced, and resources are authorized on a per transaction basis. The OCS (208) and the DRA (210) are connected via the diameter protocol to facilitate the exchange of real-time charging information and manage accounting messages for telecommunications services.

[00118] The MNP module (206) is configured to allow the user (102) to switch their mobile phone number between different mobile network providers while retaining their existing number. The MNP module (206) allows customers to change their provider without having to change their phone number, making it easier to switch to a better plan or service. The MNP module (206) and the BTAS (222) are connected via the SIP to manage and route calls effectively, ensuring proper handling of calls to ported numbers within the network (106).

[00119] The IMS core includes two types of network elements: SIP infrastructure (SIP server) and a plurality of media gateways. The SIP server is configured to manage voice and video calls over the internet. The SIP server directs calls to the UE (102), manages call routing and authentication, and provides features like call holding, forwarding, and recording.

[00120] The media gateway is an interconnect point to circuit-switched networks and other IMS network (204). The media gateway also handles the transcoding of the media plane. The media gateway is configured to carry voice traffic and hand it over to other networks. These Media Gateways handle the interworking of Voice traffic between IMS and PSTN Networks. The media gateway is an entry point to the IMS Network (204) for any user calling from a traditional 2G or 3G or fix line network.

[00121] FIG. 3 illustrates an exemplary flow diagram of a method (300) to rollout the toll-free number in the network (106), in accordance with an embodiment of the present disclosure.

[00122] At step (302) of the method (300), a request URI is set to the toll-free number. An INVITE message, which includes an SDP (Session Description Protocol) offer, is sent from the UE (104) to the Proxy Call Session Control Function (P-CSCF) (301) and subsequently to a Serving Call Session Control Function (S-CSCF) (303). This INVITE initiates the process of setting up at least one call.

[00123] At step (304) of the method (300), a “100 Trying” response is sent from the S-CSCF (303) to the UE (104). This response indicates that the INVITE (SDP offer) has been received and is being processed. At this point, the Initial Filter Criteria (IFC) are applied, which may be based on the short code or the calling party number to determine further call handling instructions. In an embodiment, the response code “100 Trying” means that the next-hop server has received a request and is taking some action on it, such as consulting a database. This response is a provisional response that stops a user agent client (UAC) from retransmitting the INVITE (SDP offer).

[00124] At step (306) of the method (300), the S-CSCF (303) forwards the INVITE (SDP) to at least one BTAS (124). This step is crucial for routing the call through the network towards the toll-free number. [00125] At step (308) of the method (300), upon receiving the INVITE, the at least one BTAS (124) sends the “100 Trying” response back to the S-CSCF (303). This response confirms that the at least one BTAS (124) is handling the call request. An algorithm is then applied to manage the call distribution. In this case, a round-robin algorithm is used to extract a best-match priority number list and make calls to them one by one.

[00126] At step (310) of the method (300), the at least one BTAS (124) sends an “INVITE MRF” message to a Media Resource Function (MRF) (214). The MRF (214) is typically involved in handling media-related tasks, such as playing announcements or managing media streams.

[00127] At step (312) of the method (300), the MRF (214) sends the “100 Trying” response back to the at least one BTAS (124), indicating that the “INVITE MRF” has been received and is in progress.

[00128] At step (314) of the method (300), following the successful setup of media resources, the MRF (214) sends a “200 OK (SDP)” response with SDP back to the at least one BTAS (124). This indicates that the call setup process has been completed on the MRF (214). In an embodiment, in the response code “200 OK (SDP)” in indicates that the request was successful.

[00129] At step (316) of the method (300), a “183 -reliable” message with reliable provisional response is sent from the at least one BTAS (124) to the S-CSCF (303). This message informs the S-CSCF (303) that the session setup is in progress and provides early media, such as a ring-back tone or announcements. In an embodiment, the “183-reliable” message is sent when a call progresses, but it's unclear if the user has been alerted.

[00130] At step (318) of the method (300), the S-CSCF (303) forwards the “ 183-reliable” message to the UE (104), ensuring that the user (102) is informed of the call progress. [00131] At step (320) of the method (300), a “PRACK (Provisional Acknowledgement)” message is sent from the UE (104) to the S-CSCF (303), acknowledging the receipt of the provisional response.

[00132] At step (322), the “PRACK” is then forwarded from the S-CSCF (303) to the at least one BTAS (124), ensuring reliable delivery of the provisional response.

[00133] At step (324) of the method (300), an “ACK (Acknowledgement)” message is sent from the at least one BTAS (124) to the MRF (214).

[00134] At step (326) of the method (300), the at least one BTAS (124) sends a “200 OK PRACK” response to the S-CSCF (303), indicating successful receipt and processing of the PRACK message.

[00135] At step (328) of the method (300), the S-CSCF (303) sends a “200 OK PRACK” response back to the UE (104), completing the provisional response acknowledgement process. In an embodiment, an announcement is played to a calling party until the user (102) connects with the calling party.

[00136] At step (330) of the method (300), the at least one BTAS (124) sends another “INVITE C (SDP)” message, this time to the S-CSCF (303), for setting up a media announcement to the calling party.

[00137] At step (332) of the method (300), the S-CSCF (303) sends a “100 Trying” response to the at least one BTAS (124), indicating that the “INVITE C (SDP)” for the media announcement is being processed. The IFC based on request URI is applied and thus outing and handling SIP messages and media based on the specific URI included in the request.

[00138] At step (334) of the method (300), the S-CSCF (303) then sends the “INVITE C (SDP)” message to a Telephony Application Server (TAS) (305). This “INVITE C (SDP)” is based on the request URI and is used for further call processing and routing decisions. [00139] At step (336) of the method (300), the TAS (305) sends a “100 Trying” response back to the S-CSCF (303), confirming the receipt and processing of the INVITE.

[00140] At step (338) of the method (300), another “INVITE C (SDP)” message is sent from the TAS (305) to the S-CSCF (303). This could be for additional call handling or routing purposes.

[00141] At step (340) of the method (300), the S-CSCF (303) responds with a “100 Trying” message back to the TAS (305), acknowledging the receipt of the “INVITE C (SDP).”

[00142] At step (342) of the method (300), the S-CSCF (303) sends the “INVITE

C (SDP)” message to an Interconnection Border Control Function (IBCF) (307). The IBCF (307) manages border control and interconnects between different networks or domains.

[00143] At step (344) of the method (300), the IBCF (307) sends a “100 Trying” response back to the S-CSCF (303), indicating that the “INVITE C (SDP)” is being processed and that the IBCF (307) is managing the call's interconnection.

[00144] FIG. 4 illustrates another exemplary flow diagram of the method (400) to rollout the toll-free number in the network (106), in accordance with an embodiment of the present disclosure.

[00145] At step (402) of the method (400), a “183 SDP Ans-C Party” request is sent from the IBCF (307) to the S-CSCF (303) via the TAS (305), MRF (214), and at least one BTAS (124). In an embodiment, the “183 SDP Ans-C Party” is the SIP response message that indicates that the called party has answered the incoming call and is sending their Session Description Protocol (SDP) information. The “183”: This is the status code indicating a provisional response and the “SDP Ans-C Party”: This phrase specifies that the called party is sending their SDP information. [00146] At step (404) of the method (400), a “183 SDP Ans-C Party” response is sent from the S-CSCF (303) to the TAS (305), passing through the at least one BTAS (124) and the MRF (214). The “183 SDP Ans-C Party” response indicates that the call is in progress, and the media negotiation is continuing towards the calling party.

[00147] At step (406) of the method (400), a “183 SDP Ans-C Party” request is again sent, this time from the TAS (305) to the S-CSCF (303), routing through the MRF (214) and the at least one BTAS (124).

[00148] At step (408) of the method (400), a “183 SDP” response is sent from the S-CSCF (303) to the at least one BTAS (124). This response confirms the continuation of the session setup, ensuring that both parties involved in the call have the necessary information to proceed. In an embodiment, the “ 183 SDP” is part of the sequence of messages used to establish a session. The “183 SDP” is a second message in the sequence.

[00149] At step (410) of the method (400), a “PRACK (Provisional Acknowledgement)” request is sent from the at least one BTAS (124) to the S-CSCF (303). The PRACK message is used to acknowledge the receipt of provisional responses, ensuring that these intermediate steps are reliably communicated.

[00150] At step (412) of the method (400), a “PRACK” response is sent from the S-CSCF (303) to the TAS (305), passing through the at least one BTAS (124) and the MRF (214). This response confirms that the PRACK has been received and acknowledged, allowing the call setup process to continue.

[00151] At step (414) of the method (400), a “PRACK” request is sent from the TAS (305) to the S-CSCF (303) via the MRF (214) and the at least one BTAS (124). This step continues the process of acknowledging provisional responses and confirms that the signaling messages are being reliably transmitted. [00152] At step (416) of the method (400), a “PRACK” response is sent from the S-CSCF (303) to the IBCF (307) via the at least one BTAS (124), the MRF (214), and the TAS (305).

[00153] At step (418) of the method (400), a “200 OK (PRACK)” request is sent from the IBCF (307) to the S-CSCF (303) via the TAS (305), the MRF (214), and the at least one BTAS (124). The “200 OK (PRACK)” message signifies the successful receipt of the PRACK message, indicating that the provisional acknowledgment process is complete. In an embodiment, the “200 OK (PRACK)” response is a message that indicates a successful request.

[00154] At step (420) of the method (400), a “200 OK (PRACK)” response is sent from the S-CSCF (303) to the TAS (305), passing through the at least one BTAS (124) and the MRF (214).

[00155] At step (422) of the method (400), a “200 OK (PRACK)” request is sent from the TAS (305) to the S-CSCF (303).

[00156] At step (424) of the method (400), a “200 OK (PRACK)” response is sent from the S-CSCF (303) to the at least one BTAS (124). This final acknowledgment within the PRACK sequence confirms that the provisional message handling has been completed.

[00157] At step (426) of the method (400), an “UPDATE W/O RH (Media Server SDP)” response is sent from the from the IBCF (307) to the S-CSCF (303). This update involves media server information and is part of the ongoing media negotiation. In an embodiment, the “UPDATE W/O RH (Media Server SDP)” response is used to modify the session description without requesting a re-negotiation of the media stream. This is typically used when changes in the media parameters do not require a new negotiation between the parties involved in the call.

[00158] At step (428) of the method (400), an “UPDATE W/O RH (Media Server SDP)” request is sent from the S-CSCF (303) to the TAS (305) via the at least one BTAS (124) and the MRF (214). This request further modifies or updates the session parameters related to media handling, ensuring that the call is configured correctly.

[00159] At step (430) of the method (400), an “UPDATE W/O RH (Media Server SDP)” response is sent from the TAS (305) to the S-CSCF (303) via the MRF (214) and the at least one BTAS (124).

[00160] At step (432) of the method (400), an “UPDATE W/O RH (Media Server SDP)” response is sent from the S-CSCF (303) to the at least one BTAS (124). In an aspect, send “200 OK” of update with port to set 0 for each media line in SDP.

[00161] At step (434) of the method (400), a “200 OK UPDATE” request is sent from the at least one BTAS (124) to the S-CSCF (303). This message indicates that the session update has been successfully processed, and the updated media parameters are accepted. In an embodiment, the “200 OK (UPDATE)” response allows the user (102) to update session parameters, such as the codecs and media streams, without affecting the dialog’s state.

[00162] At step (436) of the method (400), a “200 OK UPDATE” response is sent from the S-CSCF (303) to the TAS (305) via the at least one BTAS (124) and the MRF (214).

[00163] At step (438) of the method (400), a “200 OK UPDATE” request is sent from the TAS (305) to the S-CSCF (303) via the MRF (214) and the at least one BTAS (124).

[00164] At step (440) of the method (400), a “200 OK UPDATE” response is sent from the S-CSCF (303) to the IBCF (307) via the at least one BTAS (124), the MRF (214), and the TAS (305).

[00165] At step (442) of the method (400), a “200 OK INVITE without SDP” request is sent from the IBCF (307) to the S-CSCF (303) via the TAS (305), the MRF (214), and the at least one BTAS (124). The “200 OK INVITE without SDP” signifies the continuation of the call setup process, now focusing on signaling without specifying media parameters. In an embodiment, the “200 OK INVITE without SDP” is a message that indicates a successful response to an INVITE request, but without including a Session Description Protocol (SDP) offer. This typically occurs when the caller is not sending any media (e.g., in a pure signaling -based call or when media is negotiated later).

[00166] At step (444) of the method (400), a “200 OK INVITE without SDP” response is sent from the S-CSCF (303) to the TAS (305) via the at least one BTAS (124) and the MRF (214). The “200 OK INVITE without SDP” response indicates the successful processing of the INVITE request, maintaining the progression of the call setup.

[00167] At step (446) of the method (400), a “200 OK INVITE without SDP” request is sent from the TAS (305) to the S-CSCF (303) via the MRF (214) and the at least one BTAS (124).

[00168] At step (448) of the method (400), a “200 OK INVITE without SDP” response is sent from the S-CSCF (303) to the at least one BTAS (124). This final acknowledgment in the INVITE sequence confirms that the signaling setup has been successfully handled.

[00169] In an aspect, announcement (ANNC) is stopped on the at least one BTAS (124). “Stop ANNC” refers to a command or action taken within an IP Multimedia Subsystem (IMS) network to terminate the ANNC that is currently being played to a caller. This can occur in various scenarios, such as when a caller is placed on hold or when an automated message is being delivered.

[00170] At step (450) of the method (400), a “BYE” response is sent from the BTAS to the MRF (214). In an embodiment, the “BYE” is used to end an established call. For example, if one user calls another and either user hangs up, the call is terminated using the “BYE”.

[00171] In an aspect, recent SDP received from C party is added on the at least one BTAS (124).

[00172] At step (452) of the method (400), a “200 OK BYE” request is received from the MRF (214) to the at least one BTAS (124). This response acknowledges the receipt of the BYE message, confirming that the call termination request has been accepted and processed. In an embodiment, the “200 OK BYE response” is forwarded to the preceding or succeeding node.

[00173] At step (454) of the method (400), a “200 OK INVITE with SDP” request is sent from the at least one BTAS (124) to the S-CSCF (303). This message indicates that a new session with specific media parameters is being established, restarting the process for a new call setup. In an embodiment, the “200 OK INVITE with SDP” is a response message that indicates a successful response to an INVITE request and includes the SDP offer. This typically occurs when the caller/user sends media and wants to establish a media stream with the called party.

[00174] At step (456) of the method (400), a “200 OK INVITE with SDP” request is sent from the S-CSCF (303) to the UE (104). The “200 OK INVITE with SDP” informs the User Equipment of the successful establishment of the call session, including media parameters for the communication.

[00175] At step (458) of the method (400), an “ACK” is sent from the UE (104) to the S-CSCF (303). This acknowledgment confirms that the UE (104) has received the “200 OK INVITE with SDP” message and is ready to communicate. In an embodiment, the “ACK” is a request that confirms that an entity has received a final response to the INVITE request. [00176] At step (460) of the method (400), the “ACK” is sent from the S-CSCF (303) to the at least one BTAS (124). This step ensures that the acknowledgment of the session establishment is communicated back through the network (106).

[00177] At step (462) of the method (400), the “ACK” is sent from the at least one BTAS (124) to the S-CSCF (303). This message continues the acknowledgment sequence, confirming that all entities involved are synchronized in the session setup.

[00178] At step (464) of the method (400), the “ACK” is sent from the S-CSCF (303) to the TAS (305). This step further propagates the acknowledgment to ensure that the session establishment is confirmed across all relevant network components.

[00179] At step (466) of the method (400), the “ACK” is sent from the TAS (305) to the S-CSCF (303). This acknowledgment ensures that the TAS (305) has confirmed the session setup and is ready for communication.

[00180] At step (468) of the method (400), the “ACK” is sent from the S-CSCF (303) to the IBCF (307). This acknowledgment confirms that the session setup is complete, and all necessary entities are ready for communication.

[00181] In an aspect a Real-time Transport Protocol (RTP) is applied between the UE (104) and the IBCF (307).

[00182] At step (470) of the method (400), a “486 Busy Here” request is sent from the IBCF (307) to the S-CSCF (303). In an embodiment, the SIP error code “486 Busy Here” is returned when the called party is busy or when a redirect or proxy server does not have a valid forwarding location for the user.

[00183] At step (472) of the method (400), the “486 Busy Here” response is sent from the S-CSCF (303) to the TAS (305).

[00184] At step (474) of the method (400), the “486 Busy Here” request is sent from the TAS (305) to the S-CSCF (303). The request continues to propagate the busy signal, ensuring that all involved entities are informed of the call status. [00185] At step (476) of the method (400), a “486 Busy” response is sent from the S-CSCF (303) to the at least one BTAS (124). The acknowledgment of the busy status ensures that the call setup process is halted, and the originating party is informed of the call’s unavailability.

[00186] At step (478) of the method (400), an “ACK” request is sent from the at least one BTAS (124) to the S-CSCF (303). The acknowledgment confirms the receipt of the busy signal and completes the call termination process.

[00187] At step (480) of the method (400), an “ACK” response is sent from the S-CSCF (303) to the TAS (305) via the at least one BTAS (124) and the MRF (214). This response acknowledges the termination of the call setup and confirms that all entities are aware of the status of the call.

[00188] At step (482) of the method (400), the “ACK” request is sent from the TAS (305) to the S-CSCF (303). This step ensures that the final acknowledgment of the call termination is communicated through the network.

[00189] At step (484) of the method (400), the “ACK” response is sent from the S-CSCF (303) to the IBCF (307) via the at least one BTAS (124), the MRF (214), and the TAS (305). This acknowledgment confirms that all network components have successfully terminated the call setup process.

[00190] In an aspect, the at least one BTAS (124) will attempt to connect to another user until the UE (104) is successfully connected to the final destination. This step indicates the capability of the system (108) to handle failed call attempts and retry connecting until a successful call setup is achieved.

[00191] Referring to FIGS. 3 and 4, a toll-free number call may be received at least one terminating BTAS of the same circle. In an aspect, the at least one BTAS (124) may apply a call logic based on the toll-free number configured data to complete the toll-free number call. In an aspect, the at least one BTAS (124) for the toll-free number call may connect the UE (104) with the MRF (214), to play/generate a configured announcement to a user of the UE (104). In an aspect, the at least one BTAS (124) may try to connect the toll-free number call with any available agents that may be configured behind the toll-free number call. In an aspect, when the toll-free number call is connected with any available agent, an agent session description protocol (SDP) may be negotiated towards an A-party (calling user/incoming call) and the toll-free number (TFN) call between the A-party and the agent may get connected. In an aspect, the MRF (214) announcement may be stopped at this moment. In an aspect, as per the configured logic at the at least one BTAS (124), the at least one BTAS (124) may try to connect the toll-free number call with other available agents that may be configured behind the toll-free number call in case of any of already available connected agent may get disconnected from the toll-free number call or may be not available.

[00192] FIG. 5 illustrates a computer system (500) in which or with which the embodiments of the present disclosure may be implemented.

[00193] As shown in FIG. 5, the computer system (500) may include an external storage device (510), a bus (520), a main memory (530), a read-only memory (540), a mass storage device (550), communication port(s) (560), and a processor (570). A person skilled in the art will appreciate that the computer system may include more than one processor and communication ports. The processor (570) may include various modules associated with embodiments of the present disclosure. The communication port(s) (560) may be any of an RS-232 port for use with a modem-based dialup connection, a 10/100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication port(s) (560) may be chosen depending on a network, such a Focal Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system connects.

[00194] The main memory (530) may be random access memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (540) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input/Output System (BIOS) instructions for the processor (570). The mass storage device (550) may be any current or future mass storage solution, which can be used to store information and/or instructions. Exemplary mass storage device (550) includes, but is not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and/or Firewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks.

[00195] The bus (520) communicatively couples the processor (570) with the other memory, storage, and communication blocks. The bus (520) may be, e.g., a Peripheral Component Interconnect / Peripheral Component Interconnect Extended bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (570) to the computer system.

[00196] Optionally, operator and administrative interfaces, e.g., a display, keyboard, joystick, and a cursor control device, may also be coupled to the bus (520) to support direct operator interaction with the computer system. Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) (560). The components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system limit the scope of the present disclosure.

[00197] FIG. 6 illustrates another exemplary flow diagram of the method (600) to rollout the toll-free number in the network (106), in accordance with an embodiment of the present disclosure.

[00198] At step (602), the method (600) includes receiving (602), by a receiving unit ( 118), at least one call associated with a toll-free number from an originating circle. The receiving unit (118) captures the at least one call request and identifying it as being tied to a toll-free number. This identification is crucial for ensuring that the subsequent processes are triggered in the correct way, allowing the at least one call to be handled according to the toll-free number configuration and routing rules.

[00199] At step (604) of the method (600) includes providing, by a processing unit (116), a configuration of the at least one toll-free number to at least one Business Telephony Application Server (BTAS) (124) of the originating circle. Once the at least one call is received, the method (600) proceeds by configuring the toll-free number. This configuration process is managed by the processing unit (116), which works in conjunction with a database (120) containing configuration data. The configuration involves setting up the toll-free number with specific rules, such as how the at least one call should be routed, announcements that should play, or how to assign the at least one call to a particular agent. The at least one BTAS (124) is the key component in this step, and it receives the configuration data. The configuration data may include details such as the number format, routing rules, and any specific service parameters associated with the toll-free number. The BTAS (124) is responsible for managing voice services and telephony applications, and the BTAS (124) ensures that the toll- free number is properly set up for further processing within the originating circle. This step guarantees that the at least one call can be handled according to its designated parameters, maintaining a seamless experience for the caller.

[00200] At step (606), the method (600) includes converting, by the processing unit (116), the at least one toll-free number from a first format to a second format. The first format, typically a Telephone (Tel) URI (Universal Resource Identifier) format, is converted to a second format, such as a Session Initiation Protocol (SIP) URI format. The conversion of the toll-free number from the Tel URI format to the SIP URI format enables the at least one toll-free number to be routed through IP-based communication networks. The processing unit (116) performs this conversion, ensuring that the toll- free number is compatible with the SIP -based infrastructure used by services like VoLTE (Voice over LTE) or other IP networks. This step is vital for ensuring that the at least one toll-free number can be properly handled across different types of networks, from traditional telephony to modern IP -based networks. The conversion can be performed either by the at least one BTAS (124) or by at least one Media Gateway Control Function (MGCF) of the originating circle, depending on the network architecture and the location where the call is being processed. This step ensures that the toll-free number is in the correct format for further processing and routing within the network (106).

[00201] In an embodiment, the at least one BTAS (124) modifies the converted toll-free number to a Direct Inward Dialing (DID) number. After the toll-free number is converted to the second format, it is further processed by the at least one BTAS (124) to map it to the DID number. This mapping is essential for directing the at least one call to the correct destination within the network (106). The DID number is typically used within organizations to route calls directly to specific internal lines, bypassing the main switchboard. This step ensures that the at least one call reaches its intended recipient efficiently.

[00202] At step (608), the method (600) includes terminating, by the processing unit (116), the at least one call comprising the converted toll-free number towards the at least one BTAS (124) of the originating circle. In this step, the method (600) concludes with the termination of the at least one call. After the toll-free number has been converted to the second format, the processing unit (116) ensures that the at least one call is routed and terminated the at least one BTAS (124) of the originating circle. The at least one call is sent to the at least one BTAS (124), which handles its final stages, such as connecting it to a local network, an agent, or another telephony service. This termination process ensures that the at least one call reaches its intended destination smoothly. The at least one BTAS (124) is also responsible for managing the final call setup and ensuring that the toll-free number behaves according to its defined configuration, whether the at least one call is routed on-net, off-net, or via a VoLTE connection. This step is crucial for ensuring that the at least one call is successfully connected, and that the caller is able to reach the toll-free number they dialed. [00203] In an exemplary embodiment, the present disclosure relates to a user equipment (UE) communicatively coupled with a network. The coupling includes steps of receiving at least one call associated with a toll-free number from an originating circle by a receiving unit, providing a configuration of the at least one toll-free number to at least one Business Telephony Application Server (BTAS) of the originating circle by a processing unit, converting the at least one toll-free number from a first format to a second format by the processing unit and terminating the at least one call comprising the converted toll-free number towards the at least one BTAS of the originating circle by the processing unit.

[00204] In another exemplary embodiment, the present disclosure relates to a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method to rollout a toll-free number in a network. The method includes receiving at least one call associated with a toll-free number from an originating circle by a receiving unit, providing a configuration of the at least one toll- free number to at least one Business Telephony Application Server (BTAS) of the originating circle by a processing unit, converting the at least one toll-free number from a first format to a second format by the processing unit and terminating the at least one call comprising the converted toll-free number towards the at least one BTAS of the originating circle by the processing unit.

[00205] The present disclosure provides a technical advancement in the management of toll-free numbers within communication networks. This advancement addresses the limitations of existing solutions by using a comprehensive SIP call flow to efficiently handle toll-free number calls. The present disclosure involves converting toll-free numbers from the Tel URI to the SIP URI format, using algorithm-based load balancing, and incorporating acknowledgment and update messages for reliable call setup and termination. These inventive aspects of the present disclosure significantly improve the performance, reliability, and efficiency of toll-free call management, optimizing network resource utilization and enhancing overall user experience. [00206] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.

TECHNICAL ADVANCEMENTS

[00207] As is evident from the above, the present disclosure provides a technically advanced solution by providing a system and a method configured to:

• enable efficient rollout a toll-free number in a communication network.

• optimize network resources, reducing the need for additional hardware or software deployment.

• minimize the need for complex cross-circle routing, reducing operational costs and resource consumption by handling calls within the same originating circle.

• ensure faster call routing and reduce latency, thereby enhancing the overall quality of toll-free services.

Claims

CLAIMS We Claim:

1. A method (600) to rollout a toll-free number in a network (106), the method (600) comprising: receiving (602), by a receiving unit (118), at least one call associated with a toll-free number from an originating circle; providing (604), by a processing unit (116), a configuration of the at least one toll-free number to at least one Business Telephony Application Server (BTAS) (124) of the originating circle; converting (606), by the processing unit (116), the at least one toll-free number from a first format to a second format; and terminating (608), by the processing unit (116), the at least one call comprising the converted toll-free number towards the at least one BTAS (124) of the originating circle.

2. The method (600) as claimed in claim 1 , wherein the first format is a Telephone (Tel) universal resource identifier (URI) format, and the second format is a session initiation protocol (SIP) URI format.

3. The method (600) as claimed in claim 1, wherein the at least one call includes at least one of an on-net call, a Voice over Long Term Evolution (VoLTE) call, and an off-net call.

4. The method (600) as claimed in claim 1 , wherein the conversion of the at least one toll-free number from the first format to the second format is performed either by the at least one BTAS (124) of the originating circle or at least one Media Gateway Control Function (MGCF) of the originating circle.

5. The method (600) as claimed in claim 1, wherein the at least one BTAS (124) modifies the at least one converted toll-free number to a Direct Inward Dialing (DID) number.

6. A system (108) to rollout a toll-free number in a network (106), the system (108) comprising: a receiving unit (118) configured to receive at least one call associated with a toll-free number from an originating circle; a memory (112); and a processing unit (116) coupled with the receiving unit (118) to receive the at least one call associated with the toll-free number from the originating circle and is further coupled with the memory (112) to execute a set of instructions stored in the memory (112), the processing unit (116) is configured to: provide a configuration of the at least one toll-free number to at least one Business Telephony Application Server (BTAS) (124) of the originating circle; convert the at least one toll-free number from a first format to a second format, terminate the at least one call comprising the converted toll-free number towards the at least one BTAS (124) of the originating circle.

7. The system (108) as claimed in claim 6, wherein the first format is a Telephone (Tel) universal resource identifier (URI) format, and the second format is a session initiation protocol (SIP) URI format.

8. The system (108) as claimed in claim 6, wherein the at least one call includes at least one of an on-net call, a Voice over Long Term Evolution (VoLTE) call, and an off-net call.

9. The system (108) as claimed in claim 6, wherein the conversion of the at least one toll-free number from the first format to the second format is performed either by the at least one BTAS (124) of the originating circle or at least one Media Gateway Control Function (MGCF) of the originating circle.

10. The system (108) as claimed in claim 6, wherein the at least one BTAS (124) modifies the at least one converted toll-free number to a Direct Inward Dialing (DID) number.

11. A user equipment (UE) (104) communicatively coupled to a network (106), the coupling comprises steps of: receiving, by the network (106), a connection request from the UE (104); sending, by the network (106), an acknowledgment of the connection request to the UE (104); and transmitting a plurality of signals in response to the connection request, wherein the UE (104) is configured to rollout a toll-free number in the network (106) by a method (600) as claimed in claim 1.

12. A computer program product comprising a non -transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method (600) to rollout a toll-free number in a network (106), the method (600) comprising: receiving (602), by a receiving unit (118), at least one call associated with a toll-free number from an originating circle; providing (604), by a processing unit (116), a configuration of the at least one toll-free number to at least one Business Telephony Application Server (BTAS) (124) of the originating circle; converting (606), by the processing unit (116), the at least one toll-free number from a first format to a second format; and terminating (608), by the processing unit (116), the at least one call comprising the converted toll-free number towards the at least one BTAS (124) of the originating circle.