System and method for distributed verification of online identity

A decentralized system with trusted third-party verification keys enables real-time user identity verification, addressing privacy concerns and preventing replay attacks in online environments.

JP2024161351AActive Publication Date: 2024-11-19GOOGLE LLC
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
JP2024111019
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2019-08-28
Filing Date
2024-07-10
Publication Date
2024-11-19
Estimated Expiration
2040-04-15

AI Technical Summary

Technical Problem

Existing systems face challenges in verifying the identity of online users in real-time while protecting privacy and preventing replay attacks, particularly in third-party content item distribution platforms, due to the need for multiple referrals to external verifiers and the lack of trusted identity verification methods.

Method used

A decentralized system issues public keys only to trusted third-party content item distributors, enabling real-time verification of user identities through locally maintained verification keys, using digitally signed tokens that are encrypted and decrypted by authorized verifiers.

Benefits of technology

This approach minimizes network overhead and verification time, ensuring real-time identity verification and preventing replay attacks without compromising user privacy.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024161351000001_ABST
    Figure 2024161351000001_ABST
Patent Text Reader

Abstract

To perform distributed verification of an online identity.SOLUTION: An issuer computing system 115 receives a request to generate a composite token, the composite token configured to authorize certain verifying parties to authenticate a first-party token comprising information about a client, generates a composite token using cryptographic keys, and distributes it to the client 105. The client distributes it to other content item networks 155. A verifier computing system 140 receives the composite token from the content item networks, uses a cryptographic key for verifying the authenticity of the token corresponding to the client, and uses the token to further process content item operations. The system can distribute the cryptographic keys prior to the generation and verification of the composite token, and as such allow the parties to verify the composite token in real-time without contacting outside verification parties.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Patent Application No. 16 / 553,599, filed August 28, 2019, and U.S. Provisional Application No. 62 / 840,204, filed April 29, 2019, the contents of which are incorporated herein by reference. [Background technology]

[0002] In a computer network environment such as the Internet, users may interact with third-party content items. These third-party content items, e.g., advertisements, may be displayed on web pages associated with respective publishers. These users may provide information to the publishers indicating their interactions with the third-party content items. Summary of the Invention [Problem to be solved by the invention]

[0003] One technical problem addressed by this disclosure is the difficulty in determining the identity of an online user while preserving the privacy of the online user. Furthermore, a third-party content item distributor may want to verify the identity of a user who visits a publisher's web page within a short predefined time frame (e.g., 100 milliseconds). However, accurately verifying the user's identity requires many queries to external sources responsible for verifying the user's identity. This introduces unacceptable delays for certain third-party content item distributor platforms.

[0004] The problem addressed in this disclosure relates to providing a system that allows distributed verification of online user identities while minimizing the number of queries to third-party verifiers, while maintaining user privacy only to trusted third-party content item distributors. Public keys are issued only to trusted third-party content item distributors that can decrypt the digitally signed token data by the trusted issuer to verify the user's token data in real time. This minimizes the number of queries that verifiers need to make to verify the token data, reducing network overhead and verification time.

[0005] Cookie-based identity support does not support authentication by the issuer, nor does it prevent copying of browser sessions, also known as "replay attacks". As a result, browser cookies are a label, not a trusted identity, of an online user. Similarly, for devices such as connected televisions, device identifiers provide only a weak layer of protection. The authenticity of the device cannot be verified by other parties on behalf of the OEM. In these cases, replay attacks, in which copies of browser sessions are made to create requests for fraudulent content items, cannot be detected, nor can identity verification be performed in real time, as required by many third parties. Thus, the technical solution disclosed herein is a significant improvement over existing techniques of identity verification and fraud detection. [Means for solving the problem]

[0006] The present disclosure discusses a system that includes a publisher that knows the legitimate identity of an online user, who is responsible for authenticating and generating a digital signature corresponding to the token data associated with a particular user. Through encryption, the publisher can control which third-party content distribution platforms (third-party verifiers) can process the user's token data. The system further includes a verifier authorized by the publisher to verify the token information associated with a particular user. Since the verification key is maintained locally by the verifier, the verification process can be done in real time and does not require access to an external party. This allows for real-time identity verification that is distributed between the publisher and the third-party content item distribution platform.

[0007] At least one aspect is directed to a method for providing a signed identity token. The method comprises generating, by a party, a first party token associated with an issuer's domain. The method also comprises sending, by the party, to an issuer, the first party token associated with the issuer's domain. The method further comprises receiving, by the issuer, the first party token associated with the issuer's domain and creating a timestamp corresponding to the first party token. The method further comprises encrypting, by the issuer, the first party token and the timestamp using a private key of the issuer to create a digitally signed token. The method further comprises generating, by the issuer, a plurality of digitally signed tokens, each of the plurality of digitally signed tokens corresponding to a respective verifier. The method further comprises encrypting each of the plurality of digitally signed tokens using a public key provided by the respective verifier. The method also comprises generating, by the issuer, a composite token comprising each of the plurality of encrypted digitally signed tokens. The method further comprises providing, by the issuer, the composite token to a party responsible for generating the first party token.

[0008] Another aspect of the disclosure is directed to a method for verifying a user's identity. The method comprises receiving, by a verifier, a composite token and a timestamp, the composite token comprising a plurality of encrypted digitally signed tokens. The method further comprises enumerating, by the verifier, each of the plurality of encrypted digitally signed tokens in the composite token. The method also comprises determining, by the verifier, which of the enumerated encrypted digitally signed tokens corresponds to the verifier. The method further comprises decrypting, by the verifier, content of the encrypted signed token corresponding to the verifier using a private key belonging to the verifier to generate a signed token. The method further comprises verifying, by the verifier, the validity of a digital signature of the signed token using a public key corresponding to the issuer to generate a valid first-party token. The method further comprises processing, by the verifier, the valid first-party token generated from the signed token in response to the digital signature of the signed token being valid.

[0009] These and other aspects and implementations are described in detail below. The preceding information and the following detailed description include illustrative examples of the various aspects and implementations and provide an overview or framework for understanding the nature and characterization of the claimed aspects and implementations. The drawings provide an explanation and further understanding of the various aspects and implementations, and are incorporated in and constitute a part of this specification.

[0010] The accompanying drawings are not intended to be drawn to scale. Like reference numbers and designations in the various drawings indicate like elements. For purposes of clarity, not every component may be labeled in every drawing. [Brief description of the drawings]

[0011] [Figure 1]FIG. 1 is a block diagram illustrating an example implementation of an environment for distributed real-time verification of online identities. [Diagram 2] 1 is a block diagram representing an example implementation of a key manager 130, according to an example implementation. [Diagram 3] 4 is a flow diagram of an example process for generating a composite token, according to an example implementation. [Figure 4] 4 is a flow diagram of an example process for validation of the contents of a composite token, according to an example implementation. [Diagram 5] FIG. 3 illustrates a representation of a composite token produced by the process shown in FIG. 2. [Figure 6] FIG. 1 illustrates the general architecture of an exemplary computer system that may be employed to implement any of the computer systems discussed herein. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Below is a more detailed description of various concepts related to methods, apparatus, and systems for managing fraud-resistant content item operations, and their implementations. The various concepts introduced above and described in more detail below may be implemented in any of numerous ways, as the concepts described above are not limited to any particular implementation method.

[0013] FIG. 1 is a block diagram illustrating one implementation of an environment 100 for distributed real-time verification of online identities. The environment 100 includes at least one client computing system 105. The client computing system 105 may include at least one processor (or processing circuitry) and a memory. The memory stores processor-executable instructions that, when executed on the processor, cause the processor to perform one or more of the operations described herein. The processor may include a microprocessor, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like, or a combination thereof. The memory may include, but is not limited to, an electronic, optical, magnetic, or any other storage or transmission device capable of providing program instructions to the processor. The memory may further include a floppy disk, a CD-ROM, a DVD, a magnetic disk, a memory chip, an ASIC, an FPGA, a read-only memory (ROM), a random access memory (RAM), an electrically erasable ROM (EEPROM), an erasable-programmable ROM (EPROM), a flash memory, an optical media, or any other suitable memory from which the processor can read instructions. The instructions may include code from any suitable computer programming language. The client computing system 105 may include one or more computing devices or servers that can perform a variety of functions.

[0014] In some implementations, the client computing system 105 may include an application, such as a web browser, configured to generate a browser token. In such an embodiment, the generated browser token may be associated with the domain of the issuer computing system 115 and may include information about the web browser executed by the client computing system 105. In some implementations, the client computing system 105 is configured to generate a device token. In such an embodiment, the generated device token may be associated with the domain of the issuer computing system 115 and may include device information about the client computing system 105. The client computing system 105 may be configured to transmit the generated token to the issuer computing system 115 over the network 110. In some implementations, the client computing system 105 is configured to communicate with an advertising auction system over the content item network 155.

[0015] The network 110 may include computer networks such as the Internet, local, wide, metro or other area networks, intranets, satellite networks, other computer networks such as voice or data mobile telecommunications networks, and combinations thereof. In some implementations, either the key distribution infrastructure 135 or the content item network 155 may be the same as or part of the network 110. The client computing systems 105 of the environment 100 may communicate with, for example, at least one publisher computing system 115 via the network 110. The network 110 may be any form of computer network that relays information between the client computing systems 105 and the publisher computing systems 115 and one or more content sources such as web servers, ad servers, among others. For example, the network 105 may include the Internet and / or other types of data networks such as a local area network (LAN), a wide area network (WAN), a cellular network, a satellite network, or other types of data networks. The network 110 may also include any number of computing devices (e.g., computers, servers, routers, network switches, etc.) configured to receive and / or transmit data within the network 110. The network 110 may further include any number of hardwired and / or wireless connections. For example, the client computing system 105 may communicate wirelessly (e.g., via WiFi, cellular, radio, etc.) with transceivers that are hardwired (e.g., via fiber optic cable, CAT5 cable, etc.) to other computing devices in the network 110.

[0016] The content item network 155 can include computer networks such as the Internet, local, wide, metro or other area networks, intranets, satellite networks, other computer networks such as voice or data mobile telecommunications networks, and combinations thereof. In some implementations, the content item network 155 can be the same as or a part of the network 110. The client computing systems 105 of the environment 100 can communicate with, for example, at least one verifier computing system 140 via the content item network 155. The content item network 155 can be any form of computer network that relays information between the client computing systems 105 and at least one verifier computing system 140, and one or more content sources such as web servers, ad servers, among others. For example, the content item network 155 can include the Internet and / or other types of data networks such as a local area network (LAN), a wide area network (WAN), a cellular network, a satellite network, or other types of data networks. The content item network 155 may also include any number of computing devices (e.g., computers, servers, routers, network switches, etc.) configured to receive and / or transmit data within the content item network 155. The content item network 155 may further include any number of hardwired and / or wireless connections. For example, the verifier computing system 140 may communicate wirelessly (e.g., via WiFi, cellular, radio, etc.) with transceivers that are hardwired (e.g., via fiber optic cable, CAT5 cable, etc.) to other computing devices in the content item network 155.

[0017] The key distribution infrastructure network 135 may include computer networks such as the Internet, local, wide, metro or other area networks, intranets, satellite networks, other computer networks such as voice or data mobile telecommunications networks, and combinations thereof. In some implementations, the key distribution infrastructure network 135 may be the same as or part of the network 110. The key manager computing system 130 of the environment 100 may communicate with, for example, at least one issuer computing system 115 and / or at least one verifier computing system 140 via the key distribution infrastructure network 135. The key distribution infrastructure network 135 may be any form of computer network that relays information between the key manager computing system 130 and at least one verifier computing system 140 or at least one issuer computing system 115, and one or more content sources such as web servers, ad servers, among others. For example, the key distribution infrastructure network 135 may include the Internet and / or other types of data networks such as a local area network (LAN), a wide area network (WAN), a cellular network, a satellite network, or other types of data networks. The key distribution infrastructure network 135 may also include any number of computing devices (e.g., computers, servers, routers, network switches, etc.) configured to receive and / or transmit data within the key distribution infrastructure network 135. The key distribution infrastructure network 135 may further include any number of hardwired and / or wireless connections.For example, the key manager computing system 130 may communicate wirelessly (e.g., via WiFi, cellular, radio, etc.) with transceivers that are hardwired (e.g., via fiber optic cable, CAT5 cable, etc.) to other computing devices in the key distribution infrastructure network 135.

[0018] The issuer computing system 115 may include a server or other computing device operated by an issuer entity to authenticate and / or digitally sign token information, such as a browser or device token, received from a client computing system 105. The issuer computing device 115 may include a token signer component 120 and one or more cryptographic key components 125. In some implementations, the issuer computing system 115 may provide third-party content items or creatives (e.g., advertisements) for display on an information resource, such as a website or web page that includes primary content. The issuer computing system 115 may also provide information resources, such as web pages that include primary content. The issuer computing system 115 may include instructions or computational circuitry for generating a digital signature based on a token corresponding to information associated with the client computing system 105. The issuer computing system 115 may include instructions or computational circuitry for encrypting a digitally signed token corresponding to information associated with the client computing system 105. The issuer computing system 115 may generate a composite token based on the one or more cryptographic key components 125 and the digital signature generated by the token signer component 120. The issuer computing system 115 may generate a composite token by concatenating each of the encrypted, digitally signed tokens together into a single data structure. The issuer computing system 115 may provide the generated composite token to the client computing system 105 over the network 110. The issuer computing system 115 may receive, request, accept, or query both the token signer component 125 and / or the cryptographic key component 125 from the key manager 130 via the key distribution infrastructure 135.In some implementations, the key manager 130 may automatically transmit the token signer component 120 and / or one or more cryptographic key components 125 to the issuer computing system 115 via the key distribution infrastructure 135.

[0019] The verifier computing system 140 may include a server or other computing device operated by a content provider entity to provide verification of authenticity of a signed token received from a client computing system 105 over a content item network 155. In some implementations, the signed token received from the content item network 155 may be a composite token. The verifier computing system 140 may include a token verifier component 145 and a decryption key component 150. The verifier computing system 140 may provide a third-party content item or creative (e.g., an advertisement) for display on an information resource, such as a website or web page that includes the primary content, over the content item network 155. The verifier computing system 140 may provide only the content item in response to verifying a token associated with the client 105 using the decryption key component 150 and the token verifier component 145. One or more verifier computing systems 140 may receive a composite token corresponding to a client computing system 105 over the content item network 155. The composite token received from the content item network 155 may include one or more encrypted digital signatures, one of which may correspond to one of the verifier computer systems 140. Each of the verifier computing systems 140 that received the composite token may parse the composite token to enumerate the multiple encrypted digitally signed tokens. Each of the verifier computing systems 140 may use the decryption key component 150 to decrypt the encrypted digitally signed token corresponding to the verifier computing system 140. An encrypted digitally signed token may be determined to correspond to a verifier computing system 140 if the decrypted digital signature in the encrypted digitally signed token can be verified using the token verifier component 145.The token verifier component 145 can use a public key that corresponds to a private key maintained by the issuer computing system 115 to verify the decrypted digital signature. In some embodiments, the verifier computing system 140 can receive, request, accept, or query both the token verifier and one or more decryption keys from the key manager computing system 130 via the key distribution infrastructure 135. In some implementations, the key manager component system 130 can automatically send the verifier component 145 and / or the decryption key component 150 to the verifier computing system 140 via the key distribution infrastructure 135.

[0020] The client computing system 105, the issuer computing system 115, the verifier computing system 140, and the key manager computing system 130 may include a processor and a memory, i.e., processing circuitry. The memory stores machine instructions that, when executed on the processor, cause the processor to perform one or more of the operations described herein. The processor may include a microprocessor, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like, or a combination thereof. The memory may include, but is not limited to, an electronic, optical, magnetic, or any other storage or transmission device capable of providing program instructions to the processor. The memory may further include a floppy disk, a CD-ROM, a DVD, a magnetic disk, a memory chip, an ASIC, an FPGA, a read-only memory (ROM), a random access memory (RAM), an electrically erasable ROM (EEPROM), an erasable-programmable ROM (EPROM), a flash memory, an optical media, or any other suitable memory from which the processor can read instructions. The instructions may include code from any suitable computer programming language.

[0021] The client computing system 105, the issuer computing system 115, the verifier computing system 140, and the key manager computing system 130 may also include one or more user interface devices. In general, a user interface device refers to any electronic device (e.g., a keyboard, a mouse, a pointing device, a touch screen display, a microphone, etc.) that conveys data to a user by generating sensory information (e.g., a visualization on a display, one or more sounds, etc.) and / or converts sensory information received from a user into electronic signals. According to various implementations, the one or more user interface devices may be internal to the housing of the client computing system 105, the issuer computing system 115, the verifier computing system 140, and the key manager computing system 130 (e.g., a built-in display, a microphone, etc.) or external to the housing of the client computing system 105, the issuer computing system 115, the verifier computing system 140, and the key manager computing system 130 (e.g., a monitor connected to the client computing system 105, a speaker connected to the client computing system 105, etc.). For example, the client computing system 105, the issuer computing system 115, the verifier computing system 140, and the key manager computing system 130 may include electronic displays that visually display web pages using web page data received from one or more content sources via the network 110, the content item network 155, or the key distribution infrastructure 135.

[0022] The issuer computing system 115 may include at least one server. For example, the issuer computing system 115 may include multiple servers located in at least one data center or server farm. In some implementations, the issuer computing system 115 may include information about the client computer system 105. The issuer computing system 115 may include at least one token signer component 120 and at least one cryptographic key component 125. The token signer component 120 and the cryptographic key component 125 may each include at least one processing unit, server, virtual server, circuit, engine, agent, appliance, or other logic device such as a programmable logic array configured to communicate with other computing devices (e.g., the client computing system 105, or the key manager computing system 130) via the network 110 and / or the key distribution infrastructure 135.

[0023] The token signer component 120 and the cryptographic key component 125 can include or execute at least one computer program or at least one script. The token signer component 120 and the cryptographic key component 125 can be separate components, a single component, or part of the issuer computing system 115. The token signer component 120 and the cryptographic key component 125 can include a combination of software and hardware, such as one or more processors configured to execute one or more scripts.

[0024] The token signer component 120 can receive a first party token from a client computing system 105 over the network 110. In some embodiments, the first party token can be associated with a domain of the issuer computing system 115. In some embodiments, the first party token can be generated by a browser running on the client computing system 105. In some other embodiments, the first party token can be a device token generated by the client computing system 105. In some embodiments, the token signer component 120 can receive a request from the client computing system 105 over the network 110 to generate a first party token. The request for the first party token can include browser information corresponding to a browser running on the client computing system 105. The request for the first party token can include device information corresponding to the client computing system 105. In some embodiments, the token signer component 120 can generate a first party token in response to a request from the client computing system 105. The first party token can correspond to a domain of the issuer computing system 115. The token signer component 120 can receive a request for a composite token from the client computing system 105 over the network 110. In some embodiments, the token signer component 120 may receive a request for a digitally signed token from the client computing system 105 over the network 110. The token signer component 120 may generate a timestamp corresponding to receipt of the first party token from the client computing system 105. The timestamp may be generated based on a current time maintained by the issuer computing system 115.The token signer component 120 can maintain one or more private keys corresponding to the issuer computing system 115. In some embodiments, the one or more private keys are received from the key manager computing system 130 via the key distribution infrastructure 135. The token signer component 120 can generate a digitally signed first party token using the one or more private keys. The token signer component 120 can provide the digitally signed first party token to the encryption key component 125 to generate one or more encrypted digitally signed tokens. The token signer component 120 can provide the digitally signed first party token to the encryption key component 125 to generate a composite token comprising one or more encrypted digitally signed tokens.

[0025] The cryptographic key component 125 can receive the digitally signed first party token from the token signer component 120. In some embodiments, the cryptographic key component 125 can receive a request for a composite token from the client computing system 105 over the network 110. In some embodiments, the cryptographic key component 125 can receive a request for an encrypted digitally signed token from the client computing system 105 over the network 110. The cryptographic key component 125 can maintain one or more cryptographic keys. In some embodiments, each of the one or more cryptographic keys is a public key corresponding to the verifier computing system 140. In such an embodiment, the verifier computing system 140 can maintain a private key associated with a corresponding public key maintained by the issuer computing system 115. The one or more cryptographic keys can be received from the key manager computing system 130 via the key distribution infrastructure 135. In some embodiments, the cryptographic key component 125 can receive a request from the token signer component 120 to generate one or more encrypted digitally signed first party tokens. In such an embodiment, the cryptographic key component 125 may generate an encrypted, digitally signed token for each of one or more cryptographic keys maintained by the cryptographic key component 125. The cryptographic key component 125 may generate a composite token comprising one or more encrypted, digitally signed tokens. In such an embodiment, the cryptographic key component 125 may generate the composite token by concatenating each of the one or more encrypted, digitally signed tokens into a single data structure. The cryptographic key component may provide the composite token to the client computing system 105. In some embodiments, the cryptographic key component may provide one or more encrypted, digitally signed tokens to the client computing system 105.

[0026] The verifier computing system 140 may include at least one server. For example, the verifier computing system 140 may include multiple servers located in at least one data center or server farm. In some implementations, the verifier computing system 140 may include information about the client computer system 105. The verifier computing system 140 may include at least one token verifier component 145 and at least one decryption key component 150. The token verifier component 145 and the decryption key component 150 may each include at least one processing unit, server, virtual server, circuit, engine, agent, appliance, or other logic device such as a programmable logic array configured to communicate with other computing devices (e.g., the client computing system 105, or the key manager computing system 130) via the content item network 155 and / or the key distribution infrastructure 135.

[0027] The token verifier component 145 and the decryption key component 150 can include or execute at least one computer program or at least one script. The token verifier component 145 and the decryption key component 150 can be separate components, a single component, or part of the verifier computing system 140. The token verifier component 145 and the decryption key component 150 can include a combination of software and hardware, such as one or more processors configured to execute one or more scripts.

[0028] The decryption key component 150 can receive a composite token corresponding to the client computing system 105 via the content item network 155. The composite token can include one or more encrypted, digitally signed tokens. In some embodiments, the composite token can include a first party token and a timestamp, where the first party token is used to generate the encrypted, digitally signed portion of the composite token. In such an embodiment, the decryption key component 150 can check whether a received timestamp of the composite token is recent to determine whether the composite token was sent as part of a replay attack. If the composite token is determined to be part of a replay attack, the decryption key component can ignore the composite token and stop further processing of the composite token by the verifier computing system 140. The decryption key component 150 can receive a request from the content item network 155 to verify the authenticity of the composite token. The decryption key component 150 can receive a request from the content item network 155 to verify one or more encrypted, digitally signed tokens. The decryption key component 150 can maintain a decryption key. In some embodiments, the decryption key is a private key corresponding to the verifier computing system 140. In such an embodiment, the issuer computing system 115 maintains a public key that is associated with a corresponding private key maintained by the verifier computing system 140 .

[0029] The decryption key may be received from the key manager computing system 130 via the key distribution infrastructure 135. The decryption key component 150 may enumerate each of the encrypted digitally signed tokens in the composite token received from the content item network 155. The decryption key component 150 may enumerate each of the encrypted digitally signed tokens received from the content item network 155. The decryption key component 150 may attempt to decrypt each of the enumerated encrypted digitally signed tokens using a private key maintained by the decryption key component 150 to generate a digitally signed token corresponding to the respective encrypted digitally signed token. In some embodiments, the decryption key component 150 may determine which of the enumerated digitally signed tokens corresponds to the verifier computing system 140. In such embodiments, the decryption key component 150 may decrypt the encrypted digitally signed token corresponding to the verifier computing system 150 using the private key to generate the digitally signed token. The decryption key component 150 may provide the generated one or more digitally signed tokens to the token verifier component 145.

[0030] The token verifier component 145 can receive one or more digitally signed tokens provided by the decryption key component 150. The token verifier component can receive the first party token and a timestamp. The token verifier component 145 can maintain a public key that corresponds to a private key maintained by the issuer computing system 115. In some embodiments, the token verifier component can receive the public key from the key manager computing system 130 via the key distribution infrastructure 135. The token verifier component 145 can verify the first party token by verifying at least one of the digitally signed tokens using the public key. For example, the token verifier component 145 can use the public key to decrypt each of the digitally signed tokens received from the decryption key component 150 to generate one or more decrypted token and timestamp pairs, each of the decrypted token and timestamp pairs corresponding to a respective digitally signed token. The token verifier component 145 can then compare each of the token and timestamp pairs with the first party token and timestamp received by the verifier computing system 140 as part of the composite token. If any of the token and timestamp pairs match the first-party token and timestamp received as part of the composite token, the first-party token is considered verified. A composite token may include multiple encrypted, digitally signed tokens, each corresponding to a verifier computing system 140 authorized by the issuer computing system 115 to verify the authenticity of the first-party token. The digitally signed tokens may be used as digital signatures to verify the authenticity of the first-party token and timestamp.In some embodiments, the verifier computing system 140 may process the first-party token in response to verifying the authenticity of the first-party token.

[0031] 2 is a block diagram representing an example implementation of a key manager computing system 130. The key manager computing system 130 may include a key management service 205, a token signer binary 210, a token verifier binary 215, a verifier encryption key 220, and a verifier decryption key 225. In some implementations, the key management service 205 may be executed by an operating system of the key manager computing system 130.

[0032] In some implementations, the key management service 205 may be an application programming interface provided by the operating system that the issuer computing system 115 and the verifier computing system 140 can interface to request token signer and token verifier data. In some implementations, the issuer computing system 115 may authorize a decryption key to each verifier computing system 140 by interfacing with the key management service 205. In some implementations, the key management service may provide the private key of the token signer component 120 to the issuer computing system 115 using the token signer binary 210. In such implementations, the private key may be provided to the issuer computing system 115 via the key distribution infrastructure 135. In some implementations, the key management service may provide the public key of the token verifier component 145 to the verifier computing system 140 using the token verifier binary 215. In such implementations, the private key may be provided to the issuer computing system 115 via the key distribution infrastructure 135. The key management service 205 can authorize a particular verifier computing system 140 by generating a particular verifier encryption key 220 and a verifier decryption key 225. For example, the key management service 205 can receive a request from the issuer computing system 115 to authorize only a particular verifier computing system 140. The key management service 205 can then generate a verifier encryption key (e.g., a public key) and a verifier decryption key (e.g., a private key), where each public / private key pair corresponds to a verifier computing system 140 authorized by the issuer computing system 115. The key management service 205 can provide all the public (encryption) keys to the encryption key component 125 of the issuer computing system 115 via the key distribution infrastructure 135. The key management service 205 can distribute each of the private (decryption) keys to the respective authorized verifier computing systems 140.

[0033] 3 is a flow diagram of an exemplary process 300 for generating an encrypted composite token. The process 300 includes steps of generating a first-party token (302), sending the first-party token to an issuer (304), digitally signing the first-party token using a private key (306), selecting an i-th verifier cryptographic key (308), creating an encrypted, digitally signed token using the i-th verifier cryptographic key (310), determining whether i is equal to the number of verifier cryptographic keys (312), incrementing a register i (314), generating a composite token from the encrypted, digitally signed token (316), and providing the composite token to a party responsible for generating the first-party token (318).

[0034] In further detail of step 302, a party generates a first-party token. In some implementations, the first-party token may be associated with an issuer's domain. In some implementations, the first-party token may include data from an application (e.g., a web browser). In some implementations, generating the first-party token includes device information from a device or system performing process 300. Generating the first-party token may include generating a request for an encrypted, digitally signed token from an issuing party. The issuing party may also be referred to as an issuer. Generating the first-party token may include generating a request for a composite token from the issuer. In some implementations, generating the first-party token may include generating a timestamp. In such implementations, the timestamp may be a high-resolution (e.g., millisecond or microsecond resolution, etc.) timestamp.

[0035] In further detail of step 304, the party sends the first party token to the issuer. Sending the first party token to the issuer can include sending a timestamp generated by the party. In some implementations, sending the first party token can include sending a request for an encrypted, digitally signed token to the issuer. In some embodiments, sending the first party token can include sending a request for a composite token to the issuer, the composite token comprising at least one or more encrypted, digitally signed tokens. Sending the first party token can include sending a request for a digitally signed token from the issuer.

[0036] In further detail of step 306, the issuer digitally signs the first-party token sent in step 304 using a private key. In some embodiments, step 306 can include receiving, by the issuer, the digitally signed token generated by the party in step 302. In some embodiments, receiving, by the issuer, the digitally signed token can include receiving a timestamp generated in step 302 or step 304. In some embodiments, step 306 of the process can concatenate the first-party token and the timestamp into a token and timestamp pair. In step 306, the issuer can digitally sign the first-party token using a digital signature algorithm (e.g., DSA, RSA, etc.). In some embodiments, the issuer can generate the digitally signed token by using a digital signature algorithm on the token and timestamp pair. In some embodiments, a hash function (e.g., SHA-1, SHA-256, MD5, etc.) can be performed using the first-party token as input to generate a hashed token. In some embodiments, a hash function can be performed using the token and timestamp pair as input to generate a hashed token and timestamp pair. The issuer of process 300 can use a digital signature algorithm on the hashed token to generate a digitally signed token. In some embodiments, the issuer of process 300 can use a digital signature algorithm on the hashed token and timestamp pair to generate a signed token.

[0037] The process 300 includes a step of selecting an i-th verifier cryptographic key (308). This process step may be performed, for example, by the issuer computing system 115 to encrypt the digitally signed token of all cryptographic keys maintained by the cryptographic key component 125. In some embodiments, the step 308 may include receiving one or more cryptographic keys, each corresponding to a verifier, where n is equal to the number of cryptographic keys. In some embodiments, the cryptographic keys may be received from a key manager, for example, the key manager computing system 130. In some embodiments, the cryptographic keys are public keys corresponding to the respective verifiers. In a first iteration of the loop created by the process 300, the step 308 may select a first cryptographic key (i-th, i=1). It should be understood that the one or more cryptographic keys may be selected in any order.

[0038] In further detail of step 310, process 300 may create an encrypted digitally signed token using the i-th verifier cryptographic key. In some embodiments, process 300 uses an asymmetric encryption algorithm, where the cryptographic key is a public key and the private key belongs to the verifier. Process 300 may create the encrypted digitally signed token by encrypting the digitally signed token generated in step 306 with the i-th cryptographic key selected in step 308. In some embodiments, the cryptographic key may be the private key of a public / private key pair, where the public key is maintained by the verifier. In some embodiments, step 310 does not encrypt the digitally signed token generated in step 306, but simply returns the digitally signed token.

[0039] The process 300 includes creating encrypted digitally signed tokens corresponding to all cryptographic keys maintained by the issuer. For example, the cryptographic key component 125 of the issuer computing system 115 can determine whether the currently created encrypted digitally signed token is the nth encrypted digitally signed token, where n corresponds to the number of cryptographic keys maintained by the cryptographic key component 125. If it is not the nth encrypted digitally signed token, the cryptographic key component 125 can increment a counter i 312 and select the next cryptographic key from the cryptographic keys maintained by the cryptographic key component 125. In this manner, the issuer computing system 115 can create n encrypted digitally signed tokens, each of which corresponds to a verifier, e.g., the verifier computing system 140.

[0040] In further detail of step 316, process 300 may generate a composite token from the encrypted digitally signed tokens. The composite token may be generated by concatenating each of the encrypted digitally signed tokens into a single data structure. An example of this concatenation is shown in FIG. 5. In this exemplary embodiment, 506a-n represent each of the encrypted digitally signed tokens created in step 310, with each of the n digitally signed tokens corresponding to a verifier, such as, for example, one of verifier computing systems 140. In some embodiments, the composite token may be generated by concatenating each of the encrypted digitally signed tokens and the original first party token and timestamp into a single data structure. An embodiment of the result of this concatenation is shown in FIG. 5, where 502 is the original first party token, 504 is a timestamp corresponding to the original first party token, and 506a-n are each of the n encrypted digitally signed tokens. Although FIG. 5 shows the first party token, the timestamp, and the encrypted digitally signed token in a particular order, it should be understood that any of the components may be excluded from the composite token, and any of these elements may appear in any order in the composite token.

[0041] To further explain step 318, the process 300 provides the composite token to the party responsible for generating the first-party token. The process 300 can provide the composite token generated in step 316 to the party that generated the first-party token in step 302. For example, the issuer computing system 115 can transmit the composite token generated by the cryptographic key component 125 to the client computing system 105 via the network 110. In some embodiments, the issuer can provide the composite token to the party responsible for generating the first-party token through a web interface. For example, the issuer computing system 115 can transmit the generated composite token through a web interface, and the client computing system 105 can receive the composite token as part of a browser session.

[0042] 4 is a flow diagram of an example process 400 for verifying the contents of a composite token, according to an example implementation. The process 400 includes steps of receiving a composite token (402), enumerating each of the encrypted digitally signed tokens in the composite token (404), selecting an i-th encrypted digitally signed token (408), decrypting the encrypted digitally signed token to generate a digitally signed token (410), verifying the validity of the digitally signed token to generate a first party token (412), determining whether the encrypted token corresponds to a verifier (414), determining whether i is equal to the number of encrypted digitally signed tokens in the composite token n (416), incrementing a register i (418), ignoring the composite token (420), and processing the valid first party token (422).

[0043] In further detail of step 402, process 400 may receive a composite token comprising one or more encrypted, digitally signed tokens. For example, one of verifier computing systems 140 may receive the composite token from content item network 155. The composite token may include one or more encrypted, digitally signed tokens. The composite token may also include a first-party token and a timestamp. An exemplary schematic diagram of a composite token is shown in FIG. 5. Process 400 may be performed by a party that needs to verify the authenticity of the first-party token. In some embodiments, the composite token may be received as a single data structure. In some other embodiments, the composite token may be received as a series of data structures. For example, a verifier performing process 400 may receive the encrypted, digitally signed tokens one at a time and use them to create the composite token. In some embodiments, the first-party token may include a timestamp corresponding to the creation of the first-party token. In such an embodiment, the first-party token and a timestamp may be included in the composite token.

[0044] In further detail of step 404, process 400 enumerates each of the encrypted digitally signed tokens in the composite token received in step 402. In some embodiments, enumerating each of the encrypted digitally signed tokens includes extracting each encrypted digitally signed token. In such embodiments, the first party token and a timestamp may also be extracted from the composite token. In such embodiments, the verifier performing process 400 may compare the timestamp in the composite token to a predefined value. The verifier performing process 400 may compare the timestamp to check if the composite token is recent and defend against potential replay attacks. In some embodiments, the composite token may be a predefined data structure known to the verifier performing process 400. In such embodiments, the verifier may extract and enumerate each of the encrypted digitally signed tokens based on a known offset in the data structure. In some embodiments, enumerating each of the encrypted digitally signed tokens may include assigning a corresponding numeric value to each of the encrypted digitally signed tokens. For example, with reference to FIG. 5, each of the encrypted digitally signed tokens 506a-n may be assigned a numeric value corresponding to its order in the composite token. Further in this example, 506a may be assigned a value of 1, 506b may be assigned a value of 2, 506c may be assigned a value of 3, and so on. In some embodiments, the verifier performing step 404 may determine the number n of encrypted digitally signed tokens included in the composite token received in step 402.

[0045] Process 400 includes a step of selecting (408) an i-th encrypted digitally signed token. This process step may be performed, for example, by the verifier computing system 115, to decrypt each of the encrypted digitally signed tokens that comprise the composite token. In some embodiments, step 308 may include a received decryption key corresponding to the verifier performing process 400. In some embodiments, the decryption key may be received from a key manager, for example, the key manager computing system 130. In some embodiments, the decryption key is a private key corresponding to the verifier performing process 400. In such an embodiment, the corresponding public key is maintained by an issuer responsible for generating the composite tokens. In a first iteration of the loop created by process 400, step 408 may select a first encrypted digitally signed token (i-th, i=1). It should be understood that one or more encryption keys may be selected in any order.

[0046] In further detail of step 410, process 400 decrypts the selected encrypted digitally signed token to generate a digitally signed token. The verifier may decrypt the selected encrypted digitally signed token in step 408 to generate a digitally signed token. For example, one of the verifier computing systems 140 may perform step 410 of process 400 using the decryption key component 150. To further the example, the decryption key component 150 of the verifier computing system 140 performing process 400 may receive the decryption key from the key manager computing system 130 via the key distribution infrastructure 135. In some embodiments, step 410 of process 400 may include receiving the decryption key from the key manager. In some other embodiments, the decryption key may be maintained or received by the verifier performing process 400 prior to execution of process 400. In some embodiments, the decryption of the encrypted digitally signed token is performed using a decryption algorithm (e.g., elliptic curve, RSA, etc.).

[0047] In further detail of step 412, the digitally signed token is verified to generate a first-party token. In some embodiments, the digitally signed token is verified to generate a hash of the first-party token. The verifier performing process 400 can use a digital signature algorithm (e.g., elliptic curve, DSA, RSA, etc.) to decrypt the content of the digitally signed token generated in step 410, and the decrypted content of the digitally signed token is the first-party token and a timestamp that can be used to verify the validity of the first-party token received in a composite token in step 402 of process 400. In some embodiments, the decrypted content of the digitally signed token is a hash of the first-party token and a timestamp. In some embodiments, the digital signature algorithm uses the public key of the issuer to decrypt the content of the digitally signed token. For example, the key manager computing system 130 can distribute a private key to the issuer computing system 115 and a corresponding public key to the verifier computing system 140. The issuer computing system 115 can use the process 300 to generate a composite key that is provided to the client computing system 105. The client computing system 105 can provide the composite token to the content item network 155, which can provide the composite token to one or more verifier computing systems 140. The verifier computing systems can use process 400 to attempt to process the first party token included in the composite token.In this example, the verifier computing system 140 can use a public key that corresponds to the private key maintained by the issuer computing system 115 to decrypt the digitally signed token in step 412 to generate the first-party token and timestamp, or in some embodiments, to generate a hash of the first-party token and timestamp.

[0048] In further detail of step 414, process 400 determines whether the decrypted content of the digitally signed token corresponds to the verifier executing process 400. For example, a composite token may include multiple encrypted digitally signed tokens. Each encrypted digitally signed token may only be decrypted by authorized verifiers. In this example, authorization is controlled by the distribution of decryption keys. Each decryption key may only successfully decrypt the content of up to one of the encrypted digitally signed tokens included in the composite token. A verifier may determine whether the encrypted digitally signed token corresponds to a verifier executing process 400 by checking whether the digital signature (i.e., the digitally signed token generated in step 410) matches the first party token and timestamp included in the composite token received in step 402. A verifier may check whether the first party token and timestamp generated in step 412 match the first party token and timestamp received as part of the composite token. In some embodiments, step 412 may return a hash of the first party token and timestamp. In such an embodiment, step 414 calculates a hash of the first party token and timestamp received as part of the composite token using a cryptographic hash function (e.g., SHA-1, SHA-256, MD5, etc.) and compares it to the value returned from decrypting the digitally signed token in step 412. If the two values ​​match, the encrypted digitally signed token corresponds to the verifier and the first party token can be processed by the verifier in step 422. If the two values ​​do not match, the verifier performing process 400 can determine (416) whether the current encrypted digitally signed token is the nth encrypted digitally signed token.If not, the verifier executing process 400 may increment counter i 418 and select the next encrypted digitally signed token (408). If the current encrypted digitally signed token is the nth encrypted digitally signed token, none of the encrypted digitally signed tokens in the composite token correspond to the verifier executing process 400 and the composite token is ignored (420).

[0049] In further detail of step 422, the verifier performing process 400 can process the verified first-party token. In some embodiments, the verification process 400 can be performed in real-time without accessing an external server or database. In some embodiments, processing the first-party token includes consuming the data content of the token. For example, the token may include browser information. By verifying the authenticity of the first-party token, the verifier can associate the browser information included in the first-party token with the party responsible for generating the first-party token, e.g., the client computing system 105. The verification process 400 enables verifiers who may need very low latency token authentication a way to verify the authenticity of the first-party token under a predefined time, e.g., 100 milliseconds.

[0050] FIG. 6 illustrates a general architecture of an exemplary computer system 600 (including client computing system 105, issuer computing system 115 and its components such as token signer component 120 and encryption key component 125, verifier computing system 140 and its components such as token verifier component 145 and decryption key component 150, and key manager computing system and its components) that may be employed to implement any of the computer systems discussed herein, according to some implementations. The computer system 600 may be used to provide information over the network 110, the content item network 155, or the key distribution infrastructure 135 for display. The computer system 600 of FIG. 6 comprises one or more processors 620, one or more communication interfaces 605, and one or more output devices 610 (e.g., one or more display units) and one or more input devices 615 communicatively coupled to memory 625. The processor 620 may be included in the client computing system 115. The processor 620 may be included in the issuer computing system 115 or other components of the issuer computing system 115, such as the token signer component 120 and the encryption key component 125. The processor 620 may be included in the verifier computing system 140 or other components of the verifier computing system 140, such as the token verifier component 145 and the decryption key component 150. The processor 620 may be included in the key manager computing system 130 or other components of the key manager computing system 130, such as the key management service 205.

[0051] In the computer system 600 of Figure 6, the memory 625 may comprise any computer-readable storage medium and may store computer instructions, such as processor-executable instructions for implementing various functions described herein for the respective system, as well as any data generated thereby or associated therewith received via a communication interface or input device (if present). With reference to the key manager computing system 130 of Figure 2, the key manager computing system 130 may include a memory 625 for storing, among other things, information associated with the verifier encryption key 220 and the verifier decryption key 225. The processor 620 shown in Figure 6 is used to execute instructions stored in the memory 625, and in so doing may also read from or write to the memory various information processed and / or generated pursuant to execution of the instructions.

[0052] The processor 620 of the computer system 600 shown in FIG. 6 may also be communicatively coupled to and control the communication interface 605 to transmit or receive various information pursuant to execution of instructions. For example, the communication interface 605 may be coupled to a wired or wireless network, bus, or other communication means, thus enabling the computer system 600 to transmit information to or receive information from other devices (e.g., other computer systems). Although not explicitly shown in the system of FIG. 6, one or more communication interfaces facilitate information flow between components of the system 600. In some implementations, the communication interface may be configured (e.g., via various hardware or software components) to provide a website as an access portal to at least some aspects of the computer system 600. Examples of the communication interface 605 include a user interface (e.g., a web page) through which a user can communicate with the data processing system 600.

[0053] 6 may be provided, for example, to allow a user to make manual adjustments, make selections, input data, or otherwise interact with the processor in any of a variety of ways during execution of the instructions. Additional information regarding general computer system architectures that may be used for the various systems discussed herein is provided further herein.

[0054] Implementations of the subject matter and operations described herein can be implemented in digital electronic circuitry, or computer software embodied on tangible media, firmware, or hardware including the structures disclosed herein and their structural equivalents, or one or more combinations thereof. Implementations of the subject matter described herein can be implemented as one or more components of one or more computer programs, i.e., computer program instructions, encoded in a computer storage medium for execution by or to control the operation of a data processing device. The program instructions can be encoded in an artificially generated propagated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal generated to encode information for transmission to an appropriate receiving device for execution by a data processing device. The computer storage medium can be or be included in a computer readable storage device, a computer readable storage substrate, a random or serial access memory array or device, or one or more combinations thereof. Additionally, although a computer storage medium is not a propagated signal, a computer storage medium can include a source or destination of computer program instructions encoded in an artificially generated propagated signal. A computer storage medium may also be, or be contained in, one or more separate physical components or media (eg, multiple CDs, disks, or other storage devices).

[0055] The functionality disclosed herein may be implemented on a smart television module (or connected television module, hybrid television module, etc.) and may include a processing module configured to integrate Internet connectivity with more traditional television programming sources (e.g., received via cable, satellite, over-the-air, or other signals). A smart television module may be physically built into a television or may include separate devices such as a set-top box, Blu-ray or other digital media player, game console, hotel television system, and other companion devices. A smart television module may be configured to allow viewers to search and discover videos, movies, photos, and other content stored on the web, local cable television channels, satellite television channels, or a local hard drive. A set-top box (STB) or set-top unit (STU) may include an information appliance device that includes a tuner and may connect to a television set and an external signal source, converting the signal into content that is then displayed on a television screen or other display device. A smart television module may be configured to provide a home screen or top-level screen that includes icons for a number of different applications, such as a web browser and a number of streaming media services, connected cable or satellite media sources, other web "channels," etc. The smart television module may further be configured to provide an electronic program guide to the user. A companion application to the smart television module may operate on a mobile computing device to provide the user with additional information about available programs, allow the user to control the smart television module, etc. In alternative implementations, this functionality may be implemented on a laptop computer or other personal computer, a smartphone, other mobile phone, a handheld computer, a tablet PC, or other computing device.

[0056] The operations described herein may be implemented as operations performed by a data processing apparatus on data stored in one or more computer-readable storage devices or received from other sources.

[0057] The terms "data processing apparatus", "data processing system", "user device" or "computing device" encompass any kind of apparatus, device and machine for processing data, including, by way of example, the aforementioned programmable processor, computer, system on a chip, or multiple processors, or combinations thereof. The apparatus may include, for example, special purpose logic circuitry, such as an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit). In addition to hardware, the apparatus may also include code that creates an execution environment for the corresponding computer program, such as code constituting a processor firmware, a protocol stack, a database management system, an operating system, a cross-platform runtime environment, a virtual machine, or one or more combinations thereof. The apparatus and execution environment may realize a variety of different computing model infrastructures, such as web services, distributed computing and grid computing infrastructures. The content request component, the content selection component, and the attribute component may include or share one or more data processing apparatus, computing devices, or processors.

[0058] A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, declarative or procedural languages, and can be deployed in any form, such as a stand-alone program or as a module, component, subroutine, object, or other unit suitable for use in a computing environment. A computer program may, but does not have to, correspond to a file in a file system. A program can be stored as part of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, subprograms, or portions of code). A computer program can be deployed to be executed on one computer, or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.

[0059] The processes and logic flows described herein may be performed by one or more programmable processors executing one or more computer programs to perform actions by operating on input data to generate output. The processes and logic flows may also be performed by, and apparatus may be implemented as, special purpose logic circuitry, such as an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).

[0060] Processors suitable for executing computer programs include, by way of example, both general purpose and special purpose microprocessors, as well as any one or more processors of any kind of digital computer. Generally, a processor receives instructions and data from a read-only memory or a random access memory, or both. The essential elements of a computer are a processor for performing actions according to the instructions, and one or more memory devices for storing instructions and data. Generally, a computer also includes, or is operatively coupled to receive data from, or transfer data to, one or more mass storage devices for storing data, such as, for example, magnetic, magneto-optical, or optical disks. However, a computer need not have such devices. Furthermore, a computer can be incorporated in another device, such as, for example, a mobile phone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a global positioning system (GPS) receiver, or a portable storage device (e.g., a universal serial bus (USB) flash drive). Devices suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and memory devices, including, for example, semiconductor memory devices such as EPROM, EEPROM, and flash memory devices, magnetic disks such as internal hard disks or removable disks, magneto-optical disks, and CD-ROM and DVD-ROM disks. The processor and memory may be supplemented by, or incorporated in, special purpose logic circuitry.

[0061] To provide for user interaction, implementations of the subject matter described herein can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube), plasma, or LCD (liquid crystal display) monitor, for displaying information to the user, as well as a keyboard and a pointing device, such as a mouse or trackball, through which the user can provide input to the computer. Other types of devices can be used to provide for user interaction, e.g., feedback provided to the user can include any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback, and input from the user can be received in any form, including acoustic, speech, or tactile input. Additionally, the computer can interact with the user by sending and receiving documents to and from a device used by the user, e.g., by sending a web page to a web browser on the user's client device in response to a request received from the web browser.

[0062] Implementations of the subject matter described herein may be implemented in a computing system that includes a back-end component, e.g., as a data server, or includes a middleware component, such as an application server, or includes a front-end component, e.g., a client computer with a graphical user interface or web browser through which a user can interact with an implementation of the subject matter described herein, or any combination of one or more such back-end, middleware, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication, e.g., a communications network. Examples of communications networks include local area networks ("LANs") and wide area networks ("WANs"), internetworks (e.g., the Internet), and peer-to-peer networks (e.g., ad-hoc peer-to-peer networks).

[0063] Computing systems such as issuer computing system 115, verifier computing system 140, client computing system 105, and key manager computing system 130 may include clients and servers. For example, issuer computing system 115, verifier computing system 140, client computing system 105, and key manager computing system 130 may include one or more servers in one or more data centers or server farms. Clients and servers are typically remote from one another and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to one another. In some implementations, a server sends data (e.g., HTML pages) to a client device (e.g., for the purpose of displaying the data and receiving user input from a user interacting with the client device). Data generated at the client device (e.g., results of user interaction) may be received from the client device at the server.

[0064] Although the specification contains many specific implementation details, these should not be construed as limitations on the scope of the invention or the scope of what may be claimed, but rather as descriptions of features specific to particular implementations of the systems and methods described herein. Certain features described in the context of separate implementations herein may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented separately in multiple implementations or in any suitable subcombination. Furthermore, even if features are described above as operating in a particular combination and initially claimed as such, one or more features from the claimed combination may in some cases be deleted from the combination, and the claimed combination may be subject to subcombinations or variations of the subcombination.

[0065] Similarly, although operations are shown in a particular order in the figures, this should not be understood as requiring that such operations be performed in a particular order, or sequential order, or that all of the illustrated operations be performed, to achieve desirable results. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. Additionally, the processes depicted in the accompanying figures do not necessarily require the particular order, or sequential order, shown to achieve desirable results.

[0066] In certain circumstances, multitasking and parallel processing may be advantageous. Furthermore, the separation of various system components in the above-described implementations should not be understood to require such separation in all implementations, and it should be understood that the described program components and systems may generally be integrated into a single software product or packaged into multiple software products. For example, the token signer component 120 and the cryptographic key component 125 may be part of the issuer computing system 115, a single module, a logical device having one or more processing modules, one or more servers, or part of a search engine.

[0067] Although several exemplary implementations and implementations have now been described, it should be apparent that the foregoing is illustrative and not limiting, and is presented by way of example. In particular, while many of the examples presented herein involve specific combinations of method acts or system elements, those acts and those elements can be combined in other ways to achieve the same purpose. Acts, elements, and functions described only in connection with one implementation are not intended to be excluded from similar roles in other implementations or implementations.

[0068] The phraseology and terminology used herein are for the purpose of description and should not be regarded as limiting. The words "including," "comprising," "having," "containing," "involving," "characterized by," "characterized in that," and variations thereof herein are meant to encompass the items recited thereafter, equivalents thereof, and additional items, as well as alternative implementations that consist exclusively of the items recited thereafter. In one implementation, the systems and methods described herein consist of one, each combination of two or more, or all of the described elements, acts, or components.

[0069] References to implementations or elements or acts of systems and methods referred to in the singular herein can also include implementations that include a plurality of these elements, and references to any implementations or elements or acts herein in the plural can also encompass implementations that include only a single element. References in the singular or plural are not intended to limit the presently disclosed systems or methods, their components, acts, or elements to a singular or plural configuration. References to acts or elements that are based on information, acts, or elements can include implementations where the acts or elements are based, at least in part, on the information, acts, or elements.

[0070] Implementations disclosed herein may be combined with other implementations, and references to "an implementation," "some implementations," "an alternate implementation," "various implementations," "one implementation," and the like are not necessarily mutually exclusive and are intended to indicate that a particular feature, structure, or characteristic described in connection with an implementation may be included in at least one implementation. Such terms as used herein do not necessarily all refer to the same implementation. Any implementation may be combined, inclusively or exclusively, with any other implementation in any manner consistent with the aspects and implementations disclosed herein.

[0071] References to "or" may be construed as inclusive, such that any term described using "or" may refer to either the single, the plural, or all of the described terms.

[0072] When a reference sign is followed by a technical feature in a drawing, the detailed description, or any claim, the reference sign is included solely for the purpose of enhancing the clarity of the drawing, the detailed description, and the claims, and thus, neither the reference sign nor its absence has a limiting effect on the scope of the claim element.

[0073] The systems and methods described herein may be embodied in other specific forms without departing from their characteristics. Although the examples provided herein relate to controlling the display of content of an information resource, the systems and methods described herein may include being applied to other environments. The foregoing implementations are illustrative rather than limiting of the described systems and methods. Thus, the scope of the systems and methods described herein is indicated by the appended claims, rather than the foregoing description, and includes changes that come within the meaning and range of equivalence of the claims. [Explanation of symbols]

[0074] 100 Environment 105 Client Computing Systems 110 Network 115 Issuer Computing Systems 120 Token Signer Component 125 Cryptographic Key Components 130 Key Manager 130 Key Manager Computing System 135 Key Distribution Infrastructure 135 Key Distribution Infrastructure Network 140 Verifier Computing System 145 Token Validator Component 150 Decryption Key Components 155 Content Item Network 205 Key Management Service 210 Token Signer Binary 215 Token Verifier Binary 220 Verifier encryption key 225 Verifier Decryption Key 300 processes 400 processes 600 Computer Systems 600 Data Processing System 605 Communication Interface 610 Output Device 615 Input Devices 620 Processor 625 Memory

Claims

1. 1. A method for providing a signed identity token, comprising: generating, by a party, a first party token associated with the issuer's domain; sending, by the party, to the issuer, the first party token associated with the domain of the issuer; receiving, by the issuer, the first party token associated with the domain of the issuer and creating a timestamp corresponding to the first party token; encrypting, by the issuer, the first party token and a timestamp using a private key of the issuer to create a digitally signed token; creating, by the issuer, a plurality of digitally signed tokens, each of the plurality of digitally signed tokens corresponding to a respective verifier; encrypting each of the plurality of digitally signed tokens using a public key provided by the respective verifier; generating, by the issuer, a composite token comprising each of the plurality of encrypted digitally signed tokens; providing, by the issuer, the composite token to the party responsible for generating the first party token; A method comprising:

2. The method of claim 1 , wherein generating the first party token by the party is based in part on browser information associated with the party.

3. 3. The method of claim 2, wherein receiving by the issuer the first party token and the timestamp associated with the domain of the issuer comprises receiving browser information associated with the party.

4. The method of claim 1 , wherein generating the first party token by the party is based in part on device information associated with the party.

5. 2. The method of claim 1, wherein receiving a request by the issuer for a first party token associated with the domain of the issuer includes receiving a device associated with the party.

6. 2. The method of claim 1, wherein generating the first-party token by the party comprises generating at least a 64-bit high-resolution timestamp corresponding to the request.

7. 1. A method for verifying a user's identity, comprising: receiving, by a verifier, a composite token and a timestamp, the composite token comprising a plurality of encrypted, digitally signed tokens; enumerating, by the verifier, each of the plurality of encrypted, digitally signed tokens within the composite token; determining, by the verifier, which of the enumerated encrypted and digitally signed tokens corresponds to the verifier; decrypting, by the verifier, content of the encrypted signed token corresponding to the verifier using a private key belonging to the verifier to generate a signed token; verifying, by the verifier, the validity of a digital signature of the signed token using a public key corresponding to an issuer to generate a valid first party token; processing, by the verifier, the valid first-party token generated from the signed token in response to the digital signature of the signed token being valid; A method comprising:

8. 8. The method of claim 7, wherein receiving, by the verifier, the composite token and the timestamp comprises receiving a high resolution timestamp of at least 64 bits.

9. 8. The method of claim 7, wherein verifying, by the verifier, the validity of the digital signature of the signed token using a public key corresponding to an issuer to generate a valid first party token includes generating a valid first party device token.

10. 8. The method of claim 7, wherein verifying, by the verifier, the validity of the digital signature of the signed token using a public key corresponding to an issuer to generate a valid first party token includes generating a valid first party browser token.

11. 8. The method of claim 7, wherein determining, by the verifier, which of the enumerated encrypted, digitally signed tokens corresponds to the verifier comprises ignoring the received composite token that does not correspond to any of the enumerated encrypted, digitally signed tokens corresponding to the verifier.

12. 8. The method of claim 7, wherein verifying the validity of the digital signature of the signed token comprises comparing the decrypted token and a timestamp with an unencrypted token included in the composite token.

13. 8. The method of claim 7, wherein verifying the validity of the digital signature of the signed token comprises comparing a timestamp included in the composite token with the timestamp included in the digital signature of the signed token.

14. 1. A system for providing an encrypted and signed identity token in response to a request, comprising: generating, by a party, a first-party token associated with an issuer domain; sending the first party token and a timestamp associated with the domain of the issuer to an issuer; receiving the first party token associated with the domain of the issuer and creating a timestamp; encrypting the first party token corresponding to the request and the timestamp using a private key of the issuer to create a digitally signed token; creating a plurality of digitally signed tokens, each of the plurality of digitally signed tokens corresponding to a respective verifier; encrypting each of the plurality of digitally signed tokens using a public key provided by the respective verifier; generating a composite token comprising each of the plurality of encrypted digitally signed tokens; providing the composite token to a party responsible for initiating the request for the first party token; 16. A system comprising: one or more processors configured to:

15. the one or more processors: generating the first-party token and timestamp associated with the domain of an issuer based on browser information associated with the party; The system of claim 14, further configured to:

16. the one or more processors: receiving the first party token and the timestamp associated with the domain of the issuer, and the browser information associated with the party; The system of claim 15, further configured to:

17. the one or more processors: generating the first-party token and a timestamp associated with the domain of an issuer based on device information associated with the party; The system of claim 14, further configured to:

18. the one or more processors: receiving the first party token and the timestamp associated with the domain of the issuer, and the device information associated with the party; The system of claim 17, further configured to:

19. 15. The system of claim 14, wherein the timestamp generated using the first party token is a high-resolution timestamp of at least 64 bits.

20. 1. A system for verifying the identity of a user, comprising: receiving a composite token and a timestamp, the composite token comprising a plurality of encrypted digitally signed tokens; enumerating each of the plurality of encrypted digitally signed tokens within the composite token; determining which of the enumerated encrypted and digitally signed tokens corresponds to a verifier; decrypting content of the encrypted signed token corresponding to the verifier using a private key belonging to the verifier to generate a signed token; verifying the validity of a digital signature of the signed token using a public key corresponding to the issuer to generate a valid first-party token; in response to the digital signature of the signed token being valid, processing the valid first-party token generated from the signed token; 16. A system comprising: one or more processors configured to:

Citation Information

Patent Citations

  • Enciphering device, decoding device, information sharing device, enciphering method, decoding method, information processing method, and recording medium

    JP1999143359A

  • Electronic signature system, electronic signature method, and electronic signature program

    JP2014022920A

  • Multi-Factor Zero-Knowledge Authentication Using Pairing

    JP2016526342A