Aspects of the disclosure relate to cognitive automation-based engine processing to propagate data across multiple systems via a private network to overcome technical system, resource consumption, and architecture limitations. Data to be propagated can be manually input or extracted from a digital file. The data can be parsed by analyzing for correct syntax, normalized into first through sixth normal forms, segmented into packets for efficient data transmission, validated to ensure that the data satisfies defined formats and input criteria, and distributed into a plurality of data stores coupled to the private network, thereby propagating data without repetitive manual entry. The data may also be enriched by, for example, correcting for any errors or linking with other potentially related data. Based on data enrichment, recommendations of additional target(s) for propagation of data can be identified. Reports may also be generated. The cognitive automation may be performed in real-time to expedite processing.

A communication system includes a first mobile terminal, a second mobile terminal, a smart device, and a router. The first mobile terminal, the second mobile terminal, and the smart device each establish a Wi-Fi link to a Wi-Fi router. The first mobile terminal is configured to manage the smart device. The router performs similarity comparison on first connection information and second connection information based on the first connection information generated when the first mobile terminal is connected to the router and the second connection information generated when the second mobile terminal is connected to the router, for example, a connection time point and connection duration. If a similarity reaches a first threshold, the router sends prompt information to the first mobile terminal. The prompt information is used to prompt whether to share management permission on the smart device with the second mobile terminal.

A cloud-based API metadata management method and system. The cloud-based API metadata management method includes the step of installing an API tool by loading the API tool stored in a database by an API tool installation unit of a cloud server, the step of defining a standard API by the API tool installation unit of the cloud server, and creating an API for each hospital server by an API creation unit, and the step of testing the created API for each hospital server by a test unit of the cloud server, correcting data if there is error data, and storing and distributing the data and API for each hospital server if there is no error data.

Disclosed are systems, servers and methods for a multi-tenant framework that manages and controls operations of software as a service (SaaS) applications and services, and the data and metadata (e.g., files) created, updated and interacted with therefrom. The disclosed framework provides a centralized approach to managing the entitlement and provisioning of SaaS applications on client devices across a variety of channels on a network. The disclosed SaaS framework is configured for management, control, deployment and synchronization between devices, applications, systems and platforms both on-premises (on-prem or local devices/storage) and/or hosted on a network (e.g., a cloud platform, service or platform).

Disclosed are systems, servers and methods for a multi-tenant framework that manages and controls operations of software as a service (SaaS) applications and services, and the data and metadata (e.g., files) created, updated and interacted with therefrom. The disclosed framework provides a centralized approach to managing the entitlement and provisioning of SaaS applications on client devices across a variety of channels on a network. The disclosed SaaS framework is configured for management, control, deployment and synchronization between devices, applications, systems and platforms both on-premises (on-prem or local devices/storage) and/or hosted on a network (e.g., a cloud platform, service or platform).

An Internet of Things (IoT) system is provided. The IoT system includes a plurality of terminal devices, a cloud device, and a human machine interface device. The cloud device is communicatively connected to the terminal devices. The human-machine interface device is communicatively connected to the cloud device via a plurality of first communication channels, and is used for determining a subscription sequence according to a piece of priority information of a plurality of control commands. The human-machine interface device schedules and dynamically subscribes to the first communication channels according to the subscription sequence, so as to transmit the control commands to the cloud device through different first communication channels according to the subscription sequence, so that the cloud device transmits the control commands to the corresponding terminal devices.

An Internet of Things (IoT) system is provided. The IoT system includes a plurality of terminal devices, a cloud device, and a human machine interface device. The cloud device is communicatively connected to the terminal devices. The human-machine interface device is communicatively connected to the cloud device via a plurality of first communication channels, and is used for determining a subscription sequence according to a piece of priority information of a plurality of control commands. The human-machine interface device schedules and dynamically subscribes to the first communication channels according to the subscription sequence, so as to transmit the control commands to the cloud device through different first communication channels according to the subscription sequence, so that the cloud device transmits the control commands to the corresponding terminal devices.

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may receive a first edge application server (EAS) discovery message from an application client that is external to the UE. The UE may transmit a second EAS discovery message to an edge enabler server (EES) based at least in part on the first EAS discovery message. The UE may receive, from the EES, an EAS response message. The EAS response message may indicate a failure of a discovery request associated with the application client or the EAS response message may indicate an EAS associated with the application client. The UE may transmit an indication of the failure of the discovery request or an indication of the EAS to the application client. Numerous other aspects are described.

Example aspects include techniques for accurate and expeditious cloud service health communication to customers. These techniques may include determining that a service health incident has customer impact, the service health incident corresponding to an outage of one or more services of a cloud computing platform, identifying a plurality of customers impacted by the service health incident, and predicting, based on the service health incident and one or more other service health incidents, aggregated incident information identifying a plurality of service health incidents associated with the outage of the one or more services. In addition, the techniques may include identifying the one or more services associated with the service health incident, and transmitting, based at least in part on the aggregated incident information and the one or more services, a health notification to the plurality of customers.

Systems and methods are provided that may be implemented to manage screen sharing of local system windows from a local information handling system to other remote information handling systems by a screen sharing application. In one example, the disclosed systems and methods may be implemented to allow selected local system window/s to continue to remain visible to a local user on the local display screen of a local information handling system that is executing a screen sharing application, while at the same time blocking or otherwise preventing the selected local system window/s from being shared by the screen sharing application across a network with other remote information handling systems, e.g., that are participating with the local information handling system in a common web conference session.