fix: mobilty -> mobility (#930)

This commit is contained in:
Sukchan Lee 2021-04-13 10:02:52 +09:00
parent 688f2bc249
commit 83720fff9a
5 changed files with 6 additions and 6 deletions

View File

@ -34,7 +34,7 @@ The Open5GS 4G/ 5G NSA Core contains the following components:
The core has two main planes: the control plane and the user plane. These are physically separated in Open5GS as CUPS (control/ user plane separation) is implemented.
The MME is the main **control plane** hub of the core. It primarily manages sessions, mobilty, paging and bearers. It links to the HSS, which generates SIM authentication vectors and holds the subscriber profile; and also to the SGWC and PGWC/SMF, which are the control planes of the gateway servers. All the eNBs in the mobile network (4G basestations) connect to the MME. The final element of the control plane is the PCRF, which sits in-between the PGWC/SMF and the HSS, and handles charging and enforces subscriber policies.
The MME is the main **control plane** hub of the core. It primarily manages sessions, mobility, paging and bearers. It links to the HSS, which generates SIM authentication vectors and holds the subscriber profile; and also to the SGWC and PGWC/SMF, which are the control planes of the gateway servers. All the eNBs in the mobile network (4G basestations) connect to the MME. The final element of the control plane is the PCRF, which sits in-between the PGWC/SMF and the HSS, and handles charging and enforces subscriber policies.
The **user plane** carries user data packets between the eNB/ NSA gNB (5G NSA basestations) and the external WAN. The two user plane core components are the SGWU and PGWU/UPF. Each of these connect back to their control plane counterparts. eNBs/ NSA gNBs connect to the SGWU, which connects to the PGWU/UPF, and on to the WAN. *By having the control and user planes physically separated like this, it means you can deploy multiple user plane servers in the field (eg somewhere with a high speed Internet connection), whilst keeping control functionality centralised. This enables support of MEC use cases, for example.*

View File

@ -131,7 +131,7 @@ void ogs_nas_5gs_mobile_identity_guti_to_nas_guti(
nas_guti->m_tmsi = be32toh(mobile_identity_guti->m_tmsi);
}
void ogs_nas_5gs_nas_guti_to_mobilty_identity_guti(
void ogs_nas_5gs_nas_guti_to_mobility_identity_guti(
ogs_nas_5gs_guti_t *nas_guti,
ogs_nas_5gs_mobile_identity_guti_t *mobile_identity_guti)
{

View File

@ -39,7 +39,7 @@ char *ogs_nas_5gs_suci_from_mobile_identity(
void ogs_nas_5gs_mobile_identity_guti_to_nas_guti(
ogs_nas_5gs_mobile_identity_guti_t *mobile_identity_guti,
ogs_nas_5gs_guti_t *nas_guti);
void ogs_nas_5gs_nas_guti_to_mobilty_identity_guti(
void ogs_nas_5gs_nas_guti_to_mobility_identity_guti(
ogs_nas_5gs_guti_t *nas_guti,
ogs_nas_5gs_mobile_identity_guti_t *mobile_identity_guti);

View File

@ -76,7 +76,7 @@ ogs_pkbuf_t *gmm_build_registration_accept(amf_ue_t *amf_ue)
if (amf_ue->guti_present == true) {
registration_accept->presencemask |= OGS_NAS_5GS_REGISTRATION_ACCEPT_5G_GUTI_PRESENT;
ogs_nas_5gs_nas_guti_to_mobilty_identity_guti(
ogs_nas_5gs_nas_guti_to_mobility_identity_guti(
&amf_ue->guti, &mobile_identity_guti);
mobile_identity->length = sizeof(mobile_identity_guti);

View File

@ -77,7 +77,7 @@ ogs_pkbuf_t *testgmm_build_registration_request(
registration_type->data = test_ue->nas.data;
if (test_ue->registration_request_param.guti) {
ogs_nas_5gs_nas_guti_to_mobilty_identity_guti(
ogs_nas_5gs_nas_guti_to_mobility_identity_guti(
&test_ue->nas_5gs_guti, &mobile_identity_guti);
registration_request->mobile_identity.length =
sizeof(ogs_nas_5gs_mobile_identity_guti_t);
@ -369,7 +369,7 @@ ogs_pkbuf_t *testgmm_build_de_registration_request(
de_registration_type->access_type = test_ue->nas.access_type;
if (test_ue->nas_5gs_guti.m_tmsi) {
ogs_nas_5gs_nas_guti_to_mobilty_identity_guti(
ogs_nas_5gs_nas_guti_to_mobility_identity_guti(
&test_ue->nas_5gs_guti, &mobile_identity_guti);
deregistration_request_from_ue->mobile_identity.length =
sizeof(ogs_nas_5gs_mobile_identity_guti_t);