System and method for managing interface sessions

Abstract

The present disclosure relates to a system(108) and a method(500) for managing interface sessions. The system(108) receives a first set of signals indicative of 5 request for services from a network entity via a network. The system(108) determines whether a Policy Counter ID (PCID) is to be requested from an Online Charging System (OCS) based on a set of parameters received via the first set of signals. The system(108) transmits a second set of signals indicative of a request to receive the PCID from the OCS. The system(108) receives the PCID to fulfil request for the services made by the network entity. The system(108) determines whether the PCID needs to be requested from the OCS by applying logical operators to the set of parameters. The system(108) provides precedence to a first subset of the set of parameters over a second subset of parameters.

Description

SYSTEM AND METHOD FOR MANAGING INTERFACE 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 managing interface sessions. In particular, the present disclosure relates to a system and a method for managing Sy interface sessions.BACKGROUND OF DISCLOSURE

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

[0004] Policy and Charging Rules Functions (PCRFs) and Policy Control Function (PCFs) play an important role in service data flow detection, policy enforcement, and flow-based charging, including control of slicing and new control mechanisms in cellular networks. The PCRFs or PCFs may interact with one or more network entities, which may include an Online Charging Systems (OCS) thatallow service providers to charge users or customers in real-time based on service usage. A PCRF interacts with the OCS to fetch charging rules associated with a user.

[0005] The PCRF may communicate with the OCS using a Sy interface through a Diameter Protocol, where the OCS serves as a Diameter server while the Sy interface act as a reference point. The Sy interface may enable the transfer of information relating to a subscriber spending from the OCS to the PCRF and supports several functions, including generation and transfer of policy counters identifiers (PCIDs), where the PCIDs have policy rules of the users stored therein.

[0006] Existing approaches on the cellular networks are silent on protocols that needs to be followed for enabling such communication. Further, existing approaches also do not provide any technique for managing and controlling Sy or Charging Function (CHF) sessions for the same subscriber by PCF nodes or PCRF nodes, thereby leading to inefficiencies, and consequent degradation in network performance. Further, a lack of caching and repeated fetching of information from the OCS may lead to unnecessary delays and redundant use of the Sy interface.

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

[0008] In an embodiment, a method for managing interface sessions is disclosed. The method includes receiving a policy control create request from a session management function (SMF) or a packet data network gateway (PGW) through at least one interface. The method includes checking a plurality of trigger conditions in response to receiving the policy control create request. The method further includes controlling a flow of one or more messages in the at least one interface based on at least one of a matching of one or more of the plurality of trigger conditions and a configuration flag condition. The configuration flagcondition is one a false flag condition and a true flag condition.

[0009] In some embodiments, the one or more of plurality of trigger conditions includes a set of parameters comprising an access point name (APN) or a Data Network Name (DPN), an International Mobile Subscriber Identity (IMSI) range or a Subscription Permanent Identifier (SUPI) range, a mobile station international subscriber directory number (MSISDN) range or a generic public subscription identifier (GPSI) range, a plurality of custom subscriber provisioning fields, and a Network Slice Selection Assistance Information (NSSAI).

[0010] In some embodiments, when the configuration flag condition is the false flag condition, initiating one of a sending limit request (SLR) or a spending limit control subscriber request to at least one of a charging function (CHF) and an online charging system (OCS) based on matching of the plurality of trigger conditions; receiving a spending limit answer (SLA) including a policy control identifier (PCID); and storing a session information associated with the at least one interface or the CHF based on the received SLA and the PCID.

[0011] In some embodiments, when the configuration flag condition is the true flag condition, initiating the at least one of a CHF request and an OCS request on each Credit Control Request (CCR) based on the matching of the one or more of the plurality of trigger conditions; receiving a new SLA response in response to initiating the at least one of the CHF request and the OCS request; and updating the session information associated with the at least one interface or the CHF to at least one of an IMSI or a SUPI in response to receiving the new SLA.

[0012] In some embodiments, the method further includes maintaining a single session information associated with the at least one interface or the CHF for the at least one of the IMSI or the SUPI, wherein a set of pre-triggered messages triggered for the at least one of the IMSI or the SUPI are prevented from triggering, on receiving the CCR.

[0013] In some embodiments, the set of parameters are configured to support multiple values including comma-separated values, wildcard characters, and logical operators.

[0014] In some embodiments, the method includes receiving an activity parameter associated with a user equipment (UE). The activity parameter is configured to indicate whether the UE is in a pre-active state, an active state, or a suspended state. When the activity parameter is in the pre-active state, allowing the UE to process a plurality of messages on a plurality of interfaces. When the activity parameter is in the active state, triggering a transmission of the plurality of messages. When the activity parameter is in the suspended state, rejecting the policy control create request.

[0015] In some embodiments, the method further includes sending the SLR to one of UEs using one of the APN or the DPN by provisioning a different custom subscriber provisioning field value in a subscriber profile.

[0016] In another exemplary embodiment, a system for managing interface sessions is described. The system includes a memory and a processing engine communicatively coupled to the processing engine. The processing engine is configured to receive a policy control create request from at least one of a session management function (SMF) or a packet data network gateway (PGW) through at least one interface. The processing engine is configured to check a plurality of trigger conditions in response to receiving the policy control create request. The processing engine is configured to control a flow of one or more messages in at least one interface based on at least one of a matching of one of more of the plurality of trigger conditions and a configuration flag condition. The configuration flag condition is one a false flag condition and a true flag condition.

[0017] In some embodiments, the one or more of plurality of triggerconditions includes a set of parameters comprising an access point name (APN) or a Data Network Name (DPN), an International Mobile Subscriber Identity (IMSI) range or a Subscription Permanent Identifier (SUPI) range, a mobile station international subscriber directory number (MSISDN) range or a generic public subscription identifier (GPSI) range, a plurality of custom subscriber provisioning fields, and a Network Slice Selection Assistance Information (NSSAI).

[0018] In some embodiments, when the configuration flag condition is the false flag condition, initiating one of a sending limit request (SLR) or a spending limit control subscriber request to at least one of a charging function (CHF) and an online charging system (OCS) based on matching of the plurality of trigger conditions; receiving a spending limit answer (SLA) including a policy control identifier (PCID); and storing a session information associated with the at least one interface or the CHF based on the received SLA and the PCID.

[0019] In some embodiments, when the configuration flag condition is the true flag condition, initiating the at least one of a CHF request and an OCS request on each Credit Control Request (CCR) based on the matching of the one or more of the plurality of trigger conditions; receiving a new SLA response in response to initiating the at least one of the CHF request and the OCS request; and updating the session information associated with the at least one interface or the CHF to at least one of an IMSI or a SUPI in response to receiving the new SLA.

[0020] In some embodiments, the processing engine is further configured to maintain a single session information associated with the at least one interface or the CHF for the at least one of the IMSI or the SUPI, wherein a set of pre-triggered messages triggered for the at least one of the IMSI or the SUPI are prevented from triggering, on receiving the CCR.

[0021] In some embodiments, the set of parameters are configured to support multiple values including comma-separated values, wildcard characters,and logical operators.

[0022] In some embodiments, the processing engine is further configured to receive an activity parameter associated with a user equipment (UE). The activity parameter is configured to indicate whether the UE is in a pre-active state, an active state, or a suspended state. When the activity parameter is in the pre-active state, allowing the UE to process a plurality of messages on a plurality of interfaces. When the activity parameter is in the active state, triggering a transmission of the plurality of messages. When the activity parameter is in the suspended state, rejecting the policy control create request.

[0023] In some embodiments, the processing engine sending the SLR to one of UEs using one of the APN or the DPN by provisioning a different custom subscriber provisioning field value in a subscriber profile.

[0024] Other objects and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.OBJECTS OF THE PRESENT DISCLOSURE

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

[0026] An object of the present disclosure is to provide a system and a method for managing (Sy) interface sessions.

[0027] Another object of the present disclosure is to provide a system and a method that reduces number of exchanges required between a Policy Charging Functions (PCF) and an Online Charging System (OCS).

[0028] Another object of the present disclosure is to provide a system and a method that reduces Sy session counts.

[0029] Another object of the present disclosure is to provide a system and a method that reduces computational burden on the OCS.

[0030] Another object of the present disclosure is to provide a system and a method that optimizes computational and storage overheads of Sy interfaces.BRIEF DESCRIPTION OF DRAWINGS

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

[0032] FIG. 1 illustrates an exemplary network architecture for managing (Sy) interface sessions, in accordance with embodiments of the present disclosure.

[0033] FIG. 2 illustrates a block diagram of a system configured for managing interface sessions, in accordance with embodiments of the present disclosure.

[0034] FIG. 3 illustrates a flow diagram of a method for managing interface sessions, in accordance with embodiments of the present disclosure.

[0035] FIG. 4 illustrates an exemplary implementation of a system configured for managing interface sessions, in accordance with embodiments of the present disclosure.

[0036] FIG. 5 illustrates a sequence diagram for managing interface sessions, in accordance with embodiments of the present disclosure.

[0037] FIG. 6 illustrates an exemplary computer system (500) in which or with which embodiments of the present disclosure may be implemented.

[0038] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network architecture102-1 and 102-2- Users104-1 and 104-2 -User Equipments106 - Network108 - System202 - Processor204 - Memory206 - A Plurality of Interfaces208 - Processing Engine210 - Database212 -Receiving Engine214 -Determining Engine216 - Retrieval Engine218 - Other Engines300 - Flow diagram302 - Receiving Step304 - Checking step306 - Controlling step400 - Implementation402 - Policy Control Function (PCF) - Policy and Charging Rules Functions (PCRF)404 - Access and Mobility Management Function (AMF)406 - N15 interface408 - Application Function (AF)410 - Roaming Exchange (Rx)412 - Deep Packet Inspection (DPI)414 - Service Differentiator (Sd)416 - Session Management Function (SMF)418 - N7 interface420 - Charging Function (CHF)422 - N28 interface424 - Network Bootstrap Function (Nbsf)426 - Bootstrap Function (BSF)428 - Next Generation Network Resource Function (Nnrf)430 - Network Resource Function (NRF)432 - Online Charging Systems (OCS)434 - Sy diameter interface (Sy)436 - Packet Data Network Gateway (PGW)438 - Gx interface440 - Network Management System (NMS)442 - Subscriber Profile Repository (SPR)500 - Sequence Diagram502 - PCF - PCRF504 - SMF / PGW506 - CHF / OCS508 - Receiving step510 - Checking step512 - Sending step514 - Storing step516 - Receiving step518 - Checking step520 - Updating step610 - External Storage Device620 - Bus630 - Main Memory640 - Read Only Memory650 - Mass Storage Device660 - Communication Port670 - ProcessorDETAILED DESCRIPTION OF DISCLOSURE

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

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

[0041] 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 toobscure 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.

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

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

[0044] 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 thephrases “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.

[0045] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used 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.

[0046] The present disclosure relates to a system and a method for managing (Sy) interface sessions. The system receives a first set of signals indicative of request for services from a network entity via a network. The system determines whether a Policy Counter Identifier (PCID) is to be requested from an Online Charging System (OCS) based on a set of parameters received via the first set of signals. The system transmits a second set of signals indicative of a request to receive the PCID from the OCS. The system receives the PCID to fulfil request for services made by a network entity. The system may determine whether the PCID needs to be requested from the OCS by applying logical operators to the set of parameters. The system may provide precedence to a first subset of the set of parameters over a second subset of parameters.

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

[0048] FIG. 1, illustrates an exemplary network architecture (100) for managing interface sessions, in accordance with embodiments of the present disclosure.

[0049] In FIG. 1, the network architecture (100) may include one or more computing devices or user equipments (UEs) (104-1 and 104-2) associated with one or more users (102-1 and 102-2) in an environment. A person of ordinary skill in the art will understand that one or more users (102- 1 and 102-2) 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 UEs (104-1 and 104-2) may be individually referred to as the UE (104) and collectively referred to as the UEs (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 UEs (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 UE (104) may have a first unique identifier attribute associated therewith. In an embodiment, the first unique identifier attribute may be indicative of at least one of a Mobile Station International Subscriber Directory Number (MSISDN), International Mobile Equipment Identity (IMEI) number, an International Mobile Subscriber Identity (IMSI), a Subscriber Permanent Identifier (SUPI), and the like.

[0050] In an embodiment, the UE (104) may include smart devices operating in a smart environment, for example, an Internet of Things (loT) system. In such an embodiment, the UE (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, a networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart television (TV), computers, a smart security system, a 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 UE (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 cloudcomputing system or any other device that is network-connected.

[0051] In an embodiment, the UE (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 head-mounted 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 a wireless communication capabilities, and the like. In an embodiment, the UE (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, a laptop, a general-purpose computer, a desktop, a personal digital assistant, a tablet computer, a mainframe computer, or any other computing device. In addition, the UE (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 an entity such as touch pad, a touch enabled screen, an electronic pen, and the like. A person of ordinary skill in the art will appreciate that the UE (104) may not be restricted to the mentioned devices and various other devices may be used.

[0052] In FIG. 1, the UEs (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 (5G) network, a Sixth Generation (6G) network, or the like. The network (106) may enable the UEs (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 thiscommunication. 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, i.e., a base station-1 (112-1) and a base station-2 (112-2) for facilitating communication between the UEs (104). In an embodiment, the base station- 1 (112-1) and the base station-2 (112-2) may be collectively referred as base stations (112). The network (106) may be formed by the base stations (112) communicatively coupled with the UEs (104) to enable telecommunication exchanges between the UEs (104).

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

[0054] In an embodiment, the network (106) may include one or more network entities depicted as a network entity 1 (110-1) and a network entity 2 (110- 2) in FIG. 1. The network entity 1 (110-1) and the network entity 2 (110-2) may be collectively referred to as network entities (110). In an embodiment, the network entities (110) may include, but are not limited to, a Serving Gateway (SGW), aPacket Data Network Gateway (PGW), a Mobility Management Entity (MME), and the like. In some embodiments, where the network (106) is the 5G network, the network (106) may further include a user plane, and a control plane having the network entities (110) such as an Access and Mobility Management Function (AMF) unit, a Session Management Function (SMF) unit, and a Network Exposure Function (NEF) unit, but not limited thereto. In an embodiment, the network entities (110) forming the network (106) may be implemented as a hardware component, a software component, or any combination thereof.

[0055] In an embodiment, the system (108) may be a network entity (e.g., the network entity 1 (110-1) or the network entity 2 (110-2)) indicative of a Policy and Charging Rules Function (PCRF) or a Policy Charging Function (PCF), or a combination thereof. In an embodiment, the PCRF may be configured to determine policy and charging rules associated with the UEs (104) attempting to connect to the network (106). In an embodiment, the system (108) may be configured to retrieve the charging rules from an Online Charging System (OCS) via at least one interface (e.g., an Sy diameter interface). In an embodiment, the Sy diameter interface may allow the system (108) and the OCS to communicate using a diameter protocol. In an embedment, the OCS may be configured to retrieve a Policy Counter ID (PCID) based on the first unique identifier of the UE (104) requesting service, upon receiving a request from the system (108). In an embodiment, the PCID may include one or more charging rules applicable to the UE (104). In an embodiment, the system (108) may also be associated with a Charging Function (CHF) interface that monitors a subscriber usage consumption. The subscriber usage consumption may be used by the OCS for determining the PCID.

[0056] In an example, the UE (104) may be associated with a plan to consume 1 Gigabytes (GB) of data per day, with speed of a connection reducing after consuming the 1 GB of data as per allocation. The CHF, after monitoring the data, may cause the OCS to retrieve a corresponding PCID indicating that UE (104) has consumed the allocated data, i.e., 1 GB of the data, and must be providedservices with a lower speed. The system (108) may fulfil a request for a service from the UE (104) based on the PCID received from the OCS. In an example, the system (108) may cause the PGW to allocate bandwidths for connection based on the PCID. In an embodiment, the OCS may have a predetermined set of PCIDs. Examples of the predetermined set of PCIDs may include, but are not limited to, sequential PCIDs (ranging from PCID_1000 to PCID_1999), randomized PCIDs (PCID_ABCD, PCID_EFGH, PCIDJJKL, etc.), hierarchical PCIDs (e.g., PCID_1000 for SMF, PCID_2000 for PGW, etc., etc.), and the like. In other embodiments, the PCIDs may be dynamically generated by the OCS.

[0057] In accordance with embodiments of the present disclosure, the system (108) may be designed and configured for managing interface sessions, e.g., the Sy diameter interface sessions. In an embodiment, the system (108) may optimize a number of sessions created and maintained to fulfil requests for service from the UEs (104).

[0058] FIG. 2 illustrates a block diagram (200) of the system (108) configured for managing interface sessions, in accordance with embodiments of the present disclosure. FIG. 2 is explained in conjunction with FIG. 1.

[0059] 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 and 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 deviceincluding, 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.

[0060] As depicted in 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 communication pathway 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).

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

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

[0063] In an exemplary embodiment, the processing engine (208) may include one or more engines selected from any of a receiving engine (212), a determination engine (214), a retrieval engine (216), and other engines (218) having functions that may include, but are not limited to, testing, storage, and peripheral functions, such as a wireless communication unit for remote operation, audio unit for alerts and the like. In an embodiment, each engine, the receiving engine (212), the determination engine (214), the retrieval engine (216), and the other engines (218) may be configured using a Policy Control Function (PCF) and a Policy and Charging Rules Function (PCRF).

[0064] In an embodiment, the receiving engine (212) may receive a first set of signals indicative of the policy control create request for service from any network entity (110) or the UE (104) in the network (106). The first set of signals may correspond to a plurality of trigger conditions. In an embodiment, the plurality of trigger conditions may include a set of parameters. In an embodiment, the set of parameters may include, but not be limited to, an Access Point Name APN or a Data Network Name (DNN), a IMSI range or a SUPI Range, a MSISDN range or a generic public subscription identifier (GPSI) range, a plurality of custom subscriber provisioning fields, and Network Slice Selection Assistance Information (NSSAI). In an embodiment, the set of parameters may also include attributes of the first unique identifier of the UE (104) requesting service. Examples of the attributes of the first unique identifier may include, but are not limited to, a mobile country code, a mobile service code, a mobile subscriber identification number(MSIN), a subscription plan, and the like.

[0065] In an embodiment, the determination engine (214) may be configured to check the plurality of trigger conditions in response to receiving the policy control create request. In addition, the determination engine (214) may determine whether the PCID is to be requested from the OCS based on the set of parameters. In an embodiment, the determination engine (214) may retrieve a Sy / CHF session associated with the attributes of the first unique identifier provided in the first set of signals from the database (210). In other embodiments, the determination engine (214) may generate the Sy / CHF session to enable communication between the system (108) and the OCS. In an embodiment, the Sy / CHF session may be stored in the database (210). In an embodiment, the determination engine (214) may use any combination of logical operators, including ‘AND’ Booleans or ‘OR’ Booleans on a subset of the set of parameters for determining whether one or more messages (e.g., Sy diameter interface messages) should be triggered. In an embodiment, the Sy diameter interface messages may be triggered when a Sy session data stored in the system (108) is insufficient to fulfil the policy control create request.

[0066] In an embodiment, the retrieval engine (216) may be configured to transmit a second set of signals indicative of the policy control create request to receive the PCID from the OCS. In other words, the retrieval engine (216) may be configured to transfer one of a sending limit request (SLR) or a spending limit control subscriber request to at least one of the CHF and the OCS. The retrieval engine (216) may be configured to control a flow of one or more messages in at least one interface based on matching of one or more of the plurality of trigger conditions and a configuration flag condition. The configuration flag condition may be one of a false flag condition or a true flag condition. In other words, the retrieval engine (216) is configured to receive and redirect the PCID to fulfil policy control create request for the service made by the network entity (110). In an embodiment, the second set of signals may be transmitted as a Subscriber Limit Request having a subset of parameters from the set of parameters received in the first set of signals.In an embodiment, the response from the OCS may be received as a Spending Limit Answer (SLA) having the PCIDs, and any attributes associated therewith. In an embodiment, a Policy Charging Control (PCC) rule associated with the PCID may be installed on the system (108) so as to allow said system (108) to fulfil the service. This is further explained in detail in conjunction with FIG. 3 - FIG. 5.

[0067] FIG. 3 illustrates a flow diagram of a method (300) for managing interface sessions, in accordance with embodiments of the present disclosure. FIG. 5 is explained in conjunction with FIGS. 1 and 2.

[0068] In order to manage the interface sessions, at step 302, a policy control create request is received from at least one of a session management function (SMF) or a packet data network (PDN) gateway (PGW) through at least one interface. The at least one interface may correspond to the Sy diameter interface or an N28 interface. Further, at step 304, the plurality of trigger conditions may be checked in response to receiving the policy control create request. On PCF+PCRF side, the operator can set configurable conditions for triggering Sy / CHF messages towards OCS / CHF or not. The plurality of trigger conditions may correspond to a first set of signals. The plurality of trigger conditions may include a set of parameters. The set of parameters may include one or more parameters selected from the APN, the DPN, the IMSI range, the SUPI range, the MSISDN range, the GPSI range, the plurality of custom subscriber provisioning fields, and the Network Slice Selection Assistance Information (NSSAI). The set of parameters are configured to support multiple values including comma-separated values, wildcard characters, and logical operators.

[0069] Further, based on the checking, at step 306, a flow of one or more messages through the at least one interface may be controlled. The flow of the one or more messages may be controlled based on at least one of a matching of one or more of the plurality of trigger conditions and / or a configuration flag condition. The configuration flag condition is one of a false flag condition and a true flag condition.By using the configuration in PCF+PCRF, operator can control the flow of one or more messages flow in an Sy diameter interface and an N28 HTTP2 interface. In an embodiment, when the configuration flag condition is the false flag condition, one of the SLR or the spending limit control subscriber request (i.e., the second set of signals) may be initiated to at least one of the CHF and the OCS based on matching of the plurality of trigger conditions. Further, an SLA including a PCID may be received. In response to receiving the SLA with the PCID, a session information associated with the at least one interface or the CHF may be stored. The session information may be stored based on the received SLA and PCID.

[0070] In another embodiment, when the configuration flag condition is the true flag condition, the at least one of a CHF request and an OCS request may be initiated on each Credit Control Request (CCR) based on the matching of the one or more of the plurality of trigger conditions. Further, a new SLA response may be received in response to initiating the at least one of the CHF request and the OCS request. In response to receiving the new SLA response, the session information associated with the at least one interface or the CHF may be updated to at least one of an IMSI or a SUPI. It should be noted that, a single session information associated with the at least one interface or the CHF may be maintained for the at least one of the IMSI or the SUPI. Further, a set of pre-triggered messages (i.e., messages that has been already triggered) triggered for the at least one of the IMSI or the SUPI may be prevented from triggering again, on receiving the CCR.

[0071] In addition, an activity parameter associated with a user equipment (UE) may also be received. The activity parameters may be configured to indicate whether the UE is in a pre-active state, an active state, or a suspended state. In an embodiment, when the activity parameter is in the pre-active state, allowing the UE to process a plurality of messages on a plurality of interfaces. In another embodiment, when the activity parameter is in the active state, triggering a transmission of the plurality of messages. In yet another embodiment, when the activity parameter is in the suspended state, rejecting the policy control createrequest. Further, the SLR may be send to one of UEs using one of the APN or the DPN by provisioning a new custom subscriber provisioning field value in a subscriber profile. It should be noted that, the activity parameter has a higher precedence over the set of parameters.

[0072] FIG. 4 illustrates an exemplary implementation (400) of the system (108) configured for managing interface sessions, in accordance with embodiments of the present disclosure. FIG. 4 is explained in conjunction with FIGS. 1, 2, and 3.

[0073] In FIG. 4, a PCF-PCRF (402) configured for managing interface sessions is depicted. The PCF-PCRF (402) may interact with an AMF (404), via an N15 interface (406) and vice versa. The PCF-PCRF (402) may interact with an Application Function (AF) (408) via a Roaming Exchange (Rx) 410 and vice versa. Further, the PCF-PCRF (402) may interact with a Deep Packet Inspection (DPI) (412), an SMF (416), a CHF (420), a Bootstrap Function (BSF) (426), and an Network Resource Function (NRF) (430) via a Service Differentiator (Sd) (414), an N7 interface (418), an N28 interface (422), a Network Bootstrap Function (Nbsf) (424), and a Next Generation Network Resource Function (Nnrf) (428), respectively and vice versa. In addition, the PCF-PCRF (402) may interact with an OCS (432) and a PGW (436) via a Sy diameter interface (Sy) (434) and a Gx interface (438), respectively and vice versa. Moreover, the PCF-PCRF (402) may interact with a Network Management System (NMS) (440) and a Subscriber Profile Repository (SPR) (442) and vice versa.

[0074] The following example is described in the context of where the system (108) may require interaction with the OCS (432) through the Sy (434). For instance, the system (108) may receive a Credit Control Request (CCR) message from the PGW (436).

[0075] In an embodiment, the operator of the system (108) may set the configurable conditions for triggering Sy messages towards the OCS (432) or the CHF (420). In an embodiment, the set of parameters for triggering the at least onemessage (e.g., the Sy message) may include the APN or the DNN, the IMSI range or the SUPI Range, the MSISDN range or the GPSI Range, the plurality of custom subscriber provisioning fields, and the NSSAI (a Service Differentiator (SD) and a Slice / Service Type (SST)). In an example, the set of parameters may be provided as a comma-separated string with wild card operators for wild card characters used for missing values. In an embodiment, an ‘AND’ Boolean or an ‘OR’ Boolean may be associated with a subset of the set of parameters. In an example, based on the set of parameters, the system (108) may initiate transmission of the SLR Diameter message towards the OCS (432). In an example, to transmit the request, the system (108) may call the ‘Nchf_SpendingLimitControl_Subscribe’ service operation towards the CHF (420). The system (108) may receive the SLA having the PCIDs and the current status.

[0076] By using the above configuration in the system (108), a network operator of said system (108) may control the message flow in a Sy diameter interface (i.e., the Sy (434)) and an N28 HTTP2 interface (i.e., the N28 interface (422)). For example, two users are using the same the APN or the DNN and the requirement is to send a spending limit request message for one of the UE (104) from the system (108), said request may be fulfilled by provisioning a different Custom Subscriber Provisioning Field value in the subscriber profile. In an example, the set of parameters may include the APN / DNN and a ‘Custom subscriber provisioning Field’ to the system (108) to allow said system (108) to determine whether to trigger Sy message to the OCS (432).

[0077] In an embodiment, the PCID parameter may also be made available in the set of parameters. In an embodiment, the set of parameters may have weighted values associated thereto. In an example, an activity parameter from the set of parameters may indicate whether the UE (104) has been pre-active, active, or suspended. In such examples, in case the activity parameter is ‘pre-active,’ the system (108) may allow the UE (104) to process messages on different interfaces and no Sy trigger message. When the activity parameter is ‘active,’ the system (108)may trigger transmission of the Sy message. When the activity parameter is ‘suspended,’ the system (108) may reject the policy control create request and No Sy trigger message. In an embodiment, a subset of parameters may also have precedence over other parameters from the set of parameters. In an example, a subscriber provisioning parameter may have a higher precedence over Sy / N28 message trigger conditional configuration parameter.

[0078] In an embodiment, the system (108) may maintain a single Sy / CHF session information for each of the UE (104), where each UE (104) is identified by a first unique identifier attribute such as IMSI or SUPI. In an embodiment, a runtime configurable flag may be made available such that when the flag is false, the system (108) may transmit a first SLR diameter message or SpendingLimitSubscribe service operation request towards the OCS (432) or the CHF (420) and store the Sy / CHF session information along with the PCIDs mapped to the first unique identifier attribute. For subsequent CCR-I requests, the system (108) retrieve the service requests for the same IMSI / SUPI. PCF+PCRF application may not trigger the same messages after receiving Credit Control Request (CCR-I) ZSM create policy control messages for the same IMSI / SUPI.

[0079] In an embodiment, if the flag is true, the system (108) may initiate a CHF / OCS request on each SMF Create request / CCR-I based on the set of parameters, irrespective of whether the Sy / CHF session is already present or not. After receiving a response for said request, the system (108) stores the response, or updates the stored Sy / CHF session information associated with the first unique identifiers of the UE (104). In other words, after receiving a new SLA / SLC subscribe response, PCF+PCRF will update the stored Sy / CHF session info of the IMSI / SUPI.

[0080] In an embodiment, data associated with creation and storage of Sy / CHF sessions may be provided on a Command Line Interface (CLI), an Application Programming Interface (API), or a Graphical User Interface (GUI). Such data may include, but not be limited to, create time and refresh time of Sy / CHFsession.

[0081] In other examples, as illustrated in FIG. 4, the system (108) may receive a first request for service from the PGW with the set of parameters having a first APN parameter with value ‘X’ and the first unique identifier attribute with value ‘A’. The system (108) may determine to send a second set of signals to the OCS based on said set of parameters and generate a Sy / CHF session. On receiving a response with the PCID from the OCS, the system (108) may store the PCID and the Sy / CHF session in the database (210). Subsequently, when a second request for service is received from the PGW with set of parameters having a second APN parameter with value ‘Y’ and the first unique identifier attribute with value ‘A’, the system (108) may retrieve the PCID associated with the first unique identifier attribute of the PGW from the corresponding Sy / CHF sessions stored in the database (210).

[0082] FIG. 5 illustrates a sequence diagram (500) for managing interface sessions, in accordance with embodiments of the present disclosure. FIG. 5 is explained in conjunction with FIGS. 1, 2, 3, and 4.

[0083] In one embodiment, at step (508), a PCF and PCRF (504) (same as the PCF-PCRF (402)) may receive the policy control create request (i.e., an NpcfjSMPolicy control Create Request) from at least one of the SMF (502) (same as the SMF (416) or the PGW (502) (same as the PGW (436)) as mentioned. In some embodiment, a credit control request (CCR-1) for an IMSI = A, and an APN = X may be received by the PCF and PCRF (504). At step (510), the PCF and PCRF (504) may check the plurality of trigger conditions, i.e., the Sy diameter interface or the N28 interface conditions. Further, at step (512), one of the SLR or the spending limit control subscriber request may be sent to at least one of a CHF (506) (same as the CHF (420)) or an OCS (506) (same as the OCS (432)) as depicted. Further, at the step (512), the SLA including the PCID (e.g., 201 - created (PCIDs, current status) may be received by the PCF and PCRF (504). At step (514), thesession information may be stored at the SMF or the PGW (502) based on the received SLA and PCID. The PCC rule is installed based on the PCIDs received from OCS / CHF.

[0084] In another embodiment, at step (516), the PCF and the PCRF (504) may receive the policy control create request (i.e., an Npcf_SMPolicy control Create Request) from at least one of the SMF as mentioned via (502). In some embodiment, the CCR (CCR-1) for the IMSI = A, and the APN = Y may be received by the PCF and PCRF (504). At step (518), the PCF and PCRF (504) may check the plurality of trigger conditions, i.e., the Sy diameter interface or the N28 interface conditions. In this embodiment, at step (520), the SMF or the PGW (502) may be updated based on the session information (i.e., 201 Created or CCA -1) received from the PCF and the PCRF (504). In other words, a PCC rule may be installed based on the PCIDs information from the IMSI’s Sy / CHF session. Thus, the present disclosure provides a system and a method that reduces number of exchanges required between a PCF and an OCS.

[0085] FIG. 6 illustrates an exemplary computer system (600) in which or with which embodiments of the present disclosure may be implemented. As shown in FIG. 6, the computer system (600) may include an external storage device (610), a bus (620), a main memory (630), a read only memory (640), a mass storage device (650), a communication port (660), and a processor (670). A person skilled in the art will appreciate that the computer system (600) may include more than one processor (670) and communication port (660). The processor (670) may include various modules associated with embodiments of the present disclosure.

[0086] In an embodiment, the communication port (660) 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 (660) 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 (600) connects.

[0087] In an embodiment, the memory (630) may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. Read-only memory (640) 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 (670).

[0088] In an embodiment, the mass storage (650) 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).

[0089] In an embodiment, the bus (620) communicatively couples the processor (670) with the other memory, storage and communication blocks. The bus (620) 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 (670) to the computer system (600).

[0090] Optionally, operator and administrative interfaces, e.g., a display, keyboard, joystick, and a cursor control device, may also be coupled to the bus (620) to support direct operator interaction with the computer system (600). Other operator and administrative interfaces may be provided through network connections connected through the communication port (660). Componentsdescribed above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system (600) limit the scope of the present disclosure.

[0091] 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 to be implemented merely as illustrative of the disclosure and not as limitation.

[0092] ADVANTAGES OF THE PRESENT DISCLOSURE

[0093] The present disclosure provides a system and a method for managing interface sessions.

[0094] The present disclosure provides a system and a method that reduces number of exchanges required between a PCF and an OCS.

[0095] The present disclosure provides a system and a method configured to reduce interface session counts.

[0096] The present disclosure provides a system and a method that reduces computational burden on the OCS.

[0097] The present disclosure provides a system and a method that optimizes computational and storage overheads of interfaces.

Claims

We Claim:

1. A method (300) for managing interface sessions, the method (300) comprising: receiving (302), by a processing engine (208), a policy control create request from at least one of a session management function (SMF) and a packet data network gateway (PGW) through at least one interface; checking (304), by the processing engine (208), a plurality of trigger conditions in response to receiving the policy control create request; and controlling (306), by the processing engine (208), a flow of one or more messages in the at least one interface based on at least one of a matching of one or more of the plurality of trigger conditions and a configuration flag condition, wherein the configuration flag condition is one a false flag condition and a true flag condition.

2. The method (300) as claimed in claim 1, wherein the one or more of plurality of trigger conditions includes a set of parameters comprising an access point name (APN) or a Data Network Name (DPN), an International Mobile Subscriber Identity (IMSI) range or a Subscription Permanent Identifier (SUPI) range, a mobile station international subscriber directory number (MS ISDN) range or a generic public subscription identifier (GPSI) range, a plurality of custom subscriber provisioning fields, and a Network Slice Selection Assistance Information (NSSAI).

3. The method (300) as claimed in claim 1, wherein, when the configuration flag condition is the false flag condition, initiating, by the processing engine (208), one of a sending limit request (SLR) or a spending limit control subscriber request to at least one of a charging function (CHF) and an online charging system (OCS) based on matching of the plurality of trigger conditions;receiving, by the processing engine (208), a spending limit answer (SLA) including a policy control identifier (PCID); and storing, by the processing engine (208), a session information associated with the at least one interface or the CHF based on the received SLA and the PCID.

4. The method (300) as claimed in claim 1 , wherein, when the configuration flag condition is the true flag condition, initiating, by the processing engine (208), the at least one of a CHF request and an OCS request on each Credit Control Request (CCR) based on the matching of the one or more of the plurality of trigger conditions; receiving, by the processing engine (208), a new SLA response in response to initiating the at least one of the CHF request and the OCS request; and updating, by the processing engine (208), the session information associated with the at least one interface or the CHF to at least one of an IMSI or a SUPI in response to receiving the new SLA.

5. The method (300) claimed as in claim 1 , further comprising maintaining, by the processing engine (208), a single session information associated with the at least one interface or the CHF for the at least one of the IMSI or the SUPI, wherein a set of pre-triggered messages triggered for the at least one of the IMSI or the SUPI are prevented from triggering, on receiving the CCR.

6. The method (300) claimed as in claim 1, wherein the set of parameters are configured to support multiple values including comma- separated values, wildcard characters, and logical operators.

7. The method (300) claimed as in claim 1, further comprising receiving an activity parameter associated with a user equipment (UE), wherein the activity parameter is configured to indicate whether the UE is in a pre-active state, an active state, or a suspended state, and wherein: when the activity parameter is in the pre-active state, allowing the UE to process a plurality of messages on a plurality of interfaces; when the activity parameter is in the active state, triggering a transmission of the plurality of messages; and when the activity parameter is in the suspended state, rejecting the policy control create request.

8. The method (300) claimed as in claim 7, further comprising sending, by the processing engine (208), the SLR to one of UEs using one of the APN or the DPN by provisioning a different custom subscriber provisioning field value in a subscriber profile.

9. A system (108) for managing interface sessions, the system (108) comprising: a memory (204); and a processing engine (208) communicatively coupled with the memory (204), configured to: receive (302) a policy control create request from at least one of a session management function (SMF) or a packet data network (PDN) gateway (PGW) through at least one interface; check (304) a plurality of trigger conditions in response to receiving the policy control create request; and control (306) a flow of one or more messages in the at least one interface based on at least one of a matching of one of more of the plurality of trigger conditions and a configuration flag condition, wherein the configuration flag condition is one a false flag condition and a true flag condition.

10. The system (108) as claimed in claim 9, wherein the one or more of plurality of trigger conditions includes a set of parameters comprising an access point name (APN) or a Data Network Name (DPN), an International Mobile Subscriber Identity (IMSI) range or a Subscription Permanent Identifier (SUPI) range, a mobile station international subscriber directory number (MSISDN) range or a generic public subscription identifier (GPSI) range, a plurality of custom subscriber provisioning fields, and a Network Slice Selection Assistance Information (NSSAI).

11. The system (108) as claimed in claim 9, wherein, when the configuration flag condition is the false flag condition, initiate one of a sending limit request (SLR) or a spending limit control subscriber request to at least one of a charging function (CHF) and an online charging system (OCS) based on matching of the one or more of the plurality of trigger conditions; receive a spending limit answer (SLA) including a policy control identifier (PCID); and store a session information associated with the at least one interface or the CHF based on the received SLA and the PCID.

12. The system (108) as claimed in claim 9, wherein, when the configuration flag condition is the true flag condition, initiate the at least one of a CHF request and an OCS request on each Credit Control Request (CCR) based on the matching of the one or more of the plurality of trigger conditions; receive a new SLA response in response to initiating the at least one of the CHF request and the OCS request; and update the session information associated with the at least one interface or the CHF to at least one of an IMSI or a SUPI in response to receiving the new SLA.

13. The system (108) as claimed as in claim 9, wherein the processing engine (208) is further configured to maintain a single session information associated with the at least one interface or the CHF for the at least one of the IMSI or the SUPI, and wherein a set of pre-triggered messages triggered for the at least one of the IMSI or the SUPI are prevented from triggering, on receiving the CCR.

14. The system (108) as claimed as in claim 9, wherein the set of parameters is configured to support multiple values with comma-separated values, wildcard characters, and logical operators.

15. The system (108) as claimed as in claim 9, wherein the processing engine is further configured to receive an activity parameter associated with a user equipment (UE), and wherein the activity parameter is configured to indicate whether the UE is in a pre-active state, an active state, or a suspended state, and wherein: when the activity parameter is in the pre-active state, allowing the UE to process a plurality of messages on a plurality of interfaces; when the activity parameter is in the active state, triggering transmission of the plurality of messages; and when the activity parameter is in the suspended state, rejecting the policy control create request.

16. The system (108) as claimed as in claim 15, wherein the processing engine (208) is further configured to send the SLR message to one of UEs using the APN or the DPN by provisioning different custom subscriber provisioning field value in a subscriber profile.

17. A computer program product comprising a non-transitory computer- readable medium comprising instructions that, when executed by one ormore processors, cause the one or more processors to perform a method for managing a plurality of interface sessions, the method comprising: receiving (302) a policy control create request from at least one of a session management function (SMF) and a packet data network gateway (PGW) through at least one interface; checking (304) a plurality of trigger conditions in response to receiving the policy control create request; and controlling (306) a flow of one or more messages in the at least one interface based on at least one of a matching of one or more of the plurality of trigger conditions and a configuration flag condition, wherein the configuration flag condition is one a false flag condition and a true flag condition.

Images