Video is a major challenge for the future mobile Internet as it is foreseen to account for close to 64% percent of consumer mobile traffic by 2013. However, the current Internet, and in particular the mobile Internet, was not designed with video requirements in mind and, as a consequence, its architecture is very inefficient when handling this type of traffic. This paper presents a novel mobility architecture inspired by the Distributed Mobility Management paradigm, capable of coping with the future video traffic demands, in a distributed and more scalable way. In the proposed solution, mobility support services are spread among several nodes at the edge of the network, thus realizing a flatter architecture and pushing services closer to the terminals. Our approach overcomes some of the major limitations of centralized IP mobility management solutions, by extending existing standard protocols.
Future 5G services rely on effective end‐to‐end management and orchestration for consistently obtaining 5G network's performance benefits. vCDN systems, which are core to the efficient delivery of multimedia contents, must thus be redesigned accounting for NFV and Service‐based 5G Core for fully enabling optimal infrastructure resource optimization and the Quality of Service for increasingly demanding immersive services. This article proposes a novel orchestration framework for deep and 5G‐enabled vCDN services, and builds on two main capabilities: a) the dynamic provisioning of vCDN Edge nodes, enabling content placement at the network Edge based on nearby user's presence, and b) Preemptive video content placement, for users rapidly moving between different edge regions. The solution was modeled and validated using ONAP.
Machine learning is increasingly used in cybersecurity, for example, for anomaly and intrusion detection in microservice and Internet of Things environments. Guidance on securing the machine learning operations (MLOps) lifecycle, termed MLSecOps or SecMLOps, recommends continuous monitoring, a versioned model registry, and lifecycle integration of training, evaluation, and serving. This layer is typically built per deployment, as model-specific code rather than a shared framework. We present AICybOps, a framework that systematizes these practices so the operational features and security properties a deployed model needs are provided by design. It wraps trained models behind a uniform lifecycle interface, exposes a monitor control application programming interface (API) for long-running prediction loops, re-loads models by registered name and version across hosts, and runs durable asynchronous training and evaluation, so a developer implements only the model and inherits the rest. These four design features constitute the framework’s current version; an inheritance-and-expansion criterion governs its contents and keeps it open to further security operations. Because the framework addresses a deployed model by registered version, tracks its runs automatically, and holds the registry behind the service boundary, it yields five security properties: lineage, reproducible replay, an audit trail, private provenance, and integrity of model identity.