Ȩ > ÀڷḶ´ç > ÀÚ·á°Ë»ö > Ç¥ÁØ
ÀÚ·á °Ë»ö°á°ú
Ç¥ÁØÁ¾·ù | Á¤º¸Åë½Å´ÜüǥÁØ(TTAS) | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Ç¥ÁعøÈ£ | TTAT.3G-32.423(R7-7.4.0) | ±¸ Ç¥ÁعøÈ£ | |||||||||||||||
Á¦°³Á¤ÀÏ | 2008-04-09 | ÃÑ ÆäÀÌÁö | 0 | ||||||||||||||
ÇÑ±Û Ç¥Áظí | IMT-2000 3GPP-Åë½Å °ü¸®; °¡ÀÔÀÚ¿Í ÀåÄ¡°£ ÃßÀû; ÃßÀû µ¥ÀÌÅÍ Á¤ÀÇ¿Í °ü¸®(R7) | ||||||||||||||||
¿µ¹® Ç¥Áظí | IMT-2000 3GPP-Telecommunication management; Subscriber and equipment trace; Trace data definition and management(R7) | ||||||||||||||||
ÇÑ±Û ³»¿ë¿ä¾à | |||||||||||||||||
¿µ¹® ³»¿ë¿ä¾à |
The present document describes Trace data definition and management. It covers the trace records content, their format and transfer.
The objectives of the present document are: • To provide the descriptions for a standard set of Trace data; • To define the common format of trace records; and • To define a method for Trace results reporting across the management interfaces. Clause 4 details the various Trace records content, Annex A provides Trace report file format, Annex B provides the trace report file conventions and transfer procedure, Annex C provides the trace reporting functional architecture and Annex D provides some trace files examples. Trace concepts and requirements are covered in TS 32.421 [2] while Trace control and configuration management are described in 3GPP TS 32.422 [3]. The definition of Trace data is intended to result in comparability of Trace data produced in a multi-vendor wireless 3G network. The following is beyond the scope of the present document, and therefore the present document does not describe: • Any notification mechanisms or IRPs for trace. Only file transfer mechanism is specified for trace data transfer; • Any data compression mechanisms for trace data transfer; • Any Trace capability limitations (e.g. maximum number of simultaneous traced mobiles for a given NE). |
||||||||||||||||
°ü·Ã IPR È®¾à¼ | Á¢¼öµÈ IPR È®¾à¼ ¾øÀ½ | ||||||||||||||||
°ü·ÃÆÄÀÏ |
![]() |
||||||||||||||||
Ç¥ÁØÀÌ·Â |
|