fix: arrange doc directory
This commit is contained in:
@@ -1,24 +0,0 @@
|
||||
# 5GC OMC架构及功能
|
||||
|
||||
## 架构图
|
||||
|
||||

|
||||
|
||||
## 开发平台
|
||||
|
||||
1. 采用B/S模式,运行在linux系统,支持x86和arm平台
|
||||
2. 前端:HTML+CSS+JS(vue3)
|
||||
3. 后端:Golang+MySQL+Redis, Nginx(optional)
|
||||
|
||||
## 功能清单
|
||||
|
||||
1. 拓扑管理(State/Monitor):网络拓扑,系统状态等
|
||||
2. 故障管理(FM):活动告警/历史告警等
|
||||
3. 配置管理(CM):网元管理,参数配置等
|
||||
4. 性能管理(PM):性能统计相关指标项的订阅任务,数据报表,性能门限等
|
||||
5. 操作维护(MML):网元MML操作,UDM用户数据MML,OMC MML等
|
||||
6. 日志管理(Log):操作日志,安全日志,告警日志等
|
||||
7. 跟踪管理(Trace):信令跟踪任务创建,信令分析等
|
||||
8. 安全管理(Security):用户管理,用户组管理,权限管理等
|
||||
9. 系统管理(System): 菜单管理,字典管理,系统信息,调度任务等
|
||||
10. 北向接口(NBI: Northbound Interface): 可选接口,定制化接口,北向接口服务,资源配置数据,性能统计数据, 性能黄金指标, 告警上报, 4A等
|
||||
@@ -1,7 +0,0 @@
|
||||
## EMS Database
|
||||
|
||||
---
|
||||
|
||||
### 1. Diagram of OMC database
|
||||
|
||||

|
||||
11
docs/dataschema/07-5GC OMC Database Diagrams.md
Normal file
11
docs/dataschema/07-5GC OMC Database Diagrams.md
Normal file
@@ -0,0 +1,11 @@
|
||||
## OMC Database Diagrams
|
||||
|
||||
---
|
||||
|
||||
### Diagram of OMC database
|
||||
|
||||

|
||||
|
||||
### OMC Database Table Creation Script
|
||||
|
||||
Refer to omc_db.sql
|
||||
BIN
docs/interfaces/05-5GC OMC restful intefaces v1.10.pdf
Normal file
BIN
docs/interfaces/05-5GC OMC restful intefaces v1.10.pdf
Normal file
Binary file not shown.
@@ -1480,56 +1480,13 @@ Example:
|
||||
|
||||
### 10.1 UDM签约用户
|
||||
|
||||
#### 10.1.1 查询/增加/修改/删除
|
||||
#### 10.1.1 查询/增加/修改/删除/批量增加/批量修改/批量删除
|
||||
|
||||
用MML接口
|
||||
|
||||
* Uri
|
||||
|
||||
```uri
|
||||
/api/rest/ueManagement/v1/elementType/UDM/objectType/subData/{imsi}?neId={neId}
|
||||
```
|
||||
* Relations
|
||||
|
||||
OMC -> UDM
|
||||
* Params
|
||||
|
||||
OMC-FE -> OMC-BE, neId={neId}, 指定UDM的neId
|
||||
* Method
|
||||
|
||||
GET
|
||||
* Body
|
||||
|
||||
NA
|
||||
* Return
|
||||
|
||||
```json
|
||||
// SmfUEInfo SMF在线用户信息
|
||||
type SubData struct {
|
||||
IMSI string `json:"imsi"` // SIM卡号
|
||||
MSISDN string `json:"msisdn""`
|
||||
Amf string `json:"amf"` // Amf
|
||||
Status string `json:"status"` // 状态
|
||||
Ki string `json:"ki"` // ki
|
||||
AlgoIndex string `json:"algoIndex"` //
|
||||
Opc string `json:"opc"`
|
||||
}
|
||||
```
|
||||
|
||||
```json
|
||||
{
|
||||
"data":
|
||||
{
|
||||
"imsi": "460000100000010",
|
||||
"msisdn": "12307550010",
|
||||
"...": "..."
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### 10.2 UDM鉴权用户
|
||||
|
||||
#### 10.2.1 查询/增加/修改/删除
|
||||
#### 10.2.1 查询/增加/修改/删除/批量增加/批量修改/批量删除
|
||||
|
||||
用MML接口
|
||||
|
||||
@@ -1778,7 +1735,7 @@ Example:
|
||||
* Uri
|
||||
|
||||
```uri
|
||||
/api/rest/ueManagement/v1/elementType/n3iwf/objectType/ueInfo?imsi={imsi}&msisdn={msisdn}&neId={neId}
|
||||
/api/rest/ueManagement/v1/elementType/n3iwf/objectType/ueInfo?imsi={imsi}&neId={neId}
|
||||
```
|
||||
* Relations
|
||||
|
||||
@@ -1829,6 +1786,166 @@ type N3iwfUEData struct {
|
||||
}
|
||||
```
|
||||
|
||||
### 10.7 PCF用户策略控制信息
|
||||
|
||||
#### 10.7.1 查询/增加/修改/删除
|
||||
|
||||
说明:为了避免用户策略控制信息太多,PCF可做限制,如返回不超过100条
|
||||
|
||||
* URI
|
||||
|
||||
```uri
|
||||
/api/rest/ueManagement/v1/elementType/pcf/objectType/ueInfo?imsi={imsi}&msisdn={msisdn}&neId={neId}
|
||||
```
|
||||
* Relations
|
||||
|
||||
OMC -> PCF
|
||||
* Params
|
||||
|
||||
* OMC-FE -> OMC-BE, neId={neId}, 指定PCF的neId
|
||||
* OMC -> PCF, 查询(GET):imsi={imsi}/msisdn={msisdn},两个必填一个,都填以imsi为主,如果都不指定,则查询全部ueInfo
|
||||
* OMC -> PCF, POST/PUT/DELETE: imsi={imsi} 必选
|
||||
* Method
|
||||
|
||||
GET/POST/PUT/DELETE
|
||||
* Body (POST/PUT)
|
||||
|
||||
```json
|
||||
// PCF UEInfo PCF用户策略控制信息
|
||||
type PcfUser struct {
|
||||
Imsi string `json:"imsi,omitempty"`
|
||||
Msisdn string `json:"msisdn,omitempty"`
|
||||
|
||||
Rfsp int `json:"rfsp,omitempty"`// 0-256
|
||||
Sar string `json:"sar,omitempty"`
|
||||
|
||||
PccRules string `json:"pccRules,omitempty"`
|
||||
SessRules string `json:"sessRules,omitempty"`
|
||||
UePolicy string `json:"uePolicy,omitempty"`
|
||||
QosAudio string `json:"qosAudio,omitempty"`
|
||||
QosVideo string `json:"qosVideo,omitempty"`
|
||||
HdrEnrich string `json:"hdrEnrich,omitempty"`
|
||||
}
|
||||
```
|
||||
* Return (GET)
|
||||
|
||||
```json
|
||||
// PCF UEInfo PCF用户策略控制信息
|
||||
type PcfUser struct {
|
||||
Imsi string `json:"imsi,omitempty"`
|
||||
Msisdn string `json:"msisdn,omitempty"`
|
||||
|
||||
Rfsp int `json:"rfsp,omitempty"`// 0-256
|
||||
Sar string `json:"sar,omitempty"`
|
||||
|
||||
PccRules string `json:"pccRules,omitempty"`
|
||||
SessRules string `json:"sessRules,omitempty"`
|
||||
UePolicy string `json:"uePolicy,omitempty"`
|
||||
QosAudio string `json:"qosAudio,omitempty"`
|
||||
QosVideo string `json:"qosVideo,omitempty"`
|
||||
HdrEnrich string `json:"hdrEnrich,omitempty"`
|
||||
}
|
||||
```
|
||||
|
||||
```json
|
||||
{
|
||||
"data": [
|
||||
{
|
||||
"imsi": "460000100000010",
|
||||
"msisdn": "12307550010",
|
||||
"rfsp": 1,
|
||||
"sar": "",
|
||||
......
|
||||
},
|
||||
{
|
||||
"imsi": "460000100000038",
|
||||
"msisdn": "12307550038",
|
||||
"rfsp": 2,
|
||||
"sar": "",
|
||||
......
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
#### 10.7.2 批量增加/批量修改/批量删除
|
||||
|
||||
* URI
|
||||
|
||||
```uri
|
||||
/api/rest/ueManagement/v1/elementType/pcf/objectType/ueInfo/number?imsi={imsi}&neId={neId}
|
||||
```
|
||||
|
||||
* Relations
|
||||
|
||||
OMC -> PCF
|
||||
* Params
|
||||
|
||||
* OMC-FE -> OMC-BE, neId={neId}, 指定PCF的neId
|
||||
* OMC -> PCF, imsi={imsi} 必选
|
||||
* Method
|
||||
|
||||
POST/PUT/DELETE
|
||||
* Body
|
||||
|
||||
```json
|
||||
// PCF UEInfo PCF用户策略控制信息
|
||||
type PcfUser struct {
|
||||
Imsi string `json:"imsi,omitempty"`
|
||||
Msisdn string `json:"msisdn,omitempty"`
|
||||
|
||||
Rfsp int `json:"rfsp,omitempty"`// 0-256
|
||||
Sar string `json:"sar,omitempty"`
|
||||
|
||||
PccRules string `json:"pccRules,omitempty"`
|
||||
SessRules string `json:"sessRules,omitempty"`
|
||||
UePolicy string `json:"uePolicy,omitempty"`
|
||||
QosAudio string `json:"qosAudio,omitempty"`
|
||||
QosVideo string `json:"qosVideo,omitempty"`
|
||||
HdrEnrich string `json:"hdrEnrich,omitempty"`
|
||||
}
|
||||
```
|
||||
* Return
|
||||
|
||||
```json
|
||||
// PCF UEInfo PCF用户策略控制信息
|
||||
type PcfUser struct {
|
||||
Imsi string `json:"imsi,omitempty"`
|
||||
Msisdn string `json:"msisdn,omitempty"`
|
||||
|
||||
Rfsp int `json:"rfsp,omitempty"`// 0-256
|
||||
Sar string `json:"sar,omitempty"`
|
||||
|
||||
PccRules string `json:"pccRules,omitempty"`
|
||||
SessRules string `json:"sessRules,omitempty"`
|
||||
UePolicy string `json:"uePolicy,omitempty"`
|
||||
QosAudio string `json:"qosAudio,omitempty"`
|
||||
QosVideo string `json:"qosVideo,omitempty"`
|
||||
HdrEnrich string `json:"hdrEnrich,omitempty"`
|
||||
}
|
||||
```
|
||||
|
||||
```json
|
||||
{
|
||||
"data": [
|
||||
{
|
||||
"imsi": "460000100000010",
|
||||
"msisdn": "12307550010",
|
||||
"rfsp": 1,
|
||||
"sar": "",
|
||||
......
|
||||
},
|
||||
{
|
||||
"imsi": "460000100000038",
|
||||
"msisdn": "12307550038",
|
||||
"rfsp": 2,
|
||||
"sar": "",
|
||||
......
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
## 11 系统管理
|
||||
|
||||
### 11.1 OMC系统
|
||||
14157
docs/interfaces/08-OMC FE2BE HTTP API Interfaces.md
Normal file
14157
docs/interfaces/08-OMC FE2BE HTTP API Interfaces.md
Normal file
File diff suppressed because one or more lines are too long
BIN
docs/interfaces/08-OMC HTTP Restful API Interfaces V1.01.pdf
Normal file
BIN
docs/interfaces/08-OMC HTTP Restful API Interfaces V1.01.pdf
Normal file
Binary file not shown.
11777
docs/interfaces/08-OMC HTTP Restful API Interfaces.md
Normal file
11777
docs/interfaces/08-OMC HTTP Restful API Interfaces.md
Normal file
File diff suppressed because it is too large
Load Diff
32
docs/overview/04-5GC OMC Architecture.md
Normal file
32
docs/overview/04-5GC OMC Architecture.md
Normal file
@@ -0,0 +1,32 @@
|
||||
---
|
||||
OMC Overview
|
||||
---
|
||||
|
||||
## Introduction to OMC
|
||||
|
||||
The Core Network OMC (Operation and Maintenance Center) is a central facility used by operators to manage and maintain core network equipment. It typically includes modules for network monitoring, fault management, performance management, configuration management, security management, and other functions to ensure the smooth operation and efficient maintenance of core network equipment. By monitoring and managing core network equipment, the OMC can quickly identify and resolve network faults in real-time, improve network performance, ensure network security, and enhance operational efficiency. The OMC plays a crucial role in the network operations and maintenance of operators, serving as a key element in ensuring stable network operation.
|
||||
|
||||
## System Architecture
|
||||
|
||||

|
||||
|
||||
## Platform
|
||||
|
||||
1. Operating System: Linux
|
||||
2. Hardware Platform: X86/ARM64
|
||||
3. Network Architecture: B/S mode
|
||||
4. Front-end Languages: HTML+CSS+JS (Vue3)
|
||||
5. Back-end Languages: Golang+MySQL+Redis, Nginx (optional)
|
||||
|
||||
## Features
|
||||
|
||||
1. Topology Management (State/Monitor): Network topology, system status, etc.
|
||||
2. Fault Management (FM): Active alarms, historical alarms, etc.
|
||||
3. Configuration Management (CM): NE (Network Element) management, parameter configuration, etc.
|
||||
4. Performance Management (PM): Subscription tasks for performance-related metrics, data reports, performance thresholds, etc.
|
||||
5. Operation and Maintenance (MML): NE MML operations, UDM (User Data Management) MML, OMC (Operation and Maintenance Center) MML, etc.
|
||||
6. Log Management (Log): Operation logs, security logs, alarm logs, etc.
|
||||
7. Tracking Management (Trace): Signaling tracking task creation, signaling analysis, signaling capture, etc.
|
||||
8. Security Management (Security): User management, role management, current online users, permission management, etc.
|
||||
9. System Management (System): Menu management, dictionary management, system information, scheduling tasks, etc.
|
||||
10. Northbound Interface (NBI): Optional interfaces, customized interfaces, northbound interface services, resource configuration data, performance statistics data, performance golden indicators, alarm reporting, 4A, etc.
|
||||
31
docs/overview/04-5GC OMC 介绍.md
Normal file
31
docs/overview/04-5GC OMC 介绍.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
OMC架构与功能
|
||||
---
|
||||
## OMC简介
|
||||
|
||||
核心网OMC(Operation and Maintenance Center)是运营商用于管理和维护核心网设备的中心。它通常包括网络监控、故障管理、性能管理、配置管理、安全管理等功能模块,用于确保核心网设备的正常运行和高效维护。OMC通过监控和管理核心网设备,可以实时发现和解决网络故障,提高网络性能,保障网络安全,提升运营效率。OMC在运营商的网络运维中扮演着重要的角色,是保障网络稳定运行的关键环节。
|
||||
|
||||
## 系统架构
|
||||
|
||||

|
||||
|
||||
## 开发平台
|
||||
|
||||
1. 操作系统:linux
|
||||
2. 硬件平台:X86/ARM64
|
||||
3. 网络架构: B/S模式
|
||||
4. 前端语言:HTML+CSS+JS(vue3)
|
||||
5. 后端语言:Golang+MySQL+Redis, Nginx(optional)
|
||||
|
||||
## 功能清单
|
||||
|
||||
1. 拓扑管理(State/Monitor):网络拓扑,系统状态等
|
||||
2. 故障管理(FM):活动告警/历史告警等
|
||||
3. 配置管理(CM):网元管理,参数配置等
|
||||
4. 性能管理(PM):性能统计相关指标项的订阅任务,数据报表,性能门限等
|
||||
5. 操作维护(MML):网元MML操作,UDM用户数据MML,OMC MML等
|
||||
6. 日志管理(Log):操作日志,安全日志,告警日志等
|
||||
7. 跟踪管理(Trace):信令跟踪任务创建,信令分析,信令抓包等
|
||||
8. 安全管理(Security):用户管理,角色管理,当前在线用户,权限管理等
|
||||
9. 系统管理(System): 菜单管理,字典管理,系统信息,调度任务等
|
||||
10. 北向接口(NBI: Northbound Interface): 可选接口,定制化接口,北向接口服务,资源配置数据,性能统计数据, 性能黄金指标, 告警上报, 4A等
|
||||
BIN
docs/overview/04-5GC OMC 介绍.pdf
Normal file
BIN
docs/overview/04-5GC OMC 介绍.pdf
Normal file
Binary file not shown.
BIN
docs/overview/image/ems-arch.jpg
Normal file
BIN
docs/overview/image/ems-arch.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 66 KiB |
@@ -63,4 +63,11 @@ cd php-7.3.5/
|
||||
sed -i "s/freetype-config/pkg-config/g" ./configure
|
||||
sed -i "s/freetype-config/pkg-config/g" ./ext/gd/config.m4
|
||||
sed -i "s/FREETYPE2_CONFIG --cflags/FREETYPE2_CONFIG freetype2 --cflags/g" ./configure
|
||||
sed -i "s/FREETYPE2_CONFIG --libs/FREETYPE2_CONFIG freetype2 --cflags/g" ./configure
|
||||
sed -i "s/FREETYPE2_CONFIG --libs/FREETYPE2_CONFIG freetype2 --cflags/g" ./configure
|
||||
|
||||
|
||||
# 导入参数配置文件
|
||||
D:\local.git\ems.agt\tools\loadpconf> go run .\loadpconf.go .\load.go .\db.go -p ..\..\config\param\udm_param_config.yaml
|
||||
# 导入mml配置文件
|
||||
# 需配置load
|
||||
D:\local.git\ems.agt\tools\loadmconf> go run .\loadmconf.go .\load.go .\db.go -m ..\..\config\mml\system\mme_sys_mml_config.yaml
|
||||
Reference in New Issue
Block a user