semi合集-English.pdf - 第1881页

SEMI E53-0704 © SEMI 1996, 2004 21 NOTICE: SEMI makes no warran ties or representations as to the suitability of the standards set forth herein for any particular application. The d etermination of the su itability of th…

SEMI E53-0704 © SEMI 1996, 2004 20

8.3.4.9 Trace Delete

Table 24 Trace Delete Service Detail

Parameter Req/Ind Rsp/Cnf Comment

(list of) Trace ID C C Identifies Trace Object(s) to be deleted. If a Trace Object ispre-defined, then the

error code “Cannot delete predefined” is returned. If a TraceID is not recognized,

then the error code “unknown trace report” is returned. If parameter is omitted in the

request, then all trace reports are deleted. In all cases, the (list of) Trace ID that are

deleted, is returned in the response.

ERStatus - C ERAck is set to false if any requested TraceID cannot be deleted.

ErrorCodes:

Unknown trace report

Cannot delete predefined

ErrorText shall be set to the TraceID of reports which could not be deleted.

8.3.4.10 Trace Report Request — Request the data reports specified by the trace object ID be sampled and sent to

the service user.

Table 25 Trace Report Request Service Detail

Parameter Req/Ind Rsp/Cnf Comment

TraceID M M(=) Identifies requested trace report.

TimeStamp - C Time at which request was serviced and data report samples taken. Parameter is

omitted if Trace ID is not recognized.

(list of)

DataReportSample

- C Samples of data reports assigned to the trace report. Parameter is omitted if Trace ID

is not recognized.

ERAck - C If the Data Report Samples cannot be sent, then this item shall be returned with its

Boolean value set to false. The most likely cause of this would be that the TraceID

was undefined.

8.3.4.11 Trace Report Send — The notification message sent by the service provider to the service user when the

trace object has prepared a trace report according to its definition.

Table 26 Trace Report Send Service Detail

Parameter Req/Ind Comment

TraceID M Identifies trace report.

(list of) TraceReportSample M Number of samples in list is determined by Group Size parameter in TraceReportCreate.

8.3.4.12 Trace Object Reset

Table 27 Trace Reset Service Detail

Parameter Req/Ind Rsp/Cnf Comment

(list of) TraceID C M Identifies trace report(s) to be reset. If a Trace ID is not recognized, then the error

code “unknown trace report” is returned. If parameter is omitted in the request, then

all trace reports are reset. In all cases, the (list of) TraceID that are reset is returned in

the response.

ERStatus - C ERAck is set to false if any requested TraceID cannot be reset.

ErrorCodes:

Unknown trace report

ErrorText shall be set to the TraceID of reports which could not be reset.

SEMI E53-0704 © SEMI 1996, 2004 21

NOTICE: SEMI makes no warranties or representations as to the suitability of the standards set forth herein for

any particular application. The determination of the suitability of the standard is solely the responsibility of the user.

Users are cautioned to refer to manufacturer’s instructions, product labels, product data sheets, and other relevant

literature respecting any materials mentioned herein. These standards are subject to change without notice.

The user’s attention is called to the possibility that compliance with this standard may require use of copyrighted

material or of an invention covered by patent rights. By publication of this standard, SEMI takes no position

respecting the validity of any patent rights or copyrights asserted in connection with any item mentioned in this

standard. Users of this standard are expressly advised that determination of any such patent rights or copyrights, and

the risk of infringement of such rights, are entirely their own responsibility.

International), 3081 Zanker Road, San Jose, CA 95134. Reproduction o

the contents in whole or in part is forbidden without express written

consent of SEMI.

SEMI E53.1-0704 © SEMI 1996, 2004 1

SEMI E53.1-0704

SECS-II SUPPORT FOR EVENT REPORTING STANDARD

This standard was technically approved by the Global Information & Control Committee and is the direct

responsibility of the Japanese Information & Control Committee. Current edition approved by the Japanese

Regional Standards Committee on April 30, 2004. Initially available at www.semi.org June 2004; to be

published July 2004. Originally published December 1996.

1 Purpose

1.1 This document maps the services and data of its

prime document, SEMI E53, to SECS-II streams and

functions and data definitions.

2 Scope

2.1 This is the standard way to implement the Event

Reporting, which provides event-based reporting using

the SECS-II message format.

NOTICE: This standard does not purport to address

safety issues, if any, associated with its use. It is the

responsibility of the users of this standard to establish

appropriate safety and health practices and determine

the applicability of regulatory or other limitations prior

to use.

3 Referenced Standards

3.1 SEMI Standards

SEMI E5 — SEMI Equipment Communications

Standard 2 Message Content (SECS-II)

SEMI E39 — Object Services Standard: Concepts,

Behavior, and Services

SEMI E39.1 — SECS-II Protocol for Object Services

Standard (OSS)

SEMI E53 — Event Reporting

NOTICE: Unless otherwise indicated, all documents

cited shall be the latest published versions.

4 Terminology

None.

5 Mapping of Event Reporting Messages

Table 1 Event Messages Mapping

Service Message Name Stream, Function SECS-II Name

Event Report Send S6F11,F12,F13,F14 Event Report Send/Acknowledge

Annotated Event Report Send/ Acknowledge

Event Report Request S6F15,F16 Event Report Request/Data

Data Report Request S6F19,F20 Individual Report Request/Data

Collection Event Link Request S17F9,F10 Collection Event Link Request/Acknowledge

Collection Event Unlink Request S17F11,F12 Collection Event Unlink Request/Acknowledge