Intel Corporation

Novell, Inc.

Emc Corporation

Mcafee, Inc.

Kshitij Arun Doshi

Francesc Guim Bernat

Ned M Smith

Suraj Prabhakaran

Vadim Sukhomlinov

Mark A Schmisseur

Timothy Verrall

Daniel Rivas Barragan

Alexander Bachmutsky

Rajesh Poornachandran

Kapil Sood

Elmoustapha Ould-Ahmed-Vall

Christian Maciocco

Tarun Viswanathan

Suleyman Sair

Karthik Kumar

S M Iftekharul Alam

Marcos Emanuel Carranza

Satish Chandra Jha

Vesh Raj Sharma Banjade

John Joseph Browne

Raghu R Kondapalli

Andrew J Herdrich

Dario Sabella

Vincent J Zimmer

Christopher J Hughes

Katalin Klara Bartfai-Walcott

Miltiadis Filippou

Brinda Ganesh

Bret L Toll

Nageen Himayat

Srikathyayani Srikanteswara

Quinn Able Jacobson

Mats Gustav Agerstam

Lokpraveen B Mosur

Mona Vij

Glen J Anderson

Hong Wang

Michael Lemay

Per H Hammarlund

Gad Shlomo Sheaffer

Raj K Ramanujan

Susanne M Balle

Matthew C Merten

Deborah T Marr

John P Shen

Kuilin Clark Chen

Yi Zhang

Asit K Mishra

Nilesh K Jain

David M Durham

Ravi L Sahita

Ren Wang

Ali-Reza Adl-Tabatabai

Sanjeev N Trika

Thomas Willhalm

Ravishankar Iyer

Alex Nayshtut

Ignacio Javier Alvarez

Rahul Khanna

Bratin Saha

Gautham N Chinya

Mark D Yarvis

Liuyang L Yang

Sanjay Bakshi

Evan Custodio

Eve M Schooler

Patrick G Kutch

Edwin Verplanke

Vinodh Gopal

Jill MacDonald Boyce

Mohan J Kumar

Tsung-Yuan Charles Tai

Robert G Blankenship

Baiju V Patel

Igor G Muttik

Sujoy Sen

Giuseppe Beppe Raffa

Yang-Seok Choi

Sara S Baghsorkhi

Debra Bernstein

Hassnaa Moustafa

Jr-Shian Tsai

Omesh Tickoo

Utkarsh Y Kakaiya

Carolyn Bennion McClain

Javier Felip Leon

Mingqiu Sun

Maruti Gupta Hyde

Ian M Steiner

Ilango S Ganga

David Gomez Gutierrez

Rameshkumar G Illikkal

Kenneth D Shoemaker

Narayan Ranganathan

Ravikumar Balakrishnan

Andrey Chilikin

Jeffrey D Chamberlain

Dimitrios Ziakas

Eric Dahlen

Examples described herein relate to an Infrastructure Processing Unit (IPU) that comprises: interface circuitry to provide a communicative coupling with a platform; network interface circuitry to provide a communicative coupling with a network medium; and circuitry to expose infrastructure services to be accessed by microservices for function composition and to selectively provide a barrier to halt operation of at least one microservice based on event data from a composite node that performs the at least one microservice.

Infrastructure processing unit

Methods, apparatus, systems, and articles of manufacture are disclosed to increase resiliency in self-healing mechanisms. At least one non-transitory machine-readable medium comprises instructions that, when executed, cause at least one processor to at least partition computational resources of a first host into a primary partition and a shadow partition, the primary partition to communicate with a second host, apply a fix for the primary partition, determine if the primary partition can communicate with the second host during the application of the fix, cause, in response to the determination that the primary partition cannot communicate with the second host during the application of the fix, the shadow partition to communicate with the second host; and transfer communication with the second host from the shadow partition to the primary partition, the transfer in response to a determination that the application of the fix is complete.

Methods and apparatus to increase resiliency in self-healing mechanisms

Various aspects of methods, systems, and use cases include security-based orchestration. A method may include evaluating, within a secure environment of an untrusted device, a preamble to determine a set of security requirements. The method may include, providing, to an attestation server, an indication of security parameters for services of the untrusted device corresponding to security requirements of the set of security requirements, and in response to receiving a confirmation from the attestation server, providing a request to the untrusted device outside the secure environment to generate a trusted domain including the services.

Network supported low latency security-based orchestration

Various approaches for implementing multi-tenant data protection are described. In an edge computing system deployment, a system includes memory and processing circuitry coupled to the memory. The processing circuitry is configured to obtain a workflow execution plan that includes workload metadata defining a plurality of workloads associated with a plurality of edge service instances executing respectively on one or more edge computing devices. The workload metadata is translated to obtain workload configuration information for the plurality of workloads. The workload configuration information identifies a plurality of memory access configurations and service authorizations identifying at least one edge service instance authorized to access one or more of the memory access configurations. The memory is partitioned into a plurality of shared memory regions using the memory access configurations. A memory access request for accessing one of the shared memory regions is processed based on the service authorizations.

Multi-tenant data protection in edge computing environments

A computing device includes a direct memory access (DMA) engine coupled to a memory, a network interface, and processing circuitry. The processing circuitry is to perform a secure exchange with a second computing device to negotiate a shared encryption key, based on a request for data received via the network interface from the second computing device. The DMA engine is to retrieve the data from a storage location based on an encryption command. The encryption command indicates the storage location. The DMA engine is to encrypt the data based on the shared encryption key to generate encrypted data, and store the encrypted data in the memory.

Cryptographic data processing using a DMA engine

Systems and techniques for cross-layer automated fault tracking and anomaly detection are described herein. Anomaly data may be obtained from a plurality of layers of a network. Elements of the anomaly data may be identified that correspond to a data flow of an application executing on the network. An artificial intelligence model may be trained using the elements of the anomaly data to generate an impact score for the application. The impact score may be generated for the application by evaluating current network metrics using the artificial intelligence model. An operational component of the network may be modified based on the impact score.

Cross-layer automated fault tracking and anomaly detection

Apparatus and methods for data lifecycle management in an edge environment are disclosed herein. An example apparatus includes an operation executor to identify a first operation to be performed for a data object at an edge node in an edge environment and a second operation to be performed for the data object, the first operation different that the second operation. The example apparatus includes a time parameter retriever to retrieve a first time value associated with the first operation from a data source and a second time value associated with the second operation from the data source. The operation executor is to execute the first operation in response to the first time value and to execute the second operation in response to the second time value.

Apparatus, systems, articles of manufacture, and methods for data lifecycle management in an edge environment

A computing node includes network interface circuitry and processing circuitry. The processing circuitry assigns available computing resources to a plurality of slice contexts. Each slice context of the plurality includes resource allocations of the available computing resources associated with multiple communication networks. A first portion of the resource allocations is designated as dedicated resources and a second, remaining portion is designated as shared resources. A FAFO event associated with a workload is detected. The workload executes on a network slice instance (NSI) associated with a slice context of a subset of slice contexts. The configuration of the NSI is restored to a pre-FAFO event state based on reconfiguring one or both of the dedicated resources or the shared resources of the slice context based on the resource allocations of at least a second slice context in the subset of slice contexts.

End-to-end network slicing (ENS) from ran to core network for next generation (NG) communications

Disclosed herein are systems and methods for peer-assisted safety models for autonomous and assisted-driving vehicles. In an embodiment, a safety-model service receives a safety-model request for a safety model from a target vehicle. The safety-model service identifies, responsive to receiving the safety-model request, one or more source vehicles as safety-model input sources. The safety-model service receives safety-model data associated with the identified one or more source vehicles. The safety-model service generates, based on the safety-model request and the received safety-model data, a target-vehicle safety model for the target vehicle. The safety-model service transmits the target-vehicle safety model to the target vehicle for use by the target vehicle.

Systems and methods for brokering peer-assisted safety models for autonomous and assisted-driving vehicles

System and techniques for geographic routing are described herein. A node receives a data packet that includes map data, a sequence of geographic areas to a requestor, and a target geographic area. The node may then determine that it is within the target geographic area and start a transmit timer based on a next-hop geographic area. Here, the next-hop geographic area is determined from the sequence of geographic areas in the data packet. The node may then counts how many other nodes from the geographic area sent data packets while the transmit timer is running. When the transmit timer expires, the node may transmit a modified data packet when the number of data packets is less than a predefined threshold. Here, the modified data packet is the data packet updated to include local map data and the next-hop geographic area.

Geographic routing

Various aspects of methods, systems, and use cases include en-route computing coordination. A method may include receiving a packet including a compute task and context information, identifying a destination node for the packet, and determining a route for the packet to the destination node. The route may include an intermediary node determined based on the context information and available resources at the intermediary node to execute the compute task of the packet at the intermediary node. The method may include forwarding the packet to a next device along the route.

Software defined networking with en-route computing

System and techniques for storage node recruitment in an information centric network (ICN) are described herein. An ICN node receives a storage interest packet that includes an indication differentiating the storage interest from other ICN interests. The ICN node forwards the storage interest packet and receives a storage data packet in response. Here, the storage data packet includes an indication that the storage data packet is not to be cached along with node information for a node that created the storage data packet. The ICN node may then transmit the storage data packet in accordance with a pending interest table (PIT) entry corresponding to the storage interest packet.

Storage node recruitment in an information centric network

Methods, apparatus, systems, and articles of manufacture for networked device testing are disclosed. An example method includes determining an input to be applied to a programmable network device, mutating the input to determine an input variant, applying the input variant to the programmable network device, and in response to determining that the input variant causes the programmable network device to enter an expected state, add the input variant to a test set.

Systems and methods for networked device testing

Various systems and methods for implementing intent-based cluster administration are described herein. An orchestrator system includes: a processor; and memory to store instructions, which when executed by the processor, cause the orchestrator system to: receive, at the orchestrator system, an administrative intent-based service level objective (SLO) for an infrastructure configuration of an infrastructure; map the administrative intent-based SLO to a set of imperative policies; deploy the set of imperative policies to the infrastructure; monitor performance of the infrastructure; detect non-compliance with the set of imperative policies; and modify the administrative intent-based SLO to generate a revised set of imperative policies that cause the performance of the infrastructure to be compliant with the revised set of imperative policies.

Intent-based cluster administration

System and techniques for decentralized key generation and management are described herein. An information centric network (ICN) node receives a first ICN interest packet for public encryption parameters of an identity based encryption (IBE) key generation center (KGC). Public encryption parameters for the KGC are received in a first ICN data packet in response to the first ICN interest packet. The public encryption parameters are cached and used to respond a second ICN interest packet for the public parameters. A third ICN data packet may be received from the KGC in response to a key generation request. Here, the third data packet includes an indication that the third ICN data packet is part of a one-time session. Then, the third ICN data packet is transmitted without caching the third ICN data packet content based on the indication.

Decentralized key generation and management

Growing community of inventors

Tempe, AZ, United States of America

Kshitij Arun Doshi