Description:TECHNICAL FIELD
[0001] The present disclosure relates generally to the field of IOT devices, and more particularly to a system and a method for secure delivery authentication in a smart doorbell environment.
BACKGROUND
[0002] With the exponential growth of e-commerce platforms and online shopping, home package deliveries have become increasingly frequent, creating substantial operational challenges for logistics companies and security concerns for consumers. The modern delivery systems have attempted to address authentication requirements through various technological approaches. Traditional doorbells offer limited functionality, typically restricted to audio alerts and push-button visitor notifications, without any digital authentication capabilities. The smart doorbells have introduced several improvements, including video monitoring, Wireless Fidelity (Wi-Fi) connectivity, mobile app integration, motion detection, cloud-based video storage, and two-way audio communication.
[0003] Conventionally, existing delivery authentication methods face significant challenges in providing reliable, secure, and cost-effective verification systems for package deliveries. The traditional approaches require customers to be physically present with mobile devices during delivery windows, creating inconvenience and limiting delivery flexibility. The current systems lack integrated visual verification capabilities, preventing recipients from confirming the delivery personnel's identity before authorizing package handover. The existing authentication mechanisms demonstrate dependency on external network infrastructure, making them vulnerable to service disruptions and connectivity issues that can delay or prevent successful delivery completion.
[0004] However, conventional delivery authentication systems suffer from multiple technical limitations that create substantial operational and security challenges. The network dependency issues arise where authentication failures occur due to poor connectivity or service disruptions, resulting in delayed or incomplete delivery verification processes. The availability problems emerge when household members are unavailable during delivery attempts, leaving the delivery personnel without means to obtain proper authentication codes, leading to failed deliveries and rescheduling inefficiencies. The security vulnerabilities manifest through interception possibilities, unauthorized access risks, compromised authentication channels, and potential misuse of authentication codes by the delivery personnel who may share or inappropriately use verification credentials for unauthorized purposes. The operational inefficiencies emerge through high transmission costs for delivery companies, excessive dependency on external network infrastructure, and a lack of real-time verification capabilities that impede efficient delivery operations. User inconvenience factors include mandatory requirements for recipients to maintain constant availability with communication devices during delivery windows, difficulties in coordinating authentication among multiple household members, absence of visual verification mechanisms for confirming delivery personnel identity, and lack of control mechanisms to prevent authentication code misuse or unauthorized sharing.. Consequently, there exists a technical problem of establishing secure, efficient, and user-friendly delivery authentication systems that eliminate SMS dependency while providing enhanced security measures, reducing operational costs for delivery companies, and improving overall user experience during package delivery processes. Additional technical challenges include developing reliable local authentication mechanisms that function independently of mobile network availability, creating seamless integration between physical delivery processes and digital verification systems, and implementing cost-effective solutions that benefit both delivery companies and end consumers.
[0005] Therefore, in light of the foregoing discussion, there exists a need to overcome the aforementioned drawbacks of the conventional delivery systems.
SUMMARY
[0006] The present disclosure provides a system and a method for secure delivery authentication in a smart doorbell environment. The present disclosure provides a solution to the technical problem of establishing secure, efficient, and user-friendly delivery authentication systems that eliminate SMS dependency while providing enhanced security measures, reducing operational costs for delivery companies, and improving overall user experience during package delivery processes. An aim of the present disclosure is to provide a solution that overcomes at least partially the problems encountered in the prior art and provides an improved delivery authentication system that eliminates SMS dependency while enhancing security through two-factor authentication, reduces operational costs through cloud-based OTP management, enables real-time video communication between visitors and remote users, and offers personalized user interface capabilities with customizable aesthetics.
[0007] One or more objectives of the present disclosure is achieved by the solutions provided in the enclosed embodiments. Advantageous implementations of the present disclosure are further defined in the enclosed embodiments.
[0008] In one aspect, the present disclosure provides a system for secure delivery authentication in smart doorbell environments, the system comprising a server comprising a processor configured to receive delivery order identifier data from a smart doorbell device, wherein the delivery order identifier data comprises scanned order information, validate the delivery order identifier data against stored delivery information, receive an One-Time Password (OTP) corresponding to the validated delivery order identifier, encrypt the OTP and transmit the encrypted OTP to the smart doorbell device, receive authentication confirmation from the smart doorbell device, and log delivery confirmation events after successful OTP verification by delivery personnel, the smart doorbell device comprising a device processor configured to control a barcode scanning module to capture delivery order identifiers from delivery documentation, wherein the barcode scanning module comprises a camera module with barcode decoding capabilities, transmit the captured order identifier data to the server, receive and store the encrypted OTP from the server in local memory without displaying it on a display unit, detect authentication events when a contactless authentication card is presented to a proximity reader and the authentication events comprise card identification data. Furthermore, the system is configured to verify the authentication events against encrypted pre-stored household authentication data stored in the device processor, decrypt and display the OTP on the display unit of the smart doorbell device for a predetermined time period only upon successful verification of the authentication events. Moreover, the OTP expires after successful verification and return to an idle state after OTP display and the idle state comprises displaying customizable wallpaper content.
[0009] The disclosed system for secure delivery authentication in smart doorbell environments, structured to provide secure and efficient package verification. The server performs validation of scanned order identifiers against stored delivery records, ensuring accurate matching between packages and intended recipients, thereby minimising the likelihood of fraudulent or misrouted deliveries. The receive and encryption of an OTP on the server enhances data protection during transmission, preventing unauthorised interception of sensitive authentication credentials. The logging of delivery confirmation events offers traceable records for users and delivery services, supporting accountability and system transparency. Further, the system includes the smart doorbell device, which incorporates the barcode scanning module that enables rapid and contactless order identification, enhancing operational efficiency and eliminating the requirement for manual data entry. The captured order data is transmitted securely to the server, and the encrypted OTP is stored locally without being displayed, protecting access information until resident verification is completed. The proximity reader enables contactless local authentication by requiring the presence of an authorised household member. The verification of card credentials against pre-stored authentication data ensures that the OTP is accessible only upon valid local authentication. Once verified, the OTP is decrypted and displayed on the display unit for a predefined duration, after which it automatically expires to prevent reuse or unauthorised access. The smart doorbell device then transitions to an idle state, presenting user-defined wallpaper content to maintain an aesthetically pleasing and personalised user interface. The integration of encrypted OTP handling, contactless local authentication, and user-centric design results in a robust, privacy-preserving, and network-independent alternative to conventional SMS-based delivery verification systems.
[0010] In another aspect, the present disclosure provides a method for implementing secure delivery authentication using a smart doorbell system, the method comprising receiving delivery order identifier data from a barcode scanning module of a smart doorbell device, where the barcode scanning module comprises a camera module with barcode decoding capabilities, transmitting the delivery order identifier data to a server, validating the delivery order identifier data at the server against stored delivery information, receiving a One-Time Password (OTP) corresponding to the validated delivery order identifier at the server, encrypting the OTP and transmitting the encrypted OTP to the smart doorbell device, storing the encrypted OTP in local memory without displaying it on a display unit, detecting authentication events when a contactless authentication card is presented to a proximity reader, verifying the authentication events against encrypted pre-stored household authentication data, decrypting and displaying the OTP on the display unit for a predetermined time period only upon successful verification of the authentication events. Moreover, the OTP expires after successful verification and maintaining a secure log of all delivery authentication attempts at the server.
[0011] The method for implementing secure delivery authentication using a smart doorbell system manifests all the advantages and technical effects of the system of the present disclosure.
[0012] It is to be appreciated that all the aforementioned implementation forms can be combined.
[0013] It has to be noted that all devices, elements, circuitry, units and means described in the present application could be implemented in the software or hardware elements or any kind of combination thereof. All steps which are performed by the various entities described in the present application as well as the functionalities described to be performed by the various entities are intended to mean that the respective entity is adapted to or configured to perform the respective steps and functionalities. Even if, in the following description of specific embodiments, a specific functionality or step to be performed by external entities is not reflected in the description of a specific detailed element of that entity which performs that specific step or functionality, it should be clear for a skilled person that these methods and functionalities can be implemented in respective software or hardware elements, or any kind of combination thereof. It will be appreciated that features of the present disclosure are susceptible to being combined in various combinations without departing from the scope of the present disclosure as defined by the embodiments.
[0014] Additional aspects, advantages, features, and objects of the present disclosure would be made apparent from the drawings and the detailed description of the illustrative implementations construed in conjunction with the embodiments that follow.
BRIEF DESCRIPTION OF THE DRAWINGS
[0015] The summary above, as well as the following detailed description of illustrative embodiments, is better understood when read in conjunction with the appended drawings. For the purpose of illustrating the present disclosure, exemplary constructions of the disclosure are shown in the drawings. However, the present disclosure is not limited to specific methods and instrumentalities disclosed herein. Moreover, those in the art will understand that the drawings are not to scale. Wherever possible, like elements have been indicated by identical numbers.
[0016] Embodiments of the present disclosure will now be described, by way of example only, with reference to the following diagrams wherein:
FIG. 1 is a block diagram of a system for secure delivery authentication in smart doorbell environments, in accordance with an embodiment of the present disclosure;
FIG. 2A and 2B collectively are flowcharts of a method for implementing secure delivery authentication using a smart doorbell system, in accordance with an embodiment of the present disclosure;
FIG. 3 is a process for implementing secure delivery authentication using a smart doorbell system, in accordance with an embodiment of the present disclosure;
FIG. 4 illustrates an exploded view of a smart doorbell device, in accordance with an embodiment of the present disclosure; and
FIG. 5 is a diagram of a user interface of a mobile application associated with a smart doorbell device, in accordance with an embodiment of the present disclosure.
[0017] In the accompanying drawings, an underlined number is employed to represent an item over which the underlined number is positioned or an item to which the underlined number is adjacent. A non-underlined number relates to an item identified by a line linking the non-underlined number to the item. When a number is non-underlined and accompanied by an associated arrow, the non-underlined number is used to identify a general item at which the arrow is pointing.
DETAILED DESCRIPTION OF EMBODIMENTS
[0018] The following detailed description illustrates embodiments of the present disclosure and ways in which they can be implemented. Although some modes of carrying out the present disclosure have been disclosed, those skilled in the art would recognize that other embodiments for carrying out or practicing the present disclosure are also possible.
[0019] FIG. 1 is a block diagram of a system for secure delivery authentication in smart doorbell environments, in accordance with an embodiment of the present disclosure. With reference to FIG. 1, there is shown a block diagram of a system 100 for secure delivery authentication in smart doorbell environments. The system 100 includes a server 102 and a smart doorbell device 108, which comprises a device processor 110, a barcode scanning module 112, a housing 114, a display unit 116, a proximity reader 118, and a video communication module 120. Further, the barcode scanning module 112 comprises a camera module 128 and the proximity reader 118 comprises a Near Field Communication (NFC) reader 130.
[0020] The disclosed system 100 provides significant technical improvements over conventional delivery authentication methods. Unlike SMS-based systems that depend on cellular network availability, the present disclosure operates independently of mobile network infrastructure through local authentication mechanisms. The system eliminates per-transaction SMS transmission costs for delivery companies while reducing authentication time through local processing compared to remote SMS delivery and manual entry processes. The dual-factor authentication approach of combining order scanning with household verification provides enhanced security compared to single-factor SMS verification methods. The system supports multiple household members through individual authentication cards, overcoming the limitation of single mobile number dependency in conventional SMS-based systems.
[0021] The server 102 may be referred to as the central computing system responsible for managing data exchange, processing logic, and enabling communication between the smart doorbell device and associated user platforms. The server 102 may perform functions such as receiving inputs, executing logic operations, storing data, generating outputs, and transmitting responses to client devices. The server 102 may be implemented as a physical machine, virtualised environment, or cloud-based infrastructure. Examples of the server 102 may include, but are not limited to, cloud-hosted web servers, dedicated physical servers, edge computing nodes, Virtual Private Servers (VPS), on-premise enterprise servers, and distributed computing platforms. The server 102 may be configured to run server-side software or services, including but not limited to databases, authentication modules, encryption engines, APIs, application logic layers, or delivery management systems.
[0022] The processor 104 may be referred to as the processing unit embedded within the server 102, configured to control, manage, and execute the core computational functions required for server operations. The processor 104 enables the server 102 to perform tasks such as receiving and validating data, executing authentication algorithms, encrypting sensitive information, managing database operations, and handling communication protocols with external devices. Examples of the processor 104 may include, but are not limited to, microcontrollers, Digital Signal Processors (DSPs), Central Processing Units (CPUs), Application-Specific Integrated Circuits (ASICs), System-on-Chip (SoC) platforms, or Programmable Logic Controllers (PLCs).
[0023] The network interface 106 may be referred to as a communication component of the server 102, configured to enable data exchange between the server and external devices such as the smart doorbell device 108 and connected user platforms. The network interface 106 facilitates wired or wireless communication over local or wide-area networks using standard protocols. Examples of the network interface 106 may include, but are not limited to, Ethernet ports, Wi-Fi modules, cellular modems, or cloud-based API gateways, which are selected based on bandwidth requirements, latency tolerance, and the deployment environment.
[0024] The smart doorbell device 108 may be referred to as an interactive, network-enabled hardware unit configured to facilitate secure delivery authentication, user interaction, and real-time communication at an entry point. The smart doorbell device 108 may include components such as the display unit 116, the barcode scanning module 112, the video communication module 120, the proximity reader 118, and wireless communication interfaces. In an implementation, the smart doorbell device 108 may be installed at residential or commercial entryways and may operate in coordination with a mobile application and cloud infrastructure to enhance delivery security, user convenience, and real-time access control.
[0025] The device processor 110 may be referred to as the control and processing unit integrated within the smart doorbell device 108, configured to manage and execute the device’s operational functions. The device processor 110 is responsible for coordinating tasks, such as capturing and decoding delivery order identifiers, managing communication with the server 102, processing the authentication events via the NFC 130, and controlling the display unit 116 to display information such as OTPs and user-defined content. Examples of the device processor 110 may include, but are not limited to, microcontrollers, SoC platforms, embedded processors, or ASICs. The device processor 110 may operate in conjunction with onboard memory and firmware to ensure secure, real-time processing of data, seamless user interaction.
[0026] The barcode scanning module 112 may be referred to as an integrated hardware and software component arranged within the smart doorbell device 108, configured to capture and interpret machine-readable delivery order identifiers such as barcodes or QR codes. The barcode scanning module 112 may include, but is not limited to, a dedicated barcode sensor, an imaging camera with decoding software, or a multifunctional camera module configured with optical recognition capabilities.
[0027] The housing 114 may be referred to as the outer structural enclosure of the smart doorbell device 108, configured to protect and support the internal electronic components while providing an aesthetically suitable interface for user interaction. The housing 114 may be designed to accommodate elements such as the display unit 116, the camera module 128, the barcode scanning module 112, the proximity reader 118, and the video communication module 120 assembly in a compact and weather-resistant form factor. Materials used in the housing 114 may include, but are not limited to, polycarbonate, ABS plastic, metal alloys, or composite materials, selected for durability, heat resistance, and outdoor suitability.
[0028] The display unit 116 may be referred to as the visual interface component of the smart doorbell device 108, configured to present information and enable user interaction during delivery authentication and other operational states. The display unit 116 may be used to show OTPs, scanned order details, user greetings, live video feeds, and customizable content such as wallpapers or system notifications. Examples of the display unit 116 may include, but are not limited to, touchscreen Liquid Crystal Displays (LCDs), Organic Light Emitting Diodes (OLED) panels, or e-ink displays, selected based on power efficiency, resolution requirements, and environmental durability.
[0029] The proximity reader 118 may be referred to as a contactless sensing component integrated within the smart doorbell device 108, configured to detect and authenticate nearby identification devices such as NFC cards or Radio Frequency Identification (RFID) cards. The proximity reader 118 enables secure, resident verification by detecting card presence within a defined sensing range and transmitting the card identification data to the device processor 110 for authentication. Examples of the proximity reader 118 may include, but are not limited to, embedded NFC modules, RFID readers, or short-range wireless authentication sensors, designed for low-latency and tamper-resistant communication.
[0030] The video communication module 120 is configured to facilitate real-time visual interaction between a visitor and a remote user. The video communication module 120 enables two-way video calling by capturing, encoding, transmitting, and receiving audiovisual data over a network connection. The video communication module 120 may include, but is not limited to, a front-facing camera, a microphone, a speaker, video compression hardware, and communication interfaces such as Wi-Fi or Bluetooth.
[0031] The wide-angle camera 122 may be referred to as an imaging component of the video communication module 120, configured to capture a broad field of view for enhanced visual coverage at the entry point where the smart doorbell device 108 is installed. The wide-angle camera 122 is configured to provide comprehensive monitoring by capturing clear video footage of visitors, packages, and surrounding areas, reducing blind spots and improving overall situational awareness. Examples of the wide-angle camera 122 may include, but are not limited to, High-Definition (HD) cameras, ultra-wide lens modules, fisheye cameras, or low-light enhanced sensors, selected based on image clarity, viewing angle, and environmental performance.
[0032] The microphone 124 may be referred to as an audio input component of the video communication module 120, configured to capture sound from the environment surrounding the smart doorbell device 108. The microphone 124 enables real-time audio transmission, allowing visitors such as delivery personnel to communicate verbally with residents through a connected mobile application or cloud interface. Examples of the microphone 124 may include, but are not limited to, omnidirectional microphones, noise-cancelling microphones, Micro-Electro-Mechanical Systems (MEMS) microphones, or digital condenser microphones, selected based on sensitivity, clarity, and environmental noise handling.
[0033] The NFC reader 130 may be referred to as a short-range wireless communication component of the proximity reader 118, configured to enable secure, contactless data exchange between the smart doorbell device 108 and authorised identification devices such as access cards or smartphones. The NFC reader 130 operates over a limited range, typically within a few centimetres, to detect and read embedded identification data from NFC-enabled devices presented by residents for local authentication. Examples of the NFC reader 130 may include, but are not limited to, NFC transceivers, passive or active NFC tags, and secure element-enabled NFC modules, selected based on data security, transmission speed, and power efficiency.
[0034] In operation, the processor 104 is configured to receive delivery order identifier data from the smart doorbell device 108, where the delivery order identifier data comprises scanned order information. The smart doorbell device 108 captures the delivery order identifier using an integrated barcode or QR code scanner from package labels. In an example, the scanned information includes but is not limited to a name of a person, the cost of an article, the address of a person, a delivery partner, and the like. In an implementation, the scanned order information is pre-processed and is sent to the server 102. Thereafter, the processor 104 receives the scanned order information, initiating the backend process of verifying the scanned order information against stored delivery information in order to ensure an improved delivery of a product.
[0035] Further, the processor 104 is configured to validate the delivery order identifier data against stored delivery information to confirm the authenticity of the delivery before proceeding with any further authentication or OTP generation. The processor 104 accesses a secure database or delivery record system (such as Advanced Encryption Standard (AES) 256) that stores valid delivery information linked to user accounts. Upon receiving the delivery order identifier data, the processor 104 compares the received delivery order identifier data with the stored delivery information in order to identify a match. The matching process may involve matching order number, user ID association, timestamp, or delivery statuses. If a valid match is found, the processor 104 confirms the legitimacy of the delivery, allowing the system 100 to proceed with secure authentication operations, such as OTP generation or video communication initiation.
[0036] Further, the processor 104 receives an One-Time Password (OTP) corresponding to the validated delivery order identifier. After successful validation of the delivery order identifier data, the processor 104 utilizes an internal algorithm or secure logic to generate an OTP. In an implementation, the OTP refers to a randomly generated numeric or alphanumeric string with a limited validity period, which is associated with the specific delivery transaction and temporarily stored in the system 100, to be later transmitted to or displayed by the smart doorbell device 108 upon successful local authentication.
[0037] Further, the processor 104 is configured to encrypt the OTP and transmit the encrypted OTP to the smart doorbell device 108. Once the processor 104 receives the OTP, thereafter, the processor 104 is configured to apply an encryption algorithm, such as Advanced Encryption Standard (AES) or another cryptographic protocol, to convert the plain-text OTP into a secure and encoded format. The encrypted OTP is then sent over a secure communication channel to the smart doorbell device 108, which is configured to store the encrypted OTP in local memory without displaying the OTP to a delivery operator until the required local authentication (e.g., NFC card verification) is completed.
[0038] Further, the processor 104 receives authentication confirmation from the smart doorbell device 108. After receiving the encrypted OTP from the server 102, the smart doorbell device 108 stores it without displaying it. The smart doorbell device 108 then waits for a local authentication event, such as a household member presenting a registered NFC card to the proximity reader 118. Upon successful verification by the device processor 110, comparing the NFC card data with pre-stored authentication information, the smart doorbell device 108 sends a digital confirmation signal back to the processor 104. The confirmation signal may include metadata such as a timestamp, device ID, and authentication status.
[0039] Further, the processor 104 is configured to log delivery confirmation events after successful OTP verification by delivery personnel. Once the delivery personnel views and inputs the correct OTP, displayed on the smart doorbell device 108 after local authentication, the smart doorbell device 108 transmits a verification signal back to the server 102. The processor 104 receives the verification signal and interprets it as a successful OTP match, confirming that the delivery has been authenticated at the door. After that, the processor 104 generates a digital log entry, which may include details, such as the timestamp of the event, the associated delivery order identifier, device ID, and authentication status.
[0040] Further, the smart doorbell device 108 includes the device processor 110, which is configured to control the barcode scanning module 112 to capture delivery order identifiers from delivery documentation, where the barcode scanning module 112 comprises the camera module 128 with barcode decoding capabilities. The device processor 110 activates and manages the barcode scanning module 112, which includes the camera module 128. When delivery documentation containing a barcode or QR code is presented, the camera module 128 captures an image the barcode or QR code printed on the delivery label or packaging slip and processes it using integrated decoding software to extract the delivery order identifier. The decoded data is then used in subsequent authentication steps, including validation by the server 102. The integration of camera-based scanning and automated decoding enables fast, contactless, and error-free acquisition of delivery data, forming a critical input for the secure authentication workflow of the system 100.
[0041] Further, the device processor 110 is configured to transmit the captured order identifier data to the server 102. After the barcode scanning module 112, controlled by the device processor 110, captures and decodes the delivery order identifier from the delivery documentation, the device processor 110 formats the data and establishes a secure connection to the server 102 through the network interface 106. Using communication protocols supported by the system 100, the device processor 110 transmits the order identifier data for server-side validation. The real-time data exchange enables the server 102 to confirm the order details and proceed with the next steps in the authentication workflow, such as receiving OTP and delivery logging.
[0042] Further, the device processor 110 receives and stores the encrypted OTP from the server 102 in local memory without displaying it on the display unit 116. Once the server 102 validates the delivery order identifier and receives the OTP, the processor 104 encrypts the OTP and transmits it to the smart doorbell device 108 via the network interface. Upon receipt, the device processor 110 stores the encrypted OTP in local memory, keeping it hidden from the display unit 116. The OTP remains inaccessible until the smart doorbell device detects and verifies a valid local authentication event, such as a registered NFC card presented to the proximity reader 118. Only upon successful verification will the OTP be decrypted and displayed, ensuring secure and conditional access to sensitive delivery authentication data.
[0043] Further, the device processor 110 detects authentication events when a contactless authentication card is presented to the proximity reader 118, where the authentication events comprise card identification data. The proximity reader 118, integrated into the smart doorbell device 108, continuously monitors for the presence of a contactless authentication card, such as an NFC-enabled card. When a card is brought within the detection range, the proximity reader 118 captures the card’s identification data and sends it to the device processor 110. The device processor 110 interprets this input as an authentication event and uses the card ID to initiate a verification process against pre-stored authorized credentials.
[0044] Further, the device processor 110 verifies the authentication events against encrypted pre-stored household authentication data stored in the device processor 110. When the proximity reader 118 detects a contactless card, it sends the card identification data to the device processor 110. The device processor 110 then decrypts and compares the card identification data with a pre-stored set of household authentication credentials that were securely programmed into the system during setup or enrolment. The authentication data is encrypted to prevent tampering or unauthorized extraction. If the card ID matches an entry in the stored credentials, the authentication is deemed successful, allowing the smart doorbell device 108 to proceed with actions such as OTP decryption and display.
[0045] Further, the device processor 110 decrypts and displays the OTP on the display unit 116 of the smart doorbell device 108 for a predetermined time period such as, for example, 5 seconds, 30 seconds, or 2 minutes only upon successful verification of the authentication events, where the OTP expires after successful verification. Once the device processor 110 receives authentication confirmation, such as a valid NFC card match, the device processor 110 proceeds to decrypt the previously stored encrypted OTP using embedded decryption logic. The decrypted OTP is then shown on the display unit 116 for a predefined duration, such as a few seconds or minutes. During this window, the delivery personnel can use the OTP for verification purposes. After the OTP is used or the time window lapses, the device processor 110 automatically removes the OTP from the display unit 116 and marks it as expired in the system 100.
[0046] The system 100 is configured to provide continued functionality during cellular tower maintenance, natural disasters, or network congestion events that commonly disrupt SMS-based authentication. The local storage and processing architecture eliminates latency associated with remote server communications, providing consistent performance regardless of internet connection quality. The power consumption optimization allows the smart doorbell device 108 to operate on battery backup for up to 72 hours during power outages, with active mode consumption of 2.5 watts and standby mode consumption of 0.3 watts. The weatherproof housing 114 maintains an IP65 rating for protection against dust and water ingress, with an operational temperature range from -20°C to +60°C, suitable for diverse climatic conditions.
[0047] Further, the device processor 110 returns to an idle state after OTP display, where the idle state comprises displaying customizable wallpaper content. Following successful OTP display and subsequent expiration, the device processor 110 clears the OTP from the display unit 116 and activates the idle state. During the idle state, the display unit 116 is configured to show wallpaper content, which may be pre-selected or uploaded by the user through a connected mobile application. The wallpaper may include static images, time, weather information, or personalized greetings. The idle state ensures the smart doorbell device 108 remains responsive while minimizing unnecessary power consumption and preventing unintended interaction, keeping the smart doorbell ready for the next delivery or visitor interaction.
[0048] In accordance with an embodiment, the device processor 110 is further configured to generate error notifications for invalid authentication attempts, display error messages on the display unit 116 for failed contactless authentication card verification and transmit authentication failure alerts to the server 102. When a contactless authentication card is presented to the proximity reader 118, the device processor 110 compares the captured card identification data with pre-stored encrypted household authentication data. If the data does not match any authorized record, the device processor 110 recognizes the invalid authentication attempts. The device processor 110 then triggers an error notification, which is displayed on the display unit 116 in the form of a predefined error message indicating failed authentication. Simultaneously, the device processor 110 sends an alert to the server 102 containing relevant details such as timestamp, device ID, and nature of the failure. By transmitting the authentication failure alerts to the server 102 ensures that failed attempts are logged and monitored, enabling real-time security tracking and post-event analysis for potential misuse or system anomalies.
[0049] In accordance with an embodiment, the error notifications comprise any of timeout alerts for expired authentication attempts, invalid card format warnings, and network connectivity failure messages. The device processor 110 monitors the entire authentication process and identifies specific failure conditions. If an authentication session exceeds a preset time limit without successful card verification, the device processor 110 triggers a timeout alert and displays a corresponding message on the display unit 116. If a contactless card is presented but does not conform to supported formats or standards, the device processor 110 identifies it as an invalid card and generates a warning. Additionally, if the device processor 110 cannot communicate with the server 102 due to network issues, the device processor 110 detects the connectivity failure and displays a message accordingly. Each of the alerts (i.e., timeout alerts for expired authentication attempts, invalid card format warnings, and network connectivity failure messages) may also be transmitted to the server 102 for remote logging and monitoring, ensuring that both local users and system administrators are promptly informed of any disruptions in the authentication workflow
[0050] In accordance with an embodiment, the smart doorbell device 108 further comprises the video communication module 120 operatively connected to the device processor 110, the video communication module 120 configured to establish encrypted two-way video communication between a delivery person at the smart doorbell device 108 and a user mobile device through the server 102, capture video data of delivery personnel during order scanning, and transmit the video data to the server 102 for relay to the user mobile device. When delivery personnel approaches the smart doorbell device 108, the device processor 110 activates the video communication module 120. The wide-angle camera 122 captures video data, while the microphone 124 and speaker 126 support real-time audio exchange. The device processor 110 encrypts the audiovisual data stream and transmits it to the server 102 using the network interface 106. The server 102 acts as an intermediary, securely relaying the data to the user mobile device. During the order scanning process, the video communication module 120 also records or streams footage to ensure the entire interaction is visually documented. The encrypted communication ensures that all transmitted data remains protected against unauthorized access, maintaining user privacy and integrity of the system 100, while enabling live engagement between the resident and the delivery personnel.
[0051] In accordance with an embodiment, the video communication module 120 comprises the wide-angle camera 122 with a field of view between 120 to 160 degrees positioned behind the display unit 116 and the microphone 124 for audio capture, and the speaker 126 for audio output. When a delivery event is triggered, such as when a delivery personnel approaches or begins scanning a package, the video communication module 120 activates. The wide-angle camera 122, positioned behind the transparent or semi-transparent section of the display unit 116, captures live video within a 120 to 160-degree field of view. The microphone 124 collects surrounding audio, including speech from the delivery personnel, while the speaker 126 allows the delivery personnel to hear audio messages from the user. The wide-angle camera 122, the microphone 124, and the speaker 126, work in coordination with the device processor 110 to encode and stream the audiovisual data through the server 102 to the user mobile device.
[0052] In accordance with an embodiment, the proximity reader 118 comprises the NFC reader 130 compatible with contactless authentication cards. The NFC reader 130, embedded within the proximity reader 118, continuously scans for nearby NFC-compatible authentication cards. When a valid authentication card is brought within range, the NFC reader 130 captures the unique card identification data and transmits it to the device processor 110. The device processor 110 then verifies the card identification data against encrypted, pre-stored household authentication credentials. If a match is found, the system 100 proceeds to decrypt and display the OTP or authorize other delivery-related actions. The NFC reader 130 supports standardized protocols to ensure interoperability with a variety of commercially available contactless cards, allowing for seamless and secure resident authentication in the delivery authentication workflow.
[0053] In accordance with an embodiment, the device processor 110 is further configured to generate a data repository of authorised contactless authentication cards, update the data repository through a connected mobile application, and compare presented card identification data with the authorized card data stored in the data repository. The device processor 110 stores a list of card identification data corresponding to authorized contactless authentication cards in a secure, locally maintained data repository. The data repository can be updated through the connected mobile application, which communicates securely with the smart doorbell device 108 over the network interface 106. When the authorised contactless authentication card is presented to the proximity reader 118, the device processor 110 receives the card ID and compares it against the entries stored in the data repository. If a match is found, the authentication is confirmed, and the device processor 110 proceeds with authorized actions such as OTP decryption or video call initiation. If no match is found, the device processor 110 treats the attempt as invalid and may trigger an error notification.
[0054] In accordance with an embodiment, upon determining that the presented contactless authentication card does not match with authorized card data stored in the data repository, the device processor 110 is configured to generate an unauthorized access alert, transmit the unauthorized access alert to the server 102, and lock the smart doorbell device 108 from further authentication attempts for a predetermined time period, where the server 102 is further configured to transmit the unauthorized access alert to the user mobile application. When the contactless authentication card is presented, the proximity reader 118 captures the card’s identification data and forwards it to the device processor 110. The device processor 110 then compares the card’s identification data against the list of authorized entries stored in the data repository. If no match is found, the device processor 110 recognizes the attempt as unauthorized and generates an alert message detailing the failed attempt. The alert is transmitted to the server 102 via the network interface 106. The device processor 110 simultaneously activates a lockout function, disabling further card scans or authentication attempts at the smart doorbell device 108 for a predetermined duration (e.g., 30 seconds or 2 minutes), effectively mitigating the risk of brute-force attacks. Upon receiving the alert, the server 102 relays the message to the user’s mobile application, which may display a push notification containing the time, location, and nature of the unauthorized event.
[0055] In accordance with an embodiment, the smart doorbell device 108 further comprises the housing 114 configured as a weatherproof enclosure for outdoor installation and comprising a modular outer frame system, where an outer frame is interchangeable and removably attached to the housing 114 through a mechanical coupling mechanism. The weatherproof housing is required to ensure that the smart doorbell device 108 functions reliably in various environmental conditions such as rain, dust, heat, and humidity. The housing 114 is constructed using durable, weather-resistant materials such as polycarbonate, Acrylonitrile Butadiene Styrene (ABS) plastic, or metal alloys, and is sealed to protect internal components like the device processor 110, the barcode scanning module 112, and the video communication module 120. The outer frame forms part of the visible exterior and is connected to the housing 114 through the mechanical coupling mechanism, such as clips, slots, or slide-in rails, that allows easy detachment and replacement. The weatherproof structure ensures long-term durability, while the modular frame design adds flexibility and aesthetic value to the smart doorbell system 108.
[0056] FIG. 2A and 2B are collectively a flowchart of a method for implementing secure delivery authentication using a smart doorbell system, in accordance with an embodiment of the present disclosure. FIG. 2A and 2B is described in conjunction with elements of FIG 1. With reference to FIG. 2A and 2B, there is shown a method 200 for implementing secure delivery authentication using a smart doorbell system. The method 200 includes steps 202 to 220.
[0057] The method 200 outlines a detailed, stepwise approach for implementing secure delivery authentication using the smart doorbell system. The method 200 leverages a combination of order scanning, encrypted data exchange, local user authentication, and controlled OTP display to ensure secure, contactless, and verifiable package deliveries. Each step in the method 200 is designed to enhance delivery security, reduce dependency on mobile networks, and maintain traceability of authentication events.
[0058] Referring to FIG. 2A, at step 202, the method 200 comprises receiving delivery order identifier data from the barcode scanning module 112 of a smart doorbell device 108, where the barcode scanning module 112 comprises the camera module 128 with barcode decoding capabilities. The camera module 128 is configured to capture and interpret machine-readable codes such as QR codes or barcodes printed on delivery documentation. When delivery personnel presents a package, the camera module 128 scans the visible code on the package label. The captured image is processed locally to extract the delivery order identifier, which uniquely corresponds to the delivery item.
[0059] At step 204, the method 200 comprises transmitting the delivery order identifier data to the server 102. The step 204 involves sending the decoded identifier, captured by the barcode scanning module 112 of the smart doorbell device 108, to the server 102 through a secure wireless communication channel. The data transmission is managed by the device processor 110, which formats and forwards the order identifier in real-time or near real-time. The server 102 receives the transmitted data for further validation against pre-stored delivery records associated with the intended recipient.
[0060] At step 206, the method 200 comprises validating the delivery order identifier data at the server 102 against stored delivery information. The step 206 involves comparing the received order identifier, transmitted from the smart doorbell device 108, with delivery records maintained within the server 102. The delivery records may include pre-registered order IDs, expected delivery schedules, and recipient account details. The validation process is executed by the processor 104 of the server 102 to determine whether the scanned order corresponds to a legitimate and authorized delivery. The step 206 provides that only verified delivery events proceed further in the authentication workflow.
[0061] At step 208, the method 200 comprises receving an OTP corresponding to the validated delivery order identifier at the server 102. The step 208 involves initiating an OTP generation process upon successful validation of the delivery order identifier against stored delivery records. The processor 104 of the server 102 generates a unique, time-bound OTP that is specifically linked to the validated delivery transaction. The step 208 provides the method 200 to establish a secure and verifiable code that will later be displayed to the delivery personnel only upon successful local authentication by the resident.
[0062] At step 210, the method 200 comprises encrypting the OTP and transmitting the encrypted OTP to the smart doorbell device 108. The step 210 involves applying a secure encryption algorithm to the OTP generated at the server 102, ensuring that the OTP remains protected during transmission. Once encrypted, the OTP is transmitted to the smart doorbell device 108 over a secure communication channel via the network interface 106. The step 210 provides that the OTP cannot be intercepted, altered, or reused by unauthorized entities during transit, thereby maintaining the confidentiality and integrity of the delivery authentication process.
[0063] At step 212, the method 200 comprises storing the encrypted OTP in local memory without displaying it on the display unit 116. The step 212 involves receiving the encrypted OTP at the smart doorbell device 108 and storing it securely within the internal memory associated with the device processor 110. The OTP remains concealed from the display unit 116 and inaccessible to users or external parties until successful authentication is completed. By withholding visual output, the method 200 prevents premature exposure of the OTP, thereby safeguarding the code from unauthorized viewing or tampering.
[0064] At step 214, the method 200 comprises detecting authentication events when a contactless authentication card is presented to the proximity reader 118. The step 214 involves the proximity reader 118 continuously monitoring for the presence of a valid contactless card, such as an NFC-enabled resident identification card. When the card is brought within the detection range, the proximity reader 118 captures the card’s identification data and forwards it to the device processor 110 for verification. The step 214 initiates the verification process required to unlock access to the stored OTP, and provides that delivery authentication proceeds only when legitimate user presence is confirmed.
[0065] At step 216, the method 200 comprises verifying the authentication events against encrypted pre-stored household authentication data. The step 216 involves the device processor 110 receiving the card identification data from the proximity reader 118 and comparing it with a secure set of encrypted pre-stored household authentication data stored locally within the smart doorbell device 108. The verification process ensures that the presented card matches one of the authorized identities before proceeding. The step 216 provides essential access control, releasing the OTP only after verified resident authentication.
[0066] Referring to FIG. 2B, at step 218, the method 200 comprises decrypting and displaying the OTP on the display unit 116 for a predetermined time period only upon successful verification of the authentication events, where the OTP expires after successful verification. The step 218 executes secure OTP release through a multi-stage authentication process. The device processor 110 first verifies the presented contactless authentication card against encrypted pre-stored household data. Upon successful verification, the device processor 110 decrypts the locally stored OTP using an embedded decryption key and displays the code on the display unit 116 for a predetermined time window. The delivery personnel can then view and enter the code for delivery verification. The OTP automatically expires either upon successful entry or timeout, preventing unauthorized reuse and maintaining authentication security through time-bound conditional access.
[0067] At step 220, the method 200 comprises maintaining a secure log of all delivery authentication attempts at the server 102. The step 220 involves the server 102 recording key data points associated with each delivery event, including timestamps, order identifiers, authentication outcomes, OTP verification status, and device identifiers. The logging process is managed by the processor 104 in the server 102 and stored in a tamper-resistant format within a secured database. The log serves as a verifiable audit trail that supports accountability, user access review, and system diagnostics. By retaining a comprehensive history of authentication events, the method 200 provides traceability, enhances transparency, and enables both delivery services and residents to monitor and verify the integrity of completed or attempted delivery transactions.
[0068] For example, a delivery personnel arrives at a residence equipped with the smart doorbell system to drop off a package. The delivery personnel use the barcode scanning module 112 of the smart doorbell device 108 to scan the barcode printed on the delivery package. The camera module 128 decodes the barcode and extracts the delivery order identifier, which is then transmitted to the server 102. Upon receiving the data, the processor 104 validates the delivery order identifier against pre-stored delivery records. Once validated, the server 102 receives an unique OTP, encrypts it, and sends it back to the smart doorbell device 108. The device processor 110 stores the encrypted OTP in local memory without displaying it. Meanwhile, the resident presents a registered contactless authentication card to the proximity reader 118. The device processor 110 verifies the authentication card against encrypted household credentials stored locally. Upon successful authentication, the OTP is decrypted and briefly displayed on the display unit 116, allowing the delivery personnel to view and enter it as confirmation. The OTP immediately expires after use, and all delivery authentication events are securely logged by the server 102. The exemplary scenario illustrates a secure, contactless, and verifiable method for confirming package deliveries while protecting user privacy and enhancing system reliability.
[0069] The steps 202 to 220 are only illustrative, and other alternatives can also be provided where one or more steps are added, or one or more steps are provided in a different sequence without departing from the scope of the claims herein.
[0070] There is provided a computer program product comprising instructions for performing the method 200 when executed by one or more processors (i.e., the processor 104 in the server 102 and the device processor 110 in the smart doorbell device 108) the system 100. The computer program is implemented as an algorithm, embedded in a software stored in the non-transitory computer-readable storage medium having program instructions stored thereon, the program instructions being executable by the one or more processors in the computer system to execute the method 200. The non-transitory computer-readable storage means may include, but are not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. Examples of implementation of computer-readable storage medium, but are not limited to, an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Random Access Memory (RAM), a Read Only Memory (ROM), a Hard Disk Drive (HDD), a Flash memory, a Secure Digital (SD) card, a Solid-State Drive (SSD), a computer-readable storage medium, and/or a CPU cache memory.
[0071] FIG. 3 is a process for implementing secure delivery authentication using a smart doorbell system, in accordance with an embodiment of the present disclosure. FIG. 3 is described in conjunction with the elements of FIGs 1, 2A, and 2B. With reference to FIG. 3, there is shown a process 300 for implementing secure delivery authentication using the smart doorbell system. The smart doorbell authentication system comprising a delivery person 302 holding a package, the smart doorbell device 108 positioned at the entrance, a household member 304 equipped with the NFC card 132, the server 102, and a user mobile device 306 for remote monitoring. The process 300 includes a series of operations 308 to 316.
[0072] At operation 308, the delivery person 302, carrying a package with delivery documentation, approaches the smart doorbell device 108 and initiates the authentication process by scanning the order identifier. The delivery person 302 positions the package or delivery slip containing the order number, QR code, or barcode in front of the integrated scanner within the smart doorbell device 108. The barcode scanning module 112 captures the order identifier data and processes the information through its embedded processor.
[0073] At operation 310, concurrently with or following the scanning operation, the household member 304, retrieves their assigned NFC card and approaches the smart doorbell device 108. The household member 304 taps the NFC card against the NFC reader 130 integrated within the smart doorbell device 108. The NFC reader 130 detects the electromagnetic signal from the NFC card held by household member 304 and reads the unique identifier stored on the NFC card. The smart doorbell device 108 then verifies this identifier against pre-stored household authentication data in its local memory, confirming that household member 304 is authorized to approve delivery transactions.
[0074] At operation 312, upon successful completion of both scanning by the delivery person 302 and NFC authentication by the household member 304, the smart doorbell device 108 initiates communication with the server 102. The smart doorbell device 108 transmits the scanned order identifier captured from the package to the server 102 via encrypted data transmission protocols. The server 102 processes the order identifier, validates it against the e-commerce platform database, and receives or retrieves the corresponding authentication code (OTP) for the specific delivery transaction initiated by the delivery person 302.
[0075] At operation 314, the server 102 transmits the authentication code back to the smart doorbell device 108 through the established secure communication channel. The device processor 110 receives the authentication code and stores it in local memory without immediately displaying the code. The temporary storage operation ensures that the delivery person 302 cannot access the authentication code until proper household authorization from the household member 304 has been confirmed. After confirming that the household member 304 has completed the NFC card authentication, and the order scanning by the delivery person 302 has been verified, the device processor 110 releases the stored authentication code for display. The OTP becomes visible on the display unit 116, allowing the delivery person 302 to view the code and enter it into their delivery verification system or mobile application. The conditional display operation ensures that the delivery person 302 can only access the authentication code when both order verification and the household member 304 approval have been obtained.
[0076] At operation 316, simultaneously with the authentication code display, the smart doorbell device 108 may establish a video communication session (through the video communication module 120) with the user mobile device 306, enabling remote monitoring of the delivery process. The user mobile device 306 receives real-time notifications about the delivery attempt initiated by the delivery person 302 and the authentication process involving the household member 304. The mobile device 306 displays system status, video feed from the smart doorbell device 108, and delivery confirmation details, providing remote oversight of the entire transaction between the delivery person 302, the household member 304, and the smart doorbell device 108. The delivery person 302 uses the displayed authentication code to complete the delivery verification process in their delivery application or system. Upon successful code entry by the delivery person 302, the smart doorbell device 108 generates a delivery confirmation signal and transmits it to the server 102. The server 102 logs the successful transaction, recording details about the authentication of the delivery person 302, the approval of the household member 304, and the verification process of the smart doorbell device 108. The user mobile device 306 receives the final delivery confirmation, completing the secure authentication workflow.
[0077] FIG. 4 illustrates an exploded view of a smart doorbell device, in accordance with an embodiment of the present disclosure. FIG. 4 is described in conjunction with the elements of FIGs 1, 2A, 2B, and 3. With reference to FIG. 4, there is shown an exploded view 400 of the smart doorbell device 108. There is shown the display unit 116 serves as the primary user interface connected to the device processor 110 through internal communication pathways. The speaker 126 of the video communication module 120, which connects to the main processing circuitry for audio output during two-way communication sessions. The main body houses the components, including the device processor 110, the proximity reader 118 containing the NFC reader 130 for household authentication, the wide-angle camera 122, and the microphone 124 of the video communication module 120, and the communication capabilities for the server 102. The barcode scanner module 112 positioned at the smart doorbell device 108 base integrated with the camera module 128, enabling order identifier scanning and connecting to the device processor 110 for real-time data processing. A detachable battery 402 provides power distribution to all components within the housing 114, while the device processor 110 serves as the central coordination hub managing communication between the display unit 116, the proximity reader 118, the barcode scanning module 112, the video communication module 120, and the server 102, creating a unified smart doorbell device capable of executing secure delivery authentication workflows within the system 100 architecture.
[0078] FIG. 5 is a diagram of a user interface of a mobile application associated with a smart doorbell device, in accordance with an embodiment of the present disclosure. FIG. 5 is described in conjunction with the elements of FIGs 1, 2A, 2B, 3, and 4. With reference to FIG. 5, there is shown a diagram 500 of a user interface of a mobile application associated with the smart doorbell device 108. The user interface presents a live video feed from the wide-angle camera 122 of the video communication module 120, displaying a delivery person at the doorbell location who is holding a package for delivery verification. The user interface of the mobile application features a prominent "VERIFY OTP" button that enables remote users to participate in the authentication process, and includes a bell notification icon at the bottom indicating an active doorbell interaction. The user interface demonstrates the remote monitoring and control capabilities of the system 100, allowing the household members to visually verify delivery personnel through the video communication module 120 while maintaining the ability to remotely oversee the OTP verification process that occurs between the delivery person 302, the smart doorbell device 108, and the system’s authentication workflow.
[0079] The disclosed system provides a secure, efficient, and network-independent solution for verifying package deliveries, addressing key limitations associated with prior art systems. Existing delivery authentication approaches often depend on SMS-based OTPs, which are susceptible to interception, mobile network failures, and user inconvenience due to the requirement for active device access. The disclosed system integrates the barcode scanning module 112, the proximity reader 118 for an authentication mechanism, and an OTP verification process directly into the smart doorbell device 108. By enabling OTP display only after successful verification of a pre-authorized contactless authentication card, the system 100 prevents unauthorized access by delivery personnel or external parties. Furthermore, the encrypted communication between the server 102 and the smart doorbell device 108 ensures secure data exchange, while the automatic logging of each delivery authentication event at the server 102 provides a verifiable audit trail. The system 100 offers improved operational efficiency for logistics providers by reducing dependency on SMS infrastructure and streamlining the package handover process at the doorstep. The combination of physical presence validation and digital encryption mechanisms enhances resident control and delivery security in a manner not achievable by conventional smart doorbell systems.
[0080] Modifications to embodiments of the present disclosure described in the foregoing are possible without departing from the scope of the present disclosure as defined by the accompanying claims. Expressions such as "including", "comprising", "incorporating", "have", "is" used to describe and claim the present disclosure are intended to be construed in a non-exclusive manner, namely allowing for items, components or elements not explicitly described also to be present. Reference to the singular is also to be construed to relate to the plural. The word "exemplary" is used herein to mean "serving as an example, instance or illustration". Any embodiment described as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments and/or to exclude the incorporation of features from other embodiments. The word "optionally" is used herein to mean "is provided in some embodiments and not provided in other embodiments". It is appreciated that certain features of the present disclosure, which are, for clarity, described in the context of separate embodiments, may also be provided in combination in a single embodiment. Conversely, various features of the present disclosure, which are, for brevity, described in the context of a single embodiment, may also be provided separately or in any suitable combination or as suitable in any other described embodiment of the disclosure.
, Claims:CLAIMS
We Claim:
1. A system (100) for secure delivery authentication in smart doorbell environments, the system (100) comprising:
a server (102) comprising a processor (104) configured to:
receive delivery order identifier data from a smart doorbell device (108), wherein the delivery order identifier data comprises scanned order information;
validate the delivery order identifier data against stored delivery information;
receive a One-Time Password (OTP) corresponding to the validated delivery order identifier;
encrypt the OTP and transmit the encrypted OTP to the smart doorbell device (108);
receive authentication confirmation from the smart doorbell device (108); and
log delivery confirmation events after successful OTP verification by delivery personnel;
the smart doorbell device (108) comprising a device processor (110) configured to:
control a barcode scanning module (112) to capture delivery order identifiers from delivery documentation, wherein the barcode scanning module (112) comprises a camera module with barcode decoding capabilities;
transmit the captured order identifier data to the server (102);
receive and store the encrypted OTP from the server (102) in local memory without displaying it on a display unit (116);
detect authentication events when a contactless authentication card is presented to a proximity reader (118), wherein the authentication events comprise card identification data;
verify the authentication events against encrypted pre-stored household authentication data stored in the device processor (110);
decrypt and display the OTP on the display unit (116) of the smart doorbell device (108) for a predetermined time period only upon successful verification of the authentication events, wherein the OTP expires after successful verification; and
return to an idle state after OTP display, wherein the idle state comprises displaying customizable wallpaper content.
2. The system (100) as claimed in claim 1, wherein the device processor (110) is further configured to generate error notifications for invalid authentication attempts, display error messages on the display unit (116) for failed contactless authentication card verification, and transmit authentication failure alerts to the server (102).
3. The system (100) as claimed in claim 2, wherein the error notifications comprise any of timeout alerts for expired authentication attempts, invalid card format warnings, and network connectivity failure messages.
4. The system (100) as claimed in claim 1, wherein the smart doorbell device (108) further comprises a video communication module (120) operatively connected to the device processor (110), the video communication module (120) configured to establish encrypted two-way video communication between a delivery person at the smart doorbell device (108) and a user mobile device through the server (102), capture video data of delivery personnel during order scanning, and transmit the video data to the server (102) for relay to the user mobile device.
5. The system (100) as claimed in claim 4, wherein the video communication module (120) comprises a wide-angle camera (122) with a field of view between 120 to 160 degrees positioned behind the display unit (116) and a microphone (124) for audio capture, and a speaker (126) for audio output.
6. The system (100) as claimed in claim 1, wherein the proximity reader (118) comprises a Near Field Communication (NFC) reader compatible with contactless authentication cards.
7. The system (100) as claimed in claim 6, wherein the device processor (110) is further configured to generate a data repository of authorized contactless authentication cards, update the data repository through a connected mobile application, and compare presented card identification data with the authorized card data stored in the data repository.
8. The system (100) as claimed in claim 7, wherein upon determining that the presented contactless authentication card does not match with authorized card data stored in the data repository, the device processor (110) is configured to:
generate an unauthorized access alert;
transmit the unauthorized access alert to the server (102); and
lock the smart doorbell device (108) from further authentication attempts for a predetermined time period, wherein the server (102) is further configured to transmit the unauthorized access alert to a user mobile application.
9. The system (100) as claimed in claim 1, wherein the smart doorbell device (108) further comprises a housing (114) configured as a weatherproof enclosure for outdoor installation and comprising a modular outer frame system, wherein an outer frame is interchangeable and removably attached to the housing (114) through a mechanical coupling mechanism.
10. A method (200) for implementing secure delivery authentication using a smart doorbell system (100), the method (200) comprising:
receiving delivery order identifier data from a barcode scanning module (112) of a smart doorbell device (108), wherein the barcode scanning module (112) comprises a camera module (128) with barcode decoding capabilities;
transmitting the delivery order identifier data to a server (102); validating the delivery order identifier data at the server (102) against stored delivery information;
receiving a One-Time Password (OTP) corresponding to the validated delivery order identifier at the server (102);
encrypting the OTP and transmitting the encrypted OTP to the smart doorbell device (108);
storing the encrypted OTP in local memory without displaying it on a display unit (116);
detecting authentication events when a contactless authentication card is presented to a proximity reader (118);
verifying the authentication events against encrypted pre-stored household authentication data;
decrypting and displaying the OTP on the display unit (116) for a predetermined time period only upon successful verification of the authentication events, wherein the OTP expires after successful verification; and
maintaining a secure log of all delivery authentication attempts at the server (102).