Slice Isolation for 5G Transport Networks

Network slicing plays a key role in the 5G ecosystem for vertical industries to introduce new services. However, one widely-recognized challenge of network slicing is to provide traffic isolation and concurrently satisfy diverse performance requirements, e.g., bandwidth and latency. In this work, we showcase the capability to retain these two goals at the same time, via extending the 5Growth baseline architecture and designing a new data-plane pipeline, i.e., virtual queue, over the P4 switch. To demonstrate the effectiveness of our approach, a proof-of-concept is presented serving different service requests over a mixed data path, including P4 switches and Open vSwitches (OvSs)

Performance isolation for network slices in Industry 4.0: The 5Growth approach

Network slicing plays a key role in the 5G ecosystem for verticals to introduce new use cases in the industrial sector, i.e., Industry 4.0. However, a widely recognized challenge of network slicing is to provide traffic isolation and concurrently satisfy diverse performance requirements, e.g., bandwidth and latency. Such challenge becomes even more important when serving a large number of network traffic flows under a resource-limited condition between distributed sites, e.g., factory floor and remote office. In this work, we present the capability to retain these two goals at the same time, by applying the virtual queue notion over a priority queuing based pipeline in P4 switch over software-defined networks. To examine the effectiveness of our approach, a proof-of-concept is setup to serve different requests of Industry 4.0 use cases over a mixed data path, including P4 switch and Open vSwitch, for a large number of network flows.This work was supported in part by the EU H2020 5GROWTH Project under Grant 856709

5G-TRANSFORMER Service Orchestrator: design, implementation, and evaluation

European Conference on Networks and Communications (EuCNC 2019)5G networks will pose complex network management challenges due to the variety of vertical services they will need to serve and the diversity and heterogeneity of underlying infrastructure. The service orchestration functionality is fundamental to enable fulfilling the requirements of the different verticals while efficiently sharing the infrastructure resources. This paper details the 5G-TRANSFORMER service orchestrator implementation and operation. It also evaluates and profiles service creation time showing how the automation offered by the platform allows reducing it from hours to minutes. It also shows that the most time-consuming steps correspond to the deployment of the virtual network functions and post-deployment configuration, which consume one order of magnitude more time than the rest of steps (e.g., network creation, port creation).This work has been partially funded by the EC H2020 5G-TRANSFORMER Project (grant no. 761536) and grants TEC2017-88373-R (5G-REFINE) and 2017 SGR 1195

A Framework for Orchestration and Federation of 5G Services in a Multi-Domain Scenario

First International Workshop on Experimentation and Measurements in 5G (EM-5G).This paper presents the design of the 5GT Service Orchestrator (SO), which is one of the key components of the 5G-TRANSFORMER (5GT) system for the deployment of vertical services. Depending on the requests from verticals, the 5GT-SO offers service or resource orchestration and federation. These functions include all tasks related to coordinating and providing the vertical with an integrated view of services and resources from multiple administrative domains. In particular, service orchestration entails managing end-to-end services that are split into various domains based on requirements and availability. Federation entails managing administrative relations at the interface between the SOs belonging to different domains and handling abstraction of services. The SO key functionalities, architecture, interfaces, as well as two sample use cases for service federation and service and resource orchestration are presented. Results for the latter use case show that a vertical service is deployed in the order of minutes.This work has been partially funded by the EC H2020 5G-TRANSFORMER Project (grant no. 761536)

Exploiting Forecasting for Automatic Network Service Operations in Digital Twin Applications

This demo highlights and experimentally proves the adoption of the Forecasting Functional Block (5Gr-FFB) in the orchestration and monitoring operations of the 5G Network Services (NS). In particular, the demo will show how to instantiate an NS with related monitoring functionalities and exploit the 5Gr-FFB for generating forecasting metrics. The interactions among 5Gr-FFB and the other orchestration functional blocks (i.e., the Service Orchestrator (5Gr-SO) and the Vertical oriented Monitoring System (5Gr-VoMS) will be highlighted. The demo considers a robotic Digital Twin use-case deployed at 5Tonic premises. This work represents a first step towards the evolution of advanced close loop operations, consuming hybrid metrics (i.e., retrieved from the monitoring components and the forecasting ones) to perform automatic NS operations with margin in time

5Growth: Secure and Reliable Network Slicing for Verticals

Network slicing is well-recognized as a core 5G technology to enable heterogeneous vertical services sharing the same infrastructure. In this context, the H2020 5Growth project extends baseline 5G management and orchestration platforms to manage the life-cycle of real end-to-end, reliable, and secure network slices with performance guarantees. In this paper, we present 5Growth's approaches to (i) attain isolation across network slices, (ii) provide secure interfaces towards third parties, and (iii) exploit AI/ML to achieve reliability through automated anomaly detection. In our quest towards validating full-fledged 5G pilots, we demonstrate our slicing mechanisms in PoCs that include interacting with ICT-17 infrastructure

Risk for Major Bleeding in Patients Receiving Ticagrelor Compared With Aspirin After Transient Ischemic Attack or Acute Ischemic Stroke in the SOCRATES Study (Acute Stroke or Transient Ischemic Attack Treated With Aspirin or Ticagrelor and Patient Outcomes)

Abstract: Background: Patients with minor acute ischemic stroke or transient ischemic attack are at high risk for subsequent stroke, and more potent antiplatelet therapy in the acute setting is needed. However, the potential benefit of more intense antiplatelet therapy must be assessed in relation to the risk for major bleeding. The SOCRATES trial (Acute Stroke or Transient Ischemic Attack Treated With Aspirin or Ticagrelor and Patient Outcomes) was the first trial with ticagrelor in patients with acute ischemic stroke or transient ischemic attack in which the efficacy and safety of ticagrelor were compared with those of aspirin. The main safety objective was assessment of PLATO (Platelet Inhibition and Patient Outcomes)\u2013defined major bleeds on treatment, with special focus on intracranial hemorrhage (ICrH). Methods: An independent adjudication committee blinded to study treatment classified bleeds according to the PLATO, TIMI (Thrombolysis in Myocardial Infarction), and GUSTO (Global Use of Strategies to Open Occluded Coronary Arteries) definitions. The definitions of ICrH and major bleeding excluded cerebral microbleeds and asymptomatic hemorrhagic transformations of cerebral infarctions so that the definitions better discriminated important events in the acute stroke population. Results: A total of 13 130 of 13 199 randomized patients received at least 1 dose of study drug and were included in the safety analysis set. PLATO major bleeds occurred in 31 patients (0.5%) on ticagrelor and 38 patients (0.6%) on aspirin (hazard ratio, 0.83; 95% confidence interval, 0.52\u20131.34). The most common locations of major bleeds were intracranial and gastrointestinal. ICrH was reported in 12 patients (0.2%) on ticagrelor and 18 patients (0.3%) on aspirin. Thirteen of all 30 ICrHs (4 on ticagrelor and 9 on aspirin) were hemorrhagic strokes, and 4 (2 in each group) were symptomatic hemorrhagic transformations of brain infarctions. The ICrHs were spontaneous in 6 and 13, traumatic in 3 and 3, and procedural in 3 and 2 patients on ticagrelor and aspirin, respectively. In total, 9 fatal bleeds occurred on ticagrelor and 4 on aspirin. The composite of ICrH or fatal bleeding included 15 patients on ticagrelor and 18 on aspirin. Independently of bleeding classification, PLATO, TIMI, or GUSTO, the relative difference between treatments for major/severe bleeds was similar. Nonmajor bleeds were more common on ticagrelor. Conclusions: Antiplatelet therapy with ticagrelor in patients with acute ischemic stroke or transient ischemic attack showed a bleeding profile similar to that of aspirin for major bleeds. There were few ICrHs. Clinical Trial Registration: URL: http://www.clinicaltrials.gov. Unique identifier: NCT01994720.Abstract: BACKGROUND: Patients with minor acute ischemic stroke or transient ischemic attack are at high risk for subsequent stroke, and more potent antiplatelet therapy in the acute setting is needed. However, the potential benefit of more intense antiplatelet therapy must be assessed in relation to the risk for major bleeding. The SOCRATES trial (Acute Stroke or Transient Ischemic Attack Treated With Aspirin or Ticagrelor and Patient Outcomes) was the first trial with ticagrelor in patients with acute ischemic stroke or transient ischemic attack in which the efficacy and safety of ticagrelor were compared with those of aspirin. The main safety objective was assessment of PLATO (Platelet Inhibition and Patient Outcomes)-defined major bleeds on treatment, with special focus on intracranial hemorrhage (ICrH). METHODS: An independent adjudication committee blinded to study treatment classified bleeds according to the PLATO, TIMI (Thrombolysis in Myocardial Infarction), and GUSTO (Global Use of Strategies to Open Occluded Coronary Arteries) definitions. The definitions of ICrH and major bleeding excluded cerebral microbleeds and asymptomatic hemorrhagic transformations of cerebral infarctions so that the definitions better discriminated important events in the acute stroke population. RESULTS: A total of 13 130 of 13 199 randomized patients received at least 1 dose of study drug and were included in the safety analysis set. PLATO major bleeds occurred in 31 patients (0.5%) on ticagrelor and 38 patients (0.6%) on aspirin (hazard ratio, 0.83; 95% confidence interval, 0.52-1.34). The most common locations of major bleeds were intracranial and gastrointestinal. ICrH was reported in 12 patients (0.2%) on ticagrelor and 18 patients (0.3%) on aspirin. Thirteen of all 30 ICrHs (4 on ticagrelor and 9 on aspirin) were hemorrhagic strokes, and 4 (2 in each group) were symptomatic hemorrhagic transformations of brain infarctions. The ICrHs were spontaneous in 6 and 13, traumatic in 3 and 3, and procedural in 3 and 2 patients on ticagrelor and aspirin, respectively. In total, 9 fatal bleeds occurred on ticagrelor and 4 on aspirin. The composite of ICrH or fatal bleeding included 15 patients on ticagrelor and 18 on aspirin. Independently of bleeding classification, PLATO, TIMI, or GUSTO, the relative difference between treatments for major/severe bleeds was similar. Nonmajor bleeds were more common on ticagrelor. CONCLUSIONS: Antiplatelet therapy with ticagrelor in patients with acute ischemic stroke or transient ischemic attack showed a bleeding profile similar to that of aspirin for major bleeds. There were few ICrHs