ISO/IEC 29341-18-3:2011 PDF

Information technology — UPnP Device Architecture — Part 18-3: Remote Access Device Control Protocol — Remote Access Server Device

Название (английский):

ISO/IEC 29341-18-3:2011

Information technology — UPnP Device Architecture — Part 18-3: Remote Access Device Control Protocol — Remote Access Server Device

Статус документа:: Действующий
Формат:: Электронный (PDF)
Количество страниц:: 6
Дата публикации:: 30 августа 2011 г.
Издание:: ISO/IEC IS 29341 edition 1 version 1
ICS:: 35.200

Тип поставки:

Full version90 €Read online 24h10 €Read online 72h15 €

Язык документа:

ruen

Срок поставки:1 раб. дн. (перевод)

Цена:90 €

Описание (английский):

ISO/IEC 29341-18-3:2011(E) includes the device definition which is compliant with the UPnP Device Architecture version 1.0. It defines a device type referred to herein as RAServer Device. The RAServer Device is a UPnP Device UPnP device that allows control points to configure Remote Access Servers. This Device provides control points with the following functionality: - Determine if the Remote Access Server is reachable from the public Internet; - Enable a Remote Access Server to be reachable from the public Internet; - Enumerate the Remote Access Transport mechanisms supported by the Remote Access Server; - Enumerate the Credentials Delivery mechanisms supported by the Remote Access Server; - Configure active Remote Access Transport profiles; - Configure filters for allowing which local Devices are visible in remote networks; - Configure filters for allowing which remote Devices are visible in the local network; - Maintains list of registered remote users, and authenticates when they log in depending on their pre-configured info appropriately.

Технические детали

Технический комитет: ISO/IEC JTC 1 - Information technology
SKU: ISO/IEC 29341-18-3:2011

Abstract

Overview

ISO/IEC 29341-18-3:2011 specifies the UPnP Device Architecture definition for a Remote Access Server Device (RAServer). Aligned with UPnP Device Architecture v1.0, this part of the UPnP Remote Access Device Control Protocol defines the device type (urn:schemas-upnp-org:device:RAServer:1) and the required services and behaviors that allow UPnP control points (management consoles) to configure and manage remote access to a home network from the public Internet.

Key topics and requirements

Device scope & compliance
- RAServer Device compliant with UPnP Device Architecture 1.0.
- Defines device model, XML device description, and test guidance.
Core services (REQUIRED)
- RATAConfig – configuration of Remote Access Transport Agent (RATA) and transport profiles.
- RADAConfig – configuration of RA Discovery Agent exposure and visibility filters.
- InboundConnectionConfig – controls and checks reachability from the public Internet.
- RADASync / RADA Listener & Relay – support for discovery synchronization and relaying (hosted by the RAServer).
Functional capabilities
- Determine and enable RAS reachability on the public Internet.
- Enumerate supported Remote Access Transport mechanisms and Credentials Delivery mechanisms.
- Configure active RATA profiles (RA network interfaces).
- Define filters that control which local devices are visible remotely and which remote devices are exposed locally.
- Maintain and authenticate a list of registered remote users based on pre-configured credentials.
Notation & rules
- RFC 2119 keywords (MUST/SHOULD/MAY) used to indicate requirement levels.
- Vendor-defined extensions allowed if they follow UPnP naming and XML rules.
Limitations
- Does not specify control-level or content-level access control for local devices exposed remotely.

Applications

Network equipment and home gateway manufacturers implementing UPnP-based remote access features.
Smart home device vendors who need to expose selected local devices to remote clients securely.
Software developers and integrators building management consoles or control points for remote device configuration.
Test and certification labs validating UPnP Remote Access Server implementations against the standard.

Related standards

UPnP Device Architecture (UPnP-arch-DeviceArchitecture-v1.0) - foundational architecture and XML/device description rules.
UPnP RA service documents referenced by the standard: RATAConfig, RADAConfig, RADASync, InboundConnectionConfig, and RA Architecture specification.
RFC 2119 - keywords for requirement levels.

This standard is essential for interoperable, UPnP-based remote access solutions-helping developers and manufacturers implement transport profiles, discovery, reachability, user registration, and device visibility controls in a consistent, testable way.

Overview

Key topics and requirements

Device scope & compliance
- RAServer Device compliant with UPnP Device Architecture 1.0.
- Defines device model, XML device description, and test guidance.
Core services (REQUIRED)
- RATAConfig – configuration of Remote Access Transport Agent (RATA) and transport profiles.
- RADAConfig – configuration of RA Discovery Agent exposure and visibility filters.
- InboundConnectionConfig – controls and checks reachability from the public Internet.
- RADASync / RADA Listener & Relay – support for discovery synchronization and relaying (hosted by the RAServer).
Functional capabilities
- Determine and enable RAS reachability on the public Internet.
- Enumerate supported Remote Access Transport mechanisms and Credentials Delivery mechanisms.
- Configure active RATA profiles (RA network interfaces).
- Define filters that control which local devices are visible remotely and which remote devices are exposed locally.
- Maintain and authenticate a list of registered remote users based on pre-configured credentials.
Notation & rules
- RFC 2119 keywords (MUST/SHOULD/MAY) used to indicate requirement levels.
- Vendor-defined extensions allowed if they follow UPnP naming and XML rules.
Limitations
- Does not specify control-level or content-level access control for local devices exposed remotely.

Applications

Network equipment and home gateway manufacturers implementing UPnP-based remote access features.
Smart home device vendors who need to expose selected local devices to remote clients securely.
Software developers and integrators building management consoles or control points for remote device configuration.
Test and certification labs validating UPnP Remote Access Server implementations against the standard.

Related standards

UPnP Device Architecture (UPnP-arch-DeviceArchitecture-v1.0) - foundational architecture and XML/device description rules.
UPnP RA service documents referenced by the standard: RATAConfig, RADAConfig, RADASync, InboundConnectionConfig, and RA Architecture specification.
RFC 2119 - keywords for requirement levels.

ISO/IEC 29341-18-3:2011 PDF

Технические детали

Abstract

Overview

Key topics and requirements

Applications

Related standards

Похожие стандарты

Abstract

Overview

Key topics and requirements

Applications

Related standards

Похожие стандарты

Water quality — Biological classification of rivers — Part 1: Guidance on the interpretation of biological qu…

Standard Practice for Use of a Radiochromic Liquid Dosimetry System (Withdrawn 2020)

Standard Practice for Dosimetry in Gamma Irradiation Facilities for Food Processing (Withdrawn 2013)

Standard Practice for Dosimetry in Electron Beam and X-Ray (Bremsstrahlung) Irradiation Facilities for Food P…

Standard Practice for Dosimetry in Radiation Processing

Standard Terminology for Additive Manufacturing—Coordinate Systems and Test Methodologies

Additive Manufacturing — Round Robin Testing — General Guidelines

Standard Guide for Additive Manufacturing – General Principles – Requirements for Purchased AM Parts