US-20260127567-A1 - Application of Dynamic Tokens

Abstract

A method assigns token requirements to service subscriptions in a service platform, such as a service platform containing entities or a database containing a plurality of said entities. The operator of the service platform establishes customization factors and maintains records reserving data services associated with token requirements for delivery to entities. In addition, customization factors are determined from values representing information associated with objects in a database. Token requirements associated with data services are calculated from one or more formulas utilizing customization factors. Sponsorships associated with the entities can be accepted by the service platform. The service platform can apply credit toward the fulfillment of token requirements. An entity can be provided a data service based on a relationship with a sponsorship such that an entity assigned a subscription having a token requirement fulfilled as a result of applying credit from a sponsorship will receive services related to the subscription.

Inventors

• Ryan Hardin
• Andrew Hill

Assignees

• Ryan Hardin
• Andrew Hill

Dates

Publication Date

20260507

Application Date

20251230

Claims (2)

1. 1 . A method for improving delivery of services having token requirements, comprising: receiving, from a first device associated with a first user and an executing application, identity of the first user, wherein the identity includes a unique identifier and is received in a communication associated with the executing application; determining an expiration of an application subscription of a third party; determining that the third party is eligible to have the application subscription extended by the first user based on the expiration of the application subscription being within a predetermined period of time of a current date; transmitting an eligibility indication to the first device; receiving confirmation of payment by the first user to extend the application subscription of the third party; applying an extension to the application subscription of the third party in response to the confirmation of payment; and notifying the third party of the extension to the application subscription.
2. 2 . The method of claim 1 wherein, receiving the identity of the first user includes registering the first user for the delivery of services.

Description

CROSS REFERENCE TO RELATED APPLICATIONS This continuation patent application claims priority from co-pending U.S. Non-provisional patent application having Ser. No. 18/616,466, filed 26 Mar. 2024, entitled “APPLICATION OF DYNAMIC TOKENS”, which claims priority from co-pending U.S. Non-provisional patent application having Ser. No. 17/868,809, filed 20 Jul. 2022, entitled “APPLICATION OF DYNAMIC TOKENS”, now U.S. Pat. No. 11,972,403 issued on 30 Apr. 2024, which claims priority from co-pending U.S. Non-provisional patent application having Ser. No. 16/892,335, filed 4 Jun. 2020, entitled “APPLICATION OF DYNAMIC TOKENS”, now U.S. Pat. No. 11,423,374 issued on 3 Aug. 2022, which claims priority from co-pending U.S. Non-provisional patent application having Ser. No. 15/616,942, filed 8 Jun. 2017, entitled “APPLICATION OF DYNAMIC TOKENS”, now U.S. Pat. No. 10,719,819 issued on 21 Jul. 2020, which claims priority from co-pending U.S. Non-provisional patent application having Ser. No. 14/930,200, filed 2 Nov. 2015, entitled “APPLICATION OF DYNAMIC TOKENS”, now U.S. Pat. No. 9,710,794 issued on 18 Jul. 2017, which claims priority from co-pending U.S. Non-provisional patent application having Ser. No. 13/955,033, filed 31 Jul. 2013, entitled “APPLICATION OF DYNAMIC TOKENS”, now U.S. Pat. No. 9,245,284 issued on 26 Jan. 2016, all having a common applicant herewith and being incorporated herein in their entirety by reference. FIELD This disclosure relates generally to delivery of services, and more particularly to delivery of services having token requirements. BACKGROUND Software products and services can be provided to various entities or organizations, including membership organizations, via the Internet. For example, software products and services can be provided to a membership organization via an online membership website. Furthermore, data or software products and services can be provided to software applications running on mobile devices, desktop devices, or web applications, or via application programming interfaces (APIs), based on subscriptions and preferences. When providing data services, software products, services, and/or other features to some entities or membership organizations, currently available technologies can provide the features to all or some of the entities or organizations subscribed to receive them. In some cases, features of software products, etc. are provided to any entity or organization having a subscription level that includes the features. When providing features, for example via subscription, it is common to provide the features in response to a fee assignment delivered to the entity or organization. In some cases, coupon technology can be used to provide discounts to multiple entities or organizations concurrently. In each of these cases, an entity or organization can usually receive services from one or more, or multiple different, service providers without considering interesting characteristics of or relationships associated with or within the entity or organization. Current technologies are, therefore, less than perfect. SUMMARY Various embodiments disclosed herein include providing one or more entities services by a service platform or provider, establishing multiple parameters defining tokens or token values or requirements, and maintaining records associating sponsorships with one or more entities. The service platform can receive a request from an entity interested in using or accessing services made available for use to the entity, and the request or characteristics associated with the entity can be used, in whole or in part, to determine a token requirement. In some embodiments, a service feature is provided based on a relationship between the token requirement and one or more calculations and/or one or more applications of tokens. Services can then be provided and/or delivered to the organization or entity. In some embodiments, the service platform can record a calculated requirement associated with a software feature, and provide the calculated requirement to the entity to assist in future actions relating to one or more requests for or delivery of software features. The service platform can also receive information related to the entity—for example, contacts, members, sponsors, sponsorship values, etc.—and determine a token requirement based on the information related to the entity to provide additional service features to the entity or to perform requirement calculations in response to the received information. In some embodiments, the service platform can recalculate token requirements, token values, contact database sizes, membership quantities, sponsor quantities and sponsorship values at regular intervals. In some embodiments, software features can be provided to an entity subscribing to a service if a token requirement is at least partially satisfied by token calculations or credits associated with one or more sponsors; if the token requirement is not satisfied,