Doc. No : AMANTYA-v1.0 1.1.1.1.
Doc. No : AMANTYA-v1.0 1.1.1.1.1 AMANTYA TECHNOLOGIES NBIoT Agnostic ACP User Manual Release Date: 01-10-20 Page 2 of 23 Contents 1 About This Document ................................................................................................................ 5 1.1. Introduction .......................................................................................................................... 5 1.2. Purpose and scope .......................................................................
Doc. No : AMANTYA-v1.0 1.1.1.1.
Doc. No : AMANTYA-v1.0 1.1.1.1.1 AMANTYA TECHNOLOGIES NBIoT Agnostic ACP User Manual Release Date: 01-10-20 Page 4 of 23 Document Version History Version Number Version Date Revised By Description V1.0 01-10-2020 Vikas Dubey User Manual for Test Executor and NBIoT eNodeB setup. V1.
Doc. No : AMANTYA-v1.0 1.1.1.1.1 AMANTYA TECHNOLOGIES NBIoT Agnostic ACP User Manual Release Date: 01-10-20 Page 5 of 23 1 About This Document 1.1. Introduction Amantya supports Verizon in developing an NBIoT device tester product based on the 3GPP 36.5233 and 3GPP 36.523-1 UE conformance testing specifications. This product is used for end of the line UE testing by Verizon. The product consists of necessary customizations in the Verizon ACP product along with integration of NBIoT L1, L2 stack, 3GPP 36.
Doc. No : AMANTYA-v1.0 1.1.1.1.1 AMANTYA TECHNOLOGIES NBIoT Agnostic ACP User Manual Abbreviation Expansion SRB Signaling Radio Bearer eNB /eNB eNodeB TCI TTCN-3 Control Interface TRI TTCN-3 Runtime Interface TE Test Executor/Engine TMWC Test Manger Web Client TMWS Test Manager Web Server TM Test Management TL Test Logging TRI TTCN-3 Run time Interface TTCN Testing and Test Control Notation UE User Equipment VZW Verizon Wireless 1.5.
Doc. No : AMANTYA-v1.0 1.1.1.1.
Doc. No : AMANTYA-v1.0 1.1.1.1.1 AMANTYA TECHNOLOGIES NBIoT Agnostic ACP User Manual Release Date: 01-10-20 Page 8 of 23 3 Tuning eNodebB hardware 3.1 Static IP assign 1. Login to eNodeB NBIOT Board using ssh root@192.168.2.51 Password: root123 2. Or Login using Normal desktop setup and given under section 4. 3. Update /etc/netwok/interfaces file in system with IP address, gateway. 4. Reboot system.
Doc. No : AMANTYA-v1.0 1.1.1.1.1 AMANTYA TECHNOLOGIES NBIoT Agnostic ACP User Manual 3.2 Release Date: 01-10-20 Page 9 of 23 NBIoT eNodeB Power Up 3.2.1 Power up To power up the Board, connect power Adapter as shown below. There is a push button with power symbol. Push it to Power ON the eNodeB NBIOT board. On Power Up, Blue LED will continuously glow. To Shutdown, long press the power button. Orange LED will blink to denote RF messages transfer. 3.2.
Doc. No : AMANTYA-v1.0 1.1.1.1.1 AMANTYA TECHNOLOGIES NBIoT Agnostic ACP User Manual 3.3 Release Date: 01-10-20 Page 10 of 23 Device Provision 3.3.1 Enable eNodeB binaries start at reboot/power-up 1. Login in the enodeb hardware using ssh, user-id: root and password:root123 #ssh root@192.168.2.51 2. Edit /etc/rc.local and add sh /opt/NBIOT/start_binary.sh 3.3.2 Support for ftcmd command 1. Login in the enodeb hardware using ssh command, user id; root and password:root123 #ssh root@192.168.2.51 2.
Doc. No : AMANTYA-v1.0 1.1.1.1.1 AMANTYA TECHNOLOGIES NBIoT Agnostic ACP User Manual Release Date: 01-10-20 Page 11 of 23 3. run in enodeb terminal # ln -s /opt/NBIOT/stack_reboot.
Doc. No : AMANTYA-v1.0 1.1.1.1.1 AMANTYA TECHNOLOGIES NBIoT Agnostic ACP User Manual Release Date: 01-10-20 Page 12 of 23 4 Warnings for handling eNodeB Changes or modifications to this unit not expressly approved by the party responsible for compliance could void the user authority to operate the equipment. 1. To comply with FCC RF exposure compliance requirements, a separation distance of at least 20 cm must be maintained between the antenna of this device and all persons. 2.
Doc. No : AMANTYA-v1.0 1.1.1.1.1 AMANTYA TECHNOLOGIES NBIoT Agnostic ACP User Manual Release Date: 01-10-20 Page 13 of 23 5 Test Case execution 5.1 Test execution Note: Below is sequence of execution of test setup. 1. Run System simulation binaries (VZW_SA_Agent and NBIoT eNodeB L1L2 stack). 2. Test Cast tool setup with TTCN project 3. Run test case from Test Cast 4. Run System Adapter 5.1.1 Test execution with ACP 5.1.
Doc. No : AMANTYA-v1.0 1.1.1.1.1 AMANTYA TECHNOLOGIES NBIoT Agnostic ACP User Manual Release Date: 01-10-20 Page 14 of 23 3. Run Test case 4. Test execution produces a test log that is visible in the ttcn3_log pane. The session log contains all information of test and gives complete flow of execution and provides info whether the test has been successful or failed.
Doc. No : AMANTYA-v1.0 1.1.1.1.1 AMANTYA TECHNOLOGIES NBIoT Agnostic ACP User Manual Release Date: 01-10-20 Page 15 of 23 These logs are also saved at location where project file is placed. Also any specific log can be viewed from Project explorer as shown below.
Doc. No : AMANTYA-v1.0 1.1.1.1.1 AMANTYA TECHNOLOGIES NBIoT Agnostic ACP User Manual 5.2 Release Date: 01-10-20 Page 16 of 23 System Adapter System Adaptor (SA) module is mainly responsible for routing the UE control messages, eNodeB signalling messages and configuration messages. 1. System Adapter binary will be placed under C:/ACP/SA_EXE/hw_v4 Update SaConfig.cfg in C:/ACP/SA_EXE, for below parameters a. SELF_IP: IP of the Windows system(192.168.2.210) b.
Doc. No : AMANTYA-v1.0 1.1.1.1.1 AMANTYA TECHNOLOGIES NBIoT Agnostic ACP User Manual Release Date: 01-10-20 Page 17 of 23 System Adapter binary run through startAdapter.bat script file at C:/ACP/SA_EXE/hw_v4. Double click to run the batch file.
Doc. No : AMANTYA-v1.0 1.1.1.1.1 AMANTYA TECHNOLOGIES NBIoT Agnostic ACP User Manual Release Date: 01-10-20 Page 18 of 23 6 eNodeB and VZW_SA_Agent 1. VZW system adapter agent Windows system IP configuration. Update SA_IP in VzwSaAgent/config/config.cfg to IP of Windows system (192.168.2.210) where System Adapter is running. 2. Amantya will share Agnostic_Nbiot_v1.0.tar.gz package for NBIoT eNodeB and VZW_SA_Agent. Place this package under C:/ACP/tmBin/hw_v4/default_eNB_bin.
Doc. No : AMANTYA-v1.0 1.1.1.1.1 AMANTYA TECHNOLOGIES NBIoT Agnostic ACP User Manual Release Date: 01-10-20 Page 19 of 23 3. Run the BoardInfo_Nb.bat through Cygwin Terminal or Windows Power Shell to get Board information in form below. Pass IP address of eNodeB Hardware as parameter to batch file. (Ex Run command as ./BoardInfo.bat 192.168.2.51) Before running the batch file, modify it has correct Username and password of eNodeB Hardware. 4.
Doc. No : AMANTYA-v1.0 1.1.1.1.1 AMANTYA TECHNOLOGIES NBIoT Agnostic ACP User Manual Release Date: 01-10-20 Page 20 of 23 7 Compilation of source code 7.1 TE compilation steps 1. Open TTCN project with source code by clicking on project file (rel_nb.tcproj) as shown below. 2. Test scripts (including codec rules and external attributes and TTCN3 settings) must be prepared and compiled with TestCast TTCN-3 Professional. 3. Press Create TTCN-3 Runtime (Build->Create TTCN-3 Runtime or F7).
Doc. No : AMANTYA-v1.0 1.1.1.1.1 AMANTYA TECHNOLOGIES NBIoT Agnostic ACP User Manual Release Date: 01-10-20 Page 21 of 23 4. A folder named “Ttcn3runtime” created in the same path where your source TTCN3 project file is present and it contain a folder named “rel15_nb” or source TTCN3 project file name.
Doc. No : AMANTYA-v1.0 1.1.1.1.1 AMANTYA TECHNOLOGIES NBIoT Agnostic ACP User Manual 7.2 Release Date: 01-10-20 Page 22 of 23 VZW System Adapter Agent compilation steps 1. Compilation has been done on Ubuntu 16.04 Linux platform. 2. Go to the path of VZW_SA_AGENT code and run the command “./build.sh clean” 3. Now run “build.sh” command to compile the code. 4. Now these logs should be visible at the end of the compilation process. Logs of successful compilation VZW_SA_Agent_compilationLogs.
Doc. No : AMANTYA-v1.0 1.1.1.1.1 AMANTYA TECHNOLOGIES NBIoT Agnostic ACP User Manual 7.3 Release Date: 01-10-20 Page 23 of 23 System Adapter compilation steps 1. Compilation has been done on Microsoft Visual Studio 2017 2. In Solution Explorer, choose or open the solution (SystemAdapter). 3. On the menu bar, choose Build and then choose Clean Solution to delete any intermediate and output files. New instances of the intermediate and output files can then be built. 4.