* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Download 5 Requirements - ISO/IEC JTC 1/SC 25/WG 1 Home Page
Survey
Document related concepts
Deep packet inspection wikipedia , lookup
Bus (computing) wikipedia , lookup
Computer network wikipedia , lookup
Distributed firewall wikipedia , lookup
Network tap wikipedia , lookup
Cracking of wireless networks wikipedia , lookup
Zero-configuration networking wikipedia , lookup
Internet protocol suite wikipedia , lookup
List of wireless community networks by region wikipedia , lookup
Airborne Networking wikipedia , lookup
Recursive InterNetwork Architecture (RINA) wikipedia , lookup
Transcript
ISO/IEC JTC 1/SC 25/WG 1 N 1100a Date: 2004-06-01 Replaces ISO/IEC JTC 1/SC 25/WG 1 N xxxx ISO/IEC JTC 1/SC 25 INTERCONNECTION OF INFORMATION TECHNOLOGY EQUIPMENT Secretariat: Germany (DIN) DOC TYPE: CD TITLE: ISO/IEC CD 15045-2 Information technology — Interconnection of information technology equipment — Home Electronic System — (HES) Gateway — Part 2: Modular Interface and Protocol SOURCE: SC 25/WG 1 PROJECT: 25.01.03.02-02 STATUS: Working Draft ACTION ID: ACT DUE DATE: YYYY-MM-DD REQUESTED ACTION: National body members of SC 25/WG 1 are asked to review and comment on this CD at the Chitose meeting. MEDIUM: Defined No. of Pages: 21 (excluding cover) cover) DISTRIBUTION: ISO/IEC JTC 1 SC 25/WG 1 Size in KB: yyy (including Secretary - ISO/IEC JTC 1 / SC 25 - Dr.-Ing. Walter P. von Pattay Member of ZVEI FV 7 & FV 8, Gotthelfstr. 34, D -81677 München, Germany Tel.: +49 89-923 967 57, Tfx.: +49 89-923 967 59 EM: [email protected] Ftp address: "ftp.iec.ch", login: "sc25mem", password: see SC 25 N 449 Home page: ”http://www.iec.ch/sc25” INTERNATIONAL STANDARD (DRAFT) Information technology – Home electronic system (HES) – gateway Part 2: Modular interface and protocol ISO/IEC 15045-2 ISO/IEC FDIS 15045-2 IEC:2004 ISO/IEC JTC1 SC25/WG 1 N 1100 –2– 15045-2 ISO/IEC:2004 CONTENTS Page 1 Scope ............................................................................................................................... 4 2 Purpose ............................................................................................................................ 5 2.1 2.2 3 Statement of purpose .............................................................................................. 5 Design philosophy ................................................................................................... 5 2.2.1 Distributed gateway system ......................................................................... 6 2.3 Goals and non-goals ............................................................................................... 6 2.4 Conformity ............................................................................................................... 6 References ....................................................................................................................... 7 4 Terminology ..................................................................................................................... 7 5 4.1 Definitions ............................................................................................................... 7 4.2 Abbreviations .......................................................................................................... 8 Requirements ................................................................................................................... 9 6 5.1 Modularity requirements .......................................................................................... 9 5.2 Stakeholder requirements ........................................................................................ 9 System model ................................................................................................................... 9 7 6.1 Abstract HES system ............................................................................................... 9 6.2 Generic Interworking Function (GIWF) ................................................................... 10 6.3 Conformance paradigm—roles .............................................................................. 10 Architecture .................................................................................................................... 11 7.1 7.2 7.3 7.4 8 WAN interface module ........................................................................................... 12 HAN interface module ........................................................................................... 13 Service module ..................................................................................................... 13 Data flows ............................................................................................................. 14 7.4.1 Control plane ............................................................................................. 14 7.4.2 Content (data) plane .................................................................................. 14 7.5 Reference models ................................................................................................. 15 Internal Processes .......................................................................................................... 18 8.1 8.2 8.3 8.4 8.5 9 Protocol stacks ...................................................................................................... 18 Internal Protocol (RGIP) ........................................................................................ 19 Internal bus ........................................................................................................... 19 Service requirements ............................................................................................ 21 Network management ............................................................................................ 21 8.5.1 Resource discovery/allocation ................................................................... 22 8.5.2 Addressing/allocation ................................................................................ 22 8.5.3 Binding ...................................................................................................... 22 8.5.4 Routing ...................................................................................................... 22 8.5.5 Error control .............................................................................................. 22 8.5.6 Safety ........................................................................................................ 22 8.5.7 Privacy (aliasing/identification) .................................................................. 22 8.5.8 Security (firewall/authentication/process protection ) .................................. 22 Conformance .................................................................................................................. 22 ISO/IEC JTC 1/SC 493718434 ISO/IEC FDIS 15045-2 IEC:2004 ISO/IEC JTC1 SC25/WG 1 N 1100 9.1 9.2 –3– 15045-2 ISO/IEC:2004 Basic functions and requirements .......................................................................... 22 Compliance of qualifying products and networks ................................................... 22 ISO/IEC JTC 1/SC 493718434 1 FORWARD 2 3 4 5 6 7 8 ISO (the International Organisation for Standardisation) and IEC (the International Electrotechnical Commission) form the specialised system for world -wide standardisation. National bodies that are members of ISO or IEC p articipate in the development of International Standards through technical committees established by the respective organisation to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest . Other international organisations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. 9 10 11 12 In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75% of the national bodies casting a vote. 13 14 15 This part of ISO/IEC 15045 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 25, Interconnection of Information Technology Equipment. 16 17 ISO/IEC 15045 consists of the following parts, under the general title: Information technology — Home electronic system (HES) Gateway. 18 Part 1: A Residential gateway model for HES 19 Part 2: Modular interface and protocol 20 Part 3: Safety 21 Part 4: Privacy 22 Part 5: Security 23 ISO/IEC FDIS 15045-2 IEC:2004 ISO/IEC JTC1 SC25/WG 1 N 1100 –2– 15045-2 ISO/IEC:2004 24 INTRODUCTION 25 26 27 28 29 30 The rapid, widespread development and deployment of numerous standards, techn ologies, services, and products for communication within or to the home has created problems of incompatibility, non-interoperability, complexity, and expense for consumers, service providers, and manufacturers. This situation necessitates a standard for enabling and ensuring co-existence, compatibility, or interoperability between such network standards, specifications, and products from multiple manufacturers or providers. 31 32 33 34 35 36 37 38 For example, it is desirable and beneficial that networks or products for home lig hting control be able to share sensor or actuator information with other networks or products for home energy management, home security, or audio-visual distribution. Likewise, it would be efficient and convenient for broadband access networks, regardless of technology employed (e.g., DSL, cable, satellite, wireless, fibre-optic, etc.), to share delivery of common voice, video and data signals with a variety of home appliances ( e.g., TVs, entertainment products, phones, computers, thermostats, medical equipment, etc.), regardless of manufacturer or provider. 39 40 41 42 43 44 45 46 47 48 49 This document is part of a series of standards and technical reports for the Home Electronic System (HES) that deal with the topic of control and communication networks in homes and other small buildings. Part 1 of this standard, ISO/IEC 15045-1, A Residential Gateway Model for HES, published in 2004, defines a basic model of the residential gateway, including functional requirements. This part 2 defines a common platform for achieving interconnection and interoperability of home system products and applications from any manufacturer or provider in a manner that is safe, reliable, predictable and consistent. It accomplishes such interoperability by defining a standard modular architecture, a common signalling bus for interconnecting the modules, and a common intermediate language and protocol for interoperability of applications based on a Common Interoperability System (CIS). I t relies on the CIS as defined in the standard, ISO/IEC 18012, Guidelines for Product Interoperability . 50 ISO/IEC JTC 1/SC 493718434 ISO/IEC FDIS 15045-2 IEC:2004 ISO/IEC JTC1 SC25/WG 1 N 1100 51 52 53 54 55 56 57 15045-2 ISO/IEC:2004 –3– It is possible that a user will purchase and install two (or more) dissimilar networks, known as a home area networks (HANs), within the same premises. However, the user may expect these networks to behave as if they were logically the same network, Therefore, when linked by some physical means, each network must include an interface that conforms to this standard, as shown in Figure 1. Likewise, service providers outside the house using a variety of wide area networks (WANs) will wish to exchange information with these HANs. These WANs must also provide an interface that conforms to this standard. 58 59 O1 O2 O3 O4 60 HGI WGI 61 Wide Area Network X 62 63 Home Area Network A HomeNetwor kA Physical HESgateway O1 WGI Wide Area Network Y 64 HGI O2 O3 Logical link O4 Home Area Network B 65 WGI 66 = WAN Gateway Interface On 67 HGI = HAN Gateway Interface = Object on network 68 69 Figure 1 - Interoperating Networks 70 This document comprises the following sections: 71 72 Overview sections that define the scope and purpose of the standard, key terminology, and normative and informative references. 73 74 75 A requirements section that defines the normative functional requirements for the gateway system and associated modules, including modular interface and stakeholder requirements. 76 77 A system model section that defines the abstract HES system, the generic interworking function and the conformance paradigm. 78 79 80 An architecture section that defines wide area network (WAN) modules, home area network (HAN) modules, service modules, data flows (for both content (data) and control planes), and illustrative reference models. 81 82 83 84 An internal process section that defines protocol stacks, the residential gateway internal protocol (RGIP), the internal bus, service requirements, and network management requirements. Also, specific requirements are included to address issues of safety, security, and privacy. 85 86 A conformance section to which all interoperating networks, modules, and intermediary equipment on the Home Electronic System shall comply. 87 ISO/IEC JTC 1/SC 493718434 ISO/IEC FDIS 15045-2 IEC:2004 ISO/IEC JTC1 SC25/WG 1 N 1100 15045-2 ISO/IEC:2004 Information technology — Interconnection of information technology equipment — Home Electronic System (HES) — Gateway — Part 2: Protocol and Modular Interface 88 89 90 91 –4– 1 Scope 92 93 94 95 96 97 98 99 100 101 ISO/IEC 15045-1 (part 1) specifies the functional requirements and basic architecture for the residential gateway. This part, ISO/IEC 15045-2 (part 2), specifies a residential gateway modular structure and an internal protocol and language that may be used to implement a conforming gateway system for HES. This part specifies the modular interface and internally connecting bus with sufficient detail to create conforming modules that will interoperate in a conforming system. It specifies an interoperability language that resides above layer seven of the ISO Reference Model with sufficient detail needed to design interoperable Home Electronic System network interface and service modules. Lower layers of the internal protocol are also specified. Lower layers of specific WAN or HAN protocols are not specified, but are left entirely to the product manufacturer. 102 ISO/IEC 15045-2 is applicable to: 103 Standalone local/home area networks (HANs), connected devices, and applications. 104 Mixed local/home area networks (HANs), connected devices, and applications. 105 106 Wide area networks (WANs) (also known as access networks) and applications connected to home area networks (HANs), connected devices, and applications. 107 108 109 110 111 112 113 114 115 ISO/IEC 15045-2 specifies interoperability requirements and methods for system set -up, operation and management applied to devices connected to a single home network system or to different home network systems. Although a single uniform home network system would simplify such operations, this standard recognises that multiple dissimilar network systems may co-exist in the same premises. This standard specifies requirements to ensure that devices from multiple manufacturers and /or multiple network systems will work together as a total Home Electronic System (HES) to provide service to a specific application. Also, this standard specifies requirements that assure that a specific device could provide ser vice for multiple applications. 116 ISO/IEC 15045-2 specifies interoperability requirements with respect to: 117 Transport and interpretation/translation of control (control plane) information 118 Transport of content (data plane) information 119 Applications 120 121 Set-up of devices/elements within home area and wide are networks – static and/or dynamic binding between objects. 122 Ongoing basic network management functions 123 Security (i.e., firewall) 124 Safety 125 Privacy 126 127 128 129 This document does not specify how two home network systems share a common resource or how to ensure that two home network systems used within the same premises do not interfere with each other. However, this document requires that two home network systems may share a common resource, and that they shall not interfere with one another. ISO/IEC JTC 1/SC 493718434 ISO/IEC FDIS 15045-2 IEC:2004 ISO/IEC JTC1 SC25/WG 1 N 1100 –5– 15045-2 ISO/IEC:2004 130 2 Purpose 131 2.1 132 133 134 135 136 137 This standard provides an open, modular, and expandable framework for the delivery of broadband services to the consumer that can accommodate diverse networks on both the HAN and WAN side. It can also provide a basic firewall function that will protect the autonomy, safety, privacy, and security of the consumer, yet enable trusted relationships with preferred service providers. A basic block diagram of the HES -gateway system showing the primary functions is shown in Figure 2. Statement of purpose 138 139 HESgateway WANs HANs 140 141 WAN 142 WAN interfaces 143 HAN translator HAN Firewall interfaces 144 145 Figure 2—HES-gateway System Functional Block Diagram 146 147 148 In addition to providing access to WAN based services, this standard can also enable interoperability or interworking of HAN-based appliances, products and services. The common element is that of home services, such as: 149 Entertainment/video 150 Data/Internet access 151 Telephony 152 Energy Management 153 Environmental control (heating and cooling) 154 Security Monitoring 155 Appliance telemetry 156 Lighting control 157 2.2 158 159 160 161 162 163 164 165 Conventional gateway or set-top box designs generally take a “one-size-fits-all” approach tailored to some defined set of services on both the HAN and WAN side. In the quest for low cost and economies of scale in manufacturing, modularity and expandability are sacrificed, along with flexibility that service providers frequently need. Often, the result is a "big box" that tries to accommodate many functions and services, yet frequently fails to provide t he key features that are most needed in any particular situation. These big boxes have been characterised as “set-top boxes on steroids,” and are frequently designed around a powerful central processor and operating system. 166 167 This standard is based on a model that accommodates the conventional gateway (one WAN and one HAN) while defining the Distributed Gateway System. The Distributed Gateway Design philosophy ISO/IEC JTC 1/SC 493718434 ISO/IEC FDIS 15045-2 IEC:2004 ISO/IEC JTC1 SC25/WG 1 N 1100 –6– 15045-2 ISO/IEC:2004 168 169 170 171 172 System is a modular approach that supports multiple WANs and HANs. Nevertheless, the Distributed Gateway System modules might be combined for economy of im plementation. Thus, the Distributed Gateway System model is analogous to the OSI Reference Model for Communications (ISO 7498) in that a specific implementation is not required to include every element (layer) of the OSI Reference Model. 173 2.2.1 174 175 176 177 178 179 180 The Distributed Gateway System (DGS) seeks to design around the minimum functional unit, rather than the maximum. There is no requirement for a central processor in a DGS. Rather, the most generalised implementation of the DGS uses a distributed computing model consisting of a network of semi-autonomous interfaces and agents running in dedicated embedded microcomputers situated on individual modules or circuit cards and interconnected by an internal high speed serial bus or “backplane.” Each module is associated with a single HAN or WAN. 181 182 183 184 185 186 187 The interface to each HAN or W AN might be hosted in a variety of HES-gateway configurations. These HAN and WAN modules may be housed in a common gateway chassis or in multiple gateways that are easily interconnected. This system of modules is self configuring and should be hot-pluggable. This approach is similar to the “blade server” architecture now widely employed in the commercial networking industry. In more specialised implementations, although the modules might be combined and the internal protocol and bus might be collapsed, the principle of modularity shall be preserved. 188 189 190 191 192 193 194 195 Much like the design of the Internet, the HES-gateway seeks simplicity by separating content and application from transport and delivery. Such separation moves as much “intelligence” as possible out of the gateway . Applications and services reside on the periphery of the gateway (i.e., in service modules or on the respective HANs and WANs) where they can grow and develop in directions not dependent on the gateway itself. The HES -gateway design seeks to minimise the information or knowledge that the gateway needs about the products and services residing on each network. Rather, it provides a means of finding su ch information when needed. 196 197 198 199 200 201 This distributed minimalist architecture provides a measure of “future -proofing” by employing internal bus and protocol or language elements that are layered and upward compatible with future additions or changes. For example, the language elements are defined and contained in a metadata registry that can be endlessly re -configured and accessed by product developers. Protocol stacks for an expanding list of WAN and HAN protocols are maintained in an open-source library that is also available to developers. 202 2.3 203 204 205 206 207 208 209 [brief summary of goals and non-goals, see last paragraph of “scope” section] This standard seeks to establish a general-purpose interoperability platform or “translator” among home area networks and between specific wide area networks and such home area networks. This standard does not attempt to be a central controller or control system; and does not attempt to improve or resolve disparities or shortcomings among transmission technologies, protocols or application languages. However, this standard does seek to provide the premises with basic elements of security (i.e., firewall), safety, and autonomy. 210 2.4 211 212 [brief summary of conformity approach (e.g., self cetification, conformity testing trademark , etc.)] Distributed Gateway System Goals and non-goals Conformity ISO/IEC JTC 1/SC 493718434 ISO/IEC FDIS 15045-2 IEC:2004 ISO/IEC JTC1 SC25/WG 1 N 1100 –7– 15045-2 ISO/IEC:2004 213 3 References 214 3.1 215 216 217 The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. Normative references No: Reference Descriptive Title [1] ISO 7498 : 1984 Information processing systems - Open Systems Interconnection - Basic Reference Model [2] ISO/IEC TR-14543 Home Electronic System Architecture [3] ISO/IEC TR-14762 Guidelines for Functional Safety for Home Control Systems [4] ISO/IEC FDIS 18012-1 ISO/IEC FDIS 18012-1 Information technology — Interconnection of information technology equipment — Home electronic system — Guidelines for product interoperability — Part 1: Introduction [5] ISO/IEC FDIS 18012-2 ISO/IEC FDIS 18012-2 Information technology — Interconnection of information technology equipment — Home electronic system — Guidelines for product interoperability — Part 2: Taxonomy and Lexicon 218 3.2 Informative References 219 For the purposes of this International Standard, the following references may be useful. 220 [add informative references here—must be published material only] 221 4 222 4.1 223 224 For the purposes of this International Standard, the following definitions are applicable. [are these the right terms we need to define?] 225 226 227 4.1.1 API Application Programming Interface: The collection of invocation methods and associated parameters used by one piece of software to request actions from another piece of s oftware 228 229 4.1.2 Co-existence Two or more networks within a premises that do not interfere with one another 230 231 232 233 234 4.1.3 Component Refers to a logical subunit of a larger, encompassing concept. For example, the concept of Interoperability is broken down into constit uent components such as Safety, Management, and Operation. These constituent components are further broken down within their respective sections. Terminology Definitions ISO/IEC JTC 1/SC 493718434 ISO/IEC FDIS 15045-2 IEC:2004 ISO/IEC JTC1 SC25/WG 1 N 1100 –8– 15045-2 ISO/IEC:2004 235 236 The term component is also used to refer to logical subunits of system architecture concepts, such as the components of a networking implementation (e.g., addressing) 237 238 239 240 4.1.4 Device A distinct physical unit on a network. It can either be an end node on the network, or an intermediate node (as in the case of a network gateway device connecting two distinct physical networks) 241 242 4.1.5 Half-gateway [need definition here] 243 244 4.1.6 Interoperability Logical entities function together for applications on a network 245 246 247 4.1.7 Network A distinct interconnection of devices that share a single physical layer implementation in terms of the OSI layered network model (see ISO 7498-1:1994) 248 249 4.1.8 Object A unit of software functionality. Used as traditionally defined in object -oriented programming 250 251 4.1.9 Product A device or network that may be purchased to make up a Home Electronic System 252 253 254 4.1.10 Single implementation A single, homogeneous network implementation, where interoperability is only of concern within the single network 255 256 257 258 4.1.11 Multiple implementation A mixed collection of two or more network implementations. To establish interoperability, each network shall have a routing path to every other network in the system. This path may involve one or more hops through multiple intermediate networks 259 260 261 262 263 4.1.12 Intermediate implementation A mixed collection of two or more network implementations. To est ablish connectivity, it provides for a common intermediate translation between any two networks, assuring a worst case translation path of two hops (from any network to the common translation, and then from the common translation to the destination network 264 4.2 Abbreviations API CIS DBS DSL GWIF HAN HES IP MIB NTSC OSI PAL POTS RGIP SNMP USB Application Programming Interface Common Interoperability System Direct Broadcast Satellite Digital Subscriber Line Generic InterWorking Function Home Area Network Home Electronic System Internet Protocol Management Information Base National Television Standards Committee (TV standard, USA) Open Systems Interconnection Phase Alternate Line (TV standard, Europe) Plain Old Telephone Service (voice) Residential Gateway Internal Protocol Simple Network Management Protocol Universal Serial Bus ISO/IEC JTC 1/SC 493718434 ISO/IEC FDIS 15045-2 IEC:2004 ISO/IEC JTC1 SC25/WG 1 N 1100 VDSL WAN 15045-2 ISO/IEC:2004 –9– Very high speed DSL Wide Area Network 265 5 Requirements 266 5.1 267 268 269 270 271 272 273 274 275 276 The basic function of the HES Gateway is to translate messages between networks that use different communications protocols. This translation is accomplished by the Common Interoperability System (CIS), as specified in ISO 18012. Each message is translated into a common intermediate format, called the Residential Gateway Internal Protocol (R GIP). Then the RGIP format is translated into the protocol of the target network. The reason for introducing the RGIP is to accommodate multiple WANs and HANs without requiring separate translators for each possible combination of WAN and HAN , or HAN and HAN. The translation process in the HES Gateway is performed by the Generic Interworking Function (GIWF). A simple gateway linking one WAN and one HAN can incorporate a single translation process without using the RGIP. 277 278 279 280 281 282 283 In the most generalised implementation of the HES Distributed Gateway System, network interoperability shall be achieved by a dedicated interface module for each network that provides a GIWF linking this network to an abstract HES system network (AS) and internal protocol (RGIP). Alternatively, specific appliances may incorporate such GIWF and AS/RGIP interface functions (examples are provided in the section on reference models). Also, an optional specialised implementation such as the “simple gateway” (i.e., see ISO/IEC 15045-1, A.2.6.2) may combine modules into a single unit and collapse the internal bus. 284 285 286 287 Each module may be visualised as a “half-gateway” connected by an internal protocol and bus. This bus need not be confined to a common chas sis, but could be extended throughout the premises using an appropriate bus technology or tunnelling technique. Such a distributed half-gateway implementation options further described in later sections. 288 5.2 289 [identify stakeholder classes and their requirements] 290 6 291 6.1 292 293 294 The generalised HES-gateway system model is depicted in Figure 2, known as the CIS (Common Interoperability System) by which interoperability between all possible systems (present and future) is achieved. Modularity requirements Stakeholder requirements System model Abstract HES system 295 Abstract HES System (AS) 296 297 298 GIWF #1 GIWF #2 GIWF #3 GIWF #4 #1AS #2AS #3AS #4AS 299 300 System #1 ISO/IEC JTC 1/SC 493718434 System #2 System #3 System #4 ISO/IEC FDIS 15045-2 IEC:2004 ISO/IEC JTC1 SC25/WG 1 N 1100 – 10 – 15045-2 ISO/IEC:2004 301 302 Figure 2—Common Interoperability System (CIS) 303 304 305 306 The CIS defines an abstract HES (Home Electronic System) or set of common functions served by all home systems (including individual HANs and WANs). Each specific system is defined by a specific subset of the CIS, known as a GIWF . The CIS and GWIF are specified in ISO/IEC 18012, Guidelines for Product Interoperability . 307 6.2 308 309 310 311 312 313 314 The GIWF serves as a translator between the abstract (common) system and any specific system. The abstract HES is expressed and conveyed by an RGIP (Residential Gateway Internal Protocol) that includes a common protocol and an application language. In terms of the 7-Layer OSI Reference Model (ISO 7489), the GIWF resides above layer 7 (application layer) of the protocol stacks associated with any particular system’s interface module processor. An HES-gateway stack model is described further in a later section on the HESgateway internal processes. 315 6.3 316 [brief description of the conformance paradigm and roles of manufacturers] Generic Interworking Function (GIWF) Conformance paradigm—roles 317 ISO/IEC JTC 1/SC 493718434 ISO/IEC FDIS 15045-2 IEC:2004 ISO/IEC JTC1 SC25/WG 1 N 1100 – 11 – 15045-2 ISO/IEC:2004 318 7 Architecture 319 320 The basic physical architecture of the HES-gateway including associated architectural domains is shown in Figure 4. 321 Domain of HES-gateway Domain of WAN Domain of HAN 322 323 324 WAN WAN interface module 325 326 HESgateway internal bus and RGIP HAN interface module HAN HAN service module 327 328 329 Figure 4—HES-gateway Architectural Domains 330 331 332 333 334 335 336 337 338 339 340 341 342 The HES-gateway architecture consists of three domains, the Domain of the HES -gateway standard and the domains of the WAN and the HAN. The center block represents the HESgateway internal physical bus that conveys messages using the RGIP. The interface modules shown in Figure 4 are provided by manufacturers seeking to support various WAN or HAN networks. Each such module includes a portion that is in conformance with the HES -gateway standard and talks the language of CIS using specific GIWFs residing on each module. The se modules interconnect with each other using the RGIP and internal bus. All information processing resides on individual modules and not on the bus. There is n o specific limit to the number of modules (WAN, HAN, or service) that may be accommodated in any given configuration. However, the physical realisation of the RGIP and internal bus may set a practical limit. Three basic types of modules comprise a HES-gateway: WAN interface modules, HAN interface modules, and service modules. The latter two are associated with the domain of the HAN. 343 344 ISO/IEC JTC 1/SC 493718434 ISO/IEC FDIS 15045-2 IEC:2004 ISO/IEC JTC1 SC25/WG 1 N 1100 15045-2 ISO/IEC:2004 – 12 – 345 7.1 WAN interface module 346 347 348 349 350 351 The WAN interface module is a unit that provides a complete interface between a specific WAN and the HES-gateway internal bus and RGIP. A generalised block diagram of the WAN interface module is shown in Figure 5. The portion labelled “Domain of HES-Gateway is outside the WAN domain. For explanatory purposes, the following description will follow the flow of data from WAN to HAN. Typical WANs might include cable, xDSL, DBS, optical fiber, or wireless (e.g., LMDS, MMDS, IEEE 802.16, etc.). 352 Domain of HES-gateway 353 354 355 356 357 WAN Specific WAN interface WAN interface processes WAN private MIB GIWF& internal processes shared MIB RGIP interface processes RGIP private MIB RGIP & RG bus interface RGIP & RG bus 358 359 Figure 5—WAN Interface Block Diagram 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 The Specific WAN interface would include phys ical layer signalling, decoders or demodulators. WAN interface processes would include data processing and any protocol stack necessary to extract the message content up to the application layer (OSI layer 7) and deliver it to the GIWF and internal gatewa y processes for translation into the RGIP. The WAN interface processes are determined by the specific manufacturer and could also include any processes necessary for management of the WAN connection. A private memory or MIB (Management Information Base) might be needed to maintain such a connection (e.g., such as information relevant to maintaining a customer account relationship, passwords, usage statistics, account codes, etc.). The use of the term “MIB” here is borrowed from the IP (Internet Protocol) world, but in this case (unlike IP and SNMP – Standard Networking Management Protocol) it is not intended to imply external access to the MIB by other than a specific service provider. For instance, in the case of WAN modules, the intent is to provide a place to store private information about the WAN connection, that would allow a service provider or manufacturer to protect customer-specific information from competitors that may also have WAN modules installed in the same HES-gateway system. 375 376 377 378 379 380 381 382 The GIWF and internal gateway processes may also have access to a MIB for storage of information that might need to be shared by the WAN and the gateway ( e.g., connection status, error, data format or routing information). Once the data has been translate d into the RGIP by the GIWF process, it is passed to the RGIP internal processes, including protocol stack, that then passes it on to the internal bus and then to the appropriate HAN module(s). The RGIP private MIB might be used to store information neces sary for the proper delivery of such information (e.g., HES-gateway internal configuration information, addressing and routing, gateway management information, user preferences, access codes, etc.). 383 384 385 The portion of Figure 5 that lies within the domain of HES-gateway must be in conformance with the standard. The structure and content of the remaining portion is entirely at the option of the specific module manufacturer. ISO/IEC JTC 1/SC 493718434 ISO/IEC FDIS 15045-2 IEC:2004 ISO/IEC JTC1 SC25/WG 1 N 1100 15045-2 ISO/IEC:2004 – 13 – 386 7.2 HAN interface module 387 388 389 390 391 392 393 The HAN interface module is a unit that provides a complete interface between the HESgateway internal bus and RGIP and a specific HAN. A generalised block diagram of the HAN interface module is shown in Figure 6. The portion labelled “Domain of HES-Gateway is outside the HAN domain. Again, the data flow will be traced in the WAN to HAN direction for purposes of explanation. Typical HANs might include IEEE 1394 (Firewire or I -Link), CEBus, USB, Ethernet, IEEE 802.11 (WiFi), Bluetooth, Echonet, Konnex, HomePNA, NTSC video, PAL video, or POTS. 394 Domain of HES-gateway 395 RGIP interface processes 396 397 398 RGIP & RG bus RGIP & RG bus interface RGIP private MIB 399 GIWF & internal Processes shared MIB HAN interface processes HAN private MIB specific HAN interface HAN 400 401 Figure 6—HAN Interface Block Diagram 402 403 404 405 406 407 408 409 410 411 412 The operation of the HAN interface module follows a very similar pattern to the WAN interface module. The internal bus delivers the RGIP data to a RG bus interface. It is then passed to the RGIP interface processes where it is extracted up to layer 7 and delivered to the GIWF for translation into the specific HAN protocol. The RGIP private MIB might be used for storing local information such as internal configuration information ( e.g., addressing and routing, gateway management information, etc.). The GIWF and internal processes block formats the data and manages the appropriate user processes on the HAN side ( e.g., streaming, segmentation, error control, etc.), using a shared MIB, if necessar y. The translated data are then passed to the HAN interface processes, which actually manages the passing of data to the HAN devices, via the HAN specific interface. The HAN private MIB might be used for HAN configuration or services information, addr essing or routing. 413 414 415 416 The portion of Figure 6 that lies within the domain of HES-gateway must be in conformance with this standard. The structure and content of the remaining portion is entirely at the option of the specific module manufacturer. The HES-gateway portion is not responsible for specific knowledge about the HAN configuration or managing its services. 417 7.3 418 419 420 421 422 423 424 425 426 A third type of module in the HES-gateway is the Service Module. The Service Module resides in the domain of the HES-gateway and of the HAN. The Service Module has no HAN interface but acts as an agent for managing specific services on the HAN by having access to internal HES-gateway data traffic, and may be associated with specific HAN services. Typical Service Module applications might include security, firewall, data encryption, AAA (Authentication, Authorisation, and Accounting), energy management ( e.g., demand side management, remote meter reading), entertainment ( e.g., Interactive TV, PPV, VOD, etc.), or safety. Such applications and services might include those specified by OSGi (Open Services Gateway Initiative) or TAHI (The Application Home Initiative). Service module ISO/IEC JTC 1/SC 493718434 ISO/IEC FDIS 15045-2 IEC:2004 ISO/IEC JTC1 SC25/WG 1 N 1100 15045-2 ISO/IEC:2004 – 14 – 427 7.4 Data flows 428 429 430 431 432 433 The general data flows between the WAN and the HES-gateway system are shown in Figure 6, a copy of Figure 3 with data “pipes” overlaid to illustrate the termination of three kinds of data streams. The various functions in the HES-gateway may be managed remotely or from within the HAN, or by a combination of both. Individual portions of the HES-gateway (HAN or WAN modules) may be managed by separate entities requiring multiple remote management functions. 434 Domain of HES-gateway 435 436 WAN GIWF& interface User Service internal Functions processes processes 437 438 WAN Specific WAN interface WAN Gateway Functions private MIB WAN Functions 439 440 RGIP interface processes shared MIB RGIP private MIB RGIP & RG bus interface RGIP & RG bus 441 442 Figure 6—Data Flows 443 444 445 446 447 448 WAN functions are those that are only intended to manage the specific WAN interface and are the domain of the WAN service provider ( e.g., connection establishment signalling). The gateway functions are those that are shared between the WAN service provider and the gateway, but do not pass through the gateway to the HAN side (e.g., resource binding or routing information). User service functions are those that flow through to some application in the domain of the HAN (e.g., a video data stream). 449 7.4.1 450 [description of control information processing] 451 7.4.2 452 [description of content (data) processing] Control plane Content (data) plane 453 ISO/IEC JTC 1/SC 493718434 ISO/IEC FDIS 15045-2 IEC:2004 ISO/IEC JTC1 SC25/WG 1 N 1100 15045-2 ISO/IEC:2004 – 15 – 454 7.5 455 456 This section includes block diagrams depicting a series of “typical” or “possible” HES -gateway configurations for purposes of illustration. 457 WAN services 458 459 Reference models VDSL access WAN interfaces VDSL decoder ATM SAR 460 HAN interfaces MPEG 2 RF decoder modulator Ethernet interface 461 462 HES-gateway Internal bus 463 VoIP decoder POTS converter HAN appliances TV set PC phones 464 Figure 8—VDSL Reference Model 465 466 467 468 469 470 471 472 473 474 475 476 477 Figure 8 depicts the use of VDSL (Very-high-speed Digital Subscriber Line) service to provide voice, video and data service to the home. In this particular case, voice, video and data packets are delivered via VDSL (layer 1) service employing ATM (Asynchronous Transfer Mode) packet switching (layer 2 and 3) technology. The video packets, using MPEG 2 compression, are then decoded and converted to conventional RF modulated video and audio signals for display on a conventional TV set. A typical installation might employ more than one MPEG 2 interface module, depending on the capacity of the VDSL access service and the needs of the viewer. The MPEG 2 interface might also include a remote control receiver for initiating data traffic back to the video source to change channels or other purposes. In this example, the VoIP decoder could use a POTS (Plain Old Telephone Service) converter to provide multiple phone lines to the home and allow the use of conventional tele phone sets. The Ethernet interface might also provide a hub for multiple PCs or other Ethernet -based appliances. 478 WAN services 479 480 481 482 DSL access DBS dish WAN interfaces DSL decoder ATM SAR DBS receiver 483 484 HES-gateway Internal bus HAN interfaces MPEG 2 RF decoder modulator Ethernet interface VoIP decoder POTS converter HAN appliances TV set PC phones 485 Figure 9—DBS/DSL Reference Model 486 487 488 Figure 9 depicts the use of DBS (Direct Broadcast Satell ite) combined with DSL (Digital Subscriber Line) service to provide voice, video and data service to the home, much as in the preceding figure. In this case, video is provided by DBS and voice and data are provided by ISO/IEC JTC 1/SC 493718434 ISO/IEC FDIS 15045-2 IEC:2004 ISO/IEC JTC1 SC25/WG 1 N 1100 489 490 491 DSL. This arrangement may be employed where VDSL service is not available, or where DBS delivery is more advantageous. Also, DSL provides a reverse channel for the DBS service for PPV (Pay-Per-View), service provisioning or other interactive applications. 492 WAN services 493 DSL access 494 495 496 15045-2 ISO/IEC:2004 – 16 – cable drop WAN interfaces DSL decoder ATM SAR digital cable decoder 497 HES-gateway Internal bus HAN interfaces HAN appliances MPEG 2 RF decoder modulator TV set Ethernet interface PC CEBus interface Meter, energy applinances 498 499 energy management service module 500 501 Figure 10—Cable/DSL/Energy Management Reference Model 502 503 504 505 506 507 508 Figure 10 depicts the use of cable combined with DSL service to provide video and data service to the home. Such an arrangement might be employed when data service over cable is not available or when DSL might also be desirable for certain services. In this example, a CEBus (Consumer Electronics Bus) interface is also shown that might be used for remote meter reading and energy management functions. These functions might be man aged by a special service module provided by an energy utility or other service provider offering efficiency and cost advantages to the user. 509 WAN services 510 DSL access WAN interfaces DSL decoder ATM SAR HAN interfaces IEEE 802.11WiFi interface 511 512 513 HAN appliances healthcare appliances healthcare monitoring service module HES-gateway Internal bus 514 515 Figure 11—Healthcare Management Reference Model 516 517 518 519 520 Figure 11 depicts the use of DSL service to provide data service to speciali sed healthcare monitoring and management applications in the home. The specific healthcare appliances might employ wireless connections and be managed by a special service module provid ed by medical or healthcare related services. The DSL access could also be shared with other entertainment, data or communication applications shown in the previous figures. 521 ISO/IEC JTC 1/SC 493718434 ISO/IEC FDIS 15045-2 IEC:2004 ISO/IEC JTC1 SC25/WG 1 N 1100 15045-2 ISO/IEC:2004 – 17 – 522 523 524 525 526 527 WAN services DSL access (over POTS) WAN interfaces DSL decoder ATM SAR HAN interfaces HAN appliances HomePNA interface HES-gateway Internal bus POTS wiring HomePNA bridge POTS Phones Ethernet Appliances 528 529 Figure 12—DSL/HomePNA Reference Model 530 531 532 533 534 535 536 537 Figure 12 depicts the use of DSL service and HomePNA (Home Phone Network Alliance) signalling technology utilising the existing POTS wiring and connectors to provide combined conventional voice and Ethernet data services. The HomePNA interface module combines the analogue voice POTS signals with the digital Ethernet signals to convey the voice and data services from the WAN interface. A H omePNA bridge can extract the Ethernet/HomePNA signals or provide other appropriate formats, such as USB (Universal Serial Bus) or PCI (Peripheral Component Interconnect), to be used by various data application terminals. 538 539 540 541 542 Note that if one of the Ethernet Appliances on the HAN is a bridge to another HAN technology, such as 802.11x (wireless) or HomePlug ( utilising PLC - Power Line Carrier), this simple HAN can be expanded with segments based on different HAN technologies . This expansion of the HAN opens the possibility of receiving other WAN services through separate HES-gateways connected to these appended HAN segments. 543 HES-gateway unit 544 545 WAN 546 Halfgateway HAN Appliance(s) Halfgateway HAN Appliance(s) HES-gateway Internal bus 547 548 HAN WAN 549 550 Figure 13—Half-gateway Reference Model 551 552 553 554 555 Figure 13 depicts the use of two options for a half -gateway. The top example represents a case where the half-gateway module is physically removed from the HES-gateway unit and is linked by an extension of the internal bus and protocol. In this case, the HAN translation takes place in the half-gateway. The bottom example represents a case where the halfgateway employs a protocol that is already interoperable with the end user HAN appliance(s). ISO/IEC JTC 1/SC 493718434 ISO/IEC FDIS 15045-2 IEC:2004 ISO/IEC JTC1 SC25/WG 1 N 1100 15045-2 ISO/IEC:2004 – 18 – 556 8 Internal Processes 557 558 The HES-gateway internal processes include: 1) protocol stacks for both specific networks and the RGIP, 2) the RGIP, 3) the inter nal bus, and 4) network management functions. 559 8.1 560 8.1.1 561 562 563 564 A generalised model of the HES-gateway protocol stacks is shown in Figure 13. These stacks follow the convention of the OSI (Open Systems Interconnection) 7 layer model , which describes communication functions from the physical layer (layer 1) through the application layer (layer 7). The stack models in Figure 12 apply to either WAN or HAN modules. Protocol stacks Generalised model 565 566 GIWF Application HES-gateway Module #1 HES-gateway Module #2 GIWF: 1< > abstract system GIWF: 2< > abstract system 567 568 Application Application Application Application 569 Presentation Presentation Presentation Presentation 570 Session Session Session Session Transport Transport Transport Transport 572 Network Network Network Network 573 Data Link Data Link Data Link Data Link 574 Physical Physical Physical Physical 571 OSI Layers 575 576 HES-gateway internal bus Data Transfer HES-gateway RGIP Network 1 Network 2 577 578 Figure 13—HES-gateway Generalised Protocol Stack Model 579 580 581 582 583 584 585 586 587 Data transfer from network 1 to network 2 would begin by entering the network 1 HES gateway module and passing upward to the top of the specific network 1 stack where it is then passed to the GIWF which exists above the application layer. The GIWF translates the network 1 application language into the RGIP and then sends it downward through the RGIP stack to the HES-gateway internal bus. The data are transferred by the internal bus to the network 2 HES-gateway module where it is passed upward through its RGIP stack to the GIWF where it is translated into the application language of network 2. The data are then passed down the specific network 2 stack to network 2 —and then on to its final destination on network 2. 588 589 The specific network stacks are defined by the specific product manufacturer or by existing standards or other specifications. Many of these stacks will be accumulated and maintained ISO/IEC JTC 1/SC 493718434 ISO/IEC FDIS 15045-2 IEC:2004 ISO/IEC JTC1 SC25/WG 1 N 1100 – 19 – 15045-2 ISO/IEC:2004 590 591 592 in an open source library for use by those developing HES -gateway modules. Also associated with each of these stacks is a GIWF mapping the specific protocol to the abstract system defined as part of the HES-gateway CIS. 593 8.1.2 594 [Insert simple gateway protocol stack model (one WAN, one HAN) and supporting text.] 595 8.1.3 596 597 598 599 600 601 602 603 It is important to note that the GIWF is the application and not part of its associated stacks. The HES-gateway standard specifies the GIWF and the RGIP portions of this model. However, there is nothing to preclude additional application functions being added on top of the GIWF, depending on the particular network application being served. For instance, various service agents might reside above the GIWF, monitor the data flow, and modify or control the flow of data, or even initiate data messages, as might be appropriate to any particular application. An example might be the insertion of routing or addressing information, or perhaps to establish or terminate a data-stream connection. 604 605 606 In the case of the service module, the specific network stacks would be absent and only the RGIP would be employed. Typical service agents might include those specified by the OSGi or TAHI consortia. 607 8.1.4 608 [Text to be added.] 609 610 611 612 613 614 Figure 14, as a generalised model, might be taken to imply that all communication into and out of HES-gateway traverses all 7 layers of the ISO stack. Although such would be true in regard to “control plane” signalling, it would not be strictly true in cases of other data pl ane or data steam traffic. Some traffic will connect at the physical layer, data link layer, or network layer, as perhaps in the case of TLS or IPsec. Other traffic having little in the way of protocol stack, such as analogue CATV or POTS, may need to connect at the physical layer. 615 8.2 616 617 618 619 620 621 The term, RGIP (Residential Gateway Internal Protocol) is used here to refer to a complete 7 layer protocol and an HES oriented application language that includes a syntactic structure and semantic definitions comprising a lexicon of terms including objects and methods (actions). The RGIP is defined and standardised in such a way that it will allow the GIWF process to express (i.e., translate) any message to or from any specific HAN or WAN message. 622 8.3 623 624 625 626 627 628 629 The HES-gateway internal bus, if present, may be implemented using a high speed serial bus (e.g., such as 100 Mbps switched Ethernet, USB, or IEEE 1394). A common module connector will deliver both data and power. Although the transfer of isoch ronous data within the gateway will be frequently needed, a high data rate and a relatively small number of modules employed will allow for adequate internal bandwidth to avoid congestion. Also with some standard busses, higher data rates may be anticipat ed to be available for later implementations that will be upward compatible. 630 631 632 The internal bus can be extended directly between clusters of modules, permitting a distributed gateway. Modules can be independently powered or clusters may obtain their power separately using modular wall plug power supplies, thus easing the task of expanding Specific model – simple gateway GIWF application Data flow control plane signalling Internal Protocol (RGIP) Internal bus ISO/IEC JTC 1/SC 493718434 ISO/IEC FDIS 15045-2 IEC:2004 ISO/IEC JTC1 SC25/WG 1 N 1100 633 634 635 636 637 – 20 – 15045-2 ISO/IEC:2004 the HES-gateway system incrementally. Alternatively, the internal bus can be extended by the use of a tunneling protocol employing one of the HAN networks common to both c lusters. Such tunneling could even employ wireless HANs, although such may impose bandwidth limitations, depending on the situation. Figure 14 depicts the HES -gateway internal bus extension methods described above. 638 ISO/IEC JTC 1/SC 493718434 ISO/IEC FDIS 15045-2 IEC:2004 ISO/IEC JTC1 SC25/WG 1 N 1100 15045-2 ISO/IEC:2004 – 21 – 639 HES-gateway chassis 1 640 641 HAN a WAN x 642 643 HES-gateway Internal bus 644 645 virtual or real bus extension 646 protocol c Interface HES-gateway 2 chassis protocol c Interface WAN y 647 tunnel via protocol c 648 HAN b 649 650 651 Figure 14—HES-gateway Internal Bus Extension Methods 652 8.4 Service requirements 653 654 655 The HES-gateway will provide for the possibility of some level of uninterruptable power, such that basic services may be preserved independently of the availabili ty of house power, much as in the case of POTS. 656 8.5 657 658 659 660 661 662 663 The HES-gateway system, if implemented as a Distributed Gateway System, has no central controller. Modules may be installed at any time and a set of basic network management elements provided on each module will allow dynamic self-configuration. Depending on system or service requirements, more advanced network management elements could later be added in the form of a specialised service module. The HES -gateway standard will include basic network management elements dealing with the following issues: [how much should the gateway (interface modules know about what is on each network??] 664 Resource discovery 665 Addressing 666 Binding 667 Routing 668 Error control 669 Safety 670 Privacy 671 Security Network management 672 ISO/IEC JTC 1/SC 493718434 ISO/IEC FDIS 15045-2 IEC:2004 ISO/IEC JTC1 SC25/WG 1 N 1100 – 22 – 15045-2 ISO/IEC:2004 673 8.5.1 Resource discovery/allocation 674 8.5.2 Addressing/allocation 675 8.5.3 Binding 676 8.5.4 Routing 677 8.5.5 Error control 678 8.5.6 Safety 679 8.5.7 Privacy (aliasing/identification) 680 8.5.8 Security (firewall/authentication/process protection) 681 9 682 9.1 683 684 HES products and networks shall be required to implement the requirements of this standard of product interoperability under the following qualifying criteria: 685 Where two or more dissimilar HANs are installed or implemented in a premises 686 Where two or more dissimilar HANs are required to interoperate or interwo rk in a premises 687 688 Where a product acts as a bridge, router, gateway or residential gateway between two or more dissimilar HANs in a premises 689 9.2 690 691 In order to conform to this standard of Product Interoperability, pro ducts and networks that meet the qualifying criteria shall: 692 693 Implement functional safety as specified in ISO/IEC TR 14762 Guidelines for Functional Safety for Home Control Systems. 694 Implement measures to avoid or minimise potential hazards as specified in Se ction 5. Conformance Basic functions and requirements Compliance of qualifying products and networks 695 696 Prevent the unattended initiation/operation of potentially hazardous devices as specified in Section 5.2 697 698 699 Allow initiation commands to be sent to automatic or relocatable programmable devices only if the device can return reliably explicit informat ion as to the state of the load on the device as specified in 5.3 and 5.4 700 701 702 Implement specific rules for instances where commands from one HAN actuate devices on another dissimilar HAN as specified in 5.5 or if there is a situation of linked state changes between them as specified in 5.6 703 704 Ensure security measures are implemented if commands derive from a WAN source as specified in 5.7 705 706 Ensure that address translation between dissimilar HANs is clearly defined and disallow commands and broadcast messages if not, as specified in 5.8 and 5.9 707 708 709 710 711 Manage the installation of HES products and configuration interworking as specified in Section 6. Installation, configuration and management shall be carried out by personnel and systems appropriate to the procedures provided b y the HAN as specified in 6.2 and 6.3. ISO/IEC JTC 1/SC 493718434 ISO/IEC FDIS 15045-2 IEC:2004 ISO/IEC JTC1 SC25/WG 1 N 1100 15045-2 ISO/IEC:2004 – 23 – 712 713 714 If two dissimilar HANs are configured in premises, this shall be carried out by personnel and systems appropriate to the procedures provided by the more complex HAN as specified in 6.2 and 6.3. 715 716 To provide configuration interoperability, devices are required to support the components of configuration levels 1 to 4 as specified in 6.2 and Table 1. 717 718 719 720 To provide configuration interoperability for devices on multiple and dissimilar networks, the components of configuration le vels 1 to 4 shall be supported by the endpoint devices as well as the device between the networks as specified in 6.2 and Table 1. 721 722 Network or networks operating within a premises require that addressing, transport, data and applications shall interoperate as specified in Section 7. 723 724 The logical addressing scheme used shall be independent of the underlying transport mechanism as specified in 7.2 725 726 727 Translation between the logical addressing scheme and the transport addressing scheme shall be handled as a mapping function of the layer that binds the logical network to a particular transport as specified in 7.2 728 729 For a networked system to be interoperable, it shall support one of the three network configurations specified in 7.3 730 731 To provide information exchange inter operability, there shall be a common, defined set of value type primitives in a common lexicon as described in 7.4 and 7.5 732 733 734 735 A lexicon of common actions shall be defined as specified in 7.5 for direct translation between networks and for a common language for configuration and application actions such that actions of an application on one network shall be translated correctly to the actions of the same application on another network in the premises. Bibliography 736 737 738 EN 41 003, Particular safety telecommunications networks requirements for equipment to be connected to 739 IEC 60950-1, Information technology equipment - Safety - Part 1: General requirements 740 741 IEC 61508 (all parts), Functional safety of electrical/electronic/programmable electronic safety-related systems 742 743 744 745 IEC 62151, Safety of equipment electrically connected to a telecommunication network ISO/IEC TR-14543 (all parts), Information technology - Home Electronic System (HES) Architecture ISO/IEC JTC 1/SC 493718434