name: S9
full_form: Interface between Home Subscriber Server (HSS) and EIR
context: Figure 4.3.3.2-1 represents the Roaming architecture with local breakout and Figure 4.3.3.2-2 represents the Roaming architecture with home-routed traffic for interworking between 5GC via non-3GPP access and EPC/E-UTRAN. Figure 4.3.3.2-1: Local breakout roaming architecture for interworking between 5GC via non-3GPP access and EPC/E-UTRAN NOTE 1: There can be another UPF (not shown in the figure above) between the N3IWF/TNGF and the UPF + PGW-U, i.e. the UPF + PGW-U can support N9 towards the additional UPF, if needed. NOTE 2: S9 interface from EPC is not required since no known deployment exists. NOTE 3: N26 interface is not precluded, but it not shown in the figure because it is not required for the interworking between 5GC via non-3GPP access and EPC/E-UTRAN. Figure 4.3.3.2-2: Home-routed roaming architecture for interworking between 5GC via non-3GPP access and EPC/E-UTRAN NOTE 4: N26 interface is not precluded, but it not shown in the figure because it is not required for the interworking between 5GC via non-3GPP access and EPC/E-UTRAN.
description: The S9 interface is a reference point between the Home Subscriber Server (HSS) and the Equipment Identity Register (EIR). It plays a role in roaming architectures, particularly in scenarios involving interworking between the 5G Core Network (5GC) via non-3GPP access and the Evolved Packet Core (EPC)/Evolved Universal Terrestrial Radio Access Network (E-UTRAN).
explanation: The S9 interface is classified as an Interface because it defines a specific point of communication between two network functions, namely the HSS and EIR. This classification aligns with the context provided in 3GPP TS 23.501, which discusses system architecture for the 5GS, highlighting its relevance in roaming architectures.
section_title: 4.3.3.2 Roaming architecture
biotag_Context: O,O,O,O,O,O,O,O,O,O,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,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Network Function,O,B-Network Function,O,O,B-Interface,O,O,O,O,O,O,O,O,B-Interface,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,B-Interface,O,O,O,O,O,O,O,O,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,O,O,B-Network,O,O,O,O,O,O,O,B-Interface,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O
biotag_Description: O,B-Interface,O,O,O,O,O,O,O,B-Network Function,I-Network Function,I-Network Function,O,O,O,B-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,I-Network,I-Network,O,O,O,O,O,O,B-Network,I-Network,I-Network,O,B-Network,I-Network,I-Network,I-Network,I-Network,O