You are on page 1of 25

1 Introduction

This document describes the Gb interface which is between the Serving GPRS Support Node (SGSN) or the Combined GPRS Support Node (CGSN) and the Base Station System (BSS) in the Global System for Mobile Communications (GSM) network. The CGSN consists of the SGSN and the GGSN software applications running on the same physical node. Throughout this document, when read from a CGSN point of view, SGSN/GGSN should be read as "the SGSN/GGSN part of the CGSN". If the CGSN differs from the SGSN/GGSN this will be stated. The CGSN, SGSN, and GGSN could generically be referred to as a GPRS Support Node (GSN).

1.1 Scope
This document is divided into the following sections: General description, describing concepts related to the configuration of the Gb interface and showing an overview over the interfaces in the GSM system Hardware, describing the Plug-In Units (PIUs) and the cables related to the Gb interface Protocols, describing the protocols used over the Gb interface Networks, describing the BSS-SGSN connection types Multiplexing of PVCs, describing related multiplexing of PVCs Compression, describing different types of compression Security, including authentication and data confidentiality Configuration of the Gb interface and a dependency tree for the Gb interface configuration Signaling traffic, describing procedures used over the Gb interface Compliance limitation, listing unsupported functions and features Parameters, including parameters available for the configuration of the Gb interface

For instructions on how to configure the Gb interface, refer to Gb Interface Configuration.

1.2 Target Groups


This document is intended for personnel performing first-time configuration of the GSN and other maintenance personnel. It can be used as a basis for training and assumes a basic knowledge of telecommunications and packet-switching networks.

2 General Description
The Gb interface connects and allows exchange of signaling information between SGSN and the BSS. It also allows the exchange of signaling information and user data between SGSN and MS, see Figure 1 and Figure 2. An SGSN can be connected to one or many BSSs, but one BSS can only be connected to one SGSN.

The Gb interface allows many users to be multiplexed over the same physical connection.

Figure 1

Overview of the Interfaces in the GSM System

There is one Gb interface between the SGSN and each Packet Control Unit (PCU) in the BSS. For a description of the SGSN and the CGSN , see SGSN System Description and CGSN System Description.

Figure 2

Connection between SGSN and BSS over the Gb Interface

The GSM Radio Access Network (GSM RAN) consists of a set of BSSs. Each BSS consists of a Base Station Controller (BSC) and a number of Radio Base Stations (RBSs). For the Ericsson GPRS solution, the PCU is located in the BSC, the BSC and RBSs are separated into different physical nodes. The RBS is the radio equipment which transmits and receives information over the radio interface to enable the BSC to communicate with Mobile Stations (MSs) in the BSC area. A

group of RBSs may be controlled by one BSC. The RBS separates the MS-originated circuitswitched calls from packet data communication.

2.1 Main Features


The main feature of the Gb interface is to transfer data, signaling and payload, between the SGSN and the BSS and between the SGSN and the MS.

2.2 Interoperability
The GSN is interoperable with all BSS nodes that supports the Gb interface according to GSM release 97, 3GPP release 99 and 3GPP release 4. Release 97 and Release 99: BSS GPRS Protocol (BSSGP), see Reference [7]. Gb interface Layer 1, see Reference [9]. Network Service, see Reference [11].

Release 4: BSS GPRS Protocol (BSSGP), see Reference [6]. Gb interface Layer 1, see Reference [8]. Network Service, see Reference [10].

3 Hardware
This chapter describes the PIUs and the cables related to the Gb interface.

3.1 Plug-In Units


The single-slot Interface Board T1 E1 version 3 (IBTEv3) is used for E1 or T1 communication. The single-slot Interface Board E1 version 2 (IBE1v2) is used for E1 communication and the single-slot wide Interface Board T1 version 2 (IBT1v2) is used for T1 communication. All three PIUs supports Frame Relay for the Gb interface. The IBTEv3 PIU have two E1/T1 sub-boards with four ports each. The IBE1/T1 PIU have two E1/T1 subboards with two ports each. Note: Connection with several RBSs can exist over the same physical link.

3.2 Cables
The cable specifications and connectors for the Gb physical interface are shown in Table 1, Table 2 and Table 3.

Table 1

Cable specification for the Gb interface over E1 for IBE1v2

Interface Type

Cable Type

Gb interface over E1

Type of Connector on Plug-In Units GSN to CCF or Stewart CompuSGSN to Customer shield series 61, 8Network, Twisted pin receptacle pair cable, 120 Ohm CCF to Customer Stewart CompuNetwork, Coaxial shield series 61, 8cable, 75 Ohm pin receptacle CCF to Customer Stewart CompuNetwork, Twisted shield series 61, 8pair cable, 120 pin receptacle Ohm

Type of External Connector on Cable Sofix 24-pin plug

M4

Sofix 24-pin plug

Table 2

Cable specification for the Gb interface over T1 for IBT1v2

Interface Type

Cable Type

Gb interface over T1

Type of Connector on Plug-In Units GSN to CCF or Stewart CompuSGSN to Customer shield series 61, 8Network, Twisted pin receptacle pair cable, 100 Ohm CCF to Customer Stewart CompuNetwork, Twisted shield series 61, 8Pair cable, 100 pin receptacle Ohm

Type of External Connector on Cable Sofix 24-pin plug

Sofix 24-pin plug

Table 3

1 Cable specification for the Gb interface over E1 and T1 for IBTEv3

Interface Type

Cable Type

Gb interface over E1

Twisted pair cable, 120 Ohm Coaxial cable, 75 Ohm

Gb interface over T1

Twisted pair cable, 100 Ohm

Type of Connector on Plug-In Units Sofix 8-pin plug Sofix 8-pin plug Sofix 8-pin plug

Type of External Connector on Cable Open Open Open

4 Protocols
The Gb interface protocols are divided into protocols connecting the BSS and the SGSN and, protocols connecting the MS and the SGSN, see Figure 3.

Figure 3

Gb Interface Protocol Stack

4.1 E1/T1
E1/T1 is the physical layer. The following configurations are supported: Channelized into 64 kbps channels (E1/T1) or 56 kbps channels (T1) Fractional, using multiple 64/56 kbps channels as one fraction, multiple fractions per physical interface Non-channelized E1, using the entire 2 Mbps interface as one channel

4.2 NS
Network Service (NS) is split into NS control and Frame Relay. 4.2.1 Frame Relay

Frame Relay provides communication for NS control. Frame Relay is a connection-oriented service for transfer of user data over Point-To-Point (PTP) virtual circuits. Only the Permanent Virtual Circuit (PVC) connection mode is supported. A Data Link Connection Identifier (DLCI) is the local link identity of a PVC. For each DLCI, the Committed Information Rate (CIR), Committed Burst Size (Bc) and Excess Burst Size (Be) traffic management parameters can be configured, allowing tuning for optimum throughput. Frame Relay provides no explicit flow control per PVC, but instead simple congestion notification mechanisms. 4.2.2 NS control

NS control is an abstraction of the Frame Relay. It provides load sharing among the available Frame Relay PVCs, and sends management messages to the BSS GPRS Protocol (BSSGP). The NS control defines one Network Service Virtual Connection (NS-VC) for each Frame Relay PVC, and one Network Service Entity (NSE) for the NS-VCs with the same destination. The Network Service Entity Identifier (NSEI) identifies the NSE that is a logical instance for the PCU in the BSS.

4.3 BSSGP
The Base Station Subsystem GPRS Protocol (BSSGP) provides radio-related Quality of Service (QoS) and routing information that is required to transmit user data between a BSS and an SGSN. Additionally, BSSGP provides node management control functions, which enable the automatic configuration of BSSGP Virtual Connections (BVCs) in SGSN, based on data in the BSS. BSSGP initialization is used to synchronize the state of the signaling BVC, and the state and context data (for example cell identifier) of all related PTP BVCs, between the SGSN and the BSS. The initialization is done automatically in the SGSN after a change of the transmission capability in NS layer, or after any other event causing a reset of the signaling BVC. BSSGP initialization is done in the following cases: At system start or restart After recovery from failures, affecting NS or the signaling BVC At operator-requested resets of the signaling BVC

BSSGP initialization starts with the reset procedure for the signaling BVC. If successful, the SGSN awaits a reset procedure to be started by the BSS for each related PTP BVC. If also the BSS resets the PTP BVC, it will be set to state available in the SGSN. If the BSS does not reset the PTP BVC, it will remain in state resetting in the SGSN. During a BSSGP initialization, no Logical Link Control Protocol Data Units (LLC PDUs) can be sent uplink or downlink until the PTP BVC has been successfully reset. Before the LLC PDUs can be sent downlink, the SGSN must have received flow control information from the BSS for the related PTP BVC.

4.4 LLC
The main purpose for the Logical Link Control (LLC) is to ensure packet data transfer between the MS and the SGSN. LLC also provides data confidentiality and error detection.

4.5 GMM, SM and SMS


GPRS Mobility Management (GMM) supports mobility management functions such as attach, detach and Routing Area Update (RAU). It also includes

authentication, user identity confidentiality, user data and signaling confidentiality and identity check. Session Management (SM) supports functionality such as PDP context activation, primary and secondary Packet Data Protocols (PDPs) context, modification and deactivation. Short Message Service (SMS) transfers short messages between MS and the GPRS backbone network. Both mobile-originated and mobile-terminated SMS are supported.

4.6 SNDCP
Subnetwork Dependant Convergence Protocol (SNDCP) schedules each downlink payload packet according to the subscribed QoS. The scheduling mechanism is controlled by a set of node properties. The purpose of SNDCP is to create an interface for the PDP to the lower protocols in the stack. SNDCP is also able to decompress or compress Protocol Control Information and data, and to multiplex several PDPs on the same LLC channel. Compression is further described in Section 7. SNDCP is responsible for segmentation and reassembly of the Internet Protocol (IP) payload packets towards the LLC.

5 Networks
This chapter describes the network types over which the Gb interface traffic is transported.

5.1 BSS-SGSN Connection Types


The alternatives to provide a physical connection between a BSS and an SGSN as well as how to connect BSS and SGSN over the Frame Relay network are described in this chapter. 5.1.1 E1/T1 Direct Physical Link

The SGSN and the BSS can be connected by a E1/T1 direct physical link without intermediate multiplexers, see Figure 4.

Figure 4 5.1.2

A direct E1/T1 physical link

E1/T1 Indirect Physical Link

The SGSN may also be indirect connected through an intermediate network for example the Mobile Services Switching Center/Visitor Location Register (MSC/VLR). The Gb interface traffic can be multiplexed on an existing physical E1/T1 link between the BSS and the MSC/VLR. The MSC/VLR will only crossconnect the links (PCM timeslots) between the BSS and the SGSN. The physical link type at the SGSN may be different from the physical link at the BSS. If the SGSN service area covers several MSC/VLR service areas, the SGSN, may be directly connected to each MSC/VLR. If the SGSN is not directly connected to one or more MSC/VLRs, the existing connections between the MSC/VLRs can be used for the traffic over the Gb interface, see Figure 5.

Figure 5 5.1.3

An E1/T1 Indirect Physical Link

Frame Relay Direct Link

The Gb interface can be set up as a PTP interface. The BSS will act as the user equipment-side Data Terminal Equipment (DTE) on the User-to-Network Interface (UNI), while the SGSN will act as the network-side Data Communication Equipment (DCE). For a Frame Relay Permanent Virtual Circuit (PVC) the same Data Link Connection Identifier (DLCI) must be used in SGSN and BSS, see Figure 6.

Figure 6

Frame Relay direct link

When using Frame Relay direct link, all bandwidth on the physical link is reserved for the traffic over one Gb interface. Frame Relay Direct Link can be combined with both direct and indirect physical links between the BSS and SGSN. 5.1.4 Intermediate Frame Relay Network

The SGSN and the BSS can also be connected through an intermediate Frame Relay network. Both the BSS and the SGSN act as the user side of the UNI. For a Frame Relay PVC the DLCIs may be different in BSS and SGSN, see Figure 7.

Figure 7

Intermediate Frame Relay Network

With an intermediate Frame Relay network, it is possible for SGSN to distribute the bandwidth on a physical link between traffic over several RBS connections and BSSs. An intermediate Frame Relay network can only be combined with indirect physical links between BSS and SGSN, but both E1/T1 and Frame Relay switches can be used.

6 Multiplexing of PVCs
For each GPRS supporting cell in the BSS area, BSSGP uses one Point-To-Point BVC (PTP BVC). All cell-specific signaling data and user data or user signaling data for an MS residing in the specific cell is sent on the respective PTP BVC. All other signaling data is sent through the Signaling BVC. The BSSGP provides means for BVC management and for flow control between the BSS and the SGSN for each cell and for each MS. Multiplexing of PVCs over E1/T1 fractions and the multiplexing of BVCs over NS-VCs can be viewed in Figure 8. PVC1 and PVC2 are multiplexed on the same physical link, which is an E1/T1 fraction. The traffic on a BVC can be transmitted over any of the available NS-VCs. When for a specific mobile an NS-VC is selected all packets for that mobile is sent over the same NS-VC, in order to assure in-delivery of the packets, as long the time between two consecutive downlink packets for one MS is less than Gb_Tns_time_through_fr. In case the NS-VC currently used by a MS is blocked for traffic, then another NS-VC can be selected for the MS.

Figure 8 The Multiplexing of PVCs over E1/T1 Fractions and the Multiplexing of BVCs over NS-VCs

7 Compression
Compression may improve the throughput over the Gb interface. It is highly dependent on the application used, and for already compressed data there will not be any change in the throughout at all. There are two available types of compression for the Gb interface, Transmission Control Protocol and Internet Protocol (TCP/IP) Header Compression and Data Compression.

7.1 TCP/IP Header Compression


The TCP/IP header compression depends on the MS capabilities, and is negotiated with SGSN during PDP context activation. The header compression performed in the SGSN will have impact on the SGSN resources (using memory). For not affecting SGSN characteristics there is a fixed limit of total number of simultaneously activated PDP context using TCP/IP header compression. TCP/IP header compression reduces the size of the header, thus reducing the size of the total message, transmitted over the Gb interface. As a result, the total amount of bytes to be sent on the air interface is reduced, saving radio resources and possibly giving an increased throughput for the end user. Note: Under poor radio conditions and due to mobility, the use of TCP/IP header compression may actually degrade performance, as several retransmissions could be needed.

7.2 Data Compression

The V.42 bis data compression depends on the MS capabilities, and is negotiated with SGSN during PDP context activation. Data compression performed in the SGSN will have an impact on the SGSN resources (using Central Processing Unit [CPU] cycles). So as not to affect SGSN characteristics too much, there is a fixed limit on the total number of simultaneously activated PDP contexts using data compression. V.42 bis data compression typically increases, and may even double, the SGSN transmission efficiency compared with uncompressed data (end-to-end IP payload packets). A compressed message means that less data is sent over the air interface and the Gb interface. The SGSN compresses data packets larger than 200 bytes, and only when compression yields an advantage.

8 Security
This chapter describes security issues for the Gb interface.

8.1 Authentication
The purpose of the authentication procedure is to protect the GSN from unauthorized use. The authentication procedure performs identification and authentication of the service requester, and validation of the service request type, to ensure that the user is authorized to use the particular network service. A parameter in the GSN allows selective authentication at attach and intra RAU in the home Public Land Mobile Network (PLMN).

8.2 Data Confidentiality


Some signaling information elements are considered sensitive and must be protected. The confidentiality of user information concerns the information transmitted on the logical connection between MS and GSN. These needs for a protected mode of transmission are fulfilled by a ciphering function in the LLC. The MS and the GSN must coordinate when starting ciphering. The authentication procedure may start the ciphering. If using ciphering or not is indicated by the GSN in the authentication and ciphering request message. In order to allow start of ciphering on a logical link without authentication, GPRS Ciphering Key Sequence Number (GPRSCKSN) are used. The Authentication and ciphering request message contains the sequence number allocated to the key which may be computed from the Random Number (RAND) parameter carried in the message. If selective authentication is allowed, the GSN will continue ciphering without authentication after receiving an intra Routing Area Update Request message with a valid GPRS-

CKSN. Both the MS and the GSN will use the latest ciphering parameters. Ciphering algorithm type is also negotiated. It is either: no ciphering GPRS Encryption Algorithm/1 (GEA/1) GPRS Encryption Algorithm/2 (GEA/2)

9 Configuration of the Gb Interface


This chapter describes the configuring of the Gb interface, see Figure 9.

Figure 9

Dependency tree for the Gb Interface Configuration

A PLMN could be associated with one or more NSEs due to cell configuration in the BSC. If the feature Multiple PLMN is used, different NSEs may be associated with different PLMNs.

9.1 Settings for E1/T1 and Frame Relay


The following configuration elements are considered: BSC NSE PLMN NS-VC E1/T1 Driver E1/T1 Fraction Frame Relay stack

Frame Relay PVC

In the following sections E1/T1 Driver Section 9.1.1, Frame Relay Stack Section 9.1.2 and Frame Relay PVC Section 9.1.3 are further described. 9.1.1 E1/T1 Driver

For each E1/T1 link the E1/T1 driver settings can be modified to adapt the driver to the needed Pulse Code Modulation (PCM) specification, considering the following issues: Coding Framing Channelization Cyclic Redundancy Check (CRC) For IBTEv3 E1 or T1 can be selected For E1 on IBTEv3 , twisted pair cable (120 Ohm) or Coacial cable (75 Ohm) can be selected The Frame Relay Stack

9.1.2

The sum of PVCs and E1/T1 fractions on a Gb interface PIU must not exceed 115. 9.1.3 Frame Relay PVC

The BSSGP requires specific values for the Frame Relay PVC in order to ensure that, for example, the Frame Relay congestion handling is used in a BSSGP-specific manner.

10 Signaling Traffic
This section gives a brief overview of procedures used over the Gb interface. Services using the Gb interface: BSSGP procedures SNDCP procedures Mobility and Session Management procedures

10.1 BSSGP Procedures


The following BSSGP procedures are used over the Gb interface Data Transfer

The data transfer goes uplink and downlink with PDU transmission to and from the SGSN and the MS. Paging The paging (Packet-Switched) procedure is used by the network to identify the location of the MS, due to reception of a downlink LLC PDU when the READY timer has expired, or to prompt the MS to reattach as a result of network failure paging with IMSI. The SGSN sends a PAGING-PS message to the BSS to initiate the paging procedure. The SGSN may also be instructed by the MSC/VLR to initiate paging procedure for non-GPRS services (Circuit-Switched paging). When the SGSN initiates the paging procedure in this case it sends a PAGING-CS message to the BSS. Radio Access Capability The SGSN receives the MSs radio access capability during attach or RAU and conveys the information to the BSS in a RACAPABILITY message. Suspend or Resume The BSS sends a SUSPEND message to the SGSN when the MS signals to the BSS that it wishes its GPRS service to be suspended. All activity towards the MS, including paging, is stopped by the SGSN as long as the MS is suspended. The activity is resumed when the SGSN receives a Resume message or a RAU Request message. Radio Status The BSS sends a RADIO-STATUS message to the SGSN to indicate exception condition. In case any downlink LLC PDU needs to be sent to the MS, the SGSN initiates the paging procedure. Radio Cause values: Radio contact lost with the MS Radio link quality insufficient to continue communication or cell-reselection ordered.

Flush LL At cell update the network sends a FLUSH-LL message to the BSS inorder to inform that an MS has moved from one cell to another.

BSS can either: Delete old messages Transfer the messages to the new cell within the NSE

Flow Control The flow control mechanism manages the transfer of BSSGP UNITDATA messages, sent by the SGSN on the Gb interface to the BSS. The BSS controls the flow of BSSGP UNITDATA messages to the BVC buffer by indicating to the SGSN the maximum allowed throughput in total for each BVC. The BSS also controls the flow of BSSGP UNITDATA messages to the BVC buffer for an individual MS by indicating to the SGSN the maximum allowed throughput for a certain subscriber. BVC Blocking and Unblocking The BVC blocking and unblocking procedures are initiated by the BSS to remove from use, or bring into use, a BVC. The BSS may block a BVC because of operation and maintenance intervention for a cell, equipment failure at the BSS or cell equipment failure at the BSS. BVC Reset The BVC-RESET procedure synchronizes the initialization of GPRS BVC related contexts at the BSS and SGSN, thus enabling the BSS and SGSN to begin communication in known states. Both the BSS and the SGSN may initiate the procedure due to, for example, a system failure in the SGSN or BSS that affects GPRS BVC functionality (processor recovery). BSS Packet Flow The BSS packet flow procedure enables the BSS to perform traffic policing and resource allocation based on the QoS profiles of an MS both in the uplink and downlink directions. This is achieved by SGSN, during the PDP context activation procedure, informing the BSS of the QoS information associated with various PDP contexts. QoS information related to a MS is stored in a BSS packet flow context. The Aggregate BSS QoS Profile (ABQP) is negotiated between the SGSN and the BSS and is after negotiation stored in both BSS and SGSN. The BSS uses the negotiated ABQP when allocating radio resources and other resources such as buffer capacity. When the BSS packet flow timer expires, the BSS deletes the BSS packet flow context. The BSS may, however, at a later stage when user activity is again detected for an MS, request the SGSN to download the stored BSS packet flow context.

10.2 SNDCP Procedures


The following SNDCP procedures are used over the Gb interface. Multiplexing of Network Packet Data Units Multiplexing of Network Packet Data Units (N-PDUs) from one or several Network Service Access Point Identifiers (NSAPIs) onto a LLC Service Access Point Identifier (SAPI) is performed. In SGSN the NSAPI identifies the PDP context associated with a PDP address. The LLC SAPI identifies the service access point on the SGSN side and the MS side of the LLC interface. N-PDU buffering The N-PDUs are buffered in the SNDCP protocol before they are compressed, segmented and transmitted to the LLC protocol. Management of Delivery Sequence The SNDCP protocol retains the delivery sequence of N-PDUs of each NSAPI between the peer entities. TCP/IP Header Compression TCP/IP header compression makes the header smaller, thus reducing the size of the total message, which is transmitted on the radio interface. As a result, the total amount of timeslots used for a certain message is reduced, giving an increased throughput for the end user in a overloaded radio cell. Data Compression Data compression (V.42 bis) is performed on the entire N-PDU, including the possibly compressed protocol control information. Data compression makes the message smaller with the result that less radio resources are needed for the transmission. As a result, the total amount of timeslots used for a certain message is reduced, giving an increased throughput for the end user in a overloaded radio cell. Segmentation and Reassembly Segmentation of N-PDU to SN-PDU is performed by the SNDCP entity to ensure that any SN-PDU transmitted is no longer than the maximum length (LLC N201). The receiving SNDCP entity reassembles the segments back to the original (possibly compressed) N-PDU.

XID Parameter Negotiation Negotiation of XID parameters between peer SNDCP entities is carried out to ensure optimal information transfer (data compression). Either the MS or the SGSN may initiate XID negotiation. LLC XID negotiation is used for initiating Gb ciphering and increasing the maximum length of an Gb payload segment. Data Transfer The SNDCP entity initiates unacknowledged data transmission when the PDP context for the NSAPI identified in the SNUNITDATA request is activated.

10.3 Mobility and Session Management Procedures


The following mobility and SM procedures are used over the Gb interface. Attach and Detach When an MS wishes to access GPRS services in a PLMN, it sends an Attach Request message to the SGSN. The MS may attach to GPRS services only or to both GPRS and non-GPRS services. When the MS is attached to the network a GMM context is established. If the MS does not want to have access to the GPRS services or to both GPRS services and non-GPRS services any longer, a Detach Request is sent to the SGSN. The network can also initiate the Detach request. When detached the network no longer maintains the connection to the MS, and cannot send or receive any signaling data. Activate, Modify and Deactivate PDP context inclusive secondary PDP context The MS sends an activate PDP context request to the network when it wishes to connect to Packet Data Networks, in order to send and receive user data. An MS may have several simultaneously active PDP Contexts (multiple and secondary PDP contexts). Both the SGSN and the MS may modify an active context due to, for example, changed QoS. The network, the SGSN or the MS may initiate the PDP context deactivation. After a successful PDP context deactivation, the PDP context is no longer active and the MS is unable to communicate with external networks using that PDP context. Routing Area Update

The RAU (intra-SGSN, inter-SGSN and intersystem change (between GSM and WCDMA)) procedure allows a roaming MS to maintain its connection to the GPRS backbone. It also allows it to maintain any activated PDP context towards an external IP Network. The RAU (periodic) procedure is used by the MS to confirm its presence in the network at the expiry of the Periodic RAU timer running in the MS. Authentication of subscriber Authentication of subscriber based on GSM or WCDMA authentication. The network sends an authentication request to the MS to validate whether the MS is authorized to use the particular network services. Ciphering enables user data and signaling confidentiality. Identity Check The network sends an identity request to require the MS to provide its Mobile Identity (International Mobile Equipment Identity Software Version [IMEISV] or International Mobile Subscriber Identity [IMSI]). GMM information The GMM information message is sent by the network with certain information, such as a network identifier, to the MS. The procedure may be invoked at any time during an established GMM context. GMM and SM status The GMM status or SM status messages are sent by the MS or by the network at any time to report certain error conditions. The procedure may be invoked at any time during an established GMM context (GMM status) or an established PDP context (SM status).

11 Compliance Limitations
Unsupported functions and features in SGSN seen from the Gb interface point of view are: LLC acknowledged mode LLC tunneling of message SNDCP acknowledged mode Inter-NSE rerouting SNDCP header compression algorithm according RFC 2507

BSSGP point-to-multipoint data transfer SNDCP V.44 data compression algorithm IP sub-network, that is Gb over IP

12 Parameters
The parameters for the Gb stack are listed in this chapter. The node properties have default values which are to be modified only for protocol tuning or for adapting to specific network conditions. Modifications of a node property take effect immediately. For detailed information, see Parameter Description SGSN R5.5 (G) and Parameter Description CGSN R4 (G).

12.1 Frame Relay Parameters


Committed Burst Size Committed Information Rate Conform Congestion Step Count DLCI Identifier DTE/DCE Excess Burst Size Max. Frame Size Max. No. of PVCs Max. Number of E1/T1 Fractions N391 N392 N393 Standard T391 T392

12.2 Node Properties


This section lists the node properties used over the Gb interface: 12.2.1 NS Control BSSGP LLC GMM, SM and SMS SNDCP NS Control

The following node properties are available for NS control: Gb_Tns_block Gb_Tns_reset Gb_Tns_reset_duration

12.2.2

Gb_Tns_test Gb_Tns_time_through_fr BSSGP

The following node properties are available for BSSGP: 12.2.3 Gb_Bssgp_Th Gb_Bssgp_T2 Gb_FixedPduLifeTime Gb_T7-ResponseCreateBssPfc LLC

The following node property is available for LLC: 12.2.4 Gb_Repeat_paging GMM, SM and SMS

There are no node properties to configure for SM. The following node properties are available for GMM: Gb_MobileReachableTimer Gb_T3314-ReadyTimer Gb_T3314-ReadyTimerMin Gb_T3314-ReadyTimerMax Gb_UncipheredMode Gb_SelectiveAuthenticationFrequency Gb_IdentityImeiEnabled Gb_SendGmmInfo Gb_CellNotificationSupport

The following node properties are available for SMS: 12.2.5 Um_CMLayer Um_TC1N Um_TR1N Um_TR2N SNDCP

The following node properties are available for SNDCP: Gb_Pq_MaxHoldingTime_delay1 Gb_Pq_MaxHoldingTime_delay2 Gb_Pq_MaxHoldingTime_delay3 Gb_Pq_MaxHoldingTime_delay4

Gb_Pq_MaxQueueSize Gb_DataCompIndicator Gb_DataCompThroughputLim Gb_PciCompIndicator Gb_PciCompThroughputLim

12.3 Timers
This section briefly describes the timers used over the Gb interface. 12.3.1 BSSGP timers Mobility Management timers SMS timers BSSGP Timers

The following timers in BSSGP are used: PFT Timer The Packet Flow timer (PFT) holds the maximum time the BSS may store a BSS Packet Flow Context while no uplink data is transmitted. The timer is set by the SGSN and provided to the BSS, the timer is not running in the SGSN. Th Timer The Th timer determines the time interval, after reception of signal MS Flow Control, before the SGSN may use default MS Flow Control parameters for the particular MS. T2 Timer The T2 timer waits in the SGSN for a BVC-RESET-ACK message after a BVC-RESET message has been sent. T7 Timer The T7 timer waits in the SGSN for a CREATE-BSS-PFC-ACK or CREATE-BSS-PFC-NACK message after a CREATE-BSS-PFC message has been sent. 12.3.2 Mobility Management Timers

The following Mobility Management (MM) timer functions are used: Ready Timer

The Ready timer is used to control the time that an MS remains in a READY state. Mobile Reachable Timer The Mobile Reachable timer starts when the state returns to STANDBY and stops when READY is entered. If it expires, the SGSN clears the Paging Proceed Flag (PPF). Implicit Detach Timer The Implicit Detach timer starts when the Mobile Reachable Timer expires. T3350 Attach and RAU Complete Timer The T3350 Attach and RAU Complete timer waits in the SGSN for an Attach Complete message or a RAU Complete message after an Attach and RAU Accept message has been sent. T3322 Detach Accept Timer The T3322 Detach Accept timer waits in the SGSN for a Detach Accept message after a Detach Request message has been sent. Periodic Authentication Timer The Periodic Authentication timer defines the time between each repetition of the authentication procedure for stationary subscribers. 12.3.3 SMS Timer

The following SMS timer functions are used: TR1N Timer The TR1N timer waits in SGSN for an RP_ACK message after having sent an RP_DATA message for a mobile-terminating SMS. TR2N Timer The TR2N timer waits in SGSN before sending an RP_ACK message after having received an RP_DATA message or an RP_SMMA message for mobile-originated SMS or notification.

13 Appendix

In Table 4 the technical data for the E1 and T1 physical interfaces on IBE1, IBT1 and IBTEv3 are listed.
Table 4 Technical Data for the E1 and T1 Physical Interfaces on IBE1, IBT1 and IBTEv3

Function Maximum bit rate Timeslots

E1 2.048 Mbps 1-31 for channelized configuration, 0-31(1) for non-channelized configuration 64 kbps Channelized, Fractional, and Nonchannelized for Frame Relay. ITU-T G.704 framing is not supported for nonchannelized Yes (not applicable for non-channelized) HDB3 (default) and AMI LOF is generated 0.5 +/- 0.5 s after OOF is detected

T1 1.544 Mbps (1.536 Mbps for user data) 0-23(2)

Data rate per timeslot Configuration

56 or 64 kbps Channelized and Fractional for Frame Relay.

CRC4 Coding Framing LOF

Not applicable B8ZS (default) and AMI ESF (default) and SF (also known as D4) LOF is generated 2.5 +/- 0.5 s after OOF is detected. RAI is sent on the line. This is in accordance with ANSI T1.231. LOS is generated 0.5 +/- 0.5 s after it is detected that the interface does not receive any signal. Only supported for IBTEv3. If AIS is received on the T1 line, OOF also occurs, so RAI is sent. When LOF is cleared, RAI is no longer sent.

LOS

AIS

LOS is generated 0.5 +/- 0.5 s after it is detected that the interface does not receive any signal. Only supported for IBTEv3.

(1) The bits correspond to these timeslots in case the channelized configuration would be used, since there are no actual timeslots for the non-channelized configuration.

(2) The timeslots are called 1-24 in some T1 documentation. In Table 5 the technical data for Frame Relay is listed.
Table 5 Technical Data for Frame Relay

Function Frame size (IBT1v2, IBE1v2) Frame size (IBTEv3) Address format CLLM HDLC framing HDLC CRC (FCS) Idle mode Number of idle flags between HDLC frames Polling status DTE/DCE (user/network side of UNI) roles

Support 262 - 1600 octets 262 - 4096 octets 2 octets (10 bit DLCI) Not supported Bit-synchronous 16 or 32 bit Idle pattern or flags 1 - 16 Asynchronous and periodic Supported, when DTE unidirectional and when DCE reverse UNI procedures are used SPRINT or normal ITU-T, ANSI 1991, ANSI 1994 or OGOF 16-1007 Supported by CIR, BC, and BE parameters. DE bit is supported FECN, BECN or both may be used, as well as DE setting Supported Not supported 127 per E1/T1 PMC giving 254 per PIU 120 per E1/T1 PIU

Special conformance LMI standard DLCI range Overbooking

Flow control

PVC SVC Maximum number of VC (IBT1v2, IBE1v2) Maximum number of VC (IBTEv3) Maximum number of fractions 62 (IBE1v2) 48 (IBT1v2) that can be used by Frame Relay (IBT1v2, IBE1v2) Maximum number of fractions 248 (192 when running T1) that can be used by Frame Relay (IBTEv3) Error condition supervision of a User side user-to-network interface

14 Reference List
Ericsson Documents

[1] CGSN System Description, DESCRIPTION, 1/1550-AXB 250 09. [2] Gb Interface Configuration, OPERATION DIRECTIONS, 4/1543CSA 250 14. [3] Parameter Description CGSN R4 (G) PARAMETER DESCRIPTION, 2/190 84-AXB 250 09. [4] Parameter Description SGSN R5.5 (G) PARAMETER DESCRIPTION, 3/190 84-CSA 250 14. [5] SGSN System Description, DESCRIPTION, 44/1551-AXB 250 05.

Standards
[6] BSS GPRS Protocol (BSSGP) 3GPP TS 48.018. [7] BSS GPRS Protocol (BSSGP) GSM 08.18. [8] Gb interface Layer 1, 3GPP TS 48.014. [9] Gb interface Layer 1, GSM 08.14. [10] Network Service, 3GPP TS 48.016. [11] Network Service, GSM 08.16.

You might also like