LTE 系统工具箱Release Notes

华诺LTE后台维护操作手册目录华诺LTE后台维护操作手册 (1)第一章后台维护常用工具介绍及安装步骤 (6)1.1后台维护常用工具概述 (6)1.2 BTS Site Manager (6)1.2.1 基本介绍 (6)1.2.2工具准备 (6)1.2.3主要功能 (7)1.2.4常用场景 (10)1.3 BTS Site Browser (10)1.3.1基本介绍 (10)1.3.2 工具准备 (11)1.3.3 主要功能 (11)1.3.4 常用场景 (14)1.4 Remotely (14)1.4.1基本介绍 (14)1.4.2工具准备 (14)1.4.3主要功能 (14)1.4.4常用场景 (15)1.5 Filezilla (16)1.5.1基本介绍 (16)1.5.2工具准备 (16)1.5.3主要功能 (17)1.5.4常用场景 (17)1.6 SecureCRT (17)1.6.1基本介绍 (17)1.6.2工具准备 (17)1.6.3主要功能 (18)1.6.4常用场景 (18)1.7 BTS LOG (20)1.7.1基本介绍 (20)1.7.2工具准备 (20)1.7.3主要功能 (20)1.7.4常用场景 (21)1.7.5其他备注 (21)1.8 Email (22)1.8.1基本介绍 (22)1.8.2工具准备 (22)1.8.3主要功能 (22)1.8.4常用场景 (22)1.9 PLSQL Developer (23)1.9.1基本介绍 (23)1.9.2工具准备 (23)1.10 Application Launcher Client (25)1.10.1基本介绍 (25)1.10.2主要功能 (25)1.11 NetAct (27)1.11.1基本介绍 (27)1.11.2工具准备 (27)1.11.3主要功能 (27)1.11.4常用场景 (27)第二章基站基础配置文件 (28)2.1 SCFC (28)2.2 Config (29)2.3 vendor (29)第三章基站文件备份指导 (30)3.1BTS Site manager备份文件 (30)3.2FileZilla备份文件 (31)3.3BTS Site Browser备份文件 (32)3.4Remote备份文件 (33)第四章基站参数的修改 (35)4.1单站修改 (35)4.1.1BTS Site manager修改参数 (35)4.1.2 直接修改SCFC和vendor等配置文件 (37)4.1.3通过网管修改参数 (38)4.2批量修改 (38)4.2.1网管修改参数NetAct（CM Editor & CM operations manager） (38)4.2.2编写plan脚本导入CM operations manager执行 (44)4.3基站参数修改常见问题 (44)第五章基站升级 (45)5.1网管升级 (45)5.2BTS Site Browser升级 (47)5.3BTS Site manager升级 (48)第六章告警提取及处理指导 (51)6.1常用告警提取方法 (51)6.1.1BTS Site manage告警提取 (51)6.1.2BTS Site Browser告警提取 (52)6.1.3Application launcher告警提取 (53)6.1.4PL\SQL告警提取 (55)6.2常见告警处理指导 (57)第七章常用log提取方法 (58)7.1Snapshot (58)7.1.1软件获取及安装 (58)7.1.2Snapshot log 获取方法 (58)7.1.3生成log形式 (58)7.2BTSlog (59)7.2.1软件获取及安装 (59)7.2.2BTSLOG 获取方法 (59)7.2.3生成log形式 (60)7.3Emil log (61)7.3.1软件获取及安装 (61)7.3.2Emil log 获取方法 (61)7.3.3生成log形式 (62)7.4RRU log (62)7.4.1软件获取及安装 (62)7.4.2RRU log 获取方法 (62)7.4.3生成log形式 (63)7.5TTI trace (63)7.5.1软件获取及安装 (63)7.5.2TTI trace 获取方法 (63)7.5.3生成log形式 (63)7.6MemoryDUMP (64)7.6.1软件获取及安装 (64)7.6.2MemoryDUMP 获取方法 (64)7.6.3生成log形式 (65)第八章维护初期常见问题 (66)8.1传输配置文件（config.xml）在哪里 (66)8.2如何恢复传输配置文件 (66)8.3如何在线升降RRU功率，eNB不重启 (66)8.4如何打开光口自适应 (67)8.5如何进行指令查询 (67)8.6如何打开vswr (67)8.7手动重启基站会出现什么样的告警 (68)8.8新开站需要修改那些参数 (68)8.9如何修改天线权值 (71)8.10什么是小区加扰 (71)8.11如何为小区加扰（业务信道和控制信道加扰） (72)8.12什么是TDD 帧格式 (72)8.13如何修改TDD帧格式 (72)8.14什么是TTD特殊子帧配置 (73)8.15如何更改TTD特殊子帧配置 (73)8.16如何查看BBU光模块的硬件信息 (74)8.17如何查看RRU光模块的硬件信息 (74)第一章后台维护常用工具介绍及安装步骤1.1后台维护常用工具概述LTE后台常用维护工具较多，熟悉各个工具的功能及使用场景对后台工作有重要意义，工欲善其事，必先利其器。

QSG156: LTE-M Expansion Kit Quick-Start GuideThe LTE-M Expansion Kit is an excellent way to explore and evaluate the Digi XBee3™ LTE-M cellular module which allows you to add low-power long range wireless connectivity to your EFM32/EFR32 embedded application.The Digi XBee3™ LTE-M cellular module is an easy to use cellular module. The LTE-M Expansion Kit easily integrates and brings LTE-M connectivity to compatible Silicon Labs Wireless and MCU Starter Kits through the expansion header.Software examples for the LTE-M Expansion Kit for the EFM32GG11 Giant Gecko STK (SLSTK3701A) are available in Simplicity Studio™. This guide demonstrates how to download and run one of these examples.LTE-M Expansion Kit Contents•Expansion board with Digi XBee3™wireless module socket •Digi XBee3™ LTE-M cellular module •Hologram SIM card •Cellular patch antenna •Quick Start card1. Getting StartedIntroductionThe Digi XBee3™ LTE-M cellular module is capable of sending and receiving SMS messages. This guide will walk through the steps necessary to run the Xbee SMS demo in Simplicity Studio, which demonstrates this capability.Note: An EFM32GG11 Giant Gecko STK (SLSTK3701A) is required for this demo. Please see the following guide for instructions on how to get started with the EFM32GG11 kit:QSG149: EFM32GG11-SLSTK3701A Quick-Start GuideInstall Simplicity StudioSimplicity Studio is a free software suite needed to start developing your application. Download the latest version of Simplicity Studio from the Silicon Labs website:/simplicity-studioActivate the included SIM cardThe included Hologram SIM card must be activated before it can be used with the Digi XBee3™ LTE-M cellular module. This can be done by following these instructions:1.In a browser, navigate to https://hologram.io/ and create a new account.2.Once your account has been activated, navigate to https://dashboard.hologram.io/activate and follow the instructions to completethe activation of your SIM card.Note: The activation process will ask you to configure the SIM's APN to "hologram" with username and password empty. This will be done by automatically by the demo on the EFM32GG11 STK.3.If desired, purchase a phone number for the SIM card on the dashboard in the card's Configuration page. Instructions for this stepcan be found here: https://help.hologram.io/getting-started-with-hologram/how-can-i-get-a-phone-number-to-send-sms-messages-to-my-simNote: Purchasing a phone number is not necessary, as you can still send and receive SMS messages through the Hologram dash-board without one.Assemble the Expansion Board1.Place the Digi XBee3™ LTE-M cellular module into the socket on the expansion board.2.Insert the Hologram SIM card into the SIM card slot on the module.3.Connect the included patch antenna to the module's u.FL connector labeled 'CELL'. The completed assembly is shown in the figurebelow.Download and Run the SMS DemoThe LTE-M Expansion Kit has several demos available for it that run on an EFM32GG11 Giant Gecko STK. To download and run the Xbee SMS demo:1.Once the expansion board is assembled, connect it to the expansion header of an EFM32GG11 STK, as shown below.2.Once the expansion board is connected, the EFM32GG11 STK can then be powered by connecting the USB connector on the leftand setting the switch to the AEM position.unch the demo in Simplicity Studio by finding the [SLSTK3701_lte_xbee_sms] demo under [Getting Started] in the Launcher, under [Demos].4.Follow the initialization sequence on the LCD.Note: The initialization sequence, including finding a cell signal, may take up to one minute. If this process takes longer than a minute, try to find a location with a stronger cell signal.Send and Receive SMS messagesIf you have purchased a phone number for your Hologram SIM card, you may now send SMS messages to this phone number.If you haven't purchased a phone number, you can send SMS messages through the Hologram dashboard instead.The SMS message will be received and displayed on the EFM32GG11 STK's LCD, along with the sender's phone number. The demo will automatically respond back with the message "You are linked to this Xbee" to this phone number. Pressing BTN0 on the EFM32GG11 STK will also send a message stating the number of messages the demo has received so far.Note: Sending and receiving SMS messages may take over a minute.Note: The Hologram SIM card will cause the SMS response from the module to be from a different phone number than the one as-signed to the SIM card. This response will be from a +88 number, and some carriers block these numbers automatically. If you receive no responses from the kit during this demo, you may contact your carrier and request that they allow messages from +88 numbers. Note: The SMS demo will configure the Digi XBee3™ LTE-M cellular module to search for and use the strongest carrier, between Veri-zon and AT&T. The module also has the option to be configured to use a specific carrier, if desired.Additional Resources 2. Additional ResourcesAdditional Software ExamplesTwo additional software examples for the EFM32GG11 Giant Gecko STK are available within Simplicity Studio. These can be accessed from the [Launcher] perspective under [Software Examples] with the kit selected.1.Digi XBee Device Cloud example: This example project uses a Digi XBee module to communicate via LTE-M. It transmits tempera-ture data to the Digi Device Cloud and allows a Cloud user to modify LED's on the board.2.Digi XBee Time Server example: This example project uses a Digi XBee module to receive the current time from an online timerserver and displays the time on the LCD.Additional DocumentationFor more information, please review the following:•UG310: LTE-M Expansion Kit User's Guide•https:///xbee•https://hologram.io/Silicon Laboratories Inc.400 West Cesar Chavez Austin, TX 78701USASimplicity StudioOne-click access to MCU and wireless tools, documentation, software, source code libraries & more. Available for Windows, Mac and Linux!IoT Portfolio /IoTSW/HW/simplicityQuality /qualitySupport and CommunityDisclaimerSilicon Labs intends to provide customers with the latest, accurate, and in-depth documentation of all peripherals and modules available for system and software implementers using or intending to use the Silicon Labs products. Characterization data, available modules and peripherals, memory sizes and memory addresses refer to each specific device, and "Typical" parameters provided can and do vary in different applications. Application examples described herein are for illustrative purposes only. Silicon Labs reserves the right to make changes without further notice and limitation to product information, specifications, and descriptions herein, and does not give warranties as to the accuracy or completeness of the included information. Silicon Labs shall have no liability for the consequences of use of the information supplied herein. This document does not imply or express copyright licenses granted hereunder to design or fabricate any integrated circuits. The products are not designed or authorized to be used within any Life Support System without the specific written consent of Silicon Labs. A "Life Support System" is any product or system intended to support or sustain life and/or health, which, if it fails, can be reasonably expected to result in significant personal injury or death. Silicon Labs products are not designed or authorized for military applications. Silicon Labs products shall under no circumstances be used in weapons of mass destruction including (but not limited to) nuclear, biological or chemical weapons, or missiles capable of delivering such weapons.Trademark InformationSilicon Laboratories Inc.® , Silicon Laboratories®, Silicon Labs®, SiLabs® and the Silicon Labs logo®, Bluegiga®, Bluegiga Logo®, Clockbuilder®, CMEMS®, DSPLL®, EFM®, EFM32®, EFR, Ember®, Energy Micro, Energy Micro logo and combinations thereof, "the world’s most energy friendly microcontrollers", Ember®, EZLink®, EZRadio®, EZRadioPRO®, Gecko®, ISOmodem®, Micrium, Precision32®, ProSLIC®, Simplicity Studio®, SiPHY®, Telegesis, the Telegesis Logo®, USBXpress®, Zentri , Z-Wave, and others are trademarks or registered trademarks of Silicon Labs. ARM, CORTEX, Cortex-M3 and THUMB are trademarks or registered trademarks of ARM Holdings. Keil is a registered trademark of ARM Limited. All other products or brand names mentioned herein are trademarks of their respective holders.。

huawei机房操作指导总结一．T D-LTE组网简介整个TD-LTE系统由3部分组成，核心网（EPC），接入网（eNodeB）,用户设备（UE）.EPC又分为三部分：MME 负责信令处理部分，S-GW 负责本地网络用户数据处理部分P-GW 负责用户数据包与其他网络的处理。

接入网也称E-UTRAN，由eNodeB构成。

eNodeB与EPC之间的接口称为S1接口，eNodeB之间的接口称为X2接口，eNodeB与UE之间的接口称为Uu接口。

二．L TE网管客户端安装1、LTE网管系统目前有两套，一套为M2000系统，另一套为新版OMC920系统，两套系统主要功能基本相同，但后者将TDS系统统一整合进来；2、LTE网管的安装:系统的安装：M2000网管系统的安装，首先在IE地址栏中，输入IP地址.80/cau/，然后下载安装，OMC920网管系统，则要输入IP地址.45/cau/，然后下载安装；3、OMC920系统网管安装成功后，需要将附件hosts文件复制到C:\WINDOWS\system32\drivers\etc目录下，替换系统自带的hosts文件，否则登录时会出现异常，M2000系统没有此类问题；后面操作因M2000与OMC920类似，故仅以OMC920网管系统为例说明；三．L TE网管客户端登录登陆网管OMC920客户端。

打开客户端后，显示的是“用户登陆”，需要填写，用户名，密码，当多个OMC920客户端登陆时，需点击服务器下拉菜单，增加网元信息。

成功登录后进入OMC920网管系统首页，内容包括各类维护操作的菜单栏、工具栏和一些快捷工具图示等；OMC维护系统包括MML命令、结果查询、监控和维护等主要功能，后面对这些具体功能进行详细介绍；四．L TE常用的操作4.1 eNod eB MML常用命令在网络规划和优化工作中，对单个eNodeB进行远端操作维护的情况较少，一般都可以在M2000下对eNodeB进行相关的操作。

LTE常用工具使用指南(仅供内部使用）拟制: LTE JJFA WH 日期：2010-4-14 审核: 日期：审核: 日期：批准: 日期：华为技术有限公司Huawei Technologies Co., Ltd.版权所有侵权必究All rights reserved修订记录目录1概述 (6)1.1背景 (6)1.2常用工具概述 (6)2常用工具 (6)2.1Porbe(Huawei) (6)2.1.1安装 (11)2.1.2.连接 (12)2.1.3启动跟踪 (13)2.2Iperf (19)2.2.1下行UDP灌包（从服务器向终端灌包） (20)2.2.2上行UDP灌包（从UE灌向服务器） (20)2.2.3下行TCP灌包 (20)2.2.4上行TCP灌包 (21)2.3三星终端安装调试 (21)2.3.1软件安装 (21)2.3.2拨号功能 (21)2.3.3Band7支持频点 (24)2.3.4注意事项 (25)2.4Ethereal (25)2.4.1概述 (25)2.4.2软件安装 (25)2.4.3启动抓包 (26)2.4.4软件基本使用 (27)2.4.5TCP数据分析 (30)2.4.6文件处理 (32)2.5CHR (34)2.6一键式日志 (35)2.7欧贝特烧卡指导 (37)2.7.1烧卡前需要的信息 (37)2.7.2欧贝特软件安装 (37)2.7.3使用 (37)LTE常用工具使用指南关键词：Iperf、LMT、Probe、OMT摘要：本文是LTE常用工具和软件的使用指南，用于指导公司其他项目在各种场合进行Showcase等演示项目时，使用LTE常用工具使用指南结合演示指南达到更快更好的演示效果。

缩略语清单：1 概述1.1 背景本文主要是结合《LTE业务演示指南》给出LTE常用工具的使用指导，用以指导公司其它项目组快速熟悉LTE工具并具备初步获取日志和分析问题的能力。

1.2 常用工具概述Probe是一款空口测试工具，主要用于搜集LTE网络空口测试数据。

LTE系统消息详细解析LTE系统消息广播分为主信息块MIB(Master Information Block)和系统消息块SIB(System Information Blocks)。

对于UE当新接入一个小区或者广播消息发生变化时，都会收到网络发出的系统消息(MIB/SIB)，以帮助更新或纠正UE当前的状态，完成相应的通信业务和物理过程。

System Information Broadcast:（系统消息广播）1. MIB: 用于系上统接入，MIB上传输几个比较重要的系统信息参数。

比如小区下行带宽，PHICH（Physical Hybrid ARQ Indicator Channel，物理混合自动重传指示信道）配置参数，无线系统帧号SFN（包含SIB1消息的位置），在PBCH上发送。

在展讯平台log抓取工具中，从Armlog中的All Messages可以看到如下信令：MSG_ID_BCCH_BCH_MSG_TYPE如上图:1)phycellid=248 // 当前小区的物理小区号2)Dl-Bandwidth=n100 //小区下行带宽系统带宽，范围enumerate(1.4M(6RB，0)，3M(15RB,1)，5M(25RB,2)，10M(50RB,3)，15M(75RB,4)，20M(100RB,5))，上图为n100，对应的系统带宽为20M（100RB，带宽索引号为5, 在Wireshake解析可以看出）。

3)phich-Config // PHICH的配置参数phich-Duration当该参数设置为normal时，PDCCH占用的OFDM符号数可以自适应调整；当该参数设置为extended时，若带宽为1.4M，则PDCCH占用的OFDM符号数可以取3或4，对于其他系统带宽下，PDCCH 占用的符号数只能为3;phich-Resource该参数用于计算小区PHICH信道的资源;4)SystemFrameNumber //无线系统帧号SFNSystemFrameNumber系统帧号。

华为参数查询和配置手册（命令行方式）目录TABLE OF CONTENTS1 缩略语 ..................................................................... 错误!未定义书签。

2上行资源分配 (4)3上行ICIC (21)4下行资源分配 (27)5下行ICIC (40)6下行MIMO (46)7移动性管理 (50)8LC（过载控制） (164)9功控算法 (197)10信道配置&链路控制 (229)11数传算法 (271)12传输TRM算法 (273)13 SON (278)1 缩略语2 上行资源分配2.1SRS资源分配2.1.1PSrsOffsetDeltaMcsDisable（Delta-MCS disable时Sounding RS相对于PUSCH的功率偏置）(1)参数简要说明含义：该参数用来表示DELTAMCSENABLED= UU_DISABLE时，Sounding RS相对于PUSCH的功率偏置，表示协议中描述的SRS功率的偏置值。

为了保证SRS和PUSCH 在每个子载波的功率谱密度一致，由于SRS的带宽只占用1个Comb，因此将PSRS_OFFSET设置为-3dB以抵消其带来的影响。

类型：区间数值类型取值范围：：-105,-90,-75,-60,-45,-30,-15,0,15,30,45,60,75,90,105,120；单位：0.1dB缺省值：-30约束关系：无影响范围：小区级(2)参数查看修改方法查看方法：LST CELLULPCDEDIC修改方法：MOD CELLULPCDEDIC: LocalCellId=x, PSrsOffsetDeltaMcsDisable=x;2.1.2PSrsOffsetDeltaMcsEnable（Delta-MCS enable时Sounding RS相对于PUSCH的功率偏置）(1)参数简要说明含义：该参数用来表示DELTAMCSENABLED= UU_ ENABLE时，Sounding RS相对于PUSCH的功率偏置，表示协议中描述的SRS功率的偏置值。

DIGI INTERNATIONAL9350 Excelsior Blvd, Suite 700Hopkins, MN 55343, USA+1 (952) 912-3444 | +1 (877) 912-3444Firmware Release NotesConnectPort LTSVersion 1.4.6 (November, 2020) INTRODUCTIONThis is a production release of firmware for the ConnectPort LTS(Linux Terminal Server) products. These devices provide serial over Ethernet connectivity for applications today and into the future. They support IPv4 and IPv6 Ethernet protocols. The ConnectPort LTS MEI product is the same sizeas the ConnectPort LTS (RS-232 only) and is the fastest multi-port device with a Multiple Electrical Interface (MEI) in the industry. High-end features include Telnet/SSHv2/TCP Sockets protocols, Local, RADIUS and LDAP authentication, Port logging through Local, NFS, Samba, Syslog and SD Memory cards, keyword monitoring and SMTP/SNMPv3 notification, PPP, Encrypted RealPort, Dual10/100/1000 mbps Ethernet network interface, Python support and Digi Discovery server to allow discovery and network configuration from the Digi Discovery Tool.SUPPORTED PRODUCTS∙ConnectPort LTS 8 Family∙ConnectPort LTS 16 Family∙ConnectPort LTS 32 FamilyKNOWN ISSUESNoneADDITIONAL INFORMATIONNoneUPDATE CONSIDERATIONSIn order to add compliance with California's Senate Bill No. 327, for information privacy of connected devices, the handling of the root password for newly manufactured products is changing.Products manufactured after January 1, 2020 will no longer use a fixed, default root password. Rather, a per-device, unique password will be assigned during manufacturing, and will be visible ona product label. It will still be possible to change the password for the root user on a per-device basis.Admin user: The admin user is inactive in the new firmware. To activate the admin user, you must first assign a password to the admin user.Products manufactured prior to the adoption of the new product labeling are grandfathered in and will continue to operate as before.UPDATE BEST PRACTICESDigi recommends the following best practices:1.Test the new release in a controlled environment with your application before you updateproduction devices.2.Unless otherwise noted, apply updates in the following order:a.Device firmwareb.Modem firmwarec.Configurationd.ApplicationDigi recommends Digi Remote Manager for automated device updates. For more information, go to https:///products/iot-platform/digi-remote-manager. If you prefer manually updating one device at a time, follow these steps from the manual:1.Firmware update processTECHNICAL SUPPORTGet the help you need via our Technical Support team and online resources. Digi offers multiple support levels and professional services to meet your needs. All Digi customers have access to product documentation, firmware, drivers, and knowledge base and peer-to-peer support forums. Visit us at https:///support to find out more.CHANGE LOGVERSION 1.4.6 November, 2020This is a recommended release for any customer who needs the enhanced RTS functionality.MD5 Checksum33CB52FE9DACA5F25F7081294A8B16AFSHA-25672EBFFC04D80352A009D49A76D395F3BD62AFFA30D196DBB6CAC3E8C9E91211CNEW FEATURESNoneENHANCEMENTSNoneSECURITY FIXESNoneBUG FIXES∙Fixed a problem with RTS and DTR behavior CPLTS-178∙Fixed a problem with RTS Toggle CPLTS-182VERSION 1.4.5.1 June 05, 2020This is a mandatory release.NEW FEATURESNoneENHANCEMENTSNoneSECURITY FIXESCVE-2020-8597https:///vuln/detail/CVE-2020-8597pppd (Point to Point Protocol Daemon) versions 2.4.2 through 2.4.8 are vulnerable to buffer overflow due to a flaw in Extensible Authentication Protocol (EAP) packet processing ineap_request and eap_response subroutines.Due to a flaw in the Extensible Authentication Protocol (EAP) packet processing in the Point-to-Point Protocol Daemon (pppd), an unauthenticated remote attacker may be able to cause a stack buffer overflow, which may allow arbitrary code execution on the target system. This vulnerability is due to an error in validating the size of the input before copying the supplied data into memory. As the validation of the data size is incorrect, arbitrary data can be copied into memory and cause memory corruption possibly leading to execution of unwanted code.BUG FIXESNoneVERSION 1.4.5 November 08, 2019This is a mandatory release.NEW FEATURES1.Added support for California's Senate Bill No. 327. Product manufactured after January 1,2020 will have a unique password.ENHANCEMENTSNoneSECURITY FIXESResearchers have discovered new denial-of-service (DoS) vulnerabilities in Linux and FreeBSD kernels, including a severe vulnerability called SACK Panic that could allow malicious actors to remotely crash servers and disrupt communications, according to an advisory.“The vulnerabilities specifically relate to the Maximum Segment Size (MSS) and TCP Selective Acknowledgement (SACK) capabilities. The most serious, dubbed “SACK Panic,” allows aremotely-triggered kernel panic on recent Linux kernels,” the advis ory stated. Thisvulnerability also goes back a long time (since Linux v2.6.29, that was released 10 years ago).“The issues have been assigned multiple CVEs: CVE-2019-11477 is considered an Important severity, whereas CVE-2019-11478 and CVE-2019-11479 are considered a Moderate severity”.Researchers have discovered Medium Level security fixes - Three (3) Stored XSS Scripting and one (1) unrestricted/arbitrary file upload vulnerability. We would like to provide thanks and credit to the finding of the vulnerabilities to two (2) researchers:Murat Aydemir, Critical Infrastructe Penetration Test Specialist at Biznet Bilisim A.SFatih Kayran, Penetration Test SpecialistBUG FIXESNoneVERSION 1.4.4 May, 2019∙Add support for 50 Baud.∙Force HTTPS to use only TLS 1.2.∙Allow SSH client to change default password.∙Fix configuration parser to allow for non-standard characters.∙Fix to properly exit a telnet session after killing a port.∙Allow for capital letter in serial port description.VERSION 1.4.3 Aug, 2018∙Added support to Allow access to connect as a different user (i.e. root) when logged as a normal user.∙Added a send break option.∙Added ability to disable keyboard-interactive authentication if a user has SSH publick key authentication enabled.∙Added the DHCP custom identifier option to this product.∙Updated RealPort to allow use of TLS 1.2.∙Changed network stack behavior when LTS declines/closes an additional TCP socket open request.∙Fixed typos in CLI.∙Blocked the use of Special Swedish Characters In The Serial Port Description.∙Fixed a problem where Serial port process does not start properly during boot when data is sent during boot to the port.∙Fixed a problem where we couldn't mount a Samba share from an Ubuntu 18.04 Linux server.。

]IoT AppZone Release NotesRelease Version 4.1.480496DSW10114A r8 – 2019-09-121 6SPECIFICATIONS ARE SUBJECT TO CHANGE WITHOUT NOTICENOTICEWhile reasonable efforts have been made to assure the accuracy of this document, Telit assumes no liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained herein. The information in this document has been carefully checked and is believed to be reliable. However, no responsibility is assumed for inaccuracies or omissions. Telit reserves the right to make changes to any products described herein and reserves the right to revise this document and to make changes from time to time in content hereof with no obligation to notify any person of revisions or changes. Telit does not assume any liability arising out of the application or use of any product, software, or circuit described herein; neither does it convey license under its patent rights or the rights of others.It is possible that this publication may contain references to, or information about Telit products (machines and programs), programming, or services that are not announced in your country. Such references or information must not be construed to mean that Telit intends to announce such Telit products, programming, or services in your country. COPYRIGHTSThis instruction manual and the Telit products described in this instruction manual may be, include or describe copyrighted Telit material, such as computer programs stored in semiconductor memories or other media. Laws in the Italy and other countries preserve for Telit and its licensors certain exclusive rights for copyrighted material, including the exclusive right to copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly, any copyrighted material of Telit and its licensors contained herein or in the Telit products described in this instruction manual may not be copied, reproduced, distributed, merged or modified in any manner without the express written permission of Telit. Furthermore, the purchase of Telit products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any license under the copyrights, patents or patent applications of Telit, as arises by operation of law in the sale of a product.COMPUTER SOFTWARE COPYRIGHTSThe Telit and 3rd Party supplied Software (SW) products described in this instruction manual may include copyrighted Telit and other 3rd Party supplied computer programs stored in semiconductor memories or other media. Laws in the Italy and other countries preserve for Telit and other 3rd Party supplied SW certain exclusive rights for copyrighted computer programs, including the exclusive right to copy or reproduce in any form the copyrighted computer program. Accordingly, any copyrighted Telit or other 3rd Party supplied SW computer programs contained in the Telit products described in this instruction manual may not be copied (reverse engineered) or reproduced in any manner without the express written permission of Telit or the 3rd Party SW supplier. Furthermore, the purchase of Telit products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any license under the copyrights, patents or patent applications of Telit or other 3rd Party supplied SW, except for the normal non-exclusive, royalty free license to use that arises by operation of law in the sale of a product.USAGE AND DISCLOSURE RESTRICTIONSI. License AgreementsThe software described in this document is the property of Telit and its licensors. It is furnished by express license agreement only and may be used only in accordance with the terms of such an agreement.II. Copyrighted MaterialsSoftware and documentation are copyrighted materials. Making unauthorized copies is prohibited by law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, without prior written permission of Telit III. High Risk MaterialsComponents, units, or third-party products used in the product described herein are NOT fault-tolerant and are NOT designed, manufactured, or intended for use as on-line control equipment in the following hazardous environments requiring fail-safe controls: the operation of Nuclear Facilities, Aircraft Navigation or Aircraft Communication Systems, Air Traffic Control, Life Support, or Weapons Systems (High Risk Activities"). Telit and its supplier(s) specifically disclaim any expressed or implied warranty of fitness for such High Risk Activities.IV. TrademarksTELIT and the Stylized T Logo are registered in Trademark Office. All other product or service names are the property of their respective owners.V. Third Party RightsThe software may include Third Party Right software. In this case you agree to comply with all terms and conditions imposed on you in respect of such separate software. In addition to Third Party Terms, the disclaimer of warranty and limitation of liability provisions in this License shall apply to the Third Party Right software.TELIT HEREBY DISCLAIMS ANY AND ALL WARRANTIES EXPRESS OR IMPLIED FROM ANY THIRD PARTIES REGARDING ANY SEPARATE FILES, ANY THIRD PARTY MATERIALS INCLUDED IN THE SOFTWARE, ANY THIRD PARTY MATERIALS FROM WHICH THE SOFTWARE IS DERIVED (COLLECTIVELY “OTHER CODE”), AND THE USE OF ANY OR ALL THE OTHER CODE IN CONNECTION WITH THE SOFTWARE, INCLUDING (WITHOUT LIMITATION) ANY WARRANTIES OF SATISFACTORY QUALITY OR FITNESS FOR A PARTICULAR PURPOSE.NO THIRD PARTY LICENSORS OF OTHER CODE SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND WHETHER MADE UNDER CONTRACT, TORT OR OTHER LEGAL THEORY, ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE OTHER CODE OR THE EXERCISE OF ANY RIGHTS GRANTED UNDER EITHER OR BOTH THIS LICENSE AND THE LEGAL TERMS APPLICABLE TO ANY SEPARATE FILES, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.APPLICABILITY TABLE PRODUCTSGE910-QUADGE910-QUAD AUTOUL865 SERIESUL865-N3GUE910 SERIESUE866 SERIESHE910 SERIESCE910-DUALDE910-DUALDE910-SCME910 SERIESLE866 SERIESLE910 SERIESLE920 AUTO SERIESLE910 V2 SERIESLE910 CAT.1 SERIESCONTENTSNOTICE 2COPYRIGHTS (2)COMPUTER SOFTWARE COPYRIGHTS (2)USAGE AND DISCLOSURE RESTRICTIONS (3)I.License Agreements (3)II.Copyrighted Materials (3)III.High Risk Materials (3)IV.Trademarks (3)V.Third Party Rights (3)APPLICABILITY TABLE (4)CONTENTS (5)1.INTRODUCTION (7)2.RELEASE 4.1.4 (9)New Features available and general enhancements (9)Known limitations (9)3.RELEASE 4.1.0 (10)New Features available and general enhancements (10)Known limitations (11)4.RELEASE 4.0.0 (12)New Features available and general enhancements (12)Known limitations (13)5.RELEASE 3.0.3 (15)New Features available and general enhancements (15)6.RELEASE 3.0.2 (17)New Features available and general enhancements (17)7.RELEASE 3.0.1 (18)New Features available and general enhancements (18)8.RELEASE 3.0.0 (19)New Features available and general enhancements (19)9.RELEASE 2.1.4 (20)New Features available and general enhancements (20)10.DOCUMENT HISTORY (21)1. INTRODUCTION1.1. ScopeScope of this document is to detail the corrections, changes or enhancements made to IoT AppZone SDK.1.2. AudienceThis document is intended for Telit customers.1.3. Contact Information, SupportFor general contact, technical support services, technical questions and report documentation errors contact Telit Technical Support at:•*****************•*********************•*****************Alternatively, use:/supportFor detailed information about where you can buy the Telit modules or for recommendations on accessories and components visit:Our aim is to make this guide as helpful as possible. Keep us informed of your comments and suggestions for improvements.Telit appreciates feedback from the users of our information.1.4. Related DocumentsThe following is a list of applicable documents downloadable from the Download Zone or available in the IoT AppZone developer page:•AppZone C User Guide•AppZone C API Reference Guide•AppZone C Sample Apps Guide•AppZone Python User Guide•AppZone Python API Reference Guide•AppZone LUA User Guide•AppZone LUA API Reference Guide•AppZone LUA AT commands Guide•AppZone Linux User Guide•AppZone Linux API Reference Guide1.5. System RequirementsTo install IoT AppZone package, administrator permissions are needed. The installation requires:• 1 GB of RAM• 1.2 GB of free disk space•Java™ SE Runtime Environment 32-bit at least version 1.8 rel 101(*)•Windows 7 (32bit or 64bit), Windows 8, Windows 10(*) Note: Java™ SE Runtime Environment 64-bit is not compatible with AppZone IDE.2. RELEASE 4.1.4New Features available and general enhancementsType DescriptionIDE AZ C Updated AppZone2.0 sample apps for ME910C1IDE AZ C Updated AppZone sample apps for LE910v2, HE910IDE AZ C ME910C1: added new firmware 30.00.xx5IDE AZ C LE910v2: added new firmware 20.00.xx6IDE AZ EMU Enhancements on building for Emulator (AppZone C m2m)IDE AZ EMU Enhancement on USB cable check for printing on emulator console IDE AZ C MCU Jlink debugger support for WiFi module has been addedIDE AZ Linux Windows support for AppZone IDE (Beta)IDE AZ Linux New toolchain included to support LE910C1/C4 new software baseline IDE AZ Linux Password security removed from LE910C1Known limitations•AppZone emulator for ME910C1 is in Beta. Compilation support is full, while emulation and debugging features are under development.•New Toolchain for AZ Linux software baseline is Beta on Windows.3. RELEASE4.1.0New Features available and general enhancementsType DescriptionIDE AZ C Updated documentation and code samplesIDE AZ C AZ Console configuration fix for parityIDE AZ C AZ Perspective reset fixedIDE AZ C Allowing AZ C projects to be fully rebuilt every timeIDE AZ C Adding ME910/ML865 to the list of supported devicesIDE AZ C Added new AppZone M2MB APIs supportIDE AZ C Added new AppZone M2MB APIs code samples for ME910C1IDE AZ C Enabling ME910 static librariesIDE AZ C Adding include paths for LE866 projectsIDE AZ C Enabling static library creation to relevant productsIDE AZ C Fix .bin file upload after non-binary file uploadIDE AZ C Updated SSL demo for LE910v2 20.00.XX4 and newer versionsIDE AZ EMU Improved emulator plugins for LinuxIDE AZ EMU Adding example makefiles for samplesIDE AZ EMU Emulator automatically picks up the product for which the AZ app is built IDE AZ EMU Added extension plug-in for emulator for AT commandsIDE AZ EMU Added extension plug-in for emulator for SPIIDE AZ EMU Added support for M2MB API and ME910 projects (compilation only) IDE AZ EMU Updated documentation and samples for developersIDE AZ EMU Implemented m2m_socket_api for LinuxIDE AZ Install Enhanced installation of WHQL drivers for Windows 10IDE AZ Installer Upgraded to TATC 3.4.1 and XFP 4.0.5IDE AZ Linux Introduced new LE910C1 boot-up script method for automatic start of applicationIDE AZ Lua Added RE866 to list of LUA supported productIDE AZ Lua Added Lua to dev exportKnown limitations•AppZone emulator for ME910C1 is in Beta. Compilation is allowed but only a limited set of APIs are supported.4. RELEASE 4.0.0New Features available and general enhancementsType DescriptionIDE Installer Fixes and improvements in the installerIDE Installer The correct JRE gets installed automatically when missing in the IDE IDE AZ LUA Introducing AZ Lua which supports the BlueMod+S42 BLE module IDE AZ C Introducing integrated Emulator to run and debug applications on PC IDE AZ C Static 3rd party librariesIDE AZ C Various enhancements and bug fixes on AZ ConsoleIDE AZ C UI Button for building the AppZone applications with improved project build logicIDE AZ C Run button for Release will deploy the application to the modem and run it (using different port from AZ Console)IDE AZ C Windows file is unlocked after being uploaded to modemIDE AZ C Removed Update Telit Project, the update happens automatically without user interventionIDE AZ C More informative error dialogs when Run failsIDE AZ C UI improvementsIDE AZ C Emulator UART channel handlingIDE AZ C Emulator handing SGACT, HTTP* AT commandsIDE AZ C Windows implementation of the socket API in EmulatorIDE AZ C Handling of SIM insertion and network registration in the Emulator IDE AZ C Emulator SMS injection supportIDE AZ C Added help for sample applicationsIDE AZ C Added BLE + Cellular sampleIDE AZ C Added samples for Multitasking, OTA and SSLIDE AZ C More information available on splash screenIDE AZ C Enabled the AppZone C console in LinuxIDE AZ C Added mechanism for locking and unlocking the filesystem IDE AZ C Added support for UE866IDE AZ C Added support for UL865IDE AZ C Added support for LE866IDE AZ C Enhanced behavior when product/toolchain/FW are changed on a projectIDE AZ C Added labels of COM ports in the AZ Console SettingsIDE AZ C The AppZone Console uploads non-binary files to current dir IDE AZ C AppZone Console allows filenames up to 63 characters long IDE AZ C Updating visuals. Added information view in the main perspective IDE AZ C Enhanced build processIDE AZ C Upgraded the Lauterbach supportIDE AZ C Removed the need to Update Telit Projects when upgrading to newer version of the SDKKnown limitations•On new AppZone IDE version 4.0.0, Eclipse has been updated to Neon build and selective update of packages is not possible. The installer wizard will reinstall the environment from scratch. Existing workspace will be preserved.•With older versions of JRE the AZ Console might exhibit some issues when downloading application to the module. Please make sure that at least JRE 1.8 rel 101 is installed.5. RELEASE 3.0.3New Features available and general enhancementsType DescriptionIDE Installer Fixed the issue with the uninstaller not registering correctly the final size of the installationIDE Installer Cleaned linux installer unnecessary dependenciesIDE Installer Providing offline installerIDE Installer Prevent Python from being uninstalledIDE Installer Installing documentation of the IDEIDE AZ Py Py AT Console: enhanced launch button functionality IDE AZ Py Py AT_Console: added time logging icon in toolbarIDE AZ C Making "Update Existing Project Wizard" more visible IDE AZ C AZ_C plugin removed pydev dependencyIDE AZ C Updated FW update logic to report errorsIDE AZ C Updated flashing FW procedure to use correct naming IDE AZ C Enhanced behavior of AZ Console when flashing new FW IDE AZ C Getting user to confirm if a file will be overwrittenIDE AZ C Allowing multiple AZ build configurationsIDE AZ C AZ Console: enhanced sending of files with long nameIDE AZ C Updating 3G and 4G AZ library to allow compilation on Linux 32 bit for these modelsIDE AZ C Updated LE910v2 FW version in the help textIDE AZ C Prepending minGW location to PATH variable IDE AZ C Renewed the sample applicationsIDE AZ C Added Remote TCPAT UART sample application IDE AZ C Updated to TATC 3.4.2 and XFP 3.3.1IDE AZ C Documentation updated with new API guide6.RELEASE 3.0.2New Features available and general enhancements Type DescriptionIDE AZ C Improvement in Lauterbach support for GE910IDE AZ C Released new package 121633R4 for HE910_12.00.XX8 containing support of mode 0 (zero) in m2m_hw_sleep_modeIDE AZ C Released new package 201641R2 for LE910V2_20.00.XX2 containing:- Improvement in m2m_ssl_new_connection behavior- improvement using the M2M_SOCKET_BSD_TCP_KEEPALIVEoption - improvement in the mapping of GPIOs with interrupts - improvement in m2m_fs_gets with EOF charIDE AZ C Released new package 121540N3 for HE910_12.00.XX7 and new package 131635N3 for GE910_13.00.XX9 containing:- makefiles alignment to allow debug for 3G PIC type - debug independency from *.bin name, PIC type - infobuild and infobuild_linux aligned with last version as for 4G IDE AZ C New installer contains the latest version of XFP and TATCIDE AZ C Improvement in the selection of packages and toolchain in New Project wizardIDE AZ C Cleaner IDE build (warning removal)IDE AZ C Make file stops immediately the process in case of errorIDE AZ C Added toolchain support for compiling AppZone C apps from Linux IDE AZ C Enhanced project creation on Windows with Java 7IDE Installer Added brief summary for each AppZone environmentIDE Installer Grouped components in the custom installation page to make it easier for the users to choose features7. RELEASE 3.0.1New Features available and general enhancementsType DescriptionIDE AZ C Improvement of the auto-connect function of AZ C Console IDE AZ C Improvement in Lauterbach supportIDE AZ C Improvement in the project creation using the IDE with Windows 32 bits. Released the corresponding packages: 131635N2 for GE910, 121633R3 for HE910_12.00.XX8, 201636R2 for LE910V2_20.00.XX2IDE AZ C Added package 121540N1 for HE910_12.00.XX7IDE AZ C New installer contains the latest version of XFP and TATCIDE AZ C Improvement in the selection of packages and toolchain in New Project wizard8. RELEASE 3.0.0New Features available and general enhancementsType DescriptionIDE general Added support of AppZone AndroidIDE general Added Package and Libraries Management featureIDE general Added firmware update/compatibility functionality to IDE IDE general New link in the welcome page to Create a New ProjectIDE AZ C Add the possibility to upload into the module, thru the AZ C Console, non binary filesIDE AZ C JTAG supportIDE AZ C Project migration wizardIDE AZ CIDE AZ PythonStart App button for AZ C and AZ PY9. RELEASE 2.1.4New Features available and general enhancementsType DescriptionIDE General On-line installer: packages are downloaded during installation based on customer’s selectionsIDE General Unified installer and IDE for AppZone C, AppZone Python, AppZone LinuxIDE General On-line update of the IDE through «Check updates» function IDE General Updated on-line help and API reference guidesIDE General New project WizardIDE AZPythonNew AZ PY consoleIDE AZ C Introduced Support of LE910 V2 SeriesIoT App Zone IDE Release Note - 4.1.410. DOCUMENT HISTORYRevision Date Changes0 2016-06-15 First issue 2.1.41 2016-09-29 3.0.02 2016-10-06 3.0.13 2016-11-18 3.0.24 2017-04-10 3.0.35 2017-11-21 4.0.06 2019-02-20 4.1.07 2019-09-06 4.1.48 2019-09-12 4.1.4 and fix on the document80496DSW10114A r8 Page 21 of 22 2019-09-12[04.2016] Mod. 0809 2016-08 Rev.7。

一、LTE OSS的使用1.1 退出OSS退出登陆后要选择,Launch-Out-xxxx,直接退出的话该进程并未关闭，仍然会占用OSS系统内存。

1.2查看告警双击显示告警详细信息：1.3查看全网整体告警1.4 查看LTE基站基本配置1.5选择LTE网络在ONRM_ROOT_MO_R下面查看的地区网元1.6查看基站状态及相关部分信息在右侧的STATUS菜单下可以分别查看基站状态及相关部分的信息，如基站IP地址、ID,及告警级别和数量等信息。

可以查看小区（EUTRAN cell）当前状态如是否运行（operational）、激活（Enabled）及解锁(Unlocked)等以及部分参数如TAC,PLMN等。

在查看状态时可以在左侧的Filter界面下选择过滤条件，如只显示locked(锁)和disabled （未激活）小区,则在status中会只列出相关状态的小区。

取消Filter时可点击Reset Filter 按钮。

1.7闭锁小区小区闭锁基站闭锁二、查询指令操作lt：指令是最常用的指令，进入moshell之后，首先用lt从库中取mo,要不然你就看不到东西。

通过在lt后面配置不同的过滤器可以有选择的装载mo,例如lt all是全部mo, lt m3ua只取包含（模糊查找）M3ua的mo。

当MO发生变化，例如删除，添加，修改参数。

需要lt root更新一下，再用lt all等取mo。

Pr：print mgw中定义了的mo，例如pr" pluginunit可以显示MGW中有定义的单板。

Get：想知道该MO的具体参数设置，用get" <proxy>获得，其中proxy由pr结果获得。

St：查看mo的工作（op）状态和管理（adm）状态bl"&deb ：对MO进行lock和unlock的操作。

这两个指令只能对MO的管理状态进行修改。

割接前闭塞不用的传输，以免出告警时有效。

写出LTE的下行物理信道:\ 写出LTE上行物理信道PBCH：物理广播信道 PRACH：物理随机接入信道PHICH：物理HARQ指示信道 PUSCH：物理上行共享信道PCFICH：物理控制格式指示信道 PUCCH：物理上行控制信道PDCCH：物理下行控制信道PDSCH：物理下行共享信道PMCH：物理多播信道PCI规划应遵循什么原则PCI即物理小区标识。

LTE系统提供504个物理层小区ID(即PCI)，和TD-SCDMA系统的128个扰码概念类似。

网管配置时，为小区配置0～503之间的一个号码即可。

在TD-LTE系统中，UE需要解出两个序列：主同步序列（PSS，共有3种可能性）和辅同步序列（SSS，共有168种可能性）。

由两个序列的序号组合，即可获取该小区ID。

物理小区标识规划应遵循以下原则：不冲突原则：保证同频相邻小区之间的PCI不同；因为PCI直接决定了小区同步序列，而且多个物理信道的扰码也和PCI相关，所以相邻小区的PCI不能相同，以避免干扰。

即所谓的：避免PCI冲突。

不混淆原则：保证某个小区的同频邻小区PCI值不相等；切换时，UE将报告邻小区的PCI和测量量。

如果服务小区有两个邻区都使用同样的PCI，则服务小区无法分辨UE到底应该切往哪个邻小区。

所以，任意小区的所有邻区都应有不同的PCI。

即所谓的：避免PCI混淆相邻小区之间应尽量选择干扰最优的PCI值，即PCI值模3不相等；主同步序列的值（共3种可能性）决定了参考信号（RS）在PRB内的位置。

所以相邻小区（尤其是对打的小区）应尽量避免配置同样的主同步序列值，以错开RS之间的干扰。

即所谓的：“PCI模3不等”原则。

在时域位置固定的情况下，相邻小区PCI模6相同会造成下一个TX antenna下下行RS相互干扰；PCI 模30值相同，会造成上行DM RS和SRS的相互干扰，因此相邻小区也应尽量避免模6、模30相同。

最优化原则：保证同PCI的小区具有足够的复用距离，并在同频邻小区之间选择干扰最优的PCI值。

修改eNodeB级算法开关(MOD ENODEBALGOSWITCH) 参数说明参数说明使用实例修改eNodeB级算法开关：切换算法开关为IntraFreqCoverHoSwitch-1，下行ICIC算法开关为DlIcicDynamicSwitch_ON_ENUM，ANR算法开关为IntraRatEventAnrSwitch-1:MOD ENODEBALGOSWITCH: HoAlgoSwitch=IntraFreqCoverHoSwitch-1, DlIcicSwitch=DlIcicDynamicSwitch_ON_ENUM, AnrSwitch=IntraRatEventAnrSwitch-1;修改非连续接收(MOD DRX)使用实例修改DRX参数信息，DRX特性开关为开，DRX特性短周期开关为开，与RFSP功能对应的DRX长周期配置为40子帧，与RFSP 功能对应的DRX短周期配置为10子帧，与RFSP功能对应的DRX短周期生命周期配置为2，系统内ANR专用的DRX长周期配置为320子帧：MOD DRX: DrxAlgSwitch=ON, ShortDrxSwitch=ON, LongDrxCycleSpecial=SF40, SupportShortDrxSpecial=UU_ENABLE, ShortDrxCycleSpecial=SF10, DrxShortCycleTimerSpecial=2, LongDrxCycleForAnr=SF320;修改DRX参数组(MOD DRXPARAGROUP)使用实例修改DRX参数组，本地小区标识为0，DRX参数组ID为9，对应参数组ID的承载是否支持DRX特性为关：MOD DRXPARAGROUP: LocalCellId=0, DrxParaGroupId=9, EnterDrxSwitch=OFF;。

UG310: LTE-M Expansion Kit User's GuideThe LTE-M Expansion Kit is an excellent way to explore and evaluate the Digi XBee3™ LTE-M cellular module which allows you to add low-power long range wireless connectivity to your EFM32/EFR32 embedded application.The Digi XBee3 LTE-M cellular module is an easy-to-use cellular module. The LTE-M Expansion Kit easily integrates and brings LTE-M connectivity to compatible Silicon Labs Wireless and MCU Starter Kits through the expansion header.To get started with the LTE-M Expansion Kit go to /start-efm32-xbee .LTE-M EXP BOARD FEATURES•EXP connector for interfacing Silicon Labs MCU and Wireless Starter Kits •2x10-pin socket supporting Digi XBee™and Digi XBee Pro™ through-hole modules•Digi XBee module can be powered by (W)STK supply rail or on-board DC-DC regulator•U-blox CAM-M8Q GNSS receiver supporting GPS and GLONASSSOFTWARE SUPPORT•Software examples for the EFM32GG11Starter Kit are available in Simplicity Studio™No tR e co mme nd edf or N e wDe si g n sTable of Contents1. Introduction................................32. Hardware Overview .. (4)2.1 Hardware Layout . (4)3. Connectors (5)3.1 EXP Header...............................53.1.1 Pass-through EXP Header ........................63.1.2 EXP Header Pinout ...........................63.2 Digi XBee Module Socket ..........................73.2.1 Digi XBee Module Socket Pinout ......................83.2.2 Power Supply ....... (9)4. Using the LTE-M Expansion Kit (10)4.1 Board Identification............................104.2 Digi XBee3 LTE-M Module ..........................104.3 On-Board GNSS Receiver .................. (11)5. Schematics, Assembly Drawings, and BOM (13)6. Kit Revision History (14)6.1 SLEXP8021A Revision History ..................... (14)7. Document Revision History (15)No tR e co mme nd edf or N e wDe si g n s1. IntroductionThis user guide covers the usage of the Silicon Labs LTE-M EXP Board together with the Digi XBee3 LTE-M cellular module. The LTE-M EXP Board is designed to be compatible with all Digi XBee through-hole modules offering a wide array of wireless connectivity op-tions, such as Zigbee, Wi-Fi, 3G and LTE cellular to name a few.Software examples demonstrating how to use the LTE-M Expansion Kit with the EFM32GG11 Starter Kit are available through Simplici-ty Studio™.For more information about the Digi XBee modules see https:///xbee .IntroductionNo tR e co mme nd edf or N e wDe si g n s2. Hardware Overview2.1 Hardware LayoutThe layout of the LTE-M Expansion Kit is shown in the figure below.EXP-header for Starter KitsPower source select switchPass-through EXP-headerNot mountedDigi XBee Module ResetDigi XBee Module SocketDigi XBee Module Breakout HeaderNot mountedDigi XBee Module Breakout HeaderFigure 2.1. LTE-M Expansion Kit Hardware LayoutHardware OverviewNo tR e co mme nd edf or N e wDe si n s3. ConnectorsThis chapter gives an overview of the LTE-M Expansion Kit connectivity and power connections.EXP HeaderEXP Header (Not Mounted)(Not Mounted)(Not Mounted)Figure 3.1. LTE-M Expansion Kit Connector Layout3.1 EXP HeaderOn the left side of the LTE-M Expansion Kit, a right-angle female 20-pin EXP header is provided to allow connection to one of Silicon Labs’ MCU or Wireless Starter Kits. The EXP header on the Starter Kits follows a standard which ensures that commonly used periph-erals such as an SPI, a UART, and an I2C bus, are available on fixed locations on the connector. Additionally, the VMCU, 3V3 and 5V power rails are also available on the EXP header. For detailed information regarding the pinout to the EXP header on a specific Starter Kit, consult the accompanying kit user’s guide.The figure below shows how the Digi XBee module socket and the on-board GNSS receiver are connected to the EXP header and the peripheral functions that are available.VMCUXBEE_DINXBEE_DOUT XBEE_DIO4XBEE_RTS GNSS_RXD GNSS_TXD XBEE_PWM15V3V3GNDGNSS_TIMEPULSE XBEE_DTRGNSS_POWER_EN GNSS_VBCKP_EN XBEE_CTSXBEE_RSSI XBEE_ADC1BOARD_ID_SDA BOARD_ID_SCL Reserved (Board Identification)LTE-M EXP Board I/O PinFigure 3.2. EXP HeaderNo tR e co mme nd edf or De si g n s3.1.1 Pass-through EXP HeaderThe LTE-M Expansion Kit features a footprint for a secondary EXP header. All signals from the EXP header, including those that are not connected to any features on the LTE-M Expansion Kit are directly tied to the corresponding pins in the footprint, allowing daisy-chaining of additional EXP boards if a connector is soldered in.Pin 1 of the secondary EXP header is marked with a 1 in the silkscreen printing.3.1.2 EXP Header PinoutThe table below shows the pin assignments of the EXP header.Table 3.1. EXP Header PinoutNo tg n s3.2 Digi XBee Module SocketThe LTE-M Expansion Kit features two 1x10-pin 2mm pitch connectors for inserting a through-hole Digi XBee wireless module. There are also two unpopulated footprint for 1x10-pin 2.54mm (0.1") pitch pin headers which breaks out the signals of the Digi XBee module socket, an ASSOC status LED which indicates the wireless connection status of the Digi XBee module, and a reset button connected to the Digi XBee module's reset signal input.The pinout of the socket is illustrated in the figure below. The pinout of the unpopulated breakout headers are identical to the adjacent Digi XBee module socket connector.B E E _D I N X B E E _C T S B E E _D O U T X BE E _R T S N D B E E _V C CB E E _D I O 12X B E E _A DC 1X BE E _D I O 4B E E _P W M 1B E E _D T R B E E _R E S E T n B E E _R S S I X B E E _A D C 0X B E E _A D C 2X B E E _A D C 3X B E E _A S S O C X B E E _V R EF B E E _B KG O X B E E _O N Figure 3.3. Digi XBee Module SocketNo tR e co mme nd edf or e wDe si g n s3.2.1 Digi XBee Module Socket PinoutThe pin assignment of the Digi XBee module socket is given in the table below.Table 3.2. Digi XBee Module Socket Pin DescriptionsNo tR e co3.2.2 Power SupplyWhen connected to a Silicon Labs MCU or Wireless STK, the Digi XBee3 LTE-M cellular module can either be powered by the VMCU rail present on the EXP header, or through a DC-DC regulator onboard the LTE-M Expansion Kit. If connected to the VMCU rail of the starter kit, the current consumption of the Digi XBee3 LTE-M cellular module will be included in the starter kit's on-board Advanced Energy Monitor (AEM). The DC-DC regulator draws power from the 5V net, and hence, the power consumption of the Digi XBee3 LTE-M cellular module will not be included in any AEM measurements performed by the MCU STK.A mechanical power switch on the LTE-M Expansion Kit is used to select between Low Power (AEM) mode and High Power (DC-DC)mode. When the switch is set to Low Power (AEM) mode, the Digi XBee3 LTE-M cellular module is connected to the VMCU net on the EXP header. For most MCU Starter Kits, the regulator supplying the VMCU net is capable of sourcing up to 300 mA, bearing in mind that the MCU is also powered from this net. The EFM32GG11 starter kit and the Wireless Starter Kit main board are able to source up to 800 mA on the VMCU net (provided that the kit's power source is able to supply this much current). When the switch is set to High Power (DC-DC) mode, the Digi XBee3 LTE-M cellular module is connected to the output of the DC-DC converter, which is able to source up to 2 A (again, limited by the capability of the source powering the starter kit). For applications requiring higher power than what is available from the VMCU net, the power switch should be set to High Power (DC-DC) mode.The on-board GNSS receiver is powered from the same rail as the Digi XBee3 LTE-M cellular module through an analog switch that can be controlled by a GPIO pin on the EXP header.The power topology is illustrated in the figure below.Figure 3.4. LTE-M Expansion Kit Power TopologyNo tR e co mDe si g n s4. Using the LTE-M Expansion KitThe Digi XBee3 LTE-M cellular module is a wireless module providing cellular connectivity using the low-power LTE-M technology.4.1 Board IdentificationThe LTE-M EXP Board and the starter kit it is connected to are automatically identified by Simplicity Studio when connected to the computer to present the correct documentation and software examples. Note however that Simplicity studio is not able to identify which Digi XBee module is inserted into the LTE-M EXP Board's Digi XBee module socket.4.2 Digi XBee3 LTE-M ModuleThe Digi XBee3 LTE-M module requires an external antenna to enable wireless connectivity. Connect the included patch antenna to the module's u.FL connector labeled 'CELL' and insert the module into the socket as shown in the figure below, before connecting the board to a Silicon Labs MCU or Wireless starter kit.The kit also includes a SIM card, which needs to be activated before being inserted into the SIM slot of the Digi XBee3 LTE-M module.Refer to the LTE-M Expansion Kit Quick Start Guide for information on how to activate the SIM card.Figure 4.1. LTE-M Expansion Kit assembled for useUsing the LTE-M Expansion KitNo tR e co mme nd edf or N e wDe si g n s4.3 On-Board GNSS ReceiverThe LTE-M Expansion Kit is equipped with a U-Blox Cam-M8Q Global Navigation Satellite System (GNSS) receiver module that allows the user to retrieve position and time information and use it in their embedded application.The U-Blox Cam-M8Q can receive signals from both the GPS and GLONASS GNSS constellations, which provides good worldwide coverage. A reasonably clear view of the sky is required to obtain signal reception, meaning the GNSS receiver will work best outdoors.Indoor operation with reduced position accuracy is possible if the receiver has a reasonably clear view of the sky through a glass win-dow, though the reliability will be unpredictable.The GNSS receiver will output the current time and position (given that a satellite fix has been aquired) as well as satellite fix status over a UART interface using either the NMEA-0183 (default) or proprietary UBX protocol. Configuration commands can be input to the receiver using the same protocols. In addition, the receiver supports input of Differential GPS (DGPS) correction data using the RTCM 10402.3 protocol.For more information about the GNSS receiver refer to the following documents:•U-Blox Cam-M8Q Datasheet•U-Blox M8 Receiver Description Including Protocol SpecificationThe figure below shows how the GNSS receiver is connected to the rest of the board. The table below describes the signals:Figure 4.2. On-Board GNSS Receiver Connection DiagramTable 4.1. GNSS Receiver Signal DescriptionsNo td ed De si g n sThe GNSS receiver can be enabled, disabled or kept in sleep mode with RAM powered and RTC running depending on the state of the GNSS_PWR_ENABLE and GNSS_VBCKP pins according to the table below:Table 4.2. GNSS Receiver Power ModesNo tR e co mme nd edf or N e w5. Schematics, Assembly Drawings, and BOMSchematics, assembly drawings, and bill of materials (BOM) are available through Simplicity Studio when the kit documentation pack-age has been installed. They are also available from the Silicon Labs website and kit page.Schematics, Assembly Drawings, and BOMNo tR e co mme nd edf or N e wDe si g n s6. Kit Revision HistoryThe kit revision can be found printed on the kit packaging label, as outlined in the figure below.SLEXP8021A LTE-M Expansion Kit12480204218-10-15A00Figure 6.1. Kit Label6.1 SLEXP8021A Revision HistoryKit Revision HistoryNo tR e co mme nd edf or De si g n s7. Document Revision HistoryRevision 1.0October, 2018•Initial document revision.Document Revision HistoryNo tR e co mme nd edf or N e wDe si g n sSilicon Laboratories Inc.400 West Cesar Chavez Austin, TX 78701USASimplicity StudioOne-click access to MCU and wireless tools, documentation, software, source code libraries & more. Available for Windows, Mac and Linux!IoT Portfolio /IoTSW/HW/simplicityQuality/qualitySupport and CommunityDisclaimerSilicon Labs intends to provide customers with the latest, accurate, and in-depth documentation of all peripherals and modules available for system and software implementers using or intending to use the Silicon Labs products. Characterization data, available modules and peripherals, memory sizes and memory addresses refer to each specific device, and "Typical" parameters provided can and do vary in different applications. Application examples described herein are for illustrative purposes only. Silicon Labs reserves the right to make changes without further notice and limitation to product information, specifications, and descriptions herein, and does not give warranties as to the accuracy or completeness of the included information. Silicon Labs shall have no liability for the consequences of use of the information supplied herein. This document does not imply or express copyright licenses granted hereunder to design or fabricate any integrated circuits. The products are not designed or authorized to be used within any Life Support System without the specific written consent of Silicon Labs. A "Life Support System" is any product or system intended to support or sustain life and/or health, which, if it fails, can be reasonably expected to result in significant personal injury or death. Silicon Labs products are not designed or authorized for military applications. Silicon Labs products shall under no circumstances be used in weapons of mass destruction including (but not limited to) nuclear, biological or chemical weapons, or missiles capable of delivering such weapons.Trademark InformationSilicon Laboratories Inc.® , Silicon Laboratories®, Silicon Labs®, SiLabs® and the Silicon Labs logo®, Bluegiga®, Bluegiga Logo®, Clockbuilder®, CMEMS®, DSPLL®, EFM®, EFM32®, EFR, Ember®, Energy Micro, Energy Micro logo and combinations thereof, "the world’s most energy friendly microcontrollers", Ember®, EZLink®, EZRadio®, EZRadioPRO®, Gecko®, ISOmodem®, Micrium, Precision32®, ProSLIC®, Simplicity Studio®, SiPHY®, Telegesis, the Telegesis Logo®, USBXpress®, Zentri and others are trademarks or registered trademarks of Silicon Labs. ARM, CORTEX, Cortex-M3 and THUMB are trademarks or registered trademarks of ARM Holdings. Keil is a registered trademark of ARM Limited. All other products or brand names mentioned herein are trademarks of their respective holders.No tR e co md edf or N e wDe si g n s。

LTE软件使用说明1.软件安装目前测试LTE站点主要是用Probe软件，下面对此软件的安装，使用做一个简单的介绍。

由于本人刚开始使用此软件，对此软件还不是很精通，如有不妥的地方，望各位不吝赐教，不胜感激。

1.1安装概述要使用Probe的各种功能，必须正确的安装Probe软件、GENEX Shared组件。

1.2检查安装环境为了Probe软件的正常安装和运行，用户机器配置需要具备的条件如表1所示。

检查项应具备的条件CPU Pentium III 750 MHz以上显示器VGA（1024 x 768，16位颜色或以上）内存256MB以上硬盘40G以上PC端口至少一个串口、一个并口和一个USB口。

串口连接GPS或Scanner，并口连接硬件狗，USB口连接手机或USB Hub 操作系统Windows 7或Windows XP1.3拷贝软件拷贝如图1安装文件：图11.4安装GENEX Shared组件主程序安装过程会自动调用组件包安装程序。

卸载Probe主程序并不会同时卸载GENEX Shared组件，这是为了保证GENEX系列其他产品可以正常运行。

对于安装过Probe的机器，再次安装Probe时可以跳过GENEX Shared组件的安装，如果安装的是Probe升级版本时，建议同时再次安装GENEX Shared组件，因为GENEX Shared组件可能也需要升级。

安装GENEX Shared组件的步骤如下：步骤1打开图1中的Probe文件夹中的GENEX Shared安装文件，如图2所示，双击“setup.exe”文件，启动安装界面。

图2步骤2 单击“Next”。

步骤3 在协议确认对话框中，单击“Yes”。

步骤4 安装完成后，单击“Finish”。

GENEX Shared安装程序自动安装了以下组件：MapX组件：提供对Map处理的支持。

TeeChart组件：图标界面开发控件。

OWC组件：发布电子表格、图表及数据库到Web的一组控件。

RNC机房操作指导总结一．机房操作命名解析查询小区动态参数：DSP CELL查询小区静态参数LST CELL修改小区MOD CELL查询PDSCH配置信息(参考信号功率)：LST PDSCHCFGPDSCH配置信息(参考信号功率) MOD PDSCHCFG查询活动告警：LST ALMAF查看跟踪区域配置信息：LST CNOPERATORTA查询eNodeB加密算法优先级配置：LST ENODEBCIPHERCAP查询eNodeB完整性保护算法优先级：LST ENODEBINTEGRITYCAP查询小区模拟负载控制：LST CELLSIMULOAD查询PDCCH算法：LST CELLPDCCHALGO查询EUTRAN同频邻区关系：LST EUTRANINTRAFREQNCELL查询EUTRAN外部小区：LST EUTRANEXTERNALCELL添加外部邻区关系添加同频邻区关系删除EUTRAN同频邻区关系删除EUTRAN外部小区查询基站数据业务用户数：DSP S1INTERFACEA3同频切换参数修改：修改同频切换参数组：MOD INTRAFREQHOGROUPLST INTRAFREQHOGROUP异频切换参数：LST INTERFREQHOGROUPMod InterfreqhogroupLST DEVIP 查询enodeb IP配置24：跟踪区查询Lst cellop \ LST CNOPERATORTALTE 灌包查看空口环境，速率100M以上空口正常;扇区下最好一个用户，保持连接不做业务DSP ALLUEBASICINFO 查核心网分配的临时移动用户标识（如果没有临时标识了可以用UE 入网的随机值标识）DSP UEONLINEINFO, 得到核心网配置的E-RAB ID（如果没有临时标识了可以用UE入网的随机值标识；查询方式选UEID）STR UUDATATST 开始灌包，红色圈中为随意填写；端口号保持55；后台跟着小区吞吐量，查看速率（如果没有临时标识了可以用UE入网的随机值标识；查询方式选UEID）LTE电调天线后台调整命令1、DSP RETPORT 该命令用于电调天线RET端口的动态信息，查询电调开关是否打开；没有打开的话，Mod retport 打开端口。

LTE网络优化仿真系统操作手册V1.02018年5月目录1.系统架构 (2)2.基本步骤 (3)2.1.LTE场景编辑 (3)2.1.1.建立测试场景 (3)2.1.2.添加基站数据 (5)2.1.3.添加小区参数 (8)2.1.4.导出参数到Excel (26)2.2.添加测试仿真手机 (26)2.2.1.添加手机 (26)2.2.2.规划测试路径 (27)2.3.启动仿真引擎 (28)2.3.1.开始仿真 (28)2.3.2.开始按照规划测试 (29)2.4.仿真LTE路测 (29)2.4.1.启动UltraOptim (29)1.1.1.导入基站数据 (29)2.4.2.添加仿真设备 (32)2.4.3.记录测试文件 (33)2.4.4.打开地图 (34)2.4.5.查看参数视图 (35)3.专有名词 (36)1. 系统架构系统结构图LTE 仿真系统分为两大部分，LTE 无线网络优化仿真系统：负责仿真数据规划，仿真引擎，产生仿真数据。

LTE 路测仿真系统：进行LTE 路测行为仿真，LTE 网络优化数据分析。

2. 基本步骤2.1. LTE场景编辑2.1.1.建立测试场景1)打开“LTE网络优化仿真”右键点击左侧导航栏的“场景文件列表”，选择新建场景。

2)填写场景名称3)右键点击新建的场景，选择“地图显示”4)点击右侧地图页面上的“图层编辑”按钮5)如上图，在地图右侧的场景属性中修改场景的全局参数参数：●MCC: Mobile Country Code，移动国家码，MCC的资源由国际电联（ITU）统一分配和管理，唯一识别移动用户所属的国家，共3位，中国为460;●MNC2~3位数字组成。

●传播模型: Cost231-Hata，FastTrModel，仿真引擎所使用的空间传播模型。

●空间类型: 场景的地域参数。

2.1.2.添加基站数据2.1.2.1.定位到仿真测试区域点击地图菜单栏的“定位菜单”，，输入重庆市坐标，经度：106.6069，纬度：29.5352，定位到重庆市2.1.2.2.部署基站点击菜单“部署基站”，2.1.2.3.编辑基站基本属性参数：•TAC: TAC (Tracking area code of cell served by neighbor Enb)参数中文名称:跟踪区域码；参数英文名称:Tracking area code of cell served by neighbor eNB 引用关系:3GPP Reference: TS 36.423功能类别:工程参数；功能描述（参数功能原理简介）本参数定义了小区所属的跟踪区域码，一个跟踪区域可以涵盖一个或多个小区；影响范围：CELL；设备影响级别:2级网络影响级别:2级数据类型：整数；参数取值范围：●TAC:TAC (Tracking area code of cell served by neighbor Enb)●参数取值范围：0...65535物理取值范围：0...65535物理单位：无●调整原则与建议值：该参数设置过大，将会导致寻呼信道的拥塞；设置过小，将会导致位置更新过多，导致系统信令信道的拥塞。