SYSTEM AND METHOD FOR ASSESSING THE TRUST OF CLIENT DEVICES IN A DISTRIBUTED COMPUTING SYSTEM - Patent application

By generating and using partial trust metrics to assess client devices, the system addresses unauthorized access issues, improving security and content delivery stability in content distribution platforms.

JP7595774B2Active Publication Date: 2024-12-06GOOGLE LLC
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2023541340
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2021-03-03
Filing Date
2022-03-03
Publication Date
2024-12-06
Estimated Expiration
2042-03-03

AI Technical Summary

Technical Problem

Current content distribution platforms face challenges in accurately assessing the trustworthiness of client devices, leading to unauthorized access and potential security breaches due to the use of unlicensed media players, which can deceive the system and compromise content delivery and user data security.

Method used

The system generates partial trust metrics based on data available to the content sharing platform, which are appended to resource locators and digitally signed, enabling the CDN server to determine the trust status of client devices and adjust content delivery accordingly, using heuristic or machine learning techniques to evaluate factors such as user history and device authenticity.

Benefits of technology

This approach enhances security by verifying the authenticity of media players without lengthy verification processes, reducing computational and bandwidth usage, and ensuring stable content delivery while protecting against unauthorized functions and data breaches.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007595774000001
    Figure 0007595774000001
  • Figure 0007595774000002
    Figure 0007595774000002
  • Figure 0007595774000003
    Figure 0007595774000003
Patent Text Reader

Abstract

The method includes receiving, by a processing device of a content sharing platform, a request for desired content from a client device, the content being stored in a content delivery network (CDN). The method further includes generating a partial trust metric associated with the client device based on data available to the content sharing platform, the partial trust metric to be used by a CDN server to make a decision regarding access to the desired content by the client device. The method further includes generating a response to the content request, the response including one or more resource locators for accessing the desired content in the CDN and the partial trust metric. The method further includes transmitting the response to the client device to enable the client device to request the desired content from the CDN server using the resource locators and the partial trust metric.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] Aspects and embodiments of the present disclosure relate to content sharing platforms, and more particularly, to assessing the trust of client devices in a distributed computing system. [Background technology]

[0002] Content distribution platforms that connect via the Internet enable users to connect with each other and share information. Many content distribution platforms include content sharing aspects that allow users to upload, view, and share content, such as video items, image items, audio items, and the like. Other users of the content distribution platforms may comment on the shared content, discover new content, identify updates, share content, and otherwise interact with the provided content. Shared content may include content from professional content creators, e.g., movie clips, TV clips, and music video items, as well as content from amateur content creators, e.g., video blogs and short original video items. Summary of the Invention [Means for solving the problem]

[0003] An aspect of the present disclosure provides a method including: receiving, by a processing device of a content sharing platform, a request for desired content from a client device, the content being stored in a content delivery network (CDN); generating a partial trust metric associated with the client device based on data available to the content sharing platform, the partial trust metric to be used by a CDN server to make a decision regarding access to the desired content by the client device; generating a response to the content request, the response including one or more resource locators for accessing the desired content in the CDN and the partial trust metric; and sending the response to the client device to enable the client device to request the desired content from the CDN server using the one or more resource locators and the partial trust metric.

[0004] A further aspect of the present disclosure provides a system including a memory and a processing device coupled to the memory, for receiving, by the processing device of a content sharing platform, a request for desired content from a client device, where the content is stored in a content delivery network (CDN); generating a trust package associated with the client device based on data available to the content sharing platform, where the trust package will be used by a CDN server to make a decision regarding access to the desired content by the client device; generating a response to the content request, where the response includes one or more resource locators for accessing the desired content in the CDN and the trust package; and sending the response to the client device to enable the client device to request the desired content from the CDN server using the one or more resource locators and the trust package.

[0005] A further aspect of the present disclosure provides a computer program product (such as a tangible computer readable medium or software product that may be downloaded without necessarily being stored for a non-transitory method) that includes instructions that, upon execution by a processing device, cause the processing device to perform operations including a method according to any aspect or embodiment described herein.

[0006] Aspects and embodiments of the present disclosure will become more fully understood from the detailed description and accompanying drawings given under various aspects and embodiments of the present disclosure, which should not be construed as limiting the present disclosure to any particular aspect or embodiment, but are for purposes of illustration and understanding. [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 illustrates an exemplary system architecture according to one embodiment of the present disclosure. [Diagram 2] 4 is a diagram of operations for assessing the trust of a client device according to an embodiment of the present disclosure. [Diagram 3] FIG. 11 is another diagram of operations for assessing the trust of a client device according to an embodiment of the present disclosure. [Figure 4] 1 is a flow diagram of a method for generating a partial trust metric according to an embodiment of the present disclosure. [Diagram 5] 4 is a flow diagram of a method for determining a trust status of a client device according to an embodiment of the present disclosure. [Figure 6] FIG. 1 is a block diagram illustrating an exemplary computer system according to one embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] A content sharing platform (also referred to herein as a “content delivery platform”) may offer content, such as video items, audio items, or game items, to a user via a client device. A user may log into a user account associated with the content sharing platform to access the content sharing platform and upload and / or consume content. The content sharing platform may use a content distribution network (CDN) (also referred to herein as a “content delivery network”) to store content and provide the content to client devices. A CDN may include a geographically distributed network of servers working together to provide high availability and high performance of content delivery. For example, server A of the CDN that is in the same geographical vicinity as client device A may be selected to deliver content to client device A. The content delivered by server A may be delivered to client device A more quickly than another server, server B of the CDN, that is not in the same geographical vicinity as client device A.

[0009] In some systems, a user may request content from a content sharing platform via a media player (e.g., a mobile application, a web browser, etc.) on a client device. The content sharing platform may use an authorization service to authorize a user account associated with the user to determine whether the user has permission to access the requested content. If the user account is authorized to access the content, the content sharing platform may generate one or more resource locators (e.g., uniform resource locators (URLs)) that may be used by the client device to obtain the requested content from the CDN. For example, the content sharing platform may generate the URLs and send those URLs to the client device, and the client device may use the URLs to request the desired content from the CDN.

[0010] However, in some cases, a user may use an unauthorized media player (e.g., an overlay application, a third-party media player, a modified media player, etc.) to access content from a CDN and perform unauthorized functions on the received content. For example, an unauthorized media player may be able to download the received content to a local storage medium, a feature that may be prohibited by the content sharing platform. In other cases, a user may deceive the content sharing platform and the CDN by requesting a URL from the content sharing platform using an authorized media player and then using the URL to request content from the CDN using the unauthorized media player. Such deception may be possible because, for security reasons, the content sharing platform may wish not to share data regarding user account information, verification protocols, etc. with the CDN (which may be more vulnerable to security breaches than the content sharing platform's highly privileged core services), and thus the CDN may not be able to accurately assess the trustworthiness of the client device sending the request for content.

[0011] Therefore, in current systems, it is difficult to identify content requests from unauthorized media players, which may cause the content sharing platform and / or CDN to erroneously grant unauthorized media players permission to access the requested content, leading to the unauthorized media players performing unauthorized functions on the received content.

[0012] Aspects and implementations of the present disclosure address these and other shortcomings of existing technologies by enabling a content sharing platform to generate a partial trust metric for use by a CDN to determine the trustworthiness (e.g., authenticity) of a client device. In an exemplary embodiment, in response to receiving a request for content from a client device, the content sharing platform can generate a partial trust metric for the client device. The partial trust metric can be any score, indicator, or other type of quantifiable measure used to indicate to the CDN the authenticity of the client device, the media player used by the client device, or the user account associated with the user. In particular, the partial trust metric can be created based on data available to the content sharing platform and can be used to indicate to the CDN the likelihood that the user, media player, and / or client device will be authorized to access the requested content, as opposed to unauthorized entities such as third-party media players, bots, unauthorized entities of server farms, etc. The data used to create the partial trust metric can include factors related to the client device, the user account, the media player, or any combination thereof. In some embodiments, the factors may include the user's viewing history, whether the user has previously viewed the content, whether the client device has previously successfully decrypted the content, whether the user is logged in, whether the user has engaged in or is suspected of engaging in unauthorized activity, the IP address of the client device, encryption logs associated with the client device, etc. In some embodiments, the content sharing platform may generate the partial trust metric by using heuristic, machine learning, or other techniques.

[0013] The content sharing platform can then generate one or more resource locators (e.g., uniform resource locators (URLs)) to enable the client device to request the desired content from the CDN. The content sharing platform can append the partial trust metrics to the resource locators and digitally sign the resulting response. The digital signature can be based on signed parameters used to indicate to the CDN how the data should be provided (e.g., an expiration parameter indicating when use of the resource locator and / or partial trust metrics should expire, a bitrate parameter for delivering the requested content, an identifier of a playback event created for and associated with the content request, etc.). The client device can use the resource locator and partial trust metrics received from the content sharing platform to request the content from the CDN server.

[0014] In response to receiving a request with a resource locator and partial trust metrics from a client device, the CDN server can determine a trust status of the client device based on the partial trust metrics. The trust status of the client device can be any kind of indicator used by the CDN to determine whether the requested content should be provided to a user. In some embodiments, the CDN can use the partial trust metrics and one or more additional factors identified by the CDN (based on information available to the CDN) to obtain a final trust metric and compare the final trust metric to one or more thresholds to determine the trust status of the client device (e.g., high trust, medium trust, low trust). Based on the comparison, the CDN can reduce or cap the resolution of the requested content (e.g., from high definition to standard definition), reduce or cap the frame rate, etc.

[0015] In some embodiments, if the content sharing platform provides multiple resource locators for the desired content, the client device sends a separate request to the CDN server for each resource locator and includes in each of these requests the partial trust metric received from the content sharing platform. Based on the partial trust metric included in each request, the CDN server can ensure that all of the multiple requests for the desired content (e.g., multiple requests for portions of a particular video) are from trusted media players, thereby protecting against malicious users who may use an authorized media player to obtain an initial portion of the desired content and then switch to an unauthorized player for the remaining portions of the desired content.

[0016] In some embodiments, rather than (or in addition to) providing a partial trust metric to the client device, the content sharing platform may provide a trust package that includes multiple characteristics indicating, for example, whether the user is logged in, the type of browser used by the user to request the content, the geographic location of the client device, the IP address of the client device, etc. When requesting content from a CDN server, the client device may provide the trust package to the CDN server, which may then use the characteristics from the trust package (and in some embodiments information locally available to the CDN server) to determine whether to provide the requested content to the user.

[0017] Aspects of the present disclosure provide technical advantages in improved performance of media players on client devices, improved security of content stored by the CDN, improved security of user data, and improved security of the overall performance of the content sharing platform. In particular, aspects of the present disclosure enable content sharing platforms and CDNs to verify the authenticity of media players requesting content without exposing users to the latency associated with lengthy verification techniques. Thus, the technology disclosed herein enables users to have a stable and uninterrupted viewing experience. Additionally, aspects of the present disclosure enable CDNs to verify user accounts and / or client devices based on an opaque partial trust measure that does not expose the CDN to information known to the highly protected core services of the content sharing platform (which may be vulnerable to external attacks) used to generate the partial trust measure. Additionally, the technology disclosed herein may include reducing consumption of computational, memory, and bandwidth resources by the content sharing platform by enabling the CDN to perform authorization for delivery of requested content.

[0018] Implementations of this disclosure often refer to video for simplicity and brevity, but the teachings of this disclosure apply broadly to media items and may be applied to various types of content including, for example, video, audio, text, images, program instructions, and the like.

[0019] 1 illustrates an exemplary system architecture 100 according to one implementation of the present disclosure. The system architecture 100 (also referred to herein as the "system") includes a content sharing platform 120 (also referred to herein as the "content distribution platform"), a data store 106, client devices 110A-110Z (collectively referred to herein as "client devices 110") connected to a network 104, and a content distribution network (CDN) 130 (also referred to herein as the "content delivery network"). The CDN 130 may include multiple server machines 132A-132Z (also referred to herein as "servers 132A-132Z").

[0020] The network 104 may include a public network (e.g., the Internet), a private network (e.g., a local area network (LAN) or a wide area network (WAN)), a wired network (e.g., an Ethernet network), a wireless network (e.g., an 802.11 network or a Wi-Fi network), a cellular network (e.g., a Long Term Evolution (LTE) network), routers, hubs, switches, server computers, and / or combinations thereof.

[0021] The data store 106 may be a persistent storage capable of storing content items (such as media items) and data structures that tag, organize, and index the content items. The data store 106 may be hosted by one or more storage devices, such as main memory, disks, tapes or hard drives based on magnetic or optical storage, NAS, SAN, etc. In some embodiments, the data store 106 may be a network-attached file server, while in other embodiments, the data store 106 may be some other type of persistent storage, such as an object-oriented database, a relational database, etc., that may be hosted by the content sharing platform 120 or one or more different machines coupled to the content sharing platform 120. In some embodiments, the data store 106 may be coupled to the content sharing platform 120 via the network 104.

[0022] Each of the client devices 110A-110Z may include a computing device such as a personal computer (PC), a laptop, a mobile phone, a smartphone, a tablet computer, a netbook computer, a network-connected television, etc. In some embodiments, the client devices 110A-110Z may also be referred to as a "user device." In some embodiments, each of the client devices 110A-110Z may include a media player 112 (or media viewer) and a token module 114. In some embodiments, the media player 112 may be an application that allows a user to play, view, or upload content such as images, video items, web pages, documents, audio items, etc. For example, the media player 112 may be a web browser that can access, retrieve, or navigate content (e.g., web pages such as HyperText Markup Language (HTML) pages, digital media items, etc.) provided by a web server. The media player 112 may render, display, or present the content (e.g., web pages, media viewer) to the user. The media player 112 may also include an embedded media player (e.g., a Flash player or an HTML5 player) that is embedded in a web page (e.g., a web page that may provide information about products sold by an online merchant). In another example, the media player 112 may be a standalone application (e.g., a mobile application or a native application) that allows a user to play digital media items (e.g., digital video items, digital images, e-books, etc.). According to aspects of the present disclosure, the media player 112 may be a content sharing platform application for a user to record, edit, and / or upload content for sharing on a content sharing platform.Thus, the media player 112 may be provided to the client devices 110A-110Z by the content sharing platform 120. For example, the media player 112 may be an embedded media player embedded in a web page provided by the content sharing platform 120. In another example, the media player 112 may be an application downloaded from the content sharing platform 120.

[0023] In some embodiments, the content sharing platform 120 and / or the server machines 132A-132Z may be one or more computing devices (such as a rack mount server, a router computer, a server computer, a personal computer, a mainframe computer, a laptop computer, a tablet computer, a desktop computer, etc.), data stores (e.g., hard disks, memory, databases), networks, software components, or hardware components that may be used to provide access to media items to users or to serve media items to users. For example, the content sharing platform 120 may enable users to consume, upload, search, approve ("like"), disapprove ("nahhh"), or comment on media items. The content sharing platform 120 may also include websites (e.g., web pages) or application backend software that may be used to provide access to media items to users.

[0024] In some embodiments of the present disclosure, a "user" may be represented as a single individual. However, other embodiments of the present disclosure encompass a "user" being a set of user-controlled entities and / or automated sources. For example, a set of individual users federated as a community in a social network may be considered a "user." In another example, an automated consumer may be an automated ingestion pipeline, such as a topic channel of the content sharing platform 120.

[0025] The content sharing platform 120 may include multiple channels (e.g., channels A through Z, of which only channel A is shown in FIG. 1). A channel may be data content available from a common source or data content having a common topic, theme, or tenor. The data content may be digital content selected by a user, digital content made available by a user, digital content uploaded by a user, digital content selected by a content provider, digital content selected by a broadcaster, etc. For example, channel X may include videos Y and Z. A channel may be associated with an owner, which is a user who can perform actions on the channel. Different activities may be associated with a channel based on the owner's actions, such as the owner making digital content available on the channel, the owner selecting (e.g., liking) digital content related to another channel, the owner commenting on digital content related to another channel, etc. The activities related to the channel may be compiled into a feed of activities related to the channel. Users other than the channel owner may subscribe to one or more channels that interest them. The concept of "subscribing" may also be referred to as "liking," "following," or "becoming a friend."

[0026] When a user subscribes to a channel, the user may be presented with information from the channel's activity feed. If the user subscribes to multiple channels, the activity feeds for each channel to which the user subscribes may be combined into a syndicated activity feed. Information from the syndicated activity feeds may be presented to the user. A channel may have its own feed. For example, when navigating to a channel's home page on the content sharing platform, feed items generated by the channel may be shown on the channel's home page. A user may have a syndicated feed, which is a feed that includes at least a subset of content items from all of the channels to which the user subscribes. A syndicated feed may also include content items from channels to which the user does not subscribe. For example, the content sharing platform 120 or other social networks may insert recommended content items into the user's syndicated feed, or may insert content items related to the user's relevant connections into the syndicated feed.

[0027] Each channel may include one or more media items 122. Examples of media items 122 may include, but are not limited to, digital videos, digital movies, digital photos, digital music, audio content, melodies, website content, social media updates, electronic books (e-books), electronic magazines, digital newspapers, digital audio books, electronic journals, web blogs, real simple syndication (RSS) feeds, electronic comics, software applications, etc. In some embodiments, media items 122 are also referred to as content or content items.

[0028] For brevity and simplicity, but not limitation, video items, audio items, or game items are used throughout this specification as examples of media items 122. As used herein, "media," "media item," "online media item," "digital media," "digital media item," "content," and "content item" may include electronic files that can be executed or loaded using software, firmware, or hardware configured to present digital media items to entities. In one embodiment, the content sharing platform 120 may store the media items 122 using the data store 106. In another embodiment, the content sharing platform 120 may store the video items or fingerprints using the data store 106 as electronic files in one or more formats.

[0029] In some embodiments, the media item 122 is a video item. A video item is a set of consecutive video frames (e.g., image frames) that represent a moving scene. For example, a series of consecutive video frames may be continuously filmed or later reconstructed to generate an animation. A video item may be presented in a variety of formats, including, but not limited to, analog, digital, two-dimensional, and three-dimensional video. Furthermore, a video item may include a movie, a video clip, or any set of animated images displayed in sequence. In addition, a video item may be stored as a video file that includes a video component and an audio component. The video component may refer to video data in a video coding format or an image coding format (e.g., H.264 (MPEG-4 AVC), H.264 MPEG-4 Part 2, Graphic Interchange Format (GIF), WebP, etc.). The audio component may refer to audio data in an audio coding format (e.g., advanced audio coding (AAC), MP3, etc.). It may be noted that GIF may be stored as an image file (e.g., a .gif file) or animated as a series of images (e.g., GIF89a format). It may be noted that H.264 may be a video coding format that is, for example, a video compression standard based on block-oriented motion compensation for recording, compressing, or distributing video content.

[0030] In some embodiments, a media item may be streamed, such as a live stream, to one or more of client devices 110A-110Z. It is noted that "streamed" or "streaming" refers to the transmission or broadcast of content, such as a media item, in which a received portion of the media item may be played by a receiving device immediately upon receipt (within the limitations of the technology) or while other portions of the media content are being delivered, without the entire media item being received by the receiving device. A "stream" may refer to content, such as a media item, that is streamed or streaming. A live stream media item may refer to a live broadcast or transmission of a live event in which a media item is transmitted to a receiving device at least partially simultaneously as the event takes place, and the media item is not available in its entirety.

[0031] In some embodiments, the content sharing platform 120 may allow a user to create, share, view, or use a playlist that includes the media items (e.g., playlist A-Z that includes media item 122). A playlist refers to a collection of media items that are configured to be played one after the other in a particular order without any user interaction. In some embodiments, the content sharing platform 120 may maintain the playlist on behalf of the user. In some embodiments, the playlist feature of the content sharing platform 120 allows users to group their favorite media items together in a single location for playback. In an embodiment, the content sharing platform 120 may send the media items of the playlist to the client device 110 for playback or display. For example, the media viewer 112 may be used to play the media items of the playlist in the order in which the media items are listed in the playlist. In another example, a user may transition between media items of a playlist. In yet another example, a user may wait for the next media item of the playlist to be played or may select a particular media item in the playlist for playback.

[0032] In some embodiments, a user may access the content sharing platform 120 through a user account. A user may access (e.g., log in to) a user account by providing user account information (e.g., username and password) via an application (e.g., media viewer 112) on the client device 110. In some embodiments, a user account may be associated with a single user. In other embodiments, a user account may be a shared account (e.g., a family account shared by multiple users) (also referred to herein as a "shared user account"). A shared account may have multiple user profiles, each associated with a different user. Multiple users may log into a shared account using the same account information or different account information. In some embodiments, multiple users of a shared account may be distinguished based on different user profiles of the shared account.

[0033] In some embodiments, the authorization data service 124 (also referred to herein as a “core data service” or “authorization data source”) is a highly secured service that can access data associated with a user account on the content sharing platform 120 and use this data to determine whether the user account should be authorized to obtain the requested content. In some embodiments, the authorization data service 124 can authorize a user account (e.g., a client device associated with the user account) to access the requested content, authorize the delivery of the requested content to the client device, or both. Authorizing a user account to access the requested content may include authorizing what content is accessed and who is allowed to access the content. Authorizing the delivery of the content may include authorizing how the content is delivered.

[0034] In some embodiments, the authorization data service 124 can use the user account information to authorize the user account. In some embodiments, an authentication token associated with the client device 110 or media player 112 can be used to determine whether to authorize the user account and / or playback of the requested content.

[0035] In some embodiments, the authorization data service 124 is part of the content sharing platform 120. In other embodiments, the authorization data service 124 can be an external service, such as a highly secure authorization service offered by a third party.

[0036] As mentioned above, content distribution network (CDN) 130 may include one or more nodes represented as server machines 132A-132Z (collectively referred to herein as "server machines 132" or "servers 132"). In an embodiment, content distribution network 130 includes a geographically distributed network of servers that work together to provide rapid delivery of content. The network of servers is geographically distributed to provide high availability and high performance, possibly by distributing content or services based on proximity to client device 110. The closer the CDN server is to client device 110, the more quickly the content can be delivered to client device 110.

[0037] For example, different server machines 132A-132Z may be geographically distributed within a particular country or across different countries. User A using client device 110A located in the UK may request to obtain content hosted by content sharing platform 120. The request may be received by the authorization data service 124 of the content sharing platform 120, and a user account associated with user A may be authorized to obtain the requested content. After authorization, the content sharing platform 120 may send a resource locator, such as a uniform resource locator (URL), to the client device 110A. The resource locator may refer to a reference that specifies the location or address of a resource (e.g., content) on a computer network and a mechanism for retrieving the resource. The resource locator may instruct the client device 110A to obtain the content from a server machine 132 of the content distribution network 130 that is in the geographical vicinity of the client device 110A. For example, the resource locator may instruct the client device 110A to obtain the requested content from a particular server machine 132 of the content distribution network 130 that is also located in the UK. In another example, another user B using a client device 110B located on the west coast of the United States requests to obtain the same content as user A. The request may be received by the authorization data service 124 of the content sharing platform 120, and a user account associated with user B may be authorized to obtain the requested content. After authorization, the content sharing platform 120 may send a resource locator to the client device 110B. The resource locator may instruct the client device 110B to obtain the content from a server machine 132 of the content distribution network 130 that is in the geographical vicinity of the client device 110B.For example, the resource locator may instruct client device 110B to obtain the requested content from a server machine 132 in content distribution network 130 located on the west coast of the United States.

[0038] In some embodiments, the content distribution network 130 is part of the content sharing platform 120. In other embodiments, the content distribution network 130 is a third-party platform that provides CDN services to the content sharing platform 120. In other embodiments, a portion of the content distribution network 130 may be operated by the content sharing platform 120 and another portion of the content distribution network 130 may be operated by a third party. In an embodiment, the content distribution network 130 includes a data store, such as the data store 134. The data store 134 may be similar to the data store 106. The data store may include data files 136 relating to content, such as media content. The data store 106 may also include one or more cryptographic keys 137, such as one or more public keys or one or more private keys.

[0039] An authorization module 138 may be included in the server 132 of the CDN 130. The authorization module 138 may perform aspects of the disclosure described herein. For example, the authorization module 138 may determine a trust status of a client device. The trust status of a client device may be any type of indicator used by the CDN 130 to determine whether the requested content should be released to a user. As described in more detail herein, the trust status of a client device may be determined based on a partial trust metric or a trust package.

[0040] In general, functions described in one embodiment as being performed by the content sharing platform 120 and / or the content distribution network 130 may also be performed on the client devices 110A-110Z in other embodiments, where appropriate. In addition, functions attributed to a particular component may be performed by different or multiple components operating together. The content sharing platform 120 or the content distribution network 130 may also be accessed as a service offered to other systems or devices through appropriate application programming interfaces, and thus are not limited to use in a website.

[0041] Although embodiments of the present disclosure are discussed in terms of a content sharing platform and facilitating social network sharing of content items on the content sharing platform 120, the embodiments may be applied generally to any type of social network or content distribution platform that provides connections between users. Implementations of the present disclosure are not limited to content sharing platforms that provide users with subscriptions to channels.

[0042] In addition to the above, a user may be provided with controls that allow the user to make choices about both whether and when the systems, programs, or features described herein may enable the collection of user information (e.g., information about the user's social network, social actions, or activities, occupation, the user's preferences, or the user's current location) and whether the user will be sent content or communications from the server. Furthermore, certain data may be processed in one or more ways before being stored or used, such that personally identifiable information is removed. For example, the user's identity may be processed such that personally identifiable information cannot be determined about the user, or if location information is obtained, the user's geographic location may be generalized (such as to the city, zip code, or state level) and thus the user's specific location cannot be determined. Thus, the user may be able to control what information is collected about the user, how that information is used, and what information is provided to the user.

[0043] FIG. 2 is a diagram of operations for evaluating the trustworthiness of a client device, according to an embodiment of the present disclosure. The system 200 may include similar components as the system architecture 100 of FIG. 1. It may be noted that the components of FIG. 1 may be used to help explain FIG. 2. For purposes of illustration and not limitation, operations related to the system 200 are described as being performed by the authorization data service 124 of the content sharing platform 120, the server machine 132 of the content distribution network 130, or the client device 110, but may be performed by any component of the system 200 unless otherwise described. The operations described in connection with FIG. 2 are shown to be performed sequentially for purposes of illustration and not limitation. It may be noted that the operations may be performed in any order and that any of the operations may be performed simultaneously with one or more other operations. In some implementations, the same, different, fewer, or more operations may be performed in any order.

[0044] At operation 202, in response to user input regarding content, the client device 110 sends a request to obtain the content to the authorization data service 124 of the content sharing platform 120. For example, a user of the client device 110 may request to play a video item hosted by the content sharing platform 120. In some embodiments, the user may request the content from the content sharing platform 120 using an application, such as a browser or a native application. The content may be stored in one or more nodes or servers of a content delivery network (one or more CDN servers 132).

[0045] In some embodiments, a request from a client device 110 to the authorized data service 124 may include a format for the data to be received. For example, the request may include a format for the video item that is compatible with the media viewer 112 of the client device 110. In some embodiments, the request may include additional information (e.g., type, version, etc.) regarding the media viewer 112 in which the content, such as a video item, is to be played.

[0046] In some embodiments, the content request may include an identifier of the client device, user, or user account for which content is to be obtained. For example, the user request may specify a username and password associated with the user account requesting to obtain the content. In another example, the request may include a cookie that identifies the client device 110 or an application on the user device, and the cookie may be used to identify the particular user account. For example, the user may log into the content sharing platform 120 using user account information, and in response to authorization of the user account by the content sharing platform 120, the content sharing platform 120 may send a cookie to the user device 120. In yet another example, the content request may include other data associated with the user or user account, such as, for example, an Internet Protocol (IP) address associated with the client device.

[0047] In operation 204, the authorization data service 124 of the content sharing platform 120 may generate a partial trust metric associated with the content request. The partial trust metric may be any score, indicator, or other type of quantifiable measure used to indicate to the server 132 the authenticity of the client device, the media player used by the client device, or the user account. In particular, the partial trust metric may be used to indicate to the CDN server 132 the likelihood that the user, media player, and / or client device is trustworthy and should be authorized to access the requested content, as opposed to an unauthorized entity (e.g., an unauthorized media player, bot, server farm, etc.).

[0048] The authorized data service 124 can generate a partial trust metric based on factors (e.g., data, signals, etc.) associated with the client device 110 (or user account, media player 112, or any combination thereof). One or more factors may be accessible by the authorized data service 124 but not available to the server 132. In some embodiments, the factors may include the user's viewing history, whether the user has viewed the content before, whether the client device has successfully decrypted the content before, whether the user is logged in, whether the user has engaged in or is suspected of engaging in authorized activity, the user's IP address, encryption logs associated with the user, etc.

[0049] In some embodiments, the authorization data service 124 can generate the partial credit metric by using a heuristic approach. According to the heuristic approach, the authorization data service 124 uses heuristic rules that include assigning a weight and a numerical value between 0 and 1 to each factor used in generating the partial credit metric, and combining the weighted factors to generate the partial credit metric. In one example, for the factor of whether the client device has previously successfully decoded the content, a numerical value of 0 can be assigned if the user has not previously successfully decoded the content, or a numerical value of 1 can be assigned if the user has previously successfully decoded the content. In another example, for the factor of whether the client device has previously successfully decoded the content, a numerical value of 0 can be assigned if the user has not previously successfully decoded the content, a numerical value of 0.5 can be assigned if the user has previously successfully decoded the content less than five times, and a numerical value of 1 can be assigned if the user has previously successfully decoded the content at least five times. Different scales and arbitrary score values ​​can be used for each factor to determine the partial credit metric. Thus, in some embodiments, the partial credit metric may be the sum of each weighted factor, which may be normalized between 0 and 1.

[0050] In some embodiments, the authorization data service 124 can generate the partial trust metric by using machine learning techniques. In a machine learning approach, the authorization data service 124 can use a trained partial trust prediction model, which can be a machine learning model that corresponds to a model artifact created by a training engine using training data including training inputs and corresponding target outputs (i.e., the indicated answers for each training input). The training inputs can be based on historical data and include factors related to various client devices that have previously requested content from the authorization data service 124 and / or the CDN server 132. The target output can include an indication of whether the client device is authorized to obtain the requested content. In another implementation, the partial trust prediction model can be trained for a particular user based on training data related to the user and / or the user's media player and / or client device.

[0051] In operation 206, the authorization data service 124 of the content sharing platform 120 may authorize the content request. To authorize the request, the authorization data service 124 may determine that at least one of the client device 110 or the user (or user account) is permitted to obtain the content. In some embodiments, the authorization data service 124 may determine whether the partial trust metric satisfies (e.g., is greater than) an authorization threshold. The authorization threshold may be any value used to determine whether the client device 110 should be authorized to receive a content identifier from the content sharing platform 120. In response to the partial trust metric satisfying the authorization threshold, the authorization data service 124 may authorize the content request. For example, in response to the partial trust metric being greater than 0.2, the client device 110 may be considered authorized.

[0052] In some embodiments, determining whether to authorize a content request may not depend on an authorization threshold. In one example, the content request may specify account information for the user account requesting to obtain the content. For example, the account information may be encrypted in a cookie. In another example, the account information may be entered by a user and provided in the request. In some embodiments, the account information, such as a username and password, may be authenticated by the authorization data service 124 by comparing the account information (e.g., a received username and password) to a stored record of the account information. If the account information of the request matches the account information of the record, the authorization data service 124 may determine that the particular user account is authenticated, and the authorization data service 124 may authorize the content request and assign a predefined partial trust metric to the content request.

[0053] In some embodiments, in response to a failure to authorize the content request by the authorization data service 124 and / or to authenticate the client device 110, the content request may be rejected by the authorization data service 124. In some embodiments, if the authorization data service 124 does not authorize the request to obtain the content, the authorization data service 124 may send a message to the client device 110 indicating that authorization to obtain the requested content is not granted.

[0054] In some embodiments, in response to authorizing the request to obtain content by the authorization data service 124, the authorization data service 124 generates one or more resource locators (e.g., URLs) for authorizing the client device 110 to obtain the requested content from the CDN 130. In some embodiments, the resource locator may identify a CDN server 132 that will deliver the requested content to the client device 110. For example, the resource locator may include a hostname that identifies a particular server (e.g., server 132A, server 132B, etc.) that may be accessed to obtain the requested content. In some embodiments, the authorization data service 124 may append a partial trust metric to the resource locator and digitally sign the resulting response. The digital signature may be based on signed parameters (e.g., expiration parameters, bitrate parameters, playback event identifiers, etc.) that may be used to indicate to the CDN 130 what data should be provided and how the data should be provided. In some embodiments, the digital signature may be encrypted.

[0055] At operation 208, in response to authorizing the user account, the authorization data service 124 may send a response to the request for content (e.g., operation 202) to the client device 110. In some embodiments, the response may include one or more resource locators that identify the CDN server 132 that should deliver the content to the client device 110 and the partial trust metric. In some embodiments, the response may also include a digital signature. In some embodiments, the response may include one or more of a content identifier, a user account identifier, and / or a playback event identifier associated with the content request. In some embodiments, the response may be a HyperText Transfer Protocol (HTTP) response.

[0056] At operation 210, the client device 110 may request the content using the digitally signed resource locator and partial trust metrics. In some embodiments, the request may be sent to the CDN server 132. In some embodiments, the CDN server 132 may decrypt the digital signature using, for example, one or more cryptographic keys, public keys, private keys, etc.

[0057] At operation 212, the CDN server 132 can determine a trust status of the client device based on the partial trust metric. The trust status of the client device can be any type of indicator used by the CDN server 132 to determine whether the requested content should be released to the user. In some embodiments, the CDN server 132 can compare the partial trust metric to one or more thresholds to determine the trust status of the client device. Based on the comparison, the server 132 can reduce or cap the resolution of the requested content (e.g., 2160p, 1440p, 1080p, 720p, 480p, 540p, 360p, 240p, etc.), reduce or cap the frame rate (e.g., 24 frames per second (fps), 25 fps, 30 fps, 60 fps, 120 fps, etc.), throttle the data sent to the client device 110, etc. In one example, in response to a determination by server 132 that the partial trust metric is greater than a first threshold (e.g., 0.5), server 132 may determine that the client device is trusted and provide the content in the requested format (e.g., standard definition, high definition, etc.). In response to a determination by server 132 that the partial trust metric is less than the first threshold (e.g., 0.5) but greater than a second threshold (e.g., 0.2), server 132 may determine that the client device is suspect and release the content only in standard resolution and not high resolution. In response to a determination by server 132 that the partial trust metric is less than the second threshold (e.g., 0.2), server 132 may determine that the client device should not be trusted and deny the content request.

[0058] In some embodiments, based on the determined trust status of the client device, the CDN server 132 may request the client device 110 to perform one or more additional functions before the CDN server 132 releases the requested content. The additional functions may include requesting ReCaptcha verification, requesting the user of the client device 110 to sign in, etc. For example, in response to a determination by the CDN server 132 that the partial trust metric is less than a first threshold (e.g., 0.5) but greater than a second threshold (e.g., 0.2), the CDN server 132 may determine that the client device is suspicious and request the user to sign in to their user account.

[0059] In some embodiments, the CDN server 132 may combine the partial trust metric with one or more additional CDN-related factors to determine the trust status of the client device. The additional factors may be identified by the CDN server 132 based on information available to the CDN server 132. In particular, the additional factors may include any data related to the client device 110, the user (user account), and / or the content request to the CDN server 132 (at operation 210) that is determined by the CDN server 132 based on the content request to the CDN server 132 or other information locally available to the CDN server 132. For example, the additional factors (factors determined by the CDN) may include the IP address used to request the content, one or more cookies provided to the CDN 130 with the content request, a client agent reported by the client device (e.g., a browser, a bot, a download manager, an app accessing the Internet, etc.), the type of content requested (e.g., popular, private, advertising, paid video, etc.), the bitrate of the content requested, the amount of content requested in the request, etc. In some embodiments, the CDN server 132 may determine the device's trust status by increasing or decreasing the partial trust metric based on one or more of the factors determined by the CDN and then comparing the new trust metric to one or more thresholds. In an illustrative example, a suspicious IP address may result in the partial trust metric being decreased by a value of 0.1. Thus, in response to the allocation of the partial trust metric of 0.25 to the client device 110 and the determination by the CDN server 132 that the content request in operation 210 was received from a suspicious IP address, the CDN server 132 may decrease the partial trust metric by a value of 0.1 and compare the new trust metric of 0.15 to one or more thresholds to determine the client device's trust status for the client device 110.In some embodiments, the CDN server 132 can use heuristic techniques to combine the partial trust metrics with one or more CDN-determined factors, where each CDN-determined factor and / or partial trust metric can be assigned a weight, and the weighted factor is combined with the weighted or unweighted partial trust metric to determine the trust status of the client device. In other embodiments, the CDN server 132 can use machine learning techniques to combine the partial trust metrics with one or more CDN-determined factors.

[0060] Based on the trust status of the client device, the CDN server 132 can respond to the content request with content associated with the resource locator, in operation 214. For example, the response can include the requested video item when the trust status of the client device indicates that the client device is trusted, or can include the requested video item in a lower format than requested when the client device is suspect.

[0061] FIG. 3 is a diagram of operations for evaluating the trustworthiness of a client device, according to an embodiment of the present disclosure. The system 300 may include components similar to the system architecture 100 of FIG. 1. It may be noted that the components of FIG. 1 may be used to help explain FIG. 3. For purposes of illustration and not limitation, operations related to the system 300 are described as being performed by the authorization data service 124 of the content sharing platform 120, the server machine 132 of the content distribution network 130, or the client device 110, and may be performed by any component of the system 300 unless otherwise described. The operations described in connection with FIG. 3 are shown to be performed sequentially for purposes of illustration and not limitation. It may be noted that the operations may be performed in any order and that any of the operations may be performed simultaneously with one or more other operations. In some implementations, the same, different, fewer, or more operations may be performed in any order.

[0062] At operation 302, in response to user input regarding content, the client device 110 sends a request to obtain the content to the authorization data service 124 of the content sharing platform 120. For example, a user of the client device 110 may request to play a video item hosted by the content sharing platform 120. In some embodiments, the user may request the content from the content sharing platform 120 using an application, such as a browser or a native application. The content may be stored in one or more nodes or servers of a content delivery network (one or more CDN servers 132).

[0063] In some embodiments, a request from a client device 110 to the authorized data service 124 may include a format for the data to be received. For example, the request may include a format for the video item that is compatible with the media viewer 112 of the client device 110. In some embodiments, the request may include additional information (e.g., type, version, etc.) regarding the media viewer 112 in which the content, such as a video item, is to be played.

[0064] In some embodiments, the content request may include an identifier of the client device or user account for which content is to be obtained. For example, the user's request may specify a username and password associated with the user account requesting to obtain the content. In another example, the request may include a cookie that identifies the client device 110 or an application on the user device, and the cookie may be used to identify the particular user account. For example, the user may log into the content sharing platform 120 using user account information, and in response to authorization of the user account by the content sharing platform 120, the content sharing platform 120 may send a cookie to the user device 120. In yet another example, the content request may include other data associated with the user or user account, such as, for example, an Internet Protocol (IP) address associated with the client device.

[0065] In operation 304, the authorization data service 124 of the content sharing platform 120 may generate a credit package associated with the content request. In some embodiments, the credit package may include data such as whether the user is logged in, the type of browser used by the user to request the content, the user's geographic location, the user's IP address, etc. In some embodiments, the credit package may include instructions to the CDN server 132. The instructions may instruct the CDN server 132 to perform one or more functions in response to the satisfaction of the conditions (or criteria). The functions may include rejecting the content request, reducing or capping the resolution of the requested content, requesting ReCaptcha verification, requesting the user of the client device 110 to sign in, etc. The conditions may be based on one or more of: a content request to the CDN server 132 (in operation 310 below) originating from a specified region or not originating from a specified region, a content request to the CDN server 132 using or not using an IP address or an IP address in a specified subnet, a content request to the CDN server 132 using or not using a specified browser, etc. For example, the instructions may indicate to the CDN server 132 to reduce the resolution of the requested content if the content request to the CDN server 132 does not originate from a particular type of browser.

[0066] At operation 306, the authorization data service 124 of the content sharing platform 120 may authorize the content request. To authorize the request, the authorization data service 124 may determine that at least one of the client device 110 or the user (or user account) is authorized to obtain the content. In one example, the content request may identify account information for the user account requesting to obtain the content. For example, the account information may be encrypted in a cookie. In another example, the account information may be entered by the user and provided in the request. In some embodiments, the account information, such as a username and password, may be authenticated by the authorization data service 124 by comparing the account information (e.g., a received username and password) to a stored record of the account information. If the account information of the request matches the account information of the record, the authorization data service 124 may determine that the particular user account is authenticated, and the authorization data service 124 may authorize the content request.

[0067] In some embodiments, in response to a failure to authorize the content request by the authorization data service 124 and / or to authenticate the client device 110, the content request may be rejected by the authorization data service 124. In some embodiments, if the authorization data service 124 does not authorize the request to obtain the content, the authorization data service 124 may send a message to the client device 110 indicating that authorization to obtain the requested content is not granted.

[0068] In some embodiments, in response to authorizing the request to obtain content by the authorization data service 124, the authorization data service 124 generates one or more resource locators (e.g., URLs) for authorizing the client device 110 to obtain the requested content from the CDN network 130. In some embodiments, the resource locator may identify a CDN server that will deliver the requested content to the client device 110. For example, the resource locator may include a hostname that identifies a particular server (e.g., server 132A, server 132B, etc.) that may be accessed to obtain the requested content. In some embodiments, the authorization data service 124 may append a trust package to the resource locator and digitally sign the resulting response. The digital signature may be based on signed parameters (e.g., expiration parameters, bitrate parameters, playback event identifier parameters, etc.) that may be used to indicate to the CDN server 132 what data should be provided and how the data should be provided. In some embodiments, the digital signature may be encrypted.

[0069] At operation 308, in response to authorizing the user account, the authorization data service 124 may send a response to the request for content (e.g., operation 302) to the client device 110. In some embodiments, the response may include one or more resource locators that identify a server 132 of the CDN 130 that should deliver the content to the client device 110. In some embodiments, the response also includes a trust package and a digital signature. In some embodiments, the response may include one or more of a content identifier, a user account identifier, and / or a playback event identifier associated with the content request. In some embodiments, the response may be a HyperText Transfer Protocol (HTTP) response.

[0070] In some embodiments, the authorization data service 124 can send the credit package to the identified CDN server 132 instead of including it in the response to the client device 110. In some embodiments, the credit package is digitally signed using one or more signed parameters that provide, for example, an expiration date for the credit package and / or a playback event identifier created for the content request.

[0071] At operation 310, the client device 110 may request the content using the digitally signed resource locator and trust package. In some embodiments, the request may be sent to the CDN server 132. In some embodiments, the CDN server 132 may decrypt the digital signature using, for example, one or more cryptographic keys, public keys, private keys, etc.

[0072] At operation 312, the CDN server 132 can determine a trust status of the client device based on the trust package. The trust status of the client device can be any type of indicator used by the CDN server 132 to determine whether to release the requested content to the user. In some embodiments, the CDN server 132 can compare data from the trust package received at operation 310 (and / or received directly from the authorization data service 124) with data obtained from the content request of operation 310 (e.g., factors determined by the CDN). Based on the comparison (e.g., whether the server 132 detects a discrepancy in the comparison), the server 132 can determine a trust status of the client device. In some embodiments, in response to a determination that there is no discrepancy in the data obtained from the credit package and the data obtained from the content request of operation 310, the CDN server 132 can allocate a trusted status to the client device and release the requested content. In some embodiments, in response to a determination that there is a mismatch between the data obtained from the trust package and the data obtained from the content request of operation 310, the CDN server 132 may assign the client device 110 an untrusted or suspect status and reject the content request or downgrade the playback quality of the request, respectively. For example, in response to a determination by the CDN server 132 that the client device requested content from the authorized data service 124 using a first type of browser and content from the server 132 using a second type of browser, the CDN server 132 may reduce the requested content resolution of 1080p to 480p.

[0073] In some embodiments, in response to a determination that there is a mismatch between the data obtained from the credit package and the data obtained from the content request of operation 310, the CDN server 132 may request the client device 110 to perform one or more additional functions before the server 132 releases the requested content. The additional functions may include requesting ReCaptcha verification, requesting a user of the client device 110 to sign in, etc. For example, in response to a determination by the CDN server 132 that the client device has requested content from the authorization data service 124 using a first IP address and has requested content from the CDN server 132 using a different IP address, the CDN server 132 may determine that the client device is suspicious and request the user to sign in to their user account.

[0074] In operation 314, based on the trust status of the client device, the CDN server 132 can respond to the content request with content associated with the resource locator. For example, the response can include the requested video item when the trust status of the client device indicates that the client device is trusted, or can include the requested video item in a lower format than requested when the client device is suspect.

[0075] In some embodiments, the CDN server 132 can use any combination of the partial trust metrics, the trust package, and / or factors determined by the CDN to determine the trust status of the client device. For example, the authorization data service 124 can generate one or more resource locators for authorizing the client device 110 to obtain the requested content from the CDN 130. The authorization data service 124 can further append the partial trust metrics and the trust package to the resource locator and send the resulting response to the client device 110, and in addition, the authorization data service 124 can send the trust package to the CDN server 132. The CDN server 132 can then use the partial trust metrics and the trust package to determine the trust status of the client device.

[0076] FIG. 4 illustrates a flow diagram of a method 400 for performing partial trust metric generation according to an embodiment of the present disclosure. The method is performed by processing logic that may include hardware (circuitry, dedicated logic, etc.), software (e.g., instructions executed on a processing device), or a combination thereof. In some embodiments, some or all of the operations of the method 400 may be performed by one or more components of the system 100 of FIG. 1. In other embodiments, one or more operations of the method 400 may be performed by an authorization module or an authorization data service 124 of the content distribution network 130 described in connection with FIGS. 1-2. It may be noted that the components described in connection with FIGS. 1-3 may be used to illustrate aspects of FIG. 4.

[0077] At block 402, processing logic performing the method 400 receives a request for content from a client device.

[0078] At block 404, the processing logic generates a partial trust metric associated with the client device based on data available to the content sharing platform. In some embodiments, the partial trust metric will be used by the CDN server to make a decision regarding the client device's access to the desired content and may include a score to indicate to the CDN server the likelihood that the client device is trustworthy and should be authorized to access the requested content. In some embodiments, the partial trust metric is generated based on one or more characteristics, such as a viewing history of a user associated with the client device, whether the user has previously viewed the requested content, whether the client device has previously successfully decrypted other content, whether the user is logged in, whether the user has engaged in or is suspected of engaging in unauthorized activity, an Internet Protocol (IP) address of the client device, or an encryption log associated with the user. The characteristics used to generate the partial trust metric may not be available to the CDN server. In some embodiments, the partial trust metric is generated using heuristic rules. In some embodiments, the partial trust metric is generated using a trained machine learning model. In some embodiments, the partial trust metric is encrypted for decryption by the CDN server.

[0079] At block 406, the processing logic generates a response to the content request. The response may include one or more resource locators provided by the content sharing platform to authorize the client device to obtain the requested content. The response may also include the partial trust metric and may be digitally signed. In some embodiments, the processing logic may deny the content request based on the partial trust metric.

[0080] At block 408, the processing logic sends a response to the client device. The partial trust metric may be provided by the client device to the CDN server when requesting the desired content, but none of the characteristics used to generate the metric may be provided, and the partial trust metric may be used by the CDN server to determine whether to provide the requested content to the client device or downgrade the quality of the requested content, but none of the characteristics used to generate the metric may be used. In some embodiments, method 400 may be used to generate a trust package as discussed in FIG. 3.

[0081] FIG. 5 illustrates a flow diagram of a method 500 for determining a trust status of a client device according to an embodiment of the present disclosure. The method is performed by processing logic, which may include hardware (circuitry, dedicated logic, etc.), software (e.g., instructions executed on a processing device), or a combination thereof. In some embodiments, some or all of the operations of the method 500 may be performed by one or more components of the system 100 of FIG. 1. In other embodiments, one or more operations of the method 500 may be performed by the authorization module of the CDN server 132 or the authorization data server 124 described in connection with FIGS. 1-3. It may be noted that the components described in connection with FIGS. 1-3 may be used to illustrate aspects of FIG. 5.

[0082] At block 502, processing logic implementing method 500 receives a request for content from a client device. The request includes a resource locator provided by an authorization data service to authorize the client device to obtain the requested content. The resource locator may be appended with a partial trust metric.

[0083] At block 504, the processing logic determines a trust status of the client device based on the partial trust metric. The trust status of the client device can be any type of indicator used by the processing logic to determine whether the requested content should be released to the user. In some embodiments, the processing logic can compare the partial trust metric to one or more thresholds to determine the trust status of the client device. Based on the comparison, the processing logic can reduce or cap the resolution of the requested content, reduce or cap the frame rate, throttle the data sent to the client device, etc.

[0084] At block 506, in response to the client device's trust status indicating that the client device is authorized to receive the requested content, the processing logic provides playback of the content to the client device. For example, the processing logic may provide video data associated with the resource locator. In some embodiments, method 500 may be used to determine the trust status of the client device based on a trust package as discussed in FIG.

[0085] 6 is a block diagram illustrating an exemplary computer system 600 according to an embodiment of the present disclosure. The computer system 600 executes one or more sets of instructions that cause the machine to perform any one or more of the methods discussed herein. A set of instructions, instructions, etc., may refer to instructions that, when executed by the computer system 600, cause the computer system 600 to perform one or more operations of the initial playback module 142 (not shown), the authorization module 138, and / or the authorization data service 124 (not shown). The machine may operate as a server or a client device in a client-server network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine may be a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile phone, a web appliance, a server, a network router, a switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by the machine. Additionally, although only a single machine is shown, the term "machine" is also intended to include any collection of machines that individually or in cooperation execute a set of instructions to perform any one or more of the methodologies discussed herein.

[0086] The computer system 600 includes a processing device 602, a main memory 604 (e.g., read only memory (ROM), flash memory, dynamic random access memory (DRAM), such as synchronous DRAM (SDRAM) or Rambus DRAM (RDRAM), etc.), a static memory 606 (e.g., flash memory, static random access memory (SRAM), etc.), and a data storage device 616, which communicate with each other via a bus 608.

[0087] The processing device 602 represents one or more general-purpose processing devices, such as a microprocessor, a central processing unit, etc. More specifically, the processing device 602 may be a complex instruction set computing (CISC) microprocessor, a reduced instruction set computing (RISC) microprocessor, a very long instruction word (VLIW) microprocessor, or a processing device implementing other instruction sets or combinations of instruction sets. The processing device 602 may also be one or more special-purpose processing devices, such as an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), a network processor, etc. The processing device 602 is configured to execute instructions of the system architecture 100 and the authorization module 151 to perform the operations discussed herein.

[0088] The computer system 600 may further include a network interface device 622 that provides communication with other machines over a network 618, such as a local area network (LAN), an intranet, an extranet, or the Internet. The computer system 600 may also include a display device 610 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)), an alphanumeric input device 612 (e.g., a keyboard), a cursor control device 614 (e.g., a mouse), and a signal generation device 620 (e.g., a speaker).

[0089] The data storage device 616 may include a non-transitory computer-readable storage medium 624 on which are stored a set of instructions for the system architecture 100, the authorized data service 124, or the authorization module 138 (not shown) embodying any one or more of the methods or functions described herein. The set of instructions for the system architecture 100, the authorized data service 124, or the authorization module 138 may reside, completely or at least partially, within the main memory 604 and / or within the processing device 602 during execution of those instructions by the computer system 600, and the main memory 604 and the processing device 602 constitute computer-readable storage media. The set of instructions may further be transmitted or received over the network 618 via the network interface device 622.

[0090] Although the example of computer readable storage medium 624 is shown as a single medium, the term "computer readable storage medium" may include a single medium or multiple media that store a set of instructions (e.g., centralized or distributed databases and / or associated caches and servers). The term "computer readable storage medium" may include any medium that can store, encode, or carry a set of instructions for execution by a machine and cause the machine to perform any one or more of the methods of this disclosure. The term "computer readable storage medium" may include, but is not limited to, solid state memory, optical media, and magnetic media.

[0091] In the above description, numerous details have been set forth. However, it will be apparent to one of ordinary skill in the art having the benefit of this disclosure that the present disclosure may be practiced without these specific details. In some instances, well-known structures and devices have been shown in block diagram form, rather than in detail, in order to avoid obscuring the present disclosure.

[0092] Some portions of the detailed description have been presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. The operations are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals that can be stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, primarily for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.

[0093] It may be noted, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless expressly stated otherwise, discussions utilizing terms such as "generate," "provide," "adjust," "receive," "cancel," and the like throughout the description are understood to refer to the acts and processes of a computer system or similar electronic computing device that manipulate and convert data represented as physical (e.g., electronic) quantities in the computer system's memory or registers into other data that are similarly represented as physical quantities in the computer system's memory or registers or other such information storage, transmission, or display device.

[0094] The present disclosure also relates to an apparatus for carrying out the operations herein. This apparatus may be specially constructed for the required purposes or may include a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer-readable storage medium, such as, but not limited to, any type of disk including a floppy disk, an optical disk, a compact disk read-only memory (CD-ROM), a magneto-optical disk, a read-only memory (ROM), a random access memory (RAM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic or optical card, or any type of medium suitable for storing electronic instructions.

[0095] The word "example" or "exemplary" is used herein to mean serving as an example, instance, or example. Any aspect or design described herein as "example" or "exemplary" should not necessarily be construed as preferred or advantageous over other aspects or designs. Rather, use of the word "example" or "exemplary" is intended to present a concept in a concrete manner. As used in this application, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or." That is, unless otherwise specified or clear from the context, "X includes A or B" is intended to mean any of the natural inclusive permutations. That is, if X includes A, X includes B, or X includes both A and B, then "X includes A or B" is satisfied under any of the above cases. In addition, the articles "a" and "an" used in this application and the appended claims may generally be considered to mean "one or more" unless otherwise specified or the context makes clear that a singular form is intended. Furthermore, the use of the terms "an embodiment", "one embodiment", "an implementation", or "one implementation" throughout is not intended to refer to the same embodiment or implementation unless so described. The terms "first", "second", "third", "fourth", etc. used herein are intended as labels to distinguish different elements and may not necessarily have an ordering meaning according to the numerical designation of those terms.

[0096] For ease of explanation, the methods herein are shown and described as a series of acts or operations. However, acts according to the present disclosure may occur in various orders and / or simultaneously, as well as with other acts not shown and described herein. Moreover, not all acts shown may be required to perform a method according to the disclosed subject matter. In addition, those skilled in the art will understand and appreciate that a method may alternatively be represented as a series of interrelated states or events in a state diagram. Moreover, it should be understood that the methods disclosed herein may be stored in an article of manufacture to facilitate carrying and transferring such methods to a computing device. The term article of manufacture as used herein is intended to encompass a computer program accessible from any computer-readable device or storage medium.

[0097] In further embodiments, one or more processing devices are disclosed for performing the operations of the above-described embodiments. Additionally, in embodiments of the present disclosure, a non-transitory computer-readable storage medium stores instructions for performing the operations of the described embodiments. In other embodiments, systems for performing the operations of the described embodiments are also disclosed.

[0098] It is to be understood that the foregoing description is intended to be illustrative, and not limiting. Other embodiments will be apparent to those skilled in the art upon reading and understanding the above description. Thus, the scope of the present disclosure may be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled. [Explanation of symbols]

[0099] 100 System Architecture 104 Network 106 Datastore 110 Client Devices 110A~110Z Client Devices 112 Media player, media viewer 114 Token Module 120 Content Sharing Platform 122 Media Items 124 Authorized Data Services 130 Content Distribution Network (CDN) 132 servers, CDN servers 132A~132Z Server machines, servers 136 Data Files 137 Encryption Key 138 Authorization Module 142 Initial Regeneration Module 151 Authorization Module 200 Systems 300 Systems 400 ways 500 ways 600 Computer Systems 602 Processing device 604 Main Memory 606 Static Memory 608 Bus 610 Display Devices 612 Alphanumeric Input Device 614 Cursor Control Device 616 Data Storage Devices 618 Network 620 Signal Generating Device 622 Network Interface Device 624 Non-transitory computer-readable storage media

Claims

1. receiving, by a processing device of the content sharing platform, a request for the desired content from a client device; the desired content is stored in a content delivery network CDN; the content sharing platform offering the desired content to a plurality of client devices; the CDN providing the desired content to the plurality of client devices; generating, by an authorization service of the content sharing platform, a partial trust metric associated with the client device based on data available to the content sharing platform; the partial trust metric is used by a CDN server to make a decision regarding access to the desired content by the client device; generating a response for the content sharing platform to the request for the desired content, the response including one or more resource locators for accessing the desired content within the CDN and the partial trust metric; sending the response to the client device to enable the client device to request the desired content from the CDN server using the one or more resource locators and the partial trust metric; The method includes:

2. the data available to the content sharing platform, a user's viewing history associated with said client device; whether the user has previously viewed the desired content; whether the client device has previously successfully decrypted other content; Whether the user is logged in; Whether such user has engaged in or is suspected of engaging in unauthorized activity; the Internet Protocol (IP) address of the client device; or Encryption logs associated with the client device The method of claim 1 , comprising one or more of a number of characteristics including:

3. The method of claim 1 , wherein the partial trust metric is generated using heuristic rules.

4. The method of claim 1 , wherein the partial trust metric is generated using a machine learning model.

5. the response including the one or more resource locators and the partial trust metric, an expiration date for said one or more resource locators and / or said partial credit metrics; a bit rate for delivering said desired content; or an identifier for a playback event that was created for the request for the desired content; 2. The method of claim 1, wherein the authentication information is digitally signed using one or more signed parameters that provide at least one of:

6. The method of claim 1 , further comprising the step of denying a request for the desired content based on the partial trust metric.

7. 2. The method of claim 1, wherein the partial trust metric is used by the CDN server to determine whether to release the desired content to the client device or whether to downgrade the quality of the desired content.

8. the data available to the content sharing platform used to generate the partial trust metric is not available to the CDN server; 2. The method of claim 1, wherein the partial trust metric is provided to the CDN server when the client device requests the desired content, but none of the plurality of characteristics is provided to the CDN server.

9. the partial trust metric is combined by the CDN server with one or more additional factors to determine a trust status of the client device that is used by the CDN to determine whether to release the desired content to the client device or whether to downgrade the quality of the desired content; The method of claim 1 , wherein the one or more additional factors are identified by the CDN server based on data available to the CDN server.

10. The additional factor is the IP address used by the client device to request the desired content from the CDN server; one or more cookies provided to the CDN server along with the request for the desired content; a client agent reported by the client device to the CDN server; the type of content requested; the bit rate of the requested content; or The amount of content requested in the request for the desired content.

10. The method of claim 9, comprising at least one of:

11. Memory, a processing device of a content sharing platform coupled to the memory; wherein the processing device: receiving, by the processing device of the content sharing platform, a request for desired content from a client device; the desired content is stored in a content delivery network CDN; the content sharing platform offering the desired content to a plurality of client devices; the CDN providing or receiving the desired content to the plurality of client devices; generating a credit package associated with the client device based on data available to the content sharing platform, generating a credit package to be used by a CDN server to make decisions regarding access to the desired content by the client device; generating a response for the content sharing platform to the request for the desired content, generating the response including one or more resource locators for accessing the desired content within the CDN and the credit package; sending the response to the client device to enable the client device to request the desired content from the CDN server using the one or more resource locators and the credit package; A system that performs the above.

12. the data available to the content sharing platform, a user's viewing history associated with said client device; whether the user has previously viewed the desired content; whether the client device has previously successfully decrypted other content; Whether the user is logged in; Whether such user has engaged in or is suspected of engaging in unauthorized activity; the Internet Protocol (IP) address of the client device; or Encryption logs associated with the client device The system of claim 11, comprising one or more of a number of characteristics including:

13. The credit package: whether a user of the client device is logged in; the type of browser used by the user to request the desired content; the geographic location of the client device; or The IP address of the client device The system of claim 11 , further comprising a plurality of characteristics indicative of

14. 12. The system of claim 11, wherein the credit package includes instructions to instruct the CDN server to perform one or more functions in response to satisfaction of a condition.

15. the response including the one or more resource locators and the credit package; an expiration date for said one or more resource locators and / or said credit package; a bit rate for delivering said desired content; or an identifier for a playback event that was created for the request for the desired content; 12. The system of claim 11, wherein the authentication information is digitally signed using one or more signed parameters that provide at least one of:

16. the processing device comprising: The system of claim 11, further operable to deny a request for the desired content based on the credit package.

17. 12. The system of claim 11, wherein the credit package is to be used by the CDN server to determine whether to release the desired content to the client device or whether to downgrade the quality of the desired content.

18. 12. The system of claim 11, wherein a plurality of characteristics of the credit package are compared by the CDN server with data obtained from the client device's content request to the CDN.

19. The processing device further comprises: generating a partial trust metric associated with the client device based on data available to the content sharing platform, generating a partial trust metric that will be used together with the trust package by the CDN server to make a decision regarding access to the desired content by the client device; The system according to claim 11, 20. In response to execution by a processing device for a content sharing platform, the processing device:

13. An operation of receiving a request for desired content from a client device, comprising: the desired content is stored in a content delivery network CDN; the content sharing platform offering the desired content to a plurality of client devices; the CDN providing the desired content to the plurality of client devices; generating a partial trust metric associated with the client device based on data available to the content sharing platform, the partial trust metric is used by a CDN server to make a decision regarding access to the desired content by the client device; generating a response of the content sharing platform to the request for the desired content, the response comprising: the response includes one or more resource locators for accessing the desired content within the CDN and the partial trust metric; and sending the response to the client device to enable the client device to request the desired content from the CDN server using the one or more resource locators and the partial trust metric; A non-transitory computer-readable recording medium having stored thereon instructions for performing operations including:

Citation Information

Patent Citations

  • Information providing device, ticket providing device, reproducing device and information selling method and its program

    JP2003052029A

  • Method and apparatus for ephemeral trust devices

    JP2013541087A

  • Secure content access system

    US20180114030A1

  • Automatic token based secure content streaming method and apparatus

    US20180205742A1

  • Separating the authorization of content access and content delivery using multiple cryptographic digital signatures

    WO2020197545A1