name: SIB18
full_form: System Information Block Type 18
context: The NG-RAN node is aware of the SNPN ID(s) supported by neighbour cells. At the time of handover, cells that do not support the serving SNPN ID or the SNPN ID of an equivalent SNPN within the mobility restrictions received in the UE context are not considered as candidate target cells by the source NG-RAN node. The target NG-RAN node performs access control. In case it cannot accept the handover for the serving SNPN the target NG-RAN node fails the handover including an appropriate cause value. 16.6.3 Self-Configuration for SNPN Self-configuration is described in clause 15. In addition, on NG, the NG-RAN node signals the SNPN ID(s) supported per tracking area and the AMF signals the SNPN ID(s) supported per node; on Xn, NG-RAN nodes exchange SNPN ID(s) supported per cell. 16.6.4 Access Control During the establishment of the UE-associated logical NG-connection towards the 5GC, the AMF checks whether the UE is allowed to access the cell for the signalled SNPN ID as specified in TS 23.501[ System architecture for the 5G System (5GS) ]  [3]. If the check is successful, the AMF sets up the UE-associated logical NG-connection and provides the NG-RAN node with the mobility restrictions applicable for the SNPN. If the check is not successful, the AMF shall reject setting up the UE-associated NG connection and inform the NG-RAN node with an appropriate cause value as specified in TS 23.501[ System architecture for the 5G System (5GS) ]  [3]. 16.6.5 Access with subscription/credentials owned by a Credentials Holder An SNPN may allow access to UEs being authorized using credentials or subscription owned by a separate Credentials Holder (CH). The support of this feature is uniform across the SNPN as specified in TS 23.501[ System architecture for the 5G System (5GS) ]  [3]. The following information is broadcast to support SNPN access with subscription of a Credentials Holder: - an indication per SNPN in SIB1 that access using credentials from a Credentials Holder is supported; - optionally a list of supported GINs in SIB18 (each GIN may be assigned to one or more SNPNs); - an optional indication per SNPN in SIB1 that the SNPN allows registration attempts from UEs that are not explicitly configured to select the SNPN. The above listed items are forwarded to the UE NAS layer that uses them for SNPN selection. 16.6.6 Support of UE onboarding and remote provisioning An SNPN may offer support for restricted 3GPP connectivity for remote provisioning of credentials. The feature is enabled/disabled per cell. The following information is broadcast to support UE onboarding and remote provisioning: - an indication per onboarding SNPN in SIB1 that UE onboarding is enabled; - optionally a list of supported GINs in SIB18 (each GIN may be assigned to one or more onboarding SNPNs). The above listed items are forwarded to the UE NAS layer that uses them for onboarding SNPN selection. When a UE intends to perform onboarding, it sends the onboarding request indication to the gNB during RRC connection establishment. The NG-RAN nodes receive information about onboarding support capabilities of the AMF(s). This information is used by the NG-RAN node to select a suitable AMF when receiving the onboarding request indication from the UE.
description: System Information Block Type 18 (SIB18) is a type of system information block that contains specific information about the supported Global Identifier Numbers (GINs) for Single Network Slice Provisioning (SNPN). This information is broadcast by the Next Generation Radio Access Network (NG-RAN) node to support SNPN access with subscription or credentials owned by a Credentials Holder, as well as UE onboarding and remote provisioning. The SIB18 message includes an optional list of supported GINs, which may be assigned to one or more SNPNs.
explanation: SIB18 is classified as a Message because it refers to a specific type of system information block that contains particular details about the supported GINs for SNPN. This message is broadcast by the NG-RAN node and used by the UE NAS layer for SNPN selection, making it an essential component in the 5G network architecture.
section_title: 16.6.2.3 Connected Mode
biotag_Context: O,B-Network Function,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,B-Parameter,O,O,B-Network,B-Parameter,O,O,O,B-Network,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Network,O,O,O,O,O,O,O,B-Network Function,O,O,B-Network,O,O,O,O,O,O,B-Network Function,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,B-Network,B-Parameter,O,O,O,B-Specification,O,O,O,O,O,B-Technology,I-Technology,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Interface,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Specification,O,O,O,O,O,B-Technology,I-Technology,O,O,O,O,O,O,O,O,O,O,B-Network Function,I-Network Function,O,B-Network,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,B-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,B-Specification,O,O,O,O,O,B-Technology,I-Technology,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,B-Message,O,O,O,O,O,O,B-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,B-Message,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,B-Message,O,O,B-Network,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,B-Protocol,O,O,O,O,O,B-Network,O,O,O,O,B-Device,O,O,O,O,O,B-Network,O,O,O,O,O,B-Organization,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,B-Network,O,B-Message,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,B-Protocol,O,O,O,O,O,O,B-Network,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,B-Protocol,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O
biotag_Description: B-Message,I-Message,I-Message,I-Message,I-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,B-Network Function,I-Network Function,I-Network Function,I-Network Function,I-Network Function,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O