Page Comparison

...

1. 1. Service Based Interface Update
      1. Take new openAPI files from specification
      2. Generating the golang code for openAPI
         1. I created Created golang code using the openapi image/container for one yaml file. I need to automate the process for all yaml files
         2. I can Can do this for release 17 files and for release 18 files. Which release should we target? I think we should target R18. What do you think? Here is the release timelines: https://www.3gpp.org/specifications-technologies/releases
      3. Use newly generate openapi models in at least 1 or 2 Network Functions
   2.  PFCP Specification update. 
      1. Impacts UPF & SMF 
      2. UPF currently uses go-pfcp project and SMF uses local pfcp code. We should plan to move to go-pfcp as standard way.
   3. NAS specification upgrade 
      1. Impacts SMF, AMF network functions
      2. Impacts simulator like gnbsim
      3. Impacts the testing with real gNodeB, mobiles. 
   4. NGAP specification upgrade 
      1. Impacts AMF network function
         1. Created golang code (asn1 → proto → go) but the resulting GO code looks very different to the structure of the current ngap repository. What is the appropriate process to follow?
         2. ngap repository uses/calls aper repository. Does the aper repository also needs to be updated?
      2. Impacts simulator like gnbsim
      3. Impacts the testing with real gNodeB
   5. gtpu specification upgrade (low priority)
      1. Impacts UPF network function
      2. Impacts optionally SMF 
      3. Impacts gnbsim
      4. impacts the testing with real gNodeB
2. gNodeB Simulator changes. Only critical features listed below
   1. gNodeB handover Xn handover 
   2. gNodeB handover N2 handover
   3. Data support