Abstract: A computer-implemented system for streamlining encryption payload of a card transaction from a transaction code transaction via a merchant inside a restricted computer network firewall. A wallet application stores data of a payment device, and the wallet application retrieves information of a merchant and a transaction via a transaction code. In response to the retrieved information, the wallet application generates an encrypted payload. The wallet application transmits the encrypted payload to a payment facilitator within the restricted computer network firewall. After decryption of the encrypted payload, the payment facilitator transmits a decrypted payload in one payment packet to the payment processing server outside the restricted computer network firewall.

Abstract: A disconnection mechanism, for engaging or disengaging a fixed component and a movable component arranged on a first shaft extending in a first direction. The disconnection mechanism includes a shift fork, connected to the movable component, and constructed to be able to reciprocate linearly in the first direction, so that the movable component is engaged with or disengaged from the fixed component. An actuator includes an output end which rotates about a rotation axis of the actuator at a distance from the rotation axis. A drive rod has a first end rotatably connected to the output end and a second end rotatably connected to the shift fork, so that the output end, when rotating, is able to drive the shift fork to reciprocate linearly.

Abstract: Implementations of the present specification provide a digital item transfer interaction processing method and apparatus.

Abstract: A computer-implemented system for streamlining encryption payload of a card transaction from a transaction code transaction via a merchant inside a restricted computer network firewall. A wallet application stores data of a payment device, and the wallet application retrieves information of a merchant and a transaction via a transaction code. In response to the retrieved information, the wallet application generates an encrypted payload. The wallet application transmits the encrypted payload to a payment facilitator within the restricted computer network firewall. After decryption of the encrypted payload, the payment facilitator transmits a decrypted payload in one payment packet to the payment processing server outside the restricted computer network firewall.

Abstract: Methods, systems, and devices are provided for authenticating API messages using PKI-based authentication techniques. A client system can generate a private/public key pair associated with the client system and sign an API message using the private key of the private/public key pair and a PKI-based cryptographic algorithm, before sending the signed API message to a server system. The server system (e.g., operated by a service provider) can authenticate the incoming signed API message using a proxy authenticator located in less trusted zone (e.g., a perimeter network) of the server system. In particular, the proxy authenticator can be configured to verify the signature of the signed API message using the public key corresponding to the private key and the same cryptographic algorithm. The authenticated API message can then be forwarded to a more trusted zone (e.g., an internal network) of the server system for further processing.

Abstract: A computer-implemented system for streamlining encryption payload of a card transaction from a transaction code transaction via a merchant inside a restricted computer network firewall. A wallet application stores data of a payment device, and the wallet application retrieves information of a merchant and a transaction via a transaction code. In response to the retrieved information, the wallet application generates an encrypted payload. The wallet application transmits the encrypted payload to a payment facilitator within the restricted computer network firewall. After decryption of the encrypted payload, the payment facilitator transmits a decrypted payload in one payment packet to the payment processing server outside the restricted computer network firewall.

Abstract: Methods, systems, and devices are provided for authenticating API messages using PKI-based authentication techniques. A client system can generate a private/public key pair associated with the client system and sign an API message using the private key of the private/public key pair and a PKI-based cryptographic algorithm, before sending the signed API message to a server system. The server system (e.g., operated by a service provider) can authenticate the incoming signed API message using a proxy authenticator located in less trusted zone (e.g., a perimeter network) of the server system. In particular, the proxy authenticator can be configured to verify the signature of the signed API message using the public key corresponding to the private key and the same cryptographic algorithm. The authenticated API message can then be forwarded to a more trusted zone (e.g., an internal network) of the server system for further processing.

Abstract: Methods, systems, and devices are provided for authenticating API messages using PKI-based authentication techniques. A client system can generate a private/public key pair associated with the client system and sign an API message using the private key of the private/public key pair and a PKI-based cryptographic algorithm, before sending the signed API message to a server system. The server system (e.g., operated by a service provider) can authenticate the incoming signed API message using a proxy authenticator located in less trusted zone (e.g., a perimeter network) of the server system. In particular, the proxy authenticator can be configured to verify the signature of the signed API message using the public key corresponding to the private key and the same cryptographic algorithm. The authenticated API message can then be forwarded to a more trusted zone (e.g., an internal network) of the server system for further processing.

Abstract: Methods, systems, and devices are provided for authenticating API messages using PKI-based authentication techniques. A client system can generate a private/public key pair associated with the client system and sign an API message using the private key of the private/public key pair and a PKI-based cryptographic algorithm, before sending the signed API message to a server system. The server system (e.g., operated by a service provider) can authenticate the incoming signed API message using a proxy authenticator located in less trusted zone (e.g., a perimeter network) of the server system. In particular, the proxy authenticator can be configured to verify the signature of the signed API message using the public key corresponding to the private key and the same cryptographic algorithm. The authenticated API message can then be forwarded to a more trusted zone (e.g., an internal network) of the server system for further processing.

Abstract: Methods, systems, and devices are provided for authenticating API messages using PKI-based authentication techniques. A client system can generate a private/public key pair associated with the client system and sign an API message using the private key of the private/public key pair and a PKI-based cryptographic algorithm, before sending the signed API message to a server system. The server system (e.g., operated by a service provider) can authenticate the incoming signed API message using a proxy authenticator located in less trusted zone (e.g., a perimeter network) of the server system. In particular, the proxy authenticator can be configured to verify the signature of the signed API message using the public key corresponding to the private key and the same cryptographic algorithm. The authenticated API message can then be forwarded to a more trusted zone (e.g., an internal network) of the server system for further processing.

Abstract: Methods, systems, and devices are provided for authenticating API messages using PKI-based authentication techniques. A client system can generate a private/public key pair associated with the client system and sign an API message using the private key of the private/public key pair and a PKI-based cryptographic algorithm, before sending the signed API message to a server system. The server system (e.g., operated by a service provider) can authenticate the incoming signed API message using a proxy authenticator located in less trusted zone (e.g., a perimeter network) of the server system. In particular, the proxy authenticator can be configured to verify the signature of the signed API message using the public key corresponding to the private key and the same cryptographic algorithm. The authenticated API message can then be forwarded to a more trusted zone (e.g., an internal network) of the server system for further processing.

Abstract: Methods, systems, and devices are provided for authenticating API messages using PKI-based authentication techniques. A client system can generate a private/public key pair associated with the client system and sign an API message using the private key of the private/public key pair and a PKI-based cryptographic algorithm, before sending the signed API message to a server system. The server system (e.g., operated by a service provider) can authenticate the incoming signed API message using a proxy authenticator located in less trusted zone (e.g., a perimeter network) of the server system. In particular, the proxy authenticator can be configured to verify the signature of the signed API message using the public key corresponding to the private key and the same cryptographic algorithm. The authenticated API message can then be forwarded to a more trusted zone (e.g., an internal network) of the server system for further processing.

Abstract: Methods, systems, and devices are provided for authenticating API messages using PKI-based authentication techniques. A client system can generate a private/public key pair associated with the client system and sign an API message using the private key of the private/public key pair and a PKI-based cryptographic algorithm, before sending the signed API message to a server system. The server system (e.g., operated by a service provider) can authenticate the incoming signed API message using a proxy authenticator located in less trusted zone (e.g., a perimeter network) of the server system. In particular, the proxy authenticator can be configured to verify the signature of the signed API message using the public key corresponding to the private key and the same cryptographic algorithm. The authenticated API message can then be forwarded to a more trusted zone (e.g., an internal network) of the server system for further processing.

Abstract: Contextual data, which may describe user activity, preferences and/or a device status, is aggregated from a number of devices and/or resources. Program information is aggregated from several resources including an on-demand resource and other resources, such as a broadcast resource. Configurations disclosed herein utilize the contextual data to select content items to be added to a cross-platform programming playlist, which is configured to invoke viewing sessions from on-demand resources as well as other devices, such as a digital video recorder (DVR). Configurations disclosed herein also utilize the contextual data to determine if the selected content items are to be recorded by a device or accessed from an on-demand resource. In some configurations, recorded content items are deleted from storage depending on the availability of alternate resources sharing the recorded content items and/or other contextual information.

Abstract: Technologies are described herein for providing contextually aware management of resources. Recorded content items are deleted from or added to a storage device depending on the availability of alternate resources sharing the content items and/or other contextual information. For example, if a storage device of a DVR has reached a threshold with respect to a storage capacity and/or other conditions develop, configurations disclosed herein analyze the content items stored in the DVR to determine if the content items are provided by an on-demand resource. If one or more stored content items are available on at least one on-demand resource, the system may delete the one or more content items from the DVR and generate a link to access the one or more content items from the on-demand resource. The link and a description of the one or more content items may then be added to the cross-platform programming playlist.

Abstract: An electronic marketplace includes a plurality of video game applications available for purchase. For each of the plurality of video game applications, the electronic marketplace may display a tile identifying the video game application, a payment object for initiating a purchase of the video game application, and a preview object to initiate viewing of a live broadcast of active gameplay of the video game application.

Abstract: Disclosed are a method and a device for detecting an object in a display area. The method comprises a step of generating a first image prepared to be displayed; a step of displaying the generated first image on a screen; a step of capturing a second image of the screen including the display area; and a step of comparing the generated first image with the captured second image so as to detect the object in the display area.

Abstract: Disclosed are a method and a device for detecting an object in a display area. The method comprises a step of generating a first image prepared to be displayed; a step of displaying the generated first image on a screen; a step of capturing a second image of the screen including the display area; and a step of comparing the generated first image with the captured second image so as to detect the object in the display area.

Abstract: A human machine interface system for use in computer systems in mobile and non-mobile clients. The system divides functions required to provide a user interface into a user interface unit that is a thin client with a rendering engine for creating user interfaces from user interface descriptors and a hosting platform with an interface application that processes user input and transmits presentation instructions to the rendering engine, which executes the instructions to alter the user interface. A set of rules for creating user interface descriptors and methods and protocols for communicating between the hosting platform and the user interaction unit are provided along with a provisioning system that enhances initial creation of user interfaces and the provisioning of interfaces to clients in a manner that facilitates compatibility and consistency among clients using interfaces while allowing flexibility to make unique or branded interfaces by providing sets of vendor signatures.

Abstract: A user interfacing electronic system and method are provided for communicating data between a human machine interface and a host platform in a vehicle. The system includes a host platform having application software for executing an application for an electronic device, and a human machine interface for receiving user inputs and providing outputs to a user. A data communication link allows the communication of data between the host platform and the human machine interface. The system further has user interface markup language for communicating messages on the communication link between the host platform and human machine interface, including messages to deliver user inputs and outputs.