name: LCS-AP
full_form: LCS Application Protocol
context: information in SIB1 as described in [12]. The UE applies the system information acquisition procedure according to [12] for acquiring the assistance data information that is broadcasted. 3. If the posSIB types were ciphered by the E-SMLC, the E-SMLC provides the used ciphering keys, together with a validity time and validity area for each key, to the MME using an LCS-AP Ciphering Key Data message described in TS 29.171 [27]. The MME returns a LCS-AP Ciphering Key Data Result message back to the E-SMLC indicating whether the MME was able to successfully store the ciphering data sets. The MME may then distribute successfully stored ciphering keys and their validity times and validity areas to suitably subscribed UEs using a mobility management message as described in TS 23.271 [2]. The E-SMLC repeats this procedure whenever a ciphering key changes. 4. At any time after Step 1, the eNB may send a LPPa Assistance Information Feedback message to the E-SMLC providing feedback on assistance
description: The LCS Application Protocol (LCS-AP) is a protocol used for communication between the Evolved Serving Mobile Location Centre (E-SMLC) and the Mobility Management Entity (MME) in the context of Location Services (LCS). It enables the exchange of ciphering keys, validity times, and validity areas for secure data transmission. The LCS-AP is utilized for procedures such as broadcasting assistance data information to User Equipment (UEs), handling ciphered positioning data, and providing feedback on assistance information.
explanation: The context describes LCS-AP as a protocol facilitating communication between network entities (E-SMLC and MME) for location services. It defines rules for data exchange, including ciphering keys and validity periods, which are characteristic of protocols.
section_title: 7.6.2	Broadcast Procedures
biotag_Context: O,O,B-Message,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,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,O,O,B-Protocol,B-Parameter,I-Parameter,O,O,O,O,B-Specification,O,O,O,B-Network Function,O,O,B-Protocol,B-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,B-Network Function,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,B-Specification,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,O,O,O,O,O,O,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,O,O,O,B-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,B-Service,I-Service,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,B-Device,I-Device,O,O,O,O,O,O,O,O,O,O,O