Lesson finished
Up next: NGAP and 5G NAS Procedures, Message Structure and Week Recap
Unlock all 9 lessons of 5G TestingFull course ₹40,000 · paid
SMF, UDM, UPF and HTTP/2 in the 5G Core
A free lesson from Skill-Lync's 5G Testing course, on Grow by Skill-Lync · Last updated 16 Nov 2026 · Session: “Week 1 Session 2”
What will you learn in this free 5G Testing lesson?
The lesson describes the session management function, covering session handling, IP assignment and its links to UPF, AUSF and NRF. It then covers UDM for subscriber data and authentication, UPF packet routing and forwarding, and HTTP/2 features used on 5G core interfaces.
- SMF session creation, modification and IP allocation
- UDM: subscriber data, authentication and authorization
- UPF packet routing, forwarding and flow-based processing
- HTTP/2 multiplexing, header compression and security
What comes after lesson 2?
The next free lesson is lesson 3, “NGAP and 5G NAS Procedures, Message Structure and Week Recap” (21 min). Later in Skill-Lync's 5G Testing course (paid): lesson 4, Week 2 Session 1; lesson 5, Week 2 Session 2; lesson 6, Week 2 Session 3. The full course has 9 lessons (4 h 10 min of video); see the course overview or its price and syllabus.
Lesson transcript
Machine transcript of the lesson audio (lightly cleaned). Technical terms may contain errors; the video is the reference.
Session and Mobility Management Function or SMF. Well, SMF is one of most privileged or I would say it's one of the most primarily used jewel of the crown sort of a management function that is involved in session management, right? So, the session and mobility management function is a very critical component of the 5G core network architecture. It is responsible for session management and mobility management of the user equipment or UE. SMF, however, interacts with other network functions such as the user plane function, UPF, authentication server function, AUSF, network repository function, NRF, to provide seamless connectivity and mobility management to the UE.
Well, to divide the functionalities across session and mobility management, we have the session management in SMF. The SMF is responsible for creating, modifying and terminating sessions for the UE. SMF is also responsible for assigning IP addresses and allocating resources to the UE for the duration of the session. SMF also interacts with the user plane function to ensure that the user's data is routed efficiently and securely between the UE and the Internet. When it comes to mobility management in SMF, SMF manages the mobility of the UE, ensuring uninterrupted connectivity as UE move across different network coverage areas.
SMF maintains a record of the UE's location and network status, allowing it to direct the UE's traffic to appropriate network functions. SMF also interacts with other network functions to facilitate handovers between different network technologies and access networks. SMF interacts as well with other network functions. SMF interacts with the AUSF to authenticate and authorize the UE, ensuring that only authorized UE's can access the 5G network. SMF also interacts with the NRF to discover the available network functions and select the appropriate ones for UE. In addition, SMF interacts with UPF to ensure that the user's data traffic is properly routed and the quality of service or commonly known as QoS requirements are met.
So, as we can see on the diagram, SMF is connected to a lot of components. The commonly discussed component as we had just now discussed is the AMF. Then we have NRF, UDR, AUSF, UDM, UPF and that's it. And obviously with other SMFs. So, it is involved in indirect communication with devices via AMF regarding session management. Next, we have the, like as I discussed, it interacts with other core network entities like PCF, UPF, CHF to perform functionalities like user plane management, policy enforcement and charging related functionalities.
In conclusion, SMF is a really important function in the 5G core network that provides session management and mobility management for UE. SMF is responsible for creating, modifying and terminating sessions and managing mobility of UE. It interacts with other network entities as PCF, CHF to provide seamless connectivity, charging, policy enforcement like function and mobility management for UE. Next, we have policy control function or PCF. Well, PCF is also a very important function that is responsible for enforcing or controlling the policies. Well, policy enforcement is done by SMF per se.
But, you know, to create the policies, PCF is, you know, the go-to function. The PCF is the network function in 5G core that is responsible for policy and charging control. It manages the policies that determine how network resources are allocated and how services are delivered to the user equipment. It also manages the charging functions that determine how network usage is charged. In this case, CHF. Some of the key functionalities of PCF are policy management, charging management, traffic steering. To start with policy management, PCF is responsible for managing policies that control the allocation of network resources and delivery of the services.
Basically, with respect to managing the data sessions, these policies can be based on various parameters such as UV's identity, location and QoS requirements. Then we have a big part maintaining the QoS that is part of a bigger mechanism known as the PCC, which is responsible for flow based and QoS, flow based QoS management. So, we have the charging management also that comes, as we can see, charging management. It is PCF is connected to the CHF via the N28 interface. It is responsible for managing the charging functions that determines how the network usage is charged.
It manages the charging rules and policies that apply to different users, services and network resources. Then we have traffic steering. PCF is responsible for steering the traffic to the appropriate network functions and services based on the policies and charging rules. Then obviously, we talked about the QoS management that is responsible for managing the QoS parameters that ensure a high quality end user experience. In short, PCF interacts with network functions in the 5G core, such as the AMF, SMF, and then it interacts with CHF, UPF, all these sort of functionalities to provide charging and policy control for UV.
Or should I say, policy and charging control for UV. Overall, PCF does play a very critical role in the 5G core by managing the policies and charging functions that control allocation of the network resources and delivery of services. Its functions are really essential for efficient operation of 5G network and delivery of new and innovative services. To start with, PCF is essentially related to the policy control, but it plays an inherent role in charging as well. It plays an inherent role in access management also for the access management for the PDU session.
And then it detects the packet flows and sort of like it detects the packet flows and forces the charging and all these things is done by SMF. But packet flow detection and management and analytics of the networks is done at PCF level as well. Next up, we have the charging function or the CHF. The charging function, as we can see, it communicates with SMF and PCF for providing charging related services. Obviously, it has to communicate. I mean, SMF communicates with the UPF and then UPF reports the usage reports and based on that, charging is done.
Well, charging network function in 5G is responsible for managing charging information related to the usage of network services and resources by the UE. Secondly, it collects processes and aggregates charging data and generates charging records or CDRs that are used for billing and accounting purposes. The CHF interacts with other charging network related, charging related network functions in the 5G core, such as the charging trigger function. That is the CTF, that is the CTF, right? Then it interacts with the charging gateway function, the CGF. It interacts with the billing domain to provide end-to-end charging services.
Well, CTF is responsible for collecting charging data from the network functions and services that the UE uses. It generates charging triggers that are sent to the CHF to initiate charging. CHF is responsible for managing the charging sessions between UE and CHF. CGF is responsible for managing the sessions between UE and CHF. It acts as a mediator between the UE and CHF and does provide charging related services such as online charging, offline charging and event-based charging. The billing domain is responsible for managing the charging data that is generated by the CHF.
It provides billing services such as invoicing, rating and accounting. So, overall, the CHF and other charging related network functions plays a critical role in the 5G code by managing the charging data and providing end-to-end charging services. Well, these functions are essential mostly by the network operators so that they can charge the end-users for using the services. Now, it comes to next up is the offline and online charging or should we say online and offline charging. So, online charging is a real-time charging mechanism that enables the charging of the network usage while the user equipment or UE is connected to the network.
In this case, the CHF will interact with the CGF or the charging gateway function to provide online services to the UE. Online charging can be used for prepaid or post-paid charging models and is typically used for services such as voice calls, data usage and messaging. Offline charging, on the other hand, is a charging mechanism that enables the charging of network usage after the UE has disconnected from the network. In this case, the CHF in turn converts to motor charging. Next, with the billing domain to provide offline charging services to the UV. Offline charging is typically used for postpaid charging and is used for services such as data usage, messaging and content downloads. In both the cases, however, CHF is inherently responsible for collecting, processing and aggregating the charging data, generating the CDRs or the charging data records and providing charging information to the billing system.
The CGF and the BD play a very crucial role in providing charging related services such as online and offline charging, rating, invoicing and accounting, which we already discussed. Overall, the CHF and other charging related functions are essential as discussed for the billing purposes and all. Next, next up, we have the unified data management function or the UDM. So, UDM will be having connectivities again with SMF, AMF, right? It is sort of our HSS that we discussed in 4G, right? It is used for generation and authentication of the data for verifying the attached devices by UDM.
So, UDM is having different parts that we will be discussing now. So, authorization of access for selected users is based on the subscription information. That is important that based on their subscription, how the users will be authorized or what services the users will be authorized to use will be based on the subscription model that is with the operator. Now, coming to the different parts of the UDM, right? We have the UDR, AUSF and ASMF, right? And along with different interactions, I mean, it also interacts with the PCF, then UDC as we can see, right?
So, starting with UDR, the UDR is a central repository for all user-related data in the 5G core network. It stores, manages the user data such as subscription data, user profile, and authentication credentials along with access authorization. The AUSF, or the authentication server function, on the other hand, is responsible for managing the user authentication and authorization in the 5G core network. It is basically the similar functionality that we had in 4G. It just is responsible for authentication authorization. And it validates the user identity and provides authentication credentials to the network functions and services that the user wants to access.
Then we have the authorization server function, or the ASMF. As we can see, if we go back, I think we have the diagram of ASMF here. I don't think we have ASMF mentioned, but more or less what it does is, essentially, it's an internal part of UDR. So, what it will do is it's responsible for managing the user access authorization in the 5G core network, right? It is, it determines whether the user is authorized to access a specific service or network function based on the user profile, right?
Then we have the user data coverage, convergence, or the UDC. The UDC is responsible for managing user data convergence in the 5G network. Then, again, we have PCF, that connectivity is via the AMF, and then, again, it is responsible for quality QoS. However, overall, the UDM is essentially responsible for managing subscriber's data, and then, authentication and authorization. These are two different aspects we need to be, we need to empathize on these two areas, authentication and authorization of the services. So, together, with all these mentioned services, UDM is responsible to manage, the U is access, to the network, and after that is done, then, U is authorized to access the services.
Next up, we have the UPF or the user plane function. UPF is a key network function in 5G, right? That is responsible for forwarding and managing of the user data packets. It is responsible for several other functions, including packet routing, forwarding, flow-based processing, etc. I mean, it acts as the main reference point for mobility within and between different rats. It is the anchor point, basically. So, when it comes to packet routing, packet forwarding, and flow-based processing, we will start with packet routing. UPF is responsible for routing the user data packets to the correct destination, based on the destination address and network conditions.
Then, we have packet forwarding. The UPF is responsible for forwarding the user data packets from source to destination, based on the routing information. Then, we have flow-based processing. UPF is responsible for processing the user data packets, based on the flow information. It can apply, also, traffic shaping and traffic policies based on the user profile, service type, and QS requirement. Well, it also supports several network services, including data optimization, DPI, right? Network slicing. Data optimization is the process of compressing and decompressing the user data packets to reduce the data usage.
DPI, as we know, is a process of analyzing the data packets to identify the application type and apply specific policies based on the application requirements. Then, we have network slicing, which the UPF is complying to. That is, a process of dividing the network into several virtual network slices we saw in SSC modes, each with its own UPF to support different services and user equipments. So, as we can see, it is a router that routes the packets from the CDN to the UE and vice versa. It can carry out packet inspection.
It is very useful for lawful interception, like UPF takes the data and gives it to the lawful management entities, right? Like the MDF servers. Then, it generates an N6 tunnel between the CDN and to the N device, right? Via the radio. So, as we already discussed, that it enforces the policy rules for the user plane, including gating, redirection, and traffic steering, lawful intercept. It also generates reports and traffic usage and then sends these reports to the SMF and SMF interns, sends those reports to CHF, which generates the bill for the user.
Then, it manages the QoS based on basically uplink, enforcing the UL and DL rates and making marking reflective QoS in the downlink. That's it from the UPF point of view. So, UPF is sort of a router that routes the packets. And it is crucial in managing and forwarding the user data packets in the 5G core network. It enables the delivery of new and innovative services to the users and ensures an efficient operation continues in the 5G network. Next up, we will be talking about different protocols commonly used in 5G.
First up is the packet forwarding control protocol or commonly known as PFCP. It runs on UDP, as we can see. It is a communication protocol that is used in the 5G core network to manage and control the user plane data and forwarding between different network functions. So, it manages the user plane data and forwards data between different user plane or network functions. It is responsible for the control and management of data forwarding policies, such as the QoS and flow based forwarding rules. So, essentially, this PFCP is a protocol that sits between SMF and UPF, right?
So, that's why its functionalities will be what the PCF already does, right? So, mostly the user data communication, all these things will be happening from UDP to CDN. So, similarly, that runs on UDP, you know, all those UDP packets. And then we have this SMF communicating with UPF with the PFCP protocol that runs on UDP. The destination port of PFCP is 8805. And now let's have a look at some of the key procedures or the features of PFCP. The first feature that comes to our mind is the control and management of data forwarding policies.
The PFCP allows for definition and modification of forwarding policies, such as QoS and flow based forwarding rules. This enables the network to prioritize and manage the forwarding of the user data packets based on the user's service requirements. Then we have control of the UPF functionality. PFCP enables the control of UPF functionality, such as load balancing and congestion control. This ensures efficient utilization of the network resources and enhances the user experience. Then we have real-time network monitoring. PFCP enables the real-time monitoring of the network traffic and provides accurate and up-to-date information to the network functions.
This information is used to optimize the network performance and improve the user experience. Then we have dynamic network monitoring. Configuration. PFCP allows for dynamic configuration of the network functions and policies. This enables the network to adapt to changing traffic conditions and ensure efficient utilization of different network resources. Well, PFCP has also, it generates session reports and then sends to SMF, already discussed. I mean, the UPF does. So, PFCP actually carries that information in the form of session reports, right? Just like we had the session, there are two different types of procedures. One is node-related procedure, right? Like PFCP association, then PFCP, then setup, as all these things will be carried out by the node-related procedures, like setting of the connection between SMF and UPF, then terminating the PFCP release.
All these things will be a part of node-related procedures. When it comes to session-related procedures, PFCP session establishment procedure is one of the procedures that is related to establishment of sessions, 5G session, 5G session, 5G session comes up with PFCP session establishment message. Then there are session modification procedures, right? So, PFCP session modification and session report. These all comes as a part of session-related procedures. So, when a new protocol data unit or PDU session is established, SMF selects at least one UPF to handle it. Then, SMF establishes a PFCP session with its UPF and supplies the required information for directing the UPF to manage the user planed traffic for the PDU session.
So, first thing, when a PDU session is established, SMF selects at least one UPF. For that, we have node-related procedures. Then, when SMF establishes a PFCP session with its UPF and it supplies the required information for directing the UPF for managing the user planed traffic, it uses all those session-related procedures, right? So, overall, PFCP is a critical protocol in the 5G core network for enabling efficient and flexible management and control of user planed data forwarding. It ensures efficient utilization of the network resources and enhances user experience by providing dynamic and real-time management of network traffic, right?
So, next up, we have Hypertext Transfer Protocol or HTTP2, right? So, HTTP2 is an updated version of the widely used HTTP protocol. It's a major revision of the original HTTP protocol that was introduced in 1991. It was standardized by the Internet Engineering Task Force or popularly known as the IETF in May 2015 and was designed to improve the performance of web applications by reducing the latency associated with the web page loading. So, it's a fairly new protocol. So, some of the key features of HTTP2 are Binary Protocol, Multiplexing, Server Push, Header Compression, then Improved Security.
In terms of Binary Protocol, unlike the original HTTP protocol that was text-based, HTTP2 is a binary-based which means that it is more efficient in its handling of data. The binary protocols are generally more compact, which leads to reduced data transfer and faster web page loading times. So, remember, if we go back in our previous slides, we have service-based interfaces, right? Service-based architecture where we have SBI interfaces. All those interfaces will be essentially over HTTP2 for exposing different APIs. So, one of the key features that we just discussed is a binary protocol that enables faster web page loading or we can say faster API access.
Then we have Multiplexing. HTTP2 supports Multiplexing, which means that multiple requests can be sent and received over single connection. This is done by dividing the request and responses into smaller frames, which can be interleaved and sent over the same connection. This feature can significantly reduce the number of connections required to load a web page, which in turn reduces the overall latency. So, it supports Multiplexing, that means that multiple HTTP requests can be handled at the same time over a single connection. We don't need multiple connections to handle multiple HTTP requests.
So, we just divide the request into smaller, smaller frames and then intertwine those requests and then we send over those smaller frames over the same connection. That significantly reduces the number of connections because we just have different connections divided into smaller frames and then intertwine them over the same connection. And then obviously what happens is that it reduces the latency and again by latency we mean that faster API access or web page loading. Then we have the server push. With HTTP2, the concept of server push is introduced, which allows servers to push resources to clients before the client has requested them.
That means any kind of like we if we remember we if we know that we there are OTA updates that is sent over there from the server to the client. Right, so HTTP2 introduces that concept of server push. That means all kinds of any kinds of server related messages can be sent directly to the client even if the client has not requested. This can improve the performance of the web applications by reducing the number of round trips required to load a page. Right, as in when required the server can send some request or server can send a web page request or web page response to the client.
We don't, server doesn't need to wait for the client for a web resource to be accessed. Then we have header compression. HTTP2 features improved header compression which reduces the amount of data that needs to be transferred. This results in faster web page loading times. Then we have improved security. Obviously when a new protocol comes in, obviously there has to be some sort of security that needs to be improved. So we can see on the screen that HTTP is developed over TLS earlier is what was on TCP.
Now it is HTTP over TLS that is HTTP2. So it uses the encryption of TLS and thus improves the security of web applications by preventing any sort of eavesdropping and man in the middle sort of attacks, MIM attacks. Well, in conclusion, HTTP2 is a major update to the original HTTP protocol and it provides many features and improves the performance and security of the web applications. Its binary protocol, multiplexing server push, improved header compression and improved security, all together creates a faster and more secure web application or web experience for the users.
Well, HTTP2 is future proof. It is based on Google's SPDY protocol. It is backward compatible. Since again, HTTP is based on SPDY or the SPIDE protocol, it is possible to fall back to using SPDY if needed. Since HTTP uses TLS by default, it has improved security. This means that all communications are encrypted and thus less susceptible to attack which we just discussed. That means any sort of eavesdropping or man in the middle attack is restricted with the introduction of TLS. So again, just discussed that header compression and multiplexing also make it more difficult for attackers to spoof or tamper with the request.
Then we have stream prioritization, which is another feature of HTTP2 that allows the server to prioritize certain types of traffic as transensitive data, sensitive data over others, which can improve the overall performance. Again, HTTP is a request response protocol that we all know. So just to have an overview, HTTP or HTTP2 in general has a target and that target of a request is known as the resource. And resource is something that the server provides that can take many different forms not defined by the HTTP protocol itself.
For instance, in web browsing, a resource might be a webpage, document or a photo, right? As we can see that HTTP server happens to host the resource, an HTTP client will be sending an HTTP request and then it will be sending back with the resource. So when it comes to 3GPP, the 5G core resources can include MMS sessions provided by the service management function, policy sessions offered by the policy configuration function or subscription data provided by the ideal resource management function. Then each type of resource is identified by its own uniform resource identifier or the URL, with a common form being uniform resource locator or the URL, which not only identifies the resource, but also provides information on accessing it through the protocols like HTTP.
So URI is how our SMFs or any kind of network elements in the service-based architecture will use the URI to access certain resources from other network elements, which will be hosting those APIs. So that's it with respect to HTTP. So it has a lot of advantages like improved security, multiplexing, then obviously it has a lot of advantages. This URL that was common with HTTP, but then again adding on all those layers of TLS over HTTP has improved the security which is really required when it comes to telecommunications.