name: DCN
full_form: Dedicated Core Network
context: Iâb â IP RNC with ATM Node B - Iâr â IP RNC with ATM RNC. When an operator is migrating from ATM to IP, for example, a newly deployed UTRAN node should be allowed to support only IP interfaces and still be able to interwork with ATM UTRAN nodes. It should not be required to support AAL2/ATM UTRAN interfaces in order to interoperate with AAL2/ATM UTRAN nodes. This is the case for the following reasons Otherwise, all Release 5 RNCs having connectivity with both ATm NEs and Ip NEs terminating RNL protocols would need to support both types of interfaces There may be manufacturers that want to supply only UTRAN nodes with one transport technology (such as IP-only nodes) but interwork with existing ATM nodes terminating RNL protocols in the operators network When an operator is migrating from ATM to IP, the newly deployed nodes would need to also support ATM interfaces to interwork with the legacy ATM nodes terminating RNL protocols. This means that the ATM network is being extended, which
description: The Dedicated Core Network (DCN) is a collective set of interconnected network functions that work together to deliver specific telecommunications capabilities. In this context, the DCN is involved in the reroute NAS request procedure, where the SGSN initiates the procedure by sending a REROUTE NAS REQUEST message to the RNC, which then reroutes the INITIAL UE MESSAGE message to the DCN indicated by the SGSN Group Identity IE.
explanation: The context describes the DCN as a network entity that is involved in the reroute NAS request procedure, and is indicated by the SGSN Group Identity IE. This suggests that the DCN is a group of interconnected network functions that work together to deliver specific telecommunications capabilities, making it a NetworkFunction_Group.
section_title: 8.49.2	Successful Operation
biotag_Context: O,O,B-Protocol,B-Network Function,O,B-Specification,B-Network Function,I-Network Function,O,O,O,B-Protocol,B-Network Function,O,B-Specification,O,O,O,O,O,O,O,B-Specification,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Specification,B-Network,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,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-Specification,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,O,O,O,O,B-Specification,O,O,B-Protocol,O,O,O,O,O,B-Specification,O,O,O,O,O
biotag_Description: O,B-Network,I-Network,I-Network,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,B-Protocol,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Network,O,O,O,B-Network Function,O,B-Parameter,O