Patent Grant
11968255
Any and all applications for which a foreign or domestic priority claim is identified in the Application Data Sheet as filed with the present application, are hereby incorporated by reference in their entirety under 37 CFR 1.57.
The present invention is related to media collection, processing, and distribution.
As the use of camera-equipped phones has proliferated, the sharing of photographs and videos have become an ever more important form of social engagement. However, conventional techniques for sharing photographs and videos fail to provide a secure, well-defined and recurring system for users to instantly distribute and share their photographs.
The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.
An aspect of the present disclosure relates to systems and processes that enable users to share information and content over a network. Such shared information and content may be instantly distributed over one or more distribution channels and platforms to one or more user devices. The content may also be securely stored in a repository. The user devices may host instantiations of a content sharing application. The content sharing application may be used to capture and/or upload content, such as still or video images, to the secure repository. The content sharing application may be used to receive (e.g., download) content, such as still or video images/photographs, from the secure repository and may render such content. The user devices may selectively store certain galleries received from the secure repository. Optionally, in response to the secure repository detecting that new gallery content has been received, a notification may be transmitted to devices of users with whom the gallery has been shared. Optionally, the notification may include a deep link to the gallery so users can immediately see what content has been added to the gallery. When the user selects the notification, the content sharing application may use the link to access the corresponding gallery on the remote secure repository, and then render the gallery content items, including the new content. Optionally, new content will be presented first in the displayed gallery (e.g., in timestamp order). Optionally, a visual indicator (e.g., a colored dot or other emphasis) may be rendered on user devices in association with content items that have been newly added since the last time the user has viewed the gallery. Optionally, instead or in addition, the secure repository content galleries may be selectively synchronized with the galleries stored on the user devices. Such synchronization may be performed in real time as new content is added to the secure repository content galleries.
An aspect of this disclosure relates to optionally and selectively performing content synchronization to reduce network and processor bandwidth usage.
An aspect of this disclosure relates to the optional performance of real time automatic synchronization of content and galleries across large numbers of systems and devices.
An aspect of this disclosure relates to secure encryption of sensitive data.
An aspect of this disclosure relates to user interfaces configured to make efficient use of display space in presenting data and configured to reduce or minimize accidental user selections.
An aspect of the present disclosure relates to a system for secure content storage and delivery, the secure content storage and delivery system comprising: a computer system comprising one or more computing devices; a network interface; and a computer storage system comprising a non-transitory storage device, said computer storage system having stored thereon executable program instructions that direct the computer system to at least: receive via the network interface, from a first device associated with a first entity, a first group definition; receive via the network interface, from a second device associated with a second entity, a second group definition; transmit via the network interface a first plurality of invitations to a respective first plurality of destinations, the first plurality of invitations comprising an invitation to associate with the first group; transmit via the network interface a second plurality of invitations to a respective second plurality of destinations, the second plurality of invitations comprising an invitation to associate with the second group; receive via the network interface one or more acceptances from users that received a first group invitation; encrypt one or more items of data associated with users that accepted the first group invitation, wherein at least a portion of the encrypted data associated with users that accepted the first group invitation is used to authenticate corresponding users that accepted the first group invitation in a subsequent interaction; associate users from whom first group invitation acceptances were received with the first group; receive via the network interface one or more acceptances from users that received a second group invitation; encrypt one or more items of data associated with users that accepted the second group invitation, wherein at least a portion of the encrypted data associated with users that accepted the second group invitation is used to authenticate corresponding users that accepted the second group invitation in a subsequent interaction; associate users from whom second group invitation acceptances were received with the second group; receive, via the network interface, from the first entity a first content gallery definition; receive, via the network interface, from the first entity an indication that the first content gallery is to be shared with the first group; cause the first content gallery to be instantiated on devices of users associated with the first group; receive, via the network interface, from the first entity a first content request for the first group; transmit, via the network interface, the first content request to users associated with the first group; receive, via the network interface, from a first user associated with the first group, a first item of content and associated metadata provided in response to the first content request; transcode the first item of content from a first size to a second size; cause the transcoded first item of content to be transmitted to users associated with the first group and to appear in instantiations of the first gallery on devices; receive, via the network interface, from the second entity a second content gallery definition; receive, via the network interface, from the second entity an indication that the second content gallery is to be shared with the second group; cause the second content gallery to be instantiated on devices of users associated with the second group; receive, via the network interface, from the second entity a second content request for the second group; transmit, via the network interface, the second content request to users associated with the second group; receive, via the network interface, from a second user associated with the second group, a second item of content and associated metadata provided in response to the second content request; transcode the second item of content from a second size to a second size; and automatically cause the transcoded second item of content to be transmitted to users associated with the second group and to appear in instantiations of the second gallery on devices.
An aspect of the present disclosure relates to a non-transitory storage media having stored thereon executable program instructions configured to direct a computer system to perform operations comprising: receive an invitation to join a first content sharing group; detect a user action corresponding to acceptance of the invitation to join the first content sharing group; at least partly in response to the detected user action corresponding to acceptance of the invitation to join the first content sharing group, cause an acceptance indication to be transmitted to a remote secure content storage and delivery system; in response to an instruction from the remote secure content storage and delivery system, cause a first content gallery to be instantiated on the computer system; enable a thumbnail of an image included in the first content gallery to be rendered as a representation of the first content gallery; enable a title of the first content gallery received from the remote secure content storage and delivery system to be rendered in association with the representation of the first content gallery; enable a number to be rendered in association with the representation of the first content gallery, the number corresponding to a quantity of content items included in the first content gallery; receive a new content item in association with an indication that the new content item is associated with the first content gallery; enable an updated number to be rendered in association with the representation of the first content gallery, the updated number reflecting the association of the new content item with the first content gallery; receive a user selection of the representation of the first content gallery; in response to the user selection of the representation of the first content gallery, cause content items, including the new content item, associated with the first content gallery to be rendered; receive a content request from the remote secure content storage and delivery system; cause the content request from the remote secure content storage and delivery system to be rendered; receive a user provided content item, wherein the user provided content item is provided in response to the displayed content request; and cause the user provided content item to be transmitted in association with an identification of the content request.
An aspect of the present disclosure relates to a computer implemented method comprising: receiving, over a wireless network at a first user device, an invitation to join a first content sharing group; detecting, using a content sharing application installed on the first user device, a user action corresponding to acceptance of the invitation to join the first content sharing group; at least partly in response to the detected user action corresponding to acceptance of the invitation to join the first content sharing group, causing, by the content sharing application, an acceptance indication to be transmitted to a remote system; in response to an instruction from the remote system, causing a first content gallery, using the content sharing application installed on the first user device, to be instantiated on the first user device; enabling, using the content sharing application installed on the first user device, a version of an image included in the first content gallery to be rendered as a representation of the first content gallery; enabling, using the content sharing application installed on the first user device, a title of the first content gallery received from the remote system to be rendered in association with the representation of the first content gallery; enabling, using the content sharing application installed on the first user device, a number to be rendered in association with the representation of the first content gallery, the number corresponding to a quantity of content items included in the first content gallery; receiving, using the content sharing application installed on the first user device, a new content item in association with an indication that the new content item is associated with the first content gallery; enabling, using the content sharing application installed on the first user device, an updated number to be rendered in association with the representation of the first content gallery, the updated number reflecting the association of the new content item with the first content gallery; receiving, using the content sharing application installed on the first user device, a user selection of the representation of the first content gallery; in response to the user selection of the representation of the first content gallery, causing content items, including the new content item, associated with the first content gallery to be rendered; receiving, using the content sharing application installed on the first user device, a content request from the remote system; causing, using the content sharing application installed on the first user device, the content request from the remote system to be rendered; receiving, using the content sharing application installed on the first user device, a user provided content item, wherein the user provided content item is provided in response to the displayed content request; and causing, using the content sharing application installed on the first user device, the user provided content item to be transmitted in association with an identification of the content request.
Embodiments will now be described with reference to the drawings summarized below. These drawings and the associated description are provided to illustrate example embodiments, and not to limit the scope of the invention.
FIG. 2A1 illustrates an example data schema.
As similarly discussed above, as the use of camera-equipped phones and other mobile personal computing devices have proliferated, the sharing of photographs and videos have become an ever more important form of communication and social engagement. However, conventional techniques for sharing photographs and videos fail to provide a secure, well-defined and recurring process or system for users to instantly, securely distribute and share their photographs and videos in a transparent manner. Further, conventional techniques fail to adequately enable users to selectively share galleries of multiple items of content. Still further, conventional techniques fail to adequately provide easy-to-use content sharing interfaces. Yet further, conventional techniques fail to adequately enable the sharing of content across chained social networks.
Systems and methods are described herein that enable users to share information and content (e.g., audio, video, and/or text content), organize information and content, and search for information and content within one or more secure content repositories. Such shared information and content may be shared by users using content sharing applications hosted on user devices (e.g., mobile devices, such as smart cellular phones, tablet computers, laptop computers, wearables; desktop computers; smart televisions, game consoles, and/or other media storage devices; virtual desktops hosted on cloud-based system; and/or the like).
For example, a user may define a plurality of image galleries (which include still image/photograph files, gif files, video files, etc.) via a corresponding user interface. The gallery may optionally be maintained on a cloud-based system. The user may specify, on gallery-by-gallery basis, other users (e.g., defined sets of users or individual users) with whom a given gallery is to be shared.
Copies of some or all of the galleries may be selectively stored on a device of the user that controls the galleries, and/or on may be stored on the devices of those with whom the user is sharing the galleries (e.g., automatically or in response to a manual download command). Optionally, the content size/resolution of a given content item may be down sampled from the original size/resolution to a different size/resolution (e.g., a lower resolution), and a down sampled version may be provided to one or more devices as part of the sharing process. Optionally, a given content item may be transcoded from a first encoding to a second encoding (e.g., to make it more efficient to transmit or to be decoded). As noted above, user devices may include mobile computer devices (e.g., smart phones, tablet computers, laptop computers, wearable devices, and/or the like), desktop computers, smart televisions, game consoles, virtual desktops hosted on cloud-based system, and/or other media storage devices.
Certain example content sharing scenarios will now be described. A content requesting entity (e.g., a company or brand, or someone acting on their behalf) may, via a web application or a content sharing application hosted on a content requesting entity device, invite community members to contribute content (e.g., photographs, video, audio, and/or text content) regarding a specified subject matter. By way of illustration, if the content requesting entity is responsible for a product brand or service brand, the content requesting entity may request specified types of content (e.g., photographs, video, audio, and/or text content) regarding their experiences with the brand's products or services. The request may be provided via a textual message (optionally including images and/or sound content) transmitted to a user device. By way of further illustration, if the content requesting entity is associated with a sport team, the content requesting entity may request specified types of content regarding the team, a player on the team, or regarding a specific sporting event/game. By way of still further illustration, if the content requesting entity is associated with an entertainment entity or entertainment project (e.g., a movie, sound recording, a photograph, etc.), the content requesting entity may request specified types of content regarding the team or regarding the entertainment entity or entertainment project.
The content request may be received from the content requesting entity at a content distribution and secure storage system, which may then route the request to devices of the members of the community.
For example, the content request may be transmitted by the content distribution and secure storage system to and displayed via instantiations of a content sharing application hosted on respective member devices. A given member may generate and record the requested content (e.g., using a camera, microphone, and/or keyboard on the member device). The content may optionally be automatically associated with a gallery specified by the request. The content may be transmitted by the content sharing application to the content requesting entity (e.g., via the content distribution and secure storage system).
When the requested content is received from community members at the content distribution and secure storage system, the content distribution and secure storage system may transmit a notification indicating that the content was received to the application hosted on the content requesting entity's device. The application may in turn provide a visual and/or audio notification of the receipt of the requested. In addition or instead, the notification may be provided via a webpage, email, SMS message, or otherwise.
The requesting entity may then access, via a corresponding interface, the requested content. Optionally, the requested content is downloaded from the content distribution and secure storage system to the requesting entity device (e.g., in response to a manual user download instructions or automatically). Optionally, some or all of the downloaded content (e.g., image content) is downloaded at a lower-than-received-resolution to reduce the amount of network bandwidth needed to store the requested content on the requesting entity device and to reduce the memory on the requesting entity device needed to store the downloaded requested content. Optionally, when the requesting entity selects an item of downloaded content (e.g., by pointing at our touch content as displayed on the requesting entity device), a request for a higher resolution version (e.g., the resolution of the requested content as originally received by the content distribution and secure storage system) is automatically transmitted from the content distribution and secure storage system. The higher resolution version may then be downloaded and/or streamed to the requesting entity device.
The content requesting entity may review the low and/or high resolution versions of the content. The content requesting entity may provide real time feedback to the member that provided the content, specifying any desired content revisions through a messaging interface of the application on the requesting entity device. The feedback may be transmitted to the member device and displayed via the application hosted on the member device. In addition, the content requesting entity may organize content received from members (optionally in association with requester-created content) into content asset galleries (e.g., of videos, photographs, text, etc.). The content asset galleries may be organized by subject, content contributor, date, and/or otherwise. The content asset galleries may optionally be automatically updated in real time as new content is received using metadata associated with the new content.
The content requesting entity may approve the content via a corresponding approval user interface and share the content (e.g., specified asset galleries and/or specified individual items of content) directly with the community and/or via one or more content distribution channels. For example, the content requesting entity may specify, via a corresponding user interface, which gallery is to be shared with which individual community members or sets of community members. When the received content is added to a gallery, the update to gallery may be automatically synchronized to the selected community members/member sets, optionally in real time (e.g., so that when the community members/member sets access their devices they will be able to immediately view the new gallery content via the applications hosted on their devices). Optionally, when new content is added to a gallery, a notification may be automatically transmitted to devices of users with whom the gallery has been shared. Optionally, the notification may include a link to the updated gallery. When a user selects the notification via the user device (e.g., by tapping or clicking on the notification), a content sharing application hosted on the user device may use the link to access the corresponding gallery on the remote secure repository, and then present the gallery, including the new content. Optionally, the gallery content is not stored in non-volatile memory on the user device, and is instead only stored in volatile memory thereby reducing usage of the non-volatile memory. Optionally, rather than sharing entire content galleries, the content requesting entity may share individual items of content with selected members (e.g., on an item by item basis).
The distribution channels may include a variety of content sharing platforms, such as microblogs, social networking platforms, image sharing platforms, and/or the like. Optionally, prior to sharing the content, the content requesting entity may edit the received content, crop the content, color correct the content, rotate the content, extract portions of the content, add logos to the content, add graphic stamps to the content, add animations to the content, add notes, add metadata, and/or the like, save the modified content, and then distribute the content. For example, web-based or content sharing application editing controls may be provided via corresponding user interfaces that enable the foregoing edit-types to be performed, and the resulting edited content to be stored in memory.
In addition, the content requesting entity may also transmit requests to the community members (via the content sharing applications installed on respective community devices) to share the member-created content or content provided by the content requesting entity with the members' social network, via one or more specified or un-specified distribution channels (e.g., microblogs, social networking platforms, image sharing platforms, and/or the like). Thus, content may be shared quickly over chained social networks (wherein a given member may act as a link between the member's social network and the social network of a person in the member's social network) in a mesh matter, advantageously enabling content to be distributed to large number of users and user devices at high speed.
The content distribution and secure storage system may interface with and access a digital asset management (DAM) system of a given entity, and distribute content assets stored on the DAM.
Thus, community member-provided content and/or content provided by an entity (e.g., a sport, entertainment, and/or brand entity) may be distributed over networks in real time or near real time by the entity and/or community members associated with the entity. Such real time or near real time distribution may be used to provide community members (e.g., fans) with frequent, current perspectives on topics and entities of interest.
A search user interface may be provided enabling a user to search for desired content. The search may specify all or part of a gallery name, metadata (e.g., notes) associated with content, a time or time period associated with content creation, time or time period associated with content sharing, a community named, a content contributor name, and/or other search filter conditions. A search engine may receive the search query and filter conditions, identify matching galleries or content, and render the corresponding matching gallery thumbnails or content thumbnails in a search results list (which may be in a grid format) on the user device.
Optionally, the content distribution and secure storage system may generate analytics regarding the sharing of content so that the results of the content may be viewed and understood. The analytic data may include data received from the content sharing applications on user devices and from platforms via which content was shared or re-shared. For example, an application installed on a user device may transmit in real time an indication to the content distribution and secure storage system each time an item of content is viewed or shared via the application. The indication may include an identifier associated with the content item and an identifier associated with the platform/channel used to share the content item.
For example, the content distribution and secure storage system may track and report the number of content sharing requests made by an entity, the number of content items shared (e.g., by individuals and/or by a set of individuals), the date and time an item of content was shared, the platform via which an item of content was shared, the number of events associated with the shared content (e.g., views, clicks on, re-sharing, etc.), the shared content (or a link thereto), total social events, and/or other information. Filter controls may be provided wherein the user may instruct the system to filter the data presented to the entity user via the user interface. For example, a time filter, a shares filter, a media-type filter, and/or platform filters are provided that enable a user to specify for what time period, what type of shares, what type of shared media (e.g., videos, still images, text, etc.), and for what platforms (e.g., FACEBOOK, TWITTER, INSTAGRAM, SNAPCHAT, REDDIT, etc.) the data should be shown.
The analytic data may be updated and distributed in real time to one or more designated destinations/users each time an indication is received that a content item has been shared or acted on.
Certain aspects of the disclosure will now be discussed with reference to the figures.
Referring to
The plurality of user devices 102-1 . . . 102-N and 104-1 . . . 104-N may include standalone computers (e.g., desktop, laptop, tablet, smart phone, smart television, wearable (e.g., a camera equipped watch, eyeglasses, item of clothing, etc.), or other computer device), a centralized computer system, or a cloud computing system. The user devices 102-1 . . . 102-N may be associated with users that provide content (e.g., still images, video images, audio content, text content, and/or the like) to a content requesting entity and/or to other content sharing platforms. User devices 104-1 . . . 104-N may be associated with users that access the content provided by the users of the user devices 102-1 . . . 102-N or by the entity. Of course, a given user and user device may be a provider of content and also a recipient of content.
One or more content sharing platforms 106-1, 106-2 . . . 106-N may communicate over the network 101 with the content distribution and secure storage system 100 and the plurality of user devices 102-1 . . . 102-N and 104-1 . . . 104-N. Content may be shared by the content distribution and secure storage system 100 and by user devices 102-1 . . . 102-N and 104-1 . . . 104-N to the content sharing platforms 106-1, 106-2 . . . 106-N. The content sharing platforms 106-1, 106-2 . . . 106-N may transmit posting or action data to the content distribution and secure storage system 100, which enables the content distribution and secure storage system 100 to generate and present analytic data as discussed elsewhere herein.
The data store 202A may include one or more databases. A given database may be a relational database (e.g., an SQL database) or a non-relational database (a nonSQL database, such as NoSQL). For example, a relational database may advantageously use the same uniform language (e.g., DDL) for different user roles (developer, user, administrator, etc.), may use a standardized language for different relational database management systems, may use an advanced and non-structural querying language, and may comply with ACID principles (atomicity, consistency, isolation, durability), thus ensuring stability, security, and predictability both of the entire database and each transaction. A nonSQL database may be used rather than an SQL database as it better scales out horizontally across distributed systems and so can handle a large number of transactions (e.g., millions of transactions at a time). Further, a nonSQL database may be schema-free and so better utilized with unstructured and semi-structured data. Thus the selection of the database technology may be based on the particular use scenario (e.g., the need for stability and uniformity offered by SQL databases v. The need to process large amounts of unstructured and semi-structured data as provided by a nonSQL database).
The data store 202A may include a galleries data store 222A that may store content. The content may be logically ordered as galleries. A given item of content may be included in more than one gallery (e.g., by storing gallery pointers in the content metadata, or by storing content pointers in the gallery metadata). A given gallery may be associated with and controlled by an entity. For example, a company may have separate galleries for each entity brand. Each brand may have separate galleries for each product in a brand. By way of further example, a sports league may have different galleries for each team, and a team may have galleries for each player and for each game. A given gallery may be organized to include sub-galleries. Thus, there may be a hierarchy of galleries, enabling content to be quickly located and reducing the possibility of the wrong content being inadvertently shared. Content metadata may optionally be stored separately from the content itself. For example, the content may be stored on a cloud-based memory system, and the content metadata may be stored locally or on a different system with a pointer to the corresponding content stored on the cloud-based memory system.
For example, with reference to FIG. 1A1, metadata for a given content item may be stored in the data store 222A with the following metadata:
The data store 202A may include a routing instructions/rules data store 224A that may store a given entity's instructions as to which galleries are to be shared with which users and/or sets/communities of users. The routing instructions may also specify which galleries are to be shared with which content sharing platforms (e.g., microblogs, social networking platforms, image sharing platforms, and/or the like). The routing instructions may also specify when a gallery (or a gallery update) is to be shared. For example, a routing instruction may specify that a gallery update is to be shared in real time with corresponding sets of users. By way of further example, a routing instruction may specify that a gallery update is to be shared at specific dates and/or times. The routing instructions may also specify in which geographical areas a gallery or gallery update is to be shared. For example, if the gallery relates to an event (e.g., a concert or a fair), optionally the gallery is shared with members that are present and/or live in the geographical area of the event (e.g., the same city, the same zip code, the same state, etc.). For example, a member's geographical area may be determined based on location information expressly provided by the member (e.g., during registration) and/or by location data (e.g., determined based on GPS radio data, cell phone data, WiFi data) provided by the member device.
The data store 202A may include an account data store 226A that may store a given entity's contact information, password, content sharing history, analytics, and/or other data. In addition, the account data store may store account records for users that have the content sharing application downloaded to and installed on their devices. For example, a user account record may store a user identifier, a user password, and or a unique identifier associated with the instantiation of the content sharing application stored on the user device. The user account record may store a user email address, mobile phone number (SMS address), physical address, and/or other user data.
To enhance security and reduce the possibility of successful hacking and improper access to user data, the password may be stored in memory using a uni-directional hash (e.g., SHA512) using a combined system and unique user salt. When a user attempts to login (e.g., using a UserID/email address and password) to access the user's account or service, the system 100 may perform the account lookup for authentication by hashing the password supplied during login and comparing the hashed password against the stored value.
Other user information, such as user contact information (e.g., email address, SMS/mobile phone address, etc.) may be encrypted with a combined system and unique user salt, with the result hash data stored. Such contact information may be accessed and decrypted when sending notifications to the user.
The invitation service 204A may be configured to send out an invitation (as instructed by an entity) to one or more users to join a designated community. The invitation may be sent to the content sharing application installed on the users' devices, via email, via text message, or otherwise. If a user accepts the invitation (e.g., by activating an invitation acceptance control presented via the content sharing application, by selecting an invitation acceptance link in the invitation, by entering a code (e.g., an alphanumeric code included in the invitation into a corresponding user interface field, or otherwise), the acceptance is received by the invitation service 204A, and a record is stored indicating that the accepting user is to be assigned to the designated community. Of course, a user may be a member of more than community of more than one entity. Thus, a given user may receive multiple invitations from different entities.
The authentication service 206A authenticates users accessing the system 100 (e.g., an entity that issues content requests, users that upload/stream content to the system 100, users that download/access content stored on the system).
The optional synchronization service 210A may optionally be configured to handle various exception conditions. For example, the synchronization service 210A may be configured to detect when a user device is offline, and in response to detecting that the user device is offline, may attempt to perform content synchronization with the user device at specified intervals or time periods. By way of further example, the synchronization service 210A may be configured to detect when a synchronization process with a user device is interrupted and which content items were synchronized with the user device prior to the synchronization interruption, and in response to detecting that the synchronization interruption, attempt to complete the content synchronization (e.g., with only the not-yet synchronized content) with the user device at specified intervals or time periods. By optionally keeping track of the what content has and has not yet been synchronized with a given user device, the synchronization service 210A avoids wasteful utilization of network bandwidth and processor resources by avoiding re-synchronizing already synchronized content. Optionally, instead of or in addition to the foregoing error handling processes, if the application on the user device detects that its communication has been interrupted (e.g., because there is no network available and/or if all available network bandwidth has been consumed), the application may render an error message indicating the content is not available because of a communication failure, and instructing the user to refresh the application content viewer when the user device has a network (e.g., Internet) connection. If gallery content has not been downloaded to the user device and there is no network access, the user device will not display gallery content.
The analytic service 218 may analyze various types of data and generate data providing insights into the type of content that is popular, shared, viewed, acted on, as well as insight as to which users or sets of users are popular, sharers, viewers, etc. The following types of example information may be tracked and reported.
The user device may include one or more accelerometers/gryometers 218B that measures acceleration in 2 or 3 directions, and/or that measures orientation in 2 or 3 axes. The user device may include a tilt sensor 220B that detects user device tilt. The user device may include location services 222B that detects and report the current location of the user device. For example, the location services 222B may include and/or utilize a global navigation satellite system (GNSS) radio (e.g., a GPS, GLONASS, BeiDou, and/or Galileo GNSS) radios, a cell tower triangulation system, the WiFi location service system, or other system configured to determine and report the device location.
The user device may include one or more wireless communication interfaces 226B. For example, the user device may include a cellular radio, a WiFi modem, a Bluetooth modem, a NFC interface, and/or other wireless interface. The user device may include one or more processing devices 210B which may include code (e.g., module code) to perform the various operations described herein.
The user device may include a content repository 228B which may include content received or shared via a content sharing application 201B.
The content sharing application 201B may include some of all of the following modules: a content receiving module 202B, a gallery management module 204B, a content editor module, 205B, an encryption/decryption module 206B, a content transmission module 208B, and a content editing module 209B. The content receiving module 202B may be configured to receive content from the content distribution and secure storage system 100. The content receiving module 202B may generate a visual and/or audible notification in response to detecting the receipt of content. The visual notification may be presented on a home screen of the user device operating system, on the user device lock screen, and/or by a user interface of the content sharing application 201B (e.g., when the content sharing application 201B is open and being viewed). The gallery management module 204B is configured to cause the received content to be displayed in the appropriate content gallery. The content editor module 205B provides a user interface including content editing controls that enables the user to crop the content, color correct the content, rotate the content, extract portions of the content, add logos to the content, add graphic stamps to the content, add animations to the content, add notes, add metadata, and/or the like. The encryption/decryption module 206B may be used to encrypt and/or decrypt content items received by the content receiving module 202B, transmitted by the application 201B, and/or stored in the content repository 228B.
At block 306, the gallery assignment may be stored in association with the content. At block 308, other metadata may be stored in association with the content. For example, the metadata may include related data provided by the user (e.g., caption, comments, etc.), an identifier of the galleries to which the content has been assigned, a content identifier generated by the content sharing application, an identifier associated with the user, an identifier associated with a requester of the content item, a creation timestamp, a content type indicator, a content category indicator, content resolution data (e.g., in pixels), request text from a request for the content, a content identifier of another content item to which the current content item was uploaded or otherwise provided as a response, and/or other metadata. At bock 310, the content sharing application initiates a transmission of the content and/or associated metadata to a destination. For example, the content and metadata may be transmitted to the content distribution and secure storage system discussed elsewhere herein and/or to a separate cloud storage system. The transmission may be performed in real time in response to detecting the new content, as part of a periodic synchronization process, in response to a request by the content distribution and secure storage system, in response to a manual user command (e.g., activation of an upload control), and/or in response to other events.
Optionally, if the size of a content item to be uploaded is determined by the content sharing application to be greater than a specified threshold, the content sharing application hosted on the user device will automatically down sample the content item to generate a smaller file, and the down sampled content item may be uploaded to thereby reduce network utilization for uploading the content item, and to reduce memory storage needed for the content item. Optionally, if the user device detects that there is no network access available, the content sharing application may queue (e.g., in memory) one or more items of content that are designated for uploading. Once the user device detects that there is network access available, the content sharing application may cause the queued content to be uploaded.
At block 403, metadata and/or content may optionally be encrypted. For example, personally identifying information (e.g., a content contributor's name, email address, phone number, geolocation data, and/or other personal information that may be stored) may be encrypted while optionally other metadata (e.g., the content identifier) may not be encrypted. Optionally, all metadata or no metadata is encrypted. Similarly, content may be optionally be selectively encrypted. For example, content that includes a face (e.g., as determined using a face detection engine, such as an engine that implements Eigen-face techniques or a genetic algorithm) may be encrypted while other content may not be encrypted. Optionally, all content or no content is encrypted. By way of example, metadata image content and other content may be encrypted using a symmetric encryption algorithm, such as Advanced Encryption Standard (e.g., AES-128, AES-192, AES-256.). Optionally, a block cypher may be used for encryption (e.g., utilizing multiple keys). Optionally, RSA may be used for encryption.
At block 404, the process accesses and/or generates additional metadata. For example, the additional metadata may include metadata described herein with respect to the example data schema illustrated in FIG. 2A1, such as a unique ID, a received timestamp, a quality category indicator, and/or other metadata described herein. By way of further example, some of the metadata may be received from a system user (e.g., an administrator) via respective user interface fields, such as approval indicators, notes, title, and/or other system user provided data.
At block 406, the received content, the received content metadata, and the system generated content metadata are stored in memory (e.g., in encrypted or non-encrypted form as appropriate). Optionally, a link to the content may be stored on one system (optionally with content metadata), and the content itself (optionally with content metadata) may be stored on a another (e.g., remote) system.
At block 408, routing and synchronization rules may be accessed from an instructions/rules store. For example, as described elsewhere herein routing instructions/rules store may store instructions/rules as to which galleries are to be shared with which users and/or sets of users, and whether the sharing to be performed on a push basis or on a pull (on-demand) basis. The routing instructions may also specify which galleries are to be shared via which content sharing platforms (e.g., microblogs, social networking platforms, image sharing platforms, and/or the like). The routing instructions may additionally specify when a gallery (or a gallery update) is to be shared and synchronized with user devices. For example, a routing instruction may specify that a gallery update is to be shared in real time with corresponding sets of users. By way of further example, a routing instruction may specify that a gallery update is to be shared at specific dates and/or times. A routing instruction may specify that a gallery update is to be shared on an on-demand basis (e.g., in response to a user opening a content sharing application or activating a refresh control which causes a content update request to be transmitted to the system). The routing instructions may also specify in which geographical areas (e.g., zip code, area code, city, state, GPS coordinates, venue, etc.) a gallery or gallery update is to be shared. For example, if the gallery relates to an event (e.g., a concert or a fair), optionally the gallery is shared with members that are present and/or live in the geographical area of the event (e.g., the same city, the same zip code, the same state, etc.).
If the routing and synchronization rules indicate that the content is to be shared on a push basis, then at block 410, the process determines which user devices/applications are online and available to receive the content. For example, the process may determine if a user device is online by pinging the user device or by determining if a heartbeat signal is being received. If the content is being shared on a pull basis, the process may limit sharing to those devices (e.g., via respective content sharing applications) have requested content updates.
At block 412, the received content and selected portions of the metadata may be downloaded to and synchronized (e.g., over a wireless network) with content repositories on the user devices identified at block 410. Optionally, when the process detects that new content is added to a gallery, a notification may be transmitted over a network to devices of users with whom the gallery has been shared. The notification may include a link to the gallery. When a user selects the notification, a content sharing application hosted on the user device may use the link to access the corresponding gallery on the remote secure repository, and then present the gallery, including the new content.
Optionally, the content may have been down sampled to lower than original resolution (e.g., to thumbnail resolution) before being downloaded to the user device. Optionally, multiple versions of a given content item may be generated via transcoding (from one encoding to a different encoding) and down sampling, and then downloaded to the user device. For example, a high resolution version and thumbnail version may be generated and downloaded to the user device.
The content metadata may be filtered prior to transmission to the user device based on one or more metadata sharing rules. For example, the metadata sharing rules may filter out the content contributor ID, the content requester, the timestamp, the content item type, the content item category, the approval status, the user provided caption, the title, notes, content quality category, content request text, and/or other metadata discussed herein. Such filtering may inhibit the transmission of certain content, thereby reducing network utilization.
For example, if another user adds a photograph to a content gallery (e.g., a gallery hosted on a cloud based storage system), optionally the content distribution and secure storage system may automatically synchronize the gallery update (in accordance with any filter conditions) or provide the entire gallery in response to a notification link activation in real time to user devices that have access to the gallery so that the new content and updates to the gallery data (e.g., the number of content items in the gallery) is provided to the users.
At block 504, the content and some or all of the content metadata is stored in local user device memory (e.g., a content repository). At block 506, If the content sharing application has a galleries user interface displayed, the galleries user interface may display thumbnails of representative images of respective galleries, with a given thumbnail annotated to show how many content items are associated with the gallery. The annotations (examples of which are described elsewhere herein) associated with the galleries may be updated in real time to indicate how many content items are now associated with the respective galleries as a result of the received content. Optionally, a new content indicator may be presented in association with a gallery thumbnail to indicate that the gallery contains content that the user has not yet viewed.
At block 508, a user selection of a gallery may be received (e.g., by the user touching or clicking on a corresponding gallery thumbnail). At block 510, the selected gallery may be “opened” and the associated content items (e.g., images) displayed via a scrollable user interface. The content items may be rendered at relatively low resolution (e.g., as thumbnails). Optionally, new content items may be visually flagged (e.g., using an icon, frame, or other emphasis) by the content sharing application when rendered. For example, optionally each time the content sharing application is opened, or a gallery therein, an access timestamp is recorded. Each time the sharing application is opened, or a gallery therein, the previous access timestamp may be compared against each gallery content item timestamp. Each content item timestamp that is later than the previous access timestamp may be visually flagged by the content sharing application as a new content item so the user may quickly identify the new content.
At block 512, a user selection of a content item is received. At block 514, the selected content item is rendered at higher resolution (e.g., full screen). The higher resolution version of the content item may be accessed from local memory or it may be accessed from the content distribution and secure storage system.
Certain example user interfaces will now be described with reference to the figures. The user interfaces may optionally be specifically configured to be served by a web server for display via a web browser hosted on a user device, or the user interfaces may be presented via a dedicated application (e.g., the content sharing application discussed herein) hosted on a user device. The user interfaces may optionally be specifically be configured to be displayed and utilized via a relatively small touch-enabled display (e.g., a smart phone or tablet touch display), or to be displayed and utilized via a relatively large display (e.g., a laptop, desktop, or television display, which may or may not be touch-enabled).
Still referring to
As discussed elsewhere herein, an invitation may be sent to a user to join a designated community. The invitation may be sent to the content sharing application installed on the users' devices, via email, via text message, or otherwise. The invitation may include a unique invitation code. The user interface illustrated in
The user interface illustrated in
The user interface includes a social sharing table including the following columns for a different content item:
A total/aggregated social events number may be reported via the user interface for all of the content items.
Filter controls may be provided (e.g., via drop down menus) via which the user can have the system filter the sharing data displayed by the content sharing table. For example, the filter may enable the user to specify a time period (e.g., all time, previous month, previous day, current day, a specified start-end period, etc.), the types of shares, the types of content media shares, and the sharing platforms (e.g., FACEBOOK, TWITTER, INSTAGRAM, SNAPCHAT, etc.) for which data is to be reported (thereby more efficiently using display real estate).
A search field may be provided via which the user can search for content share data for a given content item by name.
A menu on the left provides access to other user interfaces, such as a request content user interface, a share content user interface, a network user interface, a content requests user interface (which provides a list of existing content requests), the content shares user interface, a content library user interface, a content approval user interface, a content contributor messaging user interface, a branding user interface, and a configuration user interface. This menu may be included in each of the foregoing user interfaces to provide quick and reliable access to a desired user interface.
In response to the user selecting a content item (e.g., a still or video image) in a gallery, the example content view user interface illustrated in
Thus, an aspect of the present disclosure relates to systems and processes that enable users to securely share information and content over a network. Such shared information and content may be instantly distributed over one or more distribution channels and platforms to one or more user devices. The content may also be securely stored in a repository.
Certain embodiments may be implemented via hardware, software stored on media, or a combination of hardware and software. For example, certain embodiments may include software/program instructions/modules stored on tangible, non-transitory computer-readable medium (e.g., magnetic memory/discs, optical memory/discs, RAM, ROM, FLASH memory, other semiconductor memory, etc.), accessible by one or more computing devices configured to execute the software (e.g., servers or other computing device including one or more processors, wired and/or wireless network interfaces (e.g., cellular, Wi-Fi, Bluetooth, Ti, DSL, cable, optical, or other interface(s) which may be coupled to the Internet), content databases, customer account databases, etc.). Data stores (e.g., comprising databases) may be used to store some or all of the information discussed herein in memory.
By way of example, a given computing device may optionally include user interface devices, such as some or all of the following: one or more displays, keyboards, touch screens, speakers, microphones, mice, track balls, touch pads, tilt sensors, accelerometers, biometric sensors (e.g., fingerprint or face recognition sensors for authenticating a user) printers, etc. The computing device may optionally include a media read/write device, such as a CD, DVD, Blu-ray, tape, magnetic disc, semiconductor memory, or other optical, magnetic, and/or solid state media device. A computing device, such as a user terminal, may be in the form of a general purpose computer, a personal computer, a laptop, a tablet computer, a mobile or stationary telephone, an interactive television, a set top box coupled to a display, etc. Certain embodiments may be able to conduct hundreds (or more) of transactions and processes described herein within a second.
While certain embodiments may be illustrated or discussed as having certain example components, additional, fewer, or different components may be used. Processes described as being performed by a given system may be performed by a user terminal or other system or systems. Processes described as being performed by a user terminal may be performed by another system. Data described as being accessed from a given source may be stored by and accessed from other sources. Transmissions described herein may be via a wired and/or wireless network or other communications link. Further, with respect to the processes discussed herein, various states may be performed in a different order, not all states are required to be reached, and fewer, additional, or different states may be utilized.
User interfaces described herein are optionally presented (and user instructions may be received) via a user computing device using a browser, other network resource viewer, or otherwise. For example, the user interfaces may be presented (and user optionally instructions received) via an application (sometimes referred to as an “app”), such as a dedicated app configured specifically for social networking and/or communications activities, installed on the user's mobile phone, laptop, pad, desktop, television, set top box, phone, or other terminal. For example, an app may be downloaded to a user mobile device, such as a smart phone. Various features described or illustrated as being present in different embodiments or user interfaces may be combined into the same embodiment or user interface.
Various aspects and advantages of the embodiments have been described where appropriate. It is to be understood that not necessarily all such aspects or advantages may be achieved in accordance with any particular embodiment. Thus, for example, it should be recognized that the various embodiments may be carried out in a manner that achieves or optimizes one advantage or group of advantages as taught herein without necessarily achieving other aspects or advantages as may be taught or suggested herein. Further, embodiments may include several novel features, no single one of which is solely responsible for the embodiment's desirable attributes or which is essential to practicing the systems, devices, methods, and techniques described herein. In addition, various features of different embodiments may be combined to form still further embodiments. For example, aspects found in different user interfaces may be combined to form still further user interface.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6938005 | Iverson et al. | Aug 2005 | B2 |
| 7577979 | Feinleib et al. | Aug 2009 | B2 |
| 7757254 | Shoff et al. | Jul 2010 | B2 |
| 7809603 | Steelberg et al. | Oct 2010 | B2 |
| 8024467 | Humphrey et al. | Sep 2011 | B2 |
| 8032470 | Heidenreich | Oct 2011 | B1 |
| 8539542 | Elhag | Sep 2013 | B1 |
| 8607295 | Bhatia et al. | Dec 2013 | B2 |
| 8612243 | McGill et al. | Dec 2013 | B2 |
| 8693848 | Pacor | Apr 2014 | B1 |
| 8782140 | Green | Jul 2014 | B1 |
| 8817065 | Mo | Aug 2014 | B1 |
| 8819719 | Chen et al. | Aug 2014 | B1 |
| 8943140 | Kothari | Jan 2015 | B1 |
| 9015251 | Green | Apr 2015 | B2 |
| 9063972 | Marra | Jun 2015 | B1 |
| 9071579 | Bender | Jun 2015 | B1 |
| 9081823 | Luo | Jul 2015 | B2 |
| 9104892 | Le Chevalier | Aug 2015 | B2 |
| 9280610 | Gruber | Mar 2016 | B2 |
| 9300620 | Bradley | Mar 2016 | B2 |
| 9300678 | Stack | Mar 2016 | B1 |
| 9348823 | Green | May 2016 | B2 |
| 9355387 | Dixon | May 2016 | B1 |
| 9461958 | Green | Oct 2016 | B1 |
| 9544379 | Gauglitz | Jan 2017 | B2 |
| 9762629 | Bhargava | Sep 2017 | B1 |
| 9942189 | Green | Apr 2018 | B2 |
| 10051103 | Gordon | Aug 2018 | B1 |
| 10083469 | Traina | Sep 2018 | B1 |
| 10154001 | Green | Dec 2018 | B2 |
| 10257301 | Giordano | Apr 2019 | B1 |
| 10380168 | Green | Aug 2019 | B2 |
| 10438094 | Ko | Oct 2019 | B1 |
| 10440169 | Gordon | Oct 2019 | B1 |
| 10554696 | Singh | Feb 2020 | B2 |
| 10574622 | Green | Feb 2020 | B2 |
| 10599285 | Roos | Mar 2020 | B2 |
| 10628185 | Gupta | Apr 2020 | B1 |
| 10693956 | Green | Jun 2020 | B1 |
| 10909586 | Avedissian | Feb 2021 | B2 |
| 11057337 | Green | Jul 2021 | B2 |
| 11157541 | Green | Oct 2021 | B2 |
| 11240299 | Green | Feb 2022 | B2 |
| 20010032189 | Powell | Oct 2001 | A1 |
| 20020016969 | Kimble | Feb 2002 | A1 |
| 20020073177 | Clark et al. | Jun 2002 | A1 |
| 20030229900 | Reisman | Dec 2003 | A1 |
| 20060174316 | Gregorian et al. | Aug 2006 | A1 |
| 20060253542 | McCausland et al. | Nov 2006 | A1 |
| 20070038931 | Allaire | Feb 2007 | A1 |
| 20070089151 | Moore et al. | Apr 2007 | A1 |
| 20070162566 | Desai et al. | Jul 2007 | A1 |
| 20080092181 | Britt | Apr 2008 | A1 |
| 20080103906 | Singh | May 2008 | A1 |
| 20080120324 | Davis | May 2008 | A1 |
| 20080147741 | Gonen | Jun 2008 | A1 |
| 20080177752 | Kulkarni et al. | Jul 2008 | A1 |
| 20080209480 | Eide et al. | Aug 2008 | A1 |
| 20080244681 | Gossweiler et al. | Oct 2008 | A1 |
| 20080247543 | Mick et al. | Oct 2008 | A1 |
| 20090044235 | Davidson | Feb 2009 | A1 |
| 20090060289 | Shah et al. | Mar 2009 | A1 |
| 20090089294 | Davis et al. | Apr 2009 | A1 |
| 20090094039 | Macdonald | Apr 2009 | A1 |
| 20090148124 | Athsani | Jun 2009 | A1 |
| 20090172129 | Singh et al. | Jul 2009 | A1 |
| 20090204885 | Ellsworth et al. | Aug 2009 | A1 |
| 20090210291 | Safar | Aug 2009 | A1 |
| 20090210808 | West | Aug 2009 | A1 |
| 20090328087 | Higgins et al. | Dec 2009 | A1 |
| 20100088394 | Barbieri et al. | Apr 2010 | A1 |
| 20100293598 | Collart et al. | Nov 2010 | A1 |
| 20110004831 | Steinberg | Jan 2011 | A1 |
| 20110035503 | Zaid | Feb 2011 | A1 |
| 20110082808 | Beykpour et al. | Apr 2011 | A1 |
| 20110106835 | Lauridsen | May 2011 | A1 |
| 20110126148 | Krishnaraj | May 2011 | A1 |
| 20110173214 | Karim | Jul 2011 | A1 |
| 20110225239 | Kansai | Sep 2011 | A1 |
| 20110225508 | Steelberg et al. | Sep 2011 | A1 |
| 20110264521 | Straka | Oct 2011 | A1 |
| 20110264599 | Dalton | Oct 2011 | A1 |
| 20110276423 | Davidson | Nov 2011 | A1 |
| 20110289157 | Pirnazar | Nov 2011 | A1 |
| 20110311205 | McClanahan | Dec 2011 | A1 |
| 20120004956 | Huston | Jan 2012 | A1 |
| 20120005209 | Rinearson | Jan 2012 | A1 |
| 20120042263 | Rapaport | Feb 2012 | A1 |
| 20120072835 | Gross | Mar 2012 | A1 |
| 20120096041 | Rao | Apr 2012 | A1 |
| 20120123811 | Socolof | May 2012 | A1 |
| 20120130807 | Steelberg et al. | May 2012 | A1 |
| 20120185238 | Bhatti | Jul 2012 | A1 |
| 20120192225 | Harwell et al. | Jul 2012 | A1 |
| 20120192239 | Harwell | Jul 2012 | A1 |
| 20120233000 | Fisher | Sep 2012 | A1 |
| 20120233646 | Coniglio et al. | Sep 2012 | A1 |
| 20120236201 | Larsen | Sep 2012 | A1 |
| 20120245952 | Halterman | Sep 2012 | A1 |
| 20120254301 | Fiero | Oct 2012 | A1 |
| 20120272164 | Polonsky | Oct 2012 | A1 |
| 20120304237 | Harwell et al. | Nov 2012 | A1 |
| 20120316962 | Rathod | Dec 2012 | A1 |
| 20120317227 | Bettinger | Dec 2012 | A1 |
| 20130014136 | Bhatia | Jan 2013 | A1 |
| 20130080565 | van Coppenolle | Mar 2013 | A1 |
| 20130086185 | Desmarais | Apr 2013 | A1 |
| 20130086631 | Archer et al. | Apr 2013 | A1 |
| 20130132847 | Chen | May 2013 | A1 |
| 20130151970 | Achour | Jun 2013 | A1 |
| 20130159295 | Gross | Jun 2013 | A1 |
| 20130166649 | Atzmon | Jun 2013 | A1 |
| 20130198655 | Whitnah | Aug 2013 | A1 |
| 20130226675 | Senra | Aug 2013 | A1 |
| 20130226708 | Good et al. | Aug 2013 | A1 |
| 20130226758 | Reitan | Aug 2013 | A1 |
| 20130227384 | Good et al. | Aug 2013 | A1 |
| 20130227596 | Pettis et al. | Aug 2013 | A1 |
| 20130238444 | Munaco | Sep 2013 | A1 |
| 20130254804 | Diaz Perez | Sep 2013 | A1 |
| 20130268828 | Bucchieri | Oct 2013 | A1 |
| 20130282839 | Alcala | Oct 2013 | A1 |
| 20130283301 | Avedissian | Oct 2013 | A1 |
| 20130030457 | Fetyko | Nov 2013 | A1 |
| 20130304527 | Santos, III | Nov 2013 | A1 |
| 20130304575 | Fetyko | Nov 2013 | A1 |
| 20130304820 | Vasquez | Nov 2013 | A1 |
| 20130311906 | Mackin | Nov 2013 | A1 |
| 20130312049 | Niyogi et al. | Nov 2013 | A1 |
| 20130321388 | Locke | Dec 2013 | A1 |
| 20130332213 | Heggen | Dec 2013 | A1 |
| 20130332523 | Luu | Dec 2013 | A1 |
| 20130332603 | Hutten | Dec 2013 | A1 |
| 20130346172 | Wu | Dec 2013 | A1 |
| 20140013228 | Hutten | Jan 2014 | A1 |
| 20140019882 | Chew | Jan 2014 | A1 |
| 20140047074 | Chung | Feb 2014 | A1 |
| 20140082645 | Stern | Mar 2014 | A1 |
| 20140095637 | Cropper | Apr 2014 | A1 |
| 20140108372 | Oh | Apr 2014 | A1 |
| 20140108547 | Rao | Apr 2014 | A1 |
| 20140129963 | Portale | May 2014 | A1 |
| 20140136554 | Moradi | May 2014 | A1 |
| 20140137144 | Jarvenpaa | May 2014 | A1 |
| 20140150029 | Avedissian | May 2014 | A1 |
| 20140171039 | Bjontegard | Jun 2014 | A1 |
| 20140173644 | Ball | Jun 2014 | A1 |
| 20140173648 | Ball | Jun 2014 | A1 |
| 20140181120 | Sullivan | Jun 2014 | A1 |
| 20140181196 | Sullivan | Jun 2014 | A1 |
| 20140186004 | Hamer | Jul 2014 | A1 |
| 20140188681 | Shahghasemi | Jul 2014 | A1 |
| 20140188741 | Lustberg | Jul 2014 | A1 |
| 20140192199 | Tan et al. | Jul 2014 | A1 |
| 20140195625 | Weldon | Jul 2014 | A1 |
| 20140195675 | Silver | Jul 2014 | A1 |
| 20140200974 | Morin | Jul 2014 | A1 |
| 20140211090 | Faratzis | Jul 2014 | A1 |
| 20140214522 | Skollar | Jul 2014 | A1 |
| 20140237492 | Jones | Aug 2014 | A1 |
| 20140237497 | Jones | Aug 2014 | A1 |
| 20140240247 | Jin | Aug 2014 | A1 |
| 20140253727 | Sadrieh | Sep 2014 | A1 |
| 20140267562 | Lemmey | Sep 2014 | A1 |
| 20140280540 | Wurtele | Sep 2014 | A1 |
| 20140280555 | Tapia | Sep 2014 | A1 |
| 20140282016 | Hosier, Jr. | Sep 2014 | A1 |
| 20140289337 | Green | Sep 2014 | A1 |
| 20140297652 | Stevens | Oct 2014 | A1 |
| 20140313341 | Stribling | Oct 2014 | A1 |
| 20140325402 | Jung | Oct 2014 | A1 |
| 20140337436 | Hoagland | Nov 2014 | A1 |
| 20140365580 | Azenkot | Dec 2014 | A1 |
| 20140372910 | Alford Mandzic | Dec 2014 | A1 |
| 20150058380 | Polonsky | Feb 2015 | A1 |
| 20150067102 | Tsarkova | Mar 2015 | A1 |
| 20150088622 | Ganschow | Mar 2015 | A1 |
| 20150134684 | Montana | May 2015 | A1 |
| 20150154385 | Chastagnol | Jun 2015 | A1 |
| 20150161565 | Kraft | Jun 2015 | A1 |
| 20150220526 | Green | Aug 2015 | A1 |
| 20150245097 | Agrawal | Aug 2015 | A1 |
| 20150312354 | Boyle | Oct 2015 | A1 |
| 20160006981 | Bauman | Jan 2016 | A1 |
| 20160007083 | Gurha | Jan 2016 | A1 |
| 20160042418 | Traina | Feb 2016 | A1 |
| 20160155475 | Hamer | Jun 2016 | A1 |
| 20160173738 | Jones | Jun 2016 | A1 |
| 20160180883 | Hamer | Jun 2016 | A1 |
| 20160343037 | Nicholas | Nov 2016 | A1 |
| 20170039867 | Fieldman | Feb 2017 | A1 |
| 20170054858 | Coelho | Feb 2017 | A1 |
| 20170068361 | Imbruce | Mar 2017 | A1 |
| 20170093780 | Lieb | Mar 2017 | A1 |
| 20170099512 | Oshminer | Apr 2017 | A1 |
| 20170131855 | Svendsen | May 2017 | A1 |
| 20170134783 | Boyle | May 2017 | A1 |
| 20170134831 | Talukder | May 2017 | A1 |
| 20170244655 | Moon | Aug 2017 | A1 |
| 20180034865 | Schoonmaker | Feb 2018 | A1 |
| 20180040017 | Chung | Feb 2018 | A1 |
| 20180262884 | Hosier, Jr. | Sep 2018 | A1 |
| 20190012059 | Kwon | Jan 2019 | A1 |
| 20190149954 | Erickson | May 2019 | A1 |
| 20200125218 | Bender | Apr 2020 | A1 |
| 20200387995 | Bucciarelli | Dec 2020 | A1 |
| 20210067586 | Jhanji | Mar 2021 | A1 |
| 20230308502 | Lu | Sep 2023 | A1 |
| Entry |
|---|
| http://www.filmindependent.org/blogs/check-out-chideo-its-a-coll-idea-for-a-good-cause/#,U1485IN0Azq, “Check Out Chideo: It's a Cool Idea for a Good Cause,” Sep. 2013. |
| https://itunes.aople.com/us/app/chido/id666170718?rnt=8, “Chideo,” Sep. 2013. |
| JockTalk Startup Looks to Boost Pro Athletes' Social Media Leverage, http://mashable.com/2012/04/13/jocktalk-startup/, (2012). |
| Jocktalk, http://web.archive.org/web/20121025092745/http://www.jocktalk.com/, (Oct. 25, 2012). |
| PCT International Search Report and Written Opinion dated May 15, 2017, Application No. PCT/US2017/017182, 9 pp. |
| Extended European Search Report received in European Patent Application No. EP17756987, dated Sep. 15, 2019. |
| Office Action received in Australian Patent Application No. 2017223169, dated Dec. 18, 2020, four pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20220239731 A1 | Jul 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16902706 | Jun 2020 | US |
| Child | 17647888 | US | |
| Parent | 16389743 | Apr 2019 | US |
| Child | 16902706 | US |
