System and method for managing customer premise equipment monitoring in a communication network

Abstract

Disclosed is a system (300) and a method (700) for managing Customer 5 Premise Equipment (CPE) monitoring in a communication network (100). The system (300) includes a service module (330) i.e., a dedicated microservice for managing the CPE monitoring. The service module (330) receives a monitoring alteration request to alter a monitoring state of the CPE (106) from a Fulfilment Management System (FMS) (320) and identifies a type of alteration for the 10 monitoring state of the CPE (106) based on the monitoring alteration request. The type of alteration corresponds to an activation of the CPE monitoring, a deactivation of the CPE monitoring, or a suspension of the CPE monitoring. Thereafter, the service module (330) updates a database (340) based on the type of alteration for the monitoring state of the CPE (106).

Description

SYSTEM AND METHOD FOR MANAGING CUSTOMER PREMISEEQUIPMENT MONITORING IN A 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 telecommunications networks, managing a status of network elements is critical for efficient operations. Specifically, there is a need to efficiently handle deactivation, re-activation, or suspension of network elements (such as Customer Premise Equipment) in response to customer requests. Conventional systems are not efficient in managing handling of the deactivation and the reactivation of the network elements operations smoothly, leading to potential delays, errors, and inefficiencies in network management.

[0005] In light of the aforementioned challenges, there is a need for a solution that can address the issue related to handling of the deactivation and re-activation of the network elements effectively and efficiently and ensure optimal resource management and reliable network operations.SUMMARY

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

[0007] According to an embodiment of the present disclosure, a method for managing Customer Premise Equipment (CPE) monitoring in a communication network is disclosed. The method includes receiving from a Fulfilment Management System (FMS) by a transceiver unit at a service module, a monitoring alteration request to alter a monitoring state of the CPE in the communication network. The method further includes identifying, by an identification unit at the service module, a type of alteration for the monitoring state of the CPE based on the monitoring alteration request. The type of alteration corresponds to an activation of the CPE monitoring, a deactivation of the CPE monitoring, or a suspension of the CPE monitoring. Furthermore, the method includes updating, by an update unit at the service module, a database based on the type of alteration for the monitoring state of the CPE.

[0008] In some aspects of the present disclosure, the method further includes determining, by a determination unit at the service module, whether the update of database failed or succeeded. Moreover, the method includes generating, by a generation unit at the service module, an update response for the FMS based on the determination that the update of the database succeeded.

[0009] In some aspects of the present disclosure, the method further includes generating, by the generation unit, an error response for the FMS based on the determination that the update of the database failed.

[0010] In some aspects of the present disclosure, for determining whether the update of database failed or succeeded, the method includes determining, by the determination unit, a requested monitoring state of the CPE from the monitoring alteration request. Moreover, the method includes determining, by the determination unit, a present monitoring state of the CPE from the database. Furthermore, the method includes determining, by the determination unit, whether the present monitoring state of the CPE matches or mismatches with the requested monitoring state of the CPE.

[0011] In some aspects of the present disclosure, the match between the present monitoring state of the CPE and the requested monitoring state of the CPE is associated with the failed update of the database. The mismatch between the present monitoring state of the CPE and the requested monitoring state of the CPE is associated with the succeeded update of the database.

[0012] In some aspects of the present disclosure, the method further includes transmitting, by the transceiver unit, the update response or the error response to a Customer Order Management (COM) system via the FMS.

[0013] In some aspects of the present disclosure, the monitoring alteration request further comprises a Subscriber Permanent Identifier (SUPI) associated with the CPE.

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

[0015] In some aspects of the present disclosure, the database is updated through an Application Programming Interface (API) trigger.

[0016] According to another embodiment of the present disclosure, a system to manage Customer Premise Equipment (CPE) monitoring in a communication network is provided. The system includes a transceiver unit, an identification unit, and an update unit, each at a service module. The transceiver unit is configured to receive a monitoring alteration request to alter a monitoring state for the CPE in the communication network from a Fulfilment Management System (FMS). The identification unit is configured to identify a type of alteration for the monitoring state of the CPE based on the monitoring alteration request. The type of alteration corresponds to an activation of the CPE monitoring, a deactivation of the CPE monitoring, or a suspension of the CPE monitoring. The update unit is configured to update a database based on the type of alteration for the monitoring state of the CPE.BRIEF DESCRIPTION OF DRAWINGS

[0017] 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 Customer Premise Equipment (CPE) monitoring 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 of de-activating the CPE monitoring in the comm, in accordance with an embodiment of the present disclosure.FIG. 6 illustrates a line diagram depicting a process of activating the CPE monitoring, in accordance with an embodiment of the present disclosure.FIG. 7 is a flow chart that presents a method for managing the CPE monitoring in the communication network, in accordance with an embodiment of the present disclosure.LIST OF REFERENCE NUMERALS

[0018] 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 - Identification Unit332-5 - Generation Unit340 - Database402 - Processor(s)404 - Memory404-1 - Instructions Repository406 - Communication interface408 - Scheduler412 - Communication bus500 - Process for deactivation of CPE502-510 - Operational steps of the process 500600 - Process for activation of CPE602-610 - Operational steps of the process 600700 - Method for managing the CPE monitoring in the communication network 702-714 - Operational blocks of the method 700DETAILED DESCRIPTION OF THE INVENTION

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

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

[0021] The following description contains specific information pertaining to embodiments in the present disclosure. The detailed description uses the phrases “insome 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 one implementation 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.

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

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

[0024] 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, itmay be understood by one of the ordinary skilled in the art that the embodiments disclosed herein may be practiced without these specific details.

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

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

[0027] An object of the present disclosure is to provide a system and a method for managing a monitoring process of Customer Premise Equipment (CPE) status within a Network Management System. Another object of the present disclosure is to provide a system and a method that can enable resource optimization and effective network management utilizing a microservice i.e., a Gateway Mobile Location Centre Positioning Client (GMLC-PC) to quickly stop, start, or suspend the monitoring process. Yet another object of the present disclosure is to provide a system and a method that can ensure continuous and uninterrupted network surveillance by allowing the GMLC-PC to re-initiate the monitoring process when a re-activation request is received at the GMLC-PC through a Fulfilment Management System (FMS). To facilitate an understanding of the disclosed invention, some terms are defined below.

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

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

[0030] Embodiments of the present disclosure will be described below in detail with reference to the accompanying drawings. FIG. 1 through FIG. 7, 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 to limit 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.

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

[0032] 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 similarcharacteristics 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.

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

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

[0035] 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 connectedwith 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.

[0036] 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 nodes 104. 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.

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

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

[0039] Although FIG. 1 illustrates one example of the communication network 100, various changes may be made to FIG. 1. For example, the communication network100 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.

[0040] 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 the CPE or the ODCPE to a Radio Access Network (RAN) 236 including the plurality of nodes 104.

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

[0042] 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 (alternativelyreferred 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 Plane Function (UPF) node 238 (alternatively referred to as UPF 238), and a Location Services (LCS) client node 240 (alternatively referred to as LCS 240).

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

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

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

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

[0047] The UDM 210 may be a network element capable of maintaining subscription information for user devices 108, manage subscriptions, generate authentication 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.

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

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

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

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

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

[0053] 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 beconfigured 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.

[0054] 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, monitoring state altering, and asset tracking etc. 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.

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

[0056] 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, performdownlink packet buffering, forward an “end marker” to the RAN 236 (e.g., gNB), and / or perform other types of user plane processes.

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

[0058] FIG. 3 illustrates a block diagram depicting an architecture of a system 300 for managing Customer Premise Equipment (CPE) monitoring 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.

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

[0060] 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 CPE monitoring in the communication network 100. Specifically, the microservice in the service module 330 may manage re-activation (or activation), deactivation, and / or suspension of the CPE monitoring. 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 microservicemay 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 CPE monitoring).

[0061] 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 monitoring of an equipment (for example, the CPE 106) in the communication network 100. Specifically, the orders or requests may correspond to re-activation (or activation), deactivation, or suspension of the monitoring of the CPE 106. Typically, such a controlled monitoring enables efficient resource utilization by disabling monitoring of inactive CPE(s) in the communication network 100 and initiating monitoring of new / active CPE(s) in the communication network 100. The COM system 310 forwards the monitoring alteration request for the CPE 106 to the FMS 320. The FMS 320 acquires CPE information corresponding which the request is received by the FMS 320 including, but not limited to, information of the monitoring state requested of the CPE 106 (e.g., a type of alteration for the monitoring state of the CPE 106) and a Subscriber Permanent Identifier (SUPI) of the CPE 106. Preferably, the service module 330, via the GMLC-PC units 332, may process the SUPI and / or the type of alteration requested for the monitoring state of the CPE 106 for managing the CPE monitoring in the communication network 100.

[0062] The FMS 320 is configured to process the monitoring alteration request received from the COM system 310 and acquire CPE information including, but not limited to, the Subscriber Permanent Identifier (SUPI) and the type of alteration for the monitoring state of the CPE 106. The FMS 320 is further configured to send the monitoring alteration request along with the CPE information to the service module330 (specifically to the GMLC-PC units 332) for managing the CPE monitoring in the communication network 100. Typically, the type of alteration corresponds to an activation of the CPE monitoring, a deactivation of the CPE monitoring, or a suspension of the CPE monitoring.

[0063] 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 processing the monitoring request using the CPE information. The GMLC-PC units 332 may be configured to support the FMS 320 for managing the CPE monitoring in the communication network 100 and sending a response message to the FMS 320 indicating a success or a failure of alteration of the CPE monitoring in the communication network 100, as requested through the monitoring alteration request.

[0064] For example, an activation of CPE monitoring (i.e., change in the state of monitoring state from inactive to active for the CPE 106) in response to an activation request for the CPE is a success of alteration of the CPE monitoring. A deactivation of the CPE monitoring (i.e., change in the state of monitoring state from active to inactive for the CPE 106) in response to an activation request for the CPE is a failure of alteration of the CPE monitoring. In some aspects of the present disclosure, when an operational state (i.e., a present state) of the CPE 106 is same as a requested state of the CPE 106 (i.e., derived through the monitoring alteration request), such an instance corresponds to a failure of the alteration of the CPE monitoring. Similarly, when the operational state (i.e., a present state) of the CPE 106 and the requested state of the CPE 106 (i.e., derived through the monitoring alteration request) are different, such an instance corresponds to a success of the alteration of the CPE monitoring, when updated in the database 340.

[0065] 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 databasemanagement system, hierarchical database management system, network database management system, an in-memory database including a distributed in-memory data storage, or a distributed database..

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

[0067] 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 developed technologies, 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.

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

[0069] In some aspects of the present disclosure, the processor(s) 402 may include one or a plurality of 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.

[0070] 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 more processors), 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).

[0071] 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 butaccessible to the GMLC node 234 and the processing resource. In other examples, the service module 330 may be implemented using an electronic circuitry.

[0072] 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, an identification unit 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.

[0073] 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 a monitoring alteration request from the FMS 320 to alter the monitoring state for the CPE 106 in the communication network 100. In some aspects of the present disclosure, the monitoring state for the CPE 106 may be related to active monitoring state, inactive monitoring state, or suspended monitoring state for the CPE 106.

[0074] The identification unit 332-4 may be configured to identify a type of alteration for the monitoring state of the CPE 106 based on the monitoring alteration request. The type of alteration corresponds to the activation of the CPE monitoring, the deactivation of the CPE monitoring, or the suspension of the CPE monitoring.

[0075] The update unit 332-2 may be configured to update the database 340 based on the type of alteration for the monitoring state of the CPE 106. Preferably, the update unit 332-2 may be configured to retrieve a data entry corresponding to the CPE 106 from the database 340. In some aspects of the present disclosure, the data entry may be labelled (or tagged) with an identifier corresponding to the SUPI of the CPE 106. The update unit 332-2 may extract the SUPI of the CPE 106 from the monitoring alteration request and utilize the SUPI of the CPE 106 to identify and / or retrieve the data entry corresponding to the CPE 106 from the database 340. Moreover, the update unit 332-2 may be configured to replace content(s) of the dataentry corresponding to the CPE 106 with data related to the requested monitoring state of the CPE 106 in the monitoring alteration request. In some aspects of the present disclosure, the update unit 332-2 may be configured to perform the abovementioned operations for the update of the data entry for the CPE 106 in the database 340 through an Application Programming Interface (API) trigger.

[0076] The determination unit 332-3 may be configured to determine whether the update of database 340 failed or succeeded, in response to the monitoring alteration request. In some aspects of the present disclosure, for determining whether the update of database 340 failed or succeeded, the determination unit 332-3 may be configured to determine a requested monitoring state of the CPE 106 from the monitoring alteration request. For example, when the monitoring alteration request corresponds to the activation (or re-activation) of monitoring state for the CPE 106, the requested monitoring state corresponds to the active monitoring state (e.g., ‘ 1’) for the CPE 106. In other example, when the monitoring alteration request corresponds to the deactivation of the monitoring state for the CPE 106, the requested monitoring state corresponds to the inactive monitoring state (e.g., ‘0’) for the CPE 106. The determination unit 332-3 may further be configured to determine (or retrieve) a present monitoring state of the CPE 106 from the database 340 and compare the present monitoring state with the requested monitoring state, for the CPE 106. When the determination unit 332-3 determines that the present monitoring state mismatches with the requested monitoring state and the requested monitoring state for the CPE 106 replaces the present monitoring state for the CPE 106 in the database 340, the determination unit 332-3 identifies (or determines) successful update of the database 340. Else, when the determination unit 332-3 determines that the present monitoring state matches with the requested monitoring state, the determination unit 332-3 identifies (or determines) failed update of the database 340 (e.g., activation of an already actively monitored CPE 106 is failure of the database 340 update). In other words, the match between the present monitoring state of the CPE 106 and the requested monitoring state of the CPE 106 is associated with the failed update of the database 340. Similarly, the mismatch between thepresent monitoring state of the CPE 106 and the requested monitoring state of the CPE 106 is associated with the succeeded update of the database 340.

[0077] In various aspects of the present disclosure, when the determination unit 332-3 determines that the present monitoring state of the CPE 106 is changed in accordance with that requested in the monitoring alteration state, the determination unit 332-3 determines that the database 340 updated succeeded. Else, when the determination unit 332-3 determines that the present monitoring state of the CPE 106 remains unchanged in accordance with that requested in the monitoring alteration state, the determination unit 332-3 determines that the database 340 update failed.

[0078] The generation unit 332-5 may be configured to generate an error response for the FMS 320 based on the determination that the update of the database 340 failed. Moreover, the generation unit 332-5 may be configured to update response for the FMS 320 based on the determination that the update of the database 340 succeeded.

[0079] Based on the failure or success of the database 340 update in response to the monitoring alteration request, the transceiver unit 332-1 may be configured to the transmit a response message (cumulatively referring to the update response for successful update of the database 340 or the error response for failed update of the database 340) to the COM system 310 via the FMS 320.

[0080] Various units of the GMLC-PC units 332 are presented to illustrate the functionality driven by the service module 330 for managing the monitoring state of the CPE 106 (i.e., CPE monitoring). 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.

[0081] In some aspects of the present disclosure, the service module 330 may host multiple microservices. Among the micro services, a microservice maycorrespond 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.

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

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

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

[0085] 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 instructions1 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 monitoring state of the CPE 106 in the communication network. 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.

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

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

[0088] The scheduler 408 may be configured to periodically triggering the service module 330 to acquire one or more of the SUPI and / or the information of the CPE 106, periodically at a pre-defined time interval or based on a pre-defined event, for monitoring 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 of the CPE information, 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 information of the CPE 106.

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

[0090] FIG. 5 illustrates a line diagram depicting a process 500 of deactivating the monitoring of the CPE 106, in accordance with an embodiment of the present disclosure. The process 500 comprises a series of operations presented by step 502 through step 510.

[0091] At step 502, a deactivation request for the CPE 106 is initiated by the COM system 310 and sent to the FMS 320.

[0092] At step 504, the FMS 320 processes the deactivation request for the CPE 106 and collects CPE parameter(s) including, but not limited to, the SUPI of the CPE 106. The deactivation request corresponds to changing the monitoring state of the CPE 106 in the data entry corresponding to the CPE 106 stored in the database 340 from active monitoring state to inactive monitoring state. Further, the FMS 320 sends the CPE parameter(s) along with the deactivation request to the service module 330.

[0093] At step 506, the service module 330 updates the database 340 with the CPE information received from the FMS 320. The update helps in minimizing transactions between the network components of the core network 102.

[0094] At step 508, the service module 330 determines the status of update of the CPE monitoring in the database 340 to deactivate the monitoring of the CPE 106. Based on the status, the service module 330 generates and transmits the response message (including the update response or the error response) to the FMS 320 indicating success / failure of the deactivation of the monitoring of the CPE 106.

[0095] At step 510, the FMS 320 transmits the response message to the COM system 310.

[0096] FIG. 6 illustrates a line diagram depicting a process 500 of activating the monitoring of the CPE 106, in accordance with an embodiment of the present disclosure. The process 600 comprises a series of operations presented by step 602 through step 610.

[0097] At step 602, an activation request for the CPE 106 is initiated by the COM system 310 and sent to the FMS 320.

[0098] At step 604, the FMS 320 processes the activation request for the CPE 106 and collects CPE parameter(s) including, but not limited to, the SUPI of the CPE 106. The activation request corresponds to changing the monitoring state of the CPE 106 in the data entry corresponding to the CPE 106 stored in the database 340 frominactive monitoring state to active monitoring state. Further, the FMS 320 sends the CPE parameter(s) along with the activation request to the service module 330.

[0099] At step 606, the service module 330 updates the database 340 with the CPE information received from the FMS 320. The update helps in minimizing transactions between the network components of the core network 102.

[0100] At step 608, the service module 330 determines the status of update of the CPE monitoring in the database 340 to activate the monitoring of the CPE 106. Based on the status, the service module 330 generates and transmits the response message (including the update response or the error response) to the FMS 320 indicating success / failure of the activation (or re-activation) of the monitoring of the CPE 106.

[0101] At step 610, the FMS 320 transmits the response message to the COM system 310.

[0102] FIG. 7 is a flow chart that presents a method 700 for managing the monitoring state of the CPE 106 (i.e., CPE monitoring) in the communication network 100, in accordance with an embodiment of the present disclosure. The method 700 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 CPE monitoring and are depicted hereinbelow by way of blocks 702 through 714.

[0103] At block 702, the service module 330 may receive the monitoring alteration request from the FMS 320 to alter the monitoring state for the CPE 106 in the communication network 100. In some aspects of the present disclosure, the monitoring state for the CPE 106 may be related to the active monitoring state, the inactive monitoring state, or the suspended monitoring state for the CPE 106.

[0104] At block 704, the service module 330 may identify the type of alteration for the monitoring state of the CPE 106 based on the monitoring alteration request. Thetype of alteration corresponds to the activation of the CPE monitoring, the deactivation of the CPE monitoring, or the suspension of the CPE monitoring.

[0105] At block 706, the service module 330 may update the database 340 based on the type of alteration for the monitoring state of the CPE 106. Preferably, the service module 330 may retrieve the data entry corresponding to the CPE 106 from the database 340. In some aspects of the present disclosure, the data entry may be labelled (or tagged) with the identifier corresponding to the SUPI of the CPE 106. The service module 330 may extract the SUPI of the CPE 106 from the monitoring alteration request and utilize the SUPI of the CPE 106 to identify and / or 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 data related to the requested monitoring state of the CPE 106 in the monitoring alteration 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.

[0106] At block 708, the service module 330 may determine whether the update of database 340 failed or succeeded, in response to the monitoring alteration request. In some aspects of the present disclosure, for determining whether the update of database 340 failed or succeeded, the service module 330 may determine the requested monitoring state of the CPE 106 from the monitoring alteration request. For example, when the monitoring alteration request corresponds to the activation of monitoring for the CPE 106, the requested monitoring state corresponds to the active monitoring state (e.g., ‘ 1’) for the CPE 106. In other example, when the monitoring alteration request corresponds to the deactivation of monitoring for the CPE 106, the requested monitoring state corresponds to the inactive monitoring state (e.g., ‘0’) for the CPE 106. The service module 330 may further determine (or retrieve) the present monitoring state of the CPE 106 from the database 340 and compare the present monitoring state with the requested monitoring state, for the CPE 106. When the service module 330 determines that the present monitoring statemismatches with the requested monitoring state and the requested monitoring state for the CPE 106 replaces the present monitoring state for the CPE 106 in the database 340, the service module 330 identifies (or determines) successful update of the database 340. Else, when the service module 330 determines that the present monitoring state matches with the requested monitoring state, the service module 330 identifies (or determines) failed update of the database 340 (e.g., activation of an already actively monitored CPE 106 is failure of the database 340 update). In other words, the match between the present monitoring state of the CPE 106 and the requested monitoring state of the CPE 106 is associated with the failed update of the database 340. Similarly, the mismatch between the present monitoring state of the CPE 106 and the requested monitoring state of the CPE 106 is associated with the succeeded update of the database 340.

[0107] When the service module 330 determines successful update of the database 340 in response to the monitoring alteration request, the method 700 proceeds to block 710. Else, when the service module 330 determines failed update of the database 340 in response to the monitoring alteration request, the method 700 proceeds to block 712.

[0108] At block 710, the service module 330 may generate the update response (comprising an acknowledgement notification corresponding to change of the monitoring state of the CPE 106) for the FMS 320. Particularly, the update response indicates the success of update of the alteration of the monitoring state for the CPE 106 in the database 340 in response to the monitoring alteration request. Thereafter, the method 700 proceeds to block 714.

[0109] At block 712, the service module 330 may generate the error response (comprising an error notification corresponding to change of the monitoring state of the CPE 106) for the FMS 320. Particularly, the error notification indicates the failure of update of the monitoring state of the CPE 106, in response to the monitoring alteration request. Thereafter, the method 700 proceeds to block 714.

[0110] At block 714, the service module 330 may generate the response message using the update response and / or update notification or the error response and / or the error notification) (whichever applicable, based on the status of the update of the database 340). Moreover, the service module 330 may transmit the response message comprising the status of the update of the monitoring state for the CPE 106 in the database 340 to the FMS 320. In some aspects of the present disclosure, the service module 330 transmits the response message to the COM system 310 via the FMS 320. The update notification may enable the FMS 320 to enable / disable / suspend the monitoring for the CPE 106 based on the requested (or updated) monitoring state of the CPE 106 using a set of predefined CPE monitoring protocols. Examples of the CPE monitoring protocols in the set of predefined CPE monitoring protocols may include 3GPP standards CPE monitoring protocols, such as but not limited to, Technical Report (TR)-069 CPE monitoring protocol, TR-369 CPE monitoring protocol, and TR-181 CPE monitoring protocol. Aspects of the present disclosure are intended to include or otherwise cover any existing or later developed CPE monitoring protocol in the 3 GPP telecommunication standard as one of the set of predefined CPE monitoring protocol, without deviating from the scope of the present disclosure. The error notification may enable the FMS 320 to render an error notification for the CPE 106.

[0111] Now, referring to the technical abilities and advantageous effect of the present disclosure, the embodiments disclosed herein provides a streamlined monitoring of CPE management in the communication network 100 that enables optimum resource optimization and effective network management by allowing the service module 330 (i.e., the GMLC-PC microservice) to quickly stop or suspend the monitoring process for the CPEs 106 in the communication network 100, ensuring efficient utilization of valuable network resources and enhanced throughput by optimizing functioning of the communication network 100. Further, the embodiments disclosed herein provides a streamlined re-activation call-flow that enables the GMLC-PC microservice to seamlessly re-initiate the monitoring processand ensure continuous and uninterrupted network surveillance (through monitoring of desired CPE 106 in the communication network 100).

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

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

[0114] 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 disclosed herein 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 (700) for managing Customer Premise Equipment (CPE) (106) monitoring in a communication network (100), the method (700) comprising: receiving, from a Fulfilment Management System (FMS) (320) by a transceiver unit (332-1) at a service module (330) in a Gateway Mobile Location Centre (GMLC) (234), a monitoring alteration request to alter a monitoring state of the CPE (106) in the communication network (100); identifying, by an identification unit (332-4) at the service module (330), a type of alteration for the monitoring state of the CPE (106) based on the monitoring alteration request, wherein the type of alteration corresponds to an activation of the CPE monitoring, a deactivation of the CPE monitoring, or a suspension of the CPE monitoring; and updating, by an update unit (332-2) at the service module (330), a database (340) based on the type of alteration for the monitoring state of the CPE (106).

2. The method (700) as claimed in claim 1, further comprising: determining, by a determination unit (332-3) at the service module (330), whether the update of database (340) failed or succeeded; generating, by a generation unit (332-5) at the service module (330), an update response for the FMS (320) based on the determination that the update of the database (340) succeeded.

3. The method (700) as claimed in claim 2, further comprises generating, by the generation unit (332-5), an error response for the FMS (320) based on the determination that the update of the database (340) failed.

4. The method (700) as claimed in claim 2, wherein for determining whether the update of database (340) failed or succeeded, the method (700) comprises: determining, by the determination unit (332-3), a requested monitoring state of the CPE (106) from the monitoring alteration request;determining, by the determination unit (332-3), a present monitoring state of the CPE (106) from the database (340); and determining, by the determination unit (332-3), whether the present monitoring state of the CPE (106) matches or mismatches with the requested monitoring state of the CPE (106).

5. The method (700) as claimed in claim 4, wherein: the match between the present monitoring state of the CPE (106) and the requested monitoring state of the CPE (106) is associated with the failed update of the database (340); and the mismatch between the present monitoring state of the CPE (106) and the requested monitoring state of the CPE (106) is associated with the succeeded update of the database (340).

6. The method (700) as claimed in claim 3, further comprises transmitting, by the transceiver unit (332-1), the update response or the error response to a Customer Order Management (COM) system (310) via the FMS (320).

7. The method (700) as claimed in claim 1, wherein the monitoring alteration request further comprises a Subscriber Permanent Identifier (SUPI) associated with the CPE (106).

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

9. The method (700) as claimed in claim 1, wherein the database (340) is updated through an Application Programming Interface (API) trigger.

10. A system (300) to manage Customer Premise Equipment (CPE) (106) monitoring 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 monitoring alteration request to alter a monitoring state for the CPE (106) in the communication network (100) from a Fulfilment Management System (FMS) (320); an identification unit (332-4) at the service module (330), configured to identify a type of alteration for the monitoring state of the CPE (106) based on the monitoring alteration request, wherein the type of alteration corresponds to an activation of the CPE monitoring, a deactivation of the CPE monitoring, or a suspension of the CPE monitoring; and an update unit (332-2) at the service module (330), configured to update a database (340) based on the type of alteration for the monitoring state of the CPE (106).

11. The system (300) as claimed in claim 10, further comprising: a determination unit (332-3) at the service module (330), configured to determine whether the update of database (340) failed or succeeded; and a generation unit (332-5) at the service module (330), configured to generate an update response for the FMS (320) based on the determination that the update of the database (340) succeeded.

12. The system (300) as claimed in claim 11, wherein the generation unit (332- 5) is further configured to generate an error response for the FMS (320) based on the determination that the update of the database (340) failed.

13. The system (300) as claimed in claim 11, wherein to determine whether the update of database (340) failed or succeeded, the determination unit (332-3) is configured to: determine a requested monitoring state of the CPE (106) from the monitoring alteration request; determine a present monitoring state of the CPE (106) from the database (340); anddetermine whether the present monitoring state of the CPE (106) matches or mismatches with the requested monitoring state of the CPE (106).

14. The system (300) as claimed in claim 13, wherein: the match between the present monitoring state of the CPE (106) and the requested monitoring state of the CPE (106) is associated with the failed update of the database (340); and the mismatch between the present monitoring state of the CPE (106) and the requested monitoring state of the CPE (106) is associated with the successful update of the database (340).

15. The system (300) as claimed in claim 12, wherein the transceiver unit (332- 1) is further configured to transmit the update response or the error response to a Customer Order Management (COM) system (310) via the FMS (320).

16. The system (300) as claimed in claim 10, wherein the monitoring alteration request further comprises a Subscriber Permanent Identifier (SUPI) associated with the CPE (106).

17. The system (300) as claimed in claim 10, wherein the service module (330) is a Gateway Mobile Location Centre - Positioning Client (GMLC-PC) microservice.

18. The system (300) as claimed in claim 10, wherein the database (340) is updated through an Application Programming Interface (API) trigger.

19. A computer-program product for managing Customer Premise Equipment (CPE) (106) monitoring in a communication network (100), the computer program product comprising computer-executable instructions 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 monitoring alteration request to alter a monitoring state of a CPE (106) in the communication network (100); identifying a type of alteration for the monitoring state of the CPE (106) based on the monitoring alteration request, wherein the type of alteration corresponds to an activation of the CPE monitoring, a deactivation of the CPE monitoring, or a suspension of the CPE monitoring; and updating a database (340) based on the type of alteration for the monitoring state of the CPE (106).

Images