Abstract: The techniques herein are directed generally to a “zero-knowledge” data management network. Users are able to share verifiable proof of data and/or identity information, and businesses are able to request, consume, and act on the data—all without a data storage server or those businesses ever seeing or having access to the raw sensitive information (where server-stored data is viewable only by the intended recipients, which may even be selected after storage). In one embodiment, source data is encrypted with a source encryption key (e.g., source public key), with a rekeying key being an encrypting combination of a source decryption key (e.g., source private key) and a recipient's public key. Without being able to decrypt the data, the storage server can use the rekeying key to re-encrypt the source data with the recipient's public key, to then be decrypted only by the corresponding recipient using its private key, accordingly.

Abstract: The techniques herein are directed generally to a “zero-knowledge” data management network. Users are able to share verifiable proof of data and/or identity information, and businesses are able to request, consume, and act on the data—all without a data storage server or those businesses ever seeing or having access to the raw sensitive information (where server-stored data is viewable only by the intended recipients, which may even be selected after storage). In one embodiment, source data is encrypted with a source encryption key (e.g., source public key), with a rekeying key being an encrypting combination of a source decryption key (e.g., source private key) and a recipient's public key. Without being able to decrypt the data, the storage server can use the rekeying key to re-encrypt the source data with the recipient's public key, to then be decrypted only by the corresponding recipient using its private key, accordingly.

Abstract: The techniques herein are directed generally to personalized secure communication session management, such as for virtual private networks (VPNs). In one embodiment, a user is authenticated at a client device to verify that the user is present at the client device and authorized to access one or more secured resources, and in response, a secure communication session is established for the client device to access the secured resources. At a later time during the secure communication session, it is determined whether the user is still authenticated at the client device, such that if so, access to the one or more secured resources is maintained on the secure communication session, or else access is restricted to the one or more secured resources (e.g., the session is terminated, or access is otherwise limited).

Abstract: According to one or more of the embodiments herein, systems and techniques for satellite relaying for geolocation and mitigation of Global Navigation Satellite System (GNSS) denial are provided.

Abstract: The techniques herein are directed generally to managing hotel guest departures within an automated guest satisfaction and services scheduling system. In particular, in the present disclosure, for instance, the techniques herein provide a method and system to allow guests to easily manage and schedule their departure (check-out) through the interactive interface. The interface may include various modal notifications regarding check-out options, such as requesting the guest to enter their departure time preferences. The system also facilitates notification of a housekeeping services scheduler, and further allows the hotel to incentivize or monetize different check-out times.

Abstract: The techniques herein are directed generally to a “zero-knowledge” data management network. Users are able to share verifiable proof of data and/or identity information, and businesses are able to request, consume, and act on the data—all without a data storage server or those businesses ever seeing or having access to the raw sensitive information (where server-stored data is viewable only by the intended recipients, which may even be selected after storage). In one embodiment, source data is encrypted with a source encryption key (e.g., source public key), with a rekeying key being an encrypting combination of a source decryption key (e.g., source private key) and a recipient's public key. Without being able to decrypt the data, the storage server can use the rekeying key to re-encrypt the source data with the recipient's public key, to then be decrypted only by the corresponding recipient using its private key, accordingly.

Abstract: The techniques herein are directed generally to a “zero-knowledge” data management network. Users are able to share verifiable proof of data and/or identity information, and businesses are able to request, consume, and act on the data-all without a data storage server or those businesses ever seeing or having access to the raw sensitive information (where server-stored data is viewable only by the intended recipients, which may even be selected after storage). In one embodiment, source data is encrypted with a source encryption key (e.g., source public key), with a rekeying key being an encrypting combination of a source decryption key (e.g., source private key) and a recipient's public key. Without being able to decrypt the data, the storage server can use the rekeying key to re-encrypt the source data with the recipient's public key, to then be decrypted only by the corresponding recipient using its private key, accordingly.

Abstract: The techniques herein are directed generally to a “zero-knowledge” data management network. Users are able to share verifiable proof of data and/or identity information, and businesses are able to request, consume, and act on the data-all without a data storage server or those businesses ever seeing or having access to the raw sensitive information (where server-stored data is viewable only by the intended recipients, which may even be selected after storage). In one embodiment, source data is encrypted with a source encryption key (e.g., source public key), with a rekeying key being an encrypting combination of a source decryption key (e.g., source private key) and a recipient's public key. Without being able to decrypt the data, the storage server can use the rekeying key to re-encrypt the source data with the recipient's public key, to then be decrypted only by the corresponding recipient using its private key, accordingly.

Abstract: Satellite relaying for geolocation and mitigation of GNSS denial are provided, where a method comprises: receiving, by a processing device from a communication satellite along a communication path, a message initiated at a transmission time by a transmitting device, the communication path having a target device with an unknown distance to the communication satellite; determining, by the device, a reception time upon receiving the message; determining, by the device, a time of travel of the message associated with only traversal of a portion of the communication that is path between the communication satellite and the target device based on a difference between the transmission time and the reception time; calculating, by the device, a distance between the communication satellite and the target device based on the time of travel; and performing, by the device, one or more actions based on the distance between the communication satellite and the target device.

Abstract: The techniques herein are directed generally to a “zero-knowledge” data management network. Users are able to share verifiable proof of data and/or identity information, and businesses are able to request, consume, and act on the data—all without a data storage server or those businesses ever seeing or having access to the raw sensitive information (where server-stored data is viewable only by the intended recipients, which may even be selected after storage). In one embodiment, source data is encrypted with a source encryption key (e.g., source public key), with a rekeying key being an encrypting combination of a source decryption key (e.g., source private key) and a recipient's public key. Without being able to decrypt the data, the storage server can use the rekeying key to re-encrypt the source data with the recipient's public key, to then be decrypted only by the corresponding recipient using its private key, accordingly.

Abstract: The techniques herein are directed generally to a “zero-knowledge” data management network. Users are able to share verifiable proof of data and/or identity information, and businesses are able to request, consume, and act on the data—all without a data storage server or those businesses ever seeing or having access to the raw sensitive information (where server-stored data is viewable only by the intended recipients, which may even be selected after storage). In one embodiment, source data is encrypted with a source encryption key (e.g., source public key), with a rekeying key being an encrypting combination of a source decryption key (e.g., source private key) and a recipient's public key. Without being able to decrypt the data, the storage server can use the rekeying key to re-encrypt the source data with the recipient's public key, to then be decrypted only by the corresponding recipient using its private key, accordingly.

Abstract: Satellite echoing for geolocation and mitigation of Global Navigation Satellite System (GNSS) denial are provided herein, where an example method comprises: transmitting, by a processing device, an echo message along a communication path having a communication satellite and a target device with an unknown distance to the communication satellite; receiving, by the processing device, a return of the echo message from the communication satellite over the communication path; determining, by the processing device, a time of travel of the echo message associated with only a single traversal of a portion of the communication path that is between the communication satellite and the target device; calculating, by the processing device, a distance between the communication satellite and the target device based on the time of travel; and performing, by the processing device, one or more actions based on the distance between the communication satellite and the target device.

Abstract: The techniques herein are directed generally to a “zero-knowledge” data management network. Users are able to share verifiable proof of data and/or identity information, and businesses are able to request, consume, and act on the data—all without a data storage server or those businesses ever seeing or having access to the raw sensitive information (where server-stored data is viewable only by the intended recipients, which may even be selected after storage). In one embodiment, source data is encrypted with a source encryption key (e.g., source public key), with a rekeying key being an encrypting combination of a source decryption key (e.g., source private key) and a recipient's public key. Without being able to decrypt the data, the storage server can use the rekeying key to re-encrypt the source data with the recipient's public key, to then be decrypted only by the corresponding recipient using its private key, accordingly.

Abstract: Satellite relaying for geolocation and mitigation of GNSS denial are provided, where a method comprises: receiving, by a processing device from a communication satellite along a communication path, a message initiated at a transmission time by a transmitting device, the communication path having a target device with an unknown distance to the communication satellite; determining, by the device, a reception time upon receiving the message; determining, by the device, a time of travel of the message associated with only traversal of a portion of the communication that is path between the communication satellite and the target device based on a difference between the transmission time and the reception time; calculating, by the device, a distance between the communication satellite and the target device based on the time of travel; and performing, by the device, one or more actions based on the distance between the communication satellite and the target device.

Abstract: Satellite relaying for geolocation and mitigation of GNSS denial are provided, where a method comprises: receiving, by a processing device from a communication satellite along a communication path, a message initiated at a transmission time by a transmitting device, the communication path having a target device with an unknown distance to the communication satellite; determining, by the device, a reception time upon receiving the message; determining, by the device, a time of travel of the message associated with only traversal of a portion of the communication that is path between the communication satellite and the target device based on a difference between the transmission time and the reception time; calculating, by the device, a distance between the communication satellite and the target device based on the time of travel; and performing, by the device, one or more actions based on the distance between the communication satellite and the target device.

Abstract: According to one or more of the embodiments herein, systems and techniques for multi-system-based detection and mitigation of Global Navigation Satellite System (GNSS) spoofing are provided. In one embodiment, a method comprises: obtaining a first location of an object from a primary location determination hardware system; obtaining a second location of the object from a secondary location determination hardware system; determining a distance difference between the first location and the second location; determining whether the distance difference between the first location and the second location is acceptable based on a threshold distance; and initiating one or more mitigation actions in response to the distance difference between the first location and the second location being unacceptable.

Abstract: The techniques herein are directed generally to a “zero-knowledge” data management network. Users are able to share verifiable proof of data and/or identity information, and businesses are able to request, consume, and act on the data—all without a data storage server or those businesses ever seeing or having access to the raw sensitive information (where server-stored data is viewable only by the intended recipients, which may even be selected after storage). In one embodiment, source data is encrypted with a source encryption key (e.g., source public key), with a rekeying key being an encrypting combination of a source decryption key (e.g., source private key) and a recipient's public key. Without being able to decrypt the data, the storage server can use the rekeying key to re-encrypt the source data with the recipient's public key, to then be decrypted only by the corresponding recipient using its private key, accordingly.

Abstract: The techniques herein are directed generally to a “zero-knowledge” data management network. Users are able to share verifiable proof of data and/or identity information, and businesses are able to request, consume, and act on the data—all without a data storage server or those businesses ever seeing or having access to the raw sensitive information (where server-stored data is viewable only by the intended recipients, which may even be selected after storage). In one embodiment, source data is encrypted with a source encryption key (e.g., source public key), with a rekeying key being an encrypting combination of a source decryption key (e.g., source private key) and a recipient's public key. Without being able to decrypt the data, the storage server can use the rekeying key to re-encrypt the source data with the recipient's public key, to then be decrypted only by the corresponding recipient using its private key, accordingly.

Abstract: The techniques herein are directed generally to a “zero-knowledge” data management network. Users are able to share verifiable proof of data and/or identity information, and businesses are able to request, consume, and act on the data—all without a data storage server or those businesses ever seeing or having access to the raw sensitive information (where server-stored data is viewable only by the intended recipients, which may even be selected after storage). In one embodiment, source data is encrypted with a source encryption key (e.g., source public key), with a rekeying key being an encrypting combination of a source decryption key (e.g., source private key) and a recipient's public key. Without being able to decrypt the data, the storage server can use the rekeying key to re-encrypt the source data with the recipient's public key, to then be decrypted only by the corresponding recipient using its private key, accordingly.

Abstract: Embodiments herein provide for a dosage reminder indicator for containers, allowing a user to align a dosage reminder (e.g., “last” or “next”) with timing indicators (e.g., days, times). In one embodiment, an inner dial has first engaging members and an outer ring has second engaging members mating with the first engaging members, where a dosage reminder indicator and a plurality of dosage timing indicators are opposingly located on either the inner dial or outer ring. The inner dial and the outer ring are rotatably engaged with respect to each other such that the dosage reminder indicator points to any selected one of the plurality of dosage timing indicators in a secured position (when the first and second engaging members are mated), where rotation is permitted based on user-applied force to disengage mating of the first and second engaging members, while the inner dial and the outer ring remain rotatably engaged.