A processor may detect a risk on a local machine. The processor may determine that the risk warrants a heightened-level remediation. The processor may connect the local machine to a cloud-based desktop environment. The processor may perform the heightened-level remediation on the local machine. The processor may merge data from the cloud-based desktop environment to the local machine in response to the heightened-level remediation being performed.

A method of configuring a storage system includes the steps of: sending a command to one or more units in the electronic system to enter into an address setting mode; generating a signal for a user to identify units that have entered the address setting mode; and setting up an address for a unit based on an input received from the user.

A communication method and an apparatus are provided herein. The method includes: sending, by a mobility management entity (MME), a track area update (TAU) accept message to a user equipment (UE), the TAU accept message comprising an identifier constructed from at least a resource pool identifier (pool-ID) that identifies a resource pool in a public land mobile network (PLMN), a mobility management entity identifier (MME-ID) that uniquely identifies the MME within the resource pool, and a UE temporary identifier that uniquely identifies the UE within the MME; and receiving, by the MME, a TAU complete message from the UE.

A gateway is provided with configuration management logic to identify a set of configurations corresponding to a deployment of a particular application, and automatically send corresponding configuration data to a set of devices in range of the gateway. Service management logic of the gateway determines that assets on the set of devices correspond to one or more asset abstractions defined for the particular application, where the configuration data is sent to the set of devices based on the assets corresponding to the asset abstractions. Sensor data is received during the deployment as generated by a sensor asset of one of the devices, the sensor data is processed according to service logic of the particular application to generate a result, and actuating data is generated and sent during the deployment to an actuator asset on the set of devices based on the result.

A method implemented by a network element (NE) in a mobile edge cloud (MEC) network, comprising receiving, by the NE, an offloading request message from a client, the offloading request message comprising task-related data describing a task associated with an application executable at the client, determining, by the NE, whether to offload the task to an edge cloud server of a plurality of edge cloud servers distributed within the MEC network based on the task-related data and server data associated with each of the plurality of edge cloud servers, transmitting, by the NE, a response message to the client based on whether the task is offloaded to the edge cloud server.

Technologies for secure I/O data transfer includes a compute device, which includes a processor to execute a trusted application, an input/output (I/O) device, and an I/O subsystem. The I/O subsystem is configured to establish a secured channel between the I/O subsystem and a trusted application running on the compute device, and receive, in response to an establishment of the secured channel, I/O data from the I/O device via an unsecured channel. The I/O subsystem is further configured to encrypt, in response to a receipt of the I/O data, the I/O data using a security key associated with the trusted application that is to process the I/O data and transmit the encrypted I/O data to the trusted application via the secured channel, wherein the secured channel has a data transfer rate that is higher than a data transfer rate of the unsecured channel between the I/O device and the I/O subsystem.

The present disclosure relates to systems and methods for deploying enterprise systems in cloud environments. In one implementation, a system for deploying an enterprise system in a cloud environment may include at least one processor configured to provide: one or more first containers hosting at least one application with at least one enterprise function; one or more second containers hosting at least one microservice configured to activate the at least one enterprise function; at least one application programming interface (API) between the at least one microservice and at least one client; and at least one gateway configured to manage access to the at least one API.

A method for updating software in one or more servers in a managed system includes bootstrapping of shared secrets to secure communication, using an object store with publicly accessible URLs as a mailbox system between a patch agent locally at the managed system and a patch management server located remotely. The object store provides for indirect and asynchronous communication, allowing the patch management server to manage the updates, whereas the patch agent executes the updates. The patch management server keeps track of update results, and when an update is unsuccessful it performs and supports a remediation process. Both the patch agent and the patch management server keep full logs of the update results to allow for auditing.

Disclosed are various examples for enrolling a device in a management service. An enrollment wizard can include a series of user interfaces to facilitate enrollment of a device in the management service. Enrollment data can be obtained from the user and sent to the management service for authentication of the user and device. A user interface object can be instantiated to access a webpage within a user interface of the enrollment wizard for downloading a configuration profile provided by the management service. A user can be redirected to a settings application to install the configuration profile.

Various embodiments herein described are directed to methods, apparatuses and computer program products configured for managing software product feature and version releases in complex and distributed network systems. Various embodiments are directed to systems and network frameworks that are configured to provide controlled release of software features/changes through admin user notification and control interfaces. In some embodiments, a sandbox system environment may be provided to admin users to test and configure upcoming software features/changes. Additional example embodiments provide a release track system that specifies and manages feature release schedules in a complex and multitenant cloud network environment.