WO2025196801A1

WO2025196801A1 - A method and system for determining a relocation of a customer premises equipment

Info

Publication number: WO2025196801A1
Application number: PCT/IN2025/050234
Authority: WO
Inventors: Pradeep Kumar Bhatnagar; Aayush Bhatnagar; Haresh Ambaliya; Abhinav RANA; Isha Saini; Mayank Rajput
Original assignee: Jio Platforms Ltd
Current assignee: Jio Platforms Ltd
Priority date: 2024-03-21
Filing date: 2025-02-17
Publication date: 2025-09-25
Anticipated expiration: 2026-09-21

Abstract

The present disclosure relates to a system (102) and a method (400) for identifying 5 a relocated Customer Premises Equipment (CPE) in a network (104). Current geolocation data of the CPE is obtained. A first deviation in location of the CPE is determined by comparing the current geolocation data with stored geolocation data of the CPE. A deviation counter is incremented if the determined first deviation exceeds a predefined threshold. The stored geolocation data is replaced with a 10 centroid of geolocation data obtained over a predefined period when the deviation counter reaches a predefined count within the predefined period. A second deviation between the replaced geolocation data and a centroid of geolocation data obtained over the predefined period is determined. The CPE is marked as relocated if the determined second deviation exceeds a second predefined threshold, and the 15 deviation counter reaches the predefined count within the predefined period.

Description

A METHOD AND SYSTEM FOR DETERMINING A RELOCATION OF A CUSTOMER PREMISES EQUIPMENT

RESERVATION OF RIGHTS

[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as but are not limited to, copyright, design, trademark, integrated circuit (IC) layout design, and/or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.

TECHNICAL FIELD

[0002] The present disclosure generally relates to the field of communication systems. More particularly, the present disclosure relates to a method and a system for identifying a relocated Customer Premises Equipment (CPE) in a network.

DEFINITION

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

[0004] The expression ‘Customer Premises Equipment (CPE)’ used hereinafter in the specification refers to a terminal device that receives the signals directly issued from a base station and then converts them into Wireless Fidelity (Wi-Fi) signals or wired signals. The CPE is located at a customer’s site, facilitating access to service provider networks. The CPE includes devices such as modems, routers, set-top boxes, VoIP phones, and Wi-Fi extenders. The CPE can be installed indoors or outdoors.

[0005] The expression ‘subscriber’ used hereinafter in the specification refers to a person who uses cellular services like voice calls, data service, email, streaming media, video calls, etc., with the help of a cell phone/tablet or any other device.

[0006] The expression ‘Latitude’ used hereinafter in the specification refers to is the measurement of distance north or south of the Earth's equator, expressed in degrees.

[0007] The expression ‘Longitude’ used hereinafter in the specification refers to the measurement of distance east or west of the Prime Meridian, expressed in degrees.

[0008] The expression ‘LSR’ used hereinafter in the specification refers to Long-Term Evolution (LTE) session record data. The LSR refers to the detailed log of network sessions established by the CPE, including information such as connection parameters, data usage, session duration, and signal strength during the LTE connectivity.

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

BACKGROUND OF THE DISCLOSURE

[0010] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.

[0011] In modern telecommunications, efficient network optimization is crucial for maintaining high-quality service and minimizing disruptions. Customer Premises Equipment (CPE) plays a significant role in ensuring reliable connectivity between service providers and end-users. However, one of the challenges faced by network operators is the inability to track the relocation status of CPE. This lack of information can lead to suboptimal network performance and difficulty in troubleshooting connectivity issues. [0012] The current techniques fail to monitor the relocation of CPE, including the distance they have been moved and their new positions relative to nearby buildings. This gap in information prevents service providers from making informed decisions about network adjustments and optimization.

[0013] Another significant issue that can arise from CPE relocation is line of sight (LOS) problems or changes in the distance from the reception point. These factors can severely impact signal quality and overall network performance. Tracking relocated CPE can help optimize LOS and reception at the CPE, ensuring consistent and reliable service.

[0014] There is, therefore, a need in the art to provide a system and a method to mitigate the problems associated with the existing techniques. Specifically, there is a need for the system and the method to accurately track the location and relocation of the CPEs.

SUMMARY OF THE DISCLOSURE

[0015] In an exemplary embodiment, the present disclosure discloses a method for identifying a relocated Customer Premises Equipment (CPE) in a network. The method comprising obtaining, by a receiving unit, current geolocation data of the CPE. The method comprising determining, by a processing unit, a first deviation in location of the CPE by comparing the current geolocation data with stored geolocation data of the CPE. The method comprising incrementing, by the processing unit, a deviation counter if the determined first deviation exceeds a predefined threshold. The method comprising replacing, by the processing unit, the stored geolocation data with a centroid of geolocation data obtained over a predefined period when the deviation counter reaches a predefined count within the predefined period. The method comprising determining, by the processing unit, a second deviation between the replaced geolocation data with a centroid of geolocation data obtained over the predefined period. The method comprising marking, by the processing unit, the CPE as relocated if the determined second deviation exceeds a second predefined threshold, and the deviation counter reaches the predefined count within the predefined period.

[0016] In some embodiments, the method further comprising identifying, by the processing unit, a nearest building for the CPE based on the stored geolocation data, and tagging the CPE with a unique identifier of the nearest building. The nearest building is identified using a unique building identifier, building name, and building coordinates.

[0017] In some embodiments, the second predefined threshold is greater than the predefined threshold. The predefined threshold and the second predefined threshold are configurable values.

[0018] In some embodiments, the method further comprising resetting the deviation counter to zero if the deviation counter does not reach the predefined count within the predefined period.

[0019] In some embodiments, the method further comprising maintaining records of the geolocation data and deviation distance for the CPE.

[0020] In some embodiments, the records of the geolocation data and the deviation distance include latitude and longitude coordinates of the CPE and the determined second deviation respectively.

[0021] In an exemplary embodiment, the present disclosure discloses a system for identifying a relocated Customer Premises Equipment (CPE) in a network. The system includes a receiving unit configured to obtain current geolocation data of the CPE and a processing unit coupled with the receiving unit. The processing unit is configured to determine a first deviation in location of the CPE by comparing the current geolocation data with stored geolocation data of the CPE. The processing unit is configured to increment a deviation counter if the determined first deviation exceeds a predefined threshold. The processing unit is configured to replace the stored geolocation data with a centroid of geolocation data obtained over a predefined period when the deviation counter reaches a predefined count within the predefined period. The processing unit is configured to determine a second deviation between the replaced geolocation data with a centroid of geolocation data obtained over the predefined period. The processing unit is configured to mark the CPE as relocated if the determined second deviation exceeds a second predefined threshold, and the deviation counter reaches the predefined count within the predefined period.

[0022] In another exemplary embodiment, the present invention discloses a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for identifying a relocated Customer Premises Equipment (CPE) in a network. The method comprising obtaining, by a receiving unit, current geolocation data of the CPE. The method comprising determining, by a processing unit, a first deviation in location of the CPE by comparing the current geolocation data with stored geolocation data of the CPE. The method comprising incrementing, by the processing unit, a deviation counter if the determined first deviation exceeds a predefined threshold. The method comprising replacing, by the processing unit, the stored geolocation data with a centroid of geolocation data obtained over a predefined period when the deviation counter reaches a predefined count within the predefined period. The method comprising determining, by the processing unit, a second deviation between the replaced geolocation data with a centroid of geolocation data obtained over the predefined period. The method comprising marking, by the processing unit, the CPE as relocated if the determined second deviation exceeds a second predefined threshold, and the deviation counter reaches the predefined count within the predefined period.

[0023] The foregoing general description of the illustrative embodiments and the following detailed description thereof are merely exemplary aspects of the teachings of this disclosure and are not restrictive.

OBJECTIVES OF THE DISCLOSURE

[0024] Some of the objectives of the present disclosure, which at least one embodiment herein satisfies are as listed herein below:

[0025] An objective of the present disclosure is to identify a relocated Customer Premises Equipment (CPE) in a network, thereby eliminating the need for manual tracking and its associated limitations.

[0026] Another objective of the present disclosure is to improve accuracy in identifying accurate relocations of the CPE.

[0027] Another objective of the present disclosure is to improve network performance and a seamless user experience.

[0028] Another objective of the present disclosure is to automate device relocation tracking to significantly reduce the manual workload and associated costs for network management teams.

BRIEF DESCRIPTION OF DRAWINGS

[0029] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes the disclosure of electrical components, electronic components, or circuitry commonly used to implement such components.

[0030] FIG. 1 A illustrates an exemplary network architecture implementing a system for identifying a relocated Customer Premises Equipment (CPE) in a network, in accordance with an embodiment of the present disclosure.

[0031] FIG. IB illustrates an exemplary system architecture for identifying the relocated CPE in the network, in accordance with an embodiment of the present disclosure.

[0032] FIG. 2 illustrates an exemplary flow diagram of a method for identifying the relocated CPE in the network, in accordance with an embodiment of the present disclosure.

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

[0034] FIG. 4 illustrates another exemplary flow diagram of the method for identifying the relocated CPE in the network, in accordance with an embodiment of the present disclosure.

[0035] The foregoing shall be more apparent from the following detailed description of the disclosure.

LIST OF REFERENCE NUMERALS

100A - Network Architecture

102 -System

104 -Network

106 - Centralized Server

108-1, 108-2. . . 108-N - User Equipments

110-1, 110-2...110-N - Users

152a, 152b, 152c -Customer Premises Equipment (CPE)

158 - Location Determining Unit

160 -Receiving Unit

162 -Processing Unit 164 - Data storage module

200, 400 - Flow diagram

300 - Computer System

310 - External Storage Device

320 - Bus

330 - Main Memory

340 - Read Only Memory

350 - Mass Storage Device

360 - Communication Port

370 - Processor

DETAILED DESCRIPTION

[0036] In the following description, for explanation, various specific details are outlined in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address all of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein.

[0037] The ensuing description provides exemplary embodiments only and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0038] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail to avoid obscuring the embodiments.

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

[0040] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive like the term “comprising” as an open transition word without precluding any additional or other elements.

[0041] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0042] The terminology used herein is to describe particular embodiments only and is not intended to be limiting the disclosure. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any combinations of one or more of the associated listed items.

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

[0044] FIG. 1A illustrates an exemplary network architecture (100 A) for implementing a system (102) for identifying a relocated Customer Premises Equipment (CPE) (152a, 152b, 152c) in a network (104), in accordance with embodiments of the present disclosure.

[0045] In an embodiment, the system (102) is connected to the network (104), which is further connected to at least one user equipment (108-1, 108-2, ... 108-N) (collectively referred to as user equipments (108)) associated with one or more users (110-1, 110-2, ... 110-N) (collectively referred to as users (110)). The user equipment (108) may be personal computers, laptops, tablets, wristwatches, or any custom-built computing device integrated within a modern diagnostic machine that can connect to a network as an Internet of Things (loT) device. In an embodiment, the user equipment (108) may be referred to as User Equipment (UE) or user device. Accordingly, the terms “user equipment” and “User Equipment” may be used interchangeably throughout the disclosure. In an aspect, the users (110) are network operators, field engineers or end users. Further, the network (104) can be configured with a centralized server (106) that stores compiled data.

[0046] In an embodiment, the system (102) may receive at least one input data from the users (110) via the at least one user equipment (108). In an aspect, the at least one input data may include a request from the users (110) to track the CPEs (152a, 152b, 152c), through an application interface of a mobile application installed in the user equipment (108). The mobile application may be configured to communicate with the system (102). In some examples, the mobile application may be a software or a mobile application from an application distribution platform. In an embodiment, the user equipment (108) may transmit the at least one captured data packet over a point-to-point or point-to-multipoint communication channel or network (104) to the system (102).

[0047] The network (104) may include, but not be limited to, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. In an exemplary embodiment, the network (104) may include, but not be limited to, a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public- Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.

[0048] As illustrated in FIG. 1A, the network architecture (100A) may include one or more user equipments (UEs) (108-1 , 108-2. . . 108-N) associated with one or more users (110-1, 110-2. . . 110-N) in an environment. A person of ordinary skill in the art will understand that one or more users (110-1, 110-2... 110-N) may collectively referred to as the users (110). Similarly, a person of ordinary skill in the art will understand that one or more UEs (108-1, 108-2...108-N) may be collectively referred to as the UE (108). Although only three UEs (108) are depicted in FIG. 1A, however, any number of the UE (108) may be included without departing from the scope of the ongoing description.

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

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

[0051] Referring to FIG. 1A, the UE (108) may communicate with the system (102) through the network (104) for sending or receiving various types of data. In an embodiment, the network (104) may include at least one of a 5G network, 6G network, or the like. The network (104) may enable the UE (108) to communicate with other devices in the network architecture (100 A) and/or with the system (102). The network (104) may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network (104) may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, a Public Switched Telephone Network (PSTN), or the like.

[0052] In an embodiment, the network (104) may include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network (104) may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.

[0053] In an embodiment, the UE (108) is communicatively coupled with the network (104). The network (104) may receive a connection request from the UE (108). The network (104) may send an acknowledgment of the connection request to the UE (108). The UE (108) may transmit a plurality of signals in response to the connection request.

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

[0055] FIG. IB illustrates an exemplary system architecture for identifying the relocated CPE (152a, 152b, 152c) in the network (104), in accordance with an embodiment of the present disclosure.

[0056] As shown in Fig. IB, the system (102) may include at least one CPE (152a, 152b, 152c) and a location determining unit (158).

[0057] The CPE (152a, 152b, 152c) may be configured to establish at least one session with the location determining unit (158). The CPE (152a, 152b, 152c) may be configured to receive a transmission from a base station. The CPE (152a, 152b, 152c) may use the Internet Protocol (IP) over a Transmission Control Protocol (TCP) connection to establish the at least one session with the location determining unit (158). For instance, the CPE initiates a TCP connection to the unit’s IP address, allowing for reliable, continuous data transmission. The transmission between the base station and the CPE (152a, 152b, 152c) is bidirectional. The CPE (152a, 152b, 152c) can be installed indoors or outdoors. Indoor CPE is installed inside the customer’s premises. Examples include modems, routers, set-top boxes, VoIP phones, and Wi-Fi extenders. Indoor CPE are designed to be compact and aesthetically pleasing, integrating seamlessly with a home or office environment. They are usually easier to install and maintain and are protected from weather elements, which helps in ensuring their longevity. Outdoor CPE: As the name suggests, outdoor CPE (ODCPE) is installed outside the customer's premises. This type of equipment includes outdoor modems, antennas, and receivers, which are designed to withstand harsh environmental conditions such as rain, snow, and extreme temperatures. Outdoor CPE is often used in rural or suburban areas where traditional wired connections might not be feasible. These devices usually have rugged, weather-resistant housings and are equipped with high-gain antennas to ensure reliable signal reception over greater distances. The CPE (152a, 152b, 152c) plays a crucial role in ensuring reliable connectivity, optimizing network performance, and allowing customers to customize their network setup to meet specific needs. The CPE (152a, 152b, 152c) may be further configured to transmit a trace data report over the at least one established session. In an aspect, the CPE (152a, 152b, 152c) may include an antenna for receiving and transmitting wireless signals. In some examples, at least one antenna is a near field antenna, a Wi-Fi antenna, and a radio frequency antenna. In an example, the trace data report may include measurement data and/or trace data. The measurement data may include numeric information such as the number of received/sent data packages per second, resource utilization percentage, or the like. The trace data may include information regarding events that are determined to belong together. For example, the trace data may include logs/information, timing advance, radio access (standalone, non-standalone), radio type (4G, 5G), received signal strength indicator (RSSI), and the duration of a session. In an example, the CPE (152a, 152b, 152c) may be configured to transmit the trace data report to the location determining unit (158). In an aspect, the location determining unit (158) may be configured to send a request to the CPE (152a, 152b, 152c) for sending the trace data report. In another aspect, the CPE (152a, 152b, 152c) may be configured to transmit the trace data reports to a third-party data storage application, from where the location determining unit (158) may retrieve the stored trace data reports.

[0058] The location determining unit (158) may be configured to determine the relocation of the CPE (152a, 152b, 152c). The location determining unit (158) may include a receiving unit (160), a processing unit (162), and a data storage module (164).

[0059] The receiving unit (160) may be configured to receive the trace data report transmitted by the CPE (152a, 152b, 152c). In an aspect, the receiving unit (160) may include at least one antenna for transmitting and receiving communications packets or records to/from the CPE (152a, 152b, 152c) via a wireless access node. In some examples, at least one antenna is a near-field antenna, a Wireless Fidelity (Wi-Fi) antenna, and a radio frequency antenna. The receiving unit (160) may include a wireless-frequency transceiver having a variable gain amplifier that generates radio-frequency signals for transmission. A wireless amplifier circuit may be used to amplify the radio-frequency signals at the output of the variable gain amplifier for transmission through a plurality of antennas.

[0060] The processing unit (162) may be configured to couple with the receiving unit (160) to receive the trace data report from the receiving unit (160). The received trace data report (also referred to as, for example, raw data) has multiple sessions for the CPE (152a, 152b, 152c), and each session has a different duration.

[0061] On receiving the report, the processing unit (162) may be configured to extract a plurality of values corresponding to at least one attribute from the received trace data report corresponding to each established session. In an example, the at least one attribute is a combination of a longitude, and a latitude coordinates. In an example, to extract the longitude and latitude coordinates from the trace data report, the processing unit (162) may use techniques such as parsing structured data formats, e.g., JavaScript Object Notation (JSON) or extensible Markup Language (XML) to directly retrieve the relevant fields.

[0062] In an embodiment, the data storage module (164) is configured to store program instructions. The data storage module (164) is configured to store the trace data report received from the receiving unit (160). The program instructions include a program that implements a method to determine the relocation of the CPE (152a, 152b, 152c) in accordance with embodiments of the present disclosure and may implement other embodiments described in this specification. The data storage module (164) may be configured to store pre-processed data, and the predefined set of parameters. The data storage module (164) may include any computer-readable medium known in the art, including, for example, volatile memory, such as Static Random Access Memory (SRAM) and Dynamic Random Access Memory (DRAM) and/or non-volatile memory, such as Read Only Memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes. For example, the data storage module (164) may be configured to store a list of manufacturers of the CPE (152a, 152b, 152c).

[0063] The processing unit (162) may be configured to fetch and execute computer-readable instructions stored in the data storage module (164). The processing unit (162) may be configured to execute a sequence of instructions of the method to determine the relocation of the CPE (152a, 152b, 152c), which may be embodied in a program or software. The instructions can be directed to the processing unit (162), which may subsequently program or otherwise be configured to implement the methods of the present disclosure. In some examples, the processing unit (162) is configured to control and/or communicate with large databases, perform high-volume transaction processing, and generate reports from large databases. The processing unit (162) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions.

[0064] In an embodiment, the data storage module (164) may be responsible for storing essential information about the CPE (152a, 152b, 152c), nearby buildings, and relocation tracking data. The data storage module (164) may serve as a memory for the system (102), providing persistent storage for crucial tracking information.

[0065] In an embodiment, the data storage module (164) may be structured with components like a database system (potentially structured query language (SQL) or (NoSQL) for organized storage of CPE (152a, 152b, 152c) details, building information, and relocation history. Additionally, a file storage system may be employed to store raw data or log files. Key data elements may be managed by the data storage module (164) and may include the CPE (152a, 152b, 152c) geolocation coordinates, building information such as building reference identifier (ID), building name, and latitude/longitude, and relocation details. These specific data elements may form a comprehensive dataset crucial for tracking the geospatial dynamics of the CPE (152a, 152b, 152c), associating them with nearby buildings, and determining their relocation status with precision.

[0066] In an embodiment, the CPE (152a, 152b, 152c) geolocation may include latitude and longitude coordinates of the CPE (152a, 152b, 152c) and previous record of the CPE (152a, 152b, 152c) past geolocation coordinates. The historical geolocation data may support in determining deviations in the CPE (152a, 152b, 152c) movement over time. In an embodiment, building information may include at least one Unique Building Identifier (BI). The BI is a specific identifier that may be assigned to each building for distinct recognition. This unique identifier is crucial for accurate building association. The building name is included that may comprise of the name or label that is assigned to the identified building. This provides a human-readable reference to the building associated with the CPE (152a, 152b, 152c). At least one building latitude and longitude is included that may comprise of coordinates which pinpoint the exact location of the nearest building, forming a foundational piece for the geospatial relationship between the CPE (152a, 152b, 152c) and its surroundings.

[0067] In an embodiment, the relocation details may include a clear indication of whether the CPE (152a, 152b, 152c) has undergone relocation. A “Yes” confirms relocation, while a “No” indicates that the location of the CPE (152a, 152b, 152c) has remained stable. It may also include the latitude and longitude coordinates representing the location of the CPE (152a, 152b, 152c) before any confirmed relocation. These values serve as a reference point for understanding the movement. It may further include the determined distance of the CPE (152a, 152b, 152c) relocation including the magnitude of the movement of the CPE (152a, 152b, 152c), contributing to a comprehensive understanding of its relocation dynamics.

[0068] In an embodiment, the processing unit (162) executes key processes that may include fetching periodic geolocation updates, identifying and tagging the nearest building for the CPE (152a, 152b, 152c), determining deviations in location, tracking these deviations over time, and confirming relocations based on configurable thresholds and timeframes. The processing unit may also manage data updates and resets for the CPE (152a, 152b, 152c) that may have been confirmed to have relocated.

[0069] FIG. 2 illustrates an exemplary flow diagram of a method (200) for identifying the relocated CPE (152a, 152b, 152c) in the network (104), in accordance with an embodiment of the present disclosure.

[0070] At step 202, the CPE (152a, 152b, 152c) may be configured to establish at least one session with the location determining unit (158) to transmit the trace data report over the at least one established session. In an embodiment, the trace data may include first set of geolocation data such as trace latitude and trace longitude data, logs/information, timing advance, radio access (standalone, non- standalone), radio type (4G, 5G, 6G), Reference Signal Received Power (RSRP), and the duration of a session. Further, the receiving unit (160) of the location determining unit (158) may be configured to receive the transmitted trace data report. The received trace data report (raw data) has multiple sessions for at least one CPE (152a, 152b, 152c), and each session has different duration. The received first set of geolocation data may get stored in a database such as a data storage module (164).

[0071] At step 204, building identification may be conducted. The building identification involves the measurement of distances to nearby buildings for the CPE (152a, 152b, 152c). This step aims to associate the CPE (152a, 152b, 152c) with its closest building within the network infrastructure. The system (102) may calculate the distances to all nearby buildings and tag the CPE (152a, 152b, 152c) with the unique identifier of the nearest building, known as building reference identifier (ID). The relevant building information, including the building name, Building reference ID, latitude, and longitude, may be stored in the data storage module (164), ensuring that the system (102) maintains a detailed record of the spatial relationships between the CPE (152a, 152b, 152c) and the buildings in their proximity. In an embodiment, distance to nearest building is identified and the CPE (152a, 152b, 152c) is tagged to a nearest building reference ID. The advantage of this process is that it ensures precise identification and placement of CPE (152a, 152b, 152c) within the network infrastructure. By tagging the CPE (152a, 152b, 152c) to the nearest building reference ID, the system can efficiently track and manage the CPE (152a, 152b, 152c), reducing the chances of misplacement and ensuring quick identification and resolution of any issues. This enhances the overall reliability and performance of the network.

[0072] At step 206, for every “N” days the steps 202 and 204 are repeated to determine a second set of geolocation data associated with the CPE (152a, 152b, 152c). In an embodiment, the periodic repetition of the steps may be done, for example, for every 7 days to contribute to the ongoing accuracy and relevance of the geolocation and building identification processes for the CPE (152a, 152b, 152c). By executing the step at regular intervals of “N” days (e.g., 7 days), the system (102) ensures that its understanding of locations of the CPE (152a, 152b, 152c) is kept up to date.

[0073] At step 208, a first deviation between the second set of geolocation data and the first set of geolocation data is determined. By computing the difference between the second set of geolocation data and the first set of geolocation data, the system (102) determines the degree of deviation or movement from the established previous position of the CPE (152a, 152b, 152c). This determines deviation value quantifies how far the current location deviates from the expected or previously recorded position. [0074] At step 210, it is determined if the result of the determined first deviation is more than a predefined threshold of X meter (e.g., 10 meter) or not.

[0075] At step 212, when the result of the determined first deviation exceeds/more than X meter, a deviation counter is started with 1 for the CPE (152a, 152b, 152c). By setting the deviation counter to a value 1, the system (102) marks the occurrence of a deviation that surpasses the defined threshold. The deviation counter acts as a quantitative indicator of the frequency of significant deviations for the CPE (152a, 152b, 152c) over time.

[0076] At step 214, steps 206 to 210 are repeated, and the deviation counter is incremented and monitored to determine if the deviation counter reaches to a predetermined count (e.g. 3 counts) within “M” days (e.g., 21 days, 3 weeks) from the deviation counter start date.

[0077] At step 216, when the result of step 214 is assertive, the first set of geolocation data get replaced with a centroid of a set of geolocation data calculated at every N days and the deviation counter is reset to 0.

[0078] At step 218, when the result of step 214 is not assertive, the deviation counter is reset to 0.

[0079] At step 219, after the deviation counter is reset to 0, a distance of the CPE (152a, 152b, 152c) to a nearest building is identified and the CPE (152a, 152b, 152c) is tagged to the nearest building reference ID.

[0080] At step 220, after performing step 216, it is checked if a second deviation between the replaced set of geolocation data and a centroid of a set of geolocation data calculated at another N days is more than ‘Y’ meter (e.g., 500 meters) AND step 214 get executed, the CPE (152a, 152b, 152c) is marked as relocated. In an embodiment, the previously stored set of geolocation data (replaced set of geolocation data) is further replaced with the centroid of the set of geolocation data calculated at another N days.

[0081] At step 222, step 204 get repeated and for the relocated CPE (152a, 152b, 152c) previous set of geolocation data and a deviation distance between the previous and current locations of the CPE (152a, 152b, 152c) is maintained. In an embodiment, the system (102) maintains detailed records for the CPE (152a, 152b, 152c) identified as “relocated” in the previous steps. Specifically, for the CPE (152a, 152b, 152c) marked with a “Yes” under details “Relocation”, the system (102) stores additional information in dedicated details:

[0082] “Pre Lat” details: These details capture the latitude coordinates of the CPE (152a, 152b, 152c) previous location before the relocation event.

[0083] “Pre-Long” details: Similar to “Pre Lat,” these details record the longitude coordinates of the CPE (152a, 152b, 152c) previous location.

[0084] “Relocation Distance” details: These details quantify the deviation or the extent of the relocation. It stores the determines distance between the previous and current locations of the CPE (152a, 152b, 152c).

[0085] By maintaining the historical data, the system provides a comprehensive record relocation event of the CPE (152a, 152b, 152c). The “Pre Lat” and “Pre-Long” details offer insight into the specific geographic coordinates of previous position of the CPE (152a, 152b, 152c). Simultaneously, the “Relocation Distance” details quantify the spatial shift, providing a numerical measure of how far the CPE (152a, 152b, 152c) may have moved. Further, this process helps in calculating the total number of relocated CPEs, ensuring accurate tracking and optimizing network performance.

[0086] FIG. 3 illustrates an exemplary computer system (300) in which or with which embodiments of the present disclosure may be implemented.

[0087] As shown in FIG. 3, the computer system (300) may include an external storage device (310), a bus (320), a main memory (330), a read-only memory (340), a mass storage device (350), a communication port (360), and a processor (370). A person skilled in the art will appreciate that the computer system (300) may include more than one processor (370) and communication ports (360). The processor (370) may include various modules associated with embodiments of the present disclosure.

[0088] In an embodiment, the communication port (360) may be any of an RS-232 port for use with a modem-based dialup connection, a 10/100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fibre, a serial port, a parallel port, or other existing or future ports. The communication port (360) may be chosen depending on the network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system (300) connects.

[0089] In an embodiment, the memory (330) may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. Read-only memory (340) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input/Output System (BIOS) instructions for the processor (370).

[0090] In an embodiment, the mass storage (350) may be any current or future mass storage solution, which may be used to store information and/or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and/or Firewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks (e.g., SATA arrays).

[0091] In an embodiment, the bus (320) communicatively couples the processor(s) (370) with the other memory, storage, and communication blocks. The bus (320) may be, e.g., a Peripheral Component Interconnect (PCI)/PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB) or the like, for connecting expansion cards, drives and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (370) to the computer system (300). [0092] Optionally, operator and administrative interfaces, e.g., a display, keyboard, joystick, and cursor control device, may also be coupled to the bus (320) to support direct operator interaction with the computer system (300). Other operator and administrative interfaces may be provided through network connections connected through the communication port (360). The components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system (300) limit the scope of the present disclosure.

[0093] FIG. 4 illustrates another exemplary flow diagram of the method (400) for identifying the relocated CPE (152a, 152b, 152c) in the network (104), in accordance with an embodiment of the present disclosure.

[0094] At step 402, the method includes obtaining, by the receiving unit (160), current geolocation data of the CPE (152a, 152b, 152c) (second set of geolocation data). In an embodiment, the receiving unit is configured to receive the geolocation data (latitude and longitude coordinates) of the CPE (152a, 152b, 152c) received by the via the trace data report. In an embodiment, the CPE may be configured to send the trace data report periodically or upon request to the receiving unit. In an embodiment, the geolocation data of the CPE (152a, 152b, 152c) received by the via the trace data report may be referred to as first set of geolocation data of the CPE (152a, 152b, 152c). In an embodiment, for every “N” days (e.g. 7 days) the step of obtaining is repeated to determine the second set of geolocation data associated with the CPE (152a, 152b, 152c). In an embodiment, first set of geolocation data of the CPE (152a, 152b, 152c) may get stored in a database (for example, the data storage module (164)). This step ensures that the location of the CPE (152a, 152b, 152c) is recorded for further analysis. In an embodiment, the method includes, identifying, by a processing unit (162), a nearest building for the CPE (152a, 152b, 152c) based on the stored geolocation data, and tagging the CPE (152a, 152b, 152c) with a unique identifier of the nearest building. The nearest building is identified using a unique building identifier, building name, and building coordinates. To achieve this, the processing unit (162) first draws a polygon around the coordinates from the first set of obtained geolocation data, effectively outlining the geographical area surrounding the CPE (152a, 152b, 152c). The polygon encapsulates the region within which various buildings and infrastructure are located. Further, the processing unit (162) identifies and compiles a list of buildings that lie within or near this polygonal boundary. Following this, the processing unit (162) calculates the distances between the CPE (152a, 152b, 152c) and each building on the list. The building with the shortest distance to the CPE (152a, 152b, 152c) is then selected as the nearest building (infrastructure).

[0095] At step 404, the method includes determining, by the processing unit (162), a first deviation in location of the CPE (152a, 152b, 152c) by comparing the current geolocation data with the stored geolocation data of the CPE (152a, 152b, 152c).

[0096] At step 406, the method includes incrementing, by the processing unit (162), a deviation counter if the determined first deviation exceeds a predefined threshold of X meter (e.g., 10 meter). The deviation counter acts as a quantitative indicator of the frequency of significant deviations for the CPE (152a, 152b, 152c) over time. In an embodiment, when the result of the determined first deviation exceeds/more than X meter, the deviation counter is started with 1 for the CPE (152a, 152b, 152c). In an embodiment, the method includes repeating, by the processing unit (162), steps of the obtaining (step 402) and the determining (step 404) over a predefined period (e.g., 3 weeks).

[0097] At step 408, the method includes replacing, by the processing unit (162), the stored geolocation data with a centroid of geolocation data obtained over a predefined period when the deviation counter reaches a predefined count within the predefined period. In an embodiment, the deviation counter is incremented and monitored to determine if the deviation counter reaches to a predetermined count (e.g. 3 counts) within “M” days (e.g., 21 days, 3 weeks) from the deviation counter start date. In an embodiment, the method includes resetting, by the processing unit (162), the deviation counter to zero upon replacing the stored geolocation data. In an embodiment, the method includes repeating, by the processing unit (162), steps of the obtaining (step 402) and the determining (step 404) over the predefined period to obtain another set of geolocation data of the CPE (152a, 152b, 152c). In an embodiment, the method includes resetting the deviation counter to zero if the deviation counter does not reach the predefined count within the predefined period. In an embodiment, after the deviation counter is reset to 0, a distance of the CPE (152a, 152b, 152c) to a nearest building is identified and the CPE (152a, 152b, 152c) is tagged to the nearest building reference ID.

[0098] At step 410, the method includes determining, by the processing unit (162), a second deviation between the replaced geolocation data with a centroid of geolocation data obtained over the predefined period.

[0099] At step 412, the method includes marking, by the processing unit (162), the CPE (152a, 152b, 152c) as relocated if the determined second deviation exceeds a second predefined threshold, and the deviation counter reaches the predefined count within the predefined period. In an embodiment, the second predefined threshold is greater than the predefined threshold. In an embodiment, the predefined threshold and the second predefined threshold are configurable values. In an embodiment, it is checked if a second deviation between the replaced set of geolocation data and a centroid of a set of geolocation data calculated at another N days is more than ‘Y’ meter (e.g., 500 meters) AND deviation counter reaches to a predetermined count (e.g. 3 counts) within “M” days (e.g., 21 days, 3 weeks) from the deviation counter start date, the CPE (152a, 152b, 152c) is marked as relocated. In an embodiment, the previously stored set of geolocation data (replaced set of geolocation data) is further replaced with the centroid of the set of geolocation data calculated at another N days. In an embodiment, the method includes maintaining records of the geolocation data and deviation distance for the CPE (152a, 152b, 152c). In an embodiment, the records of the geolocation data and the deviation distance include latitude and longitude coordinates of the CPE (152a, 152b, 152c) and the determined second deviation. These records include precise latitude and longitude coordinates of the CPE and the determined second deviation distance from its original position. By meticulously tracking and documenting the geolocation data, the system ensures accurate and up-to-date information about the CPE location. This comprehensive tracking mechanism provides numerous advantages, such as facilitating swift identification and resolution of any issues that may arise due to relocation. Additionally, it enhances the ability to analyze movement patterns and predict future requirements for network adjustments. Overall, maintaining these detailed records streamlines the management of network resources, reduces the likelihood of errors, and improves the reliability and performance of the network infrastructure.

[00100] In another exemplary embodiment, the present invention discloses a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for identifying a relocated Customer Premises Equipment (CPE) in a network. The method comprising determining, by a processing unit, a first deviation in location of the CPE by comparing the current geolocation data with stored geolocation data of the CPE. The method comprising incrementing, by the processing unit, a deviation counter if the determined first deviation exceeds a predefined threshold. The method comprising replacing, by the processing unit, the stored geolocation data with a centroid of geolocation data obtained over a predefined period when the deviation counter reaches a predefined count within the predefined period. The method comprising determining, by the processing unit, a second deviation between the replaced geolocation data with a centroid of geolocation data obtained over the predefined period. The method comprising marking, by the processing unit, the CPE as relocated if the determined second deviation exceeds a second predefined threshold, and the deviation counter reaches the predefined count within the predefined period.

[00101] The present disclosure introduces significant technical advancements that enhance the functionality and reliability of identifying a relocated CPE in a network. The present disclosure enables the accurate storage of geolocation data of CPE and incorporates a sophisticated mechanism to identify the nearest building for the CPE based on measured distances. The capability of the present disclosure addresses the current lack of an automated system for accurately tracking and identifying the relocation of the CPE, providing a solution that enhances network management and optimization. Furthermore, the present disclosure applies to various types of network environments, improving the overall efficiency and effectiveness of network operations. By periodically repeating the steps of storing geolocation data and identifying the nearest building, and by determining deviations of location of the CPE, the present disclosure ensures continuous and up-to-date tracking of device movements.

[00102] Through the present disclosure, geolocation data and deviation information for the CPE may be utilized to create a comprehensive database, for example, data storage module, offering valuable insights for network planning, optimization, and troubleshooting. The present disclosure thus significantly improves the management and tracking of CPE, leading to enhanced network performance and reliability. By maintaining detailed records of previous geolocation data and deviation distances, the present disclosure provides a robust framework for analyzing device movements and ensuring optimal network configuration.

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

[00104] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be implemented merely as illustrative of the disclosure and not as a limitation.

ADVANTAGES OF THE PRESENT DISCLOSURE

[00105] The present disclosure introduces an automated approach to identify and track the relocation of CPE, eliminating the need for manual tracking. This significantly reduces the workload on network administrators and minimizes the chances of human error.

[00106] The present disclosure provides a system and a method for improving accuracy in identifying genuine relocations of the CPE. The accuracy contributes to more precise network management, planning, and resource allocation.

[00107] The present disclosure provides a system and a method that tags the CPE with its closest building within the network infrastructure. This ensures precise placement and tracking of the CPE, enabling more efficient management and maintenance of network resources. By accurately tagging the CPE to its nearest buildings before relocation and after the relocation of the CPE, network administrators can quickly locate and address any issues, thus enhancing overall network reliability and performance.

[00108] The present disclosure provides a system and a method for periodic geolocation updates and continuous tracking to provide real-time information about the location of CPE. This is crucial for maintaining an up-to-date network topology map and making prompt decisions based on the latest data.

[00109] The present disclosure provides the system and the method that reduces the manual effort required for tracking and updating location of CPE. This reduction in operational overhead contributes to cost savings for network management.

Claims

1. A method (400) for identifying a relocated Customer Premises Equipment (CPE) (152a, 152b, 152c) in a network (104), the method (400) comprising: obtaining (402), by a receiving unit (160), current geolocation data of the CPE (152a, 152b, 152c); determining (404), by a processing unit (162), a first deviation in location of the CPE (152a, 152b, 152c) by comparing the current geolocation data with stored geolocation data of the CPE (152a, 152b, 152c); incrementing (406), by the processing unit (162), a deviation counter if the determined first deviation exceeds a predefined threshold; replacing (408), by the processing unit (162), the stored geolocation data with a centroid of geolocation data obtained over a predefined period when the deviation counter reaches a predefined count within the predefined period; determining (410), by the processing unit (162), a second deviation between the replaced geolocation data with a centroid of geolocation data obtained over the predefined period; and marking (412), by the processing unit (162), the CPE (152a, 152b, 152c) as relocated if the determined second deviation exceeds a second predefined threshold and the deviation counter reaches the predefined count within the predefined period.

2. The method (400) of claim 1, further comprising identifying, by the processing unit (162), a nearest building for the CPE (152a, 152b, 152c) based on the stored geolocation data, and tagging the CPE (152a, 152b, 152c) with a unique identifier of the nearest building, wherein the nearest building is identified using a unique building identifier, building name, and building coordinates.

3. The method (400) of claim 1, wherein the second predefined threshold is greater than the predefined threshold, wherein the predefined threshold and the second predefined threshold are configurable values.

4. The method (400) of claim 1, further comprising resetting the deviation counter to zero if the deviation counter does not reach the predefined count within the predefined period.

5. The method (400) of claim 1, further comprising maintaining records of the geolocation data and deviation distance for the CPE (152a, 152b, 152c).

6. The method (400) of claim 5, wherein the records of the geolocation data and the deviation distance comprising latitude and longitude coordinates of the CPE (152a, 152b, 152c) and the determined second deviation respectively.

7. A system (102) for identifying a relocated Customer Premises Equipment (CPE) (152a, 152b, 152c) in a network (104), the system (102) comprises: a receiving unit (160) configured to obtain current geolocation data of the CPE (152a, 152b, 152c); and a processing unit (162) coupled with the receiving unit, wherein the processing unit (162) is configured to: determine (408) a first deviation in location of the CPE (152a, 152b, 152c) by comparing the current geolocation data with stored geolocation data of the CPE (152a, 152b, 152c); increment a deviation counter if the determined first deviation exceeds a predefined threshold; replace the stored geolocation data with a centroid of geolocation data obtained over a predefined period when the deviation counter reaches a predefined count within the predefined period; determine a second deviation between the replaced geolocation data with a centroid of geolocation data obtained over the predefined period; and mark the CPE (152a, 152b, 152c) as relocated if the determined second deviation exceeds a second predefined threshold and the deviation counter reaches the predefined count within the predefined period.

8. The system (102) of claim 7, wherein the processing unit (162) is configured to: identify a nearest building for the CPE (152a, 152b, 152c) based on the stored geolocation data; and tag the CPE (152a, 152b, 152c) with a unique identifier of the nearest building, wherein the nearest building is identified using a unique building identifier, building name, and building coordinates.

9. The system (102) of claim 7, wherein the second predefined threshold is greater than the predefined threshold, wherein the predefined threshold and the second predefined threshold are configurable values.

10. The system (102) of claim 7, wherein the processing unit (162) is configured to reset the deviation counter to zero if the deviation counter does not reach the predefined count within the predefined period.

11. The system (102) of claim 7, wherein the data storage module (164) is further configured to maintain records of the geolocation data and deviation distance for the CPE (152a, 152b, 152c).

12. The system (102) of claim 11, wherein the records of the geolocation data and the deviation distance comprising latitude and longitude coordinates of the CPE (152a, 152b, 152c) and the determined second deviation respectively.

13. A computer program product comprising a non-transitory computer- readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method (400) for identifying a relocated Customer Premises Equipment (CPE) (152a, 152b, 152c) in a network (104), the method (400) comprising: obtaining (402), by a receiving unit (160), current geolocation data of the CPE (152a, 152b, 152c); determining (404), by a processing unit (162), a first deviation in location of the CPE (152a, 152b, 152c) by comparing the current geolocation data with stored geolocation data of the CPE (152a, 152b, 152c); incrementing (406), by the processing unit (162), a deviation counter if the determined first deviation exceeds a predefined threshold; replacing (408), by the processing unit (162), the stored geolocation data with a centroid of geolocation data obtained over a predefined period when the deviation counter reaches a predefined count within the predefined period; determining (410), by the processing unit (162), a second deviation between the replaced geolocation data with a centroid of geolocation data obtained over the predefined period; and marking (412), by the processing unit (162), the CPE (152a, 152b, 152c) as relocated if the determined second deviation exceeds a second predefined threshold and the deviation counter reaches the predefined count within the predefined period.