cellular-infrastructure
/
osmo-iuh
mirror of https://gerrit.osmocom.org/osmo-iuh
9
0
Fork 0
Code Issues Releases Wiki Activity

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.
This commit is contained in:
Harald Welte 2015-08-30 20:11:50 +02:00
parent 8d6026742f
commit 1c2b568d79
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
asn1/hnbap/HNBAP-PDU-Contents.asn
View File

@ -164,17 +164,17 @@ HNBRegisterRequestExtensions HNBAP-PROTOCOL-EXTENSION ::= {
-- **************************************************************
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}|