<p>laforge <strong>submitted</strong> this change.</p><p><a href="https://gerrit.osmocom.org/c/osmo-pcu/+/21649">View Change</a></p><div style="white-space:pre-wrap">Approvals:
Jenkins Builder: Verified
pespin: Looks good to me, but someone else must approve
fixeria: Looks good to me, approved
</div><pre style="font-family: monospace,monospace; white-space: pre-wrap;">gb manual: 08.16 -> 48.016 / 08.18 -> 48.018<br><br>Change-Id: I10505d9aebe65e1f0952df75b13951e2b40d6997<br>---<br>M doc/manuals/gb/bssgp.adoc<br>M doc/manuals/gb/ns.adoc<br>M doc/manuals/osmopcu-gb.adoc<br>3 files changed, 67 insertions(+), 67 deletions(-)<br><br></pre><pre style="font-family: monospace,monospace; white-space: pre-wrap;"><span>diff --git a/doc/manuals/gb/bssgp.adoc b/doc/manuals/gb/bssgp.adoc</span><br><span>index 18f1842..7dcf3f8 100644</span><br><span>--- a/doc/manuals/gb/bssgp.adoc</span><br><span>+++ b/doc/manuals/gb/bssgp.adoc</span><br><span>@@ -4,14 +4,14 @@</span><br><span> === List of Messages</span><br><span> </span><br><span> The following tables list the BSSGP messages used by OsmoPCU, grouped</span><br><span style="color: hsl(0, 100%, 40%);">-by their level of compliance with 3GPP TS 08.18.</span><br><span style="color: hsl(120, 100%, 40%);">+by their level of compliance with 3GPP TS 48.018.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-==== Messages Compliant With TS 08.18</span><br><span style="color: hsl(120, 100%, 40%);">+==== Messages Compliant With TS 48.018</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-.Messages compliant with TS 08.18</span><br><span style="color: hsl(120, 100%, 40%);">+.Messages compliant with TS 48.018</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 08.18 § | type code (hex) | This document § | Message | <-/-> | Received/Sent by OsmoPCU</span><br><span style="color: hsl(120, 100%, 40%);">+| TS 48.018 § | type code (hex) | This document § | Message | <-/-> | Received/Sent by OsmoPCU</span><br><span> 6+<| *RL and BSSGP SAP Messages:*</span><br><span> | 10.2.1 | 0x00 | <<dl_unit_data>> | DL-UNITDATA | <- | Received</span><br><span> | 10.2.2 | 0x01 | <<ul_unit_data>> | UL-UNITDATA | -> | Sent</span><br><span>@@ -44,10 +44,10 @@</span><br><span> [[not_impl]]</span><br><span> ==== Messages Not Implemented by OsmoPCU</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-.3GPP TS 08.18 messages not implemented by OsmoPCU</span><br><span style="color: hsl(120, 100%, 40%);">+.3GPP TS 48.018 messages not implemented by OsmoPCU</span><br><span> [options="header",cols="10%,10%,80%"]</span><br><span> |===</span><br><span style="color: hsl(0, 100%, 40%);">-| TS 08.18 § | type code (hex) | Message</span><br><span style="color: hsl(120, 100%, 40%);">+| TS 48.018 § | type code (hex) | Message</span><br><span> 3+<| *RL (relay) and BSSGP SAP Messages:*</span><br><span> | 10.2.4 | 0x03 | PTM-UNITDATA</span><br><span> 3+<| *GMM (GPRS mobility management) SAP Messages:*</span><br><span>@@ -78,7 +78,7 @@</span><br><span> [[dl_unit_data]]</span><br><span> ==== DL-UNITDATA</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-This message conforms to 3GPP TS 08.18 § 10.2.1, with the following</span><br><span style="color: hsl(120, 100%, 40%);">+This message conforms to 3GPP TS 48.018 § 10.2.1, with the following</span><br><span> limitations:</span><br><span> </span><br><span> * OsmoPCU does not support QoS</span><br><span>@@ -87,7 +87,7 @@</span><br><span> ._DL-UNITDATA_ IE limitations</span><br><span> [options="header",cols="10%,30%,60%"]</span><br><span> |===</span><br><span style="color: hsl(0, 100%, 40%);">-| TS 08.18 § | IE Name | Handling</span><br><span style="color: hsl(120, 100%, 40%);">+| TS 48.018 § | IE Name | Handling</span><br><span> | 11.3.28 | QoS Profile | _ignored_</span><br><span> | 11.3.22 | MS Radio Access Capability | _ignored_</span><br><span> | 11.3.27 | Priority | _ignored_</span><br><span>@@ -100,7 +100,7 @@</span><br><span> [[ul_unit_data]]</span><br><span> ==== UL-UNITDATA</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-This message conforms to 3GPP TS 08.18 § 10.2.2, with the following limitations:</span><br><span style="color: hsl(120, 100%, 40%);">+This message conforms to 3GPP TS 48.018 § 10.2.2, with the following limitations:</span><br><span> </span><br><span> * OsmoPCU does not send optional IEs - PFI (§ 12.3.42) and LSA</span><br><span> Identifier List (§ 11.3.18).</span><br><span>@@ -114,7 +114,7 @@</span><br><span> [[paging_ps]]</span><br><span> ==== PAGING PS</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-This message conforms to 3GPP TS 08.18 § 10.3.1, with the following</span><br><span style="color: hsl(120, 100%, 40%);">+This message conforms to 3GPP TS 48.018 § 10.3.1, with the following</span><br><span> limitations:</span><br><span> </span><br><span> * only IMSI and P-TMSI are parsed by OsmoPCU.</span><br><span>@@ -122,7 +122,7 @@</span><br><span> ._DL-UNITDATA_ IE limitations</span><br><span> [options="header",cols="10%,30%,60%"]</span><br><span> |===</span><br><span style="color: hsl(0, 100%, 40%);">-| TS 08.18 § | IE Name | Handling</span><br><span style="color: hsl(120, 100%, 40%);">+| TS 48.018 § | IE Name | Handling</span><br><span> | 11.3.11 | DRX Parameters | _ignored_</span><br><span> | 11.3.6 | BVCI | _ignored_</span><br><span> | 11.3.17 | Location Are | _ignored_</span><br><span>@@ -174,7 +174,7 @@</span><br><span> [[bvc_reset]]</span><br><span> ==== BVC-RESET</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-OsmoPCU never transmits optional Feature bitmap (3GPP TS 08.18 §</span><br><span style="color: hsl(120, 100%, 40%);">+OsmoPCU never transmits optional Feature bitmap (3GPP TS 48.018 §</span><br><span> 11.3.40) IE.</span><br><span> </span><br><span> Receiving BVC RESET will cause OsmoPCU to respond with "Unknown BVCI"</span><br><span>@@ -183,24 +183,24 @@</span><br><span> [[reset_ack]]</span><br><span> ==== BVC-RESET-ACK</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-This message conforms to 3GPP TS 08.18 § 10.4.13.</span><br><span style="color: hsl(120, 100%, 40%);">+This message conforms to 3GPP TS 48.018 § 10.4.13.</span><br><span> </span><br><span> After receiving it OsmoPCU completes the RESET procedure for BVC</span><br><span style="color: hsl(0, 100%, 40%);">-according to 3GPP TS 08.18 § 8.4.</span><br><span style="color: hsl(120, 100%, 40%);">+according to 3GPP TS 48.018 § 8.4.</span><br><span> </span><br><span> [[unblock_ack]]</span><br><span> ==== BVC-UNBLOCK-ACK</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-This message conforms to 3GPP TS 08.18 § 10.4.11.</span><br><span style="color: hsl(120, 100%, 40%);">+This message conforms to 3GPP TS 48.018 § 10.4.11.</span><br><span> </span><br><span> After receiving it OsmoPCU completes the RESET procedure for BVC</span><br><span style="color: hsl(0, 100%, 40%);">-according to 3GPP TS 08.18 § 8.3.</span><br><span style="color: hsl(120, 100%, 40%);">+according to 3GPP TS 48.018 § 8.3.</span><br><span> </span><br><span> [[bvc_unblock]]</span><br><span> ==== BVC-UNBLOCK</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-This message conforms to 3GPP TS 08.18 § 10.4.10 and is send by</span><br><span style="color: hsl(0, 100%, 40%);">-OsmoPCU as part of UNBLOCK procedure described in 3GPP TS 08.18 § 8.3.</span><br><span style="color: hsl(120, 100%, 40%);">+This message conforms to 3GPP TS 48.018 § 10.4.10 and is send by</span><br><span style="color: hsl(120, 100%, 40%);">+OsmoPCU as part of UNBLOCK procedure described in 3GPP TS 48.018 § 8.3.</span><br><span> </span><br><span> [[flow_ms_ack]]</span><br><span> ==== FLOW-CONTROL-MS-ACK</span><br><span>@@ -217,11 +217,11 @@</span><br><span> [[flow_bvc]]</span><br><span> ==== FLOW-CONTROL-BVC</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-This message conforms to 3GPP TS 08.18 § 10.4.4, with the following</span><br><span style="color: hsl(120, 100%, 40%);">+This message conforms to 3GPP TS 48.018 § 10.4.4, with the following</span><br><span> limitations:</span><br><span> </span><br><span> * OsmoPCU does not support Current Bucket Level (CBL) feature so</span><br><span style="color: hsl(0, 100%, 40%);">- Bucket_Full Ratio (TS 08.18 § 11.3.46) IE is not transmitted as part</span><br><span style="color: hsl(120, 100%, 40%);">+ Bucket_Full Ratio (TS 48.018 § 11.3.46) IE is not transmitted as part</span><br><span> of this message.</span><br><span> </span><br><span> [[flush_ll]]</span><br><span>@@ -239,22 +239,22 @@</span><br><span> [[bssgp_status]]</span><br><span> ==== STATUS</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-This message conforms to 3GPP TS 08.18 § 10.4.14.</span><br><span style="color: hsl(120, 100%, 40%);">+This message conforms to 3GPP TS 48.018 § 10.4.14.</span><br><span> </span><br><span> === Information Elements Overview</span><br><span> </span><br><span> All of the IEs handled by OsmoPCU are listed below, with limitations</span><br><span style="color: hsl(0, 100%, 40%);">-and additions to 3GPP TS 08.18 specified in more detail.</span><br><span style="color: hsl(120, 100%, 40%);">+and additions to 3GPP TS 48.018 specified in more detail.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-==== IEs Conforming to 3GPP TS 08.18</span><br><span style="color: hsl(120, 100%, 40%);">+==== IEs Conforming to 3GPP TS 48.018</span><br><span> </span><br><span> The following Information Elements are accepted by OsmoPCU. Not all</span><br><span> IEs are actually evaluated.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-.IEs conforming to 3GPP TS 08.18</span><br><span style="color: hsl(120, 100%, 40%);">+.IEs conforming to 3GPP TS 48.018</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 08.18 § | IE name | <-/-> | Received/Sent by OsmoPCU</span><br><span style="color: hsl(120, 100%, 40%);">+| tag (hex) | TS 48.018 § | IE name | <-/-> | Received/Sent by OsmoPCU</span><br><span> | 0x00 | 11.3.1 | Alignment Octets | <-/-> | Received/Sent</span><br><span> | 0x01 | 11.3.2 | Bmax default MS | -> | Sent</span><br><span> | 0x02 | 11.3.3 | BSS Area Indication | <- | Received</span><br><span>@@ -301,12 +301,12 @@</span><br><span> | 0x3d | 11.3.47 | Service UTRAN CCO (Cell Change Order) | <- | Received</span><br><span> |===</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-==== IEs Not Conforming to 3GPP TS 08.18</span><br><span style="color: hsl(120, 100%, 40%);">+==== IEs Not Conforming to 3GPP TS 48.018</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-.IEs not conforming to 3GPP TS 08.18</span><br><span style="color: hsl(120, 100%, 40%);">+.IEs not conforming to 3GPP TS 48.018</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 08.18 § | IE name | Description</span><br><span style="color: hsl(120, 100%, 40%);">+| tag (hex) | TS 48.018 § | IE name | Description</span><br><span> | 0x18 | 11.3.28 | QoS Profile | Received value is ignored. Sent value is hard-coded to 0x4 (3 octets).</span><br><span> |===</span><br><span> </span><br><span>@@ -417,7 +417,7 @@</span><br><span> ==== Tag</span><br><span> </span><br><span> This IE currently only used by OsmoPCU for Flow Control procedure (TS</span><br><span style="color: hsl(0, 100%, 40%);">-08.18 § 8.2). In other cases it's either ignored or unavailable.</span><br><span style="color: hsl(120, 100%, 40%);">+48.018 § 8.2). In other cases it's either ignored or unavailable.</span><br><span> </span><br><span> ==== Trace Reference</span><br><span> </span><br><span>@@ -494,8 +494,8 @@</span><br><span> </span><br><span> In addition to the BVCI identifying the OsmoPCU side of BSSGP</span><br><span> connection, there is also special BVCI which is accepted by OsmoPCU in</span><br><span style="color: hsl(0, 100%, 40%);">-accordance with 3GPP TS 08.18 § 5.4.1: BVCI = 0 represents signaling data</span><br><span style="color: hsl(120, 100%, 40%);">+accordance with 3GPP TS 48.018 § 5.4.1: BVCI = 0 represents signaling data</span><br><span> between SGSN and PCU in contrast to PTP (Peer-To-Peer) user's data.</span><br><span> </span><br><span> The mapping between BSSGP PDUs and signaling or PTP BVCIs is available</span><br><span style="color: hsl(0, 100%, 40%);">-in 3GPP TS 08.18 Table 5.4.</span><br><span style="color: hsl(120, 100%, 40%);">+in 3GPP TS 48.018 Table 5.4.</span><br><span>diff --git a/doc/manuals/gb/ns.adoc b/doc/manuals/gb/ns.adoc</span><br><span>index c94e018..1dc2ed8 100644</span><br><span>--- a/doc/manuals/gb/ns.adoc</span><br><span>+++ b/doc/manuals/gb/ns.adoc</span><br><span>@@ -3,18 +3,18 @@</span><br><span> === List of Messages</span><br><span> </span><br><span> The following tables list the NS messages used by OsmoPCU, grouped by their</span><br><span style="color: hsl(0, 100%, 40%);">-level of compliance with 3GPP TS 08.16.</span><br><span style="color: hsl(120, 100%, 40%);">+level of compliance with 3GPP TS 48.016.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-==== Messages Compliant With 3GPP TS 08.16</span><br><span style="color: hsl(120, 100%, 40%);">+==== Messages Compliant With 3GPP TS 48.016</span><br><span> </span><br><span> The NS protocol is implemented inside libosmocore so none of the messages below are sent by OsmoPCU explicitly.</span><br><span> Instead corresponding functions from libosmocore are called which send and receive messages as necessary. See <<ns_init>> for details</span><br><span> on establishing NS connection.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-.Messages compliant with 3GPP TS 08.16</span><br><span style="color: hsl(120, 100%, 40%);">+.Messages compliant with 3GPP TS 48.016</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 08.16 § | type code (hex) | This document § | Message | <-/-> | Received/Sent by OsmoPCU</span><br><span style="color: hsl(120, 100%, 40%);">+| TS 48.016 § | type code (hex) | This document § | Message | <-/-> | Received/Sent by OsmoPCU</span><br><span> | 9.2.10 | 0x00 | <<ns_unit_data>> | NS-UNITDATA | <-/-> | Received/Sent</span><br><span> | 9.2.5 | 0x02 | <<ns_reset>> | NS-RESET | <-/-> | Received/Sent</span><br><span> | 9.2.6 | 0x03 | <<ns_reset_ack>> | NS-RESET-ACK | <-/-> | Received/Sent</span><br><span>@@ -33,7 +33,7 @@</span><br><span> </span><br><span> ==== Messages Not Implemented by OsmoPCU</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-All the NS protocol messages from 3GPP TS 08.16 are implemented in OsmoPCU.</span><br><span style="color: hsl(120, 100%, 40%);">+All the NS protocol messages from 3GPP TS 48.016 are implemented in OsmoPCU.</span><br><span> </span><br><span> === Details on Compliant NS Messages</span><br><span> </span><br><span>@@ -51,13 +51,13 @@</span><br><span> ==== NS-RESET</span><br><span> </span><br><span> This message is send by OsmoPCU in order to initiate reset procedure</span><br><span style="color: hsl(0, 100%, 40%);">-described in 3GPP TS 08.16 § 7.3. The expected reply is NS-RESET-ACK</span><br><span style="color: hsl(120, 100%, 40%);">+described in 3GPP TS 48.016 § 7.3. The expected reply is NS-RESET-ACK</span><br><span> (<<ns_reset_ack>>) message. If no expected reply is received in 3</span><br><span> seconds than the sending is retried up to 3 times. When this message</span><br><span> is received it is replied with NS-RESET-ACK (<<ns_reset_ack>>).</span><br><span style="color: hsl(0, 100%, 40%);">-It might be ignored under conditions described in 3GPP TS 08.16 § 7.3.1.</span><br><span style="color: hsl(120, 100%, 40%);">+It might be ignored under conditions described in 3GPP TS 48.016 § 7.3.1.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-The message conforms to 3GPP TS 08.16 § 9.2.5 specification.</span><br><span style="color: hsl(120, 100%, 40%);">+The message conforms to 3GPP TS 48.016 § 9.2.5 specification.</span><br><span> </span><br><span> It contains Cause (<<ie_cause>>), NSVCI (<<ie_nsvci>>) and NSEI (<<ie_nsei>>) IEs.</span><br><span> </span><br><span>@@ -67,7 +67,7 @@</span><br><span> This message is sent as a response to proper NS-RESET (<<ns_reset>>)</span><br><span> message initiating reset procedure.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-The message conforms to 3GPP TS 08.16 § 9.2.6 specification.</span><br><span style="color: hsl(120, 100%, 40%);">+The message conforms to 3GPP TS 48.016 § 9.2.6 specification.</span><br><span> </span><br><span> It contains NSVCI (<<ie_nsvci>>) and NSEI (<<ie_nsei>>) IEs.</span><br><span> </span><br><span>@@ -79,9 +79,9 @@</span><br><span> When this message is sent by OsmoPCU corresponding NS-BLOCK-ACK</span><br><span> (<<ns_block_ack>>) reply is expected before NS-VC is actually marked</span><br><span> as blocked. This behavior follows the blocking procedure described in</span><br><span style="color: hsl(0, 100%, 40%);">-3GPP TS 08.16 § 7.2.</span><br><span style="color: hsl(120, 100%, 40%);">+3GPP TS 48.016 § 7.2.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-The message conforms to 3GPP TS 08.16 § 9.2.3 specification.</span><br><span style="color: hsl(120, 100%, 40%);">+The message conforms to 3GPP TS 48.016 § 9.2.3 specification.</span><br><span> </span><br><span> It contains Cause (<<ie_cause>>) and NSVCI (<<ie_nsvci>>) IEs.</span><br><span> </span><br><span>@@ -92,7 +92,7 @@</span><br><span> correct NS-BLOCK (<<ns_block>>) message. It is expected as a reply</span><br><span> for NS-BLOCK (<<ns_block>>) message sent by OsmoPCU.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-The message conforms to 3GPP TS 08.16 § 9.2.4 specification.</span><br><span style="color: hsl(120, 100%, 40%);">+The message conforms to 3GPP TS 48.016 § 9.2.4 specification.</span><br><span> </span><br><span> It contains NSVCI (<<ie_nsvci>>) IE.</span><br><span> </span><br><span>@@ -104,9 +104,9 @@</span><br><span> this message is sent by OsmoPCU corresponding NS-UNBLOCK-ACK</span><br><span> (<<ns_unblock_ack>>) reply is expected before NS-VC is actually marked</span><br><span> as unblocked. This behavior follows the blocking procedure described</span><br><span style="color: hsl(0, 100%, 40%);">-in 3GPP TS 08.16 § 7.2.</span><br><span style="color: hsl(120, 100%, 40%);">+in 3GPP TS 48.016 § 7.2.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-The message conforms to 3GPP TS 08.16 § 9.2.8 specification.</span><br><span style="color: hsl(120, 100%, 40%);">+The message conforms to 3GPP TS 48.016 § 9.2.8 specification.</span><br><span> </span><br><span> [[ns_unblock_ack]]</span><br><span> ==== NS-UNBLOCK-ACK</span><br><span>@@ -115,7 +115,7 @@</span><br><span> is confirmed and thus NS-VC is marked as unblocked. This message is</span><br><span> also sent as a reply to NS-UNBLOCK (<<ns_unblock>>) message.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-The message conforms to 3GPP TS 08.16 § 9.2.9 specification.</span><br><span style="color: hsl(120, 100%, 40%);">+The message conforms to 3GPP TS 48.016 § 9.2.9 specification.</span><br><span> </span><br><span> [[ns_status]]</span><br><span> ==== NS-STATUS</span><br><span>@@ -123,10 +123,10 @@</span><br><span> This message is sent to inform other party about error conditions as a</span><br><span> response to various unexpected PDUs or PDUs with unexpected/missing</span><br><span> data. If this message is received for unknown NS-VC it is ignored in</span><br><span style="color: hsl(0, 100%, 40%);">-accordance with 3GPP TS 08.16 § 7.5.1, otherwise the error cause is</span><br><span style="color: hsl(120, 100%, 40%);">+accordance with 3GPP TS 48.016 § 7.5.1, otherwise the error cause is</span><br><span> logged if present in NS-STATUS.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-The message conforms to 3GPP TS 08.16 § 9.2.7 specification.</span><br><span style="color: hsl(120, 100%, 40%);">+The message conforms to 3GPP TS 48.016 § 9.2.7 specification.</span><br><span> </span><br><span> It contains Cause (<<ie_cause>>) and might (depending on actual error)</span><br><span> contain NSVCI (<<ie_nsvci>>), NS PDU (<<ie_nspdu>>) and BVCI</span><br><span>@@ -136,13 +136,13 @@</span><br><span> ==== NS-ALIVE</span><br><span> </span><br><span> This message is sent periodically to test connectivity according to</span><br><span style="color: hsl(0, 100%, 40%);">-3GPP TS 08.16 § 4.5.3. The expected response is NS-ALIVE-ACK</span><br><span style="color: hsl(120, 100%, 40%);">+3GPP TS 48.016 § 4.5.3. The expected response is NS-ALIVE-ACK</span><br><span> (<<ns_alive_ack>>). If no such response arrives within given amount of</span><br><span> time (3 seconds) than another NS-ALIVE message is sent and failed test</span><br><span> attempt is recorded. After 10 failed attempts NS connection is</span><br><span> considered dead and OsmoPCU tries to reconnect.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-The message conforms to 3GPP TS 08.16 § 9.2.1 specification.</span><br><span style="color: hsl(120, 100%, 40%);">+The message conforms to 3GPP TS 48.016 § 9.2.1 specification.</span><br><span> </span><br><span> [[ns_alive_ack]]</span><br><span> ==== NS-ALIVE-ACK</span><br><span>@@ -150,21 +150,21 @@</span><br><span> This message is sent automatically in reply to NS-ALIVE (<<ns_alive>>)</span><br><span> message.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-The message conforms to 3GPP TS 08.16 § 9.2.2 specification.</span><br><span style="color: hsl(120, 100%, 40%);">+The message conforms to 3GPP TS 48.016 § 9.2.2 specification.</span><br><span> </span><br><span> === Information Elements Overview</span><br><span> </span><br><span> All of the IEs handled by OsmoPCU are listed below, with limitations and</span><br><span style="color: hsl(0, 100%, 40%);">-additions to 3GPP TS 08.16 specified in more detail.</span><br><span style="color: hsl(120, 100%, 40%);">+additions to 3GPP TS 48.016 specified in more detail.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-==== IEs Conforming to 3GPP TS 08.16</span><br><span style="color: hsl(120, 100%, 40%);">+==== IEs Conforming to 3GPP TS 48.016</span><br><span> </span><br><span> The following Information Elements are accepted by OsmoPCU.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-.IEs conforming to 3GPP TS 08.16</span><br><span style="color: hsl(120, 100%, 40%);">+.IEs conforming to 3GPP TS 48.016</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 08.16 § | IE name | <-/-> | Received/Sent by OsmoPCU</span><br><span style="color: hsl(120, 100%, 40%);">+| tag (hex) | TS 48.016 § | IE name | <-/-> | Received/Sent by OsmoPCU</span><br><span> | 0x00 | 10.3.2 | Cause | <-/-> | Received/Sent</span><br><span> | 0x01 | 10.3.5 | NSVCI | <-/-> | Received/Sent</span><br><span> | 0x02 | 10.3.3 | NS PDU | <-/-> | Received/Sent</span><br><span>@@ -172,9 +172,9 @@</span><br><span> | 0x04 | 10.3.6 | NSEI | <-/-> | Received/Sent</span><br><span> |===</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-==== IEs Not Conforming to 3GPP TS 08.16</span><br><span style="color: hsl(120, 100%, 40%);">+==== IEs Not Conforming to 3GPP TS 48.016</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-All IEs defined in 3GPP TS 08.16 § 10.3 are supported by OsmoPCU.</span><br><span style="color: hsl(120, 100%, 40%);">+All IEs defined in 3GPP TS 48.016 § 10.3 are supported by OsmoPCU.</span><br><span> </span><br><span> ==== Additional Attributes and Parameters</span><br><span> </span><br><span>@@ -185,18 +185,18 @@</span><br><span> [[ie_cause]]</span><br><span> ==== Cause</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-This IE contains reason for a procedure or error as described in 3GPP TS 08.16 § 10.3.2.</span><br><span style="color: hsl(120, 100%, 40%);">+This IE contains reason for a procedure or error as described in 3GPP TS 48.016 § 10.3.2.</span><br><span> </span><br><span> [[ie_nsvci]]</span><br><span> ==== NSVCI</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-This IE represents NSVCI identity described in <<ident>> and 3GPP TS 08.16 § 10.3.5.</span><br><span style="color: hsl(120, 100%, 40%);">+This IE represents NSVCI identity described in <<ident>> and 3GPP TS 48.016 § 10.3.5.</span><br><span> </span><br><span> [[ie_nspdu]]</span><br><span> ==== NS PDU</span><br><span> </span><br><span> This IE contains PDU (possibly truncated) which cause error described</span><br><span style="color: hsl(0, 100%, 40%);">-in NS-STATUS message (<<ns_status>>) as described in 3GPP TS 08.16 §</span><br><span style="color: hsl(120, 100%, 40%);">+in NS-STATUS message (<<ns_status>>) as described in 3GPP TS 48.016 §</span><br><span> 10.3.3.</span><br><span> </span><br><span> [[ie_nssdu]]</span><br><span>@@ -207,13 +207,13 @@</span><br><span> [[ie_bvci]]</span><br><span> ==== BVCI</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-This IE represents BSSGP identity described in <<ident>> and 3GPP TS 08.16</span><br><span style="color: hsl(120, 100%, 40%);">+This IE represents BSSGP identity described in <<ident>> and 3GPP TS 48.016</span><br><span> § 10.3.1.</span><br><span> </span><br><span> [[ie_nsei]]</span><br><span> ==== NSEI</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-This IE represents NSEI identity described in <<ident>> and 3GPP TS 08.16 §</span><br><span style="color: hsl(120, 100%, 40%);">+This IE represents NSEI identity described in <<ident>> and 3GPP TS 48.016 §</span><br><span> 10.3.6.</span><br><span> </span><br><span> [[ns_init]]</span><br><span>diff --git a/doc/manuals/osmopcu-gb.adoc b/doc/manuals/osmopcu-gb.adoc</span><br><span>index 00576c9..166059b 100644</span><br><span>--- a/doc/manuals/osmopcu-gb.adoc</span><br><span>+++ b/doc/manuals/osmopcu-gb.adoc</span><br><span>@@ -7,7 +7,7 @@</span><br><span> == Introduction</span><br><span> </span><br><span> This document describes the Gb interface of *OsmoPCU*. Based on 3GPP TS</span><br><span style="color: hsl(0, 100%, 40%);">-08.16 and 08.18, this document indicates which of the 3GPP specified Gb</span><br><span style="color: hsl(120, 100%, 40%);">+48.016 and 48.018, this document indicates which of the 3GPP specified Gb</span><br><span> messages and IEs are implemented according to 3GPP specifications, which of</span><br><span> these are not or not fully implemented, as well as OsmoPCU-specific extensions</span><br><span> to the Gb interface not specified by 3GPP.</span><br><span>@@ -23,8 +23,8 @@</span><br><span> |3GPP TS 08.58 | version 8.6.0 Release 1999</span><br><span> |3GPP TS 08.60 | version 8.2.1 Release 1999</span><br><span> |3GPP TS 12.21 | version 8.0.0 Release 1999</span><br><span style="color: hsl(0, 100%, 40%);">-|3GPP TS 08.16 | version 8.0.1 Release 1999</span><br><span style="color: hsl(0, 100%, 40%);">-|3GPP TS 08.18 | version 8.12.0 Release 1999</span><br><span style="color: hsl(120, 100%, 40%);">+|3GPP TS 48.016 | version 15.0.0 Release 15</span><br><span style="color: hsl(120, 100%, 40%);">+|3GPP TS 48.018 | version 15.0.0 Release 15</span><br><span> |===</span><br><span> </span><br><span> .IETF documents referred to by his document</span><br><span>@@ -74,8 +74,8 @@</span><br><span> BVCI:: BSSGP Virtual Connection Identifier</span><br><span> </span><br><span> For an explanation of those identifiers and their use in the NS and</span><br><span style="color: hsl(0, 100%, 40%);">-BSSGP protocols, please see the relevant 3GPP specifications for NS (TS 08.16)</span><br><span style="color: hsl(0, 100%, 40%);">-and BSSGP (TS 08.18).</span><br><span style="color: hsl(120, 100%, 40%);">+BSSGP protocols, please see the relevant 3GPP specifications for NS (TS 48.016)</span><br><span style="color: hsl(120, 100%, 40%);">+and BSSGP (TS 48.018).</span><br><span> </span><br><span> In most cases, all above identities belong to different namespaces and</span><br><span> must be unique within their respective namespace and within the SGSN</span><br><span></span><br></pre><p>To view, visit <a href="https://gerrit.osmocom.org/c/osmo-pcu/+/21649">change 21649</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-pcu/+/21649"/><meta itemprop="name" content="View Change"/></div></div>
<div style="display:none"> Gerrit-Project: osmo-pcu </div>
<div style="display:none"> Gerrit-Branch: master </div>
<div style="display:none"> Gerrit-Change-Id: I10505d9aebe65e1f0952df75b13951e2b40d6997 </div>
<div style="display:none"> Gerrit-Change-Number: 21649 </div>
<div style="display:none"> Gerrit-PatchSet: 2 </div>
<div style="display:none"> Gerrit-Owner: laforge <laforge@osmocom.org> </div>
<div style="display:none"> Gerrit-Reviewer: Jenkins Builder </div>
<div style="display:none"> Gerrit-Reviewer: fixeria <vyanitskiy@sysmocom.de> </div>
<div style="display:none"> Gerrit-Reviewer: laforge <laforge@osmocom.org> </div>
<div style="display:none"> Gerrit-Reviewer: pespin <pespin@sysmocom.de> </div>
<div style="display:none"> Gerrit-MessageType: merged </div>