Search

EP-4740688-A1 - METHOD AND SYSTEM FOR TRANSMITTING A SESSION INITIATION PROTOCOL ERROR RESPONSE TO A TARGET NETWORK-NODE

EP4740688A1EP 4740688 A1EP4740688 A1EP 4740688A1EP-4740688-A1

Abstract

The present disclosure relates to a method [400] and a system [300] for transmitting a Session Initiation Protocol (SIP) error response to a target node in a network The method comprises receiving a list of Integrated Services Digital Network User Part (ISUP) cause codes, a list of Session Initiation Protocol (SIP) error codes and a list of SIP error responses; mapping, by a processing unit [304] each ISUP cause code with the one or more SIP error codes; detecting by the processing unit [304], a rejected call; identifying a rejected call cause code associated with the rejected call; determining a cause code status associated with the rejected call cause code, identifying, by the processing unit [304], a target ISUP cause code, generating, the SIP error response associated with the target ISUP cause code; and transmitting, by the transceiver unit [302], the SIP error response.

Inventors

  • SINHA, ANURAG
  • SAGAR, Gautam
  • Kelkar, Priti
  • KUMAR, ABHAY
  • Solanki, Mehul
  • BHATNAGAR, AAYUSH
  • Bisht, Birendra Singh
  • Singh, Harbinder Pal
  • REDDY, P R Srikanth
  • BAROLIYA, Rakesh

Assignees

  • Jio Platforms Limited

Dates

Publication Date
20260513
Application Date
20240705

Claims (16)

  1. We Claim: 1. A method [400] for transmitting a Session Initiation Protocol (SIP) error response to a target node in a network, the method comprising: - receiving, by a transceiver unit [302] via an interface, at least one of: a list of Integrated Services Digital Network User Part (ISUP) cause codes, a list of Session Initiation Protocol (SIP) error codes and a list of SIP error responses, wherein each SIP error code from the list of SIP error codes is associated with one or more SIP error responses from the list of SIP error responses; - mapping, by a processing unit [304] at a Breakout Gateway Control Function (BGCF) node [504] in the network, each ISUP cause code from the list of ISUP cause codes with the one or more SIP error codes, wherein said each ISUP cause code is mapped with at least the SIP error response associated with the one or more SIP error codes; - detecting, by the processing unit [304] at a Media Gateway Control Function (MGCF) node [506] in the network, a rejected call from a user equipment in the network; - identifying, by the processing unit [304], a rejected call cause code associated with the rejected call; - determining, by the processing unit [304], a cause code status associated with the rejected call cause code based on matching the rejected call cause code and the list of ISUP cause codes, wherein the cause code status is one of a positive cause code status and a negative cause code status; - identifying, by the processing unit [304], a target ISUP cause code from the list of ISUP cause codes based on the positive cause code status; - generating, by the processing unit [304] at the BGCF node [504] in the network, the SIP error response associated with the target ISUP cause code based on identifying the SIP error code associated with the target ISUP cause code; and - transmitting, by the transceiver unit [302] from the BGCF node [504] to the target node in the network, the SIP error response based on the generating the SIP error response.
  2. 2. The method [400] as claimed in claim 1, wherein the positive cause code status is determined in an event the rejected call cause code is a successful match with at least one of the ISUP cause code from the list of ISUP cause codes, and wherein the negative cause code status is determined in an event the rejected call cause code is an unsuccessful match with each of the ISUP codes from the list of ISUP cause codes.
  3. 3. The method [400] as claimed in claim 2, wherein the method [400] further comprises transmitting, by the transceiver unit [302] from the BGCF node [504], the rejected call SIP error response, in an event the negative cause code status is detected.
  4. 4. The method [400] as claimed in claim 1, wherein the generating the SIP error response associated with the target ISUP cause code based on the identifying the SIP error code associated with the target ISUP cause code further comprises: - changing, by the processing unit [304], the rejected call SIP error response to the SIP error response associated with the target ISUP cause code.
  5. 5. The method [400] as claimed in claim 1, wherein identifying the rejected call cause code associated with the rejected call from the user equipment in the network further comprises determining, by the processing unit [304], an available rejected cause code status, wherein the available rejected cause code status is determined based on receiving of the rejected call cause code via the Session Initiation Protocol (SIP) reason header.
  6. 6. The method [400] as claimed in claim 5, wherein the rejected call SIP error response is transmitted by the transceiver unit [302] from the BGCF node [504], in an event of determining an unsuccessful receiving of the rejected call cause code via the Session Initiation Protocol (SIP) reason header.
  7. 7. The method [400] as claimed in claim 1, wherein the rejected call cause code comprises a rejected call SIP error response.
  8. 8. A system [300] for transmitting a Session Initiation Protocol (SIP) error response to a target node in a network, the system [300] comprises: - a transceiver unit [302], wherein the transceiver unit [302] is configured to: ^ receive, via an interface, a list of Integrated Services Digital Network User Part (ISUP) cause codes, a list Session Initiation Protocol (SIP) error codes and a list of SIP error responses, wherein each SIP error code from the list of SIP error codes is associated with one or more SIP error responses from the list of SIP error responses; and a processing unit [304] connected to at least the transceiver unit [302], wherein the processing unit [304] configured to: ^ map, at a Breakout Gateway Control Function (BGCF) node [504] in the network, each ISUP cause code from the list of ISUP cause codes with the one or more SIP error codes, wherein said each ISUP cause code is mapped with at least the SIP error response associated with the one or more SIP error codes, ^ detect, at a Media Gateway Control Function (MGCF) node [506] in the network, a rejected call from a user equipment in the network, ^ identify, a rejected call cause code associated with the rejected call; ^ determine, a cause code status associated with the rejected call cause code based on matching the rejected call cause code and the list of ISUP cause codes, wherein the cause code status is one of a positive cause code status and a negative cause code status, ^ identify, a target ISUP cause code from the list of ISUP cause codes based on the positive cause code status, ^ generate, at the BGCF node [504] in the network, the SIP error response associated with the target ISUP cause code based on identifying the SIP error code associated with the target ISUP cause code; and wherein the transceiver unit [302] is further configured to: ^ transmit, from the BGCF node [504] to the target node in the network, the SIP error response based on the generated SIP error response.
  9. 9. The system [300] as claimed in claim 8, wherein the positive cause code status is determined in an event the rejected call cause code is a successful match with at least one of the ISUP cause code from the list of ISUP cause codes, and wherein the negative cause code status is determined in an event the rejected call cause code is an unsuccessful match with each of the ISUP codes from the list of ISUP cause codes.
  10. 10. The system [300] as claimed in claim 9, wherein the transceiver unit [302] is further configured to transmit, from the BGCF node [504], the rejected call SIP error response, in an event the negative cause code status is detected.
  11. 11. The system [300] as claimed in claim 8, wherein for generating the SIP error response associated with the target ISUP cause code based on the identifying the SIP error code associated with the target ISUP cause code, the processing unit [304] is further configured to: - change the rejected call SIP error response to the SIP error response associated with the target ISUP cause code.
  12. 12. The system [300] as claimed in claim 8, wherein to identify the rejected call cause code associated with the rejected call from the user equipment in the network, the processing unit [304] is further configured to determine an available rejected cause code status, wherein the available rejected cause code status is determined based on receiving the rejected call cause code via the Session Initiation Protocol (SIP) reason header.
  13. 13. The system [300] as claimed in claim 12, wherein the rejected call SIP error response is transmitted by the transceiver unit [302] from the BGCF node [504] in an event of determining an unsuccessful receiving of the rejected call cause code via the Session Initiation Protocol (SIP) reason header.
  14. 14. The system [300] as claimed in claim 8, wherein the rejected call cause code comprises a rejected call SIP error response.
  15. 15. A User Equipment (UE) for transmitting a Session Initiation Protocol (SIP) error response to a target node in a network, the UE comprising: - a memory; and - a processor coupled to the memory, wherein the processor is configured to: o transmit, to a system [300] via an interface, at least one of: a list of Integrated Services Digital Network User Part (ISUP) cause codes, a list of Session Initiation Protocol (SIP) error codes and a list of SIP error responses, wherein each SIP error code from the list of SIP error codes is associated with one or more SIP error responses from the list of SIP error responses, and o receive, from the system [300], an SIP error response based on at least one of the list of ISUP cause codes, a list of SIP error codes and a list of SIP error responses, wherein the SIP error response is received based on: mapping, by the system [300] at a Breakout Gateway Control Function (BGCF) node [504] in the network, each ISUP cause code from the list of ISUP cause codes with the one or more SIP error codes, wherein said each ISUP cause code is mapped with at least the SIP error response associated with the one or more SIP error codes, detecting, by the system [300] at a Media Gateway Control Function (MGCF) node [506] in the network, a rejected call from a user equipment in the network, identifying, by the system [300], a rejected call cause code associated with the rejected call, determining, by the system [300], a cause code status associated with the rejected call cause code based on matching the rejected call cause code and the list of ISUP cause codes, wherein the cause code status is one of a positive cause code status and a negative cause code status, identifying, by the system [300], a target ISUP cause code from the list of ISUP cause codes based on the positive cause code status, generating, by the system [300] at the BGCF node [504] in the network, the SIP error response associated with the target ISUP cause code based on identifying the SIP error code associated with the target ISUP cause code, and transmitting, by the system [300] from the BGCF node [504] to the target node in the network, the SIP error response based on the generating the SIP error response.
  16. 16. A non-transitory computer-readable storage medium storing instruction for transmitting a Session Initiation Protocol (SIP) error response to a target node in a network, the storage medium comprising executable code which, when executed by one or more units of a system, causes: ^ a transceiver unit [302] to receive, via an interface, a list of Integrated Services Digital Network User Part (ISUP) cause codes, a list Session Initiation Protocol (SIP) error codes and a list of SIP error responses, wherein each SIP error code from the list of SIP error codes is associated with one or more SIP error responses from the list of SIP error responses; ^ a processing unit [304] to map, at a Breakout Gateway Control Function (BGCF) node [504] in the network, each ISUP cause code from the list of ISUP cause codes with the one or more SIP error codes, wherein said each ISUP cause code is mapped with at least the SIP error response associated with the one or more SIP error codes; ^ the processing unit [304] to detect at a Media Gateway Control Function (MGCF) node [506] in the network, a rejected call from a user equipment in the network; ^ the processing unit [304] to identify, a rejected call cause code associated with the rejected call, wherein the rejected call cause code comprises a rejected call SIP error response; ^ the processing unit [304] to determine, a cause code status associated with the rejected call cause code based on matching the rejected call cause code and the list of ISUP cause codes, wherein the cause code status is one of a positive cause code status and a negative cause code status; ^ the processing unit [304] to identify, a target ISUP cause code from the list of ISUP cause codes based on the positive cause code status; ^ the processing unit [304] to generate, at the BGCF node [504] in the network, the SIP error response associated with the target ISUP cause code based on identifying the SIP error code associated with the target ISUP cause code; and ^ the transceiver unit [302] to transmit, from the BGCF node [504] to the target node in the network, the SIP error response based on the generated SIP error response.

Description

METHOD AND SYSTEM FOR TRANSMITTING A SESSION INITIATION PROTOCOL ERROR RESPONSE TO A TARGET NETWORK-NODE TECHNICAL FIELD [0001] Embodiments of the present disclosure generally relate to network management systems. More particularly, embodiments of the present disclosure relate to methods and systems for transmitting a Session Initiation Protocol (SIP) error response to a target node in a network. BACKGROUND [0002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art. [0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. The third generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users. [0004] In the field of telecommunication, an offnet call refers to telephone call made between users who are connected to different telecommunications networks or operators. For example, if the user uses one mobile network such as network A and calls someone who uses a different mobile network such as network B, that call is considered an offnet call. The offnet call typically involve routing through various network elements and interfaces to connect the caller to the recipient, often involving interconnection agreements between different operators to facilitate seamless communication across networks. [0005] Further, the present solutions have several shortcomings such as inability to effectively manage offnet calls in telecommunications networks, particularly inaccurately diagnosing and addressing call failures associated with the offnet calls. The current setup, characterized by uniform SIP error code dispatch for all ISUP failures, such setup hampers specific issue identification and resolution. This limitation prolongs downtime, diminishes network performance, and underscores the need for enhanced error code differentiation and diagnostic capabilities. [0006] Firstly, offnet calls originate from the Breakout Gateway Control Function (BGCF) and are directed to the Media Gateway Control Function (MGCF) via a Mj interface, which typically uses the Session Initiation Protocol (SIP) for communication. From there, the MGCF routes the call to the intended recipient's operator over the ISUP (Integrated Services Digital Network User Part) interface. The Mj interface refers to a specific interface used in telecommunications networks, particularly in the context of the IP Multimedia Subsystem (IMS) architecture. The Mj interface is responsible for facilitating communication between the Breakout Gateway Control Function (BGCF) and the Media Gateway Control Function (MGCF). [0007] However, if something goes wrong during this process and the offnet call encounters a failure while trying to connect via the ISUP interface, the MGCF takes action by rejecting the call back at the Mj interface, using a specific SIP error code like a 480 response to indicate the failure. The ISUP interface, also known as the ISDN User Part interface, is a key component in telecommunications networks, particularly in the context of circuit-switched networks like the Public Switched Telephone Network (PSTN). ISUP facilitates the signalling necessary for the setup, maintenance, and teardown of voice calls between different network switches. [0008] Hence, the current telecommunication architectures are unable to effectively manage offnet calls in telecommunications networks, particularly in accurately diagnosing and addressing call failures. The current available setup, characterized by uniform SIP error code dispatch for all ISUP failures, hampers specific issue identification and resolution. This limitation prolongs downtime, diminishes network performance. [0009] Therefore, there is a need to provide a method and system for transmitting a Session Initiation