WO2025008976A1 - Procédé et système de gestion de facturation d'appel dans un réseau - Google Patents

Procédé et système de gestion de facturation d'appel dans un réseau Download PDF

Info

Publication number
WO2025008976A1
WO2025008976A1 PCT/IN2024/050974 IN2024050974W WO2025008976A1 WO 2025008976 A1 WO2025008976 A1 WO 2025008976A1 IN 2024050974 W IN2024050974 W IN 2024050974W WO 2025008976 A1 WO2025008976 A1 WO 2025008976A1
Authority
WO
WIPO (PCT)
Prior art keywords
call
request
charging
trigger
received
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/050974
Other languages
English (en)
Inventor
Aayush Bhatnagar
Birendra Bisht
Harbinder Singh
Sandeep Gupta
Raghav DAS
Srikanth P Reddy
Surabhi RANJAN
Priti Kelkar
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 WO2025008976A1 publication Critical patent/WO2025008976A1/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
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements specially adapted for data communications, e.g. authentication, authorisation and accounting [AAA] framework
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/08—Metering calls to called party, i.e. B-party charged for the communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/63—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on the content carried by the session initiation protocol [SIP] messages
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/64—On-line charging system [OCS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82—Criteria or parameters used for performing billing operations
    • H04M15/8228—Session based
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/83—Notification aspects
    • H04M15/85—Notification aspects characterised by the type of condition triggering a notification
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing

Definitions

  • the present invention relates to the field of wireless communication system, more particularly relates to a method and system for managing call charging in a network.
  • the present disclosure pertains to the field of telephony systems and, more specifically, to the interaction between the Online Charging System (OCS) and the Business Telephony Application System (BTAS) through the Diameter Routing Agent (DRA).
  • OCS Online Charging System
  • BTAS Business Telephony Application System
  • DAA Diameter Routing Agent
  • IMS IP Multimedia Subsystem
  • the BTAS receives service requests from subscribers, typically initiated through the Session Initiation Protocol (SIP) interface, and sends charging requests to the OCS via the Diameter interface.
  • SIP Session Initiation Protocol
  • the OCS processes these requests and provides a response that determines the call's further execution. This represents the conventional charging mechanism used across networks.
  • the customized charging support addresses several problems and offers unique features. Firstly, it allows for charging enterprise users in a manner that aligns with their individual requirements. Instead of a one-size-fits-all approach, this customization enables differentiated charging based on subscriber types within the enterprise network.
  • the behavior of the call can be governed based on the responses received via the Diameter interface.
  • the BTAS can utilize the information in the Diameter responses to determine call handling and apply specific call policies accordingly. This flexibility enhances the overall user experience and service management within the BTAS environment.
  • the BTAS can map SIP response codes based on the Diameter responses received over the Ro interface. This mapping enables seamless interoperability between the Diameter and SIP protocols, ensuring accurate and consistent handling of call-related events and signaling.
  • a method of managing a call charging in a network includes the step of receiving a call request from at least one User Equipment via an interface. The method further includes the step of retrieving information pertaining to at least one of a call service type and a call service request from the received call request. The method further includes the step of determining if a Charging Control Request (CCR) trigger is required to be transmitted to an Online Charging System (OCS) for charging the received call request.
  • CCR Charging Control Request
  • OCS Online Charging System
  • the method further includes the step of transmitting the CCR trigger to the OCS on determination that the CCR trigger is required to be transmitted via a Diameter Routing Agent (DRA).
  • the method further includes the step of determining a Credit Control Answer (CCA) utilizing the information retrieved from the received call request to indicate a charging status and a valuation of the call request, thereby managing call charging in the network.
  • CCA Credit Control Answer
  • the method further includes the step of determining a call behavior applicable to the received call request, wherein the call behavior is customizable based on a response received from the OCS and the call service type.
  • the method further includes the step of applying the determined call behavior to the received call request.
  • the call behavior pertains to an activity which includes one of continuing the call, deny the call, deny call with announcement and continue call with announcement.
  • the call service type is one of an originating call and a terminating call.
  • the call service request is one of at least a toll- free number dialing, Internet Protocol (IP) centrex services, and service for trunk users.
  • IP Internet Protocol
  • the call request is received utilizing a Session Initiation Protocol (SIP) and the CCR trigger is transmitted to the OCS via the DRA utilizing a diameter interface.
  • SIP Session Initiation Protocol
  • the CCR trigger is transmitted to the OCS based on a satisfaction of a set of predefined conditions, wherein the set of pre-defined conditions are dependent on parameters such as service type, Closed User Group, and SIP method, wherein charging is customized by a service provider based on at least one of business requirements and the call service type.
  • the method in response to transmission of the CCR trigger, the method further comprising the step of receiving a diameter response from the OCS.
  • the method further includes the step of mapping the diameter response to a SIP response as customized by a service provider.
  • the method further includes the step of implementing the call behavior at the at least one UE based on the mapping.
  • mapping of the diameter response to the SIP response is dependent on the call service type.
  • the set of predefined conditions include at least one of a first condition to check information retrieved from the call received in order to identify which BTAS service type needs to be accessed and to determine whether the CCR trigger is required to be transmitted for the identified BTAS service type based on the customization, a second condition to determine a call type of an ongoing call, whether it is at least one of, a Closed User Group (CUG) class, an INTER call type, an INTRA call type or an Outside call type and to determine whether a Ro trigger is configured for the identified BTAS service type and a third condition to check which type of SIP invite is received, which includes at least one of, an invite request and update request in the call request and to determine the Ro trigger corresponding to the SIP invite received is enabled or disabled based on the customization.
  • a first condition to check information retrieved from the call received in order to identify which BTAS service type needs to be accessed and to determine whether the CCR trigger is required to be transmitted for the identified BTAS service type based on the customization
  • a second condition
  • a system for managing call charging in a network includes a transceiver configured to receive a call request from an at least one User Equipment via an interface.
  • the system further includes an extraction unit configured to retrieve information pertaining to at least one of a call service type and a call service request from the received call request.
  • the system further includes a determination unit configured to determine if a Charging Control Request (CCR) trigger is required to be transmitted to an Online Charging System (OCS) for charging the received call request.
  • CCS Online Charging System
  • the system further includes the transceiver configured to transmit the CCR trigger to the OCS on determination that the CCR trigger is required to be transmitted via a Diameter Routing Agent (DRA).
  • DDA Diameter Routing Agent
  • the system further includes the determination unit configured to determine a Credit Control Answer (CCA) utilizing the information retrieved to indicate a charging status and a valuation of the call request, thereby managing call charging in the network.
  • CCA Credit Control Answer
  • a User Equipment UE
  • One or more primary processors communicatively coupled to one or more processors.
  • the one or more primary processors coupled with a memory.
  • the memory stores instructions which when executed by the one or more primary processors causes the UE to transmit a call request to the one or more processors via an interface.
  • the one or more processors are configured to perform the method for managing call charging in a network.
  • a non-transitory computer- readable medium having stored thereon computer-readable instructions that, when executed by a processor.
  • the processor is configured to receive a call request from an at least one User Equipment via an interface.
  • the processor is further configured to retrieve information pertaining to at least one of a call service type and a call service request from the received call request.
  • the processor is further configured to determine if a Charging Control Request (CCR) trigger is required to be transmitted to an Online Charging System (OCS) for charging the received call request.
  • the processor is further configured to transmit the CCR trigger to the OCS on determination that the CCR trigger is required to be transmitted via a Diameter Routing Agent (DRA).
  • DDA Diameter Routing Agent
  • the processor is further configured to determine a Credit Control Answer (CCA) utilizing the information retrieved to indicate a charging status and a valuation of the call request, thereby managing call charging in the network.
  • CCA Credit Control Answer
  • FIG. 1 is an exemplary block diagram of an environment for managing call charging in a network, according to one or more embodiments of the present invention
  • FIG. 2 is an exemplary block diagram of the system for managing call charging in a network, according to one or more embodiments of the present invention
  • FIG. 3 is an exemplary flow diagram of the system of FIG. 2, according to one or more embodiments of the present invention.
  • FIG. 4 is a flow diagram of a method for managing call charging in a network, according to one or more embodiments of the present invention.
  • FIG. 5 is a signal flow diagram illustrating the system for managing call charging in a network, according to one or more embodiments of the present disclosure.
  • the present invention provides a flexible and a customizable call charging support system in a network.
  • the system allows service providers to configure charging triggers, call behavior, and SIP responses based on diameter responses received from the Online Charging System (OCS) over the Ro interface.
  • OCS Online Charging System
  • the present invention eliminates the need for any backend changes or code level changes.
  • the present invention offers advantages such as tailored charging for different service types, configurable call behavior based on diameter responses, and easy mapping of SIP responses to the diameter responses.
  • FIG. 1 illustrates an exemplary block diagram of an environment 100 for managing call charging in a network 106, according to one or more embodiments of the present invention.
  • the environment 100 includes, a User Equipment (UE) 102, a server 104, a network 106 and a system 108.
  • the UE 102 aids a user to interact with the system 108 to transmit a call request in order to establish a call within a network 106.
  • UE User Equipment
  • UEs user equipment
  • Each of the at least one UE 102 namely the first UE 102a, the second UE 102b, and the third UE 102c is configured to connect to the server 104 via the network 106.
  • each of the first UE 102a, the second UE 102b, and the third UE 102c 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, a general- purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device.
  • VR virtual reality
  • AR augmented reality
  • the network 106 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 106 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
  • O-RAN Open Radio Access Network
  • the network 106 may also 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 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, a V OIP or some combination thereof.
  • PSTN Public- Switched Telephone Network
  • the environment 100 includes the server 104 accessible via the network 106.
  • the server 115 may 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, a processor 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 side, a defence facility side, or any other facility that provides service.
  • the environment 100 further includes a system 108 communicably coupled to the server 104 and each of the first UE 102a, the second UE 102b, and the third UE 102c via the network 106.
  • the system 108 is adapted to be embedded within the server 104 or is embedded as the individual entity. However, for the purpose of description, the system 108 is described as an integral part of the server 104, without deviating from the scope of the present disclosure.
  • the system 108 is configured to manipulate message in the network 106.
  • FIG. 2 is an exemplary block diagram of the system 108 for managing call charging in a network 106, according to one or more embodiments of the present invention.
  • the system 108 to manage call charging in the network 106 is a Business Telephony Application Server (BTAS).
  • BTAS provides a full-featured telephony and multimedia application system.
  • the BTAS helps to rapidly develop and deliver services for enterprise and residential customers.
  • the BTAS contains the service logic that provides the basic call-processing services, including digit analysis, routing, call setup, call waiting, call forwarding, conferencing, etc.
  • the BTAS also provides the service logic for invoking the media servers to provide the appropriate call progress tones and announcements.
  • the system 108 is a central component that handles various telephony services.
  • the system 108 operates based on industry-standard protocols and leverages configuration capabilities to customize a charging process and a call behavior.
  • the system 108 includes one or more processors 202, a memory 204, a database 218 and a User Interface module 220.
  • the one or more processors 202 includes a transceiver 206, an extraction unit 208, a determination unit 210, a mapping unit 212, and an implementation unit 214.
  • the one or more processors 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, single board computers, and/or any devices that manipulate signals based on operational instructions.
  • the system 108 may include multiple processors as per the requirement and without deviating from the scope of the present disclosure.
  • the processor 202 is configured to fetch and execute computer-readable instructions stored in the memory 204.
  • the processor 202 is configured to fetch and execute computer-readable instructions stored in the memory 204 as the memory 204 is communicably connected to the processor 202.
  • the memory 204 is 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 204 may include any non- transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as disk memory, EPROMs, FLASH memory, unalterable memory, and the like.
  • the transceiver 206 of the processor 202 is communicably connected to each of the at least first UE 102a, the second UE 102b, and the third UE 102c via the network 106. Initially, the UE 102 transmits a call request to the processor 202 via an interface. Further the processor 202 is configured to perform the method for managing call charging in a network 106. Accordingly, the transceiver 206 is configured to receive a call request from the UE 102 via an interface. In one embodiment, the interface includes at least one of, but not limited to, an Application Programming Interface (API). The transceiver 206 is further configured to transmit, the Charging Control Request (CCR) trigger to the OCS 312 (shown in FIG. 3) subsequent to determination of the CCR trigger is required to be transmitted to the OCS 312.
  • CCR Charging Control Request
  • the extraction unit 208 of the processor 202 is configured to retrieve information pertaining to at least one of a call service type and a call service request from the call request received from the UE 102.
  • the call service type is one of an originating call and a terminating call.
  • the call service request is one of at least a toll-free number dialing, Internet Protocol (IP) centrex services, and service for trunk users.
  • IP Internet Protocol
  • the IP Centrex service is a cloud-based telephony service. Businesses use it for Voice over Internet Protocol (VoIP) based communication to avoid having all the necessary equipment on-site.
  • VoIP Voice over Internet Protocol
  • the determination unit 210 of the processor 202 is configured to determine whether a Charging Control Request (CCR) trigger is required to be transmitted to an Online Charging System (OCS) 312 for charging the call request received from the UE 102.
  • the determination unit 210 checks a set of predefined conditions, based on which the transceiver 206 transmits the Charging Control Request (CCR) trigger to the OCS 312.
  • the determination unit 210 is further configured to determine a Diameter Credit Control Answer (CCA) response utilizing the information retrieved pertaining to at least one of a call service type and a call service request to indicate a charging status and a valuation of the call request.
  • the valuation of the call request is performed by the OCS 312.
  • the valuation of the call request pertains to ascertaining the charges for the call initiated by user. In another embodiment, the valuation of the call request corresponds to monetary charges incurred to the user for one or more of, initiating the call, using the calling service, call duration, making the call.
  • the determination unit 210 is further configured to determine a call behavior based on the Diameter CCA response received from the OCS 102. In an embodiment, the call behavior pertains to an activity which includes at least one of, continuing the call, denying the call, denying call with an announcement and continuing the call with an announcement. Based on the determination of the call behavior, the determination unit 210 applies the determined call behavior to the call request. In other words, the ongoing call will be continued or denied by the determination unit 210.
  • the CCR Credit Control Request
  • the CCA Credit Control Answer
  • the diameter protocol is related to the mobile communication networks, such as 4G LTE networks.
  • the diameter protocol provides authentication, authorization, and accounting (AAA) messaging services for network access and data mobility applications in 3G, IP Multimedia Systems (IMS), and LTE/4G networks.
  • the CCR represents a Diameter Credit-Control-Request message, which is transmitted to the OCS 102 by the processors 202.
  • the CCA represents the Diameter CCA response which is transmitted by the OCS 102 to the processor 202.
  • Diameter Credit-Control application messages for a Debit /Reserve Unit Request operation is a Credit-Control-Request (CCR) and for a Debit /Reserve Unit Response operation is Credit-Control-Answer (CCA).
  • CCR Credit-Control-Request
  • CCA Credit-Control-Answer
  • the mapping unit 212 of the processor 202 is configured to map the diameter responses to Session Initiation Protocol (SIP) responses as customized by the service provider.
  • the mapping of the diameter responses to the SIP responses is dependent on the call service type.
  • the mapping unit 212 enables service providers to map SIP responses to specific diameter responses which ensures consistent and appropriate handling of call-related events.
  • Service providers customize the SIP responses using a user interface module 220 according to their preferences and requirements.
  • the diameter responses are received by the system 108 from the OCS 312 and the SIP responses are stored in a database 218.
  • the Session Initiation Protocol is a signaling protocol that enables the Voice Over Internet Protocol (VoIP) by defining the messages sent between endpoints and managing the actual elements of a call.
  • VoIP Voice Over Internet Protocol
  • SIP is used for initiating, maintaining, modifying and terminating real-time communications sessions between Internet Protocol (IP) devices.
  • IP Internet Protocol
  • SIP enables voice, messaging, video and other communications applications and services between two or more endpoints on IP networks.
  • the SIP response provides information about the status of the call.
  • the database 218 is one of, but not limited to, 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 user interface module 220 of the system 108 includes a variety of interfaces, for example, a graphical user interface, a web user interface, a Command Line Interface (CLI), and the like.
  • the user interface module 220 allows service providers to configure and customize a charging mechanism, a call behavior, and Session Initiation Protocol (SIP) responses.
  • the implementation unit 214 of the processor 202 is configured to implement the call behavior at the at least one UE 102 based on the mapping of the diameter responses with the SIP responses configured by the service providers.
  • the call behavior pertains to an activity which includes one of continuing the call, denying the call, denying the call with an announcement and continuing the call with an announcement. For example, when the diameter response is received from the OCS 312, the implementation unit 214 of the system 108 decides whether to continue the ongoing call or deny the ongoing call based on the mapping of the diameter responses to the SIP responses.
  • the transceiver 206, the extraction unit 208, the determination unit 210, the mapping unit 212, and the implementation unit 214 in an exemplary embodiment, are implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processor 202.
  • programming for the processor 202 may be processor-executable instructions stored on a non-transitory machine -readable storage medium and the hardware for the processor may comprise a processing resource (for example, one or more processors), to execute such instructions.
  • the memory 204 may store instructions that, when executed by the processing resource, implement the processor 202.
  • the system 108 may comprise the memory 204 storing the instructions and the processing resource to execute the instructions, or the memory 204 may be separate but accessible to the system 108 and the processing resource.
  • the processor 202 may be implemented by electronic circuitry.
  • FIG. 3 illustrates an exemplary block diagram of an architecture for the system 108 of FIG. 2, according to one or more embodiments of the present invention. More specifically, FIG. 3 illustrates the system 108 configured for managing call charging in a network 106. It is to be noted that the embodiment with respect to FIG. 3 will be explained with respect to the UE 102 for the purpose of description and illustration and should nowhere be construed as limited to the scope of the present disclosure.
  • the FIG. 3 includes a UE 102, the system 108, a Diameter Routing Agent (DRA) 310 and an Online Charging System (OCS) 312.
  • DDA Diameter Routing Agent
  • OCS Online Charging System
  • the Diameter Routing Agent (DRA) 310 is a functional element in a 3G or 4G (such as LTE) network that provides real-time routing capabilities to ensure that request/messages/calls are routed among the correct network elements in the network.
  • the Online charging system (OCS) 312 is a system allowing a communications service provider to charge their customers, in real time, based on service usage.
  • the diameter interface connects the DRA 310 with the OCS 312 in a diameter protocol based mobile communication networks, such as 4G LTE networks.
  • the diameter protocol provides authentication, authorization, and accounting (AAA) messaging services for network access and data mobility applications in 3G, IP Multimedia Systems (IMS), and LTE/4G networks.
  • the User Equipment (UE) 102 uses network protocol connection to communicate with the system 108. Accordingly, the UE 102 is configured to transmit a call request to the system 108 via an interface.
  • the network protocol connection is the establishment and management of communication between the UE 102 and the system 108 over the network 106 using a specific protocol or set of protocols.
  • the network protocol connection includes, but not limited to, Session Initiation Protocol (SIP), System Information Block (SIB) protocol, Transmission Control Protocol (TCP), User Datagram Protocol (UDP), File Transfer Protocol (FTP), Hypertext Transfer Protocol (HTTP), Simple Network Management Protocol (SNMP), Internet Control Message Protocol (ICMP), Hypertext Transfer Protocol Secure (HTTPS) and Terminal Network (TELNET).
  • SIP Session Initiation Protocol
  • SIB System Information Block
  • TCP Transmission Control Protocol
  • UDP User Datagram Protocol
  • FTP File Transfer Protocol
  • HTTP Hypertext Transfer Protocol
  • SNMP Simple Network Management Protocol
  • ICMP Internet Control Message Protocol
  • HTTPS Hypertext Transfer Protocol Secure
  • TELNET Terminal Network
  • the UE 102 includes a primary processor 302, a memory 304, and a user interface 306.
  • the UE 102 may include more than one primary processor 302 as per the requirement of the network 106.
  • the primary processor 302 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, single board computers, and/or any devices that manipulate signals based on operational instructions.
  • the primary processor 302 is configured to fetch and execute computer-readable instructions stored in the memory 304.
  • the memory 304 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 304 may include any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as disk memory, EPROMs, FLASH memory, unalterable memory, and the like.
  • the user interface 306 of the UE 102 includes a variety of interfaces, for example, a graphical user interface, a web user interface, a Command Line Interface (CLI), and the like.
  • the user interface module 306 is configured to allow a user to transmit a call request to the processor 202.
  • the user interface module 306 facilitates communication with the system 108.
  • Diameter Routing Agent (DRA) 310 provides a realtime routing capability to ensure that calls are routed among the correct elements in a network 106.
  • the DRA 310 connects the system 108 with the OCS 312 via at least one of, a diameter interface and a Ro interface.
  • Diameter is a protocol used for authentication, authorization, and accounting (AAA) in IP networks.
  • AAA authentication, authorization, and accounting
  • the Ro interface is a 3rd Generation Partnership Project (3GPP) reference point that describes the connection to the OCS 312 from another functional component.
  • the Ro interface supports Ro protocol which allows a Charging Trigger Function (CTF) to issue charging events to the OCS 312.
  • CTF Charging Trigger Function
  • the charging events can be immediate, event-based, or session-based.
  • the Ro interface is the interface between the system and the OCS 312.
  • the Ro trigger is configured to trigger the online charging via the Ro interface based on the identified call service type.
  • the Online charging system (OCS) 312 performs charging calculations based on the information received retrieved pertaining to at least one of a call service type and a call service request and provides a Diameter Credit Control Answer (CCA) response indicating the charging status and valuation of the call.
  • the system 108 connects to the OCS 312 through a DRA 310 over at least one of, the diameter interface and the Ro interface. Diameter interface and Ro interface enables communication between the system 108 and the OCS 312, ensuring secure and reliable exchange of charging-related information.
  • the system 108 receives the call signaling through the Session Initiation Protocol (SIP).
  • SIP Session Initiation Protocol
  • the system 108 processes the SIP requests/messages and determines the call service type and specific call service request. Further based on the call service type and subsequent to checking the set of pre-defined conditions, the system 108 determines whether a Charging Control Request (CCR) trigger is required to be transmitted to the OCS 312 for charging the call.
  • CCR Charging Control Request
  • This configuration is customizable by the service provider utilizing the user interface module 220, allowing service providers to define charging triggers according to their business requirements.
  • the system 108 transmits the CCR trigger to the OCS 312 over the Diameter interface and the OCS 312 performs charging calculations based on the received information pertaining to at least one of a call service type and a call service request and provides a Diameter Credit Control Answer (CCA) response indicating the charging status and valuation of the call.
  • CCA Diameter Credit Control Answer
  • the system 108 determines the call behavior. This call behavior is configurable by the service provider and can be tailored to specific diameter response codes.
  • the system 108 includes rules which allows service providers to define actions such as call continuation, call denial, call denial with announcement, or call continuation with announcement. These actions are associated with different diameter response codes, ensuring flexible control over call handling. For example, let us consider that the system 108 receives a Diameter error response with code 5030. The service provider configures different actions based on the diameter error response with code 5030. If service provider configures system 108 utilizing the user interface module 220 to ignore the error, the system 108 will disregard the error and continue the call. Alternatively, if service provider configures system 108 to reject the call, the system 108 will terminate the call.
  • the system 108 includes rules which are configured at run time by the service providers. These rules facilitate service providers to control the charging process and the call behavior. For example, the service provider configures the system 108 to transmit the Charging Control Request (CCR) triggers for a particular service type such as society centrex calls. In other words, the system 108 will only charge for a particular service type requested by the user based on the configuration performed by the service provider utilizing the user interface module 220.
  • CCR Charging Control Request
  • FIG. 4 is a flow diagram of a method 400 for managing call charging in a network 106, according to one or more embodiments of the present invention. For the purpose of description, the method is described with the embodiments as illustrated in FIG. 2 and should nowhere be construed as limiting the scope of the present disclosure.
  • the method 400 includes the step of receiving a call request from an at least one User Equipment 102 via an interface.
  • transceiver 206 of the processor 202 is configured to receive a call transmitted from the UE 102. The call request is received utilizing a Session Initiation Protocol (SIP).
  • SIP Session Initiation Protocol
  • the method 400 includes the step of retrieving information pertaining to at least one of a call service type and a call service request from the received call request.
  • the extraction unit 208 of the processor 202 is configured to retrieve information from the received call request.
  • the call service type is one of an originating call and a terminating call.
  • the call service request is one of at least a toll-free number dialing, Internet Protocol (IP) centrex services, and service for trunk users.
  • IP Internet Protocol
  • the method 400 includes the step of determining if a Charging Control Request (CCR) trigger is required to be transmitted to an Online Charging System (OCS) for charging the received call request.
  • CCR Charging Control Request
  • OCS Online Charging System
  • the determination unit 210 determines if CCR trigger is required to be transmitted to an OCS 312 subsequent to checking the set of predefined conditions which are dependent on parameters such as service type, Closed User Group, and SIP method.
  • the set of predefined conditions include a first condition to check information retrieved from the call received in order to identify which service types are required for the user and to determine whether the CCR trigger is required to be transmitted for the identified service type based on the customization done by the service provider.
  • the determination unit 210 identifies the required service type and checks whether the service provider had provided customization utilizing the user interface module 220 related to charging for that specific service type based on which the determination unit 210 determines if there is a need to transmit a CCR for the required service type .
  • the set of predefined conditions further include a second condition in order to determine a call type of an ongoing call, whether it is at least one of, a Closed User Group (CUG) class, an INTER call type, an INTRA call type or an Outside call type and to determine whether a Ro trigger is configured for the identified service type.
  • CCG Closed User Group
  • the set of predefined conditions further include a third condition to check which type of SIP invite is received at the system 108, which includes at least one of, an invite request and update request in the call request and to determine the Ro trigger corresponding to the SIP invite received is enabled or disabled based on the customization done by the service provider.
  • the Closed User group is a supplementary service provided by the service providers to mobile subscribers/users who can make and receive calls from any member associated within the group.
  • the INTRA call is a type of an ongoing call which is considered as the local call while INTER call is a type of an ongoing call which is considered as the long-distance call.
  • the method 400 includes the step of transmitting the CCR trigger to the OCS on determination that the CCR trigger is required to be transmitted via a Diameter Routing Agent (DRA). Subsequent to checking the set of predefined conditions by the determination unit 210, the transceiver 206 transmits the CCR trigger to the OCS 312 via a Diameter Routing Agent (DRA) utilizing a diameter interface for charging the call.
  • DRA Diameter Routing Agent
  • the method 400 includes the step of determining a Credit Control Answer (CCA) utilizing the information retrieved from the received call request to indicate a charging status and a valuation of the call request, thereby managing call charging in the network.
  • CCA Credit Control Answer
  • the OCS 312 performs charging calculations based on the received information from the received call request and provides a Diameter Credit Control Answer (CCA) response indicating the charging status and valuation of the call.
  • the system 108 evaluates the diameter responses received from the OCS 312 to make decisions regarding call continuation or denial. For example, the system 108 receives a diameter error response with code 5030.
  • the service provider configures different actions utilizing the user interface module 220 based on the diameter error response. If service provider configures to ignore the error, the system 108 will disregard the error and continue the call. Alternatively, if service provider configures to reject the call, the system 108 will terminate the call and may play an announcement to the calling party such as UE 102.
  • the described method provides service providers with the ability to customize and configure the charging mechanism, call behavior, and SIP responses within the system 108.
  • This customization offers tailored and flexible call charging support based on the call service types, the SIP methods, and the diameter responses.
  • the system 108 ensures secure and reliable communication with the OCS 312, facilitating efficient charging control and call handling.
  • the runtime control and flexibility empower service providers, eliminating the need for extensive backend development or coding.
  • FIG. 5 is a signal flow diagram illustrating the system for managing call charging in a network, according to one or more embodiments of the present disclosure.
  • step 502 the user initiates a call request via the UE 102.
  • the transceiver 206 of the processor 205 receives the call request initiated by the user and forwards the call request to the extraction unit 208.
  • the extraction unit 208 retrieves information pertaining to at least one of a call service type and a call service request from the received call request and transmits a determination request to the determination unit 210.
  • the determination unit 210 determines a Charging Control Request (CCR) trigger is required to be transmitted to an Online Charging System (OCS) 312 for charging the received call request and transmits a response to the transceiver 206.
  • CCR Charging Control Request
  • OCS Online Charging System
  • the transceiver 206 transmits the CCR trigger to the OCS 312 via a Diameter Routing Agent (DRA) 310.
  • DRA Diameter Routing Agent
  • the OCS 312 transmits a response to the determination unit 206.
  • the response is a diameter response related to the call request.
  • the response indicates a charging status and a valuation of the call request.
  • the determination unit 210 receives the response from the OCS 312 and transmits a response to the transceiver 206 subsequent to determining a call behavior applicable to the received call request.
  • the call behavior is customizable by a service provider based on a response received from the OCS 312 and the call service type. Further, the determination unit 210 applies the determined call behavior on the received call request.
  • the transceiver 206 transmits the applied call behavior on the received call request which is related to call continuation of the call or the denial of the call.
  • the present invention further discloses a non-transitory computer-readable medium having stored thereon computer-readable instructions.
  • the computer- readable instructions are executed by the processor 202.
  • the processor 202 is configured to receive a call request from an at least one User Equipment via an interface.
  • the processor 202 is further configured to retrieve information pertaining to at least one of a call service type and a call service request from the received call request.
  • the processor 202 is further configured to determine if a Charging Control Request (CCR) trigger is required to be transmitted to an Online Charging System (OCS) 312 for charging the received call request.
  • CCR Charging Control Request
  • OCS Online Charging System
  • the processor 202 is further configured to transmit the CCR trigger to the OCS 312 on determination that the CCR trigger is required to be transmitted via a Diameter Routing Agent (DRA) 310.
  • the processor 202 is further configured to determine a Credit Control Answer (CCA) utilizing the information retrieved to indicate a charging status and a valuation of the call request, thereby managing call charging in the network.
  • CCA Credit Control Answer
  • the invention provides customized call charging support tailored to the specific business needs of enterprise users. Further, different types of subscribers can be charged differently, allowing service providers to offer flexible charging options based on service types and user categories. Further, this customization capability ensures that each enterprise user receives charging treatment appropriate for their requirements. Further, the invention enables service providers to govern call behavior based on diameter responses received from the Online Charging System (OCS). By configuring the system, service providers can define actions such as call continuation, call denial, call denial with announcement, or call continuation with announcement. This kind of flexibility empowers service providers to handle calls in a manner that aligns with their specific business policies and requirements.
  • OCS Online Charging System
  • service providers can map Session Initiation Protocol (SIP) error responses to specific diameter responses, ensuring consistent and appropriate handling of call-related events.
  • SIP Session Initiation Protocol
  • This mapping capability of the invention allows service providers to customize SIP error responses according to their preferences and requirements. By mapping the appropriate SIP error response based on the Diameter response received, service providers can ensure seamless call handling and enhance the overall user experience.
  • the invention eliminates the need for extensive backend development or coding.
  • the service providers can dynamically configure the system parameters and rules, providing runtime control and flexibility over the charging process, call behavior, and SIP responses. This streamlines the customization process and empowers service providers to adapt their charging mechanisms and call handling in real-time, without requiring significant system modifications.
  • service providers can offer enhanced service differentiation to their enterprise users.
  • service providers can provide unique pricing structures, packages, or features for each service category, further strengthening their value proposition and meeting the diverse needs of their customers.
  • 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.
  • UE User Equipment

Landscapes

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

Abstract

La présente invention concerne un système (108) et un procédé (400) de gestion de facturation d'appel dans un réseau (106), le procédé (400) permettant à des fournisseurs de services de configurer et de personnaliser un mécanisme de facturation, un comportement d'appel et des réponses de protocole d'ouverture de session (SIP) à l'intérieur du système (108). Le système (108) facilite l'interaction entre l'utilisateur et le système de facturation en ligne (OCS) (312) par l'intermédiaire de l'agent de routage de diamètre (DRA) (310) sur une interface de diamètre. Les fournisseurs de services peuvent configurer des paramètres et des règles à l'intérieur du système (108) pour commander le processus de facturation et le comportement d'appel en fonction d'un type de service, de procédés SIP et des réponses de diamètre. Le système (108) évalue les réponses de diamètre provenant de l'OCS (312) pour prendre des décisions concernant la continuation d'appel ou le refus, ce qui permet une gestion d'appel flexible. De plus, des fournisseurs de services mettent en correspondance des réponses d'erreur SIP avec des réponses de diamètre spécifiques, ce qui permet d'assurer une gestion d'événement liée à un appel cohérente.
PCT/IN2024/050974 2023-07-03 2024-06-27 Procédé et système de gestion de facturation d'appel dans un réseau Ceased WO2025008976A1 (fr)

Applications Claiming Priority (2)

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

Publications (1)

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

Family

ID=94171635

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IN2024/050974 Ceased WO2025008976A1 (fr) 2023-07-03 2024-06-27 Procédé et système de gestion de facturation d'appel dans un réseau

Country Status (1)

Country Link
WO (1) WO2025008976A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2086164A1 (fr) * 2008-02-03 2009-08-05 Huawei Technologies Co., Ltd. Système de chargement, appareil et procédé
US8620263B2 (en) * 2010-10-20 2013-12-31 Tekelec, Inc. Methods, systems, and computer readable media for diameter routing agent (DRA) based credit status triggered policy control

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2086164A1 (fr) * 2008-02-03 2009-08-05 Huawei Technologies Co., Ltd. Système de chargement, appareil et procédé
US8620263B2 (en) * 2010-10-20 2013-12-31 Tekelec, Inc. Methods, systems, and computer readable media for diameter routing agent (DRA) based credit status triggered policy control

Similar Documents

Publication Publication Date Title
CN102461111B (zh) 用于实现电话服务的计算机实现的方法和设备
US12132867B2 (en) Universal ring free
US10575146B2 (en) Method and apparatus relating to online charging in an IP multimedia subsystem
US20140220932A1 (en) Network Servers, Systems, and Methods for Multiple Personas on a Mobile Device
CA2904902C (fr) Systemes et procedes de fourniture de services de communication
US8332481B2 (en) Systems and methods for transmitting subject line messages
US20050240520A1 (en) Charging in communication networks
US9854102B2 (en) Systems and methods of providing communications services
EP2963957B1 (fr) Procédé et dispositif pour exécuter un appel en liant un client à un terminal
CN105847284B (zh) 一种通信服务处理方法、装置及以及服务器
WO2025008976A1 (fr) Procédé et système de gestion de facturation d'appel dans un réseau
US20050143050A1 (en) Method for billing a communications link between communications terminals
US10973059B2 (en) Systems and methods of providing communications services
CN101365021B (zh) 用于连接不同种类网络的系统和方法
JP2025512627A (ja) Ｆｉｘｅｄ ｍｏｂｉｌｅ ｃｏｎｖｅｒｇｅｎｃｅサービスを提供するためのシステムおよび方法
US8724783B1 (en) Providing access to communication plans via multiple access methods
US8219449B2 (en) Communication methods and systems
US20130114590A1 (en) Systems and methods of providing communications services
WO2025052471A1 (fr) Système et procédé permettant de gérer un appel entre un utilisateur et un tiers
CN101278273B (zh) 政策引擎
US9148508B2 (en) Systems and methods of intercepting telephony communications to provide information to communicants
WO2025094201A2 (fr) Système et procédé de gestion de demandes de service dans un réseau
WO2025008962A1 (fr) Système et procédé de routage d'un appel international
WO2025013014A1 (fr) Procédé et système de facturation d'un utilisateur dans un réseau de télécommunication
WO2025008967A1 (fr) Système et procédé de gestion d'une demande d'appel

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: 24835697

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2024835697

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: 2024835697

Country of ref document: EP

Effective date: 20260203