name: EMKS
full_form: End to Middle Key Server
context: Following procedures are supported over the RESTful HTTP reference point: - Initial registration by EMSE - Obtaining UE specific e2m_key from EMKS - Deregistration by EMSE - Subscription to Notification by EMKS - Notification by EMSE Editorâs Note: Subscription by EMSE to a particular event, and Notification by EMKS is ffs 6.10.2.2.2.1 Initial registration by EMSE The EMSE registers with EMKS by sending an HTTP POST message to the EMKS including its identifier (EMSE_Id). The EMKS establishes a session context for this EMSE and returns session id in HTTP 201 CREATED. 6.10.2.2.2.2 Obtaining UE specific e2m key from the EMKS The EMSE obtains UE specific e2m key from the EMKS by sending an HTTP GET message including an identity of the UE and a key identifier received from the UE. This message is embedded in the following example information flow using DTLS-PSK. 6.10.2.2.2.3 Deregistration by EMSE When the session needs to be terminated, EMSE may send an HTTP DELETE message including the
description: The End to Middle Key Server (EMKS) is a network function responsible for managing and distributing UE-specific e2m keys. It interacts with the End to Middle Security Entity (EMSE) through RESTful HTTP reference points, handling procedures such as initial registration, obtaining UE-specific e2m keys, deregistration, subscription to notifications, and sending notifications.
explanation: The context describes EMKS as a component that manages keys and interacts with other network entities (EMSE) via defined protocols. This clearly defines it as a Network Function performing a specific task within the telecommunications infrastructure.
section_title: 6.10.2.2.2	Procedures over the RESTful HTTP reference point
biotag_Context: O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Network Function,O,O,B-Device,O,O,O,B-Network Function,O,O,O,B-Network Function,O,O,O,O,O,B-Network Function,O,O,O,B-Network Function,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Network Function,O,B-Network Function,O,O,B-Network Function,O,O,O,B-Protocol,O,O,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-Protocol,O,O,O,O,B-Device,O,O,O,O,O,B-Network Function,O,B-Network Function,O,B-Device,O,O,O,O,O,B-Network Function,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Device,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,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Protocol,O,O,O,O
biotag_Description: O,B-Network Function,I-Network Function,I-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,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O