all | frequencies |
|
|
|
|
exhibits | applications |
---|---|---|---|---|---|---|---|
manual | photos | label |
app s | submitted / available | |||||||
---|---|---|---|---|---|---|---|---|
1 2 3 |
|
User Munaul | Users Manual | 4.60 MiB | March 27 2020 | |||
1 2 3 |
|
Internal Photos | Internal Photos | 1.49 MiB | March 27 2020 / September 23 2020 | delayed release | ||
1 2 3 |
|
External Photos | External Photos | 1.35 MiB | March 27 2020 / September 23 2020 | delayed release | ||
1 2 3 |
|
Label and Location | ID Label/Location Info | 144.81 KiB | March 27 2020 | |||
1 2 3 |
|
Agent Authorization Rev 1.0 | Cover Letter(s) | 14.69 KiB | March 27 2020 | |||
1 2 3 | BOM | Parts List/Tune Up Info | March 27 2020 | confidential | ||||
1 2 3 |
|
Block Statement | Cover Letter(s) | 89.50 KiB | March 27 2020 | |||
1 2 3 | Declaration Letter of Software Security Requirements For U-NII Devices | SDR Software/Security Inf | March 27 2020 | confidential | ||||
1 2 3 |
|
FCC Software Configuration Control Declaration Rev1.1 | Cover Letter(s) | 75.13 KiB | March 27 2020 | |||
1 2 3 |
|
FCC Short & Long Term Confidentiality | Cover Letter(s) | 78.51 KiB | March 27 2020 | |||
1 2 3 | Operation Description | Operational Description | March 27 2020 | confidential | ||||
1 2 3 |
|
Part 15E InHand Report wifi MIMO UNII-1&UNII-3 Part 1 | Test Report | 4.92 MiB | March 27 2020 | |||
1 2 3 |
|
Part 15E InHand Report wifi MIMO UNII-1&UNII-3 Part 2 | Test Report | 5.45 MiB | March 27 2020 | |||
1 2 3 |
|
Part 15E InHand Report wifi MIMO UNII-1&UNII-3 Part 3 | Test Report | 5.77 MiB | March 27 2020 | |||
1 2 3 |
|
Part 15E InHand Report wifi MIMO UNII-1&UNII-3 Part 4 | Test Report | 5.00 MiB | March 27 2020 | |||
1 2 3 |
|
Part 15E InHand Report wifi MIMO UNII-1&UNII-3 Part 5 | Test Report | 3.60 MiB | March 27 2020 | |||
1 2 3 |
|
Part 15E InHand Report wifi MIMO UNII-1&UNII-3 Part 6 | Test Report | 2.72 MiB | March 27 2020 | |||
1 2 3 |
|
RF Exposure Evaluation | RF Exposure Info | 530.68 KiB | March 27 2020 | |||
1 2 3 | SCH | Schematics | March 27 2020 | confidential | ||||
1 2 3 |
|
Test Setup Photos | Test Setup Photos | 320.37 KiB | March 27 2020 | |||
1 2 3 | Tune up Info | Parts List/Tune Up Info | March 27 2020 | confidential | ||||
1 2 3 | block diagram | Block Diagram | March 27 2020 | confidential | ||||
1 2 3 | Block Diagram | Block Diagram | March 26 2020 | confidential | ||||
1 2 3 |
|
Part22.24.27 RSS130 132 133 139 Inhand Report | Test Report | 1.76 MiB | March 26 2020 | |||
1 2 3 | Schematic | Schematics | March 26 2020 | confidential | ||||
1 2 3 | Tune up Procedure | Parts List/Tune Up Info | March 26 2020 | confidential | ||||
1 2 3 | Operational Description | Operational Description | March 26 2020 | confidential | ||||
1 2 3 |
|
Part 15C RSS 247 Inhand Report wifi SISO Part1 | Test Report | 5.51 MiB | March 26 2020 | |||
1 2 3 |
|
Part 15C RSS 247 Inhand Report wifi SISO Part2 | Test Report | 5.22 MiB | March 26 2020 | |||
1 2 3 |
|
Part 15C RSS 247 Inhand Report wifi SISO Part3 | Test Report | 5.40 MiB | March 26 2020 | |||
1 2 3 |
|
Part 15C RSS 247 Inhand Report wifi SISO Part4 | Test Report | 5.25 MiB | March 26 2020 | |||
1 2 3 | Tune up Procedure | Parts List/Tune Up Info | March 26 2020 | confidential |
1 2 3 | User Munaul | Users Manual | 4.60 MiB | March 27 2020 |
InHand VG710 InVehicle Gateway User Manual InHand VG710 InVehicle Gateway User Manual Issue: V1.0 Thursday, March 26, 2020 12:00:28 PM 1 InHand VG710 InVehicle Gateway User Manual Declaration permission of InHand. Thank you for choosing our product. Before using the product, read this manual carefully. The contents of this manual cannot be copied or reproduced in any form without the written Due to continuous updating, InHand cannot promise that the contents are consistent with the actual product information, and does not assume any disputes caused by the inconsistency of technical parameters. The information in this document is subject to change without notice. InHand reserves the right of final change and interpretation. 2020 InHand Networks. All rights reserved. Conventions Symbol
Indicates a button name, for example, the OK button. Indication Indicates a window name or menu name, for example, the pop-up window "New User". Separates a multi-level menu. For example, the multi-level menu File >> New >> Folder indicates the menu item "Folder" under the sub-menu "New", which is under the menu
"File". Reminds readers to be careful. Improper action may result in loss of data or device damage. Notes contain detailed descriptions and helpful suggestions. Technical support:
Beijing InHand Networks Technology Co., Ltd. (Headquarters) Address: Floor 5, Building 3, Yard 18, Ziyue Road, Chaoyang District, Beijing Telephone: 010-8417 0010 Chengdu Office Telephone: 028-8679 8244 Hi-tech Zone, Chengdu, Sichuan Guangzhou Office i Address: Room 1406, Building 10, Tianfu New Valley, No. 399 West Section of Fucheng Avenue, InHand VG710 InVehicle Gateway User Manual Address: Unit B-130, Yuanyang Creative Park, No. 5 Tangdong East Road, Tianhe District, Address: Room 2001, Building 11, Villa De Paris, No. 2 Luoyu East Road, Hongshan District, Wuhan, Telephone: 020-8562 9571 Guangzhou Wuhan Office Telephone: 027-8716 3566 Hubei Shanghai Office Telephone: 021-5480 8501 Address: Room 1103, No. 18 Shunyi Road, Putuo District, Shanghai ii InHand VG710 InVehicle Gateway User Manual Contents 1 Overview ........................................................................................................................................ 1 2 Hardware ....................................................................................................................................... 2 2.1 Indicator Description ............................................................................................................... 2 2.2 Restoring Default Settings via the Reset Button ..................................................................... 3 3 Default Settings .............................................................................................................................. 4 4 Login and Network Access ........................................................................................................... 6 4.1 Network Access via the Dialup Card ...................................................................................... 6 4.2 Network Access via Wi-Fi ...................................................................................................... 9 5 Network Management ................................................................................................................. 11 5.1 Network ................................................................................................................................. 11 5.1.1 Bridge Port ................................................................................................................ 11 5.1.2 VLAN Port ................................................................................................................ 12 5.1.3 ADSL Dialup (PPPoE) .............................................................................................. 14 5.1.4 Wi-Fi ............................................................................................................................ 14 5.1.5 Loopback Port ........................................................................................................... 16 5.1.6 Layer 2 Switch ........................................................................................................... 16 5.2 OBD ...................................................................................................................................... 16 5.3 VPN Application ................................................................................................................... 19 5.3.1 IPsec .......................................................................................................................... 19 5.3.2 GRE ........................................................................................................................... 23 5.3.3 L2TP .......................................................................................................................... 24 5.3.4 OpenVPN .................................................................................................................. 25 5.3.5 Certificate Management ............................................................................................ 27 5.4 Services ................................................................................................................................. 29 5.4.1 DHCP (Automatic IP Address Allocation) ............................................................... 29 5.4.2 DNS ........................................................................................................................... 30 5.4.3 DDNS ........................................................................................................................ 31 1 InHand VG710 InVehicle Gateway User Manual 5.4.4 SMS ........................................................................................................................... 33 5.4.5 GPS ............................................................................................................................ 34 5.4.6 QoS ............................................................................................................................ 36 5.4.7 Traffic Control ........................................................................................................... 37 5.5 Firewall .................................................................................................................................. 38 5.5.1 ACL ........................................................................................................................... 38 5.5.2 NAT ........................................................................................................................... 39 5.5.3 MAC-IP Binding ....................................................................................................... 40 5.6 Routing .................................................................................................................................. 41 5.6.1 Static Routing ............................................................................................................ 41 5.6.2 Dynamic Routing ...................................................................................................... 41 5.7 Link Backup .......................................................................................................................... 46 5.7.1 SLA ........................................................................................................................... 46 5.7.2 Track .......................................................................................................................... 46 5.7.3 VRRP......................................................................................................................... 48 5.7.4 Interface Backup ........................................................................................................ 50 5.8 Wizards .................................................................................................................................. 52 5.8.1 New Cellular .............................................................................................................. 52 5.8.2 New IPsec Tunnel ..................................................................................................... 53 5.8.3 IPsec Experts' Configuration ..................................................................................... 54 5.8.4 New L2TPv2 Tunnel ................................................................................................. 54 5.8.5 New Port Mapping .................................................................................................... 55 6 APP Management ........................................................................................................................ 57 7 Connecting the Gateway to a Cloud Platform .......................................................................... 58 8 Industrial Ports (Serial Ports) .................................................................................................... 59 8.1 DTU ....................................................................................................................................... 59 8.2 IO Ports ................................................................................................................................. 61 9 System Management ................................................................................................................... 63 2 InHand VG710 InVehicle Gateway User Manual 9.1 System ................................................................................................................................... 63 9.2 System Time .......................................................................................................................... 63 9.3 Management Services ............................................................................................................ 65 9.4 User Management.................................................................................................................. 66 9.5 AAA ...................................................................................................................................... 66 9.5.1 Radius ........................................................................................................................ 67 9.5.2 Tacacs+ ...................................................................................................................... 68 9.5.3 LDAP......................................................................................................................... 68 9.5.4 AAA Authentication .................................................................................................. 69 9.6 Configuration Management ................................................................................................... 70 9.7 SNMP .................................................................................................................................... 71 9.7.1 SNMP ........................................................................................................................ 71 9.7.2 SnmpTrap (Alarm) .................................................................................................... 72 9.7.3 SnmpMibs ................................................................................................................. 72 9.8 Alarm ..................................................................................................................................... 73 9.9 System Logs .......................................................................................................................... 75 9.10 System Upgrade .................................................................................................................... 76 9.11 System Reboot ....................................................................................................................... 77 10 Diagnostic Tools ........................................................................................................................... 78 3 InHand VG710 InVehicle Gateway User Manual 1 Overview InHand VG710 is a new-generation 4G in-vehicle gateway oriented at the Internet of Vehicles (IoV). It provides fast and safe networks for automobiles and transport service vehicles, meeting the requirements of police vehicles, emergency command vehicles, engineering vehicles, medical vehicles, and logistics vehicles for fast mobile networks. It is used with a cloud-based remote vehicle management platform to provide ubiquitous accessible networks and uninterrupted operation supervision for logistics management, asset tracking, mobile office, and government security. Fig. 1 Application case 1 InHand VG710 InVehicle Gateway User Manual 2 Hardware 2.1 Indicator Description VG710 Indicator Status and Definition Steady off --- The device is powered off. Steady red --- The system is starting. System Blinking green --- The system operates properly. Blinking red --- The system is faulty. Blinking blue --- The system is being upgraded. Steady off --- The dialup function is disabled. Cellular Blinking green --- Dialup is in progress. Steady green --- Dialup succeeds. Blinking red --- Dialup fails (no module or SIM card is detected). Steady off --- The current dialup card has no signal. Steady red --- The current dialup card has weak signals (signal strength: 9 asu). Steady blue --- The current dialup card has moderate signals (signal strength: 1019 Signal asu). Steady off --- GNSS is disabled. GNSS Blinking green --- Positioning is in progress. Steady green --- Positioning is completed. Used as an AP:
Steady off --- The AP is disabled. Blinking green --- The AP operates properly. Wi-Fi 2.4G Used as a STA:
Steady off --- The STA is disabled, or no AP is associated. Steady green --- Connection fails due to a wrong password after an AP is associated. Blinking green --- An AP is associated. 2 InHand VG710 InVehicle Gateway User Manual Used as an AP:
Steady off --- The AP is disabled. Blinking blue --- The AP operates properly. Wi-Fi 5G Used as a STA:
Steady off --- The STA is disabled, or no AP is associated. Steady blue --- Connection fails due to a wrong password after an AP is associated. Blinking blue --- An AP is associated. Steady off --- The APP is disabled. Steady green --- The APP is enabled. U1 and U2 U1:
U2:
Steady off --- The virtual private network (VPN) is disabled or abnormal. Steady green --- The VPN operates properly. 2.2 Restoring Default Settings via the Reset Button To restore default settings via the Reset button, perform the following steps:
1. Power on the device and immediately press and hold the Reset button. After about 15s, only 2. When the System indicator turns off and becomes red again, immediately release the Reset the System indicator is steady red. button. 3. When the System indicator turns off, press the Reset button (ensure that it blinks red twice) and then release it. The device is restored to the default settings. 3 InHand VG710 InVehicle Gateway User Manual 3 Default Settings No. Function Default Settings Enabled (The Cellular indicator is steady green after dialup By default, the dual-SIM function is disabled, and SIM1 is Enabled (The GNSS indicator is steady green after positioning succeeds.) enabled. succeeds.) Dialup over cellular network the Satellite positioning and inertial navigation service On-board diagnostics (OBD) The inertial navigation function is enabled. Enabled The CANbus baud rate is automatically detected. The OBD protocol is automatically detected. OBD data is automatically scanned. The Wi-Fi 2.4G AP is enabled. The SSID starts with VG710-, followed by six digits. 4 Default settings of Wi-Fi followed by six digits. The Wi-Fi 5G AP is enabled. The SSID starts with VG710-5G-, WPA2-PSK is used for authentication. The password contains the last eight digits of the SN. Four LAN ports are enabled. The IP address is 192.168.2.1. The subnet mask is 255.255.255.0. Default settings of Ethernet The DHCP server is enabled. The IP address pool is 192.168.2.2 192.168.2.100, and IP addresses can be automatically allocated to downstream devices. Network control access the for HTTP and HTTPS are enabled, with the port numbers of 80 and 1 2 3 5 6 4 InHand VG710 InVehicle Gateway User Manual gateway 443 respectively. Telnet is disabled. SSH is disabled. Access from the cellular network is allowed only over HTTPS. 7 User name and password adm/123456 (super administrator) 8 Power management standby mode. shutdown-delay 30: The power-off delay is 30s. standby-mode 1: The power-off function is enabled. standby-check-interval 20 indicates the power check interval in standby-voltage 90: The standby threshold voltage is 9 V. standby-resume-voltage 105: The threshold voltage for resuming normal operating in standby mode is 10.5 V. Four digital output channels generate output at low level by 9 IO default, and the pull-up resistor is disabled. The pull-up resistor for six digital input channels is disabled. 10 Serial port RS485 RS232 Baud rate: 9600 Data bits: 8 bits Parity bit: none Stop bit: 1 bit Baud rate: 9600 Data bits: 8 bits Parity bit: none Stop bit: 1 bit 5 InHand VG710 InVehicle Gateway User Manual 4 Login and Network Access 4.1 Network Access via the Dialup Card 1. Insert the SIM card, connect the GNSS and cellular antennas, and connect the power supply and PC. Insert the diversity dialup antenna when the dialup card has poor signals. Connect the PC GNSS antenna Cellular antenna Power Insert the SIM card Note:
gateway. Before inserting or removing the SIM card, unplug the power cable; otherwise, the operation will cause data loss or damage the gateway. 2. Assign an IP address to the PC, which is on the same network segment as the IP address of the Method 1:
Enable the PC to obtain an IP address automatically (recommended). Method 2:
Configure a fixed IP address on the same network segment as the gateway address for the PC. 6 InHand VG710 InVehicle Gateway User Manual Step: Select "Use the following IP address", enter any IP address in the range of 192.168.2.2 to 192.168.2.254 (different from the initial IP address 192.168.2.1 of the gateway), the subnet mask 255.255.255.0, and the default gateway address 192.168.2.1, and then click OK. Obtain an IP address automatically Use a fixed IP address 3. Open the browser, enter the default IP address 192.168.2.1 of the gateway in the address bar, and press Enter. 4. Log in (if a blocking prompt is displayed, click "Advanced >> Continue"). 5. Click "Network >> Cellular", check "Enable", and click Apply & Save. If the network connection status is "Connected" and an IP address has been allocated, the SIM card has been connected to the network.
(Set the APN parameters for a private-network card.) 7 InHand VG710 InVehicle Gateway User Manual 6. Ping a common website in China with a ping detection tool. If there is data transmission, the device has been successfully connected to the network. 7. Enable the dual-SIM function when two SIM cards are used. 8 InHand VG710 InVehicle Gateway User Manual 4.2 Network Access via Wi-Fi 1. Complete the connection shown in the following figure. Connect the PC Wi-Fi antenna Power supply GNSS antenna 2. Assign an IP address to the PC, which is on the same network segment as the IP address of the gateway. Log in to the web page. For details, see 4.1 Network Access via the Dialup Card. 9 InHand VG710 InVehicle Gateway User Manual 3. Click " Network >> Wi-Fi" and select Wi-Fi 2.4G or Wi-Fi 5G as a client. Enter the name, authentication method, and key of an available wireless access point (AP). Click Apply & Save. Note: the device for operation in the band 5150-5250MHz is only for indoor use to reduce the potential for harmful interference to co-channel mobile satellite systems. 4. Click "Status". The current network status is "Connected", and an IP address is obtained successfully, indicating that the device has been successfully connected to the network via Wi-Fi. 10 InHand VG710 InVehicle Gateway User Manual 5 Network Management In parameter settings, a green text box indicates a mandatory item, and a pure white text box indicates an optional item. 5.1 Network 5.1.1 Bridge Port A bridge port is intended to connect two different physical LANs over a bridge, to enable storage and forwarding across LANs at the link layer. Method for modifying the IP address of a bridge port and bridge members:
1. Click "Network >> Bridge" and select "Bridge >> Modify". 2. Modify the IP address of the bridge port or bridge members. Among the bridge members, dot11radio1 and dot11radio2 are Wi-Fi 2.4G and Wi-Fi 5G ports respectively. 11 InHand VG710 InVehicle Gateway User Manual 5.1.2 VLAN Port A virtual LAN (VLAN) comprises a group of logical devices and users. These devices and users are not limited by physical locations, but can be organized based on functions, departments, applications, and other factors. They communicate with each other as if they are on the same network segment, which contributes to the name of VLAN. Method for adding a port of VLAN 2:
1. Click "Network >> VLAN >> Configure VLAN Parameters >> Add". Set the virtual IP address of the port of VLAN 2 and select the member port of VLAN 2 as required. Click Apply & Save. 12 InHand VG710 InVehicle Gateway User Manual 2. Return to the VLAN list. The port of VLAN 2 has been successfully added. Currently, VLAN ports of the device support two link types: access and trunk. An access port belongs to only one VLAN and is generally connected to a computer. A trunk port can be used for multiple VLANs and can receive messages from or send messages to multiple VLANs. It can be connected to a switch or a user's computer. You can select the link type as required on the "VLAN Trunk" page. 13 InHand VG710 InVehicle Gateway User Manual 5.1.3 ADSL Dialup (PPPoE) Method for connecting the gateway to the PPPoE server:
1. Click "Network > > ADSL Dialup (PPPoE)", select the VG710 interface for connecting to the PPPoE server in the "Dial Pool" bar, and click Add. 2. Enter the user name, password, and pool ID of the PPPoE server in the "PPPoE List" bar. The pool ID must be the same as that in the "Dial Pool" bar. Click Add, and then click Apply & Save. 5.1.4 Wi-Fi The gateway can be used as an AP or a client. When it is used as an AP, other users can access the Internet through the gateway via Wi-Fi. When it is used as a client, the gateway connects to an AP for Internet access. The status bar shows the current Wi-Fi connection status of the gateway. 14 InHand VG710 InVehicle Gateway User Manual Method for providing network access services for wireless terminals when the gateway is used as an AP:
Click "Wi-Fi >> Wi-Fi 2.4 or Wi-Fi 5G" and select "AP" for "Station Role". Enter the SSID, authentication method, and key consistent with those of the wireless AP. Click Apply & Save. Method for connecting to an AP for Internet access when VG710 is used as a client:
Select "Client", enter the Wi-Fi SSID and key, and click Apply & Save. 15 InHand VG710 InVehicle Gateway User Manual 5.1.5 Loopback Port Method for adding multiple loopback ports:
Add, and then click Apply & Save. Click "Network >> Loopback >> Multi-IP Settings", configure any IP address for the gateway, click 5.1.6 Layer 2 Switch Check the network connection status of GE 1 to GE 4. LINK UP indicates that the network is connected. LINK DOWN indicates that the network is disconnected. 5.2 OBD 16 InHand VG710 InVehicle Gateway User Manual OBD is used to collect vehicle condition data, obtain emission information, and perform fault diagnosis in real time. Vehicle condition data includes key parameters such as the fuel level, mileage, driving speed, engine speed, engine load, coolant temperature, and brake pressure. Emission information includes the volume of AdBlue, the operating and monitoring status of various exhaust post-processing sensors (such as the exhaust gas sensor and diesel particle filter) and catalysts, etc. In fault diagnosis, standard fault codes of vehicles and description information can be obtained in real time, so that vehicle maintenance personnel can learn the vehicle health status in time and locate the To collect vehicle data, the gateway is connected to the diagnostic port of the vehicle through the I/O port of the gateway over the OBD-II or J1939 cable. The cable accessories can be selected or customized during purchasing. For details about the access method, see Section 4.4 in the VG710 Quick Start Guide. After the gateway starts, the OBD service is automatically enabled to collect key vehicle condition data and fault code information. The power supply and OBD cable of the gateway shall be installed when the vehicle is off. The vehicle status information is displayed on the OBD status page. CAN Link Status (ERROR-ACTIVE indicates that the gateway has successfully connected to the diagnostic port of the vehicle. Other status indicates that the connection is abnormal or the diagnostic port of the vehicle is not identified.) CAN Bitrate (In OBD, the CAN bitrate is automatically adapted, generally 250 kbps or 500 kbps.) CAN Bind ("OBD" (default) or "Custom") OBD Connection Status ("Disconnected", "Connecting", or "Connected") OBD Protocol Type (OBD-II or J1939) faults. Note:
OBD Status:
17 InHand VG710 InVehicle Gateway User Manual Scan OBD Data and Export OBD Report:
Click the Scan OBD Data button to generate a OBD data report containing detailed vehicle condition data and diagnostic information. Click the Export OBD Report button to save the generated OBD data report to the local storage. OBD Data Stream: The real-time vehicle condition data is displayed. OBD Ability:
Version of the OBD ability;
Type of the OBD protocol;
Vehicle identification number (VIN);
Valid variables and reference values that can be collected by the gateway. 18 InHand VG710 InVehicle Gateway User Manual 5.3 VPN Application The VPN is intended to establish a private network on the public network for encrypted communication. A VPN gateway enables remote access by encrypting data packets and converting the destination address of data packets. The VPN can be realized by a server, hardware, or software, or in other ways. Compared with the traditional DDN private line or frame relay, the VPN provides a more secure and convenient remote access solution. Common VPN application scenario: For example, an employee on a business trip accesses the enterprise's intranet. The employee connects to the enterprise's VPN server and then accesses the enterprise's intranet through the VPN server. Communication data between the VPN server and the client is encrypted and can be regarded as being transmitted on a dedicated data network. This ensures data security. 5.3.1 IPsec IPsec is a group of open network security protocols developed by IETF. At the IP layer, the data source authentication, data encryption, data integrity, and anti-replay functions are used to ensure the 19 InHand VG710 InVehicle Gateway User Manual security of data transmission between communication parties on the Internet. This reduces the risk of leakage and eavesdropping, ensures the integrity and confidentiality of data, and ensures the security of service transmission for users. Scenario: Data is transmitted between the subnet (192.168.1.0/24) of headquarters A and the subnet
(172.16.1.0/24) of customer branch B through gateway A and gateway B. The transmission channels of gateway A and gateway B are encrypted over IPsec, to protect the security of data transmission between headquarters A and customer branch B. Method for encrypting the transmission channels of gateway A and gateway B over IPsec:
Parameter settings:
Gateway A Gateway B Set IKEv1/v2 parameters Set IKEv1/v2 parameters ID Custom ID Custom Encryption algorithm AES128 Encryption algorithm Hash algorithm SHA1 Hash algorithm Diffie-Hellman key exchange Group2 Lifecycle 86400 IPsec policy Diffie-Hellman key exchange Lifecycle IPsec policy Same as that of gateway A Name Custom Name Custom Encapsulation ESP Encapsulation Same as that of gateway A 20 InHand VG710 InVehicle Gateway User Manual Encryption algorithm AES128 Authentication method SHA1 IPsec mode Tunnel mode Encryption algorithm Authentication method IPsec mode IPsec tunnel configuration IPsec tunnel configuration Address where gateway B Address where gateway A Peer address Peer address establishes the IPsec service establishes the IPsec service Interface for establishing the Interface for establishing the Interface Interface IPsec service IPsec service IKE version IKE version used IKE version Authentication method Shared key method Authentication Same as that of gateway A Local subnet Local subnet IP address of the subnet of IP address of the subnet of Peer subnet Peer subnet IP address of the subnet of IP address of the subnet of gateway A gateway B gateway B gateway A Detailed configuration steps:
1. Configure gateway A and gateway B.
(1) Add IKE and IPsec policies, and click Apply & Save.
(2) Add IPsec tunnels and click Apply & Save. 21 InHand VG710 InVehicle Gateway User Manual 2. Access the IPsec status page. The IPsec VPN is established successfully if the page is shown as below. Note:
22 InHand VG710 InVehicle Gateway User Manual The IPsec profile does not need to be configured for establishing an IPsec VPN, but needs to be configured for establishing a DM VPN. 5.3.2 GRE The Generic Routing Encapsulation (GRE) protocol can be used to encapsulate datagrams of some network layer protocols, so that these encapsulated datagrams can be transmitted on the IPv4 network. Scenario: GRE is enabled for VG710_A and VG710_B through the public network. Method for enabling GRE for transmission channels of VG710_A and VG710_B:
1. Click "VPN >> GRE" and then click Add. 2. Set "Index" as required. Select "Point to Point" or "Subnet" for "Network Type". Set "Local Virtual IP" and "Peer Virtual IP", ensuring that they are on the same network segment. Enter the source and peer IP addresses or interfaces and the key. Click Apply & Save. 23 InHand VG710 InVehicle Gateway User Manual 3. Set VG710_B in the same way. The virtual and peer IP addresses of VG710_B must correspond to those of VG710_A, and the key must be the same as that of VG710_A. 5.3.3 L2TP Add. The Layer 2 Tunneling Protocol (L2TP) is an industrial-standard Internet tunneling protocol used to encrypt network data streams. Method for settings when the gateway is used as an L2TP client:
1. Click "VPN >> L2TP >> L2TP Client >> L2TP Class", enter a name of an L2TP class, and click 2. Configure the pseudowire class: Enter a name of any pseudowire class. "L2TP Class" is the same as that on the "L2TP Class" page. Set "Source Interface" to the interface connecting to the server. Select L2TPV2 for "Protocol" and click Add. 24 InHand VG710 InVehicle Gateway User Manual 3. Set L2TPV2 tunnel parameters: Enter the server's domain name or IP address for "L2TP Server".
"Pseudowire Class" is the same as that on the "Pseudowire Class" page. Enter the user name and password created on the server. Set other parameters as required. Click Apply & Save. 4. After gateway A and gateway B are configured, access the L2TP status page to view the L2TP connection status. 5.3.4 OpenVPN 25 InHand VG710 InVehicle Gateway User Manual OpenVPN is realized based on the application-layer VPN of the OpenSSL library. It supports multiple authentication methods such as the certificate, key, and user name/password. Compared with the traditional VPN, it is simpler and easier to use. Authentication methods:
Authentication method Operation on the web page None No authentication is required. User name/password Enter the user name and password created on the OpenVPN server, click
"VPN >> Certificate Management", and import the CA certificate, public key, and private key for authentication. Pre-shared key Enter the pre-shared key created on the OpenVPN server. Click "VPN >> Certificate Management" and import the CA certificate, public key, and private key. Enter the user name and password created on the OpenVPN server, click
"VPN >> Certificate Management", and import the CA certificate, public key, and private key for authentication. Enter the pre-shared key created on the OpenVPN server, click "VPN >>
Certificate Management", and import the CA certificate, public key, and private key for authentication. Enter the pre-shared key, user name, and password created on the OpenVPN server, click "VPN >> Certificate Management", and import the CA certificate, public key, and private key for authentication. Digital certificate Digital certificate/user name/password Digital certificate/TLS authentication Digital certificate/TLS authentication/user name/password Method for settings when the gateway is connected to the OpenVPN server as a client:
OpenVPN can be configured manually, or OpenVPN configurations can be imported. In the following example, the authentication type is a digital certificate. 1. Set the OpenVPN parameters for the gateway as shown in the figure below, ensuring that the network parameters at both ends of the tunnel are consistent. Click Apply & Save. 26 InHand VG710 InVehicle Gateway User Manual 2. Select a digital certificate for "Authentication Type", click "VPN >> Certificate Management", and import the CA certificate, public key, and private key. 3. Click Apply & Save. Return to the "Status" page and view the tunnel status. Certificates can be imported or exported on this page. Certificates are used for IPsec and OpenVPN 5.3.5 Certificate Management services. Method for importing a certificate:
Click "VPN >> Certificate Management >> Browse", select the certificate obtained from the certificate server, click Import XX Certificate, and then click Apply & Save. 27 InHand VG710 InVehicle Gateway User Manual If no local certificate is available, check "Enable SCEP (Simple Certificate Enrollment Protocol)" to apply for a certificate online. Method for applying for a certificate for the gateway online:
1. Click "VPN >> Certificate Management". Check "Enable SCEP (Simple Certificate Enrollment Protocol)" and "Force to re-enroll". Enter the certificate protection key and confirm it. Enter the URL of the certificate server, the certificate name, and the FQDN. Click Apply & Save. 2. After the server issues the certificate, check the application status. If the application status is
"Completion", the certificate application succeeds. 28 InHand VG710 InVehicle Gateway User Manual 5.4 Services 5.4.1 DHCP (Automatic IP Address Allocation) DHCP uses the client/server communication mode. The client submits a configuration application to the server, and the server returns the IP address assigned to the client to realize the dynamic configuration of the IP address. The DHCP server and DHCP forwarding function are mutually exclusive. Method for settings when the gateway is used as a DHCP server:
Click "Services >> DHCP >> DHCP Server". In the "DHCP Server" bar, check "Enable", select an interface, set the start and end IP addresses, click Add, and then click Apply & Save. 29 InHand VG710 InVehicle Gateway User Manual Method for settings when the gateway is used as a DHCP client:
Click "Services >> DHCP >> DHCP Client", select the gateway interface, and click Apply & Save. Method for enabling DHCP forwarding for the gateway:
DHCP forwarding is also referred to as a DHCP relay agent. It can process and forward DHCP information between different subnets and physical network segments. Click "Services >> DHCP >> DHCP Relay", check "Enable", enter the server address, select the gateway interface, and click Apply & Save. 5.4.2 DNS Save. The domain name service (DNS) is a distributed network directory service mainly used for mutual conversion between a domain name and an IP address. Method for enabling the DNS server for the gateway:
Click "Services >> DNS >> DNS Server", enter the address of the DNS server, and click Apply &
30 InHand VG710 InVehicle Gateway User Manual Method for enabling DNS forwarding for the gateway:
As a DNS agent, the gateway forwards DNS request and response messages between the DNS client and the DNS server, and replaces the DNS client for domain name resolution. If the DHCP service is enabled for the gateway, DNS forwarding is enabled by default and cannot be disabled. Click "Services >> DNS >> DNS Relay", check "Enable DNS Relay", set the mapping between the domain name and the IP address, click Add, and then click Apply & Save. After the settings are completed, when a DNS client on the LAN requests a host domain name in the list, the DNS agent server returns the corresponding IP address to the client. 5.4.3 DDNS The dynamic domain name server (DDNS) maps the dynamic IP address of the gateway to a fixed DNS. Each time a user connects to the Internet, the client program transmits the dynamic IP address of the host to the server program on the server host through information transfer. The server program provides the DDNS service and realizes dynamic domain name resolution. In this way, you can access the Internet by entering the domain name, even if the IP address is changed. 31 InHand VG710 InVehicle Gateway User Manual Method for enabling the DDNS service for the gateway:
1. If the Custom service is used, set "Method Name" as required, select "Custom" for "Service Type", and enter the DDNS expression
"http://user name:password@ddns.oray.com/ph/update?hostname=host name" of the server for "Url". This expression is only for reference. The actual URL is provided by the service provider (usually available on the official website of the service provider). Click Add. If a common domain name server other than the Custom service is used, set "Method Name" and
"Service Type" as required, enter the user name, password, and host name obtained from the server, and click Add. If "Disable" is selected, the DDNS service is not used. 2. Select the gateway interface, enter the name of the DDNS update method, click Add, and then click Apply & Save to apply the DDNS update method to the gateway interface. 3. Wait several minutes after the DDNS settings are applied and saved. Then ping the host name
(domain name) of the domain name server to confirm the successful application of the DDNS service. 32 InHand VG710 InVehicle Gateway User Manual 5.4.4 SMS The short message service (SMS) is enabled for gateway restart and manual dialup via SMS messages. Some gateways can receive alarm information in the SMS whitelist. Method for controlling gateway restart and manual dialup via SMS messages Click "Services >> SMS" and check "Enable". In the "SMS Access Control" bar, set "ID" as required, select "permit" for "Action", enter the phone number, and click Apply & Save. When you activate the dialup port via SMS, after the configuration is completed, you can send the reboot command to restart the gateway by using the mobile phone number, or send the cellular 1 ppp up/down command to make the gateway redial or interrupt the dialup. 33 InHand VG710 InVehicle Gateway User Manual 5.4.5 GPS Position: You can view the current positioning information. Method for enabling GPS for the gateway:
Click "Services >> Enable GPS", check "Enable", and click Apply & Save. By default, GPS is enabled for the gateway. Method for forwarding GPS data to the server over IP when VG710 is used as a client:
Click "Services >> GPS IP Forwarding", check "Enable", select "Client" for "Type", enter the server address and port in the "Destination IP Address" bar, click Add, and then click Apply & Save. 34 InHand VG710 InVehicle Gateway User Manual Method for forwarding GPS data over IP when VG710 is used as a server:
Click "Services >> GPS IP Forwarding", check "Enable", select "Server" for "Type", and click Apply
& Save. Method for forwarding GPS data by VG710 through a serial port:
35 InHand VG710 InVehicle Gateway User Manual Click "Services >> GPS Serial Forwarding", check "Enable", and select a serial port type based on the data transmission port used. Ensure that the baud rate, data bits, parity bit, and stop bit are the same as the current settings. Click Apply & Save. 5.4.6 QoS Quality of service (QoS) is a network security mechanism that enables a network to provide better services for designated network communication by using various basic technologies. It is a technology for solving problems such as network delays and blocking. Method for setting the egress maximum bandwidth for the gateway through QoS control:
Click "QoS >> Traffic Control >> Apply QoS", select the gateway interface, enter the egress maximum bandwidth, click Add, and then click Apply & Save. Method for applying the ingress and egress policies for the gateway through QoS control:
1. Add a network link classifier. Click "QoS >> Traffic Control >> Classifier", check "Any Packets", set the source and destination addresses of the link, select transmit protocols for QoS control, and click Add. 36 InHand VG710 InVehicle Gateway User Manual 2. Set transmission policies. Click "QoS >> Traffic Control >> Policy", enter a custom policy name for "Name", enter the classifier name for "Classifier", set the guaranteed bandwidth, maximum bandwidth, and policy priority, and click Add. 3. Click "QoS >> Traffic Control >> Apply QoS", select the gateway interface, enter the policy name for "Ingress Policy" and "Egress Policy", click Add, and then click Apply & Save. 5.4.7 Traffic Control Method for enabling traffic control for the gateway:
Click "Services >> Traffic Control", enable traffic control, set traffic control parameters, and click Apply & Save. After the settings are completed, the system generates an alarm, stops forwarding, or disables the interface when the traffic exceeds the limit according to the settings on this page. 37 InHand VG710 InVehicle Gateway User Manual 5.5 Firewall 5.5.1 ACL The access control list (ACL) is an access control technology based on packet filtering. It can filter the packets on the interface based on preset conditions and allow them to pass or discard them. Common scenario: By default, all devices on the LAN (bridge 1) can access the Internet, except the device with the IP address of 192.168.2.100. Method for setting VG710:
1. Click "Firewall >> ACL >> Add". Enter the ID and sequence number. A smaller sequence number indicates a higher priority. Select "deny" for "Action". Set "Source IP" to "192.168.2.100" and "Source Wildcard" to "0.0.0.0". Leave "Destination IP" empty, which indicates 0.0.0.0/0, that is, all IP addresses. Click Apply & Save. 2. Return to the ACL page, add the rule with the ID of 101 to the management rule of bridge 1, and click Add. Click Apply & Save. 38 InHand VG710 InVehicle Gateway User Manual 5.5.2 NAT Network address translation (NAT) can be used when some hosts on a private network have been assigned with local IP addresses (that is, private IP addresses used only on the private network), but expect to communicate with hosts on the Internet (without encryption). Common scenario: A user expects to access a camera on the LAN of the device through the public network to view the current driving conditions of the vehicle. The camera address is 192.168.2.100, and the open port 18000 provides video services. 1. Click "Firewall >> NAT", and select "DNAT" for "Action", and "Outside" for "Source Network". Select "IP PORT to IP PORT" or "INTERFACE PORT to IP PORT" for "Translation Type". The public IP address obtained through dial-up is not fixed, so "INTERFACE PORT to IP PORT" is more convenient. Select "TCP" for "Transmit Protocol" because video services are transmitted over TCP. Select "cellular 1" (dialup interface for the cellular network) for "Interface" and set "Port" to "20000". Set "IP Address" and "Port" under "Translated Address" to "192.168.200" and "18000" respectively. Click Apply & Save. The gateway redirects the TCP service destined for port 20000 of the cellular 1 interface to the internal IP address 192.168.2.100 and port 18000, to enable access to the internal services. 39 InHand VG710 InVehicle Gateway User Manual 5.5.3 MAC-IP Binding After MAC-IP binding, the PC can access the public network through the gateway only by using the IP address bound to the MAC address of the PC. Method for binding the MAC address and IP address of a connected device:
1. Click "Firewall >> ACL" and select "Block" for "Default Filter Policy". 2. Click "Firewall >> MAC-IP Binding", check "Enable", enter the MAC address and IP address of the connected device, click Add, and click Apply & Save. 40 InHand VG710 InVehicle Gateway User Manual 5.6 Routing 5.6.1 Static Routing Set the destination network, subnet mask, and interface or gateway as required. 5.6.2 Dynamic Routing topology is shown below. Scenario: Enable dynamic routing between two LANs for mutual communication between them. The 5.6.2.1 RIP 41 InHand VG710 InVehicle Gateway User Manual The Routing Information Protocol (RIP) is a simple internal dynamic routing protocol mainly used on small-scale networks. scenario:
Method for enabling dynamic routing between VG710_A and VG710_B over RIP in the 1. Configure VG710_A. Click "Routing >> Dynamic Routing >> RIP", check "Enable", and configure VG710_A in the "Network" bar to announce the routing entry of VG710_A. 2. Configure VG710_B. 42 InHand VG710 InVehicle Gateway User Manual 3. After the configuration is completed, check whether PC 1 can communicate with PC 2. If yes, the dynamic route is added successfully. The RIP route learned by VG710_B is shown in the figure below. 5.6.2.2 OSPF used on large-scale networks. scenario:
routing entry of VG710_A. The Open Shortest Path First (OSPF) protocol is a link-status-based internal gateway protocol mainly Method for enabling dynamic routing between VG710_A and VG710_B over OSPF in the 1. Configure VG710_A. Click "Routing >> Dynamic Routing >> OSPF", check "Enable", enter a valid IP address for "Router ID", and configure VG710_A in the "Network" bar to announce the 2. Set parameters for VG710_B. 43 InHand VG710 InVehicle Gateway User Manual 3. After the configuration is completed, check whether PC 1 can communicate with PC 2. If yes, the dynamic route is added successfully. The OSPF route learned by VG710_B is shown in the figure below. 5.6.2.3 BGP scenario:
number" as required. Method for enabling dynamic routing between VG710_A and VG710_B over BGP in the 1. Configure VG710_A. Click "Routing >> Dynamic Routing >> BGP", check "Enable", and set "AS 2. In the "Neighbor" bar, click Add, enter the IP address 192.168.1.2 of VG710_B, set "AS number"
as required, and click Apply & Save. 44 InHand VG710 InVehicle Gateway User Manual 3. Enter a valid IP address for "Router ID", configure VG710_A in the "Network" bar, and click Add, to announce the routing entry of VG710_A. Then click Apply & Save. 4. Set parameters for VG710_B. The parameters are the same as or corresponding to those of VG710_A. 5. After the configuration is completed, check whether PC 1 can communicate with PC 2. If yes, the dynamic route is added successfully. The BGP route learned by VG710_B is shown in the figure below. 45 InHand VG710 InVehicle Gateway User Manual 5.7 Link Backup 5.7.1 SLA fails. The service level agreement (SLA) is used to detect whether the link between the gateway and the ISP Method for adding an SLA entry for the gateway:
Click "Link Backup >> SLA >> Add", enter the detected IP address for "Destination Address", set other parameters as required, click Add, and then click Apply & Save. Timeout (ms) indicates the duration for determining a detection failure. Consecutive indicates the number of detection failures resulting in a link failure. 5.7.2 Track Currently, linkage is enabled between the track module and the following application modules: VRRP, static routing, and interface backup. If detection succeeds, the corresponding track entry is in the Positive state. If detection fails, the corresponding track entry is in the Negative state. Method for adding a track entry for VG710:
46 InHand VG710 InVehicle Gateway User Manual Click "Link Backup >> Track >> Track", set "Index" as required, select "sla", "interface", or "vrrp" for
"Type", set "SLA/VRRP ID" based on the ID in the SLA list, set "Negative Delay (s)" and "Positive Delay (s)" as required, click Add, and then click Apply & Save. Negative Delay (s): In case of an abnormal state, switching can be delayed based on the delay setting Positive Delay (s): When a failure is recovered, switching can be delayed based on the delay setting (0
(0 indicates immediate switching). indicates immediate switching). Method for adding an IPsec track entry for VG710:
Click "Link Backup >> Track >> Track" and set "Index" as required. "positive-start/negative-stop"
means starting the IPsec service when the track detection state is Positive and stopping the IPsec service when the track detection state is Negative. 47 InHand VG710 InVehicle Gateway User Manual 5.7.3 VRRP Scenario: Multiple gateways are connected to a network at the same time. Gateway A acts as the host, and gateway B acts as a backup for gateway A. When gateway A fails, gateway B temporarily Host A uses the VRRP backup group comprising gateway A and gateway B as its default gateway to replaces gateway A as the host. 1. Networking requirement access host B on the Internet. Information of the VRRP backup group:
The backup group ID is 1. The IP address of the virtual gateway of the backup group is 10.5.16.88. Gateway A acts as the master gateway. Gateway A acts as a backup gateway that can be preempted. 2. Networking diagram Gateway Ethernet port connected to host A IP address of the port connected to host A Priority Work mode 48 InHand VG710 InVehicle Gateway User Manual bridge 1 bridge 1 10.5.16.80 10.5.16.81 110 100 Preemption Preemption Method for settings when VG710_A acts as the master gateway and VG710_B as a backup VG710_A VG710_B gateway:
1. Configure VG710_A. Click "Link Backup >> VRRP", set "Virtual Route ID" as required, select the gateway interface of VG710_A, enter the virtual IP address, set the interface priority to 110, and click Add. In the navigation tree, click "Link Backup >> VRRP >> Status" and view the VRRP status. 2. Configure VG710_B. Click "Link Backup >> VRRP", set the interface priority to 100, and click Add. In the navigation tree, click "Link Backup >> VRRP >> Status" and view the VRRP status. 49 InHand VG710 InVehicle Gateway User Manual Under normal circumstances, VG710_A performs gateway functions. When VG710_A is shut down or fails, VG710_B performs gateway functions. The preemption mode is intended to enable VG710_A to continue to act as the master gateway after it recovers. 5.7.4 Interface Backup Scenario: VG710 accesses the Internet via Wi-Fi, and an interface backup is created to enable VG710 to access the Internet through dial-up upon Wi-Fi failure. The topology is shown below. Method for creating an interface backup for the gateway:
1. Enable VG710 to access the Internet via Wi-Fi. 2. Click "Link Backup >> SLA >> SLA >> Add" to add an ICMP detection entry. Set the IP address to the host address that can be detected over ICMP on the public or private network, for example, the public IP address 118.122.120.22. Click Apply & Save. 50 InHand VG710 InVehicle Gateway User Manual 3. Click "Link Backup >> Track >> Track >> Add" to add a track entry. Select "sla" for "Type" and
"dot11radio1" for "Interface", click Add, and then click Apply & Save. 4. Click "Link Backup >> Interface Backup >> Add", select "dot11radio1" for "Main Interface" and
"cellular1" for "Backup Interface", and click Apply & Save. 5. Click "Routing >> Static Routing >> Add" and add two routes for network access through the
"dot11radio1" and "cellular1" interfaces. A smaller value of "Distance" indicates a higher priority. 51 InHand VG710 InVehicle Gateway User Manual 6. Trigger a Wi-Fi failure. According to the preset link detection policy, VG710 accesses the Internet through dial-up via the cellular port, and when Wi-Fi recovers, immediately switches to Wi-Fi for Internet access. 5.8 Wizards operations. 5.8.1 New Cellular connected to the network. The "Wizards" module incorporates some common communication parameters, simplifying the After a common network interface card (NIC) is inserted, click "Wizards >> New Cellular >> Apply
& Save" and access the status page to view the network connection status of the device. The device is 52 InHand VG710 InVehicle Gateway User Manual 5.8.2 New IPsec Tunnel A dedicated virtual tunnel is established between the gateway and other devices or cloud platforms on the network. Method for establishing an IPsec tunnel for the gateway:
Click "Wizards >> New IPsec Tunnel", set "Map Interface" to an interface ("bridge": bridge interface;
"cellular": dialup interface; "dot11radio": Wi-Fi interface) for which you want to establish a tunnel, enter the peer IP address for "Destination Address", and enter the subnet IP addresses and masks at both ends of the tunnel. In Phase 1, enter the IDs at both ends of the tunnel and the connection key, and click Apply & Save. 53 InHand VG710 InVehicle Gateway User Manual support personnel. 5.8.3 IPsec Experts' Configuration This function is available only for specific users. To activate this function, contact the technical 5.8.4 New L2TPv2 Tunnel Method for creating an L2TPv2 tunnel for the gateway:
Set the parameters of the L2TP server and the local/remote addresses. Click Apply & Save. 54 InHand VG710 InVehicle Gateway User Manual 5.8.5 New Port Mapping Port mapping is to map a port of a host on the intranet to a port of a host on the extranet to provide corresponding services. When a user accesses the port on the extranet, the server automatically maps the request to the internal machine on the corresponding LAN. Scenario: Users on the extranet cannot directly access a web server on the intranet. In this case, a port mapping can be created on the gateway so that the gateway automatically transfers the data to port 80 of the web server on the intranet when a user on the extranet accesses port 1000 via the cellular interface of the gateway. Method for creating a port mapping for the gateway:
Click Wizards >> New Port Mapping". Enter the gateway interface for "Outside Interface", gateway port for "Service Port", IP address of the internal host for "Internal Address", and port ID of the internal host for "Internal Port". Click Apply & Save. 55 InHand VG710 InVehicle Gateway User Manual 56 InHand VG710 InVehicle Gateway User Manual 6 APP Management This function is to be improved. 57 InHand VG710 InVehicle Gateway User Manual 7 Connecting the Gateway to a Cloud Platform 1. Click "Administration >> Device Manager >> Device Manager", check "Device Manager Enable", select the server address of the cloud platform, enter the registered account and license plate number of the cloud platform, and click Apply & Save. 2. Click "Status". "Connected" indicates that the gateway is successfully connected to the cloud platform. 58 InHand VG710 InVehicle Gateway User Manual 8 Industrial Ports (Serial Ports) The industrial ports of VG710 include RS232 serial ports, RS485 serial ports, and IO ports. 8.1 DTU data. RS232 provides full-serial communication, enabling hardware-based traffic control. RS485 provides half-duplex communication, enabling remote transmission of serial communication Method for setting web pages when the gateway is used as a DTU:
RS-485 I/O RS-232 1. Enable DTU 1 (RS232) or DTU 2 (RS-485). 2. Set the connection parameters of the gateway interface and industrial device. Communication is available only when the parameters at both ends of the network link are consistent. 59 InHand VG710 InVehicle Gateway User Manual 3. Set the IP address and transmit protocol (TCP or UDP) of the server. 4. Check that the gateway-connected PC and the server exchange data through DTU. 60 InHand VG710 InVehicle Gateway User Manual 8.2 IO Ports IO ports provide six analog inputs, six digital inputs, and four digital outputs. The analog and digital inputs share the ports. The digital parameters correspond to two states: HIGH (1) and LOW (0). 61 InHand VG710 InVehicle Gateway User Manual 62 InHand VG710 InVehicle Gateway User Manual 9 System Management 9.1 System device. Click "Administration >> System >> Status" and view the current system and network status of the Click "Basic Setup" and modify the system language and device name. 9.2 System Time To ensure the coordination between the device and other devices, set the system time accurately. 63 InHand VG710 InVehicle Gateway User Manual Manual time synchronization: Click "Administration >> System Time >> System Time >> Sync Time" to ensure consistency between the gateway time and host time. Alternatively, click "Administration >> System >> Status" to synchronize the time. Automatic time synchronization: Click "Administration >> System Time >> SNTP Client or NTP Server" and check "Enable" to synchronize the time between the gateway and the SNTP or NTP server. After NTP is enabled, the gateway can synchronize time for all devices on the network. 64 InHand VG710 InVehicle Gateway User Manual 9.3 Management Services When the gateway requires the HTTP, HTTPS, TELNET, and SSH functions, click "Administration >>
Management Services", enable the services, and click Apply & Save. 65 InHand VG710 InVehicle Gateway User Manual 9.4 User Management Click "Administration >> User Management" and create users, modify passwords, or delete users on Superuser: By default, only one superuser is automatically created by the system, with the user name of adm and the default password of 123456. It has full access rights for the Common user: A common user is created by the superuser. It can view or modify gateway Note: You cannot delete the superuser (adm) or modify its user name, but can modify its the user management page. Superuser and common user:
gateway. configurations. password. 9.5 AAA Authentication, authorization, and accounting (AAA) is a security management mechanism for access control in network security, which provides three security services: authentication, authorization, and accounting. It provides modular methods for the following services:
Authentication: Verify whether a user has the right for network access. Authorization: Authorize a user to use specific services. Accounting: Record network resource usage of a user. 66 InHand VG710 InVehicle Gateway User Manual You can use only one or two of the security services provided by AAA. For example, if a company only expects to authenticate employees when they access specific resources, the network administrator only needs to configure the authentication server. However, if the company expects to record the network usage of employees, the accounting server must be configured. AAA usually works in the client/server structure, which is highly scalable and is convenient for centralized management of user information, as shown in the figure below. Note: Radius, Tacacs+, and LDAP indicate authentication and authorization servers. Local indicates the local user name and password of the gateway. 9.5.1 Radius The Remote Authentication Dial In User Service (Radius) is a distributed information exchange protocol based on the client/server structure. It protects the network from unauthorized access, and is usually used in various network environments that require high security and allow remote user access. Method for enabling the Radius server for the gateway:
Click "Administration >> AAA >> Radius". In "Server List", enter the server address (domain name/IP address), port ID, and authentication key, click Add, and then click Apply & Save. 67 InHand VG710 InVehicle Gateway User Manual 9.5.2 Tacacs+
The Terminal Access Controller Access Control System + (Tacacs+) protocol is similar to the Radius protocol. It uses the client/server mode for communication between the network access server (NAS) and the Tacacs+ server. However, Tacacs+ works based on TCP, and Radius works based on UDP. The Tacacs+ protocol is mainly used for AAA of end users and Point-to-Point Protocol (PPP) and virtual private dial-up network (VPDN) access users. Its typical application is to authenticate, authorize, and perform accounting for an end user who needs to log in to the device for operations. As a Tacacs+ client, the device sends the user name and password to the Tacacs+ server for verification. After authentication and authorization, the user can log in to the device for operations. Method for enabling the Tacacs+ server for the gateway:
Click "Administration >> AAA >> Tacacs+". In "Server List", enter the server address (domain name/IP address), port ID, and authentication key, click Add, and then click Apply & Save. 9.5.3 LDAP The main advantage of the Lightweight Directory Access Protocol (LDAP) lies in its quick response to users' search operations. For example, massive user authentication operations may be performed concurrently. If a database is used, because the database is divided into various tables, to meet this 68 InHand VG710 InVehicle Gateway User Manual simple authentication requirement, the database must be searched each time, along with synthesis and filtering. This results in low efficiency. LDAP is equivalent to one table, and requires only the user name and password, with some other parameters, which is quite simple. It can meet the authentication requirement regarding the efficiency and structure. Method for enabling the LDAP server for the gateway:
Click "Administration >> AAA >> LDAP". In "Server List", enter any name for "Name", enter the server address (domain name/IP address) and port ID, and enter the base DN obtained from the server. Set the user name and password for accessing the server. Select "None", "SSL", or "StartTLS" for
"Security". Click Add, and then click Apply & Save. 9.5.4 AAA Authentication AAA authentication methods:
No authentication (none): No validity check is performed. Generally, this method is not used. Local authentication (local): User information is configured on the NAS. Local authentication is fast, which can reduce the operational costs, but the information storage amount is limited by hardware. Remote authentication: User information is configured on the authentication server. Remote authentication is supported over Radius, Tacacs+, and LDAP. AAA authorization methods:
No authorization (none): No authorization is performed for users. Local authorization (local): Authorization is performed based on the properties configured by the NAS for the local account. Tacacs+ authorization: Users are authorized by the Tacacs+ server. Authorization after successful Radius authentication: Authorization is bound to authentication, 69 InHand VG710 InVehicle Gateway User Manual and cannot be performed independently over Radius. LDAP authorization Method for enabling authentication and authorization for the gateway:
Click "Administration >> AAA >> AAA Settings". 1, 2, and 3 are corresponding to Radius, Tacacs, ad LDAP respectively. Authentication entries 1, 2, and 3 must be corresponding to authorization entries 1, 2, and 3 respectively. When all of radius, tacacs+, and local are set, the priority sequence is as follows: 1 > 2 > 3. 9.6 Configuration Management Method for importing configurations: Click "Administration >> Config Management >> Config Management >> Browse", select a configuration file, and click Import to import the configuration file Method for backing up current running configurations to the PC (common): Click Backup to the gateway. running-config. Method for backing up the startup file to the PC: Click Backup startup-config. Method for restoring default configurations: Click Restore default configuration and then click OK. 70 InHand VG710 InVehicle Gateway User Manual 9.7 SNMP 9.7.1 SNMP Currently, the SNMP Agent of VG710 supports SNMPv1, SNMPv2c, and SNMPv3. SNMPv1 and SNMPv2c use community names for authentication. SNMPv3 uses user names and passwords for authentication. Method for enabling SNMP for VG710:
Click "Administration >> SNMP >> SNMP", check "Enable", select "v1c" for "v2c" for "SNMP Version", and click Apply & Save. If v3c is selected, the corresponding user and user group need to be configured. Enter any name for
"Groupname", select a security level, and click Add. Enter any name for "Username", select the new group name for "Groupname", set "Authentication" and "Authentication password", click Add, and then click Apply & Save. 71 InHand VG710 InVehicle Gateway User Manual 9.7.2 SnmpTrap (Alarm) The SNMP trap is a type of entrance. When this entrance is reached, the SNMP managed devices actively notify the NMS, instead of waiting for the polling of NMS. On an SNMP-enabled network, the agents on managed devices can report errors to the NMS anytime, without the need of waiting for the polling of NMS. The errors are reported to the NMS through traps. Method for enabling SnmpTrap for the gateway:
Click "Administration >> NMP >> SnmpTrap". Enter the IP address of the NMS. Enter the corresponding group name when v1c or v2c is selected, or the corresponding user name when v3c is selected, ensuring that the name consists of 132 characters. By default, the UDP port ID ranges from 1 to 65535. 9.7.3 SnmpMibs 72 InHand VG710 InVehicle Gateway User Manual In SNMP messages, management variables are used to describe the managed objects on the device. To uniquely identify the managed objects on the device, SNMP uses a hierarchical naming scheme to identify the managed objects The entire hierarchical structure is like a tree. The nodes of the tree represent the managed objects, as shown in the figure below. Each node can be uniquely identified by a path starting from the root. The management information base (MIB) is used to describe the hierarchical structure of the tree. It is a set of standard variable definitions for the monitored network device. In the above figure, managed object B can be uniquely determined based on a string of numbers {1.2.1.1}, which form the object identifier (OID) of the managed object. Method for downloading a SnmpMibs file to the PC via the gateway:
Click "Administration >> SNMP >> SnmpMibs", select a folder, and click download to download it to the PC. Find the folder on the PC and import it to the NMS. 9.8 Alarm 73 InHand VG710 InVehicle Gateway User Manual The alarm function enables users to identify gateway abnormalities in time. When an abnormality occurs, the gateway reports an alarm. You can select system-defined abnormalities and choose an appropriate notification way to obtain the abnormality information. All alarms are recorded in alarm logs so that users can identify abnormalities and perform troubleshooting in time. Alarm states:
Raise: indicates that the alarm has been generated but not been confirmed. Confirm: indicates that the alarm cannot be solved currently. All: indicates all generated alarms. Alarm levels:
EMERG: The device undergoes a serious error that causes a system reboot. CRIT: The device undergoes an unrecoverable error. WARN: The device undergoes an error that affects system functions. NOTICE: The device undergoes an error that affects system performance. INFO: A normal event occurs.
(1) Status: Click "Administration >> Alarm >> Status" and view all alarms generated in the system since power-on.
(2) Alarm Input: Select an alarm type as required. When this item is abnormal, an alarm is generated.
(3) Alarm Output: When an alarm is generated, the system automatically sends the alarm content to the destination email address via an email. This function is not available for common users. Set the sender mail address in "Email Alarm" and the receiver mail address in "Mail Address". "Mail Server IP/Name" can be found on the browser (for example, enter "smtp.exmail.qq.com" if you use a Tencent Enterprise mailbox.) 74 InHand VG710 InVehicle Gateway User Manual
(4) Alarm Map: Alarms can be received in two ways: command line interface (CLI) (console interface) and Email. Some devices support SMS alarms. To enable email-based mapping, enable and set the email address on the "Alarm Output" page. 9.9 System Logs Method for viewing system logs:
Click "Administration >> System Log" to view system logs. This page also provides the following operations: "Clear Log", "Download Log File", "Download Diagnose Data", "Clear History Log", and "Download History Log". History logs are those stored for extended time as specified on the "System Log" page. The diagnose data file is encrypted, because the gateway configuration information is downloaded together with the diagnose data. You need to decrypt the file with the decryption tool provided by InHand. 75 InHand VG710 InVehicle Gateway User Manual The storage capacity of the gateway is limited (512 KB by default). To save all the logs, you need to use a remote log server (for example, Kiwi Syslog Daemon). Set the address and port of the log server on the web page. The gateway uploads all the system logs to the remote log server. 9.10 System Upgrade system after the upgrade is completed. Click "Administration >> Upgrade >> Browse", select an upgrade file, and click Upgrade. Restart the 76 InHand VG710 InVehicle Gateway User Manual During the software upgrade, do not perform any operation on the web page; otherwise, the software upgrade may be interrupted. 9.11 System Reboot Click "Administration >> Reboot >> OK to reboot the system. Note:
77 InHand VG710 InVehicle Gateway User Manual 10 Diagnostic Tools Diagnostic tools are used to detect the network connection of the gateway: Ping, Traceroute, Tcpdump, and Link Speed Test. Ping: It is used to detect the external network connection of the device. Enter any common website in China for "Host" and click "Ping". If data transmission occurs, the network is connected properly. Traceroute: Enter the IP address of the peer host and click "Trace" to detect the route connection. Select an interface ("any" or "bridge1"), set "Capture Number", and click Start Capture >> Stop Tcpdump:
Capture >> Download Capture File. 78 InHand VG710 InVehicle Gateway User Manual Download wireshark from the browser to open the downloaded file and analyze the messages to understand the network connection of the interface. Link Speed Test: Upload and download files to test the link speed. 79 InHand VG710 InVehicle Gateway User Manual This device complies with Industry Canadas license-exempt RSSs. Operation is subject to the English:
following two conditions:
(1) This device may not cause interference; and operation of the device. French:
(2) This device must accept any interference, including interference that may cause undesired Le prsent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence. L'exploitation est autorise aux deux conditions suivantes : (1) l'appareil ne doit pas produire de brouillage, et (2) l'utilisateur de l'appareil doit accepter tout brouillage radiolectrique subi, mme si le brouillage est susceptible d'en compromettre le fonctionnement. FCC warning:
Any Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment. This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. Note: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense. 80 InHand VG710 InVehicle Gateway User Manual FCC Radiation Exposure Statement This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment .This equipment should be installed and operated with minimum distance 20cm between the radiator& your body. transmitter. This transmitter must not be co-located or operating in conjunction with any other antenna or 81
1 2 3 | Internal Photos | Internal Photos | 1.49 MiB | March 27 2020 / September 23 2020 | delayed release |
1 2 3 | External Photos | External Photos | 1.35 MiB | March 27 2020 / September 23 2020 | delayed release |
1 2 3 | Label and Location | ID Label/Location Info | 144.81 KiB | March 27 2020 |
InVehicle Gateway www. inhandnetworks.com 9-36V=1.2-0.3A Cr For INA VG710 FS39 VF71012345654321 00:18:05:00:12:34-35 867377028023236 Wifi-xxxxxx/12345678 This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: |P: 192.168.2.1
(1)This device may not cause harmful interference. User/Pwd: adm/xxxxxx
(2)this device must accept any interference received, e . including interference that may cause undesired operation. Made In China Date:05.2019 Manufacturer: InHand Networks
1 2 3 | Agent Authorization Rev 1.0 | Cover Letter(s) | 14.69 KiB | March 27 2020 |
Beijing InHand Networks Technology Co., Ltd. Agent Authorization Company: Beijing InHand Networks Technology Co., Ltd. Address: Room 501, floor 5, building 3, yard 18, ziyue road, chaoyang district, Beijing Product Name: InVehicle Gateway Model Number(s): VG710 Product Description: LTE, GPS, 2.4G WiFi&5G WiFi Gateway We authorize MiCOM Labs Inc., 575 Boulder Court, Pleasanton, California 94566, USA, to act on our behalf on all matters concerning the certification of above named equipment. We declare that MiCOM Labs Inc. is allowed to forward all information related to the approval and certification of equipment to the regulatory agencies as required and to discuss any issues concerning the approval application. Any and all acts carried out by MiCOM Labs on our behalf shall have the same effect as acts of our own. Date: 2020/03/10 Signature:
Name:
Jichi Gu Title:
Certification Engineer Company: Beijing InHand Networks Technology Co., Ltd.
1 2 3 | Block Statement | Cover Letter(s) | 89.50 KiB | March 27 2020 |
Declaration letter Beijing InHand Networks Technology Co., Ltd. Our VG710 device does not have bluetooth capability on either hardware or software currently. Therefore, I need to apply for exemption of bluetooth function test. But in the future if the customer needs, we will add the bluetooth function and then add the test of bluetooth part. Signature:
Printed name/title:Jichi Gu/ Certification Engineer Address: Room 501, floor 5, building 3, yard 18, ziyue road, chaoyang district, Beijing, P.R.China Dear Sir, Thank you!
1 2 3 | FCC Software Configuration Control Declaration Rev1.1 | Cover Letter(s) | 75.13 KiB | March 27 2020 |
Beijing InHand Networks Technology Co., Ltd. FCC Software Configuration Control Declaration Date: March 18, 2020 Federal Communications Commission 7435 Oakland Mills Road Columbia, MD 21046 USA Attn: OET Dept. Product/ Model Number:
Regarding FCC Country Code Selection guidelines identified in KDB 594280 v02r01
. All applications for equipment authorization for transmitters that can have radio parameters, or other technical parameters, reported to the Commission set by software must have an attestation indicating that no third party will have software, or configuration control, to program the device out of compliance of the technical rules under which it has been certified. We declare that no third party will have software, or configuration control, to program the device out of compliance of the technical rules under which it has been certified. Name: Jichi Gu Title: Certification Engineer Signature of applicant Date: 2020-03-18 VG710_FCC Software Configuration Control Declaration Rev1.1.docx
1 2 3 | FCC Short & Long Term Confidentiality | Cover Letter(s) | 78.51 KiB | March 27 2020 |
Beijing InHand Networks Technology Co., Ltd. Office of Engineering Technology Federal Communications Commission 7435 Oakland Mills Road Columbia, MD 21046 USA Date: 2020/03/26 Subject; Request for Confidentiality FCC ID: 2AANYVG710 To Whom It May Concern, Pursuant to the provisions of the Commissions rules Title 47 Sections 0.457 and 0.459, we are requesting the Commission to withhold the following attachment(s) as confidential documents from public disclosure indefinitely. These documents contain detailed system and equipment descriptions and are considered as proprietary information in operation of the equipment. The public disclosure of these documents might be harmful to our company and would give competitors an unfair advantage in the market. Schematic Diagram Block Diagram Operational Description BOM List Tune-up Procedure External Photos Test Setup Photos Internal Photos User Manual In additional to above mentioned documents, in order to comply with the marketing regulations in Title 47 CFR 2.803 and the importation rules in Title 47 CFR 2.1204, while ensuring that business sensitive information remains confidential until the actual marketing of newly authorized devices, we request Short Term Confidentiality of the following attachment(s);
OR For 45 days, pursuant to Public Notice DA 04-1705. For 180 days pursuant to KDB 726920 D01. It is our understanding that all measurement test reports, FCC ID label format and correspondence during the certification review process cannot be granted as confidential documents and this information will be available for public review once the grant of equipment authorization is issued. Sincerely, Signature:
Name: Jichi Gu Title: Certification Engineer
1 2 3 | Part 15E InHand Report wifi MIMO UNII-1&UNII-3 Part 1 | Test Report | 4.92 MiB | March 27 2020 |
1 2 3 | Part 15E InHand Report wifi MIMO UNII-1&UNII-3 Part 2 | Test Report | 5.45 MiB | March 27 2020 |
1 2 3 | Part 15E InHand Report wifi MIMO UNII-1&UNII-3 Part 3 | Test Report | 5.77 MiB | March 27 2020 |
1 2 3 | Part 15E InHand Report wifi MIMO UNII-1&UNII-3 Part 4 | Test Report | 5.00 MiB | March 27 2020 |
1 2 3 | Part 15E InHand Report wifi MIMO UNII-1&UNII-3 Part 5 | Test Report | 3.60 MiB | March 27 2020 |
1 2 3 | Part 15E InHand Report wifi MIMO UNII-1&UNII-3 Part 6 | Test Report | 2.72 MiB | March 27 2020 |
frequency | equipment class | purpose | ||
---|---|---|---|---|
1 | 2020-03-27 | 5745 ~ 5825 | NII - Unlicensed National Information Infrastructure TX | Original Equipment |
2 | 2020-03-26 | 1860 ~ 1900 | PCB - PCS Licensed Transmitter | |
3 | 2412 ~ 2462 | DTS - Digital Transmission System |
app s | Applicant Information | |||||
---|---|---|---|---|---|---|
1 2 3 | Effective |
2020-03-27
|
||||
1 2 3 |
2020-03-26
|
|||||
1 2 3 | Applicant's complete, legal business name |
Beijing InHand Networks Technology Co., Ltd.
|
||||
1 2 3 | FCC Registration Number (FRN) |
0022847826
|
||||
1 2 3 | Physical Address |
Room 501, floor 5, building 3, yard 18, ziyue road chaoyang district, Beijing,China
|
||||
1 2 3 |
Room 501, floor 5, building 3, yard 18, ziyue road
|
|||||
1 2 3 |
Beijing, N/A
|
|||||
1 2 3 |
Beijing, N/A 100102
|
|||||
1 2 3 |
China
|
|||||
app s | TCB Information | |||||
1 2 3 | TCB Application Email Address |
c******@micomlabs.com
|
||||
1 2 3 | TCB Scope |
A4: UNII devices & low power transmitters using spread spectrum techniques
|
||||
1 2 3 |
B1: Commercial mobile radio services equipment in the following 47 CFR Parts 20, 22 (cellular), 24,25 (below 3 GHz) & 27
|
|||||
app s | FCC ID | |||||
1 2 3 | Grantee Code |
2AANY
|
||||
1 2 3 | Equipment Product Code |
VG710
|
||||
app s | Person at the applicant's address to receive grant or for contact | |||||
1 2 3 | Name |
J******** G******
|
||||
1 2 3 | Title |
Certification Engineer
|
||||
1 2 3 | Telephone Number |
15281********
|
||||
1 2 3 | Fax Number |
010-8********
|
||||
1 2 3 |
g******@inhand.com.cn
|
|||||
app s | Technical Contact | |||||
1 2 3 | Firm Name |
Beijing InHand Networks Technology Co., Ltd.
|
||||
1 2 3 | Physical Address |
China
|
||||
1 2 3 |
g******@inhand.com.cn
|
|||||
app s | Non Technical Contact | |||||
n/a | ||||||
app s | Confidentiality (long or short term) | |||||
1 2 3 | Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | Yes | ||||
1 2 3 | Long-Term Confidentiality Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | Yes | ||||
1 2 3 | If so, specify the short-term confidentiality release date (MM/DD/YYYY format) | 09/23/2020 | ||||
if no date is supplied, the release date will be set to 45 calendar days past the date of grant. | ||||||
app s | Cognitive Radio & Software Defined Radio, Class, etc | |||||
1 2 3 | Is this application for software defined/cognitive radio authorization? | No | ||||
1 2 3 | Equipment Class | NII - Unlicensed National Information Infrastructure TX | ||||
1 2 3 | PCB - PCS Licensed Transmitter | |||||
1 2 3 | DTS - Digital Transmission System | |||||
1 2 3 | Description of product as it is marketed: (NOTE: This text will appear below the equipment class on the grant) | InVehicle Gateway | ||||
1 2 3 | Related OET KnowledgeDataBase Inquiry: Is there a KDB inquiry associated with this application? | No | ||||
1 2 3 | Modular Equipment Type | Does not apply | ||||
1 2 3 | Purpose / Application is for | Original Equipment | ||||
1 2 3 | Composite Equipment: Is the equipment in this application a composite device subject to an additional equipment authorization? | Yes | ||||
1 2 3 | Related Equipment: Is the equipment in this application part of a system that operates with, or is marketed with, another device that requires an equipment authorization? | No | ||||
1 2 3 | Grant Comments | Output power listed is maximum combined conducted power. This device contains 20, 40 and 80 MHz signal bandwidth. The antennas used for this transmitter must be installed to provide a separation distance of at least 20 cm from all persons and must not be co-located or operating in conjunction with any other antenna or transmitter, except in accordance with FCC multi- transmitter product procedures. End-Users must be provided with transmitter operation conditions for satisfying RF exposure compliance. | ||||
1 2 3 | Power output listed is ERP for frequencies below 1GHz and EIRP for frequencies above 1GHz. The antenna used with this transmitter must be installed to provide a minimum separation distance of at least 20 cm from all persons and must not be co-located or operating in conjunction with any other antenna or transmitter, except in accordance with FCC multi- transmitter product procedures. End-users must be provided with operating procedures for satisfying RF exposure compliance. | |||||
1 2 3 | Output power listed is maximum combined conducted power. Device contains 20 and 40 MHz signal bandwidth. The antennas used for this transmitter must be installed to provide a separation distance of at least 20 cm from all persons and must not be co-located or operating in conjunction with any other antenna or transmitter, except in accordance with FCC multi- transmitter product procedures. End-Users must be provided with transmitter operation conditions for satisfying RF exposure compliance. | |||||
1 2 3 | Is there an equipment authorization waiver associated with this application? | No | ||||
1 2 3 | If there is an equipment authorization waiver associated with this application, has the associated waiver been approved and all information uploaded? | No | ||||
app s | Test Firm Name and Contact Information | |||||
1 2 3 | Firm Name |
Hunan Ecloud Testing Technology Co., Ltd.
|
||||
1 2 3 | Name |
B******** W******
|
||||
1 2 3 | Telephone Number |
+86 1********
|
||||
1 2 3 |
b******@hn-ecloud.com
|
|||||
Equipment Specifications | |||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
1 | 1 | 15E | 38 CC MO | 5180 | 5240 | 0.0525 | |||||||||||||||||||||||||||||||||||
1 | 2 | 15E | 38 CC MO | 5745 | 5825 | 0.0912 | |||||||||||||||||||||||||||||||||||
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
2 | 1 | 22H | 824.2 | 848.8 | 2.438 | 0.05 ppm | 245KGXW | ||||||||||||||||||||||||||||||||||
2 | 2 | 22H | 824.2 | 848.8 | 0.573 | 0.06 ppm | 237KG7W | ||||||||||||||||||||||||||||||||||
2 | 3 | 22H | 826.4 | 846.6 | 0.316 | 0.04 ppm | 4M13F9W | ||||||||||||||||||||||||||||||||||
2 | 4 | 22H | 826.5 | 846.5 | 0.261 | 0.02 ppm | 4M53G7D | ||||||||||||||||||||||||||||||||||
2 | 5 | 22H | 826.5 | 846.5 | 0.215 | 0.02 ppm | 4M53W7D | ||||||||||||||||||||||||||||||||||
2 | 6 | 22H | 829 | 844 | 0.252 | 0.02 ppm | 9M02G7D | ||||||||||||||||||||||||||||||||||
2 | 7 | 22H | 829 | 844 | 0.207 | 0.02 ppm | 9M02W7D | ||||||||||||||||||||||||||||||||||
2 | 8 | 24E | 1850.2 | 1909.8 | 1.849 | 0.02 ppm | 243KGXW | ||||||||||||||||||||||||||||||||||
2 | 9 | 24E | 1850.2 | 1909.8 | 0.684 | 0.1 ppm | 233KG7W | ||||||||||||||||||||||||||||||||||
2 | 1 | 24E | 1852.4 | 1907.6 | 0.419 | 0.01 ppm | 4M17F9W | ||||||||||||||||||||||||||||||||||
2 | 11 | 24E | 1860 | 1900 | 0.395 | 0.01 ppm | 18M0G7D | ||||||||||||||||||||||||||||||||||
2 | 12 | 24E | 1860 | 1900 | 0.318 | 0.01 ppm | 18M1W7D | ||||||||||||||||||||||||||||||||||
2 | 13 | 27 | 1712.4 | 1752.6 | 0.461 | 0.03 ppm | 4M13F9W | ||||||||||||||||||||||||||||||||||
2 | 14 | 27 | 1720 | 1745 | 0.46 | 0.01 ppm | 18M1G7D | ||||||||||||||||||||||||||||||||||
2 | 15 | 27 | 1720 | 1745 | 0.358 | 0.01 ppm | 18M0W7D | ||||||||||||||||||||||||||||||||||
2 | 16 | 27 | 699.7 | 715.3 | 0.217 | 0.01 ppm | 1M11G7D | ||||||||||||||||||||||||||||||||||
2 | 17 | 27 | 700.5 | 714.5 | 0.183 | 0.01 ppm | 2M79W7D | ||||||||||||||||||||||||||||||||||
2 | 18 | 27 | 704 | 711 | 0.217 | 0.01 ppm | 9M06G7D | ||||||||||||||||||||||||||||||||||
2 | 19 | 27 | 704 | 711 | 0.166 | 0.01 ppm | 9M06W7D | ||||||||||||||||||||||||||||||||||
2 | 2 | 27 | 782 | 782 | 0.183 | 0.01 ppm | 8M98G7D | ||||||||||||||||||||||||||||||||||
2 | 21 | 27 | 782 | 782 | 0.146 | 0.01 ppm | 8M98W7D | ||||||||||||||||||||||||||||||||||
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
3 | 1 | 15C | CC MO | 2412.00000000 | 2462.00000000 | 0.3160000 |
some individual PII (Personally Identifiable Information) available on the public forms may be redacted, original source may include additional details
This product uses the FCC Data API but is not endorsed or certified by the FCC