ETSI ETS 300 804-2 ed.1 (1998-02)

Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Circuit mode basic services; Data Link Layer (DLL); Part 2: Abstract Test Suite (ATS) specification

DE/ECMA-00108-2

Zasebno omrežje z integriranimi storitvami (PISN) - Medcentralni signalizacijski protokol - Osnovne storitve vodovnega načina - Podatkovna povezovalna plast (DLL) - 2. del: Abstraktni preskušalni niz (ATS) - Specifikacija

General Information

• Status: Published
• Publication Date: 09-Feb-1998
• Technical Committee: Ecma - Standardizing information and communications systems
• Current Stage: 12 - Completion
• Due Date: 13-Feb-1998
• Completion Date: 10-Feb-1998
• Mandate: T-245
• Ref Project: SIST ETS 300 804-2 E1:2005 - Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Circuit mode basic services; Data Link Layer (DLL); Part 2: Abstract Test Suite (ATS) specification

Standards Content (Sample)

SLOVENSKI STANDARD
SIST ETS 300 804-2 E1:2005
01-marec-2005
=DVHEQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL3,610HGFHQWUDOQLVLJQDOL]DFLMVNL
SURWRNRO2VQRYQHVWRULWYHYRGRYQHJDQDþLQD3RGDWNRYQDSRYH]RYDOQDSODVW
'//GHO$EVWUDNWQLSUHVNXãDOQLQL]$766SHFLILNDFLMD
Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Circuit
mode basic services; Data Link Layer (DLL); Part 2: Abstract Test Suite (ATS)
specification
Ta slovenski standard je istoveten z: ETS 300 804-2 Edition 1
ICS:
33.040.35 Telefonska omrežja Telephone networks
35.100.20 Podatkovni povezovalni sloj Data link layer
SIST ETS 300 804-2 E1:2005 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST ETS 300 804-2 E1:2005

---------------------- Page: 2 ----------------------

SIST ETS 300 804-2 E1:2005
EUROPEAN ETS 300 804-2
TELECOMMUNICATION February 1998
STANDARD
Source: ECMA Reference: DE/ECMA-00108-2
ICS: 33.020
Key words: ATS, circuit mode, layer 2, QSIG, PISN, PTN, testing
Private Integrated Services Network (PISN);
Inter-exchange signalling protocol;
Circuit mode basic services;
Data Link Layer (DLL);
Part 2: Abstract Test Suite (ATS) specification
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: [e-mail]
Tel.: [phone] - Fax: [phone]
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the
foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1998. All rights reserved.

---------------------- Page: 3 ----------------------

SIST ETS 300 804-2 E1:2005
Page 2
ETS 300 804-2: February 1998
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Editing and Committee Support Dept." at the address shown on the title page.

---------------------- Page: 4 ----------------------

SIST ETS 300 804-2 E1:2005
Page 3
ETS 300 804-2: February 1998
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Definitions and abbreviations .8
3.1 ETS definitions:.8
3.2 ISO definitions:.8
3.3 Abbreviations .8
4 Abstract Test Method (ATM).9
4.1 DLL protocol testing.9
4.2 Execution of test cases.9
4.2.1 Master-Slave testing.9
4.2.2 Handling of error indications.10
4.2.3 Test case execution sequence.10
4.3 Test step and default step structure .10
4.3.1 Preambles .10
4.3.2 Postambles.11
4.3.3 Check sequence.11
4.3.4 Defaults .11
4.4 Abstract Service Primitives (ASP) and Protocol Data Units (PDUs).11
4.4.1 Abstract Service Primitives (ASP).11
4.4.2 Protocol Data Units (PDUs).12
4.5 Timers and counters of ATS.12
4.6 Test strategy .12
5 ATS convention.12
5.1 Test case naming convention.13
5.2 Test case and test purpose mapping.13
5.3 ATS declaration part .13
5.3.1 Test suite type definitions.13
5.3.2 Test suite operations definitions.13
5.3.3 Test suite parameter declarations.13
5.3.4 Test case selection expression definitions.13
5.3.5 Test suite constant declarations.13
5.3.6 Test case variable declarations.13
5.3.7 Point of control and observation declarations .13
5.3.8 Timer declarations.14
5.3.9 ASP type definitions .14
5.3.10 PDU Type Definitions .14
5.4 ATS constraint part .14
5.5 ATS dynamic behaviour part.14
5.5.1 Implementation strategies .14
5.5.2 General conventions .15
Annex A (normative): Partial PIXIT proforma.16
A.1 Identification summary .16
A.2 Abstract Test Suite (ATS) summary.16
A.3 Test laboratory .16
A.4 Client identification .16

---------------------- Page: 5 ----------------------

SIST ETS 300 804-2 E1:2005
Page 4
ETS 300 804-2: February 1998
A.5 SUT. 16
A.6 Protocol layer information. 16
A.6.1 Protocol identification . 16
A.6.2 IUT information. 17
Annex B (normative): Protocol Conformance Test Report (PCTR) for PINX-DLL . 18
B.1 Identification summary. 18
B.1.1 Protocol conformance test report. 18
B.1.2 IUT identification. 18
B.1.3 Testing environment. 18
B.1.4 Limits and reservation . 18
B.1.5 Comments. 19
B.2 IUT conformance status . 19
B.3 Static conformance summary. 19
B.4 Dynamic conformance summary. 19
B.5 Static conformance review report . 19
B.6 Test campaign report. 20
B.7 Observations. 27
Annex C (normative): Abstract Test Suite (ATS) for PINX-DLL . 28
C.1 The TTCN Graphical form (TTCN.GR) .28
C.2 The TTCN Machine Processable form (TTCN.MP) . 28
History. 29

---------------------- Page: 6 ----------------------

SIST ETS 300 804-2 E1:2005
Page 5
ETS 300 804-2: February 1998
Foreword
This European Telecommunication Standard (ETS) has been produced by the standardizing Information
and Communication Systems Association (ECMA) on behalf of its members and those of the European
Telecommunications Standards Institute (ETSI).
This ETS comprises two parts with the generic title "Private Integrated Services Network (PISN);
Inter-exchange signalling protocol; Circuit mode basic services; Data Link Layer (DLL)". The title of each
part is listed below:
Part 1: "Test Suite Structure and Test Purposes (TSS & TPs)".
Part 2: "Abstract Test Suite Specification (ATS)".
Transposition dates
Date of adoption of this ETS: 23 January 1998
Date of latest announcement of this ETS (doa): 31 May 1998
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 30 November 1998
Date of withdrawal of any conflicting National Standard (dow): 30 November 1998

---------------------- Page: 7 ----------------------

SIST ETS 300 804-2 E1:2005
Page 6
ETS 300 804-2: February 1998
Blank page

---------------------- Page: 8 ----------------------

SIST ETS 300 804-2 E1:2005
Page 7
ETS 300 804-2: February 1998
1 Scope
This European Telecommunication Standard (ETS) contains the Abstract Test Suite (ATS) specification
for the Data Link Layer (DLL) of the Private Integrated Services Network (PISN), Inter-exchange signalling
protocol.
The objective of the present document is to provide conformance tests which give a high probability of
inter-operability of the Data Link Layer (DLL). The present document covers the procedures described in
ETS 300 402-2 [1] annex ZA.
The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [2],
ISO/IEC 9646-2 [3] and ISO/IEC 9646-3 [4]) is used as basis for the test methodology.
The present document is applicable for use in symmetrical application between two Private Integrated
Services Network eXchanges (PINXs)s and is also applicable to equipment when used in certain
scenarios that provide a continuous bit stream channel between two PINXs and will be referenced from
the standards which specifies the scenarios concerned.
ATS specifications for the Network Layer (NL) are provided in other parts of the Private Integrated
Services Network (PISN), Inter-exchange signalling protocol standards.
Annex A provides the Partial PIXIT proforma of this ETS.
Annex B provides the Protocol Conformance Test Report (PCTR) proforma of this ETS.
Annex C provides the Tree and Tabular Combined Notation (TTCN) part of this ETS.
2 Normative references
This ETS incorporates by dated and undated reference, provisions from other publications. These
normative references are cited in the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments or revisions to of any of these publications
apply to this ETS only when incorporated in it by amendment or revision. For undated references the latest
edition of the publication referred to applies.
[1] ETS 300 402-2 (1995): "User-network interface data link layer specification;
Application of CCITT Recommendations Q.920 and Q.921".
[2] ISO/IEC 9646-1: "Information Technology - OSI Conformance Testing
Methodology and Framework, Part 1: General Concepts".
[3] ISO/IEC 9646-2: "Information Technology - OSI Conformance Testing
Methodology and Framework, Part 2: Abstract Test Suite Specification".
[4] ISO/IEC 9646-3: "Information Technology - OSI Conformance Testing
Methodology and Framework, Part 3: The Tree and Tabular Combined
Notation".
[5] ISO/IEC 9646-5: "Information Technology - OSI Conformance Testing
Methodology and Framework, Part 5: Requirements on test laboratories and
clients for the conformance assessment process".
[6] ISO 7498: "Information Processing Systems - Open Systems Interconnection -
Basic Reference model".
[7] ETS 300 402-4 (1995): "Integrated Services Digital Network (ISDN); Digital
Subscriber Signalling System No. one (DSS1) protocol; Data link layer; Part 2:
General protocol specification [ITU-T Recommendation Q.921 (1993),
modified]".

---------------------- Page: 9 ----------------------

SIST ETS 300 804-2 E1:2005
Page 8
ETS 300 804-2: February 1998
[8] ETS 300 804-2 (1996): "Private Integrated Services Network (PISN); Inter-
exchange signalling protocol; Circuit mode basic services; Data Link Layer
(DLL); Part 2: Abstract Test".
3 Definitions and abbreviations
3.1 ETS definitions:
For the purposes of this ETS, the following definitions apply:
master: The Data Link entity that provides the functionality of the "network" as described in
ETS 300 402-2 [1] for a particular Data Link.
slave: The Data Link entity that provides the functionality of the "user" as described in
ETS 300 402-2 [1] for a particular Data Link.
3.2 ISO definitions:
For the purposes of this ETS, the following definitions apply:
Abstract Test Suite (ATS): see ISO/IEC 9646-1 [2]
Data Link Layer (DLL): see ISO 7498 [6]
Implementation Under Test (IUT): see ISO/IEC 9646-1 [2]
Lower Tester (LT): see ISO/IEC 9646-1 [2]
Network Layer (NWK): see ISO 7498 [6]
Physical Layer (PHL): see ISO 7498 [6]
Protocol Implementation Conformance Statement PICS proforma:see ISO/IEC 9646-1 [2]
PIXIT proforma: see ISO/IEC 9646-1 [2]
Point of Control and Observation (PCO): see ISO/IEC 9646-1 [2]
Protocol Implementation Conformance Statement (PICS): see ISO/IEC 9646-1 [2]
Protocol Implementation eXtra Information for Testing (PIXIT): see ISO/IEC 9646-1 [2]
System Under Test (SUT): see ISO/IEC 9646-1 [2]
Upper Tester (UT): see ISO/IEC 9646-1 [2]
3.3 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
ASP Abstract Service Primitive
ATM Abstract Test Method
ATS Abstract Test Suite
BI Invalid Behaviour
BO inOpportune Behaviour
BV Valid Behaviour
C/R Command/Response
DLL Data Link Layer
ETS Executable Test Suite
FCS Field Code Sequence
FSM Finite State Machine
GR GRaphics extension
ISO International Organization for Standardization
IUT Implementation Under Test
LT Lower Tester
MP Machine Procedure
NL Network Layer
PCO Point of Control and Observation
PCTR Protocol Conformance Test Report
PDU Protocol Data Unit
PH PHysical
PHL PHysical Layer
PICS Protocol Implementation Conformance Statements

---------------------- Page: 10 ----------------------

SIST ETS 300 804-2 E1:2005
Page 9
ETS 300 804-2: February 1998
PINX Private Integrated Services Network eXchange
PISN Private Integrated Services Network
PIXIT Protocol Implementation eXtra Information for Testing
PSAP PHL Service Access Point
SUT System Under Test
TP Test Purpose
TTCN Tree and Tabular Combined Notation
UT Upper Tester
4 Abstract Test Method (ATM)
This clause describes the ATM, which defines the abstract testing architecture applied in the ATS. The
remote test method is the basic method used for DLL conformance testing. However, certain DLL Test
Purposes (TPs) also need part of the NWK functions (e.g. I-frame transmission), consequently the
embedded variant of the remote test method is used.
4.1 DLL protocol testing
The DLL implementations do not offer a direct access to the upper service boundary. The Remote test
method is selected because any co-ordination procedures can only be expressed in an informal way.
LT: A Lower Tester (LT) is located in a remote DLL test system. It controls and
observes the behaviours of the IUT.
PCO: The Point of Control and Observation (PCO) for DLL testing is located on the
PHL Service Access Point (PSAP). All test events at the PCO are specified in
terms of PH-Data Abstract Service Primitives (ASPs) and DLL Protocol Data
Units (PDUs). A single PCO is defined for DLL testing.
notional UT: A notional Upper Tester (UT), i.e. the upper layer (NWK layer) of the System
Under Test (SUT) is invoked to implement the functions of the upper tester
(NWK functions) without any additional mechanism being installed.
Figure 1: The Remote test method applied to the DLL testing
4.2 Execution of test cases
4.2.1 Master-Slave testing
Regarding the DLL protocol, the interface is almost symmetrical. The naming and structure of the DLL
ATS were developed for any side testing. To apply the DLL ATS for slave or master side testing, only the
values of the Command/Response (C/R) field have to be reversed. To configure the ATS data for master
side or slave side testing the TSPX_MASTER parameter has to be set as described in table 1.

---------------------- Page: 11 ----------------------

SIST ETS 300 804-2 E1:2005
Page 10
ETS 300 804-2: February 1998
Table 1: Master-Slave parameter
Master Slave
TSPX_MASTER TRUE FALSE
4.2.2 Handling of error indications
During the execution of the DLL ATS many MDL-ERROR-IND primitives will be sent to the system
management due to the invalid and inopportune test cases. It is up to the IUT supplier to take the
necessary precautions to avoid any impact on the test result.
Some tests use NWK procedures to test DLL functions. It is not always possible to handle the NWK
procedures properly. The effects of such faulty NWK messages and procedures are out of the scope of
the DLL ATS. It is up to the IUT supplier to take the necessary precautions to avoid any impact on the test
result.
4.2.3 Test case execution sequence
There is no restriction concerning the execution sequence of the DLL test cases, but to facilitate the
analysis of the test results the execution sequence Valid Behaviour (BV), Inopportune Behaviour (BO),
Invalid Behaviour (BI) should be applied.
4.3 Test step and default step structure
The common dynamic behaviour is described in test steps as shown in figure 2. These can be called from
any test case.
STEP--------|--PREAMBLE
       |
       |--POSTAMBLE
       |
       |--CHECKSEQUENCE
       |
DEFAULT-----|
Figure 2: Test step and default structure
4.3.1 Preambles
The preamble test group contains the preamble test steps needed for initialization of the IUT before
testing a particular test purpose.
PR40_001 To bring the IUT into state 4.0.
PR50_001 To bring the IUT into state 5.0.
PR51_001 To bring the IUT into state 5.1.
PR51_002 To bring the IUT into state 5.1, with one I_Frame in queue and V(S)=V(A).
PR60_001 To bring the IUT into state 6.0.
PR70_001 To bring the IUT into state 7.0.
PR70_002 To bring the IUT into state 7.0, with one I_Frame exchange.
PR70_003 To bring the IUT into state 7.0, with V(S)=V(A) + 2.
PR71_001 To bring the IUT into state 7.1.
PR74_001 To bring the IUT into state 7.4.
PR74_002 To bring the IUT into state 7.4, with V(S)=V(A) + 2.
PR74_003 To bring the IUT into state 7.4, with DL_DATA_Request pending.
PR75_001 To bring the IUT into state 7.5.
PR80_001 To bring the IUT into state 8.0.
PR80_002 To bring the IUT into state 8.0, with V(S)=V(A) + 2.

---------------------- Page: 12 ----------------------

SIST ETS 300 804-2 E1:2005
Page 11
ETS 300 804-2: February 1998
PR81_001 To bring the IUT into state 8.1.
PR84_001 To bring the IUT into state 8.4.
PR84_002 To bring the IUT into state 8.4, with V(S)=V(A) + 2.
PR85_001 To bring the IUT into state 8.5.
4.3.2 Postambles
The postamble test group contains the postamble test steps needed for termination of the IUT to place it
in the same state after testing each test purpose.
PO40_001 To place the IUT is in state 4.0 at the end of the test.
4.3.3 Check sequence
In tables D-1 to D-3 of ETS 300 402-2 [1], it is possible to identify the state of the IUT. The states 7.2, 7.3,
7.6, 7.7, 8.2, 8.3, 8.6, 8.7 are not checked as it is not possible to bring the IUT into these states. The
states 5.0, 5.1, 5.2, 6.0 are not checked because they are transitional states between state 4.0 and
state 7.0.
CS40_001 To check if the IUT is in state 4.0 at the end of the test.
CS70_001 To check if the IUT is in state 7.0 at the end of the test with RR/P exchange.
CS70_002 To check if the IUT is in state 7.0 at the end of the test with I/P=1 frame out of
sequence.
CS71_001 To check if the IUT is in state 7.1 at the end of the test.
CS71_002 To check if the IUT is in state 7.1 at the end of the test.
CS74_001 To check if the IUT is in state 7.4 at the end of the test.
CS74_002 To check if the IUT is in state 7.4 at the end of the test.
CS75_002 To check if the IUT is in state 7.5 at the end of the test.
CS80_002 To check if the IUT is in state 8.0 at the end of the test.
CS81_002 To check if the IUT is in state 8.1 at the end of the test.
CS84_002 To check if the IUT is in state 8.4 at the end of the test.
CS85_002 To check if the IUT is in state 8.5 at the end of the test.
4.3.4 Defaults
The default subclause describes the behaviour of the tester following the receipt of an unexpected event.
DFLT_001 Sub-tree for TEI-assigned, Awaiting Establishment, Awaiting Release states.
DFLT_002 Sub-tree for Multiple Frame Operation and Timer Recovery states.
4.4 Abstract Service Primitives (ASP) and Protocol Data Units (PDUs)
4.4.1 Abstract Service Primitives (ASP)
Five ASPs are defined:
- PH_DATA_RQ
- PH_DATA_IN
- PH_ACT_RQ
- PH_ACT_IN
- PH_DEACT_IN
The PHysical (PH)-data frame is based on the frame structure described in ETS 300 402-2 [1], clause 2
(and subclauses) and in figure 1/Q.921. It contains the address field, the control field, the information field
if necessary and the Field Code Sequence (FCS) field. The value of the FCS field is usually supplied by
the physical layer of the tester, but for testing of some invalid behaviour it is necessary to change this
value. The flag sequence is supplied by the physical layer of the tester.

---------------------- Page: 13 ----------------------

SIST ETS 300 804-2 E1:2005
Page 12
ETS 300 804-2: February 1998
4.4.2 Protocol Data Units (PDUs)
The PDUs defined are based on the frame types described in ETS 300 402-2 [1], table 5/Q.921.
4.5 Timers and counters of ATS
This clause describes the timers and counters used in the ATS. The "min" and "max" indications define
that the timer value represents the minimum or maximum tolerance of a timer.
Table 2: ATS Timers
ATS timer ATS default timer value Standard timer Reference to ETS
name name
T200_min 950 ms T200 ETS 300 402-2 [1]
T200_max 1050 ms clause 5.9.1
T203_min 9500 ms T203 ETS 300 402-2 [1]
T203_max 10500 ms clause 5.9.8
ATS timer ATS default timer value Comments
name
T_AC T200 value/5 ms Watch dog timer if an ACtion from the IUT is
expected.
T_NOAC T200 value x N200 s Guard timer if NO ACtion shall appear.
T_WAIT 30 s Used by the tester for test synchronization
with external procedure (maximum time for
an IMPLICIT SEND execution
T_S4_max 6 s Maximum time to send SABME for an IUT
unstable in state S4.0.
T_READ 30 s Used in value and tolerance timer test
T_NWK PIXIT item Maximum time for a response generated by
NWK layer
Table 3: ATS Counters
ATS counter ATS default Comments Reference to ETS
name counter value
N200 3 Corresponding counter variable: ETS 300 402-2 [1],
RC clause 5.9.2
N201 260 Maximum number of octets in ETS 300 402-2 [1],
an information field clause 5.9.3
4.6 Test strategy
The ATS will rebuild the DLL functions. Therefore the test case variables N(S) and N(R) are implemented
and used according to their functions described in ETS 300 402-2 [1] .
The C/R bit of the address field is implemented as a return value of a test suite operation definition
(i.e. external ATS function), to allow the test suite to be used for master testing as well as for slave testing.
Using the tables D-1 to D-3 of ETS 300 402-2 [1] and to attempt to cover a maximum of test events with
an appropriate number of test cases the following selection criteria have been applied:
- the complete valid value ranges of the state variables V(S) and V(R) and the sequence numbers
N(S) and N(R) are not covered;
- state transitions that are defined by the characters "\" "/" "|", or that are empty are not covered.
5 ATS convention
This clause describes the conventions applied to define the ATS.

---------------------- Page: 14 ----------------------

SIST ETS 300 804-2 E1:2005
Page 13
ETS 300 804-2: February 1998
5.1 Test case naming convention
The identifier of the test cases is built according to the scheme in figure 3.
Identifier: TC_
   = state (4-8)
  = sub-state (0-7)
 = sequential number (001-300) BV, Valid Behaviour tests
(301-600) BO, Inopportune Behaviour tests
(601-900) BI, Invalid Behaviour tests
Figure 3: Test case naming convention
5.2 Test case and test purpose mapping
A test case is associated with a test purpose that has the same number, e.g.: TC74_302 is associated
with TP74-302. For TTCN syntactical reason, the character "-" in test purpose identifier is replaced by the
character "_" in test case identifier.
5.3 ATS declaration part
Complete names as defined in the standard are used for identifier names of declarations.
5.3.1 Test suite type definitions
The identifier names are written in uppercase.
5.3.2 Test suite operations definitions
The identifier names commence with test suite operations.
5.3.3 Test suite parameter declarations
The identifier names are written in uppercase and commences with test suite parameters.
5.3.4 Test case selection expression definitions
The identifier names are written in uppercase.
5.3.5 Test suite constant declarations
The identifier names commence with test suite constant. If the constant is representing a system
parameter or value, only the system name is used, e.g. N200.
5.3.6 Test case variable declarations
The identifier names are written in uppercase.
5.3.7 Point of control and observation declarations
The identifier name for point of control and observation is PHL.

---------------------- Page: 15 ----------------------

SIST ETS 300 804-2 E1:2005
Page 14
ETS 300 804-2: February 1998
5.3.8 Timer declarations
The identifier names of Timers commence with T (e.g. T01). The names as defined in the present
document are used.
5.3.9 ASP type definitions
The identifier names defined in the referenced standard are used, e.g.:
PH_DATA_Request;
PH_ACTIVATE_Indication.
5.3.10 PDU Type Definitions
The identifier names are written with words separated with "_". The first letter of each word is in uppercase
and the other letters in lowercase. For generic PDU names (i.e. information, supervisory or unnumbered)
only the first letter is used and written in uppercase, e.g.:
Empty_I_Frame;
Invalid_S_Frame.
5.4 ATS constraint part
ASP constraint identifier names are written in both uppercase and lowercase. The identifier name is
written as suitably as possible, e.g.:
Ph_Act_Rq for PH_ACTIVATE_Request;
RR_Cs for an RR command frame to be sent included in the ASP.
...