 Ladies and gentlemen, good morning or good afternoon. It's my pleasure to be here to give a presentation on the Open Network and the China Unicorns practice. Talking about Open Network, we need to recall SDNFV. 10 years ago, SDNFV was proposed to transform the token network from the monolithic closed system to a distributed open system. We wish that the network would be the standard decoupled, programmable, and lower complex under the OPEX. In these 10 years, we say that a lot of network-related open-source communities emerge to accelerate the SDNFV development. Some of them, such as Open Daylight, OPEFV, OLNAP, have joined the network umbrella of the Linux Foundation RFM. Why Open Network is attractive to token operators? I think there are three main reasons. The first is to speed up service innovation. Obviously, Open Network is more flexible and scalable to enable quickly service innovation, especially for the to-be market data and the vertical industries applications, because to be a market data, we need a flexible service innovation. So service flexibility and agility will help operators to resist the computation from the OTT and the cloud operators. The second motivation is to reduce the OPEX and OPEX of the networks. By introducing common hardware and software, the network could be effectively cut down, especially for the newly competitive operators or in the greenfield of the incumbent network operators like the China Unical, Open Network could be first introduced. The third one is to build a healthy industrial ecosystem. Open Network will help operators to build a multivendor environment to avoid a sink-vendor lock-in. So I think this is just really a main reason for the telecom operator to do the Open Network. This is China Unical attaches great importance to Open Network under D. And it's actively involved in many open source communities, including our friend, our IFA, our long tape. Our goal is to build an end-to-end Open Network from an open-run, open-edged cloud-native core network to a disability-transport network. But I think it is a long journey to construct an end-to-end Open Network. We have to do this step-by-step. Firstly, we will focus on some key parts and the captivated Open Network ecosystem. Here I will give you a brief introduction to some of China Unicorn's Open Network under D works. The first one is Open Run. Radio access network accounts for the vast majority of the network investment, usually about 16% to 17%. So the Open Run is very attractive for telecom operators. China Unicorn is actively involved in TIP and the Open Run allows to promote the development of the Open Run. Open Run should be the wide-box hardware-based. It will be the software and the hardware decoupling. It needs an open front hall so that D.U. and R.U. could conform the multi-vendors. Radio-intelligent controller, locally, is a key software for intelligent control and management. China Unicorn has already developed a cloud-native 5G base station, which integrates base station controller under the edge computing as well as the edge application platform into the one box. This 5G station could be used in private industrial network. Another important element is the Open 5G cloud network M4 interface and wide-box UPF. Open M4 interface is key for enriching the vertical solutions. China Unicorn has defined wide-box UPF and M4 standard. We have developed lightweight and low-cost UPF for the private 5G network. So that we could provide customized solutions for the vertical industries. Actually, now let's talk about edge computing. I think edge computing is the most important opportunity for promoting the Open Knock. With the development of 5G, China Unicorn deployed many mobile edge computing applications for the vertical industries. China Unicorn's MEC platform is initially designed following ETSI and 3GPP standard. From two years ago, more features beyond the standard are introduced in our MEC platform, including the world's first MP2 interface and the open self-service capabilities for customers. Now we are developing a more open edge computing platform and build rich ecosystems with our partners. China Unicorn is actively involved in the Aquino Open Source project and developing the unified cloud-native-based parts architecture to support both the CT and IT capabilities and the expansion of the unified northbound interface. Now let's talk about the optical transport network. Optical transport system is usually tightly closed. The reason is that the open object network has attracted great attention for data-centered interconnections. This could be coupled to the optical layer and the electronic layer. China Unicorn has developed a cost-effectively open natural DWDM equipment for the natural data center interconnection applications. We have developed a unified management controller on the Arc Street based on the standard southbound interface and northbound interface to support the multivend equipment interoperational. Yes, to develop an open edge transport equipment, China Unicorn has developed a network-equipment operating system. We call it CO-North, China Unicorn Network Operating System. CO-North is based on the open interface and the open source. But we also extend functions to satisfy the requirements of the telecom network's high reliability. Based on the CO-North and other open source software, including Sonica, we developed the service of customized wide box switches and the agile transport network for the data center and agile applications. Yeah, finally, the open network is always complex, even a controversial topic. I think the development of the open network is still in the early stages. The performance of the many open network equipment must be further improved to meet the telecom grid requirements. To support the open network, operators need to strengthen its network integration and under-delay capabilities. We also need to continually enrich the open network ecosystem. Meanwhile, we need to change our business model, including equipment procurement, network construction, and operation models. Anyway, the objective for the open network is to better serve our customers. So we should provide an open API and capability explosion platform to support our customers' service innovation. Yeah, today, I think we're still facing many challenges. We need to move to open network step by step. We still need to make greater efforts to make the success of the open network and open network equipment and solutions. That's my shout. OK, thank you. Thank you very much. If you could stop sharing, then we can do the video. There you go. OK. There you go, perfect. All right, very good, very good. So again, for participants, please, if you have questions, put them in the Q&A box. We will answer as many as we can in the time slot. I do have a couple of questions come in, and I have one as well. It was really good that you put each layer of the network from applications, cloud-native orchestration to network to data plane and optical all the way down, including the noses that you are looking at open source. And I like your suggestion that everybody should be doing this in steps. So the question for you is two questions, actually. One is on the optical side. We have not been very active on proactively putting communities for open source on optical, given that whether it's DWDM or Metro or Core, it's a very, very proprietary technology for the capacity part. But there is definitely control plane work that has been done that is standardized that we could take advantage of. So do you have projects that you want to bring to the open? Or do you see any initiatives out there that the rest of the community can benefit? And again, there don't have to be differentiation. It's just standard plumbing on the control side for optical. Yeah, for optical, the industry has already done a lot of work to disagree to the optical layer and the electronic layer, such as open loadable project. Yes, this year, China Unicorn has done a lot of work on the metro optic transport to decouple the optical layer and the electronic layer for the data center interconnection applications. We have already developed such systems. As for the control layer, we will define our own interface. So it could work for multi-vendor, but it is still China Unicorn's standard. So I think that the community should work together to develop a common interface. It is very important. I think that on Apple and other communities could make some contribution to this. Yeah, no, that's why I was bringing it up. So that's great. And the other question, again, for people who want to put questions, please do it in the Q&A box on your right. The other question is, as these projects and pieces come together and it's step by step, one of the initiatives that LF Networking has is the 5G Super Blueprints, where multiple projects come together. If you participate and as you participate, you can get a crane or integrated with ONAP, integrated with ORAN. And a lot of pieces come together. OPNFV, now known as Anuket, they all come together. Where do you see that helping you in China Unicorn and what can the community focus on if they were to bring projects together in a blueprint, which will ease the deployment? Yeah, because there are many projects that at this moment we mainly focus on agile applications. Yes, we want to bring some open source project just in the agile area for agile computing. For open switch is also used in agile. So at this moment, agile and mature is your focus. Okay, got it. Excellent, very good. Well, great. Thank you very much for this insightful talk. I think it aligns very well with what the community is doing. And we really appreciate you taking the time and speaking to this audience. Thank you very much. Yes, thank you. Bye. Bye.