Abstract: This document describes methods, devices, systems, and means for the provisioning of enrollee Wi-Fi devices to a Wi-Fi network. Many Wi-Fi devices have limited or no user interface capabilities, which presents challenges to connecting and, especially, securely connecting many of these devices to a Wi-Fi network. Techniques are described to enhance the Device Provisioning Protocol to solicit and provide feedback from an enrollee device to indicate band support of the enrollee device and provide the status of the enrollee device after attempting to join a provisioned Wi-Fi network.

Abstract: This document describes methods, devices, systems, and means for the provisioning of enrollee Wi-Fi devices to a Wi-Fi network. Many Wi-Fi devices have limited or no user interface capabilities, which presents challenges to connecting and, especially, securely connecting many of these devices to a Wi-Fi network. Techniques are described to enhance the Device Provisioning Protocol to solicit and provide feedback from an enrollee device to indicate band support of the enrollee device and provide the status of the enrollee device after attempting to join a provisioned Wi-Fi network.

Abstract: In some implementations, after one or more users have each been granted a respective access token allowing access to a resource device, revocation data is received by the resource device. The revocation data indicates that the previously granted access to the resource device should be revoked. For example, the revocation data may indicate (i) a user, role, or permission level for which access is revoked and (ii) a duration that access to the resource device was allowed. After receiving the revocation data, the resource device receives token data derived from an access token that allows access to the resource device. The resource device determines that the access token relies on authorization of the user, role, or permission level indicated by the revocation data, and in response, the resource device denies access.

Abstract: In some implementations, after one or more users have each been granted a respective access token allowing access to a resource device, revocation data is received by the resource device. The revocation data indicates that the previously granted access to the resource device should be revoked. For example, the revocation data may indicate (i) a user, role, or permission level for which access is revoked and (ii) a duration that access to the resource device was allowed. After receiving the revocation data, the resource device receives token data derived from an access token that allows access to the resource device. The resource device determines that the access token relies on authorization of the user, role, or permission level indicated by the revocation data, and in response, the resource device denies access.

Abstract: The disclosed embodiments include computerized methods, systems, and devices, including computer programs encoded on a computer storage medium, for device authentication. For example, the resource device may generate and maintain master access tokens, which may be transmitted to a computing system. The computing system may receive, from a device of an owner of the resource device, data granting a client device limited access to the resource device in accordance with various access restrictions. The computing system may generate and provide to the client device a limited version of the master access token that specifies the access restrictions. The client device may present the local access token to the resource device over a direct wireless connection, and the resource device may verify the token and grant the requested access without communication with the computing system.

Abstract: The disclosed embodiments include computerized methods, systems, and devices, including computer programs encoded on a computer storage medium, for establishing secure wireless communications sessions involving low-power devices. A client device may discover a low-power resource device operating within a wireless network. Upon discovery, the client and resource devices may establish mutual randomness, and establish mutual possession of a shared cryptographic key. The resource device may, in some aspects, provide data proving its knowledge of an authentication tag of a local authentication token held confidentially by the client device. If the resource device proves its knowledge of the client device's authentication tag, the client and resource device may establish a secure communication session and generate session keys for subsequent communications.

Abstract: At a server, during one or more first time periods, event data is received from a first client with respect to one or more events that occur at the first client. The event data is sent by the first client under control of a first application resident on a removable storage device. At the server, during one or more second time periods, event data is received from a second client with respect to one or more events that occur at the second client. The event data is sent by the second client under control of the first application resident on the removable storage device. The first and second time periods are non-overlapping.

Abstract: A print server may include an application manager configured to receive a print job from a user and associate the print job with a printer. The print server may include a presence manager configured to provide a presence code for the print job and the printer, and to receive the presence code from the user in conjunction with a physical presence of the user at the printer, and a print job router configured to release the print job for printing by the printer, based on the receipt of the presence code.

Abstract: At a client, a first application is executed to identify event information with respect to events that occur at the client, including events associated with execution of one or more other applications resident on the client. The first application communicates with a second application, also executing on the client, to transmit the event information to a communications network, wherein the second application and not the first application is in communication with the communications network. In some embodiments, the second application is a browser application. Optionally, the first application installs a browser loadable object in the browser application, and the browser loadable object registers callback information with the first application. Later, the first application uses the callback information to communicate a network request to the browser loadable object.

Abstract: A print server may include an application manager configured to receive a print job from a user and associate the print job with a printer. The print server may include a presence manager configured to provide a presence code for the print job and the printer, and to receive the presence code from the user in conjunction with a physical presence of the user at the printer, and a print job router configured to release the print job for printing by the printer, based on the receipt of the presence code.

Abstract: A loader application and an associated dynamic link library are installed on a client system. Upon a first execution of the loader application, a user authorization to communicate with locations external to the client via a communications network is received. The dynamic link library and not the loader application is auto-updated without requiring additional user authorization. The auto-updating is repeated during one or more executions of the loader application subsequent to the first execution.

Abstract: The embodiments provide a printing system including an application manager, implemented at a cloud print server, configured to receive a print job including encrypted content to be printed by a designated cloud-aware printer, over a network, from an application associated with a device, a print job router, implemented at the cloud print server, configured to route the print job including the encrypted content, over the network, to the designated cloud-aware printer to be decrypted, and a secure format converter configured to receive the print job including decrypted content from the designated cloud-aware printer, convert the print job from a printer-independent format to a printer-specific format associated with the designated cloud-aware printer, and provide the print job having the printer-specific format to the designated cloud-aware printer for printing.

Abstract: A print server may include an access rights manager configured to receive an access request for printer access rights. The print server may also include a customized printer identifier generator configured to generate a customized printer identifier, based on the access request, with the printer access rights associated therewith, and a print job router configured to provide printing in response to receipt of the customized printer identifier and in accordance with the printer access rights.

Abstract: An application manager may receive, from an application utilized at a device at a first location, a print job, the print job identifying a virtual print queue and application content to be printed, the application manager being further configured to store the print job in association with the virtual print queue. A print job router may receive, after the storing and from a mobile device at a second location, a print initiation identifying a printer at the second location and the print job, the print job router being further configured to send the application content to the identified printer, based on the print initiation.

Abstract: Event information with respect to events that occur at a client is identified. At a client and/or a proxy, personal identifiable information (PII) from the event information is removed to produce event data. The event data is transmitted to a server.

Abstract: An application manager may receive, from an application utilized at a device at a first location, a print job, the print job identifying a virtual print queue and application content to be printed, the application manager being further configured to store the print job in association with the virtual print queue. A print job router may receive, after the storing, a print initiation identifying a printer at a second location, the print initiation identifying the print job, including print properties thereof, and originating from the second location. A format converter may generate, from the application content and using the print properties, a printable file in a format printable by the identified printer, for sending to the identified printer by the print job router.

Abstract: An application manager may receive, from an application utilized at a device at a first location, a print job, the print job identifying a virtual print queue and application content to be printed, the application manager being further configured to store the print job in association with the virtual print queue. A print job router may receive, after the storing and from a mobile device at a second location, a print initiation identifying a printer at the second location and the print job, the print job router being further configured to send the application content to the identified printer, based on the print initiation.

Abstract: A printer may include a registration requester configured to receive an initiation request from a user to initiate a registration of the printer, and further configured to send a registration request to a cloud print service over a network. The printer may include a claim facilitator configured to receive a registration response from the cloud print service over the network, the registration response including a claim code, and further configured to provide, using printer functionality, the claim code to the user. The printer also may include an authentication manager configured to request an authentication credential issued by the cloud print service in response to a matching of the printer with a user account of the user within the cloud print service, the matching based on a receipt of the claim code from the user at the cloud print service, and further configured to receive and store the authentication credential at the printer.

Abstract: A print server may include an anonymous printer registration module configured to receive, at a cloud print service, a registration request from a printer over a network and return a registration response to the printer over the network. The anonymous printer registration module may include a claim code provider configured to provide a claim code included within the registration response to the printer over the network, wherein the printer is configured to provide the claim code to a user of the printer, and a printer matcher configured to receive the claim code from the user over the network and match a user account of the user within the cloud print service with the printer, in response to the receipt of the claim code from the user.

Abstract: The embodiments provide a print server including at least one processor, and a non-transitory computer-readable storage medium including instructions executable by the at least one processor. The instructions are configured to implement an application manager configured to receive a print request over a network from an application associated with a device, and a printer searcher configured to determine printer search criteria associated with the print request, search a plurality of available printers associated with a user account of a user of the application based on the determined printer search criteria, and determine a subset of available printers based on the search. The application manager is configured to provide, over the network, a print dialog to the user of the application in response to the print request, where the print dialog may be configured to provide a list of the subset of available printers.