AU2007229333A1 - Method and apparatus for testing wireless communication channels - Google Patents

Description

Regulation 3.2

AUSTRALIA

PATENTS ACT 1990 COMPLETE SPECIFICATION FOR A DIVISIONAL PATENT

ORIGINAL

Name of Applicant: Actual Inventors: Address for Service: Invention title: Qualcomm Incorporated Scott Eduard Fischel Idreas A Mir MADDERNS, 1st Floor, 64 Hindmarsh Square, Adelaide, South Australia, Australia METHOD AND APPARATUS FOR TESTING WIRELESS COMMUNICATION CHANNELS The following statement is a full description of this invention, including the best method of performing it known to us.

METHOD AND APPARATUS FOR TESTING WIRELESS COMMUNICATION CHANNELS 0 BACKGROUND OF THE INVENTION IND 1. Field of the Invention The present invention relates to data communication. More particularly, the present invention relates to novel and improved method and apparatus for testing wireless communication channels.

11. Description of the Related Art Wireless communication systems such as code division multiple access (CDM4A) systems, time division multiple access (TDMA) systems, and others are widely used to provide various types of communication such as voice, data, and so on. For these wireless systems, it is highly desirable to utilize the available resources bandwidth and transmit power) as efficiently as possible. This typically entails transmitting as much data to as many users within as short a time period as supported by the conditions of the communication links.

To achieve the above goal, the communication links between a transmitting source a base station) and the receiving devices "connected" remote terminals) within the system may be characterized. Based on the characterized link conditions for the remote terminals, the system may be better able to select a particular set of remote terminals to serve, allocate a portion of the available resources transmit power) to each selected remote terminal, and transmit to each remote terminal at a data rate supported by the allocated transmit power and characterized link conditions.

Conventionally, a communication link is characterized by transmitting from a base station) a known data pattern generated by a defined pseudo-random number generator), receiving the transmitted data pattern, comparing the received data pattern with a locally generated data pattern to determine transmission errors, and reporting the results back to the transmitting source. This "loop-back" testing is typically performed 2 continuously for a number of frames over the desired test interval. The test results

O

are reflective of the performance of the communication link over that test interval.

Many newer generation wireless communication systems are capable of O flexible operation. For example, data may be transmitted in bursts and over one or more traffic channels (or physical channels), the data rate may be allowed to vary from frame to frame, the processing of the data may also vary from frame to frame and/or from channel to channel), and so on. The conventional loop-back test technique typically characterizes the communication link one traffic channel) based on a defined set of test parameters, and may not provide an accurate assessment of the performance of the communication link when the system operates in this flexible manner.

As can be seen, techniques that can be used to characterize a communication link under various flexible operating conditions supported by a wireless communication system are highly desirable.

SUMMARY OF THE INVENTION In a first aspect the present invention accordingly provides a method for testing a plurality of channels under flexible operating conditions in a wireless communication system including: defining values for a set of test parameters for each of the plurality of channels to be tested; and testing each of the plurality of channels, operating under the flexible conditions, in accordance with respective values defined for the set of test parameters.

In a second aspect the present invention accordingly provides a method for testing a particular channel in a wireless communication system, including: sending from a first entity to a second entity a first message having included therein one or more proposed values for one or more parameters for testing the particular channel; and receiving from the second entity a response message rejecting or accepting the one or more proposed values sent in the first message.

In a third aspect the present invention accordingly provides a wireless

O

0 communication system in which a plurality of frames are transmitted, a method for attaining a long-term average value on a duty cycle using a two-state Markov chain, O the method including: driving on/off transitions of a test data service option (TDSO) process with a first pseudo-random number generator during a frame period if the frame period is a first length in time; and 0 driving the on/off transitions with a second pseudo-random number generator during the frame period if the frame period is either a second length in time or a third length in time.

In a fourth aspect the present invention accordingly provides a method of exchanging test parameter values between a remote terminal and a base station in a wireless communication system, the method including: sending proposed test parameter values from the remote terminal to the base station; and receiving a service option control message from the base station rejecting or negatively acknowledging the proposed test parameter values.

In a fifth aspect the present invention accordingly provides a method of constructing a circular buffer storing a plurality of maximum-rate frames transmitted on a particular channel under flexible operating conditions in a wireless communication system, the method including: constructing data for the circular buffer from iterations of a pseudo-random number generator a plurality of times for each test interval, wherein the data is to be transmitted under flexible operating conditions; and using a set of bits from a number generated by the pseudo-random number generator to indicate a byte offset to determine a starting position in the circular buffer from which to build one or more data blocks for a particular frame period.

The invention further provides other methods and system elements that implement various aspects, embodiments, and feature of the invention, as described in further detail below.

BRIEF DESCRIPTION OF THE DRAWINGS The features, nature, and advantages of the present invention will become Smore apparent from the detailed description set forth below when taken in O conjunction with the drawings in which like reference characters identify correspondingly throughout and wherein: FIG. 1 is a diagram of a spread spectrum communication system that supports e¢3 e¢ a number of users; e¢3 FIGS. 2A and 2B are block diagrams of an embodiment of a base station and a remote terminal, respectively, capable of implementing various aspects and 10 embodiments of the invention; FIG. 3 is a flow diagram of a process for generating test data using a pseudorandom number generator, in accordance with a specific embodiment of the invention.

FIG. 4 is a block diagram of the buffers and pseudo-random number generators used for generating pseudo-random test data for two traffic channels; FIG. 5 is a diagram that illustrates the reshuffling of a pseudo-random number to generate a number for the test data; FIG. 6 is a diagram that illustrates test data transmission for a discontinuous transmission (DTX) scheme based on a deterministic frame activity; FIG. 7 is a diagram of a two-state first-order Markov chain that may be used to model the ON/OFF states for a DTX scheme based on pseudo-random frame activity; FIG. 8 is a flow diagram of an embodiment of a process for transitioning between the ON and OFF states of the Markov chain for a traffic channel; and FIG. 9 is a diagram of an embodiment of a test data block.

o DETAILED DESCRIPTION OF THE SPECIFIC EMBODIMENTS FIG. 1 is a diagram of a spread spectrum communication system 100 that supports a number of users. System 100 provides communication for a number C of cells, with each cell being serviced by a corresponding base station 104.

Various remote terminals 106 are dispersed throughout the system. Each remote terminal 106 may communicate with one or more base stations 104 on the forward and reverse links at any particular moment, depending on whether or not the remote terminal is active and whether or not it is in soft handoff. As shown in FIG. 1, base station 104a communicates with remote terminals 106a, 106b, 106c, and 106d and base station 104b communicates with remote terminals 106d, 106e, and 106f.

A system controller 102 couples to base stations 104 and may further couple to a public switched telephone network (PSTN). System controller 102 provides coordination and control for the base stations coupled to it. System controller 102 further controls the routing of telephone calls among remote terminals 106, and between remote terminals 106 and the users coupled to PSTN conventional telephones), via base stations 104. For a CDMA system, system controller 102 is also referred to as a base station controller

(BSC).

System 100 may be designed to support one or more CDMA standards such as the "TIA/EIA-95-B Mobile Station-Base Station Compatibility Standard for Dual-Mode Wideband Spread Spectrum Cellular System" (the standard), the "TIA/EIA-98-D Recommended Minimum Standard for Dual- Mode Wideband Spread Spectrum Cellular Mobile Station" (the IS-98 standard), the "TIA/EIA/IS-2000.2-A Physical Layer Standard for cdma2000 Spread Spectrum Systems", the "TIA/EIA/IS-2000.5-A Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread Spectrum Systems", the standard offered by a consortium named "3rd Generation Partnership Project" (3GPP) and embodied in a set of documents including Document Nos. 3G TS 25.211, 3G TS 25.212, 3G TS 25.213, and 3G TS 25.214 (the W-CDMA standard), the standard offered by a consortium named "3rd Generation Partnership Project 2" O (3GPP2) and embodied in a set of documents including Document Nos.

C.S0002-A, C.S0005-A, C.S0010-A, C.S0011-A and C.S0026 (the cdma2000 O standard), or some other standards. These standards are incorporated herein by reference.

Some newer generation CDMA systems are capable of concurrently supporting voice and data transmissions, and may further be able to transmit to Cc C a particular remote terminal via a number of forward traffic channels. For example, in the cdma2000 system, a fundamental channel may be assigned for voice and certain types of data, and one or more supplemental channels may be assigned for high-speed packet data.

SFIG. 2A is a block diagram of an embodiment of base station 104, which is capable of implementing various aspects and embodiments of the invention.

For simplicity, FIG. 2A shows the processing at the base station for a communication with one remote terminal. On the forward link, voice and packet data (collectively referred to herein as "traffic" data) from a transmit (TX) data source 210 and test data from a forward link (FL) test data buffer 212 are provided to a multiplexer (MUX) 214. Multiplexer 214 selects and provides the traffic data to a TX data processor 216 when operating in a normal mode, and provides the test data when operating in a test mode. TX data processor 216 receives and processes formats, encodes, and interleaves) the received data, which is then further processed covered, spread, and scrambled) by a modulator (MOD) 218. The modulated data is then provided to an RF TX unit 222 and conditioned converted to one or more analog signals, amplified, filtered, and quadrature modulated) to generate a forward link signal. The forward link signal is routed through a duplexer 224 and transmitted via an antenna 226 to a remote terminal.

Although not shown in FIG. 2A for simplicity, base station 104 is capable of processing and transmitting data on one or more forward traffic channels to a particular remote terminal. For a cdma2000 system, the forward traffic channels include the fundamental channel (FCH), dedicated control channel (DCCH), supplemental channel (SCH), and supplemental code channel (SCCH). The processing encoding, interleaving, covering, and so on) for each forward traffic channel may be different from that of other forward traffic channels.

FIG. 2B is a block diagram of an embodiment of remote terminal 106.

C The forward link signal is received by an antenna 252, routed through a o duplexer 254, and provided to an RF receiver unit 256. RF receiver unit 256 conditions filters, amplifies, downconverts, and digitizes) the received signal and provides samples. A demodulator (DEMOD) 258 receives and processes despreads, decovers, and pilot demodulates) the samples to provide recovered symbols. Demodulator 258 may implement a rake receiver capable of processing multiple instances of the received signal and generating C combined recovered symbols. A receive (RX) data processor 260 decodes the recovered symbols, checks the received frames, and provides decoded traffic data to a RX data sink 264 and decoded test data to a controller 270.

Demodulator 258 and receive data processor 260 may be operated to process multiple transmissions received via multiple forward traffic channels.

On the reverse link, a multiplexer (MUX) 284 receives results of the forward traffic channel testing from controller 270, test data for testing of the reverse link from a reverse link (RL) test data buffer 278, and traffic data from a TX data source 282. Depending on the operating mode of remote terminal 106, multiplexer 284 provides the proper combination of data and/or results to a TX data processor 286. The data and results are then processed formatted, encoded, and interleaved) by TX data processor 286, further processed covered, spread) by a modulator (MOD) 288, and conditioned converted to analog signals, amplified, filtered, and quadrature modulated) by an RF TX unit 290 to generate a reverse link signal, which is then routed through duplexer 254 and transmitted via antenna 252 to one or more base stations 104.

Referring back to FIG. 2A, the reverse link signal is received by antenna 226, routed through duplexer 224, and provided to an RF receiver unit 228. The reverse link signal is conditioned downconverted, filtered, and amplified) by RF receiver unit 228, and further processed by a demodulator 232 and an RX data processor 234 in a complementary manner to recover the transmitted data and test results. The reverse link traffic data is provided to a RX data sink 238, and the forward link test results and reverse link test data are provided to a controller 220 for evaluation.

As noted above, for efficient utilization of the available system resources, the communication link between the base station and remote terminal may be characterized. The link characterization information may then be used to N_ schedule data transmission, allocate transmit power, determine data rate, and

C.)

IND The invention provides various techniques to test a wireless communication link. In an aspect, to test a forward traffic channel, test data is generated at the base station by a test data generator 240 and provided to FL test data buffer 212. The generated test data is thereafter retrieved from buffer 212 (as necessary), processed, and transmitted from the base station to the remote terminal. At the terminal, the transmitted forward link test data is received, processed in a complementary manner, and provided to controller 270. Controller 270 further directs a test data'generator 280 to locally generate the test data, which is stored in a FL test data buffer 268. The locally generated test data is thereafter retrieved from buffer 268 (as necessary) and compared against the received test data. Various performance and statistical data may be collected at the remote terminal based on the results of the comparison between the received and generated test data, as described in further detail below. The testing of the reverse link may be achieved in similar manner as that for the forward link.

For clarity, various aspects of the invention are described for a specific implementation for a cdnma20O0 system.

Channel and Frame Structure In some CDMIA systems, data may be transmitted on one or more traffic channels over the forward and reverse links. (A traffic channel may be akin to a physical channel for some CDMIA systems, a W-CDMA system.) For example, in a cdma2000 system, voice data is typically transmitted over a fundamental channel (FCH), traffic data is typically transmitted over a supplemental channel (SCH), and signaling may be transmitted over a dedicated control channel (DCCH). The FCH, DCCH, and SCH are different types of traffic channel. To receive a high-speed data transmission on the SCH, a remote terminal is also typically assigned a FCH or DCCH. In the cd-ma2000 system each assigned traffic channel is associated with a particular radio configuration (RC) that defines the channel's transmission formats, which may be characterized by various physical layer parameters such as the transmission rates, modulation characteristics, spreading rate, and so on.

o For many CDM4A systems, data is also transmitted in "frames", with each frame covering a particular time interval. For the cdma2000 system, data may be transmitted in frame lengths of 5 msec, 20 msec, 40 msec, or 80 rnsec on the fundamental and supplemental channels. For each frame of each connected traffic channel, one or more data blocks may be transmitted, depending on the radio configuration of the traffic channel.

c-i In certain embodiments of the invention, the forward and reverse traffic channels are each subdivided into independent "test intervals" (which may also be referred to as "segments"). Each test interval has a duration of 10.24 seconds, which corresponds to 2048 frames for traffic channels (FCH, DCCH) with msec frame length, 512 frames for traffic channels (FCH, DCCH, and SCH) with msec frame length, 256 frames for traffic channels (SCH) with 40 msec frame length, and 128 frames for traffic channels (SCH) with 80 msec frame length.

The first frame in the test interval is referred to as a synchronization frame. In an embodiment, the synchronization frame for each of the forward and reverse traffic channels (FCH, DCCH, SCHO, and SCHi) is selected based on a 32-bit public long code mask (PLCM) assigned to the remote terminal and the system frame number (SFN) of the traffic channel's frames, as described in further detail below. Thus, each traffic channel may be associated with synchronization frames that are different (time-wise) from those of other tra-ffic channels.

In an aspect, the CDMA system is designed to support a test data service option (TOSO), which is akin to an operating mode in whidch the performance of the forward and/or reverse traffic channels for a remote terminal may be tested and/or verified. The initiation and negotiation of the parameters for the TDSO are described in further detail below. While operating in this mode, test data may be transmitted over the forward and/or reverse links and over one or more traffic channels on each link. This allows for independent testing of various traffic channels and further allows for independent testing of the forward and reverse links.

Test Data Generation

C.)

IND may be used to test a traffic channel. These test data types may include defined data sequences, pseudo-random data, and others. The test data type may be selected via a parameter in the test data service option.

In one test configuration, one or more defined data sequences are used to test a traffic channel. Various schemes may be used to generate these data c-i sequences. In one scheme, a single byte pattern is used to fill up each data block. This byte pattern may be an all ones pattern ("11111111") or some other c-i byte pattern. If a data block includes more than a whole number of octets 171 bits), each whole octet may be represented by the byte pattern and the remaining bits may be filled with zeros The use of a defined data sequence may simplify the test data generation at the transmission source and receiving device.

In another test configuration, pseudo-random data is used to test a traffic channel. This data may be generated using one or more pseudo-random number generators, as described in further detail below.

FIG. 3 is a flow diagram of a process for generating test data using a pseudo-random number generator, in accordance with a specific embodiment of the invention. FIG. 3 presents an overall view of the test data generation process, which is described in greater detail below. Prior to the start of each test interval for a particular traffic channel to be tested, as determined at stey 312, the pseudo-random number generators used at the transmitting source and receiving device to generate the pseudo-random test data for this traffic channel are synchronized and initialized, at step 314.

The pseudo-random number generator at the transmitting source is then operated to generate a sufficient number of test data bits for N frames (where N is two or greater), at step 316. These test data bits are stored to a (circular) buffer, which is subsequently used as the data source for bits to be packed into one or more data blocks for each "active" frame period in the test interval. The receiving device similarly generates the test data bits for N frames, which are stored to a corresponding buffer at the receiving device and thereafter retrieved as necessary to verify whether or not the transmitted test data bits are received N error free.

In accordance with an aspect of the invention and as described below, C) the traffic channel may be tested using discontinuous transmission. In this case, for each frame in the test interval, a TDSO state for the current frame is updated, at step 318. A determination is then made whether or not test data, is to be transmitted for the current frame based on the updated TDSO state, at step 320. If test data is to be transmitted, one or more blocks of test data are retrieved from a particular section of the circular buffer, at step 322. These steps are described in further detail below.

FIG. 4 is a block diagram of the buffers and pseudo-random number generators used for generating pseudo-random test data for a forward and a reverse traffic channel, in accordance with an embodiment of the invention. In this embodiment, one pseudo-random number generator is associated with each traffic channel to be tested on each of the forward and reverse links. For example, if the TDSO is configured to transmit data over the FCH in the forward and reverse links and over the SCHO only in the forward link, then three pseudo-random number generators are used at the base station and three pseudo-random number generators are used at the remote terminal (only two generators are shown on each side in FIG. 4).

In the embodiment shown in FIG. 4, base station 104 includes pseudorandom number generators 440a and 440b used to generate pseudo-random data for a traffic channel on the forward and reverse links, respectively. The generated test data from generators 440a and 440b is provided to test data buffers 412a and 412b, respectively. Similarly, remote terminal 106 includes pseudo-random number generators 480a and 480b used to generate pseudorandom data for the traffic channel on the forward and reverse links, respectively, which is provided to test data buffers 482a and 482b, respectively.

Additional pseudo-random number generators are used for additional traffic channels to be tested. In an embodiment, pseudo-random number generators 440a, 440b, 480a, and 480b are initialized and synchronized at each synchronization frame once every test interval), as described in further detail below.

12 O In an embodiment, each pseudo-random number generator exhibits the following linear congruential relationship:

O

Sx x x, mod m Eq (1) In an embodiment, a 75 16807, m 231-1 2,147,483,647, and and are c 5 successive outputs of the pseudo-random number generator and are 31-bit integers. Other values may also be used for a and m.

Cl In an embodiment, each pseudo-random number generator is initialized prior to each synchronization frame on the traffic channel associate with the Sgenerator. The initialization may be achieved as follows: a 16807 m 2147483647 PRNGx seed value seed the generator PRNGx PRNGx XOR TOGGLE toggle some of the bits PRNGx PRNGx AND Ox7FFFFFFF zero out the MSB PRNGx (a*PRNGx) mod m iterate the generator PRNGx (a*PRNGx) mod m four times PRNGx (aoPRNGx) mod m PRNGx (a*PRNGx) mod m In the above pseudo-code, PRNGx denotes the content of the x h pseudorandom number generator. The seed for the pseudo-random number generator may be selected as the system time, in frames, of the synchronization frame the system frame number of the synchronization frame may be used as the seed for the pseudo-random generator). TOGGLE is a value used to toggle some of the bits of the seed, and may be selected as Ox2AAAAAAA for a generator used for the forward link and 0x55555555 for a generator used for the reverse link. As used herein, the notation denotes a hexadecimal number.

Once initiated, the pseudo-random number generator is iterated a number of times to generate the pseudo-random test data to be used for the upcoming test interval. The number of test data bits to be generated is dependent on various factors such as the traffic channel type FCH, DCCH, or SCH) the connected radio configuration of the remote terminal,

C.)

INO physical layer for each frame period, the size of the available buffer, and possibly other factors. The multiplex sublayer is a protocol layer between a physical layer and a higher layer, and which multiplexes traffic data, test data, signaling, and other types of data received from the TDSO to the assigned traffic channel(s).

In an embodiment, test data bits are generated for N frames at the maximum bit rate possible for the connected radio configuration, as described in further detail below. A default value of two, for example, may be set for N, unless another value for N is negotiated between the base station and remote terminal. A larger value for N may provide test data having better randomness properties but requires a larger-sized buffer.

After initialization, the pseudo-random number generator is used to generate test data bits for N frames. During the test data generation, whenever a pseudo-random number is needed, the current value of the variable PRN\Gx is retrieved and used, and the variable PRNGx is then updated iterated) once as shown in equation In an embodiment, only the most significant 24 bits of the 31-bit number for PRNGx are used because of better randomness properties and ease of usage, and the least significant 7 bits are discarded. Thus, each iteration of the pseudo-random number generator provides a 24-bit pseudorandom number, yj(k), used to provide three bytes of test data. P(n) iterations are performed to generate the required test data for N frames.

IFIG. 5 is a diagram that ilustrates a reshuffling of each pseudo-random number to generate 24 bits of test data. Using the 31-bit number from the pseudo-random number generator to generate test data is inefficient, from an implementation point of view, because the number is not octet aligned. It is easier to build a frame with a number that is octet aligned. The least significant bits of the 31-bit number are 'less random" than the most significant bits, and are thus shuffled to the right. In an embodiment, each 24-bit pseudo-random number yj 2 k) from the pseudo-random number generator, where 1 5 k:5 is reshuffled and stored in "little-endian" order. The reshuffling is achieved by swapping the least significant byte in the 24-bit number yjk) with the most significant byte to generate the reshuffled number yE C0 To generate test data for a new test interval for a particular rate the INO TDSO generates P(n) pseudo-random numbers corresponding to an actual buffer size where BNi) NeR(n). As an example, to generate 344 test data bits, the pseudo-random number generator is iterated 15 times (15.24=360, which is the first integer number of iterations that yield at least 344 bits). The buffer is then filled with the following number sequence: The buffer is filled with test data at the start of each test interval and prior to the synchronization frame. Thereafter, for each "active" frame in the test interval in which test data is to be transmitted, test data bits may be retrieved from the buffer to generate one or more data blocks for the frame. For a particular traffic channel, the bits from the buffer are packed serially into one or more data blocks corresponding to the available IvUX PDU (Protocol Data Unit), as determined by the connected multiplex option, where each MUX PDU represents encapsulated data communicated between peer layers at the base station and remote terminal).

In an embodiment, the test data buffer is operated as a circular buffer and test data for each frame is retrieved from a particular section of the circular buffer starting from a particular location in the circular buffer). Initially after filling the circular buffer with at least two frames of test data), a buffer pointer is set to the first location in the buffer address zero). In an embodiment, at the start of each frame, the pseudo-random number generator is iterated once and a 24-bit number is obtained as described above. The least significant 6 bits of this 24-bit number, is then used to determine an offset for the buffer pointer. The buffer pointer is advanced from its current location by [0Q, mod byte positions to the new starting location for the current frame. Bytes of test data are then retrieved from the circular buffer, starting from this starting location, to fill whole octets in a data block. For example, if a data block includes 171 bits, then 21 bytes 168 bits) of test data are retrieved from the circular buffer and the remaining three bits in the data block are filled with zeros For the next frame, the pseudo-random number generator is iterated N once more, the least significant 6 bits of the 24-bit number, from the o generator is used to determine the buffer pointer offset for this frame. The IN buffer pointer is advanced by mod byte positions from the current location (which is one byte position over from the last test data byte retrieved for the prior frame). This process for generating data blocks is repeated for each active frame in the test interval in which test data is to be transmitted. An Sexample of the test data generation is provided below.

10 Frame and Buffer Sizes O As noted above, the pseudo-random number generator for a particular traffic channel and (forward or reverse) link to be tested is iterated a number of times as often as necessary) to generate the test data to be used for a test interval. The number of test data bits to be generated for each test interval is based on the channel type and radio configuration. Table 1 lists the maximum number of bits for each (5 msec, 20 msec, 40 msec, or 80 msec) frame and the buffer size for the FCH and DCCH for various radio configurations defined by the cdma2000 standard.

Table 1 Forward Radio Buffer Size Reverse Radio Buffer Size for Configuration Maximum for Configuration Two Frames (RC) bits/frame N Frames (RC) (bits) (bits) 1,3,5 1,3,4,6, or 7 172 2 x 172 344 N x 172 2,4,6 2,5, 8, or 9 267 2 x 267 534 Nx 267 Table 2 lists the maximum number of bits per frame and the buffer size for a forward supplemental channel (F-SCHO or F-SCH1) for various radio configurations defined by the cdma2000 standard.

Table 2 Radio Cniuain Maximum Buffer Size for Buffer Size for CofRatio bits/frame Two Frames (bits) N Frames (bits) 3 3,048 2 x 3,048 =6,096 N x 3,048 4 6,120 2 x 6,120 =12,240 N x 6,120 4,584 2 x 4,584 =9,168 N x 4,584 6 6,120 2 x 6,120 =12,240 N x 6,120 7 12,264 2 x 12,264 =24,528 N x 12,264 8 9,168 2 x 9,168 =18,384 N x 9,168 9 20,172 2 x 20,172= 41,424 Nx2072j Table 3 lists the maximum number of bits per frame and the buffer size for a reverse supplemental channel (R-SCHO or R-SCH1) for various radio configurations defined by the cdma2000 standard.

Table 3 Radio Maximum Buffer Size for Buffer Size for Configuration bits/frame Two Frames (bits) N Frames (bits)

(RC)

3 6,120 2 x 6,120 =12,240 N x 6,120 4 4,584 2 x4,584 9,168 N x4,584 12,264 2 x 12,264=24,528 N x 12,264 r- 6 20,172 2 x 20,172 =41,424 N x 20,172 Discontinuous Transmission Testing In accordance with an aspect of the invention, the testing of a traffic channel may be performed in a manner to model discontinuous transmission (DTX) supported by some newer generation COMA systems the cdma2000 and W-CDMA systems). This DTX testing may be achieved by transmitting test data on the traffic channel in accordance with a particular ON/OFF frame activity. For each frame period each 20 msec, 40 nisec, or 80 msec) for the tra-ffic channel, the TDSO may choose to provide to the O multiplex sublayer either one or more data blocks corresponding to a full-rate C frame on that channel or one or more blank data blocks. Various DTX schemes O may be used to provide data to the multiplex sublayer to achieve a particular desired frame activity. Some of these DTX schemes are described in further detail below.

In a first DTX scheme, test data is provided based on a deterministic c frame activity. For this DTX scheme, test data is transmitted on the traffic channel for a particular ON duration, followed by blank data transmission for a C^ particular OFF duration, followed by test data transmission for another ON duration, and so on. The ON and OFF durations may be selectable or negotiated between the base station and remote terminal. Also, the ON/OFF cycles may be periodic or non-periodic.

FIG. 6 is a diagram that illustrates test data transmission for an embodiment of the first DTX scheme. As shown in FIG. 6, the TDSO sends to the multiplex sublayer test data blocks for a traffic channel for a particular ON duration, and then sends blank data blocks for a particular OFF duration. The ON/OFF cycle may be designated to start at the beginning of a synchronization frame on the traffic channel being tested. The ON and OFF durations may be selected such that each test interval includes one ON/OFF cycle, a test interval includes multiple ON/OFF cycles, or an ON/OFF cycle spans multiple test intervals.

In an embodiment, the ON duration for transmitting test data and the OFF duration for transmitting blank data may be specified by two parameters TX_ON_PERIOD and TX_OFF_PERIOD) in a message a Service Option Control Message in the cdma2000 system) sent or received by the transmitting source.

In a second DTX scheme, test data is provided in a pseudo-random manner based on a particular average frame activity and burst length. This DTX scheme may be used to achieve a particular (desired or selected) long-term average of frame activity and a particular average burst length for a traffic channel. The average frame activity D refers to the average number of frames in each ON duration versus the average number of frames in each ON/OFF cycle. And the average burst length B refers to the average number of frames in each ON duration.

18 FIG. 7 is a diagram of a two-state first-order Markov chain that may be Sused to model the ON/OFF states for the TDSO for the second DTX scheme. In o an embodiment, one Markov chain is maintained for each traffic channel being tested. At the start of each frame, the TDSO is either in the ON state or the OFF state. The Markov chain is characterized by a probability p of transitioning from the ON state to the OFF state, and a probability q of transitioning from the c, c OFF state to the ON state. The values of p and q may be specified by two parameters ON_TO_OFF_PROB and OFF_TO_ON_PROB) in a message a Service Option Control Message) sent by the transmitting source the base station).

SThe long-term average frame activity D may be defined as: D -q Eq (2) p+q And the average burst length B may be defined as: B Eq (3)

P

For some testing, it may be desirable to select the average frame activity D and the average burst length B, and then determine the corresponding values for p and q based on the desired D and B. Combining and rearranging equations and the following are obtained: D Bq Eq (4) 1+Bq

D

B D Eq D)q Equation indicates that for a given value of B, D varies from 0 to B(1+B) when q varies from 0 to 1, respectively. Similarly, equation indicates that for a given value of D, B varies from to infinity when q varies from 0 to 1, respectively. For example, when B is selected as 2, D should be smaller than 2/3, which indicates that the average frame activity D cannot be set higher 1^ 0 than 2/3 when B is set to 2. As another example, if D is set to 7/10, then B is set CN1 greater than 7/3.

O In an embodiment, a 24-bit) pseudo-random number is used to O drive the transition between the ON and OFF states for each frame period (each 5 msec, 20 msec, 40 msec, or 80 msec). In an embodiment, one pseudo-random number generator is used for all traffic channels having the same frame length.

For example, one pseudo-random number generator is used for all traffic channels having 20 msec frame length. A second pseudo-random number generator is used for supplemental channels configured for 40 msec or 80 msec p. 10 frame length, and this generator is updated every 40 msec or 80 msec O corresponding to the channel frame length. In an embodiment, the pseudo- CI random number generator(s) used to drive the TDSO states are different than the ones used to generate the test data.

In an embodiment, the pseudo-random number generator(s) used to drive the transitions between TDSO states are initialized at the start of the first synchronization frame after the TDSO is initialized. Upon initialization, the Markov chain for each traffic channel is set to a particular state OFF). The pseudo-random number generator(s) are thereafter maintained throughout the duration of the call, without reinitialization at subsequent synchronization frames. These generators may be reinitialized upon completion of a CDMA- CDMA hard handoff.

FIG. 8 is a flow diagram of an embodiment of a process for transitioning between the ON and OFF states of the Markov chain for a traffic channel.

Initially, the pseudo-random number generator used to drive the TDSO states for the traffic channel is initialized, at step 812. This initialization may be achieved, for example, by obtaining a seed for the generator, XORing the seed with the value Ox2AAAAAAA, ANDing the result with the value Ox7FFFFFFF, and iterating the generator four times with the modified seed, as described in the above pseudo-code.

In an embodiment, a 24-bit pseudo-random number from the pseudorandom number generator is used to determine whether or not to transition from one state to another. Thus, 24-bit ON and OFF threshold values are computed, at step 814. These thresholds may be computed as: ON_THRESHOLD ROUND (16,777,215 and OFF_THRESHOLD ROUND (16,777,215 p).

As shown in FIG. 7, the TDSO for the traffic channel transitions from the O ON state to the OFF state with a probability of p, and from the OFF state to the I ON state with a probability of q. Based on a pseudo-randomly generated 24-bit number, the TDSO transitions from the ON state to the OFF state if this number is less than the OFF_THRESHOLD, and from the OFF state to the ON state if n this number is less than the ON_THRESHOLD. Steps 812 and 814 are typically performed once, prior to the first synchronization frame after the TDSO has Cl been initialized.

The steps within box 820 are thereafter performed for each frame period.

Initially, a 24-bit pseudo-random number is generated from the current 31-bit state of the pseudo-random number generator, at step 822. A determination is next made whether or not the current TDSO state for the traffic channel is OFF, at step 824.

If the current TDSO state is OFF, a determination is made whether, the 24-bit number is greater than or equal to the ON_THRESHOLD, at step 826. If the answer is yes, the TDSO remains in the OFF state, at step 828. Otherwise, the TDSO transitions to the ON state, at step 832. In either case, the.process then proceeds to step 834.

If the current TDSO state is ON (determined back at step 824), a determination is then made whether the 24-bit number is greater than or equal to the OFF_THRESHOLD, at step 830. If the answer is yes, the TDSO remains in the ON state, at step 832. Otherwise, the TDSO transitions to the OFF state, at step 828.

At step 834, the pseudo-random number generator is iterated once, as shown in equation to update the state of the generator for the next frame.

Data Block Header and Format In accordance with an aspect of the invention, each test data block is appropriately identified to enable concurrent testing of multiple traffic channels and for frames with multiple data blocks per frame. In an embodiment, the

I

Cc, Cc, Cc, identification is achieved via a header provided in each data block supplied to the multiplex sublayer for each frame.

FIG. 9 is a diagram of an embodiment of a test data block 900, which includes a channel ID field 912, a PDU (data block) sequence number field 914, and a test data field 916. Channel ID field 912 identifies the particular traffic channel used to send this data block. PDU sequence number field 914 identifies the sequence number of this data block within the frame within a physical layer service data unit For a FCH or DCCH carrying one data block per frame, this field is set to And for an SCH capable of carrying multiple data blocks per frame, this field is set to for the first data block in the SCH frame, for the second data block in the SCH frame, and so on. Test data field 916 includes the (defined or pseudo-random) test data generated as described above.

Table 4 lists the fields and their lengths and definitions for an embodiment of test data block 900.

Table 4 Field Length (bits) Definition Channel ID of traffic channel used to Channel ID 2 carry the data block PDU Sequence 3Sequence number of the data block within Number a physical layer SDU Test Data Variable Test data bits Table 5 shows a specific definition of the Channel ID field for various traffic channel types in the cdma2000 system.

Table Channel ID Traffic Channel 0 FCH 1 DCCH 2 SCHO 3 SCH1 SExample of Test Data Generation o For clarity, the test data generation is now described for a specific O example. In this example, the following parameters are used: The TDSO is configured to transmit primary traffic over the FCH.

o The base station and remote terminal are configured to support radio configuration 3, and the frame length is 172 bits.

Multiplex option 0x01 is selected for the FCH, and one data block is C passed to the multiplex sublayer for each active (20 msec) frame.

0 10 The average frame activity D and average burst length B are based on the probabilities p 0.7 and q 0.3. Thus, D 0.3, B 1/p 1.4, ON_THRESHOLD= ROUND (16,777,215 p) 11,744,051, and OFF_THRESHOLD ROUND (16,777,215 q) 5,033,164.

The least significant 32 bits of the remote terminal's Public Long Code Mask (PLCM) is equal to 0x9F000307.

A first pseudo-random number generator used to determine the transitions between the ON/OFF states of the Markov chain for this traffic channel has a current value of Ox682DFFOC.

For this example, the TDSO is about to transmit frame number OxAB89EFAD on the forward FCH (F-FCH) to the remote terminal. The frame number is XORed with the value 0x2AAAAAAA, and the least significant 9 bits of the XOR result is equal to 0x107, which is equal to the least significant 9 bits of the remote terminal's PLCM. This frame is thus the synchronization frame for the F-FCH, and the test data generation process is resynchronized.

As part of the resynchronization, a second pseudo-random number generator used to generate test data for the F-FCH is reinitialized by seeding it with the frame number OxAB89EFAD, performing an XOR of the seed with the value Ox2AAAAAAA to generate the value 0x01234507, and (3) iterating the pseudo-random number generator four times, as described in the above pseudo-code.

After reinitialization, the state of the second pseudo-random number generator is 0x3B7E3E68, the most significant 24 bits of this state is Ox76FC7C, and the least significant 6 bits of this 24-bit number is Ox3C. This 6-bit number, is later used to determine the offset for the circular buffer.

number of iterations that will provide at least 344 bits included in two frames for radio configuration The actual buffer size is thus B(n) 45 360 bits 45 bytes).

O The generation of the test data proceeds as follows. Prior to each I_ 5 iteration, the current state of the second generator is obtained and the most significant 24 bits are used to form a 24-bit number. The following sequence of o 24-bit numbers are generated by the second pseudo-random number generator: yn(l) Ox76FC7C yn(6) Ox4CA46B yn(ll) <1 10 yn(2) OxBA6678 yn(7) OxBE783D yn(12) 0x478744 yn(3) Ox9D7F54 yn(8) OxC7EDAF yn(1 3 Ox01A3DE Ox1279A7 yn(9) OxC5BDB3 yn(14) OxAD4A7D OxFOE8EF yn(10)= Ox29428D yn(15) OxF58934 Each 24-bit number is then stored to a circular buffer for the F-FCH in little-endian fashion, as described above. For example,.the first 24-bit number Ox76FC7C is stored as Ox7CFC76, where the most and least significant bytes of the number are swapped to generate the reshuffled number y,LE(k). The circular buffer used to generate the data blocks for the F-FCH for the next 512 frames in the test interval includes the following byte sequence: 41- 7C FC 76 78 66 BA 54 7F 9D A7 79 12 EF E8 FO 6B A4 4C 3D 78 BE AF ED C7 B3 BD C5 8D 42 29 FE 5B DO 44 87 47 DE A3 01 7D 4A AD 34 89 F5 The first pseudo-random number generator used to determine the ON/OFF state is then updated, and a new 24-bit number having a value of 0x478744 (4,687,684) is generated. The first pseudo-random generator is updated at the end of the first iteration of the loop and after the 24-bit number is calculated, it is tested against the ON_THRESHOLD during the second iteration around the loop. Since this value is less than the ON_THRESHOLD value of 11,744,051, the TDSO transitions from the OFF state to the ON state, and a data block is provided to the multiplex sublayer for the current frame.

To generate this data block for the first frame in the test interval, the offset for the buffer pointer is computed as O, mod B(n) 0x3C mod 45 mod 45 15). The buffer pointer (which is initialized to zero upon reinitialization) is thus advanced by 15 byte positions, from Ox7C to Ox6B. The C 171 bits for the data block are then formed with 21 bytes (168 bits) retrieved from the circular buffer, starting at the buffer location identified by the O advanced buffer pointer. The remaining three bits in the data block are filled D 5 with zeros. The data block includes the following byte sequence: 6B A4 4C 3D 78 BE AF ED C7 B3 BD C5 8D 42 29 FE 5B DO 44 87 47 '000' cSince this frame is to be sent over the F-FCH, the first 5 bits of the octet Ci are replaced by '00000' corresponding to the channel ID of '00' and the PDU Ssequence number of '000'. The final test data block is as follows: 03 A4 4C 3D 78 BE AF ED C7 B3 BD C5 8D 42 29 FE 5B DO 44 87 47 '000' For the next TDSO frame, a new 24-bit number having a value of 107,486 is generated by the first pseudo-random number generator. Since this value is less than the ON threshold, the TDSO remains in the ON state and a new data block is generated for the multiplex sublayer.

For the second frame in the test interval, the second pseudo-random number generator is iterated, and a 24-bit number having a value of Ox02F3FD is generated. The 6-bit number O, for the buffer offset has a value of Ox3D. The buffer offset is then computed as O, mod B(n) Ox3D mod 15 61 mod 45 16). The buffer pointer (which was pointing one byte location over from the last retrieved byte value of 0x47 for the last data block) is thus advanced by 16 byte positions from OxDE to Ox6F. The 171 bits for the data block are then formed with 21 bytes from the circular buffer, starting at the new buffer location. The remaining three bits in the data block are filled with zeros. The data block includes the following byte sequence: 7F 9D A7 79 12 EF E8 FO 6B A4 4C 3D 78 BE AF ED C7 B3 BD CS 8D '000' After replacing the first 5 bits with '00000' corresponding to the data block header for the F-FCH, the data block provided to the multiplex sublayer is as follows: 07 9D A7 79 12 EF E8 FO 6B A4 4C 3D 78 BE AF ED C7 B3 BD C5 8D '000' The buffer pointer now points to the next byte position (0x42) for the next frame.

0 0 TDSO Frame Transmission and Reception To test a particular traffic channel, the data block(s) for each "active" O frame are generated based on a defined data pattern or a pseudo-random 5 number generator, as described above. The transmitting source and receiving device are synchronized so that the receiving device is able to properly C generate the transmitted frames, such that the received frames may be Cc C compared with the locally generated frames. Each data block in each frame is appropriately identified to indicate the particular traffic channel used to N, 10 send the data block and the data block number within the frame. The TDSO Sis able to compare the received and locally generated frames, count the errors, 1 determine the bit error rate (BER), PDU or data block error rate (PER), and frame error rate (FER), and compute other measures of performance.

The testing thus includes processing performed at the transmitting source to transmit a test frame and processing performed at the receiving device to receive a test frame.

The transmit frame processing includes: Generating one or more data blocks for each active frame.

Supplying the generated data block(s) to the multiplex sublayer for transmission.

Incrementing the appropriate counters.

For a test of the FCH or DCCH that operates on 20 msec frames, the TDSO provides one data block to the multiplex sublayer for each active frame interval in which the TDSO state for the traffic channel is ON. For a test of the SCH, the TDSO provides NB data blocks to the multiplex sublayer for each active frame interval (20 msec, 40 msec, or 80 msec), where NB is the maximum number of data blocks in a physical layer SDU for the connected service option.

Each data block may be generated as described above, and includes the header and test data.

The receive frame processing includes: Generating one or more data blocks for each active frame.

Receiving data block(s) from the multiplex sublayer.

Comparing the rates and contents of the received and generated data block(s).

SIncrementing the appropriate counters.

r At the receiving device, the multiplex sublayer categorizes each received O data block as either test data or blank) and the frame. The multiplex sublayer then supplies the data block type and received test data bits, if any, to

\O

the TDSO.

Various counters may be maintained at the transmitting source and Cc receiving device to support TDSO. For each traffic channel to be tested, a set of or3 or counters may be maintained at the transmitting source to keep track of the C number of frames (of various types) and data blocks transmitted to the receiving device. At the receiving device, another set of counters may be maintained to keep track of the number of frames, data blocks, and data bits received from the transmitting source, the number of frame errors, block errors, and bit errors, and so on. These counter values may be stored in a buffer. This buffer is typically implemented separate from the data buffer, and is used to store various counters over a period of time. The counter values may thereafter be used to determine the FER, PER, and/or BER, and other statistics such as the average frame activity, average burst length, and so on. The test results and statistical information may be reported from the remote terminal to the base station via one or more messages.

Test Data Service Option In accordance with an aspect of the invention, the test data service option (TDSO) is a service that may be negotiated and connected using the available service configuration and negotiation procedures defined by a particular CDMA system and used for other services a voice call, a data call). The remote terminal may be able to propose and/or accept a service configuration having attributes that are consistent with valid attributes for that configuration. The remote terminal may also be able to indicate the preferred radio configurations for the forward and reverse links.

In an embodiment, the remote terminal is able to propose or invoke service-option-specific functions for a TDSO call by sending a message a Service Option Control Message in the cdma2000 system) to the base station. This message may be sent such that an acknowledgement is requested or required from the base station. Via the message, the remote terminal may propose values for various test parameters to be used during the test period.

The base station receives the message and may accept or reject the Sremote terminal's proposed test parameter settings. If all the fields in the remote terminal's directive are within acceptable ranges for the base station, the O base station may issue a directive that accepts the remote terminal's proposal.

N 5 This directive may be sent to the remote terminal via a response message a Service Option Control Message) that includes the same values, as proposed by Cc the remote terminal, for the various fields.

Cc Alternatively, if the remote terminal proposes a particular test setting not Ssupported by or acceptable to the base station, the base station may issue a directive that may include alternative values counter-proposals) to the Sremote terminal's proposed values. This directive may be sent to the remote C terminal via a response message that includes the proposed values in the fields supported and accepted by the base station, and counter-proposed values in the fields not supported or accepted by the base station. For example, if the remote terminal requests a particular number of circular buffer frames N that is not supported by the base station, the base station may response with a value indicating the maximum number of frames for the buffer supported by the base station.

Thus, via messaging and negotiation, the base station is able to accept the remote terminal's proposal, or reject the proposal and provide alternative values for test parameters.

Upon receiving the response message from the base station, the remote terminal may accept the counter-proposed values or select new values that conform to the counter-proposed values. The remote terminal may then send to the base station another message proposing these new values.

Table 6 lists the valid service configuration for TDSO for a specific implementation in the cdma2000 system.

Table 6 Service Configuration Attribute Valid Selection Forward Multiplex Option 0x01 or 0x02 Reverse Multiplex Option 0x01 or 0x02 For the FCH Rates 1, 1/2, 1/4, and 1/8 enabled Forward Transmission Rates For the DCCH Rate 1 enabled, Rates 1/2, 1/4, and 1/8 not enabled For the FCH, Rates 1, 1/2, 1/4, and 1/8 enabled.

Reverse Transmission Rates For the DCCH, Rate 1 enabled, Rates 1/2, 1/4, and 1/8 not enabled.

Forward Traffic Type Primary or Secondary Should be Identical to the Forward Reverse Traffic Typefic Type Forward FCH Radio Configuration RC 1,2,3,4,5,Type8, or 9 Forward FCH Radio Configuration RC 1, 2, 3, 4,5,6,7, or Reverse FCH Radio Configuration RC 1,23,4,5,6,, or 6 Forward DCCH Radio Configuration RC 3, 4, 5, 6,8, or Reverse DCCH Radio Configuration RC 3,4, 56,, or 6 Forward SCH Radio Configuration RC 3, 4, 5,6,8, or Reverse SCH Radio Configuration RC 3, 4, 5, or 6 Forward SCH Frame Size 20 ms, 40 ms, or 80 ms Reverse SCH Frame Size 20 ms, 40 ms, or 80 ms 0x921, 0x911, 0x909, 0x905, 0x821, Forward Supplemental Channel 0x811, 0x809, 0x03 Multiplex Option 0x922, 0x912, Ox90a, 0x906, 0x822, 0x812, Ox80a, 0x04, 0x921, 0x911, 0x909, 0x905, 0x821, Reverse Supplemental Channel 0x811, 0x809, 0x03 Multiplex Option 0x922, 0x912, Ox90a, 0x906, 0x822, 0x812, Ox80a, 0x04, 29 r As noted above, a number of traffic channels may be concurrently tested 0 Son each of the forward and reverse links. For each traffic channel to be tested, the test parameters for the channel may be negotiated via the signaling and O negotiation described above. Thus, traffic channels of various types on the IND 5 forward and reverse links may be tested independently based on their respective sets of test parameter values.

In FIGS. 2A, 2B, and 4, the elements in the base station and remote F" terminal may be implemented by various means. For example, the pseudorandom number generators may be implemented with hardware, software, or a C 10 combination thereof. For a hardware implementation, pseudo-random number generators, controllers, and other processing units may be implemented within Sone or more application specific integrated circuits (ASICs), digital signal processors (DSPs), programmable logic devices (PLDs), controllers, microcontrollers, microprocessors, other electronic units designed to perform the functions described herein, or a combination thereof.

For a software implementation, these processing units may be implemented with modules procedures, functions, and so on) that perform the functions described herein. For example, the pseudo-random number generators may be implemented with software code stored in a memory unit and executed by a processor controller 220 or 270).

The circular buffers for the test data for the traffic channels may be implemented with one or more buffers, which may be implemented using RAM, DRAM, Flash memory, or some other memory technology. Also, the pseudo-random number generators may be operated to generate test data for the traffic channels as the data is needed, without having to store the test data in buffers. In that case, the states of the pseudo-random number generators are appropriately maintained and updated such that the generators are able to generate the proper sequence of test data for each active frame.

Although various aspects, embodiments, and features of the test data generation and traffic channel testing of the invention have been described for the cdma2000 system, these techniques may be advantageously applied for the other wireless communication systems and other CDMA systems the W- CDMA system).

A specific implementation of various aspects of the invention for a cdma2000 system is described in the following Exhibit A.

EXHIBIT A 4-4 0 Test Data Service Option (TDSO) for cdma2000 Spread Spectrum Systems N PN-4877 Ballot Version November 13,2000 Contents REEEC- 1 General ,38 1. 38 .2Notation 2 Test Data Service Otion 2.1 Overview 2.2 General description 2.3 Service option 42 2.4 ReQuired multiplex option 42 2.4.1 Multiplex option support for FCH/DCCH (for 20 ms PCHMDCCH frames 0D 42 2.4.2 Multiplex option support for S 43 2.5 Interface to multiplex options 44 2. m 2.6.1 Secondary 46 2.7 TDSO frame trnsmission and 48 2.7.1 Transmitted 49 2.7.2 Received frames 2.8 Interface to Layer 3 Sienaling when testiniz Copyright 2000 TIA. Coyiht©200TA s FCH/DCCH frames 3 TDSO Procedures and 51 3.1 Negotition and activation of service option 51 3.1.1 Mobile station 51 Q3.1.1 Supplemental channel allocation 53 53.1.1.2 CDM-CDMA hard handoff 57 3.1.2 Base station requirements 3.2 Synchronization 58 3.2.1 Forward Traffic Channels 58 3,1.2 Forward Supplemental Channels 59 C110 3.2.3 Reverse Traffic 3.2.4 Reverse Supplemental 59 3.3 59 rl3.4 Mobile station-initialization and control operation 63 3.4.1 Service option initialization 63 3.4.2 Mobile station control 3.4.2.1 Contol 3A4.2.2 Control directive 3.4.2.3 Counter 67 station initialization and control operations 67 3.5.1.1 Control invocation 67 3.5.1.2 Control 68 3.5.1.3 Counter 68 3.6 TDSO Frame 69 3.6.1 Transmit frame 69 3.6.2 Receive flame proessing 72 3.6.3 Transmit frame processing for 5 ms FCI{/DCCH 76 3.6.3.1 Mobile Station Requiremen 76 3.6.3.2 Base Station Reqluirement 77 3.7 TDSO frame 78 3.7.1 Selectable bWt 78 3.7.2 Pseudo-random number 78 3.7.2.1 3.7.2.2 Nuimber production 81 3.7,2.3 24-bit random 82 3.7.3 Circular buffer sizes 82 3.7.4 Information bit 84 337.5 Frame activty 86 3.7.5.1 Deterministicfraime 86 3.7.5.2 Random with a specified frame activity and burst length 87 3.7.6 Data block header and 89 3.8 Message formats 91 3.8.1 Service Option Control Message 91 3,8.1.1 Control 91 3.8.1.2 Counter retrieval 97 3.8.1.3 Counter responses on the fundicated 99 3.8.1.4 Receive Expected Counters 102 3.8.1.5 Transmitted Counters 105 3.8,1.6 5 ins Frame Transmitted Counter 107 3.8.1.7 5 ins Fram Received Counters Response IO 3.8.2 Counter responses -on the Suppemnental 109 3.9.2.1 FER counters 109 3,8.2.2 PER Counters Response 11 3.8,2.3 Transmitted Counters 115 ANNEX A TDSO Call Flow Examples (for a system operaing in MC-41 mode) 116 ANNEX B TWSO Operation Examples 119 ANNEX C Using the TDSO 137 ANNEX D Calculating p and gj Based on D and 142 Figures Figure 1. Synchronized operation of pseudo-random number generated 79 Figure 2. Reshuffling of to generate y f Figure 3. Two-state Markov chain representing ON/OFF transitions for TDSO 88 Figure 4. Flowchart illustrating TDSO state transitions for a D frame activity and B average "On" period in units of frames 89 Figure 5. Mobile station origination example with transmission on DCCH/FCHISCH (part I of 117 Figure 6. Mobile station origination example with transmission on DCCH/FCH/SCH (part 2 of 118 Figure 7. Base station commanded test parameters change 119 Tables ~Table 1. Summary of test data service option notation 33 Table 2 Multiplex option support for FCH or Table 3 Multiplex options applicable to an Table 4 Primary traffic types supplied by the TDSO to the multiplex OTable 5. Primary traffic frame types supplied by the multiplex layer to TDSO

\D

Table 6 Secondary traffic frames supplied by TDSO to the multiplex Table 7. Secondary traffic frames supplied by multiplex sublayer to the ST D SO 48 Table 8 Valid service configuration attributes for test data service Table 9 SCRM_REQBLOB format 54 Table 10 SCRMM_REQBLOB 56 Table 11 Encoding of the PREFERREDRATE 57 Table 12 Encoding of the DURATION Table 13 Transmit frame counters on the fundicated channel Table 14 Transmitted frame counters on the Supplemental Table 15 Receive frame counters maintained for the FCH/DCCH Table 16 Receive frame counters on the Supplemental Table 17 Receive PDU counters maintained for the Supplemental Table 18 Frame counter-value 62 Table 19 Frame counter-value storage for Supplemental Channels 63 Table 20 Counters for fundicated transmitted 71 Table 21 Counters for supplemental transmitted Table 22 Counter updates for received fundicated frames when MuxPDU Type 1 is 73 Table 23 Counter updates for received fundicated frames when MuxPDU T ype 2 is used 74 Table 24 Counter updates for PDUs received on Supplemental Channels Table 25 Counter updates for received frames on Supplemental Channels 76 Table 26 Circular buffer sizes needed to generate fundicated channel data fram 83 Table 27 Circular buffer sizes needed to generate reverse Supplemental C hannel data fram es 83 Table 28 Circular buffer sizes needed to generate forward Supplemental Channel data frames 8 o Table 29 Procedure for generating the default circular buffers for RC>2 0channels 8 IND 5 Table 30 Data block format 9 Table 31 CHANNEL.JD type 9 Table 32 CTLRECTYPE 9 Table 33 Service Option Control Message type-specific 9 Table 34 CONTROLCODE codes 9 Table 35 DATA-SOURCE codes 9 KITable 36 FRAMvE.ACTIVITY codes Table 37 CHANNEL.DJRECTION codes A Table 38 FRAMESOTJRCE codes.. 9 Table 39 TOPTIONS 9 Table 40 Type-specific fields in a Service Option Control Message used for counter retrieval on the 9 Table 41 VECT_COUNTERID codes for 9 Table42 Type-specific fields in a Service Option Conztrol Message used for counter retrieval from the mobile station for SCHs 6 9: Table 43 VECTCOUNTERID codes for SCHs Table 44 Type-specific fields in a Service Option Control Message corresponding to FER Counters Response on FCH/DCCH Table 45 Type-specific fields in a Service Option Control Message corresponding to Receive Expected Counters Response on Table 46 Type-specific fields in a Service Option Control Message corresponding to Transmitted Counters Response on Table 47 Type-specific fields in a Service Option Control Message corresponding to 5 ms Frame Transmnitted Counters Response on FCHIDCCH 6 Table 48 Type-specific fields in a Service Option Control Message corresponding to 5 ins Frame Received Counters Response on FCHIDCCH Table 49 Type-specific fields in a Service Option Control Message corresponding to FER Counters Response on SCH(s) Table 50 Type-specific fields in a Service Option Control Message Scorresponding to PER Counters response on SCH(s) 111 Table 51 Type-specific fields in a Service Option Control Message 0 corresponding to Transmitted Counters response on \O

FOREWORD

e This document specifies procedures for the Test Data Service Option (TDSO).

c The TDSO is used to allow verification of the physical layer performance frame error rate (FER) and PDU error rate (PER) of cdma2000 physical channels.

C 10 The document is organized into the following sections: Chapter 1 defines the terms and notations used in this document.

Chapter 2 outlines the requirements of the TDSO and provides a general description of the

TDSO.

Chapter 3 describes the detailed procedures and operation of the mobile station and the base station for the TDSO.

Annex A is an informative section that presents some TDSO call flow examples.

Annex B is an informative section that presents some TDSO frame generation examples.

Annex C is an informative section that presents some procedures for conducting a TDSO test. It also shows the use of the transmit counters and the receive counters for estimating the FER and PER for the Forward and Reverse Traffic Channels.

Annex D is an informative section that presents the equations for calculating transition probabilities p and q based on average frame activity and average burst length

NOTES

"Base station" refers to the functions performed on the landline side, which are typically distributed among a cell, a sector of a cell, and a mobile switching center.

S The following verbal forms: "Shall" and "shall not" identify requirements to be followed strictly to conform to the standard and from which no deviation is permitted. "Should" and "should not" indicate that one of several possibilities is recommended as particularly suitable, without mentioning or excluding others; that a certain course of action is preferred but not necessarily required; or that (in the negative form) a certain possibility or course of action is discouraged but not prohibited.

"May" and "need not" indicate a course of action permissible within the limits of the standard. "Can" and "cannot" are used for statements of possibility and capability, whether material, physical, or causal.

Footnotes appear at various points in this specification to elaborate and further clarify items discussed in the body of the specification.

S* Unless indicated otherwise, this document presents numbers in decimal form.

Binary numbers are distinguished in the text by the use of single quotation marks. In some tables, IND 5 binary values may appear without single quotation marks if the table notation clearly specifies that values are binary. The character is used to represent a binary bit of unspecified value. For example 'xxx00010' represents any 8-bit binary value such that the least significant five bits equal S'00010'.

Hexadecimal numbers (base 16) are distinguished in the text by use of the form Oxh...h where h...h represents a string of hexadecimal digits. For example, Ox2fal represents a number whose binary value is '10111110100001' and whose decimal value is 12193. Note that the exact number of bits in the binary representation of a hexadecimal number strictly depends on the implementation requirements for the variable being represented.

SThe following conventions apply to mathematical expressions in this standard: LxJ indicates the largest integer less than or equal to x: 1l.lJ 1, 1.0J 1.

[x indicates the smallest integer greater than or equal to x: r1.l1 2, [2.01 2.

ROUND(x) indicates the integer that is closest to x: ROUND(1.2) 1, ROUND(1.9) 2.

lxl indicates the absolute value of x: 1-171=17,1171=17.

min(x, y) indicates the minimum of x and y.

max(x, y) indicates the maximum ofx and y.

In figures, x indicates multiplication. In formulas within the text, multiplication is implicit. For example, if h(n) and pL(n) are functions, then h(n) pL(n) h(n) x pL(n).

x mod y indicates the remainder after dividing x by y: x mod y x (y Lx/yJ).

x e a, b, c indicates x is a member of the set comprised of elements a, b, and c.

The bracket operator, isolates individual bits of a binary value. VAR[n] refers to bit n of the binary representation of the value of the variable VAR, such that VAR[0] is the least significant bit of VAR. The value of VAR[n] is either 0 or 1.

x y indicates that x is approximately equal to y.

The following conventions apply to expressions in the pseudo code in this standard: x y represents the bit-wise AND operation between the binary representation of x andy: 31& 4 4 '00100'.

x A y represents the bit-wise exclusive OR operation between the binary representation Sof x and y: 31 A 4 27 '11011'.

O o x k represents the bit-wise right shift of x by k bits with the vacated positions at the O left filled with bits: 61>> 3 7 '000111'.

x k represents the bit-wise left shift of x by k bits with vacated positions at the right filled with bits: 4 3 32 '100000'.

represents an increment operator: increments the value of x by 1.

The symbols and are used to enclose comments.

This document applies only to base stations with P_REV equal to or greater than 6, and to mobile stations with MOB_P_REV equal to or greater than 6 and.

This document supports systems operating in MC-MAP mode.

REFERENCES

The following standards contain provisions which, through reference in this text, constitute provisions of this Standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this Standard are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below.

-Standards: 1. Reserved.

1 2. TIA/EIA/IS-2000.2-A, Physical Layer Standardfor cdma2000 Spread Spectrum Systems.

3. TIA/EIA/IS-2000.3-A, Medium Access Control Standard for cdma2000 Spread Spectrum Systems.

4. Reserved.

2 TIA/EIA/IS-2000.5-A, Upper Layer (Layer 3) Signaling Standardfor cdma2000 Spread Spectrum Systems.

6. TIA/ELA/IS-833, Multi-Carrier Specificationfor Spread Spectrum on GSM MAP (MC-MAP).

I Reserved for future use.

SGeneral STerms

O

Base Station A fixed station used for communicating with mobile stations. Depending on the context, the term base station may refer to a cell, a sector within a cell, or another part of the wireless system.

C Blank-and-burst. The preemption of the traffic in an entire traffic channel frame by another form of ,traffic, typically signaling.

Data Block. The unit of data exchanged between the multiplex sublayer and the TDSO.

Dim-and-burst A frame in which primary traffic is multiplexed with secondary, signaling, or secondary and signaling traffic.

ESCAM. Extended Supplemental Channel Assignment Message (see FER. Frame Error Rate.

Forward Dedicated Control Channel. A portion of a Radio Configuration 3 through 9 Forward Traffic Channel.

Forward Fundamental Channel. A portion of a Forward Traffic Channel.

Forward Supplemental Channel. A portion of a Radio Configuration 3 through 9 Forward Traffic Channel, which operates in conjunction with a Forward Fundamental Channel or Forward Dedicated Control Channel in that Forward Traffic Channel to provide higher data rate services.

Forward Traffic channel. One or more forward CDMA channels used to transport user and signaling traffic from the base station to the mobile station (see Forward Fundamental Channel, Forward Dedicated Control Channel, and Forward Supplemental Channel).

Frame. A basic timing interval in the system. For the traffic channel, a frame is 5 ms, 20 ms, 40 ms, or ms long.

FSCAMM. Forward Supplemental Channel Assignment Mini Message (see Fundamental Channel. A portion of a traffic channel, which includes a Forward Fundamental Channel and a Reverse Fundamental Channel.

Fundicated Frame. A TDSO frame carried in a fundicated data block.

Fundicated Channel. Fundamental Channel or a Dedicated Control Channel.

Fundicated Data Block. A data block carried on a Fundamental Channel or a Dedicated Control Channel.

Mobile Station A station that communicates with the base station.

Multiplex Format Indicator. A number that specifies the format of a MuxPDU (see 3].

2 Reserved for future use.

39 O Multiplex Option. The ability of the multiplex sublayer and lower layers to be tailored to provide special capabilities. A multiplex option defines such characteristics as the frame format and rate decision rules S(see also Multiplex Sublayer).

O Multiplex Sublayer. One of the conceptual layers of the system that multiplexes and demultiplexes IN 5 primary traffic, secondary traffic, and signaling traffic (see MuxPDU Type 1 Category. The category of the received MuxPDU type 1 as defined in MuxPDU Type 2 Category. The category of the received MuxPDU type 2 as defined in )MuxPDU Type 3 Category. The category of the received MuxPDU type 3 as defined in MuxPDU Type 5 Category. The category of the received MuxPDU type 5 as defined in PER. PDU Error Rate.

Primary Traffic. Data bits from a service that has the traffic type in the Service Configuration Record set to Primary.

Radio Configuration A set of Forward Traffic Channel and Reverse Traffic Channel transmission formats that are characterized by physical layer parameters such as transmission rates, modulation characteristics, and spreading rate.

Reverse Dedicated Control Channel. A portion of a Radio Configuration 3 through 6 Reverse Traffic Channel.

Reverse Fundamental Channel. A portion of a Reverse Traffic Channel.

Reverse Supplemental Channel. A portion of a Radio Configuration 3 through 6 Reverse Traffic Channel, which operates in conjunction with a Reverse Fundamental Channel or Reverse Dedicated Control Channel in that Reverse Traffic Channel to provide higher data rate services.

Reverse Traffic channel. One or more reverse CDMA channels on which data and signaling are transmitted from a mobile station to a base station (see Reverse Dedicated Control Channel, Reverse Fundamental Channel, and Reverse Supplemental Channel).

RSCAMM. Reverse Supplemental Channel Assignment Mini Message (see SCRM. Supplemental Channel Request Message (see SCRMM. Supplemental Channel Request Mini Message (see Secondary Traffic. Data bits from a service that has the traffic type in the Service Configuration Record set to Secondary.

Service Option. A service capability of the system. Service options may be applications such as voice, data, or facsimile etc.

Service Option Connection. A particular instance or session in which the service defined by a service option is used.

Signaling Traffic. Control messages that are carried between mobile station and the base station on the Traffic Channel.

System Time. The time reference used by the system. System Time is synchronous to Universal Coordinate Time (except for leap seconds) and uses the same time origin as GPS time. Al base stations use the same System Time (within a small margin of error). Mobile stations use the same System Time, offset by the propagation delay from the base station to the mobile station.

TDSO. Test Data Service Option.

Traffic Channel. One or more CDMA channels on which data and signaling are transmitted between a mobile station and base station (see Forward Traffic Channel and Reverse Traffic Channel).

UHDM. Universal HandoffDirection Message (see Notation The TDSO uses the notation as listed in Table 7.

Table 7. Summary of test data service option notation Parameter Section Name/Description B(n) 0 Actual circular buffer size FRNG 0 State of the Forward Traffic Channel pseudo-random number generator NUMRAND 0 Number of pseudo-random number generations per frame to generate information bits in a data block or data blocks R(n) 0 Needed circular buffer size RRNG 0 State of the Reverse Traffic Channel pseudo-random number generator xn 0 Pseudo-random number generated by the linear congruential generator yn 0 A 24-bit pseudo-random number used for the generation of circular buffer information bits y E 0 A number derived from yn(k) after storing it in little endian order On 0 A 6-bit pseudo-random number used for determining the next byte offset in the circular buffer No text.

STest Data Service Option

O

Overview

ID

The following are the requirements of the cdma2000 Test Data Service Option: Connects the Service Option at the Multiplex Sublayer.

Supports both forward and reverse links (asymmetric and symmetric).

Does bit-wise comparison of the received frame with the locally generated/expected frame to Sdetect the undetected bit errors that are not detected by frame quality bits.

Maintains separate sets of error statistics for the FCH/DCCH and SCH(s) and responds with this Ci 10 information when queried by the base station.

Defines a single service option, and sets up different RCs and service configurations on the two links through service negotiation.

May include simultaneous primary and secondary traffic (for example, can run Markov service [SO 54] on the Fundamental Channel and TDSO on the Supplemental Channel).

Can be carried by all RC combinations on the reverse/forward links as defined under cdma2000.

Requires separate channel IDs to differentiate between the FCH, DCCH, and Supplemental Channel(s).

Is able to handle multiframe interleaving over 40 ms and 80 ms intervals in the physical layer.

Does not preclude a future extension to support flexible/variable rate.

Allows two types of ON/OFF traffic models to be selectable: Deterministic frame activity given by TX_ON and TX_OFF Random frame activity with average frame activity D and average burst length B, in units of Physical Layer frames Supports two source types of bits for frame generation: Selectable byte pattern Pseudo-random bits Supports 5 ms FCH/DCCH frames testing using Layer 3 Signaling mini messages General description TDSO provides for the generation of an arbitrary (preselected or random) data source for transport over forward and reverse traffic channels while following San arbitrary (preselected or random) transmission frame activity. The test is C N performed at a fixed data rate.

o The mobile station and the base station generate TDSO data frames for the Sconfigured and allocated traffic channels. The content of each frame is generated per a selectable byte pattern or by employing a hybrid approach consisting of pseudo-randomly generated data together with a circular buffer.

C The frame generation processes are synchronized between the mobile station and the base station. This permits the receiving station to reproduce the transmitted frames and compare them to the received frames. The TDSO counts the number of various frame types that were transmitted on a particular traffic Schannel. The TDSO also counts the number of various frame types received on the traffic channel according to the information provided by the multiplex sublayer and the result of the comparison between the frame received and the locally generated replica. Frame error and bit error statistics can be calculated from these counts.

The TDSO allows system signaling to take precedence. Dim-and-burst frames and blank-and-burst frames are excluded from FER or bit error rate calculations. Because the receiver cannot predict when the transmitter transmits a dim-and-burst or blank-and-burst frame, the receiver may categorize a frame as dim-and-burst or blank-and-burst when it is not (false alarm), or categorize a frame as not dim-and-burst or blank-and-burst when it is (miss). Therefore, the frame error statistics calculated by using only frame counts recorded in the receiver may not be exact. However, the error is very small and can usually be ignored.

Service option number The TDSO described by this standard shall use service option number 32.

Required multiplex option support The TDSO shall transmit and receive traffic channel frames in accordance with the requirements of the multiplex option or multiplex options configured for the service option.

Multiplex option support for FCHIDCCH (for 20 ms FCH/DCCH frames only) On the FCH/DCCH physical channels, the TDSO shall support an interface with the multiplex options indicated in Table 8.

Table 8 Multiplex option support for FCH or DCCH Multiplex Option Forward RC 1, 3, 4, 6, or 7 Forward RC 5, 8, or 9 Reverse RC 1, 3, or 5 Reverse RC 4, or 6 FCMITCCH jx 0x When Multiplex Option Ox01 is used, MuxPDU Type 1 is used (see Ofor interface to multiplex option).

When Multiplex Option 0x02 is used, MuxPDU Type 2 is used (see Ofor interface to multiplex option) Multiplex option support for SCH On the SCH(s) physical channel(s), the TDSO shall support an interface with the multiplex options as indicated in Table 9.

Table 9 Multiplex options applicable to an SCH Multiplex option Maimum number of MuxPDUs in the physical Forward RC 3, 4,6, or 7 Forward RC 5, 8, or 9 layer SDU ReverseRC 3or 5 Reverse RC= 4or 6 Rate Mux:PDU MnxPDU Type 3 MuPU MuxPDU Type 3 MxPU MuxPDU Type 3 Type 1 orTyeI- yp2 2 Single Double Single Double Tinge 2obl 1 x I 0x03 0x04 2x 2 1 0x809 OX905 Ox8Oa 0x906 4x 4 2 0x811 0x909 0x812 Ox9Oa 8x 8 4 0x821 0X911 0x822 OX912 16x 8 0x921 0x922 The SCH rate is expressed in multiples of a base rate. For example, odd multiplex options have the base rate 9600 bps, a 2x SCH rate means twice of O 9600 bps or 19200 bps. For Supplemental Channel rates lower than or equal to C 16x, MuxPDU Type 1, 2 or 3 that is associated with the multiplex option as 9 shown in Table 9 will be used. For Supplemental Channel rates higher than 16x, the TDSO shall use MuxPDU Type 5, which is associated with the Multiplex Option The number of data blocks (either carried by MuxPDU Type 1, 2, or 3) in every c SCH frame is shown in Table 9 for different multiplex options. For SCH rates c higher than 16x, there is exactly one data block (carried by MuxPDU Type 5) in N, every SCH frame (see (see Ofor interface to multiplex options) Interface to multiplex options TDSO frames can be carried as primary or secondary traffic.

A TDSO frame supplied to the multiplex sublayer as a fundicated data block (a data block carried on an FCH or DCCH) is called a Fundicated TDSO frame.

Similarly, a TDSO frame supplied to the multiplex sublayer to be carried as a supplemental data block or data blocks (data block(s) carried on an SCHO or SCH1) is referred to as a Supplemental TDSO frame.

Primary traffic Normally, each TDSO frame supplied to the multiplex sublayer shall be one of the Rate 1, Rate 2, or Blank (zero bits) frame types shown in Table 10.Table The number of bits per data block supplied to the multiplex sublayer for each type of TDSO frame is shown in Table 10. The maximum number of MuxPDUs (or data blocks) that can be carried in an SCH TDSO frame is also shown in Table 9.

On command, the TDSO shall supply a Blank frame. A Blank frame contains no bits. Also on command, the TDSO shall supply a non-blank Fundicated TDSO frame of x bits when the multiplex sublayer requests for an x-bit data block.

The first x bits of the generated Fundicated TDSO frame shall be supplied to the multiplex sublayer.

Table 10 Primary traffic types supplied by the TDSO to the multiplex sublayer Odd-numbered Even-numbered Can be supplied Can be supplied as TDSO multiplex option multiplex option as a Fundicated a Supplemental frame type (bits per data (bits per data TDSO frame TDSO frame block) block) Rate 3' N/A Variable No Yes Rate 2 346 538 No Yes' 171 266 Yes Yes 3 Rate 1 170 266 No Yes 4 Blank 0 0 Yes Yes 'Applicable only to multiplex option Oxf20. Used when the TDSO supplies more than 4584 bits to the multiplex sublayer during a frame interval (20, 40, or 80 ms).

2 Applicable only to multiplex options 0x905, 0x906, 0x909, Ox90a, 0x911, 0x912, 0x921, and 0x922.

3 Applicable only to multiplex options 0x3 and 0x4.

4 Applicable only to multiplex options 0x0809, Ox80a, 0x811, 0x812, 0x821, and 0x822.

The multiplex sublayer in the mobile station categorizes every received MuxPDU(s) in the Traffic Channel frame and supplies the MuxPDU category and accompanying bits, if any, to TDSO. When the multiplex format indicator is supplied by the mux sublayer, the value of the multiplex format indicator shall be used as the MuxPDU category. Table 11 lists the categories (and corresponding TDSO frame types) supplied by the multiplex sublayer when TDSO is carried as primary traffic.

Table 11. Primary traffic frame types supplied by the multiplex layer to

TDSO

Odd-numbered multiplex options Even-numbered multiplex options

TDSO

Categories Categories Categories frame Bits per Bits per Categories for for for for type data data supplemental fundicated supplemental fundicated block block MuxPDU MuxPDU MuxPDU MuxPDU Rate 3 N/A N/A N/A Variable N/A 2 Rate 2 346 N/A 5 538 N/A 171 1 1 266 1 1 Rate 1 170 N/A 4 266 N/A 4 Blank 0 5,14 2 0 5,9,14,17, 2 21,23,25 Null 0 15 N/A 0 27 N/A Secondary traffic Normally, each TDSO frame supplied to the multiplex sublayer shall be one of the Rate 1, Rate 2, Rate 3, or Blank frame types shown in. The number of bits per data block supplied to the multiplex sublayer for each type of TDSO frame shall also be as shown in Table 12. The maximum number of MuxPDUs that can be carried in a SCH TDSO frame is also shown in Table 9.

On command, TDSO shall generate a Blank TDSO frame. A Blank TDSO frame contains no bits. Also on command, TDSO shall supply a non-blank Fundicated TDSO frame of x bits when the multiplex sublayer requests for an x-bit data block. The first x bits of the generated Fundicated TDSO frame shall be supplied as a data block to the multiplex sublayer.

Table 12 Secondary traffic frames supplied by TDSO to the multiplex sublayer Odd-numbered Can be supplied Even-numbered Can be supplied TDSO frame multiplex option as a multiplex option as a Fundicated type (bits per data Supplemental (bits per data block) TDSO frame block) TDSO frame Rate 3' N/A Variable No Yes Rate 2 346 538 No Yes 2 168 262 Yes Yes 3 Rate 1 170 266 No Yes 4 Blank 0 0 Yes Yes 'Applicable only to Multiplex Option Oxf20. Used when TDSO supplies more than 4584 bits to the multiplex sublayer during a frame interface (20, 40, or 80 ms).

2 Applicable only to Multiplex Options 0x905, 0x906, 0x909, Ox90a, 0x911, 0x912, 0x921, and 0x922.

3 Applicable only to Multiplex Options 0x3 and 0x4.

4 Applicable only to Multiplex Options 0x809, Ox80a, 0x811, 0x812, 0x821, and 0x822.

The multiplex sublayer in the mobile station categorizes every MuxPDU in the received Traffic Channel frame and supplies the MuxPDU category and accompanying bits, if any, to TDSO. When the multiplex format indicator is supplied by the mux sublayer, the value of the multiplex format indicator shall be used as the MuxPDU category. Table 13 lists the categories (and corresponding TDSO frame types) supplied by the multiplex sublayer when the TDSO is carried as secondary traffic.

Table 13. Secondary traffic frames supplied by multiplex sublayer to the

TDSO

Odd-numbered multiplex options Even-numbered multiplex options

TDSO

Categories Categories frame Bits per Categories for Categories for Bits per for for type data fundicated supplemental data block fundicated supplemental block MuxPDU frames MuxPDU MuxPDU Rate 3 N/A N/A N/A Variable N/A 2 Rate 2 346 N/A 5 538 N/A Ratel 168 14 2 262 9 2 170 N/A 4 266 N/A 4 Blank 0 1-8 1 0 1-5,11-14, 1 19-21, 24 Null 0 15 N/A 0 27 N/A TDSO frame transmission and reception When primary or secondary traffic is carried on SCH(s) and/or FCH/DCCH, the content of each frame is generated in one of two ways, as negotiated between the two ends. The test stream can consist of a selectable repeated byte pattern (by default set to all or a pseudo-randomly generated data stream from a circular buffer. The two ends are synchronized to the content of test data transmitted (expected) in a particular frame. This permits the receiving station to reproduce the transmitted frames and compare them to the received frames.

When a pseudo-random data stream is used, data blocks for all frames are generated by copying the bits from the circular buffer to the data blocks, starting at a random offset for each TDSO frame. The random offset is synchronized between the mobile station and the base station.

The TDSO counts the number of various frame types received on the FCH/DCCH and/or SCH separately according to the MuxPDU category information provided by the multiplex sublayer and the result of the comparison between the frames received and the locally generated replica. FER arnd PER characteristics can be calculated from these counts for each physical N7 channel.

U There can be instances of transmission power headroom running out in either C0 the base station or mobile station (causing the transmitter to not transmit on a given traffic channel for a particular frame), which leads to the physical layer reporting an erasure at the receiver. iFor the TDSO, no special mechanism is used to account for the inaccuracies that can occur in the FER (PER) calculation due to this. No transmission by the physical channel is considered to be a ci channel and/or implementation limitation.

Transmitted frames CI If configured to -operate over Fundicated Channels (ECH or DCCII) that use mns frames, if the frame activity is the service option shall supply exactly one Fundicated data block to the multiplex sublayer every 20 nms. The data block contains a header (channel ID and PIDU sequence number) followed by the service option information bits.

Unless otherwise commanded, the service option shall supply a Rate 1 or blank data block as listed in Table 10 and Table 12 when carrying primary or secondary traffic, respectively. On command, the service option shall supply a blank data block. Also on command, the service option shall supply a data block with the number of bits that the multiplex sublayer requests, by truncating the generated data block if necessary.

If configured to operate over Supplemental Channels (SCHO and/or SCHi), if the frame activity is the service option shall supply one or N data blocks to the multiplex sublayer for each Supplemental Channel every frame interval (20 ins, 40 mns, or 80 ins), where N is the maximum number of data blocks (or MuxPDUs) in a physical layer SDU for a connected multiplex option, as shown in Table 9. The data blocks contain a header (channel ID and PDU sequence number) followed by the service option information bits.

Unless otherwise commanded, the service option shall supply Rate 1, Rate 2, Rate 3, or Blank Supplemental frames, as listed in Table 10 and Table 12, when carrying primary or secondary traffic, respectively. A single data block is passed to the multiplex sublayer for the SCH when the connected multiplex option is Oxf2O.

O Received frames

C

1 The multiplex sublayer in the receiving station categorizes every received O MuxPDU(s) in the fundicated and supplemental frame (see and supplies the MuxPDU type and accompanying bits, if any, to the TDSO. The MusPDU types that are supplied are indicated in Table 10 and Table 12 for primary and secondary traffic operations, respectively.

Interface to Layer 3 Signaling when testing 5 ms FCH/DCCH frames When testing 5 ms FCH/DCCH frames, TDSO generates requests to Layer 3 Signaling to send mini messages as opposed to sending TDSO frames as described in the 20 ms frame length case. The same frame activity model will be Cl used for each 5 ms frame to determine whether to request Layer 3 Signaling to send a mini message or not during that frame. Since TDSO has no control of timing in Layer 3 Signaling, the mini message may actually be transmitted at a later 5 ms frame.

To test the Forward 5 ms FCH/DCCH frames, the TDSO in the base station shall request Layer 3 Signaling to transmit Forward Supplemental Channel Assignment Mini Message (FSCAMM), according to the frame activity. The base station shall fill the FSCAMM in accordance with 0. The-base station should count the number of 5 ms frames transmitted, which includes all the transmitted and retransmitted 5 ms Layer 3 Signaling messages. The mobile station keeps a reception counter (see of the number of good 5 ms frames received MUX1_FOR_FCH_5_ms when Multiplex Option 0x01 is used on a Forward Fundamental Channel).

To test the Reverse 5 ms FCH/DCCH frames, the TDSO in the mobile station shall request Layer 3 Signaling to transmit Supplemental Channel Request Mini Messages (SCRMM), according to the frame activity. The mobile station shall fill the SCRMMREQBLOB in the SCRMM in accordance with 0. The base station should count the number of good 5 ms frames received, which includes all the good transmitted and retransmitted 5 ms Layer 3 Signaling messages. The mobile station keeps a transmission counter (see of the number of 5 ms frames transmitted MUX1_REV_FCH_5_ms when Multiplex Option 0x01 is used on a Reverse Fundamental Channel).

No text.

51 0 TDSO Procedures and Description SNegotiation and activation of service option O The mobile stations and base stations that conform to cdma2000 are required to support service configuration and negotiation as described in Mobile station requirements C The TDSO shall be negotiated and connected using the service configuration and negotiation procedures defined in For the TDSO, the mobile station C shall not propose a service configuration whose attributes are inconsistent with the valid service configuration attribute for the service option. For a mobile station operating in MC-41 mode, the mobile station shall indicate the preferred Forward RC and Reverse RC in the FOR_RC_PREF field and the REV_RC_PREF field, respectively, in the Page Response Message and Origination Message. For a mobile station operating in MC-MAP mode (see the mobile station shall indicate the preferred Forward RC and Reverse RC in the FOR_RC_PREF field and the REV_RC_PREF field, respectively, in the MC-MAP RRC Connection Request Message. When proposing the TDSO, the mobile station shall not accept a service configuration whose attributes are inconsistent with the valid service configuration attributes for the service option as listed in Table 14. The default service configuration for the TDSO shall be as shown in the valid service configuration detailed in Table 14.

Table 14 Valid service configuration attributes for test data service option Service configuration attribute Valid selections' Forward Multiplex Option 0x01 2 or 0x02 3 Reverse Multiplex Option 0x01 4 or 0x02 Forward Transmission Rates For the FCH, Rates 1, 1/2, 1/4, and 1/8 enabled.

For the DCCH, Rate 1 enabled, Rates 1/2, 1/4, and 1/8 not enabled.

Reverse Transmission Rates For the FCH, Rates 1, 1/2, 1/4, and 1/8 enabled.

For the DCCH, Rate 1 enabled, Rates 1/2, 1/4, and 1/8 not enabled.

Forward Traffic Type Primary" or Secondary Traffic Reverse Traffic Type Should be identical to the Forward Traffic Type Forward FCH Radio Configuration RC 1, 2,3, 4, 5, 6, 7, 8, or 9 Reverse FCH Radio Configuration RC 1, 2, 3,4, 5, or 6 Forward DCCH Radio Configuration RC 3, 4, 5, 6, 7, 8, or 9 Reverse DCCH Radio Configuration RC 3, 4,5, or 6 Forward SCH Radio Configuration RC 3, 4, 5, 6, 7, 8, or 9 Reverse SCH Radio Configuration RC 3,4,5 or 6 Forward SCH Frame Size 20 ms, 40 ms, or 80 ms Reverse SCH Frame Size 20 ms, 40 ms, or 80 ms Forward Supplemental Channel Multiplex 0x921, 0x911, 0x909, 0x905, 0x821, 0x811, Option 0x809, 0x03 0x922, 0x912, Ox90a, 0x906, 0x822, 0x812, 0x04 0xf20 Reverse Supplemental Channel Multiplex 0x921, 0x911, 0x909, 0x905, 0x821, 0x811, Option 0x809, 0x03 0x922, 0x912, Ox90a, 0x906, 0x822, 0x812, 0x04 See for a description of the selections.

2 Applies when Forward RC is 1, 3, 4, 6 or 7.

3Applies when Forward RC is 2, 5, 8 or 9.

4 Applies when Reverse RC is 1, 3 or 'Applies when Reverse RC is 2, 4 or 6.

6 Selections in bold represent the default configurations for the TDSO.

If the mobile station originates or accepts a TDSO call, then the mobile station shall perform the following: O If the TDSO call is mobile station terminated, then the mobile station shall initiate an auto- N answer before entering the Waiting for Mobile Station Answer subsate.

3 The mobile station shall connect the TDSO at the action time specified in the Service Connect Message, the General Handoff Direction Message, or the Universal Handoff Direction Message containing the TDSO service option connection, and shall initialize the service option as specified in Section Oin this document. While the service option is connected, the TDSO shall process the received frames as specified in Oand generate and supply frames for transmission as 10 specified in 0.

SSupplemental channel allocation The mobile station may request high-speed operation on the Supplemental Channel(s) by sending one of the following messages to the BSC/MSC at an implementation-defined time: Supplemental Channel Request Message (SCRM) Supplemental Channel Request Mini Message (SCRMM) If a Supplemental Channel Request Message is used, the mobile station shall: Assemble the SCRM_REQBLOB (see Table Set the DURATION field in the SCRM REQ.BLOB to '1111' Include the SCRM_REQBLOB in the REQLBLOB field in the Supplemental Channel Request Message Set the SIZEOF_REQBLOB field in the Supplemental Channel Request Message to the number of octets in the SCRM_REQBLOB If a Supplemental Channel Request Mini Message is used, the mobile station shall: Assemble the SCRMMREQ_BLOB (see Table 16) and include it in the REQBLOB field in the Supplemental Channel Request Mini Message Set the DURATION field in the SCRMMREQBLOB to '1111' Include the SCRMMREQ.BLOB in the REQ.BLOB field in the Supplemental Channel Request Mini Message 3 For the purposes of this standard, the term "auto-answer" shall have the following meaning: While in the Waitingfor Mobile Station Answer Substate of the Mobile Station Control on the Traffic Channel State, the mobile station shall automatically send a Connect Order to the base station as a 1^ o After the mobile station sends the Supplemental Channel Request Message or N1 Supplemental Channel Request Mini Message, the BS may respond with an 0 allocation message (ESCAM, RSCAMM, or UHDM). The mobile station shall

O

0 not repeat the request sooner than one second after the request was sent. If the mobile station receives an UHDM, ESCAM, FSCAMM, or RSCAMM that changes the transmission rates available to the mobile station on the

C

c Supplemental Channel, the mobile station shall: At the start time indicated by the FOR_SCH_START_TIME or REVSCH_START_TIME fields, reinitialize the TDSO to supply one or more data blocks at the new rate, filled with all 1 bits with a 100% frame activity (that is, continuously) to the multiplex sublayer for the SCH(s) until Sthe next synchronization frame (see Ofor description of synchronization frame).

At the synchronization frame time, the TDSO shall: Reset all counters associated with the involved Supplemental Channels.

Commence using the same test parameters for the channel that was used before the rate change took effect If the mobile station receives a UHDM, a ESCAM, a RSCAMM, or a FSCAMM that deallocates the current Supplemental Channel(s): The mobile station shall continue transmitting the TDSO traffic over the Fundicated Channels without any reinitialization.

The mobile station may request high-speed operation on the Supplemental Channel(s) by sending a Supplemental Channel Request Message or, if permitted by the base station, a Supplemental Channel Request Mini Message to the BSC/MSC at an implementation-defined time.

SCRM_REQBLOB format Table 15 SCRM_REQBLOB format Length Field Length Definition (bits) DURATIONUNIT 3 The mobile station shall set this field to one less than the number of ms intervals in a single duration period.

NUM_REQ 3 The mobile station shall set this field to the number of service request records in the SCRM_REQ_BLOB.

message requiring acknowledgment without waiting for the user to explicitly command the call to be answered. The mobile station shall enter the Conversation Substate.

Length Field Definition (bits) RESERVED 2 The mobile station shall set this field to '00'.

Followed by NUMREQ occurrences of the following service request record: SR_ID 3 The mobile station shall set this field to the service reference identifier associated with the service option.

PREFERRED_RAT 4 The mobile station shall set this field to the Reverse Supplemental E Channel Rate (according to Table 17) that it prefers to use for this reverse high-speed operation for this service option.

DURATION 9 The mobile station shall set this field to the number of duration periods that the mobile station requires reverse high-speed operation for this service option. A value of '111111111' indicates a request for an infinite duration.

SCRMMREQBLOB format Table 16 SCRMM_REQ_BLOB format Length Field Definition (bits) SRID 3 The mobile station shall set this field to the service reference identifier associated with this service option.

PREFERRED_RATE 4 The mobile station shall set this field to the Reverse Supplemental Channel Rate (according Table 17) that it prefers to use for this reverse high-speed operation for this service option.

DURATION 4 The mobile station shall set this field to the number of 20 ms intervals (according Table 18) that the mobile station requires reverse high-speed operation at the PREFERREDRATE for this service option.

RESERVED 5 The mobile station shall set this field to '00000'.

Table 17 Encoding of the PREFERRED_RATE field Requested reverse supplemental Requested reverse PREFERREDRATE field channel rate (kbps) for RC supplemental channel rate value (binary) using Nx9.6 (kbps) for RC using Nx14.4 '0000' 9.6 14.4 '0001' 19.2 28.8 '0010' 38.4 57.6 '0011' 76.8 115.2 '0100' 153.6 230.4 '0101' 307.2 460.8 '0110' Reserved 518.4 '0111' 614.4 1036.8 '1000'-'1111' Reserved Reserved Table 18 Encoding of the DURATION field CDMA-CDMA hard handoff scenario While in a TDSO call, if the mobile station receives a Universal Handoff Direction Message signaling a hard handoff in which the active set, frame offset, or frequency assignment changes, upon performing the hard handoff, the mobile station shall: S At the action time associated with the message, reinitialize the TDSO to supply data blocks with all 1 bits at a 100% frame activity to the multiplex sublayer for the FCH/DCCH channels .0 (depending on the channel configuration).

S If a supplemental channel assignment is included, at the start time indicated by the FOR_SCH_START_TIME or REV_SCH_START_TIME fields, reinitialize the TDSO to supply one or more data blocks at the new rate filled with all 1 bits with a 100% frame activity to the multiplex sublayer for the SCH(s).

If the TDSO call in progress is a mobile-originated call, after the hard handoff, the mobile station shall propose the test parameters that were in effect before the hard handoff to the base station in a control directive using the Service Option Control Message.

Base station requirements Cl The TDSO shall be negotiated and connected using the service configuration O and negotiation procedures defined in For the TDSO, the base station shall not propose a service configuration whose attributes are inconsistent with the

ID

valid service configuration attribute for the service option. The base station shall not accept a service configuration whose attributes are inconsistent with c the valid service configuration attributes for the service option as shown in Table 14. The base station should not propose a reverse RC that is different than C the one proposed by the mobile station.

C-"

p. 10 The BS controls both the forward and reverse high-speed operation by allocating Supplemental Channels for an infinite duration. Allocation is specified in the ESCAM, FSCAMM, RSCAMM, or UHDM.

Synchronization frame The Forward and Reverse Traffic Channels (F/R-FCH or F/R-DCCH, F/R- SCHO and F/R-SCH1) are each subdivided into independent segments of 10.24 seconds each. This corresponds to every: 2048 frames for physical channels (FCH, DCCH) with 5 ms frame length 512 frames for physical channels (FCH, DCCH or SCH) with 20 ms frame length 256 frames for Supplemental Channels with a 40 ms frame length 128 frames for a Supplemental Channel with an 80 ms frame length The first frame of a segment is called the synchronization frame. All pseudorandom number generators associated with the channel are reinitialized prior to TDSO frame processing for each synchronization frame. All service option initialization and control operations also take effect prior to TDSO frame processing for a synchronization frame for each physical channel.

Forward Traffic Channels For the Forward Traffic Channels (F-FCH, F-DCCH, F-SCHO, and F-SCH1), the synchronization frames shall be those frames for which the least significant nine bits of the System Time in frames (as defined in are equal to the least significant nine bits of the bit-wise exclusive-OR of the least significant 32-bits Public Long Code Mask (PLCM 32) of the mobile station and the value Ox2aaaaaaa.

O Forward Supplemental Channels CI For 40 ms and 80 ms frame length operation on the Forward Supplemental 0 Channels, however, the synchronization frame time as calculated for the

O

Forward Traffic Channels above may not coincide with the beginning of the frame period for these channels. In that case, the circular buffer shall still be generated using the same generator as for other forward channels

C

c (F-FCH/DCCH) for the 20 ms frame length. However, the beginning of the next frame period on the Forward Supplemental Channel that is closest in time to CI the frame as calculated above for Forward Traffic Channels shall be treated as 10 the first frame of the next 10.24-second test segment for the Forward 0Supplemental Channel.

Reverse Traffic Channels For the Reverse Traffic Channels (R-FCH, R-DCCH, R-SCHO, and R-SCH1), the synchronization frames shall be those frames for which the least significant nine bits of the System Time in frames (as defined in are equal to the least significant nine bits of the bit-wise exclusive-OR of the least significant 32-bits Public Long Code Mask (PLCM_32) of the mobile station and the value 0x15555555.

Reverse Supplemental Channels For 40 ms and 80 ms frame length operation on the Reverse Supplemental Channels, however, the synchronization frame time as calculated for the Reverse Traffic Channels above may not coincide with the beginning of the frame period for these channels. In that case, the circular buffer shall still be generated using the same generator as for other reverse channels (R-FCH/DCCH) for the 20 ms frame length. However, the beginning of the next frame period on the Reverse Supplemental Channel closest in time to the frame as calculated above for Reverse Traffic Channels shall be treated as the first frame of the next 10.24-second test segment for the Reverse Supplemental Channel.

Counters The mobile station and the base station shall support the transmit counters listed in Table 19 and Table 20 for the Fundicated and Supplemental Channels, respectively.

O

O

O-

©0 Table 19 Transmit frame counters on the fundicated channel Generated frame Transmitted frame type Counter name type Rate 1 Rate 1 with no signaling TDSO_EI_T1 Rate 1 Rate 1 with dim-and-burst signaling TDSO_EI_TD Rate 1 Rate 1 with blank-and-burst signaling TDSO_EITB Blank Blank TDSO_EB_TB Blank Anything other than blank TDSO_EB_TO Table 20 Transmitted frame counters on the Supplemental Channel SCH-generated frame type Transmitted frame type (kbps) Counter name (kbps) N x 9.6 or N x 14.4' N x 9.6 or N x 14.4 TDSO_ENx_TNx N x 9.6 or N x 14.4' Blank TDSOENx_TB Blank Blank TDSO_EB_TB IN can take the values 1, 2, 4, 8, 16, 18, 32, 36, 64, or 72 depending on the connected SCH transmission rate. The SCH frame consists of one or more data blocks of type Rate 1, Rate 2, or Rate 3 as determined by the connected multiplex option.

The mobile station and the base station shall support the receive counters listed in Table 21 and Table 22.

Table 21 Receive frame counters maintained for the FCH/DCCH Expected frame type Received frame type Counter name Rate 1 Error-free Rate 1 frame with no dim-and- TDSO_E1_RI burst Rate 1 Rate 1 with bit errors detected by the service TDSO_E1_RERR option Rate 1 Dim-and-burst frame TDSO_E1_RD Rate 1 Other rate frame TDSO_E1_RO Rate 1 Blank-and-burst TDSO_EILRB Expected frame type Received frame type Counter name Rate 1 Rate 1 physical layer frame with insufficient TDSO_EI_RFL physical layer frame quality' Rate 1 Insufficient frame quality (erasure) TDSO El_RE Null Null TDSOEN_RN Null Blank TDSO_EN_RB Null Other TDSOEN_RO 1 Categorized by Multiplex Option 0x01 only.

Table 22 Receive frame counters on the Supplemental Channel SCH expected frame Received frame type Counter name type N x 9.6 or N x 14.4 Error-free N x 9.6 or N x 14.4 frame TDSO_ENx RNx N x 9.6 or N x 14.4 N x 9.6 or N x 14.4 frame with bit errors TDSO_ENx_RERR detected by the service option N x 9.6 or N x 14.4 Insufficient frame quality (erasure) TDSOENx_RE N x 9.6 or N x 14.4 Blank TDSO_ENxRB Blank Blank TDSO.EBRB Blank Anything other than blank TDSO.EB.RO The mobile station shall support the counters in Table 23 for the calculation of PER on the Supplemental Channels.

Table 23 Receive PDU counters maintained for the Supplemental Channels Bit counter SCH expected rate Received MuxPDU type name 3 Error-free Rate 3 MuxPDU TDSO_E3_R3 3 Rate 3 MuxPDU with errors detected by the TDSOE3_RER TDSO R 3 Insufficient frame quality (erasure) TDSOE3_RE 2 Error-free Rate 2 MuxPDU TDSO_2_R2 2 Rate 2 MuxPDU with errors detected by the TDSOE2_RER TDSO R SCH expected rate Received MuxPDU typeBicone name 2 Insufficient frame quality (erasure) TDSQLE2JE I a, Error-free Rate la MuxPDU TDSOElaRia 1a Rate Ia MuxPDU with errors detected by the TD)SOElaRER TWSO R Ia Insufficient frame quality (erasure) TDSOElaRE lb 2 Error-free Rate lb MuxPDU TD)SO...lLRIb lb Rate lb MuxPDtJ with errors detected by the TDSOElbRER TDSO R lb Insufficient frame quality (erasure) TDSO_Elb_RE Rate Ila corresponds to the Rate 1 type MuxPDU applicable only to multiplex options 0X3- 0x4 as indicated in Table 9.

2 Rate l b corresponds to the Rate 1 type MuxPDU applicable only to multiplex options 0x809, Ox8Oa, 0x8l. 1, 0x812, 0x821, and 0x822 as indicated in Table 9.

The following buffers shall be capable of storing the frame counter values as shown in the following tables.

Table 24 Frame counter-value storage Channel Buffer Station Counter-value storage type' R-C FHBFEMobile Transmit R Base Receive R-CH RCHBFMobile Transmit FER Base Receive FFCH FFCILBUFFE Mobile Transmit R Base Receive F-DCCH FDCCHBUTFF Mobile Transmit ER Base Receive 'For more information on transmit frame counter values, refer information on receive frame counter values, refer to Table 21.

to Table 19. For more Table 25 Frame counter-value storage for Supplemental Channels Channel Buffer Station Counter-value storage type* R-SCHO RSCHO_BUFFE Mobie Transmit R Base Receive R-SCH1 RSCHLBUFFE Mobile Transmit R Base Receive F-SCHO FSCHO_BUFFER Mobile Transmit Base Receive F-SCH1 FSCHLBUFFER Mobile Transmit Base Receive *For more information on transmit and receive frame counter values, refer to Table 20. For more information on receive bit counter values, refer to Table 23.

Mobile station initialization and control operation Service option initialization If a TDSO initialization is required as a result of a signaling message on f-dsch, the mobile station shall consider the System Time in frames coinciding with the action time of the message (as defined in to be the effective initialization frame, EFF_FRAME.

For the Forward and Reverse Fundicated Traffic Channels (F/R-DCCH and/or F/R-FCH), the TDSO shall consider the System Time in frames that coincide with the action time of the Service Connect Message as the initialization frame.

For the Forward and Reverse Supplemental Channels (F/R-SCHO and/or F/R- SCH1), the TDSO shall consider the System time in frames coinciding with the start time indicated by the FORSCHSTARTTIME (for Forward Supplemental Channels) or REV_SCH_STARTTIME (for Reverse Supplemental Channels) fields inside of the ESCAM, FSCAMM, RSCAMM, or UHDM that is the initialization frame.

The initialization frame may coincide with the synchronization frame on a physical channel. Until the first synchronization on a channel is achieved, the TDSO shall only use the default settings for the test parameters, that is, an all 63 r- 1's data pattern with a continuous transmission every frame period (20 ms, CN 40 ms, or 80 ms) on that channel.

0 To perform TDSO initialization, the mobile station shall perform the following 0 operations: Immediately prior to TDSO frame processing for the Reverse Traffic Channel (that is, R-FCH/R-DCCH/R-SCHO/R-SCH1) synchronization frame for which the System Time in C frames falls in the range from EFF_FRAME to EFF FRAME FRAMES_PER_SEGMENT_1

S

inclusive, the mobile station shall set the counters associated with the Reverse Traffic Channels Sto zero.

cI 10 For Reverse Fundicated Traffic Channels, the counters are RFCHBUFFER and

RDCCH_BUFFER

CI For Reverse Supplemental Channels, the counters areRSCHOBUFFER and RSCH1_BUFFER The value of FRAMES_PER_SEGMENT_ shall be: 511 for a 20 ms physical channel frame length 255 for a 40 ms physical channel frame length 127 for a 80 ms physical channel frame length Immediately prior to TDSO frame processing for the Forward Traffic Channel (that is, F-FCH/F-DCCH/F-SCHO/F-SCH1) synchronization frame for which the System Time in frames falls in the range from EFF_FRAME to EFF.FRAME FRAMES_PER_SEGMENT_1 inclusive, the mobile station shall set the counters associated with the Forward Traffic Channels to zero.

For Forward Fundicated Traffic Channels, the counters are FFCH_BUFFER and

FDCCHBUFFER

For Forward Supplemental Channels, the counters are FSCHO_BUFFER and

FSCHLBUFFER

The value of FRAMES_PER_SEGMENT_1 shall be: 511 for a 20 ms physical channel frame length 255 for a 40 ms physical channel frame length 127 for a 80 ms physical channel frame length O Mobile station control operations Control invocation O The mobile station can either propose or invoke service-option-specific

NO

functions for a TDSO call by sending a Service Option Control Message to the base station. When the mobile station sends the Service Option Control Message, it c shall: Send it as a message requiring acknowledgment Set the CONTROL_CODE field in the message (see Table 39) to '00000000' The mobile station can only propose values of test parameters for use during the test interval. The mobile shall be able to invoke the counter retrieval directives without any base station mediation.

Control directive When the mobile station receives a Service Option Control Message with CTL_REC_TYPE in the range 'oooo- ooo'00000100oo inclusive (corresponding to FCH, DCCH, SCHO, or SCH1 physical channels) as indicated in Table 39, the mobile station shall consider the System Time in frames coinciding with the action time of the message to be the effective operation frame or initialization frame (also known as EFFFRAME for the particular physical channel).

Reverse Traffic Channel Immediately prior to TDSO frame processing for the Reverse Traffic Channel synchronization frame for which the System Time in frames falls in the range from EFP_FRAME to EFI_FRAME 511, inclusive, the mobile station shall perform the following- If the COPY_COUNTERS field is equal to the mobile station shall copy the counters associated with the specified Reverse Traffic Channel to RFCH_BUFFER, RDCCH_BUFFER, RSCHO_BUFFER, and/or RSCH1_BUFFER as determined by the channel configuration (see Section 3.3 for more information).

If the CLEARCOUNTERS field is equal to the mobile station shall set the counters associated with the specified Reverse Traffic Channel to zero (see Section 3.3 for more information).

If the CHANNELDIRECTION field is equal to '00' or the mobile station shall perform the following: Initialize the local test variables associated with DATASOURCE to the value implied by its value in the message.

O Initialize the local test variables associated with FRAMEACTIVITY to the value implied by its value in the message.

Forward Traffic Channel Immediately prior to TDSO frame processing for the Forward Traffic Channel synchronization frame for which the System Time in frames Sfalls in the range from EFFFRAME to EFFFRAME 511, inclusive, the mobile station shall do the following: If the COPY_COUNTERS field is equal to the mobile station shall copy the counters Sassociated with the specified Forward Traffic Channel to FFCH_BUFFER, FDCCH_BUFFER, and/or FSCHIBUFFER (see Section 3.3 for more information).

If the CLEAR_COUNTERS field is equal to the mobile station shall set the counters associated with the specified Forward Traffic Channel to zero (see Section 3.3 for more information).

If the CHANNEL_DIRECTION field is equal to '00' or the mobile station shall perform the following: Initialize the local test variables associated with DATA_SOURCE to the value implied by its value in the message.

Initialize the local test variables associated with FRAME ACTIVITY to the value implied by its value in the message.

Following a mobile station test control proposal (see Section 3.5.1 for a description), if a mobile station receives a Service Option Control Message with CTL_REC_TYPE in the range 'oooooooo oo000oo0' inclusive (corresponding to FCH, DCCH, SCHO, or SCH1 physical channels) as listed in Table 38, the mobile station shall perform the following: If the CONTROLCODE field is set to '00000011', the mobile station may send another proposal with the NUM_CIRC_BUF_FRAMES field set to a value less than or equal to the value indicated in the corresponding field of the base station directive.

If the CONTROL CODE field is set to '00000110', the mobile station may send another proposal with the FRAMESOURCE field set to a value other than Counter retrieval When the mobile station receives a Service Option Control Message with CTL_REC_TYPE in the range of '00000101' '00001000' (corresponding to FCH, DCCH, SCHO, or SCH1 physical channels) as listed in Table 38, then: If the message is used to retrieve the 5 ms Transmitted Frame Counters or the 5 ms Received Frame Counters, then at the first synchronization frame boundary, the mobile station shall respond with the Service Option Control Message containing its response shown in Table 46, corresponding to the VECTCOUNTER_ID fields (see Table 47) in the received Service Option Control Message.

Otherwise, at the action time associated with the message, the mobile station shall respond with the Service Option Control Message containing its response shown in Table 46 and r-1 Table48, respectively, for the Fundicated and Supplemental Channels, corresponding to the VECT COUNTERID fields (see Table 47 and Table 49) in the received Service Option Control Message.

Base station initialization and control operations To perform TDSO initialization, if the FCH/DCCH are configured to use 5 ms frames, the base station shall send a Service Option Control Message no later than 1 second before the occurence of the first synchronization frame after EFFFRAME, in accordance with 0, to retrieve the values of the 5 ms frame counters in the mobile station MUXIFOR_FCH_5ims). Base station control operations Control invocation The base station shall use the Service Option Control Message for invoking service option specific directives. When the base station sends the Service Option Control Message, it shall send it as a message requiring acknowledgment.

When the mobile station proposes values of test parameters for use during the test interval, the base station shall decide whether or not to invoke the mobilestation-proposed test parameter settings through the Service Option Control Message.

The base station shall not send a control directive to the mobile station any later than one second before the occurrence of the synchronization frame on the channel for which the directive is intended.

Control directive c 1When the base station receives a Service Option Control Message with o CTL_RECTYPE in the range of 'ooooooo '0oooo100' inclusive (corresponding to FCH, s DCCH, SCHO, or SCH1 physical channels) as indicated in Table 38, the base station shall respond to the mobile station proposal as follows: If all of the fields in the mobile-station-proposed control directive (as indicated in Table 39) are

C¢~

Swithin the acceptable range for the base station, the base station shall issue a Control Directive

C

c including the same values for the different fields (see Table 39) as proposed by the mobile C1 station in a Service Option Control Message, while setting the CONTROL_CODE field (Table 40) in the message to a value of '00000010'.

If the base station does not have the capability of supporting the value proposed by the mobile S1 station for the NUM_CIRCBUF_FRAMES, it shall issue a Control Directive including the same values for the different fields (see Table 39) as were proposed by the mobile station, except for the NUM_CIRC_BUF_FRAMES field in a Service Option Control Message, while setting the CONTROL_CODE field (Table 40) in the message to a value of '00000011'. In the NUM_CIRC_BUFFRAMES field of the message, the base station shall indicate the maximum number of frames it can support for the circular buffer.

If the base station does not have the capability of generating one frame per frame period as requested by the mobile station through setting a value of '10' for the FRAME_SOURCE field, it shall issue a Control Directive, including the same values for the different fields (see Table 39), as proposed by the mobile station, except for the FRAMESOURCE field in a Service Option Control Message, while setting the CONTROL_CODE field (Table 40) in the message to a value of '00000110'.

If the base station is not able to recognize the fields in the mobile-proposed Control Directive, it shall issue a Control Directive including the same values for the different fields (see Table 39), as proposed by the mobile station in a Service Option Control Message, while setting the CONTROL_CODE field (Table 40) in the message to a value of '00000101'.

Counter retrieval When the base station receives a Service Option Control Message with CTL_REC_TYPE in the range of '0000011' '00001000' inclusive (corresponding to FCH, DCCH, SCHO, or SCH1 physical channels) as listed in Table 38, then at the action time associated with the message, the base station shall respond with the Service Option Control Message containing its response, as shown in Table 46 and Table48, respectively, for the Fundicated and Supplemental Channels, corresponding to the VECT_COUNTERID fields (see Table 47 and Table 49) in the received Service Option Control Message.

68 TDSO Frame processing For an FCH/DCCH that is configured to use 5 ms frames, the service option shall perform transmit frame processing for 5 ms DCCH frames exactly once for every 5 ms frame of System Time while the service option is connected on the allocated FCH/DCCH in accordance with 0.

If 20 ms frames are used, the service option shall perform transmit and receive frame processing exactly once for every 20 ms frame of System Time while the service option is connected on the allocated physical channel(s) in accordance with Oand 0, respectively.

If 40 ms (or 80 ms) SCH frames are used, the service option shall perform transmit and receive frame processing exactly once for every 40 ms (or 80 ms) frame of System Time while the service option is connected on the allocated SCH in accordance with Oand 0, respectively.

Transmit frame processing Transmit frame processing refers to F-FCH/F-DCCH/F-SCH Forward Traffic Channel frame processing in the base station or R-FCH/R-DCCH/R-SCH Reverse Traffic Channel frame processing in the mobile station. Transmit frame processing consists of the following: Generating data block(s) Supplying data block(s) to the multiplex sublayer for transmission Incrementing the corresponding counters The service option shall generate the data blocks in accordance with 3.7. For Fundicated data frames (carried over FCH or DCCH), if the multiplex sublayer has requested a Blank data block, the service option shall supply a blank data block (data block containing no bits) to the multiplex sublayer. If the multiplex sublayer has requested a non-blank x-bit data block, the service option shall supply the first x bits of the generated data block to the multiplex sublayer and discard the rest of the generated data block. Otherwise, the service option shall supply the generated data block(s) to the multiplex sublayer, every physical channel frame.

For Supplemental data frames, if the multiplex sublayer has requested a Blank data block or Blank data blocks, the service option shall supply a data block or data blocks containing zero bits to the multiplex sublayer. Otherwise, the service option shall supply the generated data block(s) to the multiplex sublayer every SCH frame.

The service option shall increment the counters that are shown in Table 26 and Table 27, corresponding to the rate of the generated Fundicated and Supplemental frames and the command received from the multiplex sublayer.

Table 26 Counters for fundicated transmitted frames Rate of generated frame Multiplex sublayer command Counter to increment 1 None TDSOEI_T1 1 Max Rate Rate 1/2 TDSO_E1_TD 1 Blank TDSO_EI_TB Blank None TDSO_EB_TB Blank Maximum Rate Rate 1/2 or Blank TDSO_EBTO Table 27 Counters for supplemental transmitted frames SCH rate of generated frame Multiplex sublayer command Counter to increment (kbps) N x 9.6 or N x 14.4' None TDSOENxTNx N x 9.6 or N x 14.4 Blank TDSO_ENx_TB Blank None TDSO.EB_TB N can take the values 1, 2, 4, 8, 16, 18, 32, 36, 64, or 72 depending on the connected SCH transmission rate. The SCH frame consists of one or more data blocks of type Rate 1, Rate 2, or Rate 3 as determined by the connected multiplex option.

Receive frame processing Receive frame processing refers to F-FCH/F-DCCH/F-SCH frame processing in the mobile station or R-FCH/R-DCCH/R-SCH frame processing in the base station. Receive frame processing consists of the following: Generating data block(s) Accepting data block(s) from the multiplex sublayer Comparing the rates and contents of the comparable data block(s) Incrementing the corresponding counters c For Fundicated Channel processing:

C.

O The service option shall generate a data block in accordance with 3.7.

IN The service option shall accept a received frame and the categorization of the MuxPDU(s) from the multiplex sublayer.

If the categorization of the received MuxPDU corresponds to the rate of the generated data C block, the service option shall compare the contents of the generated data block with the Cc) contents of the received data block, and shall determine whether or not they are identical.

The service option shall increment the counter shown in Table 28 (when MuxPDU Type 1 is used) or 71 Table 29 (when MuxPDU Type 2 is used) corresponding to the rate of the generated data block, the categorization of the received MuxPDU, and the result, if any, of the comparison of the data blocks.

Table 28 Counter updates for received fundicated frames when MuxPDU Type 1 is used Rate of Category of Category of Data block gnrtd received MuxPDU received MuxPDU coprsnCounter to genraed for primary for secondary comparison frame identical? traffic traffic 1 1 14 Y TDSEI-RI 1 1 14 N TDS0E1-RERR 1 2,3,4,11, 12, 13 11,12,13 N/A TDSO-EIRD 16,7,8 N/A N/A TDSOE1RO 1 5, 14 1-8 N/A TDSOEl_RB 1 9 9 N/A TDSO-ElRFL 1 10 10 N/A TDSOI.RE Blank 15 15 N/A TDSOEN.RN Blank 5,14 1-8 N/A TDSQ.B1'LRB Blank 1-4, 6-13 9-14 N/A TDSO-EN.R0 Table 29 Counter updates for received fundicated frames when MuxPDU Type 2 is used Category of Rate of Category of received Data block received Counter to generated MuxPDU for r d comparison C er t MuxPDU for increment frame primary traffic identical? secondary traffic 1 1 9 Y TDSO E1_RI 1 1 9 N TDSOEIRER

R

1 2-4,6-8, 10,12, 13, 6-8, 10,15, 16, N/A TDSO_E1_RD 16, 18, 20,22 18,22 1 5, 9, 14, 17,21,23, 25 1-5, 11-14, 19-21, N/A TDSO_E1 RB 24 1 26 26 N/A TDSOE1JRE 1 11,19,24 17,23,25 N/A TDSO_E1_RO Blank 27 27 N/A TDSO_EN_RN Blank 5, 9, 14, 17,21, 23, 25 1-5, 11-14, 19-21, N/A TDSOENRB 24 Blank 1-4, 6-8, 10-13, 15, 16, 6-10, 15-18, 22, N/A TDSO_EN_RO 18-20, 22, 24, 26 23, 25, 26 For Supplemental Channel processing: The service option shall generate one or more data blocks in accordance with 3.7 for every SCH frame.

o The service option shall accept one or more data blocks, along with a categorization of each MuxPDU (see from the multiplex sublayer at every SCH frame, as dictated by the connected multiplex option.

If the categorization of the received MuxPDU(s) corresponds to the rate of the corresponding generated frame, the service option shall compare the contents of the generated data block(s) with the contents of the received data block(s), and shall determine whether or not they are identical.

The service option shall increment the counter shown in Table 31 corresponding to the rate of the generated frame, the categorization of the received MuxPDU(s), and the result, if any, of the comparison of the two frames. These counters are employed in PER calculations on the Supplemental Channels.

If all of the data block(s) received within a frame interval are identical to the locally generated data block(s), the frame is declared error-free and the corresponding frame counter is incremented to reflect this as shown in Table 32. Otherwise, the frame error is noted in the appropriate counter. These counters are employed in FER calculations on the Supplemental Channels.

Table 31 Counter updates for PDUs received on Supplemental Channels Rate of Data block Category Category of Counter to generated data comparison expected received MuxPDU increment block identical? 3 2 2 Y TDSO_E3_R3 3 2 2 N TDSO_E3RERR 3 2 1 N/A TDSO_E3_RE 2 5 5 Y TDSO_E2_R2 2 5 5 N TDSO.E2_RERR 2 5 3 N/A TDSOB2_RE la 1(2) Y TDSO_Ela_Rla la 1(2) 1(2) N TDSO_Ela_RERR la 1(2) 3 N/A TDSOJla.RE lb 4 4 Y TDSO_Elb_Rlb Ib 4 4 N TDSO_Elb RERR lb 4 3 N/A TDSOElb.RE 1 The category inside the parentheses is for secondary traffic.

Table 32 Counter updates for received frames on Supplemental Channels Category of each Category of each received Category of each received MuxPDU (if MuxPDU (if carried as Re of carried as secondary Frame Rate of primary traffic) traffic) frame comparison Counter to generated Sidentical? increment frame MuxPDU Type MuxPDU Type in use in use 1 2 3 5 1 2 3 N x 9.6 or 1 1 4,5 2 2 2 4,5 2 Y TDSO_ENx Nx 14.4' _RNx Nx 9.6 or 1 1 4,5 2 2 2 4,5 2 N TDSOENx N x 14.4 _RERR Nx 9.6 or 3 3 3 1 3 3 3 1 N/A TDSOENx N x 14.4 _RE Nx 9.6 or 2 2 4,5 2 1 1 4,5 2 N/A TDSO_ENx Nx 14.4 _RB Blank 2 2 4,5 2 1 1 4,5 2 N/A TDSO EB

RB

Blank 1,3 1,3 3 1 2,3 2,3 3 1 N/A TDSO_EB_

RO

'N can take the values 1, 2, 3, 4, 8, 16, 18, 32, 36, 64, or 72 depending on the allowed SCH transmission rate. The SCH frame consists of one or more data blocks of type Rate 1, Rate 2, or Rate 3 as determined by the connected multiplex option.

Transmit frame processing for 5 ms FCH/DCCH frames Mobile Station Requirement For R-FCH/DCCH 5 ms transmit frame processing in the mobile station, the TDSO shall request Layer 3 Signaling to transmit a SCRMM when TDSO decides to send a 5 ms frame based on the frame activity. If the R-SCHO has already been assigned, the mobile station shall set the fields of the SCRMM_REQ_BLOB as follows: SRID set to the sr_id corresponding to the connected SO PREFERREDRATE set to the currently connected R-SCHO rate S* DURATION field set to '1111' CI Otherwise, the mobile station should set the fields of the SCRMM_REQBLOB 0 as follows:

O

N SR_ID set to the sr_id corresponding to the connected SO PREFERRED_RATE set to any valid R-SCHO rate DURATION field set to '0000' c n The mobile station counts and stores the number of transmitted or retransmitted 5 ms frames in the counters (MUX1_REVFCH C( MUX2_REVDCCH_5_ms, MUX2_REV_DCCH_5_ms and O 10 MUX2_REV_FCH_5_ms) as specified in C Since TDSO has no control on timing in Layer 3 Signaling, the actual transmission of the mini message may occur in a later frame.

Base Station Requirement For F-FCH/DCCH 5 ms transmit frame processing in the base station, the TDSO shall request Layer 3 Signaling to transmit an FSCAMM when TDSO decides to send a 5 ms frame based on the frame activity. If the F-SCHO has already been assigned, the base station should set the fields of the FSCAMM as follows: FOR_SCHID set to '0' FORSCH_DURATION field set to '1111' SCCL_INDEX set to the Supplemental Channel Code list index corresponds to one currently in use by F-SCHO.

Otherwise, the base station should set the fields of the FSCAMM as follows: FOR_SCH_ID set to '0' FOR_SCH_DURATION field set to '0000' SCCL_INDEX set to any Supplemental Channel Code list index that corresponds to F-SCHO, if available. If there is no Supplemental Channel Code list index corresponds to F-SCHO, SCCL_INDEX shall be set to any value, in which case the mobile station ignores the SCCL_INDEX field.

The base station should count the number of transmitted or retransmitted 5 ms frames, which includes the following: Any 5 ms frame carrying a mini message that is initiated by TDSO O Any 5 ms frame carrying a mini message that is not initiated by TDSO A retransmitted 5 ms frame due to LAC retransmission 0 TDSO frame generation Two different categories of traffic can be transported over the connected TDSO: Selectable byte pattern ¢C Pseudo-randomly generated bits At the physical layer, by default, the TDSO is configured to generate primary traffic over the Forward and Reverse Fundamental Channels using RC3. The default test mode for the TDSO service option is the byte pattern OxFF with a 100% frame activity.

For every 20 ms FCH/DCCH frame, when TDSO generates a TDSO frame, it shall generate a Rate 1 data block.For every SCH frame, when TDSO generates a TDSO frame, it shall generate one or more Rate 1, Rate 2, or Rate 3 data blocks that are applicable to the connected SCH rate.

The actual size of the transmitted data block(s) during a TDSO frame depends on the multiplex sublayer command.

Selectable byte pattern When using this scheme, a single-byte pattern is used to fill the data block or data blocks that are passed to the multiplex sublayer (up to a whole number of octets) during each TDSO frame interval (20 ms, 40 ms, or 80 ms).

When the TDSO prepares a TDSO frame for a traffic channel, it shall perform the following: *Fill up a Rate 1, Rate 2, or Rate 3 data block, whichever is applicable, with single-byte pattern up to a whole number of octets. Pad the data block with bits for any remaining bits that are not filled. a 171-bit Rate 1 has 21 full octets and 3 additional bits. The additional remaining bits are filled by bits.) Replace the first 5 bits of the data block by the header depicted in Table 37. This helps the TDSO on the receive side to categorize the data blocks on a per-channel and per-PDU basis.

Pseudo-random number generation Pseudo-random number generators are utilized for frame generation. These generators are associated with a particular physical channel (forward or reverse) and are initialized at each synchronization frame. The pseudo-random O number generators are iterated one or more times for every frame. Iterations of C the pseudo-random number generators are used for information bit generation, O enough to fill two maximum rate physical layer frames (per the configured RC).

The bits are stored in circular buffers. The buffers are regenerated with a new seed of the System Time frame number associated with a synchronization frame every 10.24 seconds.

For each physical channel, a TDSO uses two independent pseudo-random

O

C number generators. One pseudo-random number generator is associated with C the Forward Traffic Channel, while the other is associated with the Reverse 10 Traffic Channel. These pseudo-random number generators are synchronized 0with their counterparts at the other end of the link, as shown in Figure 1. At synchronization time, the pseudo-random number generator for the transmit side is used for generating the circular buffer that serves as the data source for bits packed into data blocks each frame period for the next test segment (10.24 seconds). The receive side pseudo-random number generator, by emulating the frame generation process at the other end of the link, enables the service option to verify if a data block(s) is received error-free.

TDSO TDSO

F-FCH/F-DCCH

FBUF M F-SCH/F-SCH1

FBUF

M B

R-FCH/R-DCCH

RBUF M R-SCHO/R-SCH1 RBUF B Mobile Station Base Station Figure 1. Synchronized operation of pseudo-random number generated buffers On the transmit side, the bits from the circular buffer for a particular channel are packed serially into data blocks corresponding to the available MuxPDUs as determined by the connected multiplex option. The multiplex option indicates the size of the data block or data block(s), which is equal to the number of bits to be copied from the circular buffer to the last whole octet to form a data block or data blocks. Any remaining bits up to the data block size are filled with bits. For every frame, the service option shall copy the data bits from the N7 circular buffer, starting at a reference point plus an offset, to fill the data O block(s). The reference for the current frame shall be calculated as follows: If the 0 current frame is a synchronization frame, the reference point shall be set to zero; otherwise, the reference point shall be set to the end of the last byte that was copied into the previous frame. The offset, On, which is generated every frame, shall be set to the 6 least significant bits of RNG1128 modulo where B(n) is the buffer size and RNG is the random number generator associated with the physical channel (see Ofor buffer sizes]. This process is synchronized with its counterpart on the receive side. The receive side emulates the frame generation process at the other end by following the same process of building a frame (which consists of one or more data blocks) from the circular buffer each time from a different offset.

Depending on the frame activity or the TXONPERIOD/T&.OFFPERIOD, if the TDSO transmits the TDSO frame during the current frame, it shall perform the following: 0 Replace the first 5 bits of the generated data block(s) with the header depicted in Table 37. This helps the TWSO on the receive side to categorize the data blocks on a per-channel and per-PDU basis.

0 The TWSO shall pass the generated data block(s) to the multiplex sublayer. The TDSO shall supply the first x bits of the data block to the multiplex sublayer if the multiplex sublayer requests an x-bit data block, where x may be smaller than the number of bits in a Rate I data block.

Otherwise, the TDSO shall discard the generated data block(s) during this frame.

The service option shall store the state of all the Forward Traffic Channel pseudo-random number generators, FRNG, and the state of the Reverse Traffic Channel pseudo-random number generators, RRNG.

Initialization Before frame generation for every Forward Traffic Channel synchronization frame, the service option shall initialize the Forward Traffic Channel pseudorandom number generator as follows: a 16807 m 2147483647 O FRNG System Time in frames of the forward synchronization frame 'N FRNG (FRNG A Ox2AAAAAAA) Ox7FFFFFFF 9 FRNG (FRNG a) mod m O FRNG (FRNG a) mod m FRNG (FRNG a) mod m FRNG (FRNG a) mod m C Before frame generation for every Reverse Traffic Channel synchronization C frame, the service option shall initialize the Reverse Traffic Channel pseudorandom number generator as follows: Sa 16807 m 2147483647 RRNG System Time in frames of the reverse synchronization frame RRNG (RRNG A 0x55555555) Ox7FFFFFFF RRNG (RRNG a) mod m RRNG (RRNG a) mod m RRNG (RRNG a) mod m RRNG (RRNG a) mod m Number production Whenever a pseudo-random number is required for Forward Traffic Channel frame processing, the service option shall use the current value of FRNG as the pseudo-random number and then shall update FRNG as follows: a 16807 m 2147483647 FRNG (FRNG a) mod m Whenever a pseudo-random number is required for Reverse Traffic Channel frame processing, the service option shall use the current value of RRNG as the pseudo-random number and then shall update RRNG as follows: (a 16807 0 m 2147483647

O

RRNG (RRNG a) mod m e 24-bit random number The pseudo-random number generators that are used to fill the circular buffers (see Section 0 for more information) to determine the transitions between the 0 10 two TDSO states for calculation of frame activity (see Section Ofor more C, information) and to select the 6-bit byte offset in the circular buffer (see Section 0 for more information) each frame period, all have the following linear congruent relationship: Xn a x xn i mod m, where: Sa 7 5 16807 m 2 3 1 1 2147483647 Xn 1 and xn are the successive outputs of the generator and are 31-bit integers However, because of the better randomness properties of the most significant 24 bits within the 31-bit number and for ease of usage, especially for building circular buffers (31-bit number is not octet-aligned), only the most significant 24 bits of these numbers are used throughout. That is, 24-bit number 31-bit PN number 7 Circular buffer sizes The sizes of the required buffers for generation of Fundicated and Supplemental (for each Supplemental Channel) traffic frames for various radio configurations (RCs) on the forward/reverse links are indicated in Table 32, Table 33, and 81 0 Table 34. For convenience, the buffer sizes are based on the maximum number Sof bits passed by the multiplex sublayer to the physical layer each frame period 0 (5 ms, 20 ms, 40 ms, or 80 ms) depending on the radio configuration.

Table 32 Circular buffer sizes needed to generate fundicated channel data frames Table 33 Circular buffer sizes needed to generate reverse Supplemental Channel data frames.

Default circular buffer size- Circular buffer size 2 frames (bits) N frames (bits) 2 x 6,120 12,240 Nx 6,120 2 x 4,584 9,168 Nx 4,584 2 x 12,264 24,528 N x 12,264 2 x 20,712 =41,424 Nx 20,712 Table 34 Circular buffer sizes needed to generate forward Supplemental Channel data frames Default circular buffer size Circular buffer 2 frames (bits) size N frames (bits) 2 x 3,048 6,096 Nx 3,048 2 x 6,120 12,240 N x 6,120 2 x 4,584 9,168 N x 4,584 2 x 6,120 12,240 N x 6,120 2 x 12,264 24,528 Nx 12,264 2 x 9,192 18,384 Nx 9,192 2 x 20,712 =41,424 N x 20,712 The pseudo-random number generators used to fill the circular buffers have the following linear congruent relationship: xn a x xn 1 mod m, where: a 7 5 16807 m 2 3 1 1 2147483647 Xn 1 and Xn are the successive outputs of the generator and are 31-bit integers Information bit generation For every Forward or Reverse Traffic Channel frame, the TDSO iterates the associated pseudo-random number generator for the Physical Channel (FCH/DCCH or SCH) one or more times, as specified in the following subsections. For every synchronization frame, the service option shall initiate the circular buffer. However, for ease of implementation, the actual number of random bits in a circular buffer that is generated for a radio configuration is rounded to an octet-aligned number of bits determined exactly by the minimum number of iterations conducted on the associated pseudo-random number generator to achieve the given buffer size.

83 r- To generate the circular buffer at any rate R(n): N 0 The service option shall generate a total of NJM-RAND pseudo-random numbers (as shown in o Table 35) corresponding to actual circular buffer size B(n).

IND 0 Each 24,bit number y. 1 5 k 5 NUMRAND, shall be reshuffled and stored in the littleendian order as shown in Figure 2.

0 The reshuffled number y~ L(k) has the least significant byte of in the most significant byte position and vice versa.

24-bitS YA() IY. k[23I.' Y k)[161 Y(k)(151 Yn (k[8jYn (k[71 Y(k)O]1 LE Yn 1 Yn W[O kyM[15] Y k W[8]1Y .23 Y 16] Figure 2. Reshuffling of y. to generate yE f(k) For example, the 45-byte circular buffer (generated to accommodate a needed buffer size Of 344 bits) shall be comprised 6f y' through y' E(15) as follows: Yn Yn y' Y y' Table 35 Procedure for generating the default circular buffers for RC>2 channels Minimum required Needed circular Actual circular number of 24-bit pseudo- Pseudo-random bits buffer size buffer size (bytes) random numbers generated R(n) B(n)

NUMRAND

344 15 15 x 24 360 534 23 23 x 24= 552 69 6096 254 254 x 24 6096 762 9168 382 382 x 24 9168 1146 12240 510 510 x 24 12240 1530 18384 766 766 x 24= 18384 2298 24528 1022 1022 x 24 24528 3066 41424 1726 1726 x24= 41424 5178 Information-bit generation for an N-frame circular buffer follows the same method and principles as described for the 2-frame circular buffer case.

Frame activity If 5 ms FCH/DCCH frames are used, the TDSO shall decide whether or not to request Layer 3 Signaling to send a mini message for each 5 ms frame period based on the frame activity.

Otherwise, the TDSO passes the information bits to the multiplex sublayer according to a certain ON/OFF frame activity. For each frame period (20 ms, ms, or 80 ms) on a particular physical channel, the TDSO may choose to pass data block(s) corresponding to a full-rate frame on that channel or pass a blank data block to the multiplex sublayer. The TDSO shall support two different schemes to pass data to the multiplex sublayer, as follows: Deterministic frame activity This scheme is governed by the values of the TX_ON_PERIOD and TX_OFFPERIOD indicated in the Service Option Control Message. The fields represent (in units of ms, 20 ms, 40 ms, or 80ms, depending on the target physical channel configuration) the pattern for passing data to the multiplex sublayer.

O If the channel is an FCH/DCCH configured to use 5 ms frames, the TDSO shall: Request Layer 3 Signaling to send an FSCAMM in the base station (or a SCRMM in the mobile station) every 5 ms, for a duration of TX_ON_PERIOD.

O

0\ Not request an FSCAMM in the base station (or a SCRMM in mobile station) every 5 ms, for a duration of TXOFF_PERIOD.

Otherwise, the TDSO shall: C* Pass data blocks to the multiplex sublayer for a duration of TX ON_PERIOD.

Send blank data blocks for a duration of TX_OFF_PERIOD.

C The ON/OFF cycle starts at the synchronization frame and terminates at the last frame before the next synchronization frame for that channel.

Random with a specified frame activity and burst length This second scheme is more random. Its goal is to achieve a long-term average of a specified frame activity and a specified burst length which is defined as the average consecutive "On" period, for a channel. This goal is achieved by modeling the ON/OFF states by a two-state first order MarkoV chain with transition probabilities p and q, as indicated in Figure 3. The values of p and q are specified in the ON_TOOFF_PROB field and the OFF_TO_ON_PROB field, respectively, in the base-station control directive using the Service Option Control Message (see Table 39). The value of D can be calculated based on p and q as follows: D where p is the transition probability from the "On" state to the "Off' state, and q is the transition probability from the "Off' state to the "On" state, The average consecutive "On" period in units of frames, B, can be calculated follows: B i/p Procedures for calculating p and q based on some desired D and B are explained in Annex H.

1-p O 0ON

OFF

1-q

P

CN TDSO SA 24-bit pseudo-random number is used to drive the transitions between the Nl 5 two TDSO states every frame period (5 ms, 20 ms, 40 ms, and 80 ms). For all ms frame length-based physical channels, the TDSO uses the same PN number generator, iterating every 20 ms to calculate the transitions. If the operating Supplemental Channels are configured for 40 ms or 80 ms frame lengths, a second PN number generator iterating every 40 ms or 80 ms, respectively, is used to derive the TDSO state for the Supplemental Channels.

The PN generator for the 5 ms, 20 ms frame length channels shall be initialized at the first synchronization frame time after the TDSO is initialized at the action time that is associated with the Service Connect Message. For the 40 ms or 80 ms frame lengths, the associated PN number generator shall be initialized at the first synchronization frame time after the TDSO is initialized on the Supplemental Channel at the action time associated with the UHDM, ESCAM, FSCAMM, or RSCAMM. When initialized, the state of the Markov chain shall be set to the "Off' state.

Normally, the state of the PN generators is maintained throughout the duration of the call without any reinitialization at the synchronization frames. However, the PN generators are reinitialized if a CDMA-CDMA hard handoff has been completed. In case of the latter, the reinitialization occurs at the first synchronization frame after the handoff completion message. When reinitialized, the state of the Markov chain shall be set to the "Off' state.

Section Odescribes how the 24-bit PN number is derived. The method that is followed in choosing the TDSO state (ON or OFF) during a frame period is shown in Figure 4.

a =16807 m 2147483647 SEED System Time in frames of the first synchronization frame in time on any channel SEED (SEED A Ox2AAAAAAA) Ox7FFFFFFF SEED (SEED a) mod m SEED (SEED a) mod m SEED (SEED a) mod m 31_BIT_PNNUM (SEED a) mod m OFFTHRESHOLD= ROUND(16777215* p) ON_THRESHOLD ROUND(16777215*q) 24_BIT_PN_NUM 31BITPNNUM 7 No Yes I TDSOSTATE OFF TDSOSTATE ON I I 31_BIT_PN_NUM (31_BIT_PN_NUM a) mod m Figure 4. Flowchart illustrating TDSO state transitions for a D frame activity and B average "On" period in units of frames.

Data block header and formats In order to separate the calculation of FER on a per physical channel basis, a Channel ID must mark each data block that is supplied to the multiplex sublayer during each frame interval.

Also, a sequence number is needed to help compare multiple PDUs that carry individual data blocks received in a physical layer SDU with a locally generated frame.

The first 5 bits of each generated data block are replaced by the header as shown in Table 37 for the FCH/DCCH and SCH Multiplex PDUs.

Table 37 Data block format Field Length (bits) Definition CHANNEL ID 2 Channel ID of the underlying physical channel carrying the data block.

Various channel codes are shown in Table 37.

PDU_SEQNUM 3 Sequence number of the data block within a physical layer SDU.

For FCH/DCCH data blocks, this field is set to '000'.

For SCH data blocks, this field is set as follows: It is set to '000' for the first data block (MuxPDU) in the SCH frame, '001' for the second data block in the SCH frame, and so on.

DATA Variable up to the Data bits as generated according to the selected data block size DATA_SOURCE algorithm.

Table 37 CHANNEL_ID type codes CHANNEL_ID Traffic channel '00' FCH '01' DCCH

SCHO

'11' SCHI Message formats Service Option Control Message If the base station or mobile station sends a Service Option Control Message, it shall set the CTL_REC_TYPE field to the value shown in Table 38 corresponding to the desired directive.

Table 38 CTLRECTYPE codes CTL_REC_TYPE Type of directive '00000000' Control Directive for all Physical Channels carrying TDSO traffic '00000001' Control Directive for FCH '00000010' Control Directive for DCCH '00000011' Control Directive for SCHO '00000100' Control Directive for SCH1 '00000101' Counter Retrieval Directive for FCH '00000110' Counter Retrieval Directive for DCCH '00000111' Counter Retrieval Directive for SCHO '00001000' Counter Retrieval Directive for SCH1 '00001001'-'11111111' Reserved Control When the mobile station sends a Service Option Control Message to propose control action or the base station sends a Service Option Control Message to invoke control action in a mobile station, it shall include the type-specific fields as specified in Table 39.

Table 39 Service Option Control Message type-specific fields Length Field Definition (bits) CTL_REC_TYPE 8 Control record type field.

C00000000'-'00000100') The mobile station or base station shall set this field to a value between '00000000' and '00000100' to signify a control directive on all TDSO-configured channels or for a specific channel according to Table 38.

CONTROLCODE 8 Control code field.

The mobile station or base station shall set this field according to Table Length Field Length Definition (bits) CHANNELDIRECTION 2 Channel direction field.

This field indicates what channel direction this control directive is for. The base station or mobile station shall set this field according to Table 43.

COPYCOUNTERS 1 Copy counters field.

If the mobile station and base station are to copy the counter values at the next synchronization frame, the base station shall set this field to Otherwise, the base station shall set this field to CLEARCOUNTERS 1 Clear counters field.

If the mobile station and base station are to clear the counters at the next synchronization frame, the base station shall set this field to Otherwise, the base station shall set this field to DATASOURCE 1 Data source field.

The mobile station or base station shall set this field to the DATASOURCE value shown in Table 42 corresponding to the type of traffic that is desired to be generated during the test call.

FRAMESOURCE 2 Frame source field.

Through this field, the base station or mobile station defines the source to be used for filling up the data frames for the particular channel. The various options are indicated in Table 44.

FRAMEIACTIVITY 1 Frame activity field.

The base station or mobile station shall set this field to the FRAMEACTIVITY value shown in Table 42 corresponding to the desired burstiness in the traffic that is to be generated during the test call.

TEST_OPTIONS 8 TDSO Test Options.

The base station or mobile station shall set this field according to Table Length Field Length Definition (bits) NUM_CIRC_BUF_FRAME 0 or 8 Number of full-rate frames in the circular buffer field.

S The mobile station or base station shall set this field to indicate the desired size of the circular buffer frames. This field is present only if the FRAMESOURCE field is set to If the control directive is a mobile station proposal and the base station cannot support the proposed buffer size, the base station shall set this field to the maximum number of frames it can support during that call for that channel.

ON_TO_OFF_PROB 0 or 8 "On" state to "Off" state transition probability field.

This frame is only present if the FRAMEACTIVITY field has a value of 1. The base station or mobile station shall set this field to the ROUND(Desired "On" to "Off" state transition probability 100). The valid range for this field is between '00000000' and '01100100'.

OFFTO_ON_PROB 0 or 8 "Off" state to "On" state transition probability field.

This frame is only present if the FRAME.ACTIVTY field has a value of 1. The base station or mobile station shall set this field to the ROUND(Desired "Off" to "On" state transition probability 100). The valid range for this field is between '00000000' and '01100100'.

TXONPERIOD 0 or 8 Transmission on period field.

This frame is only present if the FRAMEACTIVITY field has a value of 0. The base station or mobile station shall set this field to the desired number of adjacent frame periods ms, 40 ms, or 80 ms). The TDSO shall supply nonblank data frames to the multiplex sublayer before passing blank frames to it for the number of frame periods indicated by the TX_OFFPERIOD field.

Length Field Definition (bits) TXOFF_PERIOD 0 or 8 Transmission off period field.

This frame is only present if the FRAMEACTIVITY field has a value of The base station or mobile station shall set this field to the desired number of adjacent frame periods (20 ms, 40 ms, or 80 ms). The TDSO shall supply blank frames to the multiplex sublayer after passing nonblank frames to it for the number of frame periods indicated by the TXONPERIOD field.

DATAPAITERN 0 or 8 Data pattern field.

This frame is only present if the DATA_SOURCE field has a value of The mobile station or base station shall set this field to the selectable byte pattern to be used for the test corresponding to the type of traffic that is generated during the test call.

O

1^ 0

O

O

m C m m, o\, Table 40 CONTROL_CODE codes CONTROLCODE Meaning '00000000' Mobile station proposed control directive '00000001' Base station control directive '00000010' Base station control directive based on mobile station proposal '00000011' Base station control directive based on mobile station proposal (number of frames in circular buffer not supported NUM_CIRC_BUF_FRAMES field indicates maximum number of frames base station can support) '00000100' Base station control directive based on mobile station proposal (message cannot be handled by the current base station configuration) '00000101' Base station control directive based on mobile station proposal (message structure not acceptable) '00000110' Base station control directive based on mobile station proposal (unable to support a value of '10' for the FRAME_SOURCE field as indicated in Table 44, that is, cannot generate 1 frame each frame period) '00000111'-'11111111' Reserved Table 41 DATASOURCE codes DATA_SOURCE Traffic pattern Selectable data pattern Pseudo-random bits Table 42 FRAMEACTIVITY codes Table 43 FRAME.ACTIVITY Type Deterministic frame activity Random frame activity CHANNELDIRECTION codes CHANNEL_DIRECTION Channel types '00' Both forward and reverse link directions '01' Forward link direction only Reverse link direction only '11' Reserved Table 44 FRAMESOURCE codes FRAMESOURCE Circular buffer composition '00' 2 full-rate frames '01' N full-rate frames New frame every frame period (20 ms, ms, or 80 ms) '11' Reserved Table 45 TEST_OPTIONS codes TESTOPTIONS TDSO Test Options '00000000' -'11111111' Reserved Counter retrieval When the base station or mobile station sends a Service Option Control Message to retrieve counter values from the other end for any of the Fundicated channels (FCH/DCCH), it shall include the type-specific fields as specified in Table 46.

Table 46 Type-specific fields in a Service Option Control Message used for counter retrieval on the FCH/DCCH Field Length (bits) Definition CTL_REC_TYPE 8 Control record type field.

("00000101' or The mobile station or base station shall set this 00000110') field to '00000101' to signify a counter retrieval directive on the FCH and '00000110' to signify a counter retrieval directive on the DCCH.

VECT-COUNTERID 8 Vector counter identification field.

The base station or mobile station shall set this field to correspond to the value shown in Table 47 for the Fundicated Channels and in corresponding to the desired vector of counter values.

Table 47 VECTCOUNTER_ID codes for FCH/DCCH VECT_COUNTER_ID Vector name '00000000' FER counters '00000001' Receive Expected Counters Response '00000010' Transmitted counters '00000011' 5 ms Frame Transmitted counters '00000100' 5 ms Frame Received counters '00000101'-'11111111' Reserved When the base station or mobile station sends a Service Option Control Message to retrieve counter values from the other end for the SCHs, it shall include the type-specific fields as specified in Table48.

Table48 Type-specific fields in a Service Option Control Message used for counter retrieval from the mobile station for SCHs Field Length (bits) Definition CTL_RECTYPE 8 Control record type field.

('00000111' or The base station or mobile station shall set this field to 0001000') signify a counter retrieval directive on the Supplemental Channels. For the SCHO and SCH1 channels, the field shall be set to '00000111' and '00001000', respectively.

VECTCOUNTERJID 8 Vector counter identification field.

The base station or mobile station shall set this field to correspond to the value shown in Table 49 corresponding to the desired vector of counter values.

Table 49 VECT_COUNTER_ID codes for SCHs VECT COUNTER_ID Vector name '00000000' FER counters response '00000001' PER '00000010' Transmitted counters response '00000011' -'11111111' Reserved Counter responses on the fundicated channels FER Counters Response When the mobile station or base station sends a FER Counters Response for the FCH or DCCH channels, it shall include the following type-specific fields in the Service Option Control Message: 98 Table 50 Type-specific fields in a Service Option Control Message corresponding to FER Counters Response on FCH/DCCH Length Field LeDg Definition (bits) CTrLREC_TYPE 8 Control record type field.

('00000101' or '00000110') (00000101or'0000010) The mobile station or base station shall set this field to '00000101' when responding to an FCH Control directive and '00000110' for DCCH.

VECTCOUNTERID 8 Vector counter identification field.

('00000000) The mobile station or base station shall set this field to '00000000'.

TDSO_El_R1 24 Counter for Rate 1 data blocks received error free.

The mobile station shall set this field to the value of TDSOEl_RI stored in the FFCHBUFFER or FDCCH-BUFFER modulo 224.

The base station shall set this field to the value of TDSOE1_R stored in the RFCHBUFFER or RDCCHBUFFER modulo 2".

TDSO_El_RBAD 24 Number of Rate 1 data blocks received in error.

The mobile station shall compute this value using counter values stored in the FFCHUFFER or FDCCHBUFFER as follows: TDSO_E1_RBAD (TDSOE1_RERR TDSO_E1_RD TDSO_ElRE TDSOElRO TDSO_E1_RB TDSO_El_RFL) mod 22.

The base station shall compute this value using counter values stored in the RFCH_BUFFER or RDCCH BUFFER as follows: TDSOElRBAD (TDSO_E1_RERR TDSO_E1_RD TDSOE1_RE TDSOE1_lRO TDSOE1_RB TDSO.EI_RFL) mod 224.

Field LeghDefinition (bits) TDSOENRN 24 Counter for blank frames received as null frames.

The mobile station shall set this field to the value of TDSOENRN stored in the FFCHBUFFER or FDCCHBUFFER modulo 224.

The base station shall set this field to the value of TDSOENRN stored in the RFCHI.BUFFER]RDCCHBUFFER modulo 2~.

TDSOENREAD 24 Number of null data blocks received in error.

The mobile station shall compute this value using counter values stored in the FFCHLBUFFER or FDCCHBUFFER as follows: TDSOEN._RBAD (TDSOEN_-RB TDSOlENRO) mod 224.

The base station shall compute this value using counter values stored in the RFCHLBUFFER or RDCCH-BUFFER as follows: TDSO-EN-RBAD CrDSOIENRB TDSOENRO) mod 2214.

TDSO.x-RBAD 24 Number of bad overall data blocks.

The mobile station shall compute this value using counter values stored in the FFCHLBUFFER or FDCCHBUFFER as follows: TDSOExRBAD =(TDSCLEl-RBAD TDSOENRB TDSO-EN-RO) Mod 24.

The base station shall compute this value using counter values stored in the RFCH.BUFFER or RDCCHBUFFER as follows: TDSO__Ex__RBAD (TDSO ELRBMAD TOSOENRB TDSO_EN_RO) mod 2.

Receive Expected Counters Response When the mobile station or base station sends a Receive Expected Counters Response, it shall include the following type-specific fields in the Service Option Control Message: Table 51 Type-specific fields in a Service Option Control Message corresponding to Receive Expected Counters Response on FCH/DCCH Field Length (bits) Definition CTL_REC TYPE 8 Control record type field.

('0000o or The mobile station shall set this field to '00000101' '00000110') 00000110) when responding to an FCH Control directive and '00000110' for DCCH.

VECTCOUNTEIID 8 Vector counter identification field.

('0000001) The mobile station shall set this field to '00000001'.

TDSO_E1_R1 24 Counter for Rate 1 frames received error-free.

The mobile station shall set this field to the value of TDSO_EI_R stored in the FFCH_BUFFER or FDCCH_BUFFER, modulo 24.

The base station shall set this field to the value of TDSO_E1_R1 stored in the RFCH_BUFFER or RDCCH_BUFFER, modulo 2".

TDSO_E1_RD 24 Counter for the number of dim-and-burst frames received given that the expected data block was Rate 1.

The mobile station shall set this field to the value of TDSO_E1_RD stored in the FFCH._BUFFER or FDCCHBUFFER, modulo 24.

The base station shall set this field to the value of TDSO_E1_RD stored in the RFCHBUFFER or RDCCHBUFFER, modulo 224.

Field Length (bits) Definition TDSO El_RO 24 Counter for the number of any other frames received (excluding dim-and-burst types) given that the expected data block was Rate 1.

The mobile station shall set this field to the value of TDSO E1_RO stored in the FFCH BUFFER or FDCCH_BUFFER, modulo 224.

The base station shall set this field to the value of TDSO_E1_RO stored in the RFCHIBUFFER or RDCCIHBUFFER, modulo 224.

TDSO_E1_RB 24 Counter for the number of blank-and-burst frames received given that the expected data block was Rate 1.

The mobile station shall set this field to the value of TDSO_EI_RB stored in the FFCHJBUFFER or FDCCHBUFFER, modulo 24.

The base station shall set this field to the value of TDSOEIRB stored in the RFCHBUFFER or RDCCH_BUFFER, modulo 224.

TDSO_E1_RFL' 24 Counter for the number of Rate 1 frames with bit errors received (a categorization only applicable with the Multiplex option 2 given that the expected data block was Rate 1.

The mobile station shall set this field to the value of TDSO_E1_RFL stored in the FFCH_BUFFER or FDCCHBUFFER, modulo 2 24 The base station shall set this field to the value of TDSOE1_RFL stored in the RFCH_BUFFER or RDCCLHBUFFER, modulo 2 24 Field Length (bits) Definition TDSO E1_RE 24 Counter for the number of frames received with Insufficient frame quality (erasure) given that the expected data block was Rate 1.

The mobile station shall set this field to the value of TDSOEl RE stored in the FFCH BUFFER or FDCCH_BUFFER, modulo 224.

The base station shall set this field to the value of TDSO_El_RE stored in the RFCHBUFFER or RDCCHBUFFER, modulo 224.

TDSO El RERR 24 Counter for the number of Rate 1 frames received with bit errors (detected by the TDSO) given that the expected data block was Rate 1.

The mobile station shall set this field to the value of TDSO_E1_RERR stored in the FFCHBUFFER or FDCCH_BUFFER, modulo 224.

The base station shall set this field to the value of TDSO_EI_RERR stored in the RFCH_BUFFER or RDCCHBUFFR, modulo 2".

TDSOEN_RN 24 Counter for the number of null frames received given that the expected data block was also null.

The mobile station shall set this field to the value of TDSO_EN_RN stored in the FFCH_BUFFER or FDCCH_BUFFER, modulo 2 4 The base station shall set this field to the value of TDSOENRN stored in the RFCHBUFFER or RDCCHBUFFER, modulo 2 2 TDSO_EN_RB 24 Counter for the number of blank frames received given that the expected data block was null.

The mobile station shall set this field to the value of TDSOENRB stored in the FFCH_BUFFER or FDCCHBUFFER, modulo 2".

The base station shall set this field to the value of TDSO EN_RB stored in the RFCHBUFFER or RDCCH_BUFFER, modulo 2".

Field Length (bits) Definition TDSOENRO 24 Counter for the number of other categories of MuxPDU received given that the expected frame was null.

The mobile station shall set this field to the value of TDSOENRO stored in die FFCH_BUFFER or FDCCH_BUFFER, modulo 2".

The base station shall set this field to the value of TDSO EN RO stored in the RFCHBUFFER or RDCCHBUFFER, modulo 224.

L The counter does not get incremented for Multiplex Option 2.

2 This counter does not get incremented with Multiplex Option 2.

Transmitted Counters Response When the mobile station or base station sends a Transmitted Counters Response, it shall include the following type-specific fields in the Service Option Control Message: Table 52 Type-specific fields in a Service Option Control Message corresponding to Transmitted Counters Response on FCH/DCCH Length Field ngth Definition (bits) CTLREC_TYPE 8 Control record type field.

('00000101' or The mobile station or base station shall set this field to '00000110') '00000101' when responding to an FCH control directive and '00000110' for DCCH.

VECT_COUNTER_ 8 Vector counter identification field.

D ('00000010') D (00000010) The mobile station or base station shall set this field to '00000010'.

j Length Field Definition (bits) TDSO_El_T1 24 Counter for Rate 1 frames transmitted with no dim-and-burst or blank-and-burst given that the generated data block was Rate 1.

The mobile station shall set this field to the value of TDSO_E1_T1 stored in the RFCH_BUFFER or RDCCH_BUFFER, modulo 224.

The base station shall set this field to the value of TDSO_E1_T1 stored in the FFCH_BUFFER or FDCCHBUFFER, modulo 224.

TDSO_EI_TD 24 Counter for the number of dim-and-burst frames transmitted, given that the generated data block was Rate 1.

The mobile station shall set this field to the value of TDSO_El_TD stored in the RFCH_BUFFER or RDCCH_BUFFER, modulo 224.

The base station shall set this field to the value of TDSO_E1_TD stored in the FFCH_BUFFER or FDCCHBUFFER, modulo 2".

TDSO_E1_TB 24 Counter for the number of blank-and-burst frames transmitted, given that the generated data block was Rate 1.

The mobile station shall set this field to the value of TDSOE1_TB stored in the RFCH_BUFFER or RDCCHBUFFER, modulo 224.

The base station shall set this field to the value of TDSO_E1 TB stored in the FFCH_BUFFER or FDCCHBUFFER, modulo 22.

TDSOEBTB 24 Counter for the number of blank-and-burst frames transmitted, given that the generated data block was blank.

The mobile station shall set this field to the value of TDSO_EB_TB stored in the RFCH_BUFFER or RDCCH BUFFER, modulo 224.

The base station shall set this field to the value of TDSO_EB_TB stored in the FFCHBUFFER or FDCCHBUFFER, modulo 2 2

O

O

0 Definition TDSOEB_TO Counter for the number of other frame types transmitted, given that the generated data block was blank (basically, the counter for the event when the TDSO wants to transmit a blank and the multiplex sublayer also requests a blank frame for the particular frame period).

The mobile station shall set this field to the value of TDSO_EB_TO stored in the RFCH_BUFFER or RDCCH_BUFFER, modulo 2 2 The base station shall set this field to the value of TDSO_EB_TO stored in the FFCH_BUFFER or FDCCH_BUFFER, modulo 224.

ms Frame Transmitted Counters Response When the mobile station sends a 5 ms Frame Transmitted Counters Response, it shall include the following type-specific fields in the Service Option Control Message: Table 53 Type-specific fields in a Service Option Control Message corresponding to 5 ms Frame Transmitted Counters Response on FCHIDCCH Length Field ngth Definition (bits) CTL_REC_TYPE 8 Control record type field.

('00000101' or The mobile station or base station shall set this field to '00000101' when responding to an FCH control directive and '00000110' for DCCH.

VECTCOUNTER_I 8 Vector counter identification field.

D (00000011') The mobile station shall set this field to '00000011'.

24 Counter for 5 ms transmitted.

1 If CTL_REC_TYPE is set to '00000101', the mobile station shall set this field to the value of MUX1_REV_FCI-_5_ms (see stored in mobile station, modulo 2 2 at the ACTION_TIME specified by this Service Option Control Message.

Otherwise, the mobile station shall set this field to the value of (see stored in mobile station, modulo at ACTIONTIME specified by this Service Option Control Message.

TDSOMUX2 5ms_T 24 Counter for 5 ms transmitted.

If CTL_REC_TYPE is set to '00000101', the mobile station shall set this field to the value of MUX2_REV.FCH_5_ms (see stored in mobile station, modulo 224, at the ACTION_TIME specified by this Service Option Control Message.

Otherwise, the mobile station shall set this field to the value of (see stored in mobile station, modulo 2 2 at ACTION_TIME specified by this Service Option Control Message.

ms Frame Received Counters Response When the mobile station sends a 5 ms Frame Received Counters Response, it shall include the following type-specific fields in the Service Option Control Message: Table 54 Type-specific fields in a Service Option Control Message corresponding to 5 ms Frame Received Counters Response on FCHIDCCH Length Field LegtDefinition (bits) CTL_RECTYPE 8 Control record type field.

('00000101' or The mobile station or base station shall set this field to '00000110') '00000101' when responding to an FCH control directive and '00000110' for DCCH.

VECT_COUNTER_ID 8 Vector counter identification field.

(00000100The mobile station shall set this field to '00000100'.

1 24 Counter for 5 ms received.

If CTL_REC_TYPE is set to '00000101', the mobile station shall set this field to the value of MUX1_FO.RFCH_5_ms (see stored in mobile station, modulo at the ACTION_TIME specified by this Service Option Control Message.

Otherwise, the mobile station shall set this field to the value of (see stored in mobile station, modulo 22, at ACTION_TIME specified by this Service Option Control Message.

TDSO_MUX2_5msR1 24 Counter for 5 ms received.

If CTL_REC_TYPE is set to '00000101', the mobile station shall set this field to the value of MUX2_FOR_FCH_5_ms (see stored in mobile station, modulo 2 2 at the ACTION_TIME specified by this Service Option Control Message.

Otherwise, the mobile station shall set this field to the value of (see stored in mobile station, modulo 2 2 at ACTION_TIME specified by this Service Option Control Message.

Counter responses on the Supplemental Channels FER counters response When the mobile station or base station sends an FER Counters Response, it shall include the following type-specific fields in the Service Option Control Message: Table 55 Type-specific fields in a Service Option Control Message corresponding to FER Counters Response on SCH(s) Field Length (bits) Definition CTL_REC§ITYPE 8 Control record type field.

(-00000111- The mobile station shall set this field to '00000111' or 00001000' '00001000', respectively, when responding to an SCHO or SCHI control directive.

VECi'_COUNTER- 8 Vector counter identification field.

ID ('00000000') T'he mobile station or base station shall set this field to '00000000'.

TDSO..ENx-RNx 24 Counter for Nx9.6 or Nxl4.4 frames received error-free.

The mobile station shall set this field to the value of TDSO_E lNx_RNx stored in the PSCHOLBUFFER or FSCHIBUFFER, modulo 2 24.

The base station shall set this field to the value of T7DSO-.ENx..RNx stored in the RSCHO-BIFFER or RSCHL-BUFFER, modulo 2 4 TDSO...ENx..RBAD 24 Number of bad frames received instead of Nx9.6 or Nx14.4 frames.

The mobile station shall compute this value using counter values stored in the FSCHOBUFFER or FSCH1_BUFFER as follows: TDSOJENx..RBAD (TDSO..ENx_RERR TDSO...ENxRE TDSOENxRB) mod 224.

The base station shall compute this value using counter values stored in the RSCHO-BUFFER or RSCHI-BUFFER as follows: TDSO_ENx_RBAD (TDSCLENx_RERR TDS(ILENxRE ThSO..Nx..RB) mod 224.

TDSO_.EB_ RB 24 Counter for blank frames received as blank frames.

The mobile station shall set this field to the value of TDSO_1BR B stored in the FSCHOBUFFER or FSCHL.BUFFER. miodulo 224 The base station shall set this field to the value of TDSOEBRB stored in the RSCHO_BUFFER or RSCHIBUFFER, modulo 224 Field Length (bits) Definition TDSO_EBRBAD 24 Number of bad frames received instead of blank frames.

The mobile station shall compute this value using counter values stored in the FSCHO BUFFER or FSCH1_BUFFER as follows: TDSO_EB_RBAD (TDSO_EB_RO) mod 224.

The base station shall compute this value using counter values stored in the RSCHO_BUFFER or RSCH1BUFFER as follows: TDSO_EBRBAD (TDSO_EBRO) mod 224.

TDSO_Ex_RBAD 24 Number of bad overall frames.

The mobile station shall compute this value using counter values stored in the FSCHOBUFFER or FSCH1BUFFER as follows: TDSO_E1_RBAD (TDSO_ENx_RBAD TDSO_EB_RO) mod 2 2 4 The base station shall compute this value using counter values stored in the RSCHOBUFFER or RSCHIBUFFER as follows: TDSOJE_RBAD (TDSO_ENx_RBAD TDSO_EB_RO) mod 224.

PER Counters Response When the mobile station or base station sends a PER Counters Response, it shall include the following type-specific fields in the Service Option Control Message: Table 56 Type-specific fields in a Service Option Control Message corresponding to PER Counters response on SCH(s) Length Field Definition (bits) CTL_REC_TYPE 8 Control record type field.

('00000111' or The mobile station shall set this field to '00000111' or'00001000', '00001000') respectively, when responding to an SCHO or SCH1 control directive.

VECTCOUNTER_ID 8 Vector counter identification field.

00000001) The mobile station shall set this field to '00000001'.

Length Field Definition (bits) TDSO_E3_R3 24 Counter for Rate 3 frames received error-free.

The mobile station shall set this field to the value of TDSO_E3 R3 stored in the FSCHO_BUFFER or FSCH1_BUFFER, modulo 24.

The base station shall set this field to the value of TDSO_E3_R3 stored in the RSCHO_BUFFER or RSCHIBUFFER, modulo 2".

TDSOE3 RERR 24 Counter for Rate 3 frames received with errors detected by the

TDSO.

The mobile station shall set this field to the value of TDSO_E3_RERR stored in the FSCHO BUFFER or FSCH1_BUFFER, modulo 224.

The base station shall set this field to the value of TDSOE3_RERR stored in the RSCHOBUFFER or RSCH1BUFFER, modulo 224.

TDSO_E3_RE 24 Counter for expected Rate 3 frames received as erasures.

The mobile station shall set this field to the value of TDSO_E3_RE stored in the FSCHO3BUFFER or FSCH13UFFER, modulo 2".

The base station shall set this field to the value of TDSO_E3_RE stored in the RSCHO_BUFFER or RSCHI_BUFFER, modulo 2".

TDSO_E2_R2 24 Counter for Rate 2 frames received error-free.

The mobile station shall set this field to the value of TDSO_E2_R2 stored in the FSCHO_BUFFER or FSCHIBUFFER, modulo 2 4 The base station shall set this field to the value of TDSO_E2_R2 stored in the RSCHO.3UFFER or RSCH1_BUFFER, modulo 224.

TDSO_E2_RERR 24 Counter for Rate 2 frames received with errors detected by the

TDSO.

The mobile station shall set this field to the value of TDSO_E2_RERR stored in the FSCHOJ3UFFER or FSCH1BUFFER, modulo 24.

The base station shall set this field to the value of TDSOE2_RERR stored in the RSCHO_BUFFER or RSCH1_BUFFER, modulo 224.

Cc, Cc, Cc, Length Field Length Definition (bits) TDSOE2_RE 24 Counter for expected Rate 2 frames received as erasures.

The mobile station shall set this field to the value of TDSO_E2_RE stored in the FSCHO_BUFFER or FSCH1LBUFFER, modulo 2 24 The base station shall set this field to the value of TDSOE2 RE stored in the RSCHO_BUFFER or RSCH1_BUFFER, modulo 224.

TDSO_Ela_Rla 24 Counter for Rate la frames received error-free.

The mobile station shall set this field to the value of TDSO_Ela_Rla stored in the FSCHO_BUFFER or FSCH1 BUFFER, modulo 224.

The base station shall set this field to the value of TDSO.Ela_Rla stored in the RSCHO_BUFFER or RSCHIBUFFER, modulo 224.

TDSO..ElaRERR 24 Counter for Rate la frames received with errors detected by the

TDSO.

The mobile station shall set this field to the value of TDSO_Ela_RERR stored in the FSCHO_BUFFER or FSCH1_BUFFER, modulo 224.

The base station shall set this field to the value of TDSO_Ela_RERR stored in the RSCHO_BUFFER or RSCH1_BUFFER, modulo 2 4 TDSO_Ela_RE 24 Counter for expected Rate la frames received as erasures.

The mobile station shall set this field to the value of TDSOElaRE stored in the FSCHOBUFFER or FSCHIBUFFER, modulo 24.

The base station shall set this field to the value ofTDSOEla_RE stored in the RSCHO_BUFFER or RSCH1_BUFFER, modulo 224.

TDSOElb_Rlb 24 Counter for Rate lb frames received error-free.

The mobile station shall set this field to the value of TDSO ElbRlb stored in the FSCHO_BUFFER or FSCH1_BUFFER, modulo 224.

The base station shall set this field to the value of TDSO_Elb Rlb stored in the RSCHO_BUFFER or RSCH1_BUFFER, modulo 2".

Field LeghDefinition (bits) TDS&-ElbRERR 24 Counter for Rate lb frames received with errors detected by the

TDSO.

The mobile station shall set this field to the value of TDSOBib RERR stored in the FSGHOBUFFER or FSCHILBUFFER, modulo 2~.

The base station shall set this field to the value of TD3SO_Elb _RERR stored in the RSCHOBUFFER or RSCHLB UFFER, modulo 224.

TDS&-ElbRE 24 Counter for expected Rate l b frames received as erasures.

The mobile station shall set this field to the value of TDSO_ElbRE stored in the FSCH(LBFFR or FSCHL-BUFFER, modulo 22.

The base station shall set this field to the value of TDSO_EibRE stored in the RSCHO_BUFFER or RSCH1BUFFER, modulo 224

O

O

Transmitted Counters response When the mobile station or base station sends a Transmitted Counters Response, it shall include the following type-specific fields in the Service Option Control Message: Table 57 Type-specific fields in a Service Option Control Message corresponding to Transmitted Counters response on SCH(s) Length Field Definition (bits) CTLREC_TYPE 8 Control record type field.

{'00000111' or 000001' or The mobile station shall set this field to '00000111'or '00001000', '00001000) respectively, when responding to an SCHO or SCH1 control directive.

VECTCOUNTERI 8 Vector counter identification field.

D ('00000010') The mobile station shall set this field to '00000010'.

TDSO_ENx_TNx 24 Counter for Rate Nx9.6 or Rate Nx 14.4 frames transmitted with no blank command from the multiplex sublayer.

The mobile station shall set this field to the value of TDSO_ENx_TNx stored in the RSCHOBUFFER or RSCHI1BUFFER, modulo 2".

TDSO_ENx_TB 24 Counter for the number of blank frames transmitted given that the generated frame was Rate Nx9.6 or Rate Nx14.4.

The mobile station shall set this field to the value of TDSO_ENxTB stored in the RSCHOBUFFER or RSCH1IBUFFER, modulo 224.

TDSO EB_TB 24 Counter for the number of blank frames transmitted, given that the generated frame was blank.

The mobile station shall set this field to the value of TDSO_EB_TB stored in the RSCHO_BUFFER or RSCH1_BUFFER, modulo 224.

Length Field ngth Definition (bits) TDSO_EBTO 24 Counter for the number of other frame types transmitted given that the generated frame was blank (basically, the counter for the event when the TDSO wants to transmit a blank and the multiplex sublayer also requests a blank frame for the particular frame period).

The mobile station shall set this field to the value of TDSO_EB_TO stored in the RSCHO_BUFFER or RSCHIBUFFER, modulo 224.

TDSO Call Flow Examples (for a system operating in MC-41 mode) This annex contains examples of TDSO call flows using service negotiation.

Figure 5 to Figure 7 use the following convention: All messages are received without error.

Acknowledgments are not shown.

Mobile Station Detects user-initiated call.

Sends Origination Message specifying the TDSO service option.

Sets up Fundicated Traffic Channel.

Receives Ns5 consecutive valid frames.

Begins sending the Traffic Channel preamble.

Begins transmitting null Traffic Channel data.

r-csch f-csch r-dtch f-dsch Service Negotiation r/f-dsch f-dsch r-dsch Base Station Sets up Fundicated Traffic Channel(s).

Begins sending null Traffic Channel data.

Sends Extended Channel Assignment Message.

Acquires the Reverse Fundicated Traffic Channel.

Sends Base Station Acknowledgment Order.

Sends Service Message.

Connect Sends Service Connect Completion Message.

(Continued on next page) (Continued on next page) Figure 5. Mobile station origination example with transmission on DCCH/FCH/SCH (part 1 of 2)

O

1^ 0

O

(O

O

0 C€3 C€3 C€3 0N Mobile Station Enters the Conversation Substate, and connects the TDSO service option at the action time specified in the Service Connect Message.

Generates Rate 1 frames (by default all Is) from the time of service option connection to the frame prior to the first synchronization frame. At the first synchronization frame, resynchronizes the TDSO.

Sends Supplemental Channel Request Message and continues transmitting on the Reverse Traffic Channel.

Connects the TDSO at the action time specified in the SCH allocation message. Generates Rate 1 frames (by default all Is) from the time of service option connection to the frame prior to the first synchronization frame.

At the first synchronization frame resynchronizes the TDSO.

Continues transmitting on the Reverse Fundicated Channels.

dsch/dtch r-dsch f-dsch/f-dtch dsch/dtch Base Station Connects and initializes the TDSO service option following the action time specified in the Service Connect Message.

Allocates Supplemental Channel(s) through ESCAM, FSCAMM, RSCAMM, or UHDM.

Connects and initializes the TDSO service option following the action time specified in the ESCAM, FSCAMM, RSCAMM, or UHDM. Continues transmission on the Forward Fundicated Channels.

1" I (TDSO Traffic) (TDSO Traffic) Figure 6. Mobile station origination example with transmission on DCCH/FCH/SCH (part 2 of 2) Mobile Station (TDSO Call Active) Sends an acknowledgement.

Accepts the new fields.

Starts processing using the new data source and/or frame activity specified in the Service Option Control Message from the next synchronization frame on the specified Supplemental Channel.

Continues to use the same TDSO configuration on the Fundicated channels.

f-dsch/dtch r-dsch/dtch Base Station (TDSO Call Active) Sends Service Option Control Message specifying a new type of data source and/or transmission frame activity on the Supplemental Channel.

Starts processing TDSO traffic using the new data source and/or frame activity from the next synchronization frame on the Supplemental Channel. Continues to use the same TDSO configuration on the Fundicated channel.

(TDSO Traffic)

I

(TDSO Traffic) Figure 7. Base station commanded test parameter rs change rs change No text.

TDSO Operation Examples B.1 A TDSO scenario This annex provides two examples of TDSO test scenarios. Assume the following: The TDSO is configured to carry primary traffic over the FCH in both forward and reverse directions and on SCHO in only the forward direction.

The mobile station and base station are configured to support the RC3 configuration for the test setup.

The TDSO is passing pseudo-randomly generated data blocks to the mux sublayer per Multiplex Option 0x01 on the FCH (that is, one MuxPDU Type 1 data block can be passed to the multiplex sublayer every 20 ms).

0 SCHO is configured for 20 ms frame length, has been allocated to support 19.2 kbps, and carries K1 TDSO-generated pseudo-random data bits per Multiplex Option 0x809 format (that is, two 0 single-sized MuxPDU Type 3 data blocks can be supplied to the multiplex sublayer every O ms).

p is equal to 0.7 and q is equal to 0.3. Then, D 0.3, B lip OFF_THRESHOLD ROUND(16777215 p) 11744051 and ON_THRESHOLD ROUND(16777215 q) S5033164.

The TDSO option has been running for some time and, at the first synchronization frame after ~the TDSO was initialized (corresponding to the action time associated with the Service Connect Message), the 31_BIT_PNNUM, which supplies the 24_BIT_PIN_NUM to drive the TDSO_STATE transitions (see was initialized and iterated as illustrated in Figure 4 once Severy frame period after that. Assume the 31_BIT_PN_NUM has a current value equal to Ox682dffOc and the current Markov chain is in the "Off" state.

B.2 Fundamental Channel TDSO process Assume that in this stated mode the TDSO is about to transmit frame number Oxab89efad on the Forward Fundamental Traffic Channel (F-FCH) to a mobile Sstation with the least-significant 32 bits of Public Long-Code Mask (PLCM) equal to 0x9F000307. Since the least significant 9 bits of (0xab89efad xor Ox2aaaaaaa) equal 0x107, and the least significant 9 bits of the PLCM are 0x0107, it is time to resynchronize the F-FCH TDSO process. The pseudorandom number generator associated with F-FCH is initialized with F-FRNG (FRNG for the Forward Fundamental Channel) set equal to the 31 leastsignificant bits of (0xab89efad or Ox2aaaaaaa) 0x01234507 as follows (see 0): 01234507 (F-FRNG: starting value for the Synchronization Frame) 3288cf26 (F-FRNG: 1st iteration) 33d7elb5 (F-FRNG: 2nd iteration) 22234caa (F-FRNG: 3rd iteration) 3b7e3e68 (F-FRNG: 4th iteration) After reinitialization, the Forward Fundamental Traffic Channel TDSO service option would compute yn(l) FRNG/128 0x3b7e3e68/128 Ox76fc7c. The least-significant 6 bits of yn(l), On, is equal to Ox3c, or 60. On mod B(n) (see Table 35) for the values of for RC3 B(n) 45) determines the byte offset in the circular buffer (where to begin copying data bits into blocks for the multiplex sublayer).

For the synchronization frame, the offset is taken with respect to the firstgenerated byte in the circular buffer; whereas for subsequent System Time frames, the byte address next to that of the last-packed byte from the previous frame serves as the reference. The TDSO always advances this pointer in the circular buffer according to the value of On, irrespective of whether any data bits were actually passed to the multiplex sublayer during that frame period as determined by the value of 24_-BiTPNNUM.

For the F-FCH, the TDSO generates 45 bytes through random number iterations. These bytes are put together, starting with the same 24-bit number that was used to determine the offset.

F-FRNG 0x3b7e3e68, F-FRNG 0x5d333c!5b, F-FRNG Ox4ebfaa2a, F-FRNG OxO93cd3ca, F-FRNG =0x78747782, F-FRNG 0x26523596, F-FRNG Ox~f3cle8l, F-FRNG 0x63f6d 7ff, F-FRNG =Ox62ded99e, F-FRNG 0x14a146c8, F-FRNG =Ox682dff~c, F-FRNG 0x23c3a243, F-FRNG OxOOdlef~d, F-FRNG 0x56a53ee6, F-FRNG Ox7ac49a7a, y Ox76fc7c Oxba6678 y x9d7f54 0x1279a7 Oxf~e8ef Ox4ca46b y.( 7 Oxbe783d Oxc7edaf Oxc5bdb3 y.(10) 0x29428d yJ(ll) 0x478744 y OxOla3de Oxad4a7d y Oxf58934 Each 24-bit number is written to the frame buffer in little-endian fashion.

So Ox76fc7c becomes the byte stream Ox7c Oxfc 0x76. The little-endian version of the next 24-bit number, 0xba6678, is written immediately after the first number.

The circular buffer to be used to generate data blocks for the F-FCH for the next 512 frames is thus organized as follows: 7c fc 76 78 66 ba 54 7f 9d a7 79 12 ef e8 fO 6b a4 4c 3d 78 be af ed c7 b3 Sbd c5 8d 42 29 fe 5b dO 44 87 47 de a3 01 7d 4a ad 34 89

O

0 Following the procedure outlined in Figure 4, the new pseudo-random number generator is as follows, assuming the current value of the PN generator for the TDSO state model is Ox682dff0c: c 31_BIT_PN_NUM (0x682dff0c a) mod m 0x23c3a243 24_BIT_PNNUM 31BIT_PN_NUM 7 x478744 4687684 As the value of 24 BI_ PN_NUM is less than the ONTHRESHOLD, the TDSO_STATE turns to ON and, therefore, TDSO shall pass a Rate 1 frame to the multiplex 0 sublayer during the current frame period.

The starting offset for the first frame in the 512-frame segment is given by On mod which, in this case, is 60 mod 45 15. Therefore, the TDSO will generate a Rate 1 (171-bit) frame that can be supplied to the mux sublayer. The frame will be comprised of 21 octets from the circular buffer beginning at the byte offset in the circular buffer followed by 3 zero bits as shown: 6b a4 4c 3d 78 be af ed c7 b3 bd c5 8d 42 29 fe 5b dO 44 87 47 '000' Since this frame is to be carried over the Fundamental Channel, the first 5 bits of the first octet are replaced by '00000', the CHANNEL ID code, and PDU_SEQ_NUM for the FCH as shown in Table 37 and Table 37. Therefore, the final data block passed to the multiplex sublayer is as follows: 03 a4 4c 3d 78 be af ed c7 b3 bd c5 8d 42 29 fe 5b dO 44 87 47 '000' For the next TDSO frame, the pseudo-random numbers yn(l) is as follows: F-FRNG yn(l) Ox0179fe8e Ox02f3fd Following the procedure outlined in Figure 4, the new pseudo-random number generator is as follows: 31_BIT_PN_NUM (0x23c3a243 a) mod m Ox00dlefOd 24_BIT_PN_NUM 31_BIT_PN_NUM 7 xla3de 107486 0 As the value of 24_BITrPN_NUM is less than the ON_THRESHOLD, the TDSOSTATE turns to ON and, therefore, TDSO shall pass a Rate 1 frame to the multiplex o sublayer during the current frame period.

The 6 least-significant bits of yn(1), On, is 0x3d 61. On mod 45 16 is used to indicate the byte offset in the circular buffer. The offset is taken with respect to the byte address next to the last packed byte from the frame generated in the C¢3 Cc previous 20 ms period, that is, with respect to the byte Oxde in the buffer.

C¢3 SThe TDSO service option will generate and supply a Rate 1 frame using 21 octets from the circular buffer followed by 3 zero bits. The complete data block looks like the following: 7f 9d a7 79 12 ef e8 fO 6b a4 4c 3d 78 be af ed c7 b3 bd c5 8d '000' After replacing the first 5 bits with '00000' corresponding to the data block header for FCH, the data block supplied to the multiplex sublayer, as a data block, is as follows: 07 9d a7 79 12 ef e8 fO 6b a4 4c 3d 78 be af ed c7 b3 bd c5 8d '000' The byte offset pointer advances to the byte immediately after Ox8d, that is, 42 for the next frame.

A while later, frame number Oxab89f052 is about to be generated for the Reverse Fundamental Traffic Channel. Since the least-significant nine bits of (0xab89f052 xor 0x55555555) equal 0x107, and the least-significant nine bits of the PLCM are 0x0107, it is time to resynchronize the Reverse Traffic Channel TDSO process. The associated pseudo-random number generator is initialized with F-RRNG set equal to the 31 least-significant bits of (0xab89f052 xor 0x55555555) Ox7edca507 as follows (see 0): 7edca507 (F-RRNG starting value for the Synchronization Frame) 47d6afa2 (F-RRNG: 1st iteration) 5fa4d986 (F-RRNG: 2nd iteration) 3fc51d78 (F-RRNG: 3rd iteration) 2611dlfd (F-RRNG: 4th iteration) The Reverse Fundamental Traffic Channel TDSO first computes RRNG /128 Ox26 1d 1fd/ 128 0x4c23a3. For the R-FCH, the TDSO generates 360 bits (two TDSO frames) through random number iterations. These bytes are put together, starting with the same 24-bit number that was used to determine the offset above.

F-RRNG Ox26ldlfd, F-RRNG OxSbfl4c9l, F-RRNG Ox3ed9f2bf, F-RRNG 0x56cff9d5, F-RRNG 0x701b3b79, F-RRNG =Ox~bddbe6f, F-RRNG OxObOl6f7f, F-RRNG OxOb3fOO7e, F-RRNG =0x553955f6, F-RRNG 0x273ab530, F-RRNG 0x7f4d766e, F-RRNG 0x369a7l0d, F-RRNG =0x5574287c, F-RRNG Ox3dOelOb8, F-RRNG 0x666bbf58, y 0x4c23a3 y 0xb7e299 y,()=Ox7db3eS y Oxad9ff3 0xe03676 y Oxl7bb7c Oxl6O2de y 0x167e00 y Oxaa72ab =0x4e756a Oxfe9aec 0x6d34e2 yJ(l 3 y ,(1 4 Ox7alc2l Oxccd77e The circular buffer to be used to generate data blocks for the R-FCH for the next 512 frames is thus organized as follows: a3 23 4c 99 e2 b7 e5 b3 7d f3 9f ad 76 36 eO 7c bb 17 de 02 16 00 7e 16 ab 72 aa 6a 75 4e ec 9a fe e2 34 6d 50 e8 aa 21 1c 7a 7e d7 cc--- The 31_BiTPNUM has gone through 164 iterations since the synchronization time for the Forward Traffic Channel was reached. The current value of the 32-BIL PN.NUM 0x4de9620.

Following the procedure outlined in Figure 4, the new pseudo-random number generator is as follows, assuming the current value of the PN generator for the TDSO state model is 0x~x4de9620: 31_BIT_PN_NUM (0x0x4de9620 a) mod m 0x3152115f O 24_BIT_PN_NUM 31_BIT_PN_NUM 7 0x62a422 4687684 ND 6464546 As the value of 24_BIT_PN_NUM is greater than the ON_THRESHOLD, the TDSOSTATE C stays in OFF and, therefore, TDSO shall pass a blank data block (0 bits) to the multiplex sublayer during the current frame period.

The starting offset for the first frame in the 512-frame segment is given by the 6 10 least-significant bits of yn(l), On mod which in this case is equal to 0x23 mod 45 or 19.

Even though no frame shall be built in this frame period, the pointer associated with the starting offset for the next frame shall be incremented by 19, that is, the reference byte address for the next frame in the circular buffer is that of byte 02 in the buffer.

For the next TDSO frame, the pseudo-random numbers yn(l) is as follows: F-RRNG yn(l) Ox2bdf5ef0 Ox57bebd Following the procedure outlined in Figure 4, the new pseudo-random number generator is as follows: 31_BIT_PN_NUM (0x3152115f a)mod m 0x2f28d45 24_BIT_PN_NUM 31BIT_PN_NUM 7 x5e51a 386330 As the value of 24_BIT_PN_NUM is less than the ON_THRESHOLD, the TDSO_STATE turns to ON, therefore, it shall pass a Rate 1 frame to the multiplex sublayer during the current frame period.

The 6 least-significant bits of yn(l), On, is Ox3d 61. On mod 45 16 is used to indicate the byte offset in the circular buffer. The offset is taken with respect to the byte address of byte 02 in the buffer as stored in the previous frame.

IL4 1 O The TDSO service option will generate and supply a Rate 1 frame using 21 octets from the circular buffer followed by'3 zero bits. The packet derived from O the circular buffer thus looks like this: 6d 50 e8 aa 21 1c 7a 7e d7 cc a3 23 4c 99 e2 b7 e5 b3 7d f3 '000' cHowever, the first 5 bits are to be replaced by '00000' for the FCH. Therefore, the data block supplied to the mux sublayer is: 09 50 e8 aa 21 c 7a 7e d7 cc a3 23 4c 99 e2 b7 e5 b3 7d f3 '000' The reference byte address for the next frame in the circular buffer is that of byte 9f in the buffer.

B.3 Supplemental Channel TDSO process Assume that in this stated mode the TDSO is about to transmit frame number Oxab89efad on the Forward Supplemental Channel (F-SCHO) to a mobile station with the least-significant 32 bits of PLCM equal to Ox9F000307. Since the leastsignificant nine bits of (Oxab89efad xor Ox2aaaaaaa) equal 0x107, and the least significant nine bits of the PLCM are 0x0107, it is time to resynchronize the F- SCHO TDSO process. The pseudo-random number generator associated with F- SCHO is initialized with S-FRNGO (FRNG for the Forward Supplemental Channel 0) set equal to the 31 least-significant bits of (0xab89efad xor Ox2aaaaaaa) 0x01234507 as follows (see 0): 01234507 (S-FRNGO: starting value for the Synchronization Frame) 3288cf26 (S-FRNGO: 1st iteration) 33d7elb5 (S-FRNGO: 2nd iteration) 22234caa (S-FRNGO: 3rd iteration) 3b7e3e68 (S-FRNGO: 4th iteration) After reinitialization, the Forward Supplemental Channel TDSO service option would compute yn(1) FRNG/128 0x3b7e3e68/128 Ox76fc7c. The leastsignificant 6 bits of yn(l), On, is equal to Ox3c, or 60. On mod B(n) (see Table for the values of for RC3 B(n) 762) determines the byte offset in the circular buffer from where to begin copying data bits into blocks for the multiplex sublayer.

For the synchronization frame, the offset is taken with respect to the ffirstgenerated byte in the circular buffer; whereas for subsequent System Time frames, the byte address next to that of the last-packed byte from the previous frame serves as the reference. The TDSO always advances this pointer in the circular buffer according to the value of On mod irrespective of whether any data bits were actually passed to the multiplex sublayer during that frame period as determined by the value of 24_NT_-PNNUM.

For the F-SCHO, the TDSO generates 762 bytes (two full-rate RC3 frames) through random number iterations. These bytes are put together, starting with the same 24-bit number that was used to determine the offset.

S-FRNGO 0x3b7e3e68, S-FRNGO 0x5d333c5b, S-FRNGO Ox4ebfaa2a, S-FRNGO Ox93cd3ca, S-FRNGO 0x78747782, S-FRNGO 0x26523596, S-FRNGO Ox5f3cle~l, S-FRNGO =Ox63f6d7ff, S-FRNGO Ox62ded99e, S-FRNGO 0x14a146c8, S-FRNGO 0x682dfff~c, S-FRNGO 0x23c3a243, S-FRNGO Oxdlef0d, S-FRNGO 0x56a53ee6, S-FRNGO Ox7ac49a7a, S-FRNGO Oxl79fe8e, S-FRNGO 0x70371d63, S-FRNGO 0x326a8823, S-FRNGO Ox700fcbbO, S-FIRNGO =OxldO~c94a, Ox76fc7c y Oxba6678 0x9d7f54 x1279a7 y ()Oxf~e8ef yJ(6) Ox4ca46b =Oxbe783d yj(S) =Oxc7edaf =Oxc5bdb3 yJ(10) 0x29428d yj(ll) 0x478744 y Oxla3de yJ(l4) Oxad4a7d y 0xf58934 yJ(16) Ox2f3fd yJ(17) OxeO6e3a yJ(18) 0x64d510 y.(19) Oxe~lf97 y 0x3a~b92 S-FRNGO 0x66e22828, S-FRNGO Ox9ba~edd, S-FRNGO =0x36f95428, S-FIRNGO 0x2b042a4a, S-FRNGO 0xle747656, S-FRNGO 0x7005l7b8, S-FRNGO 0x5e586a7c, S-FRNGO Ox7eb 72347, S-FRNGO 0x296d4b4f, S-FRNGO 0x466b44c8, S-FRNGO 0x2c70ca96, S-FRNGO 0x210454a5, S-FRNGO 0x23512d92, S-FRNGO 0x2686de5b, S-FRNGO =0x60703clf, S-FRNGO 0x687b48af, S-FRNGO Ox75elOebf, S-FRNGO Oxa~f5aOf, S-FRNGO =0x49619433, S-FRNGO 0x2548c5e8, S-FRNGO 0x4cb9l577, S-FRNGO Oxb3O5efl, S-FRNGO Oxl4abb67a, S-FRNGO 0x15590e30, S-FRNGO =0x9b27c43, S-FRNGO Ox24fcl7ae, S-FRNGO 0x2276b37a, S-FRNGO 0xlf012043, S-FRNGO Ox2edle9c, S-FRNGO 0xld749544, S-FRNGO 0x50f3b277, S-FRNGO 0x2f49cc26, y 0x13751dC y.( 23 Ox6df2a8 y,,(2 4 0x560854 Ox3ce8ec OxeOOa2f y OxbcbOd4 Oxfd6e46 y 0x52da96 0x8cd689 0x58e195 y 1 0x4208a9 y 1 0x46a25b Ox4dOdbc OxcOeO78 y OxdOf69l Oxebc2ld Oxl5leb4 0x92c328 0x4a9l8b y 0x99722a Oxl66Obd 0x29576c Ox2ab2lc y 0x1364f8 0x49f82f 0x44ed66 y WOW024 y Ox5da3d Ox3ae92a 0xale764 0x5e9398 S-FRNGO Oxl5f9eb~b, S-FRNGO =0x4ab62a72, S-FRNGO =Ox7d9cc8af, S-FRNGO 0x403b9996, S-FRNGO =Ox8eO67cc, S-FRNGO 0x44be86a1, S-F1RNGO =0x3878d749, S-FRNGO 0x57e1696, S-FRNGO =Oxl8fcd4ab, S-FRNGO =Ox7eee335d, S-FRNGO =0x486e5fc5, S-FRNGO 0x465la3a9, S-FRNGO =Oxl9cfdO5O, S-FRNGO =0xla75416d, S-FRNGO =Ox8la68ad, S-FRNGO Ox7dce3aO2, S-FRNGO =0x6e4299d4, S-FRNGO =0x568165d9, S-FRNGO =0x4945b5ed, S-FRNGO =Ox7fabOO2f, S-FRNGO x33994f 24, S-FRNGO Oxl6ladef3, S-FRNGO =Ox3e232edb, S-FRNGO Ox77d94bbb, S-FRNGO =Ox5afblf75, S-FRNGO Oxlcce68fd, S-FRNGO =0x334ec8d1, S-FRNGO =0x79622ba7, S-FRNGO 0xlc201f33, S-FRNGO =OxeO5bb2 1 S-IPRNGO 0x9a40391, S-IFRNGO 0x6ee62988, Ox2bf3d6 y 0x956c54 0xfb3991 0x807733 OxllkOcf 0x897d~d Ox7Oflae Oxafc2cl 0x3lf9a9 Oxfddc66 Ox9Odcbf y 1 0x8ca347 0x339fa0 yJ(66) 0x34ea82 0x1034d1 Oxfb9c74 0xdc8533 yJ(7O) OxadO2cb y 0x928b6b yJ(72) Oxff5600 0x67329e Ox2c35bd yJ(75) 0x7c465d yJ(76) Oxefb297 Oxb5f63e y7)= 0x399cdl y 0x669d9l y 0xf2c457 0x38403e OxlcOb7 0x134807 Oxddcc53 S-FRNGO 0x48b~d899, S-FRNGO 0x525c4a17, S-FRNGO =0x2904563f, S-FRNGO 0x5bba5722, S-FRNGO Ox26aea83a, S-FRNGO Oxi4a68bad, S-FRNGO =0x421c1572, S-FRNGO 0x41lc41146, S-FRNGO 0x2f4a2c65, S-FRNGO 0x2ea8b324, S-FRNGO 0x4589186a, S-FRNGO Ox2balfadO, S-FRNGO 0x17598411, S-FRNGO 0x75ed8410, S-FRNGO =0x3c7972ec, S-FRNGO 0x496802f8, S-FRNGO Ox4b9bOd6e, S-FRNGO 0x308ed789, S-FRNGO 0x71e87c46, S-FRNGO 0x56371216, S-FRNGO 0x39848e92, S-FRNGO Ox2dac3Obe, S-FRNGO =0x3b4215f, S-FRNGO Ox26fae5df, S-FRNGO 0x2209a777, S-FRNGO 0x27d18716, S-FRNGO Ox2cfbc9c6, S-FRNGO Ox467bfd3c, S-FRNGO 0x762e924a, S-FRNGO 0x6b8674e3, S-FRNGO 0x48641a3b, S-FRNGO 0x23f63c9e, 0x9l6lb1 0xa4b894 0x5208ac yJ(88) Oxb774ae y 0x4d5d50 yJ(9O) =0x294d17 yJ( 9 1) 0x84382a y,,(9 2 0x838892 0x5e9458 0x5d5166 y 0x8b1230 0x5743f5 0x2eb308 =OxebdbO8 y ,(9 9 0x78f2e5 y,,(100) 0x92d005 yJ(l0l) 0x97361a y,,(102) Ox6lldaf y,,(103) Oxe3dOf8 yJ(lO 4 Oxac6e24 yJ(lO5) =0x73091d yJ(1O 6 0x5b5861 y,,(10 7 =0x76842 y,,(10 8 y,,(10 9 0x44134e y,(110) Ox4fa3Oe y,,(lll) 0x59f793 yJ(ll 2 Ox8cf7fa y.(11 3 Oxec5d24 y,,(11 4 Oxd7Oce9 yJ(ll5) 0x90c834 yJ(ll6) 0x47ec79

IN

S-FRNGO =0x7b05bb83, S-FIRNGO 0x3559d48e, S-FRNGO Oxlc9ldlff, S-FRNGO =0x2971cb00, S-FRNGO 0x6dc68241, S-FRNGO 0x391blb5, S-FRNGO 0x5229e3e7, S-FRNGO =0x3c3l7cd5, S-FRNGO =Ox54faa2d2, S-FRNGO xl2d7b494, S-FRNGO 0xf906a36, S-FRNGO x522d0735, S-FRNGO xa3452b9, S-.FRNGO =0x7l22f4ea, S-FRNGO =Ox2dfd68ad, S-FRNGO 0x57e34d7l, S-FRNGO Oxbfl62cb, S-FRNGO 0x148d038d, S-FRNGO 0x35e42885, S-FRNGO 0x16204f67, S-FJRNGO Ox233cfe8a, S-FRNGO =0x796b2818, S-FRNGO Ox6al57dee, S-FRNGO =Ox28fecaab, S-FRNGO Ox6fabb593, S-FRNGO Ox72ldff2b, S-FRNGO 0xf5b9a95, S-?RNGO 0x4701b4l3, S-FIRNGO 0x40d56f dO, S-FRNGO Ox7c9felfO, S-ERNGO 0x64aa937b, S-FIRNGO Ox7ab8a3cle, y ,(11 7 0xf60b77 y ,(ll8) =Ox6ab3a9 y ,(1l9) 0x3923a3 y ,(l2O) 0x52e396 y,,(121) Oxdb~dO4 y ,(l22) 0x72363 y,,(123) 0xa453c7 y,,(1 24 0x7862f9 y,,(125) O xa9f545 y ,(126) x25af69 y,,(1 2 7 =Oxlf2Od4 y,,(128) y,,(129) xl468a5 yJ(l3O) 0xe245e9 y,,(131) yJ(l32) Oxafc69a y ,(133) 0x17e2c5 y,,(134) 0x291a07 y,,(135) =0x6bc851 y,,(136) 0x2c409e y,,(137) 0x4679fd y,,(138) 0xf2d650 yJ(l3 9 =Oxd42afb y,,(1 4 0) 02x5lfd95 yJ(l4l) Oxdf576b yJ(142) Oxe43bfe yJ(1 4 3) 0xleb735 y,,(1 4 4 0x8e0368 y,,(1 45 Ox8laadf yJ(I 46 Oxf93fc3 y,,(1 4 7 0xc95526 yj(l 4 8) Oxf57147 S-FRNGO 0x700e82c3, S-FRNGO Ox48abO9ae, S-FRNGO 0x5508a3c7, S-FRNGO 0x2a38896e, S-FRNGO =0x65c6aa69, S-FRNGO =0x55de07b2, S-FRNGO 0x63cb6328, S-FRNGO Ox3ddbOa47, S-FRNGO Ox777fdbOa, S-FRNGO Ox6bO~aadO, S-FRNGO 0x41117494, S-ERNGO Ox6Ofccleb, S-FRNGO Ox72lf5dOb, S-FRNGO 0x6915b7b5, S-FRNGO OxlOdOOlf9, S-FRNGO =0x48318b~e, S-FRNGO 0x2ca06929, S-FRNGO 0x575819a2, S-FRNGO 0x58fb077a, S-FRNGO 0x48a80839, S-FRNGO Oxfb3fb73, S-FRNGO =0x71414312, S-FRNGO =0x739a8cd4, S-FRNGO 0x2793ed97, S-FRNGO 0x60d368cd, S-FRNGO 0x57859c64, S-FRNGO 0x4de9620, S-FRNGO 003152115f, S-FRNGO 0x2f28d45, S-FRNGO 0x2l8ae86, S-FRNGO =0x2269e07d, S-FRNGO 0x55114031, y ,(l49) y,,(150) 0x915613 y ,(15l) Oxaall47 y,,(152) 0x,547112 y,(153) Oxcb8d54 y,,(154) =OxabbcOf y,,(155) 0xc796c6 y.(156) =0x7bb614 yJ(i57) =Oxeeffb6 y,,(158) 0xd60b55 yJ(159) 0x8222e9 y,,(160) =0xclf983 y,,(161) Oxe43eba y,1(162) Oxd22b6f y,,(163) 0x2la003 y,,(1 6 4 0x906316 y,,(165) =0x5940d2 y,,(166) OxaebO33 y,,(167) Oxblf6Oe y,,(168) 0x915010 yJ(l69) 0xlf67f6 y ,(l7O) 0xe28286 y,,(171) 0xe73519 y.(172) =Ox4f27db y,,(173) Oxcla6dl y.(174) OxafOb38 y,,(175) Ox9bd2c y,,(176) 0x62a422 y,1(1 7 7 y,,(178) 0x4315d y ,(l79) 0x44d3c0 y.(180) =0xaa2280 S-FRNGO 0x5f8d7c98, S-FRNGO Ox4leflO2a, S-FRNGO =0036065737, S-FRNGO 0x677ff79a, S-FRNGO 0x258d48c, S-FRNGO 0x15ea3488, S-FRNGO 0x431ed7f5, S-FRNGO 0xldf43840, S-FRNGO Qxc99Olld, S-FRNGO Oxlll~ld6l, S-FRNGO =0x4630d40b, S-FRNGO 0x2fb1422d, S-FRNGO Qxle6fbOdl, S-F1RNGO 0x36c178f3, S-FRNGO Ox57ebb59a, S-FRNGO Ox33dfbe8e, S-FRNGO =0x2657773d, S-FRNGO 0x385 55 9 75 S-FIRNGO 0x6b642d37, S-FRNGO =Ox7dd4acf5, S-FRNGO 0xl5a7495d, S-FRNGO 0x19c183c 6 S-FRNGO 0x6fb2495f, S-FIRNGO 0x21ef3543, S-FRNGO Ox5f9ld3lc, S-FRNGO =0x5ebb0448, S-FRNGO 0x4816438e, S-FRNGO Ox2dad449b, S-FRNGO 0x4a73338a, S-FRNGO 0x513ccf35, S-FRNGO Ox6f47ca3d, S-FRNGO Ox522ea3de, 131 y.(181) Oxbflaf9 y,,(182) 0x83de20 y,,(1 8 3 Ox6clcae y.(1 8 4 Oxceffef y ,(1 8 5 Ox4bla9 y,,(1 86 0x2bd469 y ,(1 8 7 Ox863daf y.(188) Ox3be87O y ,(18 9 0x193202 y,(1 9 0) =0x22303a y.(1 9 1 0x8c6la8 y.(1 92 0x5f6284 y ,(1 93 Ox3cdf6l y.(1 9 4 0x6d82fl y,,(1 9 5 Oxafd76b y.(1 9 6 Ox67bf7d y.(1 9 7 =0x4caeee y.(1 9 8 Ox7Oaab2 y.(1 99 Oxd6c85a yn,( 200 =Oxfba959 y.( 2 01) 0x2b4e92 y.(20 2 0x338307 0xcdf6492 y 2

O

4 Ox43de6a y ,(2O 5 Oxbf23a6 y.( 2 0 6 0xbd7608 207 0x902c87 y,( 2 08) 0x5b5a89 y.(20 9 0x94e667 y,( 2 10) 0xa2799e y 2 ll) Oxde8f94 y 2 1 2 0xa45d47

IN

S-FRNGO 0x74086df8, S-FRNGO =Ox556bfO4b., S-FRNGO Ox2l6cf7bd, S-FRNGO =Ox78fcaa6f, S-FRNGO 0xl4199b77, S-FRNGO Oxld2dabfO, S-IFRNGO 0x21732887, S-FRNGO =0xf69c839, S-FRNGO 0x69d8le16, S-FRNGO =Ox6b9f6ca3, S-FRNGO 0x2f957888, S-FRNGO Ox7elc4llf, S-FRNGO 0x70f79ae7, S-FRNGO Oxfdaeda2, S-FRNGO Ox6e272ecf, S-FRNGO 0x4e725088, S-FRNGO 0x330538f4, S-FRNGO 0xlbde3557, S-FRNGO Oxl97ffl~c, S-FRNGO Oxleaa57e8, S-FRNGO 0x41715012, S-FRNGO =Ox763fef4e, S-FRNGO Ox5f 782688, S-FRNGO Ox4929dbaf, S-FRNGO Ox5bl5e3af, S-FRNGO 0x7a1724e0, S-FRNGO 0x5762cbf, S-FRNGO 0x1173b266, S-FRNGO 0x42c54f7d, S-FRNGO Ox27e5b9ca, S-FRNGO =0x5b08913c, S-FRNGO 0xf7728d5, y,,(213) Oxe8lOdb y ,(2l4) Oxaad7eO y,,(215) Ox42d9ef y,,(216) 0xflf954 y,,(217) 0x283336 yJ(2l8) 0x3a5b57 y ,(2l 9 0x42e651 yJ(22O) Oxled39O y,,(221) Oxd3bO3c Oxd73ed9 yJ(223) Ox5f2afl y,,(224) 0xfc3882 y,,(995) yJ2)= y ,(2 2 7 2 2 8) Ox9ce4al 0x660a7l y.(230) flx37bc6a yJ(23l) Ox32ffe2 y.(232) Ox3d54af y,,(233) 0x82e2a0 Oxec7fde yJ3)= OxbefO4d y ,(236) 0x9253b7 y.(23 7 Oxb62bc7 0xf42e49 yJ(239) Oxaec59 y ,(24O) 0x22e764 y ,(24l) 0x858a9e y,,(24 2 Ox4fcb73 y ,(24 3 0xb61122 S-FRNGO Ox58i9bfel, y,,(245) 0xb0337f __S-FRNGO =0x28479f7, y,,(246) 0x508f3

C.)

IND S-FRNGO =0x47278d6a, y,,(248) Ox8e4fla S-FRNGO 0x75b54ea4, y,,(249) =Gxeb6a9d S-FRNG0 0x523e2d5b, y ,(25O) 0xa47c5a S-FRNGO 0x7013db8b, y,,(251) 0xe027b7 S-FRNG0 0x27b2bc29, y,,(252) =0x4f6578 S-FRNGO 0x475f3c1b, y,,(253) Ox8ebe78 S-FRNGO 0x3d633538, y,,(254) =0x7ac66a Each 24-bit number Yn(k) is written to the frame buffer in little-endian fashion.

So Ox76fc7c turns into the byte stream Ox7c Gxfc 0x76. The little-endian version of the next 24-bit number, 0xba6678, is written immediately after the first number.

The circular buffer to be used to generate da-ta block(s) for the F-SCH for the next 512 frames is thus organized as follows: +7c fc 76 78 66 ba 54 7f 9d a7 79 12 ef e8 fO 6b a4 4c 3d 78 be af ed c0 b3bdc5 8d 4229 fe5b d044 87 47de a301 7d4a ad34 89 f5 fdf302 3a 6e e 10 d5 64 97 if eO 92GOb 3a 50 c4 cd Id 75 13 a8 f2 6d 54 08 56 ec e8 3c 2f Oa eQ d4 bO bc 46 6e fd 96 da 52 89 d6 8c 95 el 58 a9 08 42 a2 46 bc Gd 4d 78 eQ cO 91 f6 dO id c2 eb b4 le 15 28 c3 92 8b 91 4a 2a 72 99 bd 60 16 6c 57 29 1c b2 2a f8 64 13 2f f8 49 66 ed 44 40 02 3e 3dda05 2a e93a 64e7 al98 93 5ed6 f32b 546c 959139 fb3377 cf cO11 Od 7d89 aefl 70 2d fe Oa a9 f9 31 66 dc fd bf dc 90 47a3 8c aO 9f 33 82 ea 34 dl 34 10 74 9c Lb 33 85 dc cb 02 ad 6b 8b 92 0056 ff 9e 32 67 bd 35 2c 5d 46 7c 97 b2 ef 3e f6 b5 dl 9c 39 91 9d 66 57 c4 f2 3e 4038 b7 c00107 48 13 53 cc dd bi 6191 94 b8a4 ac08 52 ae74b7 50 5d 4d 17 4d29 2a 38 842288 8358 94 5e6651 5d 3012 8b f54357 08 b3 2e 08 db eb e5 f2 78 05 dO 92 la 36 97 af id 61 f8 dO e3 24 6e ac Id 09 7361 58,5b 42 68 07 cb f5 4d 4e 13 44 Ge a3 4f 93 f7 59 fa f7 8c 24 5d ec e9 Oc dV 34 c8 90 79 ec 47 77 Ob f6 a9 b3 6a a3 23 39 96 e3 52 04 8d db 63 23 07 c7 53 a4 f9 62 78 45 f5 a9 69 af 25 d4 20 if Oe 5a a4 68 14 e9 45e2 dlfa5b 9ac6 afc5 e217 07la 29 51c8 6b9e 402c _fd 79 46 50d6f2 fb2ad4 95 fd 516b57 df fe3b e4 35b7le 68 038e

C.)

IND ~54 8d cb Ofbc abc6 96C714b6 7bb6 ff ee55Ob d6e9 22 8283 f9 c ba3ee4 6f 2b d2 03 a211663 90d2 40 5933 bOaeOe f6 b110 5091 f6 67 if 86 82 e2 19 35 e7 db 27 4f dl a6 cl 380Ob af 2c bd 09 22 a4 62 lae505 d 3104cO d3 44 8022 aaf9la bf 20de 83aelc 6c efff ce a9 bl 04 69d4 2b af 3d 86 70e8 3b 02 32 19 3a30 22 a861 8c 8462 61tf 3c fl 826d 6bd7 af7d bf67 eeae 4cb2 aa 705a c8d6 59a9 fb r- ~10 92 4e 2b 078333 9264 df6ade 43a623 bf08 76 bd872c 90 895a 67 e6 949e 79 a2948fde 475d a4db10 e8 eOd7 aa efd942 54f9 fl 36 33 2857 Sb 3a 51 e6 42 90 d3 le 3c bO d3 d9 3e d7 fl 2a Sf 82 38 fc ef el cib b5 if 5d 4e dc al e4 9c 71 Oa 66 6a bc 37 e2 ff 32 af 54 3d aO e2 82 de 7f ec 4d fO be b7 53 92 C 2b b6 49 2e fM 59 ec Oa 64 e7 22 9e 8a8573 cb4f 22 11 b651 eele 7f33bOf3 08 0590 c6 8ela 4f8e 9d 6a eb 5a 7c a4 b7 27 eO 78 65 4f 78 be 8e 6a c6 7a-4 Following the procedure outlined in Figure 4, the new pseudo-random number generator is as follows: 31_BiT_PNNUM (Qx682dff~c a) mod m =0x23c3a243 24_BiT_PNs_NJM 31_BITPN_NUM >>7=0x478744 =4687684 As the value of 24.B1TJ'I'NNum is less than the ON_-THRESHOLD, the DsoQsTATE turnis to ON and, therefore, TDSO shall pass two Rate 1 frame to the multiplex sublayer during the current frame period.

The starting offset for the- first frame in the 512 frame segment is given by On mod which in this case is 60 mod 762 =60. Therefore, the TDSO will generate two Rate 1 (170-bit) date blocks that are supplied to the multiplex sublayer. Each data block is comprised of 21 octets from the circular buffer beginning at the 60th byte offset in the circular buffer followed by 2 zero bits as showmv c4 cd id 75 13 a8 f2 6d 54 08 56 ec e8 3c 2f Oa eO d4 bO bc '00' 46 6e fd96 da52 89d6 8c95 el58 a9 0842 5ba246 bcOd 4d'00'* The first 5 bits of each generated PDU, however, will be masked by 2 bits O representing the CHANNELID, that is, 10 for F-SCHO followed by 3 bits to Sdesignate the PDU sequence number within the physical layer SDU ('000' for first data block and '001' for the second). Therefore, the two data blocks that are passed to the multiplex sublayer look like the following: PDU1->80 c4 cd ld 75 13 a8 f2 6d 54 08 56 ec e8 3c 2f Oa eO d4 bO bc '00' PDU2->8e 6e fd 96 da 52 89 d6 8c 95 el 58 a9 08 42 5b a2 46 bc Od 4d '00' O For the next frame, however, the byte offset pointer advances to the byte immediately after 4d, that is, 78.

Using the TDSO C.1 Introduction This annex outlines the procedure for conducting a TDSO test and a method for computing frame error rates.

C.2 Conducting a TDSO test A TDSO test may be conducted at a base station using the following procedures: 1. Start a TDSO call (or clear the counters of an existing call).

To conduct a TDSO call with a random data source, send a Service Option Control Message control directive with DATA_SOURCE field set to '001' and the CLEARCOUNTERS field set to for the particular physical channel.

Wait for the test interval to elapse.

Direct the mobile station to make a copy of the TDSO counters.

Wait for the forward synchronization and reverse synchronization frame after the action time to occur.

a Retrieve the values of the copied counters from the mobile station and compute the FERs.

A call is started by negotiating the TDSO (see 0) and initializing and connecting the service option. The service option counters are cleared at initialization, or r 136 8 could be cleared explicitly by the base station by sending a control directive c while a TDSO call is in progress.

O The duration of a test should correspond to an integral number of segments C (see The mobile station's processing of the control directive (see 0) enforces this test duration.

The base station sends a Service Option Control Message directing the mobile c station to copy the received and transmitted TDSO counters to buffers at the next Forward and Reverse Traffic Channel synchronization frames. This provides a synchronized snapshot of all the TDSO counters for accurate P 10 calculations of FERs.

SThe base station sends Service Option Control Messages to request counter values to be retrieved from the copied buffer. These counter values are used in frameerror rate and bit-error rate calculations.

C.3 Computation of FERs C.3.1 FER computation on the FCH and DCCH The FER on the Forward Fundicated Traffic Channel is given by the following calculation: FERRate 1 (Forward) 1 (TDSO_El_R1m TDSO_ENRNm)/(TDSO_E1_Tlb TDSO_EB TBb) where counters in the mobile station are denoted by a subscript m, and counters in the base station are denoted by a subscript b.

The FER of the Reverse Fundicated Traffic Channel is given by the following calculation: FERRate 1 (Reverse) 1 (TDSO_E1_Rlb TDSO_EN_RNb)/(TDSO_El_T1m TDSOEB TBn,) where counters in the mobile station are denoted by a subscript m, and counters in the base station are denoted by a subscript b.

The number of dim-and-burst frames and the number of blank-and-burst frames are not used in the FER calculations described above.

The values of the base station transmit counter TDSO_E1_TIb, TDSQEB-TBb can be estimated by summing the values of the corresponding mobile station counters O for received frames as follows: TDSO_E1_Tb TDSO_E1Rm TDSO_E1.ROm TDSO_E1_RFLm TDSO_E1_REm TDSO_E1_RERRm TDSOEBTBb TDSO_ENRNm TDSOEN-ROm The values of the mobile station transmit counter TDSOEL.T1m, TDSOEBTBm can be estimated at the base station by summing the values of the corresponding base station counters for received frames as follows: TDSO_E1 T1m TDSO_ElRib TDSOEl ROb TDSOE1_RFLb TDSO_E1_REb +TDSOE1_RERRb TDSOEBTBm, TDSOENRNb TDSO_ENROb C.3.2 FER computation on the SCH The FER of Nx9.6 or Nx14.4 frames on the Forward Supplemental Channel is given by the following calculation: FERRate Nx9.6 Or Nx14.4 (Forward) 1 (TDSO ENxRNxm TDSOEBRBm) /(TDSO_ENx_TNXb+ TDSO_EBTBb) where counters in the mobile station are denoted by a subscript m, and counters in the base station are denoted by a subscript b.

The FERs of Nx9.6 or Nx14.4 frames on the Reverse Fundicated Traffic Channel are given by the following calculation: FERRate Nx9.6 or Nx14.4 (Reverse) 1 (TDSOENxRNxb TDSQEBRBb)/ (TDSOENxTNxm+ TDSOEBTBm) where counters in the mobile station are denoted by a subscript m, and counters in the base station are denoted by a subscript b.

The values of the base station transmit counter TDSOENxifNx 2 TDSOEBTBb can Cl be estimated by sumrming the values of the corresponding mobile station o counters for received frames as follows: TDSOENx(_Thxb =TDSOENxRNxm TDSOENx REm TDSOENxRERRm, TDSQEBJBb =TDSOEB RBm TDSOEB-ROm c-iThe values of the mobile station transmit counter TDSO ENxJTNxn-, TDSCLEB~jBm can be estimated at the base station by summing the values of the corresponding base station counters for received frames as follows: TDSO_ENxTNxm= TIDSOENx_-RNxb TDSO_ENx-REb TDSOENxRERRb, TDSO-EBTBm =TDSOEB RBb TDSOEB.ROb CA4 PER computation on SCH The PER of Rate la, Rate 1b, Rate 2, and Rate 3 frames on the Forward Supplemental Traffic Channel is given by the following calculation: PERRate 1,a (Forward) =1 TDSOEla-Rlam,/TDSOE1a -Tlab PERRate lb (ForwVard) 1 -TDSO_Elb Rlbm,/TDSOlb-Tlbb PERRate 2 (Forwqard) 1 TDSOE2,, TDSOE2_T2b PERRate 3 (Forward) =1 TDSOE3 R3m,/TDSC)_E3_T3b where counters in the mobile station are denoted by a subscript m, and counters in the base station are denoted by a subscript b.

The PER of Rate la, Rate 1b, Rate 2, and Rate 3 frames on the Reverse Supplemental Traffic Channel is given by the following calculation: PERRate la (Reverse) =1 TDSOEla Rlab/TDSQElaTiamn PERRate lb (Reverse) 1 TDSOElb-Rlbb/TDSOElbiITlbm PERp,,te 2 (Reverse) 1 TDSO_-E2_R2b /TDSOE2JT2m, PERRateS (Reverse) 1 TDSOE3_R3b /TDSO-E2-T2m, where counters in the mobile station are denoted by a subscript m, and

C.)

IND The values of the base station transmit counters TDSCLElaJTlab, TIJSOElbTlbb, -msoE2m,, and TDsoE3_T3b can be calculated by summing the values of the corresponding mobile station counters for received frames as follows: TDSOElaTiab TDSO_-Ela_-Riam TDSOElaRERRM TDSOElaREm, TDSOElbTlbb =TDSOElbRlbm TDSOElbRERRm TDSOElbREm, C~1TDSOE2_T2b TDSOE2 R2mn TDSOE2 RERRm TDSOJE2_REm' TDSO-E3-T3b =TDSOE3 R3m TDSO_33 RERRm TDSOJE33Em The values of the mobile station transiut counters TDSCLEaTaav TDsckEibJ-ibm, TDsoE2_Tnm, and TDsoE3Jnm can be. calculated by summing. the values of the corresponding base station counters for received frames as follows: TDSO_ElaTiam =TDSO_ElaRiab TDSOElaRERRb TDSOElaREb, TDSOElbTlbm TDSOElbRlbb TDSOElbRERRb TDSOElbREb, TDSO.E2ff..2m TDSOE2 R2b TDSOE2-RBRRb TDSOE2_REb, TDSQ...M_.T3m TDSOE3 R3b TDSOE3 RERRb TDSOE3-REb PER computation on the FCH and DCCH with 5 ms frame length The PER on the Forward Fundicated Traffic Channel is given by the following calculation: Let be the number of good 5 ins. frames received in the mobile station and Tb be the total numnber of 5 ms. frames transmitted by the base station during the test period, then FERprtI (Forward) 1 (R /Tb) where counters in the mobile station are denoted by a subscript m, and counters in the base station are denoted by a subscript b.

The PER on the Reverse Fundicated Traffic Channel is given by the following calculation: 14U O Let Rb be the number of good 5 ms frames received in the base station and Tm Sbe the total number of 5 ms frames transmitted by the mobile station during the O test period, then \O FERRate 1 (Reverse) 1 (Rb/Tm) where counters in the mobile station are denoted by a subscript m, and counters in the base station are denoted by a subscript b.

O3 Both Rm and Tm can be derived from the values of the mobile station counters MUXI_FOR_FCH_5_ms) retrieved in the 5 ms Frame Received Counters C Response and 5 ms Frame Transmitted Counters Response, respectively. For 010 example, for a 5 ms DCCH using Multiplex Option 0x01, Rm can be calculated C as the difference of the values of TDSO_MUX1 5ms_R1 at the beginning of the first TDSO frame and at the end of the last TDSO frame during the test.

Similarly, both Rb and Tb can be derived from the values of the base station counters. For example, Rb can be calculated as the difference of the values of the corresponding counter in the base station at the beginning of the first TDSO frame and at the end of the last TDSO frame during the test.

No text.

Calculating p and q Based on D and B Given the transition probabilities p and q, the average frame activity and the average burst length can be calculated based on the following equations: D (Equation 1) B 1/p (Equation 2) However, to inversely calculate p and q based on the desired D and B, cautions have to be taken since D and B are dependent on each other and some combinations cannot be achieved as explained below: From Equation 1 and Equation 2, D Bq/(l+Bq) (Equation 3) B (Equation 4) Equation 3 shows that given a fixed B, D varies from 0 to when q varies from 0 to 1. Similarly, Equation 4 shows that given a fixed value of D, B varies from to infinity.

O For example, if B is set to 2, D has to be smaller than 2/3. As a result, the frame activity can never get higher than 2/3 when B is set to 2. Similarly, if D is set to 7/10, B has to be greater than 7/3.

e¢3 Cc The corresponding valid values of p and q can be calculated from Equation 1 and e¢3 C Equation 2 given a valid pair of D and B.

The foregoing description of the preferred embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without the use of the inventive faculty. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

It will be understood that the term "comprise" and any of its derivatives (eg.

comprises, comprising) as used in this specification is to be taken to be inclusive of _0 features to which it refers, and is not meant to exclude the presence of any additional features unless otherwise stated or implied.

Claims (27)

1. A method for testing a plurality of channels under flexible operating 0 conditions in a wireless communication system including: INO defining values for a set of test parameters for each of the plurality of channels to be tested; and Cc, e testing each of the plurality of channels, operating under the flexible conditions, in accordance with respective values defined for the set of test parameters. 0

2. The method of claim 1, wherein the plurality of channels have two or more different frame lengths.

3. The method of claim 1 or 2, wherein the plurality of channels have frame lengths selected from the group consisting of 5 msec, 20 msec, 40 msec, and 80 msec.

4. The method of any one of claims I to 3, wherein the plurality of channels include at least one forward traffic channel and at least one reverse traffic channel.

5. The method of any one of claims 1 to 4, further including: generating data blocks for transmission over a plurality of frames on the plurality of channels, wherein each data block includes a header that identifies the particular channel on which the data block is transmitted.

6. The method of any one of claims 1 to 5, wherein each traffic channel to be tested is associate with a respective sequence of test data bits.

7. The method of any one of claims 1 to 5, wherein each traffic channel to be tested is associate with a respective average frame activity.

8. The method of any one of claims I to 5, wherein each traffic channel to be tested is associate with a respective average burst length.

9. The method of any one of claims 1. to 8, further including: 0 maintaining a two-state Markov chain to represent a transmission state for (N each of the plurality of channels, wherein the two-state Markov chain for each O channel includes an ON state signifying transmission of test data on the channel and an OFF state signifying no transmission of test data on the channel. e¢3 f 10. The method of claim 9, further including: Smaintaining one or more pseudo-random number generators to determine transitions between the ON and OFF states of Markov chains for the plurality of channels.

11. The method of claim 10, wherein one pseudo-random number generator is maintained for each set of one or more channels having same frame length.

12. The method of claim 11, wherein a first pseudo-random number generator is maintained for one or more channels having frame length of 20 msec and a second pseudo-random number generator is maintained for one or more channels having frame length of 40 msec or 80 msec.

13. A method for testing a particular channel in a wireless communication system, including: sending from a first entity to a second entity a first message having included therein one or more proposed values for one or more parameters for testing the particular chamnel; and receiving from the second entity a response message rejecting or accepting the one or more proposed values sent in the first message.

14. The method of claim 13, wherein the response message includes one or more alternative values for one or more parameters rejected by the second entity. The method of claim 13 or 14, further including: Ssending to the second entity a second message having included therein one or more values for one or more parameters rejected by the second entity. O

16. The method of any one of claims 13 to 15, wherein the first entity is a remote terminal and the second entity is a base station in the communication system: e¢3 e¢ at least one buffer operatively coupled to the at least one generator, each e¢3 buffer configured to store a respective generated sequence of data bits, and wherein a plurality of data blocks are formed for transmission over a plurality of time intervals on a particular channel, and wherein each data block includes at least a portion of a particular sequence of data bits from a particular buffer.

17. In a wireless communication system in which a plurality of frames are transmitted, a method for attaining a long-term average value on a duty cycle using a two-state Markov chain, the method including: driving on/off transitions of a test data service option (TDSO) process with a first pseudo-random number generator during a frame period if the frame period is a first length in time; and driving the on/off transitions with a second pseudo-random number generator during the frame period if the frame period is either a second length in time or a third length in time.

18. The method of claim 17, wherein the first and second pseudo-random number generators provide 24-bit pseudo-random numbers.

19. The method of claim 17 or 18, wherein the first length in time is 20 msec. The method of any one of claims 17 to 19, wherein the second length in time is msec and the third length in time is 80 msec.

21. The method of any one of claims 17 to 20, wherein if the frame period is equal O 0 to either the second length in time or the third length in time, the frame is a supplemental channel. 0

22. The method of any one of claims 17 to 21, wherein the long-term average value is configurable.

23. A method of exchanging test parameter values between a remote terminal and a base station in a wireless communication system, the method including: O sending proposed test parameter values from the remote terminal to the base station; and receiving a service option control message from the base station rejecting or negatively acknowledging the proposed test parameter values.

24. A method of constructing a circular buffer storing a plurality of maximum- rate frames transmitted on a particular channel under flexible operating conditions in a wireless communication system, the method including: constructing data for the circular buffer from iterations of a pseudo-random number generator a plurality of times for each test interval, wherein the data is to be transmitted under flexible operating conditions; and using a set of bits from a number generated by the pseudo-random number generator to indicate a byte offset to determine a starting position in the circular buffer from which to build one or more data blocks for a particular frame period.

25. The method of claim 24, wherein the pseudo-random number generator is a

31-bit pseudo-random number generator. 26. The method of claim 24 or 25, wherein the set of bits is obtained by extracting 24 most significant bits of number generated by the pseudo-random number generator, and extracting six least significant bits of the 24 most significant bits. 27. The method of any one of claims 24 to 26, wherein the test interval is defined 0to coincide with a synchronization frame of the channel. c, O 28. The method of any one of claims 24 to 27, wherein the test interval has a IND duration of 10.24 seconds. 29. A method as claimed in claim 1, substantially as herein described with reference to the accompanying drawings. 30. A method as claimed in claim 13, substantially as herein described with reference to the accompanying drawings. 31. A method as claimed in claim 17, substantially as herein described with reference to the accompanying drawings.

32. A method as claimed in claim 23, substantially as herein described with reference to the accompanying drawings.

33. A method as claimed in claim 24, substantially as herein described with reference to the accompanying drawings.

34. A method substantially as herein described with reference to any one of the embodiments of the invention illustrated in the accompanying drawings.

35. A transmitting entity substantially as herein described with reference to any one of the embodiments of the invention illustrated in the accompanying drawings.