# US 11,122,030 B2 · Methods, systems, devices, and products for web services > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,122,030 B2 - Document ID: US11122030B2 - Status: Granted - Kind: B2 - Application number: 16/374,792 - Filed: 2019-04-04 - Published: 2019-08-01 - Granted: 2021-09-14 - Earliest claimed: 2010-08-04 - Assignees: AT&T Mobility II LLC - Applicants: AT&T Mobility II LLC - Inventors: Jay O. Glasgow; Johannes Simon Jaskolski - Web page: https://patentgrep.com/patent/US11122030B2 ## CPC - H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)} - H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)} - H04L 63/108: {when the policy decisions are valid for a limited amount of time} - H04W 12/068: {using credential vaults, e.g. password manager applications or one time password [OTP] applications} - H04L 63/168: {above the transport layer} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract A login session server establishes a communications session between an application executing on a device and a service provided by a web services gateway. A temporary login session socket is established and a token is sent to the device. The temporary login session socket may be used to verify a service provided by the web services gateway. ## Claims ### Claim 1 A method for an authentication to a web service, comprising: receiving, by a server, a request from a client device requesting an access to the web service, the web service being provided by a service provider; configuring, by the server, a communications path to the client device in response to the request requesting the access to the web service; determining, by the server, whether an application on the client device is authorized for the access to the web service, the determining whether the application on the client device is authorized for the access to the web service resulting in a first determination; determining, by the server, whether a developer of the application on the client device has purchased sufficient access to the service provider to accommodate the application on the client device, the determining whether the developer of the application on the client device has purchased sufficient access to the service provider to accommodate the application on the client device resulting in a second determination; sending, by the server, an authentication token to the client device via the communications path in response to both the first determination being that the application on the client device is authorized for the access to the web service and the second determination being that the developer of the application on the client device has purchased sufficient access to the service provider to accommodate the application on the client device; and closing, by the server, the communications path in response to a detection that the authentication token has been received by the client device. ### Claim 2 (depends on 1) The method of claim 1, wherein the authentication token indicates that the application on the client device is authorized for the access to the web service. ### Claim 3 (depends on 1) The method of claim 1, further comprising sending, by the server, the authentication token to a web services gateway that facilitates providing the web service. ### Claim 4 (depends on 1) The method of claim 1, further comprising associating, by the server, the client device to the web service. ### Claim 5 (depends on 1) The method of claim 1, further comprising sending, by the server, the authentication token to a device that facilitates providing the web service. ### Claim 6 (depends on 1) The method of claim 1, wherein the client device comprises a smartphone, an Internet appliance, a set top box, a home security system, a home management device, or vehicle electronics. ### Claim 7 (depends on 6) The method of claim 6, wherein the client device further comprises a browser. ### Claim 8 A system, comprising: a hardware processor; and a memory device, the memory device storing instructions, the instructions when executed causing the hardware processor to perform operations, the operations comprising: receiving a request from a client device requesting an access to a web service, the web service being provided by a service provider; configuring a communications path to the client device in response to the request requesting the access to the web service; determining whether an application on the client device is authorized for the access to the web service, the determining whether the application on the client device is authorized for the access to the web service resulting in a first determination; determining whether a developer of the application on the client device has purchased sufficient access to the service provider to accommodate the application on the client device, the determining whether the developer of the application on the client device has purchased sufficient access to the service provider to accommodate the application on the client device resulting in a second determination; sending an authentication token to the client device via the communications path in response to both the first determination being that the application on the client device is authorized for the access to the web service and the second determination being that the developer of the application on the client device has purchased sufficient access to the service provider to accommodate the application on the client device; and closing the communications path in response to a detection that the authentication token has been received by the client device. ### Claim 9 (depends on 8) The system of claim 8, wherein the authentication token indicates that the application on the client device is authorized for the access to the web service. ### Claim 10 (depends on 8) The system of claim 8, wherein the operations further comprise sending the authentication token to a web services gateway that facilitates providing the web service. ### Claim 11 (depends on 8) The system of claim 8, wherein the operations further comprise associating the client device to the web service. ### Claim 12 (depends on 8) The system of claim 8, wherein the operations further comprise sending the authentication token to a device that facilitates providing the web service. ### Claim 13 (depends on 8) The system of claim 8, wherein the client device comprises a smartphone, an Internet appliance, a set top box, a home security system, a home management device, or vehicle electronics. ### Claim 14 (depends on 13) The system of claim 13, wherein the client device further comprises a browser. ### Claim 15 A memory device storing instructions that when executed cause a hardware processor to perform operations, the operations comprising: receiving a request from a client device requesting an access to a web service, the web service being provided by a service provider; configuring a communications path to the client device in response to the request requesting the access to the web service; determining whether an application on the client device is authorized for the access to the web service, the determining whether the application on the client device is authorized for the access to the web service resulting in a first determination; determining whether a developer of the application on the client device has purchased sufficient access to the service provider to accommodate the application on the client device, the determining whether the developer of the application on the client device has purchased sufficient access to the service provider to accommodate the application on the client device resulting in a second determination; sending an authentication token to the client device via the communications path in response to both the first determination being that the application on the client device is authorized for the access to the web service and the second determination being that the developer of the application on the client device has purchased sufficient access to the service provider to accommodate the application on the client device; and closing the communications path in response to a detection that the authentication token has been received by the client device. ### Claim 16 (depends on 15) The memory device of claim 15, wherein the authentication token indicates that the application on the client device is authorized for the access to the web service. ### Claim 17 (depends on 15) The memory device of claim 15, wherein the operations further comprise sending the authentication token to a web services gateway that facilitates providing the web service. ### Claim 18 (depends on 15) The memory device of claim 15, wherein the operations further comprise associating the client device to the web service. ### Claim 19 (depends on 15) The memory device of claim 15, wherein the client device comprises a smartphone, an Internet appliance, a set top box, a home security system, a home management device, or vehicle electronics. ### Claim 20 (depends on 19) The memory device of claim 19, wherein the client device further comprises a browser.