hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.4.3.1 Si2.GetSpbmCertificate command and response handling | 12.6.4.3.1.1 SI2_64311 - Si2.GetSpbmCertificate request – normal process Test ID SI2_64311 Test objectives To verify that the LBA is able to request the SPBM certificates by sending the Si2.GetSpbmCertificate command to the SPBM. To verify that the SPBM sends a response which includes aSi2GetSpbmCertificateOk. Configuration reference CSI2_6411 Initial conditions The SI2_111_command_01 is generated by using the SI2_111_command configuration file. The SI2_111_response_01 is verified by using the SI2_111_response configuration file. The procedure PSI2_6421 shall be successfully executed. Test sequence Step Description Requirements 1 The LBA sends SI2_111_command_01 to the SPBM. 2 The SPBM sends SI2_111_response_01 to the LBA containing aSi2.GetSpbmCertificateOk. RQ1206_131 RQ1206_140 RQ1206_141 RQ1206_142 RQ1206_143 RQ1206_144 RQ1206_145 RQ1206_146 RQ1206_147 RQ1206_148 RQ1206_149 RQ1206_150 RQ1206_152 RQ1206_153 RQ1206_154 ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 135 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.4.3.1.2 SI2_64312 - Si2.GetSpbmCertificate response | Test ID SI2_64312 Test objectives To verify that the SPBM is able to verify the Si2.GetSpbmCertificate response from the LBA. To verify that the Si2.GetSpbmCertificate response is well formatted and handled successfully. Configuration reference CSI2_6412 Initial conditions The SI2_112_command_01 is generated by using the SI2_112_command configuration file. The SI2_112_response_01 is verified by using the SI2_112_response configuration file. The procedure PSI2_6421 shall be successfully executed. Test sequence Step Description Requirements 1 The LBA sends SI2_112_command_01 to the SPBM. RQ1206_132 2 The SPBM sends SI2_112_response_01 to the LBA containing aSi2GetSpbmCertificateOk. RQ1206_140 RQ1206_141 RQ1206_142 RQ1206_143 RQ1206_144 RQ1206_145 RQ1206_146 RQ1206_147 RQ1206_148 RQ1206_149 RQ1206_150 RQ1206_152 RQ1206_153 RQ1206_154 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.4.3.1.3 SI2_64313 - Si2.GetSpbmCertificate - unsupported family identifier | Test ID SI2_64313 Test objectives To verify that when the LBA requests SPBM credentials for an unsupported family identifier using a Si2.GetSpbmCertificate command the SPBM sends a response which includes eNotSupportedFamilyId. Configuration reference CSI2_6411 Initial conditions The SI2_113_commands are generated by using the SI2_113_command configuration file. The SI2_113_responses are verified by using the SI2_113_response configuration file. The procedure PSI2_6421 shall be successfully executed. Test sequence Step Description Requirements 1 The LBA sends SI2_113_command_01 to the SPBM. 2 The SPBM sends SI2_113_response_01 to the LBA containing aSi2GetSpbmCertificateError with the error cause eNotSupportedFamilyId. RQ1206_148a 3 The LBA sends SI2_113_command_02 to the SPBM. 4 The SPBM sends SI2_113_response_02 to the LBA containing aSi2GetSpbmCertificateError with the error cause eNotSupportedFamilyId. RQ1206_148b ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 136 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.4.3.1.4 SI2_63314 - Si2.GetSpbmCertificate - no trusted public key ID supported by SPBM | Test ID SI2_63314 Test objectives To verify that the SPBM returns an error, when none of the trusted public key identifiers sent in the aSspPkIdListForSpbmVerification is supported by the SPBM. Configuration reference CSI2_6411 Initial conditions The SI2_114_command_01 is generated by using the SI2_114_command configuration file. The SI2_114_response_01 is verified by using the SI2_114_response configuration file. The procedure PSI2_6421 shall be successfully executed. Test sequence Step Description Requirements 1 The LBA sends SI2_114_command_01 to the SPBM. 2 The SPBM sends SI2_114_response_01 to the LBA containing aSi2GetSpbmCertificateError with the error cause eNotSupportedPkIdSpbmVerification. RQ1206_151a 12.6.4.3.1.5 SI2_64315 - Si2.GetSpbmCertificate - no trusted public key ID for SPBL verification supported Test ID SI2_64315 Test objectives To verify that the SPBM returns an error, when none of the trusted public key identifiers received in the aSspPkIdListForSpblVerification is supported. Configuration reference CSI2_6411 Initial conditions The SI2_115_command_01 is generated by using the SI2_115_command configuration file. The SI2_115_response_01 is verified by using the SI2_115_response configuration file. The procedure PSI2_6421 shall be successfully executed. Test sequence Step Description Requirements 1 The LBA sends SI2_116_command_01 to the SPBM. 2 The SPBM sends SI2_116_response_01 to the LBA containing aSi2GetSpbmCertificateError with the error cause eNotSupportedEncryptionAlgorithm. RQ1206_151d |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.4.3.1.6 SI2_64316 - Si2.GetSpbmCertificate - no supported encryption algorithm | Test ID SI2_64316 Test objectives To verify that the SPBM returns an error, when none of the algorithm identifiers received in the aCipherAlgorithmList is supported. Configuration reference CSI2_6411 Initial conditions The SI2_116_command_01 is generated by using the SI2_116_command configuration file. The SI2_116_response_01 is verified by using the SI2_116_response configuration file. The procedure PSI2_6421 shall be successfully executed. Test sequence Step Description Requirements 1 The LBA sends SI2_116_command_01 to the SPBM. 2 The SPBM sends SI2_116_response_01 to the LBA containing aSi2GetSpbmCertificateError with the error cause eNotSupportedEncryptionAlgorithm. RQ1206_151d ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 137 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.4.3.1.7 SI2_64317 - Si2.GetSpbmCertificate - no supported SKID for SPBM verification | Test ID SI2_64317 Test objectives To verify that the SPBM returns the error code eNotSupportedPkIdSpbmVerification when aSspPkIdListForSpbmVerification is not supported. Configuration reference CSI2_6411 Initial conditions The SI2_117_command_01 is generated by using the SI2_117_command configuration file. The SI2_117_response_01 is verified by using the SI2_117_response configuration file. The procedure PSI2_6421 shall be successfully executed. Test sequence Step Description Requirements 1 The LBA sends SI2_117_command_01 to the SPBM. 2 The SPBM sends SI2_117_response_01 to the LBA containing aSi2GetSpbmCertificateError with the error cause eNotSupportedPkIdSpbmVerification. RQ1206_151c |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.4.3.1.8 SI2_64318 - Si2.GetSpbmCertificate - no supported SKID for SPBL verification | Test ID SI2_64318 Test objectives To verify that the SPBM returns the error code eNotSupportedPkIdSpblVerification when aSspPkIdListForSpblVerification is not supported. Configuration reference CSI2_6411 Initial conditions The SI2_118_command_01 is generated by using the SI2_118_command configuration file. The SI2_118_response_01 is verified by using the SI2_118_response configuration file. The procedure PSI2_6421 shall be successfully executed. Test sequence Step Description Requirements 1 The LBA sends SI2_118_command_01 to the SPBM. 2 The SPBM sends SI2_118_response_01 to the LBA containing aSi2GetSpbmCertificateError with the error cause eNotSupportedPkIdSpblVerification. RQ1206_151c |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.4.3.1.9 SI2_64319 - Si2.GetSpbmCertificate - no selection of a family identifier | Test ID SI2_64319 Test objectives To verify that the SPBM returns eSpblSelectOneFamilyId with an error cause indicating that at least one family identifier shall be selected by the Secondary Platform Bundle Loader. Configuration reference CSI2_6411 Initial conditions The SI2_119_command_01 is generated by using the SI2_119_command configuration file. The SI2_119_response_01 is verified by using the SI2_119_response configuration file. The procedure PSI2_6421 shall be successfully executed. Test sequence Step Description Requirements 1 The LBA sends SI2_119_command_01 to the SPBM. 2 The SPBM sends SI2_119_response_01 to the LBA containing aSi2GetSpbmCertificateError with the error cause eSpblSelectOneFamilyId. RQ1206_148c ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 138 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.4.3.1.10 SI2_643110 - Si2.GetSpbmCertificate - no selection of an OID | Test ID SI2_643110 Test objectives To verify that the SPBM returns eSpblSelectOneOid with an error cause indicating that at least one custodian shall be selected by the SPBL. Configuration reference CSI2_6411 Initial conditions The SI2_1110_command_01 is generated by using the SI2_1110_command configuration file. The SI2_1110_response_01 is verified by using the SI2_1110_response configuration file. The procedure PSI2_6421 shall be successfully executed. Test sequence Step Description Requirements 1 The LBA sends SI2_1111_command_01 to the SPBM. 2 The SPBM sends SI2_1111_response_01 to the LBA containing aSi2GetSpbmCertificateError with the error cause eSpblSelectOneOid. RQ1206_150 ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 139 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.4.3.2 Si2.GetBoundSpbImage command and response handling | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.4.3.2.1 SI2_64321 - Si2.GetBoundSpbImage - normal process | Test ID SI2_64321 Test objectives To verify that the LBA requests the SPBL bound image from the SPBM by sending an Si2GetBoundSpbImage command. Configuration reference CSI2_6411 Initial conditions The SI2_121_command_01 is generated by using the SI2_121_command configuration file. The SI2_121_response_01 is verified by using the SI2_121_response configuration file. The procedure PSI2_6421 shall be successfully executed. Test sequence Step Description Requirements 1 The LBA sends SI2_121_command_01 to the SPBM. 2 The SPBM sends SI2_121_response_01 to the LBA. The LBA (tester) shall verify that the response is well formatted. RQ1206_155 RQ1206_156 RQ1206_157 RQ1206_158 RQ1206_159 RQ1206_160 RQ1206_161 RQ1206_162 RQ1206_164 RQ1206_165 RQ1206_166 RQ1206_167 RQ1206_168 RQ1206_169 RQ1206_170 RQ1206_171 RQ1206_172 RQ1206_173 RQ1206_174 RQ1206_175 RQ1206_176 RQ1206_177 RQ1206_178 RQ1206_179 RQ1206_180 RQ1206_182 RQ1206_183 RQ1206_184 ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 140 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.4.3.2.2 SI2_64322 - Si2.GetBoundSpbImage - no or invalid SSP credentials | Test ID SI2_64322 Test objectives To verify that the SPBM returns aSi2GetBoundSpbImageError with the error code eInvalidBoundSpbImage when the LBA requests the SPBL bound image from the SPBM by sending Si2GetBoundSpbImage command without SSP credentials or with invalid SSP credentials. Configuration reference CSI2_6411 Initial conditions The SI2_122_command_01 is generated by using the SI2_122_command configuration file. The SI2_122_response_01 is verified by using the SI2_122_response configuration file. The procedure PSI2_6421 shall be successfully executed. Test sequence Step Description Requirements 1 The LBA sends SI2_122_command_01 to the SPBM (without or with invalid, SSP credentials). 2 The SPBM sends SI2_122_response_01 response to the LBA. The LBA (tester) shall verify that the response contains aSi2GetBoundSpbImageError with the error code eInvalidSpbImage. RQ1206_170 RQ1206_184e |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.4.3.2.3 SI2_64323 - Si2.GetBoundSpbImage - invalid aCodeM | Test ID SI2_64323 Test objectives To verify that the SPBM returns aSi2GetBoundSpbImageError with the error code eInvalidCodeM when the LBA requests the SPBL bound image from the SPBM by sending Si2GetBoundSpbImage command with an unknown aCodeM included in the SSP credentials. Configuration reference CSI2_6411 Initial conditions The SI2_123_command_01 is generated by using the SI2_123_command configuration file. The SI2_123_response_01 is verified by using the SI2_123_response configuration file. The procedure PSI2_6421 shall be successfully executed. Test sequence Step Description Requirements 1 The LBA sends SI2_123_command_01 to the SPBM (with an unknown aCodeM). 2 The SPBM sends SI2_123_response_01 response to the LBA. The LBA (tester) shall verify that the response is well formatted. RQ1206_184 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.4.3.2.4 SI2_64324 - Si2.GetBoundSpbImage - invalid SPBL certificates | Test ID SI2_64324 Test objectives To verify that the SPBM returns aSi2GetBoundSpbImageError with error code eInvalidSpblCertificate when the LBA requests the SPBL bound image from the SPBM by sending Si2GetBoundSpbImage command with an invalid certification path to the SPBL certificate. Configuration reference CSI2_6411 Initial conditions The SI2_124_command_01 is generated by using the SI2_124_command configuration file. The SI2_124_response_01 is verified by using the SI2_124_response configuration file. The procedure PSI2_6421 shall be successfully executed. Test sequence Step Description Requirements 1 The LBA sends SI2_124_command_01 to the SPBM (with an invalid certification path). 2 The SPBM sends SI2_124_response_01 response to the LBA. The LBA (tester) shall verify that the response contains aSi2GetBoundSpbImageError with error code eInvalidSpblCertificate. RQ1206_184a ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 141 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.4.3.2.5 SI2_64325 - Si2.GetBoundSpbImage - invalid ChallengeS | Test ID SI2_64325 Test objectives To verify that the SPBM returns a response containing aSi2GetBoundSpbImageError with error code eInvalidChallengeS when the LBA requests the SPBL bound image from the SPBM and the ChallengeS returned by the SPBL does not match the one generated by the SPBM. Configuration reference CSI2_6411 Initial conditions The SI2_125_command_01 is generated by using the SI2_125_command configuration file. The SI2_125_response_01 is verified by using the SI2_125_response configuration file. The procedure PSI2_6421 shall be successfully executed. Test sequence Step Description Requirements 1 The LBA sends SI2_125_command_01 to the SPBM (with an invalid ChallengeS). 2 The SPBM sends SI2_125_response_01 response to the LBA. The LBA (tester) shall verify that the response contains aSi2GetBoundSpbImageError with error code eInvalidChallengeS. RQ1206_184c |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.4.3.2.6 SI2_64326 - Si2.GetBoundSpbImage - invalid selected SPB Image | Test ID SI2_64326 Test objectives To verify that the SPBM is checking the validity of the SPB for the iSSP. Configuration reference CSI2_6411 Initial conditions The SI2_126_command_01 is generated by using the SI2_126_command configuration file. The SI2_126_response_01 is verified by using the SI2_126_response configuration file. The procedure PSI2_6421 shall be successfully executed. Test sequence Step Description Requirements 1 The LBA sends SI2_126_command_01 to the SPBM. 2 The SPBM sends SI2_126_response_01 response to the LBA. The LBA (tester) shall verify that the response contains aSi2GetBoundSpbImageError with error code eInvalidSpbImage. RQ1206_184d |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.4.3.2.7 SI2_64327 - Si2.GetBoundSpbImage - invalid TransacId | Test ID SI2_64327 Test objectives To verify that the SPBM returns a response containing aSi2GetBoundSpbImageError with error code eInvalidBoundSpbImageByTransacId when the LBA requests the SPBL bound image from the SPBM by sending Si2GetBoundSpbImage command with an invalid referenced TransacId. Configuration reference CSI2_6411 Initial conditions The SI2_127_command_01 is generated by using the SI2_127_command configuration file. The SI2_127_response_01 is verified by using the SI2_127_response configuration file. The procedure PSI2_6421 shall be successfully executed. Test sequence Step Description Requirements 1 The LBA sends SI2_127_command_01 to the SPBM (with an invalid referenced TransacId. 2 The SPBM sends SI2_127_response_01 response to the LBA. The LBA (tester) shall verify that the response contains aSi2GetBoundSpbImageError with error code eInvalidBoundSpbImageByTransacId. RQ1206_184e ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 142 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.4.3.3 Si2.HandleNotification command and response handling | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.4.3.3.1 SI2_64331 - Si2.HandleNotificationCommand - normal process | Test ID SI2_64333 Test objectives To verify that the "Si2HandleNotification" function is used by the LBA to send any notification about the result of the Secondary Platform Bundle management to the SPBM. Configuration reference CSI2_6411 Initial conditions The SI2_131_command_01 is generated by using the SI2_131_command configuration file. The SI2_131_response_01 is verified by using the SI2_131_response configuration file. The procedure PSI2_6421 shall be successfully executed. Test sequence Step Description Requirements 1 The LBA sends SI2_131_command_01 to the SPBM. 2 The SPBM sends SI2_131_response_01 response to the LBA. The LBA (tester) shall verify that the response is well formatted. RQ1206_185 RQ1206_186 RQ1206_187 RQ1206_188 NOTE: The response from the SPBM does not contain error codes. Invalid parameters within the Si2.HandleNotification command will not be indicated and nor can they be identified. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.4.4 Requirements not testable, implicitly verified or verified elsewhere | The following requirements are generated from descriptive text. An explicit verification is not possible but with correct execution of the related function the requirements can be handled as implicitly verified: RQ1206_001, RQ1206_072, RQ1206_073, RQ1206_074, RQ1206_075, RQ1206_076, RQ1206_077, RQ1206_078, RQ1206_079, RQ1206_081 and RQ1206_096. The following requirements are generated from descriptive text. A verification by tests defined within the present document is not possible: RQ1206_083, RQ1206_098, RQ1206_104, RQ1206_112, RQ1206_122. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 143 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5 Si3 interface | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.1 Configurations | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.1.1 CSI3_6511 - SPBL service - host A | Configuration ID CSI3_6511 Configuration description Other host domain (Tester) SSP host domain (SUT) SSP host Other host A Administation Administration gate Administration Administration gate SPBL application SPBL application gate SPBL service SPBL service gate |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.1.2 SSP configuration | The SSP under test shall be configured by the SSP Manufacturer (SSPM). |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.2 Procedures | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.2.1 PSI3_6521 - Pipe session opening on the SPBL service gate | Procedure ID PSI3_6521 Objectives The other host A shall be able to open a pipe session to the SPBL service gate of the SSP host. SPBL service identifier is defined as the OFL service identifier in Global Platform OFL VNP Extension [16]. Configuration reference CSI3_6511 Initial conditions Test sequence Step Description 1 Administration gate in other host sends EVT_ADM_BIND to Administration gate in the SSP host with: • PIPEXY: a dynamically assigned pipe identifier for the SPBL service gate. • GATESPBL: The UUID gate identifier of the SPBL gate (BB780E30-419A-5B71-9B98- 18A042E75899). 2 Administration gate in SSP host sends EVT_ADM_BIND to Administration gate in the other host with: • PIPEYX: a dynamically assigned pipe identifier for the SPBL application gate. • GATESPBL: The UUID gate identifier of the SPBL gate (BB780E30-419A-5B71-9B98- 18A042E75899). ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 144 Release 15 12.6.5.2.2 PSI3_6522 - Verification of the SPBL service availability Procedure ID PSI3_6522 Objectives The identity application gate shall verify the availability of the SPBL service gate identifier in the register GATE_LIST of the registry in the identity service gate. Configuration reference CSVC_311, CSI3_6511 Initial conditions The procedure PSI3_6521 shall execute successfully. Test sequence Step Description 1 Identity application gate sends ANY_GET_PARAMETER command (pipe PIPEXY) to the identity service gate with the register '04'H. 2 Identity service gate sends ANY_GET_PARAMETER response to the identity application gate. The service identifier 'BB780E30-419A-5B71-9B98-18A042E75899F917' shall be present. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.3 Test descriptions | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.3.1 Si3.GetSspInfo command and response handling | 12.6.5.3.1.1 SI3_65311 - Si3.GetSspInfo command with SpbFamilyId and an OID for the custodian, SSP with configuration for aSpbFamilyId and aCustodianOid Test ID SI3_65311 Test objectives To verify that the SPBL application gate (Other Host) is able to retrieve the correct SSP Information by sending a Si3.GetSspInfo command with SpdFamilyId and an OID for the custodian of the family identifier to the SPBL service gate if the SSP has a configuration for aSpbFamilyId and aCustodianOid. Configuration reference CSI3_6511 Initial conditions The procedure PSI3_6521 shall be successfully executed where the SSP has a configuration for aSpbFamilyId and aCustodianOid. Test sequence Step Description Requirements 1 SPBL application gate (Other Host) sends GET_SSP_INFO command with SpbFamilyId and Custodian Oid to the SPBL service gate. RQ1206_190 RQ1206_191 RQ1206_195 RQ1206_274 2 SPBL service gate sends ANY_OK response with SspInfoPublic to the SPBL application gate. The response data is structured as follows: • aSpblSpecVerInfo shall be present with corresponding value defined for this version of specification. • aSspFamilyCryptoInfoBlock shall be present aSpbFamilyId shall be present a single aSspFamilyCryptoInfo shall be present aCustodianOid shall be present aSspOidCryptoInfo shall be present a list of trusted public key identifiers and a list of algorithm identifiers which can be used with that aSpbFamilyId and that aCustodianOid shall be present. RQ1206_192 RQ1206_194 RQ1206_197 RQ1206_200 RQ1203_019 RQ1206_189 RQ1206_193 RQ1206_196 ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 145 Release 15 12.6.5.3.1.2 SI3_65312 - Si3.GetSspInfo command with SpbFamilyId only, SSP has configuration for SpbFamilyId Test ID SI3_65312 Test objectives To verify that the SPBL application gate (Other Host) is able to retrieve SSP Information by sending a Si3.GetSspInfo (GET_SSP_INFO) command with SpdFamilyId only to the SPBL service gate. Configuration reference CSI3_6511 Initial conditions The procedure PSI3_6521 shall be successfully executed where the SSP has a configuration for SpbFamilyId. Test sequence Step Description Requirements 1 SPBL application gate (Other Host) sends GET_SSP_INFO command with SpbFamilyId to the SPBL service gate. 2 SPBL service gate sends ANY_OK response with SspInfoPublic to the SPBL application gate. • Verify that aSpblSpecVerInfo is present and is set to the release corresponding to the version of the implemented specification. • Verify that aSspFamilyCryptoInfoBlock is present Verify that aSpbFamilyId is present Verify that aSspOidCryptoInfoBlock is present for each supported custodian Verify that aCustodianOid is present Verify that aSspOidCryptoInfo is present Verify that the list of trusted public key identifiers and the list of algorithm identifiers which are to be used with that aSpbFamilyId and that aCustodianOid are present. RQ1206_197 RQ1206_200 12.6.5.3.1.3 SI3_65313 - Si3.GetSspInfo command with SpbFamilyId, SSP has no configuration for SpbFamilyId Test ID SI3_65313 Test objectives To verify that the SPBL application gate (Other Host) is able to retrieve SSP Information by sending a Si3.GetSspInfo (GET_SSP_INFO) command with spdFamilyId only to the SPBL service gate. Configuration reference CSI3_6511 Initial conditions The procedure PSI3_6521 shall be successfully executed where the SSP has no configuration for SpbFamilyId. Test sequence Step Description Requirements 1 SPBL application gate (Other Host) sends GET_SSP_INFO command with SpbFamilyId to the SPBL service gate. 2 SPBL service gate sends ANY_OK response with SspInfoPublic to the SPBL application gate: • Verify that aSpblSpecVerInfo is present and is set to the release corresponding to the version of the implemented specification. • Verify that aSspGeneralCryptoInfo is present Verify that a list of trusted public key identifiers and a list of algorithm identifiers are present, which are not associated with any family identifier and any custodian. RQ1206_198 RQ1206_200 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.3.1.4 SI3_65314 - Si3.GetSspInfo command with empty parameters | Test ID SI3_65314 Test objectives To verify that the SPBL application gate (Other Host) is able to retrieve SSP Information by sending a Si3.GetSspInfo (GET_SSP_INFO) command with empty parameters to the SPBL service gate. Configuration reference CSI3_6511 ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 146 Release 15 Initial conditions The procedure PSI3_6521 shall be successfully executed. Test sequence Step Description Requirements 1 SPBL application gate (Other Host) sends GET_SSP_INFO command without SpbFamilyId and OID for the associated custodian to the SPBL service gate. 2 SPBL service gate sends ANY_OK response with SspInfoPublic to the SPBL application gate: • Verify that aSpblSpecVerInfo is present and is set to the release corresponding to the version of the implemented specification. • Verify that aSspGeneralCryptoInfo is present for each supported aSpbFamilyId Verify that aSpbFamilyId is present Verify that aSpbOidCryptoInfoBlock is present Verify that a list of trusted public key identifiers and a list of algorithm identifiers are present, which are to be used with that aSpbFamilyId and the associated aCustodianOid. RQ1206_199 RQ1206_200 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.3.2 Si3.SetSpbmCredential command and response handling | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.3.2.1 SI3_65321 - Si3.SetSpbmCredential | Test ID SI3_65321 Test objectives To verify that the SPBL application gate (Other Host) is able to set SPBM Credentials by sending a Si3.SetSpbmCredential (ANY_SET_PARAMETER) to the SPBL Registry in the SPBL service gate. Configuration reference CSI3_6511 Initial conditions The procedure PSI3_6521 shall be successfully executed. Test sequence Step Description Requirements 1 SPBL application gate (Other Host) sends ANY_SET_PARAMETER command with index of IDS_CREDENTIAL_PARAMETER to the SPBL service gate. RQ1206_201 RQ1206_202 RQ1206_204 RQ1203_028 2 SPBL service gate sends ANY_OK response to the SPBL application gate. RQ1206_212 RQ1203_030 RQ1206_205 RQ1206_206 RQ1206_207 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.3.3 Si3.LoadBoundSpbInfo command and response handling | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.3.3.1 SI3_65331 - Si3.LoadBoundSpbInfo | Test ID SI3_65331 Test objectives To verify that the SPBL application gate (Other Host) is able to load bound SPB Information by sending a Si3.LoadBoundSpbInfo (OFL_DO_OPERATE) command to the SPBL service gate. Configuration reference CSI3_6511 Initial conditions The procedure PSI3_6521 shall be successfully executed. Test sequence Step Description Requirements 1 SPBL application gate (Other Host) sends OFL_DO_OPERATE command with parameter "DoOperateParameter" to the SPBL service gate to Secondary Platform Bundle. RQ1206_214 RQ1206_215 2 SPBL service gate sends ANY_OK response to the SPBL application gate. RQ1206_229 RQ1203_040 ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 147 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.3.4 Si3.LoadBoundSpbSds command and response handling | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.3.4.1 SI3_65341 - Si3.LoadBoundSpbSds | Test ID SI3_65341 Test objectives To verify that the SPBL application gate (Other Host) is able to load bound SPB SDS by sending a Si3.LoadBoundSpbSds (OFL_CHANGE_SEGMENT) command to the SPBL service gate. Configuration reference CSI3_6511 Initial conditions The test SI3_65331 shall be successfully executed. Test sequence Step Description Requirements 1 SPBL application gate (Other Host) sends OFL_CHANGE_SEGMENT command with parameter "ChangeSegmentParameter" to the SPBL service gate to Secondary Platform Bundle. RQ1206_230 RQ1206_232 RQ1206_233 2 SPBL service gate sends ANY_OK response to the SPBL application gate. RQ1206_234 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.3.5 Si3.LoadBoundSpbSeg command and response handling | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.3.5.1 SI3_65351 - Si3.LoadBoundSpbSeg | Test ID SI3_65351 Test objectives To verify that the SPBL application gate (Other Host) is able to load bound SPB Segment by sending a Si3.LoadBoundSpbSeg (OFL_LOAD_SEGMENT) command to the SPBL service gate. Configuration reference CSI3_6511 Initial conditions The test SI3_65341 shall be successfully executed. Test sequence Step Description Requirements 1 SPBL application gate (Other Host) sends OFL_LOAD_SEGMENT command with parameter "LoadSegmentParameter" to the SPBL service gate to Secondary Platform Bundle. RQ1206_236 RQ1206_237 RQ1206_238 2 SPBL service gate sends ANY_OK response to the SPBL application gate. RQ1206_239 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.3.6 Si3.GetSspCredential command and response handling | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.3.6.1 SI3_65361 - Si3.GetSspCredential | Test ID SI3_65361 Test objectives To verify that the SPBL application gate (Other Host) is able to get SSP Credentials by sending a SI3.GetSspCredential (ANY_GET_PARAMETER) to the SPBL Registry in the SPBL service gate. Configuration reference CSI3_6511 Initial conditions The test SI3_65321 shall be successfully executed. Test sequence Step Description Requirements 1 SPBL application gate (Other Host) sends ANY_GET_PARAMETER command with index of TRE_CREDENTIAL_PARAMETER to the SPBL service gate. RQ1206_241 RQ1206_242 RQ1206_243 RQ1203_031 2 SPBL service gate sends ANY_OK response to the SPBL application gate with value of TRE_CREDENTIAL_PARAMETER registry which contains SspCredential as defined in clause12.6.2.4 SSP credential of ETSI TS 103 666-2 [10]. RQ1206_244 RQ1203_032 RQ1206_203 ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 148 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.3.7 Si3.EnableSpb command and response handling | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.3.7.1 SI3_65371 - Si3.EnableSpb | Test ID SI3_65371 Test objectives To verify that the SPBL application gate is able to enable a SPB by sending a Si3.EnableSpb (OFL_ENABLE_FIRMWARE) to the SPBL service gate. Configuration reference CSI3_6511 Initial conditions The procedure PSI3_6521 shall be successfully executed. Test sequence Step Description Requirements 1 SPBL application gate sends OFL_ENABLE_FIRMWARE command to the SPBL service gate with the identifier of the Secondary Platform Bundle to enable. RQ1206_246 RQ1206_247 RQ1204_003 2 SPBL service gate sends ANY_OK response to the SPBL application gate. RQ1204_005 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.3.7.2 SI3_65372 - Si3.EnableSpb based on TELECOM_CAPABILITY value | Test ID SI3_65372 Test objectives To verify that the SPBL application gate (Other Host) is able to enable no. of SPBs as defined in registry TELECOM_CAPABILITY.by sending a Si3.EnableSpb commands to the SPBL service gate. Configuration reference CSI3_6511 Initial conditions The procedure PSI3_6521 shall be successfully executed. Registry "TELECOM_CAPABILITY" is present in OFL Service Gate with at-least value 1. Test sequence Step Description Requirements 1 SPBL application gate (Other Host) sends ANY_GET_PARAMETER command with TELECOM_CAPABILITY registry index '80' to the SPBL service gate in Secondary Platform Bundle. 2 SPBL service gate sends ANY_OK response to the SPBL application gate and provides value stored for TELECOM_CAPABILITY. 3 The test SI3_65316 shall execute successfully - Si3.GetSspInfo. 4 The test SI3_65321 shall execute successfully - Si3.SetSpbmCredential. 5 The test SI3_65361 shall execute successfully - Si3.GetSspCredential. 6 Execute step 7, step 8 and step 9 successfully, for count of TELECOM_CAPABILITY received in step 2. 7 The test SI3_65331 shall execute successfully - Si3.LoadBoundSspInfo. 8 Load Telecom SPB Image. Loop (until whole SPB Image is loaded): • The test SI3_65341 shall execute successfully - Si3.LoadBoundSpbSds. • The test SI3_65351 shall execute successfully - Si3. LoadBoundSpbSeg. 9 The test SI3_65371 shall execute successfully - Si3.EnableSpb: • With SpbId of Telecom SPB Image. 10 Execute step 7 and step 8 successfully: Execute step 9 with failure [eSPBL_E_EXCEED_TELECOM_CAPABILITY – '15']. RQ1206_249 RQ1204_004 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.3.8 Si3.DisableSpb command and response handling | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.3.8.1 SI3_65381 - Si3.DisableSpb | Test ID SI3_65381 Test objectives To verify that the SPBL application gate is able to disable a SPB by sending a Si3.DisableSpb (OFL_DISABLE_FIRMWARE) to the SPBL service gate. Configuration reference CSI3_6511 ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 149 Release 15 Initial conditions The procedure PSI3_6521 shall be successfully executed. Test sequence Step Description Requirements 1 SPBL application gate sends OFL_DISABLE_FIRMWARE command to the SPBL service gate with the identifier of the Secondary Platform Bundle to disable. RQ1206_252 RQ1206_253 2 SPBL service gate sends ANY_OK response to the SPBL application gate. RQ1204_009 RQ1204_013 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.3.9 Si3.DeleteSpb command and response handling | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.3.9.1 SI3_65391 - Si3.DeleteSpb | Test ID SI3_65391 Test objectives To verify that the SPBL application gate is able to delete a SPB by sending a Si3.DeleteSpb (OFL_DELETE_SESSION) to the SPBL service gate. Configuration reference CSI3_6511 Initial conditions The procedure PSI3_6521 shall execute successfully. Test sequence Step Description Requirements 1 SPBL application gate sends OFL_DELETE_SESSION command to the SPBL service gate with the identifier of the Secondary Platform Bundle to delete. RQ1206_257 RQ1204_014 2 SPBL service gate sends ANY_OK response to the SPBL application gate. RQ1204_015 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.3.10 Si3.GetSpbMetadata command and response handling | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.3.10.1 SI3_653101 - Si3.GetSpbMetadata | Test ID SI3_653101 Test objectives To verify that the SPBL application gate (Other Host) shall be able to retrieve SPB metadata by sending a Si3.GetSpbMetadata (GET_SPB_METADATA) command to the SPBL service gate. Configuration reference CSI3_6511 Initial conditions The procedure PSI3_6521 shall be successfully executed. Test sequence Step Description Requirements 1 SPBL application gate (Other Host) sends GET_SPB_METADATA command with SpbId to the SPBL service gate to Secondary Platform Bundle. RQ1206_190 RQ1206_191 RQ1206_260 RQ1206_261 RQ1206_262 RQ1206_054 2 SPBL service gate sends ANY_OK response to the SPBL application gate. RQ1206_192 RQ1206_264 RQ1204_017 RQ1204_018 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.3.11 Si3.UpdateSpbState command and response handling | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.3.11.1 SI3_653111 - Si3.UpdateSpbState | Test ID SI3_653111 Test objectives To verify that the SPBL application gate (Other Host) is able to update SpbId by sending a Si3.UpdateSpbState (ANY_SET_PARAMETER) command to the SPBL service gate. Configuration reference CSI3_6511 ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 150 Release 15 Initial conditions The procedure PSI3_6521 shall be successfully executed. Test sequence Step Description Requirements 1 SPBL application gate (Other Host) sends ANY_SET_PARAMETER command with SpbId and SPB_ID registry index to the SPBL service gate in Secondary Platform Bundle. RQ1206_266 RQ1206_267 RQ1206_268 RQ1204_019 2 SPBL service gate sends ANY_OK response to the SPBL application gate. RQ1206_269 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.3.12 Si3.GetSpbState command and response handling | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.3.12.1 SI3_653121 - Si3.GetSpbState | Test ID SI3_653121 Test objectives To verify that the SPBL application gate (Other Host) is able to get the SPB state by sending a Si3.GetSpbState (ANY_SET_PARAMETER) command to the SPBL service gate. Configuration reference CSI3_6511 Initial conditions The procedure PSI3_6521 shall be successfully executed. The test SI3_653111 shall be successfully executed. Test sequence Step Description Requirements 1 SPBL application gate (Other Host) sends ANY_SET_PARAMETER command with SPB_STATE registry index to the SPBL service gate in Secondary Platform Bundle. RQ1206_271 RQ1206_272 RQ1204_022 2 SPBL service gate sends ANY_OK response to the SPBL application gate. RQ1206_273 RQ1204_023 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.3.13 SI3_65313 - SPB Management Operations | Test ID SI3_65313 Test objectives To verify that the SPBL application gate (Other Host) is able to load SPB and perform SPB management operations by sending Si3 layer commands to the SPBL service gate. Configuration reference CSI3_6511 Initial conditions The procedure PSI3_6521 shall be successfully executed. Test sequence Step Description Requirements 1 The test SI3_65316 shall be successfully executed - Si3.GetSspInfo. RQ1203_017 2 The test SI3_65321 shall be successfully executed - Si3.SetSpbmCredential. 3 The test SI3_65361 shall be successfully executed - Si3.GetSspCredential. RQ1206_211 RQ1206_240 4 The test SI3_65331 shall be successfully executed - Si3.LoadBoundSspInfo For Non-Telecom SPB Image. 5 Load Non-Telecom SPB Image. Loop (until whole SPB Image is loaded): • The test SI3_65341 shall be successfully executed - Si3.LoadBoundSpbSds The test SI3_65351 shall be successfully executed - Si3. LoadBoundSpbSeg. RQ1206_230 RQ1206_235 6 The test SI3_65331 shall be successfully executed - Si3.LoadBoundSspInfo For Telecom SPB Image – 1. 7 Load Telecom SPB Image - 1. Loop (until whole SPB Image is loaded): • The test SI3_65341 shall be successfully executed - Si3.LoadBoundSpbSds The test SI3_65351 shall be successfully executed y - Si3. LoadBoundSpbSeg. 8 The test SI3_65331 shall execute successfully - Si3.LoadBoundSspInfo For Telecom SPB Image – 2. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 151 Release 15 9 Load Telecom SPB Image - 2. Loop (until whole SPB Image is loaded): • The test SI3_65341 shall execute successfully - Si3.LoadBoundSpbSds The test SI3_65351 shall execute successfully - Si3. LoadBoundSpbSeg. 10 The test SI3_65310 shall execute successfully - Si3.GetSpbMetadata With SpbId of Non-Telecom SPB Image. 11 The test SI3_65371 shall execute successfully - Si3.EnableSpb With SpbId of Non-Telecom SPB Image. RQ1206_245 12 The test SI3_65312 shall execute successfully - Si3.UpdateSpbState With SpbId of Non-Telecom SPB Image. RQ1206_265 13 The test SI3_65313 shall execute successfully - Si3.GetSpbState • With SpbId of Non-Telecom SPB Image Verify returned state is Enable. 14 The test SI3_65381 shall execute successfully - Si3.DisableSpb With SpbId of Non-Telecom SPB Image. RQ1206_251 15 The test SI3_65312 shall execute successfully - Si3.UpdateSpbState With SpbId of Non-Telecom SPB Image. 16 The test SI3_65313 shall execute successfully - Si3.GetSpbState • With SpbId of Non-Telecom SPB Image Verify returned state is Disable. RQ1206_255 RQ1206_270 17 The test SI3_65391 shall execute successfully - Si3.DeleteSpb With SpbId of Non-Telecom SPB Image. RQ1206_256 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.3.14 SI3_65314 - Si3.SwitchSpb | Test ID SI3_65314 Test objectives To verify that the SPBL application gate (Other Host) shall be able to switch between different telecom SPBs by sending and perform SPB management operations by sending Si3 layer commands to the SPBL service gate. Configuration reference CSI3_6511 Initial conditions The procedure PSI3_6521 shall be successfully executed. The test SI3_65314 shall be successfully executed. Registry "TELECOM_CAPABILITY" is present in OFL Service Gate with at-least value 1. Test sequence Step Description Requirements 1 The test SI3_65371 shall be successfully executed - Si3.EnableSpb • With SpbId of Telecom SPB Image-1. 2 The test SI3_65312 shall be successfully executed - Si3.UpdateSpbState With SpbId of Telecom SPB Image-1. 3 The test SI3_65313 shall execute successfully - Si3.GetSpbState • With SpbId of Telecom SPB Image-1 Verify returned state is Enable. 4 The test SI3_65312 shall execute successfully - Si3.UpdateSpbState • With SpbId of Telecom SPB Image-2. 5 The test SI3_65313 shall execute successfully - Si3.GetSpbState • With SpbId of Telecom SPB Image-2 Verify returned state is Disable. 6 SPBL application gate (Other Host) sends SWITCH_TELECOM_SPB command (Si3.SwitchSpb) with: • SpbId of Telecom SPB Image-1 as aSpbIdToBeDisabled; and • SpbId of Telecom SPB Image-2 as aSpbIdToBeEnabled to the SPBL service gate to Secondary Platform Bundle. RQ1206_190 RQ1206_191 7 SPBL service gate sends ANY_OK response to the SPBL application gate. RQ1206_192 8 The test SI3_65312 shall execute successfully - Si3.UpdateSpbState With SpbId of Telecom SPB Image-1. 9 The test SI3_65313 shall execute successfully - Si3.GetSpbState • With SpbId of Telecom SPB Image-1 Verify returned state is Disable. 10 The test SI3_65312 shall execute successfully - Si3.UpdateSpbState With SpbId of Telecom SPB Image-2. 11 The test SI3_65313 shall execute successfully - Si3.GetSpbState • With SpbId of Telecom SPB Image-2 Verify returned state is Enable. RQ1206_250 ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 152 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.5.4 Requirements not testable, implicitly verified or verified elsewhere | The following requirements are generated from descriptive text. A verification by tests defined within the present document is not possible: RQ1206_004, RQ1206_022, RQ1206_055, RQ1206_056, RQ1206_188, RQ1206_189, RQ1206_196, RQ1206_205, RQ1206_206, RQ1206_207, RQ1206_208, RQ1206_209, RQ1206_210, RQ1206_211, RQ1206_213, RQ1206_216, RQ1206_217, RQ1206_218, RQ1206_219, RQ1206_220, RQ1206_221, RQ1206_222, RQ1206_223, RQ1206_224, RQ1206_225, RQ1206_226, RQ1206_231, RQ1206_234, RQ1206_248, RQ1206_254, RQ1206_259, RQ1206_263. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 153 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.6 Si4 interface | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.6.0 Si4 Principles | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.6.0.1 Si4 tunneling over Si3 and Si2 | Figure 12.1 illustrates the tunneling of the Si4 over Si2 and Si3. Figure 12.1: Security Protocol over Si2 and Si3 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.6.0.2 Si4 security protocol abstract view | Figure 12.2 illustrates the handling of the Si4 security protocol between SPBL and SPBM. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 154 Release 15 Figure 12.2: Si4 Security Protocol SPBL/SPB Manager The Protocol Data Unit (PDU) conveying the Si4 security protocol are generated by using Si3 and Si2 messages. All PDUs are sequentially dependent and cannot be generated independently. In order to link these PDUs, a software tooling is available in the ETSI forge repository - SCP iSSP tooling [34]. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.6.0.3 Testing the Si4 SPBL service | Figure 12.3 illustrates the testing of the SPBL service (SUT) from the LBA (tester). The Tester emulates the SPBM. Figure 12.3: Si4 SPBL service For sake of simplicity, the returned status subsequent to any exchange are not showed. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 155 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.6.0.4 Testing the Si4 SPB Manager service | Figure 12.4 illustrates the testing of the SPBM service(SUT) from the LBA (tester). The Tester emulates the SPBL. Figure 7: Si4 SPBM service For sake of simplicity, the returned status subsequent to any exchange are not showed. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.6.1 Configurations | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.6.1.1 CSI4_6611 - LBA - SPBL (SUT) | Configuration ID CSI4_6611 Configuration description (Tester) LBA SPBL Si4 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.6.1.2 CSI4_6612 - LBA - SPB Manager (SUT) | Configuration ID CSI4_Y12 Configuration description (Tester) LBA SPBM server Si4 ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 156 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.6.2 Procedures | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.6.2.1 PSI4_6621 - session opening between SPBL and the SPB Manager | Procedure ID PSI4_6621 Procedure objectives The LBA manages the bridge between the SPBL and the SPBM. The semantic of the Si4 security protocol is conveyed by using Si3 and Si2. The LBA is in charge to get and forward the Si4 data between the SPBL and the SPBM. For tests considerations, the LBA is transparent between SPBL and SPBM. Configuration reference CSI4_6611 or CSI4_6612 Initial conditions Test sequence Step Description 1 The SPBL establishes the Si3 connection to the LBA. 2 The SBPM establishes the Si2 connection to the LBA. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.6.3 Test Descriptions | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.6.3.1 Si4 - SPBL service | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.6.3.1.1 SI4_66311 - Normal flow | Test ID SI4_66311 Test objectives To verify that no errors occur if the LBA (tester) stimulates the SPBL (SUT) with PDUs, and these PDUs are conveyed in Si4 semantic. Configuration reference CSI4_6611 Initial conditions The procedure PSI4_6621 shall be successfully executed. The SI4_111_pdu is generated by using the SI4_111_pdu configuration file. Test sequence Step Description Requirements 1 The SPBL sends to SI4_111_pdu_01 to the LBA. RQ1206_248 RQ1206_254 RQ1206_258 RQ1206_259 RQ1206_263 2 The LBA sends to SI4_111_pdu_02 to the SPBL. RQ1206_217 RQ1206_207 RQ1206_209 RQ1206_210 RQ1202_001 RQ1202_002 RQ1202_006 RQ1202_007 RQ1202_008 RQ1202_009 RQ1202_010 ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 157 Release 15 3 The SPBL sends to SI4_111_pdu_02 to the LBA. RQ1206_237 RQ1202_006 RQ1202_007 RQ1202_008 RQ1202_009 RQ1202_010 RQ1202_011 RQ1202_012 RQ1202_013 RQ1202_014 RQ1202_015 RQ1202_016 RQ1202_017 RQ1202_030 RQ1202_033 RQ1202_042 4 The LBA sends to SI4_111_pdu_04 to the SPBL. RQ1206_218 RQ1206_219 RQ1206_220 RQ1206_221 RQ1206_222 RQ1206_223 RQ1206_224 RQ1206_225 RQ1206_226 RQ1206_226a RQ1206_226b RQ1202_006 RQ1202_007 RQ1202_008 RQ1202_009 RQ1202_010 5 The LBA sends to SI4_111_pdu_05 to the SPBL. RQ1202_042 6 The LBA sends to SI4_111_pdu_06 to the SPBL. RQ1206_231 RQ1202_038 RQ1202_039 RQ1202_040 RQ1202_041 RQ1202_042 7 The SPBL sends to SI4_111_pdu_07 to the LBA. RQ1206_062 RQ1206_063 RQ1206_064 RQ1206_065 RQ1206_066 RQ1206_067 RQ1206_068 RQ1206_069 RQ1206_070 RQ1206_071 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.6.3.2 Si4 - SPB Manager service | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.6.3.2.1 SI4_66321 - Normal flow | Test ID SI4_66321 Test objectives To verify that no errors occur if the LBA (tester) stimulates the SPBM (SUT) with PDUs, and these PDUs are conveyed in Si4 semantic. Configuration reference CSI4_6612 Initial conditions The procedure PSI4_6621 shall be successfully executed. The SI4_121_pdu is generated by using the SI4_121_pdu configuration file. Test sequence Step Description Requirements 1 The LBA sends to SI4_121_pdu_01 to the SPBM. RQ1203_026 ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 158 Release 15 2 The SPBM sends to SI4_121_pdu_02 to the LBA. RQ1202_015 RQ1202_016 RQ1202_017 RQ1202_018 RQ1202_019 RQ1202_020 RQ1202_021 RQ1202_022 RQ1202_023 RQ1202_024 RQ1202_025 RQ1202_026 RQ1202_027 RQ1202_028 3 The LBA sends to SI4_121_pdu_02 to the SPBM. RQ1202_001 RQ1202_002 RQ1202_003 RQ1202_004 RQ1202_006 RQ1202_007 RQ1202_008 RQ1202_009 RQ1202_010 4 The SPBM sends to SI4_121_pdu_04 to the LBA. RQ1202_015 RQ1202_016 RQ1202_017 RQ1202_018 RQ1202_019 RQ1202_020 RQ1202_021 RQ1202_022 RQ1202_023 RQ1202_024 RQ1202_025 RQ1202_026 RQ1202_027 RQ1202_028 RQ1202_005 RQ1202_030 RQ1202_033 RQ1202_038 RQ1202_039 RQ1202_040 RQ1202_041 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.6.6.4 Requirements not testable, implicitly verified or verified elsewhere | The following requirements are generated from descriptive text. A verification by tests defined within the present document is not possible: RQ1202_005, RQ1202_029, RQ1202_031, RQ1202_032, RQ1202_034, RQ1202_035, RQ1202_036, RQ1202_037. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 159 Release 15 Annex A (informative): Core specification version information Unless otherwise specified, the versions of ETSI TS 103 666-2 [10] from which conformance requirements have been extracted are as follows: Release Latest version from which conformance requirements have been extracted 15 V15.3.0 (2020-09) ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 160 Release 15 Annex B (informative): Change History The table below indicates all changes that have been incorporated into the present document since it was published. Change history Date Meeting Plenary Doc CR Rev Cat Subject/Comment Old New 08/11/2021 SCP#102 SCP(21)000160r2 - - - Version 15.0.0 first publication - 15.0.0 ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 161 Release 15 History Document history V15.0.0 December 2021 Publication |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 1 Scope | The present document specifies the Near-RT RIC layer signalling protocol for the E2 interface. The E2 interface provides means for interconnecting a Near-RT RIC and an E2 Node. The E2 Application Protocol (E2AP) supports the functions of E2 interface by signalling procedures defined in the present document. E2AP is developed in accordance with the general principles stated in ETSI TS 104 038 [2]. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 2 References | |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at https://docbox.etsi.org/Reference. NOTE 1: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. NOTE 2: In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in 3GPP Release 17. The following referenced documents are necessary for the application of the present document. [1] Void. [2] ETSI TS 104 038: "Publicly Available Specification (PAS); E2 interface: General Aspects and Principles (O-RAN.WG3.E2GAP-R003-v04.01)". [3] ETSI TS 104 040: "Publicly Available Specification (PAS); E2 interface: Service Model (O-RAN.WG3.E2SM-R003-v04.00)". [4] Void. [5] Void. [6] Void. [7] Void. [8] ETSI TS 136 420: "LTE; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 general aspects and principles (3GPP TS 36.420)". [9] Void. [10] ETSI TS 138 410: "5G; NG-RAN; NG general aspects and principles (3GPP TS 38.410)". [11] ETSI TS 138 420: "5G; NG-RAN; Xn general aspects and principles (3GPP TS 38.420)". [12] ETSI TS 138 470: "5G; NG-RAN; F1 general aspects and principles (3GPP TS 38.470)". [13] ETSI TS 136 410: "LTE; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 general aspects and principles (3GPP TS 36.410)". [14] Void. [15] Recommendation ITU-T X.691 (07/2002): "Information technology - ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)". ETSI ETSI TS 104 039 V4.0.0 (2024-10) 9 [16] Recommendation ITU-T X.680 (07/2002): "Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation". [17] Recommendation ITU-T X.681 (07/2002): "Information technology - Abstract Syntax Notation One (ASN.1): Information object specification". [18] Void. [19] ETSI TS 138 413: "5G; NG-RAN; NG Application Protocol (NGAP) (3GPP TS 38.413)". [20] ETSI TS 138 423: "5G; NG-RAN; Xn Application Protocol (XnAP) (3GPP TS 38.423)". [21] ETSI TS 137 483: "5G; E1 Application Protocol (E1AP) (3GPP TS 37.483)". [22] ETSI TS 138 473: "5G; NG-RAN; F1 Application Protocol (F1AP) (3GPP TS 38.473)". [23] ETSI TS 137 473: "LTE; 5G; W1 interface; Application Protocol (W1AP) (3GPP TS 37.473)". [24] ETSI TS 136 413: "LTE; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) (3GPP TS 36.413)". [25] ETSI TS 136 423: "LTE; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) (3GPP TS 36.423)". [26] IETF RFC 5905: "Network Time Protocol Version 4: Protocol and Algorithms Specification". [27] ETSI TS 103 982: "Publicly Available Specification (PAS); O-RAN Architecture Description (O-RAN.WG1.OAD-R003-v08.00)". |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE 1: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. NOTE 2: In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in 3GPP Release 17. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TR 121 905: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; 5G; Vocabulary for 3GPP Specifications (3GPP TR 21.905)". [i.2] ETSI TR 125 921 (V7.0.0): "Universal Mobile Telecommunications System (UMTS); Guidelines and principles for protocol description and error handling (3GPP TR 25.921 version 7.0.0 Release 7)". ETSI ETSI TS 104 039 V4.0.0 (2024-10) 10 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 3 Definition of terms, symbols and abbreviations | |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 121 905 [i.1], ETSI TS 103 982 [27] and the following apply. NOTE: A term defined in the present document takes precedence over the definition of the same term, if any, in ETSI TR 121 905 [i.1] and ETSI TS 103 982 [27]. E2 Node Component ID: local identifier used to uniquely identify an E2 Node component Elementary Procedure: E2AP protocol consists of Elementary Procedures (EPs) NOTE: An E2AP Elementary Procedure is a unit of interaction between the Near-RT RIC and an E2 Node. An EP consists of an initiating message and possibly a response message. Two kinds of EPs are used: Class 1: Elementary Procedures with response (success or failure), Class 2: Elementary Procedures without response. Global E2 Node ID: global identifier of an E2 Node NOTE: Defined as the global eNB or gNB identifier and an optional local identifier of an CU-UP or DU which is required when and if an individual DU or CU-UP supports a direct E2 interface. Global RIC ID: global identifier of a Near-RT RIC RAN Function: specific Function in a E2 Node; examples include termination of network interfaces (i.e. X2 [8], F1 [12], S1 [13], Xn [11], NGc [10]) and RAN internal functions handling UEs, Cells, etc. RAN Function ID: local identifier of a specific RAN Function within an E2 Node that supports one or more RIC Services using a specific E2 Service Model RAN Function OID: RAN Function Object Identifier used to identify specific RAN function definition (i.e. E2SM used by specific RAN Function) RIC Action ID: local identifier used Near-RT RIC to identify a specific RIC Service Action within a specific RIC Subscription Request, used by E2 Node in subsequent RIC Indication messages RIC Call Process ID: local identifier used by E2 Node to identify the suspended associated procedure instance during an Insert RIC Service Action, used by Near-RT RIC in subsequent RIC Control procedure RIC Request ID: local identifier used to identify a specific RIC Functional procedure among all ongoing parallel procedures of the same type initiated by the same protocol peer NOTE: Messages belonging to the same procedure use the same RIC Request ID. The RIC Request ID is determined by the initiating peer of a RIC Functional Procedure. RIC Service: service provided on an E2 Node to provide access to messages and measurements and/or enable control of the E2 Node from the Near-RT RIC Transaction ID: local identifier used to uniquely identify a Global Procedure among all ongoing parallel procedures of the same type initiated by the same protocol peer NOTE: Messages belonging to the same procedure use the same Transaction ID. The Transaction ID is determined by the initiating peer of a Global Procedure (Near-RT RIC or E2 Node). |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 3.2 Symbols | Void. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 11 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TR 121 905 [i.1], ETSI TS 103 982 [27] and the following apply. NOTE: An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in ETSI TR 121 905 [i.1] and ETSI TS 103 982 [27]. EP Elementary Procedure |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 4 General | |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 4.1 Procedure Specification Principles | The principle for specifying the procedure logic is to specify the functional behaviour of the terminating node exactly and completely. Any rule that specifies the behaviour of the originating node shall be possible to be verified with information that is visible within the system. The following specification principles have been applied for the procedure text in clause 8: - The procedure text discriminates between: 1) Functionality which "shall" be executed. The procedure text indicates that the receiving node "shall" perform a certain function Y under a certain condition. If the receiving node supports procedure X but cannot perform functionality Y requested in the REQUEST message of a Class 1 EP, the receiving node shall respond with the message used to report unsuccessful outcome for this procedure, containing an appropriate cause value. 2) Functionality which "shall, if supported" be executed. The procedure text indicates that the receiving node "shall, if supported," perform a certain function Y under a certain condition. If the receiving node supports procedure X but does not support functionality Y, the receiving node shall proceed with the execution of the EP, possibly informing the requesting node about the not supported functionality. Any required inclusion of an optional IE in a response message is explicitly indicated in the procedure text. If the procedure text does not explicitly indicate that an optional IE shall be included in a response message, the optional IE shall not be included. For requirements on including Criticality Diagnostics IE, see clause 10. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 4.2 Forwards and Backwards Compatibility | The forwards and backwards compatibility of the protocol is assured by mechanism where all current and future messages, and IEs or groups of related IEs, include ID and criticality fields that are coded in a standard format that will not be changed in the future. These parts can always be decoded regardless of the standard version. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 4.3 Specification Notations | For the purposes of the present document, the following notations apply: Procedure When referring to an Elementary Procedure (EP) in the present document the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. Handover Preparation procedure. Message When referring to a message in the present document the MESSAGE NAME is written with all letters in upper case characters followed by the word "message", e.g. HANDOVER REQUEST message. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 12 IE When referring to an Information Element (IE) in the present document the Information Element Name is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation "IE", e.g. E-RAB ID IE. Value of an IE When referring to the value of an Information Element (IE) in the present document the "Value" is written as it is specified in the present document enclosed by quotation marks, e.g. "Value". |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 5 E2AP Services | |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 5.1 E2AP procedure modules | The E2 interface E2AP procedures are divided into two modules as follows: 1. RIC Functional Procedures; 2. Global Procedures. The RIC functional procedures module contains procedures used to pass application specific messages between Near-RT RIC applications and a target RAN Function in an E2 node [2]. The Global Procedures module contains procedures that are not directly related to a specific application. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 5.2 Parallel transactions | Parallel transactions, that is, multiple ongoing E2AP procedures related to the same Application and E2 node, are supported. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 6 Services expected from Signalling Transport | The signalling connection shall provide in sequence delivery of E2AP messages. E2AP shall be notified if the signalling connection breaks. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 7 Functions of E2AP | The functions of E2AP are described in ETSI TS 104 038 [2]. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8 E2AP Procedures | |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.1 Elementary Procedures | In Tables 8.1-1 and 8.1-2, all EPs are divided into Class 1 and Class 2 EPs. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 13 Table 8.1-1: Class 1 Elementary Procedures Initiated by Elementary Procedure Initiating Message Successful Outcome Unsuccessful Outcome Response message Response message Near-RT RIC RIC Subscription RIC SUBSCRIPTION REQUEST RIC SUBSCRIPTION RESPONSE RIC SUBSCRIPTION FAILURE Near-RT RIC RIC Subscription Delete RIC SUBSCRIPTION DELETE REQUEST RIC SUBSCRIPTION DELETE RESPONSE RIC SUBSCRIPTION DELETE FAILURE Near-RT RIC RIC Subscription Modification RIC SUBSCRIPTION MODIFICATION REQUEST RIC SUBSCRIPTION MODIFICATION RESPONSE RIC SUBSCRIPTION MODIFICATION FAILURE E2 Node RIC Subscription Modification Required RIC SUBSCRIPTION MODIFICATION REQUIRED RIC SUBSCRIPTION MODIFICATION CONFIRM RIC SUBSCRIPTION MODIFICATION REFUSE Near-RT RIC RIC Control RIC CONTROL REQUEST RIC CONTROL ACKNOWLEDGE RIC CONTROL FAILURE Near-RT RIC RIC Query RIC QUERY REQUEST RIC QUERY RESPONSE RIC QUERY FAILURE E2 Node E2 Setup E2 SETUP REQUEST E2 SETUP RESPONSE E2 SETUP FAILURE E2 Node RIC Service Update RIC SERVICE UPDATE RIC SERVICE UPDATE ACKNOWLEDGE RIC SERVICE UPDATE FAILURE E2 Node E2 Node Configuration Update E2 NODE CONFIGURATION UPDATE E2 NODE CONFIGURATION UPDATE ACKNOWLEDGE E2 NODE CONFIGURATION UPDATE FAILURE Near-RT RIC E2 Connection Update E2 CONNECTION UPDATE E2 CONNECTION UPDATE ACKNOWLEDGE E2 CONNECTION UPDATE FAILURE Near-RT RIC or E2 Node Reset RESET REQUEST RESET RESPONSE Near-RT RIC or E2 Node E2 Removal E2 REMOVAL REQUEST E2 REMOVAL RESPONSE E2 REMOVAL FAILURE Table 8.1-2: Class 2 Elementary Procedures Initiated by Elementary Procedure Initiating Message E2 Node RIC Indication RIC INDICATION Near-RT RIC RIC Service Query RIC SERVICE QUERY E2 Node RIC Subscription Delete Required RIC SUBSCRIPTION DELETE REQUIRED E2 Node or Near-RT RIC Error Indication ERROR INDICATION |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2 RIC Functional Procedures | |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.1 RIC Subscription procedure | |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.1.1 General | This procedure is used to establish RIC Subscriptions on E2 Node consisting of an event trigger and a sequence of RIC Service Actions. This procedure shall be initiated by the Near-RT RIC. This procedure uses RIC Service signalling. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 14 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.1.2 Successful Operation | Figure 8.2.1.2-1: RIC Subscription procedure, successful operation The Near-RT RIC initiates the procedure by sending a RIC SUBSCRIPTION REQUEST message, which shall contain a unique RIC Request ID IE, assigned by the Near-RT RIC, to the E2 Node. When the Near-RT RIC sends the RIC SUBSCRIPTION REQUEST message, it shall start the timer TRICEVENTcreate. At reception of the RIC SUBSCRIPTION REQUEST message the E2 Node shall: - Determine the target RAN Function using the information in the RAN Function ID IE and configure the requested event trigger using information in the RIC Subscription Details IE. - If one or more Report, Insert and/or Policy RIC Service Actions are included in the RIC Subscription Details IE then the target RAN Function shall validate the event trigger and requested action sequence and, if accepted, store the required RIC Request ID, RIC Event Trigger Definition IE and sequence of RIC Service Actions. - If optional RIC Subscription Start Time IE is present and has expired, then the E2 Node shall ignore the optional RIC Subscription Start Time IE. If the requested trigger and at least one required RIC Service Action are accepted by the E2 Node, the E2 Node shall reserve for each admitted RIC Service Action the necessary resources and send the RIC SUBSCRIPTION RESPONSE message back to the Near-RT RIC. The E2 Node shall include in the response message the RIC Service Actions for which resources have been prepared at the E2 Node in the RIC Actions Admitted List IE. The E2 Node shall include the RIC Service Actions that have not been admitted in the RIC Actions Not Admitted List IE with an appropriate cause value. Upon reception of the RIC SUBSCRIPTION RESPONSE message the Near-RT RIC shall stop timer TRICEVENTcreate and terminate the RIC Subscription procedure. If more than one RIC Service Actions has been accepted by the E2 Node then, at each occurrence of the common Event Trigger, the sequence of RIC Service Actions shall be executed according to the following considerations: - If optional RIC Action Execution Order IE is not present or is present and set to 0 ("Any order"), then the specific RIC Service Action in the sequence of RIC Service Actions may be executed in any order irrespective of the execution order of the other RIC Service Actions. - If optional RIC Action Execution Order IE is present and set to a value greater than 0, then the specific RIC Service Action shall be executed in order according to the RIC Action Execution Order IE. - If two or more RIC Service Actions have the same value for the optional RIC Action Execution Order IE then these RIC Service Actions shall be executed in parallel. If the optional RIC Subscription Start Time IE is present, the E2 Node shall only enable the event trigger from the indicated start time. If the optional RIC Subscription End Time IE is present, the E2 Node shall disable the event trigger when the indicated end time has expired. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 15 Interactions with RIC Subscription Delete Required procedure: If the optional RIC Subscription End Time IE is present and the indicated end time has expired, the E2 Node may send the RIC SUBSCRIPTION DELETE REQUIRED message to the Near-RT RIC with an appropriate cause value. Interactions with RIC Subscription Delete procedure: If the optional RIC Subscription End Time IE is present, the Near-RT RIC may initiate an RIC Subscription Delete procedure when the expected RIC Subscription End Time has expired. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.1.3 Unsuccessful Operation | Figure 8.2.1.3-1: RIC Subscription procedure, unsuccessful operation If a failure occurs during the RIC Subscription procedure the E2 Node shall send the RIC SUBSCRIPTION FAILURE message to the Near-RT RIC containing an appropriate cause value. If the E2 Node admits none of the requested RIC Service Actions, or detects an inconsistency in the sequence of RIC ServiceActions, or in the optional RIC Subsequent Action IE definitions, the E2 Node shall send the RIC SUBSCRIPTION FAILURE message to the Near-RT RIC containing an appropriate cause value. If the RIC Subscription procedure contains an invalid optional RIC Subscription Start Time IE and/or RIC Subscription End Time IE, the E2 Node shall send the RIC SUBSCRIPTION FAILURE message to the Near-RT RIC containing an appropriate cause value. Upon reception of the RIC SUBSCRIPTION FAILURE message the Near-RT RIC shall stop the timer TRICEVENTcreate and terminate the RIC Subscription procedure. Interactions with RIC Subscription Delete procedure: If there is no response from the E2 Node to the RIC SUBSCRIPTION REQUEST message before timer TRICEVENTcreate expires in the Near-RT RIC, the Near-RT RIC shall initiate the RIC Subscription Delete procedure containing RIC Request ID IE that was previously assigned by the Near-RT RIC to cancel the RIC Subscription towards the E2 Node. The Near-RT RIC shall ignore any RIC SUBSCRIPTION RESPONSE or RIC SUBSCRIPTION FAILURE message containing RIC Request ID IE that was previously assigned by the Near-RT RIC received after the initiation of the RIC Subscription Delete procedure and release any resources related to the concerned E2 Node. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.1.4 Abnormal Conditions | If the E2 Node receives a RIC SUBSCRIPTION REQUEST message containing RIC Subscription Details IE that does not align with the E2 Service Model [3], the E2 Node shall send the RIC SUBSCRIPTION FAILURE message to the Near-RT RIC containing an appropriate cause value. If the E2 Node receives a RIC SUBSCRIPTION REQUEST message which contains an unknown RAN Function ID IE, the E2 Node shall send the RIC SUBSCRIPTION FAILURE message to the Near-RT RIC containing an appropriate cause value. If the E2 Node receives a RIC SUBSCRIPTION REQUEST message containing identical contents the E2 Node shall send the RIC SUBSCRIPTION FAILURE message to the Near-RT RIC containing an appropriate cause value. ETSI ETSI TS 104 039 V4.0.0 (2024-10) 16 |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.2 RIC Subscription Delete procedure | |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.2.1 General | This procedure is used to delete RIC Subscriptions on E2 Node. This procedure shall be initiated by the Near-RT RIC. This procedure uses RIC Service signalling. |
3d09c7ebf7740b0683ab7944c0538513 | 104 039 | 8.2.2.2 Successful Operation | Figure 8.2.2.2-1: RIC Subscription Delete procedure, successful operation The Near-RT RIC initiates the procedure by sending a RIC SUBSCRIPTION DELETE REQUEST message, containing RIC Request ID IE that was previously assigned by the Near-RT RIC during a successful RIC Subscription procedure, to the E2 Node. When the Near-RT RIC sends the RIC SUBSCRIPTION DELETE REQUEST message, it shall start timer TRICEVENTdelete. At reception of the RIC SUBSCRIPTION DELETE REQUEST message the E2 Node shall delete the indicated RIC Subscription and release the corresponding necessary resources. The E2 Node shall send the RIC SUBSCRIPTION DELETE RESPONSE message back to the Near-RT RIC. Upon reception of the RIC SUBSCRIPTION DELETE RESPONSE message the Near-RT RIC shall stop timer TRICEVENTdelete, release any necessary resources associated with that RIC Subscription and terminate the RIC Subscription Delete procedure. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.