name: MME
full_form: Mobility Management Entity
context: This example shows transport bearer establishment and data on Iur. This shows the case where the legacy RAN is the drift RNS. Figure 6-43: Connection Establishment on Iur 1) IP based RNC (serving RNS) initiates establishment of the radio link with RNSAP message Radio Link Setup Request. 2) The legacy RNC node sends RNSAP message Radio Link Setup Response to the IP based RNC containing TLA and TA. TLA contains the ATM endpoint identifier of the ATM based RNC and TA contains an binding ID chosen form the ATM based RNC. 3) The IP based RNC sends an Q.IP-ALCAP establishment request message (ERQ) to the IWU that contains the IP endpoint identifier (IP address and UDP port of the IP based RNC for the new link). The CEID will be set to NULL. 4) The IWU acts as an AAL type 2 switch, but in addition it removes the IPEID and generates the CEID. 5) The CN node sends the connection confirm message (ECF) to the IWU. 6) The IWU acts as an AAL type 2 switch, but in addition it IPEID containing IP
description: The Mobility Management Entity (MME) is a network function responsible for managing mobility-related tasks in the Evolved Packet Core (EPC). It plays a crucial role in verifying the membership status of User Equipment (UE) and informing the target Home eNodeB (HeNB) about the verified membership status via specific procedures. The MME checks UE subscriber data to determine the UE's membership status, ensuring seamless handovers and network transitions.
explanation: The context describes the MME's specific functions within the EPC, such as verifying user equipment membership and facilitating handovers. These tasks are characteristic of a Network Function, which performs defined operations within a telecommunications infrastructure.
section_title: 6.2.2.2	Issue 2: Membership Verification
biotag_Context: 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,B-Protocol,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Protocol,O,B-Connection,I-Connection,O,O,O,O,O,B-Network Function,O,O,B-Protocol,O,B-Connection,I-Connection,O,O,O,O,B-Protocol,O,B-Network Function,O,B-Parameter,O,O,B-Parameter,O,O,B-Specification,O,O,O,O,B-Specification,O,B-Network Function,O,B-Parameter,O,O,O,B-Parameter,O,O,O,B-Specification,O,O,O,O,B-Protocol,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Protocol,O,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Protocol,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,B-Network Function,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,B-Protocol
biotag_Description: O,B-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,I-Network,I-Network,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,I-Device,O,O,O,O,O,B-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O