Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

  1. Specification upgrade: 

                 This has multiple dimensions. I shall list the tasks required to do the specification upgrade

    1. Service Based Interface Update
      1. Take new openAPI files from specification
      2. Generating the golang code for openAPI
        1. I 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 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
      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
  1. gNodeB Simulator changes. Only critical features listed below
    1. gNodeB handover Xn handover 
    2. gNodeB handover N2 handover
    3. Data support 
  • No labels