Course
Chap1 System and hardware Configuration
Chap2 SS7 configuration
Chap3 Gb interface configuration
Chap4 Gn/Gp interface configuration
Chap5 MM/SM configuration
Chap6 Charging configuration
Basic Concept
Relevant Hardware
The Gb interface refers to the interface between BSS and SGSN.
E1 acts as its physical connection.
The Gb interface is used for communication between sets of
equipment based on the frame relay protocol.
The UGBI board is the Gb processing interface unit of
SGSN9810.
UGBI is connected with BSS through the E1 line extending from
the UEPI back processing interface unit.
Basic Concept
Moreover, there are one UFEU board and one UEPC board
equipped with UGBI.
UFEU board performs the FR layer function.
UEPC board performs encryption and compression function
respectively.
Basic Concept
Protocol Structure
The protocol stack of the Gb interface is composed of
SNDCP, LLC, BSSGP, NS and FR.
Location of Gb protocol stack at the user plane
Application
IP IP
Relay
SNDCP SNDCP GTP-U GTP-U
LLC LLC
Relay UDP UDP
RLC RLC BSSGP BSSGP
IP IP
MAC MAC Network Network L2 L2
Service Service
GSM RF GSM RF L1bis L1bis L1 L1
Um Gb Gn Gi
MS BSS SGSN GGSN
Basic Concept
Location of Gb protocol stack at the control plane
GMM/SM GMM/SM
LLC LLC
Relay
RLC RLC BSSGP BSSGP
MAC MAC Network Network
Service Service
GSM RF GSM RF L1bis L1bis
Um Gb
MS BSS 2G-SGSN
Basic Concept
E1
E1 is the physical line connecting BSS and SGSN. BSS can be
connected with SGSN either directly or through the intermediate
FR network.
BC
BC refers to the bearer channel of frame relay. As the timeslot
group of E1/T1 line, BC is the physical channel for transmission.
the whole E1/T1 line can be either configured as one BC, or
divided into multiple BCs.
For easy local management, in the same line, BCs are
distinguished by numbers, which are called BCID (BC
Identification).
Basic Concept
At both ends of a line, the local BCID is irrelevant to that of the
same physical BC at the opposite end. Timeslot allocation
configured for BC at one side must be the same as for a specific
BC at the peer end, so that a communicable BC can be formed
to connect the two ends.
PVC
PVC refers to the permanent virtual connection of the frame
relay.
In one BC, a PVC is differentiated from others by its number,
which is called DLCI (Data Link Connection ID).
Basic Concept
NS-VC
NS-VC is the virtual link provided by NS layer for BSSGP layer,
via which NS transmits the data of BSSGP layer.
One NS-VC on the NS layer corresponds to one PVC on FR.
Therefore in data configuration, the configuration of either NS-
VC or PVC will do, for the data of the other will be automatically
configured.
NS-VC is solely identified by NS-VCI, which is unique in SGSN,
so is PVC. The location of NS-VC is determined by the location
of PVC, while the location of PVC is determined uniquely by
UGBI board number +E1 port number +BCID+DLCI.
NS-VC in SGSN corresponds to NS-VC in BSS one by one, and
their IDs are the same.
Basic Concept
BVC, CELL, NSE and their relations
BVC (BSSGP Virtual Connection) is the communication path
between BSSGP peer entities. According to different entities on
BSSGP layer, BVC can be divided into PTP (POINT-TO-POINT)
BVC, PTM (POINT-TO-MULTIPOINT) BVC and SIG
(SIGNALLING) BVC.
NSE (Network Service Entity)
CELL, to GB interface, is the cell of GPRS.
CELLs correspond to PTP BVCs one by one. One CELL is only
subordinating to one NSE, but one NSE can include multiple
CELLs.
Basic Concept
One PTP entity corresponds to one PTP BVC, and one signaling
entity corresponds to one SIG BVC. One PTP BVC is only
subordinating to one signaling entity, but one signaling entity
SIG can include multiple PTP BVCs.
At the maintenance console, the resetting of PTP BVC and
displaying of BVC status can be performed.
As to SIG BVC, maintenance commands can be used to reset
the specified SIG BVC from the maintenance console and to
display its status.
Basic Concept
Gb Interface Configuration procedures are as follows:
Configure the E1 link on UFEU.
Configure BC on the already configured E1. Specify time slot
correspondence between BC and the already configured E1, the
protocol working mode of BC and the local LMI protocol
parameter.
Configure the NS layer parameter:
the maximum number of NS-VCs supported by each UGBI board,
number of NSEs supported by each board and some parameters
required for the NS-VC management.
Basic Concept
Configure NS-VC
For one NS-VC is corresponding to one PVC, the PVC of NS-VC is
configured during the configuration of an NS-VC.
One NS-VC is located at BC of an E1 and belongs to an NSE. It
should be configured as specified in the plan.
Configure the NSE parameter, specify the UGBI board to
process the SIG entity. Specify whether the NSE supports PFC
(Packet Flow Context) and CBL (Current Bucket Level) functions.
Configure the general information at the Gb interface such as
the number of cells of each UGBI board and number of MSs that
can be processed by each UGBI board
Basic Concept
Configure the parameter at the NS layer, such as NSVC number
per board.
Configure the parameter at the BSSGP layer, such as times of
BVC reset sent parameter.
Configure the parameter at the LLC layer such as the maximum
number of SAPIs supported by LLC on a UGBI board.
Configure the parameter at the SNDCP layer such as the
number of N-PDUs that can be buffered in SNDCP of a UGBI
board and the data compression parameter.
Gb Interface Configuration
The data to be negotiated in the data configuration at the Gb interface
are shown in Table
Parameter type Parameter content
BC parameter BC time slot distribution, BC mode and FR protocol mode
NS-VC
NS-VCI, NSEI, BCI and DLCI
parameter
Gb Interface Configuration
1. E1 Configuration
ADD E1T1 is used to configure the E1 port of UFEU.
Only E1 configuration is completed, can the FR physical layer
function be provided. Otherwise, neither further configuration of
BC nor loop back operation can be performed.
ADD E1T1CFG: SRN=1, SN=1, PORT=1, LKFRMT=DF,
LKCT=HDB3;
Gb Interface Configuration
2.BC Configuration
The basic principles for BC allocation are as follows:
The time slots occupied by the BC corresponding to SGSN and
PCU should be the same.
If BSS is connected with SGSN directly in the point-to-point
manner:
The BC corresponding to SGSN and PCU should be transmitted
via the same pair of E1 lines. Moreover, the BCID codes of them
should be identical.
It is recommended to bind as more time slots of E1 as possible
to one BC. For example, the 31 time slots may be bound to one
BC.
Gb Interface Configuration
The BC mode at SGSN should correspond to the data
configuration at PCU. The PCU end is generally configured as
DTE while the SGSN end as DCE. For example, if PCU is
configured as DCE, SGSN has to be configured as DTE.
If BSS and SGSN are connected through an intermediate FR
network:
Both BSS and SGSN should act as DTE.
The two ends of the line should negotiate about the distribution
of the time slots in BC. It is recommended to configure as more
time slots as possible in one BC so as to simplify the
management.
Gb Interface Configuration
It is recommended to set the valid bandwidth control parameter
BWCNTL as NO.
ADD BC: SRN=1, SN=0, PN=0, BCID=0, TS="00001000",
DLCIT=1, MODE=DCE, PROTOCOL=Q933, BWCNTL=NO;
Gb Interface Configuration
3. NSVC Configuration
One group of NS-VCs corresponds to one group of cells. They
are identified using the same NSEI. The SIG is created for each
group of cells to manage the cell group
ADD NSVC: OTHERNODE="BSS0", NSVCI=0, NSEI=0,
SRN=0, SN=0, PN=0, BCID=0, DLCI=16;
Gb Interface Configuration
4. NSE Configuration
The objective of the NSE configuration is to determine which
UGBI board of the SIG entity should be used to process the
BSSGP layer. NSE has to exist in the configured NSVC.
The following commands can be used to configure NSE of
SGSN:
ADD NSE: OTHERNODE="TO BSS0", NSEI=0, SRN=0, SN=0,
BSSID=0, FLUSTHT=2000, PFC=YES, CBL=YES;
Gb Interface Configuration
5. Protocol Parameter Configuration
The protocol parameter configuration includes the configuration
of parameters at each protocol layer (such as NS, BSSGP, LLC
and SNDCP) and the Gb common information parameter. The
system provides default values for these parameters. The user
can make adjustment to meet the actual requirements.
To set the Number of GBs per subrack = 12 , Number Cells per
board = 1024 , Number of NSEs per board = 100 ,LSP range =
1024 , the following command can be used:
Gb Interface Configuration
SET GB: GBNPF=12, CELLNPB=1024, NSENPB=128,
LSPR=1024;
To set the number of NSVCs of the board as 20, the following
command can be used:
SET NS: NSVCNUM=20;
Gb Interface Configuration
To set the interval of the reset timer at the BSSGP layer as 30s,
the interval of the BVC flow control timer as 6s, the re-
transmission times of the reset message as 3, and the minimum
interval of the BVC flow control transmission as 1s, the following
command can be used:
SET BSSGP: TMRRESET=30000, TMRMSFLOW=6000,
BVCRESETRTYNUM=3, CTMR=1;
Gb Interface Configuration
To set that the SNDCP layer supports the protocol compression
(PROTOCOLMODECOMPRESS) and data compression
(DATAMODECOMPRESS), the following command can be used:
SET SNDCP: PMC=YES, DMC=YES;
Gb Interface Configuration
6. Cell Reference Parameter Configuration
The cell configuration is made at the BSS side.
No special cell configuration is needed at the SGSN side.
After a cell has been configured at the BSS side, the cell
information synchronization will be completed at the SGSN side
automatically.
Cells at the SGSN side will be evenly distributed on as many
UGBI boards as possible to meet the requirement for load
sharing.
Gb Interface Configuration
The cells at the SGSN side can be distributed as recommended
through the data configuration.
Moreover, the already existing cells can be deleted and the
UGBI board accommodating the cell can be changed.
Use the ADD CELLREF command to add the cell configuration
parameter. The parameter descriptions are as follows:
