Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A method for transmitting compressed rights, comprising: negotiating, by a terminal, a compress algorithm of rights with a server; requesting, by the terminal, the server through an “Extensions” field in a rights object request (RORequest) message to transmit the rights in compression format; generating, by the server, a rights object response (ROResponse) message according to a standard approach, compressing the rights in the ROResponse message according to the negotiated compress algorithm, generating a compressed ROResponse message, and sending the compressed ROResponse message to the terminal; and receiving, by the terminal, the compressed ROResponse message, decompressing the rights in the received ROResponse message according to the negotiated compress algorithm, and generating a decompressed ROResponse message; wherein negotiating, by the terminal, the compress algorithm of rights with the server comprises: sending, by the terminal, a device hello request (DeviceHello) message to the server, and informing the server about self-supported compress algorithms through a “Supported Compress Algorithm” field newly added in the DeviceHello message; and selecting, by the server, the compress algorithm agreed by negotiating according to content of the “Supported Compress Algorithm” field, and informing the terminal of the selected compress algorithm through a “Selected Compress Algorithm” field newly added in a rights server hello response (RIHello) message; wherein requesting, by the terminal, the server through the “Extensions” field in the RORequest message to transmit the rights in compression format comprises: sending, by the terminal, the RORequest message to the server, and informing the server through a “Need Compress Rights” field newly added in the “Extensions” field of the RORequest message to transmit the rights in compression format.
A method for efficiently transmitting digital rights involves a terminal and a server negotiating a compression algorithm. The terminal sends a request to the server indicating it wants rights in compressed format using a new "Need Compress Rights" field within the "Extensions" field of a Rights Object Request (RORequest) message. This request is initiated after the terminal informs the server of its supported algorithms via a new "Supported Compress Algorithm" field in a DeviceHello message. The server selects an agreed-upon algorithm, communicating its choice back to the terminal using a "Selected Compress Algorithm" field in a Rights Server Hello Response (RIHello) message. The server then generates a standard Rights Object Response (ROResponse), compresses the rights data using the negotiated algorithm, and sends the compressed ROResponse to the terminal, which decompresses it to obtain the original rights.
2. The method according to claim 1 , wherein generating, by the server, the ROResponse message, compressing the rights in the ROResponse message, and generating a compressed ROResponse message and sending the compressed ROResponse message to the terminal comprises: receiving, by the server, the RORequest message sent by the terminal, and acquiring that rights in compression format need to be transmitted according to a “Need Compress Rights” field in the RORequest message; and generating, by the server, the ROResponse message according to the standard approach, compressing the rights in the ROResponse message according to the compress algorithm in the “Selected Compress Algorithm” field to acquire a “Compress Rights” field, and generating a compressed ROResponse message according to the “Compress Rights” field and sending the compressed ROResponse message to the terminal.
In the method for transmitting compressed rights, as outlined previously where a terminal requests rights in compressed format and negotiates a compression algorithm with a server, the server, upon receiving the Rights Object Request (RORequest) message, checks for the "Need Compress Rights" field to confirm the compression request. The server generates a standard Rights Object Response (ROResponse) message. Then, it compresses the rights data within the ROResponse using the negotiated compression algorithm specified in the "Selected Compress Algorithm" field, creating a "Compress Rights" field. Finally, the server constructs a compressed ROResponse message based on the "Compress Rights" field and sends it to the terminal.
3. The method according to claim 2 , wherein data of the rights in the ROResponse message after compression is in base 64 format.
In the method for transmitting compressed rights, as outlined previously where the server compresses rights and includes them in a "Compress Rights" field of the Rights Object Response (ROResponse) message, the data representing the compressed rights is encoded using base64 format. This encoding ensures that the compressed binary data can be safely transmitted as text.
4. The method according to claim 2 , wherein decompressing and generating the decompressed ROResponse message by the terminal comprises: receiving, by the terminal, the compressed ROResponse message, decompressing the rights in the received ROResponse message according to the compress algorithm in the “Selected Compress Algorithm” field, and generating the decompressed ROResponse message.
In the method for transmitting compressed rights, as outlined previously where the terminal receives a compressed Rights Object Response (ROResponse) message, the terminal decompresses the rights data. The terminal uses the compression algorithm indicated in the "Selected Compress Algorithm" field to decompress the rights within the received ROResponse message, thereby generating the decompressed ROResponse message with the original rights data.
5. The method according to claim 4 , further comprising: verifying data integrity according to a hash value in the decompressed rights after the terminal decompresses the rights in the received ROResponse message.
In the method for transmitting compressed rights, as outlined previously where the terminal decompresses the rights data from the received Rights Object Response (ROResponse) message, after decompression, the terminal performs a data integrity check. This check involves verifying the integrity of the decompressed rights data by comparing a calculated hash value of the decompressed data with a pre-existing hash value included within the rights data itself.
6. A system for transmitting compressed rights, comprising: a terminal and a server; wherein, the terminal is configured to negotiate a compress algorithm of rights with the server, and request the server through an “Extensions” field in an RORequest message to transmit the rights in compression format; the terminal is further configured to receive a compressed ROResponse message from the server, decompress rights in the received ROResponse message according to the negotiated compress algorithm, and generate a decompressed ROResponse message; and the server is configured to negotiate the compress algorithm of rights with the terminal, generate the ROResponse message according to a standard approach after receiving the RORequest message from the terminal, compress the rights in the ROResponse message according to the negotiated compress algorithm, generate the compressed ROResponse message and send the compressed ROResponse message to the terminal; wherein the terminal is further configured to send a DeviceHello message to the server and inform the server about self-supported compress algorithms through a “Supported Compress Algorithm” field newly added in the DeviceHello message; and correspondingly, the server is further configured to select the compress algorithm agreed by negotiating according to the content of the “Supported Compress Algorithm” field, and inform the terminal of the selected compress algorithm through a “Selected Compress Algorithm” field newly added in a RIHello message; wherein the terminal is further configured to send the RORequest message to the server, and inform the server through a “Need Compress Rights” field newly added in the “Extensions” field of the RORequest message to transmit the rights in compression format.
A system for efficiently transmitting digital rights includes a terminal and a server. The terminal and server negotiate a compression algorithm. The terminal requests compressed rights from the server using a "Need Compress Rights" field in the "Extensions" field of a Rights Object Request (RORequest). The terminal receives a compressed Rights Object Response (ROResponse), decompresses the rights using the negotiated algorithm, and generates a decompressed ROResponse. The server, upon receiving the RORequest, generates a standard ROResponse, compresses the rights data using the negotiated algorithm, and sends the compressed ROResponse. The terminal initially informs the server of its supported algorithms via a "Supported Compress Algorithm" field in a DeviceHello message. The server selects a compression algorithm and informs the terminal of its choice in a "Selected Compress Algorithm" field in a Rights Server Hello Response (RIHello).
7. The system according to claim 6 , wherein the server is further configured to receive the RORequest message sent by the terminal, acquire that rights in compression format need to be transmitted according to a “Need Compress Rights” field in the RORrequest message, generate the ROResponse message according to the standard approach, compress the rights in the ROResponse message according to the compress algorithm in the “Selected Compress Algorithm” field to acquire a “Compress Rights” field, and generate the compressed ROResponse message according to the “Compress Rights” field and sending the compressed ROResponse message to the terminal.
In the system for transmitting compressed rights, as outlined previously where the terminal requests rights in compressed format and negotiates a compression algorithm with a server, the server, upon receiving the Rights Object Request (RORequest) message, checks the "Need Compress Rights" field to confirm the compression request. The server generates a standard Rights Object Response (ROResponse). Then, it compresses the rights data within the ROResponse using the negotiated compression algorithm specified in the "Selected Compress Algorithm" field, creating a "Compress Rights" field. Finally, the server constructs a compressed ROResponse message based on the "Compress Rights" field and sends it to the terminal.
8. The system according to claim 7 , wherein data of the rights in the ROResponse message after compression is in base 64 format.
In the system for transmitting compressed rights, as outlined previously where the server compresses rights and includes them in a "Compress Rights" field of the Rights Object Response (ROResponse) message, the data representing the compressed rights is encoded using base64 format. This encoding ensures that the compressed binary data can be safely transmitted as text.
9. The system according to claim 7 , wherein the terminal is further configured to receive the compressed ROResponse message, decompress the rights in the received ROResponse message according to the compress algorithm in the “Selected Compress Algorithm” field, and generate the decompressed ROResponse message.
The invention relates to a digital rights management (DRM) system for securely distributing and managing rights objects (ROs) in a networked environment. The system addresses the challenge of efficiently transmitting and processing rights information while ensuring security and integrity. The system includes a terminal configured to receive a compressed rights object response (ROResponse) message, which contains encrypted rights data. The terminal decompresses the rights data using a compression algorithm specified in a "Selected Compress Algorithm" field within the message. After decompression, the terminal generates a decompressed ROResponse message, allowing the rights data to be processed and applied to digital content. The system ensures that rights information is transmitted in a compact form to reduce bandwidth usage while maintaining security through encryption. The terminal's ability to dynamically select and apply the appropriate decompression algorithm ensures compatibility and efficiency in handling different types of rights data. This approach optimizes the distribution of rights objects in DRM systems, balancing performance and security requirements.
10. The system according to claim 9 , wherein the terminal is further configured to verify data integrity according to a hash value in the decompressed rights after decompressing the rights in the received ROResponse message.
In the system for transmitting compressed rights, as outlined previously where the terminal decompresses the rights data from the received Rights Object Response (ROResponse) message, after decompression, the terminal performs a data integrity check. This check involves verifying the integrity of the decompressed rights data by comparing a calculated hash value of the decompressed data with a pre-existing hash value included within the rights data itself.
Unknown
August 26, 2014
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.