Version 1: Release Note 28 November 2014


Input to the ECDSA calculation



Download 4.8 Mb.
Page73/258
Date03.04.2021
Size4.8 Mb.
1   ...   69   70   71   72   73   74   75   76   ...   258
Input to the ECDSA calculation

xDLMS Message Elements

Contents

Length (octets)

Note

No

General-Signing

0xDF

1

xDLMS APDU tag for General-Signing (223 in decimal)




transaction-id










No

length

0x09

1

Length of Originator Counter plus 1

Yes

value

CRA Flag || Originator Counter



9

CRA Flag shall be:

0x01 for Commands

0x02 for Responses

0x03 for Alerts






originator-system-title










No

length

0x08

1

Length of Entity Identifier

Yes

value

Business Originator ID

8







recipient-system-title










No

length

0x08

1

Length of Entity Identifier

Yes

value

Business Target ID

8







date-time










No

length

0x00 where no date / time is required in this Message
0x0C where a date / time field is required

1


Where date-time is not required for a Message, it shall be a 0 octet string as per the DLMS specification

Where date-time is required for a Message, it shall be a 12 octet string as per the DLMS specification. See ‘date-timestamp in response’ column, ‘Use Case reference’ tab in Mapping Table



Yes

value

Either empty or a 12 character octet-string containing the date-time stamp for this Response

0 or 12







other-information










No

length

Encoding(X)

variable

Len(Encoding(X))



X is length of other information octet string. X is 2 or 18 or 26 or variable

Yes

value

Message Code || Supplementary Remote Party ID || Supplementary Remote Party Counter || Supplementary Originator Counter || Supplementary Remote Party Key Agreement Certificate

2 or 18 or 26 or variable

The Message Code shall always be present

In an Alert, Supplementary Remote Party ID shall be present, if it is required by Section 16

In a Command or Response, the Supplementary Remote Party ID, Supplementary Remote Party Counter and Supplementary Originator Counter, shall be present or not in line with the requirements of Section 4.3.1.4

Supplementary Remote Party Key Agreement Certificate shall only be present where (1) this is a Command, (2) the Response to it should contain encrypted attributes and (3) the Supplementary Remote Party ID is for a Remote Party which does not already have a Key Agreement Public Key on the Device. It may only be present in Commands marked as allowing it in the column ‘Key Agreement Certificate Potentially in Command?’ of the Use Case reference tab of the Mapping Table






Content










No

length

Encoding(X)

Len(Encoding(X))

X is the length in octets of the Message Payload

Table 7.2.7: Required components of Grouping Header
      1. Message Construction – ASN.1 Security Payloads


For Messages containing ASN.1 Security Payloads, the Payloads shall be constructed as detailed in the Use Case for that Message Code (as defined by the Mapping Table).
      1. Message Construction – DLMS COSEM Payloads


For Messages containing DLMS COSEM payloads (as defined by the Message Code and Use Cases in Section 19):

  • any Command Payload shall comply with the requirements of Table 7.2.9a and the associated Use Case;

  • any Response Payload shall comply with the requirements of Table 7.2.9b and the associated Use Case; and

  • any Alert Payload shall comply with the requirements of Table 7.2.9c and the associated Use Case.

DLMS COSEM Payloads – Commands

No

xDLMS Message Elements

Contents

Length (octets)

Note




access-request

0xD9

1

xDLMS APDU tag for Access Request (217 in decimal)




long-invoke-id-and-priority

0x20 || Least significant 24 bits of Originator Counter

4

Construction explained in rows below detailing bit (31..0) usage




(bits 0-23) invoke-id


Least significant 24 bits of Originator Counter










(bits 24 -27) reserved

0b0000




Fixed value




(bit 28) self-descriptive

0b0




Not-Self-Descriptive




(bit 29) processing-option

0b1




Break on Error




(bit 30) service-class

0b0




Unconfirmed




(bit 31) priority

0b0




Normal




date-time

0x00

1

A value for this element is not present so the length field is 0x00




access-request-body













access-request-specification










1

SEQUENCE OF

Use Case specific

1

The total number of gets, sets and actions in the Use Case (means that there will be less than 128 in total). This content is specified in each DLMS COSEM Use Case

2

Use Case Specific Content

Use Case specific




The list of Gets, Sets and Actions specific to the Use Case. This content is specified in each DLMS COSEM Use Case




access-request-list-of-data













list-of-data










3

SEQUENCE OF Data

Use Case specific

1

The total number of attributes in the list-of-data in the Use Case (means that there will be less than 128 in total). This content is specified in each DLMS COSEM Use Case

4

Use Case Specific Content

Use Case specific

Use Case set

Values of the attributes required by the Use Case. This content is specified in each DLMS COSEM Use Case

Table 7.2.9a: Required components of Command Payload

Elements marked in Table 7.2.9a as Use Case specific shall be populated according to the Use Case for the Message Code (see Section 19).



DLMS COSEM Payloads – Responses

No

xDLMS Message Elements

Contents

Length (octets)

Note




access-response

0xDA

1

xDLMS APDU tag for Access Response (218 in decimal)




long-invoke-id-and-priority

0x20 || Least significant 24 bits of Originator Counter

4







date-time

0x00

1

A value for this element is not needed so the length field is 0x00




access-response-body













access-request -specification OPTIONAL

0x00

1

Not present so false (0x00)




access-response-list-of-data













list-of-data










5

SEQUENCE OF Data

Use Case specific

1

The total number of attributes in the Response in the Use Case. This content is specified in each DLMS COSEM Use Case

6

Use Case Specific Content

Use Case specific

Use Case set

Values of the attributes required by the Use Case. This content is specified in each DLMS COSEM Use Case




access-response-specification










7

SEQUENCE OF CHOICE

Use Case specific

1

The total number of responses, including the 1 here and those in the Use Case

8

Use Case Specific Content

Use Case specific

Use Case set

Fields stating the result of each Gets, Sets and Actions specific to the Use Case.

Table 7.2.9b: Required components of Response Payload

Elements marked in Table 7.2.9b as Use Case specific shall be populated according to the Use Case for the Message Code (see Section 19).



DLMS COSEM Payloads – Alerts

No

xDLMS Message Elements

Contents

Length (octets)

Note




data-notification

0x0F

1

xDLMS APDU tag for data-notification (15 in decimal)




long-invoke-id-and-priority

0x20 || least significant 24 bits of Originator Counter

4







date-time

0x00

1

A value for this element is not needed so the length field is 0x00




notification-body













structure

0x02

1




1

SEQUENCE OF Data

0x02 unless there is Use Case specific data additional

1

The majority of Alerts do not contain any additional data. For Alerts without additional data, there is no corresponding Use Case (since there is no Use Case specific content).

Where an Alert does contain additional content, it has a specific Use Case. The additional content is specified in each such Use Case. In such cases, this field shall contain the total number of Data in the Use Case sequence plus the one in this template




Data













Tag

0x12

1

Tag for LONG UNSIGNED




Value

Alert Code

2

The Alert Code for this Alert, shall be as defined in Section 16




Data













Tag

0x09

1

Tag for octet-string




Length

0x0C

1

Twelve characters long as DLMS date times are octet-string(12)




Value

Time Stamp

12

The time stamp for this Alert, shall be as defined in Section 16

2

Use Case Specific Additional Content

Use Case specific

Use Case

See Note at row 1, which means that, for most Alerts, there will be no Use Case specific content.

Table 7.2.9c: Required components of Alert Payload

Elements marked in Table 7.2.9c as Use Case specific shall be populated according to the Use Case for the Message Code (see Section 19).



      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   ...   69   70   71   72   73   74   75   76   ...   258




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

    Main page