08.163GPPBase Station System (BSS) - Serving GPRS Support Node (SGSN) interfaceGeneral Packet Radio Service (GPRS)Network serviceRelease 1999TS
This chapter presents the Network Service in a generic way, no assumptions are made regarding the real protocols providing the network services.
5.1 Service primitive model
The service primitive model shown in Figure 3/3GPP TS 08.16 is applicable to both BSS and SGSN.
Figure 4/3GPP TS 08.16: Network Service primitive model
The network services are provided at the Network Service-Service Access Point (NS-SAP).
5.2 Service primitives and parameters
The Network Service primitives are summarized in table 1/3GPP TS 08.16. The general syntax of the Network Service primitives is:
NS ‑ Generic name ‑ Type (Parameters)
Table 1/3GPP TS 08.16: Network Service primitives
– BVCI and NSEI
– NS SDU
– Link Selector Parameter (in Request only)
– BVCI and NSEI
– congestion cause
– BVCI and NSEI
– NS affecting cause
– transfer capability
This primitive is used by the NS user entity to send a NS SDU to its peer entity via a BVC. The NS entity sends the NS SDU in unacknowledged mode. The Link Selector Parameter is used to identify the NS SDUs which must be sent in order relatively to each other. The NSEI is used by the NS entity to select the group of NS-VCs corresponding to the addressed remote entity.
This primitive is used by the NS entity to provide the NS user entity with a NS SDU received on a virtual connection. The NS SDU are received in unacknowledged mode. BVCI together with NSEI indicate which BVC the NS SDU was received on.
The NS entity shall be able to detect when a congestion situation starts and ends on an NS-VC.
This primitive is used by the NS entity to report to the NS user entity that congestion is detected or that the congestion situation has disappeared. The BVCI and NSEI of the affected BVC and the congestion cause are reported to the NS user entity. Typically, the cause indicates the direction of transmission affected by the congestion.
There may be situations where an NS-VC becomes unavailable for NS user traffic. When this occurs, the NS user is informed of the degradation of the transfer capacity by means of this primitive including the "transfer capability" parameter.
When an NS-VC previously unavailable for NS user traffic becomes available again, the NS user entity is also informed by means of this service primitive, indicating the current transfer capability.
This primitive may be used in response to an NS-UNITDATA-Request primitive which the NS is unable to serve because of e.g. NS-VC failure.
This primitive may also be used upon recovery after a failure affecting the NS.
184.108.40.206 NS SDU
The NS SDUs are specified in 3GPP TS 08.18 . They shall never be inspected by the Network Service entity.
220.127.116.11 Link Selector Parameter
The Link Selector Parameter is included in the NS-UNITDATA-Request primitive for load sharing purposes as described in clause "Requirements on load sharing function".
18.104.22.168 BVCI I and NSEI
BVCI and NSEI parameters are included in the service primitives to identify the BVC for which the service is provided. These parameters are used by the NS entity to multiplex the NS SDUs over the NS-VCs.
22.214.171.124 Congestion cause
The congestion cause shall indicate the affected direction of transmission and may be set to the following values:
a) congestion detected, backward
b) end of congestion, backward
c) congestion detected, forward
d) end of congestion, forward
126.96.36.199 Transfer capability
This parameter is used to report to the NS user entity the current transfer capacity available for a BVC, in terms of bandwidth. This parameter may be set to any value from "0" (zero) to the maximum bandwidth provided by the complete set of NS-VCs associated to the BVC.
188.8.131.52 NS affecting cause
This parameter is used to indicate to the NS user entity the reason which caused the NS-STATUS-Indication primitive to be used. The cause values are:
a) NS-VC failure: a failure is affecting one or more NS-VCs, the NS is still available.
b) NS-VC recovery: one or more NS-VCs which were in failure are available again.
c) NS failure: the NS can not provide data transfer services to the NS user.
d) NS recovery: the NS can provide data transfer services again.