name: MN
full_form:  Node
context: it supports the use of integrity protection with ng-eNB: Case 1: UP security policy indicates UP Integrity Protection "required": In NGEN-DC scenario, the MN shall reject the PDU session. In NE-DC scenario, if the MN decides to activate the UP integrity protection for this PDU session, the MN shall not offload any DRB of the PDU session to the SN. In NR-DC scenario, the MN makes the decision for PDU sessions that are terminated at the MN while the SN makes the decision for PDU sessions that are terminated at the SN. Case 2: UP security policy indicates UP Integrity Protection "preferred": In NGEN-DC scenario, the MN shall always deactivate UP integrity protection. In this case, the SN shall always deactivate the UP integrity protection of any PDU session terminated at the SN. In NE-DC scenario, if the MN has activated any of this PDU session DRBs with UP integrity protection "on", the MN shall not offload any DRB of this PDU session to the SN. However, if the MN has activated all DRBs
description: The Mobile Node (MN) is a network function that plays a crucial role in managing PDU sessions and making decisions about UP integrity protection in various deployment scenarios, including NGEN-DC, NE-DC, and NR-DC.
explanation: MN is classified as a Network Function based on its role in controlling and managing PDU sessions, as well as making decisions about UP integrity protection, as highlighted by the context from 3GPP TS 33.501.
section_title: 6.10.4	Protection of traffic between UE and SN
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,O,O,B-Technology,O,O,B-Network Function,O,O,O,B-Connection,O,O,B-Technology,O,O,O,B-Network Function,O,O,O,O,B-Protocol,O,O,O,O,B-Connection,O,O,B-Network Function,O,O,O,O,B-Connection,O,O,B-Connection,O,O,O,O,O,B-Technology,O,O,B-Network Function,O,O,O,O,B-Connection,O,O,O,O,O,O,B-Network Function,O,O,B-Message,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,O,O,B-Technology,O,O,B-Network Function,O,O,O,B-Protocol,O,O,O,O,O,O,B-Message,O,O,O,O,B-Protocol,O,O,O,O,B-Connection,O,O,O,O,O,O,B-Technology,O,O,O,B-Network Function,O,O,O,O,O,B-Connection,O,O,O,B-Protocol,O,O,O,O,B-Network Function,O,O,O,O,B-Connection,O,O,B-Connection,O,O,O,O,O,O,O,B-Network Function,O,O,O,O
biotag_Description: O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O