blob: fc2ca8f104bcadd2f75ed78d48b578c03651d503 [file] [log] [blame]
Harald Welteb682cd62016-02-29 15:09:55 +01001OsmoPCU Gb Protocol Specification
2=================================
Maxc182b982016-03-02 16:44:13 +01003Harald Welte <hwelte@sysmocom.de>
Harald Welteb682cd62016-02-29 15:09:55 +01004
5== Introduction
6
7This document describes the Gb interface of *OsmoPCU*. Based on 3GPP TS
Maxc182b982016-03-02 16:44:13 +0100808.16 and 08.18, this document indicates which of the 3GPP specified Gb
Harald Welteb682cd62016-02-29 15:09:55 +01009messages and IEs are implemented according to 3GPP specifications, which of
10these are not or not fully implemented, as well as OsmoPCU-specific extensions
11to the Gb interface not specified by 3GPP.
12
13Extensions to the Gb interface specific to OsmoPCU are detailed in this
Harald Weltea27873f2016-03-10 12:35:09 +070014document. For details on the messages and IEs that comply with above-mentioned
Harald Welteb682cd62016-02-29 15:09:55 +0100153GPP specifications, please refer to those documents.
16
17.3GPP document versions referred to by this document
18[cols="20%,80%"]
19|===
20|3GPP TS 08.56 | version 8.0.1 Release 1999
21|3GPP TS 08.58 | version 8.6.0 Release 1999
22|3GPP TS 08.60 | version 8.2.1 Release 1999
23|3GPP TS 12.21 | version 8.0.0 Release 1999
Maxc182b982016-03-02 16:44:13 +010024|3GPP TS 08.16 | version 8.0.1 Release 1999
25|3GPP TS 08.18 | version 8.12.0 Release 1999
Harald Welteb682cd62016-02-29 15:09:55 +010026|===
27
28.IETF documents referred to by his document
29[cols="20%,80%"]
30|===
31|IETF RFC 768 | User Datagram Protocol
32|IETF RFC 791 | Internet Protocol
33|===
34
35== Overview
36
37The OsmoPCU Gb interface consists of the NS (Network Services) and
38BSSGP (Base Station Subsystem Gateway Protocol), encapsulated in UDP
39(User Datagram Protocol) and IP (Internet Protocol) version 4.
Harald Weltea27873f2016-03-10 12:35:09 +070040Use of other underlying protocols (e. g. Frame Relay) is not supported.
Harald Welteb682cd62016-02-29 15:09:55 +010041
42.UDP port numbers used by OsmoPCU Gb/IP
43[options="header",width="50%",cols="35%,65%"]
44|===
45|TCP Port Number|Usage
Harald Welte6fb29632016-03-10 12:53:06 +070046|23000|NS over UDP (default port)
Harald Welteb682cd62016-02-29 15:09:55 +010047|===
48
49The NS-over-UDP link is established in the PCU -> SGSN direction, i.e.
50the PCU is running as client while the SGSN is running as server.
51
52Establishment of the NS-over-UDP link is only possible after OsmoPCU
Harald Weltea27873f2016-03-10 12:35:09 +070053has been configured via the *PCU socket* interface from OsmoBTS.
Harald Welteb682cd62016-02-29 15:09:55 +010054
55OsmoBTS in turn receives relevant configuration parameters from
56OsmoBSC or the BSC component inside OsmoNITB.
57
58.Overview of Gb link establishment
59["mscgen"]
60----
61include::gb/gb-startup.msc[]
62----
63
Max4e2a1e32016-03-02 18:30:33 +010064[[ident]]
Harald Welteb682cd62016-02-29 15:09:55 +010065=== Identities
66
67The Gb interface identities of the PCU are configured via BSC ->
68OsmoBTS -> PCU Socket. They consist of
69
70NSEI:: NS Equipment Identifier
71NSVCI:: NS Virtual Connection Identifier
72BVCI:: BSSGP Virtual Connection Identifier
73
74For an explanation of those identifiers and their use in the NS and
Jonathan Brielmaier58721eb2016-05-25 15:01:11 +020075BSSGP protocols, please see the relevant 3GPP specifications for NS (TS 08.16)
Max4e2a1e32016-03-02 18:30:33 +010076and BSSGP (TS 08.18).
Harald Welteb682cd62016-02-29 15:09:55 +010077
78In most cases, all above identities belong to different namespaces and
79must be unique within their respective namespace and within the SGSN
80they connect to.
81
82This means that typically each OsmoPCU has one unique set of NSEI,
83NSVCI and BVCI in your network.
84
85include::gb/ns.adoc[]
86
87include::gb/bssgp.adoc[]
88
89include::../common/chapters/port_numbers.adoc[]
90
91include::../common/chapters/glossary.adoc[]
92
93include::../common/chapters/gfdl.adoc[]