Thank you for having me here. Thank you that I can speak on behalf of the LSP Potential Consortium. I was here before in another role. I'm responsible for the EIITAS implementation at the Federal Ministry of the Interior and for Community here in Germany. And besides what I spoke about before and yesterday when it comes to the German wallet prototypes, LSP Potential is the forum where we test the prototypes and we are the largest consortium of the four LSP consortia with partners from over 20 member states. So we have not only European member states but also the Ukraine as part.
The potential consortium is led by France and Germany. We have over 140 participants from both industry and from public sector. And very important is in all six use cases, I'll speak about them in a minute, in all six use cases we have in each country the respective authority involved. So for example in the banking use case we have the responsible regulatory authority in Germany, it's the Ministry for Finances within the use case group.
So we can not only talk about technical requirements but also about legal requirements and have this connection between legal and technical requirements when it comes to the implementation of the EIDAS regulation. So we have three main objectives within LSP Potential and this also shows somehow the difference with the other three consortia. We are not only the largest but we are also quite a decentral consortium as we have the responsibility within the use case groups and also within the national team.
So we don't have a central wallet and we don't have so many central structures as other consortias with the benefits but also with the challenges coming with it. So I'll talk about the wallets in a bit but for the use cases we are focusing on the use case, on the six use cases and their requirements.
At the same time we are looking at the technical interoperability so from the LSP with a focus from the use cases we are commenting the architecture and reference framework, looking at the interoperability and we also contribute to the security and the privacy analysis on an ecosystem level with the knowledge from our use cases. So in case you haven't heard about our six use cases here you see the overview about the use cases, what they want to solve like when it comes to remote flows or proximity flows so we have two use cases which also include proximity flows and which credentials.
So we are very let's say PID focused. So most of our use cases include primarily identification and authentication. In one use case, it's the use case four, we also have the mobile driving license as an electronic attribute and in the other use case we have additional QEAAs depending on the implementation but it's mainly identification. And down there you see the participants and we have different leads so for example Germany is use case lead in use case three and use case four, Austria leads use case five, Hungary use case six and Greece use case two and Netherlands use case one.
Use case one is clear, it's like we're using the wallet to identify towards e-government services so you identify yourself and then you can use governmental services. It's quite easy. Use case two is using the wallet to open a bank account. So mainly identification process but the banks need probably also additional information beside the main information which is in the PID and the PID is different in different countries so that's a big discussion.
That's like one example I'm always making when we discuss with the banks we learned that for example when you want to open a bank account in Greece, you need not only the name and the address and the birth date but you also need the name of your father.
And that's then a discussion like on a technical and on a legal political level so either all other member states provide the name of the father with the PID to allow their citizens to open a bank account in Greece or the Greek colleagues can find a way to accept the PID from another citizen from another member state without the name of the father. The question is which is like technically and which is legally more feasible and that's just one example of many so we're going through these use cases like this.
We had the specification phase in the last year and now we're starting more the implementation phase. Use case three is using the wallet to register a SIM card for like a mobile phone contract with an MNO. Use case four is a mobile driving license for two sub-use cases. The one is for car rental and the other one is at a police control in proximity. And use case five is the qualified e-signature which is like not a use case on itself but like across other use cases as well.
So for example if you want to rent a car maybe you want to sign also like a rental contract or an assurance coming with a rental contract and stuff like this. So you need the signature for other use cases. And the e-prescription is our e-health use case, the sixth one. And yeah what I already said we have some decentrality within our consortium so we don't have a consortium wallet.
The member states as we are a member state driven consortium are responsible to deliver a wallet or at least one wallet prototype for their partners or for the partners of the other countries as we want to do cross-border testing. It's also an interesting point that our partners, the German partners approach us and ask us about the German wallet prototypes. This is the point where I am telling them you have to focus especially on the prototypes of the other countries because you want to do cross-border testing.
So for you it's interesting as a German bank it's interesting how the French wallet works because you want to test a French citizen opening a bank account in Germany more than a German citizen opening a bank account in Germany because the goal of LSP is the cross-border use case, the testing of the cross-border use cases. So 15 of our members plan to have a national wallet prototype and four don't have a national wallet prototype.
At the same time like the four are obviously using the EU reference wallet and some of our members plan to use parts of the reference wallet and parts of old implementation. And that's our way ahead.
So we, as I already said, started with like the technical and functional specifications last year. That was the first thing and we're just about to finish this very crucial part. So the goal is to know for each use case which are the requirements in each country, which can we like provide in each country. So can we provide the name of the father?
Yes, no. How complicated is it? And after this phase, we start with the national implementation and national testing phase. So by mid of this year, we start testing of national prototypes as soon as they are ready, step by step. So every partner, as soon as the partner is ready, integrates like the interface with the wallet prototypes. And by the start of next year, we start the cross-border testing. And that's the crucial part. With the cross-border testing, we test German wallet prototypes in use cases, for example, like to open a bank account in Greece, to rent a car in France, etc.
So that's really interesting. So the first half of 2025 is the part where we test the interoperability cross-border and the projects coming to an end by mid of next year. And then we will have the learnings and we will know when it comes to real implementation, because that's just piloting with no real user data, what we should look for and what we should aim for. So the whole project is with dummy data, no citizen data involved. Just to make clear, that's quite important when it comes to privacy and data protection.
So the steps ahead and also, I think, important information for all of you is where can I join, where can I be part of the journey of LSP potential? We do have some next steps ahead, especially we plan to have an interop event, like a bring your own code event. So the idea is that we create the interfaces to the wallets from the issuer side and from the relying party side.
Our goal is to provide wallet prototypes, the partners within our consortium which are mainly relying parties, but also potential issuers, they need to know what to integrate on their side to be ready for the wallet prototypes, and that's their task, so they have to integrate it somehow.
So we start this interop event where they can work together on the code, and this event is open, so other partners can join who want to join and create open source code which can be used, and, yes, that's basically it, so, from our side, we provide the standards, we provide the requirements when it comes to the wallets, when it comes to the interoperability, and everything else will be solved within the consortium and within the interop event which is taking place later this year.
And yes, as it's written down, everyone's involved, so I'm happy to see some of you with the interop event and helping L3Potential and, therefore, the whole EIDIS ecosystem in these 20 member states to be developed in a very good manner. So thank you very much for your attention, and, yes, happy to work together with you. Thank you very much, Moritz. I'm calling in the previous two speakers. One of them has left.
Moritz, you can also stay because we're doing the questions at this moment. So there are two questions that came in online, and I think one is easy, that's one for you, Thomas. Is it a plan that the social insurance organisations would act as issuers to onboard the national or European social cards or credentials into the wallet?
And if so, how is the plan to onboard them on individual wallets? Well, of course, yes. The answer is yes? The answer is yes. We are the issuers, so we are keeping the data and e-cards or PDA1s or other credentials are coming from the official competent institutions as issuers to the wallet. Okay. And the other question, is it correct that Apple and Google will not support the connection of the UD wallet to the secure element of the smartphone and, therefore, the highest level of security cannot be achieved? We've heard it on the RSA conference. Thomas Maurer is asking. I can say something.
The goal is to have access on hardware security on the phone, because it's like more privacy-preserving, it's less expensive than, for example, solutions with cloud HSM. Still, we need access to hardware security on the phone independently from the manufacturers, independently from the OS, independently from MNOs. So that's the hard thing. We're working on this. We have the Digital Markets Act.
We want to have solutions in the implementing acts for this, because it needs a governance structure and I hope that with, for example, SAM, we have standardisation to access hardware security on the phones, because in the end, there's this goal. The best thing is if we find an agreement with Apple and Google to get on the phones, because I think when we have a common agreement, it's the best way for all partners. But if we can't find agreements, there will be legal ways to get on the phones, because the goal is hardware security decentrally on the phones.
Yeah, I see Thomas nodding and you also agree. I could jump in on that. I think the basic problem is that there is a EU idea about privacy and security and design and maybe there's another idea from big ecosystems like Apple and Wallet on their thing and that might arise to a conflict and we will see to what extent that technically diverges. I think there are good reasons that the EU is doing a regulation on that and is acting to build an opinion on our own.
Yeah, thank you. And then I have a final last question before we go to the lunch and that's a question to all three of you. How are the three huge or four large consortia consisting of, well, up to 100 partners, how do you co-operate within, okay, that's quite a challenge probably, but are you also co-operating across the various large-scale partner or consortia and how do you do that?
I could go, many of our members are members in both consortia, so there's already a lot of exchange on the details on the base level and we have another exchange between the large-scale pilots, there's a group and we have on the commission level, there's also LSP coordination and on the German side, national, we also have a LSP coordination, there are four levels of that. So, I think the governance of this could be quite complex.
Well, I'm quite impressed with all the information I've seen and even though that was sometimes a bit in a rush and although we've missed one other consortium, not here, the Nobit consortium, I'm really looking forward to all the actual implementations and using the wallet as a member state citizen in 2026 when our member states will launch the national wallet and see how all these use cases are going to be really practically helping me and us and the member citizens in our real life. So, thanks and if anyone has more questions, I suppose you'll be around during the lunch break.
So, that's it for the moment, see you back at 14.30 with the next session on this stage on ADAS. Thanks all.
