WO2025008962A1 - Système et procédé de routage d'un appel international - Google Patents

Système et procédé de routage d'un appel international Download PDF

Info

Publication number
WO2025008962A1
WO2025008962A1 PCT/IN2024/050949 IN2024050949W WO2025008962A1 WO 2025008962 A1 WO2025008962 A1 WO 2025008962A1 IN 2024050949 W IN2024050949 W IN 2024050949W WO 2025008962 A1 WO2025008962 A1 WO 2025008962A1
Authority
WO
WIPO (PCT)
Prior art keywords
ild
call request
call
btas
international
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/IN2024/050949
Other languages
English (en)
Inventor
Aayush Bhatnagar
Birendra Bisht
Harbinder Singh
Sandeep Gupta
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Jio Platforms Ltd
Original Assignee
Jio Platforms Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Jio Platforms Ltd filed Critical Jio Platforms Ltd
Publication of WO2025008962A1 publication Critical patent/WO2025008962A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/4228—Systems providing special services or facilities to subscribers in networks
    • H04M3/42306—Number translation services, e.g. premium-rate, freephone or vanity number services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/006—Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP), including next generation networks with a packet-switched transport layer
    • H04M7/0075—Details of addressing, directories or routing tables
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q3/00—Selecting arrangements
    • H04Q3/64—Distributing or queueing
    • H04Q3/66—Traffic distributors

Definitions

  • the present invention generally relates to communication systems, and more particularly relates to managing call services provided on International Toll-Free Services (ITFS).
  • ITFS International Toll-Free Services
  • BTAS Business Telephony Application Server
  • ITFS International Toll-Free Services
  • a customer can dial an ITFS number for free, but the business subscribing to the ITFS service bears all the charges for the calls.
  • the toll-free subscriber's physical location can affect the functionality and cost of the service.
  • real-time update, creation, or deletion of ITFS service data can be complex due to the intricacies of the network.
  • real-time data reporting as requested by an admin of the enterprise can be challenging to implement.
  • One or more embodiments of the present disclosure provide a system and method for routing an international call.
  • a system for routing an international call includes an International Long Distance (ILD) carrier communicably coupled to an International Long Distance-Session Border Controller (ILD-SBC) and an International Long Distance-Media Gateway Control Function (ILD-MGCF).
  • the ILD carrier is configured to receive a call request initiated from a caller by dialing a designated number associated to an enterprise.
  • the ILD carrier is further configured to route the call request to the ILD-SBC if the call request received is inbound and route the call to the ILD-MGCF if the call request received is outbound.
  • the system further includes a Business Telephony Application Server (BTAS) communicably coupled to the ILD carrier, the ILD-SBC, the ILD-MGCF and the enterprise.
  • the BTAS is configured to receive the call request transmitted by the ILD- SBC and the ILD-MGCF depending on the inbound or the outbound origination of the call request via an interface.
  • the BTAS is configured to customize at least one parameter of a header associated with the call request.
  • the BTAS is configured to return the call request to one of the ILD-SBC and the ILD-MGCF including the customized headers via the interface.
  • the BTAS is configured to connect the international call between the enterprise and a relevant User Equipment (UE) through one of the ILD-SBC and the ILD-MGCF based on the at least one customized parameter of the header associated with the call request.
  • UE User Equipment
  • the BTAS is further configured to provide time -based routing, direct translation with priority routing, round robin routing, and load balancing routing.
  • the interface between the BTAS and one of, the ILD- SBC and the ILD-MGCF is a customized interface for routing the international call, thereby eliminating usage of IP Multimedia Core Network Subsystem (IMS).
  • IMS IP Multimedia Core Network Subsystem
  • a method for routing an international call includes the step of receiving by an International Long Distance (ILD) carrier a call request initiated from a caller by dialing a designated number associated to an enterprise.
  • ILD International Long Distance
  • jurisdiction of the caller includes at least one of international and domestic.
  • the designated number dialed by the caller includes at least one of, an International Toll-Free Services (ITFS) number and a Universal International Freephone Number (UIFN).
  • the call request includes at least one of, Session Initiation Protocol (SIP) INVITE requests.
  • SIP Session Initiation Protocol
  • the method includes the step of routing by the ILD carrier the call request to an International Long Distance-Session Border Controller (ILD-SBC) when the call request received is inbound and routing the call to an International Long Distance-Media Gateway Control Function (ILD-MGCF) when the call request received is outbound.
  • the method further includes the step of receiving by a Business Telephony Application Server (BTAS) the call request transmitted by one of the ILD-SBC and the ILD-MGCF depending on inbound or outbound origination of the call request via an interface.
  • BTAS Business Telephony Application Server
  • the method further includes the step of customizing by the BTAS at least one parameter of a header associated with the call request.
  • the at least one parameter customized includes at least one of, routing rules, end point numbers behind International Toll-Free Services (ITFS) number and announcement files.
  • the method further includes the step of returning by the BTAS the call request to one of the ILD-SBC and the ILD-MGCF including the customized headers via the interface.
  • the method further includes the step of connecting by the BTAS the international call between the enterprise and a relevant User Equipment (UE) through one of the ILD-SBC and the ILD-MGCF based on the at least one customized parameter of the header associated with the call request.
  • the relevant UE is related to the caller.
  • customizing at least one parameter of a header associated with the call request includes one of, updating, editing, adding, and deleting information from the call request.
  • the method further includes utilizing by the BTAS a via header from the call request to route the international call to the relevant UE through one of the respective ILD-SBC and the ILD-MGCF when a route header and a P-Served User header are not present in the call request, thereby ensuring routing the call in the absence of standard headers in the call request.
  • the method further includes dynamically customizing by the BTAS the at least one parameter based on to which relevant UE the call is required to be routed.
  • the method further includes customizing by the BTAS the at least one parameter based on an input received from an admin of the enterprise via the UE in order to route the call to the relevant UE.
  • the BTAS supports configuration of ITFS numbers in all the international dialing patterns and formats such as at least one of, ‘00’ and ‘+’.
  • the BTAS is configured to extract recipient details from the call request, thereby enabling termination of the call to the relevant recipient.
  • FIG. 1 is an exemplary block diagram of a communication system for routing an international call, according to one or more embodiments of the present disclosure
  • FIG. 2 is a block diagram of exemplary servers used for providing inbound and outbound calling services, according to one or more embodiments of the present disclosure
  • FIG. 3A is a block diagram of exemplary servers used for providing the outbound calling service, according to one or more embodiments of the present disclosure
  • FIG. 3B is a block diagram of exemplary servers used for providing the inbound calling service, according to one or more embodiments of the present disclosure
  • FIG. 4 illustrates a system architecture in accordance with the present embodiment, according to one or more embodiments of the present disclosure
  • FIG. 5 illustrates a block diagram of a system for managing an outbound call, according to one or more embodiments of the present invention
  • FIG. 6 illustrates a block diagram of a system for managing an inbound call, according to one or more embodiments of the present invention.
  • FIG. 7 shows a method flow diagram for routing an international call, according to one or more embodiments of the present invention.
  • FIG. 1 is an exemplary block diagram of a communication system 100 for routing an international call, according to one or more embodiments of the present disclosure.
  • the communication system 100 includes a User Equipment (UE) 112, a network 114, and a system 116.
  • the UE 112 aids a user to interact with the system 116 for transmitting a call request to an International Long Distance (ILD) carrier 330 (as shown in FIG. 3A) in response to a caller dialing a designated number associated to an enterprise 212 (as shown in FIG.2) via a user interface module.
  • ILD International Long Distance
  • the ILD carrier 330 refers to a service provider that offers long-distance communication services between countries or regions.
  • the ILD carrier 330 specializes in facilitating voice calls, data transmission, and other forms of communication across international borders.
  • the ILD carrier 330 typically has agreements with local carriers in different countries to establish connections and provide seamless communication services to their customers.
  • the terms “user”, “caller”, and “subscriber” are used interchangeably hereinafter.
  • the UE 112 is one of, but not limited to, any electrical, electronic, electromechanical or an equipment and a combination of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, general- purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device.
  • VR virtual reality
  • AR augmented reality
  • Each of the first UE 112a, the second UE 112b, and the third UE 112c may be a computer system which may include an external storage device, a bus, a main memory, a readonly memory, a mass storage device, communication port(s), and a processor.
  • the computer system may include more than one processor and communication ports.
  • the communication port(s) 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) may be chosen depending on a network, such a Local Area Network (LAN), a Wide Area Network (WAN), or any network to which the computer system connects.
  • LAN Local Area Network
  • WAN Wide Area Network
  • the network 114 includes, by way of example but not limitation, one or more of 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.
  • PSTN Public-Switched Telephone Network
  • the network 114 may include, but is not limited to, a Third Generation (3G), a Fourth Generation (4G), a Fifth Generation (5G), a Sixth Generation (6G), a New Radio (NR), a Narrow Band Internet of Things (NB-IoT), an Open Radio Access Network (O-RAN), and the like.
  • 3G Third Generation
  • 4G Fourth Generation
  • 5G Fifth Generation
  • 6G Sixth Generation
  • NR New Radio
  • NB-IoT Narrow Band Internet of Things
  • OF-RAN Open Radio Access Network
  • Each of the first UE 112a, the second UE 112b, and the third UE 112c is configured to be communicably coupled with the system 116 via the network 114.
  • the system 116 includes a plurality of servers.
  • the plurality of servers may include, but not limited to, a first server 102 and a second server 104.
  • the plurality of servers include, by way of example but not limitation, one or more of a standalone server, a server blade, a server rack, a bank of servers, a server farm, hardware supporting a part of a cloud service or system, a home server, hardware running a virtualized server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof.
  • the entity may include, but is not limited to, a vendor, a network operator, a company, an organization, a university, a lab facility, a business enterprise, a defense facility, or any other facility that provides content.
  • FIG. 2 is a block diagram of exemplary servers used for providing inbound and outbound calling services, according to one or more embodiments of the present disclosure.
  • the first server 102 includes a memory 202, one or more processors 204, and a Business Telephony Application Server (BTAS) 206.
  • BTAS Business Telephony Application Server
  • the first server 102 is configured to host the BTAS 206.
  • the BTAS 206 is designated to handling and managing telephony applications within a business environment. It plays a crucial role in providing advanced telephony features, services, and integration capabilities for organizations.
  • the BTAS 206 acts as a central hub for telephony-related applications, enabling businesses to streamline communication processes, enhance productivity, and improve customer interactions.
  • the BTAS 206 is configured to receive a call request from the UE 112 and an enterprise 212 transmitted by the network 114 depending on the inbound or the outbound origination of the call request via an interface.
  • the first server 102 includes the memory 202 and one or more processors 204.
  • the one or more processors (s) 204 coupled with the memory 202.
  • the memory may store instructions which when executed by the one or more processor (s) 204 may cause the system to perform offloading/onloading of broadcasting or multicasting content in network 114.
  • the first server 102 may include one or more processor (s) 204.
  • the one or more processor (s) 204 may be implemented as one or more microprocessors, microcomputers, microcontrollers, edge or fog microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that process data based on operational instructions.
  • the one or more processor (s) may be configured to fetch and execute computer-readable instructions stored in a memory of the system.
  • the memory 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 202 may comprise any non-transitory storage device including, for example, volatile memory such as Random-Access Memory (RAM), or nonvolatile memory such as Electrically Erasable Programmable Read-only Memory (EPROM), flash memory, and the like.
  • the first server 102 may include an interface(s).
  • the interface(s) may comprise a variety of interfaces, for example, interfaces for data input and output devices, referred to as input/output (I/O) devices, storage devices, and the like.
  • the interface(s) may facilitate communication for the system.
  • the interface(s) may also provide a communication pathway for one or more components of the system. Examples of such components include, but are not limited to, processing unit/engine(s) and a database.
  • the processing unit/engine(s) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s).
  • programming for the processing engine(s) may be processor executable instructions stored on a non-transitory machine -readable storage medium and the hardware for the processing engine(s) may comprise a processing resource (for example, one or more processor s), to execute such instructions.
  • the machine- readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine(s).
  • the first server 102 may include 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.
  • the processing engine(s) may be implemented by electronic circuitry.
  • a database may comprise data that may be either stored or generated as a result of functionalities implemented by any of the components of the processor or the processing engines.
  • the main memory may be random access memory (RAM), or any other dynamic storage device commonly known in the art.
  • the read-only memory may be any static storage device(s) including, 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.
  • the mass storage device may be any current or future mass storage solution, which may be used to store information and/or instructions.
  • the bus communicatively couples the processor with the other memory, storage, and communication blocks.
  • the bus can be, e.g.
  • PCI Peripheral Component Interconnect
  • PCI-X PCI Extended
  • SCSI Small Computer System Interface
  • USB universal serial bus
  • operator and administrative interfaces e.g. a display, a keyboard, and a cursor control device, may also be coupled to the bus to support direct operator interaction with the computer system.
  • Other operator and administrative interfaces may be provided through network connections connected through the communication port(s).
  • the second server 104 includes a memory 208, one or more processors 210, and the enterprise 212.
  • the second server 104 is configured to host the enterprise 212.
  • the enterprise 212 is configured to register with the BTAS 206 and is adapted to opt for services at the BTAS 206.
  • the services are at least one of, but not limited to, international calling services.
  • the BTAS 206 is configured to connect an international call between the enterprise 212 and a relevant User Equipment (UE) 112 through the network 114.
  • UE User Equipment
  • the second server 104 includes the memory 208, and the one or more processors 210.
  • Description with reference to working and operation of the memory 208 and the processor 210 as illustrated in the second server 104 is same or similar to the working and operation of the memory 202 and the processor 204 as illustrated in the first server 102 above.
  • similar description related to the working and operation of the memory 208 and the processor 210 as illustrated in the second server 104 has been omitted to avoid repetition.
  • the limited description provided for the memory 208 and the processor 210 in the second server 104 should not be construed as a limitation to the scope of the present embodiment with reference to the memory 202 and the processor 204 in the first server 102, but should be read with the description as provided for the memory 202 and the processor 204 in the first server 102 above.
  • FIGS. 3A and 3B are exemplary block diagrams of the first server 102 and the second server 104 used for providing inbound and outbound calling services, according to one or more embodiments of the present invention. More specifically, FIG. 3A is an exemplary illustration of the second server 104 for providing the outbound call from the enterprise 212 to a user, according to one or more embodiments of the present invention. Further, FIG. 3B is an exemplary illustration of the first server 102 for providing the inbound call from the user to the enterprise 212 and, according to one or more embodiments of the present invention.
  • the second server 104 is configured for providing the outbound call from the enterprise 212 to the user.
  • the second server 104 is configured to host the enterprise 212 thereon.
  • the enterprise 212 may be one of, but not limited to, an organization that has opted to avail one or more services to the user.
  • the one or more services are at least one of, but not limited to, international calling services.
  • the BTAS 206 in the first server 102 is configured for providing call routing capabilities from the enterprise 212 to the user.
  • the BTAS 206 may include one or more of a Private Branch Exchange (PBX), a Session Border Controller (SBC), and/or other telephony aspects.
  • PBX Private Branch Exchange
  • SBC Session Border Controller
  • the BTAS 206 includes multiple call routing algorithms such as a time-based routing, a direct translation with priority routing, a call redirect, an IVR-based routing, a round robin routing, a load balancing routing, an origin-based routing, and a uniform call distribution.
  • the caller from the enterprise 212 can connect to the user in international destinations free of cost without having to activate International Subscriber Dialing (ISD) facility.
  • the enterprise 212 may select the call routing algorithm which needs to be implemented in the BTAS 206 or across all BTASs 206. Accordingly, the BTAS 206 implements the specified call routing algorithm, allowing for dynamic and efficient handling, and forwarding of incoming calls to the appropriate agents or destinations.
  • the first server 102 for providing the inbound call from the user to the enterprise 212.
  • the International Toll-Free Service (ITFS) inbound enables single unique ITFS number in an international location from the user to the enterprise 212 situated in a domestic network, for example India, through the BTAS 206.
  • the BTAS 206 in the first server 102 is configured for providing the call routing capabilities to connect the call from the user to the enterprise 212.
  • the BTAS 206 in the first server 102 includes multiple call routing algorithms such as a time -based routing, a direct translation with priority routing, a call redirect, an IVR-based routing, a round robin routing, a load balancing routing, an origin-based routing, and a uniform call distribution.
  • the BTAS 206 implements the specified call routing algorithm, allowing for dynamic and efficient handling, and forwarding of incoming calls to the appropriate agents or destinations.
  • the system 116 as disclosed in the present disclosure is able to advantageously improve call completion rates, optimize resource utilization, and enhance overall efficiency of call routing in the BTAS 206.
  • the BTAS 206 is configured to utilize routing rules and policies to determine how to route the call from the UE 112.
  • the routing rules and the policies are predefined by at least one of plurality of service providers.
  • the routing rules include customizing at least one parameter of a header associated with the call request generated by the user for the call from the BTAS 206 to the enterprise 212.
  • the routing rules and the policies are configured to be stored in a data store 214.
  • the data store 214 may be a database or other data store associated with a software platform.
  • the routing rules can identify the enterprise 212 to route the call from the enterprise 212 to a relevant UE 112.
  • the user or admin of the enterprise 212 which places the call to the international user via the UE and is opted for placing international toll-free calls, which further connects to the BTAS 206, and the BTAS 206 routes the call to the international user based on the routing rules stored at the data store 214.
  • the BTAS 206 receives the call from the international user and routes the call from the BTAS 206 to the enterprise 212 based on the routing rules stored at the data store 214.
  • the data store 214 is one of, but is not limited to, one of a centralized database, a cloud-based database, a commercial database, an open-source database, a distributed database, an end-user database, a graphical database, a No-Structured Query Language (NoSQL) database, an object-oriented database, a personal database, an in-memory database, a document-based database, a time series database, a wide column database, a key value database, a search database, a cache databases, and so forth.
  • NoStructured Query Language (NoSQL) database No-Structured Query Language
  • object-oriented database a personal database
  • an in-memory database a document-based database
  • a time series database a time series database
  • a wide column database a key value database
  • search database a cache databases
  • the first UE 112a includes one or more primary processors 310 communicably coupled to the ILD carrier 330.
  • the one or more primary processors 310 are coupled with a memory 320 storing instructions which are executed by the one or more primary processors 310. Execution of the stored instructions by the one or more primary processors 310 enables the first UE 112a to transmit the call request to the ILD carrier 330 in response to the caller dialing the designated number associated to the enterprise 212 via the interface.
  • the execution of the stored instructions by the one or more primary processors 310 further enables the first UE 112a to transmit the call request from the user via the interface module to the network 114.
  • FIG. 4 illustrates a system 116 architecture in accordance to the present embodiment.
  • the system 116 is implemented as a Session initiation protocol (SIP) application server for enterprise/business solutions, which would be integrated with an IMS Core.
  • SIP Session initiation protocol
  • the system 116 enables a network-based telephony and a web communication from and to a client of a customer.
  • the system 116 provides services like SIP trunking and an IP Centrex service for business customers, which are integrated with an IMS core Network 114 and other application servers to provide a supplementary service like a CUG, a short code dialing and the conferencing etc.
  • the system 116 includes a (SIP) zone, a representational state transfer (REST) zone, and a diameter zone.
  • SIP zone enables the client of the customer, such as the customer A or B, to send and receive calls over the network 114 using SIP requests and responses.
  • the web zone integrates a telephony data with the application server to enable telephony -based traffic access to software services run by the application server.
  • the REST zone includes an Operations and Business Support Systems (OSS/BSS) 408, a load balancer 411 for handling call load balancing, an Evolved Packet System (EPS) 410, and an Element Management System (EMS) 404.
  • the system 116 interacts with a Media Resource Function (MRF) 414, a Caller Ring Back Tone (CRBT) 416, a Diameter Routing Agent (DRA) 418 is connected to an Online Charging System (OCS) 420 via a diameter interface, and a Mobile Number Portability (MNP) 422 using the SIP.
  • MRF Media Resource Function
  • CBT Caller Ring Back Tone
  • DDA Diameter Routing Agent
  • OCS Online Charging System
  • MNP Mobile Number Portability
  • the OSS/BSS 408 is the combination of Business and Operations Support Systems.
  • the load balancer 411 refers to efficiently receiving the call request transmitted by one of an ILD-SBC 604 (as shown in FIG.6) and an ILD-MGCF (as shown in FIG.5) depending on the inbound or the outbound origination of the call request via an interface.
  • the EPS 410 manages the transfer of data packets related to call requests between the UE 112 and the external packet data networks 114, such as the internet.
  • the EMS 404 refers to Element Management System which manages a network element such as the BTAS 206 in the network 114.
  • the MRF 414 is responsible for carrying out a variety of processing tasks on media streams associated with one or more services. These tasks may include coordination and distribution of voice traffic associated with a conference service, playing of announcements to the user, etc.
  • an Enterprise Provisioning Server (EPS) 410 is a centralized entity which interacts with all the BTAS 206 and has the intelligence to route provisioning request towards the designated BTAS 206.
  • the EPS 410 is configured for facilitating the enterprise 212 to provision the ITFS number at the BTAS 206 with all additional parameters required to render ITFS.
  • the parameters may include, but may not be limited to, routing algorithms, end point numbers behind ITFS number, announcement files, and the like.
  • the EPS 410 provides restful API for the user to receive data requests, such as create, update, and delete, and send the same to the BTAS 206 for data provisioning.
  • the DRA 418 provides a real-time routing capability to ensure that the service request initiated by the users are routed among the first server 102 and the second server 104.
  • the CRBT 416 platform is an advanced telecommunications service that allows users of the UE 112 to personalize the ring-back tone heard by a caller.
  • the OCS 420 is responsible for facilitating real-time interactions with users, ensuring that the users are charged accurately for the consumed one or more services.
  • the MNP 422 is a service that allows a cellphone or smartphone user to change telecom carrier and keep the same phone number.
  • the IMS 406 is a standardized architectural framework for delivering an IP multimedia communication service such as voice, video and text.
  • the present invention significantly improves the integration of the at least one of plurality of servers with the system 116 for various telephony services.
  • the invention enhances flexibility, load balancing, and service continuity. These advantages result in a more efficient and reliable telephony system, improves call completion rates, optimizes resource utilization, and enhances overall efficiency of call routing in the BTAS 206.
  • FIG. 5 illustrates a block diagram of a system 116 for managing the outbound call by the BTAS 206, according to one or more embodiments of the present invention.
  • the ILD carrier 330 is configured to receive the call request initiated from the caller by dialing the designated number associated to the enterprise 212 by using the interface module in the UE 112 through a terminating network 508.
  • the terminating network 508 is JIO network.
  • the user interface module may include a messaging module, a voicemail module, and the like.
  • jurisdiction of the caller includes at least one of, international and domestic.
  • the designated number dialed by the caller includes at least one of, an International Toll-Free Services (ITFS)
  • the call request includes at least one of, Session Initiation Protocol (SIP) INVITE requests.
  • IP Session Initiation Protocol
  • the relevant UE 112 is related to the caller.
  • the call is interfaced with the ILD carrier 330.
  • the ILD carrier 330 is communicably coupled to the ILD-Media Gateway Control Function 504 (ILD-MGCF).
  • ILD-MGCF ILD-Media Gateway Control Function 504
  • the ILD carrier 330, the ILD-MGCF 504, and the enterprise 212 are communicably coupled to the BTAS 206.
  • the BTAS 206 is configured to receive the call request transmitted by the ILD-MGCF 504.
  • the call request is routed to the ILD-MGCF 504 when the call request received is outbound.
  • the Media Gateway Control Function (MGCF) is a component within the telecommunications network that controls the setup, coordination, and termination of media gateway resources in support of voice or multimedia sessions.
  • the ILD-MGCF 504 is optimized for managing and controlling the international long-distance calls within the telecommunications network. It ensures efficient routing and handling of voice traffic that crosses international boundaries, typically between different network operators or service providers.
  • the ILD-MGCF 504 implies the MGCF specifically designed or configured to handle and control media sessions related to international long-distance communications.
  • the ILD-MGCF 504 is configured to route the call from the enterprise 212 to the user through the terminating network 508.
  • the ILD-MGCF 504 is configured to interface directly with the BTAS 206. Typically, the ILD-MGCF 504 cannot be interfaced directly with the BTAS 206.
  • the ITFS number is translated by the BTAS 206 from the ITFS number to a valid and routable E.164 number. From there, the call request is passed through the terminating network 508. If the call is not terminated, it is connected with the UE 112. As shown, the BTAS 206 is communicatively coupled to the enterprise 212 for the call routing.
  • the tasks and features may include, but may not be limited to, activating/ deactivating ITFS, implementing different call routing algorithms, classifying information as blacklisted or whitelisted, and announcing files.
  • the ILD-MGCF 504 is provided to transition data between two different domains within the terminating network 508 via an ILD-Gateway (ILD-GW) 506.
  • ILD-GW ILD-Gateway
  • An interface between the BTAS 206 and the ILD-MGCF 504 is a customized interface for routing the international call, thereby eliminating usage of IP Multimedia Core Network Subsystem (IMS) 406.
  • the interface between the BTAS 206 and the ILD- MGCF 504 is not a standard IP Multimedia Subsystem Service Control (ISC) interface, but a customized and enhanced version to support this unique interaction.
  • the ILD-GW 506 facilitates routing and management of international long-distance calls.
  • the ILD-GW 506 is responsible for handling the transition of calls between domestic and international networks, managing the protocols involved, and ensuring the proper routing of calls to their destination across international borders.
  • the ILD-MGCF 504 is communicably coupled to the terminating network 508 via the ILD-GW 506 to connect the call to the relevant UE 112.
  • the BTAS 206 is configured to dynamically customize at least one parameter of a header associated with the call request based on to which relevant UE the call is required to be routed.
  • the at least one parameter customized includes at least one of, routing rules, end point numbers behind International Toll-Free Services (ITFS) number and announcement files.
  • customizing at least one parameter of a header associated with the call request includes one of, updating, editing, adding, and deleting information from the call request.
  • the BTAS 206 is configured to customize the at least one parameter based on an input received from the admin of the enterprise 212 via the UE 112 in order to route the call to the relevant UE.
  • the admin of the enterprise 212 needs to update the announcement files in the BTAS 206. After updating, the updated announcement files are received by the relevant UE 112 of the user after the at least one parameter of the header associated with the call request through the terminating network 508.
  • the BTAS 206 is configured to return the call request to the ILD-MGCF 504 including the customized headers via the interface.
  • Session Initiation Protocol (SIP) INVITE Request Handling is performed by the BTAS 206.
  • the SIP INVITE request contains a "Route" header and a "P-Served-User" header.
  • the Route header is employed in the SIP messages to control the routing of the request or response. It contains a list of SIP URIs (Uniform Resource Identifiers) or addresses that represent the route or path that the SIP message takes to reach its destination.
  • SIP URIs Uniform Resource Identifiers
  • the P-Served-User header includes a SIP header used in VoIP communication.
  • the P-Served-User header carries information about the request of the user being sent or the call being established.
  • the P-Served-User header is typically added by a SIP server to identify the user being served by the server.
  • SIP communications the P-Served-User header helps in routing calls correctly, managing the services based on user profiles, and ensuring proper handling of calls within a VoIP network. It is especially important in scenarios where services or features are customized or tailored based on individual user preferences or service subscriptions.
  • the SIP is a signaling protocol commonly employed for initiating, modifying, and terminating real-time sessions involving video, voice, messaging, and other communication services.
  • the BTAS 206 utilizes a “via” header to route the international call to the relevant UE 112 through the ILD-MGCF 504 when the Route header and the P-Served User header are not present in the call request, thereby ensuring routing the call in the absence of standard headers in the call request.
  • the standard headers are specific fields within a protocol’s message format that carry standardized information according to the protocol’s specifications.
  • the standard headers are essential for communication between different network elements, ensuring interoperability and proper functioning of the communication system.
  • the standard headers include but not limited to, From, To, Call-ID, Via, Route, Contact, Content-Type, Content-Length, and many others.
  • the standard headers carry information such as caller identities, session identifiers, routing paths, content-related details, and the like.
  • the standard headers are used in a customized manner to loopback the call towards the ILD-MGCF 504.
  • the standard headers are not standard either, and rather, are received in accordance with the interface.
  • the SIP request may not include all standard headers that would have been received, in case, if the interface was standard. Based on the headers, the calls are routed to the UE 112.
  • the BTAS 206 is configured to connect the international call between the enterprise 212 and the relevant User Equipment (UE) 112 through one of the ILD-SBC 604 and the ILD-MGCF 504 based on the at least one customized parameter of the header associated with the call request.
  • customizing at least one parameter of the header associated with the call request includes one of, updating, editing, adding, and deleting information from the call request.
  • an Enterprise Provisioning Server (EPS) 410 is a centralized entity which interacts with all the BTAS 206 and has the intelligence to route provisioning request towards the BTAS 206.
  • the EPS 410 is configured for facilitating the enterprise 212 to provision the ITFS number at the BTAS 206 with all additional parameters required to render ITFS.
  • the parameters may include, but may not be limited to, routing algorithms, end point numbers behind ITFS number, announcement files, and the like.
  • the EPS 410 provides restful API for user to receive data requests, such as create, update, and delete, and send the same to the BTAS 206 for data provisioning.
  • the BTAS 206 manages all call requests with ITFS dialing number as terminating calls, extracting the served user from the "request_uri" of the INVITE. This ensures that the call is correctly terminated at the intended recipient, enhancing the reliability and accuracy of call routing.
  • Support for MACD Requests the BTAS 206 is designed to support Modification, Addition, Creation, and Deletion (MACD) requests received from Operations Support Systems/Business Support Systems (OSS/BSS) 408. This provides a high degree of flexibility and control over the telephony system, allowing for dynamic adjustments to meet operational needs.
  • the BTAS 206 supports the configuration of international toll-free numbers in all international formats, including those prefixed with '00' and '+'. This ensures compatibility with all international toll-free dialing patterns, enhancing the system's global usability.
  • the BTAS 206 provides several advanced call routing features.
  • the call routing features include, but is not limited to, the time-based routing, the direct translation with priority routing, the round robin, and the load balancing.
  • This feature allows for dynamic routing of calls to multiple destinations based on the time of day, day of the week, and date of the year. For example, during business hours, calls could be routed to a company's main office, while after-hours calls could be directed to an answering service.
  • This feature translates the B-party number from a list of numbers in a top-down manner if the call attempt to the top number fails. For example, if a call to the first number on the list fails, the system will automatically attempt to connect to the next number on the list.
  • This feature allows calls to be routed to multiple locations based on their call handling capacity. This is particularly useful for distributed call centers, as it ensures that no single location becomes overwhelmed with calls. For example, if one call center is nearing its capacity, this feature would start routing incoming calls to a different location with available capacity.
  • FIG. 6 illustrates a block diagram of a system 116 for managing the inbound call, according to one or more embodiments of the present invention.
  • the ILD carrier 330 is communicably coupled to the ILD-SBC 604.
  • the ILD carrier 330, the ILD-SBC 604, and the enterprise 212 are communicably coupled to the BTAS 206.
  • the BTAS 206 is configured to receive the call request transmitted by the ILD-SBC 604.
  • the ILD-SBC 604, which is the Session Border Controller (SBC) is a network device that controls the signaling and media streams involved in setting up, and conducting communication sessions, such as voice calls over IP networks. It acts as a gateway between different networks, enforcing security policies, and providing functions like protocol translation, call admission control, and network address translation (NAT).
  • SBC Session Border Controller
  • the ILD-SBC 604 is specifically designed or optimized for managing international long-distance calls within the network 114. It may include features tailored for interconnection between different operators or service providers, as well as handling roaming scenarios where subscribers use services outside their home network.
  • the call request is routed to the ILD-SBC 604 when the call request received is inbound.
  • the ILD-SBC 604 is configured to interface directly with the BTAS 206.
  • the ILD-SBC 604 cannot be interfaced directly with the BTAS 206.
  • the ITFS number is translated by the BTAS 206 from the ITFS number to a valid and routable E.164 number. From there, the call request is passed through the terminating network 508. If the call is not terminated, it is connected with the UE 112.
  • the BTAS 206 is communicatively coupled to the enterprise 212 for call routing.
  • the tasks and features may include, but may not be limited to, activating/ deactivating ITFS, implementing different call routing algorithms, classifying information as blacklisted or whitelisted, and announcing files.
  • the session border controller is provided to transition data between two different domains within the terminating network 508.
  • the ILD-SBC 604 implies the Session Border Controller specifically designed or configured to handle and optimize the secure and efficient flow of Voice over Internet Protocol (VoIP) sessions across international long-distance networks to manage the signaling and media streams involved in VoIP communications. It acts as a border element between different IP networks, ensuring the secure and efficient flow of voice and multimedia sessions.
  • VoIP Voice over Internet Protocol
  • the ILD-SBC 604 supports a wide range of signaling protocols to ensure interoperability with various networks worldwide.
  • the ILD-SBC 604 is configured to connect the call from the user to the enterprise 212 through the terminating network 508 via the ILD-GW 506.
  • the ILD-SBC 604 is provided to transition data between two different domains within the terminating network 508.
  • the interface between the BTAS 206 and the ILD-SBC 604 is the customized interface for routing the international call, thereby eliminating usage of IP Multimedia Core Network Subsystem (IMS) 406.
  • the interface between the BTAS 206 and the ILD-SBC 604 is not a standard IP Multimedia Subsystem Service Control (ISC) interface, but a customized and enhanced version to support this unique interaction.
  • IMS IP Multimedia Core Network Subsystem
  • the ILD-Gateway (ILD-GW) 506 facilitates routing and management of international long-distance calls.
  • the ILD-GW 506 is responsible for handling the transition of calls between domestic and international networks, managing the protocols involved, and ensuring the proper routing of calls to their destination across international borders.
  • the UE 112 of the user initiates the request to connect the inbound call from the user to the ILD-SBC 604 within the terminating network 508 via the ILD-GW 506 .
  • the BTAS 206 is configured to dynamically customize at least one parameter of a header associated with the call request based on to which relevant UE the call is required to be routed.
  • the at least one parameter customized includes at least one of, routing rules, end point numbers behind International Toll-Free Services (ITFS) number and announcement files.
  • customizing at least one parameter of a header associated with the call request includes one of, updating, editing, adding, and deleting information from the call request.
  • the BTAS 206 is configured to customize the at least one parameter based on an input received from the admin of the enterprise 212 via the UE 112 in order to route the call to the relevant UE. Let us consider for example, the admin of the enterprise 212 needs to update the announcement files in the BTAS 206. The updated announcement files are received by the relevant UE 112 after the at least one parameter of the header associated with the call request through the terminating network 508.
  • the BTAS 206 is configured to return the call request to the ILD-SBC 604 including the customized headers via the interface.
  • Session Initiation Protocol (SIP) INVITE Request Handling is performed by the BTAS 206.
  • the SIP INVITE request received at the BTAS 206 may not contain the "Route" header and the "P-Served-User" header typically present in the interface.
  • the route header is employed in SIP messages to control the routing of the request or response. It contains a list of SIP URIs (Uniform Resource Identifiers) or addresses that represent the route or path that the SIP message should take to reach its destination.
  • SIP URIs Uniform Resource Identifiers
  • the P-Served-User header includes a SIP header used in VoIP communication.
  • the P-Served-User header carries information about the request of the user being sent or the call being established.
  • the P-Served-User header is typically added by a SIP server to identify the user being served by the server.
  • SIP communications the P-Served-User header helps in routing calls correctly, managing the services based on user profiles, and ensuring proper handling of calls within a VoIP network. It is especially important in scenarios where services or features are customized or tailored based on individual user preferences or service subscriptions.
  • the SIP is a signaling protocol commonly employed for initiating, modifying, and terminating real-time sessions involving video, voice, messaging, and other communication services.
  • the BTAS 206 utilizes the "via" header to route the international call to the relevant UE 112 through the ILD-MGCF 504 when the route header and the P-Served User header are not present in the call request, thereby ensuring routing the call in the absence of standard headers in the call request.
  • the BTAS 206 is configured to connect the international call between the enterprise 212 and the relevant User Equipment (UE) 112 through the ILD-SBC 604 based on the at least one customized parameter of the header associated with the call request.
  • customizing at least one parameter of the header associated with the call request includes one of, updating, editing, adding, and deleting information from the call request.
  • an Enterprise Provisioning Server (EPS) 410 is the centralized entity which interacts with all the BTAS 206 and has the intelligence to route provisioning request towards the designated BTAS 206.
  • the EPS 410 is configured for facilitating the enterprise 212 to provision the ITFS number at the BTAS 206 with all additional parameters required to render ITFS.
  • the parameters may include, but may not be limited to, routing algorithms, end point numbers behind ITFS number, announcement files, and the like.
  • the EPS 410 provides restful API for user to receive data requests, such as create, update, and delete, and send the same to the BTAS 206 for data provisioning.
  • the BTAS 206 manages all call requests with ITFS dialing number as terminating calls, extracting the served user from the "request_uri" of the INVITE. This ensures that the call is correctly terminated at the intended recipient, enhancing the reliability and accuracy of call routing.
  • Support for MACD Requests the BTAS 206 is designed to support Modification, Addition, Creation, and Deletion (MACD) requests received from Operations Support Systems/Business Support Systems (OSS/BSS) 408. This provides a high degree of flexibility and control over the telephony system, allowing for dynamic adjustments to meet operational needs.
  • the BTAS 206 supports the configuration of international toll-free numbers in all international formats, including those prefixed with '00' and '+'. This ensures compatibility with all international toll- free dialing patterns, enhancing the system's global usability.
  • FIG. 7 is a flow chart of a method 700 for routing an international call, according to one or more embodiments of the present invention.
  • the method 700 includes the step of receiving, by the one or more processors 204, the call request initiated from the caller by dialing the designated number associated to the enterprise 212 by the interface module in the UE 112.
  • the terminating network 508 is JIO network.
  • the user interface module may include a messaging module, a voicemail module, and the like.
  • jurisdiction of the caller includes at least one of, international and domestic.
  • the designated number dialed by the caller includes at least one of, the International Toll-Free Services (ITFS) number and the Universal International Freephone Number (UIFN).
  • the call request includes at least one of, Session Initiation Protocol (SIP) INVITE requests.
  • SIP Session Initiation Protocol
  • the method 700 includes the step of routing, by the one or more processors 204, the call request to the International Long Distance Session Border Controller (ILD-SBC) 604 when the call request received is inbound and routing the call to the International Long Distance Media Gateway Control Function (ILD- MGCF) 504 when the call request received is outbound.
  • IMS IP Multimedia Core Network Subsystem
  • the interface between the BTAS 206 and the ILD-MGCF 504/ the ILD-SBC 604 is not the standard IP Multimedia Subsystem Service Control (ISC) interface, but a customized and enhanced version to support this unique interaction.
  • ISC IP Multimedia Subsystem Service Control
  • the method 700 includes the step of receiving, by the one or more processors 204, the call request transmitted by one of, the ILD-SBC 604 and the ILD-MGCF 504 depending on inbound or outbound origination of the call request via an interface by the BTAS 206.
  • the BTAS 206 is configured to extract recipient details from the call request, thereby enabling termination of the call to the relevant recipient.
  • recipient details may include, at least one of the mobile number, the user ID, and the date and time of the call.
  • the BTAS 206 supports configuration of ITFS numbers in all the international dialing patterns and formats such as at least one of, ‘00’ and ‘+’.
  • the method 700 includes the step of customizing, by the one or more processors 204, at least one parameter of a header associated with the call request.
  • the at least one parameter customized includes at least one of, routing rules, end point numbers behind International Toll-Free Services (ITFS) number and announcement files.
  • the at least one parameter is dynamically customized by the BTAS 206 based on to which relevant UE 112 the call is required to be routed.
  • the at least one parameter is customized by the BTAS 206 based on the input received from the admin of the enterprise 212 via the UE 112 in order to route the call to the relevant UE 112.
  • the method 700 includes the step of returning, by the one or more processors 205, the call request to one of the ILD-SBC 604 and the ILD-MGCF 504 including the customized headers via the interface.
  • Session Initiation Protocol (SIP) INVITE Request Handling is performed by the BTAS 206.
  • the SIP INVITE request received at the BTAS 206 may not contain the "Route" header and the "P-Served-User" header typically present in the interface.
  • the BTAS 206 utilizes the "via" header to route the international call to the relevant UE 112 through one of the respective ILD-SBC 604 and the ILD-MGCF 504 when the route header and the p-served user header are not present in the call request, thereby ensuring routing the call in the absence of standard headers in the call request.
  • the method includes, utilizing, by the BTAS 206, a via header from the call request to route the international call to the relevant UE 112, through one of the respective ILD-SBC 604 and the ILD-MGCF 504 when the route header and the P-Served User header are not present in the call request, thereby ensuring routing the call in the absence of standard headers in the call request.
  • the method 700 includes the step of connecting, by the one or more processors 205, the international call between the enterprise 212 and the relevant User Equipment (UE) 112 through one of the ILD-SBC 604 and the ILD-MGCF 504 based on the at least one customized parameter of the header associated with the call request.
  • customizing at least one parameter of the header associated with the call request includes one of, updating, editing, adding, and deleting information from the call request.
  • the BTAS 206 manages all call requests with ITFS dialing number as terminating calls, extracting the served user from the "request_uri" of the INVITE. This ensures that the call is correctly terminated at the intended recipient, enhancing the reliability and accuracy of call routing.
  • Support for MACD Requests the BTAS 206 is designed to support Modification, Addition, Creation, and Deletion (MACD) requests received from Operations Support Systems/Business Support Systems (OSS/BSS) 308. This provides a high degree of flexibility and control over the telephony system, allowing for dynamic adjustments to meet operational needs.
  • the present invention further discloses a non-transitory computer- readable medium having stored thereon computer-readable instructions.
  • the computer-readable instructions are executed by a processor 205.
  • the processor 205 is configured to receive a call request initiated from a caller by dialing a designated number associated to an enterprise 212.
  • the processor 205 is further configured to route the call request to an International Long Distance Session Border Controller (ILD-SBC) 604 when the call request received is inbound and routing the call to an International Long Distance Media Gateway Control Function (ILD-MGCF) 504 when the call request received is outbound.
  • ILD-SBC International Long Distance Session Border Controller
  • ILD-MGCF International Long Distance Media Gateway Control Function
  • the processor 205 is further configured to customize at least one parameter of a header associated with the call request.
  • the processor 205 is further configured to return the call request to one of the ILD-SBC 604 and the ILD-MGCF 504 including the customized headers via the interface.
  • the processor 205 is further configured to connect the international call between the enterprise 212 and a relevant UE 112 through one of the ILD-SBC 604 and the ILD- MGCF 504 based on the at least one customized parameter of the header associated with the call request.
  • FIG.1 -6 A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIG.1 -6) are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
  • the present disclosure incorporates technical advancement of allowing the enterprise to extend its reach to other countries and thereby provide ITFS service and ensuring ease of connectivity for the UE and the enterprise.
  • the ITFS outbound service enables customers in one country to make toll-free calls that can be terminated in another country. Using this ITFS service callers from a country avail direct access mechanism to international destinations without having to activate ISD facility.
  • the BTAS provides flexible and easy to use provisioning interface which allows the enterprise to update/create/delete one or more parameters of their ITFS, which gets reflected in real-time independent of the complexity of network Support for real time data reporting as requested by the admin of the enterprise.
  • the present invention offers multiple advantages over the prior art and the above listed are a few examples to emphasize on some of the advantageous features.
  • the listed advantages are to be read in a non-limiting manner.
  • Second server - 104 Second server - 104;
  • ILD carrier -330 [00119]

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Telephonic Communication Services (AREA)

Abstract

La présente divulgation concerne un système (116) et un procédé (700) de routage d'un appel international, le système (116) comprenant un serveur d'application de téléphonie commerciale (BTAS) (206). Le BTAS (206) est configuré pour recevoir une demande d'appel transmise par l'un parmi l'ILD-SBC (604) et l'ILD-MGCF (504) en fonction d'une origine entrante ou sortante. Le BTAS (206) est également configuré pour personnaliser au moins un paramètre d'un en-tête associé à la demande d'appel. Le BTAS (206) est en outre configuré pour renvoyer la demande d'appel au ILD-SBC (604) et à l'ILD-MGCF (504) comprenant les en-têtes personnalisés par l'intermédiaire de l'interface. De plus, le BTAS (206) est configuré pour connecter un appel international entre l'entreprise (212) et un équipement utilisateur (UE) (112) par l'intermédiaire de l'ILD-SBC (604) et de l'ILD-MGCF (504) sur la base du ou des paramètres personnalisés de l'en-tête associé à la demande d'appel.
PCT/IN2024/050949 2023-07-03 2024-06-27 Système et procédé de routage d'un appel international Ceased WO2025008962A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN202321044344 2023-07-03
IN202321044344 2023-07-03

Publications (1)

Publication Number Publication Date
WO2025008962A1 true WO2025008962A1 (fr) 2025-01-09

Family

ID=94171567

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IN2024/050949 Ceased WO2025008962A1 (fr) 2023-07-03 2024-06-27 Système et procédé de routage d'un appel international

Country Status (1)

Country Link
WO (1) WO2025008962A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050058270A1 (en) * 2003-09-12 2005-03-17 Sbc Knowledge Ventures, L.P. International origin dependent customized routing of calls to toll-free numbers
US20230006923A1 (en) * 2021-06-30 2023-01-05 T-Mobile Innovations Llc Call Route Generation for Other Communication Service Carriers as a Service

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050058270A1 (en) * 2003-09-12 2005-03-17 Sbc Knowledge Ventures, L.P. International origin dependent customized routing of calls to toll-free numbers
US20230006923A1 (en) * 2021-06-30 2023-01-05 T-Mobile Innovations Llc Call Route Generation for Other Communication Service Carriers as a Service

Similar Documents

Publication Publication Date Title
US12395425B2 (en) Determining a time to permit a communications session to be conducted
US20080293427A1 (en) System and method for mobile originated optimal call routing
US8811383B2 (en) Communication system and method
US20080292092A1 (en) System and method for telephone number normalization and denormalization
WO2025008962A1 (fr) Système et procédé de routage d'un appel international
JP2025512627A (ja) Ｆｉｘｅｄ ｍｏｂｉｌｅ ｃｏｎｖｅｒｇｅｎｃｅサービスを提供するためのシステムおよび方法
US8654957B2 (en) Method and apparatus for providing internet protocol services to a user of a private branch exchange
US9628298B2 (en) Routing technique
US20250267217A1 (en) Method for rerouting communication in a unified communications network
WO2025008967A1 (fr) Système et procédé de gestion d'une demande d'appel
WO2025099774A1 (fr) Système et procédé de déploiement d'un numéro gratuit

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24835683

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2024835683

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2024835683

Country of ref document: EP

Effective date: 20260203