HNBAP: Remove HNBRegisterAccept / HNBRegisterResposne naming inconsistency
A HNBRegisterAccept message should not contain HNBRegisterResponse IEs
This spec inconsistency is confusing the asn1tostruct.py code generator,
so let's remove it.
diff --git a/asn1/hnbap/HNBAP-PDU-Contents.asn b/asn1/hnbap/HNBAP-PDU-Contents.asn
index 1942b0a..8f00967 100644
--- a/asn1/hnbap/HNBAP-PDU-Contents.asn
+++ b/asn1/hnbap/HNBAP-PDU-Contents.asn
@@ -164,17 +164,17 @@
-- **************************************************************
HNBRegisterAccept ::= SEQUENCE {
- protocolIEs ProtocolIE-Container { {HNBRegisterResponseIEs} },
- protocolExtensions ProtocolExtensionContainer { {HNBRegisterResponseExtensions} } OPTIONAL,
+ protocolIEs ProtocolIE-Container { {HNBRegisterAcceptIEs} },
+ protocolExtensions ProtocolExtensionContainer { {HNBRegisterAcceptExtensions} } OPTIONAL,
...
}
-HNBRegisterResponseIEs HNBAP-PROTOCOL-IES ::= {
+HNBRegisterAcceptIEs HNBAP-PROTOCOL-IES ::= {
{ ID id-RNC-ID CRITICALITY reject TYPE RNC-ID PRESENCE mandatory },
...
}
-HNBRegisterResponseExtensions HNBAP-PROTOCOL-EXTENSION ::= {
+HNBRegisterAcceptExtensions HNBAP-PROTOCOL-EXTENSION ::= {
-- Extension for Release 9 to support CS Multiplexing --
{ ID id-MuxPortNumber CRITICALITY ignore EXTENSION MuxPortNumber PRESENCE optional}|
{ ID id-Iurh-Signalling-TNL-Address CRITICALITY ignore EXTENSION IP-Address PRESENCE optional}|