systems and method for managing digital assets for a plurality of enterprises. The system may include enterprise profiles for each of the enterprises. Each enterprise profile can include one or more cost centers representative of divisions of the enterprise. assets can be organized within cost centers within containers and folders. The arrangement of containers and folders can be representative of an organization structure of a division of the enterprise. access to assets within the cost center can be determined by an access control module and be based on user-level and container-level permissions.
|
13. A method for managing digital assets for a plurality of enterprises, the method comprising:
generating one or more enterprise profiles, each enterprise profile being associated with an enterprise;
generating users for each enterprise profile, each user including user-level permissions;
generating one or more cost centers for each enterprise profile, each cost center being associated with a division of the enterprise, each cost center including containers and folders, each container including container-level permissions;
uploading one or more digital assets into one or more databases, the one or more digital assets being associated with an enterprise profile and organized within an associated cost center;
querying digital assets from the one or more databases;
controlling a user's access to the containers according to the user-level permissions and the container-level permissions of an associated user profile and an associated container, respectively; and
receiving an application programming interface (api) password and one or more api uniform resource locators (URLs); and
generating an api key for each of the enterprise profiles based on the api password and the one or more api URLs, the api key associated with an api of the one or more enterprise profiles, wherein a request to access the system via the api must be authenticated by the api key and must originate from one of the api URLs.
25. A method for managing digital assets for a plurality of enterprises, the method embodied in a set of machine-readable instructions executed on a processor and stored on a tangible medium, the method comprising:
generating one or more enterprise profiles, each enterprise profile being associated with an enterprise;
generating users for each enterprise profile, each user including user-level permissions;
generating one or more cost centers for each enterprise profile, each cost center being associated with a division of the enterprise, each cost center including containers and folders, each container including container-level permissions;
uploading one or more digital assets into one or more databases, the one or more digital assets being associated with an enterprise profile and organized within an associated cost center;
querying digital assets from the one or more databases;
controlling a user's access to the containers according to the user-level permissions and the container-level permissions of an associated user profile and an associated container, respectively; and
receiving an application programming interface (api) password and one or more api uniform resource locators (URLs); and
generating an api key for each of the enterprise profiles based on the api password and the one or more api URLs, the api key associated with an api of the one or more enterprise profiles, wherein a request to access the system via the api must be authenticated by the api key and must originate from one of the api URLs.
1. A system for managing digital assets for a plurality of enterprises comprising:
one or more databases adapted to store digital assets;
one or more processors; and
one or more computer storage mediums storing computer program modules adapted to execute on the one or more processors, the computer program modules comprising:
an enterprise customization module including an application programming interface (api), the enterprise customization module adapted to:
generate one or more enterprise profiles, each enterprise profile being associated with an enterprise;
generate users for each enterprise profile, each user including user-level permissions;
generate one or more cost centers for each enterprise profile, each cost center being associated with a division of the enterprise, each cost center including containers and folders, each container including container-level permissions;
receive one or more api uniform resource locators (URLs); and
generate an api key for each enterprise profile based on an api password and the one or more api URLs, wherein a request to access the system via the api must be authenticated by the api key and must originate from one of the api URLs;
an upload module for ingesting assets into the system;
a search module for querying digital assets from the one or more databases; and
an access control module adapted to control a user's access to the containers according to the user-level permissions and the container-level permissions of an associated user profile and an associated container, respectively.
2. The system of
3. The system of
4. The system of
5. The system of
6. The system of
7. The system of
8. The system of
receive one or more digital assets to upload into an enterprise profile;
receive descriptive information associated with the one or more digital assets;
extract asset metadata from each of the one or more digital assets;
generate system metadata for each of the one or more digital assets based on the descriptive information and/or the asset metadata for each of the one or more digital assets; and
store the one or more digital assets and the system metadata in the one or more databases and associate the one or more digital assets with a cost structure associated with the enterprise profile.
9. The system of
present a search user interface for searching the one or more databases;
receive, via the search user interface, a search description;
generate a search query based on the search description; and
generate search results based on the search query, the search results comprising one or more digital assets.
10. The system of
generate search metadata based on system metadata associated with the search results;
present, via the search user interface, one or more filters according to the search metadata;
receive, via the search user interface, a selection of one or more filters and
present filtered search results based on the selection of filters, the filtered search results comprising a subset of the search results.
11. The system of
receive a selection of a digital asset;
export a copy of the digital asset from the one or more databases to a workspace wherein a modified copy of the digital asset can be developed; and
import the modified copy of the digital asset into the one or more databases.
12. The system of
14. The method of
15. The method of
16. The method of
17. The method of
18. The method of
19. The method of
20. The method of
receiving one or more digital assets to upload into an enterprise profile;
receiving descriptive information associated with the one or more digital assets;
extracting asset metadata from each of the one or more digital assets;
generating system metadata for each of the one or more digital assets based on the descriptive information and/or the asset metadata for each of the one or more digital assets; and
storing the one or more digital assets and the system metadata in the one or more databases and associate the one or more digital assets with an enterprise file storage structure associated with the enterprise profile.
21. The method of
presenting a search user interface for searching the one or more databases;
receiving, via the search user interface, a search criteria;
generating a search query based on the search criteria; and
generating search results based on the search query, the search results comprising one or more digital assets.
22. The method of
generating search metadata based on system metadata associated with the search results;
presenting, via the search user interface, one or more filters according to the search metadata;
receiving, via the search user interface, a selection of one or more filters; and
presenting filtered search results based on the selection of filters, the filtered search results comprising a subset of the search results.
23. The method of
receiving a selection of a digital asset;
exporting a copy of the digital asset from the one or more databases to a workspace wherein a modified copy of the digital asset can be developed; and
importing the modified copy of the digital asset into the one or more databases.
24. The method of
|
Conventional asset management systems are commonly used to manage digital assets. Digital assets can include, for example, video, sound, image, and document files and can vary in form and type. Digital asset management systems can be used to store, track, and organize digital assets and are often used to manage digital assets across an enterprise. There exists a need for robust asset management systems that can be tailored to meet the needs of enterprises.
This disclosure generally relates to systems and methods for managing digital assets. In particular, certain examples relate to the managing of digital assets for a plurality of enterprises. In some examples, an asset management system can include a plurality of enterprise profiles each associated with a distinct enterprise. Certain examples of the asset management system include an enterprise customization module adapted to customize and configure the enterprise profile to be representative of an organizational structure of the enterprise. For example, an enterprise profile can include one or more cost centers each representative of a distinct division of the enterprise. In some examples, each cost center can include a plurality of containers and folders arranged in a hierarchical structure that parallels an organizational structure of the enterprise. Certain examples of the asset management system include an access control module that provides access privileges to users based on user-level and container-level permissions. In some examples, an access control module can also control access based on an override option associated with the user-level and container-level permissions. Examples of the system can also include an upload module for ingesting digital assets, a search module for querying and presenting assets stored in the system, and a workspace module adapted to facilitate the continued development of digital assets.
Examples in this disclosure provide for one or more advantages over existing systems and methods for digital asset management. For example, certain embodiments provide for a system that effectively manages a plurality of enterprises. Features of the system provide asset management services that are highly customizable and configurable to meet the diverse requirements of different enterprises. For example, disclosed systems and methods include the use of cost centers, containers, and folders that can be easily arranged and configured to mirror the organizational structure of an enterprise. This feature provides for comfort and familiarity for individuals familiar with the organizational structure (e.g., employees of the enterprise) while using the asset management system. Further, certain disclosed features of the system are directed to maintaining the arrangement of the containers and folders to preserve the enterprise's organizational structure within the asset management system. Other features of the system, for example features embodied in an access control module, are directed to providing a highly customizable workspace that allows enterprises increased functionality and convenience in managing its assets over existing solutions.
The following drawings are illustrative of particular embodiments of the invention and therefore do not limit the scope of the invention. The drawings are not necessarily to scale, unless so stated. The drawings are intended for use in conjunction with the explanations in the following detailed description. Embodiments of the invention will hereinafter be described in conjunction with the appended drawings, wherein like numerals denote like elements.
The following detailed description is exemplary in nature and is not intended to limit the scope, applicability, or configuration of the invention in any way. Rather, the following description provides some practical illustrations for implementing exemplary embodiments of the present invention. Examples of constructions, materials, dimensions, and manufacturing processes are provided for selected elements, and all other elements employ that which is known to those of ordinary skill in the field of the invention. Those skilled in the art will recognize that many of the noted examples have a variety of suitable alternatives.
In some examples, system administrators 202 of system 200 can create enterprise profiles 204.
In some examples, user interface 300 can be configured to receive and associate a master services agreement 322 with an enterprise profile. The master services agreement 322 can include terms and conditions detailing digital asset management services for enterprise 312. This feature of the enterprise customization module helps facilitate digital asset management for a plurality of enterprises, where each enterprise is likely to negotiate a unique set of terms and conditions, as compared to using a standard set of terms and conditions which is more suitable for an asset management system adapted for individuals.
In some examples, an enterprise customization module can include a company application programming interface (API) 330 to facilitate integration of an asset management system with an enterprise's existing systems and applications. For example, enterprise 312 can use an API 330 of an enterprise customization module to directly access asset management services. As just one example, enterprise 312 can use the API 330 to facilitate a mass upload of assets to the asset management system. In some examples, enterprise 312 can develop and design its own user interfaces for use with services provided by the asset management system. This feature can be particularly advantageous for enterprises that prioritize its branding. For example, enterprise 312 may want to integrate services of an asset management system into an internal or external website instead of providing a link from the enterp2se's website to a portal of the asset management system. In such examples, enterprise 318 can design its own webpages which incorporate its corporate brand and design, then integrate the developed pages with the services of the asset management system using API 330. In such examples, a user navigating the enterprise's website can be provided a seamless and uninterrupted experience as they are provided asset management services without ever leaving the enterprise's domain.
In some examples, an enterprise customization module can also be configured to generate an API key for each enterprise profile to control access to services of the asset management system. In such examples, the enterprise customization module can receive via user interface 300 an API password 332 and one or more API uniform resource locators (URLs) 334. In some examples, the one or more API URLs can be a domain name associated with enterprise 312. The enterprise customization module can then generate an API key based on the API password 332 and the one or more API URLs 334. In some examples, the API key can be used to authenticate access via an API to services provided by the asset management system. In some examples, an enterprise customization module will only authenticate connections originating from an API URL 334. These features provide the advantage of enhanced security by preventing unauthorized access to assets stored in an enterprise profile. These features can also prevent an enterprise's accidental or incidental access to assets stored in another entity's enterprise profile.
Referring back to
Once user information has been provided, the authorized user can define user-level permissions for the user. In some examples, user-level permissions can include a set of actions the user can or cannot perform. As will be discussed further below, in certain examples an asset management system can include an access control module adapted to control the user's access at least in part based on the user-level permissions. As noted above, user-level permissions can be defined by manually selecting permissible actions, or by using a pre-existing user profile that includes predefined permissions.
As noted above, in some examples, instead of manually selecting permissible actions from set 438, an authorized user can select a pre-existing user profile to streamline the user creation process (e.g., step 405 in method 400 of
In some examples, an enterprise customization module can be configured to automatically create users based on an enterprise's existing directory service. Enterprises typically employ a directory service application to manage access to its intranet, network, and/or extranet. Examples of directory services include Microsoft's Active Directory and Red Hat Directory Server. In some examples, an enterprise customization module can be configured to communicate with an enterprise's existing directory service application to automatically create corresponding users in an enterprise profile. In some examples, the enterprise customization module can be configured to communicate with the enterprise's directory service application using OAuth, SAML, or any other suitable authorization and authentication languages or standards. In some examples, in creating users within an enterprise profile, an enterprise customization module can create the users with user-level permissions according to information received from the enterprise's directory services application. As just one example, the enterprise customization module can determine a title or role of an employee of the enterprise and automatically create a user in the enterprise profile using a corresponding pre-existing user profile.
As noted above, in some examples an enterprise profile can include a plurality of cost centers. Cost centers can be representative of a division of an enterprise, for example a section or business unit. For example, an automobile manufacturer may have three distinct business units each directed to three different car models. It can be appreciated that while the three business units operate under a common enterprise, each business unit may have unique internal organizations and be monetarily isolated from one another. Cost centers can be used to emulate the organizational structure of the automobile manufacturer in an enterprise profile. For example, an authorized user (e.g., a system administrator or a user with the requisite privileges) can create an enterprise profile including a cost center for each of the three business units of the automobile manufacturer. While this example associates cost centers with defined business units of an enterprise, it should be appreciated that in other examples, cost centers can be used to represent any division of an enterprise as convenient for the enterprise to manage its digital assets. For example, in the example above, the automobile manufacturer may have a fourth cost center representative of a marketing department which markets all three products. This feature provides the advantage of allowing assets of an enterprise to be organized, managed, and even financed in a manner consistent with the way each business unit is operated.
In some examples certain facets of digital asset management services can be defined at the cost center level, as compared to the enterprise profile level. Facets of digital asset management services can include, but is not limited to, defining the amount of storage to be allocated to the cost center, the price per unit of storage (e.g., dollars per terabyte), a number of concurrent users allowed to access the cost center, a bandwidth of the cost center (e.g., for uploading and downloading of assets), and administrative privileges and permissions that can be granted to users of the enterprise profile to which the cost center is associated. In some examples, an enterprise customization module can also be adapted to provide automatic notifications for each cost center. For example, the contact of a cost center can be automatically notified when the cost center approaches its storage capacity and provide the contact the option of purchasing more storage. This high degree of configurability and customization at the cost center level provides the distinct advantage of allowing different business units of an enterprise to operate autonomously under one enterprise profile. These features can be particularly advantageous for larger enterprises which require a both consistency and autonomy between its business units. The high degree of configurability and customization at the cost center level also makes the disclosed asset management system particularly useful solution for managing assets for a plurality of enterprises where the enterprises vary in size and organizational structures. It should be appreciated that while the example above describes defining different facets of digital asset management services at a cost center level, other examples of such facets can be defined at the enterprise profile level or a combination of the enterprise level and the cost center level.
In some examples, assets can be uploaded to a cost center then stored and organized in containers and folders. Referring back to
This hierarchical relationship between containers and folders allows enterprises to organize and manage assets within a cost center consistently with an organization and structure of business units of each enterprise. For example, containers of a cost center can be customized and arranged to be representative of an organizational structure of an enterprise's business unit.
In some examples, in creating a container within a cost center an authorized user may also define container-level permissions to access and/or manage the container. In this example, container-level permissions can be automatically set by selecting a pre-defined permission template 720 or by manually selecting permissible actions from a set of actions 722. In some examples, container-level permissions may also be defined on a user-by-user basis by providing one or more sets of users in user list 724. Permissions actions associated with a container may be provided or denied for particular users based on user list 724 and/or the selection of permissible actions from the set of actions 722.
In some examples, a system for managing digital assets for enterprises can include an access control module. In such examples, the access control module can be adapted to control a user's access to containers and folders according to both user-level permissions and container-level permissions. As noted above with reference to
In some examples, an access control module can be configured such that user-level permissions supersede container-level permissions. For example, a vendor may log into an asset management system using a user profile including user-level permissions that allow the vendor to view all containers, folders, and assets in a cost center but prohibits the vendor from downloading any assets without first purchasing the asset. In browsing through the cost center, the vendor encounters a container including container-level permissions that grants the downloading of all assets in the container without having to purchase the asset. In such an example, an access control module can prioritize the permissible actions defined by the vendor's user profile over the container-level permissions of the container. Accordingly, in this example, the vendor will still have to purchase the assets included in the container.
In some examples, an access control module can be configured such that container-level permissions supersede user-level permissions. For instance, in the example above where the vendor's user-level permissions conflict with the container's container-level permissions, when the vendor encounters the container the access control module can prioritize the permissible actions defined by the container-level permissions over the user-level permissions of the vendor's user profile. In this example, the vendor will not have to purchase the assets in the container.
In some examples, an access control module can be configured to prioritize the level of permissions that is more heightened. For example, if user-level permissions require that a user must purchase assets and the container-level permissions do not, an access control module can prioritize the user-level permissions. Conversely, if the container-level permissions require that users purchase assets and the user-level permissions do not, an access control module can prioritize the container-level permissions.
In some examples, an access control module can be configured to selectively prioritize the container-level or the user-level permissions.
There are a number of advantages to controlling access on both a user-level and a container-level and providing for an override option, particularly as it applies to enterprises. For example, a container can be created with container-level permissions that do not require users to purchase assets stored in the container. When the container is accessed by a vendor with user-level permissions that require the purchasing of assets, the vendor will still have to purchase all the assets stored in the container as an access control module prioritizes the user-level permissions over the container-level permissions. In this example, if the override option is selected for the container, an access control module will prioritize the container-level permissions over the vendor's user-level permissions, thereby allowing the vendor to download assets from the container free of charge. Such a situation may arise where a business unit is running a promotion on the assets stored in the container for a limited period of time. In such a situation, the override option can be selected at the beginning of the promotional period, then turned off at the end of the promotional period. A similar situation can arise where a business unit wants to provide a free trial period for a vendor. In this situation, the vendor's user profile can be set to all downloads without purchasing and an override option can be selected for the vendor, thereby allowing the vendor to access and download assets from containers even when container-level permissions require assets to be purchased. It should be appreciated that there are many different situations where controlling access on both a user-level and container-level, and providing an override option at each level can provide an enterprise a high degree of control in managing its assets that can be used to meet various business goals.
In some examples, an access control module can control access based on folder-level permissions in addition to container-level and user-level permissions. In such examples, folder-level permissions are similar to container-level permissions. In some examples, folders can also include an override option to prioritize folder-level permissions.
After receiving the digital assets, the upload module can then receive a location in a cost center in which to upload the files and receive descriptive information about the digital assets. For example,
As noted above, in some examples the upload module can be configured to automatically extract asset metadata from the one or more digital assets. In some examples, the extracted asset metadata can be used to facilitate and streamline the upload process. For example, in
In some examples, an upload module can include features directed to facilitating and streamlining the process of contemporaneously uploading a plurality of digital assets. For example, user interface 940 can include an Apply to All checkbox 949. In this example, when checkbox 949 is selected the upload module will automatically apply descriptive information received in form 944 to all other digital assets to be uploaded. This feature is particularly useful in situations where there is a commonality between at least a subset of the assets to be uploaded. For example, the digital assets in list 926 may have been taken by a single photographer. Specifying the photographer's name, for example, in the “Keywords” or the “Notes” field and selecting the Apply to All checkbox 949 will copy the photographer's name into the descriptive information for all of the other assets to be uploaded. In some examples, the upload module can also be configured to permit a user to modify descriptive information of any of the digital assets to which the descriptive information was automatically copied. For example, where a photographer's name was automatically applied to all the digital assets to be uploaded, a user can select a digital asset from list 926 and delete or modify the automatically copied information.
After the upload module receives descriptive information and automatically extracts asset metadata, the upload module can then generate system metadata based on the descriptive information and the asset metadata. As will be discussed below, system metadata can be used by a search module to facilitate the querying and filtering of assets. Once the system metadata is generated, then the upload module can store the assets and the system metadata in the asset management system. In some examples, the system metadata is distinct from, but associated with, the digital assets. Accordingly, changes can be made to the system metadata without causing the associated digital asset to be modified in any way. This feature allows the digital asset to be stored and preserved in the original state in which it was uploaded while still allowing information about the asset to be updated and modified in the asset management system via the system metadata. For example, additional keywords or notes can be added to the system metadata associated with a digital asset to facilitate searching for the asset.
As noted above, an asset management system can include a search module for querying digital assets. For example, a search module can be adapted to present a user interface to a user for searching one or more databases of the asset management system, receive a search criteria from the user, generate a search query based on the search criteria, and generate search results based on the search query.
In some examples, a search module can be configured to generate search metadata based on the system metadata associated with the search results. In such examples, the search metadata can be used to create search filters 1030 that can be used to refine the search results 1022 to display a subset of the search result 1022. In some examples, the search metadata can comprise only the system metadata associated with each of the digital assets in the search result. For example, search filters 1030 include a filter 1032 to refine the search results according to an audio file type. In this example, filter 1032 only shows a single filter criteria “MP3” because the search results includes only audio files of the file type “MP3.” In some examples, selecting the search filter 1032 will cause user interface 1020 to present to the user only audio files with the file type “MP3.” In some examples, a user can select one or more filters from search filters 1030.
When a user identifies a digital asset of interest, the user can select the preview of the digital asset from search results to 1020 to examine a detailed view of the asset.
In some examples, a search module can be adapted to allow a user to search for assets by browsing a cost center.
In some examples, an asset management system can include a workspace module adapted to facilitate development of assets stored in the system.
In some examples, users of workspace 1110 can collaborate in developing 1124 the asset. In some examples, it is not a prerequisite that a user of workspace 1110 also be a user of the asset management system. For example, workspace 1110 can include its own directory service thereby having a distinct set of users from the asset management system. An authorized user within workspace 1110 can independently invite and manage users to collaborate in developing the asset. Workspace 1110 can be hosted on a server and accessible via a URL. In such examples, an invitation to collaborate can be included as a link in an e-mail or the like. In some examples, workspace 1110 can include a number of features that facilitate the development of the asset. For example, workspace 1110 can include versioning and collaboration features (e.g., live chat, messaging, audio and video conferencing). Once the development of the asset is complete, an authorized user can finalize 1126 the asset and import 1128 the finalized asset back into the asset management repository. In some examples, metadata generated during the course of developing and finalizing the asset can also be imported back into the asset management repository. In some examples, the finalized asset is imported as a new asset distinct from the asset that was exported in step 1122.
Various examples of the invention have been described. Although the present invention has been described in considerable detail with reference to certain disclosed embodiments, the embodiments are presented for purposes of illustration and not limitation. Other embodiments incorporating the invention are possible. One skilled in the art will appreciate that various changes, adaptations, and modifications may be made without departing from the spirit of the invention and the scope of the appended claims
Kelsey, David, Behr, John Paul
Patent | Priority | Assignee | Title |
11568304, | Dec 29 2017 | WELLS FARGO BANK, N A | Semi-structured data machine learning |
11915110, | Dec 29 2017 | Wells Fargo Bank, N.A. | Semi-structured data machine learning |
Patent | Priority | Assignee | Title |
6947959, | Oct 01 1992 | Q LIQUIDATING TRUST | Digital media asset management system and process |
6976028, | Jun 15 2001 | SONY CORPORATION TOKYO JAPAN | Media content creating and publishing system and process |
7921116, | Jun 16 2006 | Microsoft Technology Licensing, LLC | Highly meaningful multimedia metadata creation and associations |
8065303, | Dec 12 2000 | HOME BOX OFFICE, INC. | Digital asset data type definitions |
8341195, | Oct 04 2007 | BEN GROUP, INC | Platform for managing media assets for multi-model licensing over multi-level pricing and asset grouping |
8515902, | Oct 14 2011 | Box, Inc | Automatic and semi-automatic tagging features of work items in a shared workspace for metadata tracking in a cloud-based content management system with selective or optional user contribution |
8583619, | Dec 05 2007 | Box, Inc | Methods and systems for open source collaboration in an application service provider environment |
8655885, | Mar 29 2011 | Open Text SA ULC | Media catalog system, method and computer program product useful for cataloging video clips |
8706778, | Dec 22 2009 | Adobe Inc | Methods and systems for an action-based interface for files and other assets |
8935204, | Aug 14 2009 | EXCESSION TECHNOLOGIES LIMITED | Metadata tagging of moving and still image content |
20040122690, | |||
20070073776, | |||
20080109482, | |||
20080168134, | |||
20080263103, | |||
20080263471, | |||
20090106234, | |||
20090125986, | |||
20090217352, | |||
20100050080, | |||
20100077048, | |||
20100131547, | |||
20110191320, | |||
20130166587, | |||
20130232149, | |||
20130297614, | |||
20140040262, | |||
20140068737, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
May 05 2014 | BEHR, JOHN | MEDIA LOFT | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 035387 | /0747 | |
May 05 2014 | SAZAMA, ANDREW | MEDIA LOFT | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 035387 | /0747 | |
May 05 2014 | STRADEFUSE, INC | MEDIA LOFT | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 035387 | /0747 | |
Jul 03 2014 | MEDIA LOFT | KELSEY, DAVID | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 035387 | /0754 | |
Jul 23 2014 | David, Kelsey | (assignment on the face of the patent) | / |
Date | Maintenance Fee Events |
Feb 15 2021 | M2551: Payment of Maintenance Fee, 4th Yr, Small Entity. |
Date | Maintenance Schedule |
Aug 15 2020 | 4 years fee payment window open |
Feb 15 2021 | 6 months grace period start (w surcharge) |
Aug 15 2021 | patent expiry (for year 4) |
Aug 15 2023 | 2 years to revive unintentionally abandoned end. (for year 4) |
Aug 15 2024 | 8 years fee payment window open |
Feb 15 2025 | 6 months grace period start (w surcharge) |
Aug 15 2025 | patent expiry (for year 8) |
Aug 15 2027 | 2 years to revive unintentionally abandoned end. (for year 8) |
Aug 15 2028 | 12 years fee payment window open |
Feb 15 2029 | 6 months grace period start (w surcharge) |
Aug 15 2029 | patent expiry (for year 12) |
Aug 15 2031 | 2 years to revive unintentionally abandoned end. (for year 12) |