System and method for retrieving short message service management subscription data in a single transaction

Abstract

The present disclosure provides a system (108) and a method (400) for retrieving Short Message Service (SMS) management subscription data in a single transaction. The system (108) includes a UDM (304). The UDM (304) receives a single data retrieval request from a Short Message Service Function (SMSF) (302) to retrieve the SMS management subscription data along with a Generic Public Subscription Identifier (GPSI) information associated with a subscriber in the single transaction. The UDM (304) retrieves the SMS-related management data and the identifier translation data. The UDM (304) generates a response by incorporating the GPSI information from the identifier translation data into the SMS-related management data. The UDM (304) sends a response corresponding to the single data retrieval request to the SMSF. The response includes the SMS-related management data with the incorporated GPSI information of the subscriber.

Description

SYSTEM AND METHOD FOR RETRIEVING SHORT MESSAGE SERVICE MANAGEMENT SUBSCRIPTION DATA IN 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 Short Message Service (SMS) management subscription data in 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, 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, identifier translation data, slice selection subscription data, and alike.

[0013] The term “SMS management subscription data” refers to subscriber- related information used by the SMSF to provide SMS services. It may include SMS service support indication (e.g., whether SMS over NAS is supported), restrictions or barring rules on SMS delivery, and limits on SMS usage based on provisioned GPSIs.

[0014] The term “Identifier Translation Data” refers to subscriber-related information stored in the UDM or UDR that enables the mapping between different types of identifiers assigned to a subscriber. Such identifiers may include the Subscription Permanent Identifier (SUPI), Generic Public Subscription Identifier (GPSI), additional GPSI, such as MSISDNs or external identifiers, and temporary identifiers allocated during registration.

[0015] The term “Generic Public Subscription Identifier (GPSI) information” refers to a public identifier of a subscriber that may be a Mobile Station International Subscriber Directory Number (MSISDN).

[0016] The term “additional GPSI information” refers to one or more secondary GPSI information associated with the same subscriber, which may include multiple MSISDNs or multiple external identifiers. Additional GPSI information is provisionedin the UDR and may be retrieved by the UDM when more than one GPSI is associated with a subscriber profile.

[0017] The term “Mobile Station International Subscriber Directory Number (MSISDN)” refers to the public number associated with a subscriber in a mobile network, used for services such as voice and SMS. An MSISDN is a form of GPSI.

[0018] The term “external identifier” refers to a public identifier of a subscriber other than an MSISDN, typically represented in the form of a Network Access Identifier (NAI)-like string (e.g., “sip:user@example.com”. An external identifier is a form of GPSI used for IP-based services and IMS / VoIP contexts.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0034] 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 (e.g., SMSF) to retrieve and manage SMS -related subscription management data stored in the UDM or UDR.

[0035] The term “sms-management-data (sms-mng-data)” used hereinafter in the specification refers to a resource that enables the retrieval of a subscriber’s Short Message Service (SMS) management subscription data. The sms-mng-data resource is accessible via a resource Uniform Resource Identifier (URI) exposed by the Unified Data Management (UDM) and contains subscription information required by the SMSF to provide SMS -related services to the subscriber.

[0036] The term “SMS data addition feature” refers to a configuration attribute that indicates whether the SMSF supports or is configured to receive GPSI information and one or more additional GPSI alongside SMS subscription data in a response from the UDM.

[0037] The term “single data retrieval request” refers to a GET operation initiated by the SMSF towards the UDM to retrieve, in one transaction, SMS management subscription data and the associated GPSI information (including additional GPSI if provisioned).

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

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

[0040] 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, and user 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 LocationCenter (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.

[0041] To access the subscriber data pertinent to the operations, the consumer NFs utilize the Get Service operation of the Service Nudm Subscriber Data Management service. This operation allows the consumer NFs to retrieve subscriber- related data such as session management data, mobility data, policy data, SMS subscription data, and identifier translation data. For instance, the AMF may need mobility subscription data for registration procedures, the SMF may require session management subscription data, and the SMSF may require SMS -related subscription data to enable or restrict SMS services for a subscriber.

[0042] 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 identifier translation data, it may initiate three distinct Get service operations. This results in multiple transactions between the SMSF 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 SMSF and UDM, leading to potential inefficiencies in the network performance. It also creates a risk of data inconsistency if different requests are processed at different times or if there is a failure in any of the transactions.

[0043] Additionally, when the SMSF requires Generic Public Subscription Identifier (GPSI) related information for providing services such as barring based on provisioned GPSI or limiting the number of SMS based on provisioned GPSI, the existing systems do not provide a direct option. Instead, the SMSF may need to use the identifier translation procedure of the UDM to obtain GPSI information. This resultsin an additional transaction for every such request, both at the SMSF and at the UDM (and / or UDR), thereby further increasing signaling load, latency, and resource consumption.

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

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

[0046] An objective of the present disclosure is to provide a system and a method that enables a Short Message Service Function (SMSF) to retrieve, in a single transaction, all subscription data necessary for SMS service delivery, thereby avoiding multiple independent requests to a Unified Data Management (UDM).

[0047] Another objective of the present disclosure is to retrieve a Short Message Service (SMS) management subscription data along with a Generic Public Subscription Identifier (GPSI) information or additional GPSI information if provisioned, in a single transaction.

[0048] Another objective of the present disclosure is to incorporate GPSI information, including one or more additional GPSI information, from an identifier translation data into the SMS management subscription data returned in the UDM response, thereby allowing the SMSF to use GPSI-based rules, such as barring or SMS usage limitations, without requiring a separate identifier translation procedure.

[0049] Another objective of the present disclosure is to reduce the total number of transactions required between Short Message Service Function (SMSF) and the Unified Data Management (UDM) and between the UDM and the Unified DataRepository (UDR), leading to lower transaction overhead and improved system efficiency.

[0050] Yet another objective of the present disclosure is to reduce signaling overhead, minimize latency, and improve processing efficiency in SMS service delivery by allowing the SMSF to obtain all required subscription data in one consolidated retrieval operation.

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

[0052] In an exemplary embodiment, a method for retrieving Short Message Service (SMS) management subscription data in a single transaction is disclosed. The method includes receiving, by a unified data management (UDM), a single data retrieval request from a Short Message Service Function (SMSF). The single data retrieval request combines a GET request for SMS -related management data and a GET request for identifier translation data, to retrieve the SMS management subscription data along with a Generic Public Subscription Identifier (GPSI) information associated with a subscriber in the single transaction. In response to receiving the single data retrieval request, the method includes retrieving, by the UDM, the SMS -related management data and the identifier translation data. The identifier translation data comprises the GPSI information associated with the subscriber. Upon retrieving, the method includes generating, by the UDM, a response by incorporating the GPSI information from the identifier translation data into the SMS-related management data. The method further includes sending, by the UDM, a response corresponding to the single data retrieval request to the SMSF, wherein the response comprises the SMS- related management data with the incorporated GPSI information of the subscriber.

[0053] In some embodiments, the GPSI information represents a Mobile Station International Subscriber Directory Number (MSISDN) associated with the subscriber.

[0054] In some embodiments, the identifier translation data further comprises one or more additional GPSI information associated with the subscriber. The one or more additional GPSI information is included in the identifier translation data when the UDM receives more than one GPSI information matching the single data retrieval request from a Unified Data Repository (UDR).

[0055] In some embodiments, the SMS -related management data is configured with an SMS data addition feature indicating whether the SMSF supports receiving the GPSI information and the one or more additional GPSI information in the response.

[0056] In some embodiments, when the SMS data addition feature is enabled, the UDM incorporates the GPSI information and the one or more additional GPSI information in the SMS-related management data to send to the SMSF in the response.

[0057] In some embodiments, the single data retrieval request corresponds to a combined retrieval procedure that enables the SMSF to obtain the SMS -related management data and the identifier translation data in a single transaction to avoid sending multiple separate retrieval requests to the UDM.

[0058] In some embodiments, the SMSF uses the GPSI information to provide one or more services. The one or more services comprise at least one of SMS barring service, or limiting a number of SMS messages allowed based on the provision of the GPSI information.

[0059] In some embodiments, the identifier translation data is retrieved by the UDM based on at least one of a subscription permanent identifier (SUPI), an externalidentifier, and a user equipment identifier (UE ID) associated with the single data retrieval request.

[0060] In another exemplary embodiment, a system for retrieving Short Message Service (SMS) management subscription data in a single transaction is disclosed. The system includes a unified data management (UDM) configured to receive a single data retrieval request from a Short Message Service Function (SMSF). The single data retrieval request combines a GET request for SMS-related management data and a GET request for identifier translation data, to retrieve the SMS management subscription data along with a Generic Public Subscription Identifier (GPSI) information associated with a subscriber in the single transaction. In response to receiving the single data retrieval request, the UDM is further configured to retrieve the SMS-related management data and the identifier translation data. The identifier translation data comprises the GPSI information associated with the subscriber. Upon retrieving, the UDM is further configured to generate a response by incorporating the GPSI information from the identifier translation data into the SMS-related management data. The UDM is further configured to send a response corresponding to the single data retrieval request to the SMSF. The response comprises the SMS-related management data with the incorporated GPSI information of the subscriber.

[0061] 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 Short Message Service (SMS) management subscription data in a single transaction. The method includes receiving, by a unified data management (UDM), a single data retrieval request from a Short Message Service Function (SMSF). The single data retrieval request combines a GET request for SMS -related management data and a GET request for identifier translation data, to retrieve the SMS management subscription data along with a Generic PublicSubscription Identifier (GPSI) information associated with a subscriber in the single transaction. In response to receiving the single data retrieval request, the method includes retrieving, by the UDM, the SMS-related management data and the identifier translation data. The identifier translation data comprises the GPSI information associated with the subscriber. Upon retrieving, the method includes generating, by the UDM, a response by incorporating the GPSI information from the identifier translation data into the SMS-related management data. The method further includes sending, by the UDM, a response corresponding to the single data retrieval request to the SMSF, wherein the response comprises the SMS -related management data with the incorporated GPSI information of the subscriber.

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

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

[0064] FIG. 1 illustrates an exemplary network architecture for retrieving Short Message Service (SMS) management subscription data in a single transaction, in accordance with an embodiment of the present disclosure.

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

[0066] FIG. 3 illustrates an exemplary flow diagram of a method for retrieving SMS management subscription data in a single transaction, in accordance with an embodiment of the present disclosure.

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

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

[0069] 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 - Short Message Service Function (SMSF)500 - Computing system510 - External Storage Device520 - Bus530 - Main Memory540 - Read Only Memory550 - Mass Storage Device560 - Communication Port570 - ProcessorDETAILED DESCRIPTION

[0070] 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 embodimentsof the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein. Example embodiments of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.

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

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

[0073] 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 terminatedwhen 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.

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

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

[0076] 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 the terms “mobile device”, “user equipment”, “user device”, “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The invention is not limited to any 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.

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

[0078] 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 networkcoverage, 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 of Things (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.

[0079] 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. In particular, a Short Message Service Function (SMSF) requires both SMS management subscription data and an associated subscription identifier (e.g., a Generic Public Subscription Identifier (GPSI) or additional GPSI) in order to provide SMS services for a subscriber.

[0080] However, conventional systems require the SMSF to perform separate transactions to obtain this information. For example, the SMSF invokes a Nudm SDM subscription data retrieval procedure to obtain SMS management subscription data, while a separate identifier translation procedure may be invoked to obtain the GPSI information from a Unified Data Management (UDM) and Unified Data Repository (UDR). This separation increases the number of Application Programming Interface (API) calls, introduces additional latency, creates redundant signaling between theSMSF, UDM, and UDR, and complicates synchronization of subscriber information across the network.

[0081] The present disclosure addresses the above-mentioned problems by combining multiple subscription data retrieval operations (e.g., combining a GET request for SMS -related management data and a GET request for identifier translation data) into a single, unified transaction. The single transaction means that instead of sending multiple requests (i.e., one request to retrieve SMS management subscription data and another request to retrieve GPSI information included in the identifier translation data), the SMSF can send one combined request that specifies all the types of data it needs by extending the SMS management subscription data retrieval procedure to incorporate identifier translation information. In particular, the disclosure enables a consumer NF, such as the SMSF, to obtain both SMS management subscription data and GPSI-related identifier translation data within the single transaction. By eliminating the need for two separate Nudm procedures, the disclosure reduces transaction overhead, minimizes redundant queries to the UDM and UDR, and ensures faster and more consistent provisioning of SMS services.

[0082] As such, the present disclosure provides a system and method for retrieving the SMS management subscription data in a single transaction. The UDM is configured to receive a single data retrieval request from the SMSF. The single data retrieval request combines a GET request for SMS -related management data and a GET request for identifier translation data to retrieve the SMS management subscription data along with the GPSI information associated with the subscriber in the single transaction. In response to receiving the single data retrieval request, the UDM is further configured to retrieve the SMS -related management data and the identifier translation data. The identifier translation data comprises the GPSI information associated with the subscriber. Upon retrieving, the UDM is further configured to generate a response by incorporating the GPSI information from the identifiertranslation data into the SMS -related management data. The UDM is further configured to send a response corresponding to the single data retrieval request to the SMSF. The response comprises the SMS-related management data with the incorporated GPSI information of the subscriber. This integrated approach reduces signaling load on the consumer NF (SMSF) and core network functions, lowers response latency, and improves overall efficiency of subscription data management in the network.

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

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

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

[0086] 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, a person 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.

[0087] 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, smartwatches, 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.

[0088] Additionally, in some embodiments, the UE (104) may include, but not limited to, a handheld wireless communication device (e.g., a mobile phone, a smartphone, a phablet device, and so on), a wearable computer device (e.g., a headmounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and / or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the UE (104) may include, but are not limited to, any electrical, electronic, electromechanical, or equipment, or a combination of one or more of the above devices, such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general -purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device, wherein the UE (104) may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user (102) or the entity such as touchpad, touch-enabled screen, electronic pen, and the like. A person of ordinary skill in the art will appreciate that the UE (104) may not be restricted to the mentioned devices and various other devices may be used.

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

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

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

[0092] In an embodiment, the system (108) may be configured to retrieve SMS management subscription data in a single transaction. The system (108) includes the UDM. The UDM is configured to receive a single data retrieval request from the SMSF. The single data retrieval request combines a GET request for SMS -related management data and a GET request for identifier translation data to retrieve the SMS management subscription data along with the GPSI information associated with the subscriber in the single transaction. In response to receiving the single data retrieval request, the UDM is further configured to retrieve the SMS-related management data and the identifier translation data. The identifier translation data comprises the GPSI information associated with the subscriber. Upon retrieving, the UDM is further configured to generate a response by incorporating the GPSI information from the identifier translation data into the SMS-related management data. The UDM is further configured to send a response corresponding to the single data retrieval request to the SMSF. The response comprises the SMS-related management data with the incorporated GPSI information of the subscriber. This integrated approach reduces signaling load on the consumer NF (SMSF) and core network functions, lowers response latency, and improves overall efficiency of subscription data management in the network.

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

[0094] 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 SMS management subscription data in a single transaction.

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

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

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

[0098] The UDM (208) is configured to receive a single data retrieval request from a consumer NF, such as a Short Message Service Function (SMSF). In an embodiment, the single data retrieval request combines a GET request for SMS -related management data and a GET request for identifier translation data. The single data retrieval request corresponds to a combined retrieval procedure that enables the SMSF to obtain the SMS-related management data and the identifier translation data in a single transaction, thereby avoiding sending multiple separate retrieval requests to the UDM (208). The SMS-related management data corresponds to SMS management subscription data. The combined retrieval procedure refers to a unified mechanism defined within the UDM (208) and UDR (210) for handling multiple subscription data retrieval operations within a single transaction. Instead of invoking distinct and independent GET procedures for each type of subscription data (for example, a GETprocedure for SMS management subscription data and another GET procedure for identifier translation data), the combined retrieval procedure allows the SMSF to merge such requests into a single structured operation. This unified operation is designed to be machine-readable, standardized, and discoverable through a dedicated resource URI, thereby ensuring interoperability across vendor implementations and compliance with service-based architecture principles of the 5G core network.

[0099] In an embodiment, the GET request for SMS -related management data refers to a standardized service operation invoked by the SMSF to retrieve SMS management subscription data required for supporting SMS delivery and control functions. The SMS management subscription data may include parameters like SMS over NAS support indication, barring rules for SMS delivery, or limitations on the number of SMS messages allowed based on provisioned subscription identifiers.

[0100] In an embodiment, the SMS over NAS support indication specifies whether a subscriber’s device and the network support the transmission of Short Message Service (SMS) over the Non-Access Stratum (NAS) signaling. This parameter is essential to determine if SMS messages can be delivered without requiring a circuit-switched fallback, thereby ensuring seamless SMS delivery in pure 5G environments.

[0101] In an embodiment, the barring rules for SMS delivery define subscription-specific restrictions that prohibit or limit the delivery of SMS messages under certain conditions. Such barring rules may be configured by the operator to enforce policies such as preventing SMS transmission during roaming or restricting SMS services to specific subscriber categories.

[0102] In an embodiment, the limitations on the number of SMS messages allowed specify thresholds associated with SMS delivery for a subscriber, based on provisioned subscription identifiers. For example, the subscription data may restrict asubscriber to a maximum number of SMS messages within a billing cycle or enforce limits to prevent misuse of SMS services, such as spamming. These limitations are enforced by the SMSF using the subscription data retrieved from the UDM / UDR

[0103] Similarly, the GET request for identifier translation data refers to a service operation through which the SMSF, via the UDM (208), obtains mappings between different subscriber identifiers. This typically includes resolving a Subscription Permanent Identifier (SUPI) into one or more Generic Public Subscription Identifiers (GPSI), such as a Mobile Station International Subscriber Directory Number (MSISDN) or external identifiers. The identifier translation data ensures that SMS services can be properly routed, billed, or barred based on subscriber-specific GPSI information.

[0104] In response to receiving the single data retrieval request, the UDM (208) is configured to retrieve the SMS-related management data and the identifier translation data. The identifier translation data includes the GPSI information associated with the subscriber.

[0105] In an embodiment, the GPSI serves as a generic identifier used by external applications or network functions to reference a subscriber without exposing the SUPI. The GPSI information may correspond to a Mobile Station International Subscriber Directory Number (MSISDN) associated with the subscriber. The MSISDN represents a telephone number associated with the subscriber. The MSISDN allows the network to route SMS messages and other services to the subscriber based on a standardized numbering plan. In identifier translation data, the MSISDN is mapped to the SUPI to enable service continuity and efficient identifier resolution.

[0106] In an embodiment, the identifier translation data is retrieved by the UDM (208) based on at least one of a subscription permanent identifier (SUPI), anexternal identifier, and a user equipment identifier (UE ID) associated with the single data retrieval request.

[0107] In an embodiment, the SUPI is a unique, long-term identifier of the subscriber that is provisioned in the network. The SUPI is used for authentication and authorization of the subscriber and is mapped to one or more service-level identifiers for enabling communication services. The SUPI may be represented in International Mobile Subscriber Identity (IMSI) format in legacy systems or in Network Access Identifier (NAI) format in 5G deployments.

[0108] In an embodiment, the external identifier corresponds to an identifier used for addressing the subscriber outside the core network, such as an email-like identifier in the format “user@realm”. External identifiers are commonly used in Machine-to-Machine (M2M) and Internet of Things (loT) scenarios to uniquely reference devices or applications. The identifier translation data provides mapping between such external identifiers and the SUPI, thereby ensuring consistent identification of the subscriber across different service domains.

[0109] In an embodiment, the UE ID represents a context-specific identifier that is assigned to the user equipment for ongoing communication sessions. By retrieving identifier translation data based on these identifiers, the UDM (208) ensures that the SMSF receives the appropriate GPSI information or mappings required to support SMS services, including message delivery, barring, or quota enforcement.

[0110] In an embodiment, to retrieve the identifier translation data, when the request includes the SUPI, the UDM (208) queries its internal database or forwards a query to the UDR (210) to obtain the corresponding GPSI. Further, to retrieve the identifier translation data, in case the request specifies an external identifier, such as a network-assigned identifier in the format “username@realm”, the UDM (208) resolves this external identifier to the underlying SUPI and retrieves the associated GPSIinformation. Alternatively, when the request contains the UE ID, the UDM (208) uses the UE context information to identify the corresponding SUPI or external identifier, and subsequently retrieves the related GPSI mappings.

[0111] In some embodiments, the identifier translation data further includes one or more additional GPSI information associated with the subscriber. The one or more additional GPSI refers to other public identifiers associated with the same subscriber. These are returned by the UDM only if more than one GPSI is associated with the same UE ID or SUPI in the UDR. For example, a subscriber may have: GPSI: +91-9876543210 (MSISDN). Additional GPSI may have: sip:+919876543210@ims.mnc001.mcc404.3gppnetwork.org, xyz@abc.com.

[0112] In an embodiment, the one or more additional GPSI information is included in the identifier translation data when the UDM (208) receives more than one GPSI information matching the single data retrieval request from the UDR (210). The term “matching the single data retrieval request” refers to the situation where the UDR (210), upon processing the single data retrieval request, identifies that the provided identifier (e.g., SUPI, external identifier, or UE ID) is associated with more than one GPSI within the subscription profile. For example, a single SUPI may be provisioned with multiple GPSIs, such as a primary MSISDN, one or more secondary MSISDNs, and an external identifier (e.g., “user@operator.com”). Each of these GPSIs may be valid for different services, roaming agreements, or service domains. When such a case arises, the UDM (208) includes all the GPSIs (one or more additional GPSIs) that are validly associated with the subscriber in the identifier translation data returned to the SMSF. This ensures that the SMSF has complete visibility of all identifiers linked to the subscriber and can apply SMS -related service policies consistently. For example, the SMSF may enforce barring or message limitations across all GPSIs belonging to the subscriber, thereby preventing situations where a restriction applied on one identifier may be bypassed by using another associated identifier.

[0113] In order to retrieve the SMS management subscription data and the identifier translation data, the UDM (208) determines whether the requested SMS management subscription data and the corresponding identifier translation data are available locally in the UDM (208). If available, the UDM (208) directly retrieves the requested data from its internal storage. If the requested data is not available, the UDM (208) transmits a data query request to the UDR (210). The UDR (210) responds to the UDM (208) with the requested data. In an embodiment, the UDR response includes: the SMS management subscription data (such as SMS over NAS support indication, or provisioning details for SMS barring or limitation based on GPSI), and the identifier translation data, which may include the GPSI associated with the subscriber, or one or more additional GPSI if more than one mapping exists for the subscriber.

[0114] After retrieving the SMS-related management data and the identifier translation data, the UDM (208) generates a response (i.e., a consolidated response that needs to be sent to the SMSF (302)). In an embodiment, the UDM (208) generates the response by incorporating the GPSI information into the SMS management subscription data.

[0115] In an embodiment, if more than one GPSI information is provisioned for the same subscriber in the UDM (208) or UDR (210), the UDM (208) is further configured to include one or more additional GPSI entries in the response.

[0116] Table 1 illustrates the SMS management subscription data with the incorporated GPSI and additional GPSI.Table: 1

[0117] The generated response is then sent from the UDM (208) back to the SMSF. The response includes the SMS -related management data with the incorporated GPSI information of the subscriber.

[0118] In an embodiment, to receive the GPSI information in the response, theSMS management subscription data may be configured with an SMS data addition feature (e.g., “SmsAddData”).

[0119] Table 2 illustrates the incorporation of a new feature, “SmsAddData” in a list of existing supported features of the consumer NFs. The “SmsAddData” feature indicates whether the SMSF supports receiving responses that include GPSI information. When the feature is enabled, the UDM (208) incorporates GPSI information and / or additional GPSI information into the SMS-related management data before sending the response to the SMSF. When the “SmsAddData” feature is disabled, the UDM (208) may return only the basic SMS-related management data without GPSI information.Table: 2

[0120] In the context of the SMS, such identifier translation data is critical because the SMSF relies on GPSI information (e.g., MSISDNs or other external identifiers) to enforce service-level policies, such as barring specific subscribers from sending or receiving SMS messages or limiting the number of SMS deliveries provisioned under a subscription. By retrieving and incorporating the GPSI information into the SMS management subscription data, the UDM (208) ensures that the SMSF obtains both the subscriber’s SMS service configuration and the necessary identifiers in a single response. This eliminates the need for the SMSF to issue multiple queries, reduces signaling overhead, and ensures consistency between SMS -related policy enforcement and identifier management.

[0121] Upon receiving the response, the SMSF may perform various service operations based on the incorporated GPSI information. The service operations include, but are not limited to, SMS barring service, or limiting the number of SMS messages allowed based on a provision of the GPSI information.

[0122] In SMS barring service, the SMSF enforces barring rules to restrict or block SMS delivery for a particular subscriber or for a specific GPSI provisioned with barring conditions. For instance, if a subscriber’s GPSI is configured with a “no SMS” policy while roaming, the SMSF may block outgoing SMS messages associated with that GPSI. Similarly, the SMSF may implement a limitation on the number of SMS messages allowed, based on the GPSI information. For example, a GPSI may beprovisioned with a threshold permitting only a certain number of SMS messages per day or per billing cycle. Once the limit is reached, the SMSF may reject or defer additional SMS messages linked to that GPSI. By using GPSI information in this manner, the SMSF ensures that service policies are consistently and accurately enforced across all identifiers associated with the subscriber.

[0123] In an embodiment, the response further includes at least one of a positive response and a negative response. The positive response indicates successful retrieval of both the SMS management subscription data and the identifier translation data, including incorporation of the GPSI information into the SMS -related management data. In this case, the response returned to the SMSF comprises the consolidated subscription data set, enabling the SMSF to proceed with its service operations without requiring further queries.

[0124] In an alternative embodiment, the negative response indicates a failure in retrieving one or more portions of the requested data. For example, the UDM (208) may be unable to obtain GPSI information from the UDR (210) due to data unavailability or a query mismatch. In such a scenario, the negative response may include detailed problem information, such as an error code and descriptive cause specific to SMS management (e.g., GPSI not found, unsupported feature), to allow the SMSF to determine whether to retry the request, initiate fallback procedures, or adjust service operations accordingly.

[0125] In an embodiment, the system (108) ensures that both SMS-related management data and GPSI information are provided in a single transaction, thereby avoiding redundant queries, reducing load on the UDM (208) and UDR (210), and improving response efficiency for the SMSF.

[0126] For example, in a conventional approach, the SMSF may first transmit a GET request to the UDM (208) for SMS management subscription data, such as anindication of whether SMS over NAS is supported or whether barring restrictions apply for a given subscriber. Subsequently, in order to obtain the corresponding GPSI information, the SMSF must transmit a second, separate GET request for identifier translation data, such as a mapping from the subscriber’s SUPI to one or more GPSI (e.g., MSISDN). Each of these requests requires independent processing, signaling overhead, and potentially separate interactions between the UDM (208) and the UDR (210).

[0127] In contrast, the present disclosure allows the SMSF to combine both requests into a single transaction. The SMSF transmits a unified data retrieval request that explicitly includes both the SMS management procedure and the identifier translation procedure. Upon receiving this combined request, the UDM (208) retrieves the SMS management data and, if necessary, queries the UDR (210) for identifier translation data. The UDM (208) then prepares a response, in which the GPSI information obtained from the identifier translation procedure is directly incorporated into the SMS -related management data. The SMSF thereby receives all required information in one response, significantly reducing signaling exchanges, transaction latency, and processing overhead across the network.

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

[0129] FIG. 3 illustrates an exemplary flow diagram of a method (300) for retrieving SMS management subscription data in a single transaction, in accordance with an embodiment of the disclosure. The method (300) involves interactions between a consumer NF (e.g., an SMSF (302)), a UDM (304), and a UDR (306).

[0130] At step 308, the SMSF (302) initiates the process by transmitting a single request using a “Nudm_SubscriberDataManagement_Get sms-mng-data” service operation. In an embodiment, the service operation “Nudm Subscriber Data Management GET” refers to a standardized service-based interface (SBI), which enables consumer NFs (e.g., SMSF 302) to retrieve and manage SMS-related subscription management data stored in the UDM (304) or UDR (306). Further, the procedure name “sms-management-data or sms-mng-data” refers to a resource that enables the retrieval of a subscriber’s SMS management subscription data. The sms- mng-data resource is accessible via a resource Uniform Resource Identifier (URI) exposed by the UDM (304) and contains subscription information required by the SMSF (302) to provide SMS-related services to the subscriber.

[0131] The request specifically targets the retrieval of SMS management subscription data, while also requesting identifier translation data associated with the subscriber. In particular, for requesting the identifier translation data (i.e., GPSI information and / or the one or more additional GPSI information), the UDM (304) may check for the support of an SMS data addition feature, indicating whether the SMSF supports receiving the GPSI information and the one or more additional GPSI information from the UDM (304) in the response. When the SMS data addition feature is enabled, the UDM (304) incorporates the GPSI information and / or the one or more additional GPSI information in the SMS-related management data to send to the SMSF (302) in the response

[0132] In an embodiment, rather than performing multiple separate retrieval operations (e.g., one for SMS management subscription data and another for identifier translation data), the SMSF (302) uses the single data retrieval request to obtain both types of information from the UDM (304). The single data retrieval request corresponds to a combined retrieval procedure that enables the SMSF (302) to obtain the SMS -related management data and the identifier translation data in a singletransaction to avoid sending multiple separate retrieval requests to the UDM (304). This eliminates the need for multiple signaling exchanges, thereby reducing latency and network overhead while ensuring that SMSF receives consolidated subscription data in a single step.

[0133] In an embodiment, the single data retrieval request may also include various filtering criteria based on which the SMS management subscription data, along with identifier translation data, may be retrieved from the UDM (304). The filtering criteria may include, but are not limited to, a RAT type, an IMEI, an external group ID, an NS SAI, a DNN, an access type, supported features, a Subscription Permanent Identifier (SUPI), or a User Equipment Identifier (UE ID). These filtering criteria enable the SMSF (302) to narrow down retrieval requests, for example, by requesting only SMS management data associated with a particular SUPI or GPSI, or by limiting the retrieval to SMS -related services provisioned for a specific device or group of devices.

[0134] Upon receiving the request, the UDM (304) processes the request message and determines whether the required SMS management subscription data and GPSI-related information are locally available in the UDM (304).

[0135] At step 310, if the required data is not readily available within the UDM (304), the UDM forwards the query to the UDR (306) via a “Nudr_DM_Query” request. The UDR (306) processes the “Nudr DM Query” request and retrieves the SMS management subscription data, which may include parameters such as SMS over NAS support, SMS barring configuration, and message delivery limitations based on provisioned GPSI information. Alongside, the UDR (306) also provides GPSI mappings, which may include a Mobile Station International Subscriber Directory Number (MSISDN) or one or more external identifiers associated with the subscriber’s SUPI.

[0136] At step 312, the UDR (306) then sends a response back to the UDM (304), containing the requested SMS management subscription data and the GPSI- related information. Once the UDM (304) receives the requested SMS management subscription data and the GPSI-related information from the UDR (306), the UDM (304) generates a response by incorporating the GPSI information from the identifier translation data into the SMS-related management data.

[0137] At step 314, the UDM (304) sends the response back to the SMSF (302). This response includes the SMS management subscription data with the incorporated GPSI information. In some embodiments, the SMS management subscription data may also include one or more additional GPSI information. The inclusion of the one or more additional GPSI information allows the SMSF (302) to handle scenarios where multiple identifiers are associated with the same subscriber, thereby ensuring accurate barring and message delivery control across all provisioned identifiers.

[0138] In some embodiments, it is required that both the UDM (304) and UDR (306) are equipped to support the procedure “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, and in particular for the SMSF (302), to invoke the combined retrieval procedure. In the context of the present disclosure, this allows the SMSF (302) to request both SMS management subscription data and identifier translation data (including GPSI or additional GPSI) in a single transaction, rather than issuing separate queries for each dataset. This enables theSMSF (302) to obtain all SMS -related subscription information in one response over a service-based interface (SBI), thereby reducing signaling overhead, improving SMS delivery efficiency, and ensuring that SMSF services such as barring or SMS -limiting functions can be executed with up-to-date GPSI information.

[0139] The JavaScript Object Notation (JSON) body of the message sent to the 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. For SMSF, the supported features may include “smsDataAdditionFeature”, which signals support for GPSI or additional GPSI; 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. For SMSF, the procedureName explicitly includes “sms-mng-data” to indicate that SMS management subscription data is requested. This ensuresthat the UDM and UDR return information specifically relevant to SMS services, along with associated GPSI mappings.

[0140] 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 “sms-mng-data” is listed as a procedure, an IE named “queryParamSmsProc” is included, containing query parameters specific to SMS management subscription data. The “queryParamSmsProc” IE may include parameters such as: (i) whether SMS over NAS is supported, (ii) SMS barring conditions based on provisioned GPSI, and (iii) the request for GPSI and additional GPSI associated with the subscriber. The significance of the “queryParamSmsProc” IE lies in its ability to ensure that SMS -specific subscription information, including GPSI mappings, is retrieved in a precise and filtered manner during the combined subscription data retrieval process. This avoids over-fetching of unrelated data and enables the SMSF (302) to directly obtain information required for applying SMS policies, message barring, and identifier translation in a single query.

[0141] Similarly, for other procedures, such as 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., session management, identifier translation), thereby providing a structured way torepresent and process procedure-specific query parameters while still allowing all requests to be executed in a single combined transaction.

[0142] The response returned by the UDM (304) to the SMSF (302) may contain the results for each requested procedure, structured according to the IES specified in the request. In the case where the “sms-mng-data” procedure is requested, the response explicitly includes subscription data necessary for SMS service delivery. This response may contain one or more GPSI associated with the subscriber, including a primary GPSI or one or more additional GPSI (if provisioned).

[0143] In an embodiment, if the retrieval of the requested data for the SMS procedure is unsuccessful, the response may include problem details specific to SMS management (e.g., GPSI not found, unsupported feature), while still returning the successful results for any other requested procedures.

[0144] In an embodiment, the present disclosure provides a system (108) and method (300) by which the SMSF (302) retrieves SMS -specific subscription data, including GPSI and additional GPSI, from the UDM (304) in a single transaction. This avoids the need for the SMSF (302) to issue multiple sequential queries for identifier translation or SMS management data, thereby reducing signaling load and improving response latency.

[0145] Upon identifying the requirement for SMS management subscription data (e.g., GPSI mapping for message routing or policy enforcement), the SMSF (302) creates a message specifying the “smsAddData” feature to indicate that the SMSF (302) is requesting the retrieval of all provisioned GPSI (both primary and additional GPSI). Once created, the SMSF (302) transmits this message to the UDM (304), initiating the data retrieval process.

[0146] In an embodiment, upon receipt of the “sms-mng-data” retrieval request, the UDM (304) processes the request by examining the included procedures andchecking its internal database for the relevant SMS management subscription data. If the GPSI or additional GPSI is not locally available or requires further resolution, the UDM (304) interacts with the UDR (306) to retrieve the necessary data. This ensures that the SMSF (302) obtains a complete view of the subscriber’s provisioned identifiers, enabling correct routing and enforcement of SMS policies.

[0147] Subsequently, in an embodiment, the UDM (304) compiles the SMS- related data retrieved (e.g., GPSI, additional GPSI, SMS barring parameters, SMS over NAS indication) and prepares a response to be sent back to the SMSF (302). If retrieval is successful, the response contains the set of GPSI and associated SMS subscription parameters. If one or more elements (e.g., additional GPSI, SMS barring parameters, etc.) cannot be retrieved, the response still returns the successfully retrieved GPSI along with detailed problem information for the failed elements.

[0148] In scenarios where the UDM (304) is unable to process the SMS- specific retrieval request, the present disclosure ensures that the UDM (304) returns a negative response to the SMSF (302). This negative response may explicitly state that GPSI or additional GPSI are unavailable, not provisioned, or that the “SmsAddData” Feature is not supported. The response also includes a problem detail field, allowing the SMSF (302) to take corrective measures (e.g., fallback to a default GPSI, retry with alternative identifiers, or trigger error handling workflows).

[0149] Further, the SMSF (302) processes the response received from the UDM (304), extracting and utilizing the GPSI and additional GPSI for subsequent SMS delivery operations. The retrieved information may be used for routing short messages, enforcing SMS barring rules, or limiting the number of SMS messages per GPSI as per subscriber-specific policies. By enabling SMSF to obtain all relevant identifiers and SMS subscription data in a single transaction, the present disclosure ensures reduced latency, minimized signaling overhead, and improved accuracy in SMS service handling.

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

[0151] At step 402, the UDM (208, 304) may receive a single data retrieval request from a SMSF (302). The single data retrieval request combines a GET request for SMS-related management data and a GET request for identifier translation data to retrieve the SMS management subscription data along with the GPSI information associated with a subscriber in the single transaction. In an embodiment, the single data retrieval request corresponds to a combined retrieval procedure that enables the SMSF to obtain the SMS-related management data and the identifier translation data in a single transaction to avoid sending multiple separate retrieval requests to the UDM (208, 304).

[0152] In response to receiving the single data retrieval request, at step 404, the UDM (208, 304) retrieves the SMS-related management data and the identifier translation data. The identifier translation data includes the GPSI information associated with the subscriber. The GPSI information represents a Mobile Station International Subscriber Directory Number (MSISDN) associated with the subscriber.

[0153] In an embodiment, the identifier translation data is retrieved by the UDM based on at least one of a subscription permanent identifier (SUPI), an external identifier, and a user equipment identifier (UE ID) associated with the single data retrieval request.

[0154] In an embodiment, the identifier translation data further includes one or more additional GPSI information associated with the subscriber. The one or more additional GPSI information is included in the identifier translation data when the UDM receives more than one GPSI information matching the single data retrieval request from a Unified Data Repository (UDR).

[0155] In an embodiment, the SMS-related management data is configured with an SMS data addition feature indicating whether the SMSF supports receiving the GPSI information and the one or more additional GPSI information in the response. When the SMS data addition feature is enabled, the UDM incorporates the GPSI information and the one or more additional GPSI information in the SMS -related management data to send to the SMSF in the response.

[0156] At step 406, upon retrieving, the UDM (208, 304) may generate a response by incorporating the GPSI information from the identifier translation data into the SMS-related management data.

[0157] At step 408, the UDM (208, 304) sends a response corresponding to the single data retrieval request to the SMSF (302). The response comprises the SMS- related management data with the incorporated GPSI information of the subscriber. In an embodiment, the SMSF uses the GPSI information to provide one or more services. The one or more services include at least one of SMS barring service, or limiting a number of SMS messages allowed based on a provision of the GPSI information.

[0158] FIG. 5 illustrates a computer system (500) in which or with which the embodiments of the present disclosure may be implemented.

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

[0160] 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 Firewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks.

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

[0162] 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 meantonly to exemplify various possibilities. In no way should the aforementioned exemplary computer system limit the scope of the present disclosure.

[0163] In an exemplary embodiment, a system for retrieving SMS management subscription data in a single transaction is disclosed. The system includes the UDM configured to receive a single data retrieval request from the SMSF. The single data retrieval request combines a GET request for SMS -related management data and a GET request for identifier translation data, to retrieve the SMS management subscription data along with the GPSI information associated with a subscriber in the single transaction. In response to receiving the single data retrieval request, the UDM is further configured to retrieve the SMS-related management data and the identifier translation data. The identifier translation data comprises the GPSI information associated with the subscriber. Upon retrieving, the UDM is further configured to generate a response by incorporating the GPSI information from the identifier translation data into the SMS -related management data. The UDM is further configured to send a response corresponding to the single data retrieval request to the SMSF. The response comprises the SMS-related management data with the incorporated GPSI information of the subscriber.

[0164] 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 SMS management subscription data in a single transaction. The method includes receiving, by the UDM, a single data retrieval request from the SMSF. The single data retrieval request combines a GET request for SMS -related management data and a GET request for identifier translation data, to retrieve the SMS management subscription data along with a Generic Public Subscription Identifier (GPSI) information associated with a subscriber in the single transaction. In response to receiving the single data retrieval request, the methodincludes retrieving, by the UDM, the SMS-related management data and the identifier translation data. The identifier translation data comprises the GPSI information associated with the subscriber. Upon retrieving, the method includes generating, by the UDM, a response by incorporating the GPSI information from the identifier translation data into the SMS-related management data. The method further includes sending, by the UDM, a response corresponding to the single data retrieval request to the SMSF, wherein the response comprises the SMS -related management data with the incorporated GPSI information of the subscriber.

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

[0166] The present disclosure provides a technical advancement in SMS- related subscription data by enabling the retrieval of SMS management subscription data together with identifier translation data (e.g., GPSI information) in a single transaction. Unlike traditional approaches, where the SMSF may send multiple separate requests to the UDM for retrieval of SMS -related management data and GPSI information, the present disclosure allows a combined retrieval request that consolidates both operations into a single data retrieval request. The present disclosure further enables the UDM to determine whether the SMS -related management data and GPSI information are locally available or may need to be retrieved from the UDR, and to generate a response incorporating the GPSI information into the SMS management subscription data. This reduces signaling overhead, avoids duplicate requests, and improves the efficiency of SMS-related subscription data handling across the 5G corenetwork. The present disclosure significantly reduces transaction latency, improves SMSF performance, and enhances scalability by supporting filtering criteria, integrated GPSI mapping, and optimized subscription data delivery to the SMSF.ADVANTAGES OF THE PRESENT DISCLOSURE

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

[0168] The present disclosure provides a system and a method that enables a Short Message Service Function (SMSF) to retrieve, in a single transaction, all subscription data necessary for SMS service delivery, thereby avoiding multiple independent requests to a Unified Data Management (UDM).

[0169] The present disclosure provides a system and a method to retrieve a Short Message Service (SMS) management subscription data along with a Generic Public Subscription Identifier (GPSI) information or additional GPSI information if provisioned, in a single transaction.

[0170] The present disclosure provides a system and a method that incorporates GPSI information, including one or more additional GPSI information, from an identifier translation data into the SMS management subscription data returned in the UDM response, thereby allowing the SMSF to use GPSI-based rules, such as barring or SMS usage limitations, without requiring a separate identifier translation procedure.

[0171] The present disclosure provides a system and a method that reduces the total number of transactions required between Short Message Service Function (SMSF) 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.

[0172] The present disclosure provides a system and a method that reduces signaling overhead, minimize latency, and improve processing efficiency in SMS service delivery by allowing the SMSF to obtain all required subscription data in one consolidated retrieval operation.

Claims

CLAIMS1. A method (400) for retrieving Short Message Service (SMS) management subscription data in a single transaction, the method (400) comprising: receiving (402), by a unified data management (UDM) (208, 304), a single data retrieval request from a Short Message Service Function (SMSF) (302), wherein the single data retrieval request combines a GET request for SMS-related management data and a GET request for identifier translation data, to retrieve the SMS management subscription data along with a Generic Public Subscription Identifier (GPSI) information associated with a subscriber in the single transaction; in response to receiving the single data retrieval request, retrieving (404), by the UDM (208, 304), the SMS-related management data and the identifier translation data, wherein the identifier translation data comprises the GPSI information associated with the subscriber; upon retrieving, generating (406), by the UDM (208, 304), a response by incorporating the GPSI information from the identifier translation data into the SMS- related management data; and sending (408), by the UDM (208, 304), a response corresponding to the single data retrieval request to the SMSF (302), wherein the response comprises the SMS- related management data with the incorporated GPSI information of the subscriber.

2. The method (400) as claimed in claim 1 , wherein the GPSI information represents a Mobile Station International Subscriber Directory Number (MSISDN) associated with the subscriber.

3. The method (400) as claimed in claim 1, wherein the identifier translation data further comprises one or more additional GPSI information associated with the subscriber, and wherein the one or more additional GPSI information is included in theidentifier translation data when the UDM (208, 304) receives more than one GPSI information matching the single data retrieval request from a Unified Data Repository (UDR) (210, 306).

4. The method (400) as claimed in claim 1, wherein the SMS -related management data is configured with an SMS data addition feature indicating whether the SMSF (302) supports receiving the GPSI information and the one or more additional GPSI information in the response.

5. The method (400) as claimed in claim 4, wherein when the SMS data addition feature is enabled, the UDM (208, 304) incorporates the GPSI information and the one or more additional GPSI information in the SMS -related management data to send to the SMSF (302) in the response.

6. The method (400) as claimed in claim 1, wherein the single data retrieval request corresponds to a combined retrieval procedure that enables the SMSF (302) to obtain the SMS -related management data and the identifier translation data in a single transaction to avoid sending multiple separate retrieval requests to the UDM (208, 304).

7. The method (400) as claimed in claim 1, wherein the SMSF (302) uses the GPSI information to provide one or more services, and wherein the one or more services comprise at least one of SMS barring service, or limiting a number of SMS messages allowed based on a provision of the GPSI information.

8. The method (400) as claimed in claim 1, wherein the identifier translation data is retrieved by the UDM (208, 304) based on at least one of a subscription permanent identifier (SUPI), an external identifier, and a user equipment identifier (UE ID) associated with the single data retrieval request.

9. A system (108) for retrieving Short Message Service (SMS) management subscription data in a single transaction, the system (108) comprising: a unified data management (UDM) (208, 304) configured to: receive a single data retrieval request from a Short Message Service Function (SMSF) (302), wherein the single data retrieval request combines a GET request for SMS-related management data and a GET request for identifier translation data, to retrieve the SMS management subscription data along with a Generic Public Subscription Identifier (GPSI) information associated with a subscriber in the single transaction; in response to receiving the single data retrieval request, retrieve the SMS-related management data and the identifier translation data, wherein the identifier translation data comprises the GPSI information associated with the subscriber; upon retrieving, generate a response by incorporating the GPSI information from the identifier translation data into the SMS -related management data; and send a response corresponding to the single data retrieval request to the SMSF (302), wherein the response comprises the SMS -related management data with the incorporated GPSI information of the subscriber.

10. The system (108) as claimed in claim 9, wherein the GPSI information represents a Mobile Station International Subscriber Directory Number (MSISDN) associated with the subscriber.

11. The system (108) as claimed in claim 9, wherein the identifier translation data further comprises one or more additional GPSI information associated with the subscriber, and wherein the one or more additional GPSI information is included in theidentifier translation data when the UDM (208, 304) receives more than one GPSI information matching the single data retrieval request from a Unified Data Repository (UDR) (210, 306).

12. The system (108) as claimed in claim 9, wherein the SMS-related management data is configured with an SMS data addition feature indicating whether the SMSF (302) supports receiving the GPSI information and the one or more additional GPSI information in the response.

13. The system (108) as claimed in claim 12, wherein when the SMS data addition feature is enabled, the UDM (208, 304) incorporates the GPSI information and the one or more additional GPSI information in the SMS -related management data to send to the SMSF (302) in the response.

14. The system (108) as claimed in claim 9, wherein the single data retrieval request corresponds to a combined retrieval procedure that enables the SMSF (302) to obtain the SMS -related management data and the identifier translation data in a single transaction to avoid sending multiple separate retrieval requests to the UDM (208, 304).

15. The system (108) as claimed in claim 9, wherein the SMSF (302) uses the GPSI information to provide one or more services, and wherein the one or more services comprise at least one of SMS barring service, or limiting a number of SMS messages allowed based on a provision of the GPSI information.

16. The system (108) as claimed in claim 9, wherein the identifier translation data is retrieved by the UDM (208, 304) based on at least one of a subscription permanent identifier (SUPI), an external identifier, and a user equipment identifier (UE ID) associated with the single data retrieval request.

17. 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 Short Message Service (SMS) management subscription data in a single transaction, the method (400) comprises: receiving (402), by a unified data management (UDM) (208, 304), a single data retrieval request from a Short Message Service Function (SMSF) (302), wherein the single data retrieval request combines a GET request for SMS -related management data and a GET request for identifier translation data, to retrieve the SMS management subscription data along with a Generic Public Subscription Identifier (GPSI) information associated with a subscriber in the single transaction; in response to receiving the single data retrieval request, retrieving (404), by the UDM (208, 304), the SMS-related management data and the identifier translation data, wherein the identifier translation data comprises the GPSI information associated with the subscriber; upon retrieving, generating (406), by the UDM (208, 304), a response by incorporating the GPSI information from the identifier translation data into the SMS- related management data; and sending (408), by the UDM (208, 304), a response corresponding to the single data retrieval request to the SMSF (302), wherein the response comprises the SMS- related management data with the incorporated GPSI information of the subscriber.

Images