Systems and methods for application identification
US-9794233-B2 · Oct 17, 2017 · US
US10341306B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10341306-B2 |
| Application number | US-201715682453-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 21, 2017 |
| Priority date | Aug 31, 2011 |
| Publication date | Jul 2, 2019 |
| Grant date | Jul 2, 2019 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Systems and methods for application identification in accordance with embodiments of the invention are disclosed. In one embodiment, a user device includes a processor and memory configured to store an application, a session manager, an application identifier, and at least one shared library, and the processor is configured by the session manager to communicate the application identifier and the application identifier data to an authentication server and permit the execution of the application in response to authentication of the application by the authentication server.
Opening claim text (preview).
What is claimed is: 1. A method for granting access to a software library on a user device using a session token, the method comprising: receiving a request for access to a software library on a user device, where the request for access includes a session token, provisioning data and the name of the software library; where the session token is associated with the software library, is encrypted using information specific to the software library, grants access to the software library when authenticated, and denies access to the software library when not authenticated; negotiating a session token key with the software library using the user device; and encrypting the session token with the session token key; decrypting the session token using the information specific to the software library; authenticating the decrypted session token; granting access to the software library when the decrypted session token is authenticated; and denying access to the software library when the decrypted session token is not authenticated; receiving at least a portion of an encoded bitstream containing media content; decoding the at least a portion of an encoded bitstream to access the media content using the user device; and playing back the accessed media content by the user device. 2. The method of claim 1 , further comprising retrieving a product identifier stored in a memory of the user device, where the product identifier is associated with the execution platform of the user device. 3. The method of claim 1 , further comprising: verifying the software library stored on the user device using a library manifest containing information that can be used to identify and verify the software library; wherein the library manifest contains at least one hash value of the software library; and wherein verifying the software library comprises taking a hash value of the software library and comparing the hash value against the at least one hash value contained in the library manifest. 4. The method of claim 3 , wherein the library manifest contains at least one private key signature. 5. The method of claim 1 , wherein the session token contains a creation time that can be used to validate the token. 6. The method of claim 1 , wherein the session token contains a validity duration for the amount of time before the token expires. 7. The method of claim 1 , further comprising determining whether the software library is compatible with a particular application using an application identifier of the application. 8. The method of claim 7 , wherein determining whether the software library is compatible with a particular application using an application identifier of the application comprises determining whether the application is the current version. 9. A user device, comprising: a processor; and a non-volatile storage containing an access authorization application for causing the processor to perform the steps of: receiving a request for access to a software library on the user device, where the request for access includes a session token, provisioning data and the name of the software library; where the session token is associated with the software library, is encrypted using information specific to the software library, grants access to the software library when authenticated, and denies access to the software library when not authenticated; negotiating a session token key with the software library using the user device; and encrypting the session token with the session token key; decrypting the session token using the information specific to the software library; authenticating the decrypted session token; granting access to the software library when the decrypted session token is authenticated; and denying access to the software library when the decrypted session token is not authenticated; receiving at least a portion of an encoded bistream containing media content; decoding the at least a portion of an encoded bitstream to access the media content using the user device; and playing back the accessed media content by the user device. 10. The user device of claim 9 , wherein the access authorization application further causes the processor to perform the step of retrieving a product identifier stored in a memory of the user device, where the product identifier is associated with the execution platform of the user device. 11. The user device of claim 9 , wherein: the access authorization application further causes the processor to perform the step of verifying the software library stored on the user device using a library manifest containing information that can be used to identify and verify the software library; the library manifest contains at least one hash value of the software library; and verifying the software library comprises taking a hash value of the software library and comparing the hash value against the at least one hash value contained in the library manifest. 12. The user device of claim 11 , wherein the library manifest contains at least one private key signature. 13. The user device of claim 9 , wherein the session token contains a creation time that can be used to validate the token. 14. The user device of claim 9 , wherein the session token contains a validity duration for the amount of time before the token expires. 15. The user device of claim 9 , wherein the access authorization application further causes the processor to perform the step of determining whether the software library is compatible with a particular application using an application identifier of the application. 16. The user device of claim 15 , wherein determining whether the software library is compatible with a particular application using an application identifier of the application comprises determining whether the application is the current version.
above the transport layer · CPC title
for supporting key management in a packet data network (cryptographic mechanisms or cryptographic arrangements for key management H04L9/08) · CPC title
Protecting executable software · CPC title
by delegation of authentication, e.g. a proxy authenticates an entity to be authenticated on behalf of this entity vis-à-vis an authentication entity · CPC title
based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.