name: SSDT
full_form: Site Selection Diversity Transmision
context: as RTP flow" solution. No backward compatibility issue with Release 5, in which RTP and RTCP must use the same PDP Context: - TS 23.228 states it in clause 4.2.5.1 "All associated IP flows (such as e.g. RTP / RTCP flows) used by the UE to support a single media component are assumed to be carried within the same PDP context.", - LS from SA2 to CN3 (S2-022627 [2]) confirmed it very clearly: to the question on what should be the interpretation to use, SA2 answered: " Interpretation 1) All RTCP flows shall be sent over the same PDP context as the associated RTP flows, Or Interpretation 2) That although it is assumed that in general RTCP packets will be sent over the same PDP context as the associated RTP flow, the mechanism shall also allow for the RTCP packets to be sent over different PDP contexts to the RTP data stream. SA2 confirms that interpretation 1 is the correct interpretation for Rel-5 IMS." Because of the separation of RTP and RTCP on different radio bearers no delay of RTP
description: Site Selection Diversity Transmission (SSDT) is a feature in the Universal Mobile Telecommunications System (UMTS) that enables the selection of the best cell site for transmission. It is used to improve the performance and efficiency of the network by allowing the Node B to activate or deactivate SSDT based on specific conditions, such as the inclusion of the SSDT Cell Identity IE in the RADIO LINK SETUP REQUEST message.
explanation: The context describes a technical feature (SSDT) within a telecommunications standard (UMTS). It outlines how SSDT operates, its purpose (improving network performance), and its implementation details (activation based on specific messages and information elements). This clearly classifies SSDT as a technological concept.
section_title: 8.2.17.2	Successful Operation
biotag_Context: O,B-Protocol,O,O,O,O,O,O,O,B-Specification,O,O,O,B-Protocol,O,B-Protocol,O,O,O,O,B-Protocol,O,O,B-Specification,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,B-Protocol,O,B-Protocol,O,O,O,O,B-Device,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,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Protocol,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,B-Protocol,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,B-Protocol,O,O,O,O,O,O,O,B-Protocol
biotag_Description: O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,I-Miscellaneous,I-Miscellaneous,I-Miscellaneous,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,I-Network Function,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,B-Technology,B-Parameter,I-Parameter,B-Message,O,O,O,O,O,O,O