System and method for verifying a location of a device provisioned in a communication network

Abstract

Disclosed is a system and a method for verifying a location of a device provisioned in a communication network (100). The method comprises receiving a request for verification of the location from a Location Services (LCS) client (240). Upon receiving the request, identification information corresponding to the device is acquired via a first service module (408-5). The first service module (408-5) determines based on the identification information, whether the device is a Customer Premise Equipment (CPE) or a device different from the CPE. Upon the determination that the device is the CPE, the received request is re-routed from the first service module (408-5) to a second service module (408-6). The second service module (408-6) determines a change in a location of the CPE based on a comparison between the location information of the CPE acquired from a LMF node and the location information of the CPE stored in a database.

Description

SYSTEM AND METHOD FOR VERIFYING A LOCATION OF A DEVICE PROVISIONED IN A COMMUNICATION NETWORKCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of Indian patent application No. 202421065845, titled “User Interface framework based system for tracking and monitoring ODCPE devices in communication networks” filed on August 30, 2024. The disclosure of the prior application is considered part of and is incorporated by reference into this patent application.TECHNICAL FIELD

[0002] 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 verifying a location of a device provisioned in a communication network.BACKGROUND OF THE INVENTION

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

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

[0005] In modern telecommunications networks, efficient provisioning of network components is essential for maintaining optimal performance and reducing network overhead. Currently available provisioning methods involve numerous transactions for provisioning the network components which leads to increased network congestion, higher latency, and reduced overall efficiency.

[0006] Thus, efficiency and accuracy of location-based services are crucial for maintaining optimal network performance. To this end, for adopting network resources and services to evolving requirements, dynamic needs of location change requests need to be addressed. Heretofore, conventional methods for managing location changes of network elements have not been successful since the same were not able to differentiate between location fetching / updating requests from Customer Premise Equipment (CPEs) and those from Fourth Generation / Fifth Generation (4G / 5G) network users. This leads to inefficiencies in processing location data, potentially compromising performance of networks and user experience.

[0007] Owing to lack of a mechanism in conventional systems / methods to distinguish between the types of the location fetching / updating requests, in scenarios where the CPEs are involved, suboptimal routing of location data results, since specific requirements of the CPEs differ from those of the traditional 4G / 5G users. For instance, the CPEs require specialized handling or routing to ensure that the location data is processed correctly and efficiently. In absence of the ability to identify and appropriately route these requests, the network experience enhanced latency, reduced accuracy in location-based services, and overall degraded performance of the network.

[0008] In light of the aforementioned challenges, there is a need for a solution that is capable of efficiently verifying positioning of the CPEs in a communication network.SUMMARY

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

[0010] In an embodiment, disclosed herein is a method for verifying a location of a device provisioned in a communication network. The method comprises receiving, by a transceiver module in a Gateway Mobile Location Centre (GMLC) node, a request from a Location Services (LCS) client for verification of a location of the device provisioned in the communication network. Further, the method comprises acquiring, by an acquisition module in the GMLC node upon receiving the request, identification information corresponding to the device from a database via a first service module in the GMLC node. Furthermore, the method comprises determining, by a processing module in the GMLC node using the first service module, whether the device is a Customer Premise Equipment (CPE) or a device different from the CPE based on the identification information. Thereafter, the method comprises re-routing, by a routing module in the GMLC node via the first service module, the received request to a second service module in the GMLC node upon a determination that the device is the CPE.

[0011] In one or more embodiments, the method further comprises acquiring, by the acquisition module from a Location Management Function (LMF) node using the second service module, location information of the CPE comprising a current location of the CPE. Thereafter, the method comprises determining, by the processing module using the second service module, a change in the location of the CPE based on a comparison between the location information of the CPE acquired from the LMF node and the location information of the CPE stored in the database.

[0012] In one or more embodiments, for acquiring the location information of the CPE via the second service module, the method comprises initiating, by theacquisition module, an Application Programming Interface (API) request to the second service module.

[0013] In one or more embodiments, the method further comprises transmitting, by the transceiver module via the second service module, a message indicating the verification of the change in the location of the CPE to a display interface of a user device. The message is transmitted to the display interface based on the determined change in the location of the CPE.

[0014] In one or more embodiments, the method further comprises generating, by a processing module in the GMLC node, a notification including the message and information related to the current location of the CPE based on a reception of the message from the second service module. The transceiver module is configured to transmit the notification to the display interface.

[0015] In one or more embodiments, the method further comprises transmitting, by the transceiver module using the second service module, a message indicating the verification of the change in the location of the CPE to a Fulfilment Management System (FMS). The message is transmitted to the FMS based on the determined change in the location of the CPE.

[0016] In one or more embodiments, the location information comprises longitude and latitude coordinates of a site of installation of the CPE. The identification information comprises subscription data corresponding to the device. The subscription data includes a Subscriber Permanent Identifier (SUPI) of the device. The first service module is a Gateway Mobile Location Centre Location Element (GMLC-LE) and the second service module is a Gateway Mobile Location Centre Positioning Client (GMLC-PC).

[0017] In another embodiment, disclosed herein is a system for verifying a location of a device provisioned in a communication network. The system comprises a Location Services (LCS) client and a Gateway Mobile Location Centre (GMLC) node. The GMLC node comprises a transceiver module, an acquisition module, aprocessing module, and a routing module. The transceiver module is configured to receive a request from the LCS client for verification of a location of the device provisioned in the communication network. The acquisition module is configured to acquire via a first service module, from a database upon receiving the request, identification information corresponding to the device. The processing module is configured to determine using the first service module in the GMLC node, whether the device is a Customer Premise Equipment (CPE) or a device different from the CPE based on the identification information. The routing module is configured to re-route via the first service module, the received request to a second service module upon a determination that the device is the CPE.

[0018] In one or more embodiments, the acquisition module is configured to acquire, from a Location Management Function (LMF) node using the second service module, location information of the CPE comprising a current location of the CPE. Further, the processing module is configured to determine, using the second service module, a change in the location of the CPE based on a comparison between the location information of the CPE acquired from the LMF node and the location information of the CPE stored in the database.

[0019] In one or more embodiments, for acquiring the location information of the CPE via the second service module, the acquisition module is further configured to initiate an Application Programming Interface (API) request to the second service module.

[0020] In one or more embodiments, the transceiver module is further configured to transmit, via the second service module, based on the determined change in the location of the CPE, a message indicating the verification of the change in the location of the CPE to a display interface of a user device. The message is transmitted to the display interface based on the determined change in the location of the CPE.

[0021] In one or more embodiments, the system further comprises a processing module in the GMLC node configured to generate a notification including themessage and information related to the current location of the CPE based on a reception of the message from the second service module. The transceiver module is configured to transmit the notification to the display interface.

[0022] In one or more embodiments, the transceiver module is configured to transmit using the second service module, a message indicating the verification of the change in the location of the CPE to the FMS. The message is transmitted to the FMS based on the determined change in the location of the CPE.

[0023] In one or more embodiments, the location information comprises longitude and latitude coordinates of a site of installation of the CPE. The identification information comprises subscription data corresponding to the device. The subscription data includes a Subscriber Permanent Identifier (SUPI) of the device. The first service module is a Gateway Mobile Location Centre Location Element (GMLC-LE) and the second service module is a Gateway Mobile Location Centre Positioning Client (GMLC-PC).BRIEF DESCRIPTION OF DRAWINGS

[0024] Various embodiments disclosed herein will become better understood from the following detailed description when read with the accompanying drawings. The accompanying drawings constitute a part of the present disclosure and illustrate certain non-limiting embodiments of inventive concepts. Further, components and elements shown in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. For the purpose of consistency and ease of understanding, similar components and elements are annotated by reference numerals in the exemplary drawings.

[0025] FIG. 1 illustrates a block diagram of an example communication environment of a core network, in accordance with an embodiment of the present disclosure.

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

[0027] FIG. 3 illustrates a block diagram depicting an architecture of a communication system for verifying location of a device provisioned in a communication network, in accordance with an embodiment of the present disclosure.

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

[0029] FIG. 5 illustrates a flowchart depicting a method for verifying the location of the device provisioned in the communication network, in accordance with an embodiment of the present disclosure.DETAILED DESCRIPTION OF THE INVENTION

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

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

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

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

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

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

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

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

[0038] An object of the present disclosure is to provide a system and a method for verifying a location of a device, such as an indoor or outdoor Customer Premise Equipment (CPE) provisioned in a communication network. Another object of the present disclosure is to provide a system and a method that facilitates enhanced network performance and reliability by accurately verifying the CPEs positioning through re-routing of location requests, ensuring that the communication network functions optimally and delivers expected performance. Another object of the present disclosure is to provide a system and a method for managing a monitoring process of the CPE status within a network management system.

[0039] Yet another object of the present disclosure is to provide a system and a method that can enable resource optimization and effective network managementutilizing a microservice i.e., a Gateway Mobile Location Centre Positioning Client (GMLC-PC) to quickly stop or suspend the monitoring process. Still another object of the present disclosure is to provide a system and a method that can reduce latency and provide uninterrupted network surveillance by ensuring that a location change detection is not solely reliant on periodic polling or scheduled tracking.

[0040] In order to facilitate an understanding of the disclosed invention, a number of terms are defined below.

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

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

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

[0044] 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 base station 104-1 through base station 104-N. Thecore network 102 is configured to facilitate a secured communication among the plurality of base stations (collectively referred to as the “base stations 104”, and individually referred to as the “base station 104”, hereinafter).

[0045] The term “base station 104” may refer to any component (or collection of components) configured to provide wireless access to a network. Examples of the base station 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 base stations 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 “base stations” and “gNBs” are used interchangeably in the present disclosure to refer to network infrastructure components that provide wireless access to remote terminals.

[0046] 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” and individually referred to as “network device 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, Customer Premise Equipment (CPE), an Outdoor Customer Premise Equipment (ODCPE), an Indoor Customer Premise Equipment (IDCPE), and the like. In some embodiments, the gNBs 104 may communicate with each other and with the network devices 106 using a communication technique, such as a 5th Generation 5G / New Radio (NR), Long Term Evolution (LTE), Long Term Evolution Advanced (LTE-A), Worldwide Interoperability for Microwave Access (WiMAX), Wireless Fidelity (Wi-Fi), or other wireless communication techniques.

[0047] Further, depending on the network connection type, the term “network device 106” may refer to any component such as “mobile station,” “subscriber station,” “remote terminal,” “wireless terminal,” “receiver terminal”. In a nonlimiting example, the “device” in this disclosure wirelessly accesses the nodes (i.e., gNB 104). In a non-limiting example, the CPE 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.

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

[0049] In one aspect, the core network 102 may establish a secured communication between the one or more UEs 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 UEs 108 associated with the same node 104.

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

[0051] 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 UE 108 via a network coupled with a server. The core network 102 may pertain to 5G service-based 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.

[0052] 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 base stations, CPEs, and UEs 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.

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

[0054] 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), aNetwork Slice Selection Function (NSSF) node 216 (alternatively referred to as NSSF 216), a Location Management Function (LMF) node 218 (alternatively referred to as LMF 218), a Session Management Function (SMF) node 220 (alternatively referred to as SMF 220), a Network Data Analytics Function (NWDAF) node 222 (alternatively referred to as NWDAF 222), a Charging Function-Protocol converter (CHF -PC) node 224 (alternatively referred to as CHF- PC 224), a Network Exposure Function (NEF) node 226 (alternatively referred to as NEF 226), a Signaling Transfer Point (STP) node 228 (alternatively referred to as STP 228), a Diameter Routing Agent (DRA) node 230 (alternatively referred to as DRA 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).

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

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

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

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

[0059] The UDM 210 may be a network element that is capable of maintaining subscription information for UE 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.

[0060] 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 UE 108. The NSSF 216 includes one or more devices that select network slice instances for the UE 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.

[0061] 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 location-based service platforms to ensure seamless mobility management and locationbased service provisioning for the subscribers.

[0062] 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 data notification, manage roaming functionality, and / or perform other types of control plane processes for managing user plane data.

[0063] 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. The CHF PC 224 resides at the edge of the 4G and 5G networks. The CHF-PC 224 acts as a protocol converter for interactions with the existing 4G network diameter protocol-based online charging system to convert an HTTP / 2 message received from the SMF 220 and the PCF 204 in 5G network, to diameter messages before forwarding them to the online charging system and vice versa. The CHF-PC 224 has a highly scalable cluster which supports conversion for credit control (Gy / N40) and spending limit information (Sy / N28) exchange.

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

[0065] The STP 228 may be a network element configured to route signaling messages based a destination point code in core network 102. Specifically, the STP 228 acts a router that relays network messages between signaling end points and other signal transfer points in the core network 102.

[0066] The DRA 230 may be a network element configured as a centralized diameter routing point, ensuring that diameter messages are directed to appropriate network elements (e.g., PCF 204, SMF 220, CHF-PC 224, BSF 232). The DRA 230 may further be configured for load balancing and ability to route traffic based on specific fields or policies, enhancing the efficiency of network operations.

[0067] The BSF 232 may be a network element that is capable of managing session bindings and subscriber contexts within the core network 102.

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

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

[0070] 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 ruleenforcement, 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.

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

[0072] FIG. 3 illustrates a block diagram depicting an architecture of a communication system 300 for verifying location of the device provisioned in the communication network, in accordance with an embodiment of the present invention. 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.

[0073] As shown in FIG. 3, the communication system 300 (alternatively referred to as “system 300”) includes the AMF node 202, the LMF node 218, the LCS client 240, a Customer Order Management (COM) system 310 (hereinafter also referred to as order care system 310”), a Fulfillment Management System (FMS) 320, the GLMC node 234, and a database 330.

[0074] The FMS 320 refers to a backend enterprise system responsible for managing provisioning, activation, and configuration workflows for devices and services within the communication network 100. In the context of location -based operations, the FMS 320 may process provisioning or deprovisioning requests and issue location monitoring or tracking requests for devices such as the network devices 106 or the UE 108 to the GMLC node 234.

[0075] 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 verification of location of the device provisioned in the communication network, for example, the network devices 106 or the UE 108, in the communication network 100. 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.

[0076] 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 340. The service module 340 stores the CPE information from the FMS 320 in the database 330. The FMS 320 thus completes the CPE provisioning in the communication network 100 through the service module 340 and other network elements.

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

[0078] The database 330 is configured to store the information related to the requests for verification of the location of the device such as the network devices 106 or the UE 108 from the LCS client 240 and the network components received from the FMS 320 including the CPE information. The database 330 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.

[0079] The GMLC node 234 may utilize one or more service modules 340-1 to 340- n (collectively referred to as “service modules 340”) hosting a plurality of microservices. For example, a first service module 340-1 among the one or more service modules 340-1 to 340-n may include a first microservice for receiving location requests from the FMS 320 and detecting the change in location of the CPE provisioned in the communication network 100. The first service module 340-1 corresponds to an Positioning Client (PC) module. The first microservice is a GMLC Positioning Client (GMLC-PC) microservice. A second service module 340-2 among the one or more service modules 340-1 to 340-n may include a second microservice for receiving location requests from various LCS clients 240 in the communication network 100. The second service module 340-2 corresponds to a GMLC Location Element (GMLC-LE) module. The second microservice is a GMLC Location Element (GMLC-LE) microservice. The one or more service modules 340 are communicatively coupled with each other and are integrated with each other.

[0080] The microservices are 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 microservices may adhere to a well-defined API. The one or more service modules 340-1 to 340-n are communicatively coupled with the AMF 202 and the LMF 218 via NLt and NLs interfaces within the core network 102. NLt is an interface between the GMLC node 234 and the LMF node 218 for communication of location services control plane messages between the GMLC node 234 and the LMF node 218. NLs is an interface between the LMF node 218 and the AMF node 202 for transport for positioning protocol messages.

[0081] The GMLC-PC microservice is responsible for handling incoming requests for verification of location of the device such as the network devices 106 or the UE 108 from external systems such as the FMS 320 and initiate internal processing of such requests for detecting location changes of the device. When a requestcorresponding to verification of location information of the device provisioned in the communication network 100 is received at the GMLC node 234 from the FMS 320, the first service module 340-1 starts monitoring the location of the CPE on a periodic basis. When a location change is detected, the GMLC-PC microservice notifies the FMS 320 accordingly. The GMLC-PC microservice also communicates with the GMLC-LE microservice to handle location requests that do not originate from FMS 320 and perform the location change detection. Additionally, GMLC-PC microservice handles Create, Read, Update, and Delete (CRUD) operations for the provisioning of the device in the communication network 100, including creation, update, retrieval, and deletion of CPE configuration data.

[0082] The GMLC-LE microservice is responsible for validating and managing incoming location requests from various clients such as the LCS client 240 and coordinating with other service modules 340 for location determination and reporting. The GMLC-LE microservice validates the clients such as the LCS client 240 requesting for verification of the location of the device, checks whether the device is the CPE or the UE 108, and retrieves the location of the device. When the GMLC-LE microservice identifies the device 106 as the CPE, the request for verification of the location of the device 106 i.e. the CPE is forwarded to the GMLC- PC microservice.

[0083] The LCS clients 240 are entities that request location information of the device i.e. the network devices 106 or the UE 108 from the GMLC node 234. The LCS clients 240 may have different purposes, such as emergency services, commercial applications, or legal interception. In an embodiment, the LCS client 240 such as a Lawful Intercept Management (LIM) client is responsible for initiating and managing location-based requests for lawful interception purposes. The LIM client may interact with the GMLC node 234 to obtain the location of the device including the network devices 106 or the UE 108 as mandated by regulatory or legal authorities.

[0084] Once the provisioning of the CPE is completed in the communication network 100 by the FMS 320, the GMLC node 234 is configured to receive requests from the LCS client 240 for verifying the location of the device provisioned in the communication network 100.

[0085] Upon receiving the request, the GMLC node 234 is configured to acquire an identification information corresponding to the device from the database 330 via the first service module 340-1. The identification information may include subscription data including the SUPI of the device provisioned in the database 330. The first service module 340-1 determines, based on the information, whether the device is the CPE or a device different from the CPE. The GMLC node 234 is further configured to determine whether the request is for the CPE i.e., a CPE positioning request, for the UE 108 or for any other device. Further, the GMLC node 234 reroutes the request to the second service module 340-2 based on a determination that the device is the CPE, and the request is for verifying location of the CPE.

[0086] Thereafter, the first service module 340-1 is configured to re-route the request to the second service module 340-2. The second service module 340-2 is configured to fetch from the LMF 218, a current location of the CPE. Further, the second service module 340-2 is configured to determine a difference (delta) between the current location of the CPE and a provisioned location of the CPE. Furthermore, the second service module 340-2 is configured to transmit, to the FMS 320, a notification message indicating a change in a location of the CPE and the information related to the changed location of the CPE. The notification message may also indicate to a network operator that the functionality of the CPE should be suspended (CPE deregistration) based on the determination that there is a difference between the current location and the provisioned location.

[0087] FIG. 4 illustrates a block diagram depicting a system architecture 400 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, andFIG. 4 does not limit the scope of the present disclosure to any particular implementation of the GMLC node 234.

[0088] 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, and a plurality of module(s) 408 (hereinafter interchangeably referred to as “module(s) 408”). Components of the GMLC 234 are communicatively coupled to each other via a communication bus 410.

[0089] 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, and the modules 408 via the communication bus 410. Examples of the communication bus 410 may include, but are not limited to, a Peripheral Component Interconnect (PCI) / PCI Extended (PCLX) 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 other subsystems of the GMLC 234, as the communication bus 410, without deviating from the scope of the present disclosure.

[0090] 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 node 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.

[0091] The processor 402 may include one or a plurality of processors, including a general-purpose processor, such as, for example, and without limitation, a CentralProcessing 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.

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

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

[0094] In one or more embodiments, the module(s) 408 may include one or more modules such as a transceiver module 408-1, an acquisition module 408-2, a processing module 408-3, a routing module 408-4, a first service module 408-5 (same as the first service module 340-1), and a second service module 408-6 (sameas the second service module 340-2). Each of the module(s) 408 is communicatively coupled with each other.

[0095] In an aspect, the processor 402, via the transceiver module 408-1, is configured to receive the request from the LCS client 240 for verification of the location of the device provisioned in the communication network 100. Upon receiving the request, the acquisition module 408-2 is configured to acquire the identification information corresponding to the device from the database 330 for monitoring the location of the device. The identification information corresponding to the device includes one or more of the SUPI of the device, and the longitude and latitude coordinates of a site of installation of the device. The acquisition module 408-2, via the first service module 408-5, acquires the identification information corresponding to the device from the database 330 for verifying the location of the device.

[0096] The processor 402, via the processing module 408-3 using the first service module 408-5, is configured to determine whether the device is a CPE or a device different from the CPE based on the acquired identification information. Upon the determination that the device is the CPE, the processor 402, using the routing module 408-4 via the first service module 408-5, re-routes the request for verification of the location of the device to the second service module 408-6.

[0097] Upon receiving the request for verification of the location of the device by the second service module 408-6, the acquisition module 408-2 is configured to initiate an API request to the second service module 408-6. Upon receiving the API request, the acquisition module 408-2 using the second service module 408-6 is configured to acquire from the LMF node 218, the location information of the CPE comprising a current location of the CPE.

[0098] Further, the processing module 408-3, via the second service module 408-6 is configured to determine a change in the location of the CPE based on a comparison between the location information of the CPE acquired from the LMF node 218 and the location information of the CPE acquired from the database 330.

[0099] In an embodiment, when the change in location of the CPE is determined, the processor 402, using the transceiver module 408-1, is configured to transmit via the second service module 408-6, a message indicating the verification of the change in the location of the CPE to the FMS 320. The message includes the current location of the CPE. The message may also include a deprovisioning request to the FMS 320 to deprovision the CPE from the communication network 100 based on the determined change in the location of the CPE. The message may also include a deprovisioning request to the FMS 320 to deprovision the CPE from the communication network 100 based on the determined change in the location of the CPE.

[0100] In another embodiment, when the change in location of the CPE is determined, the processor 402, using the transceiver module 408-1, is configured to transmit via the second service module 408-6, the message indicating the verification of the change in the location of the CPE of a user device utilized by the network operator. The message includes the current location of the CPE. The user device may correspond to a network management console or a server-end device, including, but not limited to, a desktop computer, a portable computing device such as a laptop, a tablet computer, a handheld computer, a mobile phone, wearable computer, or any other device suitable to provide front end services. The front-end services may include a display interface (alternatively referred to as “front-end interface”) for accessing different functionalities of the system 300.

[0101] In an embodiment, the display interface may correspond to a Graphical User Interface (GUI) including an application or a software for displaying the message, based on the determined change in the location of the CPE. In another embodiment, the display interface may correspond to a web User Interface (UI) including a website or a web application for displaying the message and allowing the network operator to interact with it.

[0102] Further, the processing module 408-3 generates a notification including the message and information related to the current location of the CPE based on areception of the message from the second service module 408-6. The transceiver module 408-1 is configured to transmit the notification to the GUI or the web UI. The notification may correspond to a pop-up message, an email, or a report. The processing module 408-3 may control the display of the notification on the GUI or the web UI of the user device and provide interactive options to the network operator to track or control the CPE.

[0103] The user device may further include a communication unit for communicating with the GMLC node 234. The communication unit may include a plurality of antennas, a plurality of Radio Frequency (RF) transceivers, a transmit processing circuitry, and a receive processing circuitry. The communication unit may allow the user device to receive from the GMEC node 234, visualization data including the message or the notification corresponding to the CPE.

[0104] The transceiver module 408-1 may receive incoming Radio Frequency (RF) signals, such as signals transmitted by the base stations 104 and the UE 108 in the communication network. The reception module 410-1 may down-convert the incoming RF signals to generate the IF or baseband signals which may be sent to the receiver processing circuitry. The transceiver module 408-1 may transmit the processed baseband signals to the processor 402 for further processing. The transceiver module 408-1 may receive analog or digital data from the processor 402 and may encode, multiplex, and / or digitize the outgoing baseband data to generate processed baseband or IF signals. The transceiver module 408-1 may further process the outgoing processed baseband or IF signals from the transmit processing circuitry and up-converts the baseband or IF signals to RF signals that may be transmitted to the UE 108 and the base stations 104.

[0105] Further, the processing module 408-3 may control the display interface for displaying various operations for viewing and managing a plurality of the CPEs. The processing module 408-3 may control the display interface to display data comprising the location information of the plurality of the CPEs and an operational status of the plurality of the CPEs i.e. activation status, deactivation status,provisioning status, or de-provisioning status to the network operator. The processing module 408-3 is configured to detect and verify changes in the operational status or the location of the CPE, generate and control the display of the notification on the display interface based on the changes in the operational status or the location of the CPE.

[0106] Furthermore, the processing module 408-3 may control the GUI or the web UI to display a user profile to the network operator. The network operator may login to the user profile by entering predefined user credentials over the GUI or the web UI. The network operator may be categorized into one of an administrator mode and a non-administrator mode, ensuring that access rights and system capabilities are aligned with roles of the network operator. The user profile accessed via the GUI or the web UI provides an interface to the network operator to track or control one or more CPEs among the plurality of CPEs as per the rights available to the network operator.

[0107] Based on the administrator mode and the non-administrator mode, the network operator may be provided different management rights for managing the plurality of the CPEs, such as, but not limited to, initiating a provisioning or deprovisioning request for the CPE, an activation or deactivation request for the CPE, location monitoring request. The network operator categorized into the administrator mode may be permitted to activate, deactivate, or reactivate the plurality of the CPEs, modify configuration settings to receive the notifications corresponding to any changes, and modify the data related to the plurality of the CPEs.

[0108] The network operator categorized into the non-administrator mode may be permitted to view a real-time status and the location of the plurality of the CPEs, and the notifications about the changes in the status or the location of the plurality of the CPEs. The network operator categorized into the non-administrator mode may monitor the plurality of the CPEs, view status updates, and receive the notifications corresponding to the plurality of the CPEs, without an ability to accessand modify the data related to the plurality of the CPEs, enable or disable features or settings corresponding to the plurality of the CPEs, and the like. For instance, once a location change notification is received at the GUI or the web UI, the network operator categorized in the non-admini strati ve mode may only be able to see the notification and may raise a concern to a respective network operation team or staff for the implementation of corrective actions.

[0109] Further, the first service module 408-5 and the second service module 408- 6 may host the plurality of microservices (or alternatively referred to as “microservices”). Among the microservices, the first microservice may correspond to the GMLC-LE microservice and the second microservice may correspond to the GMLC-PC microservice. The GMLC node 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.

[0110] 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 node 234, for example, GMLC-PC microservice could be responsible for acquiring the real-time information corresponding to the CPE from the LMF 218 and determine the change in the location of the device.

[0111] The GMLC-LE microservice could be responsible for receiving the request for verification of the location the LCS client 240. The GMLC-LE microservice also performs authentication and authorization of the received request. The GMLC-LE microservice is also configured to determine whether the device is the CPE by checking an internal subscriber profile repository of the device from the database 330 or querying the provisioning data maintained by the GMLC-PC microservice corresponding to the device in the database 330.

[0112] It must be understood that the microservices platform may also be hosted outside the GMLC node 234 in a similar manner utilizing the resources of a computing device separate from the GMLC node 234 itself. The module(s) 408 may make a call to the microservices for synchronization of flow of data between various components of the GMLC node 234 and performing other tasks within the system 300.

[0113] The memory 404 stores the set of instructions 404-1 required by the processor 402 for controlling its overall operations. 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 nonmovable. 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 Random Access Memory (RAM) or cache). The memory 404 may be an internal storage unit or an external storage unit of the GMLC node 234, cloud storage, or any other type of external storage.

[0114] The communication interface 406 may manage communications with the base stations or the network devices 106. For example, the communication interface 406 may manage the transfer of the status information of the CPE, the subscription data including the SUPI, and the location information corresponding to customer orders for verifying the location of the device 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.

[0115] Although FIG. 4 illustrates one example of GMLC node 234, various changes may be made to FIG. 4. For example, the GMLC node 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.

[0116] 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 514. Although method 500 shows example blocks of steps 502 to 514, 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- 514 may be combined or may be performed in parallel.

[0117] Once the CPE is provisioned in the communication network 100, the processor 402, via the transceiver module 408-1, at step 502, receives from the LCS client 240, the request for verification of the location of the device provisioned in the communication network 100.

[0118] Upon receiving the request, at step 504, the acquisition module 408-1 via the first service module 408-5, is configured to fetch from the database 330, the identification information corresponding to the device. The identification information comprises the subscription data corresponding to the device and the longitude and latitude coordinates of a site of installation of the device.

[0119] At step 506, the processor 402, via the processing module 408-3 using the first service module 408-5, is configured to determine whether the device is the CPE or a device different from the CPE, based on the received identification information. The device different from the CPE may include any other network user device provisioned in the communication network including a 4thgeneration (4G) device or a 5thgeneration (5G) device.

[0120] At step 508, upon the determination that the device is the CPE, the processor 402, using the routing module 408-4 via the GMLC-LE microservice of the firstservice module 408-5, re-routes the request for verification of the location of the device to the GMLC-PC microservice of the second service module 408-6. The request may be transmitted from the GMLC-LE microservice to the GMLC-PC microservice using an event-based request publication mechanism where the request may be stored for processing by the GMLC-PC microservice as logs.

[0121] At step 510, the acquisition module 408-2, using the second service module 408-6, is configured to acquire from the LMF node 218, the current location information of the device.

[0122] Further, at step 512, the processing module 408-3, via the GMLC-PC microservice, compares the location information of the provisioned CPE acquired from the database 330 and the current location acquired from the LMF 218. In one aspect, when the GMLC-PC microservice determines that the current location information acquired from the provisioned CPE matches with the location information of the provisioned CPE stored in the database 330, the GMLC-PC microservice detects that there is no change in the location of the CPE. Upon detecting that there is no change in the location of the device, the transceiver module 408-1 transmits via the second service module 408-6, a message to the FMS 320 indicating no change in the location of the CPE. The message indicating no change in the location of the CPE, may also be transmitted to the GUI or the web UI of the user device of the network operator via the transceiver module 408-1.

[0123] In another aspect, when the GMLC-PC microservice determines that the current location information acquired from the provisioned CPE does not match with the location information of the provisioned CPE stored in the database 330, the GMLC-PC microservice detects the change in the location of the CPE.

[0124] The GMLC-PC microservice is configured to detect the change in the location when there is a mismatch in the location information of the provisioned CPE, outside of the 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 bedependent on a configuration of a Global Positioning System (GPS) sensor installed in the CPE.

[0125] At step 514, upon detecting the change in the location of the provisioned CPE, the transceiver module 408-1 is further configured to transmit, via the second service module 408-6, based on the determined change in the location of the CPE, the message indicating the verification of the change in the location of the CPE to the GUI or the web UI of the user device of the network operator.

[0126] In another embodiment, the message is also transmitted to the FMS 320, based on the determined change in the location of the CPE. The message transmitted to the FMS 320 may indicate the verification of the change in the location of the CPE and may also include the current location of the CPE. Based on the message, the network operator may initiate a request, from the FMS 320 to suspended or deregister the CPE based on a determination that there is a difference between the current location and the provisioned location. The FMS 320 may deprovision the CPE and update the status information of the ODCPE in a Unified Data Management (UDM) profile of the CPE as “deactivated or deregistered”.

[0127] Now, referring to the technical abilities and advantageous effect of the present disclosure, the embodiments disclosed herein provide a system and a method that integrates a plurality of microservice to efficiently verifying the location of the device provisioned in the communication network 100. Another noteworthy advantage of the one or more embodiments of the present disclosure includes but not limited thereto, facilitating enhanced network performance and reliability by accurately verifying the CPEs positioning through re-routing of location requests, ensuring that the communication network functions optimally and delivers expected performance. The disclosed system and the method ensure that the location change detection is not solely reliant on periodic polling or scheduled tracking of the device to be performed by the GLMC-PC microservice, thereby reducing latency in location change detection of the device.

[0128] Yet another noteworthy advantage of the one or more embodiments of the present disclosure includes that the disclosed system and the method ensures that location detection for the CPEs is performed on every incoming request, regardless of whether the CPE is part of scheduled tracking configured to be performed by the GMLC-PC microservice. Any request involving the verification of the location of the device, triggers an immediate location check to be performed by the plurality of microservices, ensuring the most current location information corresponding to the CPE is used.

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

[0130] 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 direct a 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).

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

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

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

[0134] 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

[0135] 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 Equipment (UE)202 - Access and Mobility Management Function (AMF) node204 - Policy Control Function (PCF) node206 - Equipment Identity Register (EIR) node208 - Authentication Server Function (AUSF) node210 - Unified Data Management (UDM) function node212 - Subscriber Profile Repository (SPR) node214 - Short Message Service Function (SMSF) node216 - Network Slice Selection Function (NSSF) node218 - Location Management Function (LMF) node220 - Session Management Function (SMF) node222 - Network Data Analytics Function (NWDAF) node224 - Charging Function-Protocol Converter (CHF-PC) node226 - Network Exposure Function (NEF) node228 - Signaling Transfer Point (STP) node230 - Diameter Routing Agent (DRA) node232 - Binding Support Function (BSF) node234 - Gateway Mobile Location Center (GMLC) node238 - User Plane Function (UPF) node240 - Location Services (LCS) client node300 - Communication system310 - Customer Order Management (COM) system320 - Fulfillment Management System (FMS)330 - Database340 - Service modules340-1 - First Service Module340-2 - Second Service Module402 - Processor(s)404 - Memory406 - Communication interface408 - Module(s)408-1 - Transceiver Module408-2 - Acquisition Module408-3 - Processing Module408-4 - Routing Module408-5 - First Service Module408-6 - Second Service Module410 - Communication bus500 - Method for verifying a location of a device provisioned in a communication network502-514 - Operational steps of method 500

Claims

WE CLAIM:

1. A method (500) for verifying a location of a device provisioned in a communication network (100), the method comprising: receiving, by a transceiver module (408-1) in a Gateway Mobile Location Centre (GMLC) node (234), a request from a Location Services (LCS) client (240) for verification of a location of the device provisioned in the communication network (100); acquiring, by an acquisition module (408-2) in the GMLC node (234) upon receiving the request, identification information corresponding to the device from a database (330) via a first service module (408-5) in the GMLC node (234); determining, by a processing module (408-3) in the GMLC node (234) using the first service module (408-5), whether the device is a Customer Premise Equipment (CPE) or a device different from the CPE based on the identification information; and re-routing, by a routing module (408-4) in the GMLC node (234) via the first service module (408-5), the received request to a second service module (408-6) in the GMLC node (234) upon a determination that the device is the CPE.

2. The method (500) as claimed in claim 1, further comprising: acquiring, by the acquisition module (408-2) from a Location Management Function (LMF) node (218) using the second service module (408-6), location information of the CPE comprising a current location of the CPE; and determining, by the processing module (408-3) using the second service module (408-6), a change in the location of the CPE based on a comparison between the location information of the CPE acquired from the LMF node and the location information of the CPE stored in the database (330).

3. The method (500) as claimed in claim 2, wherein, for acquiring the location information of the CPE via the second service module (408-6), the method comprises initiating, by the acquisition module, an Application Programming Interface (API) request to the second service module.

4. The method (500) as claimed in claim 2, further comprising transmitting, by the transceiver module (408-1) via the second service module (408-6), a message indicating the verification of the change in the location of the CPE to a display interface of a user device, wherein the message is transmitted to the display interface based on the determined change in the location of the CPE.

5. The method (500) as claimed in claim 4, further comprising: generating, by the processing module in the GMLC node (234), a notification including the message and information related to the current location of the CPE based on a reception of the message from the second service module (408-6), and wherein the transceiver module (408-1) is configured to transmit the notification to the display interface.

6. The method (500) as claimed in claim 2, further comprising transmitting, by the transceiver module using the second service module (408-1), a message indicating the verification of the change in the location of the CPE to a Fulfilment Management System (FMS) (320), wherein the message is transmitted to the FMS (320) based on the determined change in the location of the CPE.

7. The method (500) as claimed in claim 1, wherein: the location information comprises longitude and latitude coordinates of a site of installation of the CPE, the identification information comprises subscription data corresponding to the device, the subscription data includes a Subscriber Permanent Identifier (SUPI) of the device, andthe first service module (408-5) is a Gateway Mobile Location Centre Location Element (GMLC-LE) and the second service module (408- 6) is a Gateway Mobile Location Centre Positioning Client (GMLC-PC).

8. A system (300) of verifying a location of a device provisioned in a communication network, the system (300) comprising: a Location Services (LCS) client (240); and a Gateway Mobile Location Centre (GMLC) node (234) comprising: a transceiver module (408-1) configured to receive a request from the LCS client for verification of a location of the device provisioned in the communication network (100); an acquisition module (408-2) configured to acquire via a first service module (408-5), from a database (330) upon receiving the request, identification information corresponding to the device; a processing module (408-3) configured to determine using the first service module (408-5) in the GMLC node, whether the device is a Customer Premise Equipment (CPE)- or a device different from the CPE based on the identification information; and a routing module (408-4) configured to re-route via the first service module (408-5), the received request to a second service module (408-6) upon a determination that the device is the CPE.

9. The system (300) as claimed in claim 8, wherein the acquisition module (408-2) is configured to acquire, from a Location Management Function (LMF) node (218) using the second service module, location information of the CPE comprising a current location of the CPE, and wherein the processing module (408-3) is configured to determine, using the second service module, a change in the location of the CPE based on a comparison between the location information of the CPE acquired from the LMF node (218) and the location information of the CPE stored in the database (330).

10. The system (300) as claimed in claim 9, wherein, for acquiring the location information of the CPE via the second service module (408-6), theacquisition module is further configured to initiate an Application Programming Interface (API) request to the second service module (408-6).

11. The system (300) as claimed in claim 9, wherein the transceiver module (408-1) is further configured to transmit, via the second service module (408-6), based on the determined change in the location of the CPE, a message indicating the verification of the change in the location of the CPE to a display interface of a user device, and wherein the message is transmitted to the display interface based on the determined change in the location of the CPE.

12. The system (300) as claimed in claim 11, wherein the processing module in the GMLC node (234) is configured to generate a notification including the message and information related to the current location of the CPE based on a reception of the message from the second service module (408-6), and wherein the transceiver module (408-1) is configured to transmit the notification to the display interface.

13. The system (300) as claimed in claim 9, wherein the transceiver module (408-1) is configured to transmit using the second service module (408-6), a message indicating the verification of the change in the location of the CPE to a Fulfilment Management System (FMS) (320), and wherein the message is transmitted to the FMS (320) based on the determined change in the location of the CPE.

14. The system (300) as claimed in claim 8, wherein: the location information comprises longitude and latitude coordinates of a site of installation of the CPE, the identification information comprises subscription data corresponding to the device, the subscription data includes a Subscriber Permanent Identifier (SUPI) of the device, andthe first service module (408-5) is a Gateway Mobile Location Centre Location Element (GMLC-LE) and the second service module (408- 6) is a Gateway Mobile Location Centre Positioning Client (GMLC-PC).

15. 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 from a Location Services (LCS) client, a request for verification of a location of a device provisioned in a communication network; acquiring, via a first service module in the GMLC node, identification information corresponding to the device from a database upon receiving the request; determining, using the first service module, whether the device is a Customer Premise Equipment (CPE) or a device different from the CPE based on the identification information; and re-routing, via the first service module, the received request to a second service module in the GMLC node upon a determination that the device is the CPE.

Images