-
Notifications
You must be signed in to change notification settings - Fork 0
/
OMA-Template-EnablerTestSpec.html
836 lines (833 loc) · 31.4 KB
/
OMA-Template-EnablerTestSpec.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
<!DOCTYPE html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Enabler Test Specification for [EnablerName]</title>
<meta charset="UTF-8">
<script src="http://openmobilealliance.github.io/Tools/builds/respec-oma-common.js" async class="remove"></script>
<script class="remove">
var respecConfig = {
// for editor use
docType: "ETS", // options are BASE, RD, AD, TS, SUP, ETS, ORG
subtitle: "File_Name",
shortName: "shortName",
otherLinks: [{
key: "Other Link",
data: [{
value: "Link Name",
href: "#location"
}]
}],
editors: [{
name: "Editor Name",
url: "http://example.com/",
company: "Editor Company",
companyURL: "http://example.org/",
mailto: "[email protected]",
note: "editor note"
}],
authors: [{
name: "Author Name",
url: "http://example.com/",
company: "Author Company",
companyURL: "http://example.org/",
mailto: "[email protected]",
note: "author note"
}],
interactiveLinks: [{
name: "Link Name",
description: "Link Description",
uri: "http://example.com/",
},{
name: "Second Link Name",
description: "Second Link Description",
uri: "http://example2.com/",
}],
// for staff only
specStatus: "DRAFT", // options are Draft, Candidate, Approved, Historic
publishDate: ""
};
</script>
</head>
<body><!-- start table of content & table of figures -->
<section id="toc"></section>
<section id="tof"></section>
<section id="tot"></section>
<!-- /end table of content & table of figures -->
<p><br>
</p>
<!-- start scope -->
<section>
<h2>Scope</h2>
<p>This document describes in detail available test cases for <Enabler name and version, insert hyperlink to specification pages>.</p>
<p>The test cases are split in two categories, conformance and interoperability test cases.</p>
<p>The conformance test cases are aimed to verify the adherence to normative requirements described in the technical specifications.</p>
<p>The interoperability test cases are aimed to verify that implementations of the specifications work satisfactory.</p>
<p>If either conformance or interoperability tests do not exists at the creation of the test specification this part should be marked not available.</p>
</section>
<section>
<h2>New Test Section</h2>
<p>paragraph with some text.</p>
</section>
<!-- end scope -->
<p><br>
</p>
<!-- end scope -->
<p><br>
</p>
<!-- end scope -->
<p><br>
</p>
<!-- end scope -->
<p><br>
</p>
<!-- end scope -->
<p><br>
</p>
<!-- end scope -->
<p><br>
</p>
<!-- end scope -->
<p><br>
</p>
<!-- end scope -->
<p><br>
</p>
<!-- end scope -->
<p><br>
</p>
<!-- end scope -->
<p><br>
</p>
<!-- end scope -->
<p><br>
</p>
<!-- start terminology and conventions -->
<section>
<h2>Terminology and Conventions</h2>
<section><!-- start conventions -->
<h2>Conventions</h2>
<p>The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in [[!RFC2119]].</p>
<p>All sections and appendixes, except “Scope” and “Introduction”, are normative, unless they are explicitly indicated to be informative.</p>
<p>The following numbering scheme is used:</p>
<pre> <strong>xxx-y.z-con-number</strong> where:
xxx Name of enabler, e.g. MMS or Browsing
y.z Version of enabler release, e.g. 1.2 or 1.2.1
"con" Indicating this test is a conformance test case
number Leap number for the test case
</pre>
<p>Or</p>
<pre> <strong>xxx-y.z-int-number</strong> where:
xxx Name of enabler, e.g. MMS or Browsing
y.z Version of enabler release, e.g. 1.2 or 1.2.1
"int" Indicating this test is a interoperability test case
number Leap number for the test case
</pre>
<aside class="example">
<p>If needed, describe or declare using appropriate normative references the additional conventions that are used.</p>
<p><strong>DELETE THIS COMMENT</strong></p>
</aside>
</section>
<!-- /end conventions --> <!-- /end conventions --> <!-- /end conventions --> <!-- start definitions -->
<section>
<h2>Definitions</h2>
<aside class="example">
<p>Add definitions in new rows of the following table as needed. The following examples show how dictionary references should be made as well as locally defined terms. This description list should be maintained in sorted alphabetic order based on the labels of the terms.</p>
<p><strong>DELETE THIS COMMENT.</strong></p>
</aside>
<!-- start definition list -->
<dl>
<dt><dfn>Entity</dfn></dt>
<dd>Use definition #1 from [OMADICT].</dd>
<dt><dfn>Interactive Service</dfn></dt>
<dd>Use definition from [OMADICT].</dd>
<dt><dfn>Loal Term</dfn></dt>
<dd>The definition description would be presented directly here.</dd>
</dl>
<p>Kindly consult [[OMADICT]] for more definitions used in this document.</p>
</section>
<!-- /end definitions --> <!-- /end definitions --> <!-- /end definitions --> <!-- start abbreviations -->
<section>
<h2>Abbreviations</h2>
<aside class="example">
<p>Add abbreviations as needed to the following definition list. No special notation should be made regarding terms copied from the Dictionary. This definition list should be maintained in alphabetic order.</p>
<p><strong>DELETE THIS COMMENT.</strong></p>
</aside>
<!-- start abbreviations list -->
<dl>
<dt><abbr title="Implementation Conformance Specification">ICS</abbr></dt>
<dd>Implementation Conformance Specification.</dd>
<dt><abbr title="Implementation eXtra Information">IXIT</abbr></dt>
<dd>Implementation eXtra Information.</dd>
<dt><abbr title="Open Mobile Alliance">OMA</abbr></dt>
<dd>Open Mobile Alliance.</dd>
</dl>
<!-- end abbreviations list-->
<p>Kindly consult [[OMADICT]] for more abbreviations used in this document.</p>
</section>
<!-- /end abbreviations --> <!-- /end abbreviations --> <!-- /end abbreviations --></section>
<!-- end terminology and conventions -->
<p><br>
</p>
<!-- end terminology and conventions -->
<p><br>
</p>
<!-- end terminology and conventions -->
<p><br>
</p>
<!-- end terminology and conventions -->
<p><br>
</p>
<!-- end terminology and conventions -->
<p><br>
</p>
<!-- end terminology and conventions -->
<p><br>
</p>
<!-- end terminology and conventions -->
<p><br>
</p>
<!-- end terminology and conventions -->
<p><br>
</p>
<!-- end terminology and conventions -->
<p><br>
</p>
<!-- end terminology and conventions -->
<p><br>
</p>
<!-- end terminology and conventions -->
<p><br>
</p>
<!-- start introduction -->
<section class="informative">
<h2>Introduction</h2>
<aside class="example">
<p>This chapter should describe the introduction to the test cases specified in the document.</p>
<p><strong>DELETE THIS COMMENT.</strong></p>
</aside>
<p>The purpose of this document is to provide test cases for <xxx> Enabler Release <y.z>.</p>
<aside class="example">
<p>This part should give some introduction for the need of verification.</p>
<p><strong>DELETE THIS COMMENT.</strong></p>
</aside>
<p>The implementation of some features is optional for the Clients and/or the Servers in the <xxx> Enabler. The tests associated with these optional features are marked as "(Includes Optional Features)" in the test specification.</p>
<aside class="example">
<p>List the items needed to test the enabler, e.g. The following items on an overall level are needed to adequately test the <xxx> enabler:</p>
<ul>
<li>An origin server configured to support….</li>
<li>A web page providing a link…</li>
<li>[Optional] A web page providing a link…</li>
</ul>
<p>Detailed info will be put in the specific test cases description.</p>
<p><strong>DELETE THIS COMMENT.</strong></p>
</aside>
<aside class="example">
<p>If possible this part of the document should describe any protocols used by this enabler, e.g. The <xxx> enabler tests are carried out using <yyy> and/or <zzz> protocols.</p>
<p><strong>DELETE THIS COMMENT.</strong></p>
</aside>
</section>
<!-- /end introduction -->
<p><br>
</p>
<!-- /end introduction -->
<p><br>
</p>
<!-- /end introduction -->
<p><br>
</p>
<!-- /end introduction -->
<p><br>
</p>
<!-- /end introduction -->
<p><br>
</p>
<!-- /end introduction -->
<p><br>
</p>
<!-- /end introduction -->
<p><br>
</p>
<!-- /end introduction -->
<p><br>
</p>
<!-- /end introduction -->
<p><br>
</p>
<!-- /end introduction -->
<p><br>
</p>
<!-- /end introduction -->
<p><br>
</p>
<!-- start Conformance Test Cases -->
<section>
<h2><xxx> Conformance Test Cases</h2>
<aside class="example">
<p>There should be a chapter for conformance tests, under this chapter the test cases may be grouped in best possible way according to e.g. feature or groups of features to make the document easy to read and use.</p>
<p>Test Cases should not address anything not explicitly mentioned in the Specifications or ETR. They should also not address any quality of service issues. The Pass/Fail verdict for a Test Case should be clearly specified and not be open to interpretation.</p>
<p>If there are no conformance test cases available, please indicate with 'Not Available'.</p>
<p>If information for a heading of the test case is not available, please indicate that with 'Not Available' in the appropriate row of a test case.</p>
<p>Section n.1 shows example on headings for one test case. It should be replicated, as needed, for each test case.</p>
<p>If the test case tests one or more optional SCR Items, the title of the test case should have "(Includes Optional Features)" string appended to it.</p>
<p><strong>DELETE THIS COMMENT.</strong></p>
</aside>
<!-- start Conformance Test Cases Level 2 -->
<section>
<h2><xxx-y.z-con-number></h2>
<aside class="example">
<p>This section lists the steps needed for a conformance test case.</p>
<p><strong>DELETE THIS COMMENT.</strong></p>
</aside>
<table class="mce-item-table"><caption>Test Information for <yyy> Conformance Test</caption>
<tbody>
<tr>
<td>Test Case Id</td>
<td><xxx-y.z-con-number, e.g. IMPS-1.2-con-001.></td>
</tr>
<tr>
<td>Test Object</td>
<td><Client and/or Server device under test.></td>
</tr>
<tr>
<td>Test Case Description</td>
<td><Short description of the test case, e.g. To test delivery functionality.></td>
</tr>
<tr>
<td>Specification Reference</td>
<td><[REFERENCE EXAMPLE 1] Chapter x.></td>
</tr>
<tr>
<td>SCR Reference</td>
<td><Reference to explicitly tested SCR items, e.g. xxx-C-001-M.>
<aside class="example">
<p>The SCRs listed in this section should directly apply to this test case's Test Object. Listing of the SCRs tested implicitly should be avoided.</p>
<p><strong>DELETE THIS COMMENT.</strong></p>
</aside>
</td>
</tr>
<tr>
<td>Tool</td>
<td><List any tool including version available for this test case, if any.></td>
</tr>
<tr>
<td>Test code</td>
<td><List any code including version available for this test case, if any.></td>
</tr>
<tr>
<td>Preconditions</td>
<td><List the preconditions needed to execute the test case, e.g.
<ul>
<ul>
<li>Equipment:</li>
<ul>
<li>2 clients (A, B) / 1 server.</li>
<li>Functioning SAP with the 2 user accounts (A, B) existing on it.</li>
</ul>
<li>State:</li>
<ul>
<li>Both clients are logged in.</li>
<li>Both client and server support the same type of the delivery mechanism (Push or Notify/Get or both).</li>
<li>Both clients and server support Delivery Report functionality.</li>
<li>Client A is capable of displaying a successful delivery report.</li>
</ul>
<li>Continuation of / Can be tested at the same time as:</li>
<ul>
<li>IMPS-1.1-int-IMSE-001 - Verify that a message sent by one client is delivered to the other client.</li>
</ul>
<li>Prerequisite for this test:</li>
<ul>
<li>IMPS-1.1-int-IMSE-001 - Verify that a message sent by one client is delivered to the other client></li>
</ul>
</ul>
</ul>
<p><Optionally ICS (Implementation Conformance Statement) / IXIT (Implementation eXtra Information for Testing) information can be added here.></p>
<ul>
<li>Applicability:</li>
<ul>
<li>ics_PSK_TLS AND ics_3GPP.</li>
<li>ixit_mAC_KEY_ID.></li>
</ul>
</ul>
</td>
</tr>
<tr>
<td>Test Procedure</td>
<td><Describe the procedure to execute the test case, e.g.
<ol>
<li>User sends MMS message with terminal A to terminal B.</li>
<li>The message should be received in terminal B.</li>
</ol>
Any additional tips and tricks to the test procedure can also be added here.></td>
</tr>
<tr>
<td>Pass-Criteria</td>
<td><Describe the criteria for passing the test case, e.g.<br>
<ol>
<li>MMS is received in terminal B.</li>
<li>MMS is readable.></li>
</ol>
</td>
</tr>
</tbody>
</table>
</section>
<!-- end Conformance Test Cases Level 2 --> <!-- end Conformance Test Cases Level 2 --> <!-- end Conformance Test Cases Level 2 --></section>
<!-- /end Conformance Test Cases -->
<p><br>
</p>
<!-- /end Conformance Test Cases -->
<p><br>
</p>
<!-- /end Conformance Test Cases -->
<p><br>
</p>
<!-- /end Conformance Test Cases -->
<p><br>
</p>
<!-- /end Conformance Test Cases -->
<p><br>
</p>
<!-- /end Conformance Test Cases -->
<p><br>
</p>
<!-- /end Conformance Test Cases -->
<p><br>
</p>
<!-- /end Conformance Test Cases -->
<p><br>
</p>
<!-- /end Conformance Test Cases -->
<p><br>
</p>
<!-- /end Conformance Test Cases -->
<p><br>
</p>
<!-- /end Conformance Test Cases -->
<p><br>
</p>
<!-- /end Conformance Test Cases -->
<p><br>
</p>
<!-- start Interoperability Test Cases -->
<section>
<h2><xxx> Interoperability Test Cases</h2>
<aside class="example">
<p>There should be a chapter for interoperability tests. Under this chapter the test cases should be grouped according to the ETR feature key grouping as specified in the ETR document for the Enabler. This is done for the ease of association of the test cases to the corresponding ETR requirements and the SCRs.</p>
<p>Test Cases should not address anything not explicitly mentioned in the Specifications or ETR. They should also not address any quality of service issues. The Pass/Fail verdict for a Test Case should be clearly specified and not be open to interpretation.</p>
<p>If there are no conformance test cases available, please indicate with 'Not Available'.</p>
<p>If information for a heading of the test case is not available, please indicate that with 'Not Available' in the appropriate row of a test case.</p>
<p>Section n.1 shows example on headings for one test case. It should be replicated, as needed, for each test case.</p>
<p>If the test case tests one or more optional SCR Items, the title of the test case should have "(Includes Optional Features)" string appended to it.</p>
<p><strong>DELETE THIS COMMENT.</strong></p>
</aside>
<!-- start Level 2 -->
<section>
<h2><xxx-y.z-int-number></h2>
<aside class="example">
<p>This section lists the steps needed for a interoperability test case.</p>
<p><strong>DELETE THIS COMMENT.</strong></p>
</aside>
<table class="mce-item-table"><caption>Test Information for <zzz> Interoperability Test</caption>
<tbody>
<tr>
<td>Test Case Id</td>
<td><xxx-y.z-int-number, e.g. IMPS-1.2-int-001.></td>
</tr>
<tr>
<td>Test Object</td>
<td><Client and/or Server device under test.></td>
</tr>
<tr>
<td>Test Case Description</td>
<td><Short description of the test case, e.g. To test delivery functionality.></td>
</tr>
<tr>
<td>Specification Reference</td>
<td><[REFERENCE EXAMPLE 1] Chapter x.></td>
</tr>
<tr>
<td>SCR Reference</td>
<td><Reference to explicitly tested SCR items, e.g. xxx-C-001-M.>
<aside class="example">
<p>The SCRs listed in this section should directly apply to this test case's Test Object and to the ETR requirement(s) listed in the below ETR Reference section. Listing of the SCRs tested implicitly should be avoided.</p>
<p><strong>DELETE THIS COMMENT.</strong></p>
</aside>
</td>
</tr>
<tr>
<td>ETR Reference</td>
<td><Reference to the applicable ETR requirement (s), e.g. xxx-04>
<aside class="example">
<p>The ETR requirement(s) listed in this section should directly apply to this test case's Test Object.</p>
<p><strong>DELETE THIS COMMENT.</strong></p>
</aside>
</td>
</tr>
<tr>
<td>Tool</td>
<td><List any tool including version available for this test case, if any.></td>
</tr>
<tr>
<td>Test code</td>
<td><List any code including version available for this test case, if any.></td>
</tr>
<tr>
<td>Preconditions</td>
<td><List the preconditions needed to execute the test case, e.g.
<ul>
<li>Equipment:</li>
<ul>
<li>2 clients (A, B) / 1 server.</li>
<li>Functioning SAP with the 2 user accounts (A, B) existing on it.</li>
</ul>
<li>State:</li>
<ul>
<li>Both clients are logged in.</li>
<li>Both client and server support the same type of the delivery mechanism (Push or Notify/Get or both).</li>
<li>Both clients and server support Delivery Report functionality.</li>
<li>Client A is capable of displaying a successful delivery report.</li>
</ul>
<li>Continuation of / Can be tested at the same time as:</li>
<ul>
<li>IMPS-1.1-int-IMSE-001 - Verify that a message sent by one client is delivered to the other client.</li>
</ul>
<li>Prerequisite for this test:</li>
<ul>
<li>IMPS-1.1-int-IMSE-001 - Verify that a message sent by one client is delivered to the other client.></li>
</ul>
</ul>
</td>
</tr>
<tr>
<td>Test Procedure</td>
<td><Describe the procedure to execute the test case, e.g.
<ol>
<li>User sends MMS message with terminal A to terminal B.</li>
<li>The message should be received in terminal B.</li>
</ol>
Any additional tips and tricks to the test procedure can also be added here.></td>
</tr>
<tr>
<td>Pass-Criteria</td>
<td><Describe the criteria for passing the test case, e.g.<br>
<ol>
<li>MMS is received in terminal B.</li>
<li>MMS is readable.></li>
</ol>
</td>
</tr>
</tbody>
</table>
</section>
<!-- /end Level 2 --> <!-- /end Level 2 --> <!-- /end Level 2 --></section>
<!-- end Interoperability Test Cases -->
<p><br>
</p>
<!-- end Interoperability Test Cases -->
<p><br>
</p>
<!-- end Interoperability Test Cases -->
<p><br>
</p>
<!-- end Interoperability Test Cases -->
<p><br>
</p>
<!-- end Interoperability Test Cases -->
<p><br>
</p>
<!-- end Interoperability Test Cases -->
<p><br>
</p>
<!-- end Interoperability Test Cases -->
<p><br>
</p>
<!-- end Interoperability Test Cases -->
<p><br>
</p>
<!-- end Interoperability Test Cases -->
<p><br>
</p>
<!-- end Interoperability Test Cases -->
<p><br>
</p>
<!-- end Interoperability Test Cases -->
<p><br>
</p>
<!-- end Interoperability Test Cases -->
<p><br>
</p>
<!-- end Interoperability Test Cases -->
<p><br>
</p>
<!-- end Interoperability Test Cases -->
<p><br>
</p>
<!-- start Conformance Test Case applicability appendix -->
<section class="appendix">
<h2><<Optional>> Conformance Test Case applicability</h2>
<!-- start Introduction -->
<section>
<h2>Introduction</h2>
<p>This section shall help implementers of the <<xxx>> Enabler to select appropriate Conformance test cases that are applicable to the features implemented.</p>
<p>This appendix lists all test cases testing only mandatory features, ICS, IXIT and a mapping from ICS/IXIT to applicable test cases as defined by the Open Mobile Alliance.</p>
</section>
<!-- end Introduction --> <!-- start Test Cases testing only mandatory features -->
<section>
<h2>Test Cases testing only mandatory features</h2>
<p>These Conformance test cases are independent from any applicability, are testing only mandatory SCRs and SHALL be run with every implementation.</p>
<table class="mce-item-table"><caption>Test Cases testing only mandatory features</caption>
<thead>
<tr>
<td>Test Case</td>
</tr>
</thead>
<tbody>
<tr>
<td>SUPL-1.0-con-000 - Compatible Versions</td>
</tr>
</tbody>
</table>
</section>
<!-- /end Test Cases testing only mandatory features --> <!-- /end Test Cases testing only mandatory features --> <!-- /end Test Cases testing only mandatory features --> <!-- start Applicability -->
<section>
<h2>Applicability</h2>
<!-- start client ics -->
<section>
<h2>Client ICS</h2>
<table class="mce-item-table"><caption>Client ICS</caption>
<thead>
<tr>
<td>ICS</td>
<td>Description</td>
<td>SCR Reference(s)</td>
<td>Supported (yes/no)</td>
</tr>
</thead>
<tbody>
<tr>
<td>ics_SLP_SessionID _Ipv4.</td>
<td>IPV4 in SLP session ID supported.</td>
<td><br>
</td>
<td><br>
</td>
</tr>
</tbody>
</table>
</section>
<!-- /end client ics --> <!-- /end client ics --> <!-- /end client ics --> <!-- start Client IXIT -->
<section>
<h2>Client IXIT</h2>
<table class="mce-item-table"><caption>Client IXIT</caption>
<thead>
<tr>
<td>IXIT</td>
<td>Description</td>
<td>Unit <<(Range of values)>></td>
<td>Value</td>
</tr>
</thead>
<tbody>
<tr>
<td>ixit_timer_UT1.</td>
<td>Value of Timer UT1.</td>
<td>seconds (5 to 25).</td>
<td><br>
</td>
</tr>
</tbody>
</table>
</section>
<!-- end Client IXIT --> <!-- end Client IXIT --> <!-- end Client IXIT --> <!-- start Server ICS -->
<section>
<h2>Server ICS</h2>
<table class="mce-item-table"><caption>Server ICS</caption>
<thead>
<tr>
<td>ICS</td>
<td>Description</td>
<td>SCR Reference(s)</td>
<td>Supported (yes/no)</td>
</tr>
</thead>
<tbody>
<tr>
<td>ics_SLP_SessionID _Ipv4.</td>
<td>IPV4 in SLP session ID supported.</td>
<td><br>
</td>
<td><br>
</td>
</tr>
</tbody>
</table>
</section>
<!-- end Server ICS --> <!-- end Server ICS --> <!-- end Server ICS --> <!-- start Server IXIT -->
<section>
<h2>Server IXIT</h2>
<table class="mce-item-table"><caption>Server IXIT</caption>
<thead>
<tr>
<td>IXIT</td>
<td>Description</td>
<td>Unit <<(Range of values)>></td>
<td>Value</td>
</tr>
</thead>
<tbody>
<tr>
<td>ixit_timer_ST1.</td>
<td>Value of Timer ST1.</td>
<td>seconds (5 to 25).</td>
<td><br>
</td>
</tr>
</tbody>
</table>
</section>
<!-- end Server IXIT --> <!-- end Server IXIT --> <!-- end Server IXIT --></section>
<!-- end Applicability --> <!-- end Applicability --> <!-- end Applicability --> <!-- start ICS to test case mapping -->
<section>
<h2>ICS to test case mapping</h2>
<p>According to the ICS described above the applicable test cases can be derived from the following table.</p>
<table class="mce-item-table"><caption>ICS to test case mapping</caption>
<thead>
<tr>
<td>Applicability</td>
<td>Test Cases</td>
</tr>
</thead>
<tbody>
<tr>
<td>ics_MT_SMS AND ics_3GPP.</td>
<td>SUPL-1.0-con-014 - Incorrect MT SMS message content.</td>
</tr>
</tbody>
</table>
</section>
<!-- end ICS to test case mapping --> <!-- end ICS to test case mapping --> <!-- end ICS to test case mapping --></section>
<!-- end Conformance Test Case applicability appendix -->
<p><br>
</p>
<!-- end Conformance Test Case applicability appendix -->
<p><br>
</p>
<!-- end Conformance Test Case applicability appendix -->
<p><br>
</p>
<!-- end Conformance Test Case applicability appendix -->
<p><br>
</p>
<!-- end Conformance Test Case applicability appendix -->
<p><br>
</p>
<!-- end Conformance Test Case applicability appendix -->
<p><br>
</p>
<!-- end Conformance Test Case applicability appendix -->
<p><br>
</p>
<!-- end Conformance Test Case applicability appendix -->
<p><br>
</p>
<!-- end Conformance Test Case applicability appendix -->
<p><br>
</p>
<!-- end Conformance Test Case applicability appendix -->
<p><br>
</p>
<!-- end Conformance Test Case applicability appendix -->
<p><br>
</p>
<!-- end Conformance Test Case applicability appendix -->
<p><br>
</p>
<!-- end Conformance Test Case applicability appendix -->
<p><br>
</p>
<!-- end Conformance Test Case applicability appendix -->
<p><br>
</p>
<!-- end Conformance Test Case applicability appendix -->
<p><br>
</p>
<!-- end Conformance Test Case applicability appendix -->
<p><br>
</p>
<!-- start additional appendix -->
<p><br>
</p>
<!-- note that there is no need for appendix class -->
<section>
<h2>Additional Appendix</h2>
<aside class="example">
<p>If needed, add annex to provide additional information to support the document.</p>
<p>In general, this information should be informative, as normative material should be contained in the primary body of the document.</p>
<p>Note that the styles for the headers in the appendix (App1, App2, App3) are different than the main body.</p>
<p>The use below is intended to validate the styles to be used. Remove if not needed.</p>
<p><strong>DELETE THIS COMMENT</strong></p>
</aside>
<!-- start App Headers -->
<section>
<h2>App Headers</h2>
<p>Text goes here.</p>
<!-- start More Headers -->
<section>
<h2>More Headers</h2>
<p>More text goes here.</p>
<!-- start Even More Headers -->
<section>
<h2>Even More Header</h2>
<p>More text goes here.</p>
<figure id="fig1_example"><img src="images/fig1_example.png" data-mce-src="images/fig1_example.png">
<figcaption>Example Figure.</figcaption>
</figure>
<p>new paragraph</p>
<p>New text</p>
</section>
<!-- end Even More Headers --></section>
<!-- end More Headers --></section>
<!-- end App Headers --></section>
<!-- end additional appendix -->
<p><br>
</p>
<!-- end additional appendix -->
<p><br>
</p>
<!-- end additional appendix -->
<p><br>
</p>
<!-- end additional appendix -->
<p><br>
</p>
<!-- end additional appendix -->
<p><br>
</p>
<!-- end additional appendix -->
<p><br>
</p>
<!-- end additional appendix -->
<p><br>
</p>
<!-- end additional appendix -->
<p><br>
</p>
<!-- end additional appendix -->
<p><br>
</p>
<!-- end additional appendix -->
<p><br>
</p>
<!-- end additional appendix -->
<p><br>
</p>
<!-- end additional appendix -->
<p><br>
</p>
<!-- end additional appendix -->
<p><br>
</p>
<!-- end additional appendix -->
<p><br>
</p>
<!-- end additional appendix --></body>