Search

EP-4740503-A1 - METHOD AND SYSTEM FOR MANAGING CALL CHARGING IN A NETWORK

EP4740503A1EP 4740503 A1EP4740503 A1EP 4740503A1EP-4740503-A1

Abstract

The present invention relates to a system (108) and a method (400) for managing call charging in a network (106) The method (400) enables service providers to configure and customize a charging mechanism, a call behavior, and Session Initiation Protocol (SIP) responses within the system (108). The system (108) facilitates the interaction between the user and the Online Charging System (OCS) (312) through the Diameter Routing Agent (DRA) (310) over a diameter interface. Service providers can configure parameters and rules within the system (108) to control the charging process and call behavior based on a service type, SIP methods, and the diameter responses. The system (108) evaluates the diameter responses from the OCS (312) to make decisions regarding call continuation or denial, allowing flexible call handling. Additionally, service providers map SIP error responses to specific diameter responses, ensuring consistent call-related event handling.

Inventors

  • BHATNAGAR, AAYUSH
  • BISHT, BIRENDRA
  • SINGH, HARBINDER
  • GUPTA, SANDEEP
  • DAS, Raghav
  • Reddy, Srikanth P
  • RANJAN, Surabhi
  • Kelkar, Priti

Assignees

  • Jio Platforms Limited

Dates

Publication Date
20260513
Application Date
20240627

Claims (20)

  1. 1. A method (400) of managing call charging in a network (106), the method (400) comprises the steps of: receiving, by one or more processors (202), a call request from an at least one User Equipment (102) via an interface; retrieving, by the one or more processors (202), information pertaining to at least one of a call service type and a call service request from the received call request; determining, by the one or more processors (202), 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; transmitting, by the one or more processors (202), 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); and determining, by the one or more processors (202), 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 (106).
  2. 2. The method (400) as claimed in claim 1, further comprising the steps of: determining, by the one or more processors (202), a call behaviour applicable to the received call request, wherein the call behaviour is customizable based on a response received from the OCS (312) and the call service type; and applying, by the one or more processors (202), the determined call behaviour to the received call request.
  3. 3. The method (400) as claimed in claim 2, wherein the call behaviour pertains to an activity which includes one of continuing the call, deny the call, deny call with announcement and continue call with announcement.
  4. 4. The method (400) as claimed in claim 1 , wherein the call service type is one of an originating call and a terminating call.
  5. 5. The method (400) as claimed in claim 1, wherein the call service request is one of at least a toll-free number dialling, Internet Protocol (IP) centrex services, and service for trunk users.
  6. 6. The method (400) as claimed in claim 1, wherein the call request is received utilizing a Session Initiation Protocol (SIP) and the CCR trigger is transmitted to the OCS (312) via the DRA (310) utilizing a diameter interface.
  7. 7. The method (400) as claimed in claim 1, wherein subsequent to checking a set of predefined conditions, the CCR trigger is transmitted to the OCS (312), 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.
  8. 8. The method (400) as claimed in claim 1, wherein in response to transmission of the CCR trigger, the method (400) further comprising the steps of: receiving, by the one or more processors (202), a diameter response from the OCS (312); mapping, by the one or more processors (202), the diameter response to a SIP response as customized by a service provider; implementing, by the one or more processors (202), the call behaviour at the at least one UE (102) based on the mapping.
  9. 9. The method (400) as claimed in claim 8, wherein the mapping of the diameter response to the SIP response is dependent on the call service type.
  10. 10. The method (400) as claimed in claim 7, wherein 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.
  11. 11. A User Equipment (UE) (102), comprising: one or more primary processors (302) communicatively coupled to one or more processors (202), the one or more primary processors (302) coupled with a memory (304), wherein said memory (304) stores instructions which when executed by the one or more primary processors (302) causes the UE (102) to: transmit a call request to the one or more processors (202) via an interface, wherein the one or more processors (202) are configured to perform the method (400) as claimed in claim 1.
  12. 12. A system (108) of managing call charging in a network (106), the system (108) comprising: a transceiver (206) configured to receive, a call request from an at least one User Equipment (102) via an interface; an extraction unit (208) configured to retrieve, information pertaining to at least one of a call service type and a call service request from the received call request; a determination unit (210) 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; the transceiver (206) 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); and the determination unit (210) 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 (106).
  13. 13. The system (108) as claimed in claim 12, wherein the determination unit (210) is further configured to: determine, a call behaviour applicable to the received call request, wherein the call behaviour is customizable based on a response received from the OCS (312) and the call service type; and apply, the determined call behaviour on the received call request.
  14. 14. The system (108) as claimed in claim 13, wherein the call behaviour pertains to an activity which includes one of continue the call, deny the call, deny call with announcement and continue call with announcement.
  15. 15. The system (108) as claimed in claim 12, wherein the call service type is one of an originating call and a terminating call.
  16. 16. The system (108) as claimed in claim 12, wherein the call service request is one of at least a toll-free number dialling, Internet Protocol (IP) centrex services, and service for trunk users.
  17. 17. The system (108) as claimed in claim 12, wherein the call request is received utilizing a Session Initiation Protocol (SIP) and the CCR trigger is transmitted to the OCS (312) via the DRA (310) utilizing a diameter interface.
  18. 18. The system (108) as claimed in claim 12, wherein subsequent to checking a set of predefined conditions, the CCR trigger is transmitted to the OCS (312) , wherein the set of pre-defined conditions are dependent on parameters including at least one of, 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.
  19. 19. The system (108) as claimed in claim 12, wherein in response to transmission of the CCR trigger: the transceiver (206) is configured to, receive, a diameter response from the OCS (312); a mapping unit (212) is configured to map, the diameter response to a SIP response as customized by a service provider; an implementation unit (214) is configured to, implement, the call behaviour at the at least one UE (102) based on the mapping.
  20. 20. The system (108) as claimed in claim 19, wherein the mapping of the diameter response to the SIP response is dependent on the call service type.

Description

METHOD AND SYSTEM FOR MANAGING CALL CHARGING IN A NETWORK FIELD OF THE INVENTION [0001] 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. BACKGROUND OF THE INVENTION [0002] 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). The Diameter interface plays a crucial role in the charging process within an IP Multimedia Subsystem (IMS) network, as it facilitates subscriber charging for various telephony services. [0003] In a standard implementation, 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. 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. [0004] However, there is a need for a customized charging support in the BTAS, considering its primary purpose as a business telephony application server catering to enterprise users. Different types of enterprise subscribers often require distinct charging schemes tailored to their specific needs. This customization adds value to the BTAS solution, enabling flexible and business-driven charging capabilities. [0005] 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. [0006] Secondly, 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. [0007] Furthermore, 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. [0008] The state of the art in telephony systems primarily focuses on standardized charging mechanisms and limited customization options. The customization provided by the BTAS allows for fine-tuning the charging process and call behaviour, thus improving the service delivery and meeting specific business requirements. [0009] There is a need for offering a customized call charging support, to address the limitations of a standard charging mechanism and thereby, provide a more adaptable and business-centric solution. The subsequent sections of this patent specification will further describe the features, implementations, and advantages of the customized charging support within the BTAS, along with relevant technical details and embodiment. SUMMARY OF THE INVENTION [0010] One or more embodiments of the present disclosure provide a method and system for managing call charging in a network. [0011] In one aspect of the present invention, a method of managing a call charging in a network is disclosed. The method 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. 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. [0012] In one embodiment, 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. [0013] In another embodiment, the call behavior pertains to an activity which includes one of continuing the call, deny the call, deny call with announcement