NPN (Non-Public Network), commonly referred to as a private network, represents a dedicated cellular network deployed and operated for the exclusive use of a specific organization or site. The fundamental concept and motivation behind 5G private networks are rooted in the same principles that drove the development of  LTE private network—namely, the desire for greater control, enhanced security, and tailored performance that cannot always be guaranteed by public mobile networks. For a more foundational understanding, it’s useful to also review the concepts surrounding LTE private networks, as they laid the groundwork for many of today’s private cellular deployments.

However, while the overarching goals remain similar, the leap from LTE to 5G introduces a host of technological advancements that significantly amplify the potential and demand for private network solutions. 5G brings with it ultra-low latency, significantly higher bandwidth, improved device density handling, and enhanced support for mission-critical applications. These capabilities open the door to entirely new use cases—ranging from real-time industrial automation and autonomous robotics to immersive telemedicine and next-generation smart grids—that would be difficult or impossible to achieve with LTE alone. As a result, the business case for private 5G is not only stronger but also more diverse and compelling. Many industries now view private 5G not simply as an upgrade from LTE, but as a transformational technology essential for enabling Industry 4.0 and beyond.

• What does 'Private' mean ?
• What does 'Unlicensed Spectrum' mean ?
• How to deploy it ?
• Why we would need NPN/Private Network ?
• Why Private Network is getting popularity recently ?
• What are the most common Use Cases ?
• 5G vs. Wi-Fi in Private Networks: Comparison of Capabilities
• RRC Parameters
• Get the Test Procedure and Log / Amarisoft TechAcademy

What does 'Private' mean ?

First of all, let's think of what it mean by 'Private' mean ? Actually 'Private' is not 3GPP term. In 3GPP, we call it as 'Non Public'. The term 'Private' in this context would not be a legal term since I think most of cellular network, even the major carriers that we all know' are 'Non public' company legally. The term 'Private' in this context refers to 'Unlicensed', especially 'Unlicensed Spectrum'.

NOTE : As the concept of Private Network evolves, I think the association between 'Private' and 'Unlicensed' gets weaker and we see some use cases of implementing Private Network using Network Slicing technology which is provided by Network Operators using licensed spectrum.

What does 'Unlicensed Spectrum' mean ?

Radio Frequency Spectrum is very rare resources and is strictly controlled by government regulation in most cases. We would need to aquire specific licenese for most of those radio spectrum and it would cost a lot. But there are some range of radio spectrum that is allowed for public use without any specific licenses. Some of the common examples of 'Unlicensed Spectrum' are as follows.

• ISM (Industrial, Science, Medical) band : There are many segments belong to this band (see wikipedia). Most common ISM band is 433 Mhz (used frequently for various remote control, remote sensing etc), 2.4 Ghz/5.6 Ghz used mostly for Bluetooth, Wireless LAN.
• CBRS (Citizens Broadband Radio Service ) : It is a block of spectrum in 3.5 Ghz with the range of 150 Mhz (3.5 (3550 MHz to 3700 MHz) for shared wireless access (See CBRS page).   

The main target for 5G Private Network spectrum is likely to be ISM (mainly for 5.6 Ghz) and CBRS at least at early phase of deployment. In LTE, it was difficult to use the unlicensed spectrum with higher frequency (e.g, higher than 5 Ghz) since most of LTE frequency specified in 3GPP is below 3 Ghz. However, NR frequency spectrum already defined in 3GPP is very widely spreaded from relatively low frequency like below 2Ghz, mid range frequency between 3Ghz and 7Ghz and very high frequency like mmWave. It would be relatively easy to develope the device for the unlicensed spectrum wherever they are located.

How to deploy it ?

There are many different options to deploy (implement) 5G NPN. Some of the common options can be illustrated as below.

Simply speaking, there are two large categories of NPN deployment labled as Standalone NPN(SNPN) and Public Network Integrated NPN(PNI-NPN). There are a few sub categories within the PNI-NPN as illustrated below. There can be even more sub categories depending on the detailed mechanism of interfaction between Public network and Private network, but the categories shown below would be the most common high level classification you may see from almost every documents on NPN.

Following table shows the summaries of these deployment mode in a table.

Followings are descriptions on each of these deployment mode :

A. SNPN (Standalone Non-Public Network)

An SNPN operates completely independently from any public network. It has its own Radio Access Network (RAN) and Core Network (CN), with no integration or dependency on a public network.

• The SNPN has a dedicated RAN (either public or private spectrum) and a private core network.
• The control plane (CP) and user plane (UP) are fully isolated from any public network.
• Services can be hosted either on a public cloud (e.g., AWS, Azure) or a private cloud (on-premises).
• Use Case: Ideal for highly sensitive environments (e.g., military bases, critical infrastructure) where full isolation is required.

Signaling Protocols:

• RAN to UE (User Equipment): The UE connects to the RAN using 5G New Radio (NR) protocols, specifically the RRC (Radio Resource Control) protocol for connection setup, bearer establishment, and mobility management.
• RAN to Core (NG Interface): The RAN (gNodeB) communicates with the core network using the NGAP (NG Application Protocol) over the NG interface. This handles signaling for session management, UE registration, and mobility.
• Core Network (Control Plane): Within the core, the AMF (Access and Mobility Management Function) uses NAS (Non-Access Stratum) signaling to communicate with the UE for authentication, registration, and session setup.
• Authentication: The SNPN uses its own UDM (Unified Data Management) for subscriber data and authentication, typically via EAP (Extensible Authentication Protocol) or 5G-AKA (Authentication and Key Agreement).
• User Plane: The user plane traffic flows through the UPF (User Plane Function) using GTP-U (GPRS Tunneling Protocol - User Plane) for data encapsulation.

B. PNI-NPN: Shared RAN

The RAN is shared between public and private users, but the core network is split (public CN for public users, private CN for NPN users).

• The RAN is shared between public and private users, meaning the same base station (gNodeB) serves both.
• The core network is split: a public core network serves public users, while a private core network serves NPN users.
• Services can be public or private, depending on the use case.
• Use Case: Suitable for enterprises that want to leverage existing public RAN infrastructure (e.g., a mobile operator’s towers) but need a private core for data isolation.

Signaling Protocols:

• RAN to UE: Same as SNPN, using 5G NR and RRC for connection setup.
• RAN Slicing: The shared RAN uses network slicing to differentiate between public and private users. This is achieved through the NSSAI (Network Slice Selection Assistance Information) included in the RRC signaling, which identifies the slice (public or private) for the UE.
• RAN to Core: The gNodeB routes signaling to the appropriate core network (public or private) using NGAP. The gNodeB selects the AMF based on the NSSAI.
• Core Network (Control Plane): The private core’s AMF handles NAS signaling for NPN users, while the public core’s AMF serves public users.
• Authentication: The private core has its own UDM for NPN users, while public users authenticate via the public core’s UDM.
• User Plane: The private UPF handles NPN user data, while the public UPF serves public users, both using GTP-U.

C. PNI-NPN: Shared RAN and Shared CN Control Plane

The RAN and the control plane of the core network are shared, but the user plane is separate for public and private users.

• The RAN and the control plane (e.g., AMF) are shared between public and private users.
• The user plane is separated: a private UPF for NPN users and a public UPF for public users.
• Services can be public or private.
• Use Case: Useful for scenarios where control plane isolation is less critical, but user data isolation is still required (e.g., smart factories sharing a mobile operator’s control plane).

Signaling Protocols:

• RAN to UE: Same as above, using RRC and NSSAI for slice selection.
• RAN to Core: The gNodeB communicates with a shared AMF using NGAP. The AMF identifies whether the UE belongs to the public or private network based on the NSSAI or subscription data.
• Core Network (Control Plane): The shared AMF handles NAS signaling for both public and private users. It communicates with a shared SMF (Session Management Function) to set up sessions.
• Authentication: The AMF may use a shared UDM or route authentication requests to a private UDM for NPN users.
• User Plane: The SMF assigns a private UPF for NPN users and a public UPF for public users. Data traffic is encapsulated using GTP-U.

D. PNI-NPN: Shared RAN and Shared CN CP & UP

The RAN, control plane, and user plane are all shared, with logical separation for private services.

• The RAN, control plane, and user plane are all shared.
• Logical separation is achieved through network slicing, ensuring NPN traffic is isolated within the shared infrastructure.
• Services can still be public or private.
• Use Case: Best for cost-efficient deployments where full isolation is not critical, but some level of privacy is still needed (e.g., a retail chain using a mobile operator’s infrastructure).

Signaling Protocols:

• RAN to UE: RRC with NSSAI for slice selection.
• RAN to Core: NGAP to the shared AMF.
• Core Network (Control Plane): The shared AMF and SMF handle NAS signaling and session management for both public and private users.
• Authentication: Likely uses a shared UDM, but NPN users may have specific subscription profiles.
• User Plane: The shared UPF handles both public and private traffic, with isolation enforced through network slicing (e.g., using different APNs or DNNs—Data Network Names—for public and private traffic). GTP-U is used for data encapsulation.

Why We would need NPN/Private Network ?

The core motivation for deploying a Non-Public Network (NPN), also known as a private network, aligns closely with the rationale behind LTE private networks. Both aim to provide organizations with dedicated, secure, and high-performance wireless connectivity that is tailored to their specific operational needs—something that shared public networks often struggle to deliver consistently. If you're familiar with the motivations for LTE private networks, such as enhanced control, deterministic quality of service (QoS), and enterprise-level security, then you're already partway to understanding the case for 5G private networks. I recommend revisiting the note on LTE private network motivation as a useful foundation.

That said, I believe the justification for 5G-based NPNs is not just a repetition of LTE’s benefits—it’s an evolution, and in many cases, a necessity. The capabilities that 5G introduces fundamentally expand what a private network can do. Features like ultra-low latency, high throughput, support for massive numbers of connected devices, and network slicing aren’t just technical upgrades—they’re enablers of entirely new kinds of use cases. These include real-time control of industrial robotics, remote surgery using AR/VR interfaces, intelligent transportation systems, and mission-critical applications in energy, defense, and healthcare sectors.

In my view, the real motivation behind 5G NPNs comes down to control and assurance at scale. As enterprises digitalize their operations and begin to rely on automation, AI-driven systems, and distributed edge computing, they can no longer afford to rely on “best effort” connectivity. Public networks, no matter how fast or modern, are not built for the nuanced performance guarantees required by a smart factory floor or a life-critical hospital system. Enterprises are seeking independence—not just from network congestion, but from the variability and unpredictability of public infrastructure.

Moreover, 5G offers private network operators fine-grained control over traffic prioritization, access control, and service-level agreements (SLAs), allowing them to design networks that are tightly aligned with business processes and safety requirements. For example, with private 5G, an automotive manufacturer can assign a specific QoS class to the wireless control of a robotic arm—something that's nearly impossible over Wi-Fi or public mobile networks.

So while the high-level motivation may echo LTE—control, security, customization—the depth of why we need private 5G today is more urgent and more strategic. It's not just about having a faster pipe; it's about enabling a new generation of applications that depend on trust, reliability, and fine-tuned wireless performance. In this context, 5G NPNs are not just an option—they are increasingly becoming a prerequisite for digital transformation.

Here’s a list of summary on the motivation of 5G Private Network:

• Shared motivation with LTE private networks
• Both aim to provide dedicated, secure, and controlled wireless connectivity.
• Motivated by the need for reliable performance not guaranteed by public networks.
• LTE private network motivations (e.g. QoS, security, customization) still apply.
• Enhanced justification with 5G capabilities
• 5G introduces ultra-low latency, high throughput, massive device connectivity, and network slicing.
• Enables use cases not feasible with LTE: e.g., real-time robotics, remote surgery, smart infrastructure.
• Enterprise need for control and assurance
• As operations become more digital and automated, reliance on public networks becomes risky.
• Enterprises require guaranteed service levels and deterministic network behavior.
• Customization and fine-grained control
• 5G allows prioritization of traffic, secure segmentation, and alignment with business-critical processes.
• Example: assigning specific QoS profiles to robotic arms or telemetry systems.
• 5G NPNs as a strategic enabler
• Not just a faster network—it's infrastructure for digital transformation.
• Increasingly seen as a prerequisite rather than a luxury in industrial, healthcare, and critical sectors.

Why Private Network is getting popularity recently ?

Recently (esepcially since 2024 and onwards), 5G private networks transitioned from emerging technology to essential enterprise infrastructure. This surge was driven by policy shifts enabling direct enterprise deployment, technological maturity delivering on latency and reliability promises, and the growing demand for high-performance wireless to power Industry 4.0. Adoption is accelerating globally, with strong investment momentum and a shift from pilot to production-scale implementations.

Followings are the list of factors contributing the recent popularity of private network.

• Spectrum liberalization and regulatory support
• U.S. CBRS (3.5 GHz) and similar policies worldwide allowed enterprises to access licensed/shared spectrum.
• Enabled deployment of private 5G networks without depending on mobile operators.
• Maturity of 5G Standalone technology
• Low latency and high reliability now achievable. (NOTE : I don't think URLLC is mature and widely adopted enough as of now, but the technology has been optimized and matured enough to provide enough low latency and reliability)
• Industrial applications began shifting from LTE-based to full 5G SA systems.
• Rapid market growth and adoption
• Private 5G market valued at ~$2.1B in 2023; projected CAGR over 40%.
• Analysts predict global private 5G spending to grow ~65% annually through 2030.
• Enterprise digitalization needs driving demand
• Use cases: smart factories, telemedicine, logistics tracking, smart grids.
• Demand for wireless with better performance than Wi-Fi or public networks.
• Deployment scale by 2024
• Over 7,300 private LTE/5G deployments across 130+ countries.
• LTE still dominant, but 5G adoption accelerating fast.
• U.S. market trends
• Annual private LTE/5G infrastructure spend growing ~18%.
• Expected to exceed $3.7B by 2027.
• Core drivers of popularity
• Tech readiness (5G SA), pro-enterprise policy, and Industry 4.0 requirements.
• 5G is now seen as mission-critical wireless infrastructure, not just innovation.

What are the most common Use Cases ?

The widespread adoption of 5G private networks is no longer theoretical—real deployments are happening across key industries. Recently (especially since 2024 and onwards), enterprises in manufacturing, healthcare, logistics, and beyond have moved from pilots to production, leveraging 5G’s speed, low latency, and reliability to enable new capabilities. These aren’t generic experiments—they’re targeted, high-impact use cases driving real operational gains and reshaping how organizations operate at scale.

• Manufacturing & Industrial Automation
• Manufacturing leads with ~20% share of the private 5G market (as of 2023).
• Major deployments: BMW (Spartanburg), GM (Factory ZERO), Toyota, Tesla.
• Use cases: wireless PLCs, autonomous guided vehicles (AGVs), HD camera-based quality control, AR-assisted assembly.
• 5G enables fast reconfiguration of production lines and predictive maintenance (e.g. via digital twins).
• Hundreds of factories have adopted private 5G; 76% of manufacturers planned deployment by 2024.
• Healthcare
• Hospitals require ultra-reliable wireless for critical systems.
• Deployed in: Boston Children’s Hospital, Cleveland Clinic’s Mentor Hospital, U.S. VA healthcare facilities.
• Use cases: wireless monitoring, telepresence consultations, AR/VR surgical training, smart beds, connected imaging equipment.
• Positioned for future use: robotic remote surgery, smart ambulances.
• Estimated to contribute $530B to global GDP by 2030 via enhanced efficiency and services.
• Logistics, Transportation & Warehousing
• 5G offers large-area coverage, high device density, and mobility—key for logistics.
• Deployed by: Walmart (distribution centers), DFW Airport, Port of Virginia.
• Use cases: real-time inventory tracking, automated forklifts, crane remote control, baggage handling.
• Enhances operational efficiency and safety; allows for real-time asset tracking and automation across vast facilities.
• Other Sectors (Energy, Mining, Education, Entertainment)
• Energy/Mining:
• Deployed underground in China, Australia for automation and safety (e.g. Shanxi Coking Coal Group).
• Smart grids with connected substations, sensors, and maintenance crews.
• Education:
• Private 5G trials at Arizona State, Cal Poly for smart campus and research applications (e.g. autonomous vehicles).
• Entertainment:
• Stadiums implementing 5G for AR/VR experiences and traffic offload during live events.
• Cross-Industry Impact
• Private 5G is delivering tailored benefits in each vertical—from factory automation to telehealth and port operations.
• Common thread: need for secure, high-performance wireless in dynamic or mission-critical environments.

5G vs. Wi‑Fi in Private Networks: Comparison of Capabilities

As enterprises consider upgrading their wireless networks, a common question is how 5G private networks compare to Wi‑Fi-based networks (including the latest Wi‑Fi 6, 6E, and emerging Wi‑Fi 7 standards). Both technologies can deliver high-speed wireless connectivity, but they differ in performance characteristics, deployment model, scalability, cost, and security. In many cases 5G and Wi‑Fi are complementary rather than strictly competing – organizations may use both to meet different requirements​

RRC Parameters

SIB1 ::=        SEQUENCE {

    cellSelectionInfo                   SEQUENCE {

        q-RxLevMin                          Q-RxLevMin,

        q-RxLevMinOffset                    INTEGER (1..8)      OPTIONAL,   -- Need R

        q-RxLevMinSUL                       Q-RxLevMin          OPTIONAL,   -- Need R

        q-QualMin                           Q-QualMin           OPTIONAL,   -- Need R

        q-QualMinOffset                     INTEGER (1..8)      OPTIONAL    -- Need R

    }    OPTIONAL,   -- Need S

    cellAccessRelatedInfo               CellAccessRelatedInfo,

    connEstFailureControl               ConnEstFailureControl   OPTIONAL,   -- Need R

    si-SchedulingInfo                   SI-SchedulingInfo       OPTIONAL,   -- Need R

    servingCellConfigCommon             ServingCellConfigCommonSIB    OPTIONAL,   -- Need R

    ims-EmergencySupport                ENUMERATED {true}             OPTIONAL,   -- Need R

    eCallOverIMS-Support                ENUMERATED {true}             OPTIONAL,   -- Cond Absent

    ue-TimersAndConstants               UE-TimersAndConstants         OPTIONAL,   -- Need R

    uac-BarringInfo                     SEQUENCE {

        uac-BarringForCommon                UAC-BarringPerCatList     OPTIONAL,   -- Need S

        uac-BarringPerPLMN-List             UAC-BarringPerPLMN-List   OPTIONAL,   -- Need S

        uac-BarringInfoSetList              UAC-BarringInfoSetList,

        uac-AccessCategory1-SelectionAssistanceInfo CHOICE {

            plmnCommon                      UAC-AccessCategory1-SelectionAssistanceInfo,

            individualPLMNList              SEQUENCE (SIZE (2..maxPLMN))

                                               OF UAC-AccessCategory1-SelectionAssistanceInfo

        }   OPTIONAL

    }     OPTIONAL,   -- Need R

    useFullResumeID                     ENUMERATED {true}    OPTIONAL,   -- Need N

    lateNonCriticalExtension            OCTET STRING         OPTIONAL,

    nonCriticalExtension                SIB1-v1610-IEs       OPTIONAL

}

CellAccessRelatedInfo ::= SEQUENCE {

   plmn-IdentityInfoList            PLMN-IdentityInfoList,

   cellReservedForOtherUse          ENUMERATED {true} OPTIONAL, -- Need R

   ...,

   [[

   cellReservedForFutureUse-r16     ENUMERATED {true} OPTIONAL, -- Need R

   npn-IdentityInfoList-r16         NPN-IdentityInfoList-r16 OPTIONAL -- Need R

   ]],

   [[

   snpn-AccessInfoList-r17  SEQUENCE (SIZE (1..maxNPN-r16)) OF SNPN-AccessInfo-r17 OPTIONAL--Need R

   ]]

}

NPN-IdentityInfoList-r16 ::= SEQUENCE (SIZE (1..maxNPN-r16)) OF NPN-IdentityInfo-r16

NPN-IdentityInfo-r16 ::= SEQUENCE {

   npn-IdentityList-r16                 SEQUENCE (SIZE (1..maxNPN-r16)) OF NPN-Identity-r16,

   trackingAreaCode-r16                 TrackingAreaCode,

   ranac-r16                            RAN-AreaCode OPTIONAL, -- Need R

   cellIdentity-r16                     CellIdentity,

   cellReservedForOperatorUse-r16       ENUMERATED {reserved, notReserved},

   iab-Support-r16                      ENUMERATED {true} OPTIONAL, -- Need S

   ...,

   [[

   gNB-ID-Length-r17                    INTEGER (22..32) OPTIONAL -- Need R

   ]]

}

NPN-Identity-r16 ::= CHOICE {

   pni-npn-r16 SEQUENCE {

      plmn-Identity-r16                 PLMN-Identity,

      cag-IdentityList-r16              SEQUENCE (SIZE (1..maxNPN-r16)) OF CAG-IdentityInfo-r16

   },

   snpn-r16 SEQUENCE {

      plmn-Identity-r16                 PLMN-Identity,

      nid-List-r16                      SEQUENCE (SIZE (1..maxNPN-r16)) OF NID-r16

   }

}

CAG-IdentityInfo-r16 ::= SEQUENCE {

   cag-Identity-r16                    BIT STRING (SIZE (32)),

   manualCAGselectionAllowed-r16       ENUMERATED {true} OPTIONAL -- Need R

}

NID-r16 ::= BIT STRING (SIZE (44))

SNPN-AccessInfo-r17 ::= SEQUENCE {

   extCH-Supported-r17 ENUMERATED {true} OPTIONAL, -- Need R

   extCH-WithoutConfigAllowed-r17 ENUMERATED {true} OPTIONAL, -- Need R

   onboardingEnabled-r17 ENUMERATED {true} OPTIONAL, -- Need R

   imsEmergencySupportForSNPN-r17 ENUMERATED {true} OPTIONAL -- Need R

}

SIB1-v1700-IEs ::= SEQUENCE {

   hsdn-Cell-r17                      ENUMERATED {true} OPTIONAL, -- Need R

   uac-BarringInfo-v1700 SEQUENCE {

      uac-BarringInfoSetList-v1700    UAC-BarringInfoSetList-v1700

   } OPTIONAL, -- Cond MINT

   sdt-ConfigCommon-r17               SDT-ConfigCommonSIB-r17 OPTIONAL, -- Need R

   redCap-ConfigCommon-r17            RedCap-ConfigCommonSIB-r17 OPTIONAL, -- Need R

   featurePriorities-r17 SEQUENCE {

      redCapPriority-r17              FeaturePriority-r17 OPTIONAL, -- Need R

      slicingPriority-r17             FeaturePriority-r17 OPTIONAL, -- Need R

      msg3-Repetitions-Priority-r17   FeaturePriority-r17 OPTIONAL, -- Need R

      sdt-Priority-r17                FeaturePriority-r17 OPTIONAL -- Need R

   } OPTIONAL, -- Need R

   si-SchedulingInfo-v1700            SI-SchedulingInfo-v1700 OPTIONAL, -- Need R

   hyperSFN-r17                       BIT STRING (SIZE (10)) OPTIONAL, -- Need R

   eDRX-AllowedIdle-r17               ENUMERATED {true} OPTIONAL, -- Need R

   eDRX-AllowedInactive-r17           ENUMERATED {true} OPTIONAL, -- Cond EDRX-RC

   intraFreqReselectionRedCap-r17     ENUMERATED {allowed, notAllowed} OPTIONAL, -- Need S

   cellBarredNTN-r17                  ENUMERATED {barred, notBarred} OPTIONAL, -- Need S

   nonCriticalExtension SEQUENCE {} OPTIONAL

}

UAC-AccessCategory1-SelectionAssistanceInfo ::= ENUMERATED {a, b, c}

UAC-AC1-SelectAssistInfo-r16 ::= ENUMERATED {a, b, c, notConfigured}

SDT-ConfigCommonSIB-r17 ::= SEQUENCE {

   sdt-RSRP-Threshold-r17        RSRP-Range OPTIONAL, -- Need R

   sdt-LogicalChannelSR-DelayTimer-r17        ENUMERATED { sf20, sf40, sf64, sf128, sf512, sf1024,

                                                           sf2560, spare1} OPTIONAL, -- Need R

   sdt-DataVolumeThreshold-r17                ENUMERATED {byte32, byte100, byte200, byte400,

                                                          byte600, byte800, byte1000, byte2000,

                                                          byte4000, byte8000, byte9000, byte10000,

                                                          byte12000, byte24000, byte48000,

                                                          byte96000},

   t319a-r17            ENUMERATED { ms100, ms200, ms300, ms400, ms600, ms1000, ms2000,

                                     ms3000, ms4000, spare7, spare6, spare5, spare4, spare3,

                                     spare2, spare1}

}

RedCap-ConfigCommonSIB-r17 ::= SEQUENCE {

   halfDuplexRedCapAllowed-r17         ENUMERATED {true} OPTIONAL, -- Need R

   cellBarredRedCap-r17      SEQUENCE {

      cellBarredRedCap1Rx-r17          ENUMERATED {barred, notBarred},

      cellBarredRedCap2Rx-r17          ENUMERATED {barred, notBarred}

   } OPTIONAL, -- Need R

   ...

}

FeaturePriority-r17 ::= INTEGER (0..7)

npn-IdentityInfoList :

The npn-IdentityInfoList is used to configure a set of NPN-IdentityInfo elements. Each of those elements contains a list of one or more NPN Identities and additional information associated with those NPNs. The total number of PLMNs (identified by a PLMN identity in plmn -IdentityList), PNI-NPNs (identified by a PLMN identity and a CAG-ID), and SNPNs (identified by a PLMN identity and a NID) together in the PLMN-IdentityInfoList and NPN-IdentityInfoList does not exceed 12, except for the NPN-only cells. A PNI-NPN and SNPN can be included only once, and in only one entry of the NPN-IdentityInfoList. In case of NPN-only cells the PLMN-IdentityList contains a single element that does not count to the limit of 12. The NPN index is defined as B+c1+c2+…+c(n-1)+d1+d2+…+d(m-1)+e(i) for the NPN identity included in the n-th entry of NPN-IdentityInfoList and in the m-th entry of npn-Identitylist within that NPN-IdentityInfoList entry, and the i-th entry of its corresponding NPN-Identity, where

- B is the index used for the last PLMN in the PLMN-IdentittyInfoList; in NPN-only cells B is considered 0;

- c(j) is the number of NPN index values used in the j-th NPN-IdentityInfoList entry;

- d(k) is the number of NPN index values used in the k-th npn-IdentityList entry within the n-th NPN-IdentityInfoList entry;

- e(i) is

- i if the n-th entry of NPN-IdentityInfoList entry is for SNPN(s);

- 1 if the n-th entry of NPN-IdentityInfoList entry is for PNI-NPN(s).

plmn-IdentityInfoList

The plmn-IdentityInfoList is used to configure a set of PLMN-IdentityInfo elements. Each of those elements contains a list of one or more PLMN Identities and additional information associated with those PLMNs. A PLMN-identity can be included only once, and in only one entry of the PLMN-IdentityInfoList. The PLMN index is defined as b1+b2+…+b(n-1)+i for the PLMN included at the n-th entry of PLMN-IdentityInfoList and the i-th entry of its corresponding PLMN-IdentityInfo, where b(j) is the number of PLMN-Identity entries in each PLMN-IdentityInfo, respectively.

snpn-AccessInfoList

This list provides access related information for each SNPN in npn-IdentityInfoList, see TS 23.501 [32]. The n-th entry of the list contains the access related information of the n-th SNPN in npn-IdentityInfoList.

SIB10-r16 ::= SEQUENCE {

    hrnn-List-r16                   HRNN-List-r16 OPTIONAL, -- Need R

    lateNonCriticalExtension        OCTET STRING OPTIONAL,

    ...

}

HRNN-List-r16 ::= SEQUENCE (SIZE (1..maxNPN-r16)) OF HRNN-r16

HRNN-r16 ::= SEQUENCE {

    hrnn-r16                        OCTET STRING (SIZE(1.. maxHRNN-Len-r16)) OPTIONAL -- Need R

}

YouTube

• World's first private #5G​ pop-up network with Telia Finland and Nokia (Jun 2019)
• Build Your Own Private 5G Network on Kubernetes - Frank Zdarsky (Nov 2019)
• Advanced: Private Networks & 5G Non-Public Networks (Feb 2020)
• Private 5G Network in Test Center from Siemens (Mar 2020)
• Transforming Private 5G Networks  (Apr 2020)
• Private 5G Networks - Mpirical (Oct 2020)
• IoT WebTalk: 5G Private & Dedicated Networks for Industry 4.0 (GSMA, Oct 2020)
• Enterprise 5G Webinar Series Cellular Interconnect on CBRS and Private Networks (Oct 2020)
• Industrial 5G: Remaining challenges and future perspectives (Nov 2020)
• Radisys Webinar: Private 5G Network Deployment Use Cases (Jan 2021)
• The First 5G Private Network in Taiwan (Jan 2021)
• 5G Course - 5G Private Networks / Industrial Networks / Enterprise networks (Feb 2021)
• 5G Private Networks & Port Efficiency (Mar 2021)
• Baicells Webinar - 2021 CBRS Products Leading up to 5G(Mar 2021)
• Private 5G networks will serve as a foundation for Industry 4.0 (May 2021)
• Qualcomm 5G Summit: 5G Private Network masterclass (May 2022)
• Private 5G for HOBAN Construction (May 2023)

References

• Private 5G Mobile Networks for Industrial IoT (Qualcomm)
• Transforming enterprise and industry with 5G private networks (Qualcomm)
• 5G for Industry 4.0 (3GPP)
• What is NPN in 5G? (telecomHall Forum)
• Private 5G networks are an example of NPNs (RCR Wireless)
• 5G Non-Public Network (LinkedIn Post)
• 5G Technologies in Private Networks (5G America Whitepaper)
• Benefits of 5G and Wi-Fi: superior indoor connectivity - Ericsson
• Private 5G Network Market - By Component (Hardware, Software, Services), By Spectrum (Licensed Spectrum, Unlicensed Spectrum), By Industry Vertical (Manufacturing, Healthcare, Transportation & Logistics, Energy & Utilities, Retail, Oil & Gas), & Forecast 2024 - 2032 - GMI (Dec 2023)
• Private-Mobile-Networks Summary February 2024 - GSA(Feb 2024)
• The Power Pair: How Private 5G and Wi-Fi Conquer Connectivity White Paper - Cisco (May 2024)
• U.S. Private LTE and 5G Network Market Analysis: Adoption Across Industries and $3.7 Billion Growth Potential - Businesswire (Jan 2025)