Merge pull request #86 from pf-lin/blog/pmfp

Update 20240103.md

docs/blog/20240103/20240103.md

@@ -1,85 +1,89 @@
 # UE-initiated PLR Measurement Procedure in PMFP Procedure
 
 >[!NOTE]
-> Author: Samuel Lin 
+> Author: Samuel Lin
 > Date: 2024/01/03
 
 ## Introduction
+
 Performance measurement function protocol (PMFP) procedures are performed between a performance measurement function (PMF) in a UE and a PMF in the UPF.
 
 The PMF can measure Round-Trip Time (RTT) and Packet Loss Rate (PLR) by exchanging information through PMFP messages to perform these calculations.
 
 In this document, we solely introduce the UE-initiated Packet Loss Rate (PLR) Measurement Procedure.
 
-
 ![PMFP_PLR(UE)](./PMFP_PLR(UE).png)
 
-
 ### <u>Description</u>
+
 **Counting start:**
-* [1-4] UE initiates measurement by sending a ```PMFP PLR Count Request message``` to the UPF. UE and UPF commence respective packet counting processes.
+
+- [1-4] UE initiates measurement by sending a ```PMFP PLR Count Request message``` to the UPF. UE and UPF commence respective packet counting processes.
 
 **Reporting and Potential Restart:**
-* [5, 6-2]. UE sends a ```PMFP PLR Report Request message``` to request UPF's counted packets and may optionally request counting restart.
-* [7-2, 8]. UPF responds with a ```PMFP PLR Report Response message``` containing counted packets and potentially restarts counting if requested and accepted.
+
+- [5, 6-2] UE sends a ```PMFP PLR Report Request message``` to request UPF's counted packets and may optionally request counting restart.
+- [7-2, 8] UPF responds with a ```PMFP PLR Report Response message``` containing counted packets and potentially restarts counting if requested and accepted.
 
 **PLR Calculation and Procedure Termination:**
-* [6-1, 7-1]. Procedure terminates if restart is not requested or not accepted.
-* [9]. UE calculates the UL PLR (Uplink PLR) based on local and reported packet counts.
-* [10-14]. Counting can be restarted multiple times upon mutual agreement between UE and UPF, enabling continuous measurement.
+
+- [6-1, 7-1] Procedure terminates if restart is not requested or not accepted.
+- [9] UE calculates the UL PLR (Uplink PLR) based on local and reported packet counts.
+- [10-14] Counting can be restarted multiple times upon mutual agreement between UE and UPF, enabling continuous measurement.
 
 ### <u>Key Considerations</u>
+
 **Message Transport**: All PMFP messages are transported over the same QoS flow on the same access.
 
 **PLR Calculation**: UE derives the UL PLR using its own transmitted packet count and the UPF's reported received packet count.
 
 **Compliance**: The procedure adheres to 3GPP specifications for packet loss management.
 
 ### <u>Additional Notes</u>
+
 **QoS Flow Selection**: The specific QoS flow for message transmission is contingent upon the measurement type (default or non-default QoS rule).
 
 **Continuous Measurement**: The restart capability facilitates ongoing packet loss monitoring.
 
-
 ### <u>Conclusion</u>
+
 This UE-initiated PLR measurement procedure provides a standardized and coordinated approach to assess UL packet loss within 5G networks. Its adherence to 3GPP specifications ensures interoperability and consistency across network implementations.
 
->[!NOTE] 
+>[!NOTE]
 > The **network-initiated** PLR measurement procedure is to enable UPF to measure the PLR of DL traffic access to the UE through the MA PDU session. The process is the same as the UE-initiated PLR measurement, except that the **objects are reversed**.
 
-
 ## Reference
+
 - *3GPP TS 24.193*: 5G System; Access Traffic Steering, Switching and Splitting (ATSSS); Stage 3
 - *3GPP TS 23.501*: System architecture for the 5G System (5GS)
 
-
 ## About
+
 Hello, I am Samuel Lin. I have just started making contributions to the free5GC core network. This post is my first blog, so if there are any inquiries or identification of errors within, we welcome discussion and correction. Your feedback is invaluable, so please don't hesitate to reach out via email to share your insights.
 
 ### Connect with Me
+
 <p align="left">
 <a href="https://www.linkedin.com/in/pin-fan-lin-464201290/" target="blank">
-	<img align="center"
-  		src="https://raw.githubusercontent.com/rahuldkjain/github-profile-readme-generator/master/src/images/icons/Social/linked-in-alt.svg"
-  		alt="Linkedin" height="30" width="40" />
-</a> 
+ <img align="center"
+    src="https://raw.githubusercontent.com/rahuldkjain/github-profile-readme-generator/master/src/images/icons/Social/linked-in-alt.svg"
+    alt="Linkedin" height="30" width="40" />
+</a>
 <a href="https://github.com/pf-lin" target="blank">
-  	<img align="center"
+   <img align="center"
       src="https://raw.githubusercontent.com/rahuldkjain/github-profile-readme-generator/master/src/images/icons/Social/github.svg"
       alt="Github" height="30" width="40" />
-</a> 
+</a>
 </p>
 
 - Linkedin: [https://www.linkedin.com/in/pin-fan-lin-464201290/](https://www.linkedin.com/in/pin-fan-lin-464201290/)
 - Github: [https://github.com/pf-lin](https://github.com/pf-lin)
 
-
 ## Appendix
 
 Additionally, I have provided the graph with the network-initiated PLR measurement procedure.
 
 ![PMFP_PLR(UPF)](./PMFP_PLR(UPF).png)
 
-
 >[!NOTE]
 > If you are interested in supporting free5GC, we welcome your donation. Please visit this [link](https://free5gc.org/membership/) for more details.