name: GPL
full_form: Generic Push Layer
context: between the ME and the UICC. To utilise GPL as described in this document the ME and/or UICC shall be equipped with a GPL protocol entity implementing the processing of the protocol. In addition, to be able to use GPL it is necessary to implement the GPI processing described in TS 33.223 [3]. The GPL protocol entity resides in the ME (called GPL_ME) or in the UICC (called GPL_U). When the GPL protocol entity to be used is in the ME, Ks_NAF shall be used as the shared master key between the ME and the Push-NAF. When the GPL protocol entity to be used resides in the UICC, Ks_int_NAF shall be used as the shared master key between the UICC and the Push-NAF. The Push-NAF must have knowledge of MEâs capabilities to support GPL_ME and/or the USIM/ISIMs capabilities to support GPL_U (depending on which GPL protocol entity is targeted). Otherwise the Push-NAF cannot know if it can send GPL messages to the UE or which type of GPL messages the UE understands. Therefore the GPL capabilities of
description: The Generic Push Layer (GPL) is a protocol entity that enables the processing of push messages between the Mobile Equipment (ME) and the Universal Integrated Circuit Card (UICC). It resides in either the ME or the UICC and utilizes shared master keys for secure communication with the Push-NAF.
explanation: The text describes GPL as a layer facilitating secure communication and processing of push messages, which are key functions of a protocol.
section_title: 4.2	Requirements
biotag_Context: O,O,B-Network Function,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Network Function,O,B-Device,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Message,O,O,O,B-Specification,O,O,O,B-Protocol,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Device,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,O,B-Network Function,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,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,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,B-Device,O,O,O,O,B-Protocol,O,O,B-Device,O,O,O,B-Protocol,O,O
biotag_Description: O,B-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,I-Device,O,O,O,B-Device,I-Device,I-Device,I-Device,O,O,O,O,O,O,B-Network Function,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O