Version 1: Release Note 28 November 2014



Download 4.8 Mb.
Page12/258
Date03.04.2021
Size4.8 Mb.
1   ...   8   9   10   11   12   13   14   15   ...   258

Scope


This Section 3.2 lays out the scope of the GBCS and introduces definitions relied upon in this GBCS.

A Message shall be of one the following:



  • a Command;

  • a Response to a Command;

  • an Alert; or

  • an information provision transaction (HAN Only Message).

A Message instance shall be an instance of one of the Messages detailed in this GBCS.

The Device Specifications define the minimum functional capabilities required of Devices.

Except where those functional capabilities are internal to the Devices or are accessed via the Device’s User Interfaces, the minimum functional capabilities shall be invoked by, and / or result in, Messages being passed via the Devices’ Network Interfaces.

The GBCS is the technical specification, sufficient for the creation by the originator(s) and processing by the target(s), of each Message, where the Message is required in order to implement minimum functionality defined in the Device Specifications.

Specifically, the GBCS details the format, structure and associated processing for each of the Messages required to implement the Device Specifications’ minimum functionality.

There are two classifications of Message:



  • HAN Only Message4, where both the original sender and ultimate recipient are Devices within the same Smart Metering Home Area Network (SMHAN); and

  • Remote Party Message, where either the original sender or the ultimate recipient is not a Device.

A Remote Party Message shall only be of one of the following:

  • a Command;

  • a Response to a Command; or

  • an Alert.

Each Remote Party Message shall have a unique Message Code, which shall be as specified in Section 15.

Where a Remote Party is known to a Device by way of that Remote Party’s Security Credentials being stored on the Device (as specified in Section 4.3.2.5), the Remote Party is referred to as a Known Remote Party (KRP). Otherwise, it is referred to as an Unknown Remote Party (URP).

Commands requiring a Response to an Unknown Remote Party shall always be sent to the Device by the Device’s Access Control Broker (see Section 4.3.2.5).

For clarity, Type 2 Devices shall not be required to support any Remote Party Messages. Thus, provisions in this GBCS in relation to Remote Party Messages shall not apply to Type 2 Devices.

Remote Parties and Devices are collectively referred to in this GBCS as Smart Metering Entities.


    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   ...   8   9   10   11   12   13   14   15   ...   258




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

    Main page