name: SGSN
full_form: Serving GPRS Support Node
context: In the special case of a UTRAN target RNC a possible SGSN that can control that RNC can be identified by RNC-ID. This identifier can be used for SRNS relocation with a U-TRAN target RNC. A subdomain name for use by core network nodes based on RNC-ID shall be derived from the MNC and MCC by adding the label "rnc" to the beginning of the Home Network Realm/Domain (see clause 19.2). The RNC FQDN shall be constructed as: rnc<RNC>.rnc.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org <RNC> shall be Hex coded digits representing the RNC-ID code of the RNC. If there are less than 4 significant digits in <RNC>, one or more "0" digit(s) is/are inserted at the left side to fill the 4 digit coding. NOTE: Above subdomain is for release 8 core network nodes to allow DNS records other than A/AAAA records. The subdomain name in Annex C.3 are still used for existing A/AAAA records for pre-Release 8 nodes and are still used for backward compatibility. However, RNC-ID in Annex C.3 was originally intended for the case where only one SGSN controlled an RNC-ID and gave the SGSN IP address. The usage for the above RNC FQDN is potentially broader and can target an SGSN pool.
description: The Serving GPRS Support Node (SGSN) is a network function that controls and manages multiple Radio Network Controllers (RNCs) in a UTRAN. It plays a crucial role in identifying the target RNC for SRNS relocation and is involved in constructing the RNC Fully Qualified Domain Name (FQDN) based on the RNC-ID, MNC, and MCC.
explanation: SGSN is classified as a Network Function because it serves as an intermediary between the core network and the radio access network, managing multiple RNCs and facilitating communication between them. Its role in identifying target RNCs for SRNS relocation and constructing RNC FQDNs highlights its importance in maintaining seamless connectivity within the UTRAN.
section_title: 19.4.2.7 Target RNC-ID for U-TRAN
biotag_Context: O,O,O,O,O,O,B-Network,O,B-Network Function,O,O,B-Network Function,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,B-Network,I-Network,O,O,O,O,O,B-Network Function,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Service,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,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,O,O,O,B-Network Function,B-Protocol,O,O,O,O,O,O,B-Network Function,B-Parameter,O,O,O,O,O,O,O,B-Network Function,O
biotag_Description: O,B-Network Function,I-Network Function,I-Network Function,I-Network Function,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 Function,O,B-Procedure,O,O,O,O,O,O,O,B-Network Function,B-Parameter,I-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O,O