DESC:FIELD OF INVENTION
[0001] The embodiments of the present disclosure generally relate to locating mobile devices. More particularly, the present disclosure relates to systems and methods for locating lost, stolen, and/or misplaced mobile devices using an Open Radio Access Network (O-RAN).

BACKGROUND OF THE INVENTION
[0002] 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 is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
[0003] In general, mobile computing devices may be an integral part of human life. Notebooks, netbooks, tablet computers, smartphones, and other portable devices comprise more than half of all computing devices produced worldwide. Users use mobile computing devices to communicate, work, relax, and study. The memory in these devices may store large amounts of personal and/or official data such as contacts, photographs, videos, authorization information, and more. Work-related mobile computing devices may also contain official correspondence and documentation, which may include trade secrets. These mobile computing devices may often be targets for theft or robbery. Further, mobile computing devices may be easily lost due to their size and the fact that they are constantly moved around by the user. Approximately, seventy million mobile devices are lost each year, out of which only about seven percent are recovered. The lost/stolen mobile devices may cause financial loss to the end user, and apart from the financial loss personal valuable information stored in the phone may also be lost along with mobile devices. In addition, if the mobile computing devices are misplaced, then the user may have to search manually, or the user may have to priorly attach additional device/tags to the mobile computing devices to find the misplaced mobile computing devices.
[0004] Currently, mobile technology permits mobile devices to be identified centrally by network operators. The conventional methods to find lost mobile devices may be tedious for an ordinary user of the mobile devices. To locate a mobile device, current solutions may involve multiple authorities and processes, and may also require human intervention. Hence, in most scenarios, it may be impossible to locate the lost/stolen mobile devices for a normal user. The network operators may provide services/applications to find lost mobile devices, however, if the Subscriber Identity Module (SIM) card in the mobile devices is changed or the application is removed or the mobile device is reset to factory settings, then it may not be possible to locate the lost mobile device. In addition, the conventional methods may not allow the user to locate the misplaced devices without priorly attaching additional device/tags to the mobile computing devices.
[0005] There is therefore a need in the art to provide a method and system that can overcome the shortcomings of the existing prior art.

OBJECTS OF THE PRESENT DISCLOSURE
[0006] Some of the objects of the present disclosure, which at least one embodiment herein satisfy are as listed herein below.
[0007] An object of the present disclosure is to provide efficient and reliable systems and methods for locating lost, stolen, and/or misplaced mobile devices using Open Radio Access Network (O-RAN).
[0008] An object of the present disclosure is to provide a portal where a user may subscribe and add identity details of the lost, stolen, and/or misplaced mobile devices for locating lost, stolen, and/or misplaced mobile devices using Open Radio Access Network (O-RAN).
[0009] An object of the present disclosure is to enable Open Radio Access Network (O-RAN) to locate/track the lost, stolen, and/or misplaced mobile devices using rApps/xApps, based on events in the lost, stolen, and/or misplaced mobile devices, or periodic events, or manually triggered events.
[0010] An object of the present disclosure is to provide a portal where the user of the lost, stolen, and/or misplaced mobile device may log in and locate the lost, stolen, and/or misplaced mobile device by himself/herself.
[0011] An object of the present disclosure is to provide an application where the user of the lost, stolen, and/or misplaced mobile device may log in and locate the lost, stolen, and/or misplaced mobile device by installing the application on any device.
[0012] An object of the present disclosure is to enable the lost, stolen, and/or misplaced mobile device to perform tasks/actions, after locating the lost, stolen, and/or misplaced mobile device.

SUMMARY
[0013] This section is provided to introduce certain objects and aspects of the present invention in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.In an aspect, the present disclosure provides a system for locating a device to be tracked. The system receives an information of the device to be tracked from a user. The information of the device to be tracked may be entered into an application on or a portal in the user device or the device to be tracked. The information of the device to be tracked may comprise an IMEI (International Mobile Equipment Identity) code of the device to be tracked. Further, the system sends a request for locating the device to be tracked based on the registered information. Further, the system registers the received information. The registration of the received information may create a credential entry of the device to be tracked for logging into an application on or a portal. Further, the system sends a request for locating the device to be tracked (102) based on the registered information. Further, the system transmits the request for locating the device to be tracked based on the registered information from a data acquisition engine to a data transfer engine via an E2 interface of an Open radio access network Distributed Unit (O-DU), an Open radio access network Central Unit Control Plane (O-CU-CP), and an Open radio access network Central Unit User Plane (O-CU-UP) of an Open Radio Access Network (O-RAN). Further, the system receives a response corresponding to the request sent for locating the device to be tracked. Further, the system triggers a data acquisition engine to execute the event in the device to be tracked. Further, the system triggers a data transfer engine to execute the event in the device to be tracked. Furthermore, the system transmits the response to the user device to locate the device to be tracked and outputs a location of the device to be tracked to the user device.
[0014] In an aspect, the present disclosure provides a method for locating a device to be tracked. The method includes receiving, an information of the device to be tracked from a user. The information of the device to be tracked may be entered into an application on or a portal. The information of the device to be tracked comprises an IMEI (International Mobile Equipment Identity) code of the device to be tracked. Further, the method includes registering, the received information. The registration of the received information creates a credential entry of the device to be tracked for logging into an application on or a portal. Further, the method includes sending, a request for locating the device to be tracked based on the registered information by triggering an event in the device to be tracked that comprises paging the device to be tracked, ringing the device to be tracked, clicking a photo by the device to be tracked, displaying a message in the device to be tracked, locking the device to be tracked, and resetting the device to be tracked for sending the request for locating the device to be tracked based on the registered information. Further, the method includes transmitting the request for locating the device to be tracked based on the registered information from a data acquisition engine to a data transfer engine via an E2 interface of an Open radio access network Distributed Unit (O-DU), an Open radio access network Central Unit Control Plane (O-CU-CP), and an Open radio access network Central Unit User Plane (O-CU-UP) of an Open Radio Access Network (O-RAN). Further, the method includes triggering a data acquisition engine to execute the event in the device to be tracked. Further, the method includes triggering a data transfer engine to execute the event in the device to be tracked. Further, the method includes receiving, a response corresponding to the request sent for locating the device to be tracked based on a periodic monitoring and a detection of an event occurring in the device to be tracked. Furthermore, the method includes transmitting, the response to the user device to locate the device to be tracked by outputting a location of the device to be tracked to the user.

BRIEF DESCRIPTION OF DRAWINGS
[0015] The accompanying drawings, which are incorporated herein, and constitute a part of this invention, illustrate exemplary embodiments of the disclosed methods and systems in 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 invention. 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 such drawings include the invention of electrical components, electronic components, or circuitry commonly used to implement such components.
[0016] FIG. 1 illustrates an exemplary network architecture (100) in which or with which proposed system of the present disclosure can be implemented, in accordance with an embodiment of the present disclosure.
[0017] FIG. 2 illustrates an exemplary representation (200) of proposed Service Management and Orchestration (SMO) system for locating lost, stolen, and/or misplaced mobile devices using an Open-RAN (O-RAN), in accordance with an embodiment of the present disclosure.
[0018] FIG. 3 illustrates an exemplary block diagram representation (300) of a system architecture, in accordance with an embodiment of the present disclosure.
[0019] FIG. 4A illustrates an exemplary flow chart (400a) depicting a method for registering the mobile device in a portal for locating the mobile device using an O-RAN, in accordance with an embodiment of the present disclosure.
[0020] FIG. 4B illustrates an exemplary flow chart (400b) depicting a method for locating the mobile devices, in accordance with an embodiment of the present disclosure.
[0021] FIG. 5 illustrates a sequence diagram representation (500) of registering the mobile device in a portal and locating the mobile device using an O-RAN architecture, in accordance with an embodiment of the present disclosure.
[0022] FIG. 6 illustrates an exemplary computer system (600) in which or with which embodiments of the present invention can be utilized, in accordance with embodiments of the present disclosure.
[0023] FIG. 7 illustrates an exemplary method flow chart (700) depicting a method for locating a device to be tracked (102) by a data acquisition engine (212), in accordance with an embodiment of the present disclosure.
[0024] The foregoing shall be more apparent from the following more detailed description of the invention.

DETAILED DESCRIPTION OF INVENTION
[0025] 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. 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.
[0026] 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 invention as set forth.
[0027] 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.
[0028] Also, it is noted that individual embodiments may be described as a process which 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.
[0029] 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—in a manner similar to the term “comprising” as an open transition word—without precluding any additional or other elements.
[0030] 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 invention. 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 particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
[0031] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting to the invention. 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 and all combinations of one or more of the associated listed items.
[0032] The present disclosure provides efficient and reliable systems and methods for locating lost, stolen, and/or misplaced mobile devices using an Open Radio Access Network (O-RAN). The systems and methods enable a user to locate and find lost, stolen, and/or misplaced mobile devices based on a user requirement, without involving any official authorities or assistance. In an embodiment, the systems and methods enable the O-RAN to locate/track the mobile devices using rApps/xApps, based on one or more non-periodic events in the mobile devices, periodic events, or manually triggered events. Since O-RAN is used for locating the mobile device, the mobile device may be located using an International Mobile Equipment Identity (IMEI) of the mobile device, even if the Subscriber Identity Module (SIM) is changed or the mobile is reset to factory settings. In an embodiment, the systems and methods provide a portal where the user of the lost, stolen, and/or misplaced mobile device may log in and locate the lost, stolen, and/or misplaced mobile device. The systems and methods may enable the lost, stolen, and/or misplaced mobile device to perform tasks/actions, after locating the lost, stolen, and/or misplaced mobile device. The actions may include, but not limited to, ringing, clicking a photo, displaying a message, finding location/paging, locking, erasing/resetting, and the like. The actions such as clicking a photo, displaying a message, and erasing/resetting may be performed via a dedicated application installed on the mobile device. When the mobile device is lost/stolen, resetting the mobile device may erase all the features in the mobile device including the dedicated application. However, locating or paging the mobile device may be performed using the IMEI, even if the dedicated application is removed/deleted.
[0033] Referring to FIG. 1 that illustrates an exemplary network architecture (100) in which or with which a Service Management and Orchestration (SMO) system (108) or simply referred to as the SMO system (108) of the present disclosure can be implemented, in accordance with an embodiment of the present disclosure. As illustrated, the exemplary network architecture (100) may implement a Non-Real-Time Radio Intelligent Controller (Non-RT RIC) (110) implemented in the SMO (108), and a Near-Real-Time Radio Intelligent Controller (Near-RT RIC) (114A) associated with the SMO system (108). In an embodiment, the Non-Real-Time Radio Intelligent Controller (Non-RT RIC) (110) may be a logical function within the SMO (108) that may enable Non-RT optimization and control of O-RAN functions by using Machine Learning and Artificial Intelligence. In an embodiment, the Non-RT RIC (110) may comprise a Non-RT RIC Framework and a Non-RT RIC Applications (rApps (112)). In an embodiment, the Non-RT RIC Framework may include Non-RT RIC framework functionalities that support the rApps (112) and an A1 interface. In an embodiment, the A1 interface may serve as an interface between Non-RT RIC and Near-RT RIC functions and applications.
[0034] In an exemplary embodiment, the Near-Real-Time Radio Intelligent Controller (Near-RT RIC) (114A) may be a logical function that may enable Near-RT control and optimization of O-RAN functions via fine-grained data collection and actions over an E2 interface. The E2 interface may be an interface between the Near-RT RIC (114A) and an Open radio access network Distributed Unit (O-DU) (106), an Open radio access network Central Unit Control Plane (O-CU-CP) (116), and an Open radio access network Central Unit User Plane (O-CU-UP) (118) respectively. In an embodiment, E2 interface may be composed of a plurality of E2 nodes. The Near-RT RIC (114A) may include AI/ML workflow including model training, inference, and updates. In an embodiment, the Near-RT RIC (114A) may comprise a Near-RT RIC Framework and Near-RT RIC Applications (xApps (114B)).
[0035] The Non-RT RIC (110) and the Near-RT RIC (114A) may be configured for locating of mobile devices to be tracked (102) by users (128-1, 128-2, 128-3…128-N) (individually referred to as a user (128) and collectively referred to as users (128)). The users (128) may be associated with one or more first computing devices (124-1, 124-2…124-N) (individually referred to as the computing device (124) and collectively referred to as the computing devices (124)). The SMO (108) may be further operatively coupled to the mobile devices (102-1, 102-2,…..102-N) (individually referred to as the mobile device (102) and collectively referred to as the mobile devices (102)), via an Open radio access network Radio Unit (O-RU) (104). The O-RU (104) may process radio frequencies and send the processed radio frequencies to the (O-DU) (106) through a front haul interface.
[0036] The SMO (108) may be communicatively coupled to an external Enrichment Information (EI) server (126). The rApps (112) of the Non-RT RIC (110) interface with the external EI server (126) to obtain an information of the device to be tracked (102). The SMO system (108) and the Near-RT RIC (114A) may be communicatively coupled to the O-DU (106). The O-DU (106) may be communicatively coupled to the O-CU-CP (116) and the O-CU-UP (118). The Near-RT RIC (114A) may also be communicatively coupled to the O-CU-CP (116) and the O-CU-UP (118). Further, the O-CU-CP (116) may be communicatively coupled to the Fifth-Generation (5G) Core (5GC) (120) and the O-CU-UP (118) may be communicatively coupled to a User Plane Function (UPF) (122).
[0037] In an embodiment, the user (128) may subscribe to a service for locating the device to be tracked (102) via a portal in the first computing device (124) or in the device to be tracked (102), by entering the information about the device to be tracked (102). In an embodiment, the user (128) may also subscribe to the service for locating the device to be tracked (102) via an application installed in the device to be tracked (102) or in the first computing device (124) by entering the information about the device to be tracked (102) in the application. In an embodiment, the information of the device to be tracked (102) may be the IMEI of the device to be tracked (102). The user (128) may also create a login credentials to access the portal or the application securely. Once, the subscription to the service for locating the device to be tracked (102) is completed, the first computing device (124) may transmit the information of the device to be tracked (102) to the r-Apps (112) of the Non-RT RIC (110). The r-Apps (112) of the Non-RT RIC (110) may register the information of the device to be tracked (102) and store the information in a database (e.g., 210 as shown in FIG. 2), external to the SMO system (108).
[0038] In an embodiment, the r-Apps (112) of the Non-RT RIC (110) may communicate with the external EI server (126) to determine the IMEI of the mobile device (102), which may be used to track the mobile device (102). Further, the r-Apps (112) may create a policy that may correspond to a RIC Subscription Request. Next, the r-Apps may send the RIC Subscription Request to the x-Apps (114B) of the Near-RT RIC (114A) via the A1 interface (not shown in FIG. 1).
[0039] In an embodiment, the x-Apps (114B) of the Near-RT RIC (114A) may transmit the RIC Subscription Request received from the r-Apps (112) to a plurality of E2 nodes (depicted in FIG. 1) to trigger an occurrence of an event in the device to be tracked (102). The event in the device to be tracked (102) may be triggered by the r-Apps (112) as well as the x-Apps (114B). The plurality of E2 nodes may be logical nodes terminating at the E2 interface. Further, the plurality of E2 nodes may serve as an interface between the Near-RT RIC (114A) and the O-CU-CP (116), the O-CU-UP (118), the O-DU (106), or any combination as allowed by the O-RAN architecture.
[0040] In an embodiment, the plurality of E2 nodes may respond with a RIC Subscription response to the x-Apps (114B) of the Near-RT RIC (114A) in response to the RIC Subscription Request. The plurality of E2 nodes may monitor the occurrence of the event in the device to be tracked (102) periodically prior to sending the RIC Subscription response to the x-Apps (114B) of the Near-RT RIC (114A). The events that may be periodically monitored by the plurality of E2 nodes may include paging the device to be tracked, ringing the device to be tracked, taking a photo by the device to be tracked, displaying a message in the device to be tracked, locking the device to be tracked, and resetting the device to be tracked after locating the device to be tracked. If the event is detected, the plurality of E2 nodes may transmit the RIC Subscription response to the x-Apps (114B) of the Near-RT RIC (114A).
[0041] In an embodiment, the plurality of E2 nodes may transmit Operations and Management (OAM) measurements via an O1 interface (not shown in FIG. 1). In an embodiment, the x-Apps (114B) may consolidate the OAM measurements and may transmit feedback to the r-Apps (112) of the Non-RT RIC (110) via the A1 interface. In an embodiment, the r-Apps (112) may obtain the feedback from the A1 interface and may periodically calculate the events and store an information about the occurrence of events in the device to be tracked (102) in the database (210).
[0042] In an embodiment, the user (128) may request for locating the mobile device (102) via the portal in or the application on the computing device (124) or the device to be tracked (102), to the r-Apps (112) of the Non-RT RIC (110).
[0043] If the r-Apps (112) has the information of the mobile device to be tracked (102), then the r-Apps (112) may retrieve the information of the mobile device (102) from the database (210). The r-Apps (112) may respond to the computing device (124) based on the information retrieved from the database (210), and the computing device (124) may update the details of the mobile device (102) on the portal or the application with the location of the mobile device to be tracked (102). If the r-Apps (112) does not have the information of the mobile device (102), then, the r-Apps (112) may create a request and transmit the created request to the x-Apps (114B) of Near-RT RIC (114A).
[0044] In an embodiment, the x-Apps (114B) of the Near-RT RIC (114A) may receive the request from the r-Apps (112) and may execute the occurrence of the events in the plurality of E2 nodes via a plurality of E2 interfaces (not shown in FIG. 1). In an embodiment, the r-Apps (112) may also execute the occurrence of the events in the device to be tracked (102). The x-Apps (114B) may execute the occurrence of the events as per RIC control procedures of the plurality of E2 nodes. The events to be executed by the x-Apps (114B) or the r-Apps (112) may include paging the mobile device (102), finding the location of the mobile device (102), or triggering certain actions in the mobile device (102), and the like.
[0045] In an embodiment, the plurality of E2 nodes may transmit the RIC Subscription response to the Near-RT RIC (114A). The x-Apps (114B) of the Near-RT RIC (114A) may gather required information and send a feedback to the Non-RT RIC (110) via the A1 interface. In an embodiment, the r-Apps (112) of the Non-RT RIC (110) may consolidate the RIC Subscription response and transmit the RIC Subscription response to the computing device (124). The portal in the computing device 124 may output the location of the mobile device to be tracked (102) to the user (128).
[0046] In an embodiment, the SMO system (108), the Near-RT RIC (114A), and the external EI server (126) may be a System On Chip (SoC) system but not limited to the like. In another embodiment, an onsite data capture, storage, matching, processing, decision-making, and actuation logic may be coded using a Micro-Services Architecture (MSA) but not limited to it. A plurality of microservices may be containerized and may be event-based to support portability.
[0047] In an embodiment, the network architecture (100) may be modular and flexible. The modularity and flexibility of the network architecture (100) may help to accommodate any change in the SMO (108), the Near-RT RIC (114A), and the external EI server (126) as proximate processing may be acquired towards locating mobile devices (102). Configuration details of the SMO system (108), the Near-RT RIC (114A), and the external EI server (126) may be modified on the fly.
[0048] In an exemplary embodiment, a communication network (not shown in FIG. 1) 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. A network may 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 Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, some combination thereof.
[0049] In another exemplary embodiment, the external EI server (126) may include or comprise, by way of example but not limitation, one or more of a stand-alone server, a server blade, a server rack, a bank of servers, a server farm, hardware supporting a part of a cloud service or system, a home server, a hardware running a virtualized server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof.
[0050] In an embodiment, the one or more first computing devices (124), and the one or more mobile devices (102) may communicate with the SMO system (108) via a set of executable instructions residing on any operating system, including but not limited to, Android TM, iOS TM, Kai OS TM and the like. In an embodiment, one or more first computing devices (124) and the one or more mobile devices (102) may include, but not limited to, any electrical, electronic, electro-mechanical or an equipment or a combination of one or more of the above devices such as mobile phone, smartphone, 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 computing device may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, any input device for receiving input from a user such as a touchpad, a touch-enabled screen, an electronic pen, receiving devices for receiving any audio or visual signal in any range of frequencies and transmitting devices that can transmit any audio or visual signal in any range of frequencies. It may be appreciated that the one or more first computing devices (124), and the one or more mobile devices (102) may not be restricted to the mentioned devices and various other devices may be used. A smart computing device may be one of the appropriate systems for storing data and other private/sensitive information.
[0051] In an embodiment, the information of the device to be tracked (102) may be entered into the application installed in the device to be tracked (102) or in the portal in the user device (124) or in the device to be tracked (102). The portal may be a web-based site that may be accessible in the user device (124). The portal may be designed to receive information as input and display information as output. The application may be a software app, that may be available in an app store. The application may be downloaded from the app store and installed in the user device (124) or in the the device to be tracked (102). The application may receive information that may be needed for locating the device to be tracked (102).
[0052] FIG. 2 illustrates an exemplary representation (200) of the Service Management and Orchestration (SMO) system (108) for locating the lost, stolen, and/or misplaced mobile device (102) using an Open-RAN (O-RAN), in accordance with an embodiment of the present disclosure. In an aspect, the SMO system (108) may include one or more processor(s) (202). The one or more processor(s) (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, edge or fog microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (202) may be configured to fetch and execute one or more computer-readable instructions or routines stored in a memory (204) of the SMO system (108). The memory (204) may store the one or more computer-readable instructions or routines in a non-transitory computer-readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (204) may comprise any non-transitory storage device including, for example, a volatile memory such as RAM, or non-volatile memory such as EPROM, flash memory, and the like.
[0053] In an embodiment, the SMO system (108) may include one or more interface(s) (206). The interface(s) (206) may include a variety of interfaces, for example, interfaces for data input and output devices referred to as I/O devices, storage devices, and the like. The interface(s) (206) may facilitate communication with the SMO system (108). The interface(s) (206) may also provide a communication pathway for one or more components of the SMO system (108). Examples of such components may include but are not limited to, processing unit/engine(s) (208) and a database (210).
[0054] The processing unit/engine(s) (208) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s) (208). In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine(s) (208) may be processor-executable instructions stored on a non-transitory machine-readable storage medium. The hardware for the processing engine(s) (208) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine(s) (208).
[0055] In such examples, the SMO system (108) may 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 SMO system (108) and the processing resource. In other examples, the processing engine(s) (208) may be implemented by electronic circuitry.
[0056] The processing engine (208) may include one or more engines selected from any of a data acquisition engine (212) and other engines (216). The data acquisition engine (212) may correspond to the Non-RT RIC (110) which comprises the r-apps (112). The processing engine (208) may allow an edge-based microservice event processing but not limited to the like. In an embodiment, the data acquisition engine (212) may enable the receiving of the information of the device to be tracked (102) from the user device (124) by the processor (202). Further, the data acquisition engine (212) may enable registration of the information of the device to be tracked (102) from the user device (124) by the processor (202). The information of the device to be tracked (102) and the credentials generated upon successful registration of the information of the device to be tracked (102) may be stored in the database (210). In an embodiment, the information of the device to be tracked (102) comprises an IMEI (International Mobile Equipment Identity) code of the device to be tracked (102).
[0057] In an embodiment, the data transfer engine (214) may be external to the SMO system (108), and may correspond to the Near-RT RIC (114A) which may comprise of the x-apps (114). The data transfer engine (214) may be configured to receive a request for locating the device to be tracked (102) based on the registered information from the data acquisition engine (212). Further, the data transfer engine (214) may be configured to send a response corresponding to the received request to the data acquisition engine (212) for locating the device to be tracked (214).
[0058] FIG. 3 illustrates an exemplary block diagram representation (300) of a system architecture, in accordance with an embodiment of the present disclosure.
[0059] The system architecture may be an O-RAN architecture. The r-Apps (112) may have an interface where an external information may be fed to an Operator network. In an embodiment, the Near-RT RIC (306) may be a logical function that enables near-real-time control and optimization of RAN elements and resources via fine-grained data collection and actions over the E2 interfaces, as shown in FIG. 3. The Near-RT RIC (306) may include Artificial Intelligence (AI)/ Machine Learning (ML) workflows including model training, inferences, and updates which are handled by the x-Apps (114B).
[0060] Further, the Non-RT RIC (304) may include a logical function within the Service Management and Orchestration system (SMO) (108), that may drive the content carried across the A1 interface, as shown in FIG. 3. The Non-RT RIC (110) may include a Non-RT RIC Framework and the Non-RT RIC Applications such as the r-Apps (112). Furthermore, the Non-RT RIC framework may function internal to the SMO system (108). The Non-RT RIC framework may logically terminate the A1 interface to the Near-RT RIC (114A). Further, the Non-RT RIC framework may expose a set of internal SMO services needed for their runtime processing, to the r-Apps (112), via an internal R1 interface. The internal R1 interface may serve as an interface between the r-Apps (112) and the functionalities of the Non-RT RIC (304). The Non-RT RIC framework may function within the Non-RT RIC (304) and may provide AI/ML workflow including model training, inference, and updates needed for r-Apps (112).
[0061] Further, the O1 interface from the O-RAN components may terminate at the SMO (108). The O-CU-CP (308) may be a logical node hosting the Radio Resource Control (RRC) and a control plane part of a Packet Data Convergence Protocol (PDCP) of the O-RAN architecture. Further, the O-CU-UP (310) may be a logical node hosting the user plane part of the PDCP and the Service Data Adaptation Protocol (SDAP). The O-DU (312) may be a logical node hosting Radio Link Control (RLC)/Medium Access Control (MAC)/High-Physical (PHY) layers based on a lower layer functional split. Further, the E2 nodes may be terminating at the E2 interface that is for an NR access at the O-CU-CP (116), the O-CU-UP (118), and the O-DU (106), or any combination, and an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (E-UTRA) at the O-eNB (318).
[0062] In an embodiment, the Non-RT RIC applications such as the r-Apps (112) may be modular apps. The r-Apps (112) may leverage a functionality exposed via the R1 interface of the Non-RT RIC framework, to provide value-added services relative to the RAN operation. In an embodiment, the value-added services relative to the RAN operation include, but not limited to, driving the A1 interface, recommending values and actions that may be subsequently applied over the O1/O2 interface, and generating an “enrichment information” for the use of the r-Apps (112), and the like. The r-Apps (112) may function within the Non-RT RIC (304) to enable the Non-RT control and the optimization of RAN elements and resources and the policy-based guidance to the applications/features in Near-RT RIC (306). Further, the Near-RT RIC applications such as the x-Apps (114B) may run on the Near-RT RIC (306). Such applications may include one or more microservices. At the point of onboarding, such applications may identify what data they consume and what data they provide. The applications are independent of the Near-RT RIC (306) and may be provided by any third party. The E2 interface enables a direct association between the x-Apps (114B) and the RAN functionality.
[0063] Further, an O-Cloud (316) may be a cloud computing platform that includes a plurality of physical infrastructure nodes that meet one or more O-RAN requirements to host one or more O-RAN functions of the Near-RT RIC (305), the O-CU-CP (308), the O-CU-UP (310), and the O-DU (312), one or more supporting software components (such as Operating System, Virtual Machine Monitor, Container Runtime, etc.) and one or more management and orchestration functions.
[0064] Additionally, the O1 interface may be between an SMO framework and one or more O-RAN managed elements, for operation and management to achieve Fault management, Configuration, Accounting, Performance, Security, (FCAPS) management, Physical Network Function (PNF) software management, and file management. Further, the O2 interface may be implemented between the SMO framework and the O-Cloud (316) for supporting O-RAN virtual network functions. Furthermore, the A1 interface between the Non-RT RIC (304) and the Near-RT RIC (306) enables non-RT RIC functions to provide policy-based guidance, ML model management, and enrichment information to the Near-RT RIC function so that the RAN can optimize e.g., Radio Resource Management (RRM) under certain conditions. Further, the E2 interface may connect the Near-RT RIC (306) and the one or more O-CU-CPs (308), the one or more O-CU-Ups (310), and the one or more O-DUs (312). The R1 interface may be between the r-Apps (112) and the non-RT RIC framework.
[0065] FIG. 4A illustrates an exemplary flow chart (400a) depicting a method for registering the mobile device to be tracked (102) in a portal for locating the mobile device to be tracked (102) by using the O-RAN architecture (300), in accordance with an embodiment of the present disclosure.
[0066] At block (402), the method may include receiving, by the data acquisition engine (212), the information of the mobile device to be tracked (102). The information of the mobile device to be tracked (102) may be entered into the application installed on or the portal in the computing device (124). The information of the device to be tracked (102) may comprise the IMEI code of the device to be tracked (102). The information of the device to be tracked (102) may be stored in the database (210). At block (404), the method (400a) may include registering of the information of the device to be tracked (102), by the data acquisition engine (212).
[0067] At block (406), the data acquisition engine (212) may communicate with the EI server to obtain the information of the mobile device to be tracked (102). The method may include gathering information by the data acquisition engine (212) and transmitting policies to the data transfer engine (214).
[0068] At block (408), the method (400a) may include subscribing, by the data transfer engine (214), to the E2 nodes. At block (410), the method (400a) may include generating, by the data transfer engine (214), E2 reports and O1 events corresponding to the subscription. At block (412), the method (400a) may include collecting, by the data transfer engine (214), the E2 reports from the E2 nodes, and sending the feedback to the data acquisition engine (212). At block (414), the method (400a) may include collecting, by the data acquisition engine (212), the feedback and the events, and storing major events.
[0069] FIG. 4B illustrates an exemplary flow chart depicting a method (400b) for locating the mobile devices (102), in accordance with an embodiment of the present disclosure.
[0070] At block (422), the method (400b) may include, receiving, by the data acquisition engine (212), the information of the mobile device to be tracked (102) from the user (128) via the computing device (124) to locate lost, stolen, and/or mobile device (102). At block (424), the method (400b) may include, registering, by the data acquisition engine (212), the information of the mobile device to be tracked (102) from the computing device (124). Further, the data acquisition engine (212) may check if the mobile device (102) may be tracked based on the availability of the information of the mobile device to be tracked (102) in the database (210). If the information of the mobile device to be tracked (102) is not available in the database (210), then at block (426), the method (400b) may include, transmitting, by the data transfer engine (214), the policies to the data transfer engine (214) for locating the mobile device (102). At block (428), the method (400b) may include, transmitting, by the data transfer engine (214), a new subscription to the E2 nodes.
[0071] At block (430), the method (400b) may include, receiving, by the data transfer engine (214) the response from the E2 nodes. At block (432), the method (400b) may include, transmitting, by the data transfer engine (214), the feedback to the data acquisition engine (212) based on the response received from the E2 nodes. At block (434), the method (400b) may include, using, by the data acquisition engine (212), the feedback received from the data transfer engine (214), to send the location of the device to be tracked (102) to the computing device (124). At block (436), the method (400b) may include, outputting, by the data acquisition engine (212), the location information of the device to be tracked (102) to the user (128) via the computing device (124).
[0072] Thereafter, the data transfer engine (214), may instruct the mobile device (102) to perform certain actions. The actions may include, but not limited to ringing, clicking a photo, displaying a message, finding the location/paging, locking, erasing/resetting, and the like. The actions such as clicking a photo, displaying a message, erase/reset may be performed via a dedicated application pre-installed in the mobile device (102). When the mobile device (102) is lost/stolen, resetting the mobile device (102) may erase all features in the mobile device (102) including the dedicated application. In an embodiment, locating or paging the mobile device (102) may be performed using the IMEI of the mobile device (102), even though the dedicated application is removed/deleted.
[0073] Further, the data acquisition engine (212) may check if the mobile device (102) may be tracked based on the information of the device to be tracked (102) available in the database (210). If the information of the device to be tracked (102) is available in the database (210), then at block (438), the method (400b) may include, transmitting, by the data acquisition engine (212), the information in the database (210) to the computing device (124). At block (440), the method (400b) may include, outputting, by the data acquisition engine (212), the information of the device to be tracked (102) to the user (128) via the computing device (124).
[0074] Further, similar steps may be involved if the mobile device (102) is misplaced by the user (128). Thereafter, the data transfer engine (214), may instruct the mobile device (102) to perform certain actions. The actions may include, but not limited to ringing, taking a photo, displaying a message, finding location/paging, locking, erasing, resetting, and the like. The actions such as taking a photo, displaying a message, erasing, and resetting may be performed via the dedicated application installed on the mobile device (102). When the mobile device (102) is lost/stolen, resetting the mobile device (102) may erase all the features in the mobile device (102) including the dedicated application. However, locating or paging the mobile device (102) may be performed using the IMEI, even though the dedicated application is removed/deleted.
[0075] FIG. 5 illustrates a sequence diagram representation (500) of registering the mobile device (102) in a portal and locating the mobile device (102) using an O-RAN architecture (300), in accordance with an embodiment of the present disclosure.
[0076] At step (504), the user (128) may subscribe to the service via the portal in or the application on the first computing device (124), by inputting mobile device (102) details. The user (128) may also create the credentials to access the portal or application securely. At step (506), the first computing device (124) may transmit the information of the mobile device (102) to the data acquisition engine (212), upon completing the subscription. At step (508), the data acquisition engine (212) may register the information of the mobile device (102). At step (510), the data acquisition engine (212) may communicate with the external EI server (126) to determine the identity of the mobile device (102), which may be used to track the mobile device (102). At step (512), the data acquisition engine (212) may track the occurrence of the events and send it to the data transfer engine (214) via the A1 interface.
[0077] At step (514), the data transfer engine (214) may transmit the RIC Subscription Request to the plurality of E2 nodes to subscribe for the occurrence of the events mobile device (102) to be periodically monitored. At step (516), the plurality of E2 nodes may respond with the RIC Subscription response to the data transfer engine (214). At step (518), the plurality of E2 nodes may monitor periodically the events, and in case of detection of the occurrence of the event in the mobile device (102), the E2 nodes may transmit the RIC indication to the data transfer engine (214). At step (520), the data transfer engine (214) may consolidate the RIC indication and may transmit the feedback to the data acquisition engine (212). At step (522), the plurality of E2 nodes may transmit the OAM measurements via the O1 interface. In an embodiment, the OAM measurements may be based on periodic monitoring of the event in the device to be tracked (102) and may be sent to the data transfer engine (214). In an embodiment, the data acquisition engine (212) may obtain the feedback from the A1 interface and may periodically calculate the events and store the information about the occurrence of events in the device to be tracked (102) in the database (210).
[0078] At step (524), the user (128) may request for locating the mobile device (102) via the portal in or the application on the computing device (124), to the data acquisition engine (212). If the data acquisition engine (212) has the information of the mobile device to be tracked (102), then the data acquisition engine (212) may retrieve the information of the mobile device (102) from the database (210). The data acquisition engine (212) may respond to the computing device (124) based on the information retrieved from the database (210), and the computing device (124) may update the details of the mobile device (102) on the portal or the application with the location of the mobile device to be tracked (102). If the data acquisition engine (212) does not have the information of the mobile device (102), then, the data acquisition engine (212) may raise a request to locate the device to be tracked (102) and transmit the raised request to the data transfer engine (214).
[0079] At steps (530) and (532), the data transfer engine (214) may receive the request from the data acquisition engine (212) and may execute the occurrence of the events in the plurality of E2 nodes via a plurality of E2 interfaces (not shown in FIG. 1). The data transfer engine (214) may execute the occurrence of the events as per RIC control procedures of the plurality of E2 nodes. In an embodiment, the data acquisition engine (212) may also execute the occurrence of the events in the device to be tracked (102). The events to be executed by the data transfer engine (214) or the data acquisition engine (212) may include paging the mobile device (102), finding the location of the mobile device (102), triggering certain actions in the mobile device (102), and the like.
[0080] At step (534), the plurality of E2 nodes may transmit the RIC Subscription response to the data transfer engine (214). The data transfer engine (214) may gather the information and send the feedback to the data acquisition engine (212) via the A1 interface. In an embodiment, the data acquisition engine (212) may consolidate the RIC Subscription response and transmit the RIC Subscription response to the computing device (124). The portal in or the application on the computing device (124) or the device to be tracked (102) may output the location of the mobile device to be tracked (102) to the user (128).
[0081] FIG. 6 illustrates an exemplary computer system (600) in which or with which embodiments of the present disclosure can be implemented in accordance with embodiments of the present disclosure. As shown in FIG. 6, the computer system (600) can include an external storage device (610), a bus (620), a main memory (630), a read-only memory (640), a mass storage device (650), a communication port (660), and a processor (670). A person skilled in the art will appreciate that the computer system may include more than one processor and communication ports. Examples of the processor (670) include, but are not limited to, an Intel® Itanium® or Itanium 2 processor(s), an AMD® Opteron® or Athlon MP® processor(s), a Motorola® lines of processors, a FortiSOC™ system on chip processors or other future processors. The processor (670) may include various modules associated with embodiments of the present disclosure. The communication port (660) can 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 fiber, a serial port, a parallel port, or other existing or future ports. The communication port (660) may be chosen depending on a network, such as a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system (600) connects. The memory (630) can be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (640) can 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 BIOS instructions for the processor (670). The mass storage (650) may be any current or future mass storage solution, which can 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), e.g. those available from Seagate (e.g., the Seagate Barracuda 782 family) or Hitachi (e.g., the Hitachi Deskstar 13K800), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g. an array of disks (e.g., SATA arrays), available from various vendors including Dot Hill Systems Corp., LaCie, Nexsan Technologies, Inc. and Enhance Technology, Inc.
[0082] The bus (620) communicatively couples the processor(s) (670) with the other memory, storage, and communication blocks. The bus (620) can be, e.g. a Peripheral Component Interconnect (PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), 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 (670) to the computer system (600).
[0083] Optionally, operator and administrative interfaces, e.g., a display, keyboard, and a cursor control device, may also be coupled to the bus (620) to support direct operator interaction with a computer system. Other operator and administrative interfaces can be provided through network connections connected through the communication port (660). The external storage device (610) can be any kind of external hard drive, floppy drive, IOMEGA® Zip Drive, Compact Disc Read-Only Memory (CD-ROM), Compact Disc-Re-Writable (CD-RW), and Digital Video Disk-Read Only Memory (DVD-ROM). Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system limit the scope of the present disclosure.
[0084] FIG. 7 illustrates an exemplary method flow chart (700) depicting a method for locating a device to be tracked (102) by the data acquisition engine (212), in accordance with an embodiment of the present disclosure. The method (700) may be described in the general context of computer-executable instructions. Generally, computer-executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform functions or implement abstract data types.
[0085] The order in which the method (700) is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method (700). Additionally, individual blocks may be deleted from the methods without departing from the scope of the subject matter described herein. Furthermore, the method (700) can be implemented in any suitable hardware, software, firmware, or combination thereof.
[0086] At block (702), the method may include receiving, by a processor (202), an information of the device to be tracked (102) from a user device (124). The information of the device to be tracked (102) may be entered into the application on or the portal in the user device (124) or in the device to be tracked (102). The information of the device to be tracked (102) comprises an IMEI (International Mobile Equipment Identity) code of the device to be tracked (102).
[0087] At block (704), the method may include registering, by the processor (202), the received information. The registration of the received information of the device to be tracked (102) may create a credential entry of the device to be tracked (102) for logging into an application on or a portal in the user device (124).
[0088] At block (706), the method may include sending, by the processor (202), a request for locating the device to be tracked (102) based on the registered information. In this block (706), sending the request for locating the device to be tracked (102) based on the registered information may further trigger an event in the device to be tracked (102) that comprises paging the device to be tracked, ringing the device to be tracked, clicking a photo by the device to be tracked, displaying a message in the device to be tracked, locking the device to be tracked, and resetting the device to be tracked for sending the request for locating the device to be tracked (102) based on the registered information.
[0089] At block (708), the method may include receiving, by the processor (202), a response corresponding to the request sent for locating the device to be tracked (102). In this block, receiving a response corresponding to the request sent for locating the device to be tracked (102) may be based on a periodic monitoring and a detection of an event occurring in the device to be tracked (102).
[0090] At block (710), the method may include transmitting, by the processor (202), the response to the user device (124) to locate the device to be tracked (102). At this block (710), transmitting the response to the user device (124) to locate the device to be tracked (102) may include outputting a location of the device to be tracked to the user device (124).
[0091] 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 invention. These and other changes in the preferred embodiments of the invention 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 to be implemented merely as illustrative of the invention and not as a limitation.

ADVANTAGES OF THE PRESENT DISCLOSURE
[0092] The present disclosure provides a system and method for locating lost, stolen, and/or misplaced mobile devices using the Open Radio Access Network (O-RAN).
[0093] The present disclosure provides systems and methods to enable the user to locate and find the lost, stolen, and/or misplaced mobile devices based on the user requirement, without involving any official authorities or assistance.
[0094] The present disclosure provides systems and methods to enable O-RAN to locate/track the mobile devices using rApps/xApps, based on events in the mobile devices, or periodic events, or manually triggered events.
[0095] Since O-RAN is used for locating the mobile device, the mobile device may be located using the International Mobile Equipment Identity (IMEI) of the mobile device, even if the Subscriber Identity Module (SIM) is changed or the mobile is reset to factory settings.
[0096] The present disclosure provides systems and methods for providing a portal where the user of the lost, stolen, and/or misplaced mobile device may log in and locate the lost, stolen, and/or misplaced mobile device.
[0097] The present disclosure provides systems and methods to enable the lost, stolen, and/or misplaced mobile device to perform tasks/actions, after locating the lost, stolen, and/or misplaced mobile device. The actions may include, but not limited to ringing, taking a photo, displaying a message, finding location/paging, locking, erasing/resetting the mobile device, and the like.

RESERVATION OF RIGHTS
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, IC layout design, and/or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (herein after 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. The present disclosure may pertain to O-RAN specifications as given in 3GPP TR 21.905 [1].
,CLAIMS:1. A system (108) for locating a device to be tracked (102), the system (108) comprising:
a processor (202);
a memory (204) coupled to the processor (202), wherein the memory (204) comprises processor-executable instructions, which on execution, causes the processor to:
receive an information of the device to be tracked (102) from a user device (124);
register the received information;
send a request for locating the device to be tracked (102) based on the registered information;
receive a response corresponding to the request sent for locating the device to be tracked (102); and
transmit the response to the user device (124) to locate the device to be tracked (102).
2. The system (108) as claimed in claim 1, wherein the information of the device to be tracked (102) is entered into an application on or a portal in the user device (124).
3. The system (108) as claimed in claim 1, wherein the information of the device to be tracked (102) comprises an IMEI (International Mobile Equipment Identity) code of the device to be tracked (102).
4. The system (108) as claimed in claim 1, wherein the processor-executable instructions, which on execution, further causes the processor (202) to create a credential entry of the device to be tracked (102) for logging into an application on or a portal in the user device (124) or the device to be tracked (102).
5. The system (108) as claimed in claim 1, wherein the processor-executable instructions, which on execution, further causes the processor (202) to transmit the request for locating the device to be tracked (102) based on the registered information from a data acquisition engine (212) to a data transfer engine (214) via an E2 interface of an Open radio access network Distributed Unit (O-DU) (106), an Open radio access network Central Unit Control Plane (O-CU-CP) (116), and an Open radio access network Central Unit User Plane (O-CU-UP) (118) of an Open Radio Access Network (O-RAN).
6. The system (108) as claimed in claim 1, wherein the processor-executable instructions, which on execution, further causes the processor (202) to trigger an event in the device to be tracked (102) that comprises paging the device to be tracked, ringing the device to be tracked, clicking a photo by the device to be tracked, displaying a message in the device to be tracked, locking the device to be tracked, and resetting the device to be tracked for sending the request for locating the device to be tracked (102) based on the registered information.
7. The system (108) as claimed in claim 6, wherein the processor-executable instructions, which on execution, further causes the processor (202) to trigger a data acquisition engine (212) to execute the event in the device to be tracked (102).
8. The system (108) as claimed in claim 6, wherein the processor-executable instructions, which on execution, further causes the processor (202) to trigger a data transfer engine (214) to execute the event in the device to be tracked (102).
9. The system (108) as claimed in claim 1, wherein the processor-executable instructions, which on execution, further causes the processor (202) to receive a response corresponding to the request sent for locating the device to be tracked (102) based on a periodic monitoring and a detection of an event occurring in the device to be tracked (102).
10. The system (108) as claimed in claim 1, wherein the processor-executable instructions, which on execution, further causes the processor (202) to output a location of the device to be tracked to the user device (124) to locate the device to be tracked (102).
11. A method for locating a device to be tracked (102), the method comprising:
receiving (702), by a processor (202), an information of the device to be tracked (102) from a user device (124);
registering (704), by the processor (202), the received information;
sending (706), by the processor (202), a request for locating the device to be tracked (102) based on the registered information;
receiving (708), by the processor (202), a response corresponding to the request sent for locating the device to be tracked (102); and
transmitting (710), by the processor (202), the response to the user device (124) to locate the device to be tracked (102).
12. The method as claimed in claim 11, wherein the information of the device to be tracked (102) is entered into an application on or a portal in the user device (124) or in the device to be tracked (102).
13. The method as claimed in claim 11, wherein the information of the device to be tracked (102) comprises an IMEI (International Mobile Equipment Identity) code of the device to be tracked (102).
14. The method as claimed in claim 11, wherein the processor (202) further creates a credential entry of the device to be tracked (102) for logging into an application on or a portal in the user device (124) or the device to be tracked.
15. The method as claimed in claim 11, wherein the processor (202) further transmits the request for locating the device to be tracked (102) based on the registered information from a data acquisition engine (212) to a data transfer engine (214) via an E2 interface of an Open radio access network Distributed Unit (O-DU) (106), an Open radio access network Central Unit Control Plane (O-CU-CP) (116), and an Open radio access network Central Unit User Plane (O-CU-UP) (118) of an Open Radio Access Network (O-RAN).
16. The method as claimed in claim 11, wherein the processor (202) further triggers an event in the device to be tracked (102) that comprises paging the device to be tracked, ringing the device to be tracked, clicking a photo by the device to be tracked, displaying a message in the device to be tracked, locking the device to be tracked, and resetting the device to be tracked for sending the request for locating the device to be tracked (102) based on the registered information.
17. The method as claimed in claim 16, wherein the processor (202) further triggers a data acquisition engine (212) to execute the event in the device to be tracked (102).
18. The method as claimed in claim 16, wherein the processor (202) further triggers a data transfer engine (214) to execute the event in the device to be tracked (102).
19. The method as claimed in claim 11, wherein the processor (202) further receives a response corresponding to the request sent for locating the device to be tracked (102) based on a periodic monitoring and a detection of an event occurring in the device to be tracked (102).
20. The method as claimed in claim 11, wherein the processor (202) further outputs a location of the device to be tracked to the user device (124).