name: EUTRAN
full_form: Evolved Universal Terrestrial Radio Access Network
context: A Delete Session Response message shall be sent on the S11 interface by the SGW to the MME and on the S5/S8 interface by the PGW to the SGW as part of the following procedures: - EUTRAN Initial Attach - UE, HSS or MME Initiated Detach - UE or MME Requested PDN Disconnection It shall also be sent on the S4 interface by the SGW to the SGSN and on the S5/S8 interface by the PGW to the SGW as part of the procedures: - MS, HLR or SGSN initiated detach procedure - Combined GPRS/IMSI Attach - MS and SGSN Initiated Default Bearer Deactivation Procedure using S4 On the S11 interface by the SGW to the MME as part of the procedures: - Tracking Area Update with SGW Change - S1 Based Handover with SGW Change - X2 Based Handover with SGW Relocation - E-UTRAN to UTRAN Iu mode Inter RAT handover with SGW change - E-UTRAN to GERAN A/Gb mode Inter RAT handover with SGW change - Inter RAT handover cancel with SGW change - MME to Gn/Gp SGSN combined hard handover and SRNS relocation procedure - MME to SGSN Routing Area Update - E-UTRAN to Gn/Gp SGSN Inter RAT handover - S1 Based handover cancel with SGW change - Optimised Active Handover: E-UTRAN Access to CDMA2000 HRPD Access - MME triggered Serving GW relocation And on the S4 interface by the SGW to the SGSN as part of the procedures: - Enhanced Serving RNS Relocation with SGW relocation using S4 - Routing Area Update with SGW change - SGSN to MME Tracking Area Update with SGW change - Serving RNS relocation with SGW change - UTRAN Iu mode to E-UTRAN Inter RAT handover with SGW change - GERAN A/Gb mode to E-UTRAN Inter RAT handover with SGW change - S4 SGSN to Gn/Gp SGSN Routeing Area Update - S4 SGSN to Gn/Gp SGSN Serving RNS Relocation Procedures - S4 SGSN to Gn/Gp SGSN PS handover Procedures - S4-SGSN triggered Serving GW relocation The message shall also be sent on the S2b interface by the PGW to the ePDG as part of procedures: - UE/ePDG Initiated Detach with GTP on S2b - UE Requested PDN Disconnection with GTP on S2b - HSS/AAA Initiated Detach with GTP on S2b The message shall also be sent on the S2a interface by the PGW to the TWAN as part of procedures: - UE/TWAN Initiated Detach and UE/TWAN Requested PDN Disconnection in WLAN on GTP S2a - HSS/AAA Initiated Detach in WLAN on GTP S2a This message may also be sent on S5/S8 interface by the PGW to the SGW: - If Downlink Data Notification Acknowledge message with Context not found cause value is received. The sending entity shall include Cause IE in the Delete Session Response message. The IE indicates if the peer has deleted the bearer, or not. Possible Cause values are specified in Table 8.4-1. Message specific cause values are: - "Context not found". - "Invalid peer". Table .1-1 specifies the presence of the IEs in the message. Table .1-1: Information Elements in a Delete Session Response Table 7.2.10.1-2: Load Control Information within Delete Session Response Table 7.2.10.1-3: Overload Control Information within Delete Session Response
description: The Evolved Universal Terrestrial Radio Access Network (EUTRAN) is a critical component of the Long-Term Evolution (LTE) network architecture, responsible for providing wireless access to user equipment. It consists of eNodeBs (eNBs), which are the base stations that provide radio coverage and connect to the core network via the S1 interface. EUTRAN plays a vital role in managing various procedures such as initial attach, detach, handover, and bearer management, ensuring efficient communication between user equipment and the core network.
explanation: EUTRAN is classified as a NetworkFunction_Group because it encompasses a set of interconnected network functions that work together to deliver specific telecommunications capabilities. In this context, EUTRAN is responsible for managing radio access and connectivity, making it an essential part of the LTE network architecture.
section_title: .1 Delete Session Response
biotag_Context: O,O,O,O,O,O,O,O,O,O,B-Interface,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,O,O,O,B-Network,O,O,O,O,B-Network Function,O,B-Network Function,O,B-Message,O,B-Device,O,B-Network Function,O,B-Network,O,O,O,O,O,O,O,O,B-Interface,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,O,O,O,B-Network Function,O,B-Network Function,O,O,O,O,O,O,O,O,B-Parameter,O,B-Network Function,O,O,O,O,O,O,B-Interface,O,O,B-Interface,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,O,O,B-Procedure,I-Procedure,I-Procedure,O,B-Network Function,O,O,B-Miscellaneous,O,B-Procedure,O,B-Network Function,O,O,B-Miscellaneous,O,B-Procedure,O,B-Network Function,O,O,B-Network,O,B-Network,B-Mode,I-Mode,O,B-Technology,O,O,B-Network Function,O,O,B-Network,O,B-Network,B-Mode,I-Mode,O,B-Technology,O,O,B-Network Function,O,O,O,B-Technology,O,O,O,B-Network Function,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,B-Procedure,O,O,O,B-Network Function,O,B-Network Function,B-Procedure,I-Procedure,I-Procedure,O,B-Network,O,O,B-Network Function,O,B-Technology,O,O,B-Miscellaneous,O,O,O,O,B-Network Function,O,O,O,O,O,B-Network,O,O,O,B-Technology,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,B-Interface,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,O,O,O,B-Procedure,I-Procedure,O,O,B-Network Function,O,O,B-Interface,O,B-Procedure,I-Procedure,I-Procedure,O,B-Network Function,O,O,B-Network Function,O,B-Network Function,B-Procedure,I-Procedure,I-Procedure,O,B-Network Function,O,O,B-Procedure,I-Procedure,O,O,B-Network Function,O,O,B-Network,B-Mode,I-Mode,O,B-Network,O,B-Technology,O,O,B-Network Function,O,O,B-Network,B-Mode,I-Mode,O,B-Network,O,B-Technology,O,O,B-Network Function,O,O,B-Interface,B-Network Function,O,O,B-Network Function,O,O,O,O,B-Interface,B-Network Function,O,O,B-Network Function,B-Procedure,I-Procedure,O,O,O,B-Interface,B-Network Function,O,O,B-Network Function,B-Mode,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,B-Message,O,B-Protocol,O,O,O,B-Device,O,B-Network,O,O,B-Protocol,O,O,O,O,O,B-Message,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Network,O,O,O,O,O,O,O,B-Message,O,O,O,B-Network,O,O,B-Network,O,B-Protocol,O,O,O,O,B-Message,O,B-Network,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,B-Message,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,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: O,B-Network,I-Network,I-Network,I-Network,I-Network,I-Network,O,O,O,O,O,O,O,B-Technology,I-Technology,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-Miscellaneous,O,B-Network,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