like designing a public network, the first and foremost consideration while designing a private network is to determine the use case to be applied. In most cases, the non-public network is for an enterprise or campus. In either case, certain simplifications in design can be applied. For example, in an enterprise network, there is hardly the need to charge subscribers, and roaming is seldom required. Hence, the minimum number of network functions needed to design such a network is very small. The most essential network functions needed are as follows: 5G NR for radio access AMF for access and mobility management SMF for session management UDM and UDR for subscription management UPF for the data plane PCF for the policy (optional - good to have) 5G Standalone Networks In some cases, an unlicensed CBRS spectrum can be used; this is a more popular approach in the USA. If an unlicensed spectrum is used, then the allotment of the same is done by a Spectrum Access System (SAS) provider. Several deployment options can be adopted by the enterprise. Firstly, the enterprise can choose to deploy its private network on its own. In this case, the enterprise adopts the end-to-end responsibility of deploying and maintaining a network. There is another common alternative that enterprises go for, which is to have a mobile network operator provide the enterprise network. This way, the responsibility of maintaining the network is largely on the network operator. Next, let us go over the various types of private network options: Enterprise Premises Service Public Cloud Description Provider Premises Radio, license Wholly private network. management, Deployed, operated, and control and user maintained entirely by plane functions, the enterprise. analytics, orchestration, and Complete data maintenance software ownership by the enterprise. Radio, license Analytics, Analytics, orchestration, management, and orchestration, and and maintenance control and user maintenance software is maintained plane functions software in the public cloud w