A computer system for verifying vehicle software configuration may be provided. The computer system may include a processor and a non-transitory, tangible, computer-readable storage medium having instructions stored thereon that, in response to execution by the processor, cause the processor to: (1) transmit, to a vehicle computing system, an authentication request including a hash algorithm specification; (2) receive, from the vehicle computing system, a current configuration hash value and a vehicle identifier; (3) retrieve a trusted data block from a memory based upon the vehicle identifier, the trusted data block including a stored configuration hash value and a smart contract code segment; (4) execute the smart contract code segment, the smart contract code segment including a failsafe code segment; and/or (5) transmit the authentication response to the vehicle computing system, and cause the vehicle computing system to execute the failsafe code segment.

A method includes selecting, by one or more servers, a digital component to be presented in an application executed at a client device; obtaining, by the one or more servers, attributes of the digital component, including at least one or more of a destination network location to which the digital component redirects users in response to interaction with the digital component and a reporting network location to which the interaction with the digital component is reported; after selecting the digital component and obtaining the attributes of the digital component, selecting, by the one or more servers and based on the obtained attributes, a config file that specifies a set of operations to be performed by the client device that presents the digital component; and transmitting, to the client device, a payload that includes information specifying the digital component to be presented in the application and the config file that, upon execution by the client device, causes the client device to perform the set of operations specified by the config file.

A playback device includes programming for connecting to a first wireless local area network (WLAN) and storing a first set of network configuration parameters including an identifier of the first WLAN and a first security parameter for the first WLAN. The functions also include disconnecting from the first WLAN, receiving a second set of network configuration parameters including an identifier of a second WLAN and a second security parameter for the second WLAN, and storing the second set of network configuration parameters. The functions also include reconnecting to the first WLAN using the stored first set of network configuration parameters and, after reconnecting to the first WLAN, transmitting, absent user request, the second set of network configuration parameters to at least one other playback device that is connected to the first WLAN for storage on the at least one other playback device that is connected to the first WLAN.

Examples relate to execution of interaction flows. The examples disclosed herein enable obtaining, via a user interface of a local client computing device, an interaction flow that defines an order of execution of a plurality of interaction points and values exchanged among the plurality of interaction points, the plurality of interaction points comprising a first interaction point that indicates an event executed by an application; triggering the execution of the interaction flow; determining whether any of remote client computing devices that are in communication with the local client computing device includes the application; and causing the first interaction point to be executed by the application in at least one of the remote client computing devices that are determined to include the application.

The present invention relates to methods for updating an NSD and an apparatus. One method includes: receiving, by an NFVO, an NSD update request from a transmit end; and sending to an NSD coordinator an NSD update instruction carrying a to-be-updated NSD, so that the NSD coordinator updates the NSD, and the NSD coordinator updates the NSD according to the received NSD update instruction. The other method includes: when receiving a trigger message, obtaining, by an NFVO, an NSD in which a source VNF is located, the trigger message is used to indicate that a status of a VNF is changed to disabled, and the source VNF is a VNF whose status is changed to disabled; and sending to an NSD coordinator an NSD update instruction carrying the NSD, so that the NSD coordinator updates the NSD according to the received NSD update instruction.

The present invention discloses a user portrait based skill package recommendation device, comprising: an acquisition module, used for acquiring and collating the identity information of an intelligent robot user and the interaction information of the user and an intelligent robot, and acquiring the user portrait information of the user; an analysis module, connected to a skill package management platform at a cloud network terminal, and used for analyzing the user portrait information and associating a first skill package on the skill package management platform according to the user portrait information; and a recommendation module, used for acquiring the description information of each first skill package, and pushing the description information to the intelligent robot user.

Enabling interaction with an external service feature via a productivity application is provided. Features in an application are oftentimes an integration of an external or third party service into the application. To enable access to a feature, such as for testing purposes, a secret globally unique identifier (GUID) is input into a designated interface of the application, and a request is sent to enable the external service feature, wherein the request provides an indication to provide resources to interact with the external service feature. The application receives the resources and enables interaction with the external service feature via the productivity application by providing an interface within the productivity application for interacting with the external service feature. Various GUIDs may be used to enable different features. Further, another GUID may be used to disable interaction with the external service feature.

Various systems, mediums, and methods may determine one or more configurations associated with a provider application. For example, a mobile system may determine a request to install a provider application, possibly based on one or more user inputs received by the mobile system. The mobile system may determine other applications installed on the mobile system. The mobile system may determine one or more configurations of the provider application based on the other applications installed. As such, the mobile system may install the provider application to the mobile system based on the one or more configurations determined.

Implementations described herein relate to methods, systems, and computer-readable media to provide an alert based on a release of a software application implemented in a distributed computing system. In some implementations, the method includes receiving, at a processor, an indication of the release of the software application, obtaining a first set of metric values for each metric of a list of metrics for a first time period preceding a time of release of the release, obtaining a second set of metric values for each metric of the list of metrics for a second time period following the time of release, comparing the first set of metric values to the second set of metric values to determine a deviation score, generating an alert based on the deviation score, and transmitting the alert via one of a user interface and a communication channel.

Technologies are described for updating a live system with static changes. According to some examples, changes such as installing and/or removing features may be applied to a cloud based service in live environment without disrupting the service. New software may be patched and installed on an upgraded machine (i.e., server). New features, diagnostics, and language packs may be added. Existing features and certificates may be removed. To accomplish these, new software to be installed and existing software to be removed may be detected. Removal and additions may be performed without preparation and activation of replacement farms.