 Good morning, everyone. My name is Yin Xiong. I'm the chief architect of Path Platform at Huawei. As Sam just mentioned, that yesterday we officially joined the foundation as a Go member. There's no better time. Thank you. So there's no better time for me to stand here to talk about Huawei, to talk about Huawei's Path Platform, what are we doing there, and talk about our experience with Cloud Foundries. Get my slides here. Yeah. So our Path Platform actually supports multiple scenarios. One of the scenarios is a cache, communication as a service, which I will focus a little bit on for today, just morning. Now, first of all, about Huawei. How many of you heard or know about Huawei before? Not today? Not yesterday? That's good. It's more than I expected. That's great. But anyway, Huawei was founded in 1987 in Shenzhen, China as a telecom equipment maker. So traditionally, we were hardware companies. But we still make a lot of hardware. But last 28 years, the company has grown to a leading global ICT company. By ICT, I mean the information and communication technologies. So Huawei provides wireless, wireline, and network services, network product, and network solution. But also, we provide enterprise IT technology, such as storage. We have our own database, and storage services, computer server, and end-to-end data center management solutions. So as you see from this slide, last year, year 2014, we have our revenue reached $46 billion. We're really growing fast. By the end of last year, we have about 117,000 employees. We are one of the big companies in China. Of course, we are one of the big companies in India globally. So today, the company is in the middle of transformation. We started a couple of years ago. As many of you know already, the cloud computing, the big data, the IoT has significantly impacted telecom industries. Our customer, telecom service provider, they want SDN, software-defined network. They want to watch and analyze their network functions. They want to use the cloud computing model to manage the network, to control the network, which they have built over the years. They want to open up existing network capability quickly to the users to reach more developers. They want to quickly develop new apps, new network function apps, where they can expose to the users, to developers. Now, we want to need innovations. We want to help our customer to realize the SDN and their vision. Now, we have a strategy called Softcom. Now, Softcom is an open network architecture. We are abstract the network function from the hardware. So we're talking about software-defined switches. So we're talking about software-defined routers. We're talking about software-defined firewalls. Software-defined everything. So those software network functions as a software, as an application, they're going to run the cloud infrastructures and they're managed by the platform. That's the Softcom vision. They want to help our customer to realize the SDN and NFV visions. Now, how are all this related to Cloud Foundry? And after all, this is the Cloud Foundry Summit, right? And we've got to talk about Cloud Foundry. I need to experience a history with Cloud Foundry. Although we joined the Cloud Foundry as a government board yesterday officially, our experience with Cloud Foundry actually started back in 2013, where we have a group of people, about 50 people, working on the Cloud Foundry. And we played one with Cloud Foundry. The last year, we released an internal version of our past platform. We call it Mushroom Cloud. That's based on Cloud Foundry. What you see in this slide is a home page of the Mushroom Cloud. If you can read the world, if you can read the home page, let me know. Besides the number, so far, we have more than 4,800 applications deployed. We have more than 35 users that has registered that they go to Mushroom Cloud to deploy the applications, the managed applications, the monitor applications. Although those applications are not production applications yet, but we really see a tremendous interest in our platform. We really see a tremendous interest in the Cloud Foundry technologies. People want to know, what's Cloud Foundry? What's the architecture? How do they work together? Can they scale? How do they monitor the applications? So we see a tremendous interest in the Cloud Foundry within our companies. Now, back to our scenarios. I mentioned earlier that we support many scenarios. Now, each scenario brings us a different set of challenges. Of course, there are different scenarios. Now, today, I want to share some of the challenges with you. And hopefully, in the future, we'll work through the communities that we can resolve or address some of the challenges that we are facing today. Now, in the NFA scenario, where the past managed the lifecycle of NFA applications. Now, in this scenario, the NFA application is very sensitive to the network status, because there are network applications. So where to deploy these applications? How many systems will deploy? And where to deploy? How to deploy? It's actually governed by a model. And that's different than as unique. And it's different than traditional IT web applications. And that's a challenge for us, too. Additionally, most of NFA applications, they are distributed complicated applications with multiple components. If we deploy each component as a container, then those kind of need to communicate each other, right? They need to communicate each other directly without HTTP protocol, because there are network functions. Another one big challenge to us is the monitoring systems. For if NFA application die from this detection all the way to full recover, it needs to have in seconds, if not million seconds, because there are network applications. So we cannot just monitor the resource, like CPU, memory, and IEO. We need to monitor the performance, the application performance indicator, like a response time, in order to respond to achieve that monitoring goals. Second scenarios, communication and service, which I will skip or talk about later on this. Like in many other big IT, enterprise IT, internally we have thousands of applications. Every day we have hundreds of applications in the queue to be deployed to be upgraded. So in the IT scenarios, the large-scale deployment, the deployment speed, how fast they can deploy, is the key to our IT scenarios. Can we deploy 300 or 400 containers per minute? Can we do that? Can we have hundreds of deployment requests at the same time for different applications? Can we do that? Those are challenging to us and to our customers too. Last but not least is Huawei Public Cloud. As some of you that, Huawei will launch public cloud services later this year. Our past platform actually will power and support the public cloud, which we're really excited. But at the same time, we face many challenges. As I have public cloud experience personally, the manager public cloud is a huge undertaking to us. So we want to make sure the past platform, the platform we build, the every component has to be secure independently. And every component has reliable under stress. And every component has an HAA design. Without this, you cannot manage public cloud. It's critical, it's important. Now let's focus on a little real scenario, the simple scenario is CAS, communication and service. CAS is not new. There are quite a few cloud-based CAS services out there. Now we want to share our CAS experience, how our platform and the Cloud Foundry play a role in the CAS overall solutions. So what's the problem we try to solve? I mentioned earlier, the cloud computing, the internet has significant impact to the economy in the industry. Traditionally, for enterprise, to build a voice, a video-enabled application, it's a long process. So how quickly can we get these capabilities out there for app to use to build a communication-enabled application? That's the problem that we try to solve. And this scenario we try to solve. And our past platform can be part of the solutions. So what's the solution? Now we start with the simple but effective solutions. You can review the solution two layers. One is the CAS API layer, which is hosted on the platform in the cloud. The second layer is CAS backend, where it resides in telecom network and on-premise. So it's kind of a hybrid cloud. But with the CAS API, the users, the developers, can discover this API, can subscribe it, and can just use it as a developer other applications. So how exactly we're using it? So we have built a CAS API surface broker, using Cloud Foundry's surface broker mechanism. With CAS API surface broker, we have a catalog API that developer can go there to browse the catalog, browse the API, to subscribe the API they need to. And they don't have to subscribe all API. And our past platform will create an API instance, surface instance, and monitor the API for them after they subscribe the API. Of course, we will scale it if you need to. Now, another part of the solution is we have integrated API management solution, which is based on open source. They integrate into the CAS API layer so that we can secure, throttle the API. We can monitor the API's SLA. This is very important. If you open up your API in the cloud, the security, the throttling, and the managed SLA is so important. Now, I want to show you a few use cases in these scenarios, in CAS. And the use case solution is very simple. The point here is you can build a voice-enabled application in hours, if not in minutes. Just call the CAS API through the URL. And the CAS backend will take care of the call, put the number you put there in your applications. And you can schedule the call anytime. And then the CAS backend will make a call by the sequences you put in your applications. And they will connect the voice with two parties together. Just so easy and simple. Now, this use case should be a little bit more complicated, but it's really cool. In this use case, a camera is registered to the CAS platform through the CAS SDK. And you can put a camera to monitor your family room, your living room, or your bedroom if you want to. And then once the camera detects a motion, you make a call to your cell phone. And your cell phone can answer the call and can view the videos from your cell phone. Really cool. And you can monitor your room. What happened in the bedroom? You can monitor that. Additionally, your cell phone can call the CAS API to actually control your cameras, control your cameras, how the angles, where you want to monitor. This is really cool. By the way, we have this real demo in our booth, booth 108. So if you are interested and want to learn about the CAS and then want to see the demo, please stop by booth 108. Another simple scenario. Just to show you how simple it is that you can develop communication-enabled applications, do it test, develop, and deploy on the same platform within minutes. As many as it is, it's simple with your API there. So as a summary, and also conclude my speech, I would like to see with open technology, there are a lot of opportunities in the tunnel coming that's where that we can innovate to help our customer in the cloud-based transformations. And we are committed to work with the community to build a robust quality advanced past platform to help our customer for them to innovate in these areas. End of the day, you make your customer happy, right? For that, I thank you very much for your time. I hope you enjoy your rest of the summit.