name: DTT
full_form: Digital Terrestrial Television
context: For optimization of RABs also SIP traffic should be taken into account. SIP traffic is mainly generated at session start up and session release. However SIP traffic is also allowed during the session. The SIP RAB should allow the transmission of SIP packets without significant delay and without SIP packet loss. The allocated bandwidth should be as small as possible. Please note that the signaling RAB for SIP is also the focus of a separate RAN3 investigation. It can be expected that in most cases PDP contexts marked with the signalling flag over Iu interface transfer IMS related signalling traffic like SIP. Nevertheless, it is not guaranteed that only IMS related signalling traffic is transferred. Therefore in general UTRAN cannot rely on the âsignalling flagâ. There is an optional mechanism defined for the GGSN to enforce that only IMS related signalling traffic is transferred. There is no enforcement in the UE possible, i.e. in uplink direction any traffic would have to be
description: Digital Terrestrial Television (DTT) is a technology standard for broadcasting digital television signals over-the-air using terrestrial transmission methods. In the context of 3GPP specifications, DTT is relevant to the protection requirements for Mobile/Fixed Communications Networks operating in specific frequency bands, ensuring that these networks do not interfere with DTT services.
explanation: The classification of DTT as a Technology entity type is based on its description within the provided context. The text mentions 'Digital Terrestrial Television' in relation to broadcasting and protection requirements for mobile communications networks, indicating it refers to a specific technological standard or method rather than any other category like Network Function, Interface, etc.
section_title: Annex D (normative):
  Regional requirement for protection of DTT
biotag_Context: O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Protocol,B-Connection,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,B-Protocol,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,B-Interface,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,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,B-Network,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: B-Technology,I-Technology,I-Technology,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Organization,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,O