name: ECS
full_form: Edge Configuration Server
context: Figure 6.9.2-1: Authentication/Authorization between Edge Enabler Client and ECS Pre-conditions: - The EEC and ECS have shared A-KID and KAF via AKMA (as specified in TS 33.535 [1]). - The ECS or the 5GC is configured with the edge computing related profile for the EEC. - The ECS and the 5GC share an UE identifier (i.e. GPSI) to identify the EEC. - The ECS stores the association between EEC ID and UE identifier. This association is pre-configured in the ECS by the ECS administrator. Step 1: UE initiates the service provisioning procedure with EEC ID included (as specified in clause 8.3 in TS 23.558 [2]). Step 2: The ECS retrieves GPSI from EEC ID according to the preconfigured association. Step 3: In order to prove the authenticity of the UE's GPSI, the ECS sends an association check request to UDM (if the ECS is located out of 5GC, the request should be sent via NEF), including the GPSI and A-KID. Step 4: In order to verify the association of GPSI and A-KID, the UDM first contacts the
description: The Edge Configuration Server (ECS) is a network function responsible for managing edge computing configurations and authenticating/authorizing edge enabler clients. It interacts with other network functions such as the User Data Management (UDM) and the Network Exposure Function (NEF) to verify user equipment identities and manage service provisioning.
explanation: The ECS is classified as a Network Function based on its role in managing edge computing configurations, authenticating/authorizing clients, and interacting with other network functions as described in the context from 3GPP TS 33.839.
section_title: 6.9.2	Solution details
biotag_Context: O,O,O,O,B-Network Function,I-Network Function,I-Network Function,O,B-Network Function,O,O,O,B-Network Function,O,B-Network Function,O,O,O,O,B-Parameter,O,B-Protocol,O,O,O,B-Specification,O,O,O,O,B-Network Function,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Network,O,O,B-Device,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Network Function,B-Parameter,O,B-Device,O,O,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,B-Device,O,O,O,O,O,O,B-Network Function,B-Parameter,O,O,O,O,O,O,O,B-Specification,O,O,O,O,O,B-Network Function,O,B-Parameter,O,B-Network Function,B-Parameter,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,B-Network Function,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Network Function,O,O,O
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,O,O,O,O,B-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O