-
Bug
-
Resolution: Done
-
Medium
-
None
-
None
-
None
[we close this issue as it was against an older version of RIC. It has been already fixed by https://gerrit.o-ran-sc.org/r/gitweb?p=ric-plt/e2mgr.git;a=commit;h=d2f1a29d3f1cc779045148a82729f644e6110776 ]
I am unsure if I wrote this correctly so I am providing the information here again in case I made any mistake.
The bug has been created for the https://gerrit.o-ran-sc.org/r/gitweb?p=ric-plt/e2mgr.git;a=tree repository.
There is a problem in which if an E2SetupRequest message is sent with E2nodeComponentConfigAddition entry which contains a GNB information specified through the XN interface makes the e2mgr generate an incorrect XML message which is sent to the e2interface.
Our E2SetupRequest contains the following field:
<E2nodeComponentConfigAddition-Item> <e2nodeComponentInterfaceType> <xn/> </e2nodeComponentInterfaceType> <e2nodeComponentID> <e2nodeComponentInterfaceTypeXn> <global-NG-RAN-Node-ID> <gNB> <plmn-id>00F110</plmn-id> <gnb-id> <gnb-ID>000100100011010001010110</gnb-ID> </gnb-id> </gNB> </global-NG-RAN-Node-ID> </e2nodeComponentInterfaceTypeXn> </e2nodeComponentID> <e2nodeComponentConfiguration> <e2nodeComponentRequestPart> <XnAP-PDU> <initiatingMessage> <procedureCode>18</procedureCode> <criticality> <reject/> </criticality> <value> <NGRANNodeConfigurationUpdate> <protocolIEs> <NGRANNodeConfigurationUpdate-IEs> <id>9</id> <criticality> <ignore/> </criticality> <value> <ConfigurationUpdateInitiatingNodeChoice> <gNB> <ConfigurationUpdate-gNB> <id>68</id> <criticality> <ignore/> </criticality> <value> <ServedCellsToUpdate-NR> <served-Cells-ToAdd-NR> <ServedCells-NR-Item> <served-cell-info-NR> <nrPCI>1</nrPCI> <cellID> <plmn-id>00F110</plmn-id> <nr-CI>000100100011010001010110000000000001</nr-CI> </cellID> <tac>7F6F4B</tac> <broadcastPLMN> <PLMN-Identity>00F110</PLMN-Identity> </broadcastPLMN> <nrModeInfo> <tdd> <nrFrequencyInfo> <nrARFCN>644667</nrARFCN> <frequencyBand-List> <NRFrequencyBandItem> <nr-frequency-band>77</nr-frequency-band> </NRFrequencyBandItem> </frequencyBand-List> </nrFrequencyInfo> <nrTransmissonBandwidth> <nRSCS> <scs15/> </nRSCS> <nRNRB> <nrb270/> </nRNRB> </nrTransmissonBandwidth> </tdd> </nrModeInfo> <measurementTimingConfiguration> <MeasurementTimingConfiguration> <criticalExtensions> <c1> <measTimingConf> <measTiming> <MeasTiming> <frequencyAndTiming> <carrierFreq>2076667</carrierFreq> <ssbSubcarrierSpacing> <kHz240/> </ssbSubcarrierSpacing> <ssb-RRC-MeasurementTimingConfiguration> <periodicityAndOffset> <sf20>5</sf20> </periodicityAndOffset> <duration> <sf3/> </duration> </ssb-RRC-MeasurementTimingConfiguration> </frequencyAndTiming> </MeasTiming> </measTiming> </measTimingConf> </c1> </criticalExtensions> </MeasurementTimingConfiguration> </measurementTimingConfiguration> <connectivitySupport> <eNDC-Support> <supported/> </eNDC-Support> </connectivitySupport> </served-cell-info-NR> </ServedCells-NR-Item> </served-Cells-ToAdd-NR> </ServedCellsToUpdate-NR> </value> </ConfigurationUpdate-gNB> </gNB> </ConfigurationUpdateInitiatingNodeChoice> </value> </NGRANNodeConfigurationUpdate-IEs> </protocolIEs> </NGRANNodeConfigurationUpdate> </value> </initiatingMessage> </XnAP-PDU> </e2nodeComponentRequestPart> <e2nodeComponentResponsePart/> </e2nodeComponentConfiguration> </E2nodeComponentConfigAddition-Item>
The e2mgr sends after parsing the information exactly this:
<E2AP-PDU> <successfulOutcome> <procedureCode>1</procedureCode> <criticality> <reject/> </criticality> <value> <E2setupResponse> <protocolIEs> <E2setupResponseIEs> <id>49</id> <criticality> <reject/> </criticality> <value> <TransactionID>1</TransactionID> </value> </E2setupResponseIEs> <E2setupResponseIEs> <id>4</id> <criticality> <reject/> </criticality> <value> <GlobalRIC-ID> <pLMN-Identity>131014</pLMN-Identity> <ric-ID>10101010110011001110</ric-ID> </GlobalRIC-ID> </value> </E2setupResponseIEs> <E2setupResponseIEs> <id>9</id> <criticality> <reject/> </criticality> <value> <RANfunctionsID-List> <ProtocolIE-SingleContainer> <id>6</id> <criticality> <ignore/> </criticality> <value> <RANfunctionID-Item> <ranFunctionID>2</ranFunctionID> <ranFunctionRevision>203</ranFunctionRevision> </RANfunctionID-Item> </value> </ProtocolIE-SingleContainer> <ProtocolIE-SingleContainer> <id>6</id> <criticality> <ignore/> </criticality> <value> <RANfunctionID-Item> <ranFunctionID>3</ranFunctionID> <ranFunctionRevision>101</ranFunctionRevision> </RANfunctionID-Item> </value> </ProtocolIE-SingleContainer> </RANfunctionsID-List> </value> </E2setupResponseIEs> <E2setupResponseIEs> <id>52</id> <criticality> <reject/> </criticality> <value> <E2nodeComponentConfigAdditionAck-List> <ProtocolIE-SingleContainer> <id>53</id> <criticality> <reject/> </criticality> <value> <E2nodeComponentConfigAdditionAck-Item> <e2nodeComponentInterfaceType> <f1/> </e2nodeComponentInterfaceType> <e2nodeComponentID> <e2nodeComponentInterfaceTypeF1> <gNB-DU-ID>0</gNB-DU-ID> </e2nodeComponentInterfaceTypeF1> </e2nodeComponentID> <e2nodeComponentConfigurationAck> <updateOutcome> <success/> </updateOutcome> </e2nodeComponentConfigurationAck> </E2nodeComponentConfigAdditionAck-Item> </value> </ProtocolIE-SingleContainer> <ProtocolIE-SingleContainer> <id>53</id> <criticality> <reject/> </criticality> <value> <E2nodeComponentConfigAdditionAck-Item> <e2nodeComponentInterfaceType> <e1/> </e2nodeComponentInterfaceType> <e2nodeComponentID> <e2nodeComponentInterfaceTypeE1> <gNB-CU-CP-ID>0</gNB-CU-CP-ID> </e2nodeComponentInterfaceTypeE1> </e2nodeComponentID> <e2nodeComponentConfigurationAck> <updateOutcome> <success/> </updateOutcome> </e2nodeComponentConfigurationAck> </E2nodeComponentConfigAdditionAck-Item> </value> </ProtocolIE-SingleContainer> <ProtocolIE-SingleContainer> <id>53</id> <criticality> <reject/> </criticality> <value> <E2nodeComponentConfigAdditionAck-Item> <e2nodeComponentInterfaceType> <xn/> </e2nodeComponentInterfaceType> <e2nodeComponentID> <e2nodeComponentInterfaceTypeXn> <global-NG-RAN-Node-ID> <gNB> <plmn-id>00F110</plmn-id> <gnb-id> <gnb-ID>000100100011010001010110</gnb-ID> </gnb-id> </gNB> <ng-eNB> <plmn-id/> <gnb-id> <enb-ID-macro/> <enb-ID-shortmacro/> <enb-ID-longmacro/> </gnb-id> </ng-eNB> </global-NG-RAN-Node-ID> </e2nodeComponentInterfaceTypeXn> </e2nodeComponentID> <e2nodeComponentConfigurationAck> <updateOutcome> <success/> </updateOutcome> </e2nodeComponentConfigurationAck> </E2nodeComponentConfigAdditionAck-Item> </value> </ProtocolIE-SingleContainer> </E2nodeComponentConfigAdditionAck-List> </value> </E2setupResponseIEs> </protocolIEs> </E2setupResponse> </value> </successfulOutcome> </E2AP-PDU>
The ng-ENB part should not be present and breaks the connection.
I have added here a PCAP file which contains our E2SetupRequest and also the messages that the e2mgr sends back to the e2 interface component.
For indication the E2AP setup request is the packet no: 47 and the incorrect XML is sent at packet no: 64. I have also attached the packet information as a text capture. In case this is confusing you can use the pcap which is much clearer.
