Daily Report - HackMD

> Joshevan (TEEP) # Daily Report 2023/07/03 ## Goals :::success - [x] Researching about NGAP Protocol ::: ## Report The NGAP Protocol is the protocol that is used to send data from 5G Core (Free5GC) to the RAN (gNodeB). In the PWS system, the data should be forwarded by the AMF, but for now, it not have been implemented yet, so I will try to research about it to be able to forward the data using NGAP Protocol ## Comment ## Further Plan 1. Trace the code from Free5GC NGAP Github Repository # Daily Report 2023/07/04 ## Goals :::success - [x] Tracing the code from Free5GC NGAP Github Repository ::: ## Report The NGAP Protocol Github Repository is located on this [link](https://github.com/free5gc/ngap). The repository can be imported to the code to the NGAP Message and send it using the protocol. I must trace the code further to be able to use the library ## Comment ## Further Plan 1. Trace the code further from Free5GC NGAP GitHub Repository # Daily Report 2023/07/05 ## Goals :::success - [x] Tracing the code further from Free5GC NGAP Github Repository ::: ## Report The NGAP Protocol Github Repository is located on this [link](https://github.com/free5gc/ngap). The repository can be imported to the code to the NGAP Message and send it using the protocol. In that code contains function to build a NGAP package and also function to send it into the RAN ## Comment ## Further Plan 1. Try to implement by building/sending the NGAP package # Daily Report 2023/07/06 ## Goals :::success - [x] Try to sending the NGAP package to NGRAN ::: ## Report The NGAP Package is successfuly send to RAN (UERANSIM) using the function provided. The function is used to find the RAN and then send it, the package is successfully send, but in the UERANSIM log showed that "APER decoding failed", maybe it is because the message has not properly built, the complete report can be seen on this [report](https://hackmd.io/@joshevan/AMF#Implement-NGAP-Protocol-in-AMF) ## Comment ## Further Plan 1. Try to build the NGAP package # Daily Report 2023/07/07 ## Goals :::success - [x] Try to build the NGAP package PDU properly ::: ## Report The NGAP Package is successfuly bulit and send to RAN (UERANSIM) using the new function created. The function is used to build the NGAP package PDU properly using other function as reference. After that, the package will be sent into the RAN. The package is successfully send, but in the UERANSIM log showed that "Unhandled NGAP initiating message-received", maybe it is because the UERANSIM has not handled the Write Replace Warning Request, the complete report can be seen on this [report](https://hackmd.io/@joshevan/AMF#Implement-NGAP-Protocol-in-AMF) ## Comment ## Further Plan 1. Trace the pcap file to see if the message is successfully received in the UERANSIM # Daily Report 2023/07/10 ## Goals :::success - [x] Trace the pcap file ::: ## Report After tracing the PCAP, it is known that the package is successfully received in the UERANSIM, and it has been identified as a Write Replace Warning Request message, and the information in the package is also received. It means that the UERANSIM does not have the handler for Write Replace Warning Request Message. The complete report can be seen [here](https://hackmd.io/@joshevan/AMF#Trying-to-build-Write-Replace-Warning-Request-Message-and-send-to-RAN) ## Comment ## Further Plan 1. Try other RAN Simulator to test for the Write Replace Warning Request # Daily Report 2023/07/11 ## Goals :::success - [x] Completing the parameters ::: ## Report Write Replace Warning Request has several parameters, the mandatory and thend thend the, before the parameter is just one, so I will try to add all the mandatory parameters, the parameters is still hardcoded for testing, for next part the parameters will be from the binary message N2 information ## Comment ## Further Plan 1. Try other RAN Simulator to test for the Write Replace Warning Request 2. Create condition for the optional parameters, if the parameters is available # Daily Report 2023/07/12 ## Goals :::success - [x] Tidy up the AMF code ::: ## Report The AMF code has a few functions, the communication, procedure, build, and the send. In the previous code, all of the function are in the same code, in the communication. In this version, the code are divided into each function, so that the code are easier to understand and more effective ## Comment ## Further Plan 1. Try other RAN Simulator to test for the Write Replace Warning Request 2. Create condition for the optional parameters, if the parameters is available # Daily Report 2023/07/13 ## Goals :::success - [x] Use other RAN ::: ## Report The write replace warning request has not succedded in the UERANSIM, so we will try to use other RAN that has the write replace warning request to see whether our request is handled correctly in the RAN. The RAN has the handler for the Write Replace Warning Request, but it still says error, message-not-compatible-with-receiver-state, maybe it don't handle all kind of message. We must trace to see which type of message it support. The type of RAN used is Nokia 474021A ASIK AirScale. The complete report can be seen on [this]() ## Comment ## Further Plan 1. Trace the type of RAN to see the type of message it support and modify the AMF to match it 2. Create condition for the optional parameters, if the parameters is available # Daily Report 2023/07/14 ## Goals :::success - [x] Use other RAN ::: ## Report I continue the testing for the write replace warning request. The testing still failed, it still shows the error message, the specificiation for the RAN is also hard to search because it is a commercial product, so we will continue the test by trial and error ## Comment ## Further Plan 1. Test different type of message and parameters to see if the write replace warning request is succedded 2. Create condition for the optional parameters, if the parameters is available # Daily Report 2023/07/17 ## Goals :::success - [x] Add parameter from the CBCF ::: ## Report I created the message so that it takes parameter from CBCF, previously it is still hardcoded because of testing purpose. If the testing succedded, I will add more parameters to the CBE simulator, so that it can simulate the real CBE to send the data to the CBCF, and also the data will be used as parameters in the Write Replace Warning Request Message ## Comment ## Further Plan 1. Test different type of message and parameters to see if the write replace warning request is succedded 2. Create condition for the optional parameters, if the parameters is available # Daily Report 2023/07/18 ## Goals :::success - [x] Build ETWS and CMAS message ::: ## Report I built the ETWS and CMAS package to test it, I followed reference to make sure that the created package is match with the real package. To test it, I have to wait for the BBU. After the testing is succeeded, I will add more parameters including the optional parameters. The reference for ETWS message can be seen [here](https://osmocom.org/issues/4945), and CMAS message can be seen [here](https://www.sharetechnote.com/html/Handbook_LTE_CMAS.html) ## Comment ## Further Plan 1. Create condition for the optional parameters, if the parameters is available # Daily Report 2023/07/19 ## Goals :::success - [x] Build warning message content for CMAS ::: ## Report I built the warning message content for CMAS package because CMAS package needs warning message content. The warning message content needs to be encoded to GSM 7 bit string, so I designed a code to encode the normal string to it, so that string can be taken as an input to the warning message content. The output is the message have been able to be encoded so that the wireshark shows the message. If built correctly, when sending to the RAN with the capability of handling Write Replace Warning Request Message, the UE that is connected to the RAN will be able to show the warning message content ## Comment ## Further Plan 1. Create condition for the optional parameters, if the parameters is available # Daily Report 2023/07/20 ## Goals :::success - [x] Warning message shown on UE ::: ## Report The built warning message is sent to the gNB and it returns Write Replace Warning Response, it means that the warning message is successfully sent without error, the message is also shown on the UE, the complete report can be seen [here](https://hackmd.io/@joshevan/AMF#Build-again-the-message) ## Comment ## Further Plan 1. Create condition for the optional parameters, if the parameters is available # Daily Report 2023/07/21 ## Goals :::success - [x] Modify the parameter to take input from CBCF ::: ## Report In the code before, the message is hardcoded in the AMF, so I try to modify it so that it can receive input from CBCF, just like in real cases. In this version, the warning message content is in English language, I will try to modify it so the warning message content can be in Taiwanese language [here](https://hackmd.io/@joshevan/AMF#Build-again-the-message) ## Comment ## Further Plan 1. Insert warning message content in Taiwanese # Daily Report 2023/07/24 ## Goals :::success - [x] Insert warning message content in Taiwanese ::: ## Report Before, the warning message content in the Write Replace Warning Request message can just be inputted in English language. I modify the data coding scheme to change the encoding format so that the Write Replace Warning Request can send a Taiwanese language warning message content ## Comment ## Further Plan 1. Modify the length of the warning message content to be able to receive all messages # Daily Report 2023/07/25 ## Goals :::success - [x] Modify the length of the warning message content ::: ## Report Create dynamic size of messages for the warning message content, so that the warning message content is paged according to its size. Before, the warning message is only 1 page, I modify it so that the warning message can be up to 15 pages ## Comment ## Further Plan 1. Insert the send time cbe/cbcf/amf 2. Insert the receive time in cbcf/amf 3. According the convert table to put the info into cbe and cbcf 4. Test using multiple gNB to see the delay in receiving time of each gNB # Daily Report 2023/07/26 ## Goals :::success - [x] Change the CBE simulator into the CAP-TWP protocol - [x] Change the CBCF to receive in CAP-TWP protocol and match it to the write replace warning request to be sent into the AMF ::: ## Report Before, the CBE simulator just send the message in JSON format, now it is changed to CAP-TWP (Common Alerting Protocol, Taiwan) to match the real cases, CAP-TWP is in XML format with all of its parameter. Other than that, the CBCF must also be changed to match the XML format, so the CBCF receive the data in CAP-TWP then change it to match the write replace warning request to be sent into the AMF. The CBE is still hardcoded, so the next part is to modify it so that it can receive input to variate the message. The complete report can be seen [here](https://hackmd.io/@joshevan/cbcf#Modify-the-CBE-and-CBCF-to-match-the-CAP-TWP) ## Comment ## Further Plan 1. Insert the send time cbe/cbcf/amf 2. Insert the receive time in cbcf/amf 3. Modify the CBE to receive parameters from input to change the data 4. Test using multiple gNB to see the delay in receiving time of each gNB # Daily Report 2023/07/27 ## Goals :::success - [x] Insert the send time cbe/cbcf/amf - [x] Insert the receive time in cbcf/amf ::: ## Report I have inserted the send and receive time in the CBE, CBCF, and AMF. It will shows on the output when running the program ## Comment ## Further Plan 1. Modify the CBE to receive parameters from input to change the data 2. Test using multiple gNB to see the delay in receiving time of each gNB # Daily Report 2023/07/28 ## Goals :::success - [x] Progress Presentation ::: ## Report Today I am preparing for the presentation for my progress in the last month ## Comment ## Further Plan 1. Modify the CBE to receive parameters from input to change the data 2. Test using multiple gNB to see the delay in receiving time of each gNB # Daily Report 2023/07/31 ## Goals :::success - [x] Fixing the topic for patent proposal ::: ## Report Today I am discussing with Prof RT the topic for my patent proposal, the result of the discussion is: - The topic is to do a multicast for the PWS, the procedure might be: from the AMF into the CU, then the CU/xApp do the multicast - The multicast is done via the "tunnel" from the CU to the UE - There is two main points: how to create the tunnel, and how to use the tunnel - Find the way to do it on unicast, show it on wednesday - Modify the unicast, so that it can do the multicast Based on the discussion, I must research about the current result about unicast and also multicast ## Comment ## Further Plan 1. Research about the unicast from the CU to the UE 2. Research about the multicast # Daily Report 2023/08/01 ## Goals :::success - [x] Finding the current result of multicast ::: ## Report Today I found that the 3GPP has defined the spec about MBS (Multicast Broadcast System) architecture. The procedure is it will create a multicast session and the UE will modify the PDU session to join the multicast session. I will use that as a reference for my patent proposal ## Comment ## Further Plan 1. Research about the unicast # Daily Report 2023/08/02 ## Goals :::success - [x] Finding the general procedure for the patent proposal ::: ## Report After knowing about the multicast, I try to create the idea for my patent proposal. The idea is to create a new tunnel between the CU to the UE. The tunnel must has the capabilities to do multicast and able to encapsulate SIB (System Information Block) because SIB is the format that is used in PWS to transmit between RU and UE. ## Comment ## Further Plan 1. Research about the unicast from the CU to the UE # Daily Report 2023/08/03 ## Goals :::success - [x] Create the slides about several types of casting from the AMF or the UPF to the UE ::: ## Report There is a few mechanism about casting, like unicast from AMF to the UE use N1 interface directly, unicast from UPF to the UE use the PDU session with the GTP tunnel, broadcast from AMF to the UE use the RRC protocol from the gNB ## Comment ## Further Plan 1. Research more about the idea of the proposal # Daily Report 2023/08/04 ## Goals :::success - [x] Testing the PWS message with Taiwanese language and more than one page conten ::: ## Report Today, I tested again the PWS message with Taiwanese language and more than one page content. There is a problem where the message can only be shown on the UE if the BBU and the UE is restarted, if we send it again, the message will not shown on the UE. I must search which parameters cause that ## Comment ## Further Plan 1. Finding which parameters cause that and fix that 2. Research more about the idea of the proposal # Daily Report 2023/08/07 ## Goals :::success - [x] Finding the cause of the problem and fix it so that the message can be received multiple times ::: ## Report I have found the cause of the problem, it is the hardcoded message identifier and serial number. In the UE, if it receives message with the same message identifier, serial number, and update number, it will discard the message. I create the mechanism where the serial number is dynamic from user input in CBE, and also if the serial number is the same as before, it will increment the update number to indicate there is an update in the message and it will show in the UE. The complete report can be seen [here](https://hackmd.io/@joshevan/cbcf#Modify-the-CBE-and-CBCF-for-Serial-Number) ## Comment ## Further Plan 1. Research more about the idea of the proposal # Daily Report 2023/08/08 ## Goals :::success - [x] Creating the updated version of the slides ::: ## Report I research more to create the updated version of the slides. I added the O-RAN architecture, F1AP interface between the CU and the DU for the PWS, Downlink procedure in O-RAN using RRC, and my idea that I propose. I found some problems about the idea and I will discuss it further with Prof. RT and my mentor ## Comment ## Further Plan 1. Discuss the problems to find a way for my idea propose # Daily Report 2023/08/09 ## Goals :::success - [x] ::: ## Report ## Comment ## Further Plan 1 # Daily Report 2023/08/10 ## Goals :::success - [x] ::: ## Report ## Comment ## Further Plan 1 # Daily Report 2023/08/11 ## Goals :::success - [x] ::: ## Report ## Comment ## Further Plan 1