TA Document 2002016 IEEE1394 Interface Implementation Test Specification STB Device for Japanese Digital Broadcasting System 1.0 December 15, 2003 Sponsored by: 1394 Trade Association Accepted for Release by: 1394 Trade Association Board of Directors. Abstract: This document provides the IEEE 1394 test specification for STB devices which supports Japanese digital broadcasting system. Keywords: STB Copyright 1996-2004 by the 1394 Trade Association. 1111 South Main Street, Suite 100, Grapevine, TX 76051, USA http://www.1394ta.org All rights reserved. Permission is granted to members of the 1394 Trade Association to reproduce this document for their own use or the use of other 1394 Trade Association members only, provided this notice is included. All other rights reserved. Duplication for sale, or for commercial or for-profit use is strictly prohibited without the prior written consent of the 1394 Trade Association.
STB for Japanese Test Specification 1.0 TA Document 2002016, December 15, 2003 1394 Trade Association Specifications are developed within Working Groups of the 1394 Trade Association, a non-profit industry association devoted to the promotion of and growth of the market for IEEE 1394-compliant products. Participants in working groups serve voluntarily and without compensation from the Trade Association. Most participants represent member organizations of the 1394 Trade Association. The specifications developed within the working groups represent a consensus of the expertise represented by the participants. Use of a 1394 Trade Association Specification is wholly voluntary. The existence of a 1394 Trade Association Specification is not meant to imply that there are not other ways to produce, test, measure, purchase, market or provide other goods and services related to the scope of the 1394 Trade Association Specification. Furthermore, the viewpoint expressed at the time a specification is accepted and issued is subject to change brought about through developments in the state of the art and comments received from users of the specification. Users are cautioned to check to determine that they have the latest revision of any 1394 Trade Association Specification. Comments for revision of 1394 Trade Association Specifications are welcome from any interested party, regardless of membership affiliation with the 1394 Trade Association. Suggestions for changes in documents should be in the form of a proposed change of text, together with appropriate supporting comments. Interpretations: Occasionally, questions may arise about the meaning of specifications in relationship to specific applications. When the need for interpretations is brought to the attention of the 1394 Trade Association, the Association will initiate action to prepare appropriate responses. Comments on specifications and requests for interpretations should be addressed to: Editor, 1394 Trade Association 1111 South Main Street, Suite 100 Grapevine, TX 76051, USA 1394 Trade Association Specifications are adopted by the 1394 Trade Association without regard to patents which may exist on articles, materials or processes or to other proprietary intellectual property which may exist within a specification. Adoption of a specification by the 1394 Trade Association does not assume any liability to any patent owner or any obligation whatsoever to those parties who rely on the specification documents. Readers of this document are advised to make an independent determination regarding the existence of intellectual property rights, which may be infringed by conformance to this specification. Page 2 Copyright 2004, 1394 Trade Association. All rights reserved.
TA Document 2002016, December 15, 2003 STB for Japanese Test Specification 1.0 Table of contents 1. Overview...6 1.1 Purpose...7 1.2 Scope...7 2. References...8 3. Definitions...9 3.1 Conformance levels...9 3.2 Glossary of terms...9 3.3 Acronyms and abbreviations...9 4. Lists of Test Items...10 4.1 General...10 4.1.1 Test environment...10 4.2 Basic Policies...10 4.2.1 AV/C Command Implementation Test...10 4.2.2 Isochronous Connection Control Implementation Test...11 4.2.3 Configuration ROM Specification Implementation Test...11 4.3 Evaluation Criteria...11 4.3.1 Evaluation Criteria for AV/C Command Implementation Test...11 4.3.2 Evaluation Criteria for Isochronous Connection Control Implementation Test...11 4.3.3 Evaluation Criteria for Configuration ROM Implementation Test...11 4.4 Descriptions of Test Contents...12 4.4.1 Grouping of Test Items...12 4.4.2 Structure of Test Contents...12 4.4.3 Setting range of test data...12 4.4.4 Test number...14 5. Test Items...19 5.1 Tuner Subunit implementation test...19 5.2 Bulletin Board Subunit implementation test...19 5.3 Implementation test items of AV/C to Unit...19 5.3.1 CONNECT command...19 5.3.2 CONNECTIONS command...21 5.3.3 SUBUNIT INFO command...22 5.3.4 UNIT INFO command...23 5.3.5 POWER command...24 5.3.6 PLUG INFO command...28 5.4 Implementation test items for control of Isochronous Connection...29 5.4.1 Implementation test items for control of Isochronous Connection for the Input Plug...29 5.4.2 Implementation test items for control of Isochronous Connection for the Output Plug...33 5.4.3 Other rule...34 5.5 Implementation test item for Configuration ROM...34 5.6 Implementation test for POWER command to Tuner Subunit...34 5.6.1 From Power off to Power on...35 5.6.2 From Power on to Power off...35 5.7 Implementation test for Unit internal signal connection...35 5.7.1 Behavior of SW1...35 5.7.2 Behavior of SW2...36 Copyright 2004, 1394 Trade Association. All rights reserved. Page 3
STB for Japanese Test Specification 1.0 TA Document 2002016, December 15, 2003 List of figures Figure 4-1 Test environment...10 Page 4 Copyright 2004, 1394 Trade Association. All rights reserved.
TA Document 2002016, December 15, 2003 STB for Japanese Test Specification 1.0 List of tables Table 4-1 Value of test number [Division 1] in AV/C command implementation test...14 Table 4-2 Value of test number [Division 2] in AV/C command implementation test...14 Table 4-3 Value of test number [Division 3] in AV/C command implementation test...15 Table 4-4 Value of test number [Division 1] in Isochronous Connection control implementation test...16 Table 4-5 Value of test number [Division 2], [Division 3] in test for input plug implementation test...16 Table 4-6 Value of test number [Division 1] in Configuration ROM implementation test...16 Table 4-7 Value of test number [Division 2] in Configuration ROM implementation test...17 Table 4-8 Value of test number [Division 1] in POWER command addressed to Tuner Subunit implementation test...17 Table 4-9 Value of test number [Division 2] in POWER command addressed to Tuner Subunit implementation test...17 Table 4-10 Value of test number [Division 1] in Unit internal signal connection implementation test...18 Table 4-11 Value of test number [Division 2] in Unit internal signal connection implementation test...18 Table 5-1 Test item on CONNECT command...19 Table 5-2 Test item on CONNECTIONS command...21 Table 5-3 Test item on SUBUNIT INFO command...22 Table 5-4 Test item on UNIT INFO command...23 Table 5-5 Test item on POWER control command...24 Table 5-6 Test item on POWER status command...25 Table 5-7 Test item on POWER notify command...26 Table 5-8 Test item on POWER specific inquiry command...27 Table 5-9 Test item on POWER general inquiry command...28 Table 5-10 Test item on PLUG INFO command...28 Table 5-11 Test item on Isochronous Connection control for the Input Plug...29 Table 5-12 Test item on Isochronous Connection control for the Output Plug...33 Table 5-13 Test item on other rule...34 Table 5-14 Test item on Configuration ROM...34 Table 5-15 Test item on Power-on command...35 Table 5-16 Test item on Power-off command...35 Table 5-17 Test item on control of SW1...35 Table 5-18 Test item on control of SW2...36 Copyright 2004, 1394 Trade Association. All rights reserved. Page 5
STB for Japanese Test Specification 1.0 TA Document 2002016, December 15, 2003 This page is left intentionally blank Page 6 Copyright 2004, 1394 Trade Association. All rights reserved.
TA Document 2002016, December 15, 2003 STB for Japanese Test Specification 1.0 1. Overview 1.1 Purpose This test specification defines the test items, which confirm that operations of a STB unit and functions of subunits in the STB unit conform to the IEEE1394 Interface Implementation Guideline, STB Device for Japanese Digital Broadcasting System 1.0 [R13]. (The document is referred as Implementation Guideline [R13] after this.) This specification describes specific AV/C command and responses; contents of each register and Configuration ROM before and after the test, including test conditions. Specific test environment such as hardware and software used in the test and procedures to confirm each test item will be defined separately in the Test Procedure. 1.2 Scope The scope of this test specification is contents described in the Implementation Guideline [R13]; implementation rules of Control, Status, Notify, General Inquiry and Specific Inquiry commands for each AV/C command; implementation rule of Isochronous Connection control; implementation rule of Configuration ROM. AV/C commands, which are not described in the Implementation Guideline [R13], are not within the scope of this test specification. Test of Isochronous Connection control limited to items, which can be confirmed by checking contents of transaction responses to plug registers (ipcr, opcr, ompr and impr) and change of values for BANDWIDTH_AVAILABLE register, CHANNELS_AVAILABLE_hi register and CHANNELS_AVAILABLE_lo register of Isochronous Resource Manager. Existence of Isochronous packet and other confirmations by bus analyzer are included. Copyright 2004, 1394 Trade Association. All rights reserved. Page 7
STB for Japanese Test Specification 1.0 TA Document 2002016, December 15, 2003 2. References The following standards contain provisions, which through reference in this document, constitute provisions of this standard. All the standards listed are normative references. Informative references are given in Annex A. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this standard are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. [R1] IEEE Std 1394-1995, Standard for a High Performance Serial Bus [R2] IEEE Std 1394a-2000, Standard for a High Performance Serial Bus Amendment 1 [R3] [R4] IEC 61883-1, Consumer audio/video equipment Digital interface Part 1: General IEC 61883-4, Consumer audio/video equipment Digital interface Part 4: MPEG2-TS [R5] 1394TA Document 1999035, AV/C Tuner Model and Command Set Version 2.0 [R6] 1394TA Document 1998005, AV/C Tuner Broadcasting System Specification Digital Video Broadcast (DVB), Version 1.0 [R7] 1394TA Document 1999003, Enhancements to the AV/C Tuner Broadcast System Specification Digital Video Broadcast (DVB) Version 1.0 [R8] 1394TA Document 1999027, Configuration ROM for AV/C Devices 1.0 [R9] 1394TA Document 1999031, AV/C Connection and Compatibility Management Specification 1.0 [R10] 1394TA Document 2001012, AV/C Digital Interface Command Set, General Specification Version 4.1 [R11] 1394TA Document 1999025, AV/C Descriptor Mechanism Specification Version 1.0 [R12] ARIB Standard for Receiver for Digital Broadcasting B21 3.1 [R13] 1394TA document 2002XXX, IEEE1394 Interface Implementation Guideline, STB Device for Japanese Digital Broadcasting System 1.0 Page 8 Copyright 2004, 1394 Trade Association. All rights reserved.
TA Document 2002016, December 15, 2003 STB for Japanese Test Specification 1.0 3. Definitions 3.1 Conformance levels 3.1.1 expected: A key word used to describe the behavior of the hardware or software in the design models assumed by this Specification. Other hardware and software design models may also be implemented. 3.1.2 may: A key word that indicates flexibility of choice with no implied preference. 3.1.3 shall: A key word indicating a mandatory requirement. Designers are required to implement all such mandatory requirements. 3.1.4 should: A key word indicating flexibility of choice with a strongly preferred alternative. Equivalent to the phrase is recommended. 3.1.5 reserved fields: A set of bits within a data structure that are defined in this specification as reserved, and are not otherwise used. Implementations of this specification shall zero these fields. Future revisions of this specification, however, may define their usage. 3.1.6 reserved values: A set of values for a field that are defined in this specification as reserved, and are not otherwise used. Implementations of this specification shall not generate these values for the field. Future revisions of this specification, however, may define their usage. The IEEE is investigating whether the may, shall, should and possibly expected terms will be formally defined by IEEE. If and when this occurs, draft editors should obtain their conformance definitions from the latest IEEE style document. 3.2 Glossary of terms 3.2.1 byte: Eight bits of data, used as a synonym for octet. 3.2.2 R Architecture: A convenient abbreviation of the following reference (see clause 2): ISO/IEC 13213 : 1994 [ANSI/IEEE Std 1212, 1994 Edition], Information Technology Microprocessor systems Control and Status Register (R) Architecture for Microcomputer Buses. 3.2.3 quadlet: Four bytes of data. 3.3 Acronyms and abbreviations AV/C IEEE Audio Video Control The Institute of Electrical and Electronics Engineers, Inc. Copyright 2004, 1394 Trade Association. All rights reserved. Page 9
STB for Japanese Test Specification 1.0 TA Document 2002016, December 15, 2003 4. Lists of Test Items 4.1 General 4.1.1 Test environment In this test specification, test environment is assumed that one controller, e.g. PC and one target device, e.g. STB device are connected with IEEE1394 cable. However, in some cases of tests, other devices may be connected to IEEE1394 bus. Test Operator Config ROM AV/C (Unit, Tuner) CMP CT (e.g. PC) IEEE1394 R Transaction Link Phy Target (STB) Figure 4-1 Test environment 4.2 Basic Policies Tests defined in this test specification are shown in the following sub-clauses. In tests defined in this test specification, a target is set in certain condition, test procedure is performed and its response is confirmed whether it is complied with specification written in the Implementation Guideline [R13]. Contents confirmed in each test are called test items and are shown in the following sub-clauses. 4.2.1 AV/C Command Implementation Test When commands are transmitted to a target under certain conditions, responses returned from the target are confirmed whether they are complied with specification written in the Implementation Guideline [R13]. Results of tests are evaluated by contents of AV/C responses returned from the target. Confirmation by visual observation is not performed. Contents confirmed in a test are called test items and are described in Chapter 5 Test Items. Test items describe that a target state is set up, contents of AV/C command that the controller sends to the target at the state and contents of AV/C responses expected to be returned from the target responding to the AV/C command. Page 10 Copyright 2004, 1394 Trade Association. All rights reserved.
TA Document 2002016, December 15, 2003 STB for Japanese Test Specification 1.0 Every condition setting should be performed by AV/C commands if AV/C commands may set up test condition. Whether condition setting is complete or not is confirmed by receiving STABLE response using Status command. Namely, test is performed on the condition that device state obtained by AV/C commands may reflect actual device state. 4.2.2 Isochronous Connection Control Implementation Test Setting condition of the other device for connection (only in case of necessity) and the target, i.e., STB for Digital Broadcasting System is defined before test. Each condition is set up and then, trigger to the state transition is initiated. Content of each plug register for the other device and the target (if used in test) after the transition is read by READ Transaction and is confirmed whether its contents correspond with contents described in the Implementation Guideline [R13]. 4.2.3 Configuration ROM Specification Implementation Test Read request packet is sent to address for Entry, directory and leaf, which are defined as mandatory implementation in Configuration ROM for AV/C Devices 1.0 (Reference [R8]). Results are determined by confirmation of response code (rcode) and contents of data contained in response packet, which is returned to the read request packet. 4.3 Evaluation Criteria 4.3.1 Evaluation Criteria for AV/C Command Implementation Test Passing status of each test item is checked by comparing contents of responses returned from the target with contents of responses expected in test items, and whether they correspond with each other. However when received commands alter status of the target, a command to confirm the altered status is additionally transmitted and contents of response to the command is checked at the same time. Such confirmation of results is applied to only the case of response with ACCEPTED and not applied to the case of response with NOT_IMPLEMENTED or REJECTED. When the command, which is described as may return REJECTED or ACCEPTED/REJECTED depends on device implementation in the guideline, is transmitted, response code may be REJECTED or ACCEPTED. 4.3.2 Evaluation Criteria for Isochronous Connection Control Implementation Test Passing status of each test item is checked by comparing contents of plug register returned from the other device or the target with contents of plug register expected in test items, and whether they correspond with each other. 4.3.3 Evaluation Criteria for Configuration ROM Implementation Test Data of Entry, which is defined as mandatory implementation in Configuration ROM for AV/C Devices 1.0 (Reference [R8]), and data of directory and leaf assigned by the entry are read by Read request packet. Contents of data are confirmed whether they comply with the specification. Copyright 2004, 1394 Trade Association. All rights reserved. Page 11
STB for Japanese Test Specification 1.0 TA Document 2002016, December 15, 2003 4.4 Descriptions of Test Contents 4.4.1 Grouping of Test Items Test items are divided into transmitting AV/C command and contents of responses, which is expected to be returned as response to the command. When the command, which is described as may return REJECTED or ACCEPTED/REJECTED depends on device implementation in the guideline, is transmitted, the test item is categorized as REJECTED response. 4.4.2 Structure of Test Contents 4.4.2.1 Contents Structure of AV/C Commands Implementation Test Items Each test item is comprised with the following contents. Kind of Commands Purpose Test Number Numbers to identify items (Detail will be explained at Division 4.4.4) Condition to set up operand Setting condition for transmitting operand of AV/C command Condition of Target Side State of the target device in Item in the Implementation Guideline Section number in the Implementation Guideline related to the test Contents of expected response data should be described on the assumption that the target device complies with AV/C General 4.1 (reference [R10]) and AV/C Descriptor (reference [R11]). 4.4.3 Setting range of test data Test data written in contents of command and contents of responses in test item are basically set up according to descriptions in the Implementation Guideline [R13]. However, depending on condition of setting, numbers of pattern combinations are too big to test combinations under whole conditions. It is necessary to make a small list of test data. Conditions to make a small list of test data are described as follows. 4.4.3.1 About commands in total (a) Kinds of Field Value If transmitting field value is altered at the test in which NOT_IMPLEMENTED and REJECTED return, the field value should be selected on the following condition Page 12 Not supported value in the Implementation Guideline [R13] All values, which are specified as not supported in the guideline should be confirmed. Copyright 2004, 1394 Trade Association. All rights reserved.
TA Document 2002016, December 15, 2003 STB for Japanese Test Specification 1.0 Not defined value One of the not defined values is selected. Any value may be selected. (b) Check of invalid command length Invalid command length should be checked in the two ways, i.e., 1 byte longer and 1 byte shorter than the normal command frame. 4.4.3.2 General Inquiry command (a) General Inquiry command should be transmitted only when control command (mandatory or option) is written in the guideline. For mandatory command, returning of IMPLEMENTED should be confirmed. (b) When control command is supported, General Inquiry command should be transmitted and returning of IMPLEMENTED response should be confirmed even for VENDOR DEPENDENT command. 4.4.3.3 Specific Inquiry command Specific Inquiry command should be transmitted changing operands of control command (mandatory or optional), which is described in the guideline and the following contents should be confirmed. Corresponding to the control command test in which other than NOT_IMPLEMENTED response returns, Specific Inquiry command with the similar contents is transmitted and returning of IMPLEMENTED response is confirmed. Corresponding to the control command test in which NOT_IMPLEMENTED response returns, Specific Inquiry command with the similar contents is transmitted and returning of NOT IMPLEMENTED response is confirmed. 4.4.3.4 In the case of test for optional command Person in charge of the above tests for General Inquiry command and Specific Inquiry command should input support/not support of the commands. Whether the test corresponds with the support list should be also confirmed. Copyright 2004, 1394 Trade Association. All rights reserved. Page 13
STB for Japanese Test Specification 1.0 TA Document 2002016, December 15, 2003 4.4.4 Test number Allocation of test numbers are different in implementation tests of AV/C command, Isochronous Connection Control, Configuration ROM specification, recommended specification for controller, Tuner Subunit and Signal Connection model in STB Unit. They are described separately as follows. 4.4.4.1 Test number for AV/C command implementation test This test items is combination of command transmitted from the controller and responses expected to be returned when the target receive the command. Test number in each test item is allocated based on the kind of the command and responses. Test number consists of four sections and each section has the following meaning. 1. 1. 1. 1 [Division 1] [Division 2] [Division 3] [Division 4] [Division 1] Value corresponded to opcode of command. See Table 4-1. [Division 2] Value corresponded to ctype of command. See Table 4-2. [Division 3] Value corresponded to response code of response. See Table 4-3. [Division 4] Consecutive number categorized in Division 1 to Division 3 for each condition Table 4-1 Value of test number [Division 1] in AV/C command implementation test Value Opcode 1 CONNECT 2 CONNECTIONS 3 SUBUNIT INFO 4 UNIT INFO 5 POWER 6 PLUG INFO Table 4-2 Value of test number [Division 2] in AV/C command implementation test Value Ctype 1 Control 2 Status 3 Specific Inquiry 4 Notify 5 General Inquiry Page 14 Copyright 2004, 1394 Trade Association. All rights reserved.
TA Document 2002016, December 15, 2003 STB for Japanese Test Specification 1.0 Table 4-3 Value of test number [Division 3] in AV/C command implementation test Value Response code 1 NOT IMPLEMENTED 2 ACCEPTED 3 REJECTED 4 IN TRANSITION 5 IMPLEMENTED/STABLE 6 CHANGED 7 INTERIM (Example) In the case of test number 1.2.1.1 [Division 1] 1.CONNECT command [Division 2] 2 status command [Division 3] 1 NOT IMPLEMENTED [Division 4] 1 Consecutive number 1 It means test item in which Connect Status command is transmitted to the STB device and NOT IMPLEMENTED response returns. 4.4.4.2 Test number for Isochronous Connection control implementation test The test item is divided into test for input plug, test for output plug and test for other rule in Isochronous Connection control implementation test. The test for input plug is divided based on each condition of state transition written in the IEEE1394 Interface Implementation Guideline, STB Device for Japanese Digital Broadcasting System (Reference [R13]). Test number is expressed state number before/after transition in the state transition and consecutive number in the same pattern of state transition. (Example) In the case of state transition S2 S3 and consecutive number 1 in test for input plug has test number 7.2.3.1 Test number consists of four sections and each section has the following meaning. 1. 1. 1. 1 [Division 1] [Division 2] [Division 3] [Division 4] [Division 1] Value for plug under test. See Table 4.4. [Division 2] Value for state before transition. See Table 4.5. [Division 3] Value for state after transition. See Table 4.5. [Division 4] Consecutive number categorized in Division 1 to Division 3 for each condition Copyright 2004, 1394 Trade Association. All rights reserved. Page 15
STB for Japanese Test Specification 1.0 TA Document 2002016, December 15, 2003 Table 4-4 Value of test number [Division 1] in Isochronous Connection control implementation test Value Plug 7 Input plug 8 Output plug 9 Other rule Table 4-5 Value of test number [Division 2], [Division 3] in test for input plug implementation test State number State before/after transition 0 No connection exists; no 1394 input action undertaken 1 2 3 With input (1394) device selected; undertake 1394 input action. State where point-to-point connection established by other device. Because STB is not in 1394 input state, no actual 1394 input action is undertaken. In the state after 1394 input is performed, undertake 1394 input action. Test number [Division 2] and [Division 3] of test for output plug and test for other rule have fixed value 1. 4.4.4.3 Test number for Configuration ROM implementation test This test item has only Configuration ROM implementation test. Test number consists of four sections and each section has the following meaning. 1. 1. 1. 1 [Division 1] [Division 2] [Division 3] [Division 4] [Division 1] Value for Configuration ROM implementation test. See Table 4-6. [Division 2] Value for device recognition/status inquiry of STB for Digital Broadcasting System. See Table 4-7. [Division 3] Fixed to value = 1 [Division 4] Consecutive number categorized in Division 1 to Division 2 for each condition Table 4-6 Value of test number [Division 1] in Configuration ROM implementation test Value Description 10 Value for Configuration ROM implementation test Page 16 Copyright 2004, 1394 Trade Association. All rights reserved.
TA Document 2002016, December 15, 2003 STB for Japanese Test Specification 1.0 Table 4-7 Value of test number [Division 2] in Configuration ROM implementation test Number Description 1 Test for Bus_info_block 2 Test for Vendor_ID of Root directory 3 Test for Model_ID of Root directory 4 Test for Node_capabilities of Root directory 5 Test for Unit directory of Root directory 4.4.4.4 Test number for Power Command addressed to Tuner Subunit implementation test Test number in this test item is allocated according to the rule in section 5.1 POWER control command of the Implementation Guideline as follows. Test number consists of four sections and each section has meaning as follows. 1. 1. 1. 1 [Division 1] [Division 2] [Division 3] [Division 4] [Division 1] Value for POWER command addressed to Tuner Subunit implementation test. See Table 4-8. [Division 2] Value for change of Power status. See Table4-9. [Division 3] Fixed to value = 1 [Division 4] Consecutive number categorized in Division 1 to Division 2 for each condition Table 4-8 Value of test number [Division 1] in POWER command addressed to Tuner Subunit implementation test 11 Value Description Value for Power Command addressed to Tuner Subunit implementation test Table 4-9 Value of test number [Division 2] in POWER command addressed to Tuner Subunit implementation test Number Description 1 From Power off to Power on 2 From Power on to Power off Copyright 2004, 1394 Trade Association. All rights reserved. Page 17
STB for Japanese Test Specification 1.0 TA Document 2002016, December 15, 2003 4.4.4.5 Test number for Unit internal signal connection model implementation test Test number in this test item is allocated according to behavior of SW1 and behavior of SW2 in section 7.1 Internal signal connection of the Implementation Guideline as follows. Test number consists of four sections and each section has meaning as follows. 1. 1. 1. 1 [Division 1] [Division 2] [Division 3] [Division 4] [Division 1] Value for Unit internal signal connection model implementation test. See Table 4-10. [Division 2] Value for behavior of SW1or behavior of SW2. See Table 4-11 [Division 3] Fixed to value = 1 [Division 4] Consecutive number categorized in Division 1 and Division 2 for each condition Table 4-10 Value of test number [Division 1] in Unit internal signal connection implementation test 12 Value Description Value for Unit internal signal connection model implementation test Table 4-11 Value of test number [Division 2] in Unit internal signal connection implementation test Number Description 1 Behavior of SW1 2 Behavior of SW2 Page 18 Copyright 2004, 1394 Trade Association. All rights reserved.
TA Document 2002016, December 15, 2003 STB for Japanese Test Specification 1.0 5. Test Items 5.1 Tuner Subunit implementation test Tuner Subunit implementation test is described in Supplement to Test Specification for IEEE1394 Interface Implementation Guideline Tuner Subunit. Test based on additional rule in the Implementation Guideline [R13] should be performed. (Refer to section 5.6) 5.2 Bulletin Board Subunit implementation test Bulletin board subunit implementation test is described in Supplement to Test Specification for IEEE1394 Interface Implementation Guideline Bulletin Board Subunit. (Resource Schedule Board) 5.3 Implementation test items of AV/C to Unit 5.3.1 CONNECT command 5.3.1.1 CONNECT status command Table 5-1 Test item on CONNECT command Response Test number Contents of test Guideline Reference 1.2.1.1 NOT IMPLEMENTED 1.2.1.2 STABLE 1.2.5.1 [Purpose] To confirm that a response frame of NOT_IMPLEMENTED is returned when CONNECT status command with non-supported operand is sent. [Condition to set up operand] To set up not supported operand. [Condition of the target] Arbitrary state. [Purpose] To confirm that a response frame of NOT_IMPLEMENTED is returned when command length for CONNECT status command is not correct. [Condition to set up operand] To set up command frame with invalid word length. [Condition of the target] Arbitrary state. [Purpose] To confirm that a response frame of STABLE is returned and input state of the target and the contents of response correspond when CONNECT status command is sent. [Condition to set up operand] To inquire source plug by specifying destination plug. [Condition of the target] In case of receiving digital broadcasting signal and not Digital/Analog-individual-outputmode 7.2.2.1 7.2.2.1 7.2.2.1 Copyright 2004, 1394 Trade Association. All rights reserved. Page 19
STB for Japanese Test Specification 1.0 TA Document 2002016, December 15, 2003 1.2.5.2 1.2.5.3 1.2.5.4 [Purpose] To confirm that a response frame of STABLE is returned and input state of the target and the contents of response correspond when CONNECT status command is sent. [Condition to set up operand] To set up value to comply with the Implementation Guideline [R13]. [Condition of the target] In case of receiving digital broadcasting signal and Digital/Analog-individual-output-mode. [Remarks] This test is not executed when the target does not support digital/analog-separate-operation-mode. [Purpose] To confirm that a response frame of STABLE is returned and input state of the target and the contents of response correspond when CONNECT status command is sent. [Condition to set up operand] To inquire source plug by specifying destination plug. [Condition of the target] In case of receiving the stream from IEEE1394 bus and not using the demux function of Tuner Subunit. [Remarks] This test is not executed when the target with digital/analog-separate-operation-mode has not the state described in the [condition of the target]. 7.2.2.1 7.2.2.1 [Purpose] To confirm that a response frame of STABLE is 7.2.2.1 returned and input state of the target and the contents of response correspond when CONNECT status command is sent. [Condition to set up operand] To inquire source plug by specifying destination plug. [Condition of the target] In case of receiving the stream from IEEE1394 bus and using the demux function of Tuner Subunit. [Remarks] This test is not executed when the target does not support demux function of Tuner Subunit and the target with digital/analog-separate-operation-mode has not the state described in the [condition of the target]. Page 20 Copyright 2004, 1394 Trade Association. All rights reserved.
TA Document 2002016, December 15, 2003 STB for Japanese Test Specification 1.0 5.3.2 CONNECTIONS command 5.3.2.1 CONNECTIONS status command Table 5-2 Test item on CONNECTIONS command Response Test number Contents of test Guideline Reference NOT IMPLEMENTED STABLE 2.2.1.1 2.2.1.2 2.2.5.1 2.2.5.2 [Purpose] To confirm that a response frame of NOT_IMPLEMENTED is returned when CONNECT status command setting a value other than 0xFF in operand[0] is sent. [Condition to set up operand] To set up not supported operand. [Condition of the target] Arbitrary state. [Remarks] This test shall be executed regardless of the target s support [of CONNECTIONS status command. [Purpose] To confirm that a response frame of NOT_IMPLEMENTED is returned when command length for CONNECTIONS status command is not correct. [Condition to set up operand] To set up command frame with invalid word length. [Condition of the target] Arbitrary state. [Remarks] This test shall be executed regardless of the target s support [of CONNECTIONS status command. [Purpose] To confirm that a response frame of STABLE is returned when CONNECTIONS status command is sent. [Condition to set up operand] To set up value to comply with the Implementation Guideline [R13]. [Condition of the target] In case of receiving digital broadcasting signal and not using Digital/Analog-individualoutput-mode. [Remarks] This test is not executed when the target does not support CONNECTIONS status command. [Purpose] To confirm that a response frame of STABLE is returned when CONNECTIONS status command is sent. [Condition to set up operand] To set up value to comply with the Implementation Guideline [R13]. [Condition of the target] In case of receiving digital broadcasting signal and using Digital/Analog-individual-outputmode. [Remarks] This test is not executed when the target does not support CONNECTIONS status command and This test is not executed when the target does not support digital/analog-separate-operation-mode. 7.2.2.2 7.2.2.2 7.2.2.2 7.2.2.2 Copyright 2004, 1394 Trade Association. All rights reserved. Page 21
STB for Japanese Test Specification 1.0 TA Document 2002016, December 15, 2003 2.2.5.3 2.2.5.4 [Purpose] To confirm that a response frame of STABLE is returned when CONNECTIONS status command is sent. [Condition to set up operand] To set up value to comply with the Implementation Guideline [R13]. [Condition of the target] In case of receiving the stream from IEEE1394 bus and not using the demux function of Tuner Subunit. [Remarks] This test is not executed when target does not support CONNECTIONS status command. This test is not executed when the target with digital/analogseparate-operation-mode has not the state described in the [condition of the target]. [Purpose] To confirm that a response frame of STABLE is returned when CONNECTIONS status command is sent. [Condition to set up operand] To set up value to comply with the Implementation Guideline [R13]. [Condition of the target] In case of receiving the stream from IEEE1394 bus and using the demux function of Tuner Subunit. [Remarks] This test is not executed when the target does not support CONNECTIONS status command. This test is not executed when demux function of Tuner Subunit. This test is not executed when the target with digital/analogseparate-operation-mode has not the state described in the [condition of the target]. 7.2.2.2 7.2.2.2 5.3.3 SUBUNIT INFO command 5.3.3.1 SUBUNIT INFO status command Table 5-3 Test item on SUBUNIT INFO command Response Test number Contents of test Guideline Reference NOT IMPLEMENTED 3.2.1.1 3.2.1.2 [Purpose] To confirm that a response frame of NOT_IMPLEMENTED is returned when SUBUNIT INFO status command with non-supported operand is sent. [Condition to set up operand] To set up not supported operand. [Condition of the target] Arbitrary state. [Purpose] To confirm that a response frame of NOT_IMPLEMENTED is returned when command length for SUBUNIT INFO status command is not correct. [Condition to set up operand] To set up command frame with invalid word length. [Condition of the target] Arbitrary state. 7.2.2.3 7.2.2.3 Page 22 Copyright 2004, 1394 Trade Association. All rights reserved.
TA Document 2002016, December 15, 2003 STB for Japanese Test Specification 1.0 STABLE 3.2.5.1 [Purpose] To confirm that a response frame of STABLE is returned when SUBUNIT INFO status command is sent. [Condition to set up operand] To set up value to comply with the Implementation Guideline [R13]. [Condition of the target] Arbitrary state. 7.2.2.3 5.3.4 UNIT INFO command 5.3.4.1 UNIT INFO status command Table 5-4 Test item on UNIT INFO command Response Test number Contents of test Guideline Reference 4.2.1.1 NOT IMPLEMENTED 4.2.1.2 STABLE 4.2.5.1 [Purpose] To confirm that a response frame of NOT_IMPLEMENTED is returned when UNIT INFO status command with non-supported operand is sent. [Condition to set up operand] To set up not supported operand. [Condition of the target] Arbitrary state. [Purpose] To confirm that a response frame of NOT_IMPLEMENTED is returned when command length for UNIT INFO status command is not correct. [Condition to set up operand] To set up command frame with invalid word length. [Condition of the target] Arbitrary state. [Purpose] To confirm that a response frame of STABLE is returned when UNIT INFO status command is sent. [Condition to set up operand] To set up value to comply with the Implementation Guideline [R13]. [Condition of the target] Arbitrary state. 7.2.2.4 7.2.2.4 7.2.2.4 Copyright 2004, 1394 Trade Association. All rights reserved. Page 23
STB for Japanese Test Specification 1.0 TA Document 2002016, December 15, 2003 5.3.5 POWER command 5.3.5.1 POWER control command Table 5-5 Test item on POWER control command Response Test number Contents of test Guideline Reference NOT IMPLEMENTED ACCEPTED 5.1.1.1 5.1.1.2 5.1.2.1 5.1.2.2 [Purpose] To confirm that a response frame of NOT_IMPLEMENTED is returned when POWER control command with non-supported operand is sent. [Condition to set up operand] To set up not supported operand. [Condition of the target] Arbitrary state. [Purpose] To confirm that a response frame of NOT_IMPLEMENTED is returned when command length for POWER control command is not correct. [Condition to set up operand] To set up command frame with invalid word length. [Condition of the target] Arbitrary state. [Purpose] To confirm that a response frame of ACCEPTED is returned and to be the requested Power status when POWER control command to request Power on is sent. This test is executed for state of Power on and Power off. [Condition to set up operand] To set up value to comply with the Implementation Guideline [R13]. (To request Power on) [Condition of the target] To be able to control power. Power on/power off. [Purpose] To confirm that a response frame of ACCEPTED is returned and to be the requested Power status when POWER control command to request Power off is sent. This test is executed for state of Power on and Power off. [Condition to set up operand] To set up value to comply with the Implementation Guideline [R13]. (To request Power off) [Condition of the target] To be able to control power. Power on/power off. 7.2.2.5 7.2.2.5 7.2.2.5 7.2.2.5 Page 24 Copyright 2004, 1394 Trade Association. All rights reserved.
TA Document 2002016, December 15, 2003 STB for Japanese Test Specification 1.0 5.3.5.2 POWER status command Table 5-6 Test item on POWER status command Response Test number Contents of test Guideline Reference 5.2.1.1 NOT IMPLEMENTED 5.2.1.2 5.2.4.1 IN TRANSITION 5.2.4.2 STABLE 5.2.5.1 [Purpose] To confirm that a response frame of NOT_IMPLEMENTED is returned when POWER status command with non-supported operand is sent. [Condition to set up operand] To set up not supported operand. [Condition of the target] Arbitrary state. [Purpose] To confirm that a response frame of NOT_IMPLEMENTED is returned when command length for POWER status command is not correct. [Condition to set up operand] To set up command frame with invalid word length. [Condition of the target] Arbitrary state. [Purpose] To confirm that a response frame of IN_TRANSITION is returned when POWER control command to request Power on is sent and POWER status command is sent during transition of Power state after receiving the corresponding ACCEPTED response frame. (To confirm a response frame of STABLE is returned for those devices, which do not support IN_TRANSITION.) [Condition to set up operand] To set up command frame with invalid word length. [Condition of the target] Arbitrary state. [Purpose] To confirm that a response frame of IN_TRANSITION is returned when POWER control command to request Power off is sent and POWER status command is sent during transition of Power state after receiving the corresponding ACCEPTED response frame. (To confirm a response frame of STABLE is returned for those devices, which do not support IN_TRANSITION.) [Condition to set up operand] To set up value to comply with the Implementation Guideline [R13]. (To request Power off) [Condition of the target] To be able to control power. Power off state. [Purpose] To confirm that a response frame of STABLE is returned when POWER status command is sent. This test is executed to set the target in the state of Power on and Power off. [Condition to set up operand] To set up value to comply with the Implementation Guideline [R13]. [Condition of the target] To be able to control power. Power on state. 7.2.2.5 7.2.2.5 7.2.2.5 7.2.2.5 7.2.2.5 Copyright 2004, 1394 Trade Association. All rights reserved. Page 25
STB for Japanese Test Specification 1.0 TA Document 2002016, December 15, 2003 5.3.5.3 POWER notify command Table 5-7 Test item on POWER notify command Response Test number Contents of test Guideline Reference NOT IMPLEMENTED REJECTED 5.4.1.1 5.4.1.2 5.4.3.1 5.4.3.2 [Purpose] To confirm that a response frame of NOT_IMPLEMENTED is returned when POWER notify command with non-supported operand is sent. [Condition to set up operand] To set up not supported operand. [Condition of the target] Arbitrary state. [Remarks] This test shall be executed regardless of the target s support of POWER notify command. [Purpose] To confirm that a response frame of NOT_IMPLEMENTED is returned when command length for POWER notify command is not correct. [Condition to set up operand] To set up command frame with invalid word length. [Condition of the target] Arbitrary state. [Remarks] This test shall be executed regardless of the target s support of POWER notify command. 7.2.2.5 7.2.2.5 [Purpose] POWER notify commands are already received from 7.2.2.5 three controllers, which can receive POWER notify command, and additional POWER notify commands sent. To confirm that a response frame of REJECTED is returned when number of controllers, which the target supports, is three. To confirm that INTERIM response frame is returned when number of controllers is more than 4. [Condition to set up operand] To set up value to comply with the Implementation Guideline [R13]. [Condition of the target] Already accepted the notification requests from three controllers (i.e., minimum number of controllers, which can receive POWER notify command specified in the Guideline = 3). [Remarks] It is necessary to prepare maximum number of controllers to set the state where the target can receive POWER notify command from maximum number of controllers, which can receive POWER notify command. This test is not executed when the target does not support POWER notify command. [Purpose] To confirm that a response frame of REJECTED is returned when POWER notify command is sent to the target, which is already received POWER notify command from the same controller. [Condition to set up operand] To set up value to comply with the Implementation Guideline [R13]. [Condition of the target] Already accepted the pending from the same controller that issues the command. [Remarks] This test is not executed when the target does not support POWER notify command. 7.2.2.5 Page 26 Copyright 2004, 1394 Trade Association. All rights reserved.
TA Document 2002016, December 15, 2003 STB for Japanese Test Specification 1.0 CHANGED after INTERIM 5.4.7.1 5.4.7.2 [Purpose] To confirm that a response frame of INTERIM with 60 16 (Power off state) in power_state field is returned when the Power status command is sent. Then to confirm that a response frame of CHANGED with 70 16 (Power on state) in power_state field is returned when the target is changed to Power on state. [Condition to set up operand] To set up value to comply with the Implementation Guideline [R13]. [Condition of the target] To be Power off state and be able to receive POWER notify command. [Remarks] This test is not executed when the target does not support POWER notify command. [Purpose] To confirm that a response frame of INTERIM with 70 16 (Power on state) in power_state field is returned when the Power status command is sent. Then to confirm that a response frame of CHANGED with 60 16 (Power off state) in power_state field is returned when the target is changed to Power off state. [Condition to set up operand] To set up value to comply with the Implementation Guideline [R13]. [Condition of the target] To be Power on state and be able to receive POWER notify command. [Remarks] This test is not executed when the target does not support POWER notify command. 7.2.2.5 7.2.2.5 5.3.5.4 POWER specific inquiry command Table 5-8 Test item on POWER specific inquiry command Response Test number Contents of test Guideline Reference NOT_ IMPLEMENTED 5.3.1.1 5.3.1.2 IMPLEMENTED 5.3.5.1 [Purpose] To confirm that a response frame of NOT_IMPLEMENTED is returned when POWER specific inquiry command with non-supported operand is sent. [Condition to set up operand] To set up not supported operand. [Condition of the target] Arbitrary state. [Purpose] To confirm that a response frame of NOT_IMPLEMENTED is returned when command length for POWER specific inquiry command is not correct. [Condition to set up operand] To set up command frame with invalid word length. [Condition of the target] Arbitrary state. 7.2.1 7.2.1 [Purpose] To confirm that a response frame of IMPLEMENTED 7.2.1 is returned when POWER specific inquiry command is sent to request Power on request or Power off request. [Condition to set up operand] To set up value to comply with the Implementation Guideline [R13]. [Condition of the target] Arbitrary state. Copyright 2004, 1394 Trade Association. All rights reserved. Page 27
STB for Japanese Test Specification 1.0 TA Document 2002016, December 15, 2003 5.3.5.5 POWER general inquiry command Table 5-9 Test item on POWER general inquiry command Response Test number Contents of test Guideline Reference IMPLEMENTED 5.5.5.1 [Purpose] To confirm that a response frame of IMPLEMENTED is returned when POWER general inquiry command is sent. [Condition to set up operand] To set up value to comply with the Implementation Guideline [R13]. [Condition of the target] Arbitrary state. 7.2.1 5.3.6 PLUG INFO command 5.3.6.1 PLUG INFO status command Table 5-10 Test item on PLUG INFO command Response Test number Contents of test Guideline Reference 6.2.1.1 NOT IMPLEMENTED 6.2.1.2 STABLE 6.2.5.1 [Purpose] To confirm that a response frame of NOT_IMPLEMENTED is returned when PLUG INFO status command with non-supported operand is sent. [Condition to set up operand] To set up not supported operand. [Condition of the target] Arbitrary state. [Purpose] To confirm that a response frame of NOT_IMPLEMENTED is returned when command length for PLUG INFO status command is not correct. [Condition to set up operand] To set up command frame with invalid word length. [Condition of the target] Arbitrary state. [Purpose] To confirm that a response frame of STABLE is returned when PLUG INFO status command defined in the Implementation Guideline [R13] is sent. [Condition to set up operand] To set up value to comply with the Implementation Guideline [R13]. [Condition of the target] Arbitrary state. 7.2.2.6 7.2.2.6 7.2.2.6 Page 28 Copyright 2004, 1394 Trade Association. All rights reserved.
TA Document 2002016, December 15, 2003 STB for Japanese Test Specification 1.0 5.4 Implementation test items for control of Isochronous Connection 5.4.1 Implementation test items for control of Isochronous Connection for the Input Plug Table 5-11 Test item on Isochronous Connection control for the Input Plug Transition to be confirmed Test number Contents of test Guideline Reference S0 -> S1(1) 7.0.1.1 S0 -> S1(2) 7.0.1.2 S0 -> S1(3) 7.0.1.3 [Purpose] To establish P-to-P connection when Input-selection is enabled and to confirm to use the channel 32 when the channel 32 is used. [Condition of the other device] opcr is UNCONNECTED. [Condition of the target] ipcr is UNCONNECTED and the target is in other than 1394 input state. [Remarks] The bandwidth for 1394 input selection is calculated by BWU equation described at Section 7.7 of IEC 61883-1. This test is executed only for the target, which uses channel number in ascending order from the 32 channel for establishment of P-to-P Connection in the case that the input device selection function is enabled. [Purpose] To establish P-to-P connection when Input-selection is enabled and to confirm to use the channel 33 when the channel 32 is used. [Condition of the other device] opcr is UNCONNECTED. [Condition of the target] ipcr is UNCONNECTED and the target is in other than 1394 input state. [Remarks] This test is executed only for the target, which uses channel number in ascending order from the 32 channel for establishment of P-to-P Connection in the case that the input device selection function is enabled. [Purpose] To establish P-to-P connection when Input-selection is enabled and to confirm to use the channel 34 when the channel 32 and 33 are used. [Condition of the other device] opcr is UNCONNECTED. [Condition of the target] ipcr is UNCONNECTED and the target is in other than 1394 input state. [Remarks] This test is executed only for the target, which uses channel number in ascending order from the 32 channel for establishment of P-to-P Connection in the case that the input device selection function is enabled. 7.4.1 7.4.1 7.4.1 Copyright 2004, 1394 Trade Association. All rights reserved. Page 29