Version 1: Release Note 28 November 2014


Mandatory, OPTIONAL or DEFAULT value



Download 4.8 Mb.
Page172/258
Date03.04.2021
Size4.8 Mb.
1   ...   168   169   170   171   172   173   174   175   ...   258
Mandatory, OPTIONAL or DEFAULT value

Notes

executionOutcome

SEQUENCE










authorisingRemotePartySeqNumber

INTEGER

Originator Counter of Remote Party authorising the Command, as specified in the corresponding Command

Mandatory

This is to allow the Alert to be linked to the Command that caused execution

credentialsReplacementMode

INTEGER

rootBySupplier (0) ,

rootByWanProvider (1) ,

supplierBySupplier (2) ,

networkOperatorByNetworkOperator (3) ,

accessControlBrokerByACB (4) ,

wanProviderByWanProvider (5) ,

transCoSByTransCoS (6) ,

supplierByTransCoS (7) ,

anyExceptAbnormalRootByRecovery (8) ,

anyByContingency (9)} ,




Mandatory

Provide details of the corresponding Command that are not in the standard GBCS message header. Specifically the mode in which the Command was invoked

remotePartySeqNumberChanges

SEQUENCE OF




OPTIONAL

The resulting changes to any replay counters held on the Device

SEQUENCE













otherRemotePartyRole

INTEGER

root (0) ,

recovery (1) ,

supplier (2) ,

networkOperator (3) ,

accessControlBroker (4) ,

transitionalCoS (5) ,

wanProvider (6) ,


Mandatory if SEQUENCE is present

The role which has had its counter values changed on the Device

otherRemotePartyFloorSeqNumber

INTEGER

The corresponding Counter value

Mandatory if SEQUENCE is present




newRemotePartySpecialistFloorSeqNumber

SEQUENCE OF




OPTIONAL

Only present where Remote Party Role is supplier

SEQUENCE













seqNumberUsage

INTEGER

{prepaymentTopUp (0)} ,


Mandatory if newRemotePartySpecialistFloorSeqNumber present

Specify the usage of the SeqNumber

seqNumber

INTEGER




Mandatory if newRemotePartySpecialistFloorSeqNumber present

Specify the associated SeqNumber


replacementOutcomes

SEQUENCE OF




One per replacement in the corresponding Command so at least one

For each replacement in the Command, detail the outcome and impacted parties


SEQUENCE













affectedTrustAnchorCell

SEQUENCE




Mandatory if SEQUENCE is present

Specify which Trust Anchor Cell was the target of this replacement

trustAnchorCellRemotePartyRole

INTEGER

root (0) ,

recovery (1) ,

supplier (2) ,

networkOperator (3) ,

accessControlBroker (4) ,

transitionalCoS (5) ,

wanProvider (6)


Mandatory if SEQUENCE is present

Specify the Remote Party Role to which the Trust Anchor Cell relates

trustAnchorCellKeyUsage

BIT STRING

digitalSignature (0) ,

keyAgreement (4) ,

keyCertSign (5)


Mandatory if SEQUENCE is present

To what use can the public key in this Cell be put

trustAnchorCellUsage

INTEGER

{management(0) ,

prePaymentTopUp(1)}



DEFAULT management

Absent unless:

  • the deviceType is eSME or gSME; and

  • the Supplier operating the Device has chosen to use a separate key agreement Key Pair in relation to prepayment top ups to the Device and this is a replacement of the corresponding certificate

statusCode

ENUMERATED

success (0) ,

badCertificate (5) ,

noTrustAnchor (10) ,

insufficientMemory (17) ,

contingencyPublicKeyDecrypt (22) ,

trustAnchorNotFound (25) ,

resourcesBusy (30) ,

other (127)



Mandatory if SEQUENCE is present

Whether the replacement to this Cell was successful or, if it failed, why it failed

existingSubjectUniqueID

OCTET STRING




Mandatory if SEQUENCE is present

The 64 bit Entity Identifier of the Remote Party whose credentials were in this Cell prior to receipt of the corresponding Command

existingSubjectKeyIdentifier

OCTET STRING




Mandatory if SEQUENCE is present

For the public key in this Cell prior to receipt of the corresponding Command

replacingSubjectUniqueID

OCTET STRING




Mandatory if SEQUENCE is present

The 64 bit Entity Identifier of the Remote Party whose credentials were to be placed in this Cell

replacingSubjectKeyIdentifier

OCTET STRING




Mandatory if SEQUENCE is present

For the public key which was to be placed in this Cell

Table 13.3.4.4: Attribute values for executionOutcome
      1. Common Requirements

        1. Update Security Credentials Command Verification


The Device shall undertake the checks set out in this Section 13.3.5.1 before undertaking any other processing of the Command. The checks should be carried out in the order specified. Checking shall cease at the point that any one check fails. The checks required are shown in Table 13.3.5.1.

Check Number

Criteria that must be tested by the Device

How the Device shall test the Criteria

1.1

The Message is for the Device

The value of the Business Target ID in the Grouping Header in Command instance must be equal to the Device’s Entity Identifier

1.2

The Message Code is for Update Security Credentials

The value in the Message Code field of the Grouping Header must be equal to the value specified in Table 13.3.5.2 for the CredentialsReplacementMode specified in CommandPayload.

1.3

If executionDateTime is present the Command is to replace Supplier Security Credentials.

If executionDateTime is present then credentialsReplacementMode must either supplierBySupplier

or supplierByTransCoS



1.4

The Device has not already actioned this Command.

As specified in Section 13.3.5.3

2.1

The targetTrustAnchorCells all exist on a Device of this type

As specified in Section 13.3.5.4

2.2

The credentialsReplacementMode is one that can be Authorised by the Remote Party / Parties authorising the Command

As specified in Section 13.3.5.5

2.2

The replacements specified are all allowed in this credentialsReplacementMode.

As specified in Section 13.3.5.6

2.3

The keyUsage in each of the replacement certificates provided is consistent with the target Trust Anchor Cells identified in replacements

As specified in Section 13.3.5.7

3.1

The Cryptographic Protections are valid

As specified in Section 13.3.5.8

Table 13.3.5.1: Update Security Credentials Command authenticity and integrity verification

        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   ...   168   169   170   171   172   173   174   175   ...   258




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

    Main page