3GPP51.010-1Mobile Station (MS) conformance specificationPart 1: Conformance specificationTS
For lower layer tests the following basic format for tests is used:
This subclause provides, if necessary, a definition of the feature/function being tested and the applicability of the test to different MS (e.g. speech only, data only etc.). The applicability information in this clause is informative. The normative applicability information is in 51.010-2.
*.*..*.2 Conformance requirement
This subclause details the core specification requirements being tested and includes any necessary core specification references.
*.*..*.3 Test purpose
This subclause details the purpose of the test.
*.*..*.4 Method of test
*.*..*.4.1 Initial conditions
If present this subclause defines the initial conditions to be established before running the test.
This subclause details the test procedure.
*.*..*.5 Test requirements
This subclause details the conditions to be met for successful completion of the test.
However for the higher layer tests, in general, a slightly modified format, as described below, is used:
This subclause provides, if necessary, a definition of the feature/function being tested and optionally the applicability of the test to different MS (e.g. speech only, data only etc.). The applicability information in this clause is informative. The normative applicability information is in 51.010-2.
*.*..*.1 Conformance requirement
This subclause details the core specification requirements being tested. Normally this is a direct quote from the core specification. In some cases due to the core specification structure it is hard to find a direct quote, then the conformance requirement can be a summary of the core specification requirements.
This subclause gives the core specification number and subclause of the conformance requirement.
*.*..*.2 Test purpose
The test purpose describes the purpose of the test i.e. what shall be tested. The test purpose must be justified by the conformance requirement. The complete conformance requirement needs not to be tested i.e. the test purpose can be a subset of the conformance requirement but not vice versa.
*.*..*.3 Method of test
For every test initial conditions for both the System Simulator and the Mobile Station are given. Normally the System Simulator simulates a network with one or several cells and all necessary channels to set up a network. The network set-up that is used in different sections of this specification varies but is normally defined in a default section that applies for a certain test. In each test is only specified the deviations from the default network set-up.
If a test contains several test procedures or if a test sequence is repeated with an execution counter then the initial conditions shall be re-established before each execution.
Related PICS/PIXIT statement
For every test the related PICS/PIXIT statements that are necessary for performing the test are given.
Foreseen final state of the MS
This subclause is optional. If included the text is informative i.e. non-normative and does not contain a description of verifications to be performed.
This subclause describes the test procedure. The text is non-normative.
Maximum duration of the test
This is a rough estimate of the time to run the test sequence. If the last step of the test sequence is not passed within this time the test has failed. The time shall be long enough to guarantee that all correctly implemented MS will pass the test but not unnecessarily long since this would increase testing time if the test fails.
This subclause defines the exact test steps and the verifications to be performed in the test. The subclause is normative and gives requirements for the MS behaviour.
The expected sequence specifies the actions in numbered steps in a tabular form. In the column "direction", "SS -> MS" denotes a message sent from the SS to the MS, i.e. downlink. "MS -> SS" denotes a message sent from the MS to the SS i.e. uplink. "SS" denotes an action at the SS and "MS" denotes an action at the MS (e.g. interaction with the user or higher layers). The column "message" defines the messages to be sent from the SS or expected by the SS. The "comments" column contains further normative information e.g. message parameters or timing requirements.
In some cases, different alternative behaviours are possible in a test. Then test steps in alternative sequences are numbered as:
"A n", "A n + 1",…,"A n + k";
"B n", "B n + 1",…,"B n + l";
"C n", "C n + 1",…,"C n + m";
etc. (n, m, l, k integers > 0).
In some cases the complete set of test steps is to be repeated with minor variations. In this case an execution counter is used and the following text is included "The test sequence is repeated for k = 1 … n."
Unless specified in the test sequence there are no timing requirements on the uplink messages except maximum duration of the test. The System Simulator shall send the next downlink message "immediately" after the previous message unless something else is specified in the test sequence. "Immediately" means as fast as the performance of the System Simulator allows, i.e. without any delays.
The Message Type of all uplink messages shall be checked . If the value of a parameter of an uplink message is specified in a test, the SS shall check the value. If the value is not specified, the SS shall not check the parameter unless stated otherwise. If an optional field or Information Element is not indicated for the uplink – unless specified otherwise -, it may be included or not.
Specific message contents
This subclause specifies the content of all downlink messages unless they are specified in a referenced default section. Then only the deviations from the default messages are specified. All optional fields or optional Information Elements of a downlink message that shall be included have to be specified otherwise they shall not be included.
Content of uplink messages that shall be checked can also be specfied in this subclause.