Patent Application
20230021327
The disclosure relates to the field of computer-based communication systems, routing and optimization, and artificial intelligent systems, and more particularly to the field of computerized routing and optimization systems using a promotional rewards wheel.
Business enterprises often communicate with their customers in a siloed non-contextual approach offering one generic customer experience for in-store interactions; another for Internet website accessed via a fixed compute device; and yet another experience from a mobile device. In each case, generic communications modes are made available to the customer requiring them to navigate various screens and options when all they really want is assistance with their pre- or post-sales transaction from a resource knowing their unique history using a communication mode of their choosing. Moreover, when a customer does require assistance with their transaction, they want to accomplish it without introducing unnecessary delay while using their preferred mode of communication, whether text, chat or email. From the business enterprise perspective, they are often already heavily invested in traditional call centers systems and human resources (agents) and therefore drive their customers to these resources when oftentimes better resources exist outside the call center. The end result is often a near-term suboptimal experience for the customer and potential loss of sale and long-term viability for the business.
What is needed is a system and method for optimized omnichannel customer interaction utilizing text-based communication resulting in short- and long-term business competitive advantage and viability.
Accordingly, the inventor has conceived, and reduced to practice, a system and method for delivering promotional rewards to a customer mobile device comprising a promotional reward wheel, a media server, and messaging application operating on the customer's mobile device. A customer interacts with the promotional reward wheel and the system captures that interaction and responsive to the promotional reward that was won by the interaction, generates a message on the customer's mobile device with a means to claim the reward by sending the generated message to the appropriate message endpoint.
The system may be configured to further facilitate interactions by utilizing a short message service (SMS) authorization methodology wherein interaction with a CTA on a smartphone initiates a series of SMS messages back and forth to a server which authorizes communications between the user of a smartphone and a third party associated with the CTA. When a user interacts with the CTA on his or her smartphone, the CTA causes the smartphone to generate a first SMS on the smartphone which has been pre-filled with an SMS address code and a CTA identifier. When the first SMS is sent from the smartphone, the server at the address code receives the first SMS, captures the CTA identifier and phone number of the smartphone, and sends a second SMS back to the smartphone with a link and a request for authorization to send the phone number to a third party for communications. Clicking on the link in the second SMS sends a third SMS back to the server at the address code authorizing the transmission of the phone number to a third party. In this way, authorization for capture of the user's phone number and establishment of communications with a third party can be established simply by having the user click on two automatically-generated SMS messages without having to otherwise enter any data on the smartphone. This method works universally on all smartphones with SMS technology without having to install additional applications. Note that while SMS technology is the primary example used herein, the invention is not so limited and other forms of mobile device interactions may be used, provided that an identifier for the mobile device can be obtained from the interaction (e.g., multi-media message service (MMS) messages, email addresses from email headers, caller ID from phone calls, caller ID from VOIP calls, etc.).
According to a preferred embodiment, a system for offering promotional rewards using a rewards wheel is disclosed, comprising: an enterprise database, the enterprise database comprising a plurality of promotional rewards and a plurality of enterprise endpoints; a mobile device comprising at least a plurality of programming instructions stored in a memory of, and operating on at least one processor of, a computing device, wherein the plurality of programming instructions, when operating on the at least one processor, causes the computing device to: display a promotional rewards wheel and an interactive button, wherein interacting with the button causes the rewards wheel to spin and land on a promotional reward; send promotional reward data to a server; receive and display a text-based message comprising a promotional reward and an enterprise endpoint; and connect a user to the enterprise endpoint when the user sends the received text-based message to the enterprise endpoint; and a server comprising at least a plurality of programming instructions stored in a memory of, and operating on at least one processor of, a computing device, wherein the plurality of programming instructions, when operating on the at least one processor, causes the computing device to: receive the promotional reward data; parse the promotional reward data to identify the promotional reward; retrieve enterprise endpoint data from the enterprise database, the enterprise endpoint data associated with the promotional reward; generate the text-based message, the text-based message comprising the promotional reward and an enterprise endpoint; and send the text-based message to the mobile device.
According to another preferred embodiment, a method for offering promotional coupons using a rewards wheel is disclosed, comprising the steps of: displaying a promotional rewards wheel and an interactive button, wherein interacting with the button causes the rewards wheel to spin and land on a promotional reward; sending promotional reward data to a server; receiving and displaying a text-based message comprising a promotional reward and an enterprise endpoint; connecting a user to the enterprise endpoint when the user sends the received text-based message to the enterprise endpoint; receiving the promotional reward data; parsing the promotional reward data to identify the promotional reward; retrieving enterprise endpoint data from the enterprise database, the enterprise endpoint data associated with the promotional reward; generating the text-based message, the text-based message comprising the promotional reward and the enterprise endpoint; and sending the text-based message to the mobile device.
According to an aspect of an embodiment, the promotional rewards wheel is divided into a plurality of sections.
According to an aspect of an embodiment, the plurality of sections are the same size.
According to an aspect of an embodiment, the plurality of sections are different sizes.
According to an aspect of an embodiment, an indicator directed at the rewards wheel is displayed on the mobile device.
According to an aspect of an embodiment, the promotional reward data comprises a promotional reward.
According to an aspect of an embodiment, the interactive button comprises a word or phrase that prompts the mobile device user to interact with the button.
According to an aspect of an embodiment, the text-based message is displayed in a default messaging application operating on the mobile device.
According to an aspect of an embodiment, the text-based message is a pre-filled SMS or MMS message.
The accompanying drawings illustrate several aspects and, together with the description, serve to explain the principles of the disclosed embodiments. It will be appreciated by one skilled in the art that the particular arrangements illustrated in the drawings are merely exemplary, and are not to be considered as limiting of the scope of the claims herein in any way.
The inventor has conceived and reduced to practiced, a system and method for delivering promotional rewards to a customer mobile device comprising a promotional reward wheel, a media server, and messaging application operating on the customer's mobile device. A customer interacts with the promotional reward wheel and the system captures that interaction and responsive to the promotional reward that was won by the interaction, generates a message on the customer's mobile device with a means to claim the reward by sending the generated message to the appropriate message endpoint.
One or more different aspects may be described in the present application. Further, for one or more of the aspects described herein, numerous alternative arrangements may be described; it should be appreciated that these are presented for illustrative purposes only and are not limiting of the aspects contained herein or the claims presented herein in any way. One or more of the arrangements may be widely applicable to numerous aspects, as may be readily apparent from the disclosure. In general, arrangements are described in sufficient detail to enable those skilled in the art to practice one or more of the aspects, and it should be appreciated that other arrangements may be utilized and that structural, logical, software, electrical and other changes may be made without departing from the scope of the particular aspects. Particular features of one or more of the aspects described herein may be described with reference to one or more particular aspects or figures that form a part of the present disclosure, and in which are shown, by way of illustration, specific arrangements of one or more of the aspects. It should be appreciated, however, that such features are not limited to usage in the one or more particular aspects or figures with reference to which they are described. The present disclosure is neither a literal description of all arrangements of one or more of the aspects nor a listing of features of one or more of the aspects that must be present in said arrangements.
Headings of sections provided in this patent application and the title of this patent application are for convenience only, and are not to be taken as limiting the disclosure in any way.
Devices that are in communication with each other need not be in continuous communication with each other, unless expressly specified otherwise. In addition, devices that are in communication with each other may communicate directly or indirectly through one or more communication means or intermediaries, logical or physical.
A description of an aspect with several components in communication with each other does not imply that all such components are required. To the contrary, a variety of optional components may be described to illustrate a wide variety of possible aspects and in order to more fully illustrate one or more aspects. Similarly, although process steps, method steps, algorithms or the like may be described in a sequential order, such processes, methods and algorithms may generally be configured to work in alternate orders, unless specifically stated to the contrary. In other words, any sequence or order of steps that may be described in this patent application does not, in and of itself, indicate a requirement that the steps be performed in that order. The steps of described processes may be performed in any order practical. Further, some steps may be performed simultaneously despite being described or implied as occurring non-simultaneously (e.g., because one step is described after the other step). Moreover, the illustration of a process by its depiction in a drawing does not imply that the illustrated process is exclusive of other variations and modifications thereto, does not imply that the illustrated process or any of its steps are necessary to one or more of the aspects, and does not imply that the illustrated process is preferred. Also, steps are generally described once per aspect, but this does not mean they must occur once, or that they may only occur once each time a process, method, or algorithm is carried out or executed. Some steps may be omitted in some aspects or some occurrences, or some steps may be executed more than once in a given aspect or occurrence.
When a single device or article is described herein, it will be readily apparent that more than one device or article may be used in place of a single device or article. Similarly, where more than one device or article is described herein, it will be readily apparent that a single device or article may be used in place of the more than one device or article.
The functionality or the features of a device may be alternatively embodied by one or more other devices that are not explicitly described as having such functionality or features. Thus, other aspects need not include the device itself.
Techniques and mechanisms described or referenced herein will sometimes be described in singular form for clarity. However, it should be appreciated that particular aspects may include multiple iterations of a technique or multiple instantiations of a mechanism unless noted otherwise. Process descriptions or blocks in figures should be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of various aspects in which, for example, functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those having ordinary skill in the art.
The media server 200 acts as the communication channel interface between client and customer devices, passing various forms of communications media (emails, texts, traditional telephone, VOIP, etc.) between the devices. The routing manager 300 selects an appropriate routing for incoming and outgoing communications based on information from the session manager. The session manager 400 creates and manages each communication session between a client and customer by creating a session initiation protocol (SIP) communication sessions for each communication between a client and customer using the CTA identifier, the customer's contact information, and information about the communications medium being used. The session manager 400 monitors and logs the session, and terminates the session when the communication ends. The campaign manager 500 provides the client with an interface through which the client may create automated advertising campaigns which may be dynamically adjusted based on feedback from customer interactions with CTAs and other information. The positioning manager 600 creates campaign instances from a campaign, and automatically determines where and when to place CTAs for each campaign instance depending on scheduling, targeting, and budgeting goals. The databases 700 store campaign information, client information, and customer information. The token manager 800 provides an interface for design and generation of PNFTs, establishment of automation rules for interactions with PNFTS, and verification of identities using PNFTs.
In this embodiment, an SMS-based authorization handler 210 is shown as part of the media server 200. The SMS-based authorization handler 210 handles the data use authorization (also called an “opt-in”) process via text messages. Using the SMS-based authorization handler 210, the system is configured to facilitate interactions by utilizing a short message service (SMS) authorization methodology wherein interaction with a CTA on a smartphone initiates a series of SMS messages back and forth to the media server 200 which authorizes communications between the user of a smartphone (a customer) and a third party associated with the CTA (a client). When the customer interacts with the CTA on his or her smartphone, the CTA accesses the smartphone's text messaging application and causes the smartphone to generate a first SMS on the smartphone which has been pre-filled with an SMS address code for the SMS-based authorization handler 210 of the media server 200 and a CTA identifier. When the first SMS is sent from the smartphone, the SMS-based authorization handler 210 of the media server 200 receives the first SMS, captures the CTA identifier and phone number of the smartphone, and sends a second SMS back to the smartphone containing a link and a request for authorization to send the phone number to a third party for communications (e.g., “To authorize Company X to call you back on phone number Y to purchase product Z, click here.”). Clicking on the link in the second SMS sends a third SMS back to the SMS-based authorization handler 210 of the media server 200 authorizing the transmission of the phone number to a client so that the client may contact the customer. In this way, authorization for capture of the customer's phone number and establishment of communications with a client can be established simply by having the customer click on two automatically-generated SMS messages without having to otherwise enter any data on the smartphone. This method works universally on all smartphones with SMS technology without having to install additional applications. The data use approval confirmation received by the customer is logged and passed to other components of the system (e.g., to the session manager via the data masker) to confirm authorization to use private information. Note that while SMS technology is the primary example used herein, the invention is not so limited and other forms of mobile device interactions may be used, provided that an identifier for the mobile device can be obtained from the interaction (e.g., multi-media message service (MMS) messages, email addresses from email headers, caller ID from phone calls, caller ID from VOIP calls, etc.).
A data masker 220 operating on the media server 200 preserves the privacy of both client and customer by masking the phone number, email addresses, and other identifying information of the parties until they voluntarily exchange confidential information between themselves via the communications medium. As the data masker 220 is privy to the private information of the parties, it can establish a connection with each party separately using the private information, and they join the parties together via a real-time communications medium (e.g., phone) without having to pass the private information to each of the parties or can forward non-real-time communications between the parties (e.g., emails) while stripping identifying information from the transmitted messages (e.g., from the email headers).
The media processor 230 converts audio and image communications media to text, and passes through text communications to the session manager 400. For example, where the interaction with the CTA is in audio form (e.g., a call to a phone number printed on the CTA), the audio from the interaction may be sent to an automated speech recognition (ASR) processor 231 (also known as a speech-to-text (STT) processor) to convert the speech from the audio into text. Where the interaction with the CTA is a transmitted image (e.g., a photo of the CTA sent by MMS), the image from the interaction may be sent to an optical character recognition (OCR) processor 232 to extract any text in the image (e.g., the CTA identifier). The converted text is then sent to the NLP engine to be processed as with the interactions in text form. Any text interactions with the CTA (e.g., text messages), are passed through to the session manager 400.
User device gateways 240a, 240b on both the client side and customer side both comprise a plurality of interfaces 241a-244a, 241b-244b receive and transmit communications to and from client and customer devices. For simplicity and clarity, a single user device gateway is shown on the client end 240a and on the customer end 240b, each comprising an email interface 241A,b, a short message service (SMS) handler 242a,b, a plain old telephone (POTS, or traditional telephone line) interface 243a,b, and a voice-over-Internet-protocol (VOIP) interface 244a,b. While these are the most common media interfaces, the user device gateways 240a,b may have other such communications media interfaces and there may be a plurality of user device gateways 240a,b on either side.
The routing manager 300 selects an appropriate routing for incoming and outgoing communications based on information from the session manager. In this embodiment, the media server 200 sends connection information to the session manager 400. Where a customer has interacted with a CTA, the connection information initially comprises a communications medium (e.g., mobile phone service), the customer's contact information for that communications medium (e.g., a phone number), and an identifier for the CTA (e.g., a CTA identification number or string). The session manager initiates a session initiation protocol (SIP) session by issuing an SIP invitation to the routing manager 300. The routing manager 300 receives the SIP invitation, retrieves one or more routing policies from the databases 700 using a route selector 310, determines an appropriate routing for the communication (e.g., to salesperson X at company Y who handles sales of the type of product advertised by the identified CTA), and sends the routing information to the media server 200, which proceeds to establish the connection.
Where a customer has interacted with a CTA, an identifier for the CTA is obtained from one of a variety of methods (e.g., an identifier embedded in a link, a call to certain phone numbers designated to handle CTAs of a certain type, a CTA identifier in a text message from the customer, etc.). In this embodiment, where the interaction with the CTA is in text form (e.g., clicking on a website link CTA generates a pre-populated SMS containing the CTA identifier on the customer's mobile device which is sent to the media server), the text from the interaction with the CTA is sent to a natural language processing engine 420 which parses the text to extract the CTA ID, and possible other contextual information (such as the terms “lease” or “buy,” which may determine to which department a lead is sent), along with the customer contact information (in this example, the phone number of the customer's mobile device from which the SMS was sent) and the communications medium (in this case, a return phone call to the phone number of the customer in response to the SMS).
Thus, the connection information initially comprises a communications medium (e.g., mobile phone service), the customer's contact information for that communications medium (e.g., a phone number), and an identifier for the CTA (e.g., a CTA identification number or string). Using the CTA identifier, the campaign and target information associated with the CTA identifier are retrieved from a campaign database for the relevant client, and a target selector 430 selects an appropriate client target to receive the communication depending on the connection information (e.g., a salesperson X in department Y at company Z who specializes in the type of product advertised by the CTA). After the target is selected, a communications manager 440 of the session manager 400 initiates a session initiation protocol (SIP) session by issuing an SIP invitation to the routing manager 300. After creation of the session, the communication manager 440 monitors and logs the session, and terminates the session when the communication ends.
Should the initially-selected target not be available, the target selector 430 may initiate a routing script that queries the databases 700 to determine next target resource. This process may be repeated until all potential targets of the client in the campaign are exhausted (i.e. no client resource is available to accept the call for that CTA). In that event, the voice call may be routed to a voicemail system corresponding to one of the client's resources or a general voicemail box. A notification of the failed attempt to connect with a live client resource may be sent to the client.
The campaign design interface 510 comprises one or more campaign design APIs 511 which allow clients to set up campaigns comprising products and services, target audiences, rules, schedules, budgets, and the like. Each campaign design API 511 provides one or more aspects of the interface such as a graphical interface, rule creation tools, budgeting tools, target audience selection tools, etc., and the collection of the campaign design APIs 511 allows the client to define complete marketing campaigns, which are stored in the campaign database of the databases 700. If PNFTs are used, the PNFT design API extension 512 allows access to a similar PNFT design interface in the token manager 800 for creation and implementation of PNFTs.
Once a marketing campaign is created and implemented, the dynamic advertising engine 520 can be configured to make automatic changes to the campaign (or an aspect of a campaign) based on feedback from interaction with CTAs and other information such as product or service sales numbers. In some embodiments, ad variants may be generated by dynamic advertisement engine 520. In some embodiments, ad variants may be generated semi-autonomously with input from business personnel. For example, dynamic advertisement engine 520 may receive data associated with an ad campaign and analyze it, and based on the analytic data it may suggest an element of an advertisement to be altered, which can then be reviewed and implemented by a client representative such as a business marketing manager. In some embodiments, ad variants may be generated autonomously. For example, dynamic advertisement engine 520 may receive analytic data associated with an ad campaign and based on the received data it may suggest an element of an advertisement to be altered, which can be automatically applied to the ad via the ad campaign data stored in campaign database 730.
A purpose of utilizing ad variants is to gather useful data about the efficacy, efficiency, and profitability of a given advertisement and/or an ad campaign. Implementing two similar ads with the only difference between the two being a single element alteration (i.e., A/B testing) can allow businesses to understand how elemental choices for an advertisement affect customer interaction. For example, an ad campaign for a hiking boot may be developed with the tagline “Reach New Heights With These Boots,” and a variant ad may be developed the tagline “Tough On The Mountain, Gentle On Your Feet,” wherein the only difference between both ads is the tagline. Both the baseline ad and the variant ad can then be deployed and customer engagement data with both the baseline and variant can be monitored and analyzed to determine which of the baseline or the variant led to better outcomes for the business running the ads and/or ad campaign. In some embodiments, ad campaign data may include a test plan for configuring the deployment of two variant advertisements. For example, a test plan may describe what element is to be tested and subsequently altered, the goals of the test plan (e.g., improving conversion rates), initial state of advertisement (i.e., baseline metric that describes current state of advertisement), the order of element alterations to be made, test design (e.g., how long to test the variants, which devices to test on, etc.) and the like. In some embodiments, test plans may be received, retrieved, or otherwise obtained from campaign database 730 by dynamic advertisement engine 520 as an input into suggesting element alterations.
According to some embodiments, the analytic module 522 may receive, retrieve, or otherwise obtain a plurality of data such as, but not limited to, details of interactions with CTAs, media stream data, ad campaign data, survey data, and business data, and may process the plurality of data in order to determine the efficacy of a given advertisement and/or ad campaign. In some embodiments, analytic module 522 may receive data pertaining to at least two advertisements comprising a baseline advertisement and a variant advertisement, and determine which of the two advertisements produced better results based upon analysis of the received data.
According to some embodiments, analytical data such as, for example, a determination of a better advertisement between at least two advertisements, may be received, retrieved, or otherwise obtained by dynamic advertisement engine 520. Dynamic advertisement engine 520 and/or alteration module 521 may process the analytical data together with ad campaign data (e.g., test plan information) in order to suggest at least one advertisement element to alter in order to form a new variant of an advertisement. For example, data analytics suggest that a first variant of a baseline advertisement was better at leading to product sales than the baseline version of the advertisement, and responsive to this analysis alteration module 521 can suggest an element alteration to the first variant to form a second variant. The first and second advertisement variants may then be deployed to various platforms via position manager 600 and the process of collecting data related to advertisement engagement/interaction can begin again using the first and second variant, wherein after statistically relevant data is collected, analytic module 522 may make a determination of whether the first variant or the second variant was better. The determination of a “better” advertisement can be based on statistically significant metrics such as, for example, ad clicks and conversion rates. In the case that the differences between two advertisements are statistically insignificant, dynamic advertisement engine 520 may suggest no alterations to an element. In some embodiments, the element to be altered is the same type of element (e.g., the tagline is altered between two advertisements).
In some embodiments, dynamic advertisement engine 520 may receive, retrieve, or otherwise obtain 3rd party data to be used as an input when making element alteration suggestions. Because marketing is such a vital component of any business within any industry, there is a lot of market research data available regarding advertisement content and configuration which may be used by dynamic advertisement engine 520 to determine appropriate and effective element alterations. For example, studies have shown that an advertisement with a red call-to-action button outperforms a green call-to-action button by about 21%. The large difference in click rate between such a minor change shows the importance of testing different variants of a given advertisement in order to maximize customer engagement and improve conversion rates.
The positioning manager 600 receives notification of the initiation of a campaign from the campaign manager, retrieves relevant information about the campaign from the databases 700, and creates one or more campaign instances 610 for implementation of the campaign. Not all campaigns will have multiple instances. Depending on the campaign configuration, each campaign instance will represent some portion or division of the campaign for implementation. For example, in a campaign by a dealership for automobile sales, instances may be generated for different types of cars which will be marketed to different target audiences. Campaign instances 610 will typically have rules associated scheduling, target audiences, and budgets. In this embodiment, each instance will is analyzed by a scheduling module 620 to identify scheduling rules and constraints and output an advertisement schedule, a target audience selector 630 to identify relevant target audiences and output a target audience selection, and a budgeting module 640 to track budgeting expenditures for the instance and output a remaining budget amount for advertising of the instance. The outputs of the scheduling module 620, target audience selector 630, and a budgeting module 640 are send to an API call generator 650, which generates an appropriate API call to a third party advertiser in accordance with the third party advertiser's ad placement API (as one example, the Google Ads API has more than 200 parameters that can be set to determine where and when an ad should be placed on its platform).
The client database 710 comprises information about the client for facilitating communications between clients and customers such as client contact information; target information for the client such as subsidiaries, office locations, departments, units, agents, sales representatives, and employees; logs of interactions with customers; records of the products, services, and campaigns associated with certain customers; and lists of campaigns associated with the client.
The customer database 720 has the same characteristics as described for ref 172 of
The campaign database 730 has the same characteristics as described for ref 2604 of
The campaign database 730 may be configured to store a plurality of ad campaigns including the associated ad campaign data for each ad campaign in the ad campaign database 730. In some embodiments, the ad campaign data specifies the different media platforms that will be used to broadcast the ad campaign. In some embodiments, ad campaign data may include one or more variants of an advertisement. In some embodiments, an advertisement variant may be an advertisement where at least one element of the advertisement has been altered in some form. Non-limiting examples of advertisement elements include: headlines and copywriting; call to actions (CTAs); images, audio, and video; subject lines (e.g., email ads); content depth (i.e., how much information to include in ad); product descriptions (e.g., length, placement, etc.); social proof (e.g., customer/purchaser reviews of product); media mentions; and landing pages. In some embodiments, elements may further include font, colors, ad placement, time and location (e.g., when and where is ad displayed), and audience.
Interaction data 731 may be generated from any interactions between clients and customers, and may be stored in any of the three databases 710-730, as necessary.
The PNFT design interface 810 may be accessed directly or may be accessed via the PNFT design API extension 512 of the campaign manager 500. The PNFT design interface allows to set up personal non-fungible tokens (PNFTs) as universal, secure identities for online communications, interactions, and exchanges wherein each PNFT uniquely associates an image, sound, or other digital asset with a person's identity using a non-fungible token (NFT). An image, sound, or other digital asset is stored on a blockchain as an NFT, which uniquely and immutably associates the digital asset with the account owning that digital asset, thereby establishing a unique, secure personal identifier (a “personal non-fungible token” or PNFT) of the person owning that account for online communications and interactions. Links to the PNFT (also sometimes herein called “calls to action” or CTAs similarly those associated with marketing campaigns) can be customized via an online platform such that interaction with a given link or type of link initiates automated actions. Further, the online platform can be configured to automatically place the customized links to the PNFT in locations which will facilitate communications and interactions with the owner of the PNFT such as on websites, in communications such as emails and short message service (SMS) communications, and in advertisements and marketing messages.
Similarly to the campaign design APIs 511 of the campaign manager, the PNFT design interface 810 may comprise a graphical interface, rule creation tools, budgeting tools, target audience selection tools, etc., allowing the client to design automated rule sets for individual PNFT CTAs, groups of PNFT CTAs, or types of PNFT CTAs, whereby customer interactions with a given CTA will initiate certain automated actions such as requesting contact with the client, requesting authorization from the client, production of information to the client, or establishment of communications with the client. The CTAs associated with PNFTs operate similarly to CTAs associated with marketing campaigns, but are secure identifiers for a person or entity, and are not necessarily associated with marketing activity. For example, a CTA for a PNFT on a website may contain a company's trademarked logo. Interaction with the CTA provides automatic verification to the person interacting with the CTA that the website is, in fact, owned by the owner of the CTA. Thus, although CTAs for PNFTs can be used for marketing, they function primarily as secure personal identifiers and means for personal interaction with the owner of the PNFT (which can also be a business). The rules for automation of CTAs for PNFTs are stored in a PNFT rules database 820. A PNFT generator 830 generates PNFTs for each client and sends each generated PNFT to a verification manager 840 for verification of the uniqueness of the PNFT (i.e., that there is no duplicate of that particular PNFT for that particular client) and storage of the PNFT as an immutable entry on a blockchain. Because blockchains are immutable and all records of a blockchain are permanently stored on the blockchain, this ensures that each PNFT will be unique. The verification manager 840 also serves to verify the identity of the owner of a given PNFT by verifying the PNFT's identifier on the blockchain. Note that while each PNFT is unique, it is possible for the same person or entity to have more than one PNFT (e.g., the person may have a personal PNFT and also be the owner of multiple businesses, each with its own PNFT).
A similar process occurs for PNFT generation and placement. The client 110 sets up a PNFT 920, in this case via the PNFT design API extension 512 of the campaign manager 400. The positioning manager 600 retrieves a PNFT for placement 922, retrieves a token for the PNFT from the token manager 924, the token comprising the PNFT identifier and its associated image, sound, or other digital asset, and places a CTA including the token 926 in an appropriate online location via third party web servers or in appropriate messaging such as embedded in emails, text messages, etc. (in this case, the PNFT token). The media server 300 receives interactions with the CTA 928 and verifies the validity of the token 930 with the token manager 800. In this example, PNFTs are not automatically modified as with campaigns, although PNFT rules could be set up to do so.
Once authorization has been established via text messaging, the media server 200 requests initiation of a session initiation protocol (SIP) session 1010 from the session manager 400. The session manager 400 generates an SIP invitation and sends it to the routing manager 300 with a request for routing 1012. The routing manager 300 selects a communications route and passes through the SIP invitation to the media server 200, which establishes an SIP connection through the media server 200 between the client 1016a and the customer 1016b.
Once authorization has been established via text messaging, the media server 200 requests verification of the PNFT token from and receipt of rules for the token 1110 from the token manager 800. The token manager 800 verifies the PNFT token and sends rules associated with it 1112 to the media server 200. Depending on the rules, the media server may take one of several actions, two of which are shown here. The media server 200 may automatically forward information 1114a to the customer 120 according to the PNFT rules, or may request session initiation 1114b from the session manager 400. If a session request is sent 1114b, the session manager initiates an SIP session 1116, which establishes an SIP connection through the media server 200 between the client 1118a and the customer 1118b.
According to some embodiments, a customer may view on his or her mobile device a promotional advertisement in the form of a rewards wheel spinner 1322. A customer/user mobile device can include, but is not limited to, a smart cell phone, a tablet, and a smart wearable device. The rewards wheel may be divided into a plurality of sections, in some embodiments the sections are evenly distributed and uniform in size. In other embodiments the sections may not be uniform in size. An indicator may also be present to provide a visual reference for mobile device users to view what section of the reward wheel 1322 has been landed on after the user has interacted with the wheel. In some embodiments a triangle is used as the indicator, however, in other embodiments different shapes (e.g., an arrow, finger pointing emoji, etc.) may be used as indicators with various sizes and color schemes. In addition to the reward wheel, an interactive button may also be displayed that prompts the customer to engage with the reward wheel such as, for example, a prompt which instructs mobile device user to ‘spin the wheel’ to play the game and receive a promotional reward. The promotional rewards can take any number of forms such as, for example, a percentage off the total cost of product (e.g., 25% off), a buy-one-get-one free (BOGO) reward, customer loyalty rewards points (RP) that may be exchanged for discounts and other offers, or early access (EA) to a new product or service. These are just a few examples of the types of promotional rewards that may be available, but are in no way limiting to the types of promotional rewards that may be offered in this embodiment or in various other embodiments of the disclosed system. A client 110 can initialize and configure promotional rewards during marketing campaign configuration as facilitated by campaign manager 500.
When the customer (e.g., mobile device user) interacts (e.g., touches, taps, bumps, slides a finger across, voice activation, hand gesture, etc.) with the rewards wheel, an animation can spin and land on one of the sections of the wheel 1321, the section landed on corresponding to a promotional reward. The data associated with the section of the wheel that was landed on after a mobile device user spins the wheel may be sent via an appropriate communications network to a media server 200. The data associated with the section of the wheel can include, but is not limited to, the promotional reward information associated with the section of the wheel and information associated with the enterprise (e.g., online retailer, wholesaler, individual, etc.) that is running the promotional offers. For example, a mobile device user spins the rewards wheel 1321 and the wheel lands on ‘10% off total sale price’ as indicated by an indicator that may or may not be present, depending upon the embodiment used, then that information may be sent, via a communication network, to media server 200. This transmission of data may happen in real-time as soon as the rewards wheel 1321 has stopped spinning and landed on a section of the wheel. The type of communication network utilized by this system can include, but is not limited to, a cellular phone network (e.g., Global System for Mobile Communications, General Packet Radio Service, Code Division Multiple Access, Mobitex, Enhanced Data for Global Evolution, etc.) and an internet connection via a WiFi network or other wireless network.
According to an aspect, media server 200 may receive the data associated with section of the rewards wheel 1321 that was landed on and send the promotional reward (e.g., coupon code), via the communication network, to the default messaging application operating on the user's mobile device in the form of a pre-filled SMS or MMS message which can be displayed in the default messaging application. As media server 200 receives the data associated with the reward the mobile device user has won, it may parse the data in order to retrieve information identifying what enterprise the promotional reward is associated with as well as identify what reward was won. Media server 200 may utilize an enterprise database 700 to retrieve information associated with the identified enterprise and specific to the promotional reward data that was received from mobile device 200. For example, the proper endpoint from which to claim a won promotional reward may be dependent upon the type of reward and/or the section of the wheel that was landed on after the reward wheel 1321 has been spun. The data associated with the won reward that is sent to media server 200 may be used to identify and retrieve from enterprise database 700 the appropriate endpoint associated with the won promotional reward. Media server 200 can retrieve this information from enterprise database 700 and then use this retrieved information to generate a text-based message. The text-based message may comprise information about the user's reward (e.g., “You won 15% off your next order”) as well as an indication to the appropriate enterprise endpoint where the user can claim his or her reward. Media server 200 may then send the generated and pre-filled text-based message to the default messaging application of the user's mobile device.
According to some embodiments, enterprise database 700 may comprise information including, but not limited to, enterprise information, promotional rewards information, enterprise endpoints, and user information. Enterprise information may include, but is not limited to, enterprise contact information (e.g., name, address, phone number, email address, social media handle(s), hours of operation, enterprise website and/or webapp URL, etc.), and enterprise product and inventory information. Promotional rewards may comprise information including, but not limited to, current and historical enterprise advertisement campaigns, current and historical promotional reward offers (e.g., coupons, free shipping, % off total price, etc.), and a duration of time associated with a current promotional reward offer and/or advertisement campaign. Enterprise endpoints may include information related to a plurality of endpoints, wherein each endpoint may be associated with at least one or more promotional rewards and/or advertisement campaigns. For example, a free shipping promotional reward may be associated with an enterprise endpoint such as an online shopping cart, whereas a free rewards points promotional reward may be associated with an enterprise endpoint such as a customer account log-in page. In some embodiments, promotional rewards and enterprise endpoints may be stored together (e.g., as key-value pairs) or otherwise logically linked such that retrieval of either promotional rewards information or enterprise endpoints information may also retrieve the associated enterprise endpoint or promotional reward, respectively. According to some embodiments, enterprise database 700 may further comprise user information. User information may include, but is not limited to, user social media handle(s), user mobile device identifier (e.g., phone number, Media Access Control address, etc.), username, address, email address, and past claimed promotional rewards. As an example, an enterprise may have a rule that a given user can't claim two promotional rewards within a 90 day time-span; in this case user information such as past claimed promotional rewards may be retrieved by media server 200 in order to determine if the mobile device user is allowed to claim a won promotional reward based on the time between the last claimed promotional reward and the current promotional reward won by spinning reward wheel 1321.
The mobile device user can view the pre-filled message associated with their won promotional reward via his or her default messaging application. According to an aspect, the pre-filled text-based message may contain an indication or description of the reward won and an indication of an appropriate enterprise endpoint such as, for example, a product landing page or other type of URL associated with the product of the enterprise who sells the product, a salesperson associated with the enterprise, or an automated chat bot. When the user chooses to, they may send the generated pre-filled text-based message to the indicated enterprise endpoint thereby creating a communication session between the mobile device user and the given enterprise endpoint. In this way, promotional rewards wheel system users may interact with a promotional offer and directly receive the rewards of the promotional offer to their personal mobile device without the need to use a third party messaging application, without having to fill out forms, sign-up for enterprise accounts, or divulge personal information to claim the reward, and without having to navigate multiple web pages and redirects.
Generally, the techniques disclosed herein may be implemented on hardware or a combination of software and hardware. For example, they may be implemented in an operating system kernel, in a separate user process, in a library package bound into network applications, on a specially constructed machine, on an application-specific integrated circuit (“ASIC”), or on a network interface card.
Software/hardware hybrid implementations of at least some of the aspects disclosed herein may be implemented on a programmable network-resident machine (which should be understood to include intermittently connected network-aware machines) selectively activated or reconfigured by a computer program stored in memory. Such network devices may have multiple network interfaces that may be configured or designed to utilize different types of network communication protocols. A general architecture for some of these machines may be described herein in order to illustrate one or more exemplary means by which a given unit of functionality may be implemented. According to specific aspects, at least some of the features or functionalities of the various aspects disclosed herein may be implemented on one or more general-purpose computers associated with one or more networks, such as for example an end-user computer system, a client computer, a network server or other server system, a mobile computing device (e.g., tablet computing device, mobile phone, smartphone, laptop, or other appropriate computing device), a consumer electronic device, a music player, or any other suitable electronic device, router, switch, or other suitable device, or any combination thereof. In at least some aspects, at least some of the features or functionalities of the various aspects disclosed herein may be implemented in one or more virtualized computing environments (e.g., network computing clouds, virtual machines hosted on one or more physical computing machines, or other appropriate virtual environments).
Referring now to
In one embodiment, computing device 10 includes one or more central processing units (CPU) 12, one or more interfaces 15, and one or more busses 14 (such as a peripheral component interconnect (PCI) bus). When acting under the control of appropriate software or firmware, CPU 12 may be responsible for implementing specific functions associated with the functions of a specifically configured computing device or machine. For example, in at least one embodiment, a computing device 10 may be configured or designed to function as a server system utilizing CPU 12, local memory 11 and/or remote memory 16, and interface(s) 15. In at least one embodiment, CPU 12 may be caused to perform one or more of the different types of functions and/or operations under the control of software modules or components, which for example, may include an operating system and any appropriate applications software, drivers, and the like.
CPU 12 may include one or more processors 13 such as, for example, a processor from one of the Intel, ARM, Qualcomm, and AMD families of microprocessors. In some embodiments, processors 13 may include specially designed hardware such as application-specific integrated circuits (ASICs), electrically erasable programmable read-only memories (EEPROMs), field-programmable gate arrays (FPGAs), and so forth, for controlling operations of computing device 10. In a specific embodiment, a local memory 11 (such as non-volatile random access memory (RAM) and/or read-only memory (ROM), including for example one or more levels of cached memory) may also form part of CPU 12. However, there are many different ways in which memory may be coupled to system 10. Memory 11 may be used for a variety of purposes such as, for example, caching and/or storing data, programming instructions, and the like. It should be further appreciated that CPU 12 may be one of a variety of system-on-a-chip (SOC) type hardware that may include additional hardware such as memory or graphics processing chips, such as a QUALCOMM SNAPDRAGON™ or SAMSUNG EXYNOS™ CPU as are becoming increasingly common in the art, such as for use in mobile devices or integrated devices.
As used herein, the term “processor” is not limited merely to those integrated circuits referred to in the art as a processor, a mobile processor, or a microprocessor, but broadly refers to a microcontroller, a microcomputer, a programmable logic controller, an application-specific integrated circuit, and any other programmable circuit.
In one embodiment, interfaces 15 are provided as network interface cards (NICs). Generally, NICs control the sending and receiving of data packets over a computer network; other types of interfaces 15 may for example support other peripherals used with computing device 10. Among the interfaces that may be provided are Ethernet interfaces, frame relay interfaces, cable interfaces, DSL interfaces, token ring interfaces, graphics interfaces, and the like. In addition, various types of interfaces may be provided such as, for example, universal serial bus (USB), Serial, Ethernet, FIREWIRE™, THUNDERBOLT™, PCI, parallel, radio frequency (RF), BLUETOOTH™, near-field communications (e.g., using near-field magnetics), 802.11 (Wi-Fi), frame relay, TCP/IP, ISDN, fast Ethernet interfaces, Gigabit Ethernet interfaces, Serial ATA (SATA) or external SATA (ESATA) interfaces, high-definition multimedia interface (HDMI), digital visual interface (DVI), analog or digital audio interfaces, asynchronous transfer mode (ATM) interfaces, high-speed serial interface (HSSI) interfaces, Point of Sale (POS) interfaces, fiber data distributed interfaces (FDDIs), and the like. Generally, such interfaces 15 may include physical ports appropriate for communication with appropriate media. In some cases, they may also include an independent processor (such as a dedicated audio or video processor, as is common in the art for high-fidelity A/V hardware interfaces) and, in some instances, volatile and/or non-volatile memory (e.g., RAM).
Although the system shown in
Regardless of network device configuration, the system may employ one or more memories or memory modules (such as, for example, remote memory block 16 and local memory 11) configured to store data, program instructions for the general-purpose network operations, or other information relating to the functionality of the embodiments described herein (or any combinations of the above). Program instructions may control execution of or comprise an operating system and/or one or more applications, for example. Memory 16 or memories 11, 16 may also be configured to store data structures, configuration data, encryption data, historical system operations information, or any other specific or generic non-program information described herein.
Because such information and program instructions may be employed to implement one or more systems or methods described herein, at least some network device embodiments may include nontransitory machine-readable storage media, which, for example, may be configured or designed to store program instructions, state information, and the like for performing various operations described herein. Examples of such nontransitory machine-readable storage media include, but are not limited to, magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROM disks; magneto-optical media such as optical disks, and hardware devices that are specially configured to store and perform program instructions, such as read-only memory devices (ROM), flash memory (as is common in mobile devices and integrated systems), solid state drives (SSD) and “hybrid SSD” storage drives that may combine physical components of solid state and hard disk drives in a single hardware device (as are becoming increasingly common in the art with regard to personal computers), memristor memory, random access memory (RAM), and the like. It should be appreciated that such storage means may be integral and non-removable (such as RAM hardware modules that may be soldered onto a motherboard or otherwise integrated into an electronic device), or they may be removable such as swappable flash memory modules (such as “thumb drives” or other removable media designed for rapidly exchanging physical storage devices), “hot-swappable” hard disk drives or solid state drives, removable optical storage discs, or other such removable media, and that such integral and removable storage media may be utilized interchangeably. Examples of program instructions include both object code, such as may be produced by a compiler, machine code, such as may be produced by an assembler or a linker, byte code, such as may be generated by for example a JAVA™ compiler and may be executed using a Java virtual machine or equivalent, or files containing higher level code that may be executed by the computer using an interpreter (for example, scripts written in Python, Perl, Ruby, Groovy, or any other scripting language).
In some embodiments, systems may be implemented on a standalone computing system. Referring now to
In some embodiments, systems may be implemented on a distributed computing network, such as one having any number of clients and/or servers. Referring now to
In addition, in some embodiments, servers 32 may call external services 37 when needed to obtain additional information, or to refer to additional data concerning a particular call. Communications with external services 37 may take place, for example, via one or more networks 31. In various embodiments, external services 37 may comprise web-enabled services or functionality related to or installed on the hardware device itself. For example, in an embodiment where client applications 24 are implemented on a smartphone or other electronic device, client applications 24 may obtain information stored in a server system 32 in the cloud or on an external service 37 deployed on one or more of a particular enterprise's or user's premises.
In some embodiments, clients 33 or servers 32 (or both) may make use of one or more specialized services or appliances that may be deployed locally or remotely across one or more networks 31. For example, one or more databases 34 may be used or referred to by one or more embodiments. It should be understood by one having ordinary skill in the art that databases 34 may be arranged in a wide variety of architectures and using a wide variety of data access and manipulation means. For example, in various embodiments one or more databases 34 may comprise a relational database system using a SQL, while others may comprise an alternative data storage technology such as those referred to in the art as “NoSQL” (for example, HADOOP CASSANDRA™, GOOGLE BIGTABLE™, and so forth). In some embodiments, variant database architectures such as column-oriented databases, in-memory databases, clustered databases, distributed databases, or even flat file data repositories may be used. It will be appreciated by one having ordinary skill in the art that any combination of known or future database technologies may be used as appropriate, unless a specific database technology or a specific arrangement of components is specified for a particular embodiment herein. Moreover, it should be appreciated that the term “database” as used herein may refer to a physical database machine, a cluster of machines acting as a single database system, or a logical database within an overall database management system. Unless a specific meaning is specified for a given use of the term “database”, it should be construed to mean any of these senses of the word, all of which are understood as a plain meaning of the term “database” by those having ordinary skill in the art.
Similarly, most embodiments may make use of one or more security systems 36 and configuration systems 35. Security and configuration management are common information technology (IT) and web functions, and some amount of each are generally associated with any IT or web systems. It should be understood by one having ordinary skill in the art that any configuration or security subsystems known in the art now or in the future may be used in conjunction with embodiments without limitation, unless a specific security 36 or configuration system 35 or approach is specifically required by the description of any specific embodiment.
In various embodiments, functionality for implementing systems or methods may be distributed among any number of client and/or server components. For example, various software modules may be implemented for performing various functions in connection with the various embodiments, and such modules may be variously implemented to run on server and/or client components.
According to a preferred embodiment, end users such as consumers can generate their own personal non-fungible tokens (PNFTs), and optionally associate them with their own image (such as a photo of the end user). These PNFTs are identified by a unique identifier, such as a globally unique identifier (GUID) that points to the location of the PNFT in a distributed ledger such as a blockchain. In some aspects a link or pointer to the image may be stored in the PNFT, while in others code such as that for smart contracts may be stored; as is known in the art with respect to non-fungible tokens, once a PNFT is saved on a distributed ledger it is immutable. A key aspect is that the PNFT is identified with a unique phone number (typically the number of the mobile phone from which the end user generated her PNFT). This is important because the user may, when desired, send a link (such as a URL) to another party (such as a business or another end user). The link may comprise metadata that may specify a bundle of rights or actions that the recipient is authorized to enjoy or to take. For example, the end user may use an application or a website to create a link that is tied to her PNFT and that authorizes the recipient to download a copy of the end user's resume from a specific location. On receipt of the link, and after clicking on it, the recipient may receive a message comprising a pre-drafted text message and a “Send” button; upon pressing Send, the text message is sent to the phone number associated with the PNFT of the end user who sent the link. At no time does the recipient have any knowledge of the phone number used; this is maintained by the platform that generated the PNFT at the request of the end user. When the end user receives the text message, for example saying, “Company X has received a link to your PNFT and requests to download your resume; do you approve?” she may either approve the request (if she sent the link) or not (if she didn't). In this way, a unique identifier that can be transmitted with metadata to any desired recipient and that is guaranteed to be associated with only a single person is used.
In order to generate a PNFT, according to an embodiment, an end user using either a web page or an application connected to a token-granting server requests that a personal non-fungible token be generated and optionally uploads an image or other data element to be stored permanently in association with the generated token. The requesting end user also provides her mobile phone number. On receipt of the request, and after any additional authentication or verification steps are taken, adds a record to a pending block based on the image or data received, and sends a text message to the end user at the mobile phone number provided. The requesting end user receives the text message and affirms that she sent the request, by clicking on a link in the text message (or otherwise indicating her assent, such as by an email confirmation). Once confirmed, the new record is permanently written to a distributed ledger, and the requesting end user receives the unique identifier of the newly-generated PNFT. At this point, the end user is able to post the PNFT on any suitable electronic medium, for example her webpage or a social network home page, or even embedded in her standard email template. It will be appreciated by one having ordinary skill in the art that “posting” an PNFT means placing an image (such as the personal photo image that was optionally uploaded when generating the PNFT) along with a (hidden) link “behind” the image or accessible via scanning the image. For example, a quick response (QR) code could be placed on a page or email that, when scanned by a QR-capable scanner, returns a clickable link with metadata. In many cases, the posting of an image representing a link is referred to as “posting the PNFT;” when a viewer of the page or application or social media page hosting the posted PNFT is viewed by a third party, the third party may click on the PNFT to activate the link. In some embodiments, such “clicking on the PNFT” by a third party causes a text message to be created (based on the PNFT and any associated metadata), which the third party may then send (without seeing the phone number to which it is sent; it is sent from the interaction manager or the media translation manager as described above). The owner of the PNFT will then receive a text message requesting that the third party be authorized to carry out whatever action is indicated (generally, this action whether downloading a file, activating a smart contract, or obtaining access to specific elements of the PNFT owner's private data—is described in the metadata associated with the link or in a smart contract stored in the distributed ledger as part of the PNFT).
In some aspects, the party clicking on a first PNFT may themselves possess a second PNFT or other identifying information, so that the owner of the first PNFT will receive an authorization request identifying and attesting to the authenticity of the identity of the requesting party. In some aspects, a plurality of third parties may be specifically pre-authorized by an owner of a PNFT to take any actions associated with a specific link associated with the PNFT without the transmission of any authorizing text message; in some cases, pre-authorization of such parties just prior to clicking on a PNFT may be done by using the same text message authorization capability to confirm the identity of the requesting party before the request is made (biometric data may also be used in this way).
The systems described herein also may comprises a personal non-fungible token (PNFT) generator server. This server receives the request for a PNFT from end users as described above. The PNFT generator server, on receipt of such a request, either directly sends a text message to the mobile phone number given withy the request or instructs the interaction manager or media translation manager to send the text message. Upon receipt of a text message from the same phone number, confirming the request for a new PNFT, the PNFT generator server then determines a new unique identifier and sends the identifier via text message to the requesting user. In some embodiments the server may also send the PNFT identifier via email if requested and authorized. The PNFT generation server also writes the new token to the current block of a digital ledger or other immutable data store, such that it can be accessed using the unique identifier. It will be appreciated by one having ordinary skill in the art that this method of generating personal non-fungible tokens in effect creates a permanent association between a human person (and possibly their image), their mobile phone number, and the unique identifier of their newly-created personal non-fungible token. This allows the owner of a PNFT to post or send the PNFT with varying permissions or data payloads, and so to control their privacy and identity in a decentralized and secure way.
The skilled person will be aware of a range of possible modifications of the various embodiments described above. Accordingly, the present invention is defined by the claims and their equivalents.
Priority is claimed in the application data sheet to the following patents or patent applications, the entire written description of each of which is expressly incorporated herein by reference in its entirety: 63/235,785Ser. No. 17/209,474Ser. No. 17/208,059Ser. No. 17/191,977Ser. No. 17/190,260Ser. No. 17/153,42662/965,62662/963,36862/963,37963/040,61063/025,28763/022,19062/994,21963/154,357Ser. No. 16/693,27562/904,56862/883,36062/879,862Ser. No. 16/930,816
| Number | Date | Country | |
|---|---|---|---|
| 63235785 | Aug 2021 | US | |
| 62965626 | Jan 2020 | US | |
| 62963368 | Jan 2020 | US | |
| 62963379 | Jan 2020 | US | |
| 63040610 | Jun 2020 | US | |
| 63025287 | May 2020 | US | |
| 63022190 | May 2020 | US | |
| 62994219 | Mar 2020 | US | |
| 63154357 | Feb 2021 | US | |
| 63040610 | Jun 2020 | US | |
| 63025287 | May 2020 | US | |
| 63022190 | May 2020 | US | |
| 62994219 | Mar 2020 | US | |
| 62965626 | Jan 2020 | US | |
| 62963568 | Jan 2020 | US | |
| 62963368 | Jan 2020 | US | |
| 62963379 | Jan 2020 | US | |
| 62940607 | Nov 2019 | US | |
| 62904568 | Sep 2019 | US | |
| 62883360 | Aug 2019 | US | |
| 62879862 | Jul 2019 | US | |
| 63166391 | Mar 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17349659 | Jun 2021 | US |
| Child | 17351321 | US | |
| Parent | 17348660 | Jun 2021 | US |
| Child | 17349659 | US | |
| Parent | 17344695 | Jun 2021 | US |
| Child | 17348660 | US | |
| Parent | 17229251 | Apr 2021 | US |
| Child | 17344695 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17879605 | Aug 2022 | US |
| Child | 17967606 | US | |
| Parent | 17209474 | Mar 2021 | US |
| Child | 17879605 | US | |
| Parent | 17208059 | Mar 2021 | US |
| Child | 17209474 | US | |
| Parent | 17191977 | Mar 2021 | US |
| Child | 17208059 | US | |
| Parent | 17190260 | Mar 2021 | US |
| Child | 17191977 | US | |
| Parent | 17153426 | Jan 2021 | US |
| Child | 17190260 | US | |
| Parent | 16930816 | Jul 2020 | US |
| Child | 17879605 | US | |
| Parent | 16693275 | Nov 2019 | US |
| Child | 16930816 | US | |
| Parent | 17351321 | Jun 2021 | US |
| Child | 16693275 | US | |
| Parent | 17209474 | Mar 2021 | US |
| Child | 17229251 | US |
