Encryption-based session establishment
AssigneeVerizon Patent and Licensing Inc.
InventorsFenglin Yin, Jianxiu Hao, Zhiying Jin
Life of this patent
Estimating the term…
Loading patent…
AssigneeVerizon Patent and Licensing Inc.
InventorsFenglin Yin, Jianxiu Hao, Zhiying Jin
Estimating the term…
A first server is configured to receive a first token from a user device, determine whether the first token is valid, request the user device to provide a set of credentials to a second server, based on determining that the first token is invalid, and receive a first response from the user device. The first response may include information identifying whether the user device is authenticated to communicate with the first server. The first server is further configured to send the first response to a third server. The third server may generate a second response to indicate authentication of the user device to communicate with the first server. The first server is further configured to receive the second response from the third server, generate a second token, based on receiving the second response, and send the second token to the user device.
A method comprising:
A system comprising:
A non-transitory computer-readable medium storing instructions, the instructions comprising:
Dependencies are inferred from the claim text.
From the US filing history. Foreign family members aren’t listed.
Applying verification of the received information: the source of the received data
Wherein the data content is protected, e.g. by encrypting or encapsulating the payload: wherein the sending and receiving network entities apply…
For authentication of entities: using tickets, e.g. Kerberos
For controlling access to devices or network resources: when the policy decisions are valid for a limited amount of time
About 6 years 5 months of term left · ends 13 Mar 2033 (estimated)
Drawings are temporarily unavailable. Open the PDF at USPTO
Users sometimes use user devices to access content (e.g., videos, images, audio, or some other content) from a content provider via interaction with a content platform. The content provider may authenticate the user device to allow the user device to access the content provider via the content platform. Authenticating the user device to access the content provider may pose security risks for the user device, the content platform and the content provider.
FIG. 1 illustrates an example overview of an implementation described herein;
FIG. 2 illustrates an example environment in which systems and/or methods, described herein, may be implemented;
FIG. 3 illustrates example components of a device that may be used within the environment of FIG. 2;
The following detailed description refers to the accompanying drawings. The same reference numbers in different drawings may identify the same or similar elements.
The systems and/or methods, as described herein, may authenticate a user device to establish a secure session with a platform accounts server in order to allow the user device to access content (e.g., videos, photos, audio, and/or some other content) associated with a partner accounts server. For example, assume that the platform accounts server is a trusted entity with respect to the partner accounts server (e.g., the platform accounts server may access the partner accounts server using a server-to-sever call authorization protocol, such as an OAuth protocol, and/or some other protocol).
In some implementations, the user device may access content from a content distribution server, associated with the partner accounts server, when a session with the platform accounts server is established (e.g., to allow the user device to select and/or receive content via a content platform, associated with the platform accounts server). The systems and/or methods may use multiple authentication responses between trusted servers to authenticate the user device to establish a session with the platform accounts server. Additionally, the systems and/or methods and may further allow the user device to establish a session with the platform accounts server without providing login credentials with each session request.