System and method for managing network requests

Abstract

The present disclosure relates to a system (102) and a method (500) for managing a request in a network (108). The method (500) includes receiving, by a network function (NF) (204), at least one request from an NF consumer (202); extracting, by the NF (204), at least one unique identifier, corresponding to at least one subscriber, from the at least one received request; determining, by the NF (204), at least one predefined criterion stored in a memory (304) associated with the NF (204); upon meeting the at least one predefined criterion, applying, by the NF (204), a modulo operation on the at least one extracted unique identifier to identify at least one policy control function (PCF) (206); and performing, by the NF (204), at least one operation based on the at least one identified PCF (206).

Description

SYSTEM AND METHOD FOR MANAGING NETWORK REQUESTSRESERVATION 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 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 present disclosure generally relates to the field of communication networks. More particularly, the present disclosure relates to a system and a method for managing network requests in distributed network architectures.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 expression ‘Network Function (NF)’ used hereinafter in the specification refers to a logical entity within a telecommunications core network, such as a fifth generation (5G) core network, that provides a specific service or performs a designated control or user-plane task. The NF is implemented as a software running on one or more physical or virtualized network nodes and is configured to interact with other NFs through service-based interfaces. Examples of NFs include an access and mobility management function (AMF), a session management function (SMF), a policy control function (PCF), a network exposure function (NEF), and a binding support function (BSF).

[0005] The expression ‘Access and Mobility Management Function (AMF)’ used hereinafter in the specification refers to a network function (NF) within a 5G core network responsible for managing user equipment (UE) registration, mobility, and connection handling. The AMF performs key functions such as user authentication, access authorization, mobility management (e.g., handover control), and security context establishment. It serves as the primary control point between the UE and the core network for signaling and session setup procedures.

[0006] The expression ‘Session Management Function (SMF)’ used hereinafter in the specification refers to a network function (NF) in a 5G core network responsible for managing and controlling user sessions and IP address allocations. The SMF handles session establishment, modification, and release, as well as policy enforcement control and interaction with the Policy Control Function (PCF).

[0007] The expression ‘Network Exposure Function (NEF)’ used hereinafter in the specification refers to a service enabler within the 5G core network that provides secure and controlled exposure of network capabilities and events to external applications or third-party services. The NEF enables application functions (AFs) to interact with core network functions through application programming interfaces (APIs), and supports functionalities such as event exposure, monitoring capabilities, policy control delegation, and application influence on traffic routing.

[0008] The expression ‘Application Function (AF)’ used hereinafter in the specification refers to a type of NF that provides application-level control or signaling functionality and interacts with control-plane NFs in the core network. The AF is associated with specific services, such as video streaming, voice-over-IP (VoIP), gaming, or internet of things (loT) applications.

[0009] The expression ‘NF Consumer’ used hereinafter in the specification refers to a network function that initiates requests to another NF, referred to as an NF Producer. The NF Consumer acts as a client in a service-based architecture (SBA) and is configured to consume services or functionality provided by otherNFs, such as the PCF. Examples of NF Consumers include the Application Function (AF), Session Management Function (SMF), and Network Exposure Function (NEF).

[0010] The expression ‘Binding Support Function (BSF) used hereinafter in the specification refers to a network function in the 5G core network architecture responsible for managing the association (binding) between an application session and the corresponding policy control information. The BSF is configured to receive requests from NF Consumers (e.g., AF) and determine, based on a subscriber identifier or network context, the appropriate PCF instance responsible for policy control.

[0011] The expression ‘Policy Control Function (PCF)’ used hereinafter in the specification refers to a centralized network function within the core network architecture responsible for making policy decisions related to Quality of Service (QoS), charging, traffic routing, access control, and other service-level rules. The PCF interacts with other NFs, including the BSF, SMF, and AF, to enforce policies that govern application sessions.

[0012] The expression ‘Service Communication Proxy (SCP)’ used hereinafter in the specification refers to a core network function in a 5G service-based architecture (SBA) that acts as an intermediary or relay node between consumer and producer network functions (NFs). The SCP is responsible for managing service communication paths, enforcing routing policies, supporting load balancing, failover mechanisms, and ensuring service discovery and request forwarding in a controlled and efficient manner.

[0013] The expression ‘modulo operation’ used hereinafter in the specification refers to a mathematical technique employed within a deterministic routing framework to compute a remainder value by dividing an input numerical value derived from a unique subscriber identifier such as a Subscription Permanent Identifier (SUPI) or International Mobile Subscriber Identity (IMSI) by a predefined number corresponding to the total count of available target networkfunction instances (e.g., PCFs). The resulting remainder (i.e., modulo result) serves as an index into a pre-configured mapping table that deterministically associates specific modulo outcomes with respective PCF instances.

[0014] The expression ‘modulo configuration parameter’ used hereinafter in the specification refers to a runtime-configurable setting stored in a memory associated with a network function or in an external configuration repository accessible to the network function. The modulo configuration parameter indicates whether a modulo-based fallback mechanism should be activated for selecting an appropriate Policy Control Function (PCF) instance. For example, the modulo configuration parameter may be implemented as a flag named “enable modulo fallback”, which is stored in the memory associated with the network function (e.g., BSF). When the network function detects that this flag is setto alogical true (i.e., in an enabled state), the network function proceeds to apply modulo operation for PCF selection even if database lookup fails or is bypassed.

[0015] The expression ‘Authorization and Authentication Request (AAR)’ used hereinafter in the specification refers to a control-plane message, typically compliant with the Diameter protocol, initiated by a network function (e.g., Application Function) toward a Policy Control Function (PCF) to request policy authorization for an application session.

[0016] The expression ‘Management Discovery Request’ used hereinafter in the specification refers to a control-plane signaling message generated by a network function consumer (e.g., AF or SMF) to determine or locate the appropriate Policy Control Function (PCF) instance responsible for handling a given subscriber session.

[0017] The expression ‘Subscription Permanent Identifier (SUPI)’ used hereinafter in the specification refers to a globally unique identifier assigned to a subscriber in a 5G system. The SUPI is used by the core network to identify a user across different access and core functions.

[0018] The expression ‘International Mobile Subscriber Identity (IMSI)’ used hereinafter in the specification refers to a globally unique number assigned to a mobile subscriber, as defined by 3GPP standards. The IMSI is composed of a Mobile Country Code (MCC), Mobile Network Code (MNC), and a Mobile Subscriber Identification Number (MSIN).

[0019] The expression, ‘Attribute-Value Pair (A VP)’ used hereinafter in the specification refers to a structured data format used in various communication protocols, such as a Diameter protocol, to convey specific parameters within signaling messages. Each AVP includes an attribute (or “type”) that defines the nature of the information, and a corresponding value that represents the content or data associated with that attribute.

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

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

[0022] In 5G network architecture, efficient handling of requests related to policy control is crucial for ensuring smooth communication between different network functions such as, a binding support function (BSF), a session management function (SMF) and a policy control function (PCF). The BSF plays a crucial role in managing Hypertext Transfer Protocol (HTTP) / 2 and Rx requests by interacting with the PCF. The BSF is responsible for routing these requests to an appropriate PCF instance, which manages network resource usage policies, service quality, and other critical network functions.

[0023] Conventionally, the BSF relies on stored PCF information in a database to accurately and efficiently route these requests. However, the PCF information may become unavailable for various reasons, such as server connection failures, database outages, or application errors. When the BSF cannot access the PCF information, then the BSF cannot route the requests correctly, resulting in significant disruptions to network’s functionality. These disruptions can lead to service interruptions, degraded user experiences, and decreased user satisfaction.

[0024] For instance, when an initial authentication and authorization request (AAR) is received, then the BSF attempts to find the appropriate PCF instance using the stored PCF information. If this information is unavailable, then the BSF fails to route the request correctly, leading to failed service delivery. In critical applications, such failures can have cascading effects, impacting many services and applications that rely on seamless network operation.

[0025] Further, in conventional 5G network implementations, the BSF relies on a central database to store the PCF information for each user session. This PCF information includes details like the specific PCF responsible for handling the request of a corresponding user. When the user initiates a session, the BSF retrieves the corresponding details from the database and routes the request accordingly.

[0026] However, this reliance on the central database introduces a potential vulnerability. Database failures or connectivity disruptions can hinder BSF processing of the PCF information. In such scenarios, the BSF might be unable to identify a correct PCF, leading to service interruptions, degraded network performance, and reduced network reliability.

[0027] Thus, there is a need for a system and a method that allows the BSF to effectively manage the requests even when the PCF information is not accessible.OBJECTIVES OF THE PRESENT DISCLOSURE

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

[0029] An objective of the present disclosure is to provide a system and a method for handling failures in fetching policy control function (PCF) information at binding support function (BSF) in 5G networks.

[0030] Another objective of the present disclosure is to provide a system and a method that ensures higher availability and reliability of BSF by implementing alternative mechanisms for routing requests when PCF information is unavailable.

[0031] Yet another objective of the present disclosure is to provide a system and a method that improves user satisfaction by ensuring uninterrupted service delivery and preventing service disruptions caused by the unavailability of PCF information.

[0032] Another objective of the present disclosure is to provide a system and a method that dynamically updates a modulo mapping table to accommodate changes in a network and maintain accurate routing of requests.

[0033] Yet another objective of the present disclosure is to provide customizable criteria for applying a modulo operation based on the unavailability of PCF information in a database or an active state of a modulo configuration parameter in a memory.

[0034] Another obj ective of the present disclosure is to reduce latency involved in handling requests by pre -configuring modulo mapping tables at both BSF and session communication proxy (SCP) server, ensuring faster routing decisions and minimizing delays in generating discovery responses.

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

[0036] In an exemplary embodiment, the present invention discloses a method for managing a request in a network. The method includes receiving, by a networkfunction (NF), at least one request from an NF consumer. The method further includes extracting, by the NF, at least one unique identifier, corresponding to at least one subscriber, from the at least one received request. The method further includes determining, by the NF, at least one predefined criterion stored in a memory associated with the NF. The method further includes upon meeting the at least one predefined criterion, applying, by the NF, a modulo operation on the at least one extracted unique identifier to identify at least one policy control function (PCF). The method further includes performing, by the NF, at least one operation based on the at least one identified PCF.

[0037] In some embodiments, the at least one request is one of an initial authorization and authentication request (AAR), and a management discovery request.

[0038] In some embodiments, the NF is a binding support function (BSF).

[0039] In some embodiments, the at least one unique identifier includes a subscription permanent identifier (SUPI), an international mobile subscriber identity (IMSI), or a combination thereof.

[0040] In some embodiments, the at least one predefined criterion includes at least one of: an unavailability of one or more details of the at least one PCF in a database; and an active state of a modulo configuration parameter in the memory. The active state triggers the modulo operation irrespective of availability of the one or more details of the at least one PCF in the database.

[0041] In some embodiments, the memory includes at least one mapping table pre-configured with a plurality of modulo result values representing one or more outcomes of the modulo operation, and one or more corresponding details of the at least one PCF associated with each modulo result value of the plurality of modulo result values.

[0042] In some embodiments, the at least one mapping table pre-configured at the NF and a service communication proxy (SCP) are identical.

[0043] In some embodiments, the modulo operation includes processing a portion of the at least one extracted unique identifier to generate an index value within a range defined by a number of available PCF instances.

[0044] In some embodiments, the at least one operation includes a routing of the at least one received request to the at least one identified PCF, and generating a response to the at least one received request based on information associated with the at least one identified PCF.

[0045] In an exemplary embodiment, a system for managing a request in a network is disclosed. The system includes a network function (NF) configured to receive at least one request from an NF consumer. The NF is further configured to extract at least one unique identifier, corresponding to at least one subscriber, from the at least one received request. The NF is further configured to determine at least one predefined criterion stored in a memory associated with the NF. The NF is further configured to upon meeting the at least one predefined criterion, apply a modulo operation on the at least one extracted unique identifier to identify at least one policy control function (PCF). The NF is further configured to perform at least one operation based on the at least one identified PCF.

[0046] In some embodiments, the at least one request is one of an initial authorization and authentication request (AAR), and a management discovery request.

[0047] In some embodiments, the NF is a binding support function (BSF).

[0048] In some embodiments, the at least one unique identifier includes a subscription permanent identifier (SUPI), an international mobile subscriber identity (IMSI), or a combination thereof.

[0049] In some embodiments, the at least one predefined criterion includes at least one of: an unavailability of one or more details of the at least one PCF in a database; and an active state of a modulo configuration parameter in the memory.The active state triggers the modulo operation irrespective of availability of the one or more details of the at least one PCF in the database.

[0050] In some embodiments, the memory includes at least one mapping table pre-configured with a plurality of modulo result values representing one or more outcomes of the modulo operation, and one or more corresponding details of the at least one PCF associated with each modulo result value of the plurality of modulo result values.

[0051] In some embodiments, the at least one mapping table pre-configured at the NF and a service communication proxy (SCP) are identical.

[0052] In some embodiments, the modulo operation includes processing a portion of the at least one extracted unique identifier to generate an index value within a range defined by a number of available PCF instances.

[0053] In some embodiments, the at least one operation includes a routing of the at least one received request to the at least one identified PCF, and generating a response to the at least one received request based on information associated with the at least one identified PCF.

[0054] In an exemplary embodiment, a user equipment (UE) communicatively coupled with a network is disclosed. The coupling includes 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. The UE is connected with a system configured to manage a request in the network. The system includes a network function (NF) configured to receive at least one request from an NF consumer. The NF is further configured to extract at least one unique identifier, corresponding to at least one subscriber, from the at least one received request. The NF is further configured to determine at least one predefined criterion stored in a memory associated with the NF. The NF is further configured to upon meeting the at least one predefined criterion, apply a modulo operation on the at least one extracted unique identifier to identify at least one policy control function (PCF). The NF isfurther configured to perform at least one operation based on the at least one identified PCF.

[0055] In an exemplary embodiment, a computer program product including a non-transitory computer-readable medium including instructions that, when executed by one or more processors, cause the one or more processors to execute a method for managing a request in a network. The method includes receiving, by a network function (NF), at least one request from an NF consumer. The method further includes extracting, by the NF, at least one unique identifier, corresponding to at least one subscriber, from the at least one received request. The method further includes determining, by the NF, at least one predefined criterion stored in a memory associated with the NF. The method further includes upon meeting the at least one predefined criterion, applying, by the NF, a modulo operation on the at least one extracted unique identifier to identify at least one policy control function (PCF). The method further includes performing, by the NF, at least one operation based on the at least one identified PCF.

[0056] 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.BRIEF DESCRIPTION OF DRAWINGS

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

[0058] FIG. 1 illustrates an exemplary network architecture for implementing a system to manage requests in a network, in accordance with embodiments of the present disclosure.

[0059] FIG. 2 illustrates an exemplary schematic block diagram representing a signaling architecture between a network function (NF) consumer, a NF and a policy control function (PCF) in a network environment, in accordance with embodiments of the present disclosure.

[0060] FIG. 3 illustrates an exemplary block diagram of the system for managing the requests in the network, in accordance with embodiments of the present disclosure.

[0061] FIG. 4 illustrates an exemplary flowchart of a process for performing PCF selection and routing of authorization and authentication request (AAR) at the NF, in accordance with embodiments of the present disclosure.

[0062] FIG. 5 illustrates an exemplary flow diagram of a method for managing the requests in the network, in accordance with embodiments of the present disclosure.

[0063] FIG. 6 illustrates an exemplary computer system in which or with which the system may be implemented, in accordance with embodiments of the present disclosure.

[0064] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network Architecture102 - System104-1, 104-2. . . 104-N - Plurality of User Equipment (UE)106-1, 106-2... 106-N - Plurality of Users- Network - Signaling Architecture - Network Function (NF) Consumer - Network Function (NF) - Policy Control Function (PCF)A - PCF1 B - PCF2 C - PCF3 D - PCF4 E - PCF5 - Block Diagram - Processor(s) - Memory - Plurality of Interfaces - Processing Engine - Database - Request Receiving Module - Identifier Extraction Module - Criteria Evaluation Module - Modulo Computation Module - Request Routing Module400 - Process500 - Method600 - Computer System610 - External Storage Device620 - Bus630 - Main Memory640 - Read-Only Memory650 - Mass Storage Device660 - Communication Ports670 - ProcessorDETAILED DESCRIPTION OF DISCLOSURE

[0065] In the following description, for the purposes of explanation, various specific details are set forth 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 any 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. Example embodiments of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.

[0066] 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 thoseskilled 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.

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

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

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

[0070] 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 features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0071] The terminology used herein is to describe 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. It should be noted that the terms “mobile device”, “user equipment”, “user device”, “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The invention is not limited to any device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.

[0072] As used herein, an “electronic device” or “portable electronic device” or “user device” or “communication device” or “user equipment” or “device” refers to any electrical, electronic, electromechanical, and computing device. The user device can receive and / or transmitting one or parameters, performing function / s, communicating with other user devices, and transmitting data to the other user devices. The user equipment may have a processor, a display, a memory, a battery, and an input-means such as a hard keypad and / or a soft keypad. The user equipment may be capable of operating on any radio access technology including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For instance, the user equipment may include, but not limited to, a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.

[0073] Further, the user device may also comprise a “processor” or “processing unit” includes processing unit, wherein processor refers to any logic circuitry for processing instructions. The processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input / output processing, and / or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor is a hardware processor.

[0074] Aspects of this disclosure are directed to a system and method for managing network requests in a 5G communication infrastructure, at a binding support function (BSF), when policy control function (PCF) information is unavailable due to database failures or other connectivity issues. In conventional architectures, the BSF relies on stored PCF information retrieved from a databaseto handle initial request types such as authorization and authentication requests (AAR) or management discovery requests. If the PCF information is missing or inaccessible, these requests cannot be properly routed or served, resulting in service degradation, delayed responses, or outright failure in processing a user session setup or policy enforcement.

[0075] The present disclosure introduces a fallback mechanism that enables theBSF to handle such requests using a modulo-based selection technique. Upon detecting the unavailability of the PCF information or when a modulo configuration parameter is active, the BSF uses a portion of a unique identifier (such as last n digits of a subscription permanent identifier (SUPI) / international mobile subscriber identity (IMSI)) of a subscriber as an input for a modulo operation, where a denominator corresponds to a number of available PCF instances. The resulting modulo value indexes into a preconfigured mapping table that associates modulo results with specific PCF instance details. This allows the BSF to forward the request or generate a discovery response even in the absence of database connectivity. The preconfigured mapping table is configured to be consistent between the BSF and a Service Communication Proxy (SCP) to ensure uniform routing decisions across network functions. This inventive approach enhances service availability, ensures uninterrupted handling of Rx / HTTP / 2 requests, and provides a robust and deterministic fallback mechanism that improves resilience and reliability in a 5G core network architecture.

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

[0077] FIG. 1 illustrates an exemplary network architecture (100) for implementing a system (102) to manage requests in a network (108), in accordance with embodiments of the present disclosure.

[0078] Referring to FIG. 1, the network architecture (100) may include one or more user equipment (UEs) (104-1, 104-2... 104-N) that may be associated with one or more users (106-1, 106-2... 106-N) and the system (102) in an environment.In an embodiment, the one or more UEs (104-1, 104-2... 104-N) may be communicated to the system (102) through the network (108). A person of ordinary skill in the art will understand that the one or more UEs (104-1, 104-2... 104-N) 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 “UE” may be used interchangeably throughout the disclosure. Although three UEs (104) are depicted in the FIG. 1, however any number of the UE (104) may be included without departing from the scope of the ongoing description. Similarly, a person of ordinary skill in the art will understand that the one or more users (106-1, 106-2... 106-N) may be individually referred to as the user (106) and collectively referred to as the users (106).

[0079] 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 embodiment, the UE (104) may include, but is not limited to, smartphones, smart watches, smart sensors (e.g., mechanical, thermal, electrical, magnetic, etc.), networked appliances, networked peripheral devices, networked lighting systems, 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 (106) and / or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the UE (104) may include, but not be limited to, intelligent multi-sensing, network-connected devices that can integrate seamlessly with each other and / or with a central server or a cloud-computing system or any other device that is network-connected.

[0080] In an embodiment, the UE (104) may include but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a smartphone, 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, a tablet computer, or another type of portable computer, a media playing device, a portablegaming system, and / or any other type of computer device with wireless communication capabilities, and the like.

[0081] In an embodiment, the UE (104) may include, but is not limited to, any electrical, electronic, electro-mechanical, or equipment, or a combination of one or more of the above devices, such as virtual reality (VR) devices, augmented reality (AR) devices, a general-purpose computer, a desktop, a personal digital assistant, a mainframe computer, or any other computing device. In another embodiment, 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 (106) or the entity such as a touchpad, 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.

[0082] Referring to FIG. 1, the UE (104) may communicate with the system (102) through a set of executable instructions residing on any operating system. In an embodiment, the set of executable instructions may reside within a network function (NF) (204), which is configured to manage and process network-related requests received from a NF consumer (202). The executable instructions may include logic for receiving, parsing, evaluating, and routing the network-related requests. The NF (204), through the set of executable instructions, enables dynamic policy control and seamless communication between the UEs (104) and a policy control function (PCF) (206), thereby facilitating network session establishment and management.

[0083] In an embodiment, the UE (104) may communicate with the system (102) through the network (108) for sending or receiving various types of data. In an embodiment, the network (108) may include at least one of a 5G network, a 6G network, or the like. The network (108) may enable the UE (104) to communicate with other devices in the network architecture (100) and / or with the system (102). The network (108) may include a wireless card or some other transceiverconnection to facilitate this communication. In another embodiment, the network (108) 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 or the like.

[0084] In an embodiment, the network (108) 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 (108) may also include, by way of example but not limitation, one or more of a radio access network (RAN), a wireless network, a wired network, the internet, the 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. In an embodiment, the system (102) may be connected to backend servers (not shown).

[0085] In an embodiment, the UE (104) is communicatively coupled with the network (108). The network (108) may receive a connection request from the UE (104). The network (108) may send an acknowledgment of the connection request to the UE ( 104) . The UE ( 104) may transmit a plurality of signals in response to the connection request.

[0086] Although the FIG. 1 shows exemplary components of the network architecture (100), in other embodiments, the network architecture (100) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 1. Additionally, or alternatively, one or more components of the network architecture (100) may perform functions described as being performed by one or more other components of the network architecture (100).

[0087] FIG. 2 illustrates an exemplary schematic block diagram representing a signaling architecture (200) between the NF consumer (202), the NF (204) and the PCF (206) in a network environment, in accordance with embodiments of the present disclosure. FIG. 2, with reference to FIG. 1, illustrates the signaling architecture (200) between the NF consumer (202), the NF (204) and the PCF (206) in a network environment.

[0088] In an embodiment, the NF consumer (202) may include, but is not limited to, network functions such as a session management function (SMF), an access and mobility management function (AMF), a network exposure function (NEF), and other core NFs that initiate the requests toward producer NFs (e.g. PCFs). In a preferred embodiment, the NF consumer (202) may be an application function (AF).

[0089] The NF consumer (202), such as the AF, is a critical network entity within the network (108) that is configured to initiate at least one request and facilitate the delivery of application-layer services to end-user devices such as the UEs (104). The request may be a service-related request, such as, but not limited to, a quality of service (QoS) control request, an application session management request, and so forth. In a preferred embodiment, the service-related request includes an initial authorization and authentication request (AAR), and a management discovery request. In an exemplary embodiment, the AAR and management discovery requests are control-plane mechanisms used by the NF consumer (202) to initiate, authorize, and route session-based services (e.g., streaming, voice over internet protocol (VoIP), gaming) through the network (108) by coordinating with the NF (204) and the PCF (206). These ensure that appropriate policies, QoS, and charging rules are applied for delivering the application-layer services to the UE (104).

[0090] For example, the AAR may be sent by the AF to request authorization and policy decisions from the PCF (206) for a service session (e.g., media streaming, VoIP). In an embodiment, the AAR may include session descriptors,such as, but not limited to, a media type (e.g., audio / video), QoS requirements (e.g., latency, bandwidth), a subscriber ID (e.g., subscription permanent identifier (SUPI) / international mobile subscriber identity (IMSI)), and so forth. Similarly, the management discovery request may be sent by the AF to identify at least one correct instance of the PCF (206) for a corresponding subscriber or session. In an embodiment, the management discovery request may be transmitted prior to or concurrently with the AAR, for the purpose of identifying the appropriate instance of the PCF (206) to which the AAR should be routed. This facilitates the delivery of the application-layer services, such as, but not limited to, video streaming, voice calling, real-time messaging, Internet of Things (loT) service provisioning, and other application-layer services.

[0091] In an embodiment, the NF consumer (202) interfaces with one or more applications operating on the UE (104) and functions as an intermediary between such applications and an underlying core network (108). In an exemplary embodiment, the NF consumer (202) may be configured to monitor, detect, or receive triggers associated with application-level session events initiated by the UE (104), such as session initiation, session modification, session termination, and so forth. For example, when the user (106) launches an application or accesses a webbased service through a browser on the UE (104), the NF consumer (202) detects the service session and initiates the corresponding request. The NF consumer (202) is configured to transmit the request to the NF (204) via a service-based interface. The service-based interface may include, but not be limited to, N5 interface, Nbsf interface, and so forth. The NF (204) may be, but is not limited to, a network repository function (NRF), a network exposure function (NEF), and so forth. In a preferred embodiment, the NF (204) is a binding support function (BSF).

[0092] The NF (204) acts as an intermediary between the NF consumer (202) and the PCF (206). In one embodiment, the NF (204) is configured for identifying at least one PCF (206) based on a unique subscriber identifier included in the request received from the NF consumer (202). The NF (204) is configured to facilitate the routing of requests by obtaining PCF-related information from adatabase (310). In scenarios where such PCF information is unavailable due to, for example, a failure in a database connectivity or absence of pre-stored data, the NF (204) may invoke a fallback mechanism that applies a modulo operation, to identify the PCF (206) for handling the corresponding request and forwards the request accordingly to the identified PCF (206). Through this intermediary functionality, the NF (204) ensures that the requests are accurately and efficiently routed to the PCF (206), enabling policy enforcement, QoS handling, and service authorization in alignment with the 5G core architecture.

[0093] In an embodiment, the PCF (206) is configured to make dynamic policy decisions and manage network resources in accordance with subscription information, service requirements, and current network conditions. The PCF (206) functions as a centralized control entity within the network (108) that enforces policy rules related to QoS charging, access control, and traffic routing. Upon receiving the requests from the NF (204), the PCF (206) processes the requests to determine applicable policy control actions required to support the associated service session.

[0094] In an aspect, the PCF (206) analyses each incoming request to derive appropriate policy rules by referencing user-specific subscription profiles, network slice information, service type descriptors, and pre-defined operator policies. Based on this analysis, the PCF (206) formulates and enforces decisions regarding session admission, QoS treatment, and traffic handling.

[0095] In another aspect, the PCF (206) is configured to optimize overall network performance by dynamically managing QoS parameters and allocating the network resources in real time. For example, in the context of a video streaming application, the PCF (206) may prioritize bandwidth allocation to maintain smooth video playback. In contrast, for latency-sensitive applications such as online gaming or VoIP communication, the PCF (206) may enforce low-latency policies to ensure minimal delay and improve user experience. By tailoring the policydecisions to application requirements and subscriber entitlements, the PCF (206) enhances service quality and ensures efficient utilization of network infrastructure.

[0096] Although FIG. 2 illustrates a single instance of the PCF (206), alternative embodiments of the present disclosure may include a plurality of PCF instances such as PCF1 (206A), PCF2 (206B), PCF3 (206C), PCF4 (206D) and PCF5 (206E).

[0097] FIG. 3 illustrates an exemplary block diagram (300) of the system (102) for managing the requests in the network (108), in accordance with embodiments of the present disclosure. FIG. 3 is explained in conjunction with FIG. 1 and FIG. 2.

[0098] Referring to FIG. 3, in an embodiment, the system (102) may include one or more processor(s) (302). The one or more processor(s) (302) 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 one or more processor(s) (302) may be configured to fetch and execute computer-readable instructions stored in a memory (304) of the system (102). The memory (304) 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 (304) may comprise any non-transitory storage device, including, for example, volatile memory such as random-access memory (RAM), or non-volatile memory such as erasable programmable read-only memory (EPROM), flash memory, and the like.

[0099] In an embodiment, the memory (304) may be operatively associated with the NF (204), and configured to store at least one mapping table used in a deterministic routing logic. The memory (304) is configured to store a PCF mapping table, which includes a plurality of modulo result values and corresponding PCF details. Each entry in the PCF mapping table maps a moduloresult value to one or more attributes of a PCF instance, including, but not limited to, an instance identifier, a network address, supported service types, associated network slice information, and so forth. The PCF mapping table facilitates deterministic routing of the requests based on the outcome of the modulo operation performed on a subscriber-specific identifier.

[0100] Further, in an embodiment, the memory (304) is configured to store a service communication proxy (SCP) mapping table which includes a plurality of entries, each corresponding to the modulo result value, with each entry mapping to an SCP instance. In an embodiment, SCP details may include, but are not limited to, the IP address of the SCP, an instance ID, a load-balancing group, or routing parameters. This SCP mapping table is used when routing the requests through the SCP to ensure that the request follows a correct deterministic path based on the outcome of the modulo operation.

[0101] In an embodiment, the SCP mapping table stored in the memory (304) is maintained in synchronization with the PCF mapping table to ensure routing consistency. In other words, the mapping tables pre-configured at the NF (204) and the SCP are logically and structurally identical. That is, for a modulo result value derived from a subscriber identifier, both the NF (204) and SCP independently resolve to the same PCF instance, thereby preserving statelessness and ensuring correctness in the policy enforcement flow.

[0102] In certain embodiments, the memory (304) may be part of an NF node or may reside in an external configuration repository accessible via service-based interfaces. The memory (304) may support runtime configurability, enabling operators to update, modify, or synchronize the mapping tables without requiring a system restart or service disruption. In an embodiment, configuration synchronization mechanisms may be implemented to ensure that updates to the PCF mapping table are mirrored in the SCP mapping table to maintain alignment across nodes.

[0103] The memory (304) is also configured to store one or more predefined criteria used to determine whether the fallback mechanism, such as the modulo operation, should be triggered. The predefined criteria may include, but not limited to, an unavailability of one or more details of the at least one PCF (206) in the database (310), and an active state of a modulo configuration parameter in the memory (304). When the modulo configuration parameter is in the active state, the modulo operation is triggered irrespective of availability of the one or more details of the at least one PCF (206) in the database (310).

[0104] In an embodiment, the system (102) may include an interface(s) (306). The interface(s) (306) 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) (306) may facilitate communication through the system (102). The interface(s) (306) may also provide a communication pathway for one or more components of the system (102). Examples of such components include, but are not limited to, a processing engine(s) (308) and the database (310).

[0105] In an embodiment, the processing engine(s) (308) 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) (308). 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) (308) may be processor-executable instructions stored on a non-transitory machine -readable storage medium, and the hardware for the processing engine(s) (308) 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 engine(s) (308). In such examples, the system (102) 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 butaccessible to the system (102) and the processing resource. In other examples, the processing engine(s) (308) may be implemented by electronic circuitry.

[0106] In an embodiment, database (310) may include data that may be either stored or generated as a result of functionalities implemented by any of the components of the processor (302) or the processing engine (308). In an embodiment, the database (310) may be separate from the system (102).

[0107] In an embodiment, the database (310) may store data that may be generated as a result of functionalities implemented by any of the components of the processor (302) or the processing engine (308). In an embodiment, the database (310) may be indicative of including, but not limited to, a relational database, a distributed database, a cloud-based database, or the like. In an exemplary embodiment, the processing engine (308) may include one or more units having functions that may include, but are not limited to, testing, storage, and peripheral functions, such as a wireless communication unit for remote operation and the like. In an embodiment, the database (310) may be a PCF database configured to store the one or more details of the at least one PCF (206) including, but not limited to, a PCF instance identifier, an IP address, a fully qualified domain name (FQDN), load information, availability status, and so forth.

[0108] In an embodiment, the processing engine (308) may be integrated within the NF (204), and configured to manage the requests in the network (108). In another embodiment, the processing engine (308) may be implemented as a separate physical or logical component that communicates with the NF (204) and assists the NF (204) in managing the requests in the network (108). In yet another embodiment, the processing engine (308) may include the NF (204) configured to receive the requests from the NF consumer (202) and to manage processing of the requests within the network (108).

[0109] In an embodiment, the processing engine (308) may include a plurality of functional modules that enable the NF (204) to perform one or more operations for managing the requests. These modules may include, but are not limited to, arequest receiving module (312), an identifier extraction module (314), a criteria evaluation module (316), a modulo computation module (318) and a request routing module (320).

[0110] The request receiving module (312) is configured to receive the at least one request from the NF consumer (202) via the service-based interface. In an embodiment, the service-based interface may include an HTTP / 2-based application programming interface (API) in accordance with 3GPP specifications, such as an Nbsf interface or an Rx interface. The received request may include, for example, an initial AAR or the management discovery request, and may include session- related information, subscriber identifiers (e.g., SUPI or IMSI), media descriptors, the QoS requirements, and so forth. The request receiving module (312) is configured to transmit the at least one received request to the identifier extraction module (314).

[0111] The identifier extraction module (314) is communicatively coupled to the request receiving module (312). The identifier extraction module (314) is configured to receive the at least one request from the request receiving module (312). The identifier extraction module (314) is configured to extract at least one unique identifier, corresponding to at least one subscriber, from the at least one received request. The unique identifier includes, but is not limited to, the SUPI, the IMSI, or any other identifier uniquely associated with the subscriber or user session. In an exemplary embodiment, the identifier extraction module (314) may be configured to analyze a structure of the received request, such as the AAR or the management discovery request, by parsing a request header or payload to identify and isolate a field containing the unique identifier. For example, in the HTTPSbased request, the unique identifier may be located within a JavaScript object notation (JSON) or an extensible markup language (XML) element, or within a protocol-defined attribute-value pair (A VP) in the case of a Diameter message.

[0112] In an embodiment, the identifier extraction module (314) may be configured to utilize predefined schemas, interface specifications (e.g., 3GPP-defined Rx or Nbsf interfaces), or data templates to locate and extract the unique identifier. In some embodiments, the extracted unique identifier may be validated for format compliance (e.g., ensuring the SUPI / IMSI conforms to expected digit length or encoding format) and may be temporarily cached or passed to subsequent modules for further computation, such as modulo-based PCF selection.

[0113] In an embodiment, the identifier extraction module (314) may be configured to extract only a portion of the at least one unique identifier (e.g., last n digits of the SUPI or IM SI), when required for downstream computations such as modulo operations. The identifier extraction module (314) is configured to transmit the extracted unique identifier or the portion of the extracted unique identifier to the criteria evaluation module (316).

[0114] The criteria evaluation module (316) is communicatively coupled to the identifier extraction module (314) to receive the extracted unique identifier or the portion of the extracted unique identifier from the identifier extraction module (314). The criteria evaluation module (316) is configured to determine at least one predefined criterion stored in the memory (304) associated with the NF (204). In an embodiment, the criteria evaluation module (316) is configured to determine whether any of the predefined criteria are satisfied to trigger the fallback mechanism for identifying the PCF (206). The fallback mechanism may be invoked when a default PCF selection process, involving a database lookup, either fails or is explicitly bypassed. The satisfaction of either condition is sufficient to trigger the modulo operation for identifying the PCF (206).

[0115] For example, the unavailability of the details of the at least one PCF (206) may result from various failure scenarios, such as but not limited to, (a) failure to establish a connection to the database (310) (e.g., due to network outage, server downtime, or timeout), (b) retrieval of incomplete, missing or corrupted database records, (c) failure to locate a matching entry for the extracted unique identifier (e.g., resulting in a 404 or null response), or (d) receipt of records with invalid format or missing parameters required for policy selection. The criteria evaluationmodule (316) may be configured to perform a database query using the extracted unique identifier and receive a result code (e.g., null, error code, or timeout). Based on the result code, the criteria evaluation module (316) may set an internal flag indicating data unavailability, thereby satisfying the predefined criterion.

[0116] In another scenario, the fallback mechanism may be triggered based on the status of the modulo configuration parameter (i.e., a runtime configurable setting) stored in the memory (304) or in an external configuration repository accessible to the NF (204). The modulo configuration parameter may be represented in various forms, including, but not limited to, a binary flag, a Boolean variable, a key-value pair, a bitmask indicator, and so forth. The modulo configuration parameter indicates whether the fallback mechanism involving the modulo operation should be enforced, even when the PCF information is available in the database (310).

[0117] When the modulo configuration parameter is set to an active state (e.g., a Boolean true, a flag set to 1, a key set to “ENABLED”), the NF (204) bypasses the default PCF selection process and invokes the modulo operation on the extracted unique identifier (e.g., SUPI or IMSI). This ensures stateless and deterministic routing of the request to the appropriate instance of the PCF (206). The active configuration may be applied in various scenarios, such as during planned maintenance of the PCF database, testing of fallback behavior, or in minimalist deployments that avoid dependency on external statefill systems.

[0118] In operation, the criteria evaluation module (316) may be configured to access the memory (304) or external configuration repository either periodically, at system startup, or on-demand, to determine a current value of the modulo configuration parameter. If the value of the modulo configuration parameter reflects the active state, the criteria evaluation module (316) considers the condition satisfied, and is configured to generate and transmit a corresponding control signal, status flag, or activation trigger to the modulo computation module (318). This control signal indicates that the modulo operation needs to be executed for selectingthe appropriate instance of the PCF (206), even if the PCF-related data is accessible from the database (310).

[0119] In another embodiment, if none of the predefined criteria are satisfied, such as when the PCF data is available in the database (310) and the modulo configuration parameter is inactive, the criteria evaluation module (316) is configured to initiate a direct retrieval of the one or more details of the at least one PCF (206) from the database (310). This retrieval process includes performing the database query using the extracted unique identifier (e.g., SUPI or IMSI) to locate a matching PCF record. If the database query returns a valid response including a complete set of PCF details such as the instance identifier, the network address, and supported service attributes, the NF (204) proceeds to route the request to the identified PCF (206) based on the retrieved information.

[0120] The modulo computation module (318) is communicatively coupled to the criteria evaluation module (316), to receive the control signal from the criteria evaluation module (316). Based on the received control signal, the modulo computation module (318) is configured to trigger the modulo operation on the extracted unique identifier. The modulo operation includes processing the portion of the extracted unique identifier to generate an index value within a range defined by a number of available PCF instances. As used herein, the term “index value” refers to a numerical result generated by applying the modulo operation to the portion of the unique identifier. The index value represents a bounded numerical position within a predefined range, where an upper limit of the range is defined by a total number of available PCF instances. This index value serves as a selection key for identifying a specific entry in the pre-configured mapping table that associates each index value with the corresponding PCF instance. The use of the index value ensures deterministic and efficient routing of the requests to appropriate PCFs.

[0121] In an embodiment, the modulo operation is performed using the last n digits of the extracted unique identifier as a numerator, and the number of availablePCF instances defined in the mapping table as a denominator. This results in a remainder value representing a modulo result value orthe index value. For example, if the last n digits of the SUPI / IMSI equal 102, and the system (102) includes 10 PCF instances, the result of the modulo operation 102 % 10 yields the index value of 2, which is used to access the corresponding PCF entry in the mapping table. In an embodiment, the modulo result values may range from 0 to (x-1), where x denotes the number of PCF instances registered in the system (102).

[0122] As an illustration, consider a scenario where there are five registered PCF instances. The modulo result values may range from 0 to 4. The mapping table may be pre-configured as follows:

[0123] In this configuration, if the request contains the SUPI / IMSI with the extracted portion 987654, then 987654 % 5 = 4. Accordingly, the modulo computation module (318) selects PCF E from the mapping table. This enables deterministic routing of the requests based on the extracted unique identifier, ensuring even distribution and eliminating reliance on real-time database queries during fallback scenarios.

[0124] In one implementation, the NF (204) may be configured to extract the unique identifier from the received request. The extraction of the unique identifier may be performed based on the message type. For example, the unique identifiermay be retrieved from query parameters included in the management discovery request or from a subscription-ID attribute value pair (A VP) in the AAR, where a subscription-ID-type is set to IMSI. Once extracted, the unique identifier or a portion thereof is processed as input to the modulo operation. The output of the modulo operation, i.e., the modulo result value or index value, is used to identify the corresponding PCF instance from the pre-configured mapping table. This deterministic selection method enables the NF (204) to identify and forward the request to the appropriate PCF (206) without querying external databases. The modulo computation module (318) is configured to transmit the information associated with the identified PCF (206) to the request routing module (320).

[0125] In an embodiment, the modulo operation may be further employed to deterministically route the requests between an initiating NF (204) (e.g., BSF) and the target PCF (206) via an intermediate SCP. The SCP serves as a proxy node that facilitates service-based interface (SBI) communication between the NF consumer (202) and the producer NF (i.e., PCF (206)). When the SCP is involved in a routing path, it is essential that the SCP independently derives the same routing decision as the NF (204) (e.g., BSF), to ensure consistency and stateless operation.

[0126] To maintain synchronization in the modulo-based selection technique across distributed components, a modulo mapping configuration stored at the SCP must be identical to a mapping logic implemented at the NF (204). This ensures that, for a subscriber-specific identifier (e.g., SUPI or IMSI), both the NF (204) and SCP compute the same modulo result value and resolve it to the same PCF instance. The mapping tables at both the NF (204) and the SCP define an association between the modulo result values (e.g., ranging from 0 to x-1, where x denotes the number of PCF instances) and their respective PCF instance details.

[0127] Any inconsistency or mismatch between the mapping tables at the NF (204) and SCP may lead to divergent routing outcomes, causing incorrect PCF selection, policy misalignment, or session delivery failures. Accordingly, as a prerequisite for successful deployment of the modulo-based fallback mechanism, itis imperative that network operators pre-configure the mapping tables at both the NF (204) and the SCP to be logically and functionally identical. This alignment ensures deterministic, seamless, and stateless routing of the requests even during database failures or fallback scenarios, thereby enhancing overall system resilience and operational reliability.

[0128] The request routing module (320) is communicatively coupled to the modulo computation module (318). The request routing module (320) is configured to perform at least one operation based on the at least one identified PCF (206). The at least one operation includes a routing of the received request to the identified PCF (206) and generating a response to the received request based on the information associated with the identified PCF (206).

[0129] In an embodiment, the request routing module (320) is configured to determine the appropriate PCF instance for processing the received request, such as the initial AAR or the management discovery request. For AAR-type requests, the request routing module (320) utilizes the PCF information identified through the database lookup or modulo-based selection technique to directly forward the request to the identified PCF (206). For the management discovery requests, the request routing module (320) is configured to generate a discovery response that includes details of the identified PCF (206). In such an embodiment, the request routing module (320) may be configured to extract parameters, such as, but not limited to, internet protocol (IP) address, media access control (MAC) address, data network name (DNN), slice / service type, and so forth from the received request itself, while additional PCF-specific information may be retrieved from the PCF mapping table associated with the NF (204).

[0130] In another embodiment, once the initial AAR request has been processed and a session context has been established, the NF (204) is configured to maintain session-specific information in a local cache or session store. Accordingly, any subsequent diameter requests that reference a same session-ID as the initial AAR are not subjected to the modulo-based fallback logic or PCF selectionalgorithms again. Instead, the cached session context is used to consistently route all subsequent messages to the originally selected PCF instance. This approach minimizes computational overhead, ensures session continuity, and enhances processing efficiency for ongoing sessions.

[0131] For example, when a UE ‘X’ initiates the video streaming session via the streaming application, the corresponding AF may transmit the AAR to the BSF to request authorization and policy control. The BSF, through the request routing module (320), identifies the appropriate PCF instance (e.g., PCF-3 (206C)) using either the database lookup or the modulo-based selection technique. The AAR is then forwarded to the PCF-3 (206C), which applies relevant QoS, charging, and policy rules to the session.

[0132] Prior to initiating the AAR, the AF may send the management discovery request to determine the appropriate PCF instance to use. The BSF processes the management discovery request, applies the modulo operation to derive the modulo result value (e.g., value 3), and retrieves the corresponding PCF details (e.g., PCF- 3 (206C) with IP address 10.0.0.2, supporting slice SI and DNN “internet”) from the mapping table. These details are compiled into the discovery response and returned to the AF, enabling it to direct the AAR to the correct PCF instance.

[0133] Once the PCF-3 (206C) has successfully processed the initial AAR and established the session context for the user session (e.g., Session-Id = “session- 12345”), the BSF caches the associated PCF selection and relevant session metadata. Later, when the AF or another NF sends subsequent diameter messages associated with “session-12345,” the BSF bypasses the modulo operation and directly routes the messages to the PCF-3 (206C) using the cached data. This ensures consistent handling of session requests and avoids redundant PCF selection logic.

[0134] FIG. 4 illustrates an exemplary flowchart of a process (400) for performing PCF selection and routing of the AAR at the NF (204), in accordance with embodiments of the present disclosure. FIG. 4, with reference to FIG. 1, FIG.2 and FIG. 3, illustrates the process (400) for performing the PCF selection and routing of the AAR at the NF (204) by using the processing engine (308) of the system (102).

[0135] At step (402), the process (400) includes receiving, at the NF (204), the request from the NF consumer (202). The received request may include userspecific information required for initiating or managing network access procedures. In an embodiment, the request may be of any type, such as the AAR and the management discovery request.

[0136] In one embodiment, the AAR corresponds to an initial attempt by the user (106) to establish the service session within the network (108). The AAR may include session initiation parameters and is used to request authentication and authorization from the core network (108). This includes verifying that the user (106) possesses valid credentials and is authorized to access the requested services, such as media streaming, VoIP, or other application-layer services. In another embodiment, the management discovery request is configured to retrieve information pertaining to one or more available network functions or service endpoints (e.g., PCF instances). The management discovery request may be used to facilitate initial service setup by assisting the UE (104) or the NF consumer (202) in identifying accessible PCFs supported service types, and associated configuration parameters necessary for communication and session establishment. This enables dynamic discovery of relevant core network resources, ensuring optimal connectivity and service delivery. Upon receiving the request, the NF (204), which may be implemented as the BSF, is configured to process the request in accordance with the request type and user-specific context, thereby enabling seamless and policy-compliant network access and interaction with required services.

[0137] At step (404), the process (400) includes, upon receiving the request from the NF consumer (202), determining, at the NF (204), whether the information associated with at least one PCF (206) responsible for handling the received requestis available. In an embodiment, the NF (204) may attempt to retrieve such information from the database (310) that stores pre-associated PCF-related details corresponding to the requesting user (106).

[0138] For example, when the user (106) initiates the service session, such as the video streaming session via the streaming application operating as the NF consumer (202), the NF consumer (202) may transmit the initial AAR to the NF (204). In response, the NF (204) may query the database (310) using one or more parameters included in the request, such as the unique identifier (e.g., SUPI or IMSI), to retrieve the corresponding PCF details.

[0139] If the database query is successful and the PCF-related information is available, the process (400) proceeds to step (406), where the request is routed to the identified PCF (206). If the one or more details of the corresponding PCF (206) are not available in the database (310), then the process (400) proceeds to step (408).

[0140] At step (406), the process (400) includes sending the received request from the NF consumer (202) directly to at least one identified PCF (206). For example, consider a scenario in which the user (106) launches an online gaming application (i.e., AF) on the UE (104) and initiates an online gaming session. The NF consumer (202) may generate and transmit the AAR to the NF (204). The NF (204), having previously accessed and cached the details of the at least one PCF (206) from the database (310), forwards this request to the identified PCF (206). In an embodiment, the PCF instance may be one of a plurality of registered PCFs, such as PCF1 (206A), PCF2 (206B), PCF3 (206C), PCF4 (206D), or PCF5 (206E) based on the result of the database lookup or a previously performed modulo operation. For instance, if the previously obtained result indicates the PCF3 (206C), the request is routed directly to the PCF3 (206C) for further processing. Once the request reaches the identified PCF (206), the PCF (206) processes the request by enforcing the relevant policies and managing the required quality of service (QoS) parameters. In an embodiment, the PCF (206) may generate a policy decision response and transmit the response back through the NF (204) to the NF consumer(202), confirming that the necessary network resources and QoS settings have been provisioned to support the ongoing session.

[0141] At step (408), the process (400) includes executing the modulo operation based on a flag condition, in response to determining that the details of the at least one PCF (206) are unavailable in the database (310). In a preferred embodiment, the modulo operation is triggered when the modulo configuration parameter is set to the active state (e.g., a Boolean true, a flag set to 1, a key set to “ENABLED”). The flag-based condition ensures that fallback mechanism is only applied when explicitly permitted by system configuration.

[0142] In an embodiment, the modulo operation utilizes the unique identifier included in the request received from the NF consumer (202). For instance, when the user (106) initiates the service session (e.g., video streaming) and the NF consumer (202) transmits an initial request to the NF (204), the NF (204) extracts the last n digits of the unique identifier, where n is a predefined configuration parameter, and uses the extracted digits as the numerator in the modulo operation. The denominator in the modulo operation corresponds to the number of PCF instances pre-defined in the mapping table stored within the NF (204). The modulo operation thus yields a result in the range of 0 to (x-I), which is referred to as the modulo result value or index value. The modulo result value is used as a lookup index against the mapping table. Each entry in the mapping table associates a specific modulo result value with the corresponding PCF instance details. For example, if the modulo result is 3, the mapping table may indicate that the request should be routed to a PCF instance labeled as PCF-3 (206C).

[0143] Based on the PCF instance identified using the modulo operation, the NF (204) is configured to perform at least one operation. In an embodiment, this includes routing the received request to the identified PCF (e.g., PCF3 (206C)), or generating and transmitting the discovery response to the NF consumer (202), the response containing the PCF-related information derived from the mapping table.Following the modulo-based PCF selection and identification of the appropriate PCF instance at step (408), the process (400) proceeds to step (406).

[0144] FIG. 5 illustrates an exemplary flow diagram of a method (500) for managing the request in the network (108), in accordance with embodiments of the present disclosure. FIG. 5, with reference to FIG. 1, FIG. 2 and FIG. 3, illustrates the method (500) for managing the request in the network (108) by using the processing engine (308) of the system (102).

[0145] At step (502), the method (500) includes receiving, by the NF (204), the at least one request from the NF consumer (202). The at least one request is one of the AAR and the management discovery request. In a preferred embodiment, the NF (204) is the BSF.

[0146] At step (504), the method (500) includes extracting, by the NF (204), the at least one unique identifier, corresponding to the at least one subscriber, from the at least one received request. The at least one unique identifier includes the SUPI, the IMSI, and so forth.

[0147] At step (506), the method (500) includes determining, by the NF (204), the at least one predefined criterion stored in the memory (304) associated with the NF (204). The at least one predefined criterion includes at least one of: the unavailability of the details of the at least one PCF (206) in the database (310); and the active state of the modulo configuration parameter in the memory (304). The active state triggers the modulo operation irrespective of the availability of the details of at least one PCF (206) in the database (310). The memory (304) includes at least one mapping table pre-configured with the modulo result values representing the outcomes of the modulo operation, and the corresponding details of the at least one PCF (206) associated with each modulo result value of the modulo result values. The mapping table pre-configured at the NF (204) and the SCP are identical.

[0148] At step (508), the method (500) includes applying, by the NF (204), the modulo operation on the at least one extracted unique identifier to identify the atleast one policy control function (PCF) (206). The modulo operation includes processing the portion of the at least one extracted unique identifier to generate the index value within the range defined by a number of available PCF instances.

[0149] At step (510), the method (500) includes performing, by the NF (204), the at least one operation based on the at least one identified PCF (206). The at least one operation includes routing of the at least one received request to the at least one identified PCF (206), and generating the response to the at least one received request based on information associated with the at least one identified PCF (206).

[0150] FIG. 6 illustrates an exemplary computer system (600) in which, or with which, the system (102) and the method (500) 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 the communication ports (660). The processor (670) may include various modules associated with embodiments of the present disclosure.

[0151] In an embodiment, the external storage device (610) may be any device that is commonly known in the art, such as, but not limited to, a memory card, a memory stick, a solid-state drive, a hard disk drive (HDD), and so forth.

[0152] In an embodiment, the bus (620) may be communicatively coupled with the processor(s) (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, a small computer system interface (SCSI), a 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).

[0153] In an embodiment, the main memory (630) may be a random-access memory (RAM), or any other dynamic storage device commonly known in the art.The 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).

[0154] In an embodiment, the mass storage device (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, a parallel advanced technology attachment (PATA) or a 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).

[0155] Further, 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 the network (108), such a local area network (LAN), wide area network (WAN), or any network to which the computer system (600) connects.

[0156] Optionally, operator and administrative interfaces, e.g., a display, a keyboard, a joystick, and a cursor control device, may also be coupled to the bus (620) to support a 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). Components described 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.

[0157] The exemplary computer system (600) is configured to execute a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause theone or more processors to perform a method (500) for managing a request in a network (108). The method (500) includes receiving, by a network function (NF) (204), at least one request from an NF consumer (202). The method (500) further includes extracting, by the NF (204), at least one unique identifier, corresponding to at least one subscriber, from the at least one received request. The method (500) further includes determining, by the NF (204), at least one predefined criterion stored in a memory (304) associated with the NF (204). The method (500) further includes upon meeting the at least one predefined criterion, applying, by the NF (204), a modulo operation on the at least one extracted unique identifier to identify at least one policy control function (PCF) (206). The method (500) further includes performing, by the NF (204), at least one operation based on the at least one identified PCF (206).

[0158] In an exemplary embodiment, a user equipment (UE) (104) communicatively coupled with a network (108) is disclosed. The coupling includes steps of receiving, by the network (108), a connection request from the UE (104), sending, by the network (108), an acknowledgment of the connection request to the UE (104) and transmitting a plurality of signals in response to the connection request. The UE (104) is connected with a system (102) configured to manage a request in the network (108). The system (102) includes a network function (NF) (204) configured to receive at least one request from an NF consumer (202). The NF (204) is further configured to extract at least one unique identifier, corresponding to at least one subscriber, from the at least one received request. The NF (204) is further configured to determine at least one predefined criterion stored in a memory (304) associated with the NF (204). The NF (204) is further configured to upon meeting the at least one predefined criterion, apply a modulo operation on the at least one extracted unique identifier to identify at least one policy control function (PCF) (206). The NF (204) is further configured to perform at least one operation based on the at least one identified PCF (206).

[0159] The present disclosure provides a technical advancement in a field of 5G network request management by addressing limitations of existing solutionsrelated to PCF information retrieval failures. This advancement is achieved through a solution of a modulo-based approach at BSF, which allows a system to efficiently route requests even when PCF details cannot be fetched from a database, ensuring higher service availability and resilience. The inventive aspects of using SUPI / IMSI for modulo calculations, combined with configurable logic to force a use of modulo routing when needed, offer significant improvements in network performance, scalability, and fault tolerance. By implementing this invention, the disclosed solution enhances the reliability of network operations, reduces request latency, and optimizes load distribution across multiple PCF instances, resulting in uninterrupted service delivery and an overall improved user experience.

[0160] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.TECHNICAL ADVANTAGES OF THE PRESENT DISCLOSURE

[0161] As is evident from above, the present disclosure described herein above has several technical advantages including:• ensuring continuous service availability at BSF by enabling fallback request handling using a modulo-based selection logic, thereby minimizing disruptions during PCF data unavailability. maintaining Quality of Service (QoS) by allowing the BSF to handle Rx or HTTP / 2 requests efficiently, even in the absence of direct access to PCF information stored in a database.• reducing the risk of network outages and enhancing the fault tolerance of 5G core infrastructure by introducing a deterministic fallback mechanism based on subscriber identifiers (e.g., SUPI / IMSI).• supporting uninterrupted service delivery by enabling the BSF to identify and forward requests to an appropriate PCF instance using a pre -configured modulo mapping table, ensuring timely policy and resource decisions.• facilitating modular implementation through the use of configurable parameters (e.g., modulo flag and mapping tables), allowing dynamic control over fallback behavior without service interruption.• providing a deterministic PCF selection approach that integrates seamlessly with Service Communication Proxy (SCP) logic, assuming synchronized modulo mapping configurations between BSF and SCP. improving system robustness and resilience against backend database failures or temporary unavailability of network function (NF) profiles.

Claims

CLAIMS1. A method (500) for managing a request in a network ( 108), the method (500) comprising steps of: receiving, by a network function (NF) (204), at least one request from an NF consumer (202); extracting, by the NF (204), at least one unique identifier, corresponding to at least one subscriber, from the at least one received request; determining, by the NF (204), at least one predefined criterion stored in a memory (304) associated with the NF (204); upon meeting the at least one predefined criterion, applying, by the NF (204), a modulo operation on the at least one extracted unique identifier to identify at least one policy control function (PCF) (206); and performing, by the NF (204), at least one operation based on the at least one identified PCF (206).

2. The method (500) as claimed in claim 1, wherein the at least one request is one of an initial authorization and authentication request (AAR), and a management discovery request.

3. The method (500) as claimed in claim 1, wherein the NF (204) is a binding support function (BSF).

4. The method (500) as claimed in claim 1, wherein the at least one unique identifier comprises a subscription permanent identifier (SUPI), an international mobile subscriber identity (IMSI), or a combination thereof.

5. The method (500) as claimed in claim 1 , wherein the at least one predefined criterion comprises at least one of: an unavailability of one or more details of the at least one PCF (206) in a database (310); andan active state of a modulo configuration parameter in the memory (304), wherein the active state triggers the modulo operation irrespective of availability of the one or more details of the at least one PCF (206) in the database (310).

6. The method (500) as claimed in claim 5, wherein the memory (304) comprises at least one mapping table pre-configured with a plurality of modulo result values representing one or more outcomes of the modulo operation, and one or more corresponding details of the at least one PCF (206) associated with each modulo result value of the plurality of modulo result values.

7. The method (500) as claimed in claim 6, wherein the at least one mapping table pre-configured at the NF (204) and a service communication proxy (SCP) are identical.

8. The method (500) as claimed in claim 1, wherein the modulo operation comprises processing a portion of the at least one extracted unique identifier to generate an index value within a range defined by a number of available PCF instances.

9. The method (500) as claimed in claim 1, wherein the at least one operation comprises a routing of the at least one received request to the at least one identified PCF (206), and generating a response to the at least one received request based on information associated with the at least one identified PCF (206).

10. A system (102) for managing a request in a network (108), wherein the system (102) comprising: a network function (NF) (204) configured to: receive at least one request from an NF consumer (202);extract at least one unique identifier, corresponding to at least one subscriber, from the at least one received request; determine at least one predefined criterion stored in a memory (304) associated with the NF (204); upon meeting the at least one predefined criterion, apply a modulo operation on the at least one extracted unique identifier to identify at least one policy control function (PCF) (206); and perform at least one operation based on the at least one identified PCF (206).

11. The system (102) as claimed in claim 10, wherein the at least one request is one of an initial authorization and authentication request (AAR), and a management discovery request.

12. The system (102) as claimed in claim 10, wherein the NF (204) is a binding support function (BSF).

13. The system (102) as claimed in claim 10, wherein the at least one unique identifier comprises a subscription permanent identifier (SUPI), an international mobile subscriber identity (IMSI), or a combination thereof.

14. The system (102) as claimed in claim 10, wherein the at least one predefined criterion comprises at least one of: an unavailability of one or more details of the at least one PCF (206) in a database (310); and an active state of a modulo configuration parameter in the memory (304), wherein the active state triggers the modulo operation irrespective of availability of the one or more details of the at least one PCF (206) in the database (310).

15. The system (102) as claimed in claim 14, wherein the memory (304) comprises at least one mapping table pre-configured with a plurality of modulo result values representing one or more outcomes of the modulo operation, and one or more corresponding details of the at least one PCF (206) associated with each modulo result value of the plurality of modulo result values.

16. The system (102) as claimed in claim 15, wherein the at least one mapping table pre-configured at the NF (204) and a service communication proxy (SCP) are identical.

17. The system (102) as claimed in claim 10, wherein the modulo operation comprises processing a portion of the at least one extracted unique identifier to generate an index value within a range defined by a number of available PCF instances.

18. The system (102) as claimed in claim 10, wherein the at least one operation comprises a routing of the at least one received request to the at least one identified PCF (206), and generating a response to the at least one received request based on information associated with the at least one identified PCF (206).

19. A user equipment (UE) (104) communicatively coupled with a network (108), the coupling comprises steps of: receiving, by the network (108), a connection request from the UE (104); sending, by the network (108), an acknowledgment of the connection request to the UE (104); and transmitting a plurality of signals in response to the connection request, wherein the UE (104) is connected with a system (102) configured to manage a request in the network (108), as claimed in claim 10.

20. 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 execute a method (500) for managing a request in a network (108), the method (500) comprising steps of: receiving, by a network function (NF) (204), at least one request from an NF consumer (202); extracting, by the NF (204), at least one unique identifier, corresponding to at least one subscriber, from the at least one received request; determining, by the NF (204), at least one predefined criterion stored in a memory (304) associated with the NF (204); upon meeting the at least one predefined criterion, applying, by the NF (204), a modulo operation on the at least one extracted unique identifier to identify at least one policy control function (PCF) (206); and performing, by the NF (204), at least one operation based on the at least one identified PCF (206)

Images