System and method for termination of sessions

Abstract

The present disclosure relates to a system (108) and a method (400) for termination of one or more sessions. The system (108) comprises a processing engine (208) configured to receive a session management (SM) policy delete request from a session management function (SMF) (302) and transmit a session termination request from the PCF (304) for terminating a session and send the request to an application function (AF) or a proxy call state call function (P-CSCF) (306) and check for error information in the response. If an error is detected, the processing engine (208) extracts the error information and receives a subsequent authentication authorization request (AAR) from the AF / P-CSCF (306). The PCF (304) determines the session identifier in the response and sends an authentication authorization response containing the error information back to the AF / P-CSCF (306). The AF / P-CSCF (306) interprets this error information to terminate the session.

Description

SYSTEM AND METHOD FOR TERMINATION OF SESSIONSRESERVATION OF RIGHTS

[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, Integrated Circuit (IC) layout design, and / or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.FIELD OF DISCLOSURE

[0002] The embodiments of the present disclosure generally relate to communication networks. In particular, the present disclosure relates to a system and a method for termination of sessions.DEFINITIONS

[0003] As used in the present disclosure, the following terms are generally intended to have the meaning as set forth below, except to the extent that the context in which they are used to indicate otherwise.

[0004] The expression ‘Policy Control Function (PCF) and Policy and Charging Rules Function (PCRF)’ used hereinafter in the specification refers to the network function that enforces network policies for session management. They decide how to allocate resources and prioritize traffic based on predefined rules and policies. The PCF is crucial for transmitting session termination requests (ASR), receiving responses (ASA), checking for errors, extracting error attributes, and sending authentication authorization responses (AAA) with error information. The PCF ensures that sessions are terminated harmoniously, preventing inconsistencies and resource wastage.

[0005] The expression ‘Session Management Function (SMF)’ used hereinafter in the specification refers to the network function responsible for managing session-related activities in a communication network. It handles the establishment, modification, and termination of sessions, interacts with the Policy Control Function (PCF) for policy enforcement, and ensures that the sessions are created and deleted according to network policies and user requests. In the context of the present disclosure, the SMF initiates the session creation and deletion processes, which are critical for managing network resources efficiently.

[0006] The expression ‘application function / proxy call session control function (AF / P-CSCF)’ used hereinafter in the specification refers to the network entities involved in session signalling and control. The AF provides applicationlevel signalling and control, while the P-CSCF handles call control signalling in IP multimedia subsystem (IMS) networks.

[0007] The expression ‘session termination response’ refers to feedback received from a network entity after a session termination request has been initiated. This response indicates whether the termination request was successful or encountered errors.

[0008] The expression ‘abort session request (ASR)’ or the session termination request used hereinafter in the specification refers to the request message sent by the PCF to terminate a session. This message is directed to the AF / P-CSCF to initiate the termination process. The ASR is the primary mechanism for the PCF to signal the need to end a session, ensuring that the network can free up resources and maintain consistent session states.

[0009] The expression ‘Abort Session Answer (ASA)’ used hereinafter in the specification refers the response message sent by the AF / P-CSCF in reply to an Abort Session Request (ASR). This message indicates whether the session termination was successful or if an error occurred. The ASA provides crucial feedback to the PCF, allowing it to detect errors and proceed with appropriate error handling measures.

[0010] The expression ‘Authentication Authorization Request (AAR)’ used hereinafter in the specification refers the request message sent by the AF / P-CSCF to the PCF for authentication and authorization purposes. This message is part of the ongoing session management and may be sent when errors occur during session termination. The AAR plays a role in the error handling process, where the PCF must determine the session identifier’s correspondence and respond with appropriate error information.

[0011] The expression ‘Authentication Authorization Answer (AAA)’ used hereinafter in the specification refers the response message sent by the PCF to the AF / P-CSCF in reply to an Authentication Authorization Request (AAR). This message includes error information if any issues were detected during the session termination process. The AAA contains critical error codes, such as the error code 5002, that inform the AF / P-CSCF how to terminate the session harmoniously.

[0012] The expression ‘error information’ used hereinafter in the specification refers to the specific details related to any issues or failures encountered during the session termination process. This information is included in the session termination response received from the AF or the P-CSCF when an error occurs. Error information typically comprises one or more error attributes, such as error codes, error descriptions, and session identifiers, which help in diagnosing and resolving the issue that prevented successful session termination. Further, the format and specific details of the error information might vary depending on the implementation.

[0013] The expression ‘session identifiers’ used hereinafter in the specification refers to unique identifiers assigned to each session within the network. The session identifiers may be assigned to each communication session between user equipment (UE) and network entities, such as the Policy Control Function (PCF), Application Function (AF), and Proxy Call Session Control Function (P-CSCF). These identifiers serve as a distinct reference for tracking and managing individual sessions throughout their lifecycle.

[0014] The expression ‘error condition’ used hereinafter in the specification refers to specific types of errors that are pre-determined and recognized by the system during the session termination process. These error conditions are typically identified by unique error codes and descriptive attributes that detail the nature of the error encountered. In the context of the termination of sessions, a defined error condition might be an instance where the system encounters a network communication failure, incorrect session parameters, or an authentication failure. For example, during the session termination process, the system might receive an Abort Session Answer (ASA) that includes an error code indicating a failure due to network unavailability or an authorization issue. Examples might include “Insufficient Resources” on the network entity’s side or “Session Not Found” due to invalid identification. By including these defined error conditions (potentially represented by error codes) in the information extracted from the termination response message, the network entity (AF / P-CSCF) equips the PCF with crucial details about the encountered problem. This allows the PCF to understand the nature of the failure, take appropriate actions based on the specific error (like informing the user or retrying termination), and potentially communicate the issue to other entities involved in the session. This use of defined error conditions facilitates efficient and informative error handling during the termination process.

[0015] The expression ‘plurality of issues’ mentioned within the error information of the AAA message refers to various problems that might occur during the entire authentication and authorization response flow associated with termination process. This flow encompasses multiple message exchanges between the PCF and the network entity (AF / P-CSCF). Examples may include the PCF might encounter errors parsing the received AAR message from the AF / P-CSCF due to invalid formatting or missing information, the session identifier mentioned in the AAR message might not match the identifier included in the original termination request (ASR). This inconsistency could indicate a problem with session tracking or message routing, if the AAR message requires authentication, the PCF might encounter an authentication failure due to invalid credentials orauthorization issues, the AF / P-CSCF might experience internal errors during processing, preventing it from sending a proper AAR message or including complete error information, communication issues between the PCF and the AF / P- CSCF, such as packet loss or timeouts, could lead to incomplete or missing information in the AAR message.

[0016] These definitions are in addition to those expressed in the art.BACKGROUND OF DISCLOSURE

[0017] The following description of 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 be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.

[0018] Abort Session Requests (ASR) are used to terminate service sessions between two or more user equipment. A Policy Change Function (PCF) may send ASRs to an Application Function (AF) or a proxy Call State Call Function (P- CSCF) to terminate sessions, such as voice calls or video calls. On receiving the ASR, the AF or P-CSCF may terminate the session and respond with an Abort Session Answer (ASA). The ASA may include a success message if the session was terminated by the AF or P-CSCF successfully. The ASA may include a failure message if the AF or P-CSCF fails to terminate the session. Meanwhile, the PCF may terminate the session by sending a termination request to an appropriate network entity.

[0019] The ASR error response indicates that the session cannot proceed further. If it is not handled in subsequent AAR, the session may not be properly terminated which can consume network resources and can cause inefficiencies in session management.

[0020] For example, if an error response for ASR request is received, P- CSCF may still assume that the session is active even when PCF terminates the session. Due to maintenance of inconsistent states, other network entities in the networks may not behave consistently and may lead situations where services cannot be provided to the user equipment. Further, inefficiencies may develop in the network for resolving the inconsistencies.

[0021] There is, therefore, a need in the art to provide a method and a system that can overcome the shortcomings of the existing prior arts.SUMMARY

[0022] In an exemplary embodiment, a method for performing termination of one or more sessions, the method comprising: receiving, by a PCF, a session management (SM) policy delete request from an SMF, transmitting, by the PCF, a session termination request based on the SM policy delete request for terminating a session to an AF or a P-CSCF, receiving, by the PCF, a session termination response from the AF / P-CSCF, checking, by the PCF, whether an error information is received in the session termination response, on detecting that the error information is received in the session termination response, extracting, by the PCF, the error information from the session termination response, receiving, by the PCF, an AAR from the AF / P-CSCF, determining, by the PCF, whether a session identifier of the session termination response corresponds to a session identifier of the session termination request, and on determining that the session identifier of the session termination response corresponds to a session identifier of the session termination request, sending, by the PCF, an authentication authorization response to the AF / P-CSCF, wherein the authentication authorization response includes the error information, wherein on receiving the authentication authorization response by the AF / P-CSCF, the error information of the authentication authorization response is interpreted, by the AF / P-CSCF, and terminating, by the AF / P-CSCF, the session.

[0023] In some embodiments, the error information includes a defined error condition that occurred during the session termination process.

[0024] In some embodiments, the error information includes information related to a plurality of issues involved in the authentication authorization response flow.

[0025] In some embodiments, a database is configured to store session- related data, including session identifiers and the error information, to facilitate session matching and error handling.

[0026] In another exemplary embodiment, a system for performing termination of one or more sessions, the system comprising a processing engine configured to: receive a SM policy delete request from a SMF to a PCF. transmit a session termination request from the PCF based on the policy delete request for terminating a session to an AF or a P-CSCF, receive by the PCF a session termination response from the AF / P-CSCF, check by the PCF whether an error information is received in the session termination response, on detecting that the error is received in the session termination response, extract the error information from the session termination response, receive by the PCF a subsequent AAR from the AF / P-CSCF, determine by the PCF whether a session identifier of the session termination response corresponds to a session identifier of the session termination request, on determining that the session identifier of the session termination response corresponds to a session identifier of the session termination request, send by the PCF an authentication authorization response to the AF / P-CSCF, wherein the authentication authorization response includes the error information, wherein on receiving the authentication authorization response by the AF / P-CSCF, the error information of the authentication authorization response is interpreted by the AF / P- CSCF and terminate the session by the AF / P-CSCF.

[0027] In accordance with one embodiment of the present disclosure, a user equipment that is communicatively coupled with a network is disclosed. The coupling comprises of receiving, by a PCF, a session management (SM) policydelete request from an SMF, transmitting, by the PCF, a session termination request based on the SM policy delete request for terminating a session to an AF or a P- CSCF, receiving, by the PCF, a session termination response from the AF / P-CSCF, checking, by the PCF, whether an error information is received in the session termination response, on detecting that the error information is received in the session termination response, extracting, by the PCF, the error information from the session termination response, receiving, by the PCF, an AAR from the AF / P-CSCF, determining, by the PCF, whether a session identifier of the session termination response corresponds to a session identifier of the session termination request, and on determining that the session identifier of the session termination response corresponds to a session identifier of the session termination request, sending, by the PCF, an authentication authorization response to the AF / P-CSCF, wherein the authentication authorization response includes the error information, wherein on receiving the authentication authorization response by the AF / P-CSCF, the error information of the authentication authorization response is interpreted, by the AF / P- CSCF, and terminating, by the AF / P-CSCF, the session.

[0028] In accordance with one embodiment of the present disclosure a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method for establishing a sequential initialization of one or more interfaces within a network function (NF), the method comprises receiving, by a PCF, a session management (SM) policy delete request from an SMF, transmitting, by the PCF, a session termination request based on the SM policy delete request for terminating a session to an AF or a P-CSCF, receiving, by the PCF, a session termination response from the AF / P-CSCF, checking, by the PCF, whether an error information is received in the session termination response, on detecting that the error information is received in the session termination response, extracting, by the PCF, the error information from the session termination response, receiving, by the PCF, an AAR from the AF / P-CSCF, determining, by the PCF, whether a session identifier of the session termination responsecorresponds to a session identifier of the session termination request, and on determining that the session identifier of the session termination response corresponds to a session identifier of the session termination request, sending, by the PCF, an authentication authorization response to the AF / P-CSCF, wherein the authentication authorization response includes the error information, wherein on receiving the authentication authorization response by the AF / P-CSCF, the error information of the authentication authorization response is interpreted, by the AF / P- CSCF, and terminating, by the AF / P-CSCF, the session.

[0029] The foregoing general description of the illustrative embodiments and the following detailed description thereof are merely exemplary aspects of the teachings of this disclosure and are not restrictive.OBJECTS OF THE PRESENT DISCLOSURE

[0030] Some of the objects of the present disclosure, which at least one embodiment herein satisfies are as listed herein below.

[0031] An object of the present disclosure is to provide a system and a method for termination of sessions.

[0032] Another object of the present disclosure is to provide a system and a method that prevents networks from operating in inconsistent states.

[0033] Another object of the present disclosure is to provide a system and a method that handles error responses for gracefully terminating sessions. The session can be terminated in an orderly manner, ensuring that any ongoing processes or transactions associated with session are terminated correctly.

[0034] Another object of the present disclosure is to provide a system and a method that prevents inconsistent states when session is abruptly terminated.

[0035] Another object of the present disclosure is to provide a system and a method that utilizes network resources efficiently by resolving inconsistent states promptly.

[0036] Another object of the present disclosure is to provide a system and a method that helps in preventing the service disruptions or incorrect behavior due to unresolved sessions. By terminating sessions that encounter errors, the system can provide a more reliable and consistent user experience ensuring a smoother interaction.BRIEF DESCRIPTION OF DRAWINGS

[0037] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes the disclosure of electrical components, electronic components or circuitry commonly used to implement such components.

[0038] FIG. 1 illustrates an exemplary architecture for termination of sessions, in accordance with embodiments of the present disclosure.

[0039] FIG. 2 illustrates a block diagram of a system for performing termination of sessions, in accordance with embodiments of the present disclosure.

[0040] FIG. 3A illustrates a sequence diagram for performing termination of sessions, in accordance with embodiments of the present disclosure.

[0041] FIG. 3B illustrates the communication flow between the PCF / PCRF and the AF / P-CSCF, in accordance with embodiments of the present disclosure.

[0042] FIG. 4 illustrates a flow diagram of a method for performing termination of sessions, in accordance with embodiments of the present disclosure.

[0043] FIG. 5 illustrates an exemplary computer system in which or with which the system may be implemented, in accordance with an embodiment of the present disclosure.

[0044] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network Architecture102-1, 102-2...102-N - Users104-1, 104-2. . . 104-N - User equipments106 - Network108, 300 - System110-1, 110-2- Network entities202 - One or more processor(s)204 - Memory206 - Interface208 - Processing engine210 - Database212 - Session management engine214 - Termination engine / Termination harmonization engine216 - Other unit(s)302 - SMF304 - PCF306 - AF / P-CSCF510 - External storage device520 - Bus530 - Main memory540 - Read only memory550 - Mass storage device560 - Communication port570 - ProcessorDETAILED DESCRIPTION OF DISCLOSURE

[0045] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address all of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein.

[0046] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0047] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.

[0048] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, astructure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.

[0049] The word “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. In addition, 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. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising” as an open transition word without precluding any additional or other elements.

[0050] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0051] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. Asused herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and / or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed items.

[0052] The present disclosure relates to a system and a method for termination or termination of one or more sessions. The system may terminate a first session from the set of sessions corresponding to a session between the user equipment (UE) and the system. The sessions may be created between the UE and one or more network entities in a network, when the UE request for services from said network. The system transmits an ASR to the one or more network entities to terminate a set of sessions between UE and said network entities. The system receives an Abort Session Answer (ASA) from the one of the one or more network entities having a first message associated thereto. When the first message is indicative of an error, the system extracts one or more error attributes from the message. The error attributes may be indicative of a first error code and an identifier attribute of the session. The system receives an Authentication Authorization Request (AAR) and determines whether the session identifier attribute in the AAR corresponds to the session identifier attribute in the ASA. The system transmits an Authentication Authorization Answer (AAA) to the one or more network entities with a second error code and the session identifier attributes such that the one or more network entities terminates the session on receiving the AAA.

[0053] The various embodiments throughout the disclosure will be explained in more detail with reference to FIG. 1- FIG. 5.

[0054] Referring to FIG. 1, the network architecture (100) may include one or more computing devices or user equipments (104-1, 104-2...104-N) associatedwith one or more users (102-1, 102-2...102-N) in an environment. A person of ordinary skill in the art will understand that one or more users (102-1, 102-2...102- N) may be individually referred to as the user (102) and collectively referred to as the users (102). Similarly, a person of ordinary skill in the art will understand that one or more user equipments (104-1, 104-2. . . 104- N) may be individually referred to as the user equipment (104) and collectively referred to as the user equipment (104). A person of ordinary skill in the art will appreciate that the terms “computing device(s)” and “user equipment” may be used interchangeably throughout the disclosure. Although two user equipments (104) are depicted in FIG. 1, however any number of the user equipments (104) may be included without departing from the scope of the ongoing description. In an embodiment, each of the user equipment (104) may have a first unique identifier attribute associated therewith. In an embodiment, the first unique identifier attribute may be indicative of Mobile Station International Subscriber Directory Number (MSISDN), International Mobile Equipment Identity (IMEI) number, International Mobile Subscriber Identity (IMSI), Subscriber Permanent Identifier (SUPI) and the like.

[0055] In an embodiment, the user equipment (104) may include smart devices operating in a smart environment, for example, an Internet of Things (loT) system. In such an embodiment, the user equipment (104) may include, but is not limited to, smart phones, smart watches, smart sensors (e.g., mechanical, thermal, electrical, magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart television (TV), computers, smart security system, smart home system, other devices for monitoring or interacting with or for the users (102) and / or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the user equipment (104) may include, but is not limited to, intelligent, multi-sensing, network-connected devices, that can integrate seamlessly with each other and / or with a central server or a cloud-computing system or any other device that is network-connected.

[0056] In an embodiment, the user equipment (104) may include, but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a smart phone, a phablet device, and so on), a wearable computer device(e.g., a headmounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and / or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the user equipment (104) may include, but is not limited to, any electrical, electronic, electro-mechanical, or an equipment, or a combination of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device, wherein the user equipment (104) may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user (102) or the entity such as touch pad, touch enabled screen, electronic pen, and the like. A person of ordinary skill in the art will appreciate that the user equipment (104) may not be restricted to the mentioned devices and various other devices may be used.

[0057] Referring to FIG. 1, the user equipment (104) may communicate with a system (108) via a network (106). In an embodiment, the network (106) may include at least one of a Fifth Generation (4G) network, 6G network, or the like. The network (106) may enable the user equipment (104) to communicate with other devices in the network architecture (100) and / or with the system (108). The network (106) may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network (106) may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet,the Public Switched Telephone Network (PSTN), or the like. In an embodiment, the network (106) may include one or more base stations (112) for facilitating communication between the one or more UEs (104). The network (106) may be formed by a set of base stations (112) communicatively coupled to enable telecommunication exchanges between one or more UEs (104).

[0058] The base station (112) may be a network infrastructure that provides wireless access to one or more terminals associated therewith. The base station (112) may have coverage defined to be a predetermined geographic area based on the distance over which a signal may be transmitted. The base station (112) may include, but not be limited to, wireless access point, evolved NodeB (eNodeB), 5G node or next generation NodeB (gNB), wireless point, transmission / reception point (TRP), and the like. In an embodiment, the base station (112) may include one or more operational units that enable telecommunication between two or more UEs (104). In an embodiment, the one or more operational units may include, but not be limited to, transceivers, baseband unit (BBU), (remote radio unit - RRU), antennae, mobile switching centres, radio network control units, one or more processors associated thereto.

[0059] In an embodiment, the network (106) may include one or more network entities (110) depicted by network entity 1 (110-1) and network entity 2 (110-2) in FIG. 1. In an embodiment, the network entities (110) may include, but not limited to, a PCF, P-CSCF, serving gateway (SGW), packet data network (PDN) gateway (PGW), mobility management entity (MME), and the like. In an embodiment, the network (106) may further include a user plane, and a control plane having network entities (110) such as application function (AF), access and mobility management function (AMF) unit, session management function (SMF) unit, and network exposure function (NEF) units, but not limited thereto. In an embodiment, the network entities (110) forming the network (106) may be implemented as a hardware component, software component, or any combination thereof.

[0060] In an embodiment, the system (108) may be a network entity (110) indicative of the PCRF or the PCF, or a combination thereof. In an embodiment, the PCF may be configured to determine policy and charging rules associated with the UEs (104) attempting to connect to the network (106).

[0061] In accordance with embodiments of the present disclosure, the system (108) may be designed and configured for the termination of sessions. In an embodiment, the system (108) may optimize the number of sessions maintained to fulfil requests for service from the UEs (104).

[0062] FIG. 2 illustrates a block diagram (200) of the system (108), in accordance with embodiments of the present disclosure.

[0063] In an aspect, the system (108) may include one or more processor(s) (202). The one or more processor(s) (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, edge or fog microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (202) may be configured to fetch and execute computer-readable instructions stored in a memory (204) of the system (108). The memory (204) may be configured to store one or more computer- readable instructions or routines in a non-transitory computer-readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (204) may include any non-transitory storage device including, for example, volatile memory such as Random Access Memory (RAM), or non-volatile memory such as Erasable Programmable Read-Only Memory (EPROM), flash memory, and the like.

[0064] Referring to FIG. 2, the system (108) may include an interface(s) (206). The interface(s) (206) may include a variety of interfaces, for example, interfaces for data input and output devices, referred to as I / O devices, storage devices, and the like. The interface(s) (206) may facilitate communication to / from the system (108). The interface(s) (206) may also provide a communicationpathway for one or more components of the system (108). Examples of such components include, but are not limited to, processing unit / engine(s) (208) and a database (210).

[0065] In an embodiment, the processing unit / engine(s) (208) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s) (208). In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine(s) (208) may be processorexecutable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing engine(s) (208) may include a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine(s) (208). In such examples, the system (108) may include the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system (108) and the processing resource. In other examples, the processing engine(s) (208) may be implemented by electronic circuitry.

[0066] In an embodiment, the database (210) may include data that may be either stored or generated as a result of functionalities implemented by any of the components of the processor (202) or the processing engines (208). In an embodiment, the database (210) may be separate from the system (108). In an embodiment, the database (210) may be indicative of including, but not limited to, a relational database, a distributed database, a cloud-based database, or the like.

[0067] In an exemplary embodiment, the processing engine (208) may include one or more engines selected from any of a session management engine (212), a termination engine or termination harmonizer engine (214), and otherengines (216) having functions that may include, but are not limited to, testing, storage, and peripheral functions, such as wireless communication unit for remote operation, audio unit for alerts and the like. The session management engine (212) may handle the creation, maintenance, and termination of sessions between the UE (104) and the network entities (110). For example, the session management engine (212) processes requests to establish new sessions, applies necessary policies, and ensures proper termination of sessions by coordinating with other network functions such as the PCF and the SMF. If the user (102) initiates a video call, the session management engine (212) will manage the session from initiation through to termination, ensuring consistent state and resource management throughout.

[0068] In an embodiment, the session management engine (212) may terminate a first session from a set of sessions. The first session may refer to the session that was created first in time. The set of sessions may be designed to manage multiple active sessions simultaneously for each UE (104). The set of sessions could represent different communication channels. The first session may correspond to a session between the UE (104) and the system (108).

[0069] Referring to FIG. 1, in an embodiment, the system (108) may create the set of sessions when a request to create a session is received by one or more network entities (110-1, 110-2). In an example, the system (108) may be indicative of the PCF / PCRF, which may receive a SM policy creation request from the SMF to create an SM session. The SM policy creation request refers to a set of rules and configurations used by the PCF to manage the lifecycle of network sessions. This includes creating, maintaining, and terminating sessions based on predefined criteria such as user profiles, service types, and network conditions. For example, an SM policy creation request might dictate how long a data session can last or the quality of service required for a video call, ensuring optimal resource allocation and session continuity. In such examples, the PCF may transmit a SM policy creation request success response to the SMF. In an embodiment, the session management engine (212) may terminate the first session on receiving a request to delete a session from the set of sessions. In an example, the system (108) may be indicativeof the PCF, which may receive an SM policy delete request from the SMF to delete the SM session. In such examples, the PCF may transmit an SM policy delete success response to the SMF.

[0070] In an embodiment, a termination harmonizer engine (214) may transmit the ASR to the one or more network entities (110) to terminate a set of sessions between the UE (104) and the network entities (110). The termination harmonizer engine (214) may receive an ASA from the corresponding network entities (110) having a first message associated thereto. When the first message is indicative of an error, the termination harmonizer engine (214) may extract error information from the message. In an embodiment, the error information or error attributes may include information related to a plurality of issues involved in the authentication authorization response flow. The authentication authorization response flow refers to a specific message exchange between the PCF and the AF / P- CSCF that addresses error scenarios during termination. Also, the error information may be indicative of an error code and an identifier attribute of the session. The termination harmonizer engine (214) may receive an AAR and may determine whether the session identifier attribute in the AAR corresponds to the session identifier attribute in the ASA. The termination harmonizer engine (214) sends an AAA to the network entities (110) containing a second error code and the session identifier attributes. This causes the network entities (110) to terminate the session upon receiving the AAA. In an example, the PCF may exchange Abort Session messages and authentication application messages to the AF or the P-CSCF. In such examples, when the PCF receives error message in the ASA, the PCF may generate a second error code having value ‘5002’ and include the second error code in the AAA for subsequent AAR requests from the AF or the P-CSCF.

[0071] FIG. 3A illustrates a sequence diagram of a method (300) for termination of sessions, in accordance with embodiments of the present disclosure.

[0072] The method (300) includes terminating, by the processing enginebetween the UE (104) and the system (108). The sessions may be created between the UE (104) and one or more network entities (112) in the network (106), when the UE (104) request for services from the network (106).

[0073] At step 308, the SMF (302) initiates the process by sending a Session Management (SM) policy create request to the PCF (304). This request is made to establish the new session and set up the necessary policies for session management. The PCF (304) receiving a session creation request from the SMF (302) aligns with the capability of the system (108) to handle session initiation. The system (108) creates sessions upon request from the network entities (110).

[0074] At step 310, the PCF (304) processes the SM policy create request and responds to the SMF (302) with a success message, indicating that the session has been successfully created and the policies have been applied. The processing engine (208) is responsible for the execution and confirmation of session policies and handles the setup and validation of session policies, ensuring that all necessary parameters are correctly applied, and that the session is properly managed from its initiation.

[0075] At step 312, the AF / P-CSCF (306) sends an Authentication Authorization Request (AAR) to the PCF (304). The AAR is part of the session management process where the AF / P-CSCF (306) seeks authorization for the session.

[0076] At step 314, upon receiving and processing the AAR, the PCF (304) sends back an Authentication Authorization Answer (AAA) success response to the AF / P-CSCF. This indicates that the session authorization has been successfully completed. The processing of AAA responses may be integral to the functionality of the system (108), ensuring that the session continues with proper authorization.

[0077] At step 316, the SMF (302) initiates the session termination process by sending an SM policy delete request to the PCF (304). This request is aimed at terminating the session and deleting the associated policies. The processing engine(208) may be equipped to handle session termination requests, initiating the steps necessary to terminate sessions.

[0078] At step 318, the PCF (304) processes the SM policy delete request and sends a successful response back to the SMF (302), indicating that the session policies have been successfully deleted and the session is terminated. The confirmation of session termination aligns with the capabilities of the system (108) to manage and confirm session deletions.

[0079] At step 320, the PCF (304) sends an Abort Session Request (ASR) to the AF / P-CSCF (306) to terminate the session on the AF / P-CSCF (306) side. This request is part of the session termination process. Sending the ASR requests is a key part of the present invention, where the PCF (304) initiates the session termination across various network entities (110) to ensure consistent session management. For example, the PCF (304) receives a user request to disconnect from a video call. It initiates termination by sending an ASR message to the AF / P-CSCF (306) responsible for managing video call sessions. The ASR message could include the session identifier associated with the video call.

[0080] At step 322, the AF / P-CSCF (306) processes the ASR and sends an Abort Session Answer (ASA) response back to the PCF (304). This response indicates whether the session termination was successful or if there were errors. Receiving and processing ASA responses is crucial to the error handling process of the system (108), where the PCF (304) extracts error attributes from the ASA if an error is detected. For example, the AF / P-CSCF (306) receives the ASR for the video call session. The AF / P-CSCF (306) attempts to terminate the call by releasing network resources and notifying other participants. However, it encounters an error due to insufficient bandwidth on the user’s connection. The AF / P-CSCF (306) responds with an ASA message to the PCF (304). The ASA might include an error code indicating the specific reason for the termination failure (e.g., “503 - Insufficient Bandwidth”).

[0081] At step 324, if the ASA contains an error code, the AF / P-CSCF (306) sends a subsequent AAR to the PCF (304). This step ensures that any issues in the session termination process are addressed. For example, recognizing the error code in the ASA, the AF / P-CSCF (306) sends an AAR message to the PCF (304). This AAR message includes the session identifier for the video call session to ensure it relates to the same failed termination attempt.

[0082] At step 326, the PCF processes the subsequent AAR and responds with an AAA that includes the 5002 error code. This code indicates that there was an error in the session termination process, and specific actions need to be taken. Sending an AAA with the 5002 error code is where the system (108) uses specific error codes to communicate issues and ensure proper session termination. For example, the PCF (304) receives the AAR with the matching session identifier. The PCF (304) acknowledges the error by sending an AAA message back to the AF / P- CSCF (306). The AAA message may include a specific error code (5002) indicating a session termination failure due to reasons beyond the control of the PCF (304) and the session identifier attribute, ensuring the AAA relates to the video call session with the bandwidth limitation.

[0083] At step 328, upon receiving the AAA with the 5002 error code, the AF / P-CSCF (306) interprets the error and terminates the session accordingly. This ensures that the session is properly terminated despite the initial error, ensuring network efficiency and consistency. For example, upon receiving the AAA with the 5002 error code, the AF / P-CSCF (306) interprets the error. The AF / P-CSCF (306) understands that the termination failed due to network resource limitations. The AF / P-CSCF (306) then takes action to terminate the video call session gracefully, informing the user (102) about the issue.

[0084] FIG. 3B illustrates the communication flow between the PCF / PCRF (304) and the AF / P-CSCF (306). The PCF / PCRF (304) may be responsible for enforcing policy rules, while the AF / P-CSCF (306) may handle signalling and session management. The figure illustrates the sequential exchange of requests andresponses between the PCF / PCRF (304) and the AF / P-CSCF (306). This bidirectional communication involves the PCF / PCRF (304) transmitting session termination requests to the AF / P-CSCF (306) and subsequently receiving session termination responses. These interactions are critical for coordinating the session termination process, ensuring both functions have the necessary information to proceed with and confirm the termination of sessions. The reception (Rx) of these requests and responses underlines the dynamic and responsive nature of the communication, which is essential for maintaining session integrity and compliance with network policies.

[0085] FIG. 4 illustrates a method (400) for termination of sessions, in accordance with embodiments of the present disclosure.

[0086] At step 402, the method (400) is configured to receive, by the PCF (304), the SM policy delete request from the SMF (302). The SMF (302) may send the SM policy delete request to the PCF (304) to initiate session termination. The SM policy delete request signals the PCF (304) to delete and terminate the session policies associated with a specific session or user (102). This occurs when a session is terminated or no longer required.

[0087] At step 404, the method (400) is configured to transmit, by the PCF (304), the session termination request based on the SM policy delete request for terminating a session to the AF or the P-CSCF (306). For instance, when a session needs to be terminated due to policy changes or resource management, the PCF (304) sends an Abort Session Request (ASR) to the AF or P-CSCF (306). This request includes session identifiers and reasons for termination. This step is facilitated by the processing engine (208) within the PCF (304), which ensures that the termination request is accurately transmitted, reflecting the proper session policies and conditions for termination.

[0088] At step 406, the method (400) involves receiving, by the PCF (304), a session termination response from the AF / P-CSCF (306). After sending the ASR, the PCF (304) waits for an ASA from the AF or P-CSCF (306), which indicateswhether the session termination was successful or encountered an error. This response is managed by the processing engine (208), which monitors incoming messages and processes the session termination response accordingly.

[0089] At step 408, the method (400) is configured to check, by the PCF (304), whether an error is received in the session termination response. The PCF (304) analyzes the ASA for any error codes or failure messages. For instance, if the ASA indicates a failure due to a network issue, the PCF (304) identifies this error. The error checking is performed by the processing engine (208), which is designed to detect and interpret error codes within the session termination responses.

[0090] At step 410, the method (400) includes receiving, by the PCF (304), a subsequent authentication authorization request (AAR) from the AF / P-CSCF (306). If an error was detected in the ASA, the AF or P-CSCF (306) might send a follow-up AAR to the PCF (304) to address the issue and attempt to reauthorize or terminate the session properly. This reception is handled by the processing engine (208), which ensures that subsequent requests related to the session are properly managed.

[0091] At step 412, the method (400) is configured to determine, by the PCF (304), whether a session identifier of the session termination response corresponds to a session identifier of the session termination request. The PCF (304) checks whether the session identifier in the ASA matches the session identifier in the original ASR. This verification ensures that the response is correctly associated with the initial termination request. The processing engine (208) performs this matching process, ensuring the integrity and consistency of session management.

[0092] At step 416, the method (400) involves sending, by the PCF (304), an authentication authorization response to the AF / P-CSCF (306), wherein the authentication authorization response includes error information. If the session identifiers match, the PCF (304) sends an AAA containing error information (e.g., error code 5002) back to the AF or P-CSCF (306). This message informs the AF / P- CSCF of the issues encountered during the session termination process. Theprocessing engine (208) generates and transmits the AAA, ensuring that it contains accurate error information to facilitate proper session handling. Upon receiving the authentication authorization response, the AF / P-CSCF (306) interprets the error information and terminates the session as per the received instructions. The AF or P-CSCF (306) processes the error code (e.g., 5002) in the AAA and initiates procedures to clean up and terminate the session, ensuring no resources are wasted on an invalid or failed session. This step is enabled by the robust communication and error handling mechanisms within the system, ensuring that the AF / P-CSCF (306) correctly interprets the instructions and terminates the session harmoniously. In an example, the user (102) initiates a video call, and the PCF (304) sends an ASR message to the AF / P-CSCF (306) to terminate the call. The AF / P-CSCF (306) attempts to terminate the call but encounters insufficient bandwidth on the connection of the user (102). In the ASA message sent back to the PCF (304), the error information might include: an Error Code: “503” or a Descriptive Text: “Insufficient Bandwidth for Session Termination.” By receiving this error information, the PCF (304) understands that the termination failed due to network resource limitations, not because of any issue with the session itself. The PCF (304) can then take appropriate actions, potentially sending an AAA message back to the AF / P-CSCF (306) with the specific error code and informing the user (102) about the connection issue.

[0093] FIG. 5 illustrates an exemplary computer system (500) in which or with which embodiments of the present disclosure may be implemented. As shown in FIG. 5, the computer system (500) may include an external storage device (510), a bus (520), a main memory (530), a read only memory (540), a mass storage device (550), a communication port (560), and a processor (570). A person skilled in the art will appreciate that the computer system (500) may include more than one processor (570) and communication ports (560). Processor (570) may include various modules associated with embodiments of the present disclosure.

[0094] In an embodiment, the communication port (560) may be any of an RS-232 port for use with a modem-based dialup connection, a 10 / 100 Ethernet port,a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication port (560) may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system (500) connects.

[0095] In an embodiment, the memory (530) may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. Read-only memory (540) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input / Output System (BIOS) instructions for the processor (570).

[0096] In an embodiment, the mass storage (550) may be any current or future mass storage solution, which may be used to store information and / or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Firewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks (e.g., SATA arrays).

[0097] In an embodiment, the bus (520) communicatively couples the processor(s) (570) with the other memory, storage and communication blocks. The bus (520) may be, e.g., a Peripheral Component Interconnect (PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB) or the like, for connecting expansion cards, drives and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (570) to the computer system (500).

[0098] Optionally, operator and administrative interfaces, e.g., a display, keyboard, joystick, and a cursor control device, may also be coupled to the bus (520) to support direct operator interaction with the computer system (500). Other operator and administrative interfaces may be provided through networkconnections connected through the communication port (560). The components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system (500) limit the scope of the present disclosure.

[0099] Ref. FIG. 1 and FIG. 3, in accordance with one embodiment of the present disclosure, the user equipment (104) that is communicatively coupled with the network (106) is disclosed. The coupling comprises of transmitting, by the PCF (304), a session termination request for terminating a session to the AF / P-CSCF (306), receiving, by the PCF (304), a session termination response from the AF / P- CSCF (306), checking, by the PCF (304), whether an error information is received in the session termination response, on detecting that the error information is received in the session termination response, extracting, by the PCF (304), the error information from the session termination response, receiving, by the PCF (304), an authentication authorization request (AAR) from the AF / P-CSCF (306), determining, by the PCF (304), whether a session identifier of the session termination response corresponds to a session identifier of the session termination request, and on determining that the session identifier of the session termination response corresponds to a session identifier of the session termination request, sending, by the PCF (304), an authentication authorization response to the AF / P- CSCF (306), wherein the authentication authorization response includes the error information, wherein on receiving the authentication authorization response by the AF / P-CSCF (306), the error information of the authentication authorization response is interpreted, by the AF / P-CSCF (306), and terminating, by the AF / P- CSCF (306), the session.

[0100] The present disclosure introduces a novel approach to session termination within communication networks. The present disclosure tackles the challenge of ensuring consistent and coordinated termination across diverse network elements by implementing a centralized Policy Control Function (PCF) that orchestrates the termination process. The core of the present disclosure lies in the utilization of specific messages (ASR, ASA, AAR, and AAA) for error handlingand communication between the PCF and network entities (AF / P-CSCF). This enables the exchange of detailed error information (including defined error conditions and a wider range of issues) to facilitate efficient troubleshooting and robust session termination. By employing harmonized termination, the present disclosure offers significant improvements in the reliability and manageability of session lifecycles within communication networks, leading to a more seamless user experience and enhanced network resource utilization.

[0101] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be implemented merely as illustrative of the disclosure and not as a limitation.

[0102] The present disclosure provides technical advancement related to the managing termination of sessions. This advancement addresses the limitations of existing technology that does not manage error response for ASR, which leads to inconsistent states and consumption of resources. The disclosure provides a technique for performing termination of one or more sessions, which offers significant improvements in terms of managing error response, leading to consistent services and better utilization of resources.ADVANTAGES OF THE PRESENT DISCLOSURE

[0103] The present disclosure provides a system and a method for termination of sessions.

[0104] The present disclosure provides a system and a method that prevents networks from operating in inconsistent states.

[0105] The present disclosure provides a system and a method that handles error responses for gracefully terminating sessions.

[0106] The present disclosure provides a system and a method that prevents inconsistent states when a session is abruptly terminated.

[0107] The present disclosure provides a system and a method that helps in preventing the service disruptions or incorrect behavior due to unresolved sessions. By terminating sessions that encounter errors, the system can provide a more reliable and consistent user experience ensuring a smoother interaction.

[0108] The present disclosure provides a system and a method that utilizes network resources efficiently by resolving inconsistent states promptly.

Claims

We claim:

1. A method (400) for termination of one or more sessions, the method (400) comprising: receiving (402), by a policy control function (PCF) (304), a session management (SM) policy delete request from a session management function (SMF) (302); transmitting (404), by the PCF (304), a session termination request based on the SM policy delete request for terminating a session to an application function (AF) or a proxy call state call function (P-CSCF) (306); receiving (406), by the PCF (304), a session termination response from the AF / P-CSCF (306); checking (408), by the PCF (304), whether an error information is received in the session termination response, on detecting that the error information is received in the session termination response, extracting, by the PCF (304), the error information from the session termination response; receiving (410), by the PCF (304), an authentication authorization request (AAR) from the AF / P-CSCF (306); determining (412), by the PCF (304), whether a session identifier of the session termination response corresponds to a session identifier of the session termination request, and on determining that the session identifier of the session termination response corresponds to a session identifier of the session termination request, sending, by the PCF (304), an authentication authorization response to the AF / P-CSCF (306), wherein the authentication authorization response includes the error information, wherein on receiving the authentication authorization response by the AF / P-CSCF (306), the error information of the authentication authorization response is interpreted, by the AF / P-CSCF (306); and terminating (414), by the AF / P-CSCF (306), the session.

2. The method (400) claimed as in claim 1, wherein the error information includes a defined error condition that occurred during the session termination process.

3. The method (400) claimed as in claim 1, wherein the error information includes information related to a plurality of issues involved in the authentication authorization response flow.

4. The method (400) claimed as in claim 1, wherein a database (210) is configured to store session-related data, including session identifiers and the error information, to facilitate session matching and error handling.

5. A system (108) for termination of one or more sessions, the system (108) comprising a: a processing engine (208) configured to: receive a session management (SM) policy delete request from a session management function (SMF) (302) to a policy control function (PCF) (304); transmit a session termination request from the PCF (304) based on the policy delete request for terminating a session to an application function (AF) or a proxy call state call function (P-CSCF) (306); receive by the PCF (304) a session termination response from the AF / P-CSCF (306); check by the PCF (304) whether an error information is received in the session termination response, on detecting that the error is received in the session termination response, extract the error information from the session termination response; receive by the PCF (304), a subsequent authentication authorization request (AAR) from the AF / P-CSCF (306); determine by the PCF (304), whether a session identifier of thesession termination response corresponds to a session identifier of the session termination request, on determining that the session identifier of the session termination response corresponds to a session identifier of the session termination request, sending, by the PCF (304), an authentication authorization response to the AF / P-CSCF (306), wherein the authentication authorization response includes the error information, wherein on receiving the authentication authorization response by the AF / P-CSCF (306), the error information of the authentication authorization response is interpreted, by the AF / P-CSCF (306); and terminate the session by the AF / P-CSCF (306).

6. The system (108) claimed as in claim 5, wherein the error information includes a defined error condition that occurred during the session termination process.

7. The system (108) claimed as in claim 5, wherein the error information includes information related to a plurality of issues involved in the authentication authorization response flow.

8. The system (108) as claimed in claim 5, wherein a database (210) is configured to store session-related data, including session identifiers and error attributes, to facilitate session matching and error handling.

9. A user equipment (UE) (104) communicatively coupled with a network (106), the coupling comprises steps of: receiving, by a policy control function (PCF) (304), a session management (SM) policy delete request from a session management function (SMF) (302); transmitting, by the PCF (304), a session termination request based on the SM policy delete request for terminating a session to an applicationfunction (AF) or a proxy call state call function (P-CSCF) (306); receiving, by the PCF (304), a session termination response from the AF / P-CSCF (306); checking, by the PCF (304), whether an error information is received in the session termination response, on detecting that the error information is received in the session termination response, extracting, by the PCF (304), the error information from the session termination response; receiving, by the PCF (304), an authentication authorization request (AAR) from the AF / P-CSCF (306); determining, by the PCF (304), whether a session identifier of the session termination response corresponds to a session identifier of the session termination request, and on determining that the session identifier of the session termination response corresponds to a session identifier of the session termination request, sending, by the PCF (304), an authentication authorization response to the AF / P-CSCF (306), wherein the authentication authorization response includes the error information, wherein on receiving the authentication authorization response by the AF / P-CSCF (306), the error information of the authentication authorization response is interpreted, by the AF / P- CSCF (306); and terminating, by the AF / P-CSCF (306), the session.

10. A computer program product comprising a non-transitory computer- readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method (500) for establishing a sequential initialization of one or more interfaces within a network function (NF), said method (500) comprising: receiving (402), by a policy control function (PCF) (304), a session management (SM) policy delete request from a session managementfunction (SMF) (302); transmitting (404), by the PCF (304), a session termination request based on the SM policy delete request for terminating a session to an application function (AF) or a proxy call state call function (P-CSCF) (306); receiving (406), by the PCF (304), a session termination response from the AF / P-CSCF (306); checking (408), by the PCF (304), whether an error information is received in the session termination response, on detecting that the error information is received in the session termination response, extracting, by the PCF (304), the error information from the session termination response; receiving (410), by the PCF (304), an authentication authorization request (AAR) from the AF / P-CSCF (306); determining (412), by the PCF (304), whether a session identifier of the session termination response corresponds to a session identifier of the session termination request, and on determining that the session identifier of the session termination response corresponds to a session identifier of the session termination request, sending, by the PCF (304), an authentication authorization response to the AF / P-CSCF (306), wherein the authentication authorization response includes the error information, wherein on receiving the authentication authorization response by the AF / P-CSCF (306), the error information of the authentication authorization response is interpreted, by the AF / P- CSCF (306); and terminating (414), by the AF / P-CSCF (306), the session.

Images