huawei wcdma umts6.1 ip clock test case description(t-umts61-ipclk-v1.0-20071023)

Huawei WCDMA Test Cases Description

IP CLOCK

(UMTS 6.1)

Huawei Technologies Co., Ltd. Website:http://support.huawei.com

E-MAIL:[email protected]

All Rights Reserved. Address:Bantian, Longgang District, Shenzhen, P. R. China

Postal Code:518129

Doc No: T-umts61-ipclk Total 17 pagesDoc Ver: v1.0-20071023

Huawei WCDMA Test Cases Description UMTS61 IP CLOCK Internal use

Table of Contents

IPCLK01 Basic function..............................................................................................................1

IPCLK01-01 Basic function test.................................................................................................1

IPCLK01-0101 IP clock function test when server in lock and NODEB as a client...........1

IPCLK02 Stability Test................................................................................................................1

IPCLK02-01 Long-time stability test..........................................................................................1

IPCLK02-0101 IP clock long-time stability test when server in locked state and NODEB as a client.......................................................................................................................... 1

IPCLK03 Reliability Test.............................................................................................................3

IPCLK03-01 Test of Server in abnormal...................................................................................3

IPCLK03-0101 Test of Server ‘s clock source lost.............................................................3

IPCLK03-0102 Test of Server’s power turn off –standby server exist...............................3

IPCLK03-0103 Test of Server’s power turn off –standby server not exist..........................4

IPCLK03-0104 Test of Server’s reset - standby server exist.............................................5

IPCLK03-0105 Test of Server’s reset –standby server not exist.......................................6

IPCLK03-02 Test of transmission in abnormal..........................................................................7

IPCLK03-0201 Test of transmission broken off -- standby server exist.............................7

IPCLK03-0202 Test of transmission broken off -- standby server not exist.......................8

IPCLK03-0203 Test of transmission QOS abnormal--Clock over ip to restore it...............8

IPCLK03-0204 Test of transmission QOS abnormal-- clock stability dependance on delay........................................................................................................................................ 10

IPCLK03-0205 Test of transmission QOS abnormal-- clock stability dependance on jitter........................................................................................................................................ 11

IPCLK03-0206 Test of transmission QOS abnormal-- clock stability dependance on packet loss....................................................................................................................... 12

IPCLK03-03 Test of NODEB in abnormal...............................................................................13

IPCLK03-0301 Test of NODEB power off........................................................................13

IPCLK03-0302 Test of NODEB reset...............................................................................13

IPCLK03-04 Test of transmission congestion.........................................................................14

IPCLK03-0401 Test of transmission congestion..............................................................14

Appendix A: Network diagram..................................................................................................16

T-umts61-ipclk-v1.0-20071023

HUAWEI Proprietary and ConfidentialPage i of i


IP CLOCK Test Case Description

IPCLK01 Basic function

IPCLK01-01 Basic function test

IPCLK01-0101 IP clock function test when server in lock and NODEB as a client

Objective

Test the function of NODEB as a client restore IP clock when Server in locked state. The clock precision of the NODEB preceded 0.05ppm

Network diagram

See Figure 1 in Appendix.

Prerequisites

1. IPCLK1000 is normal

2. The clock precision of the IPCLK source preceded 0.005ppm. IPCLK source maybe is BITS/GPS/ 1pps /10MHz and so on

3. Service channel is unblocked and server ping client (or client ping server) is reachable

4. Maintain channel is unblocked and data configure is finished

Procedure Expected result

1. Viewing client(NODEB) link state in server(IPCLK1000)

Query the client info successfully by client ip

address

2. Server (IPCLK1000) is in locked state The clock precision of the server output

clock preceded 0.005ppm and to ensure the

source is exact.

3. Oberserving the PLL state change in client (NODEB)

Clock state in NODEB move from free to locked and current clock frequency go with source. The clock precision of the NODEB preceded 0.05ppm in locked state

1. Server and tranmit device hold steady and to measure the output clock in client(NODEB)

Clock state in NODEB hold lock with the precision preceded 0.05ppm in 24 hours(to use cymometer)

Remarks

T-umts61-ipclk-v1.0-20071023 HUAWEI Proprietary and Confidential Page 1 of 17


1. To ensure clock resource meet the precision, however, we would suggest that clock source from Rubidium Clock or GPS .

2.

IPCLK02 Stability Test

IPCLK02-01 Long-time stability test

IPCLK02-0101 IP clock long-time stability test when server in locked state and NODEB as a client

Objective

Test the clock stability of NODEB as a client restore IP clock when Server in locked state exceeded 7 days. The clock precision of the NODEB preceded 0.05ppm

Network diagram


Prerequisites




4. Maintain channel is unblocked and data configure is finished


Viewing client(NODEB) link state in server(IPCLK1000)

Query the client info successfully by client IP address

Oberserving the PLL state change in client (NODEB)

Clock state in NODEB move from free to

lock and current clock frequency go with

source. The clock precision of the NODEB

preceded 0.05ppm in locked state.

Clock state in Server(IPCLK1000) keep locked exceeded 7 days

Clock state in NODEB keep lock with the precision preceded 0.05ppm in 7 days(to use cymometer)

Remarks

1. Anytime, the clock precision in NODEB preceded 0.05ppm in 7 days



IPCLK03 Reliability Test

IPCLK03-01 Test of Server in abnormal

IPCLK03-0101 Test of Server ‘s clock source lost

Objective

While Server’s clock source is lost, however, NODEB as a client restore IP clock with the clock precision preceded 0.05ppm over 24 hours

Network diagram


Prerequisites

1. IPCLK1000 (server) & NODEB (client) is in locked state

2. IPCLK1000’s clock source is lost


4. Maintain channel is unblocked and data configuration is finished


Viewing server(IPCLK1000) pll state in server after clock source is lost

Clock state in server move from locked to hold with clock precision preceded 0.005ppm


Clock state in NODEB keep hold and

current clock frequency go with source. The

clock precision of the NODEB preceded

0.05ppm in locked state.

Clock state in Server(IPCLK1000) keep hold after clock source is lost over 24 hours

Clock state in NODEB keep lock with the precision preceded 0.05ppm over 24 hours(to use cymometer)

Remarks

1. If it has enough time to test, the trial will need 24 hours; if not, it will need12 hours

IPCLK03-0102 Test of Server’s power turn off –standby server exist

Objective

While Server is power off, NODEB as a client switch to standby server and restore IP clock with the clock precision preceded 0.05ppm over 24 hours



Network diagram

See Figure 2in Appendix.

Prerequisites


2. Standby server exist and is in locked state




After main server is power off, Viewing client(NODEB) clock state in client

NODEB raise alarm of clock source loss, after 15 minutes, main IP clock link moved from normal to abnormal and IP clock source switch to backup link

Viewing client(NODEB) link state in standby server(IPCLK1000)

Query the client info successfully by client

IP address


Clock state in NODEB move as: free -> fast

tracing ->lock. The clock precision of the

NODEB preceded 0.05ppm in locked state.

After 30 minutes, main server’s power turn on and clock state come back

NODEB use standby server as service

server, however, do not swap to main

server

During the course of this time, NODEB output clock precision of the NODEB preceded 0.05ppm

Remarks

1. When backup IP clock link exist in NODEB: if the time of main link interrupted is over 15 minutes, NODEB IP clock source auto swap; if the time is under 15 minutes, NODEB IP clock source use old link steadily and trace the IP clock source over again.

IPCLK03-0103 Test of Server’s power turn off –standby server not exist

Objective

While Server’s power turn off, NODEB as a client detect IPCLK link unavailable and PLL state transfer to free

Network diagram




Prerequisites

1. The clock precision of the IPCLK source preceded 0.005ppm.


3. Standby server is inexistence


After main server is power off , Viewing client(NODEB) clock state in client

NODEB raise alarm of clock source loss, after 15 minutes, main IP clock link moved from normal to abnormal and raise alarm about IPCLK link in abnormal


Clock state in NODEB transfer to free .The

current frequency of the NODEB is changed

Keep server’s power turn off 12hours (may test 24 hours in conditioanal)

During the course of the trail, NODEB

output clock precision of the NODEB

preceded 0.05ppm

server come back Link Between NODEB and sever

(IPCLK1000) set up over again and Clock

state in NODEB move from free to fast

tracing then lock. The clock precision of the



Remarks

1. After server is power off over 1 minute, NODEB raise clock source loss alarm immediately

2. The time of IPCLK link broken off is over 15 minutes, NODEB raise alarm of IP clock link abnormal

3. If the time is under 15 minutes, NODEB do not raise alarm of IP clock link abnormal and trace the IP clock source over again.

IPCLK03-0104 Test of Server’s reset - standby server exist

Objective

While Server reset, NODEB as a client do not switch to standby server .When server come



back ,NODEB will restore IP clock from main server as clock source

Network diagram


Prerequisites

1. Standby server exist and is in locked state

2. Service channel is unblocked and server ping client (or client ping server) is reachable. The link between client (NODEB) and server(IPCLK1000) is established. IPCLK1000 (server) & NODEB (client) is in locked state



After main server reset , Viewing client(NODEB) clock state in client

NODEB raise alarm about clock source loss, but it has no handover. The clock state transfer to free

After server reset finished,Viewing client(NODEB) state in client (IPCLK1000)

Alarm is cleanup and NODEB still use old

server as IP clock source. Clock state in

NODEB move as: free -> fast tracing -

>lock. The clock precision of the NODEB



Remarks

1. Even if it has backup IP clock source, the NODEB do not swap automatically in order to avoid high frequency handover which would result in unexpected status.

2. After server reset finished 3~4 hours, client(NODEB) turn into locked state. During the course of the trial, NODEB output clock precision of the NODEB preceded 0.05ppm

IPCLK03-0105 Test of Server’s reset –standby server not exist

Objective

While Server’s reset, NODEB as a client detect IPCLK link unavailable and PLL state transfer to free

Network diagram




Prerequisites



3. Standby server is inexistence


After main server’s reset , Viewing client(NODEB) clock state in client

NODEB raise alarm of clock source loss, Clock state in NODEB transfer to free

After server reset finished NODEB still use old server as IP clock

source. Clock state in NODEB move as:

free -> fast tracing ->lock. The clock

precision of the NODEB preceded 0.05ppm

in locked state.


Remarks

1. If not existing backup IP clock source in NODEB, the NODEB would raise alarm of clock source loss

2. After server reset finished 3~4 hours, client(NODEB) turn into locked state. During the course of the trial, NODEB output clock precision of the NODEB preceded 0.05ppm

IPCLK03-02 Test of transmission in abnormal

IPCLK03-0201 Test of transmission broken off -- standby server exist

Objective

IPCLK server run in normal, but transmission is broken off .The clock source of NODEB will switch to standby server ,and it will restore IP clock from standby server as clock source

Network diagram


Prerequisites

1. Maintain channel is unblocked and data configuration is finished .Standby server exist

2. Service channel is unblocked and server ping client (or client ping server) is



reachable.




To pull out the connection in main server by manual. Viewing client(NODEB) clock state in client

NODEB raise alarm about clock source loss. After 15 minutes, the clock source in NODEB would switch to standby server and raise alarm about main IPCLK link in abnormal.

To query the state of client link state in standby server

It could be queried by the IP address of

NODEB


Clock state in NODEB is moved from fast

tracing to locked .The current frequency of

the NODEB is changed

The transmission in main server is restored afer 12 hours

NODEB still use old server as IP clock

source, and it would be not switch to main

server


Remarks

1. It is required to consume 15 minutes before clock source in NODEB is switched

2. If the main IPCLK link is restored in 15 minutes, NODEB would use this link as clock source and begin to capture the clock again.

IPCLK03-0202 Test of transmission broken off -- standby server not exist

Objective

IPCLK server run in normal, but transmission is broken off. NODEB would work as free with the clock precision preceded 0.05PPM. When server come back ,NODEB will restore IP clock from main server as clock source

Network diagram

See Figure1 in Appendix.

Prerequisites

1. Maintain channel is unblocked and data configuration is finished .



2. Service channel is unblocked and server ping client (or client ping server) is reachable.

3. Standby server is not exist


To pull out the connection in main server by manual. Viewing client(NODEB) clock state in client

NODEB raise alarm about clock source loss. After 15 minutes, it raises alarm about main IPCLK link in abnormal.


Clock state in the NODEB is transfered to

free. The current frequency of the NODEB

is changed


Link Between NODEB and sever






Remarks

IPCLK03-0203 Test of transmission QOS abnormal--Clock over ip to restore it

Objective

Use test instrument to simulate various QOS characteristic on network and observe NODEB clock restoration as it picks up clock from IP packet of bad QOS .

Network diagram


Prerequisites

1. Maintain channel is unblocked and data configuration is finished.


3. It has a certain extent delay, packet loss and jitter ( 60ms delay, 1% packet loss, 20ms jitter)





To simulate a 60ms delay, 1% packet loss and 10ms jitter in transmission by IPSTORM

Reset the NODEB



tracing to locked with a clock precision

preceded 0.05ppm

Server clock state keep locked 24 hours

NODEB is locked with a clock precision

preceded 0.05ppm

Remarks

1. It is required to offer a special equipment, IPSTORM or PACKETSTORM

2. It would lead to a longer time to lock the clock source maybe as data’s smoothness handling.

IPCLK03-0204 Test of transmission QOS abnormal-- clock stability dependance on delay

Objective

Use test equipment to simulate various delay on network and observe NODEB clock restoration since it picks up clock from IP packet of bad QOS .

Network diagram


Prerequisites



3. It has a range delay by the emulator equipment (60ms delay)



To simulate a 60ms delay by IPSTORM

Reset the NODEB



To modify the current frequency on NODEB, and to make the frequency different from the clock source

(Notes: the modified frequency on NODEB would not exceed 2Hz which is the scope of big different frequency. It would be suggested to modify the frequency below 0.5Hz)

The frequency on NODEB is different from

the clock source by using cymometer

Oberserving the PLL state changing in client (NODEB)



preceded 0.05ppm

Server clock state keep locked for a few hours.


preceded 0.05ppm

Remarks



IPCLK03-0205 Test of transmission QOS abnormal-- clock stability dependance on jitter

Objective

Use test equipment to simulate various jitter on network and observe NODEB clock restoration since it picks up clock from IP packet of bad QOS .

Network diagram


Prerequisites



3. It has a range jitter by the emulator equipment (20ms jitter)



To simulate a 20ms jitter in transmission by IPSTORM

Reset the NODEB










preceded 0.05ppm



preceded 0.05ppm

Remarks



IPCLK03-0206 Test of transmission QOS abnormal-- clock stability dependance on packet loss

Objective

Use test equipment to simulate various packet loss rate on network and observe NODEB clock restoration since it picks up clock from IP packet of bad QOS .

Network diagram


Prerequisites



3. It has a range packet loss by the emulator equipment (1% packet loss)



To simulate a 1% packet loss in transmission by IPSTORM



Reset the NODEB








preceded 0.05ppm



preceded 0.05ppm

Remarks



IPCLK03-03 Test of NODEB in abnormal

IPCLK03-0301 Test of NODEB power off

Objective

IPCLK server run in normal and NODEB is power off. After it has finished the start-up, NODEB can trace the IP clock source again

Network diagram


Prerequisites








NODEB is power off while it is running in normal

Once the power is available, NODEB start up

After IP clock link is detected to be steady,

Link between NODEB and sever

(IPCLK1000) is established again


Clock state in the NODEB transfer to free.

The current frequency of the NODEB is

changed







Remarks

1. The PLL state moved correctly and current clock frequency is changed with clock source

IPCLK03-0302 Test of NODEB reset

Objective

IPCLK server run in normal and NODEB is reset. After it has finished the start-up, NODEB can trace the IP clock source again

Network diagram


Prerequisites








NODEB is reset while it is running in normal

NODEB start up After IP clock link is detected to be steady,




Clock state in the NODEB transfer to free.

The current frequency of the NODEB is

changed







Remarks

The PLL state moved correctly and current clock frequency is changed with clock source

IPCLK03-04 Test of transmission congestion

IPCLK03-0401 Test of transmission congestion

Objective

While the transmission is congestion, we would confirm the IP clock restoration

Network diagram


Prerequisites



3. Transmit network is congestion and it is filled with service data. The highest priority is set for clock data


Clock state in NODEB is free and



server is normal. There are HSDPA service in the NODEB and it occupied all bandwidth.

There is the highest priority to clock data in server and transmission equipment .

Once the power is available, NODEB start up

After IP clock link is detected to be steady,




Clock state in the NODEB moved from fast



Server clock state keep locked 24 hours


preceded 0.05ppm

Remarks

1. The PLL state moved correctly and current clock frequency is changed with clock source



Appendix A: Network diagram

Figure 1: test network diagram without standby server


CLK SOURCE

IPCLK Server

NETWORK

RNC

BBU/NODEB

FE

FE/GE

FE/GE

cymometerRubidium

Clock

10MHzRubidium

Clock/GPS/BITS


Figure 2: test network diagram with main-standby server

Figure 3: test network diagram with network emulator


CLK SOURCE

IPCLK Server 2

NETWORKBBU/NODEB

FE

FE/GE

FE/GE

cymometerRubidium

Clock

10MHzRubidium Clock/GPS/BITS

IPCLK server

CLK SOURCE

IPCLK Server

IP NETWORK EMULATO

RRNC

BBU/NODEB

FE

FE/GE

FE/GE

cymometerRubidium

Clock

10MHz Rubidium

Clock/GPS/BITS /

GPS/BITS

huawei wcdma umts6.1 ip clock test case description(t-umts61-ipclk-v1.0-20071023)

Documents