 Okay, we are now live Veben, do you want to get it started or I want us to just introduce the First if you can introduce yourself and then we can continue and in the last weekend. Yeah, and I'll just give a quick quick overview of the project and the idea concept behind it and then I'll let everyone introduce Let everyone here introduce themselves. So the idea behind the project is that Telecom roaming agreements are digital Sorry legal agreements usually they are bilateral agreements and Usually it's it's lots of Legal terms, but there's also a technical side of it as well a commercial and And the concept here is we are trying to tackle This at the early stage of building the telecom roaming agreements, which is at the stage of drafting and negotiation and We came across the concept from other From other domains actually in financial markets. There is this Over the counter derivatives agreements, which is look to us something similar And there's already something similar in the financial market that that hand is something In the domain of how to draft and negotiate a kind of master agreement so the concept is to use both natural language processing and DLT In this case, it's high religious fabric the natural language processing is to analyze the text of different legal agreement documents and try to classify the text into Different different parts and Santiago will will go through this and then the the DLT is to manage the automation Bees and ensure the trust and the auditing and the traceability Myself is my self is Ahmad Sawyer. I work in blockchain Industry for the last three to four years. I build blockchain solutions and I ask it both Nurdine and Muhammad to join me because they they can bring the other The other side of the project, which is the natural language processing, which is their their specialty and Santiago is the mentee in this in this mentorship project And he was the one Performing all this this work while we provided him with guidance throughout the project So I leave it to Nurdine and Muhammad and then leave Santiago as the last one since he's going to be doing the entire presentation so Nurdine Thank you, Ahmed. Hello everyone and welcome to this meeting. My name is Nurdine Sadawi. I'm from Libya based in London, UK I'm a senior lecturer at the University of London and instructor with O'Reilly and Pearson I Specialized in machine deep learning and in those areas. So that's why I was invited to co-supervised this project I'd like to thank Ahmed and Hyperledger and Direct Foundation for facilitating this. It's been a really good project Santiago has done a Fantastic job as he will present to us today I'm grateful also to Muhammad for his contribution. It's been a really nice and useful project. We've learned a lot along the way And yeah, thanks everyone again for joining us over to you Muhammad Hi everyone, this is Muhammad El-Sharif. I'm a software engineer at Qatar Center for Artificial Intelligence Like I'm like mainly work in applied machine learning and deep learning under like spectrum of applications And I'm involved in many projects with local and international entities Like we have like collaboration projects with Boeing in predictive maintenance in detecting small objects And also we have a collaboration project with MIT about urban computing and with Qatar Airways in local entities So like yeah, so that's why Ahmed he like Asked me to join this project like because I'm like kind of working in machine learning and deep learning, you know During my career for the past like five years So thank you Ahmed and it's over to you Santiago Okay. Thank you very much Let's start it. Okay. Good morning. Good afternoon. Good evening for everyone. My name is Santiago I recently finished my PhD I am currently working in data analysis and information management group Of faith that is a research center in basket country that is part of the University of Nevada First of all, I would like to send to the special telecom group for the invitation to the present the war the use of an LTV DLT to enable the digitalization of telecom running agreement as part of the hyper legend mentorship 2021 project Additionally, I would like to to to well to to introduce to to to know to my to my mentors projects, Ahmed, Norebin and Mohammed Who were present in the call and talk a bit Before me so you can see the minted project presentation on the link place it you know in the slide footer And now I will start with one overview of their running agreement concept Running agreement operation ensures business continuity on the victim service Access to the end customer across various technologies stack including for instance new technologies like 5G IOT technologies and IOT The running agreement address the technical and commercial components necessary to enable the service to a running customer so that it constitute an essential part of the business Managing issues such as you know the interoperational search Thinking that running agreement are mainly you know a bilateral agreement with an established template provided by Yissi main Therefore, conducting a dynamic and transparent running agreement drafting process ensure advantage for telco companies in terms for instance of monetization The necessity of the project comes from problems detected in the running agreement drafting process, which includes first of all, the running agreement negotiation is manual, slow and untrace worthy And second is that the Yissi main approach for the wholesale running initiative is like a generalist in terms of negotiation and drafting of the running agreement so it's lacks of standardization So there is a necessity to establish a framework that provide capabilities such as you know a fine-grained methodology that digitalize the running agreement drafting process And in addition the promotion of a transparent negotiation process between two mobiles networks operator And in addition to ensure trustability in the running agreement drafting process In this way blockchain integrated with other technologies such as natural language processing can cover these capabilities You know an overview of the project can be found in the first medium article that we published as part of our project and the URL is included in the in the footer of this slide For this reason the two main project objectives are first of all to build a library that will capture the different variations and variables that construct a telecom running agreement And in addition to build a proof of concept based on a set of smart contracts that will automate the process of drafting and negotiation In general terms we can think in this project that looks very early phases of the running agreement and specifically the drafting and negotiation process Our solution can facilitate the process of drafting and agreement and turning into digital format can help in establish a route of truth of the agreement For this reason we first collect a few agreements including you know the GCMA template and build a simple NLP model to extract the main feature of the text that we classify as standard class variables, variation and custom text This model then is used in the drafting of any agreement to build each article where the action of user are managed through the same code in terms of article proposal, article change until the entire agreement is finalized At background level we want to analyze on the one hand the NLP technology and the Amazon Comprehension tool, but a quick concept In this term natural language processing is you know it's a soup field, it's a soup field sorry, of linguists and computer science and artificial intelligence Concern with the interaction between computer and human language At the same time you know Amazon Comprehension is a natural language processing service, it's like a tool that uses machine learning to uncover variables inside and connection in text To understand what are variables, variation and standard class sorry and custom text, a snapshot of two documents are used On the left side you can see the 8-8-12 GCMA template and on the right side you can see one sample of the mobile network operator proxies running agreement In this way a standard class implies to leave an article or sub-article as found in the template Variables represent the value of certain attributes that are found in a certain text such as for instance dates, name of entities, amounts and others In addition, variation represents changing variables for instance you know mobile networks operator, dates, penalty, currency and so on Concerning the original text, I mean the GCMA template in the article or sub-article Finally, customized text introduce completely new you know article of sub-article that respond to particular interests The reference architectures includes not only participant entity but also the functionalities that they perform throughout the application lifecycle First the entities participant in the running agreement are composed by you know two mobile network operators and the GCMA as administrator There are functions that they perform in common such as you know the maintenance of the hyper-layer fabric network and participation in the network consensus But particularly mobile network operators negotiate and draft the running agreement among themselves Maintaining the privacy of the information and using the NLB engine to create a template which will be used as part of the drafting process In addition, the GCMA is in charge of the registration of the mobile network operator, the network monitor, the auditing, the accountability of the running agreement conducting between the two mobile network operators The application lifecycle is composed by four stages The first one is enabled the running agreement principle, the second one is the registration of both the mobile network operator and the running agreement In addition, the third stage is the running agreement drafting process and finally is the phase of to reach the agreement The third phase starts when two mobile network operators enable the running agreement principle Throw out you know a document that could be shared with the GCMA as a central authority At this point GCMA is able to create the running agreement output template using the NLB engine execution The second phase is that one is produced when the GCMA loads the running agreement output template to the platform to manage the running agreement It must enable the mobile network operator who will be able to register themselves on the hyper-layer file instruction platform before starting the negotiation and drafting of the running agreement The third stage contains the running agreement drafting process, although in this image, three processes are represented Any combination that includes, for instance, an article, accept article, propose change in the article and forget the article can be performed Finally, the fourth stage consists of the proposal to reach an agreement as well as the acceptance of the running agreement by two mobile network operators The two main components of the project are first of all the NLB engine and the second one the shame code, which are discussed below The overall architecture of the NLB engine is built over a doctor infrastructure, establishing as input the running agreement draft as well as the GCMA template The processing layer is a logic identified as the NLB engine, which includes as output the classification of the article in standard class, in variation, in customised text and variables A very important component in the NLB engine is the Amazon Comprehensive Service This service, as we mentioned, used machine learning to uncover variables inside and connection in text Throughout Amazon Comprehensive Tool, running agreement text is processive to extract, for instance, key phrases, entities, sentiments for further analysis Details of the NLB engine can be found in the second immediate article published as part of this project And again, the URL is included in the footer of the presentation of this slide, sorry This image of this slide illustrates the part of the set of methods that can make up the shame code lifecycle The invocation of this method established the transition between the different states of the shame code This transition takes place at three application levels, the first one is the running agreement level, the second one is the articles level, and the third one is that article level Details of the shame code design can be found in the third immediate article published as part of this project and the URL is included in the in the footer To illustrate the operation of the shame code, the following figure or slide show the sequence given of the proposed agreement initiation method Thus, you know, the proxy module enable the interaction with other modules The identity modules allow verifying the Mobile Networks Operator Identity The organization module verify whether the Mobile Network Operator exceeds and has been previously registered The agreement modules perform the following functionalities First, the generation of unique identifier for the list of articles, second one the generation of another unique identifier for the running agreement The third one is that the status of the running agreement negotiation is set as a started running agreement The status of the article negotiation is set at meet And the started running agreement event is submitted Again, detail of the shame code implementation can be found in the fourth immediate article published as part of the project Again, the URL is included in the footer of this slide The product implementation is based on a set of microservices using, you know, using vector infrastructure It should be noted how this email is the administrator and the maintainer of a set of services including, you know, the front-end, NLBNG, the Kibana, Grafana, Prometheus and Swagger In addition, the two Mobile Networks Operator include the functionalities to maintain and monitoring the ledger One of the most remarkable points of this project is, you know, if the integration with other open source projects that belong to the hyperlayer mentoring or mentorship program Specifically, the project analyzing hyperlayer-fabric ledger transaction and logs using elastic search and Kibana We include this project as part of, you know, of our project And in the demo it's possible to see how this integration, sorry Now it's time to have a demo time First one, you can see the transaction committed into the ledger once the shame code is installed and instantiated The attempt to access for the user failed because GSMAs need to register it before Now GSMAs register admins a user of the Mobile Networks Operator The user one now is able to register, for instance, one Mobile Network Operator Now you can see how the transaction is committed into the ledger Again, the user two is able to register the second Mobile Network Operator Again, when the information is provided, now can be verified how the transaction is committed into the ledger Now the roaming agreement, let me stop here the video As you can see here, you know, the Mobile Network Operator number two proposed a roaming agreement registration As you can see here, this thing represents the roaming agreement output template that was provided by the NLD engine As you can see here, the roaming agreement is proposed And here you can see how the pipeline created can show the roaming agreement is available between the two Mobile Networks Operator Now, the other user in this case, the user one with the Mobile Network Operator one need to confirm the roaming agreement Again, the transaction is committed into the ledger And now this Mobile Network Operator is able to propose an article based again on the roaming agreement output template from the NLD engine Here, as you can see a standard clause is defined, variables are introduced and in addition, variations are defined Again, transaction is committed into the ledger And now as you can see, as you can see here, you know, the article is added into the pipeline One important thing here is that the Mobile Network Operator that propose the change cannot be able to accept it So now the second Mobile Network Operator is able to, for instance, to propose a new changes Now the variables are changing But accept the same variations Okay, here it should be possible to see that how the standard is updated And now the Mobile Network Operator number one is able to accept the proposition Again, the transaction is committed into the ledger And then new articles are added into the pipeline This is a new article And another article should be added into the pipeline But again, one important thing The Mobile Network Operator number one cannot accept its own changes So Mobile Network Operator two, accept the proposed change Here, transaction committed into the ledger The next article is accepted The status change And now this Mobile Network Operator is able to propose To propose that the roaming arrival be accepted Just three articles into the pipeline, in this case, is enough And now the Mobile Network Operator number one can accept the proposal As part of the project, the developers include a series of medium articles Explaining the main project vision, the main concept, and the proposal design approach The NLP model that extracts the main feature of the telecom agreement Agreement template as a set of variables and variation In addition, a chain code that automates and map the business process of the agreement, drafting, and negotiation In addition, the architectural design document of the system Also, we create a simple user interface as a group of concepts That will show the steps of the agreement drafting And finally, we publish an academic conference paper with the main finding of the project For the future works, we have included to build a model based on one open source library Such as Spacy, because right now we are using the Amazon conference tool In addition, to create a drafting library in JavaScript and publish it as MPM package We also plan to ensure information privacy between two mobile networks Operator through the Prevail Data Collection In addition, we want to contextualize the traceability of the robbing agreement negotiation Between two mobile networks operator through the visualization tool In addition, the definition and establishment of an audit and accountability layer for the system Another future work is the full API for monitoring based on Prometheus and Rafa And the last one needs to submit a manuscript to the IEEE International Conference on Blockchain in 2022 At this point, I want to thank my mentors, the knowledge and still gain around this project Thank you very much Thank you Santiago, thanks a lot It was really an honor to work with you during this project Me and I think even my colleagues, Mohamed and Nurdin, we learned a lot from you through this project And the most important thing, we also got this from a concept written in one Bezier into an actual proof of concept During the mentorship project, which was really good And also it's worth noting that when we developed this, we looked at what GSMA is trying to achieve At GSMA, they have their BWR initiative, which they are trying to build a framework for telecom roaming agreements using blockchain But they are focusing more into the actionable pieces of the telecom roaming agreement in terms of settlement dispute resolution And the good thing is that what we found is that our work can be complementary to theirs So we come at the very early stage where we try to digitize the agreement text and extract it into those features through the NLB model And then use the chain code to build the actual digital version of the roaming agreement and make it actionable The text phases in terms of settlement, dispute resolution can benefit from having this digitized version of the roaming agreement text Which I think that's the point where Santiago mentioned that right now it's more of a generalist approach so it's like relying on BDF files exchanged or something like that where you add digital signature But it's not like at a very granular level where you can identify exactly, this is the amount of the credits used or this is the operator name or this is the date of start of agreement or whatever So any of those variables or the different variations used so just wanted to put that into the context and I think also it's good to mention that next week we are meeting with GSMA to try to find out some synergy between what we've worked on and the BWR group at the GSMA And see if how we can maybe contribute with our work that Santiago built into the GSMA BWR initiative so yeah Thanks for sharing everything and I want to know like is it like open source like because it's a part of I think Hyperledger mentorship program or what frame if you can tell us more about this framework like is it you what do you use like is it fabric or some other platform Yeah it's open source all the links to the repos etc are available I think in the different medium articles and yeah it's all based on Hyperledger fabric with the different tools that Santiago highlighted in terms of monitoring tools or other tools We are also that's something maybe I would like to mention to you Vivian and David, we are building a more detailed solution design document, we can share that document with you and maybe we can maybe have it sort of as a solution brief or I don't know what exactly the best name to call it, we're calling it solution design document but maybe we can get some editing from you David and the Hyperledger fabric team and if okay we can we would like to publish it under the Hyperledger umbrella Sure, I mean that would be a good discussion to have it a future telecom call we've done two other solution briefs from the group and talk are talking about other ones yeah we can certainly sort through that and get it published And we have one question in the chat box like thank you sir, could you share with us your API monitoring tools Yes, yes for sure, maybe I share my email and then I can share all Docker created for monitoring proposal, yeah sure There is a question also from you David Yeah, and the question is, do the wireless carriers have to agree to participate on the Hyperledger platform applications Yes, definitely yes and there's also the role of the GSMA to enable registration of those MNOs into the platform so of course And also because anyhow we are not means as interoperability is not part of this and I for example, let's say if someone some carrier is using Hyperledger or someone is using Ethereum so interoperability is in your vision It's Hyperledger fabric right now on the chain code is deployed differently on Hyperledger fabric so it has to be Hyperledger fabric And the next question is from Anis, is it possible to build a generalized agreement negotiation system on Hyperledger And the second is what is the need to develop a specific system for mobile operators Yeah, I think yeah that could be but in terms I think one of the issues that we faced we we we didn't have anyone who's a legal person in our team And just as I said, we borrowed this concept from financial markets and I know how they built it in financial markets it was legal team that they were analyzing text, not using NLB but People analyzing text and identifying variables variations etc. So to build a generalized agreement that means, for example, SLA agreement or any other types of agreements, it could be done but it would require a more sophisticated model and branching in that model, if it's the best word to use for this. So, yeah, that's my answer to this I don't know if the other guys has any comment on this And also one more like what is the need to develop a specific system for mobile operators like this is one basic question like means why you started to develop a specific system for mobile operator. I don't know what, if, if Anna scan elaborate more, we could maybe understand exactly what's a complementary question to the first part. Basically, if we can build a generalized negotiation agreement agreement negotiation system on hyper ledger fabric that can be working dropped in like the template of the contract and then the negotiation process in terms of as presented in this scenario, each party kind of suggests changes and then the process moves on and everybody agrees and then have at the final stage you have a contract that everybody agrees on. To me that sounds like the process that can be applied to any type of or any type of contract like that. Yeah, I totally agree that it could be a generalized approach, but what's the need to develop is that, as I said, there could be different types of legal agreements for mobile operators. And it is one thing SLAs is another thing and definitely there are others. One of the objectives was of this project that we actually didn't, didn't complete was to build a library a package. We targeted JavaScript, like an NBM package that will enable transforming that NLB model into a library that will allow easily to pick article two, and then once you pick article two, that will populate what are the variables what are the different variations. And this is actually was done by Santiago but not as a library but he coded that into the front end. So our work maybe is to extract that into a library. So if we would like to build that generalized model, what will happen, you will take different different SLA agreements, you will take different roaming agreements with and then you will build an NLB model for each one of these and then build some packages that once you select what type of agreement it will select it will. It will grab the specific model for that type of agreement and then you start executing the next steps of selecting an article, specifying what are the values for each variable, which variations you would like to include do you want to include some custom text, things like that so Yeah, I mean, I see huge potential like if such a model can be generalized and you can expand your customer base and like in healthcare, like real estate, people like Exactly. A lot of people can benefit from like the basically hyper leather, the immutability of the contract and the whole process is transparent. This just opens up a lot of potential. Yeah, in that case, I totally agree. So that would be like the chain code will be the most generalized system here that will handle just the process of adding articles specifying the ins and outs of each article and then handle the negotiation of the release which is if you accept it if you propose change if you want to delete it, reject it, whatever. But again, it would have to start with building the different models for the different use cases that you would like this system to handle so without that model, you don't know how the text is interpreted because definitely there are specific things that you can capture maybe in roaming agreements but one if you go to a real state brokering agreement that would be maybe different kind of variables and text that you need to analyze to come up with the exact model. And the other thing is which we mentioned already that we borrowed the concept from another industry so definitely a generalized model can be built and that is just you need to do that batch processing at the beginning by building your NLP model. So if you built that generalized chain code, then you would start every now and then to go into a specific domain, analyze lots of legal text and come up with the model that can be used Fair to say is that telecom roaming agreements are not that complicated. So that's what made our life easy. We don't know about other applications. Great. Great. Okay, Jason was to ask some questions. Jason, could you unmute yourself? Yeah, thank you. I've been and thanks a lot in Santiago for the presentations very helpful. So thank you for that. So I know this is a proof of concept project so it's not a production environment but it's a good starting point to carry over to production. So my question is when we move up to production and governance question. So there is a roaming agreement that that comes into existence right in the example in the presentations between orange and telephonica so who would have ownership of this document because it's a roaming agreement between two operators. So that document obviously it's off chain. But do you see that being a repository held by a third party or is it one of the operators or where does that go? One of the things that we are looking at is to look into private data collections. And in that case, that will be something where the roaming agreement is just built inside the chain code actually. And you kind of, let me try to find the best word to describe this. You generate the actual text based on what's inside the chain code and since it's a private data collection so that means it's only the two operators that they have access to this agreement. Okay, so it's a private data repository? Yeah, yeah. Currently it's not there. Currently like GSMA is the authority that handles or manages the entire network and everything is plain accessible to everyone but our concept is to advance this and build it on top of private data collections where data will become only accessible to the two operators that they are. So the roaming agreement would reside in operator one and if operator two needs to access that roaming agreement they have to go into operator one's repository to retrieve it. Yeah, as I said, it's actually coded inside the chain code. So when you define the variables, when you define what are the variations, we do not include the actual text inside the chain code but we include references. So let's say article two, there are three variations, two A, two B, two C and when operator one proposed the article, he included two A and two B and then operator two approved it. So right now, inside the chain code, article two is defined as whatever the standard clause, so standard clause is always there, plus it's identified by two variations, two A, two B. When the other operator would like to construct the agreement, the engine maps, do some indexes into the actual text and generate the BDF for that one. But the main thing here is that variables are identified by their actual values inside the chain code, variations are identified by their indexes, which as I explained right now. The only thing is custom text, custom text is the only thing that's stored as is inside the chain code. Right, so if whenever they want to retrieve the document, they can, they can reference the ledger generate on the clock to generate the document. Okay, got it. Okay. Thank you very much. Thanks guys really great presentation. Thank you for sharing. So, Amit, are you planning to host this PUC code on Hyperledger Labs as well or it's just an individual project that means how you will, what are your next steps on this? Yeah, we would love to do that. Yeah. Honestly, that was something on my side, but I didn't do my job. So, yeah, we would love to do that and probably we can ask for help on how to set up that on the literature. That will be good because in that case this mean this will increase the outreach as well and then because if if Hyperledger Labs can be used by let's say GSMA or other operators as a as a standard or something so that like it will help for other operators to start with something. Yeah, yeah, we can discuss that. I see David putting a link here, but we can discuss offline and see how to. Yeah, feel free to reach out and you may have already taken a look at the process, but it's fairly straightforward. So if you have questions or something, you know, yeah, sure. Hi guys, sorry to just to jump in quickly. I'm sure David and the VPN have spotted already from Santiago Slides that he's actually reused some of the existing components from previous project, which is really good. Yeah, yeah, just the Hyperledger Lab nerdy and just to, but maybe webbing can provide further there but it's like costing this solution or proof of concept there. So allow my point is a little different. What I'm saying is, because we've been mentioned that it's good for outreach we have done actually some of that to prove that the previous work can be quite useful. So Santiago has used already existing stuff and hopefully for this project, it can take different branches. So a couple of suggestions, for example, where we're really good already sorry I forgot names and I think I forgot sorry for the other person's name. So these are quite useful suggestions. Some of the stuff here I must say is basically future work. Okay, so please do bear in mind that this is just a proof of concept project. So it's not really a large scale project. So it can go into different directions. One of them, for example, sorry, it was Jason. Yeah, Jason, John. One of them, one of them could be for example, this project can be the basis or the foundation for another project so somebody can maybe extend it to something else, like for example, interoperability for example between different providers of blockchain technology such as Ethereum and so on. Also, of course, packaging is stuff I'm putting into libraries and reusable modules. That's also really good. Yeah, so this is just one point I wanted to highlight. Also regarding the material and the existing stuff that already is there, we do have already a couple of medium articles written and also a GitHub repository where the code is. So I think Santiago if you're still around then you perhaps can copy and paste the link here and then people can find it really useful. And I also want to add a very important point is like once like GSMA will be involved in this thing. So that's what GSMA is doing with the like with other foundations or other projects is like they are building some reference architectures and reference implementations. So if we can work on that part like as a separate project or something that's what they do in different foundations, for example, CNTT. This is with Linux Foundation Networking and GSMA for what telco cloud should be like in the implementation part. So if we can do something like this that what we can propose to GSMA regarding we are interested in building some reference architecture implementations and models so that it will be like a reference point for other operators as well. That's what GSMA can push into. So Ahmed, that's just a suggestion that you can ask them like if they are interested in. Yeah, let's see. I think they already work with two or three operators and two vendors I think. I think you already hosted Shamit and someone from Cineverse they delivered a presentation to the group in the past few months. Yeah, yeah, we'll discuss that with them and see if they would like maybe to set up a small group that can bring synergies what they are doing and what the group might be able to add. And Santiago already shared one link like those participants who are interested in this blog they can see. Yes, we will. Yeah. Yeah, I share the link of the project. Here is the whole information of the demonstration, the medium articles. I think that is a good entry point to the rest. In this we also included the repository link, the repository URL. So always concentrated in this space. And so Santiago feel free to share that on the group's list. You know not everybody in the group was able to join to the call today so there's over 200 people in the list so if you want to have a conversation there you're certainly welcome to and anybody who is not on the group's list but would like to take part in discussions it's an open list and you're certainly welcome to subscribe. Okay. And the link is shared in the chat as well. Okay, do we have more questions. Anyone. Okay, so thanks Emma then everyone for joining today. And we have bi-weekly calls every Thursday like in second week of Thursday so if you're interested in like delivering more talks or attending sessions please feel free to join these calls. Thank you. Thank you very much. Thanks everyone. Thanks everyone. Thank you. Take care. Thank you everyone. Thank you very much. Thank you. See you next time.