RUCKUS携手JOYMAKE 打造物联网医疗解决方案

Deploying APIs to a Ruckus Smartzone Controller This document is to help in the use and deployment of API call to a Ruckus Smartzone 3.4 Controller. The below link is a reference to the locations we will be using as well as a host of other API calls you will ever need. In the location, the first part is a version folder location. This is specific to versions of Smartzone. Here is an example:Smartzone version 3.2 - /v3_0Smartzone version 3.4 - /v4_0Smartzone API Reference 3.4:/vscg-enterprise/vsz-e-public-api-reference-guide-3-4.htmlTo deploy API commands to a Smartzone controller, there are several ways to accomplish this. For this demonstration, we will be using Postman by Google.First, you will need to download and install Postman:https:///Once you have Postman installed, create a new Collection. This is where we will keep our API Calls. Create a Collection:Create an Environment:Select the Gear and Manage Environments:Select Add:Give the Environment a Name and Select Add:Inside the Environment is where we will define variables for you API calls. The Key will be the variable name and the Value will be the value for the Key.You will need to add two header values to every API you create. Below is an explanation and the values.Create a Login Session API Call:Select POST and add the destination to the controller and the location for this call. I have used a variable for the destination. Here is a break down:{{LabvSz}} - https://{host}:7443/api/public (Where {host} is the IP Address or Hostname of your controller). If you use the {{LabvSz}}, this is a variable created in your environment./v4_0/session is the location.Under the Headers Tab, add the two fields for all your API Calls:Content-Type - application/json;charset=UTF-8Cookie - JSESSIONID={JSESSIONID}Headers TabUnder the Body Tab, you need to add the username and password to login to the controller. You will use the raw format and it must be formatted exactly as below. The apiVersion can be left to the default and the timeZoneUtcOffset is the time zone of the controller.Body TabWhen you are done, select the down arrow next to Save to do Save As.Save the API to the Collection Name you created earlier.Retrieve the System Summary API:Now we are going to create an API to Retrieve the System Summary.For this call Use GET and add the destination URL plus the location (/v4_0/controller). Remember to add the header information as above and Save AS when you are done.To execute this call, select the send button.Below is a Sample Output:Retrieve AP List API:Now we are going to create an API to retrieve a list of APs from the controller.For this call Use GET and add the destination URL plus the location (/v4_0/aps). Remember to add the header information as above and Save AS when you are done. Below is the command and sample output.AP MACIn this example, we received a list of APs from the controller. I only have one AP. From here we can get the MAC Address of the AP to use in the next API.Retrieve AP Information API:Now we are going to create an API to retrieve information about a specific AP from the controller.For this call Use GET and add the destination URL plus the location (/v4_0/aps/{apMac}). For this example, we need the AP MAC Address from the last example to replace {apMac}. Remember to add the header information as above and Save AS when you are done. Below is the command and sample output.AP MACNow we are going to create an API to retrieve a list of AP Zones from the controller.For this call Use GET and add the destination URL plus the location (/v4_0/rkszones). Remember to add the header information as above and Save AS when you are done. Below is the command and sample output.Default Zone ID We will use the “Default Zone” ID to perform the next API.Now we are going to create an API to create a WLAN Group on the controller.For this call Use POST and add the destination URL plus the location(/v4_0/rkszones/{zoneId}/wlangroups). Remember to add the header information as above. Here wewill also have to add information to the Body Tab. The body tab has the name of the WLAN Group we want to create and the Description. This is input in the raw format. Refer to the API Guide for more details. Be sure to Save AS when you are done. Below is the command and sample output.Zone ID fromprevious exampleBody TabInput must be formattedexactly as aboveWhen you execute this command with the Send Button, you will see the following:ID for new WLAN GroupNow we are going to create an API to delete a WLAN Group on the controller.For this call Use DELETE and add the destination URL plus the location(/v4_0/rkszones/{zoneId}/wlangroups/{id}). We will use the zone ID from the previous example and the ID of the WLAN Group we want to delete. This can be found from a retrieve WLAN List API. Rememberto add the header information as above and Save AS when you are done.Below is the output from the Retrieve WLAN Group List: Total Count is 2 for my example.ID of the WLAN Group todeleteBelow is the command and sample output.Now we run the WLAN Group Retrieve API again and the group has been deleted. Total Count is now one.ID of the WLAN Group todeleteCreate a Logout API:When you are finished, we need to logout of the controller. For this call Use DELETE and add the destination URL plus the location (/v4_0/session). Remember to add the header information as above and Save AS when you are done.This is only the beginning of the APIs you can create. Please refer to the API Guide for reference.。

Wi-SUN SDK 1.3.2.0 GAGecko SDK Suite 4.1 September 28, 2022Wireless Smart Ubiquitous Network (Wi-SUN) is the leading IPv6 sub-GHz mesh tech-nology for smart city and smart utility applications. Wi-SUN brings Smart Ubiquitous Networks to service providers, utilities, municipalities/local government, and other enter-prises, by enabling interoperable, multi-service, and secure wireless mesh networks. Wi-SUN can be used for large-scale outdoor IoT wireless communication networks in a wide range of applications covering both line-powered and battery-powered nodes. Silicon Labs' Wi-SUN hardware is certified by the Wi-SUN Alliance, a global industry association devoted to seamless LPWAN connectivity. Wi-SUN builds upon open stand-ard internet protocols (IP) and APIs, enabling developers to extend existing infrastruc-ture platforms to add new capabilities. Built to scale with long-range capabilities, high-data throughput and IPv6 support, Wi-SUN simplifies wireless infrastructure for industrial applications and the evolution of smart cities.These release notes cover SDK versions: 1.3.2.0 released September 28, 2022 1.3.1.0 released August 17,2022 1.3.0.0 released June 8, 2022Compatibility and Use NoticesFor information about security updates and notices, see the Security chapter of the Gecko Platform Release notes installed with this SDK or on the TECH DOCS tab on https:///developers/wi-sun-protocol-stack . Silicon Labs also strongly recommends that you subscribe to Security Advisories for up-to-date information. For instructions, or if you are new to the Silicon Labs Wi-SUN SDK, see Using This Release . Compatible Compilers:IAR Embedded Workbench for ARM (IAR-EWARM) version 9.20.4 •Using wine to build with the IarBuild.exe command line utility or IAR Embedded Workbench GUI on macOS or Linux could result in incorrect files being used due to collisions in wine’s hashing algorithm for generating short file names.•Customers on macOS or Linux are advised not to build with IAR outside of Simplicity Studio. Customers who do should carefully verify that the correct files are being used.GCC (The GNU Compiler Collection) version 10.3-2021.10, provided with Simplicity Studio.Contents Contents1Wi-SUN Stack (2)1.1New Items (2)1.2Improvements (2)1.3Fixed Issues (2)1.4Known Issues in the Current Release (3)1.5Deprecated Items (3)1.6Removed Items (3)2Wi-SUN Applications (4)2.1New Items (4)2.2Improvements (4)2.3Fixed Issues (4)2.4Known Issues in the Current Release (4)2.5Deprecated Items (4)2.6Removed Items (4)3Using This Release (5)3.1Installation and Use (5)3.2Security Information (5)3.3Support (6)1 Wi-SUN Stack1.1 New ItemsAdded in release 1.3.0.0•Most of the stack crypto operations are now made through ARM PSA Crypo API.•Added a new API sl_wisun_set_device_private_key_id() that indicates which PSA Crypto key handler contains the de-vice private key and has to be used by the stack. It is the application’s responsibility to create the key.•Added a new API sl_wisun_set_regulation() that configures the regional regulation to which the stack must comply. Refer to UG495: Silicon Labs Wi-SUN Developer's Guide for more information about regional regulation in the Wi-SUN Stack.•Added a new event SL_WISUN_MSG_REGULATION_TX_LEVEL_IND_ID that is fired when the transmission budget crosses one of the transmission budget thresholds. The transmission budget is defined by the regional regulation. Refer to UG495: Silicon Labs Wi-SUN Developer's Guide for more information about regional regulation in the Wi-SUN Stack.•Added a new API sl_wisun_set_regulation_tx_thresholds()that configures the threshold used to fire SL_WISUN_MSG_REGULATION_TX_LEVEL_IND_ID event.•Added a new API sl_wisun_set_advert_fragment_duration() that configures the asynchronous transmission fragment duration. It can be used to reduce the impact on the latency of long advertisement periods.•Added a new API sl_wisun_set_unicast_tx_mode() that enables a high-reliability transmission mechanism for unicast communication. It trades off unicast communication reliability for latency.1.2 ImprovementsChanged in release 1.3.1.0•When ARIB radio regulation is selected, the stack refuses all EDFE initialization requests sending an EDFE final frame.Changed in release 1.3.0.0•sl_wisun_set_channel_mask() channel filter is now applied to asynchronous transmissions and unicast listening schedule.The function was renamed sl_wisun_set_allowed_channel_mask() to make it more self-explanatory.1.3 Fixed IssuesFixed in release 1.3.2.01023782 Fixed an invalid Path Control field configuration in RPL DAO packet.Fixed in release 1.3.1.0851960 Fixed PAN Advert and PAN Config Trickle timer configuration. Inconsistent transmissions were not correctly managed. It could lead to suboptimal behavior in dense areas of a network.840698Fixed a performance issue that was causing Linux Border Router RCP to become unreachable when running throughput tests with high-speed data rates. That issue was fixed by using DMA to collect UART data.853035 Fixed an initialization issue that was causing PAN Advert and PAN Config asynchronous transmission requests to be dropped. That issue was most likely to happen with TEST and SMALL network size configuration and couldcause connection durations to be significantly longer.Fixed in release 1.3.0.0Fixed an error that was causing radio calibrations to be skipped during Wi-SUN Stack initialization. 8134407742901.4 Known Issues in the Current ReleaseNone1.5 Deprecated ItemsNone1.6 Removed ItemsNoneWi-SUN Applications 2 Wi-SUN Applications2.1 New ItemsAdded in release 1.3.0.0iPerf2 support•Integrated into Wi-SUN - SoC Network Measurement Application•Option to install the Iperf2 component to other applications alsoWi-SUN Configurator – UI Tool•Configuration options are being used by the Applications automatically•MAC Address•MAC Allow/Deny List•Unicast Dwell IntervalCoAP discovery feature (limited, RFC 6690):•Register Resources•Return list of Registered Resources in response to GET .well-known/core request2.2 ImprovementsAdded in release 1.3.1.0Wi-SUN Linux Border Router RCP•Released version 1.1.0•It now collects UART data using a DMA.2.3 Fixed IssuesNone2.4 Known Issues in the Current ReleaseIssues in bold were added since the previous release.Simplicity Studio – Network Analyzer: Wi-SUN Encrypted Packets arenot supported.2.5 Deprecated ItemsNone2.6 Removed ItemsRemoved in release 1.3.0.0•Wi-SUN - SoC Border Router with backhaul.3 Using This ReleaseThis release contains the following•Wi-SUN stack library•Wi-SUN sample applications•Wi-SUN border router pre-compiled demos•DocumentationIf you are a first time user, see QSG181: Silicon Labs Wi-SUN Quick-Start Guide.3.1 Installation and UseThe Wi-SUN SDK is provided as part of the Gecko SDK (GSDK), the suite of Silicon Labs SDKs. To quickly get started with the GSDK, install Simplicity Studio 5, which will set up your development environment and walk you through GSDK installation. Simplicity Studio 5 includes everything needed for IoT product development with Silicon Labs devices, including a resource and project launcher, software configuration tools, full IDE with GNU toolchain, and analysis tools. Installation instructions are provided in the online Simplicity Studio 5 User’s Guide.Alternatively, Gecko SDK may be installed manually by downloading or cloning the latest from GitHub. See https:///SiliconLabs/gecko_sdk for more information.Simplicity Studio installs the GSDK by default in:•(Windows): C:\Users\<NAME>\SimplicityStudio\SDKs\gecko_sdk•(MacOS): /Users/<NAME>/SimplicityStudio/SDKs/gecko_sdkDocumentation specific to the SDK version is installed with the SDK.3.2 Security InformationSecure Vault IntegrationThis version of the stack does not integrate Secure Vault Key Management.Security AdvisoriesTo subscribe to Security Advisories, log in to the Silicon Labs customer portal, then select Account Home. Click HOME to go to the portal home page and then click the Manage Notifications tile. Make sure that ‘Software/Security Advisory Notices & Product Change Notices (PCNs)’ is checked, and that you are subscribed at minimum for your platform and protocol. Click Save to save any changes.3.3 SupportDevelopment Kit customers are eligible for training and technical support. Contact Silicon Laboratories support at /support.Silicon Laboratories Inc.400 West Cesar Chavez Austin, TX 78701USAIoT Portfolio/IoTSW/HW/simplicityQuality /qualitySupport & Community/communityDisclaimerSilicon Labs intends to provide customers with the latest, accurate, and in-depth documentation of all peripherals and modules available for system and software imple-menters 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 to the product information, specifications, and descriptions herein, and does not give warranties as to the accuracy or completeness of the included information. Without prior notification, Silicon Labs may update product firmware during the manufacturing process for security or reliability reasons. Such changes will not alter the specifications or the performance of the product. Silicon Labs shall have no liability for the consequences of use of the infor -mation supplied in this document. This document does not imply or expressly grant any license to design or fabricate any integrated circuits. The products are not designed or authorized to be used within any FDA Class III devices, applications for which FDA premarket approval is required or Life Support Systems 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. Silicon Labs disclaims all express and implied warranties and shall not be responsible or liable for any injuries or damages related to use of a Silicon Labs product in such unauthorized applications. Note: This content may contain offensive terminology that is now obsolete. Silicon Labs is replacing these terms with inclusive language wherever possible. For more information, visit /about-us/inclusive-lexicon-projectTrademark InformationSilicon Laboratories Inc.®, Silicon Laboratories ®, Silicon Labs ®, SiLabs ® and the Silicon Labs logo ®, Bluegiga ®, Bluegiga Logo ®, EFM ®, EFM32®, EFR, Ember ®, Energy Micro, Energy Micro logo and combinations thereof, “the world’s most energy friendly microcontrollers”, Redpine Signals ®, WiSeConnect , n-Link, ThreadArch ®, EZLink ®, EZRadio ®, EZRadioPRO ®, Gecko ®, Gecko OS, Gecko OS Studio, Precision32®, Simplicity Studio ®, Telegesis, the Telegesis Logo ®, USBXpress ® , Zentri, the Zentri logo and Zentri DMS, 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. Wi-Fi is a registered trademark of the Wi-Fi Alliance. All other products or brand names mentioned herein are trademarks of their respective holders.。

条码与信息系统2021年第3期总第163期BAR CODE &INFORMATION SYSTEM促进零供协同发展推动供应链数字化——2021年中国ECR 联合工委会春季会议在京东总部召开本刊记者翟亚丽谢昊婧ECR 专栏2021年4月27日，中国ECR 联合工委会春季会议在北京亦庄京东集团总部召开。

来自宝洁、联合利华、雀巢、京东、美团、伊利、屈臣氏、SPAR 、尼尔森、集保、怡亚通、艾利丹尼森、邓韩贝、商务部国际贸易经济合作研究院、CCFA 、杉数科技、嘉实多、G7物联、嘉华汇诚、博枫物流、用友网络、敖维科技、齐炫科技、恒流管理、珠海晶通等公司和单位的50余位代表齐聚，就供应链数字化建设、品类管理、零供协同和技术赋能等快消品行业热点议题进行深入讨论。

中国物品编码中心应用推广部主任、中国ECR 委员会执行秘书长孔洪亮和京东供应链产品群产品规划与经营组高级总监贺岩出席会议并致辞。

孔洪亮在讲话中提到，中国ECR 委员会始终以为消费者创造价值为宗旨，致力于推动ECR 理念在我国的传播、促进零供合作、提高供应链效率、助推消费品行业健康可持续发展。

感谢各工委会会员和企业长期以来对ECR 工作的关心、支持和帮助。

本次会议在京东召开，得到了京东的大力支持，京东作为中国电商平台发展的一面旗帜，京东的发展速度让人感到非常振奋。

在全球抗击疫情的大环境下，京东也让全世界看到了砥砺奋进的中国信心。

贺岩总监表示，京东物流即将成为全球第五大物流服务商，在物流行业复杂和激烈的竞争场景下，京东多年来还能够保持高效率和很高的用户体验，源于一直以来京东对标准化、数字化和智能化的推进。

京东通过标准化的托盘或者载具，结合RFID 和GS1编码技术，把标准化、数字化和智能化进一步渗透到整个供应链，京东云箱就是京东物流标准化领域一个非常重要的尝试。

京东希望未来能够和更多先进的公司、先进的技术和先进的理念深入合作，携手推动全球供应链效率的提升。

中⾦⼿术机器⼈：医疗⾰命，⽆限未来摘要⼿术机器⼈，颠覆传统医疗与重构未来⼿术。

2015年，达芬奇腔镜⼿术机器⼈展⽰葡萄⽪缝合⼿术后，⼿术机器⼈以其更精准、更微创、更简便的优势开始被中国市场熟知，国内⾏业加速发展。

除发展最为成熟的腔镜⼿术机器⼈外，⼿术机器⼈还包括⾻科、经⽪穿刺、经⾃然腔道、泛⾎管等。

随着技术的逐步成熟，2010年后各⼿术领域陆续开始进⼊机器⼈时代。

我们认为传统医疗正被颠覆，未来⼿术即将重构。

未来⼿术机器⼈的⾰命，是使传统⼿术从⼀个定性的动作转变为定量的标准化数据，为⼿术开启数字化与智能化时代带来可能。

此外，作为直接作⽤于患者的治疗⽅式，我们预期平台化将进⼀步打开⾏业成长空间。

近年来我国⼿术机器⼈⾏业发展迅速，2020年国内市场规模为4.3亿美元，占全球⽐例为5.1%。

我们认为，随着上游供应链的国产化提升与下游医院端配置证的放开，⾏业发展有望进⼀步提速。

设备+耗材+服务，商业模式升级三步曲。

⼿术机器⼈收⼊分设备、耗材、服务三部分，伴随机器⼈的规模化与智能化进程，我们判断⼿术机器⼈将呈现出短期以设备为主、中期以耗材为主、远期以服务为主的商业模式演绎。

海外成熟腔镜与⾻科⼿术机器⼈的发展历史验证了我们对未来短期与中期的判断。

达芬奇腔镜⼿术机器⼈通过20+年4代机器⼈的进化，在提升技术壁垒的同时增强客户粘性。

2013年，在累计装机量达到⼀定规模后，耗材成为其⽣产企业Intuitive Surgical的主要收⼊来源，后续⼏年收⼊占⽐持续提升；全球器械巨头史赛克则通过收购Mako机器⼈来巩固其⾻科耗材的领导地位，在⾏业过去20年的发展中，耗材与机器⼈的协同收并购普遍存在。

我们判断，随着技术的成熟和数字化、智能化进程推进，服务业务除常规维护外将延伸出术前规划、术中指导、术后分析等⼤量软件增值业务，这些将在未来发挥越来越重要的作⽤。

2030年国内市场规模超700亿元，腔镜⼿术机器⼈最⼤。

我们测算到2030年中国⼿术机器⼈市场将超过700亿元，且随着⼿术机器⼈技术成熟，数字化与智能化的突破，市场空间仍有进⼀步突破的可能。