System and method for retrieving cell id associated with user equipment (UE) in network

Abstract

A method (800) for retrieving at least one cell parameter associated with at least one user equipment (UE) (104) in a network (106) is provided. The method (800) includes a first network function (e.g., an access and mobility management function (AMF) (306)) receiving a request from a second network function (e.g., a short message service function (SMSF) (302)) for providing location information. The AMF (306) extracts relevant information elements (IEs) from the request, analyzes them, generates a response based on the analysis, and sends the response to the SMSF (302). The SMSF (302) retrieves the cell parameters from the response and uses them to perform operations in the network (106).

Description

SYSTEM AND METHOD FOR RETRIEVING CELL ID ASSOCIATED WITH USER EQUIPMENT (UE) IN NETWORKRESERVATION OF RIGHTS

[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, Integrated Circuit (IC) layout design, and / or trade dress protection, belonging to Jio Platforms Limited (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 telecommunications. In particular, the present disclosure relates to a system and a method for retrieving at least one cell identity (ID) associated with at least one user equipment (UE) in a network.DEFINITIONS

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

[0004] The term “Network Function (NF)” used hereinafter in the specification refers to a component within the 5G network architecture that performs specific roles and services. The design of NFs in 5G allows for greater flexibility, scalability, and efficiency compared to previous generations of mobile networks. Each NF operatesindependently but can interconnect with other NFs to support a wide range of services. Examples of the network functions (NFs) include User Plane Function (UPF), the Access and Mobility Management Function (AMF), Session Management Function (SMF), Network Exposure Function (NEF), and Policy Control Function (PCF).

[0005] The term “Access and Mobility Management Function (AMF)” used hereinafter in the specification refers to a network function tasked with overseeing essential processes related to user session registration, authentication, and management of user mobility. This function plays a pivotal role in ensuring that subscribers maintain continuous connectivity while transitioning across different network domains.

[0006] The term “Short Message Service Function (SMSF)” used hereinafter in the specification refers to a network function that handles activation and deactivation of user equipment (UE). The SMSF ensures registration with a unified data management (UDM), maintains UE contexts and provides short message services to UE as well as other network functions. The SMSF works with the AMF to determine the UE availability and involves checking the UE status and location information.

[0007] The term “Unified Data Management (UDM)” used hereinafter in the specification refers to a network function that manages user-related data such as user credentials, subscription details, and service preferences. The UDM updates the user- related data based on changes in network subscription or network conditions. The AMF interacts with the UDM to retrieve user authentication data and subscription information during connection establishment.

[0008] The term “Service Communication Proxy (SCP)” used hereinafter in the specification refers to a network function facilitating communication between the different NFs. The SCP functions as an intermediary that routes service requests and responses between the NFs, ensuring that communications are directed to the appropriate the NF.

[0009] The term “Internet Protocol (IP) Short Message (IPSM)” used hereinafter in the specification refers to a gateway that acts as a bridge between the network and the internet protocol. The IPSM allows Short Message Service (SMS) to be sent and received over an IP network.

[0010] The term “Cell Identity (ID)” used hereinafter in the specification refers to a unique identifier assigned to a specific cell within the network. The cell ID is used for location-based services in the network. The cell ID enables the network to determine the approximate location of the UE based on the cell connected to the UE in the network. When the UE handovers between cells (for example, while a user moves from one cell coverage area to another), the cell ID smoothly manages the transition.

[0011] The term “Mobile Terminating (MT) flow” used hereinafter in the specification refers to a process of handling communications, such as voice calls, SMS, or data, directed to the UE in the network. The MT flow process involves the entire process of initiating a call or message to its delivery to the UE.

[0012] The term “Call Detail Record (CDR)” used hereinafter in the specification refers to a data record that provides details about a call or message transaction between the UE and the network. A network operator uses the CDR for billing, coverage, and analytics purposes. The CDR includes caller information, recipient information, call type and call status.

[0013] The term "Public Land Mobile Network (PLMN)” used hereinafter in the specification refers to a network that is accessible by the users using the UE and operated by the network operators. The PLMN provides communication services to users, such as voice call access, SMS, and data services.

[0014] The term "Information Element (IE)” used hereinafter in the specification refers to a structured data that conveys specific information within arequest or protocol. The IE includes one or more fields, such as an identifier, a parameter, and a status indicator.

[0015] The term "Network Provided Location Information (NPLI)” used hereinafter in the specification refers to information that the network provides regarding the geographic location of the UE. The NPLI is vital in managing various services, including calls, location-based services, and optimized network performance.

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

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

[0018] In a modern network, users are able to move with ease across the various network coverage areas, increasing demand for network services and applications. The network operators capture a cell identity (ID) of a user equipment to accommodate the demand for network services such as a cell ID barring, a roaming control, a service restriction, a call blocking, a number portability and an emergency calling. The network services are provided by various network functions, including a short message service function (SMSF), an access and mobility management function (AMF), a service communication proxy (SCP), and a unified data management (UDM).

[0019] In existing systems, the SMSF uses the cell ID information for cell ID barring service in the network during a mobile terminating (MT) flow. The Cell ID determines whether the UE lies in a specific cell or is within range of a base station.The MT flow is activated for the UE from the AMF. The AMF sends the cell ID to the SMSF. The cell ID received by the SMSF is stored in a UE context, which is used for cell ID barring functionality. The cell IDs of the existing users in the network are available in the SMSF cache. However, these cell IDs in the cache lack updation of the cell ID due to improper communication between the UE and the NFs, such as the AMF and the SMSF. Also, the new users in the network are yet to be registered with the network, hence cell IDs are absent in the SMSF.

[0020] Further, when inaccurate / stale cell IDs are used for cell ID barring functionality, the barring process fails. Using inaccurate / stale cell IDs leads to configuration errors, mobility management issues, and signal interference. Also, maintaining a call detail record (CDR) with imprecise cell ID data for reporting and analyzing provides misleading insights about the network performance and conditions.

[0021] Hence, a method and system that can address the shortcomings of existing solutions are needed.OBJECTIVES OF THE DISCLOSURE

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

[0023] An objective of the present disclosure is to provide a system and a method for retrieving at least one cell identity (ID) associated with at least one user equipment (UE) in a network.

[0024] Another objective of the present disclosure is to provide a system and a method that fetches accurate cell ID from an Access and Mobility Management Function (AMF) to perform cell ID barring in the network.

[0025] Another objective of the present disclosure is to provide a system and a method that provides the cell ID using an application programming interface (API) from the A MF.

[0026] Yet another objective of the present disclosure is to provide a system and a method that enables a Short Message Service Function (SMSF) to dynamically retrieve accurate cell ID information on demand for already activated users from the AMF. This ensures that the SMSF has access to the most current location data, significantly enhancing the effectiveness of cell ID barring operations within the Public Land Mobile Network (PLMN).

[0027] Yet another objective of the present disclosure is to provide a system and a method that addresses an information gap for newly activated users by ensuring that their Cell ID information is captured and made available to the SMSF immediately upon activation. This proactive approach eliminates the previous absence of cell ID data for new users, thereby facilitating consistent and accurate service delivery from the outset.

[0028] Yet another objective of the present disclosure is to provide a system and a method that enhances the accuracy and reliability of call detail record (CDR) reporting by ensuring that the cell ID data used in the records is up-to-date and reflective of real-time conditions. This improvement will provide network operators with better insights into network performance and user behavior, enabling more informed decision-making.

[0029] Yet another objective of the present disclosure is to implement robust error-handling and synchronization mechanisms to minimize discrepancies between the SMSF and the AMF, thereby enhancing the overall reliability of the network services.

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

[0031] In an exemplary embodiment, a method for retrieving at least one cell parameter associated with at least one user equipment (UE) in a network. The method includes receiving, by a first network function, at least one request from a second network function for providing at least one location information. The method includes extracting, by the first network function, at least one information element (IE) from the at least one received request. The method includes analyzing, by the first network function, the at least one extracted information element (IE) and generating at least one response. The method includes, based on the analysis, sending, by the first network function, the at least one response to the second network function and retrieving, by the second network function, the at least one cell parameter from the at least one response to perform at least one operation in the network.

[0032] In an embodiment, the method includes receiving, by the first network function, the at least one request via an application programming interface (API).

[0033] In an embodiment, the first network function is an access and mobility management function (AMF), and the second network function is a short message service function (SMSF).

[0034] In an embodiment, the at least one information element (IE) includes an attribute-value pair (A VP), where the attribute of the AVP includes at least one of a current geographic location, a cell identifier (ID), a tracking area, a location area and a service area, and where the value is set to true when the information corresponding to the attribute is requested.

[0035] In an embodiment, the at least one cell parameter includes at least one of the cell ID, a tracking area identifier, a location area identifier, and a service area identifier.

[0036] In an embodiment, the at least one operation includes at least one of barring the cell ID in the network and storing a cell detail record (CDR) in a database.

[0037] In an embodiment, the location information includes a current location or a last known location of the at least one user equipment.

[0038] In an embodiment, the first network function and the second network function are communicated through a service communication proxy (SCP).

[0039] In an exemplary embodiment, a system for retrieving at least one cell parameter associated with at least one user equipment (UE) in a network includes a first network function and a second network function. The first network function includes a receiving unit configured to receive at least one request from the second network function for providing at least one location information. An extracting unit configured to extract at least one information element (IE) from the at least one received request. An analyzing unit configured to analyze the at least one extracted information element (IE) and generate at least one response based on the analysis. A sending unit configured to send the at least one response to the second network function, where the second network function is configured to retrieve the at least one cell parameter from the at least one response to perform at least one operation in the network.

[0040] In an embodiment, the receiving unit is configured to receive the at least one request from the second network function via an application programming interface (API).

[0041] In an embodiment, the first network function is an access and mobility management function (AMF) and the second network function is a short message service function (SMSF).

[0042] In an embodiment, the at least one information element (IE) includes an attribute-value pair (A VP), where the attribute of the AVP includes at least one of a current geographic location, a cell identifier (ID), a tracking area, a location area and a service area, and where the value is set to true when the information corresponding to the attribute is requested.

[0043] In an embodiment, the at least one cell parameter includes at least one of the cell ID, a tracking area identifier, a location area identifier, and a service area identifier.

[0044] In an embodiment, the at least one operation includes at least one of barring the cell ID in the network and storing a cell detail record (CDR) in a database.

[0045] In an embodiment, the location information includes a current location or a last known location of the at least one user equipment.

[0046] In an embodiment, the first network function and the second network function are configured to communicate through a service communication proxy (SCP).

[0047] In an exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium includes instructions that, when executed by one or more processors, cause the one or more processors to execute a method for retrieving at least one cell parameter associated with at least one user equipment (UE) in a network. The method includes receiving, by a first network function, at least one request from a second network function for providing at least one location information. The method includes extracting, by the first network function, at least one informationelement (IE) from the at least one received request. The method includes analyzing, by the first network function, the at least one extracted information element (IE) and generating at least one response. The method includes, based on the analysis, sending, by the first network function, the at least one response to the second network function and retrieving, by the second network function, the at least one cell parameter from the at least one response to perform at least one operation in the network.BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING

[0048] 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 is 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.

[0049] FIG. 1 illustrates an exemplary network architecture of a system for retrieving at least one cell identity (ID) associated with at least one user equipment (UE) in a network, in accordance with an embodiment of the present disclosure.

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

[0051] FIG. 3 illustrates an exemplary system architecture, in accordance with an embodiment of the present disclosure.

[0052] FIG. 4 illustrates an exemplary interaction between a short message service function (SMSF) and a network function (NF), in accordance with an embodiment of the present disclosure.

[0053] FIG. 5 illustrates an exemplary flow chart of a network function communicated in the network, in accordance with an embodiment of the present disclosure.

[0054] FIG. 6 illustrates a flow diagram of a mobile terminating (MT) flow in the network, in accordance with a prior art.

[0055] FIG. 7 illustrates an exemplary flow diagram of the MT flow in the network, in accordance with an embodiment of the present disclosure.

[0056] FIG. 8 illustrates an exemplary flow chart of a method for retrieving at least one ID associated with at least one UE in the network, in accordance with an embodiment of the present disclosure.

[0057] FIG. 9 illustrates an exemplary computer system in which or with which the embodiments of the present disclosure may be implemented.

[0058] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network architecture102 - User(s)104 - User Equipments (UEs)106 - Network108 - System200 - Block diagram202 - Processor(s)204 - Memory 206 - Interface(s)208 - Processing Engine210 - Database212 - Receiving Unit214 - Extracting Unit 216 - Analyzing Unit218 - Sending Unit300 - Exemplary System Architecture302- Short Message Service Function (SMSF)304- Unified Data Management (UDM) 306- Access and Mobility Management Function (AMF)400 - Flow Diagram500 - Flow Diagram502- Service Communication Proxy (SCP)600 - Flow Diagram602- Internet Protocol (IP) Short Message (IPSM)700 - Flow Diagram800 - Flow Diagram900 - Computer system910 - External Storage Device920 - Bus930 - Main Memory940 - Read Only Memory950 - Mass Storage Device960 - Communication Port970 - ProcessorDETAILED DESCRIPTION

[0059] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any ofthe features described herein. Example embodiments of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.

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

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

[0062] Also, it is noted that individual embodiments may be described as a process that is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.

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

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

[0065] The terminology used herein is to describe particular embodiments only and is not intended to be limiting the disclosure. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms “comprises” and / or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term “and / or” includes any combinations of one or more of the associated listed items. It should be noted that theterms “mobile device”, “user equipment”, “user device”, “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The invention is not limited to any particular type of device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.

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

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

[0068] In telecommunications, a cell identity (ID) is a unique identifier assigned to a specific cell in a network. The cell ID facilitates identifying the location of a UE connected to the specific cell. The network operators use the cell ID to implement the cell ID barring functionality for a user in the network. The cell ID barring is a network management technique that restricts access to mobile services based on the cell identity in which the user resides. By identifying the geographic location of a user equipment (UE) within specific cell coverage areas, network operators can prevent certain UEs from receiving services such as calls or messages in designated regions. The cell ID barring functionality serves various purposes, including regulatory compliance, where access is limited in sensitive areas; network load management, which helps alleviate congestion in high-traffic zones by barring new connections; and enhancing security by blocking service access in regions prone to fraud or other risks. In practice, the cell ID barring relies on network functions, such as the Short Message Service Function (SMSF), which stores and references relevantcell IDs during service requests. This process enables the network to determine whether to permit or deny access based on the location of the UE, ensuring efficient use of network resources and adherence to policy requirements.

[0069] Overall, the cell ID barring process enables the network operators to restrict access to certain cell towers or areas for specific UEs in the network. The cell ID barring functionality helps to maintain network quality by preventing too many users from connecting to congested cell towers. The network operator implements the cell ID barring based on certain criteria, such as subscription plan, roaming status, and network conditions.

[0070] Further, the network operators use various network functions to implement the cell ID barring in the network. The various network functions include a short message service function (SMSF), an access and mobility management function (AMF), a service communication proxy (SCP), and a unified data management (UDM). In existing methods, the SMSF utilizes a cell ID information for the cell ID barring in the network during a mobile terminating (MT) flow. The cell ID information helps to determine whether the UE falls into the cell coverage area. The MT flow is initiated from the AMF. The SMSF receives the cell ID from the AMF. The SMSF stores the received cell ID information in a UE context that is used for cell ID barring. The cell IDs of the existing users exist in a memory associated with the SMSF, while the cell IDs of the new users are absent in the SMSF. These cell IDs lack real-time updation at the SMSF. Hence, the cell barring faces failure. The cell ID barring process failure is due to inaccurate / stale cell IDs of the users in the network. The usage of stale cell IDs leads to configuration errors, mobility management issues, and signal interference.

[0071] The present disclosure relates to a method and a system for retrieving at least one cell ID of at least one UE in the network. The present disclosure employs customized flow integration with the AMF with a framework (for example, a ProvideLocationlnfo application programming interface (API)). To overcome theproblems associated with the stale sell ID information, the disclosed framework may enable the SMSF to obtain accurate cell ID data for both already activated users and new users. The disclosed framework may be seamlessly integrated into the MT flow, ensuring that the cell ID information of a target UE is both up-to-date and precise. By leveraging this integration, the SMSF can reliably receive the latest Cell ID information directly from the AMF during the MT flow, enhancing the overall effectiveness of network services. The method involves implementing the API in the MT flow that enables the SMSF to get accurate cell ID information for existing and new users in the network.

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

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

[0074] FIG. 1 illustrates an exemplary network architecture (100) of a system (108) for and retrieving at least one cell identity (ID) of at least UE (104) in a network (106), in accordance with an embodiment of the present disclosure.

[0075] In an aspect, the cell ID is a unique identifier assigned to each cell in the network. The cell ID enables distinguishing between one cell and another cell within the network. The cell ID is used for various network services, such as call routing, location tracking, and network optimization.

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

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

[0078] Additionally, in some embodiments, the UE (104) may include, but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a smartphone, a tablet 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 is 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 othercomputing device, wherein the UE (104) may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user (102) or the entity such as touchpad, touch-enabled screen, electronic pen, and the like. A person of ordinary skill in the art will appreciate that the UE (104) may not be restricted to the mentioned devices and various other devices may be used.

[0079] In FIG. 1, the UE 104 may communicate with the system (108) through the network (106). In particular, the UE (104) may be communicatively coupled with the network (106). The coupling includes steps of receiving, by the network (106), a connection request from the UE (104). Upon receiving the connection request, the coupling includes steps of sending, by the network (106), an acknowledgment of the connection request to the UE (104). Further, the coupling includes steps of transmitting a plurality of signals in response to the connection request.

[0080] Referring to FIG. 1, the UE (104) may communicate with the 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 fifth generation (5G) network, sixth generation (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.

[0081] 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 nodesthat 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 cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.

[0082] 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. The network (106) is configured to perform a method for retrieving the cell IDs of the UEs (104).

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

[0084] FIG. 2 illustrates an exemplary block diagram (200) of the system (108), for retrieving cell id associated with the UE (104) in the network (106) in accordance with an embodiment of the present disclosure. FIG. 2 is explained in conjunction with FIG. 1.

[0085] In an embodiment, 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, digital signal processors, central processing units, logic circuitries, and / or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (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 a Random-Access Memory (RAM), or a non-volatile memory such as an Erasable Programmable Read Only Memory (EPROM), a flash memory, and the like.

[0086] 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 (I / O), storage devices, and the like. The interface(s) (206) may facilitate communication through the system (108). The interface(s) (206) may also provide a communication pathway for one or more components of the system (108). Examples of such components include, but are not limited to, a processing engine (208) and a database (210).

[0087] In an embodiment, the system (108) may include a processing engine (208) that may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine (208). The processing engine (208) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that process data based on operational instructions. Among other capabilities, the processing engine (208) may beconfigured to fetch and execute computer-readable instructions stored in the memory (204) of the system (108). In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine (208) may be processorexecutable instructions stored on a non-transitory machine-readable storage medium, and the hardware for the processing engine (208) may comprise a processing resource (for example, one or more processors) to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine (208). In such examples, the system may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine- readable storage medium may be separate but accessible to the system and the processing resource. In other examples, the processing engine (208) may be implemented by electronic circuitry.

[0088] The system (108) is configured to retrieve at least one cell parameter associated with at least one UE (104) in the network that includes a first network function and a second network function.

[0089] The system (108) may comprise the first network function and the second network function. The first network function is the AMF (306) (e.g., AMF (306) as shown in FIG. 3), and the second network function is the SMSF (e.g., the SMSF (302) as shown in FIG. 3). The first network function and the second network function are configured to communicate through the SCP.

[0090] In an aspect, the AMF refers to a network function responsible for handling all access-related and mobility-related signaling between the UE (104) and the network. The AMF manages the UE’s (104) registration procedures, including attach, periodic updates, deregistration, and authentication. The AMF also establishes and maintains security, ensuring ciphering and integrity protection for signalingmessages. In addition, the AMF performs mobility management by maintaining the UE (104) context and coordinating handovers as the UE (104) moves across cells or tracking areas. The AMF serves as the primary control entity, ensuring secure, continuous, and seamless connectivity for the UE (104) within the network (106).

[0091] In an aspect, the SMSF is primarily responsible for facilitating the sending and receiving of Short Message Service (SMS) messages. By processing both incoming and outgoing SMS messages, the SMSF ensures that messages are accurately routed between senders and receivers, thus maintaining effective communication. The SMSF has the ability to interface with other network functions, such as the AMF and the SCP. This interaction allows the SMSF to retrieve essential user context information and manage message delivery based on the user's status and geographic location. For example, the SMSF may utilize the cell ID information to implement a cell ID barring, which restricts message delivery to certain areas, thereby enhancing service management and compliance with regulatory requirements. Further, the SMSF stores vital user context data, including active subscriptions and message preferences, which helps tailor the SMS experience for individual users. The SMSF is also equipped to handle various message types, including text messages, multimedia messages, and service-related alerts, further expanding its functionality within the mobile network ecosystem. The SMSF enables the sending, receiving and routing of messages in the network. The SMSF provides status updates regarding the message delivery to the user. The SMSF is configured to conduct subscription checks and perform a relay function between the UE (104) and the AMF.

[0092] In an aspect, the AMF and the SMSF communicate with each other through the SCP, which acts as a smart intermediary for routing and managing messages. When the AMF needs to deliver or receive SMS-related signaling for the UE (104), the AMF sends the request to the SCP instead of directly addressing the SMSF. The SCP then performs service discovery, forwards the message to theappropriate SMSF instance, and applies policies, such as load balancing, security filtering, or congestion control. This indirect communication via the SCP simplifies the network architecture, improves reliability, and ensures that messages between the AMF and SMSF are efficiently managed and correctly routed within the network.

[0093] In an aspect, the first network function may comprise the processing engine (208). The processing engine (208) includes a receiving unit (212), an extracting unit (214), an analyzing unit (216) and a sending unit (218).

[0094] The receiving unit (212) is configured to receive at least one request from the second network function for providing at least one location information. In an aspect, the location information comprises a current location or a last known location of the at least one UE (104).

[0095] In an aspect, the AMF receives the request from the SMSF. The SMSF may be configured to generate at least one request towards the AMF. For example, the at least one request may be a Hypertext Transfer Protocol (HTTP) request or an API request. The HTTP request may include a POST, a GET, and a PUT. For example, each HTTP request type serves distinct purposes: the POST request may be used to submit data to the AMF, the GET request can be utilized to request data retrieval, and the PUT request may be used to update existing resources. In another embodiment, the AMF may be configured to receive at least one request from the UE (104). The at least one request includes a connection request, a status request, a retrieval request, a forwarding request, and a delivery report request. For example, the UE (104) may initiate the connection request to connect with the AMF. The connection request may include a user identity, a requested service, and a network parameter. The user identity may include an International Mobile Subscriber Identity (IMSI), an International Mobile Equipment Identity (IMEI) and a user profile. The AMF may authenticate the user identity of the UE (104) and enable the connection with the network (106). The status request allows the UE (104) to request a status of the connection with the network(106). The UE (104) initiates the retrieval request to retrieve the connection details using the network (106). The delivery report request allows UE (104) to confirm whether the connection is established with the network (106).

[0096] In an aspect, the at least one request may be transmitted to retrieve at least one cell ID for at least one UE (104) in the network (106). The at least one request may include a retrieval request, a modification request, and an authentication request.

[0097] The retrieval request is a signaling message or service invocation used to obtain previously stored data from a network function or data repository. The retrieval request performs a read-only operation and returns subscriber information, policy data, or session context without modifying the stored records. For example, the retrieval request may include a user identifier, a timestamp, and a message. The user identifier may be a device ID, a session ID, or a Subscription Permanent Identifier (SUPI). The timestamp may include a date and time of request. The message may include a cause for accessing a location information of the UE (104). For example, the location information may include a current location of the user or a last known user location.

[0098] The modification request is a message that instructs the network function to update, replace, or alter existing stored data. The modification request performs a write or update operation on subscriber profiles, session parameters, or policy rules to change the current network state. For example, the modification request may be used for modifying the location information of the UE (104) in the AMF, if the UE (104) moves from one cell ID to another.

[0099] The authentication request is a control-plane message used to initiate or continue an authentication procedure. The authentication request delivers authentication challenge parameters to the UE (104), enabling verification of identity and establishment of cryptographic keys under authentication mechanisms. Forexample, the authentication request may be used to verify the UE (104) identity with the AMF.

[0100] In an aspect, the receiving unit (212) is configured to receive the at least one request from the second network function via the API or through standardized network interfaces. In an aspect, the API refers to a defined set of rules, protocols, and methods that allow two network functions to communicate with each other. The API may specify how requests should be made, how data should be formatted, and what responses should look like, enabling different applications, services, or network functions to interact in a standardized and controlled manner. The API acts as a bridge that lets one network function request information or services from another network function without needing to understand the internal workings of the network functions.

[0101] Upon receiving the at least one request, the receiving unit (212) validates and parses the at least one request to ensure its integrity before forwarding the request to the extracting unit (214) for further processing.

[0102] The extracting unit (214) is configured to extract at least one information element (IE) from the at least one received request. The extracting unit (214) is configured to process the validated request received from the receiving unit (212). The extracting unit’s primary function is to extract at least one information element (IE) from the request.

[0103] In an aspect, the at least one IE includes an attribute-value pair (AVP). The attribute of the AVP comprises at least one of a current geographic location, a cell identifier (ID), a tracking area, a location area and a service area. The value is set to true when the information corresponding to the attribute is requested. The current geographic location may be a physical location of the UE (104), such as a location coordinate with a latitude and longitude. The cell ID may be the identifier of a base station or a cell in which the UE (104) is currently connected. The tracking area maybe an area defined in the network (106) that efficiently tracks the UE (104). The AMF may parse and extract the at least one location parameter from the received request and store the location parameters in the memory or the database. For example, the at least one location parameter may be stored in the database in a table format. The table format may include at least one row and at least one column. The at least one location parameter is mapped with a UE identifier such as an International Mobile Equipment Identity (IMEI), and an International Mobile Subscriber Identity (IMSI). The at least one location parameter for each UE (104) is stored in an individual row mapped with the UE identifier.

[0104] In an aspect, the extracting unit (214) efficiently parses and structures IES, preparing the IES for the subsequent analytical stage. The extracting unit (214) may employ parsing logic or predefined schemas to accurately identify and extract relevant IEs based on the attributes requested.

[0105] The extracting unit (214) then inputs the extracted IE to the analyzing unit. The analyzing unit is configured to analyze the at least one extracted IE and generate at least one response based on the analysis. In an aspect, the analyzing unit (216) is used to analyze the received information, which may involve verifying the requested attributes, querying internal or external database resources, and applying logic to determine the availability or status of the requested cell parameters. The analyzing unit (216) generates at least one response that contains the requested cell parameters and associated data necessary for network operations, such as the current or last known location, cell ID, tracking area, location area, or service area. The analyzing unit (216) may also include security and policy compliance checks in accordance with network rules.

[0106] In an aspect, the AMF may be configured to analyse the received at least one request (also referred to as a ProvideLocationlnfo request) from the SMSF.

[0107] ProvideLocationlnfo Request is a service. ProvideLocationlnfo Request allows the NF (such as the AMF (306) or the SMSF (302)) to request the Location Management Function (LMF) to provide the UE’s location information. This request includes parameters like UE identity, location type (e.g., cell ID, GNSS coordinates), and accuracy requirements. The at least one request may contain the IE (also referred to as a flag) that indicates the status of the location information.

[0108] A req5GSLoc is defined as a mandatory boolean parameter that, when set to true, requests the retrieval of the UE (104) location information specifically within the 5G System (5GS) context. The req5GSLoc ensures that the returned data leverages 5G positioning capabilities such as NR-based measurements and 5G core integration, enabling high-accuracy and low-latency services for advanced applications like loT, autonomous systems, and emergency positioning.

[0109] For example, the IE may be designated as “req5GSLoc”, which signifies whether the location information of the UE (104) is being requested from the AMF. For instance, if “req5GSLoc” is set to "TRUE," it indicates that the location of the UE (104) is actively requested by the SMSF. Conversely, if “req5GSLoc” is set to "FALSE" (the default state), it signifies that the location information is not being requested by the system

[0110] The sending unit (218) is configured to send the at least one response to the second network function. In an aspect, the sending unit (218) is responsible for transmitting the generated response back to the second network function. The sending unit (218) packages the at least one response with the required cell parameter or location information and sends over the network (106), using secure and reliable communication channels. The sending unit (218) may check that responses are correctly addressed, formatted, and delivered within the expected timeframe

[0111] Upon receiving the response from the sending unit (218) of the first network function, the second network function is configured to retrieve the at least one cell parameter from the at least one response to perform at least one operation in the network. In an aspect, the at least one cell parameter comprises at least one of the cell ID, a tracking area identifier, a location area identifier, and a service area identifier. In an aspect, the at least one operation comprises at least one of barring the cell ID in the network and storing a cell detail record (CDR) in the database.

[0112] The second network function (i.e., SMSF) is configured to receive the at least one response having the location information from the AMF. For example, the AMF may send the location information of the UE (104) in the network (106). The location information may be included in a specific data parameter or field labeled ProvideLocationlnfo API. The ProvideLocationlnfo API field encompasses data, including the cell ID information, which is essential for the SMSF to accurately manage services and maintain effective communication based on the location of the UE. In an aspect, the cell ID information may include several key components that are essential for effective network management and service delivery. The cell ID information may include the at least one cell ID, which is a unique identifier for each specific cell tower. In an example, the cell ID information may include a Location Area Code (LAC), which groups multiple cells together to indicate the broader area in which a particular cell is located. In an example, the cell ID information may include a Global Navigation Satellite System (GNSS) coordinates to provide precise geographical positioning information, including latitude and longitude for the cell tower.

[0113] For example, the cell ID information may include a frequency band used by the cell tower, influencing service quality and coverage. Furthermore, the cell ID information may include details regarding the cell type, whether it is a macro cell, micro cell, or femtocell, along with the coverage area, which outlines the geographic region served by the cell. For example, the cell ID information may includeneighboring cell information, including their Cell IDs and signal strengths, which is crucial for handover processes and maintaining service continuity. Collectively, the comprehensive Cell ID information is vital for optimizing user experiences based on location and ensuring efficient network operations.

[0114] In an embodiment, the second network function may be configured to retrieve the at least one cell ID from the location information from the received response from the AMF. The second network function may be configured to store the retrieved cell ID(s) in the database (210) For example, the second network function may parse the response. The parsing involves reading and fetching the location information from the response. The second network function may fetch the “providelocationinfo” parameter from the response and fetch the location information of the requested UE (104).

[0115] In an embodiment, the second network function may be configured to manage the cell IDs in the database (210) for performing cell ID barring in the network. The second network function may store the one or more cell IDs in the database (210). For example, the one or more cell IDs stored in a table format. The one or more cell IDs may be mapped with a user identity. The user identity may be an IMEI, an IMSI, and an IP address.

[0116] In an aspect, the SMSF initially may not have the cell ID information in a Mobile terminating (MT) Flow for the new users. The cell ID for existing activated users is stale as it is not up-to-date and is the one that was stored in the UE (104) context during user activation.

[0117] The SMSF may send the ProvideLocationlnfo request to the AMF which contains a data structure (IE) named as “RequestLocInfo” and the data structure contains a flag called as “req5gsLoc”. This field ‘req5gsLoc’ that the SMSF sets in the request to indicate the AMF to send back the current cell ID information. The flag shallbe present and set to "true", if 5GS location information is requested in NPLI (Network Provided Location Information). The NPLI refers to the data that a telecommunications network provides about the geographic position of the UE (104) within its coverage area.

[0118] The AMF may check the “req5gsLoc” flag value and if true then send the location information in the response (data structure named as ProvideLocationlnfo). The location information provided by the AMF contains accurate cell ID information which may be further used by the SMSF.

[0119] The SMSF may use the accurate cell ID for the cell ID barring in a Public Land Mobile Network (PLMN) in the MT flow, and may also be used for the CDR purpose. The CDRs can further be used for reporting and analytics.

[0120] The system (108) reliably receives, processes, analyzes, and communicates cell parameters associated with the UE (104), facilitating flexible and secure operation in modern communication networks.

[0121] FIG. 3 illustrates an exemplary system architecture (300) in accordance with an embodiment of the present disclosure.

[0122] In an embodiment, the system architecture (300) comprises the SMSF (302), the UDM (304), the AMF (306) and the UE (104).

[0123] In an embodiment, the SMSF (302) may be configured to ensure the short message service (SMS) functionalities such as routing, forwarding, and delivery of messages in the network. In an example, the SMSF (302) may include one or more components. The one or more components include a service control function (SCF), a service data function (SDF) and a SMS interworking function (IWF). The one or more components are configured to manage the control plane functions such as session management, authentication and routing decisions. The SCF handles the user datarelated to SMS, such as temporary storage and delivery reports. In an aspect, the SMSF uses an Internet protocol (IP)- based protocol for interworking with an Internet protocol short message gateway (IPSM-GW). The IP-SM-GW acts as a bridge between the IP services and the network (106). The IP-SM-GW manages the routing of data packets between the network (106) to ensure the IP-SM-GW reach their intended destination. The SMSF (302) may be configured to communicate with a Gateway Mobile Switching Center (MSC) for SMS (SMS-GMSC) or an Interworking MSC for SMS (SMS- IWMSC), or an SMS router. The SMSF (302) may communicate with the SMS- GMSC / SMS-IWMSC / SMS router to retrieve the routing information needed for routing the short message to serve the UE (104) in the network (106). The SMS-GMSC may be configured to route SMS messages to an appropriate destination by determining the recipient's current location. The SMS-GMSC accomplishes this by querying a Home Location Register (HLR) to obtain necessary subscriber information, ensuring that messages are directed to the correct SMSC or directly to the intended UE (104). In addition to handling incoming messages, the SMS-GMSC facilitates communication between the SMSC and the mobile switching center, ensuring efficient delivery of SMS traffic across the network. The SMS-IWMSC enables SMS communication across different network technologies, such as GSM and CDMA, as well as legacy systems. The SMS-IWMSC handles protocol translation, ensuring that messages from one network type can effectively communicate with another. Additionally, the SMS- IWMSC integrates various messaging services, providing a seamless user experience regardless of the network. The SMS-GMSC and SMS-IWMSC ensure that SMS messages are routed, delivered, and interoperable across diverse mobile networks, enhancing overall communication capabilities for users. The SMSF (302) may communicate with other NFs using a Nsmsf interface. The Nsmsf interface may enable the activation or deactivation of SMS services for the UE (104).

[0124] In an embodiment, the UDM (304) may be configured to enable efficient and cohesive user and service data management across the network (106). The UDM(304) may serve as a centralized database for managing user profiles, subscriptions, and service data. The UDM (304) ensures that all NFs access consistent and up-to-date information of the UE (104). The UDM (304) may communicate with the NFs using a Nudm interface. The Nudm is a service-based interface for the UDM (304).

[0125] In an embodiment, the AMF (306) may be configured to handle the registration of the UE (104) to the network (106) and authenticate the UE (104) based on the user identity, such as an IMEI to ensure authorized users access the network. The AMF (306) manages user session establishment, modification, and release by coordinating with the NFs to ensure efficient data flow. The AMF (306) may communicate with the other network function (NF) using a Namf. The Namf interface may be a service-based interface. In an aspect, the UE (104) may communicate with the AMF (306) using a N1 interface. The N1 interface is used by the UE (104) for transmitting non-radio signaling between the UE (104) and the AMF (306).

[0126] FIG. 4 illustrates an exemplary interaction (400) between the SMSF (302) and the network function, in accordance with an embodiment of the present disclosure.

[0127] In an embodiment, the SMSF (302) may be configured to send the at least one request to the NF. In an example, the NF may be the AMF (306). The at least one request may include the HTTP request or the API request.

[0128] At step 402, the SMSF (302) may be configured to send the POST request to the AMF (306) with a Uniform Resource Identifier (URI). The URI may be a "provide-loc-info". The “provide-loc-info” may include one or more types of location parameters. The types of location parameters include a currentLoc, a location, a geoinfo, a locationAge, a timezone. For example, the SMSF (302) sends a request such as POST / {ueContextId} / provide-loc-info (RequestLocInfo). The “provide-loc-info” may provide the location information of the UE (104) from the AMF (306). The AMF(306) may access a Network Provided Location Information (NPLI) service to gather the location information. The NPLI is responsible for retrieving the location information of the UE (104) in the network (106). The POST request includes a "requestLocInfo" data structure indicating the desired type of location information. For example, if the SMSF (302) desires to retrieve the current location information of the UE (104), the SMSF (302) may set "reqCurrentLoc" attribute to "true".

[0129] A reqCurrentLoc is defined as an optional boolean parameter that specifies whether the system (108) should return the current location of the UE (104) or the last known location. The reqCurrentLoc distinction is required for scenarios where real-time positioning is required versus historical location data, impacting latency and resource allocation strategies.

[0130] The AMF (306) may initiate a paging procedure to the UE (104). If the paging procedure is successful, the AMF (306) may respond with the current location information and set "currentLoc" attribute to "true" in the response. Conversely, if the UE (104) does not respond to the paging, the AMF (306) may provide the last known location and set "currentLoc" attribute to "false" in the response.

[0131] In an aspect, the RequestLocInfo may be any attribute such as a req5gsLoc, a reqCurrentLoc, a reqRatType, and a reqTimeZone.

[0132] A reqRatType is defined as a boolean indicator that, when set to true, requests the Radio Access Technology (RAT) type associated with the UE (104) (e.g., NR for 5G, LTE for 4G). This attribute enables multi-RAT positioning and supports network optimization by providing context on the UE’s (104) connectivity environment.

[0133] A reqTimeZone is defined as a boolean parameter that, when enabled, retrieves the UE’s (104) local time zone information. The reqTimeZone is essential forcontext-aware services, billing, and compliance with regional regulations, and can be leveraged in applications requiring synchronization across distributed systems.

[0134] The req5gsLoc is set as “TRUE” when the SMSF (302) requests the 5GS location information from the AMF (306). Otherwise, the req5gsLoc is set to “FALSE”, when the location of the UE (104) is not requested by the SMSF (302).

[0135] At step 404, the AMF (306) may send a response to the SMSF (302) with a status code. The status code may be "200 OK" for successful retrieval of the "ProvideLocInfo" data structure from the NPLI service for the UE (104). In case of failure, the AMF (306) may respond with a status code such as a “307 temporary redirect”, a “308 permanent redirect”, a “403 Forbidden,” and a “404 Not Found”.

[0136] FIG. 5 illustrates an exemplary flow chart (500) of a method for retrieving at least cell ID associated with the at least one UE (104) in the network (106), in accordance with an embodiment of the present disclosure.

[0137] In an embodiment, the SMSF (302) may communicate with the SCP (502). The SCP (502) may communicate with the AMF (306).

[0138] At step 504, the SMSF (302) may initiate at least one request ((Providelocationinfo request) to the SCP (502). The SCP (502) is configured to facilitate and manage the interactions between different NFs. The SCP (502) may route the incoming request to the appropriate NF based on the request. For example, the at least one request may be the providelocationinfo request. The providelocationinfo request allows the SMSF (302) to request the NPLI of the UE (104) in the network (106). The providelocationinfo request may be the HTTP request such as the POST request. At step 506, the providelocationinfo request may be forwarded to the AMF (306). The providelocationinfo comprises an IE that indicates the AMF (306) to send back the current cell ID information of the UE (104) in the network (106).

[0139] At step 508, the AMF (306) may send the response to the SCP (502). For example, the response may be the HTTP response. The response may be a providelocationinfo response.

[0140] At step 510, the response may be forwarded from the SCP (502) to the SMSF (302). For example, the response (Providelocationinfo response) may include a providelocinfo parameter (location information). The providelocinfo parameter may comprise the cell ID of the requested UE (104). The SMSF (302) may use the cell ID for the cell ID barring functionality. The cell ID is stored as the call detail record (CDR) for reporting and analysis of the network performance.

[0141] FIG. 6 illustrates a flow diagram (600) of a mobile terminating (MT) flow in the network (106), in accordance with a prior art.

[0142] At step 604, the Internet protocol short message gateway (IPSM) (602) may initiate a mobile terminating (MT) request (MT REQUEST) towards the SMSF (302). The MT REQUEST refers to a network-initiated procedure to deliver signaling or user data to the UE (104). Unlike mobile-originated requests, which start from the UE (104), MT requests originate from the network (106) and require the UE (104) to be reachable.

[0143] For example, the MT request is initiated by the IPSM (602) to determine the location of the UE (104) to perform one or more network services based on the cell ID information. In an aspect, the IPSM (602) may initiate the MT request by receiving a request from an external system. The external system may be configured to employ the one or more network services including the cell ID barring, the call forwarding, the roaming service, the call routing, and the traffic management. For example, the cell ID barring service involves blocking or restricting access to certain cell towers or network coverage areas within the network (106).

[0144] At step 606, the SMSF (302) triggers the Namf MT EnableReachability request towards the SCP (502). The Namf_MT_EnableReachability procedure, under the AMF (306) MT service, is a critical operation that ensures the UE (104) can be reached for the MT signaling or data delivery. The Namf MT EnableReachability request is initiated by network functions such as the SMSF (302) or SMF when the Namf_MT_EnableReachability need to deliver messages or initiate sessions to the UE (104) that may be in an idle state.

[0145] The request may be the HTTP request, such as the PUT request sent to the SCP (502). At step 608, the SCP (502) forwards the Namf_MT_EnableReachability request to the AMF (306). For example, the Namf MT EnableReachability request may be invoked by the SMSF (302) to enable the reachability of the AMF (306). The Namf MT EnableReachability request informs the AMF (306) that a specific UE should be reachable for incoming service requests, such as voice calls or SMS messages.

[0146] At step 610, the AMF (306) processes the Namf MT EnableReachability request and sends a Namf MT EnableReachability response to the SCP (502). At step 612, the SCP (502) sends the Namf MT EnableReachability response to the SMSF (302). The primary purpose of the Namf MT EnableReachability response is to communicate the result of the reachability request back to the SCP (502). For example, the AMF (306) may send the response with a response code. The response code may include “200 OK”, “307 temporary indirect”, “403 Forbidden”, and “404 Not found”. The “200 OK” response code indicates that the AMF (306) is reachable.

[0147] In the MT message flow, when evaluating Cell ID barring, the location information acquired by the AMF 306 through a UEReachability request. The UEReachability request is not accurate and may be stale. At step 614, the SMSF (302) may send Namf_Communication_NlN2Message Transfer (SMS body) to the SCP(502). The Namf_Communication_NlN2MessageTransfer operation, N1 and N2 is used to transfer messages from a network function (such as SMSF (302) or SMF) to the UE (104) via the AMF (306). For SMS delivery in 5G, the SMS payload is encapsulated within the N1 message container (NAS-level signaling), while optional N2 information may carry RAN-level signaling for session setup or optimization.

[0148] At step 616, the SCP (502) forwards the received Namf_Communication_NlN2MessageTransfer (SMS body) to the AMF (306). For example, the NlN2MessageTransfer is used by the SMSF (302) to transfer N1 and / or N2 information to the AMF (306) using the SCP (502). The NlN2Message Transfer may be a HTTP request that includes the SUPI, a session ID, a quality of service(QoS) parameter, and a paging policy indication.

[0149] At step 618, the AMF (306) may send an acknowledgment to the SCP (502) for the received SMS body. The acknowledgement may be sent using an Nsmsf_SMService_Uplink SMS Control Plane Acknowledgment (CP- ACK) message. Nsmsf-SMService_Uplink SMS CP-ACK message is a Network Addressing and Switching (NAS)-layer control-plane acknowledgement message for SMS over NAS in 5G. Nsmsf_SMService_Uplink SMS CP-ACK message confirms receipt of a CP-DATA message carrying SMS payloads (e.g., SMS-SUBMIT or SMS-DELIVER) between the UE (104) and the SMSF (302) via the AMF (306). The primary purpose of the CP-ACK message is to confirm the successful receipt of a service uplink SMS sent by the SCP (502).

[0150] At step 620, the SCP (502) receives and forwards the Nsmsf_SMService_Uplink SMS CP-ACK message to the SMSF (302). For example, the AMF (306) may send the CP-ACK message in an uplink Non-Access Stratum (NAS) transport message to acknowledge that the SMSF (302) received the N1N2 transfer message (SMS body). The CP-ACK notifies the SMSF (302) that theAMF (306) has received the N1N2 message (SMS body), and no additional copies are expected from the SMSF (302).

[0151] At step 622, the AMF (306) may generate a delivery report regarding the delivery of the SMS body. The Nsmsf_SMService_UplinkSMS delivery report may be used as a response for delivering the report.

[0152] At step 624, the delivery report may be forwarded to the SMSF (302) using the response Nsmsf_SMService_UplinkSMS delivery report. For example, the delivery report summarizes the MT flow process, including the status of the request, a timestamp, a UE identity, a network parameter and a UE location. Nsmsf_SMService_UplinkSMS Delivery Report refers to the NAS-level message flow in 5G SMS over NAS where the UE (104) sends a delivery status acknowledgment for a previously received SMS. Nsmsf_SMService_UplinkSMS Delivery Report operation carries an RP-ACK (SMS -DELIVER-REPORT) encapsulated in CP-DATA via the Nsmsf_SMService_UplinkSMS service from the UE (104) to the SMSF (302) through the AMF (306). Nsmsf_SMService_UplinkSMS Delivery Report confirms successful receipt of an SMS-DELIVER message and ensures end-to-end reliability in mobile-terminated SMS scenarios.

[0153] At step 626, the SMSF (302) sends the received delivery report to the IPSM (602). For example, the delivery report may include a message ID, a delivery status, an error code, a timestamp and a message content. The delivery report represents the details of processing the requests at the AMF (306).

[0154] At step 628, the SMSF (302) sends the acknowledgment for the delivery report using a Namf_Communication_NlN2 MessageTransfer (CP- ACK) message to the SCP (502). At step 630, the SCP (502) forwards the Namf_Communication_NlN2 MessageTransfer (CP-ACK) message to the AMF (306). For example, the AMF (306)may send an acknowledgment message regarding the delivery of the delivery report to the IPSM (602).

[0155] As explained in FIG. 6, in SMSF (302), accurate Cell ID information is required in CDR during SMS flows. However, in the MT flows where the Cell ID barring applies, the system (108) currently retrieves stale Cell ID data, resulting in inaccurate location information. Additionally, when the AMF (306) checks the Cell ID barring using the UEReachability API, the location details obtained are often outdated and unreliable. This limitation necessitates the involvement of additional APIs to ensure accuracy and is explained in detail in FIG. 7.

[0156] FIG. 7 illustrates a flow diagram (700) of a mobile terminating (MT) flow in the network (106), in accordance with an embodiment of the present disclosure.

[0157] At step 702, the IPSM (602) may initiate the mobile terminating (MT) request (MT REQUEST) towards the SMSF (302). For example, the MT REQUEST is initiated by the IPSM (602) to the SMSF (302) to determine the location of the UE (104) to perform the one or more network services based on the cell ID information.

[0158] At step 704, the SMSF (302) may send a ProvideLocationlnfo request to the SCP (502).

[0159] At step 706, the SCP (502) may forward the received ProvideLocationlnfo request to the AMF (306). For example, the ProvideLocationlnfo request may be the HTTP request, such as the POST request. The POST request may include the IE to indicate the status of the location information. The IE may be a req5GSLoc parameter that may be used by the SMSF (302) to indicate the AMF (306) to send the current location information of the UE (104). If the req5GS is set as TRUE, the AMF (306) may send the current location information to the SMSF (302). Otherwise, if the req5GSLoc is set as FALSE, the AMF (306) may not send the location information to the SMSF (302).

[0160] At step 708, the AMF (306) sends the response (Provi deLocationinfo) for the received request to the SCP (502). The response may be a ProvideLocationlnfo response.

[0161] At step 710, the SCP (502) forwards the response received from the AMF (306) to the SMSF (302). For example, the AMF (306) sends the response to the SMSF (302) using the SCP (502). The response may include a data parameter such as a “ProvideLocInfo”. The providelocinfo may include a currentLoc, a location, a geoInfo, a locationAge, a ratType, a timezone, and a supported features. The currentLoc comprises the present location of the UE (104), if the IE is set as TRUE. Otherwise, the currentLoc comprises a last known location of the UE (104), if the IE is set as FALSE.

[0162] At step 712, the SMSF (302) triggers the Namf MT EnableUEReachability request to the SCP (502). The Namf MT EnableUEReachability operation, allows the network function to request the AMF (306) to enable or confirm the UE (104) reachability for mobile-terminated services such as SMS or loT data delivery.

[0163] At step 714, the SCP (502) forwards the Namf MT EnableUEReachability request to the AMF (306). For example, the Namf_MT_EnableUEReachability request may be invoked by the SMSF (302) to enable the reachability of the AMF (306).

[0164] At step 716, the AMF (306) processes the Namf MT EnableUEReachability request and sends a Namf MT EnableUEReachability response to the SCP (502). For example, the AMF (306) may send the response with a response code. The response code may include “200 OK”, “307 temporary indirect”, “403 Forbidden”, and “404 Not found”. The “200OK” response code indicates that the AMF (306) is reachable. At step 718, the SCP (502) forwards the Namf_MT_EnableUEReachability response to the SMSF (302).

[0165] At step 720, the SMSF (302) may send Namf_Communication_NlN2Message Transfer (SMS body) to the SCP (502). At step 722, the SCP (502) forwards the received Namf_Communication_NlN2MessageTransfer (SMS body) to the AMF (306). For example, the N1N2 message transfer is used by the SMSF (302) to transfer N1 and / or N2 information to the AMF (306) using the SCP (502).

[0166] At step 724, the AMF (306) may send an acknowledgment to the SCP (502) for the received SMS body. The acknowledgement may be sent using an Nsmsf_SMService_UplinkSMS CP-ACK message.

[0167] At step 726, the SCP (502) receives and forwards the acknowledgement to the SMSF (302). The acknowledgement may be forwarded using the Nsmsf_SMService_UplinkSMS CP-ACK message. The CP-ACK notifies the SMSF (302) that the AMF (306) has received the N1N2 message (SMS body), and no additional copies are expected from the SMSF (302).

[0168] At step 728, the AMF (306) may generate a delivery report regarding the delivery of the SMS body. The Nsmsf_SMService_UplinkSMS delivery report may be used as a response for delivering the report.

[0169] At step 730, the delivery report may be forwarded to the SMSF (302) using the response Nsmsf_SMService_UplinkSMS delivery report. For example, the delivery report summarizes the MT flow process including the status of the request, a timestamp, a UE identity, a network parameter and a UE location.

[0170] At step 732, the SMSF (302) sends the received delivery report to the IPSM (602). For example, the delivery report may include a message ID, a deliverystatus, an error code, a timestamp and a message content. The delivery report represents the details of processing the requests at the AMF (306).

[0171] At step 734, the SMSF (302) sends the acknowledgment for the delivery report using the Namf_Communication_NlN2MessageTransfer (CP- ACK) message to the SCP (502).

[0172] At step 736, the SCP (502) forwards the acknowledgment message to the AMF (306). The acknowledgment message may be a Namf_Communication_NlN2 MessageTransfer (CP- ACK) message. For example, the AMF (306) may be sent an acknowledgement message regarding the delivery of the delivery report to the IPSM (602).

[0173] FIG. 8 illustrates an exemplary flow chart of the method (800) for retrieving at least one ID associated with at least one UE (104) in the network (106), in accordance with an embodiment of the present disclosure.

[0174] At step 802, the method (800) begins with the first network function receiving a request from the second network function for specific location information. The first network function is the AMF (306) and the second network function is the SMSF (302). In an embodiment, the request may pertain to one or more UEs (104) and is received from the second network function (i.e., SMSF (302)), by the first network function (i.e., AMF (306)), the at least one request via API. The location information comprises a current location or a last known location of the at least one the UE (104).

[0175] At step 804, upon receiving the request, the first network function extracts one or more IES from the received request. In an embodiment, IES may include the AVPs, where the attributes specify the type of information requested such as current location, cell ID, tracking area, location area, or service area, and the values indicate whether the information is requested set to true.

[0176] At step 806, the first network function analyzes the extracted information elements. Based on this analysis, the first network function generates an appropriate response. In an embodiment, collecting or determining the requested cell parameter data, such as the current or last known cell ID, the tracking area identifier, the location area identifier, or service area identifier for the specified UE (104).

[0177] At step 808, the first network function sends the generated response, which includes the requested cell parameter information, back to the second network function. In an embodiment, the exchange between the first and second network functions may be mediated by the SCP (502) to facilitate secure and efficient communication.

[0178] At step 810, the second network function receives the response and retrieves the at least one cell parameter from the at least one response to perform at least one operation in the network (106). The second network function may then use the retrieved cell parameter to perform specific operations within the network. In an embodiment, the specific operations include operations such as barring the identified cell in the network (106) or storing the CDR in the database (210) for further processing or compliance purposes.

[0179] FIG. 9 illustrates an exemplary computer system (900) in which or with which embodiments of the present disclosure may be implemented.

[0180] As shown in FIG. 9, the computer system (900) may include an external storage device (910), a bus (920), a main memory (930), a read-only memory (940), a mass storage device (950), a communication port (960), and a processor (970). A person skilled in the art will appreciate that the computer system (900) may include more than one processor (970) and communication ports (960). The processor (970) may include various modules associated with embodiments of the present disclosure.

[0181] In an embodiment, the communication port (960) 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 fibre, a serial port, a parallel port, or other existing or future ports. The communication port (960) may be chosen depending on the network (106), such as a Local Area Network (LAN), a Wide Area Network (WAN), or any network to which the computer system (900) connects.

[0182] In an embodiment, the memory (930) may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. Read-only memory (940) 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 (970).

[0183] In an embodiment, the mass storage device (950) may be any current or future mass storage solution, which may be used to store information and / or instructions. Exemplary mass storage solutions include, but are not limited to, 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 Lirewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks (e.g., SATA arrays).

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

[0185] Optionally, operator and administrative interfaces, e.g., a display, keyboard, joystick, and cursor control device, may also be coupled to the bus (920) to support direct operator interaction with the computer system (900). Other operator and administrative interfaces may be provided through network connections connected through the communication port (960). The components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system (900) limit the scope of the present disclosure.

[0186] In an embodiment, a computer program product includes a non- transitory computer-readable medium include instructions that, when executed by one or more processors, cause the one or more processors to execute the method (800) for retrieving at least one cell parameter associated with at least one UE (104) in the network (106) The method (800) includes receiving, by a first network function, at least one request from a second network function for providing at least one location information. The method (800) includes extracting, by the first network function, at least one information element (IE) from the at least one received request. The method (800) includes analyzing, by the first network function, the at least one extracted information element (IE) and generating at least one response. The method (800) includes, based on the analysis, sending, by the first network function, the at least one response to the second network function and retrieving, by the second network function, the at least one cell parameter from the at least one response to perform at least one operation in the network (106).

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

[0188] The method (800) and system (108) of the present disclosure may be implemented in a number of ways. For example, the methods and systems of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless specifically stated otherwise. Further, in some embodiments, the present disclosure may also be embodied as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.

[0189] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be implemented merely as illustrative of the disclosure and not as a limitation.The present disclosure offers the method and the system for retrieving at least one cell parameter associated with at least one the UE in the network. The present disclosure provides technical advancement by addressing the issue of outdated or inaccurate cell ID information in the SMSF, especially in mobile terminated (MT) SMS flows. The technical advancement overcomes drawbacks of conventional APIs by enabling a customized flow between the SMSF and AMF using the ProvideLocationlnfo API, where the SMSF sets a request parameter ('req5gsLoc') to ensure the AMF returns themost current cell ID. This ensures accurate cell ID logging in CDRs and for cell barring operations, overcoming unreliable data in prior solutions. The present disclosure further provides technical advancement by adapting and extending the ProvideLocationlnfo API specifically for real-time cell ID retrieval in the MT SMS flow, a use not previously considered, thus delivering reliable data and improved operational accuracy over prior approaches.ADVANTAGES OF THE PRESENT DISCLOSURE

[0190] The present disclosure described herein above has several technical advantages including, but not limited to a method and a system for retrieving at least one cell parameter associated with at least one user equipment (UE) in a network.

[0191] The present disclosure enables automated and accurate retrieval of cell parameters from network requests, improving network responsiveness.

[0192] The present disclosure allows dynamic acquisition of cell and location information, enhancing operational flexibility and network control in functions such as cell barring and record storage.

[0193] The present disclosure facilitates reliable communication between network functions through defined interfaces, supporting scalable and modular integration.

[0194] The present disclosure improves location-based services by providing current and last known device locations, advancing targeted messaging and emergency communications.

[0195] The present disclosure supports system and software compatibility with various network configurations, allowing easy implementation through software updates and reducing deployment costs.

[0196] The present disclosure streamlines information retrieval, lowers latency, and optimizes workflows by minimizing manual steps.

[0197] The present disclosure is versatile, with applicability across various networks and operations, ensuring broad utility for future telecommunication needs.

Claims

CLAIMS1. A method (800) for retrieving at least one cell parameter associated with at least one user equipment (UE) (104) in a network (106), the method (800) comprising: receiving, by a first network function, at least one request from a second network function for providing at least one location information; extracting, by the first network function, at least one information element (IE) from the at least one received request; analyzing, by the first network function, the at least one extracted information element (IE) and generating at least one response based on the analysis; and sending, by the first network function, the at least one response to the second network function; and retrieving, by the second network function, the at least one cell parameter from the at least one response to perform at least one operation in the network (106).

2. The method (800) as claimed in claim 1, further comprising: receiving, by the first network function, the at least one request via an application programming interface (API).

3. The method (800) as claimed in claim 1, wherein the first network function is an access and mobility management function (AMF) (306), and the second network function is a short message service function (SMSF) (302).

4. The method (800) as claimed in claim 1, wherein the at least one information element (IE) comprises an attribute-value pair (A VP), wherein the attribute of the AVP comprises at least one of a current geographic location, a cell identifier(ID), a tracking area, a location area and a service area, and wherein the value is set to true when the information corresponding to the attribute is requested.

5. The method (800) as claimed in claim 1, wherein the at least one cell parameter comprises at least one of the cell ID, a tracking area identifier, a location area identifier, and a service area identifier.

6. The method (800) as claimed in claim 4, wherein the at least one operation comprises at least one of barring the cell ID in the network (106) and storing a cell detail record (CDR) in a database (210).

7. The method (800) as claimed in claim 1, wherein the location information comprises a current location or a last known location of the at least one user equipment (104).

8. The method (800) as claimed in claim 1, wherein the first network function and the second network function are communicated through a service communication proxy (SCP) (502).

9. A system (108) for retrieving at least one cell parameter associated with at least one user equipment (UE) (104) in a network (106) comprising a first network function and a second network function, wherein the first network function comprising: a receiving unit (212) configured to receive at least one request from the second network function for providing at least one location information; an extracting unit (214) configured to extract at least one information element (IE) from the at least one received request;an analyzing unit (216) configured to analyze the at least one extracted information element (IE) and generate at least one response based on the analysis; and a sending unit (218) configured to send the at least one response to the second network function, wherein the second network function is configured to retrieve the at least one cell parameter from the at least one response to perform at least one operation in the network.

10. The system (108) as claimed in claim 9, wherein the receiving unit is configured to receive the at least one request from the second network function via an application programming interface (API).

11. The system (108) as claimed in claim 9, wherein the first network function is an access and mobility management function (AMF) (306), and the second network function is a short message service function (SMSF) (302).

12. The system (108) as claimed in claim 9, wherein the at least one information element (IE) comprises an attribute-value pair (A VP), wherein the attribute of the AVP comprises at least one of a current geographic location, a cell identifier (ID), a tracking area, a location area and a service area, and wherein the value is set to true when the information corresponding to the attribute is requested.

13. The system (108) as claimed in claim 9, wherein the at least one cell parameter comprises at least one of the cell ID, a tracking area identifier, a location area identifier, and a service area identifier.

14. The system (108) as claimed in claim 12, wherein the at least one operation comprises at least one of barring the cell ID in the network and storing a cell detail record (CDR) in a database (210).

15. The system as (108) claimed in claim 9, wherein the location information comprises a current location or a last known location of the at least one user equipment (104).

16. The system (108) as claimed in claim 9, wherein the first network function and the second network function are configured to communicate through a service communication proxy (SCP) (502).

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 (800) for retrieving at least one cell parameter associated with at least one user equipment (UE) (104) in a network (106), the method (800) comprising: receiving, by a first network function, at least one request from a second network function for providing at least one location information; extracting, by the first network function, at least one information element (IE) from the at least one received request; analyzing, by the first network function, the at least one extracted information element (IE) and generating at least one response based on the analysis; and sending, by the first network function, the at least one response to the second network function; and retrieving, by the second network function, the at least one cell parameter from the at least one response to perform at least one operation in the network (106).

Images