11 Iub Interface Interconnection-32

8/6/2019 11 Iub Interface Interconnection-32

1/32

UMTS _RNS_II_05_20090430

Iub Interface Interconnection

ZTE University


2/32

Content

Alarm troubleshooting

Viewing SSCOP link

Viewing common channel

Viewing NBAP signaling

Testing servicesNodeB fault collection


3/32

Alarm Troubleshooting


4/32


5/32

Alarm Troubleshooting


6/32

Content


Viewing SSCOP link





7/32

Viewing SSCOP Link


8/32

Viewing SSCOP Link


9/32

Viewing SSCOP Link


10/32

Viewing SSCOP Link


11/32


12/32

Content


Viewing SSCOP link





13/32

Viewing Common PhysicalChannel


14/32

Viewing Common PhysicalChannel


15/32

Content


Viewing SSCOP link





16/32


17/32

Viewing NBAP Signaling

Use the NbapWatcherprogram of the LMT software

to explain the information contained in the signaling

in details.


18/32


19/32

Content


Viewing SSCOP link





20/32

Testing Service Testing Services in CS Domain

Testing 12.2k voice services Preparations

1. The equipment is turned on normally.

2. Prepare two UEs for testing, relevant assemblies, and twoUSIM cards.

Steps 1. Enable the signaling trace and start the user tracing function.

2. Make a call ofAMR12.2k voice service from the UE1 to theUE2.

3. If the call succeeds, the quality of the voice is good, and thecall can be disconnected normally, it indicates that the test

succeeds. 4. Repeat the above steps five times.

Rules for judging a successful test

The voice service is normal.


21/32

Testing Service Testing Services in CS Domain

Testing 64k videophone service Preparations

1. The equipment is turned on normally.

2. Prepare two UEs for testing, relevant assemblies, and twoUSIM cards.

Steps 1. Enable the signaling trace and start the user tracing function.

2. Make a call of 64k videophone service from the UE1 to theUE2.

3. If the call succeeds, the quality of the voice is good, thepicture is clear, and the call can be disconnected normally, it

indicates that the test succeeds. 4. Repeat the above steps five times


The videophone service is normal.


22/32

Testing Service Testing Services in PS Domain

Testing 384K service FTP downloading

Preparations 1. The equipment is turned on normally .

2. Prepare one UE that supports PS domain services, relevantassemblies (such as, data cable), and one USIM card.

3. Prepare one computer for testing and connect it with the UE for testing.

Steps

1. Connect the UE for testing with the computer for testing with the datacable. Dial the number on the UE to instate the PS service.

2. After the UE connects to the FTP server successfully, download thefile (suggested to be smaller than 10M) from the FTOP site with thenetwork downloading tool (taking as Netants as an example).

3. Observe the download speed. After the downloading competes,disconnect the service normally.

4. Repeat the above steps five times Rules for judging a successful test

1. The file is downloaded from the FTP site successfully.

2. The downloaded file is complete.

3. After the downloading completes, the speed displayed in the Netantstool is not slower than 280 Kbps.


23/32

Testing Service Testing Services in PS Domain

Testing concurrent services Preparations

1. The equipment is turned on normally .

2. Prepare two UEs that support concurrent services, relevant assemblies(such as, data cable), and two USIM cards.

3. Prepare one computer for testing and connect it with the UE for testing

Steps 1. Initiate 384k data service from the UE1.

2. After the activation succeeds, initiate a service of 12.2k voice call from theUE1 to the UE2.

3. De-activate the PS service and initiate the 12.2k voice service call requestfrom the UE.

4. After the call succeeds and the communication is normal, disconnect the CSservice.

5. Initiate the service of 12.2k voice call from the UE2 to the UE1. 6. After the call succeeds and the communication is normal, disconnect the CS

service and PS service.


PS384k+CS12.2k concurrent service is normal. The normal disconnection ofeither service does not influence the other.


24/32

Content


Viewing SSCOP link





25/32

NodeB Fault Collection Transport Type

E1 link disconnected E1/T1 link electrical signalloss (E1/T1 link NO.: XX)

E1/T1 IMA f\group in non-working state (IMA group No.: XX)

Topology relation of BBU and RRU not configured

RTR reports Board communication link disconnected message(direct link disconnection alarm) and Application softwaremonitoring alarm.

Fiber between BBU and RRU disconnected

On the CCI board, there is the Ir opticalport optical signalloss

(Ir optical oirt No: N) alarm.

To support ATMF5OAM loopback cell or not

After it is checked, all celland channels are set up normally butall PVC links report the PVC link fault alarm.


26/32

NodeB Fault Collection Hardware Type

Board type configuration error On the BP board, there is the Board plugging erroralarm.

On the RTR, there is the Board plugging erroralarm and Board

parameter synchronization abnormal (IQ switching information

configuration failure) alarm.

The hardware configured on the BP board but not distributed to

the cell group

On the BP board, there is the Board configuration parameter

erroralarm and the Application software monitoring alarm.

BP board not working normally

The cell is set up unsuccessfully because of

tCause.u.radioNetwork =

TNBAP_nodeB_Resources_unavailable


27/32

NodeB Fault Collection Hardware Type

RTR board not working normally The cell is set up unsuccessfully and the NBAP fails because

of tCause.u.misc = TNBAP_hardware_failure

There is subcard on the CCI board but it is not configured in

the data configuration

On the CCI board, there is Find not-configured XX subcard

alarm.

No subcard on the CCI board but configured in the data

configuration

On the CCI board, there is the XX subcar is not in position

alarm.


28/32

NodeB Fault Collection ATM Parameter Type

ATM address is configured by error

The cell is set up successfully. The ALCAP does not find any signaling.

Observe the common transport channeland only the BCH is found. ThePCH is created and deleted repeatedly. No other channel is set up.

Observe the common physical channeland only PSCH, SSCH, PCPICH,and PCCPCH are found. The SCCPCH and PICH are created anddeleted repeatedly. No other channel is set up.

After correcting the configurations, fourlink setup request and link setupcomplete messages are reported on the ALCAP.

AAL2 parameter is configured by error

The cell is set up successfully.

On the ALCAP, the link is set upand released repeatedly.

Observe the common transport channeland only the BCH is found. The

PCH is created and deleted repeatedly. No other channel is set up. Observe the common physical channeland only PSCH, SSCH, PCPICH,

and PCCPCH are found. The SCCPCH and PICH are created anddeleted repeatedly. No other channel is set up.

After correcting the configurations, fourlink setup request and link setupcomplete messages are reported on the ALCAP.


29/32

NodeB Fault Collection ATM Parameter Type

AAL5 parameter is configured by error NCP: BGN and END occur in the SSCOP signaling

observation. The cell can not be set up. The NBAP signalingobservation window does not report any signaling.

ALCAP: BGN and END occur in the SSCOP signalingobservation. The cell is set up successfully. The ALCAP doenot report any singling other than the first release requestmessage and three reset request messages. In the commontransport channel, the PCH is created and deleted repeatedly.In the common physical channel, the first SCCPCH and PICHare created and deleted repeatedly.

CCP: Related to the service. Other than the BGN and ENDoccurred in the SSCOP signaling observation, it doe not

appear in the NBAP signaling. Therefore, it must be paidspecialattention to.

IPOA: Related to the remote operation and maintenance pathof the Node B, such as, LMT and OMCB. Any modification willbring alot of inconvenience in the maintenance because theengineer had to deal with on the site.


30/32

NodeB Fault Collection Radio Parameter

Cell ID is configured by error

The RNC does not send the Cell setup request

message.

Cell frequency is configured by error

The cell is set up unsuccessfully and the NBAP failsbecause of tCause.u.radioNetwork =

TNBAP_requested_configuration_not_supported

Other radio parameters are configured by error

RF unit connection: Affecting the transceivingfunction

Rx/Tx delay parameter: On the CCI board, there is a

delay alarm.


31/32

NodeB Fault Collection OtherParameter

Bandwidth and traffic feature parameters inconsistent with theplan

No alarm occurs but in actualapplication, it will influence the

service performance. The QoS can not be guaranteed. The

fault should be paid specialattention to.

NODEB/Cell blocked The cell is set up unsuccessfully and the NBAP fails because

of tCause.u.protocol =

TNBAP_message_not_compatible_with_receiver_state

BP board blocked

The cell is set up unsuccessfully and the NBAP fails becauseof tCause.u.radioNetwork =

TNBAP_nodeB_Resources_unavailable

Clock reference source is set incorrectly

On the CCI board, there is a clock alarm.


32/32

11 Iub Interface Interconnection-32

Documents

Transcript of 11 Iub Interface Interconnection-32