Search

EP-4740565-A1 - METHOD AND SYSTEM FOR RECOVERY OF SUBSCRIBER SERVICES

EP4740565A1EP 4740565 A1EP4740565 A1EP 4740565A1EP-4740565-A1

Abstract

The present disclosure relates to a method and a system for recovery of subscriber services The method includes detecting, by a detecting unit [302] via BSF [508], a call failure in a network. Further invoking, by an invoking unit [304] via BSF [508], an API call in at least one of a unified data management (UDM) [124] system, and home subscriber server to deregister at least one subscriber from the network. Furthermore, determining, by a determining unit [306] via the at least one of UDM [124], and HSS, attach status of the subscriber. Furthermore, transmitting, by a transmitting unit [308], the corresponding cause over non-access stratum (NAS) by at least one of the AMF [506], and the MME [502]. Further re-attaching, by an attaching unit [310], based on the attach status of the subscriber, the subscriber to the network after successful detachment.

Inventors

  • SINGH, MUKESH
  • BHATNAGAR, AAYUSH
  • Agrahari, Nilesh
  • MORE, AJAY
  • Adate, Snehal
  • Arumugam, Yoganandan
  • Dhiman, Anshul

Assignees

  • Jio Platforms Limited

Dates

Publication Date
20260513
Application Date
20240612

Claims (20)

  1. 1. A method for recovery of subscriber services, the method comprising the steps of: detecting, by a detecting unit [302] via a binding support function (BSF) [508], a call failure in a network; invoking, by an invoking unit [304] via the BSF [508], an application programming interface (API) call in at least one of a unified data management (UDM) [124] system, and home subscriber server (HSS) to deregister at least one subscriber from the network; determining, by a determining unit [306] via the at least one of UDM [124], and HSS, attach status of the subscriber, wherein if the subscriber is attached to a 4G network, sending a deregistration notification to a mobility management entity (MME) [502] with a cause of 'Re-Attach required', by the HSS, and wherein if the subscriber is attached to a 5G network, sending a deregistration notification to an access and mobility management function (AMF) [506] with a cause of reregistration required by the UDM [124]; transmitting, by a transmitting unit [308], the corresponding cause over non-access stratum (NAS) by at least one of the AMF [506], and the MME [502]; and re-attaching, by an attaching unit [310], based on the attach status of the subscriber, the subscriber to the network after successful detachment.
  2. 2. The method as claimed in claim 1, wherein the call failure occurs due to an error in an authorization and authentication (AA) ANSWER system from one or more network functions, detected at a binding support function (BSF) [508] end.
  3. 3. The method as claimed in claim 2, wherein the error is IP-CAN_Session_Not_A vailable (5065) error.
  4. 4. The method as claimed in claim 2, wherein the one or more network functions comprise at least one of a policy and charging rules function (PCRF) [510], and policy control function (PCF) [510],
  5. 5. The method as claimed in claim 1 , the method comprises restoring, via a restoring unit [312], high-speed internet (HSI) and voice video and multimedia (VVM) services by the network.
  6. 6. The method as claimed in claim 1, wherein the API call comprises at least one of a subscription permanent identifier (SUPI), and international mobile subscriber identity (IMSI) as a query parameter.
  7. 7. The method as claimed in claim 1, wherein if the subscriber is connected to the 4G network, the HSS sends a cancel location request (CLR) to the MME [502],
  8. 8. The method as claimed in claim 1, wherein if the subscriber is attached to the 5G network, the UDM [124] sends the deregistration notification to the AMF [506],
  9. 9. The method as claimed in claim 1, wherein determining the attach status of the subscriber comprises checking, by the determining unit [306], if a user equipment (UE) [102] associated with the subscriber is attached to at least one of 4G network, and 5G network.
  10. 10. The method as claimed in claim 1, wherein the call failure occurs due to establishment or maintenance of a pre-established internet protocol connectivity access network (IP-CAN) session.
  11. 11. A system for recovery of subscriber services, said system comprises: a detecting unit [302] configured to detect, via a binding support function (BSF) [508], a call failure in a network; an invoking unit [304] configured to invoke, via the BSF [508], an application programming interface (API) call in at least one of a Unified Data Management (UDM) [124] system and home subscriber server (HSS) to deregister at least one subscriber from the network; a determining unit [306] configured to determine, via the at least one of UDM [124], and HSS, attach status of the subscriber, wherein if the subscriber is attached to a 4G network, send a deregistration notification to a mobility management entity (MME) [502] with a cause of 'Re-Attach required', by the HSS, and wherein if the subscriber is attached to a 5G network, send a deregistration notification to an access and mobility management function (AMF) [506] with a cause of Reregistration required by the UDM [124]; a transmitting unit [308] configured to transmit the corresponding cause over non- access stratum (NAS) by at least one of the AMF [506], and the MME [502]; and an ataching unit [310] configured to re-atach the subscriber to the network based on the atach status of the subscriber after successful detachment.
  12. 12. The system [300] as claimed in claim 11, wherein the call failure occurs due to an error in an authorization and authentication (AA) ANSWER system from one or more network functions, detected at a binding support function (BSF) [508] end.
  13. 13. The system [300] as claimed in claim 12, wherein the error is IP- CAN_Session_Not_Available (5065) error.
  14. 14. The system [300] as claimed in claim 12, wherein the one or more network functions comprise at least one of a policy and charging rules function (PCRF) [510] and policy control function (PCF) [510],
  15. 15. The system [300] as claimed in claim 11, comprising a restoring unit [312] is configured to restore, via the network, high-speed internet (HSI) and voice video and multimedia (VVM) services.
  16. 16. The system [300] as claimed in claim 11, wherein the API call comprises at least one of a subscription permanent identifier (SUPI), and international mobile subscriber identity (IMSI) as a query parameter.
  17. 17. The system [300] as claimed in claim 11, wherein if the subscriber is connected to the 4G network, the HSS sends a cancel location request (CLR) to the MME [502],
  18. 18. The system [300] as claimed in claim 11, wherein if the subscriber is atached to the 5G network, the UDM [124] sends the deregistration notification to the AMF [506],
  19. 19. The system [300] as claimed in claim 11, wherein for the determination of the attach status of the subscriber the determining unit [306] is configured to check if a user equipment (UE) [102] associated with the subscriber is attached to at least one of 4G network, and 5G network.
  20. 20. The system [300] as claimed in claim 11, wherein the call failure occurs due to at least one of establishment, and maintenance of a pre-established internet protocol connectivity access network (IP-CAN) session.

Description

METHOD AND SYSTEM FOR RECOVERY OF SUBSCRIBER SERVICES FIELD OF THE DISCLOSURE [001] The present disclosure generally relates to network performance management systems. More particularly, relates to a method and system for the recovery of subscriber services. BACKGROUND [002] 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. [003] 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. 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. [004] Currently, whenever there is a network failure, users manually intervene to restore the network and regain access to various network services. This process can be time-consuming and prone to human error. Additionally, the current methods and systems lack mechanisms for immediate detection and recovery from network failures, such as failure of the network caused due to IP-CAN_Session_Not_Available (5065) error. This leads to service downtime, which can be highly inconvenient for users. Moreover, the existing systems do not provide any efficient way of handling subscriber deregistration and re-registration during network failures. The existing systems handle network failures differently based on the type of subscriber, leading to inconsistent service quality. Consequently, there are no solutions for automatic recovery from specific network failures in the existing systems. [005] Therefore, in light of the foregoing discussion, there exists a need to overcome the aforementioned drawbacks by providing an improved method and system that can efficiently handle network failures to ensure continuous and reliable network services for users. SUMMARY [006] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter. [007] An aspect of the present disclosure may relate to a method for recovery of subscriber services. The method includes detecting, by a detecting unit via a binding support function (BSF), a call failure in a network. Further, the method encompasses invoking, by an invoking unit via the BSF, an application programming interface (API) call in at least one of a unified data management (UDM) system, and home subscriber server (HSS) to deregister at least one subscriber from the network. The method further includes determining, by a determining unit via the at least one of UDM, and HSS systems, attach status of the subscriber. If the subscriber is attached to a 4G network, sending a deregistration notification to a mobility management entity (MME) with a cause of 'Re-Attach required', by the HSS, and wherein if the subscriber is attached to a 5G network, sending a deregistration notification to an access and mobility management function (AMF) with a cause of Re-registration required by the UDM. Furthermore, the method encompasses transmitting, by a transmitter unit, the corresponding cause over non-access stratum (NAS) by at least one of the AMF, and the MME. The method further includes re-attaching, by an attaching unit, based on the attach status of the subscriber, the subscriber to the network after successful detachment. [008] In an exemplary aspect of the present disclosure, the call failure occurs due to an error in an authorization and authentication (AA) ANSWER system from one or more network functions, detected at a binding support function (BSF) end. [009] In an exemplary aspect of the present disclosure, the error is an IP- CAN_Session_Not_Available (5065) error. [0010] In an exemplary aspect of the present disclosure, the one or more network functions comprise at leas