1
|
The UE sends a Initial Registration Request to the gNB, which sends it to the AMF in a INITIAL UE message.
|
2
|
On the AMF, the message reaches the SCTP Endpoint (EP). The SCTP EP terminates SCTP protocol, extracts the payload. It sends
a DataInd GRPC message to the NGAP EP.
|
3
|
The NGAP EP parses the request. Both NGAP message parsing and NAS parsing is done by the NGAP EP. It takes the ID that came
in the initial message, and checks for any existing state in any AMF service by looking up the Session Affinity Cache.
|
4
|
To optimally serve UE, AMF maintains affinity of subscriber with service pod internally. If there is session affinity information
for the UE, the NGAP EP forwards the message to that AMF service pod. Otherwise, it load balances the request to any available
AMF service pod.
|
5
|
The AMF service finds the MME to check the identity of the UE. Currently, the MME information is locally configured. The AMF
service sends this request to the EGTPC EP.
|
6
|
The EGTPC EP forwards the request to the UDP proxy after a transaction ID has been allocated.
|
7
|
UDP proxy forwards this message to the MME and gets a response.
|
8
|
The response from the MME is forwarded to EGTPC EP. The EGTPC EP does the transaction matching for the request.
|
9
|
The identity response is sent to the AMF service.
|
10
|
If the security context is not present in the response from the MME, the AMF service decides to authenticate the UE. The authentication
procedure is started by sending a AuthenticationRequest to the REST EP.
|
11
|
REST EP handles all the client and server requests for the AMF, and all NRF interactions. REST EP makes a query to the NRF
to find the AUSF to serve the UE. In further steps, the interaction with the NRF to resolve UDM and PCF have been skipped.
|
12
|
REST EP sends an AuthenticationInformationRequest to the AUSF and gets a response.
|
13
|
The response from the AUSF is forwarded to the AMF service. The authentication procedure between the AMF service and the UE
is not explained here.
|
14
|
If there is any vestigial PDU state for the UE in the SMF, the AMF clears the state. The AMF service sends a message to REST
EP for each SMF that needs to be cleared of state.
|
15
|
On the REST EP, there is no NRF interaction for this message, and the REST-EP forwards this to the SMF identified in the request
from the AMF service.
|
16
|
The response from the SMF is sent to the AMF service by REST EP.
|
17
|
The AMF service sends a UECM registration request to the REST EP.
|
18
|
REST EP uses the NRF to resolve UDM selection for this request and sends a request to the UDM.
|
19
|
The response from the UDM is forwarded to the AMF Service. Retrieval of subscription data information and registering for
notifications for change is not explained here.
|
20
|
The AMF service checks the configuration to see if an AM policy association needs to be done for this registration, and if
it is, sends a request to REST EP.
|
21
|
REST EP does NRF discovery for PCF and sends a request to the PCF.
|
22
|
Response from the PCR is forwarded to the AMF service.
|
23
|
The AMF service sends a registration accept message to NGAP.
|
24
|
NGAP encodes both the NAS message and the NGAP message and sends a message to the SCTP EP.
|
25
|
SCTP EP sends the message out to the gNB.
|
26
|
The rest of the message has been excluded.
|