hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
6d2cffa783978764a5328727a2d01168 | 104 007 | 8.2.1 Overview | If both ends of an interface do not terminate in a secure enclave, the entire chain may be compromised. As an example, the visibility of X0, X1, X2/X3, HI2/HI3/HI4 interfaces in the network is a good place to start. Assuming basic measures such as TLS are taken, the vulnerability is pushed into the endpoints of the int... |
6d2cffa783978764a5328727a2d01168 | 104 007 | 8.2.2 Analysis | Using the LI interfaces as an example, figure 8.2.2-1 below identifies network elements susceptible to attack, the attack locations, and objects of attack. As previously stated, NFs are Network Functions, and ELIs are Elements of LI, such as Points of Interception (POIs), Triggering Functions (TFs), and Mediation and D... |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 1 Scope | The present document defines what an Artificial Intelligence (AI) threat is and defines how it can be distinguished from any non-AI threat. The model of an AI threat is presented in the form of an ontology to give a view of the relationships between actors representing threats, threat agents, assets and so forth and de... |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 2 References | |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 3 Definition of terms, symbols and abbreviations | |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 104 221 [i.21], ISO/IEC 22989 [1] and the following apply: Artificial General Intelligence (AGI): applying intelligence to any intellectual task, at a level equivalent to a human NOTE: AGI is also termed Strong AI. Artificial Intelligence (AI): abilit... |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 3.2 Symbols | Void. |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TR 104 221 [i.21] and the following apply: AGI Artificial General Intelligence AI Artificial Intelligence ANI Artificial Narrow Intelligence ASI Artificial Super Intelligence CAV Connected and Autonomous Vehicles CIA Confidentiality Integrity Ava... |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 4 From taxonomy to an ontology for secure AI | |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 4.1 Overview | An ontology in information science identifies a set of concepts and categories within a particular field of knowledge that shows the properties of the concepts and categories and the relations between them. ETSI ETSI TS 104 050 V1.1.1 (2025-03) 8 This overview illustrates and demonstrates how the various concepts that ... |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 4.2 Formal expression of an ontology | There are many ways to express an ontology in information science. The most common are: • OWL - Ontology Web Language [i.5] • RDF - Resource Description Framework [i.6] It should be noted, however, that OWL and RDF, whilst common when referring to ontologies, are not equivalent but are mutually supportive. A simple mod... |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 4.3 Relationship to other work | In the scope of the present document an ontology is also developed to assist in the development of strategies in securing AI. This addresses the modes in which AI can exist in a system, shown figuratively in Figure 3 below. Figure 3: Modes of application of AI in networks and services AI can be deployed in attack mode ... |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 5 Threat landscape | |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 5.1 Threat dimensions | The TVRA model in ETSI TS 102 165-1 [2] states that "A threat agent enacts a specific attack against a system weakness to exploit a vulnerability". AI shall be considered in the context of each of the items in this statement identified with bold text, in both offensive and defensive contexts. The SAI problem statement ... |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 5.2 Attacks as instance of threat agent | According to a 2019 report by Forrester, 86 % of cybersecurity decision makers are concerned about the offensive use of AI by threat actors [i.10]. As with many other organizations, adversaries are increasingly looking to AI to automate, scale and speed up activities which are currently conducted manually. This is part... |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 5.3 Adversarial Goals | |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 5.3.1 Violation of Confidentiality | As mentioned above, data is a crucial asset in an AI-based system. By definition, information about training data is encoded in a model itself: a model can be considered the aggregated understanding of a scenario or task derived from analysis of many examples of that scenario. Techniques exist whereby an adversary can ... |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 5.3.2 Violation of Integrity and Availability | As described in clause 5, the role of AI in a system is usually to make inferences about data to enable downstream decision making (human or machine), or to carry out actions based on input data. Compromise of the AI component can hence lead to a violation of integrity of the system, in that inferences and decisions wi... |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 5.4 Threat modelling | |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 5.4.1 Attacker objectives | As with any cyberattack, an adversary will ultimately be aiming to extract information from a system or affect its operation in some way. The adversary can choose to do so using AI, or by attacking AI components, but ultimately the objective will be to affect a system or the information within it. Where an AI component... |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 5.4.2 Attack surface | |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 5.4.2.1 AI effect on impact and likelihood | As discussed in clause 6.2, the use of AI in an offensive context is not likely to increase the attack surface, or if it does, only because AI is being used to attack vulnerabilities in AI components. It can, however, increase the likelihood of attacks being prosecuted at all and/or successfully. This restates the asse... |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 5.4.2.2 Data acquisition and curation | As previously described, compromise of training data represents a compromise of the system itself as the training data represents a core asset of the AI's performance. This is the case regardless of whether by "training data" it is meant the data used to create the initial model, or any additional data used to fine-tun... |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 5.4.2.3 Implementation | The training phase is where any offline manipulation of training data becomes encoded into a model i.e. where dataset compromise becomes model compromise. In reinforcement learning, an adversary can modify the environment in which the RL agent is learning, in order to cause it to learn an incorrect or suboptimal policy... |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 5.4.2.4 Deployment | Ultimately, compromise of a model cannot cause harm until that model, or one based upon it, is deployed. If an actor can trigger an incorrect response from a model (e.g. misclassification by inputting adversarial examples or by taking advantage of a backdoor), then they may be able to achieve an effect on the system do... |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 5.4.2.5 Humans | The human interaction with, and understanding of, AI is a factor that is worth emphasizing in this context. As previously mentioned, AI is a growing field, and understanding of AI is likely to be less widespread than for other software paradigms. This lack of understanding can affect threats and potential outcomes. As ... |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 5.4.3 Trust model | Trust is at the root of security in ICT systems. In symmetric relationships for example, there is trust that Alice does not share with Eve any secrets at the heart of her relationship with Bob. Several classes of actors are relevant to a deployed ML-based system as shown in Table 1. Table 1: Classes of actor in deploye... |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 5.5 Statistics in AI and ML | In many ML systems, such as those offered in packaged programming suites and covered in ML practitioner education, the underlying approach is based on forms of statistical analysis of large data sets. In ontological terms the role of statistical analysis in ML can be addressed by defining the relationship "is enabled b... |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 6 AI and SAI ontology | |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 6.1 Nouns, verbs, adverbs and adjectives | An ontology is fundamentally a language to describe a domain. For intelligence, and for the particular domain of AI, and then for the action of securing AI, it is useful to move from natural language to the ontological expression in small steps (see Table 2 for a mapping of terms in natural language to their model form... |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 6.2 Taxonomy and ontology | A taxonomy is a means of classification, and an ontology is an extension of a taxonomy by the inclusion of how things are related across classifications. Thus, in the security domain a taxonomy will often identify authentication methods within a taxonomical class, or when reporting vulnerabilities using the Common Vuln... |
9ff69be2a632fa79a2425a4abce25074 | 104 050 | 6.3 Core SAI ontology relationships | Security can be understood within a wider ontology representing the state of relations between objects that symbolize, in broad terms, the Confidentiality Integrity Availability (CIA) paradigm. As such, attacks that undermine the relationships inherent in that paradigm are at the heart of understanding the role of secu... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 1 Scope | The present document is a revision of ETSI GS OSG 001 [i.5] (mainly clause 7 on security). ETSI GS OSG 001 [i.5] was originally created under the ETSI ISG OSG. This ETSI ISG is now closed and no longer active and its area of work falls under the TC PLT. The security specified in ETSI GS OSG 001 [i.5] has become obsolet... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 2 References | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 3 Definitions and abbreviations | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: active energy/power: measure of active power expended over time (resistive load) AES: symmetric 128-bitblock data encryption technique authentication: process where data is validated to be current and to have come from the expected sou... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ABO Alarm read/Big read/One-time-read AC Alternating Current ADC Analog to Digital Conversion ADD Automated Device Discovery AES Advanced Encryption Standard APDU Application Protocol Data Unit ASCII American Standard Code for Information Inte... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 4 OSGP operation overview | This clause illustrates how a data concentrator can leverage OSGP to read or write a value in an OSGP device. In figure 1, a data concentrator issues a Table Read Request (see clause 9) targeted to a specific OSGP device, identified by its subnet/node or Unique Node ID. For a complete reference of available OSGP applic... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 5 OSGP network formation and maintenance | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 5.0 Foreword | This clause defines the manner in which the OSGP network will automatically discover and maintain OSGP device topology. This capability is known as the Automated Topology Management (ATM) feature. The ATM feature includes the following capabilities: • Automated association of a device to a DC at installation. • Automat... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 5.1 Discovery Protocol | The basic mechanism used to make device associations is a discovery mechanism called Automated Device Discovery (ADD). ADD allows the DC to discover any device supporting ADD, including other DCs. The discovery can be made through repeaters whether or not those repeaters are not commissioned, commissioned in the DC's d... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 5.2 Discovery Domain | ATM ADD defines a global discovery domain (DD) using the following BS EN 14908-1:2014 [1] 6-byte domain: (0x7A3340F1BCD2). All devices will always be configured in the DD. The DD is configured as a Clone domain so that subnet/node conflicts are not an issue. The key for the DD is the upper bytes of the OMA key (see cla... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 5.3 ADD Proxy Message | Each ATM ADD message has a header that allows the message to be sent through repeaters, even if those repeaters are not commissioned. This allows a DC to discover devices without first commissioning intervening devices. As such, all addressing is based on physical (Unique Node ID and broadcast) addressing. Each message... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 5.4 ATM Query ID | The ATM Query ID message is always sent using the ATM ADD mechanism, i.e. as payload preceded by the ADD header. This minimizes the different scenarios to one and it provides the target with the DC NID and the DC with the target NID. The format of the ATM Query ID is as follows: • BS EN 14908-1:2014 [1] message code: 0... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 5.5 ATM Respond to Query | Tells a device to respond or not respond further to ATM Query ID messages for a given session. Also, this message will give the device a repeat chain quality value to store for this DC. It is sufficient for the end device to store only the Unique Node ID and quality value for the DC with the best quality. The repeat ch... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 5.6 Signal Strength Values | SSI is a single byte and has the following format: • Margin value (bit 4..7). • Signal strength as encoded by transceiver, divided by 2 (bit 1..3). • One and only one bit (bit 0). Chain Quality is a two byte value and has the following format: • Hop count (1 byte): number of hops from the DC to the device. ETSI ETSI TS... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 5.7 Examples | Assume the following Unique Node IDs: • DC: N1. • OSGP Device 1: N2. • OSGP Device 2: N3. • OSGP Device 3: N4. The following APDUs would be used to send a request to Device 3 and have a response returned to the DC (values are in hex) using transaction number 01 and a path mask of 2 indicating that the second hop uses t... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 5.8 Fast Commission Message (FCM) | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 5.8.1 Overview | Because of the number of individual PLC messages that are required to commission an OSGP device there is a lot of PLC traffic involved to achieve a single function: Commissioning of a meter. This clause describes an enhancement to the way OSGP devices can be commissioned through the use of a single message. This messag... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 5.8.2 FCM message and response description | The FCM uses a specific BS EN 14908-1:2014 [1] type code (0x05). The FCM message is always encrypted and authenticated using the meter's current or original OMAK key - both are accepted. Table 1 Message field Data type Value Comments <code> UINT8 0x05 BS EN 14908-1:2014 [1] type code <FCM> LtFCM Fast Commission Message... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 6 OSGP Device data representation | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 6.1 General overview | OSGP uses a representation oriented model of a smart-grid device. The device data structures are presented and used in tabular form, and include binary encoded information elements. This data representation has been selected for its efficiency in terms of NVM requirements, as well as compactness for network data transf... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 6.2 Data Types | This clause provides definitions for the data types used in the Application Layer protocol and referenced in the table definitions. NOTE: All multiple-byte fields, such as UINT16, INT32, and FLOAT (excluding arrays) are ordered least significant byte (LSB) first. Table 4: Data Types Type Data Type Definition INTx (x= 8... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 6.3 Pending tables | Pending tables provide a way to synchronize configuration changes in multiple OSGP devices to a single moment in time. As a typical use case a utility may want to enact a new time-of-use calendar in all the meters in a particular region at precisely the same time, marking midnight of a new year or the day when a new la... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 6.4 Value Control Identifiers (VCI) | The VCI (Value Control Identifier) table column in the annexes show which entity has primary control over the value. The definitions for the VCI column are: • F = Fixed value. • M = OSGP Device controls value. OSGP agents should not attempt to write, or do not have write access to this field. • HD = Host Direct. OSPG a... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 6.5 Value | This field specifies the hard-coded value for fields marked "F" or the non-zero value in effect when the OSGP device is shipped. Fields with no value identified here are initialized to 0, but may have been be changed with provisioning. |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 6.6 Register Naming Convention | Throughout the present document, the per-phase measurement registers are denoted as follows: • A = Line 1 (for example 'A' Sag events). • B = Line 2 (for example Phase 'B' Loss). • C = Line 3 (for example RMS Current 'C'). • ABC = All phases in a polyphase OSGP device (for example Fwd Active Wh ABC). |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 6.7 Table and Procedure Naming Conventions | The following defines the letters preceding the table or procedure numbers in the present document. This naming convention is used in titles, and in references to tables/procedures in formulas and descriptions. • BT = Basic Table. For example, BT00, BT01, etc. • ET = Extended Table. For example, ET01, ET03, etc. • BP =... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 6.8 Interface Change Alarm (ICA NAK) | Modifying some OSGP device data tables or calling some OSGP device procedures described in the present document may cause the OSGP device data representation to change. In this case, the dimensions of some OSGP device tables may change and the Interface Change Alarm in BT03 shall be logged. In addition, the Interface D... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 7 Security | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 7.0 Foreword | Measures are included to protect the privacy of consumers by restricting access to data and encrypting such data to prevent access by other than authorized bodies. Measures are also included to detect attempts to circumvent metering functions such as might result in unrecorded access to utility services. The BS EN 1490... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 7.1 OMA Key (OMAK) | During the manufacturing process, OSGP devices are configured with a unique 96-bit OMA key. These keys are transmitted securely to the utility so they can be used by Data Concentrators. The original device-specific OMAK typically gets replaced by a shared OMAK by the Data Concentrator after is has discovered the new OS... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 7.2 OSGP-RC4-PSK Authentication | The OSGP data concentrator uses application level digest authentication to authenticate application level messages with the devices. This form of authentication requires half the packets that native BS EN 14908-1:2014 [1] authentication requires (no challenge). To avoid replay attacks, a sequence number is appended to ... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 7.3 OSGP-RC4-PSK Encryption | The data concentrator shall support encryption of some application layer messages sent between utility meters and the data concentrators using the stream cipher RC4. It shall discover whether a device requires encryption at the end of commissioning and at the switchover stage of a download. The Base Encryption Key (BEK... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 7.4 OSGP-AES-128-PSK Security Suite | As of this publication, OSGP supports two security suites: OSGP-RC4-PSK, which is the original suite used in OSGP v1, and OSGP-AES-128-PSK, which has been subsequently proposed. While both suites are supported by the meters, it is recommended that OSGP-AES-128-PSK be used. The OSGP-AES-128-PSK security suite provides a... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 7.5 Hardware Lock | In addition to the OMAK key and other security features provided by OSGP-AES-128-PSK and OSGP-RC4-PSK, the OSGP device may employ a hardware-integrated security mechanism that supersedes the key access permissions. The hardware locks may be table and procedure specific, and may apply only to certain tables (or parts of... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.1 General | Clauses 8.1 to 8.19 provide an overview of the primary functional areas of the device, and describe which tables and procedures should be used when configuring each functional area. This includes a number of which are at the manufacturer's or, where implemented by the device manufacturer, at the OSGP network operator's... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.2 Time-Of Use Calendar (Optional) | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.2.0 Foreword | Time-Of-Use (TOU) is the term used to describe the partitioning of energy usage into different registers based on a schedule. The device may support up to four such registers, called tariffs (T1, T2, T3 and T4). The tariffs may be selected for different time periods within a day (midnight to midnight - local time). The... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.2.1 Manual Override Options (optional) | The device may support the ability to override the currently active tariff and switch to another (user-specified) tariff manually. The tariff change can be configured to happen immediately as soon as the manual override occurs, or at a scheduled date/time at some point after the manual override is performed. The tariff... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.2.2 Over Power Threshold Tariff (optional) | The Over Power Threshold Tariff can be enabled or disabled. When enabled, whenever instantaneous power exceeds a pre-set power threshold over a pre-set time threshold the active tariff is forced to a configured tariff. When this occurs, it supersedes any other tariff control including TOU tariff control, calendar overr... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.3 Clock Adjustment (mandatory) | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.3.1 Absolute Time Synch | BP10 is used to set the date and time of the device at the factory. When calling this procedure. UTC time shall be passed in as a parameter. The device will then directly overwrite the current clock and calendar setting with the input UTC time. Since adjusting the clock using BP10 may affect the Load Profile and TOU mo... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.3.2 Clock Adjustment by Delta | The recommended method to modify the device's clock during normal operation is to use EP16. There are two ways to modify the device time through EP16. The first method is to send the time delta in seconds directly, which requires first reading the device clock and comparing to a reference clock. This procedure will acc... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.4 Billing Functions | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.4.1 Self-Reads (mandatory) | "Self-read" is the term used to describe the automatic, periodic storage of measurement data to a separate area of memory that can be read for billing purposes. Self-reads provide a mechanism for all meters with the same self-read schedule to record billing data at the same time of day. An OSGP device shall be capable ... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.4.2 Total Energy (optional) | The device may also store the day's consumption for all of the total energy measurements (excluding tariff registers). This storage occurs at UTC midnight and contains only the previous day's energy consumption. This snapshot of total energy may be used by a host system to determine total usage of the secondary side of... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.4.3 On-Demand Reads of Current Billing Register Values (mandatory) | BT23 can be read at any time to get the current billing register values. However, if BT23 is read using multiple partial reads, there is no guarantee of consistency of the data. Therefore, the transaction table (ET27) should be used to perform on-demand reads. |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.5 Load Profile (mandatory) | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.5.0 Foreword | Load profiling is the periodic storage of interval measurement(s). Load profile data and configuration can be found in BT61 "Actual Load Profile," BT62 "Load Profile Control," BT63 "Load Profile Status" and BT64 "Load Profile Data". All the pertinent configuration and dimension information required for interpreting loa... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.5.1 Use case: Reading Load Profile Data | To read the most recently recorded load profile data in the OSGP device, follow these steps: 1) Read and store BT61 or ET42 for the present load profile configuration, including the number of blocks (days) with available data, the number of intervals recorded in each block, the number of channels (registers) being logg... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.5.2 Use case: Parsing M-Bus Load Profile Data | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.5.2.0 Foreword | The OSGP device load profile data can be parsed to extract and interpret M-Bus data. • The device shall generate alerts when new M-Bus information is available for either control valve status or load profile if the "M-Bus Alerts" field in ET50 (ET50.30.2) is set to 1. • For general information on M-Bus devices, see cla... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.5.2.1 M-Bus Data Types and ET57 | The previous clause on reading load profile data describes how to determine which source IDs correspond to all the configured load profile channels. Typically, only a subset of the channels will correspond to M-Bus device data. M-Bus source IDs will all be extended source ids of the following format in ET42: • Bits 15.... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.5.2.2 Load Profile Poll Rate | The load profile poll rate is configured via ET34. This determines how often M-Bus devices will be read for load profile purposes. A value of 0 means there is no limit on the polling, and the poll rate is determined by the load profile interval duration. This is an approximation, as M-Bus reads may not occur at an exac... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.5.2.3 Time Stamping | There are two possible behaviours of the M-Bus device. One is that the device returns instantaneous values, and the other is that it returns an hourly read. In the latter case, the hourly read should be accompanied by a time stamp. If it is, then the OSGP device will check the time stamp to make sure it is current. The... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.5.3 Load Profile Unread Entries Alarm | An alarm defined in BT03 indicates that at least one complete unread block is available. Note that the device shall increment the unread count as soon as any valid intervals are placed into a block. The flag shall not be set until the block is complete (all intervals are set or the next block has been created, e.g. due... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.6 Self-Test (Alarms, Error Codes) (optional) | The device may periodically perform self tests and setflags to indicate when alarm conditions are detected. Self tests will not clear any alarms if the alarm condition no longer persists. It is the responsibility of the Data Concentrator (or other mechanism e.g. optical reader) to clear the necessary alarms. BT03 conta... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.7 Pulse Inputs (optional) | The device can collect pulse data from pulse output devices, such as gas and water meters, and transmit the collected data to the Data Concentrator. Tamper alarm monitoring for each pulse output device is also included. Pulse data collection is an optional item. Pulse input data collected from channel one and channel t... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.8 Power Quality (optional) | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.8.1 Functional Description | The device may monitor various parameters for power quality. All power quality recordings are stored in ET09 unless stated otherwise below. Power quality events can be read by the Data Concentrator, and can also be read directly from the OSGP device via the optical port. When a power quality event occurs, the status sh... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.9 Display (optional) | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.9.0 Foreword | 8. |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 9.0 Foreword | Each device may contain display with several programmable features. A device with a display can display up to 30 numeric value items, which are chosen from data sources including the available total and tariff energy measurements, as well as time, date, and prepay energy credit remaining. The display scrolls through ea... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.9.1 Display Sources List (optional) | BT33 defines the items to be included in the present display list by source number and category. The 2-byte display list source number consists of a high byte and low byte. The high byte indicates the display list category. The low byte indicates the measurement source number. The following is a list of categories (hig... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.9.2 Display Configuration (optional) | ET07 allows the user to define how the items in the display list will be displayed, including the ID code, the number of digits to display, whether leading zeros will be displayed or not, the active and inactive features indicated by the name plate, and the decimal point configuration associated with each item on the d... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.