owb091009(slide)sgsn9810 v900r010c02 gb interface data configuration-20101105-b-v2.0

www.huawei.com

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

Gb Interface Data Configuration

ISSUE2.0

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

References 3GPP TS 48.016

SGSN9810 Configuration Guide


Contents

1. Basic Concepts

2. Data Configuration for Gb over FR3. Data Configuration for Gb over IP


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.


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.

Um Gb SGSNMS

GMM/SM

LLC

RLC

MAC

GSM RF

NetworkService

RLC

MAC

GSM RF

BSSGP

L1bis

Relay

BSS

GMM/SM

LLC

BSSGP

L1bis

NetworkService


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.

Um Gb Gn GiSGSN GGSN

Application

MS

IP

SNDCP

LLC

RLC

MAC

GSM RF

NetworkService

RLC

MAC

GSM RF

BSSGP

L1bis

Relay

BSS

Relay

GTP-USNDCP

LLC

BSSGP

L1bis

L2

L1

IP

NetworkService

UDP

L2

L1

IP

GTP -U

IP

UDP


BC

•SGSN:NS

E1

E1 1TS0~TS31

•BSS:

NSE1

•TS3•TS2•TS1

BC1(TS1~TS3)

BC2(TS4~TS6)

NSVC 1

NSVC 2

NSVC 3

NSVC 4•TS6

•TS4•TS5

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.


Concepts Related to the Gb Interface

Gb BSS

LLC

BSSGP

L1

SGSN

NS

L1

MAC

BSSGP RLC

RELAY

NS

Sub-Network Service / Sub-Network Service protocol

Network Service Control / Network Service Control protocol

Network Service

The 3GPP protocol defines that the NS sublayers use the FR or IP network as the bearer network.


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.

NSVCINSVCI

PVCPVC


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.

SGSGSNSN

(BVCI 1-4)(BVCI 1-4)

GGbb

(BVCI 5-8)(BVCI 5-8)

NSEI-1NSEI-1

NSEI-2NSEI-2

BVC = BVCI + NSEI

BBSSCC

BVCI 6BVCI 6BVCI 5BVCI 5

BVCI 7BVCI 7

BVCI 8BVCI 8

BBSSCC

BVCI 2BVCI 2BVCI 1BVCI 1

BVCI 3BVCI 3

BVCI 4BVCI 4


Contents

1. Basic Concepts 2. Data Configuration for Gb over FR

3. Data Configuration for Gb over IP


SGSN and PCU Negotiation Data

NSE

NSVC NSVC NSVC

DLCI DLCI DLCI

BC BC

E1

1:N

1:1

N:1

N:1

NSVC

DLCI

BC

E1

SGSN and PCU negotiation data: NSE, NSVC, DLCI, and timeslot

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.

BSSGP layerBSSGP layer

NS layerNS layer


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.


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.

PCU1PCU1 PCU2PCU2

EECCUU

EECCUU


Gb over FR Related Hardware

MM/SM/SNDCP ECU SPP process

LLC

BSSGP

NS

FR

Physical Layer ETI

ECU LLP processECU LLP process

ECU GBP processECU GBP process


Gb over FR Networking Example

NSEI=1

BSS1

BSS2

460010001010001

460010001010002

460010001010003

460010002010001

460010002010002

460010002010003

Port 0

Port 1

1

2

34

SGSNSGSN

ECU

ECU

ECU

ETI

ETI

ETI0/0

0/1

0/2

TS=1-10,DLCI=100, NSVCI=11

Port 1

Port 0

TS=2-17,DLCI=100, NSVCI=22NSEI=2

TS=1-9,DLCI=100,

NSVCI=12

TS=4-20,DLCI=100, NSVCI=21


Networking Data

Link Link No.No.

SubracSubrack No.k No.

Slot Slot No.No.

PorPort t

No.No.

BCIBCIDD

TimesTimeslotlot

DLDLCICI

NSVCNSVCII

NSEINSEI BSSID

1 0 0 0 0 1~10 100 11 1 BSS1

2 0 0 1 0 4~20 100 21 2 BSS2

3 0 1 0 0 1~9 100 12 1 BSS1

4 0 1 1 0 2~17 100 22 2 BSS2


Configuration Procedure

Step Action Performed LMT Command

1 Add related boards. CGP ADD BRD

2 Add related process groups. SGSN ADD

PROCESSGRP

3 Set information about the ETI. CGP SET ETICFG

4 Set information about the

E1/T1 port.CGP SET ET1PORT

5 Add BCs. SGSN ADD BC

6 Add NSVCs. SGSN ADD NSVC

7 Add NSEs. SGSN ADD NSE


Step 1: Add Related Boards

ADD BRD: ADD BRD: SRN=0, SN=0, METYPE=SGSN,

FBRDHTYP=UPBA3, BBRDHTYP=ETIA0, APPTYPE=ECU;

ADD BRD: SRN=0, SN=1, METYPE=SGSN,





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;


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; SET ET1PORT: SRN=0, SN=1, 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;


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;


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.


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.


DTE/DCE/DLCI

FR interface types: DTE and DCE

If a link is Down, the DTE sends link setup request to the DCE.

LAN LANFRDLCI

DLCI

DCE

DCE

DTEDTE

One NSVC corresponds to one PVC.

FR is based on the PVC and identified by the DLCI.


DTE/DCE Configuration Principle

BC

DCE

DCE

DTE

DTE

BSC SGSN

BSC SGSN

DTE DTE

FR

FR

Scenario 1

Scenario 2


DLCIThe 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 1 2 3 4 5

DLCI value 16 to

1007

16 to

1007

1024 to

64511

2048 to

129023

131072 to

4194303

The DCLI on the SGSN should be the same as the DCLI on the PCU. The value is usually 1.


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;


SRN=0, SN=0, PRON=1, PN=1, BCID=0, DLCI=100;


SRN=0, SN=1, PN=0, BCID=0, DLCI=100;


SRN=0, SN=1, PN=1, BCID=0, DLCI=100;


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;


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


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.

Gb Interface Fr Trace_2009-05-19-14-12-52.ptmf


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.Gb_Ns_2009-05-19-14-25-10_e1.ptmf


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.


Contents

1. Basic Concepts 2. Data Configuration for Gb over FR3. Data Configuration for Gb over IP


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.


Gb over IP Related Boards

MM/SM/SNDCP ECU

LLC

BSSGP

NS

IP EPU

L2/Physical Layer PFI


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


Example

IP network

Ethernet interface

EPU

PFI

EPU

PFI

Logical IP address

IP of PCU1

10.20.20.1:3322

/10.20.20.2:3323

IP of PCU2

10.20.30.1:2244/

10.20.30.2:2245

IP of PFI:10.30.30.1/10.30.30.2

IP of EPU: 10.10.10.1/10.10.11.2

Router

IP of router: 10.30.30.3

PCU1 PCU2

UDP port: 3344, 3345

IP route

ECU


Networking Data

Board Subrack No.

Slot No.

Active/Standby

Back board

Upper Subboard Lower Subboard

ECU 0 0 A 　　　ECU 0 2 A 　　　EPU 3 10 A PFI EEC 　 EEC

EPU 3 12 A PFI EEC 　 EEC


IP Networking Data

Data Type Data Item ValueIP address and UDP port of the PCU IP address and UDP port of PCU 1 10.20.20.1:3322

IP address and UDP port of PCU 1 10.20.20.2:3323



IP address of the PFI port on the SGSN

Interface (3/10/1) 10.30.30.1

Interface (3/12/1) 10.30.30.2

IP address of the Gb logical interface (the IP address is provided by the EPU)

EPU(3/10) 10.10.10.1

EPU(3/12) 10.10.11.2

UDP port corresponding to the IP address of the Gb logical interface

ECU(0/0) 3344

ECU(0/2) 3345


IP Routing

EPU(3/10)

PFI(3/10/1)

PCU/BSS

ROUTER

EPU IP

IP network

PCU IPDATA EPU IP PCU IP

Physical route Logical route


IP Virtual Link

ECU(0/0)

ECU(0/2)

EPU(3/10)

EPU(3/12)

IP triplet virtual link 1


IP Virtual Link ECU EPU IP EPU UDP Port

1 0/0 10.10.10.1 3344

2 0/0 10.10.11.2 3344

3 0/1 10.10.10.1 3345

4 0/1 10.10.11.2 3345




IP NSVC

ECU(0/0)

ECU(0/2)

IP NSVC 1

IP NSVC 2

IP NSVC 3IP NSVC 4

PCU (NSEI=1)

Board 1

Board 2

ECU(0/0)

ECU(0/2)

IP NSVC 5

IP NSVC 6

IP NSVC 7IP NSVC 8

PCU (NSEI=2)

Board 1

Board 2


IP NSVC DataIP NSVC NSEI NSVCI ECU SGSN IP

(EPU)SGSN PORT

PCU IP PCU Port

1 1 11 0/0 10.10.10.1 3344 10.20.20.1 3322

2 1 12 0/0 10.10.11.2 3344 10.20.20.2 3323

3 1 13 0/2 10.10.10.1 3345 10.20.20.1 3322

4 1 14 0/2 10.10.11.2 3345 10.20.20.2 3323

5 2 21 0/0 10.10.10.1 3344 10.20.30.1 2244

6 2 22 0/0 10.10.11.2 3344 10.20.30.2 2245

7 2 23 0/2 10.10.10.1 3345 10.20.30.1 2244

8 2 24 0/2 10.10.11.2 3345 10.20.30.2 2245


Networking Diagram

PCU IPEPU IPDATA

IP network

IP triplet virtual link

IP NSVCEthernet interface

PFI

EPU

PFI

Logical IP address

IP of PCU1

10.20.20.1:3322

/10.20.20.2:3323

IP of PCU2

10.20.30.1:2244/

10.20.30.2:2245

IP of PFI:10.30.30.1/10.30.30.2

IP of EPU: 10.10.10.1/10.10.11.2

Router

IP of router: 10.30.30.3

User data and control signaling

IPVlink

PCU1 PCU2

UDP port: 3344, 3345

Ethernet

ECU


Configuration Procedure

Step ActionPerformed on

the CGP or SGSN

Command

1. Configure the boards and related process groups.1 Add the ECU. CGP ADD BRD

2 Add the EPU. CGP ADD BRD

3 Add the process group on

the ECU. SGSN ADD PROCESSGRP

4 Add the process group on

the EPU. SGSN ADD PROCESSGRP


Configuration Procedure (Cont.)


the CGP or SGSN

Command

2. Configure the IP routes.5 Set the port on the PFI. CGP MOD PORT

6 Activate the port on the PFI. CGP ACT PORT

7 Set the public IPv4 address

segment of the EPU.SGSN ADD PUBNWIP

8 Set the IP addresses . SGSN ADD IFIP


Configuration Procedure (Cont.)


the CGP or SGSN

Command

3. Configure the Gb interface.

9 Set the service IP address of the Gb

interface.SGSN ADD BRDIP

10 Add NSEs. SGSN ADD NSE

11 Add local endpoints of the Gb

interface.SGSN ADD

GBIPLOCENDPT

12 Add peer endpoints of the Gb interface. SGSN ADD

GBIPRMTENDPT


Step 1: Add the ECU ADD BRD:


FBRDHTYP=UPBA3, APPTYPE=ECU;


FBRDHTYP=UPBA3, APPTYPE=ECU;


Step 2: Add the EPU ADD BRD:


FBRDHTYP=MPF1, BBRDHTYP=PFI, APPTYPE=EPU,

BUPDBRDTYPE=EEC, BDOWNDBRDTYPE=EEC;


FBRDHTYP=MPF1, BBRDHTYP=PFI, APPTYPE=EPU,

BUPDBRDTYPE=EEC, BDOWNDBRDTYPE=EEC;


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;


PROCGRP=ECUGP_2;


Step 4: Add the Process Group on the EPU

ADD PROCESSGRP: ADD PROCESSGRP: SRN=3, SN=10, PSN=11,

PROCGRP=EPUGP;


PROCGRP=EPUGP;


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;;


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;;


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";

Same subnet

Router

PFI

PFIPFI


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";


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 EPU IP PCU IP

DATA PCU IP EPU IP

PCU

PCU


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;


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;


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;





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.


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


SIZE and Configuration Procedures

PCU SGSN

SNS-SIZE

SNS-SIZE-ACK

Preconfigured EndPoint

PCU SGSN

SNS-CONFIG-ACK

SNS-CONFIG-ACK

SNS-CONFIG

SNS-CONFIG


Modification and Test Procedures

PCU SGSN

SNS-ADD/DELETE/CHANGE WEIGHT

SNS-ACK

PCU SGSN

NS-ALIVE-ACK

NS-ALIVE

NS-ALIVE

NS-ALIVE-ACK

SNS-SIZE

SNS-SIZE-ACK


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


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.


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.

Thank youwww.huawei.com

owb091009(slide)sgsn9810 v900r010c02 gb interface data configuration-20101105-b-v2.0

Documents