UMTS _RNS_II_05_20090430 Iub Interface Interconnection

ZTE University

Content Alarm troubleshooting Viewing SSCOP link Viewing common channel Viewing NBAP signaling Testing services NodeB fault collection

Alarm Troubleshooting

Alarm Troubleshooting

Content Alarm troubleshooting Viewing SSCOP link Viewing common channel Viewing NBAP signaling Testing services NodeB fault collection

Viewing SSCOP Link

Viewing SSCOP Link

Viewing SSCOP Link

Viewing SSCOP Link

Viewing SSCOP Link

Content Alarm troubleshooting Viewing SSCOP link Viewing common channel Viewing NBAP signaling Testing services NodeB fault collection

Viewing Common Physical Channel

Viewing Common Physical Channel

Content Alarm troubleshooting Viewing SSCOP link Viewing common channel Viewing NBAP signaling Testing services NodeB fault collection

Viewing NBAP Signaling

Viewing NBAP Signaling



Use the NbapWatcher program of the LMT software to explain the information contained in the signaling in details.

Content Alarm troubleshooting Viewing SSCOP link Viewing common channel Viewing NBAP signaling Testing services NodeB fault collection

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 two USIM cards. Steps 1. Enable the signaling trace and start the user tracing function. 2. Make a call of AMR12.2k voice service from the UE1 to the UE2. 3. If the call succeeds, the quality of the voice is good, and the call 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.

   

  

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 two USIM 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 the UE2. 3. If the call succeeds, the quality of the voice is good, the picture is clear, and the call can be disconnected normally, it indicates that the test succeeds. 4. Repeat the above steps five times Rules for judging a successful test The videophone service is normal.

   

  

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, relevant assemblies (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 data cable. Dial the number on the UE to instate the PS service. 2. After the UE connects to the FTP server successfully, download the file (suggested to be smaller than 10M) from the FTOP site with the network 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 Netants tool is not slower than 280 Kbps.

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 the UE1 to the UE2. 3. De-activate the PS service and initiate the 12.2k voice service call request from the UE. 4. After the call succeeds and the communication is normal, disconnect the CS service. 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. Rules for judging a successful test PS384k+CS12.2k concurrent service is normal. The normal disconnection of either service does not influence the other.

 

Content Alarm troubleshooting Viewing SSCOP link Viewing common channel Viewing NBAP signaling Testing services NodeB fault collection

NodeB Fault Collection

    

Transport Type

E1 link disconnected E1/T1 link electrical signal loss (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 software monitoring alarm. Fiber between BBU and RRU disconnected On the CCI board, there is the Ir optical port optical signal loss (Ir optical oirt No: N) alarm. To support ATMF5OAM loopback cell or not After it is checked, all cell and channels are set up normally but all PVC links report the PVC link fault alarm.

 

 

NodeB Fault Collection

  

Hardware Type

Board type configuration error On the BP board, there is the Board plugging error alarm. On the RTR, there is the Board plugging error alarm 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 error alarm 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

 

 

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.

 

 

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 channel and only the BCH is found. The PCH is created and deleted repeatedly. No other channel is set up. Observe the common physical channel and only PSCH, SSCH, PCPICH, and PCCPCH are found. The SCCPCH and PICH are created and deleted repeatedly. No other channel is set up. After correcting the configurations, four link setup request and link setup complete 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 up and released repeatedly. Observe the common transport channel and only the BCH is found. The PCH is created and deleted repeatedly. No other channel is set up. Observe the common physical channel and only PSCH, SSCH, PCPICH, and PCCPCH are found. The SCCPCH and PICH are created and deleted repeatedly. No other channel is set up. After correcting the configurations, four link setup request and link setup complete messages are reported on the ALCAP.

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 signaling observation window does not report any signaling. ALCAP: BGN and END occur in the SSCOP signaling observation. The cell is set up successfully. The ALCAP doe not report any singling other than the first release request message and three reset request messages. In the common transport channel, the PCH is created and deleted repeatedly. In the common physical channel, the first SCCPCH and PICH are created and deleted repeatedly. CCP: Related to the service. Other than the BGN and END occurred in the SSCOP signaling observation, it doe not appear in the NBAP signaling. Therefore, it must be paid special attention to. IPOA: Related to the remote operation and maintenance path of the Node B, such as, LMT and OMCB. Any modification will bring a lot of inconvenience in the maintenance because the engineer had to deal with on the site.

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 fails because of tCause.u.radioNetwork = TNBAP_requested_configuration_not_supported Other radio parameters are configured by error RF unit connection: Affecting the transceiving function Rx/Tx delay parameter: On the CCI board, there is a delay alarm.

NodeB Fault Collection

 

Other Parameter

 

 

 

Bandwidth and traffic feature parameters inconsistent with the plan No alarm occurs but in actual application, it will influence the service performance. The QoS can not be guaranteed. The fault should be paid special attention 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 because of tCause.u.radioNetwork = TNBAP_nodeB_Resources_unavailable Clock reference source is set incorrectly On the CCI board, there is a clock alarm.