 Thank you, Arpett, and hello to everyone. Let me share my screen. Okay, next generation mobile networks Alliance. We are an operator-driven organization. We have a bit more than 80 companies at the moment in NGMM. We are growing and we embrace the entire value chain. And as you can see from our partner and membership slide here, starting from research institutes, but also, of course, embracing vendors and mobile network operators, system integrators and alike. We focus mainly on three areas. The first one is mastering the route to disaggregation with a specific focus on the end-to-end operating model of disaggregated networks. The second big topic is the green future networks, so everything around sustainability. And the third big topic of NGMM, as our name suggests, is 16. And in addition, we still support the full implementation of 5G with a number of projects. So I would like to jump quickly into the different focus topics we have in our work program and explain what the scope of this work is and, of course, also how this relates to the topic we have today here and there in the conference. So operating disaggregated networks, we delivered a first publication last year. It's about the context, the current challenges and needs observed by operators. So with the disaggregation of networks, it is clear that the operating model has to be adjusted and operators need to understand also the level of disruption it takes with regards to their processes, with regards to their skills, but also with regards to technical skills, technical tools. So currently, the project works on the industry status and roadmap. It will also work on the target picture delivered by disaggregation. It will consider the relationship with specific industry verticals. It will deliver operating model blueprints, looking at the different options, pros and cons, and main decision points, so helping operators to make their own decisions. Naturally, as an alliance, we work in the pre-competitive environment. And it will also consider the role and impact of disaggregated network testing because it has, of course, also impact on testing integration. And the project will submit requirements to the industry. And one example is the Kamara Alliance. I think we will come to this in more detail a little later in this session. About 6G. So 6G, we delivered the first driver's admission publication last year and just beginning of this year, the first publication on use cases, an analysis. And we started now with the entire partnership in NGMM to work on the enter and system requirements for 6G. Naturally, the standardization will start later via early stage for 6G, but it is very important to start right now considering the technology cycles. Green Future Networks. So in 2021, we delivered several publications. One important one was on network energy efficiency, but also we had a very detailed work on network equipment equity design and also considered how to develop metrics for an enter and services footprint measurement. We delivered also a generic overview on sustainability challenges and initiatives in mobile networks. And last but not least, considerations and requirements about metering for sustainable networks. In 2022 now, we started with four new topics. So one is semi-new because it is the continuation of the network energy efficiency work we have done in 2021. So it's continuing this year and it is also embracing topics like energy efficiency means through artificial intelligence. And it will also look on the network energy efficiency of disaggregated networks. We have a general work group about reduction of environmental impact. This includes the view on critical materials, so the reduction of critical materials usage, any impact on water footprint, but also again the eco design of our products. And the two big topics in addition are supply chain circular economy criteria for procurement leaders. And we work on developing an industry standard for a global green networks benchmark. So this will include methodologies, KPIs and also consider the data sources for such a benchmark. So those are the main topics we have at the moment. It's not the full work program but because we have not too much time today, I stop here and head over to Henry. Thank you Henry. Your introduction please. Thank you very much Anita and everyone. I'm just going to share my screen. Hopefully people can actually see that now. Welcome everyone. I'm Henry Kelvin, I've been head of this. So the GSMA, we're almost like the grandfather of associations. Certainly in the mobile industry we're founded in 1987 and we have over a thousand members. Not only operator, mobile operator network companies, there's about 750, but also ecosystem players and partners like NGMM and the Linux foundation. So we have around about 400 of those sort of things. We sort of focus on a very large organization and lots of activities and we've got four three main focus areas. Connectivity for good, which is really where policy and regulation actually comes from. It also does charitable actions for developing markets through our mobile for development, which is supported by grant funding. But mainly we focus on governments and the education of regulation and the impact of regulation in the industry. Then we have industry services and solutions, which is one of the hearts of the GSMA and that's really our technology angle. That's how do we ensure that everything that is actually produced, innovated by the likes of 3GPP were even led by NGMM who actually came out with the first 5G white paper. You see they're working on the 6G. We sort of look at how do we commercially bring that to the marketplace and make everything hopefully work and fix in the mobile industry. And then we have our outreach, which is the Mobile World Congress is in Barcelona, Shanghai and now Las Vegas. So they're the three major trade association events that we have across the years. Just in the technology area that we actually have. It is such a large scope of everything we actually do. So I'm just going to focus then on a few things. But in the technology working groups, which is usually the establishments of how things work in the industry, how things are actually interoperable, for example like roaming, how roaming works, how things actually connect together. There are eight key working groups that we focus on. But as the networks are changing and the practices are changing, we've decided to start to create two groups. One focused on IoT and the next focus on cloud networks, which we've been working on for some time. So I just want to give a little bit more detail in that and how we've been working through cloud networks. In the GSMA, we've been looking at how these cloud networks are going to actually support and change industry that we actually have. We more have a stack based software, stack based approach to how we're looking at architectures and defining specifications, but hopefully are going to employ the standardization and the ideas that are coming from other collaborative and STO activities. We have three main activity groups that we've been doing. For the last three, four years, we've actually had the open infrastructure task force that's been working with the Linux foundation on Acneet that actually looks at what is the store and compute models that we need to deploy in operators and operators deploy in enterprises so people can actually provide their software stacks, virtualization, containerization. So it's all profiled correctly and understood by everyone. Then we have the operator platform, which is trying to sort of start to expose and provide interoperability of the network capabilities and how they are integrated east of Westbound through interconnection or federation in what we're doing from exposing capabilities and one way to actually deploy and service the applications. And then lastly, the OPI group is looking at basically how do we then expose that up to the developer communities and enterprise communities. But as an operator association, we realize we cannot do that alone because we can only talk a certain language and as we get into the wider community of IT and T and how the IT industry is also converging very much on the networks, the mobile and fixed telecommunications businesses, it makes sense that we've actually pulled together with the likes of Deutsche Telekom, the Global Telco API Association and with Linux to create Kamera, which is really trying to actually establish where APIs and capabilities can actually be adopted by the wider ecosystem. So everyone's using off the same standard and really drive that market portion adoption of APIs. So thank you very much. So hopefully that sets up the discussion for us as well, Arpit. I'll hand back to you now and stop sharing my screen. Thank you, Henry. And I believe, yeah. Okay. All right. There we go. Awesome. That was a great introduction. Even though we claim that we know NGMM and GSMA forever, there's always something new we learn about the progress. So really exciting time. So let's, and again, for the attendees, please ask questions to the experts here in your Q&A box and we will answer them as they come in. I have a couple of sort of first questions to make sure that we are setting the context here. One of the asks from the community was to speed up open source standards, whether it's standards or specifications. And I think there's a difference between the rigidity and the default kind of let's just do it this way type. How have you seen in the last couple of years the evolution and the speed of how the ecosystem wants to work on these specifications or standards as we want to call it, as we go through the 5G deployment and revolution. And as you know, the context of this is cloud service providers, enterprises, and telecom, they all need to work together in this new era. So Anita, if you want to start off, and I know it starts off with this aggregation, obviously, but how do you see the overall progress in the industry as these ecosystems come together? Yes, and we work on the requirements level. And of course, we consolidate and submit the requirements to the industry and we cooperate with all different type of corporation partners, so including the classical standards development organizations, including GSMA, but also including now the Linux Foundation and the Oran Alliance and alike. And I think the ecosystem is going and this yet alone shows that we need, of course, to also find new ways of work and new corporations here in finding the right channels and submitting requirements. We are not producing a code by ourselves. But for instance, an example would be now the foundation of the Kamara Alliance. Developers, of course, we need to balance between the speed of innovation and at the same time to have a reliable, let's say, de facto standard also when it comes to open source. And I think for developers, it is important to develop funds and use it multiple times. And looking at the example of the Kamara Alliance, so maybe you will explain it a bit more in detail, it will be important for our Operating Disaggregated Networks project. So this regards to requirements. So it will have impact on the way operators monitor, integrate and test and operate the networks. And people provide requirements to the Kamara Alliance. Of course, it is not a mandatory requirement, but it is a requirement submitted by a large number of operators and other ecosystem members. We have an NGMM working on those topics. And I think it's always a matter of the balance between speed and at the same time submit reliability and specific form of still having standards to have certainty for the developers that they don't need to develop a specific code for each of their customers. Awesome. And Henry, you want to walk us through the whole Kamara setup and how quickly it came about and how specifications and code are being handled. Just as an example, because I think Anita is right, this is a perfect example of how foundations and organisations and alliances come together and help the end user, right, in this case operators. Yeah, just check, can you hear me? Yeah, yeah, we can hear you. Yeah, great. My video is just frozen at my end. So if I don't move it all, don't worry about it, I can stand still alive. Yeah, for sure. And just the first thing I want to say is it's been a pleasure working with the Linux Foundation, NGMM, also TM Forum. I think one of the most important things we've got to actually stop is duplication of activities and we need to focus all the attention of what everyone's doing through one vehicle. And Kamara came about, I think, only since October last year, October 2022, where Deutsche Telecom was very keen to actually bring together operators, bring the ecosystem and the players in the ecosystem together, so that the telco APIs can be exposed. They're looking at capabilities that you might not think about at this point in time, like on-demand quality of service APIs, which is very important in things like Edge Compute and also network slicing and being able to provide the resources to the developers. And really, when we actually look at it, it's very difficult for the operator community to actually talk to the developers because we've taught different languages. And that's where the Linux Foundation has been absolutely critical in being able to actually be able to parse almost through what we actually need from our capability in networks because, don't forget, there's 750 networks behind us. You want one way to talk to those networks. You don't want 750 ways to talk to those networks when you're a developer looking for some resource in a particular market, a particular region, maybe with a particular operator. That's irrelevant to you about, do I go with Vodafone? Do I go with Deutsche? Who do I go with? You just want resources in Berlin or you want resources in London or you want resources in particular places to get the improvement. And really, we've put the fundamentals together where we can contribute the code. Software is how everything is going to be built and that gets built at such a pace these days that we have to respect that that code needs to be actually utilised in a particular way. And the most difficult aspect, I'll be honest, was the IPR regime that you actually put around this. Where is that? That actually went to a vote across the whole thing and we've decided on actually two licensing. So it's clear, very transparent for when developers are actually using the APIs and things like that, that they can be comforted and they can be secured by they know the IPR regime and what they're doing and how they actually do it. I think that all speeds up. It moves the hurdles, it moves the barriers. Just speeds up the implementation. Awesome. And I think that's exactly the goal of these kind of activities and collaboration. If a standard or a specification exists, code it. If it does not exist, code it and push it upstream. Or if it doesn't exist, work together so that you have that quick feedback loop. So very good. I know there are questions. I think the first one on the requirements was answered. There's also how there's other questions coming in. I know we're going to sort of quickly run out of time. Wish we had more, but any closing statements on this whole philosophy, I'll start off with you, Henry, this time. I'll just reiterate. If we can stop any duplication out there and we all work together, it's going to be so much quicker. And we want the developers and the enterprises to be happy at the end of the day. Oh, well said. Anita. Nothing more to it. I think collaboration is really key here. Yeah. And I know we didn't get a chance to talk about green networks today, but that has been a hot topic of how the telecommunications industry can enable other verticals. So please download the information on NGMN and green networks and we will have a lot more deeper sessions because that's a big topic coming up in 2022. So with that said, thank you very much, Henry and Anita for joining and really appreciate it. Thank you. Thank you. Thank you.