WO2025008902A1 - Procédé et système de récupération de services d'abonné - Google Patents

Procédé et système de récupération de services d'abonné Download PDF

Info

Publication number
WO2025008902A1
WO2025008902A1 PCT/IN2024/050797 IN2024050797W WO2025008902A1 WO 2025008902 A1 WO2025008902 A1 WO 2025008902A1 IN 2024050797 W IN2024050797 W IN 2024050797W WO 2025008902 A1 WO2025008902 A1 WO 2025008902A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
subscriber
unit
udm
attach
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/050797
Other languages
English (en)
Inventor
Mukesh Singh
Aayush Bhatnagar
Nilesh Agrahari
Ajay More
Snehal Adate
Yoganandan Arumugam
Anshul Dhiman
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 WO2025008902A1 publication Critical patent/WO2025008902A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/06—De-registration or detaching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data

Definitions

  • the present disclosure generally relates to network performance management systems. More particularly, relates to a method and system for the recovery of subscriber services.
  • 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.
  • 2G second-generation
  • 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services.
  • 4G fourth-generation
  • 5G fifth-generation
  • wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
  • 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.
  • API application programming interface
  • UDM unified data management
  • HSS home subscriber server
  • the method further includes determining, by a determining unit via the at least one of UDM, and HSS systems, attach status of the subscriber.
  • 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.
  • 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.
  • the error is an IP- CAN_Session_Not_Available (5065) error.
  • the one or more network functions comprise at least one of a policy and charging rules function (PCRF), and policy control function (PCF).
  • PCF policy and charging rules function
  • PCF policy control function
  • the method further includes restoring high-speed internet (HSI) and voice video and multimedia (VVM) services by the network.
  • HAI high-speed internet
  • VVM voice video and multimedia
  • the API call comprises at least one of a subscription permanent identifier (SUPI), and international mobile subscriber identity (IMSI) as a query parameter.
  • SUPI subscription permanent identifier
  • IMSI international mobile subscriber identity
  • the HSS sends a cancel location request (CLR) to the MME.
  • CLR cancel location request
  • the UDM sends the deregistration notification to the AMF.
  • the determining the attach status of the subscriber further comprises checking, by the determining unit, if a user equipment (UE) associated with the subscriber is attached to at least one of 4G network, and 5G network.
  • UE user equipment
  • the call failure occurs due to establishment or maintenance of a pre-established internet protocol connectivity access network (IP-CAN) session.
  • IP-CAN internet protocol connectivity access network
  • the system includes a detecting unit configured to detect, via a binding support function (BSF), a call failure in a network.
  • the system further includes an invoking unit configured to invoke, 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 system includes a determining unit configured to determine, via the at least one of UDM, and HSS system, attach status of the subscriber.
  • the system further includes a transmiting unit configured to transmit the corresponding cause over non-access stratum (NAS) by at least one of the AMF, and the MME. Furthermore, the system includes an ataching unit configured to re-atach the subscriber to the network based on the attach status of the subscriber after successful detachment.
  • MME mobility management entity
  • AMF access and mobility management function
  • the UE includes a processing unit.
  • the processing unit is configured to receive a request for deregistering of a subscriber based on detected call failure in a network, wherein if the subscriber is attached to a 4G network, a deregistration notification is sent to a mobility management entity (MME) with a cause of 're-Attach required', and wherein if the subscriber is attached to a 5G network, a deregistration notification is sent to an access and mobility management function (AMF) with a cause of re-registration required.
  • MME mobility management entity
  • AMF access and mobility management function
  • the processing unit is further configured to receive the corresponding cause over non-access stratum (NAS) from at least one of the AMF, and the MME; re-atach the subscriber to the network based on an atach status of the subscriber after successful detachment.
  • NAS non-access stratum
  • Yet another aspect of the present disclosure may relate to a non-transitory computer- readable storage medium storing instruction, the storage medium comprising executable code which, when executed by one or more units of a system, causes: a detecting unit of the system to detect, via a binding support function (BSF), a call failure in a network; an invoking unit of the system to invoke, 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; a determining unit configured to determine, via the at least one of UDM, and HSS system, atach status of the subscriber, wherein if the subscriber is atached to a 4G network, send a deregistration notification to a mobility management entity (MME) with a cause of 're-Atach required', by the HSS, and wherein if the subscriber is atached to a 5G network, send a
  • FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture.
  • 5GC 5th generation core
  • FIG. 2 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
  • FIG. 3 illustrates an exemplary block diagram of a system for recovery of subscriber services, in accordance with exemplary implementations of the present disclosure.
  • FIG. 4 illustrates a method flow diagram for recovery of subscriber services in accordance with exemplary implementations of the present disclosure.
  • FIG. 5 illustrates an exemplary process flow diagram for automated subscriber services recovery upon failure detection at network end, in accordance with exemplary embodiments of the present disclosure.
  • exemplary and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples.
  • any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art.
  • a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions.
  • a processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a (Digital Signal Processing) DSP core, a controller, a micro controller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc.
  • the processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
  • a user equipment may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure.
  • the user equipment/device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure.
  • the user device may contain at least one input means configured to receive an input from at least one of a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.
  • storage unit or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine.
  • a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media.
  • the storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.
  • interface or “user interface refers to a shared boundary across which two or more separate components of a system exchange information or data. The interface may also be referred to as set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
  • AA ANSWER refers to a response message in the Diameter protocol for providing the necessary information regarding the authentication and authorization status of a user or device.
  • the AA -ANSWER indicates whether a user or device has been successfully authenticated and authorized to access specific network services or resources. It also conveys any errors or issues encountered during the authentication and authorization process, such as the IP-CAN_Session_Not_Available (5065) error, which can trigger further network actions to maintain service continuity and network integrity.
  • an AA-Request refers to a message sent within the Diameter protocol that initiates the processes of Authentication, Authorization, and Accounting in the network.
  • the request is used by the Dynamic Resource Allocation (DRA) to communicate with the Binding Support Function (BSF), such that the subscriber's identity and permissions are verified and the resource usage is tracked.
  • DRA Dynamic Resource Allocation
  • BSF Binding Support Function
  • All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
  • DSP digital signal processor
  • ASIC Application Specific Integrated Circuits
  • FPGA Field Programmable Gate Array circuits
  • FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture, in accordance with exemplary implementation of the present disclosure.
  • the 5GC network architecture [100] includes a user equipment (UE) [102], a radio access network (RAN) [104], an access and mobility management function (AMF) [106], a Session Management Function (SMF) [108], a Service Communication Proxy (SCP) [110], an Authentication Server Function (AUSF) [112], a Network Slice Specific Authentication and Authorization Function (NSSAAF) [114], a Network Slice Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a Network Repository Function (NRF) [120], a Policy Control Function (PCF) [122], a Unified Data Management (UDM) [124], an application function (AF) [126], a User Plane Function (UPF) [128], a data network (DN) [130], wherein all the components are assumed to be connected
  • UE user equipment
  • Radio Access Network (RAN) is the part of a mobile telecommunications system that connects user equipment (UE) [102] to the core network (CN) and provides access to different types of networks (e.g., 5G network). It consists of radio base stations and the radio access technologies that enable wireless communication.
  • Access and Mobility Management Function (AMF) is a 5G core network function responsible for managing access and mobility aspects, such as UE registration, connection, and reachability. It also handles mobility management procedures like handovers and paging.
  • Session Management Function (SMF) [108] is a 5G core network function responsible for managing session-related aspects, such as establishing, modifying, and releasing sessions. It coordinates with the User Plane Function (UPF) for data forwarding and handles IP address allocation and QoS enforcement.
  • UPF User Plane Function
  • Service Communication Proxy (SCP) [110] is a network function in the 5G core network that facilitates communication between other network functions by providing a secure and efficient messaging service. It acts as a mediator for service-based interfaces.
  • AUSF Authentication Server Function
  • NSSAAF Network Slice Specific Authentication and Authorization Function
  • Network Slice Selection Function (NSSF) [116] is a network function responsible for selecting the appropriate network slice for a UE based on factors such as subscription, requested services, and network policies.
  • Network Exposure Function [118] is a network function that exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.
  • Network Repository Function (NRF) [120] is a network function that acts as a central repository for information about available network functions and services. It facilitates the discovery and dynamic registration of network functions.
  • Policy Control Function (PCF) is a network function responsible for policy control decisions, such as QoS, charging, and access control, based on subscriber information and network policies.
  • Unified Data Management [124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information.
  • Application Function (AF) is a network function that represents external applications interfacing with the 5G core network to access network capabilities and services.
  • User Plane Function [128] is a network function responsible for handling user data traffic, including packet routing, forwarding, and QoS enforcement.
  • Data Network [130] refers to a network that provides data services to user equipment (UE) in a telecommunications system.
  • the data services may include but are not limited to Internet services, private data network related services.
  • FIG. 2 illustrates an exemplary block diagram of a computing device [1000] (also referred to herein as a computer system [1000]) upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
  • the computing device [1000] may also implement a method for recovery of subscriber services utilising the system.
  • the computing device [1000] itself implements the method for recovery of subscriber services using one or more units configured within the computing device [1000], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
  • the computing device [1000] encompasses a wide range of electronic devices capable of processing data and performing computations. Examples of computing device [1000] include, but are not limited only to, personal computers, laptops, tablets, smartphones, servers, and embedded systems. The devices may operate independently or as part of a network and can perform a variety of tasks such as data storage, retrieval, and analysis. Additionally, computing device [1000] may include peripheral devices, such as monitors, keyboards, and printers, as well as integrated components within larger electronic systems, sselling their versatility in various technological applications.
  • the computing device [1000] may include a bus [1002] or other communication mechanism for communicating information, and a hardware processor [1004] coupled with bus [ 1002] for processing information.
  • the hardware processor [ 1004] may be, for example, a general- purpose microprocessor.
  • the computing device [1000] may also include a main memory [1006], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [1002] for storing information and instructions to be executed by the processor [1004],
  • the main memory [1006] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [1004],
  • Such instructions when stored in non-transitory storage media accessible to the processor [1004], render the computing device [1000] into a special-purpose machine that is customized to perform the operations specified in the instructions.
  • the computing device [1000] further includes a read only memory (ROM) [1008] or other static storage device coupled to the bus [1002] for storing static information and instructions for the processor [1004], [0067]
  • ROM read only memory
  • a storage device [1010], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [1002] for storing information and instructions.
  • the computing device [1000] may be coupled via the bus [1002] to a display [1012], such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user.
  • CTR cathode ray tube
  • LCD Liquid crystal Display
  • LED Light Emitting Diode
  • OLED Organic LED
  • An input device [1014] including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [1002] for communicating information and command selections to the processor [1004],
  • Another type of user input device may be a cursor controller [1016], such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [1004], and for controlling cursor movement on the display [1012],
  • This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
  • the computing device [1000] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [1000] causes or programs the computing device [1000] to be a special -purpose machine.
  • the techniques herein are performed by the computing device [1000] in response to the processor [1004] executing one or more sequences of one or more instructions contained in the main memory [1006], Such instructions may be read into the main memory [1006] from another storage medium, such as the storage device [1010], Execution of the sequences of instructions contained in the main memory [1006] causes the processor [1004] to perform the process steps described herein.
  • hard-wired circuitry may be used in place of or in combination with software instructions.
  • the computing device [1000] also may include a communication interface [1018] coupled to the bus [1002],
  • the communication interface [1018] provides a two-way data communication coupling to a network link [1020] that is connected to a local network [1022].
  • the communication interface [1018] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line.
  • the communication interface [1018] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN.
  • LAN local area network
  • Wireless links may also be implemented.
  • the communication interface [1018] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
  • the computing device [1000] can send messages and receive data, including program code, through the network(s), the network link [1020] and the communication interface [1018],
  • a server [1030] might transmit a requested code for an application program through the Internet [1028], the ISP [1026], the host [1024], the local network [1022] and the communication interface [1018],
  • the received code may be executed by the processor [1004] as it is received, and/or stored in the storage device [1010], or other non-volatile storage for later execution.
  • FIG. 3 an exemplary block diagram of a system [300] for recovery of subscriber services, is shown, in accordance with the exemplary implementations of the present disclosure.
  • the system [300] comprises at least one detecting unit [302], at least one invoking unit [304], at least one determining unit [306], at least one transmitting unit [308], and at least one attaching unit [310], Also, all of the components/ units of the system [300] are assumed to be connected to each other unless otherwise indicated below. As shown in the figures all units shown within the system should also be assumed to be connected to each other. Also, in FIG.
  • system [300] may comprise multiple such units or the system [300] may comprise any such numbers of said units, as required to implement the features of the present disclosure.
  • the system [300] may reside in a server or a network entity to implement the features of the present disclosure.
  • the system [300] may be present in a user device.
  • the system [300] may be a part of the user device / or may be independent of but in communication with the user device (may also referred to herein as a UE).
  • the system [300] may reside partly in the server/ network entity and partly in the user device.
  • the system [300] is configured to perform recovery of subscriber services, with the help of the interconnection between the components/units of the system [300] . Further, reference to the components depicted in FIG. 5 is made to explain the FIG. 3.
  • the system [300] includes a detecting unit [302] configured to detect, via a binding support function (BSF) [508], a call failure in a network.
  • BSF binding support function
  • the BSF stores the binding information for a certain Protocol Data Unit (PDU) session and discovers the binding information (e.g., the address information of the selected Policy Control Function).
  • PDU Protocol Data Unit
  • the BSF allows network function service consumers (e.g., PCF) to register, update and remove the binding information, and allows other service consumers (e.g., Application Function, Network Exposure Function) to discover the binding information (e.g., the address information of the selected PCF).
  • the call failure occurs due to an error in an authorization and authentication (AA) ANSWER system from one or more network functions, which is detected at the binding support function (BSF) [508] end.
  • 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],
  • PCRF policy and charging rules function
  • PCF policy control function
  • the call failure occurs due to issues in either the establishment, or maintenance of a pre-established internet protocol connectivity access network (IP-CAN) session. Failure in establishing or maintaining the IP-CAN session leads to an occurrence of IP-CAN_Session_Not_A vailable (5065) error.
  • the Binding Support Function (BSF) [508] may constantly monitor the network to detect a call failure.
  • the network may be a 4 th Generation network or a 5 th Generation core network.
  • the call failure may be due to an error verifying the identity and permissions of the users involved.
  • the error may include, but are not limited to, the establishment or maintenance of a pre-established internet protocol connectivity access network (IP-CAN).
  • IP-CAN refers to a connection that can be set up in advance to provide a user with access to the internet or other IP -based services.
  • the determining unit [306] determines the cause of the call failure. For example, the failure of the call may have occurred due to the IP-CAN_Session_Not_A vailable (5065) error.
  • CAN_Session_Not_A vailable (5065) error is a specific error code indicating a failure to establish a multimedia session, such as a voice or video call, within an IP Multimedia Subsystem (IMS) network or Voice over Internet Protocol (VoIP) service.
  • the error can then be sent from the Policy and Charging Rules Function (PCRF) [510] or the Policy Control Function (PCF) [510] to the BSF whenever the error is detected in the AA -Answer, a
  • PCRF Policy and Charging Rules Function
  • PCF Policy Control Function
  • the system [300] includes 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.
  • the API call comprises at least one of a subscription permanent identifier (SUPI), and international mobile subscriber identity (IMSI) as a query parameter.
  • SUPI subscription permanent identifier
  • IMSI international mobile subscriber identity
  • the API call may include, but are not limited to subscription permanent identifier (SUPI), international mobile subscriber identity (IMSI).
  • SUPI subscription permanent identifier
  • IMSI international mobile subscriber identity
  • the SUPI refers to a unique identifier associated with a subscriber's account
  • IMSI refers to a unique identifier associated with the subscriber’s SIM.
  • the system [300] includes a determining unit [306] configured to determine, via the at least one of UDM [124], and HSS system, attach status of the subscriber. 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.
  • MME mobility management entity
  • the HSS sends a cancel location request (CUR) to the MME [502].
  • CUR cancel location request
  • the CLR refers to a signaling message or command within a telecommunications network to terminate the ongoing tracking of the subscriber's location
  • AMF access and mobility management function
  • the determining unit [306] may determine if the subscriber is attached to a 4 th Generation network or a 5 th Generation core network.
  • the deregistration notification is sent to the MME [502]
  • the notification message may give a reason as ‘re-attach required’.
  • the deregistration notification message may be sent to the AMF [506]
  • the message may include ‘re-registration required’.
  • the system [300] further includes 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],
  • NAS non-access stratum
  • the transmitting unit [308] may transmit the cause of the error.
  • the AMF [506] for the 5 th Generation subscriber and the MME [502] for the 4 th generation subscriber sends out the error cause over non-access stratum.
  • the Non-Access Stratum (NAS) is a layer of communication procedure to handle signalling and control functions for establishment and maintenance of connection between the user equipment [102] and corresponding core network (e.g., 4G network or 5G network).
  • the system [300] includes an attaching unit [310] configured to re-attach the subscriber to the network based on the attach status of the subscriber after successful detachment.
  • an attaching unit [310] may re-attach the subscriber to the corresponding network.
  • the network may be a 4 th generation network or a 5 th generation core network which is defined based on the subscriber details.
  • the re-attachment may be performed on a confirmation of the successful detachment of the subscriber.
  • the system [300] comprising a restoring unit [312] configured to restore, via the network, high-speed internet (HSI) and voice video and multimedia (VVM) services for the users.
  • HAI high-speed internet
  • VVM voice video and multimedia
  • the restoring unit [312] restores high speed internet and voice video and multimedia services on the subscriber’s UE [102]
  • FIG. 4 an exemplary method flow diagram [400] for recovery of subscriber services, in accordance with exemplary implementations of the present disclosure is shown.
  • the method [400] is performed by the system [300] .
  • the system [300] may be present in a server to implement the features of the present disclosure.
  • the method [400] starts at step [402],
  • the method comprises detecting, by a detecting unit [302] via a binding support function (BSF) [508], a call failure in a network.
  • the call failure occurs due to an error in an authorization and authentication (AA) ANSWER system from one or more network functions which is detected at the binding support function (BSF) [508] end.
  • 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],
  • PCF policy control function
  • the call failure occurs due to issues in either the establishment or maintenance of a pre-established internet protocol connectivity access network (IP-CAN) session.
  • IP-CAN internet protocol connectivity access network
  • the error is referred to as IP-CAN_Session_Not_A vailable (5065) error.
  • the Binding Support Function (BSF) [508] may constantly monitor the network to detect a call failure.
  • the network may be a 4 th Generation network or a 5 th Generation core network.
  • the call failure may be due to an error verifying the identity and permissions of the users involved.
  • the error may include, but are not limited to establishment or maintenance of a pre-established internet protocol connectivity access network (IP-CAN).
  • IP-CAN internet protocol connectivity access network
  • a call fail error is determined as IP- CAN_Session_Not_A vailable (5065) error by the determining unit [306] .
  • the error can then be sent from the Policy and Charging Rules Function (PCRF) [510] or the Policy Control Function (PCF) [510] to the BSF whenever the error is detected in the AA-Answer, a message in the Diameter protocol, which is used in network signalling and management.
  • PCF Policy and Charging Rules Function
  • PCF Policy Control Function
  • the method comprises 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, the API call comprises at least one of a subscription permanent identifier (SUPI), and international mobile subscriber identity (IMSI) as a query parameter.
  • API application programming interface
  • UDM unified data management
  • HSS home subscriber server
  • API Application Programming Interface
  • UDM Unified Data Management
  • the API call may include, but are not limited to subscription permanent identifier (SUPI), international mobile subscriber identity (IMSI).
  • SUPI refers to a unique identifier associated with a subscriber's account
  • IMSI refers to a unique identifier associated with the subscriber's SIM.
  • the method comprises determining, by a determining unit [306] via the at least one of UDM [124], and HSS, attach status of the subscriber. 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. [0093] At step [410], the method comprises determining the network to which the subscriber is attached or connected. For example, the subscriber may be connected or attached to a 4G network or a 5G network.
  • the method comprises, 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 More particularly, if the subscriber is connected to the 4G network, the HSS sends a cancel location request (CLR) to the MME [502],
  • MME mobility management entity
  • the method comprises, 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 re-registration required by the UDM [124], More particularly, if the subscriber is attached to the 5G network, the UDM [124] sends the deregistration notification to the AMF [506],
  • the determining unit [306] may determine if the subscriber is attached to a 4 th Generation network or a 5 th Generation core network.
  • the deregistration notification is sent to the MME [502]
  • the notification message may give a reason as ‘re-attach required’.
  • the deregistration notification message may be sent to the AMF [506]
  • the message may include ‘re-registration required’.
  • the method comprises 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],
  • NAS non-access stratum
  • the cause of the error may be transmitted by a transmitting unit [308], Tire AMF [506] for the 5 th Generation subscriber and the MME [502] for the 4 th generation subscriber, sends out the error cause over a non-access stratum.
  • the Non-Access Stratum is a layer of communication procedure to handle signaling and control functions for establishment and maintenance of connected between the user equipment [102] and corresponding core network (e.g., 4G network or 5G network).
  • the method comprises re-attaching, by an attaching unit [310], based on the attach status of the subscriber, the subscriber to the network after successful detachment.
  • the method comprises restoring high-speed internet (HSI) and voice video and multimedia (VVM) services by the network.
  • HAI high-speed internet
  • VVM voice video and multimedia
  • re-attaching the UE [102] of the subscriber to the network may be performed by the attaching unit [310],
  • the network may be a 4 th generation network or a 5 th generation core network.
  • the re-attachment may be performed on a confirmation of the successful detachment of the subscriber.
  • restoring of the high-speed internet and voice video and multimedia services on the subscriber’s UE [102] is performed by a restoring unit [312], The method terminates at step [420],
  • FIG. 5 an exemplary process flow [500] for automated subscriber services recovery upon failure detection at network end is shown, in accordance with exemplary embodiments of the present disclosure.
  • the system 300 depicted in FIG. 3 may be utilized for executing several specific steps of FIG. 5 for automated subscriber services recovery upon failure detection at network end:
  • the Binding Support Function (BSF) [508] is constantly monitoring the network. At step 1, if a call fails, it will detect this failure and associated error or reason of the failure. For example, IP-CAN_Session_Not_A vailable (5065) error may be indicated as a cause of the failure of the call. The error can then be sent from the Policy and Charging Rules Function (PCRF) [510] or the Policy Control Function (PCF) [510], which is detected in the AA-Answer, a message in the Diameter protocol, which is used in network signalling and management.
  • PCRF Policy and Charging Rules Function
  • PCF Policy Control Function
  • the BSF [508] responds by invoking an Application Programming Interface (API) in the Unified Data Management (UDM)/ HSS (504).
  • API Application Programming Interface
  • UDM Unified Data Management
  • HSS HSS
  • the API call contains either the Subscription Permanent Identifier (SUPI) or the International Mobile Subscriber Identity (IMSI) as a query parameter. These parameters identify the subscriber that needs to be deregistered.
  • SUPI Subscription Permanent Identifier
  • IMSI International Mobile Subscriber Identity
  • the API request is then received by the UDM Provisioning Server (PS).
  • PS UDM Provisioning Server
  • This server checks the exact status of the subscriber, meaning it verifies whether the subscriber is currently connected to the network and on which type of network (4G or 5G) they are attached.
  • HSS Home Subscriber Server
  • CLR Cancel Location Request
  • MME Mobility Management Entity
  • the UDM sends a deregistration notification to the Access and Mobility Management Function (AMF) [506], This notification also contains the cause 'Re-Registration required,' asking the AMF [506] to disconnect the subscriber and allow them to reconnect.
  • AMF Access and Mobility Management Function
  • the AMF [506] or MME [502] (depending on whether the subscriber is on a 5G or 4G network, respectively) will transmit the cause for deregistration over the Non-Access Stratum (NAS), which is a functional layer in the mobile communication system that carries nonradio-related signaling between the UE (User Equipment) [102] and the core network.
  • NAS Non-Access Stratum
  • the User Equipment (UE) [102] which could be a smartphone or other mobile device, will try to reconnect or 're-attach' to the network. This reconnection completes the process and restores network services for the subscriber.
  • the DRA [512] monitors resource usage across the network and detects inefficiencies or potential bottlenecks. If the DRA [512] identifies that a call failure is due to resource constraints, it can trigger an API call to the Unified Data Management (UDM) [124] or Home Subscriber Server (HSS) through the BSF [508],
  • UDM Unified Data Management
  • HSS Home Subscriber Server
  • the PCS CF [514] enforces policies related to subscriber services, such as quality of service (QoS) and access controls such that the subscribers receive services according to their subscription plans and network policies. Additionally, the PCS CF [514] applies charging rules to the services used by subscribers, calculating charges based on usage and ensuring accurate billing. When a call failure occurs, the PCS CF [514] communicates with the BSF [508], providing details on policy enforcement status and any charging issues that might have contributed to the failure.
  • QoS quality of service
  • the present disclosure further discloses a user equipment (UE) [102],
  • the UE [102] comprises a processing unit or processor [1004] to receive a request for deregister of a subscriber based on detected call failure in a network, wherein if the subscriber is attached to a 4G network, a deregistration notification is sent to a mobility management entity (MME) with a cause of 'Re- Attach required', and wherein if the subscriber is attached to a 5G network, a deregistration notification is sent to an access and mobility management function (AMF) with a cause of Reregistration required.
  • MME mobility management entity
  • AMF access and mobility management function
  • the processing unit is further configured to receive the corresponding cause over non-access stratum (NAS) from at least one of the AMF, and the MME; re-attach the subscriber to the network based on an attach status of the subscriber after successful detachment.
  • NAS non-access stratum
  • a non-transitory computer-readable storage medium storing instruction, the storage medium comprising executable code which, when executed by one or more units of a system, causes: a detecting unit of the system to detect, via a binding support function (BSF), a call failure in a network; an invoking unit of the system to invoke, 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; a determining unit [306] configured to determine, via the at least one of UDM [124], and HSS system, 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
  • BSF binding support function
  • API application programming interface
  • Tire present solution provides a method and system for recovery subscriber services recovery upon failure detection at network end that provides automated recovery in the event of a call failure to significantly reduce downtime and improve service availability.
  • the present solution further provides a standardized approach to deregistering and re-registering subscribers across different network types (4G and 5G). It enables real-time detection of the network failure and prompt recovery. This could minimize service disruptions for subscribers.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente divulgation concerne un procédé et un système de récupération de services d'abonné. Le procédé consiste à : détecter, par une unité de détection (302) via BSF (508), une défaillance d'appel dans un réseau ; invoquer, par une unité d'invocation (304) via BSF (508), un appel API dans au moins l'un parmi un système de gestion unifiée de données (UDM) (124) et un serveur d'abonné domestique, afin de désenregistrer au moins un abonné du réseau ; déterminer, par une unité de détermination (306) via l'UDM (124) et/ou HSS, l'état de rattachement de l'abonné ; transmettre, par une unité de transmission (308), la cause correspondante sur une strate de non-accès (NAS) par l'AMF (506) et/ou la MME (502) ; et se rattacher, par une unité de rattachement (310), sur la base de l'état de rattachement de l'abonné, l'abonné au réseau après un détachement réussi.
PCT/IN2024/050797 2023-07-04 2024-06-12 Procédé et système de récupération de services d'abonné Ceased WO2025008902A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN202321044639 2023-07-04
IN202321044639 2023-07-04

Publications (1)

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

Family

ID=94171390

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IN2024/050797 Ceased WO2025008902A1 (fr) 2023-07-04 2024-06-12 Procédé et système de récupération de services d'abonné

Country Status (1)

Country Link
WO (1) WO2025008902A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101513451B1 (ko) * 2013-10-30 2015-04-20 에스케이텔레콤 주식회사 무선 통신 시스템에서 재등록을 유도하기 위한 장치 및 이를 위한 방법
CN104936309B (zh) * 2010-04-27 2018-11-30 日本电气株式会社 通信方法、移动网络系统以及装置
WO2021223202A1 (fr) * 2020-05-08 2021-11-11 Qualcomm Incorporated Restauration de service de données avec des modules d'identité d'abonné doubles

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104936309B (zh) * 2010-04-27 2018-11-30 日本电气株式会社 通信方法、移动网络系统以及装置
KR101513451B1 (ko) * 2013-10-30 2015-04-20 에스케이텔레콤 주식회사 무선 통신 시스템에서 재등록을 유도하기 위한 장치 및 이를 위한 방법
WO2021223202A1 (fr) * 2020-05-08 2021-11-11 Qualcomm Incorporated Restauration de service de données avec des modules d'identité d'abonné doubles

Similar Documents

Publication Publication Date Title
WO2025012936A1 (fr) Procédé et système de rapport d'informations de charge spécifiques à une tranche
WO2025008895A1 (fr) Procédé et système pour effectuer un transfert intercellulaire d'un wlan à une nouvelle radio (nr) dans un réseau sans fil
WO2025008902A1 (fr) Procédé et système de récupération de services d'abonné
WO2025013070A1 (fr) Procédé et système de pointage de contrôle d'un appel dans un sous-système multimédia de protocole internet
WO2025062422A1 (fr) Procédé et système de gestion de liaisons de session dans un réseau
WO2025012980A1 (fr) Procédé et système pour la réalisation d'une procédure d'interdiction dans une zone de rapport de présence prédéfinie (pra)
WO2025012964A1 (fr) Procédé et système de gestion de routage de messages
WO2025062413A1 (fr) Procédé et système de maintien de session pour des demandes d'autorisation d'authentification (aar)
WO2025052413A1 (fr) Procédé et système pour effectuer une mise à jour de commande de politique pour une application
WO2025012921A1 (fr) Procédé et système de réenregistrement automatique de fonctions de réseau dans un réseau de communication
WO2025012989A1 (fr) Procédé et système de mise en œuvre de processus d'arrêt de nœud dans un réseau
WO2025012939A1 (fr) Procédé et système de surveillance en temps réel d'état(s) de fonction(s) réseau
WO2025062429A1 (fr) Procédé et système de gestion d'une condition de course dans un réseau de communication
WO2025008883A1 (fr) Procédé et système de migration de trafic d'un site dr à un site pr dans une fonction s-cscf
WO2025069054A1 (fr) Procédé et système de gestion d'alarme dans un réseau de communication sans fil
WO2025069097A1 (fr) Procédé et système de gestion d'une ou plusieurs politiques de session dans un réseau
WO2025062446A1 (fr) Procédé et système pour effectuer des opérations sur des fonctions de réseau
WO2025052475A1 (fr) Procédé et système de gestion simultanée de notifications d'abonnement sur une ou plusieurs fonctions de réseau (nf)
WO2025052410A1 (fr) Procédé et système pour initier un retrait d'enregistrement au niveau d'une unité de fonction de gestion d'accès et de mobilité (amf)
WO2025012937A1 (fr) Procédé et système de récupération d'un emplacement d'abonné cible
WO2025008904A1 (fr) Procédé et système pour effectuer une gestion de temporisation dans une procédure en mode veille
WO2025012979A1 (fr) Procédé et système aux fins d'une gestion basée sur la configuration d'une demande de procédure
WO2025012991A1 (fr) Procédé et système de commande d'un ou de plusieurs serveurs d'application dans un réseau
WO2025008871A1 (fr) Procédé et système de routage d'une demande d'enregistrement dans réseau de communication
WO2025012938A1 (fr) Procédé et système pour initier une planification de notification d'attribut de charge à partir d'une fonction de référentiel de réseau (nrf)

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2024835623

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

Country of ref document: EP

Effective date: 20260204