MN1788 Tac

s
PLMN
SBS System Specialist TAC
Course MN1788 File 1
A30808-X5226-C559-1-7618
Siemens Ltda. Centro de Treinamento Werner von Siemens R. Pedro Gusso, 2635 - CEP 81310-900 - Curitiba - PR Tel./Fax: (++41) 341-6722 / 341-5013 Al Aluno: (++41) 341-6592 CAS - Central de Atendimento Siemens: 0800 119484 Homepage: http://www.siemens.com.br/IC/tti/index.htm e-mail: treinamento@siemens.com.br
Siemens
MN1788EU08MN_0001 Export Control Marks: AL: 5A001b1 EC:N This course is subject to the European Export Control Restrictions.
2000 Siemens AG The reproduction, transmission or use of this document or its contents is not permitted without express written authority. Offenders will be liable for damages. All rights, including rights created by patent grant or registration of utility model or design, are reserved. Technical modifications possible. Technical specifications and features are binding only insofar as they are specifically and expressly agreed upon in a written contract.
II
MN1788EU08MN_0001
Organization of Siemens Technical Assistance Center - TAC Siemens SBS System Specialist TAC ISO-OSI Model and Protocols
1 2 3 4 5 6 7
Sub-sections
Air Interface Um
Interface Abis
A-Interface/Signaling System CCS7
Synchronization
SBS System Specialist TAC File 1 MN1788EU08MN_0001
Protocols Analyser-K1297-G20
MN1788EU08MN_0001
III
Siemens
Sub-section reference
Sub-section identification 1 2 3 4 5 6 7 MN1788EU08 Organization Siemens TAC MN_0001 MN1788EU08 ISO-OSI Model + Protocols MN_0001 MN1788EU08 Air Interface Um MN_0001 MN1788EU08 Interface Abis MN_0001 MN1788EU08 A-Interface/CCS7 MN_0001 MN1788EU08 Synchronization MN_0001 MN1788EU08 Protocols Analyser-K1297-G20 1 1 1 1 1 1 1 Pages 56 20 92 36 84 24 88
This document consists of 406 pages.
MN1788EU08MN_0001
Organization of Siemens Technical Assistance Center - TAC
Siemens
2UJDQL]DWLRQ RI 6LHPHQV 7HFKQLFDO $VVLVWDQFH &HQWHU 7$&
&RQWHQWV
1 1.1 1.2 1.3 1.4 2 2.1 2.2 2.3 2.4 3 3.1 3.2 3.3 4 4.1 5 6 6.1 6.2 7 Technical Assistance TAC Levels According to Support Services Technical Assistance Tasks Tools used on TAC Performance Plus Program Fault Report Processing Fault Report Handling Fault Priority Response Times FMERF Repair and Replacement Service General Tasks of RuAD 2 Tools Handling of Trouble Reports (TR) Accompanying Documents System Upgrade Hardware/Firmware Updates HW inventory Record Keeping AKUHW TOOLS Overview 3 3 4 6 8 11 13 15 16 16 21 21 25 27 33 35 36 37 38 42 47
A30808-X5226-C559-1-7618
1-1
Siemens
8 8.1 8.2 8.3 8.4
CASINO Customers Advanced Support in Network Operation Introduction Structure of ICN Service Service Operations CASINO Levels, Tasks and Tools
48 48 49 50 54
1-2
A30808-X5226-C559-1-7618
Siemens
7HFKQLFDO $VVLVWDQFH
The objectives of technical assistance is to ensure a high level of system and service availability. TAC is provided on basis of different responsibilities of manufacturer and operating company:
z z z
Taking assigned responsibilities into account Step-by-step support (fallback positions) Provision of problem oriented service.

7$& /HYHOV $FFRUGLQJ WR 6XSSRUW 6HUYLFHV
All services are available on an individual basis. However Siemens has created an innovative line of three standard service portfolios. These three have been designed for a variety of operating budgets and formulated according to the depth and breadth of service required. Taking into consideration the Operators individual requirements, experience and own resources we will work closely with the Operator to determine the perfect service portfolio. The portfolios have been classified as follows:
z z z
lean classic premium. 3UHPLXP &ODVVLF Customer Siemens Siemens /HDQ Customer Customer Siemens
7$& 7$& 7$&
Siemens Siemens Siemens
A30808-X5226-C559-1-7618
1-3
Siemens

7HFKQLFDO $VVLVWDQFH 7DVNV
Safeguard monitor systems and service availability/system performance in different countries.
This applies to the 3 TAC levels but with different emphasis in each case.
Fig. 1

z z z z z z z z
7$& 7DVNV
Provide contact for TAC2 and operating personnel Supporting BSS acceptance Reporting errors and collecting error symptoms Providing system and operating data Initiating and monitoring system modifications (SW/HW/FW) Holding user feedback meetings Supporting and coordinating the O&M Staff Organizing a 24-hour on-call service for exchanges and OMC.
1-4
A30808-X5226-C559-1-7618
Siemens

z z z z z z z z z z z z z
7$& 7DVNV
Supporting and informing TAC1 Recording and completing error messages Locating and initial diagnoses of malfunctions Processing fault reports Supporting cutover and FOA (if required) Providing contact for the TAC3 diagnostic center Verification and release of system modifications (on national basis) Working with the operating statistics in TSC Working with SW/HW/FW inventory Recording user feedback Organizing 24-hour on-call service for TAC1 Operating and testing on test/training systems (optional) Interface to the regional developers (optional).

z z z z z z z z z
7$& 7DVNV
Provide contact for TAC2 Processing fault reports Performing project/product diagnosis Provision and release of system modifications Coordination of projects, providing preventive corrective measures Organizing 24-hour on-call service for TAC2 Evaluating field data/analyzing weak points Create an interface to central system development department Providing diagnostic support.
A30808-X5226-C559-1-7618
1-5
Siemens

7RROV XVHG RQ 7$&
FMERF AUSKAT
STMKAT
AKUHW FEKAT HISTORY
AKUSW
SSG
PATCHdoc
Fig. 2

1-6
A30808-X5226-C559-1-7618
Siemens
available on PC XVHG WR UHFRUG Total/partial outage reports HW/FW inventory record keeping Patch handling History data Fault report processing Defective modules
7RRO PROCONS - AUSKAT PROCONS - AKUHW PROCONS - AKUSW PROCONS - HISTORY PROCONS - FMERF PROCONS - STMKAT
available on MVS 'HVFULSWLRQ Central DB for faults Central DB for patches
7RRO FEKAT SSG
A30808-X5226-C559-1-7618
1-7
Siemens

3HUIRUPDQFH 3OXV 3URJUDP
Once commercial operation has commenced, the next step is for network operators to realize the highest possible return on their investments. This requires a network with optimal capability, availability and performance to make the best possible use of the installed resources. In order to achieve this target we offer our Customers the PerformancePlus program a maintenance program specially developed and designed for system maintenance and network performance during the entire network life cycle. PerformancePlus services are focused on a combination of both proactive and reactive services and strategies to provide full network support during the operating phase of the network. Our extensive range of services are supported by an on-site, regional and central service organization with fallback facilities and predefined escalation strategies to ensure that our services are reliable, consistent and above all, fast. PerformancePlus provides the following support services on a contract basis:
z z z z z z
Emergency Service On-Call Support Fault Report Processing Software/Hardware Update Field Service Repair and Replacement Service.
2SWLRQDO VHUYLFHV (not available for all product lines)

z z
Basic Software Upgrade Bulletin Board.
PerformancePlus has been designed to offer many benefits to Network Operators including:
z z z
increased revenue due to improved network availability and reliability decreased costs due to optimal network support quick solutions to technical problems to ensure that problems do not become crises.
1-8
A30808-X5226-C559-1-7618
Siemens

3HUIRUPDQFH 3OXV 6HUYLFH 3RUWIROLRV
At Siemens, we take a strategic approach, not only to the network planning and implementation phases, but also to the operating phase of the network life cycle. This means that we work closely with our Customers to develop the right PerformancePlus service strategy based on present and future requirements. To aid in this process, we have developed a standard set of PerformancePlus service portfolios. The three service portfolios have been designed with different network requirements, budgets and Operator experience in mind, and are competitively priced to cost less than the same services purchased individually. PerformancePlus service portfolios are thus the easiest and most economical way to keep your network running at a maximum performance. /($1 Designed for the Customer who must adhere to strict budget restrictions, the LEAN portfolio provides solid back-up assistance. The LEAN portfolio of services provides a variety of reliable support services during normal working hours and is intended for Customers who prefer and are able to perform their own first-line maintenance. &/$66,& The CLASSIC service portfolio has been designed for those Customers who are able to carry out first-line maintenance themselves but require the highest level of network support possible. Requiring an optimal extensive array of back-up and support services, CLASSIC Customers will enjoy access to a fully enhanced selection of PerformancePlus services including 24 hour emergency back-up assistance. 35(0,80 Our most comprehensive portfolio of PerformancePlus services, PREMIUM is designed for Customers who are committed to the highest standards of network performance and operation. PREMIUM Customers are typically either following an outsourcing strategy, or simply do not want to carry out first-line maintenance themselves. They require comprehensive service agreements, knowing that they are essential to the success of their business. The PREMIUM service package consists of a full selection of PerformancePlus services, which provide comprehensive on-site maintenance, as well as a complete back-up support.
A30808-X5226-C559-1-7618
1-9
Siemens
6HUYLFH
/($1
&/$66,&
35(0,80
Emergency Service
On-Call Support
Fault Report Processing
SW/HW Update
Field Service
Basic-SW Upgrade *
Bulletin Board
Repair & Replacement Service
Definition and extend are subject of a seperate Repair & Replacement Service agreement
Legend: Carried out (performance data may be different for each portfolio) Optional Services: * Currently this service applies only to products of Mobile Networks
Fig. 3
1-10
A30808-X5226-C559-1-7618
Siemens
)DXOW 5HSRUW 3URFHVVLQJ
If a hardware fault, documentation or software error is identified or suspected, the Customer should inform Fault Report Processing immediately, so that the latter can devise a solution. Depending on the priority of the problem reported, the Customer will receive an expert report, followed by corrective action within a defined period of time. In certain cases, work-around solutions will be provided immediately.
)DXOW UHSRUW FRQVLVW RI DQ HUURU UHSRUW DQG D FXVWRPHU LQIRUPDWLRQ (UURU UHSRUW (5
z z
&XVWRPHU LQIRUPDWLRQ &,

z z
collected in all TSC Forwarded to TSC3 analysis and correction
response written for the originator indicates the status of the error solving
A30808-X5226-C559-1-7618
1-11
Siemens
Fault report
Reported analyzed processed
expert report / CI
correction
Fig. 4

1-12
A30808-X5226-C559-1-7618
Siemens

)DXOW 5HSRUW +DQGOLQJ

A fault report (FR) consists of an error report (ER), which reports the error and a costumer information (CI), which comments the error and announces corrective measures. ER CI FR
Fault location and reporting SW DOC Test and implementation of modification patch source Fault processing analysis correction operator hint HW/FW
Fig. 5
Error Reports are used to document and describe errors
CI
Fehlermeldungerfassung
Fehlerkatalog
analysis Error report
correction
source
patch
HW/FW
Fig. 6
A30808-X5226-C559-1-7618
1-13
Siemens
)DXOW 5HSRUW 3URFHVVLQJ 6HUYLFH operates according to the following procedure: &XVWRPHU If a hardware or software defect is detected or suspected, the Customer informs )DXOW 5HSRUW 3URFHVVLQJ 6HUYLFH using the defined 2Q&DOO 6XSSRUW communication methods and forwards the following data contract number customer name affected system/technology short description of the defect )DXOW 5HSRUW 3URFHVVLQJ 6HUYLFH creates a fault report, collects the available error symptoms and assigns a fault priority in agreement with the Customer. Within the ILUVW FRPPHQWDU\ time, the Customer gets a first response confirming fault report processing and informing them about analysis results already available. If technically possible, )DXOW 5HSRUW 3URFHVVLQJ 6HUYLFH can apply a WHPSRUDU\ ZRUNDURXQG solution. After fault analysis )DXOW 5HSRUW 3URFHVVLQJ 6HUYLFH provides the Customer with a ILQDO FRPPHQWDU\ to the fault report within the final commentary time. This final commentary gives notification of planned correction measure and time. If the reported fault requires correction, )DXOW 5HSRUW 3URFHVVLQJ 6HUYLFH will provide a hardware or software modification within the FRUUHFWLRQ time and implement it in agreement with the Customer. The Customer confirms successful fault correction. )DXOW 5HSRUW 3URFHVVLQJ
1-14
A30808-X5226-C559-1-7618
Siemens

)DXOW 3ULRULW\
)DXOW 5HSRUW 3URFHVVLQJ 6HUYLFH processes the incoming fault reports according to their urgency. For this, each fault report is given one of the following priorities in agreement with the Customer: 3ULRULW\ 1 'HILQLWLRQ Major Fault An urgent software or hardware problem that has escalated to produce considerable operational restrictions. As a result, the fault may cause system availability to be significantly reduced. 2 Minor Fault A software or hardware problem that produces operational and service restrictions, but does not affect the main functions of the system. 3 Impairment a minor software or hardware problem that, while an inconvenience, does not affect system functionality ([DPSOH a fault report that is related to an already neutralized emergency a problem that threatens to escalate to an emergency an important key function of the system is unusable particular features are inoperative a fault report that is related to an urgent problem which could be neutralized by a workaround
errors in documents failure of automatic procedures which can be avoided manually (e.g. auto back-up)
A30808-X5226-C559-1-7618
1-15
Siemens

5HVSRQVH 7LPHV
Due to system complexity, the values for correction time apply to 90% of the fault reports within each priority. If a fault cannot be corrected within the defined period of time, Fault Report Processing Service will in any event provide a correction as soon as possible with all reasonable effort. 3ULRULW\ 1 2 3 )LUVW FRPPHQWDU\&, FXVWRPHU LQIR 2 weeks 1 month 2 month 1 month 3 months next version )LQDO FRUUHFWLRQ

z z z z z z z z
)0(5)
FMERF: Fault report processing Create/edit fault reports supported by plausibility checks Edit commentaries Receive FR from lower service level and send to upper service level Receive status and commentary from upper level and return to lower level Transfer data via EMail or floppy disk FR status and statistics Regional FR database administration FR reporting for all Product lines supported by FEKAT.
1-16
A30808-X5226-C559-1-7618
Siemens
PROCONS DB
FEKAT
receipt and forwarding of FRs via file interface for processing in FEKAT
receipt and distribution of the TSCs costumer information (CI) via file interface
Regional service
checking of FR processing
FMERF
closing of FRs (regional shortcutting)
FR
higher service level
CI
create and edit fault reports (FR) (plausibility checks)
writing and revision of commentaries
statistics
lists
forms
statistics in monthly report format
Fig. 7

A30808-X5226-C559-1-7618
1-17
Siemens

3URFHGXUH RI )DXOW 5HSRUWLQJ
Error reports (ER) are collected in all TSC and are forwarded to TSC3, were they are analyzed and solved. As response, Customer Information(s) (CI) are written telling the status of the error solving. They are returned to the originator of the ER. Until the FR processing is ended, preliminary CI may be written at any time. At least one final CI has to be returned as response to the originator of the ER. The forwarding and returning of the ER and CI between the service levels is shown in the following picture.
)DXOW 5HSRUWLQJ The error reports and the associated customer information are handled in FMERF as described.
1-18
A30808-X5226-C559-1-7618
Siemens
TSC3
TSC2
TSC1
CI on paper
F E K A T M V S ER + CI (TSC3) FMERF ER + CI(TSC3) + CI(TSC2) new error ER (TSC2 + TSC1)

SIEMENS NIXDORF
SIEMENS NIXDORF
ER FMERF ER on paper
ER + CI(TSC3) + CI(TSC2)
SIEMENS NIXDORF
new ER
FMERF ER on paper
Fig. 8

A30808-X5226-C559-1-7618
1-19
Siemens

3ULQFLSDO 6WHSV
2ULJLQDWH (5 76& RU 76& Subject of ER are FRQFHSWLRQDO HUURUV in software, documentation or hardware. Physical defects in HW-modules or repeated system breakdowns must be reported with the PROCONS functions STMKAT respectively AUSKAT. Write only one ER, even when the error occurs repeatedly. )RUZDUG (5 WR 76&
z
If it is an error of priority 1 or 2 you have to start the FMERF transfer function immediately. (If you have no service network connection, you must make printouts of the ER additionally and fax the printouts to TSC3). If it is an error of priority 3, you will start the above transfer regularly (every 14 days) and send the resulting file by floppy or service net.
5HFHLYH (5 IRUP DQRWKHU )0(5) 76&76&

z z
If you have received the ER by FAX: Insert the ER with the error number on the printout into your PROCONS installation If you have received an ER transfer file, load it with "Transfer-In Error Reports (from Subinstallation)".
$QDO\]H (5 LQ 76&
z z
If it is duplicate, or it is no error at all, close it directly in your PROCONS installation with the FMERF function "Process Customer Information" If it is an error, and you can already give explanations or operator hints, you can write a preliminary customer information to be returned to the originator of the ER.
1-20
A30808-X5226-C559-1-7618
Siemens
5HSDLU DQG 5HSODFHPHQW 6HUYLFH
As the market for public telecommunication networks expands, the services offered by ICN Service are becoming increasingly important. As an integral part of the Product Support for the public communication networks sector, we offer a worldwide Repair and Replacement Service (RuAD) tailored to the requirements of the individual network operators. The aim of the RuAD is to perform the services as agreed upon with the operators and in accordance with the requirements of the Quality and Environmental Management (QUM), e.g. to achieve.
z z z
predefined cycle times, especially for modules to be repaired in the country concerned optimized management of spare hardware (modules, equipment,...) cost-effective repair and processing.

3ULQFLSOH
*HQHUDO
The concept of the repair and replacement service (RuAD) is to replace the defective HW. The actual localization of the fault, right up to the component, and repair of the fault, is not performed at the system site but in a repair center. Should a hardware component fail, it has to be replaced with a component from the spare parts pool. This pool is held by the Customer or Siemens (depending on the order). Siemens will ensure that the faulty component is repaired or replaced and returned to the Customer within a pre-defined turnaround time. In exceptional cases, advance replacement is also possible. The objective of the Repair and Replacement Service (RuAD) is to provide users of Siemens Network Systems' products with replacement or repaired components as fast as possible.
A30808-X5226-C559-1-7618
1-21
Siemens
7,3 Only components that can be identified by their part/order numbers can be repaired or exchanged. Ensure all parts are listed on the Order and Dispatch Note form for components equipped with additional modules. Ensure you indicate the OEM part number on the repair report when submitting OEM products/components for repair.1
'HILQLWLRQV
z
5HSDLU Repair means the act of restoring the functional capability of HW at the repair center: e.g. replacing defective components while retaining the as-delivered module status.
0RGLILFDWLRQ The term "modification" applies if a correction has to be made on account of known faults (for example in components). This information can be obtained from the AKUHW (priority-driven modification) and if necessary, from the Functional Level List (FLL).
8SJUDGH Upgrade means the act of adapting a module to a new status so as to obtain additional service features. It involves adaptation of the HW and/or firmware (FW) implemented as a result of the software. In RuAD, upgrading is a special case because it has nothing to do with "repair" in the true sense of the word. An upgrade must therefore be clearly identified when the HW is forwarded to RuAD 3. RuAD 2 is responsible for ensuring that the target status for an upgrade is correct, and this is not checked by RuAD 3. An order for upgrade is generally subject to a charge. Upgrades are not considered in the statistics (no HW trouble report).
FDEOHV DQG DVVHPEO\ PDWHULDOV DUH QRW DYDLODEOH WKURXJK 5X$' DQG FDQ QRW EH UHSDLUHG E\ 5X$' )RU WKHVH LWHPV SOHDVH FRQWDFW WKH DSSURSULDWH VDOHV GHSDUWPHQW
1-22
A30808-X5226-C559-1-7618
Siemens
5X$' 6WUXFWXUH Efficient operation of the Repair and Replacement Service is based on the following organizational structures:
z z z
RuAD 1: Network Operators organization RuAD 2: Regional organization (ICN Service, local Siemens company, Siemens project of licensee or joint venture) RuAD 3: Central organization of Siemens AG (central repair centers).
The main features of the RuAD concept (RuAD 2) in respect of RuAD 1 are:
z
The Network Operator RuAD 1 is supplied directly from RuAD 2 as the permanent regional contact and service partner in the country or contact point for all RuAD transfers to RuAD 3. Independent spare HW (module) store in RuAD 2 and thus reduced cycle time RuAD 1 2 1 for defective/replaced modules Establishment of a regional repair center at RuAD 2 to increase the service capability vis--vis the network operator(s).
z z
A30808-X5226-C559-1-7618
1-23
Siemens
*OREDO 5X$' &RQFHSW
Public Communication Networks RuAD 1

NE NE NE NE NE
Spare HW store
OMC
Spare HW store RuAD 1 center
OMC
Repair center
Spare HW store
Network Operator
RuAD 2
RuAD 2 center Repair center Spare HW store
OEN-Service, Siemens Company outside Germany, Licensee, Joint-Venture

RuAD 2 of other countries
RuAD 2 of other countries
RuAD 3
Spare HW store Repair center
Fig. 9

1-24
A30808-X5226-C559-1-7618
Siemens

z z z z z z z z z
7DVNV RI 5X$'
Following tasks are to be handled at RuAD 2 processing office: Receipt of defective HW from RuAD1 and preparation of a trouble report Identifying, preparing and shipping the replacement HW to RuAD 1 in accordance with the service contract Deciding how the defective HW is to be processed Commercial processing of the defective HW Packaging and shipping of the defective HW for repair Receipt of the repaired HW from the repair center and recording the results of the repair Inventory administration for the spare HW store (e.g. using AKUHW) Monthly feedback of trouble reports to (TR) TSC 3 for operational statistics Monitoring cycle times.
A30808-X5226-C559-1-7618
1-25
Siemens
RuAD 1 PR/TR DN Y UPGRADE ? N Delivery documents
AKUHW
Regional upgrade ? N
Regional repair UPGRADE repair/modification Test Y Regional repair ? N DISPATCH prepare delivered documents Upgrade of inventory of the network operator* SHW withdrawal * via AKUHW
AKUHW
Clarify / start special action RuAD 2
SHW available ?
SHW store FLL Forward to RuAD 3 via AKUHW +FLL
Customs Forwarding agent Dispatch
Upgrade inventory Put HW in store
PR/DN
Delivery documents
RuAD 3
DN FLL RR SHW TR
Fig. 10
Dispatch Note Functional Level List Repair Report Spare Hardware Trouble Report
1-26
A30808-X5226-C559-1-7618
Siemens

7RROV
The software tools AKUHW and PROCONS are provided by OEN Service as part of the service toolset to support the tasks that are handled in RuAD 2. Functions relevant to RuAD are: in AKUHW:
z z z z
inventory administration of the HW used by the Network Operator determining compatible HW administration of the HW store priority-controlled modification data.
in PROCONS:
z z
recording and transfer of HW trouble reports and repair reports (STMKAT) preparation, administration and tracking of RuAD deliveries (RUADMAN).
A30808-X5226-C559-1-7618
1-27
Siemens
PROCONS
STMKAT
RuAD AKUHW
Fig. 11

1-28
A30808-X5226-C559-1-7618
Siemens

z z z z z z z z z
670.$7
Create and edit HW-trouble reports (TR) supported by comfortable plausibility checks; Barcode reader for HW module entry Allow all PL, OEM Modules Supplement data about the repair results (RR) (general result BSL, fault catalog) TSC 3: import RR from repair center/ BSL (Bruchsal) Receive and send TR and RR via EMail of floppy disk Overview lists by various selection and sorting criterias Basis for RuAD management and repair statistics with EVOS Basis for HW-reliability evaluation with EVOS Import RR from repair center via file interface (TSC3 only, separate programs).
A30808-X5226-C559-1-7618
1-29
Siemens
recording of HW trouble and repair reports lower service level higher service level
create and edit HW trouble reports
STMKAT
Barcode reader for HW module entry
forwarding of HW trouble and repair reports to next service level upward via file interface
receipt of HW trouble and repair reports from lower service levels via file interface
lists
Outfile
Fig. 12

1-30
A30808-X5226-C559-1-7618
Siemens

z
5X$' 0DQDJHPHQW
support the sending and receiving RuAD deliveries (defective/replacement modules) used in relation to STMKAT administrate the RuAD activities control the procedure by statistics and lists
z z z
A30808-X5226-C559-1-7618
1-31
Siemens
3URFHGXUH RI 58$'0$1
5X$' 6HQG GHIHFWLYHPRGXOH 5X$' 5HFHLYH GHIHFWLYHPRGXOH 6HQG GHIHFWLYHPRGXOH 5HFHLYH UHSODFHPHQWPRGXOH 5HFHLYH UHSODFHPHQWPRGXOH 5HFHLYH GHIHFWLYHPRGXOH 6HQG UHSODFHPHQWPRGXOH 5X$'
6HQG UHSODFHPHQWPRGXOH
Fig. 13

1-32
A30808-X5226-C559-1-7618
Siemens
+DQGOLQJ RI 7URXEOH 5HSRUWV 75
The trouble report (in full) is prepared as a form by RuAD 1 and passed on to RuAD 2. The contents of the form are transferred at the RuAD 2 center to the PC tool PROCONS with the STMKAT printout is enclosed with the defective HW. A description of this form is included in the user manual PROCONS, register STMKAT: Each report is assigned a 6-digit STMKAT number; this serves as an unambiguous reference (also for RuAD 3). In the regional repair center the repair results are completed with STMKAT. The trouble reports must be sent to TSC 3 for modifying the record statistics. In the event of central repair in RuAD 3, the repair results are forwarded via a data interface from RuAD 3 TSC 3. It must be ensured that the trouble report is already present when the repair report is received at TSC 3 (the transfer files form STMKAT must be forwarded immediately!). This case concerns repair at the central Repair Center (RuAD 3) only.
A30808-X5226-C559-1-7618
1-33
Siemens
repaired replaced HW RuAD 1: network operator defective HW RuAD 2: trouble reports RuAD 3: HW statistics
repaired/replaced HW
Repair data as a file
RuAD 3: result of repair defective HW and trouble report form and voder and dispatch note
Fig. 14

1-34
A30808-X5226-C559-1-7618
Siemens

$FFRPSDQ\LQJ 'RFXPHQWV
Include the requisite accompanying documents, filled out completely and legibly, to ensure expedient exchange and repair services:

7URXEOH 5HSRUW
A trouble report with a detailed description of the fault must be enclosed with each defective hardware unit. The STMKAT number must be recorded on the trouble report. This number links trouble report to the field data and repair results.

5HSDLU 5HSRUW
When a trouble report is to be created an empty repair form is generated in order to be manually filled at the repair center. A repair report must be filled out for every component, regardless to which facility it is sent, and returned with the component. The specific repair number on the repair report must be entered on the Order and Dispatch Note under the heading "Repair Report No." This is a reference number so the customer can later trace the module. It also ensures that the item is easily and quickly identifiable and expedites further processing by RuAD. The repair report is also used to identify problem areas, i.e. if specific components have a history of defects.

2UGHU DQG 'LVSDWFK 1RWH
For the sake of customs formalities to avoid incorrect deliveries, the "repair order/ dispatch note" can be filled out and faxed to RuAD 3 as advance notification of defective hardware. 7,3 Ensure you indicate if the item has warranty coverage. If it does, the contract number for the project where this component is in use must also be indicated.
A30808-X5226-C559-1-7618
1-35
Siemens
6\VWHP 8SJUDGH
System Upgrade is the conversion of an in-service exchange to a new system version in order to incorporate new or additional features. The central service organization provides upgrade procedures to support the customer in carrying out system upgrades. These upgrade procedures define a fast and safe method of incorporating
z z z
hardware firmware software.
modifications needed to operate the new system software. To enable system upgrades to be performed at regional level, the upgrade procedures must be
z z z z
simple to handle, to prevent operator errors easily adapted to the specific requirements of a national network capable of being carried out with a minimum of interruption to service and with the least possible effect of system availability supported by automatic methods.
For each upgrade a special upgrade manual is released. For upgrade of BSS and OMC-B the Siemens number of the document is: A30808-X3247-Z9XX-........-7618
1-36
A30808-X5226-C559-1-7618
Siemens
+DUGZDUH)LUPZDUH 8SGDWHV
$.8+:
+:): &RQILJXUDWLRQ 0DQDJHU
Inventory record keeping
Modification service
([FKDQJH %DVLV 'DWD ,QYHQWRU\
+LVWRU\ &RPSDULVRQ UXQ )//
PROJECT data
PRODUCT data
Fig. 15
A30808-X5226-C559-1-7618
1-37
Siemens
3URMHFW DQG 3URGXFW GDWD FRPSRQHQWV Product data

z z z
History: Functional Level List: SW Control Files:
Title of modules, reasons and explanation of modification List of compatibilities in accordance with different SW Version (APS) in use Files used for function "comparison run"
Project data
z z
Exchange Basis Data: Inventory:
header information of exchanges contents of exchange e.g. Rack, field, modules

+: LQYHQWRU\ 5HFRUG .HHSLQJ
The aim of inventory record keeping is to support planning and service activities by supplying up-to-date hardware/firmware data. Knowledge of what hardware and firmware is installed is essential when carrying out improvements to the system:
z z
expanding the system (either as upgrade, with new features, or as expansion, with added line units) detect and correct faults in the system.
1-38
A30808-X5226-C559-1-7618
Siemens
,PSRUWDQW ,WHPV RI ,QIRUPDWLRQ
3K\VLFDO LGHQWLILFDWLRQ
z
country code (CC) customer code (CUC) exchange code (EC) e.g. 040-1-001
rack location number (RLOCNO) e.g. 040203 field number (FIELD) e.g. 03A043
)XQFWLRQDO LGHQWLILFDWLRQ
z
Siemens Code number including 4 blocks: Construction Function Variation Issue
)RU H[DPSOH
S30810-Q1364-X101-4
X100-1
IIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII
Fig. 16
A30808-X5226-C559-1-7618
1-39
Siemens

3URMHFW 'DWD DQG 3URGXFW 'DWD
([FKDQJH %DVLV 'DWD

z
address data: country name; code customer name; code exchange/NE name; code Exchange characteristics: exchange/NE ID number status worksorder number types of functional units installation type number of ports warranty date etc.
,QYHQWRU\ 'DWD
z z z z
physical identification functional identification modification issue modification acknowledgment etc.
3URGXFW 'DWD
z z z z z
assures the HW/FW functionality and quality of service of exchanges flexible adaptation of the system to customer requirements and to technical innovations plannability of modification activities, e.g. for system upgrades fast response to problems, by checking the HW/FW status determine, coordinate all required HW/FW modifications in an exchange: new features (system upgrade) functional improvements addition line units fault clearance
1-40
A30808-X5226-C559-1-7618
Siemens
$.8+: 3URFHVV 2YHUYLHZ
Planning data (BERADE) Input of data Delivery data (FABDAT)
Exchange Basis Data
Inventory
= Project data
AKUHW
History
History + Functional Level List + Software-control of file Inventory documentation = Product data
Inventory corrections
Inventory "check"
Fig. 17
A30808-X5226-C559-1-7618
1-41
Siemens

z z z z z z z z
$.8+:
+:&RQILJXUDWLRQ 0DQDJHU HW/FW configuration Database administration at all TSC levels and OMC Inventory record keeping for all NE Administration of spare part pools Check and control of compatibility of HW/FW to SW versions Overview lists on NE basis and inventory data with various selection criteria Functional level list Exchange data with other AKUHW installations and PROCONS Supply Product data.
1-42
A30808-X5226-C559-1-7618
Siemens
IDEULFDWLRQ GDWDEDVH
RWKHU $.8+: LQVWDOODWLRQV
3ODQQLQJ GDWDEDVH
352&216
%$5&2'( /$%(/6
68%6<67(06
RYHUYLHZOLVWV RQ1(EDVLV DQGLQYHQWRU\ GDWD
20FHQWHU (;&+%$6,6 ,19(1725< 352'8&7'$7$
IXQFWLRQOHYHO 1( DGPLQLVWUDWLRQ
$.8+:
SURGXFWGDWD PDQDJHPHQW
OLVWV
6SDUHPRGXOH
FKHFNDQGFRQWURO RI+:):WR6: YHUVLRQV RIH[FKDQJH
FRQWURORI UHTXHVWHG +:): PRGLILFDWLRQ
LQYHQWRU\UHFRUG NHHSLQJIRUDOO1( UHODWHGEDVLVDQG FRQILJXUDWLRQGDWD
PRGLILFDWLRQ RUGHUOLVWV
Fig. 18

A30808-X5226-C559-1-7618
1-43
Siemens

&RPSDULVRQ 5XQ
The function "comparison run" is used or an automatically evaluation of HW/FW modifications according to SW version. The evaluation is made country-, customeror exchange-wide. when?
z z
before installation or system upgrade after priority 0.
Output files
z z z
protocol modification notice modification acknowledged.
$FWLYLWLHV
z z z z z
Inventory check update of inventory data file start evaluation analyze the output result react according to planned activities.
1-44
A30808-X5226-C559-1-7618
Siemens
Comparison run
modification message run
calculation run
output files and all results will be stored on database
output files but no registration on database
Fig. 19

A30808-X5226-C559-1-7618
1-45
Siemens

3ULRULW\ 0
3ULRULW\ 3ODFLQJ
5HDVRQ
z z z z z
Priority = priority of modification ,PSOHPHQWDWLRQ PXVW implementation (immediately)
acute danger of loss of billing acute danger of total break down acute danger of partial break down acute danger of emergency call out of order administration not possible APS-dependent failure improvement of system performance non critical defected component correction of documentation new manufacture
z z
ZLOO implementation (for exchange activities) PXVW implementation (for system upgrade) in case of reparation no action taken
2 3
z z z
1-46
A30808-X5226-C559-1-7618
Siemens

7$6.6
722/6 2YHUYLHZ
722/6 AUSKAT STMKAT HISTORY 5HPDUNV
Diagnostic support
HW/FW Inventory record keeping HW/FW Updates Project data administration Repair and return procedures
AKUHW AKUHW AKUHW STMKAT AKUHW RUADMAN AKUSW (SSG) AKUSW (SSG) FMERF (FEKAT) AUSKAT STMKAT
SW Inventory record keeping SW Updates Trouble reports processing
Upgrade
AKUSW / AKUHW
A30808-X5226-C559-1-7618
1-47
Siemens

&$6,12 &XVWRPHUV $GYDQFHG 6XSSRUW LQ 1HWZRUN 2SHUDWLRQ

,QWURGXFWLRQ
Until now service tool PROCONS (Product Support Control System), a part of the Service Tool Set, has been used for handling After Sales Service in the local service centers. The completely new designed service tool CASINO will replace in future PROCONS. CASINO is intended to provide the local service centers with a higher level of support for dealing with after-sales service than was previously the case. The service and quality-oriented processing of the services included in the Performance Plus product, such as On-Call Support, Software Update, Fault Report Processing and Repair and Replacement are supported by CASINO through a series of integrated functions and by tailored electronic interfaces to the central and local ICN S partner procedures. Thus, for example, for service process On-Call support, CASINO provides an integrated Call Handling System with the option of immediate service contract checking and automatic scheduling, routing, workflow and expenditure recording. In addition CASINO provides functions for collection of operational data, operating statistics and for SW inventory management. An integrated transfer management function allows automation of the electronic communication between CASINO and the partner process or customer.
1-48
A30808-X5226-C559-1-7618
Siemens

6WUXFWXUH RI ,&1 6HUYLFH
The structure of ICN service can be roughly seen as operating on three levels. The relevant organizational units there are in the further addressed as 7HFKQLFDO 6HUYLFH &HQWHUV 76& By that we dont anticipate the actual existence of an organization with that name but rather intend to have a technical term to identify the work units where the according activities are pursued. Each TSC has its own competence and responsibilities. Being aware of the fact that there exist a wide spectrum of local variations on that subject the most commonly case can be described as following: 76& LV operating very close to the customer, if not the customer himself, typically an 2peration and 0aintenance &enter (20&). This is the place where the trouble is originally found and has to be finally solved. 76& plays its RQH IDFH WR WKH FXVWRPHU role by
z z
Collecting all problems and queries coming up from 76& Providing the measures, answers and solutions to the customers satisfaction
In order to do this job 76& UHOLHV also, next to its own competence, on the support of TSC3. In any case it plays the central role in the processing and takes care for the proper documentation of all actions. 76& LV at Siemens in Munich or at one of the other emerging big continental development and support centers. Here product faults are being investigated in the according development departments. Reaction queries, temporary solutions, patches and updates are sent back to 76& level. Next to problem support, the collection of statistical data from worldwide installations is an important task of 76& Good statistics is essential for reliable quality monitoring and efficient direction of improvement activities.
A30808-X5226-C559-1-7618
1-49
Siemens

6HUYLFH 2SHUDWLRQV
&$6,12 has been designed to efficiently support the daily routine in a 76& organization. That means it provides all documentation and communication facilities necessary to obsolete the deployment of additional tools for problem tracking and administration. The core functionality of CASINO are the so called 6ervice 2perations (62), each of them being a collection of both general and (SO-) specific tasks for data collection, data transfer to and from the other TSC levels and documentation of taken measures. The following SOs are handled by CASINO: 2SHUDWLRQDO 3UREOHP +DQGOLQJ OP
z
any kind of problem can be tracked here
)DXOW 5HSRUW +DQGOLQJ FR Featuring an automatic interface to )(.$7 9 5HSDLU DQG 5HSODFHPHQW 6HUYLFH R&R
z
with integrated trouble reporting, module tracking and repair documentation
6RIWZDUH 8SGDWH 6HUYLFH SUS

z
supports provision by TSC3 staff and different types of update packs
7HFKQLFDO 4XHU\ 3URFHVVLQJ TQ

z
featuring an automatic interface to TSC3 +(/3'(6. $QDO\VLV OU
2XWDJH 5HSRUWLQJ
z
featuring an automatic interface to TSC3 Service Quality Monitoring
To facilitate the data exchange with the other TSC levels a powerful and configurable Transfer Management (7)) has been incorporated. It handles all sorts of different data and communication media and provides automatic destination selection. Once configured, a simple "button push" initiates transfer. Base Data Maintenance (%'0) comprises the dialog access to the project specific base data objects.
1-50
A30808-X5226-C559-1-7618
Siemens
%'0 %DVH'DWD 0DLQWHQDQFH 686 6RIWZDUH 8SGDWH6HUYLFH 665 6HUYLFH 6\VWHP 5HSRUWLQJ
23 2SHUDWLRQDO 3UREOHP +DQGOLQJ
)5 )DXOW5HSRUW 3URFHVVLQJ 74 7HFKQLFDO4XHU\ 3URFHVVLQJ 55 5HSDLU 5HSODFHPHQW 6HUYLFH
&$6,12 '%
28 2XWDJH 5HSRUWLQJ $QDO\VLV
Fig. 20 Service Operations
A30808-X5226-C559-1-7618
1-51
Siemens
2SHUDWLRQDO 3UREOHP +DQGOLQJ 23 Provides the basic handling of all locally manageable or initially not further classifiable problems. Any number of local attempts (measures) to solve the problem and their respective success/failure at the customers premises is documented. In case of non-explainable or sporadic behavior the OP case can be set in observation mode and related to other cases showing a similar pattern. )DXOW 5HSRUW 3URFHVVLQJ )5 Supports the standard service procedure FR Processing and offers multiple and parallel exchange of information from and to the customer, i.e.:
z z z z
Receive all comments from TSC3. Send the customers or TSC2 operators comments to TSC3. Enter customer's reaction to the proposed solution. Integrates transfer of symptom files to the TSC3 symptom files server
7HFKQLFDO 4XHU\ 74 Like with FR processing information can flow in both ways, based on automated (email) data exchange. 5HSDLU DQG 5HSODFHPHQW 6HUYLFH 5 5 Its task is keeping track of faulty HW-modules and exchange units. The repair cycle of faulty units sent in by the customer is followed from their initial receipt over send and return to and from the according repair center back to the customer or the TSC2 pool. Modules are assigned to outgoing and identified in incoming delivery packs administrated by the CASINO user. Next to standard delivery and repair sheets also a trouble report is automatically generated and sent to TSC3 level to allow for quality controlling measures there.
z z z z z z z z z z z
The following tasks can be performed: Register the receipt or occurrence of defective HW objects Track the delivery of a replacement item to the customer Track the repair of the defective object at the repair center Store serial number and warranty date per HW object Make quality statistics on the HW Objects (HW TOPTEN) Follow-up turnaround times and delayed objects Document repair results, if available Support individual project configurations, as local repair centers Print HW trouble reports for sending to the repair center Automized reporting HW troubles to the TSC3 statistics department
1-52
A30808-X5226-C559-1-7618
Siemens
6RIWZDUH 8SGDWH 6HUYLFH 686 Correction sets for a specific software system can be imported and their (automatic) distribution to customers controlled by CASINO. CASINO can automatically detect the receipt of such a package and generate an according service case. Special support is available for the handling of corrections (patchsets). 2XWDJH 5HSRUW DQG $QDO\VLV 28 Mark problems, e.g. OPs, having caused system unavailability as outages that have to be analyzed by TSC3 and should figure in the SW availability statistics. Automized sending of outage reports to TSC3 statistics department. Partial or complete outages of a customer's equipment can be recorded together with the available results of an analysis. Outage data feed local monitoring functions of CASINO (e.g. total outage time per customer, mean time to restore operation) and, as outages are (automatically) reported to TSC3, supports the generation of global performance statistics.
A30808-X5226-C559-1-7618
1-53
Siemens

&$6,12 /HYHOV 7DVNV DQG 7RROV
The CASINO tool will be used for recording outage reports, hardware fault reports and software fault reports. The inventory data will continue to be recorded in the "AKUHW" tool. 6\VWHP RXWDJHV 6\VWHP DYDLODELOLW\ RXWDJH UHSRUWV The enclosed service reports are the basis for evaluating the system outages. System outages (partial and total) are recorded using the CASINO tool. Where possible, the outages should be processed immediately after they occur and included in CASINO. After entry the reports should be sent without delay (via the integrated email function) to TSC 3 where they are stored in the CASINO database or used to evaluate statistics. 'HIHFWLYH +: PRGXOHV +DUGZDUH UHOLDELOLW\ WURXEOH UHSRUWV In addition to system outage reports, the reports (fault reports) about all hardware module faults are also needed to ensure hardware availability. These will also be recorded using the CASINO tool. After entry the reports should be sent without delay (via the integrated e-mail function) to TSC 3 where they are stored in the CASINO database or used to evaluate statistics. 6: IDXOWV HUURU UHSRUWV Software faults will also be recorded with the CASINO tool. After entry the reports should be sent without delay (via the integrated e-mail function) to TSC 3 where they will be stored in the FEKAT-database or further processed.
1-54
A30808-X5226-C559-1-7618
Siemens
TSC3: Development & Support
,QYHQWRU\ $ .8 +: 6$ 0621
TSC3: Repair & Replacement Center
&$6,1276& &$6,12 :RUOG )0 )(.$7 +HOS 'HVN
0RGXOH 7UDFNLQJ
Long card
+:0RGXOH
&$6,12 '%
,QY HQWRU\ $ .8+: 6$ 0621
6:0DQDJHU
+:0RGXOH
76&6XSHUYLVRU &DOO5HFHSWLRQ
TSC2: Local Service Center
550DQDJHU
&)( &$6,12 &XVWRPHU )URQWHQG +:0RGXOH
TSC1: The Customer
Fig. 21 TSC Levels, Tasks and Tools
A30808-X5226-C559-1-7618
1-55
Siemens
Page intentionally left blank.
1-56
A30808-X5226-C559-1-7618
ISO-OSI Model and Protocols
Siemens
,6226, 0RGHO DQG 3URWRFROV
&RQWHQWV
1 2 3 ISO-OSI Layered Model Protocol Types in the GSM- and GPRS-PLMN Exercises 3 11 17
A30808-X5226-C559-1-7618
2-1
Siemens
2-2
A30808-X5226-C559-1-7618
Siemens
,6226, /D\HUHG 0RGHO
The OSI reference model was established in 1983 as ISO Standard 7498. It subdivides the communication procedure into 7 functionally different elements which are normally shown as layers lying on top of one another; hence the name "layer model". To prevent a "Babel of languages the ,62 ,QWHUQDWLRQDO 6WDQGDUGL]DWLRQ 2UJDQL]DWLRQ) developed a model for open, standardized communication - the 26, UHIHUHQFH PRGHO 5HIHUHQFH 0RGHO RI 2SHQ 6\VWHP ,QWHUFRQQHFWLRQ). An "open system is a communication system for which certain interfaces are defined and to which equipment from a wide range of manufacturers can be connected as long as it meets these interface requirements. 26, SULQFLSOH The 7 layers of the OSI layered model are set up logically; the functions from a lower layer are the prerequisite for the functions of an upper layer. Each upper layer of subscriber A can only communicate with its partner layer in the exchange or at subscriber B if it takes advantage of the services from the layers below. The functions in each layer are realized with certain automatic hardware and software components. A layer can comprise several independent function units to fulfill its functions. To coordinate these many functions (tasks, procedure) the layers can be divided into "sublayers".
A30808-X5226-C559-1-7618
2-3
Siemens
User entity
Network
User entity
Layer 7 6 5 4 3 2 1 Application Presentation Session Transport Network Data Link Physical Connection

Layer
Applicationoriented protocols
7 6 5 4 3 2 1
Transportoriented protocols
Transmission channel
Fig. 1 OSI reference model according to ISO 7498

Network access protocols
End-to-end protocols

2-4
A30808-X5226-C559-1-7618
Siemens
1DPH DQG IXQFWLRQ RI WKH OD\HUV RI WKH 26, PRGHO An explanation of the OSI model is usually very unclear without concrete application. The 7 layers with function examples are only outlined briefly below. The next chapters will provide an overview of OSI model adaptation to the GSM concept as well as the use of layer 1, layer 2 and 3 in this concept in detail. /D\HU GHVLJQDWLRQ 7 6 Application layer Presentation layer 'HVFULSWLRQ H[DPSOHV Application programs and services which monitor the procedure. Presentation of the information; adaptation to the information system; the character set, for example, is set here. Controls communication between 2 application processes end-to-end; ensures organization and synchronization of the dialog and the handling of data exchange (e.g.: transmission authorization,...) Creates an end-to-end connection between 2 systems and provides various functions for this. Determines the whole physical transmission path of the communication connection; ensures for routing, and flow control, for example. Determines protected transmission on a partial route of the transmission path; is responsible for problem detection and repair. Describes the necessary mechanical, electrical and functional properties and procedure aids for signal transmission.
Session layer
4 3
Transport layer Network layer
Link layer
Physical layer
Layers of the OSI model
A30808-X5226-C559-1-7618
2-5
Siemens
$QDORJ\ RI WKH 26, PRGHO

England Germany
Makes a request to a german Manager
/D\HU
$SSOLFDWLRQ /D\HU 3UHVHQWDWLRQ /D\HU
Works on the request
Manager
Manager
Rewrites the request into 2 message parts Reads the message parts and informs the manager about the contents
/D\HU
Secretary
Secretary
Puts the 2 message parts into 2 different envelopes
UP
/D\HU
6HVVLRQ /D\HU
Removes the message parts from the envelopes and collects it with the right order
Mail
Mail
Determines the way and media for transport and attaches a delivery note of the whole delivery
/D\HU
7UDQVSRUW /D\HU
Checks the received information for correctness according to the delivery note
Transport Manager
Transport Manager
/D\HU
5R\DO 0DLO
Royal Mail
Selection of means of transport according to the informations on the envelopes
1HWZRUN /D\HU
Selection of means of transport according to the informations on the envelopes
3
German Mail
/D\HU
9
Inspection
Checks the mail on each check point, weather nothing was stolen, damaged or got lost
/LQN /D\HU
Checks the mail on each check point, weather nothing was stolen, damaged or got lost
9
Inspection
MTP
/D\HU
3K\VLFDO /D\HU
Royal Mail British Rail British Airways German Rail
3
German Mail
Fig. 2
2-6
A30808-X5226-C559-1-7618
Siemens
Only circuit-related applications existed when the architecture model for CCS7 was specified. The resultant model comprised levels (CCITT / ITU Recommendation Q.701). Some time after this structure was specified, the International Standards Organization (ISO) specified the -layer Open Systems Interconnection Model (OSI model). The OSI model comprises OD\HUV, whereas the CCS7 model has merely OHYHOV. The correlation and mapping between the two models will be examined more closely later in this description. The CCS7 signaling system has meanwhile been extended to include non circuitrelated applications. The original OHYHO model is not suitable for such applications, however, meaning both models are now used for CCS7. In other words: some applications use the 4-level model, while others use the 7-layer model.
/HYHO 0RGHO The 4-level model can be used in national and international networks. It is very flexible, supports a large number of applications and performance features, and has been optimized for usage in a digital environment.
A30808-X5226-C559-1-7618
2-7
Siemens
ISDN-UP, Level 4
DATA-UP, Level 4
TUP, Level 4
Examples of user parts
Signaling network functions, level 3
Signaling link functions, level 2
Message transfer part (MTP)
Physical and electrical attributes, level 1
Fig. 3 CCS7 levels
2-8
A30808-X5226-C559-1-7618
Siemens
/HYHO Level 1 (signaling data link) defines the physical, electrical and functional attributes of a signaling data link as well as the access equipment. The incorporation of these attributes in Level 1 has the major advantage of making the Levels 2-4 independent of the transmission medium. Level 1 represents the carrier for a signaling link. Normally, 64-kbit/s channels are used as signaling data links in a digital network. Alternatively, analog channels (preferably with bit rate 4.8 kbit/s) can be used via modem as signaling data link. /HYHO Level 2 (signaling link) defines the function and procedure for error-free signaling message exchange between two adjacent signaling points via a signaling link. This definition includes the control of signaling links in the event of a failure, and the monitoring of signaling links. The Level-2 functions can be optimized separately without an automatic adaption requirement for the adjacent Levels 1 and 3. However, this rule applies only if no modification of the interfaces takes place. /HYHO Level 3 (signaling network) defines functions that are valid for several signaling links. A distinction is made between the following two functional groups:
z z
message handling, i.e. directing messages to the required signaling link or, as applicable, to the correct user part. signaling network management, i.e. controlling message traffic by measures such as changeover of signaling links in the case of a failure and restoring normal operation following repair.
The various Level-3 functions can inter operate with each other, with functions belonging to other levels, and with the equivalent functions in other signaling points.
A30808-X5226-C559-1-7618
2-9
Siemens
/HYHO Level 4 contains the User Part (UP). The UP defines the message format as well as the functional procedures for specific applications (e.g. call setup for an ISDN user part call). Level 4 therefore includes call control functions. All Level-4 user parts can use Levels 1-3 as a standardized option for error-free message transfer. CCITT / ITU have so far defined the following user parts:
z z z
Data User Part (DUP) Telephone User Part (TUP) and ISDN User Part (ISUP).
Should these specified user parts prove inadequate for future requirements, or if new user parts become necessary, it will easily be possible to adapt the existing user parts or specify new ones as long as the lower levels are not influenced.
2-10
A30808-X5226-C559-1-7618
Siemens
3URWRFRO 7\SHV LQ WKH *60 DQG *356 3/01
The following diagrams provide an overview of the most important protocols used in the GSM-PLMN and in the GPRS-PLMN. More details on the use or realization of the individual layers in the GSM-PLMN are given in the following chapters. The central signaling system CCS7 (Common Channel Signaling System No.7) is used in the GSM system for signaling between all components of the SSS, between the MSC and BSC as well as signaling to external networks such as ISDN. It comprises 4 levels, the lower 3 of which are summarized in the message transfer part (= MTP) and the 4th level which contains different user parts. The air interface Um is subdivided into 3 layers:
z z z
Layer 1 is a physical bi-directional point to point connection, Layer 2 contains the LAPDm protocol, Layer 3 consists of Radio Resource Management (RR), Mobility Management (MM) and Connection Management (CM).
The Abis interface also consists of 3 layers:

z z z
Layer 1, the physical layer, the LAPD protocol as layer 2. Layer 3 comprises the Radio Signaling Link (RSL), Operation and Maintenance messages (O&M) and Layer 2 Management Link messages (L2ML).
A30808-X5226-C559-1-7618
2-11
Siemens
CC SS SMS CM MM RR LAPDm L1
HLR
AC
VLR
EIR
MAP TCAP RSL O&M L2ML LAPD L1 SCCP MTP CCS7 CCS7 BSC CCS7 MSC ISDN ISUP SCCP MTP
BTS
OMC-B
DT AP
BSS MAP
OMC-S
BSSAP SCCP MTP
BSSAP BSSMAP CC CM DTAP ISUP L1 L2 L2ML MAP LAPD
Base Station System Application Part Base Station System Management Part Call Control Connection Management Direct Transfer Application Part ISDN User Part Layer 1 Layer 2 Layer 2 Management Link Mobile Application Part Link Access Protocol for the D channel
MM MTP O&M RR RSL SCCP SMS SS TCAP RSL
Mobility Management Message Transfer Part Operation and Maintenance Radio Resource Management Radio Signaling Link Signaling Connection Control Part Short Message Service Support Supplementary Services Support Transaction Capabilities Part Radio Signaling Link
Fig. 4 Overview of the signaling in the GSM-PLMN
2-12
A30808-X5226-C559-1-7618
Siemens
Signaling & Datatransfer Signaling
606*06& 606,:06&
E C
SM-SC
*G 06&9/5
A D
+/5*5 *Q *F
**61
*V %66 *Q *E
6*61
*U
06
Um
*L
3'1
TE
6*61 GGSN
other
*S 3/01
*I
(,5
Fig. 5 Interfaces of the GPRS-PLMN
A30808-X5226-C559-1-7618
2-13
Siemens
$SSOLFDWLRQ ,3; 61'&3 //& 5/& 0$& *605)

06
8P
61'&3 5HOD\ //& %66*3 )5 / bis

*E
5HOD\
,3; *73 8'3 7&3 ,3 / /

*Q
*73 8'3 7&3 ,3 / /

**61
*L
5/& 0$&
%66*3 )5 / bis
6*61
*605)
%66
SNDCP : SubNetwork Dependent Convergence Protocol LLC: Logical Link Control RLC: Radio Link Control BSSGP: BSS GPRS Protocol MAC: Medium Access Control FR: Frame Relay
GTP: GPRS Tunnelling Protocol UDP : User Datagram Protocol TCP : Transmission Control Protocol IP: Internet Protocol
Fig. 6 Protocols used in the GPRS-PLMN on the GPRS transmission plane
2-14
A30808-X5226-C559-1-7618
Siemens
*356 0RELOLW\ 0DQDJHPHQW 6HVVLRQ 0DQDJHPHQW

//& 5HOD\ 5/& 5/& %66*3
*0060
*356 0RELOLW\ 0DQDJHPHQW 6HVVLRQ 0DQDJHPHQW

//&
*0060
%66*3
0$&
0$&
)5
)5
*60 5)
*60 5)
/ bis
/ bis
06
8P
%66
*E
6*61
Fig. 7 Protocols used in the GPRS-PLMN on the GPRS signaling plane (MS-SGSN)
A30808-X5226-C559-1-7618
2-15
Siemens
0$3
0RELOH $SSOLFDWLRQ 3DUW
0$3
%66$3
%66 $SSOLFDWLRQ 3DUW
%66$3
%66 $SSOLFDWLRQ 3DUW
7&$3
Transaction Capabilities Application Part
7&$3 6&&3
6&&3
Signalling Connction Control Part
6&&3 073 / 073 / / *U IG
Signalling Connction Control Part
6&&3 073 / 073 / / *V
073 / 073 / /
073 / 073 / /
6*61
+/5(,5606*06& +/5
6*61
06&9/5
**61
*F
Fig. 8 Protocols used in the GPRS-PLMN on the GPRS signaling plane
2-16
A30808-X5226-C559-1-7618
Siemens
([HUFLVHV
A30808-X5226-C559-1-7618
2-17
Siemens
([HUFLVH
The ITU-T recommendations and the GSM specifications are very important sources of information. Complete the following tables: ,787 UHFRPPHQGDWLRQV Series A recommendations Series B recommendations Series C recommendations Series D recommendations Series E recommendations Series F recommendations Series G recommendations Series H recommendations Series I recommendations Series J recommendations Series K recommendations Series L recommendations Series M recommendations &RQWHQWV Organization of the work of the ITU-T Means of expression General telecommunication statistics General tariff principles Telephone network and ISDN Non-telephone telecommunication services " Transmission of non- telephone signals Integrated services digital network Transmission of sound-programs and television signals Protection against interference Construction, installation and protection of cables and other elements of outside plant Maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits Maintenance: international sound-programs and television transmission circuits Specification of measurement equipment Telephone transmission quality " Telegraph transmission Telegraph services terminal equipment Terminal equipments and protocols for telematic services Telegraph switching Data communication over the telephone network " Programming languages
Series N recommendations Series O recommendations Series P recommendations Series Q recommendations Series R recommendations Series S recommendations Series T recommendations Series U recommendations Series V recommendations Series X recommendations Series Z recommendations
2-18
A30808-X5226-C559-1-7618
Siemens
*60 VSHFLILFDWLRQV Series 01.yy Series 02.yy Series 03.yy Series 04.yy Series 05.yy Series 06.yy Series 07.yy Series 08.yy Series 09.yy Series 10.yy Series 11.yy Series 12.yy
&RQWHQWV General Service Aspects Network Aspects " " Speech Coding Terminal Adapters for Mobile Stations " Network Interworking Service Interworking Equipment and Type Approval Specifications Network management, Operation and Maintenance aspects
,QIRUPDWLRQ DERXW Air interface, Layer 1 Air interface, Layer 2 Air interface, Layer 3 Abis interface, Layer 1 Abis interface, Layer 2 Abis interface, Layer 3 A interface, Layer 1 Signaling transport mechanism on A interface A interface Layer 3
5HIHUHQFH
A30808-X5226-C559-1-7618
2-19
Siemens
2-20
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
$LU ,QWHUIDFH 8P
&RQWHQWV
1 1.1 1.2 2 3 3.1 3.2 4 4.1 Layer 1 of Air Interface - Um Physics of Layer 1 (Um) Logic of Layer 1 (Um) Layer 2 - Um-Interface Layer 3 - Um Radio Resource- , Mobility- , Connection Management Formatting Rules Call Sequences on Um Complete Sequences 3 5 33 51 58 58 70 75 75
A30808-X5226-C559-1-7618
3-1
Siemens
Air Interface Um
3-2
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
/D\HU RI $LU ,QWHUIDFH 8P
The MS is linked to the fixed PLMN structure via a UDGLR OLQN. The air or radio interface Um describes the radio link function. The MS/BSS interface must ensure: use of the same standard interface by the MS and terminal equipment (TE) use of MSs from different manufacturers in the whole system area of the GSM network connection with terminal equipment using the same identifiers and codes independent of the respective location of the unit The transmission of speech, data and signaling is carried out on the air interface Um via radio channels (RFCs). The RFCs form layer 1 of the GSM system air interface. Layer 1 (Um) is described in *605HF .
A30808-X5226-C559-1-7618
3-3
Siemens
Air Interface Um
Layer 3
CC
SS
SMS
CM
MM
RR
Layer 2
Logik Layer 1 Physik
Fig. 1 Layer 1 - 3 of the air interface Um

3-4
A30808-X5226-C559-1-7618
Air Interface Um
Siemens

3K\VLFV RI /D\HU 8P
Speech and data transmission on the air interface Um is carried out via the physical channels. A physical channel is defined by a specific carrier pair (RFC = Radio Frequency Channel) in the UL and DL and the number of the time slot in the TDMA frame. Layer 1 (physical Layer : GSM 04.04) is a physical bi-directional point to point connection in multiframe mode. Layer 1 communicates with layer 3 directly according to channel management and measurement control. The physical layer will offer layer 2 appropriate channels by usage of the following functions :
z z z
Burst transmission Error correction and -detection Supervision of RSS Link Control
Furthermore the layer 1 protocol defines the mobile stations search for a suitable BCCH and the seizure of DCCH through the MS (after allocation by the base station)
A30808-X5226-C559-1-7618
3-5
Siemens
Air Interface Um
UL
DL
7 6 5 4 3 2 1 RFC 1 RFC 2 RFC 3 0 RFC 174 TDMA
RFC 1
RFC 2
FDMA
Fig. 2 Physical channel in the FDMA and TDMA frame

3-6
A30808-X5226-C559-1-7618
6 4 5
TDMA RFC 3 RFC 174 FDMA
7 6

Air Interface Um
Siemens

7KH 7'0$ )UDPH
A TDMA frame is divided into WLPH VORWV 76. The whole TDMA frame lasts 4.615 ms, an individual time slot 0.577 ms. A physical channel is assigned exactly one time slot TS in the TDMA frame. Each subscriber receives a time slot and sends all 8 time slots1 once. Transmission is not allowed outside the allocated time slots TS (i.e. after the TS has expired) so other physical channels are not exposed to interference.
:LWKIXOOUDWHWUDQVPLVVLRQZLWKKDOIUDWHWUDQVPLVVLRQHYHU\WLPHVORWV+6&6'DQG*356DUHQRW\HWWDNHQLQWR FRQVLGHUDWLRQ
3-7
A30808-X5226-C559-1-7618
Siemens
Air Interface Um
TDMA-frame
0,577 ms 4,615 ms
Fig. 3 Assignment / repeat of a TDMA frame

3-8
A30808-X5226-C559-1-7618
Air Interface Um
Siemens

%XUVW 1RUPDO %XUVW
Sending the information in the individual time slot of 0.577 ms with a permanently defined bit sequence is called a EXUVW. The burst is realized by the MS by switching on, transmitting briefly and switching off the transmitter again.
A30808-X5226-C559-1-7618
3-9
Siemens
Air Interface Um
Power
542,80 s 28 s 28 s
Time
Fig. 4 Time pattern of the resulting transmit power of a burst2
1RWHWKHGXUDWLRQRIDWLPHVORWLVVDFFRUGLQJWRWKHGHILQLWLRQ7KHVHVDUHQRWJLYHQLQGHVFULSWLRQVRIWKH WUDQVPLWSRZHURIDEXUVWDQGRIWHQLUULWDWHUHDGHUVRIOLWHUDWXUHRQ*607KHWLPHGRPDLQRIVVKRZQLQILJDQG FRUUHVSRQGLQJZLWKELWDOVRNQRZQDVdXVHIXOSDUWoLVWKHUDQJHZKHUHWUDQVPLWSRZHULVUHTXLUHGDWDFRQVWDQWSRZHU OHYHODOPRVWDVDLQIRUPDWLRQWUDQVPLVVLRQSODWIRUP7RJHWKHUZLWKWKHWLPHUDQJHVIURPWKHIODQNVLQFUHDVHGHFUHDVHRI SRZHURIDPD[LPXPRIVHDFKWKLVJLYHVVDQGLVWKXVVOLJKWO\ORQJHUWKDQWKHGXUDWLRQRIWKHDFFRPSDQ\LQJWLPH VORW7KHWZRVDUHKRZHYHURQO\WLPHPD[LPXPOLPLWVIRUWKHIODQNVDQGLQWHUIHUHQFHIURPEXUVWRIVXFFHVVLYHWLPHVORWV 7KH\DUHUHOLDEOHZKHQWKHSRZHULVDSSURSULDWHO\ORZVRWKHGXUDWLRQRIWKHWHFKQLFDOO\UHDOL]HGEXUVWFRLQFLGHVZLWKWKH GHILQHGGXUDWLRQRIDWLPHVORWLQWKHVWDSSURDFK
A30808-X5226-C559-1-7618
3-10
Air Interface Um
Siemens
With base stations the dynamic range is 70 dB, with low power (mobile phone: 2.5 W) 36 dB. The set tolerance masks for transmitting a burst from a BTSE are shown in the following diagram.
A30808-X5226-C559-1-7618
3-11
Siemens
Air Interface Um
Power (dB) 4 0,5 0 -0,5
-6
-30
-70
useful part 147 bits
10
10
T0
10 Time (s)
10
Fig. 5 Tolerance masks of the TDMA burst

3-12
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
7LPH VWUXFWXUH RI WKH WLPH IUDPH ELW VHTXHQFH A time slot is defined at a time frame of 577s (to be precise: 576 12/13 s 576.923 s). This time frame is divided into 156.25 bit. This means an individual bit has a duration of 3.6923 s. The 156.25 bits are used as follows:
z z
142 bits for LQIRUPDWLRQ WUDQVPLVVLRQ, 3 bits each as WDLO ELWV (TB) for edge limitation of the time slots. They are also used as protection zones if a neighboring channel happens to interfere with the first or lasts bits. 8.25 bits as a JXDUG SHULRG (GP) (exception: the GP for access burst is 68.25 bits long) for collecting variable run or reception times (determined by the distance BTSE MS).
A30808-X5226-C559-1-7618
3-13
Siemens
Air Interface Um

7%
,QIRUPDWLRQ
7%
*3
Burst
Fig. 6 Breaking down a time slot into bits

3-14
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
5HDOL]DWLRQ RI LQIRUPDWLRQ WUDQVPLVVLRQ LQ WKH EXUVW As a rule 142 bits of information transmission are realized in a burst presented as "1" or "0" as indicated below. They are in the time middle of the burst transmission in the "useful part". The two 3 tail bits (TB) on the edge of the information section provided as security zones are realized as constant transmission of "0". No information is transmitted in the guard period (GP). There are 5 different types of burst
z z z z z
Normal burst Frequency correction burst Synchronization burst Access burst Dummy burst
Each of these bursts has a different configuration and has a particular purpose. 7KH QRUPDO EXUVW It contains
z z z
2 x 3 bits as tail bits (7%); 2 x 57 HQFU\SWHG GDWD ELWV which carry the actual information 2 x 1 bit as a "VWHDOLQJ IODJ" which tell the receiver that data transmission is being interrupted briefly and signaling data is being transmitted instead of useful data (or vice versa). 26 bits for synchronizing and problem detection (WUDLQLQJ VHTXHQFH) which allow both the BS and the MS to synchronize themselves to a burst and allocate the data bits exactly. Distorted or incomplete received signals can thus be reconstructed.
Now that the contents of the most important burst has been described down to the bit level, how information transmission is realized at the level of individual bits in the burst now has to be described. This means: How is the "0" or "1" presented exactly on the radio path?
A30808-X5226-C559-1-7618
3-15
Siemens
Air Interface Um
TB
Encrypted Bits
S Training Sequence
S Encrypted Bits
TB
57
26
57
Fig. 7 Normal burst

3-16
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
*06. *DXVVLDQ 0LQLPXP 6KLIW .H\LQJ The information to be transmitted consisting of a sequence of binary data (bit sequence) must be modulated on an information carrier with a specific rate (bit rate). The receiver must then be able to remove them from this carrier. To obtain the best possible bandwidth utilization taking the minimum requirements for transmission quality into consideration, a IUHTXHQF\ PRGXODWLRQ PHWKRG was chosen for the GSM system. It is known as *06. *DXVVLDQ 0LQLPXP 6KLIW .H\LQJ. In principle the bandwidth of a radio channel (RFC) of 200 kHz varies here around the center of the bandwidth (carrier frequency ft) with a maximum frequency displacement f = 67.7 kHz3 .
06. 0LQLPXP 6KLIW .H\LQJ MSK is a frequency shifting modulation process which involves the information in the instantaneous frequency of the HF signal. This process stands out because of the continuous phase4 processing of the modulation signal resulting in excellent bandwidth utilization. The binary signal is modulated5 on the carrier using a modulation index = f/fmod = 0.5. The instantaneous frequency of the HF signal changes with the applied modulation data. When there is a "1", the carrier frequency ft is increased by f, when there is a "0" decreased by f. With a modulation index of 0.5 f corresponds with the half modulation frequency fmod. With MSK the phase angle of the carrier is changed linearly and continually during the bit duration T. It is changed by +90 for a logical "1" at the modulator input and by -90 for a "0". The frequency of the HF signal can be seen in the context of the phase relationship. It is also obtained from the trajectory of the phase path or the phase path is obtained from the integral of the frequency path. f can also be calculated from bit duration T and the change in the phase relationship (). f = (/t) / 2; with = /2 (90) and t = T = 3.6923 s hence: f = 1/(4T) = 1/(4*3.6923s) = 67.7 kHz

I I
7DSSOLHV7 GXUDWLRQRIDELW
V
LHWKHUHLVQRSKDVHMLWWHULQJ FDUULHUGHYLDWLRQI
PRG
PRGXODWLRQIUHTXHQF\I
PRGELWUDWHIELW
A30808-X5226-C559-1-7618
3-17
Siemens
Air Interface Um
MSK Modulation
Phase response 1 Binary signal f Frequency response f f f f 0
+180 +90 Phase t -90 -180
Fig. 8 Frequency and phase response with the MSK modulation process

3-18
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
*06. Reducing the bandwidth required for MSK can be achieved by prefiltering the data signal. The "increments" of the data (0 1) and thus also frequencies or unsteadiness of the phase path result in a comparably wide spectrum. To reduce the bandwidth requirement by means of improved attenuation of the side bands a lowpass prefilter with the pass through characteristic of a Gaussian bell-shaped curve is used. The filter used with bandwidth B6 has the following impulse answer (Rec. 05.04):
H( t )= 1 / 2 T * et /2 T with = 2 /2B * T
2 2 2
H (f)= e(ln2/2B
)*f2
The data signals Gaussian filtered here have "softer" transitions thus affecting the phase path. A frequency or phase change without jumps (continuous) results.
ZDVFKRVHQDVDVWDQGDUGL]HGILOWHUEDQGZLWKIRUWKH*DXVVILOWHULHEDQGZLGWK% ELWGXUDWLRQ7JLYHQ% N+]
A30808-X5226-C559-1-7618
3-19
Siemens
Air Interface Um
3-20
A30808-X5226-C559-1-7618
Air Interface Um
Siemens

7LPH 2UJDQL]DWLRQ )UDPLQJ
The transmission of the control and user information (speech/data) takes place in physical channels. A time slot is available in the TDMA frame every 4.615 ms. The information is transmitted according to specific time schemas, i.e. certain contents are repeated at specific time intervals. This process, i.e. the periodical repeat of the TDMA frame is called "framing".
A30808-X5226-C559-1-7618
3-21
Siemens
Air Interface Um
BCCHMultiframe Time 50 49 48 47 46 . . . . . . . . 6 5 4 3 2 1 RFC 1 RFC 2 0 0 RFC 3 1 RFC 174 Frequency FDMA 2 3 25 . 24 . . . 6 5 4 3 2 1 0 4 TDMA Frame 5 6 7 TCHMultiframe
Fig. 9 Physical channels / traffic and control channel multiframe

3-22
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
0XOWLIUDPH TDMA frames belonging together in a first framing level are called PXOWLIUDPHV. There are 26 TDMA frames in a XVHU FKDQQHO PXOWLIUDPH, in a FRQWURO or VLJQDOLQJ FKDQQHO PXOWLIUDPH there are 51 TDMA frames. The control channel multiframes are transmitted as a rule in time slot 0 of one of the radio channels (RFCs) from a BTSE, the remaining time slots are available for user channel multiframes.
1RWH1RWRQO\VXEVFULEHULQIRUPDWLRQVSHHFKGDWDFDQEHWUDQVPLWWHGLQDdWUDIILFFKDQQHOo,IWKHVLJQDOLQJUHTXLUHPHQW LQFUHDVHVVLJQDOLQJFDQDOVREHWUDQVPLWWHGYLDDWUDIILFFKDQQHO$FKDQJHEHWZHHQVXEVFULEHULQIRUPDWLRQDQGVLJQDOLQJLV LQGLFDWHGE\WKHVRFDOOHGdVWHDOLQJIODJVoLQWKHQRUPDOEXUVW
A30808-X5226-C559-1-7618
3-23
Siemens
Air Interface Um
1 Multiframe for signaling 1) 51 TDMA frame = 235,38 ms 0 1 2 49 50 0
1 Multiframe for Speech/Data 2) 26 TDMA frame = 120 ms 1 2 1) 2) 1 TDMA frame 4,615 ms 4 5 6 7 24 25
Signaling channels User channels and associated signaling channels
8 Time slot = 0 1 2 3
1 Time slot BURST = Contents of a time slot
156,25 bit = 576,88 s (1 bit = 3,692 s)
Time organization of the air interface
Fig. 10 Multiframe

3-24
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
The multiframe for user information (full or half rate transmission) will be used at this point as an example of multiframe time organization. The diagram shows the periodical repeat of the fixed structure of certain "logical contents" for a user channel with half and full rate transmission. All 26 TDMA frames repeat specific contents. This is necessary because not only user information (data, speech) is transmitted in the traffic channel connection (called TCH here) but also further specific signaling information (SACCH) has to be transmitted repeatedly at fixed intervals in a traffic channel multiframe. The information (user information signaling) is transmitted between MS and BTS as burst in physical channels. To differentiate the contents a division into "logical" channels is useful. These "logical channels" specify therefor certain contents of the transmission over the air interface. In particularly for signaling different contents and therefor "logical channels" are relevant. They are repeated in the signaling channel multiframe every 51 TDMA frames.
A30808-X5226-C559-1-7618
3-25
Siemens
Air Interface Um
UPLINK / DOWNLINK: Traffic Channel (TCH)
26 TDMA frame 120 ms
A full rate TCH T/t A/a = TDMA frame for TCH TDMA frame for SACCH/T
Two full rate TCH
Fig. 11 Multiframe for a user channel

3-26
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
6XSHUIUDPH +\SHUIUDPH The data packets from the time slots are compiled in even higher frame structures in addition to this first framing level of the merging of the TDMA frames to multiframes. These are called superframes and hyperframes. A VXSHUIUDPH comprises 26 x 51 = 1326 frames and is thus 6.12 s long. The superframe is the smallest common multiple of traffic channel multiframes (26 frames) and control or signaling channel multiframes (51 frames). The time window of a superframe is the shortest cycle in which the organization of all channels is repeated. Some characteristics of the channel organization are excluded from this repeat. These are contained in the hyperframe. The K\SHUIUDPH is the numbering period. It comprises 2048 superframes and is thus exactly 12,533.760 s or 3 h 28 min 56.76 s long. It is a multiple of all cycles described up to now and determines all transmission cycles or periods on the air interface in practice.
A30808-X5226-C559-1-7618
3-27
Siemens
Air Interface Um
Hyperframe = 2048 Superframe
Superframe = 26 x 51 (Multi-) Frames
TCH Multiframe 0 1 2 3 24 25
BCH Multiframe 0 1 2 3 4 49 50
TDMA Frame
Fig. 12 Time organization: multiframe, superframe and hyperframe

3-28
A30808-X5226-C559-1-7618
Air Interface Um
Siemens

$GDSWLYH )UDPH $OLJQPHQW
Adaptive frame alignment is the time condition between uplink (UL) and downlink (DL). The TDMA frames (UL) running from the mobile station (MS) to the base station (BS) or especially the transmission and reception station (BTSE) are delayed by 3 time slots (burst periods) compared with the (DL) TDMA frame running in the opposite direction. The BTSE sets the frame (master), the MS has to adapt itself to the presetting. The delay of 3 time slots (= 1.73 ms) is GSM-defined. This GSM convention is set up in such a way that the numbering of the time slots can be identical both in the UL and the DL direction. The time delay allows the mobile station to avoid sending and receiving at the same time. This means substantially simpler technical implementation as the MS receiver does not have to be protected against the transmitter from the same MS ("signal isolation"). The so-called "combining" of antennas is thus not necessary. 7LPLQJ DGYDQFH There is a problem, however, when implementing this convention. If the distance between the BTSE and the MS is greater, the delay due to the run time of the signals must be taken into consideration. Even at the speed of light (3 x 108 m/s) the radio signals also require a specific time to bridge the path between the BTSE and the MS. With a maximum cell radius (GSM900) of approx. 35 km this means a delay of approx. 0.1 ms for the path BTSE - MS or of approx. 0.2 ms for a "round path". This delay in the run time must be taken into consideration when the signal is sent from the MS because it is absolutely necessary that the BTSE receives the signals (bursts) from the different MS in the correct time range. Bursts can otherwise overlap time slots from neighboring time slots and thus reduce the transmission quality substantially or even lead to a communication breakdown. This problem can be solved by the MS transmitting its signals earlier and compensating the run time delay. This compensation or its amount is called the "timing advance" (TA). The exact relocation between DL and UL from the viewpoint of the MS is 3 time slots minus the timing advance, i.e.: 1.73 ms - TA. The duration of the timing advance is measured by the BTSE and transferred to the MS. This takes it into consideration within the framework of adaptive frame alignment and signals the total relocation (1.73 ms - TA) to the MS so the MS can take it into consideration when sending its bursts.
A30808-X5226-C559-1-7618
3-29
Siemens
Air Interface Um
BS transmission/receive station (BTS)
Information for MS on the Timing Advance
1 Mobile station (MS) 2 x Run time (TA)
Transmitter Receiver
t = 3 Time slots
Fig. 13 Adaptive frame alignment

3-30
A30808-X5226-C559-1-7618
Air Interface Um
Siemens

)UHTXHQF\ +RSSLQJ
Frequency hopping means that RFC physical channels8, therefore the transmit channel and consequently the transmit frequency are changed to a set algorithm. The time slot is not changed. The logic behind frequency hopping is to guarantee that all channels have the same high degree of transmission quality by dividing possible interference occurring in only one RFC over all available channels. Frequency hopping is used to reduce or evenly distribute signal losses. These can be caused by screening of an MS in a vehicle or due to multipath propagation (direct signal + on trees, houses, mountains,... reflected signals) as a result of negative interference. As the local occurrence of these signal losses is directly dependent on the wave length of the radio signal (approx. 33 cm at 900 MHz), changing the transmission frequency will also lead to a change in the radio wave propagation. This allows great transmission losses to be minimized. As well as reducing interference, frequency hopping also improves protection against eavesdropping. The BTSE controls optional frequency hopping. As the MS also has to carry out these the BTSE also transmits the frequency hopping algorithm via a BCCH. This BCCH is therefore not affected by the frequency hopping.
7KHH[FHSWLRQLVWKHFKDQQHOVRIWKH5)&VRQZKLFKWKH%&&+LVVHQW
A30808-X5226-C559-1-7618
3-31
Siemens
Air Interface Um
TDMA Frame RFC 1
RFC 2
RFC 3
RFC 4
RFC 5
TCH
Frame 0
Frame 1
Frame 2
Frame 3
Frame 4
Frame 5
Fig. 14 An example of frequency hopping

3-32
A30808-X5226-C559-1-7618
Air Interface Um
Siemens

/RJLF RI /D\HU 8P
/RJLFDO 7\SHV DQ 2YHUYLHZ
A multitude (for signaling in particular) of different "logical channels" or "logical channel types" is used in the GSM system for transmission via the air interface. These logical types:
z z
WUDIILF FKDQQHOV VLJQDOLQJ FKDQQHOV
A30808-X5226-C559-1-7618
3-33
Siemens
Air Interface Um
&+$11(/6
TRAFFIC CHANNELS
SIGNALING CHANNELS
FULL RATE
HALF RATE
BROADCAST CONTROL CHANNLES
COMMON CONTROL CHANNLES
DEDICATED CONTROL CHANNLES
UL + DL UL + DL UL + DL DL DL UL
TCH/F
TCH/H
BCCH FCCH
SCH PCH NCH AGCH
RACH
SACCH
SDCCH FACCH
Fig. 15 Hierarchy of the logical channels

3-34
A30808-X5226-C559-1-7618
Air Interface Um
Siemens

7UDIILF &KDQQHOV
7UDIILF FKDQQHOV 7&+ The task of the traffic channels is to transmit coded speech and data information from the mobile subscriber. Two general forms of a traffic channels are defined: a) Full rate traffic channels (TCH / F) This channel transmits speech on the air interface Um at a transmission rate of 13 kbit/s (TCH / FS) or data at 9.6 kbit/s (TCH / F9.6), 4.8 kbit/s (TCH / F4.8) or 2.4 kbit/s (TCH / F2.4). b) Half rate traffic channels (TCH / H) Speech is transmitted at 6.5 kbit/s (TCH / HS), data is transmitted at 4.8 kbit/s (TCH / H4.8) or 2.4 kbit/s (TCH / H2.4).

z z z
6LJQDOLQJ &KDQQHOV
%&&+ &&&+ '&&+
The signaling channels are organized into 3 types according to their tasks: Broadcast control channels: Common control channels: Dedicated control channels:
A30808-X5226-C559-1-7618
3-35
Siemens
Air Interface Um
%URDGFDVW FRQWURO FKDQQHOV %&&+ The broadcast control channels BCCH are used for synchronizing and transmitting the cell-specific data from the BTSE to the MS. They only work in downlink (DL) direction, i.e. from the BS in the direction of the MS. There are the following according to tasks:
z
Frequency correction channel )&&+: allows exact frequency matching for MS Synchronization channel 6&+: after frequency synchronization (by the FCCH) the MS receives further information via the SCH in order to continue with the check-in procedure. The information contains the BSIC and the current TDMA frame number
Broadcast control channel %&&+: contains further information which the MS requires as a reference to the cell (e.g.: channel combination, frequency hopping sequence, cell identification CGI)
&RPPRQ FRQWURO FKDQQHOV &&&+ The common control channels CCCH are used to control access to the BTSE or the MS. They are unidirectional channels, i.e. they work in either downlink (DL) or uplink (UL) direction There are the following according to tasks:
z
Paging channel 3&+: used (DL) by the BTSE to call the MS Notification Channel 1&+: used (only DL) to notify mobile stations of voice group and voice broadcast calls. Random access channel 5$&+: used by the MS to request a signaling channel (UL) from the network or to react to a PCH.
Access grant channel $*&+: assignment of a signaling channel by the BTSE (network) for the MS (DL).
3-36
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
'HGLFDWHG FRQWURO FKDQQHOV '&&+ The group of GHGLFDWHG FRQWURO FKDQQHOV DCCH also comprises 3 channels:
z
Stand alone dedicated control channel 6'&&+: Bi-directional and used for call setup. $XWKHQWLFDWLRQ and other main VLJQDOLQJ IXQFWLRQV takes place here. The MS is assigned a specific TCH with the help of the SDCCH.
Slow associated control channel 6$&&+: always coupled to an SDCCH or with a TCH. Signaling information (FRQWURO and PHDVXULQJ SDUDPHWHUV) is exchanged between the MS and BTSE via the SACCH.
%6
transmits network-specific information using SACCH to keep the MS up to date on any changes in the cell parameters. Furthermore the control commands for timing advance and power control are transmitted by the BS to the MS via the SACCH. transmits measuring results (e.g. receive level) to the BS to support them in decisions on the handover. It also informs the BS of the current values of transmission power and timing advance. This function is known as a measurement report.
06
Fast associated control channel) )$&&+: activated when the signaling requirement increases in certain situations (e.g. during a handover). The FACCH is transmitted instead of a TCH. The "stealing bits" in the TCH indicate the channel change.
A30808-X5226-C559-1-7618
3-37
Siemens
Air Interface Um

3-38
A30808-X5226-C559-1-7618
Air Interface Um
Siemens

%XUVW 7\SHV
As previously described transmission of the information from an individual time slot with a permanently defined bit sequence is called a EXUVW. There are 5 different types of bursts:
z z z z z
Normal burst Frequency correction burst Synchronization burst Access burst Dummy burst
1RUPDO EXUVW The normal burst contains information in traffic and control channels and is structured as following:
z z z
2 x 3 bits as tail bits (7%) for edge limitation of the time slot. 2 x 57 HQFU\SWHG ELWV which carry the actual information / data. 2 x 1 bit as a "stealing flag" which tells the receiver that the user data transmission is interrupted briefly and signaling data is transmitted instead of the user data (or vice versa). 26 bits for synchronizing and fault detection (WUDLQLQJ VHTXHQFH) allow both the BS and the MS to synchronize itself to a burst and thus assign the data bits exactly. There are 8 various training sequences in the GSM with a permanently defined bit pattern allowing the bit sequence actually received to be compared with the known bit sequence. This allows distorted or incomplete received signals9 to be reconstructed. 8.25 bits JXDUG SHULRG (GP) for collecting run times and reception times (determined by the distance BTSE MS).
'XHWRPXOWLSDWKSURSDJDWLRQ'RSSOHUHIIHFW
A30808-X5226-C559-1-7618
3-39
Siemens
Air Interface Um
148 bit = 546,12 s (+8,25 bit = 30,44 s )
TB
Information
Training Sequence
Information
TB
GP
57
26
57
8,25 bit
Fig. 16 Normal burst

3-40
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
)UHTXHQF\ FRUUHFWLRQ EXUVW The frequency correction burst is transmitted from the BTS for frequency synchronization. The bit sequence of the fixed bits corresponds with an unmodulated carrier, i.e. a pure sine wave, so the MS can synchronize itself to the preset frequency. The repeat of frequency correction bursts is also known as the IUHTXHQF\ FRUUHFWLRQ FKDQQHO )&&+. The frequency correction burst consists of:
z z z
2 x 3 bit tail bits (TB); 142 bit as fixed bits (sine wave10) for frequency synchronization; 8.25 bit guard period (GP);
7REHPRUHSUHFLVHWKHIL[HGELWV[VLJQDOdoOHDGYLDWKLVPRGXODWLRQWRDVLQXVRLGDOVLJQDOIRUWKLVSHULRGZLWKD IUHTXHQF\EHLQJN+]DERYHWKHFDUULHUFHQWUDOIUHTXHQF\

A30808-X5226-C559-1-7618
3-41
Siemens
Air Interface Um
TB
fixed Bits
TB
GP
142
8,25 bits
Fig. 17 Frequency correction burst

3-42
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
6\QFKURQL]DWLRQ EXUVW The MS receives the first information on the BS from the synchronization burst allowing it to V\QFKURQL]H WLPH on the base station. The burst contains a long training sequence, the TDMA number and the identity code of the BS, BSIC11. The TDMA frame number is required as one of the parameters for encryption. The synchronization burst is transmitted together with the frequency correction burst in the TDMA time slot zero. The repeat of synchronization bursts is called synchronization channel. The synchronization burst consists of:
z z z z
2 x 3 bit tail bits (TB); 2 x 39 bit which contain the TDMA frame number and the identity code of the BS (BSIC); 64 bit training sequence for time synchronization and fault detection; 8.25 bit guard period (GP);
%6,&%DVHWUDQVFHLYHU6WDWLRQ,GHQWLW\&RGH,GHQWLW\FRGHRIWKH%76DOORZLQJWKH06WRGLVWLQJXLVKEHWZHHQGLIIHUHQW %76LWFRQVLVWVRIFKDUDFWHUVFKDUDFWHUVIRUWKH1&&1HWZRUN&RORU&RGH 3/01LGHQWLW\DQGFKDUDFWHUVIRUWKH%&& %DVH&RORU&RGHZKLFKDOORZVGLIIHUHQW5)&VZLWKWKHVDPHIUHTXHQF\LQQHLJKERULQJFOXVWHUVWREHGLVWLQJXLVKHG
A30808-X5226-C559-1-7618
3-43
Siemens
Air Interface Um
TB
Information
Training Sequence
Information
TB
GP
39
64
39
8,25 bits
Fig. 18 Synchronization burst

3-44
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
$FFHVV EXUVW The access burst is used for the MS contact setup with the BTSE. It is characterized by a long protection time (GP = 68.25 bits or 252 s) which takes the signal run time12 from MS to BTSE into consideration. The MS does not know the distance to the BTSE first of all and therefore does not know how the transmission has to be staggered (moved forward). The access burst consists of:
z z z z
8 + 3 bit tail bits (TB); 41 bit synchronization sequence; 36 bit information bits; 68.25 bit guard period (GP);
'XPP\ EXUVW The dummy burst is sometimes sent as padding if there is no other information. It does not contain any information but has the same format as the normal burst.
1RWH7KHOHQJWKRIWKHDFFHVVEXUVWLVGHFLVLYHIRUWKHPD[LPXPFHOOVL]HRID*60FHOO:KHQDFRQWDFWLVVHWXSZLWKDQ 06WKHELWVZLWKDGXUDWLRQRIVDUHVXIILFLHQWDVDVHFXULW\GLVWDQFHIRU[PV[V NP7KHFHOO UDGLXVPXVWWKHUHIRUHEHOHVVWKDQNPWDNLQJWKHZD\%76(06%76(LQWRFRQVLGHUDWLRQ

A30808-X5226-C559-1-7618
3-45
Siemens
Air Interface Um
TB
Synchro.- Sequence
Information
TB
GP
41
36
68,25 bits
Fig. 19 Access burst

3-46
A30808-X5226-C559-1-7618
Air Interface Um
Siemens

0XOWLIUDPH &KDQQHO &RPELQDWLRQ
The description of the multiframe mentioned that there was only one possibility of arranging the logical channels in multiframes. Moreover there are 7 different combinations (channel combinations) for arranging logical channels in multiframes. In the channel combinations13 listed below RACH, PCH and AGCH are combined in CCCHs as they all involve the allocation of a channel to a subscriber: , 7&+) )$&&+) 6$&&+) ,, 7&++ )$&&++ 6$&&++ ,,, 7&++ )$&&++ 6$&&++ 7&++ )$&&++ 6$&&++ ,9 )&&+ 6&+ &&&+ %&&+ 9 )&&+ 6&+ &&&+ %&&+ 6'&&+ 6$&&+ 9, &&&+ %&&+ 9,, 6'&&+ 6$&&+
F S 0 1
BCCH 2-5
CCCH 6-9
F S 10 11
CCCH 12 - 19
F S 20 21
CCCH 22 - 29
F S 30 31
CCCH 32 - 39
F S 40 41
CCCH 42 - 49
I 50
DL: F = FCCH, S = SCH, B = BCCH, C = CCCH, (PCH, AGCH), I = idle
R R 0 1
R R 10 11
R R 20 21 UL: R = RACH
R R 30 31
R R 40 41
R 50
Fig. 20 Multiframe for channel combination IV) FCCH + SCH + CCCH + BCCH

RUPHDQVXSWRGHGLFDWHGDQGDVVRFLDWHGFRQQHFWLRQVWR06
A30808-X5226-C559-1-7618
3-47
Siemens
Air Interface Um
51 TDMA Rahmen = 235,38 ms DOWNLINK: Broadcast Control Channel (BCCH), Common Control Channel (CCCH) +4 Stand Alone Dedicated Control Channels (SDCCH/4)
FS FS
B B
C C
FS FS
C C
C C
FS FS
D0 D0
D1 D1
FS FS
D2 D2
D3 D3
FS FS
A0 A2
A1 A3
I I
UPLINK:
Common Control Channel (CCCH) +4 Stand Alone Dedicated Control Channels (SDCCH/4)
D3 D3
RR RR
A2 A0
A3 A1
RRRRRRRRRRRRRRRRRRRRRRR RRRRRRRRRRRRRRRRRRRRRRR
D0 D0
D1 D1
RR RR
D2 D2
A B C D F R S I
TMDA frame for SACCH BCCH CCCH SDCCH frequency correction burst RACH synchronized burst idle
Fig. 21 Multiframe for channel combination V)

3-48
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
3XUSRVH XVH RI WKH GLIIHUHQW FKDQQHO FRPELQDWLRQV , ,,, I) &DOO DQG GDWD WUDQVPLVVLRQ LQ D 7&+ IUDPH Combination I) is primarily used to transmit TCH/F (full rate speech). In combination I) the first 12 frames (0 - 11) are used for call or data transmission, a SACCH is then transmitted (frame 12) and also 12 frames (13 - 24) for call and data transmission. The last frame (25) is not used (I: idle). Combination II) and III) are primarily used for transmitting user data at half rate. 2 TCH/H have to "share" the 26 multiframe with their associated control channels. Data from the first or second subscriber is alternately filled into the frame. The SACCH of the 1st subscriber is in frame 12, the SACCH of the 2nd subscriber in frame 25. This means there are no empty (idle) frames.
II) III)
The FACCH does not have a fixed frame in combination I) to III). If signaling is necessary, indicated by the "stealing flag" in the normal burst, a 20 ms long part of the multiframe which is 120 ms long in total is occupied with FACCHs instead of TCHs. 9 9,, 9 %76(
j 06 VLJQDOLQJ
Channel combination V) is the minimum configuration for a base station. It is mostly used when a BTS is only equipped with 1 or 2 RFCs. Channel combination V) may only be used once in a cell because the mobile station searches for the frequency correction channel FCCH for synchronizing and the channel for time synchronization SCH. It is transmitted to time slot 0 of an RFCs (base frequency14). Channel combination V) and IV) rule each other out.

7KHEDVHIUHTXHQF\FDQEHDQ\5)&LWPXVWEHVHQWFRQVWDQWO\KRZHYHU
A30808-X5226-C559-1-7618
3-49
Siemens
Air Interface Um
,9
Channel combination IV) is mainly used for BTS with several RFCs as it provides the common control channels CCCH with a lot of space. It may only be used once for the same reasons as with combination V) (in time slot 0 of one of the RFC). As opposed to combination V) there are no dedicated channels in combination IV). Channel combination VII) is thus also required when channel combination IV) is used. A BTS can contain up to 16 RFCs in the GSM system. When a lot of RFCs are used (corresponding with a very high traffic volume in the cell) further task sharing can be useful in the channel combination. Channel combination VI) which only contains common control channels CCCH as well as the BCCH is used for this. This means that it is necessary to also use combination IV) and VII) in addition to channel combination VI). Combination IV) is in time slot 0 of the base frequency and VI) going onto 2, 4 and 6. Channel combination VII) is used to accommodate the dedicated channels SDCCH and SACCH each for up to 8 connections between BTSE and MS and is used as a supplement to combination IV) and VI). Meanwhile there are channel combinations existing, which inhabit the Cell Broadcast (for SMS CBS).
9,
9,,
Remark:
3-50
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
/D\HU 8P,QWHUIDFH
The task of layer 2, the data circuit layer, is so-called "linking", i.e. the safe transmission of signaling messages via an individual signaling link. Layer 2 (linking) protocols in the different GSM interfaces are the same to a great extent, they have very similar functions. The main tasks of layer 2 are generally the structuring of the information to be transmitted on the communication channel:
z z z z
Fault detection and correction Stable transmission, i.e. guaranteed free of errors; otherwise transmission repeat Disassembly of the individual data stream and reconstruction Flow control
Layer 2 (Data Link Layer) defines the structure of the 23-byte blocks in the CCM and in particular the numbering and acknowledgment of the blocks.
A30808-X5226-C559-1-7618
3-51
Siemens
Air Interface Um
&& &DOO &RQWURO
666 6XSSOHPHQWDU\ 6HUYLFHV 6XSSRUW
606 6KRUW 0HVVDJH 6HUYLFH
/D\HU 1HWZRUN /D\HU &0 &RQQHFWLRQ 0DQDJHPHQW 00 0RELOLW\ 0DQDJHPHQW
55 5DGLR 5HVRXUFH 0DQDJHPHQW
/D\HU 'DWD /LQN /D\HU
/D\HU 3K\VLFDO /D\HU
Fig. 22 Layers 1 to 3 at the air interface; the sublayers of layer 3
3-52
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
The structure of a 23-byte transmission block in the SDCCH, FACCH, PCH, AGCH or BCCH is shown in the adjacent figure. (The block structure in SACCH deviates slightly from the illustration, whilst a block in the RACH consists of only one byte). A block of this type (known also as layer 2 frame) begins with an DGGUHVV ILHOG (1 byte), a FRQWURO ILHOG (1 byte) and a OHQJWK LQGLFDWRU (1 byte). The subsequent LQIRUPDWLRQ ILHOG contains the layer 3 data. If the 20 bytes available for this data are not completely used, the residual bytes are filled with the ILOO ELW SDWWHUQ "00101011" ("11111111" also permissible in uplink direction) in order to attain a total length of 23 bytes. Address field contents:
z z
/LQN 3URWRFRO 'LVFULPLQDWRU (LPD) for discriminating between the GSM protocol and other protocols (national or manufacturer-specific) 6HUYLFH $FFHVV 3RLQW ,GHQWLILHU (SAPI) for discriminating between short message service (SMS) and other layer 3 parts (RR, MM, CC or SSS) in the information field. (A special layer 3 format is used for SMS, and the SMS messages are numbered independently of the other messages in the control field). &RPPDQG5HVSRQVH )LHOG ELW (C/R) for discriminating between commands (messages transmitted on own initiative) and responses (reactions to received commands).
The control field is used to number and acknowledge the frames. Its structure is shown in the next figure. The length indicator specifies the length in bytes of the information field. The indicator additionally contains the 0RUH 'DWD ELW (M) specifying whether the layer 3 message extends to the follow-on layer 2 frame. It may be the case that a layer 3 message is longer than 20 bytes and must therefore be distributed over several layer 2 frames. In this case, the last frame is transmitted with M = 0 and all preceding frames with M = 1 ("Continuation in the next issue"). If the layer 3 messages fits into one layer 2 frame, the More-Data bit of the latter is set to 0 ("End").
A30808-X5226-C559-1-7618
3-53
Siemens
Air Interface Um
1 2 3
LPD
SAPI see next figure
C/R
Address Field Control Field
Length
Length Indicator
n Layer 3
23
Fill bits
Fig. 23 Structure of a Layer 2 frame (acc. to GSM 04.06)
3-54
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
The control field differentiates the following three frame types: ,QIRUPDWLRQ )UDPHV (I-frames), 6XSHUYLVRU\ )UDPHV (S-frames) and 8QQXPEHUHG )UDPHV (U-frames). Information frames are identified by the digit 0 in the least significant bit in the control field. These frames are used for error-protected message transmission. "Error protection" means in this context that the messages are individually numbered and acknowledged, thus allowing the receiver the opportunity to request a repeat transmission in the event of a transmission error or reception fault. Accordingly, the control field in the I-frame contains one VHQG QXPEHU N(S) and one UHFHSWLRQ QXPEHU N(R), each 3 bits in length. The send number numbers consecutively all Iframes running in the same direction on one CCH, whereby short message service (SMS) messages and other layer 3 part messages are counted separately. The reception number specifies which I-frame is next expected in the counterdirection; thus, the number is that of the last correctly-received I-frame + 1. I-frames are always commands and always include an information field. Supervisory frames are identified by the bit combination "01" in the two least significant bits in the control field. These frames are used for acknowledgment of received information frames without simultaneously supplying new information. Therefore, the S-frame control fields have only a reception number N(R) indicating the next anticipated I-frame in the counterdirection. Three types of S-frame are distinguished:
z z z
5HFHLYH 5HDG\ (RR): positive acknowledgment in normal operation 5HFHLYH 1RW 5HDG\ (RNR): positive acknowledgment simultaneously declaring that due to overload no further I-frames can currently be accepted 5HMHFW (REJ): negative acknowledgment (i.e. repeat request)
Supervisory frames can occur as commands or responses; they never include an information field. If information and supervisory frames are exchanged between MS and BSS in a CCH, D OD\HU FRQQHFWLRQ is said to exist in this CCH. The set up of such a layer 2 connection means that both sides allocate storage space for the valid send and reception numbers as well as for the buffering of as yet unacknowledged I-frames (which must possibly be retransmitted). This storage space is released when the layer 2 connection is cleared down.
A30808-X5226-C559-1-7618
3-55
Siemens
Air Interface Um
Frame
Format
bit pattern
Command Response N(S) 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 Command both both both Command Response Command Command Response
Inform. Field yes no no no possible no yes no possible
I RR S RNR REJ SABM DM U UI DISC UA 0 0 0 0 0
N(R) N(R) N(R) N(R) 0 0 0 1 1 1 0 0 0 1
P P/F P/F P/F P F P P F 0 0 1 1 1 0 0 0
0 1 0 1 1 0 0 0
Fig. 24 Control Field Structure (acc. to GSM 04.06)
3-56
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
As SMS messages are numbered separately from other messages, two independent layer 2 connections can exist in the same CCH: one layer 2 connection for SMS, one for all other layer 3 messages. Layer 2 connections may only be established in SDCCH and FACCH. For this reason, only unnumbered frames are used in all other CCH (i.e. BCCH, AGCH, PCH and SACCH). Unnumbered frames are identified by the digit 1 in the two least significant bits in the control field. These frames contain like their name suggests neither a send number nor reception number. The frames are not acknowledged, therefore, and the receiver cannot request a retransmission. A distinction is made between the following types of unnumbered frames:
z z z z
6HW $V\QFKURQRXV %DODQFHG 0RGH (SABM): layer 2 connection set up 'LVFRQQHFW (DISC): layer 2 connection cleardown 8QQXPEHUHG DFNQRZOHGJH (UA): positive acknowledgment for SABM 'LVFRQQHFW 0RGH (DM): negative acknowledgment for SABM; is also used in cases where an I-frame or S-frame arrives without a layer 2 connection having been established 8QQXPEHUHG ,QIRUPDWLRQ (UI): transmission of an information field without layer 2 connection.
SABM, DISC and UI are commands; UA and DM are responses. An information field is always included in the UI, but never in the DISC or DM. SABM and UA may optionally contain an information field. As layer 2 connections exist only in the SDCCH and FACCH, UI-frames are used exclusively in the BCCH, AGCH, PCH and SACCH. The P, F or P/F bits shown in table 3 are known as SROO ELWV in commands and ILQDO ELWV in responses. Their standard value is 0. By transmitting a command with P = 1, one side (MS or BSS) can specially request the opposite side to send a response labeled with F = 1. This polling method is used for set up and cleardown of the layer 2 connection (SABM or DISC with P = 1, UA with F = 1). The BSS likewise polls the MS to ascertain whether the latter is still accessible. Polling is additionally used when one side reports overload with RNR: the opposite side regularly queries (command RR with P = 1) whether the overload still exists (response RNR with F = 1) or not (response RR with F = 1). For all details of the Layer 2 protocol release refer to GSM Guideline 04.06
A30808-X5226-C559-1-7618
3-57
Siemens
Air Interface Um

/D\HU 8P
5DGLR 5HVRXUFH 0RELOLW\ &RQQHFWLRQ 0DQDJHPHQW
The layer 3 is composed of three sublayers comprising :

z z z
the Radio Resource Management (RR) functions the Mobility Management (MM) functions the Connection Management (CM) functions.
The Layer 3 messages can only contain maximal 249 Bytes.
3-58
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
CC Call Control
SSS Suplementary Services Support
SMS Short Message Service
Layer 3 Network Layer &0 Connectioon Management 00 Mobility Management
55 Radio Resuorce Management
Layer 2 Data Link Layer
Layer 1 Physical Layer
Fig. 25 Layers to 3 at the air interface; the sublayers of layer 3
A30808-X5226-C559-1-7618
3-59
Siemens
Air Interface Um

5DGLR 5HVRXUFH 0DQDJHPHQW 55
The Radio Resource management (GSM 04.08) messages will be sent between MS and BTS / BSC. Many RR messages will be transported over the Abis Interface within the RSL / DTAP to the BSC. Radio Resource management procedures include the functions related to the management of the common transmission resources, e.g. the physical channels and the data link connections on control channels. The general purpose of Radio Resource procedures is to establish, maintain and release RR connections that allow a point-to-point dialogue between the network and a Mobile Station. This includes the cell selection/reselection and the handover procedures. Moreover, Radio Resource management procedures include the reception of the uni-directional BCCH and CCCH when no RR connection is established. This permits automatic cell selection/reselection.
3-60
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
The HOHPHQWDU\ SURFHGXUHV IRU 5DGLR 5HVRXUFH PDQDJHPHQW are as follows :

z
,GOH PRGH SURFHGXUHV System information broadcasting Paging
55 FRQQHFWLRQ HVWDEOLVKPHQW SURFHGXUHV Entering the dedicated mode: immediate assignment procedure Entering the group transmit mode: uplink access procedure Paging procedure for RR connection establishment Notification procedure
3URFHGXUHV LQ GHGLFDWHG PRGH DQG LQ JURXS WUDQVPLW PRGH SACCH procedures Channel assignment procedure Handover procedure Frequency redefinition procedure Channel mode modify procedure Ciphering mode setting procedure Additional channel assignment procedure Partial channel release procedure Classmark change procedure Classmark interrogation procedure RR connection release procedure Group receive mode procedures Configuration change procedure
The following table summarizes Radio Resource Management messages:
A30808-X5226-C559-1-7618
3-61
Siemens
Air Interface Um
55 0DQDJHPHQW 0HVVDJHV FKDQQHO HVWDEOLVKPHQW PHVVDJHV ADDITIONAL ASSIGNMENT IMMEDIATE ASSIGNMENT IMMEDIATE ASSIGNMENT EXTENDED IMMEDIATE ASSIGNMENT REJECT &LSKHULQJ PHVVDJHV CIPHERING MODE COMMAND CIPHERING MODE COMPLETE +DQGRYHU PHVVDJHV ASSIGNMENT COMMAND ASSIGNMENT COMPLETE ASSIGNMENT FAILURE PDCH ASSIGNMENT COMMAND HANDOVER ACCESS HANDOVER COMMAND HANDOVER COMPLETE HANDOVER FAILURE RR-CELL CHANGE ORDER PHYSICAL INFORMATION RR INITIALISATION REQUEST HANDOVER ACCESS HANDOVER COMMAND HANDOVER COMPLETE HANDOVER FAILURE PHYSICAL INFORMATION &KDQQHO UHOHDVH PHVVDJHV CHANNEL RELEASE PARTIAL RELEASE PARTIAL RELEASE COMPLETE
5HPDUNV
3-62
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
3DJLQJ PHVVDJHV PAGING REQUEST TYPE 1 PAGING REQUEST TYPE 2 PAGING REQUEST TYPE 3 PAGING RESPONSE 6\VWHP LQIRUPDWLRQ PHVVDJHV SYSTEM INFORMATION TYPE 1 SYSTEM INFORMATION TYPE 2 SYSTEM INFORMATION TYPE 2bis SYSTEM INFORMATION TYPE 2ter SYSTEM INFORMATION TYPE 3 SYSTEM INFORMATION TYPE 4 SYSTEM INFORMATION TYPE 5 SYSTEM INFORMATION TYPE 5bis SYSTEM INFORMATION TYPE 5ter SYSTEM INFORMATION TYPE 6 SYSTEM INFORMATION TYPE 7 SYSTEM INFORMATION TYPE 8 SYSTEM INFORMATION TYPE 9 SYSTEM INFORMATION TYPE 13 SYSTEM INFORMATION TYPE 16 SYSTEM INFORMATION TYPE 17 6SHFLILF PHVVDJHV IRU 9%69*&6 NOTIFICATION/FACCH NOTIFICATION/NCH TALKER INDICATION UPLINK ACCESS UPLINK BUSY UPLINK FREE UPLINK RELEASE
A30808-X5226-C559-1-7618
3-63
Siemens
Air Interface Um
VGCS UPLINK GRANT EXTENDED MEASUREMENT ORDER EXTENDED MEASUREMENT REPORT 0LVFHOODQHRXV PHVVDJHV CHANNEL MODE MODIFY CHANNEL MODE MODIFY ACKNOWLEDGE CHANNEL REQUEST CLASSMARK CHANGE CLASSMARK ENQUIRY FREQUENCY REDEFINTION MEASUREMENT REPORT SYNCHRONIZATION CHANNEL INFORMATION RR STATUS GPRS SUSPENSION REQUEST &RQILJXUDWLRQ &KDQJH PHVVDJHV CONFIGURATION CHANGE COMMAND CONFIGURATION CHANGE ACKNOWLEDGE CONFIGURATION CHANGE REJECT $SSOLFDWLRQ PHVVDJHV APPLICATION INFORMATION
3-64
A30808-X5226-C559-1-7618
Air Interface Um
Siemens

0RELOLW\ 0DQDJHPHQW 00
The Mobility Management (GSM 04.08) messages will be sent between MS and MSC and have no influences to the BSS. The MM messages will be transported over the Abis and A-Interface within the RSL / DTAP and DTAP to the BSC. The main function of the Mobility Management sublayer (GSM 04.08) is to support the mobility of user terminals, such as informing the network of its present location and providing user identity confidentiality. A further function of the MM sublayer is to provide connection management services to the different entities of the upper Connection Management (CM) sublayer. The HOHPHQWDU\ SURFHGXUHV IRU 0RELOLW\ 0DQDJHPHQW are as follows :
z
00 FRPPRQ SURFHGXUHV TMSI reallocation procedure Authentication procedure Identification procedure IMSI detach procedure Abort procedure MM information procedure
00 VSHFLILF SURFHGXUHV Location updating procedure Periodic updating IMSI attach procedure Generic Location Updating procedure
&RQQHFWLRQ PDQDJHPHQW VXEOD\HU VHUYLFH SURYLVLRQ MM connection establishment MM connection information transfer phase MM connection release
The following table summarizes Mobility Management messages:
A30808-X5226-C559-1-7618
3-65
Siemens
Air Interface Um
00 0DQDJHPHQW PHVVDJHV 5HJLVWUDWLRQ PHVVDJHV IMSI DETACH INDICATION LOCATION UPDATING ACCEPT LOCATION UPDATING REJECT LOCATION UPDATING REQUEST 6HFXULW\ PHVVDJHV AUTHENTICATION REJECT AUTHENTICATION REQUEST AUTHENTICATION RESPONSE IDENTITY REQUEST IDENTITY RESPONSE TMSI REALLOCATION COMMAND TMSI REALLOCATION COMPLETE &RQQHFWLRQ PDQDJHPHQW PHVVDJHV CM SERVICE ACCEPT CM SERVICE REJECT CM SERVICE ABORT CM SERVICE REQUEST CM RE-ESTABLISHMENT REQUEST ABORT 0LVFHOODQHRXV PHVVDJHV MM INFORMATION MM STATUS MM NULL
5HPDUNV
3-66
A30808-X5226-C559-1-7618
Air Interface Um
Siemens

z z z
&RQQHFWLRQ 0DQDJHPHQW &0
The Connection Management (CM) sublayer is composed of : Call Control (CC) Short Message Service Support (SMS) Supplementary Services Support (SS)
The CC messages will be sent between the MS and the MSC and will therefore be considered mainly. Every mobile station must support the call control protocol. If a mobile station does not support any bearer capability at all then it shall respond to a SETUP message with a RELEASE COMPLETE message. In the call control protocol, more than one CC entity are defined. Each CC entity is independent from each other and shall communicate with the correspondent peer entity using its own MM connection. Different CC entities use different transaction identifiers. The HOHPHQWDU\ SURFHGXUHV IRU FLUFXLW VZLWFKHG &DOO &RQWURO are as follows:
z
&DOO HVWDEOLVKPHQW SURFHGXUHV Mobile originating call establishment Mobile terminating call establishment
6LJQDOLQJ SURFHGXUHV GXULQJ WKH DFWLYH VWDWH User notification procedure Call rearrangements User initiated level up- and downgrading
&DOO FOHDULQJ Clearing initiated by the mobile station Clearing initiated by the network Clear collision
0LVFHOODQHRXV SURFHGXUHV In-band tones and announcements Call collisions Status procedures Call re-establishment, mobile station side Call re-establishment, network side DTMF protocol control procedure
The following table summarizes Call Control messages:
A30808-X5226-C559-1-7618
3-67
Siemens
Air Interface Um
&& PHVVDJHV &DOO HVWDEOLVKPHQW PHVVDJHV ALERTING CALL CONFIRMED CALL PROCEEDING CONNECT CONNECT ACKNOWLEDGE EMERGENCY SETUP PROGRESS SETUP &DOO LQIRUPDWLRQ SKDVH PHVVDJHV MODIFY MODIFY COMPLETE MODIFY REJECT USER INFORMATION &DOO FOHDULQJ PHVVDJHV DISCONNECT RELEASE RELEASE COMPLETE 0HVVDJHV IRU VXSSOHPHQWDU\ VHUYLFH FRQWURO FACILITY HOLD HOLD ACKNOWLEDGE HOLD REJECT RETRIEVE RETRIEVE ACKNOWLEDGE RETRIEVE REJECT
5HPDUNV
3-68
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
0LVFHOODQHRXV PHVVDJHV CONGESTION CONTROL NOTIFY START DTMF START DTMF ACKNOWLEDGE START DTMF REJECT STATUS STATUS ENQUIRY STOP DTMF STOP DTMF ACKNOWLEDGE
CC Call Control
SSS Supplementary Services Support
SMS Short Message Service
Layer 3 Network Layer &0 Connection Management
00 Mobility Management
55 Radio Resource Management
Layer 2 Data Link Layer
Layer 1 Physical Layer
Fig. 26 Layers to 3 at the air interface; the sublayers of layer 3
A30808-X5226-C559-1-7618
3-69
Siemens
Air Interface Um

)RUPDWWLQJ 5XOHV
Every layer 3 message is comprised of several parameters, also known as information elements. Section 9 of GSM Guideline 04.08 defines the mandatory and optional parameters for every message. The same parameter may be mandatory for one message and optional for another. Optional parameters bear an identifier (Information Element Identifier, IEI) to designate their presence. The identifier is always located at the beginning of the parameter. Mandatory parameters, by contrast, include sometimes - dependent on the position - an identifier. The parameters are sub-divided into 5 parameter formats (described in GSM 04.07): 9 (value only) parameters have neither an identifier (IEI) nor a length indicator; they are mandatory parameters of fixed length. The length is either an integer amount of bytes or 1/2 byte. In the last case, V-parameters of 1/2 byte length are combined to form pairs whenever possible. The first parameter in the combination encompasses the 4 least significant bits, the second parameter the 4 most significant bits. If the total number of V-parameters of 1/2 byte is odd, the 4 most significant bits of the last byte are filled with 0000. (type and value) parameters have an identifier (IEI) but no length indicator. If the length of the contents is an integer amount of bytes, then the IEI is 1 byte in length, and the most significant IEI bit is 0. If the length of the contents is 1/2 byte, then the IEI is likewise 1/2 byte in length. The most significant bit is 1, and the succeeding bits must not be 010 (to distinguish them from Tparameters, see below). (type only) parameters have 0 byte content. The communicated information consists solely in the presence or absence of the parameter. Obviously, such parameters can only be considered as optional. The identifier (IEI) is 1 byte in length and begins with 1010 (so that no confusion with TV-parameters is possible). One example of a type-2 parameter is the authorization given in "Location Update Accept" for the Mobile Station to set up a MM connection directly after the location update (i.e. in the same RR connection). This authorization may, or may not, be present. (length and value) parameters have a length indicator but no identifier (IEI); they are mandatory parameters of variable length. The length indicator is the first byte and indicates how many bytes of contents follow. (type, length and value) parameters have an identifier (IEI) and a length indicator. The IEI is the first byte of the parameter; its most significant bit is 0. The length indicator is the second byte of the parameter and indicates how many bytes of contents follow.
79
/9
7/9
3-70
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
/D\HU SDUDPHWHUV *60

Parameter Format Length integer amount of Bytes Length of 1/2 Bytes Example: 5 parameters 9 alue content content 2 content 4 0 0 0 0 content 1 content 3 content 5
7 ype, 9 alue
IEI 0 content IEI 010 content
7 ype
1 0
IEI
/ ength, 9 alue
Length indicator content
7 ype, / ength, 9 alue
IEI Length indicator content
Fig. 27 Parameter formats
A30808-X5226-C559-1-7618
3-71
Siemens
Air Interface Um
Each message begins with the same three V-parameters: The SURWRFRO GLVFULPLQDWRU specifies the layer 3 part to which the message belongs. It is a parameter of 1/2 byte length. The WUDQVDFWLRQ LGHQWLILHU (TI) characterizes the transaction ( = CM connection, cf. 2.3). It is a V-parameter of 1/2 byte, too; in conformity with the rules, the protocol discriminator and the TI together fill 1 byte. For RR and MM messages (protocol discriminator = 0110 or 0101), no CM connection is established; for this reason, the TI is replaced by the VNLS LQGLFDWRU whose value is 0. With a proper TI, the most significant bit serves as TI flag in messages for other TI parts; it is 0 in messages IURP the side which set up the transaction, and 1 in messages to the side which set up the transaction. The three remaining bits form the TI value are freely selected by the initiating side in a transaction set up; the value 111 is not permissible. The PHVVDJH W\SH identifies the nature of the message (e.g. "Handover Command", "Location Update Request", "Setup" and many other examples). It is a V-parameter with a length of 1 byte. The second bit is the send sequence number N(SD). In all messages from the Base Station, as well as in RR messages from the Mobile Station, this bit is 0. In MM and CM messages from the Mobile Station the bit alternately has the values 0 and 1. For the remaining parameters, the protocol may define three different presence requirements: 0 (mandatory), & (conditional) or 2 (optional). An M-parameter must always be included in a message of a given type; its absence is reason enough for the receiver to reject the whole message. A C-parameter must be present under certain conditions, but can be absent under other conditions. An O-parameter, finally, is never bound to be present; its absence is never sufficient reason for the receiver to reject the message.
3-72
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
Transaction identifier or Skip indicator
Protocol discriminator
TIflag
TI-Value
Protocol discriminator Message type
N(SD)
Message Type
Fig. 28 Layer 3 message header (GSM 04.07)
Value 0110 0101 0011 1011 1001 1111
Layer 3 part Radio Resource Management (RR) Mobility Management (MM) Call Control (CC) Supplementary Services Support (SSS) Short Message Service (SMS) reserved for tests
Fig. 29 Protocol discriminator
A30808-X5226-C559-1-7618
3-73
Siemens
Air Interface Um
Some examples of layer 3 messages will now be examined. First we shall consider a Radio Resource Management message the "Handover Command" from Base Station to Mobile Station. Apart from the parameters in the message header, the mandatory parameters are the description of the new cell (Cell Description), the specification of the new speech channel (Description of the First Channel) and the required power of the Mobile Station in the new cell (Power Command). Several conditional and optional parameters exist which depend on the cell synchronization or on whether frequency hopping is employed in the new cell. The length specifications indicate the total parameter lengths, i.e. inclusive of identifier and length indicator, where applicable. Thus, V-parameters have the length 1/2 or an integer value. With TV-parameters, the length is 1 if they have 1/2 byte contents and 1/2 byte identifier; otherwise, the length of the contents is 1 byte less than the indicated length (because the first byte is the IEI). T-parameters always have a length of 1 byte. LV-parameters have a length of the contents which is 1 byte less than the indicated length (here, the first byte is the length indicator). Finally, with TLV-parameters, the length of the contents is 2 bytes less than the indicated length, since the first byte is the IEI and the second byte is the length indicator. For example, the parameter "Real Time Difference" (TLV) has a total length of 3 bytes. When 1 byte is subtracted for identifier and length indicator respectively, 1 byte remains for the content.
3-74
A30808-X5226-C559-1-7618
Air Interface Um
Siemens

&DOO 6HTXHQFHV RQ 8P
&RPSOHWH 6HTXHQFHV
Our consideration of a ORFDWLRQ XSGDWH will be confined to the following case: a Mobile Station, which is in service but without an existing user connection, changes its location area. As soon as the Mobile Station has tuned itself to the new Base Station and recognizes the new LAI in the BCCH, it requests (via the RACH) a signaling channel (SDCCH). After being assigned a signaling channel (in the AGCH), the Mobile Station sets up a layer 2 connection with the "Contention Resolution" procedure, including in the SABM the layer 3 message "Location Update Request" along with the old CKSN, the prior TMSI and previous LAI. The Mobile Station additionally indicates that the requested location update is a normal one (and not a periodic one or an IMSI Attach). The Base Station acknowledges the SABM with UA. The VLR determines the IMSI on the basis of the TMSI and LAI (and possibly by querying the previous VLR), and notifies (if necessary) the HLR. Before confirming the location update and assigning a new TMSI to the Mobile Station, the VLR performs the authentication (I-frames "Authentication Request" and "Authentication Response") and the ciphering activation (I-frames "Ciphering Mode Command" and "Ciphering Mode Complete"). After this, a new TMSI can be allocated with the enciphered message "Location Update Accept"; the Mobile Station responds with "TMSI Reallocation Complete". The Base Station then clears down the RR connection.
A30808-X5226-C559-1-7618
3-75
Siemens
Air Interface Um
Location update
RACH
Channel Request (Reason = Loc. Upd., Random Reference) UI (Immediate Assignment) (Request Reference, SDCCH-No.) SABM (Location Update Request) (TMSI + old LAI, CKSN, loc upd. type) UA I (Authentication Request) (RAND, CKSN) I (Authentication Response) (SRES) I (Ciphering Mode Command) I (Ciphering Mode Complete) I (Location Update Accept) (new TMSI, new LAI) I (TMSI Reallocation Complete) I (Channel Release)
AGCH
SDCCH
SDCCH SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
DISC UA
SDCCH
Fig. 30 Location Update
3-76
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
For a PRELOH RULJLQDWLQJ FDOO (MOC) we will consider the case that a Mobile Station, whose current location is already updated, sets up an outgoing call. Therefore, a location update with directly following MM connection set up is not required first of all; instead, a RR connection must be set up specifically for the MOC. For this, the Mobile Station requests a SDCCH (in the RACH; reason for request = MOC set up). After allocation of the SDCCH (via the AGCH), the Mobile Station sets up the layer 2 connection and conveys in the SABM the message "CM Service Request", which includes the CKSN of the last authentication and the information that a MM connection for call control (CC) is to be set up. The Base Station acknowledges the SABM with UA. The Base Station now performs the authentication (I-frames "Authentication Request" and "Authentication Response") and ciphering activation (I-frames "Ciphering Mode Command" and "Ciphering Mode Complete"). With this, the MM connection is set up and the Mobile Station for its part can establish a CC connection with the message "Setup". This message contains a new transaction identifier (TI; selected by the Mobile Station) as well as all information required for a network call set up (in particular the bearer capability and the called party number). The Base Station answers with the I-frame "Call Proceeding", to which the Mobile Station responds with "Receive Ready".
A30808-X5226-C559-1-7618
3-77
Siemens
Air Interface Um
0RELOH RULJLQDWLQJ FDOO 02& EHJLQQLQJ
RACH
Channel Request (Reason = MOC, Random Reference) UI (Immediate Assignment) (Request Reference, SDCCH-No.)
AGCH
SDCCH
SABM (CM Service Request) (CC, CKSN) UA
SDCCH SDCCH
I (Authentication Request) (RAND, CKSN)
SDCCH
I (Authentication Response) (SRES) I (Ciphering Mode Command)
SDCCH
SDCCH
I (Ciphering Mode Complete) Receive Ready
SDCCH
SDCCH
I (Setup) (bearer capability, compatibility, called party number, features) I (Call Proceeding) Receive Ready
SDCCH
SDCCH
Fig. 31 Mobile originating call, part 1
3-78
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
At this stage, if Off-Air Call Set up (OACSU) is not active, the network side assigns a speech channel by sending an "Assignment Command" I-frame with the TCH number. The Mobile Station responds with "Receive Ready", whereupon the layer 2 connection in the SDCCH can be cleared down locally, and a new layer 2 connection is set up in the FACCH. The Mobile Station uses this new FACCH to acknowledge the received "Assignment Command" with "Assignment Complete". As soon as ringing begins for the called party, the network side sends to the Mobile Station the I-frame "Alerting", to which the Mobile Station responds with "Receive Ready". Once the called party answers, the network side sends the I-frame "Connect" to the Mobile Station; the latter responds with I-frame "Connect Acknowledge". Finally, the Base Station acknowledges the MS response with "Receive Ready", thus completing the connection set up.
A30808-X5226-C559-1-7618
3-79
Siemens
Air Interface Um
0RELOH RULJLQDWLQJ FDOO 02& FRQWLQXDWLRQ ZLWKRXW 2$&68
I (Assignment Command) (TCH-No.)
SDCCH
SDCCH FACCH
Receive Ready SABM UA
FACCH
FACCH
I (Assignment Complete) Receive Ready I (Alerting) Receive Ready I (Connect) I (Connect Acknowledge) Receive Ready
FACCH FACCH
FACCH
FACCH
FACCH
FACCH
Fig. 32 Mobile originating call, part 2a
3-80
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
If Off-Air Call Set up (OACSU) is active, the speech channel is first assigned when the called party answers (i.e. directly before the "Connect"). The transmission of "Alerting" and the associated "Receive Ready" continues in the SDCCH.
A30808-X5226-C559-1-7618
3-81
Siemens
Air Interface Um
0RELOH RULJLQDWLQJ FDOO 02& FRQWLQXDWLRQ ZLWK 2$&68
I (Alerting) Receive Ready I (Assignment Command) (TCH-No.)
SDCCH
SDCCH
SDCCH
SDCCH FACCH
Receive Ready
SABM UA I (Assignment Complete) I (Connect) I (Connect Acknowledge) Receive Ready
FACCH
FACCH
FACCH
FACCH
FACCH
Fig. 33 Mobile originating call, part 2b
3-82
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
The Base Station initiates a PRELOH WHUPLQDWLQJ FDOO (MTC) by paging. For this, it sends in the PCH a UI-frame "Paging Request" including the TMSI. The called Mobile Station requests ("Channel Request" in RACH, Reason = Answer to paging) and obtains ("Immediate Assignment" in AGCH) a channel, in which it sets up a layer 2 connection. The SABM for this set up includes the message "Paging Response" along with the last CKSN and the TMSI. The network recognizes the positive paging result and answers the SABM with UA. The Base Station now performs the authentication (I-frames "Authentication Request" and "Authentication Response") and ciphering activation (I-frames "Ciphering Mode Command" and "Ciphering Mode Complete"). With this, the MM connection is set up and the Base Station can establish a CC connection with the message "Setup". This message contains a new transaction identifier (TI; selected by Base Station) as well as all information required for a call set up (in particular the bearer capability). The Mobile Station answers with the I-frame "Call Confirmed", to which the Base Station responds with "Receive Ready".
A30808-X5226-C559-1-7618
3-83
Siemens
Air Interface Um
0RELOH WHUPLQDWLQJ FDOO 07& EHJLQQLQJ
UI (Paging Request) (Mobile Identity)
PCH
RACH
Channel Request (Reason = Answer to Paging, Random Reference) UI (Immediate Assignment) (Request Reference, SDCCH-No.) SABM (Paging Response) (TMSI, CKSN) UA
AGCH
SDCCH
SDCCH SDCCH
I (Authentication Request) (RAND, CKSN)
SDCCH
I (Authentication Response) (SRES) I (Ciphering Mode Command) I (Ciphering Mode Complete) I (Setup) (bearer capability, compatibility, calling party number, features)
SDCCH
SDCCH
SDCCH
SDCCH
I (Call Confirmed) Receive Ready
SDCCH
Fig. 34 Mobile terminating call, part 1
3-84
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
If Off-Air Call Set up (OACSU) is not active, the Base Station assigns the speech channel at this point. The procedure is identical with that for a mobile originating call (see above). Most importantly, the remaining RR connection in the SDCCH is replaced by a new one in the FACCH. As soon as ringing begins for the called party, the Mobile Station sends the I-frame "Alerting", to which the Base Station responds with "Receive Ready". If the called party answers, the Mobile Station notifies the Base Station with the Iframe "Connect". The Base Station responds with "Connect Acknowledge". Finally, the Mobile Station acknowledges the Base Station response with "Receive Ready", thus completing the connection set up for a mobile terminating call.
A30808-X5226-C559-1-7618
3-85
Siemens
Air Interface Um
0RELOH WHUPLQDWLQJ FDOO 07& FRQWLQXDWLRQ ZLWKRXW 2$&68
I (Assignment Command) (TCH-No.)
SDCCH
SDCCH FACCH
Receive Ready SABM UA
FACCH
FACCH
I (Assignment Complete) Receive Ready I (Alerting) Receive Ready I (Connect) I (Connect Acknowledge) Receive Ready
FACCH
FACCH
FACCH
FACCH
FACCH
FACCH
Fig. 35 Mobile terminating call, part 2a
3-86
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
If Off-Air Call Set up (OACSU) is active, the speech channel is first assigned when the called party answers (i.e. after the "Connect"). The transmission of "Alerting", the associated "Receive Ready", and "Connect" continue in the SDCCH.
A30808-X5226-C559-1-7618
3-87
Siemens
Air Interface Um
0RELOH WHUPLQDWLQJ FDOO 07& FRQWLQXDWLRQ ZLWK 2$&68
SDCCH
I (Alerting) Receive Ready I (Connect) I (Assignment Command) (TCH-No.)
SDCCH
SDCCH
SDCCH
SDCCH FACCH
Receive Ready SABM UA I (Assignment Complete) I (Connect Acknowledge) Receive Ready
FACCH
FACCH
FACCH
FACCH
Fig. 36 Mobile terminating call, part 2b
3-88
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
From the view of the Mobile Station, the +DQGRYHU procedure begins when the Base Station sends an I-frame with a "Handover Command" message in the FACCH valid up to that point. The message contains specifications of the new cell (e.g. color code, channel structure, timing advance), of the new speech channel (TCH) and a new Handover reference number. The Mobile Station acknowledges this I-frame with "Receive Ready". With this, the layer 2 connection in the remaining FACCH is cleared down locally. The old speech channel (TCH), together with its associated signaling channels (FACCH and SACCH), is now idle once more. The Mobile Station now logs-on in the new cell by transmitting four separate "Handover Access" messages in the FACCH of the new TCH. This message does not conform to the standard format of 23 Byte length; it is one byte long and comprises only the Handover reference number. The Mobile Station subsequently sets up with SABM the layer 2 connection in the new FACCH and, after receiving the UA, transmits the message "Handover Complete" in the first I-frame to the new Base Station. This Base Station responds with "Receive Ready". From the viewpoint of the Mobile Station, the handover is now completed.
A30808-X5226-C559-1-7618
3-89
Siemens
Air Interface Um
+DQGRYHU
I (Handover Command) (data about new cell, new TCH-No., handover reference)
FACCH old
FACCH old FACCH new FACCH new FACCH new FACCH new FACCH new
Receive Ready
Handover Access (Handover Reference) Handover Access (Handover Reference) Handover Access (Handover Reference) Handover Access (Handover Reference) SABM UA
FACCH new
FACCH new
I (Handover Complete) Receive Ready
FACCH new
Fig. 37 Handover
3-90
A30808-X5226-C559-1-7618
Air Interface Um
Siemens
The FDOO FOHDUGRZQ can be initiated by either the Mobile Station or network side (i.e. the partner side). Here, only the cleardown of an established useful connection will be considered. If the Mobile Station initiates the cleardown, it sends the I-frame "Disconnect". The Base Station responds by clearing down the CM connection with the I-frame "Release", which is answered by "Release Complete". If the partner side initiates the cleardown, the Base Station transmits "Release" immediately. Again, the Mobile Station answers with "Release Complete". The MM connection is cleared down only locally. The RR connection, however must be cleared down explicitly. The Base Station must initiate the RR cleardown (irrespective of the initiating side for the user connection cleardown) by sending the Iframe "Channel Release". Finally, the Mobile Station clears down the layer 2 connection with DISC, which the Base Station acknowledges with UA. With this, all seized resources are released, and the connection cleardown is completed.
A30808-X5226-C559-1-7618
3-91
Siemens
Air Interface Um
&DOO FOHDUGRZQ
,QLWLDWHG E\ PRELOH VWDWLRQ
FACCH
I (Disconnect)
I (Release) I (Release Complete) I (Channel Release)
FACCH
FACCH
FACCH
FACCH
DISC UA
FACCH
,QLWLDWHG E\ SDUWQHU VLGH I (Release) I (Release Complete) I (Channel Release) DISC UA
FACCH
FACCH
FACCH
FACCH
FACCH
Fig. 38 Call clear down
3-92
A30808-X5226-C559-1-7618
Interface Abis
Siemens
,QWHUIDFH $ELV
&RQWHQWV
1 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 2 2.1 2.2 3 3.1 3.2 3.3 Layer 1 Structure of the 2 Mbit/s Frame according to CCITT Recommendation G.704 Structure of the Signaling Pulse Frame according to CCITT Recommendation G.704 CRC4-Synchronization for Primary Multiplexer Alarms PCM Transmission Systems Baseband Transmission of Digital Signals Interface Codes Reasons for Bit Errors Layer 2 on Abis (LAPD) Structure of a LAPD Frame (Modulo 128) on Abis Layer 2 Parameters Layer 3 on Abis Layer 3 on RSL (SAPI 0) Layer 3 Parameters Layer 3 on O&M Link (SAPI 62) 3 3 5 7 9 11 13 15 19 23 24 25 32 32 33 35
A30808-X5226-C559-1-7618
4-1
Siemens
Interface Abis
4-2
A30808-X5226-C559-1-7618
Interface Abis
Siemens
/D\HU
The Abis interface is physically a 2 Mbit PCM System with 16 kbit/s subchannels. These 16 Kbit/s subchannels can be used for signaling and speech. The 16 kbit/s speech information will be transformed in the TRAU to 64 kbit/s.

6WUXFWXUH RI WKH 0ELWV )UDPH DFFRUGLQJ WR &&,77 5HFRPPHQGDWLRQ *
0ELWV3XOVH IUDPH In the direction of transmission the primary multiplexer PCM30 transforms up to 30 signals with different features into 64-kbit/s-digital signals and then combines them by the time division multiplexing procedure to a 2048-kbit/s (2-Mbit/s)-signal. The individual signals can be either LF-speech signals converted by pulse code modulation, or digital signals (e.g. data). In the receive direction a demultiplexer isolates the individual signals out of the 2 Mbit/s signal. The 64-kbit/s-digital signals are then converted again into analog signals. The 2-Mbit/s pulse frame accord. to CCITT-recommendation G.704 consists of 32 time intervals with 8 bits each (octets). In the intervals 1 to 15 and 17 to 31 speech or digital signals are transmitted. Interval 16 contains the channel-associated signaling information (CAS) combined in one multiframe or, optionally, an additional devicespecific data channel. In the interval 0 there is an alternate transmission of a frame alignment signal (FAS) or a service word (SVW). In order to isolate the individual signals out of the pulse frame the FAS is searched for in the received 2-Mbit/s-signal. As soon as the bit pattern is recognized, the demultiplexer part of the central multiplexer synchronizes itself to time interval 0. To additionally ensure the synchronization the CRC4-procedure is applied. The service word is used for the transmission of urgent and non-urgent alarms (bit A and bit Sa4), for loop commands (bits Sa6 and Sa7) (CCITT-Redbook: bits D, N and Y1 to Y3).
A30808-X5226-C559-1-7618
4-3
Siemens
Interface Abis
125 s Coded telephone signals 1 to 15 or digital signals 1 to 15 Signaling information or digital signal channels 31 Coded telephone signals 16 to 30 or digital signals 16 to 30
Time slots
15 16 17
30 31
8 bits
X 0 0 1 1 0 1 1
Frame alignment signal in frames 1, 3, 5 ... 15 Service word in frames 0, 2, 4 ... 14
X 1 D
N Y
Y Y Y Y
D X Y
Fig. 1
= = =
Service bit for urgent alarm Bits reserved for international use Bits reserved for national use
4-4
A30808-X5226-C559-1-7618
Interface Abis
Siemens

6WUXFWXUH RI WKH 6LJQDOLQJ 3XOVH )UDPH DFFRUGLQJ WR &&,77 5HFRPPHQGDWLRQ *
6LJQDOLQJ SXOVH IUDPH If analog signal insets are used the PCM30 transmits up to 30 speech signals in the time intervals 1 to 15 and 17 to 31 of the 2-Mbit/s-pulse frame. It has to be ensured that the 64-kbit/s-signals in the time intervals 17 to 31 are counted as channels 16 to 30. The individual channel-associated signaling information is coded with 4 bits (a, b, c, d) separate from the speech signal. The signaling of 30 channels can therefore be combined in 15 octets, which are supplemented by a code and service word of 8 bits, to a multiframe (signaling pulse frame). This multiframe is transmitted in time interval 16 by 16 consecutive 2-Mbit/s-pulse frames (R0 to R15). The code and service word contained in interval R0 is necessary for the multiframe synchronization and for alarm messages.
A30808-X5226-C559-1-7618
4-5
Siemens
Interface Abis
PCM30 time slots 125 s PCM pulse frame No. 0 0 1 16 31 0 1 No. 8 16 31 0 1 No. 15 16 31
2 ms signaling pulse frame
Signaling time slots
14 15
0 0 0 0 1 DK 1 1 Signaling frame alingment signal Signaling service word
a b c d a b c d Channel 8 Channel 23
a b c d a b c d Channel 15 Channel 30
Signaling words
Signaling words
D = Service bit for urgent alarm a, b, c, d = Signaling bits in a signaling word
D a, b, c, d
Fig. 2
Service bit for urgent alarm Signaling bits in a signaling word
4-6
A30808-X5226-C559-1-7618
Interface Abis
Siemens

&5&6\QFKURQL]DWLRQ IRU 3ULPDU\ 0XOWLSOH[HU
With the data transmission of synchronous 64 kbit/s digital signals it is possible that the bit patterns of the FAS and the SVW are transmitted (either randomly or on purpose) in the time intervals defined for user signals. If there is a synchronization of the receive side demultiplexer to this bit pattern, an isolation of the individual signals is impossible. Therefore, the CRC4-procedure (Cyclic Redundancy Check by 4 bits) described in CCITT-recommendation G.704 is used in addition, to ensure the synchronization. For this, 16 consecutive 2-Mbit/s frames are combined to a CRC4 multiframe consisting of 2 data blocks and of the multiframe parts I and II. The highest rating bits of the service words in the first twelve 2-Mbit/s frames form the multiframe code word (001011). Here, the synchronization is based on two criteria: finding the FAS of the 2-Mbit/s frame and the FAS of a CRC4 multiframe. To continually supervise the synchronization, a data block (e.g. block I) is modified in a data transmitter accord. to a certain algorithm, whereby a rest of 4 bits (the control bits C1 and C4) is left over. These bits are transmitted as highest rating bits in the 2Mbit frame alignment words of the IROORZLQJ data block (block II). The data receiver processes the incoming data block according to the same algorithm as the transmitter. Again, a rest of 4 bits is left over, which are compared individually to the control bits received in the next data block (block II). In case of a correspondence, block I is considered to be error-free. If 915 or more out of 1000 checked blocks were found to be faulty, a new synchronization is started. A CRC4-error is indicated by two E-bits (CCITT-Redbook: Si-bits) at the transmit side; these two E-bits are transmitted as highest rating bits of the service words in the 2-Mbit/s frames 13 and 15 of the CRC4 multiframe. The BER of the 2-Mbit/s-signal can be derived from the number of faulty blocks. Thus, for example, a number of 512 or more faulty blocks within a measuring interval of 1 s results in a BER > 10-3.
A30808-X5226-C559-1-7618
4-7
Siemens
Interface Abis
2-Mbit/s-frame 32 x 8 bits = 256 bits telephone or data time slots signaling information telephone or data
0 1 2
15 16 17
30 31
X 0 0
1 1 0 1 1
alternating
frame alignment signal FAS
X 1 D N/Y Y Y Y Y
bit position 1 2 3 4 5 6 7 8
service word SW
16 (2-Mbit/sframe)
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
C1 0 C2 0 C3 1 C4 0 C1 1 C2 1 C3 E C4 E
0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1
0 D 0 D 0 D 0 D 0 D 0 D 0 D 0 D
1 N/Y 1 N/Y 1 N/Y 1 N/Y 1 N/Y 1 N/Y 1 N/Y 1 N/Y
1 Y 1 Y 1 Y 1 Y 1 Y 1 Y 1 Y 1 Y
0 Y 0 Y 0 Y 0 Y 0 Y 0 Y 0 Y 0 Y
1 Y 1 Y 1 Y 1 Y 1 Y 1 Y 1 Y 1 Y
1 Y 1 Y 1 Y 1 Y 1 Y 1 Y 1 Y 1 Y
FAS SW FAS SW FAS SW FAS SW FAS SW FAS SW FAS SW FAS SW
multiframe part I
CRC4multiframe MFR
multiframe part II
C1 to C4 (X) E
Fig. 3
2-Mbit/s-frame mark, FAS CRC4-multiframe codeword (X) CRC4-control bits D CRC4-service bits for the N/Y reporting of CRC4-errors
service bit for urgent alarm service bit for non-urgent alarm
4-8
A30808-X5226-C559-1-7618
Interface Abis
Siemens

$ODUPV
$,6 $ODUP ,QGLFDWLRQ 6LJQDO The AIS signal is an "all-one-signal" which, if an error occurs, is inserted as replacement signal only in forward direction.
'%LW If the counterpart gets no signal, a remote alarm is indicated.
A30808-X5226-C559-1-7618
4-9
Siemens
Interface Abis

4-10
A30808-X5226-C559-1-7618
Interface Abis
Siemens

3&0 7UDQVPLVVLRQ 6\VWHPV
The transmission systems recommended by the CCITT and described below are the PCM30 system, with 2048 kbit/s (CCITT Recommendation G.732), and the PCM24 system, with 1544 kbit/s (CCITT Recommendations G.733); these combine 30 and 24 telephone channels per transmission direction respectively to form a time-division multiplex signal. PCM30 transmission systems are used throughout Europe and in many non-European countries; PCM24 transmission systems have been installed mainly in the USA, Canada and Japan. PCM30 and PCM24 are also known as "primary transmission systems" or basic systems.
A30808-X5226-C559-1-7618
4-11
Siemens
Interface Abis
Common characteristics a b Sampling frequency No. of samples per telephone signal Pulse frame period No. of bits in a PCM word Bit rate of a telephone channel
PCM30 and PCM24 8 kHz 8.000/s

= = V E V
c d e
8 bits b.d.=8.000/s 8bits=64kbit/s PCM30 PCM24 -law 15
System-specific characteristics Encoding/Decoding No. of segments in characteristic Number of channel time slots per pulse frame Number of bits per pulse frame (* = additional bit) Period of an 8-bit channel time slot
A-law 13
g h
32 d.g. = 8 bits 32 = 256 bits

FG V = K
24 d.g. + 1* = 8 bits 24 + 1* = 193 bits

FG V = K
aprox. 3.9 s k Bit rate of time division mulitplex signal b.h. = 8.000/s. 256 bits = 2.048 kbit/s
aprox. 5.2 s b.h. = 8.000/s.193 bits = 1.544 kbit/s
Fig. 4 Characteristics of the PCM30 and PCM24 Transmission Systems
4-12
A30808-X5226-C559-1-7618
Interface Abis
Siemens

%DVHEDQG 7UDQVPLVVLRQ RI 'LJLWDO 6LJQDOV
Digital signal devices process the signals as purely binary information, i.e. the signal level does not change between bits with the same logical state. For this reason, these so-called NRZ signals (no return to zero) can only be processed together with the corresponding clock, which enables the identification of individual bit positions. This separate clock is not available for the transmission of data signals and thus it has to be possible to derive (i.e. regenerate) the clock from the data signal on the receiving side. It is obvious that for a NRZ code this is very complicated, if not virtually impossible. A further disadvantage of the NRZ code is that it carries a certain amount of dc-voltage which excludes the signals galvanic isolation at the interface (transformer etc.). Due to these disadvantages, various interface codes have been developed, all of which comply with the following requirements:
z z
good clock retrieval features no dc-component
A30808-X5226-C559-1-7618
4-13
Siemens
Interface Abis
1 bit
NRZSignal Clock Binary information 1 1 1 0 0 0 1 0 1 1 0 0
Fig. 5 Processing of NRZ signals with the aid of separate clock

4-14
A30808-X5226-C559-1-7618
Interface Abis
Siemens

,QWHUIDFH &RGHV
A suitable interface code has a maximum of transitions between the different signal levels, even for the transmission of lengthy sequences of identical logical states; it has no dc-component. The survey shows the development of individual codes. RZ Code A log. 1 is represented as half-bit with a change of signals levels from Low High Low. Advantage: clock retrieval possible also for adjacent log. 1 bits.
Disadvantage: no clock information for zero sequences, dc-component. AMI Code The state log. 1 is represented alternately as positive or negative signal level. Advantage: clock retrieval possible also for adjacent log. 1 bits, no dc-component.
Disadvantage: no clock information for zero sequences HDB3 Code Is derived from the AMI code. Here, four consequent zero bits are replaced by a 1001 or 0001 combination. This is done in such a way that the signal receiver detects the mutilation of informational contents and cancels it. Advantage: Maximum clock information, no dc-component. Disadvantage: None This code is applied for the device interfaces from 2 Mbit/s up to 34 Mbit/s (baseband transmission). The exact coding rules are enumerated in the following. CMI Code Due to its easy generation with delay lines and simple gate functions the CMI code is suited especially for interfaces with high bitrates. Therefore, this code is standardized for the 140 Mbit/s device interface.
A rather important advantage of the interface code is the possibility it offers to detect transmission errors by supervising the coding rules. With the HDB3 code, for example, the receiving of four zero bits would represent the violation of a coding rule, i.e. at least one bit error must have been occurred during transmission. The standardization of interface codes only refers to device interfaces. The codes for conductor-bound transmission paths are manufacturer-dependent and are generally adapted to the requirements of the respective terminating unit.
A30808-X5226-C559-1-7618
4-15
Siemens
Interface Abis
'LJLWDO ,QWHUIDFH &RGHV
Clock NRZ Binary RZ Binary
AMI
HDB3
CMI
Fig. 6

4-16
A30808-X5226-C559-1-7618
Interface Abis
Siemens
+'%&RGLQJ UXOHV 7KLUG2UGHU+LJK'HQVLW\%LSRODU&RGH The HDB3-code is a modified version of the AMI-code. Binary signals or AMI-code signals may contain lengthy "0" sequences, which hinder the clock retrieval in the regenerative repeaters along digital transmission paths. The HDB3 code enables the elimination of "0" sequences with more than 3 zeros. 1. If there are more than 4 consecutive "0"-signal elements, the fourth "0"-signal element shall be replaced by a V-signal element (= "1"-signal element) (000V). Hereby, the V-signal element takes on the same polarity as the "1"-signal element. A V-signal element causes a Violation of the AMI-rule. 2. If between the V-signal element, inserted according to the conditions specified above (rule 1), and the preceding V-signal element there is an even number of "1"signal elements, then the first of four "0"-signal elements shall be replaced by an Asignal element (= "1"-signal element). The polarity of the A-signal element complies with the AMI rule. The last of four "0"-signal elements becomes again a V-signal element (A00V). In this case the A- and V-signal elements have the same polarity.
A30808-X5226-C559-1-7618
4-17
Siemens
Interface Abis
1 binary
V V 0 HDB3
previous V-bit
rule 1 applies rule 2 does not apply
1 binary
A V
V 0 HDB3
previous V-bit
rule 1 and 2 apply
Fig. 7 Transformation of two binary signals into HDB3-signals
4-18
A30808-X5226-C559-1-7618
Interface Abis
Siemens

5HDVRQV IRU %LW (UURUV
The decisive quality criteria for the transmission of digital signals is the bit error rate (BER). This BER represents the proportion of bits which have been mutilated (i.e. incorrectly recorded) during transmission, to the total amount of bits transmitted within a certain interval. The BER directly influences the quality of the transmitted services (e.g. voice channels, data channels, video signals). Two significant BER are explained exemplary in the following:
z
BER = 10-6 This BER virtually cannot be perceived in a voice channel. For the transmission of data channels, however, this value represents the maximum acceptable limit. The transmission system is in a state of "degraded quality", which is indicated by a degradation alarm (low priority) on the devices involved. The transmission path remains, nevertheless, in operation.
BER = 10-3 This BER causes a strong interference noise in a voice channel. The operating state is judged to be of "unacceptable quality", which is signaled by the devices involved by the emission of a failure alarm (high priority). The transmission path goes out of operation.
+RZ GR ELW HUURUV DULVH" In the previous section it was mentioned that digital signals can be regenerated as requested, i.e. a transmission without quality reduction is possible. This statement is, however, only partially true, i.e. whenever the impairment of the transmission signals is within limits which still permit the regeneration at the receiving side. The reasons for the formation of bit errors are
z z z
low signal/noise ratio jitter intersymbol interference
/RZ VLJQDOQRLVH SURSRUWLRQ Noise amplitudes which influence the amplitude decision process are superimposed to the originally sent signal. The superimposed interference peaks lead to an incorrect signal interpretation at the receiving end. Reasons for a low S/N-ratio are: a) too strong signal attenuation during transmission b) external interference during transmission. For transmission in cable sections (especially optical fiber) both reasons can be largely eliminated by careful planning.
A30808-X5226-C559-1-7618
4-19
Siemens
Interface Abis
Decision treshold
Fig. 8 Low S/N-proportion

4-20
A30808-X5226-C559-1-7618
Interface Abis
Siemens
-LWWHU Due to jitter, the transitions between signal levels log. 0 and log. 1 do not take place at periodically recurring points in time (characteristically moments) as for undisturbed signals, which means that the transitions oscillate around the characteristically moments. Jitter is characterized by jitter amplitude (unit intervals UI) and jitter frequency. One UI means that, because of deviation from the characteristically moments, the signal edges are within a range equal to the width of 1 bit. The jitter frequency is the number of oscillations around the characteristically moment per one second. Jitter influences the time decision process in the regenerator and causes bit errors for high jitter amplitudes and frequency. Jitter arises in the devices used for signal transmission (i.e. in regenerators and demultiplexers = systematically jitter), or on the transmission path due to external influences (non-systematic jitter). ,QWHUV\PERO LQWHUIHUHQFH Is caused by a discrepancy between the band width of the transmission path and the bandwidth required for the digital signal. This leads to a bit extension, so that there is an overlap of bits which follow each other. Thus, bit errors occur, the reasons of which can be traced back to the impairment of amplitude decision process. For conductor-bound transmission of digital signals this effect can be excluded by adequate planning. For transmission on radio paths this effect is of fundamental importance as the frequency response of the transmission path can change due to atmospherically influence.
A30808-X5226-C559-1-7618
4-21
Siemens
Interface Abis
signal without jitter
premature occurence of signal edge (+T/2)
characteristical moment T
Fig. 9 Representation of an Unit Interval (UI)
late occurence of signal edge (-T/2)

4-22
A30808-X5226-C559-1-7618
Interface Abis
Siemens
/D\HU RQ $ELV /$3'
The layer 2 is the so called Link Layer and uses LAPD protocol (Link Access Protocol for the D-Channel) on Abis. The main task of layer 2 is to realize a safe transmission. This is achieved e.g. by:
z z z z
Introduction of a frame structure (LAPD Frames) Acknowledgement of received messages Check of counters (send and receive number) Building of checksums
A30808-X5226-C559-1-7618
4-23
Siemens
Interface Abis

6WUXFWXUH RI D /$3' )UDPH 0RGXOR RQ $ELV

7 6 5 4 3 2 1 0 Bit-No
1 C/R
0 EA
opening flag
SAPI TEI N(S) N(R)
address field EA 0 P control field of an information frame
Layer 3 data (max. 260 octets)
FCS frame check sequence FCS 0 1 1 1 1 1 1 0 closing flag
Fig. 10 LAPD frame on Abis
4-24
A30808-X5226-C559-1-7618
Interface Abis
Siemens

/D\HU 3DUDPHWHUV
RSHQLQJ IODJ FORVLQJ IODJ The opening / closing flag indicates the beginning / end of a LAPD frame.
($ ELWV In the first octet of the address field EA=0. In the second (=last) octet of the address field EA=1.
&5 ELW Command/Response bit.
User Side: BTSE
Network Side: BSC
ITU-T BSS
C=1 BTSE R=1 BSC
C=0 BTSE R=0 BSC
Fig. 11 Usage of the command/response bit on Abis
A30808-X5226-C559-1-7618
4-25
Siemens
Interface Abis
6$3, Service Access Point Identifier. The SAPI value indicates whether the signaling message is a radio signaling link message, or an O&M message, or a Layer 2 Management message. 6$3, 0 62 63 3ULRULW\ 2 (=low) 1 (=high) 1 (=high) 0HDQLQJ radio signaling link O&M messages Layer 2 Management
It should be emphasized that the SAPI values on Abis are not the same as the SAPI values used on Um.
7(, Terminal Endpoint Identifier. With the help of the TEI, several functional same units (e.g. several TRX) can be distinguished.
4-26
A30808-X5226-C559-1-7618
Interface Abis
Siemens
16 15 Send Number / Receive Number. N(S) and N(R) are counter values and allow the acknowledged transmission and reception of information frames. N(S) of the received I-frame must have the same value as the counter N(R) on the receiving side.
BTSE N(S) 01 1 1 1 1 1 1 N(R) 0 0 0 0 01 1 1

I-Frame N(S)=0/N(R)=0
BSC N(S) 0 0 0 01 1 1 1 N(R) 0 01 1 1 1 1 1
RR-Frame N(R)=1
I-Frame N(S)=0/N(R)=1
RR-Frame N(R)=1
Fig. 12 The principle function of the counters N(S) and N(R)
A30808-X5226-C559-1-7618
4-27
Siemens
Interface Abis
3)ELW Polling / Final bit. In command-frames: P/F bit = P. In response-frames: P/F bit = F. P-bit: The P-bit indicates whether or not the transmission side expects an acknowledgement on the transmitted messages, although the type of message would not require such an acknowledgement. If P=1: Frame must be acknowledged. If P=0: Frame must not be acknowledged. F-bit: If the receiving side receives a command frame with P=1, then the receive side must answer at once with a supervisory frame where F=1. )&6 Frame check sequence. The FCS is used for error detection. The bits of the address field, of the control field and of the layer 3 data are taken as input of a check sequence and the result is written into the FCS field. The transmission side evaluates the FCS and sends it to the receive side. The receive side also independently evaluates the FCS and compares its value with the received value. If both values differ, a retransmission of the frame is performed.
4-28
A30808-X5226-C559-1-7618
Interface Abis
Siemens
$GGLWLRQDO 5HPDUNV WR WKH FRQWURO ILHOG There are three different types of control fields:
z z z
information frames (I-frames) supervisory frames (S-frames) unnumbered frames (U-frames)
,QIRUPDWLRQ )UDPH N(S) N(R) 0 P
The information frame always is a command and is used e.g. for the transfer of layer 3 messages.
6XSHUYLVRU\ )UDPHV
z
55)UDPH: (Receive Ready) 0 0 0 0 N(R) 0 0 0 1 P/F
The receive ready frame is used e.g. to acknowledge the reception of an information frame.
z
515)UDPH: (Receive Not Ready) 0 0 0 0 N(R) 0 1 0 1 P/F
The receive not ready frame is used to indicate an overload state to the counterpart, i.e. it is not possible for the receive side to receive further I-frames.
z
5(-)UDPH: (Reject Frame) 0 0 0 0 N(R) 1 0 0 1 P/F
The reject frame is sent to indicate to the counterpart that a transmission error occurred (compare FCS) and that the I-frame has to be sent again.
A30808-X5226-C559-1-7618
4-29
Siemens
Interface Abis
8QQXPEHUHG )UDPHV The length of the control field of all unnumbered frames is only one octet.
z
6$%0()UDPH (Set Asynchronous Balanced Mode Extended) 0 1 1 P 1 1 1 1 SABME-frames are sent as long as a layer 2 connection is not established. For instance, if one measures SABME-frames on Abis, this may be an indication that between the BSC and minimum one TRX there is no layer 2 connection.
'0)UDPH (Disconnect Mode) 0 0 0 F 1 1 1 1 With the disconnect mode frame the send side indicates to the receive side that the layer 2 connection cannot be established any more. DM-frames will not be acknowledged.
8,)UDPH (Unnumbered Information) 0 0 0 P 0 0 1 1 Unnumbered information frames are used to transport messages containing measurement results.
',6&)UDPH (Disconnect) 0 1 0 P 0 0 1 1 Disconnect frames are used to clear down a layer 2 connection. The receive side must acknowledge such frames.
8$)UDPH (Unnumbered Acknowledgement) 0 1 1 F 0 0 1 1 Unnumbered acknowledgement frames are used to answer to SABME-frames and to DISC-frames, that means both the establishment and the clear down of a layer 2 message are confirmed with unnumbered acknowledgement frames.
4-30
A30808-X5226-C559-1-7618
Interface Abis
Siemens
)505)UDPH (Frame Reject) 1 0 0 F 0 1 1 1
The frame reject frame is sent if protocol errors appear, i.e. a message is faulty or unexpected and indicates that the counterpart or the transmission system has problems.
A30808-X5226-C559-1-7618
4-31
Siemens
Interface Abis
/D\HU RQ $ELV
In I-frames and UI-frames, a layer 3 information follows the layer 2 header. Depending on the SAPI value (62, 63 or 0) layer 3 uses different formats.

/D\HU RQ 56/ 6$3,

Layer 2
message discriminator message type channel number identifier channel number
8 bit 8 bit 8 bit 8 bit Layer 3 header
Layer 3 data field (GSM 04.08 data, RSL) (max. 255 octets)
Layer 3 Layer 3 data field
Layer 2
Fig. 13 Layer 3 on Abis (RSL)
4-32
A30808-X5226-C559-1-7618
Interface Abis
Siemens

/D\HU 3DUDPHWHUV
PHVVDJH GLVFULPLQDWRU This 1 octet field is used to discriminate between

z z
WUDQVSDUHQW messages QRQWUDQVSDUHQW messages radio link layer messages (5/0) dedicated channel management messages ('&0) common channel management messages (&&0) TRX management messages (75;0). RLM: 0 DCM: 0 CCM: 0 0 0 0 1 1 0 T 0 0 0 1 0 0 T 0 0 0 0 0 1 T
and also between

z z z z
TRXM: 0 0 0 1 0 0 0 T
The 7ELW is set to 1 to indicate that the message is a transparent message, i.e. the message is to be considered (was considered) transparent by the BTS. The T-bit is set to 0 for non-transparent messages. 5/0: Messages which are needed for the control of a layer 2 connection between MS and BTS. '&0: Messages which are needed for the control of layer 1 on air interface. &&0: Messages which carry common control channel data to/from air interface. 75;0: Messages which are needed for the TRX management.
A30808-X5226-C559-1-7618
4-33
Siemens
Interface Abis
PHVVDJH W\SH The message type uniquely describes the function of the layer 3 message being sent
FKDQQHO QXPEHU The channel number is used to indicate the channel type (SDCCH, BCCH, ...) and the timeslot and subslot which are used on air interface for a connection.
4-34
A30808-X5226-C559-1-7618
Interface Abis
Siemens

/D\HU RQ 2 0 /LQN 6$3,
On the O&M link manufacturer dependent solutions are visible. However, GSM 08.59 and GSM 12.21 offer some specifications. Usually during software transfer, a large amount of data must be transferred. Therefore it is necessary to segment the data and to give them a sequence number.
Layer 2
identifier placement sequence number length
8 bit 8 bit 8 bit 8 bit Layer 3 header
Layer 3 data field O&M data MMI data (max. 255 octets)
Layer 3 data field
Layer 2
Fig. 14 Layer 3 on Abis (O&M)
A30808-X5226-C559-1-7618
4-35
Siemens
Interface Abis
The identifier allows a differentiation between MMI and O&M messages. The placement parameter indicates whether or not the message consists of several segments. The sequence number allows a numbering of the single messages in case of multisegment messages. The length parameter indicates how many useful bytes the following layer 3 data field contains.
4-36
A30808-X5226-C559-1-7618
Siemens
$,QWHUIDFH6LJQDOLQJ 6\VWHP &&6
&RQWHQWV
1 1.1 1.2 1.3 2 3 4 4.1 4.2 4.3 Signaling System CCS7 Structure of the CCS7 Message Transfer Part MTP User Parts UP Complete Sequences Formatting Rules Appendix BSSMAP-Procedures K1103 Trace in Short Format K1103 Trace in Long Format 3 3 5 7 25 33 45 47 49 51
A30808-X5226-C559-1-7618
5-1
Siemens
5-2
A30808-X5226-C559-1-7618
Siemens
6LJQDOLQJ 6\VWHP &&6
CCS7 stands for Common Channel Signaling system No.7. CCS7 is a signaling system employing a common channel signaling link specified by the CCITT (Committee Consultative International Telephonic et Telegraphic). The common channel signaling link is a special communication channel between functional entities which is used specially for the exchange of signaling data. This data can be circuit-related (switching signaling e.g. ISDN-UP1) or not (transactions e.g. SCCP2, TCAP3). The CCS7 is characterized by high capacity and speed. It was originally developed for the ISDN fixed network and is also used in GSM-PLMNs between all components of the call switching subsystems SSS (i.e. on the interfaces B to G), between MSC and BSC (interface A) as well as in connections to external networks (other PLMNs, ISDN). Signaling may run via several intermediate stations. The air interface Um as well as the Abis and Asub interface have their own protocol procedure.

6WUXFWXUH RI WKH &&6
The signaling system CCS7 follows the OSI reference model (Reference Model of Open System Interconnection). However, instead of 7 layers as in the OSI layered model only 4 levels are specified in the CCS7. Only the first two levels of CCS7 are identical with the first two layers of the OSI model. With the CCS7 the system tasks can be divided into the levels 1-3 and the level 4:
z z
level 4 contains the WDVNVSHFLILF XVHU SDUWV or XVHU SDUWV 83 (comparable with layers 4 - 7 of the OSI model), levels 1 - 3 contain the 0HVVDJH 7UDQVIHU 3DUW 073.

,6'183 ,6'1 XVHU SDUW 6&&3 6LJQDOLQJ FRQQHFWLRQ FRQWURO SDUW WKH 6&&3 FDQ DOVR EH FLUFXLWUHODWHG HJ LQ FRQMXQFWLRQ ZLWK %66$3 7&$3 7UDQVDFWLRQ &DSDELOLWLHV $SSOLFDWLRQ 3DUW
A30808-X5226-C559-1-7618
5-3
Siemens
,6'183 /HYHO
6&&3 /HYHO
783 /HYHO
Example for user parts
6LJQDOLQJ OLQN IXQFWLRQV /HYHO
Message transfer part
Fig. 1 Functional levels of the CCS7

5-4
A30808-X5226-C559-1-7618
Siemens

0HVVDJH 7UDQVIHU 3DUW 073
The message transfer part MTP is a user-independent means of transport for messages between the (max. 14 defined) users and is formed from the following 3 levels:
/HYHO SK\VLFDO OD\HU

z z
defines the physical, electrical and functional features of the signaling link, is realized by PCM30 systems or individual 64kbit/s lines (ref. to layer 1 of AbisInterface).
/HYHO OLQN OD\HU

z
Level 2 of the MTP includes all functions and procedures for stable transmission of signaling messages via a single signaling link. It thus defines the connection between two individual points of the CCS7 network and is responsible for fault detection and rectification. The individual tasks are: Error detection, i.e. checking the delimitation of the messages (flag detection), monitoring the synchronization of the CSC4 terminal units as well as checking the contents of the received messages for transmission faults (check bits). Transmission control and reception control Link state control, i.e. monitoring and controlling the operating state of a CSC; activation (controlled by level 3) of disturbed CSC Congestion control, i.e. monitoring the receiving memory, transmission of an overload defense message to the partner terminal unit if necessary
z z z
/HYHO QHWZRUN OD\HU

z z
Message routing: involves the routing of messages to the right destinations. Operates "Network management", i.e. updates information on the state of the network, informs the user parts about the failure or re-availability of signaling connections or about overloading (MTP status message) and creates "diversions for the messages if parts of the network fail.
&RPPRQ 6LJQDOLQJ &KDQQHO &6&
A30808-X5226-C559-1-7618
5-5
Siemens
,6'183 /HYHO
6&&3 /HYHO
783 /HYHO
Example for user parts
Message transfer part
Fig. 2 Functional levels of the CCS7

5-6
A30808-X5226-C559-1-7618
Siemens

8VHU 3DUWV 83
8VHU 3DUWV *HQHUDO
The user parts (UP) encompass the functions, protocols and coding for signaling via the CCS7, for each user type (e.g. telephone call service, data service). The user parts control e.g. the circuit connection setup and release, the handling of services, as well as user channel administration and maintenance functions. A user part makes the following functions for the use of message transmission elements available for each defined user type:
z z z z
For telephone calls: Telephone User Part (TUP) For ISDN: ISDN User Part (ISDN-UP or ISUP) For signaling transactions: Signaling Connection Control Part (SCCP) For transaction processing: Transaction Capabilities Application Part (TCAP)
The following diagram shows the MTP users, as well as the relationship between one another and the MTP. The modular structure means that the CCS7 can be adapted to the set requirements; expansion for further installation is also possible. Each CCS7 user also has the option of specifying an individual user part (UP). The user part for mobile communication (MUP) is a Siemens own specification user part for the C450 mobile communication network, for example. The D900 PLMN internally uses the SCCP, and externally the ISDN UP or SCCP.
A30808-X5226-C559-1-7618
5-7
Siemens
CCS7 user
7&$3XVHU
7&$3
,6'183
783
RWKHU 073 XVHUV
6&&3
0HVVDJH WUDQVIHU SDUW 073
Fig. 3 Examples of User Parts (UP)

5-8
A30808-X5226-C559-1-7618
Siemens
The protocol architecture of the central signaling channels in the GSM system or those coming from it, is depicted as follows. The setup of the MTP, SCCP, TCAP, ISDN UP, MAP and BSSAP protocols is shown.
A30808-X5226-C559-1-7618
5-9
Siemens
%66$3
0$3
,6'183
7&$3
6&&3
073

Fig. 4 CCS7 Protocol Architecture in the D900

5-10
A30808-X5226-C559-1-7618
Siemens
All CCS7 user parts (UP) set up on the three message transfer part (MTP) levels. The Signaling Connection User Part (SCCP) forms the basis of all user parts, with the exception of ISDN user parts. The MTP forms the basis for ISDN user parts, which can only be used alone in order to control all other applications regarding communication, within the PLMN, between different PLMNs and to the fixed network (e.g. ISDN).

8VHU 3DUW IRU WKH &RQWURO RI 6LJQDOLQJ &RQQHFWLRQV 6&&3 6LJQDOLQJ &RQQHFWLRQ &RQWURO 3DUW
The SCCP completes the message transfer part (MTP), expands the MTP routing functions and the regulation points outside the respective signaling network and offers additional functions for message bearing. It coordinates all call paths, informs its user of CCS7 network errors (incl. subsystem errors of other exchanges) and forms the basis for all user parts (UP) in the digital switching network. The ISDN user part is an exception that can operate with, as well as without SCCP. The SCCP is established as a user part on level 4, yet it basically has level 3 functions (when compared to the OSI layer model). The SCCP forms the 1HWZRUN 6HUYLFH 3DUW 163 together with the MTP. The NSP enables the user to take advantage of IXUWKHU PHVVDJH WUDQVPLVVLRQ IXQFWLRQV and WUDQVPLVVLRQV VHUYLFHV, additional to the MTP functions. The VXSSOHPHQWDU\ WUDQVPLVVLRQ IXQFWLRQV can be separated into connection orientated and connectionless, they are divided into 4 protocol classes. The user can decide on a certain data transmission method and quality with this selection of classes. The service quality increases with the selected protocol class. &RQQHFWLRQ 2ULHQWHG &2 This function first creates a virtual signaling connection between the participating users, before transmitting their data. This corresponds to an "end to end" connection. The users determine the connection setup and release point. The messages contain a connection reference parameter with which they can be allocated to a specified virtual connection.
&RQQHFWLRQ/HVV &/ This function enables users in different switching centers to exchange data with each other without a connection reference (physical or virtual) having to be created beforehand. Individual messages are sent via the signaling network.
A30808-X5226-C559-1-7618
5-11
Siemens
SCCP
connectionless service
connectionoriented service
Protocol class single message with individual routing
Protocol class message groups with common routing
Protocol class signaling connections with uniform routing
Protocol class signaling connections with uniform routing and message numbering
Fig. 5 Protocol classes of the SCCP
5-12
A30808-X5226-C559-1-7618
Siemens
The distinction between connectionless and connection oriented services differentiates the SCCP application cases as to their functional capability. A finer graduation is given by the so-called protocol classes. CCITT defines four SURWRFRO FODVVHV (0 to 3). The higher the protocol class, the higher the functional capacities, i.e. protocol class n+1 can do everything what protocol class n can do, and even a little bit more. The protocol classes 0 and 1 are the connectionless services, the protocol classes 2 and 3 are the connection oriented services. With SURWRFRO FODVV , the SCCP only carries the information from one point to the other. The individual messages have nothing to do with each other and are routed independently to their destinations. This means that the Signaling Link Selection (SLS) is selected in such a way that the load is distributed as evenly as possible over the available signaling links. Of course, it can happen that messages overtake each other: the later dispatched message can arrive earlier if it was fortunate enough to be routed on a more suitable route. With SURWRFRO FODVV , no signaling connections exist either, but the user can mark several messages as belonging together. Those messages get the same SLS so that the MTP ensures (with a high degree of probability) that they arrive in the same order in which they were dispatched. This protocol class is used at the interfaces between SSS subunits only whilst protocol class 0 is employed both at the A-interface and between the SSS subunits. With SURWRFRO FODVV , the SCCP sets up and clears down signaling connections and transports messages in both directions over these signaling connections. Messages of the same signaling connection always get the same SLS so that the sequence control from protocol class 1 is ensured, too. This protocol class is used at the Ainterface. With SURWRFRO FODVV , additionally the messages are numbered and acknowledged within each signaling connection, so that message losses can be detected, too. This protocol class is not used for a GSM-PLMN; therefore, we shall not discuss it any more. With each signaling message, it must be clarified which protocol class it belongs to. Either the protocol class is itself transmitted as a message parameter, or it can be derived from the context.
A30808-X5226-C559-1-7618
5-13
Siemens
SCCP
connectionless service
connectionoriented service
Protocol class single message with individual routing
Protocol class message groups with common routing
Protocol class signaling connections with uniform routing
Protocol class signaling connections with uniform routing and message numbering
Fig. 6 Protocol classes of the SCCP
5-14
A30808-X5226-C559-1-7618
Siemens

%66 8VHU 3DUW %66$3 %DVH 6WDWLRQ 6\VWHP $SSOLFDWLRQ 3DUW
Signaling based on the BSSAP between BSS and SSS (interface A), which sets up on the SCCP and MTP functions. The function of the BSSAP is to support communication between the MSC and the BSC or TRAU. In this capacity, the BSSAP is divided into two subsystems, the %660$3 and the '7$3. The BSSAP uses the two SCCP protocol classes 0 (connectionless) and 2 (connection-oriented). Messages which are related to a particular RR connection at the air interface (e.g. a user connection, a Location Update, etc.), are always transmitted with protocol class 2. Messages which do not concern a particular SCCP connection make use of protocol class 0. The SCCP connections of protocol class 2 are set up together with the RR connections. The Base Station knows the allocation between the RR connections at the air interface and the SCCP connections at the A-interface. Therefore, the BSS can forward each message it has received over an RR connection towards the MSC over the allocated SCCP connection. Vice-versa, messages the BSS has received over an SCCP connection are forwarded over the allocated RR connection towards the Mobile Station. Messages which are exchanged in this manner between Mobile Station and MSC transparently through the BSS belong to the 'LUHFW 7UDQVIHU $SSOLFDWLRQ 3DUW (DTAP). The DTAP is a part of the BSSAP and consists of those messages where the layer 3 data are not modified in any way by the BSS. When the BSS receives such a message on the air interface (RR connection), it evaluates the layer 2 data, puts the layer 3 data without any alteration into an MTP-SCCP frame and transmits this frame over the corresponding SCCP connection to the MSC. When the BSS receives a DTAP message over an SCCP connection, it evaluates MTP and SCCP, puts the DTAP data without any alteration into a layer 2 frame and forwards this layer 2 frame over the corresponding RR connection to the Mobile Station. The reason for the introduction of the DTAP is that, with messages of the Mobility Management (MM) and of the Connection Management (CM), not the BSS but the SSS is affected. Only the Radio Resource Management (RR) lies within the responsibility of the BSS. Therefore, the BSS should be transparent for MM and CM. The other BSSAP messages (i.e. the messages where the BSS is not transparent) form the %66 0DQDJHPHQW $SSOLFDWLRQ 3DUW (BSSMAP). With these messages, the BSS at least modifies the received information, or it is alone the sender or the receiver of these messages, respectively (e.g. the blocking of a terrestrial circuit).
A30808-X5226-C559-1-7618
5-15
Siemens
MSC
6 ,( 0 ( 1 6 ' 6 ,( 0 ( 1 6 '
A- Interface BSS MTP
SCCP
BSSOMAP
BSSAP
DTAP
BSSMAP
Fig. 7 Structure of the A-Interface

5-16
A30808-X5226-C559-1-7618
Siemens
It follows from what has been said that DTAP messages are always related to a particular RR connection; thus, they are always transmitted in protocol class 2 (connection-oriented) between BSC and MSC. The BSSMAP messages can belong to protocol class 2 as well, but there are connectionless BSSMAP messages, too (protocol class 0). All messages belong to the Common Channel Signaling System No. 7 with User Part SCCP. There are the two Application Parts BSSOMAP and BSSAP; they are distinguished in the Called Party Address of the SCCP. The BSSAP, in due course, is subdivided into DTAP (BSS is transparent for layer 3) and BSSMAP (BSS is not transparent for layer 3). The distinction between these two parts lies within the BSSAP. the DTAP messages always belong to protocol class 2, but the BSSMAP messages belong to protocol class 2 or 0. To each RR connection MS-BSS, there is an SCCP connection BSS MSC. Since the BSS is transparent for MM and CM messages, the MM and CM connections do not exist between MS and BSS but between MS and MSC.
A30808-X5226-C559-1-7618
5-17
Siemens
MSC BSS
6 ,( 0 ( 1 6 ' 6 ,( 0 ( 1 6 '
CM connection
MM connection
RR connection
SCCP conn.
Fig. 8 Signaling connections

5-18
A30808-X5226-C559-1-7618
Siemens

7UDQVDFWLRQ &DSDELOLWLHV $SSOLFDWLRQ 3DUW 7&$3
In the GSM system the TCAP supports the mobile specific application part (MAP) and extends the functions and services of the network services part NSP (MTP + SCCP). For message transfer TCAP uses SCCP protocol classes (CL) 0 and 1. The TCAP controls information exchange between users in different network nodes of CCS7. No circuit connections are set up. The TCAP adds, for example, a transaction indicator to each message. This indicator makes it possible for the other party to identify the relation of all messages within one and the same transaction to an overall context. Thanks to the TCAP the MAP protocol does not need to concern itself, for example, with the interconnection of a message transfer for messages belonging to a single Location Update. Inefficiencies which occur during transactions are also prevented. Due to TCAP functions important data in MAP procedures (e.g. subscriber identity) need to be transmitted just once within a transaction frame. This information is valid for the remainder of the transaction.
A30808-X5226-C559-1-7618
5-19
Siemens
%66$3
0$3
,6'183
7&$3
6&&3
073

Fig. 9 Protocol architecture in the D900

5-20
A30808-X5226-C559-1-7618
Siemens

The functions of MAP signaling procedures have a key importance within the GSM system. They affect information exchange in relation to the roaming capabilities of a mobile station (MS). In particular it controls the interrogation and updating of data in the D900 SSS specific databases VLR, HLR, EIR and AC. Examples of procedures that make it possible for a subscriber to roam within the GSM service area are:
z z z z z z z z z z z
Location Registration Deletion of previous location registrations e.g. when making new location registrations or canceling a subscription (Location Cancellation) Handling of supplementary services available to the subscriber (Handling of Supplementary Services) Support of Short Message Service (SMS) Handling of an access request from an MS (Access Request Management) Updating of subscriber parameters in HLR and VLR MSC handover Paging and searching for the MS Transfer of confidential data for authentication and encipherment Transfer of charge information Support of different operating and maintenance functions
A30808-X5226-C559-1-7618
5-21
Siemens
%66$3
0$3
,6'183
7&$3
6&&3
073

Fig. 10 CCS7 protocol architecture in the D900

5-22
A30808-X5226-C559-1-7618
Siemens

,6'1 8VHU 3DUW ,683
ISUP provides the respective signaling capabilities for basic bearer and supplementary services. Signaling can occur either link-by-link or end-to-end. In general the ISUP is comprised of the signaling function for
z z z
the control of the setup and release of call connections (digital / analog subscribers) management of trunk lines handling of services and service aspects (e.g. display of A subscribers CLIP, Closed User Group CUG, call holding HOLD,...)
The ISUP is also able to utilize SCCP services although this is not necessary.
A30808-X5226-C559-1-7618
5-23
Siemens
%66$3
0$3
,6'183
7&$3
6&&3
073

Fig. 11 CCS7 protocol architecture in the D900

5-24
A30808-X5226-C559-1-7618
Siemens
&RPSOHWH 6HTXHQFHV
In this section, we are going to investigate how the mobile specific procedures (i.e. call set up and clear down and location update) appear at the A-interface, which parts belong to the BSSMAP and which to the DTAP. With all call setups, the case we are going to consider is with authentication and enciphering, but without IMEI interrogation. With 0RELOH 2ULJLQDWLQJ &DOOV (MOC), the following BSSMAP procedures are affected: At first, the Mobile Station sets up (after the channel assignment in the RACH / AGCH) a layer 2 connection and demands in the SABM the set up of a layer 2 connection for call control (message "CM Service Request"). This is the ,QLWLDO 06 0HVVDJH; therefore, it leads to the SCCP connection set up, and the Base Station forwards the "CM Service Request" in the CR to the MSC. The following authentication makes use of the DTAP: the messages are transmitted at the A-interface as SCCP-messages but at the air interface as I-Frames. The first message "Authentication Request" can be contained in the SCCP-message CC which acknowledges the CR. Alternatively, it is possible that the MSC sends a CC without user message to the BSS and transmits the "Authentication Request" in a DT1. Afterwards, the &LSKHU 0RGH &RQWURO is performed. The following messages "Setup" and "Call Proceeding" again belong to the DTAP. Sooner (without OACSU) or later (with OACSU), a user channel is assigned to the Mobile Station. This is the BSSMAP procedure $VVLJQPHQW. All further proceedings with a mobile originating call (use the DTAP.
A30808-X5226-C559-1-7618
5-25
Siemens
MSC
6 ,( 0 ( 1 6 ' 6 ,( 0 ( 1 6 '
Channel Req. RACH UI (Imm. Assign.)
BSS
AGCH CR (Complete L3 Info) (Cell-Id., CM-Request)
SDDCH UA
SABM (CM Request) SDDCH Authentication Request (RAND) Authentication Response (SRES)
I I I(Ciph. Comm.)
CC DT1 DT1 (Cipher Command)
SDDCH
SDDCH I
I(Ciph. Compl.)
DT1 (Ciph. Compl.)
Setup DQG VR RQ
DT1
I (Ass. Command)
SDDCH
DT1 (Assign Request)
FACCH UA
SABM
FACCH DT1 (Assign Complete)
FACCH
I (Ass. Complete)
Fig. 12 Mobile Originating Call (MOC)
5-26
A30808-X5226-C559-1-7618
Siemens
A 0RELOH 7HUPLQDWLQJ &DOO (MTC) begins with Paging. In the course of this procedure, both the RR connection at the air interface and the SCCP connection at the A-interface are set up. The following authentication is done in the DTAP whereas the &LSKHU 0RGH &RQWURO is again a BSSMAP procedure. "Setup" and "Call Confirmed" are DTAP messages. The last BSSMAP procedure is the $VVLJQPHQW. Everything else again runs in the DTAP.
A30808-X5226-C559-1-7618
5-27
Siemens
MSC
6 ,( 0 ( 1 6 ' 6 ,( 0 ( 1 6 '
BSS UI (Paging Requ.) PCH UDT (Paging)
RACH
Channel Request
UI (Imm. Assign.)
AGCH
SDCCH
SABM (Paging Resp.) CR (Complete L3 Info) Cell-Id., Paging resp.) CC
UA
SDCCH Authentication Request (RAND)
Authentication Response (SRES)
DT1
I(Ciph. Comm.)
SDDCH
DT1 (Cipher Command)
SDDCH I
I(Ciph. Compl.)
DT1 (Ciph. Compl.)
Setup
DT1
DQG VR RQ &KDQQHO DVVLJQPHQW DV ZLWK 0RELOH 2ULJLQDWLQJ &DOOV

Fig. 13 Mobile terminating call (MTC)
5-28
A30808-X5226-C559-1-7618
Siemens
With the &DOO FOHDU GRZQ, the messages "Disconnect" (if it is the Mobile Station who initiates the cleardown), "Release" and "Release Complete" run in the DTAP. Afterwards, &KDQQHO 5HOHDVH is performed with "Clear Command" and "Clear Complete" at the A-interface and "Channel Release" at the air interface. Finally, the layer 2 connection at the air interface and the SCCP connection will be cleared down.
A30808-X5226-C559-1-7618
5-29
Siemens
MSC LQLWLDWHG E\ WKH 0RELOH 6WDWLRQ BSS I I I I (Channel Rel.) DISC UA Authentication Response (SRES) Authentication Request (RAND) Authentication Response (SRES) FACCH DT1 DT1 DT1 DT1 (Clear Command) DT1 (Clear Complete) RLSD FACCH RLC
6 ,( 0 ( 1 6 ' 6 ,( 0 ( 1 6 '
FACCH
MSC
6 ,( 0 ( 1 6 ' 6 ,( 0 ( 1 6 '
LQLWLDWHG E\ WKH SDUWQHU VLGH BSS
I I
Release Release Complete
DT1 DT1
I (Channel Rel.) DISC UA
FACCH
DT1 (Clear Command) DT1 (Clear Complete) RLSD
FACCH
FACCH
RLC
Fig. 14 Call clear down
5-30
A30808-X5226-C559-1-7618
Siemens
Finally, with the /RFDWLRQ 8SGDWH, there are three relevant BSSMAP procedures. It starts with the ,QLWLDO 060HVVDJH, namely the message "Location Update Request"; this includes the set up of the SCCP connection. As usual, the first Mobile Station message (after the assignment of the SDCCH) is contained in the SABM (Contention resolution procedure). The following authentication again uses the DTAP. As before, "Authentication Request" can run in the CC or in a DT1 (in this case, the MSC must send an empty CC beforehand). Afterwards, the &LSKHU 0RGH &RQWURO is performed in the BSSMAP. The messages "Location Update Accept" and "TMSI Reallocation Complete" belong to the DTAP. Afterwards, however, the 5HOHDVH procedure of the BSSMAP is performed with "Clear Command" and "Clear Complete" at the A-interface and "Channel Release" at the air interface. Finally, the layer 2 connection at the air interface and the SCCP connection are cleared down.
A30808-X5226-C559-1-7618
5-31
Siemens
MSC
6 ,( 0 ( 1 6 ' 6 ,( 0 ( 1 6 '
RACH
Channel Req.
BSS
UI (Imm. Assign.)
AGCH CR (Complete L3 Info) (Cell-Id., Upd.Request)
SDCCH UA
SABM (CM Request) SDCCH Authentication Request (RAND) Authentication Response (SRES)
I I I(Ciph. Comm.)
CC DT1 DT1 (Cipher Command)
SDCCH
SDCCH I I
I(Ciph. Compl.)
DT1 (Ciph. Compl.)
Location Update Accept TMSI Reallocation Complete SDCCH DISC
DT1 DT1 DT1 (Clear Command)
I (Channel Rel.)
SDCCH UA
DT1 (Clear Complete) RLSD
SDCCH
RLC
Fig. 15 Location update
5-32
A30808-X5226-C559-1-7618
Siemens

z z
)RUPDWWLQJ 5XOHV
an optional parameter in the SCCP messages "Connection Request" (CR), "Connection Confirm" (CC) and "Released"(RLSD) a mandatory parameter of variable length in the SCCP messages "Data Form 1" (DT1) and "Unitdata"(UDT).
The BSSAP is always transmitted in the SCCP parameter "Data". This is
CR, CC, RLSD and DT1 are messages of the protocol class 2 (connection-oriented) whilst UDT belongs (at the A-interface) to the protocol class 0 (connectionless). Because "Data" can appear as an optional parameter or as a mandatory parameter of variable length, the SCCP always contains a length indicator for the "Data" field which gives the total length of the BSSAP. After this length indicator, the so-called 'LVFULPLQDWLRQ E\WH follows which distinguishes between DTAP and BSSMAP. The most significant seven bit are 0, and the least significant bit (= the discrimination bit) is 1 for the DTAP (i.e. transparent) and 0 for the BSSMAP (i.e. not transparent).
A30808-X5226-C559-1-7618
5-33
Siemens
Optional in CR, CC and RLSD SCCP message type: CR, CC, RLSD Mandatory parameters of fixed lengt Mandatory parameters of variable lengt Optional parameters Identifier: Data Length indicator Discrimination Byte
Mandatory in UDT and DT1 SCCP message type: UDT, DT1 Mandatory parameters of fixed lengt Mandatory parameters of variable lengt P o i n t e r: D a t a
Length indicator Discrimination Byte
BSSAP
BSSAP
Optional parameters
Fig. 16 Embedding of the BSSAP into the SCCP
5-34
A30808-X5226-C559-1-7618
Siemens
In the case of the DTAP, after the Discrimination byte the 'DWD /LQN &RQQHFWLRQ ,GHQWLILFDWLRQ (DLCI) ensues which is also 1 byte long. The byte indicates the SAPI (Service Access Point Identifier, from layer 2 of the air interface) with which the message has been received or is to be sent, respectively. After the DLCI, the following data ensue:
z z
the length indicator for layer 3 of the air interface (1 byte) layer 3 of the air interface corresponding its formatting rules .
The value of the SCCP length indicator for the "Data" parameter exceeds by 3 the length indicator for layer 3 since the "Data" length indicator includes three additional bytes (the discrimination byte, the DLCI and the length indicator for layer 3). In the case of the BSSMAP, the following data ensue after the discrimination byte:
z z
the length indicator for layer 3 of the BSSMAP layer 3 of the BSSMAP itself.
This time, the two length indicators ("Data" parameter, layer 3 BSSMAP) differ by 2 only since the DLCI byte is omitted. Layer 3 of the BSSMAP consists of information elements. The first information element (after the length indicator) is the message type. It has a length of 1 byte and classifies the messages as to their purpose (e.g. "Assignment Request", "Complete Layer 3 Information" etc.). The GSM guideline 08.08 contains, for each message type, a list of the further information elements of the message; these further information elements can be optional (O) or mandatory (M). However, the elements DOZD\V begin with an element identifier with the length of 1 byte. Thus, the only element without an element identifier is the message type itself. Simultaneously, the list of information elements indicates the sequence in which the mandatory and optional parameters (the latter as far as present) must be sent. There is no general rule for this sequence; rather, it is defined for each message type individually.
A30808-X5226-C559-1-7618
5-35
Siemens
DTAP:
0 0
0 0
0 0
0 0
0 0
0 SAPI
1 Discriminator: transparent DLCI
Length indicator
Layer 3 of the air interface
BSSMAP:
Discriminator: not transparent
Length indicator BSSMAP message type
information elements (always with identifier)
Fig. 17 Layout of DTAP and BSSMAP (GSM 08.06)
5-36
A30808-X5226-C559-1-7618
Siemens
Elements of variable length contain after the identifier a length indicator of 1 byte which indicates how many bytes will follow after the indicator. The total length of such an element is the length indicator value +2 (since the length indicator does not count the identifier and itself). With elements of fixed length, the length indicator is omitted; here, after the identifier, the contents begin immediately. Lets consider as a first example the message "Block" which is used by the BSC to inform the MSC that it cannot access a certain terrestrial circuit any longer (see the BSSMAP procedure "blocking"). Besides the message type, the message contains two more parameters: the Circuit Identity Code (CIC) of the affected channel and the cause for the blocking (e.g. "Equipment failure" or "OAM intervention"). Both parameters are mandatory. Whilst the CIC has the fixed length of 3 byte, the cause can have a length of 3 or 4 byte; thus, the indication of the length in the message is necessary. "Block" is always transmitted in a "Unitdata" (UDT). Therefore, "Data" is a mandatory SCCP parameter of variable length. As a second example, we take the message "Complete Layer 3 Information" which is used by the BSC to set up the SCCP connection. This message belongs to the BSSMAP procedure "Initial MS message". A layer 3 message of the air interface received in an SABM is forwarded to the MSC; the BSC adds the identity of the radio cell. Correspondingly, the message contains, besides the message type, the cell identity and the layer 3 data of the air interface. Both parameters are mandatory and have a variable length. As a consequence, length indicators are required. The optional parameter chosen channel tells which channel was selected at the air interface. "Complete Layer 3 Information" is always transmitted in a "Connect Request" (CR). Thus, "Data" is an optional SCCP parameter.
A30808-X5226-C559-1-7618
5-37
Siemens
Information element Message Type Circuit Identity Code (CIC) Cause
Type M M M
Length 1 3 3-4
Fig. 18 Complete layer 3 information
Information element Message Type Cell Identity Layer 3 information Chosen Channel
Type M M M 0
Length 1 3-10 3-n 2
Fig. 19 Complete layer 3 information
5-38
A30808-X5226-C559-1-7618
Siemens
As an example for a DTAP message, we select the "Setup" MS BSS MSC. The BSS removes the layer 2 frame of this message and adds instead
z z z
the Discrimination byte (0000 0001 = transparent, i.e. DTAP) the DLCI (Data Link Control Identifier). The last 3 bit provide the SAPI value 000 (signaling) the length indicator of layer 3 (here: 17 byte).
The layer 3 data with protocol discriminator, transaction identifier, message type and all information elements are forwarded to the MSC in an unaltered manner. The DTAP message constructed in this way is contained in an SCCP message "Data Form 1" (DT1) as parameter "Data".
A30808-X5226-C559-1-7618
5-39
Siemens
0 0 0 0
0 0 0
0 0 0 TI-Value
0 0 1
0 0 0 0
0 0 0 0 1 1 0 0 1 1 1 0 0 0 0 1 1 1 1 0 0
0 0 0 1 0 0 0 0 1 1 1 0 0 0 1 0 0 1 0 0 0
1 0 1 1 1 0 1 0 0 11 0 0 1 0 0 0 1 0 1 0
Discrim.:transparent DLCI: SAPI = 0 (signaling) Length indicator: 17 Byte Protocol discriminator CC (TI-Flag = 0) Message Type Setup Bearer Capability: Length 1, speech full rate, Circuit Mode
0 N(SD) 0 0 0 1 0 00 1 1 0 0 0 1 1 0 0 0 0 0 0 1 0 0 0 0 1 0 0 0 1 1 0 0 0 0 1 0 0 0 0 0 1 1 0 0 1 1 0 0
0 0 0 0 1 0 0 0 1 0 1 1 1 1 0 0
0 0 0 0 1 0 0 0 1 0 0 0 0 1 0 0
Called Party BCD Number: Length 7, Type of Number unknown, Numbering Plan unknown, Number 08972241497
Low Layer Capability: Length 1, speech
Fig. 20 Example for a DTAP message
5-40
A30808-X5226-C559-1-7618
Siemens
Now, we consider an example for a "Block" message. The message begins with the Discriminator byte 0000 0000 (not transparent, i.e. BSSMAP). There now follows the length indicator (here: 7 byte). The subsequent message type 0100 0000 identifies the message as "Block". Afterwards, the CIC must ensure. Indeed, we find next the element identifier 0000 0001 which marks the next element as CIC, followed by 2 bytes CIC value. Here, the length is fixed, and no length indicator is included. Now, we find the element identifier 0000 0100, i.e. Cause. This time, a length indicator is required since the total length can vary. The length indicator has the value 1 (1 byte contents), and we conclude 3 bytes total length of the element (1 byte identifier, 1 byte length indicator, 1 byte contents). The content of the element "Cause" begins with an extension bit (value 0: no further byte present). The next 3 bits identify the class of the cause (value 010: resource unavailable), whilst the next 4 bits clearly identify the cause within its class (here: equipment failure). "Block" is a "Data" parameter in the SCCP message "Unitdata" (UDT).
A30808-X5226-C559-1-7618
5-41
Siemens
0 0 0 0
0 0 1 0
0 0 0 0
0 0 0 0 CIC
0 0 0 0
0 1 0 0
0 1 0 0
0 1 0 1
Discrim.: not transparent Length indicator: 7 byte Message Type Block Element identifier Circuit Identity Code
0 0 0
0 0 0
0 0 1
0 0 0
0 0 0
1 0 0
0 0 0
0 1 0
Element identifier Cause Length 1 Equipment Failure
Fig. 21 Example for a "Block"

5-42
A30808-X5226-C559-1-7618
Siemens
As last example, we consider a "Complete Layer 3 Information" where the layer 3 message "Location Update Request" is embedded. The message begins with the Discriminator byte 0000 0000 (not transparent, i.e. BSSMAP), and the length indicator ensues (here: 23 bytes). The next byte with the value 0101 0111 identifies the BSSMAP message as "Complete Layer 3 Information". The first parameter is the cell identity which is marked by the identifier value 0000 0101. The next byte says that 3 bytes for the contents are going to follow; thus, the total length of the element is 5 bytes. Next, a discriminator follows which indicates which cell characteristics are contained in the element. The value 0000 0010 means that the cell is identified by the Cell Identity CI alone (and not by LACOD+CI or even by CGI = MCC+MNC+LACOD+CI). Accordingly, two bytes CI-value ensue. The next - and last - parameter is the layer 3 information, marked by the identifier 0001 0111. The length indicator states that the layer 3 data have a length of 15 bytes; a total length of 17 bytes results. There now follows the "Location Update Request" with protocol discriminator, transaction identifier, message type and all information elements. This BSSMAP message is a "Data" parameter in a "Connect Request" (CR) from the Base Station to the MSC.
A30808-X5226-C559-1-7618
5-43
Siemens
0 0 0 0 0 0
0 0 1 0 0 0
0 0 0 0 0 0
0 1 1 0 0 0 CI
0 0 0 0 0 0
0 1 1 1 0 0
0 1 1 0 1 1
1 1 1 1 1 1
Discrim.: not transparent Length indicator: 23 byte Message type Complete Layer 3 inform. Element identifier Cell identity Length 3 byte Cell identified by CI
0 0 0
0 0 0
0 0 0
1 0 0 0
0 1 0 1 0
1 1 1 0 0
1 1 0 0 0
1 1 1 0 0
Element identifier Layer 3 information Length 15 byte Protocol discriminator MM (TI=0) Message Type Loc. Update Request Normal Loc. Upd.; no follow-on
0 N(SD) 0
Key Sequ. Nr. 1 1 1 1
MCC MNC LACOD 0 0 1 0 0 1 0 0 1 0 0 1 0 0 0 RF Power 1 1 0 0 1 0 Mobile Identity: Length 5; TMSI TMSI Mobile Station Classmark 1 Location Area Identification
Fig. 22 Example for a "Complete Layer 3 Information"
5-44
A30808-X5226-C559-1-7618
Siemens
$SSHQGL[
Simplified, it can be said that the BSS tries as far as possible to deal by itself with the proceedings at the air interface, whereas the SSS is in charge of all proceedings between MSC and BSC and, of course, within the SSS itself. Thus, the user channels at the A-interface are always seized and released by the MSC; the BSC can only indicate if a channel is blocked. On the other hand, all channels of the air interface are administered by the BSC. Here, the MSC can only initiate the channel release (during call clear down, Handover etc.). Handover within one cell or within the BSC area is controlled by the BSC, but as soon as the BSC area is left, the MSC is in charge, of course. Finally, the BSC enciphers and deciphers the radio channels, but it gets the ciphering key from the MSC.
A30808-X5226-C559-1-7618
5-45
Siemens
Function Terrestrial channel: Channel Allocation Terrestrial channel: Blocking indication Radio channel: Configuration Managenemt Radio channel: Frequency hopping Management Radio channel: Idle channel Observation Radio channel: Power control TCH: Channel Allocation (Choice) TCH: Link Supervision TCH: Channel Release BCCH/CCCH: Scheduling of Messages DCCH: Link Supervision DCCH: Channel Release DCCH: Allocation Radio Ressource Indication (report idle channels) Channel Coding Transcoding/Rate Adaptation Interworking Function (data calls) Measurements: Reported from MS Measurements: Uplink Measurements: Traffic Handover: within one cell Handover: within the BSC Handover: external; Recognition Radio Reason Handover: external; Recognition Traffic Reason Handover: external; Decision Handover: external; Execution MM: Authentication MM: Location Update MM: Paging Call Control User Data Encryption Signaling Element Encryption
BSS
SSS X
X X X X X X X X X X X X X X X X X X X X X X X MSC informed MSC informed
X (Invoked by MSC)
X (Invoked by MSC)
MSC defines Call Type X
X X X X X X X Key / Algorithms from MSC Key / Algorithms from MSC
X X
Fig. 23 BSS - SSS Function Split (GSM 08.02)
5-46
A30808-X5226-C559-1-7618
Siemens

%660$33URFHGXUHV
Fig. 24 gives an overview over all the procedures of the BSSMAP and their distribution over the SCCP protocol classes 0 (connectionless) and 2 (connectionoriented). It can be seen that all proceedings related to an existing user connection belong to class 2 whilst global procedures such as blocking and releasing of circuits are executed in class 0. The VHW XS RI 6&&3 FRQQHFWLRQV is performed by the BSSMAP, too. This can be caused by the BSC and by the MSC as well. When a Mobile Station sets up a new RR connection at the air interface, e.g. for a mobile originating or terminating call, or for a location update, the Base Station reacts by setting up the SCCP connection to the mobile switching center. This is the BSSMAP procedure "Initial MS message". When, on the other hand, a Handover to a new BSC is executed, it is the MSC which sets up the SCCP connection. This is done in the BSSMAP procedures "Handover resource allocation" and "Handover execution".
A30808-X5226-C559-1-7618
5-47
Siemens
Procedure Initial MS message Assignment Release Cipher mode control Paging Handover required indication Handover resource allocation Handover execution Classmark update Trace invocation Queuing indication Data link control for SAPI 0 Blocking Resource indication Reset Reset Circuit Handover candidate enquiry Flow control
Fig. 24 BSSMAP procedures (GSM 08.08)
Class 0
Class 2 X X X X
X X X X X X X X X X X X X X
5-48
A30808-X5226-C559-1-7618
Siemens

.
. 7UDFH LQ 6KRUW )RUPDW

&&6 1R 0RQLWRU 'DWH 7LPH , )61 , /, 6/6 &,& 1$0( &5 &/, &065(4 && &,&0' '7 &,&03 '7 ,'5(4 '7 6(783 '7 &352& '7 $65(4 '7 ,'5(6 '7 $6&03 8'7 3$*,1 &5 &/, 3$*5(6 && &,&0' '7 &,&03 '7 ,'5(4 '7 6(783 '7 ,'5(6 '7 &&21) '7 $65(4 '7 $6&03 '7 $/(57 '7 $/(57 '7 &211(&7 '7 &21$&. '7 &211(&7 '7 &21$&.
++00VV P )520 7<3( %61 EVV VFFS EPDS GWDS PVF VFFS EPDS EVV VFFS EPDS PVF VFFS GWDS EVV VFFS GWDS PVF VFFS GWDS PVF VFFS EPDS EVV VFFS GWDS EVV VFFS EPDS PVF VFFS EPDS EVV VFFS EPDS GWDS PVF VFFS EPDS EVV VFFS EPDS PVF VFFS GWDS PVF VFFS GWDS EVV VFFS GWDS EVV VFFS GWDS PVF VFFS EPDS EVV VFFS EPDS EVV VFFS GWDS PVF VFFS GWDS EVV VFFS GWDS PVF VFFS GWDS PVF VFFS GWDS EVV VFFS GWDS
A30808-X5226-C559-1-7618
5-49
Siemens
EVV PVF PVF EVV EVV PVF EVV PVF PVF EVV EVV PVF EVV
VFFS GWDS VFFS GWDS VFFS GWDS VFFS GWDS VFFS GWDS VFFS EPDS VFFS EPDS VFFS EPDS VFFS VFFS EPDS VFFS VFFS VFFS

'7 ',6& '7 5(/($6 '7 5(/($6 '7 5(/&03 '7 5(/&03 '7 &/&0' '7 &/&03 '7 &/&0' 5/6' '7 &/&03 5/& 5/6' 5/&
5-50
A30808-X5226-C559-1-7618
Siemens

K1103 ---
. 7UDFH LQ /RQJ )RUPDW

CCS No. 7 - Monitor , Date: 21.01.97 , Time: 10:50:44
HH:MM:ss"m FROM TYPE SIO DPC OPC SLS CIC NAME 15:20:51"6 bss sccp 83 3050 408 5 CR ITU-T WHITE BOOK SCCP (sccp) &RQQHFWLRQ 5HTXHVW &5 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 3050 ******** Originating Point Code 408 ******** Signalling Link Selection 5 00000001 SCCP Message Type 0x1 ******** Source Local Reference 0x202C00 ----0010 Protocol Class Class 2 0000---- Spare 00000010 Ptr to Called address pa 2 00000100 Ptr to optional param. 4 Called address parameter 00000010 Parameter Length 2 -------0 Point Code Indicator PC absent ------1- Subsystem No. Indicator SSN present --0000-- Global Title Indicator No global title included -1------ Routing Indicator Route on DPC + Subsystem No. 0------- For national use 0 11111110 Subsystem number BSSAP Data parameter 00001111 Parameter name Data 00011011 Parameter length 27 ******** Data 00 19 57 05 05 01 00 01 00 1A 17 0F 05 24 71 02 03 08 08 29 26 20 26 00 00 00 40 00000000 Parameter name End of Optional Params bmap CL3I E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) &RPSOHWH OD\HU LQIRUPDWLRQ &/, -------0 Discrimination bit D BSSMAP 0000000- Filler 00011001 Message Length 25 01010111 Message Type 0x57 Cell Identifier 00000101 IE Name Cell identifier 00000101 IE Length 5 ----0001 Cell ID discriminator LAC/CI used to ident cell ******** LAC 1 ******** CI 26
A30808-X5226-C559-1-7618
5-51
Siemens
Layer 3 information 15 05 24 71 02 03 08 08 29 26 20 26 00 00 00 40 dtap 5 CMSREQ MM Message Connection management message E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) &0 VHUYLFH UHTXHVW &065(4 ----0101 Protocol Discriminator mobility management msg -000---- Transaction Id value TI value 0 0------- Transaction Id flag message sent from orig TI --100100 Message Type 0x24 -0------ Send Sequence Number 0 0------- Extension bit ----0001 CM Service type MOC est/pkt mode con estab 0111---- Key sequence no key available/reserved Mobile Station Classmark 2 00000010 IE Length 2 -----011 RF power capability Class 4 ----0--- A5/1 algorithm supported Available ---0---- Spare -00----- Revision level Reserved for phase 1 0------- Spare -------0 Frequency capability MS does not support the ext. band G1 -----00- Spare ----1--- SM capability Present --00---- SS Screening Indicator Phase 1 -0------ PS capability Not present 0------- Spare Mobile IDentity 00001000 IE Length 8 -----001 Type of identity IMSI ----1--- Odd/Even Indicator Odd no of digits ******** Identity digits 262026200000004 15:20:51"7 msc sccp 83 408 3050 11 CC ITU-T WHITE BOOK SCCP (sccp) &RQQHFWLRQ &RQILUP && ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 408 ******** Originating Point Code 3050 ******** Signalling Link Selection 11 00000010 SCCP Message Type 0x2 ******** Destination Local Ref. 0x202C00 ******** Source Local Reference 0x402021 ----0010 Protocol Class Class 2 0000---- Spare 00000001 Ptr to optional param. 1 Data parameter 00001111 Parameter name Data 00001010 Parameter length 10 ******** Data 00 08 53 07 02 06 00 0A 01 01 00000000 Parameter name End of Optional Params bmap CICMD E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) &LSKHU 0RGH &RPPDQG &,&0'
LAyer 3 Information 00010111 IE Name 00001111 IE Length ******** L3 Message Contents
5-52
A30808-X5226-C559-1-7618
Siemens
-------0 Discrimination bit D 0000000- Filler 00001000 Message Length 01010011 Message Type Layer 3 header INformation 00000111 IE Name 00000010 IE Length ----0110 Protocol Discriminator 0000---- Spare -----000 Transaction Id value ----0--- Transaction Id flag 0000---- Spare Encryption Information 00001010 IE Name 00000001 IE Length -------1 No encryption ------0- GSM A5/1 -----0-- GSM A5/2 ----0--- GSM A5/3 ---0---- GSM A5/4 --0----- GSM A5/5 -0------ GSM A5/6 0------- GSM A5/7
BSSMAP 8 0x53 Layer 3 header information 2 radio resources management msg TI value 0 message sent from orig TI
Encryption information 1 May be used Not used Not used Not used Not used Not used Not used Not used
15:20:52"3 bss sccp 83 3050 408 5 DT1 ITU-T WHITE BOOK SCCP (sccp) 'DWD )RUP '7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 3050 ******** Originating Point Code 408 ******** Signalling Link Selection 5 00000110 SCCP Message Type 0x6 ******** Destination Local Ref. 0x402021 -------0 Segment/reass M indicator No more data 0000000- Spare 00000001 Ptr to Data parameter 1 Data parameter 00000011 Parameter length 3 ******** Data 00 01 55 bmap CICMP E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) &LSKHU 0RGH &RPSOHWH &,&03 -------0 Discrimination bit D BSSMAP 0000000- Filler 00000001 Message Length 1 01010101 Message Type 0x55
A30808-X5226-C559-1-7618
5-53
Siemens
15:20:52"3 msc sccp 83 408 3050 11 DT1 ITU-T WHITE BOOK SCCP (sccp) 'DWD )RUP '7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 408 ******** Originating Point Code 3050 ******** Signalling Link Selection 11 00000110 SCCP Message Type 0x6 ******** Destination Local Ref. 0x202C00 -------0 Segment/reass M indicator No more data 0000000- Spare 00000001 Ptr to Data parameter 1 Data parameter 00000110 Parameter length 6 ******** Data 01 00 03 05 18 02 dtap 5 IDREQ MM Message Security message E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) ,GHQWLW\ UHTXHVW ,'5(4 -------1 Discrimination bit D DTAP 0000000- Filler -----000 SAPI Signalling --000--- Spare 00------ Radio channel id fACCH or sDCCH 00000011 Message Length 3 ----0101 Protocol Discriminator mobility management msg -000---- Transaction Id value TI value 0 0------- Transaction Id flag message sent from orig TI --011000 Message Type 0x18 -0------ Send Sequence Number 0 0------- Extension bit -----010 Type of identity IMEI ----0--- Spare 0000---- Spare
5-54
A30808-X5226-C559-1-7618
Siemens
15:20:52"5 bss sccp 83 3050 408 5 DT1 ITU-T WHITE BOOK SCCP (sccp) 'DWD )RUP '7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 3050 ******** Originating Point Code 408 ******** Signalling Link Selection 5 00000110 SCCP Message Type 0x6 ******** Destination Local Ref. 0x402021 -------0 Segment/reass M indicator No more data 0000000- Spare 00000001 Ptr to Data parameter 1 Data parameter 00001111 Parameter length 15 ******** Data 01 00 0C 03 45 04 01 A0 5E 05 81 26 00 00 F7 dtap 3 SETUP CC Message Call establishment message E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) 6HWXS 6(783 -------1 Discrimination bit D DTAP 0000000- Filler -----000 SAPI Signalling --000--- Spare 00------ Radio channel id fACCH or sDCCH 00001100 Message Length 12 ----0011 Protocol Discriminator Call/Connection control, CR SS -000---- Transaction Id value TI value 0 0------- Transaction Id flag message sent from orig TI --000101 Message Type 0x5 -1------ Send Sequence Number 1 0------- Extension bit Bearer Capability 00000100 IE Name Bearer Capability 00000001 IE Length 1 -----000 Info transfer capability Speech ----0--- Transfer mode Circuit mode ---0---- Coding standard GSM standardized coding -01----- Radio channel requirement Full rate channel 1------- Extension bit No Extension CaLleD party BCD number 01011110 IE Name CaLleD party BCD number 00000101 IE Length 5 ----0001 Number plan ISDN/telephony numbering plan -000---- Type of number Unknown 1------- Extension bit No Extension ******** Called party number 6200007 1111---- Filler
A30808-X5226-C559-1-7618
5-55
Siemens
15:20:52"6 msc sccp 83 408 3050 11 DT1 ITU-T WHITE BOOK SCCP (sccp) 'DWD )RUP '7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 408 ******** Originating Point Code 3050 ******** Signalling Link Selection 11 00000110 SCCP Message Type 0x6 ******** Destination Local Ref. 0x202C00 -------0 Segment/reass M indicator No more data 0000000- Spare 00000001 Ptr to Data parameter 1 Data parameter 00000101 Parameter length 5 ******** Data 01 00 02 83 02 dtap 3 CPROC CC Message Call establishment message E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) &DOO SURFHHGLQJ &352& -------1 Discrimination bit D DTAP 0000000- Filler -----000 SAPI Signalling --000--- Spare 00------ Radio channel id fACCH or sDCCH 00000010 Message Length 2 ----0011 Protocol Discriminator Call/Connection control, CR SS -000---- Transaction Id value TI value 0 1------- Transaction Id flag message sent to orig TI --000010 Message Type 0x2 -0------ Send Sequence Number 0 0------- Extension bit
5-56
A30808-X5226-C559-1-7618
Siemens
15:20:52"6 msc sccp 83 408 3050 11 DT1 ITU-T WHITE BOOK SCCP (sccp) 'DWD )RUP '7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 408 ******** Originating Point Code 3050 ******** Signalling Link Selection 11 00000110 SCCP Message Type 0x6 ******** Destination Local Ref. 0x202C00 -------0 Segment/reass M indicator No more data 0000000- Spare 00000001 Ptr to Data parameter 1 Data parameter 00010100 Parameter length 20 ******** Data 00 12 01 0B 03 01 08 01 07 02 06 00 06 01 15 01 00 01 19 01 bmap ASREQ E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) $66LJQPHQW 5(4HVW $65(4 -------0 Discrimination bit D BSSMAP 0000000- Filler 00010010 Message Length 18 00000001 Message Type 0x1 Channel Type 00001011 IE Name Channel type 00000011 IE Length 3 00000001 Speech/Data Indicator Speech 00001000 Channel Rate/Type Full rate TCH channel Bm 00000001 Speech Encoding Algorithm GSM speech algorithm Ver 1 Layer 3 header INformation 00000111 IE Name Layer 3 header information 00000010 IE Length 2 ----0110 Protocol Discriminator radio resources management msg 0000---- Spare -----000 Transaction Id value TI value 0 ----0--- Transaction Id flag message sent from orig TI 0000---- Spare PRIority 00000110 IE Name Priority 00000001 IE Length 1 -------1 Preemption Vulnerab. Ind Might be prerempted ------0- Queueing allowed ind not allowed --0101-- Priority level 5 -0------ Preemption Capability ind not allowed 0------- Spare Circuit Identity Code 00000001 IE Name Circuit identity code 00000000 PCM Multiplex a-h 0 000----- PCM Multiplex i-k 0 ---00001 Timeslot in use 1 Downlink DTX flag 00011001 IE Name Downlink DTX flag -------1 DTX in downlink direction forbidden 0000000- Spare
A30808-X5226-C559-1-7618
5-57
Siemens
15:20:53"0 bss sccp 83 3050 408 5 DT1 ITU-T WHITE BOOK SCCP (sccp) 'DWD )RUP '7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 3050 ******** Originating Point Code 408 ******** Signalling Link Selection 5 00000110 SCCP Message Type 0x6 ******** Destination Local Ref. 0x402021 -------0 Segment/reass M indicator No more data 0000000- Spare 00000001 Ptr to Data parameter 1 Data parameter 00001110 Parameter length 14 ******** Data 01 00 0B 05 19 08 4A 09 01 40 01 34 85 09 dtap 5 IDRES MM Message Security message E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) ,GHQWLW\ UHVSRQVH ,'5(6 -------1 Discrimination bit D DTAP 0000000- Filler -----000 SAPI Signalling --000--- Spare 00------ Radio channel id fACCH or sDCCH 00001011 Message Length 11 ----0101 Protocol Discriminator mobility management msg -000---- Transaction Id value TI value 0 0------- Transaction Id flag message sent from orig TI --011001 Message Type 0x19 -0------ Send Sequence Number 0 0------- Extension bit Mobile IDentity 00001000 IE Length 8 -----010 Type of identity IMEI ----1--- Odd/Even Indicator Odd no of digits ******** Identity digits 490100410435890
5-58
A30808-X5226-C559-1-7618
Siemens
15:20:53"8 bss sccp 83 3050 408 5 DT1 ITU-T WHITE BOOK SCCP (sccp) 'DWD )RUP '7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 3050 ******** Originating Point Code 408 ******** Signalling Link Selection 5 00000110 SCCP Message Type 0x6 ******** Destination Local Ref. 0x402021 -------0 Segment/reass M indicator No more data 0000000- Spare 00000001 Ptr to Data parameter 1 Data parameter 00000011 Parameter length 3 ******** Data 00 01 02 bmap ASCMP E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) $66LJQPHQW &20SOHWH $6&03 -------0 Discrimination bit D BSSMAP 0000000- Filler 00000001 Message Length 1 00000010 Message Type 0x2
A30808-X5226-C559-1-7618
5-59
Siemens
15:20:54"1 msc sccp 83 408 3050 3 UDT ITU-T WHITE BOOK SCCP (sccp) 8QLWGDWD 8'7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 408 ******** Originating Point Code 3050 ******** Signalling Link Selection 3 00001001 SCCP Message Type 0x9 ----0000 Protocol Class Class 0 0000---- Message Handling No special options 00000011 Ptr to Called address pa 3 00000111 Ptr to Calling address p 7 00001011 Ptr to Data parameter 11 Called address parameter 00000100 Parameter Length 4 -------1 Point Code Indicator PC present ------1- Subsystem No. Indicator SSN present --0000-- Global Title Indicator No global title included -1------ Routing Indicator Route on DPC + Subsystem No. 0------- For national use 0 ******** Called Party SPC 408 00------ Spare 11111110 Subsystem number BSSAP Calling address parameter 00000100 Parameter Length 4 -------1 Point Code Indicator PC present ------1- Subsystem No. Indicator SSN present --0000-- Global Title Indicator No global title included -1------ Routing Indicator Route on DPC + Subsystem No. 0------- For national use 0 ******** Calling Party SPC 3050 00------ Spare 11111110 Subsystem number BSSAP Data parameter 00010101 Parameter length 21 ******** Data 00 13 52 08 08 29 26 20 26 00 00 00 70 1A 06 04 62 F2 20 00 01 bmap PAGIN E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) 3DJLQJ 3$*,1 -------0 Discrimination bit D BSSMAP 0000000- Filler 00010011 Message Length 19 01010010 Message Type 0x52 IMSI 00001000 IE Name IMSI 00001000 IE Length 8 -----001 Type of identity IMSI ----1--- Odd/Even Indicator Odd no of digits ******** IMSI digits 262026200000007 Cell Identifier List 00011010 IE Name Cell identifier list 00000110 IE Length 6 ----0100 Cell ID Discriminator LAI used to ident cell 0000---- Spare
5-60
A30808-X5226-C559-1-7618
Siemens
******** 1111-------0000 0010---********
MCC number Filler MNC digit 1 MNC digit 2 LAC
262 0 2 1
15:20:55"1 bss sccp 83 3050 408 4 CR ITU-T WHITE BOOK SCCP (sccp) &RQQHFWLRQ 5HTXHVW &5 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 3050 ******** Originating Point Code 408 ******** Signalling Link Selection 4 00000001 SCCP Message Type 0x1 ******** Source Local Reference 0x602100 ----0010 Protocol Class Class 2 0000---- Spare 00000010 Ptr to Called address pa 2 00000100 Ptr to optional param. 4 Called address parameter 00000010 Parameter Length 2 -------0 Point Code Indicator PC absent ------1- Subsystem No. Indicator SSN present --0000-- Global Title Indicator No global title included -1------ Routing Indicator Route on DPC + Subsystem No. 0------- For national use 0 11111110 Subsystem number BSSAP Data parameter 00001111 Parameter name Data 00011011 Parameter length 27 ******** Data 00 19 57 05 05 01 00 01 00 1A 17 0F 06 27 07 02 03 08 08 29 26 20 26 00 00 00 70 00000000 Parameter name End of Optional Params bmap CL3I E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) &RPSO OD\HU LQIRUP &/, -------0 Discrimination bit D BSSMAP 0000000- Filler 00011001 Message Length 25 01010111 Message Type 0x57 Cell Identifier 00000101 IE Name Cell identifier 00000101 IE Length 5 ----0001 Cell ID discriminator LAC/CI used to ident cell ******** LAC 1 ******** CI 26 LAyer 3 Information 00010111 IE Name Layer 3 information 00001111 IE Length 15 ******** L3 Message Contents 06 27 07 02 03 08 08 29 26 20 26 00 00 00 70 dtap 6 PAGRES RR Message Paging message
A30808-X5226-C559-1-7618
5-61
Siemens
E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) 3DJLQJ UHVSRQVH 3$*5(6 ----0110 Protocol Discriminator radio resources management msg -000---- Transaction Id value TI value 0 0------- Transaction Id flag message sent from orig TI -0100111 Message Type 0x27 0------- Extension bit ----0111 Key sequence no key available/reserved 0000---- Spare Mobile Station Classmark 2 00000010 IE Length 2 -----011 RF power capability Class 4 ----0--- A5/1 algorithm supported Available ---0---- Spare -00----- Revision level Reserved for phase 1 0------- Spare -------0 Frequency capability MS does not support the ext. band G1 -----00- Spare ----1--- SM capability --00---- SS Screening Indicator -0------ PS capability 0------- Spare Mobile IDentity 00001000 IE Length -----001 Type of identity ----1--- Odd/Even Indicator ******** Identity digits Present Phase 1 Not present
8 IMSI Odd no of digits 262026200000007
5-62
A30808-X5226-C559-1-7618
Siemens
15:20:55"2 msc sccp 83 408 3050 6 CC ITU-T WHITE BOOK SCCP (sccp) &RQQHFWLRQ &RQILUP && ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 408 ******** Originating Point Code 3050 ******** Signalling Link Selection 6 00000010 SCCP Message Type 0x2 ******** Destination Local Ref. 0x602100 ******** Source Local Reference 0x422021 ----0010 Protocol Class Class 2 0000---- Spare 00000001 Ptr to optional param. 1 Data parameter 00001111 Parameter name Data 00001010 Parameter length 10 ******** Data 00 08 53 07 02 06 00 0A 01 01 00000000 Parameter name End of Optional Params bmap CICMD E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) &LSKHU 0RGH &RPPDQG &,&0' -------0 Discrimination bit D BSSMAP 0000000- Filler 00001000 Message Length 8 01010011 Message Type 0x53 Layer 3 header INformation 00000111 IE Name Layer 3 header information 00000010 IE Length 2 ----0110 Protocol Discriminator radio resources management msg 0000---- Spare -----000 Transaction Id value TI value 0 ----0--- Transaction Id flag message sent from orig TI 0000---- Spare Encryption Information 00001010 IE Name Encryption information 00000001 IE Length 1 -------1 No encryption May be used ------0- GSM A5/1 Not used -----0-- GSM A5/2 Not used ----0--- GSM A5/3 Not used ---0---- GSM A5/4 Not used --0----- GSM A5/5 Not used -0------ GSM A5/6 Not used 0------- GSM A5/7 Not used
A30808-X5226-C559-1-7618
5-63
Siemens
15:20:55"8 bss sccp 83 3050 408 4 DT1 ITU-T WHITE BOOK SCCP (sccp) 'DWD )RUP '7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 3050 ******** Originating Point Code 408 ******** Signalling Link Selection 4 00000110 SCCP Message Type 0x6 ******** Destination Local Ref. 0x422021 -------0 Segment/reass M indicator No more data 0000000- Spare 00000001 Ptr to Data parameter 1 Data parameter 00000011 Parameter length 3 ******** Data 00 01 55 bmap CICMP E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) &LSKHU 0RGH &RPSOHWH &,&03 -------0 Discrimination bit D BSSMAP 0000000- Filler 00000001 Message Length 1 01010101 Message Type 0x55
15:20:55"8 msc sccp 83 408 3050 6 DT1 ITU-T WHITE BOOK SCCP (sccp) 'DWD )RUP '7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 408 ******** Originating Point Code 3050 ******** Signalling Link Selection 6 00000110 SCCP Message Type 0x6 ******** Destination Local Ref. 0x602100 -------0 Segment/reass M indicator No more data 0000000- Spare 00000001 Ptr to Data parameter 1 Data parameter 00000110 Parameter length 6 ******** Data 01 00 03 05 18 02 dtap 5 IDREQ MM Message Security message E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) ,GHQWLW\ UHTXHVW ,'5(4 -------1 Discrimination bit D DTAP 0000000- Filler -----000 SAPI Signalling --000--- Spare 00------ Radio channel id fACCH or sDCCH 00000011 Message Length 3 ----0101 Protocol Discriminator mobility management msg -000---- Transaction Id value TI value 0 0------- Transaction Id flag message sent from orig TI --011000 Message Type 0x18 -0------ Send Sequence Number 0 0------- Extension bit -----010 Type of identity IMEI ----0--- Spare 0000---- Spare
5-64
A30808-X5226-C559-1-7618
Siemens
15:20:55"9 msc sccp 83 408 3050 6 DT1 ITU-T WHITE BOOK SCCP (sccp) 'DWD )RUP '7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 408 ******** Originating Point Code 3050 ******** Signalling Link Selection 6 00000110 SCCP Message Type 0x6 ******** Destination Local Ref. 0x602100 -------0 Segment/reass M indicator No more data 0000000- Spare 00000001 Ptr to Data parameter 1 Data parameter 00010000 Parameter length 16 ******** Data 01 00 0D 13 05 04 01 A0 1E 02 EA 83 7D 02 91 81 dtap 3 SETUP CC Message Call establishment message E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) 6HWXS 6(783 -------1 Discrimination bit D DTAP 0000000- Filler -----000 SAPI Signalling --000--- Spare 00------ Radio channel id fACCH or sDCCH 00001101 Message Length 13 ----0011 Protocol Discriminator Call/Connection control, CR SS -001---- Transaction Id value TI value 1 0------- Transaction Id flag message sent from orig TI --000101 Message Type 0x5 -0------ Send Sequence Number 0 0------- Extension bit Bearer Capability 00000100 IE Name Bearer Capability 00000001 IE Length 1 -----000 Info transfer capability Speech ----0--- Transfer mode Circuit mode ---0---- Coding standard GSM standardized coding -01----- Radio channel requirement Full rate channel 1------- Extension bit No Extension Progress Indicator 00011110 IE Name Progress Indicator 00000010 IE Length 2 ----1010 Location NTW beyond interworking point ---0---- Spare -11----- Coding standard Standard for the GSM PLMNS 1------- Extension bit No Extension -0000011 Progress description Origination address 1------- Extension bit No Extension High Layer Compatibility 01111101 IE Name High Layer Compatibility 00000010 IE Length 2 ------01 Pres. of protocol profile Highlayer protocol profile ---100-- Interpretation Highlayer characteristics ID -00----- Coding standard Standardized coding 1------- Extension bit No Extension -0000001 High layer character. ID Telephony 1------- Extension bit No Extension
A30808-X5226-C559-1-7618
5-65
Siemens
15:20:56"5 bss sccp 83 3050 408 4 DT1 ITU-T WHITE BOOK SCCP (sccp) 'DWD )RUP '7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 3050 ******** Originating Point Code 408 ******** Signalling Link Selection 4 00000110 SCCP Message Type 0x6 ******** Destination Local Ref. 0x422021 -------0 Segment/reass M indicator No more data 0000000- Spare 00000001 Ptr to Data parameter 1 Data parameter 00001110 Parameter length 14 ******** Data 01 00 0B 05 19 08 4A 09 21 42 51 50 43 09 dtap 5 IDRES MM Message Security message E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) ,GHQWLW\ UHVSRQVH ,'5(6 -------1 Discrimination bit D DTAP 0000000- Filler -----000 SAPI Signalling --000--- Spare 00------ Radio channel id fACCH or sDCCH 00001011 Message Length 11 ----0101 Protocol Discriminator mobility management msg -000---- Transaction Id value TI value 0 0------- Transaction Id flag message sent from orig TI --011001 Message Type 0x19 -0------ Send Sequence Number 0 0------- Extension bit Mobile IDentity 00001000 IE Length 8 -----010 Type of identity IMEI ----1--- Odd/Even Indicator Odd no of digits ******** Identity digits 490122415053490
5-66
A30808-X5226-C559-1-7618
Siemens
15:20:56"7 bss sccp 83 3050 408 4 DT1 ITU-T WHITE BOOK SCCP (sccp) 'DWD )RUP '7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 3050 ******** Originating Point Code 408 ******** Signalling Link Selection 4 00000110 SCCP Message Type 0x6 ******** Destination Local Ref. 0x422021 -------0 Segment/reass M indicator No more data 0000000- Spare 00000001 Ptr to Data parameter 1 Data parameter 00000101 Parameter length 5 ******** Data 01 00 02 93 48 dtap 3 CCONF CC Message Call establishment message E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) &DOO FRQILUPHG &&21) -------1 Discrimination bit D DTAP 0000000- Filler -----000 SAPI Signalling --000--- Spare 00------ Radio channel id fACCH or sDCCH 00000010 Message Length 2 ----0011 Protocol Discriminator Call/Connection control, CR SS -001---- Transaction Id value TI value 1 1------- Transaction Id flag message sent to orig TI --001000 Message Type 0x8 -1------ Send Sequence Number 1 0------- Extension bit
A30808-X5226-C559-1-7618
5-67
Siemens
15:20:56"9 msc sccp 83 408 3050 6 DT1 ITU-T WHITE BOOK SCCP (sccp) 'DWD )RUP '7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 408 ******** Originating Point Code 3050 ******** Signalling Link Selection 6 00000110 SCCP Message Type 0x6 ******** Destination Local Ref. 0x602100 -------0 Segment/reass M indicator No more data 0000000- Spare 00000001 Ptr to Data parameter 1 Data parameter 00010100 Parameter length 20 ******** Data 00 12 01 0B 03 01 08 01 07 02 06 00 06 01 19 01 00 05 19 01 bmap ASREQ E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) $66LJQPHQW 5(4HVW $65(4 -------0 Discrimination bit D BSSMAP 0000000- Filler 00010010 Message Length 18 00000001 Message Type 0x1 Channel Type 00001011 IE Name Channel type 00000011 IE Length 3 00000001 Speech/Data Indicator Speech 00001000 Channel Rate/Type Full rate TCH channel Bm 00000001 Speech Encoding Algorithm GSM speech algorithm Ver 1 Layer 3 header INformation 00000111 IE Name Layer 3 header information 00000010 IE Length 2 ----0110 Protocol Discriminator radio resources management msg 0000---- Spare -----000 Transaction Id value TI value 0 ----0--- Transaction Id flag message sent from orig TI 0000---- Spare PRIority 00000110 IE Name Priority 00000001 IE Length 1 -------1 Preemption Vulnerab. Ind Might be prerempted ------0- Queueing allowed ind not allowed --0110-- Priority level 6 -0------ Preemption Capability ind not allowed 0------- Spare Circuit Identity Code 00000001 IE Name Circuit identity code 00000000 PCM Multiplex a-h 0 000----- PCM Multiplex i-k 0 ---00101 Timeslot in use 5 Downlink DTX flag 00011001 IE Name Downlink DTX flag -------1 DTX in downlink direction forbidden 0000000- Spare
5-68
A30808-X5226-C559-1-7618
Siemens
15:20:57"9 bss sccp 83 3050 408 4 DT1 ITU-T WHITE BOOK SCCP (sccp) 'DWD )RUP '7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 3050 ******** Originating Point Code 408 ******** Signalling Link Selection 4 00000110 SCCP Message Type 0x6 ******** Destination Local Ref. 0x422021 -------0 Segment/reass M indicator No more data 0000000- Spare 00000001 Ptr to Data parameter 1 Data parameter 00000011 Parameter length 3 ******** Data 00 01 02 bmap ASCMP E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) $66LJQPHQW &20SOHWH $6&03 -------0 Discrimination bit D BSSMAP 0000000- Filler 00000001 Message Length 1 00000010 Message Type 0x2
15:20:58"0 bss sccp 83 3050 408 4 DT1 ITU-T WHITE BOOK SCCP (sccp) 'DWD )RUP '7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 3050 ******** Originating Point Code 408 ******** Signalling Link Selection 4 00000110 SCCP Message Type 0x6 ******** Destination Local Ref. 0x422021 -------0 Segment/reass M indicator No more data 0000000- Spare 00000001 Ptr to Data parameter 1 Data parameter 00000101 Parameter length 5 ******** Data 01 00 02 93 01 dtap 3 ALERT CC Message Call establishment message E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) $OHUWLQJ $/(57 -------1 Discrimination bit D DTAP 0000000- Filler -----000 SAPI Signalling --000--- Spare 00------ Radio channel id fACCH or sDCCH 00000010 Message Length 2 ----0011 Protocol Discriminator Call/Connection control, CR SS -001---- Transaction Id value TI value 1 1------- Transaction Id flag message sent to orig TI --000001 Message Type 0x1 -0------ Send Sequence Number 0 0------- Extension bit
A30808-X5226-C559-1-7618
5-69
Siemens
15:20:58"1 msc sccp 83 408 3050 11 DT1 ITU-T WHITE BOOK SCCP (sccp) 'DWD )RUP '7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 408 ******** Originating Point Code 3050 ******** Signalling Link Selection 11 00000110 SCCP Message Type 0x6 ******** Destination Local Ref. 0x202C00 -------0 Segment/reass M indicator No more data 0000000- Spare 00000001 Ptr to Data parameter 1 Data parameter 00001001 Parameter length 9 ******** Data 01 00 06 83 01 1E 02 EA 88 dtap 3 ALERT CC Message Call establishment message E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) $OHUWLQJ $/(57 -------1 Discrimination bit D DTAP 0000000- Filler -----000 SAPI Signalling --000--- Spare 00------ Radio channel id fACCH or sDCCH 00000110 Message Length 6 ----0011 Protocol Discriminator Call/Connection control, CR SS -000---- Transaction Id value TI value 0 1------- Transaction Id flag message sent to orig TI --000001 Message Type 0x1 -0------ Send Sequence Number 0 0------- Extension bit Progress Indicator 00011110 IE Name Progress Indicator 00000010 IE Length 2 ----1010 Location NTW beyond interworking point ---0---- Spare -11----- Coding standard Standard for the GSM PLMNS 1------- Extension bit No Extension -0001000 Progress description Info/pattern now available 1------- Extension bit No Extension
5-70
A30808-X5226-C559-1-7618
Siemens
15:21:00"8 bss sccp 83 3050 408 4 DT1 ITU-T WHITE BOOK SCCP (sccp) 'DWD )RUP '7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 3050 ******** Originating Point Code 408 ******** Signalling Link Selection 4 00000110 SCCP Message Type 0x6 ******** Destination Local Ref. 0x422021 -------0 Segment/reass M indicator No more data 0000000- Spare 00000001 Ptr to Data parameter 1 Data parameter 00000101 Parameter length 5 ******** Data 01 00 02 93 47 dtap 3 CONNECT CC Message Call establishment message E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) &RQQHFW &211(&7 -------1 Discrimination bit D DTAP 0000000- Filler -----000 SAPI Signalling --000--- Spare 00------ Radio channel id fACCH or sDCCH 00000010 Message Length 2 ----0011 Protocol Discriminator Call/Connection control, CR SS -001---- Transaction Id value TI value 1 1------- Transaction Id flag message sent to orig TI --000111 Message Type 0x7 -1------ Send Sequence Number 1 0------- Extension bit
A30808-X5226-C559-1-7618
5-71
Siemens
15:21:00"8 msc sccp 83 408 3050 6 DT1 ITU-T WHITE BOOK SCCP (sccp) 'DWD )RUP '7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 408 ******** Originating Point Code 3050 ******** Signalling Link Selection 6 00000110 SCCP Message Type 0x6 ******** Destination Local Ref. 0x602100 -------0 Segment/reass M indicator No more data 0000000- Spare 00000001 Ptr to Data parameter 1 Data parameter 00000101 Parameter length 5 ******** Data 01 00 02 13 0F dtap 3 CONACK CC Message Call establishment message E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) &RQQHFW DFNQRZOHGJH &21$&. -------1 Discrimination bit D DTAP 0000000- Filler -----000 SAPI Signalling --000--- Spare 00------ Radio channel id fACCH or sDCCH 00000010 Message Length 2 ----0011 Protocol Discriminator Call/Connection control, CR SS -001---- Transaction Id value TI value 1 0------- Transaction Id flag message sent from orig TI --001111 Message Type 0xF -0------ Send Sequence Number 0 0------- Extension bit
5-72
A30808-X5226-C559-1-7618
Siemens
15:21:00"9 msc sccp 83 408 3050 11 DT1 ITU-T WHITE BOOK SCCP (sccp) 'DWD )RUP '7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 408 ******** Originating Point Code 3050 ******** Signalling Link Selection 11 00000110 SCCP Message Type 0x6 ******** Destination Local Ref. 0x202C00 -------0 Segment/reass M indicator No more data 0000000- Spare 00000001 Ptr to Data parameter 1 Data parameter 00000101 Parameter length 5 ******** Data 01 00 02 83 07 dtap 3 CONNECT CC Message Call establishment message E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) &RQQHFW &211(&7 -------1 Discrimination bit D DTAP 0000000- Filler -----000 SAPI Signalling --000--- Spare 00------ Radio channel id fACCH or sDCCH 00000010 Message Length 2 ----0011 Protocol Discriminator Call/Connection control, CR SS -000---- Transaction Id value TI value 0 1------- Transaction Id flag message sent to orig TI --000111 Message Type 0x7 -0------ Send Sequence Number 0 0------- Extension bit
A30808-X5226-C559-1-7618
5-73
Siemens
15:21:01"0 bss sccp 83 3050 408 5 DT1 ITU-T WHITE BOOK SCCP (sccp) 'DWD )RUP '7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 3050 ******** Originating Point Code 408 ******** Signalling Link Selection 5 00000110 SCCP Message Type 0x6 ******** Destination Local Ref. 0x402021 -------0 Segment/reass M indicator No more data 0000000- Spare 00000001 Ptr to Data parameter 1 Data parameter 00000101 Parameter length 5 ******** Data 01 00 02 03 4F dtap 3 CONACK CC Message Call establishment message E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) &RQQHFW DFNQRZOHGJH &21$&. -------1 Discrimination bit D DTAP 0000000- Filler -----000 SAPI Signalling --000--- Spare 00------ Radio channel id fACCH or sDCCH 00000010 Message Length 2 ----0011 Protocol Discriminator Call/Connection control, CR SS -000---- Transaction Id value TI value 0 0------- Transaction Id flag message sent from orig TI --001111 Message Type 0xF -1------ Send Sequence Number 1 0------- Extension bit
5-74
A30808-X5226-C559-1-7618
Siemens
15:21:08"1 bss sccp 83 3050 408 5 DT1 ITU-T WHITE BOOK SCCP (sccp) 'DWD )RUP '7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 3050 ******** Originating Point Code 408 ******** Signalling Link Selection 5 00000110 SCCP Message Type 0x6 ******** Destination Local Ref. 0x402021 -------0 Segment/reass M indicator No more data 0000000- Spare 00000001 Ptr to Data parameter 1 Data parameter 00001000 Parameter length 8 ******** Data 01 00 05 03 25 02 E0 90 dtap 3 DISC CC Message Call clearing message E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) 'LVFRQQHFW ',6& -------1 Discrimination bit D DTAP 0000000- Filler -----000 SAPI Signalling --000--- Spare 00------ Radio channel id fACCH or sDCCH 00000101 Message Length 5 ----0011 Protocol Discriminator Call/Connection control, CR SS -000---- Transaction Id value TI value 0 0------- Transaction Id flag message sent from orig TI --100101 Message Type 0x25 -0------ Send Sequence Number 0 0------- Extension bit Cause 00000010 IE Length 2 ----0000 Location User ---0---- Spare -11----- Coding standard Standard for the GSM PLMNS 1------- Extension bit No Extension -0010000 Cause value Normal call clearing 1------- Extension bit No Extension
A30808-X5226-C559-1-7618
5-75
Siemens
15:21:08"2 msc sccp 83 408 3050 11 DT1 ITU-T WHITE BOOK SCCP (sccp) 'DWD )RUP '7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 408 ******** Originating Point Code 3050 ******** Signalling Link Selection 11 00000110 SCCP Message Type 0x6 ******** Destination Local Ref. 0x202C00 -------0 Segment/reass M indicator No more data 0000000- Spare 00000001 Ptr to Data parameter 1 Data parameter 00001001 Parameter length 9 ******** Data 01 00 06 83 2D 08 02 E0 90 dtap 3 RELEAS CC Message Call clearing message E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) 5HOHDVH 5(/($6 -------1 Discrimination bit D DTAP 0000000- Filler -----000 SAPI Signalling --000--- Spare 00------ Radio channel id fACCH or sDCCH 00000110 Message Length 6 ----0011 Protocol Discriminator Call/Connection control, CR SS -000---- Transaction Id value TI value 0 1------- Transaction Id flag message sent to orig TI --101101 Message Type 0x2D -0------ Send Sequence Number 0 0------- Extension bit Cause 00001000 IE Name Cause 00000010 IE Length 2 ----0000 Location User ---0---- Spare -11----- Coding standard Standard for the GSM PLMNS 1------- Extension bit No Extension -0010000 Cause value Normal call clearing 1------- Extension bit No Extension
5-76
A30808-X5226-C559-1-7618
Siemens
15:21:08"2 msc sccp 83 408 3050 6 DT1 ITU-T WHITE BOOK SCCP (sccp) 'DWD )RUP '7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 408 ******** Originating Point Code 3050 ******** Signalling Link Selection 6 00000110 SCCP Message Type 0x6 ******** Destination Local Ref. 0x602100 -------0 Segment/reass M indicator No more data 0000000- Spare 00000001 Ptr to Data parameter 1 Data parameter 00001001 Parameter length 9 ******** Data 01 00 06 13 2D 08 02 E0 90 dtap 3 RELEAS CC Message Call clearing message E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) 5HOHDVH 5(/($6 -------1 Discrimination bit D DTAP 0000000- Filler -----000 SAPI Signalling --000--- Spare 00------ Radio channel id fACCH or sDCCH 00000110 Message Length 6 ----0011 Protocol Discriminator Call/Connection control, CR SS -001---- Transaction Id value TI value 1 0------- Transaction Id flag message sent from orig TI --101101 Message Type 0x2D -0------ Send Sequence Number 0 0------- Extension bit Cause 00001000 IE Name Cause 00000010 IE Length 2 ----0000 Location User ---0---- Spare -11----- Coding standard Standard for the GSM PLMNS 1------- Extension bit No Extension -0010000 Cause value Normal call clearing 1------- Extension bit No Extension
A30808-X5226-C559-1-7618
5-77
Siemens
15:21:08"4 bss sccp 83 3050 408 5 DT1 ITU-T WHITE BOOK SCCP (sccp) 'DWD )RUP '7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 3050 ******** Originating Point Code 408 ******** Signalling Link Selection 5 00000110 SCCP Message Type 0x6 ******** Destination Local Ref. 0x402021 -------0 Segment/reass M indicator No more data 0000000- Spare 00000001 Ptr to Data parameter 1 Data parameter 00000101 Parameter length 5 ******** Data 01 00 02 03 6A dtap 3 RELCMP CC Message Call clearing message E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) 5HOHDVH FRPSOHWH 5(/&03 -------1 Discrimination bit D DTAP 0000000- Filler -----000 SAPI Signalling --000--- Spare 00------ Radio channel id fACCH or sDCCH 00000010 Message Length 2 ----0011 Protocol Discriminator Call/Connection control, CR SS -000---- Transaction Id value TI value 0 0------- Transaction Id flag message sent from orig TI --101010 Message Type 0x2A -1------ Send Sequence Number 1 0------- Extension bit
5-78
A30808-X5226-C559-1-7618
Siemens
15:21:08"4 bss sccp 83 3050 408 4 DT1 ITU-T WHITE BOOK SCCP (sccp) 'DWD )RUP '7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 3050 ******** Originating Point Code 408 ******** Signalling Link Selection 4 00000110 SCCP Message Type 0x6 ******** Destination Local Ref. 0x422021 -------0 Segment/reass M indicator No more data 0000000- Spare 00000001 Ptr to Data parameter 1 Data parameter 00000101 Parameter length 5 ******** Data 01 00 02 93 2A dtap 3 RELCMP CC Message Call clearing message E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) 5HOHDVH FRPSOHWH 5(/&03 -------1 Discrimination bit D DTAP 0000000- Filler -----000 SAPI Signalling --000--- Spare 00------ Radio channel id fACCH or sDCCH 00000010 Message Length 2 ----0011 Protocol Discriminator Call/Connection control, CR SS -001---- Transaction Id value TI value 1 1------- Transaction Id flag message sent to orig TI --101010 Message Type 0x2A -0------ Send Sequence Number 0 0------- Extension bit
A30808-X5226-C559-1-7618
5-79
Siemens
15:21:08"4 msc sccp 83 408 3050 11 DT1 ITU-T WHITE BOOK SCCP (sccp) 'DWD )RUP '7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 408 ******** Originating Point Code 3050 ******** Signalling Link Selection 11 00000110 SCCP Message Type 0x6 ******** Destination Local Ref. 0x202C00 -------0 Segment/reass M indicator No more data 0000000- Spare 00000001 Ptr to Data parameter 1 Data parameter 00001010 Parameter length 10 ******** Data 00 08 20 07 02 06 00 04 01 09 bmap CLCMD E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) &/HD5 &R0PDQ' &/&0' -------0 Discrimination bit D BSSMAP 0000000- Filler 00001000 Message Length 8 00100000 Message Type 0x20 Layer 3 header INformation 00000111 IE Name Layer 3 header information 00000010 IE Length 2 ----0110 Protocol Discriminator radio resources management msg 0000---- Spare -----000 Transaction Id value TI value 0 ----0--- Transaction Id flag message sent from orig TI 0000---- Spare CAUse 00000100 IE Name Cause 00000001 IE Length 1 -0001001 Cause value Call control 0------- Cause Extension No Extension
5-80
A30808-X5226-C559-1-7618
Siemens
15:21:08"5 bss sccp 83 3050 408 5 DT1 ITU-T WHITE BOOK SCCP (sccp) 'DWD )RUP '7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 3050 ******** Originating Point Code 408 ******** Signalling Link Selection 5 00000110 SCCP Message Type 0x6 ******** Destination Local Ref. 0x402021 -------0 Segment/reass M indicator No more data 0000000- Spare 00000001 Ptr to Data parameter 1 Data parameter 00000011 Parameter length 3 ******** Data 00 01 21 bmap CLCMP E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) &OHD5 &20SOHWH &/&03 -------0 Discrimination bit D BSSMAP 0000000- Filler 00000001 Message Length 1 00100001 Message Type 0x21
15:21:08"5 msc sccp 83 408 3050 6 DT1 ITU-T WHITE BOOK SCCP (sccp) 'DWD )RUP '7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 408 ******** Originating Point Code 3050 ******** Signalling Link Selection 6 00000110 SCCP Message Type 0x6 ******** Destination Local Ref. 0x602100 -------0 Segment/reass M indicator No more data 0000000- Spare 00000001 Ptr to Data parameter 1 Data parameter 00001010 Parameter length 10 ******** Data 00 08 20 07 02 06 00 04 01 09 bmap CLCMD E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) &/HD5 &R0PDQ' &/&0' -------0 Discrimination bit D BSSMAP 0000000- Filler 00001000 Message Length 8 00100000 Message Type 0x20 Layer 3 header INformation 00000111 IE Name Layer 3 header information 00000010 IE Length 2 ----0110 Protocol Discriminator radio resources management msg 0000---- Spare -----000 Transaction Id value TI value 0 ----0--- Transaction Id flag message sent from orig TI 0000---- Spare CAUse 00000100 IE Name Cause 00000001 IE Length 1 -0001001 Cause value Call control 0------- Cause Extension No Extension
A30808-X5226-C559-1-7618
5-81
Siemens
15:21:08"5 msc sccp 83 408 3050 11 RLSD ITU-T WHITE BOOK SCCP (sccp) 5HOHDVHG 5/6' ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 408 ******** Originating Point Code 3050 ******** Signalling Link Selection 11 00000100 SCCP Message Type 0x4 ******** Destination Local Ref. 0x202C00 ******** Source Local Reference 0x402021 00000000 Release Cause End user originated 00000000 Ptr to optional param. 0
15:21:08"5 bss sccp 83 3050 408 4 DT1 ITU-T WHITE BOOK SCCP (sccp) 'DWD )RUP '7 ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 3050 ******** Originating Point Code 408 ******** Signalling Link Selection 4 00000110 SCCP Message Type 0x6 ******** Destination Local Ref. 0x422021 -------0 Segment/reass M indicator No more data 0000000- Spare 00000001 Ptr to Data parameter 1 Data parameter 00000011 Parameter length 3 ******** Data 00 01 21 bmap CLCMP E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) CleaR COMplete (CLCMP) -------0 Discrimination bit D BSSMAP 0000000- Filler 00000001 Message Length 1 00100001 Message Type 0x21
15:21:08"5 bss sccp 83 3050 408 5 RLC ITU-T WHITE BOOK SCCP (sccp) 5HOHDVH &RPSOHWH 5/& ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 3050 ******** Originating Point Code 408 ******** Signalling Link Selection 5 00000101 SCCP Message Type 0x5 ******** Destination Local Ref. 0x402021 ******** Source Local Reference 0x202C00
5-82
A30808-X5226-C559-1-7618
Siemens
15:21:08"5 msc sccp 83 408 3050 6 RLSD ITU-T WHITE BOOK SCCP (sccp) 5HOHDVHG 5/6' ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 408 ******** Originating Point Code 3050 ******** Signalling Link Selection 6 00000100 SCCP Message Type 0x4 ******** Destination Local Ref. 0x602100 ******** Source Local Reference 0x422021 00000000 Release Cause End user originated 00000000 Ptr to optional param. 0
15:21:08"6 bss sccp 83 3050 408 4 RLC ITU-T WHITE BOOK SCCP (sccp) 5HOHDVH &RPSOHWH 5/& ----0011 Service Indicator SCCP --00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only) 10------ Sub-Service: Network Ind National message ******** Destination Point Code 3050 ******** Originating Point Code 408 ******** Signalling Link Selection 4 00000101 SCCP Message Type 0x5 ******** Destination Local Ref. 0x422021 ******** Source Local Reference 0x602100
A30808-X5226-C559-1-7618
5-83
Siemens
5-84
A30808-X5226-C559-1-7618
Synchronization
Siemens
6\QFKURQL]DWLRQ
&RQWHQWV
1 1.1 1.2 1.3 2 3 3.1 3.2 4 4.1 4.2 5 6 6.1 6.2 7 Introduction to Synchronization Why is it so Important to have Synchronous Networks? What has to be Synchronized? How can a Network be Synchronized ? Planning of Synchronization and Clock Distribution Synchronization in PDH Networks Characteristics of PDH Networks (Focus on Synchronization) Synchronization Aspects for PDH Networks Synchronization in SDH Networks Characteristics of SDH Networks (Focus on Synchronization) Synchronization Aspects for SDH Networks Examples Appendix Summary of the Principles of PDH Multiplexing Summary of the Principles of SDH Multiplexing Exercise 3 3 4 5 6 11 11 12 13 13 13 15 18 18 19 20
A30808-X5226-C559-1-7618
6-1
Siemens
Synchronization
Page intentionally left blank
6-2
A30808-X5226-C559-1-7618
Synchronization
Siemens
,QWURGXFWLRQ WR 6\QFKURQL]DWLRQ
Network synchronization is something which is hardly noticed as long as it works, but many mysterious faults result from improper synchronization. The problems of network synchronization have increased with the introduction of new transport and switching technologies and with the liberalization in the telecommunication market. The intention of this subsection is : to make aware that synchronization is an important issue, and to provide information about synchronization in the SBS.

:K\ LV LW VR ,PSRUWDQW WR KDYH 6\QFKURQRXV 1HWZRUNV"
Imagine, you would be a network operator offering services like telephone, fax, multimedia, transmission of digital data, encrypted text, ..., your customers would probably not be content if they often have effects like: 6HUYLFH Voice (IIHFW Possible 'click', loss of signaling data (CCS7). Handover problems and interruption of calls in mobile phone networks (GSM). Deletion of 4 to 8 scan lines or reduced throughput (increased transmission time). Video frames frozen for several seconds, noise burst on audio. Encryption key must be retransmitted. Deletion or repetition of data, reduction of throughput.
Fax Multimedia Encrypted text Digital data
All of these effects, among many others, may result from synchronization problems in your network or in other networks in which your customer's data are transported. The problems are increasing rapidly due to the increasing complexity of the networks, the increasing number of technologies (SDH, ATM,...) and due to the increasing number of operators in the liberalized telecommunication markets.
A30808-X5226-C559-1-7618
6-3
Siemens
Synchronization

:KDW KDV WR EH 6\QFKURQL]HG"
Most of todays digital communication networks are based on PCM (Pulse Code Modulation)-coded signals. Multiplexing is done in the time domain by arranging the 64kbit/s base signals in time slots relative to a reference signal (frame). Switching is done in a combination of space switches and time switches (time slot interchange). Time domain switching or multiplexing requires that the time slots are equal in all equipments assembling, disassembling or switching those signals. The time slot procedure needs elastic data buffers to compensate for wander-induced delay variations of the incoming data. Periodic over- or underflow of those buffers (equivalent to a frequency difference) results in regular frame slips which corrupt the integrity of the signal. Depending on the type of service affected by the slips the impacts are more or less severe, some effects are listed in the table above. Consequently the following network elements have to be synchronized (examples):
z
Digital exchanges: Public exchanges, Private exchanges, Mobile switches.
Network elements in SDH (Synchronous Digital Hierarchy) networks: Multiplexers, Line Terminations, Cross Connects, Regenerators.
z z
Base stations of mobile networks. ATM network elements, if they have CBR (Constant Bit Rate) interfaces.
6-4
A30808-X5226-C559-1-7618
Synchronization
Siemens

+RZ FDQ D 1HWZRUN EH 6\QFKURQL]HG "
The task sounds simple: operate all equipment that has to be synchronized at the same frequency and a fixed phase relation. Achieving that state is not so easy because the absolute frequency accuracy has to be very high, in order to allow interworking between different networks. The required accuracy is in the range of 1exp-11 (from the nominal value), which can currently only be guaranteed with atomic frequency references. Obviously it is not reasonable to equip each network element with an atomic clock, so the solution is to distribute a reference signal with the required accuracy from a master clock, the Primary Reference Clock, to all network elements for controlling their internal clocks (slave clocks). This results in a Synchronization Network which is logically separate from the communication network. This Synchronization Network has its own architecture, many special requirements, special equipment, a special communication channel (in SDH networks), and maybe a separate management. Physically the Synchronization Network uses partly paths in the communication network and partly paths dedicated to synchronization. This is not the place to go into details, but the message here is: Synchronization can cause a lot of trouble, so it has to be considered in all levels of a network and in all phases of a network project !
A30808-X5226-C559-1-7618
6-5
Siemens
Synchronization
3ODQQLQJ RI 6\QFKURQL]DWLRQ DQG &ORFN 'LVWULEXWLRQ
The following example illustrates the synchronization planning process. The planning of synchronization and clock distribution in Switching and Transmission Networks can be supported by a specific SIEMENS tool which is called 6,&$36\QF. The topology of a physical transmission network. This is the starting point for planning the clock distribution. Each node represents a unit which has to be supplied with the network clock. The lines between the nodes represent the links (cable links, radio links)
A B O H R F I P C D K S X = Network Node L M N
Fig. 1
6-6
A30808-X5226-C559-1-7618
Synchronization
Siemens
A suitable node has to be determined as master node, that means at this node the primary reference clock (PRC) has to be installed. All the remaining nodes must be supplied from this central point. The selection of the master node should be driven by the following arguments: The distribution hierarchy should be as flat as possible. Evenly balanced clock trees (nearly equal number of nodes per subtree). Maximum possible number of nodes in the first hierarchy level.
A B O H E R I P C D F N
K = Station F as PRC X = Station/Network Node L S M
Fig. 2
A30808-X5226-C559-1-7618
6-7
Siemens
Synchronization
A B O F R E H N PRC I P D C K S = Direction of Clock Transportation L = PRC Node X = Network Node M
Fig. 3 In this figure, a possible result of the planning process is shown.
PRC F E B R D C S L K H I M N P A O
= Back-up Lines
= Direction of Clock Transportation
Fig. 4 A hierarchical presentation of the clock distribution.
6-8
A30808-X5226-C559-1-7618
Synchronization
Siemens
A B R3 E R R2 D R8 S = Direction of Clock Transport = Back-up-PRC Node = PRC Node X = Network Node L R1 R2 R4 = Main Ring, Interconn. of PRC and Back-up PRC = PRC connected Ring = Secondary Ring K M PRC C R4 F H R7 R1 I N P R5 R6 O
Fig. 5 Clock distribution in a ring structured network (master slave principle).
A30808-X5226-C559-1-7618
6-9
Siemens
Synchronization
Hierarchical presentation of the clock distribution in a ring structured network (master slave principle). The clock is distributed along the continuos-line arrows. The dashed arrows indicate the standby paths.
PRC Back-up F F E R3 S R8 C A R6 H F R2 C F R1 PRC I
C R4
I M
I R5
N F = Direction of Clock Transportation with Indication of the Transition Node

Fig. 6
P R7
6-10
A30808-X5226-C559-1-7618
Synchronization
Siemens

(
6\QFKURQL]DWLRQ LQ 3'+ 1HWZRUNV

&KDUDFWHULVWLFV RI 3'+ 1HWZRUNV )RFXV RQ 6\QFKURQL]DWLRQ

PDH networks consist of switches switching 64kbit/s signals and a transport network interconnecting the switches. The transport network is a highly meshed network of point-to-point connections. The basic transport signal between switches is the 2048kbit/s signal with PCM30structure (CCITT, recommendation G.7036). Peripheral equipment is connected to the switches via 2048kbit/s or 64kbit/s signals. Higher-order transport signals (8448kbit/s, 34368kbit/s, 139264kbit/s) are generated by multiplexing signals of the next-lower level into a higher-order frame. The timing of that frame is not derived from the 2048kbit/s level, but generated locally in the multiplexer with the accuracy of the multiplexer's internal oscillator. Therefore, PDH transport signals above 2048kbit/s are not synchronous to the 2048kbit/s-level. Frequency adaptation of the tributary signals to the aggregate (multiplexed) signal is done by bit-stuffing. Due to this method the frequency of each of the tributary signals can be recovered in the demultiplexer by removing the stuff bits and filtering the demultiplexed signals for reducing the stuffing jitter. The frequency and magnitude of the stuffing events allows easy filtering. Therefore, PDH transport is clock-(frequency)-transparent.
A30808-X5226-C559-1-7618
6-11
Siemens
Synchronization

6\QFKURQL]DWLRQ $VSHFWV IRU 3'+ 1HWZRUNV
Originating from a PRC, synchronization is distributed hierarchically, using the master-slave method. The transport of the synchronization information is done in the 2048kbit/s-level. Synchronism exists only in the 2048kbit/s-level. 64kbit/s-signals multiplexed into the 2048kbit/s-level (PCM30-signal) are frequency adapted by byte-slips, if necessary. As stated above, higher-order PDH signals (above 2048kbit/s) are not synchronous to the 2048kbit/s-level, therefore those signals are normally not suitable as reference signals. Exceptions (rarely used): - The higher-order frame is generated by a multiplexer whose internal oscillator is controlled by an external reference signal derived from the 2048kbit/s level. - A 'synchronous PDH-signal' (PDH bitrate with 125s frame structure) according to ETSI ETS 300337 is used. Alternative synchronization trails are easily available, so synchronization can be distributed to each switch on two or more independent trails, determined during network planning. Those preselected synchronization signals are ordered in a priority list. In case of a failure of a reference signal the signal with the next lower priority is selected as the active reference signal. The high degree of meshing also allows a flat distribution hierarchy.
6-12
A30808-X5226-C559-1-7618
Synchronization
Siemens

6\QFKURQL]DWLRQ LQ 6'+ 1HWZRUNV

&KDUDFWHULVWLFV RI 6'+ 1HWZRUNV )RFXV RQ 6\QFKURQL]DWLRQ
Network interconnecting the switches. The transport network is a highly meshed network of point-to-point connections. The basic transport signal is the STM-1 signal (Synchronous Transport Module 1) with a bitrate of 155.52Mbit/s. The payload is transported in synchronous containers. Various container sizes are avail-able. The position of the containers in the STM-N frame is not fixed. Pointers indicate the position of the containers relative to the frame. If synchronism is disturbed or significant phase variations of the container occur, the container can be shifted within the frame. Due to the byte-structure of the signal the container can only be shifted in steps (one or three bytes). When the container is shifted, the associated pointer must be adjusted (PJE: Pointer Justification Event). Higher-level transport signals (STM-N) are generated by byte-multiplexing lower-level signals (STM-M with M<N). The bitrates of higher-level signals are integer multiples of the STM-1 bitrate. Therefore higher-level SDH transport signals (STM-N) are synchronous to lower-level signals.

6\QFKURQL]DWLRQ $VSHFWV IRU 6'+ 1HWZRUNV
Originating from a PRC, synchronization is distributed hierarchically, using the master-slave method. The transport of the synchronization information is done in the STM-N level. Synchronism exists in all signal levels (STM-N levels). As stated above, higher-order PDH signals (above 2048kbit/s) are not synchronous to the 2048kbit/s-level, therefore those signals are normally not suitable as reference signals. Exceptions (applications rare): - The higher-order frame is generated by a multiplexer whose internal oscillator is controlled by an external reference signal derived from the 2048kbit/s level. - A 'synchronous PDH-signal' (PDH bitrate with 125s frame structure) according to ETSI ETS 300337 is used.
A30808-X5226-C559-1-7618
6-13
Siemens
Synchronization
7UDQVSRUW VLJQDOV SDH transport signals (STM-N signals) consist of a frame synchronous to the network reference frequency and multiplexed containers which are nominally synchronous to the frame. Frequency and phase variations between frame and containers or between higherorder and lower-order containers are adjusted with pointer techniques. PDH signals are mapped (synchronized) into suitable containers by bit stuffing. Pointer adjustments during the transport through an SDH network cause phase jumps on the transported signals. Those phase jumps do not degrade the transport and recovery of the payload but make the transported payload signals unsuitable for synchronization, specifically in the case of 2Mbit/s signals. The frame of STM-N signals is not subject to pointer actions, therefore STM-N signals can be used for synchronization transport. 5HIHUHQFH VHOHFWLRQ IXQFWLRQDOLWLHV RI 6'+ QHWZRUN HOHPHQWV Out of the signals arriving at an SDH network element (e.g. a multiplexer or line terminating equipment) one signal is selected as reference for the system clock for internal signal processing, a second signal is selected independently for a reference output signal that may be used by other equipment. The selection of the signals is based on a priority table and on a quality information transported in SDH signals (see Synchronization status messaging). 6\QFKURQL]DWLRQ VWDWXV PHVVDJLQJ One (half-)byte in the STM-N signals is reserved for transporting synchronizationrelated messages. Those messages contain an information about the quality level of the clock signal which was used for generating the STM-N signal. An important message is the do not use for synchronization message which is used to prevent timing loops. $XWRPDWLF UHFRQILJXUDWLRQ PHFKDQLVPV With the functionalities of SDH network elements self-healing synchronization subnetworks can be created. Suitable subnetworks are e.g. Add/Drop multiplexer chains or rings. If a failure in the normal synchronization flow occurs, an alternative synchronization chain is established supplying the network elements downstream of the failure.
6-14
A30808-X5226-C559-1-7618
Synchronization
Siemens
([DPSOHV
Synchronization hierarchy in a MN network with PDH transmission (TRAU* is the so called passing TRAU which is defined by the command FUHDWH V\QF in the BSC database, TRAU** are the remaining TRAU).
PRC
MSC A
MSC D TRAU *
BSC
TRAU **
TRAU **
BTSE
BTSE BTSE BTSE
BTSE
Fig. 7
A30808-X5226-C559-1-7618
6-15
Siemens
Synchronization
via 2 Mbit/s from Public Network or other clock sources f ref 2,048 MHz f ref 2,048 MHz
T3
T3
CCG(A) MSC LTGB

2 Mbit/s Mobile Switching Center
TRAU
PLL
Transcoding and Rate Adapting Unit
ASUB
PRC
T3
STM STM
SDH
STM
2 Mbit/s
BSC
PLL
Base Station Control Equ. (Main Block Gen.)

PRC T3 SDH STM
PRC T3 STM
STM SDH STM
2 Mbit/s
STM
ABIS
STM
BTSE
PLL
BTSE
PLL
Fig. 8 Clock distribution in a MN network with SDH transmission (clock source: SDH network).
6-16
A30808-X5226-C559-1-7618
Synchronization
Siemens
via 2 Mbit/s from Public Network or other clock sources f ref 2,048 MHz from CDEX or seperate Tracking-Osc. f ref 2,048 MHz
T3
T3
CCG(A) CDEX
MSC
LTGB
2 Mbit/s
Mobile Switching Center
TRAU
PLL
T3
Transcoding and Rate Adapting Unit
ASUB
SDH
T3
STM
PDH
STM
2 Mbit/s
2 Mbit/s
BSC
PLL T3 2 Mbit/s
BSC
PLL
Base Station Control Equ. (main Glock Gen.)
ABIS
2 Mbit/s
STM STM
PDH
SDH
T3
Base Transceiver Station Equ.
BTSE
PLL
BTSE
PLL
BTSE
PLL
BTSE
PLL
Fig. 9 Clock distribution in a MN network with SDH and PDH transmission.
A30808-X5226-C559-1-7618
6-17
Siemens
Synchronization

z z
$SSHQGL[
6XPPDU\ RI WKH 3ULQFLSOHV RI 3'+ 0XOWLSOH[LQJ
PDH (Plesiochronous Digital Hierarchy) is a digital transmission technology. Bitrates in accordance with ANSI (American National Standards Institute): 1.5 Mbit/s (= basic bitrate), 6 Mbit/s, 45 Mbit/s.
Bitrates in accordance with CEPT (Conference Europeene des Administrations des Poste et des Telecommunications): 2 Mbit/s (= basic bitrate), 8 Mbit/s, 34 Mbit/s, 140 Mbit/s.
z z z
Each of these signals has a specific frame structure. With PDH bit-by-bit multiplexing is performed. The tributary signals are plesiochronous to each other: Their clock rates have the same nominal value. Nevertheless, small variations between specified limits are allowed.
6-18
A30808-X5226-C559-1-7618
Synchronization
Siemens

z z
6XPPDU\ RI WKH 3ULQFLSOHV RI 6'+ 0XOWLSOH[LQJ
SDH (Synchronous Digital Hierarchy) is a digital transmission technology (worldwide standard). Bitrates in accordance with ITU-T (International Telecommunication UnionTelecommunication Sector): STM-1 (Synchronous Transport Module-1): 155.52 Mbit/s (=basic signal for SDH) STM-4: 622.08 Mbit/s STM-16: 2.5 Gbit/s STM-N: Nx155.52 Mbit/s
z z z
The size of a STM-1 is 9x270 byte, the duration of each STM-N is 125 s. PDH or ATM signals which are to be transmitted in an SDH network first have to be packed into STM-1 modules ("mapping"). Each STM-1 module consists of 3 blocks: - Payload (tributary information) - Pointer ( indicates the start address of the tributary information in the payload block) - Section Overhead SOH with additional transmission capacity (e.g. for alarm signaling, error monitoring, ...)
SDH systems are designed for a TMN (Telecommunication Management Network). The SDH network can be monitored and the configuration of the SDH network can be adjusted very quickly via the TMN. The TMN information is transmitted in the SOH of the STM. Before multiplexing, the tributary signals are synchronized. This is done by modifying the pointer values ("pointer adjustment operation").
A30808-X5226-C559-1-7618
6-19
Siemens
Synchronization

z z
([HUFLVH
Use a sensible command to check with OMC or LMT the synchronization on the running test SBS. Is the PLLH of the test SBS properly calibrated?
6-20
A30808-X5226-C559-1-7618
Synchronization
Siemens
Consider the following OMC window:
Screenshot of a get syncOp...-NTW window at OMC.
Is everything ok?
A30808-X5226-C559-1-7618
6-21
Siemens
Synchronization
Fill in the meaning of the following parameters: 0HDQLQJ
3DUDPHWHU elapsedTime
tuneValue
DACValue
deltaNano
6-22
A30808-X5226-C559-1-7618
Synchronization
Siemens
What is the difference between Wander, Jitter, and Frequency Departure?
Wander Jitter Frequency Departure 2QH SRVVLELOLW\ WR FKHFN V\QFKURQL]DWLRQ LV WKH IROORZLQJ FRQILJXUDWLRQ For the experimental setup, compare the following sketch of a synchronization measurement on a PCM line connecting 2 EWSD.
MDF/DDF
EWSDNode
DIU 30
LT 2 Mbit/s
PCM30 PDH/SDH
2 Mbit/s
LT
DIU 30
EWSDNode
PCM30 links between: EWSD-EWSD EWSD-Mobile Phone Equipment Other PCM30 Links
2 Mbit/s
Measurement on 2 Mbit links: PCM format Level Jitter Wander (Time Intervall Error) ...
Tautron 5120 incl. Wander/Jitter Option

2,048 MHz
Elapsed
OUT IN
TIE
WAN REF IN
Rubidium Reference MRT 10-11

ser.
SIEMENS N IXD ORF
Synchronization measurement on 2 Mbit/s lines.
A30808-X5226-C559-1-7618
6-23
Siemens
Synchronization
6-24
A30808-X5226-C559-1-7618
$QDOLVDGRU .*
QGLFH *HQHUDOLGDGHV 0RQLWRUDomR QD ,QWHUIDFH $ELV 0RQLWRUDomR QD ,QWHUIDFH $
MN1788
A30808-X5226-C559-1-7618
7-1
2 $QDOLVDGRU GH 3URWRFRORV WHP DSOLFDo}HV SDUD YiULDV LQWHUIDFHV H 3URWRFRORV SDUD D iUHD GH WHOHFRPXQLFDo}HV HP HVSHFtILFR SDUD D QRVVD DSOLFDomR SDUD UHGH *60 3/01 LQWHUIDFHV $ELV H $ $OpP GH 0RQLWRUDomR HVWH LQVWUXPHQWR WDPEpP p 6LPXODGRU H (PXODGRU SRUpP Vy WUDEDOKDUHPRV FRP D 0RQLWRUDomR 1D ,QWHUIDFH $ELV 2V GDGRV VmR LQWHUSUHWDGRV GH DFRUGR FRP DV HVSHFLILFDo}HV *60 *06 *60 H *60 1D LQWHUIDFH $ WDPEpP VH XWLOL]D DV UHFRPHQGDo}HV GR ,787 :KLWH %RRN 6&&3 9iULRV )LOWURV GH FDSWXUD SRGHP VHU XWLOL]DGRV GH DFRUGR FRP R GHVHMR GR RSHUDGRU SDUD DQDOLVDU HVSHFLILFDPHQWH VHP VREUHFDUUHJDU FRP PXLWDV LQIRUPDo}HV GHVQHFHVViULDV
MN1788 A30808-X5226-C559-1-7618 7-2
*HQHUDOLGDGHV
$V PHQVDJHQV GH VLQDOL]DomR GD FDPDGD H FDPDGD SRGHP VHU YLVWDV LQFOXVLYH FRP XPD YLVXDOL]DomR GRV 4XDGURV FRP D PiVFDUD GRV ELWV $V LQIRUPDo}HV TXH IOXHP SHOR ( DOpP GH VHU PRQLWRUDGDV SRGHP VHU ILOWUDGDV H UHJLVWUDGDV HP DUTXLYRV &RP &DOO WUDFH WDPEpP SRGH VHU IHLWR XP DFRPSDQKDPHQWR GH GLYHUVRV WLSRV GH FKDPDGDV FRPR 02& 07& /8 +DQGRYHU HWF
MN1788
A30808-X5226-C559-1-7618
7-3
$OJXPDV GDV PHQVDJHQV SRGHP VHU H[SOLFDGDV FRP R +HOS QR GLFLRQiULR QD TXDO PRVWUD HP XPD MDQHOD D HVWUXWXUD GD PHQVDJHP QR IRUPDWR GR TXDGUR H HP TXDO FDPDGD VH HQFRQWUD 2 2EMHWLYR DTXL DSUHVHQWDGR p SDUD HVFODUHFHU DV PHQVDJHQV DSUHVHQWDGDV QR GLVSOD\ GXUDQWH SRU H[HPSOR GH XP HVWDEHOHFLPHQWR GH XPD FKDPDGD 02& 07& /8 +DQGRYHU HWF 1mR ID] SDUWH GR FXUVR R GHWDOKDPHQWR SURIXQGR GR $QDOLVDGRU . SRU WHU XPD LPHQ VLGmR GH GHWDOKHV H TXH QmR ID] SDUWH GR HVFRSR GHVWH FXUVR
MN1788 A30808-X5226-C559-1-7618 7-4
,QWHUIDFH $ELV 1D 0RQLWRUDomR GD ,QWHUIDFH $ELV UHFHSomR GR ODGR $ %76( H ODGR % 06& p IHLWR HP SDUDOHOR GR 7LPH VORW GH VLQDOL]DomR /$3' SH[ 2 SURWRFROR D VHU PHGLGR SRGH VHU HVFROKLGR TXDLV HVWmR GLVSRQLELOL]DGRV SHOR LQVWUXPHQWR
MN1788
A30808-X5226-C559-1-7618
7-5
'LDJUDPD HP %ORFR GDV LQWHUIDFHV

CC SS SMS CM MM RR LAPDm L1 RSL O&M L2ML LAPD L1 BTS BSC CCS7 OMC-S OMC-B DTAP BSSMAP BSSAP SCCP MTP MN1788 A30808-X5226-C559-1-7618 7-6 MAP HLR AC VLR EIR
$ELV
TCAP SCCP MTP ISUP SCCP MTP CCS7 MSC ISDN
8P
CCS7
&RQH[mR GD &DPDGD HQWUH D 06 H 06&
MS RR
BSC BSSMAP
MSC
MM
'7$3
CM
'7$3
MN1788
A30808-X5226-C559-1-7618
7-7
'LDJUDPD GH FRQH[mR QD $ELV
BTSE
Abis PCM30
BSC
E1 #1 Rx1 Monitor Abis K1297
MN1788
A30808-X5226-C559-1-7618
7-8
7HOD GR .
0HQVDJHP GH XP 3HGLGR GH /RFDWLRQ 8SGDWH
3LSHOLQH
MN1788
-DQHOD 0HQVDJHQV
A30808-X5226-C559-1-7618
([SOLFDomR GDV PHQVDJHQV H 0iVFDUD GH ELWV

7-9
3UHSDUDomR SDUD D &RQILJXUDU R $QDOLVDGRU SDUD 0RQLWRUDomR QD ,QWHUIDFH $ELV (VWD SUHSDUDomR LQLFLDO p YiOLGD SDUD D LQWHUIDFH $ELV H SDUD D ,QWHUIDFH $ PXGD R 76 R SURWRFROR QDWXUDOPHQWH R &HQiULR HP Vt
MN1788
A30808-X5226-C559-1-7618
7-10
&ULDomR GR &HQiULR GH 0RQLWRUDomR
&ULDU &HQiULR 2Q OLQH RX RIIOLQH $GG 6FHQDULR ZLWK 3LSHOLQH RQ OLQH PRQLWRULQJ &OLFDU QR FHQiULR &ULDGR H GLJLWDU R QRPH GHVHMDGR GD 0RQLWRUDomR SH[7(/(0$5B$%,6
MN1788
A30808-X5226-C559-1-7618
7-11
)LOWHU 6HWXS $MXVWH QR 3LSHOLQH

3URWRFROR %\ 3DVV VLJQLILFD TXH WRGDV RV SURWRFRORV QD LQWHUIDFH SDVVDUmR VHP VHU EDUUDGDV
&DVR TXHLUD VHOHFLRQDU DOJXP LWHP GHVPDUFDU R E\ SDVV H VHOHFLRQDU RV SURWRFRORV (UURU (YHQWV )UDPH WLSR HWF
MN1788 A30808-X5226-C559-1-7618
2. DSyV VHOHFLRQDU WRGRV RV LWHQV EiVLFRV FDVR TXHLUD DOWHUDU p SRVVtYHO PHVPR HP PRQLWRUDPHQWR
7-12
9LVWD VXSHULRU GR LQVWUXPHQWR SODFD ( H (
0HDVXUHPHQW 6FHQDULRV &DUGV RYHUYLHZ -DQHOD GH YLVXDOL]DomR GD FRQH[mR H SRUWD (

MN1788 A30808-X5226-C559-1-7618 7-13
9LVWD )URQWDO GD 3ODFD (
&OLFDU HP 3RUWV 6HWXS YHU D MDQHOD GH FRQILJ 1D SiJLQD VHJXLQWH
MN1788
A30808-X5226-C559-1-7618
7-14
3RUW 6HWXS (
3RUW 6HOHFWLRQ &DUGV ( 3RUW $5[ %5[ 2SHUDWLRQ 0RGH 0RQLWRULQJ /LQH &RGH+'% ,PSHGDQFH +LJK ,PSHGDQFH 2.
MN1788 A30808-X5226-C559-1-7618 7-15
/RJLF OLQN 6HWXS
0RQLWRU 3DU ( &DQDO 3URWRFROR JVPSBVDELV
&HQiULR &ULDGR 7(/(0$5 $%,6 YHU SURFHGLPHQWR
MN1788
A30808-X5226-C559-1-7618
7-16
6HOHomR GR /RJLFDO /LQNV QR )LOWHU
1D MDQHOD )LOWHU 6HWXS FOLFDU HP /RJLFDO /LQNV SDUD VHOHFLRQDU R /RJLFDO /LQN H D SLOKD GR SURWRFROR 1R ILOWUR GH TXDGURV GR SURWRFROR QmR Ki QHFHVVLGDGH GH PDUFDU SRLV Mi IRL H[HFXWDGR QD MDQHOD GR 3URWRFROV
MN1788 A30808-X5226-C559-1-7618 7-17
$SOLFDomR GH 0RQLWRUDomR 0RQ$SS
&OLFDU QR 3LSHOLQH HP $SSOLFDWLRQV

MN1788 A30808-X5226-C559-1-7618 7-18
6HOHFLRQDU &DOO7UDFH 6HTrQFLD

&OLFDU 1D -DQHOD 0RQ$SS HP &DOO7U6HT PRVWUDGR QR VOLGH DQWHULRU
&OLFDU HP /RDG SDUD FDUUHJDU R 6: GH DSOLFDomR (VSHFtILFD *60 ,QWHUIDFH $ELV )DVH $R FOLFDU HP /RDG DSDUHFHUi D MDQHOD TXH HVWi QD SiJLQD D VHJXLU
MN1788
A30808-X5226-C559-1-7618
7-19
0RGR GH $SOLFDomR GD &DOO 7UDFH 6HTXHQFH

&OLFDU HP &764 3DUkPHWURV GR 7LSR GH 1~PHUR 1~PHUR GH $ H RX 1~PHUR GH % ,0(, 706,,06,
7UDFH 0RGH 6LQJOH0XOWLSOH )LOWHU 0RGH 6XSUHHV IUDPHV RI RWKHUV FDOOV 6&&38'7 PHVVDJHV
)RUPDW RI WUDFH WH[W 'HWDLOHG p D PHOKRU RSomR GH GHWD OKDPHQWR GDV FKDPDGDV
MN1788
A30808-X5226-C559-1-7618
7-20
0RGR GH $SOLFDomR GD &DOO 7UDFH 6HTXHQFH &DXVH 9DOXHV

&OLFDU HP &DXVH 9DOXHV WHUHPRV RSo}HV GH HVFROKHU TXDLV DV FDXVDV $OO VHOHFWHGHG YDOXHV PHOKRU RSomR 7RGRV RV YDORUHV GH XPD GHWHUPLQDGD FKDPDGD SH[ VHP URWD GH GHVWLQR XVXiULR RFXSDGR 8VH &DXVH 9DOXHV H $OO QRW VHOHFW YDOXHV SUHGHILQH QD OLVWD TXDO R YDORU TXH VH GHVHMD YHU QD PHQVDJHP 0HVVDJH 2SWLRQV VXSULPH D SULPHLUD RX D ~OWLPD PHQVDJHP SH[
MN1788
A30808-X5226-C559-1-7618
7-21
0RGR GH $SOLFDomR GD &DOO 7UDFH 6HTXHQFH 0HVVDJH 2SWLRQV

0HVVDJH 2SWLRQV VXSULPH D SULPHLUD RX D ~OWLPD PHQVDJHP SH[ 56/B0($6B5(6 1~PHUR Pi[LPR GH PHQVDJHQV TXH QmR SRGHP VHU VXSULPLGDV 6XSULPH D SULPHLUD RX D ~OWLPD PHQVDJHP 3RU ~OWLPR 6WDUW DR FOLFDU LQLFLDVH R SURFHGLPHQWR GH FDOO WUDFH FRP VHTrQFLD GDV PHQVDJHQV TXH HVWmR RFRUUHQGR QD ,QWHUDFH $ELV TXH HVWDPRV PRQLWRUDQGR 3DUD DOWHUDU TXDOTXHU LWHP YROWDU QR 3LSHOLQH $SSOLFDWLRQ &DOO7U 6HT H 6WRS QD UHIHULGD MDQHOD
MN1788
A30808-X5226-C559-1-7618
7-22
&DSWXUH 5$0
'HILQH D iUHD GH PHPyULD UHVHUYDGD SDUD EXIIHUL]DU RV GDGRV GH VLQDOL ]DomR QRV PyGXORV GH LQWHUIDFH 2 WDPDQKR GD &DSWXUH 5$0 SRGH VHU DMXVWDGD HQWUH . DWp . HP . SDVVRV 3DUD R QRVVR H[HPSOR QmR SUHFLVDPRV VHWDU GHL[DPRV FRUUHU OLYUHPHQWH 3DUD VDOYDU HP XP $UTXLYR VHOHFLRQDU HP 3LSHOLQH HOHPHQWV &DSWXUH 5$0 5LQJ 0RGH 6DYH &DSWXUH 5$0 PRGH 5HFRUGLQJ )LOH 6$9( $6 &DSWXUH 5$0 QR 5LQJ 0RGH HVFUHYH RV GDGRV HQTXDQWR HVWLYHU GLVSRQtYHO XPD YH] FKHLD RV QRYRV GDGRV VmR VREUHVFULWRV H /LQHDU 0RGH RV GDGRV VmR DUPD]HQDGRV DWp HQFKHU D &DSWXUH 5$0
MN1788
A30808-X5226-C559-1-7618
7-23
7HOD GR 021,725
3LSHOLQH H (OHPHQWRV GD FRPSRVLomR IOOX[R GH 'DGRV
6KRUW 9LHZ 9LVWD GDV 0HQVDJHQV H 3URWRFRORV
)UDPH 9LHZ 9LVWD GRV TXDGURV GDV PHQVDJHQV H VHXV VLJQLILFDGRV

MN1788 A30808-X5226-C559-1-7618 7-24
7HOD ([SORGLGD GDV 0HQVDJHQV H 3URWRFRORV
3URWRFROR /$3' 0HQVDJHP
0HQVDJHP GH 3HGLGR GH /2&$7,21 83'$7( /RFDWLRQ 8SGDWH $FFHSW
MN1788
A30808-X5226-C559-1-7618
7-25
$ VHJXLU WHUHPRV DV WHODV GH 0HQVDJHQV GD ,QWHUIDFH $ELV H[HPSORV GH /8 02& 07& +DQGRYHU 3DJLQJ HWF
MN1788
A30808-X5226-C559-1-7618
7-26
0RQLWRUDomR QD ,QWHUIDFH $ %66 06&

2%6 $ SUHSDUDomR GD ,QWHUIDFH $ p VLPLODU j ,QWHUIDFH $ELV SRUpP DOWHUD R SURWRFROR R 76 H DOJXQV ILOWURV PDV p SRVVtYHO VHJXLU R PHVPR SURFHGLPHQWR GD LQWHUIDFH $ELV
MN1788
A30808-X5226-C559-1-7618
7-27
TRAU
iNTERFACE A PCM30-- TS 16 CCSS7

30&
MSC
E1 #1 Rx1 Monitor Interface A K1297
MN1788
A30808-X5226-C559-1-7618
7-28
,QWHUIDFH ( SDUD FDQDO &&66
3URWRFROR

&DQDO 1U
MN1788
A30808-X5226-C559-1-7618
7-29
%76 ' 7 $ 3 2 / 5 6 00 /
%6& ' 7 $ '7$3 3 5 / 2 %660$3 6 / 0 0 6&&3 /$3' 073

,QWHUIDFH
55
/$3'P /$3' /D\HU /D\HU WR 80
/D\HU /D\HU 06& $ELV

bis
06&
75$8
76
MN1788
A30808-X5226-C559-1-7618
7-30
&RQH[mR GD &DPDGD HQWUH D 06 H 06&
MS RR
BSC BSSMAP
MSC
MM
'7$3
CM
'7$3
MN1788
A30808-X5226-C559-1-7618
7-31
$ VHJXLU WHUHPRV DV WHODV GH 0HQVDJHQV GD ,QWHUIDFH $ H[HPSORV GH /8 02& 07& +DQGRYHU 3DJLQJ HWF
MN1788
A30808-X5226-C559-1-7618
7-32
SHORT VIEW- MOC-MTC-LU
A30808-X5226-C559-1-7618
7-33
s
SHORT VIEW- MOC-MTC-LU
+--------------------+------------------------+-------+-------------------------------------------+------+--------+------------+------------+ |Long Time |From |2. Prot|2. MSG |3. Prot|3. MSG |4. Prot |4. MSG | +--------------------+------------------------+-------+-------------------------------------------+------+--------+------------+------------+ | | | | | |======================================== | | | | | |8:35:22 AM,146,336 |1:A (Rx):31 | text |=== Call tracing started. | | | | | |8:35:22 AM,146,336 |1:A (Rx):31 | text |===------------------------------------| | | | | |8:35:22 AM,146,336 |1:A (Rx):31 | text |=== Parameters for search: | | | | | |8:35:22 AM,146,336 |1:A (Rx):31 | text |=== Number: * | | | | | |8:35:22 AM,146,336 |1:A (Rx):31 | text |=== Type of Number: Called or Calling P|arty N|umber | | | |8:35:22 AM,146,336 |1:A (Rx):31 | text |=== Cause Values: Not selected | | | | | |8:35:22 AM,146,336 |1:A (Rx):31 | text |=== Trace mode: Multiple | | | | | |8:35:22 AM,146,336 |1:A (Rx):31 | text |=== Filter mode: Forward frames of o|ther c|alls | | | |8:35:22 AM,146,336 |1:A (Rx):31 | text |=== MEAS_RES messages: Suppress | | | | | |8:35:22 AM,146,336 |1:A (Rx):31 | text |=== Number of MEAS_RES: 0 | | | | | |8:35:22 AM,146,336 |1:A (Rx):31 | text |=== Which MEAS_RES: First | | | | | |8:35:22 AM,146,336 |1:A (Rx):31 | text |=== Trace Text: Detailed | | | | | |8:35:22 AM,146,336 |1:A (Rx):31 | text |=== Display mode: Sequenced | | | | | |8:35:22 AM,146,336 |1:A (Rx):31 | text |======================================== | | | | |
A30808-X5226-C559-1-7618
7-34
s
|8:35:26 AM,501,650 |1:A (Rx):31 |LAPD |INFO |RSL |RESIN | | | |8:35:26 AM,704,630 |1:A (Rx):31 |LAPD |INFO |RSL |RESIN | | | |8:35:27 AM,510,271 |1:A (Rx):31 |LAPD |INFO |RSL |RESIN | | | |8:35:37 AM,106,156 |1:B (Rx):31 |LAPD |INFO | | | | | |8:35:37 AM,110,935 |1:A (Rx):31 |LAPD |INFO | | | | | |8:35:47 AM,963,270 |1:A (Rx):31 |LAPD |INFO |RSL |CHNRD | | | |8:35:48 AM,019,481 |1:B (Rx):31 |LAPD |INFO |RSL |CHNAV | | | +--------------------+------------------------+-------+-------------------------------------------+------+--------+------------+------------+ |Long Time |From |2. Prot|2. MSG |3. Prot|3. MSG |4. Prot |4. MSG | +--------------------+------------------------+-------+-------------------------------------------+------+--------+------------+------------+ |8:35:48 AM,032,884 |1:A (Rx):31 |LAPD |INFO |RSL |CHNAK | | | |8:35:48 AM,107,593 |1:B (Rx):31 |LAPD |INFO |RSL |IACMD |DTAP |IMASS | |8:35:48 AM,399,771 |1:A (Rx):31 |LAPD |INFO |RSL |ESTIN |DTAP |IMDETIN | |8:35:48 AM,454,596 |1:B (Rx):31 |LAPD |INFO |RSL |??? | | | |8:35:48 AM,617,855 |1:B (Rx):31 |LAPD |INFO |RSL |DATRQ |DTAP |CHREL | |8:35:48 AM,619,583 |1:B (Rx):31 |LAPD |INFO |RSL |DESAC | | | |8:35:48 AM,634,892 |1:A (Rx):31 |LAPD |INFO |RSL |DATIN |DTAP |CLAMCH | |8:35:49 AM,218,272 |1:A (Rx):31 |LAPD |INFO |RSL |RELIN | | | |8:35:49 AM,691,844 |1:B (Rx):31 |LAPD |INFO |RSL |RCHRL | | | |8:35:49 AM,696,750 |1:A (Rx):31 |LAPD |INFO |RSL |RCHRA | | |
A30808-X5226-C559-1-7618
7-35
s
|8:35:57 |RESIN |8:35:57 |RESIN |8:35:58 |RESIN |8:36:28 |RESIN |8:36:28 |RESIN |8:36:29 |RESIN |8:36:37 | |8:36:37 | |8:36:59 |RESIN |8:36:59 |RESIN |8:37:00 |RESIN |8:37:30 |RESIN |8:37:30 |RESIN |8:37:31 |RESIN |8:37:37 | |8:37:37 | |8:38:01 |RESIN |8:38:01 |RESIN |8:38:02 |RESIN |8:38:13 |CHNRD AM,465,715 | AM,669,011 | AM,474,460 | AM,430,583 | AM,633,713 | AM,440,588 | AM,091,379 | AM,096,182 | AM,396,714 | AM,600,202 | AM,406,716 | AM,361,731 | AM,564,722 | AM,372,229 | AM,090,524 | AM,095,431 | AM,327,857 | AM,531,189 | AM,338,475 | AM,645,059 | |1:A | |1:A | |1:A | |1:A | |1:A | |1:A | |1:B (Rx):31 | (Rx):31 | (Rx):31 | (Rx):31 | (Rx):31 | (Rx):31 | |LAPD |LAPD |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD |LAPD |LAPD | |LAPD | |LAPD | |LAPD | |INFO |RSL |INFO |RSL |INFO |RSL |INFO |INFO |INFO | | |RSL | | |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |INFO |INFO | | |RSL | | |LAPD |INFO |RSL |LAPD |INFO |RSL |LAPD |INFO |RSL |LAPD |INFO |RSL |LAPD |INFO |RSL |LAPD |INFO |RSL
(Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:B (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 |
A30808-X5226-C559-1-7618
7-36
s
|8:38:13 |CHNAV |8:38:13 |CHNAK |8:38:13 |IACMD |8:38:13 |ESTIN |8:38:14 |??? |8:38:14 |DATRQ |8:38:14 |DATRQ |8:38:14 |DESAC |8:38:14 |DATIN |8:38:15 |RELIN |8:38:15 |RCHRL |8:38:15 |RCHRA |8:38:32 |RESIN |8:38:32 |RESIN |8:38:33 |RESIN |8:38:37 | |8:38:37 | |8:39:03 |RESIN |8:39:03 |RESIN |8:39:04 |RESIN AM,704,398 | AM,718,435 | AM,780,011 |DTAP AM,971,184 |DTAP AM,014,509 | AM,165,887 |DTAP AM,178,630 |DTAP AM,180,364 | AM,206,191 |DTAP AM,025,180 | AM,576,887 | AM,582,409 | AM,293,863 | AM,496,363 | AM,305,110 | AM,077,798 | AM,082,580 | AM,259,378 | AM,462,499 | AM,271,502 | |1:B (Rx):31 | |1:A (Rx):31 | |1:B (Rx):31 |IMASS |1:A (Rx):31 |LUREQ |1:B (Rx):31 | |1:B (Rx):31 |LUACC |1:B (Rx):31 |CHREL |1:B (Rx):31 | |1:A (Rx):31 |CLAMCH |1:A (Rx):31 | |1:B (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:B (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD |LAPD |LAPD | |LAPD | |LAPD | |INFO |RSL |INFO |RSL |INFO |INFO |INFO | | |RSL | | |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL
A30808-X5226-C559-1-7618
7-37
s
|8:39:14 AM,591,086 |1:A (Rx):31 |LAPD |INFO |RSL |CHNRD | | | |8:39:14 AM,654,033 |1:B (Rx):31 |LAPD |INFO |RSL |CHNAV | | | |8:39:14 AM,668,213 |1:A (Rx):31 |LAPD |INFO |RSL |CHNAK | | | |8:39:14 AM,742,167 |1:B (Rx):31 |LAPD |INFO |RSL |IACMD |DTAP |IMASS | |8:39:14 AM,953,955 |1:A (Rx):31 |LAPD |INFO |RSL |ESTIN |DTAP |CMSREQ | |8:39:14 AM,953,955 |1:A (Rx):31 |LAPD |INFO |RSL |ESTIN |DTAP |CMSREQ | |8:39:15 AM,014,283 |1:B (Rx):31 |LAPD |INFO |RSL |??? | | | |8:39:15 AM,189,079 |1:A (Rx):31 |LAPD |INFO |RSL |DATIN |DTAP |CLAMCH | |8:39:15 AM,189,079 |1:A (Rx):31 |LAPD |INFO |RSL |DATIN |DTAP |CLAMCH | +--------------------+------------------------+-------+-------------------------------------------+------+--------+------------+------------+ |Long Time |From |2. Prot|2. MSG |3. Prot|3. MSG |4. Prot |4. MSG | +--------------------+------------------------+-------+-------------------------------------------+------+--------+------------+------------+ |8:39:15 AM,190,410 |1:B (Rx):31 |LAPD |INFO |RSL |ENCRY |DTAP |CIMCMD | |8:39:15 AM,190,410 |1:B (Rx):31 |LAPD |INFO |RSL |ENCRY |DTAP |CIMCMD | |8:39:15 AM,252,408 |1:B (Rx):31 |LAPD |INFO |RSL |??? | | | |8:39:15 AM,425,077 |1:A (Rx):31 |LAPD |INFO |RSL |DATIN |DTAP |CIMCMP | |8:39:15 AM,425,077 |1:A (Rx):31 |LAPD |INFO |RSL |DATIN |DTAP |CIMCMP | |8:39:15 AM,591,405 |1:B (Rx):31 |LAPD |INFO |RSL |DATRQ |DTAP |TRCMD | |8:39:15 AM,591,405 |1:B (Rx):31 |LAPD |INFO |RSL |DATRQ |DTAP |TRCMD | |8:39:15 AM,660,451 |1:A (Rx):31 |LAPD |INFO |RSL |DATIN |DTAP |SETUP |
A30808-X5226-C559-1-7618
7-38
s
|8:39:15 |DATIN |8:39:15 | |8:39:15 | |8:39:15 | |8:39:15 |DATRQ |8:39:15 |DATRQ |8:39:15 |PHCRQ |8:39:15 |PHCRQ |8:39:15 |PHCCN |8:39:15 |PHCCN |8:39:15 |DATIN |8:39:15 |DATIN |8:39:15 |CHNAV |8:39:15 |CHNAV |8:39:15 |CHNAK |8:39:15 |CHNAK |8:39:16 |DATRQ |8:39:16 |DATRQ |8:39:16 | |8:39:16 | AM,660,451 |DTAP AM,660,451 | AM,660,451 | AM,660,451 | AM,877,659 |DTAP AM,877,659 |DTAP AM,879,394 | AM,879,394 | AM,884,962 | AM,884,962 | AM,894,439 |DTAP AM,894,439 |DTAP AM,941,908 | AM,941,908 | AM,956,326 | AM,956,326 | AM,015,901 |DTAP AM,015,901 |DTAP AM,015,901 | AM,015,901 | |1:A (Rx):31 |SETUP |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:B (Rx):31 |CPROC |1:B (Rx):31 |CPROC |1:B (Rx):31 | |1:B (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 |TRCMP |1:A (Rx):31 |TRCMP |1:B (Rx):31 | |1:B (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:B (Rx):31 |ASSCMD |1:B (Rx):31 |ASSCMD |1:B (Rx):31 | |1:B (Rx):31 | |LAPD | | text | text | text |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | | text | text |=== Call on TEI=1, TS=1, CHAN=9 |=== Now linked to ===> | | | | |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |=== S T A R T === |=== Called Party Number = 99956600 |=== TS: 1 |INFO CHAN: 9 | | | |RSL | | | |INFO |RSL
A30808-X5226-C559-1-7618
7-39
s
|8:39:16 | |8:39:16 |ESTIN |8:39:16 |DATIN |8:39:16 |DATIN |8:39:16 |??? |8:39:16 |RELRQ |8:39:16 |RELRQ |8:39:16 |RELCN |8:39:16 |RELCN |8:39:16 |RCHRL |8:39:16 |RCHRL |8:39:16 |RCHRA |8:39:16 |RCHRA |8:39:16 | |8:39:16 | |8:39:16 | |8:39:16 | |8:39:17 |PGCMD |8:39:17 |PGCMD |8:39:17 |PGCMD AM,015,901 | AM,629,318 | AM,750,074 |DTAP AM,750,074 |DTAP AM,814,775 | AM,817,173 | AM,817,173 | AM,822,428 | AM,822,428 | AM,876,534 | AM,876,534 | AM,882,182 | AM,882,182 | AM,882,182 | AM,882,182 | AM,882,182 | AM,882,182 | AM,152,652 | AM,155,511 | AM,158,384 | |1:B (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 |ASSCMP |1:A (Rx):31 |ASSCMP |1:B (Rx):31 | |1:B (Rx):31 | |1:B (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:B (Rx):31 | |1:B (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:B (Rx):31 | |1:B (Rx):31 | |1:B (Rx):31 | | text |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | | text | text | text | text |LAPD | |LAPD | |LAPD | |INFO |RSL |INFO |RSL |=========================== |=== RSL connection released: |=== TEI = 1 Time Slot = 1 Channel = 9 | | | | |RSL | | | | |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |===> |INFO TEI=1, TS=4, CHAN=1 | |RSL |
|============================= |INFO
A30808-X5226-C559-1-7618
7-40
s
|8:39:17 AM,716,339 |1:A (Rx):31 |LAPD |INFO |RSL |CHNRD | | | |8:39:17 AM,779,023 |1:B (Rx):31 |LAPD |INFO |RSL |CHNAV | | | |8:39:17 AM,792,575 |1:A (Rx):31 |LAPD |INFO |RSL |CHNAK | | | |8:39:17 AM,854,647 |1:B (Rx):31 |LAPD |INFO |RSL |IACMD |DTAP |IMASS | |8:39:18 AM,069,450 |1:A (Rx):31 |LAPD |INFO |RSL |ESTIN |DTAP |PAGRES | |8:39:18 AM,069,450 |1:A (Rx):31 |LAPD |INFO |RSL |ESTIN |DTAP |PAGRES | |8:39:18 AM,126,771 |1:B (Rx):31 |LAPD |INFO |RSL |??? | | | |8:39:18 AM,290,399 |1:B (Rx):31 |LAPD |INFO |RSL |ENCRY |DTAP |CIMCMD | |8:39:18 AM,290,399 |1:B (Rx):31 |LAPD |INFO |RSL |ENCRY |DTAP |CIMCMD | |8:39:18 AM,304,698 |1:A (Rx):31 |LAPD |INFO |RSL |DATIN |DTAP |CLAMCH | |8:39:18 AM,304,698 |1:A (Rx):31 |LAPD |INFO |RSL |DATIN |DTAP |CLAMCH | +--------------------+------------------------+-------+-------------------------------------------+------+--------+------------+------------+ |Long Time |From |2. Prot|2. MSG |3. Prot|3. MSG |4. Prot |4. MSG | +--------------------+------------------------+-------+-------------------------------------------+------+--------+------------+------------+ |8:39:18 AM,377,400 |1:B (Rx):31 |LAPD |INFO |RSL |??? | | | |8:39:18 AM,540,071 |1:A (Rx):31 |LAPD |INFO |RSL |DATIN |DTAP |CIMCMP | |8:39:18 AM,540,071 |1:A (Rx):31 |LAPD |INFO |RSL |DATIN |DTAP |CIMCMP | |8:39:18 AM,717,658 |1:B (Rx):31 |LAPD |INFO |RSL |DATRQ |DTAP |SETUP | |8:39:18 AM,717,658 |1:B (Rx):31 |LAPD |INFO |RSL |DATRQ |DTAP |SETUP | |8:39:18 AM,717,658 |1:B (Rx):31 | text |=== S T A R T === | | | | |
A30808-X5226-C559-1-7618
7-41
s
|8:39:18 | |8:39:18 | |8:39:19 |DATIN |8:39:19 |DATIN |8:39:19 |PHCRQ |8:39:19 |PHCRQ |8:39:19 |PHCCN |8:39:19 |PHCCN |8:39:19 |CHNAV |8:39:19 |CHNAV |8:39:19 |CHNAK |8:39:19 |CHNAK |8:39:19 |DATRQ |8:39:19 |DATRQ |8:39:19 | |8:39:19 | |8:39:19 | |8:39:20 |ESTIN |8:39:20 |DATIN |8:39:20 |DATIN AM,717,658 | AM,717,658 | AM,481,317 |DTAP AM,481,317 |DTAP AM,776,514 | AM,776,514 | AM,781,672 | AM,781,672 | AM,829,261 | AM,829,261 | AM,843,189 | AM,843,189 | AM,890,655 |DTAP AM,890,655 |DTAP AM,890,655 | AM,890,655 | AM,890,655 | AM,444,938 | AM,546,936 |DTAP AM,546,936 |DTAP |1:B (Rx):31 | |1:B (Rx):31 | |1:A (Rx):31 |CCONF |1:A (Rx):31 |CCONF |1:B (Rx):31 | |1:B (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:B (Rx):31 | |1:B (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:B (Rx):31 |ASSCMD |1:B (Rx):31 |ASSCMD |1:B (Rx):31 | |1:B (Rx):31 | |1:B (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 |ASSCMP |1:A (Rx):31 |ASSCMP | text | text |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | | text | text | text |LAPD | |LAPD | |LAPD | |INFO |RSL |INFO |RSL |=== Call on TEI=3, TS=1, CHAN=12 |=== Now linked to ===> |===> |INFO TEI=3, TS=2, CHAN=1 | | | |RSL | | | |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |=== Calling Party Number = 554199956604 |=== TS: 1 |INFO CHAN: 12 | | |RSL | |
A30808-X5226-C559-1-7618
7-42
s
|8:39:20 |??? |8:39:20 |RELRQ |8:39:20 |RELRQ |8:39:20 |RELCN |8:39:20 |RELCN |8:39:20 |RCHRL |8:39:20 |RCHRL |8:39:20 |RCHRA |8:39:20 |RCHRA |8:39:20 | |8:39:20 | |8:39:20 | |8:39:20 | |8:39:20 |DATIN |8:39:20 |DATIN |8:39:21 |DATRQ |8:39:21 |DATRQ |8:39:23 |DATIN |8:39:23 |DATIN |8:39:23 |DATRQ AM,589,762 | AM,592,132 | AM,592,132 | AM,596,790 | AM,596,790 | AM,651,510 | AM,651,510 | AM,656,543 | AM,656,543 | AM,656,543 | AM,656,543 | AM,656,543 | AM,656,543 | AM,846,813 |DTAP AM,846,813 |DTAP AM,027,886 |DTAP AM,027,886 |DTAP AM,805,551 |DTAP AM,805,551 |DTAP AM,989,879 |DTAP |1:B | |1:B | |1:B | |1:A | |1:A | |1:B | |1:B | |1:A | |1:A | |1:A (Rx):31 | (Rx):31 | (Rx):31 | (Rx):31 | (Rx):31 | (Rx):31 | (Rx):31 | (Rx):31 | (Rx):31 | | text | text | text | text |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |=========================== |=== RSL connection released: |=== TEI = 3 Time Slot = 1 | | Channel = 12 | | |RSL | | | | |LAPD |INFO |RSL |LAPD |INFO |RSL |LAPD |INFO |RSL |LAPD |INFO |RSL |LAPD |INFO |RSL |LAPD |INFO |RSL |LAPD |INFO |RSL |LAPD |INFO |RSL |LAPD |INFO |RSL
(Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 |ALERT |1:A (Rx):31 |ALERT |1:B (Rx):31 |ALERT |1:B (Rx):31 |ALERT |1:A (Rx):31 |CONNECT |1:A (Rx):31 |CONNECT |1:B (Rx):31 |CONACK
|============================= |INFO
A30808-X5226-C559-1-7618
7-43
s
|8:39:23 AM,989,879 |1:B (Rx):31 |LAPD |INFO |RSL |DATRQ |DTAP |CONACK | |8:39:24 AM,027,376 |1:B (Rx):31 |LAPD |INFO |RSL |DATRQ |DTAP |CONNECT | |8:39:24 AM,027,376 |1:B (Rx):31 |LAPD |INFO |RSL |DATRQ |DTAP |CONNECT | |8:39:24 AM,166,794 |1:A (Rx):31 |LAPD |INFO |RSL |DATIN |DTAP |CONACK | |8:39:24 AM,166,794 |1:A (Rx):31 |LAPD |INFO |RSL |DATIN |DTAP |CONACK | |8:39:24 AM,893,309 |1:A (Rx):31 |LAPD |INFO |RSL |??? | | | |8:39:25 AM,116,624 |1:B (Rx):31 |LAPD |INFO |RSL |CHNAV | | | |8:39:25 AM,116,624 |1:B (Rx):31 |LAPD |INFO |RSL |CHNAV | | | |8:39:25 AM,130,780 |1:A (Rx):31 |LAPD |INFO |RSL |CHNAK | | | |8:39:25 AM,130,780 |1:A (Rx):31 |LAPD |INFO |RSL |CHNAK | | | |8:39:25 AM,378,751 |1:B (Rx):31 |LAPD |INFO |RSL |DATRQ |DTAP |HOCMD | |8:39:25 AM,378,751 |1:B (Rx):31 |LAPD |INFO |RSL |DATRQ |DTAP |HOCMD | |8:39:25 AM,378,751 |1:B (Rx):31 | text |=== Call on TEI=1, TS=4, CHAN=1 | | | | | +--------------------+------------------------+-------+-------------------------------------------+------+--------+------------+------------+ |Long Time |From |2. Prot|2. MSG |3. Prot|3. MSG |4. Prot |4. MSG | +--------------------+------------------------+-------+-------------------------------------------+------+--------+------------+------------+ |8:39:25 AM,378,751 |1:B (Rx):31 | text |=== Now linked to ===> | | | | | |8:39:25 AM,378,751 |1:B (Rx):31 | text |===> TEI=3, TS=3, CHAN=1 | | | | | |8:39:25 AM,503,163 |1:A (Rx):31 |LAPD |INFO |RSL |HANDO | | | |8:39:25 AM,647,539 |1:A (Rx):31 |LAPD |INFO |RSL |ESTIN | | |
A30808-X5226-C559-1-7618
7-44
s
|8:39:25 |DATIN |8:39:25 |DATIN |8:39:25 |??? |8:39:25 |RELRQ |8:39:25 |RELRQ |8:39:25 |RELCN |8:39:25 |RELCN |8:39:26 |RCHRL |8:39:26 |RCHRL |8:39:26 |RCHRA |8:39:26 |RCHRA |8:39:26 | |8:39:26 | |8:39:26 | |8:39:26 | |8:39:34 |RESIN |8:39:34 |RESIN |8:39:34 | |8:39:34 | |8:39:34 | AM,767,663 |DTAP AM,767,663 |DTAP AM,826,743 | AM,976,995 | AM,976,995 | AM,982,023 | AM,982,023 | AM,026,488 | AM,026,488 | AM,031,768 | AM,031,768 | AM,031,768 | AM,031,768 | AM,031,768 | AM,031,768 | AM,225,271 | AM,428,007 | AM,430,094 | AM,430,094 | AM,430,094 | |1:A (Rx):31 |HOCMP |1:A (Rx):31 |HOCMP |1:B (Rx):31 | |1:B (Rx):31 | |1:B (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:B (Rx):31 | |1:B (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:B (Rx):31 | |1:B (Rx):31 | |1:B (Rx):31 | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | | text | text | text | text |LAPD | |LAPD | | text | text | text |=========================== |=== RSL connection timed out: |=== TEI = 3 Time Slot = 2 Channel = 1 | | | | | | |INFO |RSL |=========================== |=== RSL connection released: |=== TEI = 1 Time Slot = 4 Channel = 1 | | | | |RSL | | | | |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL
|============================= |INFO
A30808-X5226-C559-1-7618
7-45
s
|8:39:34 | |8:39:35 |RESIN |8:39:37 | |8:39:37 | |8:39:37 | |8:39:37 | |8:39:37 | |8:39:37 | |8:39:42 |DATIN |8:39:43 |DATRQ |8:39:43 |DATRQ |8:39:43 |DATIN |8:39:43 |DATIN |8:39:43 |DATRQ |8:39:43 |DATRQ |8:39:43 |DESAC |8:39:43 |DATRQ |8:39:43 |DESAC |8:39:43 |RELIN |8:39:43 |RELIN AM,430,094 | AM,236,891 | AM,065,090 | AM,069,732 | AM,072,084 | AM,072,084 | AM,072,084 | AM,072,084 | AM,927,727 |DTAP AM,152,805 |DTAP AM,165,182 |DTAP AM,288,731 |DTAP AM,306,261 |DTAP AM,465,431 |DTAP AM,468,162 |DTAP AM,470,333 | AM,474,055 |DTAP AM,475,787 | AM,671,097 | AM,790,476 | |1:B (Rx):31 | |1:A (Rx):31 | |1:B (Rx):31 | |1:A (Rx):31 | |1:B (Rx):31 | |1:B (Rx):31 | |1:B (Rx):31 | |1:B (Rx):31 | |1:A (Rx):31 |DISC |1:B (Rx):31 |RELEAS |1:B (Rx):31 |DISC |1:A (Rx):31 |RELCMP |1:A (Rx):31 |RELEAS |1:B (Rx):31 |RELCMP |1:B (Rx):31 |CHREL |1:B (Rx):31 | |1:B (Rx):31 |CHREL |1:B (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | | text |LAPD | |LAPD |LAPD | text | text | text | text |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |INFO |=========================== |=== RSL connection timed out: |=== TEI = 3 Time Slot = 3 Channel = 1 | | | | | | |RSL | | | | | | |============================= |INFO | |RSL |
|============================= |INFO
A30808-X5226-C559-1-7618
7-46
s
|8:39:45 AM,163,922 |1:B (Rx):31 |LAPD |INFO |RSL |RCHRL | | | |8:39:45 AM,169,574 |1:A (Rx):31 |LAPD |INFO |RSL |RCHRA | | | |8:39:45 AM,264,045 |1:B (Rx):31 |LAPD |INFO |RSL |RCHRL | | | |8:39:45 AM,269,571 |1:A (Rx):31 |LAPD |INFO |RSL |RCHRA | | | |8:40:05 AM,191,140 |1:A (Rx):31 |LAPD |INFO |RSL |RESIN | | | |8:40:05 AM,394,151 |1:A (Rx):31 |LAPD |INFO |RSL |RESIN | | | |8:40:06 AM,203,635 |1:A (Rx):31 |LAPD |INFO |RSL |RESIN | | | |8:40:36 AM,154,595 |1:A (Rx):31 |LAPD |INFO |RSL |RESIN | | | |8:40:36 AM,357,095 |1:A (Rx):31 |LAPD |INFO |RSL |RESIN | | | |8:40:37 AM,062,167 |1:B (Rx):31 |LAPD |INFO | | | | | |8:40:37 AM,066,844 |1:A (Rx):31 |LAPD |INFO | | | | | |8:40:37 AM,167,716 |1:A (Rx):31 |LAPD |INFO |RSL |RESIN | | | |8:40:42 AM,400,061 |1:A (Rx):31 |LAPD |INFO |RSL |CHNRD | | | |8:40:42 AM,463,010 |1:B (Rx):31 |LAPD |INFO |RSL |CHNAV | | | |8:40:42 AM,477,185 |1:A (Rx):31 |LAPD |INFO |RSL |CHNAK | | | +--------------------+------------------------+-------+-------------------------------------------+------+--------+------------+------------+ |Long Time |From |2. Prot|2. MSG |3. Prot|3. MSG |4. Prot |4. MSG | +--------------------+------------------------+-------+-------------------------------------------+------+--------+------------+------------+ |8:40:42 AM,538,633 |1:B (Rx):31 |LAPD |INFO |RSL |IACMD |DTAP |IMASS | |8:40:42 AM,767,191 |1:A (Rx):31 |LAPD |INFO |RSL |ESTIN |DTAP |CMSREQ |
A30808-X5226-C559-1-7618
7-47
s
|8:40:42 |ESTIN |8:40:42 |??? |8:40:42 |ENCRY |8:40:42 |ENCRY |8:40:43 |DATIN |8:40:43 |DATIN |8:40:43 |??? |8:40:43 |DATIN |8:40:43 |DATIN |8:40:43 |DATIN |8:40:43 |DATIN |8:40:43 | |8:40:43 | |8:40:43 | |8:40:43 |DATRQ |8:40:43 |DATRQ |8:40:43 |PHCRQ |8:40:43 |PHCRQ |8:40:43 |PHCCN |8:40:43 |PHCCN AM,767,191 |DTAP AM,823,260 | AM,986,761 |DTAP AM,986,761 |DTAP AM,002,553 |DTAP AM,002,553 |DTAP AM,061,254 | AM,238,569 |DTAP AM,238,569 |DTAP AM,473,676 |DTAP AM,473,676 |DTAP AM,473,676 | AM,473,676 | AM,473,676 | AM,686,510 |DTAP AM,686,510 |DTAP AM,697,990 | AM,697,990 | AM,703,172 | AM,703,172 | |1:A (Rx):31 |CMSREQ |1:B (Rx):31 | |1:B (Rx):31 |CIMCMD |1:B (Rx):31 |CIMCMD |1:A (Rx):31 |CLAMCH |1:A (Rx):31 |CLAMCH |1:B (Rx):31 | |1:A (Rx):31 |CIMCMP |1:A (Rx):31 |CIMCMP |1:A (Rx):31 |SETUP |1:A (Rx):31 |SETUP |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:B (Rx):31 |CPROC |1:B (Rx):31 |CPROC |1:B (Rx):31 | |1:B (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | | text | text | text |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |=== S T A R T === |=== Called Party Number = 99956600 |=== TS: 1 |INFO CHAN: 10 | | | |RSL | | | |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL
A30808-X5226-C559-1-7618
7-48
s
|8:40:43 |CHNAV |8:40:43 |CHNAV |8:40:43 |CHNAK |8:40:43 |CHNAK |8:40:43 |DATRQ |8:40:43 |DATRQ |8:40:43 | |8:40:43 | |8:40:43 | |8:40:44 |ESTIN |8:40:44 |DATIN |8:40:44 |DATIN |8:40:44 |??? |8:40:44 |RELRQ |8:40:44 |RELRQ |8:40:44 |RELCN |8:40:44 |RELCN |8:40:44 |RCHRL |8:40:44 |RCHRL |8:40:44 |RCHRA AM,763,256 | AM,763,256 | AM,777,807 | AM,777,807 | AM,837,127 |DTAP AM,837,127 |DTAP AM,837,127 | AM,837,127 | AM,837,127 | AM,443,298 | AM,545,301 |DTAP AM,545,301 |DTAP AM,598,759 | AM,601,594 | AM,601,594 | AM,605,780 | AM,605,780 | AM,660,506 | AM,660,506 | AM,666,154 | |1:B (Rx):31 | |1:B (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:B (Rx):31 |ASSCMD |1:B (Rx):31 |ASSCMD |1:B (Rx):31 | |1:B (Rx):31 | |1:B (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 |ASSCMP |1:A (Rx):31 |ASSCMP |1:B (Rx):31 | |1:B (Rx):31 | |1:B (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:B (Rx):31 | |1:B (Rx):31 | |1:A (Rx):31 | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | | text | text | text |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |=== Call on TEI=1, TS=1, CHAN=10 |=== Now linked to ===> |===> |INFO TEI=1, TS=5, CHAN=1 | | | |RSL | | | |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL
A30808-X5226-C559-1-7618
7-49
s
|8:40:44 AM,666,154 |1:A (Rx):31 |LAPD |INFO |RSL |RCHRA | | | |8:40:44 AM,666,154 |1:A (Rx):31 | text |=========================== | | | | | |8:40:44 AM,666,154 |1:A (Rx):31 | text |=== RSL connection released: | | | | | |8:40:44 AM,666,154 |1:A (Rx):31 | text |=== TEI = 1 Time Slot = 1 Channel = 10 | | | | | |8:40:44 AM,666,154 |1:A (Rx):31 | text |============================= | | | | | |8:40:44 AM,936,632 |1:B (Rx):31 |LAPD |INFO |RSL |PGCMD | | | |8:40:44 AM,939,485 |1:B (Rx):31 |LAPD |INFO |RSL |PGCMD | | | |8:40:44 AM,942,362 |1:B (Rx):31 |LAPD |INFO |RSL |PGCMD | | | |8:40:45 AM,243,184 |1:A (Rx):31 |LAPD |INFO |RSL |CHNRD | | | |8:40:45 AM,301,255 |1:B (Rx):31 |LAPD |INFO |RSL |CHNAV | | | |8:40:45 AM,315,906 |1:A (Rx):31 |LAPD |INFO |RSL |CHNAK | | | |8:40:45 AM,388,629 |1:B (Rx):31 |LAPD |INFO |RSL |IACMD |DTAP |IMASS | |8:40:45 AM,647,292 |1:A (Rx):31 |LAPD |INFO |RSL |ESTIN |DTAP |PAGRES | |8:40:45 AM,647,292 |1:A (Rx):31 |LAPD |INFO |RSL |ESTIN |DTAP |PAGRES | |8:40:45 AM,723,122 |1:B (Rx):31 |LAPD |INFO |RSL |??? | | | |8:40:45 AM,882,418 |1:A (Rx):31 |LAPD |INFO |RSL |DATIN |DTAP |CLAMCH | |8:40:45 AM,882,418 |1:A (Rx):31 |LAPD |INFO |RSL |DATIN |DTAP |CLAMCH | +--------------------+------------------------+-------+-------------------------------------------+------+--------+------------+------------+ |Long Time |From |2. Prot|2. MSG |3. Prot|3. MSG |4. Prot |4. MSG | +--------------------+------------------------+-------+-------------------------------------------+------+--------+------------+------------+
A30808-X5226-C559-1-7618
7-50
s
|8:40:45 |ENCRY |8:40:45 |ENCRY |8:40:45 |??? |8:40:46 |DATIN |8:40:46 |DATIN |8:40:46 |DATRQ |8:40:46 |DATRQ |8:40:46 | |8:40:46 | |8:40:46 | |8:40:47 |DATIN |8:40:47 |DATIN |8:40:47 |PHCRQ |8:40:47 |PHCRQ |8:40:47 |PHCCN |8:40:47 |PHCCN |8:40:47 |CHNAV |8:40:47 |CHNAV |8:40:47 |CHNAK |8:40:47 |CHNAK AM,887,748 |DTAP AM,887,748 |DTAP AM,936,128 | AM,118,545 |DTAP AM,118,545 |DTAP AM,289,130 |DTAP AM,289,130 |DTAP AM,289,130 | AM,289,130 | AM,289,130 | AM,059,047 |DTAP AM,059,047 |DTAP AM,360,491 | AM,360,491 | AM,365,651 | AM,365,651 | AM,426,494 | AM,426,494 | AM,440,289 | AM,440,289 | |1:B (Rx):31 |CIMCMD |1:B (Rx):31 |CIMCMD |1:B (Rx):31 | |1:A (Rx):31 |CIMCMP |1:A (Rx):31 |CIMCMP |1:B (Rx):31 |SETUP |1:B (Rx):31 |SETUP |1:B (Rx):31 | |1:B (Rx):31 | |1:B (Rx):31 | |1:A (Rx):31 |CCONF |1:A (Rx):31 |CCONF |1:B (Rx):31 | |1:B (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:B (Rx):31 | |1:B (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | | text | text | text |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |=== S T A R T === |=== Calling Party Number = 554199956604 |=== TS: 1 |INFO CHAN: 13 | | | |RSL | | | |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL
A30808-X5226-C559-1-7618
7-51
s
|8:40:47 |DATRQ |8:40:47 |DATRQ |8:40:47 | |8:40:47 | |8:40:47 | |8:40:48 |ESTIN |8:40:48 |DATIN |8:40:48 |DATIN |8:40:48 |??? |8:40:48 |RELRQ |8:40:48 |RELRQ |8:40:48 |RELCN |8:40:48 |RELCN |8:40:48 |RCHRL |8:40:48 |RCHRL |8:40:48 |DATIN |8:40:48 |DATIN |8:40:48 |RCHRA |8:40:48 |RCHRA |8:40:48 | AM,499,622 |DTAP AM,499,622 |DTAP AM,499,622 | AM,499,622 | AM,499,622 | AM,023,914 | AM,144,660 |DTAP AM,144,660 |DTAP AM,198,735 | AM,201,106 | AM,201,106 | AM,206,402 | AM,206,402 | AM,260,494 | AM,260,494 | AM,264,895 |DTAP AM,264,895 |DTAP AM,266,266 | AM,266,266 | AM,266,266 | |1:B (Rx):31 |ASSCMD |1:B (Rx):31 |ASSCMD |1:B (Rx):31 | |1:B (Rx):31 | |1:B (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 |ASSCMP |1:A (Rx):31 |ASSCMP |1:B (Rx):31 | |1:B (Rx):31 | |1:B (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:B (Rx):31 | |1:B (Rx):31 | |1:A (Rx):31 |ALERT |1:A (Rx):31 |ALERT |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |LAPD | |LAPD | | text | text | text |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | | text |=========================== | | |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |=== Call on TEI=3, TS=1, CHAN=13 |=== Now linked to ===> |===> |INFO TEI=3, TS=4, CHAN=1 | | | |RSL | | | |INFO |RSL |INFO |RSL
A30808-X5226-C559-1-7618
7-52
s
|8:40:48 AM,266,266 |1:A (Rx):31 | text |=== RSL connection released: | | | | | |8:40:48 AM,266,266 |1:A (Rx):31 | text |=== TEI = 3 Time Slot = 1 Channel = 13 | | | | | |8:40:48 AM,266,266 |1:A (Rx):31 | text |============================= | | | | | |8:40:48 AM,461,870 |1:B (Rx):31 |LAPD |INFO |RSL |DATRQ |DTAP |ALERT | |8:40:48 AM,461,870 |1:B (Rx):31 |LAPD |INFO |RSL |DATRQ |DTAP |ALERT | |8:40:50 AM,064,533 |1:A (Rx):31 |LAPD |INFO |RSL |DATIN |DTAP |CONNECT | |8:40:50 AM,064,533 |1:A (Rx):31 |LAPD |INFO |RSL |DATIN |DTAP |CONNECT | |8:40:50 AM,261,360 |1:B (Rx):31 |LAPD |INFO |RSL |DATRQ |DTAP |CONACK | |8:40:50 AM,261,360 |1:B (Rx):31 |LAPD |INFO |RSL |DATRQ |DTAP |CONACK | |8:40:50 AM,273,854 |1:B (Rx):31 |LAPD |INFO |RSL |DATRQ |DTAP |CONNECT | |8:40:50 AM,273,854 |1:B (Rx):31 |LAPD |INFO |RSL |DATRQ |DTAP |CONNECT | |8:40:50 AM,383,277 |1:A (Rx):31 |LAPD |INFO |RSL |DATIN |DTAP |CONACK | |8:40:50 AM,383,277 |1:A (Rx):31 |LAPD |INFO |RSL |DATIN |DTAP |CONACK | |8:41:02 AM,024,541 |1:B (Rx):31 |LAPD |INFO |RSL |DATRQ |DTAP |SETUP | |8:41:02 AM,024,541 |1:B (Rx):31 |LAPD |INFO |RSL |DATRQ |DTAP |SETUP | |8:41:02 AM,026,707 |1:A (Rx):31 | text |=========================== | | | | | |8:41:02 AM,026,707 |1:A (Rx):31 | text |=== RSL connection timed out: | | | | | |8:41:02 AM,026,707 |1:A (Rx):31 | text |=== TEI = 3 Time Slot = 4 Channel = 1 | | | | | |8:41:02 AM,026,707 |1:A (Rx):31 | text |============================= | | | | | +--------------------+------------------------+-------+-------------------------------------------+------+--------+------------+------------+
A30808-X5226-C559-1-7618
7-53
s
|Long Time |From |2. Prot|2. MSG |3. Prot|3. MSG |4. Prot |4. MSG | +--------------------+------------------------+-------+-------------------------------------------+------+--------+------------+------------+ |8:41:02 AM,204,000 |1:A (Rx):31 |LAPD |INFO |RSL |DATIN |DTAP |CCONF | |8:41:02 AM,204,000 |1:A (Rx):31 |LAPD |INFO |RSL |DATIN |DTAP |CCONF | |8:41:02 AM,304,058 |1:A (Rx):31 |LAPD |INFO |RSL |DATIN |DTAP |ALERT | |8:41:02 AM,304,058 |1:A (Rx):31 |LAPD |INFO |RSL |DATIN |DTAP |ALERT | |8:41:07 AM,118,063 |1:A (Rx):31 |LAPD |INFO |RSL |RESIN | | | |8:41:07 AM,321,314 |1:A (Rx):31 |LAPD |INFO |RSL |RESIN | | | |8:41:08 AM,131,681 |1:A (Rx):31 |LAPD |INFO |RSL |RESIN | | | |8:41:09 AM,365,051 |1:A (Rx):31 |LAPD |INFO |RSL |DATIN |DTAP |HOLD | |8:41:09 AM,365,051 |1:A (Rx):31 |LAPD |INFO |RSL |DATIN |DTAP |HOLD | |8:41:09 AM,522,505 |1:B (Rx):31 |LAPD |INFO |RSL |DATRQ |DTAP |HOLDACK | |8:41:09 AM,522,505 |1:B (Rx):31 |LAPD |INFO |RSL |DATRQ |DTAP |HOLDACK | |8:41:09 AM,561,759 |1:B (Rx):31 |LAPD |INFO |RSL |DATRQ |DTAP |FACIL | |8:41:09 AM,683,804 |1:A (Rx):31 |LAPD |INFO |RSL |DATIN |DTAP |CONNECT | |8:41:09 AM,683,804 |1:A (Rx):31 |LAPD |INFO |RSL |DATIN |DTAP |CONNECT | |8:41:09 AM,872,505 |1:B (Rx):31 |LAPD |INFO |RSL |DATRQ |DTAP |CONACK | |8:41:09 AM,872,505 |1:B (Rx):31 |LAPD |INFO |RSL |DATRQ |DTAP |CONACK | |8:41:27 AM,048,110 |1:A (Rx):31 | text |=========================== | | | | | |8:41:27 AM,048,110 |1:A (Rx):31 | text |=== RSL connection timed out: | | | | |
A30808-X5226-C559-1-7618
7-54
s
|8:41:27 | |8:41:27 | |8:41:32 |DATIN |8:41:32 |DATIN |8:41:32 |DATRQ |8:41:32 |DATRQ |8:41:32 |DATRQ |8:41:37 | |8:41:37 | |8:41:38 |RESIN |8:41:38 |RESIN |8:41:39 |RESIN |8:42:09 |RESIN |8:42:09 |RESIN |8:42:10 |RESIN |8:42:17 |DATIN |8:42:17 |DATIN |8:42:18 |DATRQ |8:42:18 |DATRQ |8:42:18 |DATRQ AM,048,110 | AM,048,110 | AM,183,717 |DTAP AM,303,726 |DTAP AM,472,420 |DTAP AM,497,428 |DTAP AM,511,718 |DTAP AM,051,644 | AM,058,554 | AM,084,085 | AM,286,822 | AM,097,955 | AM,050,315 | AM,253,084 | AM,063,952 | AM,825,553 |DTAP AM,944,797 |DTAP AM,134,757 |DTAP AM,137,363 |DTAP AM,186,377 |DTAP |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 |HOLD |1:A (Rx):31 |RETRV |1:B (Rx):31 |HOLDACK |1:B (Rx):31 |RETRACK |1:B (Rx):31 |FACIL |1:B (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 |HOLD |1:A (Rx):31 |RETRV |1:B (Rx):31 |HOLDACK |1:B (Rx):31 |RETRACK |1:B (Rx):31 |FACIL | text | text |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD |LAPD |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |INFO |INFO | | |RSL | | |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |=== TEI = 1 Time Slot = 5 Channel = 1 | | |RSL | | |============================= |INFO
A30808-X5226-C559-1-7618
7-55
s
|8:42:29 |DATIN |8:42:29 |DATRQ |8:42:29 |DATIN |8:42:33 |DATIN |8:42:33 |DATRQ |8:42:34 |DATRQ |8:42:34 |DATIN |8:42:34 |DATIN |8:42:34 |DATRQ |8:42:34 |DESAC |8:42:34 |DATRQ |8:42:34 |DATRQ |8:42:34 |DESAC |8:42:34 |RELIN |8:42:34 |RELIN |8:42:35 |RCHRL |8:42:35 |RCHRA |8:42:36 |RCHRL |8:42:36 |RCHRA |8:42:37 | AM,442,635 |DTAP AM,622,710 |DTAP AM,742,755 |DTAP AM,785,869 |DTAP AM,985,195 |DTAP AM,009,938 |DTAP AM,122,870 |DTAP AM,145,358 |DTAP AM,284,694 |DTAP AM,286,423 | AM,322,690 |DTAP AM,325,424 |DTAP AM,327,628 | AM,486,740 | AM,647,234 | AM,046,938 | AM,051,969 | AM,146,184 | AM,151,458 | AM,051,417 | |1:A (Rx):31 |DISC |1:B (Rx):31 |RELEAS |1:A (Rx):31 |RELCMP |1:A (Rx):31 |DISC |1:B (Rx):31 |RELEAS |1:B (Rx):31 |DISC |1:A (Rx):31 |RELCMP |1:A (Rx):31 |RELEAS |1:B (Rx):31 |CHREL |1:B (Rx):31 | |1:B (Rx):31 |RELCMP |1:B (Rx):31 |CHREL |1:B (Rx):31 | |1:A (Rx):31 | |1:A (Rx):31 | |1:B (Rx):31 | |1:A (Rx):31 | |1:B (Rx):31 | |1:A (Rx):31 | |1:B (Rx):31 | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD | |LAPD |INFO | | |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL |INFO |RSL
A30808-X5226-C559-1-7618
7-56
s
|8:42:37 AM,056,204 |1:A (Rx):31 |LAPD |INFO | | | | | +--------------------+------------------------+-------+-------------------------------------------+------+--------+------------+------------+ |Long Time |From |2. Prot|2. MSG |3. Prot|3. MSG |4. Prot |4. MSG | +--------------------+------------------------+-------+-------------------------------------------+------+--------+------------+------------+ |8:42:40 AM,015,842 |1:A (Rx):31 |LAPD |INFO |RSL |RESIN | | | |8:42:40 AM,218,464 |1:A (Rx):31 |LAPD |INFO |RSL |RESIN | | | |8:42:41 AM,030,716 |1:A (Rx):31 |LAPD |INFO |RSL |RESIN | | | |8:42:52 AM,542,154 |L1: 0/A | L1 |SWITCH OFF | | | | | K1297-G20 1 SHORT VIEW MENSAGENS / 23 MOC / MTC / LU 17/01/02
A30808-X5226-C559-1-7618
7-57
INTERFACE A
MENSAGENS LU, MOC, MTC, PAGING
A30808-X5226-C559-1-7618
7-56
s
INTERFACE A MENSAGENS LU, MOC, MTC, PAGING
+--------------------+------------------------+------------+------------+------------+------------+-----------+------------+--------------------+--------------------+ |Long Time |From |2. Prot |2. MSG |3. Prot |3. MSG |4. Prot |4. MSG |Called Party |Calling Party | +--------------------+------------------------+------------+------------+------------+------------+-----------+------------+--------------------+--------------------+ |3:42:22 PM,335,848 |2:A (Rx):1 | text |============|============|============|==== | | | | |3:42:22 PM,335,848 |2:A (Rx):1 | text |=== Call tra|cing started|. === | | | | | |3:42:22 PM,335,848 |2:A (Rx):1 | text |===---------|------------|------------|---| | | | |3:42:22 PM,335,848 |2:A (Rx):1 | text |=== Paramete|rs for searc|h: === | | | | | |3:42:22 PM,335,848 |2:A (Rx):1 | text |=== Work mod|e: |Sequenced | | | | | |3:42:22 PM,335,848 |2:A (Rx):1 | text |=== Number: | |* | | | | | |3:42:22 PM,335,848 |2:A (Rx):1 | text |=== Type of |Number: |IMSI | | | | | |3:42:22 PM,335,848 |2:A (Rx):1 | text |=== Trace mo|de: |Multiple | | | | | |3:42:22 PM,335,848 |2:A (Rx):1 | text |=== Filter m|ode: |Forward fram|es | | | | |3:42:22 PM,335,848 |2:A (Rx):1 | text |=== Unsequen|ced frames: |Forward | | | | | |3:42:22 PM,335,848 |2:A (Rx):1 | text |=== Text mod|e: |Detailed tex|t | | | | |3:42:22 PM,335,848 |2:A (Rx):1 | text |============|============|============|==== | | | | |3:42:34 PM,422,658 |2:B (Rx):16 |MTP-L2 |MSU |MTP-T&M |SLTM | | | | | |3:42:34 PM,423,797 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | |
A30808-X5226-C559-1-7618
7-57
s
|3:42:34 | |3:42:34 | |3:42:34 | |3:42:34 | |3:42:39 | |3:42:39 | |3:42:39 | |3:42:44 |CL3I |3:42:44 | |3:42:44 | |3:42:44 |CICMD |3:42:44 | |3:42:44 | |3:42:44 |CLUPD |3:42:44 | |3:42:44 | |3:42:44 |CICMP |3:42:44 | |3:42:44 | |3:42:45 |TRCMD PM,426,098 | PM,440,167 | PM,441,611 | PM,443,250 | PM,139,598 | PM,140,837 | PM,141,956 | PM,502,595 | PM,503,708 | PM,506,516 | PM,593,513 | PM,594,653 | PM,595,964 | PM,735,833 | PM,736,953 | PM,739,637 | PM,987,113 | PM,988,248 | PM,990,506 | PM,026,757 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |MTP-L2 | |MTP-L2 | |MSU |SCCP |DT1 |DTAP |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |BSSM |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |BSSM |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |CC |BSSM |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |CR |BSSM |MTP-L2 | |FISU | | | |MTP-L2 | | | | | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTA | |FISU | | |
A30808-X5226-C559-1-7618
7-58
s
|3:42:45 | |3:42:45 | |3:42:45 |SETUP |3:42:45 | |3:42:45 | |3:42:45 |CPROC |3:42:45 | |3:42:45 | |3:42:45 |ASREQ |3:42:45 | |3:42:45 | |3:42:45 |TRCMP |3:42:45 | |3:42:45 | |3:42:46 |ASCMP |3:42:46 | |3:42:46 | |3:42:46 |PAGIN |3:42:46 | |3:42:46 | PM,028,021 |2:A | PM,029,829 |2:B | PM,223,732 |2:B |99956604 PM,224,865 |2:B | PM,227,808 |2:A | PM,308,504 |2:A | PM,309,628 |2:A | PM,311,489 |2:B | PM,318,286 |2:A | PM,319,419 |2:A | PM,320,576 |2:B | PM,434,570 |2:B | PM,435,691 |2:B | PM,438,495 |2:A | PM,297,590 |2:B | PM,298,723 |2:B | PM,300,977 |2:A | PM,554,731 |2:A | PM,555,844 |2:A | PM,557,420 |2:B | (Rx):16 | (Rx):16 | (Rx):16 | (Rx):16 | (Rx):16 | (Rx):16 | (Rx):16 | (Rx):16 | (Rx):16 | (Rx):16 | (Rx):16 | (Rx):16 | (Rx):16 | (Rx):16 | (Rx):16 | (Rx):16 | (Rx):16 | (Rx):16 | (Rx):16 | (Rx):16 | |MTP-L2 | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |UDT |BSSM |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |BSSM |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |DTAP |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |BSSM |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |DTAP |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |DTAP |MTP-L2 | |FISU | | | |FISU | | |
A30808-X5226-C559-1-7618
7-59
s
|3:42:47 PM,689,410 |2:B (Rx):16 |MTP-L2 |MSU |SCCP |CR |BSSM |CL3I | | | |3:42:47 PM,690,519 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:42:47 PM,693,331 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:42:47 PM,799,330 |2:A (Rx):16 |MTP-L2 |MSU |SCCP |CC |BSSM |CICMD | | | |3:42:47 PM,800,450 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | +--------------------+------------------------+------------+------------+------------+------------+-----------+------------+--------------------+--------------------+ |Long Time |From |2. Prot |2. MSG |3. Prot |3. MSG |4. Prot |4. MSG |Called Party |Calling Party | +--------------------+------------------------+------------+------------+------------+------------+-----------+------------+--------------------+--------------------+ |3:42:47 PM,801,904 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:42:47 PM,898,280 |2:B (Rx):16 |MTP-L2 |MSU |SCCP |DT1 |BSSM |CLUPD | | | |3:42:47 PM,899,524 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:42:47 PM,902,203 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:42:48 PM,136,801 |2:B (Rx):16 |MTP-L2 |MSU |SCCP |DT1 |BSSM |CICMP | | | |3:42:48 PM,137,937 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:42:48 PM,140,197 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:42:48 PM,180,447 |2:A (Rx):16 |MTP-L2 |MSU |SCCP |DT1 |DTAP |SETUP | |554199956600 | |3:42:48 PM,181,572 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:42:48 PM,182,893 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:42:49 PM,085,752 |2:B (Rx):16 |MTP-L2 |MSU |SCCP |DT1 |DTAP |CCONF | | | |3:42:49 PM,086,878 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | |
A30808-X5226-C559-1-7618
7-60
s
|3:42:49 | |3:42:49 |ASREQ |3:42:49 | |3:42:49 | |3:42:50 |ASCMP |3:42:50 | |3:42:50 | |3:42:50 |ALERT |3:42:50 | |3:42:50 | |3:42:50 |ALERT |3:42:50 | |3:42:50 | |3:42:51 |CONNECT |3:42:51 | |3:42:51 | |3:42:51 |CONACK |3:42:51 | |3:42:51 | |3:42:51 |CONNECT PM,089,428 | PM,264,679 | PM,265,798 | PM,266,917 | PM,135,487 | PM,136,601 | PM,138,818 | PM,260,258 | PM,261,397 | PM,263,668 | PM,334,034 | PM,335,155 | PM,336,610 | PM,722,325 | PM,723,445 | PM,726,255 | PM,773,374 | PM,774,499 | PM,776,325 | PM,816,013 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |MTP-L2 | |MTP-L2 | |MSU |SCCP |DT1 |DTAP |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |DTAP |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |DTAP |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |DTAP |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |DTAP |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |BSSM |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |BSSM |FISU | | |
A30808-X5226-C559-1-7618
7-61
s
|3:42:51 | |3:42:51 | |3:42:52 |CONACK |3:42:52 | |3:42:52 | |3:42:53 |DISC |3:42:53 | |3:42:53 | |3:42:53 |RELEAS |3:42:53 | |3:42:53 | |3:42:53 |DISC |3:42:53 | |3:42:53 | |3:42:54 |RELCMP |3:42:54 | |3:42:54 | |3:42:54 |RELEAS |3:42:54 | |3:42:54 | PM,817,254 | PM,819,074 | PM,072,076 | PM,073,188 | PM,076,119 | PM,897,198 | PM,898,314 | PM,900,998 | PM,972,369 | PM,973,495 | PM,974,824 | PM,996,425 | PM,997,366 | PM,998,486 | PM,235,189 | PM,236,309 | PM,239,238 | PM,260,592 | PM,261,727 | PM,263,995 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |MTP-L2 | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |DTAP |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |DTAP |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |DTAP |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |DTAP |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |DTAP |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |DTAP |MTP-L2 | |FISU | | | |FISU | | |
A30808-X5226-C559-1-7618
7-62
s
|3:42:54 PM,275,855 |2:A (Rx):16 |MTP-L2 |MSU |SCCP |DT1 |BSSM |CLCMD | | | |3:42:54 PM,277,103 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:42:54 PM,278,557 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:42:54 PM,304,745 |2:A (Rx):16 |MTP-L2 |MSU |SCCP |DT1 |DTAP |RELCMP | | | |3:42:54 PM,305,983 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:42:54 PM,307,811 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:42:54 PM,318,997 |2:A (Rx):16 |MTP-L2 |MSU |SCCP |DT1 |BSSM |CLCMD | | | +--------------------+------------------------+------------+------------+------------+------------+-----------+------------+--------------------+--------------------+ |Long Time |From |2. Prot |2. MSG |3. Prot |3. MSG |4. Prot |4. MSG |Called Party |Calling Party | +--------------------+------------------------+------------+------------+------------+------------+-----------+------------+--------------------+--------------------+ |3:42:54 PM,320,110 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:42:54 PM,321,437 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:42:54 PM,334,689 |2:B (Rx):16 |MTP-L2 |MSU |SCCP |DT1 |BSSM |CLCMP | | | |3:42:54 PM,335,801 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:42:54 PM,338,488 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:42:54 PM,367,982 |2:A (Rx):16 |MTP-L2 |MSU |SCCP |RLSD | | | | | |3:42:54 PM,369,112 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:42:54 PM,372,311 |2:B (Rx):16 |MTP-L2 |MSU |SCCP |DT1 |BSSM |CLCMP | | | |3:42:54 PM,373,431 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:42:54 PM,375,978 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | |
A30808-X5226-C559-1-7618
7-63
s
|3:42:54 | |3:42:54 | |3:42:54 | |3:42:54 | |3:42:54 | |3:42:54 | |3:42:54 | |3:42:54 | |3:42:54 | |3:43:04 | |3:43:04 | |3:43:04 | |3:43:04 | |3:43:04 | |3:43:04 | |3:43:27 | |3:43:27 | |3:43:34 | |3:43:34 | |3:43:34 | PM,409,235 | PM,410,362 | PM,411,686 | PM,422,310 | PM,423,428 | PM,426,108 | PM,471,713 | PM,472,849 | PM,475,109 | PM,422,777 | PM,423,906 | PM,427,203 | PM,438,988 | PM,440,119 | PM,441,278 | PM,748,188 | PM,749,297 | PM,407,706 | PM,408,824 | PM,411,001 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |MTP-L2 | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTM | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTA | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTM | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |RLC | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |RLC | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MSU |SCCP |RLSD |
A30808-X5226-C559-1-7618
7-64
s
|3:43:34 | |3:43:34 | |3:43:34 | |3:43:52 | |3:43:52 | |3:44:04 | |3:44:04 | |3:44:04 | |3:44:04 | |3:44:04 | |3:44:04 | |3:44:34 | |3:44:34 | |3:44:34 | |3:44:34 | |3:44:34 | |3:44:34 | |3:45:04 | |3:45:04 | |3:45:04 | PM,424,249 | PM,425,370 | PM,427,073 | PM,012,118 | PM,013,354 | PM,405,957 | PM,407,074 | PM,410,005 | PM,422,156 | PM,423,288 | PM,424,457 | PM,406,110 | PM,407,228 | PM,409,439 | PM,420,280 | PM,421,403 | PM,422,976 | PM,405,900 | PM,407,008 | PM,409,585 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |MTP-L2 | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTM | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTA | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTM | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTA | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTM | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MSU |MTP-T&M |SLTA |
A30808-X5226-C559-1-7618
7-65
s
|3:45:04 PM,423,675 |2:A (Rx):16 |MTP-L2 |MSU |MTP-T&M |SLTA | | | | | |3:45:04 PM,424,795 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:45:04 PM,426,378 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:45:04 PM,518,309 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:45:04 PM,519,418 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:45:34 PM,392,207 |2:B (Rx):16 |MTP-L2 |MSU |MTP-T&M |SLTM | | | | | |3:45:34 PM,393,324 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:45:34 PM,395,542 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:45:34 PM,411,006 |2:A (Rx):16 |MTP-L2 |MSU |MTP-T&M |SLTA | | | | | +--------------------+------------------------+------------+------------+------------+------------+-----------+------------+--------------------+--------------------+ |Long Time |From |2. Prot |2. MSG |3. Prot |3. MSG |4. Prot |4. MSG |Called Party |Calling Party | +--------------------+------------------------+------------+------------+------------+------------+-----------+------------+--------------------+--------------------+ |3:45:34 PM,412,121 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:45:34 PM,413,950 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:45:52 PM,522,832 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:45:52 PM,524,436 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:46:04 PM,393,107 |2:B (Rx):16 |MTP-L2 |MSU |MTP-T&M |SLTM | | | | | |3:46:04 PM,394,227 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:46:04 PM,396,561 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:46:04 PM,411,780 |2:A (Rx):16 |MTP-L2 |MSU |MTP-T&M |SLTA | | | | |
A30808-X5226-C559-1-7618
7-66
s
|3:46:04 | |3:46:04 | |3:46:16 | |3:46:16 | |3:46:34 | |3:46:34 | |3:46:34 | |3:46:34 | |3:46:34 | |3:46:34 | |3:47:03 | |3:47:03 | |3:47:04 | |3:47:04 | |3:47:04 | |3:47:04 | |3:47:04 | |3:47:04 | |3:47:27 | |3:47:27 | PM,412,900 | PM,414,849 | PM,402,030 | PM,403,267 | PM,389,319 | PM,390,437 | PM,393,118 | PM,403,870 | PM,405,118 | PM,406,439 | PM,897,517 | PM,898,636 | PM,375,208 | PM,376,326 | PM,378,754 | PM,391,878 | PM,392,999 | PM,394,575 | PM,511,573 | PM,512,687 | |2:A (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |MTP-L2 | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTA | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTM | |MTP-L2 | |FISU | | | |MTP-L2 | | | | | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTA | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTM | |MTP-L2 | |FISU | | | |MTP-L2 | | | | | |MTP-L2 | |FISU | | | |FISU | | |
A30808-X5226-C559-1-7618
7-67
s
|3:47:34 | |3:47:34 | |3:47:34 | |3:47:34 | |3:47:34 | |3:47:34 | |3:47:51 | |3:47:51 | |3:48:04 | |3:48:04 | |3:48:04 | |3:48:04 | |3:48:04 | |3:48:04 | |3:48:14 | |3:48:14 | |3:48:34 | |3:48:34 | |3:48:34 | |3:48:34 | PM,374,942 | PM,376,082 | PM,378,346 | PM,389,079 | PM,390,327 | PM,392,029 | PM,032,305 | PM,033,420 | PM,375,068 | PM,376,304 | PM,379,112 | PM,389,897 | PM,391,026 | PM,392,184 | PM,457,095 | PM,458,323 | PM,373,822 | PM,376,221 | PM,377,181 | PM,390,233 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |MTP-L2 | |MTP-L2 | |MSU |MTP-T&M |SLTA | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTM | |MTP-L2 | |FISU | | | |MTP-L2 | | | | | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTA | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTM | |MTP-L2 | |FISU | | | |MTP-L2 | | | | | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTA | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MSU |MTP-T&M |SLTM |
A30808-X5226-C559-1-7618
7-68
s
|3:48:34 PM,391,766 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:48:34 PM,393,213 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:48:37 PM,788,185 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:48:37 PM,789,426 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:49:01 PM,028,424 |2:A (Rx):16 |MTP-L2 | | | | | | | | |3:49:01 PM,029,539 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:49:04 PM,361,215 |2:B (Rx):16 |MTP-L2 |MSU |MTP-T&M |SLTM | | | | | |3:49:04 PM,362,334 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:49:04 PM,365,139 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:49:04 PM,379,641 |2:A (Rx):16 |MTP-L2 |MSU |MTP-T&M |SLTA | | | | | |3:49:04 PM,380,759 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | +--------------------+------------------------+------------+------------+------------+------------+-----------+------------+--------------------+--------------------+ |Long Time |From |2. Prot |2. MSG |3. Prot |3. MSG |4. Prot |4. MSG |Called Party |Calling Party | +--------------------+------------------------+------------+------------+------------+------------+-----------+------------+--------------------+--------------------+ |3:49:04 PM,381,720 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:49:24 PM,182,130 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:49:24 PM,183,242 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:49:34 PM,359,129 |2:B (Rx):16 |MTP-L2 |MSU |MTP-T&M |SLTM | | | | | |3:49:34 PM,360,272 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:49:34 PM,362,525 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | |
A30808-X5226-C559-1-7618
7-69
s
|3:49:34 | |3:49:34 | |3:49:34 | |3:50:04 | |3:50:04 | |3:50:04 | |3:50:04 | |3:50:04 | |3:50:04 | |3:50:10 | |3:50:10 | |3:50:33 | |3:50:33 | |3:50:34 | |3:50:34 | |3:50:34 | |3:50:34 | |3:50:34 | |3:50:34 | |3:50:56 | PM,373,286 | PM,374,395 | PM,376,349 | PM,357,477 | PM,358,607 | PM,361,059 | PM,372,777 | PM,373,899 | PM,375,849 | PM,284,802 | PM,285,918 | PM,260,878 | PM,261,982 | PM,357,163 | PM,358,290 | PM,361,092 | PM,370,721 | PM,371,836 | PM,372,957 | PM,202,617 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |MTP-L2 | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTA | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTM | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |LSSU-SIO | | | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTA | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTM | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MSU |MTP-T&M |SLTA |
A30808-X5226-C559-1-7618
7-70
s
|3:50:56 | |3:51:04 | |3:51:04 | |3:51:04 | |3:51:04 | |3:51:04 | |3:51:04 | |3:51:34 | |3:51:34 | |3:51:34 | |3:51:34 | |3:51:34 | |3:51:34 | |3:51:42 | |3:51:42 | |3:52:04 | |3:52:04 | |3:52:04 | |3:52:04 | |3:52:04 | PM,203,728 | PM,344,474 | PM,345,612 | PM,347,895 | PM,359,622 | PM,360,861 | PM,362,684 | PM,344,294 | PM,345,536 | PM,347,969 | PM,366,815 | PM,367,837 | PM,369,789 | PM,032,703 | PM,033,816 | PM,343,564 | PM,344,686 | PM,347,364 | PM,359,620 | PM,360,736 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |MTP-L2 | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTA | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTM | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTA | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTM | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTA | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTM | |FISU | | |
A30808-X5226-C559-1-7618
7-71
s
|3:52:04 PM,362,063 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:52:04 PM,938,610 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:52:04 PM,939,846 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:52:27 PM,851,842 |2:A (Rx):16 |MTP-L2 | | | | | | | | |3:52:27 PM,853,094 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:52:34 PM,343,713 |2:B (Rx):16 |MTP-L2 |MSU |MTP-T&M |SLTM | | | | | |3:52:34 PM,344,840 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:52:34 PM,347,050 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:52:34 PM,361,150 |2:A (Rx):16 |MTP-L2 |MSU |MTP-T&M |SLTA | | | | | |3:52:34 PM,362,392 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:52:34 PM,363,965 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:52:50 PM,781,118 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:52:50 PM,782,234 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | +--------------------+------------------------+------------+------------+------------+------------+-----------+------------+--------------------+--------------------+ |Long Time |From |2. Prot |2. MSG |3. Prot |3. MSG |4. Prot |4. MSG |Called Party |Calling Party | +--------------------+------------------------+------------+------------+------------+------------+-----------+------------+--------------------+--------------------+ |3:53:04 PM,330,990 |2:B (Rx):16 |MTP-L2 |MSU |MTP-T&M |SLTM | | | | | |3:53:04 PM,332,107 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:53:04 PM,334,916 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:53:04 PM,345,667 |2:A (Rx):16 |MTP-L2 |MSU |MTP-T&M |SLTA | | | | |
A30808-X5226-C559-1-7618
7-72
s
|3:53:04 | |3:53:04 | |3:53:13 | |3:53:13 | |3:53:34 | |3:53:34 | |3:53:34 | |3:53:34 | |3:53:34 | |3:53:34 | |3:53:36 | |3:53:36 | |3:53:59 | |3:53:59 | |3:54:04 | |3:54:04 | |3:54:04 | |3:54:04 | |3:54:04 | |3:54:04 | PM,346,784 | PM,347,901 | PM,733,775 | PM,735,015 | PM,330,644 | PM,331,780 | PM,334,194 | PM,346,056 | PM,347,185 | PM,348,646 | PM,713,158 | PM,714,272 | PM,726,280 | PM,727,394 | PM,330,415 | PM,331,528 | PM,334,341 | PM,347,468 | PM,348,585 | PM,349,544 | |2:A (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |MTP-L2 | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTA | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTM | |MTP-L2 | |FISU | | | |MTP-L2 | | | | | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTA | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTM | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |FISU | | |
A30808-X5226-C559-1-7618
7-73
s
|3:54:22 | |3:54:22 | |3:54:34 | |3:54:34 | |3:54:34 | |3:54:34 | |3:54:34 | |3:54:34 | |3:54:45 | |3:54:45 | |3:54:55 |CL3I |3:54:55 | |3:54:55 | |3:54:55 |LUACC |3:54:55 | |3:54:55 | |3:54:55 |CLCMD |3:54:55 | |3:54:55 | |3:54:55 |CLCMP PM,775,316 | PM,776,579 | PM,327,835 | PM,328,933 | PM,331,480 | PM,345,502 | PM,346,607 | PM,348,058 | PM,863,219 | PM,864,340 | PM,219,407 | PM,220,525 | PM,223,457 | PM,299,960 | PM,301,074 | PM,302,647 | PM,311,696 | PM,312,818 | PM,313,932 | PM,401,277 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |MTP-L2 | |MTP-L2 | |MSU |SCCP |DT1 |BSSM |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |BSSM |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |CC |DTAP |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |CR |BSSM |MTP-L2 | |FISU | | | |MTP-L2 | | | | | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTA | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTM | |MTP-L2 | |FISU | | | |FISU | | |
A30808-X5226-C559-1-7618
7-74
s
|3:54:55 PM,402,397 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:54:55 PM,405,078 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:54:55 PM,430,856 |2:A (Rx):16 |MTP-L2 |MSU |SCCP |RLSD | | | | | |3:54:55 PM,432,238 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:54:55 PM,433,151 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:54:55 PM,475,149 |2:B (Rx):16 |MTP-L2 |MSU |SCCP |RLC | | | | | |3:54:55 PM,476,270 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:54:55 PM,479,194 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:55:04 PM,314,568 |2:B (Rx):16 |MTP-L2 |MSU |MTP-T&M |SLTM | | | | | |3:55:04 PM,315,697 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:55:04 PM,317,982 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:55:04 PM,329,839 |2:A (Rx):16 |MTP-L2 |MSU |MTP-T&M |SLTA | | | | | |3:55:04 PM,330,954 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:55:04 PM,332,533 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:55:34 PM,310,543 |2:B (Rx):16 |MTP-L2 |MSU |MTP-T&M |SLTM | | | | | +--------------------+------------------------+------------+------------+------------+------------+-----------+------------+--------------------+--------------------+ |Long Time |From |2. Prot |2. MSG |3. Prot |3. MSG |4. Prot |4. MSG |Called Party |Calling Party | +--------------------+------------------------+------------+------------+------------+------------+-----------+------------+--------------------+--------------------+ |3:55:34 PM,311,662 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:55:34 PM,313,593 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | |
A30808-X5226-C559-1-7618
7-75
s
|3:55:34 | |3:55:34 | |3:55:34 | |3:56:04 | |3:56:04 | |3:56:04 | |3:56:04 | |3:56:04 | |3:56:04 | |3:56:34 | |3:56:34 | |3:56:34 | |3:56:34 | |3:56:34 | |3:56:34 | |3:57:04 | |3:57:04 | |3:57:04 | |3:57:04 | |3:57:04 | PM,327,844 | PM,328,958 | PM,330,784 | PM,308,528 | PM,309,647 | PM,312,338 | PM,326,571 | PM,327,730 | PM,329,038 | PM,295,773 | PM,296,896 | PM,299,949 | PM,313,979 | PM,315,114 | PM,316,275 | PM,295,824 | PM,296,964 | PM,299,223 | PM,312,100 | PM,313,220 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |MTP-L2 | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTA | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTM | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTA | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTM | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTA | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTM | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MSU |MTP-T&M |SLTA |
A30808-X5226-C559-1-7618
7-76
s
|3:57:04 | |3:57:05 | |3:57:05 | |3:57:07 |CL3I |3:57:07 | |3:57:07 | |3:57:07 |LUACC |3:57:07 | |3:57:07 | |3:57:07 |CLCMD |3:57:07 | |3:57:07 | |3:57:07 |CLCMP |3:57:07 | |3:57:07 | |3:57:07 | |3:57:07 | |3:57:07 | |3:57:07 | |3:57:07 | PM,314,918 | PM,309,588 | PM,310,824 | PM,287,619 | PM,288,857 | PM,291,918 | PM,386,164 | PM,387,290 | PM,389,109 | PM,398,071 | PM,399,206 | PM,400,364 | PM,456,357 | PM,457,483 | PM,460,312 | PM,488,038 | PM,489,154 | PM,490,117 | PM,530,985 | PM,532,105 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |MTP-L2 | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |RLC | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |RLSD | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |BSSM |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |BSSM |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |CC |DTAP |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |CR |BSSM |MTP-L2 | |FISU | | | |MTP-L2 | | | | | |FISU | | |
A30808-X5226-C559-1-7618
7-77
s
|3:57:07 PM,534,160 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:57:28 PM,712,614 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:57:28 PM,713,727 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:57:34 PM,295,037 |2:B (Rx):16 |MTP-L2 |MSU |MTP-T&M |SLTM | | | | | |3:57:34 PM,296,170 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:57:34 PM,298,429 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:57:34 PM,311,309 |2:A (Rx):16 |MTP-L2 |MSU |MTP-T&M |SLTA | | | | | |3:57:34 PM,312,547 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:57:34 PM,314,126 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:57:50 PM,191,072 |2:A (Rx):16 |MTP-L2 |MSU |SCCP |UDT |BSSM |PAGIN | | | |3:57:50 PM,192,196 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:57:50 PM,193,356 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:57:51 PM,099,347 |2:B (Rx):16 |MTP-L2 |MSU |SCCP |CR |BSSM |CL3I | | | |3:57:51 PM,100,458 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:57:51 PM,103,387 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:57:51 PM,199,269 |2:A (Rx):16 |MTP-L2 |MSU |SCCP |CC |BSSM |CICMD | | | |3:57:51 PM,200,391 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | +--------------------+------------------------+------------+------------+------------+------------+-----------+------------+--------------------+--------------------+ |Long Time |From |2. Prot |2. MSG |3. Prot |3. MSG |4. Prot |4. MSG |Called Party |Calling Party | +--------------------+------------------------+------------+------------+------------+------------+-----------+------------+--------------------+--------------------+
A30808-X5226-C559-1-7618
7-78
s
|3:57:51 | |3:57:51 |CLUPD |3:57:51 | |3:57:51 | |3:57:51 |CICMP |3:57:51 | |3:57:51 | |3:57:51 |SETUP |3:57:51 | |3:57:51 | |3:57:52 |CCONF |3:57:52 | |3:57:52 | |3:57:52 |ASREQ |3:57:52 | |3:57:52 | |3:57:53 |ASCMP |3:57:53 | |3:57:53 | |3:57:53 |ALERT PM,201,706 | PM,307,335 | PM,308,452 | PM,311,139 | PM,558,608 | PM,559,749 | PM,562,002 | PM,598,383 | PM,599,629 | PM,601,331 | PM,032,073 | PM,033,192 | PM,035,242 | PM,211,494 | PM,212,616 | PM,214,315 | PM,106,554 | PM,107,668 | PM,110,477 | PM,231,299 | |2:B (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 |55418880 |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |MTP-L2 | |MTP-L2 | |MSU |SCCP |DT1 |DTAP |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |BSSM |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |BSSM |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |DTAP |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |DTAP |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |BSSM |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |BSSM |FISU | | |
A30808-X5226-C559-1-7618
7-79
s
|3:57:53 | |3:57:53 | |3:58:00 |CONNECT |3:58:00 | |3:58:00 | |3:58:00 |CONACK |3:58:00 | |3:58:00 | |3:58:04 | |3:58:04 | |3:58:04 | |3:58:04 | |3:58:04 | |3:58:04 | |3:58:18 |STDTMF |3:58:18 | |3:58:18 | |3:58:18 |STDACK |3:58:18 | |3:58:18 | PM,232,420 | PM,234,970 | PM,406,442 | PM,407,568 | PM,410,495 | PM,460,121 | PM,461,242 | PM,462,684 | PM,295,030 | PM,296,144 | PM,298,703 | PM,308,363 | PM,309,453 | PM,310,772 | PM,467,203 | PM,468,338 | PM,470,590 | PM,535,754 | PM,536,963 | PM,538,088 | |2:B (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |MTP-L2 | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |DTAP |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |DTAP |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTA | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTM | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |DTAP |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |DTAP |MTP-L2 | |FISU | | | |FISU | | |
A30808-X5226-C559-1-7618
7-80
s
|3:58:18 PM,767,417 |2:B (Rx):16 |MTP-L2 |MSU |SCCP |DT1 |DTAP |SPDTMF | | | |3:58:18 PM,768,542 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:58:18 PM,771,092 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:58:18 PM,841,831 |2:A (Rx):16 |MTP-L2 |MSU |SCCP |DT1 |DTAP |SPDACK | | | |3:58:18 PM,842,962 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:58:18 PM,844,106 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:58:19 PM,367,657 |2:B (Rx):16 |MTP-L2 |MSU |SCCP |DT1 |DTAP |STDTMF | | | |3:58:19 PM,368,771 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:58:19 PM,371,076 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:58:19 PM,437,113 |2:A (Rx):16 |MTP-L2 |MSU |SCCP |DT1 |DTAP |STDACK | | | |3:58:19 PM,438,209 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:58:19 PM,439,524 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:58:19 PM,667,773 |2:B (Rx):16 |MTP-L2 |MSU |SCCP |DT1 |DTAP |SPDTMF | | | |3:58:19 PM,668,889 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:58:19 PM,671,101 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:58:19 PM,737,320 |2:A (Rx):16 |MTP-L2 |MSU |SCCP |DT1 |DTAP |SPDACK | | | |3:58:19 PM,738,452 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:58:19 PM,739,772 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:58:21 PM,494,165 |2:B (Rx):16 |MTP-L2 |MSU |SCCP |DT1 |DTAP |CMSREQ | | | +--------------------+------------------------+------------+------------+------------+------------+-----------+------------+--------------------+--------------------+
A30808-X5226-C559-1-7618
7-81
s
|Long Time |From |2. Prot |2. MSG |3. Prot |3. MSG |4. Prot |4. MSG |Called Party |Calling Party | +--------------------+------------------------+------------+------------+------------+------------+-----------+------------+--------------------+--------------------+ |3:58:21 PM,495,116 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:58:21 PM,497,667 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:58:21 PM,553,792 |2:A (Rx):16 |MTP-L2 |MSU |SCCP |DT1 |DTAP |CMSACC | | | |3:58:21 PM,554,911 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:58:21 PM,555,872 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:58:21 PM,945,605 |2:B (Rx):16 |MTP-L2 |MSU |SCCP |DT1 |DTAP |REG | | | |3:58:21 PM,946,726 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:58:21 PM,948,658 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:58:22 PM,019,531 |2:A (Rx):16 |MTP-L2 |MSU |SCCP |DT1 |DTAP |RELC | | | |3:58:22 PM,020,777 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:58:22 PM,022,104 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:58:22 PM,293,600 |2:B (Rx):16 |MTP-L2 |MSU |SCCP |DT1 |DTAP |CMSREQ | | | |3:58:22 PM,294,766 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:58:22 PM,297,904 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:58:22 PM,358,150 |2:A (Rx):16 |MTP-L2 |MSU |SCCP |DT1 |DTAP |CMSACC | | | |3:58:22 PM,359,267 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:58:22 PM,361,153 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:58:22 PM,363,907 |2:A (Rx):16 |MTP-L2 |MSU |SCCP |DT1 |DTAP |TRCMD | | |
A30808-X5226-C559-1-7618
7-82
s
|3:58:22 | |3:58:22 | |3:58:22 |REG |3:58:22 | |3:58:22 | |3:58:22 |RELC |3:58:22 | |3:58:22 | |3:58:22 |TRCMP |3:58:22 | |3:58:22 | |3:58:34 | |3:58:34 | |3:58:34 | |3:58:34 | |3:58:34 | |3:58:34 | |3:58:38 |DISC |3:58:38 | |3:58:38 | PM,365,018 | PM,366,594 | PM,631,716 | PM,632,837 | PM,635,144 | PM,709,396 | PM,710,512 | PM,711,649 | PM,741,839 | PM,742,962 | PM,745,400 | PM,279,784 | PM,280,734 | PM,283,787 | PM,294,403 | PM,295,530 | PM,297,085 | PM,792,982 | PM,794,115 | PM,795,271 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |MTP-L2 | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |DTAP |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTA | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTM | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |DTAP |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |DTAP |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |DTAP |MTP-L2 | |FISU | | | |FISU | | |
A30808-X5226-C559-1-7618
7-83
s
|3:58:39 |RELEAS |3:58:39 | |3:58:39 | |3:58:39 |RELCMP |3:58:39 | |3:58:39 | |3:58:39 |CLCMD |3:58:39 | |3:58:39 | |3:58:39 |CLCMP |3:58:39 | |3:58:39 | |3:58:39 | |3:58:39 | |3:58:39 | |3:58:39 | |3:58:39 | |3:58:39 | |3:59:02 | |3:59:02 | PM,029,644 | PM,031,221 | PM,033,955 | PM,075,947 | PM,077,069 | PM,078,020 | PM,081,242 | PM,082,079 | PM,083,633 | PM,140,644 | PM,141,762 | PM,143,974 | PM,173,940 | PM,175,063 | PM,176,638 | PM,228,270 | PM,229,388 | PM,232,324 | PM,776,083 | PM,777,202 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |MTP-L2 | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |RLC | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |RLSD | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |BSSM |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |BSSM |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |DTAP |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MSU |SCCP |DT1 |DTAP
A30808-X5226-C559-1-7618
7-84
s
|3:59:04 PM,277,407 |2:B (Rx):16 |MTP-L2 |MSU |MTP-T&M |SLTM | | | | | +--------------------+------------------------+------------+------------+------------+------------+-----------+------------+--------------------+--------------------+ |Long Time |From |2. Prot |2. MSG |3. Prot |3. MSG |4. Prot |4. MSG |Called Party |Calling Party | +--------------------+------------------------+------------+------------+------------+------------+-----------+------------+--------------------+--------------------+ |3:59:04 PM,278,527 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:59:04 PM,281,580 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:59:04 PM,294,585 |2:A (Rx):16 |MTP-L2 |MSU |MTP-T&M |SLTA | | | | | |3:59:04 PM,295,827 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:59:04 PM,297,651 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:59:26 PM,412,510 |2:A (Rx):16 |MTP-L2 | | | | | | | | |3:59:26 PM,413,617 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:59:34 PM,276,715 |2:B (Rx):16 |MTP-L2 |MSU |MTP-T&M |SLTM | | | | | |3:59:34 PM,277,827 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:59:34 PM,280,246 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:59:34 PM,292,238 |2:A (Rx):16 |MTP-L2 |MSU |MTP-T&M |SLTA | | | | | |3:59:34 PM,293,397 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:59:34 PM,294,702 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:59:50 PM,092,989 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:59:50 PM,094,223 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |4:00:04 PM,276,439 |2:B (Rx):16 |MTP-L2 |MSU |MTP-T&M |SLTM | | | | |
A30808-X5226-C559-1-7618
7-85
s
|4:00:04 | |4:00:04 | |4:00:04 | |4:00:04 | |4:00:04 | |4:00:13 | |4:00:13 | |4:00:34 | |4:00:34 | |4:00:34 | |4:00:34 | |4:00:34 | |4:00:34 | |4:01:01 | |4:01:01 | |4:01:04 | |4:01:04 | |4:01:04 | |4:01:04 | |4:01:04 | PM,277,564 | PM,280,614 | PM,293,621 | PM,294,741 | PM,295,854 | PM,818,123 | PM,819,236 | PM,263,839 | PM,264,956 | PM,267,759 | PM,280,766 | PM,282,044 | PM,283,208 | PM,399,222 | PM,400,319 | PM,264,255 | PM,265,375 | PM,268,185 | PM,278,953 | PM,280,054 |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 |MTP-L2 |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTA | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTM | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTA | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTM | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |MTP-T&M |SLTA | |MTP-L2 | |FISU | | | |FISU | | |
A30808-X5226-C559-1-7618
7-86
s
+--------------------+------------------------+------------+------------+------------+------------+-----------+------------+--------------------+--------------------+ |Long Time |From |2. Prot |2. MSG |3. Prot |3. MSG |4. Prot |4. MSG |Called Party |Calling Party | +--------------------+------------------------+------------+------------+------------+------------+-----------+------------+--------------------+--------------------+ |3:42:48 PM,140,197 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:42:48 PM,180,447 |2:A (Rx):16 |MTP-L2 |MSU |SCCP |DT1 |DTAP |SETUP | |554199956600 | |3:42:48 PM,181,572 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | |3:42:48 PM,182,893 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:42:49 PM,085,752 |2:B (Rx):16 |MTP-L2 |MSU |SCCP |DT1 |DTAP |CCONF | | |
+--------------------+------------------------+------------+------------+------------+------------+-----------+------------+--------------------+--------------------+ |Long Time |From |2. Prot |2. MSG |3. Prot |3. MSG |4. Prot |4. MSG |Called Party |Calling Party | +--------------------+------------------------+------------+------------+------------+------------+-----------+------------+--------------------+--------------------+ |3:42:45 PM,029,829 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:42:45 PM,223,732 |2:B (Rx):16 |MTP-L2 |MSU |SCCP |DT1 |DTAP |SETUP |99956604 | | |3:42:45 PM,224,865 |2:B (Rx):16 |MTP-L2 |FISU | | | | | | | |3:42:45 PM,227,808 |2:A (Rx):16 |MTP-L2 |FISU | | | | | | | ---+------------+--------------------+--------------------+ |Long Time |From |2. Prot |2. MSG |3. Prot |3. MSG |4. Prot |4. MSG |Called Party |Calling Party | +--------------------+------------------------+------------+------------+------------+------------+-----------+------------+--------------------+--------------------+
A30808-X5226-C559-1-7618
7-87
s
|2:53:25 |HOREQ |2:53:25 | |2:53:25 | |2:53:25 |HORAC |2:53:25 | |2:53:25 | |2:53:26 |HOCMD |2:53:26 | |2:53:26 | |2:53:26 |HODET |2:53:26 | |2:53:26 | |2:53:26 |HOCMP |2:53:26 | |2:53:26 | |2:53:26 |CLCMD PM,805,334 | PM,806,458 | PM,807,586 | PM,943,685 | PM,944,819 | PM,947,077 | PM,078,951 | PM,080,070 | PM,081,649 | PM,352,653 | PM,353,761 | PM,357,345 | PM,639,387 | PM,640,761 | PM,643,694 | PM,720,693 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:B (Rx):16 | |2:B (Rx):16 | |2:A (Rx):16 | |2:A (Rx):16 | GSM By Otto Wutzke 17/01/02 31-30 |MTP-L2 | |MTP-L2 | |MSU |SCCP |DT1 |BSSM |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |BSSM |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |BSSM |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |DT1 |BSSM |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MTP-L2 | |MSU |SCCP |CC |BSSM |MTP-L2 | |FISU | | | |MTP-L2 | |FISU | | | |MSU |SCCP |CR |BSSM
SIEMENS TRAINING CENTER K1297-G20 INTERFACE A -
LU-MOC-MTC- PAGING -HANDOVER
A30808-X5226-C559-1-7618
7-88
PLMN
Course MN1788 File 2
A30808-X5226-C559-1-7618
Siemens Ltda. Centro de Treinamento Werner von Siemens R. Pedro Gusso, 2635 - CEP 81310-900 - Curitiba - PR Tel./Fax: (++41) 341-6722 / 341-5013 Al Aluno: (++41) 341-6592 CAS - Central de Atendimento Siemens: 0800 119484 Homepage: http://www.siemens.com.br/IC/tti/index.htm e-mail: treinamento@siemens.com.br
Siemens
MN1788EU08MN_0001 Export Control Marks: AL: 5A001b1 EC:N This course is subject to the European Export Control Restrictions.
2000 Siemens AG The reproduction, transmission or use of this document or its contents is not permitted without express written authority. Offenders will be liable for damages. All rights, including rights created by patent grant or registration of utility model or design, are reserved. Technical modifications possible. Technical specifications and features are binding only insofar as they are specifically and expressly agreed upon in a written contract.
II
MN1788EU08MN_0001
BSC Database
Siemens
1 2 3 4 5 6 7 8 9 10
Cell Selection / Cell Reselection
Sub-sections
Handover
Channel Configuration
Hierarchical Cell Structure
Radio Link Failure

SBS System Specialist TAC File 2 MN1788EU08MN_0001
Overload Handling
Interference Reduction
Error Symptom Saving
IMSI Tracing and Cell Traffic Recording
MN1788EU08MN_0001
III
Siemens
Sub-section reference
Sub-section identification 1 2 3 4 5 6 7 8 9 10 MN1788EU08 BSC Database MN_0001 MN1788EU08 Cell Selection/Reselect. MN_0001 MN1788EU08 Handover MN_0001 MN1788EU08 Channel Configuration MN_0001 MN1788EU08 Hierarchical Cell Struct. MN_0001 MN1788EU08 Radio Link Failure MN_0001 MN1788EU08 Overload Handling MN_0001 MN1788EU08 Interference Reduction MN_0001 MN1788EU08 Error Symptom Saving MN_0001 MN1788EU08 IMSI Tracing MN_0001 1 1 1 1 1 1 1 1 1 1 Pages 66 30 60 46 42 12 14 30 26 22
This document consists of 352 pages.
MN1788EU08MN_0001
BSC Database
Siemens
BSC Database
Contents
1 2 2.1 2.2 2.3 2.4 3 4 4.1 4.2 5 6 Creation Tree Explanation of Database Entries Creation of PPLD, LICD/LICDS and EPWR Creation of Objects on the BTSE Side Creation of Objects on the TRAU Side Summary: GPRS Objects Database Example Example of Timeslot Assignment on Interfaces Asub and A Interface Abis and Um Interface Table of Frequency Bands Exercises 3 7 7 9 23 37 39 58 58 60 62 63
A30808-X5226-C559-1-7618
1-66
Siemens
BSC Database
1-2
A30808-X5226-C559-1-7618
BSC Database
Siemens
Creation Tree
The Creation Tree shown contains the objects in the BSC database. Moreover, it shows the specific order, in which these objects have to be created in the database.
A30808-X5226-C559-1-7618
3-66
Siemens
BSC Database
DELETE
CREATE
Fig. 1 Creation tree
1-4
A30808-X5226-C559-1-7618
BSC Database
Siemens
The CREATE command is used to add new objects to the system. Objects must be created starting from the root down to the leaves of the tree. Objects can be removed from the database as well (DELETE command). Therefore the deletion must be performed in the opposite order, from the leaves up to the root. The objects on the same line can be created without preconditions. Objects closed in a dashed rectangle correspond to each other and must be created together.
A30808-X5226-C559-1-7618
5-66
Siemens
BSC Database
DELETE
CREATE
Fig. 2 Creation tree
LPDLM&LPDLR
LPDLS
SS7L
Um
BTSE PCMB Abis
BSC PCMS Asub
TRAU PCMA A
MSC
BSSGP
SGSN PCMG Gb
Fig. 3 Interfaces and signaling
1-6
A30808-X5226-C559-1-7618
BSC Database
Siemens
Explanation of Database Entries
In the database the structure of the network controlled by the BSC is defined by logical objects (cells, carriers, etc.) as well as some physical objects (hardware) of the BSC. For the hardware, only the PPLD (and PCU), LICD and EPWR modules equipped are listed in the database. All other hardware modules are created automatically during commissioning without an entry in the database. The objects in the database are created according to the order shown in the creation tree below. In the following chapters the most important parameters are explained using the highlighted commands of the example database given below.
2.1
Creation of PPLD, LICD/LICDS and EPWR
First all the PPLD and LICD (LICDS) boards needed have to be created. If modules of the expansion subrack are equipped, the power supply of the expansion subrack (EPWR) has to be created first.
2.1.1
Creation of EPWR
To create the power supply of the expansion subrack, the command is as follows CREATE EPWR:NAME=BSCE:0/epwr:0;
2.1.2
Creation of LICDS
Before LICD modules can be created, the redundant module has to exist in the database. This is also valid for the expansion boards: Before the creation of the first LICD card of the expansion subrack (LICD-2), the spare board (LICDS-1) has to be created. The corresponding command for this is: CREATE LICDS:NAME=BSCE:0/licds:0,LICDTYPE=LICDQTLP; The type of the LICDS module has to be specified; it can be either LICDDTLP or LICDQTLP.
A30808-X5226-C559-1-7618
7-66
Siemens
BSC Database
2.1.3
Creation of LICD
If the spare boards exist in the database, the LICD cards can be configured with the following command: CREATE LICD:NAME=BSCE:0/licd:1,LICDTYPE=LICDQTLP , ALARMT1=200,ALARMT2=10, ALARMT3=1,ALACOUNT=32; Again, the type of the LICD module has to be defined, either LICDDTLP or LICDQTLP.
2.1.4
Creation of PPLD
The PPLD modules are created with the following command: CREATE PPLD:NAME=BSCE:0/ppld:0;
2.1.5
Creation of PCU
The PCU is created with the following command: CREATE PCU:NAME=BSC:0/pcu:0, NMO=NMO_3, TNSVCBLK=3, NNSVCBLKR=3,NNSVCUBLR=3,TNSVCR=3,NNSVCRR=10,TNSVCTST=30, TNSVCPTST=3,NNSVCTSTR=10,NBVCBR=3,NBVCRR=10,T1=10,TF1=5, N3101=9,N3103=10,N3105=10,NRLCMAX=32,T3141=5,T3169=5,T3172=5, T3191=5,T3193=8, T3195=5,TEMPCH=90,THPROXT=500-50-500;
2.1.6
Creation of FRL
The Frame Relay link is created with the following command: CREATE FRL:NAME=BSC:0/frl:0,PCUN=0,GLK=PCMA:0,GTS=1,T391=10, N391=6,N392=3, N393=4,TCONG=10,TCONOFF=20; GLK indicates which PCMA or PCMG is used for carrying packet data traffic to SGSN. GTS gives the 64 kbit/s timeslots on GLK carrying packet data.
2.1.7
Creation of Permanent Virtual Connection
The PVC between BSC and SGSN is created with the following command: CREATE NSVC:NAME=BSC:0/nsvc=0,NSVCI=501,NSVLI=0-151; NSVCI is the Network Service Virtual Connection ID for the PVC. NSVLI is composed of the FRL and the (local) Data Link Connection ID.
1-8
A30808-X5226-C559-1-7618
BSC Database
Siemens
2.2
1. PCMB 2. LPDLM 3. BTSM 4. BTS 5. ADJC 6. LPDLR 7. TRX
Creation of Objects on the BTSE Side
On the BTSE side we have to create
8. FHSY (if necessary) 9. CHAN The chosen link configuration for a BTSE (star, multidrop, loop) influences the creation of the LI during the commissioning of the BTSE. In addition to this, the cabling of the BTSE has to be configured according this database.
2.2.1
Creation of PCMB
The PCMB line is configured with the following command: CREATE PCMB:NAME=BSC:0/pcmb:0,PCML=0-0, CRC=TRUE,CODE=HDB3,NUA=FALSE,BER=E10_3, BAF=0,LREDUNEQ=SIMPLEXA, L1CTRLTS1=31-3, LOWBER=0, REMAL=CCITT; The PCMB line is assigned to a specific port of a specific LICD board. This is indicated by the parameter PCML: PCML = LICD # - Port # Moreover, the terminal is specified by the parameter LREDUNEQ: LREDUNEQ = SIMPLEXA, SIMPLEXB or DUPLEXAB. L1CTRLTS1 (optional) = the dedicated layer 1 supervision timeslot for loop direction switch or the second PCMB connected to the same BTSE. LOWBER = lower bit error rate, for PCM24 only, REMAL = remote alarm, for PCM24 only.
A30808-X5226-C559-1-7618
9-66
Siemens
BSC Database
OMAL
PPLD
LICD/ LICDS
EPWR
SYNE
OPC
PCMB LPDLM BTSM BTS ADJC LPDLR TRX CREATE FHSY CHAN
PCMS LPDLS TRAU SYNE PCMA OMAL SS7L
DELETE
Fig. 4 Creation of PCMB
QTLP Port 0
2 Mbit/s (TRAU or BTSE) terminal A terminal B terminal A
Port 1
terminal B terminal A terminal B
Port 2
Port 3
terminal A terminal B 2 Mbit/s (TRAU or BTSE) terminal A terminal B
DTLP Port 0
Port 1
terminal A terminal B
Fig. 5 LICD ports
1-10
A30808-X5226-C559-1-7618
BSC Database
Siemens
2.2.2
Creation of LPDLM
The LAPD signaling for the operation and maintenance of a BTSE is defined with the following command: CREATE LPDLM:NAME=BSC:0/lpdlm:0,ABISCH=0-1,TEI=0,LPDLMSAT=FALSE; For every BTSE a LPDLM has to be defined. The number of the LPDLM link has to be the same as the number of the corresponding BTS Site Manager (BTSM). The signaling is put into a timeslot of the specific PCMB line. This is defined by the parameter ABISCH: ABISCHAN = PCMB # - Timeslot # or ABISCHAN = PCMB # - Timeslot # - Subslot # The Subslot # can only be chosen if the number of carriers in the BTSE is not more than two. The Terminal Endpoint Identifier is the basic criterion used to identify the network element during the alignment procedure. The same TEI can be used more than once within a BSC. Therefore, to identify the network element unambiguously, the (optional) parameter Sales Unique Name may be necessary (c. f. parameter SALUNAME in CREATE BTSM). The attribute LPDLM via satellite indicates whether the Abis is running via a satellite link.
2.2.3
Creation of BTSM
The BTS Site Manager (BTSM) is connected via a LPDLM signaling link. It is created with the following command: CREATE BTSM:/NAME=BSC:0/btsm:0,EXPSWV="01-01-08-00-13-00_98-11-06", SHLAPDIT=5,OMLAPDRT=5,EMT1=10,EMT2=0,SALUNAME="BSC0BTSE0", PCMCON0=PCMB_0-PORT_0,PCMCON1=PCMB_1-PORT_1; The expected SW version should be loaded into the BTSE. If it is not available there, the BTSE automatically requests a download of this SW from the BSC during alignment. The (optional) Sales Unique Name defines a unique symbolic name for the network element. It can be used together with the TEI to identify the network element for ID verification during alignment. The PCM connection 0 and 1 indicate which PCMB line carries the LPDLM (must always arrive on Bport 0) and which PCMB is the auxiliary line, respectively. Note that more than one LPDLM and BTSM can be created on the same PCMB line in case of multidrop chain or loop configuration.
A30808-X5226-C559-1-7618
11-66
Siemens
BSC Database
OMAL
PPLD
LICD/ LICDS
EPWR
SYNE
OPC
PCMB LPDLM BTSM BTS ADJC LPDLR TRX CREATE FHSY

Fig. 6 Creation of LPDLM and BTSM
CHAN
DELETE
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
1-12
A30808-X5226-C559-1-7618
BSC Database
Siemens
2.2.4
Creation of BTS
The creation of a cell is performed with the following command: CREATE BTS PKGBTSB:NAME=BSC:0/bts:10,BTSMN=0,BTSR=0,CELLGLID= "262"-"02"-13-1,BSIC=7-7,PLMNP=128,CELLRESH=2,MSTXPMAX=0, RXLEVAMI=6, RDLNKTO=4,RACHBT=102,RACHLAS=250,TCCCHLDI=100, PCCCHLDI=255, FACCHQ=7,CELLTYPE=STDCELL,SYSID=DCS1800, BCCHFREQ=559,CALL=579&589&599,CRESPARI=0,CRESOFF=1,TEMPOFF=1, PENTIME=0,CBQ=0,NMULBAC=0,CONCELL=FALSE,BTSHSCSD=FALSE, BTSSUPP145=FALSE; The meaning of the most important parameters is the following: Parameter BTSMN BTSR CELLGLID Meaning The number of the BTS Site Manager The relative number of the BTS in the BTSE The Cell Global Identity is a unique number identifying the cell. It consists of the Mobile Country Code (MCC), the Mobile Network Code (MNC), the Location Area Code (LAC) and the Cell Identity (CI). The Base Station Identity Code consists of the Network Color Code (NCC) and the Base station Color Code (BCC). The Absolute Radio Frequency Carrier Number (ARFCN) of the Broadcast Control Channel (BCCH) The Cell ALLocation is a list of up to 15 possible ARFCN, which can be used in the BTS.
BSIC BCCHFREQ CALL
Important parameters for BTS creation
When the BTS is created, along with the base package other parameter packages, which are listed below, are created automatically using default values. These values can be adjusted using a SET command. Note that up to three (BS6x) / six (BS24x) / 24 (picoBTS) BTS can be created for the same BTSM.
A30808-X5226-C559-1-7618
13-66
Siemens
BSC Database
OMAL
PPLD
LICD/ LICDS
EPWR
SYNE
OPC
DELETE
Fig. 7 Creation of BTS
Package BTSB Base package BTSI Interference package BTST Timer package HAND Handover package PWRC Power Control package BTSO Options package
Parameter packages for BTS
meaning General parameters Parameters for interference handling Parameters of timers Handover parameters Power Control parameters Parameters to enable/disable optional features
BTSC Common Control Channel package Attributes of control channels
1-14
A30808-X5226-C559-1-7618
BSC Database
Siemens
2.2.5
Creation of PTPPKF
Cells supporting GPRS are created with the following command: CREATE PTPPKF:NAME=BSC:0/ptppkf:0,PCUN=0,RACODE=100,RACOL=0, BSCDVMA=15,PKTNDEC=2,PKTNINC=2,PKTNMA=4,GRXLAMI=10, GMSTXPMAC=10,ABUTYP=ACBU8BIT,RAARET=TRUE,GPATH=PKAAP4, GTXINT=3,GS=0,GMANRETS=2-2-2-2,GMANPAL=3,GMANSAL=7-16, T3166_68=7,T3192=4,INISCH=CS2,NTWCOR=NC0,GTEMPOFF=1, GPENTIME=0,GRES0FF=0,GCELLRESH=2,C31H=TRUE,C32QUAL=TRUE, TRESEL=0,RARESH=2,GHCSTH=10,GHCSPC=3,ALPHA=3,TAVGW=15, TAVGT=5,PRPBCCH=0,PCMECH=MEABCCH,NAVGI=10,BSPBBLK=1, BPAGCHR=0,BPRACHR=0,DRXTMA=0,CACKTYP=1; PCUN specifies which PCU is responsible for the GPRS point-to-point packet function. The GPRS routing area RA usually is smaller than the GSM location area. GMANPAL specifies the maximum number of PDTCH allocated in this cell.
2.2.6
Creation of ADJC
Adjacent cells define the topology of the network, i.e. between which cells a handover is possible. Note: No handover is foreseen for GPRS. CREATE ADJC:NAME=BSC:0/bts:10/adjc:1,BSIC=7-7,CELLGLID="262"-"02"-133,RXLEVMIN=8, MSTXPMAXCL=2,HOM=28,BCCHFREQ=611,HOMSOFF=0, HOMDTIME=0, HOMDOFF=0,MICROCELL=FALSE,FHORLMO=6,TIMERFHO=12, PLNC=0, PPLNC=0,LEVONC=0,TINHBAKHO=30,TINHFAIHO=5,GSUP=TRUE,...; The numbering of the cells is ADJC - own cell# - relative number of neighboring cell (0..31) The most important informations about the neighboring cells are: BSIC, CELLGLID, BCCHFREQ and GSUP (GPRS supported).
A30808-X5226-C559-1-7618
15-66
Siemens
BSC Database
OMAL
PPLD
LICD/ LICDS
EPWR
SYNE
OPC
DELETE
Fig. 8 Creation of ADJC
BTS-10
ADJC-11-1 ADJC-12-6 ADJC-13-7
BTS-11
BTS-12
BTS-13
Fig. 9 Adjacent cells
1-16
A30808-X5226-C559-1-7618
BSC Database
Siemens
2.2.7
Creation of LPDLR
The creation of the LAPD signaling corresponding to a carrier (TRX) is performed with the following command: CREATE LPDLR:NAME=BSC:0/bts:10/lpdlr:0,ABISCH=0-1; The association to the TRX is given by LPDLR - BTS # - relative number of TRX The parameter ABISCH specifies the PCMB line and the timeslot which carries the signaling: ABISCH = PCMB # - Timeslot # - Subslot # As for LPDLM, a subslot can be chosen only if the number of carriers in the BTSE is two or less, otherwise this parameter has to be skipped. The LPDLR signaling is carried in the same timeslot (and subslot, if defined) as the LPDLM. Therefore the parameters for LPDLR and LPDLM must be identical.
2.2.8
Creation of TRX
The creation of a TRX is only possible if the corresponding LPDLR is already defined: CREATE TRX:NAME=BSC:0/bts:10/trx:0,TRXFREQ=559,PWRRED=6, RADIOMR=OFF,RADIOMG=254, MOEC=TRUE,TRXAREA=NONE; The TRX is specified by: TRX-BTS # - relative number of TRX The frequency of the TRX has to be defined according to the list of possible frequencies in the cell, i.e. it has to be the BCCH TRX frequency or a TRX frequency defined in the CALL parameter:
A30808-X5226-C559-1-7618
17-66
Siemens
BSC Database
OMAL
PPLD
LICD/ LICDS
EPWR
SYNE
OPC
DELETE
Fig. 10 Creation of LPDLR and TRX
. . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
A30808-X5226-C559-1-7618
BSC Database
Siemens
2.2.9
Creation of FHSY
The creation of a frequency hopping systems is performed with the following command: CREATE FHSY:NAME=BSC:0/ - bts # /- fhsy #, . . . Up to 10 different frequency hopping systems (FHSY) can be created. This is indicated by the FHSY # parameter, which has a value range from 0 to 10. The default value 0 means no hopping. A hopping sequence is defined by an algorithm which needs a start value in the range between 0 and 63, and the list of frequencies to be included in the hopping sequence. For every traffic channel can be defined, which of the existing FHSY it shall use, and at which step in the hopping sequence it should start hopping (MAIO Mobile Allocation Index Offset).
A30808-X5226-C559-1-7618
19-66
Siemens
BSC Database
OMAL
PPLD
LICD/ LICDS
EPWR
SYNE
OPC
DELETE
Fig. 11 Creation of FHSY
TRX-0
TRX-1
TRX-2
TRX-3
Fig. 12 Frequency hopping
1-20
A30808-X5226-C559-1-7618
BSC Database
Siemens
2.2.10
Creation of CHAN
The creation of the radio channels can be performed only when all other objects on the BTSE side have been defined. On the air interface, we need signaling channels and traffic channels. The command to create e.g. a broadcast control channel has the following syntax: CREATE CHAN:NAME=BSC:0/bts:10/trx:0/chan:0,CHTYPE=MAINBCCH, FHSYID=0,MAIO=0,TSC=7,EXTMODE=FALSE; The parameters specify CHAN - BTS # - TRX # - timeslot # CHTYPE = type of the channel For a broadcast control channel no frequency hopping is allowed. Therefore the frequency hopping system must be 0. Traffic channels have to be defined according to the following syntax: CREATE CHAN:NAME=BSC:0/bts:10/trx:0/chan:1,CHTYPE=TCHFULL, TERTCH=0-2-2,FHSYID=0,MAIO=0,TSC=7,EXTMODE=FALSE; Again, the first parameter specifies CHAN - BTS # - TRX # - timeslot # CHTYPE = type of the channel TERTCH = PCMB # - timeslot # - subslot # The TERTCH parameter specifies the assignment between a traffic channel on the Abis interface (terrestrial channel) and a traffic channel on the air interface. It allows to enter values for PCMB #, timeslot # and subslot #. GPRS physical channels may only be located on full rate time slots located on BCCH TRX. GPRS channels are dynamically shared with circuit switched channels there is no TCH reservation for GPRS (exception: channels with PCCCH). A cell allocates one or more PDCH ("capacity on demand") to support GPRS. These channels are taken from the common channel pool:
l l
A channel allocated to GPRS is released to circuit switched services when required (speech always has highest priority). The GPRS channel carries PTCH and (optionally) PCCCH or PCCCH/PBCCH.
The parameter specifying the channel combination is GCCH = NOGPRSCCH, GPRSPBCCH, GPRSPCCCH.
A30808-X5226-C559-1-7618
21-66
Siemens
BSC Database
OMAL
PPLD
LICD/ LICDS
EPWR
SYNE
OPC

Fig. 13 Creation of CHAN
CHAN
DELETE
Channel type MAINBCCH MBCCHC SDCCH SCBCH BCBCH CCCH TCHFULL TCHF&HLF
Description Main broadcast control channel, does not include a SDCCH Main broadcast control channel combined with a SDCCH Contains SDCCH and SACCH SDCCH, also featuring SMS cell broadcast service Main broadcast channel including a SDCCH and featuring SMS cell broadcast service Control channels CCCH and BCCH Traffic channels full rate service including SACCH and FACCH Traffic channels for both full rate and half rate service including SACCH and FACCH
Possible channel configurations
1-22
A30808-X5226-C559-1-7618
BSC Database
Siemens
2.3
1. PCMS 2. LPDLS 3. TRAU 4. PCMA 5. OPC 6. SS7L 7. OMAL 8. SYNC
Creation of Objects on the TRAU Side
On the TRAU side we have to create
2.3.1
Creation of PCMS
The PCMS line is configured with the following command: CREATE PCMS:NAME=BSC:0/pcms:0,PCML=1-1,CRC=TRUE,CODE=HDB3, NUA=FALSE,BER=E10_3,BAF=0,LREDUNEQ=SIMPLEXA,LOWBER=E10_3, REMAL=CCITT,WMOD=DOUBLE_TRUNK ; The PCMS line is assigned to a specific port of a specific LICD board. This is indicated by the parameter PCML: PCML = LICD # - Port # Moreover, the terminal is specified by the parameter LREDUNEQ: LREDUNEQ = SIMPLEXA or SIMPLEXB or DUPLEX. LOWBER = low bit error rate, for PCM24 only. REMAL = remote alarm, for PCM24 only. The attribute working mode indicates whether the PCMS works in single trunk ("selection") mode or in double trunk ("transparent") mode. This parameter can only be used if the parameter ASUBENCAP (Asub enhanced capacity allowed) in PKGBSCB has been set accordingly.
A30808-X5226-C559-1-7618
23-66
Siemens
BSC Database
OMAL
PPLD
LICD/ LICDS
EPWR
SYNE
OPC
DELETE
Fig. 14 Creation of PCMS
QTLP Port 0
2 Mbit/s (TRAU or BTSE)
terminal A terminal B terminal A
Port 1
terminal B terminal A terminal B terminal A terminal B 2 Mbit/s (TRAU or BTSE)
Port 2
Port 3
DTLP Port 0
terminal A terminal B
terminal A Port 1 terminal B
Fig. 15 LICD ports
1-24
A30808-X5226-C559-1-7618
BSC Database
Siemens
2.3.2
Creation of LPDLS
The LAPD signaling for the TRAU is defined with CREATE LPDLS:NAME=BSC:0/lpdls:0,ASUBCH=0-31,TEI=0; For every TRAU a LPDLS has to be defined. The signaling is put into a timeslot of a specific PCMS line. The definition of this assignment is ASUBCH= PCMS # - timeslot # - subslot #. Since it is not possible to define 16 kbit/s signaling for LPDLS, in this statement no subslot # can be used. The terminal endpoint identifier is the basic criterion to identify a network element during alignment. As the same TEI can be used more than once within a BSC, the (optional) parameter SALUNAME (c. f. CREATE TRAU) may be necessary to uniquely identify a network element.
2.3.3
Creation of TRAU
The TRAU is created with the following command: CREATE TRAU:NAME=BSC:0/trau:0,PCMSN=0,TSYNC=1000,EXPSWV="02-0401--02-12-01_98-10-21", ALLCRIT=NOT_COMPATIBLE_WITH_CROSSCONNECT, SALUNAME="BSC0TRAU0" ; The parameters define the assignment between the TRAU and the PCM line used: PCMSN = PCMS # ALLCRIT= NOT_COMPATIBLE_WITH_CROSSCONNECT: former TRAU matrix type 1, COMPATIBLE_WITH_CROSS_CONNECT: former TRAU matrix type 2. The (optional) Sales Unique Name specifies a unique symbolic name for every network element. It can be used in addition to the TEI for the ID verification during alignment.
A30808-X5226-C559-1-7618
25-66
Siemens
BSC Database
OMAL
PPLD
LICD/ LICDS
EPWR
SYNE
OPC

Fig. 16 Creation of LPDLS and TRAU
CHAN
DELETE
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
1-26
A30808-X5226-C559-1-7618
BSC Database
Siemens
2.3.4
Creation of PCMA
Every TRAU can be connected to the MSC by up to 4 PCM lines. With a maximum of 20 TRAU the maximum number of PCMA is 80. They are defined in the BSC database by the command: CREATE PCMA:NAME=BSC:0/pcma:0,PCMT=0-0,CRC=TRUE,CODE=HDB3, NUA=FALSE,BER=E10_3, BAF=0,HCICN=0;LOWBER=E10_3,REMAL=0, DEFPOOLTYP=NOT_DEFINED; The syntax is the following: PCMA - PCMA # PCMT = TRAU # - relative number of PCMA line for this TRAU. DEFPOOLTYP = the default type of pool assigned to every TSLA of the given PCMA. The different pool types are predefined and represent a certain combination of supported coding types for speech and data (see also parameter ENPOOL in PKGBSCB).
Pool Number 1 Number 2 Number 3 Number 4 Number 5 Number 6 ...... Number 21
Supported Channels and Coding Types FR speech version 1, FR data (12, 6, 3.6 kbit/s) HR speech version 1, HR data (6, 3.6 kbit/s) FR speech version 1, FR data (12, 6, 3.6 kbit/s) HR speech, HR data (6, 3.6 kbit/s) FR speech version 2, FR data (12, 6, 3.6 kbit/s) (FR speech version 1, FR speech version 2, FR data (12, 6, 3.6 kbit/s) FR speech version 2, FR data (12, 6, 3.6 kbit/s) HR speech version 1, HR data (6, 3.6 kbit/s) ...... FR speech version 1 and 2. FR data (14.5, 12, 6, 3.6 kbit/s) HR speech version 1, HR data (6, 3.6 kbit/s) HSCSD max 2 x FR data (14.5, 12.6 kbit/s)
Number 22
FR speech version 1 and 2, FR data (14.5, 12, 6, 3.6 kbit/s) HR speech version 1, HR data (6, 3.6 kbit/s) HSCSD max 4 x FR data (14.5, 12.6 kbit/s)
A30808-X5226-C559-1-7618
27-66
Siemens
BSC Database
OMAL
PPLD
LICD/ LICDS
EPWR
SYNE
OPC
DELETE
Fig. 17 Creation of PCMA
. . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
A30808-X5226-C559-1-7618
BSC Database
Siemens
2.3.5
Creation of OPC
The OPC describes the addresses of both BSC and MSC for the exchange of CCSS7 signaling information. The corresponding command is: CREATE OPC PKGOPCP:NAME=BSC:0/opc:0,OPC=219-48,SPC=48-144, NTWIND=2; The meaning of the parameters is the following: OPC = Origination Point Code, address of the BSC in structured format SPC = Signaling Point Code, address of the MSC in structured format The value for OPC and SPC is entered as "NetworkClusterMember-NetworkClusterNetworkIdentifier". For ITU the conversion from decimal to structured format is done in the following way: Convert decimal value to hex, the 2 least significant digits (converted to decimal) give the NetworkClusterMember, the 2 most significant digits (converted to decimal) give the NetworkCluster. The values of the Origination and Signaling Point Code have to be defined consistent with the values of the MSC database. NETWIND = NETWork INDicator, decimal GSM definition INAT 0 INAT 1 NAT 0 NAT 1
Definition of the network indicator
NTWIND 0 1 2 3
A30808-X5226-C559-1-7618
29-66
Siemens
BSC Database
OMAL
PPLD
LICD/ LICDS
EPWR
SYNE
OPC
DELETE
Fig. 18 Creation of OPC
Package OPCP MTL2 MTL3 SCCP
Meaning OPC, SPC and network indicator timers of MTP level 2 protocol timers of MTP level 3 protocol timers of SCCP protocol
Parameter packages for OPC
1-30
A30808-X5226-C559-1-7618
BSC Database
Siemens
2.3.6
Creation of SS7L
Only after the definition of the OPC it is possible to define CCSS7 signaling links between BSC and MSC. The syntax is the following: CREATE SS7L:NAME=BSC:0/ss7l:0,LNKA=0-0,TSLA=0-16,SLC=0; The meaning of the parameters is: LNKA = PPCC # - port# TSLA = PCMA # - timeslot # Note that every PPCC can handle up to 4 CCSS7 signaling links. The port # indicates the relative number of these signaling links, 0 to 3. Thus, in total up to 8 CCSS7 links can be defined.
A30808-X5226-C559-1-7618
31-66
Siemens
BSC Database
OMAL
PPLD
LICD/ LICDS
EPWR
SYNE
OPC
DELETE
Fig. 19 Creation of SS7L
PPCC
Port 0
Port 1
Port 2
Port 3
Fig. 20 PPCC ports
1-32
A30808-X5226-C559-1-7618
BSC Database
Siemens
2.3.7
Creation of OMAL
The signaling link between BSC and OMC, called Operation and Maintenance Access Link (OMAL), can be defined choosing one of two connection types: A interface connection or dedicated line connection. Depending on the configuration, a X25 link has to be defined first as X25A or X25D, e.g. CREATE X25D:NAME=BSC:0/x25d:0,CLOCK=EXTERNAL, BAUDRATE=BAUD_64000,DTEDCE=DTE; In our example database, it is created as an A interface connection. It can be defined only when the A interface has been defined before: CREATE X25A:NAME=BSC:0/x25a:0,ACHAN=0-30; The ACHAN parameter defines PCMA# - Timeslot#. The OMAL link itself is defined with CREATE OMAL:NAME=BSC:0/omal:0,LINKTYPE=X25D , X121ADDR="22510111111112",REGION=1, DISTRICT=0,BSSNAME=0; As parameter, the Linktype X25D or X25A has to be specified.
A30808-X5226-C559-1-7618
33-66
Siemens
BSC Database
OMAL
PPLD
LICD/ LICDS
EPWR
SYNE
OPC
DELETE
Fig. 21 Creation of OMAL
. . . . . . . . . . . . . . . . . . . . . . . . . . 1-34
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
A30808-X5226-C559-1-7618
BSC Database
Siemens
2.3.8
Creation of SYNC and SYNE
The source for the synchronization signal is defined with the following command: CREATE SYNC:NAME=BSC:0/sync:0,PCMSOBJ=0; The parameter specifies, from which PCMS line the synchronization signal should be derived: PCMSOBJ = PCMS # Up to 10 SYNC can be defined. In case of external synchronization sources (SYNE), their priority is higher than the priority of the SYNC. Up to two external sources can be defined. The command syntax to create a SYNE is CREATE SYNE:NAME=BSC:0/syne:#
A30808-X5226-C559-1-7618
35-66
Siemens
BSC Database
OMAL
PPLD
LICD/ LICDS
EPWR
SYNE
OPC
DELETE
Fig. 22 Creation of SYNC and SYNE
. . . . . . . . . . . . . . . . . . . . . . . . . . 1-36
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
A30808-X5226-C559-1-7618
BSC Database
Siemens
2.4
Summary: GPRS Objects
The following commands are used for establishing GPRS: Command CREATE PCU: NAME=BSC:0/pcu:0, ...,TEMPCH=90, ...; CREATE PTPPKF : NAME=BSC:0/ptppkf:0, PCUN=0,..., GRXLAMI=63, GMSTXPMAC=31,..., GMANPAL=7, GMANMSAL=7-16,..., INICSCH=CS2,...; CREATE FRL : NAME=BSC:0/frl:0, PCUN=0, GLK=PCMA:0, GTS=1,...; CREATE PCMG: NAME=BSC:0/pcmg:0, PCML=1-1-TRUNKA,...; CREATE PCMA: NAME=BSC:0/pcma:0, PCMT=0-0,CRC=TRUE,...; CREATE NSVC: NAME=BSC:0/nsvc:0, NSVCI=501, NSVLI=0-151; NSVCI (virtual connection ID) FRLN-DLCIN (link ID) TRAUNumber - PCMALinkNumber LICDNumber - CircuitNumber - Trunk (A or B) PCUNumber GPRSLink (PCMA-x or PCMG-x) GPRSTimeSlot (max 16) PCUNumber GPRSLevelAccessMin GPRSMSTXPowerMaxChannel MaxNumberPDTCHAllocated (per cell) MaxMSUplink-Downlink (per PDCH) InitialCodingScheme TimerEmptyChannel (release of PDTCH for no activities) Parameters
A30808-X5226-C559-1-7618
37-66
Siemens
BSC Database
Command CREATE ADJC: NAME=BTS:0/ADJ:0, ...,GSUP=FALSE,...; CREATE CHAN : NAME=BTS:0/TRX:0/CHAN:0, ..., GCCH=GPRSPCCCH; CREATE SCAN BTSGPRSMEAS NAME=SCAN:0, SCANNAME="tobeornottobe1", ACTMEASLS=LST_ELEM, LSTGPRSMEASTYPE= ... , ACTOBJLS=LST_ELEM; BTSLST=1&3&5, GRANP=MINUTES_15, REPMETHOH=BYFILE, START=1-JAN-2001, STOP=1-JAN-2002, PERTYPE=DAILY, ACTPER=2-4-1440;
Parameters
GPRSSupported
GPRSControlChannel (supported or not)
NAVPDCH=min, max and mean no of PDCH, AALPDCT=time with all PDCH allocated, TASGPRS=total no of GPRS attempts, TASUGPRS=total no of successful attempts, NRETRLCB=retransm. of single RLC blocks, NATGPPAG=attempts of GPRS paging, NASUGPPAG=successful GPRS pagings, MUTHRF=mean data throughput in one cell, MSTHRF= mean signal. throughput (one cell), MUTHBS=mean throughput on Gb (one cell), MSTHBS=mean signaling throughput on Gb, BSCPRCLD=MPCC, TDPC and PCU load, NATPRRE=attempted packet reass. per cell, NSUPRRE=successful packet reassignments, MEALPDCO=mean no. of PDCH per connect, NPMSDISQ=no of packet request discarded.
1-38
A30808-X5226-C559-1-7618
BSC Database
Siemens
Database Example
SET BSC PKGBSCC:NAME=BSC:0,MEDAFUST=1-0,MEDAFUPE=UPPE_2H, MASCLOGFS=3, IMSIFSIZ=20,CFS=1; SET BSC PKGBSCT:NAME=BSC:0,BSCT1=HLFSEC-12,BSCT3=HLFSEC-50, BSCT4=HLFSEC-60,BSCT7=HLFSEC-4,BSCT8=HLFSEC-10, BSCT10=HLFSEC-10,BSCT11=HLFSEC-16,BSCT13=HLFSEC-50, BSCT17=HLFSEC-20, BSCT18=HLFSEC-60,BSCT19=HLFSEC-12, BSCT20=HLFSEC-12, BSCTQHO=HLFSEC-120,TCBCSI=0; SET BSC PKGBSCB:NAME=BSC:0,NETWTYPE=GSMDCS,T3122=5, ERRACT=NOFILTER-NOFILTER-FERMAINT-NOFILTER-NOFILTER, ENCALSUP=GSMV1,MAXNCELL=6, MSCV=PHASE2,OVLSTTHR=9500, OVLENTHR=8500,BSCOVLH=TRUE,BTSOVLH=TRUE,MSCOVLH=TRUE, EISDCCHHO=ENABLE,ENFORCHO=ENABLE,NTWCARD=NTWSN16, AMONTH=ENABLE-30-ENABLE-60-ENABLE-90, ASMONTH=ENABLE-30ENABLE-60-ENABLE-90, SPENLAW=A_LAW,PCMTYPE=PCM30, EFRSUPP=FALSE,CICFM=GSM,MSCPOOL=FALSE,HRSPEECH=TRUE, SPEED145=FALSE,ENHSCSD=FALSE,ENFOIAHO=FALSE,HOSYNC=NONSYNC, ASUBENCAP=FALSE,ASUBISAT=FALSE,AISAT=FALSE, EPREHSCSD=DISABLED,MAFIRACHO=2,MADGRLV=2,NOTFACCH=ALWAYS; SET BSC PKGBSCS:NAME=BSC:0,ALRMSEVBTS=CRITICAL, ALRMSEVBTSM=MAJOR,ALRMSEVCBCL=MAJOR,ALRMSEVLPDLM=MAJOR, ALRMSEVLPDLR=MAJOR,ALRMSEVLPDLS=MAJOR,ALRMSEVOMAL=MAJOR, ALRMSEVPCMA=MAJOR,ALRMSEVPCMB=MAJOR,ALRMSEVPCMS=MAJOR, ALRMSEVTRAU=CRITICAL,ALRMSEVTRX=MAJOR,ALRMSEVPCU=CRITICAL, ALRMSEVFRL=MINOR,ALRMSEVNSVC=MINOR,ALRMSEVPTPPKF=MAJOR, ALRMSEVPCMG=MAJOR; SET BSCE PKGBSCES:NAME=BSCE:0,ALRMSEVDISK=MAJOR, ALRMSEVDK40=MAJOR,ALRMSEVEPWR=MAJOR,ALRMSEVIXLT=MAJOR, ALRMSEVLICD=MINOR,ALRMSEVLICDS=MINOR,ALRMSEVMEMT=MAJOR, ALRMSEVMPCC=MAJOR,ALRMSEVNTW=MAJOR,ALRMSEVPPCC=MAJOR, ALRMSEVPPLD=MINOR,ALRMSEVPWRD=MAJOR,ALRMSEVSYNC=MAJOR, ALRMSEVSYNE=MAJOR,ALRMSEVTDPC=MAJOR,ALRMSEVX25A=MAJOR, ALRMSEVX25D=MAJOR,ALRMSEVPPCU=MINOR; CREATE EPWR:NAME=BSCE:0/epwr:0; CREATE EPWR:NAME=BSCE:0/epwr:1;
A30808-X5226-C559-1-7618 39-66
Siemens
BSC Database
CREATE LICDS:NAME=BSCE:0/licds:0,LICDTYP=LICDQTLP; CREATE LICDS:NAME=BSCE:0/licds:1,LICDTYP=LICDQTLP; CREATE LICD:NAME=BSCE:0/licd:0,LICDTYP=LICDQTLP,ALARMT1=200, ALARMT2=90,ALARMT3=1,ALACOUNT=32; CREATE LICD:NAME=BSCE:0/licd:1,LICDTYP=LICDQTLP,ALARMT1=200, ALARMT2=10,ALARMT3=1,ALACOUNT=32; CREATE LICD:NAME=BSCE:0/licd:2,LICDTYP=LICDQTLP,ALARMT1=200, ALARMT2=90,ALARMT3=1,ALACOUNT=32; CREATE PPLD:NAME=BSCE:0/ppld:0; CREATE PPLD:NAME=BSCE:0/ppld:1; CREATE PPLD:NAME=BSCE:0/ppld:2; CREATE PPLD:NAME=BSCE:0/ppld:3; CREATE PPLD:NAME=BSCE:0/ppld:4; CREATE PPLD:NAME=BSCE:0/ppld:5; CREATE PPLD:NAME=BSCE:0/ppld:6; CREATE PCU:NAME=BSC:0/pcu:0,NMO=NMO_3,NSEI=5,TNSVCBLK=10, NNSVCBLKR=3,NNSVCUBLR=3,TNSVCR=3,NNSVCRR=10,TNSVCTST=30, TNSVCPTST=3,NNSVCTSTR=10,NBVCBR=3,NBVCUR=3,NBVCRR=3,T1=10, T2=10,TF1=9,N3101=9,N3103=10,N3105=10,NRLCMAX=22,T3141=5,T3169=5, T3172=5,T3191=20,T3193=4,T3195=5,TEMPCH=100,THPROXT=500-50-550;
1-40
A30808-X5226-C559-1-7618
BSC Database
Siemens
CREATE PCU:NAME=BSC:0/pcu:1,NMO=NMO_3,NSEI=15,TNSVCBLK=3, NNSVCBLKR=3,NNSVCUBLR=3,TNSVCR=3,NNSVCRR=10,TNSVCTST=30, TNSVCPTST=3,NNSVCTSTR=10,NBVCBR=3,NBVCUR=3,NBVCRR=3,T1=10, T2=10,TF1=5,N3101=9,N3103=10,N3105=10,NRLCMAX=20,T3141=5,T3169=5, T3172=5,T3191=5,T3193=4,T3195=5,TEMPCH=100,THPROXT=500-50-550; CREATE PCMB:NAME=BSC:0/pcmb:0,PCML=0-0,CRC=TRUE,CODE=HDB3, NUA=FALSE, BER=E10_3,BAF=0,LREDUNEQ=SIMPLEXA, L1CTS=NOT_DEFINED-NOT_DEFINED, LOWBER=E10_6; CREATE PCMB:NAME=BSC:0/pcmb:5,PCML=2-0,CRC=TRUE,CODE=HDB3, NUA=FALSE,BER=E10_3,BAF=0,LREDUNEQ=SIMPLEXA, L1CTS=NOT_DEFINED-NOT_DEFINED, LOWBER=E10_6; CREATE LPDLM:NAME=BSC:0/lpdlm:0,ABISCH=0-1,TEI=0,LPDLMSAT=FALSE; CREATE LPDLM:NAME=BSC:0/lpdlm:5,ABISCH=5-2-1,TEI=1,LPDLMSAT=FALSE; CREATE BTSM:NAME=BSC:0/btsm:0,EXPSWV="01-01-12-00-22-00_00-07-20", SHLAPDIT=15,OMLAPDRT=30,EMT1=10,EMT2=0,SALUNAME="GPRSBTSM000", PCMCON0=PCMB_0-PORT_0, PCMCON1=NOT_DEFINED-NOT_DEFINED; CREATE BTSM:NAME=BSC:0/btsm:5,EXPSWV="01-04-12-01-79-01_00-07-25", SHLAPDIT=15,OMLAPDRT=30,EMT1=10,EMT2=0,SALUNAME="GPRSBTSM101", PCMCON0=PCMB_5-PORT_0, PCMCON1=NOT_DEFINED-NOT_DEFINED; CREATE PCMS:NAME=BSC:0/pcms:0,PCML=1-0,CRC=TRUE,CODE=HDB3, NUA=FALSE, BER=E10_3,BAF=0,LREDUNEQ=SIMPLEXA,LOWBER=E10_6, WMOD=DOUBLE_TRUNK; CREATE LPDLS:NAME=BSC:0/lpdls:0,ASUBCH=0-31,TEI=0; CREATE TRAU:NAME=BSC:0/trau:0,PCMSN=0,TSYNC=1000, EXPSWV="02-05-05-01-17-00_00-07-10", ALLCRIT=NOT_COMPATIBLE_WITH_CROSSCONNECT, SALUNAME="GPRSTRAU100",ETFO=FALSE;
A30808-X5226-C559-1-7618
41-66
Siemens
BSC Database
CREATE PCMA:NAME=BSC:0/pcma:0,PCMT=0-0,CRC=TRUE,CODE=HDB3, NUA=FALSE, BER=E10_3,BAF=0,HCICN=0,LOWBER=E10_6; CREATE PCMG:NAME=BSC:0/pcmg:0,PCML=1-1-TRUNKA,CRC=TRUE, CODE=HDB3, NUA=TRUE,BER=E10_3,BAF=0,LOWBER=E10_6; CREATE PCMG:NAME=BSC:0/pcmg:1,PCML=2-2-TRUNKA,CRC=TRUE, CODE=HDB3,NUA=FALSE,BER=E10_3,BAF=0,LOWBER=E10_3; CREATE FRL:NAME=BSC:0/frl:0,PCUN=0,GLK=PCMA:0,GTS=1,T391=10, N391=6,N392=3,N393=4,TCONG=10,TCONOFF=20,FRSTD=ITU; CREATE FRL:NAME=BSC:0/frl:1,PCUN=0,GLK=PCMG:0,GTS=1&2&3&4, T391=10,N391=6,N392=3,N393=4,TCONG=10,TCONOFF=20,FRSTD=ITU; CREATE NSVC:NAME=BSC:0/nsvc:0,NSVCI=501,NSVLI=0-151; CREATE NSVC:NAME=BSC:0/nsvc:1,NSVCI=502,NSVLI=1-152; CREATE BTS PKGBTSB:NAME=BSC:0/bts:0,BTSMN=0,BTSR=0, CELLGLID="555"-"10"-2100-100,BSIC=7-0,PLMNP=128,CELLRESH=2, MSTXPMAX=2, RXLEVAMI=15,RDLNKTO=7,RACHBT=127,RACHLAS=250, TCCCHLDI=100, PCCCHLDI=255,FACCHQ=7,CELLTYPE=STDCELL, SYSID=BB900,BCCHFREQ=3,CALL=63,CRESPARI=0,NMULBAC=0, CONCELL=FALSE,BTSHSCSD=FALSE,BTSSUP145=FALSE; CREATE BTS PKGBTSB:NAME=BSC:0/bts:1,BTSMN=0,BTSR=1, CELLGLID="555"-"10"-2100-101,BSIC=7-1,PLMNP=128,CELLRESH=2, MSTXPMAX=2,RXLEVAMI=15,RDLNKTO=7,RACHBT=127,RACHLAS=250, TCCCHLDI=100,PCCCHLDI=255,FACCHQ=7,CELLTYPE=STDCELL, SYSID=BB900,BCCHFREQ=21,CALL=81,CRESPARI=0,NMULBAC=0, CONCELL=FALSE, BTSHSCSD=FALSE,BTSSUP145=FALSE; CREATE BTS PKGBTSB:NAME=BSC:0/bts:2,BTSMN=0,BTSR=2, CELLGLID="555"-"10"-2100-102,BSIC=7-2,PLMNP=128,CELLRESH=2, MSTXPMAX=2, RXLEVAMI=10,RDLNKTO=5, RACHBT=127,RACHLAS=127, TCCCHLDI=64,PCCCHLDI=255,FACCHQ=7,CELLTYPE=STDCELL,SYSID=BB900, BCCHFREQ=39,CALL=99,CRESPARI=0,NMULBAC=0,CONCELL=FALSE, BTSHSCSD=FALSE,BTSSUP145=FALSE;
1-42
A30808-X5226-C559-1-7618
BSC Database
Siemens
CREATE BTS PKGBTSB:NAME=BSC:0/bts:5,BTSMN=5,BTSR=0, CELLGLID="555"-"10"-2101-105,BSIC=7-5,PLMNP=4,CELLRESH=2, MSTXPMAX=2,RXLEVAMI=10, RDLNKTO=7,RACHBT=127,RACHLAS=127, TCCCHLDI=100,PCCCHLDI=255,FACCHQ=5,CELLTYPE=STDCELL, SYSID=BB900,BCCHFREQ=6,CRESPARI=0,NMULBAC=0,CONCELL=FALSE, BTSHSCSD=FALSE,BTSSUP145=FALSE; SET BTS PKGBTSC:NAME=BSC:0/bts:0,MAXRETR=FOUR,NSLOTST=9,NY1=40, NBLKACGR=2,NFRAMEPG=2,MSTXPMAXCH=8,PWROFS=0, ASCISER=ASCIDISABLED,NOCHFBLK=1,NOCHBLKN=1; SET BTS PKGBTSC:NAME=BSC:0/bts:1,MAXRETR=FOUR,NSLOTST=9,NY1=40, NBLKACGR=2,NFRAMEPG=2,MSTXPMAXCH=8,PWROFS=0, ASCISER=ASCIDISABLED,NOCHFBLK=1,NOCHBLKN=1; SET BTS PKGBTSC:NAME=BSC:0/bts:2,MAXRETR=ONE,NSLOTST=9,NY1=40, NBLKACGR=2,NFRAMEPG=2,MSTXPMAXCH=2,PWROFS=0, ASCISER=ASCIDISABLED,NOCHFBLK=1,NOCHBLKN=1; SET BTS PKGBTSC:NAME=BSC:0/bts:5,MAXRETR=ONE,NSLOTST=9,NY1=20, NBLKACGR=0,NFRAMEPG=2,MSTXPMAXCH=8,PWROFS=0, ASCISER=ASCIDISABLED,NOCHFBLK=1,NOCHBLKN=1; SET BTS PKGBTSI:NAME=BSC:0/bts:0,INTCLASS=TRUE,INTAVEPR=31-10-2540-55, RFRSINDP=254; SET BTS PKGBTSI:NAME=BSC:0/bts:1,INTCLASS=TRUE,INTAVEPR=31-10-2540-55, RFRSINDP=254; SET BTS PKGBTSI:NAME=BSC:0/bts:2,INTCLASS=TRUE,INTAVEPR=31-10-2540-55, RFRSINDP=254; SET BTS PKGBTSI:NAME=BSC:0/bts:5,INTCLASS=FALSE,INTAVEPR=31-10-2540-55, RFRSINDP=60; SET BTS PKGBTST:NAME=BSC:0/bts:0,T200=44-31-41-90-90-90-135, T3101=HLFSEC-6,T3105=MS10-8,T3109=HLFSEC-24,T3111=HLFSEC-1, TSYNC=1000,TSYNCUL=400,TSYNCDL=400,TSYNCR=400,TTRAU=1000, ENANCD=DISABLED,NCDP1=H5-1,NCDP2=NOTUSED,TGRANT=4, NRPGRANT=20,VGRULF=2,TNOCH=16;
A30808-X5226-C559-1-7618
43-66
Siemens
BSC Database
SET BTS PKGBTST:NAME=BSC:0/bts:1,T200=44-31-41-90-90-90-135, T3101=HLFSEC-6,T3105=MS10-8,T3109=HLFSEC-24,T3111=HLFSEC-1, TSYNC=1000,TSYNCUL=400,TSYNCDL=400,TSYNCR=400,TTRAU=1000, ENANCD=DISABLED,NCDP1=H5-1,NCDP2=NOTUSED,TGRANT=4, NRPGRANT=20,VGRULF=2,TNOCH=16; SET BTS PKGBTST:NAME=BSC:0/bts:2,T200=44-31-41-90-90-90-135, T3101=HLFSEC-6,T3105=MS10-8,T3109=HLFSEC-24,T3111=HLFSEC-1, TSYNC=1000,TSYNCUL=400,TSYNCDL=400,TSYNCR=400,TTRAU=1000, ENANCD=DISABLED,NCDP1=H5-1,NCDP2=NOTUSED,TGRANT=4, NRPGRANT=20,VGRULF=2,TNOCH=16; SET BTS PKGBTST:NAME=BSC:0/bts:5,T200=44-31-41-90-90-90-135, T3101=HLFSEC-6,T3105=MS10-8,T3109=HLFSEC-24,T3111=HLFSEC-1, TSYNC=1000,TSYNCUL=400,TSYNCDL=400,TSYNCR=400,TTRAU=1000, ENANCD=DISABLED,NCDP1=H5-1, NCDP2=NOTUSED,TGRANT=4, NRPGRANT=20,VGRULF=2,TNOCH=16; SET BTS PKGBTSO:NAME=BSC:0/bts:0,CELLBARR=FALSE, CREALL=NOTALLOWED,NALLWACC=ALLALLOWED,EC=FALSE, DTXDLFR=FALSE,DTXDLHR=FALSE,DTXUL=SHNFSHNH,IMSIATDT=TRUE, T3212=0,PWROUT=M10DB-M6DB-DB5,DIRTCHASS=FALSE,BMONTH=ENABLE30-ENABLE-60-ENABLE-90, BSMONTH=ENABLE-30-ENABLE-60-ENABLE-90, EARCLM=FALSE,HOPMODE=BBHOP,EQ=DISABLED,QL=50,EPRE=DISABLED; SET BTS PKGBTSO:NAME=BSC:0/bts:1,CELLBARR=FALSE, CREALL=NOTALLOWED,NALLWACC=ALLALLOWED,EC=FALSE, DTXDLFR=FALSE,DTXDLHR=FALSE,DTXUL=SHNFSHNH,IMSIATDT=TRUE, T3212=0,PWROUT=M10DB-M6DB-DB5,DIRTCHASS=FALSE,BMONTH=ENABLE30-ENABLE-60-ENABLE-90,BSMONTH=ENABLE-30-ENABLE-60-ENABLE-90, EARCLM=FALSE,HOPMODE=BBHOP,EQ=DISABLED,QL=50,EPRE=DISABLED; SET BTS PKGBTSO:NAME=BSC:0/bts:2,CELLBARR=FALSE, CREALL=NOTALLOWED,NALLWACC=ALLALLOWED,EC=FALSE, DTXDLFR=FALSE,DTXDLHR=FALSE,DTXUL=SHNFSHNH,IMSIATDT=TRUE, T3212=0,PWROUT=M10DB-M6DB-DB5,DIRTCHASS=FALSE,BMONTH=ENABLE30-ENABLE-60-ENABLE-90,BSMONTH=ENABLE-30-ENABLE-60-ENABLE-90, EARCLM=FALSE,HOPMODE=BBHOP,EQ=DISABLED,QL=50,EPRE=DISABLED;
1-44
A30808-X5226-C559-1-7618
BSC Database
Siemens
SET BTS PKGBTSO:NAME=BSC:0/bts:5,CELLBARR=FALSE, CREALL=NOTALLOWED,NALLWACC=ALLALLOWED,EC=FALSE, DTXDLFR=FALSE,DTXDLHR=FALSE,DTXUL=SHNFSHNH,IMSIATDT=FALSE, T3212=0,PWROUT=M10DB-M6DB-DB5,DIRTCHASS=FALSE,BMONTH=ENABLE30-ENABLE-60-ENABLE-90,BSMONTH=ENABLE-30-ENABLE-60-ENABLE-90, EARCLM=TRUE,HOPMODE=BBHOP,EQ=DISABLED,QL=50,EPRE=DISABLED; SET HAND PKGHANDB:NAME=BSC:0/hand:0,INTERCH=TRUE,INTRACH=TRUE, IERCHOSDCCH=FALSE,IRACHOSDCCH=FALSE,LOTERCH=TRUE, LOTRACH=TRUE,RXQUALHO=TRUE,RXLEVHO=TRUE,DISTHO=TRUE, PBGTHO=TRUE,NCELL=6,THORQST=5,HOAVLEV=8-1,HOAVQUAL=8-2, HOAVDIST=8,HOAVPWRB=16,HOLTHLVDL=10,HOTDLINT=20,HOLTHLVUL=5, HOTULINT=20,HOLTHQUDL=6,HOLTHQUUL=6,HOTMSRM=35, DPBGTHO=FALSE,HIERC=FALSE,PL=7,HIERF=RANK0,CCDIST=FALSE, HORXLVDLI=26,HORXLVDLO=32,HOCCDIST=5,ININHO=FALSE, CCELL=NOT_DEFINED-NOT_DEFINED,HOTMSRME=100,HOMSTAM=32, HOMRGTA=4,NOBAKHO=FALSE,NOFREPHO=FALSE,MAXFAILHO=4, ELIMITCH=FALSE,MAIRACHO=10,TINOIERCHO=60; SET HAND PKGHANDB:NAME=BSC:0/hand:1,INTERCH=TRUE,INTRACH=TRUE, IERCHOSDCCH=FALSE,IRACHOSDCCH=FALSE,LOTERCH=TRUE, LOTRACH=TRUE,RXQUALHO=TRUE,RXLEVHO=TRUE,DISTHO=TRUE,PBGTHO =TRUE,NCELL=6,THORQST=5,HOAVLEV=8-1,HOAVQUAL=8-2,HOAVDIST=8, HOAVPWRB=16,HOLTHLVDL=10,HOTDLINT=20,HOLTHLVUL=5,HOTULINT=20, HOLTHQUDL=6,HOLTHQUUL=6,HOTMSRM=35,DPBGTHO=FALSE, HIERC=FALSE,PL=0,HIERF=RANK0,CCDIST=FALSE,HORXLVDLI=26, HORXLVDLO=32,HOCCDIST=5, ININHO=FALSE,CCELL=NOT_DEFINEDNOT_DEFINED,HOTMSRME=100,HOMSTAM=32,HOMRGTA=4, NOBAKHO=FALSE,NOFREPHO=FALSE,MAXFAILHO=4,ELIMITCH=FALSE, MAIRACHO=10,TINOIERCHO=60; SET HAND PKGHANDB:NAME=BSC:0/hand:2,INTERCH=TRUE,INTRACH=TRUE, IERCHOSDCCH=FALSE,IRACHOSDCCH=FALSE,LOTERCH=TRUE, LOTRACH=TRUE,RXQUALHO=TRUE,RXLEVHO=TRUE,DISTHO=TRUE, PBGTHO=TRUE,NCELL=6,THORQST=5,HOAVLEV=8-1,HOAVQUAL=8-2, HOAVDIST=8,HOAVPWRB=16,HOLTHLVDL=10,HOTDLINT=20,HOLTHLVUL=5, HOTULINT=20,HOLTHQUDL=6,HOLTHQUUL=6,HOTMSRM=35, DPBGTHO=FALSE,HIERC=FALSE,PL=0,HIERF=RANK0,CCDIST=FALSE, HORXLVDLI=26, HORXLVDLO=32,HOCCDIST=5,ININHO=FALSE, CCELL=NOT_DEFINED-NOT_DEFINED,HOTMSRME=100,HOMSTAM=32, HOMRGTA=4, NOBAKHO=FALSE, NOFREPHO=FALSE,MAXFAILHO=4, ELIMITCH=FALSE, MAIRACHO=10,TINOIERCHO=60;
A30808-X5226-C559-1-7618
45-66
Siemens
BSC Database
SET HAND PKGHANDB:NAME=BSC:0/hand:5,INTERCH=TRUE,INTRACH=TRUE, IERCHOSDCCH=FALSE,IRACHOSDCCH=FALSE,LOTERCH=TRUE, LOTRACH=TRUE,RXQUALHO=TRUE,RXLEVHO=TRUE,DISTHO=TRUE, PBGTHO=TRUE,NCELL=6,THORQST=5,HOAVLEV=8-1,HOAVQUAL=8-2, HOAVDIST=8,HOAVPWRB=16,HOLTHLVDL=10,HOTDLINT=20,HOLTHLVUL=5, HOTULINT=20,HOLTHQUDL=6,HOLTHQUUL=6,HOTMSRM=35, DPBGTHO=FALSE,HIERC=FALSE,PL=0,HIERF=RANK0,CCDIST=FALSE, HORXLVDLI=26,HORXLVDLO=32,HOCCDIST=5,ININHO=FALSE, CCELL=NOT_DEFINED-NOT_DEFINED,HOTMSRME=100,HOMSTAM=32, HOMRGTA=4,NOBAKHO=FALSE,NOFREPHO=FALSE,MAXFAILHO=4, ELIMITCH=FALSE,MAIRACHO=10,TINOIERCHO=60; SET HAND PKGHANDD:NAME=BSC:0/hand:0,ERUDGR=FALSE,TINHRUGR=10, TINHRDGR=5,RAVEW=8,RUGRUL=1,RUGRDL=1,RDGRUL=2,RDGRDL=2, RHOLTQUL=3,RHOLTQDL=3; SET HAND PKGHANDD:NAME=BSC:0/hand:1,ERUDGR=FALSE,TINHRUGR=10, TINHRDGR=5,RAVEW=8,RUGRUL=1,RUGRDL=1,RDGRUL=2,RDGRDL=2, RHOLTQUL=3,RHOLTQDL=3; SET HAND PKGHANDD:NAME=BSC:0/hand:2,ERUDGR=FALSE,TINHRUGR=10, TINHRDGR=5,RAVEW=8,RUGRUL=1,RUGRDL=1,RDGRUL=2,RDGRDL=2, RHOLTQUL=3,RHOLTQDL=3; SET HAND PKGHANDD:NAME=BSC:0/hand:5,ERUDGR=FALSE,TINHRUGR=10, TINHRDGR=5,RAVEW=8,RUGRUL=1,RUGRDL=1,RDGRUL=2,RDGRDL=2, RHOLTQUL=3,RHOLTQDL=3; SET PWRC:NAME=BSC:0/pwrc:0,EBSPWRC=FALSE,EMSPWRC=FALSE, PWRINCSS=DB4, PWREDSS=DB2,PWRCONF=2,PCONINT=2,PAVRLEV=4-1, PAVRQUAL=4-2,LOWTLEVD=25,UPTLEVD=35,LOWTLEVU=25,UPTLEVU=35, LOWTQUAD=5,UPTQUAD=4,LOWTQUAU=5,UPTQUAU=4,RDLNKTBS=16, EPWCRLFW=TRUE,PCRLFTH=8,EBSPWCR=FALSE; SET PWRC:NAME=BSC:0/pwrc:1,EBSPWRC=FALSE,EMSPWRC=FALSE, PWRINCSS=DB4, PWREDSS=DB2,PWRCONF=2,PCONINT=2,PAVRLEV=4-1, PAVRQUAL=4-2,LOWTLEVD=25,UPTLEVD=35,LOWTLEVU=25,UPTLEVU=35, LOWTQUAD=5,UPTQUAD=4,LOWTQUAU=5,UPTQUAU=4,RDLNKTBS=16, EPWCRLFW=TRUE,PCRLFTH=8,EBSPWCR=FALSE;
1-46
A30808-X5226-C559-1-7618
BSC Database
Siemens
SET PWRC:NAME=BSC:0/pwrc:2,EBSPWRC=FALSE,EMSPWRC=FALSE, PWRINCSS=DB4, PWREDSS=DB2,PWRCONF=2,PCONINT=2,PAVRLEV=4-1, PAVRQUAL=4-2,LOWTLEVD=25,UPTLEVD=35,LOWTLEVU=25,UPTLEVU=35, LOWTQUAD=5,UPTQUAD=4,LOWTQUAU=5,UPTQUAU=4,RDLNKTBS=16, EPWCRLFW=TRUE,PCRLFTH=8,EBSPWCR=FALSE; SET PWRC:NAME=BSC:0/pwrc:5,EBSPWRC=FALSE,EMSPWRC=FALSE, PWRINCSS=DB4, PWREDSS=DB2,PWRCONF=2,PCONINT=2,PAVRLEV=4-1, PAVRQUAL=4-2,LOWTLEVD=15,UPTLEVD=20,LOWTLEVU=10,UPTLEVU=15, LOWTQUAD=5,UPTQUAD=4,LOWTQUAU=5,UPTQUAU=4,RDLNKTBS=24, EPWCRLFW=FALSE,PCRLFTH=12,EBSPWCR=FALSE; CREATE PTPPKF:NAME=BSC:0/ptppkf:0,PCUN=0,RACODE=100,RACOL=0, BSCDVMA=15,PKTNDEC=2,PKTNINC=2,PKTNMA=4,GRXLAMI=10, GMSTXPMAC=10,ABUTYP=ACBU8BIT,RAARET=TRUE,GPATH=PKAAP4,GTXIN T=3,GS=0,GMANRETS=2-2-2-2,GMANPAL=3, GMANMSAL=7-16,T3166_68=7, T3192=4,INICSCH=CS2,NTWCOR=NC0,GTEMPOFF=1,GPENTIME=0, GRESOFF=0,GCELLRESH=2,C31H=TRUE,C32QUAL=TRUE,TRESEL=0, RARESH=2,GHCSTH=10,GHCSPC=3,ALPHA=3,TAVGW=15,TAVGT=5, PRPBCCH=0,PCMECH=MEABCCH,NAVGI=10,BSPBBLK=1,BPAGCHR=0, BPRACHR=0,DRXTMA=0,CACKTYP=1; CREATE PTPPKF:NAME=BSC:0/ptppkf:1,PCUN=0,RACODE=100,RACOL=0, BSCDVMA=15,PKTNDEC=2,PKTNINC=2,PKTNMA=4,GRXLAMI=6, GMSTXPMAC=15,ABUTYP=ACBU8BIT,RAARET=TRUE,GPATH=PKAAP4, GTXINT=3,GS=0,GMANRETS=2-2-2-2,GMANPAL=3,GMANMSAL=7-16, T3166_68=7,T3192=4,INICSCH=CS2,NTWCOR=NC0,GTEMPOFF=1, GPENTIME=0,GRESOFF=0,GCELLRESH=2,C31H=TRUE,C32QUAL=FALSE, TRESEL=0,RARESH=2,GHCSTH=10,GHCSPC=3,ALPHA=3,TAVGW=15, TAVGT=5,PRPBCCH=0,PCMECH=MEABCCH,NAVGI=10,BSPBBLK=1, BPAGCHR=0,BPRACHR=0,DRXTMA=0,CACKTYP=1; CREATE PTPPKF:NAME=BSC:0/ptppkf:2,PCUN=0,RACODE=100,RACOL=0, BSCDVMA=15,PKTNDEC=2,PKTNINC=2,PKTNMA=4,GRXLAMI=6, GMSTXPMAC=15,ABUTYP=ACBU8BIT,RAARET=TRUE,GPATH=PKAAP4, GTXINT=3,GS=0,GMANRETS=2-2-2-2,GMANPAL=2,GMANMSAL=1-1, T3166_68=7,T3192=4,INICSCH=CS1,NTWCOR=NC0,GTEMPOFF=1, GPENTIME=0,GRESOFF=0,GCELLRESH=2,C31H=TRUE,C32QUAL=FALSE, TRESEL=5,RARESH=2,GHCSTH=10,GHCSPC=3,ALPHA=3,TAVGW=15, TAVGT=5,PRPBCCH=0,PCMECH=MEABCCH,NAVGI=10,BSPBBLK=1, BPAGCHR=0,BPRACHR=0,DRXTMA=0,CACKTYP=1;
A30808-X5226-C559-1-7618
47-66
Siemens
BSC Database
CREATE PTPPKF:NAME=BSC:0/ptppkf:5,PCUN=0,RACODE=101,RACOL=0, BSCDVMA=15,PKTNDEC=2,PKTNINC=2,PKTNMA=4,GRXLAMI=6, GMSTXPMAC=15,ABUTYP=ACBU8BIT,RAARET=TRUE,GPATH=PKAAP4, GTXINT=3,GS=0,GMANRETS=2-2-2-2,GMANPAL=3,GMANMSAL=7-16, T3166_68=7,T3192=4,INICSCH=CS2,NTWCOR=NC0,GTEMPOFF=1, GPENTIME=2,GRESOFF=2,GCELLRESH=2,C31H=TRUE,C32QUAL=FALSE, TRESEL=0,RARESH=2,GHCSTH=10,GHCSPC=3,ALPHA=3,TAVGW=15, TAVGT=5,PRPBCCH=0,PCMECH=MEABCCH,NAVGI=10,BSPBBLK=1, BPAGCHR=0,BPRACHR=0,DRXTMA=0,CACKTYP=1; CREATE ADJC:NAME=BSC:0/bts:0/adjc:0,TGTCELLREF=INTERNAL, TGTCELL=BTS:1,RXLEVMIN=20,HOM=69,HOMSOFF=0,HOMDTIME=0, HOMDOFF=0,MICROCELL=FALSE,FHORLMO=6,TIMERFHO=12,PLNC=5, PPLNC=0,LEVONC=0,TINHBAKHO=30,TINHFAIHO=5,GSUP=FALSE; CREATE ADJC:NAME=BSC:0/bts:0/adjc:5,TGTCELLREF=INTERNAL, TGTCELL=BTS:5,RXLEVMIN=20,HOM=69,HOMSOFF=0,HOMDTIME=0, HOMDOFF=0,MICROCELL=FALSE,FHORLMO=6,TIMERFHO=12,PLNC=3, PPLNC=0,LEVONC=0,TINHBAKHO=30,TINHFAIHO=5,GSUP=FALSE; CREATE ADJC:NAME=BSC:0/bts:1/adjc:0,TGTCELLREF=INTERNAL, TGTCELL=BTS:0,RXLEVMIN=20,HOM=69,HOMSOFF=0,HOMDTIME=0, HOMDOFF=0,MICROCELL=FALSE,FHORLMO=6,TIMERFHO=12,PLNC=0, PPLNC=0,LEVONC=0,TINHBAKHO=30,TINHFAIHO=5,GSUP=FALSE; CREATE ADJC:NAME=BSC:0/bts:1/adjc:5,TGTCELLREF=INTERNAL, TGTCELL=BTS:5,RXLEVMIN=20,HOM=69,HOMSOFF=0,HOMDTIME=0, HOMDOFF=0,MICROCELL=FALSE,FHORLMO=6,TIMERFHO=12,PLNC=0, PPLNC=0,LEVONC=0,TINHBAKHO=30,TINHFAIHO=5,GSUP=FALSE; CREATE ADJC:NAME=BSC:0/bts:5/adjc:0,TGTCELLREF=INTERNAL, TGTCELL=BTS:0,RXLEVMIN=20,HOM=69,HOMSOFF=0,HOMDTIME=0, HOMDOFF=0,MICROCELL=FALSE,FHORLMO=6,TIMERFHO=12,PLNC=0, PPLNC=0,LEVONC=0,TINHBAKHO=30,TINHFAIHO=5,GSUP=FALSE; CREATE ADJC:NAME=BSC:0/bts:5/adjc:1,TGTCELLREF=INTERNAL, TGTCELL=BTS:1,RXLEVMIN=20,HOM=69,HOMSOFF=0,HOMDTIME=0, HOMDOFF=0,MICROCELL=FALSE,FHORLMO=6,TIMERFHO=12,PLNC=0, PPLNC=0,LEVONC=0,TINHBAKHO=30,TINHFAIHO=5,GSUP=FALSE; CREATE LPDLR:NAME=BSC:0/bts:0/lpdlr:0,ABISCH=0-1;
1-48
A30808-X5226-C559-1-7618
BSC Database
Siemens
CREATE LPDLR:NAME=BSC:0/bts:0/lpdlr:1,ABISCH=0-1; CREATE LPDLR:NAME=BSC:0/bts:1/lpdlr:0,ABISCH=0-1; CREATE LPDLR:NAME=BSC:0/bts:1/lpdlr:1,ABISCH=0-1; CREATE LPDLR:NAME=BSC:0/bts:2/lpdlr:0,ABISCH=0-1; CREATE LPDLR:NAME=BSC:0/bts:2/lpdlr:1,ABISCH=0-1; CREATE LPDLR:NAME=BSC:0/bts:5/lpdlr:0,ABISCH=5-2-1; CREATE TRX:NAME=BSC:0/bts:0/trx:0,TRXFREQ=3,PWRRED=6,RADIOMR=OFF, RADIOMG=254, MOEC=TRUE,TRXAREA=NONE; CREATE TRX:NAME=BSC:0/bts:0/trx:1,TRXFREQ=63,PWRRED=6, RADIOMR=OFF,RADIOMG=254,MOEC=TRUE,TRXAREA=NONE; CREATE TRX:NAME=BSC:0/bts:1/trx:0,TRXFREQ=21,PWRRED=6, RADIOMR=OFF,RADIOMG=254,MOEC=TRUE,TRXAREA=NONE; CREATE TRX:NAME=BSC:0/bts:1/trx:1,TRXFREQ=81,PWRRED=6, RADIOMR=OFF,RADIOMG=254,MOEC=TRUE,TRXAREA=NONE; CREATE TRX:NAME=BSC:0/bts:2/trx:0,TRXFREQ=39,PWRRED=6, RADIOMR=OFF,RADIOMG=254,MOEC=TRUE,TRXAREA=NONE; CREATE TRX:NAME=BSC:0/bts:2/trx:1,TRXFREQ=99,PWRRED=6, RADIOMR=OFF,RADIOMG=254,MOEC=TRUE,TRXAREA=NONE; CREATE TRX:NAME=BSC:0/bts:5/trx:0,TRXFREQ=6,PWRRED=6,RADIOMR=ON, RADIOMG=254,MOEC=TRUE,TRXAREA=NONE; CREATE FHSY:NAME=BSC:0/bts:1/fhsy:1,HSN=2,MOBALLOC=21&81;
A30808-X5226-C559-1-7618
49-66
Siemens
BSC Database
CREATE CHAN:NAME=BSC:0/bts:0/trx:0/chan:0,CHTYPE=MAINBCCH,FHSYID=0, MAIO=0,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:0/trx:0/chan:1,CHTYPE=SDCCH,FHSYID=0, MAIO=0,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:0/trx:0/chan:2,CHTYPE=TCHF_HLF, TERTCH=0-3-2,FHSYID=0,MAIO=0,TSC=0,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:0/trx:0/chan:3,CHTYPE=TCHF_HLF, TERTCH=0-3-3,FHSYID=0,MAIO=0,TSC=0,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:0/trx:0/chan:4,CHTYPE=TCHF_HLF, TERTCH=0-4-0, FHSYID=0,MAIO=0,TSC=0,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:0/trx:0/chan:5,CHTYPE=TCHF_HLF, TERTCH=0-4-1,FHSYID=0,MAIO=0,TSC=0,EXTMODE=FALSE, GCCH=NOGPRSCCH; CREATE CHAN:NAME=BSC:0/bts:0/trx:0/chan:6,CHTYPE=TCHF_HLF, TERTCH=0-4-2,FHSYID=0,MAIO=0,TSC=0,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:0/trx:0/chan:7,CHTYPE=TCHF_HLF, TERTCH=0-4-3,FHSYID=0,MAIO=0,TSC=0,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:1/trx:0/chan:0,CHTYPE=MAINBCCH,FHSYID=0, MAIO=0,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:1/trx:0/chan:1,CHTYPE=SDCCH,FHSYID=0, MAIO=0,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:1/trx:0/chan:2,CHTYPE=TCHF_HLF, TERTCH=0-13-2,FHSYID=0,MAIO=0,TSC=1,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:1/trx:0/chan:3,CHTYPE=TCHF_HLF, TERTCH=0-13-3,FHSYID=0,MAIO=0,TSC=1,EXTMODE=FALSE;
1-50
A30808-X5226-C559-1-7618
BSC Database
Siemens
CREATE CHAN:NAME=BSC:0/bts:1/trx:0/chan:4,CHTYPE=TCHF_HLF, TERTCH=0-14-0,FHSYID=0,MAIO=0,TSC=1,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:1/trx:0/chan:5,CHTYPE=TCHF_HLF, TERTCH=0-14-1,FHSYID=0,MAIO=0,TSC=1,EXTMODE=FALSE, GCCH=NOGPRSCCH; CREATE CHAN:NAME=BSC:0/bts:1/trx:0/chan:6,CHTYPE=TCHF_HLF, TERTCH=0-14-2,FHSYID=0,MAIO=0,TSC=1,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:1/trx:0/chan:7,CHTYPE=TCHF_HLF, TERTCH=0-14-3,FHSYID=0,MAIO=0,TSC=1,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:2/trx:0/chan:0,CHTYPE=MAINBCCH,FHSYID=0, MAIO=0,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:2/trx:0/chan:1,CHTYPE=SDCCH,FHSYID=0, MAIO=0,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:2/trx:0/chan:2,CHTYPE=TCHF_HLF, TERTCH=0-23-2,FHSYID=0,MAIO=0,TSC=2,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:2/trx:0/chan:3,CHTYPE=TCHF_HLF, TERTCH=0-23-3,FHSYID=0,MAIO=0,TSC=2,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:2/trx:0/chan:4,CHTYPE=TCHF_HLF, TERTCH=0-24-0,FHSYID=0,MAIO=0,TSC=2,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:2/trx:0/chan:5,CHTYPE=TCHF_HLF, TERTCH=0-24-1,FHSYID=0,MAIO=0,TSC=2,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:2/trx:0/chan:6,CHTYPE=TCHF_HLF, TERTCH=0-24-2,FHSYID=0,MAIO=0,TSC=2,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:2/trx:0/chan:7,CHTYPE=TCHF_HLF, TERTCH=0-24-3,FHSYID=0,MAIO=0,TSC=2,EXTMODE=FALSE;
A30808-X5226-C559-1-7618
51-66
Siemens
BSC Database
CREATE CHAN:NAME=BSC:0/bts:5/trx:0/chan:0,CHTYPE=MBCCHC,FHSYID=0, MAIO=0,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:5/trx:0/chan:1,CHTYPE=TCHF_HLF, TERTCH=5-10-1,FHSYID=0,MAIO=0,TSC=5,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:5/trx:0/chan:2,CHTYPE=TCHF_HLF, TERTCH=5-10-2,FHSYID=0,MAIO=0,TSC=5,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:5/trx:0/chan:3,CHTYPE=TCHF_HLF, TERTCH=5-10-3,FHSYID=0,MAIO=0,TSC=5,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:5/trx:0/chan:4,CHTYPE=TCHF_HLF, TERTCH=5-9-0,FHSYID=0,MAIO=0,TSC=5,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:5/trx:0/chan:5,CHTYPE=TCHF_HLF, TERTCH=5-9-1,FHSYID=0,MAIO=0,TSC=5,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:5/trx:0/chan:6,CHTYPE=TCHF_HLF, TERTCH=5-9-2,FHSYID=0,MAIO=0,TSC=5,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:5/trx:0/chan:7,CHTYPE=TCHF_HLF, TERTCH=5-9-3,FHSYID=0,MAIO=0,TSC=5,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:0/trx:1/chan:0,CHTYPE=TCHF_HLF, TERTCH=0-5-0,FHSYID=0,MAIO=0,TSC=0,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:0/trx:1/chan:1,CHTYPE=TCHF_HLF, TERTCH=0-5-1,FHSYID=0,MAIO=0,TSC=0,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:0/trx:1/chan:2,CHTYPE=TCHF_HLF, TERTCH=0-5-2,FHSYID=0,MAIO=0,TSC=0,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:0/trx:1/chan:3,CHTYPE=TCHF_HLF, TERTCH=0-5-3,FHSYID=0,MAIO=0,TSC=0,EXTMODE=FALSE;
1-52
A30808-X5226-C559-1-7618
BSC Database
Siemens
CREATE CHAN:NAME=BSC:0/bts:0/trx:1/chan:4,CHTYPE=TCHF_HLF, TERTCH=0-6-0,FHSYID=0,MAIO=0,TSC=0,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:0/trx:1/chan:5,CHTYPE=TCHF_HLF, TERTCH=0-6-1,FHSYID=0,MAIO=0,TSC=0,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:0/trx:1/chan:6,CHTYPE=TCHF_HLF, TERTCH=0-6-2,FHSYID=0,MAIO=0,TSC=0,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:0/trx:1/chan:7,CHTYPE=TCHF_HLF, TERTCH=0-6-3,FHSYID=0,MAIO=0,TSC=0,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:1/trx:1/chan:0,CHTYPE=TCHF_HLF, TERTCH=0-15-0,FHSYID=0,MAIO=0,TSC=1,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:1/trx:1/chan:1,CHTYPE=TCHF_HLF, TERTCH=0-15-1,FHSYID=0,MAIO=0,TSC=1,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:1/trx:1/chan:2,CHTYPE=TCHF_HLF, TERTCH=0-15-2,FHSYID=0,MAIO=0,TSC=1,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:1/trx:1/chan:3,CHTYPE=TCHF_HLF, TERTCH=0-15-3,FHSYID=0,MAIO=0,TSC=1,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:1/trx:1/chan:4,CHTYPE=TCHF_HLF, TERTCH=0-16-0,FHSYID=0,MAIO=0,TSC=1,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:1/trx:1/chan:5,CHTYPE=TCHF_HLF, TERTCH=0-16-1,FHSYID=0,MAIO=0,TSC=1,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:1/trx:1/chan:6,CHTYPE=TCHF_HLF, TERTCH=0-16-2,FHSYID=0,MAIO=0,TSC=1,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:1/trx:1/chan:7,CHTYPE=TCHF_HLF, TERTCH=0-16-3,FHSYID=0,MAIO=0,TSC=1,EXTMODE=FALSE;
A30808-X5226-C559-1-7618
53-66
Siemens
BSC Database
CREATE CHAN:NAME=BSC:0/bts:2/trx:1/chan:0,CHTYPE=TCHF_HLF, TERTCH=0-25-0,FHSYID=0,MAIO=0,TSC=2,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:2/trx:1/chan:1,CHTYPE=TCHF_HLF, TERTCH=0-25-1,FHSYID=0,MAIO=0,TSC=2,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:2/trx:1/chan:2,CHTYPE=TCHF_HLF, TERTCH=0-25-2,FHSYID=0,MAIO=0,TSC=2,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:2/trx:1/chan:3,CHTYPE=TCHF_HLF, TERTCH=0-25-3,FHSYID=0,MAIO=0,TSC=2,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:2/trx:1/chan:4,CHTYPE=TCHF_HLF, TERTCH=0-26-0,FHSYID=0,MAIO=0,TSC=2,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:2/trx:1/chan:5,CHTYPE=TCHF_HLF, TERTCH=0-26-1,FHSYID=0,MAIO=0,TSC=2,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:2/trx:1/chan:6,CHTYPE=TCHF_HLF, TERTCH=0-26-2,FHSYID=0,MAIO=0,TSC=2,EXTMODE=FALSE; CREATE CHAN:NAME=BSC:0/bts:2/trx:1/chan:7,CHTYPE=TCHF_HLF, TERTCH=0-26-3,FHSYID=0,MAIO=0,TSC=2,EXTMODE=FALSE; SET HAND PKGHANDB:NAME=BSC:0/hand:0,EXTCHO=FALSE; SET HAND PKGHANDB:NAME=BSC:0/hand:1,EXTCHO=FALSE; SET HAND PKGHANDB:NAME=BSC:0/hand:2,EXTCHO=FALSE; SET HAND PKGHANDB:NAME=BSC:0/hand:5,EXTCHO=FALSE; SET BTS PKGBTSO:NAME=BSC:0/bts:0,SMSCBUSE=FALSE,HOPP=FALSE, EXCDIST=35,EEXCDIST=FALSE;
1-54
A30808-X5226-C559-1-7618
BSC Database
Siemens
SET BTS PKGBTSO:NAME=BSC:0/bts:1,SMSCBUSE=FALSE,HOPP=FALSE, EXCDIST=35,EEXCDIST=FALSE; SET BTS PKGBTSO:NAME=BSC:0/bts:2,SMSCBUSE=FALSE,HOPP=FALSE, EXCDIST=35,EEXCDIST=FALSE; SET BTS PKGBTSO:NAME=BSC:0/bts:5,SMSCBUSE=FALSE,HOPP=FALSE, EXCDIST=35,EEXCDIST=FALSE; SET TSLA:NAME=BSC:0/pcma:0/tsla:1,VOLUL=12,VOLDL=12; SET TSLA:NAME=BSC:0/pcma:0/tsla:2,VOLUL=12,VOLDL=12; SET TSLA:NAME=BSC:0/pcma:0/tsla:3,VOLUL=12,VOLDL=12; SET TSLA:NAME=BSC:0/pcma:0/tsla:4,VOLUL=12,VOLDL=12; SET TSLA:NAME=BSC:0/pcma:0/tsla:5,VOLUL=12,VOLDL=12; SET TSLA:NAME=BSC:0/pcma:0/tsla:6,VOLUL=12,VOLDL=12; SET TSLA:NAME=BSC:0/pcma:0/tsla:7,VOLUL=12,VOLDL=12; SET TSLA:NAME=BSC:0/pcma:0/tsla:8,VOLUL=12,VOLDL=12; SET TSLA:NAME=BSC:0/pcma:0/tsla:9,VOLUL=12,VOLDL=12; SET TSLA:NAME=BSC:0/pcma:0/tsla:10,VOLUL=12,VOLDL=12; SET TSLA:NAME=BSC:0/pcma:0/tsla:11,VOLUL=12,VOLDL=12; SET TSLA:NAME=BSC:0/pcma:0/tsla:12,VOLUL=12,VOLDL=12; SET TSLA:NAME=BSC:0/pcma:0/tsla:13,VOLUL=12,VOLDL=12;
A30808-X5226-C559-1-7618
55-66
Siemens
BSC Database
SET TSLA:NAME=BSC:0/pcma:0/tsla:14,VOLUL=12,VOLDL=12; SET TSLA:NAME=BSC:0/pcma:0/tsla:15,VOLUL=12,VOLDL=12; SET TSLA:NAME=BSC:0/pcma:0/tsla:16,VOLUL=12,VOLDL=12; SET TSLA:NAME=BSC:0/pcma:0/tsla:17,VOLUL=12,VOLDL=12; SET TSLA:NAME=BSC:0/pcma:0/tsla:18,VOLUL=12,VOLDL=12; SET TSLA:NAME=BSC:0/pcma:0/tsla:19,VOLUL=12,VOLDL=12; SET TSLA:NAME=BSC:0/pcma:0/tsla:20,VOLUL=12,VOLDL=12; SET TSLA:NAME=BSC:0/pcma:0/tsla:21,VOLUL=12,VOLDL=12; SET TSLA:NAME=BSC:0/pcma:0/tsla:22,VOLUL=12,VOLDL=12; SET TSLA:NAME=BSC:0/pcma:0/tsla:23,VOLUL=12,VOLDL=12; SET TSLA:NAME=BSC:0/pcma:0/tsla:24,VOLUL=12,VOLDL=12; SET TSLA:NAME=BSC:0/pcma:0/tsla:25,VOLUL=12,VOLDL=12; SET TSLA:NAME=BSC:0/pcma:0/tsla:26,VOLUL=12,VOLDL=12; SET TSLA:NAME=BSC:0/pcma:0/tsla:27,VOLUL=12,VOLDL=12; SET TSLA:NAME=BSC:0/pcma:0/tsla:28,VOLUL=12,VOLDL=12; SET TSLA:NAME=BSC:0/pcma:0/tsla:29,VOLUL=12,VOLDL=12; SET TSLA:NAME=BSC:0/pcma:0/tsla:30,VOLUL=12,VOLDL=12;
1-56
A30808-X5226-C559-1-7618
BSC Database
Siemens
SET TSLA:NAME=BSC:0/pcma:0/tsla:31,VOLUL=12,VOLDL=12; CREATE OPC PKGOPCP:NAME=BSC:0/opc:0,SS7MTPTYP=CCITT, OPC=45-41, SPC=8-41, NTWIND=NAT0,BSSAPSSN=254,PERTFLAG=TRUE; SET OPC PKGMTL2:NAME=BSC:0/opc:0,M2T1=450,M2T2=1000,M2T3=10, M2T4N=80,M2T4E=5,M2T5=1,M2T6=60,M2T7=20,FLOWCTH=3,CONGTH=0, SANTIME=10,ERRCORMTD=BASIC_ERROR_CORRECTION,N1=110,N2=3000; SET OPC PKGMTL3:NAME=BSC:0/opc:0,M3T1=9,M3T2=13,M3T3=9,M3T4=8, M3T5=8,M3T12=12,M3T13=8,M3T14=20,M3T17=10,M3T19=12,M3T22OR20=36, M3T23OR21=36,M3T1TM=100,M3T2TM=6; SET OPC PKGSCCP:NAME=BSC:0/opc:0,TCONN=3,TIAS=96,TIAR=180,TREL=20, TGUARD=12, TSBS=60,TWCUSER=20,TINT=36; CREATE SS7L:NAME=BSC:0/ss7l:0,LNKA=0-0,TSLA=0-16,SLC=0; CREATE X25D:NAME=BSC:0/x25d:0,CLOCK=EXTERNAL, BAUDRATE=BAUD_64000,DTEDCE=DTE; SET X25D:NAME=BSC:0/x25d:0,L2PV=ISO_7776,T1=80,T4=200,RETRY=8, L2WIN=7,LCN2WC=1,L3WIN=7,T20=1800,T21=2000,T22=1800,T23=1800, T26=1800,T28=0,R20=3,R22=3,R23=3,L3PV=ISO8208VER84,FCTRL=YES, L3PS=PACKET_2048; CREATE OMAL:NAME=BSC:0/omal:0,LINKTYPE=X25D, X121ADDR="11111111110",REGION=0, DISTRICT=0,BSSNAME=0; CREATE SCAN BSCMEAS:NAME=BSC:0/scan:0,SCANNAME="Proc_load", ACTMEASLS=LST_ELEM,LSTBSCMEASTYPE=BSCPRCLD,GRANP=MINUTES_5, REPMETHD=BYMSG,START=1-JAN-1992,STOP=31-DEC-9999,PERTYPE=ALL; CREATE SYNC:NAME=BSC:0/sync:0,PCMSOBJ=0; $ENDFILE
A30808-X5226-C559-1-7618
57-66
Siemens
BSC Database
Example of Timeslot Assignment on Interfaces
An example of the assignment of the different timeslots and subslots is shown for the different interfaces in the figures below.
4.1
Asub and A Interface
The upper part of the figure shows the PCMS line, whereas in the lower part the 4 corresponding PCMA lines are drawn. Timeslot 0 of every PCM line carries the Service Word / Frame Alignment Word (SW/FAW) which is used e.g. for synchronization. Timeslot 31 is used for the exchange of LPDLS signaling between TRAU and BSC on the PCMS line. The corresponding timeslots on the 4 PCMA lines remain empty. Timeslot 16 on the Asub interface is used to carry CCSS7 signaling information in our example. This signaling is transmitted with a transmission rate of 64 kbit/s. One of the 4 PCM lines on the A interface carries the signaling information to the MSC. Therefore, timeslot 16 of one of the PCMA lines is occupied, whereas the corresponding timeslots on the other three PCMA lines remain empty. Note that not every TRAU is carrying CCSS7 signaling information. In case of an OMAL signaling link being defined via AINT (nailed up connection), as in our example, this is put in timeslot 30. OMAL is transmitted with 64 kbit/s, for this reason only one PCMA is needed. Timeslot 30 of the other PCMA lines remains empty. The traffic timeslots on the PCMA line, containing 64 kbit/s of information, are submultiplexed to one subslot with 16 kbit/s on the PCMS line and vice versa.
1-58
A30808-X5226-C559-1-7618
BSC Database
Siemens
31 30 16
C C S S 7
Asub
BSC
L P O M D A L L S
e f g h
a b c d
S W / F A W
TRAU
L P D L S
O M A L
C C S S 7
S W / F A W
e a

16
f b g c h d
0
TRAU

30 31
MSC
Fig. 23 Assignment of timeslots on Asub and A interface
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
A30808-X5226-C559-1-7618
59-66
Siemens
BSC Database
4.2
Abis and Um Interface
The upper part of the figure shows the PCMB line (Abis interface), whereas in the lower part the different carriers (TRX) on the air interface (Um) are drawn. Timeslot 0 of the PCM line carries the Service Word / Frame Alignment Word (SW/FAW) which is used e.g. for synchronization. In our example, with one PCM line 3 BTSE are connected. BTSE 0 contains 2 cells (BTS-0 and BTS-1), BTSE-1 and BTSE-2 contain only one cell (BTS-2 and BTS-3 respectively). For every BTSE a LAPD signaling link has to be defined, containing LPDLM and LPDLR. This signaling link can be created with 16 kbit/s or 64 kbit/s, the first being only possible for a BTSE with one or two carriers. The signaling for BTSE-0 is created in timeslot 1 in our example. It contains LPDLM-0 LPDLR-0-0 LPDLR-0-1 LPDLR-0-2 LPDLR-1-0
Contents of LAPD signaling timeslot
O&M signaling for BTSE-0 radio signaling for TRX-0 of BTS-0 radio signaling for TRX-1 of BTS-0 radio signaling for TRX-2 of BTS-0 radio signaling for TRX-0 of BTS-1
The signaling information in timeslot 10 is used for BTSE-1 and contains LPDLM-1, LPDLR-2-0 and LPDLR-2-1. It is created as 64 kbit/s signaling, whereas the signaling for BTSE-2 is defined in timeslot 15, subslot 0, as 16 kbit/s, containing LPDLM-2, LPDLR-3-0 and LPDLR-3-1. The traffic data are grouped into the 8 subslots of 2 timeslots on the Abis interface, thus forming the contents of a carrier on the air interface. For every BTS at least one broadcast channel has to be provided. This is reflected in the assignment of timeslots: In our example, TRX-0-0 contains the broadcast control channel for BTS-0, which is put into timeslot 0. Thus, on the Abis interface timeslot 2 subslot 0 remains empty. The remaining 7 timeslots are used for traffic, as well as the 8 timeslots of the other 2 carriers. The signaling for BTSE-3 is located in timeslot 15, subslot 0. The traffic channels are located in the remaining subslots of timeslot 15 and in timeslots 16, 17 and 18 of the PCMB line. So for this BTSE only 4 timeslots on the Abis interface are needed.
1-60
A30808-X5226-C559-1-7618
BSC Database
Siemens
Abis
BTSE 2 BTSE 1 BTSE 0
31 17 18 16 4 0 5 1 6 2 7 3
L A P D 14
1 10 4 L 4 5 1 A 5 1 6 2 P 6 2 D 7 3 7 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 2 0 S 4 L W 5 1 A / 6 2 P F D A 7 3 W T R X 0 0
TRX-3-0 TRX-3-1
TRX-2-0 TRX-2-1
TRX-0-0 TRX-0-1 TRX-0-2 TRX-1-0
4 4 0 5 1 5 1 6 2 6 2 7 3 7 3
BSC
T R X 3 1
T R X 3 0
T R X 2 1
T R X 2 0
T R X 1 0
T R X 0 2
T R X 0 1
Um
TRX-3-0
7 6 5 4 3 2 1
TRX-2-0
7 6 5 4 3 2 1
TRX-0-0
7 6 5 4 3 2 1
TRX-3-1
7 6 5 4 3 2 1 0
TRX-2-1
7 6 5 4 3 2 1 0
TRX-0-1
7 6 5 4 3 2 1 0
empty Signaling channel on Um Traffic channel
TRX-0-1
7 6 5 4 3 2 1 0
LAPD = LPDLM + LPDLR TRX-1-0

7 6 5 4 3 2 1
Fig. 24 Assignment of timeslots on Abis and Um interface
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
A30808-X5226-C559-1-7618
61-66
Siemens
BSC Database
Table of Frequency Bands

Downlink 935-960 925-960 921-960 921-946 925-950 1805-1880 1930-1990 Uplink 890-915 880-915 876-915 876-901 880-905 1710-1785 1850-1910 Number 124 174 194 124 124 374 299 512 ... 885 512 ... 810 Value range 001 ... 124 975 ... 1023 955 ... 1023
Frequency GSM900 E-GSM900 R-GSM900 RE-GSM900 PS-GSM900 GSM1800 GSM1900

Frequency bands
1-62
A30808-X5226-C559-1-7618
BSC Database
Siemens
6
Title:
Exercises
Database Interrogation
Exercise 1
Enter the following command to obtain all of the cells or BTS that have been created in the BTSE (BTSM) in the Base Station of the Training Center: GSLIST:BTSM-0
Enter the following command to obtain all of the carriers (TRX) that have been created in all of the BTS: GSLIST:BTS-# Enter the following command to obtain all of the radio channels that have been created in all of the TRX: GSLIST:TRX-BTS#-TRX#
A30808-X5226-C559-1-7618
63-66
Siemens
BSC Database
Enter the following command to obtain all of the timeslots on the PCMB that have been associated with a radio channel: GET:CHAN-BTS#-TRX#-(Radio_Channel_#)
Perform the command for all of the BTS, TRX and Radio Channels and list the result in the following table: Subslot 0 TS0 TS1 TS2 TS3 TS4 TS5 TS6 TS7 TS8 TS9 TS10 Subslot 1 Subslot 2 Subslot 3
1-64
A30808-X5226-C559-1-7618
BSC Database
Siemens
Enter the following command to obtain all of the LPDLM and LPDLR that have been assigned to the PCMB: GSLIST:PCMB-0
Enter the following commands to obtain the timeslot on the PCMB that has been assigned to the LPDLM and LPDLR: GET:LPDLM-BTSM# GET:LPDLR-BTS#-TRX#
A30808-X5226-C559-1-7618
65-66
Siemens
BSC Database
Exercise 2
Title:
Database Interpretation
1. Use the ASCII representation of the database of the training BSC and interpret the entries. 2. Draw the connections between the network elements in a graph like the creation tree. Are there BTSE connected in multidrop or loop configuration? 3. For each of the BTSE show the BTS supported with the corresponding TRX, their frequencies etc.
1-66
A30808-X5226-C559-1-7618
Siemens
Objectives
The participant is able to explain and use the parameters for cell selection and cell reselection
Contents
1 1.1 1.2 2 2.1 2.2 2.3 2.4 3 4 Cell Selection Measurements for Normal Cell Selection Criteria for Cell Selection Cell Reselection Necessary Actions for a Cell Reselection Phase 1 MS Phase 2 MS Triggers for Cell Reselection Parameters for Cell Selection/Reselection Exercise 3 3 4 12 12 13 14 16 18 30
A30808-X5226-C559-1-7618
2-1
Siemens
2-2
A30808-X5226-C559-1-7618
Siemens
Cell Selection
Cell selection/reselection are processes which are performed by a GSM mobile station in idle mode. The MS uses the cell selection algorithm to look for a cell (of the chosen PLMN) where it can camp on ("camping on a cell"). If the MS looses coverage of that cell (caused for example by moving out of the cell) it will look for the most suitable alternative cell (of the selected PLMN) and it will camp on that cell. This is called cell reselection. The cell selection /reselection processes are described in GSM 03.22, GSM 05.08 and ETSI TS 123 122.
1.1
Measurements for Normal Cell Selection
In case of normal cell selection the MS has no prior knowledge on which GSM 900 or DCS 1800 frequencies are BCCH carriers. Therefore the MS has to search in the beginning all RF carriers of the corresponding system (124 carriers for P-GSM, 174 carriers for E-GSM and 374 carriers for DCS 1800), and has to measure the signal strength on each RF carrier. The MS takes 5 measurement samples per RF carrier which are averaged: AV_RXLEV = 1/5 x (RXLEV1 + RXLEV2 + ... + RXLEV5) A multi band MS searches all carriers within its band of operation. The number of carriers searched corresponds to the sum of carriers on each band of operation.
A30808-X5226-C559-1-7618
2-3
Siemens
1.2
Criteria for Cell Selection
Based on these measurements the MS can estimate whether a cell will be an appropriate serving cell from the radio propagation point of view, i.e. whether there will be a sufficient link quality:
1.2.1
C1 Criterion for Cell Selection
C1 = AV_RXLEV - RXLEV_ACCESS_MIN - max (0, MS_TXPWR_MAX_CCH - P )
RXLEV_ACCESS_MIN : MS_TXPWR_MAX_CCH: P:
minimum received level at the MS required for access to the system maximum allowed MS transmit power on RACH Powerclass of MS specified in GSM O5.05
Power Class (GSM 05.05) 1 2 3 4 5
Max. Output Power (GSM 900) -8 Watt = 39 dBm 5 Watt = 37 dBm 2 Watt = 33 dBm 0.8 Watt= 29 dBm
Max. Output Power (DCS 1800) 1 Watt = 30 dBm 0.25W = 24 dBm 4 Watt = 36 dBm
Power classes of GSM 900 and DCS 1800 MS
2-4
A30808-X5226-C559-1-7618
Siemens
During cell selection procedure the MS will select only those cells which have C1 > 0. This means that the averaged received level downlink has to be greater than the threshold RXLEV_ACCESS_MIN + max (0, MS_TXPWR_MAX_CCH - P):
l
AV_RXLEV > RXLEV_ACCESS_MIN + max (0, MS_TXPWR_MAX_CCH - P)
The maximum term is included to ensure a sufficient uplink received level even for MS of low maximum transmit power: If P < MS_TXPWR_MAX_CCH, then the C1 criterion is equivalent to:
l
AV_RXLEV > RXLEV_ACCESS_MIN + (MS_TXPWR_MAX_CCH - P)
i.e. the averaged received level downlink has to exceed the RXLEV_ACCESS_MIN by a certain margin to ensure that the Base Station can receive the MS even in case of a MS with low maximum output power. If P > MS_TXPWR_MAX_CCH, then the C1 criterion reduces to:
l
AV_RXLEV > RXLEV_ACCESS_MIN
A30808-X5226-C559-1-7618
2-5
Siemens
1.2.2
Suitable Cell
Beside the C1 radio criterion there are some other criteria (administrative and traffic control) for a cell to be suitable: A Suitable Cell is defined as a cell which
l l l l
is part of the selected PLMN, is unbarred (parameter CELL_BAR_ACCESS = 0), has a value C1 > 0, is not in a location area forbidden for national roaming.
To allow e.g. emergency calls the conditions for a serving cell are less restrictive: An Acceptable Cell is defined as a cell which
l l
is unbarred, has a parameter C1 > 0.
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
2-6
A30808-X5226-C559-1-7618
Siemens
The general strategy for cell selection is to find the suitable cell with the highest C1 (best estimated link quality). If no suitable cell can be found, an acceptable cell is selected.
A30808-X5226-C559-1-7618
2-7
Siemens
Cell Selection Algorithm (no BCCH Info)
measure all carriers
sort by received level
carriers in list yes trial carrier: best level in list
no
Selection of an acceptable cell
no BCCH yes decode BCCH
remove trial carrier from list
suitable cell yes
no
cell in selected PLMN yes try only carriers of BCCH allocation
no
Camp on normal priority cell
Fig. 1 Cell selection for phase 1 MS - no BCCH info is stored
2-8
A30808-X5226-C559-1-7618
Siemens
For phase 2 MS there is an additional parameter called CELL_BAR_QUALIFY (values: 0, 1) used to assign different priorities to cells: CELL_BAR_QUALIFY = 0 CELL_BAR_QUALIFY = 1 <=> <=> normal priority cell low priority cell
A MS tries first to select a suitable normal priority cell. If no such cell can be found, a suitable low priority cell is selected.
A30808-X5226-C559-1-7618
2-9
Siemens
Cell Selection Algorithm (no BCCH Info)
measure all carriers
sort by received level
carriers in list yes trial carrier: best level in list
no
low priority cell found no Selection of an acceptable cell
yes
Camp on low priority cell
BCCH yes decode BCCH
no
remove trial carrier from list
suitable cell yes
no
cell in selected PLMN yes try only carriers of BCCH allocation
no
normal priority yes Camp on normal priority cell
no
suitable low priority cell found
try only normal priority cells
Fig. 2 Cell selection for phase 2 MS - no BCCH info is stored
2-10
A30808-X5226-C559-1-7618
Siemens
1.2.3
Cell Selection with Stored BCCH Information
Optionally, the MS may store information on received level on BCCH carriers when switched off. When switched on, the MS first performs measurements on these carriers. If cell selection for the corresponding cells is not successful, normal cell selection is carried out.
A30808-X5226-C559-1-7618
2-11
Siemens
Cell Reselection
While moving within the radio network in idle mode another cell may be more appropriate to serve the MS. Therefore cell reselection may be performed. For the following discussion the MS shall camp on a cell which is called serving cell.
2.1
Necessary Actions for a Cell Reselection
The following actions are performed by the MS to detect whether or not a cell reselection is necessary:
l
Detection of a Downlink Signaling Failure: The downlink signaling failure counter DSC is a counter running in the MS. The starting value of this counter is called DSC0 and is set by the MS to the following value: DSC0 = round(90 / BS_PA_MFRMS) The value of BS_PA_MFRMS is broadcasted in the system informations on the BCCH of the serving cell. Each BS_PA_MFRMS, the MS attempts to decode the messages on its paging sub-channel. Depending on whether or not this decoding is successful, the value of the downlink signaling failure counter DSC is modified in the following way : successful decoding: DSC new = DSC old + 1 if DSC new + 1 > DSC0 DSC new = DSC old unsuccessful decoding: DSC new = DSC old - 4
If DSC < 0 the MS has detected a downlink signaling failure.
2-12
A30808-X5226-C559-1-7618
Siemens
Monitoring of all BCCH carriers given in the BCCH allocation (neighbor cells) of the serving cell Taking at least 5 samples of the received level from the serving cell (on paging sub-channel) as well as from the neighbor cells => AV_RXLEV(serving cell) and AV_RXLEV (neighbor cell)
Decoding of full BCCH data of the serving cell at least every 30 sec Decoding of BCCH data of the 6 strongest neighbor cells at least every 5 minutes
2.2
Phase 1 MS
From the radio propagation point of view it is worth to select a new (neighbor) cell if the received level from that neighbor cell exceeds the received level of the current serving cell. For phase 1 MS this is expressed using the C1 criterion C1 (neighbor cell) > C1 (serving cell). For the reselection process for phase 1 MS the neighbor cells are ordered according to their C1-value.
A30808-X5226-C559-1-7618
2-13
Siemens
2.3
Phase 2 MS
For phase 2 MS a modified path loss criterion, the C2 criterion, is used The C2 criterion depends on the value of a timer T which is called PENALTY_TIMER. The timer T is started in the MS for each cell in the list of the 6 strongest neighbor cells as soon as it is placed on the list. Timer T is reset to 0 if the cell is removed from the list. During penalty time: C2 = C1 + CELL_RESELECT_OFFSET - TEMPORARY_OFFSET After penalty time: C2 = C1 + CELL_RESELECT_OFFSET For penalty time = 31 the whole time: C2 = C1 - CELL_RESELECT_OFFSET CELL_RESELECT_OFFSET, TEMPORARY_OFFSET, and PENALTY_TIME are cell reselection parameters which are broadcasted on the BCCH of the cell in the system informations if CELL_RESLECT_PARAM_IND (Cell Reselection Parameter Indication) is set to 1.
2-14
A30808-X5226-C559-1-7618
Siemens
Cell included in the list of 6 strongest
C2 TEMPORARY_OFFSET C1 CELL_RESELECT_OFFSET
PENALTY_TIME
Fig. 3 Illustration of the C2 criterion
A negative TEMPORARY_OFFSET reduces the priority of a cell in the list of strongest neighbor cells. A positive CELL_RESELECT_OFFSET increases the priority of a cell in the list of strongest neighbor cells. This mechanism may be applied in hierarchical cell structures to keep fast moving mobiles in the umbrella cells and slow moving mobiles in the micro cells: When a mobile reaches the coverage area of a (neighbor) micro cell given by the C1 criterion, this cell becomes effectively excluded from reselection during the PENALTY_TIME. A fast moving mobile is assumed to have left the coverage area of the micro cell before PENALTY_TIME is reached and hence the micro cell is not selected. In contrast a slow moving mobile is assumed to be still within the coverage area of the micro cell when PENALTY_TIME has expired. Applying the positive CELL_RESELECT_OFFSET, this cell is selected with preference.
A30808-X5226-C559-1-7618
2-15
Siemens
2.4
Triggers for Cell Reselection
Cell reselection is triggered by the following conditions: 1. C1 < 0 for the serving cell for a period of 5 s 2. MS detects a downlink signaling failure 3. Serving cell becomes barred 4. Phase 1 MS C1 (serving cell) < C1 (suitable neighbor cell) if the suitable neighbor cell is in the same location area C1 (serving cell) + CELL_RESELECT_HYSTERESIS < C1 (suitable neighbor cell) if the suitable neighbor cell is in another location area for a period of 5 sec. 5. Phase 2 MS C2 (serving cell) < C2 (suitable neighbor cell) if the suitable neighbor cell is in the same location area C2 (serving cell) + CELL_RESELECT_HYSTERESIS < C2 (suitable neighbor cell) if the suitable neighbor cell is in another location area for a period of 5 sec. 6. A random access attempt is unsuccessful even after the maximum number of repetitions. For phase 2 there is the additional trigger: 7. A location update request has been rejected with cause location area not allowed.
2-16
A30808-X5226-C559-1-7618
Siemens
C1 BTS1
Phase 1 MS
direction of movement BTS2
high power class MS low power class MS
BTS1
BTS2
CELL_RESELECT_ HYSTERESIS C1=0 (h) (l)
Radius of Cell 2 for selection (l) low power MS (h) high power MS
(a) (b) Cell Reselection (a) no change of location area (b) change of location area
Fig. 4 Illustration of Cell Selection / Reselection
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . 2-17
A30808-X5226-C559-1-7618
Siemens
Parameters for Cell Selection/Reselection
BA (BCCH) - BCCH Allocation broadcasted on BCCH In each cell the absolute radio frequency carrier number BCCH_ARFCN_NC(n) of each of its neighbor cell n has to be known. This information is broadcasted as the so called BCCH Allocation to all MS in the respective cell. On the corresponding frequencies the MS take measurement samples of the received level used for cell selection / reselection. Furthermore, the BCCH of neighbor cells has to be decoded by the MS (at least every 5 min) to know the current values of the control parameters for the reselection algorithm. Object ADJC Package DB Name BCCHFREQ Range 0...1023 Step Size 1 Unit -
BCCH_ARFCN_NC(n)
2-18
A30808-X5226-C559-1-7618
Siemens
CELL_BAR_ACCESS - Cell Barred for Access A mobile station can not camp on a barred cell, i.e. a barred cell is not selected by the cell selection/reselection procedure. Mobile stations which camp on a cell while it becomes barred initialize the reselection procedure to find a new (unbarred) cell, i.e. traffic load is distributed to neighbor cells. This means that e.g. neither a call nor a location update can start in a barred cell. However, a cell barred for access is not barred for incoming handovers. To barr a cell completely, e.g. for maintenance reasons also incoming handovers have to be avoided. To reduce overload in a certain cell more moderately without distributing the overload to neighbor cells, barring of access classes has to be used. Barring access for an access class does not trigger a cell reselection for MSs of that class. Object BTS Package BTSO DB Name Range Step Size Unit -
CELLBARR FALSE/TRUE
CELL_BAR_ACCESS - Cell Barred for Access default: FALSE
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . 2-19
A30808-X5226-C559-1-7618
Siemens
RXLEV_ACCESS_MIN - Minimum Downlink Received Level for Cell to be Selected The parameter RXLEV_ACCESS_MIN determines the cell border for a MS in idle mode by means of the C1 or C2 criterion respectively. Choosing a high value, reduces the risk of a handover immediately after call setup. On the other hand the value has to be low enough to achieve a sufficient overlap between adjacent cells (especially if they belong to different location areas). It has to be observed that the overlap may be different for mobiles of different power classes (refer to MS_TXPWR_MAX_CCH). In any case RXLEV_ACCESS_MIN has to be above the MS receiver sensitivity level (-100 dBm for DCS1800, -102 dBm for GSM handhelds, -104 dBm for other GSM MS). Furthermore, it has to harmonize with the handover thresholds (RXLEV_MIN, L_RXLEV_HO). Object BTS Package BTSB DB Name RXLEVAMI Range 0...63 Step Size 1 Unit RXLEV
RXLEV_ACCESS_MIN - Minimum downlink received level for cell to be selected default: 6 RXLEV 0 = less than -110 dBm. RXLEV 1 = -110 dBm to -109 dBm. ... RXLEV 62 = -49 dBm to-48 dBm. RXLEV 63 = greater than -48 dBm.
2-20
A30808-X5226-C559-1-7618
Siemens
MS_TXPWR_MAX_CCH - Maximum allowed MS Transmit Power on RACH The transmit power level the MS uses for the access on the Random Access Channel is given by the minimum of two values:
l l
the maximum possible transmit power of the MS (given by the power class P of the MS) the maximum allowed power for access within the respective cell (given by MS_TXP WR_MAX_CCH).
This parameter affects the

l l
the random access procedure the cell selection procedure.
Random access: If there is a collision of channel requests on the random access channel, the one with the higher received level has a good chance to be decoded and to get a response by the BTS. Hence MS with higher output power are preferred. This imbalance can be avoided by choosing a low maximum allowed transmit power. Cell Selection: To be selected by the cell selection procedure, a cell has to fulfill the C1 criterion C1 > 0 where C1 = AV_RXLEV - RXLEV_ACCESS_MIN - Max(0, MS_TXPWR_MAX_CCH - P ) Choosing for example MS_TXPWR_MAX_CCH = Pmin where Pmin is the output power level for the minimum power class 5 (29 dBm), the C1 criterion reduces to AV_RXLEV > RXLEV_ACCESS_MIN for MSs of all power classes. Hence the same idle mode cell border is seen by each mobile.
A30808-X5226-C559-1-7618
2-21
Siemens
Choosing for example MS_TXPWR_MAX_CCH = Pmax where Pmax is the output power level for the maximum power class 1 (43 dBm), the C1 criterion reduces to AV_RXLEV > RXLEV_ACCESS_MIN + ( MS_TXPWR_MAX_CCH - P ) for MSs of all power classes. Hence, a larger cell radius is seen by a mobile of higher output power than by a mobile of lower output power. On the other hand one can ensure by this mechanism that a certain uplink received level is exceeded by each MS independent of its power class. Object BTS Package BTSC DB Name MSTXPMAXCH Range 0...31 Step Size 1 Unit 2 dB
MS_TXPWR_MAX_CCH - Maximum allowed MS transmit power on RACH default: 2 For the values of MS_TXPWR_MAX_CCH see the power control level defined in GSM rec. 05.05: MS GSM900 Phase 1 0 := 43 dBm 1 := 41 dBm 2 := 39 dBm 3 := 37 dBm ... 15 := 13dBm 16-31 := 13 dBm MS GSM900 Phase 2 0 := 39 dBm 1 := 39 dBm 2 := 39 dBm 3 := 37 dBm ... 19 := 5 dBm 20-31 := 5 dBm MS DCS1800 0 := 30 dBm 1 := 28 dBm 2 := 26 dBm 3 := 24 dBm ... 15 := 0 dBm 16-31 := 0 dBm
2-22
A30808-X5226-C559-1-7618
Siemens
POWER_OFFSET - Additional Parameter for Class 3 DCS1800 MS The parameter POWER_OFFSET is only used by class 3 DCS1800 MS to calculate the C1-criterion described as follows. C1 = AV_RXLEV - RXLEV_ACCESS_MIN - Max(0,MS_TXPWR_MAX_CCH + POWER_OFFSET- P). Object BTS Power_Offset Package BTSC DB Name PWROFS Range 0...3 Step Size 1 Unit 2 dB
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
A30808-X5226-C559-1-7618
Siemens
CELL_RESELECT_HYSTERESIS - Hysteresis for Reselection of a Cell from another Location Area In idle mode the MS selects a new (neighbor) cell if the received level of the neighbor cell exceeds the received level of the current cell in order to be served by the cell with the expected best link quality. However, due to fading effects, the propagation conditions may change rapidly and therefore a reselection may occur very frequently. If the cells involved in the reselection process belong to the same location area, frequent cell reselection does not have an effect on the network performance. But if the involved cells belong to different location area, the reselection of a new cell triggers a location update procedure which causes signaling load (e.g. on the SDCCH) and involves all network elements. To avoid unnecessary signaling load by forward and backward reselection due to fading, a hysteresis given by the parameter CELL_RESELECT_HYSTERESIS is introduced, i.e. a cell from another location area is selected only if the corresponding received level exceeds the level of the current serving cell by the value of this parameter. This is expressed in terms of the C1 (phase 1) or C2 (phase 2) criterion: C1 (serving cell) + CELL_RESELECT_HYSTERESES(serving) < C1 (suitable neighbor cell) or C2 (serving cell) + CELL_RESELECT_HYSTERESES(serving) < C2 (suitable neighbor cell) respectively. The adjustment of CELL_RESELECT_HYSTERESES should be a compromise between
l l
reduction of unnecessary location updates (high value) and selection of the cell with best reception quality (low value). Object BTS Package BTSB DB Name CELLRESH Range 0...7 Step Size 1 Unit 2 dB
CELL_RESELECT_HYSTERESIS - Hysteresis for reselection of a cell from another location area default: 2
2-24
A30808-X5226-C559-1-7618
Siemens
CELL_RESELCT_PARAM_IND_ - Phase 2 Reselection Parameter Indication CELL_RESELECT_PARAM_IND=1: The cell reselection parameters CELL_RESELECT_OFFSET, TEMPORARY_OFFSET and PENALTY_TIME used for the C2 criterion as well as the parameter CELL_BAR_QUALIFY are broadcasted on the BCCH. These parameters are taken into account by phase 2 MS, but are ignored by phase 1 MS. CELL_RESELECT_PARAM_IND = 0: The cell reselection parameters and CELL_BAR_QUALIFY are not broadcasted on the BCCH. A phase 2 MS then uses the value 0 for all these parameters, i.e. C1 = C2. Object BTS Package BTSB DB Name CRESPARI Range 0...1 Step Size Unit -
CELL_RESELCT_PARAM_IND_ - Phase 2 Reselection Parameter Indication default: 1
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . 2-25
A30808-X5226-C559-1-7618
Siemens
CELL_BAR_QUALIFY Parameter is used to assign a priority to a cell selection process. A suitable cell of low priority is only selected if no suitable cell of normal priority can be found. This parameter can be used e.g. in hierarchical cell structures that the MS initially selects an umbrella cell. Object BTS Package BTSB DB Name CBQ Range 0...1 Step Size 1 Unit -
CELL_BAR_QUALIFY default: 0 normal priority: 0 low priority: 1
2-26
A30808-X5226-C559-1-7618
Siemens
PENALTY_TIME - Time to Apply a Negative Offset to C2 of a Neighbor Cell PENALTY_TIME < 31: A timer T is started in the MS for each cell in the list of the 6 strongest neighbor cells as soon as it is placed on the list. T is reset to 0 if the cell is removed from the list. During Penalty Time (T < PENALTY_TIME ) a negative TEMPORARY_OFFSET is applied to the C2 of the respective neighbor cell C2 = C1 + CELL_RESELECT_OFFSET - TEMPORARY_OFFSET which is removed after Penalty Time (T > PENALTY_TIME ): C2 = C1 + CELL_RESELECT_OFFSET. PENALTY_TIME = 31: C2 = C1 - CELL_RESELECT_OFFSET. For PENALTY_TIME = 31 the priority of a neighbor cell for reselection is permanently reduced. Object BTS Package BTSB DB Name PENTIME Range 0...30 and 31: special meaning Step Size 1 Unit 20 sec
PENALTY_TIME - Time to apply a negative offset to C2 of a neighbor cell default: 5
A30808-X5226-C559-1-7618
2-27
Siemens
TEMPORARY_OFFSET Subtracting TEMPORARY_OFFSET from CELL_RESELECT_OFFSET reduces the priority of a cell in the list of strongest neighbor cells, i.e. during run time of the timer the corresponding neighbor cell is effectively barred for cell reselection. Object BTS Package BTSB DB Name TEMPOFF Range 0...7 Step Size 1 Unit 10 dB 7: infinity
TEMPORARY_OFFSET default: 1
2-28
A30808-X5226-C559-1-7618
Siemens
CELL_RESELECT_OFFSET Adding CELL_RESELECT_OFFSET increases the priority of a cell in the list of strongest neighbor cells when the timer has expired. This mechanism may be applied in hierarchical cell structures to keep fast moving mobiles in the umbrella cells and slow moving mobiles in the micro cells: When a mobile reaches the coverage area of a (neighbor) micro cell, given by the C1 criterion, this cell becomes effectively excluded from reselection during the PENALTY_TIME. A fast moving mobile is assumed to have left the coverage area of the micro cell before PENALTY_TIME is reached and hence the micro cell is not selected. In contrast, a slow moving mobile is assumed to be still within the coverage area of the micro cell when PENALTY_TIME has expired. Applying the positive CELL_RESELECT_OFFSET, this cell is selected with preference. Object BTS Package BTSB DB Name CRESOFF Range 0...63 Step Size 1 Unit 2 dB
CELL_RESELECT_OFFSET default: 1
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
A30808-X5226-C559-1-7618
Siemens
Exercise
Exercise 1
Fill in the relevant parameters for Cell Selection/Reselection: Specification Name (GSM Name) BSC-Database Name Value Range Remarks
2-30
A30808-X5226-C559-1-7618
Handover
Siemens
Handover
Contents
1 1.1 1.2 1.3 1.4 1.5 2 2.1 2.2 2.3 2.4 2.5 2.6 3 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 General Steps of the Handover Process Types of Handover Handover Causes Flags to Enable/Disable Handover Types and Causes Comments Measurement Preprocessing Measurement Values Summary of Measurement Values for Handover Measurement Reporting and Neighbor Cell Book-Keeping Illustration of Measurement Preprocessing Parameters for Measurement Preprocessing Remarks Threshold Comparisons and Handover Detection Algorithms Decision Criteria Handover Regions Power Budget Parameters for Handover Decision Priorities of Handover Causes Limitation of Intracell Handover Repetition Prevention of Back-Handover Limitation of Handover Failure Repetition Remarks 3 3 4 5 7 8 9 9 13 14 18 19 20 21 21 22 23 24 25 26 28 30 32
A30808-X5226-C559-1-7618
3-1
Siemens
Handover
4 4.1 4.2 4.3 5 5.1 6 6.1 6.2 6.3 7 8
Target Cell List Generation Conditions for Neighbor Cells to be included in the Target Cell List Order Criterion for Handover Candidate Cells within the Target Cell List Evaluation of the Target Cell List Handover Signaling and Timer Parameters and Timers for Handover Signaling Preemption, Directed Retry, Queuing Parameters for Preemption and Queuing Directed Retry Parameters for Directed Retry Handover related Performance Measurements Exercise
36 36 36 37 39 40 43 44 48 52 54 59
3-2
A30808-X5226-C559-1-7618
Handover
Siemens
1
l l l
General
maintaining a connection in case of a cell change (movement) changing a channel in case of severe disturbance (interference) designing cell borders and radio network structure
The handover main objectives are:
1.1
Steps of the Handover Process
The handover process can be divided into several sub-processes: No. 1 Sub-process Measurements: - DL Level serving cell - DL Quality serving cell - DL Level neighbor cells - UL Level - UL Quality - Timing advance 2 3 4 5 6 Measurement reporting and neighbor cell book-keeping Measurement preprocessing Threshold comparison and handover detection Target cell list generation Target cell list evaluation - intra BSS handover - inter BSS handover 7 8 Selection of new channel Handover execution BSC MSC BSC MS, BTSE, BSC, MSC MS BTSE BTSE BTSE BTSE BTSE MS Involved Network Element
A30808-X5226-C559-1-7618
3-3
Siemens
Handover
1.2
Types of Handover
Different types of handover can be distinguished with respect to the changed region: a cell, a BSS area or an MSC area. The different types of handover can be enabled or disabled by several flags.
1. Intracell Handover 2. Intra-BSS Handover 3. Intra-MSC Handover 4. Inter-MSC Handover 2 BSC 1a
BSC 2
MSC 1
3 MSC 2 BSC 1b
Fig. 1 Types of Handover
. . . . . . . . . . . . . . . 3-4
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
A30808-X5226-C559-1-7618
Handover
Siemens
1.3
Handover Causes
Two criteria groups of different handover causes are defined: Radio Criteria received quality (too bad that means bit error rate too high) received level (too low) MS-BS distance (too high) better cell (power budget: relative received level) Network Criteria serving cell congestion --> directed retry for call setup MS-BS distance (too high/low in extended cells) received level or MS-BS distance (too low/high in concentric cells) intracell HO inter-/intracell HO intercell HO intercell HO intercell HO intercell HO intracell HO
A30808-X5226-C559-1-7618
3-5
Siemens
Handover
The first three causes are known as mandatory or imperative causes, i.e. if one of these causes occurs, a handover is necessary to maintain the call. This may happen because the MS is leaving the coverage area of the serving cell (intercell handover) or because there is a strong interferer using the same channel in another cell (intracell handover). The fourth cause is an optional one, i.e. the link quality in the serving cell is sufficiently good, but there are neighbor cells with better received level. Though its not necessary for the link quality of this specific call, there is a benefit for overall network performance to handover the call to the better cell: A call in the better cell causes less interference. Especially, if power control is applied. To achieve the same received level in the better cell, a smaller transmit power can be used in this cell. In a well planned radio network better cell should be the overwhelming handover cause. Hence, the locations of a better cell handover determine the cell boundaries. The fifth cause is named forced handover because it is triggered by the BSC due to a congestion situation, and not due to radio conditions on the link. This handover (directed retry) is performed from a SDCCH in the congested cell to a TCH in a neighbor cell during call setup. The last two causes are intracell handovers in special cell configurations:
l l
in extended cells handovers are feasible from single to double timeslots and vice versa. In a concentric cell handovers are performed between the inner and complete area.
These handover causes can be enabled/disabled separately by corresponding flags.
3-6
A30808-X5226-C559-1-7618
Handover
Siemens
1.4
Flags to Enable/Disable Handover Types and Causes
The flags to enable(TRUE) / disable(FALSE) the different handover types and causes are listed in the table below. With one exception they are all administered in the object HAND. Specification Name EN_INTER_HO EN_INTRA_HO EN_BSS_INTER_HO DB Name INTERCH INTRACH LOTERCH Meaning Flag to enable/disable generally intercell handover for this BTS. Flag to enable/disable generally intracell handover for this BTS. Flag to determine weather inter cell handover are controlled by BSC (TRUE) or MSC (FALSE). Flag to determine weather intra cell handover are controlled by BSC (TRUE) or MSC (FALSE). Flag to enable/disable intercell handover due to quality. Flag to enable/disable intercell handover due to level. Flag to enable/disable intercell handover due to distance. Flag to enable/disable better cell (power budget) handover. Flag to enable/disable forced handover. Flag to enable/disable extended cell handover. Flag to enable/disable concentric cell distance handover. Flag to enable/disable inner to inner handover in a sectorized concentric cell.
EN_BSS_INTRA_HO
LOTRACH
EN_RXQUAL_HO EN_RXLEV_HO EN_DIST_HO EN_PBGT_HO EN_FORCED_HO
RXQUALHO RXLEVHO DISTHO PBGTHO ENFORCHO (PKG BSCB)
EN_EXTENDED_CELL_HO EXTCHO EN_CON_CELL_DIST_HO EN_INNER_INNER_HO CCDIST ININHO
A30808-X5226-C559-1-7618
3-7
Siemens
Handover
1.5
l
Comments
Enabling BSS internal handover has the following advantages: - reduction of signaling load on the A-interface - reduction of processor load in the MSC - faster handover execution. Consequences: - BSS internal handover should be enabled, - BSS regions should be adapted to the real traffic flow to reduce the inter-BSS handover rate.
Normally, intracell handover should be enabled to allow a handover from a channel with high interference to another one with less interference within the same cell. However, if random frequency hopping is applied, it may be reasonable to disable intracell handover since interference is approximately the same on all channels and no improvement can be achieved by intracell handover. If distance handover is disabled, a MS could largely exceed the planned cell boundaries in the case of favorable radio conditions at the serving cell without causing a handover. As a consequence, neighboring cells may suffer from excessive interference produced by this MS. Furthermore, there is a risk that link quality decreases very suddenly (turn around a corner), i.e. there is the risk of a call drop. Hence, distance handover should be switched on. If power budget handover is disabled, no handovers with cause better cell are generated. Nevertheless, power budget is calculated and evaluated for the ranking of neighbor cells within the target cell list which also has to be compiled for mandatory handovers.
3-8
A30808-X5226-C559-1-7618
Handover
Siemens
2
2.1
Measurement Preprocessing
Measurement Values
The following values are measured and calculated each SACCH multiframe (480ms):
RXQUAL: The received signal quality is defined according to GSM 05.08 as function of the bit error rate (BER) before channel decoding: RXQUAL = 0: RXQUAL = 1: RXQUAL = 2: RXQUAL = 3: RXQUAL = 4: RXQUAL = 5: RXQUAL = 6: RXQUAL = 7: 0.2% 0.4% 0.8% 1.6% 3.2% 6.4% < < < < < < BER BER BER BER BER BER BER BER < < < < < < < 0.2% 0.4% 0.8% 1.6% 3.2% 6.4% 12.8% assumed value: assumed value: assumed value: assumed value: assumed value: assumed value: assumed value: assumed value: 0.14% 0.28% 0.57% 1.13% 2.26% 4.53% 9.05% 18.01%
12.8% <
The RXQUAL values are measured on the dedicated channel for the uplink as well as for the downlink for each TDMA frame (100 frames) within an SACCH multiframe. The measured RXQUAL values are averaged over the respective SACCH period using the assumed values of the table above.
A30808-X5226-C559-1-7618
3-9
Siemens
Handover
Since there are 104 TDMA frames in each SACCH multiframe (and the measurements in 4 of these frames are optional), the number of samples on each BCCH carrier depends on the number of carriers defined in the BCCH Allocation and therefore can be different: Number of BCCH carriers defined in the BCCH allocation 32 16 10 8 ... Number of samples per carrier in each SACCH multiframe 3-4 6-7 10 - 11 12 - 13 ...
These figures are increased if the MS is able to perform measurements on more than 1 BCCH carrier during each TDMA frame.
3-10
A30808-X5226-C559-1-7618
Handover
Siemens
RXLEV: The received signal level is measured on the dedicated channel for the uplink as well as for the downlink for each TDMA frame (100 frames) within an SACCH multiframe. The measured level values in [dBm] are averaged over the respective SACCH period. The average value is mapped on an RXLEV value (refer to GSM 05.08): RXLEV = 0: RXLEV = 1: RXLEV = 2: ... RXLEV = 62: RXLEV = 63: < -110 dBm -110 dBm ... -109 dBm -109 dBm ... -108 dBm ... -49 dBm ...-48 dBm > -48 dBm
RXLEV_NCELL(n): The mobile measures the level received on the BCCH frequency of each neighbor cell n. The mapping is as for RXLEV.
MS_BS_DIST: The distance MS_BS_DIST between the MS and BS is calculated from the timing advance (TA) value measured by the BS and is coded as follows: MS_BS_DIST = 0, 1, ... 35. Distance[Km]
A30808-X5226-C559-1-7618
3-11
Siemens
Handover
Aspects of Discontinuous Transmission When Voice Activity Detection (VAD) and Discontinuous Transmission (DTX) is applied not all TDMA frames within a SACCH multiframe may be transmitted. Hence, RXQUAL and RXLEV measurement values (SUB values) for the corresponding SACCH frames are less reliable than those for that SACCH multiframes with no silence period (FULL values). Therefore SUB and FULL values have to be distinguished within measurement preprocessing (see below).
DTX not applied: 100 slots not idle
DTX applied (silence periode): 12 slots not idle
idle slot
speech burst
SACCH burst
Silence description burst
Fig. 2 SACCH Multiframe occupancy
3-12
A30808-X5226-C559-1-7618
Handover
Siemens
2.2
Summary of Measurement Values for Handover

Range 0 - 63 0 - 63 0-7 0-7 0.-.1 0 - 63 Measurement Type Description Received signal level on TCH/SDCCH (full set of TDMA frames) downlink Received signal level on TCH (subset of TDMA frames) downlink Received signal quality on TCH/SDCCH (full set of TDMA frames downlink Received signal quality on TCH (subset of TDMA frames) downlink DTX used/not used on uplink in previous frame Received signal level on BCCH of up to 6 neighbor cells (downlink) BCCH RF channel number of up to 6 neighbor cells (downlink)
Measurement RXLEV_DL_FULL RXLEV_DL_SUB RXQUAL_DL_FULL RXQUAL_DL_SUB DTX_USED RXLEV_NCELL(1..6)
BCCH_FREQ_NCELL_(1...6) 0 - 31 BSIC_NCELL (1...6)
0-7 (NCC) Base Station Identity Code of up to 6 0-7 (BCC) neighbor cells (downlink) Parameter format:NCC-BCC 0 - 63 0 - 63 0-7 0-7 0 - 35 Km Received signal level on TCH/SDCCH (full set of TDMA frames) uplink Received signal level on TCH (subset of TDMA frames) uplink Received signal quality on TCH/SDCCH (full set of TDMA frames) uplink Received signal quality on TCH (subset of TDMA frames) uplink Absolute MS-BS distance
RXLEV_UL_FULL RXLEV_UL_SUB RXQUAL_UL_FULL RXQUAL_UL_SUB MS_BS_DIST
A30808-X5226-C559-1-7618
3-13
Siemens
Handover
2.3
l
Measurement Reporting and Neighbor Cell BookKeeping
The MS needs the BCCH frequency of each neighbor cell n: Absolute Radio Frequency Carrier Number BCCH_ARFCN_NCELL(n). The MS reports to the BTSE the level measured on a certain ARFCN(n) together with the relative BCCH frequency number BCCH_FREQ_NCELL_(n). The MS also decodes the Base Station Identity Code BSIC(n). Different neighbor cells n1 and n2 which use the same BCCH frequency ARFCN(n1) = ARFCN(n2) have to have different Base Station Identity Codes. BSIC NCC: BCC: = NCC - BCC National Color Code (3 bits) Base Station Color Code (3 bits), has to be chosen by the network operator in accordance with rule given above.
l l
3-14
A30808-X5226-C559-1-7618
Handover
Siemens
Example Neighbor Cell 1 2 3 4 5 6 7 8 ARFCN_NCELL 4 4 11 18 25 32 39 39 BCC 1 2 1 1 1 3 2 4 BCCH_FREQ_NCELL 0 0 1 2 3 4 5 5
BCCH_FREQ_NCELL(n) and BSIC(n) CI_NCELL(n)uniquely !
A30808-X5226-C559-1-7618
3-15
Siemens
Handover
Measurement Report by MS reporting of the strongest cells with known and allowed BSIC; maximum: 6 cells BCC 1 2 3 4 1 BCC_FREQ _NC NELL 1 0 4 5 2 Book-Keeping at BS Neighbor Cell 1 2 3 4 5 6 7 8 ARFCN 4 4 11 18 25 32 39 39 BCC 1 2 1 1 1 3 2 4 For not reported neighbor cells RXLEV_NCELL is set to 0 RXLEV_NCEL L (n) 48 37 36 29 27 each SACCHMultiframe
BCCH_FREQ_ RXLEV_NCEL NCELL L (n) 0 0 1 2 3 4 5 5 0 37 48 27 0 36 0 29
Fig. 3
3-16
A30808-X5226-C559-1-7618
Handover
Siemens
The parameters for measurement reporting and cell book keeping are summarized in the table below. Specification Name CI_NELL MCC + MNC + LAC + CI ARFCN_NCELL /ADJC DB Name / Object CELLGLID Range 4 CHAR + 4 CHAR + 1...65535 + 0...65535 BCCHFREQ 0...1023 /ADJC BSIC = NCC - BCC /ADJC BSIC 0...7 0...7 Base station identity code consisting of national color code and base station color code. Neighbor cell measurements are identified using the BSIC and the relative frequency number of the BCCH. The MS includes only received level values of those cells within the measurement report which are defined as cells of a permitted PLMN. Absolute radio frequency channel number of the BCCH frequency of the neighbor cell. Meaning Global cell identifier of the adjacent cell consisting of mobile country code, mobile network code, location area identifier and cell identity
PLMN_ PERMITTED
PLMNP /BTSB
0...255 8 bits
A30808-X5226-C559-1-7618
3-17
Siemens
Handover
2.4
Illustration of Measurement Preprocessing
The measured (and reported) data per SACCH multiframe are preprocessed within the BTSE using a gliding average window. The size of the window can be set separately for RXQUAL, RXLEV, DIST and PBGT. The measured RXLEV_FULL/SUB or RXQUAL_FULL/SUB values are put into the gliding window with a multiplicity (weight) given by the parameter W_LEV_HO or W_QUAL_HO, respectively.
DTX enabled: Averaging of RXLEV Example: Average of RXLEV with a gliding window of size and a weight factor of the full values of A_LEV_HO = 4 W_LEV_HO = 2 .
average value = 27 Gliding Window 32 27 27 23 29 29 21
28
31
32
27
23
29
21
Measurement Values each SACCH Multiframe (0.48 s)
RXLEV_SUB (weight 1)
RXLEV_FULL (weight 2)
Fig. 4 Illustration of weighting and averaging of measurement values
3-18
A30808-X5226-C559-1-7618
Handover
Siemens
2.5
Parameters for Measurement Preprocessing
The parameters for measurement preprocessing for handover are administered in the object HAND and are listed in the table below.
DB Name
Range (default)
Meaning
HOAVQUAL AQUALHO
1-31 (8)
Averaging window size for RXQUAL values, used for handover decisions due to RXQUAL Weighting factor for RXQUAL_FULL values Averaging window size for RXLEV values, used for handover decisions due to RXLEV Weighting factor for RXLEV_FULL values Averaging window size for Timing Advance values used for handover decisions due to distance. Averaging window size used for power budget calculation.
HOAVQUAL WQUALHO HOAVELEV ALEVHO
1-3 (2) 1-31 (8)
HOAVELEV WLEVHO HOAVDIST
1-3 (1) 1-31 (8)
HOAVPWRB
1-31 (10)
A30808-X5226-C559-1-7618
3-19
Siemens
Handover
2.6
Remarks
The adjustment of the averaging window size mainly depends on the change of the radio propagation conditions:
Example:
l l l
path loss (change of 3 dB at a distance of 2000m): MS movement of ~400 m long term fading change of 6 dB: short term fading: MS movement of ~5...100 m MS movement of ~0.15 m
Hence, at the cell border the main variation of the received level is due to long and short term fading. Within one SACCH multiframe a MS moves: 0.5 m 5.0 m for MS speed = 1 m/s = 3.6 km/h for MS speed = 10 m/s = 36 km/h
Using an averaging window size of 10 SACCH frames, short term fading is averaged for pedestrians (as well as for fast moving MS). Long term fading is partly averaged for fast moving MS (the degree of averaging depends on the exact speed and the correlation length of long term fading, whereas there is nearly no averaging of long term fading for pedestrians. The setting of the averaging window size has to be a compromise between a fast decision and a reliable decision. Therefore it is recommended to use a larger window size for the optional handover (better cell) to do not cause a lot of unnecessary handovers and a smaller window size for the mandatory handover causes (quality, level, distance) to be able to react quickly on a sudden decrease of link quality.
3-20
A30808-X5226-C559-1-7618
Handover
Siemens
3
3.1
Threshold Comparisons and Handover Detection Algorithms

Decision Criteria
The standard handover algorithm for radio criteria uses the decision criteria listed in the table below. These criteria will be modified for a speed sensitive handover used within hierarchical cells. Handover Types Intercell HO due to Quality Decision Criteria 1. RXQUAL_XX > L_RXQUAL_XX_H 2. RXLEV_XX < L_RXLEV_XX_IH 3. XX_TXPWR = Min (XX_TXPWR_MAX, P) HO due to Level HO due to Distance HO due to Power Budget 1. RXLEV_XX < L_RXLEV_XX_H 2. XX_TXPWR = Min (XX_TXPWR_MAX, P) 1. MS_BS_DIST > MS_RANGE_MAX 1. RXLEV_NCELL(n) > RXLEV_MIN(n) + Max (0, MS_TXPWR_MAX(n) - P) 2. PBGT(n) > HO_MARGIN(n) Intracell HO due to Quality 1. RXQUAL_XX > L_RXQUAL_XX_H 2. RXLEV_XX > L_RXLEV_XX_IH
Notes:
l l l l l
XX: MS_TXPWR_MAX:
used as variable for both UL (uplink) and DL (downlink) maximum allowed transmit power of the MS in the serving cell,
MS_TXPWR_MAX(n): maximum allowed transmit power of the MS in the adjacent cell n P [dBm]: the maximum power capability of the MS (power class) An intercell handover due quality or level is only performed if the transmit power of the MS or BS respectively is on its maximum
A30808-X5226-C559-1-7618
3-21
Siemens
Handover
3.2
Handover Regions
RXQUAL
L_RXLEV_XX_IH
7 Intercell HO due to quality Intracell HO due to quality L_RXQUAL_XX_H
Intercell HO due to level
no handover action due to quality or level
RXLEV 0 63
L_RXLEV_XX_H
Fig. 5 Regions of handover defined by quality and level thresholds
3-22
A30808-X5226-C559-1-7618
Handover
Siemens
3.3
Power Budget
The power budget PBGT(n) is calculated in the following way: PBGT(n) = RXLEV_NCELL(n) - (RXLEV_DL + PWR_C_D) + Min(MS_TXPWR_MAX, P) - Min(MS_TXPWR_MAX(n), P)
RXLEV_DL: PWR_C_D:
averaged value of the measured downlink level in the serving cell, BS_TXPWR_MAX [dBm] - BS_TXPWR [dBm] averaged difference between the maximum downlink RF power BS_TXPWR_MAX and the actual downlink power BS_TXPWR due to power control in the serving cell.
RXLEV_NCELL(n): averaged value of the measured downlink level of the adjacent cell n HO_MARGIN(n): handover margin; if path loss with respect to the serving cell exceeds the path loss with respect to the adjacent cell n by this margin, the adjacent cell is considered as the (much) better cell.
A30808-X5226-C559-1-7618
3-23
Siemens
Handover
3.4
Parameters for Handover Decision

DB Name / (Object) HOLTHQUDL HOLTHQUUL (HAND) (6) Range (Default) 0...7 Thresholds for downlink/uplink quality. If RXQUAL is above these thresholds, the received level is low and the transmit power has reached its maximum, a quality intercell handover is initiated. Thresholds for downlink/uplink level. If RXLEV is below these thresholds and the transmit power has reached its maximum a level handover is initiated. If the measured timing advance value is above this threshold, a distance handover is initiated. If the quality falls below a threshold, but the received level is high, higher than L_RXLEV_XX_IH, an intracell handover is initiated. Meaning
Specification Name L_RXQUAL_DL_H L_RXQUAL_UL_H
L_RXLEV_DL_H L_RXLEV_UL_H
HOLTHLVDL HOLTHLVUL (HAND)
0...63 (10) (5) 0...35 Km (35) 0...63 (20)
MS_RANGE_MAX
HOTMSRM (HAND) HOTDLINT HOTULINT (HAND) MSTXPMX (BTSB)
L_RXLEV_DL_IH L_RXLEV_UL_IH
MS_TXPWR_MAX
MS_TXPWR_MAX (n)
MSTXPMAXCL (ADJC)
RXLEV_MIN(n)
RXLEVMIN (ADJC)
HO_MARGIN(n)
HOM (ADJC)
Maximum TXPWR a MS is allowed to use in the serving cell. * 2 dB 0 = 43 dBm, 19 = 5 dBm (GSM) 0 = 30 dBm, 15 = 0 dBm (DCS) 0...19 Maximum TXPWR a MS is allowed to use in the neighbor cell n * 2 dB 0 =43 dBm, 19 = 5 dBm (GSM) 0 = 30 dBm, 15 = 0 dBm (DCS) 0...63 The level received from a neighbor cell n has to exceed this threshold - to initiate a better cell handover to that neighbor cell - to include this cell in the target cell (20) list for a mandatory handover 0...126 The path loss difference between - 63... serving and adjacent cell has to + 63 dB exceed this margin for a better cell handover. (69)
0...19
3-24
A30808-X5226-C559-1-7618
Handover
Siemens
3.5
Priorities of Handover Causes
On TCHs it is possible that the condition for more than one handover cause is fulfilled. Therefore it is necessary to rank the evaluation of handover causes. On SDCCH where only one cause is evaluated, no ranking is necessary. Static ranking is performed according a priority list. Priority 1 2 3 4 5 6 Handover Cause Extended Cell Handover Concentric Cell Handover Quality Intercell Handover Level Handover Distance Handover Power Budget Handover Quality Intracell Handover Forced Handover intercell intercell intercell intercell intracell intercell imperative imperative imperative normal imperative forced TCH TCH TCH TCH TCH SDCCH HO type intracell HO class imperative evaluated on TCH
Handover Causes Priorities
A30808-X5226-C559-1-7618
3-25
Siemens
Handover
3.6
Limitation of Intracell Handover Repetition
In a situation, where for a connection in an interfered cell consecutive intracell handovers are performed without improving the quality of the connection (especially if frequency hopping is active), further intracell handovers should be avoided. In BR4.0, the operator has the possibility to handle this situation with new parameters, which have been introduced: Parameter ELIMITCH Range: TRUE, FALSE Default: FALSE TINOIERCHO Range: 1-254 Default: 60 MAIRACHO Range: 1-15 Default: 10 HAND This parameter defines the maximum number of intracell handovers, before further intracell handovers are prohibited. HAND This parameter defines the time in seconds, how long an intracell handover is prohibited. Location HAND Meaning This parameter enables the operator to switch on or off the feature of intracell handover limitation.
The following configuration rule should be regarded: TINOIERCHO (BTS timer) > THORQST (BTS timer) > T7 (BSC timer).
This condition allows the possibility to perform an intercell handover.
3-26
A30808-X5226-C559-1-7618
Handover
Siemens
TRX:0
TRX:4
TRX:1
BTS
TRX:3
TRX:2
Fig. 6 Limitation of intracell handovers
A30808-X5226-C559-1-7618
3-27
Siemens
Handover
3.7
Prevention of Back-Handover
In specific cases back handovers, i.e. handovers to a cell just left before, should be avoided. Two different reasons for the first of the two handovers have to be distinguished:
l
Imperative Handover If an imperative handover occurs, i.e. a handover due to bad quality, excessive distance or low signal level, then a back handover should be avoided if the reason for this second handover is the power budget.
Forced Handover In case of a forced handover, e.g. after a directed retry, a back handover should be avoided only, if the reason for this second handover is the power budget. Up to BR3.7, every back handover was prohibited for a time defined with the parameter TIMERFHO. Since BR4.0 this timer refers only to handovers due to power budget.
DB Name NOBAKHO Range: TRUE, FALSE Default: FALSE TINHBAKHO Range: 1-254 Default: 30 TIMERFHO Range: 0-320 Default: 12
Object HAND
Meaning This parameter enables the operator to switch on or off the feature of back handover prevention. This parameter defines the time in seconds, how long a power budget back handover is prohibited to a cell just left with an imperative handover. This parameter defines the time in 10 seconds intervals, how long a power budget back handover is prohibited to a cell just left with a forced handover.
ADJC
ADJC
3-28
A30808-X5226-C559-1-7618
Handover
Siemens
Imperative HO BTS-0 Power Budget HO

TINBACKHO
Fig. 7 Prevention of Power budget back handover for time TINBAKHO.
BTS-1
Forced HO BTS-0 Power Budget HO

T_FHO
Fig. 8 Prevention of Power budget back handover for time T_FHO.
BTS-1
A30808-X5226-C559-1-7618
3-29
Siemens
Handover
3.8
Limitation of Handover Failure Repetition
After consecutive handover failures further handovers towards the same cell should be avoided. For this reason the BSC informs the BTS after a number of subsequent Intra-BSC handover failures to exclude the cell from the target cell list. New parameters have been introduced in BR4.0 to enable or disable this feature, to define the maximum number of handover failures and the time period for which a cell is not seen as target for handover. Parameter NOFREPHO Range: TRUE, FALSE Default: FALSE TINHFAIHO Range: 1-254 Default: 5 MAXFAILHO Range: 1-15 Default: 4 HAND This parameter defines the maximum number of handover attempts, before a cell is removed from the target cell list. ADJC This parameter defines the time in seconds, how long a cell is removed from the target cell list after a sequence of handover failures. Object HAND Meaning This parameter enables the operator to switch on or off the feature of handover failure repetition prevention.
The following configuration rule should be regarded: TINHFAIHO (BTS timer) > THORQST (BTS timer) > T7 (BSC timer).
This condition allows the possibility to perform the handover towards the second cell indicated in the target cell list.
3-30
A30808-X5226-C559-1-7618
Handover
Siemens
1 2 3 4
BTS-0
... MAXFAILHO
BTS-1
TINFAILHO
Fig. 9 Concept of handover failure repetition prevention.
A30808-X5226-C559-1-7618
3-31
Siemens
Handover
3.9
Remarks
For adjusting the handover thresholds two scenarios are distinguished: Scenario A Noise Limited Scenario:
Large cells (in rural area) with low traffic load: received level at the cell border is not much above the receiver limit sensitivity level. Scenario B Interference Limited Scenario:
Small cells (in urban area) with high traffic load: received level at cell border significantly exceeds the receiver sensitivity level, but C/I is not much above the reference interference sensitivity. In any case intercell handover due to quality should be avoided as far as possible. Therefore:
l l
set L_RXQUAL_XX_H to highest value for acceptable speech quality, set L_RXLEV_XX_IH to a high value so that in case of low RXQUAL an intracell handover is initiated for the locations within the cell area defined by the other thresholds.
Scenario A: In this scenario the main handover criterion is the level criterion and L_RXLEV_XX_H has to be set to a value just some dB above the receiver limit sensitivity level. Furthermore, there should be a hysteresis between the threshold RXLEV_MIN for incoming handover and the corresponding threshold L_RXLEV_XX_H for outgoing handover to avoid a lot of unnecessary forward and backward handover: RXLEV_MIN - L_RXLEV_XX_H = level hysteresis > 0. The order of magnitude for the level hysteresis is given by the standard deviation of the long term fading, i.e. RXLEV_MIN > L_RXLEV_XX_H + 4 ... 10 dB.
3-32
A30808-X5226-C559-1-7618
Handover
Siemens
Scenario B: In this scenario the better cell criterion should be the main handover criterion, because
l l
it is the most suitable criterion for designing well defined cell borders, it guarantees that the mobile is served by the cell with (nearly) the lowest path loss and therefore offers the greatest potential for power control to reduce interference.
To avoid a lot of unnecessary forward and backward power budget handover caused by long term fading fluctuations of the received levels from the respective BTS, a hysteresis has to be introduced: HO_MARGIN(cell1 -> cell2) + HO_MARGIN(cell2 -> cell1) = power budget hysteresis > 0.
Usually, the handover margin is chosen symmetrically; its value should be a compromise between ideal power budget handover (low value) and a low rate of forward and backward handovers (high value) By choosing unsymmetrical values for the handover margin, one can adapt the cell area to the traffic load, e.g. increasing HO_MARGIN(cell1 -> cell2) while keeping the power budget hysteresis constant (i.e. reducing HO_MARGIN(cell2 -> cell1) by the same amount), increases the effective area of cell 1 while reducing that of cell 2. RXLEV_MIN(n) should be set to a value so that RXLEV_NCELL(n) > RXLEV_MIN(n) for almost all locations where PBGT(n) > HO_MARGIN(n), i.e. a better cell handover is really initiated if the power budget condition is fulfilled. This means that there should be an overlap of the outgoing power budget area of one cell and the incoming RXLEV_MIN area of the neighbor cell n. Furthermore, as for scenario A, there should be a level hysteresis between RXLEV_MIN and L_RXLEV_XX_H.
A30808-X5226-C559-1-7618
3-33
Siemens
Handover
RXLEV_MIN
L_RXLEV_XX_H
BT S1
BT S2
BT S3 ideal power budget cell border
Fig. 10 Cell borders defined by handover thresholds.
3-34
A30808-X5226-C559-1-7618
Handover
Siemens
L_RXLEV_XX_IH (inter / intracell quality HO)
BTS
RXLEV_MIN (incoming HO) L_RXLEV_XX_H (outgoing level HO)
receiver limit sensitivity
Fig. 11 Relation between handover level thresholds
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
A30808-X5226-C559-1-7618
3-35
Siemens
Handover
Target Cell List Generation
If the BTSE detects a handover cause it generates a target cell list. This list contains possible handover candidates that means neighbor cells to where the call can be handed over. The cells in the target cell list are given by their Cell Global Identifier. The maximum number of cells to be included in the target cell list is given by the parameter N_CELL (Parameter NCELL in object HAND, Range: 0 ... 15).
4.1
Conditions for Neighbor Cells to be included in the Target Cell List
Only those neighbor cells are included in the target cell list which fulfill the following conditions:
l
for Quality, Level and Distance Intercell Handover: RXLEV_NCELL(n) > RXLEV_MIN(n) + MAX(0, MS_TXPWR_MAX(n) - P)
for Power Budget Handover: RXLEV_NCELL(n) > RXLEV_MIN(n) + MAX(0, MS_TXPWR_MAX(n) - P) & PBGT(n) - HO_MARGIN(n) > 0
4.2
Order Criterion for Handover Candidate Cells within the Target Cell List
The ranking of the target cells in the target cell list is performed on the basis of the power budget minus handover margin value: PRIO_NCELL(n) = PBGT(n) - HO_MARGIN(n) PBGT(n): averaged value of the power budget The cell with the highest PRIO_NCELL(n) value will be listed first.
3-36
A30808-X5226-C559-1-7618
Handover
Siemens
4.3
Evaluation of the Target Cell List
Intracell Handover: A HO Condition Indication message with cause Intracell HO without target cell list is sent from the BTSE to the BSC. The BSC selects the new channel for the call within the same BTSE.
Intercell Handover A HO Condition Indication message containing the HO cause and the target cell list is sent from the BTSE to the BSC. If the first cell within the target cell list is within its BSS area, the BSC selects a channel at the corresponding BTS. If no channel is available at that BTS, the next cell within the target cell is tried. If the first target cell (or the ones tried in further steps) does not belong to the own BSS area, a Handover Required message is sent to the MSC. This message contains a reduced target cell list (without the cells tried internally).
A30808-X5226-C559-1-7618
3-37
Siemens
Handover
Illustrated of Target Cell Evaluation
BTS
BSC
MSC
Handover Detection
yes HO Cond Ind - cause - target cell list
no Handover Failure
next cell available yes yes next cell external no select channel HO Required - cause - reduced target cell list
yes Channel Activation
channel available no try next cell
Fig. 12
3-38
A30808-X5226-C559-1-7618
Handover
Siemens
Handover Signaling and Timer

MS BTSE serving Measurement Rep . Measurement Rep . HO Condition Ind. T_HAND_REQ T7 HO Command T8 HO Condition Ind. HO Access HO Access T3124 HO Required HO Required HO Request HO Request Ack. BSC serving MSC BSS target
HO Command
HO Command
. .
HO Detect Physical Info. T3105 Physical Info.
HO Complete
NY 1
HO Failure Channel Release Channel Release HO Complete
messages for successful handover, e.g. messages at timer expiry, e.g.
HO Required HO Failure
Fig. 13 Example for the signaling of a handover
A30808-X5226-C559-1-7618
3-39
Siemens
Handover
5.1
T3105 Object BTS
Parameters and Timers for Handover Signaling
Package BTST
DB Name T3105
Range unit * (0...255)
Step Size 1
Unit MS10 = 10 msec
Purpose: Start: Stop: Action expiry: Default:
period for repetition of PHYSICAL INFORMATION sending of PHYSICAL INFORMATION by BTS reception of correctly decoded signaling or TCH frame on new channel from MS at BTS repetition of PHYSICAL INFORMATION; if the maximum number of repetitions has been reached: release of new channel MS10-10
T3124 - MS Timer, not adjustable by database parameter Purpose: Start: Stop: Action expiry: Default: detect the lack of answer from the network at handover access. sending of first HANDOVER ACCESS by MS reception of PHYSICAL INFORMATION by MS deactivation of new channel, reactivation of old channel, send HANDOVER FAILURE 675 msec
3-40
A30808-X5226-C559-1-7618
Handover
Siemens
T_HAND_REQ Object HAND Package DB Name THORQST Range 0...31 Step Size 1 Unit 2 * SACCH multiframe
Purpose: Start: Stop:
minimum time for HANDOVER CONDITION INDICATION messages for the same connection sending of HANDOVER CONDITION INDICATION by BTS HANDOVER COMMAND received reason for handover has disappeared communication with MS is lost transaction has ended, call cleared
Action expiry: Default:
repetition of HANDOVER CONDITION INDICATION 5
T7 Object BSC Package BSCT DB Name BSCT7 Range unit * (0...255) Step Size 1 Unit HLFSEC = 0.5 sec MS100 = 100 msec SEC5 = 5 sec
Purpose: Start: Stop:
minimum time for HANDOVER REQUIRED messages for the same connection sending of HANDOVER REQUIRED by BSC - HANDOVER COMMAND received - reason for handover has disappeared - communication with MS is lost - transaction has ended, call cleared
Action expiry: Default:
repetition of HANDOVER REQUIRED HLFSEC-4
A30808-X5226-C559-1-7618
3-41
Siemens
Handover
T8 Object BSC Package BSCT DB Name BSCT8 Range unit * (0...255) Step Size 1 Unit HLFSEC = 0.5 secMS100 = 100 msecSEC5 = 5 sec
Purpose: Start: Stop: Action expiry: Default:
keep the old channel sufficient long to be able to return to it, and to release the channels if the MS is lost reception of HANDOVER COMMAND at BSC reception of CLEAR COMMAND from MSC or HANDOVER FAILURE from MS at BTS release of old channels HLFSEC-20
NY1 Object BTS Package BTSC DB Name NY1 Range 0...254 Step Size 1 Unit -
NY1 is the maximum number of repetitions of the physical information by the BTS. Default: 20
3-42
A30808-X5226-C559-1-7618
Handover
Siemens
Preemption, Directed Retry, Queuing
Preemption, directed retry, and queuing allows to assign a TCH when, due to the unavailability of resources, no unused channel can be found within the serving cell:
l l l
Preemption is a means of providing TCH resources for high priority TCH requests. Directed Retry is the handover from a SDCCH in one cell to a TCH in another cell. Queuing allows the queuing of TCH requests on a per cell and priority basis.
In case of unavailability of resources, two cases can be distinguished (assignment request and handover request): In case of an Assignment Request, preemption is tried first: The BSC looks for a call in the cell with a priority lower than the new TCH request and, then moves the lower priority call to another cell performing a forced handover (or a forced release if HO fails) in order to free the TCH. The free TCH is then assigned to the new request. If no call with a lower priority is using a TCH or a call with the same priority or higher is already waiting (queued) Directed Retry is performed. If still no free TCH is available, the queuing procedure is carried out, storing the TCH request in the cell queue based on their priority. In case of Handover Request, preemption is tried first. If preemption is not successful, the directed retry procedure will be skipped and queuing is carried out. The preemption feature gives the operator the possibility to differentiate subscriptions per user class (e.g. different contracts for high priority classes such as police and other emergency organizations, business people etc.) Queuing and directed retry improve the network access and, in general, the network QOS.
A30808-X5226-C559-1-7618
3-43
Siemens
Handover
6.1
Parameters for Preemption and Queuing
EN_PREEMPTION The parameter Enable Preemption is used to enable/disable the preemption feature. Object BTS Package BTSO DB Name EPRE Range ENABLED DISABLED Step Size Unit -
EN_QUEUEING The parameter Enable Queuing is used to enable/disable the queuing feature: Object BTS Package BTSO DB Name EQ Range ENABLED DISABLED Step Size Unit -
QUEUEING_LENGTH The parameter Queuing Length defines the maximum number of TCH requests that can be queued in the cell. Object BTS Package BTSO DB Name QL Range 1...100 Step Size 1 Unit
3-44
A30808-X5226-C559-1-7618
Handover
Siemens
T11 The timer T11 defines the maximum queuing time for an ASS_REQ: Object BSC Package DB Name BSCT BSCT11 Range unit * (0...255) Step Size 1 Unit MS100 = 100 msec HLFSEC = 0.5 sec SEC5 = 5 sec
Start: Stop: Action e xpiry: Default:
ASS_REQ is queued, BSC sends QUEUE_IND to MSC TCH becomes free for assignment or the request is replaced by an other request with higher priority. remove ASS_REQ from queue, send CLEAR_REQ to MSC HLFSEC-16
Tqho The timer Tqho defines the maximum queuing time for HO_REQ: Object BSC Package DB Name BSCT Range Step Size 1 Unit MS100 = 100 msec HLFSEC = 0.5 sec SEC5 = 5 sec
BSCTQHO unit * (0...255)
Start: Stop: Action e xpiry: Default:
HO_REQ is queued, BSC sends QUEUE_IND to MSC TCH becomes free for assignment or the request is replaced by an other request with higher priority. remove HO_REQ from queue, send HO_FAIL to MSC HLFSEC-20
A30808-X5226-C559-1-7618
3-45
Siemens
Handover
GSM supports the prioritization of calls using 14 priority levels: A priority level and a queuing allowed indicator is attached to each TCH request in the (optional) priority information element within the assignment request or handover request message The priority information element is organized in the following way: Bit 8 Spare Bit 7 PCI Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 QA Bit 1 PVI
PRIORITY LEVEL
The PCI (preemption capability indicator) indicates whether or not the preemption shall be applied. The PRIORITY LEVEL contains the priority of the call; GSM supports the prioritization of calls using 14 priority levels (1 is the highest and 14 is the lowest priority). The QA (queuing allowed indicator) is used to decide on a per call basis whether or not queuing shall be applied. The PVI (preemption vulnerability indicator) applies for the entire duration of a connection and indicates whether or not this connection might be preempted by another allocation request (i.e. may become a target of preemption).
The entire procedure is shown in the following figures. These flowcharts basically indicate which algorithms and which checks are necessary in which network entity (BTSE, BSC or MSC) and the message flow that has to be conveyed between the networks entities. It can be seen that, in the best case, an assignment of a TCH in a neighbor cell takes place.
3-46
A30808-X5226-C559-1-7618
Handover
Siemens
Flowchart of Preemption
ASS_REQ / HO_REQ (no TCH available)
Does the message N contain the priority I.E.? Y Directed Retry Procedure (see flowchart) N PCI = 1 ? Y Y Other queued calls with PCI=1 and higher or equal priority ? N N Other active call with PVI=1 and lower PL Y
Set PCI=0, PVI=0, QA=1, PL=14
Send Forced Handover for the lower PL call
Successful ? Y
Forced Release of the lower PL call
BSC assigns the free TCH
Fig. 14
A30808-X5226-C559-1-7618
3-47
Siemens
Handover
6.2
Directed Retry
Directed retry is the transition (handover) from a SDCCH in one cell to a TCH in another cell during call setup because of unavailability of an empty TCH within the first cell. Directed retry is a means to control the traffic distribution between cells and to avoid a call rejection because of congestion in one cell. If Queuing of ASS REQs is not supported within a BSC Directed retry is merely triggered by the BSC by sending a Forced HO Request message to the BTS which has to respond with a "initiated" Intercell HO Cond. Indic. message. It can happen that the Intercell HO Cond. Indic. message does contain only an empty target cell list (If triggered by a Forced HO Request message the BTS has to send a Intercell HO Cond. Indic. message even if no suitable neighbor cell exists - in this case the target cell list is empty!). In this case a TCH can not be assigned and the BSC shall not send a HO RQD message to the MSC of course but shall send an ASS FAILURE (cause "no radio resource available"). If the target cell list contains cells from inside and outside the BSC area and if e.g. the first and second cell is inside, the third outside and the fourth inside the BSC area than the Directed retry attempts shall be carried out as BSC controlled Directed retries to the first and second one. If these Directed retries are not possible for any reason (e.g. no empty TCH) than the third attempt and all following attempts (independently whether the fourth and the following cells lie in- or outside the BSC area) shall be executed as MSC controlled Directed retry. If in case of a MSC controlled handover the MS cannot access the new cell and the MSC receives a HO FAILURE (cause "radio interface failure, reversion to old channel") from the old BSS, it can happen that the MSC generally releases this SDCCH connection by sending a CLEAR CMD message (cause "radio interface failure, reversion to old channel") to the BSC independently. If the MSC does not support Directed retry HOs the BSC may perform BSC controlled Directed retries (approximately 75% of all Directed retries) only. In this case the EN_INTER_SDCCH_HO flag in the BSC shall be set to "disabled" and the BSC has to check the target cell list of Intercell HO_Cond_Ind messages belonging to a SDCCH connection. All cell identifiers not belonging to the BSC area shall be skipped and if there remain cell identifiers belonging to the BSC area the corresponding HO shall be performed to strongest (if impossible to the second strongest, third strongest etc.) remaining cell. If the target cell list does not contain a remaining or any cell identifier of the same BSC area, this Intercell HO Cond. Indic. message shall be discarded and the BSC shall release this SDCCH connection (Sending of an ASS FAILURE with cause "no radio resource available").
3-48
A30808-X5226-C559-1-7618
Handover
Siemens
6.2.1
Flowchart of Directed Retry
Directed Retry Procedure
Is the incoming message an Assignment_REQ ? Y BSC sends to BTS Forced_HO_Request
BTS sends to BSC Intercell_HO_Cond_Ind with target cell list
Suiteble cell in list ? Y BSC assigns TCH internally and sends Assignmend_Complete to MSC Y Cell within BSC area ? N
Start Queueing Procedure
EN_INTER_SDCCH_HO set to enable ? Y Assign TCH Y Directed Retry towards MSC successful ?
Fig. 15
A30808-X5226-C559-1-7618
3-49
Siemens
Handover
6.2.2
HO Algorithm and Generation of the Target Cell List for Directed Retry
The BTS has to send the Intercell HO Cond. Indic. messages toward the BSC. For Directed retry the sending of an Intercell HO Cond. Indic. message for a SDCCH may only be triggered by a BTS external event: The BSC sends a Forced HO Request because of "no TCH available". If an Intercell HO Cond. Indic. message is to be sent, the target cell list shall contain all neighbor cells which fulfill the following condition: RXLEV > RXLEV_MIN + Max(0, MS_TXPWR_MAX-P) + FHO_RXLEV_MIN_OFFSET The ranking of the neighbor cells in the target cell list is performed in the order of decreasing values of: PBGT - HO_MARGIN Additional parameters specific to speed sensitive HO shall be taken into account for the ranking of the target cells. Even if no suitable neighbor cell exist, the BTS shall send an Intercell HO Cond. Indic. message. In this case the target cell list ("Cell Identif. List Pref. IE") shall be empty! The cause of the Intercell HO Cond. Indic. message shall be FORCED. FHO_RXLEV_MIN_OFFSET is a cell specific O&M-parameter to select only target cells for forced HO which the MS can access without any problems. It is a result of radio planning for each individual cell. It allows to influence the amount of Forced HOs failed because of empty target cell list, the amount of HO attempts back to the "old" cell and the success rate of HO ACCESSes to the target cell
3-50
A30808-X5226-C559-1-7618
Handover
Siemens
6.2.3
Prevention of Back-Handovers
A major general problem of forced HO (Directed retry is one sort of forced HO!) is the probability of HO due to PBGT back to the "old" (congested) cell. Its drawbacks are: 1. increased load at the Abis-interface because of periodic sending of Intercell HO_Cond_Ind messages in intervals of T7 2. increased load at the A-interface in case of inter-BSC-HO because of the same reason 3. additional processor capacity in BSC (and MSC) is required for HO trials for which it is known in advance that they are useless 4. the load in the congested cell will not be reduced for a certain time, but it will be kept at a permanent high level. For the Channel Activation message a new optional information element "Cell Identifier List (no target)" is defined. This information element contains the cell identifier (CI) of a cell from which a handover request (intra- or inter-BSC) because of forced HO was received. If this information element exists in the Channel Activation message, the BTS
l l
shall not trigger a (TCH-)HO due to PBGT for the time Tbho if the PBGT condition is fulfilled for the indicated cell only and shall not include the indicated CIs in the target cell list in this case for the time Tbho (i.e. for the condition HO due QUAL/LEV/DIST the indicated cell identifier may be part of the target cell list)
Tbho is a timer that limits the mentioned prohibitions. It has to be set by O&M command. If a HO is necessary the target BSC has to generate the Channel Activation message. The target BSC shall insert the Cell Identifier List (no target) IE into this message The BSC shall derive the CI for the Cell Identifier List (no target) IE from the stored context in case of intra BSC HO or from the mandatory Cell Identifier (serving) IE of the HO REQ message in case of inter BSC HO with cause "Directed retry".
A30808-X5226-C559-1-7618
3-51
Siemens
Handover
6.3
Object BSC
Parameters for Directed Retry

Package BSCB DB Name ENFORCHO Range ENABLE DISABLE Step Size Unit -
EN_FORCED_HO
This BSC specific O&M flag allows to enable/disable the sending of Forced HO Request messages for running SDCCH connections (e.g. queued or not queued ASS REQs which do not find an empty TCH). It is used to enable/disable Directed retry. This flag should be set to "disable" by an operator if in a network the MSC which the BSS is connected to or other adjacent BSS do not support the prevention of "backHO".
EN_INTER_SDCCH_HO Object BSC Package BSCB DB Name ESDCCHHO Range ENABLE DISABLE Step Size Unit -
This BSC specific O&M flag allows to enable/disable inter BSC SDCCH-HO (i.e. SDCCH-SDCCH-HO and Directed retry). It simply prevents the sending of HO RQD messages for SDCCH connections to the MSC. This flag should be set to disable by an operator if in the network the MSC to where the BSS is connected to or other adjacent BSS do not support the prevention of back-HO. If it set to disable the BSC shall skip all cell identifiers of the target cell list of the Intercell HO Cond. Ind message which belong to another BSC area.
3-52
A30808-X5226-C559-1-7618
Handover
Siemens
FHO_RXLEV_MIN_OFFSET Object ADJC Package DB Name FHORLMO Range 0...24 Step Size 1 Unit 1 dB
FHO_RXLEV_MIN_OFFSET ("RXLEV_MIN offset for forced-handover") is a cell specific O&M-parameter used within the BTS to select only target cells for forced HO which the MS can access without any problems. It is a result of radio planning for each individual cell. It allows to influence the amount of Forced HO failed because of empty target cell list, the amount of HO attempts back to the "old" cell and the success rate of HO ACCESSes to the target cell. Default: 6
Tbho Object ADJC Package DB Name TIMERFHO Range 1...320 Step Size 1 Unit 10 sec
Tbho (bho=back handover) is a network wide O&M parameter. It is the value of a timer running in the BTS that controls the duration how long a former serving cell from which forced HO was performed to the new serving cell may not be considered in the HO decision algorithm of the new serving cell and may not be contained in the target cell list. It is started at the reception of a Channel Activation message containing a Cell Identifier (no target) IE. Default: 12
A30808-X5226-C559-1-7618
3-53
Siemens
Handover
Handover related Performance Measurements
In a running network the handover performance can be monitored using the handover performance measurements. On the one hand, handovers are important for mobility and traffic distribution, on the other hand they are associated with a greater amount of signaling. The evaluation of the handover performance measurements enable weak points to be identified and corrected at an early stage:
l l
For example in a well planned network handovers with certain reasons should predominate those with other reasons. By measuring the number of handovers between cells, locations with greater or lesser handover activity can be localized. and also missing neighbor cell relations in the database can be found out. By varying handover threshold values it is possible to force traffic from highly frequented cells into cells which may be under less pressure earlier. A more uniform distribution of traffic can be achieved in this way.
3-54
A30808-X5226-C559-1-7618
Handover
Siemens
Handover Performance Measurements The following table summarizes the handover performance measurements: Measurement Type Abbreviation Functional group
Intracell Attempted internal Handovers, intracell, per cause Successful internal Handovers, intracell, per cause Unsuccessful internal Handovers, intracell Unsuccessful internal Handover, intracell, with loss of MS Intercell Attempted internal Handovers, intercell, per cause Successful internal Handovers, intercell, per cause Attempted incoming internal intercell Handovers per originating cell Successful incoming internal intercell Handovers per originating cell Attempted outgoing internal intercell Handovers per neighbor-cell relationship Successful outgoing internal intercell Handovers per neighbor-cell relationship Total number of Handover failures, intra BSC ATINHIRC SINTHINT AININIRH SININIRH AOUINIRH SOUINIRH HOFITABS BTSMEAS BTSMEAS BTSIHDOMEAS BTSIHDOMEAS BTSOHDOMEAS BTSOHDOMEAS BSCMEAS BTSMEAS ATINHIAC SINTHITA UNINHOIA UNIHIALC BTSMEAS BTSMEAS BTSMEAS BTSMEAS
Unsuccessful internal HOs, intercell, with UNINHOIE reconnection to the old channel, cause, per target cell Unsuccessful internal Handovers, intercell, UNIHIRLC with loss of MS
BTSMEAS
A30808-X5226-C559-1-7618
3-55
Siemens
Handover
Inter BSC Attempted outgoing inter BSC Handovers per neighbor cell relationship Successful outgoing inter BSC Handovers per neighbor cell relationship Number of unsuccessful outgoing inter BSC Handovers per neighbor cell relationship Number of inter BSC Handover failures Others Successful internal Handovers per cause SINHOBSC BSCMEAS ATINBHDO BTSOHDOMEAS
SUINBHDO
BTSOHDOMEAS
NRUNINHD
BTSOHDOMEAS
NRINHDFL
BSCMEAS
3-56
A30808-X5226-C559-1-7618
Handover
Siemens
Queuing Performance measurements In the following table the queuing related performance measurements are summarized: Mean TCH queue length (Fullrate/Halfrate) Mean duration a TCH is queued (Fullrate/Halfrate) Number of messages discarded from the TCH queue per cell (Fullrate/Halfrate) MTCHQLEN MDURTCRQ NMSGDISQ BTSMEAS BTSMEAS BTSMEAS
Quality related performance measurement The performance measurement related to power and quality measurements is listed below: Power and quality measurements on uplink/downlink busy TCHs PWRUPDW CHANMEAS
A30808-X5226-C559-1-7618
3-57
Siemens
Handover
3-58
A30808-X5226-C559-1-7618
Handover
Siemens
Exercise
Exercise
Task 1
Is the handover algorithm strictly defined in GSM?
In which GSM recommendation can you find information about the handover process?
Color all the handover related parameters in the BSC database given in the appendix.
A30808-X5226-C559-1-7618
3-59
Siemens
Handover
Task 2
Are all handover performance measurements defined by GSM?
In which GSM recommendation can you find information about performance measurements? Fill in the meaning of the following key words: Keyword Scanner Meaning
Performance measurement
Counter
Trigger event
3-60
A30808-X5226-C559-1-7618
Siemens
Contents
1 2 2.1 2.2 2.3 2.4 3 4 4.1 4.2 4.3 4.4 4.5 4.6 4.7 5 Channel Configuration Overview Control Channel Configuration Dedicated Channels Random Access Channel RACH Paging / Access Grant and Notification-Channel Parameters for Control Channel Configuration Extended Channel Mode Channel Configuration related Performance Measurements Flow of Messages between the Network Elements Immediate Assignment Procedure Paging Procedure Assignment Procedure Clearing Sequence Error Indication Channel (Configuration) related Performance Measurements Exercise 3 14 15 17 24 27 28 30 30 31 34 36 38 40 42 45
A30808-X5226-C559-1-7618
4- 1
Siemens
4-2
A30808-X5226-C559-1-7618
Siemens
Channel Configuration Overview
On the radio interface Um two subbands for the BTS-MS duplex connection are specified: Uplink UL 890 - 915 880 - 915 1710 - 1785 876 - 880 1850 - 1910 Downlink DL 935 - 960 925 - 960 1805 - 1880 921 - 925 1930 - 1990 MHz MHz MHz MHz MHz MS-BTS MHz MHz MHz MHz MHz P-GSM900 (primary band) E-GSM900 (extended band) DCS1800 GSM-R PCS1900 BTS-MS P-GSM900 (primary band) E-GSM900 (extended band) DCS1800 GSM-R PCS1900 ( BR 3.6) ( BR 3.6) ( >=BR 3.6) ( >=BR 3.6)
The radio frequency channel spacing in 200 kHz, allowing 124 RFC in P-GSM, 174 RFC in E-GSM, 374 in DCS, 19 RFC in GSM-R and 299 in PCS1900.
A30808-X5226-C559-1-7618
4- 3
Siemens
Within the database or within the protocol messages a carrier frequency is characterized by its absolute radio frequency channel number (ARFCN). Using the abbreviation n = ARFCN, there is the following relation between ARFCN and the frequency in MHz in the uplink Fu [MHz] and the downlink Fd [MHz]. P-GSM900 Fu(n) = 890 + 0.2 n 1 < n < 124 Fd(n) = Fu(n) + 45
E-GSM 960 Fu(n) = 890 + 0.2 n Fu(n) = 890 + 0.2 x (n -1024) DCS1800 GSM-R PCS1900 Fu(n) = 1710.2 + 0.2 x (n 512) Fu(n) = 876.2 + 0.2 x (n -955) Fu(n) = 1850.2 + 0.2 x (n 512)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
0< n < 124 Fd(n) = Fu(n) + 45 975 < n < 1023 512 < n < 885 955 < n < 974 512 < n < 810 Fd(n) = Fu(n) + 95 Fd(n) = Fu(n) + 45 Fd(n) = Fu(n) + 80
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A30808-X5226-C559-1-7618
Siemens
(880) 890 Mhz 1710 MHz UPLINK (UL) Transmit band of the mobile station
915 Mhz 1785 MHz
(925) 935 Mhz 1805 MHz DOWNLINK (DL)
960 Mhz 1880 MHz
GSM 900 DCS 1800
Transmit band of the base station
Duplex Distance 45 MHz resp. 95 MHz 25 (35) MHz 75 MHz Guard band not used 25 (35) MHz 75 MHz
C 1
C 2
C 3
C 124 (174) 374
C 1
C 2
C 3
C 124 (174) 374
200 kHz
C = radio frequency channel (RFC)
512...............885 DCS1800
975....1024 01...............124 GSM900 E-GSM900 ARFCN (Absolute RF channel number)
Fig. 1 Radio frequency channels RFC on Um
A30808-X5226-C559-1-7618
4- 5
Siemens
Each RFC offers 8 physical channels a time division multiplex access TDMA. The physical channels are subdivided into logical channels, divided in traffic channels and control channels according to GSM 04.03.
4 3 2 1 0 7 6 5 4 3 2 200 kHz 1 0 4,615 msec = 8 577 s
Fig. 2
4-6
A30808-X5226-C559-1-7618
Siemens
Speech Channels (Full/Half) Traffic Channels TCH Data Channels (Data Rate) Logical Channels Broadcast Control Channel BCCH
Control Channels CCH
Common Control Channel CCCH
Dedicated Control Channel DCCH
Fig. 3 Logical channels
A30808-X5226-C559-1-7618
4- 7
Siemens
Random Access Channel RACH
MS requests a dedicated channel from network
Access Grant Channel AGCH Common Control Channel CCCH Paging Channel PCH
answer to a random access, assignment of dedicated signaling channel
paging of a MS in all cells of a location area for a mobile terminating call
Notification Channel NCH
paging of MSs in all cells of a voice group call area to perform ASCI (Advanced Speech Call Items)
Fig. 4 The common control channels
4-8
A30808-X5226-C559-1-7618
Siemens
Frequency Correction Channel FCCH
identification of BCCH frequency, MS frequency synchronization
Synchronization Channel SCH Broadcast Control Channels BCCH Broadcast Control Channel BCCH
frame (time) synchronization, identification of neighbour cells (handover)
system information: cell identifier, cell parameter, channel configuration, cell frequencies, broadcast frequencies of neighbour cells
Cell Broadcast Channel CBCH
broadcast of short messages: traffic, weather, date, ... (no mobile system info)
Fig. 5 The broadcast control channels
A30808-X5226-C559-1-7618
4- 9
Siemens
out of band signaling channel for: Stand Alone call setup signaling, short message service Dedicated Control (SMS), location update (LUP), Channel SDCCH IMSI attach/detach
Dedicated Control Channel DCCH
Slow Associated Control Channel SACCH
in band signaling channel (periodic): downlink: system info, power command, TA; uplink: measurements (level quality), short messages service
Fast Associated Control Channel FACCH
in band signaling channel (sporadic): handover signaling channel mode modify: speech data
Fig. 6 The dedicated control channels
. . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
A30808-X5226-C559-1-7618
Siemens
Multiplexing of Logical Channels 1 physical channel (timeslot) can carry one of the following logical channel combinations: Channel Combination a) TCH / F + FAACH / F + SACCH / F b) TCH/H (0, 1) + FACCH/H (0, 1) + SACCH/H (0, 1) c) FCCH + SCH + BCCH + CCCH uplink: 800 000 RACH slots per hour downlink: 140 000 CCCH blocks per hour uplink: 400 000 RACH slots per hour downlink: 46 000 CCCH blocks per hour+ dedicated signaling channels for 4 subscribers dedicated signaling channels for 8 subscribers Capacity 1 full rate subscriber 2 half rate subscriber (speech or data)
d) FCCH + SCH + BCCH + CCCH + SDCCH / 4 (0...3) + SACCH / 4 (0...3)
e) SDCCH / 8 (0...7) + SACCH / 8 (0...7)...
1 RACH slot: 1 channel request message of 1 subscriber 1 CCCH block (4 slots): - 1 paging message for 1...4 subscribers or - 1 access grant message for 1...2 subscribers
A30808-X5226-C559-1-7618
4- 11
Siemens
Channel Organization in a Cell Since SBS BR2.1 the following channel combinations are allowed:
l l l l
TCH/F + FACCH/F + SACCH/F FCCH + SCH+ BCCH+ CCCH FCCH + SCH + BCCH + CCCH + 4 (SDCCH + SACCH) 8 (SDCCH + SACCH)
TCHFULL MAINBCCH MBCCHC SDCCH
Additional channel combinations since SBS BR3.0:

l
TCH/H (0,1) + FACCH/H (0,1) + SACCH/TH (0,1) or TCH/F + FACCH/F + SACCH/TF FCCH + SCH + BCCH + CCCH + 3 (SDCCH + SACCH) + CBCH 7 (SDCCH + SACCH) + CBCH BCCH + CCCH
TCHF_HLF BCBCH SCBCH CCCH
l l l
In a cell with a single RFC the allocation should be the following: Radio Timeslot 0 Radio Timeslot 1...7 FCCH+SCH + BCCH + CCCH + 4 (SDCCH + SACCH) TCH/F + FACCH/F + SACCH/F
The Radio Timeslot 0 runs in the 51 frame organization:
1. 2.
F S BCCH 0 1 2 3 4 5 F S BCCH 0 1 2 3 4 5
CCCH F S CCCH CCCH F S SDCCH0 SDCCH1 F S SDCCH2 SDCCH3 F S SACCH0 SACCH1 I 6 7 8 9 10 11 12 1 3 14 15 1 6 17 18 19 20 21 22 23 24 25 2 6 27 28 29 30 3 1 3 2 33 34 35 36 37 38 39 40 41 42 43 44 45 4 6 47 48 49 50 CCCH F S CCCH CCCH F S SDCCH0 SDCCH1 F S SDCCH2 SDCCH3 F S SACCH2 SACCH3 I 6 7 8 9 10 11 12 1 3 14 15 1 6 17 18 19 20 21 22 23 24 25 2 6 27 28 29 30 3 1 3 2 33 34 35 36 37 38 39 40 41 42 43 44 45 4 6 47 48 49 50
downlink BCCH + CCCH + 4 SDCCH / 4, F = FCCH, S = SCH
1. 2.
SDCCH3 R R SACCH2 0 1 2 3 4 5 6 7 8 9 SDCCH3 R R SACCH0 0 1 2 3 4 5 6 7 8 9
SACCH3 R R R R R R R R R R R R R R R R R R R R R R R SDCCH0 SDCCH1 R R SDCCH2 1 0 11 1213 14 15 1 6 17 18 19 20 21 22 23 24 25 26 27 28 2 9 30 31 32 33 34 35 3 6 37 38 39 4 0 41 42 43 44 45 4 6 47 48 49 50 SACCH1 R R R R R R R R R R R R R R R R R R R R R R R SDCCH0 SDCCH1 R R SDCCH2 1 0 11 1213 14 15 1 6 17 18 19 20 21 22 23 24 25 26 27 28 2 9 30 31 32 33 34 35 3 6 37 38 39 4 0 41 42 43 44 45 4 6 47 48 49 50
uplink R = RACH + SDCCH / 4
1 SACCH-Multiframe = 2 x 235,38 ms)

Fig. 7 1 frame = 235,38 msec
4-12
A30808-X5226-C559-1-7618
Siemens
The Radio Timeslots 1...7 run in the 26 frame organization In a cell with 2 RFC there are more possibilities, depending on the used traffic model [SDCCH dimensioning], for example: RFC-0 RFC-1 see cell with 1 TRX Timeslot 0...7 or Timeslot 0 Timeslot 1...7 8 (SDCCH + SACCH) TCH / F + FACCH / F + SACCH / F TCH / F + FACCH / F + SACCH / F
1 Full Rate TCH
26 frames = 120 ms
2 Half Rate TCH
T: t: A: a:
Traffic Channel Burst for Traffic Channel Burst for Slow Associated Control Slow Associated Control
subscriber 1 subscriber 2 Channel for subscriber 1 Channel for subscriber 2
Fig. 8 Time organization for one TCH
A30808-X5226-C559-1-7618
4- 13
Siemens
Control Channel Configuration
Introduction: In a MOC, MTC, LU the MS has to request an SDCCH using the RACH. There is a time delay between the request and the SDCCH allocation due to the traffic load. If there is a free SDCCH, it is allocated using the AGCH. The SDCCH is used for the authentication, transmission of cipher parameters and call initialization. Next a traffic channel is requested and allocated, if available. After this, the SDCCH is released. The MS acknowledges the allocation on the FACCH. The TCH with its FACCH and SACCH is occupied until the end of the call. So the blocking probability is a function of
l l l l
availability of SDCCH availability of TCH waiting time in TCH queue, if queuing performed (BTS parameter) time for connection establishment
4-14
A30808-X5226-C559-1-7618
Siemens
2.1
Dedicated Channels
If we evaluate a given traffic model, we find a certain traffic load per subscriber. Additionally we have to calculate the SDCCH load per subscriber. According to the traffic model there are four values to be considered:
l l l l
call attempts per subscriber per hour time for MOC/MTC setup signaling time for Location Update Location Updates per subscriber per hour
1.1 3 sec 5 sec 2.2
The SDCCH load per subscriber is calculated as follows: (1.1 * 3 sec + 2.2 * 5 sec) / 3600 sec = 0.004 Erl Furthermore we have for the TCH: 25 mErl
. . . . . . . . . . . . . . . . . . . . . . . . . . .
4
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
A30808-X5226-C559-1-7618
4- 15
Siemens
Example for Channel Configuration Assumptions: 25 mErl TCH Load per subscriber 4 mErl SDCCH load per subscriber no load problem on CCCH Cell with 2 TRX: 16 channels Configuration A
l l
Configuration B
l l l
1 comb. CCCH/SDCCH 4 SDCCH 15 TCH
uncomb. CCCH 1 SDCCH/8 8 SDCCH 14 TCH
offered TCH load at 1 % blocking 8.11 Erl Subscriber 8.11 / 0.025 = 324 offered SDCCH load at 1 % blocking 0.87 Erl Subscriber 0.87 / 0.004 = 218 SDCCH limited: 218 subscriber
offered TCH load at 1 % blocking 7.35 Erl Subscriber: 7.35 / 0.025 = 294 offered SDCCH load at 1 % blocking 3.13 Erl Subscriber: 3.13 / 0.004 = 782 TCH limited: 294 subscriber
Configuration B is the better one for this scenario
4-16
A30808-X5226-C559-1-7618
Siemens
2.2
Random Access Channel RACH
The RACH is used by the MS to request a dedicated channel, the SDCCH. The channel request needs one RACH timeslot. The cause for the channel request can be a paging response in MTC, an emergency call, a MOC, LU or IMSI attach/detach. The RACH is configured only uplink, his frequency corresponds to the downlink BCCH frequency. The RACH may be combined with the uplink part of the SDCCH. In the combined case, the RACH is multiplexed onto 27 timeslots 0 out of 51 of a BCCH combined. The RACH can also be configured uncombined on all timeslots 0, 2, 4, 6. This gives the following capacities, the frame duration is 4.6 ms (period between two successive timeslots 0): combined: uncombined: uncombined: uncombined: uncombined: 27/51 of all timeslots 0 timeslot 0 timeslot 0,2 timeslot 0,2,4 timeslot 0,2,4,6 => 400000 RACH slots per hour => 800000 RACH slots per hour => 1560000 RACH slots per hour => 2340000 RACH slots per hour => 3120000 RACH slots per hour
In a cell with 5000 subscriber normally there are about 20 000 RACH activities per hour only.
1. 2.
SDCCH3 0 1 2 3 SDCCH3 0 1 2 3
R 4 R 4
R SACCH2 SACCH3 5 6 7 8 9 1 0 11 1213 R SACCH0 SACCH1 5 6 7 8 9 1 0 11 1213
R 14 R 14
R 15 R 15
R 16 R 16
R 17 R 17
R 18 R 18
R 19 R 19
R 20 R 20
R 21 R 21
R 22 R 22
R 23 R 23
R 24 R 24
R 25 R 25
R 26 R 26
R 27 R 27
R 28 R 28
R 29 R 29
R 30 R 30
R 31 R 31
R 32 R 32
R 33 R 33
R 34 R 34
R 35 R 35
R SDCCH0 SDCCH1 36 37 38 3 9 40 41 42 4 3 44 SDCCH1 R SDCCH0 36 37 38 3 9 40 41 42 4 3 44
R 45 R 45
R SDCCH2 46 47 48 49 5 0 R SDCCH2 46 47 48 49 5 0
uplink R = RACH + SDCCH / 4
Fig. 9
A30808-X5226-C559-1-7618
4- 17
Siemens
2.2.1
l
RACH Control Parameter
The MS receives the RACH control parameters from the base station on the BCCH : Maximum number of retransmission (max_retrans) MAXRETR = 1, 2, 4, 7 If a channel request is not acknowledged by the base station, the MS repeats the request until the given value of MAXRETR.
l
Number of slots to spread transmissions (tx_integer) NSLOTST = 0,..15 representing the real values
of 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 14, 16, 20, 25, 32, 50 This value determines the time period between sending of two channel requests. This period is measured in RACH slots and is the sum of a deterministic part td and a random part tr: The deterministic part td of retransmission period as a function of tx_integer is given in the following table: MS Phase 1 tx_integer ----3, 8, 14, 50 4, 9, 16 Phase 2 5, 10, 20 6, 11, 25 7, 12, 32 td (RACH slots, combined) 41 (0.35 sec) 41 (0.35 sec) 52 (0.45 sec) 58 (0.50 sec) 86 (0.75 sec) 115 (1.00 sec) td (RACH slots, uncombined) 55 (0.25 sec) 55 (0.25 sec) 76 (0.35 sec) 109 (0.50 sec) 163(0.75 sec) 217(1.00 sec)
4-18
A30808-X5226-C559-1-7618
Siemens
The random part tr is an integer between 1 and tx_integer where the probability of choosing a certain time slot i is given by : p ( tr = i ) = 1 / tx_integer for i = 1...tx_integer
retransmission
td = 163 slots
first transmission with a collision
tr = tx_integer = 6
Fig. 10
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
4
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 19
A30808-X5226-C559-1-7618
Siemens
Immediate Assignment Procedure: The procedure is specified in GSM 04.08:
IMMEDIATE ASSIGNMENT PROCEDURE Select RACH slot for first transmission number of retransmissions = 0 Send CHANNEL REQUEST msg.
no.of retransmissions = max _retrans
set timer T3126 wait for grant
GRANT during Sup. time
N Select RACH slot for next transmission, wait for grant
Y CELL RESELECTION
inmediate assignment
Y Y
Rejection N number of retransmissions + 1 N SDCCH Allocation
WAIT T3122
Fig. 11 Immediate Assignment Procedure
4-20
A30808-X5226-C559-1-7618
Siemens
2.2.2
Evaluation of Immediate Assignment Procedure for Different Parameter Values
Traffic Load / RACH activities per hour The relative traffic load is the average number of initiated immediate assignment procedures or RACH activities in a timeslot: traffic load = total number of immediate assignment procedures / total number of RACH slots The absolute number of RACH activities per hour is obtained by multiplying this relative load with the number of RACH slots per hour.
Blocking The blocking shows the percentage of not successful immediate assignment procedures initialized by the MS. blocking [%] = (number of unsucc. imm. ass. proc. / total number of imm. ass. Proc. ) * 100
Throughput The channel throughput is the average number of successful transmissions per time slot. throughput = number of successful transmissions / number of simulated time slots throughput = ( 1 - blocking ) * traffic load
Wait Time The wait time is the time between the initiation of the immediate assignment procedure and the arrival of the immediate assignment message. For the waiting time it is useful to consider the 90% quantile of the wait time: for 90% of the immediate assignment procedures, the wait time is less than the time t90. The blocking and the 90% (95%) quantile for different values of the RACH control parameters is shown in the following tables for a combined RACH/SDCCH:
A30808-X5226-C559-1-7618
4- 21
Siemens
tx_integer 3 3 3 3 7 7 7 7 14 14 14 14 25 25 25 25 50 50 50 50
max_retrans blocking(%) 1 2 4 7 1 2 4 7 1 2 4 7 1 2 4 7 1 2 4 7 2.9 1.1 0.2 < 0.01 1.6 0.4 0.1 < 0.01 0.9 0.1 < 0.01 < 0.01 0.6 < 0.1 < 0.01 < 0.01 0.5 0.1 < 0.01 < 0.01
90% quantile(s) < 0.1 < 0.1 < 0.1 < 0.1 < 0.1 < 0.1 < 0.1 < 0.1 < 0.1 < 0.1 < 0.1 < 0.1 < 0.1 < 0.1 < 0.1 < 0.1 < 0.1 < 0.1 < 0.1 < 0.1
95% quantile(s) 0.35 0.35 0.35 0.4 1.0 1.0 1.0 1.0 0.4 0.4 0.4 0.4 0.8 0.8 0.8 0.8 0.5 0.5 0.5 0.5
Values for 25000 RACH activities per hour
4-22
A30808-X5226-C559-1-7618
Siemens
tx_integer 3 3 3 3 7 7 7 7 14 14 14 14 25 25 25 25 50 50 50 50
max_retrans blocking(%) 1 2 4 7 1 2 4 7 1 2 4 7 1 2 4 7 1 2 4 7 6.1 2.8 0.6 0.1 3.6 1.0 0.1 < 0.1 2.6 0.5 < 0.1 < 0.01 2.0 0.4 < 0.01 < 0.01 1.8 0.2 < 0.01 < 0.01
90% quantile(s) 0.35 0.35 0.35 0.35 1.0 1.0 1.0 1.0 0.4 0.4 0.4 0.4 0.8 0.8 0.8 0.8 0.5 0.5 0.5 0.5
95% quantile(s)
0.75 0.75 0.75 1.1 1.1 1.1 1.1 0.45 0.45 0.45 0.45 0.9 0.9 0.9 0.9 0.7 0.7 0.7 0.7
Values for 50000 RACH activities per hour The results of these studies show, that even the RACH minimal configuration (combined RACH/SDCCH is able to serve 50000 RACH activities per hour at a low blocking (< 0.5%) with an acceptable wait time. An uncombined RACH is able to serve twice the traffic load with the same grade of service. The minimum blocking for the considered traffic load is achieved by the following setting of parameters: max_retrans = 7, tx_integer = 50. Though a combined RACH can serve the expected traffic load, another RACH configuration may have to be chosen. The RACH is only the uplink part of the CCCH. The downlink parts (AGCH,PCH) may need a higher capacity. Therefore, the configuration of CCCH is determined by the capacity needed by the downlink channels, the RACH configuration is uncritical.
A30808-X5226-C559-1-7618
4- 23
Siemens
2.3
Paging / Access Grant and Notification-Channel
PCH/AGCH The paging channel and the access grant channel share the same TDMA frame mapping (modulo 51) when combined onto a basic physical channel. The channels are shared on a block by block basis. The information within each block allows the MS to determine if it is a paging or an access grant message. Every paging channel can be used by the system as access grant channel but it is not allowed to the system to use access grant channels as paging channels. However, to ensure a mobile a satisfactory access to the system, there is a control parameter to define a fixed number of access grant blocks in the 51 multiframe. The number of blocks reserved for AGCH is broadcasted on the BCH. The number of available paging blocks is reduced by this number. Paging channels may be used as access grant channels but not vice versa. Therefore it is useful to set the parameter BS_AG_BLKS_RES to the smallest value and let the system organize the use of channels. In case of MOC more AGCH are needed, in case of MTC more PCH are needed. In average the number of MOC is higher than the number of MTC. If the BS_AG_BLKS_RES value is set too high with the result of a PCH shortage, a overload indication for the PCH may arise in high traffic time. In GSM traffic model the paging per subscriber per hour is 0.93. The second parameter to be set is called BS_PA_MFRMS ( value = 2..9, number of multiframes between paging). It indicates the number of TDMA multiframes between transmission of paging messages to the same paging subgroup. The MS gets the information on BCH, to which paging groups it should listen to. By this way the MS can save battery because it only listens to its own paging group. If the value is too high so that the time between two blocks of the same paging sub-channel is high, the time for setting up an MTC is high. In a medium cell the common channel pattern on timeslot 0 on one of the TRX can use the following combination downlink (in uplink all channels are used as RACH): FSBBBBPPPPFSPPPPPPPPFSPPPPPPPPFSPPPPPPPPFSPPPPPPPP F = FCCH S = SCH B = BCCH P = PACH/AGCH. An example for the load and the servable number of subscribers is given at the following pages.
4-24
A30808-X5226-C559-1-7618
Siemens
NCH In all cells where the ASCI service is enabled, a new logical channel belonging to CCCH is defined, this new downlink channel is the Notification Channel (NCH). A MS which is VBS/VGCS* subscriber, besides the paging blocks, monitors also the Notification Channel. This logical channel is mapped onto contiguous blocks reserved for access grants, the position and the number of blocks are defined by the two parameters NCH_FIRST_BLOCK and NCH_BLOCK_NUMBER. Service subscribers are notified of the VBS/VGCS call in each cell via notification messages that are broadcasted on the Notification Channel; these messages dont use individually TMSI/IMSI but the group identity and service area identity. The process of broadcasting messages on NCH is carried out throughout the call in order to provide late entry facility. The repetition time is defined by the parameter TIMER_NCH. * Voice Broadcast Service / Voice Group Call Service
CCCH Load
paging messages per hour: random messages per hour:
SUBSCR * LA_size * MTC_ph * REPET / subscr_per_pag_message SUBSCR * (MTC_PR_ph + MOC_ph + LU_ph + IMSI_ph + SMS_ph)
access grant messages per hour: SUBSCR * (MTC_PR_ph + MOC_ph + LU_ph + IMSI_ph + SMS_ph) / subscr_per_agch_message SUBSCR LA_size MTC_ph REPET MTC_PR_ph MOC_ph LU_ph IMSI_ph SMS_ph number of subscribers within the cell number of cells on the location area mobile terminating calls per subscriber per hour (with and without paging response) mean number of repetitions of a paging message (no paging response to first paging) mobile terminating calls per subscriber per hour with paging response to first paging) mobile originating calls per subscriber per hour location updates per subscriber per hour IMSI attach/detach per subscriber per hour short message service requests per subscriber per hour
A30808-X5226-C559-1-7618
4- 25
Siemens
CCCH Load (Example)
paging messages per hour:
SUBSCR * LA_size * MTC_ph * REPET / subscr_per_pag_message
access grant messages per hour: SUBSCR * (MTC_PR_ph + MOC_ph + LU_ph + IMSI_ph + SMS_ph) / subscr_per_agch_message random messages per hour: SUBSCR * (MTC_PR_ph + MOC_ph + LU_ph + IMSI_ph + SMS_ph)
SUBSCR: LA_size: MTC_ph: REPET: MOC_ph LU_ph IMSI_ph SMS_ph
? 20 0.46 1.33 0.64 2.2 1.0 -
MTC_PR_ph0.30
subscr_per_pag_message = 2 subscr_per_agch_message = 1.0

l l
paging messages per hour = SUBSCR * 20 * 0.46 * 1.33 / 2 ~ SUBSCR * 6 / h access grant messages per hour ~ SUBSCR * 4 / h ~ SUBSCR * 10 / h paging + access grant messages ~ 4600 subscriber (combined CCCH) ~ 14000 subscriber (uncombined CCCH)
random access messages per hour ~ SUBSCR * 4 / h (at 10 % load) ~ 10000 subscriber (combined CCCH) ~ 20000 subscriber (uncombined CCCH)
4-26
A30808-X5226-C559-1-7618
Siemens
2.4
Parameters for Control Channel Configuration

Object/ Package CHAN DB Name CHTYPE Range Meaning
Specification Name CH_TYPE
TCHFULL channel type SDCCH MAINBCCH MBCCHC CCCH SCBCH BCBCH TCHF_HLF ONE TWO FOUR SEVEN 0...15 maximum number of allowed retransmissions of a channel request on the RACH number of RACH slots to spread re-transmission of channel request; also fixing the deterministic part of wait time 0 ... 15 = 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 14, 16, 20, 25, 32, 50 number of common control blocks per multiframe used for access grant exclusively number of multiframes between paging blocks belonging to the same paging sub-channel indicates the first block of downlink CCCH to be used for NCH number of downlink CCCH blocks to be used for NCH repetition period for notification messages defined in steps of one multiframe period 235 ms
MAX_RETRANS BTS/BTSC
MAXRETR
TX_INTEGER
BTS/BTSC
NSLOTST
BS_AG_BLKS_R BTS/BTSC ES
NBLKACGR 0...7 0...2 for comb. CCCH NFRAMEPG 2...9
BS_PA_MFRMS BTS/BTSC
NCH_FIRST_BL BTS/BTSC OCK NCH_BLOCK_NU BTS/BTSC MBER TIMER_NCH BTS/BTST
NOCHFBLK 1...7
NOCHBLKN 1...4 TNOCH 1...254
A30808-X5226-C559-1-7618
4- 27
Siemens
Extended Channel Mode
In a normal GSM standard cell the maximum MS-BTS distance is 35 km; this is the limit given by the maximum TA (timing advance 0...63 bit) which is possible on one radio timeslot. Distance calculation: Dist = TA * bit-period * light-speed / 2 bit-period = 48/13 (3.69) s light-speed = 300000 km/s. The feature Extended Cells supports a larger distance between MS and BTS by using two subsequent radio timeslots to compensate the longer delay of the bursts. The first timeslot of a double timeslot has always an even number (0,2,4,6), the following corresponding channel must not be created. For a double timeslot the maximum propagation delay can be 219 bit ( 120 km), but note that the maximum distance which can be configured by O&M is 100 km. The BTS splits the propagation delay into two values:
l l
timing advance (TA), covering the first 63 bit delay timing offset (TO), used for extended cells as an offset to TA for delays greater 63 bit (the propagation delay is the algebraic sum of TA and TO).
When activating the SDCCH and later the TCH for that corresponding MS, the evaluated initial TA value forms part of the layer 1 header downlink, the initial TO is used BTS-internally. If the average of the deviation exceeds 1 bit period (48/13 s) in comparison to the TA confirmed by the MS (contained in every uplink SACCH header information), the previously ordered TA is incremented/decremented by one and sent as new ordered TA in the layer 1 header downlink to MS. As previously mentioned TA cannot exceed 63 bit. TO is used internally for processing further delay in case of extended cells. Note that TO may only be greater then 0 when TA has the maximum value 63. In extended cells all control and signaling channels must be defined in extended (double) mode.
4-28
A30808-X5226-C559-1-7618
Siemens
Parameters for Extended Cell Configuration Specification Name CELL_TYPE Object/ Package BTS/BTSB DB Name Range Meaning
CELLTYPE STDCELL maximum range UMBCELL 35 km a cell covering EXTCELL other cells maximum range 100 km EXTMODE TRUE FALSE defines if a channel is used in extended mode or not
EXTENDED_MODE CHAN
A30808-X5226-C559-1-7618
4- 29
Siemens
4
4.1
Channel Configuration related Performance Measurements

Flow of Messages between the Network Elements
The scanners gather data by adapting the counters assigned to them at certain events. These events are messages which are exchanged between the network elements (NE) on different occasions (call setup, handover, location update etc.). This chapter describes the most important procedures during which data is collected for measurements on the air-interface.
4-30
A30808-X5226-C559-1-7618
Siemens
4.2
Immediate Assignment Procedure
The immediate assignment procedure is used to create a signaling connection between the MS and the network. It can be initiated only by the MS. The reason for this may be:
l l l l
response to a PAGING REQUEST message location update call setup etc.
With a CHANNEL REQUEST message on the RACH the MS signals the BTS that it requires a signaling channel (SDCCH). This message contains the information field establishment cause and random reference. The establishment cause gives the reason why the MS is requesting a SDCCH. Possible reasons are:
l l l l l l l
emergency call call re-establishment answer to paging originating speech call originating data call location updating other procedures which can be completed with an SDCCH
The BTS forwards the request to the BSC with a CHANNEL REQUIRED message. The BSC selects a free SDCCH and instructs the BTS with a CHANNEL ACTIVation message to activate it. If the SDCCH is successfully activated, the BTS responds with a CHANNEL ACTIVE ACKnowledge message. If not, it sends a CHANNEL ACTIVNegativeACKnolwedge message. A channel activation may fail for the following reasons:
l l l l
O&M intervention (channel blocked) channel already occupied hardware fault etc.
The BSC then sends the BTS an IMMEDIATE ASSignment CoMmanD message containing an IMMEDIATE ASSIGNMENT or (if there is a failure) an IMMEDIATE ASSignment REJect message, which is forwarded to the MS.
A30808-X5226-C559-1-7618
4- 31
Siemens
If the BTS is not able to send the IMMEDIATE ASSIGNMENT message due to the Access Grant Channel (AGCH) being overloaded, it notifies the BSC of this with a DELETE INDICATION message. When the MS receives the IMMEDIATE ASSIGNMENT message, it switches to the assigned channel and activates it. By sending an SABM frame containing a Service Request Message, it switches the SDCCH to the Multiple Frame Acknowledge mode, thereby activating it. The Service Request message helps the network to recognize the service being requested by the MS. This information is used to decide how to proceed. Service request messages are:
l l l l l
CM SERVICE REQUEST LOCATION UPDATING REQUEST IMSI DETACH PAGING RESPONSE CM REESTABLISHMENT REQUEST
The BTS sends confirmation to the MS that it has received the service by means of a UA frame containing the service request message received. It informs the BSC with an ESTABLISH INDICATION message which also contains the service request message. Further coordination procedures (authentication, ciphering etc.) are now performed on the SDCCH.
4-32
A30808-X5226-C559-1-7618
Siemens
MS CHANNEL REQUEST
BTS
BSC
CHANNEL REQUIRED
CHANNEL ACTIV
CHANNEL ACTIV ACK
CHANNEL ACTIV. NEG. ACK
IMMEDIATE ASS CMD IMMEDIATE ASSIGNMENT
SABM
UA ESTABLISH INDICATION
Fig. 12 Immediate assignment procedure
. . . . . . . . . . . . . . . . . . . .
4
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . 4- 33
A30808-X5226-C559-1-7618
Siemens
4.3
Paging Procedure
The paging procedure is used to inform the mobile station (MS) that a connection set up is being requested. The MSC sends the BSC a PAGING message which contains the identity (IMSI or TMSI) and the location area of the MS. The BSC then generates a PAGING COMMAND message which it transmits to all the BTSs in the location area. If a BTS contains a PAGING COMMAND message, it transmits a PAGING REQUEST message on the paging channel (PCH). The PAGING REQUEST message contains the identity of the MS to which it is directed. An MS which receives a PAGING REQUEST message checks whether it is the subscriber being called. If this is the case, it initiates an immediate assignment procedure (-> 1.3.1) to occupy an SDCCH. When the SDCCH is occupied, the BSC sends a CONNECTION REQUEST and COMPLETE LAYER 3 INFORMATION message to the MSC.
4-34
A30808-X5226-C559-1-7618
Siemens
MS
BTS
BSC PAGING PAGING COMMAND
MSC
PAGING REQUEST CHANNEL REQUEST
CHANNEL REQUIRED IMMEDIATE ASS CMD
IMMEDIATE ASSIGNMENT SABM (PAGING RESPONSE) UA (PAGING RESPONSE) ESTABLISH INDICATION CONNECTION REQUEST COMPLETE LAYER 3 INFO
Fig. 13 Paging and immediate assignment procedure
. . . . . . . . . . . . . . . . . . . . . . . . . .
4
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . 4- 35
A30808-X5226-C559-1-7618
Siemens
4.4
Assignment Procedure
The assignment procedure is used to occupy a radio resource (e.g. speech channel) if it is required by an MS. Prior to this, the MS receives information on the SDCCH which enables the MSC to receive all the data required to set up the connection. The MSC now sends an ASSIGNMENT REQUEST message to the BSC requesting the assignment of a radio resource (RR). The ASSIGNMENT REQUEST message contains information on the requested channel (channel type (speech/data/signal), priority, interference band to be used etc.) which is to be evaluated by the BSC. Based on this data, the BSC selects a suitable RR and activates it (CHAN ACTIV). It then instructs the MS with an ASSIGNMENT COMMAND message to occupy the channels. When the MS receives the ASSIGNMENT COMMAND message it switches to the assigned channels and activates them by sending an SABM frame. The BTS acknowledges receipt of the SABM frame with a UA frame to the MS and informs the BSC with an ESTablishment INDication message that the MS has occupied the channels. When the MS receives the UA frame, it sends an ASSIGNMENT COMPLETE message to the BSC. If the assignment procedure was initiated by the MSC (the BSC can also initiate the procedure independently for an intracell handover), the BSC informs the MSC with an ASSIGNMENT COMPLETE message that the procedure has been successful.
4-36
A30808-X5226-C559-1-7618
Siemens
MS
BTS
BSC
MSC
ASSIGNMENT REQUEST CHANNEL ACTIV CHANNEL ACTIV ACK CHANNEL ACTIV NEG. ACK ASSIGNMENT COMMAND SABM UA ASSIGNMENT COMPLETE ASSIGNMENT COMPLETE ASSIGNMENT FAILURE
Fig. 14 Assignment procedure
. . . . . . . . . . . . . . . . . . . . . . . . . .
4
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . 4- 37
A30808-X5226-C559-1-7618
Siemens
4.5
Clearing Sequence
The clearing sequence is used to release radio resources and associated terrestrial channels. The MSC initiates the sequence with a CLEAR COMMAND to the BSC. Once the CLEAR COMMAND message is received, the BSC returns a CLEAR COMPLETE message to the MSC, which then releases the related terrestrial channels. The BSC instructs the MS to release the occupied mobile channels with a CHANNEL RELEASE on the FACCH at the same time as the CLEAR COMPLETE message is sent to the MSC. A DEACTIVATE SACCH message is sent to the BTS to deactivate the signaling channel. Timer T3109 is started in the BTS by sending the CHANNEL RELEASE message. T3109 is stopped if the MS displays the release of the SACCH with a DISC message. If the T3109 stops without a DISC message being received, the BSS deactivates all the channels connected to the MS. When the CHANNEL RELEASE message is received the MS starts Timer T3110, deactivates the SACCH and reports this to the BTS with a DISConnect message. Timer T3110 is stopped if the BTS sends a UA frame to confirm the DISC message. If the MS receives no confirmation while T3110 is running, it considers the connection to be ended and releases the remaining channels. T3110 should be less than T3109 so that the MS always releases the channels before the BTS. (Standard: T3109 = 8 s, T3110 = 1.5 s) The BTS acknowledges the reception of the DISC message with a UA frame to the MS, informs the BSC with a RELease INDication message and starts Timer T3111. (Standard: T3111 = 1.5 s) After releasing the UA frame the MS releases all the remaining channels and goes into idle mode. When T3111 expires, the BSC instructs the BTS with a RadioFrequence CHANnel RELease message to release the channels already deactivated by the MS. After release, the BTS acknowledges this with an RF CHAN REL ACKnowledge message. A clearing sequence can be triggered e.g. by the call ending as normal, a handover, the end of a location update or the aborting of a connection. In the latter case the BSC is informed of this by a CONNection FAILure INDication message, which it uses as an opportunity to request the MSC with a CLEAR REQUEST to introduce a clearing sequence.
4-38
A30808-X5226-C559-1-7618
Siemens
MS
BTS (CONN FAIL IND)
BSC
MSC
(CLEAR REQUEST) CLEAR COMMAND T3110 T3109 DEACTIVATE SACCH DISC T3111 UA REL IND RF CHAN REL T1 RF CHAN REL ACK CLEAR COMPLETE CHANNEL RELEASE
Fig. 15 Clearing sequence
. . . . . . . . . . . . . . . . . . . . . . . . . .
4
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . 4- 39
A30808-X5226-C559-1-7618
Siemens
4.6
Error Indication
By sending an ERROR INDication message to the BSC the BTS informs it of an unexpected incident occurring on the air-interface. The ERROR IND message contains the reason for the error in the RLM cause field. Incidents which result in an ERROR IND message are:
l l
protocol errors link layer errors (e.g. repetition of an I frame N200 times without confirmation) After sending the I frame, confirmation is expected within the duration of T200 (UA frame). If no confirmation is received in this period, the I frame is repeated a maximum of N200 times (maximum number of retransmissions).
l l
repetition of an SABM or DISC frame N200 times without confirmation receipt of an SABM frame in the multi-frame established state
4-40
A30808-X5226-C559-1-7618
Siemens
MS
BTS
BSC
ERROR IND
Fig. 16 Error Indication message
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 41
A30808-X5226-C559-1-7618
Siemens
4.7
Channel (Configuration) related Performance Measurements
The following table summarizes the channel (configuration) related performance measurements: Measurement Type Abbreviation Functional group
TCH / TCH Connection related measurements Number of available TCH (Fullrate/Halfrate) NAVTCH BTSMEAS BTSMEAS BTSMEAS BTSMEAS BTSMEAS BTSMEAS
Mean number of busy TCH MEBUSTCH (Fullrate/Halfrate) Attempted TCH seizures (Fullrate/Halfrate) Successful TCH seizures (Fullrate/Halfrate) Mean TCH busy time (Fullrate/Halfrate) Total number of TCH connections, per cell (Fullrate/Halfrate) ATTCHSEI SUCTCHSE MTCHBUTI TNTCHCL
All available TCH allocated AALTCHTI time Number of lost radio links while using a TCH (Fullrate/Halfrate) Attempted TCH seizures meeting a TCH blocked state (Fullrate/Halfrate) NRFLTCH
BTSMEAS BTSMEAS
ATCHSMBS
BTSMEAS
4-42
A30808-X5226-C559-1-7618
Siemens
SDCCH / SDCCH Connection related measurements Number of available SDCCH Mean number of busy SDCCH Maximum number of busy SDCCH per cell Number of attempted SDCCH seizures in a period Attempted SDCCH seizures meeting an SDCCH blocked state All available SDCCH allocated time Number of lost radio links while using an SDCCH NAVSDCCH MBUSYSDC MAXBUSDC NATTSDPE BTSMEAS BTSMEAS BTSMEAS BTSMEAS
ATSDCMBS
BTSMEAS
ASDCALTI NRFLSDCC
BTSMEAS BTSMEAS
CCCH related measurements Total number of accesses by procedures (PCH, AGCH) TACCBPRO BTSMEAS
Number of accesses with a NACSUCPR successful result by procedure (PCH, AGCH and RACH)
BTSMEAS
A30808-X5226-C559-1-7618
4- 43
Siemens
Immediate assignment measurements Attempted immediate assignment procedures, per cause Successful immediate assignment procedures, per cause Successful immediate assignments of signaling channels per cause ATIMASCA BTSMEAS
SUIMASCA
BTSMEAS
NSUCCHPC
BTSMEAS
Assignment procedure measurements Total number of assignment attempts per cell per channel type TASSATT BTSMEAS
Total number of successful TASSSUCC assignments per cell per channel type ASCI connection related measurements Total number of assignment attempts relevant to VBS/VGCS Broadcast/Group Channels, per cell TASSATVS
BTSMEAS
BTSMEAS
Total number of successful TASSUCVS assignments relevant to VBS/VGCS Broadcast/Group Channels, per cell Number of new notifications to be sent on the Notification Channel (NCH) NNNOTNCH
BTSMEAS
BTSMEAS
4-44
A30808-X5226-C559-1-7618
Siemens
Exercise
Exercise
Task 1 What is a physical channel and what is a logical channel?
In which GSM recommendation can you find further information about logical channels?
Color all parameters which have been discussed in this chapter in your BSC database given in the appendix.
A30808-X5226-C559-1-7618
4- 45
Siemens
4-46
A30808-X5226-C559-1-7618
Siemens
Contents
1 2 2.1 3 3.1 3.2 3.3 4 4.1 4.2 5 5.1 5.2 6 6.1 6.2 7 Introduction Mobile Speed Sensitive Handover Relevant Parameters in BSC Database Priority Layers General Remarks Relevant Parameters in BSC Database Influence of Priorities on Cell Ranking Concentric Cells Introduction to Concentric Cells Relevant Parameters in BSC Database Extended Cells Introduction to Extended Cells Relevant Parameters in BSC Database Call Release for Excessive Distance Introduction to Call Release for Excessive Distance Relevant Parameters in BSC Database Exercise 3 7 8 12 12 15 18 20 20 22 29 30 32 36 37 38 40
A30808-X5226-C559-1-7618
5-1
Siemens
5-2
A30808-X5226-C559-1-7618
Siemens
Introduction
The capacity of a mobile radio network is given by the number of radio channels NTCH per unit area A, e.g. per km2:
NTCH N 1 = CPF x total x A K CA

where Ntotal: K: CA: CPF: total number of frequencies for the radio network, cluster size, cell area, channels per frequency.
Hence, there are two possibilities to increase the network capacity:

l l
to increase the number of channels per BTS by decreasing the cluster size, to increase the density of BTS locations, i.e. to use smaller cells.
To give an example, reducing the cell radius from 1000 m to 100 m reduces the cell area by factor 100. Hence, the number of channels per area is increased by the same factor 100. This illustrates the huge potential of micro cells. But this extremely high capacity is not expected to be needed all over the radio network, but only in certain regions.
For example:
l l
Hot Spots as Railway Station, Airport or a Shopping Mall which can be covered by a small number of micro cells (1 ... 10), City Center covered by about 100 micro cells.
Due to economical reasons micro cells are intended to be served by cheaper and smaller BTS (Micro BTS) which are easy to install with antennas installed below the roof top level, especially for the second scenario with a large number of micro cells. Nevertheless, in principle it is possible to install very small cells (also called micro cells in the following sections) for hot spot coverage (scenario 1) using classical BTS. Micro cells shall be embedded in an (existing) overlayer network of (conventional) macro cells. A network consisting of (at least) two layers of cells of different dimensions (macro micro cells) is called a Hierarchical Cell Structure.
A30808-X5226-C559-1-7618
5-3
Siemens
The overlayer macro cells are needed for the following reasons:
l l l
to achieve a global coverage, to serve as a rescue cell in the case of a rapid decrease of link quality (road corner effect), to serve fast moving MS.
Additionally, the macro cell can be used

l l
to serve overflow traffic load from the micro cells (all channels busy within the micro cells), as a redundancy cell in case of a failure of a micro cell BTS.
Advantages of HCS
=> Serving fast moving mobiles by macro cells reduces the handover rate => significant reduction of call drop probability => significant reduction of unnecessary handover signaling load
Hierarchical Cell Structure Upper layer: umbrella cells

l l l l
high transmit power antenna above roof top level global coverage basically handles high speed mobile
Lower layer: micro cells

l l l l
low transmit power antenna below roof top level coverage of regions of high traffic load basically handles low speed mobile
5-4
A30808-X5226-C559-1-7618
Siemens
l l l
indoor coverage by an outdoor BTS; mobiles passing that BTS on the street are served by the umbrella cell; a parking lot served by a micro cell; a busy street canyon served by a chain of micro cells; in this example micro cells are assumed to have a radius of 200 m (along the busy street) and to serve pedestrians (~ 1 m/s = 3.6 km/h) as well as mobiles with a speed up to about 10 m/s = 36 km/h; mobiles moving in side road are served by the umbrella cell; they shall be kept in the umbrella cell when they cross the busy street canyon (no handover into the micro cell); this illustrates that whether to serve a mobile by the micro or macro cell is not matter of absolute mobile speed, but of mobile speed relative to the dimension of the micro cell, i.e. the criterion for serving a mobile by a micro cell should be the expected duration of stay within the respective micro cell.
This criterion is used for the Cell Selection mechanism for phase 2 MS (idle mode) as well as for the Mobile Speed Sensitive Handover. It should be noted that the Mobile Speed Handover works properly for both phase 1 and phase 2 MS: Phase 2 mobiles already set up a call in the correct layer and the handover algorithm keeps them in that layer (as long as they do not change their speed); phase1 MS may set up the call in the wrong layer, but the handover algorithm will force them to the correct layer after some seconds.
A30808-X5226-C559-1-7618
5-5
Siemens
Umbrella Cell GSM900 Radio Coverage Layer 5
Macro Cell GSM900 Radio Coverage Layer 4
Small Cell GSM900/1800 Radio Coverage Layer 3 Micro Cell GSM900 Radio Coverage Layer 2
Pico Cell GSM900/1800 Radio Coverage Layer 1
Fig. 1
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
5-6
A30808-X5226-C559-1-7618
Siemens
2
l l
Mobile Speed Sensitive Handover

by introducing timers T(n) for each connection in a cell and each handover candidate micro cell n (analogous to the timers defined for cell selection of phase 2 MS) and by using a time dependent handover margin for the better cell criterion.
Mobile speed sensitivity is achieved
The timer is started if both of the following conditions are fulfilled: RXLEV_NCELL(n) > RXLEV_MIN(n) + Max(0, MS_TXPWR_MAX(n) - P ) PBGT(n) > HO_MARGIN(n) (T1) (T2)
After each SACCH frame in which these conditions are fulfilled the timer is incremented by 1. If one of these conditions is not fulfilled the timer is reset to 0.
A better cell handover is initiated if PBGT(n) > HO_MARGIN_TIME(n) where the time dependent handover margin is given by HO_MARGIN_TIME(n) = HO_MARGIN(n) + HO_STATIC_OFFSET(n) for T(n) < DELAY_TIME(n) (HOM1) (BC)
HO_MARGIN_TIME(n) = HO_MARGIN(n) + HO_STATIC_OFFSET(n) - HO_DYNAMIC_OFFSET(n) for T(n)>= DELAY_TIME(n) (HOM2)
A30808-X5226-C559-1-7618
5-7
Siemens
2.1
Relevant Parameters in BSC Database
EN_PBGTD_HO Flag to enable (TRUE) and disable (FALSE) the mobile speed sensitive handover algorithm. Object HAND Package DB Name DPBGTHO Range TRUE/FALSE Step Size Unit -
HO_STATIC_OFFSET HO_STATIC_OFFSET is added to the handover margin of those neighbor cells of the lower layer structure whose timer has not yet been started or is still running. A high value of HO_STATIC_OFFSET effectively prevents a handover into the respective cell during the runtime of the timer for that cell. Object ADJC Package DB Name HOMSOFF Range 0...127 Step Size 1 Unit dB
5-8
A30808-X5226-C559-1-7618
Siemens
HO_DYNAMIC_OFFSET For those neighbor cells of the lower layer structure, whose timer has expired , the handover margin is reduced by HO_DYNAMIC_OFFSET, i.e. corresponding handover margin is given by HO_MARGIN_TIME(n) = HO_MARGIN(n) + HO_STATIC_OFFSET(n) HO_DYNAMIC_OFFSET(n). This is the margin fixing the cell borders of the cell of the lower layer and replacing the usual HO_MARGIN(n) within the standard handover. On timer expiry the reduced HO_MARGIN(n) allows a power budget handover into a cell of the lower layer structure for a slow moving mobile which is expected to be still in the coverage area of that cell. On the contrary, a fast moving mobile is expected to have left the coverage area of an embedded cell of the lower layer structure while the timer for that cell is running and therefore the conditions for a better cell handover will be violated and thus preventing a handover request into that cell. Consequently fast moving mobiles are kept in the umbrella cell. A fast moving mobile initially connected to a cell of the lower layer structure (e.g. a phase 1 mobile or mobile having changed its speed) is steered to the upper layer structure by requesting for it a handover based on the absolute level criterion. It should be noted that HO_MARGIN_TIME is not only used as a threshold for power budget handover decisions, but also for ranking of cell within the target cell list, i.e. the order criterion for the target cell list is modified to PRIO_NCELL(n) = PBGT(n) - HO_MARGIN_TIME(n). This means that a rescue handover (Quality, Level and Distance) into a cell of the lower layer get a lower priority before the expiry of the timer.
A30808-X5226-C559-1-7618
5-9
Siemens
To prevent a power budget handover from a cell of the lower layer to an umbrella cell n HO_MARGIN(n) has to be set to a high value for each umbrella neighbor cell. It should be noted that there is no time dependent handover margin for the transition micro to umbrella cell (umbrella cell is not barred). Object ADJC Package DB Name HOMDOFF Range 0...127 Step Size 1 Unit dB
DELAY_TIME DELAY_TIME defines the time a cell of the lower layer structure is barred (by applying the HO_STATIC_OFFSET) for an incoming handover after the mobile has entered the coverage area of that cell defined by conditions (T1) and (T2). DELAY_TIME(n) ~ cell size of neighbor micro cell n/ vcritical where vcritical is that mobile speed above which mobiles are considered as fast. Object ADJC Package DB Name HOMDTIME Range 0...255 Step Size 1 Unit TSACCH
5-10
A30808-X5226-C559-1-7618
Siemens
HO_MARGIN The meaning of the HO_MARGIN for the mobile speed sensitive handover differs from that for the standard handover. For the standard handover it defines the threshold for a better cell handover; for the mobile speed sensitive handover it defines the location of the timer start according to the condition (T2). The role of the handover margin is transferred to HO_MARGIN_TIME. Choosing small or even negative values for HO_MARGIN results in an early timer start and thereby avoids cell border displacements and interference problems. Setting HO_MARGIN to large negative values effectively cancels condition (T2), and consequently the timer start is only triggered by condition (T1). Hence, in this case the cell borders of the lower layer structure are independent of the cell site positions with respect to the cell sites in the upper layer structure. Object ADJC Package DB Name HOM Range 0...126 -63...+63 dB Step Size 1 Unit dB
MICRO_CELL Flag to indicate whether a neighbor cell is handled as a micro cell by the speed sensitive handover algorithm. Only for micro neighbor cells the above mentioned timers are started and a handover is prevented using the offsets. Object ADJC Package DB Name MICROCELL Range TRUE/FALSE Step Size Unit -
A30808-X5226-C559-1-7618
5-11
Siemens
3
3.1
Priority Layers
General Remarks
Umbrella and macro cells can easily provide coverage, whereas the capacity of the network can be increased by the implementation of small cells, micro cells and pico cells. All equal cells characterized by the radio point of view are defining one Radio Coverage Layer. To overcome the limited radio resources, in addition to the introduction of small cells, micro cells and pico cells, it is also possible to operate different layers in different frequency bands e.g. GSM 900 and GSM 1800 in a dual band network.
Umbrella Cell GSM900 Radio Coverage Layer 5
Macro Cell GSM900 Radio Coverage Layer 4
Small Cell GSM900/1800 Radio Coverage Layer 3 Micro Cell GSM900 Radio Coverage Layer 2
Pico Cell GSM900/1800 Radio Coverage Layer 1
Fig. 2 Multiple layer and dual band network
5-12
A30808-X5226-C559-1-7618
Siemens
For the management of such a multiple layer network, SIEMENS introduced the Hierarchical Cell Structure feature. The cells and layers are characterized with settable Priority Levels. Up to 16 different priority levels can be assigned to the different layers and cells respectively. The handover procedure from one cell to another is divided into three main parts:
l l l
Handover Detection Generation of a Target Cell List Ranking of the Target Cell List
These parts and the mobile and base station measurement reports are executed by the base station.
Handover Detection: Different types of handovers are detected because of different reasons. The following table gives an overview: Type of handover Forced Handover Reason for this type of handover
During call set up phase, no free traffic (necessary for the Directed Retry feature) channel can be allocated in the target cell. Imperative Handover Bad uplink and downlink quality. Low uplink and downlink level. Exceeding maximum distance. A neighbor cell would provide a better receiving level even if the serving cell is performing sufficiently good.
Better Cell Handover (Power Budget Handover)
A30808-X5226-C559-1-7618
5-13
Siemens
Generation of the Target Cell List: When a handover cause is detected, a target cell list is generated. Only those cells which are declared as neighbor cells of the serving cell are possible target cells. In addition, depending on the type of handover, specific conditions have to be fulfilled by a neighbor cell to be included in the target cell list.
Ranking of the Target Cell List: In case of a forced handover or an imperative handover, there are two ranking algorithms for the target cell list: rank 0 and rank 1. Both these algorithms generate two ranked sublists of cells (upper sublist and lower sublist). The cells which are listed in both sublists are ranked according to specific criteria e.g. increasing values of priority.
5-14
A30808-X5226-C559-1-7618
Siemens
3.2
In the BSC database the parameters relevant for the Hierarchical Cell Structure feature are:
Hierarchical Cell Handover HIERC This parameter indicates whether the ranking of the target cells based on the priority layers is enabled or disabled. Object HAND Package DB Name HIERC Range TRUE/FALSE Step Size Unit -
Priority Layer PL If hierarchical cell handover is enabled (HIERC=TRUE) this parameter determines the priority layer of the own (=serving) cell. This priority is only evaluated for the Power Budget handover decision. The priority layers of the neighbor cells are administered in the ADJC object (see parameter PLNC). Object HAND Package DB Name PL Range 0-15 Step Size 1 Unit -
0=highest priority, 15=lowest priority default: 0
A30808-X5226-C559-1-7618
5-15
Siemens
Hierarchical Cell Ranking Flag HIERF This parameter is used to switch between two alternative ranking methods. Both these ranking methods are only relevant for imperative handovers (i.e. level, quality or distance handovers) and they influence the ranking of the cells in the upper and lower sublist of the target cell list. Object HAND Package DB Name HIERF Range RANK0 / RANK1 Step Size Unit -
default: Rank0
Priority Layer of Neighbor Cell PLNC This parameter determines the priority layer of the adjacent cell. The priority layer is relevant for the handover decision if the feature ranking of target cells on the basis of priority layer is enabled (HIERC=TRUE). Object ADJC Package DB Name PLNC Range 0-15 Step Size 1 Unit -
5-16
A30808-X5226-C559-1-7618
Siemens
Penalty Priority Layer of Neighbor Cell PPLNC This parameter determines the priority layer of those adjacent cells which are defined as microcells (see parameter MICROCEL in the command CREATE:ADJC) and for which the speed sensitive handover timer (see parameter HOMDTIME in the command CREATE:ADJC) is currently running. This priority layer is relevant for the handover decision if the features speed sensitive handover (see parameter ENDPWBHO in the command SET:HAND) and ranking of target cells on the basis of priority (see parameter HIERC in the command SET:HAND) are enabled. Object ADJC Package DB Name PPLNC Range 0-15 Step Size 1 Unit -
Level Offset for Neighbor Cell LEVONC This parameter determines the level offset that is added to the minimum receive level of an adjacent cell if ranking method Rank1 is selected in the hierarchical cell ranking flag (see parameter HIERF). With the help of this offset, the ranking of the target cells can be controlled. Object ADJC Package DB Name LEVONC Range 0-63 Step Size 1 Unit 1 dB
A30808-X5226-C559-1-7618
5-17
Siemens
3.3
3.3.1
l l
Influence of Priorities on Cell Ranking

for Powerbudget Handovers
&
In case of a powerbudget handover only the cells having a value of: PBGT(n) > HO_MARGIN(n) PLNC(n) PL
are inserted in the target cell list. 1. These cells are sorted in increasing order of priority -PLNC(n) 2. Having the same priority these cells are sorted by: PBGT (N) - HO_MARGIN (N)
3.3.2
for Imperative Handovers
In case of an imperative handover two ranking possibilities are foreseen , according to the setting of a HIERARCHICAL_CELL_RANK_FLAG. Rank0: All cells where:
RXLEV_NCELL(n) > RXLEV_MIN (n) + MAX( 0,MS_TXPWR_MAX (n) - P ) are sorted in the target cell list into two groups: 3. Cells where: PBGT(n) - HO_MARGIN(n) > 0 are followed by those cells where: PBGT(n) - HO_MARGIN(n) 0 4. Inside these groups the cells are sorted in increasing order of priority - PLNC(n) 5. Having the same priority these cells are sorted by: PBGT (n) - HO_MARGIN (n)
5-18
A30808-X5226-C559-1-7618
Siemens
Rank1:
All cells where:
RXLEV_NCELL(n) > RXLEV_MIN (n) + MAX( 0,MS_TXPWR_MAX (n) - P ) are sorted in the target cell list into two groups: 6. Cells where: rxlev_ncell(n)> rxLev_MIN(n)+max(0,MS_TXPWR_MAX(n)P)+LEVEL_OFFSET_NCELL(n) are followed by those cells where: rxlev_ncell(n) rxLev_MIN(n)+max(0,MS_TXPWR_MAX(n)P)+LEVEL_OFFSET_NCELL(n) 7. Inside these groups the cells are sorted in increasing order of priority - PLNC(n) 8. Having the same priority these cells are sorted by: BCVPBGT (n) - HO_MARGIN (n) If the flag is set to RANK0 the cell ranking is reworked separately in the set of cells having PBGT > HO_MARGIN and in the other one , that is PBGT < HO_MARGIN. With the flag set to RANK1 the operator has the possibility to organize two sets of cells on the basis of a signal level that it has been considered Sufficient ; this method allows to further encourage, with respect to the previous RANK0 the HO towards the lower layers.
A30808-X5226-C559-1-7618
5-19
Siemens
4
4.1
Concentric Cells
Introduction to Concentric Cells
The feature Concentric Cells allows the creation of two logical cells within one GSM cell. These cells are called inner area and complete area. The transmission power of the smaller cell is strongly reduced (lower cell radius). Handovers between the two areas are depending on the field strength level and the location of the mobile station. The broadcast channels (BCCH and SDCCH signaling channels) have to cover the complete area and are used for both cells. The customer benefits are:
l l l l
The concentric cells feature can be used to introduce an additional frequency reuse pattern for the frequencies in the inner area. The new frequency re-use pattern can be used with a shorter re-use distance. Increased network capacity. Increased grade of service.
inner area
complete area complete area

Fig. 3 Inner and complete area of a concentric cell
inner area
5-20
A30808-X5226-C559-1-7618
Siemens
Possible intracell handovers:

l l
From complete area to inner area of a concentric cell. From inner area to complete area of a concentric cell.
Possible intercell handovers:

l l l l
From complete area of concentric cell A to complete area of concentric cell B. From complete area of concentric cell A to inner area of concentric cell B. From inner area of concentric cell A to complete area of concentric cell B. From inner area of concentric cell A to inner area of concentric cell B (but only for sectorized concentric cells, i.e. both concentric cells are served by the same BTSE.)
inner area of cell A
inner area of cell B
complete area of cell A
complete area of cell B
Fig. 4 Inner and complete area of two adjacent concentric cells A and B
A30808-X5226-C559-1-7618
5-21
Siemens
4.2
In the BSC database , the new parameters relevant for the Concentric Cells feature are:
Concentric Cell This parameter defines whether or not the cell is a concentric one. Whether a TRX serves the inner area or the complete area is defined in the TRX object (see parameter TRXAREA in the command CREATE:TRX). The different TRX ranges are determined by the values entered for the power reduction (see parameter PWRRED in the command CREATE:TRX). Within a concentric cell special concentric cell handovers can be enabled from the inner to the complete area and vice versa. These handovers are executed on level / distance conditions defined in the handover package (see parameters ENCCD, RXLVI, RXLVO and CCDST in the command SET:HAND). Object BTS Package BTSB DB Name CONCELL Range TRUE / FALSE Step Size Unit -
default: FALSE
5-22
A30808-X5226-C559-1-7618
Siemens
Enable Concentric Cell Distance Handover This parameter determines whether in the concentric cell the distance should also be a possible cause for the intracell handover. Note: If ENCCD is set to TRUE then
l
a handover from inner to complete area is executed if the level conditions defined by the parameter RXLVI (see below) is fulfilled or if the MS-BTSE distance exceeds the distance limit according to the principles explained for the parameter CCDST (see below). a handover from complete to inner area is executed if the level conditions defined by the parameter RXLVO (see below) is fulfilled and if the MS-BTSE distance is smaller than the distance limit according to the principles explained for the parameter CCDST (see below). Object HAND Package DB Name CCDIST Range TRUE / FALSE Step Size Unit -
default: FALSE
A30808-X5226-C559-1-7618
5-23
Siemens
RXLEV Threshold Downlink for Inner Area This parameter defines the downlink receive level threshold in the inner area of a concentric cell the transition of which causes an intracell handover from the inner area to the complete area. Principle: If the MS is served by the TRX of the inner area and RXLEV_DL < RXLVI then the MS will be handed over to the complete area TRX. Object HAND Package DB Name HORXLVDLI Range 0 - 63 Step Size 1 Unit 1 dB
0 = less than -110dBm 1 = -110dBm 2 = -109dBm ... 62 = -48dBm 63 = more than -48dBm default: 26
5-24
A30808-X5226-C559-1-7618
Siemens
RXLEV Threshold Downlink for Outer Area This parameter defines the downlink receive level threshold in the complete area of a concentric cell the transition of which causes an intracell handover from the complete area to the inner area. Principle: If the MS is served by the TRX of the complete area and RXLEV_DL > RXLVO then the MS will be handed over to the inner area TRX. Object HAND Package DB Name HORXLVDLO Range 0 - 63 Step Size 1 Unit 1 dB
0 = less than -110dBm 1 = -110dBm 2 = -109dBm ... 62 = -48dBm 63 = more than -48dBm default: 32
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
A30808-X5226-C559-1-7618
5-25
Siemens
Handover Concentric Cell Distance Limit This parameter is only relevant if the parameter ENCCD (see above) is set to TRUE. It determines the distance limit used for the 'distance' intracell handover decision within the concentric cell. Principle:
l l
If the MS is served by a TRX of the complete area and MS_BTSE-distance < CCDST then the call will be handed over to the inner area. If the MS is served by a TRX of the inner area and MS_BTSE-distance > CCDST+1 then the call will be handed over to the complete area. The hysteresis '+1' is automatically applied to avoid handover oscillation if the MS moves very close to the de-fined distance limit. Object HAND Package DB Name HOCCDIST Range 0 - 35 Step Size 1 Unit 1 km
unit: 1 km range: 0-35 default: 5
5-26
A30808-X5226-C559-1-7618
Siemens
Enable Inner-Inner Handover This parameter determines whether an intercell handover from inner to inner area in sectorized concentric cells is enabled. Under normal conditions (i.e. with EININ=FALSE) the handover would be executed to the complete area of the collocated cell first, after that a complete-to-inner handover would follow. To avoid these unnecessary signaling transactions EININ should be set to TRUE. Object HAND Package DB Name ININHO Range TRUE / FALSE Step Size Unit -
default: FALSE
Collocated Cell CCELL This parameter defines the cell belonging to the sectorized concentric cells to which an intercell handover from inner to inner area is possible. Parameter format: collocated cell 1 - collocated cell 2. The collocated cell is represented by its BTS-no. Object HAND Package DB Name CCELL Range 0-119 Step Size 1 Unit -
range: 0-119, 254 (=NOT_DEFINED) default: 254 (= NOT_DEFINED)
A30808-X5226-C559-1-7618
5-27
Siemens
Power Reduction This parameter specifies the number of 2-dB-steps the Tx power should be reduced from the maximum transmit power. Since the sending power determines the actual cell size the PWRRED parameter is used to adjust the sending power according to the desired transmission range. Note for concentric cells: Since in concentric cells this parameter determines the different ranges of inner and complete area TRX it must be set in accordance with the setting of the parameter TRXAREA (see below)! Object TRX Package DB Name PWRRED Range 0-6 Step Size 1 Unit 2 dB
range: 0-6 (0dB-12dB) default: 6
TRX Area This parameter specifies whether a TRX belongs to a concentric cell and, if yes, whether it serves the inner or the complete area. Note: For concentric cells this parameter must be set in conjunction with a sensible setting of PWRRED (see above)! Object TRX Package DB Name TRXAREA Range NONE, INNER, COMPLETE Step Size Unit -
default: NONE
5-28
A30808-X5226-C559-1-7618
Siemens
Extended Cells
extended area
normal area
Fig. 5 Concept of extended cells
A30808-X5226-C559-1-7618
5-29
Siemens
5.1
Introduction to Extended Cells
The purpose of the new feature Extended Cells is to overcome the 35 km radius of the normal GSM cell range. This limit is imposed by the maximum transmission delay on the air interface which allows the reception of the bursts exchanged between MS and BTSE in the appropriate timeslot. By using two consecutive timeslots to receive the RACH bursts and the normal bursts on the radio channels this transmission delay may be longer and thus the maximum distance between MS and BTSE will be increased to approximately 100 km. Because of this concept, SDCCH, broadcast and control channels must also be defined using two consecutive timeslots. Although by using two consecutive timeslots for one logical channel the capacity of the carrier is reduced accordingly, the main benefit is that the coverage area of a mobile network can be increased at minimum of site costs. Especially with sea coverage, where transmission losses are comparatively low, extended cells can create new business opportunities. Other applications are e.g. fast coverage increase in low density areas and the filling of coverage gaps in existing networks. Because of the different channel types a new type of intracell handover has been introduced: from SINGLE timeslot channel towards DOUBLE and vice versa. The handover decision depends on the MS - BTSE distance. For a MS in the normal area (MS - BTSE distance less than 35 km) the BSC will allocate a SINGLE timeslot, if available. Otherwise it will assign a DOUBLE timeslot. For a MS in the extended area always a DOUBLE timeslot will be assigned. In extended cells the features halfrate transmission and baseband frequency hopping can be used. When the operator assigns a frequency hopping system to a DOUBLE channel the two timeslots used automatically obtain the same frequency hopping attributes. This configuration rule has to be considered when defining the frequency hopping for the same timeslots on other TRX. Example: If channel 2 on one TRX is defined as DOUBLE with MAIO=0, then all channels 2 and also all channels 3 on the other TRX using the same frequency hopping system must not use the same value, otherwise the command is rejected.
5-30
A30808-X5226-C559-1-7618
Siemens
156,25 Bit = 0,576875 ms
156,25 Bit = 0,576875 ms
3 TB
41 Sync.Sequence
36 Encrypted Bits
3 TB
68,25 GP empty Burst
Fig. 6 Burst structure for extended cells
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A30808-X5226-C559-1-7618
5-31
Siemens
5.2
Parameter CELLTYPE

Explanation With this parameter the cell type is chosen. In case of an extended cell, the maximum cell radius is approximately 100 km. Extended cells can not be used together with concentric cells. If a cell is defined as an extended cell, with the parameter EXTENDED MODE a channel can be defined using two subsequent timeslots. For STANDARDCELL or UMBRELLACELL the value FALSE has to be used. For broadcast and control channels (BCCH, CCCH, SDCCH) in an extended cell the value TRUE must be used. In case of an extended cell the next timeslot cannot be configured.
Range: STDCELL, UMBCELL; EXTCELL Default value: STDCELL EXTMODE Range. TRUE, FALSE Default value: FALSE
EXTCHO Range: ENABLED, DISABLED Default: value: FALSE HOTMSRME Range: 35 ... 100 (35 ... 100km) Default value: 100
The parameter ENABLE EXTENDED CELL HANDOVER defines whether intracell handovers between the normal and extended area of a cell are allowed or not. The value HANDOVER THRESHOLD MS RANGE MAXIMUM EXTENDED CELL represents the maximum allowed MS - BTSE distance for the Extended Cell. To avoid conflict with the feature Call Release for Excessive Distance this parameter must be less than the parameter ExcessiveDistance.
HOMSTAM Range: 0 ... 35 (0 ... 35 km) Default value: 32
Threshold for the maximum MS distance This parameter represents the maximum allowed MS - BTS distance to use a single timeslot channel.
5-32
A30808-X5226-C559-1-7618
Siemens
BCCH double
TCH double
TCH double
TCH single
TCH single
channel instance must not be used
Fig. 7 Example of a TDMA frame with single and double channels
double timeslot channel
single timeslot Channel
HOMSTAM
HOTMSRME Excessive Distance
Fig. 8 Explanation of HOMSTAM parameter
A30808-X5226-C559-1-7618
5-33
Siemens
Parameter HOMRGTA Range: 0 ... 35 (0 ... 35 km) Default value: 4
Explanation This attribute is used to prevent a handover oscillation when a MS leaves the extended area and enters the normal area. The handover will be performed only when the MS - BTSE distance added to this margin is below of the defined value of HOMSTAM, i.e.: Distance + HOTMRGTA < HOMSTAM.
5-34
A30808-X5226-C559-1-7618
Siemens
HOTMRGTA
Distance
MS - BTSE
HOMSTAM
HOTMSRME
Fig. 9 Criterion for Extended Cell Intracell Handover
A30808-X5226-C559-1-7618
5-35
Siemens
Call Release for Excessive Distance
Home PLMN
Region, where no service is supported or no roaming agreement exists
Borderline of the home PLMN
Fig. 10 Concept of Call Release for Excessive Distance
5-36
A30808-X5226-C559-1-7618
Siemens
6.1
Introduction to Call Release for Excessive Distance
The feature Call Release for Excessive Distance requires the BTSE to trigger the release of a call when the MS distance has exceeded a predefined threshold value. This may be useful in two situations:
l l
When the MS is moving towards a region where no service is supported. In this case, call release avoids jamming the adjacent radio timeslot. When the MS crosses the borderline with another PLMN, where no agreement exists. In this case, even if the distance from the BTSE still allows the communication, it is better to release the call to avoid isofrequential interference inside the other network.
The criterion for Call Release for Excessive Distance is the Timing Advance. Obviously, the call release will occur only if the Handover request cannot be satisfied by any adjacent cell. For this reason it is necessary to set the power level of each cell so that the Handover request is forwarded before the Timing Advance has reached the threshold value for Call Release. The mechanism of Call release is already implemented. When a call must be released because of abnormal conditions, the BTSE sends a CONNECTION_FAILURE message to the BSC and specifies the cause, e.g. radio link failure. In case of excessive distance the same message CONNECTION_FAILURE is used to notify this condition with the new cause value DISTANCE_LIMIT_EXCEEDED.
A30808-X5226-C559-1-7618
5-37
Siemens
6.2
Parameter EXCDIST Range:

Explanation The attribute EXCESSIVE DISTANCE specifies the distance threshold for call release. In case of Extended Cells this value should be higher than the parameter HOTMSRME to ensure that a Handover request is sent before the call is released.
1 ... 100 (1 ... 100 km) for Extended Cells, 1 ... 35 (1 ... 35 km) for Standard Cells Default value: 100 km for Extended Cells 35 km for not Extended Cells EEXCDIST Range: FALSE, TRUE Default value: FALSE
The attribute ENABLE EXCESSIVE DISTANCE CALL RELEASE indicates whether a call release because of an excessive distance between MS and BTSE is enabled or not.
5-38
A30808-X5226-C559-1-7618
Siemens
Border Line of the network
EXCDIST
Call Release
Handover due to the power level

Fig. 11 Call Release for Excessive Distance at the border of different PLMN.
A30808-X5226-C559-1-7618
5-39
Siemens
Exercise
Exercise
What is influenced by setting Hierarchical Cell Handover Parameter (HIERC) to true:

l l l l l l l
The measurement reports? The averaging of the measurement reports? The comparison of the averaged measurement values with the handover thresholds defined in the BSC database? The handover reason? The conditions for neighbor cells to be listed in the target cell list? The ranking of the cells in the target cell list? The handover condition indication message?
The feature Call Release for Excessive Distance, does it offer advantages for the Network operator or for the Mobile Subscribers?
Color all the parameters which have been discussed in this chapter in the BSC database given in the appendix.
5-40
A30808-X5226-C559-1-7618
Siemens
A30808-X5226-C559-1-7618
5-41
Siemens
5-42
A30808-X5226-C559-1-7618
Radio Link Failure
Siemens
Radio Link Failure
Contents
1 2 3 4 5 6 Introduction Radio Link Failure Procedure Radio Link Failure Warning Procedure Parameters for Radio Link Failure Radio Link Failure related Performance Measurements Exercise 3 4 5 9 10 11
A30808-X5226-C559-1-7618
6-1
Siemens
Radio Link Failure
6-2
A30808-X5226-C559-1-7618
Radio Link Failure
Siemens
Introduction
The Radio Link Failure (RLF) is defined as a loss of communication means on a dedicated channel. The purpose of detecting an RLF in both the MS and BTS is to ensure that connections with unacceptable voice/data quality, which can not be improved either by RF power control or handover (e.g. if the MS leaves the coverage area of the network), are either released or re-established in a defined manner. In the MS, the criterion for determining an RLF is based on the success rate of decoding messages on the downlink SACCH. In the BTS, the same criterion for the detection of an RLF is implemented as in the MS, i.e. the RLF criterion is based on the success rate of decoding messages on the uplink SACCH . Furthermore as an extension of the RLF procedure a declaration of a Radio Link Failure Warning (RLFW) is proposed in the case that the communication link threatens to break-down. Upon detection of RLFW both the TRX and the MS are directed to use their maximum allowed RF power level on the concerned dedicated channel.
A30808-X5226-C559-1-7618
6-3
Siemens
Radio Link Failure
Radio Link Failure Procedure
In the BTS as well as in the MS, the criterion for the detection of a RLF is based on the success rate of decoding messages on the uplink or downlink SACCH, respectively. In the beginning, when a connection on a dedicated channel is established, the radio link counter S (separately for MS and BTS) is initialized with the value of the O&M parameter RADIO_LINK_TIMEOUTMS/BTS (range 4...64, step size 4) which is administered on a cell by cell basis. There are different parameters for uplink and downlink to initialize the counters in the MS and BTS separately. The downlink parameter is broadcasted to all mobiles in the respective cell. Every time the BTS/MS is unable to decode a SACCH message on the uplink/downlink, the respective counter S is decremented by 1. Every time a SACCH message is successfully decoded in the BTS, the counter S is incremented by 2. In any case the counter shall not exceed the value of the RADIO_LINK_TIMEOUT parameter. As soon as the counter S in the BTS reaches 0, a RLF is declared and a CONNection FAILure INDication message with cause radio link failure is sent to the BSC via the Abis interface and the BSC initiates a release of the concerned connection. An analogous action is taken by the MS when the MS counter reaches 0. In case of a channel change (handover) counter S is reset to its initial value RADIO_LINK_TIMEOUT.
6-4
A30808-X5226-C559-1-7618
Radio Link Failure
Siemens
Radio Link Failure Warning Procedure
The radio link failure warning procedure is only applied for the uplink. A call in progress with a good quality may suddenly experience the impact of a severe shadowing or any other kind of high level interference. As a consequence, a sudden degradation of the link quality is observed. Due to the considerable delay inherent in the regular PC process, the required power increase (if feasible) may not be performed fast enough to properly cope with the situation. Note that Intercell Handover due to quality or level is not allowed as long as the RF power has not reached the permitted maximum value. Therefore a procedure is implemented in the BTS which immediately directs the MS and the concerned TRX in the BTS to use their maximum RF power if a RLF Warning occurs. The RLF warning is produced by the BTS as soon as it detects that radio communication on the uplink of a connection is short before break-down and a RLF threatens to come about. The generation of RLF Warnings in the BTS can be enabled or disabled by an O&M flag EN_PC_RLFW. The criterion for the generation of a RLF Warning is based on the radio link counter S. Every SACCH multiframe the radio link counter S is modified and a RLF Warning is generated if the counter S is less than or equal to the threshold PC_TIMEOUT. The threshold PC_TIMEOUT is an O&M parameter administered on a cell by cell basis. The following regularity condition shall apply: RADIO_LINK_TIMEOUT > PC_TIMEOUT Upon detection of a RLF Warning in the BTS, the regular power control process on the concerned dedicated channel is immediately suspended. Power control actions due to RLF Warning have a higher priority than regular PC actions.
A30808-X5226-C559-1-7618
6-5
Siemens
Radio Link Failure
RLF Counter S
RADIO_LINK_TIMEOUT = 8 Radio Link Failure Warning Power Command Radio Link Failure
PC_TIMEOUT = 2
SACCH Frames decoded SACCH message not decoded SACCH message
Fig. 1
. . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
A30808-X5226-C559-1-7618
Radio Link Failure
Siemens
The first time a RLF Warning is detected in the BTS, the power control timers are reset (if running), both MS_TXPWR and BS_TXPWR are set to their upper bounds MS_TXPWR_MAX and BS_TXPWR_MAX (if not already set by the regular PC process), respectively, and the corresponding timers for suspension of the regular power control process are started with the value of the O&M parameter P_CON_INTERVAL The timers monitoring the confirmation of the commanded power level are not used because of the irregular reception on the SACCH. If MS_TXPWR or BS_TXPWR has already achieved its upper bound either on a regular PC command or due to the first RLF Warning, the only action to be taken is to restart timers for suspension of the regular power control process (P_CON_INTERVAL), respectively. As a consequence in the case of repeated RLF Warnings, both timers shall be restarted simultaneously. Upon expiration of these timers the threshold comparison process of the respective (uplink/downlink) power control process is resumed, provided that the call on the dedicated channel is still in progress.
A30808-X5226-C559-1-7618
6-7
Siemens
Radio Link Failure
RLF Counter S
RADIO_LINK_TIMEOUT = 8 Radio Link Failure Warning Power Command Radio Link Failure
PC_TIMEOUT = 2
SACCH Frames decoded SACCH message not decoded SACCH message
Fig. 2 Example for the radio link failure process
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
6-8
A30808-X5226-C559-1-7618
Radio Link Failure
Siemens
Parameters for Radio Link Failure

DB Name/ Object EPWCRLFW /PWRC Range Meaning
Specification Name EN_PC_RLFW
TRUE/ Flag to enable/disable the radio FALSE link failure warning mechanism. 0...15 Initial value of the radio link failure counter S within the MS: S0 = 4 + 4 * RDLNKTO.S is increased / decreased by 2/1 if an SACCH message can / cannot be decoded. If S reaches 0, the connection is released and the MS returns into the idle mode. Initial value of the radio link failure counter S within the BTS: S0 = RDLNKTBS.S is increased /decreased by 2/1) if an SACCH message can / cannot be decoded. If S reaches 0, the connection is released. If the radio link failure counter S within the BS reaches PC_TIMEOUT, the transmit power of the MS and the BS is set to its maximum value.
RADIO_LINK_TIMEOUTM RDLNKTO
S
/BTSB
(7) RADIO_LINK_TIMEOUTBS RDLNKTBS /PWRC (24) PC_TIMEOUT PCRLFTH /PWRC 0...63 (12) 4...64
A30808-X5226-C559-1-7618
6-9
Siemens
Radio Link Failure
Radio Link Failure related Performance Measurements

Abbreviation NRFLTCH Functional group BTSMEAS
Measurement Type Number of lost radio links while using a TCH (Fullrate/Halfrate) Number of lost radio links while using an SDCCH
NRFLSDCC
BTSMEAS
6-10
A30808-X5226-C559-1-7618
Radio Link Failure
Siemens
Exercise
Exercise
In which GSM recommendation can you find information about Radio Link Failure?
Look for the details of the performance measurement "Number of lost radio links while using a TCH" in the electronic documentation. How many counters are related to this performance measurement?
Enable the Radio Link Failure mechanism with the following values: Radio_Link_Timeout PC_Timeout:
MS :
10 28 20
Radio_Link_Timeout BS:
A30808-X5226-C559-1-7618
6-11
Siemens
Radio Link Failure
6-12
A30808-X5226-C559-1-7618
Overload Handling
Siemens
Overload Handling
Contents
1 2 3 3.1 3.2 3.3 3.4 4 5 Introduction Timer Control of Overload Reduction Overload Detection and Counter Measures BTS Overload Handling BSC Overload Handling MSC Overload Handling Parameters for Overload Handling: Overload Handling related Performance Measurements Exercise 3 4 6 6 7 8 9 10 14
A30808-X5226-C559-1-7618
7-1
Siemens
Overload Handling
7-2
A30808-X5226-C559-1-7618
Overload Handling
Siemens
Introduction
The aim of the overload control mechanism is to preserve the traffic-handling capabilities of the mobile base station system (BSS) under adverse conditions. The overload control mechanism is implemented in the BSC and consists of traffic detection mechanism and defensive action makers. Traffic detection mechanism consists of overload messages coming either from the various parts of the network (BTS and/or MSC) of from the BSC itself (overload detection). Defensive actions aimed at reducing both mobile originating (MOC) and/or mobile terminating (MTC) calls (overload handler); the strategy is here presented and follows the GSM recommendation 08.08. GSM rec 08.08 gives the following definition of the general overload handling strategy: The overload causing traffic is reduced in several timer guarded steps until the overload is prevented. Otherwise, if for some time no overload is indicated, the traffic is increased again in timing steps until full load has been resumed. The time-out values of the timers, number of steps, amount and type of traffic reduced in each step, overload recognition and threshold parameters are all considered implementation dependent and have not been specified. Essentially there are two methods to reduce overload:
l l
reducing the mobile terminating traffic by discarding paging messages, reducing the mobile originating traffic by barring the access to specific cells.
Access barring is done using the access classes specified by GSM (refer to GSM 08.08). There are 10 access classes (0...9) related to normal subscribers. The access class to which a subscriber belongs is derived from his IMSI. Furthermore, there are 5 classes (11...15) assigned to special high priority subscribers (e.g. police, PLMN operator, ...). To reduce overload in moderate way, incoming traffic is not completely rejected, but reduced by several steps of escalation controlled by two timers.
A30808-X5226-C559-1-7618
7-3
Siemens
Overload Handling
Timer Control of Overload Reduction
When getting informed on an overload situation in a BTS, in the MSC or in the BSC itself, the BSC performs the first step for traffic reduction and starts two timers T17 and T18 with T18 > T17. During run time of T17 all overload messages with the same cause as the initializing message are ignored in order not to reduce the traffic too rapidly. If the overload situation is still present after expiry of T17, but during runtime of T18, the next step of traffic reduction is initiated and T17 and T18 are started again. This step by step reduction of traffic is maintained until the maximum reduction is obtained arriving at the last step. If timer T18 expires (i.e. no overload message is received), the BSC increases the traffic by one step (i.e. stops the traffic reduction measure of the last step) and restarts timer T18. This increment will continue until full load has been resumed. T17: Overload message block timer T18: Overload observation timer
7-4
A30808-X5226-C559-1-7618
Overload Handling
Siemens
BSC start timers 1. step of load reduction restart timers 2. step of load reduction T 18 T 17 overload overload (ignored) overload overload (ignored)
MSC
restart T 18 increase traffic by one step
increase traffic to full load

Fig. 1
The two timer T17, T18 are administered in the object BSC, package BSCT: DB Name BSCT17 Range <unit>-0... <unit> 254 Default: 20 half sec. <unit>-0... <unit> 254 Default: 60 half sec. Unit half seconds five seconds Meaning Started when an overload message is detected. During runtime of T17 overload messages are ignored. Started in case of overload, defines the observation time for overload.
BSCT18
half seconds five seconds
A30808-X5226-C559-1-7618
7-5
Siemens
Overload Handling
3
3.1
l l
Overload Detection and Counter Measures

BTS Overload Handling
call rejected (in future release: queuing and directed retry, i.e. serving the call by a suitable neighbor cell) rejection by immediate assignment reject message, new access is barred for a certain time (timer T3122)
no TCH available no SDCCH available
AGCH overload (i.e. BS is not able to forward immediate assignment or immediate assignment reject messages). 1st step: BSC barrs the first half of access classes of that cell 2nd step: BSC barrs the second half of access classes of that cell
PCH overload: PCH overload is detected when the free buffer space in the BTS for paging messages is zero or below a threshold (given by the parameter CCCH_LOAD_THRESH ). Then the BSC is periodically (period given by parameter CCCH_LOAD_IND_PERIOD ) informed on the current load on the PCH. The reaction of the BSC is pagings for the concerned BTS are discarded and the MSC is informed.
7-6
A30808-X5226-C559-1-7618
Overload Handling
Siemens
3.2
l l l
BSC Overload Handling
BSC overload is detected when the Tx buffers of the CCS7 links are congested the percentage of busy (level 3) registers to handle incoming call requests is above a threshold (90%) The real time processor load of the telephony processor TDPC is above a certain threshold set by the O&M parameter OVL_START_THRESH . Sending of overload messages is stopped when the load is below a second parameter OVL_END_THRESH with OVL_END_THRESH < OVL_START_THRESH.
When BSC overload is detected, the following steps for traffic reduction are performed 1st step: the BSC barrs the first half of access classes in a group of cells 2nd step: the BSC barrs all access classes in that group of cells 3rd step: BSC performs step 1 and 2 for the next group of cells 4th step: ... (and so on till the overload situation disappears) Within the traffic reduction algorithm, a round robin mechanism is used. This means if for counteracting one overload situation, cells 1 to 4 had been barred and the overload ends, the 4 cells are unbarred. If an overload situation occurs again, the overload handler starts barring from the 5th cell and not from the first one.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A30808-X5226-C559-1-7618
7-7
Siemens
Overload Handling
3.3
MSC Overload Handling
MSC overload is detected by the MSC itself. The BSC is informed by an overload indication messages with cause processor overload. The MSC reduces paging load by its own and therefore the BSC reduces only mobile originating traffic by means of barring access classes (in the same way as for BSC overload).
7-8
A30808-X5226-C559-1-7618
Overload Handling
Siemens
3.4
Parameters for Overload Handling:

Object/ Package BSC/ BSCB DB Name T3122 Range 0...255 sec (5) Meaning Timer to barr a new access for a certain time after unsuccessful access (e.g. no SDCCH available) flag to enable/disable BSC overload handling flag to enable/disable MSC overload handling flag to enable/disable BTS overload handling threshold for TDPC processor (in BSC) overload detection: 10000 = 100 % threshold for TDPC processor (in BSC) below which the sending of overload messages is stopped: 10000 = 100 % period for sending the CCCH load indication message from BTS to BSC CCCH load threshold, if this threshold is exceeded the BTS informs the BSC using the CCCH load indication message
Specification Name T3122
EN_BSC_OVL _HAND EN_MSC_OVL _HAND EN_BTS_OVL _HAND OVL_START _THRESH OVL_END _THRESH
BSC/ BSCB BSC/ BSCB BSC/ BSCB BSC/ BSCB BSC/ BSCB
BSCOVLH MSCOVLH BTSOVLH OVLSTTHR
TRUE, FALSE TRUE, FALSE TRUE, FALSE 7000... 10000 7000... 10000
OVLENTHR
CCCH_LOAD _IND_PERIOD CCCH_LOAD _THRESH
BTS/ BTSB BTS/ BTSB
PCCCHLDI
0...255 sec (255) 0...100%
TCCCHLDI
(100)
A30808-X5226-C559-1-7618
7-9
Siemens
Overload Handling
Overload Handling related Performance Measurements
The very high growth rates of subscribers using mobile communication services means that existing resources have to be constantly controlled to ensure that bottlenecks and problems are detected and eliminated in good time. Subscriber behavior, which formed the basis for the original network plans, can be greatly influenced by new tariffs being issued by the network operators. For this reason, the cell configuration must constantly be adapted to the needs of the subscribers and the network operator must maintain the economic efficiency of the network structure. The network operator wants to offer the subscriber attractive communication possibilities as well as good network quality. The network status must be monitored constantly with the aid of the traffic measurement on the air-interface to meet these requirements.
7-10
A30808-X5226-C559-1-7618
Overload Handling
Siemens
The following table summarizes the overload handling related performance measurements: Measurement Type Abbreviation Functional group
TCH / TCH Connection related measurements Mean number of busy TCH MEBUSTCH (Fullrate/Halfrate) Number of available TCH (Fullrate/Halfrate) Attempted TCH seizures (Fullrate/Halfrate) Successful TCH seizures (Fullrate/Halfrate) Mean TCH busy time (Fullrate/Halfrate) Total number of TCH connections, per cell (Fullrate/Halfrate) NAVTCH ATTCHSEI SUCTCHSE MTCHBUTI TNTCHCL BTSMEAS BTSMEAS BTSMEAS BTSMEAS BTSMEAS BTSMEAS
All available TCH allocated AALTCHTI time Attempted TCH seizures meeting a TCH blocked state (Fullrate/Halfrate) ATCHSMBS
BTSMEAS BTSMEAS
A30808-X5226-C559-1-7618
7-11
Siemens
Overload Handling
SDCCH / SDCCH Connection related measurements Number of available SDCCH Mean number of busy SDCCH Maximum number of busy SDCCH per cell Number of attempted SDCCH seizures in a period Attempted SDCCH seizures meeting an SDCCH blocked state All available SDCCH allocated time NAVSDCCH MBUSYSDC MAXBUSDC NATTSDPE BTSMEAS BTSMEAS BTSMEAS BTSMEAS
ATSDCMBS
BTSMEAS
ASDCALTI
BTSMEAS
CCCH related measurements Total number of accesses by procedures (PCH, AGCH) TACCBPRO BTSMEAS
Number of accesses with a NACSUCPR successful result by procedure (PCH, AGCH and RACH)
BTSMEAS
7-12
A30808-X5226-C559-1-7618
Overload Handling
Siemens
Immediate assignment measurements Attempted immediate assignment procedures, per cause Successful immediate assignment procedures, per cause Successful immediate assignments of signaling channels per cause ATIMASCA BTSMEAS
SUIMASCA
BTSMEAS
NSUCCHPC
BTSMEAS
Assignment procedure measurements Total number of assignment attempts per cell per channel type TASSATT BTSMEAS
Total number of successful TASSSUCC assignments per cell per channel type ASCI connection related measurements Total number of assignment attempts relevant to VBS/VGCS Broadcast/Group Channels, per cell TASSATVS
BTSMEAS
BTSMEAS
Total number of successful TASSUCVS assignments relevant to VBS/VGCS Broadcast/Group Channels, per cell Number of new notifications to be sent on the Notification Channel (NCH) NNNOTNCH
BTSMEAS
BTSMEAS
Processor load measurements BSC processor load BTSE processor load BSCPRCLD BTSEPRLD BSCMEAS BTSMMEAS
A30808-X5226-C559-1-7618
7-13
Siemens
Overload Handling
Exercise
Exercise
In which GSM recommendation can you find information about Overload Handling?
Enable the overload handling by setting the following values in the BSC database: Wait indication timer (T3122) TDPC overload start threshold: TDPC overload end threshold: BTS overload handling: MSC overload handling: Overload message block timer: Overload message observation timer: 10 sec 94% 84% activated activated 7 seconds 9 seconds
7-14
A30808-X5226-C559-1-7618
Siemens
Contents
1 1.1 1.2 1.3 1.4 1.5 1.6 2 3 3.1 3.2 3.3 4 Power Control General Information Measurement Preprocessing for Power Control Power Control Decision Power Control Execution Parameters for Power Control Execution Power and Quality Measurements on Uplink/Downlink TCHs Discontinuous Transmission DTX Channel Allocation Due to Interference Level General Parameters for Channel Allocation due to Interference Level Interference Level Measurements on Idle TCHs Exercise 3 3 5 7 11 14 15 17 20 20 24 26 28
A30808-X5226-C559-1-7618
8-1
Siemens
8-2
A30808-X5226-C559-1-7618
Siemens
1
1.1
Power Control
General Information
The objective of power control is to adapt the transmit power of the MS as well as of the BTS to the reception conditions. For example a mobile station MS 1 located near the BTS can use a lower transmit power than a mobile station MS 2 at the edge of a cell to achieve the required uplink quality.
Advantages of power control:

l l
reduction of the average power consumption (especially in the MS), reduction of the interference experienced by co-channel (for adjacent) channel users.
A30808-X5226-C559-1-7618
8-3
Siemens
BTS T X P W R
T X P W R
MS 1
MS 2
Fig. 1
Power control is applied separately for the uplink and the downlink and separately for each logical channel. It can be enabled/disabled using the following flags (administered within the PWRC object): Specification Name EN_MS_PC EN_BS_PC DB Name EMSPWRC EBSPWRC Meaning Flag to enable/disable uplink power control. Flag to enable/disable downlink power control.
Remark: Downlink power control is not applied for downlink bursts using the BCCH frequency.
8-4
A30808-X5226-C559-1-7618
Siemens
1.2
Measurement Preprocessing for Power Control
Any control loop is based on measurements of the controlled system parameters. For PC purposes, for each call in progress and for both links (downlink/uplink), measurements of:
l l
received signal level received signal quality
are carried out over each SACCH multiframe, Every SACCH multiframe the MS sends in the next SACCH message block the downlink measurements on the dedicated channel (averaged over one SACCH multiframe) via the Measurement Report message to the serving TRX of the BTS. This means that any SACCH message will report the averaged data for the previous reporting period only. The TRX performs the uplink measurements on the dedicated channel. The measurement reports (uplink and downlink) referring to the same SACCH multiframe are used as input parameters for the Measurement Report averaging procedures, implemented within the BTS. The adjustment of the transmit power of the MS and the BTS is based on following measurement values:
l l
RXLEV_DL_FULL / SUB- RXLEV_UL_FULL / SUB RXQUAL_DL_FULL / SUB- RXQUAL_UL_FULL / SUB
A30808-X5226-C559-1-7618
8-5
Siemens
The measurement values are preprocessed within the BTS in the same way as for the handover process, i.e. a gliding average window and a weighting of FULL and SUB values is used. The parameters for measurement preprocessing for power control are administered in the object PWRC. Specification Name A_QUAL_PC DB Name PAVRQUAL AQUALPC PAVRQUAL WQUALPC PAVRLEV ALEVPC PAVRLEV WLEVPC Range 1-31 Meaning Averaging window size for RXQUAL values, used for power control decisions Weighting for RXQUAL_FULL values Averaging window size for RXLEV values, used for power control decisions Weighting factor for RXLEV_FULL values
W_QUAL_PC A_LEV_PC
1-3 1-31
W_LEV_PC
1-3
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
8-6
A30808-X5226-C559-1-7618
Siemens
1.3
Power Control Decision
For power control decision the average values of RXLEV_UL/DL and RXQUAL_UL/DL are compared with some preset thresholds (O&M parameters).
PC Decision Process
RXQUAL_XX< U_RXQUAL_XX_P
yes
no
yes
RXLEV_XX< L_RXLEV_XX_P + 2* POW_RED_ STEP_SIZE no power decrease
X RXQUAL_XX> L_RXQUAL_XX_P yes
power increase no X RXLEV_XX> U_RXLEV_XX_P yes
power increase no X RXLEV_XX< L_RXLEV_XX_P no X yes
power increase
Fig. 2 Power Control Decision Process
A30808-X5226-C559-1-7618
8-7
Siemens
Power Control Decision

RXQUAL
7 Power Increase (bad quality) L_RXQUAL_XX_P Power Increase (bad level) U_RXQUAL_XX_P Power Decrease (good quality) RXLEV 0 L_RXLEV_XX_P U_RXLEV_XX_P 63 Power Decrease (good level)
2 * POW_RED_STEP_SIZE
Fig. 3
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
8-8
A30808-X5226-C559-1-7618
Siemens
The power control decision is primarily based upon the received signal quality, rather than on the received signal level. The reason for this is that the transmitter power directly affects the quality of the radio link regardless of the overall received signal level, which may be dominated by co-channel interference. If the controlled variable (its average value) lies in the tolerance defined by the thresholds, then no control action is taken, i.e. a deadband type of control response is produced. This introduces stability into the control process and guarantees an adequate speech quality. Note, that the controlled variables involved in the algorithm are used in accordance with their coding, e.g. RXQUAL_XX = 0 corresponds to the least BER (best signal quality: BER<0.2%). The test RXLEV_XX < L_RXLEV_XX_P + 2 * POW_RED_STEP_SIZE should prevent the control loop from oscillating, i.e. a power decrease decision for quality reasons should not be followed by power increase decision for signal level reasons. Note, that the O&M parameter POW_RED_STEP_SIZE is defined in terms of a difference between two transmit power levels. An unit power level step corresponds to a nominal 2 dB step in the variation of the transmit power. Field measurements have shown that even at very low received power levels a good quality for a radio link can be obtained with a relative high probability. Because sudden fades may deteriorate the quality very rapidly, if the above condition is satisfied, the received power level is then compared with the corresponding lower threshold to ensure a required minimum power level on the radio link.
A30808-X5226-C559-1-7618
8-9
Siemens
Parameters for Power Control Decision The parameters for power control decision are administered in the object PWRC Specification Name L_RXLEV_DL_P L_RXLEV_UL_P U_RXLEV_DL_P U_RXLEV_UL_P L_RXQUAL_DL_P L_RXQUAL_UL_P U_RXQUAL_DL_P U_RXQUAL_UL_P DB Name LOWTLEVD LOWTLEVU UPTLEVD UPTLEVU LOWTQUAD LOWTQUAU UPTQUAD UPTQUAU Range 0...63 Meaning RXLEV threshold on downlink/uplink for power increase RXLEV threshold on downlink/uplink for power decrease RXQUAL threshold on downlink/uplink for power increase RXQUAL threshold on downlink/uplink for power decrease
0...63
0...7
0...7
The following integrity conditions on the power control thresholds have to be observed: U_RXQUAL_XX_P < L_RXLEV_XX_P < L_RXQUAL_XX_P U_RXLEV_XX_P XX = UL, DL; XX = UL, DL.
Furthermore the power control thresholds have to harmonize with the ones for handover, i.e.: U_RXQUAL_XX_P L_RXLEV_XX_ H < < L_RXQUAL_XX_P < L_RXLEV_XX_ P < L_RXQUAL_XX_ H U_RXLEV_XX_P XX = UL, DL; XX = UL, DL.
8-10
A30808-X5226-C559-1-7618
Siemens
1.4
Power Control Execution
Having detected within the decision process that a change of transmit power should be carried out, the value for this change has to be fixed. If power control would only be based on RXLEV, the difference between RXLEV and the level threshold could be used as the step size for power control decision. However, since the main objective is to maintain an acceptable speech quality and since there is no direct simple relation between a change of the transmit power level and the resulting change of RXQUAL, the strategy is to change the transmit power in small steps and then analyze the resulting RXQUAL. This means that fixed step sizes for power increase and power decrease are used given by the parameters:
l l
POW_INCR_STEP_SIZE: 2, 4 or 6 dB POW_RED_STEP_SIZE: 2 or 4 dB,
To be able to react fast enough on sudden drops of link quality it is recommended: POW_INCR_STEP_SIZE > POW_RED_STEP_SIZE. The maximum range for uplink power control is given by: 13 dBm ... Min (MS_TXPWR_MAX, P) 5 dBm ... Min (MS_TXPWR_MAX, P) 0 dBm ... Min (MS_TXPWR_MAX, P) for a GSM-MS for a GSM-MS for a DCS1800-MS Phase 1 Phase 2
where P is the maximum RF output power of the MS (power class) and MS_TXPWR_MAX the maximum transmit power allowed in the respective cell. The minimum step size for transmit power adjustment is 2 dB.
A30808-X5226-C559-1-7618
8-11
Siemens
For downlink power control the range is determined by the maximum output power PBTS of the BTS and the static reduction BS_TXPWR_RED of the BTS output power: BS_TXPWR_MAX = PBTS - 2 * BS_TXPWR_RED BS_TXPWR_RED = 0, 1, ... 6, Unit: 2 dB.
The range for downlink power control is then given by: BS_TXPWR_MAX - 30 dB ... BS_TXPWR_MAX with a step size of 2 dB. In the case of a power control decision a MS/BS Power Control message is created wherein the MS/BS is requested to adjust its transmit power level to: REQ_TXPWR = CONF_TXPWR + POW_INCR_STEP_SIZE (Power Increase) REQ_TXPWR = CONF_TXPWR - POW_RED_STEP_SIZE (Power Decrease) where CONF_TXPWR is the confirmed power level used by the MS or BTS on the concerned channel. If these values of REQ_TXPWR are not within the range for power control, the nearest value within the range is used instead. Having requested a transmit power REQ_TXPWR, the power control decision process is suspended and it is waited for a confirmation that the transmit power of the MS/BTS is adjusted to requested value, i.e. CONF_TXPWR = REQ_TXPWR. If such a confirmation is not received within an interval of P_CONFIRM SACCH multiframes, the power control decision process is immediately resumed using the most recently reported confirmed value. If a confirmation is received, the power control decision process is suspended for a certain number of SACCH multiframes given by the parameter P_CON_INTERVAL. The reason for this is to allow an observation of the effect of one power control decision before initializing the next one; by this means the power control process is stabilized. Thus it is recommended to set P_CON_INTERVAL > A_QUAL_PC in terms of a number of multiframes.
8-12
A30808-X5226-C559-1-7618
Siemens
Time relations for power control execution:

l l
case 1: case 2:
requested transmit power confirmed requested transmit power not confirmed
(1) requested transmit power confirmed
request TXPWR
CONF_TXPWR = REQ_TXPWR
resume Power Control
(1)
(2)
suspension of PC decision P_CON_INTERVAL
time P_CONFIRM
resume Power Control
(2) requested transmit power not confirmed
Fig. 4
A30808-X5226-C559-1-7618
8-13
Siemens
1.5
Parameters for Power Control Execution

DB Name /Object Range Meaning
Specification Name
MS_TXPWR_MAX MSTXPMAX / BTSB
0...19 GSM maximum TXPWR an MS may use 0...15 DCS in the serving cell * 2 dB 0 = 43 dBm, 15 = 13 dBm (GSM, phase 1) 0 = 43 dBm, 19 = 5 dBm (GSM, phase 2) 0 = 30 dBm, 15 = 0 dBm (DCS) Range for uplink power control: 5 dBm ... MAX (GSM, phase 2) 0 dBm ... MAX (DCS) MAX = Min (MS_TXPWR_MAX, P) P: power class of the MS 0, 1...6 * 2 dB Static reduction of the TRX output power: BS_TXPWR_MAX = P BTS - 2 * BS_TXPWR_RED Range for downlink power control: BS_TXPWR_MAX - 30 dB ... BS_TXPWR_MAX
BS_TXPWR_RED
PWRRED / TRX
POW_INCR_ STEP_SIZE
PWRINCSS / PWRC
DB2, DB4, Step size for power increase DB6 DB2, DB4 Step size for power reduction
POW_RED_ STEP_SIZE
PWREDSS / PWRC
P_CONFIRM
PWRCONF / PWRC
1...31 Maximum interval for waiting for a * 2 TSACCH confirmation of the new transmit power level. 0...31 Minimum interval between changes * 2 TSACCH of the RF transmit power level (time for suspension of a power control decision after a power control execution)
P_CON_INTERVA PCONINT L / PWRC
8-14
A30808-X5226-C559-1-7618
Siemens
1.6
Overview
Power and Quality Measurements on Uplink/Downlink TCHs
Long name OMC name BR3.0 short name Function group Number of counters
Power and quality measurements on uplink/downlink TCHs powerAndQualityMeasOnTCHsUplinkDownlink PWRUPDW CHANMEAS (64+8) *2 = 144 64 values, one for each RXLEV band 8 values, one for each RXQUAL band 2 times of these values (uplink, downlink) CC, Integer --TRX per TCH BR3.0 ---
Kind of counters Unit of counters Observed object Measurement depth First release implemented GSM/CCITT reference
Description These performance measurements are based on the radio link measurements RXLEV and RXQUAL (as standardized in GSM 05.08), used in the handover and RF power control processes. This measurements considers the kind of configuration of the Traffic Channel (Fullrate, Halfrate).
A30808-X5226-C559-1-7618
8-15
Siemens
Trigger Events For the selected Traffic Channel in use, the MS received signal level in dBm (reported as RXLEV value) and received signal quality, (equivalent to BER, reported as RXQUAL value) are reported to the BTS at 480 ms intervals. The performance measurements to be processed with these raw data provide for each busy traffic channel: a) the number of times the received signal level exists, as the corresponding RXLEV value (0 to 63), b) the number of times the received signal quality exists, within the corresponding RXQUAL bands The counters per RXLEV/RXQUAL band are implemented in the BTS. One "scanReport" notification is generated at the end of the granularity period and sent by the BTS to the BSC, containing the accumulated value for each RXLEV/RXQUAL band. The measurements on uplink and downlink idle TCHs are always reported together. The RXQUAL- / RXLEV-Bands are separated as follows: RXQUAL_0: RXQUAL_1: 0.2% RXQUAL_2: 0.4% RXQUAL_3: 0.8% RXQUAL_4: 1.6% RXQUAL_5: 3.2% RXQUAL_6: 6.4% RXQUAL_7: 12.8% BER = Bit error rate < < < < < < < BER < 0.2% BER < 0.4% BER < 0.8% BER < 1.6% BER < 3.2% BER < 6.4% BER RXLEV_62: -49 dBm... -48 dBm > -48 dBm BER < 12.8% RXLEV_63: RXLEV_0: RXLEV_1: RXLEV_2: <-110 dBm -110 dBm... -109 dBm -109 dBm... -108 dBm
8-16
A30808-X5226-C559-1-7618
Siemens
Discontinuous Transmission DTX
The goal of DTX is to reduce MS power consumption and to reduce the interference in a cell. Each direction of transmission is occupied about 50% of time. DTX is a mode of operation where the transmitters are switched on only for those frames containing useful information. The difficulty is to find techniques to distinguish noisy speech from real noise even in a noisy environment. These algorithms are implemented in the VAD (Voice Activity Detection) function. The background acoustic noise has to be evaluated in order to transmit characteristic parameters to the receive side. The receive sides generates a similar noise called comfort noise during periods where the radio transmission is cut.
SBS parameter for DTX / VAD administration: Specification Name Object/ Package DB Name DTXUL Meaning 0: MS may use DTX (if possible) 1: MS shall use DTX 2: MS shall not use DTX FALSE: downlink DTX disabled at BTS TRUE: downlink DTX enabled at BTS
DTX indicator uplink BTS/BTS O DTX indicator down-link BTS/BTS O
DTXDL
A30808-X5226-C559-1-7618
8-17
Siemens
The goal of DTX is to reduce the speech data rate from 13 kbit/s (user speaking) to 500 bit/s. This low rate is enough to encode the background noise. This means instead of one frame of 260 bits per 20 ms only one frame per 480 ms is sent. These so called SID frames (Silence Descriptor Frames) are sent at the start of every inactivity period, then all 480 ms, as long as the inactivity lasts between BTS and MS. Between TRAU and BTS these comfort noise frames are sent all 20 ms. The time behavior looks like following: TRAU <-> BTS SSSSCCCCCCCCCCCCCCCSSCCCCCCCS BTS <-> MS SSSSC where C C C SSC C S
S = speech frame C = comfort noise frame
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
8-18
A30808-X5226-C559-1-7618
Siemens
The so called TRAU frame contains not only these 260 bit: number of bits, UL frame synchronization discrimination: speech, data, full rate, half rate time alignment bad frame indication DTX mode other info speech spare 35 5 6 1 1 3 260 5 1 1 260 9 number of bits, DL 35 5 6
Contents of a speech block for transmission at 16 kbit/s, details in GSM 08.60
A30808-X5226-C559-1-7618
8-19
Siemens
3
3.1
Channel Allocation Due to Interference Level

General
The BTS performs measurements of the (uplink) received level on all its idle traffic channels (TCHs) in the same way as for the busy channels, i.e. the level values in [dBm] in each TDMA frame are averaged over one SACCH period. The averaged value is mapped on an RXLEV value (0, ..., 63). Since these measurements are related to idle channel the measured level is interpreted as interference level caused by a mobile in another cell using this channel or an adjacent channel (or by an external source of interference). The information on the interference level can be taken into account at channel selection to assign the channel with the lowest interference level which is expected to guarantee the best link quality. An improvement of link quality by this mechanism is only possible if there is a choice, i.e.
l l
in cells with low traffic load where some idle channels are available for assignment if the interference level on idle channels differs significantly (this is not the case if random frequency hopping is applied).
The following section describes the classification and selection of traffic channels due to interference level in more detail. Having measured the interference level for some SACCH multiframes, an arithmetic mean RXLEV_IDLE of a certain number of successive interference level samples, given by a parameter INTAVE, is calculated if the channel has been idle for the whole measurement period INTAVE * TSACCH .
8-20
A30808-X5226-C559-1-7618
Siemens
Using this averaged interference level, an idle traffic channel is classified as a channel of Interference Band 1 if Interference Band 2 if Interference Band 3 if Interference Band 4 if Interference Band 5 if 0 X 1 X 2 X 3 X 4 < RXLEV_IDLE < X1 X2 X3 X4 X5 = 63
< RXLEV_IDLE < < RXLEV_IDLE < < RXLEV_IDLE < < RXLEV_IDLE <
where X1, X2, ... X5 denote the boundaries (O&M parameter) of the five interference bands. 0 < X1 < X2 < X3 < X4 < X5 = 63
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21
A30808-X5226-C559-1-7618
Siemens
RXLEV_IDLE
low quality
X5 Interference Band 5 X4 Interference Band 4 X3 Interference Band 3 X2 Interference Band 2 X1 Interference Band 1 0 high quality
Fig. 5
If a traffic channel has not been idle during the whole measurement period, it is not taken into account in the classification procedure. Having classified all the traffic channels which have been idle during the whole measurement period, the TRX immediately sends the result of this classification to the BSC (RF Resource Indication message) where it is used in the channel allocation process. The period for sending the RF Resource Indication message can be set by a parameter RF_RES_IND_PERIOD.
8-22
A30808-X5226-C559-1-7618
Siemens
The time relations between measurements in the BTS and information sending to the BSC is illustrated in the figure below. In the case of a call setup as well as in the case of a handover a traffic channel out of the best non-empty interference class is allocated. A condensed form of the information on the quality of the idle traffic channels at a certain BTS is sent from the BSC to the MSC using the RESOURCE INDICATION message. This message contains, for a specified cell (BTS), the number of idle TCHs which are available separately in each of the five interference bands.
RF resource indication period RF_RES_IND_PERIOD = 15 averaging period INTAVE = 5 averaging period INTAVE = 5
time
SACCH_ Multiframe
RF RES IND (TRX -> BSC)
RF RES IND (TRX -> BSC)
Fig. 6
A30808-X5226-C559-1-7618
8-23
Siemens
3.2
Parameters for Channel Allocation due to Interference Level
The parameters are administered in the object BTS in the package BTSI and are listed in the table below. Specification Name EN_INT_CLASS INTAVE DB Name INTCLASS INTAVEPR averaging Period Range Meaning
TRUE/ Flag to enable the classification FALSE procedure in the BTS 1...31 Period for averaging the measured * T SACCH interference level. A traffic channels which has not been idle during the whole measurement and averaging period, it is not take into account in the classification procedure. 0...63 Boundaries of the interference classes/ bands.
X1, X2, ..., X5
INTAVEPR interference Thresholds Boundaries
RF_RES_IND_PERIO RFRSINDP D
1...254 Period for sending the classification * T SACCH information to the BSC.
Relations: 0 < X1 < X2 < X3 < X4 < X5 = 63 INTAVE < RF_RES_IND_PERIOD
8-24
A30808-X5226-C559-1-7618
Siemens
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A30808-X5226-C559-1-7618
8-25
Siemens
3.3
Overview Long name OMC name
Interference Level Measurements on Idle TCHs
Interference level Measurements on idle TCHs interferenceLevelMeasOnIdleTCHs ILUPLKIC TRXMEAS 5 * No. of idle TCHs one value for each of the 5 interference bands CC, Integer --TRX per idle TCH, per interference band BR3.0 ---
BR3.0 short name Function group Number of counters Kind of counters Unit of counters Observed object Measurement depth First release implemented GSM/CCITT reference
Description The measurement "Interference measurements on uplink idle TCHs" provides the number of times the measured RXLEV value on the idle TCHs exists within the appropriate interference bands. This measurement is executed per selected cell.
8-26
A30808-X5226-C559-1-7618
Siemens
Trigger Events This performance measurement is based on the radio link measurement RXLEV on idle traffic channels (standardized in GSM 05.08, GSM 08.58), used for definition of the channel allocation algorithm. Interference measurements have to be performed on all idle TCHs of a BTS separately by each TRX. Measurements of the received level are made over every SACCH multiframe period. An arithmetic mean of a certain number of successive interference level measurements shall be calculated. This number is given by the parameter INTAVE. Values are calculated for those TCHs which have been idle during the whole measurement period INTAVE x TSACCH (480ms). The idle TCHs are classified using 5 interference bands. The BTS maps the averaged interference level measurements into these 5 interference bands. The BTS transmits the result of this classification regularly to the BSC using the RF RESource INDication message. These radio link measurement data are used to calculate this proprietary performance measurement within the BSC described below. 'They are also used for execution of the GSM 12.04, Vers. 4.3.0 defined performance measurement Annex B, B.2.1.13: "Mean Number of Idle TCHs per Interference Band".
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-27
A30808-X5226-C559-1-7618
Siemens
4
Title: Task
Exercise
Power Control
Exercise 1
Consider a mobile station (of GSM phase 1) of maximum output power P MS = 39 dBm. Within the cell serving that MS the following parameters are set: MS_TXPWR_MAX = 33 dBm BS_TXPWR_MAX = 43 dBm POW_INCR_STEP_SIZE = 3 (6 dB) POW_RED_STEP_SIZE = 2 (4 dB) Furthermore, the following thresholds for the uplink power control decision are set: L_RXQUAL_P = 4 U_RXQUAL_P = 3 L_RXLEV_P = 20 U_RXLEV_P = 26
In the table below some examples for the measured and average (uplink) RXLEV and RXQUAL as well as for the last confirmed TXPWR are given. What are the corresponding values for the new commended TXPWR? Example last confirmed TXPWR (dBm) 25 21 15 31 17 RXQUAL RXLEV new commanded TXPWR ? ? ? ? ?
1 2 3 4 5
2 4 2 5 5
23 28 30 25 34
8-28
A30808-X5226-C559-1-7618
Siemens
Exercise 2
Title: Task
Consider a cell with the following parameters or interference classification: INTAVE = 2 RF_RES_IND_PERIO = 4 X1 = 10 X2 = 20 X3 = 30 X4 = 40 X5 = 63 The following levels have been measured by the BTS on its channels each SACCH frame Channel Allocation due to Interference Level
chan 1 chan 2 chan 3 chan 4
B B 12 20 1
19 B 14 22 2
21 B 14 18 3
23 B 16 18 4
15 B 14 17 5
15 B 14 18 6 SACCH frame B: busy channel
Last RF Resource indication message
To which interference bands do channel 1-4 belong at SACCH frame 7? Which channel is allocated this time in the case of an assignment request?
A30808-X5226-C559-1-7618
8-29
Siemens
Exercise 3
Enable the power control mechanism and create the related scanner
8-30
A30808-X5226-C559-1-7618
Siemens
Contents
1 2 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 3 General Hints Standard Symptom Saving LMT Logfiles OMC Logfiles Database Network Element Event Logging A-Interface or Abis Trace with K1103 A / Abis-Interface Trace with K1205 Abis Interface Trace with MA10 Air Interface Trace with TEMS Measurements with Scanners Exercise 3 4 4 5 7 10 11 12 17 17 19 26
A30808-X5226-C559-1-7618
9-1
Siemens
9-2
A30808-X5226-C559-1-7618
Siemens
1
l l l l l l l l
General Hints
Description of malfunction. What is the suspected origin of the error? What are the functional and hardware related states of the affected system? What are the issues of the affected boards? Check Hardware and Firmware states using the actual customer documentation. Observed system activities? External Influences (Power Supply, Environment)? What has been done (customer, local service staff)? Exact time of error: Synchronize the time stamp of all logfiles if possible. Otherwise determine exact time offsets (to real time) for every logfile.
While creating a Hotline Demand or an Error Report pay attention on the following questions and tasks:
A30808-X5226-C559-1-7618
9-3
Siemens
Standard Symptom Saving
Check and write down the software running at the BSC. Check also the presence and state of the patches (enabled or just activated). If no complete database is available check at least the DB entries of the parameter EXPSWV (Expected Software Version) of all network elements BTSM and TRAU. It is important to verify that an alignment has been performed to all network elements BTSE, TRAU to be sure that the correct SW has been activated already. Otherwise interrogate the SW locally using LMT.
2.1
LMT Logfiles
With every login at BSC, BTSE or TRAU with the LMT logfiles are created. These logfiles can be copied to a floppy disk and can be sent to your next TSC level.
9-4
A30808-X5226-C559-1-7618
Siemens
2.2
OMC Logfiles
Error logfiles and Alarm reports can be saved from OMC-B to floppy disk from each network element by using the following commands: Do see ErrorLog select all Report Save [select save on floppy] [select DOS-File System] ok or Do see active Alarms select all Report Save [select save on floppy] [select DOS-File System] ok
A30808-X5226-C559-1-7618
9-5
Siemens
It is also possible to convert the files from binary format into ASCII format with the tool AlarmConv and export the alarmlogfile from the ORACLE DB into a generic file: General Summary Panel OMC-Operational OMC-Data Handler Do export ASCII Alarms Select: Name B . . . . D for example BMA01D Start date End date
The output file will be in the directory (under UNIX) /users/omcws/ft_common/data/OMC/generic with the name A_B. . . . D_<start date>_<end date>.exp The file can be copied under UNIX also on disk.
9-6
A30808-X5226-C559-1-7618
Siemens
2.3
Database
The BSC database can be uploaded to LMT or OMC-B and can be converted into ASCII format using the tool DBAEM.
2.3.1
LMT-Procedure
Upload of the DBFILE.DBA from BSC harddisk (DK40) into LMT directory. The DBFILE.DBA-file must be in the directory: DBAEM/<Site Name>/DBINPUT After the DBFILE.DBA-file has been uploaded to the LMT, it can be converted to an ASCII file. Change to the directory that contains the DBAEM-software (DBAEM.EXE) and enter the following command at the DOS-prompt: DBAEM CREATE_CMD <Site Name> The ASCII file with the name CMDxxxxx.ASC will be created in the site directory, It is now possible to read or edit the ASCII file (CMDxxxxx.ASC).
A30808-X5226-C559-1-7618
9-7
Siemens
2.3.2
Steps:
OMC-B Procedure
a) upload the Database from BSC harddisk (DK40) BSS-Panel Icon SW-handling Action Do upload alldba specify: source dir: backup (BSC-Directory) target dir: dba/backup (OMC-Dir) The DBFILE.DBA-file will be stored in the OMC directory: ...ft_common/data/B.D /dba/backup (B.....D is the name of the BSC in the OMC) b) when the upload is finished open the Database Emulation tool (DBAEM) select: Configuration DBA Tools DBAEM (select the actual SW version of DBAEM) CREATE CMD select from Files the actual BSC (B.D) the DBFILE.DBA-file is converted into a readable ASCII file This ASCII file can be opened with the text editor from the OMC Directory: ../ft_common/data/DBAEM/acl The name of the file is: dbB.D.acl.brxx The file can be modified and must be saved under the same name.
9-8
A30808-X5226-C559-1-7618
Siemens
c) Conversion of the readable ASCII-file into binary DBFILE.DBA-file select: Configuration DBA Tools DBAEM (select the actual SW version of DBAEM) CREATE DB select from Files the actual BSC (B.D) The readable ASCII file is converted into the binary DBFILE.DBA-file. The DBFILE.DBA-file is saved automatically and always in OMC directory ../ft_common/data/B.D/dba/new and can be copied to floppy disk.
A30808-X5226-C559-1-7618
9-9
Siemens
2.4
2.4.1
Network Element Event Logging

BTSE Alarm Buffer
In the BTSE errors and internal activities are reported to a file which is stored on the Flash EPROM. The analysis of this file allows a deeper understanding of the events and the systems behavior e.g. before an error occurred. The file containing this messages can be uploaded to the LMT from the Flash EPROM and can be evaluated offline using a special tool to convert the binary information to a readable ASCII text.
2.4.2
TRAU Event Logging
In the TRAU errors and internal activities are reported to a file which is stored on the Flash EPROM. The analysis of this file allows a deeper understanding of the events and the systems behavior e.g. before an error occurred. The file containing this messages can be uploaded to the LMT from the Flash EPROM and can be evaluated offline using a special tool to convert the binary information to a readable ASCII text.
2.4.3
BSC Event Logging
A fully automatic Event logging function has been introduced for the BSC with BR4.0. Up to BR3.7 changed state event reports and failure event reports are buffered in the ME2M module. When a LMT is connected to the BSC, it will receive these messages. Since BR4.0, changed state event reports and failure event reports are first collected in the ME2M and then periodically written to the DK40. Four files are used, which are called SBS1.LOG, SBS2.LOG, SBS3.LOG and SBS4.LOG. These files stored in the directory LOG are cyclically used to emulate a circular mode. An upload of these files is possible using the common UPLOAD command. Further processing has to be done in order to convert the information from binary to ASCII format.
9-10
A30808-X5226-C559-1-7618
Siemens
2.5
Recording
A-Interface or Abis Trace with K1103
To record a trace on a file select from main menu: Open recording file Specify a filename xxx.rec (for example: test.rec) Two recording methods are available: cyclic: the first records will be overwritten when the recording file reaches its maximum size: "first in - first out" Linear: the data are not overwritten when the recording file reaches its maximum size click on " open file " Select from main menu: Recording Start recording The traces can be monitored also in the online monitor, additionally the traces are stored now in the specified recording file. To stop the recording select from main menu: Recording Stop recording Recording Close recording File
A30808-X5226-C559-1-7618
9-11
Siemens
2.6
A / Abis-Interface Trace with K1205
Recording data The right side of the window Measurement Scenarios contains a pipeline branch with the processing element Recording File, which displays a file icon. NONE signifies that no recording file has been created. Click the processing element Recording File to create a recording file.
9-12
A30808-X5226-C559-1-7618
Siemens
Fig. 1
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13
A30808-X5226-C559-1-7618
Siemens
The Recording Write Configuration dialog box opens: Click to the right of c:\k1205\rec\ in the File Name field and enter a name for the recording file. Storing all your recording files in c:\k1205\rec\ facilitates the search for individual files later on. Press Browse to locate an existing file. You do not need to enter the file extension .rf5 for K1205 recording files when entering the file name. The program appends it automatically. The remaining settings (Open Mode and File Size) are optional. Click "Close the file after each opening of the switch" to ensure that the file closes properly. Confirm your entries with "OK". The name of the recording file appears in the processing element "Recording File". To start recording, click the "ON/OFF Switch" of the recording pipeline branch to "ON".
9-14
A30808-X5226-C559-1-7618
Siemens
Fig. 2
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
A30808-X5226-C559-1-7618
9-15
Siemens
The signaling data of the activated data flow are written to the recording file until the file is full or until you terminate the process. The data in the recording file can be read after the current measurement is complete. You can stop recording by clicking the "ON/OFF Switch" of the recording branch to "OFF". In most cases, data are recorded and reviewed at different times. It is possible to check the contents of the recording file immediately after having recorded the data.
Fig. 3
9-16
A30808-X5226-C559-1-7618
Siemens
2.7
Abis Interface Trace with MA10
MA10 traces are stored under a specific filename *.sig. The file can be copied to floppy and sent to the next TSC level.
2.8
Air Interface Trace with TEMS
Using log files, it is possible to store messages or sequences as they occur and to replay them later for a more detailed examination. TEMS automatically creates default file names for the logfiles: MMDD_X.log (MM means the month, DD stands for the day and X is an increasing counter). The saving of the logfiles can be performed either manually or it can be initiated by an automatic logging procedure: Select Log Select Start logging or Select Log Select Automatic logging
Fig. 4 The Save logfile window
A30808-X5226-C559-1-7618
9-17
Siemens
It is possible to choose a set of messages which shall be logged: Select Log Select Log setup
Fig. 5 The Define and start automatic logging window
Fig. 6 The Log setup window
9-18
A30808-X5226-C559-1-7618
Siemens
2.9
2.9.1
Measurements with Scanners

Overview Scanner Commands
There are the following MML Commands to administrate the performance measurement Scanner :
l
ACTIVATE SCAN... This command provides a report of the partial results, collected after the last report, related to the instance. The report mode has been already selected in the configuration phase.
CREATE SCAN... This command creates the configuration of instance of the scanner managed object class. The parameters specify the values for the scheduling and reporting activities.
DELETE SCAN... This command deletes a scanner instance which has been previously created. GETINFO SCANCO... This command enables the operator to get a list of the created scanners and for each scanner its most important information, as the number of configured scanners, current, temporary and maximum logfile size, scanner id, scanner name, measure class, administrative state, availability state, reporting type, granularity, start date, stop date, periodicity, amount of objects defined and esteem of a daily usage.
GET SCAN... This command shows the parameters of an existing scanner instance. GET SCAN STAT... This command allows to display the administrative, operational and usage state and all the status attributes of a specified object.
GETSUBO SCAN... This command allows to display the list of direct subordinate objects of a specified object.
INHALL BSC... When the command is entered, the SCAN.TMP file is renamed in SCAN.LOG, then it is put into the UPL_READY directory where there are the files ready to be uploaded by OMC.
LOCK SCAN... This command allows to set an object to the administrative state "Locked". The command can be rejected due to high criticity of the system state, so the forced parameter allows the operator to skip this criticity checks.
A30808-X5226-C559-1-7618
9-19
Siemens
SET SCAN... This command sets the configuration of instance of the scanner managed object class. The parameters specify the values for the scheduling and reporting activities.
UNLOCK SCAN... This command allows to set an object to the administrative state "Unlocked". UPLFILE... Loads a BSC disk file (e.g. SCAN.LOG, binary result file for scanners created by file) to the LMT.
9-20
A30808-X5226-C559-1-7618
Siemens
2.9.2
Performance Measurement Handling

Meas. by Event max. 10 Scanner Meas. by File max. 90 Scanner - Upl. by Hand - Upl. Scanlog > 3MB
BTS transfer of BTS data
BSC
OMP
Internal Files
SCANLOG SCANTMP
Oracle
storage of counter PWRUPDW, BTSEPRLD, IFRMABIS, ILUPLKID
S I M E N E S N I X D O R F
LMT export of Scanner to Ascii with Offline Tool
OMT export of Scanner to Ascii
Fig. 7
A30808-X5226-C559-1-7618
9-21
Siemens
The scanner object definition specifies also the reporting style adopted for each measurement job. This can be:
l l
by message: the results are directly sent to LMT or OMC. by file: the results are stored in a file called "SCAN.LOG" in the directory "MEASURE_DIR" on the DK40.
Normally the operator can specify the reporting style when he creates a scanner; in few cases there are restrictions. The measurement LOG file must be uploaded on OMC or on the LMT local disk on a daily basis. On LMT, a specific off-line tool called MRV enables the operator to browse the contents of this file. After the upload, the LOG file must be deleted. An important restriction concerns the maximum scanner LOG file size, which is configurable between 1 and 6 Mbytes. A check is done whenever a new scanner is created, to control the size of the related report. If this size would exceed the maximum scanner LOG file size, a loss of information may happen. As soon as the operator sends a CREATE SCAN command, the system verifies the whole size of the required daily LOG file. If this is greater than the maximum allowed, a NACK message is sent.
9-22
A30808-X5226-C559-1-7618
Siemens
2.9.3
l l l l
Performance Measurement Handling Features at the LMT
There are the following possibilities for Performance Measurement Handling Administration of scheduled measurement tasks Performance measurement logging, retrieving and handling Requesting the Current Measurement Values of a Scanner Job immediate output of actual Scanner data with the command ACTSCAN Export of Measurement data in ASCII file will be done after upload with a Offline conversion tool on the LMT
A30808-X5226-C559-1-7618
9-23
Siemens
2.9.4
l l l
Performance Measurement Handling Features at the OMC
There are the following possibilities for Performance Measurement Handling Administration of scheduled measurement tasks Performance measurement logging, retrieving and handling Graphical representation of measurement results Data viewer for measure selection Data viewer for measure details Data viewer for measure graphs
l
Upload and Conversion of measurement data Upload request Automatic upload request Uploading of measure file on the Network Element is automatically performed when the size of the file SCAN.LOG reaches the 3Mbyte. Conversion request
Export of Measurement data in ASCII file
Measurement files can be saved from OMC-B to floppy disk from BSS- Icon: Do see Measures [select: events since up to symbolic name] show select all Report Save [select save on floppy] [select DOS-File System] ok
9-24
A30808-X5226-C559-1-7618
Siemens
It is also possible to convert the files from binary format into ASCII format with the tool MeasConv and export the measurement files from the ORACLE DB into a generic file. General Summary Panel OMC-Operational OMC-Data Handler Do export ASCII Measures Select: Name B . . . . D - for example BMA01D Start date End date
The output file will be in the directory (under UNIX) /users/omcws/ft_common/data/OMC/generic with the name M_B. . . . D_<start date>_<end date>.exp The file can be copied under UNIX also on disk.
A30808-X5226-C559-1-7618
9-25
Siemens
Exercise
Exercise
Sum up all the possibilities you have to perform an Error Symptom Saving. Possibility Remarks
9-26
A30808-X5226-C559-1-7618
Siemens
Contents
1 1.1 1.2 1.3 1.4 2 2.1 2.2 2.3 IMSI Tracing Introduction to IMSI Tracing Settings in MSC and BSC Databases Signaling Procedure Description Cell Traffic Recording Introduction to Cell Traffic Recording CTR Initiation and Termination Procedure Description 3 4 4 6 7 12 12 13 16
A30808-X5226-C559-1-7618
10-1
Siemens
10-2
A30808-X5226-C559-1-7618
Siemens
IMSI Tracing
Fig. 1
A30808-X5226-C559-1-7618
10-3
Siemens
1.1
Introduction to IMSI Tracing
The feature IMSI tracing allows the BSC to trace a subscriber during a call or a short message transfer. As the maximal number of traces within one BSC (and at the same time) is seven, this feature will not be used to trace anybody. The operator will use the feature to get information on its own network to point out problems or to improve its quality. If a particular problem appears in a network-area, e.g. a subscriber complains of the quality in a special area, a tester may travel through this area with active TEMS or the operator activates IMSI Tracing for this special subscriber. The BSC collects the information and uploads them to the OMC. At the end of the test, the operator can analyze the collected signaling and radio information to find out the source of the problem.
1.2
Settings in MSC and BSC Databases
To run the IMSI tracing in the network, some database modifications are necessary in the MSC and in the BSC. The IMSI tracing feature requires no special mobiles.
l
In the MSC database: The SW-version SR6.0 supports the BSS IMSI tracing by sending the phase2 message MSC_Invoke_Trace. The previous version supports an MSC-internal connection-tracing but does not send the message MSC_Invoke_Trace needed by the BSC BR4.0 to start the trace collection. The feature must be first activated: MOD MSERVREL:FEAT=IMSITRAC,RELSTAT=REL; ACT MSERVOPT:FEAT=BSSTRAC; The IMSI tracing should be activated for the concerned subscriber: ACT IMSITRAC:MSIN=2600001001,REF=X,TYPE=CSMSNORM or CSMSPRIO; MSIN: REF: TYPE: MSUB Identification number Trace Reference Number Trace Type
In the BSC database: In the BSC the database object TraceControl should be created. This could be done with the LMT or OMC. LMT: BSC/TRACE/CREATE TRACE Record_Criteria=No_Criteria OMC: BSC Summary / Icon BSC / Action / doCreateTraceControl (No_Criteria).
10-4
A30808-X5226-C559-1-7618
Siemens
BSC
OMP
Fig. 2 IMSI Tracing
A30808-X5226-C559-1-7618
10-5
Siemens
1.3
Signaling
The BSC starts the trace collection after reception of the message MSC_Invoke_Trace. The MSC sends this message every time a subscriber with IMSI tracing active sets up a call (MOC/MTC) or a MSC-controlled handover takes place or a short message is sent. The BSC sends the Abis message Start_Trace to the BTS for the concerned timeslot. The BSC also sends the message TraceStartedNotification to the OMC and to the LMT. The BTS sends back regularly (every 0.5 seconds) the messages Trace_Measurement_Result which contains the Measurement_Reports from the mobile and the uplink measurements from the BTS. At the end of the call, the BTS receives RF_Channel_Release and stops the sending of the Trace_Measurement_Result. The BSC stops the trace collection and sends the message TraceStoppedNotification to the OMC and to the LMT. The BSC uploads the compressed trace-files to the OMC. The OMC decompresses them and converts them to ASCII. At the end of a call (or short message transfer), whatever the reason for the release is, the BTS sends the Trace_Measurement_Results not anymore. The BSC may send the message Stop_Trace on the Abis if the operator lock the database object TraceControl. This message is not acknowledge by the BSC.
10-6
A30808-X5226-C559-1-7618
Siemens
1.4
1.4.1
Procedure Description
Creation of the Trace Control
(BSC Icon (BSC summary) - Action - doCreateTraceControl (No_Criteria)) The TraceControl Icon appears in the BSC summary window.
1.4.2
l
Management of the TraceControl
On the Icon TraceControl, the operator can access with the GET State&Status command the DBA object. Also the functions lock/unlock or delete are present under this Icon. GetInfoReport: On the Icon TraceControl, the operator can access GET InfoReport of the DBA object.
Message ErrorTraceNotification: This warning message is collected in the windows seeErrorLog from the concerned BSC.
In the BSC Basic package, the parameter ProFailEvent from erract should be set to FERMAINT. The messages StartTraceNotification, StoppedTraceNotification and UploadRequest are stored in the windows SeeSWEvent. This window is selected by Activating the SeeSWEvent under the BSC Icon from the BSC summary.
A30808-X5226-C559-1-7618
10-7
Siemens
1.4.3
Retrieving of recorded Trace Data
If any call setups or releases will be done by the appropriate IMSI-owner, the traces will be recorded and stored into different LOG-files (one for each trace) on the DK40 in the TRACE directory . If you want to retrieve this data, you have to upload the IMSI-file. For this purpose you have to know the Trace Reference number.
1. Retrieval of Trace Reference Number Before you can upload IMSI traces you have to retrieve the Trace Reference Number. From BSS icon in BSS Network Summary panel select: Action -> Do GetInfoReportTrace In detail the information retrieved through the use of this service are the following:
l
General information: 1. current value of the administrative state 2. current value of the operational state 3. current value of the usage state 4. current value of the record criteria (always NoCriteria)
List of the active mobile traces (max. 7) and for each one the following information: 1. trace reference 2. IMSI (International Mobile Station Identity) 3. trace type 4. trace start time 5. current imsi file size
10-8
A30808-X5226-C559-1-7618
Siemens
List of the last 5 mobile trace terminated and for each one the following information 1. trace reference 2. IMSI (International Mobile Station Identity) 3. trace type 4. trace start time 5. trace stop time List of file names to be uploaded and for each one the correspondent size.
2. Upload of IMSI file All trace files belonging to the same Trace Reference number will be uploaded to the OMC. From Trace Control icon in BSS panel select: Action -> Do uploadIMSIfile All trace files on DK40 belonging to the same Trace Reference number will be compressed to one single file and this compressed file will be uploaded to the OMC. The compressed file for BR 4. is moved into the directory defined by the environment variable named PLMNDIR (/ft_common/data/plmn) and it is renamed according to the following rule: bssCode_RdnRegion_RdnDistrict_RdnBss-DDMMYY-hh:mm:ss-IM-40.ZIP bssCode = name of the BSS RdnRegion = relative distinguish name of the Region RdnDistrict = relative distinguish name of the district RdnBss = relative distinguish name of the BSS DD-MM-YY-hh:mm:ss = date and time of the upload termination
A30808-X5226-C559-1-7618
10-9
Siemens
Now the automatic decompression mechanism will take place and the decompressed binary files are moved in a directory defined by the environment variable: SAVEIMBINARYFILEDIR (/ft_common/data/binaryimsifiles) and renamed with a new name which has the following format: BSSCode_RegId_DistrId_BssId-DATE-IM-VER-LOGFILENAME where: BSSCode is the code of the BSS (BAU01D, BRO08D,...) RegId is the region identifier DistrId is the district identifier DATE is the date and file upload time (DD-MM-YY-hh:mm:ss) VER is the version of the BSS (40) IM is the fixed character string IM LOGFILENAME is the original filename of the binary file (T0001001.LOG, T0001002.LOG) Note : The compressed file in PLMNDIR will automatically deleted after successful decompression.
3. Listing of uploaded binary IMSI files (take a look to SAVEIMBINARYFILEDIR) The operator can request the display of all the IMSI Tracing binary files present on the OMP and ready to be converted in ASCII format. From PLMN icon in General Summary panel select: Action -> Do listImsiFile
10-10
A30808-X5226-C559-1-7618
Siemens
This command will foresee that the OMT operator will fill two filtering fields in order to reduce the number of filenames to show. However no more than 50 filenames at a time will be displayed. The filtering fields which shall be filled are the following: BSSCode, in order to identify unambiguously the BSS which is looked for Trace Reference, in order to identify the IMSI traced.
4. Conversion of binary IMSI file to readable ASCII IMSI file The operator can request the conversion of a binary IMSI file in ASCII readable. From PLMN icon in General Summary panel select: Action -> Do convertImsiFile This command will foresee that the IMSI Tracing binary filename interested to the conversion is passed in input. The command output will be: in case of successful, the ASCII converted file. in case of unsuccessful, the error occurred. When the conversion of a binary file will be successfully terminated and the operator will close the ASCII file without saving it, both the binary and ASCII files will be removed from the OMP disks.
A30808-X5226-C559-1-7618
10-11
Siemens
2
2.1
Cell Traffic Recording

Introduction to Cell Traffic Recording
With Cell Traffic Recording or Cell Trace (CTR) a dedicated number of calls within a specified cell can be traced. In contrast to IMSI tracing, CTR is cell related. Furthermore CTR is local to the BSS, i.e. neither a trace invocation is received from the MSC nor the MSC is informed about any cell tracing activities. A new object CTRControl controls CTR activities within the BSS - similar to the object TraceControl in case of IMSI tracing. Per BSS, up to 16 calls (incl. IMSI traces) can be traced simultaneously. IMSI traces take precedence of cell traces. The operator activates a cell trace from OMC/LMT by the O&M command ActivateCTR specifying - among others - the cell in which the trace is running. At a given start time the trace commences taking a specified number of calls under tracing. The trace data recorded are temporarily stored in the BSC. The collected trace data include among others:
l l l l l l l l
BTS ID Trace type Start / end time BSC, TRAU, TRX IDs Measurement reports Radio channel types and descriptions Terrestrial Circuit Identification Code (CIC) Message contents (Abis, BSC-MS)
An active cell trace can be deactivated at any time on a per cell basis via DeactivateCTR. Tracing is disabled for the whole BSS e.g. in case of an overload situation, during a system reset, HW and/or SW error. The relevant recommendations are GSM 12.08, GSM 08.08, GSM 8.58, GSM 4.08.
10-12
A30808-X5226-C559-1-7618
Siemens
2.2
CTR Initiation and Termination
The object "CTRControl" is created by the operator - very similar to the TraceControl object of the IMSI-Tracing feature - to control the CTR tracing activities within a BSS. By activating CTR via CREATE of CTRSCHED the operator defines
l l l l
the cell to be traced, when the cell tracing is done, the maximum number of calls to be traced, the types of data kinds to be collected.
With LOCK of CTRSCHED the operator is able to stop the tracing of a specific cell. Thus, the call tracing in the specified cell is immediately deactivated, independently of the trace scheduling given during the CTR activation. To modify the characteristics of an active cell tracing, the cell tracing has first to be deactivated by LOCK of CTRSCHED and then activated again with the new parameters using SET and UNLOCK of CTRSCHED. The BSS system rejects a further cell trace activation in a cell where cell tracing is already in progress. At a given start time the trace starts taking calls. From this moment only new calls are traced up to the maximum number specified. The maximum number of calls simultaneously being traced per BSS is limited to 16. This number includes cell traces as well as IMSI traces. The maximum number of IMSI traces remains 7. If the maximum number of active traces is reached and an IMSI trace is invoked from the MSC, the IMSI trace has always precedence over the cell trace. This means that, if the maximum number of traces is reached, for one new IMSI Trace activation request one active cell trace is stopped. A cell trace is automatically terminated in one of the following cases:
l l l
expiring of the operator defined trace duration tracing is disabled for the whole BSS (e.g. in case of an overload situation, through the use of the administrative state set) occurrence of a BSS system reset, BSS hardware and/or software errors
In the first case only the trace of the concerned cell is terminated, in all other cases all traces within the BSS are terminated. The CTRControl delete command is available only after the object administrative state has been set to locked. The setting to locked of the administrative state means that all the trace activities on the BSCs are stopped.
A30808-X5226-C559-1-7618
10-13
Siemens
Activation and start of a cell trace Traces are activated for a particular cell with the command: 'CREATE CTRSCHED:NAME=CTRCO:0/CTRSCHED:ctr#, ' The 'CREATE CTRSCHED ' command contains:
l l l l l
Cell ID: The cell in which a trace is started Maximum number of connections traced (this is not to be confused with the maximum number of traces allowed per BSC, range: 1..16) Trace Start Date (optional, default value is 1-1-1992) Trace Stop Date (optional, if not specified tracing can be stopped with an operator command; default expiring value is 31-12-2099) Trace Period Type - ALL (default):the trace is always active between the start date and stop date, - WEEKLY the activation depends from periods list. (optional attribute. Trace Periods: a list of periods, one for every day of the week; every period has start time (hour and minute) and trace duration (in minutes) Trace record type: the kind of data to be collected (possible values are: "message" and "all")
l l
The 'CREATE CTRSCHED' command is rejected if the maximum number of connections traceable in a BSS, considering all the scheduled periods, is exceeded (UNSUCCESSFUL_TOO_MANY_TRACES). A cell trace is started if its administrative state is UNLOCKED and its operational state is ENABLED. Cell Traffic Recording is enabled in the BSS (CTRCO is UNLOCKED and ENABLED) when the scheduled time of the trace schedule is reached. The target cell must be EQUIPPED, UNLOCKED and ENABLED. When a cell trace is started a Start notification message is sent to OMC/LMT and the next n calls coming in the specified cell are put under tracing where n is the maximum number of connections to be traced in the specific cell as given in the 'CTRSCHED' object. If a cell is configured in a CTRSCHED instance, all subsequent 'CREATE CTRSCHED' commands, related to the same cell, are rejected if the scheduled periods overlap (UNSUCCESSFUL_CELL_ALREADY_TRACED).
Change stop and start of a cell trace Cell tracing activities can be modified by command from OMC and LMT: 'SET CTRSCHED:NAME=CTRCO:0/CTRSCHED:ctr#, ' The 'SET CTRSCHED' command specifies:
10-14
A30808-X5226-C559-1-7618
Siemens
l l l l l
Cell ID The cell in which a trace is started Maximum number of connections traced (this is not to be confused with the maximum number of traces allowed per BSC, range: 1..16) Trace Start Date Trace Stop Date Trace Period Type ALL: the trace is always active between the start date and stop date WEEKLY: the activation depends from periods list Trace Periods: a list of periods, one for every day of the week; every period has start time (hour and minute) and trace duration (in minutes) Trace record type: the kind of data to be collected (possible values are "message" and "all")
l l
The 'SET CTRSCHED' command is rejected if the maximum number of connections traceable in a BSS is exceeded (considering all the scheduled periods). The SET CTRSCHED:ctr# on a cell just under tracing stops the trace activities. This activities restarts according with the new scheduled periods. After the SET CTRSCHED command the behavior of the ctr# instance is the same as for the CREATE CTRSCHED command.
Deactivation and termination of a cell trace Cell traces are deactivated by O&M commands: 'LOCK CTRSCHED:NAME=CTRCO:0/CTRSCHED:ctr#' 'DELETE CTRSCHED:NAME=CTRCO:0/CTRSCHED:ctr#' The trace in the specified CTRSCHED instance is then deactivated immediately regardless of the schedule. Additionally, a cell trace is automatically terminated in one of the following cases:
l l l l l l l
expiration of the operator defined trace scheduling entering the SET CTRSCHED command on the same ctr# tracing is disabled for the whole BSS (e.g. in case of an overload situation) bring-up or full initialization loading the data base locking the CTR Control Object system reset, hardware and/or software errors
In the first two cases the trace of the concerned cell is terminated, in all other cases (i.e. also in case of an overload situation) all traces within the SBS are terminated. When a cell trace is stopped, a "Stop notification" message is sent to OMC/LMT.
A30808-X5226-C559-1-7618
10-15
Siemens
2.3
2.3.1
Procedure Description
Tracing of Connections within a Cell
When a trace in a cell is started, the next n calls established in the cell are put under tracing where n is the number of connections to be traced as specified in the CTRSCHED object. Only connections using TCHs with mode other than signaling only (no matter whether they are fullrate or halfrate TCHs) are traced. This means that in case of a direct assignment the call is traced from the moment the TCH mode changes from signaling only to speech/data. If the trace of a connection is terminated (e.g. due to connection failure, connection release) the next connection established in the cell and using a TCH with mode other than signaling only is put under tracing. The trace of a connection is terminated in one of the following cases
l l l l l
call release internal intercell handover (after a certain period of time, see below) external handover abnormal loss of a call (e.g. connection failure) privileged incoming IMSI trace
Call release, external handover, abnormal loss of a call (e.g. connection failure) The trace of the connection is terminated after a full release of all resources (TCH, links) in the cell. Internal intercell handover If a connection is handovered to an internal neighbor cell and the handover is controlled by the BSC (internal intercell handover) the connection is traced in the old cell as long as the resources are not yet fully released. Additionally this connection is traced in the new cell as soon as the resources in the new BSC are allocated. If the handover has been performed successfully, the trace continues on the target cell for a certain period of time ("trace handover persistence time", ca. 10 s). During this time interval, n-1 traces are active in the original cell and one (more) trace is active in the target cell. The number of calls under tracing for a specific cell always includes the call that have performed handover and are currently under persistence time. As soon as the tracing in the new cell is terminated, a new connection in the original cell can be started. From this time again n traces are active in the original cell. If during the trace handover persistence time the call is released or once again handovered the trace of this connection is terminated and on the originating cell a new connection can be taken under tracing.
10-16
A30808-X5226-C559-1-7618
Siemens
Privileged incoming IMSI trace The number of connections to be traced, both by means of IMSI trace and CTR, is limited. Every time a cell trace is configured the BSC checks how many calls are already under tracing by rejecting the trace activation command if the maximum number of traced connections in the BSC is exceeded. However a privileged procedure for IMSI traces is introduced: If an MSC_INVOKE_TRACE message is received from the MSC (i.e. an IMSI trace in the BSS is requested) and the maximum number of connections allowed per BSS are already under trace, the IMSI trace (if less than 7 IMSI traces are currently running) is accepted and the tracing of one connection of CTR is terminated. The limit of maximum 7 IMSI traces simultaneously running is still valid. The incoming IMSI trace request is served immediately. There is not any delay in the service of the MSC_INVOKE_TRACE message caused by cell tracing.
2.3.2
l l
CTR Trace Data Recording
The following types of CTR data can be collected by the BSS: Messages: Event data only All: Event data and measurement results
The operator specifies the types of data to be collected for each cell trace separately. For this he uses the attribute 'Trace record type' in the SET or CREATE command of CTRSCHED.
2.3.3
State Management Attributes
The CTRControl object has the state management attributes associated. Through the handling of the values of these attributes, the current state of the CTRControl object is shown with a graphic representation and the OMT operator is able to control the Cell Trace activity. The tracing activity is possible when the operational state value is enabled, while disabled value means that the BSC could be in an abnormal state which inhibits the tracing (i.e. overload condition, etc). The OMT operator is able to stop all the trace sessions on a BSC through the setting of the administrative state to 'locked'. The shutting down value for the administrative state means that the current connection traces in the cell is finished, but no new connections are taken under tracing. When all the active traces are terminated the administrative state changes automatically to locked value.
A30808-X5226-C559-1-7618
10-17
Siemens
The usage state of the CTRControl object reports the information related to the capacity of the BSC to trace one more call: the idle value means that no tracing is running on that BSC, active means that at least one tracing session is running but the BSC is able to start a new one, busy means that the maximum number of tracing session (maximum 16 per BSC) has been. As for tracing sessions there are not differences between IMSI and Cell Trace, so that, the busy state does not mean that all the active tracing sessions are Cell Tracing. The usage state can be requested with the GetStateAndStatus command.
2.3.4
Trace Events
The new entity manages the receiving from the BSC of new SW events related to Cell Tracing activity. The following information is logged into the OMP database:
l l l
the start of a Cell Trace data collection session; the stop of a Cell Trace data collection session; the notification of trace file upload request successfully completed.
The retrieve procedure of these Cell Trace events is also supported.
2.3.5
Trace Alarms
In case of failures concerning tracing activities the new CTRerror alarm is sent to OMC. It is a processing alarm with severity warning. No related ceased alarm is available. A suitable command is provided in order to retrieve the new trace alarm from the database.
2.3.6
Get Info Report Cell Command
A service which provides full information about the Cell Trace sessions in progress on a BSC is provided to the OMT operator (GET INFOREPORT CELL). This command is very similar to the already implemented GetInfoReportTrace command.
10-18
A30808-X5226-C559-1-7618
Siemens
2.3.7
Logfiles Management and Upload Administration
For Cell Trace as well as IMSI Trace, the data collected are stored on BSC hard disk and then uploaded to the OMC system. For Cell and IMSI Trace the data collection by event is not foreseen. The OMC system can proceed with the upload operation in two ways: automatically, if the BSC system requests explicitly the upload since one or more logfiles are ready to be uploaded, or manually, if the OMT operator requests the upload. A set of trace files ready to be uploaded, requested both automatically and manually, are transferred from BSC to OMC through the upload of a single compressed file. The compressed file upload and decompression service is already provided by the Upload and Conversion Data Procedure subsystem which handles all the phases of compression, transfer, decompression and conversion activation for all the measure files (PM, IMSI and also Cell Trace logfiles) managed by the OMC system. Moreover, during the decompression phase the original file is renamed by this subsystem in order to avoid that the files can be overwritten. The OMT operator is also able to manage the size of the Cell Trace logfiles (new parameter CFS-CTR file size, 1-6 Mbyte, defined in the BSC Control Package). Moreover, the OMT operator is also able to browse the CTR logfiles as well as IMSI Trace logfiles. Besides, the operator can
l l l
get the current logfile size set the maximum BSC logfile size upload trace logfiles
The retrieval of the current logfile size of each CTR logfile can be part of the GETINFO-REPORT command result.
2.3.8
Logfiles Conversion
As already provided for the IMSI Trace, also for Cell Trace the translation of the binary Cell Trace logfiles to ASCII is provided (c.f. Action Do convertImsiFile).
A30808-X5226-C559-1-7618
10-19
Siemens
2.3.9
Trace Record and Cell Trace Logfile Generation (in BSC)
Trace record generation One trace record is generated per cell trace. It is generated after a cell trace has been terminated or when the operator enters the switch CTR file command or when the size of cell log exceeds the maximum CTR logfile size in the BSC control object. The trace record contains a trace record header and all trace data related to all calls traced in this cell. Trace data related to a call includes an identifier of the concerned call (SCCP connection number). In case the trace of a connection is continued on the target cell after internal handover the trace data collected on the target cell is written into the same trace record as the trace data collected in the originating cell. Note: The generation of trace records and the storage into the BSC trace logfiles is implemented in a way that a minimum of trace data is lost in case of board reset or BSC bringup / full-init. BSC CTR logfile generation One BSC CTR trace logfile contains a whole or only part of trace record. In general more than one file can be generated from a cell: a file for the trace record is generated after a cell trace has been terminated or when the operator enters the switch CTR file command or when the size of cell log exceeds the maximum CTR logfile size in BSC control object (file ready to be uploaded). The CTR trace logfile (when is ready to be uploaded) is compressed and put in the directory UPL_READY on the BSC DISK. CTR logfile naming A name is assigned automatically to each generated logfile. It contains the cell id and a sequence number. The sequence number is necessary to distinguish logfiles of traces of the same cell. The BSC maintains a sequence number. Each time a new trace logfile is created the sequence number is incremented by one. NAME: Cbbbnnnn.LOG where C is common to all files (trace file identification) bbb is the cell id expressed in hexadecimal form (in upper case). nnnn is a progressive number expressed in hexadecimal form (in upper case).
10-20
A30808-X5226-C559-1-7618
Siemens
2.3.10
l
BSC Trace Logfile Upload Notification
BSC trace logfiles are uploaded using FTAM. The upload can take place: Automatically : every 5 minutes the BSC sends the CTR upload request notification to OMC/LMT with the list of CTR trace logfile ready to be uploaded (OMC uploads this file). Manually : at any time when the operator issues a corresponding upload command (one or all files).
2.3.11
Administration of Cell Traces from CLI
All services for the administration of cell traces are also available at the CLI. This includes
l l l
the BSC CTR logfile handling commands the administrative commands related to the CTRControl object the configuration and administrative commands related to CTRSCHED object
A30808-X5226-C559-1-7618
10-21
Siemens
2.3.12
CTR Monitoring in the OMC/LMT
The operator can issue a command called 'GetInfoReport: CTR' to retrieve the following information about CTR:
l l
attribute values of the object 'CTRControl' List of all the created CTRSCHED giving ctr# cell id administrative state operational state availability status information current connections traced (connection number) maximum number of connections traced elapsed information trace record types start time current BSC logfile size
information about trace files in the BSC available for upload
2.3.13
Trace Administration at the LMT
On the LMT the same functionalities as on the OMC are available. The trace logfiles can also be uploaded by the operator. However, the logfiles within the BSC are not deleted.
10-22
A30808-X5226-C559-1-7618

MN1788 Tac

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

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

MN1788 Tac

Diunggah oleh

Hak Cipta:

Format Tersedia

s

SBS System Specialist TAC

A-Interface/Signaling System CCS7

SBS System Specialist TAC

This document consists of 406 pages.

Organization of Siemens Technical Assistance Center - TAC

2UJDQL]DWLRQ RI 6LHPHQV 7HFKQLFDO $VVLVWDQFH &HQWHU  7$&

Organization of Siemens Technical Assistance Center - TAC

8 8.1 8.2 8.3 8.4

Organization of Siemens Technical Assistance Center - TAC

7$& /HYHOV $FFRUGLQJ WR 6XSSRUW 6HUYLFHV

7$& 7$& 7$&

Siemens Siemens Siemens

Organization of Siemens Technical Assistance Center - TAC

7HFKQLFDO $VVLVWDQFH 7DVNV

Safeguard monitor systems and service availability/system performance in different countries.

Organization of Siemens Technical Assistance Center - TAC

Organization of Siemens Technical Assistance Center - TAC

7RROV XVHG RQ 7$&

AKUHW FEKAT HISTORY

Organization of Siemens Technical Assistance Center - TAC

available on MVS 'HVFULSWLRQ Central DB for faults Central DB for patches

7RRO FEKAT SSG

Organization of Siemens Technical Assistance Center - TAC

3HUIRUPDQFH 3OXV 3URJUDP

2SWLRQDO VHUYLFHV (not available for all product lines)

Basic Software Upgrade Bulletin Board.

Organization of Siemens Technical Assistance Center - TAC

3HUIRUPDQFH 3OXV 6HUYLFH 3RUWIROLRV

Organization of Siemens Technical Assistance Center - TAC

Fault Report Processing

Repair & Replacement Service

Organization of Siemens Technical Assistance Center - TAC

)DXOW 5HSRUW 3URFHVVLQJ

&XVWRPHU LQIRUPDWLRQ &,

collected in all TSC Forwarded to TSC3 analysis and correction

Organization of Siemens Technical Assistance Center - TAC

Reported analyzed processed

Organization of Siemens Technical Assistance Center - TAC

)DXOW 5HSRUW +DQGOLQJ

Error Reports are used to document and describe errors

analysis Error report

Organization of Siemens Technical Assistance Center - TAC

Organization of Siemens Technical Assistance Center - TAC

Organization of Siemens Technical Assistance Center - TAC

Organization of Siemens Technical Assistance Center - TAC

closing of FRs (regional shortcutting)

higher service level

create and edit fault reports (FR) (plausibility checks)

writing and revision of commentaries

statistics in monthly report format

Organization of Siemens Technical Assistance Center - TAC

3URFHGXUH RI )DXOW 5HSRUWLQJ

Organization of Siemens Technical Assistance Center - TAC

F E K A T M V S ER + CI (TSC3) FMERF ER + CI(TSC3) + CI(TSC2) new error ER (TSC2 + TSC1)

Organization of Siemens Technical Assistance Center - TAC

5HFHLYH (5 IRUP DQRWKHU )0(5) 76&76&

Organization of Siemens Technical Assistance Center - TAC

5HSDLU DQG 5HSODFHPHQW 6HUYLFH

Organization of Siemens Technical Assistance Center - TAC

Organization of Siemens Technical Assistance Center - TAC

Organization of Siemens Technical Assistance Center - TAC

2UJDQL]DWLRQ RI 6LHPHQV 7HFKQLFDO $VVLVWDQFH &HQWHU 7$&

7$& 7$& 7$&

5HFHLYH (5 IRUP DQRWKHU )0(5) 76&76&

+:): &RQILJXUDWLRQ 0DQDJHU

20FHQWHU (;&+%$6,6 ,19(1725< 352'8&7'$7$

FKHFNDQGFRQWURO RI+:):WR6: YHUVLRQV RIH[FKDQJH

FRQWURORI UHTXHVWHG +:): PRGLILFDWLRQ