JP6790169B2 - Systems, methods and computer programs for media session concurrency management with repeated license renewals - Google Patents

Description

Cross-reference to related applications This application is filed with US Patent Application No. 15 / 213,624 filed on July 19, 2016 and US Provisional Patent Application No. 62 filed on July 30, 2015. Claiming the benefits of / 199,211 and US Provisional Patent Application No. 62 / 194,804 filed on July 20, 2015, each of which is referred to in its entirety herein. It will be used.

Technical Area The subject matter disclosed relates to systems, methods and media for media session concurrency management with repeated license renewals. More specifically, the disclosed subject matter uses repetitive license renewals for concurrency detection and concurrency restriction enforcement for video delivery services and handles such repetitive license renewals. Regarding managing server resources for.

Background Other forms of movie, music, and media content are provided to computing devices via the Internet from various content providers. For many reasons, some of this content is protected and requires a license to at least identify the various rights in which the associated media content is used, played, copied, and / or distributed. Will be done. Other protections may include various levels or types of encryption protection that may require a key to decrypt media content.

In addition, a limit may be imposed on the number of simultaneous streaming connections that a particular user is allowed to establish. That is, each can be authenticated with the same user account and the number of devices on which media content can be streamed and viewed at the same time can be limited (eg, a total of 2 connections per user account, 3 per user account for 4 devices). Two connections etc.). To enforce such a limit, when a user requests a new streaming connection, the number of currently established streaming connections associated with that user is detected and that number is the maximum number of concurrent streaming connections allowed. If so, the request for a new streaming connection may be rejected. Managing the implementation of policies that include this limitation is a difficult task.

Addresses the issue of implementing concurrency limits by requiring the client device associated with a particular user to send a message to the server when a particular user stops watching a piece of media content. Various approaches have been tried. However, such an approach can suppress client implementation and device architecture and may require persistent storage on the client device. That is, in these approaches, simultaneous restriction enforcement will depend on each individual client device. Moreover, these approaches are generally considered unreliable. This is because the client device can stop playback in a "chaotic" manner due to a device failure (crash), power outage, network failure, or the like.

Therefore, it is desirable to provide new systems, methods and media for media session concurrency management with repeated license renewals.

Overview Following some implementations of the disclosed subject matter, a mechanism for managing media session concurrency with repeated license renewals is provided.

According to some implementations, a system for simultaneity detection and implementation is provided, which includes at least one server. The at least one server is configured to receive requests for media content licenses related to media content items to be presented on the media playback device, and requests for media content licenses are user accounts. Associated with, at least one server, in response to a request for a media content license, contains one or more keys associated with the media content item and a policy that includes a limited license period and renewal request interval. Sending the license to the media playback device, receiving a request for license renewal related to the media content item presented on the media playback device at some time within the renewal request interval, and to the user account. Based on media session concurrency across multiple associated media playback devices, it is configured to decide whether to issue a license renewal for a media content item, and the decision is for a given period of time for the user account. Includes querying for license renewal records issued to, and at least one server also performs license renewals to the media playback device based on the license renewal record associated with the user account. It is configured as follows.

In some implementations, at least one server is further configured to modify at least one of the limited license period and renewal request interval. In some implementations, the fix considers the license renewal record issued for the user account over a given period of time, and the license renewal record is the license renewal by multiple media playback devices associated with the user account. It is done in response to determining that it indicates suppression of demand. In some implementations, the fix is performed in response to detecting a server outage.

In some implementations, the limited license period associated with a license renewal has a zero period or in response to determining that one or more keys in the license should be revoked. , Has some other means of implementing discontinuation of media rights.

In some implementations, the media playback device also has a limited license period license for the media content item, while simultaneously showing the previously issued license in the record for discontinuity. Is configured to automatically send to.

In some implementations, at least one server further reviews the license renewal records issued for the user account over a given period of time and determines the implementation mode to apply to the user account from multiple execution modes. At least one of the limited license period and renewal request interval is adjusted to do so and to apply the determined implementation mode when issuing the license renewal.

In some implementations, at least one server is further configured to send a list of multiple license servers to handle requests for license renewals to media playback applications running on the media playback device. , When the media playback application sends a request for license renewal to the first license server of the plurality of license servers and detects that the first license server is unavailable and the license is terminated. Prior to, the request is sent to the second license server of the plurality of license servers until a license update for the media content license is received.

In some implementations, at least one server determines whether to issue license renewals by counting the number of license renewals associated with a user account within a given time period, and based on the count. It is further configured to send license updates to the media playback device.

In some implementations, at least one server should further decide whether to enter emergency renewal mode, which automatically issues license renewals, in response to the inability to access license renewal records. It is composed. In some implementations, emergency renewal mode is entered based on the resource information associated with one or more servers corresponding to the initial license request or renewal request. In some implementations, the license renewal includes a second license period that is greater than the first license period. In some implementations, the emergency update mode is entered in response to the number of failures communicating with the server being greater than the threshold, and the hardware processor is also an alternative to respond to the initial license or renewal request. It is configured to send license updates to a typical server. In some implementations, should the system enter update-only mode to issue license renewals in response to detecting that a server configured to accommodate the initial license request is unavailable? Further includes deciding whether.

According to some implementations, a system for simultaneity detection and implementation is provided, the system including at least one server including a hardware processor. The hardware processor receives a request from the media playback device associated with the user account for the initial license corresponding to the media content item, and a detection mode that sets the initial license period and initial license renewal interval for the initial license. Is configured to impose on the user account and send the initial license to the media playback device, the initial license has an initial license period and an initial license renewal interval, and the hardware processor also Tighter than determining whether a user account is associated with suspicious behavior indicating renewal request suppression and setting a renewal license period that is less than the initial license period or a license renewal interval that is less than the initial license renewal interval. It is configured to impose an execution mode on the user account and send the license renewal to the media playback device, and the license renewal has at least one of a renewal license period and a license renewal interval.

In some implementations, the initial license period is greater than the content period of the media content item. In some implementations, at least one of the initial license period and the renewal license period is less than the content period of the media content item. In some implementations, the renewal license period is a predetermined period that is less than half the content period of the media content item. In some implementations, the license renewal interval is less than the initial renewal interval.

In some implementations, determining whether a user account is associated with suspicious behavior detects that the user account is generating multiple license requests across multiple media playback devices associated with the user account. Including that further.

In some implementations, determining whether a user account is associated with suspicious behavior further includes detecting that the user account has not generated a license renewal request within a certain time period.

In some implementations, determining whether a user account is associated with suspicious behavior detects that the user account is generating multiple license requests for the same media content item on the same media playback device. Including that further.

In some implementations, determining whether a user account is associated with suspicious behavior further involves detecting suspicious update requests, and the time associated with suspicious update requests is earlier than the initial update interval. Close to the license period of.

In some implementations, the system further comprises imposing a mode of implementation on the user account that is not as restrictive as the more stringent implementation mode in response to the passage of a particular time period.

The various purposes, features and advantages of the disclosed subject matter may be more fully recognized with reference to the following detailed description of the disclosed subject matter when considered in connection with the accompanying drawings. In the drawings, similar reference numbers identify similar elements.

FIG. 5 illustrates an exemplary example of data flow, including requests and responses, between a media playback device and one or more license servers, according to some implementations of the disclosed subject matter. FIG. 5 illustrates an exemplary example for the process of managing media session concurrency with repeated license renewals, following some implementations of the disclosed subject matter. FIG. 5 illustrates an exemplary example of a process for applying one of a plurality of implementation modes to a user account based on user account behavior information, according to some implementations of the disclosed subject matter. .. FIG. 5 illustrates an example of a generalized schematic of a system in which a mechanism for media session concurrency management by repeated license renewals as described herein can be implemented according to some implementation examples. It is a diagram showing an example of hardware that can be used to implement one or more computing devices and servers shown in FIG. 4, according to some implementation examples of the disclosed subject matter.

Detailed Description Following various implementations, a mechanism (including systems, methods and media) for managing media session concurrency with repeated license renewals is provided.

Generally speaking, a content distribution system may include a content server, a media playback application running on a computing device, and a communication network connecting the content server to the media playback application running on the computing device. The content server may be configured to store media content items that may be downloaded from the content server in a media playback application running on the computing device. For example, a media playback application running on a computing device corresponds to a media content item in response to receiving a user request to select any other suitable information that identifies the title or media content item. It can be configured to download and play media files. The media file may include continuous content data, audio data, video data and the like. Such reproduction may include decoding and rendering audio and video data into audio and video signals. In some implementations, the content server continuously sends or streams media files to the media playback application. Therefore, a media playback application running on a computing device uses the media file to present a portion of the media content item while one or more additional media files of the media content item are being retrieved. Can be done.

In some situations, a limit may be imposed on the number of simultaneous streaming connections that a particular user account is allowed to establish. For example, based on a particular account and / or a particular type of device, the content provider may impose a limit on the maximum number of simultaneous streaming connections that can be established for that account or that device. As used herein, the enforcement of limits on the number of simultaneous streaming connections can be performed by any suitable server, such as a digital rights management (DRM) server. If a user with a particular user account requests a new streaming connection, a media license may be required in addition to the media content. The DRM server detects the number of currently active or established streaming connections associated with that user account, and if that number exceeds the maximum number of concurrent streaming connections allowed, a new streaming connection. By denying the request for, at least in part, you can decide whether to issue a media license to the device requesting a new streaming connection. It should be noted that denying such a license makes the media content unplayable, or prevents the media content from being played otherwise.

Also, in some situations, the media playback application terminates the previous streaming connection established by the user of a user account, but notification of the termination event is not received by the license server. This can result in inaccurate or outdated state information related to the user account being stored on the DRM server, which can affect the browsing experience of the user associated with that user account. For example, a user of a user account who has legitimately terminated a particular streaming connection cannot be allowed to establish any new streaming connection if the DRM server does not know that the particular streaming connection has been terminated. It is not desirable in such content distribution systems as it can compromise the user experience if the user is not allowed to establish a new streaming connection if he / she complies with the restrictions imposed on simultaneous streaming connections.

The DRM server may respond with a license for a limited period of time in response to receiving a media license request from the DRM client device for the new license. For example, a license may have a limited period of about a few minutes (eg, 5 minutes) and may be associated with a policy that allows license renewal. It should be noted that the license can be state information specific to the key system, including one or more keys, each of which can be associated with a key identifier, and any other suitable information about the use of the key. Also, one or more keys included in the license cannot be used to decrypt media content (eg, one or more blocks of media data) if the license has expired.

Prior to the termination of the license on the DRM client device, the DRM client device may issue a license renewal request in accordance with the license renewal policy. For example, a license renewal policy may indicate the renewal request interval (ie, the time between license renewal requests) and the license period. Note that the license renewal policy can be dynamically adjusted based on any suitable parameters (eg, per account, per device, per media content title, etc.). The adjustments increase the license period during server overload times or during data center outages, and increase the license period for user accounts that are likely to exhibit certain types of behavior, and certain types of It may include a more frequent update request interval for user accounts that are considered to behave. Also, license renewal can be repeated if no license renewal request is received after a certain timeout period.

In response to receiving a license renewal request from the DRM client device, the DRM server may decide whether to extend the license for another license renewal period or to discontinue key usage. For example, a license renewal can generally be lighter than the initial license, as it generally contains policy data indicating that the use of the media key is extended or invalidated (for example, while the license may contain one or more media keys). Note that the discontinuation or invalidation of the use of the media key can be done, for example, by transmitting a license renewal for a period of 0 or some other means to enforce the discontinuation of media rights.

Therefore, the DRM client device plays media content items by extending the license by the amount specified in the license renewal or by disabling access to the media key in response to receiving the license renewal. Can be configured to terminate.

With respect to detecting simultaneous streaming connections, the DRM server identifies how many DRM client devices are by counting the number of license renewal requests received during the last renewal period for a user account and / or media content item. You can determine if you are accessing a media content item (or media service in general). Note that if the DRM server has not received a request from the DRM client instance within the last update period, the DRM server can assume that the DRM client device is no longer playing the media content item. For example, a user on a DRM client device may have discontinued playback of a media content item. In another example, key usage rights may have been revoked or discontinued due to license termination.

In some implementations, the DRM server or any other suitable server that responds to the license renewal request may maintain a queue for the license renewal request, and the old entry in that queue ends after a time equivalent to the license period. Can be. The DRM server may decide whether to issue an initial license by checking queues (eg, license renewal server queues) to determine concurrent playback sessions in response to a new initial license request. .. Alternatively, the DRM server always discontinues the license right for the oldest session to the DRM server or any other suitable renewal server the next time a license renewal request is received for the oldest session. It can be configured to meet new demands. This has the advantage, for example, that it always allows the most recent user request, rather than rejecting a new request, as another replay session is considered in progress.

In some implementations, additional or alternative, the DRM server may be configured to implement a discovery-only implementation mode. In the detection-only execution mode, the license server that processes the initial license request and the license renewal server that processes the license renewal request can respond to the received request and log to the record.

These mechanisms described herein can be used in a variety of applications. For example, these mechanisms can be used to detect and suppress users who exhibit suspicious behavior without affecting media delivery services to users who do not exhibit such suspicious behavior. In another example, these mechanisms are independent of the client architecture, so they can be scaled across different types and numbers of clients, do not require storage (eg Javascript® storage) on the client device, and are private. It can be implemented to operate in browsing mode. In more specific examples, these mechanisms cannot suppress the client device implementation or client device architecture. Client devices that can request and process licenses may support the use of repeated license renewals. In yet another example, these mechanisms may provide flexibility as the threat grows or shrinks. In yet another example, these mechanisms can be used to provide a single implementation that detects fraud and enforces simultaneity restriction.

In a more specific example, the absence of a license renewal request received prior to license termination can be used as an indication that the media content is no longer being played. As such, such instructions cannot be lost due to device crashes, closing lids on laptop computing devices, and so on.

These and other features of media session concurrency management with repeated license renewals will be further described in the context of FIGS. 1-5.

With reference to FIG. 1, an exemplary flow of FIG. 100 for achieving repeated license renewals between a media playback device and one or more DRMs or license servers, according to some implementations of the disclosed subject matter. An example is shown. For example, a media playback device may send a license and license renewal request to a DRM server, which handles the decision on whether to issue a license and license renewal. Although FIG. 1 shows one DRM license server, any suitable number of DRM license servers can be used. For example, a media playback device may send a request for a license to a license server and a request for a license renewal to one or more license renewal servers. In another example, a server such as a web server can handle a request for a license or license renewal, which license server should handle the license request, and which license renewal server handles the license renewal request. You can decide if you should. In yet another example, the DRM client separates to another DRM license server in response to the DRM client not receiving a response to a license request or license renewal request within a certain time period (eg, a given timeout). Can be configured to send a license request or license renewal request.

Note that each license renewal can be used to indicate that the connection for streaming a particular media content item remains active, as described below. For example, this is to determine the number of active streaming connections and to compare the determined number of active streaming connections with concurrency limits when deciding whether to issue another license or license renewal. Can be used for.

In some implementations, process 100 may begin at 110 by receiving a request for a media content license for a media content item for presentation on a media playback device. For example, a DRM client may receive encrypted media data in response to requesting a media content item from a content server (eg, to stream a media content item). When the encrypted media data is decrypted with a media license containing one or more keys, the media content item is played on the DRM client. Requests for media content licenses may include metadata associated with media content items, such as title information, video format information, resolution or bit rate, aspect ratio, length information, audio format information, subtitle information, and so on. In another example, a request for a media content license may include user credential information such as the username and password associated with the user account and device information such as device identifier, device type information, connection information, and so on.

In some implementations, the DRM license server may decide whether to respond to license requests from DRM client devices. For example, the DRM license server counts the number of license renewal requests received for a user account during the last renewal period, so that any suitable number of DRM client devices can associate with a user account with simultaneous streaming connections. Can be detected. Continuing with this example, if the DRM license server has not received a renewal request from the DRM client instance within the last renewal period, the DRM license server says that the DRM client device is no longer playing media content items. Such information may be used as an indication of that. This may be, for example, a user of a DRM client device may have discontinued playback of a media content item, or key usage rights may have been revoked or discontinued due to license termination.

In some implementations, the DRM license server may detect the number of concurrent streaming connections by maintaining a queue of license renewal requests where old entries in the queue can terminate after a time equivalent to the license period. Should the DRM license server issue an initial license by checking queues (eg, license renewal server queues) to determine concurrent playback sessions in response to new initial license requests? I can decide.

It should be noted that any suitable information may be obtained to assist the DRM license server in determining how to respond to a new initial license request from a user device authenticated with a particular user account. For example, in an implementation that includes a DRM license server that processes license requests and one or more license renewal servers that process license renewal requests and maintain a license renewal queue, such information is the number of active sessions. Given the number of license renewal requests, the number of license renewals, the timing information associated with the license renewal request, the device information associated with the license renewal request, the license information, and the maximum number of allowed simultaneous sessions. It may include a suitable response and the number of concurrent sessions that remain available for the user account.

Alternatively, the DRM license server deactivates the license right for the oldest session to the DRM license server or any other suitable renewal server the next time a license renewal request is received for the oldest session. , Can be configured to always meet new demands. This has the advantage, for example, that it always allows the most recent user request, rather than rejecting a new request, as another replay session is considered in progress.

With reference to FIG. 1 again, in some implementations, at 120, in response to a request received for a media license from a DRM client device, the DRM license server sends a response containing a license for a limited period of time. Can be. For example, using metadata or other information from a request sent by a DRM client device, the DRM license server can identify and obtain one or more keys associated with the media data to be decrypted. One or more keys may be included in a license for a limited period of time. In a more specific example, the license issued by the DRM license server is in the key system, each containing one or more keys that can be associated with a key identifier and any other suitable information about the use of the keys. It can be peculiar state information.

Note that the duration of such a license can be, for example, a given number of minutes (eg, 3 minutes, 5 minutes, etc.). For example, the duration of a license can be equal to the duration of a media content item or the overall length of playback. In another example, the duration of the license can be equivalent to the duration of the media content item and the additional duration for user interaction such as pausing the playback of the media content item (eg content duration plus x minutes). In yet another example, the license period can be set as a short period compared to the overall playback length of the media content item (eg, a 5 minute license period for a media content item with a total playback period of 30 minutes). ). Also, in some implementations, such licenses may be configured to have a policy that allows for license renewal by setting a specific license period, and prior to the termination of the license, the DRM client device. Issue a license renewal request to maintain your media license and keep playing media content items. One or more keys included in the license cannot be used to decrypt media content (eg, one or more blocks of media data) if the license has expired.

In some implementations, the license issued by a DRM license server or license renewal server (eg, a suitable server that maintains a license renewal account) may be configured based on any suitable parameter. For example, a content provider may provide any suitable parameter that dynamically adjusts the license period of a license for a particular user account, a particular device, a particular media content, and so on. Such parameters include server overload (for example, increasing the license period to ease the use of server resources) and data center outage (for example, increasing the license period in response to detection of a data center outage). (To do) and user accounts that are considered good or good behavior (eg, increasing the license period for certain user accounts that have little or no suspicious behavior detected) and suspicious behavior were detected. User accounts (for example, reducing the license period and / or applying different license policies that reduce or dynamically change the number of concurrent sessions based on user behavior) and conflict resolution (for example, the server is abnormal) Automatically allow initial licenses or license renewals for user accounts that are considered good behavior in response to indicating that a situation exists) and media type (for example, in contrast to shorter audio clips). In response to decisions such as (longer movies receive a shorter license period), or in response to receiving these instructions, a license period adjustment can be triggered.

In some implementations, as an additional or alternative to allowing the license period to be modified, the renewal request interval may also be modified based on any suitable parameter. For example, the general behavior of a user account or user device (eg, good behavior in that it does not have an instance of suspicious behavior detected, bad behavior in that the number of detections of suspicious behavior is greater than the threshold, specific The update request interval may be modified based on the behavior parameters in response to parameters that indicate (such as undetermined behavior in having a user account or user device with behavior information that is less than the period of. In a more specific example, the server issues a license with a renewal request interval of the default period (eg, a longer renewal grace period of 5 minutes compared to a shorter and more restrictive 2 minute renewal grace period). It may, in response to the behavioral information associated with the user account or user device, determine whether the renewal request interval in later license requests should be reduced. In this example, the initial license request can receive a less restrictive license with a longer renewal request interval, for example every 6 minutes, but the license renewal request detects suspicious behavior (eg, certain). In response to the number of license requests in a particular time period that is greater than the threshold), you may receive more restrictive license renewals with shorter renewal request intervals, such as every two minutes. It can be used, for example, in response to a decision that a user account has multiple new license requests while other licenses are in effect. This is because a user with a particular user account is abusing their account by streaming a lot of media content at the same time and blocking update requests, or is interested in the user consuming it. It can show that you are legitimately browsing various media content until you find the media content you are using.

Note that any suitable approach can be used to set the update request interval. For example, the server may associate behavioral instructions with each user account or each user device. Each behavioral instruction is associated with a specific license period and / or a specific renewal request interval. In response to receiving the behavioral instructions, the DRM license server may send the appropriate license in response to the received license request or license renewal request.

In some implementations, if a license renewal is allowed for the issued license, the license may contain information related to one or more servers for processing the license renewal request (eg, one or more). URL about the license renewal server). In some implementations, such information may include an ordered list of URLs for one or more license renewal servers. Examples of the URL include a URL for the first license renewal server and a URL for the second license renewal server when no response is received within a given timeout period. Alternatively, in some implementations, such information is the URL of the first license renewal server and one of the license renewal servers if the first license renewal server cannot be reached within a certain time period. It may include one or more fallback URLs.

In some implementations, at 130, the DRM client may determine if a license renewal is required for the currently issued license. For example, in response to receiving a license issued at 120, the DRM client has a specific license period (eg 5 minutes) and the license renewal for the issued license is a specific license renewal. It may be decided that it is allowed at the request interval. In response to determining the license period, the DRM client renews the license, such as 2 minutes before the end of the currently issued license (or well before the end of the currently issued license). Can determine the specific time period in which should be obtained.

In a more specific example, the DRM client may determine that the policy associated with the issued license indicates the license period and the renewal request interval (or the time between license renewal requests). For example, if a user wishes to continue playing a media content item by extending the currently issued license, the policy may instruct the DRM client to open a particular license renewal window at a particular time. For example, a license renewal request may be received from the DRM server within a renewal window that opens at least one minute before the end of the currently issued license. Note that the license renewal policy can be dynamically adjusted by the DRM license server based on any suitable parameters (eg, per account, per device, per media content title, etc.). The adjustment may increase the license period during server overload or data center outage, increase the license period for user accounts that may exhibit certain types of behavior, and exhibit certain types of behavior. It may include making the update request interval more frequent for the user account, and so on.

In some implementations, the DRM client device has 140 in response to determining that a license update is required to continue playing the media content item prior to the termination of the currently issued license. A license renewal request can be sent at. A license renewal request issues a license identifier associated with the currently issued license, a session identifier associated with the currently active streaming connection, a certain amount of time prior to the termination of the currently issued license, or a license renewal. It may include any suitable information, such as any other suitable information from the DRM client device required by the DRM license server to do so. In some implementations, the license issued by the DRM license server has any information (eg, user account information, license information, device information, timing information, or) to issue a license update for the currently issued license. It may include instructions as to whether any suitable combination thereof) is required.

In some implementations, if no response to the license renewal request is received, the DRM client device may repeat the license renewal request to obtain any suitable number of valid renewals after the configured timeout. For example, a response to a license renewal request may not be received due to the shutdown of a particular license renewal server. In a more specific example, in response to sending a license renewal request to the license renewal server at the first URL, the DRM client device sends a fallback URL to another license renewal server for subsequent license renewals. A request can be sent. The transmission of the license renewal request may continue to be transmitted to the license renewal server at the fallback URL until the license renewal is obtained.

At 150, in response to receiving a license renewal request from the DRM client device, the DRM license server may decide whether to issue a license renewal. For example, the DRM license server may decide whether to extend the license for another license renewal period or to deactivate the key usage right. Note that the decision to issue a license renewal may include setting a license renewal period (eg, another 3 minutes, another 5 minutes, etc.) to continue using the media key, which will keep the media content item playing. Becomes possible. Also, discontinuing or invalidating the use of media keys in a license can be done, for example, by sending a license renewal for a period of zero, or by issuing an order to terminate the right to use the key otherwise.

In some implementations, as mentioned above, the DRM license server counts the number of license renewal requests received during the last renewal period for a user account from any suitable number of DRM client devices. Can detect the number of simultaneous streaming connections associated with. Continuing with this example, if the DRM license server has not received a renewal request from the DRM client instance within the last renewal period, the DRM license server means that the DRM client device is no longer playing media content items. Such information may be used as instructions for. Examples of such instructions include an instruction that the user of the DRM client device has discontinued the playback of the media content item, an instruction that the key usage right has been invalidated or discontinued due to the termination of the license, and the like.

In some implementations, the DRM license server may detect the number of concurrent streaming connections by maintaining a queue of license renewal requests where old entries in the queue can terminate after a time equivalent to the license period. Therefore, the DRM license server may decide whether to issue a license renewal by checking the queue (eg, the license renewal server queue) to determine the ongoing playback session in response to the license renewal request. ..

In an embodiment in which one or more license renewal servers process license renewal requests, the license server may query the license renewal queue and determine information that can be used to process the license renewal request. .. Examples of such information are the number of active sessions, the number of license renewal requests, the number of license renewals, the timing information associated with the license renewal request, the device information associated with the license renewal request, the license information, and the maximum number that can be allowed. There is a favorable response given the concurrent sessions of, the number of concurrent sessions that remain available for the user account, and so on.

Alternatively, in some implementations, the DRM license server may implement a discovery-only mode in which initial license requests and / or license renewal requests are automatically addressed, as well as the licenses and licenses associated with the requests. Keep a log with updates. This can be achieved during periods such as server overloads, data center outages, and so on.

Note that in some implementations, the DRM license server grants the DRM license server or any other suitable renewal server license rights for the oldest session the next time a license renewal request is received for the oldest session. It can be configured to always respond to new update requests while being discontinuous. In response to determining that the license renewal request will respond to an older session in the queue specified for termination, the DRM license server will perform a license renewal or media right discontinuation with a period of zero. The license renewal request can be responded to by some means. This may have the advantage of always allowing the most recent user request, rather than rejecting the new request, for example, as another replay session is considered in progress.

At 160, license renewal messages with specific renewal parameters may be sent from the DRM license server to the DRM client device. At 170, the DRM client device may decide whether to allow playback of the media content item based on the license renewal message received. For example, as mentioned above, in response to receiving a license renewal message, the DRM client device may extract renewal parameters from the received license renewal message and the extension to the license may extend for a specific period of time (eg to the initial license). It may be determined that another short term that is the same as the associated license period, a short term that is less than the license period associated with the initial license, etc.) has been granted. At 180, media playback items with renewed licenses may continue to play. The DRM client device can return to 130 and it may be determined at a later time whether a license renewal is required to continue playing the media content item. For example, prior to the termination of a renewed license (eg, when the license renewal window opens), the DRM client device may decide if a license renewal is required to continue playing the media content item.

In another example, as described above, receiving a license renewal message, extracting renewal parameters from the received license renewal message, and performing a zero period license renewal (or media rights discontinuation). In response to determining that some other means) has been issued, the DRM client device may disable access to the key, thereby ending playback of the media content at 190.

In some implementations, different modes of implementation may be used with respect to the disclosed subject matter. In an exemplary example where the license period and renewal request interval can be dynamically adjusted by the DRM license server, the DRM license server may make such adjustments to achieve one of a plurality of implementation modes.

With reference to FIG. 2, the DRM license server may initiate process 200 at 210 by receiving a request from a credentially authenticated user device corresponding to the user account. For example, the request may be a request for an initial license in response to selecting a media content item for playback.

At 220, the DRM license server may send a response to the request according to an implementation mode with specific license parameters. For example, the DRM license server may start each DRM client device in the initial discovery only mode. Continuing with this example, in the initial detection-only mode, the DRM license server sets the update request interval to 5 minutes (or any other suitable request interval), plus the content duration of the media content item plus x minutes. A license period equivalent to (for example, content period + x minutes for pause instructions that can be received during playback of media content items) can be set. It should be noted that any suitable initial renewal request interval and / or license period may be provided in this detection-only implementation mode.

In some implementations, the DRM license server may continue at 230 by accessing the user account behavior information and examining the user account behavior information. For example, in response to receiving a license request or license renewal request from a user device authenticated with the credentials corresponding to the user account, and in connection with deciding whether the DRM license server should respond to the request. , Process 200 may access the license record associated with the user account and determine if the information in the user account record behaves suspiciously. Suspicious behavior may include, for example, information indicating possible suppression or possible suppression of update requests by one or more devices associated with a user account. In a more specific example, a user account is generating more new license requests than a certain number of new license requests across multiple devices, and is not generating renewal requests within a certain time period. In response to discovering from the information in the record, the DRM license may use such user account behavior information as an indication that the renewal request is suppressed by the device associated with the user account, and the license or license renewal. The parameters can be adjusted.

In some implementations, at 240, the DRM license server may adjust license or license renewal parameters. For example, in response to detecting possible suppression of renewal requests (or any other suspicious behavior regarding a user account), the DRM license server has different implementations with adjusted license parameters for that user account. Modes can be imposed. Generally speaking, this can be a stricter implementation mode, including, for example, shorter license terms and / or more frequent renewal request intervals.

As shown in FIG. 2, if the DRM license server continues to receive requests from one or more devices associated with the user account, the DRM license may return to 230 and continue to review user account behavior information. .. Therefore, in response to continuing to detect possible suppression of renewal requests (or any other suspicious behavior regarding the user account), the DRM license server has the adjusted license parameters for the user account. Yet another mode of implementation may be imposed. The yet another implementation mode is, for example, a strict implementation mode with a further adjusted license period and / or a further adjusted renewal request interval.

In some implementations, at 250, the DRM license server may decide whether to modify the current implementation mode based on user account behavior information. For example, the DRM license server may modify the execution mode in response to determining that the device associated with the user account is suppressing renewal requests or is less likely to behave suspiciously. Alternatively, the license parameters associated with the request from the device associated with the user account may be adjusted. In a more specific example, the DRM license server may include multiple levels of enforcement, and in response to user account behavior information, the DRM license server may set the level of enforcement (eg, detection only enforcement mode and more stringent enforcement mode). Can decide whether to increase or decrease (with). In another more specific example, the DRM license server may reduce the level of implementation to a less stringent implementation mode in response to detecting that a certain amount of time has passed. In yet another, more specific example, the DRM license server detects that a certain amount of time has passed and in response that the device associated with the user account continues to behave suspiciously. A license or license renewal for a period of 0 may be issued, which discontinues or invalidates the use of the media key.

An exemplary example of a plurality of applicable modes of implementation is shown in FIG.
As shown, the DRM license server can be started at 310 by applying a detection-only mode with a specific renewal interval and a specific license period. For example, as described above in connection with FIG. 2, the DRM license server may start each DRM client device in the initial detection only mode. Continuing with this example, in the initial detection-only mode, the DRM license server sets the update request interval to 5 minutes (or any other suitable request interval), plus the content duration of the media content item plus x minutes. A license period equivalent to (for example, content period + x minutes for pause instructions that can be received during playback of media content items) can be set. It should be noted that any suitable initial renewal request interval and / or license period may be provided in this detection-only implementation mode.

During discovery-only mode, the DRM license server may continue to receive requests from the user device associated with the user account, querying the license record at 320 and reviewing the user account behavior information associated with the user account. By detecting the possibility of suppression of renewal requests (or any other suspicious behavior regarding the user account), a lightweight implementation mode with adjusted renewal interval and / or license period parameters is applied at 330. Can be done. For example, examining user account behavior information in a license record and, within a certain time period, a user account is generating more new license requests than a certain number of new license requests (eg, across multiple devices). In response to detecting that the update request has not been generated, the DRM license server may use the user account behavior information as an indication that the update request is suppressed, and the user account is in lightweight implementation mode. Can be imposed.

In lightweight implementation mode, the DRM license server may modify the renewal request interval and / or license period. Continuing with reference to the example above, the DRM license server can maintain the renewal request interval to 5 minutes (or any other suitable request interval) and reduce the license period to half the content period (content period ÷ 2). Can be set to be equal. Note that setting the license period equal to half the content period of the media content item is merely an example, and any suitable license period less than the content period of the media content item can be set and / or detected. Any suitable license period that is less than the license period set in the only mode can be set. In response to the user of the user account suppressing the update request, such user account will not be able to consume the entire media content.

During the lightweight implementation mode, the DRM license server may continue to receive requests from the user device associated with the user account and detect potential suppression of update requests (or any other suspicious behavior regarding the user account). In response to, at 340, query the license record and examine the user account behavior information associated with the user account. For example, in response to receiving a license request or license renewal request from a device associated with a user account, the DRM license server takes this opportunity to further review the user account behavior information based on the license record. obtain.

Referencing FIG. 3 again, at 350, further adjusted in response to determining that the user account behavior information continues to indicate that the device associated with the user account may be involved in suspicious behavior. Strict implementation modes with renewal intervals or license duration parameters may be applied. For example, the DRM license server determines that a certain period of time has passed and that the device associated with that user account behaves to indicate that it may be suppressing license renewal requests. Strict implementation modes may be applied in response to. In another example, the DRM license server recorded a specific event in the license record, such as receiving two or more new license requests for the same media content item on the same device, or receiving a suspicious license renewal request. Strict implementation modes can be applied in response to detecting that.

In a more specific example, in response to detecting that a user account is consistently generating more than one new license request for the same media content on the same device, or a suspicious update request from the device. In response to receiving (eg, instead of a 5 minute renewal interval, the time since the last renewal request is close to the license period), the DRM license server updates such information from the license record. It can be used as an indication that the request is suppressed and that a reload is being performed in the middle of the content (at the end of the license). Note that user accounts that are subject to the lightweight implementation mode can be affected only slightly by server outages. This is because only an extended stop can stop the playback of a media content item. Also, if suspicious behavior persists, the user account may be subject to a stricter implementation mode, or any other preferred mode that is more restrictive.

In strict implementation modes, the DRM license server may further modify the renewal request interval and / or license period parameters. Continuing with reference to the examples above, the DRM license server may set the renewal interval to 3 minutes (or any other suitable request interval) and the license period to 5 minutes (or any other suitable period). Can be set to. Therefore,
If the update request is suppressed, the user of the user account cannot watch the media content for more than 5 minutes at a time. Note that user accounts that have been subject to strict implementation modes can only be affected by server outages longer than a few minutes (eg 2 minutes).

Also, in some implementations, after a certain period of time (eg, one week, two weeks, etc.), the DRM license server, at 360, is more like the lightweight implementation mode or detection only mode described above. A relaxed mode can be imposed on the user account.

Note that most users generally fall into the category associated with relaxed implementation modes, so the user experience for user accounts imposed with more relaxed implementation modes cannot be affected, and server resources are also affected. I can't receive it. Also, for non-abuse users, imposing a more restrictive mode with an update server outage can simply negatively affect the user and the user experience, but even in such an outage the user. Can be given a long grace period, and suspicious users can reach an alternative server.

FIG. 4 shows Example 400 of a generalized schematic of a system in which a mechanism for media session concurrency management with repeated license renewals as described herein can be implemented according to some implementation examples. .. As shown, the system 400 may include one or more user devices 410. User devices 410 can be local to each other or remote to each other. The user device 410 may be connected to the communication network 406 by one or more communication links 408, which communication network 406 becomes a server such as a digital rights management (DRM) license server 402 via the communication link 404. Can be linked.

System 400 may include one or more servers 402. Server 402 provides access to the mechanisms described herein for media session concurrency management with repeated license renewals, such as processors, computers, data processing devices or any suitable combination of such devices. It can be any suitable server to do. In some implementations, the DRM license server 402 that handles license requests and license renewal requests can be distributed as any suitable number of servers. For example, as described above and as shown in FIG. 4, the mechanism for issuing initial licenses and issuing license renewals is distributed across multiple backend components and multiple frontend components and / or interfaces. Can be done. In a more specific example, a DRM license server 402 may be provided that handles an initial license request from one or more user devices 410 that can respond with one or more media keys, and the use of media keys. One or more license renewal servers 420 may be provided that handle license renewal requests that may respond with policy data indicating extension or revocation. In this example, by having multiple server devices 402 and 410, the response to the license renewal request may include, for example, extracting the media key and incorporating the media key into the license, rather than responding to an initial license request. Can also be faster. This may further allow one or more license renewal servers 420 to handle license renewals to be isolated from the key server or key storage device and user account database. As described below, this may further allow the system 400 to include multiple servers for handling license renewals (eg, providing server reliability and redundancy).

In some implementations, multiple license servers 402 and 420 increase reliability and / or increase the speed at which the server can communicate with user device 410 (eg, license and / or license renewal communication). It can be realized in various positions to do what it does.

In some implementations, yet another server (or set of servers) may maintain a record of licenses and renewal licenses to indicate the number of concurrent sessions.

Some implementations of license renewal may require servers 402 and 420 as well as user device 410 to have a shared awareness of the session key used to authenticate messages, as described herein. The mechanism is that server 402, which responds to the initial license request, and server 420, which responds to the license renewal request, can derive the same session key and authenticate and sign the message without the need to exchange any information between them. It can be realized to calculate such a key, as it can. Therefore, the license renewal server 420 may continue to respond to the license renewal request even if the license server 402 does not have access to the infrastructure required to respond to the initial license request. In addition, the license server 402 and / or 420 may be configured to constantly renew the license in an emergency mode, such as when the backend infrastructure becomes unavailable and the simultaneity cannot be checked.

In such an embodiment, the existing media playback session cannot be interrupted if the license server is running and reachable (eg, even if the original DRM server 402 is unreachable). Therefore, adding license server redundancy can increase resiliency and the media playback application can include multiple URLs to process license renewal messages or requests. This could, for example, allow the media playback application to be more resilient to server interrupts or failures.

In some implementations, system 400 may be implemented to further increase resiliency by deploying license renewal server 420 across the configuration and infrastructure. This can increase the likelihood that a license renewal request will be processed, for example, in the event that the central server or data center becomes unreachable.

Note that license renewals are generally smaller in size than the initial license, as they include policy data indicating whether the use of the media key should be extended or disabled (and not the media key itself). .. Therefore, the license renewal request may require that a smaller number of resources be addressed than the initial license request. The license renewal server 420 can then be separated from the key server / store and, for example, the main user account database. Therefore, the license renewal server 420 may differ from the server 402 corresponding to the initial license request. This can, for example, increase the reliability of the overall system 400.

In some implementations of the disclosed subject matter, the simultaneity implementation system 400 described herein can be implemented to increase the reliability of the simultaneity implementation system using distributed redundancy. Such implementations are valid for users of user accounts that have been subject to the severe enforcement modes described above (since, for example, user accounts that are subject to detection-only enforcement mode or lightweight enforcement mode cannot be adversely affected by server outages). possible.

In some implementations, if the license server 402 corresponding to the initial license request becomes unavailable, the initial license request from the media playback application running on the user device 410 will fail (eg 503). Or other error message). For example, the media playback application is License Server 402
Can receive an HTTP response code indicating that it was unable to provide a response to the license request. In response to detecting a network and / or server failure for the license request message, the media playback application running on the client device will fall back the URL (eg, the following URL from the list of license servers) License Server 402 Can be used to send a request for a license. As mentioned above, the media playback application is of any preference for license server 402, including, for example, different clusters or data centers across countries, different clusters or data centers in different countries, different clusters or data centers in different continents, and so on. You can access a list with a large number of fallback URLs. The media playback application may continue to send license requests to one or more fallback license servers 402 until a license is received. For example, a media playback application may attempt to reach a particular license server 402 a certain number of times before proceeding to the next license server 402. In another example, the media playback application may attempt to reach the license server 402 at a particular location a certain number of times before proceeding to the license server 402 at a different location (eg, utilized by a West Coast based data center). If not possible, try to reach license server 402 located on the east coast). Note that in some implementations, the media playback application may execute these repetitive requests until a license server 402 becomes available and a license is received.

In some implementations, if the license renewal server 420 corresponding to the license renewal request becomes unavailable, the license renewal request from the media playback application running on the user device 410 will fail (eg 503 or). Other error messages). For example, the media playback application may receive an HTTP response code indicating that the license renewal server 420 was unable to provide a response to the license renewal request. In response to detecting a network and / or server failure for a license renewal request message, a media playback application running on a client device will fallback license a URL (for example, the following URL from the list of license renewal servers). It can be used on update server 420 to send requests for license renewals. As mentioned above, the media playback application can be any for license renewal server 420, including, for example, different clusters or data centers across countries, different clusters or data centers in different countries, different clusters or data centers in different continents, and so on. You can access a list with a suitable number of fallback URLs. The media playback application may continue to send license renewal requests to one or more fallback license renewal servers 420 until a license renewal is received. For example, a media playback application may attempt to reach a particular license renewal server 420 a certain number of times before proceeding to the next license renewal server 420. In another example, the media playback application may attempt to reach the license renewal server 420 at a particular location a certain number of times before proceeding to the license renewal server 420 at a different location (eg, a West Coast based data center). If is not available, try to reach the license renewal server located on the east coast). Note that in some implementations, the media playback application may perform these attempts to receive license renewals from the license renewal server 420 while the license period of the currently active license has not expired.

In some implementations, the license server 402 may begin responding to the initial license request by accessing the user database and content keystore to meet the license request. Note that if the license server backend is not available, the server rejects the license request (eg, 500, 503 or other error message is received). The license server 402 may then check the license request or concurrent use record (eg, record 422 on license renewal server 420 or any other suitable server). Similarly, if the simultaneity infrastructure is not available, the server may choose to respond to the request or fail (eg, receive a 500, 503 or other error message). Based on the simultaneity information, the license server 402 may reject the license request or respond to the license request. Alternatively, as mentioned above, the license server 402 may always be configured to respond to new license requests, flagging older licenses for discontinuity.

In some implementations, the license renewal server 420 may begin to respond to the license renewal request by checking for renewal requests or concurrent use records such as license record 422 on the license renewal server 420. If the session is flagged for discontinuity, the license server 420 may reject the license renewal request or issue a response indicating that replay should be discontinued. Otherwise, the license renewal server 420 may issue a license renewal.

In some implementations, the license server 402 or 420 is used to determine if a license renewal should be issued a renewal request or a record of concurrent use or any other suitable information (eg, record 422). If no access is available, the license server 402 or 420 may decide whether to enter emergency update mode. For example, in response to the number of failed attempts to access records from the backend server component to be greater than a given threshold, the license server 402 or 420 should put the server into emergency update mode. It can be determined that there is. Such detections can be logged and alerts can be triggered. In emergency renewal mode, the license server 420 may automatically renew all valid licenses. In some implementations of emergency update mode, the license period and / or update request interval may be increased (eg, to mitigate update messages to the server during server outage or server overload).

With reference to FIG. 4 again, other servers may be included in system 400. For example, a content delivery server 430 may receive a request to present a media content item (eg, an encryption that requires a key from DRM license server 402 or any other suitable server to decrypt the media data. Can provide media content items (in the form of). In another example, the content delivery server 430 may provide metadata or other information corresponding to the media content displayed by the user device 410.

In general, the user device 410 may include any computing device capable of sending and receiving messages over a network such as network 406 and accessing and / or playing content. Further, the user device 410 may include any computing device capable of connecting to and receiving information from another computing device, such as a laptop computer, smartphone and tablet computer. However, computing devices are not so limited: mobile phones, display pagers, radio frequency (“RF”) devices, infrared (“IR”) devices, personal digital assistants (“PDAs”), handheld computers, etc. It may include yet other devices such as wearable computers and integrated devices that combine one or more of the aforementioned devices. As such, the user device 410 is typically broad in terms of capabilities and features.

In some implementations, the web-enabled user device 410 may include a browser application configured to send and receive web pages, web-based messages, and the like. The browser application can be configured to receive and display graphics, text, multimedia, media content, etc. using virtually any internet-based protocol and / or network-based protocol. Internet-based protocols and / or network-based protocols include, but are not limited to, wireless application protocol messages (“WAP”) or hypertext transfer protocols (“HTTP”). In one embodiment, the browser application uses a Handheld Device Markup Language (HDML), a Wireless Markup Language (WML) to display and send messages. , WM
LSscript, JavaScript, Standard Generalized Markup Language ("SGML"), HyperText Markup Audio Language (HTMAL), and Extendable Markup Language (XML) (eXtensible Markup Language) ”) etc. is enabled. In one implementation, a user of a client user may use a browser application to perform various activities over the network (online). However, other applications can also be used to perform various online activities.

The user device 410 may further include at least one other client application configured to receive and / or transmit content to and from another computing device. The client application may include the ability to send and / or receive content and the like. The client application may further provide information that identifies itself, including type, ability, and name. In one embodiment, the user devices 410 may identify themselves as part of a class of devices. In another implementation, the user device 410 has a telephone number, a mobile identification number (“MIN (Mobile Identification Number)”), an electronic serial number (“ESN (electronic serial number)”), and an Internet Protocol (IP (Internet Protocol)). ) It may uniquely identify itself through any of a variety of mechanisms, including addresses, network addresses, or other mobile device identifiers. The information may further indicate the content format that can be used by the mobile device. Such information may be provided, such as in network packets, and may be transmitted between other client devices or other computing devices. In addition, the device and / or the components within a device communicating with the client device may identify themselves using any of a variety of mechanisms, including the mechanism used by the client device. It should be easily understood.

The user device 410 may further be configured to include a client application that allows the user to log in to a user account that may be managed by another computing device. Such a user account may be configured to allow a user to manage one or more online activities in one non-limiting example. The online activity includes, in one non-limiting example, search activity, social networking activity, browsing various websites, or communicating with other users. In one embodiment, the user's client device may receive content that is streamed to the client device for playback on the client device. However, participation in online activities can also be performed without logging in to the user account.

In some embodiments, each of the user device 410 and the servers 402, 420 and 430 can be either a general purpose device such as a computer or a special purpose device such as a client, server or the like. Either of these general purpose devices or special purpose devices can be any suitable component such as a hardware processor (which can be a microprocessor, digital signal processor, controller, etc.), memory, communication interface, display controller, input device, etc. Can include. For example, the user device 410 may be a smartphone with a camera, a tablet computer with a camera, a wearable computer with a camera, a camera device interfaced with the smartphone (eg a camera dongle for a smartphone), or a digital camera (eg a point and shoot camera). Can be realized as point and shoot camera), DSLR camera, digital cam coder, etc.), analog cam coder, personal computer, laptop computer, smartphone, tablet computer, gaming device, digital media receiver, set top box, smart television, server, etc. ..

The communication network 406 includes the Internet, an intranet, a wide area network (WAN), and a local area network (LAN (local-area)).
network)), wireless network, digital subscriber line (DSL (digital subscriber)
line)) In any suitable computer network or combination of such networks, including networks, frame relay networks, asynchronous transfer mode (ATM) networks, virtual private networks (VPNs), etc. possible. Communication links 404, 408, 425 and 435 can be any communication link suitable for communicating data between the user device 410 and the servers 402, 420 and 430. Examples of such communication links are network links, dial-up links, wireless links, hard wire drinks, any other suitable communication links, or any suitable combination of such links. The user device 410 can also be used to present the video to the viewer from the content delivery server 430 or any other suitable source (eg, hard drive, cloud storage, flash drive, etc.). The user device 410, servers 402, 420 and 430 may be located in any suitable location.

FIG. 5 shows the hardware that can be used to implement server 402 (or server 420 or 430) and one of the user devices 410 shown in FIG. 4, according to some implementations of the disclosed subject matter. Example 500 of the wear is shown. With reference to FIG. 5, the user device 410 may include a hardware processor 512, a display 514, an input device 516, and a memory 518 that can be interconnected. In some implementations, memory 518 may include a storage device (such as a non-temporary computer-readable medium) for storing a computer program for controlling the hardware processor 512.

The hardware processor 512 may use a computer program to present content and / or an interface on display 514, which allows the user to, for example, extract video from server 430 and interact with a media playback application. To interact with the mechanisms described herein for resource management in a state where repeated license renewals are performed by a device such as DRM license server 402 or license renewal server 420, and communication link 408. Allows you to send and receive data through. Also, data received through communication link 408 or any other communication link can be received from any suitable source. In some implementations, the hardware processor 512 is, for example, a transmitter, a receiver, a transmitter / receiver, a transceiver,
Alternatively, any other suitable communication device may be used to send and receive data over the communication link 408 or any other communication link. The display 514 can be a flat panel display, a cathode ray tube display, a projector, a touch screen, a speaker, and / or any other suitable display and / or presentation device. The input device 516 can be a computer keyboard, computer mouse, microphone, touch pad, speech recognition circuit, touch screen and / or any other suitable input device.

The server 402 (or server 420 or 430) may include a hardware processor 522, a display 524, an input device 526 and a memory 528 that can be interconnected. In some implementations, memory 228 may include a storage device for storing data received through communication link 104 or other links. The storage device may further include a server program for controlling the hardware processor 222.

The hardware processor 522 may use a server program to communicate with the user device 412. Also, data received through communication link 404 or any other communication link can be received from any suitable source. In some implementations, the hardware processor 522 uses, for example, a transmitter, receiver, transmitter / receiver, transceiver, or any other suitable communication device to provide communication link 404 or any other communication link. Data can be sent and received via. In some implementations, the hardware processor 522 may receive commands and / or values sent by one or more users. The display 524 can be a flat panel display, a cathode ray tube display, a projector, a touch screen, a speaker, and / or any other suitable display and / or presentation device. The input device 526 can be a computer keyboard, computer mouse, microphone, touch pad, speech recognition circuit, touch screen and / or any other suitable input device.

In one particular embodiment, the mechanisms described herein include server-side software, server-side hardware, client-side software, client-side hardware, or any suitable combination thereof. Can include. For example, a media playback application may be a computer program written in a programming language that is recognizable by a server 402 running an editing application (eg, Java®, C, Objective-C, C ++, C #, Javascript, VisualBasic, etc. Or it can include programs written in programming languages such as any other preferred approach). As another example, media playback applications include (eg, "HTML (Hyper Text Markup Language)"), dynamic hyper text markup language ("DHTML (Dynamic Hyper Text Markup Language)"), and extensions. Via any suitable encoding such as HTML (Extensible Markup Language), JavaServer Pages (“JSP”), Active Server Pages (“ASP”), ColdFusion, or any other suitable approach. Can include one or more web pages or web page parts.

Therefore, systems, methods and media for media session concurrency management with repeated license renewals are provided.

In some implementations, any suitable computer-readable medium may be used to store instructions for performing the functions and / or processes described herein. For example, in some implementations, the computer-readable medium can be temporary or non-temporary. For example, non-temporary computer-readable media include magnetic media (such as hard disks, floppy® disks), optical media (such as compact disks, digital video disks, and Blu-ray disks), and flash memory. Semiconductor media (such as EEPROM (electrically programmable read only memory)), electrically erasable programmable read only memory (EEPROM), non-temporary or It may include any suitable medium such as any suitable medium and / or any suitable tangible medium that does not lack an aspect of permanence during transmission. As another example, a temporary computer-readable medium is a wire, conductor, optical fiber, signal on a network in a circuit, any suitable medium that is temporary or lacks an aspect of permanence during transmission. And / or may include any suitable intangible medium.

It should be understood that the above steps of the process can be performed in any order or sequence, not limited to the order and sequence shown and shown in the figure. In addition, some of the above steps in the process can, where appropriate, be performed substantially simultaneously, or in parallel to reduce latency and processing time.

Also, as used herein, the term mechanism may include hardware, software, firmware or any suitable combination.

Although the present invention has been described and demonstrated in the exemplary embodiments described above, the present disclosure is considered exemplary and numerous in the details of the embodiments of the invention limited only by the appended claims. It is understood that changes can be made without departing from the spirit and scope of the invention. The features of the disclosed embodiments can be combined and reconstructed in various aspects.

Claims (11)

A system for simultaneity detection and implementation
With memory
When the hardware processor executes a computer-executable instruction stored in the memory, the at least one server includes at least one server including a hardware processor.
In response to a request for a media content license related to a media content item to be presented on the media playback device, one or more keys associated with said media content item and a limited license period and renewal request interval. Sending a license, including a policy, to the media playback device,
Receiving a request for a license renewal relating to the media content item presented on the media playback device at a time within the renewal request interval.
Determining whether to issue the license renewal for the media content item based on media session concurrency across multiple media playback devices associated with the user account.
A system configured to send the license renewal to the media playback device. The system of claim 1, wherein the request for the media content license is associated with the user account. In claim 1 or 2 , the limited license period associated with the license renewal has a period of 0 in response to determining that one or more keys in the license are invalidated. Described system. The at least one server is further configured to send a list of plurality of license servers for processing the request for the license renewal to a media playback application running on the media playback device, said media. When the reproduction application sends the request for the license renewal to the first license server among the plurality of license servers and detects that the first license server is unavailable, and said. Claims 1 to 3 which send the request to a second license server among the plurality of license servers until the license renewal for the media content license is received prior to the termination of the license. The system according to any one item. The at least one server further
Determining that the license renewal record is inaccessible in response to querying the license renewal record issued for the user account in a given period of time .
Claim 1 or claim 2 configured to automatically enter emergency renewal mode to issue the license renewal in response to determining that the record of the license renewal is inaccessible. The system described in. A method for simultaneity detection and enforcement that is performed using at least one server, including a hardware processor .
In response to a request for a media content license related to a media content item to be presented on the media playback device, one or more keys associated with said media content item and a limited license period and renewal request interval. Sending a license, including a policy, to the media playback device,
Receiving a request for a license renewal relating to the media content item presented on the media playback device at a time within the renewal request interval.
Determining whether to issue the license renewal for the media content item based on media session concurrency across multiple media playback devices associated with the user account.
A method comprising sending the license renewal to the media playback device. The method of claim 6 , wherein the request for the media content license is associated with the user account. In claim 6 or 7 , the limited license period associated with the license renewal has a period of 0 in response to determining that the one or more keys in the license are invalidated. The method described. The media playback application further comprises transmitting a list of plurality of license servers for processing the request for the license renewal to a media playback application running on the media playback device, wherein the media playback application has the plurality of licenses. When sending the request for the license renewal to the first license server of the servers and detecting that the first license server is unavailable and prior to the termination of the license, the said The method according to any one of claims 6 to 8 , wherein the request is transmitted to a second license server among the plurality of license servers until the license renewal for the media content license is received. .. Determining that the license renewal record is inaccessible in response to querying the license renewal record issued for the user account in a given period of time .
The method of claim 6 or 7 , comprising entering an emergency renewal mode that automatically issues the license renewal in response to determining that the record of the license renewal is inaccessible. A computer program for causing a computer to execute the method according to any one of claims 6 to 10 .

Images