Abstract: A method of soliciting and receiving a bid for placement of an ad on a web browser. The method includes receiving a request from the browser to serve an ad, the request from the browser including information describing browsing activity of the browser. The method also includes soliciting a bid from the at least one advertiser for placement of an ad on the browser; receiving at least one bid from the at least one advertiser for placement of an ad on the browser; evaluating the at least one bid; and placing an ad from at least one advertiser on the browser based on the evaluation of the at least one bid.

Abstract: A graphical user interface for setting parameters related to ad delivery, including a first window for logging into a web interface; a second window for setting at least one of a basic or advanced configuration policies; a third window for displaying at least one of a case study, a budget report, a traffic report, a data mining report, and an ad denial report.

Abstract: A method for transferring state information between a client device and a server, the client device being configured to select content, and the server having a memory module and being configured to store referenced content and to transmit referenced content to at least one client device. The method includes receiving a request on the server from the client device, wherein the request includes the state information from the client device; detecting whether the state information has previously been received by the server; updating the state information; and transmitting a response including the updated state information to the client device.

Abstract: In an infrastructure in which some of a plurality of entities provide cryptographically supported services, a method of registering a subscriber entity of a plurality of entities at a principal entity of a plurality of entities, the method comprising the subscriber entity requesting service from the principal entity by sending a request message to a registrar entity of the plurality of entities; the registrar entity verifying the subscriber entity and forwarding the request for service to the principal entity; the principal entity storing the forwarded request and transmitting an acknowledgement message to the registrar entity, the acknowledgement stating acceptance and authentication/authorization information that the subscriber entity requires for the requested service; and the registrar entity verifying the authenticity of the received acknowledgement message, and, if correct, forwarding the acknowledgement message to the subscriber entity.

Abstract: In an infrastructure in which some of a plurality of entities provide cryptographically supported services, a method of registering a subscriber entity of a plurality of entities at a principal entity of a plurality of entities, the method comprising the subscriber entity requesting service from the principal entity by sending a request message to a registrar entity of the plurality of entities; the registrar entity verifying the subscriber entity and forwarding the request for service to the principal entity; the principal entity storing the forwarded request and transmitting an acknowledgement message to the registrar entity, the acknowledgement stating acceptance and authentication/authorization information that the subscriber entity requires for the requested service; and the registrar entity verifying the authenticity of the received acknowledgement message, and, if correct, forwarding the acknowledgement message to the subscriber entity.

Abstract: A system and method for performing an electronic transaction, including registration, audit and trusted recovery features. A transaction request message is received from a registered user that includes an unblinded validated certificate, and a blinded unvalidated certificate. If the unblinded validated certificate is determined to be legitimate, then a transaction can be performed, and the blinded unvalidated certificate is validated to obtain a blinded, validated certificate that is sent to the user. An audit protocol can be used to further verify the legitimacy of the transaction request message, and a user can recover from a broken connection by replaying a protocol run.