System and method for retrieving multiple subscription data in a network through a single transaction

Abstract

The present disclosure provides a system (108) and a method (400) for retrieving multiple subscription data in a network (106) through a single transaction. The system (108) includes a UDM (304). The UDM (304) receives a combined data retrieval request from a consumer NF (302) to obtain a set of subscription data in one operation. The UDM (304) determines whether the requested subscription data is available in the UDM (304) or requires retrieval from a UDR (306). If at least one type of subscription data is not available, the UDM (304) transmits a data query request to the UDR (306), receives the at least one type of subscription data, and generates a consolidated response including another type of subscription data available in the UDM (304) and the at least one type of subscription data retrieved from the UDR (306). The consolidated response is sent to the consumer NF (302).

Description

SYSTEM AND METHOD FOR RETRIEVING MULTIPLE SUBSCRIPTION DATA IN A NETWORK THROUGH A SINGLE TRANSACTIONRESERVATION OF RIGHTS

[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, Integrated Circuit (IC) layout design, and / or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.TECHNICAL FIELD

[0002] The present disclosure relates generally to the field of telecommunication networks. More particularly, the present disclosure relates to a system and a method for retrieving multiple subscription data in a network through a single transaction.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] The term “consumer Network Function (NF)” used hereinafter in the specification refers to a functional entity in a Fifth Generation (5G) core network that provides services via standardized Service-Based Interfaces (SBIs). Consumer NFs include, for example, AMF, SMF, SMSF, GMLC, NEF, DDNMF, NWDAF, DCCF,and Trusted AF, each of which may interact with the UDM and UDR for subscription data retrieval.

[0005] The term “Unified Data Management (UDM)” used hereinafter in the specification refers to a network function that manages subscription data and provides services such as authentication, subscriber identification, and subscription data retrieval.

[0006] The term “Unified Data Repository (UDR)” used hereinafter in the specification refers to a network function that stores subscription data, policy data, and application data, and provides data storage and retrieval services to other network functions such as UDM, PCF, and NEF.

[0007] The term “Access and Mobility Management Function (AMF)” used hereinafter in the specification refers to a network function responsible for handling UE registration, connection management, mobility management, and access authentication.

[0008] The term “Session Management Function (SMF)” used hereinafter in the specification refers to a network function responsible for managing PDU sessions, including session establishment, modification, and release.

[0009] The term “Short Message Service Function (SMSF)” used hereinafter in the specification refers to a network function that provides SMS delivery services over 5G core networks and interacts with UDM to retrieve SMS -related subscription data.

[0010] The term “Network Exposure Function (NEF)” used hereinafter in the specification refers to a network function that exposes services and capabilities of the system securely to external applications.

[0011] The term “Network Data Analytics Function (NWDAF)” used hereinafter in the specification refers to a network function that collects data from other NFs and provides analytics services to support network optimization and policy decisions.

[0012] The term “Subscription Data” used hereinafter in the specification refers to subscriber-related data stored in the UDM / UDR, including but not limited to wherein the set of subscription data comprises session management subscription data, access and mobility subscription data, Short Message Service (SMS) management subscription data, SMS subscription data, Session Management Function (SMF) selection subscription data, user equipment (UE) context in SMF data, UE context in Short Message Service Function (SMSF) data, identifier translation data, slice selection subscription data, shared subscription data, trace data, Location Services (LCS) privacy data, LCS mobile originated data, enhanced coverage restriction data, Vehicle-to- Everything (V2X) subscription data, and LCS broadcast assistance subscription data.

[0013] The term “Session Management Subscription Data” refers to data required by the Session Management Function (SMF) to establish, maintain, and release Protocol Data Unit (PDU) sessions, including allowed Data Network Names (DNNs), subscribed Quality of Service (QoS) profiles, and Aggregate Maximum Bit Rate (AMBR) values.

[0014] The term “Access and Mobility Subscription Data” refers to data used by the AMF for registration, authentication, and mobility management, including roaming restrictions, permitted or barred Radio Access Technologies (RATs), and subscribed Network Slice Selection Assistance Information (NSSAI).

[0015] The term “Short Message Service (SMS) Subscription Data” refers to data that enables delivery and support of SMS services for a subscriber, including SMS over IP or SMS over NAS configurations.

[0016] The term “SMS Management Subscription Data” refers to data needed by the Short Message Service Function (SMSF) to manage SMS-related features such as barring, delivery restrictions, or limiting SMS services based on provisioned Generic Public Subscription Identifiers (GPSIs).

[0017] The term “Session Management Function (SMF) Selection Subscription Data” refers to subscription data required by the network to select an appropriate SMF instance for handling a subscriber’s PDU session, based on policies, slice selection, or access type.

[0018] The term “User Equipment (UE) Context in SMF Data” refers to subscription-related data that provides the SMF with the context of the UE, including active PDU sessions, allocated IP addresses, and session continuity parameters.

[0019] The term “UE Context in SMSF Data” refers to data required by the SMSF to maintain SMS -related session state and context of the subscriber.

[0020] The term “Identifier Translation Data” refers to data enabling mapping between different subscriber identifiers, such as Subscription Permanent Identifier (SUPI) to GPSI, GPSI to external identifier, or other translation forms.

[0021] The term “Slice Selection Subscription Data” refers to data defining subscribed Single-Network Slice Selection Assistance Information (S-NSSAIs) or mapping rules that enable allocation of the subscriber to one or more network slices.

[0022] The term “Shared Subscription Data” refers to subscription data shared by multiple subscribers or devices, for example, group subscriptions for enterprise loT devices.

[0023] The term “Trace Data” refers to data used for activation and configuration of trace sessions in the network to monitor subscriber activities for troubleshooting or lawful interception.

[0024] The term “Location Services (LCS) Privacy Data” refers to data controlling the use of subscriber location information, including privacy profiles and restrictions on how and when location may be shared.

[0025] The term “LCS Mobile Originated Data” refers to data supporting the initiation of location services by the subscriber’s device, including service permissions and supported LCS features.

[0026] The term “Enhanced Coverage Restriction Data” refers to subscription data restricting a subscriber from accessing enhanced coverage areas such as extended cell range or coverage enhancement modes.

[0027] The term “Vehicle-to-Everything (V2X) Subscription Data” refers to data enabling V2X communication services, including V2X application authorization, permitted communication modes, and resource allocations.

[0028] The term “LCS Broadcast Assistance Subscription Data” refers to subscription data supporting broadcast of assistance information for location services, enabling optimized location determination for subscribers.

[0029] The term “Data Network Name (DNN)” used hereinafter in the specification refers to an identifier of a data network, equivalent to an Access Point Name (APN) in EPC, and used during PDU session establishment.

[0030] The term “Subscription Permanent Identifier (SUPI)” used hereinafter in the specification refers to a globally unique identifier assigned to a subscriber in 5Gnetworks, typically in the form of an International Mobile Subscriber Identity (IMSI) or Network Access Identifier (NAI) for network authentication and management.

[0031] The term “Generic Public Subscription Identifier (GPSI)” used hereinafter in the specification refers to a publicly routable identifier that represents a subscriber in the network. The GPSI provides a means for external applications and service functions to address a subscriber without exposing the internal Subscription Permanent Identifier (SUPI).

[0032] The term “International Mobile Equipment Identity (IMEI)” used hereinafter in the specification refers to a unique identifier assigned to a mobile device, used by the network for equipment identification.

[0033] The term “Gateway Mobile Location Center (GMLC)” used hereinafter in the specification refers to a network function that provides location-based services and manages the location information of mobile devices.

[0034] The term “Direct Discovery Name Management Function (DDNMF) is a logical function handling network-related actions required for dynamic Proximity Services (ProSe) Direct Discovery.

[0035] The term “dynamic Proximity Services (ProSe) Direct Discovery” used hereinafter in the specification refers to a procedure that enables the UE to dynamically identify and discover other nearby UEs or ProSe-enabled devices without relying solely on network infrastructure. This discovery process allows UEs to exchange discovery information, such as identifiers or capabilities, in order to establish direct communication links for public safety, social applications, or localized services.

[0036] The term “Data Collection Coordination Function (DCCF)” used hereinafter in the specification refers to a network function that coordinates thecollection of data from various data sources and distributes it to analytics consumers such as the Network Data Analytics Function (NWDAF).

[0037] The term “Trusted Application Function (Trusted AF)” used hereinafter in the specification refers to a network function that ensures the security and trustworthiness of applications interacting with the network.

[0038] The term “Get Service operation” used hereinafter in the specification refers to a structured communication sent by the customer NF to request a specific set of subscription data from the UDM or UDR.

[0039] The term “Network Slice Selection Assistance Information (NSSAI)” used hereinafter in the specification 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.

[0040] The term “Information Element (IE)” used hereinafter in the specification is a structured unit of data used in communication protocols to convey specific pieces of information within messages.

[0041] The term “Data Network (DN)” used hereinafter in the specification refers to a type of network that provides connectivity to various data services, enabling users to access internet services and applications.

[0042] The term “Service-Based Interface (SBI)” is a type of network interface that enables communication between network functions using standardized servicebased communication protocols.

[0043] The term “Radio Access Technology (RAT) type” refers to a specific technology standard used for wireless communication between mobile devices and thenetwork, such as Long-Term Evolution (LIE), New Radio (NR) (5G), or Global System for Mobile Communications (GSM).

[0044] The term “Uniform Resource Identifier (URI)” refers to an identifier that uniquely identifies a specific resource or endpoint within a system or application. The resource URI may be a web page, a file, a database record, or any other digital asset.

[0045] The term “Nudm_Subscriber Data Management service” or “Nudm_SDM service” used hereinafter in the specification refers to a standardized service-based interface (SBI), which enables consumer NFs such as AMF, SMF, SMSF, NEF, and others to access, retrieve, and manage subscription-related data stored in the UDM. The Nudm_SDM service provides operations for retrieving, updating, and subscribing to changes in subscription data, thereby ensuring that NFs obtain consistent and up-to-date information required for handling mobility, session management, policy enforcement, and service delivery.

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

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

[0048] In modern network architectures, particularly within Fifth Generation (5G) and Sixth Generation (6G) networks, various Network Functions (NFs) are essential for supporting various aspects of network management, service delivery, anduser experience. The NFs are designed to handle specific tasks such as session management, data routing, and user authentication. By decomposing network operations into discrete functions, organizations can achieve greater flexibility, scalability, and efficiency in managing their networks. The NFs interact with the Unified Data Management (UDM) to retrieve and manage subscriber-related data. These NFs include Application 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), among others.

[0049] To access the subscriber data pertinent to the operations, the consumer NFs utilize the Get Service operation of the Service Nudm Subscriber Data Management interface. This operation allows the consumer NFs to retrieve specific subscription information stored in the UDM. For instance, the AMF may need to access subscription details to manage sessions effectively, while the NEF may require such data for exposure control and analytics.

[0050] Currently, each NF that requires different sets of subscription data must make separate Application Programming Interface (API) calls corresponding to each type of subscription data. For example, if the SMSF needs to retrieve SMS subscription data, SMS management data, and perform identifier translation, it must initiate three distinct Get Service operations. This results in multiple transactions between the NF and UDM, which is not only resource-intensive but also adds latency to the system, as each request requires separate processing. Further, the need to make multiple transactions increases the load on both the NF and UDM, leading to potential inefficiencies in the network performance. It also creates a risk of data inconsistency ifdifferent requests are processed at different times or if there is a failure in any of the transactions.

[0051] Therefore, there is a need for a system and a method that overcomes the limitations of the prior art.OBJECTIVES OF THE PRESENT DISCLOSURE

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

[0053] An objective of the present disclosure is to provide a system and a method for retrieving multiple subscription data in a network through a single transaction.

[0054] Another objective 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.

[0055] Another objective of the present disclosure is to minimize the latency and processing time associated with retrieving the set of subscription data by combining multiple requests into a single transaction.

[0056] Yet another objective of the present disclosure is to decrease the computational load on both the customer NFs and the UDM, thereby enhancing the efficiency and performance of the network.

[0057] Other objects and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.SUMMARY

[0058] In an exemplary embodiment, a method for retrieving multiple subscription data in a network in a single transaction is disclosed. The method includes receiving, by a unified data management (UDM), a combined data retrieval request from a network function (NF). The combined data retrieval request corresponds to retrieval of a set of subscription data in the single transaction. The method includes determining, by the UDM, whether at least one type of subscription data in the set of subscription data is available in the UDM based on the received combined data retrieval request. Upon determining if the at least one type of subscription data from the set of subscription data is not available, the method includes transmitting, by the UDM, a data query request towards a unified data repository (UDR), The data query request corresponds to retrieval of the at least one type of subscription data from the UDR. The method includes receiving, by the UDM, a response corresponding to the transmitted data query request from the UDR. The response includes the at least one type of subscription data. The method includes sending, by the UDM, a consolidated response, corresponding to the combined data retrieval request, to the NF. The consolidated response includes one or more another type of the subscription data available in the UDM and the at least one type of subscription data retrieved from the UDR.

[0059] In some embodiments, the set of subscription data comprises session management subscription data, access and mobility subscription data, Short Message Service (SMS) management subscription data, SMS subscription data, Session Management Function (SMF) selection subscription data, user equipment (UE) context in SMF data, UE context in Short Message Service Function (SMSF) data, identifier translation data, slice selection subscription data, shared subscription data, trace data, Location Services (LCS) privacy data, LCS mobile originated data, enhanced coverage restriction data, Vehicle-to-Everything (V2X) subscription data, and LCS broadcast assistance subscription data.

[0060] In some embodiments, the receiving unit receives at least one user input from a user for modifying the at least one determined configuration change.

[0061] In some embodiments, upon receiving the response from the UDR, combining, by the UDM, the at least one type of subscription data received from the UDR and the one or more another type of subscription data from the set of subscription data available in the UDM to create the consolidated response.

[0062] In some embodiments, upon determining that the one or more another type of the subscription data and the at least one type of subscription data from the set of subscription data are available in the UDM, transmitting, by the UDM, the set of subscription data to the NF in the single transaction.

[0063] In some embodiments, the combined data retrieval request includes one or more filtering criteria associated with the set of subscription data, and the set of subscription data is retrieved from the UDM based on the one or more filtering criteria.

[0064] In some embodiments, the one or more filtering criteria includes one of Radio Access Technology (RAT) type, International Mobile Equipment Identity (IMEI), group ID, Network Slice Selection Assistance Information (NSSAI), Data Network Name (DNN), access type, supported features, Subscription Permanent Identifier (SUPI), and Mobile Equipment Identifier (MEID).

[0065] In some embodiments, the consolidated response further includes at least one of: a positive response indicating successful retrieval of the set of subscription data, and a negative response indicating a failure in the retrieval of the at least one type of subscription data from the set of subscription data. The negative response also includes a detailed problem description.

[0066] In another exemplary embodiment, a system for retrieving multiple subscription data in a network in a single transaction is disclosed. The system includesa unified data management (UDM) configured to receive a combined data retrieval request from a network function (NF). The combined data retrieval request corresponds to retrieval of a set of subscription data in the single transaction. The UDM is configured to determine whether at least one type of subscription data in the set of subscription data is available in the UDM based on the received combined data retrieval request. Upon determining if the at least one type of subscription data from the set of subscription data is not available, the UDM is configured to transmit a data query request towards a unified data repository (UDR), the data query request corresponds to retrieval of the at least one type of subscription data from the UDR. The UDM is configured to receive a response corresponding to the transmitted data query request from the UDR, the response comprises the at least one type of subscription data. The UDM is configured to send a consolidated response, corresponding to the data retrieval request, to the NF. The consolidated response includes one or more another type of the subscription data available in the UDM and the at least one type of subscription data retrieved from the UDR.

[0067] In yet another exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium is disclosed. The medium includes instructions that, when executed by one or more processors, cause the one or more processors to execute a method for retrieving multiple subscription data in a network in a single transaction. The method includes receiving, by a unified data management (UDM), a combined data retrieval request from a network function (NF). The combined data retrieval request corresponds to retrieval of a set of subscription data in the single transaction. The method includes determining, by the UDM, whether at least one type of subscription data in the set of subscription data is available in the UDM based on the received combined data retrieval request. Upon determining if the at least one type of subscription data from the set of subscription data is not available, the method includes transmitting, by the UDM, a data query request towards a unified data repository (UDR), The data query request corresponds to retrieval of the at leastone type of subscription data from the UDR. The method includes receiving, by the UDM, a response corresponding to the transmitted data query request from the UDR. The response includes the at least one type of subscription data. The method includes sending, by the UDM, a consolidated response, corresponding to the combined data retrieval request, to the NF. The consolidated response includes one or more another type of the subscription data available in the UDM and the at least one type of subscription data retrieved from the UDR.

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

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

[0070] FIG. 1 illustrates an exemplary network architecture for retrieving multiple subscription data in a network through a single transaction, in accordance with an embodiment of the present disclosure.

[0071] FIG. 2 illustrates a block diagram of the system, in accordance with an embodiment of the present disclosure.

[0072] FIG. 3 illustrates an exemplary flow diagram of a method for retrieving multiple subscription data in the network through the single transaction, in accordance with an embodiment of the present disclosure.

[0073] FIG. 4 illustrates another exemplary flow diagram of a method for retrieving multiple subscription data in the network through the single transaction, in accordance with an embodiment of the present disclosure.

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

[0075] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network architecture102-1, 102-2... 102-N - A plurality of users104-1, 104-2... 104-N - User Equipments (UEs)106 - Network108 - System200 - Block diagram202 - Processor204 - Memory206 - Interface(s)208, 304 - Unified Data Management (UDM)210, 306 - Unified Data Repository (UDR)212 - Database300, 400 - Method302 - Consumer Network Function (NF)500 - Computing system510 - External Storage Device520 - Bus530 - Main Memory540 - Read Only Memory550 - Mass Storage Device560 - Communication Port570 - ProcessorDETAILED DESCRIPTION

[0076] 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 of the features described herein. Example embodiments of the present disclosure aredescribed below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.

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

[0078] 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 in order to avoid obscuring the embodiments.

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

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

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

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

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

[0084] Wireless communication technology has rapidly evolved over the past few decades. The first generation of wireless communication technology was analog, offering only voice services. Further, text messaging and data services became possible when the second-generation (2G) technology was introduced. The third generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized wireless communication with faster data speeds, improved network coverage, and security. Currently, fifth-generation (5G) technology is being deployed, offering significantly faster data speeds, lower latency, and the ability to connect many devices simultaneously. These advancements represent a significant leap forward from previous generations, enabling enhanced mobile broadband, improved Internet ofThings (loT) connectivity, and more efficient use of network resources. The sixth generation (6G) technology promises to build upon these advancements, pushing the boundaries of wireless communication even further. While the 5G technology is still being rolled out globally, research and development into the 6G are rapidly progressing, with the aim of revolutionizing the way to connect and interact with technology.

[0085] In modern network management systems, particularly within 5G and emerging 6G core network systems, the efficiency of data management and transaction handling is crucial for maintaining optimal network performance and minimizing operational complexities. Conventional approaches for data retrieval in network management systems often require multiple transactions for obtaining different sets of subscriber data, leading to increased network load, higher latency, and reduced system efficiency. These conventional approaches involve separate Application Programming Interface (API) calls for each type of data request, which may create unnecessary overhead on both the consumer Network Functions (NFs) and the data management systems, such as a Unified Data Management (UDM) and Unified Data Repository (UDR). This may result in greater processing time, increased chances of errors, and challenges in maintaining data consistency across the network. Thus, there is a need for a system and a method that may mitigate the disadvantages of the prior art.

[0086] The present disclosure addresses these inefficiencies by combining multiple subscription data retrieval operations into a single, unified transaction. The single transaction means that instead of sending multiple requests (e.g., GET requests), the consumer NF may send one combined request that specifies all the types of data it needs. The UDM processes this single request, retrieves the required data (either directly or via communication with the UDR if necessary), and returns all the requested data in a single response. By combining various procedures conventionally handled through separate transactions into one integrated request, the present disclosure reducesthe number of interactions required between consumer NFs and the UDM system. This integration not only improves the data retrieval process but also enhances overall network performance by reducing transaction overhead, improving resource utilization, and lowering system latency.

[0087] According to one embodiment of the present disclosure, a new procedure, referred to as “Combined Subscription Data Retrieval” is introduced. This procedure allows consumer NFs to request multiple sets of subscription data, which may include Session Management Subscription Data, Access and Mobility Subscription Data, SMS Management Data, Identifier Translation, and the like, within a single transaction. The UDM processes this unified request, retrieving the required data directly if available, or querying the UDR when additional data retrieval is necessary. This approach minimizes the need for multiple API calls, thereby reducing the load on the NF Consumer, the UDM and the UDR and improving the overall efficiency of the network management system.

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

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

[0090] FIG. 1 illustrates an exemplary network architecture (100) for retrieving multiple subscription data in a network through a single transaction, in accordance with an embodiment of the present disclosure.

[0091] As illustrated in FIG. 1, the network architecture (100) may include one or more user equipments (UEs) (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 be individually referred to as the user (102) and collectively referred to as the users (102). Similarly, aperson of ordinary skill in the art will understand that 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). Although three UEs (104) are depicted in FIG. 1, however, any number of the UEs (104) may be included without departing from the scope of the ongoing description.

[0092] In an embodiment, the UE (104) may include smart devices operating in a smart environment, for example, an Internet of Things (loT) system. In such an embodiment, the UE (104) may include, but is not limited to, 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.

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

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

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

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

[0097] In an embodiment, the system (108) may be configured to retrieve multiple subscription data in a network in a single transaction. The system (108) includes the UDM. The UDM is configured to receive a combined data retrieval request from the NF. The combined data retrieval request corresponds to retrieval of a set of subscription data in the single transaction. The UDM is configured to determine whether at least one type of subscription data in the set of subscription data is available in the UDM based on the received combined data retrieval request. Upon determining if the at least one type of subscription data from the set of subscription data is not available, the UDM is configured to transmit a data query request towards a unified data repository (UDR), the data query request corresponds to retrieval of the at least one type of subscription data from the UDR. The UDM is configured to receive a response corresponding to the transmitted data query request from the UDR, the response comprises the at least one type of subscription data. The UDM is configured to send a consolidated response, corresponding to the data retrieval request, to the NF. The consolidated response includes one or more another type of the subscription data available in the UDM and the at least one type of subscription data retrieved from the UDR.

[0098] Although FIG. 1 shows exemplary components of the network architecture (100), in other embodiments, the network architecture (100) may includefewer 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).

[0099] FIG. 2 illustrates a block diagram (200) of the system (108) in accordance with an embodiment of the present disclosure. The system (108) may be configured to retrieve multiple subscription data through a single transaction.[000100] In an aspect, the system (108) may include one or more processor(s) (202). The one or more processor(s) (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, edge or fog microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that process data based on operational instructions. Among other capabilities, one or more processor(s) (202) may be configured to fetch and execute computer-readable instructions stored in a memory (204) of the system (108). The memory (204) may be configured to store one or more computer-readable instructions or routines in a non- transitory computer-readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (204) may include any non-transitory storage 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.[000101] The one or more processor(s) (202) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the one or more processor(s) (202). In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the one or more processor(s) (202) may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the one or more processor(s) (202) may include a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine- readable storage medium may store instructions that, when executed by the processing resource, implement the one or more processor(s) (202). In such examples, the system (108) may include the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system (108) and the processing resource. In other examples, the one or more processor(s) (202) may be implemented by an electronic circuitry.[000102] In an embodiment, the system (108) may include an interface(s) (206). The interface(s) (206) may include a variety of interfaces, for example, interfaces for data input and output devices, referred to as I / O devices, storage devices, and the like. The interface(s) (206) may facilitate communication of the system (108). The interface(s) (206) may also provide a communication pathway for one or more components of the system (108). Examples of such components include, but are not limited to, a UDM (208), a UDR (210) and a database (212). In an embodiment, the database (212) includes data that may be either stored or generated as a result of functionalities implemented by any of the components of the one or more processor(s) (202).[000103] The UDM (208) may be configured to receive a combined data retrieval request from a network function (NF) (e.g., a consumer NF). In an embodiment, the combined data retrieval request corresponds to the retrieval of a set of subscription data in the single transaction. Examples of consumer NF may include, but are not limited to, Access and Mobility Management Function (AMF), Session Management Function (SMF), Short Message Service Function (SMSF), Gateway Mobile Location Centre (GMLC), Network Exposure Function (NEF), Direct Discovery Name ManagementFunction (DDNMF), Network Data Analytics Function (NWDAF), Data Collection Coordination Function (DCCF), and Trusted AF. In an embodiment, the set of subscription data may include, but is not limited to, session management subscription data, access and mobility subscription data, Short Message Service (SMS) management subscription data, SMS subscription data, Session Management Function (SMF) selection subscription data, user equipment (UE) context in SMF data, UE context in Short Message Service Function (SMSF) data, identifier translation data, slice selection subscription data, shared subscription data, trace data, Location Services (LCS) privacy data, LCS mobile originated data, enhanced coverage restriction data, Vehicle-to- Everything (V2X) subscription data, and LCS broadcast assistance subscription data.[000104] In an embodiment, to retrieve multiple subscription data (or multiple types of subscription data) in the network (106) from the UDM (208) through a single transaction, the consumer NF identifies that it requires access to more than one type of subscription data stored within the UDM (208) or the UDR (210). For example, consider a scenario where a consumer NF may simultaneously require access and mobility subscription data for user registration, session management subscription data for establishing a PDU session, and SMS subscription data for enabling short message delivery for the same subscriber. Conventionally, such requirements are fulfilled through multiple independent retrieval requests, each targeting a specific type of subscription data, thereby creating additional signaling overhead and processing load on both the consumer NF and the UDM (208).[000105] To address inefficiency of conventional systems, the UDM (208) may be configured to receive and process a combined data retrieval request (e.g., a “Combined Subscription Data Retrieval” request). In an embodiment, the combined data retrieval request consolidates two or more individual requests (such as GET requests for session management subscription data, access and mobility subscription data, Short Message Service (SMS) management subscription data, SMS subscriptiondata, Session Management Function (SMF) selection subscription data, user equipment (UE) context in SMF data, UE context in Short Message Service Function (SMSF) data, identifier translation data, slice selection subscription data, shared subscription data, trace data, Location Services (LCS) privacy data, LCS mobile originated data, enhanced coverage restriction data, Vehicle-to-Everything (V2X) subscription data, or LCS broadcast assistance subscription data) into a single unified request message.[000106] In an embodiment, the session management subscription data refers to data required by the SMF to establish, maintain, and release Protocol Data Unit (PDU) sessions, including allowed Data Network Names (DNNs), subscribed Quality of Service (QoS) profiles, and Aggregate Maximum Bit Rate (AMBR) values. The access and mobility subscription data refers to data used by the AMF for registration, authentication, and mobility management, including roaming restrictions, permitted or barred Radio Access Technologies (RATs), and subscribed Network Slice Selection Assistance Information (NSSAI). The SMS subscription data refers to data that enables delivery and support of SMS services for a subscriber, including SMS over IP or SMS over NAS configurations. The SMS management subscription data refers to data needed by the SMSF to manage SMS -related features such as barring, delivery restrictions, or limiting SMS services based on provisioned Generic Public Subscription Identifiers (GPSIs). The SMF selection subscription data refers to subscription data required by the network to select an appropriate SMF instance for handling a subscriber’s PDU session, based on policies, slice selection, or access type. The UE Context in SMF data refers to subscription-related data that provides the SMF with the context of the UE, including active PDU sessions, allocated IP addresses, and session continuity parameters. The UE Context in SMSF data refers to data required by the SMSF to maintain SMS -related session state and context of the subscriber.[000107] Further, the identifier translation data refers to data enabling mapping between different subscriber identifiers, such as Subscription Permanent Identifier(SUPI) to Generic Public Subscription Identifier (GPSI), GPSI to external identifier, or other translation forms. The slice selection subscription data refers to data defining subscribed Single-Network Slice Selection Assistance Information (S-NSSAIs) or mapping rules that enable allocation of the subscriber to one or more network slices. The shared subscription data refers to subscription data shared by multiple subscribers or devices, for example, group subscriptions for enterprise loT devices. The trace data refers to data used for activation and configuration of trace sessions in the network to monitor subscriber activities for troubleshooting or lawful interception. The LCS privacy data refers to data controlling the use of subscriber location information, including privacy profiles and restrictions on how and when location may be shared. The LCS mobile originated data refers to data supporting the initiation of location services by the subscriber’s device, including service permissions and supported LCS features. The enhanced coverage restriction data refers to subscription data restricting a subscriber from accessing enhanced coverage areas such as extended cell range or coverage enhancement modes. The V2X subscription data refers to data enabling V2X communication services, including V2X application authorization, permitted communication modes, and resource allocations. Additionally, the LCS broadcast assistance subscription data refers to subscription data supporting broadcast of assistance information for location services, enabling optimized location determination for subscribers.[000108] Upon receiving the combined data retrieval request, the UDM (208) interprets this request to identify the set of subscription data required by the consumer NF. This enables the UDM (208) to process the request as a single transaction, thereby avoiding the need for the consumer NF to send multiple independent GET requests and eliminating redundant communication exchanges.[000109] In an embodiment, the combined data retrieval request includes one or more filtering criteria associated with the set of subscription data. The set ofsubscription data is retrieved from the UDM (208) based on the one or more filtering criteria. The one or more filtering criteria serve to refine or limit the scope of subscription data retrieved from the UDM (208), ensuring that only data relevant to the requesting NF and the subscriber context is provided in the consolidated response. The one or more filtering criteria includes one of Radio Access Technology (RAT) type, International Mobile Equipment Identity (IMEI), group ID, Network Slice Selection Assistance Information (NSSAI), Data Network Name (DNN), access type, supported features, Subscription Permanent Identifier (SUPI), and Mobile Equipment Identifier (MEID).[000110] In an embodiment, the RAT type specifies whether the subscription data is requested in relation to LTE, 5G New Radio (NR), GSM, or any other supported RAT. Further, the IMEI identifies the subscriber device and may be used to filter subscription data relevant to a particular terminal. Further, the group ID allows the retrieval of subscription data associated with a specific subscriber group or enterprise. Further, the NSSAI may be used to filter data applicable to a subscribed slice or set of slices. Further, the DNN identifies the target data network, such as an internet APN or enterprise VPN, for which subscription information is required. Further, the access type distinguishes between cellular access and non-cellular access (e.g., Wi-Fi). Further, the supported features may indicate capabilities or features provisioned for the subscriber, which may be included as an optional element of type ‘Supported Features’ with a cardinality of 0..1, indicating the features supported for the transaction (e.g., whether GPSI inclusion is supported in the consolidated response). Further, the SUPI uniquely identifies the subscriber and may serve as the primary filtering criterion for retrieving the associated subscription data. Further, the MEID provides another device-specific filter similar to IMEI, particularly applicable in certain deployments.[000111] By way of example, consider a scenario in which a consumer NF, such as an AMF, requires both access and mobility subscription data and sessionmanagement subscription data for a subscriber connected over a 5G New Radio (NR) RAT. The combined data retrieval request generated by the AMF may include a filtering criterion specifying the RAT type = 5G NR and the Subscription Permanent Identifier (SUPI) corresponding to the subscriber. Based on this request, the UDM (208) retrieves access and mobility subscription data indicating roaming restrictions applicable only to 5G NR, along with session management subscription data identifying the allowed Data Network Names (DNNs) and subscribed quality of service (QoS) profiles for the subscriber.[000112] In another example, the consumer NF may be an SMSF that requires SMS management subscription data and identifier translation data for the purpose of barring or limiting SMS delivery. In this case, the combined data retrieval request may include the SUPI of the subscriber and a filtering criterion based on a provisioned Generic Public Subscription Identifier (GPSI). The UDM (208), upon processing the request, retrieves the SMS management subscription data along with the GPSI mapping from the identifier translation data and consolidates them into a single response. Similarly, a DNN-based filtering criterion may be used by an SMF to retrieve only those subscription parameters that are relevant to a specific enterprise VPN identified by a DNN, rather than retrieving all subscription data provisioned for the subscriber. In each of these scenarios, the use of filtering criteria ensures that the UDM (208) provides only the relevant subset of subscription data in the consolidated response, thereby reducing signaling overhead and improving efficiency.[000113] Based on the received combined data retrieval request, the UDM (208) determines whether at least one type of subscription data in the set of subscription data is available in the UDM (208). In an embodiment, the at least one type of subscription data may refer to different categories of subscriber-related data that are not available in the UDM (208) and can be retrieved from the UDR (210).[000114] By way of example, the at least one type of subscription data may include, but is not limited to, a session management type subscription data, access and mobility type subscription data, short message service management type subscription data, SMS subscription type data, SMF selection type subscription data, UE context in SMF type data, UE context in SMSF type data, identifier translation type data, slice selection subscription type data, shared subscription type data, trace type data, LCS privacy type data, LCS mobile originated type data, enhanced coverage restriction type data, V2X type subscription data, and LCS broadcast assistance type subscription data.[000115] In an embodiment, the session management type subscription data may include parameters required by the SMF for establishing and maintaining Protocol Data Unit (PDU) sessions of a subscriber, such as allowed Data Network Names (DNNs), subscribed quality of service (QoS) profiles, or Aggregate Maximum Bit Rate (AMBR) values. In an embodiment, the access and mobility subscription type data may include information required by the AMF for handling subscriber registration, authentication, and mobility, such as roaming restrictions, allowed or restricted Radio Access Technologies (RATs), or subscribed NSSAI. Further, the SMS subscription type data may include subscription-related parameters enabling or restricting SMS delivery services for a subscriber, including support for SMS over IP or SMS over NAS. The SMF selection type subscription data may define policies or rules that assist the network in choosing an appropriate SMF instance for a subscriber, based on factors such as slice information, access type, or supported features. Further, the UE context in SMF type subscription data may capture session-specific context of the UE, such as ongoing PDU sessions, IP address allocations, and continuity rules, while the UE context in SMSF type subscription data may capture active SMS sessions, state information, and routing data needed by the SMSF.[000116] In an embodiment, the short message service management type subscription data may include information needed by the SMSF for supporting deliveryof SMS services, such as indication of whether SMS over NAS is supported, or information relating to barring or limitation of SMS delivery based on provisioned Generic Public Subscription Identifiers (GPSIs). The identifier translation type data may include mapping between different subscriber identifiers, such as a mapping of a Subscription Permanent Identifier (SUPI) to one or more GPSIs. The GPSIs may correspond to a Mobile Station International Subscriber Directory Number (MSISDN) or one or more external identifiers. The GPSI is used for addressing purposes in service delivery, such as for routing Short Message Service (SMS) messages, establishing data sessions, or applying barring and charging policies. The UDM and UDR maintain mappings between the SUPI and one or more GPSIs of a subscriber, enabling identifier translation for efficient and secure subscriber management. The SUPI is used for identifying and authenticating a subscriber within the network. The SUPI may be represented as an International Mobile Subscriber Identity (IMSI) in legacy interworking scenarios, or it may be based on a Network Access Identifier (NAI) format in purely 5G deployments. The SUPI is internally mapped by the UDM and UDR to the one or more GPSIs, such as the MSISDN or an external identifier, for service delivery and identifier translation purposes. Similarly, the slice selection type subscription data may include subscribed Single Network Slice Selection Assistance Information (S-NSSAIs) or mapping rules to facilitate allocation of the subscriber to an appropriate network slice. The term “S-NSSAI” is a structured identifier that consists of a Slice / Service Type (SST) and, optionally, a Slice Differentiator (SD). The S-NSSAI uniquely identifies a specific network slice that provides a set of services and resources to a subscriber. By leveraging S-NSSAIs, the UDM may ensure that a subscriber is allocated to the appropriate network slice that meets their service requirements (e.g., enhanced mobile broadband, ultra-reliable low- latency communication, or massive machine-type communication).[000117] Further, the shared subscription type data may include information common to a group of subscribers, such as enterprise loT device subscriptions. Thetrace type subscription data may include information required for activating and configuring trace sessions for monitoring subscriber activities. The LCS privacy type subscription data may include privacy profiles controlling the use and disclosure of subscriber location. The LCS mobile originated type subscription data may include service permissions and supported features for subscriber-initiated location services. The enhanced coverage restriction type subscription data may restrict a subscriber from accessing enhanced coverage modes, such as extended cell range or coverage enhancement. The V2X subscription type data may define the parameters required for enabling V2X services, such as allowed communication modes and resource allocations. Further, the LCS broadcast assistance type subscription data may include broadcast assistance information for enabling or optimizing location determination of the subscriber device.[000118] Upon determining that at least one type of subscription data from the set of subscription data is not available within the UDM (208), the UDM (208) is configured to transmit a data query request towards the UDR (210). The data query request corresponds to a retrieval of the at least one type of subscription data from the UDR (210). In this manner, the UDM (208) ensures that the subscriber-related information, even if not locally stored, may be dynamically retrieved from the backend repository (e.g., UDR 210) to complete the combined subscription data retrieval process.[000119] The UDM (208) receives a response corresponding to the transmitted data query request from the UDR (210). The response includes the at least one type of subscription data. Upon receiving the response from the UDR (210), the UDM (208) combines the at least one type of subscription data received from the UDR (210) and one or more another type of subscription data from the set of subscription data available in the UDM (208) to create the consolidated response.[000120] In an embodiment, the one or more another type of the subscription data may refer to any type of subscription data that is locally available in the UDM (208), apart from the at least one type of subscription data that is retrieved from the UDR (210). For example, if the UDM (208) receives a combined data retrieval request from an AMF that requires both access and mobility subscription data and session management subscription data, and only the session management subscription data is available locally in the UDM (208), then the UDM (208) retrieves the access and mobility subscription data from the UDR (210) while utilizing the locally available session management subscription data. In another example, if the UDM (208) receives a request from an SMSF requiring SMS management subscription data along with identifier translation data, and the SMS management subscription data is already present in the UDM (208), then only the identifier translation data is queried from the UDR (210), while the SMS management subscription data is provided from the local repository of the UDM (208). Similarly, in case an SMF requests both session management subscription data and Data Network Name (DNN) subscription data, the UDM (208) may determine that the DNN subscription data is already locally provisioned while session management subscription data needs to be retrieved from the UDR (210). In each of these instances, the consolidated response generated by the UDM (208) incorporates both the subscription data retrieved from the UDR (210) and the one or more another type of subscription data available locally, thereby avoiding redundant queries to the UDR (210) and reducing signaling overhead.[000121] Upon creating the consolidated response, the UDM (208) sends the consolidated response, corresponding to the combined data retrieval request, to the NF. In an embodiment, the consolidated response includes the one or more another type of the subscription data available in the UDM (208) and the at least one type of subscription data retrieved from the UDR (210).[000122] In some embodiments, upon determining that the one or more another type of the subscription data and the at least one type of subscription data from the set of subscription data are available in the UDM (208), the UDM (208) directly transmits the set of subscription data to the NF in the single transaction without involving or querying the UDR (210). In an embodiment, the UDM (208) locates the requested types of subscription data in its local store (e.g., an internal repository or cache), applies any filtering criteria or supported-feature indications carried in the combined request, and assembles the selected data into a single, unified payload. The unified payload is generated so as to preserve the logical separation of each type of subscription data (e.g., session management type subscription data, access and mobility type subscription data, SMS management type subscription data, identifier translation type data, network slice selection assistance type information, and data network name subscription data), while allowing delivery in a single response message.[000123] In one example, the combined data retrieval request specifies a set comprising session management type subscription data and data network name type subscription data. If both types of subscription data are available locally at the UDM (208), the UDM (208) selects the relevant records, honors any request-scoped filters (e.g., RAT type, NSSAI, DNN, SUPI), and generates a consolidated response that includes each requested type as separate objects within the single response. In another example, the set comprises access and mobility type subscription data, SMS management type subscription data, and identifier translation type data; when all three are available locally, the UDM (208) aggregates these into the consolidated response without initiating any backend transaction towards the UDR (210).[000124] In an embodiment, the consolidated response further includes at least one of a positive response and a negative response. The positive response indicates successful retrieval of the entire set of subscription data, including both the subscription data available locally in the UDM (208) and the subscription data retrieved from theUDR (210). For example, if an SMF requests both session management subscription data and DNN subscription data, and the UDM (208) successfully retrieves the session management subscription data from the UDR (210) and combines it with the locally available DNN subscription data, the consolidated response returned to the SMF contains a positive response indication.[000125] In an alternative embodiment, the consolidated response may include the negative response indicating a failure in the retrieval of at least one type of subscription data from the set of subscription data. For instance, if the UDM (208) fails to obtain access and mobility subscription data from the UDR (210) due to unavailability or query timeout, the consolidated response returned to the requesting NF (e.g., AMF) contains a negative response. The negative response may also include a detailed problem description, such as “subscription data not found,” “data retrieval timeout,” or “unsupported query parameters.” The inclusion of such a problem description allows the requesting NF to identify the cause of the failure and to take appropriate remedial actions, such as re-trying the request, switching to alternate subscription parameters, or notifying higher-layer applications.[000126] Although FIG. 2 shows an exemplary block diagram (200) of the system (108), in other embodiments, the system (108) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 2. Additionally, or alternatively, one or more components of the system (108) may perform functions described as being performed by one or more other components of the system (108).[000127] FIG. 3 illustrates an exemplary flow diagram of a method (300) for retrieving multiple subscription data in the network through a single transaction in accordance with an embodiment of the disclosure. The method (300) involves interactions between a consumer Network Function (NF) (302), a UDM (304), and a UDR (306).[000128] At step 308, the consumer NF (302) initiates the process by transmitting a request using a “Nudm_SubscriberDataManagement_Get” service operation, which includes a list of procedure names. These procedure names correspond to the specific subscription data that the consumer NF (302) seeks to retrieve from the UDM (304) and the UDR (306). The list of procedure names may include, but is not limited to, session management subscription data, access and mobility subscription data, SMS management data, identifier translation data, NS SAI subscription data, and DNN subscription data.[000129] In an embodiment, rather than multiple separate transactions per procedure (e g., for the Get Service Operation “Nudm_SubscriberDataManagement_Get), consumer NF (302) may use a single transaction for getting subscriber data for multiple procedures from the UDM (304). The UDM (304) may also use the single transaction to query multiple procedure data from the UDR (306) in the single transaction.[000130] The request may be a procedure request message, for example, “Combined Subscription Data Retrieval” request that is transmitted in a predefined format and may include various filtering criteria based on the procedures requested. This request message is used by the consumer NF (302) to request multiple sets of subscription data for each procedure in a single transaction. The filtering criteria may include, but are not limited to, a RAT type, an IMEI, a group ID, a NS SAI, a DNN, an access type, supported features (AM data / SM data), and SUPI.[000131] Upon receiving the request, the UDM (304) processes the request message and determines the necessary procedures related to subscription data that need to be executed to fulfil the request.[000132] At step 310, if the required set of subscription data is not readily available within the UDM (304), it forwards the request message to the UDR (306) via“Nudr_DM_Query” to retrieve the set of subscription data associated with the requested procedures. The UDR (306) processes the Nudr DM Query request and compiles the required set of subscription data based on the procedures specified.[000133] At step 312, the UDR (306) then sends a response back to the UDM (304), containing the requested subscription data. Once the UDM (304) receives the response from the UDR (306), it combines the required subscription data and sends the response back to the consumer NF (302), at step 314. This response includes the results for each requested procedure. The consumer NF (302) then processes the procedure results received from the UDM (304).[000134] In an embodiment, it is required that both the UDM (304) and UDR (306) are equipped to support the procedure termed as “Combined Subscription Data Retrieval”. In an embodiment, this procedure is defined by the inclusion of a dedicated resource URI structure. Specifically, the resource URI may be formatted as “{apiroot} / nudm-sdm / v2 / comboprocedure”. Here, “{apiroot}” represents the base address of the UDM service instance, while “nudm-sdm / v2” refers to the versioned Nudm SubscriberDataManagement service. The suffix “comboprocedure” uniquely identifies the endpoint dedicated to initiating and handling the combined data retrieval process. The significance of this URI is that it provides a standardized, discoverable, and machine-readable entry point for consumer NFs (e.g., AMF, SMF, SMSF) to invoke the combined retrieval procedure. This allows different subscription data types to be requested in a single transaction over the service-based interface (SBI), thereby improving interoperability across vendor implementations, and reducing signaling overhead compared to multiple individual requests.[000135] The JavaScript Object Notation (JSON) body of the message sent to this endpoint may include specific Information Elements (IES) to effectively communicate the request and criteria for the data retrieval. The required IEs are as follows:• mSupi: A conditional element represented as an array of type supi, with a cardinality of 0..1, used to specify the Subscriber Permanent Identifier;• mUeid: A conditional element represented as an array of type VarUeld, with a cardinality of 0..1, used to identify the User Equipment;• shared-data-ids: A conditional element represented as an array of type SharedDatald, with a cardinality of 0..1, specifying shared data identifiers;• ext-group-id: A conditional element of type ExtGroupId, with a cardinality of 0..1, representing external group identifiers;• int-group-id: A conditional element of type Groupld, with a cardinality of 0..1, representing internal group identifiers;• supported-features: An optional element of type SupportedFeatures, with a cardinality of 0..1, indicating the supported features for this transaction; and• procedureNames: A mandatory element represented as an array of type ProcedureName, with a cardinality of 1. This element lists the procedures supported by the UDM and the UDR, which are to be retrieved in the combined transaction.[000136] In an embodiment, each procedure name listed in the “procedureNames” IE triggers the inclusion of corresponding sub-objects, which are grouped into separate IES for each procedure. For example, when “nssai procedure” is listed, an IE named “queryParamNssaiProc” is included, containing query parameters specific to the NSSAI procedure. Similar IEs are defined for all procedures requiring support within the combined procedure framework. The “queryParamNssaiProc” IE carries query parameters specific to the NSSAI procedure, such as the requested Single Network Slice Selection Assistance Information (S-NSSAI), allowed slice types, or mapping rules associated with the subscriber. The significance of the “queryParamNssaiProc IE” lies in its ability to ensure that slice-specific subscription information is retrieved in a precise and filtered manner during the combined subscription data retrieval. Similar IEs may be defined for other procedures (e.g., SMSmanagement, session management, identifier translation), thereby providing a structured way to represent and process procedure-specific query parameters while still allowing all requests to be executed in a single combined transaction.[000137] The response returned by the UDM (304) to the consumer NF (302) may contain the results for each requested procedure, structured according to the IES specified in the request. If the retrieval of the set of subscription data for a particular procedure is unsuccessful, the response may include problem details specific to that procedure while still returning the successful results for other requested procedures. If no procedure is processed successfully, the UDM (304) may return a negative response with the appropriate status code and detailed problem descriptions.[000138] In an embodiment, the present disclosure provides a system (108) and method (300) by which the consumer NF (302) retrieves multiple sets of subscription data from the UDM (304) in a single transaction. In an embodiment, the consumer NF (302) identifies the need to retrieve various subscription data, such as session management data, access and mobility data, and other relevant subscription-related information.[000139] Upon identifying this requirement, the consumer NF (302) creates a message incorporating the newly defined procedure, termed “Combined Subscription Data Retrieval”. This message is essential for the retrieval of the set of subscription data from the UDM (304) and UDR (306) in the single transaction. This message is formatted according to predefined specifications and includes all necessary Information Elements (IEs), such as procedure names and relevant filter criteria (e.g., RAT type, IMEI, group ID, NSSAI, DNN, Access type, supported features (AM data / SM data), SUPI), as detailed in the procedural definitions. Once created, the consumer NF transmits this message to the UDM (304), initiating the data retrieval process.[000140] In an embodiment, upon receipt of the “Combined Subscription Data Retrieval” request, the UDM (304) processes the request by examining the included procedures for which data retrieval results are requested. The UDM (304) checks its internal database for the relevant subscription data. If any portion of the requested data is not locally available or requires additional processing, the UDM (304) interacts with the UDR (304) to retrieve the necessary data. This interaction may involve the UDM (304) sending a similar “Combined Subscription Data Retrieval” request to the UDR (306), ensuring that all requested data is aggregated efficiently.[000141] Subsequently, in an embodiment, the UDM (304) compiles the data retrieved for each procedure and prepares a response to be sent back to the consumer NF (302). If the data retrieval is successful for all requested procedures, the UDM (304) returns a comprehensive response containing the results for each procedure. However, if one or more of the requested procedures encounter an error or cannot be processed, the UDM (304) still returns the successful results while providing detailed problem information for each failed procedure.[000142] In scenarios where the UDM (304) is unable to process any of the requested procedures, an embodiment of the present disclosure ensures that the UDM (304) returns a negative response to the consumer NF (302). This negative response includes an appropriate status code and detailed problem descriptions, enabling the consumer NF (302) to understand the cause of the failure and take necessary corrective actions.[000143] Further, the consumer NF (302) processes the response received from the UDM (304), extracting and utilizing the results for the successful procedures. The consumer NF (302) may then continue its operations based on this retrieved data, integrating the information into its ongoing network management or service delivery tasks.[000144] FIG. 4 illustrates another exemplary flow diagram of a method (400) for retrieving multiple subscription data in the network (106) through a single transaction in accordance with an embodiment of the disclosure.[000145] At step 402, the UDM (208, 304) may receive a combined data retrieval request from a network function (NF) (302). The combined data retrieval request corresponds to retrieval of a set of subscription data in the single transaction. The set of subscription data includes, but not limited to, session management subscription data, access and mobility subscription data, Short Message Service (SMS) management subscription data, SMS subscription data, Session Management Function (SMF) selection subscription data, user equipment (UE) context in SMF data, UE context in Short Message Service Function (SMSF) data, identifier translation data, slice selection subscription data, shared subscription data, trace data, Location Services (LCS) privacy data, LCS mobile originated data, enhanced coverage restriction data, Vehicle-to- Everything (V2X) subscription data, and LCS broadcast assistance subscription data.[000146] In an embodiment, the combined data retrieval request includes one or more filtering criteria associated with the set of subscription data, and wherein the set of subscription data is retrieved from the UDM (208, 304) based on the one or more filtering criteria. The one or more filtering criteria comprises one of Radio Access Technology (RAT) type, International Mobile Equipment Identity (IMEI), group ID, Network Slice Selection Assistance Information (NSSAI), Data Network Name (DNN), access type, supported features, Subscription Permanent Identifier (SUPI), and Mobile Equipment Identifier (MEID).[000147] At step 404, the UDM (208, 304) determines whether at least one type of subscription data in the set of subscription data is available in the UDM (208, 304) based on the received combined data retrieval request.[000148] Upon determining if the at least one type of subscription data from the set of subscription data is not available, at step 406, the UDM (208, 304) may transmit a data query request towards the UDR (210, 306). The data query request corresponds to the retrieval of at least one type of subscription data from the UDR (210, 306).[000149] In an embodiment, upon determining that the one or more another type of the subscription data and the at least one type of subscription data from the set of subscription data are available in the UDM (208, 304), the UDM (208, 304) may transmit the set of subscription data to the NF in the single transaction.[000150] At step 408, the UDM (208, 304) may receive a response corresponding to the transmitted data query request from the UDR (210, 306). The response includes the at least one type of subscription data. In an embodiment, upon receiving the response from the UDR (210, 306), the UDM (208, 304) may combine the at least one type of subscription data received from the UDR (210, 306) and the one or more another type of subscription data from the set of subscription data available in the UDM (208, 304) to create the consolidated response.[000151] At step 410, the UDM (208, 304) sends a consolidated response, corresponding to the combined data retrieval request, to the NF. The consolidated response includes the one or more another type of the subscription data available in the UDM (208, 304) and the at least one type of subscription data retrieved from the UDR (210, 306).[000152] In some embodiments, the consolidated response further includes at least one of: a positive response indicating successful retrieval of the set of subscription data, and a negative response indicating a failure in the retrieval of the at least one type of subscription data from the set of subscription data. The negative response also includes a detailed problem description that allows the requesting NF to identify the cause of the failure and to take appropriate remedial actions, such as re-trying therequest, switching to alternate subscription parameters, or notifying higher-layer applications.[000153] FIG. 5 illustrates a computer system (500) in which or with which the embodiments of the present disclosure may be implemented.[000154] As shown in FIG. 5, the computer system (500) may include an external storage device (510), a bus (520), a main memory (530), a read-only memory (540), a mass storage device (550), communication port(s) (560), and a processor (570). A person skilled in the art will appreciate that the computer system may include more than one processor and communication ports. The processor (570) may include various modules associated with embodiments of the present disclosure. The communication port(s) (560) may be any of an RS-232 port for use with a modem-based dialup connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication port(s) (560) may be chosen depending on a network (106), such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system connects.[000155] The main memory (530) may be random access memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (540) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input / Output System (BIOS) instructions for the processor (570). The mass storage device (550) may be any current or future mass storage solution which can be used to store information and / or instructions. Exemplary mass storage device (550) includes, but is not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Firewireinterfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks.[000156] The bus (520) communicatively couples the processor (570) with the other memory, storage, and communication blocks. The bus (520) may be, e.g., a Peripheral Component Interconnect / Peripheral Component Interconnect Extended bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (570) to the computer system.[000157] Optionally, operator and administrative interfaces, e.g., a display, keyboard, joystick, and a cursor control device, may also be coupled to the bus (520) to support direct operator interaction with the computer system. Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) (560). The components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system limit the scope of the present disclosure.[000158] In an exemplary embodiment, a system for retrieving multiple subscription data in a network in a single transaction is disclosed. The system includes a unified data management (UDM) configured to receive a combined data retrieval request from a network function (NF). The combined data retrieval request corresponds to retrieval of a set of subscription data in the single transaction. The UDM is configured to determine whether at least one type of subscription data in the set of subscription data is available in the UDM based on the received combined data retrieval request. Upon determining if the at least one type of subscription data from the set of subscription data is not available, the UDM is configured to transmit a data query request towards a unified data repository (UDR), the data query request corresponds to retrieval of the at least one type of subscription data from the UDR. The UDM isconfigured to receive a response corresponding to the transmitted data query request from the UDR, the response comprises the at least one type of subscription data. The UDM is configured to send a consolidated response, corresponding to the data retrieval request, to the NF. The consolidated response includes one or more another type of the subscription data available in the UDM and the at least one type of subscription data retrieved from the UDR.[000159] In another exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium is disclosed. The medium includes instructions that, when executed by one or more processors, cause the one or more processors to execute a method for retrieving multiple subscription data in a network in a single transaction. The method includes receiving, by a unified data management (UDM), a combined data retrieval request from a network function (NF). The combined data retrieval request corresponds to retrieval of a set of subscription data in the single transaction. The method includes determining, by the UDM, whether at least one type of subscription data in the set of subscription data is available in the UDM based on the received combined data retrieval request. Upon determining if the at least one type of subscription data from the set of subscription data is not available, the method includes transmitting, by the UDM, a data query request towards a unified data repository (UDR), The data query request corresponds to retrieval of the at least one type of subscription data from the UDR. The method includes receiving, by the UDM, a response corresponding to the transmitted data query request from the UDR. The response includes the at least one type of subscription data. The method includes sending, by the UDM, a consolidated response, corresponding to the combined data retrieval request, to the NF. The consolidated response includes one or more another type of the subscription data available in the UDM and the at least one type of subscription data retrieved from the UDR.[000160] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made, and many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be implemented merely as illustrative of the disclosure and not as a limitation.[000161] The present disclosure provides a technical advancement in subscription data management by enabling the retrieval of multiple types of subscription data in a single transaction. Unlike traditional approaches, where a consumer NF must send multiple individual requests to the UDM for different types of subscription data, the present disclosure allows a combined data retrieval request that consolidates such operations. The present disclosure further enables the UDM to determine whether requested subscription data is locally available or may be retrieved from the UDR, and to generate a consolidated response accordingly. This reduces signaling overhead, minimizes redundant query operations, and improves the efficiency of subscription data handling across the 5G core network. The present disclosure significantly reduces transaction latency, improves network performance, and enhances scalability by supporting filtering criteria and integrated identifier translation, thereby providing optimized subscription data delivery to the consumer NFs.ADVANTAGES OF THE PRESENT DISCLOSURE[000162] The present disclosure described herein above has several technical advantages including, but not limited to, the realization of the system and the method that:[000163] The present disclosure provides a system and a method that allows retrieval of the set of subscription data from the UDM and UDR in the singletransaction, thereby reducing the number of interactions required between the customer NFs and the data management systems (i.e., the UDM and UDR).[000164] The present disclosure reduces transaction overhead, minimizing system load, and improving the efficiency of network operations.[000165] The present disclosure introduces a “Combined Subscription Data Retrieval” procedure, which integrates the retrieval and subscription management operations into the single transaction, resulting in a more efficient data management process.[000166] The present disclosure ensures that the system remains responsive even in cases where one or more procedures fail, by returning successful results for completed procedures along with detailed problem information for those that encountered issues. This improves fault tolerance and robustness in the data retrieval process.[000167] The present disclosure provides a method and a system for optimizing the overall number of transactions from consumer NF towards UDM for a Get service operation.[000168] The present disclosure provides a method and a system for optimizing the overall number of transactions from consumer NF towards UDR for a Get / Query service operation.

Claims

CLAIMS1. A method (400) for retrieving multiple subscription data in a network in a single transaction, the method (400) comprising: receiving (402), by a unified data management (UDM) (208, 304), a combined data retrieval request from a network function (NF) (302), wherein the combined data retrieval request corresponds to retrieval of a set of subscription data in the single transaction; determining (404), by the UDM (208, 304), whether at least one type of subscription data in the set of subscription data is available in the UDM (208, 304) based on the received combined data retrieval request; upon determining if the at least one type of subscription data from the set of subscription data is not available, transmitting (406), by the UDM (208, 304), a data query request towards a unified data repository (UDR) (210, 306), wherein the data query request corresponds to retrieval of the at least one type of subscription data from the UDR (210, 306); receiving (408), by the UDM (208, 304), a response corresponding to the transmitted data query request from the UDR (210, 306), wherein the response comprises the at least one type of subscription data; and sending (410), by the UDM (208, 304), a consolidated response, corresponding to the combined data retrieval request, to the NF, wherein the consolidated response comprises one or more another type of the subscription data available in the UDM (208, 304) and the at least one type of subscription data retrieved from the UDR (210, 306).

2. The method (400) as claimed in claim 1, wherein the set of subscription data comprises session management subscription data, access and mobility subscription data, Short Message Service (SMS) management subscription data, SMS subscription data, Session Management Function (SMF) selection subscription data, user equipment(UE) context in SMF data, UE context in Short Message Service Function (SMSF) data, identifier translation data, slice selection subscription data, shared subscription data, trace data, Location Services (LCS) privacy data, LCS mobile originated data, enhanced coverage restriction data, Vehicle-to-Everything (V2X) subscription data, and LCS broadcast assistance subscription data.

3. The method (400) as claimed in claim 1, wherein upon receiving the response from the UDR (210, 306), combining, by the UDM (208, 304), the at least one type of subscription data received from the UDR (210, 306) and the one or more another type of subscription data from the set of subscription data available in the UDM (208, 304) to create the consolidated response.

4. The method (400) as claimed in claim 1 , wherein upon determining that the one or more another type of the subscription data and the at least one type of subscription data from the set of subscription data are available in the UDM (208, 304), transmitting, by the UDM (208, 304), the set of subscription data to the NF in the single transaction.

5. The method (400) as claimed in claim 1, wherein the combined data retrieval request comprises one or more filtering criteria associated with the set of subscription data, and wherein the set of subscription data is retrieved from the UDM (208, 304) based on the one or more filtering criteria.

6. The method (400) as claimed in claim 5, wherein the one or more filtering criteria comprises one of Radio Access Technology (RAT) type, International Mobile Equipment Identity (IMEI), group ID, Network Slice Selection Assistance Information (NSSAI), Data Network Name (DNN), access type, supported features, Subscription Permanent Identifier (SUPI), and Mobile Equipment Identifier (MEID).

7. The method (400) as claimed in claim 1 , wherein the consolidated response further comprises at least one of: a positive response indicating successful retrieval of the set of subscription data, and a negative response indicating a failure in the retrieval of the at least one type of subscription data from the set of subscription data, wherein the negative response also comprises a detailed problem description.

8. A system (108) for retrieving multiple subscription data in a network in a single transaction, the system (108) comprising: a unified data management (UDM) (208, 304) configured to: receive a combined data retrieval request from a network function (NF) (302), wherein the combined data retrieval request corresponds to retrieval of a set of subscription data in the single transaction; determine whether at least one type of subscription data in the set of subscription data is available in the UDM (208, 304) based on the received combined data retrieval request; upon determining if the at least one type of subscription data from the set of subscription data is not available, transmit a data query request towards a unified data repository (UDR) (210, 306), wherein the data query request corresponds to retrieval of the at least one type of subscription data from the UDR (210, 306); receive a response corresponding to the transmitted data query request from the UDR (210, 306), wherein the response comprises the at least one type of subscription data; and send a consolidated response, corresponding to the data retrieval request, to the NF, wherein the consolidated response comprises one or moreanother type of the subscription data available in the UDM (208, 304) and the at least one type of subscription data retrieved from the UDR (210, 306).

9. The system (108) as claimed in claim 8, wherein the set of subscription data comprises session management subscription data, access and mobility subscription data, Short Message Service (SMS) management subscription data, SMS subscription data, Session Management Function (SMF) selection subscription data, user equipment (UE) context in SMF data, UE context in Short Message Service Function (SMSF) data, identifier translation data, slice selection subscription data, shared subscription data, trace data, Location Services (LCS) privacy data, LCS mobile originated data, enhanced coverage restriction data, Vehicle-to-Everything (V2X) subscription data, and LCS broadcast assistance subscription data.

10. The system (108) as claimed in claim 8, wherein upon receiving the response from the UDR (210, 306), the UDM (208, 304) is configured to: combine the at least one type of subscription data received from the UDR (210, 306) and the one or more another type of subscription data from the set of subscription data available in the UDM (208, 304) to create the consolidated response.

11. The system (108) as claimed in claim 8, wherein upon determining that the one or more another type of the subscription data and the at least one type of subscription data from the set of subscription data is available in the UDM (208, 304), the UDM (208, 304) is configured to: transmit the set of subscription data to the NF in the single transaction.

12. The system (108) as claimed in claim 8, wherein the combined data retrieval request comprises one or more filtering criteria associated with the set of subscriptiondata, and wherein the set of subscription data is retrieved from the UDM (208, 304) based on the one or more filtering criteria.

13. The system (108) as claimed in claim 12, wherein the one or more filtering criteria comprises one of Radio Access Technology (RAT) type, International Mobile Equipment Identity (IMEI), group ID, Network Slice Selection Assistance Information (NSSAI), Data Network Name (DNN), access type, supported features, Subscription Permanent Identifier (SUPI), and Mobile Equipment Identifier (MEID).

14. The system (108) as claimed in claim 8, wherein the consolidated response further comprises at least one of: a positive response indicating successful retrieval of the set of subscription data, and a negative response indicating a failure in retrieval of the at least one type of subscription data from the set of subscription data, wherein the negative response also comprises a detailed problem description.

15. 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 (400) for retrieving multiple subscription data of a network in a single transaction, the method (400) comprises: receiving, by a unified data management (UDM) (208, 304), a combined data retrieval request from a network function (NF) (302), wherein the combined data retrieval request corresponds to retrieval of a set of subscription data in the single transaction; determining, by the UDM (208, 304), whether at least one type of subscription data in the set of subscription data is available in the UDM (208, 304) based on the received combined data retrieval request;upon determining if the at least one type of subscription data from the set of subscription data is not available, transmitting, by the UDM (208, 304), a data query request towards a unified data repository (UDR) (210, 306), wherein the data query request corresponds to retrieval of the at least one type of subscription data from the UDR (210, 306); receiving, by the UDM (208, 304), a response corresponding to the transmitted data query request from the UDR (210, 306), wherein the response comprises the at least one type of subscription data; and sending, by the UDM (208, 304), a consolidated response, corresponding to the combined data retrieval request, to the NF, wherein the consolidated response comprises one or more another type of the subscription data available in the UDM (208, 304) and the at least one type of subscription data retrieved from the UDR (210, 306).

Images