oSIST prEN IEC 62769-6-100:2022

Field Device Integration (FDI) - Part 6-100: Technology Mapping - Net

IEC 62769-6-100:2023 specifies the technology mapping for the concepts described in the Field Device Integration (FDI®[1]) standard. The technology mapping focuses on implementation regarding the components FDI® Client and User Interface Plug-in (UIP) using the Runtime .NET. This runtime is specific only to the WORKSTATION platform as defined in IEC 62769‑4.
[1] FDI is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.

Feldgeräteintegration (FDI®) - Teil 6-100: FDI-Technologieabbildungen - .Net

Intégration des appareils de terrain (FDI) - Partie 6-100: Mapping de technologies - Reseau

L'IEC 62769-6-100:2023 spécifie le mapping de technologies pour les concepts décrits dans la norme d'intégration des appareils de terrain (FDI®[1], Field Device Integration). Le mapping de technologies porte essentiellement sur la mise en œuvre des composants Client FDI® et Plugiciel d'interface utilisateur (UIP, User Interface Plug-in) à l'aide de l'environnement d'exécution .NET. Cet environnement d'exécution n'est spécifique qu'à la plateforme WORKSTATION définie dans l'IEC 62769‑4.
[1] FDI est une marque déposée de l’organisation à but non lucratif Fieldbus Foundation, Inc. Cette information est donnée à l'intention des utilisateurs du présent document et ne signifie nullement que l'IEC approuve le détenteur de la marque ou l'emploi de ses produits. La conformité n'exige pas l'utilisation de la marque. L'utilisation de la marque exige l'autorisation du détenteur de la marque.

Integracija procesne naprave (FDI) - 6-100. del: Preslikava tehnologije - Mreža

General Information

• Status: Not Published
• Public Enquiry End Date: 22-May-2022
• ICS: 25.040.40 - Industrial process measurement and control
• ICS: 35.100.05 - Multilayer applications
• ICS: 35.240.50 - IT applications in industry
• Technical Committee: MOV - Measuring equipment for electromagnetic quantities
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 04-Jul-2023
• Due Date: 08-Sep-2023
• Ref Project: EN IEC 62769-6-100:2023 - Field Device Integration (FDI®) - Part 6-100: Technology Mapping - .Net

Standards Content (Sample)

SLOVENSKI STANDARD
oSIST prEN IEC 62769-6-100:2022
01-maj-2022
Integracija procesne naprave (FDI) - 6-100. del: Načrtovanje tehnologije - Mreža
Field Device Integration (FDI) - Part 6-100: Technology Mapping - Net

Intégration des appareils de terrain (FDI) - Partie 6-100: Mapping de technologies -

Reseau
Ta slovenski standard je istoveten z: prEN IEC 62769-6-100:2022
ICS:
25.040.40 Merjenje in krmiljenje Industrial process
industrijskih postopkov measurement and control
35.240.50 Uporabniške rešitve IT v IT applications in industry
industriji
oSIST prEN IEC 62769-6-100:2022 en,fr,de

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
oSIST prEN IEC 62769-6-100:2022
---------------------- Page: 2 ----------------------
oSIST prEN IEC 62769-6-100:2022
65E/868/CDV
COMMITTEE DRAFT FOR VOTE (CDV)
PROJECT NUMBER:
IEC 62769-6-100 ED1
DATE OF CIRCULATION: CLOSING DATE FOR VOTING:
2022-03-04 2022-05-27
SUPERSEDES DOCUMENTS:
65E/841/RR
IEC SC 65E : DEVICES AND INTEGRATION IN ENTERPRISE SYSTEMS
SECRETARIAT: SECRETARY:
United States of America Mr Donald (Bob) Lattimer
OF INTEREST TO THE FOLLOWING COMMITTEES: PROPOSED HORIZONTAL STANDARD:
Other TC/SCs are requested to indicate their interest, if any,
in this CDV to the secretary.
FUNCTIONS CONCERNED:
EMC ENVIRONMENT QUALITY ASSURANCE SAFETY

SUBMITTED FOR CENELEC PARALLEL VOTING NOT SUBMITTED FOR CENELEC PARALLEL VOTING

Attention IEC-CENELEC parallel voting
The attention of IEC National Committees, members of
CENELEC, is drawn to the fact that this Committee Draft for
Vote (CDV) is submitted for parallel voting.
The CENELEC members are invited to vote through the
CENELEC online voting system.

This document is still under study and subject to change. It should not be used for reference purposes.

Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of which they

are aware and to provide supporting documentation.
TITLE:
Field Device Integration (FDI) - Part 6-100: Technology Mapping - Net
PROPOSED STABILITY DATE: 2025

Copyright © 2022 International Electrotechnical Commission, IEC. All rights reserved. It is permitted to download this

electronic file, to make a copy and to print out the content for the sole purpose of preparing National Committee positions.

You may not copy or "mirror" the file or printed version of the document, or any part of it, for any other purpose without

permission in writing from IEC.
---------------------- Page: 3 ----------------------
oSIST prEN IEC 62769-6-100:2022
65E/868/CDV – 2 – IEC CDV 62769-6-100 © IEC:2022
NOTE FROM TC/SC OFFICERS:
---------------------- Page: 4 ----------------------
oSIST prEN IEC 62769-6-100:2022
65E/868/CDV – 3 – IEC CDV 62769-6-100 © IEC:2022
1 CONTENTS

3 FOREWORD .......................................................................................................................... 5

4 1 Scope ............................................................................................................................. 7

5 2 Normative references ...................................................................................................... 7

6 3 Terms, definitions, abbreviated terms, acronyms and conventions .................................. 7

7 3.1 Terms and definitions ............................................................................................. 7

8 3.2 Abbreviated terms and acronyms ........................................................................... 8

9 3.3 Symbols ................................................................................................................. 8

10 4 Technical concepts ......................................................................................................... 8

11 4.1 General .................................................................................................................. 8

12 4.1.1 Overview ......................................................................................................... 8

13 4.1.2 FDI Type Library ............................................................................................. 8

14 4.2 UIP representation ................................................................................................. 9

15 4.3 UIP executable representation ............................................................................... 9

16 4.4 UIP executable compatibility rules ........................................................................ 10

17 4.5 Allowed .NET CLR versions.................................................................................. 10

18 4.5.1 General ......................................................................................................... 10

19 4.5.2 CLR compatibility strategy ............................................................................ 10

20 4.5.3 How to identify the .NET target platform of a UIP .......................................... 11

21 4.6 UIP Deployment ................................................................................................... 11

22 4.7 UIP Life-cycle ....................................................................................................... 12

23 4.7.1 General ......................................................................................................... 12

24 4.7.2 UIP Assembly activation steps ...................................................................... 12

25 4.7.3 UIP Assembly deactivation steps .................................................................. 14

26 4.7.4 Backward compatibility .................................................................................. 15

27 4.8 Interaction between an FDI Client and a UIP ........................................................ 15

28 4.8.1 Handling of standard UI elements ................................................................. 15

29 4.8.2 Non-blocking service execution ..................................................................... 15

30 4.8.3 Blocking service execution ............................................................................ 16

31 4.8.4 Cancel service execution .............................................................................. 17

32 4.8.5 Threading ..................................................................................................... 18

33 4.8.6 Timeout ......................................................................................................... 18

34 4.8.7 Exception handling ........................................................................................ 19

35 4.8.8 Type safe interfaces ...................................................................................... 20

36 4.8.9 Globalization and localization ........................................................................ 20

37 4.8.10 WPF Control handling ................................................................................... 20

38 4.8.11 Win Form handling ........................................................................................ 20

39 4.9 Security ................................................................................................................ 20

40 4.9.1 General ......................................................................................................... 20

41 4.9.2 Access permissions ...................................................................................... 21

42 4.9.3 Code identity concept.................................................................................... 21

43 5 Interface definition ........................................................................................................ 22

---------------------- Page: 5 ----------------------
oSIST prEN IEC 62769-6-100:2022
65E/868/CDV – 4 – IEC CDV 62769-6-100 © IEC:2022

44 Bibliography ......................................................................................................................... 26

46 Figure 1 – FDI Type Library structure ..................................................................................... 9

47 Figure 2 – .NET surrogate process ....................................................................................... 11

48 Figure 3 – Identification of Run-time Version ........................................................................ 11

49 Figure 4 – Example snippet of a UIP host config file for the binding redirect ......................... 15

50 Figure 5 – IAsyncPattern based asynchronous service execution example ........................... 16

51 Figure 6 – Blocking service execution example using IAsyncResult based pattern ............... 17

52 Figure 7 – Cancel service processing sequence example ..................................................... 17

53 Figure 8 – Exception source ................................................................................................. 19

55 Table 1 – Base Property Services ........................................................................................ 22

56 Table 2 – Device Model Services ......................................................................................... 22

57 Table 3 – Access Control Services ....................................................................................... 22

58 Table 4 – Direct Access Services ......................................................................................... 23

59 Table 5 – Hosting Services ................................................................................................... 23

60 Table 6 – UIP Services ......................................................................................................... 24

61 Table 7 – Base Data Types .................................................................................................. 24

62 Table 8 – Special Types ....................................................................................................... 25

---------------------- Page: 6 ----------------------
oSIST prEN IEC 62769-6-100:2022
IEC CDV 62769-6-100 © IEC:2022 – 5 – 65E/868/CDV
65 INTERNATIONAL ELECTROTECHNICAL COMMISSION
66 ____________
68 FIELD DEVICE INTEGRATION (FDI) –
70 Part 6-100: Technology Mapping - .NET
72 FOREWORD

73 1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising all national

74 electrotechnical committees (IEC National Committees). The object of IEC is to promote international co-operation on all

75 questions concerning standardization in the electrical and electronic fields. To this end and in addition to other activities , IEC

76 publishes International Standards, Technical Specifications, Technical Reports, Publicly Available Specifications (PAS) and

77 Guides (hereafter referred to as “IEC Publication(s)”). Their preparation is entrusted to technical committees; any IEC Natio nal

78 Committee interested in the subject dealt with may participate in this preparatory work. International, governmental and non-

79 governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely with the

80 International Organization for Standardization (ISO) in accordance with conditions determined by agreement between the two

81 organizations.

82 2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international consensus

83 of opinion on the relevant subjects since each technical committee has representation from all interested IEC National

84 Committees.

85 3) IEC Publications have the form of recommendations for international use and are accepted by IEC National Committees in

86 that sense. While all reasonable efforts are made to ensure that the technical content of IEC Publications is accurate, IEC

87 cannot be held responsible for the way in which they are used or for any misinterpretation by any end user.

88 4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications transparently to

89 the maximum extent possible in their national and regional publications. Any divergence between any IEC Publication and the

90 corresponding national or regional publication shall be clearly indicated in the latter.

91 5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity assessment

92 services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any services carried out b y

93 independent certification bodies.

94 6) All users should ensure that they have the latest edition of this publication.

95 7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and members of its

96 technical committees and IEC National Committees for any personal injury, property damage or other damage of any nature

97 whatsoever, whether direct or indirect, or for costs (including legal fees) and expenses arising out of the publication, use of,

98 or reliance upon, this IEC Publication or any other IEC Publications.

99 8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is indispensable

100 for the correct application of this publication.

101 9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of patent rights. IEC

102 shall not be held responsible for identifying any or all such patent rights.

103 IEC 62769-6-100 has been prepared by subcommittee 65E: Devices and integration in enterprise systems,

104 of IEC technical committee 65: Industrial-process measurement, control and automation. It is an

105 International Standard.
106 The text of this International Standard is based on the following documents:
Draft Report on voting
XX/XX/FDIS XX/XX/RVD
107

108 Full information on the voting for its approval can be found in the report on voting indicated in the above

109 table.

110 The language used for the development of this International Standard is English.

---------------------- Page: 7 ----------------------
oSIST prEN IEC 62769-6-100:2022
65E/868/CDV – 6 – IEC CDV 62769-6-100 © IEC:2022

111 This document was drafted in accordance with ISO/IEC Directives, Part 2, and developed in accordance

112 with ISO/IEC Directives, Part 1 and ISO/IEC Directives, IEC Supplement, available at

113 www.iec.ch/members_experts/refdocs. The main document types developed by IEC are described in

114 greater detail at www.iec.ch/standardsdev/publications.

115 The committee has decided that the contents of this document will remain unchanged until the stability

116 date indicated on the IEC website under "http://webstore.iec.ch" in the data related to the specific

117 document. At this date, the document will be
118 • reconfirmed,
119 • withdrawn,
120 • replaced by a revised edition, or
121 • amended.
122
---------------------- Page: 8 ----------------------
oSIST prEN IEC 62769-6-100:2022
IEC CDV 62769-6-100 © IEC:2022 – 7 – 65E/868/CDV
123
124 FIELD DEVICE INTEGRATION (FDI) –
125
126 Part 6-100: Technology Mapping - .NET
127
128
129
130 1 Scope

131 This part of IEC 62769 specifies the technology mapping for the concepts described in the Field Device

132 Integration (FDI) standard. The technology mapping focuses on implementation regarding the components

133 FDI Client and User Interface Plug-in (UIP) using the Runtime .NET. This runtime is specific only to the

134 WORKSTATION platform as defined in IEC 62769-4.
135 2 Normative references

136 The following documents, in whole or in part, are normatively referenced in this document and are

137 indispensable for its application. For dated references, only the edition cited applies. For undated

138 references, the latest edition of the referenced document (including any amendments) applies.

139 IEC 61804 (all parts), Function blocks (FB) for process control and Electronic Device Description

140 Language (EDDL)
141 FCG TS10099, Field Device Integration (FDI) – Technology Management
142 IEC 62769-1, Field Device Integration (FDI) – Part 1: Overview
143 IEC 62769-2, Field Device Integration (FDI) – Part 2: FDI Client
144 IEC 62769-4, Field Device Integration (FDI) – Part 4: FDI Packages
145 IEC 62769-6, Field Device Integration (FDI) – Part 6: Technology Mappings

146 ISO/IEC 19505-1, Information technology – Object Management Group Unified Modeling Language (OMG

147 UML) – Part 1: Infrastructure
148 3 Terms, definitions, abbreviated terms, acronyms and conventions
149 3.1 Terms and definitions

150 For the purposes of this document, the terms and definitions given in IEC 62769-1, IEC 62769-6, as well

151 as the following apply.
152 1.1.1
153 Application Domain
154 isolated environment where applications execute
155 1.1.2
156 Assembly

157 reusable, version information providing, and self-describing building block of a CLR application

---------------------- Page: 9 ----------------------
oSIST prEN IEC 62769-6-100:2022
65E/868/CDV – 8 – IEC CDV 62769-6-100 © IEC:2022
158 1.1.3
159 Global Assembly Cache

160 machine-wide code cache that stores Assemblies specifically designated to be shared by several

161 applications
162 1.1.4
163 Windows Registry

164 system-defined database in which applications and system components store and retrieve configuration

165 data
166 3.2 Abbreviated terms and acronyms

167 For the purposes of this document, the abbreviated terms and acronyms given in IEC 62769-1,

168 IEC 62769-6, as well as the following apply.
MSI Microsoft Installer
WPF Windows Presentation Foundation
UML Unified Modeling Language
169
170 3.3 Symbols

171 Figures in this document use the graphical symbols according to ISO/IEC 19505-1, (UML 2.0).

172 4 Technical concepts
173 4.1 General
174 4.1.1 Overview

175 In 4.1.2, 4.2, 4.3, 4.4, and 4.5, this document describes the technology base for UIP implementation based

176 on the runtime .NET Framework CLR4, the hardware and software environment including the related

177 implementation rules. Clause 4 follows a lifecycle (use case) oriented approach.

178 Subclause 4.6 describes the copy deployment procedures and related implementation rules for the UIP

179 and the FDI Client. UIP executable instantiation and termination is described in 4.7. Subclause 4.8 defines

180 the rules about interaction between the FDI Client and the UIP. Security related definitions are written in

181 4.9. The service interface definitions for the FDI Client and the UIP are found in Clause 5.

182 4.1.2 FDI Type Library

183 The Device Access Services and the UIP Services can be modelled as .NET interfaces passing .NET data

184 type arguments. These interfaces and data types are used for the data exchange and interaction between

185 the UIP and the FDI Client. For runtime error handling purposes during interface method calls .NET

186 exceptions classes are defined.

187 The FDI .NET interfaces, data types, and exception classes are defined in a single FDI Type Library. The

188 FDI Type Library is provided within a Nuget Package, which contains one or more strong named

189 assemblies. The file name of this Nuget Package shall be Fdi..nupkg. The FDI Type Library shall

190 be versioned as per IEC 62769-1 – section 8.1. The FDI Type Library is part of the FDI Core Technology

191 as per IEC 62769-1 – section 8.3.2.1. Therefore, it directly influences the FDI Technology Version. All

192 compatible changes of the FDI Type Library lead to an increase of the minor portion of the FDI Technology

193 Version. Incompatible changes lead to an increase of the major portion of the FDI Technology Version

194 (see IEC 62769-1 – section 8.3.2.2). The version information of the FDI Type Library can be found in

195 FCG TS10099.
---------------------- Page: 10 ----------------------
oSIST prEN IEC 62769-6-100:2022
IEC CDV 62769-6-100 © IEC:2022 – 9 – 65E/868/CDV

196 The FDI Type Library is signed with a single unique key by the issuer of the file. The FDI Type Library

197 shall be installed separately as part of every FDI Client installation. User Interface Plug -Ins (UIP) and the

198 FDI Client Application shall use this instance of the FDI Type Library. UIPs shall not carry or deploy the

199 FDI Type Library. The FDI Client is responsible to provide means to allow updates of this type library over

200 time.
201
202 Figure 1 shows the FDI Type Library structure.
203
204 Figure 1 – FDI Type Library structure

205 NOTE The composite structure diagram shows only the core interfaces that implement the interfaces defined in .

206 4.2 UIP representation

207 The UIP Variant can contain either a single or multiple runtime modules (.NET Assembly) and their related

208 supplementary files (for example: resource files). The runtime module of the UIP Variant is called UIP

209 executable. The supplementary file(s) of the UIP Variant is/are called UIP supplement(s).

210 UIP supplement(s) is/are stored under (a) subfolder(s) of the UIP executable installation directory

211 EXAMPLE Examples of UIP supplementary data files include resource files and application configuration data.

212 The supported RuntimeIds and .NET Framework versions for a specific FDI Technology Version are

213 specified in FCG TS10099 FDI Technology Management.

214 The UIP Variant shall be self-contained. All UIP required libraries (.NET Assemblies) required by a UIP

215 Variant are stored within the same Folder.
216 4.3 UIP executable representation

217 The implementation of the UIP depends on the type of user interface elements that can be embedded into

218 the user interface hosting environment of the FDI Client. UIP shall be implemented as a .NET

219 System.Windows.Forms class UserControl or a WPF System.Windows.Controls class UserControl.

---------------------- Page: 11 ----------------------
oSIST prEN IEC 62769-6-100:2022
65E/868/CDV – 10 – IEC CDV 62769-6-100 © IEC:2022

220 UIP executables and their required libraries shall have strong names. The signing of a strong named

221 Assembly can be done using a self-generated key.

222 NOTE The identity of strong named Assemblies consists of a name, version, culture, public key token and digital signature.

223 UIP executables and their required libraries shall be shipped with file containing the public key i n order to

224 enable Assembly verification.
225 4.4 UIP executable compatibility rules

226 The compatibility rules for different versions of the UIP component are specified in IEC 62769-4.

227 The compilation target platform for the UIP shall be “anyCPU”. If this is not feasible the UIP shall be

228 shipped in two variants. One UIP variant shall be compiled for target platform “x86”. The second UIP

229 variant shall be compiled for target platform “x64”. The compilation platform target shall be described in

230 the catalog.xml file which is defined in IEC 62769-4. This catalog.xml file contains an xml element

231 “CpuInformation” that describes the User Interface Plug-in variant. The allowed values that shall be used

232 in the xml element “CpuInformation” are “anyCPU”, “x86” or “x64”.
233 4.5 Allowed .NET CLR versions
234 4.5.1 General

235 Specific CLR versions are released for the execution of software components built with specific .NET

236 Framework versions. The .NET CLR version 4.0 is used to execute software components built with .NET

237 Framework 4.0. .NET Components are built for one CLR version only but can be capable to run also under

238 a newer CLR version.

239 FDI Clients can be built based on CLR version 4.0 or future versions. An FDI Client has to realize the

240 following situations when starting a UIP.

241 • When the UIP to be started was built for the same run-time, the UIP can be started in the FDI Client

242 as usual.

243 • When the UIP to be started was built with another CLR version and is not compiled for the current

244 running CLR version, the FDI Client shall start the UIP in a surrogate process with the adequate CLR

245 version. (More details are described in 4.5.2.)

246 Taking this behavior in account, a UIP shall be developed for CLR version 4.0 or any future version. In

247 case the CLR versions do not match, the UIP shall be started in a separate process. The UIP will then not

248 be displayed as an integrated module within the FDI Client. It is up to the FDI Client to realize the surrogate

249 process.
250 4.5.2 CLR compatibility strategy

251 In the future, FDI Clients and UIPs will be permitted to be built on different incompatible versions of the

252 CLR.

253 If an FDI Client detects that a UIP requires a CLR that is not compatible with the FDI Client, the FDI Client

254 can use a proxy class that enables interaction with the UIP built using a different version of the CLR.

255 The FDI Client loads a proxy UIP executable, creates an instance of the proxy cl ass, and delegates the

256 execution of the UIP to this proxy. The proxy starts a process with the required CLR and executes the UIP

257 in this surrogate process. The proxy classes provide the standard FDI interfaces. The FDI Client can use

258 these interfaces to interact with the UIP executed in the surrogate process.
---------------------- Page: 12 ----------------------
oSIST prEN IEC 62769-6-100:2022
IEC CDV 62769-6-100 © IEC:2022 – 11 – 65E/868/CDV
FDI Client Process
«library»
UIP Interface Proxy
.NET CLR Surrogate Process
«library»
UIP Interface Stub
«executable»
UIP
259
260 Figure 2 – .NET surrogate process
261 4.5.3 How to identify the .NET target platform of a UIP

262 The .NET target platform CLR version information for which a certain Assembly is compiled can be extracted by

263 means of .NET Framework library functions (see
clrVersion = Assembly.LoadFrom().ImageRuntimeVersion;
264
265 Figure 3).
clrVersion = Assembly.LoadFrom().ImageRuntimeVersion;
266
267 Figure 3 – Identification of Run-time Version

268 NOTE The Visual Studio 2008 and 2010 IDE allow developers to select the .NET Framework target. The selection of a .NET

269 Framework target older than the base for the current Visual Studio IDE automatically creates a configuration file listed as

270 “app.config” within the solution explorer. This file only reflects the current complier setting. The compiler does not read t hat file.

271 4.6 UIP Deployment

272 The general UIP installation rules are outlined in IEC 62769-2. The UIP executable shall not be registered

273 within the Global Assembly Cache.

274 The “strong-name” rule ensures that related Assemblies of different versions of the UIP can coexist during

275 runtime.

276 The FDI Client implementation ensures that UIP deployment works independently from current user

277 credentials. (See the NOTE below.)

278 NOTE Certain operating system managed folders require specific access rights, for example, modifications in folder “Program

279 Files” require “Administrator” rights. The Windows operating system provides several means to allow an application running wi th

Visual Studio is the trade name of Microsoft Corporation. This information is given for the convenience of users of this part of

FCG TS62769 and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance

does not require use of the trade name. Use of the trade name requires permission of the trade nam e holder.

---------------------- Page: 13 ----------------------
oSIST prEN IEC 62769-6-100:2022
65E/868/CDV – 12 – IEC CDV 62769-6-100 © IEC:2022

280 restricted user rights, to execute actions with administrator privileges transparent to the user, for example, special restriction

281 handling for identified directories, services with administration rights, executables that are configured to automatically ru n with

282 administration rights. The alternative is to copy UIP executables into folders writeable for “normal” users.

283 4.7 UIP Life-cycle
284 4.7.1 General

285 The UIP state machine, outlined in IEC 62769-2, is composed of the Loaded, Created, Operational,

286 Deactivated and Disposed states. The mechanisms affecting state changes are described in 4.7.

287 After the FDI Client has stored the UIP executable on the FDI Client the FDI Client loads the UIP

288 Assemblies dynamically into the memory and executes the related logic by calling the corresponding FDI

289 specified interface functions.

290 Subclause 4.7 describes rules about how the FDI Client shall activate and deactivate the UIP.

291 4.7.2 UIP Assembly activation steps
292 4.7.2.1 Load

293 The FDI Client shall load the UIP executables by using the LoadFrom mechanism. The .NET framework

294 provides System.Reflection.Assembly.LoadFrom for this purpose:
295 The LoadFrom mechanism behaves as follows.

296 • LoadFrom loads the Assembly addressed with the file path and also the referenced Assemblies

297 located within same directory. The argument string assemblyFile shall contain the file name of the

298 UIP executable. The file name of the UIP executable represents the StartElementName described in

299 IEC 62769-4.

300 • If an Assembly is loaded with LoadFrom, and later an Assembly in the “load context” attempts to load

301 the same Assembly by display name, then this load attempt fails.

302 • If an Assembly with the same identity is already loaded (for example, by another UIP), then

303 LoadFrom returns the Assemb
...