name: UP
full_form: User Plane
context: protection is "preferred", then the MN (MeNB) always deactivates UP IP. The SN (SgNB) always deactivates the UP IP of any PDU session terminated at the SN. This is because MN being an eNB does not support UP IP and thus is not able to indicate to the SN (SgNB) regarding the use of UP IP. c. If the UP security policy indicates UP integrity protection is "not needed", then the MN and SN always activates DRBs disabling the UP IP. 2. NE-DC scenario (CN=5GC, eNB=SN, gNB=MN) a. If the UP security policy indicates UP integrity protection is "required", then if the MN (MgNB) activates the UP IP for the PDU session, then the MN (MgNB) does not offload any DRB of the PDU session to the SN (SeNB). This is because the MN (MgNB) supports UP IP, but the SN being an eNB does not support the UP IP. b. If the UP security policy indicates UP integrity protection is "preferred", and if the MN (MgNB) activates any of the PDU session DRBs with UP IP, then the MN (MgNB) does not offload any DRB on this PDU
description: The User Plane (UP) is a network function responsible for managing user data transmission in the 5G core network. It handles packet forwarding, routing, and switching, enabling efficient data transfer between the radio access network and the core network.
explanation: UP is classified as a Network Function based on its role in managing user data transmission within the network, as highlighted by the context which describes UP's involvement in deactivating/activating IP and offloading DRBs.
section_title: 5.4.1	Issue description
biotag_Context: O,O,O,O,O,B-Network Function,O,O,O,B-Protocol,O,O,B-Message,O,O,O,O,B-Protocol,B-Protocol,O,O,B-Connection,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,B-Protocol,B-Protocol,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,B-Protocol,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Network Function,O,B-Message,O,O,O,O,O,B-Protocol,O,O,B-Technology,O,O,O,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Protocol,B-Protocol,O,O,B-Connection,O,O,O,B-Network Function,O,O,O,O,O,B-Connection,O,O,B-Connection,O,O,O,B-Message,O,O,O,O,O,B-Network Function,O,O,B-Protocol,O,O,O,B-Message,O,O,B-Network Function,O,O,O,O,B-Protocol,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Connection,O,O,O,B-Protocol,O,O,O,B-Network Function,O,O,O,O,O,B-Connection,O,O,B-Connection
biotag_Description: O,B-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O