WO2024097509A1

WO2024097509A1 - Asynchronous video messaging using a printable medium without sharing personal identifiable information

Info

Publication number: WO2024097509A1
Application number: PCT/US2023/076396
Authority: WO
Inventors: Yeganeh PAYAM; Zakeri BAHMAN
Original assignee: Video Stamps, Inc.
Priority date: 2022-11-05
Filing date: 2023-10-09
Publication date: 2024-05-10

Abstract

An anonymous messaging system includes printable media embedded with machine- readable code. Each machine-readable code includes a URL with the name of a host server and a tokenized unique identifier. The host server stores a copy of the tokenized unique identifiers. The host server receives a first anonymous video message from a first electronic device and stores the first video message as a video message associated with a first tokenized unique identifier. The first electronic device authorizes receiving web push notifications through a push notification service. The printable media with the machine-readable code that includes the first tokenized unique identifier is attached to a physical object and is sent to a recipient. The recipient's electronic device activates the machine-readable code to anonymously download the first video message from the host server and send an anonymous reply message to the first electronic device through the host server and the push notification server.

Description

ASYNCHRONOUS VIDEO MESSAGING USING A PRINTABLE MEDIUM WITHOUT SHARING PERSONAL IDENTIFIABLE INFORMATION

CLAIM OF BENEFIT TO PRIOR APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Patent Application Serial No. 63/422,964, filed on November 5, 2022. The contents of U.S. Provisional Patent Application 63/422,964 are hereby incorporated by reference.

BACKGROUND

[0002] Physical products may now be enhanced with digital capabilities. The possibilities for people connected by mobile devices to interact with the physical world are unlimited. These interactions may affect our identity and all issues associated with it including our privacy. Privacy is one of the greatest challenges posed by a connected world yet tracking and sharing of personal information has become part of the new connectivity.

[0003] There are several existing systems for adding digital enhancements to the physical products, especially with a focus on providing video messages with the delivery of packages or for enhancing gifting experience. However, a number of technical challenges remain especially around usability and user privacy.

[0004] For example, one system provides a personalized message delivered with a gift or package using a quick response (QR) code or a near field communication (NFC) tag by receiving the identity of the intended recipient and including messages and advertisements regarding products or services related to the physical package.

[0005] Another system provides a method to associate a video message with a package to be shipped. Specifically, generating a package shipping label linked to the video message. Another system applies affixable media (e.g., stickers) with scannable code linked to prerecorded contents to personalize greeting cards. Another system facilitates anonymous and private communication between publishers and consumers, using publisher and consumer smartphone applications, and a scannable code that is generated by the publisher. In this system, the publisher and consumers have to maintain and update their profiles and the associated contact information and permissions to the secure server.

[0006] While the above-described technologies have incorporated scannable codes and methods, in general to share and/or exchange personalized messages together with physical packages, a number of technical challenges remain to enable a simple private and anonymous physical to digital interaction suitable for mass adoption. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] The various embodiments of the present asynchronous video messaging using a printable medium without sharing personal identifiable information now will be discussed in detail with an emphasis on highlighting the advantageous features. These embodiments depict the novel and non-obvious asynchronous video messaging using a printable medium without sharing personal identifiable information shown in the accompanying drawings, which are for illustrative purposes only. These drawings include the following figures, in which like numerals indicate like parts:

[0008] FIGS. 1A-1C are functional diagrams illustrating an embodiment of an anonymous asynchronous video messaging system that uses printable mediums without sharing personal identifiable information, according to various aspects of the present disclosure;

[0009] FIG. 2 is a schematic front view of a client device that may display a user interface for recording a video message to be associated with a tokenized unique identifier, according to various aspects of the present disclosure;

[0010] FIG. 3 is a schematic front view of a client device that may display a user interface for receiving a video message or recording a reply message, according to various aspects of the present disclosure;

[0011] FIG. 4A is a schematic front view of a client device that may display a user interface 400 for displaying a push notification to inform the client device that a video message has been viewed, according to various aspects of the present disclosure;

[0012] FIG. 4B is a schematic front view of a client device that may display a user interface for displaying a push notification and providing a reply message to the client device, according to various aspects of the present disclosure;

[0013] FIG. 5 is a functional diagram illustrating the components of the video messaging system of FIGS. 1 A-1C, according to various aspects of the present disclosure;

[0014] FIGS. 6A-6B are a flowchart illustrating an example process for exchanging asynchronous video messaging between client devices using a printable medium without sharing personal identifiable information, according to various aspects of the present disclosure;

[0015] FIG. 7 is a functional diagram illustrating an example of using the anonymous video messaging for sending flyers, according to various aspects of the present disclosure; [0016] FIG. 8 is a functional diagram illustrating an example of using the anonymous video messaging using official government issued postage stamps, according to various aspects of the present disclosure;

[0017] FIG. 9 is a functional diagram illustrating an example of using the anonymous video messaging in a social event where participants may anonymously and privately video message with the meeting organizer or host, according to various aspects of the present disclosure;

[0018] FIG. 10 is a functional diagram illustrating an example of sending each of several anonymous video messaging to multiple recipients and using push notification to correlate the received replies to each anonymous video message, according to various aspects of the present disclosure; and

[0019] FIG. 11 conceptually illustrates an electronic system with which some embodiments of the invention are implemented.

DETAILED DESCRIPTION

[0020] Anonymous messaging applications (apps) are systems and platforms that provide messaging between senders and receivers of messages without revealing the identity of the participants. One aspect of the present embodiments includes the realization that the existing anonymous messaging platforms require the users (e.g., senders and receivers) to provide some form of identity to the platform. The users have to install the same smartphone app or have access to the same messaging platform cloud service. As part of the registration process to these services, users are typically required to enter their phone numbers, email addresses, and/or other personal information. These days email addresses and phone numbers may reveal more personal information than most people think. A person's phone number is even a more accurate way of identifying them than their name.

[0021] Some of the present embodiments solve the aforementioned problems by providing a messaging system where no personal identifiable information such as name, email, or phone number is shared, therefore users' data and privacy are protected. These embodiments eliminate sharing of personal identifiable information while allowing an asynchronous video messaging between users.

[0022] Some embodiments may provide printable media such as stickers or smart labels with embedded machine-readable code. The machine-readable code may be a bar code, for example, a two-dimensional (2D) bar code (e.g., a QR code), an NFC tag, a radio frequency identification (RFID) tag, etc. Each machine-readable code, in some embodiments, may include a URL. Each URL may include the name of a host server and a tokenized unique identifier.

[0023] The host server may store, or may have access to, a copy of the tokenized unique identifiers. The host server may receive an anonymous request from a first electronic device to associate a first video message with a first tokenized unique identifier embedded in a corresponding printable medium. For example, the first electronic device may be a first smartphone. The first smartphone may activate the machine-readable code embedded in the printable medium, for example, by scanning a QR code embedded in the printable medium with the first smartphone’s camera, or bringing the first smartphone’s NFC reader close to an NFC tag embedded in the printable medium, or activating an RFID tag embedded in the printable medium, etc., resulting in the web browser of the first smartphone to access the URL included in the machine-readable code. Accessing the URL may provide the first tokenized unique identifier, as a URL parameter, from the web browser of the first smartphone to the host server. [0024] The host server may send a request to the first electronic device to send the first video message after determining that the first tokenized unique identifier is one of the stored tokenized unique identifiers and the first tokenized unique identifier is not already associated with a video message. The host server may receive the first video message from the first electronic device and may store the first video message as a video message associated with the first tokenized unique identifier.

[0025] The host server may provide a web push notification option to the first electronic device. For example, a message may be displayed on the display of the first electronic device whether a web push notification may be provided after receiving a reply from the receiver of the first video message. If the push notification option is accepted, the host server may send a notification through a third-party push service, such as the vendor of the web browser of the client device, to the web browser of the first smartphone when a reply to the first video message is received.

[0026] The printable medium with the machine-readable code that includes the first URL may then be attached to a physical object that may be sent to a recipient. The recipient may view the first video message and may send a reply message by performing the following steps. The host server may receive an anonymous request from a second electronic device associated with the receiving person to receive the first video message. For example, the second electronic device may be a second smartphone. The second smartphone may activate the machine-readable code embedded in the printable medium, for example, by scanning a QR code embedded in the printable medium with the second smartphone’s camera, or bringing the smartphone’ s NFC reader close to an NFC tag embedded in the printable medium, or activating an RFID tag embedded in the printable medium, etc., resulting in the web browser of the second smartphone to access the URL included in the machine-readable code. Accessing the URL may provide the first tokenized unique identifier, as a URL parameter, from the web browser of the second smartphone to the host server.

[0027] The host server may retrieve the first video message using the first tokenized unique identifier. The host server may then provide the first video message to the web browser of the second electronic device.

[0028] The second electronic device may receive an option from the host server to send a reply message to the sender of the first video message. The reply message may be a second anonymous video message, an anonymous audio message, or an anonymous textual message. The host server may receive the reply message from the second electronic device and may store the second video message as a reply video message associated with the first tokenized unique identifier. The host server may inform the web browser of the first electronic device through web push notification that a reply message is available. The host server may send a link to the reply message to the web browser of the first electronic device, through the third-party push service, when the web push notification is accepted by the first electronic device.

[0029] The messaging system of the present embodiments enables mass adoption of the physical to digital interaction while addressing the users’ privacy concerns of the connected world. The anonymous messaging system of the present embodiments provides the following technical advantages over the existing anonymous messaging systems. The communication between the users is asynchronous and is initiated only when an electronic device of a user reads the printable medium's unique embedded tokenized identifier. The printable medium acts as a private asynchronous data exchange gateway between the users. The message sender or recipient identities or any personal identifiable data record associated with them are not linked nor exchanged. The messaging system of the present embodiments requires no registration, and no personal information is logged or shared. Therefore, privacy of the users is protected.

[0030] Since the printable medium is physical, the act of physically interacting with a printable medium such as paper, postcard, or sticker to invoke a communication, has an element of sensory input. The printable medium is something that the brain remembers much more vividly than a digital communication message. The messaging system of the present embodiments enables an interaction with a physical object by augmenting a digital experience and accelerates the adoption of physical-digital convergence, due to usability and accessibility of printable media.

[0031] The remaining detailed description describes the present embodiments with reference to the drawings. In the drawings, reference numbers label elements of the present embodiments. These reference numbers are reproduced below in connection with the discussion of the corresponding drawing features.

[0032] FIGS. 1A-1C are functional diagrams illustrating an embodiment of an anonymous asynchronous video messaging system 100 that uses printable mediums without sharing personal identifiable information, according to various aspects of the present disclosure. With reference to FIGS. 1A-1C, the system may include one or more messaging servers (also referred to as the host servers) 110, several client devices 121-122, and several printable media 130 (only one printable medium 130 is shown for clarity). The network(s) 190 may be one or more of the Internet, intranets, cellular networks, networks of server s/b ackend devices, and/or users’ networks (e.g., Wi-Fi, Ethernet, etc.). [0033] The printable medium 130 may include stickers, smart labels, greeting cards, postcards, gift cards, gift tags, books, flyers, postage stamps, etc. The printable medium 130 may be made of paper, fabric, plastic, etc. The terms printable mediums or printable media are interchangeably used, herein, to refer to more than one printable medium. The machine- readable code 140 embedded in the printable medium 130 may be a bar code, a 2D bar code such as a QR code, an RFID tag, an NFC tag, a printable label with flexible electronics, a smart label, etc. Flexible electronics are electronic devices built on conformable or stretchable substrates made of plastic, metal foil, paper, etc. A smart label may be a flat configured transponder that includes a chip, an antenna, and bonding wires that are laminated as inlays in labels made of paper, fabric, or plastic.

[0034] The machine-readable code 140 may include a URL. The URL may include a host server name and a tokenized unique identifier as a URL parameter. Tokenization is the process of substituting a sensitive data element with a non-sensitive equivalent, referred to as a token, that has no intrinsic or exploitable meaning or value. The token is a reference (or identifier) that maps back to the sensitive data through a tokenization system. The mapping from original data to a token uses methods, such as, using tokens created from random numbers, that render tokens infeasible to reverse in the absence of the tokenization system.

[0035] For example, the tokenized unique identifier may be a hash value in the form of several characters. The characters may be combinations of letters and digits making up the unique portion of the URL. The URL included in each machine-readable code of the present embodiments may, therefore, be different than the URLs included in other machine-readable code. The messaging server(s) 110 may store, or may have access to, a copy of the tokenized unique identifiers. A non-limiting example of a URL of the present embodiments that includes a tokenized unique identifier is:

[0036] https://www.app. hostname. com?tokenizeduniqueid=WFU18h4!R9di48%SIA7 j0mxo52h912hq

[0037] where the URL may include a protocol name (e.g., http or https), a domain name system (DNS) hierarchy (e.g., www.app.hostname.com) that identifies an application of the messaging server(s) 110 that handles the messaging system 100, and a URL parameter (e.g., the key value pair of tokenizeduniqueid=WFU18h4!R9di48%SIA7j0mxo52h912hq). In this example, the key value pair is used to pass the value of the tokenized unique identifier to the messaging server(s) 110. The tokenized unique identifier included in the URL stored in each machine-readable code (such as the tokenized unique identifier included in the URL stored in the machine-readable code 140) is different than the tokenized unique identifiers included in the URL stored in any other machine-readable code.

[0038] The client devices 121-122 may be electronic devices, such as smartphones, tablets, smart watches, laptop computers, desktop computers, etc. The client devices 121-122 may include optical sensors and/or cameras to read optical bar codes such as QR codes and/or to record videos. The client devices 121-122 may include RFID readers to read RFID tags. The client devices 121-122 may include NFC readers to read NFC tag. The client devices 121- 122 may include communication transceivers, such as cellular, Wi-Fi, and/or Bluetooth transceivers.

[0039] In some embodiments, the printable media may not be printed by the system 100. For example, the printable media may be purchased from a third party that may print images on the printable media and may embed the machine-readable code 140 that includes a URL and a corresponding tokenized unique identifier in each printed medium 130. In other embodiments, the system 100 may print images on the printable media and may embed the machine-readable code 140 that includes a URL and a corresponding tokenized unique identifier in each printed medium 130. Regardless of whether the printed mediums are printed by the system 100 or by a third party, the tokenized unique identifiers included in the machine- readable codes that are embedded in the printable media are not associated with a video message prior to the first use.

[0040] The anonymous tokenized unique identifier that is pre-integrated within the printable medium provides the technical advantage that the message sender does not require using a printer, or using the services of a third party (such as an order processor), to print the anonymous token on a printable medium. The message sender and the message receiver do not need to know the web address of the messaging servers and/or use any particular apps other than a web browser to record a message, to read a message, and/or to record a reply message. The sender of the first message may optionally subscribe to receive anonymous web push notification to get notification and read any reply messages using their browsers.

[0041] FIGS. 1A-1C, as shown, may include five operational stages 101-105. Different steps of FIGS. 1A-1C are shown by reference numbers 1-12. In stage 101, the client device 121 of a first person may activate (as shown by step 1) the machine-readable code 140 that is embedded in the printable medium 130. For example, a printed machine-readable code, such as a QR code may be scanned by the camera of the client device 121. A machine-readable code stored in an NFC may be activated by bringing the internal NFC reader of the client device 121 close to the NFC tag embedded in the printable medium. [0042] By activating the machine-readable code 140, the web browser of the client device 121 may access the URL included in the machine-readable code 140. The terms web browser and browser are, herein, used interchangeably. Accessing the URL may cause the web browser of the client device 121 to send a connection request to the messaging server(s) 110 and may provide the tokenized unique identifier that is included in the URL to the messaging server(s) 110. For example, the tokenized unique identifier may be included as a parameter in the URL, as described above.

[0043] In response to the web browser of the client device 121 accessing the URL, the messaging server(s) 110 may determine whether the tokenized unique identifier included in URL is already associated with a recorded video message (e.g., as described below with reference to stage 104 of FIG. 1C) or no video message is associated with the URL. In the example of FIGS. 1A-1C, tokenized unique identifier included in the URL has not been associated with a video message in step 1.

[0044] The messaging server(s) 110 may send a request to the web browser of the client device 121 to record and send a video message. The client device 121 may be prompted to record a video message, without requiring registering for the service, nor requiring providing one’s personal identifiable information such as email address or cell phone number.

[0045] The messaging server(s) 110 may provide a user interface to the web browser of the client device 121 with an option for recording a video message 161. FIG. 2 is a schematic front view of a client device 121 that may display a user interface 200 for recording a video message to be associated with a tokenized unique identifier, according to various aspects of the present disclosure. FIG. 2, as shown, includes four operational stages 201-204. In stage 201, the client device 121 may display a user interface (UI) 200 on the display 210 of the client device 121. The UI 200 may be displayed in response to the client device 121 activating the machine-readable code 140 in stage 101 of FIG. 1A and the web browser of the client device 121 accessing the URL that is embedded in the machine-readable code 140. The UI 200 may display an option 220 to record a new video message and an option 230 to upload a previously recorded video message. In stage 201 the option 220 may be selected enabling the person using the client device 121 to record a new video message.

[0046] The user of the client device 121, in some embodiments, may upload (e.g., by selecting the option 230 in stage 203 of FIG. 2) an Augmented Reality (AR) video. AR is an interactive experience that combines the real world and computer-generated content. AR may incorporate a combination of real and virtual worlds, real-time interaction, and accurate 3D registration of virtual and real objects. In these embodiments, the machine-readable code 140 may trigger the Web-based AR trigger.

[0047] In stage 202, the UI may provide an option 250 to record video, an option 240 to preview the recorded video, and an option 255 to save the recorded video. In the example of FIG. 2, after recording and previewing the video message, the option 255 may be selected to save the video message.

[0048] In stage 203, the option 230 may be selected to upload a recorded video to the messaging server(s) 110 of FIG. 1A. For example, the video that was recorded in stage 202, or any other video message saved by client device 121 may be uploaded. Selecting the option 230 may upload the video message to the messaging server(s) 110 as shown by the video message 161 being sent from the client device 121 to the messaging server(s) 110 in step 2 of FIG. 1A. The video message 161 may be recorded and sent to the messaging servers 110 by the client device 121 without requiring any personal contact information regarding the persons associated with the client devices 121-122.

[0049] As shown in stage 204 of FIG. 2, a message 260 may be displayed on the display 210 of the client device 121 asking whether a notification may be allowed when a reply message is received from a person who receives the video message 161 of FIG. 1A. The UI 200 may provide an option 270 to allow receiving the notification and an option 280 to reject receiving notifications. The UI 200 may provide a display area 290 for entering an optional identifier 295 to use in the notification. For example, the optional identifier 295 may be “Video for Product X” and the notification (as shown in stage 401 of FIG. 4) may indicate “You have received a reply message to Video for Product X.”

[0050] The optional identifier may facilitate corelating a reply message for a video message when the client device 121 records multiple video messages that are associated with different tokenized unique identifiers. For example, the person using client device 121 may generate 10 different videos for 10 different types of packaged food products. The videos may be associated with the tokenized unique identifiers that are embedded in printed media attached to the food packages that are sent to 1000 buyers. The optional identifier 295 may allow the user of the client device 121 to know a reply message is associated with which type of packaged food product. If the optional identifier 295 is left blank, the notification may only indicate a notification for the reply message.

[0051] Some embodiments may use web push notifications (also known as browser push notifications) to notify the client device 121 when the video message 161 is viewed by the client device of the receiver of the video message 161 and/or when a reply message for the video message 161 is received. The web push notification is a combination of push technology and notification technology. The push technology enables a server to send messages to client devices even when the client devices are not actively using a website related to the server. The notification technology is used for displaying the pushed messages on the client device.

[0052] In the example of FIG. 2, when the option 270 is selected, the web browser of client device 121 may send a message to the messaging server(s) 110 that the client device 121 has accepted to receive push notifications. The messaging server(s) 110 may then send a request to a web service referred to as a push service. The messaging server(s) 110 may also generate a private and public encryption key pair and send the public key to the push service. The public and private keys may be used to encrypt the communication between the messaging server(s) 110 and the push service. The push service is a service that, in some embodiments, may be provided by one or more servers 195 of a third party such as the vendor of the browser of the client device 121.

[0053] Referring back to stage 101 of FIG. 1A, the messaging server(s) 110 may receive a push subscription object from the push service server 195, as shown in step 3 of stage 101 of FIG. 1A. The push subscription object may identify the push service server. For example, the push subscription object may include the web address and other information regarding the push service server that may allow the messaging server(s) 110 to contact the push service server 195. The messaging server(s) 110 may store the push subscription object and the private key, and may associate them with the tokenized unique identifier that is used to retrieve video message 161.

[0054] As described below with reference to stage 105 of FIG. 1C, when the messaging server(s) 110 receive(s) a reply message to the video message 161, the messaging server(s) 110 may send a link to the reply message to the client device 121 through the push service server 195 using the stored push notification object that corresponds to the tokenized unique identifier associated with the machine-readable code 140.

[0055] The printable medium 130 may be attached (as shown by step 4) to a physical object 150. The printable medium 130 may be affixed to the outside of the physical object 150, may be affixed to an item that is inside the physical object 150, may be included in a postcard or a flyer accompanying the physical object, etc. The physical object 150 may be a package, a gift card, an envelope, a flyer, post card, a letter, etc.

[0056] The printable medium 130 may then be accessed by a person associated with the client device 122. For example, the physical object 150 may be sent to, may be purchased by, or may be at a location that is accessible by, the person associated with the client device 122.

[0057] In stage 102 of FIG. 1A, the client device 122 may activate (as shown by step 5) the machine-readable code 140 that is embedded on the printable medium 130 attached to the physical object 150. For example, the client device 122 may scan a QR code embedded in the printable medium 130 with the camera of the client device 122, or may bring the client device’s 122 NFC reader close to an NFC tag embedded in the printable medium 130, etc., resulting in the browser of the client device 122 to access the URL included in the machine- readable code 130.

[0058] Accessing the URL may cause the browser of the client device 122 to send a connection request to the messaging server(s) 110 and may provide the tokenized unique identifier that is included in the URL, for example as a URL parameter, to the messaging server(s) 110. The messaging server(s) 110 may identify the video message 161 using the tokenized unique identifier that is included in the URL. For example, in stage 101, the messaging server(s) 110 may store the video message 161 in a database and may associate it with the tokenized unique identifier included in the machine-readable code 140. In stage 102, the messaging server(s) 110 may search the database using the tokenized unique identifier included in the machine-readable code 140 to find the stored video message 161.

[0059] In response to the activation of the machine-readable code 140, the messaging server(s) 110 may provide a user interface to the client device 122 with options for receiving the video message 161 or recording a reply video message. FIG. 3 is a schematic front view of a client device 122 that may display a user interface 300 for receiving a video message or recording a reply message, according to various aspects of the present disclosure.

[0060] FIG. 3, as shown, includes three operational stages 301-303. In stage 301, the client device 122 may display the UI 300 on the display 310 of the client device 122. The UI 300 may be displayed in response to the client device 122 activating the machine-readable code 140 in stage 102 of FIG. 1A. The UI 300 may provide an option 320 for playing the video message and an option 330 for sending a reply message.

[0061] In the example of FIG. 3, option 320 may be selected in stage 301. As shown in step 6 of FIG. 1A, the messaging server(s) 110 may provide the video message 161 to the browser of the client device 122 in response to the selection of option 320 of FIG. 3. If the client device 121 had accepted to allow notifications (e.g., as described above with reference to stage 204 of FIG. 2), playing the video message by the client device 122 may cause the messaging server(s) 110 to send a notification message 163 to the client device 121 through the push notification server 195. As shown in in stage 103 of FIG. IB, the notification message 163 is sent (in steps 7 and 8) from the messaging server(s) 110 to the client device 121 through the push notification server 195.

[0062] FIG. 4A is a schematic front view of a client device 121 that may display a user interface 400 for displaying a push notification to inform the client device that a video message has been viewed, according to various aspects of the present disclosure. As shown, the client device 121 may display a UI 400 on the display 210 of the client device 121. The UI 400 may be displayed in response to the client device 121 receiving a push notification from the push service server 195 in step 8 of FIG. IB. The UI, in some embodiments, may be a notification center that may provide different notifications 411-413 for the user of the client deice 121.

[0063] In the example of FIG. 4 A, the UI 400 may display a notification message 411 indicating that a video message has been viewed. The UI 400 may provide an option (e.g., clicking) to open the notification in a full-page display. If the optional identifier 295 was provided by the client device 121 as described above in stage 204 of FIG. 2, then the message 411 may also display the identifier.

[0064] Referring back to FIG. 3, in stage 302, the option 330 may be selected to provide a reply to the video message 161. In response, the UI 300 in stage 303 may provide an option 340 to reply with video, an option 350 to reply by voice, and an option 360 to reply by providing a textual message.

[0065] The client device 122 may then record and send (as shown by step 9 in stage 104 of FIG. 1C) the reply message 162 to the messaging server(s) 110. The reply message may be sent from the client device 122 to the messaging server(s) 110 as a file. Alternatively, client device 122 may send a link to the reply message to the messaging server(s) 110 to retrieve the reply message. When the option 340 is selected in stage 303 of FIG. 3, the client device 122 may record a video message and the browser of client device 122 may send a file including the video message to the messaging server(s) 110 in step 9 of FIG. 1C. When the option 350 is selected in stage 303 of FIG. 3, the client device 122 may record an audio message and the browser of client device 122 may send a file including the audio message to the messaging server(s) 110 in step 9 of FIG. 1C. When the option 360 is selected in stage 303 of FIG. 3, the person using the client device 122 may type a textual message and the browser of client device 122 may send a file including the textual message to the messaging server(s) 110 in step 9 of FIG. 1C.

[0066] In the embodiments that use web push notifications, the client device 121 may receive a notification that a reply message is received. For example, as described above with reference to stage 101 of FIG. 1 A, the messaging server(s) 110 may store the push notification object as the push notification object for the tokenized unique identifier that corresponds to video message 161. When the messaging server(s) 110 receive(s) the reply message 162 to the video message 161, the messaging server(s) 110 may identify the push service server 195 using the stored push notification object associated with the tokenized unique identifier.

[0067] The messaging server(s) 110 may send (as shown by step 10 in stage 105 of FIG. 1C) a link 164 to the reply message to the push service server 195 using the stored push notification object that corresponds to the tokenized unique identifier. The push service server 195 may send the 164 link to reply message to the client device 121 as shown in step 11 in stage 105 of FIG. 1C.

[0068] FIG. 4B is a schematic front view of a client device 121 that may display a user interface 400 for displaying a push notification and providing a reply message to the client device 121, according to various aspects of the present disclosure. FIG. 4B, as shown, includes two operational stages 401-402. In stage 403, the client device 121 may display a UI 400 on the display 210 of the client device 121. The UI 400 may be displayed in response to the client device 121 receiving a push notification from the push service server 195 in step 11 of FIG. 1C. The UI 400, in some embodiments, may be a notification center that may provide different notifications 414-417 for the user of the client deice 121.

[0069] As shown in stage 401 of FIG. 4B, the UI 400 may display a message 414 indicating that a reply message is received. The UI 400 may provide an option (e.g., clicking) to open the notification message 414. In response to the selection of the notification message 414, the UI may provide an option 450 to display the reply message in stage 402. In the example of FIG. 4B, the reply message is a video message that may be played by selecting the option 450. As shown in stage 105 of FIG. 1C, the messaging server(s) 110 may send the reply message 162 to the client device 121 in step 12 (e.g., after the link 440 to the reply message is selected in stage 403 of FIG. 4B).

[0070] As described with reference to FIGS. 1 A-1C, the present embodiments provide the technical advantage that the client device 122 may receive the video message 161 and may send a reply message 162 to the client device 121 without requiring any personal identification of the persons associated with the client devices 121-122. The sending of the video messages 161-162 and the notifications are anonymously facilitated the messaging server(s) 110 and the push service server 195. The client devices 121-122 are neither required to register for the service nor to provide any personal identifiable information such as email address or cell phone number. [0071] It should be noted that while certain functions are being performed by the messaging server(s) 110, some of these functions may be located within applications (apps) running on client devices 121-122, which is a design choice. The data that is received from the client devices may include message content, client device information (e.g., operating system, device type, web browser metadata, display capability) or client application specific inputs.

[0072] The anonymous asynchronous video messaging system 100 the present embodiments provides several technical advantages over the previous messaging systems. In the anonymous messaging system of the present embodiments, the sender and receiver of a video message may interact using a tangible printable medium while remaining anonymous. They do not need to provide their personally identifiable contact information such as email addresses or cell phone numbers to send a video message and receive a reply. Furthermore, there is no requirement to register to any service or download a smartphone application.

[0073] This anonymity is achieved by incorporating a single-use anonymous token (referred to as the tokenized unique identifier) embedded in the printable media in conjunction with web push notification technology. The anonymous token serves as a private key to the users’ messages. Whoever possesses the printable medium, which contains this embedded private key, gains access to the video message. This system offers a proxy service for user-to- user communication, as follows.

[0074] Token recognition and video association is achieved by the first user’s device reading the token from the printable medium and communicating with the host server to upload the video. Subsequently, the host server associates the video message with the said token. Push notification consent and subscription is provided by the first user granting push notification permission and subsequently subscribing to the push service provided by a push notification server. This subscription enables the first user to anonymously receive push notification for a second user’s reply.

[0075] Video message retrieval is provided after the second user gets the possession of the printable medium. The second user’s device may read the anonymous token from the printable medium, accessing the first user’s video message. For reply upload and token association , the second user uploads the reply, and the host server pairs it with the initial token.

[0076] For push service call and push message dispatch, a web service request is orchestrated by the host server to the push service. The push service processes the host server’s request, dispatching a push message to the web browser on the first user’s device. For notification receipt and response retrieval, the first user’s device receives the push notifications that carry a URL embedded with the original token. This URL redirects the user to the host server, enabling access to the second user’s reply.

[0077] In the background, the host server acts as an asynchronous communication server and administers the functionalities of the anonymous token. This token, embedded within a URL on a tangible print medium, pairs the video message and its corresponding reply message and serves as a proxy between the video messages of the first and second users.

[0078] The anonymous token has the following properties. The anonymous token is randomly generated (issued) through a tokenization process. The anonymous token is preintegrated within a printable medium and is usable only with that printable medium. Exclusively the issuer (host server) may generate a valid token. The host server cannot associate the token with either of the users, hence the users’ identity remains obscured to the host server.

[0079] Since the token resides within a tangible print medium, initially only the first user may interface with the host server to upload their video. However, once the second user gains possession of the print medium, they may access the first user’s video message and may also upload their reply. Using this approach, the first user sends a video message without needing any contact information of the second user. The token, which pairs the video message and its corresponding reply message, effectively masks the association between messages and the users.

[0080] Additionally, when the first user agrees to receive push notifications from the host server, their device browser does not disclose any personal data. Instead, it generates a web push unique token (referred to as the push notification object). The web push unique token enables the host server to communicate directly with the first user's device browser, allowing the first user to receive notifications from the second user while preserving their anonymity.

[0081] FIG. 5 is a functional diagram illustrating the components of the video messaging system of FIGS. 1A-1C, according to various aspects of the present disclosure. With reference to FIG. 5, the video messaging system 100 enables private communication between the client devices 121-122 through interactions with the printable medium 130 that includes the embedded machine-readable code 140. The system 100 enables private communication through the integration of the physical printable medium (sticker, label, postcard, etc.) 130 and digital messaging (e.g., the messages 161-162 of FIGS. 1 A-1C). In the system of the present embodiments, no personal contact information is shared between parties, nor any identity data is captured, therefore the users’ privacy is protected. [0082] With further reference to FIG. 5, the system 100 may include the client devices 121-122, the printable medium 130, the machine-readable code 140, the messaging servers 110, and one or more databases 545. The client devices 121-122 may be communicatively coupled to the messaging servers 110 via the network(s) 190 (one messaging server and its functional components are shown in FIG. 5). The client devices 121-122 and the messaging server 110 may be communicatively coupled to push service server 195 via the network(s) 190.

[0083] Although only two client devices 121-122 and one printable medium 130 are shown in FIG. 5, it should be noted that the system 100 may enable private messaging between multiple pairs of client devices with each pair using a printable medium with an embedded machine-readable code that includes a token parameter comprising a unique identifier. The printable medium 130 and the machine-readable code 140 may be similar to the printable medium 130 and the machine-readable code 140 of FIGS. 1A-1C, respectively.

[0084] The machine-readable code 140 may include a URL. The URL may include a host server name and a tokenized unique identifier as described above with reference to FIGS. 1A-1C. The client devices 121-122 may be electronic devices may be similar to the client devices 121-122 of FIGS. 1A-1C.

[0085] The messaging server 110 may include an application programming interface (API) manager 510, an application manager 530, and a database manager 540. The messaging server 110 may provide server-side functionality to the client devices through the network(s) 190. These functionality may include transmitting data to, receiving data from, processing data, video recording, video format conversation, data management, data storage, etc.

[0086] The API manager 510 may provide a programmatic interface to the application manager 530. The application manager 530 may be coupled to the database manager 540. The database manager 540 may be communicatively coupled to one or more databases 545 that store data associated with the printable media unique codes and messages data processed by the application manager 530. The API manager 510 may expose functions supported by the application manager 530 from a particular client device to another client device. These functions may include authentication of printable media codes, authentication of client devices, sending of notifications, sending of video media files, retrieval of messages, recording of video, sharing the recorded video to social networks, interacting with the push service server 195, etc.

[0087] The application manager 530 may host several applications and systems, including a message processing application 531, a token management application 533, a multimedia processing application 532, a private message exchange application 534, and an analytics application 535. The multi-media processing application 532 may facilitate various media conversation operations. Depending on a client device’s operating system, browser, display aspect ratio, display resolution, and/or device type, a different video format may be transmitted to/from a particular client. The multi-media processing application 532 may perform operations to generate interoperable video media for various client device types.

[0088] The token management application 533 may keep track of the tokens that have been generated and embedded in the printable media machine-readable codes. Each of these tokens are unique. For example, the token management application 533 may store a copy of the tokenized unique identifiers in the database(s) 545. It should be noted that each tokenized unique identifier is also included in a URL stored in the machine-readable codes 140 that are stored in the printable mediums 130. One of the functions of token management application 533 is to validate that a particular token that is transmitted by a client device, is valid and authenticated. The token management application 533 may only validate a token received from a client device when the token matches one of the tokenized unique identifiers that is stored in the database(s) 545 by the messaging server 110. The token management application 533 may also determine whether a token has not been used previously (i.e., the token has not been associated with a video message).

[0089] The private message exchange application 534 may correlate the client devices and their associated video messages with the unique tokenized unique identifier of the URL included in the machine-readable code 140. The private message exchange application 534 may maintain a message table and a tokenized unique identifier table. The private message exchange application 534 may store the tables and the associated data in the database(s) 545. It should be noted that the choice of data structure such as records, tables, graphs, etc. is a design decision.

[0090] The private message exchange application 534 may maintain a database (e.g., one of the databases 545) that includes the information regarding the printable media, video messages, and any associated metadata. It should be noted that the message, in some embodiments may be in the form of video, images, textual, or voice recordings.

[0091] The private message exchange application’s 534 database, in some embodiments, may link the sender’ s video message to the printable medium’ s tokenized unique identifier. The tokenized unique identifier, that is part of the URL included in the machine- readable medium 140, may be a pointer to the location in the tables and database within which content data are stored. The private message exchange application 534 may also communicate with the token management application 533 to keep track of the latest status of the token (e.g., not used, in-use, expired, etc.). [0092] When a recipient’s client device (e.g., the client device 121 or 122 of FIGS. 1 A- 1C) activates a particular machine-readable code, the private message exchange application 534 may update the database to link the client device to the particular video message. The database may maintain the relationship between video messages and the corresponding tokenized unique identifiers without keeping any identity data or users’ personal information. In some embodiments, the database also maintains the push subscription objects 197 (FIG. 1 A) generated by the push service server 195.

[0093] The Analytics application 535 may perform several data aggregation and contextual analysis on the message contents and payloads. Examples of data aggregation and analytics may include number of tokens scanned, number of tokens used, number and type of response messages received for a particular token, etc. Examples of the contextual analysis may include sentiment analysis of the video messages using Machine Learning, or video content analysis, etc.

[0094] Each client device 121-122 may be able to communicate and exchange messages with another client device and with the messaging server 110 via the network(s) 190. By scanning the machine-readable code 140 embedded in the printable medium 130, a client device may initiate communication to/from the messaging server 110, which allows recording and exchanging a video message with other client devices.

[0095] FIGS. 6A-6B are a flowchart illustrating an example process 600 for exchanging asynchronous video messaging between client devices using a printable medium without sharing personal identifiable information, according to various aspects of the present disclosure. The process 600, in some of the present embodiments, may be performed by a processor of a messaging server 110 of FIGS. 1 A-1C and 5.

[0096] With reference to FIGS. 6A-6B, a copy of several tokenized unique identifiers may be stored (at block 605) in a database accessible by the processor of a server, where each tokenized unique identifier is also a part of a URL that is stored in a machine-readable code embedded in a corresponding printable medium. For example, a copy of the tokenized unique identifiers may be stored in the database(s) 545 by the token management application 533 of the messaging server 110, as described above with reference to FIG. 5.

[0097] An anonymous request may be received (at block 610) from the browser of an electronic device to connect to the server, the first anonymous request includes a copy of a first URL stored in a first machine-readable code embedded in a corresponding printable medium and includes a first tokenized unique identifier. For example, the messaging server(s) 110 of FIGS. 1A-1C may receive a request from the browser of client device 121 to connect to the messaging server(s) 110 after the URL embedded in the computer-readable medium 140 is accessed, as described above with reference to stage 101 of FIG. 1A.

[0098] A determination may be made (at block 615) whether the first tokenized unique identifier is one of the tokenized unique identifiers stored in the database. For example, the token management application 533 of the messaging server 110 may search the database(s) 545 to determine whether a copy of the first tokenized unique identifier is stored in the database€, as described above with reference to FIG. 5. If not, the process 500 may end.

[0099] Otherwise, a determination may be made (at block 620) whether the first tokenized unique identifier is associated with a video message. If the first tokenized unique identifier is not associated with a video message, the electronic device, referred to herein as the first electronic device, is identified (at block 620) as the electronic device of the sender of the printable medium. The process 600 may then proceed to block 625, which is described below. Otherwise, the electronic device, referred to herein as the second electronic device, is identified (at block 655) as the electronic device of the sender of the printable medium. The process 600 may then proceed to block 660, which is described below.

[00100] As described above with reference to FIGS. 1A-1C, the computer-readable media 140 that are embedded in the printable media are not associated with any video messages prior to the first end user activating the computer-readable media 140. When the computer- readable media 140 is activated by an electronic device, the tokenized unique identifier that is in the URL stored in the computer-readable media 140 is received as a parameter of the URL by the messaging server(s) 110 from the browser of the electronic device. The messaging server(s) 110 may search the database(s) 545 and if the tokenized unique identifier is not associated with any video messages, the messaging server(s) 110 identify the electronic device as the electronic device of the sender of the printed medium (referred to herein as the first electronic device). The messaging server(s) 110 would then allow the first electronic device to send a video message, which is stored in the database(s) 545 as the video message that is associated with that particular tokenized unique identifier.

[00101] When the next electronic device (referred to herein as the second electronic device) activates the computer-readable media 140, the same tokenized unique identifier that is in the URL stored in the computer-readable media 140 is received as a parameter of the URL by the messaging server(s) 110 from the browser of the second electronic device. This time, the messaging server(s) 110 search the database(s) 545 and determine that the tokenized unique identifier is already associated with a video message. The messaging server(s) 110 identify the electronic device as electronic device of the receiver of the printed medium. The messaging server(s) 110 would then send the video message to the second electronic device.

[00102] At block 630, a request may be sent to the first electronic device to send a video message. For example, the messaging server(s) 110 of FIGS. 1 A-1C may send a request to the client device 121 to send the video message 161. A first video message may be received (at block 635) from the first electronic device. For example, the video message 161 may be received by the messaging server(s) 110 of FIGS. 1A-1C from the client device 121. The first video message may be stored (at block 640) as a video message associated with the first tokenized unique identifier. For example, the video message may be stored in the database(s) 545 as a video message associated with the first tokenized unique identifier, as described above with reference to FIG. 5.

[00103] A request may be sent (at block 645) to the first electronic device for authorization to receive an anonymous web push notification when a reply message to the first video message is received. For example, the messaging server(s) 110 may request for authorization for anonymous web push notification, as described above with reference to stage 204 of FIG. 2.

[00104] An authorization may be received (at block 650) from the first electronic device allowing the anonymous web push notification through a push service. For example, as described above with reference to stage 204 of FIG. 2, the messaging server(s) 110 may receive authorization for anonymous web push notification. The browser of the first electronic device may send a request to the push service server 195. The browser may receive a push subscription object from the push service server 195. The push subscription object may include identification information, such as the web address and other information regarding the push service server, that may allow the messaging server(s) 110 to contact the push service server 195. The messaging server(s) 110 may store the push subscription object to be able to send a future reply message to the first electronic device through the push service server 195. The process 600 may then end.

[00105] At block 660, the first video message may be retrieved using the first tokenized unique identifier. For example, the messaging server(s) 110 may search the database(s) 545 of FIG. 5 and may find the first video message as the video message associated with the first tokenized unique identifier. The first video message may be sent (at block 665) to the second electronic device. For example, as described above with reference to stage 102 of FIG. 1A, the video message 161 may be sent from the messaging server(s) 110 to the client device 122. [00106] A reply message to the first video message may be received (at block 670) from the second electronic device. For example, the second electronic device may send a reply message after one of the options 340-360 is selected in stage 303 of FIG. 3 and a video, audio, or textual reply message is sent from the client device 122 to the messaging server(s) 110.

[00107] The reply message may be stored (at block 675) as a reply message associated with the tokenized first unique identifier. For example, the reply message may be stored in the database(s) 545 of FIG. 5. The link to the reply message may be sent (at block 680) to the first electronic device through the push service server. For example, the messaging server(s) 110 may use the push notification object that was stored at block 650 to identify the push service server. The messaging server(s) 110 may send a link to the reply message to the first electronic device, through the push notification server, as described above with reference to stages 104- 105 of FIG. 1C and FIG. 4B. The process 600 may then end.

[00108] The specific operations of the process 600 may not be performed in the exact order shown and described. Furthermore, the specific operations described with reference to FIGS. 6A-6B may not be performed in one continuous series of operations in some embodiments, and different specific operations may be performed in different embodiments.

[00109] The followings describe several examples use cases of the present embodiments. FIG. 7 is a functional diagram illustrating an example of using the anonymous video messaging for sending flyers for direct mail advertising, according to various aspects of the present disclosure. With reference to FIG. 7, an advertiser, such as a real estate agent, may send flyers using the printable media 731-739. Each flyer may include a machine-readable code 741-749 with a URL that includes a tokenized unique identifier. For example, if the advertiser sends 5,000 flyers, there will be five thousand different tokenized unique identifiers. The uniqueness of the tokenized unique identifiers allows anonymous two-way messaging between the client device 121 of the sender of the flyers and the client devices 721-729 of the receivers of the flyers.

[00110] However, the advertiser is not required to have a unique video for each flyer. For example, if a real estate agent has 5 house listings, the client device 121 of the real estate agent may record five different video messages using the UI 200 described above with reference to FIG. 2 and store the video messages in the database(s) 545. The client device 121 may then use option 230 of FIG. 2 to selectively associate one of the 5 recorded video messages to each of the 5,000 tokenized unique identifiers, for example, based on the regions where the receipts and a listed house are located. [00111] The client device 721-729 of a flyer recipient may activate the machine- readable code 741-749 (e.g., by scanning a QR code, activating an NFC tag, etc.) included in the printable media 731-739, which results in the browser of the client device 721-729 to connect to the messaging server(s) 110 using the URL that is stored in the corresponding machine-readable code 741-749.

[00112] Each URL may include a tokenized unique identifier as a URL parameter. The messaging server(s) 110 may search the database(s) 545 to identify the video massage that corresponds to the received tokenized unique identifier. The video message stored for the tokenized unique identifier may then be provided to the client device 721-729 that has sent the tokenized unique identifier. The client device 721-729 may read the video message and may send a reply message, as described above with reference to FIG. 3.

[00113] FIG. 8 is a functional diagram illustrating an example of using the anonymous video messaging using official government issued postage stamps, according to various aspects of the present disclosure. With reference to FIG. 8, the postage stamps 831-839 may be printed and sold by a government. The printable media that include machine-readable code, in the example of FIG. 8, are the postage stamps 831-839. Each postage stamp 831-839 may include a machine-readable code 841-849, respectively.

[00114] As shown by the expanded view 810, each postage stamp may include a denomination 880, which is the inscribed value of the stamp. Instead of a denomination, the stamp may be undenominated, such as the Forever stamp of the United States, which is guaranteed to remain valid for first-class postage despite any and all future postal rate increases. The stamps 831-839 may or may not be sold for a higher price than the denomination 880 because of the inclusion of the machine-readable code and the ability to include a video message with each stamp. The expanded view 810 also shows that each postage stamp may include an illustration 815. For example, the illustration may be a commemorative image, image of an object, image of a person, etc.

[00115] The postage stamps 831-839 may be purchased (e.g., from the post offices) by the users of the client devices 811-819. Each individual postage stamp 831-839 may include an embedded machine-readable code 831-839 with a different tokenized unique identifier. The uniqueness of the tokenized unique identifiers may allow anonymous two-way messaging between the client device 811-819 of a purchaser of a postage stamp 831-839 and a client device 821-829 of a receiver of a postage stamp 831-839.

[00116] The purchasers of the postage stamps 831-839 may activate the machine- readable code 841-849 (e.g., by scanning a QR code, activating an NFC tag, etc.) included in the postage stamp 831-839, which results in the browser of the client device 821-829 to connect to the messaging server(s) 110 using the URL that is stored in the corresponding machine- readable code 841-849. The browser of each client device 821-829 may pass a tokenized unique identifier as a URL parameter to the messaging server(s). A client device 821-829 may then associate a video message to a tokenized unique identifier of a postage stamp 831-839, as described above with reference to FIG. 2. The messaging server(s) 110 may store the video message in the database(s) 545 as the video message associated with the tokenized unique identifier.

[00117] The postage stamp 831-839 may then be placed on different mailing objects 851-859 and be used as postage stamps for the mailing objects 851-859. The client device 821- 829 of a mail recipient may activate the machine-readable code 841-849 (e.g., by scanning a QR code, activating an NFC tag, etc.) included in the postage stamp 831-839, which results in the browser of the client device 821-829 to connect to the messaging server(s) 110 using the URL that is stored in the corresponding machine-readable code 841-849.

[00118] Each URL may include a tokenized unique identifier as a URL parameter. The messaging server(s) 110 may search the database(s) 545 to identify the video massage that corresponds to a received tokenized unique identifier. The video message stored for the tokenized unique identifier may then be provided to the client device 821-829 that has sent the tokenized unique identifier. The client device 821-829 may read the video message and may send a reply message to the sender of the mailing object 851-859, as described above with reference to FIG. 3.

[00119] FIG. 9 is a functional diagram illustrating an example of using the anonymous video messaging in a social event where participants may anonymously and privately video message with the meeting organizer or host, according to various aspects of the present disclosure. With reference to FIG. 9, participants of a social event may exchange information messages with the meeting organizer and/or meeting host. Examples of social events are corporate meetings, fundraising events, weddings, etc. A meeting host may be a master of ceremony, an event planner, bride & groom, a corporate marketing or public relationship (PR) person, etc.

[00120] In the example of FIG. 9, each event participant may have a corresponding client device 921-929. Each event participant may be provided with a printable medium 931- 939 with a corresponding machine-readable code 941-949. Each machine-readable code 941- 949 may store a URL that includes a tokenized unique identifier. The printable media 931-939 may be in the form of event registration or invitation card, event information sheet, table sitting cards, etc.

[00121] The event participants may use their client devices 921-929 to activate the machine-readable codes 941-949 embedded in printable media to initiate an anonymous and asynchronous communication with the client device 970 of the meeting organizer. The client devices 921-929 may send their message to the messaging server(S) 110, as described above with reference to stage 101 of FIG. 1A.

[00122] The messaging server(s) 110 may receive the messages from the participants. The messaging server(s) 110 may store the messages in the database(s) 545. The private message exchange of FIG. 9 may keep track of each message and its status using the tokenized unique identifiers without linking or keeping any identity data of the participants.

[00123] The meeting organizer or host may view and respond to the messages from the participants, as described above with reference to stages 102-105 of FIGS. 1A-1C. The meeting organizer or host may provide an individual personalized response to each participant, without sharing any personal contact information. The meeting organizer or host may alternatively respond to several participants with a group message, without sharing any personal contact information. For example, with reference to stage 303 of FIG. 3, selecting any of the options 340-360, in some embodiments, may provide an option to record a new message and an option to reply with a pre-recorded message (similar to the options 220 and 230 of FIG. 2). Through the disclosed anonymous message system, all parties may be able to establish asynchronous and anonymous communication in an easy and private way.

[00124] FIG. 10 is a functional diagram illustrating an example of sending each of several anonymous video messaging to multiple recipients and using push notification to correlate the received replies to each anonymous video message, according to various aspects of the present disclosure. With reference to FIG. 10, a merchant may have several different types of products for sale and may use the tokenized unique identifiers to associate a video message to each type of product. The merchant may then be interest to know the reply messages that are received correspond to which video message.

[00125] In the example, of FIG. 10, the merchant may be a seller of prepared meals, such as meals for people who subscribe to receive pre-made meals for certain type of diets, health food packages, meals made for occasions such as Christmas, Thanksgiving, etc. The merchant may include a video message for each type of food (e.g., to describe the nutrients in food or instructions for warming the food, etc. The merchant may be interested in knowing a reply message such as “the food needs more veggies” or “the food was too salty” was sent in response to the video for which type of food item.

[00126] With reference to FIG. 10, there may be n type of packaged food items 1051- 1059. The user of the client device 121 may have several of each type food items 1051-1059. Each packaged food item may have a corresponding printable medium 1031-1034, for example, attached to the food packaging (as shown), or on a flyer or a note card inside the food packaging. Each printable medium 1031-1034 may include a machine-readable medium 1041- 1044. Each machine-readable medium 1041-1044 may store a URL that may include a tokenized unique identifier as a URL parameter. It should be noted that each tokenized unique identifier is different than all other tokenized unique identifiers, including the tokenized unique identifiers that are attached to the same food item types.

[00127] The user of the client device 121 may generate n video messages, one for each type of food product 1051-1059. The client device 121 may include an identifier 195 such as “video message for salmon salad,” video message for halibut,” etc., in the display area 290 to be used for receiving notification, as described above with reference to stage 204 of FIG. 2. The client device 121 may associate the video messages for each type of food product 1051- 1059 with the tokenized unique identifiers in the machine-readable code 1041-1049, as described above with reference to stage 101 of FIG. 1A. The food item may then be sent to the users of client devices 1021-1029.

[00128] The client device 1021-1029 of a food item recipient may activate the machine- readable code 1041-1049 (e.g., by scanning a QR code, activating an NFC tag, etc.) included in the printable media 1031-1034 of their food item, which results in the browser of the client device 1021-1029 to connect to the messaging server(s) 110 using the URL that is stored in the corresponding machine-readable code 1041-1049.

[00129] Each URL may include a tokenized unique identifier as a URL parameter. The messaging server(s) 110 may search the database(s) 545 to identify the video massage that corresponds to the received tokenized unique identifier. The video message stored for the tokenized unique identifier may then be provided to the client device 1021-1029 that has sent the tokenized unique identifier. The client device 1021-1029 may read the video message and may send a reply message, as described above with reference to FIG. 3. The client device 1021-1029 may send a generic reply such as, the fish needs to be cooked more or please add less salt to the food that may not be easily correlated to a particular food item type.

[00130] However, since client device 121 had provided the identifier 290, the push notification for the reply message may be configured to indicate “you have received a reply message for video message for salmon salad,” “you have received a reply message for video message for halibut,” etc., that may facilitate corelating reply messages to a particular video message out of several video messages that the user of the client device 121 has associated with different tokenized unique identifier.

[00131] Some of the above-described features and applications are implemented as software processes that are specified as a set of instructions recorded on a computer readable storage medium (also referred to as computer readable medium). When these instructions are executed by one or more processing unit(s) (e.g., one or more processors, cores of processors, or other processing units), they cause the processing unit(s) to perform the actions indicated in the instructions. Examples of computer readable media include, but are not limited to, CD- ROMs, flash drives, RAM chips, hard drives, EPROMs, etc. The computer readable media does not include carrier waves and electronic signals passing wirelessly or over wired connections.

[00132] In this specification, the term “software” is meant to include firmware residing in read-only memory or applications stored in magnetic storage, which can be read into memory for processing by a processor. Also, in some embodiments, multiple software inventions can be implemented as sub-parts of a larger program while remaining distinct software inventions. In some embodiments, multiple software inventions can also be implemented as separate programs. Finally, any combination of separate programs that together implement a software invention described here is within the scope of the invention. In some embodiments, the software programs, when installed to operate on one or more electronic systems, define one or more specific machine implementations that execute and perform the operations of the software programs.

[00133] FIG. 11 conceptually illustrates an electronic system 1100 with which some embodiments of the invention (e.g., the servers, the client devices, etc., described above) are implemented. The electronic system 1100 can be used to execute any of the control, virtualization, or operating system applications described above. The electronic system 1100 may be a computer (e.g., desktop computer, personal computer, tablet computer, server computer, mainframe, blade computer etc.), smartphone, PDA, or any other sort of electronic device. Such an electronic system includes various types of computer readable media and interfaces for various other types of computer readable media. The electronic system 1100 includes a bus 1105, processing unit(s) 1110, a system memory 1120, a read-only memory (ROM) 1130, a permanent storage device 1135, input devices 1140, and output devices 1145. [00134] The bus 1105 collectively represents all system, peripheral, and chipset buses that communicatively connect the numerous internal devices of the electronic system 1100. For instance, the bus 1105 communicatively connects the processing unit(s) 1110 with the readonly memory 1130, the system memory 1120, and the permanent storage device 1135.

[00135] From these various memory units, the processing unit(s) 1110 retrieve(s) instructions to execute and data to process in order to execute the processes of the invention. The processing unit(s) may be a single processor or a multi-core processor in different embodiments.

[00136] The read-only-memory 1130 stores static data and instructions that are needed by the processing unit(s) 1110 and other modules of the electronic system. The permanent storage device 1135, on the other hand, is a read-and-write memory device. This device is a non-volatile memory unit that stores instructions and data even when the electronic system 1100 is off. Some embodiments of the invention use a mass-storage device (such as a magnetic or optical disk and its corresponding disk drive) as the permanent storage device 1135.

[00137] Other embodiments use a removable storage device (such as a flash drive, etc.) as the permanent storage device. Like the permanent storage device 1135, the system memory 1120 is a read-and-write memory device. However, unlike storage device 1135, the system memory is a volatile read-and-write memory, such as random access memory. The system memory stores some of the instructions and data that the processor needs at runtime. In some embodiments, the invention’s processes are stored in the system memory 1120, the permanent storage device 1135, and/or the read-only memory 1130. From these various memory units, the processing unit(s) 1110 retrieve instructions to execute and data to process in order to execute the processes of some embodiments.

[00138] The bus 1105 also connects to the input and output devices 1140 and 1145. The input devices enable the user to communicate information and select commands to the electronic system. The input devices 1140 include alphanumeric keyboards and pointing devices (also called “cursor control devices”). The input devices 1140 include cameras, optical sensors, NFC readers, and/or RFID readers. The output devices 1145 display images generated by the electronic system. The output devices include printers and display devices, such as cathode ray tubes (CRT) or liquid crystal displays (LCD). Some embodiments include devices, such as a touchscreen, that function as both input and output devices.

[00139] Finally, as shown in FIG. 11, bus 1105 also couples electronic system 1100 to a network 1125 through a network adapter (not shown). In this manner, the computer can be a part of a network of computers (such as a local area network (“LAN”), a wide area network (“WAN”), an Intranet, or a network of networks, such as the Internet. Any or all components of electronic system 1100 may be used in conjunction with the invention.

[00140] Some embodiments include electronic components, such as microprocessors, storage, and memory, that store computer program instructions in a machine-readable or computer-readable medium (alternatively referred to as computer-readable storage media, machine-readable media, or machine-readable storage media). Some examples of such computer-readable media include RAM, ROM, read-only compact discs (CD-ROM), recordable compact discs (CD-R), rewritable compact discs (CD-RW), read-only digital versatile discs (e.g., DVD-ROM, dual-layer DVD-ROM), a variety of recordable/rewritable DVDs (e g., DVD-RAM, DVD-RW, DVD+RW, etc ), flash memory (e g., SD cards, mini-SD cards, micro-SD cards, etc.), magnetic and/or solid state hard drives, read-only and recordable Blu-Ray® discs, ultra-density optical discs, any other optical or magnetic media. The computer-readable media may store a computer program that is executable by at least one processing unit and includes sets of instructions for performing various operations. Examples of computer programs or computer code include machine code, such as is produced by a compiler, and files including higher-level code that are executed by a computer, an electronic component, or a microprocessor using an interpreter.

[00141] While the above discussion primarily refers to microprocessor or multi-core processors that execute software, some embodiments are performed by one or more integrated circuits, such as application specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs). In some embodiments, such integrated circuits execute instructions that are stored on the circuit itself.

[00142] As used in this specification, the terms “computer”, “server”, “processor”, and “memory” all refer to electronic or other technological devices. These terms exclude people or groups of people. For the purposes of the specification, the terms display or displaying means displaying on an electronic device. As used in this specification, the terms “computer readable medium,” “computer readable media,” “machine readable medium,” “computer readable memory,” and “machine readable memory” are entirely restricted to tangible, non-transitory, physical objects that store information in a form that is readable by a computer. These terms exclude any wireless signals, wired download signals, and any other ephemeral or transitory signals.

[00143] In a first aspect, a system for anonymous asynchronous communication is provided. The system includes a server computing device that includes a processor. The system also includes several printable mediums. Each of the several printable mediums is embedded with a machine-readable code that stores a URL in a plurality of URLs. Each URL includes the name of the server computing device and a parameter that includes a tokenized unique identifier of a plurality of unique identifiers. The system also includes a non-transitory computer-readable storage communicatively couple to the processor that stores a copy of the plurality of tokenized unique identifiers. The processor configured to receive a first anonymous request from a web browser of a first electronic device to connect to the server computing device. The first anonymous request includes a copy of a first URL of the plurality of URLs. The first URL includes a parameter that includes a first tokenized unique identifier of the plurality of tokenized unique identifiers. The first URL is stored in a first machine- readable code embedded in a corresponding printable medium. The processor is configured to determine, in response to receiving the first anonymous request, that the first tokenized unique identifier is one of the plurality of tokenized unique identifiers stored in the non-transitory computer-readable storage and the first tokenized unique identifier is not associated with a video message; send a request to the first electronic device to send a first video message; receive the first video message from the first electronic device; store the first video message as a video message associated with the first tokenized unique identifier; send a request to the first electronic device for authorization to receive an anonymous web push notification through a push service when a reply message to the first video message is received; receive an authorization from the first electronic device subscribing the anonymous web push notification; receive a second anonymous request from a web browser of a second electronic device to connect to the server computing device, the second anonymous request comprising the first tokenized unique identifier; retrieve, in response to receiving the second anonymous request, the first video message associated with the first tokenized unique identifier; send a link to the second electronic device to access the first video message; receive a reply message to the first video message; store the reply message as a reply message associated with the tokenized first unique identifier; and send a notification that includes a link to the reply message to the first electronic device through the push service

[00144] In an embodiment of the first aspect, sending the request to the first electronic device for authorization to receive an anonymous web push notification through the push service includes: providing an option to the first electronic device to receive the anonymous web push notification; in response to a selection of the option by the first electronic device to receive the anonymous web push notification, subscribing the first electronic device to a push service server; receiving a push notification object from the push service server, the push notification object identifying the push service server; and storing the push notification object as the push notification object associated with the first tokenized unique identifier.

[00145] In another embodiment of the first aspect, sending the reply notification that includes the link to the reply message to the first electronic device through the push service includes identifying the push service server from the push notification object associated with the first tokenized unique identifier and sending the link to the reply message to the push service server identified by the push notification object.

[00146] In another embodiment of the first aspect, the processor is further configured to send a notification to the first electronic device through the push service after the second electronic device accesses the link to the first video message.

[00147] In another embodiment of the first aspect, the reply message includes one of a video message, an audio message, or a textual message.

[00148] In another embodiment of the first aspect, no email or phone number is provided by the first and second electronic devices to the server computing device.

[00149] In another embodiment of the first aspect, the parameter of the first URL includes a key value pair, where the key identifies the parameter as a tokenized unique identifier, and where the value comprises the first tokenized unique identifier as a string of characters.

[00150] In another embodiment of the first aspect, the second anonymous request includes at least one of an aspect ratio of a display screen associated with the second electronic device, a display resolution associated with the second electronic device, an operating system associated with the second electronic device, and a web browser associated with the second electronic device, the processor is further configured to convert a format of the first video message to a format compatible with the aspect ratio of the display screen associated with the second electronic device prior to transmitting the first video message to the second electronic device.

[00151] In another embodiment of the first aspect, the first machine-readable code is a printable bar code that includes the first URL.

[00152] In another embodiment of the first aspect, the printable bar code is a 2D barcode.

[00153] In another embodiment of the first aspect, the printable bar code is a QR code.

[00154] In another embodiment of the first aspect, the first anonymous request is received from the first electronic device after the first electronic device scans the bar code, and wherein the second anonymous request is received from the second electronic device after the second electronic device scans the bar code. [00155] In another embodiment of the first aspect, the first machine-readable code is an NFC tag storing the first URL.

[00156] In another embodiment of the first aspect, the first anonymous request is received from the first electronic device after the first electronic device activates the NFC tag, and wherein the second anonymous request is received from the second electronic device after the second electronic device activates the NFC tag.

[00157] In another embodiment of the first aspect, the first machine-readable code is an RFID tag storing the first URL.

[00158] In another embodiment of the first aspect, the first anonymous request is received from the first electronic device after the first electronic device activates the RFID tag, and wherein the second anonymous request is received from the second electronic device after the second electronic device activates the RFID tag.

[00159] In another embodiment of the first aspect, the printable medium corresponding to the first machine-readable code is one of a smart label with wireless connectivity or a printable label with flexible electronics.

[00160] In another embodiment of the first aspect, wherein the printable medium corresponding to the first URL comprises one of a customized image associated with a user of the first electronic device, a customized logo, a uniquely recognizable icon, an emoji, an animated emoji, or a memoji.

[00161] In another embodiment of the first aspect, the printable medium corresponding to the first machine-readable code is one of a customizable sticker, an affixable label, a gift tag, a gift note, a business card, a postcard, a gift tag, or a book.

[00162] In another embodiment of the first aspect, the printable medium corresponding to the first machine-readable code comprises a government issued postage stamp, the government issued postage stamp comprising a postage value, an illustration, and the first machine-readable code.

[00163] In another embodiment of the first aspect, the printable mediums are made of one or more of paper, fabric, or plastic.

[00164] In another embodiment of the first aspect, receiving the reply message includes: receiving a third anonymous request from the second electronic device to send the reply message to the first video message, the third anonymous request comprising a link to the reply message; and retrieving the reply message using the link to the reply message.

[00165] In another embodiment of the first aspect, receiving the reply message comprises receiving a third anonymous request from the second electronic device to send the reply message to the first video message, the third anonymous request comprising the reply message.

[00166] In another embodiment of the first aspect, the first video message is a Webbased Augmented Reality (AR), and the first machine-readable code triggers the Web-based AR.

[00167] In a second aspect, an automated method of asynchronous communication stores a plurality of unique uniform URLs. Each URL includes the name of a host server and a token parameter that includes a unique identifier. Each URL is configured to be stored in a machine-readable code embedded in a corresponding printable medium. The method receives a first anonymous request at the host server to associate a first video message from a first electronic device with a first URL stored in a machine-readable code embedded in a corresponding printable medium. The method, in response to the first request, determines that the first URL is one of the stored URLs and the first URL is not associated with a video message. The method sends a request to the first electronic device to send the first video message. The method receives the first video message from the first electronic device. The method stores the first video message as a video message associated with the first URL. The method receives a second anonymous request from a second electronic device to receive the first video message, the second anonymous request includes the first URL. The method, in response to receiving the second request, identifies the first video message as the video message associated with the first URL using the unique parameter of the token parameter of the first URL. The method transmits the first video message to the second electronic device. The method receives a third anonymous request from the second electronic device to associate a second video message with the first URL, the third request includes the second video message and the first URL. The method stores the second video message as a reply video message associated with the first URL.

[00168] An embodiment of the second aspect receives a fourth anonymous request from the first electronic device to receive the reply video message associated with the first URL, identifies the second video message as the reply video message associated with the first URL, and transmits the second video message to the first electronic device.

[00169] In an embodiment of the second aspect, the second request includes at least an aspect ratio of a display screen associated with the second electronic device, a display resolution associated with the second electronic device, an operating system associated with the second electronic device, or a web browser associated with the second electronic device. The method further includes converting a format of the first video message to a format compatible with the aspect ratio of the display screen associated with the second electronic device prior to transmitting the first video message to the second electronic device.

[00170] In another embodiment of the second aspect, the first URL is embedded in the corresponding printable medium as a printable bar code.

[00171] In another embodiment of the second aspect, the printable bar code is a two- dimensional barcode.

[00172] In another embodiment of the second aspect, the printable bar code is a QR code.

[00173] In another embodiment of the second aspect, the printable medium corresponding to the first URL is a smart label with wireless connectivity, wherein the printable medium embeds the first URL.

[00174] In another embodiment of the second aspect, the first URL is embedded in the corresponding printable medium as an RFID tag.

[00175] In another embodiment of the second aspect, the first URL is embedded in the corresponding printable medium as an NFC tag.

[00176] In another embodiment of the second aspect, the printable medium corresponding to the first URL includes a personalized image associated with a user of the first electronic device.

[00177] In another embodiment of the second aspect, the printable medium corresponding to the first URL includes a personalized image that includes an emoji, an animated emoji, or a memoji.

[00178] In another embodiment of the second aspect, the printable medium corresponding to the first URL includes a personalized logo or a uniquely recognizable icon.

[00179] Another embodiment of the second aspect further includes receiving a third anonymous request from a third electronic device to associate a video message with the first URL after the first video message is stored as the video message associated with the first URL; determining that the first URL is associated with the first video message; and sending a message to the third electronic device rejecting the third anonymous request.

[00180] In another embodiment of the second aspect, the printable medium corresponding to the first URL is a customizable sticker, an affixable label, a stamp, a gift tag, or a gift note.

[00181] In another embodiment of the second aspect, the printable medium corresponding to the first URL is a signage associated with a physical location. [00182] In another embodiment of the second aspect, the first anonymous request is received from the first electronic device after the first electronic device scans the machine- readable code that stores the first URL.

[00183] In another embodiment of the second aspect, the first anonymous request is received from a third electronic device to associate the first electronic device with the machine- readable code that stores the first URL, wherein the first electronic device receives a link from the third electronic device to send the first video message to the host server.

[00184] While the invention has been described with reference to numerous specific details, one of ordinary skill in the art will recognize that the invention can be embodied in other specific forms without departing from the spirit of the invention. In addition, a number of the figures conceptually illustrate processes. The specific operations of these processes may not be performed in the exact order shown and described. The specific operations may not be performed in one continuous series of operations, and different specific operations may be performed in different embodiments. Furthermore, the process could be implemented using several sub-processes, or as part of a larger macro process.

[00185] The above description presents the best mode contemplated for carrying out the present embodiments, and of the manner and process of practicing them, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which they pertain to practice these embodiments. The present embodiments are, however, susceptible to modifications and alternate constructions from those discussed above that are fully equivalent. Consequently, the present invention is not limited to the particular embodiments disclosed. On the contrary, the present invention covers all modifications and alternate constructions coming within the spirit and scope of the present disclosure. For example, the steps in the processes described herein need not be performed in the same order as they have been presented and may be performed in any order(s). Further, steps that have been presented as being performed separately may in alternative embodiments be performed concurrently. Likewise, steps that have been presented as being performed concurrently may in alternative embodiments be performed separately.

Claims

CLAIMS WHAT IS CLAIMED IS:

1. A system for anonymous asynchronous communication, the system comprising: a server computing device comprising a processor; a plurality of printable mediums, each of the plurality of printable mediums embedded with a machine-readable code storing a uniform resource locator identifier (URL) in a plurality of URLs, each URL comprising a name of the server computing device and a parameter comprising a tokenized unique identifier of a plurality of unique identifiers; a non-transitory computer-readable storage communicatively couple to the processor and storing a copy of the plurality of tokenized unique identifiers; the processor configured to: receive a first anonymous request from a web browser of a first electronic device to connect to the server computing device, the first anonymous request comprising a copy of a first URL of the plurality of URLs, the first URL comprising a parameter comprising first tokenized unique identifier of the plurality of tokenized unique identifiers, the first URL stored in a first machine-readable code embedded in a corresponding printable medium; determine, in response to receiving the first anonymous request, that the first tokenized unique identifier is one of the plurality of tokenized unique identifiers stored in the non-transitory computer-readable storage and the first tokenized unique identifier is not associated with a video message; send a request to the first electronic device to send a first video message; receive the first video message from the first electronic device; store the first video message as a video message associated with the first tokenized unique identifier; send a request to the first electronic device for authorization to receive an anonymous web push notification through a push service when a reply message to the first video message is received; receive an authorization from the first electronic device subscribing the anonymous web push notification; receive a second anonymous request from a web browser of a second electronic device to connect to the server computing device, the second anonymous request comprising the first tokenized unique identifier; retrieve, in response to receiving the second anonymous request, the first video message associated with the first tokenized unique identifier; send a link to the second electronic device to access the first video message; receive a reply message to the first video message from the second electronic device; store the reply message as a reply message associated with the tokenized first unique identifier; and send a notification comprising a link to the reply message to the first electronic device through the push service.

2. The system of claim 1, wherein sending the request to the first electronic device for authorization to receive an anonymous web push notification through the push service comprises: providing an option to the first electronic device to receive the anonymous web push notification; in response to a selection of the option by the first electronic device to receive the anonymous web push notification, subscribing the first electronic device to a push service server; receiving a push notification object from the push service server, the push notification object identifying the push service server; and storing the push notification object as the push notification object associated with the first tokenized unique identifier.

3. The system of claim 2, wherein sending the reply notification comprising the link to the reply message to the first electronic device through the push service comprises: identifying the push service server from the push notification object associated with the first tokenized unique identifier; and sending the link to the reply message to the push service server identified by the push notification object.

4. The system of claim 1, wherein the processor is further configured to: send a notification to the first electronic device through the push service after the second electronic device accesses the link to the first video message.

5. The system of claim 1, wherein the reply message comprises one of a video message, an audio message, or a textual message.

6. The system of claim 1, wherein no email or phone number is provided by the first and second electronic devices to the server computing device.

7. The system of claim 1, wherein the parameter of the first URL comprises a key value pair, wherein the key identifies the parameter as a tokenized unique identifier, and wherein the value comprises the first tokenized unique identifier as a string of characters.

8. The system of claim 1, wherein the second anonymous request comprises at least one of an aspect ratio of a display screen associated with the second electronic device, a display resolution associated with the second electronic device, an operating system associated with the second electronic device, and a web browser associated with the second electronic device, wherein the processor is further configured to: convert a format of the first video message to a format compatible with the aspect ratio of the display screen associated with the second electronic device prior to transmitting the first video message to the second electronic device.

9. The system of claim 1, wherein the first machine-readable code is a printable bar code that includes the first URL.

10. The system of claim 9, wherein the printable bar code is a two-dimensional (2D) barcode.

11. The system of claim 9, wherein the printable bar code is a quick response (QR) code.

12. The system of claim 9, wherein the first anonymous request is received from the first electronic device after the first electronic device scans the bar code, and wherein the second anonymous request is received from the second electronic device after the second electronic device scans the bar code.

13. The system of claim 1, wherein the first machine-readable code is a near field communication (NFC) tag storing the first URL.

14. The system of claim 13, wherein the first anonymous request is received from the first electronic device after the first electronic device activates the NFC tag, and wherein the second anonymous request is received from the second electronic device after the second electronic device activates the NFC tag.

15. The system of claim 1, wherein the first machine-readable code is a radio frequency identification (RFID) tag storing the first URL.

16. The system of claim 15, wherein the first anonymous request is received from the first electronic device after the first electronic device activates the RFID tag, and wherein the second anonymous request is received from the second electronic device after the second electronic device activates the RFID tag.

17. The system of claim 1, wherein the printable medium corresponding to the first machine-readable code is one of a smart label with wireless connectivity or a printable label with flexible electronics.

18. The system of claim 1, wherein the printable medium corresponding to the first URL comprises one of a customized image associated with a user of the first electronic device, a customized logo, a uniquely recognizable icon, an emoji, an animated emoji, or a memoji.

19. The system of claim 1, wherein the printable medium corresponding to the first machine-readable code is one of a customizable sticker, an affixable label, a gift tag, a gift note, a business card, a postcard, a gift tag, or a book.

20. The system of claim 1, wherein the printable medium corresponding to the first machine-readable code comprises a government issued postage stamp, the government issued postage stamp comprising a postage value, an illustration, and the first machine-readable code.

21. The system of claim 1, wherein the printable mediums are made of one or more of paper, fabric, or plastic.

22. The system of claim 1, wherein receiving the reply message comprises: receiving a third anonymous request from the second electronic device to send the reply message to the first video message, the third anonymous request comprising a link to the reply message; and retrieving the reply message using the link to the reply message.

23. The system of claim 1, wherein receiving the reply message comprises: receiving a third anonymous request from the second electronic device to send the reply message to the first video message, the third anonymous request comprising the reply message.

24. The system of claim 1, wherein the first video message is a Web-based Augmented Reality (AR), and wherein the first machine-readable code triggers the Web-based AR.