Version 1: Release Note 28 November 2014


Component Requirements – Join



Download 4.8 Mb.
Page194/258
Date03.04.2021
Size4.8 Mb.
1   ...   190   191   192   193   194   195   196   197   ...   258

Component Requirements – Join

  1. Join Command and Response payloads – structure definition

Each instance of @JoinDevice.CommandPayload and of @JoinDevice.ResponsePayload shall be an octet string containing the DER encoding of the populated structure defined in this Section 13.7.4.5.1 which specifies the structure in ASN.1 notation.

JoinDevice DEFINITIONS ::= BEGIN

CommandPayload ::= SEQUENCE

{

-- specify which type of joining is being authorised and,



-- for Method A Joins, the role the Device is to play

joinMethodAndRole JoinMethodAndRole,

-- specify the Entity Identifier of the Device which is to be Joined with

otherDeviceEntityIdentifier OCTET STRING,

-- specify the DeviceType of that other Device

otherDeviceType DeviceType,

-- provide the other Device’s Key Agreement certificate, if and only if this

-- is a join between a gSME and a type1PrepaymentInterfaceDevice.

-- Certificate shall be as defined in IETF RFC 5912

otherDeviceCertificate Certificate OPTIONAL

}

-- detail whether the Command successful executed or, if it didn’t,



-- what the failure reason was

ResponsePayload ::= JoinResponseCode

JoinMethodAndRole ::= INTEGER

{

-- methodB is to be used where the other Device is a Type 2 Device or GPF.



-- methodC is used where the Devices involved are a GSME and a PPMID.

-- methodA is used otherwise.

-- methodAInitiator is used where the Device this Command is targeted at

-- should initiate the Key Agreement process

-- methodAResponder is used where the Device this Command is targeted at

-- should respond in the Key Agreement process, but shall not initiate it

methodAInitiator (0),

methodAResponder (1),

methodB (2),

methodC (3)

}

DeviceType ::= INTEGER



{

gSME (0),

eSME (1),

communicationsHubCommunicationsHubFunction (2),

communicationsHubGasProxyFunction (3),

type1HANConnectedAuxiliaryLoadControlSwitch (4),

type1PrepaymentInterfaceDevice (5),

type2 (6)

}

JoinResponseCode::= INTEGER



{

success (0),

invalidMessageCodeForJoinMethodAndRole (1),

invalidJoinMethodAndRole (2),

incompatibleWithExistingEntry (3),

deviceLogFull (4),

writeFailure (5),

keyAgreementNoResources (6),

keyAgreementUnknownIssuer (7),

keyAgreementUnsupportedSuite (8),

keyAgreementBadMessage (9),

keyAgreementBadKeyConfirm (10),

invalidOrMissingCertificate (11)

}

END


          1. Constructing the @JoinDevice.CommandPayload and of @JoinDevice.ResponsePayload

@JoinDevice.CommandPayload shall have the structure defined in Section 13.7.4.5.1, and the Remote Party constructing the Command shall populate with values according to Table 13.7.4.5.2a.


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   ...   190   191   192   193   194   195   196   197   ...   258




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

    Main page