 Konnichiwa. Hi, this is Tina Zhou, Enterprise Architect for ARM. At the same time, I'm also the Acreno Edge Stack TSC Co-Chair. I was the chair, Co-Chair last year, I just got re-elected for this year, 2019, 2020. Thank you for all the support, especially from the company's entity, and Renesis, who are the active participants in Acreno. Okay, so first of all, I would like to talk about Acreno Edge Stack Routine. Why? Because this morning, like James, Chris, and all the other speakers have already talked about there are many open-source projects in this foundation and also in the other community. But more important to the end users is about the deployable. Whether this is deployment-ready. So in this spirit, Acreno is more like a deployment-ready and oriented to the deployment and production-ready. So Acreno take the specific use cases, like the enterprise use case, IoT use cases, and cloud use cases, turbo use cases, and select the specific hardware piece and the software. The hardware could be based on open-edge or specific hardware. The software is a sector for software stack or some integration of an upstream community like Venet, his own app, and the other things. And based on this piece of software and hardware, we do the fully CICD to do the integrated, continuous integration and continuous deployment. So we do have a community lab which is located in New Hampshire University, and we have many validation lab across the whole world in Europe, in Japan, China, and the US, and Canada. So those validation lab is corresponding to some specific blueprint. It connected to the CI via the Jenkins. You can set other Jenkins peers from your validation lab. You can also do the CD. CD means you push the deployment logs from your validation lab to the nexus located in Acreno. So also we provide the community lifecycle support. All the project could be at the incubation and then becomes mature and core, and then it becomes the archive projects. So the full community lifecycle support it supports a long-term support. Finally, the production quality is because all the blueprint have to be like driven or specific, have the involvement and engagement from the end user. That's why we can say it's production quality. So what are the benefits we bring here? Benefit number one, low cost, because from the end user point of view, no matter what, in the end of day, you still need to call all your vendors to your lab or to your trial to do the downloading, integration, and testing. So if you do it in the community, it saves your OPECs in advance. Also, it could be larger scale deployment because we have the newly smart need blueprint proposal. We have at least one, two, three hyperscalers and at least one, two, two operators are very interesting on that. It becomes one common software stack could be used by server end users. This is how you have this blueprint as a recipe, but it can be used. Like if you have the unagi rice, the recipe is unique. You can make all the unagi rice all over the Japan, all of the work. That's my favorite food, by the way. Thank you. And also zero touch provisioning because we do the edge cloud zero touch provisioning here. We have different blueprints, some of them using on app or the Kubernetes and the other orchestration and controllers to do the zero touch provisioning. And giving you an example, the rack, they use ISO images to build the binary. So you build the ISO images as a foundation of the software stack. But then you can do the telecom, telco appliances. You have Siba for the GPOM department. You have rack for the radio 5G department. Just like a slicing of the telco appliances. It's very easy to divide. For the industry adoption, we have many industries, like we have We Bank, which is more like PayPal in China. It's very big. They bring their use case in. We have the industry IoT and we also have like insurance company, the VNF vendors, they have different kinds of industry. In this way, we can accelerate the industry adoption of these blueprints and this technology. Lastly, I mentioned the hardware. OCP Open Edge is the telco hardware specs. So if you know the telco appliance, the blueprint family integrate them as an upstream hardware requirements. So all the hardware pieces in this blueprint family will need to comply with the OCP Open Edge. Of course, there are more like OCP hardware. We also have the other OCP rather than OCP and the other like we have open power. No one mentioned here, but maybe in the near future, somebody said, hey, this is our hardware requirements. You have to comply with this. So this is a concept of Aquino. Before Aquino, after Aquino, the developers. So before Aquino, the developers has to go to the upstream community and download and test the software integrated them. But with the blueprint, you already do the work in the community. That's the whole concept. So let's have a look what Aquino release one has released. This is from June. But today is December 16th. We've already have the R2 completed internally in the community. The announcement from the media will be next month in January because of the holiday season in the U.S. So let's have a look. From left to right, you can see the gateways. It could include a thin gateway or a thick gateway. Elect means Agilite IoT. This IoT gateway and the UCP for SD-WAN have been deployed in about 10 tier one operators in the whole world. There is one more, which will be released three, which is led by Tencent. They have already deployed in Tencent's buildings in China in Shenzhen. And also they have the plans to deploy in several other tier one cities in China. The RadioEdge Cloud, correct. It's located in the industry or the Telco RadioEdge applications or HCI. So this is part of the 5G deployment for the configuration and deployment on the multi sites. And IEC is integrated Edge Cloud could be deployed in the mini data center edge. Top one means the small board, like Makilda Bing. Top two means it can run on the edge server. There is a type four, which also part of release two. That means you can do the AR, VR. They have done the virtual classroom, very interesting. If you go to Wikipedia, you can see the teachers and the students are, looks like in the virtual room. The Far Edge Styling X provides the integration of Styling X to the very Far Edge distributed cloud. It can run in between the mini data center and on-premise DC edge. So the provider's access edge is led by Red Hat, the OS company, but they do very good job here to work with the operators to provide the PAE here. Last thing, not the only thing, the network cloud grouping family has about seven blueprints. From release one, we release the unicycle and rover. This term means rover is the very end, far end with one server. Unicycle has about six to seven servers with two to three control node and the rest are the computer node. These are part of the telco and cloud edge to help operators to deploy the 5G. So people may ask, so we have release one, but how about release two? Release two is more like the industry enabler and also the enhancement to the release one or the existing blueprints. Besides the enhancement, we have a lot of community lab and validation, we have more and more either following foundation. Thank you, Sim. I hope he's here. For them, also the board budget to purchase some more hardware and pay for the lab stuff there. And also it's very kind to some companies donate their spare hardware here so we can do more work as a community. The mandatory security performance testing, it's very interesting. Starting from release two, we have the security performance that makes all the code will be scanned by the sonar cloud, which is a static code scanning. But also we recommend several dynamic code scanning and security mechanism. If you wanna go through the maturity review and the blueprint has to go through this more secure mechanism. And for the performance testing, we have the layering mechanism. Like there's a feature project called a keynote blueprint validation framework. In this framework, you can have the hardware performance testing, operating system performance testing based on CentOS, Ubuntu, etc. And also the Kubernetes performance testing. We selected the sonar cloud from the Kubernetes CNCF community and test it here. So we do set up a liaison official channel with OMN, ONF, ONAP and LF edge and all the other community. So maintaining this official channel is very important because we do take the upstream first methodology. Don't fork, so we don't take any technical depth. And if we do find anything we need to add, first we go to the upstream community, ask, hey, we do have these questions, can you please add this new feature? If they say, oh, this is not generic feature, it can be developer within a keynote. So we come back to a keynote and create a feature project, which means the developer and the project then we develop it there. And the feature project will be used by multiple blueprints. The lastly, API specs. API specs provide the API of some of them in line with the etymic API standards. So we provide the implementation divided into two groups, the developer facing APIs and also the infrastructure APIs. So we have the wiki on the community lab. If you're interested, go there and have a look. You can find out the different lab. As long as you have your VPN, we open a credential for you, anyone can use it. It's open to everyone. Okay, let's have a look as an example of how we work together with O-RAN. So O-RAN is RAN, this application. It has the VM, virtualize the network elements, provide the wide box hardware and standardized interface. For bottom to up, you can see in the 5G network, if you think about the layer one, layer two, there are many RRU there. And then coming up, there's a DU on the data plan. And then some CU for the controller and control plan. Giving, if you're looking up, there was a RAN intelligent to controller, which is we call RIC. This is the part we already have a blueprint. Above it, through the A1 interface, we need to do the design, inventory, policy, configuration, et cetera, which is the part of like a subset of O-NAP. So we take the lightweight O-NAP there to fulfill this functionality. So incremental community blueprint can supply an end-to-end edge stack to support NMBI. We call it a virtualize the network elements per O-RAN requirements. In the next page, you will see for the RAC, which is the first blueprint doing this under the telco appliance blueprint family. We take RIC, RIC is RAN intelligent controller as an upstream community software component. We integrate it, you can see on the right hand side, the blue part is the equivalent blueprint. Left hand side is for O-RAN SC. O-RAN SC is O-RAN software committee. So this part, everything below the RIC, you see RIC as apps don't have a pointer. Oh yes, in my pocket, sorry, I have a jet lag. Should I, oh here, okay. So this part of RIC, we include the RIC apps and RIC basic function and RIC parts. And it communicate with this part is TA telco appliance, which is the blueprint family. We have some lines up code building ISO images and they communicate through this NOSbound interface APIs. For here, from the middle well and like the center OS and these things are the fundamental software stack for TA and RIC is the application as the appliances running on top of that. We also have something called CBA, the software enable broadband access can also run as an appliance. And on the left hand side, you can see O-NAP here and you see the regional controller. Regional controller is actually a feature project within a cradle and the regional controller as a feature project has been used by RAC and also the other blueprint like the Unicycle in network cloud grouping family. All right, whether the hardware pieces is part of RAC is a discussion point, but there are five flavors hardware are used for release two, only one flavor is validated is part of release two. And the others may be the release three. It's like which one has been validated but the CICD pipeline and enablement are happening on all the other flavors. So I know there are many vendor companies in Japan. If you wanna join this blueprint or this blueprint family, you can bring your specific hardware first, download the software stack and install and integrate onto your hardware to see whether it works. If it works perfectly, that makes your compliance with this blueprint. If not, then you can find out whether there's any software patches you wanna submit. So the benefits to do all of this RAC is like we can do the fully integrated appliances to adjust our rent requirements. We can only also do the fully automated zero touch provisioning because you can do it all through the region of Tola. And it supports both X86 and ARM instruction set and support the OCP YBox and OEM and the other hardware. So far this one, who knows where it is. This is a Nokia L-frame open edge server and the HPE and Dell servers and mobile servers and APU servers. Okay. Okay. So in detail how we liaison with the other organization like we provide the liaison between O-RAN and Acreno. So first we take requirements and specifications from O-RAN working groups and then they input into the next foundation community and we key and JIRA. And then we integrate O-RAN code into Acreno community blueprints. At the same time, we also need Kubernetes, O-NAP, the software and the hardware, OCP, OEMs as an upstream integration. You see these two arrows into this blueprint. So we do the blueprint validation and lab testing and deliveries here. At the same time, there's additional integration in O-RAN and C happens here and it will feed that loop to here. The integrated additionally was sent the input to the end-to-end certification finally to the user which are the all the operators here. Let's have a look at some of the blueprints as an example to show you how Acreno works. So this is IEC, the integrated edge cloud blueprint family. IEC can run as an individual edge or individual blueprint. It can also be used by the other blueprints as a component. It supports x86 and ARM instruction set. It supports cloud native applications. So it takes the line way approach from bottom. We can see there were switches and gateways as a network equipment and going up, we can run the networking edge platform or edge server here. This FPGA may include the Xilinx FPGA and the GPU from NVIDIA and AMD. Above it, in parallel, you can have the different flavors as my links. I mentioned we have a Smonic blueprint. We have a Smonic OBS offload feature project. They are all at the blueprint proposal or feature project proposal stage. The Smonic's flavor include Broadcom. They contributed from the Stingray software stack and also from Mellanox, also from Xilinx. Integrated accelerators. These are the other components within the accelerations for hardware. This is not really the real-time OS. It's not the audio OS. It's more like the Ubuntu and CETOS. Above it, there is the data plan like SIOV and DPDK support. On top of it, there are three blocks, the infrastructure orchestration and installer, networking software and controllers. So Kubernetes across is most important in the orchestration like many of the blueprints are using Kubernetes and few. It takes from the OpenMP, from the LFN and can pass as one of the containerized installer is being used here. We support different kinds of Linux system networking and VPP and OBS are two alternatives for the forwarding plan. So OBS is more the existing one. The VPP is part of FIDO because it provides the high performance forwarding platform by using the mechanism of the batch of a packet forwarding. On the controller, Calico is part of the CNCF project and Network Service Match is the emerging technology and acts connect with the contribution from VMware. And then continue VPP is already upstream from FIDO community. OVN Kubernetes is more to how to manage OBS. So we have the controller, networking software and infrastructure orchestration in installer. Let's have a look. What kind of different applications we're running or services? Knative is more for service and could be flow for machine learning, edge apps for IoT services. We can run either on bare metal or containers. Of course, we can take some lightweight app orchestration on the top. Then we can give an example. We talked about the architecture support on Radio Edge Cloud Rack. You can see from here, we need to read down the remote installer providing some arm packages for remote installer and also arm images and packages for center OS. Also, secondly, the arm solutions for hardware management. In this case, the rack can support multi-arch. Okay, this figure is only part of the release two but it can give you an idea how the other blueprints can use IEC as arm enabler. You can see from here the rack, the Radio Edge Cloud, we talked about this. It can run directly on the telco appliances and the Siba, it's more for the Japan case. It runs on TA and also IEC because all the Siba code is actually from ONF code. Any changes will go there. Currently, it builds on TA, it can run directly and also the Siba code on IEC can also run. You can get today. And the Siba on TA are still under development from the AR-64 point of view. Micromech is interesting. There is a project from Finland. It's called the Smartest 5G Road. They build the Smartest 5G Road all the way from Helsinki to the very west city in Finland. The use case is, the first use case is to, who can guess, to avoid the collision of rain tears because the rain tears going for the Christmas gift so busy on the highway, you try to avoid the rain tears bump into each other. This is just one use case. The other one is it can do some smart navigation until the cars, it's very icy in front and weather changes, please pay attention or some road is blocked and please select the other way, something like that. They have put some very small boxes in the light poles in between the base station and below the light poles. So it's more like the very far Micromech. And then added, I mentioned already the edge light IOT previously, three, four minutes? Oh, time flies. Okay, then IEC type four AR-VR edge. I mentioned for this version is for the edge for the virtual classroom and the next release release three by middle of 2020. There will be more data visualization added and the connecting vehicle I'm gonna describe in the next page. It has been deployed through the TARS project and in China from Tencent. The AR edge was powered by Baidu and Webend. And 5G Max size, it's more like B2B2C like China Mobile give the B2B 5G services to Tencent and Tencent give the B2C services to any user including the cloud gaming, including the live streaming and including the HD video. Okay, this is how Tencent's Connective Vehicle Blue Plane uses. It can do the location accuracy so you know where it is and the smart navigation is similar to Micromech and the safe drive improvement telling you, okay, you gotta turn change the lane but there is a car there because sometimes you were blocked by the blind point. You cannot see it as a driver and also reduce the traffic violation. It's all telling you from the Mac platform to the car. How can we make this happen? And this is the Connective Vehicle Blue Plane architecture made by Tencent together with in Chinese is Dongfeng Group. You know, it's called East Wing Group. It's the number one biggest the automotive company in China. The integrated Edge Cloud AR-VR stack. It's similar because it's part of IEC Brooklyn family. You can see it just changes more like a lightweight removed unnecessary part but this part has the GPUs from the AMD or the MEDM. Okay, this is a demo made by IBM all the way from the stage one to collect some signals, chance data and then do data collection and data application. There's the Edge server and then you can do the data visualization. Think about we have 5G or Wi-Fi in this room but not every spot had the same strengths of the signal. Then you can see a lot of a green light, green, yellow, orange, rainbow like a Skeeto. It's American candy. If you like it, you will see a lot of spots. You know, the green part maybe have the strongest signal. This is one of the VR demo here. Okay, so this is an overview of our two groupings. We are announcing very soon but this is what we complete including the Connective Vehicle, TA Grouping Family, EDIT, KNI, Dental Cloud, IEC and ICN. Okay, how to get involved? We have a website, a wiki and I think my slides are ready and here. No worries, last page. Take away. So, APNNOW is proudly announced with stage three project because in LF Edge we have different stages. Only two projects and we have seven projects only to reach the stage three. That means we can end the acceleration time to deployment from projects to products and production. We have 10 more blueprints including all the segments of use cases and the new blueprint includes the Edge AI, 5G Mac and Tom Critical Edge and other tours and the new community lab and the Edge APIs within the LF Edge projects. That's about it.