Version 1: Release Note 28 November 2014



Download 4.8 Mb.
Page75/258
Date03.04.2021
Size4.8 Mb.
1   ...   71   72   73   74   75   76   77   78   ...   258
GBZ Payloads – Commands

No

Message Elements

Contents

Length (octets)

Note




Profile ID

0x0109

2

ZSE

1

Total number of GBZ Use Case Specific Component(s)

See ‘Note’ column

1

This octet is to be interpreted as an 8 bit unsigned integer specifying the total number of GBZ Use Case Specific Component(s)

2

GBZ Use Case Specific Component(s)

Use Case specific




See Tables 7.2.10d and 7.2.10e

Table 7.2.10a: Required components of GBZ Command Payload

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



GBZ Payloads – Response

No

Message Elements

Contents

Length (octets)

Note




Profile ID

0x0109

2

ZSE

1

Total number of GBZ Use Case Specific Component(s)

See ‘Note’ column

1

This octet is to be interpreted as an 8 bit unsigned integer specifying the total number of GBZ Use Case Specific Component(s) in this Message

2

GBZ Use Case Specific Component(s)

Use Case specific




See Tables 7.2.10d and 7.2.10e

Table 7.2.10b: Required components of GBZ Response Payload

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



GBZ Payloads – Alerts

No

Message Elements

Contents

Length (octets)

Note




Profile ID

0x0109

2

ZSE

1

Total number of GBZ Use Case Specific Component(s)

See ‘Note’ column

1

This octet is to be interpreted as an 8 bit unsigned integer specifying the total number of GBZ Use Case Specific Component(s)




Alert Code

See ‘Note’ column

2

The Alert Code for this Alert as defined in Section 16




Timestamp

UTCTime

4

The UTCTime, with its ZCL meaning, at which this Alert was created

2

GBZ Use Case Specific Component(s)

Use Case specific




See Tables 7.2.10d and 7.2.10e

Table 7.2.10c: Required components of GBZ Alert Payload

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



GBZ Use Case Specific Component without encrypted content

No

Message Elements

Contents

Length (octets)

Note




Extended Header Control Field

0x00, 0x10, 0x11Or

0x01



1

Most significant nibble:

0x0 if ‘From Date Time’ not present;

or

0x1 if ‘From Date Time’ present


Least significant nibble:

0x0 (if not the last GBZ Use Case Specific Component in this Message)



Or

0x1 (if the last GBZ Use Case Specific Component in this Message)






Extended Header Cluster ID

See ‘Note’ column

2

The Cluster ID of the ZSE / ZCL command contained in this GBZ Use Case Specific Component




Extended Header GBZ Command Length

See ‘Note’ column

2

These two octets shall be interpreted as a 16 bit unsigned integer specifying the total length on octets of the remainder of this GBZ Component (so excluding this and prior fields)




From Date Time

See ‘Note’ column

4

The earliest date-time of any entry that can be returned in the response, specified as a ZigBee UTCTime.




ZCL header

Use Case specific

3

These fields shall have the meaning specified in the ZSE / ZCL Specifications except for the Transaction Sequence Number. The Transaction Sequence Number shall be set to 0 for the first request-style ZSE / ZCL command in the Message and shall be incremented by one for every subsequent request-style ZSE / ZCL command frame in the Message. The corresponding response-style ZSE / ZCL command frame shall copy the Transaction Sequence Number from the request-style ZSE / ZCL command frame




ZCL payload

Use Case specific

Variable

These fields shall have the meaning specified in the ZSE / ZCL specifications

Table 7.2.10d: Required components of GBZ Use Case Specific Component without encrypted content


GBZ Use Case Specific Component with encrypted content

No

Message Elements

Contents

Length (octets)

Note




Extended Header Control Field

0x02

Or

0x03




1

0x02 (if not the last GBZ Use Case Specific Component in this Message)

Or

0x03 (if the last GBZ Use Case Specific Component in this Message)






Extended Header Cluster ID

See ‘Note’ column

2

The Cluster ID of the ZCL Command contained in this GBZ Use Case Specific Component




Extended Header GBZ Command Length

See ‘Note’ column

2

These two octets shall be interpreted as a 16 bit unsigned integer specifying the total length in octets of the remainder of this GBZ Component (so excluding this and prior fields but including the 2 octets of Additional Header)




Additional Header Control

0x00

1

Reserved for future extensibility




Additional Header Frame Counter

See ‘Note’ column

1

This octet is to be interpreted as an 8 bit unsigned integer. Its value shall be 0x00 for the first GBZ Use Case Specific Component with encrypted content in a Message. The value shall increase by one in each subsequent GBZ Use Case Specific Component with encrypted content in a Message




ZCL header

See ‘Note’ column

3

These fields shall have the meaning specified in the ZigBee Cluster Library




Length of Ciphered Information

See ‘Note’ column

2

These two octets shall be interpreted as a 16 bit unsigned integer specifying the total length in octets of the Ciphered Information




Ciphered Information

See ‘Note’ column

Variable

See Section 8.4

Table 7.2.10e: Required components of GBZ Use Case Specific Component with encrypted content
      1. Transfer of Large Remote Party Messages


All Devices which are not Type 2 Devices shall be capable of supporting the General Block Transfer (GBT) requirements of this Section 7.2.11.
        1. GBT Terminology and Parameters18


A GBT Message shall be an APDU constructed and processed as defined by this Section 7.2.11.

A GBT Message Series shall be the set of GBT Messages needed to exchange one complete Remote Party Message between a GBT Initiator and a GBT Recipient.

For a Remote Party Command sent using a GBT Message Series, the GBT Initiator shall be the Access Control Broker and the GBT Recipient shall be the target Device.

For a Remote Party Response or a Remote Party Alert sent using a GBT Message Series, the GBT Initiator shall be the sending Device and the GBT Recipient shall be the Access Control Broker.

A GBT Third Party shall be the Remote Party identified by:


  • in a Remote Party Command, the value in the Business Originator ID field; and

  • in a Remote Party Response or a Remote Party Alert, the value in the Business Target ID field.

GBT Streaming Window shall be the number of GBT Messages the GBT Initiator sends without receipt of a GBT Message (Acknowledgement), or since receipt of the most recent GBT Message (Acknowledgement).

GBT Streaming Window shall be:



  • 63 where the GBT Message Series carries a Remote Party Response;

  • 6 where the GBT Message Series carries a Remote Party Command; or

  • the number of GBT Messages the sender wishes to be resent in response to a GBT Message (Request Block Resend).

Maximum PDU Size shall be 1200 octets.

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




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

    Main page