I. How to Clone Source Code

...

|── 5GCEmulator
│   ├── go.mod
│   ├── go.sum
│   └── ngc
|── INFO.yaml
|── edgecontroller
│   ├── CHANGELOG.md
│   ├── LICENSE
│   ├── Makefile
│   ├── README.md
│   ├── SECURITY.md
│   ├── app.go
│   ├── app_test.go
│   ├── authentication.go
│   ├── authority.go
│   ├── cce.go
│   ├── cce_suite_test.go
│   ├── cmd
│   ├── cnca
│   ├── constants.go
│   ├── credentials.go
│   ├── credentials_test.go
│   ├── dns_config.go
│   ├── dns_config_app_alias.go
│   ├── dns_config_app_alias_test.go
│   ├── dns_config_test.go
│   ├── docker
│   ├── docker-compose.yml
│   ├── edgednscli
│   ├── fpga
│   ├── go.mod
│   ├── go.sum
│   ├── gorilla
│   ├── grpc
│   ├── http
│   ├── internal
│   ├── jose
│   ├── k8s
│   ├── kubevirt
│   ├── mock
│   ├── mysql
│   ├── network-edge
│   ├── nfd-master
│   ├── node.go
│   ├── node_app.go
│   ├── node_app_test.go
│   ├── node_app_traffic_policy.go
│   ├── node_app_traffic_policy_test.go
│   ├── node_dns_config.go
│   ├── node_dns_config_test.go
│   ├── node_grpc_target.go
│   ├── node_grpc_target_test.go
│   ├── node_interface.go
│   ├── node_interface_traffic_policy.go
│   ├── node_test.go
│   ├── pb
│   ├── pki
│   ├── sriov
│   ├── swagger
│   ├── telemetry
│   ├── test
│   ├── traffic_policy.go
│   ├── traffic_policy_kube_ovn.go
│   ├── traffic_policy_kube_ovn_test.go
│   ├── traffic_policy_test.go
│   ├── ui
│   └── uuid
|── edgenode
│   ├── CHANGELOG.md
│   ├── LICENSE
│   ├── Makefile
│   ├── README.md
│   ├── build
│   ├── cmd
│   ├── configs
│   ├── docker-compose.yml
│   ├── fpga
│   ├── go.mod
│   ├── go.sum
│   ├── internal
│   ├── pkg
│   ├── tools
│   └── ug-images
|── verify.sh

36 directories, 48 files

III. Source Code Structure Description

TODO..The source code of 5G MEC/Slice System mainly consists of 3 modules: 5GCEmulator, edgecontroller, and edgenode.

/5GCEmulator 

This folder contains the files that implements part of the functions of the 5GC. For the time being, the functions that are implemeneted include traffic offloading,  which is provided by NEF (network exposure function). 

/edgecontroller

This folder contains the files to provide the functionality to configure one or more edge nodes and the application services that run on those nodes.

/edgenode

This folder contains the files that are needed for edge application deployments. It also consists of APIs that are used for the discovery of application services.