<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: Raavi, "Nirmala UI", "Gurmukhi MN", sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Dear Pavel, all</div>
<div class="elementToProof" style="font-family: Raavi, "Nirmala UI", "Gurmukhi MN", sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Raavi, "Nirmala UI", "Gurmukhi MN", sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
We can do that for our two use cases (Charbel + Tamara). </div>
<div class="elementToProof" style="font-family: Raavi, "Nirmala UI", "Gurmukhi MN", sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" id="Signature">
<div style="background-color: rgb(255, 255, 255); font-family: "Franklin Gothic Book", "Avenir Next Condensed", sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-size:12pt;color:#000000;font-family:Arial,Helvetica,sans-serif" dir="ltr" id="divtagdefaultwrapper">
<div style="margin: 0px; font-family: "Calibri Light", "Helvetica Light", sans-serif; font-size: 10px; color: rgb(0, 0, 0);">
Wirelessly Yours</div>
<div style="margin-right: 0px; margin-left: 0px; font-family: "Calibri Light", "Helvetica Light", sans-serif; font-size: 10px; color: rgb(0, 0, 0);">
~~~~~~~~~~~~~</div>
<div style="margin: 0px; font-family: Calibri, Arial, Helvetica, sans-serif;"><span style="font-family: "Calibri Light", "Helvetica Light", sans-serif; font-size: 10pt; color: rgb(0, 0, 0); line-height: normal;">Mehdi Bennis, Full Professor</span><span style="font-family: Arial; font-size: 10px;"><br>
</span></div>
<div style="margin: 0px; font-family: "Calibri Light", "Helvetica Light", sans-serif; font-size: 10pt;">
<span style="background-color: rgb(255, 255, 255); line-height: normal;">6G Flagship, Centre for Wireless Communications</span></div>
<div style="margin: 0px; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 10pt;">
<span style="font-family: "Calibri Light", "Helvetica Light", sans-serif; line-height: normal;">HEAD of ICON</span><span style="font-family: Arial; line-height: normal;">,
</span><span style="font-family: "Calibri Light", "Helvetica Light", sans-serif; line-height: normal;">IEEE Fellow</span></div>
<div style="margin: 0px; font-family: "Calibri Light", "Helvetica Light", sans-serif; font-size: 10pt;">
University of Oulu</div>
<div style="margin: 0px; font-family: Arial, Helvetica, sans-serif;"><br>
</div>
</div>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Musecom2 <musecom2-bounces@fel.cvut.cz> on behalf of machp2@fel.cvut.cz <machp2@fel.cvut.cz><br>
<b>Sent:</b> 05 March 2025 15:37<br>
<b>To:</b> musecom2@fel.cvut.cz <musecom2@fel.cvut.cz><br>
<b>Subject:</b> [MUSE-COM2] WP2 deliverable</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Dear all,<br>
<br>
I would like to ask you for some inputs to deliverable we committed to <br>
be delivered within WP2. More specifically, I would really appreciate <br>
your inputs to D2.1 deliverable related to use-cases, scenarios and <br>
requirements. For your convenience here is the expected content taking <br>
from the application:<br>
<br>
"… we will identify a set of complementary use-cases spanning various <br>
environments and scenarios of application of the developed system <br>
aiming at identifying commonalities and specifics of individual <br>
use-cases and scenarios. We will also define the set of requirements <br>
on the system, its individual components, and a broad set of KPIs for <br>
performance evaluation…"<br>
<br>
In this regard, could you please send me use-cases, scenarios, and <br>
requirements on the system that you are targeting (in the form of <br>
short description)? Inputs would be very welcome especially from OULU <br>
and EURECOM. I guess that you could only compile the set of use-cases, <br>
scenarios, requirements on the system (if any), and KPIs that you <br>
already consider in your papers (or plan to assume in ongoing and <br>
future papers related to MUSE-COM2). After that, I can compile your <br>
inputs into single and comprehensive document.<br>
<br>
I have found a very nice paper on KPIs related to SemCom <br>
(<a href="https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=10107602">https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=10107602</a>).
<br>
Mehdi, as the co-author of this paper, do you mind if we reuse some <br>
parts of the paper describing KPIs that are closely related to <br>
MUSE-COM2?<br>
<br>
Since the deliverable should be ready by the end of March, could you <br>
please provide me the inputs by 14.3. (next Friday)?<br>
<br>
<br>
If you have any questions, don’t hesitate to contact me,<br>
Pavel<br>
<br>
<br>
_______________________________________________<br>
Musecom2 mailing list<br>
Musecom2@fel.cvut.cz<br>
<a href="https://list.feld.cvut.cz/cgi-bin/mailman/listinfo/musecom2">https://list.feld.cvut.cz/cgi-bin/mailman/listinfo/musecom2</a><br>
</div>
</span></font></div>
</body>
</html>