OWB091009 (Slide) SGSN9810 V900R010C02 GB Interface Data Configuration-20101105-B-V2.0

Gb Interface Data Configuration
ISSUE2.0
www.huawei.com
Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.
References

3GPP TS 48.016 SGSN9810 Configuration Guide
Page2
Contents
1. Basic Concepts 2. Data Configuration for Gb over FR 3. Data Configuration for Gb over IP
Page3
Introduction to the Gb Interface

Gb is the interface between the SGSN and the PCU. Gb is a mandatory interface on the GPRS network. Gb consists of the user plane and control plane.
The control plane is used for resource allocation and access control.
The user plane is used for transparent transmission of user data.
Page4
Protocol Stack of the Gb Interface in the Signaling Plane
The protocol stack of the Gb interface in the user plane

consists of GMM/SM, LLC, BSSGP, NS, and L1bis.
GMM/SM LLC
Relay
GMM/SM LLC RLC MAC GSM RF Um BSSGP Network Service L1bis Gb BSSGP Network Service L1bis
RLC MAC GSM RF
MS
BSS
SGSN
Page5
Protocol Stack of the Gb Interface in the User Plane
The protocol stack of the Gb interface in the signaling plane consists of SNDCP, LLC, BSSGP, NS, and L1bis.
Application IP
Relay
IP SNDCP LLC
Relay
SNDCP LLC RLC MAC GSM RF RLC MAC GSM RF Um BSSGP Network Service L1bis Gb
GTP -U UDP IP L2 L1 Gn
GTP -U
UDP IP L2 L1
BSSGP Network Service L1bis
MS
BSS
SGSN
GGSN
Gi
Page6
BC
A BC corresponds to a timeslot group in an E1/T1 link and is the bearer channel on the frame relay network (FRN).
A BC can contain multiple NSVCs.
TS1 TS2 TS3
BC1(TS1~TS3 )
NSVC 1
NSVC 2
BSS: NSE1
TS4 TS5 TS6
SGSN:NS E1 NSVC 3
NSVC 4
BC2(TS4~TS6)
E1 1 TS0~TS31
Page7
Concepts Related to the Gb Interface
The 3GPP protocol defines that the NS sublayers use the FR or IP network as the bearer network.
Network Service
LL C RE L AY RL C M AC BSSGP NS L1 Gb BSSGP NS L1
Network Service Control / Network Service Control protocol
Sub-Network Service / Sub-Network Service protocol
BSS
SGSN
Page8
NSVC and PVC
The NS layer consists of the following sublayers:
Network service control sublayer: User data is transmitted on the
NSVCs in load-sharing mode.
Subnet service sublayer: It runs the FR protocol and uses PVCs for transmission.
One NSVC corresponds to one PVC.
NSVCI
PVC
Page9
Relation Between the BVC, Cell, and NSE
An NSE provides one signaling BVC and multiple PTP BVCs.
The signaling BVC manages the cells of the NSE and the ID of the signaling BVC is 0.
The PTP BVC is used for transmission.

Gb
B S C
NSEI-1
SG SN B S C NSEI-2
BVC = BVCI + NSEI
Page10
Contents
Page11
SGSN and PCU Negotiation Data

NSE 1:N
SGSN and PCU negotiation data: NSE, NSVC, DLCI, and timeslot BSSGP layer
NSVC 1:1
NSVC
NSVC
NSVC
DLCI N:1
DLCI
DLCI
DLCI
NS layer
The BC ID on the SGSN can be different from the BC ID on the PCU. The BC ID must be unique on an Et/T1 port.
BC N:1
BC
BC
E1
E1
Page12
NSE Configuration Guidelines
An NSE manages a group of NSVCs.
If all NSVCs to a PCU are grouped together, one NSE is required and the group of NSVCs must be configured in one subrack.
If the NSVCs to a PCU are divided into multiple groups, multiple NSEs are required.
The NSE configuration must be bound to a specific ECU. NSEs must be configured equally on different ECUs. The NSE ID must not be 0.
Page13
NSVC Configuration Guidelines
An NSVC must be configured on the same ECU with the BC to be used by the NSVC.
If multiple boards in the back slots of ECUs all have available BCs, configure
the NSVCs of an NSE on different ECU for load balancing among boards.
If only one board in the back slot of an ECU has available BCs, configure the NSVCs on different GBP processes on the ECU for load balancing among
processes.
PCU1
PCU2
E C U
Page14
E C U
Gb over FR Related Hardware

MM/SM/SNDCP LLC BSSGP
ECU GBP process ECU SPP process
NS
FR Physical Layer
ECU LLP process ETI
Page15
Gb over FR Networking Example

NSEI=1
0/0
E C U E TI
Port 0 Port 1
460010001010001
TS=1-10,DLCI=100, NSVCI=11
1 2
BSS1
460010001010002 460010001010003
0/1
E C U
E TI
Port 0
3 4
Port 1 TS=2-17,DLCI=100, NSVCI=22
460010002010001
BSS2
NSEI=2
460010002010002 460010002010003
0/2
E C U
E TI
SGSN
Page16
Networking Data
Link Subrac Slot Por
No. k No. No. t No.
1 2 3 4 0 0 0 0 0 0 1 1 0 1 0 1 0 0 0 0 1~10 4~20 1~9 2~17 100 100 100 100 11 21 12 22 1 2 1 2 BSS1 BSS2 BSS1 BSS2
BCI
D
Times DL
lot CI
NSVC
I
NSEI
BSSID
Page17
Configuration Procedure
Step 1 2 Action Add related boards. Add related process groups. Performed LMT CGP SGSN Command ADD BRD ADD PROCESSGRP SET ETICFG
Set information about the ETI. Set information about the E1/T1 port. Add BCs. Add NSVCs. Add NSEs.
CGP
4 5 6 7
CGP SGSN SGSN SGSN
SET ET1PORT ADD BC ADD NSVC ADD NSE
Page18
Step 1: Add Related Boards
ADD BRD:
ADD BRD: SRN=0, SN=0, METYPE=SGSN, FBRDHTYP=UPBA3, BBRDHTYP=ETIA0, APPTYPE=ECU;
Page19
Step 3: Set the ETI
SET ETICFG:
This command is used to set the TDM type and impedance of the ETI in the configuration database.
For example:
SET ETICFG: SRN=0, SN=0, CFGTDMTYPE=E1,
E1IMPED=E1_75ohm, CFGAPPMODE=FR;
SET ETICFG: SRN=0, SN=1, CFGTDMTYPE=E1, E1IMPED=E1_75ohm, CFGAPPMODE=FR;
SET ETICFG: SRN=0, SN=2, CFGTDMTYPE=E1, E1IMPED=E1_75ohm, CFGAPPMODE=FR;
Page20
Step 4: Set E1/T1 Port
SET ET1PORT:
This command is used to set the attributes of an E1/T1 port in

the configuration database.
For example:
SET ET1PORT: SRN=0, SN=0, STRPORTID=1, ENDPORTID=31, CFGTDMTYPE=E1, CFGE1FRM=DF, CFGE1ENC=HDB3;

Page21
Step 5: Configure the BC
ADD BC:
This command is used to configure the BC.

ADD BC: SRN=0, SN=0, PRON=0, PN=0, BCID=0, BTS=1, ETS=10, DLCIT=1, PROTOCOL=Q933, BWCNTL=NO, BCMODE=DCE;
ADD BC: SRN=0, SN=0, PRON=1, PN=1, BCID=0, BTS=4, ETS=20, DLCIT=1, PROTOCOL=Q933, BWCNTL=NO, BCMODE=DCE;
ADD BC: SRN=0, SN=1, PN=0, BCID=0, BTS=1, ETS=9, DLCIT=1, PROTOCOL=Q933, BWCNTL=NO, BCMODE=DCE;
ADD BC: SRN=0, SN=1, PN=1, BCID=0, BTS=2, ETS=17, DLCIT=1, PROTOCOL=Q933, BWCNTL=NO, BCMODE=DCE;
Page22
BC Configuration Guidelines and Bandwidth Control
BWCNTL: bandwidth control switch
When BWCNTL is set to YES, bandwidth control is performed according to bandwidth usage. If the remaining bandwidth of the BC is greater than the reserved bandwidth, users should be allowed to use the remaining bandwidth.
When BWCNTL is set to NO, the bandwidth of NSVCs must

not be larger than the maximum available bandwidth, that is, users are forbidden to use the bandwidth in addition to the allowed bandwidth.
Page23
Bandwidth Control Example
Assume that a BC occupies timeslots 1 to 31. Each timeslot is 64 K and the total bandwidth is 2 Mbit/s. The BC is configured with two NSVCs.
When BWCNTL is set to NO, the 2 Mbit/s bandwidth is distributed equally among the two NSVCs.
When BWCNTL is set to YES, if there is remaining bandwidth after the CIRs of the two NSVCs are guaranteed, users are allowed to use the remaining bandwidth.
Page24
DTE/DCE/DLCI
One NSVC corresponds to one PVC.
LAN
DTE
DCE
FR
DTE
LAN
DCE
FR is based on the PVC and identified by the DLCI.
FR interface types: DTE and DCE
If a link is Down, the DTE sends link setup request to the DCE.
Page25
DTE/DCE Configuration Principle

Scenario 1
BSC BC DCE DTE DTE DCE SGSN
Scenario 2
BSC
FR
SGSN
DTE
FR
DTE
Page26
DLCI
The DLCI type determines the value range of the DLCI corresponding to the
NSVCs of a BC.

The DLCI ranges from 1 to 5. The DLCI has no default value.

The following table shows the mapping between DLCI types and DLCIs:
DLCI type DLCI value
1
16 to 1007
2
16 to 1007
3
1024 to 64511
4
2048 to 129023
5
131072 to 4194303
The DCLI on the SGSN should be the same as the DCLI on the PCU. The value is usually 1.
Page27
Step 6: Configure the NSVC
ADD NSVC:
This command is used to configure the NSVC.
ADD NSVC: OTHERNODE="to BSS1", NSVCI=11, NSEI=1, SRN=0, SN=0, PRON=0, PN=0, BCID=0, DLCI=100;
ADD NSVC: OTHERNODE="to BSS2", NSVCI=21, NSEI=2, SRN=0, SN=0, PRON=1, PN=1, BCID=0, DLCI=100;
ADD NSVC: OTHERNODE="to BSS1", NSVCI=12, NSEI=1, SRN=0, SN=1, PN=0, BCID=0, DLCI=100;
ADD NSVC: OTHERNODE="to BSS2", NSVCI=22, NSEI=2, SRN=0,

SN=1, PN=1, BCID=0, DLCI=100;
Page28
Step 7: Configure the NSE
ADD NSE:
This command is used to configure the NSE.
ADD NSE: OTHERNODE="to BSS1", NSEI=1, SRN=0, SN=0, PRON=0, BSSID=1;
ADD NSE: OTHERNODE="to BSS2", NSEI=2, SRN=0, SN=1, BSSID=2;
Page29
Gb over FR Interface Status Check
Check the BC status.
DSP BC
Check the PVC status.
DSP FRPVC
Check the NSVC status.
DSP NSVC
Check the SIG status.
DSP SIGBVC
Check the cell information.
LST CELL
Page30
Checking the BC Status
After a BC is connected, the messages exchanged between the
DTE and the DCE are as follows:
The BC is available when the DTE and the DCE are exchanging these messages.
Page31
Checking the NSVC Status
If the NSVC is available, the NS_ALIVE_PDU and NS_ALIVE_ACK_PDU messages
are sent between the SGSN and the PCU. You can trace the messages at the NS layer on the Gb interface. The traced messages are shown as follows:
When the NSVC is unavailable, the PCU does not respond to the NS_ALIVE_PDU message from the SGSN.
Page32
Checking the Cell Information
How to determine that a cell is lost:
On a 2.5G network, the PCU reports cells automatically. If a cell is lost, you can check whether the cell is reported by using the following methods:
Trace the messages on the Gb interface on the LMT of the SGSN. Run RST PTPBVC and specify the cell ID.
If the PCU has reported the cell, you can view the cell ID in the BVC_RESET_ACK message. One message reports one cell.
If the messages do not contain the specified cell ID, it indicates
that the cell is not reported.
Page33
Contents
Page34
Gb over IP Data Configuration Guidelines
General guidelines:
NSEs must be distributed to different ECUs. Consider the capacities of the ECUs during the planning for better implementation of load balancing.
The IP addresses of local endpoints on the NSEs must be set on different ECUs.
Page35
Gb over IP Related Boards

MM/SM/SNDCP LLC BSSGP NS IP L2/Physical Layer EPU PFI ECU
Page36
Gb over IP Negotiation Data

IP address of the router IP address and UDP port of the PCU IP address of the port on the PFI of the SGSN IP address of the Gb logical interface (the IP address is
provided by the EPU)
UDP port corresponding to the IP address of the Gb logical interface
Page37
Example
PCU1
IP of PCU1 10.20.20.1:3322 /10.20.20.2:3323
PCU2
IP of PCU2 10.20.30.1:2244/
IP network
Router
10.20.30.2:2245
IP of router: 10.30.30.3 PFI PFI IP of PFI:10.30.30.1/10.30.30.2 EPU EPU IP of EPU: 10.10.10.1/10.10.11.2 UDP port: 3344, 3345 ECU Logical IP address Ethernet interface IP route
Page38
Networking Data
Board ECU ECU EPU EPU Subrack No. 0 0 3 3 Slot No. 0 2 10 12 Active/ Standby A A A A PFI PFI EEC EEC EEC EEC Back board Upper Subboard Lower Subboard
Page39
IP Networking Data
Data Type
IP address and UDP port of the PCU
Data Item
IP address and UDP port of PCU 1 IP address and UDP port of PCU 1 IP address and UDP port of PCU 2 IP address and UDP port of PCU 2
Value
10.20.20.1:3322 10.20.20.2:3323 10.20.30.1:2244 10.20.30.2:2245 10.30.30.1 10.30.30.2 10.10.10.1 10.10.11.2 3344
IP address of the PFI port on the SGSN IP address of the Gb logical interface (the IP address is provided by the EPU)
Interface (3/10/1) Interface (3/12/1) EPU(3/10) EPU(3/12) ECU(0/0)
UDP port corresponding to the IP address of the Gb logical interface
ECU(0/2)
3345
Page40
IP Routing
EPU IP DATA EPU IP PCU IP PCU IP
EPU(3/10)
PCU/BSS
IP network
PFI(3/10/1)
ROUTER
Physical route
Logical route
Page41
IP Virtual Link
IP triplet virtual link 1
ECU(0/0)
EPU(3/10)
ECU(0/2)
EPU(3/12)
IP Virtual Link
1
2 3 4
ECU
0/0
0/0 0/1 0/1
EPU IP
10.10.10.1
10.10.11.2 10.10.10.1 10.10.11.2
EPU UDP Port

3344
3344 3345 3345
Page42
IP NSVC
IP NSVC 1
ECU(0/0) ECU(0/2)
Board 1
IP NSVC 2 IP NSVC 3
PCU (NSEI=1)
IP NSVC 4
Board 2
IP NSVC 5
ECU(0/0) ECU(0/2)
Board 1
IP NSVC 6 IP NSVC 7
PCU (NSEI=2)
IP NSVC 8
Board 2
Page43
IP NSVC Data
IP NSVC NSEI NSVCI ECU SGSN IP (EPU) 1 2 3 4 5 6 7 8 1 1 1 1 2 2 2 2 11 12 13 14 21 22 23 24 0/0 0/0 0/2 0/2 0/0 0/0 0/2 0/2 10.10.10.1 10.10.11.2 10.10.10.1 10.10.11.2 10.10.10.1 10.10.11.2 10.10.10.1 10.10.11.2 SGSN PORT 3344 3344 3345 3345 3344 3344 3345 3345 10.20.20.1 10.20.20.2 10.20.20.1 10.20.20.2 10.20.30.1 10.20.30.2 10.20.30.1 10.20.30.2 PCU IP PCU Port 3322 3323 3322 3323 2244 2245 2244 2245
Page44
Networking Diagram
IP of PCU1 10.20.20.1:3322 /10.20.20.2:3323
PCU1
PCU2 IP of PCU2
10.20.30.1:2244/ 10.20.30.2:2245
IP network
Router
IP of router: 10.30.30.3 PFI PFI IP of PFI:10.30.30.1/10.30.30.2 EPU IP of EPU: 10.10.10.1/10.10.11.2 UDP port: 3344, 3345 IPVlink Logical IP address Ethernet interface IP NSVC IP triplet virtual link Ethernet
Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved. Page45
DATA
EPU IP
PCU IP
User data and control signaling
ECU
Configuration Procedure
Step Action Performed on the CGP or SGSN
CGP
Command
1. Configure the boards and related process groups.

1 Add the ECU. ADD BRD
2
3
Add the EPU.

Add the process group on the ECU. Add the process group on
CGP
SGSN
ADD BRD
ADD PROCESSGRP
the EPU.
SGSN
ADD PROCESSGRP
Page46
Configuration Procedure (Cont.)

Step Action Performed on the CGP or SGSN
CGP CGP
Command
2. Configure the IP routes.

5 6
Set the port on the PFI.

Activate the port on the PFI. Set the public IPv4 address segment of the EPU. Set the IP addresses .
MOD PORT ACT PORT
7 8
SGSN SGSN
ADD PUBNWIP ADD IFIP
Page47
Configuration Procedure (Cont.)

Step Action
Performed on the CGP or SGSN
Command
3. Configure the Gb interface.

9 10 11 Set the service IP address of the Gb interface. Add NSEs. Add local endpoints of the Gb SGSN SGSN SGSN ADD BRDIP ADD NSE ADD GBIPLOCENDPT
interface. Add peer endpoints of the Gb interface.
12
SGSN
ADD GBIPRMTENDPT
Page48
Step 1: Add the ECU
ADD BRD:
ADD BRD: SRN=0, SN=0, METYPE=SGSN, FBRDHTYP=UPBA3, APPTYPE=ECU;
ADD BRD: SRN=0, SN=2, METYPE=SGSN, FBRDHTYP=UPBA3, APPTYPE=ECU;
Page49
Step 2: Add the EPU
ADD BRD:
ADD BRD: SRN=3, SN=10, METYPE=SGSN, FBRDHTYP=MPF1, BBRDHTYP=PFI, APPTYPE=EPU, BUPDBRDTYPE=EEC, BDOWNDBRDTYPE=EEC;
ADD BRD: SRN=3, SN=12, METYPE=SGSN, FBRDHTYP=MPF1, BBRDHTYP=PFI, APPTYPE=EPU, BUPDBRDTYPE=EEC, BDOWNDBRDTYPE=EEC;
Page50
Step 3: Add the Process Group on the ECU
ADD PROCESSGRP:
This command is used to add a process group on a pair of
boards.
For example:
ADD PROCESSGRP: SRN=0, SN=0, PSN=3,
PROCGRP=ECUGP_2;
ADD PROCESSGRP: SRN=0, SN=1, PSN=4, PROCGRP=ECUGP_2;
Page51
Step 4: Add the Process Group on the EPU
ADD PROCESSGRP:

PROCGRP=EPUGP;
PROCGRP=EPUGP;
Page52
Step 5: Set the Port on the PFI
MOD PORT:
This command is used to modify the attribute of the port of a board in a back slot.
For example:
MOD PORT: SRN=3, SN=10, PORTID=1, PORTTYPE=EETH,
ASISTMOD=AS;;
MOD PORT: SRN=3, SN=12, PORTID=1, PORTTYPE=EETH, ASISTMOD=AS;;
Page53
Step 6: Activate the port on the PFI.
ACT PORT:
This command is used to activate the port that is not in use on

a board in a back slot.
For example:
ACT PORT: SRN=3, SN=10, PORTID=1;;

ACT PORT: SRN=3, SN=12, PORTID=1;;
Page54
Step 7: Set the public IPv4 address segment of the EPU (Optional)
ADD PUBNWIP
This command is used to set the public IP address segment of the EPU so that the IP addresses of the EPU belong to one subnet.
ADD PUBNWIP: IP="10.30.30.0, MSK="255.255.255.0";

Router
Same subnet
PFI
PFI
Page55
Step 8: Set the IP Addresses
ADD IFIP:
This command is used to set the IP addresses of the ports on the PFI.
For example:
ADD IFIP: SRN=3, SN=10, PN=0, IP="10.30.30.1", MSK="255.255.255.0", DESC="EPU interface ip";
ADD IFIP: SRN=3, SN=12, PN=0, IP="10.30.30.2", MSK="255.255.255.0", DESC="EPU interface ip";
Page56
Step 9: Set the Service IP address of the Gb Interface
ADD BRDIP:
This command is used to set the service IP address of the Gb interface.

For example:
ADD BRDIP: SRN=3, SN=10, MSTYPE=SECONDARY, IPT=IPV4, IPV4="10.10.10.1";
ADD BRDIP: SRN=3, SN=12, MSTYPE=SECONDARY, IPT=IPV4, IPV4="10.10.11.2";

DATA DATA
EPU IP PCU IP
PCU IP EPU IP
PCU
PCU
Page57
Step 10: Add NSEs
ADD NSE:
For example, add an NSE for PCU 1.
ADD NSE: OTHERNODE="TO bss1", NSEI=1, SRN=0, SN=0,

PRON=0, BSSID=1, BT=IP ;
For example, add an NSE for PCU 2.
ADD NSE: OTHERNODE="TO bss2", NSEI=2, SRN=0, SN=1,

PRON=0, BSSID=2, BT=IP;
Page58
Step 11: Add Local Endpoints of the Gb Interface
ADD GBIPLOCENDPT:
To add the configuration for a local endpoint of the Gb interface in the
case of GB OVER IP.
Weight
If the NSE of the local endpoint supports static Gb over IP, the SGSN can negotiate the weight of the local endpoint with the peer in advance. If the NSE of the local endpoint supports dynamic Gb over IP, the peer is informed of the weight of the local endpoint through the dynamic CONFIG procedure; in addition, the weight can be changed through the dynamic CHANGEWEIGHT procedure. ADD GBIPLOCENDPT: SRN=0, SN=0, PRON=0, NSEI=1, IPT=IPV4, LIPV4="10.10.10.1", LUP=3344, SW=200, DW=200;
Page59
Step 12: Add Peer Endpoints of the Gb Interface
ADD GBIPRMTENDPT:
To add the Gb Interface IP EndPoint Weight, including remote EndPoint data Weight and signaling weight.

For example:
ADD GBIPRMTENDPT: IPT=IPV4, RIPV4="10.20.20.1", RUP=3322, NSEI=1, SW=200, DW=200; ADD GBIPRMTENDPT: IPT=IPV4, RIPV4="10.20.20.2", RUP=3323, NSEI=1, SW=50, DW=50; ADD GBIPRMTENDPT: IPT=IPV4, RIPV4="10.20.20.1", RUP=2244, NSEI=2, SW=200, DW=200; ADD GBIPRMTENDPT: IPT=IPV4, RIPV4="10.20.20.2", RUP=2245, NSEI=2, SW=50, DW=50;
Page60
Weight

SW is the signaling weight. DW is the data weight.
The local endpoint with a larger weight is preferred by the peer.
For example, if you set the weight of the local endpoint corresponding to an idle link to a large value, this endpoint takes precedence over other endpoints in the selection by the PCU.
Similarly, the SGSN prefers a peer endpoint with a larger weight on the PCU.
Page61
NSVC Automatic Configuration
SGSN9810 V900R010 supports the IP NSVC automatic negotiation function. The automatic configuration of the IP NSVC to the peer PCU is implemented through the following procedures.
SIZE Configuration ADD/DELETE/CHANGE WEIGHT TEST
Page62
SIZE and Configuration Procedures

Preconfigured EndPoint SNS-SIZE SNS-SIZE-ACK
PCU
SNS-CONFIG SNS-CONFIG-ACK SNS-CONFIG SNS-CONFIG-ACK
SGSN
PCU
SGSN
Page63
Modification and Test Procedures

SNS-ADD/DELETE/CHANGE WEIGHT SNS-ACK
PCU
SGSN
NS-ALIVE
NS-ALIVE-ACK
NS-ALIVE NS-ALIVE-ACK SNS-SIZE
PCU
SNS-SIZE-ACK
SGSN
Page64
Gb over IP Interface Status Check
Check the PFI port status.
DSP PORT
Check the route status.
PING
Check whether the IP NSVC is available.
DSP IPNSVC
Check the cell report.
LST CELL
Page65
Checking the IP NSVC Status
If the IP NSVC is available, the NS_ALIVE_PDU and NS_ALIVE_ACK_PDU messages are sent between the SGSN and the PCU. You can trace the messages at the NS layer on the Gb interface. The traced messages are shown as follows:
When the IP NSVC is unavailable, the SGSN does not respond to the NS_ALIVE_PDU message from the PCU.
Page66
Checking the Cell Information
The cell check for the Gb over IP service is the same as the cell check for the Gb over FR server. The BSSGP layer does not distinguish the lower layer bearer type and therefore the management mechanisms of cells are the same.
Page67
Thank you
www.huawei.com

OWB091009 (Slide) SGSN9810 V900R010C02 GB Interface Data Configuration-20101105-B-V2.0

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

OWB091009 (Slide) SGSN9810 V900R010C02 GB Interface Data Configuration-20101105-B-V2.0

Diunggah oleh

Hak Cipta:

Format Tersedia

Gb Interface Data Configuration

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

3GPP TS 48.016 SGSN9810 Configuration Guide

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

Introduction to the Gb Interface

The user plane is used for transparent transmission of user data.

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

Protocol Stack of the Gb Interface in the Signaling Plane

The protocol stack of the Gb interface in the user plane

RLC MAC GSM RF

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

Protocol Stack of the Gb Interface in the User Plane

BSSGP Network Service L1bis

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

A BC can contain multiple NSVCs.

TS1 TS2 TS3

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

Concepts Related to the Gb Interface

Sub-Network Service / Sub-Network Service protocol

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

NSVC and PVC

The NS layer consists of the following sublayers:

Network service control sublayer: User data is transmitted on the

NSVCs in load-sharing mode.

One NSVC corresponds to one PVC.

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

Relation Between the BVC, Cell, and NSE

An NSE provides one signaling BVC and multiple PTP BVCs.

The PTP BVC is used for transmission.

BVC = BVCI + NSEI

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

SGSN and PCU Negotiation Data

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

NSE Configuration Guidelines

An NSE manages a group of NSVCs.

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

NSVC Configuration Guidelines

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

Gb over FR Related Hardware

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

Gb over FR Networking Example

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

CGP SGSN SGSN SGSN

SET ET1PORT ADD BC ADD NSVC ADD NSE

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

Step 1: Add Related Boards

ADD BRD: SRN=0, SN=0, METYPE=SGSN, FBRDHTYP=UPBA3, BBRDHTYP=ETIA0, APPTYPE=ECU;

ADD BRD: SRN=0, SN=1, METYPE=SGSN, FBRDHTYP=UPBA3, BBRDHTYP=ETIA0, APPTYPE=ECU;

ADD BRD: SRN=0, SN=2, METYPE=SGSN, FBRDHTYP=UPBA3, BBRDHTYP=ETIA0, APPTYPE=ECU;

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

Step 3: Set the ETI

SET ETICFG: SRN=0, SN=0, CFGTDMTYPE=E1,

SET ETICFG: SRN=0, SN=1, CFGTDMTYPE=E1, E1IMPED=E1_75ohm, CFGAPPMODE=FR;

SET ETICFG: SRN=0, SN=2, CFGTDMTYPE=E1, E1IMPED=E1_75ohm, CFGAPPMODE=FR;

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

Step 4: Set E1/T1 Port

This command is used to set the attributes of an E1/T1 port in

SET ET1PORT: SRN=0, SN=0, STRPORTID=1, ENDPORTID=31, CFGTDMTYPE=E1, CFGE1FRM=DF, CFGE1ENC=HDB3;

SET ET1PORT: SRN=0, SN=2, STRPORTID=1, ENDPORTID=31, CFGTDMTYPE=E1, CFGE1FRM=DF, CFGE1ENC=HDB3;

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.