Loading patent…
AssigneeVerizon Patent and Licensing Inc.
InventorsJianxiu Hao, Fenglin Yin, Zhong Chen, Pramod Kalyanasundaram
Estimating the term…
A device may receive traffic flow information that includes user device identifiers. The device may receive, from a user device accessing an application associated with a third party service, an authentication request to authenticate the user device with a third party device that provides the third party service. The request may include a session token that identifies a session, an application identifier that identifies the application, and a user device identifier that identifies the user device. The device may determine to authenticate the user device based on whether the user device identifier matches one of the user device identifiers included in the traffic flow information. The device may provide, to the third party device, the session token and an indication of whether the user device has been authenticated to permit the third party device to allow or deny access to the third party service.
A device, comprising:
A non-transitory computer-readable medium storing instructions, the instructions comprising:
A method, comprising:
Dependencies are inferred from the claim text.
From the US filing history. Foreign family members aren’t listed.
For authentication of entities: based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or…
For authentication of entities: by delegation of authentication, e.g. a proxy authenticates an entity to be authenticated on behalf of this entity…
For controlling access to devices or network resources: wherein the security policies are location-dependent, e.g. entities privileges depend on…
Digital communication
About 8 years 11 months of term left · ends 30 Sep 2035 (estimated)
Authentication is a process for proving the identity of an authorized user so that the authorized user can gain access to a protected resource. Authentication may be accomplished using a password. For example, a username and password may be used by an authorized user during a log-in process that controls access to protected computing devices, operating systems, applications (e.g., email, web sites, etc.), databases, networks, etc.
FIG. 1 is a diagram of an overview of an example implementation described herein;
FIG. 2 is a diagram of an example environment in which systems and/or methods, described herein, may be implemented;
FIG. 3 is a diagram of example components of one or more devices of FIG. 2;
The following detailed description of example implementations refers to the accompanying drawings. The same reference numbers in different drawings may identify the same or similar elements.
User authentication may be achieved by requiring a user to enter a username and/or a password in order for the user's identity to be verified. However, requiring a username and password for user authentication may be inefficient. For example, the user may use a single username or password for multiple services, which may cause security issues if there is a security breach in one of the services. Alternatively, the user may use different usernames or passwords for different services, which may cause the user to forget a username or password. Also, usernames and passwords may be hacked, stolen, forgotten, misplaced, etc. Implementations described herein may provide another means of authentication using traffic flow information (e.g., information in association with user devices belonging to a network (e.g., a mobile network), which may include a protocol identifier, a source network address (e.g., a source internet protocol (IP) address), a source port identifier, a destination network address (e.g., a destination IP address), a destination port identifier, etc.), which may reduce user reliance on usernames and passwords and/or may increase security.
FIG. 1 is a diagram of an overview of an example implementation 100 described herein. As shown in FIG. 1, assume that example implementation 100 includes a user device, a third party application server, an authentication device, and flow aggregation devices. The third party application server may host an application that the user device is attempting to access. The authentication device may be used to authenticate the user device for the third party application server using traffic flow information which the authentication device gets from flow aggregation devices. The flow aggregation devices can capture traffic flow information from user devices on a network.