## 6 Mobile Networks
### 5 GS Capabilities  
The generic 5 GS architectural framework introduced by 3 GPP [117] envisions multiple functionalities and mechanisms that enable not only the provision of communication satisfying the diverse and specific QoS requirements but also provide added value. The primary network features that can bring benefits to the vertical industries are described below. **Performance and QoS control**: The main peak 5 GS performance indicators include data rates of up to 20 Gbps, latency reaching 1 ms, up to a million devices per km\({}^{2}\), and very high reliability and support for objects moving at speeds of up to 500 km/h. The specific QoS targets can be enforced on the UP level by assigning the user data traffic a relevant 5G QoSIdentifier (5 QI)--the identifier associated with a set of QoS parameters (communication type, priority level, delay, errors, etc.) [117]. So far, 32 different standardized categories have been specified by 3 GPP, but the list can be dynamically extended by an MNO for private use if needed. **Programmingability**: The 5 GS architecture design incorporates softwarization, virtualization, Software-Defined Networking (SDN), and other cloud-native approaches as the basis for operation. This facilitates the programmability of both the Control Plane (CP) and UP. The CP functionalities can be extended by any Network Function (NF), e.g., generic Application Functions (AFs), as long as compatibility with the Service-Based Architecture (SBA) is provided, i.e., communication with other CP NFs using RESTful Application Programming Interfaces (APIs), JSON serialization, usage of HTTP/2 in the application layer, and TCP for transport. The UP operation can be enhanced by chaining atomic functions that improve UP traffic handling with regard to use-case specificity or service requirements. Example extensions involve deep packet inspection, firewalls, selective marking or altering, packet classification and encapsulation, anti-virus protection, parental control, traffic forwarding or redirection, etc. **Network Slicing**: Network Slicing (NS) is a concept that allows the creation of a \"federation\" of virtual parallel networks over a shared infrastructure, with each network tailored to the requirements of the specific supported services (joint usage of certain mechanisms, e.g., mobility or user capability subscription management). At present, there exist five network slice types defined by 3 GPP [117], with future extensions possible, namely eMBB, URLLC, Massive Internet of Things (MIoT), Vehicle to Everything (V2X) (since Release 16), and High-Performance Machine-Type Communications (HMTC) (since Release 17). The adaptation to the requirements can involve the integration of slice-specific CP functions with 5 GS CP (using SBA CP communication bus-separation mechanisms) and slice-specific user traffic processing chains (individualized traffic operations, e.g., flow duplication for URLLC to improve reliability). The necessary support for slice selection and admission control has to be provided on the network side, as well as the UE side, to enable the on-demand attachment to one or multiple slices. **Integration of third parties with 5 GS Core Network (CN)**: The 5 GS CP incorporates multiple mechanisms that facilitate the network capabilities' exposure, integration with external entities, and reuse of already deployed functionalities among multiple stakeholders. Firstly, the 3 GPP functions implement a unified northbound interface API framework, i.e., Common Application Programming Interface Framework (CAPIF) [118]. The adopted framework enables the secure exposure of the 5 GS CNs' APIs to external consumers and standardizes the exposure of the third parties' APIs to the 5 GS CN. The Service Enabler Architecture Layer for Verticals (SEAL) framework provides the means for sharing already developed core functions and mechanisms among the industries implementing the parallel use cases.