name: ME
full_form:  Equipment
context: Confirm (uplink message 10), the updated target RNC deduces that the ME is a legacy ME since the ME did not include an IE about its enhanced UTRAN KH capabilities. - The target RNC informs the ME about that it is capable of the enhanced UTRAN KH in the Cell update confirm/URA update confirm message (downlink message 10). Since the ME is legacy, it will discard this unknown IE. SRNS relocation without ME involvement: - The key handling is exactly as described in the combined hard handover and SRNS relocation case above. - The target RNC informs the ME about that it is capable of the enhanced UTRAN KH in the RAN Mobility Information message (downlink message 10). Since the ME is legacy, it will discard this unknown IE. - From the RAN Mobility Information Confirm (uplink message 10), the updated target RNC deduces that the ME is a legacy ME since the ME did not include an IE about its enhanced UTRAN KH capabilities. A.2.1.2 Target RNC is not updated Combined hard handover and SRNS
description: The Mobile Equipment (ME) refers to user equipment, such as mobile phones or IoT devices, that connect to the network. In this context, ME is described as either legacy or capable of enhanced UTRAN key handling, indicating its role in telecommunications as a device interacting with the network.
explanation: The classification of ME as a Device is justified by the context describing it as user equipment that interacts with the network, receives messages from the RNC, and has capabilities related to key handling. This aligns with the definition of a Device within the telecommunications domain.
section_title: 5.3.2.3	Key derivations and capability indication at intra-UTRAN mobility with SRNS relocation
biotag_Context: O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Network Function,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,B-Message,O,O,O,B-Network,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Network,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,B-Procedure,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Network,O,O,O,B-Network,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Network Function,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,B-Message,O,O,O,B-Network,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Procedure
biotag_Description: O,B-Device,I-Device,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O