name: LMA
full_form: Local Mobility Anchor
context: (From S3-070756) PMIPv6 defines a MAG (Mobile Access Gateway) and an LMA (Local Mobility Anchor) from which the LMA will be integrated in the PDN Gateway or Serving Gateway (for the roaming case). Figure 9: Protocols for MM control and user planes of S2a for the PMIPv6 option TS 23.402v130 section 5 is relevant in this respect and specifies that PMIPv6 may be used on following reference points: S2a: Between a node in the trusted non-3GPP access network (Foreign agent) and the LMA (Home Agent) S2b: Between the ePDG and the LMA (Home Agent). TS 23.402v130 section mentions the use of PMIP based S5 reference point between the Serving Gateway and the PDN Gateway. The S5 reference point may also apply GTP, and is an intra-operator interface. PMIP usage over S5/S8b is currently included in the description of PMIP use over S2b, and (see section 5.4.2.4.3 TS 23.402) in case of roaming, the S-GW is the LMA for PMIP procedure in S2b between the ePDG and the S-GW and the PDN GW is the LMA for PMIP
description: The Local Mobility Anchor (LMA) is a network function that plays a crucial role in managing mobility of user equipment (UE) within the network. It serves as an anchor point for UE sessions, enabling seamless handovers and session continuity across different access networks.
explanation: Based on the context from 3GPP TS 33.922 and TS 23.402, LMA is classified as a Network Function due to its involvement in mobility management, integration with PDN Gateway or Serving Gateway, and participation in PMIPv6 procedures.
section_title: 7.4.1.2	Overview of PMIP usage in 3GPP
biotag_Context: O,O,B-Protocol,O,O,B-Network Function,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Network Function,I-Network Function,O,B-Network Function,I-Network Function,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Protocol,O,B-Specification,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,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Specification,O,O,O,O,O,O,B-Protocol,O,B-Interface,O,O,O,O,B-Network Function,I-Network Function,O,O,B-Network,O,O,B-Interface,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Specification,O,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,B-Protocol,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Network Function,I-Network Function,O,O,B-Network Function,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,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O