Trau Formats Version 1 Rev 2

Trau Formats - cont.

The sub timeslots that make up the Trau on the BTS/BSS link must be
on the same E1 Link.
The sub timeslots that make up the Trau on the PCU/BSS link must be
on the same E1 Link.
Once the Trau timeslots have been enabled and allowed, all
Trau
timeslots on that carrier will be classed as trau of that particular type.
32K & 64K Trau are not allowed with sub-equipped RTF's.
A 64K Trau may only be configured if the radio type is CTU2.
pkt
_radio_type <*>
* 0 = none
1 = 16K
2 = 32k
3 = 64k
MOTOROLA LTD.2002
SYS102 - BSS (GPRS) Database
TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED
2-19
Version 1 Rev 2 LCF
LCF
GPRS Signalling Link (GSL) are managed at the BSS by Link Control Functions (LCFs). The
number of GSLs that an LCF can manage is referred to by max_gsls. This maximum may not
exceed 12. While the LCF can manage GSLs along with other link devices, for example RSLs,
CBLs, GSLs, MTLs and LMTLs, certain combinations are not recommended
The number of GSLs supported by the LCF must not exceed the maximum number it can support.
The maximum number of GSLs per LCF are defined by the number of available GPROC slots and
is limited to 12. To allow for this new expansion, 24 will now be a valid entry for gproc_slots
when at a BSS only. During LCF equipage the maximum number of MTLs, CBLs, LMTLs and
GSLs are specified. The total number of these combined must be less than
gproc_slots - Reserved HDLC Channels.
2-20 SYS102 - BSS (GPRS) Database
TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED
MOTOROLA LTD.2002
LCF Version 1 Rev 2
LCF - cont.
Enter the function ID for the LCF: <*> 0 - 24
Enter the number of MTLS the LCF can manage: <*>
* 0-2
Enter the number of LMTLS the LCF can manage: <*>
* 0-2
Enter the number of CBLs the LCF can manage: <*>
* 0-1
Enter the number of GSLs the LCF can manage: <*>
* 0-12
equip bsc LCF
MOTOROLA LTD.2002
SYS102 - BSS (GPRS) Database
TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED
2-21
Version 1 Rev 2 GPRS Signalling Link (GSL)
GPRS Signalling Link (GSL)
The GPRS Signalling Link (GSL), consists of one or more 64Kbps LAPD signalling links
timeslots on a GPRS Data Stream (GDS) LAPD link. The GSL is used for signalling, code
download and communication between the PCU and the BSS.
The maximum number of GSLs that may be equipped to a PCU is 60, with a maximum of 30 GSLs
being assigned to any GDS LAPD link. The first GSL equipped to a GDS LAPD link will use timeslot
1 of the GDS and the second GSL equipped to the same GDS LAPD link will use timeslot 2.
A GSL must be equipped to the default location to allow code download. The maximum number of
GSLs equipped, must not exceed the maximum number of GSLs that the Link Control Functions
(LCFs) at the BSS can manage. An LCF at the BSS is capable of handling up to 12 RSLs but
must not process any other type of link. The LCF which controls the GSL may be assigned
manually or automatically, using the parameter gsl_lcf_mapping.
If the parameter gsl_lcf_mapping is set to automatic, the LCF identifier will
not be prompted when equipping a GSL.
LCF Mapping
The operator has the ability to decide on manual or automatic LCF mapping at the BSS for control
of GSLs. The parameter used for this is gsl_lcf_mapping. During sysgen, the operator may
choose either option. Outside of sysgen mode, manual is the only option allowed.
GSL identifiers
When viewed from a BSS, the GSL will have an identifier from 0-2 which matches the PCU
ID. When viewed from the PCU, the GSL id will always be 0.
example
The second GSL on the first GDS link going from the BSS to PCU 1, will have a device
id of 1, 1, 0 at the BSS and 0, 1, 0 at the PCU
2-22 SYS102 - BSS (GPRS) Database
TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED
MOTOROLA LTD.2002
GPRS Signalling Link (GSL) Version 1 Rev 2
GPRS Signalling Link (GSL) - cont.
MSI
BSS
MMS
MMS
MSI
PCU
MMS
MMS
GSL 1
GSL 0
Sync 0
1
2
31
Enter the GSL identifier: <*>
* 0 - 59
Enter the unique GDS identifier: <*>
* 0 - 37
Enter the LCF: identifier: <*>
* 0 - 24
MMS MMS
MSI
RSL
Sync 0
1
2
31
RSL
Sync 0
1
2
31
NIU
NIU
BTS 1
BTS 2
S
L
O
T
1
1
0
S
O
C
K
E
T
0
equip <PCU_ID> GSL
gsl_lcf_mapping <*>
*0 = manual mode
*1 = automatic mode
Default = 0 outside Sysgen
Default = 1 inside Sysgen
MOTOROLA LTD.2002
SYS102 - BSS (GPRS) Database
TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED
2-23
Version 1 Rev 2 Network Service
Network Service
The Network Service performs the transport of NS SDUs between the SGSN
and the BSS. The services provided are:
Network Service SDU transfer
Network congestion indication
Status indication
An SGSN and a BSS may use different physical links for connecting to each other. Each physical link
is locally (at each side of Gb interface) identified by means of a physical link identifier.
Each physical link supports one or more Network Service Virtual Links (NS-VL). Each NS-VL
is identified by means of a Network Service Virtual Link Identifier. The significance (i.e.
local or end to end) depends on the configuration of the Gb interface. The NS_VLI is the
association of the Frame Relay DLCI and the bearer channel identifier. Within a Motorola
solution, only one bearer channel is allowed on a physical link.
In order to provide end to end communication between the SGSN and the BSS irrespective of
the exact configuration of the Gb interface the Network Service Virtual Connection is used. The
NS_VCs are end to end virtual connections between the BSS and the SGSN. At each end of the
Gb interface there is a one to one correspondence between NS_VCs and NS_VLs. An NS_VC is
identified by the means of a Network Service Virtual Connection Identifier (NS_VCI).
Functions of Network Service
The responsibilities of Network Service are:
data transmission
load sharing of Network service traffic over the available Network Service
Virtual Connections (NSVCs).
node management functions including:
periodic testing of NSVCs,
blocking and unblocking of NSVCs
reset of connections in an unknown state.
Network service is independent of the underlying Frame Relay layer. While Frame Relay provides a
virtual communication path between the BSS and an access node of the intermediate network used on
the Gb interface, Network Service provides an end-to-end virtual path between the SGSN and the BSS.
A Base Station GPRS Virtual Connection (BVC) is a virtual end-to-end communication path between
remote BSSGP entities. BSSGP entities are classed as point-to-point, signalling and point to multipoint.
There is one point-to-point entity for every cell providing a GPRS service. For a BSS there is one
BSSGP signalling entity used for BSS signalling such as paging between the SGSN and BSS (in effect
a dummy cell). A unique BVCI (default of zero) is always reserved for the signalling BVCI. Point to
multipoint is for future use. Every BSSGP entity is identified by a unique BSSGP Virtual Connection
Identifier (BVCI). These are assigned on PCU initialization but may be changed by the Network operator.
The Network Service Entity (NSE) is used to identify peer NSE entities between the BSS and SGSN.
For every PCU within a BSS, there is one Network Service Entity Identifier (NSEI). Each NSEI
represents a BSS/SGSN communication path. All NSVCIs are automatically mapped to an NSEI and
are unique within an NSEI and so a BSS. Each BVCI is also mapped automatically to an NSEI. For
example, a cell providing GPRS service will have a point-to-point BVCI. A cell is part of a BSS, so a
BVCI is part of a BSS. A BSS is identified by an NSEI so the BVCIs are mapped to the NSEI.
2-24 SYS102 - BSS (GPRS) Database
TRAINING PURPOSES ONLY - THIS MANUAL WILL NOT BE UPDATED
MOTOROLA LTD.2002