Akraino & Alicon Partner Page
Contact
Ike Alisson
Below attached you can find a list of some of the activities reflecting the Akraino and ALICON (Ike ALIsson CONsulting) partnering. Alicon's Partnering approach reflects ideas from the field of "Alliance Strategy", distinguishing the "Partner" role/responsibility and interaction from the "Vendor/Supplier" role/responsibility and interaction.
3GPP granted ALICON SWEDEN on April 24th, 2024 the right to use the New 6G logo for use on specifications for 6G (https://lists.akraino.org/g/tsc/topic/3gpp_6g_technology_logo_ike/105733616).
The creation of this 6G Graphical Mark is the next step in 3GPP’s preparations for the Next Generation of Mobile Systems. In December 2023, the Organizational Partners: ARIB (Japan), ATIS (North America), CCSA (China), ETSI (Europe), TSDSI (India), TTA (Korea) and TTC (Japan) announced their joint commitment to make 6G happen in 3GPP. Now there is a graphical badge that can accompany the 3GPP work on the topic. One of the 1st outings for the Logo is expected to be at the 8-10 May 2024 Working Group SA1 ‘3GPP Stage-1 Workshop on IMT2030 Use Cases’, held in Rotterdam.
3GPP granted ALICON SWEDEN on November 10th, 2021 the right to use the
"5G Advanced" marker (logo) on ALICON SWEDEN 5G presentations and marketing material . The 3GPP decision to adopt the new marker (logo) for 5G was taken at the 3GPP Project Coordination Group (PCG#46-e Meeting) in April 2021. The "5G-Advanced" logo is envisioned to mark the 3GPP Reports and Specifications, from Release-18 & onward.
This is an evolvement to 3GPP granting ALICON SWEDEN on February 13th, 2017, the right to use
5G marker/logo (3GPP Rel. 15 and onward specifications) on presentations and marketing material about 5G.
Below attached is a list of some of the Akraino & Alicon Partnering Activities
Akraino Forum's purpose is to facilitate the on-going flow of Information to TSC and BPs' PTLs in terms of seminars, that take place each Tuesday at the Akraino TSC meetings. The presentations are conducted either by Akraino TSC member or a guest invited by Akraino TSC member.
The model behind that process aiming to facilitate outlining the Issues, that stands on the way and hinder to achive the Goals is denoted as G. A. I. N. (what is Needed to resolve the Issue(s) that hinders/stands on the way to Achieve the Goal(s)) (please see attached below Ref. Ericsson PtW).
The link to Akraino Forum for generating and evolving innovative ideas is: Akraino Forum for generating and evolving "innovative ideas"
The following presentation and input have been provided by Ike Alisson
1. 6G Service Requirements incl AI General Service Requirements
Attached from 6G Service Requirements Specification in Release 21, Sept., 2026 including the AI General Service Requirements. The Spec is TS not TR. So, the provided Tables on AI Performance Requirements, Bursty Data Traffic and IMS Disability, should have been V & V, preferably with several Parties to refine the Numbers with the experienced in the commissioned Service limited Environment with several Parties, hopefully, since, NOTHING, that is even remotely close when it comes to AI ML (LLMs Agentic AI Apps) PERFORMANCE could have been revealed/released (also w.r.t. LLM ARCHITECTURE & AI ML App Service AVAILABILITY, RELIABILITY & MOBILITY....& no one asks/requests Data/Info about that &/or is interested in knowing...NO ONE....yet...
2. 5G 6G AI ML for AEL SEAL Protocol
Two (2) remarks on this 3GPP 5G 6G AI ML use in Service Enablement Application Layer (SEAL) Protocol Spec for 3rd Party AI Agents use. 1st, despite the recent criticism to AI Domain Industry lack of Security, need for continuous Monitoring & Model (Data update) Training & financial issues re. circular financing, there is hardly any criticism re. the Specified Architecture, Interfaces, Protocols, (not in the presentation, but available specifications on) Service Performance Requirements, ML Model Training, Split & Transfer on the Network End-points & more)...None of the above is available in currently dominant AI ML Domain Enterprises Solutions as OpenAI, Anthropic, Google DeepMind, Amazon Web Services (AWS), Microsoft...NONE...& above all, No one asks & inquiries about this...but in case that the speculated AI bubble burst happens, one might wonder if "this" info could be used as "Technical" ground for analysis for the current AI ML Enterprises lack of Innovation, as criticized by some. 2nd, while those Architecture Specifications are almost 5 years old, no MNO &/or Equipment Vendor presents anything on those Solutions for 5G & 6G Service Enablement & surprisingly, No One asks either...as if those are none existent. There might be a "marginal" minority at 3GPP, though, that is focused on that Architecture, simply because, it continues to evolve...& above all, available 7/24 to anyone & everyone...Be Notified!
Fascinating (Telecom) Domain/topic that could, so far, survive to further evolve & take place in the 6G Specifications. Conceived in 3G, totally ignored in 4G & 5G, now, as a result of the revealed/experienced issues, problems, challenges, limitations in the so called "Private 5G" (that was actually running on 4G EPC CN), as you see, the Service Enablement, presented as a Framework, provides the right, inter-related Architectures Solution....While presented to/"primarily targeting the "Developers", there could not be one single @3GPP SA6 WG member who could truly believe that a Developer, just any Developer, would know/have insights into CAPIF CCF with Network Exposure Topology for Service Invocation, SEALAPP Architecture Common Functions and EDGEAPP Architecture interaction between AC/EEC/EDC with ECS on the Network and EES/EAS (the latter added Inter-EAS Communication Capability) in the DN & Interaction limitations between AF & DNAI (Configuration). Please note that each one of those is actually a Stand-alone Platforms with specified Feature Functionalities (with use of "Context" for Service & Session Continuity (SSC1-3) as specified. You want to test/experience that? Simple, you just could join/participate at the CAMARA Project TSC, that is an OPEN Project, and check about whatsoever connection to any of the presented Telecom Application Enablement Framework Architectures, and inquire with them about any connection/ conformance/ compliance to CAMARA Project APIs to those Application Enablement....or just any MNO/Equipment Vendor Representative about any of those as CAPIF, EDGEAPP, SEALAPP References about Deployments that those might have any in the last 10 years. Nevertheless, PLEASE, be Vigilant!...as you see from the text included in the Presentation, someone has some experience from such Deployments...It is in the 3GPP Specs text.. as presented hereby in one of the included slides.
1. 6G CN Resilience and Reliability with 6G CP and UP and AI Protocols and Network Exposure Capability enhancements with Lesson from 5G Deployments 5G Limitations
About the revealed 5G Limitations (Lessons from 5G Implementation-oriented Deployments). As revealed (quoted from the Spec) on p. 24 (reg. the specified NF-to-NF Indirect Communication with use of SCP), the Cloud-native adoption in Implementation of 5G SBA/SBI CN NFs had further shifted the lack & inability of Multi-vendor Interoperability to Cellular Networks inability to be able to deploy the foundational CP/UP Implementation in the Network, as SBA/SBI specified. Since the initial 6G System Architecture Specifications use the 5G SBA/SBI Architecture as a "starting-point" on which the 6G System Architecture would be built, as it looks like, the so called 6G Deployment would actually be a realization of 5G SBA/SBI, very much like in the past, when the 3G Specifications were realized with the 4G LTE EPC Deployments and 4G LTE EPC Specifications were realized with the deployment of 5G NSA...the 5G Specifications would be realized with the 6G Deployments...hopefully...if anyone (can be found to be able) can prepare SoC (Statement of Compliance) and map/list in the MNOs Networks to the respective 5G Specifications what versions and level of compliance of HW & SW versions are existent/ delivered...so that there can be outlined what is missing...and then "how to fix" it...preferably...with a "new" Approach since here are the revealed outcomes (as also indicated on slide/page nr 24)...and "this" would also have an impact on implementing 6G to be AI-native since the Data from 5G Networks would be needed to train those LLMs to generate/make available the so-called Agentic AI Applications...depending also if/when the widely-popular in the Media AI Bubble bursts...and whatever remains from the current/existing Data Centers...
2 6GS NRF based Registration and Discovery
https://www.linkedin.com/ posts/ike-alisson-21173_6g-system-architecture-nrf-registration-ugcPost-7490498583973007360-oJj1/?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAACTG0BMU8kFXcOJwNsDGWci6xxBF6fdhw
3, 6G AI Protocols and 6G System Arch KI#18 AI for 6G
https://www.linkedin.com/ posts/ike-alisson-21173_6g-ai-protocols-for-ai-for-6g-and-6g-network-activity-7478897103419674624-Zy7c?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAACTG0BMU8kFXcOJwNsDGWci6xxBF6fdhw
6G Network capability Exposure enhancements
https://www.linkedin.com/ posts/ike-alisson-21173_6g-network-capability-exposure-enhancements-ugcPost-7485906471709450240-Zz-O/?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAACTG0BMU8kFXcOJwNsDGWci6xxBF6fdhw
6G RAN HLS CU-DU Split
https://www.linkedin.com/ posts/ike-alisson-21173_6g-ran-anb-cu-du-hls-challenges-and-benefits-activity-7476621717768171520-cErd?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAACTG0BMU8kFXcOJwNsDGWci6xxBF6fdhw
6. 6G RAN aNB HLS CU-DU Challenges and Benefits
In case of interest in Telecom 5G & 6G attached on the 6G RAN discussion on aNB split into CU-DU from 5G NG-RAN/NR gNB CU-DU Split Failures/ Issues/ Complications due to variety of Implementations in 5G RAN Deployment. The respective RAN Architecture gNB Split into CU-DU (with CUPS) & unaligned design between the CU & DU, deployed with huge variety in Implementations of the 5G RAN, is partly unable to resolve the Complexity & Cost in Communicating the UE Context and State Measurement between the CU-DU. As you would read, the DESIGN of CU & DU must be aligned. Since you would not be able to find any PR/announcement of 5G RAN HLS (Higher Layer Split) Deployment on the market in the last 10 years with a single explicit Reference to any Architecture Release Specification, whether from 3GPP or @O-RAN Alliance, one can wonder if "this HLS" related to RAN, is the "only issue" that impose the need for a new (aligned) Design of the both CU & DU in RAN, since similar to 5G RAN Deployments lacking any Reference to any Architecture Specification(from 3GPP or O-RAN ALLIANCE), any news &/or PRs on 5G & 5G Advance Release Deployments, lacks References similar to 5G RAN HLS Deployments....and the Organisational Structure with Processes & Business Approach, is the same, irrespective if it is a MNO or Equipment Vendor....So, to use now 3GPP 6G Architecture Specifications (with new RAN Design with Interfaces) would be......relatively easy to solve as it would/could be straightforward to resolve the Functional Specifications....the "difficult" part would be, as in the 5G...to find/identify Who would be able to Deliver/Deploy/Commission those as EVERYTHING, as e.g. Org. Structures, Processes, Business Objectives, all are tuned to the IT DevOps CI/CD SaaS Business Model and not the Telecom Business Model aaP.....The specified NFs as NEs in terms of "Platforms", is not only "non-existent" any longer....The Enterprise R&D Depts. are deprived from any Org Structure with Processes to be able to serve such an evolvement for the Telecom aaP Business Model. 6G discussions would/could be "exciting", as in the attached below info on 6G RAN HLS. those might reveal additional substantial Strategic Mistakes done with 5G Deployments & at the end, provide a ground to measure something, once denoted in Telecom as "Professional Dignity, since related to Service Requirements Service Availability, Reliability & QoS...may be removing all the Humans and leave it for AI ML to fix it all in Telecom...both 5G and 6G at once?!?!?...attached below... Be Notified!
2. 6G RAN Architecture and aNB BTS
Be notified that while for the majority out there, this info on 6G RAN Architecture BTS aNB, is/could be perceived as "new" since part of the "6G", for the very few out there, 6G RAN aNB is an evolvement & Solution to existing issues/problems/limited (RAN) Capabilities in (RAN) deployments out there (predominantly following/deploying O-RAN ALLIANCE Specs. Please note on p. 5 the aNB Functionality to determine for the UE the respective 6G CN Node (NF) (& the shift of AMF for UE that "relay" role to the 6G RAN aNB). The respective RAN-CN (N2) Interface alternatives (P2P & SBA/SBI compliant) with Options, as specified, are listed too. Please note the impact/Capability enablement of the latter on the Network Service Exposure enablement (Framework, specified for/supporting LTE & 5G Network Service Exposure & MDA Types A, B (LTE related) and Type C (5G SBA/SBI PMF related), but non existent/supported by both MNOs & Equipment Vendors) and primarily on the need of expertise on 3GPP RAN, Service Exposure and Management as non-existent as primarily focused/used on Partners (Cloud-native Suppliers proprietary APIs & Management Tools). The 3GPP 5G RAN RRC Protocol (Table of Contents ToC) is presented to exemplify the Functionality support for some UCs. That is also non-existent in the O-RAN ALLIANCE Specs. Be notified..
3. 6G User Identities and Application User Consent as specified by 3GPP and LF Camara Project
Be notified on the enhancements in 3GPP 5G Advanced Release(s)(B5G) to re-defined "User" (to no longer refer solely to Human Subscriber), difference between Subscription & User Profile.. & respective Capability change in (the Network) settings (on Application Layer) to enable access to Localized services without the need for Subscription....All as part of the 5G Advanced 1st Release shift in Private 5G VIAPA to "equivalent" Private 5G Networks and shift in the Specified IoT from CIoT to 5G Advanced IoT Networks with Standard 5G UE to be configurable to be either an IoT Device, or an IoT Device with GW Capability or an IoT Device with Management Capability with MA (Multi Access to both 3GPP & Non-3GPP RAT). Please note that the so called in the Market IoT Solution (with more than 620 different IoT Platforms) and Private 5G Deployments (with Vendor Proprietary APIs & only Cellular enablement Capability related to Connectivity) can not be upgraded, respectively, compete with the attached info on the enhancements including Application User Consent...due to immense focus & popularity to generate revenues from Developers as Google and Apple do from their respective Google & Apple Stores... so there is a huge market potential for those with insights on the B5G System Feature Functionalities evolvement E2E (on Network & Application Layers).
4. 6G System Architecture CN Enhancements KI 9 enabling Network Access to Localized Services
This "6G System Architecture KI#9 specifying various (5G Advanced Release) Network Configurations for Access to Localized Services could/would be the Capability characterizing variety of 6G Networks enabling 6G End-User Services. As you would see from the Presentation, those that could master the specified 5GA AEL Framework with specific enhancements on the 5G/6G CN would be able to proliferate & differentiate those Service Offerings. Please note that in this 6G KI9 Solution Spec, Enterprises, that are MNOs proposed the SSTs as Solution & Enterprises that are Cellular Equipment Vendors proposed Solution as NPNs. Nevertheless, while it is common for both to focus on (the traditional) 1st Network build-up & then Service deployment Approach, both had not reflected on the latest advancements specified in the 5G Advanced Releases specifications and ailed to focus on the type and nature of the "Localized" Services that those "Networks" would commission with KPIs specified E2E & 6QI MANDATORY. As you would see, deliberately, the Presentation includes the initial Spec on Network Access to Localized Services from Dec., 2021 & 5G Service Requirements for Localized Services. Please note that in the initial 5G Spec from Dec., 2021 the used term "Service Operator" was kindly elaborated to me (by thens 3GPP SA2 Chair) to be "a misunderstanding" overlapping with the term "Service Provider" (SP). As included in the Presentation, 2 years later, in the 5G (Advanced Release) for Factory of the Future (FF), "this misunderstanding" re-appeared... due to specified Service Enabling Platform Specs evolvement, that MNOs had left in the hands/monopoly of Apple & Google Stores & (MNOs) focused on Connectivity to generate Revenues...As it looks like, realizing the 5G Advanced Releases Feature Functionalities Specifications would, very likely, position 6G to be "NETWORK of NETWORKS" providing Access to Localized Services through SERVICE ENABLEMENT PLATFORMS, already specified in 5G Advanced Releases, but not deployed/ commissioned. You may try to start getting acquainted with those BECAUSE NO ONE, whether MNOs, or Equipment Vendors representatives with Analysts talk (expressing their opinions) or mention or present anything about those...& the Practice to present the specified already 5G SBA/SBI Architecture with specified Service Requirements is abandoned and not known since more than a decade now... B
5. 6G System Architecture CN Enhancements KI 6 and KI9 as PCC, QoS (6QI Mandatory) 6G Network for AI
6G System Arch KI#6 and KI#9 CN enhancements PCC, 6QI, 6G Netw for AI
6. 5G Advanced Energy End-to-End (E2E) Efficiency (EE) and Energy Saving (ES) Rel-20
5GA EE ES E2E Rel-20
https://www.linkedin.com/ posts/ike-alisson-21173_5g-advanced-system-e2e-energy-efficiency-activity-7432302895439605760-U6gh?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAACTG0BMU8kFXcOJwNsDGWci6xxBF6fdhw
7. 6G AEL (Application Enabl Layer) Service Enablement with 5GA Service Enabler Framework (AEF) Architectures Rel - 20
For some very few, the theme in "this" presentation could be an "echo from the past", since the notion of this SL (Service (Enabler) Layer in Annex 1) was conceived with 3G, to boost the "Data" Traffic in the Network by deploing Application Enablers to proliferate Mobile (Internet) Applications, deployed with 4G LTE (as an IT SI (System Integration) Projects & reached its "peak" with 5G Deployments as "Private 5G" (predominantly with proprietory APIs & IT Mngmnt tools). In order to "fix" all the issues experienced with the deployed out there called "Private 5G" Projects (with "Connectivity" as the only Characteristic of "5G" Networks, that in reality were 5G NSA Deployments with LTE EPC CN & RAN E-UTRAN Configuration with NG-eNB as ALWAYS "Primary" Access Node & the 5G NR gNB as "Secondary" for UCs Services requiring "extra Capacity"), to resolve all the issues of "lacking Common Functionalities" among Applications in "Private 5G" Solutions, making unable to connect ´those, 3GPP specified in Rel-17 (approved 5 years ago, in June 2022 as Ready for Deployment/Production), a Platform denoted as SEAL. "Dislike "Private 5G" IT Solutions, 5G SEAL had not only specified/enabled "Common Functionalities" and Commection beween various Application Enabler Architectures), but used the 5G SBA/SBI to put each Enabler Architecture & Client to underake the role of an "Invoker" to the Network (Telecom) Northbound APIs (that no MNO &/or Equipment Vendor as Ericsson &/or Nokia or an Initiative as Aduna Global &/or CAMARA Project even mentions about, as if "non-existent") to benefit from the specified Network Capabilities (similar to 3Gs "Common" Network Functionalities in SNF/SDP), but now evolved with 5G SBA also very much due to the fact that QoS Service Requirements and KPIs from 3GPP Rel-17 & onwards are specified E2E...As an Analyst referred to respective @3GPP Specs for 5G as "stuff", please note NOT so much about "THIS STUFF" EXISTENCE, but , above all, "WHY" "THIS STUFF" offers the SPECIFIED (inter-related) FEATURES/CAPABILITIES"in this way"...
8. Telecom System AI ML use Consistency Alignment in B5G & 6G Networks Rel-19 and Rel-20
The purpose with sharing the info in "this presentation" about the specified use of AI ML in Telecom is twofold. 1st, it is an attempt to provide an answer to the (most important) Question: "Compared to What? So here is the specified use of AI ML in Telecom in alignment with the SPECIFIED 1. Service Requirements, 2. System Architecture, 3. Security & Privacy, 4. Multimedia, 5. Management, Ochestration & Charging 6. Application Enablement and Terminals (Phones, Sensors, Entities) at/as a SYSTEM and compared to existing AI ML Approach, Architecture, Terminology. Model Trainings in LLMs & Agentic AI "specified" use of AI ML resulted in variety of Solution Tool Suppliers out there & their Methods, Approach & Processes for Product Development. 2nd, w.r.t. FCC TAC WG 6G Report from Aug., 2025 (pgs 12,16), for ANYONE/EVERYONE involved with AI-RAN Alliance &/or O-RAN ALLIANCE with Specifications work/focus on 6G, dislike in the past 10 years with 5G, now, there would not only be needed to be aware of those Specifications specifics "existence" (as in the past case with 5G), but also have both, insights into the Specifications inter-dependencies, and above all, the knowledge for selecting the needed Set of Feature Functionalities from the listed/specified "Normative" & "Optional" Feature Functionalities on the System level due to the specified E2E Performance & Functional Operations. Dislike in the past as done with 5G ignoring an Service Requirements & KPIs, now, there will be needed to have insights into the Specified for QoS Service Availability, Reliability & Mobility, the specified lowest Data granularity with Characteristics (also specifided 5 types) formats and NRM for both CN & RAN, as specified....be Notified/Forewarned...
9. 5G System Core Network (CN) enhancements for use of AI ML Rel-20
"To be forewarned is to be forearmed"..they say...Be forewarned on the 5GS CN enhancements for AI ML use & DP (Data Profile) for Data (sets) for Data Statistics (Performance) & Predictions & 3rd Party UMTES (UE Model Training Entity Server) Specified as an Input to 6G System Architecture Release normative work. As we had seen in the past (& told by my colleague Wallis Dudhnath), 3G Specs were realized with 4G LTE & 4G EPC Specs were realized with 5G NSA deployments, & those 5G Advanced Specs will be realized/deployed with commissioning of "6G" Services. For anyone/everyone involved with O-RAN ALLIANCE & AI-RAN Alliance Specs, "THIS (CN) DOMAIN" is non-existing in your Specs & as such, THE INFO in the PRESENTATION, could feel/be perceived as too alien, uninteresting, unimportant (as in the last 10 years), &/but also very much cumbersome & challenging (too many new terms & abbreviations). Please "be notified" (aka "forewarned") on Info in Solution #32 on page 51, that, "THIS" (RAN DESIGN ARCH. with INTERFACES) is under change/evolving (Specs work on-going) in terms that the "whole (3GPP specified) RAN" would undertake the role of "a Relay" for the UE (UDCF Architecture) to the CN (currently undertaken by AMF, as you see ) & it is not "if", but more of "when", "this" will happen. As with "Private 5G" (decisions by Verizon & Nokia Mngmnts) this (RAN) evolvement, may suddenly put you in a situation to be involved with an "old/legacy Solution" & responsible for "Support & Maintenance" & it may happen much sooner than projected/forecasted 2030 year... As they also say "Hope is a Pleasant Company, but a Bad Advisor"..."BE NOTIFIED", aka "forewarned" as "the new" Competition might pick this up and "implement it" ("on the periphery")..."on the way towards "6G". Let's see HOW MUCH one could "see" from the Specified in the Presentation about "THOSE SPECIFIED KEY ISSUES (2) & USE CASES (2) WITH SOLUTIONS AT MWC 2026 at Barcelona in March 2026..that is about "TELECOM", right?!?!?!?
10. Towards AI-Native 6G Systems Standards Enablers
4 aspects related to this post. The attached Paper is "an Introduction" to the post "tomorrow". 1st, as this Paper focus on the 3GPP limitation on 5G CN UP (User Plane) for AI ML use to enable "Dynamic Task Migration", the post tomorrow, presents the 5GS CN enhancements for use of AI ML on User Plane (also including enhancements on UL & Capabilities for dynamic PCC in 5GS CN), enhanced Capabilities, as Specified in 3GPP Rel-20. 2nd, "The SW Approach in the Paper (with proposed Solution for a AI ML Controller) also reveals the Approach to Product & SW development, deployment in Telecom & commissioning towards 5GS CN NFs as Apps DevOps SaaS Business Model in terms of SI (System Integration) Project for a tenure of 3-5 years, widely adopted for deploment of 5G from Rel-15 onwards. It also explicitly shows the embraced & applied neglect & ignorance to 3GPP Approach since its initial Rel-99 to have all its Releases as "Parallel" & "Inter-operable". 3rd,. the Paper also focus on proposing, as perfectly elaborated by Thierry Van de Velde in his post on "Making 6G as successful as 5G NSA", where he points out that (quote) "Today in 2025, there's a Geopolitical Marketing Push to force AI Agents into the (5G CN) NFs, abusing the Service-based Architecture (SBA) (HTTPS) to convey Self-invented Non-3GPP-Standardized Protocols (HTTPS POST someuri:predict-me-this?someparameter), destroying the Compatibility between different NF Vendors, between hosting MNOs and MVNOs, or between Visited 5GC and Home 5GC in Roaming Scenarios. As a result of Geopolitics and Vendorpush, Market Confidence got eroded when it came to the truly Valuable Innovations of the 5G System (5GS), which came in R16/R17: URLLC, TSN, 5GLAN, ATSSS, PNI-NPN, NTN, RedCap... No, Not Slicing" (end of quote). 4th, last but not least, the type & nr of used References in the Paper, using only two (2) 3GPP Specs, & giving preference to other Research Papers, is an example of why Agentic AIs & LLMs have an about 20% correct hit rate when it comes to 3GPP Specs Information. Simply because, not the 3GPP Specs, but respective Research Papers are chosen by the PEOPLE "training" all those Agentic AIs & LLMs about "Telecom" & "5G".
11. 6G specified Use Cases, System Architecture and new RAN Design with Interfaces as an input to Rel-21 Specifications normative work (the timeline to be finalized by June 2026).
12. Ike Alisson input to Akraino TSC on BPs 6G evolvement Rev PA04 May 29 2025 and Summary of the 3GPP 6G WS at Incheon March 10-11, 2025
13. Ike Alisson input to Akraino TSC on BPs 6G evolvement Rev PA02 May 25 2025
14. Presentation on AI ML Opportunities in 2023 to Akraino TSC on Nov. 23, 2023.
15. Presentation on use of AI ML in 5G with specified AL ML Management Data Analytics, AI ML Model Transfer and AI ML Services KPIs on Nov. 4th, 2023
16. Presentation on AI ML Mobile Device Requirement Specification on Nov. 20th, 2023
17. Presentation on 5G Advanced Release specification on use of AI/ML in 5G with 5G Standard specified Management Data Analytics, Transfer of AI/ML Models Training, Knowledge Transfer, defined AI/ML Service KPIs.
Link to the presentation on LinkedIn: https://www.linkedin.com/posts/ike-alisson-21173_5g-advanced-use-of-aiml-with-aiml-models-activity-7125775255331090432-nQvD?utm_source=share&utm_medium=member_desktop
18. Presentation on Beyond 5G (B5G) and 6G Network Capabilities with the 5G Advanced Release
The presentation focuses on elaboration of NGMN White Papers on Operators view on 6G and Cloud-native Manifesto related Network evolvements with the current 3GPP 5G Advanced Releases for new Services in B5G & 6G Programmable, Predictable, Deterministic Networks assuring Services with Performance and User Experience Guarantees.
19. Presentation on 5G Personal IoT Networks (PINs) enhancements in 5G Network and Application Layers to Akraino TSC on July 20 & July 27, 2023
20. Presentation on Challenges in (selected) Cloud-native adoption in (distributed & disaggregated) MNOs (5G and B5G) Networks need for Synergy between Compute, Storage, Networking and Communications
21. Presentation on "5G Advanced Capabilities presented on September 22nd to LF Edge Akraino Technical Summit, Fall 2022
The presentation aimed to share selected nsights 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.
Link to the presentation: https://www.slideshare.net/IkeAlisson/ike-al-pres-on-5g-and-5g-advanced-selected-capabilities-to-lf-edge-akraino-summit-fall-2022-rev-pa10-sept-22-2022pdf
22. Ike Alisson input to LFN (Linux Foundation Networking) 5G Super Blueprint Project (SBP) on selected 5G aspects (links below):
Link to the input: https://wiki.lfnetworking.org/pages/viewpage.action?pageId=74645746&src=contextnavpagetreemode
Link to the input: https://wiki.lfnetworking.org/display/LN/5G+SBP+5G+and+5G+Advanced+Capabilities?src=contextnavpagetreemode
Link to the input: https://wiki.lfnetworking.org/display/LN/5G+SBP+Cloud-native+NFs+%28Network+Functions%29+implementation+in+5G
Link to the input: https://wiki.lfnetworking.org/display/LN/5G+SBP+Security+in+5G+Architecture
Link to the input: https://wiki.lfnetworking.org/display/LN/5G+SBP+Use+Case+-+5G+Slicing
Link to the input: https://wiki.lfnetworking.org/display/LN/5G+SBP+Use+Cases+related+5G+Service+Requirements
23.7 FF (Factory of Future) - https://www.linkedin.com/posts/ike-alisson-21173_5g-advanced-factory-of-the-future-architecture-activity-7165498066043559936-kl7V?utm_source=share&utm_medium=member_desktop
24. Presentation on "5G and 5G Advanced" selected Capabilities to LFN 5G Super Blueprint Project on June 7th, 2022
25. Presentation on "5G Private Networks" (3GPP standard specified PNI-NPN/SNPN, Public Network Integrated - Non-Public Network/Stand-alone Non-Public Network) on March 9th, 2022 at LF Edge Akraino Technical Meeting, Spring 2022
26.5G Wireline-Wireless Convergence
27. Presentation on February 22nd, 2022 to LF Edge Board about Akraino 2021 Annual Review
28. Presentation on February 9th, 2022 to LF Edge TAC about Akraino 2021 Annual Review
Akraino OH Pres TAC Annual Review Rev A Feb 9th, 2022.pdf
29. Input on Akraino China co-operation with OpenGCC (Green Computing Consortium), EEC (Edge Computing Consortium) and SDNLab
KICS is the largest ICT Institute in Korea with over 26,000 members, 50 members, 8 domestic and 5 overseas chapters, and 30 specialized Research Groups. As the growth engine and leader of ICT in Korea that has achieved the greatest accomplishments in the world, KICS provides open networks for Universities, Corporations, Government-affiliated Agencies and Research Institutes to engage in Academic activities, Technical Cooperation and Policy Reviews in the fields of ICT-based Communications, Broadcasting and ICT Convergence Industries.
31. Presentation on October 4th, 2021 to Cloud Native Computing Foundation (CNCF) Telecom User Group (TUG) on 5G selected Architecture Themes on 5G New Service Capabilities
32. Presentation as part of the Introduction co-speaker to the Akraino IoT Area Webinar / Regional Developer Meetup - Africa on September 15th, 2021
Link to Akraino IoT Area Webinar video presentation:
33. Presentation on July 27th, 2021 on Self-driving/Autonomous Cars to Akraino Automotive Area workshop as part of the Introduction to Open Discussion
34. Presentation on June 29th, 2021 to Akraino TSC on " 6G selected Architecture Themes as Sensing Networks through 3GPP PIoT (PINs), ETSI SAREF eHAWs, 3GPP Core RAN Synergy & CS (Cell Free) Solution
35. Presentation on March 23rd, 2021 to ETSI MEC ISG about LF Edge Akraino Project
36. Presentation on February 19th, 2021 to Akraino TSC API Sub-committee on the "5G System and Service Providers (SP) New Services: Data-centric Approach"
IKAL 5G PINs Network and Applic Layers Capabilities
37. Input on IoT legacy OPC UA IEC 62 541 standard specification and 5G Personal IoT Network(s) (PINs) and oneM2M IoT Service Layer (SL) Platform Global Standard as a sub-catalogue to Akraino IoT Family Integration Projects (Blueprints)
5G Personal IoT Network(s) (PINs) and oneM2M IoT Service Layer (SL) Platform
38. Presentation to LF Edge TAC on Akraino Annual Review for 2020 from January 13th, 2021
39. Presentation to Akraino TSC API Sub-committee on the "Edge evolvement" in 5G Network Mobility and 5G ETSI MEC synergy from November 6th, 2020
40. Akraino liaison to LF Edge SOTE and input about Akraino Project to LF Edge SOTE Annual report from October 2020
41. Input presentation to Akraino TSC on Akraino Goals for 2020 from November 4th, 2019:
42. Contributions to Akraino API Sub-committee with Techical Reports and Specifications (TRs/GRs & TSs) on APIs evolvement from various SDOs such as 3GPP, ETSI MEC, TM Forum.
The link to Akraino API Sub-committee Docs Archive is: Akrano API Sub-committee Docs File Archive
43. Defining the procedure on How to request Documentation Review" at the Akraino Documentation Sub-committee
For further information and insight on the procedure defintion, you may look at the Akraino Documentation Sub-committee link: Documentation Sub-committee