S’‘ђЏЋЌЊ‹Љ‰€‡†…„ѓ‚ЃЂ~}|{zyxwvutsrqponmlkjihgfedcba`_^]\[ZYXWVUTSRQPONMLKJIHGFEDCBA@?>=<;:9876543210/.-,+*)('&%$#"!  х` ()‚ `^BLT TTT * where, for each service element,*Аях   аях];OI - the status of the service element is indicated as mandatoryIЎях] I (M), optional (O) or not applicable (-) in columns la D shown as not supported are in fact not present rather thanD¦ях5 ! improperly implemented.!Йях   аях@ , The IPMS(P2) PICS is in two parts:,ѕях   аяхa M - a part requesting information concerning the support of serviceMќях+  elements,Уях¦TLРR  аяхYT@Y@PE - a part requesting info ImplementationHўях; ' Conformance Statement (PICS).'Гях   аях^ЄHJ The proforma IPMS(P2) PICS contained in this Annex specifies theJ ях9O % information to be supplied.%Еях   аях[ G This information is needed for test case selection. SuppliersGЈях] I should note that tests will be performed to check that servicesIЎяхX The numbers on the right side indicate the places where the itemJ ях7 # occurs in the test suite.#Зях   аях> * Annex B IPMS(P2) PICS Proformas*Аях   аях*  B.1 GeneralФях   аяхY E As a prerequisite to conformance testing the supplier of anEҐях\ H IPMS(P2) implementation must provide a Protocol suite.(ВяхІІІ  аях&ІІІ Example:Шях3  :Лях3  :ЛяхC;O/ IM_UAPDU_1_14 586 1467/»яхC / IM_UAPDU_1_15 587 1470/»ях3  :Лях3  :Лях   аях^ J references.7іяхІІІмях   аях< ( A.6.2 Cross Reference Listing(Вях   аях` L At the end of MTS(P1) and IPMS(P2) test suites there is a separateLћях\¦TLРRH cross reference listing of all the ASPs, test PDUs and libraryHўяхYT@Y@PE components together with the place identifiers of all theirEҐях< ( occurrences in the testst PDUMќях] I or library component, the cross references for each item in theIЎях` L line are separated by vertical bars (" ") in the right hand marginLћях< ( as shown in Figure A-15/X.403.(Вях   аях мях мях мях мях¦TLРRмяхT@Y@P  аяхK 7 Figure A-15/X.403 Multiple crossrC§яхT @ occurrences of the ASP, test PDU or library component.@Єях   аях_ K Where a forward or backward reference can not be found then a dotKџяхaЄHM (".") is printed in the right hand margin. This should not occur inMќях8O $ fully defined test suites.$Жях   аяхa M Where a line in the test suite contains more than one ASP, tealMќяхa M order and are "place identifiers". They occur whenever an ASP, testMќяхP < PDU or library component occurs in the test suite.<®ях   аях` L Whenever an ASP, test PDU or library component occurs, numbers areLћяхa M also placed in the right hand margin. These numbers are forward andMќяхW C backward references to the place identifiers of the othe ' 'Гях мях мях мях мях мях¦TLРRмяхT@Y@Pмях мяхІІІмяхІІІмях   аяхC / Figure A-14/X.403 Cross referencing./»ях;O  аяхa M Numbers in the left hand margin of the test suite are in sequenti  аях> * A.6.1 Cross Reference Numbering*АяхЄH  аях^O J The MTS(P1) and IPMS(P2) test suites contain a cross referencingJ ях^ J system for the ASPs, test PDUs and library components. The crossJ яхa M referencing appears in the left and right margins of the test suiteMќях< ( as shown in Figure A-14/X.403.(Вях   аях;istinguished fromJ ях` L those which exercise the IUT's reaction to invalid and inopportuneLћяхR > behaviour using the numeric identifiers shown below:>¬яхЄH  аях1O  Valid 1Нях1  Invalid 2Нях1  Inopportune 3Нях   аях4  A.6 Cross Referencing Кях  roups asIЎях*ІІІ shown below:Фях   аях1  Initiator 1Нях1;O Responder 2Нях1  Sender 1Нях1  Receiver 2Нях   аях; ' A.5.2.3 Validity identifiers'Гях   аях^ J Test cases which exercise valid behaviour are d Association Establishment 1+їях? + Association Release 2+їях? + Data Transfer 3+їях? + Association Recovery 4+їях? + X.409 Tests 5+їях   аях0T@Y@P A.5.2.2 SubgroupsОях   аях]ІІІI Numeric identifiers have been allocated to the RTS subg particular group/subgroup/validity are numberedJ ях+  sequentially.Уях   аях7 # A.5.2 RTS Identification#Зях   аях2ЄH A.5.2.1 Test GroupsМяхO   аях\ H Number ranges have been allocated for the test groups as shownHўях$  below:Ъях   аях? + r are distinguished fromJ ях`¦TLРRL those which exercise the IUT's reaction to invalid behaviour usingLћяхBT@Y@P. the numeric identifiers shown below:.јях   аях1ІІІ Valid 1Нях1ІІІ Invalid 2Нях   аях8 $ A.5.1.4 Test case numbers$Жях   аях^ J Test cases for a 2$Жях8T@Y@P$ encode 1$Жях8 $ decode 2$Жях8ІІІ$ Relay 3$Жях8ІІІ$ Relaying-Recipient 4$Жях8 $ Relaying-Originator 5$Жях   аях; ' A.5.1.3 Validity identifiers'Гях   аях^ J Test cases which exercise valid behavious 300 - 399;ЇяхO ; Additional Tests 400 - 499;Їях   аях0  A.5.1.2 SubgroupsОях   аях^ J Numeric identifiers have been allocated to the test subgroups asJ ях*  shown below:Фях   аях8 $ Originator 1$Жях8¦TLРR$ Recipient es have been allocated for the test groups as shownHўях$  below:Ъях   аяхO ; Initial Tests 001 - 099;ЇяхO ; X.409 Tests 100 - 199;ЇяхO ; Protocol Elements Tests 200 - 299;ЇяхEЄH1 (for frequently occurring Elements)1№яхOO ; X.400 Service Elements Test аях` L - As a Test Identifier where the four components are numeric andLћях*¦TLРR concise.Фях мях)  Example:Хях4  307.2.1.2 КяхH;O4 A.5.1 IPMS(P2) and MTS(P1) identification4¶ях   аях2  A.5.1.1 Test GroupsМях   аях\ H Number rang   аяхY E These four components are specified in two equivalent ways:EҐях   аях_ K - As a Test Reference where the four components are textual andKџях.  descriptive.Рях!   Эях*  Example:Фях^ J OriginalEncodedInfoTypeIndication/Recipient/Valid/2J ях  schedules.Цях мях; ' A.5 Test Case Identification'Гях   аяхY E Test cases are completely identified using four components:EҐях   аях: & - a test group identifier.&Дях8 $ - a subgroup identifier.$Жях8ЄH$ - a validity identifier.$Жях0O  - a test number.Ояхf theMќях? + value of the parameter .+їях   аях_ K [ - ] indicates that the tester shall check that the parameterKџях1¦TLРR is absent.НяхT@Y@P  аях[ G Note that the "?" and "-" symbols in value assignments of PDUGЈях`ІІІL components have got other meanings than "?" and "-" in generic ASPLћях(ІІІTO @ [ - ] indicates that the parameter shall be absent.@Єях   аях_ K [ * ] indicates that the value is to be inserted by the testerKџях= ) before test execution.)Бях   аях@ , For PDU's received by the tester :,ѕях   аяхa M [ ? ] indicates that the tester need make no verification oeparated by comma (egKџях-  {"abc",'0A'H}).Сях   аях< ( For PDU's sent by the tester :(Вях   аях` L [ ? ] indicates that the value has no influence on the test andLћях^ J may be anything that is legal according to the relevantJ яхD 0 service or protocol standard.0єяхЄH  аяхr within the Test Suite Parameters section.Hўях[ G CharacterString Values can specified within double-quotes (egGЈях^;OJ "abc"); Bit String Values are specified within single-quotes (egJ ях_ K '0A'H or '0001'B; hexadecimal or binary notation); Integer ValuesKџях_ K are specified as numeric characters (eg 2); sets and sequences ofKџях_ K values are specified within curly brackets sмях мях мях мях мях мях6¦TLРR" A.4.6 Value Conventions"ИяхT@Y@P  аях^ J The following conventions are used when defining values or valueJ ях<ІІІ( references for PDU components.(Вях\ІІІH Value references identify components defined either within theHўях\ H Component Library o Example:ШяхO   аяхZ F F¤ях мях мях мях мях мях мях мях мях мях¦TLРRмяхT@Y@Pмях мяхІІІмяхІІІмях мях мях;Oications, Test PDU specifications and by otherGЈях1  library components.Нях   аяхM 9 The name of a Library Component is of the form:9±ях   аяхD 0 L__0єях   аяхW C and is specified using the techniques described in A.4.3.C§ях   аях&ЄH ях мях мях мях¦TLРRмяхT@Y@Pмях] I IЎяхІІІ  аяхІІІ  бях6 " A.4.5 Component Library"Иях;O  аяхa M Components of PDUs are defined in the library and are referenced inMќях[ G Base PDU specif мях мях мях мях   аях] I IЎях мях мях мях   аях&  Example:ШяхЄH  аях мях мях мях мях мях мMќях2  purpose of the test.Мях   аях` L A component of interest is identified and its value assigned usingLћях@ , the techniques described in A.4.3.,ѕях   аяхN : The specification scheme has the following form::°ях   аях мяхЄHмяхO мях мях IЎях]¦TLРRI This means that L_ORDescriptor_1 is used here with the modifiedIЎях_T@Y@PK ORName type, whereas the usage of this library component in otherKџяхC / PDUs or components remains unaltered./»яхІІІ  аяхG 3 A.4.4.2 Test PDUs received by the tester3·ях;O  аяхa M For received PDUs normally only a portion of the PDU relates to theY E EҐях   аях] I The error to be constructed here is the wrong tag of the ORNameIЎях_ K type (the correct tag would be [APPLICATION 0]). The scope of theKџях_ K erroneous type-definition constructed by "REDEFINE" is restrictedKџях] I to all occurrences of ORName in the definition of IM_UAPDU_1_3. мях&ІІІ Example:Шях   аяхY E EҐях мях мях мях мях мях мях мях мях мяхЄHмяхO мях мях мях мях мяхtype is restricted to the PDUF¤яхK 7 definition containing the REDEFINE operation.7іях¦TLРR  аях[T@Y@PG Note that if the is a reference to an element definedGЈях^ J elsewhere (i.e. a TSP or a Library Component), then the new typeJ ях_ІІІK definition does not affect the referenced element itself but onlyKџях:ІІІ& its usage in the actual PDU.&Дях It isJ ях] I used together with the REPLACE operation in the following form:IЎях   аях   аях мях мяхЄHмяхO мях мях мях мях мях мях мях мях   аяхZ F The scope of the newly defined мях¦TLРRмяхT@Y@Pмях мяхІІІмяхІІІмях мях мяхY;OE EҐях   аях   аях\ H To construct invalid components in test PDUs to be sent by theHўях^ J tester, the abstract REDEFINE operation is sometimes used. мях мяхЄHмяхO мях мях мях мях мях мях мях мяхY E For the conventions of value assignments see section A.4.6.EҐях   аях&  Example:Шях   аях мях мях мяхMќях+  base PDU.Уях   аяхC / A.4.4.1 Test PDUs sent by the tester/»ях   аях^ J A test PDU sent by the tester to the IUT is normally constructedJ яхP < from a Base PDU by means of the REPLACE operation.<®ях   аях= ) The specification has the form:)Бях   аях derived.Фях!   ЭяхQ = - PDUs received by the tester (IUT as originator)=­ях!   ЭяхW¦TLРRC By convention the names of these PDUs are of the formC§ях!T@Y@P  Эях= ) _0_)Бях!ІІІ  ЭяхaІІІM where "0" indicates that these test PDUs are not derived from ast PDU:*АяхЄH  аяхLO 8 - PDUs sent by the tester (IUT as recipient)8Іях   аяхW C By convention the names of these PDUs are of the formC§ях!   Эях= ) _x_)Бях!   Эяхb N where x is the number of the base PDU from which the test PDU isNњях* uld be instance_1.a.D¦ях\ H In order to reference "e", the path would be instance_1.b.d.e.Hўях мях.  A.4.4 Test PDUsРях   аях_ K Test PDUs are defined in terms of operations on Base PDU's. TheseKџях^ J operations refer to Library Components, TSPs or specific values.J ях   аях> * There are two kinds of teample, consider the following definitions::°ях;O  аях мях мях мях мях мях мях мях мях мях мяхЄHмяхO мях мях мях мях   аяхX D In order to reference "a", the path wo".". TheF¤ях\¦TLРRH elements in the list can be labels which appear in a BASE PDU,HўяхXT@Y@PD components which appear in the left-hand side of a labeledD¦ях^ J declaration, or components which appear in the left-hand side ofJ ях^ІІІJ the expansion of a library reference in the right-hand side of aJ ях*ІІІ declaration.Фях   аяхN : For exthat any valid encoding of lengthMќях)  is allowed.Хях   аяхP < A.4.3.2 Identifying the components to be modified<®ях   аях] I A component which is to be replaced in a PDU is identified by aIЎях_ K path through the declaration of the PDU. The path is written as aKџяхZ F list of elements, each separated from the next by a мях;Oмях мях мях мях мях мях мях мях мях мях мяхZЄHF The values of ID and LI can be specified explicitly to allowF¤ях[O G invalid and various forms of valid codings to be defined. TheGЈяхa M mnemonic "LI" is used to indicate мяхY E When specifying the encoding of a PDU for encoding/decodingEҐях_ K tests,two additional columns are used to specify the ID Code [ID]Kџях^ J and Length Indicator [LI] of each element of the PDU. The formatJ яхK¦TLРR7 for doing this is shown in the example below.7іяхT@Y@P  аях кяхІІІмяхІІІмях мях мях мяхЄHмяхO мях мях мяхZ F F¤ях   аях^ J The value or value reference of each element of the structure isJ ях_ K specified within square brackets ("[" and "]") under the VALUE orKџях0  REFERENCE heading.ОяхPDUtypename>_/»ях   аяхF 2 An example of a Base PDU is shown below.2ёях¦TLРR  аях&T@Y@P Example:Шях   аяхІІІмяхІІІмях мях мях;Oмях мях мях мях мях мях мях мях4.3.1 Base PDU specification)БяхO   аях` L Base PDUs are not themselves used as test PDUs but they serve as aLћях_ K basis from which to derive the test PDUs. Usually only a few BaseKџях8 $ PDUs need to be specified.$Жях   аяхD 0 The name of a Base PDU is of the form:0єях   аяхC / BASE_< M PDU is defined in terms of modifications to one of the small numberMќях-  of "base" PDUs.Сях   аях[ G For convenience commonly used PDU components are defined in aGЈяхT @ library and are referenced by test PDUs and base PDUs.@ЄяхЄH  аях.  A.4.3 Base PDUsРях   аях=ЄH) A.ІІІ) whose values are to be checked.)БяхІІІ  аях` L The "VALUE or REFERENCE" column can contain either specific valuesLћяхT @ or references to library components ASPs or test PDUs.@Єях;O  аях: & A.4.2 Specifying PDU values&Дях   аяхa M The MHS test suite contains a large number of test PDU values. EachMќяхa  аях_ K The "INSTANCE NAME" column is used to identify specific instancesKџях@ , of the ASP used in the test suite.,ѕях   аях]¦TLРRI The "MODIFIED PARAMETER" column identifies, for "request" ASP'sIЎях_T@Y@PK those parameters whose values are to be modified from the genericKџях^ J ASP specification, and for "notification" ASP's those parametersJ ях= EҐях мях мях мях мях мях мях мях мяхЄHмяхO мях мях мях мях   аяхD 0 Figure A-13/X.403 Specific ASP value.0єях   аях  ;ON have a value defined in a specific instance if it is a componentNњях.  of interest.Рях   аяхE 1 A.4.1.2 Specification of ASP Instances1№яхІІІ  аях`ІІІL Specific values of ASPs are defined using the tabular format shownLћях3  in Figure A-13/X.403.Лях   аяхY;OE e a TSP name or a library componentKџях'  name.Чях¦TLРR  аях7T@Y@P# (b) As an explicit value.#Зях   аяхZІІІF (c) As "-" to indicate that this parameter may be omitted inF¤яхAІІІ- specific instances of this ASP.-Ѕях   аяхa M (d) As "?" to indicate that for "request" ASP's this parameter mustMќяхb 7 Figure A-12/X.403 Generic ASP specification.7іях   аях` L The "FIELDS" column is used to list all the parameters of the ASP.Lћях   аяхa M The "VALUE or REFERENCE" column is used to specify a value for eachMќяхJ 6 parameter and this can be done in four ways:6ґях   аях_ K (a) As a reference which can b   аяхYT@Y@PE EҐях мях;Oмях мях мях мях мях мях мях мях мях мях мях мях мях мяхЄHмяхO   аяхKture of the Constraints Part.BЁях   аях4O  A.4.1 ASP Constraints Кях   аях` L Values of ASPs are defined as specific instances of a generic ASP.Lћях   аяхG 3 A.4.1.1 Specification of a "Generic" ASP3·ях   аяхc O A generic ASP is defined using the format shown in Figure A-12/X.403.O›ях мях мях мях мях мях¦TLРRмяхT@Y@Pмях мяхІІІмяхІІІмях мях мях мях мях;Oмях мях мях/  Пях   аяхV B Figure A-11/X.403 The struc divided into the followingIЎях'  sections:Чях   аяхC / - Introduction to Constraints Part/»ях2  - ASP ConstraintsМях7 # - Test PDU Constraints#Зях7 # - Base PDU Constraints#Зях5ЄH! - Components Library!ЙяхO   аях мях мях мяхome of the verdict alternatives are "hidden" in theKџях> * Default Library element.*АяхІІІ  аях3;O A.4 Constraints PartЛях   аяхa M The Constraints Part of a Test Suite specifies the values and theirMќяхa M encoding of all instances of ASPs, Test PDUs, Base PDUs and LibraryMќях] I Components. The Constraints Parts is   аяхM 9 + 9±ях%  ЩяхX D Note 3: The behaviour tree of every Test Case provides theD¦ях^ J verdicts pass, fail, and where appropriate inconclusive.J ях%  ЩяхX¦TLРRD Note 4: When using Default Library elements it is possibleD¦ях_T@Y@PK that s + LIB_unexpected [T]+їях%ЄH Щях\O H it means that the subtree associated with this DefaultHўях^ J Behaviour is considered to be associated with the SAP T.J ях%  Щях^ J Note 2: Test Step Library behaviour is included in the behaviourJ яхH 4 tree using the following notation:4¶яхigure A-10/X.403 Test Case Behaviour.1№ях   аях   аях\ H Note 1: In this field all Default Library Identifiers used areHўяхb N inserted. Where necessary, the SAP at which they are appliedNњях_ K is also identified. If for example the field contains theKџях,  entry:Тях%  Щях? using the tree notation definedLћях3  in section A.3.2.ЛяхY E EҐях мях мях мях мях¦TLРRмяхT@Y@Pмях мяхІІІмяхІІІмях мях мях;Oмях   аяхE 1 F (c) Test Description (optional))Бях!   Эяхa M This provides an informal description of the actions and eventsMќях` L that should take place during the test and an informal verdictLћях+  criteria.Уях   аях0  (d) Behaviour TreeОях!   Эях` L Dynamic behaviour is described est Identifier0єях!   Эях` L These elements give a unique reference and identifier for eachLћяхS ? test case and are described fully in section A.5.?«ях   аях)  (b) SummaryХях!   ЭяхZ F A brief overview of the purpose of the test is provided.F¤яхЄH  аях=O ) EҐях¦TLРR  аяхDT@Y@P0 Figure A-9/X.403 Test Step Behaviour.0єях   аях.  A.3.5 Test CaseРях   аях_;OK Each test case in the main body of the test suite is described inKџяхY E terms of three headings (a) - (c), and a behaviour tree (d)EҐях   аяхD 0 (a) Test Reference and Tat test case and the identifier is notEҐях3  prefixed with "LIB_".Лях мях мях мях мяхЄHмяхO мях мях мях мях мях мях мях мях мях мяхY E of use in several test cases theyMќях^ J can be included in the Test Step Library and given a name of theJ ях#  form:Ыях   аях(ЄH LIB_ЦяхO   аях#  Note:Ыях   аяхa M Where a test step applies to a single test case the behaviour tableMќяхY E is associated with th мях мях мях мях мях¦TLРRмяхT@Y@Pмях мяхІІІмях;O  аяхB . Figure A-8/X.403 Default Behaviour..јях   аях   аях6 " A.3.4 Test Step Library"Иях   аяхa M Where a sequence of test steps is  аях^ J Where particular default behaviour applies to a single test caseJ ях` L only the behaviour table is associated with that test case and theLћяхEЄH1 identifier is not prefixed with "LIB_".1№яхO   аяхY E EҐях мях мях мях мях of the default is of the form:<®ях   аях(;O LIB_Цях  or Юях,  LIB_ [X]Тях   аях_ K where X is a place holder which is replaced by an actual SAP whenKџяхU A applying the default element in a particular Test Case.A©ях   аях#  Note:Ыях  D receipt of a Transfer Indication at T, or a DisconnectD¦ях> * Indication is received at T.*Аях мях5T@Y@P! A.3.3 Defaults Library!Йях   аяхaІІІM General default behaviours which are used by several test cases areMќях^ІІІJ defined in the Defaults Library using the format shown in figureJ яхP < A-8/X.403. The name wo kinds of combinationLћях+  can be mixed.УяхІІІ  аях&ІІІ Example:Шях   аях мях;Oмях мях мях   аяхa M This means that after sending a Submission Request at I, eitherMќях] I a Submission Confirmation is received at I, followed by theIЎяхX Example of alternative events:(Вях"  Ьях*  T?DELindФях5 ! T?Timeout I/T-timer!Йях"  ЬяхY E This means that at SAP T either a Deliver Indication isEҐяхZ F received or alternatively the timeout is received there.F¤ях¦TLРR  аях`T@Y@PL To build up a complex behaviour tree, the t I?SUBconУях,  T?TRNindТях"  Ьях\ЄHH This means that first at the SAP I a Submission Request isHўяхYO E sent, then at the same SAP a Submission Confirmation isEҐях` L received, after which a Transfer Indication is received at theLћях1  tester's SAP T.Нях"  Ьях< ( 6 " - as sequences of events"Иях5;O! - as alternative events!Йях   аяхY E The two combination kinds are distinguished by indented andEҐях> * vertical alignment respectively.*Аях   аях> * Example of a sequence of events:*Аях   аях*  I!SUBreqФях+  :Шях   аях-  T?OTHERWISEСях"  ЬяхW C Means that at the tester's SAP T an unspecified eventC§ях.  is received.Рях   аях9 % A.3.2.4 Trees of behaviour%ЕяхІІІ  аяхLІІІ8 Trees of behaviour combine events in two ways:8Іях   аях@Y@P Ьяхa M means that at the IUT's SAP I the timeout of the above timer isMќях+ІІІ received.УяхІІІмях?ЄH+ A.3.2.3 Single OTHERWISE events.+їяхO   аяхY E If is the OTHERWISE pseudo-event, this indicates anEҐях0  unspecified event.Оях   аях&  Examplemple:Шях   аях5 ! I!Start T/I-timer_1!Йях"  Ьях[ G means that at the IUT's SAP I the T/I-timer_1 (e.g. for aGЈяхa M transmission time for a UAPDU to be transferred from the testerMќях@ , to the IUT's user) is started.,ѕях"  Ьях7¦TLРR# I?Timeout T/I-timer_1#Зях"T%Еях   аяхa M where denotes the operation. When the timer was startedMќях_ЄHK using the form "Start ", the form " " must be used; when the timer was started using the formHўяхa M "Start ", the form " " must be used.Mќях   аях&  Exaels a running or suspended timer=­яхE 1 Suspend: suspends a running timer1№яхF 2 Resume: resumes a suspended timer2ёяхJ 6 Timeout: expiration of a running timer6ґях   аяхE 1 These operations take one of two forms:1№ях   аях; ' 'Гях9 % >).јях¦TLРR  аях]T@Y@PI Where is defined in the Declaration Part and has aIЎяхa M fixed value associated with it defined in terms of TSPs. The allows a name to be attached to an instance of a timer type.J яхІІІ  аях7 # The other operations are:#Зях   аяхQ;O= Cancel: cancngle Timer events.'Гях   аяхP < If is a timer event then it is of the form<®ях   аях? + +їях   аяхN : The "start" operation can take one of two forms::°ях   аях5 ! Start !ЙяхB . Start (, is an ASP event then the names for the ASPs areHўях` L those specified in the Declaration Part (the value is specified asthe point of control and observation at which theHўяхa M occurs. The SAPs used are those declared in the DeclarationMќях#  Part.Ыях   аях^ J The "!" symbol indicates that the event is sent from the SAP andJ яхR > "?" indicates that the event is received at the SAP.>¬ях   аях0  The can beОях¦TL   аяхY E Trees of behaviour are defined in terms of events which areEҐях3  generally of the formЛях   аях4  ! Кях   аях,ЄH or of the formТяхO   аях4  ? Кях   аях\ H The is ІІ  аяхZІІІF - pass: no misbehaviour of the IUT is detected.F¤яхW C - fail: misbehaviour of the IUT is detected.C§ях\ H - inconclusive: the observed behaviour does not allow theHўяхX;OD assignment of a pass or fail verdict.D¦ях   аяхG 3 A.3.2 Tree notation for test behaviours.3·яхtional comments may be given in the "ExtendedGЈях_ K Comments" area. This column can also be used to identify testKџяхC / PDUs associated with test events./»ях   аях%  RESULT:Щях"¦TLРR ЬяхaT@Y@PM This column indicates which test events generate test verdicts.Mќях> * Values of test verdicts are:*АяхІ Ьях`ІІІL For each ASP event of a behaviour tree line, this column givesLћяхXІІІD the reference to the specific ASP value defined in theD¦ях3  Constraints Part.Лях мях'  COMMENTS:Чях"  Ьях_ K This column provides comments which ease understanding of theKџях[ G events. Addi  in A.3.2.Уях   аях$  LABEL:Ъях"  Ьях\ H The LABELS column may be used to identify events. BranchesHўях` L between events (i.e. "GO TO") are specified by " > Label" inLћях5 ! the behaviour tree.!Йях¦TLРR  аях4T@Y@P CONSTRAINTS REFERENCE: Кях" ^ J This lists the identifiers of default behaviour descriptionsJ ях` L which are to be used in conjunction with the Dynamic behaviourLћяхLЄH8 shown in the "BEHAVIOUR DESCRIPTION" part.8ІяхO   аях4  BEHAVIOUR DESCRIPTION: Кях"  Ьях^ J Test behaviour is defined using a tree notation as describedJ ях+the behaviour: DEFAULT for the Default Library;F¤яхS;O? DYNAMIC for the Test Step Library and test cases.?«ях   аях)  IDENTIFIER:Хях"  ЬяхU A This provides a unique identifier for the behaviourA©ях.  description.Рях   аях'  DEFAULTS:Чях"  Ьяхмях мях мях мях мях мях мях мях мях мях¦TLРR  аяхFT@Y@P2 Figure A-7/X.403 Behaviour Description.2ёях   аяхІІІ  аях0ІІІ BEHAVIOUR:�Оях"�������� � � �� �ЬяхZ�������� � ���F� Title of �J� Section A.3.5 describes how each test case in the main body of a�J ях6������������ЄH"� test suite is specified.�"Иях��������O��� ���мяхG�������� � � �3� A.3.1 Proforma table for Test Behaviours�3·ях�������� � � � � � аяхY�������� � � �E� �EҐях�������� � � ���мях�������� � � ���мях�������� � � ���мях�������� � � ���мях������������ЄH��мях��������O��� ���мях�������� � � f behaviour.�Нях�������� � � � � � аях`�������� � � �L� Sections A.3.1 and A.3.2 describe generally how trees of behaviour�Lћях*�������� � � �� are defined.�Фях�������� � � � � � аях^�������� � � �J� Section A.3.3 describes the content and use of Defaults Library.�J ях�������� � � � � � аях_�������� � � �K� Section A.3.4 describes the content and use of Test Step Library.�Kџях�������� � � � � � аях^�������� � � � ���мях�������� � � ���мях�������� � � ���мях�������� � � ���мях�������� � � ���мях�������� � �����мях��������¦TLРR � � аях>��������T@Y@P�*� Figure A-6/X.403 Abbreviations.�*Аях�������� � � � � � аях��������І�І�І� � � аях2�������� � � �� A.3 Dynamic Part�Мях�������� � ��� � � аяхa���������;��O�M� The Dynamic Part defines the test cases of a test suite in terms of�Mќях1�������� � � �� trees o����� � � ���мях�������� � � ���мях�������� � � � � � аях7�������� � � �#� Figure A-5/X.403 Timers.�#Зях������� � � � � � аях2�������� � � �� A.2.7 Abbreviations�Мях������������ЄH � � аях_��������O��� �K� Abbreviations used in the Test Suite are defined in the form of a�KџяхA�������� � � �-� table as shown in Figure A-6/X.403.�-Ѕях�������� � � � � � аях�������� � � ���мях�������� � � ���мях�������� �es are�GЈях^��������¦TLРRJ� expressions in terms of Test Suite Parameters, and are fixed for�J ях`��������T@Y@P�L� the whole test suite. Timer values are declared in tabular form as�Lћях8�������� � � �$� shown in figure A-5/X.403.�$Жях��������І�І�І� � � аяхY��������І�І�І�E� �EҐях�������� � � ���мях�������� � �����мях���������;��O���мях�������� � � ���мях�������� � � ���мях��������І�І�І�E� �EҐях�������� � � ���мях�������� � � ���мях��������T@Y@P���мях�������� � � ���мях��������І�І�І���мях��������І�І�І���мях�������� � � � � � аяхD�������� � ���0� Figure A-4/X.403 Protocol Data Units.�0єях���������;��O���мях+�������� � � �� A.2.6 Timers�Уях�������� � � � � � аях[�������� � ���G� This section declares the timers to be used. Timer valu� The PDU types used in test suites are declared in the form of�GЈях]�������� � � �I� tables as shown in Figure A-4/X.403. These PDUs are not defined�IЎях`�������� � � �L� explicitly in the test suite, but are given a precise reference to�Lћях`�������� � � �L� the full definition in the X.400 Recommendations, in the type name�Lћях3�������� � � �� section of the table.�Лях�������� � � � � � аях�������� � � ���мях��������І�І�І���мяхY���K� formalize the requirements for observation and invocation of IPMS�Kџяхa�������� � � �M� service elements by the use of these new ASPs. The relation between�Mќяхa�������� � � �M� IPMS service elements and the actual behaviour of the IUT has to be�MќяхN�������� � � �:� specified in the implementation-dependent PIXIT.�:°ях�������� � � � � � аях8�������� � � �$� A.2.5 Protocol Data Units�$Жях�������� � � � � � аях[�������� � � �Gхa�������� � � �M� Since there are no IPMS(P2) ASPs defined in the Recommendations, in�MќяхZ�������� � � �F� order to describe conformance tests it has been necessary to�F¤яхa�������� � � �M� construct hypothetical ASPs at the upper boundary of the User Agent�Mќяхa�������� � � �M� Layer. This does not imply, however that manufacturers are required�Mќях]�������� � � �I� to implement these ASPs within their systems. It serves only to�IЎях_�������� � � � is derived�Lћяхa�������� � � �M� from the corresponding name in the X.400 Series of Recommendations.�Mќях^��������І�І�І�J� The SAP at which the ASP occurs is specified in the "SAP" field.�J яхY��������І�І�І�E� The parameters of the ASP are declared in the "NAME" column�EҐях`�������� � � �L� together with information in "RANGE OF VALUES OR TYPE", "COMMENTS"�LћяхB�������� � ���.� and "Conditional/Mandatory" columns.�.јях���������;��O� � � аяm as shown in Figure A-3/X.403.�@Єях������������ЄH � � аях��������O��� ���мях�������� � � ���мях�������� � � ���мях�������� � � ���мях�������� � � ���мях�������� � � ���мях�������� � � ���мях�������� � � ���мях�������� � � � � � аяхL�������� � � �8� Figure A-3/X.403 Abstract Service Primitives.�8Іях������� � ��� � � аях��������¦TLРR � � аях`��������T@Y@P�L� The name of the ASP is specified in the "ASP" field and By convention the name of a SAP in the MHS Test Suites is generally�Mќях^�������� � � �J� one capital letter, such as T, U, V (for tester SAPs) or I, J, K�J ях-�������� � � �� (for IUT SAPs).�Сях�������� � � � � � аях@�������� � � �,� A.2.4 Abstract Service Primitives�,ѕях�������� � � � � � аяхa�������� � � �M� Each ASP type and its associated parameters used in a test suite is�MќяхT�������� � � �@� declared in tabular for Figure A-2/X.403.�Пях�������� � � � � � аяхY�������� � � �E� �EҐях�������� � � ���мях�������� � � ���мях�������� � �����мях��������¦TLРR��мях��������T@Y@P���мях�������� � � ���мях��������І�І�І���мях��������І�І�І� � � аяхF�������� � � �2� Figure A-2/X.403 Service Access Points.�2ёях�������� � ��� � � аях���������;��O� � � аяхa�������� � � �M� suites is of the form:� Кях�������� � � � � � аях2�������� � � �� TSP_<name>�Мях�������� � � � � � аях�������� � � � � � аяхA������������ЄH-� A.2.3 Service Access Points (SAPs)�-Ѕях�������� � � � � � аяхa�������� � � �M� Service Access Points are used as points of control and observation�Mќяхa�������� � � �M� in the MHS Test Suites and are declared in tabular form as shown in�Mќях/�������� � � �� as shown in Figure A-1/X.403.�IЎях�������� � � ���мях�������� � � ���мях��������T@Y@P���мях�������� � � ���мях��������І�І�І���мях��������І�І�І���мях�������� � � ���мях�������� � �����мях���������;��O���мях�������� � � ���мях�������� � � ���мяхF�������� � � �2� Figure A-1/X.403 Test Suite Parameters.�2ёях�������� � � � � � аяхa�������� � � �M� By convention the name of each Test Suite Parameter in the MHS test�Mќях4�������� � � � � vation are declared in this section.�Mќях�������� � ��� � � аях:��������¦TLРR&� A.2.2 Test Suite Parameters�&Дях�������� � � � � � аяхa��������І�І�І�M� Every MHS Test Suite has a set of parameters whose values are fixed�Mќях^��������І�І�І�J� prior to testing and which are used to define a specific testing�J ях*�������� � � �� environment.�Фях������� � ��� � � аях]���������;��O�I� TSPs are declared in tabular formuite Parameters (TSPs)�*Аях>������������ЄH*� - Service Access Points (SAPs)�*АяхD��������O��� �0� - Abstract Service Primitives (ASPs)�0єях<�������� � � �(� - Protocol Data Units (PDUs)�(Вях(�������� � � �� - Timers�Цях/�������� � � �� - Abbreviations�Пях�������� � � � � � аях8�������� � � �$� A.2.1 Test Configurations�$Жях�������� � � � � � аяхa�������� � � �M� The points of control and obsert Case Identification�&Дях2���������;��O�� - Cross-References�Мях�������� � � � � � аях3�������� � � �� A.2 Declaration Part�Лях�������� � � � � � аях_�������� � � �K� The Declaration Part declares the environment and objects used in�KџяхL�������� � � �8� the test suites and is composed of 7 sections:�8Іях�������� � � � � � аях5�������� � � �!� - Test Configurations�!Йях>�������� � � �*� - Test S �K� early form of TTCN and has been developed specifically for use in�KџяхI�������� � ���5� the MHS conformance testing specifications.�5µях��������¦TLРR � � аяхU��������T@Y@P�A� Each of the MHS test suites is specified in five parts:�A©ях�������� � � � � � аях2��������І�І�І�� - Declaration Part�Мях.��������І�І�І�� - Dynamic Part�Рях2�������� � � �� - Constraints Part�Мях:�������� � ���&� - TesхB� the behaviour tree.�!Йях��������¦TLРR � � јях�������� � � � � � аях\�������� � � �H� The test notation described here is based on the test notation�Hўях\�������� � � �H� called Tree and Tabular Combined Notation (TTCN) that has been�HўяхA�������� � � �-� developed jointly by ISO and CCITT.�-Ѕях�������� � � � � � аях^�������� � � �J� The notation described in this Recommendation is derived from an�J ях_�������� � �хю�ьях4������� � ��� � Annex A Test Notation� Кях”�of this Recommendation and describes�MќяхC���� � � �H� The test notation described here is based on the test notation�Hўях\�������� jях�������� � � � � � аях/�������� � � �� A.1 Introduction�Пях��������O��� � � � аяхa�������� � � �M� This annex is an integral part of this Recommendation and describes�MќяхJ�������� � � �6� the notation used in the test suite manuals.�6ґя