Method and system for managing data fetching and subscribe operations in a network

Abstract

The disclosure relates to a method and system for managing a data fetching operation and a subscribe operation in a network (106) are disclosed. The method (500) comprises receiving, by a network function (402), a request to obtain subscription data and to subscribe for the subscription data associated with a user equipment (UE) (104). Upon receiving the request, a service operation is initiated by the NF (402) towards a Unified Data Management (UDM) implemented in the system (108), wherein the service operation comprises either a combination of Get and Subscribe service operation or a modified Get service operation. A processing engine (208) of the system (108) identifies the service type, and a corresponding initiated service operation is triggered towards a Unified Data Repository (UDR). The UDR performs the operation, stores data in a database (210), and returns the subscription data and a subscription identifier.

Description

METHOD AND SYSTEM FOR MANAGING DATA FETCHING AND SUBSCRIBE OPERATIONS IN A NETWORKRESERVATION 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.TECHNICAL FIELD

[0002] The present disclosure relates to the field of telecommunications. The present disclosure relates to a system and a method for managing data fetching and subscribe operations in a network.DEFINITIONS

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

[0004] Network Functions (NFs) are modular components in a network that handle specific tasks such as data processing, service management, and user interactions.

[0005] Unified Data Management (UDM) is a centralized system that manages and stores subscriber data and network-related information.

[0006] Application Management Function (AMF) is a network function configured for managing user session registration, authentication, and mobility.

[0007] Session Management Function (SMF) is a network function that handles the setup, maintenance, and termination of user data sessions.

[0008] Short Message Service Function (SMSF) is a network function that manages the sending, receiving, and processing of Short Message Service (SMS) messages.

[0009] Gateway Mobile Location Center (GMLC) is a network function that provides location-based services and manages the location information of mobile devices.

[0010] Network Exposure Function (NEF) is a network function that exposes network capabilities to external applications and services for enhanced integration.

[0011] Data Distribution Network Management Function (DDNMF) is a network function configured for efficiently distributing data across different network segments.

[0012] Network Data Analytics Function (NWDAF): is a network function that analyzes network data to provide insights into performance and user behavior.

[0013] Data Communication Control Function (DCCF) is a network function that manages the coordination and control of data communication across the network.

[0014] Trusted Application Function (Trusted AF) is a network function that ensures the security and trustworthiness of applications interacting with the network.

[0015] The “Get” Service operation is used in network management and communications systems to request and retrieve specific information or data from a network function (NF).

[0016] The term “SdmSubscription” refers to an Information Element (IE) that encapsulates subscription-related attributes required by a consumer network function (NF) to register interest in specific subscription data maintained by a Unified Data Repository (UDR) via a Unified Data Management (UDM) entity. The SdmSubscription IE comprises a plurality of sub-information Elements (sub-IEs) that define the scope, context, delivery preferences, and identifiers associated with the subscription.

[0017] The term “CallbackReference” refers to a sub-IE that specifies the Uniform Resource Identifier (URI) or network endpoint at which the consumer NF desires to receive notifications related to changes in the subscribed data.

[0018] The term “SingleNssai” refers to a sub-IE representing a Single Network Slice Selection Assistance Information identifier. This field indicates the specific network slice for which the subscription is applicable. It may include a Slice / Service Type (SST) and an optional Slice Differentiator (SD). The term “Slice / Service Type” (SST) refers to a value used to identify a specific type of network slice in a 5G core network. The term “Slice Differentiator” (SD) refers to an optional sub-field used in conjunction with the SST to uniquely distinguish between multiple network slices offering the same service type.

[0019] The term “Dnn” refers to a sub-IE denoting the Data Network Name associated with the subscription context. The Dnn identifies the specific data network (e.g., internet, enterprise VPN, IMS) for which the subscription is relevant.

[0020] The term “ Subscript! onld” refers to a sub-IE that uniquely identifies the subscription instance created by the UDR. The identifier enables lifecycle management of the subscription, including modification, renewal, or deregistration.

[0021] The term “Contextinfo” refers to a sub-IE providing auxiliary metadata associated with the subscription session. It may include the source of the request, the purpose of the subscription, access type (e.g., 3GPP access vs. non-3GPP access), or policy hints. Contextinfo enhances filtering, routing, or logging of notifications within the system.

[0022] The term “Plmnld” refers to a sub-IE specifying the Public Land MobileNetwork Identifier associated with the subscription. It typically comprises the Mobile Country Code (MCC) and Mobile Network Code (MNC), thereby uniquely identifying the operator network for which the subscription is valid.

[0023] The “Subscribe” Service operation is used in network management and communications systems to enable a Network Function (NF) to receive ongoing notifications about changes or updates to a specific resource or set of data.

[0024] Subscription Identifier (ID) is allocated by the UDM when the subscribe request is received. It may be used by the consumer of the UDM to correlate the received notification with the active subscription.

[0025] Data network name (dnn) is a unique identifier that specifies a particular data network or service in a telecommunications network.

[0026] Network Repository Function (NRF) is a crucial network function within the 5G Core (5GC) network architecture, designed to facilitate service discovery and management of network functions.

[0027] Public Land Mobile Network Identifier (plmnld) is a critical element in mobile telecommunications, used to uniquely identify a public land mobile network within a global network of telecommunications systems.

[0028] Network Slice Selection Assistance Information (Nssai) is a key concept in the 5G network architecture, specifically designed to facilitate the management and selection of network slices for different types of services and user requirements.

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

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

[0031] In modern telecommunication networks, particularly in fifth generation (5G) architectures, Network Functions (NFs) operate as modular, service-oriented components configured for delivering critical control and user plane functionalities. Examples of such NFs include the Access and Mobility Management Function (AMF), Session Management Function (SMF), Short Message Service Function (SMSF), Gateway Mobile Location Center (GMLC), Network Exposure Function (NEF), Data Distribution Network Management Function (DDNMF), Network Data Analytics Function (NWDAF), Data Communication Control Function (DCCF), and Trusted Application Function (Trusted AF). These NFs interact with the Unified Data Management (UDM) component to obtain user subscription data necessary to perform authentication, session management, policy enforcement, and service delivery.

[0032] To access the relevant subscriber data, each consumer NF initiates a Get operation using the service interface. This operation enables retrieval of subscription data associated with a particular User Equipment (UE), including parameters that define access restrictions, mobility policies, subscribed services, and other userspecific configurations. In addition to retrieval, the consumer NFs are also required to monitor any changes in the subscription data that may impact ongoing sessions or network behavior. This is facilitated through a Subscribe operation using the same interface. The Subscribe operation enables the NF to receive notifications from the UDM when the underlying subscription data is modified. Such notifications allow the NF to update its internal state and ensure compliance with the most current user entitlements.

[0033] A similar process is observed between the UDM and the Unified Data Repository (UDR). The UDM, acting as a consumer, retrieves subscriber data from the UDR using a Query operation and separately subscribes to updates using a Subscribe operation available through Nudr DM service interfaces. These interfaces adhere to specifications defined in telecommunications standards and are designed to ensure consistency of subscriber data across network functions.

[0034] In existing implementations, the Get and Subscribe operations are implemented as distinct service invocations. Each consumer NF performs two transactions: one to retrieve the subscription data and another to subscribe for changes to that data. Although logically connected, these actions are treated independently within the system and are not combined into a single workflow. This separation results in a sequential and redundant process that requires two separate requests and responses for every instance where both retrieval and monitoring are required.

[0035] This conventional dual-operation approach introduces increased signaling load and resource consumption on both the consumer NF and the UDM. The consumer NF must allocate processing resources to execute both transactionsindependently and maintain the resulting transaction contexts. The UDM, in turn, is required to handle separate service requests for the same consumer, which leads to duplicated state management, redundant access validations, and increased message handling. The same pattern of inefficiency is reflected in the UDM's downstream interactions with the UDR, where retrieval and subscription operations are also performed as separate transactions.

[0036] The need for two sequential service operations results in elevated latency, unnecessary use of control plane bandwidth, and increased internal system load. In high-throughput networks with thousands of consumer NTs operating concurrently, the cumulative effect of such redundant interactions can significantly degrade performance, increase the likelihood of signaling bottlenecks, and reduce the scalability of the system. Furthermore, in scenarios where both the Get and Subscribe operations are routinely performed together, the lack of integration between the two functions represents an inefficiency in interface design and protocol behavior.

[0037] A further limitation in existing systems is the absence of any mechanism by which a consumer NF may indicate, within a single service call, the requirement to both retrieve subscription data and subscribe to updates. The service definitions do not provide a way to embed subscription parameters into the retrieval request. Likewise, server-side components such as the UDM and UDR are not equipped to detect such combined intent and process it accordingly. The need to interpret, schedule, and execute two independent transactions adds complexity to the service handling logic and increases the chance of synchronization delays or race conditions, particularly in latency-sensitive deployments.

[0038] Accordingly, there exists a need in current telecommunications systems involving inefficiencies in the handling of subscription data access and monitoring. The reliance on sequential execution of Get and Subscribe operations introduces redundant processing, increased latency, signaling overhead, and architecturalcomplexity. These limitations hinder the responsiveness and efficiency of network functions and constrain the ability of the system to scale dynamically with user demand and service diversity.OBJECTIVES OF THE DISCLOSURE

[0039] Some of the objectives of the present disclosure, which at least one embodiment herein satisfies, are as follows:

[0040] An object of the present disclosure is to provide a system and a method for a revised Get operation that includes the “SdmSubscription” Information Element (IE). This allows for retrieving both general subscriber data and detailed subscription information in a single request.

[0041] Another object of the present disclosure is to provide the IE that carries comprehensive subscription details, including attributes such as subscription status and service configurations, integrated within the Get operation response.

[0042] Another object of the present disclosure is to provide a system and a method that enables obtaining both subscriber and subscription information through a single service operation, improving data completeness and reducing the need for multiple requests.

[0043] Another object of the present disclosure is to reduce the total number of transactions required between consumer Network Functions (NFs) and the Unified Data Management (UDM) and between the UDM and the Unified Data Repository (UDR), leading to lower transaction overhead and improved system efficiency.

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

[0045] In an exemplary embodiment, a method for managing data fetching operation and subscribe operation in a network is described. The method comprises receiving, by a network function, a request to obtain subscription data and to subscribe for the subscription data associated with a user equipment (UE). The method comprises initiating, by the network function, a service operation towards a unified data management (UDM) based on the received request, wherein the service operation comprises either a combination of Get and Subscribe service operation or a modified Get service operation. The method further comprises obtaining, by the network function, subscription data and an indication of successful subscription for the subscription data from the UDM.

[0046] In an embodiment, the network function is one of an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a Short Message Service Function (SMSF), a Gateway Mobile Location Center (GMLC), a Network Exposure Function (NEF), a Network Data Analytics Function (NWDAF), and a Data Collection Coordination Function (DCCF).

[0047] In an embodiment, the method further comprises determining, by the UDM, whether the service operation corresponds to the combination of Get and Subscribe service operation or the modified Get service operation.

[0048] In an embodiment, the method further comprises initiating, by the UDM towards a Unified Data Repository (UDR), either a combination of Query and Subscribe service operation when the determined service operation is the combination of Get and Subscribe service operation, or a modified Query service operation when the determined service operation is the modified Get service operation.

[0049] In an embodiment, the UDR performs the corresponding initiated service operation to transmit the subscription data and a subscription identifier (ID) after creating the subscription for the subscription data towards the UDM.

[0050] In an embodiment, the UDM transmits the subscription data and the subscription ID after creating the subscription for the subscription data towards the network function.

[0051] In an embodiment, the modified Get service operation comprises at least one additional Information Element (IE) associated with the Subscribe service operation.

[0052] In an embodiment, the modified Query service operation comprises at least one additional Information Element (IE) associated with the Subscribe service operation.

[0053] In an exemplary embodiment, a system for managing data fetching operation and subscribe operation in a network is disclosed. The system comprises a network function configured to receive a request to obtain subscription data and to subscribe for the subscription data associated with a user equipment (UE). The network function is configured to initiate a service operation towards a unified data management (UDM) based on the received request, wherein the service operation comprises either a combination of Get and Subscribe service operation or a modified Get service operation. The network function is configured to obtain subscription data and an indication of successful subscription for the subscription data from the UDM.

[0054] In an exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium is disclosed. The non-transitory computer- readable medium comprises instructions that, when executed by one or more processors, cause the one or more processors to receive, by a network function, a request to obtain subscription data and to subscribe for the subscription data associatedwith a user equipment (UE). The instructions further cause the one or more processors to initiate, by the network function, a service operation towards a unified data management (UDM) based on the received request, wherein the service operation comprises either a combination of Get and Subscribe service operation or a modified Get service operation, and to obtain, by the network function, subscription data and an indication of successful subscription for the subscription data from the UDM.BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING

[0055] 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 disclosure of electrical components, electronic components or circuitry commonly used to implement such components.FIG. 1 illustrates an exemplary network architecture of a system for managing data fetching and subscribe operations in a network, in accordance with an embodiment of the present disclosure.FIG. 2 illustrates a block diagram of the system, in accordance with an embodiment of the present disclosure.FIG. 3 illustrates an exemplary flow diagram of a method for managing data fetching and subscribe operations in a network, in accordance with an embodiment of the present disclosure.FIG. 4 illustrates another exemplary flow diagram of the method, in accordance with an embodiment of the present disclosure.FIG. 5 illustrates a method flow chart for managing data fetching and subscribe operations in a network, in accordance with an embodiment of the present disclosure.FIG. 6 illustrates an example computer system in which or with which the embodiments of the present disclosure may be implemented.

[0056] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network Architecture102 - User(s)104 -User Equipments (UEs)106 - Network108 - System200 - Block Diagram202 - Processor(s)204 - Memory206 -Interface(s)208 - Processing Engine210 - Database300, 500 - Flow Diagram400 - System architecture402 - Network Function404 - Transition Application600 - Computer System610 - External Storage Device620 - Bus630 - Main Memory640 - Read Only Memory650 - Mass Storage Device660 - Communication Port670 - ProcessorDETAILED DESCRIPTION

[0057] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address 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 ofthe 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.

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

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

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

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

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

[0063] The terminology used herein is to describe particular embodiments only and is not intended to be limiting the disclosure. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms “comprises” and / or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term “and / or” includes any combinations of one or more of the associated listed items. It should be noted that theterms “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 particular type of 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.

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

[0065] In modern network management systems, the efficiency of data retrieval and transaction handling is critical for maintaining high performance and reducing operational overhead. However, conventional techniques require separate transactions for fetching subscriber data and subscribing to updates, which can lead to increased load on network functions and data management systems. Thus, there is a need for a system and a method that can mitigate the disadvantages of the prior art.

[0066] According to the present disclosure, by integrating the Get and Subscribe operations into a single, unified transaction, the present disclosure significantly reduces the number of interactions required between consumer network functions and data management systems. The present disclosure minimizes transaction overhead, and enhances resource utilization and overall system performance. Thepresent disclosure addresses the inefficiencies of the conventional techniques by combining data fetching and subscription management, thus improving responsiveness and reducing latency in network operations. The present disclosure results in advancing network efficiency and ensuring more effective management of subscriber information.

[0067] The present disclosure provides “Get with Subscription” service operation that offers a streamlined approach by combining the traditional Get and Subscribe operations into a single, integrated transaction. Instead of requiring two separate transactions, one for retrieving current subscriber data and another for subscribing to updates, the “Get with Subscription” operation enables the consumer Network Functions (NFs) to accomplish both tasks simultaneously. This integration reduces the number of transactions needed between the consumer NF and the Unified Data Management (UDM) system, as well as between the UDM and the Unified Data Repository (UDR), if applicable.

[0068] In an embodiment, the present disclosure provides “Nudr DM QueryWSubsc” service operation from the UDM to the UDR analogous to the “Get with Subscription” operation. The “Nudr_DM_QueryWSubsc” is designed to optimize interactions between the UDM system and the UDR. The new service operation combines the functionalities of the conventional ‘Nudr DM Query” and “Nudr_DM_Subscribe” operations into a single, integrated transaction. By merging these operations, the “Nudr_DM_QueryWSubsc” service allows the UDM to perform both the retrieval of subscriber data and the subscription to updates in one unified request. The present disclosure reduces the number of separate transactions required, thereby minimizing overhead and improving efficiency. The present disclosure simplifies the process of fetching and subscribing to subscriber information changes, leading to faster response times, reduced system load, and more effective data management across the UDM-UDR interface. By consolidating the operations, the new service minimizes transaction overhead, decreases processing load, and improvesoverall efficiency, leading to faster data retrieval, reduced latency, and enhanced responsiveness in network management. The present disclosure simplifies the interaction process, reduces potential errors, and optimizes resource utilization, ultimately resulting in a more effective and agile network system.

[0069] In an embodiment, the present disclosure provides a modified service operation “Get” that introduces an enhancement to the conventional “Get” operation by incorporating the “SdmSubscription” Information Element (IE), along with its corresponding sub IES as specified in available standards. The sub IES may include specific sub-components within the “SdmSubscription” IE that provide detailed attributes related to the subscription e.g., “callbackreference” “singleNssai”, “dnn”, “subscriptionld”, “contextinfo” , “plmnid” etc. The sub IEs may include subscription status, service configurations, entitlements, and other subscription-related parameters. The modification allows the Get operation to not only retrieve the general subscriber data but also include detailed subscription information in the response. By embedding the “SdmSubscription” IE and its sub IEs, the updated Get operation offers a more thorough and integrated view of the subscriber information.

[0070] In an embodiment, similarly, the “Nudr DM Query” service operation will be updated to include the “SubsData” IE e.g., “callbackreference” “singleNssai”, “dnn”, “subscriptionld”, “contextinfo” , “plmnid” etc.

[0071] The update will ensure that the “Nudr DM Query” operation can also fetch detailed subscription data along with the general subscriber information. The modifications enhance the functionality of both the Get and “Nudr DM Query” operations by integrating subscription-specific data into their responses, thereby improving the completeness of the information retrieved and streamlining the data management processes.

[0072] In an embodiment, the UDM and the UDR supports the new service operation and the modified service operation. Further, an alternative approach for identifying a supported service operation (method) involves using a combination of the supported features bit and / or Network Repository Function (NRF) profile indications. The supported features bit method entails using a specific bit or flag within a feature indicator to denote the support for particular service operations or capabilities. The NRF maintains profiles of available consumer NFs and their supported features. By including the supported service operations in the NRF profile, consumer NFs can advertise their capabilities to other network functions. This profile information can include specific indications or metadata about whether an NF supports the integrated service operations. When other consumer NFs need to interact with a specific consumer NF, they can query the NRF to retrieve this profile information and identify which methods are supported.

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

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

[0075] FIG. 1 illustrates an exemplary network architecture of a system for managing data fetching and subscribe operations in a network, in accordance with an embodiment of the present disclosure.

[0076] As illustrated in FIG. 1, the network architecture (100) may include one or more user equipment (UE) ( 104- 1 , 104-2... 104-N) associated with one or more users (102-1, 102-2... 102 -N) in an environment. A person of ordinary skill in the art will understand that one or more users (102-1, 102-2... 102-N) may collectively referred to as the users (102). Similarly, a person of ordinary skill in the art will understand that one or more UEs (104-1, 104-2... 104-N) may be collectively referred to as the UE(104). Although only three UE (104) are depicted in FIG. 1, however, any number of the UE (104) may be included without departing from the scope of the ongoing description.

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

[0078] Additionally, in some embodiments, the UE (104) may include, but 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 headmounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and / or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the UE (104) may include, but are not limited to, any electrical, electronic, electromechanical, or equipment, or a combination of one or more of the above devices, such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general -purpose computer,desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device, wherein the UE (104) may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user (102) or the entity such as touchpad, touch-enabled screen, 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.

[0079] Referring to FIG. 1, the UE (104) may communicate with a system (108) through a network (wireless communication network) (106) for sending or receiving various types of data. In an embodiment, the network (106) may include at least one of a 5G network, 6G network, or the like. The network (106) may enable the UE (104) to communicate with other devices in the network architecture (100) and / or with the system (108). The network (106) may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network (106) may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like.

[0080] In an embodiment, the network (106) may include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network (106) may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet- switched network, a circuit-switched network, an ad hoc network, an infrastructurenetwork, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.

[0081] In an embodiment, the UE (104) is communicatively coupled with the network (106). The network (106) may receive a connection request from the UE (104). The network (106) 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.

[0082] Although 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).

[0083] FIG. 2 illustrates an exemplary block diagram (200) of the system (108) configured for managing data fetching and subscribe operations in a network, in accordance with an embodiment of the present disclosure

[0084] The system (108) includes one or more processors (202). The processor(s) (202) may comprise general-purpose or dedicated processing resources, such as microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or system-on- chip (SoC) components. The processor(s) (202) are configured to execute machine- readable instructions to perform subscription data orchestration, inter-network function signaling, service request validation, protocol decoding, and dynamic subscription session handling. In some embodiments, the processor(s) (202) may operate in a multithreaded environment with support for concurrent transaction execution acrossdifferent subscriber contexts. Additionally, the processor(s) (202) may be configured to apply request differentiation rules based on input payload characteristics, monitor performance counters, manage timer-triggered cleanup of expired subscription contexts, and ensure adherence to service-level agreements by dynamically allocating processing resources based on request priority.

[0085] The memory (204) is operably coupled to the processor(s) (202) and stores executable program code, runtime session data, state flags, configuration templates, and service logic policies. The memory (204) may include volatile memory such as dynamic RAM (DRAM) for real-time processing and non-volatile memory such as NAND flash, EEPROM, or phase-change memory for persistent data retention. In one embodiment, the memory (204) may cache subscription templates or default Information Elements (IES) for rapid response generation. In another embodiment, the memory (204) includes a lookup table for associating received NF request formats with internal service processing modules. The memory (204) may also store precompiled rule sets for IE parsing, schema translation mappings for multiple 3 GPP releases, and state tables for concurrently tracked UE contexts. In certain configurations, memory (204) may include segmented buffers for atomic operations and concurrent updates to avoid race conditions in subscription lifecycle handling.

[0086] The interface(s) (206) are configured to enable communication between the system (108) and external entities, including but not limited to NFs and a Unified Data Repository (UDR). The interface(s) (206) may support both synchronous and asynchronous message exchange and may implement 3GPP-defined service-based interfaces (SBIs) such as Nudm SDM and Nudr DM over protocols including HTTP / 2, TCP, SCTP, or QUIC. In one embodiment, the interface(s) (206) may include container-native service mesh interfaces that route traffic between microservices within a virtualized UDM instance. The interface(s) (206) may be implemented via software-defined network adapters or through virtual NICs embedded in networkfunction virtualization infrastructure (NFVI). In certain implementations, the interface(s) (206) may also include protocol translation gateways for interoperability with legacy systems or inter-PLMN scenarios. Interface configuration may support QoS markings, connection retry mechanisms, MTLS security, and request tracing for end-to-end observability.

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

[0088] In an embodiment, the system (108) may include a database (210) that includes data that may be either stored or generated as a result of functionalities implemented by any of the components of the processor (202) or the processing engine (208).

[0089] The database (210) is configured to persist the results of interactions with the UDR, including subscription data, associated IDs, context version tags, andoperational metadata. The database (210) may be implemented as a distributed NoSQL store, a clustered SQL database, or an in-memory key-value engine depending on deployment scale. For example, in a deployment supporting millions of subscribers, the database (210) may be realized using a sharded Cassandra cluster with TTL policies for temporary subscription contexts. The database (210) supports indexed retrieval of UE-related data keyed by SUCI or SUPI identifiers. In another embodiment, the database (210) may maintain a subscription change log, a retry queue for failed transactions, and checkpoint snapshots for audit compliance.

[0090] In one embodiment, the system (108) may be implemented as a network function (NF) and may be interchangeably referred to as an NF throughout the present disclosure. The NF refers to a virtualized or physical component within a network infrastructure that is configured for performing specific tasks necessary for the delivery and management of network services. Examples of such NFs may include, but are not limited to, a session border controller (SBC), which manages signaling and media streams for real-time communication sessions; a load balancer, which distributes network traffic across multiple servers to optimize resource utilization; a network address translation (NAT) function, which enables multiple devices on a local network to access external networks using a single public IP address and a domain name system (DNS) function, which translates human-readable domain names into machine- readable IP addresses.

[0091] These NFs are configured to perform well-defined roles that are essential to the efficient operation and reliability of telecommunications and data networks. The specific functions carried out by these NFs may include, but are not limited to, packet routing, network switching, traffic filtering and firewalling, load distribution, traffic prioritization, session handling, and other traffic management operations. Such capabilities enable the network to maintain service continuity,improve responsiveness, manage congestion, and ensure secure and optimized data flow across interconnected systems and services.

[0092] In an embodiment, the NF is configured to receive a request to obtain subscription data and to subscribe for the subscription data associated with a user equipment (UE). The network function is instantiated within the network to serve as a consumer of subscription data, such as UE-specific policy, configuration, or service- related information. In one embodiment, the network function is configured to be one of an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a Short Message Service Function (SMSF), a Gateway Mobile Location Center (GMLC), a Network Exposure Function (NEF), a Network Data Analytics Function (NWDAF), or a Data Collection Coordination Function (DCCF). Each of these network functions is configured to retrieve UE-specific subscription data and register interest for subsequent notifications pertaining to the subscribed information. Each of these functions provides specialized services within the 5G core network architecture.

[0093] The AMF is configured for handling connection and mobility management for UE. It may request subscription data related to UE mobility restrictions, registration areas, allowed tracking area lists, and configuration updates needed for access stratum security context handling. For example, when a UE performs initial registration, the AMF retrieves its mobility subscription profile from the UDM and registers for updates to ensure timely adaptations to access network policies. The AMF may be configured to support emergency registration procedures, periodic registration updates, and handover-related subscription data refreshes.

[0094] The SMF handles session management tasks such as PDU session establishment, modification, and release. It requires subscription data such as session continuity settings, Quality of Service (QoS) profiles, and policy control information. The SMF may subscribe to receive updates on session policy changes or session releasetriggers for a given UE. It may be deployed in distributed user plane (CUPS) configurations or integrated with UPFs to align session state changes with underlying transport policies.

[0095] The SMSF is configured for supporting SMS services over IP-based networks. It may retrieve and subscribe to SMS configuration parameters for a UE, such as supported delivery modes or service center routing addresses. For instance, during UE attach procedures, the SMSF ensures that SMS services are provisioned correctly by retrieving the subscriber's SMS profile and subscribing to changes. It may be configured to support store-and-forward modes and instant delivery based on UE capability indication.

[0096] The GMLC is utilized for location-based services and may retrieve UE location permissions, routing indicators, and location service configurations. It subscribes for notifications when a UE changes location permissions or when new location sessions are triggered. The GMLC may also interface with external LCS clients, process privacy checks, and enforce location service usage authorizations.

[0097] The NEF serves as an exposure interface for third-party application functions. It retrieves service authorization data and subscribes to event triggers for API invocations such as service state changes or device status updates. For example, a NEF may be configured to retrieve the event exposure policy for an application and register to receive notifications when device configuration states change. The NEF may also expose RESTful APIs to external clients and manage quota enforcement through interaction with policy control functions.

[0098] The NWDAF collects and analyzes network analytics data, and it may subscribe to metrics related to UE behavior, slice usage, or service experience. For instance, it may request analytics subscription data indicating mobility patterns or service latency trends and register to receive updates on these metrics to performpredictive analytics. NWDAF may be configured with Al inference models and integrate with data lakes or external analytic pipelines.

[0099] The DCCF functions as a coordinator for collection of measurement data from multiple NFs. It retrieves subscription data to determine what information to collect from various sources and subscribes to updates indicating when measurement thresholds are crossed or when new collection rules are activated. DCCF may operate as a scheduler of periodic collection jobs, define granularity constraints, and enforce data retention parameters.

[0100] In another embodiment, upon receiving the request, the system (108), through its processing engine (208), is configured to initiate a service operation towards the Unified Data Management (UDM) based on the received request. The nature of the service operation is determined to be one of two alternatives. First, a combination of Get and Subscribe service operation, or second a modified Get service operation. These two modes of operation differ in structure, signaling semantics, compatibility requirements, and the way subscription metadata is conveyed within the service invocation.

[0101] In one embodiment, the combination of Get and Subscribe service operation refers to a consolidated request that simultaneously triggers both the retrieval of the latest subscription data for a user equipment (UE) and the registration of a subscription context that allows future change notifications to be delivered to the requesting NF. This combination operation is implemented as a single atomic transaction, typically expressed using a service primitive such as Nudm SubscriberDataManagement GetWSubsc. For example, consider an AMF that needs to retrieve AM subscription data for a newly registered UE. By invoking this combined operation, the AMF can immediately obtain the UE’s tracking area list, mobility restriction information, and registration policy data, and simultaneously register interest to receive update notifications whenever these parameters are modifiedin the UDR. Thus, the system (108) renders reduced signaling overhead, synchronized state between the NF and the data repository, and improved network responsiveness by consolidating two functionally related operations into a single interaction.

[0102] In one implementation, the combination service operation comprises a request message that includes both data query parameters (e.g., SUPI, data category) and subscription registration attributes (e.g., notificationURI, expiryTime, monitored Attributes). The UDM, upon receiving such a request, identifies the request as a GetWSubsc invocation and translates it into a corresponding Nudr DM QueryWSubsc message to the UDR. The UDR processes this message by performing two tasks, first retrieving the relevant data from its internal storage and registering a new subscription instance that includes the requested monitoring criteria. A unique subscription ID is generated and returned alongside the retrieved data to the UDM, which then transmits the complete response, including both the subscription data and the subscription ID, to the NF that initiated the request.

[0103] In another embodiment, the modified Get service operation refers to an adaptation of the conventional Get operation, enhanced to support subscription behavior by embedding the IES in the request. The IE may be “SdmSubscription”, and corresponding sub IEs as defined in 3gpp TS 29.503, which serves as a standardized container for expressing subscription parameters relevant to user equipment (UE) data monitoring. The SdmSubscription IE enables a consumer network function (NF), such as a Session Management Function (SMF), to encapsulate both the intent and configuration required for establishing a subscription context. This includes, for example, the identification of monitored attributes, notification delivery endpoints, subscription duration constraints, and applicable slice or data network parameters. By including the SdmSubscription IE within the request, typically in a Nudm_SubscriberDataManagement_Get message, the consumer NF effectively signals the Unified Data Management (UDM) that the operation is not limited to dataretrieval but also entails a request for future change notifications. The present embodiment thus ensures that the UDM initiates the appropriate procedures with the Unified Data Repository (UDR) to register the subscription context and return a subscription identifier. Importantly, the use of SdmSubscription within a modified Get operation is designed to maintain backward compatibility with consumer NFs that may not support new service operation names or primitives but can be upgraded to include optional subscription metadata within standard request formats. For example, an SMF may issue a Nudm SubscriberDataManagement Get request to obtain the UE’s session management configuration, and in doing so, may append IES such as eventNotificationURI, changeType, subscriptionLifetime, or attributeFilterList to signal that it also wishes to subscribe to changes in this data. These IEs are interpreted by the UDM as subscription registration triggers, even though the request format remains structurally similar to a legacy Get operation.

[0104] The legacy Get service operation, as conventionally defined, facilitates a one-time retrieval of subscription data associated with a user equipment (UE) from the Unified Data Management (UDM), based solely on mandatory query parameters such as the Subscription Permanent Identifier (SUPI) and the target data resource (e.g., AM data or SM policy data). This operation does not include any subscription semantics and results in a transient, stateless exchange wherein the requesting network function (NF) receives the current value of the requested data without any provision for future change notifications. In contrast, the modified Get service operation retains the same message format and interface primitives as the legacy variant but embeds additional Information Elements (IEs), for example, a SdmSubscription IE, a notificationURI, or an expiryTime, which declaratively indicate the NF's intent to register for ongoing updates to the retrieved data. Upon detecting these appended IEs, the UDM interprets the modified Get operation as one that serves both to retrieve data and to initiate a subscription session, thereby triggering subsequent notification workflows via coordination with the Unified Data Repository (UDR). Such modifiedGet operation results in backward-compatible subscription handling and avoids the need for invoking a dedicated Subscribe interface.

[0105] In one embodiment, these additional IES serve as semantic cues for the UDM and the UDR to infer subscription intent without requiring the consumer NF to invoke a separate subscription method or service endpoint. These IEs may include:

[0106] EventnotificationURI: a uniform resource identifier that specifies the callback endpoint of the NF where update notifications must be delivered;

[0107] expiryTime: a timestamp indicating the validity duration of the subscription beyond which the subscription will be terminated automatically;

[0108] monitoredAttributes: a list of attribute names within the data pay load that the NF is interested in monitoring;

[0109] changeType: a categorical flag indicating the nature of updates that should trigger a notification (e.g., value change, threshold crossing, deletion);

[0110] subscriptionPriority or maxNotificationRate: optional controls for network-level scheduling and throttling of notifications.

[0111] plmnld: a Public Land Mobile Network Identifier that specifies the operator domain to which the subscription applies;

[0112] contextinfo: descriptive metadata or auxiliary tags associated with the subscription, which may include user-defined labels, system usage context, or diagnostic markers;

[0113] reportingMode: a mode configuration indicating how the notifications are to be issued (e.g., on-change, periodic, or conditional threshold-based reporting);

[0114] subscriptionPriority: an optional flag used to indicate the priority level of the subscription for internal processing, scheduling, or throttling purposes;

[0115] singleNssai: a combination of a Slice / Service Type (SST) and an optional Slice Differentiator (SD), indicating the specific network slice for which the subscription is requested;

[0116] monitoredAttributes: a list of attribute names within the subscription data payload that the NF is interested in monitoring for changes;

[0117] dnn: a Data Network Name (DNN) such as “internet” or “ims”, which identifies the external packet data network associated with the subscribed session; and

[0118] callbackReference: a uniform resource identifier that specifies the callback endpoint of the network function (NF) where update notifications must be delivered.

[0119] The UDM, upon detecting the presence of such IES in a Get request, interprets the request as a modified Get and initiates a corresponding downstream signaling operation to the UDR in the form of a Nudr DM Query message with appended subscription-related metadata. The UDR then parses the received IEs, performs a data retrieval operation, and registers the subscription context if all metadata fields are valid. A subscription ID is generated and transmitted back to the UDM, along with the requested subscription data.

[0120] Both these approaches, however, result in the same system-level outcome. The NF receives the current subscription data and is registered to receive update notifications when changes occur. For example, a NEF that initiates a combined Get and Subscribe request for application-specific exposure controls will receive the current control values and, upon future updates by the UDR (e.g., policy revocation, throttling change), will be notified via its subscribed notification URL Similarly, a DataCollection Coordination Function (DCCF) using the modified Get operation with embedded IES for event monitoring will be subscribed to updates in measurement reporting configurations, without the need for explicitly invoking a new subscription procedure. The DCCF is a network function (NF) configured to orchestrate the collection of measurement and monitoring data across various consumer and producer functions within a 5G network. The DCCF determines what data is to be collected, from which NFs, and under what conditions. It is typically implemented in conjunction with analytics-driven use cases where timely and accurate measurement data, such as user experience metrics, policy enforcement indicators, or usage thresholds, is essential for intelligent decision-making. The DCCF interacts with other NFs, including the Network Data Analytics Function (NWDAF), the Policy Control Function (PCF), and application functions via exposure interfaces, to configure, trigger, and manage data collection task.

[0121] In another embodiment, the UDM is configured to determine whether the received service operation corresponds to the combination of Get and Subscribe service operation or to the modified Get service operation. The UDM performs such determination by parsing the received service message and inspecting structural headers and payload metadata to identify the presence of subscription-specific IEs. The service message may be received over a Nudm_SDM interface and formatted according to RESTful protocols using HTTP / 2 encapsulation. Parsing includes syntactic validation of the service endpoint, such as / nudm-sdm / vl / subscription- data / {supi}, and semantic evaluation of the accompanying metadata block. For example, if the request includes a subscription metadata block containing a notificationURI, an expiry Timestamp, a changeTriggerList, or a monitoredAttributeList, the UDM infers that the operation includes a subscription intent.

[0122] In another embodiment, based on the determination, the UDM is configured to initiate a corresponding initiated service operation to transmit the subscription data and a subscription identifier (ID) after creating the subscription for the subscription data towards the UDR. When the determined operation is the combination of Get and Subscribe, the UDM constructs a Nudr DM QueryWSubsc message and transmits it via the interface(s) (206) to the UDR. The Nudr_DM_QueryWSubsc message is a compound service primitive defined for the dual purpose of data query and subscription creation, and includes both query path parameters (e.g., supi, dataCategory) and subscription metadata (e.g., notificationURI, expiryTime, monitoredAttribute, changeType). This consolidated payload reduces roundtrip signaling latency and ensures atomicity in data and subscription state alignment. For instance, in the context of AMF retrieving and subscribing to access and mobility data, the Nudr DM QueryWSubsc may include monitored attributes such as tracking area list and mobility restriction changes, bundled with a subscription TTL of 3600 seconds.

[0123] In an alternate embodiment, when the determined operation is the modified Get service operation, the UDM transmits a Nudr DM Query request that includes at least one appended Information Element associated with the Subscribe service operation. The modified Nudr DM Query message retains the conventional GET semantics but includes an extended metadata section or query parameters indicating the subscription intent. The modified query is recognized by the UDR as containing subscription directives embedded in its query string or request body, thereby enabling implicit subscription registration during data retrieval.

[0124] In another embodiment, the UDR is configured to perform the corresponding initiated service operation and transmit the subscription data and a subscription identifier (ID) after creating the subscription for the subscription data towards the UDM. The UDR parses the received request to extract the data identifierassociated with the UE, typically the Subscription Permanent Identifier (SUPI), and identifies the requested data class (e.g., am-data, smf-sel ection, sms-subscription, policy-data). It then performs a retrieval operation from its internal data store using key-value lookup, indexed document queries, or structured path resolution based on the request URL Simultaneously, the UDR registers a subscription context using internal monitoring registries. This context includes subscription parameters such as the notification target, monitored data attributes, event types (e.g., value change, deletion), and validity duration. The UDR generates a globally unique subscription identifier (e.g., sub-9f6e78) associated with the subscription session and returns a composite response containing both the subscription data and the subscription ID. This enables consistent state management and future event correlation.

[0125] In another embodiment, the NF is configured to service operation data and an indication of successful subscription for the subscription data from the UDM. The UDM transmits the subscription data and the subscription ID, after creating the subscription, towards the initiating network function. This transmission is conducted over the Nudm SDM interface and is formatted according to service response schemas, including both the data object (e.g., mobility restriction configuration) and metadata (e.g., subscriptionld). The response ensures that the network function not only obtains the required configuration or policy information but is also equipped with the reference identifier for managing the active subscription session. The subscription ID enables the network function to subsequently perform lifecycle operations such as modifying subscription parameters, extending the subscription expiration, or explicitly deregistering the subscription. For instance, a NWDAF may use the received subscription ID to later issue a Nudm SubscriberDataManagement Unsubscribe call when its analytics horizon changes or when it no longer requires notifications.

[0126] In an illustrative working example, a Session Management Function (SMF) receives a request to obtain UE session-level subscription data, includingallowed QoS profiles and PDU session authorization rules. The SMF transmits a modified Get request including an additional IE indicating interest in future updates related to session configuration changes. The UDM, via the processing engine (208), detects the embedded subscription intent and initiates a modified Nudr DM Query with the parsed IES. The UDR returns the current session subscription data and registers the SMF for future notifications. If the UE’s session profile is later updated due to policy enforcement or user-triggered configuration changes, the UDR automatically sends a notification to the SMF using the previously registered subscription context, thereby enabling real-time session consistency without redundant polling.

[0127] FIG. 3 illustrates an exemplary flow diagram of a method (300) for managing data fetching and subscribe operations in a network, in accordance with an embodiment of the present disclosure.

[0128] At step 308, the UDM (304) receives a message from the consumer NF (302). The UDM (304) checks that it is the new service operation i.e. “Nudm SubscriberDataManagement GetWSubsc” with modified IEs (sub IEs). The “Nudm_SubscriberDataManagement_GetWSubsc” operation is a standardized service operation that enables a consumer Network Function (NF) to simultaneously retrieve subscriber-related data and register for subsequent change notifications pertaining to the same data.

[0129] At step 310, the UDM (304) communicates with the UDR (306) using the Nudr_DM_QueryWSubsc with modified IEs. The “Nudr_DM_QueryWSubsc” is a service operation which is invoked by the UDM to both retrieve subscription-related data and concurrently register a subscription context within the UDR for receiving future update notifications.

[0130] At step 312, the UDR (306) created a subscription for the UDM (304) based on a single transaction and provides a response message to the UDM (304). The response message comprises subscription data and subscription identifier (ID).

[0131] At step 314, the UDM (304) creates subscription for the consumer NF (302) for monitored resources. The UDM (304) sends the response message towards consumer NF (302) along with the subscription data and the subscription ID.

[0132] In an embodiment, the consumer NF processes the subscription data and subscription confirmation received from the UDM (304).

[0133] FIG. 4 illustrates another exemplary flow diagram of the method (400), in accordance with an embodiment of the present disclosure.

[0134] At step 402, the UDM (304) receives a message from the consumer NF (302). The UDM (304) checks that it is the new service operation i.e. “Nudm SubscriberDataManagement Get” message with modified IES. The “Nudm_SubscriberDataManagement_Get” message may include the “SdmSubscription” IE.

[0135] At step 404, the UDM (304) communicates with the UDR (306) using the “Nudr DM Query” with modified IEs (Subsdata IEs).

[0136] At step 406, the UDR (306) provides a response message to the UDM (304). The response message comprises subscription data with subscription ID. Thus, the UDR (306) creates subscription based on single transaction and passes the same towards UDM (304).

[0137] At step 408, the UDM (304) creates subscription for the consumer NF (302) for monitored resources and also sends the response message back towards consumer NF (302). The response message includes the subscription data with thesubscription ID. In an embodiment, the consumer NF (302) processes the subscription data and subscription confirmation received from the UDM (304).

[0138] In an embodiment, the present disclosure provides a system and a method for managing data fetching and subscribe operations in the network (106). The method comprising transmitting, by the consumer NF (302), at least one first request message related to subscription data towards the UDM (304). The method comprising communicating, by the UDM (304), at least one second request message related to the at least one first request message towards the UDR (306). The method comprising receiving, by the UDM (304), at least one response message from the UDR (306). The method comprising communicating, by the UDM (304), the at least one received response message towards the consumer NF (302). The method comprising performing, by the consumer NF (302), at least one operation based on the at least one received response message.

[0139] FIG. 5 illustrates a flowchart (500) depicting an exemplary method for managing data fetching and subscribe operations in a network, in accordance with one or more embodiments of the present disclosure.

[0140] At step (502), the method includes receiving, by a network function, a request to obtain subscription data and to subscribe for the subscription data associated with a user equipment (UE). In one embodiment, the NF may be configured as one of an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a Short Message Service Function (SMSF), a Gateway Mobile Uocation Center (GMLC), a Network Exposure Function (NEF), a Network Data Analytics Function (NWDAF), or a Data Collection Coordination Function (DCCF). Each of these network functions may initiate such a request in the context of their respective roles: for example, the AMF may request mobility subscription data; the SMF may initiate data retrieval for PDU session policies; and the NEF may subscribe to service exposure triggers associated with UE behavior.

[0141] At step (504), the method includes initiating, by the network function, a service operation towards a Unified Data Management (UDM) node based on the received request. In an embodiment, the service operation may be configured as either a combination of Get and Subscribe service operation or a modified Get service operation. In one embodiment, the modified Get service operation includes at least one additional Information Element (IE) that indicates a subscription intent alongside the retrieval of existing data. These additional IES may be schema-aligned with 3 GPP definitions to ensure compatibility with both standard and extended service operations. The network function is configured to select the type of service operation depending on system capabilities, latency tolerance, and compatibility with legacy or hybrid UDM implementations.

[0142] In an embodiment, upon receiving the service operation request, the UDM is configured to determine whether the requested operation corresponds to the combined Get and Subscribe service operation or the modified Get service operation. Based on this determination, the UDM invokes the appropriate downstream action toward a Unified Data Repository (UDR).

[0143] At step (506), the method includes obtaining, by the network function, subscription data and an indication of successful subscription for the subscription data from the UDM. In an embodiment, when the UDM confirms that the request is a combined operation, it initiates a combination of Query and Subscribe service operation toward the UDR. In another embodiment, when the UDM identifies the operation as a modified Get request, it triggers a modified Query service operation to the UDR that includes one or more additional IEs associated with the subscription handling. These IEs may specify the resource to be monitored, the notification granularity, and the update triggering conditions.

[0144] In an embodiment, the UDR performs the corresponding service operation and transmits the requested subscription data and a subscription identifier(ID) after creating the appropriate subscription context. The subscription ID confirms the establishment of a monitoring session within the UDR for the subscribed resource or attribute. The UDM receives this data and, in an embodiment, transmits both the subscription data and the associated subscription ID to the originating network function. This enables the network function to maintain consistency of service logic, initiate tracking for asynchronous updates, and correlate future notifications with the current UE context.

[0145] In one illustrative example, a NEF operating as the network function may receive a third-party request for monitoring device configuration changes. The NEF prepares a request with extended IES that indicate both the required subscription data and the need to subscribe for future updates. Upon sending this to the UDM, the UDM identifies the request as a modified Get service operation, invokes the modified Query operation to the UDR, receives the subscription data along with a subscription ID, and returns both elements to the NEF. The NEF stores the subscription ID and establishes a callback mechanism to handle future data updates using the registered subscription context.

[0146] In this manner, FIG. 5 exemplifies a cohesive signaling and data orchestration method that enables both immediate access to subscription data and realtime subscription registration through a unified service interaction between the network function, the UDM, and the UDR.

[0147] FIG. 6 illustrates an example computer system (600) in which or with which the embodiments of the present disclosure may be implemented.

[0148] 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(s) (660), and a processor (670). A person skilled in the art will appreciate that the computer system (600) may include more than one processor and communication ports. The processor (670) may includevarious modules associated with embodiments of the present disclosure. The communication port(s) (660) may be any of an RS -232 port for use with a modembased dialup connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication ports(s) (660) may be chosen depending on a network, such as a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system (600) connects.

[0149] In an embodiment, the main memory (630) may be 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) chip for storing static information e.g., start-up or basic input / output system (BIOS) instructions for the processor (670). The mass storage device (650) may be any current or future mass storage solution, which can be used to store information and / or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PAT A) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Lirewire interfaces).

[0150] In an embodiment, the bus (620) may communicatively couple 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, Small Computer System Interface (SCSI), Universal Serial Bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (670) to the computer system (600).

[0151] In another embodiment, operator and administrative interfaces, e.g., a display, keyboard, and cursor control device may also be coupled to the bus (620) tosupport direct operator interaction with the computer system (600). Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) (660). The 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.

[0152] While considerable emphasis has been placed herein on the components and component parts of the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiment, as well as other embodiments of the disclosure, will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be interpreted merely as illustrative of the disclosure and not as a limitation.ADVANTAGES OF THE PRESENT DISCLOSURE

[0153] The present disclosure described herein above has several technical advantages including, but not limited to, the realization of the system and the method that:

[0154] The present disclosure provides a system and a method that provides a revised Get operation that includes the “SdmSubscription” Information Element (IE), which allows for retrieving both general subscriber data and detailed subscription information in a single request.

[0155] The present disclosure provides the IE that carries comprehensive subscription details, including attributes such as subscription status and service configurations, integrated within the Get operation response.

[0156] The present disclosure provides a system and a method that enables in obtaining both subscriber and subscription information through a single service operation, improving data completeness, and reducing the need for multiple requests.

[0157] The present disclosure provides a reduction in the total number of transactions required between consumer NFs and the UDM system, as well as between the UDM and the UDR, leading to lower transaction overhead and improved system efficiency.

Claims

CLAIMS1. A method (500) for managing data fetching operation and subscribe operation in a network (106), the method (500) comprising: receiving, by a network function (402), a request to obtain subscription data and to subscribe for the subscription data associated with a user equipment (UE) (104); initiating, by the network function (402), a service operation towards a unified data management (UDM) implemented in a system (108) based on the received request, wherein the service operation comprises either: a combination of Get and Subscribe service operation or a modified Get service operation; and obtaining, by the network function (402), subscription data and an indication of successful subscription for the subscription data from the UDM.

2. The method (500) as claimed in claim 1, wherein the network function (402) is one of an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a Short Message Service Function (SMSF), a Gateway Mobile Location Center (GMLC), a Network Exposure Function (NEF), a Network Data Analytics Function (NWDAF), and a Data Collection Coordination Function (DCCF).

3. The method (500) as claimed in claim 1, further comprising determining, by the UDM implemented in the system (108), whether the service operation corresponds to the combination of Get and Subscribe service operation or the modified Get service operation.

4. The method (500) as claimed in claim 3, further comprising, initiating, by the UDM towards a Unified Data Repository (UDR), either:a combination of Query and Subscribe service operation when the determined service operation is the combination of Get and Subscribe service operation; or a modified Query service operation when the determined service operation is the modified Get service operation.

5. The method (500) as claimed in claim 4, wherein the UDR performs the corresponding initiated service operation to transmit the subscription data and a subscription identifier (ID) after creating the subscription for the subscription data towards the UDM.

6. The method (500) as claimed in claim 5, wherein the UDM transmits the subscription data and the subscription ID after creating the subscription for the subscription data towards the network function (402).

7. The method (500) as claimed in claim 1, wherein the modified Get service operation comprises at least one additional Information Element (IE) associated with the Subscribe service operation.

8. The method (500) as claimed in claim 4, wherein the modified Query service operation comprises at least one additional IE associated with the Subscribe service operation.

9. A system (108) for managing data fetching operation and subscribe operation in a network (106), the system (108) comprising: a network function (402) configured to: receive a request to obtain subscription data and to subscribe for the subscription data associated with a user equipment (UE) (104);initiate a service operation towards a unified data management (UDM) based on the received request, wherein the service operation comprises either: a combination of Get and Subscribe service operation or a modified Get service operation; and obtain subscription data and an indication of successful subscription for the subscription data from the UDM.

10. The system (108) as claimed in claim 9, wherein the network function (402) is one of an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a Short Message Service Function (SMSF), a Gateway Mobile Location Center (GMLC), a Network Exposure Function (NEF), a Network Data Analytics Function (NWDAF), and a Data Collection Coordination Function (DCCF).

11. The system (108) as claimed in claim 9, wherein the UDM comprises a processing engine (208) configured to determine whether the service operation corresponds to the combination of Get and Subscribe service operation or the modified Get service operation12. The system (108) as claimed in claim 11, wherein the UDM is further configured to initiate, via an interface (206), towards a Unified Data Repository (UDR), either: a combination of Query and Subscribe service operation when the determined service operation is the combination of Get and Subscribe service operation; or a modified Query service operation when the determined service operation is the modified Get service operation.

13. The system (108) as claimed in claim 12, wherein the UDR is configured to perform the corresponding initiated service operation to transmit the subscription dataand a subscription identifier (ID) after creating the subscription for the subscription data towards the UDM.

14. The system (108) as claimed in claim 13, wherein the UDM is configured to transmit the subscription data and the subscription ID after creating the subscription for the subscription data towards the network function (402) via the interface (206).

15. The system (108) as claimed in claim 9, wherein the modified Get service operation comprises at least one additional Information Element (IE) associated with the Subscribe service operation and is stored in memory (204).

16. The system (108) as claimed in claim 12, wherein the modified Query service operation comprises at least one additional IE associated with the Subscribe service operation, and is issued by the processing engine (208).

17. A computer program product comprising a non -transitory computer-readable medium stored in memory (204), comprising instructions that, when executed by one or more processors (202), cause the one or more processors (202) to: receive, by a network function (402), a request to obtain subscription data and to subscribe for the subscription data associated with a user equipment (UE) (104); initiate, by the network function (402), a service operation towards a unified data management (UDM) implemented in the system (108) based on the received request, wherein the service operation comprises either: a combination of Get and Subscribe service operation or a modified Get service operation; and obtain, by the network function (402), subscription data and an indication of successful subscription for the subscription data from the UDM.

Images