System and method for managing location information of customer premise equipment in communication network

Abstract

Disclosed is a system (300) and a method (700) managing location information of a Customer Premise Equipment (CPE) (106) in a communication network (100). The system (300) includes a service module (330) i.e., a dedicated microservice for managing the location information of the CPE through a database (340). The service module (330) a location operation request for the CPE (106) from a Fulfilment Management System (FMS) (320) and identifies whether the location operation request corresponds to a data fetch operation or a data update operation for the location information of the CPE (106). Thereafter, the service module (330) fetches the location information of the CPE (106) from the database (340) in response to a determination that the location operation request corresponds to the data fetch operation and transmits the location information of the CPE (106) to the FMS (320).

Description

SYSTEM AND METHOD FOR MANAGING LOCATION INFORMATION OF CUSTOMER PREMISE EQUIPMENT IN COMMUNICATION NETWORKTECHNICAL FIELD

[0001] The embodiments of the present disclosure generally relate to the field of networks and systems. More particularly, the present disclosure relates to a system and a method for managing Customer Premise Equipment (CPE) monitoring in a communication network.BACKGROUND OF THE INVENTION

[0002] The subject matter disclosed in the background section should not be assumed or construed to be prior art merely due to its mention in the background section. Similarly, any problem statement mentioned in the background section or its association with the subject matter of the background section should not be assumed or construed to have been previously recognized in the prior art.

[0003] With the advent of technological advancement in the field of telecommunications, several wireless technologies have been developed to meet growing number of broadband subscribers for providing better applications and services. As mobile and cellular communication networks experience growing data demands, there is a strong emphasis on achieving maximum throughput for users and ensuring uninterrupted service.

[0004] In modern communications networks, efficiency and accuracy of locationbased services are crucial for maintaining optimal network performance. To this end, for adopting network resources and services to evolving requirements, dynamic needs of location change requests need to be addressed. Heretofore, conventional methods for managing location changes of network elements have not been successful since the same relied on static configurations and lacked robustmechanisms for real time updates, leading to inefficiencies and potential disruptions in service.

[0005] Furthermore, the conventional methods involved manual processes and outdated automation techniques, thereby causing delays in processing the location change requests, causing sub optimal resource allocation and service interruptions. Moreover, the conventional methods lacked integration with provisioning information Application Programming Interfaces (APIs) from Fulfilment Management Systems (FMS), which is critical for ensuring that location changes are accurately reflected across the network infrastructure. This handling of the location change requests and provisioning data in isolation led to inconsistencies and errors. Due to lack of a unified mechanism for processing these requests, risk of misconfiguration and reduced network reliability. This fragmentation further hampers the network’s ability to efficiently manage and adapt to changes, impacting overall network performance and user experience. Additionally, the conventional methods do not offer adequate support for dynamic, real-time adjustments in network management.

[0006] In view of the aforementioned challenges, there is a need for a solution that can seamlessly handle the location change requests and interact with provisioning information APIs to ensure accurate and timely updates of location information.SUMMARY

[0007] The following embodiments present a simplified summary in order to provide a basic understanding of some aspects of the disclosed invention. This summary is not an extensive overview, and it is not intended to identify key / critical elements or to delineate the scope thereof. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.

[0008] According to an embodiment of the present disclosure, a method for managing location information of a Customer Premise Equipment (CPE) in acommunication network is provided. The method includes receiving, by a transceiver unit at a service module in a Gateway Mobile Location Centre (GMLC), a location operation request for the CPE from a Fulfilment Management System (FMS). The location operation request corresponds to a data fetch operation or a data update operation for the location information of the CPE. The method further includes fetching, by a fetching unit at the service module, the location information of the CPE from a database in response to a determination that the location operation request corresponds to the data fetch operation. Furthermore, the method includes transmitting, by the transceiver unit, the location information of the CPE to the FMS.

[0009] In some aspects of the present disclosure, the method further includes updating, by an update unit of the service module, the location information of the CPE in the database in response to a determination that the location operation request corresponds to the data update operation. Moreover, the method includes transmitting, by the transceiver unit, the updated location information of the CPE to the FMS.

[0010] In some aspects of the present disclosure, the location information comprises latitude and longitude coordinates of the CPE.

[0011] In some aspects of the present disclosure, the location operation request is transmitted through an Application Programming Interface (API) as an API request that enables the service module to retrieve or update the location information in the database.

[0012] In some aspects of the present disclosure, the service module is triggered periodically to process the location information of the CPE.

[0013] In some aspects of the present disclosure, the API request is a Representational State Transfer (REST) based API request.

[0014] In some aspects of the present disclosure, the service module corresponds to a Gateway Mobile Location Centre - Positioning Client (GMLC-PC) microservice.

[0015] According to another embodiment of the present disclosure, a system manage location information of Customer Premise Equipment (CPE) in a communication network is provided. The system includes a transceiver unit and a fetching unit, each at a service module in a Gateway Mobile Location Centre (GMLC). The transceiver unit is configured to receive a location operation request for the CPE from a Fulfilment Management System (FMS). The location operation request corresponds to a data fetch operation or a data update operation for the location information of the CPE. The fetching unit is configured to fetch the location information of the CPE from a database in response to a determination that the location operation request corresponds to the fetch operation. The transceiver unit is further configured to transmit the location information of the CPE to the FMS.BRIEF DESCRIPTION OF DRAWINGS

[0016] Various embodiments disclosed herein will become better understood from the following detailed description when read with the accompanying drawings. The accompanying drawings constitute a part of the present disclosure and illustrate certain non-limiting embodiments of inventive concepts. Further, components and elements shown in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. For the purpose of consistency and ease of understanding, similar components and elements are annotated by reference numerals in the exemplary drawings.FIG. 1 is a diagram illustrating an exemplary communication network, in accordance with an embodiment of the present disclosure.FIG. 2 is a diagram illustrating exemplary components of a network, in accordance with an embodiment of the present disclosure.FIG. 3 illustrates a block diagram depicting exemplary components of a system to manage location information of a Customer Premise Equipment (CPE) in a communication network, in accordance with an embodiment of the present disclosure.FIG. 4 illustrates exemplary components of a Gateway Mobile Location Centre server, in accordance with an embodiment of the present disclosure.FIG. 5 illustrates a line diagram depicting a process depicting operations of managing the location information of the CPE in the communication network, in accordance with an embodiment of the present disclosure.FIG. 6 is a flow chart that presents a method for managing the location information of the CPE in the communication network, in accordance with an embodiment of the present disclosure.LIST OF REFERENCE NUMERALS

[0017] The following list is provided for convenience and in support of the drawing figures and as part of the text of the specification, which describe innovations by reference to multiple items. Items not listed here may nonetheless be part of a given embodiment. For better legibility of the text, a given reference number is recited near some, but not all, recitations of the referenced item in the text. The same reference number may be used with reference to different examples or different instances of a given item. The list of reference numerals is as follows:100 - Communication network102 - Core network104 - Nodes106 - Network devices / Customer Premises Equipment (CPE)108 - User devices202 - Access and Mobility Management Function (AMF) node204 - Policy Control Function (PCF) node206 - Equipment Identity Register (EIR) node208 - Authentication Server Function (AUSF) node210 - Unified Data Management (UDM) function node212 - Subscriber Profile Repository (SPR) node214 - Short Message Service Function (SMSF) node216 - Network Slice Selection Function (NSSF) node218 - Location Management Function (LMF) node220 - Session Management Function (SMF) node222 - Network Data Analytics Function (NWDAF) node224 - Charging Function-Protocol Converter (CHF -PC) node226 - Network Exposure Function (NEF) node228 - Signaling Transfer Point (STP) node230 - Diameter Routing Agent (DRA) node232 - Binding Support Function (BSF) node234 - Gateway Mobile Location Center (GMLC) node238 - User Plane Function (UPF) node240 - Location Services (LCS) client node300 - System to managing CPE monitoring in the communication network310 - Customer Order Management (COM) system320 - Fulfillment Management System (FMS)330 - Service Module332 - GMLC - Positioning Client (GMLC-PC) Unit(s)332-1 - Transceiver Unit332-2 - Update Unit332-3 - Determination Unit332-4 - Fetching Unit340 - Database402 - Processor(s)404 - Memory404-1 - Instructions Repository406 - Communication interface408 - Scheduler412 - Communication bus500 - Process for managing the location information of CPE502-512 - Operational steps of the process 500600 - Method for managing the location information of CPE602-610 - Operational blocks of the method 600DETAILED DESCRIPTION OF THE INVENTION

[0018] Inventive concepts of the present disclosure will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of one or more embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Further, the one or more embodiments disclosed herein are provided to describe the inventive concept thoroughly and completely, and to fully convey the scope of each of the present inventive concepts to those skilled in the art. Furthermore, it should be noted that the embodiments disclosed herein are not mutually exclusive concepts. Accordingly, one or more components from one embodiment may be tacitly assumed to be present or used in any other embodiment.

[0019] The following description presents various embodiments of the present disclosure. The embodiments disclosed herein are presented as teaching examples and are not to be construed as limiting the scope of the present disclosure. The present disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, including the exemplary design and implementation illustrated and described herein, but may be modified, omitted, or expanded upon without departing from the scope of the present disclosure.

[0020] The following description contains specific information pertaining to embodiments in the present disclosure. The detailed description uses the phrases “in some embodiments” or “some implementations” which may each refer to one or more or all of the same or different embodiments or implementations. The term “some” as used herein is defined as “one, or more than one, or all.” Accordingly, the terms “one,” “more than one,” “more than one, but not all” or “all” would all fall under the definition of “some.” In view of the same, the terms, for example, “in an embodiment” or “in an implementation” refers to one embodiment or oneimplementation and the term, for example, “in one or more embodiments” refers to “at least one embodiment, or more than one embodiment, or all embodiments ”. Further, the term, for example, “in one or more implementations” refers to “at least one implementation, or more than one implementation, or all implementations.

[0021] The term “comprising,” when utilized, means “including, but not necessarily limited to;” it specifically indicates open-ended inclusion in the so-described one or more listed features, elements in a combination, unless otherwise stated with limiting language. Furthermore, to the extent that the terms “includes,” “has,” “have,” “contains,” and other similar words are used in either the detailed description, such terms are intended to be inclusive in a manner similar to the term “comprising.”

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

[0023] The description provided herein discloses exemplary embodiments only and is not intended to limit the scope, applicability, or configuration of the present disclosure. Rather, the foregoing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing any of the exemplary embodiments. Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it may be understood by one of the ordinary skilled in the art that the embodiments disclosed herein may be practiced without these specific details.

[0024] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein the description, the singular forms "a", "an", and "the" include plural forms unless the context of the invention indicates otherwise.

[0025] The terminology and structure employed herein are for describing, teaching, and illuminating some embodiments and their specific features and elements and do not limit, restrict, or reduce the scope of the present disclosure. Accordingly, unless otherwise defined, all terms, and especially any technical and / or scientific terms, used herein may be taken to have the same meaning as commonly understood by one having ordinary skill in the art.

[0026] The present disclosure relates to a system and a method for managing (i.e., fetching and / or updating location information) of a Customer Premise Equipment (CPE) in a communication network. An aspect of the present disclosure is to provide seamless handling location change requests of the CPEs in the communication network and interact with provisioning information Application Programming Interfaces (APIs) to ensure accurate and timely updates of the location information of each requested CPE in the communication network. Another aspect of the present disclosure is to facilitate flexibility and control over management of CPEs in the communication network.

[0027] The term “Customer Premise Equipment (CPE)” refers to a physical device located at a customer’s premises that connects to a communication network for access to data or telecommunication services. The CPE may include, but is not limited to, routers, gateways, modems, or fixed wireless access terminals, and may support 4G, 5G, beyond 5G, or 6G network connectivity.

[0028] The term “network connection type” refers to the radio access technology currently used by a CPE or wireless device, such as Long-Term Evolution (LTE) (i.e., 4G) or NR (i.e., 5G). The network connection type determines which service modules or procedures are invoked in the GMLC for location services, including use of the AMF in 5 G or Mobility Management Entity (MME) in 4G.

[0029] Embodiments of the present disclosure will be described below in detail with reference to the accompanying drawings. FIG. 1 through FIG. 6, discussed below, and the one or more embodiments used to describe the principles of the present disclosure are by way of illustration only and should not be construed in any way tolimit the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged system or device.

[0030] FIG. 1 illustrates an exemplary environment of a communication network 100, in accordance with an embodiment of the present disclosure. As illustrated in FIG. 1, the communication network 100 includes a core network 102 coupled with a plurality of nodes including Node 104-1 through Node 104-N. The core network 102 is configured to facilitate a secured communication among the plurality of nodes (collectively referred to as the “nodes 104”, and individually referred to as the “node 104”, hereinafter).

[0031] The term “node 104” may refer to any component (or collection of components) configured to provide wireless access to a network. Examples of the node 104 may include, but not limited to, a Transmit Point (TP), a Transmit-Receive Point (TRP), an Evolved Base Station (eNodeB or eNB), a 5G / NR base station (gNB), a macrocell, a femtocell, a Wi-Fi Access Point (AP), or other wirelessly enabled devices. The nodes 104 may provide wireless access to the network in accordance with wireless communication protocols, e.g., 5G / NR 3GPP New Radio interface / access (NR), LTE, LTE-A, High Speed Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc. Aspects of the present disclosure are intended to include, or otherwise cover, any technology (known or later developed) bearing same or similar characteristics as of the above-mentioned BS, without deviating from the scope of the present disclosure. For the sake of convenience, the terms “nodes” and “gNBs” are used interchangeably in the present disclosure to refer to network infrastructure components that provide wireless access to remote terminals.

[0032] The gNB 104 provides wireless broadband access to the network for a plurality of network devices 106-1 to 106-n (collectively referred to as “network devices 106”) within a serving region of the gNB 104. The network devices 106 may be wired or wireless. Examples of the network devices 106 may include, but not limited to, Outdoor Customer Premise Equipment (ODCPE), an IndoorCustomer Premise Equipment (IDCPE), and the like. In some embodiments, the gNBs 104 may communicate with each other and with the network devices 106 using a communication technique, such as a 5th Generation 5G / New Radio (NR), Long Term Evolution (LTE), Long Term Evolution Advanced (LTE-A), Worldwide Interoperability for Microwave Access (WiMAX), Wireless Fidelity (Wi-Fi), or other wireless communication techniques.

[0033] Further, depending on the network connection type, the term “network device 106” may refer to any component such as “mobile station,” “subscriber station,” “remote terminal,” “wireless terminal,” “receiver terminal”. In a nonlimiting example, the “device” in this disclosure wirelessly accesses the nodes (i.e., gNB 104). In a non-limiting example, the CPE 106 disclosed herein may correspond to the ODCPE or IDCPE which is designed to transmit, receive, or process wireless signals for communication purposes, typically utilizing radio frequency technology, and may include components such as antennas, transmitters, receivers, and processors. The term “CPE” or “ODCPE” are used interchangeably throughout the disclosure without any deviation from the scope of the present disclosure.

[0034] In an embodiment, each of the network devices 106 are coupled with one or more user devices 108-1, 108-2, 108-3, 108-4, through 108-(N-l), 108-N (collectively referred to as the “user devices 108”, and individually referred to as the “user device 108”, hereinafter) directly or via a fixed wireless device connected with the network device 106. The User device 108 may correspond to, but is not limited to, any of mobile devices, tablets, or portable devices utilized by subscribers or users to access services provided by the core network 102. In some aspects of the present disclosure, the network device 106, when installed in the premises of a user (i.e., a customer of network service(s) rendered through the communication network 100), may also be referred to as the Customer Premises Equipment (CPE) 106.

[0035] In one aspect, the core network 102 may establish a secured communication between the one or more user devices 108 associated with the plurality of nodes104. In another aspect, the core network 102 may establish a secured communication between the one or more user devices 108 associated with the same node 104.

[0036] In one embodiment, the core network 102 may effectively establish a secured communication between the user device 108-1 and the user device 108-2 or the CPE 106-1 and the CPE 106-2, where the user device 108-1 and the user device 108-2 or the CPE 106-1 and the CPE 106-2 both are coupled with the Node 104-1. In another embodiment, the core network 102 may establish a secured communication between the user device 108-1 or the CPE 106-1 and the user device 108-N or the CPE 106-n, where the user device 108-1 or the CPE 106-1 is coupled with the Node 104-1 and the user device 108-N or the CPE 106-n is coupled with the Node 104-N.

[0037] In an exemplary embodiment, the core network 102 (also, referred to as network 102, herein) may be configured as an application server and may be communicably operational or may be integrated with the user device 108 via a network coupled with a server. The core network 102 may pertain to 5G servicebased architecture and may be configured to interconnect distinct networks associated with the architecture. Therefore, the core network 102 may provide a path for the exchange of information between one or more of the networks, and corresponding subnetworks.

[0038] Although FIG. 1 illustrates one example of the communication network 100, various changes may be made to FIG. 1. For example, the communication network 100 may include any number of nodes, CPEs, and / or user devices in any suitable arrangement, without deviating from the scope of the present disclosure. Further, various components in FIG. 1 may be combined, further subdivided, or omitted and additional components may be added according to particular needs.

[0039] FIG. 2 illustrates an exemplary block diagram depicting components of the core network 102, in accordance with an embodiment of the present disclosure. As shown in FIG. 2, the core network 102 connects the network device 106 such as theCPE or the ODCPE to a Radio Access Network (RAN) 236 including the plurality of nodes 104.

[0040] As shown in FIG. 2, the communication system may include the network device (e.g., CPE 106), a Radio Access Network (RAN) 236 i.e., node 104 configured to communicate with an Access and Mobility Management Function (AMF) 202, a Unified Data Management (UDM) function 210, a Network Exposure Function (NEF) 226, and a Gateway Mobile Location Center (GMLC) 234. In some aspects of the present disclosure the CPE 106 is configured to communicate with a plurality of network elements of the core network 102.

[0041] The plurality of network elements of the core network 102 includes the Access and Mobility Management Function (AMF) node 202 (alternatively referred to as AMF 202), a Policy Control Function (PCF) node 204 (alternatively referred to as PCF 204), an Equipment Identity Register (EIR) node 206 (alternatively referred to as EIR 206), an Authentication Server Function (AUSF) node 208 (alternatively referred to as AUSF 208), a Unified Data Management (UDM) node 210 (alternatively referred to as UDM 210), a Subscriber Profile Repository (SPR) node 212 (alternatively referred to as SPR 212), a Short Message Service Function (SMSF) node 214 (alternatively referred to as SMSF 214), a Network Slice Selection Function (NSSF) node 216 (alternatively referred to as NSSF 216), a Location Management Function (LMF) node 218 (alternatively referred to as LMF 218), a Session Management Function (SMF) node 220 (alternatively referred to as SMF 220), a Network Data Analytics Function (NWDAF) node 222 (alternatively referred to as NWDAF 222), a Charging Function-Protocol Converter (CHF -PC) node 224 (alternatively referred to as CHF -PC 224), a Network Exposure Function (NEF) node 226 (alternatively referred to as NEF 226), a Signaling Transfer Point (STP) node 228 (alternatively referred to as STP 228), a Diameter Routing Agent (DRA) node 230 (alternatively referred to as DRA230), a Binding Support Function (BSF) node 232 (alternatively referred to as BSF 232), a Gateway Mobile Location Center (GMLC) node 234 (alternatively referred to as GMLC 234), a User PlaneFunction (UPF) node 238 (alternatively referred to as UPF 238), and a Location Services (LCS) client node 240 (alternatively referred to as LCS 240).

[0042] The components depicted in FIG. 2 may be implemented as dedicated hardware components or as virtualized functions implemented on top of a common shared physical infrastructure using Software-Defined Networking (SDN). For example, an SDN controller may implement one or more of the components of FIG. 2 using an adapter implementing a Virtual Network Function (VNF) virtual machine, an event driven serverless architecture interface, and / or another type of SDN architecture.

[0043] The AMF 202 may be a network element that is capable of performing registration management, connection management, reachability management, mobility management, lawful intercepts, SMS transport between the user device(s) 108 and SMSF 214, session management messages transport between the user device(s) 108 and the SMF 220, access authentication and authorization, location services management, functionality to support non-3GPP access networks, and / or other types of management processes.

[0044] The PCF 204 is a network node capable of supporting policies to control network behavior, provide policy rules to control plane functions (e.g., to the SMF 220), access subscription information relevant to policy decisions, perform policy decisions, and / or perform other types of processes associated with policy enforcement.

[0045] The EIR 206 may correspond to an independent network component that may help telecom operators in protecting the telecom networks. The EIR 206 can aid in protecting a network by providing a mechanism to restrict malicious user terminals or devices in the network. The AUSF 208 may be a network element capable of performing authentication.

[0046] The UDM 210 may be a network element capable of maintaining subscription information for user devices 108, manage subscriptions, generateauthentication credentials, handle user identification, perform access authorization based on subscription data, perform network function registration management, maintain service and / or session continuity by maintaining assignment of the SMF 220 for ongoing sessions, support SMS delivery, support lawful intercept functionality, and / or perform other processes associated with managing user data.

[0047] The SPR 212 corresponds to a centralized repository for storing subscriber profile information, service entitlements, and policy rules within the network. The SMSF 214 may be a network element capable of performing SMS services for the user devices 108. The NSSF 216 includes one or more devices that select network slice instances for the user devices 108. By providing network slicing, the NSSF 216 allows an operator to deploy multiple substantially independent end-to-end networks potentially with the same infrastructure.

[0048] The LMF 218 may be a network element capable of managing subscriber location information within the core network 102. The LMF 218 may track the current location of mobile devices, handles location updates, and supports mobility management functions such as handover and roaming. The LMF 218 may interface with network elements such as the RAN 236, the AMF 202, and location -based service platforms to ensure seamless mobility management and location-based service provisioning for the subscribers.

[0049] The SMF 220 may be a network element capable of performing session establishment, session modification, and / or session release, perform IP address allocation and management, perform Dynamic Host Configuration Protocol (DHCP) functions, perform selection and control of the UPF 238, configure traffic steering at the UPF 238 to guide the traffic to the correct destinations, terminate interfaces toward the PCF 204, perform lawful intercepts, charge data collection, support charging interfaces, control and coordinate of charging data collection, terminate session management parts of NAS messages, perform downlink data notification, manage roaming functionality, and / or perform other types of control plane processes for managing user plane data.

[0050] The NWDAF 222 may be a network element capable of collecting analytics information associated with RAN and / or the core network 102. The CHF -PC 224 may be a network element capable of controlling and managing charging-related operations within the network. The CHF -PC 224 coordinates communication between a CHF, the PCF 204, and session management entities to ensure accurate and timely charging of subscriber services. The CHF PC 224 resides at the edge of the 4G and 5G networks. The CHF-PC 224 acts as a protocol converter for interactions with the existing 4G network diameter protocol-based online charging system to convert an HTTP / 2 message received from SMF and PCF in 5G network, to diameter messages before forwarding them to the online charging system and vice versa. The CHF-PC 224 has a highly scalable cluster which supports conversion for credit control (Gy / N40) and spending limit information (Sy / N28) exchange.

[0051] The NEF 226 may be a network element capable of exposing capabilities and events to other NFs, including third party NFs, AFs, edge computing NFs, and / or other types of NFs. The STP 228 may be a node configured to route signaling messages based a destination point code in core network 102. Specifically, the STP 228 acts a router that relays network messages between signaling end points and other signal transfer points in the core network 102.

[0052] The DRA 230 may be configured as a centralized diameter routing point, ensuring that diameter messages are directed to appropriate network elements (e.g., PCF 204, SMSF 214, CHF-PC 224, BSF 232). The DRA 230 may further be configured for load balancing and ability to route traffic based on specific fields or policies, enhancing the efficiency of network operations. The BSF 232 may be a network element capable of managing session bindings and subscriber contexts within the core network 102.

[0053] The GMLC 234 is a network element configured to provide location-based services within the 5G core network. The GMLC 234 facilitates the retrieval of mobile device location information, enabling services such as emergency call routing, location-based advertising, device location management, and asset trackingetc. The GMLC 234 may interface with location-based service applications and network elements to provide accurate location data while ensuring user privacy and compliance with regulatory requirements. The GMLC 234 may serve as a gateway for location-based queries and requests. In some aspects of the present disclosure, the GMLC 234 is communicatively coupled with the AMF 202, the UDM 210, and the NEF 226 via NLt, NLs, and Nlf interfaces within the core network 102. Particularly, the NLt interface connects the GMLC 234 to AMF 202, the NLs interface connects the GMLC 234 to the UDM 210, and the NLf interface connects the GMLC to the NEF 226.

[0054] The LCS client 240 may be a network element capable of enabling provisions of location-based functionalities and applications within the core network 102. The LCS client 240 may interface with application servers, service platforms, and subscriber devices to deliver personalized and context-aware location-based experiences.

[0055] The UPF 238 may be a network element capable of maintaining an anchor point for intra / inter-Radio Access Technology (RAT) mobility, maintain an external Packet Data Unit (PDU) point of interconnect to Data Network (DN) 242, perform packet routing and forwarding, perform the user plane part of policy rule enforcement, perform packet inspection, perform lawful intercept, perform traffic usage reporting, perform Quality of Service (QoS) handling in the user plane, perform uplink traffic verification, perform transport level packet marking, perform downlink packet buffering, forward an “end marker” to the RAN 236 (e.g., gNB), and / or perform other types of user plane processes.

[0056] Although FIG. 2 shows exemplary components of core network 102, in other implementations, the core network 102 may include fewer components, different components, differently arranged components, or additional components than depicted in FIG. 2. Additionally, or alternatively, one or more components of the core network 102 may perform functions described as being performed by one or more other components of the core network 102.

[0057] FIG. 3 illustrates a block diagram depicting an architecture of a system 300 for managing location information of the CPE 106 in the communication network 100, in accordance with an exemplary embodiment. The embodiment of the system 300 as shown in FIG. 3 is for illustration only. However, the system 300 may come in a wide variety of configurations, and FIG. 3 does not limit the scope of the present disclosure to any particular implementation of the system 300.

[0058] As shown in FIG. 3, the system 300 includes the AMF node 202, the LMF node 218, a Customer Order Management (COM) system 310 (hereinafter also referred to as “order care system 310”), a Fulfillment Management System (FMS) 320, the GMLC node 234, and a database 340. Each entity in the system 300 may be communicatively coupled with the other entities in the system 300.

[0059] The GMLC 234 (hereinafter interchangeably referred to as ‘the GMLC node 234’) may utilize a service module 330 hosting a plurality of microservices. For example, the service module 330 may include a microservice for managing the location information of the CPE 106 (in the database 340). Specifically, the microservice in the service module 330 may fetching location information of the CPE 106 and / or updating the location information of the CPE 106 in the database 340. In some aspects of the present disclosure, the service module 330 corresponds to a Positioning Client (PC) module, where the microservice is a GMLC Positioning Client (GMLC-PC) 332 microservice. The microservice is an independently deployable software in which complex applications are composed of small and independent processes. The microservice may be developed as a suite of small services, each running in its own process and communicating with lightweight mechanisms such as Application Programming Interface (API). The microservice may adhere to a well-defined API. The service module 330 is communicatively coupled with the AMF 202 and the LMF 218 via the NLt and NLs interfaces, respectively, within the core network 102. Preferably, the service module 330 may include multiple operational units (e.g., GMLC-PC units 332) configured to perform operational steps for the service module (i.e., specifically, for managing the location information of the CPE 106 in the database 340).

[0060] The COM system 310 corresponds to an order care system (alternatively referred to and designated as “order care system 310”) configured to manage customer orders or requests for managing operation(s) related to the managing information of the location of an equipment (for example, the CPE 106) in the communication network 100. Specifically, the orders or requests may correspond to fetching / updating the location information of the CPE 106 from / into the database 340. Typically, such a controlled monitoring of the location information of the CPE(s) 106 in the communication network 100 enhances the accuracy of location information of the CPE(s) 106 in the communication network 100. The COM system 310 forwards a location operation request for the CPE 106 to the FMS 320. The FMS 320 acquires CPE information (or CPE parameters) corresponding which the request is received by the FMS 320 including, but not limited to, a Subscriber Permanent Identifier (SUPI) of the CPE 106 and / or geographical location (i.e., latitude / longitude coordinates) of the CPE 106. Preferably, the service module 330, via the GMLC-PC units 332, may process the CPE parameters for managing the location information of the CPE 106 in the communication network 100 (through the database 340).

[0061] The FMS 320 is configured to process the location operation request received from the COM system 310 and acquire the CPE information including, but not limited to, the Subscriber Permanent Identifier (SUPI) and the geographical location of the CPE 106. The FMS 320 is further configured to send the location operation request along with the CPE information to the service module 330 (specifically to the GMLC-PC units 332) for managing the location information of the CPE 106 in the communication network 100. Typically, the location operation request may be a location request that corresponds to fetching (or obtaining) the location information of the CPE 106 from the database 340 or an update location request corresponding to updating the location information of the CPE 106 into the database 340.

[0062] In some aspects of the present disclosure, each operation unit of the GMLC- PC units 332 may be configured as a micro service component capable of processingthe monitoring request using the CPE information. The GMLC-PC units 332 may be configured to support the FMS 320 for managing the location information of the CPE 106 in the communication network 100 through the database 340 and sending a response message to the FMS 320 rendering the location information of the CPE 106, as requested through the location operation request.

[0063] The database 340 may be configured to store information related to the network components received from the FMS 320 including the CPE information. The database 340 may be implemented as one or more of centralized database, Relational Database Management System (RDBMS), non-relational database management system, hierarchical database management system, network database management system, an in-memory database including a distributed in-memory data storage, or a distributed database.

[0064] FIG. 4 illustrates exemplary components of the GMLC 234, in accordance with an embodiment of the present disclosure. The embodiment of the GMLC node 234 as shown in FIG. 4 is for illustration only. However, the GMLC node 234 may come in a wide variety of configurations, and FIG. 4 does not limit the scope of the present disclosure to any particular implementation of the GMLC node 234. The GMLC 234 may include the service module 330, processor(s) 402, memory 404, a communication interface 406, and a scheduler 408. Each entity of the GMLC 234 may be communicatively coupled to each other by way of a communication bus 412.

[0065] The processor(s) 402 may include processing circuitry, logic, interface(s), and / or code(s), and may be configured to communicate with the memory 404, the communication interface 406, the scheduler 408, and the service module 330 via the communication bus 412. Examples of the communication bus 412 may include, but are not limited to, a Peripheral Component Interconnect (PCI) / PCI Extended (PCI- X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB), and a Front Side Bus (FSB). Aspects of the present disclosure are intended to include or otherwise cover any type of coupling means present or related to later developedtechnologies, that may be configured to connect the processor(s) 402 to the other subsystems of the GMLC 234, as the communication bus 412, without deviating from the scope of the present disclosure.

[0066] The processor(s) 402 may be configured to execute instructions (hereinafter also referred to as “a set of instructions”) stored in the memory 404 (by way of instructions repository 404-1) and to perform a variety of operations pertaining to the management of the location information of the CPE 106 in the communication network 100. The processor(s) 402 may also include a plurality of processing engines i.e., information processing units for controlling overall operation of the GMLC 234. For example, the processor(s) 402 may be configured to execute computer-implemented programs and / or instructions stored in the memory 404. The processor(s) 402 are further configured to move data into or out of the memory 404 as required by an execution process.

[0067] In some aspects of the present disclosure, the processor(s) 402 may include one or more data processors, including a general-purpose processor, such as, for example, and without limitation, a Central Processing Unit (CPU), an Application Processor (AP), a dedicated processor, a graphics-only processing unit such as a Graphics Processing Unit (GPU) or the like, a programmable logic device, or any combination thereof.

[0068] In an embodiment, the service module 330 may be implemented as a combination of hardware and software programming (for example, programmable instructions) to implement one or more functionalities of the GMLC 234. In nonlimiting examples, described herein, such combinations of hardware and software programming may be implemented in several different ways, without deviating from the scope of the present disclosure. The service module 330 may include suitable logic, circuitry, interfaces, and / or codes. For example, the programming for the service module 330 may be processor-executable instructions stored on a non- transitory machine-readable storage medium and the hardware for the service module 330 may comprise a processing resource (for example, one or moreprocessors), to execute such instructions. In an embodiment, the service module 330 may be subdivided into different operational modules / units (e.g., the GMLC-PC units 332). In an exemplary embodiment, the service module 330 may be triggered periodically by the GMLC 234 (e.g., in response to an indication by the FMS 320) to process the location information of the CPE 106. Preferably, the FMS 320 sends the location operation request for the CPE 106 to the service module 330 through an Application Programming Interface (API) as an API request, which enables the service module 330 to retrieve or update the location information of the CPE 106 in the database 340. In some aspects of the present disclosure, the API request is a Representational State Transfer (REST) based API request.

[0069] According to an embodiment of the present disclosure, the machine-readable storage medium may store instructions that implement the service module 330 (specifically, the GMLC-PC units 332), when executed by the processing resource. In such examples, the GMLC node 234 may also 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 GMLC node 234 and the processing resource. In other examples, the service module 330 may be implemented using an electronic circuitry.

[0070] In an exemplary embodiment of the present disclosure, the service module 330 may include multiple GMLC-PC units 332. Specifically, the GMLC-PC units 332 may include a transceiver unit 332-1, an update unit 332-2, a determination unit 332-3, a fetching 332-4, and a generation unit 332-5, communicatively coupled to one another. The processor(s) 402 may serve as execution unit(s) providing circuitry for operations of the GMLC-PC units 332.

[0071] Preferably, the transceiver unit 332-1 may be configured to enable exchange of request(s), input(s), data, signal(s), trigger(s), instructions, and / or notification(s), between the GMLC-PC units 332 and other components of the core network 102. Particularly, the transceiver unit 332-1 may be configured to receive the location operation request for the CPE 106 from the FMS 320. The location operation requestmay either be the location request corresponding to extraction (or fetching of) the location information of the CPE 106 from the database 340 or the update location request corresponding to updating the location information of the CPE 106 into the database 340. The determination unit 332-3 may be configured to determine (or identify) whether the location operation request is the location request or the update location request. When the determination unit 332-3 determines that the location operation request is the location request, the determination unit 332-3 may trigger the fetching unit 332-4 for further operations. Else, when the determination unit 332-3 determines that the location operation request is the update location request, the determination unit 332-3 may trigger the update unit 332-2 for further operations.

[0072] The update unit 332-2 may be configured to update the location information of the CPE 106 in the database 340 in response to the trigger from the determination unit 332-3 (i.e., generated based on the determination that the location operation request corresponds to the data update operation). Thereafter, the transceiver unit 332-1 may be configured to transmit the updated location information of the CPE 106 to the FMS 320. In some aspects of the present disclosure, the updated location information of the CPE 106 is rendered through the COM system 310.

[0073] The fetching unit 332-4 may be configured to fetch location information of the CPE 106 from the database 340 based on the trigger from the determination unit 332-3 (i.e., triggered in response to a determination that the location operation request corresponds to the data fetch operation). Thereafter, the transceiver unit 332- 1 may be configured to transmit the location information of the CPE 106 to the FMS 320. In some aspects of the present disclosure, the location information of the CPE 106 is rendered through the COM system 310.

[0074] In some aspects of the present disclosure, the fetched / updated location information of the CPE 106 is shared by the transceiver unit 332-1 in the form of a response message including latitude and longitude coordinates of the CPE 106. Theresponse message may be shared to the FMS 320 or to the COM system 310 (via the FMS 320) by the transceiver unit 332-1.

[0075] Various units of the GMLC-PC units 332 are presented to illustrate the functionality driven by the service module 330 for managing the location information of the communication network 100 through the database 340. It will be apparent to a person having ordinary skill in the art that various units in the GMLC- PC units 332 are for illustrative purposes and not limited to any specific combination of hardware circuitry and / or software.

[0076] In some aspects of the present disclosure, the service module 330 may host multiple microservices. Among the micro services, a microservice may correspond to the GMLC-PC 332 microservice. The GMLC 234 may utilize a multiple computing resources where the plurality of microservices may be deployed, and multiple storage devices may be provided in the computing resource for each microservice.

[0077] The microservices may correspond to a network architecture, where independent microservices communicate over APIs, enabling modular, scalable, and resilient network management applications. The microservices may refer to individual components that perform specific tasks within the GMLC 234, for example, GMLC-PC 332 microservice could be responsible for acquiring the realtime location information corresponding to the CPE 106 from the LMF 218 and sharing the response message to one of the COM system 310 or the FMS 320 via the transceiver unit 332-1.

[0078] As will be appreciated by a person of ordinary skill in the art, it must be understood that the microservices platform may also be hosted outside the GMLC 234 in a similar manner utilizing the resources of a computing device separate from the GMLC 234 itself. The service module 330 may make a call to the microservices for synchronization of flow of data between various components of the GMLC 234 and performing other tasks within the system 300.

[0079] The memory 404 includes the instructions repository 404-1 that stores the set of instructions required by the processor 402 for controlling its overall operations. A part of the memory 404 may include a Random Access Memory (RAM), a cache memory, or a Read Only Memory (ROM). The memory 404 may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories.

[0080] In an embodiment of the present disclosure, the instructions repository 404- 1 is configured to store computer program instructions and / or codes for operation(s) of various components of the service module 330. For example, the instructions repository 404-1 may be configured to store computer program instructions corresponding to the operation(s) performed by the service module 330 for managing the location information of the CPE 106 in the communication network 100. In an embodiment of the present disclosure, the instructions repository 404-1 may be configured as a non-transitory storage medium. Examples of the instructions repository 404-1 configured as the non-transitory storage medium includes hard drives, solid-state drives, flash drives, Compact Disk (CD), Digital Video Disk (DVD), and the like. Aspects of the present disclosure are intended to include or otherwise cover any type of non-transitory storage medium as the instructions repository 404-1, without deviating from the scope of the present disclosure. As will be appreciated, any such computer program instructions stored in the instructions repository 404-1 may be executed by one or more computer processors, including without limitation a general-purpose computer or special purpose computer, or other programmable processing apparatus to produce a machine, such that the computer program instructions which execute on the computer processor(s) or other programmable processing apparatus create means for implementing the function(s) specified.

[0081] In addition, the memory 404 may, in some examples, be considered a non- transitory storage medium. The "non -transitory" storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non -transitory" should not be interpreted as the memory 404 is non-movable. In some examples, the memory 404 may be configured to store larger amounts of information. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in RAM or cache). The memory 404 may be an internal storage unit or an external storage unit of the GMLC 234, cloud storage, or any other type of external storage. Aspects of the present disclosure are intended to include or otherwise cover any data storage medium as ‘the memory 404’, without deviating from the scope of the present disclosure.

[0082] The communication interface 406 may manage communications with the nodes 104 or the CPE 106. For example, the communication interface 406 may manage exchange of data and / or information between the GMLC 234 and the FMS 320 and / or between the GMLC 234 and the COM system 310 via the FMS 320. The communication interface 406 may include an electronic circuit specific to a standard that enables wired or wireless communication. The communication interface 406 is configured for communicating with external devices via one or more networks.

[0083] The scheduler 408 may be configured to periodically triggering the service module 330 to acquire one or more of the SUPI and / or the location information of the CPE 106, periodically at a pre-defined time interval or based on a pre-defined event, for managing the location information of the CPE 106. The scheduler 408 may further be configured to schedule execution of analytical tasks and job workflows allocated by the processor 402, and thus ensures timely processing and acquisition / update of the location information for the CPE 106, such as at an hourly basis, daily basis, or weekly basis. The scheduler 408 may also configured to cause a trigger to the update unit 332-2 to update the database 340 with the acquired SUPI and the location information of the CPE 106.1

[0084] Although FIG. 4 illustrates one example of GMLC 234, various changes may be made to FIG. 4. For example, the GMLC 234 may include any number of components in addition to the components shown in FIG. 4. Further, various components in FIG. 4 may be combined, further subdivided, or omitted, and additional components may be added according to particular needs.

[0085] FIG. 5 illustrates a line diagram depicting a process 500 depicting operations of managing the location information of the CPE 106 in the communication network 100, in accordance with an embodiment of the present disclosure. The process 500 comprises a series of operations presented by step 502 through step 512. Particularly, the steps 502 through 506 represent operation(s) performed by the system 300 corresponding to fetching (or acquiring) the location information of the CPE 106 when the location operation request corresponds to the location determination operation. Steps 508 through 512 represents operation(s) performed by the system 300 corresponding to update of the location information of the CPE 106 when the location operation request corresponds to the location update operation.

[0086] At step 502, the location request for the CPE 106 is initiated by the COM system 310 and sent to the FMS 320. The FMS 320 processes the location request for the CPE 106 and collects CPE information (or the CPE parameters) including, but not limited to, the SUPI of the CPE 106. Moreover, the FMS 320 sends the CPE parameter(s) along with the location request to the service module 330.

[0087] At step 504, the service module 330 fetches the database 340 using the CPE information received from the FMS 320. The location request enables the service module 330 to fetch the location information of the CPE 106 from a data entry corresponding to the CPE 106 stored in the database 340 based on the SUPI of the CPE 106.

[0088] At step 506, the service module 330 generates and transmits the response message (including the location information of the CPE 106) to the FMS 320.

[0089] At step 508, the update location request for the CPE 106 is initiated by the COM system 310 and sent to the FMS 320. The FMS 320 processes the update location request for the CPE 106 and collects CPE information (or the CPE parameters) including, but not limited to, the SUPI of the CPE 106 and the location information of the CPE 106. Moreover, the FMS 320 sends the CPE parameter(s) along with the update location request to the service module 330.

[0090] At step 510, the service module 330 updates the database 340 using the CPE information received from the FMS 320. The location request enables the service module 330 to update the data entry corresponding to the CPE 106 stored in the database 340 with the location information of the CPE 106 through the SUPI of the CPE 106.

[0091] At step 506, the service module 330 generates and transmits the response message (including information of update of the location information of the CPE 106) to the FMS 320.

[0092] FIG. 6 is a flow chart that presents a method 600 for managing the location information of the CPE in the communication network, in accordance with an embodiment of the present disclosure. The method 600 presents operation(s) performed by the service module 330 (i.e., the GMLC-PC microservice) of the GMLC node 234. The operations enable the service module 330 to manage the location information of the CPE 106 in the communication network 100 as are depicted hereinbelow by way of blocks 602 through 610.

[0093] At block 602, the service module 330 may receive the location operation request for the CPE 106. The location operation request corresponds to the data fetch operation (i.e., the location request) or the data update operation (i.e., the update location request) for the location information of the CPE 106. In some aspects of the present disclosure, the location operation request is transmitted through as an API request (e.g. a REST based API request) that enables the service module 330 to retrieve or update the location information of the CPE 106 in the database 340. Insome aspects of the present disclosure, the service module 330 is triggered periodically to process the location information of the CPE 106.

[0094] At block 604, the service module 330 may identify a type of operation associated with the location operation request. When the type of operation corresponds to determination (or fetching) of the location information of the CPE 106, the method 600 proceeds to block 606. Else when the type of operation corresponds to update of the location information of the CPE 106, the method 600 proceeds to block 608.

[0095] At block 606, the service module 330 may fetch the location information of the CPE 106 from the database 340. Specifically, the service module 330 may extract the SUPI of the CPE 106 from the location operation request and identify the data entry corresponding to location information of the CPE 106 stored in the database 340. The service module 330 may generate trigger for retrieval of the data entry to fetch the location information of the CPE 106. Thereafter, the method 600 proceeds to block 610.

[0096] At block 608, the service module 330 may update the location information of the CPE 106 in the database 340. Specifically, the service module 330 may extract the location information and the SUPI of the CPE 106 from the location operation request (i.e., the update location request). Thereafter, the service module 330 may retrieve the data entry corresponding to the CPE 106 from the database 340. Moreover, the service module 330 may replace the content(s) of the data entry corresponding to the CPE 106 with location information extracted from the location operation request. In some aspects of the present disclosure, the service module 330 may perform the abovementioned operations for the update of the data entry for the CPE 106 in the database 340 through the Application Programming Interface (API) trigger. Thereafter, the method 600 proceeds to block 610.

[0097] At block 610, the service module 330 may may generate and transmit the response message to the FMS 320. The response message may include the location information requested / updated by way of the location operation request. In someaspects of the present disclosure, the location information comprises latitude and longitude coordinates of the CPE 106.

[0098] Now, referring to the technical abilities and advantageous effect of the present disclosure, the embodiments disclosed herein provide seamless handling the location change requests of the CPEs 106 in the communication network 100 and interact with provisioning information APIs to ensure accurate and timely updates of the location information of the CPEs 106 in the communication network 100, thereby reducing operational expenditure on failed / faulty operations for the CPE 106 due to outdated location information of the CPE 106. Another noteworthy advantage of the one or more embodiments of the present disclosure includes but not limited thereto, facilitating greater flexibility and control over management of the CPEs 106 in the communication network 100.

[0099] Those skilled in the art will appreciate that the methodology described herein in the present disclosure may be carried out in other specific ways than those set forth herein in the above disclosed embodiments without departing from essential characteristics and features of the present invention. The above-described embodiments are therefore to be construed in all aspects as illustrative and not restrictive.

[0100] The drawings and the forgoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, orders of processes described herein may be changed and are not limited to the manner described herein. Any combination of the above features and functionalities may be used in accordance with one or more embodiments.

[0101] In the present disclosure, each of the embodiments has been described with reference to numerous specific details which may vary from embodiment to embodiment. The foregoing description of the specific embodiments disclosedherein may reveal the general nature of the embodiments herein that others may, by applying current knowledge, readily modify and / or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications are intended to be comprehended within the meaning of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and is not limited in scope.

Claims

WE CLAIM:

1. A method (600) for managing location information of a Customer Premise Equipment (CPE) (106) in a communication network (100), the method (600) comprising: receiving, by a transceiver unit (332-1) at a service module (330) in a Gateway Mobile Location Centre (GMLC) (234), from a Fulfilment Management System (FMS) (320), a location operation request for the CPE (106), wherein the location operation request corresponds to a data fetch operation or a data update operation for the location information of the CPE (106); fetching, by a fetching unit (332-4) at the service module (330), the location information of the CPE (106) from a database (340) in response to a determination that the location operation request corresponds to the data fetch operation; and transmitting, by the transceiver unit (332-1), the location information of the CPE (106) to the FMS (320).

2. The method (600) as claimed in claim 1, further comprising: updating, by an update unit of the service module (330), the location information of the CPE (106) in the database (340) in response to a determination that the location operation request corresponds to the data update operation; and transmitting, by the transceiver unit (332-1), the updated location information of the CPE (106) to the FMS (320).

3. The method (600) as claimed in claim 1, wherein the location information comprises latitude and longitude coordinates of the CPE (106).

4. The method (600) as claimed in claim 1, wherein the location operation request is transmitted through an Application Programming Interface (API) as an API request that enables the service module (330) to retrieve or update the location information in the database (340).

5. The method (600) as claimed in claim 4, wherein the service module (330) is triggered periodically to process the location information of the CPE (106).

6. The method (600) as claimed in claim 4, wherein the API request is a Representational State Transfer (REST) based API request.

7. The method (600) as claimed in claim 1, wherein the service module (330) corresponds to a Gateway Mobile Location Centre - Positioning Client (GMLC-PC) microservice.

8. A system (300) to manage location information of Customer Premise Equipment (CPE) (106) in a communication network (100), the system (300) comprising: a transceiver unit (332-1) at a service module (330) in a Gateway Mobile Location Centre (GMLC) (234), configured to receive a location operation request for the CPE (106) from a Fulfilment Management System (FMS) (320), wherein the location operation request corresponds to a data fetch operation or a data update operation for the location information of the CPE (106); and a fetching unit (332-4) at the service module (330), configured to fetch the location information of the CPE (106) from a database (340) in response to a determination that the location operation request corresponds to the fetch operation, wherein the transceiver unit (332-1) transmits the location information of the CPE (106) to the FMS (320).

9. The system (300) as claimed in claim 8, further comprises an update unit at the service module (330), configured to update the location information of the CPE (106) in the database (340) in response to a determination that the location operation request corresponds to the data update operation, wherein the transceiver unit (332- 1) transmits the updated location information of the CPE (106) to the FMS (320).

10. The system (300) as claimed in claim 8, wherein the location information comprises latitude and longitude coordinates of the CPE (106).

11. The system (300) as claimed in claim 8, wherein the location operation request is transmitted through an Application Programming Interface (API) as an API request that enables the service module (330) to retrieve or update the location information in the database (340).

12. The system (300) as claimed in claim 11, wherein the service module (330) is triggered periodically to process the location information of the CPE (106).

13. The system (300) as claimed in claim 11, wherein the API request is a Representational State Transfer (REST) based API request.

14. The system (300) as claimed in claim 8, wherein the service module (330) corresponds to a Gateway Mobile Location Centre - Positioning Client (GMLC-PC) microservice.

15. A computer-program product comprising computer-executable instructions for managing location information of an Outdoor Customer Premise Equipment (ODCPE (106)) in a communication network (100), that are stored on a non- transitory computer-readable medium and that, when executed by at least one processor performs operations comprising: receiving, from a Fulfilment Management System (FMS) (320), a location operation request for the CPE (106), wherein the location operation request corresponds to a data fetch operation or a data update operation for the location information of the CPE (106); fetching the location information of the CPE (106) from a database (340), in response to a determination that the location operation request corresponds to the data fetch operation; and transmitting the location information of the CPE (106) to the FMS (320).

Images