I want to know what caused the test case to fail

[pinkgun]

Harness and CBSD have been configured. The following is the registration request received by the CBSD

The registrationresponse of SAS is not given, either in the console or in the log, only displayed

'The final result of the test : WINNF.FT.C.REG.1 is - FAIL'

2024-10-15T02:42:11.759Z - INFO - registration request from CBRS : { "registrationRequest": [ { "airInterface": { "radioTechnology": "NR" }, "callSign": "", "cbsdCategory": "A", "cbsdSerialNumber": "120200056822C2B0002", "fccId": "2AG32BSC7048A243", "measCapability": [], "userId": "120200056822C2B0002" } ] }

The following is the configuration information about harness and CBSD
cbsdc1.xml is entered into the CBSD device serial number,
cbsdc2.xml is not changed,
and conf.xml is changed into the corresponding IP address and certificate name

[pinkgun]

[idanrazisrdev]

Hi,
this is your lates e-mail following my answer:
Hi, Lee.

Sorry to bother you again,

According to the response from the project team,

"measCapability": -- > I didn't find how to configure it

This may depend on how the CBSD vendor has implemented it. Suggest to contact the CBSD vendor to determine how this parameter is populated.

As mentioned below, the following would be the acceptable values in measCapability (as described in WINNF-SSC-002)

“RECEIVED_POWER_WITHOUT_GRANT” or

“RECEIVED_POWER_WITH_GRANT” or

“RECEIVED_POWER_WITHOUT_GRANT, RECEIVED_POWER_WITH_GRANT” or

“RECEIVED_POWER_WITH_GRANT, RECEIVED_POWER_WITHOUT_GRANT”

"callSign": -- > Fill in "baicells",

radioTechnology": "NR" -- > is the default parameter

As mentioned below, there is a file for the test harness that needs to be updated to allow use of NR. NR may be default value populated by the CBSD in the registration request message, but the test harness file needs to include the NR value (NR was not an option during the timeframe when test harness was being developed. Realizing other radioTechnologies may be included in the future, the harness was developed to allow easily adding new values.)

Has section 10.4 in WINNF-IN-0156 been followed to add NR to radiotechnology?

File to be updated: “cbrsPython-master\Configuration\ObjectListConfig\laterDefindedOptionaljson”, following is the part in the file where NR is to be included.

"airInterface": {

"type": "object",

"description": "Air interface parameter for a CBSD",

"required": [ "radioTechnology" ],

"properties": {

  "radioTechnology": { "enum": [ "E_UTRA", "CAMBIUM_NETWORKS", “NR” ],

In addition, the CBSD model we use is Aurora243 n48, the manufacturer is baicells,

The first email attachment shows the test case fail,

However, the response of SAS Harness Test to CBSD cannot be queried.

Does the userID fill it in arbitrarily or does it need to fill in something specific?

Unclear what “it” refers to.

Attached is the log screenshot of CBSD, hoping to further help locate the problem

Not familiar with the png snapshot.

Refer to WINNF-IN-0156, wction 14.2 and 14.3 for log files of the windows command prompt running the WinnForum SAS test harness and of the individual test case.

[idanrazisrdev]

Your BaiCells CBSD should have a Management system that allows to configure various things like the "userId" and "callSign".
Configuring the "measCapability" should be also from the same Management system.
Please consult the person that gave you the Baicells CBSD for such configurations.

In addition - DO NOT run the SAS Harness from inside a debugging tool like you show in the attached screenshots for this case.
You MUST ALWAYS run from Windows Command Prompt using Administrator privileges as explained in WINNF-0156 section 6.2.

And the SAS Harness MUST be installed with Python version 2.7.13 which is 32 bit installation as explained in WINNF-0156 section 5.1.1.1 with the specific Python installation file name.
If you installed the Python 2.7.13 64 bit version - you need to uninstall it and installt the Python version 2.7.13 32 bit.
If you installed a more advanced version of Python on your Windows PC - the SAS Harness python code may also encounter issues.
You need to follow the EXACT instructions as written in WINNF-0156.

Hope this solves your problem with the Baicells CBSD,
Regards,
Idan Raz

[pinkgun]

Your BaiCells CBSD should have a Management system that allows to configure various things like the "userId" and "callSign". Configuring the "measCapability" should be also from the same Management system. Please consult the person that gave you the Baicells CBSD for such configurations.

In addition - DO NOT run the SAS Harness from inside a debugging tool like you show in the attached screenshots for this case. You MUST ALWAYS run from Windows Command Prompt using Administrator privileges as explained in WINNF-0156 section 6.2.

And the SAS Harness MUST be installed with Python version 2.7.13 which is 32 bit installation as explained in WINNF-0156 section 5.1.1.1 with the specific Python installation file name. If you installed the Python 2.7.13 64 bit version - you need to uninstall it and installt the Python version 2.7.13 32 bit. If you installed a more advanced version of Python on your Windows PC - the SAS Harness python code may also encounter issues. You need to follow the EXACT instructions as written in WINNF-0156.

Hope this solves your problem with the Baicells CBSD, Regards, Idan Raz

I've added "NR" to the laterDefinedOptionaljson file, and the BaiCells CBSD Management system can fill in "userId" and "callSign", but no "measCapability" option is available.

I have followed WINNF-0156 to the letter, Python version 2.7.13 32-bit.

There are also possible problems that cause test cases to fail.

[idanrazisrdev]

Looking at your latest PNG of Windows Command Prompt I still see the SAS Harness installation was wrong. You should not get all these messages of all the Python files.
How did you put the SAS Harness on your Windows machine?
Cloning (or Pulling) the project from Github is WRONG.
You need to take the ZIP file of v1.0.0.3 from the "Releases" section of the project as explained in WINNF-0156 section 5.2 and then unzip it locally in your Windows machine. I recommend creating in your Windows PC main C drive a directory called "sasharness" , download the ZIP file to that C:\sasharness and extract the zip file there.
And then open your Windows Command Prompt with Administrative Privileges, and you are doing "cd C:\sasharness\cbrsPython-master\cbrsPython\controllers". And then "python StartOfProject.py"
This is explained in WINNF-IN-0156 section 6.2

[pinkgun]

Looking at your latest PNG of Windows Command Prompt I still see the SAS Harness installation was wrong. You should not get all these messages of all the Python files. How did you put the SAS Harness on your Windows machine? Cloning (or Pulling) the project from Github is WRONG. You need to take the ZIP file of v1.0.0.3 from the "Releases" section of the project as explained in WINNF-0156 section 5.2 and then unzip it locally in your Windows machine. I recommend creating in your Windows PC main C drive a directory called "sasharness" , download the ZIP file to that C:\sasharness and extract the zip file there. And then open your Windows Command Prompt with Administrative Privileges, and you are doing "cd C:\sasharness\cbrsPython-master\cbrsPython\controllers". And then "python StartOfProject.py" This is explained in WINNF-IN-0156 section 6.2

I have carried out debugging according to what you said, what should I input in the next step,
which is the same as WINNF-IN-0156 section 6.2
Figure 2: The example of Windows Command Prompt Running WInnForum SAS Test Harness is different. The test case entered in the figure is idan4 and idan test 31 aug is entered. What should I enter at "idan test 31 aug"

[idanrazisrdev]

Hi,
the Figure 1 which you placed now from 8-Nov-2024 shows everything is working properly for you. from the SAS<->CBSD protocol messages.
You activated in the Command Prompt the SAS Harness correctly. Then you started correctly the test WINNF.FT.C.REG.1.
CBSD Sent "Registration Request" and SAS Harness sent successful "Registration Response". At this point the SAS<->CBSD protocol messages designed for test WINNF.FT.C.REG.1 completed successfully and you reached the "questions phase for the technician". The question is "were there RF transmissions during the test" you replied "y". But the expected answer is "n" . Hence the final result of the test WINNF.FT.C.REG.1 is FAIL.

So to conclude for 8-Nov-2024 your SAS Harness is working correctly:
(1) you did the SAS Harness installation correctly.
(2) The SAS<->CBSD protocol messages are successful and correct between your CBSD and the SAS Harness
(3) you reached the "questions phase for the technician" and the final PASS/FAIL result of the test is given correctly based on the y/n answers you are providing.
Hence you can close this github issue as resolved

For the desired y/n answer of the "questions phase for the technician", please see document WINNF-TS-0122. Table 6-3 in WINNF-TS-0122 details the various test cases. The name of the test case is the same name you are running in the SAS Harness. And you can see in document WINNF-TS-0122 the steps of each test case with the expected result of each step.
You executed test WINNF.FT.C.REG.1 - you can see the full test details in section 6.1.4.1.1 of WINNF-TS-0122.