The document discusses challenges in adopting cloud-native technologies in distributed and disaggregated mobile network operator (MNO) 5G and beyond 5G (B5G) networks. It notes that today's cloud and communication systems are not capable of capturing, transmitting, storing, and analyzing the large amounts of data that will be generated by trillions of sensors operating continuously. It also says they are not prepared to deliver the compute needed for real-time AI/ML inferencing required to drive demands from various industries and technologies. The document outlines some of the key issues around managing resources and workloads in distributed edge environments and the need for new approaches to discover and deploy resources in real-time across multi-site multi-edge infra
Akraino API TSC Ike Alisson 5G Mobility Edge MEC synergy present 2020 11 06 R...Ike Alisson
Edge in 5G Mobility context evolvement from NGMN 5G WP in Feb 2015 and ETSI MEC renaming MEC to Multi-access Edge Computing by March 2017 and setting Phase 2 New Scope with some examples from 3GPP Rel 15 NSA New Services and System Aspects enhancements revisiosn preceding ETSI MEC renaming and latest 5G Capabilities for Traffic Routing & Service Steering impact on MEC and latest support for AVT (Alternative Virtualized Technologies) and 5G SCEF/NEF SCS/AS for CIoT integrated (like in 5G MEC case through CAPIF/NAPS) with 5G SL IoT Platform oneM2M with support to Ontology SAREF across 10 UCs.
Whitepaper: Mobile Networks in a smart digital future - deploying a platform ...Petr Nemec
The Internet of Things poses particular challenges on the mobile networks of the future - this Whitepaper gives an outlook on what CSPs need to consider when choosing a viable upgrade path and migration strategy towards meeting IoT and NB-IoT (narrow band IoT) requirements.
This report describes the 5G requirements, use cases and technologies which are modelling the transformation of the core network and a roadmap how the 3GPP Evolve Packet Core can be modified to become the core for the 5G networks.
Akraino API TSC Ike Alisson 5G Mobility Edge MEC synergy present 2020 11 06 R...Ike Alisson
Edge in 5G Mobility context evolvement from NGMN 5G WP in Feb 2015 and ETSI MEC renaming MEC to Multi-access Edge Computing by March 2017 and setting Phase 2 New Scope with some examples from 3GPP Rel 15 NSA New Services and System Aspects enhancements revisiosn preceding ETSI MEC renaming and latest 5G Capabilities for Traffic Routing & Service Steering impact on MEC and latest support for AVT (Alternative Virtualized Technologies) and 5G SCEF/NEF SCS/AS for CIoT integrated (like in 5G MEC case through CAPIF/NAPS) with 5G SL IoT Platform oneM2M with support to Ontology SAREF across 10 UCs.
Whitepaper: Mobile Networks in a smart digital future - deploying a platform ...Petr Nemec
The Internet of Things poses particular challenges on the mobile networks of the future - this Whitepaper gives an outlook on what CSPs need to consider when choosing a viable upgrade path and migration strategy towards meeting IoT and NB-IoT (narrow band IoT) requirements.
This report describes the 5G requirements, use cases and technologies which are modelling the transformation of the core network and a roadmap how the 3GPP Evolve Packet Core can be modified to become the core for the 5G networks.
Towards achieving-high-performance-in-5g-mobile-packet-cores-user-plane-functionEiko Seidel
White Paper Intel SK Telekom
This paper presents the architecture for a user plane function (UPF) in the mobile packet core (MPC) targeting 5G deployments.
Time is everywhere but it's implementation in #5G is not easy. Unlike #4G, #TDD is more common in 5G especially in mid-bands [ #3.5Ghz (CBRS) and #Sub6Ghz ] to higher bands (as in mmWave) spectrums and also in spectrum overlays. TDD provides #spectrum efficiency but requires precision time synchronization.
Read this article to learn more about 5G synchronization challenges and how to address it.
Report of the LTE breakout session (NB-IoT) by Mediatek Inc. (Session Chair)Yi-Hsueh Tsai
7.16 WI: Narrowband IOT
(NB_IOT-Core; leading WG: RAN1; started: Sep. 15; target: Mar. 16; WID: RP-151621)
Time budget: N/A
Overall: At this meeting we need to determine the scope of the work. Which parts of LTE TSes to be reused, which parts are not applicable, which parts need change. Identification of issues and candidate solutions. The mindset should be that Requirements in TR 45.820 shall be fulfilled.
A practical architecture for mobile edge computingTejas subramanya
Recently, mobile broadband networks are focused
on bringing additional capabilities to the network edge. For
instance, Mobile Edge Computing (MEC) brings storage and
processing capabilities closer to the mobile user i.e., at the radio
access network, in order to deploy services with minimum delay.
In this paper, we propose a resource constrained cloud-enabled
small cell that includes a MEC server for deploying mobile
edge computing functionalities. We present the architecture with
special focus on realizing the proper forwarding of data packets
between the mobile data path and the MEC applications, based
on the principles of SDN, without requiring any changes to
the functionality of existing mobile network nodes both in the
access and the core network segments. The significant benefits
of adopting the proposed architecture are analyzed based on a
proof-of-concept demonstration for content caching application
use case.
IKAL IoT PINS (Personal IoT Networks) in Netw & Applic layers with selected 5...Ike Alisson
Personal IoT Networks (PINs) and Customer Premises Networks (CPNs) provide local connectivity between UEs and/or non-3GPP devices. The CPN via an eRG, or PIN Elements via a PIN Element with Gateway Capability (PEGC) can provide access to 5G Network Services for the UEs and/or non-3GPP devices on the CPN or PIN.
The 5G System shall be able to support access to the 5G Network and its Services via at least one (1) Gateway (i.e. PIN Element with Gateway Capability PEGC, or eRG) for "authorised UEs" and "authorised non-3GPP devices"in a PIN or a CPN. The 5GS (System) shall be able to support IP traffic offload to Data Network for a CPN. A Personal IoT Network (PIN) consists of PIN Elements (PINE) that communicate using PIN "Direct Connection" or "direct network connection" and is managed locally (using a PIN Element with Management Capability, PEMC). Via a PIN Element with Gateway Capability (PEGC), PIN Elements have access to the 5G Network Services and can communicate with PIN Elements that are not within range to use PIN Direct Connection. A PIN includes at least one PIN Element with Gateway Capability and at least one PIN Element with Management Capability. Only a 3GPP UE can act as PEGC and/or PEMC. A PIN Element with Management Capability, PEMC, is a PIN Element that provides a means for an authorised administrator to configure and manage a PIN. The 5GS shall enable a UE or non-3GPP device in a CPN or PIN to discover other UEs or non-3GPP devices within the same CPN or PIN subject to acess rights. The 5G S shall efficiently support service discovery mechanisms where a UE or non-3GPP device in a CPN or PIN can discover, subject to access rights, "availability" and "reachability" of other entities (e.g. other UEs or non-3GPP devices) on the CPN or PIN. The 5G System shall provide "User Privacy", "Location Privacy", "Identity Protection" and "Communication Confidentiallity" for non-3GPP devices and UEs that are using the PIN Element with Gateway Capability (PEGC), eRG or PRAS. "Privacy" protection should not block differentiated routing and QoS for different destinations and Services for the UE(s). The 5GS shall support Authentication of a UE with 3GPP Credentials for Communication with entities (UEs, non-3GPP devices) in a CPN. The PIN can also have a PIN Application Server (AS) that includes an AF (Application Function) functionality. The AF can be deployed by Mobile Operator or by an Authorized Third (3rd) Party. The 5GS shall support Real-time E2E QoS (Quality ofService) Monitoring and Control for any intra-CPN Data Traffic to or from a UE (i.e. via eRG or via PRAS and eRG). The 5GS shall support Charging Data collection for Data Traffic to/from individual UEs in a CPN or PIN (i.e., UEs behind the PIN Element with Gateway Capability (PEGC) or eRG and/or PRAS). "Relay selection" within a PIN is enabled for both UEs and non-3GPP device and, through 5GS, supports a Mechanism for a PIN Element to select a relay for PIN direct connection.
According to a new Gartner report1, “Around 10% of enterprise-generated data is created and processed outside a traditional centralized data center or cloud. By 2022, Gartner predicts this
figure will reach 75%”. In addition to hosting new 5G era services, the other major network operator driver for edge compute and edge clouds is deploying virtualized network infrastructure, replacing many dedicated hardware-based elements with virtual network functions (VNFs) running on general purpose edge compute. Even portions of access networks are being virtualized, and many of these functions need to be deployed close to end users. The combination of these infrastructure and applications drivers is a major reason that so much of 5G era network transformation resolves around edge cloud distribution.
Entendre els fonaments de la tecnologia i conèixer com ens impactarà el seu desplegament. Vam descobrir les diferents aplicacions que tindrà el 5G en el nostre dia a dia i el valor que aportarà
Question 7 of 30 . Which type of hardware can.pdfaman05bhatia1
Question 7 of 30 . Which type of hardware can be reprogrammed to the desired application or
functionality requirements after manufacturing? FPGA ASIC CPU Accelerator Mark for follow
up Question 8 of 30. What is an advantage for L1 Inline (or full L1 accelerator) acceleration for
5G? Relieve the general-purpose CPUs (GPPs) from the ultra-high L1processing demands.
Supports multiple vDU SW vendors. Supports acceleration for only LDPC forward error
correction. Using a in-line acceleration leaves the CPU free to use itscycles to process other L1
useful tasks. Mark for follow up Question 9 of 30 . Which type of Cloud deployment is used for
exclusive use of the owner? Public Cloud Private Cloud Hybrid Cloud Mark for follow up
5G Cloud Native RAN Orchestration \& Automation Question 18 of 30 . What procedure of the
Life Cycle Management involves uninstalling a container network function to free up resources
on the cluster? Termination Deletion Onboarding Instantiation Mark for follow up Question 19
of 30. In the O-RAN architecture, which component is responsible for the cloud management
and orchestration functions? SMO Non-Real time RIC. Near-Real time RIC. DMS Mark for
follow up Question 20 of 30. True False Mark for follow up
Test - Nokia Bell Labs 5G Cloud Native RAN Exam | BL00460-E-2207 5G Cloud Native RAN
Evolution and Challenges Question 10 of 30 . How does the RAN Intelligent Controller use
AI/ML in the RAN? Enables external applications to control aspects of the 5G network. Enables
RAN programmability. RIC is deployed in Edge data centers and can support classical and cloud
RAN. Provides O1 interface towards SMO. Mark for follow up Question 11 of 30. Which of the
following challenges applies to DevSecOps ? Capability to push new code into real production.
Non-Optimal performances with generic code. Separation of tightly intertwined functions from
application and platform. Adding modularity increases system complexity. Mark for follow up
Question 12 of 30 . Which of the following is a challenge in implementing a microservice
architecture for cloud native RAN?
Test - Nokia Bell Labs 5G Cloud Native RAN Exam | BL00460-E-2207 5G Cloud Native RAN
Open Interfaces and API Question 13 of 30 . The fronthaul interface protocol specified by O-
RAN is based. CPRI eCPRI OBSAI PDH Mark for follow up Question 14 of 30 . In the O-RAN
ALLIANCE specified fronthaul low level split (LLS) options, which two protocol functions are
moved to the RU in 7-2e compared to 7-2? Beamforming and RF. IRC and Channel estimation.
MAC and RLC. RRC and PDCP. Mark for follow up Question 15 of 30 . What is the purpose of
the E1 interface in the gNB?
Question 21 of 30 . Why do we need automation in network operations for 5G ? (Choose 2)
Reduced network complexity enables easier automation to save costs. New business dimensions
and opportunities to support specialized and customized services. Increased network complexity
requires automation to help manage and deploy. Container-as.
3GPP LTE-A Standardisation in Release 12 and Beyond - Jan 2013 Eiko Seidel, C...Eiko Seidel
Quite some time ago major improvements have been made to LTE with LTE-Advanced as part of 3GPP Release 10. Unquestionably, LTE-A will be the leading global 4G standard fulfilling the defined ITU-R requirements [1] on IMT-Advanced such as peak data rates beyond 1Gbps. While further enhancements to LTE-Advanced have just been completed in 3GPP Release 11, the new technology trends become visible to serve the continuously growing traffic demand. This White Paper, based on Nomor’s attendance of 3GPP, provides an outlook on 3GPP standardisation for the forthcoming years. Besides a summary of general trends and a projected release schedule, it includes an overview of the work and study items of Release 12 in the Radio Working Groups. New key technologies that Release 12 will address are: Small Cell Enhancements, a New Carrier Type, 3D-MIMO Beamforming, Machine-Type-Communication, LTE-WiFi Integration at radio level and Public Safety incl. Device-to-Device communication. While the completion of Release 12 is expected mid of 2014, deployments might be seen around the end of 2015 and later. NoMoR is active in different related research projects and offers consultancy services for related research, standardisation, simulation, early prototyping and technology training.
Enabling 5G X-Haul with Deterministic Ethernet - A TransPacket whitepaperIvar Søvold
Transpacket (www.transpacket.com) explores the concept of Ethernet X-Haul in a newly released whitepaper. Discussed extensively in the mobile industry in connection with 5G, the idea is to have an Ethernet based converged transport network serving multiple purposes including fronthaul and backhaul. The whitepaper presents the RAN architectures under consideration for 5G, and their consequences in terms of requirements for the transport network. It further describes how an innovative Ethernet scheduling mechanism is required to support deterministic Ethernet, and to fully achieve an 5G Ethernet X-Haul. It also introduces two use cases, namely Ethernet Crosshaul, and Indoor Coverage, which demonstrate the added value of deterministic Ethernet for mobile transport applications.
AI ML 2023 Measuring Trends Analysis by Stanford UniversityIke Alisson
This year, the Stanford Institute for Human-Centered Artificial Intelligence (HAI) 386 pages Report introduces more original data than any previous edition, including a new Chapter on AI Public Opinion, a more thorough Technical Performance Chapter, Original Analysis about Large Language and Multimodal Models, detailed Trends in Global AI Legislation Records, a Study of the Environmental Impact of AI Systems, and more. On the "success" of AI ML on the Market, w.r.t. Chapter 4, indicating: "Corporate Investment (Mergers/Acquisitions, Minority Stakes, Private Investment, & Public Offerings) dipped in 2022 to 190 billion from 2021 amount of 276 billion highs, but the number has still increased 13-fold in the last decade. The Biggest Investment event of the Year was the Nuance Communications acquisition; the Computer SW Tech Company was picked up by Microsoft for $19.7 billion."
Ike Al Pres on 5G and 5G Advanced selected Capabilities to LF Edge Akraino Su...Ike Alisson
Insights into 3GPP specifications for "5G Advanced" release related to both, insights and pace of development related to "equivalent" NPNs/SNPNs (Private Networks) with support to non 3GPP Access and providing support for Localized Services, APIs evolvement for realization of Service Enablement Framework Services, Analytics on System & Application level, Enhacements on System & Application level for developing Applications/Service on the Edge, exemplifying the alignment between 3GPP EDGEAPP & ETSI MEC Architectures as part of the GSMA proposed in June 2021 Solution for providing E2E Solution for Edge Applications & some insights on the O-RAN Alliance SMO related non RT-RIC related to rApps.
More Related Content
Similar to Ike A to LF Edge Akraino Comp Stor Netw & Commun & ETSI MEC AppD Mngmnt Present Dec 8th 2022 Rev PA06.pdf
Towards achieving-high-performance-in-5g-mobile-packet-cores-user-plane-functionEiko Seidel
White Paper Intel SK Telekom
This paper presents the architecture for a user plane function (UPF) in the mobile packet core (MPC) targeting 5G deployments.
Time is everywhere but it's implementation in #5G is not easy. Unlike #4G, #TDD is more common in 5G especially in mid-bands [ #3.5Ghz (CBRS) and #Sub6Ghz ] to higher bands (as in mmWave) spectrums and also in spectrum overlays. TDD provides #spectrum efficiency but requires precision time synchronization.
Read this article to learn more about 5G synchronization challenges and how to address it.
Report of the LTE breakout session (NB-IoT) by Mediatek Inc. (Session Chair)Yi-Hsueh Tsai
7.16 WI: Narrowband IOT
(NB_IOT-Core; leading WG: RAN1; started: Sep. 15; target: Mar. 16; WID: RP-151621)
Time budget: N/A
Overall: At this meeting we need to determine the scope of the work. Which parts of LTE TSes to be reused, which parts are not applicable, which parts need change. Identification of issues and candidate solutions. The mindset should be that Requirements in TR 45.820 shall be fulfilled.
A practical architecture for mobile edge computingTejas subramanya
Recently, mobile broadband networks are focused
on bringing additional capabilities to the network edge. For
instance, Mobile Edge Computing (MEC) brings storage and
processing capabilities closer to the mobile user i.e., at the radio
access network, in order to deploy services with minimum delay.
In this paper, we propose a resource constrained cloud-enabled
small cell that includes a MEC server for deploying mobile
edge computing functionalities. We present the architecture with
special focus on realizing the proper forwarding of data packets
between the mobile data path and the MEC applications, based
on the principles of SDN, without requiring any changes to
the functionality of existing mobile network nodes both in the
access and the core network segments. The significant benefits
of adopting the proposed architecture are analyzed based on a
proof-of-concept demonstration for content caching application
use case.
IKAL IoT PINS (Personal IoT Networks) in Netw & Applic layers with selected 5...Ike Alisson
Personal IoT Networks (PINs) and Customer Premises Networks (CPNs) provide local connectivity between UEs and/or non-3GPP devices. The CPN via an eRG, or PIN Elements via a PIN Element with Gateway Capability (PEGC) can provide access to 5G Network Services for the UEs and/or non-3GPP devices on the CPN or PIN.
The 5G System shall be able to support access to the 5G Network and its Services via at least one (1) Gateway (i.e. PIN Element with Gateway Capability PEGC, or eRG) for "authorised UEs" and "authorised non-3GPP devices"in a PIN or a CPN. The 5GS (System) shall be able to support IP traffic offload to Data Network for a CPN. A Personal IoT Network (PIN) consists of PIN Elements (PINE) that communicate using PIN "Direct Connection" or "direct network connection" and is managed locally (using a PIN Element with Management Capability, PEMC). Via a PIN Element with Gateway Capability (PEGC), PIN Elements have access to the 5G Network Services and can communicate with PIN Elements that are not within range to use PIN Direct Connection. A PIN includes at least one PIN Element with Gateway Capability and at least one PIN Element with Management Capability. Only a 3GPP UE can act as PEGC and/or PEMC. A PIN Element with Management Capability, PEMC, is a PIN Element that provides a means for an authorised administrator to configure and manage a PIN. The 5GS shall enable a UE or non-3GPP device in a CPN or PIN to discover other UEs or non-3GPP devices within the same CPN or PIN subject to acess rights. The 5G S shall efficiently support service discovery mechanisms where a UE or non-3GPP device in a CPN or PIN can discover, subject to access rights, "availability" and "reachability" of other entities (e.g. other UEs or non-3GPP devices) on the CPN or PIN. The 5G System shall provide "User Privacy", "Location Privacy", "Identity Protection" and "Communication Confidentiallity" for non-3GPP devices and UEs that are using the PIN Element with Gateway Capability (PEGC), eRG or PRAS. "Privacy" protection should not block differentiated routing and QoS for different destinations and Services for the UE(s). The 5GS shall support Authentication of a UE with 3GPP Credentials for Communication with entities (UEs, non-3GPP devices) in a CPN. The PIN can also have a PIN Application Server (AS) that includes an AF (Application Function) functionality. The AF can be deployed by Mobile Operator or by an Authorized Third (3rd) Party. The 5GS shall support Real-time E2E QoS (Quality ofService) Monitoring and Control for any intra-CPN Data Traffic to or from a UE (i.e. via eRG or via PRAS and eRG). The 5GS shall support Charging Data collection for Data Traffic to/from individual UEs in a CPN or PIN (i.e., UEs behind the PIN Element with Gateway Capability (PEGC) or eRG and/or PRAS). "Relay selection" within a PIN is enabled for both UEs and non-3GPP device and, through 5GS, supports a Mechanism for a PIN Element to select a relay for PIN direct connection.
According to a new Gartner report1, “Around 10% of enterprise-generated data is created and processed outside a traditional centralized data center or cloud. By 2022, Gartner predicts this
figure will reach 75%”. In addition to hosting new 5G era services, the other major network operator driver for edge compute and edge clouds is deploying virtualized network infrastructure, replacing many dedicated hardware-based elements with virtual network functions (VNFs) running on general purpose edge compute. Even portions of access networks are being virtualized, and many of these functions need to be deployed close to end users. The combination of these infrastructure and applications drivers is a major reason that so much of 5G era network transformation resolves around edge cloud distribution.
Entendre els fonaments de la tecnologia i conèixer com ens impactarà el seu desplegament. Vam descobrir les diferents aplicacions que tindrà el 5G en el nostre dia a dia i el valor que aportarà
Question 7 of 30 . Which type of hardware can.pdfaman05bhatia1
Question 7 of 30 . Which type of hardware can be reprogrammed to the desired application or
functionality requirements after manufacturing? FPGA ASIC CPU Accelerator Mark for follow
up Question 8 of 30. What is an advantage for L1 Inline (or full L1 accelerator) acceleration for
5G? Relieve the general-purpose CPUs (GPPs) from the ultra-high L1processing demands.
Supports multiple vDU SW vendors. Supports acceleration for only LDPC forward error
correction. Using a in-line acceleration leaves the CPU free to use itscycles to process other L1
useful tasks. Mark for follow up Question 9 of 30 . Which type of Cloud deployment is used for
exclusive use of the owner? Public Cloud Private Cloud Hybrid Cloud Mark for follow up
5G Cloud Native RAN Orchestration \& Automation Question 18 of 30 . What procedure of the
Life Cycle Management involves uninstalling a container network function to free up resources
on the cluster? Termination Deletion Onboarding Instantiation Mark for follow up Question 19
of 30. In the O-RAN architecture, which component is responsible for the cloud management
and orchestration functions? SMO Non-Real time RIC. Near-Real time RIC. DMS Mark for
follow up Question 20 of 30. True False Mark for follow up
Test - Nokia Bell Labs 5G Cloud Native RAN Exam | BL00460-E-2207 5G Cloud Native RAN
Evolution and Challenges Question 10 of 30 . How does the RAN Intelligent Controller use
AI/ML in the RAN? Enables external applications to control aspects of the 5G network. Enables
RAN programmability. RIC is deployed in Edge data centers and can support classical and cloud
RAN. Provides O1 interface towards SMO. Mark for follow up Question 11 of 30. Which of the
following challenges applies to DevSecOps ? Capability to push new code into real production.
Non-Optimal performances with generic code. Separation of tightly intertwined functions from
application and platform. Adding modularity increases system complexity. Mark for follow up
Question 12 of 30 . Which of the following is a challenge in implementing a microservice
architecture for cloud native RAN?
Test - Nokia Bell Labs 5G Cloud Native RAN Exam | BL00460-E-2207 5G Cloud Native RAN
Open Interfaces and API Question 13 of 30 . The fronthaul interface protocol specified by O-
RAN is based. CPRI eCPRI OBSAI PDH Mark for follow up Question 14 of 30 . In the O-RAN
ALLIANCE specified fronthaul low level split (LLS) options, which two protocol functions are
moved to the RU in 7-2e compared to 7-2? Beamforming and RF. IRC and Channel estimation.
MAC and RLC. RRC and PDCP. Mark for follow up Question 15 of 30 . What is the purpose of
the E1 interface in the gNB?
Question 21 of 30 . Why do we need automation in network operations for 5G ? (Choose 2)
Reduced network complexity enables easier automation to save costs. New business dimensions
and opportunities to support specialized and customized services. Increased network complexity
requires automation to help manage and deploy. Container-as.
3GPP LTE-A Standardisation in Release 12 and Beyond - Jan 2013 Eiko Seidel, C...Eiko Seidel
Quite some time ago major improvements have been made to LTE with LTE-Advanced as part of 3GPP Release 10. Unquestionably, LTE-A will be the leading global 4G standard fulfilling the defined ITU-R requirements [1] on IMT-Advanced such as peak data rates beyond 1Gbps. While further enhancements to LTE-Advanced have just been completed in 3GPP Release 11, the new technology trends become visible to serve the continuously growing traffic demand. This White Paper, based on Nomor’s attendance of 3GPP, provides an outlook on 3GPP standardisation for the forthcoming years. Besides a summary of general trends and a projected release schedule, it includes an overview of the work and study items of Release 12 in the Radio Working Groups. New key technologies that Release 12 will address are: Small Cell Enhancements, a New Carrier Type, 3D-MIMO Beamforming, Machine-Type-Communication, LTE-WiFi Integration at radio level and Public Safety incl. Device-to-Device communication. While the completion of Release 12 is expected mid of 2014, deployments might be seen around the end of 2015 and later. NoMoR is active in different related research projects and offers consultancy services for related research, standardisation, simulation, early prototyping and technology training.
Enabling 5G X-Haul with Deterministic Ethernet - A TransPacket whitepaperIvar Søvold
Transpacket (www.transpacket.com) explores the concept of Ethernet X-Haul in a newly released whitepaper. Discussed extensively in the mobile industry in connection with 5G, the idea is to have an Ethernet based converged transport network serving multiple purposes including fronthaul and backhaul. The whitepaper presents the RAN architectures under consideration for 5G, and their consequences in terms of requirements for the transport network. It further describes how an innovative Ethernet scheduling mechanism is required to support deterministic Ethernet, and to fully achieve an 5G Ethernet X-Haul. It also introduces two use cases, namely Ethernet Crosshaul, and Indoor Coverage, which demonstrate the added value of deterministic Ethernet for mobile transport applications.
AI ML 2023 Measuring Trends Analysis by Stanford UniversityIke Alisson
This year, the Stanford Institute for Human-Centered Artificial Intelligence (HAI) 386 pages Report introduces more original data than any previous edition, including a new Chapter on AI Public Opinion, a more thorough Technical Performance Chapter, Original Analysis about Large Language and Multimodal Models, detailed Trends in Global AI Legislation Records, a Study of the Environmental Impact of AI Systems, and more. On the "success" of AI ML on the Market, w.r.t. Chapter 4, indicating: "Corporate Investment (Mergers/Acquisitions, Minority Stakes, Private Investment, & Public Offerings) dipped in 2022 to 190 billion from 2021 amount of 276 billion highs, but the number has still increased 13-fold in the last decade. The Biggest Investment event of the Year was the Nuance Communications acquisition; the Computer SW Tech Company was picked up by Microsoft for $19.7 billion."
Ike Al Pres on 5G and 5G Advanced selected Capabilities to LF Edge Akraino Su...Ike Alisson
Insights into 3GPP specifications for "5G Advanced" release related to both, insights and pace of development related to "equivalent" NPNs/SNPNs (Private Networks) with support to non 3GPP Access and providing support for Localized Services, APIs evolvement for realization of Service Enablement Framework Services, Analytics on System & Application level, Enhacements on System & Application level for developing Applications/Service on the Edge, exemplifying the alignment between 3GPP EDGEAPP & ETSI MEC Architectures as part of the GSMA proposed in June 2021 Solution for providing E2E Solution for Edge Applications & some insights on the O-RAN Alliance SMO related non RT-RIC related to rApps.
Ike A 5G Private Networks PNI-NPN/SNPN LF Edge Akraino Technical Meeting Spri...Ike Alisson
Presentation on 3GPP standard specified PNI-NPN/SNPN also in marketing terms denoted as "Private 5G". The presentation also provides some insights on the evolvement of PNI-NPN/SNPN for the coming 3GPP Release denoted as "5G Advanced" that shall specify inter-operability and roaming between "equivalent NPNs/SNPNs and NPN/SNPNs access to Non-3GPP Access.
CNCF TUG (Telecom User Group) Ike Alisson 5G New Service Capabilities Rev pa10Ike Alisson
5G New Service Capabilities (with an overview on the synergy between 5G CN and RAN (O-RAN Specifications) via CUPS and some of the Enhancements for URLLC UCs enhancements
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
UiPath Test Automation using UiPath Test Suite series, part 5DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 5. In this session, we will cover CI/CD with devops.
Topics covered:
CI/CD with in UiPath
End-to-end overview of CI/CD pipeline with Azure devops
Speaker:
Lyndsey Byblow, Test Suite Sales Engineer @ UiPath, Inc.
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...SOFTTECHHUB
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
GridMate - End to end testing is a critical piece to ensure quality and avoid...ThomasParaiso2
End to end testing is a critical piece to ensure quality and avoid regressions. In this session, we share our journey building an E2E testing pipeline for GridMate components (LWC and Aura) using Cypress, JSForce, FakerJS…
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
Ike A to LF Edge Akraino Comp Stor Netw & Commun & ETSI MEC AppD Mngmnt Present Dec 8th 2022 Rev PA06.pdf
1. Challenges in (selected) Cloud-native adoption in
(distributed & disaggregated)
MNOs 5G and B5G Networks need
for
Synergy between
Compute, Storage, Networking
and
Communications
Ike Alisson
2022 - 12- 08 Rev PA06
2. Table of Contents (ToC)
1. Cloud & Communication Issues & Challenges
2. ETSI MEC design & implementation example
3. 3GPP "5G Advanced" (Rel. 18 & 19) proposed Capabilities (evolvement
with e.g. MNOs/ CSPs MOCN "direct" & "indirect" & "equivalent"/inter-
operable NPNs/SNPNs).
2
3. 3
1. Cloud & Communications Systems' (current) Challenges & Issues
Today’s Cloud and Communications Systems are NOT CAPABLE of
- Capturing,
- Transmitting,
- Storing, and
- Analysing
the Petabytes of Data generated by the soon-to-be trillions of Sensors operating 24/7.
They are also NOT PREPARED to deliver the Compute needed for Real-Time AI/ML Inferencing required to drive such
demands that we anticipate will come from our
- FoF (Factory of the Future)
- VR/XR/MR (Virtual, Extended, Mixed Reality and Extended Reality) with Haptic Interactions,
- (V2X) Connected Vehicles,
- Assisted living, or
- Merging of Physical & Digital worlds with 5G & B5G
Ref.: 5GA, DCC, Nov., 2022: 4
4. 4
The Cloud is "Changing"
1st - Applications want to be deployed anywhere & change deployment anytime.
The focus moves from "sharing resources to Composing Dynamic Capabilities,
even after Deployment.
Applications will be Delay- and Latency sensitive, on varying Time-scales
with different Hard- & Soft boundaries.
Communication, Compute, and Storage must be considered as an Integrated Set of Changeable Configurations that
provide the required service to an application.
2nd - “Center of Gravity is moving toward the Devices ("Edge"), & interactions in a Cyber-Physical World best
suited for these tasks and configure any required communication between all end points in important areas such as
- IoT,
- Industry 4.0,
- Private 5G, or
- Retail and Public Services.
5. 5
Management of Resources and Workloads:
Most Orchestration Frameworks today use a Centralized Approach (where)
One (1) Entity has knowledge of all the Resources in the System and Plan how the
Workloads will be mapped.
With the start of Docker & containers, the Kubernetes Project was started to
provide a lightweight & scalable Orchestration solution.
Most existing Compute Systems today, including Edge Computing Systems, rely on
static provisioning.
Thus, the SW & the Services needed to perform the Compute are already residing
at the Edge Server prior to an Edge node requests a Service & the pool of HW
resources is also known a priori to Kubernetes.
This architecture works well for Cloud & the MEC where a Centralized
Orchestration is used.
Since the Resources of the Pervasive Edge are independently owned, the
Orchestration Frameworks need to be extended to handle Dynamic and Multi-
Tenant Resources in a secure manner.
6. 6
Management of Resources and Workloads:
it is important for the Orchestration Architecture to be able to support
Dynamic Discovery & Use of (HW) Resources distributed in the edge.
Kubernetes and Docker are both centralized Architectures, which need
messages exchange and synchronization before a new Service can be
configured on a server.
Hence, new approaches have to be investigated to discover and deploy
new (HW) Resources in Real-Time within the Multi-site & Multi-Edge
Infrastructure of 5G & B5G Systems.
Content Sharing and Resource/Service Orchestration in 5G & B5G
New innovations in terms of Data Movement & the Orchestration of Resource
and
Compute Services will be required.
a few new exemplary approaches on Network - & Application - Layers are
detailed such as …………..
7. 7
2. ETSI MEC design & implementation example
3GPP EAS and ETSI MEC Application Profile Provisioning
The MEC Application can start "producing" or "consuming"
MEC Services after the MEC Application is instantiated &
running.
The Application Information (AppInfo), which can be
regarded as the MEC Application Profile, represents the
information provided by the MEC application instance as part
of the "Application Registration request" message.
Some fields in AppInfo are intentionally not duplicating the
EAS profile (if present) with conflicting parameters but should
be consistent with them.
It can be seen that unlike AppD, which is
mainly used in the Management Plane for
instantiating an Application, and is static in
nature, AppInfo carries the runtime information about the
MEC application instance.
In 3GPP EDGEAPP, the EAS profile is provided in the EAS
registration request. Ref.: 3GPP, Rel. 18 (5G Adv), Nov., 2022
8. 8
3GPP EAS and ETSI MEC Application Profile Provisioning
… in current ETSI MEC specification, no APIs
for MEC Application Registration is defined
because it is assumed that all MEC Applications
are on-boarded and managed by MEC
Orchestrator.
API for MEC Application discovery is not
defined since the existing MEC Service is either
defined from the MEC Application's perspective
or it is consumed by the MEC Application
rather than the UE.
Therefore, the comparison EAS Registration and EAS discovery of
EDGEAPP and ETSI MEC specification shows that:
[Observation 2] ETSI MEC platform(MEP) supports service registration. In the registration parameter
"ServiceInfo",there is a mandatory field "consumedLocalOnly" used to indicate that the service can
only be consumed by the MEC applications located in the same locality, which means ETSI MEC
services (produced by Authorized MEC APPs) registered and exposed on MEP can be invoked by
MEC consumer APPs deployed on the same or another MEC host.
Ref.: 3GPP, Rel. 18 (5G Adv), Nov., 2022
22. 22
For the special MEC/Hybrid Cloud Assurance UC - CI/CD/CT,
MEC assurance becomes essential for critical Edge Compute
Applications & Performance & particularly in a Multi-Cloud
Environment at the Carrier/Hyperscale Gateway.
An MEC Validation Platform provides Full Stack MEC Testing &
Performance coverage including Global Security assessment.
This is divided in 3 Main Categories starting from the ground floor
with Cloud Infrastructure Validation including:
1. Capacity & Performance for Latency, Bandwidth & Resiliency,
Benchmarking, Scaling and Secure Access Service Edge (SASE).
2. MEC Nodes Validation need to be conducted for QoS / QoE
Validation, Jitter Latency, Video & Audio Processing, O-RAN
RIC, 5G Core UPF split / N9 interface, xHaul Transport as a
Service, Extended Visibility and Security Assurance
Specification (SCAS).
3. MEC Vertical Services & Applications with QoS / QoE Validation,
Jitter Latency, O-Cloud, Video & Audio Processing, all the
Verticals like C-V2X, industry 4.0, Video surveillance etc. and
Network Security.
23. 23
The O-RAN WG4 Conformance Test Specification
ensures the O-RU’s compliance with the O-RAN
Fronthaul (FH) Standards.
The 3GPP (Test) Specifications requires a full gNB since
3GPP does not recognize the open nature of O-RAN.
3GPP does not separate the Radio from the BaseBand
processing Unit (BBU) as required by O-RAN.
However, it is possible to leverage the 3GPP Transmitter &
Receiver (TRU) Tests (Chptrs 6 & 7 of 3GPP
Specifications) when validating the O-RAN FH.
All test waveforms specified by the O-RAN Conformance
Test Specification use the same test waveforms used in
3GPP tests.
The Test set-up can test a Radio for 3GPP TRU performance and O-RAN conformance. The only difference is that 3GPP
expects the tests to run on a gNB that is in test mode.
The O-RAN tests the Radio using an O-DU emulator and does not require a test mode.
It is not possible to perform 3GPP Chapter 8 conformance tests using the O-DU emulator because it requires MAC layer
processing, which is not present in the O-DU emulator.
24. 24
Autonomous Service Management (enabling
Autonomous Networks) tries to put Analysis &
Decisions into Machines, so it becomes a “Zero-
touch” System for the Operator – more correct: the
operator’s touch moves from the Network to the
Design of the Automation.
• The Management Systems need to provide
Capabilities to enable Autonomy, but also to
accelerate and simplify the DevOps process
• System interactions need to be simplified at API level
and allow autonomous decisions in requested
systems at different levels On the path to full
cloudification, hybrid situations will appear.
28. 1. List of Equivalent PLMNs, as specified in TS 5G System Architecture
Rel. 17, clause 5.18.2a.
2. The Solution re-use existing Function as specified in clause 5.18.1 of TS 5G
System Architecture, Rel. 17, where different combination of PLMN ID and NID
can point to the same 5GC.
5.18 Network Sharing
A Network Sharing Architecture shall allow Multiple Participating Operators to share resources of a
Single Shared Network according to agreed allocation schemes. The shared network includes a radio
access network. The shared resources include radio resources.
The shared network operator allocates shared resources to the participating operators based on their
planned and current needs and according to service level agreements.
In this Release of the specification, only the 5G Multi-Operator Core Network (5G MOCN) network
sharing architecture, in which only the RAN is shared in 5G System, is supported. 5G MOCN for 5G
System, including UE, RAN and AMF, shall support operators' ability to use more than one PLMN
ID (i.e. with same or different country code (MCC) some of which is specified in TS NAS for UE in
Idle mode and different network codes (MNC)) or combinations of PLMN ID and NID. 5G MOCN
supports NG-RAN Sharing with or without multiple Cell Identity broadcast as described in TS NG
RAN.
5G MOCN also supports the following sharing scenarios involving non-public networks, i.e.NG-
RAN can be shared by any combination of PLMNs, PNI-NPNs (with CAG), and SNPNs (each
identified by PLMN ID and NID).
NOTE 1: PNI-NPNs (without CAG) are not explicitly listed above as it does not require additional NG-RAN
sharing functionality compared to sharing by one or multiple PLMNs.
In all Non-Public Network sharing scenarios, each Cell Identity … is associated with one (1) of the following
Configuration options:
- one or multiple SNPNs;
- one or multiple PNI-NPNs (with CAG); or
- one or multiple PLMNs only.
NOTE 2: This allows the assignment of Multiple Cell Identities to a Cell and also allows the cell identities to be
independently assigned, i.e. without need for coordination, by the network sharing partners, between PLMNs and/or non-
public networks.
NOTE 3: Different PLMN IDs (or combinations of PLMN ID and NID) can also point to the same 5GC. When
same 5GC supports multiple SNPNs (identified by PLMN ID and NID), then they are not used as equivalent SNPNs for a
UE.
NOTE 4: There is no standardized mechanism to avoid paging collisions if the same 5G-S-TMSI is allocated to
different UEs by different PLMNs or SNPNs of the shared network, as the risk of paging collision is assumed to be very
low. If such risk is to be eliminated then PLMNs and SNPNs of the shared network needs to coordinate the value space
of the 5G-S-TMSI to differentiate the PLMNs and SNPNs of the shared network.
29. 29
5G Architecture for Hybrid and Multi-Cloud Environments
The Main Challenges to overcome in a Hybrid & Multi-Cloud Strategy are:
1. Maintaining Portability; 2. Controlling the Total Cost of Ownership (TCO); 3. Optimizing Productivity & Time to Market (TTM).
DevOps – a Set of Practices that brings together SW Development & IT operations with the Goal of Shortening the Development & Delivery Cycle & increasing SW Quality - is
often thought of and discussed in the Context of a Single Company or Organization. The Company usually Develops the SW, Operates it & Provides it as a Service to
Customers, according to the SW-as-a-Service (SaaS) Model. Within this context, it is easier to have Full Control over the Entire Flow, including Full Knowledge of the
Target Deployment Environment.
In the Telecom Space, by contrast, we typically follow the "as-a-Product (aaP) Business model, in which SW is developed by Network SW Vendors e.g. as Ericsson
(Nokia, Huawei, ZTE) & provided to Communication Service Providers (CSPs) that Deploy & Operate it within their Network. This Business Model requires the consideration
of additional aspects.
The most important contrasts between the Standard DevOps SaaS Model & the Telecom aaP Model are the Multiplicity of Deployment
Environments & the fact the Network SW Vendor Development Teams cannot know upfront exactly what the Target Environment looks like.
Although a SaaS Company is likely to Deploy & Manage its SW on two (2) or more different Cloud Environments, this is inevitable within Telco, as each CSP creates &/or
selects its own Cloud infrastructure (Fig. 1 below).
Figure 1: The DevOps and (Telecom) aaP Business Models