System and method for location-based deactivation of a customer premise equipment provisioned in communication network

Abstract

Disclosed is a system (300) and a method (500) for location-based deactivation of a Customer Premise Equipment (CPE) provisioned in a communication network (100). The method comprises receiving a request from a Fulfilment Management System (320) for monitoring the CPE in the communication network (100). Upon receiving the request, a service module (330, 410-5) in a Gateway Mobile Location Centre (GMLC) node (234) acquires from a Location Management Function (LMF), information corresponding to the CPE, the information comprises a current positional information of the CPE. A mismatch between the current positional information of the CPE and positional information of the CPE stored in a database is determined. Based on the mismatch, a change in a location of the CPE is determined, a deactivation request is sent to the FMS (320) to deactivate the CPE, and acquisition of the information corresponding to the CPE from the LMF (218) is terminated.

Description

SYSTEM AND METHOD FOR LOCATION-BASED DEACTIVATION OF A CUSTOMER PREMISE EQUIPMENT PROVISIONED IN COMMUNICATION NETWORKTECHNICAL FIELD

[0001] The embodiments of the present disclosure generally relate to the field of communication networks and systems. More particularly, the present disclosure relates to a system and a method for location-based deactivation of a Customer Premise Equipment (CPE) provisioned 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 recent advancement in Fifth Generation (5G) communication networks, several wireless technologies are being developed to meet demands of an increasing number of users of the communication network. Along with keeping up with the growing data demands of the users, telecom operators are also striving to improve user experience and provide better applications and services.

[0004] To this end, to facilitate faster network traffic within the communication network, network devices such as Customer Premise Equipment(s) (CPEs) are often installed by the users in their premises such as homes and offices. The CPEs enable efficient and widespread internet access and other services of the communication network for the users in or around the premises.

[0005] However, the CPEs are prone to theft as the CPEs are often installed at an exterior of the premises. Such instances can lead to significant costs and disruptionsfor the users, and also poses an increased risk of misuse of the information stored and processed by the CPEs. Traditional methods for identifying the theft of the CPEs and reporting the same to the telecom operators involved numerous transactions between the users and the telecom operators, that often lead to delays.

[0006] In light of the aforementioned challenges, there is a need for a solution that can detect a change in location of the CPE in real-time accurately to prevent misuse of a stolen CPE.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] In an embodiment, disclosed herein is a method for location-based deactivation of a Customer Premise Equipment (CPE) in a communication network. The method comprises receiving, by a reception module in a Gateway Mobile Location Centre (GMLC) node, a request from a Fulfilment Management System (FMS) for monitoring the CPE for the location-based deactivation. Further, the method comprises acquiring, by an acquisition module from a Location Management Function (LMF) via a service module in the GMLC node, information corresponding to the CPE upon receiving the request for monitoring the CPE, the information comprises a current positional information of the CPE. Further, the method comprises determining, by a determination module in the GMLC node, a change in a location of the CPE based on a mismatch between the current positional information of the CPE and positional information of the CPE stored in a database. Furthermore, the method comprises transmitting, by a transmitting module in the GMLC node, based on the determined change in the location of the CPE, a deactivation request to one of an order care system or the FMS to deactivate theCPE from the communication network. Thereafter, the method comprises terminating, by the transmitting module, the acquisition of the information corresponding to the CPE from the LMF for monitoring the CPE, based on a response including a deactivated status of the CPE received from one of the order care system or the FMS.

[0009] In one or more embodiments, the method further comprises sending, by the transmitting module to one of the order care system or the FMS, the deactivation request to deactivate the CPE at a Unified Data Management (UDM) node of the communication network. Thereafter, the method comprises receiving, by the reception module from one of the order care system or the FMS, the response including the deactivated status of the CPE at the UDM node corresponding to the deactivation request sent to one of the order care system or the FMS.

[0010] In one or more embodiments, for determining the change in the location of the CPE, the method comprises determining, by the determination module, the mismatch between the current positional information of the CPE and the positional information of the CPE by comparing the current positional information of the CPE and the positional information of the CPE.

[0011] In one or more embodiments, the method further comprises initiating, by the acquisition module, an Application Programming Interface (API) request to the service module for sending the deactivation request to one of the order care system or the FMS. Thereafter, the method comprises sending, by the service module, the deactivation request to one of the order care system or the FMS via the transmitting module. The service module is a Gateway Mobile Location Centre Positioning Client (GMLC-PC).

[0012] In one or more embodiments, the method further comprises triggering, by the acquisition module via a scheduler, the service module at a periodic time interval to acquire the information corresponding to the CPE from the LMF for monitoring the CPE.

[0013] In one or more embodiments, the information further comprises subscription data corresponding to the CPE including a Subscriber Permanent Identifier (SUPI) of the CPE, and the positional information comprises longitude and latitude coordinates of a geographical location corresponding to the CPE.

[0014] In another embodiment, disclosed herein is a system for location-based deactivation of a Customer Premise Equipment (CPE) in a communication network. The system comprises a Fulfilment Management System (FMS) and a Gateway Mobile Location Centre (GMLC) node. The GMLC node comprises a reception module, an acquisition module, a determination module, and a transmitting module. The reception module is configured to receive a request from the FMS for monitoring the CPE for the location-based deactivation. The acquisition module is configured to acquire, from a Location Management Function (LMF) via a service module in the GMLC node, information corresponding to the CPE upon receiving the request for monitoring the CPE, the information comprises a current positional information of the CPE. The determination module is configured to determine a change in a location of the CPE based on a mismatch between the current positional information of the CPE and a positional information of the CPE stored in a database. The transmitting module is configured to transmit, based on the determined change in the location of the CPE, a deactivation request to one of an order care system or the FMS to deactivate the CPE from the communication network. Thereafter, the transmitting module is configured to terminate the acquisition of the information corresponding to the CPE from the LMF for monitoring the CPE, based on a response including a deactivated status of the CPE received from one of the order care system or the FMS.

[0015] In one or more embodiments, the transmitting module is further configured to send, to one of the order care system or the FMS, the deactivation request to deactivate the CPE at a Unified Data Management (UDM) node of the communication network. The reception module is configured to receive from one of the order care system or the FMS, the response including the deactivated statusof the CPE at the UDM node corresponding to the deactivation request sent to one of the order care system or the FMS.

[0016] In one or more embodiments, for determining the change in the location of the CPE, the determination module is further configured to determine the mismatch between the current positional information of the CPE and the positional information of the CPE by comparing the current positional information of the CPE and the positional information of the CPE.

[0017] In one or more embodiments, the acquisition module is further configured to initiate an Application Programming Interface (API) request to the service module for sending the deactivation request to one of the order care system or the FMS. Thereafter, the acquisition module is configured to send, by the service module, the deactivation request to one of the order care system or the FMS via the transmitting module. The service module is a Gateway Mobile Location Centre Positioning Client (GMLC-PC).

[0018] In one or more embodiments, the acquisition module is further configured to trigger, via a scheduler, the service module at a periodic time interval to acquire the information corresponding to the CPE from the LMF for monitoring the CPE.

[0019] In one or more embodiments, the information further comprises subscription data corresponding to the CPE including a Subscriber Permanent Identifier (SUPI) of the CPE, and the positional information comprises longitude and latitude coordinates of a geographical location corresponding to the CPE.BRIEF DESCRIPTION OF DRAWINGS

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

[0021] FIG. 1 illustrates an exemplary environment of a communication network, in accordance with an embodiment of the present disclosure.

[0022] FIG. 2 illustrates an exemplary block diagram depicting components of a core network, in accordance with an embodiment of the present disclosure.

[0023] FIG. 3 illustrates a block diagram depicting an architecture of a communication system for location-based deactivation of a Customer Premise Equipment (CPE) provisioned in the communication network, in accordance with an embodiment of the present disclosure.

[0024] FIG. 4 illustrates a block diagram depicting a system architecture of a Gateway Mobile Location Centre (GMLC), in accordance with an embodiment of the present disclosure.

[0025] FIG. 5 illustrates a flowchart depicting a method for location-based deactivation of the CPE provisioned in the communication network, in accordance with an embodiment of the present disclosure.DETAILED DESCRIPTION OF THE INVENTION

[0026] 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 morecomponents from one embodiment may be tacitly assumed to be present or used in any other embodiment.

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

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

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

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

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

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

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

[0034] An object of the present disclosure is to provide a system and a method for location-based deactivation of a Customer Premise Equipment (CPE) in a communication network. Another object of the present disclosure is to provide a system and a method that detects change in location of the CPE. Yet another objectof the present disclosure is to provide a system and a method that deactivates or deregisters the CPE upon detecting the change in the location of the CPE.

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

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

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

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

[0039] 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 but not limited to 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.

[0040] Further, depending on the network 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 non-limiting example, the “device” in this disclosure wirelessly accesses the nodes (i.e., gNB 104). In a nonlimiting example, the CPE 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.

[0041] In an embodiment, each of the network devices 106 are configured to be coupled with one or more user devices 108-1, 108-2, 108-3, 108-4, through 108-(N- 1), 108-N (collectively referred to as the “user devices 108”, “User Equipment (UE) 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 UE 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.

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

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

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

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

[0046] 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. The CPE is configured to communicate with a plurality of network elements of the core network 102.

[0047] The plurality of network elements of the core network 102 includes an 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) function 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-Proxy Control (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 asDRA 230), 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).

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

[0049] 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 one or more user device 108 and SMSF 214, session management messages transport between the one or more user device 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.

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

[0051] 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 that is capable of performing authentication.

[0052] The UDM 210 may be a network element that is 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.

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

[0054] The LMF 218 may be a network element that is 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 locationbased service platforms to ensure seamless mobility management and locationbased service provisioning for the subscribers.

[0055] The SMF 220 may be a network element that is 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 datanotification, manage roaming functionality, and / or perform other types of control plane processes for managing user plane data.

[0056] The NWDAF 222 may be a network element that is capable of collecting analytics information associated with RAN and / or the core network 102. The CHF- PC 224 may be a network element that is 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.

[0057] The NEF 226 may be a network element that is 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 route signaling messages based a destination point code in core network 102. In some aspects of the present disclosure, the STP 228 acts a router that relays network messages between signaling end points and other signal transfer points in the core network 102.

[0058] The DRA 230 may be a network element that provides real-time routing capabilities to ensure that messages are routed among the correct elements in the network. The BSF 232 may be a network element that is capable of managing session bindings and subscriber contexts within the core network 102.

[0059] The GMLC 234 is a critical network element configured to provide locationbased 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, and asset tracking. 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.

[0060] The LCS client 240 may be a network element that is 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.

[0061] The UPF 238 may be a network element that is 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.

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

[0063] FIG. 3 illustrates a block diagram depicting an architecture of a communication system 300 for location-based deactivation of the CPE provisioned in the communication network 100, in accordance with an embodiment of the present disclosure. The embodiment of the communication system 300 as shown in FIG. 3 is for illustration only. However, the communication 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 communication system 300.

[0064] As shown in FIG. 3, the communication system 300 (alternatively referred to as system 300) includes the AMF node 202, the LMF node 218, a Customer OrderManagement (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.

[0065] 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 detecting the change in location of the CPE provisioned in the communication network 100. The service module 330 corresponds to a Positioning Client (PC) module. 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 NLt and NLs interfaces within the core network 102.

[0066] The COM system 310 corresponds to an order care system (alternatively referred to as an “order care system 310”) that is configured to manage customer orders or requests for location-based deactivation of an equipment in the communication network 100, for example, the CPE. Further, the COM system 310 also initiates provisioning request for a new equipment, for example, the CPE. The COM system 310 forwards the provisioning request for a new CPE 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, a status information of the CPE, Subscriber Permanent Identifier (SUPI) and positional information. The positional information of the CPE includes longitude and latitude coordinates of a geographical location corresponding to the CPE where the CPE is installed. The status information includes an active, de-active, registered, or de-registered status of the CPE.

[0067] The FMS 320 processes the provisioning request received from the COM system 310 using the acquired the CPE information and sends the processed information to the service module 330. The service module 330 stores the CPE information from the FMS 320 in the database 340. The FMS 320 thus completes the CPE provisioning in the communication network 100 through the GMLC-PC 332 and other network elements.

[0068] For the CPE that is provisioned in the communication network 100, the GMLC 234 may receive request from the FMS for deactivation of the CPE. The GMLC 234 is configured to detect change in location of the CPE periodically or based on the request received from the COM system 310 via the FMS 320. Upon receiving the request, the service module 330, via the GMLC-PC 332, is configured to acquire one or more of the SUPI and a current positional information of the provisioned CPE for monitoring the CPE, from the LMF 218 via the AMF 202. In one embodiment, the service module 330 may utilize a scheduler for triggering the GMLC-PC 332 to acquire one or more of the SUPI and the current positional information of the CPE, periodically at a pre-defined time interval or post a predefined event, for monitoring the CPE. The information acquired corresponding to the CPE is processed by the service module 330 and stored in the database 340.

[0069] The database 340 is configured to store the 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.

[0070] The service module 330, via the GMLC-PC 332, processes the one or more of the SUPI and the positional information of the CPE for monitoring the CPE, to detect the change in the location of the CPE. Further, the service module 330, via the GMLC-PC 332, is configured to inform other network elements to deactivatethe CPE from the communication network 100 when there is a change in the location of the CPE. The deactivation of the CPE may correspond to suspending or deregistering the CPE from the communication network 100, to terminate access of the CPE to the services of the communication network 100. When there is no change in the location of the CPE, the service module 330 is configured to acquire the information corresponding to the CPE from the LMF 218 for monitoring the CPE. Thereupon, the service module 330 continues to monitor the information to detect the change in the location.

[0071] FIG. 4 illustrates a block diagram depicting a system architecture of the GMLC node 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.

[0072] As shown in FIG. 4, the GMLC node 234 includes one or more processors 402 (hereinafter may also be referred to as “processor 402” or “at least one processor 402”), a memory 404, a communication interface 406, a scheduler 408, and a plurality of module(s) 410 (hereinafter interchangeably referred to as “module(s) 410”). Components of the GMLC 234 are communicatively coupled to each other via a communication bus 412.

[0073] The processor 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 modules 410 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 402 to the othersubsystems of the GMLC 234, as the communication bus 412, without deviating from the scope of the present disclosure.

[0074] The processor 402 is configured to execute instructions 404-1 (hereinafter also referred to as “a set of instructions 404-1”) stored in the memory 404 and to perform various processes. The processor 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 402 is configured to execute programs and other processes stored in the memory 404. The processor 402 is further configured to move data into or out of the memory 404 as required by an execution process.

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

[0076] In an embodiment, the module(s) 410 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 non-limiting 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 module(s) 410 may include suitable logic, circuitry, interfaces, and / or codes. For example, the programming for the module(s) 410 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the module(s) 410 may comprise a processing resource (for example, one or more processors), to execute such instructions. In an embodiment, the module(s) 410 may be combined to a single module or each module of the module(s) 410 may be further subdivided into different modules.

[0077] In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the module(s) 410. 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 module(s) 410 may be implemented using an electronic circuitry.

[0078] In one or more embodiments, the module(s) 410 may include one or more modules such as a reception module 410-1, an acquisition module 410-2, a determination module 410-3, a transmitting module 410-4, and a service module 410-5 (same as the service module 330). Each of the module(s) 410 is communicatively coupled with each other.

[0079] In an aspect, the processor 402, via the reception module 410-1, is configured to request from the FMS 320 for deactivation of the CPE. Upon receiving the request, the acquisition module 410-2 is configured to acquire real-time information corresponding to the CPE from the LMF 218 for monitoring the CPE. The real-time information corresponding to the CPE includes one or more of the SUPI of the CPE and the longitude and latitude coordinates of a current geographical location of the CPE. The acquisition module 410-2, via the service module 410-5, acquires the real-time information corresponding to the CPE from the LMF 218 for monitoring the CPE.

[0080] The determination module 410-3 determines a mismatch between the current positional information of the CPE and the positional information of the CPE stored in the database 340. The determination module 410-3, using the GMLC-PC 332, determines the mismatch between the current positional information of the CPE and the positional information of the CPE by comparing the current positional information of the CPE and the positional information of the CPE. Upon determining the change in the location of the CPE, the transmitting module 410-4 isconfigured to send a deactivation request to the FMS 320 to deactivate the CPE, based on the determined change in the location of the CPE. In another embodiment, upon determining the change in the location of the CPE, the transmitting module 410-4 is configured to transmit the deactivation request to the COM system 310 via the FMS 320. Thereafter, the transmitting module 410-4 terminates the acquisition of the information corresponding to the CPE from the LMF 218 for monitoring the CPE based on a response received from the FMS 320. The response includes a deactivated status of the CPE.

[0081] Further, the service module 410-5 may host the plurality of microservices (or alternatively referred to as “microservices”). Among the microservices, a microservice may correspond to the GMLC-PC 332 microservice. The GMLC 234 may utilize a plurality of computing resources where the plurality of microservices may be deployed, and a plurality of storage devices such as a database 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 from the LMF 218 and initiating sending of the deactivation request to one of the COM system 310 or the FMS 320 via the transmitting module 410-4.

[0083] 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 module(s) 410 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 communication system 300.

[0084] The memory 404 stores the set of instructions 404-1 required by the processor 402 for controlling its overall operations. A part of the memory 404 mayinclude 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. 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.

[0085] The communication interface 406 may manage communications with the nodes 104 or the CPE. For example, the communication interface 406 may manage the transfer of the status information of the CPE, the Subscriber Permanent Identifier (SUPI) and the positional information corresponding to customer orders for monitoring the CPE for location-based deactivation of the CPE provisioned in the communication network 100. 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.

[0086] The scheduler 408 may be connected to the service modules 410-5 of the processor 402 for periodically triggering the GMLC-PC 332 to acquire one or more of the SUPI and the current positional information of the CPE, periodically at a predefined time interval or a pre-defined event, for monitoring the CPE. The scheduler 408 is configured to schedule execution of analytical tasks and job workflowsallocated 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 is also configured to cause a trigger to the service module 410-5 to update the database 340 with the acquired one or more of the SUPI and the current positional information of the CPE.

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

[0088] FIG. 5 illustrates a flowchart depicting a method 500 for location-based deactivation of the CPE in the communication network 100, in accordance with an embodiment of the present disclosure. The method 500 comprises a series of operations indicated by steps 502 through 512. Although method 500 shows example blocks of steps 502 to 512, in some embodiments, the method 500 may include additional steps, fewer steps or steps in different order than those depicted in FIG. 5. In other embodiments, the steps 502-512 may be combined or may be performed in parallel.

[0089] Once the CPE is provisioned in the communication network 100, the GMLC node 234, at step 502, may receive, via the reception module 410-1, a request from FMS 320 for monitoring the CPE for location-based deactivation. Upon receiving the request, at step 504, the acquisition module 410-2 is configured to acquire information corresponding to the CPE from the LMF 218 for monitoring the CPE. The information corresponding to the CPE is a real-time information comprising one or more of the SUPI and the current positional information of the provisioned CPE. In one embodiment, the acquisition module 410-2 may trigger the service module 330 using the scheduler 408 to periodically acquire, via the GMLC-PC 332, at the periodic time interval or at the pre-defined event, one or more of the SUPI and the current positional information for monitoring the CPE from the LMF 218via the AMF 202. In another embodiment, the acquisition module 410-2 may trigger the service module 330 using the scheduler 408 to fetch, via the GMLC-PC 332, one or more of the SUPI and the current positional information on demand by the COM system 310 for monitoring the CPE from the LMF 218 via the AMF 202, when the COM system 310 receives a request to deactivate the provisioned CPE.

[0090] At step 506, the determination module 410-3, using the GMLC-PC 332, determines the mismatch between the current positional information of the CPE acquired from the LMF 218 and the positional information of the CPE stored in the database 340. The mismatch may be determined by comparing the current positional information of the CPE and the positional information of the CPE.

[0091] In one aspect, when the determination module 410-3 determines that the current positional information acquired from the provisioned CPE does not match with the positional information of the provisioned CPE stored in the database 340, the GMLC-PC 332 detects a change in the location of the CPE. The GMLC-PC 332 is configured to detect the change in the location when there is the mismatch in the positional information of the provisioned CPE, outside of a pre-defined range of distance from the positional information of the provisioned CPE. In one embodiment, the pre-defined range of distance may be defined based on accuracy of capturing the positional information and may be dependent on a configuration of a Global Positioning System (GPS) sensor installed in the CPE.

[0092] At step 508, upon detecting the change in the location of the provisioned CPE, the acquisition module 410-2 initiates an API call to the service module 330 to the FMS 320 for sending a deactivation request to the FMS 320 to deactivate the CPE from the communication network 100. Thereupon, the transmitting module 410-4 transmits the deactivation request to the FMS 320. In another embodiment, the transmitting module 410-4 transmits the deactivation request to the COM system 310 via the FMS 320.

[0093] Corresponding to the deactivation request, one of the COM system 310 or the FMS 320 may deactivate the CPE at the deactivation request to deactivate theCPE at the UDM node 210 of the communication network 100. The FMS 320 may update the status information of the CPE in a Unified Data Management (UDM) profile of the CPE as “deactivated, inactive, or deregistered”.

[0094] At step 510, the reception module 410-1 is configured to receive from the FMS 320, a response including the deactivated status of the CPE at the UDM node corresponding to the deactivation request sent to one of the COM system 310 or the FMS 320.

[0095] Upon deactivation the CPE from the communication network 100, at step 512, based on the received response, the service module 330 updates the status information of the CPE in the database 340 as “deactivated, inactive or deregistered”. The transmitting module 410-4 terminates the triggering of the GMLC-PC 332 from acquiring one or more of the SUPI and the current positional information of the CPE from the LMF 218 for monitoring the CPE.

[0096] Furthermore, the FMS 320 sends a message to the COM system 310 indicating that there is a change in the positional information of the CPE and the CPE has been deactivated from the communication network 100. The service module 330, via the GMLC-PC 332, is configured to indicate to the COM system 310, any new request for registering or activating the deprovisioned CPE from the COM system 310 will be marked “failed”.

[0097] In another aspect, at step 506, when the determination module 410-3 determines that the positional information fetched from the CPE matches with the positional information of the provisioned CPE stored in the database 340 or is within the pre-defined range of distance from the positional information of the provisioned CPE, the acquisition module 410-2, using the GMLC-PC 332, continues to acquire the positional information of the provisioned CPE, periodically or on demand by the FMS 320, for monitoring and detecting the change in the location of the CPE.

[0098] Now, referring to the technical abilities and advantageous effect of the present disclosure, the embodiments disclosed herein provides a system and amethod capable of deactivation the CPE by detecting changes in location of CPE using available location data of the provisioned CPE, periodically or on demand. The system may be used to analyze location data of the CPE over a specified timeperiod and identify patterns indicating periodic changes in movement of the CPE. By identifying patterns of the movement of the CPE, a network operations team may initiate a proactive response in deactivation the CPE upon detecting a change in the location of the CPE beyond its normal patterns. The system may also enable the network operations team to detect a theft of the CPE and helps a consumer by swiftly deactivation the CPE in case of the theft, thereby avoiding misuse of the CPE. As a result, service quality for end-users is improved as there is high precision and minimal delay in deactivation the CPE. Furthermore, the system and the method help in optimization of efficiency of the communication network by enhancing resource utilization.

[0099] Embodiments of the present technology may be described herein with reference to flowchart illustrations of methods and systems according to embodiments of the technology, and / or procedures, algorithms, steps, operations, formulae, or other computational depictions, which may also be implemented as computer program products. In this regard, each block or step of the flowchart, and combinations of blocks (and / or steps) in the flowchart, as well as any procedure, algorithm, step, operation, formula, or computational depiction can be implemented by various means, such as hardware, firmware, and / or software including one or more computer program instructions embodied in computer-readable program code. As will be appreciated, any such computer program instructions 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 perform a group of operations comprising the operations or blocks described in connection with the disclosed methods.

[0100] Further, these computer program instructions, such as embodied in computer-readable program code, may also be stored in one or more computer- readable memory or memory devices (for example, the memory 404) that can directa computer processor or other programmable processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory or memory devices produce an article of manufacture including instruction means which implement the function specified in the block(s) of the flowchart(s).

[0101] It will further be appreciated that the term “computer program instructions” as used herein refer to one or more instructions that can be executed by the one or more processors (for example, the processor 402) to perform one or more functions as described herein. The instructions may also be stored remotely such as on a server, or all or a portion of the instructions can be stored locally and remotely.

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

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

[0104] 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.LIST OF REFERENCE NUMERALS

[0105] 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:100 - Communication network102 - Core network104 - Plurality of nodes106 - Plurality of network devices108 - 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-Proxy Control (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 - Communication system310 - Customer Order Management (COM) system320 - Fulfillment Management System (FMS)330 - Service module340 - Database402 - Processor(s)404 - Memory406 - Communication interface408 - Scheduler410 - Module(s)410-1 - Reception Module410-2 - Acquisition Module410-3 - Determination Module410-4 - Transmitting Module410-5 - Service Module412 - Communication bus500 - Method for location-based deactivation of the CPE in the communication network502-512 - Operational steps of method 500

Claims

WE CLAIM:

1. A method (500) for location-based deactivation of a Customer Premise Equipment (CPE) in a communication network (100), the method (500) comprising: receiving, by a reception module (410-1) in a Gateway Mobile Location Centre (GMLC) node (234), a request from a Fulfilment Management System (FMS) (320) for monitoring the CPE for the locationbased deactivation; acquiring, by an acquisition module (410-2) from a Location Management Function (LMF) (218) via a service module (330, 410-5) in the GMLC node (234), information corresponding to the CPE upon receiving the request for monitoring the CPE, the information comprises a current positional information of the CPE; determining, by a determination module (410-3) in the GMLC node (234), a change in a location of the CPE based on a mismatch between the current positional information of the CPE and positional information of the CPE stored in a database; transmitting, by a transmitting module (410-4) in the GMLC node (234), based on the determined change in the location of the CPE, a deactivation request to one of an order care system (310) or the FMS (320) to deactivate the CPE from the communication network (100); and terminating, by the transmitting module (410-4), the acquisition of the information corresponding to the CPE from the LMF (218) for monitoring the CPE, based on a response including a deactivated status of the CPE received from the one of the order care system (310) or the FMS (320).

2. The method (500) as claimed in claim 1, further comprising: sending, by the transmitting module (410-4) to one of the order care system (310) or the FMS (320), the deactivation request to deactivate theCPE at a Unified Data Management (UDM) (210) node of the communication network (100); and receiving, by the reception module (410-1) from one of the order care system (310) or the FMS (320), the response including the deactivated status of the CPE at the UDM (210) node corresponding to the deactivation request sent to one of the order care system (310) or the FMS (320).

3. The method (500) as claimed in claim 1, wherein, for determining the change in the location of the CPE, the method (500) comprises: determining, by the determination module (410-3), the mismatch between the current positional information of the CPE and the positional information of the CPE by comparing the current positional information of the CPE and the positional information of the CPE.

4. The method (500) as claimed in claim 1, further comprising: initiating, by the acquisition module (410-2), an Application Programming Interface (API) request to the service module (330, 410-5) for sending the deactivation request to one of the order care system (310) or the FMS (320); and sending, by the service module (330, 410-5), the deactivation request to one of the order care system (310) or the FMS (320) via the transmitting module (410-4), wherein the service module is a Gateway Mobile Location Centre Positioning Client (GMLC-PC).

5. The method (500) as claimed in claim 1, further comprising triggering, by the acquisition module (410-2) via a scheduler (408), the service module (330, 410-5) at a periodic time interval to acquire the information corresponding to the CPE from the LMF (218) for monitoring the CPE.

6. The method (500) as claimed in claim 1, wherein the information further comprises subscription data corresponding to the CPE including a Subscriber Permanent Identifier (SUPI) of the CPE, and the positionalinformation comprises longitude and latitude coordinates of a geographical location corresponding to the CPE.

7. A system (300) of location-based deactivation of a Customer Premise Equipment (CPE) in a communication network (100), the system comprising: a Fulfdment Management System (FMS) (320); and a Gateway Mobile Location Centre (GMLC) node (234) comprising: a reception module (410-1) configured to receive a request from the FMS (320) for monitoring the CPE for the location-based deactivation; an acquisition module (410-2) configured to acquire, from a Location Management Function (LMF) (218) via a service module (330, 410-5) in the GMLC node (234), information corresponding to the CPE upon receiving the request for monitoring the CPE, the information comprises a current positional information of the CPE; a determination module (410-3) configured to determine a change in a location of the CPE based on a mismatch between the current positional information of the CPE and a positional information of the CPE stored in a database; and a transmitting module (410-4) configured to: transmit, based on the determined change in the location of the CPE, a deactivation request to one of an order care system (310) or the FMS (320) to deactivate the CPE from the communication network (100); and terminate the acquisition of the information corresponding to the CPE from the LMF (218) for monitoring the CPE, based on a response including a deactivated status of the CPE received from one of the order care system (310) or the FMS (320).

8. The system (300) as claimed in claim 7, wherein the transmitting module (410-4) is further configured to: send, to the FMS (320), the deactivation request to deactivate the CPE at a Unified Data Management (UDM) (210) node of the communication network (100), and wherein the reception module (410-1) is configured to receive from one of the order care system (310) or the FMS (320), the response including the deactivated status of the CPE at the UDM (210) node corresponding to the deactivation request sent to one of the order care system (310) or the FMS (320).

9. The system (300) as claimed in claim 7, wherein, for determining the change in the location of the CPE, the determination module (410-3) is configured to: determine the mismatch between the current positional information of the CPE and the positional information of the CPE by comparing the current positional information of the CPE and the positional information of the CPE.

10. The system (300) as claimed in claim 7, wherein the acquisition module (410-2) is further configured to: initiate an Application Programming Interface (API) request to the service module (330, 410-5) for sending the deactivation request to one of the order care system (310) or the FMS (320); and send, by the service module (330, 410-5), the deactivation request to one of the order care system (310) or the FMS (320) via the transmitting module (410-4), wherein the service module (330, 410-5) is a Gateway Mobile Location Centre Positioning Client (GMLC-PC).

11. The system (300) as claimed in claim 7, wherein the acquisition module (410-2) is further configured to trigger, via a scheduler (408), the service module (330, 410-5) at a periodic time interval to acquire the information corresponding to the CPE from the LMF (218) for monitoring the CPE.

12. The system (300) as claimed in claim 7, wherein the information further comprises subscription data corresponding to the CPE including a Subscriber Permanent Identifier (SUPI) of the CPE, and the positional information comprises longitude and latitude coordinates of a geographical location corresponding to the CPE.

13. A 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, at a Gateway Mobile Location Centre (GMLC) node, a request from a Fulfilment Management System (FMS) for monitoring a Customer Premise Equipment (CPE) in a communication network for location-based deactivation; acquiring, via a service module in the GMLC node from a Location Management Function (LMF), information corresponding to the CPE upon receiving the request for monitoring the CPE, the information comprises a current positional information of the CPE; determining a change in a location of the CPE based on a mismatch between the current positional information of the CPE and the positional information of the CPE stored in a database; transmitting, based on the determined change in the location of the CPE, a deactivation request to one of the order care system or the FMS to deactivate the CPE from the communication network; and terminating the acquisition of the information corresponding to the CPE from the LMF for monitoring the CPE, based on a response including a deactivated status of the CPE received from one of the order care system or the FMS.

Images