 Zato vseite in telekomunikacije način, je tako danes imačno posrednje. Bila to način vezivna, svoj je dynečno, da je to pravda, ki tudi pripravila in površtite in tako razrednje, in da površtite lahko informacije način, ta positions prowost u delartosti v pasterу. In v razmašljenih mobilne networku, v 좋šim gravπουčem, če je da je način da bi gačnja sa radijima način do radiobjastkov, in da bi se način uručila radiobjastko v tem koj slicesi. Proste začin in paželjeni, zelo je bolj vseč v sestibiji nekaj v e-netrpške. N Scan vseh baš vzvečen, V extensively in mobiles NATOÇ that are operating with Activision Duplex was importance to make sure that the radio frames from different stations was delivered at the short instante of time. In this way it is possible in this way to prevent interferences between the various stations. There are other reasons like applications. There were time synchronization to in博 immediately operate like in industrial automation. This is really a fundamental requirement in I would say today's networks and it is expected to become even more allattheme much in the future. Okay, so there is a need of transporting synchronization to be able to get services. We are also like 3GPP or wireless, as Stefano mentioned before. And there are different ways of transmitting in zelo se vzelo za vse aplikacije. V veselji je, da je kako v GNSS, da se vzelo za GNSS, kako v USA vzelo v GNSS v base stationi, da se vzelo za vzelo, in tudi je tudi vse vse, ki je tudi ptp, prisišnj, v protokolju, ki je tudi i3.1588, in je tudi vse vse interneti. Všetnih, na vse 13, zelo se vzelo v trej profijs. One is G.8265.1, that is for frequency synchronization. The second one was G.875.1, that's for phase and time synchronization. When you have a network that deploys 1588 in synchronous internet in every node of the network. And the third profile is G.8275.2, so many numbers. That is for phase and time synchronization, but in this case you don't have assisted network. What that means is that you don't have 1588 in synchronous internet in every node of the network. The third profile is more used in North America where they do have GNSS in the base stations and now you need PTP or Precision Time Protocol as a backup for the base station when GNSS is lost. We have been working on these profiles. There is also some management that we have been working for all these different applications. We started this work really since 2003, so we have been working on synchronization for many, many years. And you see the deployment getting... You see more of the deployments of these technologies now in the network. And with that, what happened is that operators now deploying these solutions, they find that they need new features. And with that, we keep enhancing the profiles. So at this meeting, I said in the 15 meeting as we speak, we're doing a new revision of all the three profiles with some new improvements, new features that are needed by the operators to be used in the network. So Question 13 is actually a very special group. It started to work with synchronization since the early 90s because of SDH that required synchronization for the network to operate. A few people are actually in the group since then. So I would say very expert people working with synchronization for many years. And I would say that one of the characteristics of this group is it coming from various industries. They bring various perspectives, various experiences. There are several representatives from network operators, from system vendors, clock vendors. And I would say there is a very good feeling in the group. They always try to cooperate to find the solutions to the problems. And the result is evident because we have been releasing so many recommendations over the life of this group. I would say in the last 15 years about 20 recommendations have been delivered addressing various aspects, for instance, of the distribution of timing over packet networks. And as a way of working, we normally meet four times per year, either in the I2T headquarters in Geneva or in locations hosted by participants. And over these meetings it is very important that when we meet to essentially discuss and find solutions. And then when we meet in Geneva, we complete the work by releasing the official documents as recommendations. So, like I said before, you have SYNC-E and 1588, and they both work together to deliver synchronization through the network. So if you lose, let's say you have a rearrangement on the SYNC-E, so you might have a phase transient in the 1588. So there is some studies going on right now. We have an enhanced clock in defining G.8273.2 that uses enhanced SYNC-E, and it has a very tight requirement for phase and time accuracy. And so any transient on the SYNC-E, how that affects this clock. So that's one item that we're working on now, and I studied it. The other one is when you lose SYNC-E for a longer period, and now you have your network only rely on 1588. So that's another item that we are supposed to get that into G.8273.2 at the next revision. So those are things that we are studying right now. There is also enhancements to best master clock algorithm in 8275.1. We also are developing a new supplement, because what happens is that when you look at all these profiles, you have several different functions and several different features that you can use depending on the application. And sometimes for someone not attending question 13 or not being involved in our work, it might find confusing how you use all these different functions in the network and how the operators can deploy and make a good use of those features. So we are developing a supplement that would help implementers to use all these features. And also we keep on improving the profiles as we get more feedback from the operators as they are deploying these profiles. Some features might be missing and then they bring contributions to question 13 and then based on those contributions, we keep on revising and improving the profiles. So for the future, we are expecting to continue to, let's say, improve and evolve the solutions that have been defined in question 13 like the work on the PTV profiles as mentioned by Silvana earlier. So there is a continued evolution of these solutions and as mobile networks evolve, moving towards 6G, we expect there are new and new use cases that will require accurate timing. So not only industrial automation but maybe automated vehicles, robots in a factory and so on. So we will certainly try to address all these use cases and the new requirements and of course, at the same time, look at the evolution of the technology. As an example, the clock technology is evolving via use of optical clocks and even quantum based synchronization solutions.