name: EPC
full_form: Evolved Packet Core
context: entity in the local EPC domain with any entity in the macro EPC domain shall be confidentiality and integrity protected. NOTE 1: The IOPS solution described in 3GPP TS 23.401 [10] addresses only the scenario of a Local EPC with no backhaul to the Macro EPC. The architecture does not allow for eNBs to be connected to both a Local EPC and Macro EPC simultaneously. Furthermore, the architecture does not allow for signaling between Local and Macro EPC. Any signaling interface between any entity in one local EPC domain with any entity in another local EPC domain shall be confidentiality and integrity protected. NOTE 2: The IOPS solution described in 3GPP TS 23.401 [10] means an eNB operating in IOPS mode may only establish an S1 interface to one Local EPC (either a co-located Local EPC or a Local EPC within the local IP network). The S1 interface between an eNB operating in IOPS mode and a Local EPC is subject to the same security requirements as for an S1 interface between an eNB and a
description: The Evolved Packet Core (EPC) is a core network architecture in LTE that provides a converged IP-based infrastructure for various access networks, including LTE, UMTS, and others. It consists of several key components such as the Mobility Management Entity (MME), Serving Gateway (SGW), and Packet Data Network Gateway (PGW).
explanation: EPC is classified as a Network because it provides the fundamental infrastructure for communication within a mobile network. It manages user connections, routes data traffic, and handles essential network functions like authentication and security.
section_title: 6.3.3	Potential security requirement
biotag_Context: O,O,O,O,B-Network,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,B-Specification,I-Specification,I-Specification,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,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,B-Network,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,B-Specification,I-Specification,I-Specification,O,O,O,B-Network Function,O,O,B-Technology,O,O,O,O,O,B-Miscellaneous,O,O,O,O,B-Network,O,O,O,O,B-Network,O,O,O,B-Network,O,O,O,B-Protocol,O,O,B-Miscellaneous,O,O,O,B-Network Function,O,O,B-Technology,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,B-Network Function,O,O
biotag_Description: O,B-Network,I-Network,I-Network,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,O,O,B-Network Function,I-Network Function,I-Network Function,O,B-Network Function,I-Network Function,O,O,B-Network Function,I-Network Function,I-Network Function,I-Network Function,O