Skip to main content
  • 产品
  • Evaluate our Software
  • 下载
  • Free Utilities
  • 购买
  • 支持
  • 关于我们
  • Search
    • Contact Us
    • Forum
    • Knowledge Base
    • Newsletter
    • RSS
  •   工作机会
  •   视频
  •   永续性
  • emNet
  • UPnP
  • Technology
  • Add-Ons
  • Tools

UPnP

The emNet UPnP implementation is an optional extension which can be integrated into your TCP/IP application seamlessly. It combines the possibility to implemented UPnP services in a most flexible way - namely by allowing to specify content to be sent upon UPnP requests completely generated by the application - with a small memory footprint.

Contact us
Downloads
Documentation
SEGGER emNet
  1. 1.Overview
    1. 1.1.Key features
  2. 2.Requirements
  3. 3.Relevant parts
  4. 4.Resource Usage

Overview

UPnP is designed to provide services throughout a network without interaction of the user. It is designed to use standardised protocols such as IP, TCP, UDP, Multicast, HTTP and XML for communication and to distribute services provided by a device. UPnP can be used to advertise services provided by a device across the network such as where to find the web interface for the device advertising. Newer operating systems support UPnP from scratch and will show UPnP devices available across a network and may provide easy access to a device by simply selecting the discovered UPnP device.

A typical usage would be to advertise media accessible on a media storage on the network and to open a file browser window to the resource upon opening the UPnP entry discovered.

Key features

  • Low memory footprint
  • •Advertising your services on the network
  • Easy to implement

Requirements

TCP/IP Stack

The emNet UPnP implementation requires the emNet TCP/IP stack and is designed to be used with the emNet Web server Add-on.

Relevant parts

The UPnP module implements the relevant parts of the UPnP documentation released by the UPnP Forum.

Document Download
UPnP Device Architecture 1.0Direct download: http://upnp.org/specs/arch/UPnP- arch-DeviceArchitecture-v1.0.pdf

Resource Usage

The ROM usage depends on the compiler options, the compiler version and the used CPU. The memory requirements of the UPnP modules presented in the tables below have been measured on an ARM7 and a Cortex-M3 system. Details about the further configuration can be found in the sections of the specific example.

The pure size of the UPnP add-on has been measured as the size of the services provided may vary.

ROM Usage on an ARM7 System

The following resource usage has been measured on an ARM7 system using IAR Embedded Workbench V6.30.6, Thumb mode, no interwork, size optimization.

Add-onROM
emNet UPnPApproximately 2.2 KByte

ROM Usage on a Cortex-M3 System

The following resource usage has been measured on a Cortex-M3 system using IAR Embedded Workbench V6.30.6, size optimization.

Add-onROM
emNet UPnPApproximately 2.0 KByte

RAM Usage

Add-onRAM
emNet UPnPApproximately 170 Byte

全球总部

德国: SEGGER Microcontroller GmbH

地址: Ecolab-Allee 5
40789 Monheim am Rhein, Germany
电邮: info@segger.com
电话: +49-2173-99312-0
传真: +49-2173-99312-28

网点分布

中国:哲戈微系统科技(上海)有限公司

地址: 中国上海市闵行区秀涟路133号
大虹桥国际A 栋218室
邮编201199
电邮: china@segger.com
电话: +86-133-619-907-60

通过ISO 9001认证

ISO 9001

30多年的嵌入式行业经验

First-class embedded software tools since 1992
  • 版本说明
  • 免责声明
  • 隐私策略
  • 沪ICP备2022005181号
  • 沪公网安备 31011202014525号
© 2025 SEGGER - 版权所有.

您即将离开 segger.cn 而访问境外网站,是否继续?