A system and method for location tagging and retrieval using unique codes associated with user identifiers

Abstract

The present disclosure relates to a system and method for tagging, retrieving, sharing, and storing locations using unique codes linked to user identifiers. The system (100) includes a user device (101) with a processor (102) and memory, enabling it to receive a user identifier and location data, transmit this data to a server (104), and obtain a unique code. The code is either user-provided or generated by the server (104). Users can retrieve stored locations by providing the unique code, allowing the server (104) to fetch and transmit the data. A database (107) stores user identifiers, location data, and unique codes, ensuring efficient data management. This system enables secure location sharing, efficient tagging, and easy retrieval, enhancing user convenience in managing location information.

Description

A SYSTEM AND METHOD FOR LOCATION TAGGINGAND RETRIEVAL USING UNIQUE CODES ASSOCIATED WITH USER IDENTIFIERSFIELD

[0001] The embodiments herein generally relate to location-based digital mapping and retrieval systems. More particularly, the disclosure relates to a system and method for tagging locations using unique codes and associating them with user identifiers to enable structured, secure, and efficient location retrieval and sharing.BACKGROUND AND PRIOR ART

[0002] Location-based services for identifying and mapping the location of a user or entity are widely used in various applications. With increasing reliance on technology, precise location mapping and retrieval have become critical in numerous real-world scenarios, including navigation, logistics, emergency services, and personal location sharing.

[0003] Conventional methods for location identification primarily rely on manual input or GPS-based retrieval, requiring users to either share exact geographic coordinates or manually enter addresses. These methods are often complex, inefficient, and lack a structured reference for easy retrieval. Furthermore, existing solutions fail to provide a secure and simplified mechanism for associating locations with identifiable references that users can easily recall and share.

[0004] Additionally, conventional systems do not allow efficient multi-user integration for shared location access, leading to fragmented, unstructured, and inefficient location mapping. Current methods often require repetitive input, making them time-consuming, error-prone, and inconvenient for users.

[0005] Therefore, there is a need for a secure and user-friendly system and method for mapping, tagging, and retrieving locations using unique codes. Moreover, there is a need for a structured approach to associating locations with user identifiers, enabling seamless, customized, and secure location access without requiring direct GPS-based location sharing.OBJECTS

[0006] Some of the objects of the present disclosure are described herein below:

[0007] The main objective of the present disclosure is to provide a system and method for tagging locations using unique codes and associating them with user identifiers to enable structured, secure, and efficient location retrieval.

[0008] The main objective of the present disclosure is to provide a system and method for tagging locations using unique codes and associating them with user identifiers to enable structured, secure, and efficient location retrieval.

[0009] Another objective of the present disclosure is to provide a user-friendly system for mapping, tagging, and retrieving locations without requiring direct GPS-based input.

[0010] Yet another objective of the present disclosure is to enable multiple users to efficiently store, access, and retrieve locations using unique codes linked to user identifiers, improving collaborative and shared location mapping.

[0011] Another objective of the present disclosure is to provide a consistent, structured, and searchable digital address system, enabling efficient location referencing without the need for direct geolocation sharing.

[0012] Still another objective of the present disclosure is to facilitate faster and more accurate location retrieval, reducing time spent searching for destinations.

[0013] Yet another objective of the present disclosure is to enhance security and privacy by eliminating the need for sharing live locations or raw GPS coordinates, while still allowing users to access mapped locations.

[0014] Another objective of the present disclosure is to enable users to share a location with contacts by providing only the unique code, wherein the recipient can retrieve the location using the shared unique code and the sender’s already- known user identifier.

[0015] Another objective of the present disclosure is to improve emergency response times by enabling quicker identification of tagged locations in crisis situations.

[0016] Still another objective of the present disclosure is to facilitate e- commerce, logistics, and delivery services by providing a structured and reliable location-tagging system for accurate deliveries.

[0017] Yet another objective of the present disclosure is to improve government, business, and organizational efficiency by implementing a structured locationtagging and retrieval system, reducing reliance on manually entered addresses.

[0018] Another objective of the present disclosure is to provide a secure, scalable, and intuitive system for mapping and retrieving locations, reducing dependency on existing GPS -based services.

[0019] The other objects and advantages of the present disclosure will be apparent from the following description when read in conjunction with the accompanying drawings, which are incorporated for illustration of preferred embodiments of the present disclosure and are not intended to limit the scope thereof.SUMMARY

[0020] In view of the foregoing, an embodiment herein provides a system and method for location tagging and retrieval using unique codes associated with user identifiers.

[0021] In accordance with an embodiment, a system and method for tagging, retrieving, sharing, and storing location data using unique codes associated with user identifiers. The system comprises user devices, a communication network, a server, an API, and a location map. The user devices capture and transmit user identifiers along with location data to the server, where the information is processed, stored, and made accessible for retrieval and sharing. The user identifiers can include mobile numbers, email addresses, Aadhaar numbers, or Unique Personal Identification Numbers (UPINs), which are validated during user registration.

[0022] In one embodiment, the user device includes a user device processor (UD processor) coupled with memory, which processes and transmits location data to the server. The UD processor facilitates user registration, location tagging, and the generation of unique location codes. The location data, along with the unique codes, is stored on the server, which can later be retrieved by the user through a request. In an embodiment, the unique code can include but limited to an alphabet string, a numeric string, an alphanumeric string, a QR code, and a barcode.

[0023] In accordance with an embodiment, the communication network enables real-time data transmission between user devices and the server. It may include wireless networks, wired networks, cellular networks, or the internet, ensuring seamless communication for location-based services. The network allows users to tag, share, and retrieve location data quickly, supporting real-time updates for enhanced location-sharing capabilities.

[0024] In accordance with an embodiment, the server includes an S processor, core engine, and a database. The S processor is responsible for processing user information, generating unique codes, and managing data storage. The core engine enables functionalities like location tagging, retrieval, and mapping, and is integral to interacting with external services via the API. The database storeslocation data securely, allowing efficient retrieval and managing access permissions to protect the stored data.

[0025] In accordance with an embodiment, the API acts as a middleware interface between the server, user devices, and external services. It ensures secure data exchange by managing user authentication and facilitating location tagging, storage, and retrieval. The API can also integrate with third-party mapping platforms, emergency response systems, and logistics tools. It ensures that all interactions with the server are encrypted, and access control policies are enforced to maintain data security.

[0026] In accordance with an embodiment, the location map offers a graphical representation of user-tagged locations and their unique codes. It functions similarly to popular mapping tools like Google Maps, allowing users to interact with and visualize their stored location data. The map is capable of real-time updates and can integrate with third-party services to enhance its functionality. This interactive map enables users to manage their location data effectively and share it with others.

[0027] In accordance with an embodiment, user devices include various interfaces such as registration, location selection, OTP input, and data retrieval. These interfaces facilitate seamless user interaction, enabling easy tagging, sharing, and retrieval of location data. Modules within the user device manage tasks like processing location data, generating unique codes, and transmitting requests to the server for data retrieval. The system ensures secure storage and sharing of location data, giving users full control over their information and ensuring privacy.

[0028] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however,that the following descriptions, while indicating preferred embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.BRIEF DESCRIPTION OF DRAWINGS

[0029] The detailed description is set forth with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different figures indicates similar or identical items.

[0030] Fig. 1 illustrates exemplary network architecture of the proposed system, according to an embodiment herein;

[0031] Fig. 2 illustrates a block diagram of a user device of the proposed system, according to an embodiment herein;

[0032] Fig. 3 illustrates exemplary server architecture of the proposed system, according to an embodiment herein;

[0033] Fig. 4 illustratesan exemplary view of a flow diagram of the proposed method using a user device, according to an embodiment herein; and

[0034] Fig. 5 illustrates an exemplary view of a flow diagram of the proposed method using a server, according to an embodiment herein.DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0035] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments and detailed in the following description. Descriptions of well- known components and processing techniques are omitted soas to notunnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

[0036] As mentioned above, there is a need for a secure and user-friendly system and method for tagging, retrieving, and sharing locations using unique codes. In particular, there is a need for a structured approach that enables associating locations with user identifiers, ensuring efficient location access and retrieval without requiring direct GPS-based inputs.The embodiments herein achieve this by providing "A System and Method for Location Tagging and Retrieval Using Unique Codes Associated with User Identifiers. "Referring now to the drawings, and more particularly to Fig. 1 through Fig. 5, which illustrate various components and processes of the system, including the system architecture, user device modules, server architecture, and methods for tagging and retrieving locations, there are shown preferred embodiments.

[0037] Fig. 1 illustrates an architecture of a system 100 for tagging, retrieving, sharing, and storing locations using unique codes associated with user identifiers. The system 100 may include a plurality of user devices 101, a communication network 103, a server 104, an API 111, and a location map 112. The user devices 101 can be configured to communicate with the server 104 via the communication network 103 to facilitate location tagging, retrieval, sharing, and storage.

[0038] In an embodiment, the user device 101 may include a user device processor (referred herein as UD processor) 102 coupled with a memory. The UD processorcan be configured to capture, process, and transmit user identifier inputs and location data. The UD processor 102 can be further configured to transmit the user identifier and tagged location information via the communication network103 to the server processor (referred herein as S processor) 105 in the server 104, where the information is processed for user registration, authentication, secure location-tagging, and storage. The user identifier can include, but is not limited to, a mobile number, an email, an Aadhaar number, or a UPIN.

[0039] In an embodiment, the user device 101 can include, but is not limited to, a mobile phone, a laptop, a tablet, or any electronic communication device.

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

[0041] In an embodiment, the server 104 may include the S processor 105, core engine 106, and a database 107. The S processor 105 can be configured to retrieve user identifier, validate the user, and generate a UUID (Unique User Identifier), and transmit the tagged location with the unique code to the database 107.

[0042] In an embodiment, the database 107 may comprise data including user table 108, location table 109, and tagging table 110 that may be either stored or generated as a result of functionalities implemented by any of the components ofthe S processor 105 or the core engine 106. In an embodiment, the database 107 may be separate from the system 100.

[0043] Upon successful registration and location tagging, the S processor 105 can be configured to transmit a confirmation to the user device 101 via the communication network 103, thereby enabling controlled access for the user to the tagged location and its associated unique code for future retrieval and sharing.

[0044] In an embodiment, the API 111 can be configured to serve as a middleware interface for communication between the server 104, user devices 101, and external services. The API 111 can be further configured to facilitate user registration and authentication, thereby ensuring secure data exchange between the user devices 101 and the server 104. Additionally, the API 111 may enable location tagging, storage, retrieval, and sharing, thereby handling requests for storing, retrieving, and distributing tagged locations. The API 111 can be further configured to facilitate integration with external services, including mapping providers, logistics systems, and emergency response platforms. The API 111 can also be configured to enforce security by ensuring end-to-end encryption and implementing access control policies for location retrieval and sharing.

[0045] In an embodiment, the location map 112 can be configured to serve as the graphical representation of tagged locations with their unique codes, wherein the locationmap 112 can function like an interactive mapping system such as Google Maps. The location map 112 canbe configured to display the user-tagged locations, thereby allowing users to visually manage location-based data. Additionally, the location map 112 can configured to support real-time updates, thereby integrating live location-sharing, retrieval, and storage capabilities. The location map 112 can be further configured to provide third-party mapping servicecompatibility, thereby supporting platforms such as Google Maps, OpenStreetMap, or proprietary GIS solutions.

[0046] In an alternative embodiment, the system 100 can be configured to store tagged location data in decentralized or distributed storage systems, including blockchain or secure peer-to-peer networks, to enhance privacy and access control.

[0047] In an embodiment, Fig. 2 illustrates a block diagram of a user device 101 of the proposed system 100 for tagging, retrieving, sharing, and storing locations using unique codes associated with user identifiers. In an embodiment, the user device 101 can be configured to provide a plurality of interfaces that enable user interaction for various input and output functions from the various modules provided in the user device 101.

[0048] In an embodiment, the user device 101 may include a user registration interface 201, an OTP input interface 202, an authentication confirmation interface 203, a location selection interface 204, an unique code input interface 205, a system-generated unique code display interface 206, a location confirmation interface 207, a location search interface 208 and other interfaces. Further, the user device 101 may include a user registration and communication module 211, an OTP handling module 212, an authentication and verification module 213, a location processing module 214, a location transmission module 215, a data retrieval module 216, a tagging and association module 217, a location retrieval module 218 and data display module 219, and other modules having functions that may include but are not limited totagging location with unique code, retrieval, sharing, and storage.

[0049] In an embodiment, the user registration interface 201 can be configured to allow a user to input a user identifier, wherein the user identifier can include, but is not limited to, a mobile number, an email, an Aadhaar number, or a UPIN.The UD processor 102 can be configured to capture the user identifier, execute data transmission via the communication network 103, and transfer the identifier to the server 104 for processing.

[0050] In an embodiment, a user registration and communication module 211 may facilitate the data transmission by ensuring seamless interaction between the UD processor 102 and the S processor 105 in the server 104.

[0051] In an embodiment, An OTP input interface 202 can be configured to enable users to enter a one-time password (OTP) for verification based on the input user identifier, wherein an OTP handling module 212 can be configured to enable the UD Processor 102 to execute OTP transmission to the S processor 105 in the server 104 for validation.

[0052] In an embodiment, an authentication confirmation interface 203 can be configured to display the successful verification status of the OTP, wherein an authentication and verification module 213 can be configured to enable the UD processor 102 to execute secure authentication and system access confirmation.

[0053] In an embodiment, a location selection interface 204 can be configured to allow users to select or specify a desired location using a map-based input mechanism, wherein the location selection enables tagging, searching, or retrieval operations within the system. In an embodiment, a location processing module 214 can be configured to enable the UD processor 102 to execute processing of the selected location and prepare it for further actions. In an embodiment, a location transmission module 215 can be configured to enable the UD processor 102 to execute real-time capture and transmission of the user’s selected location (latitude & longitude) via the communication network 103 to the S processor 105 in the server 104 for processing and storage. Further, The location transmission module 215 can be configured to ensure synchronization and consistency of location data across the system.

[0054] In an embodiment, a unique code input interface 205 can be configured to enable the user to securely enter a unique identifier for location association and authentication. In another embodiment, a system-generated unique code display interface 206 can be configured to enable the display of a unique code that is automatically generated, which can be associated with a user-selected location for verification and future retrieval.

[0055] In an embodiment, a tagging and association module 217 can be configured to enable the UD processor 102 to execute the processing and storage of the entered or system-generated unique code, ensuring secure tagging. The tagging and association module 217 can also be configured to allow the UD processor 102 to execute operations for modification and deletion of tagged locations based on user preferences.

[0056] In an embodiment, a location confirmation interface 207 can be configured to display the user's geographical location using location data, wherein a location verification module can be configured enables the UD Processor 102 to execute verification of location data and control access to location-based services. The location verification module can be configured to ensure the accuracy of tagged locations and prevents unauthorized modifications.

[0057] In an embodiment, a location search interface 208 can be configured to display search options for specific geographic locations based on stored unique codes, addresses, or points of interest, wherein a location retrieval module 218 can be configured to enable the UD processor 102 to execute retrieval of stored location data. Further, the location retrieval module 218 can be configured to enable filtering and sorting of search results based on user-defined preferences.

[0058] In an embodiment, a retrieved location display interface 209 can be configured to present the retrieved mapped location and associated details, wherein a data display module 219 can be configured to enable the UD processor102 to execute visualization and structured presentation of the retrieved mapped location and associated details. In an embodiment, a data retrieval module 216 can be configured to enable the UD processor 102 to execute access and confirmation of stored location data from the S processor 105 in the server 104, ensuring successful tagging and association. Further, the data retrieval module 216 may also enables synchronization of stored location data across multiple devices associated with the same user account.

[0059] Fig. 3 illustrates the server architecture 300 of the proposed system, according to an embodiment. The server 104 may include a server processor (S processor) 105, a core engine 106, and a database 107. The S processor 105 can be configured to store, retrieve, and process data based on instructions received from the modules in the core engine 106. The core engine 106 can be configured to enable location-based tagging, mapping, retrieval, and management functionalities via the API 111. The database 107 can be configured to store user authentication records, tagged location data, retrieval logs, and access control policies, ensuring redundancy, encryption, and secure access.

[0060] In an embodiment, the core engine 106 may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the core engine 106. In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the core engine 106 may be processor-executable instructions stored on a non- transitory machine-readable storage medium and the hardware for the core engine 106 may comprise a processing resource (for example, one or more processors 105), 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 core engine 208. In such examples, thesystem 100 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 system 100 and the processing resource. In other examples, the core engine 106 may be implemented by electronic circuitry.

[0061] In an embodiment, the core engine 106 may include one or more engines selected from any of a user registration and authentication module 301, a location processing module 302, an unique code generation module 303, a tagging and association module 304 and a data storage and security module 305having functions that may include but are not limited to tagging, retrieving, and sharing locations using unique codes.

[0062] In an embodiment, a user registration and authentication module 301 can be configured to enable the S processor 105 to receive, validate, and register user identifiers, execute authentication functions, and store UUIDs in the database 107. Upon successful validation, the S processor 105 can be configured to execute the generation of a UUID and stores the user identifier and generated UUID in the database 107.

[0063] In an embodiment, a location processing module 302 can be configured to enable the S processor 105 for receiving, processing, and storing location data from a user device 101 via a communication network 103. Further, the S processor 105 can be configured to receive location details and executes the operations for storing and managing location data within the database 107.

[0064] In an embodiment, a unique code generation module 303 can be configured to enable the S processor 105 to generate and store a unique code associated with a user-selected location based on predefined instructions. In an embodiment, the tagging and association module 304 can be configured to enable the S processor 105 to execute operations for linking the generated unique codewith the respective user identifier and storing the tagged location data accordingly.

[0065] In an embodiment, a data storage and security module 305 can be configured to enable the S processor 105 to execute secure storage, retrieval, encryption, and integrity validation of location-based data. The module ensures encryption, access control policies, and data integrity validation for location -based data stored in the database 107.

[0066] In an embodiment, the database 107 can be configured to support indexing and query-based retrieval of stored location data, along with backup and redundancy mechanisms to ensure reliability and prevent data loss.

[0067] Fig. 4 illustrates an exemplary flow diagram of a method implemented using a user device 101, according to an embodiment of the present disclosure. The method includes:

[0068] At step 401, displaying a user registration interface via the user interface module 210 to facilitate user interaction for entering a user identifier and capturing the user identifier input, andtransmitting the user identifier from the UD Processor 102 to the S processor 105 in the server 104 via the user registration & communication module 211.

[0069] At step 402, receiving an OTP from the S Processor 105 in the server 104 via the OTP handling module 212 and displaying an OTP input interface, andcapturing OTP input from the user using the authentication & verification module 213 and transmitting it to the S Processor 105 for validation.

[0070] At step 403, receiving the authentication success or failure response from the S Processor 105 in the server 104 via the authentication & verification module 213, and proceeding to allow or restrict user access.

[0071] At step 404, displaying a location selection interface via the location processing module 214 and capturing the user’s location selection (latitude & longitude) via a map-based input mechanism.

[0072] At step 405, transmitting the captured location data from the UD Processor 102 to the S Processor 105 in the server 104 using the location transmission module 215 and storing the data in the database 107.

[0073] At step 406, receiving confirmation of the stored location from the S Processor 105 in the server 104 via the data retrieval module 216 and displaying a tagging interface for unique code entry via the tagging & association module 217.

[0074] At step 407, capturing a user-defined unique code (if provided) and transmitting it from the UD Processor 102 to the S Processor 105 in the server 104 via the tagging & association module 217. If a user-defined unique code is not provided, receiving a system-generated unique code from the S Processor 105.

[0075] At step 408, linking the unique code with the user identifier using the tagging & association module 217 and sending a confirmation message to the UD processor 102.

[0076] At step 409, allowing the user to search for stored locations using the unique code through the location retrieval module 218 and transmitting the unique code-based location retrieval request to the S Processor 105 via the data retrieval module 216.

[0077] At step 410, receiving and displaying the retrieved mapped location and associated details via the data display module 219 on the user device 101, ensuring secure and seamless access to location-based data.

[0078] Fig. 5 illustrates an exemplary view of a flow diagram of the proposed method using a server, according to an embodiment of the present disclosure. The method includes:

[0079] At step 501, receiving a user identifier from the UD Processor 102 in the user device 101 via the user registration & communication module 211, wherein the user identifier includes, but is not limited to, a mobile number, an email, an Aadhaar number, or a UPIN, and generating a UUID using the user registration & authentication module 301 in the core engine 106.

[0080] At step 502, transmitting an OTP to the user device 101 via the authentication & verification module 213 and SMS Gateway, receiving the OTP input from the UD Processor 102, and validating the OTP using the authentication & verification module 213.

[0081] At step 503, storing the UUID and user identifier in the database 107 using the data storage & security module 305.

[0082] At step 504, receiving location selection input (latitude and longitude) from the UD Processor 102 via the location processing module 302, processing the received location data, and storing it in the database 107 using the data storage & security module 305.

[0083] At step 505, associating a unique code with the stored location. If a user- defined unique code is received, storing it via the tagging & association module 304. Otherwise, generating a system-defined unique code via the unique code generation module 303 and storing it in the database 107.

[0084] At step 506, linking the unique code with the user identifier using the tagging & association module 304 and confirming the unique code association, sending a confirmation message to the UD Processor 102.

[0085] At step 507, receiving a location retrieval request from the UD Processor 102, wherein the request contains a unique code for retrieving a mapped location, and processing the retrieval request using the location retrieval module 218.

[0086] At step 508, fetching the corresponding mapped location from the database 107 and transmitting it to the UD Processor 102.

[0087] At step 509, displaying the retrieved mapped location and associated details via the data display module 219 on the user device 101.

[0088] At step 510, enabling secure access and management of location-based data by integrating retrieval, tagging, and authentication functionalities to ensure seamless operation between the user device 101 and the server 104.

[0089] The present disclosure provides a secure, structured, and user-friendly system and method for tagging, retrieving, sharing, and storing locations using unique codes associated with user identifiers. The system enhances location-based services by enabling seamless mapping, identification, and retrieval of locations through an intuitive tagging mechanism.

[0090] One of the key advantages of the present disclosure is the ability to associate a unique code with a location while linking it to a registered user identifier. This ensures simplified retrieval of stored locations, reducing the dependency on traditional address-based searching. The system further enables efficient navigation, making it particularly useful for logistics, emergency response, and e-commerce applications.

[0091] Another advantage is the improved security and privacy provided by the architecture. The system ensures controlled access to location data, preventing unauthorized modifications or retrievals. The use of a two-step authentication mechanism involving a one-time password (OTP) verification and unique code tagging enhances the security of the system. Furthermore, role-based access controls ensure that only authorized users can retrieve or modify stored locations.

[0092] The present disclosure also improves data management and accessibility by leveraging structured database storage for tagged locations. The system maintains indexed retrieval mechanisms, allowing for quick and efficient lookup of stored locations based on unique codes or user identifiers. The integration withexternal mapping services, such as Google Maps or GIS systems, further enhances usability and adaptability.

[0093] Additionally, the system facilitates location-sharing with minimal data exchange, ensuring that users can share only the unique code instead of complex address details. This feature is particularly useful in ride-sharing, event management, and delivery services, where precise location sharing is critical.

[0094] The modular architecture of the system further enhances scalability and adaptability. The system can be deployed across multiple devices and platforms, ensuring compatibility with mobile applications, web interfaces, and enterprise software solutions. The ability to store and retrieve locations efficiently reduces manual intervention, thereby improving the overall user experience.

[0095] Moreover, the present disclosure allows for alternative embodiments, including decentralized storage using blockchain technology or secure peer-to- peer networks, ensuring tamper-proof and verifiable location data storage. The adaptability of the system enables its application in smart city planning, geolocation-based authentication, and secure logistics tracking.

[0096] If the specification states a component or feature “may”, “can”, “could”, or “might” be included or have a characteristic, that particular component or feature is not required to be included or have the characteristic.

[0097] As used in the description herein and throughout the claims that follow, the meaning of “a,” “an,” and “the” includes plural reference unless the context clearly dictates otherwise. Also, as used in the description herein, the meaning of “in” includes “in” and “on” unless the context clearly dictates otherwise.

[0098] It is to be appreciated by a person skilled in the art that while various embodiments of the present disclosure have been elaborated for system and method for facilitating decentralized identity management. However, the teachings of the present disclosure are also applicable for other types ofapplications as well, and all such embodiments are well within the scope of the present disclosure. However, the system and method facilitating decentralized identity management is also equally implementable in other industries as well, and all such embodiments are well within the scope of the present disclosure without any limitation.

[0099] Accordingly, the present disclosure provides a system and method for facilitating decentralized identity management.[000100] Moreover, in interpreting the specification, all terms should be interpreted in the broadest possible manner consistent with the context. In particular, the terms “comprises” and “comprising” should be interpreted as referring to elements, components, or steps in a nonexclusive manner, indicating that the referenced elements, components, or steps may be present, or utilized, or combined with other elements, components, or steps that are not expressly referenced. Where the specification claims refer to at least one of something selected from the group consisting of A, B, C....and N, the text should be interpreted as requiring only one element from the group, not A plus N, or B plus N, etc.[000101] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, 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 should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in theart will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the embodiments as described herein.

Claims

aim:

1. A system (100) for tagging, retrieving, sharing, and storing locations using unique codes associated with user identifiers, the system (100) comprising: at least one user device (101) including a user device processor (UD processor 102) coupled with a memory, wherein the memory stores instructions which, when executed by the UD processor (102), cause the user device (101) to: receive a user identifier and location data selected by the user; transmit the user identifier and location data to a server (104); receive a unique code associated with the location data, wherein the unique code is either: provided by the user and transmitted to the server (104); or generated by the server (104) and transmitted to the user device (101); transmit a request to the server (104) for retrieval of the location data using the unique code; and receive the location data from the server (104) in response to the request. the server (104) including a server processor (S processor 105) coupled with a memory, wherein the memory stores instructions which, when executed by the S processor (105), cause the server (104) to: receive the user identifier and location data from the user device (101); generate the unique code associated with the location data if not provided by the user; store the user identifier, location data, and unique code in a database (107);receive a request from the user device (101) for retrieval of the location data using the unique code; and transmit the location data to the user device (101) in response to the request.

2. The system (100) of claim 1, wherein the user identifier comprises at least one of a mobile number, an email address, an Aadhaar number, or a Unique Personal Identification Number (UPIN).

3. The system (100) of claim 1, wherein the location data comprises at least one of latitude and longitude coordinates, a physical address, or a point of interest.

4. The system (100) of claim 1, wherein the unique code comprises at least one selected from the group consisting of an alphabet string, a numeric string, an alphanumeric string, a QR code, and a barcode.

5. The system (100) of claim 1, wherein the user device (101) further configured to: utilize a Global Positioning System (GPS) module to determine the user's current geographical location, facilitating the selection of accurate location data; link the unique code with the selected location data within the user device (101); transmit the linked unique code and location data to the server (104) for association and storage; enable the user to share the unique code with other users through communication applications installed on the user device (101); and store a history of transmitted unique codes and associated location data for future reference.

6. The system (100) of claim 1, wherein the server (104) comprises a core engine (106) coupled with the S processor (105), wherein the core engine (106) is configured to: integrate with a location map module (112) to provide visual representations of the stored location data; and utilize an Application Programming Interface (API) (111) to facilitate communication between the server (104) and external services or applications.

7. The system (100) of claim 1, wherein the server (104) further comprises a database (107) configured to: store the user identifier, unique code, and associated location data received from the user device (101); maintain the integrity and security of the stored data; facilitate efficient retrieval of location data upon receiving a request containing the unique code; and support data backup and recovery processes to prevent data loss.

8. The system (100) of claim 1, wherein the server (104) comprises an Application Programming Interface (API) (111) configured to: facilitate communication between the user device(s) (101) and the server (104) for transmitting and receiving data, including user identifiers, location data, and unique codes; enable third-party applications to access and interact with the system (100) for retrieving and displaying location data associated with unique codes; ensure secure data transmission by implementing authentication and encryption protocols to protect user information during communication; andprovide standardized endpoints for consistent and efficient data exchange between the user device (101), server (104), and external services.

9. A method for tagging, retrieving, sharing, and storing locations using unique codes associated with user identifiers, the method comprising: receiving, by a user device (101), a user identifier and location data selected by a user; transmitting, by the user device (101), the user identifier and location data to a server (104); generating, by the server (104), a unique code associated with the location data; transmitting, by the server (104), the unique code to the user device (101); storing, by the server (104), the user identifier, unique code, and associated location data in a database (107); receiving, by the server (104), a request from the user device (101) for retrieval of the location data using the unique code; retrieving, by the server (104), the location data associated with the unique code from the database (107); transmitting, by the server (104), the retrieved location data to the user device (101); displaying, by the user device (101), the retrieved location data to the user.

10. The method of claim 9, further comprising: authenticating the user identifier by the server (104) before generating the unique code;providing the user with an option to manually input a unique code associated with the selected location data; encrypting the user identifier, location data, and unique code before transmission between the user device (101) and the server (104) to ensure data security; allowing the user to share the unique code with other users through communication applications installed on the user device (101); and enabling other users to retrieve the associated location data by inputting the shared unique code into their user devices (101).

Images