Ç¥ÁØÈ­ Âü¿©¾È³»

TTAÀÇ Ç¥ÁØÇöȲ

Ȩ > Ç¥ÁØÈ­ °³¿ä > TTAÀÇ Ç¥ÁØÇöȲ

Ç¥ÁعøÈ£ TTAT.3G-32.421(R7-7.2.0) ±¸Ç¥ÁعøÈ£
Á¦°³Á¤ÀÏ 2008-04-09 ÃÑÆäÀÌÁö 0
ÇѱÛÇ¥Áظí IMT-2000 3GPP-Åë½Å °ü¸®; °¡ÀÔÀÚ¿Í ÀåÄ¡°£ ÃßÀû; ÃßÀûÀÇ °³³ä°ú ¿ä±¸»çÇ×(R7)
¿µ¹®Ç¥Áظí IMT-2000 3GPP-Telecommunication management; Subscriber and equipment trace; Trace concepts and requirements(R7)
Çѱ۳»¿ë¿ä¾à
¿µ¹®³»¿ë¿ä¾à The present document describes the requirements for the management of Trace and the reporting of Trace data (including FDD mode and TDD mode) across UMTS networks as it refers to subscriber tracing (tracing of IMSI or Private ID) and equipment tracing (tracing of IMEI or IMEISV). Trace also includes the ability to trace all active calls in a cell or multiple cells (Cell Traffic Trace). The present document also includes the description of Service Level Tracing (tracing of a specific service). It defines the administration of Trace Session activation/deactivation by the Element Manager (EM), the network or User Equipment (UE) itself via signalling, the generation of Trace results in the Network Elements (NEs) and UE and the transfer of these results to one or more Operations Systems, i.e. EM(s) and/or Network Manager(s) (NM(s)).
The present document is built upon the basic Subscriber and UE Trace concept described in clause 4.
The high-level requirements for Trace data, Trace Session activation/deactivation and Trace reporting are defined in clause 5. Clause 5 also contains an overview of use cases for Trace (the use cases are described in Annex A). Trace control and configuration management are described in 3GPP TS 32.422 [2], and Trace data definition and management are described in 3GPP TS 32.423 [3].
In this 3GPP Release, the present document does not cover any Trace capability limitations within a NE (e.g. maximum number of simultaneous traced mobiles for a given NE) or any functionality related to these limitations (e.g. NE aborting a Trace Session due to resource limitations).
The objectives of UMTS Trace specifications are:
a) to provide the descriptions for a standard set of Trace data;
b) to produce a common description of the management technique for Trace administration and result reporting;
c) to define a method for Trace results reporting across the management interfaces.
The following is beyond the scope of the present document, and therefore the present document does not describe:
- tracing non-Subscriber or non-UE related events within an NE;
- tracing of all possible parties in a multi-party call (although multiple calls related to the IMSI specified in the Trace control and configuration parameters are traceable).
The definition of Trace data is intended to result in comparability of Trace data produced in a multi-vendor wireless UMTS network, for those Trace control and configuration parameters that can be standardised across all vendors' implementations.
Vendor specific extensions to the Trace control and configuration parameters and Trace data are discussed in 3GPP TS 32.422 [2] and 3GPP TS 32.423 [3].
±¹Á¦Ç¥ÁØ
°ü·ÃÆÄÀÏ TTAT.3G-32.421(R7-7.2.0).zip TTAT.3G-32.421(R7-7.2.0).zip            

ÀÌÀü
IMT-2000 3GPP - ÁøÈ­µÈ UTRAN-S1 °èÃþ(R8)
´ÙÀ½
IMT-2000 3GPP - ÁøÈ­µÈ UTRAN-S1 ÀÀ¿ë ÇÁ·ÎÅäÄÝ(R8)