Uni-Directional Digital Cable Products Supporting m-card m-udcp device Acceptance Test Plan tp-atp-m-udcp-i05-20080304 issued notice This Test Plan document is furnished by Cable Television Laboratories, Inc



Download 3.36 Mb.
Page16/31
Date28.01.2017
Size3.36 Mb.
#10091
1   ...   12   13   14   15   16   17   18   19   ...   31

4.4Extended Channel Support

4.4.1Host Extended Channel Link Layer Test


This test verifies that the Host can successfully implement link layer protocols for transferring data between the Host and the CableCARD device. The test also verifies that the Host has properly implemented the extxtended channel APDU’s to open a data flow of type MPEG sections, IP flow and a DSG flow.

Equipment: Host (DUT), HPNX PRO Test tool.


Procedure:

Step

Procedure

Pass/Fail

PICS



Bring up the HPNX Pro software on the given PC. Verify that the PC and HPNX Pro are on the same isolated network.

N/A






Note the last 4 (mac address) digits of HPNx Pro you are using.

(Information is on the back side of card)



N/A






Under the Device tab, enter the 4 digits in the blank space labeled “Your HPNx Pro ID”.

N/A






Insert the HPNX Pro extender card into DUT. From the HPNx Pro trace window, check that the status of the HPNx Pro goes ready and the resource manager opens its session.

N/A






Right click on the Trace window to select SPDU and Payload for full vision of all layers.

N/A






Select “Extended channel” tab.

Depending on the DUT you may have to change the resource version of the HPNX PRO to match that of the DUT.

(To do this, right click on the extended channel slot session. Select “Change resource version”. In the explorer user prompt window enter the correct resource version needed to match the DUT). Click OK.

On the “Extended channel” tab press the Play button to open the extended channel resource.



N/A






From HPNx Pro trace window, verify that the DUT sends a open_session response on resource “extended channel”






ExchF.1 ExchF.24

ExchF.39


ExchF.40



Verify that the DUT sends a new_flow_req() from extended channel with service_type = MPEG_section. (PID = 0x1FFC).




ExchF.2

ExchF.4


ExchF.23



Note that the HPNX PRO Test tool sends back new_flow_cnf() from extended channel granting the flow.

Note: the Flow_Id (0x_____)



N/A






Verify no error condition occurs on the DUT.




ExchF.27

ExchF.28


Exchf.29



Right Click on the “Extended channel” tab.

Select “Add Session Slot”

Depending on the DUT you may have to change the resource version of the HPNX PRO to match that of the DUT.

(To do this, right click on the extended channel slot session. Select “Change resource version”. In the explorer user prompt window enter the correct resource version needed to match the DUT). Click OK.

On the “Extended channel” tab press the Play button to open the extended channel resource.


N/A






Verify that the DUT denies the request. The Host should not respond to the request of the flow type.




ExchF.4 ExchF.30




Delete the 2nd session on the HPNx Pro.

N/A






Using the HPNX PRO Test tool, click on the lost_flow_ind button and enter the flow_id recorded.

Click Send to send a lost_flow_ind() to the DUT.



N/A






Verify that the DUT accepts the lost_flow_ind for the right flow_id and includes a reason field.




ExchF.13

ExchF.14 ExchF.32 ExchF.33





Verify that the DUT acknowledges by sending a lost_flow_cnf() PDU.




ExchF.15



4.4.2SCTE 65 Service Information Delivered OOB Profiles 1-6


This test verifies different profiles of SI tables delivered via an out-of-band path to support service selection and navigation by digital cable set-top boxes and other “digital cable-ready” devices. The SI tables defined in this test procedure are formatted in accordance with the Program Specific Information (PSI) data structures and constructed in accordance with SCTE65.

Equipment: DUT, HPNx Pro Test tool, SI files (Profile1.hex, Profile2thru3.hex, Profile 4.hex, Profile 5.hex, and Profile 6.hex).

Note: The attached files need to be copied to the computer running the HPNX application.



Procedure:

Step#

Procedure

Pass/Fail

PICS Item



Bring up the HPNX Pro software on the given PC. Verify that the PC and HPNX Pro are on the same isolated network.

N/A






Note the last 4 (mac address) digits of HPNX Pro you are using.

(Information is on the back side of card)



N/A






Under the Device tab, enter the 4 digits in the blank space labeled “Your HPNX Pro ID”

N/A






Insert the HPNX Pro extender card into the DUT. From the HPNx Pro trace window, check that the status of the HPNx Pro goes ready and the resource manager opens its session.

N/A






Right click on the Trace window to select SPDU and Payload for full vision of all layers.

N/A






Select the “Extended Channel” tab. Depending on the DUT you may have to change the resource version of the HPNX Pro to match that of the DUT. To do this, right click on the extended channel session slot. Select “Change resource version”. In the explorer user prompt window enter the correct resource version needed to match the DUT. Click OK.

On the “Extended Channel” tab press the Play button to open the Extended Channel resource.



N/A






Verify that the DUT establishes a session to the Extended Channel and requests a service_type = MPEG_section with a PID = 0x1FFC.

S [649:19:06.023] open_session_request from Extended Channel

[ 91 04 00 A0 00 43 ]

S [649:19:06.123] open_session_response on resource Extended Channel, Status = 0x00, SessionNb = 2

[ 92 07 00 00 A0 00 43 00 02 ]

A [649:19:06.313] New_flow_req to Extended Channel (note: description version and opened version differs)

[ 9F 8E 00 03 00 FF FC ]

service_type = MPEG_section [0x00]



MPEG_section_parameters

PID = 0x1FFC

A [649:19:06.383] New_flow_cnf from Extended Channel

[ 9F 8E 01 06 00 05 00 00 01 00]

status_field = request granted [0x00]

flows_remaining = 0x05



flow_info

FLOW_ID = 0x000001

service_type = MPEG_section [0x00]

Note: Note the FLOW_ID assigned by the DUT in the New_flow_cnf. In this example, the FLOW_ID assigned to the PID 0x1FFC MPEG_section flow is 0x000001.


N/A






Under the “Extended channel” tab, expand the Flow Feed button.

N/A






Click the “Browse” button and select “Profile1.hex” file. Click “OPEN”.

N/A






Enter the FLOW_ID that was noted in step 8 into the Flow ID window and click send.

In this step immediately after you click send, the following tables will be sent to the DUT.



  • Network Information Table

    • Network Information Table with a Carrier Definition table subtype.

    • Network Information Table with a Modulation Mode table subtype.

  • Short Form Virtual Channel Table

    • Short Form Virtual Channel Table with Defined Channel Map subtype.

    • Short Form Virtual Channel Table with Virtual Channel Map subtype 1.

    • Short Form Virtual Channel Table with Optional Inverse Channel Map.

  • System Time Table.

  • Network Text Table

    • Network Text Table with optional Source Name Sub-table

    • Network Text Table with optional Source Name Sub-table.

Note: It is imperative that the correct Flow id be used in order for this test to function properly.

N/A






On the DUT using the channel up and down buttons or the remote control, verify that the channel map has been successfully loaded and that the DUT can navigate the channel map.

Verify that navigation occurs with at least one or more of the SCTE65 profiles. Record if profile 1 is supported.



Note: Refer to CableLabs site, http://visitors.cablelabs.com/interopweb for current HE channel maps.




ExchF.38

ExchF.56


FDCP.14




Under the “Flow Feed” function, click the “Browse” button. Select the “Profile2thru3.hex” file and click “OPEN”.

N/A






Enter the FLOW_ID that was noted in step 8 into the Flow ID window and click send.

In this step immediately after you click send, the following tables will be sent to the DUT.



  • Network Information Table.

    • Network Information Table with a Carrier Definition table subtype.

    • Network Information Table with a Modulation Mode table subtype.

  • Short Form Virtual Channel Table.

    • Short Form Virtual Channel Table with Defined Channel Map subtype.

    • Short Form Virtual Channel Table with Virtual Channel Map subtype 1.

    • Short Form Virtual Channel Table with Virtual Channel Map subtype 2.

    • Short Form Virtual Channel Table with Optional Inverse Channel Map.

  • System Time Table

  • Network Text Table

    • Network Text Table with optional Source Name Sub-table.

Note: It is imperative that the correct Flow id be used in order for this test to function properly.

N/A






On the DUT using the channel up and down buttons or the remote control, verify that the channel map has been successfully loaded and that the DUT can navigate the channel map.

Verify that navigation occurs with at least one or more of the SCTE65 profiles. Record if profiles 2 and 3 are supported.



Note: Reference step 12 for channel map.




ExchF.38

ExchF.56





Using whatever means available clear the channel map from the DUT. Example of this would be on a Motorola DUT press and hold the “Power” and “select” buttons on the front panel. While depressing these buttons unplug the DUT and allow the front panel to flash at least 3 times and release the buttons. Power on the DUT and verify that there is no channel map loaded. This can be accomplished by channel up down operations.

N/A






Repeat steps 1 through 9.

N/A






Under the “Flow Feed” function, click the “Browse” button. Select the “Profile4.hex” file and click “OPEN”.

N/A






Enter the FLOW_ID that was noted in step 8 into the Flow ID window and click send.

In this step immediately after you click send, the following tables will be sent to the DUT.



  • Network Information Table.

    • Network Information Table with a Carrier Definition table subtype.

    • Network Information Table with a Modulation Mode table subtype.

      • Short Form Virtual Channel Table.

        • Short Form Virtual Channel Table with Defined Channel Map subtype.

        • Short Form Virtual Channel Table with Virtual Channel Map subtype 1.

        • Short Form Virtual Channel Table with Virtual Channel Map subtype 2.

        • Short Form Virtual Channel Table with Optional Inverse Channel Map.

          • System Time Table.

          • Network Text Table.

            • Network Text Table with optional Source Name Sub-table.

              • Master Guide Table.

Note: It is imperative that the correct Flow id be used in order for this test to function properly.

N/A






On the DUT using the channel up and down buttons or the remote control, verify that the channel map has been successfully loaded and that the DUT can navigate the channel map.

Verify that navigation occurs with at least one or more of the SCTE65 profiles. Record if profile 4 is supported.



Note: Reference step 12 for channel map.




ExchF.38

ExchF.56


VirtChan.1



Using whatever means available clear the channel map from the DUT. Example of this would be on a Motorola DUT press and hold the “Power” and “select” buttons on the front panel. While depressing these buttons unplug the DUT and allow the front panel to flash at least 3 times and release the buttons. Power on the DUT and verify that there is no channel map loaded. This can be accomplished by channel up down operations.

N/A






Repeat steps 1 through 9.

N/A






Under the “Flow Feed” function, click the “Browse” button. Select the “Profile5.hex” file and click “OPEN”.

N/A






Enter the FLOW_ID that was noted in step 8 into the Flow ID window and click send.

In this step immediately after you click send, the following tables will be sent to the DUT.



  • Network Information Table.

    • Network Information Table with a Carrier Definition table subtype.

    • Network Information Table with a Modulation Mode table subtype

      • Short Form Virtual Channel Table.

        • Short Form Virtual Channel Table with Defined Channel Map subtype.

        • Short Form Virtual Channel Table with Virtual Channel Map subtype 1.

        • Short Form Virtual Channel Table with Virtual Channel Map subtype 2.

        • Short Form Virtual Channel Table with Optional Inverse Channel Map.

          • System Time Table.

          • Network Text Table.

            • Network Text Table with optional Source Name Sub-table

  • Master Guide Table.

  • Aggregate Event Information Table

Note: It is imperative that the correct Flow id be used in order for this test to function properly.

N/A






On the DUT using the channel up and down buttons or the remote control, verify that the channel map has been successfully loaded and that the DUT can navigate the channel map.

Verify that navigation occurs with at least one or more of the SCTE65 profiles. Record if profile 5 is supported.



Note: Reference step 12 for channel map.




ExchF.38

ExchF.56


VirtChan.1

Hpinit.308

Hpinit.309




Using whatever means available clear the channel map from the DUT. Example of this would be on a Motorola DUT press and hold the “Power” and “select” buttons on the front panel. While depressing these buttons unplug the DUT and allow the front panel to flash at least 3 times and release the buttons. Power on the DUT and verify that there is no channel map loaded. This can be accomplished by channel up down operations.

N/A






Repeat steps 1 through 9.

N/A






Under the “Flow Feed” function, click the “Browse” button. Select the “Profile6.hex” file and click “OPEN”.

N/A






Enter the FLOW_ID that was noted in step 7 into the Flow ID window and click send.

In this step immediately after you click send, the following tables will be sent to the DUT.



    1. Network Information Table.

    2. System Time Table.

    3. Master Guide Table.

    4. Long Form Virtual Channel Table.

Note: It is imperative that the correct Flow id be used in order for this test to function properly.

N/A






On the DUT using the channel up and down buttons or the remote control, verify that the channel map has been successfully loaded and that the DUT can navigate the channel map. Attached is the channel map that is used for this test.

Verify that navigation occurs with at least one or more of the SCTE65 profiles. Record if profile 6 is supported.






ExchF.38

ExchF.56


FDCP.14

ExchF.41


ExchF.42




If the vendor stated in “Vendor Documentation” that they support CRC error checking, then remove the CableCARD and power cycle the DUT and repeat steps 1 through 9.

N/A






Open the Extended Channel Resource and under “Flow Feed” function, click the “Browse” button. Select the “Test CRC.hex” file and click “OPEN”.



N/A






Verify the DUT correctly processes the TestCRC.hex file.




ExchF.36

ExchF.62





Download 3.36 Mb.

Share with your friends:
1   ...   12   13   14   15   16   17   18   19   ...   31




The database is protected by copyright ©ininet.org 2024
send message

    Main page