Patent classifications
H04L67/34
Methods, systems, and devices for dynamically modeling and grouping endpoints for edge networking
Various embodiments described herein disclose an endpoint modeling and grouping management system that can collect data from endpoint computer devices in a network. In some embodiments, agents installed on the endpoints can collect real-time information at the kernel level providing the system with deep visibility. In some embodiments, the endpoint modeling and grouping management system can identify similarities in behavior in response to assessing the data collected by the agents. In some embodiments, the endpoint modeling and grouping management system can dynamically model groups such as logical groups, and cluster endpoints based on the similarities and/or differences in behavior of the endpoints. In some embodiments, the endpoint modeling and grouping management system transmits the behavioral models to the agents to allow the agents to identify anomalies and/or security threats autonomously.
System and method for autopartitioning and processing electronic resources
Embodiments of the present invention provide a system for autopartitioning and processing electronic resources. The system is configured for receiving one or more electronic resources from one or more third party systems, determining that the one or more electronic resources match one or more predetermined characteristics, moving the one or more electronic resources that match the one or more predetermined characteristics into a first pipeline and processing the one or more electronic resources.
Provenance audit trails for microservices architectures
An apparatus to facilitate provenance audit trails for microservices architectures is disclosed. The apparatus includes one or more processors to: obtain, by a microservice of a service hosted in a datacenter, provisioned credentials for the microservice based on an attestation protocol; generate, for a task performed by the microservice, provenance metadata for the task, the provenance metadata including identification of the microservice, operating state of at least one of a hardware resource or a software resource used to execute the microservice and the task, and operating state of a sidecar of the microservice during the task; encrypt the provenance metadata with the provisioned credentials for the microservice; and record the encrypted provenance metadata in a local blockchain of provenance metadata maintained for the hardware resource executing the task and the microservice.
Method, apparatus, and computer program product for installing third party applications requiring variable host address identification in a group-based communication system
Embodiments of the present disclosure provide methods, systems, apparatuses, and computer program products that provide for an improved and more efficient system of networked computing devices. The embodiments disclose an apparatus and system that enable client devices to install integrations of a third party application that supports variable host address identification. The apparatus and methods further enable a user of the client device to modify the host address identification associated with an installed integration. In this manner, the group-based communication system establishes communication links with network locations that vary from integration to integration and that may vary over time. To implement the invention, the group-based communication system supports the creation of a blueprint application, with an associated blueprint row that serves as the basis from which a plurality of differing integrations are generated. Further, the blueprint row stores variable host address identifications. The reduced number of data structures that result from supporting variable host address identifications increases system efficiency and reduces infrastructure requirements.
Building management system with adaptive edge processing
Systems and methods for building management utilizing adaptive edge processing are disclosed. The building system can store gateway components on storage devices. The gateway components can facilitate communication with a cloud platform and facilitate communication with a physical building device. The building system can identify a computing system of the building that is in communication with the physical building device. The physical building device can store one or more data samples. The building system can deploy the gateway components to the computing system responsive to identifying that the computing system is in communication with the physical building device. The gateway components can cause the computing system to communicate with the physical building device to receive the one or more data samples and cause the computing system to communicate the one or more data samples to the cloud platform.
Data collection configuration file generation
A network monitoring system may receive a configuration request to generate a configuration file associated with collecting feature or debug data associated with a feature, hardware, or software associated with a network device. The network monitoring system may determine a command profile associated with the feature, hardware, or software that identifies a set of commands associated with obtaining the feature or debug data from the network device. The network monitoring system may determine respective parameters of one or more commands of the set of commands. The network monitoring system may determine, based on the respective parameters, respective arguments of the one or more commands. The network monitoring system may generate the configuration file based on the respective arguments and may perform an action associated with the configuration file to permit the configuration file to be used to collect the feature or debug data from the network device.
Automated port configuration management in a service mesh
Systems, methods and/or computer program products for managing and dynamically automating service mesh communications between microservices, eliminating unnecessary exposure of microservice ports and increasing security between microservices of the service mesh. The control plane collects data describing communications between microservices and tracks the frequency at which microservices communicate. Collected data is fed to machine learning models which outputs a forecast predicting future communication interactions between microservices. Using the predicted requirements for facilitating communications between microservices of the service mesh, an allowed list of communications can be generated describing the microservices allowed to send and receive communications, duration of communications allowed, when such communications are allowed, and the ports that will be used for facilitating the communication between microservices. Administrators of the service mesh may manually override the one or more approved aspects of the dynamically generated allowed list configured automatically by the service mesh.
Master Agent and Distributed Agent Architecture for Vehicles
A system and method for an eSync update agent is provided. The update agent can communicate with an eSync client, which receives software updates from an external server and transmits the software updates to the update agent. In turn, the update agent may use its programming to determine one or more aspects of the software update, such as when or whether to perform the software update on its associated electronic device and whether to rollback the update in response to a failure performing the software update on its associated electronic device. The update agent may also be tasked with performing one or both of data gathering from or device control of its associated electronic device. The various functions, including software updating, data gathering and device control, may be programmable and activatable, thereby tailoring the functions performed by the update agent to the lifecycle needs of its associated electronic device.
WIRELESS COMMUNICATION SERVICE OVER AN EDGE DATA NETWORK (EDN) BETWEEN A USER EQUIPMENT (UE) AND AN APPLICATION SERVER (AS)
In a wireless communication network, an Edge Enablement Client (EEC) in a UE Gateway (GW) exchanges EDGE-5 signaling with a user app and exchanges EDGE-1 signaling with a Gateway Enablement Server (GES) in the GW. The GES exchanges EDGE-9 signaling with an Edge Enablement Server (EES) in an Edge Data Network (EDN) and exchanges EDGE-3 signaling with a Gateway Application Server (GAS) in the GW. The GAS exchanges user data between the user app and an Edge Application Server (EAS) in the EDN responsive to the EDGE-3 signaling. The EES exchanges additional EDGE-3 signaling with the EAS. The EAS exchanges the user data between the GAS and a network core responsive to the additional EDGE-3 signaling. The core exchanges the user with the AS and transfers network information for the exchange to a Digital Ledger (DL) node. The DL node determines trust based on the network information.
Scalable onboarding for internet-connected devices
Examples described herein include systems and methods for onboarding a device into a management system. An example method can include loading a management agent onto the device and receiving inventory information for the device. The example method can further include receiving a request to whitelist the device. In some examples, the request originates from a different device, such as a device used by a technician installing the connected device. The management server can authorize the device and add it to the whitelist. After authorizing the device, the management server can onboard the device by sending management information to the management agent on the device. The management server can then exercise management control of the device through the management agent installed on the device.