Description:BACKGROUND
Field of Invention
[001] Embodiments of the present invention generally relate to a based system for managing an electronic device and particularly to a blockchain based system for managing an electronic device.
Description of Related Art
[002] Consumers purchasing second-hand electronic devices such as mobile phones, laptops, tablets, sound systems, and so forth face uncertainty due to the absence of reliable product information. They cannot easily determine whether a device still has valid warranty coverage, whether it is authentic, or whether it has a lawful ownership record. Repair and service history is unavailable, that prevents buyers from making informed decisions. This lack of transparency discourages customers from purchasing used electronics and contributes to a rise in electronic waste.
[003] At present, resale of used electronics largely occurs through online marketplaces or local vendors. Buyers rely on details provided by sellers, and some manufacturers provide limited warranty verification through serial numbers. A few service providers offer extended warranties, but these generally remain restricted to the original purchaser. Certain third-party tools allow manual entry of repair records, though these depend on voluntary updates and cannot ensure accuracy.
[004] However, these existing solutions suffer from significant shortcomings. Warranty verification mechanisms reveal only partial information and fail to capture ownership or repair history. Extended warranties are often non-transferable and difficult to validate when a product changes hands. Seller-dependent systems lack reliability and are vulnerable to manipulation. As a result, information remains fragmented, unverifiable, and incomplete, leaving consumers exposed to risks such as counterfeit products, hidden damages, or unsupported device.
[005] There is thus a need for an improved and advanced blockchain based system for managing an electronic device that can administer the aforementioned limitations in a more efficient manner.
SUMMARY
[006] Embodiments in accordance with the present invention provide a blockchain based system for managing an electronic device. The system comprising a processor, operably in communication with a client device through a communication network. The processor is configured to acquire a service data related to the electronic device from the client device. The acquired service data is linked to a unique identifier; classify the acquired service data based on service attributes. The service attributes are selected from ownership details, a warranty information, a repair history, or a combination thereof; map the service attributes to the corresponding unique identifier linked with the classified service data; and store the unique identifier and the corresponding linkage of the classified service data and the service attributes in a blockchain ledger associated with the electronic device.
[007] Embodiments in accordance with the present invention further provide a method for managing an electronic device. The method comprising steps of acquiring a service data related to the electronic device from a client device. The acquired service data is linked to an unique identifier; classifying the acquired service data based on service attributes., the service attributes are selected from ownership details, a warranty information, a repair history, or a combination thereof; mapping the service attributes to the corresponding unique identifier linked with the classified service data; and storing the unique identifier and the corresponding linkage of the classified service data and the service attributes in a blockchain ledger associated with the electronic device.
[008] Embodiments of the present invention may provide a number of advantages depending on their particular configuration. First, embodiments of the present application may provide a blockchain based system for managing an electronic device.
[009] Next, embodiments of the present application may provide a system for managing an electronic device that allows warranty coverage to move seamlessly between different owners.
[0010] Next, embodiments of the present application may provide a system for managing an electronic device that maintains a secure, tamper-proof record of purchase, ownership, warranty, and repair events.
[0011] Next, embodiments of the present application may provide a system for managing an electronic device that stores data on a blockchain.
[0012] These and other advantages will be apparent from the present application of the embodiments described herein.
[0013] The preceding is a simplified summary to provide an understanding of some embodiments of the present invention. This summary is neither an extensive nor exhaustive overview of the present invention and its various embodiments. The summary presents selected concepts of the embodiments of the present invention in a simplified form as an introduction to the more detailed description presented below. As will be appreciated, other embodiments of the present invention are possible utilizing, alone or in combination, one or more of the features set forth above or described in detail below.
BRIEF DESCRIPTION OF THE DRAWINGS
[0014] The above and still further features and advantages of embodiments of the present invention will become apparent upon consideration of the following detailed description of embodiments thereof, especially when taken in conjunction with the accompanying drawings, and wherein:
[0015] FIG. 1 illustrates a block diagram of a blockchain based system for managing an electronic device, according to an embodiment of the present invention;
[0016] FIG. 2 illustrates a schematic diagram of a blockchain based system for managing an electronic device, according to an embodiment of the present invention; and
[0017] FIG. 3 depicts a flowchart of a method for managing an electronic device, according to an embodiment of the present invention.
[0018] The headings used herein are for organizational purposes only and are not meant to be used to limit the scope of the description or the claims. As used throughout this application, the word "may" is used in a permissive sense (i.e., meaning having the potential to), rather than the mandatory sense (i.e., meaning must). Similarly, the words “include”, “including”, and “includes” mean including but not limited to. To facilitate understanding, like reference numerals have been used, where possible, to designate like elements common to the figures. Optional portions of the figures may be illustrated using dashed or dotted lines, unless the context of usage indicates otherwise.
DETAILED DESCRIPTION
[0019] The following description includes the preferred best mode of one embodiment of the present invention. It will be clear from this description of the invention that the invention is not limited to these illustrated embodiments but that the invention also includes a variety of modifications and embodiments thereto. Therefore, the present description should be seen as illustrative and not limiting. While the invention is susceptible to various modifications and alternative constructions, it should be understood, that there is no intention to limit the invention to the specific form disclosed, but, on the contrary, the invention is to cover all modifications, alternative constructions, and equivalents falling within the scope of the invention as defined in the claims.
[0020] In any embodiment described herein, the open-ended terms "comprising", "comprises”, and the like (which are synonymous with "including", "having” and "characterized by") may be replaced by the respective partially closed phrases "consisting essentially of", “consists essentially of", and the like or the respective closed phrases "consisting of", "consists of”, the like.
[0021] As used herein, the singular forms “a”, “an”, and “the” designate both the singular and the plural, unless expressly stated to designate the singular only.
[0022] FIG. 1 illustrates a block diagram of a blockchain based system 100 (hereinafter referred to as the system 100) for managing an electronic device 200 (as shown in FIG. 2), according to an embodiment of the present invention. In an embodiment of the present invention, the system 100 may be configured to perform operations that may enable acquisition of service data related to the electronic device 200, association of the service data with a unique identifier, and subsequent management of warranty, ownership, and repair history. The system 100 may provide a unified framework that may ensure secure storage and retrieval of the service data in a blockchain, thereby facilitating transparency and trust in an electronic device lifecycle management.
[0023] In operation, the system 100 may enable receipt of information corresponding to the electronic device 200, may process the received information in accordance with predetermined service attributes, and may store the processed information in a tamper-proof blockchain ledger. The system 100 may further allow authorized service centers or authorized users to access or verify the stored information, ensuring that warranty status, ownership history, and repair records of the electronic device 200 remain verifiable and reliable.
[0024] In an embodiment of the present invention, the system 100 may allow authorized service centers or registered users to log the service events, such as repairs, part replacements, or transfers of ownership into the system 100. The logging may require authentication to ensure that only authorized entities update the service data.
[0025] Accordingly, the system 100 may establish an integrated environment for handling electronic device 200 data in a decentralized and immutable manner, which may address challenges related to fragmented, unverifiable, or manipulated records in the domain of second-hand electronics. Further, the system 100 may be configured to encourage reuse of electronic device 200 by maintaining a verifiable digital record of ownership, warranty, and repair history. Such transparency may reduce consumer hesitation in purchasing used electronics, thereby contributing to reduction of electronic waste. The system 100 may overcome limitations of existing platforms that rely on seller-provided information or centralized databases by providing tamper-proof, verifiable, and transferable records through decentralized storage.
[0026] According to the embodiments of the present invention, the system 100 may incorporate non-limiting hardware components to enhance a processing speed and an efficiency, such as the system 100 may comprise a client device 102, a processor 104, an application server 106, a blockchain ledger 108, smart contracts 110, a communication network 112, and a storage medium 114. In an embodiment of the present invention, the hardware components of the system 100 may be integrated with computer-executable instructions for overcoming the challenges and the limitations of the existing systems.
[0027] In an embodiment of the present invention, the client device 102 may be a device used by a user. The client device 102 may enable the user to upload the service data relating to the electronic device 200 to the system 100. The client device 102 may be adapted to relay the acquired service data to the processor 104. In an embodiment of the present invention, the system 100 may be configured to register the electronic device 200 at a point of first sale. The registration may be initiated by a manufacturer or an authorized seller who may enter original purchase details, warranty terms, and initial ownership information into the system 100 using a client device 102.
[0028] In an embodiment of the present invention, the client device 102 may comprise a mobile application (not shown) or a web interface (not shown) that may enable the user to scan a quick response (QR) code or input the unique identifier to access warranty, ownership, and repair history of the electronic device 200. The mobile application or the web interface may provide a graphical dashboard to view device history and service records. The backend logic may be configured to interact with the blockchain ledger 108 and the smart contracts 110, while the frontend logic may allow scanning of QR codes and input of device identifiers.
[0029] The client device 102 may be, but not limited to, a personal computer, a consumer device, and alike. Embodiments of the present invention are intended to include or otherwise cover any type of the client device 102 including known, related art, and/or later developed technologies. In an embodiment of the present invention, the personal computer may be, but not limited to, a desktop, a server, a laptop, and alike. Embodiments of the present invention are intended to include or otherwise cover any type of the personal computer, including known, related art, and/or later developed technologies.
[0030] Further, in an embodiment of the present invention, the consumer device may be, but not limited to, a tablet, a mobile phone, a notebook, a netbook, a smartphone, a wearable device, and so forth. Embodiments of the present invention are intended to include or otherwise cover any type of the consumer device, including known, related art, and/or later developed technologies.
[0031] In an embodiment of the present invention, the processor 104 may be located on the application server 106. The processor 104 may be configured to acquire the service data related to the electronic device 200 from the client device 102. In an embodiment of the present invention, the processor 104 may be configured to acquire the service data related to the electronic device 200 from the client device 102 through a secure communication channel. In another embodiment, the processor 104 may be configured to acquire the service data by invoking an application programming interface (API) installed on the client device 102. The API may be adapted to collect relevant information from the device memory or from user inputs and may transmit the same to the processor 104. In yet another embodiment, the processor 104 may be configured to acquire the service data through wireless protocols supported by the client device 102. The wireless protocols may include Bluetooth, Wi-Fi, or cellular connectivity, that may facilitate real-time transfer of the service data from the client device 102 to the processor 104. In a further embodiment, the processor 104 may be configured to acquire the service data by scanning the unique identifier associated with the electronic device 200 through the client device 102. The processor 104 may be configured to acquire original purchase details, including purchase date, seller information, and warranty initiation data, and may link the details to the unique identifier of the electronic device 200. The unique identifier may be a quick response (QR) code, a near-field communication (NFC) tag, or a serial number that may be relayed to the processor 104 for linking with the corresponding service attributes.
[0032] The processor 104 may be configured to link the acquired service data to the unique identifier. The unique identifier may be a string of characters encoded in a quick response (QR) code, a near-field communication (NFC) tag, and so forth. The acquired service data may be linked to the unique identifier by embedding metadata within an identifier string. The metadata may include attributes such as timestamp, device type, or service category that may be associated with the electronic device 200. In another embodiment, the processor 104 may be configured to link the acquired service data to the unique identifier by generating a mapping table that may associate each service record with the corresponding quick response (QR) code or the near-field communication (NFC) tag assigned to the electronic device 200. In yet another embodiment, the processor 104 may be configured to link the acquired service data to the unique identifier by encrypting the service data and embedding a cryptographic hash of the data into the identifier string, thereby ensuring authenticity and traceability. In a further embodiment, the processor 104 may be configured to link the acquired service data to the unique identifier by digitally signing the service data and associating the digital signature with the identifier stored on the client device 102. In a further embodiment, the processor 104 may be configured to link the acquired service data to the unique identifier by encoding the identifier in machine-readable formats that may be scanned by the client device 102 for verification of the service attributes.
[0033] The processor 104 may be configured to classify the acquired service data based on the service attributes. The service attributes may be, but not limited to, ownership details, a warranty information, a repair history, and so forth. The warranty information may be, but not limited to, from a service history of the electronic device 200, part replacements, authorized service information, a validity period, coverage details, an eligibility for transfer, and so forth. The repair history may be selected from a timestamp, service center details, type of parts used in repair, and so forth.
[0034] In an embodiment of the present invention, the processor 104 may be configured to classify the acquired service data based on ownership details by identifying previous and current owner credentials, transfer history, and associated authorization records. In another embodiment, the processor 104 may be configured to classify the acquired service data as warranty information by analyzing parameters such as validity period, coverage details, eligibility for transfer, and authorized service information. In yet another embodiment, the processor 104 may be configured to classify the acquired service data as repair history by organizing records according to the timestamp, the service center details, and the type of parts used in repair. In a further embodiment, the processor 104 may be configured to classify the acquired service data by applying rule-based algorithms that automatically separate ownership details, warranty information, and repair history into distinct categories for easier retrieval. In a further embodiment, the processor 104 may be configured to classify the acquired service data by tagging each entry with the predefined service attributes. The tags may be used to filter and retrieve data corresponding to ownership, warranty, or repair history.
[0035] The processor 104 may be configured to enable a verification of the classified service attributes of the electronic device 200 on the client device 102. In an embodiment of the present invention, the processor 104 may be configured to enable verification by authenticating the unique identifier of the electronic device 200 through public-key cryptography. The processor 104 may generate a digital signature linked to the service attributes, and the client device 102 may validate the authenticity of the service attributes using a corresponding public key. In yet another embodiment, the processor 104 may be configured to enable verification by computing a cryptographic hash of the service attributes and comparing the computed hash with a reference hash transmitted from the client device 102. Further, a match may confirm integrity of the service attributes. In a further embodiment, the processor 104 may be configured to establish a secure communication channel with the client device 102 using encryption protocols such as Secure Sockets Layer (SSL) or Transport Layer Security (TLS), thereby enabling trusted verification of the service attributes. The processor 104 may be configured to enable verification by issuing a digitally signed certificate of the service attributes that may be displayed on the client device 102 to confirm validity and authenticity.
[0036] The processor 104 may be configured to map the service attributes to the corresponding unique identifier linked with the classified service data. In an embodiment of the present invention, the processor 104 may be configured to map the service attributes to the corresponding unique identifier by creating an index table. Further, each of the classified service attributes may be associated with the unique identifier string, such as the quick response (QR) code or the near-field communication (NFC) tag. In another embodiment, the processor 104 may be configured to map the service attributes to the unique identifier by generating a relational data structure that links ownership details, warranty information, and repair history with the identifier assigned to the electronic device 200. In yet another embodiment, the processor 104 may be configured to map the service attributes to the unique identifier by embedding a hash of the classified attributes into the identifier string, thereby ensuring that the attributes can be verified against the identifier. In a further embodiment, the processor 104 may be configured to map the service attributes to the unique identifier by attaching digital signatures of the attributes to the identifier, enabling secure validation of ownership, warranty, and repair records. In a further embodiment, the processor 104 may be configured to map the service attributes to the unique identifier by assigning attribute tags that are encoded into machine-readable identifiers such as the quick response (QR) code or the near-field communication (NFC) tag, that may be scanned for retrieving linked service information.
[0037] The processor 104 may be configured to store the unique identifier and the corresponding linkage of the classified service data and the service attributes in the blockchain ledger 108 associated with the electronic device 200. In an embodiment of the present invention, the processor 104 may be configured to store the unique identifier and the linkage of the classified service data with the service attributes in the blockchain ledger 108 by creating a new transaction block that encapsulates the identifier and associated attributes. In another embodiment, the processor 104 may be configured to store the unique identifier and the linkage of the classified service data by encoding the information into a block header and committing the block to the blockchain ledger 108 through a consensus mechanism. In yet another embodiment, the processor 104 may be configured to store the unique identifier and the corresponding service attributes by generating a cryptographic hash of the data and appending it to the ledger as part of an immutable record. In another embodiment, the processor 104 may be configured to store the unique identifier and the service attributes linkage by executing a smart contract. The smart contract validates the data and records it permanently in the blockchain ledger 108. In another embodiment, the processor 104 may be configured to store the unique identifier along with the linked service attributes by distributing the record across multiple blockchain nodes to ensure decentralization, immutability, and fault tolerance.
[0038] The processor 104 may be configured to record subsequent ownership transfers of the electronic device 200 in the blockchain ledger 108. The processor 104 may be configured to update ownership transfer by generating a new entry with details of a new owner in the blockchain ledger 108. In an embodiment of the present invention, the processor 104 may be configured to update warranty records to reflect transfer of coverage to a new owner and may additionally support extension of warranty terms based on eligibility criteria defined by the manufacturer or authorized seller. In an embodiment of the present invention, the smart contracts 110 may be configured to notify users regarding warranty expiration, eligibility for extension, or transfer status. The notification may be delivered to the client device 102 through push alerts or email.
[0039] In an embodiment of the present invention, the blockchain ledger 108 may be adapted to store the unique identifier and the corresponding linkage of the classified service data and the service attributes. The blockchain ledger 108 may be decentralized to ensure tamper-proof storage of warranty, ownership, repair history, and so forth of the electronic device 200. The blockchain ledger 108 may be programmed with the smart contracts 110. The smart contracts 110 of the blockchain ledger 108 may be adapted to automatically update warranty coverage and notify the user regarding expiration or extension.
[0040] The blockchain ledger 108 may be, for example, but not limited to, a distributed database, a personal database, an end-user database, a commercial database, a Structured Query Language (SQL) database, a non-SQL database, an operational database, a relational database, an object-oriented database, a graph database, a cloud server database, and so forth. Embodiments of the present invention are intended to include or otherwise cover any type of the blockchain ledger 108, including known, related art, and/or later developed technologies.
[0041] Further, the blockchain ledger 108 may be implanted in a cloud server database, in an embodiment of the present invention. In an embodiment of the present invention, the cloud server may be remotely located. In an exemplary embodiment of the present invention, the cloud server may be a public cloud server. In another exemplary embodiment of the present invention, the cloud server may be a private cloud server. In yet another embodiment of the present invention, the cloud server may be a dedicated cloud server. The cloud server may be, but not limited to, a Microsoft Azure cloud server, an Amazon AWS cloud server, a Google Compute Engine (GCE) cloud server, an Amazon Elastic Compute Cloud (EC2) cloud server, and so forth. Embodiments of the present invention are intended to include or otherwise cover any type of the cloud server, including known, related art, and/or later developed technologies.
[0042] In an embodiment of the present invention, the communication network 112 may be adapted to establish a communicative link connecting the client device 102 to the application server 106. The communication network 112 may utilize one or more protocols, including LoRa for long-range low-power data exchange, Zigbee for mesh-based short-range connectivity, Bluetooth or Bluetooth Low Energy for local communication, Wi-Fi for high-bandwidth data transfer, and cellular standards such as 4G or 5G for wide-area coverage. The communication network 112 may be configured to dynamically select or switch among these protocols based on latency requirements, bandwidth availability, and energy constraints. The communication network 112 may further implement encryption schemes and secure authentication to safeguard transmitted data. In certain cases, adaptive routing or mesh topologies may be employed so that uninterrupted connectivity may be maintained between the client device 102 and the application server 106.
[0043] In an embodiment of the present invention, the storage medium 114 may comprise programming instructions executable by the processor 104. In an embodiment of the present invention, the storage medium 114 may store the computer programmable instructions in form of programming modules. The storage medium 114 may be a non-transitory storage medium, in an embodiment of the present invention. The storage medium 114 may communicate with the processor 104 and execute a computer-readable set of instructions present in storage medium 114, in an embodiment of the present invention.
[0044] The storage medium 114 may be, but not limited to, a Random-Access Memory (RAM), a Static Random-access Memory (SRAM), a Dynamic Random-access Memory (DRAM), a Read Only Memory (ROM), an Erasable Programmable Read-only Memory (EPROM), an Electrically Erasable Programmable Read-only Memory (EEPROM), a NAND Flash, a Secure Digital (SD) memory, a cache memory, a Hard Disk Drive (HDD), a Solid-State Drive (SSD) and so forth. Embodiments of the present invention are intended to include or otherwise cover any type of the storage medium 114, including known, related art, and/or later developed technologies.
[0045] FIG. 2 illustrates a schematic diagram of the system 100 for managing the electronic device 200, according to an embodiment of the present invention
[0046] In an exemplary scenario of the present invention, the system 100 may be configured to acquire the service data related to the electronic device 200 that may be a laptop device from the client device 102. The service data may include details of ownership transfers, authentication records, and user credentials. The system 100 may be configured to classify the service data into the service attributes representing ownership details such as previous owner information, transfer dates, and authorization status. The system 100 may be configured to link the ownership attributes with the unique identifier of the laptop, that may be encoded in a quick response (QR) code. The system 100 may be further configured to map the classified ownership attributes to the QR code and may store the linkage for later retrieval. The system 100 may be configured to enable verification of the ownership attributes on the client device 102, thereby allowing a prospective buyer to confirm lawful ownership before purchase.
[0047] In another exemplary scenario of the present invention, the electronic device 200 may be a smartphone device that may have an active but soon-to-expire warranty. The system 100 may be configured to acquire the service data from the client device 102 related to the electronic device 200. The service data may include warranty terms, purchase date, and seller details. The system 100 may be configured to classify the service data into warranty-related service attributes, including validity period, coverage details, eligibility for transfer, and authorized service information. The system 100 may be configured to link the warranty attributes to the smartphone’s unique identifier, that may be encoded in a near-field communication (NFC) tag. The system 100 may be configured to map the classified warranty attributes to the identifier and may store the linkage for secure access. The system 100 may be configured to enable verification of the warranty attributes on the client device 102, while smart contracts 110 may be configured to notify the smartphone owner regarding warranty expiration or eligibility for extension.
[0048] In yet another exemplary scenario of the present invention, the electronic device 200 may be a tablet device that may have undergone multiple repairs. The system 100 may be configured to acquire the service data related to the electronic device 200 from the client device 102. The service data may include repair logs, service center details, and parts replaced. The system 100 may be configured to classify the acquired service data into repair-related service attributes such as timestamps of repair, service provider identification, and type of part replacements. The system 100 may be configured to link the repair attributes with the tablet’s unique identifier, that may be encoded in the QR code or the NFC tag. The system 100 may be configured to map the classified repair attributes to the identifier and may store the linkage for later reference. The system 100 may be further configured to enable verification of repair history attributes on the client device 102, thereby providing transparency regarding the device’s service condition to a buyer or technician.
[0049] FIG. 3 depicts a flowchart of a method 300 for managing the electronic device 200 using the system 100, according to an embodiment of the present invention.
[0050] At step 302, the system 100 may acquire the service data related to the electronic device 200 from the client device 102. The acquired service data may be linked to the unique identifier.
[0051] At step 304, the system 100 may classify the acquired service data based on the service attributes. The service attributes may be, but not limited to, the ownership details, the warranty information, the repair history, and so forth.
[0052] At step 306, the system 100 may map the service attributes to the corresponding unique identifier linked with the classified service data.
[0053] At step 308, the system 100 may store the unique identifier and the corresponding linkage of the classified service data and the service attributes in the blockchain ledger 108 associated with the electronic device 200.
[0054] While the invention has been described in connection with what is presently considered to be the most practical and various embodiments, it is to be understood that the invention is not to be limited to the disclosed embodiments, but on the contrary, is intended to cover various modifications and equivalent arrangements included within the scope of the appended claims.
[0055] This written description uses examples to disclose the invention, including the best mode, and also to enable any person skilled in the art to practice the invention, including making and using any device or systems and performing any incorporated methods. The patentable scope of the invention is defined in the claims, and may include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements within substantial differences from the literal languages of the claims. , Claims:CLAIMS
I/We Claim:
1. A blockchain based system (100) for managing an electronic device (200), the system (100) comprising:
a processor (104), operably in communication with a client device (102) through a communication network (112), characterized in that the processor (104) is configured to:
acquire a service data related to the electronic device (200) from the client device (102), wherein the acquired service data is linked to a unique identifier;
classify the acquired service data based on service attributes, wherein the service attributes are selected from ownership details, a warranty information, a repair history, or a combination thereof;
map the service attributes to the corresponding unique identifier linked with the classified service data; and
store the unique identifier and the corresponding linkage of the classified service data and the service attributes in a blockchain ledger (108) associated with the electronic device (200).
2. The system (100) as claimed in claim 1, wherein the processor (104) is configured to enable a verification of service attributes of the electronic device (200) on the client device (102).
3. The system (100) as claimed in claim 1, wherein the unique identifier is a string of characters encoded in a quick response (QR) code, a near-field communication (NFC) tag, or a combination thereof.
4. The system (100) as claimed in claim 1, wherein the blockchain ledger (108) is decentralized to ensure tamper-proof storage of warranty, ownership, repair history, or a combination thereof.
5. The system (100) as claimed in claim 1, wherein the blockchain ledger (108) is programmed with smart contracts (110) adapted to automatically update warranty coverage and notify users regarding expiration or extension.
6. The system (100) as claimed in claim 1, wherein the processor (104) is configured to record subsequent ownership transfers of the electronic device (200) in the blockchain ledger (108).
7. The system (100) as claimed in claim 1, wherein the processor (104) is configured to update ownership transfer by generating a new entry with details of a new owner in the blockchain ledger (108).
8. The system (100) as claimed in claim 1, wherein the warranty information is selected from a service history of the electronic device (200), part replacements, authorized service information, a validity period, coverage details, an eligibility for transfer, or a combination thereof.
9. The system (100) as claimed in claim 1, wherein the repair history selected from a timestamp, service center details, type of parts used in repair, or a combination thereof.
10. A method (300) for managing an electronic device (200), the method (300) is characterized by steps of:
acquiring a service data related to the electronic device (200) from a client device (102), wherein the acquired service data is linked to a unique identifier;
classifying the acquired service data based on service attributes, wherein the service attributes are selected from ownership details, a warranty information, a repair history, or a combination thereof;
mapping the service attributes to the corresponding unique identifier linked with the classified service data; and
storing the unique identifier and the corresponding linkage of the classified service data and the service attributes in a blockchain ledger (108) associated with the electronic device (200).

Date: October 09, 2025
Place: Noida

Nainsi Rastogi
Patent Agent (IN/PA-2372)
Agent for the Applicant