Version 1: Release Note 28 November 2014


Annex 1 – Additional DLMS Class



Download 4.8 Mb.
Page248/258
Date03.04.2021
Size4.8 Mb.
1   ...   244   245   246   247   248   249   250   251   ...   258

Annex 1 – Additional DLMS Class


The class described below shall be supported by ESME. Extended Data (class_id: 9000 version: 0)

Attribute(s)

Data type

Min.

Max.

Def.

1.

logical_name

(static)

octet-string[6]










2.

value_active

(dyn.)

CHOICE










3.

scaler_unit_active

(dyn.)

scal_unit_type










4.

value_passive

(static)

CHOICE










5.

scaler_unit_passive

(static)

scal_unit_type










6.

activate_passive_value_time

(static)

octet-string










Methods(s)

Data type




1.

reset(data)

Integer




2.

activate_passive_value(data)

integer



    1. Attribute description


      logical_name

      Identifies the ‘Data’ object instance

      value_active

      Contains the data.

      CHOICE

      {

      -- simple data types



      null-data [0],

      Boolean [3],

      bit-string [4],

      double-long [5],

      double-long-unsigned [6],

      octet-string [9],

      visible-string [10],

      UTF8-string [12],

      Bcd [13],

      integer [15],

      long [16],

      unsigned [17],

      long-unsigned [18],

      long64 [20],

      long64-unsigned [21],

      enum [22],

      float32 [23],

      float64 [24],

      date-time [25],

      date [26],

      time [27],

      -- complex data types

      array [1],

      structure [2],

      compact-array [19]

      }


      The data type depends on the instantiation defined by the ‘logical name’. It has to be chosen so, that together with the logical name, an unambiguous interpretation is possible.

      scaler_unit_active

      Provides information on the unit and the scalar for the value.

      scal_unit_type: structure

      {

      scalar,


      unit

      }

      scalar: integer



      This is the exponent (to the base of 10) of the multiplication factor

      unit: enum

      Enumeration defining the physical unit; for more information check the Blue Book


      value_passive

      Contains the data.

      CHOICE

      {

      -- simple data types



      null-data [0],

      Boolean [3],

      bit-string [4],

      double-long [5],

      double-long-unsigned [6],

      octet-string [9],

      visible-string [10],

      UTF8-string [12],

      Bcd [13],

      integer [15],

      long [16],

      unsigned [17],

      long-unsigned [18],

      long64 [20],

      long64-unsigned [21],

      enum [22],

      float32 [23],

      float64 [24],

      date-time [25],

      date [26],

      time [27],

      -- complex data types

      array [1],

      structure [2],

      compact-array [19]

      }

      The data type depends on the instantiation defined by the ‘logical name’. It has to be chosen so, that together with the logical name, an unambiguous interpretation is possible.






      scaler_unit_passive

      Provides information on the unit and the scalar for the value.

      scal_unit_type: structure

      {

      scalar,


      unit

      }

      scalar: integer



      This is the exponent (to the base of 10) of the multiplication factor

      unit: enum

      Enumeration defining the physical unit; for more information check the Blue Book


      activate_passive_value_time

      Defines the time when the object itself calls the specific method activate_passive_value. A definition with ‘not specified’ notation in all fields of the attribute will deactivate this automatic activation. Partial ‘not specified’ notation in just some fields of date and time is not allowed.

      octet-string, formatted as set in 4.1.6.1 for date_time of the Blue DLMS Book


    2. Method description


      Reset

      This method forces a reset of the object. By invoking this method, the value is set to the default value. The default value is an instance specific constant.

      data ::= integer(0)



      activate_passive_value

      This method copies all attributes called …_passive to the corresponding attributes called …_active.

      data ::= integer(0)


  1. Annex 2 - Counters and their use in transaction identification and Protection Against Replay protection - informative


Table 23 provides a summary of the Counters used in GB Smart Metering and outlines the purpose each serves in providing transaction identity, traceability and Protection Against Replay protection. These are fully detailed in Section 4.3.1 and Section 14 and are provided here as a review aid only.

Name

Description

Purpose

Impact on Device

[Remote Party] Originator Counter


The KRP or the ACB’s Originator Counter.

Originator Counters are always strictly numerically greater than any previous Originator Counter from that Message originator to the targeted Device.

Originator Counters shall not use the UTRN reserved range unless as part of a Prepayment Top Up Command. Remote Parties may choose to increment a UTRN Originator Counter separately from other Originator Counters.


The Originator Counter provides a unique Message identity (in combination with CRA Flag, sender id and recipient id).

The Originator Counter is also used as an input value for symmetric Key Derivation Functions.

The Originator Counter is used for Protection Against Replay protection.


The highest accepted value is stored as the Execution Counter or in the UTRN Counter cache as appropriate.

[Device] Originator Counter


A Device’s Originator Counter

This must be strictly numerically greater than any previous Originator Counter from that Device.



The Originator Counter provides a unique Message Identity (in combination with CRA Flag, sender id and recipient id)

The Originator Counter is also used as an input value for symmetric Key Derivation Functions.



The Device shall ensure that the value it generates (e.g. for Alerts) is strictly numerically greater than any previous Originator Counter value or Supplementary Originator Counter value it has placed in any previous Message it has generated.

Supplementary Remote Party Counter

The Originator Counter (or reference) of an Unknown Remote Party requesting the service from the ACB.

The Supplementary Remote Party Counter supports Message identification of Responses by the URP as the originator of the service request associated to the Command.

The Supplementary Remote Party Counter is incorporated into the corresponding Response by the Device.

The Response also contains the Originator Counter of the ACB



Supplementary Originator Counter

The Supplementary Originator Counter is a Device generated number which is strictly numerically greater than any previous Supplementary Originator Counter or Originator Counter placed in previous Messages by the Device). This is used in response to Commands as specified in Section 4.3.1.4 (URP accessible Commands where the response contains sensitive values).

The Supplementary Originator Counter is used in a Response to a Command from an URP for the generation of symmetric keys for use in MAC creation and Encryption of sensitive values.

The Device shall ensure that the value it generates (e.g. for Alerts) is strictly numerically greater than any previous Originator Counter or Supplementary Originator Counter values it has used in any previous Message.

The Supplementary Originator Counter may be the same as Originator Counter in any given Message but this is an implementation decision).



Execution Counter

The Execution Counter is the last accepted Originator Counter value for commands requiring Protection Against Replay and which cannot be future dated. It is stored by the Device for each Remote Party/Command combination.

Note that only the Supplier (or for CHF the WAN Provider) can send Commands that require Protection Against Replay with the exception of the Update Security Credentials Command which can be sent by multiple roles.



The Execution Counter is used to support Protection Against Replay of Commands for immediate execution.

Where Commands are protected from Protection Against Replay then Devices will reject Commands where the Originator Counter in the Command not greater than the existing value of the Execution Counter stored on the Device.



Each Device will store an Execution Counter value for each KRP/Command- type combination.



UTRN Counter

The UTRN Counter is detailed separately in Section 14 but a summary is included here for completeness.

The UTRN Counter must be strictly greater by one than the highest previous UTRN Counter issued for the target Device by the KRP

The UTRN Counter comprises the 32 most significant bits of the Originator Counter (this is a reserved range of Originator Counters where the least significant 32 bits are set to 0) which is included in a Pre-payment Top-Up Command (whether entered locally or received over the WAN).

The Device checks:



  • that the UTRN Counter contained within a UTRN is greater than the lowest value in the UTRN Counter cache held on the Device. This ensures that a limited number of UTRNs can be executed out of sequence); and

  • that the UTRN Counter is not equal to any value currently held in the UTRN Counter cache, i.e. that the Pre-payment Command has not be accepted before.

The UTRN Counter provides a specific Protection Against Replay mechanism for pre-pay

Where the Command is received over the WAN, the Originator Counter (and therefore the UTRN Counter) is as contained in the WAN Prepayment Top Up Command.

If the UTRN Counter contained within a prepayment Command (whether entered locally or received over the WAN) is already in the UTRN Counter Cache or is less than the lowest value in the UTRN Counter Cache on the Device, then Devices will reject the UTRN.


Each ESME and GSME must maintain a UTRN Counter Cache as an array of the last 100 UTRN Counter entries. Where the array is full, the numerically lowest value in the array is overwritten.



PTUT Truncated Originator Counter

The PTUT Truncated Originator Counter is detailed separately in Section 14 but a summary is included here for completeness.

This is the UTRN Counter as carried in the locally entered 20 digit UTRN. It is the 10 least significant bits of the UTRN Counter, which is itself the 32 most significant bits of the Originator Counter for the Command.

The PTUT truncated counter is not processed in WAN received top-up commands.


The PTUT Truncated Originator provides a means for a Device to derive the Originator Counter (and therefore the UTRN Counter) for the Prepayment Top Up Command when it is entered locally (as a numeric 20 digit code).

In order to determine the UTRN Counter, the Device uses the algorithm defined in Section 14.6.



There is no additional impact to the Device as the same UTRN Counter cache is used as for the UTRN Counter.

Remote Party Floor Sequence Numbers

64-bit values carried in Update Security Credentials Command, in:

  • newRemotePartyFloorSeqNumber attribute;

  • otherRemotePartyFloorSeqNumber sequence;

  • newRemotePartySpecialistFloorSeqNumber attribute; and

  • otherRemotePartySpecialistFloorSeqNumber sequence;

The values are used to set Counters associated with the credential being updated to new values. Processing is as detailed in Section 13.3.5.10.

Remote Party Floor Sequence Numbers are of two types:

  • Remote Party Sequence Numbers. Values used to set Execution Counters on a change of a Remote Party’s digital signing credential with which the counter is associated; and

  • Remote Party Specialist Sequence Numbers. Value is used to populate UTRN Counter cache following its clearance on change of the Supplier Key Agreement Prepayment credential.

Both types have a ‘new’ and ‘other’ variant. ‘new’ is used when the authorising remote party is changing its own credentials (e.g. supplier changing its own digital signing credential).

‘other’ is used when the authorising remote party is changing the credentials of another remote party (e.g. TCoS changing supplier’s credentials).

Where – and only where - the Update Credentials Command changes the supplier entity ID (or indicates change of supplier), Counters are always reset – either to the Remote Party Sequence number indicated or to zero where the attribute is absent . Otherwise, Counters are only reset where the Remote Party Sequence Number is present.





Encryption Originator Counter

The Counter value used for the purposes of encryption (see Section 8.3) for Responses and Alerts sent from the Device. 

This is either the Supplementary Originator Counter in the case that this is to be included in the message (e.g. for an Unknown Remote Party) or the [Device] Originator Counter in all other instances.

The Device re-uses either the Supplementary Originator Counter or [Device] Originator Counter.

Table 23: Counters and their use in transaction identification and Protection Against Replay protection

  1. Directory: government -> uploads -> system -> uploads -> attachment data -> file
    file -> Remove this if sending to pagerunnerr Page Title Light Rail Security Recommended Best Practice
    file -> 8 Section 1 : Sport
    file -> Notice of exercise of additional powers of seizure under Sections 50 or 51 of the Criminal Justice and Police Act 2001
    file -> Home office circular 004/2014 Powers to search for and seize invalid travel documents in Schedule 8 to the Anti-social Behaviour, Crime and Policing Act 2014
    file -> Consultation on the Royal Parks and Other Open Spaces (Amendment) (No. 2) Regulations 2012
    file -> Crown copyright 2012
    file -> This is the Report to Government by the Film Policy Review Panel The brief
    file -> Impact Assessment (IA)
    file -> Dcms/Wolfson Museums and Galleries Improvement Fund a public-Private Partnership (2002-2010)


    Share with your friends:
1   ...   244   245   246   247   248   249   250   251   ...   258




The database is protected by copyright ©essaydocs.org 2020
send message

    Main page