WO2025017602A1 - System and method for throttling services with retry mechanism in a network - Google Patents

Abstract

The present disclosure provides a system (108) and a method (600) for enabling a retry mechanism in a network (106). The method (600) comprising communicating (602) at least one create request towards a network function and communicating (604) at least one session request towards a network node. The method (600) comprising receiving (606) at least one response message, determining (608) if the at least one response message includes at least one negative response, and provisioning (610) at least one flag at the network function and recommunicating the at least one session request towards the network node when at least one condition is met. The method (600) comprising establishing (612) at least one session between the network function and the network node and installing (614) a plurality of rules on the network node based on the at least one established session.

Description

SYSTEM AND METHOD FOR THROTTLING SERVICES WITH RETRY MECHANISM IN A NETWORK

RESERVATION 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 INVENTION

[0002] The embodiments of the present disclosure generally relate to a system and method for throttling services with a retry mechanism in a network. More particularly, the present disclosure relates to a system and method for enabling a retry mechanism in a network.

DEFINITION

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

[0004] The term PCF as used herein, refers to Policy Control Function. The PCF is a key component of the 5G architecture and plays a crucial role in enforcing policy decisions related to Quality of Service (QoS), traffic management, and network resource allocation.

[0005] The term PCRF as used herein, refers to a Policy and Chaiging Rules Function. The PCRF plays a central role in controlling and enforcing policies related to network resource allocation, quality of service (QoS), and charging for subscriber sessions.

[0006] The term DPI as used herein, refers to a Deep Packet Inspection. The DPI provides detailed visibility into network traffic, allowing network operators to monitor, control, and optimize network performance, security, and user experience.

[0007] The term SMF as used herein, refers to a Session Management Function. The SMF plays a crucial role in establishing, managing, and terminating communication sessions between User Equipment (UE) and 5G network services.

[0008] The term AMF as used herein, refers to an Access and Mobility Management Function. The AMF is responsible for managing access to the 5G network and handling mobility-related functions for UE devices.

[0009] The term CHF as used herein, refers to a Charging Function (CHF). The CHF plays a crucial role in managing chaiging-related functions within the network, including real-time charging, policy control, and usage monitoring.

[0010] The term BSF as used herein, refers to a Binding Support Function. The BSF is responsible for providing support functions related to binding a user's identity to the Internet Protocol (IP) address. In the 5G Core, the BSF is used for binding an application-function request to a specific PCF instance.

[0011] The term NRF as used herein, refers to a Network Repository Function. The NRF plays a critical role in the management and orchestration of network functions and services.

[0012] The term OCS as used herein, refers to an Online Charging System. The OCS is responsible for real-time charging and credit management for various services offered to subscribers by the network.

[0013] The term PGW as used herein, refers to a Packet Data Network Gateway. The PGW serves as the point of interconnection between the mobile network and external packet data networks, such as the Internet or private corporate networks.

[0014] The term NMS as used herein, refers to a Network Management System. The network operators use the NMS to monitor, manage, and control various aspects of the 5G network infrastructure. The NMS provides operators with tools and functionalities to ensure the efficient operation, optimization, and maintenance of the network.

[0015] The term SPR as used herein, refers to a Subscription Profile Repository. The SPR is a critical component within the 5G Core network architecture, responsible for storing and managing subscriber profiles and subscription-related information.

[0016] The term AF as used herein, refers to an Application Function. The AF is a network function responsible for providing application-specific capabilities and services within the 5G Core architecture.

[0017] The term PCEF as used herein, refers to a Policy and Charging Enforcement Function. The PCEF plays a central role in enforcing policy control and charging rules for subscriber sessions, ensuring that service usage is managed according to operator-defined policies and that subscribers are correctly charged for their usage.

[0018] The term DRA as used herein, refers to a Diameter Routing Agent. The DRA serves as a key element responsible for routing Diameter messages between various Diameter-based network entities.

[0019] The term Gx as used herein, refers to an interface that serves as a critical link between the PCRF and the PCEF. It enables dynamic policy control and charging management, allowing operators to define and enforce policies related to quality of service (QoS), bandwidth allocation, and charging mechanisms based on subscriber profiles and network conditions. [0020] The term N7 as used herein, refers to an interface that facilitates session control and interconnection between IP Multimedia Subsystem (IMS) domains. It supports the establishment, management, and teardown of multimedia sessions, ensuring seamless communication and service delivery across heterogeneous networks.

[0021] These definitions are in addition to those expressed in the art.

BACKGROUND OF THE INVENTION

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

[0023] Wireless communication technology has rapidly evolved over the past few decades. The first generation of wireless communication technology was based on analog technology that offered only voice services. Further, when the second-generation (2G) technology was introduced, text messaging and data services became possible. The 3G technology marked the introduction of highspeed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized the wireless communication with faster data speeds, improved network coverage, and security. Currently, the fifth generation (5G) technology is being deployed, with even faster data speeds, low latency, and the ability to connect multiple devices simultaneously.

[0024] As wireless technologies are advancing, there is a need to cope with the 5G requirements and deliver an elevated level of service to the subscribers. In the telecommunication network, a policy and charging rules function (PCRF) is the network node designated in real-time to determine policy rules in a multimedia network. The PCRF may provide application detection and control (ADC) rules to a deep packet inspection (DPI) node. The ADC rules are used to provide and apply the detection, enforcement actions and applicable charging parameters for the specified application traffic.

[0025] The ADC rules are selected based on various information such as information obtained from the PGW, e.g. request type, subscriber/device related information, location information, information obtained from a subscriber profile repository (SPR), information obtained from the DPI node, information obtained from a bearer binding and event reporting function (BBERF), and information obtained from an application function (AF), and PCRF pre-configured information etc. The BBERF is responsible for managing bearer bindings and reporting events related to bearer establishment and release.

[0026] In case when network fluctuation issues may be raised, or overload situations may occur at the DPI node. In such cases, the PCF and the PCRF may not be able to provision or install the ADC rules in the DPI node. In such cases, service providers should follow regulatory requirements and correct the ADC rules should provision automatically even in network failure cases.

[0027] Further, the continuous retry logic is not recommended as such application of the retry logic continuously can increase signalling traffic in negative scenarios.

[0028] There is, therefore, a need in the art to provide a system and a method that can mitigate the problems associated with the prior arts.

SUMMARY

[0029] In an exemplary embodiment, the present disclosure discloses a method for enabling a retry mechanism in a network. The method comprising communicating, by at least one network entity, at least one create request towards a network function. The method comprising communicating, by the network function, at least one session request towards a network node (deep packet inspection (DPI) node) based on the at least one communicated create request. The method comprising receiving, by the network function, at least one response message from the network node. The method comprising determining if the at least one received response message includes at least one negative response. The method comprising responsive to determining, provisioning at least one flag at the network function and recommunicating, by the network function, the at least one session request towards the network node when at least one condition is met. The method comprising establishing at least one session between the network function and the network node based on the at least one recommunicated session request. The method comprising installing, by the network function, a plurality of rules on the network node based on the at least one established session.

[0030] In some embodiments, the at least one condition includes at least one provisioned flag is true and at least one update request is received from the at least one network entity at the network function.

[0031] In some embodiments, the at least one session request is recommunicated towards the network node until the least one session is established between the network function and the network node.

[0032] In some embodiments, the plurality of rules installed at the network node includes a plurality of application detection and control rules.

[0033] In some embodiments, the at least one negative response includes a session request timeout message or an error message.

[0034] In some embodiments, the method further comprising communicating, by the network function, at least one answer message towards the at least one network entity.

[0035] In some embodiments, the network function includes a policy control function (PCF) and a policy and charging rules function (PCRF).

[0036] In some embodiments, the at least one network entity includes at least one of a session management function (SMF), a charging function (CHF), a binding support function (BSF), a network repository function (NRF), an access and mobility management function (AMF), an online charging system (OCS), a packet data network gateway (PGW), a network management system (NMS), a subscription profile repository (SPR) and an application function (AF).

[0037] In an exemplary embodiment, the present disclosure discloses a system for enabling a retry mechanism in a network. The system comprises a receiving unit configured to receive at least one create request from at least one network entity, a processing unit, and a memory coupled to the processing unit. The memory includes computer implemented instructions to configure the processing unit to communicate the at least one received create request towards a network function. The processing unit is configured to communicate, by the network function, at least one session request towards a network node (deep packet inspection (DPI) node) based on the at least one communicated create request. The processing unit is configured to receive, by the network function, at least one response message from the network node. The processing unit is configured to determine if the at least one received response message includes at least one negative response. The processing unit is configured to provision at least one flag at the network function and recommunicate, by the network function, the at least one session request towards the network node when at least one condition is met. The processing unit is configured to establish at least one session between the network function and the network node based on the at least one recommunicated session request. The processing unit is configured to install, by the network function, a plurality of rules on the network node based on the at least one established session.

[0038] In some embodiments, the at least one condition includes at least one provisioned flag is true and at least one update request is received from the at least one network entity at the network function.

[0039] In some embodiments, the at least one session request is recommunicated towards the network node until the least one session is established between the network function and the network node. [0040] In some embodiments, the plurality of rules installed at the network node include a plurality of application detection and control rules.

[0041] In some embodiments, the at least one negative response includes a session request timeout message or an error message.

[0042] In some embodiments, the system is further configured to communicate, by the network function, at least one answer message towards the at least one network entity.

[0043] In some embodiments, the network function includes a policy control function (PCF) and a policy and charging rules function (PCRF).

[0044] In some embodiments, the at least one network entity includes at least one of a session management function (SMF), a charging function (CHF), a binding support function (BSF), a network repository function (NRF), an access and mobility management function (AMF), an online charging system (OCS), a packet data network gateway (PGW), a network management system (NMS), a subscription profile repository (SPR) and an application function (AF).

[0045] In an exemplary embodiment, the present disclosure discloses a user equipment (UE) communicatively coupled with a network. The coupling comprises steps of receiving, by the network, a connection request from the UE, sending, by the network, an acknowledgment of the connection request to the UE and transmitting a plurality of signals in response to the connection request. A retry mechanism is enabled in the network by a method comprising communicating, by at least one network entity, at least one create request towards a network function. The method comprising communicating, by the network function, at least one session request towards a network node (deep packet inspection (DPI) node) based on the at least one communicated create request. The method comprising receiving, by the network function, at least one response message from the network node. The method comprising determining if the at least one received response message includes at least one negative response. The method comprising responsive to determining, provisioning at least one flag at the network function and recommunicating, by the network function, the at least one session request towards the network node when at least one condition is met. The method comprising establishing at least one session between the network function and the network node based on the at least one recommunicated session request. The method comprising installing, by the network function, a plurality of rules on the network node based on the at least one established session.

[0046] In another exemplary embodiment, the present invention discloses a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for enabling a retry mechanism in a network. The method comprising communicating, by at least one network entity, at least one create request towards a network function. The method comprising communicating, by the network function, at least one session request towards a network node (deep packet inspection (DPI) node) based on the at least one communicated create request. The method comprising receiving, by the network function, at least one response message from the network node. The method comprising determining if the at least one received response message includes at least one negative response. The method comprising responsive to determining, provisioning at least one flag at the network function and recommunicating, by the network function, the at least one session request towards the network node when at least one condition is met. The method comprising establishing at least one session between the network function and the network node based on the at least one recommunicated session request. The method comprising installing, by the network function, a plurality of rules on the network node based on the at least one established session.

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

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

[0049] An object of the present disclosure is to provide a system and a method for throttling services with a retry mechanism in a network. The throttling services in the network includes limiting network bandwidth for some of the network services in case of overload traffic conditions in the network or during network fluctuations.

[0050] An object of the present disclosure is to provide a system and a method for enabling a retry mechanism in a network.

[0051] Another object of the present disclosure is to achieve smooth and efficient operation of the production network.

[0052] Another object of the present disclosure is to provide a system and a method that are economical and easy to implement.

BRIEF DESCRIPTION OF DRAWINGS

[0053] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems 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.

[0054] FIG. 1 illustrates an example network architecture for implementing a system for enabling a retry mechanism in a network, in accordance with an embodiment of the present disclosure.

[0055] FIG. 2 illustrates an example block diagram of the system for enabling the retry mechanism in the network, in accordance with an embodiment of the present disclosure.

[0056] FIG. 3 illustrates an exemplary representation of a system architecture showing connection of a policy control function (PCF) and a policy and charging rules function (PCRF) with other network elements through corresponding interfaces, in accordance with some embodiments of the present disclosure.

[0057] FIG. 4 illustrates an exemplary representation of flow diagram representing a method for enabling a retry mechanism in the network, in accordance with some embodiments of the present disclosure.

[0058] FIG. 5 illustrates an example computer system in which or with which the embodiments of the present disclosure may be implemented.

[0059] FIG. 6 illustrates another exemplary flow diagram for the method for enabling a retry mechanism in the network, in accordance with an embodiment of the present disclosure.

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

LIST OF REFERENCE NUMERALS

100 - Network architecture

102-1, 102-2... 102-N - A plurality of users

104-1, 104-2. . . 104-N - A plurality of computing devices

106 - Network

108 - System

200 - Block Diagram

202 - Receiving unit 204 - Memory

206 - Interface(s)

208 - Processing unit

210 - Database

300 - System architecture

400 - Flow Diagram

500 - Computer system

510 - External storage device

520 - Bus

530 - Main memory

540 - Read only memory

550 - Mass storage device

560 - Communication port(s)

570 - Processor

600 - Flow Diagram

DETAILED DESCRIPTION

[0061] In the following description, for explanation, various specific details are outlined 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.

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

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

[0064] Also, it is noted that individual embodiments may be described as a process that 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.

[0065] 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 like the term “comprising” as an open transition word without precluding any additional or other elements.

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

[0067] The terminology used herein is to describe particular embodiments only and is not intended to be limiting the disclosure. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context 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 combinations of one or more of the associated listed items.

[0068] Embodiments herein relate to systems and methods for enabling a retry mechanism in the network. In a telecommunication network, the policy control function (PCF) and a policy and charging rules function (PCRF) can provision application detection and control (ADC) rules to the deep packet inspection (DPI) node via a Sd reference point. The Sd reference point facilitates communication and interaction between network functions in the 5G Core (5GC) network architecture. The PCF and PCRF select the ADC rules based on information obtained from the Policy and Chaiging Enforcement Function (PCEF) / Session Management Function (SMF) via the Gx/N7 reference point, e.g., request type, subscriber/device-related information, location information. The Gx/N7 reference point facilitates communication and interaction between network elements responsible for policy control and charging management. Further, once the session over the Sd interface has been established between the PCF and PCRF and the DPI node, the PCF and PCRF initiate a traffic detection function (TDF) session request (TSR) message towards the DPI node. The TSR refers to a request initiated by a network element to the TDF to establish a session. The TDF is a network function responsible for detecting and analyzing traffic flows within the network, typically at the user plane level. The PCF and PCRF maintain the session until the termination message is received over Gx/N7 reference points.

[0069] In case when a negative response is received at the PCF and PCRF, in response to the TDF Session Answer (TSA) or TDF Session Request (TSR) diameter message timeout, network fluctuation issues may be raised, or overload situations may occur at the DPI node or a Diameter Routing Agent (DRA). In such cases, the PCF and PCRF cannot provision ADC rules in the DPI node. In such cases, service providers should follow regulatory requirements, and correct ADC rules should be provisioned automatically, even in network failure cases. Further, retrying continuously over the Sd interface increases the signalling load on the network. In an embodiment, the at least one received response message may include a success response. The success response indicates that the session request has received a timely response from the DPI node and the PCF+PCRF has pushed correct ADC rules towards the DPI node. Thus, the retry mechanism may not be performed when the at least one received response message include the success response.

[0070] In order to overcome the above-mentioned technical problem, the PCF and PCRF can be configured with a runtime configurable flag to establish the session between the PCF and PCRF and the DPI node. The runtime configurable flag is used to determine whether to send a retry TSR message to the DPI node. The configurable flag is set to true or false based on the type of error message received from DPI and based on the update message received from the SMF or Packet Data Network Gateway (PGW) over the over Gx/N7 reference points.

[0071] In an embodiment, if the flag is true, the PCF and PCRF can retry the TSR message to the DPI node upon reception of any update message over the Gx/N7 reference points. In each instance when the update message is received, the PCF and PCRF retries communicating the TSRmessage towards the DPI node. This retry logic based on the configurable flags runs until Sd session is established between the PCF and PCRF and DPI node. In this manner, the retry logic based on the configurable flags facilitates provisioning the ADC rules at DPI node. In case when the flag is false, the PCF and PCRF may not retry the TSR message. Therefore, the flag can be set as per network requirement and accordingly, both functions are available at the PCF and PCRF.

[0072] The various embodiments throughout the disclosure will be explained in more detail with reference to FIGS. 1-6.

[0073] FIG. 1 illustrates an example network architecture (100) for implementing a system (108) for enabling a retry mechanism in a network (106), in accordance with an embodiment of the present disclosure.

[0074] As illustrated in FIG. 1, one or more computing devices (104-1, 104- 2... 104-N) may be connected to the system (108) through the network (106). A person of ordinary skill in the art will understand that the one or more computing devices (104-1, 104-2... 104-N) may be collectively referred as computing devices (104) and individually referred as a computing device (104). One or more users (102-1, 102-2... 102 -N) may provide one or more requests to the system (108). A person of ordinary skill in the art will understand that the one or more users (102- 1, 102-2... 102-N) may be collectively referred as users (102) and individually referred as a user (102). Further, the computing devices (104) may also be referred to as a user equipment (UE) (104) or as UEs (104) throughout the disclosure.

[0075] In an embodiment, the computing device (104) may include, but not be limited to, a mobile, a laptop, etc. Further, the computing device (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, audio aid, microphone, or keyboard. Furthermore, the computing device (104) may include a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, a laptop, a general- purpose computer, a desktop, a personal digital assistant, a tablet computer, and a mainframe computer. Additionally, input devices for receiving input from the user 102 such as a touchpad, touch-enabled screen, electronic pen, and the like may be used.

[0076] In an embodiment, network (106) may include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network (106) may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof. The UE (104) may be communicatively coupled with the network (106). The communicatively coupling comprises receiving, from the UE (104), a connection request by the network (106), sending an acknowledgment of the connection request to the UE (104), and transmitting a plurality of signals in response to the connection request.

[0077] FIG. 2 illustrates an example block diagram of the system (108) for enabling the retry mechanism in the network (106), in accordance with an embodiment of the present disclosure.

[0078] Referring to FIG. 2, in an embodiment, the system (108) includes a receiving unit (202), a memory (204), interface(s) (206), a processing unit (208), and a database (210). The receiving unit (202) is configured to receive at least one create request from at least one network entity. In an embodiment, the at least one create request includes a ‘Npcf_SMpolicy Control_Create Request’ or an initial credit control request (CCR-I). The ‘Npcf_SMpolicy Control_Create Request’ represents a request to create or update service-specific policies, enabling network operators to define and enforce policies tailored to specific services, subscribers, or network conditions. The CCR-I ensures that subscriber sessions are appropriately authorized and charged based on operator-defined policies and subscriber account status. In some embodiments, the at least one network entity includes at least one of a session management function (SMF), a charging function (CHF), a binding support function (BSF), a network repository function (NRF), an access and mobility management function (AMF), an online charging system (OCS), a packet data network gateway (PGW), a network management system (NMS), a subscription profile repository (SPR) and an application function (AF).

[0079] In an embodiment, the processing unit (208) is configured to communicate the at least one received create request towards a network function. In some embodiments, the network function includes a policy control function (PCF) and a policy and chaiging rules function (PCRF). In an embodiment, the processing unit (208) is configured to communicate, by the network function, at least one session request towards a network node (deep packet inspection (DPI) node). In an embodiment, the at least one session request includes a traffic detection function (TDF) session request (TSR) message towards the DPI node. In an embodiment, the processing unit (208) is configured to receive, by the network function, at least one response message from the DPI node. In an embodiment, the at least one response message includes a TDF Session Answer (TSA). TDF Session Answer (TSA) refers to a mechanism or protocol related to TDF within the network architecture. The TDF is responsible for identifying and classifying traffic flows based on various attributes such as application type, Quality of Service (QoS) requirements, and security considerations. The TSA within the TDF could denote a specific type of response or action taken by the network based on the detected traffic during a session. This could include routing decisions, traffic prioritization, application-specific optimizations, or security enforcement measures. In an embodiment, the processing unit (208) is configured to determine if the at least one received response message includes at least one negative response. In an embodiment, the at least one negative response includes a session request timeout message (TSR timeout message) and an error message received in the TSA. The TSR timeout message is likely sent when a session request times out, indicating that the requested session couldn't be established within the specified time frame. This could happen due to network congestion, communication errors, or other factors delaying the establishment of the session. Further, the error message received in the TSA may refer to an error or negative response related to traffic steering or management. This could include messages indicating problems with routing, congestion, policy enforcement, or other issues affecting the handling of network traffic. In an embodiment, the system (108) is further configured to communicate, by the network function, at least one answer message to the at least one network entity. In an embodiment, the at least one answer message includes a ‘201 created’ message or an initial credit control answer (CCA -I) message . In an aspect, the “201 Created” message is a Hypertext Transfer Protocol (HTTP) response status code indicating that a request has been fulfilled and has resulted in one or more new resources being created. It signifies the successful creation or establishment of a session, service, or resource. In an embodiment, the at least one received response message may include a success response. The success response indicates that the session request has received a timely response from the DPI node and the PCF+PCRF has pushed correct ADC rules towards the DPI node. Thus, the retry mechanism may not be performed when the at least one received response message include the success response.

[0080] In an embodiment, the processing unit (208) is configured to provision at least one flag at the network function. In an embodiment, the processing unit (208) is configured to recommunicate, by the network function, the at least one session request towards the DPI node when at least one condition is met. In an embodiment, the at least one condition includes at least the one provisioned flag is true and at least one update request is received from the at least one network entity at the network function. In an embodiment, the at least one update request is ‘Npcf_SMpolicy Control_Update Request’ or an update credit control request (CCR-U) for the same at least one established session. The Npcf_SMpolicy Control_Update Request is made to update or modify an existing service-specific policy within the network. The CCR-U enables dynamic updates to credit control parameters during ongoing subscriber sessions, allowing network operators to adapt to changing service requirements, subscriber needs, and network conditions in real-time. In an embodiment, at least one recommunicated session request includes the TSR request. The TSR refers to the initiation of a session for traffic detection and classification purposes. The TDF is a network function responsible for detecting and analyzing traffic flows within the network, typically at the user plane level. The TSR is triggered when the need for traffic detection and classification arises, often based on the subscriber’s activity or network policies. The TSR is sent from the PCF+PCRF (404) or other network elements to the TDF (e.g., DPI node (406)). The request includes parameters such as subscriber context, session identifiers, and possibly specific traffic flow information.

[0081] In an embodiment, the at least one update request is received from the at least one network entity at the network function over the Gx/N7 reference points.

[0082] In an embodiment, the processing unit (208) is configured to establish at least one session between the network function and the DPI node based on the at least one recommunicated session request. In an embodiment, the processing unit (208) is configured to install, by the network function, a plurality of rules on the DPI node based on the at least one established session. In an embodiment, the plurality of rules includes a plurality of ADC rules. In an aspect, the ADC rules define criteria for identifying different types of applications based on their traffic patterns, protocols, or other attributes. For example, streaming video, VoIP calls, web browsing, and gaming may all have distinct signatures that can be detected by examining packet headers, payload characteristics, or behaviour paterns. In an embodiment, the at least one session request is recommunicated towards the DPI node until the least one session is established between the network function and the DPI node.

[0083] In an embodiment, the system is further configured to communicate, by the network function, ‘200 OK’ or an update credit control answer (CCA-U) message.

[0084] The processing unit (208) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that process data based on operational instructions. Among other capabilities, the processing unit (208) 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 comprise any non- transitory storage device including, for example, volatile memory such as randomaccess memory (RAM), or non-volatile memory such as erasable programmable read only memory (EPROM), flash memory, and the like.

[0085] In an embodiment, the system (108) may include the interface(s) (206). The interface(s) (206) may comprise a variety of interfaces, for example, interfaces for data input and output devices (I/O), storage devices, and the like. The interface(s) (206) may facilitate communication through 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, the processing unit (208) and the database (210). Further, the processing unit (208) may include one or more engine(s) such as, but not limited to, an input/output engine, an identification engine, and an optimization engine.

[0086] In an embodiment, the processing unit (208) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing unit (208). In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing unit (208) may be processor-executable instructions stored on a non- transitory machine-readable storage medium and the hardware for the processing unit (208) may comprise 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 unit (208). In such examples, the system may comprise 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 and the processing resource. In other examples, the processing unit (208) may be implemented by electronic circuitry.

[0087] In an embodiment, if the flag is true, PCF and PCRF can retry the TSR message upon reception of any update message over Gx/N7 reference points. In each instance, when the update message is received, PCF and PCRF retries the TSR message. This retry logic based on the configurable flags runs until Sd session is established between PCF and PCRF, and DPI. In this manner, the retry logic based on the configurable flags facilitates provisioning the ADC rules at the DPI node. In case when the flag is false, the PCF and PCRF may not retry the TSR message. Therefore, the flag can be set as per network requirements, and accordingly, both functions are available at PCF and PCRF.

[0088] Although FIG. 2 shows exemplary components of the system (108), in other embodiments, the system 108 may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 2. Additionally, or alternatively, one or more components of the system (108) may perform functions described as being performed by one or more other components of the system (108). [0089] FIG. 3 illustrates an exemplary representation of a system architecture (300) showing a connection of PCF and PCRF (also referred to as converged PCF”) with other network elements through corresponding interfaces, in accordance with some embodiments of the present disclosure.

[0090] In some embodiments, the PCF and the PCRF may be referred to as a converged policy control function (PCF+PCRF) (302). In an embodiment, the PCF+PCRF (302) is connected to the AMF (304) with an N15 interface therebetween. The AMF (304) is responsible for managing access to the 5G network and handling mobility-related functions for UE devices.

[0091] In an embodiment, the PCF+PCRF (302) is connected to the OCS (306) with a Sy interface. The OCS (306) is responsible for real-time charging and credit management for various network services offered to subscribers.

[0092] In an embodiment, the PCF+PCRF (302) is connected to the PGW (308) with a Gx interface therebetween. The PGW (308) serves as the point of interconnection between the mobile network and external packet data networks, such as the internet or private corporate networks.

[0093] In an embodiment, the PCF+PCRF (302) is connected to the NMS (310) and the SPR (312). The network operators use the NMS to monitor, manage, and control various aspects of the 5G network infrastructure. The NMS (310) provides operators with tools and functionalities to ensure the efficient operation, optimization, and maintenance of the network. The SPR (312) is responsible for storing and managing subscriber profiles and subscription-related information.

[0094] In an embodiment, the PCF+PCRF (302) is connected to the AF (314) with an Rx interface between. The AF (314) is a network function responsible for providing application-specific capabilities and services within the 5G Core architecture.

[0095] In an embodiment, the PCF+PCRF (302) is connected to the NRF (316) with an Nnrf interface therebetween. The NRF (316) plays a critical role in the management and orchestration of network functions and services.

[0096] In an embodiment, the PCF+PCRF (302) is connected to the BSF (318) with an Nbsf interface therebetween. The PCF+PCRF (302) is connected to the CHF (320) with a N28 interface therebetween. The CHF (320) plays a crucial role in managing charging-related functions within the network, including real-time charging, policy control, and usage monitoring.

[0097] In an embodiment, the PCF+PCRF (302) is connected to the SMF (322) with a N7 interface therebetween. The SMF (322) plays a crucial role in establishing, managing, and terminating communication sessions between User Equipment (UE) and 5G network services.

[0098] In an embodiment, the PCF+PCRF (302) is connected to the DPI (324) with an Sd interface therebetween. The DPI (324) provides detailed visibility into network traffic, allowing network operators to monitor, control, and optimize network performance, security, and user experience.

[0099] FIG. 4 illustrates an exemplary representation of flow diagram representing a method (400) for enabling the retry mechanism in the network, in accordance with some embodiments of the present disclosure.

[00100] At step 408, the SMF/PGW (402) communicates the Npcf_SMpolicy Control_Create Request or an initial credit control request (CCR- I) towards the PCF+PCRF (404).

[00101] At step 410, the PCF+PCRF (404) communicates the TSR message towards the DPI (406).

[00102] At step 412, the PCF+PCRF (404) communicates the ‘201 created’ or an initial credit control answer (CCA-I) message towards the SMF/PGW (402).

[00103] At step 414, the DPI (406) communicates the TSA message towards the PCF+PCRF (404). In an embodiment, it is determined if the TSA message includes at least one negative response. In an embodiment, the at least one negative response includes a TSR timeout message, and an error message received in the TSA. In an embodiment, in response to the negative response, at least one flag is provisioned at the PCF+PCRF (404) and at least one session request is recommunicated, by the PCF+PCRF (404), the towards the DPI node (406) when at least one condition is met. In an embodiment, the at least one condition includes at least the one provisioned flag is true and at least one update request is received from the SMF/PGW (402) at the PCF+PCRF (404).

[00104] At step 416, the SMF/PGW (402) communicates the Npcf_SMpolicy Control_Update Request or an update credit control request (CCR- U) for the established session towards the PCF+PCRF (404).

[00105] At step 418, the PCF+PCRF (404) communicates the TSR message towards the DPI (406) and the DPI (406) communicates the TSA message towards the PCF+PCRF (404).

[00106] At step 420, the PCF+PCRF (404) communicates a ‘200 OK’ or an update credit control answer (CCA-U) message towards the SMF/PGW (402).

[00107] FIG. 5 illustrates an example computer system 500 in which or with which the embodiments of the present disclosure may be implemented.

[00108] As shown in FIG. 5, the computer system (500) may include an external storage device (510), a bus (520), a main memory (530), a read-only memory (540), a mass storage device (550(), a communication port(s) (560), and a processor (570). A person skilled in the art will appreciate that the computer system (500) may include more than one processor and communication ports. The processor (570) may include various modules associated with embodiments of the present disclosure. The communication port(s) (560) may be any of an RS-232 port for use with a modem-based dialup connection, a 10/100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication ports(s) (560) may be chosen depending on a network, such as a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system (500) connects. [00109] In an embodiment, the main memory (530) may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (540) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chip for storing static information e.g., start-up or basic input/output system (BIOS) instructions for the processor (570). The mass storage device 550 may be any current or future mass storage solution, which can 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).

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

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

[00112] FIG. 6 illustrates another exemplary flow diagram for the method (600) for enabling a retry mechanism in the network (106), in accordance with an embodiment of the present disclosure. [00113] At step 602: The method (600) includes communicating, by at least one network entity, at least one create request towards a network function. In an embodiment, the SMF/PGW (402) communicates at least one ‘Npcf_SMpolicy Control Create Request’ or an initial credit control request (CCR-I) towards the PCF+PCRF (404). In an embodiment, when the UE (104) initiates a service request, such as starting a data session or accessing a specific application, the SMF/PGW (402) evaluates the service requirements and subscriber context. Based on the session context (e.g., service type, QoS requirements), the SMF/PGW (402) determines the need for specific policies. For example, it may need to establish or update policies related to QoS parameters, bandwidth allocation, or traffic prioritization. If policy creation or update is required, the SMF/PGW (402) generates the ‘Npcf_SMpolicy Control_Create Request’. This message includes details about the desired policies and service-specific parameters. The 'Npcf_SMpolicy Control_Create Request' is then sent from the SMF/PGW (402) to the PCF+PCRF (404) overthe interface. This interface uses protocols like Diameter to ensure secure and reliable communication between network functions. In an embodiment, the CCR-I request is initiated by the SMF/PGW (402) to request credit authorization from the PCF+PCRF (404) before allowing the subscriber to start using a service or session. When the subscriber initiates a new service or session (e.g., starting a data session, making a voice call), the SMF/PGW (402) evaluates the service requirements. If the service requires charging or if there are specific service attributes that may impact charging (like data volume or duration), the SMF/PGW (402) generates a CCR-I message.

[00114] At step 604: The method (600) includes communicating by the network function, at least one session request towards a network node (e.g., deep packet inspection (DPI) node (406)) based on the at least one communicated create request. In an embodiment, the PCF+PCRF (404) communicates the TSR message towards the DPI node (406). The TSR refers to the initiation of a session for traffic detection and classification purposes. The TDF is a network function responsible for detecting and analyzing traffic flows within the network, typically at the user plane level. The TSR is triggered when the need for traffic detection and classification arises, often based on the subscriber’s activity or network policies. The TSR is sent from the PCF+PCRF (404) or other network elements to the TDF (e.g., DPI node (406)). The request includes parameters such as subscriber context, session identifiers, and possibly specific traffic flow information.

[00115] At step 606: The method (600) includes receiving, by the network function, at least one response message from the DPI node (406). In an embodiment, the PCF+PCRF (404) receives a TSA message from the DPI node (406). The TSA response is generated in reply to a TSR from the DPI node (406) towards the PCF+PCRF (404). The TSA serves to acknowledge and confirm the establishment or modification of a session between the DPI node (406) and the PCF/PCRF(404).

[00116] At step 608: The method (600) includes determining if the at least one received response message includes at least one negative response. In an embodiment, the at least one negative response includes a session request timeout message (TSR timeout message) and an error message received in the TSA. In an embodiment, the negative response indicates the network fluctuation issues or the overload situations occur at the DPI node (406). The TSRtimeout message signifies that the expected response did not arrive within the specified timeframe, necessitating further action to handle the timeout gracefully and potentially retry the request. Similarly, error messages received from the TSA provide specific feedback on issues encountered during traffic steering, such as service unavailability or invalid parameters. Detecting these errors allows systems to promptly address issues, adjust parameters, or implement fallback procedures to ensure uninterrupted service and optimal network performance. The handling of negative responses involves parsing and analyzing response messages in real-time, checking for predefined error codes or message types that indicate a negative outcome. In an embodiment, the at least one received response message may include a success response. The success response indicates that the session request has received a timely response from the DPI node and the PCF+PCRF has pushed correct ADC rules towards the DPI node. Thus, the retry mechanism may not be performed when the at least one received response message include the success response.

[00117] At step 610: The method (600) includes provisioning at least one flag at the network function and recommunicating, by the network function, the at least one session request towards the DPI node (406) when at least one condition is met. In an embodiment, in response to the negative response, at least one flag is provisioned at the PCF+PCRF (404) and at least one session request is recommunicated, by the PCF+PCRF (404), the towards the DPI node (406) when at least one condition is met. In an embodiment, the at least one condition includes at least the one provisioned flag is true and at least one update request is received from the SMF/PGW (402) at the PCF+PCRF (404). In an embodiment, when the PCF+PCRF (404) detects that the session request has not received a timely response or has encountered an error, it initiates the recommunication process. This may be triggered by factors such as network timeouts, communication failures, or the need to update policies dynamically. The PCF+PCRF (404) reconstructs the session request message, ensuring all necessary parameters such as subscriber identifiers, service context, and policy rules are accurately included. The PCF+PCRF (404) resends the session request message over the relevant interface (e.g., Gx/N7) towards the DPI node responsible for deep packet inspection and traffic management. Upon receiving the recommunicated session request, the DPI node (406) performs its tasks, which may include deep packet inspection to classify traffic, enforce specific policies, or apply quality of service parameters. The DPI node (406) evaluates the session request based on its configured rules and operational context. The outcome of the recommunication process depends on the response received from the DPI node (406). If successful, the session proceeds as intended, with policies effectively enforced. If unsuccessful, the PCF+PCRF (404) may initiate additional retries or implement error handling procedures based on predefined network policies. In an embodiment, the at least one flag is a Boolean flag that is provisioned based on a configuration (setting parameters or options that dictate how the network function operates within the network) at the network function. When the value of the at least one provisioned flag is set to true (e.g., 1), the retry mechanism is performed. The Boolean flag-based configuration in the network function determines whether a specific feature or behavior, such as a retry mechanism, will be enabled, or disabled based on the flag’s value. When the flag is setto true, the retry mechanism becomes active and operates according to its defined parameters and logic. This configuration approach allows network operators or administrators to control the activation of retry mechanisms dynamically, depending on operational needs or specific network conditions.

[00118] At step 612: the method (600) includes establishing at least one session between the network function and the DPI node (406) based on the at least one recommunicated session request. In an embodiment, at least one session is established between the PCF+PCRF (404) and the DPI node (406). In an embodiment the at least one session is the Sd (Session Directory) session. This session is established to facilitate the seamless management of policies, QoS parameters, and operational configurations across the network infrastructure. During the establishment of an Sd session, the PCF+PCRF (404) and the DPI node (406) exchange essential data necessary for effective traffic management, service provisioning, and subscriber management. This includes synchronizing session states, updating policy rules, and coordinating service activations or modifications based on real-time network conditions and subscriber requirements. Moreover, the Sd session supports fault management and performance monitoring activities, enabling proactive detection and resolution of network issues. It ensures that network operations adhere to defined service-level agreements (SLAs) and regulatory compliance requirements, thereby enhancing overall network reliability, efficiency, and service delivery capabilities.

[00119] At step 614: The method (600) includes installing, by the network function, a plurality of rules on the DPI node (406) based on the at least one established session. In an embodiment, the PCF+PCRF (404) installs the plurality of ADC rules at the DPI node (406). The ADC rules define how network traffic is identified, classified, and prioritized to ensure efficient resource utilization and enhance user experience. The ADC rules enable network operators to differentiate between various types of traffic such as web browsing, streaming media, voice calls, or file transfers. This classification allows for the implementation of tailored policies that govern aspects like QoS, bandwidth allocation, and application prioritization. The installation of ADC rules at the DPI node (406) by the PCF+PCRF (404) involves a systematic process aimed at enabling precise traffic management and policy enforcement within telecommunications networks. Firstly, the PCF+PCRF defines a comprehensive set of ADC rules based on network policies, subscriber profiles, and service-level agreements. These rules are crafted to specify how traffic should be identified, classified, and prioritized across the network. Parameters such as application signatures, protocol identifiers, and QoS criteria are configured to ensure accurate traffic classification and optimal resource allocation. Once defined, the PCF+PCRF (404) communicates these ADC rules to the DPI node (406) via standardized interfaces such as Gx/N7, utilizing protocols like Diameter for efficient data exchange. The DPI node (406), upon receiving these rules, undertakes the installation process, which involves integrating them into its rule database or configuration repository. This step ensures that the DPI node (406) is equipped to perform real-time inspection of incoming packets, accurately matching them against the installed ADC rules. The installed ADC rules enable the DPI node (406) to dynamically monitor and manage traffic flows based on predefined policies. By inspecting packet headers and payloads, the DPI node (406) identifies applications, protocols, or specific traffic types, applying corresponding QoS policies or traffic steering directives as dictated by the ADC rules.

[00120] In some embodiments, the at least one condition includes at least one provisioned flag is true and at least one update request is received from the at least one network entity at the network function.

[00121] In some embodiments, the at least one session request is recommunicated towards the DPI node (406) until the least one session is established between the network function and the DPI node (406). [00122] In some embodiments, the plurality of rules installed at the DPI node (406) includes a plurality of application detection and control rules.

[00123] In some embodiments, the at least one negative response includes a session request timeout message and an error message.

[00124] In some embodiments, the method further includes communicating, by the network function, at least one answer message towards the at least one network entity. In an embodiment, the at least one answer message may include the ‘201 created’ message or the initial credit control answer (CCA -I) message. In an aspect, the “201 Created” message is the HTTP response status code indicating that the CCR-I request has been fulfilled and has resulted in one or more new resources being created. It signifies the successful creation or establishment of a session, service, or resource. In an embodiment, the at least one answer message may include the 2000K/CCA-U message in response to the CCR-U message. The CCA- U message serves to update and synchronize session-related parameters between these network elements, ensuring accurate and responsive control over subscriber usage and service provisioning. During operational scenarios, such as data sessions or voice calls, the PCF+PCRF (404) dynamically monitors and manages the consumption of network resources by subscribers based on predefined policies and charging rules. The CCA-U message is specifically crafted to convey essential information, including updated session usage metrics, remaining credit balances, granted service units, and any final unit reservations (FURs) that allocate resources for ongoing services. By transmitting the CCA-U message, the PCF+PCRF (404) effectively informs the SMF/PGW (402) about changes in subscriber activity and resource consumption in real-time. This enables the network to promptly adjust service parameters, enforce QoS policies, and allocate additional resources as needed, ensuring continuous service delivery aligned with subscriber expectations and service-level agreements (SLAs).

[00125] In some embodiments, the network function includes a policy control function (PCF) and a policy and charging rules function (PCRF). [00126] In some embodiments, the at least one network entity includes at least one of a session management function (SMF) (322), a chaiging function (CHF) (320), a binding support function (BSF) (318), a network repository function (NRF) (316), an access and mobility management function (AMF) (304), an online charging system (OCS) (306), a packet data network gateway (PGW) (308), a network management system (NMS) (310), a subscription profde repository (SPR) (312) and an application function (AF) (314).

[00127] In an exemplary embodiment, the present disclosure discloses a user equipment (UE) (104) communicatively coupled with a network (106). The coupling comprises steps of receiving, by the network (106), a connection request from the UE (104), sending, by the network, an acknowledgment of the connection request to the UE (104) and transmitting a plurality of signals in response to the connection request. A retry mechanism is enabled in the network (106) by a method (600) includes communicating (602), by at least one network entity, at least one create request towards a network function. The method (600) includes communicating (604), by the network function, at least one session request towards a deep packet inspection (DPI) node (406) based on the at least one communicated create request. The method (600) includes receiving (606), by the network function, at least one response message from the DPI node (406). The method (600) includes determining (608) if the at least one received response message includes at least one negative response. The method (600) includes responsive to determining, provisioning (610) at least one flag at the network function and recommunicating, by the network function, the at least one session request towards the DPI node (406) when at least one condition is met. The method (600) includes establishing (612) at least one session between the network function and the DPI node (406) based on the at least one recommunicated session request. The method (600) includes installing (614), by the network function, a plurality of rules on the DPI node (406) based on the at least one established session.

[00128] The present disclosure provides technical advancement related to managing performance of the network. This advancement addresses the limitations of existing solutions by providing an improved system and method for enabling a retry mechanism in the network. By implementing the present disclosure, the PCF and the PCRF can effectively deploy accurate ADC rules despite of network instability/fluctuations. Thus, the present disclosure ensures smooth and efficient operation of the network and results in enhancing the service provider reliability and the performance of the network.

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

ADVANTAGES OF THE INVENTION

[00130] The present disclosure provides a system and a method for throttling services with a retry mechanism in a network.

[00131] The present disclosure provides a system and a method for enabling a retry mechanism in a network.

[00132] The present disclosure provides a system and a method to achieve efficient resource utilization at the deep packet inspection (DPI) node.

[00133] The present disclosure provides a system and a method to provide a system and a method that are economical and easy to implement.

Claims

We claim:

1. A method (600) for enabling a retry mechanism in a network (106), the method (600) comprising: communicating (602), by at least one network entity, at least one create request towards a network function; communicating (604), by the network function, at least one session request towards a network node based on the at least one communicated create request; receiving (606), by the network function, at least one response message from the network node ; determining (608) if the at least one received response message includes at least one negative response; responsive to determining, provisioning (610) at least one flag at the network function and recommunicating, by the network function, the at least one session request towards the network node when at least one condition is met; establishing (612) at least one session between the network function and the network node based on the at least one recommunicated session request; and installing (614), by the network function, a plurality of rules on the network node based on the at least one established session.

2. The method (600) as claimed in claim 1, wherein the at least one condition includes: at least one provisioned flag is true; and at least one update request is received from the at least one network entity at the network function.

3. The method (600) as claimed in claim 1, wherein the at least one session request is recommunicated towards the network node until the at least one session is established between the network function and the network node.

4. The method (600) as claimed in claim 1, wherein the plurality of rules installed at the network node includes a plurality of application detection and control rules.

5. The method (600) as claimed in claim 1, wherein the at least one negative response includes a session request timeout message or an error message.

6. The method (600) as claimed in claim 1 , further comprising communicating, by the network function, at least one answer message towards the at least one network entity.

7. The method (600) as claimed in claim 1, wherein the network function includes a policy control function (PCF) and a policy and charging rules function (PCRF).

8. The method (600) as claimed in claim 1, wherein the at least one network entity includes at least one of a session management function (SMF) (322), a charging function (CHF) (320), a binding support function (BSF) (318), a network repository function (NRF) (316), an access and mobility management function (AMF) (304), an online charging system (OCS) (306), a packet data network gateway (PGW) (308), a network management system (NMS) (310), a subscription profde repository (SPR) (312) and an application function (AF) (314).

9. A system (108) for enabling a retry mechanism in a network (106), the system (108) comprising: a receiving unit (202) configured to receive at least one create request from at least one network entity; a processing unit (208); and a memory (204) coupled to the processing unit, wherein the memory (204) includes computer implemented instructions to configure the processing unit (208) to: communicate the at least one received create request towards a network function; communicate, by the network function, at least one session request towards a network node based on the at least one communicated create request; receive, by the network function, at least one response message from the network node; determine if the at least one received response message includes at least one negative response; responsive to determining, provision at least one flag at the network function and recommunicate, by the network function, the at least one session request towards the network node when at least one condition is met; establish at least one session between the network function and the network node based on the at least one recommunicated session request; and install, by the network function, a plurality of rules on the network node based on the at least one established session.

10. The system (108) as claimed in claim 9, wherein the at least one condition includes: the at least one provisioned flag is true; and at least one update request is received from the at least one network entity at the network function.

11. The system (108) as claimed in claim 9, wherein the at least one session request is recommunicated towards the network node until the at least one session is established between the network function and the network node.

12. The system (108) as claimed in claim 9, wherein the plurality of rules installed at the network node include a plurality of application detection and control rules.

13. The system (108) as claimed in claim 9, wherein the at least one negative response includes a session request timeout message or an error message.

14. The system (108) as claimed in claim 9, is further configured to communicate, by the network function, at least one answer message towards the at least one network entity.

15. The system (108) as claimed in claim 9, wherein the network function includes a policy control function (PCF) and a policy and charging rules function (PCRF).

16. The system (108) as claimed in claim 9, wherein the at least one network entity includes at least one of a session management function (SMF) (322), a charging function (CHF) (320), a binding support function (BSF) (318), a network repository function (NRF) (316), an access and mobility management function (AMF) (304), an online charging system (OCS) (306), a packet data network gateway (PGW) (308), a network management system (NMS) (310), a subscription profile repository (SPR) (312) and an application function (AF) (314).

17. A user equipment (UE) (104) communicatively coupled with a network (106), the coupling comprises steps of: receiving, by the network (106), a connection request from the UE

(104); sending, by the network (106), an acknowledgment of the connection request to the UE (104); and transmitting a plurality of signals in response to the connection request, wherein a retry mechanism is enabled in the network (106) by a method as claimed in claim 1.

18. A computer program product comprising a non-transitory computer- readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method (600) for enabling a retry mechanism in a network (106), the method (600) comprising: communicating (602), by at least one network entity, at least one create request towards a network function; communicating (604), by the network function, at least one session request towards a network node based on the at least one communicated create request; receiving (606), by the network function, at least one response message from the network node; determining (608) if the at least one received response message includes at least one negative response; responsive to determining, provisioning (610) at least one flag at the network function and recommunicating, by the network function, the at least one session request towards the network node when at least one condition is met; establishing (612) at least one session between the network function and the network node based on the at least one recommunicated session request; and installing (614), by the network function, a plurality of rules on the network node based on the at least one established session.