Method and system for managing one or more session requests at a charging function (CHF)

Abstract

The present disclosure relates to approaches for managing one or more session requests at a Charging Function (CHF) In one example, a session create request may be received from a Network Function (NF). Thereafter, a network session may be initiated based on the session create request. Thereafter, a target session update request, which may be a session terminate request, may be received from the NF. Thereafter, a session holding timer associated with the network session may be configured. Thereafter, one or more session update requests may be received from the NF. The one or more session update requests may be associated with the network session. Thereafter, a network session status associated with the network session may be determined based on the session holding timer. The network session status may be one of a network session suspended state status and a network holding state status.

Description

METHOD AND SYSTEM FOR MANAGING ONE OR MORE SESSION REQUESTS AT A CHARGING FUNCTION (CHF)FIELD OF INVENTION

[0001] Embodiments of the present disclosure relate generally to the field of wireless communication systems. More particularly, embodiment of the present disclosure relates to a method and system for managing one or more session requests at a Charging Function (CHF).BACKGROUND

[0002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.

[0003] In the context of 5G network management, Charging Function (CHF) plays a pivotal role in managing subscriber connections and protocol conversions, tailored to their data usage and resource consumption patterns. This function interfaces with a database to meticulously execute its services. Generally, in a telecommunications network, a user may initiate a session, such as for making a call or starting a data transfer. As a part of the session initiation, a Session Management Function (SMF) may establish the session and communicate with different network elements in the network. For handling the charging and billing-related functions, the SMF may need to establish session with the CHF.

[0004] For establishing the network session with the CHF, the SMF may transmit a request to the CHF for creating and initiating the session. Once the network session has been established, the SMF may keep communicating with the CHF for updating session parameters and charging information as the session progresses. In the end, the session may be terminated and the charging and billing may be finalized.

[0005] However, in conventional approaches, it may be possible that after the session has been terminated, the SMF may again transmit a request for updating the network session. For example, shortly after the session has been terminated, SMF may transmit an update request to the CHF.The CHF may assume that the network session is still active, or the CHF may process the update request for a session that it has already marked as terminated. As a result, this situation may result in various problems such as incorrect billing, resource mismanagement, and incorrect session states.

[0006] Thus, there exists an imperative need in the art to manage session requests at a Charging Function (CHF) and automatically maintain a session suspended state for a session terminate request, which the present disclosure aims to address.SUMMARY

[0007] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.

[0008] An aspect of the present disclosure may relate to a method for managing one or more session requests at a Charging Function (CHF). The method comprises receiving, by a transceiver unit, a session create request from a Network Function (NF). The method further comprises initiating, by an initiation unit, a network session based on the session create request. The method further comprises receiving, by the transceiver unit, a target session update request from the NF, wherein the target session update request is a session terminate request. The method further comprises configuring, by a configuration unit, a session holding timer associated with the network session. The method further comprises receiving, by the transceiver unit, one or more session update requests from the NF, wherein the one or more session update requests are associated with the network session. On receiving the one or more session update requests, the method further comprises determining, by a determination unit, a network session status associated with the network session based on the session holding timer, wherein the network session status is one of a network session suspended state status and a network session holding state status.

[0009] In an exemplary aspect of the present disclosure, the session create request comprises a session identifier (ID).

[0010] In an exemplary aspect of the present disclosure, the Network Function (NF) is one of a Session Management Function (SMF), a Policy Control Function (PCF), and a Charging Trigger Function (CTF).

[0011] In an exemplary aspect of the present disclosure, the step of configuring comprises: configuring, by the configuration unit, the session holding timer with the network session for a predefined time period based on a network session configuration associated with the network session.

[0012] In an exemplary aspect of the present disclosure, the method further comprises determining, by the determination unit, the network session holding state status in an event of receiving the one or more session update requests within the predefined time period.

[0013] In an exemplary aspect of the present disclosure, the method further comprises determining, by the determination unit, the network session suspended state status in an event of receiving the one or more session update requests after the predefined time period.

[0014] In an exemplary aspect of the present disclosure, on determining the network session holding state status, the method further comprises transmitting, by the transceiver unit, a diameter request to an Online Charging System (OCS), wherein the diameter request is associated with one of the session create request and the one or more session update requests. The method further comprises transmitting, by the transceiver unit, a positive response to the NF.

[0015] In an exemplary aspect of the present disclosure, on determining the network session suspended state status, the method further comprises transmitting, by the transceiver unit, a negative response to the NF.

[0016] Another aspect of the present disclosure may relate to a system for managing one or more session requests at a Charging Function (CHF). The system comprises a transceiver unit. The transceiver unit is configured to receive a session create request from a Network Function (NF). The system further comprises an initiation unit connected at least to the transceiver unit. The initiation unit is configured to initiate a network session based on the session create request. The transceiver unit is further configured to receive a target session update request from the NF, wherein the target session update request is a session terminate request. The system further comprises a configuration unit connected at least to the initiation unit. The configuration unit is configured to configure a session holding timer associated with the network session. The transceiver unit is further configured to receive one or more session update requests from the NF, wherein the one or more session update requests are associated with the network session. Thesystem further comprises a determination unit connected at least to the configuration unit. On receiving the one or more session update requests, the determination unit is configured to determine a network session status associated with the network session based on the session holding timer, wherein the network session status is one of a network session suspended state status and a network session holding state status.

[0017] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for managing one or more session requests at a Charging Function (CHF). The instructions include executable code which, when executed by one or more units of a system, causes a transceiver unit of the system to receive a session create request from a Network Function (NF). Further, the instructions include executable code which, when executed, causes an initiation unit to initiate a network session based on the session create request. Further, the instructions include executable code which, when executed, causes the transceiver unit to receive a target session update request from the NF, wherein the target session update request is a session terminate request. Further, the instructions include executable code which, when executed, causes a configuration unit to configure a session holding timer associated with the network session. Further, the instructions include executable code which, when executed, causes the transceiver unit to receive one or more session update requests from the NF, wherein the one or more session update requests are associated with the network session. Further, the instructions include executable code which, when executed, causes a determination unit to determine a network session status associated with the network session based on the session holding timer, on receiving the one or more session update requests, wherein the network session status is one of a network session suspended state status and a network session holding state status.OBJECTS OF THE DISCLOSURE

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

[0019] It is an object of the present disclosure to provide a system and a method for managing one or more session requests at a Charging Function (CHF).

[0020] It is another object of the present disclosure to provide a solution for receiving a session update request associated with the session create request and detecting by the CHF of the network the session update request is at least a session terminate request.

[0021] It is yet another object of the present disclosure to provide a solution for maintaining by the CHF a session suspended state for a predefined period of time based on the session terminate request received by the CHF from the SMF.

[0022] It is yet another object of the present disclosure to provide a solution for controlling a race condition at a Charging Function (CHF).DESCRIPTION OF THE DRAWINGS

[0023] 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. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.

[0024] FIG. 1 illustrates an exemplary block diagram representation of 5thgeneration core (5GC) network architecture;

[0025] 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;

[0026] FIG. 3 illustrates an exemplary block diagram of a system for managing one or more session requests at a Charging Function (CHF), in accordance with exemplary implementations of the present disclosure;

[0027] FIG. 4 illustrates an exemplary flow diagram for managing one or more session requests at a Charging Function (CHF) in accordance with exemplary implementations of the present disclosure;

[0028] FIG. 5 illustrates an exemplary signalling call flow diagram for managing one or more session requests at a Charging Function (CHF), in accordance with exemplary implementations of the present disclosure; and

[0029] FIG. 6 illustrates a method flow diagram for managing one or more session requests at a Charging Function (CHF) in accordance with exemplary implementations of the present disclosure.

[0030] The foregoing shall be more apparent from the following more detailed description of the disclosure.DETAILED DESCRIPTION

[0031] 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 may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.

[0032] 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.

[0033] 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, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.

[0034] 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, a structure diagram, or a blockdiagram. Although a flowchart may describe the operations as a sequential process, many of the operations may 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.

[0035] 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.

[0036] As used herein, 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 microcontroller, 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.

[0037] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smartdevice”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” 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. Also, the user device may contain at least one input means configured to receive an input from unit(s) which are required to implement the features of the present disclosure.

[0038] As used herein, “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. For example, 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.

[0039] As used herein “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 a 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.

[0040] 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.

[0041] As used herein the transceiver unit include at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information or a combination thereof between units / components within the system and / or connected with the system.

[0042] As discussed in the background section, the current known solutions have several shortcomings. The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing method and system of managing one or more session requests at a Charging Function (CHF).

[0043] The present invention discloses a novel solution to address the challenges of maintaining a session suspended state for a session terminate request, which lies in the strategic focus on controlling the race condition between incoming update and terminate requests on the CHF from the SMF side.

[0044] A crucial solution to this challenge involves the introduction of a configurable parameter on the CHF side. This parameter introduces a time delay whenever a terminate request is received, providing a buffer before the session is deleted. This deliberate delay ensures that the session is only removed after a specific period following the receipt of the terminate request.

[0045] The Gy and Sy interfaces take charge of establishing and maintaining peer connections, ensuring the seamless delivery of services. Notably, when the gySessionReleaseDelayTime parameter is configured, denoting a specified time period in seconds, the CHF retains sessions for this designated duration before initiating their release, thereby optimizing resource allocation and ensuring efficient network management. The Gy is diameter interface between CHF and OCS. This parameter holds significant implications for the operational efficiency and resource utilization within the CHF system.

[0046] The approaches of the present subject matter revolutionize the processing of update requests, allowing for smoother operations and significantly reducing anomalies within the session data. Ultimately, it guarantees the deletion of properly updated sessions, enhancing the overall efficiency and accuracy of the system. This innovation marks a significant advancement in managing concurrent requests within the CHF-SMF interaction.

[0047] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0048] FIG. 1 illustrates an exemplary block diagram representation of 5thgeneration core (5GC) network architecture, in accordance with exemplary implementation of the present disclosure. As shown in FIG. 1, the 5GC network architecture

[0100] includes a user equipment (UE)

[0102] , a radio access network (RAN)

[0104] , an access and mobility management function (AMF)

[0106] , a Session Management Function (SMF)

[0108] , a Service Communication Proxy (SCP)

[0110] , an Authentication Server Function (AUSF)

[0112] , a Network Slice Specific Authentication and Authorization Function (NSSAAF)

[0114] , a Network Slice Selection Function (NSSF)

[0116] , a Network Exposure Function (NEF)

[0118] , a Network Repository Function (NRF)

[0120] , a Policy Control Function (PCF)

[0122] , a Unified Data Management (UDM)

[0124] , an application function (AF)

[0126] , a User Plane Function (UPF)

[0128] , a data network (DN)

[0130] , a Charging Function

[0132] , wherein all the components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure.

[0049] Radio Access Network (RAN)

[0104] is the part of a mobile telecommunications system that connects user equipment (UE)

[0102] 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.

[0050] Access and Mobility Management Function (AMF)

[0106] 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.

[0051] Session Management Function (SMF)

[0108] 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.

[0052] Service Communication Proxy (SCP)

[0110] 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.

[0053] Authentication Server Function (AUSF)

[0112] is a network function in the 5G core responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens.

[0054] Network Slice Specific Authentication and Authorization Function (NSSAAF)

[0114] is a network function that provides authentication and authorization services specific to network slices. It ensures that UEs can access only the slices for which they are authorized.

[0055] Network Slice Selection Function (NSSF)

[0116] 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.

[0056] Network Exposure Function (NEF)

[0118] is a network function that exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.

[0057] Network Repository Function (NRF)

[0120] 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.

[0058] Policy Control Function (PCF)

[0122] is a network function responsible for policy control decisions, such as QoS, charging, and access control, based on subscriber information and network policies.

[0059] Unified Data Management (UDM)

[0124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information.

[0060] Application Function (AF)

[0126] is a network function that represents external applications interfacing with the 5G core network to access network capabilities and services.

[0061] User Plane Function (UPF)

[0128] is a network function responsible for handling user data traffic, including packet routing, forwarding, and QoS enforcement.

[0062] Data Network (DN)

[0130] 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.

[0063] Charging Function (CHF)

[0132] refers refer to a network function responsible for converged online charging and offline charging functionalities. The CHF

[0132] provides Quota, Re-authorisation triggers, Notifications when Charging Domain determines rating conditions is affected or when CHF determines to terminate the charging service. The CHF

[0132] receives service usage reports from NF Service Consumers. The CHF

[0132] is also responsible for generation of call data records.

[0064] The 5GC network architecture also comprises a plurality of interfaces for connecting the network functions with a network entity for performing the network functions. The NSSF

[0116] is connected with the network entity via the interface denoted as (Nnssf) interface in FIG. 1. The NEF

[0118] is connected with the network entity via the interface denoted as (Nnef) interface in FIG. 1. The NRF

[0120] is connected with the network entity via the interface denoted as (Nnrf) interface in FIG. 1. The PCF

[0122] is connected with the network entity via the interface denotedas (Npcf) interface in FIG. 1. The UDM

[0124] is connected with the network entity via the interface denoted as (Nudm) interface in FIG. 1. The AF

[0126] is connected with the network entity via the interface denoted as (Naf) interface in FIG. 1. The NSSAAF

[0114] is connected with the network entity via the interface denoted as (Nnssaaf) interface in FIG. 1. The AUSF

[0112] is connected with the network entity via the interface denoted as (Nausf) interface in FIG. 1. The AMF

[0106] is connected with the network entity via the interface denoted as (Namf) interface in FIG. 1. The SMF

[0108] is connected with the network entity via the interface denoted as (Nsmf) interface in FIG. 1. The SMF

[0108] is connected with the UPF

[0128] via the interface denoted as (N4) interface in FIG. 1. The UPF

[0128] is connected with the RAN

[0104] via the interface denoted as (N3) interface in FIG. 1. The UPF

[0128] is connected with the DN

[0130] via the interface denoted as (N6) interface in FIG. 1. The CHF

[0132] is connected with the network entity via the interface demoted as (Nchf) interface in FIG. 1. The RAN

[0104] is connected with the AMF

[0106] via the interface denoted as (N2) in FIG. 1. The AMF

[0106] is connected with the RAN

[0104] via the interface denoted as (Nl) in FIG. 1. The UPF

[0128] is connected with other UPF

[0128] via the interface denoted as (N9) in FIG. 1.

[0065] The interfaces such as Nnssf, Nnef, Nnrf, Npcf, Nudm, Naf, Nnssaaf, Nausf, Namf, Nsmf, N9, N6, N4, N3, N2, and Nl can be referred to as a communication channel between one or more functions or modules for enabling exchange of data or information between such functions or modules, and network entities.

[0066] FIG. 2 illustrates an exemplary block diagram of a computing device

[0200] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an implementation, the computing device

[0200] may also implement a method for managing one or more session requests at a Charging Function (CHF) utilising the system

[0300] , as would be described later in the foregoing description. In another implementation, the computing device

[0200] itself implements the method for managing one or more session requests at a Charging Function (CHF) using one or more units configured within the computing device

[0200] , wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.

[0067] The computing device

[0200] may include a bus

[0202] or other communication mechanism for communicating information, and a hardware processor

[0204] coupled with bus

[0202] for processing information. The hardware processor

[0204] may be, for example, a general-purpose microprocessor. The computing device

[0200] may also include a main memory

[0206] , such as arandom-access memory (RAM), or other dynamic storage device, coupled to the bus

[0202] for storing information and instructions to be executed by the processor

[0204] , The main memory

[0206] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor

[0204] , Such instructions, when stored in non-transitory storage media accessible to the processor

[0204] , render the computing device

[0200] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device

[0200] further includes a read only memory (ROM)

[0208] or other static storage device coupled to the bus

[0202] for storing static information and instructions for the processor

[0204] ,

[0068] A storage device

[0210] , such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus

[0202] for storing information and instructions. The computing device

[0200] may be coupled via the bus

[0202] to a display

[0212] , 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. An input device

[0214] , including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus

[0202] for communicating information and command selections to the processor

[0204] , Another type of user input device may be a cursor controller

[0216] , such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor

[0204] , and for controlling cursor movement on the display

[0212] , 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.

[0069] The computing device

[0200] 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

[0200] causes or programs the computing device

[0200] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device

[0200] in response to the processor

[0204] executing one or more sequences of one or more instructions contained in the main memory

[0206] , Such instructions may be read into the main memory

[0206] from another storage medium, such as the storage device

[0210] , Execution of the sequences of instructions contained in the main memory

[0206] causes the processor

[0204] to perform the process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.

[0070] The computing device

[0200] also may include a communication interface

[0218] coupled to the bus

[0202] , The communication interface

[0218] provides a two-way data communication coupling to a network link

[0220] that is connected to a local network

[0222] , For example, the communication interface

[0218] 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. As another example, the communication interface

[0218] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface

[0218] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.

[0071] The computing device

[0200] can send messages and receive data, including program code, through the network(s), the network link

[0220] and the communication interface

[0218] , In the Internet example, a server

[0230] might transmit a requested code for an application program through the Internet

[0228] , the ISP

[0226] , the local network

[0222] , the host

[0224] and the communication interface

[0218] , The received code may be executed by the processor

[0204] as it is received, and / or stored in the storage device

[0210] , or other non-volatile storage for later execution.

[0072] Referring to FIG. 3, an exemplary block diagram of a system

[0300] for managing one or more session requests at a Charging Function (CHF), in accordance with the exemplary implementations of the present disclosure, is shown. In one example, the system

[0300] may be implemented as or within a Charging Function (CHF). In such cases, the system

[0300] , implemented as the CHF, may be understood with respect to the CHF

[0132] as explained in conjunction with FIG. 1.

[0073] In one example, the system

[0300] may be in communication with other network entities / components known to a person skilled in the art. Such network entities / components have not been depicted and explained here for the sake of brevity.

[0074] Further, FIG. 4 illustrates an exemplary flow diagram for managing one or more session requests at a Charging Function (CHF) in accordance with exemplary implementations of the present disclosure.

[0075] Furthermore, FIG. 5 illustrates an exemplary signalling call flow diagram

[0500] for managing one or more session requests at a Charging Function (CHF), in accordance with exemplary implementations of the present disclosure.

[0076] It may be noted that FIG. 3, FIG. 4, and FIG. 5 have been explained simultaneously and may be read in conjunction with each other.

[0077] As depicted in FIG. 3, the system

[0300] may include at least one transceiver unit

[0302] , at least one initiation unit

[0304] , at least one configuration unit

[0306] and at least one determination unit

[0308] , In cases where the system

[0300] may be implemented as or within the Charging Function (CHF), the different aforementioned units may be a part of such Charging Function (CHF).

[0078] Also, all of the components / units of the system

[0300] are assumed to be connected to each other unless otherwise indicated below. As shown in FIG. 3, all units shown within the system

[0300] should also be assumed to be connected to each other. Also, in FIG. 3 only a few units are shown, however, the system

[0300] may comprise multiple such units or the system

[0300] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system

[0300] may be present in a user device / user equipment

[0102] to implement the features of the present disclosure. In another implementation, the system

[0300] may reside in a server or a network entity. In yet another implementation, the system

[0300] may reside partly in the server / network entity and partly in the user device.

[0079] The system

[0300] is configured for managing one or more session requests at a Charging Function (CHF) with the help of the interconnection between the components / units of the system

[0300] ,

[0080] In operation, the transceiver unit

[0302] may receive a session create request from a Network Function (NF). This has been depicted by Step

[0402] in FIG. 4 and Step

[0502] in FIG. 5.

[0081] In one example, the Network Function (NF) may be one of a Session Management Function (SMF), a Policy control function (PCF), or a Charging Trigger Function (CTF). It may be noted that the SMF and PCF, as mentioned here, may be understood as SMF

[0108] and PCF

[0122] as explained in conjunction with FIG. 1. The description of the same have not been repeated here for the sake of brevity.

[0082] A Charging Trigger Function (CTF) is a network component responsible for initiating charging actions based on specific events or conditions related to network services. The CTF detects triggering events, such as the start of a new session or changes in service usage, and subsequently initiates the necessary charging processes. This includes sending requests to a charging system, updating usage records, and calculating costs based on predefined rules or policies.

[0083] It may be noted that the aforementioned examples of NFs are not to be construed to limit the scope of the present subject matter in any manner. The NF, in the context of the present subject matter, may be implemented as any other NF as well. All such other examples would lie within the scope of the present subject matter.

[0084] The session create request is an operation used to initiate a new session within the network. Also, in certain other implementations of the present disclosure, the session create request may be for creating new session. In an example in case of NF being SMF for converged charging, for creating new session, a service operation may be performed such as a Nchf_ConvergedCharging_Create service operation which provides means for NF (CTF) to request quotas for service delivery or initial report of service usage. Also, in case of NF being PCF and the spending limit control, in an example, for creating new session, the NF service consumer may send an HTTP POST request to create a subscription for retrieval of the policy counter status and spending limit reporting. The request includes subscription information, which identifies the user or subscriber associated with the session, as well as Service Data Flow (SDF) information, which provides details on the services being used and the associated quality of service (QoS) parameters. Additionally, the charging data, which includes the metrics used to calculate the cost of the session, such as data volume or the duration of the session, is included. The request may also specify the requested service units, indicating the network resources being required, such as additional data or session time.

[0085] Continuing further, in an example, the session create request may include a session identifier (ID). In the context of the present subject matter, the session identifier may be understood as a unique string that identifies the session being established. The session ID is generated by the initiating entity, such as a Network Function (NF).

[0086] In one embodiment of the present disclosure, upon receiving the session create request, an initiation unit

[0304] may initiate a network session based on the session create request. This has been depicted by Step

[0404] in FIG. 4 and Step

[0504] in FIG. 5. As would be understood, the network session may refer to a session which utilizes telecommunications network resources and related services which may be used for online charging of network / user sessions, e.g. voice calls, IP CAN bearers, IP CAN session or IMS sessions.

[0087] In an implementation of the present disclosure, the network session refers to the communication established between a user’s equipment (UE) and the network. The creation of a network session activates a charging event at the CHF, where the resources used during the session are monitored and reserved as required. This session is identified by a unique session identifier (ID) and includes various parameters related to quality of service, service data flows, and charging information.

[0088] Continuing further, thereafter, once the session has been initiated, the transceiver unit

[0302] may then subsequently receive a target session update request from the NF. The target session update request may be a session terminate request. Similarly, in another example, for updating the existing session, a service operation may be performed such as a Nchf_ConvergedCharging_Update service operation which provides means for NF (CTF) to update the charging data. Similarly, in another example, for updating the existing session, the NF service consumer may send an HTTP PUT request to modify the subscription for retrieval of the policy counter status and spending limit reporting. This has been depicted by Step

[0406] in FIG. 4 and Step

[0506] in FIG. 5.

[0089] In an implementation of the present disclosure, after the session has been successfully established a communication from the NF, subsequently, the NF may instruct the transceiver unit

[0302] to terminate the session. The session terminate request is used to notify the CHF that a particular network session is finishing. The target session update request activated when the network or user decides to end the session, either due to normal session completion, network management requirements, or user-initiated actions. Upon receiving this request, the transceiver unit

[0302] may proceed to terminate the session. In an example, for terminating the existing session, a service operation may be performed such as a Nchf ConvergedCharging Release service operation which provides means for NF (CTF) to terminate charging Session. Also, in another example, for terminating the existing session, a service operation may be performed such as Nchf SpendingLimitControl Unsubscribe service operation, in which the NF service consumermay send an HTTP DELETE request, along with a subscription Id for identification of the existing subscription to be deleted, to remove the corresponding subscription. This has been depicted by Step

[0406] in FIG. 4 and Step

[0506] in FIG. 5.

[0090] After the session has been terminated, the configuration unit

[0306] may configure a session holding timer associated with the network session. This has been depicted by Step

[0408] in FIG. 4 and Step

[0508] in FIG. 5.

[0091] In an implementation of the present disclosure, the session holding timer is a mechanism used to manage the duration for which the session remains active, after receiving the session terminate request from the NF. This timer defines how long the session will be maintained by the system

[0300] , even in the absence of active data transmission.

[0092] The configuration of this timer may depend on factors such as network policies, Quality of Service (QoS) requirements, or user preferences. Once the session holding timer expires, and if no further communication or update is received, the session may be automatically terminated to free up network resources.

[0093] In an example, the configuration unit

[0306] may further configure the session holding timer with the network session for a predefined time period based on a network session configuration associated with the network session. The configuration associated with the network session may include the predefined time period, which determines how long the session will remain active even in the absence of data transmission.

[0094] The configuration unit

[0306] takes into account the session configuration associated with the network session. These configurations may include the type of service being used, user subscription levels. The session holding timer confirms that the session remains open for a specified duration, allowing for data exchange without immediate termination due to inactivity. Once the session holding timer is configured, the session may stay active for the predefined time period. If no further communication or updates occur during this period, the session may be automatically terminated.

[0095] Continuing further, thereafter, the transceiver unit

[0302] may receive one or more session update requests from the NF. The one or more session update requests may be associated with the network session. This has been depicted by Step

[0410] in FIG. 4 and Step

[0510] in FIG. 5.

[0096] In an implementation of the present disclosure, these session update requests are related to the ongoing network session and may involve changes or modifications to the session.

[0097] For example, the requests may update parameters like the session duration, Quality of Service (QoS) settings, resource allocation.

[0098] The session update requests may be sent by the NF at various points during the session, depending on the network's needs (such as network load, faults and failure) or user activity (such as data usage). These updates confirm that the session remains associated with current network conditions or user requirements.

[0099] Further, on receiving the session update request, the determination unit

[0308] may ascertain if the session update request is received within the predefined time period (of the session holding timer). This has been depicted by Step / Block

[0412] in FIG. 4. For example, the determination unit may determine a network session status associated with the network session based on the session holding timer. The network session status may be one of a network session suspended state status and a network session holding state status.

[0100] If the one or more session update requests is received within the predefined time period (as depicted by ‘Yes’ path from block

[0412] in FIG. 4), the determination unit

[0308] may determine the network session status as ‘network session holding state status’.

[0101] The network session holding state status indicates that the timer has not yet expired and the session is actively maintained and waiting for further activity or data exchange. The network session may continue to operate as expected, rather than transitioning to a suspended or terminated state. For example, an ongoing file transfer or an active VoIP call where the network continuously manages and supports the session.

[0102] In response to determining that the network session is in the holding state, the transceiver unit

[0302] , may transmit a diameter request to an Online Charging System (OCS)

[0134] , wherein the diameter request is associated with one of the session create request and the one or more session update requests. This has been depicted by Step

[0512] in FIG. 5.

[0103] When the determination unit

[0308] finds that the network session is in the holding state, the transceiver unit

[0302] takes specific actions. First, it sends a diameter request to the Online Charging System (OCS)

[0134] , This diameter request is related to either the initial session create request or any of the one or more session update requests previously received. The Diameter protocol is used for communication between network entities to handle charging, authentication, and other network management tasks. The Diameter protocol may also utilize for communication between the CHF and other network functions. The diameter request for charging typically includes attributes such as the session identifier (ID), which uniquely identifies the charging session, and origin and destination host addresses, specifying the sender and receiver of the request.

[0104] In addition to sending the diameter request, the transceiver unit

[0302] also transmits a positive response back to the Network Function (NF). This has been depicted by Step

[0414] in FIG. 4 and Step

[0514] in FIG. 5.

[0105] The positive response indicates that the session is being properly maintained in the holding state and that the requested updates or configurations have been acknowledged and are being processed.

[0106] Continuing further, on the other hand, if the one or more session update requests is received after the predefined time period (as depicted by ‘No’ path from block

[0412] in FIG. 4), the determination unit

[0308] may determine the network session status as ‘network session suspended state status’.

[0107] The network session suspended state status indicates that the network session has been terminated, and not available for data transfer. For example, if the timer has expired, the session may no longer be in the holding state and may need to be reassessed or moved to a different state.

[0108] If predefined time period for the session holding timer has lapsed and updates are still being received, the determination unit

[0308] checks if the session has transitioned from an active holding state to a suspended state. In the suspended state, the session is temporarily paused, and no active data processing is occurring, but the session is still maintained in the system and may be resumed later.

[0109] Furthermore, upon determining that the network session is in the suspended state, the transceiver unit

[0302] may transmit a negative response to the NF. This has been depicted by Step

[0416] in FIG. 4 and Step

[0516] in FIG. 5.

[0110] This negative response indicates that the session is not currently active and is instead in a suspended state. The response informs the NF that the session is paused and may need further action or handling, such as resuming the session or addressing any issues that caused the suspension.

[0111] Referring to FIG. 6, an exemplary method flow diagram

[0600] for managing one or more session requests at a Charging Function (CHF), in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method

[0600] is performed by the system

[0300] , Further, in an implementation, the system

[0300] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 6, the method

[0600] starts at step

[0602] ,

[0112] At step

[0604] , the method

[0600] comprises, receiving, by a transceiver unit

[0302] , a session create request from a Network Function (NF). Also, in certain other implementations of the present disclosure, the session create request may be for creating new session. In an example in case of NF being SMF for converged charging, for creating new session, a service operation may be performed such as a Nchf ConvergedCharging Create service operation which provides means for NF (CTF) to request quotas for service delivery or initial report of service usage. Also, in case of NF being PCF and the spending limit control, in an example, for creating new session, the NF service consumer may send an HTTP POST request to create a subscription for retrieval of the policy counter status and spending limit reporting.

[0113] In operation, the transceiver unit

[0302] may receive a session create request from a Network Function (NF). In one example, the Network Function (NF) may be one of a Session Management Function (SMF), a Policy control function (PCF), or a Charging Trigger Function (CTF).

[0114] Continuing further, in an example, the session create request may include a session identifier (ID). In the context of the present subject matter, the session identifier may be understood as a unique string that identifies the session being established. The session ID is generated by the initiating entity, such as a Network Function (NF).

[0115] At step

[0606] , the method

[0600] comprises, initiating, by an initiation unit

[0304] , a network session based on the session create request.

[0116] In one embodiment of the present disclosure, upon receiving the session create request, an initiation unit

[0304] may initiate a network session based on the session create request. As would be understood, the network session may refer to a session which utilizes telecommunications network resources and related services which may be used for online charging of network / user sessions, e.g. voice calls, IP CAN bearers, IP CAN session or IMS sessions.

[0117] In an implementation of the present disclosure, the network session refers to the communication established between a user’s equipment (UE) and the network. The creation of a network session activates a charging event at the CHF, where the resources used during the session are monitored and reserved as required. This session is identified by a unique session identifier (ID) and includes various parameters related to quality of service, service data flows, and charging information.

[0118] At step

[0608] , the method

[0600] comprises, receiving, by the transceiver unit

[0302] , a target session update request from the NF, wherein the target session update request is a session terminate request.

[0119] Continuing further, thereafter, once the session has been initiated, the transceiver unit

[0302] may then subsequently receive a target session update request from the NF. The target session update request may be a session terminate request.

[0120] In an implementation of the present disclosure, after the session has been successfully established a communication from the NF, subsequently, the NF may instruct the transceiver unit

[0302] to terminate the session. The session terminate request is used to notify the CHF that a particular network session is finishing. The target session update request activated when the network or user decides to end the session, either due to normal session completion, network management requirements, or user-initiated actions. Upon receiving this request, the transceiver unit

[0302] may proceed to terminate the session. In an example, for terminating the existing session, a service operation may be performed such as a Nchf ConvergedCharging Release service operation which provides means for NF (CTF) to terminate charging Session. Also, in another example, for terminating the existing session, a service operation may be performed such as Nchf SpendingLimitControl Unsubscribe service operation, in which the NF service consumermay send an HTTP DELETE request, along with a subscription Id for identification of the existing subscription to be deleted, to remove the corresponding subscription.

[0121] At step

[0610] , the method

[0600] comprises, configuring, by a configuration unit

[0306] , a session holding timer associated with the network session.

[0122] After the session has been terminated, the configuration unit

[0306] may configure a session holding timer associated with the network session.

[0123] In an implementation of the present disclosure, the session holding timer is a mechanism used to manage the duration for which the session remains active, after receiving the session terminate request from the NF. This timer defines how long the session will be maintained by the system

[0300] , even in the absence of active data transmission.

[0124] In an example, the configuration unit

[0306] may further configure the session holding timer with the network session for a predefined time period based on a network session configuration associated with the network session. The configuration associated with the network session may include the predefined time period, which determines how long the session will remain active even in the absence of data transmission.

[0125] The configuration unit

[0306] takes into account the session configuration associated with the network session. These configurations may include the type of service being used, user subscription levels. The session holding timer confirms that the session remains open for a specified duration, allowing for data exchange without immediate termination due to inactivity. Once the session holding timer is configured, the session may stay active for the predefined time period. If no further communication or updates occur during this period, the session may be automatically terminated.

[0126] At step

[0612] , the method

[0600] comprises, receiving, by the transceiver unit

[0302] , one or more session update requests from the NF, wherein the one or more session update requests are associated with the network session. Similarly, in another example, for updating the existing session, a service operation may be performed such as a Nchf ConvergedCharging Update service operation which provides means for NF (CTF) to update the charging data. Similarly, in another example, for updating the existing session, the NF service consumer may send an HTTPPUT request to modify the subscription for retrieval of the policy counter status and spending limit reporting.

[0127] Continuing further, thereafter, the transceiver unit

[0302] may receive one or more session update requests from the NF. The one or more session update requests may be associated with the network session.

[0128] In an implementation of the present disclosure, these session update requests are related to the ongoing network session and may involve changes or modifications to the session.

[0129] For example, the requests may update parameters like the session duration, Quality of Service (QoS) settings, resource allocation.

[0130] The session update requests may be sent by the NF at various points during the session, depending on the network's needs (such as network load, faults and failure) or user activity (such as data usage). These updates confirm that the session remains associated with current network conditions or user requirements.

[0131] At step

[0614] , the method

[0600] comprises, on receiving the one or more session update requests, determining, by a determination unit

[0308] , a network session status associated with the network session based on the session holding timer, wherein the network session status is one of a network session suspended state status and a network session holding state status.

[0132] Further, on receiving the session update request, the determination unit

[0308] may ascertain if the session update request is received within the predefined time period (of the session holding timer). For example, the determination unit may determine a network session status associated with the network session based on the session holding timer. The network session status may be one of a network session suspended state status and a network session holding state status.

[0133] If the one or more session update requests is received within the predefined time period, the determination unit

[0308] may determine the network session status as ‘network session holding state status’.

[0134] The network session holding state status indicates that the timer has not yet expired and the session is actively maintained and waiting for further activity or data exchange. The networksession may continue to operate as expected, rather than transitioning to a suspended or terminated state.

[0135] In response to determining that the network session is in the holding state, the transceiver unit

[0302] , may transmit a diameter request to an Online Charging System (OCS)

[0134] , wherein the diameter request is associated with one of the session create request and the one or more session update requests.

[0136] When the determination unit

[0308] finds that the network session is in the holding state, the transceiver unit

[0302] takes specific actions. First, it sends a diameter request to the Online Charging System (OCS)

[0134] , In addition to sending the diameter request, the transceiver unit

[0302] also transmits a positive response back to the Network Function (NF). The positive response indicates that the session is being properly maintained in the holding state and that the requested updates or configurations have been acknowledged and are being processed.

[0137] On the other hand, if the one or more session update requests is received after the predefined time period, the determination unit

[0308] may determine the network session status as ‘network session suspended state status’.

[0138] The network session suspended state status indicates that the network session has been terminated, and not available for data transfer.

[0139] Furthermore, upon determining that the network session is in the suspended state, the transceiver unit

[0302] may transmit a negative response to the NF. This negative response indicates that the session is not currently active and is instead in a suspended state. The response informs the NF that the session is paused and may need further action or handling, such as resuming the session or addressing any issues that caused the suspension.

[0140] Thereafter, the method

[0600] terminates at step

[0616] ,

[0141] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for managing one or more session requests at a Charging Function (CHF). The instructions include executable code which, when executed by one or more units of a system

[0300] , causes a transceiver unit

[0302] of the system

[0300] to receive a session create request from a Network Function (NF). Further, the instructions include executable code which, whenexecuted, causes an initiation unit

[0304] to initiate a network session based on the session create request. Further, the instructions include executable code which, when executed, causes the transceiver unit

[0302] to receive a target session update request from the NF, wherein the target session update request is a session terminate request. Further, the instructions include executable code which, when executed, causes a configuration unit

[0306] to configure a session holding timer associated with the network session. Further, the instructions include executable code which, when executed, causes the transceiver unit

[0302] to receive one or more session update requests from the NF, wherein the one or more session update requests are associated with the network session. Further, the instructions include executable code which, when executed, causes a determination unit

[0308] to determine a network session status associated with the network session based on the session holding timer, on receiving the one or more session update requests, wherein the network session status is one of a network session suspended state status and a network session holding state status.

[0142] As is evident from the above, the present disclosure provides a technically advanced solution for managing one or more session requests at a Charging Function (CHF). As disclosed by the present solution, the technical advancement lies in its meticulous management of session requests, controlling race conditions, and effectively reducing the likelihood of exceptions occurring.

[0143] Firstly, it ensures impeccable data consistency by processing requests in the expected order, preventing scenarios where terminate requests might lead to updates on non-existing sessions, thereby averting data inconsistency and request loss. Secondly, it significantly diminishes error probabilities through the implementation of timer technology. This technology facilitates the delay of queued threads, allowing preceding threads to execute first, thus minimizing potential errors. Moreover, this advancement ensures the success of call flows by synchronizing create, update, and terminate requests, preventing disruptions caused by latency or other influencing factors. Lastly, it addresses the critical issue of handling race conditions when update and terminate requests coincide. The introduced parameter plays a pivotal role in effectively managing this scenario, enhancing the overall robustness and reliability of the system. This technological breakthrough marks a substantial stride forward in ensuring seamless and error-free operation within the CHF- SMF interaction.

[0144] While considerable emphasis has been placed herein on the disclosed implementations, it will be appreciated that many implementations can be made and that many changes can be madeto the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.

[0145] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components / units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.

Claims

We Claim:

1. A method [600] for managing one or more session requests at a Charging Function (CHF), the method [600] comprising: receiving [604], by a transceiver unit [302], a session create request from a Network Function (NF); initiating [606], by an initiation unit [304], a network session based on the session create request; receiving [608], by the transceiver unit [302], a target session update request from the NF, wherein the target session update request is a session terminate request; configuring [610], by a configuration unit [306], a session holding timer associated with the network session; receiving [612], by the transceiver unit [302], one or more session update requests from the NF, wherein the one or more session update requests are associated with the network session; and on receiving the one or more session update requests, determining [614], by a determination unit [308], a network session status associated with the network session based on the session holding timer, wherein the network session status is one of a network session suspended state status and a network session holding state status.

2. The method [600] as claimed in claim 1, wherein the session create request comprises a session identifier (ID).

3. The method [600] as claimed in claim 1, wherein the Network Function (NF) is one of a Session Management Function (SMF), a Policy Control Function (PCF), and a Charging Trigger Function (CTF).

4. The method [600] as claimed in claim 1, wherein the step of configuring [610] comprises: configuring, by the configuration unit [306], the session holding timer with the network session for a predefined time period based on a network session configuration associated with the network session.

5. The method [600] as claimed in claim 4, further comprising: determining, by the determination unit [308], the network session holding state status in an event of receiving the one or more session update requests within the predefined time period.

6. The method [600] as claimed in claim 4, further comprising: determining, by the determination unit [308], the network session suspended state status in an event of receiving the one or more session update requests after the predefined time period.

7. The method [600] as claimed in claim 5, wherein, on determining the network session holding state status, the method further comprises: transmitting, by the transceiver unit [302], a diameter request to an Online Charging System (OCS) [134], wherein the diameter request is associated with one of the session create request and the one or more session update requests; and transmitting, by the transceiver unit [302], a positive response to the NF.

8. The method [600] as claimed in claim 6, wherein, on determining the network session suspended state status, the method further comprises: transmitting, by the transceiver unit [302], a negative response to the NF.

9. A system [300] for managing one or more session requests at a Charging Function (CHF), the system [300] comprising: a transceiver unit [302], wherein the transceiver unit [302] is configured to: receive a session create request from a Network Function (NF); an initiation unit [304] connected at least to the transceiver unit [302], wherein the initiation unit [304] is configured to: initiate a network session based on the session create request; the transceiver unit [302] is further configured to: receive a target session update request from the NF, wherein the target session update request is a session terminate request; a configuration unit [306] connected at least to the initiation unit [304], wherein the configuration unit [306] is configured to: configure a session holding timer associated with the network session; the transceiver unit [302] is further configured to: receive one or more session update requests from the NF, wherein the one or more session update requests are associated with the network session; and a determination unit [308] connected at least to the configuration unit [306], wherein the determination unit [308] is configured to: on receiving the one or more session update requests, determine a network session status associated with the network session based on the session holding timer, wherein the network session status is one of a network session suspended state status and a network session holding state status.

10. The system [300] as claimed in claim 9, wherein the session create request comprises a session identifier (ID).

11. The system [300] as claimed in claim 9, wherein the Network Function (NF) is one of a Session Management Function (SMF), a Policy Control Function (PCF), and a Charging Trigger Function (CTF).

12. The system [300] as claimed in claim 9, wherein the configuration unit [306] is further configured to: configure the session holding timer with the network session for a predefined time period based on a network session configuration associated with the network session.

13. The system [300] as claimed in claim 12, wherein the determination unit [308] is further configured to: determine the network session holding state status in an event of receiving the one or more session update requests within the predefined time period.

14. The system [300] as claimed in claim 12, wherein the determination unit [308] is further configured to: determine the network session suspended state status in an event of receiving the one or more session update requests after the predefined time period.

15. The system [300] as claimed in claim 13, wherein the transceiver unit [302], on determination of the network session holding state status, is further configured to: transmit a diameter request to an Online Charging System (OCS) [134], wherein the diameter request is associated with one of the session create request and the one or more session update requests; and transmit a positive response to the NF.

16. The system [300] as claimed in claim 14, wherein the transceiver unit [302], on determination of the network session suspended state status, is further configured to: transmit a negative response to the NF.

17. A non-transitory computer-readable storage medium storing instructions for managing one or more session requests at a Charging Function (CHF), the instructions comprising executable code which, when executed by one or more units of a system [300], causes: a transceiver unit [302] to receive a session create request from a Network Function (NF);an initiation unit [304] to initiate a network session based on the session create request; the transceiver unit [302] to receive a target session update request from the NF, wherein the target session update request is a session terminate request; a configuration unit [306] to configure a session holding timer associated with the network session; the transceiver unit [302] to receive one or more session update requests from the NF, wherein the one or more session update requests are associated with the network session; and a determination unit [308] to determine a network session status associated with the network session based on the session holding timer, on receiving the one or more session update requests, wherein the network session status is one of a network session suspended state status and a network session holding state status.

Images