DOCSLIB.ORG

Iot Device Management Development Guide Contents

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Iot Device Management Development Guide Contents IoT Device Management Development Guide Issue 02 Date 2019-08-28 HUAWEI TECHNOLOGIES CO., LTD. Copyright © Huawei Technologies Co., Ltd. 2019. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd. Trademarks and Permissions and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders. Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied. Issue 02 (2019-08-28) Copyright © Huawei Technologies Co., Ltd. i IoT Device Management Development Guide Contents Contents 1 Product Development................................................................................................................... 1 1.1 Obtaining Development Resources................................................................................................................................ 1 1.2 Creating a Project and Product....................................................................................................................................... 4 1.3 Developing a Product Model..........................................................................................................................................9 1.3.1 Development Guide.....................................................................................................................................................9 1.3.2 Offline Development................................................................................................................................................. 14 1.3.2.1 Profile Writing Guide............................................................................................................................................. 14 1.3.2.2 Profile Providing Method....................................................................................................................................... 17 1.3.2.3 Profile Field Description........................................................................................................................................ 18 1.3.3 Reference................................................................................................................................................................... 29 1.3.3.1 Product Model Sample........................................................................................................................................... 29 1.3.3.2 Fields in the Profile Sample....................................................................................................................................38 1.4 Developing a Codec......................................................................................................................................................49 1.4.1 Development Guide...................................................................................................................................................49 1.4.2 Offline Development................................................................................................................................................. 64 1.4.2.1 Preparing the Development Environment.............................................................................................................. 65 1.4.2.2 Importing the DEMO Project of the Codec............................................................................................................67 1.4.2.3 Developing a Codec................................................................................................................................................69 1.4.2.4 Packaging the Codec.............................................................................................................................................. 69 1.4.2.5 Inspecting the Quality of the Codec....................................................................................................................... 72 1.4.2.6 Signing the Codec Package with an Offline Signature...........................................................................................76 1.4.3 Codec Development Examples..................................................................................................................................78 1.4.3.1 Codec for Data Reporting and Command Delivery............................................................................................... 78 1.4.3.2 Codec for Multiple Data Reporting Messages....................................................................................................... 86 1.4.3.3 Codec for Strings and Variable-Length Strings......................................................................................................99 1.4.3.4 Codec for Arrays and Variable-Length Arrays.....................................................................................................117 1.4.3.5 Codec for Containing Command Execution Results............................................................................................135 1.4.4 Reference................................................................................................................................................................. 150 1.4.4.1 Message Processing Flow.....................................................................................................................................151 1.4.4.2 decode API Description........................................................................................................................................152 1.4.4.3 Description of encode API................................................................................................................................... 156 1.4.4.4 getManufacturerId Interface Description............................................................................................................. 159 1.4.4.5 getModel Interface Description............................................................................................................................ 160 Issue 02 (2019-08-28) Copyright © Huawei Technologies Co., Ltd. ii IoT Device Management Development Guide Contents 1.4.4.6 Precautions on Interface Implementation............................................................................................................. 160 1.4.4.7 Input/Output Format of the Codec Plug-In...........................................................................................................163 1.4.4.8 Implementation Sample Interpretation................................................................................................................. 165 1.4.4.9 Appendix: Encryption Algorithms Supported by the JDK...................................................................................173 1.5 Developing an Application.........................................................................................................................................174 1.5.1 Application Connection to the IoT Platform........................................................................................................... 175 1.5.2 Data Subscription.................................................................................................................................................... 176 1.5.3 Device Registration................................................................................................................................................. 178 1.5.4 Device Access to the IoT Platform..........................................................................................................................179 1.5.5 Data Reporting.........................................................................................................................................................180 1.5.6 Command Delivery..................................................................................................................................................182 1.5.7 Development of Other APIs.................................................................................................................................... 183 1.5.8 Reference................................................................................................................................................................. 183 1.5.8.1 Preparing the Java Development Environment.................................................................................................... 183 1.5.8.1.1 Installing JDK 1.8..............................................................................................................................................183 1.5.8.1.2 Configuring Java Environment Variables (Windows OS).................................................................................183
Load more

Recommended publications
  • A Comparative Study Between Operating Systems (Os) for the Internet of Things (Iot)
    VOLUME 5 NO 4, 2017 A Comparative Study Between Operating Systems (Os) for the Internet of Things (IoT) Aberbach Hicham, Adil Jeghal, Abdelouahed Sabrim, Hamid Tairi LIIAN, Department of Mathematic & Computer Sciences, Sciences School, Sidi Mohammed Ben Abdellah University, [email protected], [email protected], [email protected], [email protected] ABSTRACT Abstract : We describe The Internet of Things (IoT) as a network of physical objects or "things" embedded with electronics, software, sensors, and network connectivity, which enables these objects to collect and exchange data in real time with the outside world. It therefore assumes an operating system (OS) which is considered as an unavoidable point for good communication between all devices “objects”. For this purpose, this paper presents a comparative study between the popular known operating systems for internet of things . In a first step we will define in detail the advantages and disadvantages of each one , then another part of Interpretation is developed, in order to analyze the specific requirements that an OS should satisfy to be used and determine the most appropriate .This work will solve the problem of choice of operating system suitable for the Internet of things in order to incorporate it within our research team. Keywords: Internet of things , network, physical object ,sensors,operating system. 1 Introduction The Internet of Things (IoT) is the vision of interconnecting objects, users and entities “objects”. Much, if not most, of the billions of intelligent devices on the Internet will be embedded systems equipped with an Operating Systems (OS) which is a system programs that manage computer resources whether tangible resources (like memory, storage, network, input/output etc.) or intangible resources (like running other computer programs as processes, providing logical ports for different network connections etc.), So it is the most important program that runs on a computer[1].
    [Show full text]
  • Iot Ecosystem Brand White Paper
    IoT Ecosystem Brand White Paper The Standards and Definition of IoT Ecosystem Brand September 20th, 2020 IoT Ecosystem Brand White Paper 1 There are times when it is wise for important role in business growth Foreword corporations to take a pregnant in the years to come. Frameworks pause. To look around and see if the that encourage entrepreneurism very things that have made them and put the customer at the center successful are the right ingredients of the organisation to create lasting to secure success in the future. lifetime value right across a vibrant ecosystem. As a diligent student of corporate history and business transformation But here is the issue that has been myself it is often easy to spot, with troubling me and many others for the magic of hindsight, the point at some time. which a successful company started to fail. From then on, it's often a long, Our financial accounting models, undignified journey of management performance metrics, calculations denial and subsequent terminal of economic profit, ROCE and many David Roth decline with the destruction of much of the established metrics that shareholder value along the way. analysts plug into their spreadsheets to uncover hidden value, are all CEO The Store WPP, Corporations have a bad habit of part of an old model - a model not Chairman BrandZTM thinking they will last forever - that's designed for an ecosystem era. and BAV Group, how they are built and structured. Global They struggle to extract onto the Consumers and customers have a balance sheet the true value the very different mindset as viewed ecosystem is creating, the value to through the lens of their changing the firm, it's ecosystem partners and attitudes and bonds towards the their respective brands.
    [Show full text]
  • Huawei HCIA-Iot V. 2.5 Evaluation Questions Michel Bakni
    Huawei HCIA-IoT v. 2.5 Evaluation Questions Michel Bakni To cite this version: Michel Bakni. Huawei HCIA-IoT v. 2.5 Evaluation Questions. Engineering school. Huawei HCIA-IoT v. 2.5, Bidart, France. 2021, pp.77. hal-03189245 HAL Id: hal-03189245 https://hal.archives-ouvertes.fr/hal-03189245 Submitted on 2 Apr 2021 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Distributed under a Creative Commons Attribution| 4.0 International License Huawei HCIA-IoT v. 2.5 Evaluation Questions March 2021 Michel BAKNI Author: Michel BAKNI Editor: Sandra HANBO Version: 1.0 , 2021 DOI: 10.6084/m9.figshare.14336687 Copyright notice This work is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0) You are free to: Share — copy and redistribute the material in any medium or format Adapt — remix, transform, and build upon the material for any purpose, even commercially. The licensor cannot revoke these freedoms as long as you follow the license terms: Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
    [Show full text]
  • RIOT, the Friendly Operating System for The
    The friendly operating system for the IoT by Thomas Eichinger (on behalf of the RIOT community) OpenIoT Summit NA 2017 Why? How? What is RIOT? Why? How? What is RIOT? Why a software platform for the IoT? ● Linux, Arduino, … bare metal? ● But as IoT software evolves … ○ More complex pieces e.g. an IP network stack ○ Evolution of application logic ● … non-portable IoT software slows innovation ○ 90% of IoT software should be hardware-independent → this is achievable with a good software platform (but not if you develop bare metal) Why a software platform for the IoT? ✓ faster innovation by spreading IoT software dev. costs ✓ long-term IoT software robustness & security ✓ trust, transparency & protection of IoT users’ privacy ✓ less garbage with less IoT device lock-down Why? How? What is RIOT? How to achieve our goals? Experience (e.g. with Linux) points towards ● Open source Indirect business models ● Free core Geopolitical neutrality ● Driven by a grassroot community Main Challenges of an OS in IoT Low-end IoT device resource constraints ● Kernel performance ● System-level interoperability ● Network-level interoperability ● Trust SW platform on low-end IoT devices ● The good news: ○ No need for advanced GUI (a simple shell is sufficient) ○ No need for high throughput performance (kbit/s) ○ No need to support dozens of concurrent applications ● The bad news: ○ kBytes of memory! ○ Typically no MMU! ○ Extreme energy efficency must be built in! SW platform on low-end IoT devices ● Contiki ● mbedOS (ARM) ● ● Zephyr (Intel) ● TinyOS ● LiteOS (Huawei) ● myNewt ● … ● FreeRTOS ● and closed source alternatives Reference: O. Hahm et al. "Operating Systems for Low-End Devices in the Internet of Things: A survey," IEEE Internet of Things Journal, 2016.
    [Show full text]
  • Iot Connectivity Platform SDN/NFV Platform: Transforming Telco Network to Cloud
    Building a Better Connected World in Digital Economy “Open, Collaborative and Sharing” Dr. Sanqi Li CTO, Huawei Products & Solutions ICT Cloud Transformation Foundation of Next Digital Revolution Industry Players (Services) Private Public Hybrid Data Center Internet (Cloud) 3-5G NFV Communications Internet (Network) SDN IoT GW Industrial Internet (Device) Platform Revolution In ICT Cloud Transformation Open Developer Ecosystem: Open, Collaborative and Sharing Platform Initiatives Big Data Video IoT Digital PaaS/IaaS SDN/NFV Connect Operation Product Portfolios Product Server & Smart MBB FBB Core OSS VAS IoT GW UC&C Security Enterprise Network Network Storage Phone Wearable VR & BSS CT Category IT Category Consumer Category Platform Construct Consisting of Many Open Source Components Open Developer Ecosystem: Open, Collaborative and Sharing Big Data Video IoT Digital PaaS/IaaS SDN/NFV Connect Operation DC Infrastructure DC Platform Big Data Analytics Network Infrastructure Operation Tool Set Building Open Source Ecosystem Huawei Leadership Position NFV Top 1 KERNEL Contributor Platinum Member 9 Lead Roles, Top 3 1 Long Term 3 WG Chairs Open-O Contributor Maintainer Gold Member Founding Top 6 Member 1 Committer Contributor Board Director Top 2 Founding Member Top 5-8 Contributor 2 Committers Contributors Founding Member Top 2 Top 4 Strategic Contributor Contributor Partner “Platform + Product” Solutions Huawei Early Business Success Open Developer Ecosystem: Open, Collaborative and Sharing SDN/NFV Digital Video Big Data FusionSphereOperation
    [Show full text]
  • Liteos Version 0.2 Quick Start Guide
    LiteOS User’s Guide Version 2.1 Last updated: Oct 2 2011 This guide illustrates how to get started as well as an In-depth description of the LiteOS operating system. Download location: www.liteos.net Copyright ©2007-2011 LiteOS developers, all rights reserved. LiteOS User’s Guide Contents Preface ............................................................................................................................................. 4 References ....................................................................................................................................... 4 Installation of LiteOS ........................................................................................................................ 5 Installing LiteOS on Windows machine ........................................................................................ 5 Installing JDK ................................................................................................................................ 6 Installing Cygwin .......................................................................................................................... 6 Check that Cygwin and Java have been correctly configured ...................................................... 6 Install the AVR Studio 5.0 ............................................................................................................ 7 Get familiar with your equipment ............................................................................................... 8 A bare-bone Blink example
    [Show full text]
  • Wireless Sensor Network (WSN)
    Catherine Greene Chloe Norris CREU 2010-2011 Wireless Sensor Network (WSN) Detects Uses Temperature Industrial process & Sound monitoring Vibrations Machine monitoring Pressure Monitoring the Motion environment Pollutants Healthcare Home automation Traffic control Source: http://en.wikipedia.org/wiki/Wireless_sensor_network Nodes What it consists of Prices Can have more than one Varies sensor Size Usually has a radio Complexity transceiver A more complex sensor For wireless could be a few hundred communication A less intricate one Small microcontroller could be fairly cheap Energy source Ex: battery Source: http://en.wikipedia.org/wiki/Wireless_sensor_network How they work Sensors support a multi-hop routing algorithm nodes function as forwarders Relay data packets to a base station (known as a wireless ad-hoc network) Think of a sensor like a computer Source: http://en.wikipedia.org/wiki/Wireless_sensor_network Applications Area Monitoring WSN would be put in an area where something is being monitored Ex: a country at war with another may place nodes over a battlefield to detect enemy intrusion, sensors would detect heat, pressure, sound, light, electro-magnetic fields, vibrations, etc… If a sensor went off it would report it to a base station (message might be sent through internet or satellite) Ex: detecting vehicles Source: http://en.wikipedia.org/wiki/Wireless_sensor_network Applications Environmental Monitoring Similar to area monitoring Ex (pictured): state of permafrost in the Swiss Alps
    [Show full text]
  • CCS Insight Wearables Insight Huawei
    Huawei's New Smartwatch Abandons Wear OS Summary On 16 October 2018, Huawei held a major event in London centred on the launch of its Mate 20 series smartphones. Here we examine the wearable devices also announced at the event. Insight ▪ At the launch event in London, Huawei revealed its latest flagship smartwatch, the Watch GT. It features the proprietary LiteOS operating system, rather than Google's Wear OS. ▪ Huawei also unveiled the Band 3 Pro as the company continues to focus on the fitness-tracking category of wearables. Analysis Huawei Watch GT During a launch event focussed on new Mate 20 series smartphones, Huawei unveiled its latest smartwatch, called the Watch GT (see Figure 1). It comes almost two years after the Huawei Watch 2 was launched in Barcelona (see Mobile World Congress 2017: Wearables). Most notable of the new watch's features was Huawei's decision against using Wear OS, which ran on its previous two generations of smartwatches. Figure 1. Huawei Watch GT Sport and Watch GT Classic Source: Huawei The Watch GT runs LiteOS, Huawei's own operating system for small connected devices. LiteOS is open source, and Huawei claims to be collaborating with its LiteOS partners to help build "a better ecosystem" for the Internet of things. LiteOS has been previously used by Huawei in its fitness watches and trackers. Powering the Watch GT is a custom chipset developed in-house and based on Arm's Cortex-M4 design. It contrasts with the Qualcomm Snapdragon processors found in previous Huawei smartwatches. The silicon features a "double chipset" architecture; a high-power processor performs computing-intensive tasks and a lesser one handles tasks such as the always-on display.
    [Show full text]
  • Analysis of Thread Schedulability in Huawei Liteos
    MATEC Web of Conferences 336, 05031 (2021) https://doi.org/10.1051/matecconf/202133605031 CSCNS2020 Analysis of thread schedulability in Huawei LiteOS Xiaochun Wang1,* 1School of AI, Shenzhen Polytechnic, 518055, Shenzhen, Guangdong, China Abstract. Huawei LiteOS is a real-time operating system. Thread schedulability is an important thing to be considered first when we use the RTOS in an application. There are a lot of methods to value thread schedulability in practical application. Rate monotonic scheduling algorithm is a widely used static priority scheduling algorithm. We discussed the thread schedulability in Huawei LiteOS. 1. Foreword Huawei LiteOS is lightweight IoT operating system, it is a real-time operating system. According to the document of the LiteOS[1], the minimum size of the kernel will be under 10KB, so the product use LiteOS will consume very little power and have a faster response. How about the performance of the LiteOS when it is in a real-time environment? In Huawei LiteOS, it guaranteed the highest-priority thread scheduling, which will meet the time critical system demands. Huawei LiteOS used as a real-time operating system in many application area, such as smart homes, wearables, Internet of Vehicles (IoV), and intelligent manufacturing. A real time application product must be designed to meet time demands, the system is not only need to provide the correct response, but also need to respond within a specified period. It is must important to make sure that threads will be scheduled before its deadlines in Huawei LiteOS. Rate Monotonic scheduling algorithm (RM[2]) is an static-priority algorithm.
    [Show full text]
  • Hi3559 V100 Professional 2K／4K Mobile Camera Soc Brief Data Sheet
    Hi3559 V100 Hi3559 V100 Professional 2K/4K Mobile Camera SoC Introduction Key Specifications Hi3559 V100 is a new-generation MobileCamTM z 4K30/1440P60 H.265 Encoding intelligent video processor provided by HiSilicon, a leading 4K@30 fps+1080p@30 fps or 1440p@60 fps+1080p@30 supplier in the global ultra-HD video technologies. The Hi3559 fps H.265 encoding V100 processor is launched for the professional camera, high- end drone camera, extreme sports motion DV, 3D/VR camera, z Dual-Sensor Inputs and high-end EDR product fields. 2K x 2K@30 fps 3D or 3K x 3K@15 fps dual-fisheye Hi3559 V100 uses the HiSilicon fifth-generation Hi-Lark inputs high-performance video encoder, which supports simultaneous z 6-DoF DIS 4K@30 fps encoding and 1-channel 1080p@30 fps small- z High-Speed Memory Interfaces stream encoding. Besides, it can also record high-frame-rate videos such as 2K@60 fps, 1080p@120 fps, and 720p@240 USB 3.0 or PCIe 2.0 high-speed interface fps. z RAW Video Output Hi3559 V100 uses the HiSilicon fourth-generation Hi-ISP Professional 1080p@30 fps video RAW output high-performance graphics processor and adopts the latest 3A, z Low Power Consumption 3DNR, and HDR technologies to achieve professional picture effect. Hi3559 V100 supports dual sensor inputs and maximum 1.25 W typical power consumption in the 4K@30 16-megapixel and 8-megapixel video processing to flexibly fps+1080p@30 fps H.265 encoding scenario support the service scenarios that required dual-channel z Miniaturization Package recording, such as the 3D/VR camera.
    [Show full text]
  • Pressrelease HUAWEI Develop
    ! PRESSMEDDELANDE Huawei utvecklarkonferens - Huawei bygger ekosystem och lockar samarbetspartners Huawei arrangerade utvecklarkonferensen Huawei Developer Conference (HDC) vid deras Songshan Lake-säte i Dongguan. 600 teknikexperter från Huawei träffade nästan 6000 utvecklare och samarbetspartners från hela världen för att prata om teknik och globala ekosystem under temat ”Rethink Possibilities”. Konferensen syftar till att utforska framtidens AI-baserade ekosystem, som ska ge en fulländad upplevelse för varje användare. När Huawei fortfarande var ny på marknaden, sålde företaget tre miljoner mobiltelefoner. Åtta år senare har antalet ökat 68 gånger om. Under första kvartalet 2019 sålde Huawei 118 miljoner mobiltelefoner, vilket är 17,6 procent av den globala mobilmarknaden enligt IDC och därtill en ökning med 24 procent från föregående år. Men även surfplattor, datorer och bärbara enheter har bidragit till Huaweis snabba tillväxt. Idag finns företaget i över 170 länder och har 530 miljoner användare. Huaweis öppna plattform, Huawei HiAI, har mer än 2500 partners och över 140 miljoner IoT-enheter världen över stödjer HiLink- protokoll. Huawei presenterade under konferensen det microkernel-baserade operativsystemet HarmonyOS och visade operativsystemets fördelar. Operativsystemet markerar en ny era av Internet of Everything och ger utvecklare effektiva verktyg som stöttar enkel utveckling av programvara till flera enheter. - HarmonyOS kopplar samman allt och öppnar för en miljardmarknad. HarmonyOS är inte bara till för idag och i morgon, utan är en katalysator för all teknik i framtiden. Huawei är dedikerade till att förbättra sina tekniker, inklusive chip och OS, med mål att hjälpa kunder och utvecklare, säger Yu Chengdong, vd för Huaweis Consumer Business. HarmonyOS är ett operativsystem med öppen källkod och med hjälp av Huawei Mobile Services (HMS) för globala utvecklare går det snabbt att komma åt HMS-ekosystemet för resursdelning.
    [Show full text]
  • Huawei Liteos 不开发者共建物联网生态
    Security Level: Huawei LiteOS 不开发者共建物联网生态 华为物联网终端操作系统 Huawei LiteOS运营总监 林旅强 Richard Lin 千亿物联时代需要物联网操作系统 10亿连接 150亿连接 1000亿连接 PC时代 移劢互联网时代 物联网时代 x86架构电脑 ARM架构手机 x86/ARM/DSP/MIPS/FPGA… 各种终端 Windows Android/iOS 物联网操作系统 2 物联网操作系统让终端更智能 终端智能化是物联网发展的基础 华为提供完整、标准化物联网操作系统LiteOS，加速终端智能化进程 3 Huawei LiteOS 发展进程 • 手机、穿戴出货30M+ • IoT设备出货100K+ 2017~ 2016 手机、穿戴破亿 IoT 设备的出货量 2015 会超过3M 通过开源策略，LiteOS进入IoT市场 2014 使用 LiteOS 的多款华为智 2012 能手机开始出货，包括 Mate, Honor, P-series手机 开始内部开发LiteOS， 支持华为消费类产品 4 Huawei LiteOS物联网操作系统 哑终端 Huawei 智能终端 LiteOS Open APIs 互联框架 传感框架 安全框架 内核 [ 轻量级 ] [ 联接智能 ] [ 组网智能 ] [ 管理智能 ] • 可伸缩内核 • WiFi、Zigbee、 • 优化的Mesh自组 • 丌同类型、丌同接口传感器的 • uA级功耗 NB-IoT等短距、 网，组网快、组网 统一管理，即插即用 • uS级响应 长距协议设备的 稳、组网多 • 端管云协同的安全管理，降低 互联互通 终端被攻击的风险 5 Huawei LiteOS，1个轻量级内核+N个框架 Open APIs 互联框架 传感框架 安全框架 多协议设备互联互通、自组网 统一多传感器的管理 提供终端的安全能力 应用Profile 自组网 APIs 传感算法库 双向设备讣证 互联互通（HTTP/CoAP/MQTT/LWM2M） 传感器管理 低功耗DTLS 通信协议 网络协议栈 BLE/WiFi/6LowPAN/Zigbee/ uIP/lwIP/RPL 驱劢管理 FOTA安全升级 PLC/NB-IoT POSIX接口（Libc/Libm/STL C/C++语言标准库） • 可伸缩，最小到6KB • uA级功耗 内核功能 任务管理 内存管理 中断管理 SafeArea … 轻量 级内 • uS级响应 硬件抽象层 核 • 支持多种芯片架构 芯片驱劢 外设驱劢 • 提供标准接口 ARM Cortex-M0，Cortex-M3，Cortex-M4，Cortex-M7 ARM Cortex-A7，Cortex-A17，Cortex-A53 ARM11 X86 DSP 6 Huawei LiteOS 开放能力不应用 MCU伙伴 • 开放源码、可裁剪 • 可自定义协议栈 ① MCU LiteOS全栈+APP + 模组Modem ② 通信Soc（LiteOS系统+APP） 开源、开放 7 在LPWA芯片上的实践效果不优势 超低功耗安全连接能力 内核：小体积、响应快 组件驱劢、多场景 System Components LiteOS XXRTOS Task Y Y Boudica Management Memory LiteOS XXRTOS Y Y A-Core with LiteOS Basic Management Kernel Event Stack 数据传输层安全 RAM for Kernel (KB) 6.5 10.25 Y Y Management 协议增，标准版 Task
    [Show full text]