版权说明:本文档由用户提供并上传,收益归属内容提供方,若内容存在侵权,请进行举报或认领
文档简介
1、WANConnectionDevice:2 Device Template Version 1.01For UPnP Versions1.0 and 1.1Status: Standardized DCP (SDCP), Version 1.00Date: September 10, 2010This Standardized DCP has been adopted as a Standardized DCP by the Steering Committee of the UPnP Forum, pursuant to Section 2.1(c)(ii) of the UPnP Foru
2、m Membership Agreement. UPnP Forum Members have rights and licenses defined by Section 3 of the UPnP Forum Membership Agreement to use and reproduce the Standardized DCP in UPnP Compliant Devices. All such use is subject to all of the provisions of the UPnP Forum Membership Agreement.THE UPNP FORUM
3、TAKES NO POSITION AS TO WHETHER ANY INTELLECTUAL PROPERTY RIGHTS EXIST IN THE STANDARDIZED DCPS. THE STANDARDIZED DCPS ARE PROVIDED "AS IS" AND "WITH ALL FAULTS". THE UPNP FORUM MAKES NO WARRANTIES, EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE WITH RESPECT TO THE STANDARDIZED DCPS,
4、INCLUDING BUT NOT LIMITED TO ALL IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT AND FITNESS FOR A PARTICULAR PURPOSE, OF REASONABLE CARE OR WORKMANLIKE EFFORT, OR RESULTS OR OF LACK OF NEGLIGENCE.? 2010 UPnP Forum. All Rights Reserved.Authors*CompanyFr é dé ric Pennerath, Gert Mar
5、ynissenAlcatelFabrice FontaineOrange Labs* Note: The UPnP Forum in no way guarantees the accuracy or completeness of this author list and in no wayimplies any rights for or support from those members listed. This list is not the specifications conkept on the UPnP Forum s website.UPnP WANConnectionDe
6、vice:2, version 1.00. Device Template Version 1.012Contents1.OVERVIEW AND SCOPE .31.1.REFERENCES .31.1.1.Normative References .32.DEVICE DEFINITIONS .62.1.DEVICETYPE .62.2.DMODEL .6EVICE2.2.1.Description of Device Requirements .72.2.2.Relationships Between Services.72.3.THEORY OF OPERATION .83.XML D
7、EVICE DESCRIPTION .114.TEST .13List of TablesTable 1: Device Requirements6Table 2: Valid Combinations of LinkType and PossibleConnectionTypes10? 2010 UPnP Forum. All rights reserved.UPnP WANConnectionDevice:2, version 1.00. Device Template Version 1.0131. Overview and ScopeThis device template is co
8、mpliant with the Universal Plug and Play Architecture, Version1.0 and 1.1.WANConnectionDevice is a REQUIRED virtual device defined under:urn: schemas-upnp-org :device:WANDevice:2An instance of WANDevice is specified under the root device:urn: schemas-upnp-org :device:InternetGatewayDevice:2WANConnec
9、tionDevice is a container for a link and connection services specific to a link on a WAN interface. Most types of WAN interfaces can be modeled by a single instance ofWANConnectionDevice. However, in the case of DSL, each VC can have unique link attributes and can be provisioned for connection servi
10、ces that are different from other VCs. In this case, each VC will be modeled by an instance ofWANConnectionDevice. Also, in the case of a POTS modem basedInternetGatewayDevice (IGD), each separate ISP instance can be modeled as an instance of WANConnectionDevice.The Theory of Operation section descr
11、ibes the services contained inWANConnectionDevice in more detail.Figure 1: WANConnectionDevice Devices and Services Hierarchy1.1. ReferencesReferencesThis section lists the normative references used in this specification and includes the tag inside square brackets that is used for each such referenc
12、e:IGD2 UPnPInternetGatewayDevice:2, version 1.00, UPnP Forum, December 10, 2010.Available at /specs/gw/UPnP-gw-InternetGatewayDevice-v2-Device.pdf.? 2010 UPnP Forum. All rights reserved.UPnP WANConnectionDevice:2, version 1.00. Device Template Version 1.014WANDevice UPnPWANDevice:2, ve
13、rsion 1.0, UPnP Forum, September 10, 2010.Available at: /specs/gw/UPnP-gw-WANDevice-v2-Device.pdf.WANIPConnection UPnPWANIPConnection:2, version 1.00, UPnP Forum, September 10, 2010.Available at: /specs/gw/UPnP-gw-WANIPConnection-v2-Service.pdf.WANIPv6FirewallControl UPnP
14、WANIPv6FirewallControl:1, version 1.0, UPnP Forum, December 10, 2010.Available at: /specs/gw/UPnP-gw-WANIPv6FirewallControl-v1-Service.pdf .LANDevice UPnPLANDevice:1, version 1.0, UPnP Forum, November 19, 2001.Available at: /specs/gw/UPnP-gw-LANDevice-v1-Device.pdf.LANHos
15、tConfigManagement UPnPLANHostConfigManagement:1, version 1.0, UPnP Forum, November 19, 2001.Available at: /specs/gw/UPnP-gw-LANHostConfigManagement-v1-Service.pdf.L3Forwarding UPnPLayer3Forwarding:1, version 1.0, UPnP Forum, November 19, 2001.Available at: /specs/gw/UPnP-
16、gw-Layer3Forwarding-v1-Service.pdf.WANCableLinkConfig UPnPWANCableLinkConfig:1, version 1.0, UPnP Forum, November 19, 2001.Available at: /specs/gw/UPnP-gw-WANCableLinkConfig-v1-Service.pdf .WANCommonInterfaceConfig UPnPWANCommonInterfaceConfig:1, version 1.0, UPnP Forum, November 19, 2
17、001.Available at: /specs/gw/UPnP-gw-WANCommonInterfaceConfig-v1-Service.pdf.WANDSLLinkConfig UPnPWANDSLLinkConfig:1, version 1.0, UPnP Forum, November 19, 2001.Available at: /specs/gw/UPnP-gw-WANCableLinkConfig-v1-Service.pdf.WANEthernetLinkConfig UPnPWANEthernetLinkConfi
18、g:1, version 1.0, UPnP Forum, November 19, 2001. Available at: /specs/gw/UPnP-gw-WANEthernetLinkConfig-v1-Service.pdfWANPOTSLinkConfig UPnPWANPOTSLinkConfig:1, version 1.0, UPnP Forum, November 19, 2001.Available at: /specs/gw/UPnP-gw-WANPOTSLinkConfig-v1-Service.pdfWANPP
19、PConnection UPnPWANPPPConection:1, version 1.0, UPnP Forum, November 19, 2001.Available at: /specs/gw/UPnP-gw-WANPPPConnection-v1-Service.pdfDEVICE UPnP Device Architecture, version 1.0, UPnP Forum, June 8, 2000. Available at:ISO 8601 Data elements and interchange formats Information i
20、nterchange - Representation of dates and timesInternational Standards Organization, December 21, 2000.Available at: ISO 8601:2000.RFC 2119 IETF RFC 2119, Key words for use in RFCs to Indicate Requirement Levels, S. Bradner, March 1997.RFC 3986 IETF RFC 3986, Uniform Resource Identifier (URI): Generi
21、c Syntax, T. Berners-Lee, R. Fielding, L.Masinter, January 2005.RFC 3339 IETF RFC 3339, Date and Time on the Internet: Timestamps, G. Klyne, Clearswift Corporation, C.Newman, Sun Microsystems, July 2002.XML Extensible Markup Language (XML) 1.0 (Third Edition), Fran?ois Yergeau, Tim Bray, Jean Paoli,
22、 C. M.Sperberg-McQueen, Eve Maler, eds., W3C Recommendation, February 4, 2004.? 2010 UPnP Forum. All rights reserved.UPnP WANConnectionDevice:2, version 1.00. Device Template Version 1.015XML SCHEMA-2 XML Schema Part 2: Data Types, Second Edition, Paul V. Biron, Ashok Malhotra, W3C Recommendation, 2
23、8 October 2004.? 2010 UPnP Forum. All rights reserved.UPnP WANConnectionDevice:2, version 1.00. Device Template Version 1.0162. DeviceDefinitions2.1. DeviceTypeThe following device type identifies a device that is compliant with this template:urn:schemas-upnp-org:device :WANConnectionDevice:22.2. De
24、viceModelProducts that expose devices of the typeurn: schemas-upnp-org :device:WANConnectionDevice:2 MUST implement minimum version numbers of all required embedded devices and services specified in the table below.Table 1: Device RequirementsDeviceTypeRoot Req. orServiceTypeReq. or Opt. 1Service ID
25、 2Opt. 1WANPOTSLinkConfig:1O for POTSWANPOTSLinkC1modemsWANDSLLinkConfig:1O for DSLWANDSLLinkC1modemsWANCableLinkConfig:1O for CableWANCableLinkC1modemsWANEthernetLinkConfig:1O for EthernetWANEthLinkC1attachedmodemsWANPPPConnection:1 Rfor modemsMultiple instancesthat supportpossible within aPPP base
26、dWANConnectionDeviconnectionsce. ServiceIDs formultiple instanceswill beWANPPPConn1,WANPPPConn2,WANPPPConn3 andso on.WANIPConnection:2 Rfor modemsOnly 1 instance perthat supportWANConnectionDeviIPv4 basedce is envisioned atconnectionsthis time, althoughthe design couldsupport multipleinstances in fu
27、ture.ServiceIDs formultiple instanceswill beWANIPConn1,WANIPConn2,WANIPConn3 and soon.WANIPv6FirewallControl:1O for IPv6Only 1 instance perenabled IGDsWANIPv6FirewallCo? 2010 UPnP Forum. All rights reserved.UPnP WANConnectionDevice:2, version 1.00. Device Template Version 1.017ntrol is envisioned at
28、this time, althoughthe design couldsupport multipleinstances in future.ServiceIDs formultiple instanceswill beWANIPv6Firewall1,WANIPv6Firewall2,WANIPv6Firewall3and so on.Non-standard services embeddedX TBDby an UPnP vendor go here.Non-standardTBD XTBDTBDTBDdevicesembedded byan UPnPvendor gohere.1 R
29、= Required, O = Optional, X = Non-standard.2 Prefixed by urn:upnp-org :serviceId : .Note: the word modem in the table above refers to the WAN interface (orWANDevice).Each WANConnectionDevice models a link on a physical WAN interface. A WANDevice may contain one or more instances of WANConnectionDevi
30、cecorresponding to one or more active links on a modem. WANCommonInterfaceConfig is a service in WANDevice that models attributes and actions that are common across all links and all connection instances on a link.The DefaultConnectionService state variable in theLayer3Forwarding service refers to t
31、he UDN of a WANConnectionDeviceinstance this is an external dependency. There may also be dependencies between a specific instance of WAN* LinkConfig (where * can be POTS, DSL, Cable or Ethernet)and WAN* Connection service (where * can be PPP or IP) or WANIPv6FirewallControl service in a WANConnecti
32、onDevice.? 2010 UPnP Forum. All rights reserved.UPnP WANConnectionDevice:2, version 1.00. Device Template Version 1.0182.3.Theory of OperationConnections to the Internet are initiated either from the WAN interface of an IGD or are relayed or bridged throughthe WAN interface. DSL can be provisioned t
33、o support multiple Virtual Circuits (VCs) simultaneously. Each VCcan in turn be provisioned to support one or more PPP connections or an IP connection. To handle these scenarios,each WANDevice includes one or more instances ofWANConnectionDevice. A WANConnectionDevice encapsulatesa logical or physic
34、al link on a WAN interface over which connections are modeled. Furthermore, connections on aWAN interface can be of type PPP or IP. These are modeled by correspondingWANPPP/IPConnection serviceinstances for IPv4 connections orWANIPv6FirewallControl service instances for IPv6 connections. Propertiess
35、pecific to a link are modeled in a WANPOTS/DSL/Cable/EthernetLinkConfig service.The definition of the WAN*LinkConfig 1, WAN*Connection2 and WANIPv6FirewallControl services are based on the following broad objectives:? To allow for the distinction between Internet access scenarios that are typically
36、independent of the modem types used and configuration scenarios that are specific to modem types. This enables easier modeling of various connectivity scenarios independent of the underlying modem type or its configuration.? To support most of the commonly deployed connection types (either originati
37、ng at the WAN interface of the gateway or relayed/bridged through the gateway).? To support manual (may need Out-Of-Band security and access control mechanisms) or automatic configuration of parameters on a modem.? To ensure extensibility for new connection types in future.Configuration and connecti
38、vity scenarios are independent of each other. However, there is an implied relationship in that control points will first need to complete configuration actions (unless this process is completed automatically) before initiating any connectivity related actions. It is also important to note that auto
39、 and manual configuration of a modem are mutually exclusive operations in most cases. Furthermore, in most deployment scenarios, auto configuration is given higher priority over manual configuration.The process of configuration and subsequent management of WAN connections is via 3 variables:?LinkTyp
40、e: This variable, if defined in a WAN*LinkConfig service, indicates the protocol configured on a3specific link. This variable can be set manually, or through an automatic mechanism (for example, AutoConfig specified by Broadband Forum).? PossibleConnectionTypes: specifies only those connection types
41、 that are permissible in a particular implementation for a specific modem link configuration (as indicated by the value of LinkType). This variable is defined in WAN*Connection service.? ConnectionType: indicates a specific connection type selected from those permissible on a link, as indicated by P
42、ossibleConnectionTypes. This variable is defined in WAN*Connection service.Figure 2 illustrates the process of configuration and connection management, using a DSL modem as an example. Note that the configuring agent and subsequent user(s) of connections need not be the same network entities. The 4
43、conceptual steps are described below.? Step 1: A configuring entity sets up the LinkType to an appropriate value.1 Refer to companion DCP drafts for specificWAN*LinkConfig descriptions and description of variables such as LinkType.2 Refer to companion DCP drafts for specificWAN*Connection service de
44、scriptions and variables such as PossibleConnectionTypesand ConnectionType.3 Refer to the Broadband Forum website http:/www(.) for more details.? 2010 UPnP Forum. All rights reserved.UPnP WANConnectionDevice:2, version 1.00. Device Template Version 1.019? Step 2: The value of Link
45、Type is combined with the capabilities of the modem to come up with a list of possible connection types appropriate for the particular configuration.? Step 3: The variable PossibleConnectionTypesis updated with the list derived from step above.? Step 4: A control point may subsequently initiate a co
46、nnection by settingConnectionTypeto a value from the allowable list specified in PossibleConnectionTypes. In this step, a control point evaluates its own capabilitiesvis- à -vis the capabilities exposedPossibleConnectionTypesinand selects one that is appropriate for its use. In some deployment
47、scenarios, the value ofConnectionType may be strictly read-only from a control point perspective.Manual ConfigurationAutoConfigurationvia UPnP Control PointMechanismORLink ConfigurationStep1WANDSLLinkConfigServiceLinkTypeStep3WANPPPConnectionVP, VC ,CombineUpdateServiceReadPossibleConnectionTypesSte
48、p2Modem capabilitiesand restrictionsStep4Control Pointsets up connectionConnectionTypeFigure 2: Configuration and Connection ManagementThe following table lists valid combinations of LinkType and PossibleConnectionTypesas well as connection service type for different types of WAN interfaces.? 2010 UPnP Forum. All rights reserved.UPnP WANConnectionDevice:2, version 1.00. Device Template Version 1.0110Table 2: Valid Combinations ofLinkType andPossibleConnectionTypesM
温馨提示
- 1. 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。图纸软件为CAD,CAXA,PROE,UG,SolidWorks等.压缩文件请下载最新的WinRAR软件解压。
- 2. 本站的文档不包含任何第三方提供的附件图纸等,如果需要附件,请联系上传者。文件的所有权益归上传用户所有。
- 3. 本站RAR压缩包中若带图纸,网页内容里面会有图纸预览,若没有图纸预览就没有图纸。
- 4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
- 5. 人人文库网仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对用户上传分享的文档内容本身不做任何修改或编辑,并不能对任何下载内容负责。
- 6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
- 7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。
最新文档
- 二零二五年度外卖配送服务承包合同(含食品安全)
- 2025年度个人独院买卖合同(含租赁权)协议书
- 课题申报参考:民族基层地区检察听证实质化改革路径构建研究
- 二零二五年度智能停车场租赁与维护一体化合同
- 2025年个人担保居间合同标准实施范本2篇
- 二零二五年度女方违反离婚协议财产分割及房产过户合同4篇
- 2025年度个人户外装备分期购买合同
- 湖北省黄冈市重点中学高三上学期期末考试语文试题(含答案)
- 2025版美容院美容师团队建设聘用标准合同4篇
- 二零二五年度牧业产业扶贫项目承包合同范本3篇
- 2024年高考语文思辨类作文预测+考前模拟题+高分范文
- 桥本甲状腺炎-90天治疗方案
- 《量化交易之门》连载27:风险的角度谈收益MAR和夏普比率
- (2024年)安全注射培训课件
- 2024版《建设工程开工、停工、复工安全管理台账表格(流程图、申请表、报审表、考核表、通知单等)》模版
- 部编版《道德与法治》六年级下册教材分析万永霞
- 粘液腺肺癌病理报告
- 酒店人防管理制度
- 油田酸化工艺技术
- 上海高考英语词汇手册列表
- 移动商务内容运营(吴洪贵)任务五 其他内容类型的生产
评论
0/150
提交评论