<p>neels has uploaded this change for <strong>review</strong>.</p><p><a href="https://gerrit.osmocom.org/c/osmo-bts/+/23846">View Change</a></p><pre style="font-family: monospace,monospace; white-space: pre-wrap;">Abis manual: s/TS 12.21/TS 52.021<br><br>Change-Id: I662a3419a6ec741fe162ccc7c7221df20b2780b1<br>---<br>M doc/manuals/abis/oml.adoc<br>1 file changed, 53 insertions(+), 52 deletions(-)<br><br></pre><pre style="font-family: monospace,monospace; white-space: pre-wrap;">git pull ssh://gerrit.osmocom.org:29418/osmo-bts refs/changes/46/23846/1</pre><pre style="font-family: monospace,monospace; white-space: pre-wrap;"><span>diff --git a/doc/manuals/abis/oml.adoc b/doc/manuals/abis/oml.adoc</span><br><span>index 4afcec0..0fbd321 100644</span><br><span>--- a/doc/manuals/abis/oml.adoc</span><br><span>+++ b/doc/manuals/abis/oml.adoc</span><br><span>@@ -3,16 +3,17 @@</span><br><span> === List of Messages</span><br><span> </span><br><span> The following tables list the OML messages used by OsmoBTS, grouped by their</span><br><span style="color: hsl(0, 100%, 40%);">-level of compliance with 3GPP TS 12.21.</span><br><span style="color: hsl(120, 100%, 40%);">+level of compliance with 3GPP TS 52.021 [[3gpp-ts-52-021]] (previously 3GPP TS</span><br><span style="color: hsl(120, 100%, 40%);">+12.21).</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-==== Messages Compliant With TS 12.21</span><br><span style="color: hsl(120, 100%, 40%);">+==== Messages Compliant With TS 52.021</span><br><span> </span><br><span> Specific limitations apply, see the linked sections.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-.Messages compliant with TS 12.21</span><br><span style="color: hsl(120, 100%, 40%);">+.Messages compliant with TS 52.021</span><br><span> [options="header",cols="10%,10%,20%,35%,5%,20%"]</span><br><span> |===</span><br><span style="color: hsl(0, 100%, 40%);">-| TS 12.21 § | type code (hex) | This document § | Message | <-/-> | Received/Sent by OsmoBTS</span><br><span style="color: hsl(120, 100%, 40%);">+| TS 52.021 § | type code (hex) | This document § | Message | <-/-> | Received/Sent by OsmoBTS</span><br><span> 6+<| *SW Download Management Messages:*</span><br><span> | 8.3.7 | 0x10 | <<sw_act_rep>> | SW Activated Report | -> | Sent</span><br><span> 6+<| *Air Interface Management Messages:*</span><br><span>@@ -39,7 +40,7 @@</span><br><span> </span><br><span> ==== Messages Specific to OsmoBTS</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-.Messages specific to OsmoBTS, not found in 3GPP TS 12.21</span><br><span style="color: hsl(120, 100%, 40%);">+.Messages specific to OsmoBTS, not found in 3GPP TS 52.021</span><br><span> [options="header"]</span><br><span> [options="header",cols="20%,55%,5%,20%"]</span><br><span> |===</span><br><span>@@ -49,10 +50,10 @@</span><br><span> </span><br><span> </span><br><span> ==== Messages Not Implemented by OsmoBTS</span><br><span style="color: hsl(0, 100%, 40%);">-.3GPP TS 12.21 messages not implemented by OsmoBTS</span><br><span style="color: hsl(120, 100%, 40%);">+.3GPP TS 52.021 messages not implemented by OsmoBTS</span><br><span> [options="header",cols="10%,10%,80%"]</span><br><span> |===</span><br><span style="color: hsl(0, 100%, 40%);">-| TS 12.21 § | type code (hex) | Message</span><br><span style="color: hsl(120, 100%, 40%);">+| TS 52.021 § | type code (hex) | Message</span><br><span> 3+<| *SW Download Management Messages:*</span><br><span> .3+.| 8.3.1 | 0x01 | Load Data Initiate</span><br><span> | 0x02 | Load Data Initiate Ack</span><br><span>@@ -151,7 +152,7 @@</span><br><span> ==== SW Activated Report</span><br><span> </span><br><span> OsmoBTS will send an _SW Activated Report_ when RF has been activated</span><br><span style="color: hsl(0, 100%, 40%);">-successfully. The message is compliant with 3GPP TS 12.21 § 8.3.7.</span><br><span style="color: hsl(120, 100%, 40%);">+successfully. The message is compliant with 3GPP TS 52.021 § 8.3.7.</span><br><span> </span><br><span> Upon RF activation, two _SW Activated Report_ messages will be sent, for the Object Classes</span><br><span> </span><br><span>@@ -163,13 +164,13 @@</span><br><span> </span><br><span> OsmoBTS will receive a _Set BTS Attributes_ message and reply with a</span><br><span> corresponding ACK message on success. IE handling is fully compliant to TS</span><br><span style="color: hsl(0, 100%, 40%);">-12.21, except that a change of BCCH ARFCN or BSIC while in operation is not</span><br><span style="color: hsl(120, 100%, 40%);">+52.021, except that a change of BCCH ARFCN or BSIC while in operation is not</span><br><span> supported, and hence the _Starting Time_ IE is rejected.</span><br><span> </span><br><span> ._Set BTS Attributes_ IEs not handled by OsmoBTS</span><br><span> [options="header",cols="10%,30%,60%"]</span><br><span> |===</span><br><span style="color: hsl(0, 100%, 40%);">-| TS 12.21 § | IE Name | Handling</span><br><span style="color: hsl(120, 100%, 40%);">+| TS 52.021 § | IE Name | Handling</span><br><span> | 9.4.52 | Starting Time | not supported (provokes NACK cause 0x10)</span><br><span> |===</span><br><span> </span><br><span>@@ -177,13 +178,13 @@</span><br><span> [[set_radio_attr]]</span><br><span> ==== Set Radio Carrier Attributes</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-This message conforms to 3GPP TS 12.21, with the following limitation,</span><br><span style="color: hsl(120, 100%, 40%);">+This message conforms to 3GPP TS 52.021, with the following limitation,</span><br><span> as frequency hopping is not supported by OsmoBTS:</span><br><span> </span><br><span> ._Set Radio Carrier Attributes_ IE limitations</span><br><span> [options="header",cols="10%,30%,60%"]</span><br><span> |===</span><br><span style="color: hsl(0, 100%, 40%);">-| TS 12.21 § | IE Name | Handling</span><br><span style="color: hsl(120, 100%, 40%);">+| TS 52.021 § | IE Name | Handling</span><br><span> | 9.4.5 | ARFCN List | ignored</span><br><span> |===</span><br><span> </span><br><span>@@ -191,14 +192,14 @@</span><br><span> [[set_chan_attr]]</span><br><span> ==== Set Channel Attributes</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-This message conforms to 3GPP TS 12.21, with the following limitation: the</span><br><span style="color: hsl(0, 100%, 40%);">-following 3GPP TS 12.21 IEs provoke a NACK response when sent to OsmoBTS, as</span><br><span style="color: hsl(120, 100%, 40%);">+This message conforms to 3GPP TS 52.021, with the following limitation: the</span><br><span style="color: hsl(120, 100%, 40%);">+following 3GPP TS 52.021 IEs provoke a NACK response when sent to OsmoBTS, as</span><br><span> frequency hopping is not supported:</span><br><span> </span><br><span> ._Set Channel Attributes_ IE limitations</span><br><span> [options="header",cols="10%,30%,60%"]</span><br><span> |===</span><br><span style="color: hsl(0, 100%, 40%);">-| TS 12.21 § | IE Name | Handling</span><br><span style="color: hsl(120, 100%, 40%);">+| TS 52.021 § | IE Name | Handling</span><br><span> | 9.4.21 | HSN | not supported (provokes NACK cause 0x10)</span><br><span> | 9.4.27 | MAIO | not supported (provokes NACK cause 0x10)</span><br><span> | 9.4.52 | Starting Time | not supported (provokes NACK cause 0x10)</span><br><span>@@ -207,32 +208,32 @@</span><br><span> [[state_changed_rep]]</span><br><span> ==== State Changed Event Report</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-This message is compliant with 3GPP TS 12.21. Exactly these IEs are sent by</span><br><span style="color: hsl(120, 100%, 40%);">+This message is compliant with 3GPP TS 52.021. Exactly these IEs are sent by</span><br><span> OsmoBTS:</span><br><span> </span><br><span> [options="header"]</span><br><span> [cols="30%,25%,15%,15%,15%"]</span><br><span> |===</span><br><span> | INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH</span><br><span style="color: hsl(0, 100%, 40%);">-| Message Type (0xf5) | 3GPP TS 12.21 9.1 | M | V | 1</span><br><span style="color: hsl(0, 100%, 40%);">-| Object Class | 3GPP TS 12.21 9.2 | M | V | 1</span><br><span style="color: hsl(0, 100%, 40%);">-| Object Instance | 3GPP TS 12.21 9.3 | M | V | 3</span><br><span style="color: hsl(0, 100%, 40%);">-| Operational State | 3GPP TS 12.21 9.4.38 | O | TV | 2</span><br><span style="color: hsl(0, 100%, 40%);">-| Availability Status | 3GPP TS 12.21 9.4.7 | O | TL16V (with length of 1) | 3</span><br><span style="color: hsl(120, 100%, 40%);">+| Message Type (0xf5) | 3GPP TS 52.021 9.1 | M | V | 1</span><br><span style="color: hsl(120, 100%, 40%);">+| Object Class | 3GPP TS 52.021 9.2 | M | V | 1</span><br><span style="color: hsl(120, 100%, 40%);">+| Object Instance | 3GPP TS 52.021 9.3 | M | V | 3</span><br><span style="color: hsl(120, 100%, 40%);">+| Operational State | 3GPP TS 52.021 9.4.38 | O | TV | 2</span><br><span style="color: hsl(120, 100%, 40%);">+| Availability Status | 3GPP TS 52.021 9.4.7 | O | TL16V (with length of 1) | 3</span><br><span> |===</span><br><span> </span><br><span> [[chg_adm_state]]</span><br><span> ==== Change Administrative State</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-This message is compliant with 3GPP TS 12.21 § 8.8.5. It applies to all of the</span><br><span style="color: hsl(0, 100%, 40%);">-Object Classes defined in 3GPP TS 12.21 § 9.2 as well as</span><br><span style="color: hsl(120, 100%, 40%);">+This message is compliant with 3GPP TS 52.021 § 8.8.5. It applies to all of the</span><br><span style="color: hsl(120, 100%, 40%);">+Object Classes defined in 3GPP TS 52.021 § 9.2 as well as</span><br><span> <<addnl_obj_classes>>.</span><br><span> </span><br><span> [[opstart]]</span><br><span> ==== Opstart</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-This message is compliant with 3GPP TS 12.21 § 8.9.2. It applies to all of the</span><br><span style="color: hsl(0, 100%, 40%);">-Object Classes defined in 3GPP TS 12.21 § 9.2 as well as</span><br><span style="color: hsl(120, 100%, 40%);">+This message is compliant with 3GPP TS 52.021 § 8.9.2. It applies to all of the</span><br><span style="color: hsl(120, 100%, 40%);">+Object Classes defined in 3GPP TS 52.021 § 9.2 as well as</span><br><span> <<addnl_obj_classes>>.</span><br><span> </span><br><span> </span><br><span>@@ -252,9 +253,9 @@</span><br><span> [cols="30%,25%,15%,15%,15%"]</span><br><span> |===</span><br><span> | INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH</span><br><span style="color: hsl(0, 100%, 40%);">-| Message Type (0xf5) | 3GPP TS 12.21 9.1 | M | V | 1</span><br><span style="color: hsl(0, 100%, 40%);">-| Object Class | 3GPP TS 12.21 9.2 | M | V | 1</span><br><span style="color: hsl(0, 100%, 40%);">-| Object Instance | 3GPP TS 12.21 9.3 | M | V | 3</span><br><span style="color: hsl(120, 100%, 40%);">+| Message Type (0xf5) | 3GPP TS 52.021 9.1 | M | V | 1</span><br><span style="color: hsl(120, 100%, 40%);">+| Object Class | 3GPP TS 52.021 9.2 | M | V | 1</span><br><span style="color: hsl(120, 100%, 40%);">+| Object Instance | 3GPP TS 52.021 9.3 | M | V | 3</span><br><span> 5+<| _Object Class specific IEs follow, see <<addnl_obj_classes>>..._</span><br><span> |===</span><br><span> </span><br><span>@@ -262,7 +263,7 @@</span><br><span> [[addnl_obj_classes]]</span><br><span> === Additional Object Classes</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-In addition to 3GPP TS 12.21 Chapter 9.2, the following managed objects</span><br><span style="color: hsl(120, 100%, 40%);">+In addition to 3GPP TS 52.021 Chapter 9.2, the following managed objects</span><br><span> are supported:</span><br><span> </span><br><span> .Additional Managed Object Classes</span><br><span>@@ -284,9 +285,9 @@</span><br><span> [cols="30%,25%,15%,15%,15%"]</span><br><span> |===</span><br><span> | INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH</span><br><span style="color: hsl(0, 100%, 40%);">-| Message Type | 3GPP TS 12.21 9.1 | M | V | 1</span><br><span style="color: hsl(0, 100%, 40%);">-| Object Class | 3GPP TS 12.21 9.2 | M | V | 1</span><br><span style="color: hsl(0, 100%, 40%);">-| Object Instance | 3GPP TS 12.21 9.3 | M | V | 3</span><br><span style="color: hsl(120, 100%, 40%);">+| Message Type | 3GPP TS 52.021 9.1 | M | V | 1</span><br><span style="color: hsl(120, 100%, 40%);">+| Object Class | 3GPP TS 52.021 9.2 | M | V | 1</span><br><span style="color: hsl(120, 100%, 40%);">+| Object Instance | 3GPP TS 52.021 9.3 | M | V | 3</span><br><span> | GPRS NSEI | <<NM_ATT_IPACC_NSEI>> | O | TL16V | >= 5</span><br><span> | GPRS NS Configuration | <<NM_ATT_IPACC_NS_LINK_CFG>> | O | TL16V | >= 10</span><br><span> | GPRS BSSGP Configuration | <<NM_ATT_IPACC_BSSGP_CFG>> | O | TL16V | >= 14</span><br><span>@@ -301,9 +302,9 @@</span><br><span> [cols="30%,25%,15%,15%,15%"]</span><br><span> |===</span><br><span> | INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH</span><br><span style="color: hsl(0, 100%, 40%);">-| Message Type | 3GPP TS 12.21 9.1 | M | V | 1</span><br><span style="color: hsl(0, 100%, 40%);">-| Object Class | 3GPP TS 12.21 9.2 | M | V | 1</span><br><span style="color: hsl(0, 100%, 40%);">-| Object Instance | 3GPP TS 12.21 9.3 | M | V | 3</span><br><span style="color: hsl(120, 100%, 40%);">+| Message Type | 3GPP TS 52.021 9.1 | M | V | 1</span><br><span style="color: hsl(120, 100%, 40%);">+| Object Class | 3GPP TS 52.021 9.2 | M | V | 1</span><br><span style="color: hsl(120, 100%, 40%);">+| Object Instance | 3GPP TS 52.021 9.3 | M | V | 3</span><br><span> | GPRS Routing Area Code | <<NM_ATT_IPACC_RAC>> | O | TL16V | >= 4</span><br><span> | GPRS Paging Configuration | <<NM_ATT_IPACC_GPRS_PAGING_CFG>> | O | TL16V | >= 5</span><br><span> | GPRS RLC Configuration | <<NM_ATT_IPACC_RLC_CFG>> | O | TL16V | >= 12</span><br><span>@@ -321,9 +322,9 @@</span><br><span> [cols="30%,25%,15%,15%,15%"]</span><br><span> |===</span><br><span> | INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH</span><br><span style="color: hsl(0, 100%, 40%);">-| Message Type | 3GPP TS 12.21 9.1 | M | V | 1</span><br><span style="color: hsl(0, 100%, 40%);">-| Object Class | 3GPP TS 12.21 9.2 | M | V | 1</span><br><span style="color: hsl(0, 100%, 40%);">-| Object Instance | 3GPP TS 12.21 9.3 | M | V | 3</span><br><span style="color: hsl(120, 100%, 40%);">+| Message Type | 3GPP TS 52.021 9.1 | M | V | 1</span><br><span style="color: hsl(120, 100%, 40%);">+| Object Class | 3GPP TS 52.021 9.2 | M | V | 1</span><br><span style="color: hsl(120, 100%, 40%);">+| Object Instance | 3GPP TS 52.021 9.3 | M | V | 3</span><br><span> | GPRS NSVCI | <<NM_ATT_IPACC_NSVCI>> | O | TL16V | >= 5</span><br><span> | GPRS NS Link Configuration | <<NM_ATT_IPACC_NS_LINK_CFG>> | O | TL16V | >= 11</span><br><span> |===</span><br><span>@@ -332,9 +333,9 @@</span><br><span> === Information Elements Overview</span><br><span> </span><br><span> All of the IEs handled by OsmoBTS are listed below, with limitations and</span><br><span style="color: hsl(0, 100%, 40%);">-additions to TS 12.21 specified in more detail.</span><br><span style="color: hsl(120, 100%, 40%);">+additions to TS 52.021 specified in more detail.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-==== IEs Conforming to TS 12.21</span><br><span style="color: hsl(120, 100%, 40%);">+==== IEs Conforming to TS 52.021</span><br><span> </span><br><span> The following Information Elements are accepted by OsmoBTS.</span><br><span> </span><br><span>@@ -346,10 +347,10 @@</span><br><span> (<-) are in fact parsed and their values are stored by OsmoBTS, but these</span><br><span> stored items are currently not used in the OsmoBTS code base.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-.IEs conforming to TS 12.21</span><br><span style="color: hsl(120, 100%, 40%);">+.IEs conforming to TS 52.021</span><br><span> [options="header",cols="5%,10%,40%,5%,40%"]</span><br><span> |===</span><br><span style="color: hsl(0, 100%, 40%);">-| tag (hex) | TS 12.21 § | IE name | <-/-> | Received/Sent by OsmoBTS</span><br><span style="color: hsl(120, 100%, 40%);">+| tag (hex) | TS 52.021 § | IE name | <-/-> | Received/Sent by OsmoBTS</span><br><span> | 0x00 | 9.4.1 | Abis Channel | | _ignored_</span><br><span> | 0x01 | 9.4.2 | Additional Info | | _ignored_</span><br><span> | 0x02 | 9.4.3 | Additional Text | | _ignored_</span><br><span>@@ -413,12 +414,12 @@</span><br><span> | 0x47 | 9.4.32 | Measurement Result | | _ignored_</span><br><span> |===</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-==== IEs Not Conforming to TS 12.21</span><br><span style="color: hsl(120, 100%, 40%);">+==== IEs Not Conforming to TS 52.021</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-.IEs not conforming to TS 12.21</span><br><span style="color: hsl(120, 100%, 40%);">+.IEs not conforming to TS 52.021</span><br><span> [options="header",cols="5%,10%,30%,55%"]</span><br><span> |===</span><br><span style="color: hsl(0, 100%, 40%);">-| tag (hex) | TS 12.21 § | IE name | Description</span><br><span style="color: hsl(120, 100%, 40%);">+| tag (hex) | TS 52.021 § | IE name | Description</span><br><span> | 0x15 | 9.4.21 | HSN | presence causes NACK response</span><br><span> | 0x17 | 9.4.23 | HW Description | _ignored_ by OsmoBTS, but coding may differ, see <<ie_hw_desc>></span><br><span> | 0x1b | 9.4.27 | MAIO | presence causes NACK response </span><br><span>@@ -431,14 +432,14 @@</span><br><span> ==== Additional Attributes and Parameters</span><br><span> </span><br><span> The following Information Elements are defined in addition to those</span><br><span style="color: hsl(0, 100%, 40%);">-specified in 3GPP TS 12.21 Chapter 9.4.</span><br><span style="color: hsl(120, 100%, 40%);">+specified in 3GPP TS 52.021 Chapter 9.4.</span><br><span> </span><br><span> All of these additional IEs are _received_ by OsmoBTS.</span><br><span> </span><br><span> These attributes are not used by OsmoBTS, but</span><br><span> simply passed to OsmoPCU connected to the PCU socket.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-.Additional IEs handled by OsmoBTS but not defined in TS 12.21</span><br><span style="color: hsl(120, 100%, 40%);">+.Additional IEs handled by OsmoBTS but not defined in TS 52.021</span><br><span> [options="header",cols="5%,50%,45%"]</span><br><span> |===</span><br><span> | tag (hex) | IE name | Description</span><br><span>@@ -465,7 +466,7 @@</span><br><span> [[ie_hw_desc]]</span><br><span> ==== HW Description</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-TS 12.21 suggests a series of 5 length-value pairs for the _HW Description_ IE.</span><br><span style="color: hsl(120, 100%, 40%);">+TS 52.021 suggests a series of 5 length-value pairs for the _HW Description_ IE.</span><br><span> Instead, OsmoBTS interprets it as a single TL16V. The value of this IE is</span><br><span> ignored by OsmoBTS, yet the coding may affect message parsing.</span><br><span> </span><br><span>@@ -487,7 +488,7 @@</span><br><span> [[ie_chan_comb]]</span><br><span> ==== Additional Channel Combinations</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-In addition to 3GPP TS 12.21 Chapter 9.4.13, the following channel</span><br><span style="color: hsl(120, 100%, 40%);">+In addition to 3GPP TS 52.021 Chapter 9.4.13, the following channel</span><br><span> combinations are supported:</span><br><span> </span><br><span> .Additional Channel Combinations</span><br><span>@@ -513,7 +514,7 @@</span><br><span> [[ie_conn_fail_crit]]</span><br><span> ==== Connection Failure Criterion</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-3GPP TS 12.21 Chapter 9.4.14 specifies two different options for the</span><br><span style="color: hsl(120, 100%, 40%);">+3GPP TS 52.021 Chapter 9.4.14 specifies two different options for the</span><br><span> _Connection Failure Criterion_. OsmoBTS only implements the option</span><br><span> coded as 0x01, i.e. based upon uplink SACCH error rate</span><br><span> (RADIO_LINK_TIMEOUT).</span><br><span>@@ -523,7 +524,7 @@</span><br><span> </span><br><span> Due to limitations in the currently supported PHY implementations,</span><br><span> OsmoBTS supports only one global TSC for all channels on one TRX, rather</span><br><span style="color: hsl(0, 100%, 40%);">-than a separate TSC for each timeslot, as expected by 3GPP TS 12.21.</span><br><span style="color: hsl(120, 100%, 40%);">+than a separate TSC for each timeslot, as expected by 3GPP TS 52.021.</span><br><span> </span><br><span> </span><br><span> [[NM_ATT_IPACC_DST_IP]]</span><br><span>@@ -786,7 +787,7 @@</span><br><span> === A-bis OML Initialization / BTS bring-up</span><br><span> </span><br><span> At the time an Abis/IP BTS connects to via OML to the BSC, it is</span><br><span style="color: hsl(0, 100%, 40%);">-initialized according to the procedures described in 3GPP TS 12.21 as</span><br><span style="color: hsl(120, 100%, 40%);">+initialized according to the procedures described in 3GPP TS 52.021 as</span><br><span> amended by this document.</span><br><span> </span><br><span> Each Managed Object (MO) is separately initialized. The initialization</span><br><span></span><br></pre><p>To view, visit <a href="https://gerrit.osmocom.org/c/osmo-bts/+/23846">change 23846</a>. To unsubscribe, or for help writing mail filters, visit <a href="https://gerrit.osmocom.org/settings">settings</a>.</p><div itemscope itemtype="http://schema.org/EmailMessage"><div itemscope itemprop="action" itemtype="http://schema.org/ViewAction"><link itemprop="url" href="https://gerrit.osmocom.org/c/osmo-bts/+/23846"/><meta itemprop="name" content="View Change"/></div></div>
<div style="display:none"> Gerrit-Project: osmo-bts </div>
<div style="display:none"> Gerrit-Branch: master </div>
<div style="display:none"> Gerrit-Change-Id: I662a3419a6ec741fe162ccc7c7221df20b2780b1 </div>
<div style="display:none"> Gerrit-Change-Number: 23846 </div>
<div style="display:none"> Gerrit-PatchSet: 1 </div>
<div style="display:none"> Gerrit-Owner: neels <nhofmeyr@sysmocom.de> </div>
<div style="display:none"> Gerrit-MessageType: newchange </div>