SIST I-ETS 300 490-1 E1:2003

SLOVENSKI STANDARD
01-december-2003
Terminalska oprema (TE) – Prenos datotek prek digitalnega omrežja z integriranimi
storitvami (ISDN) – Specifikacija preskušanja skladnosti – 1. del: Proforma izjava o
skladnosti izvedbe (ICS) profila za profil EUROFILE (ETS 300 383)
Terminal Equipment (TE); File transfer over the Integrated Services Digital Network
(ISDN); Conformance testing specification; Part 1: Profile Implementation Conformance
Statement (ICS) proforma for the EUROFILE profile (ETS 300 383)
Ta slovenski standard je istoveten z: I-ETS 300 490-1 Edition 1
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
35.180 Terminalska in druga IT Terminal and other
periferna oprema IT peripheral equipment
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

INTERIM
EUROPEAN I-ETS 300 490-1
TELECOMMUNICATION September 1996
STANDARD
Source: ETSI TC-TE Reference: DI/TE-01044-1
ICS: 33.080, 35.180
Key words: ISDN, file transfer, EUROFILE
Terminal Equipment (TE);
File transfer over the Integrated Services Digital Network (ISDN);
Conformance testing specification;
Part 1: Profile Implementation Conformance Statement (ICS)
proforma for the EUROFILE profile (ETS 300 383)
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: secretariat@etsi.fr
Tel.: +33 92 94 42 00 - Fax: +33 93 65 47 16
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 1996. All rights reserved.

Page 2
I-ETS 300 490-1: September 1996
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 3
I-ETS 300 490-1: September 1996
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Definitions and abbreviations .7
3.1 Definitions .7
3.2 Abbreviations .7
4 Conformance requirement concerning profile ICS.7
Annex A (normative): PICS proforma.9
Annex B (normative): Profile Requirement List (RL) for ETS 300 383.10
B.1 Requirements.10
B.2 General options of the profile as a whole.11
B.3 A list of the specifications selected and combined in the profile .11
B.4 References to the provisional PICS proforma for ETS 300 075 .11
B.5 Restrictions for PICS proforma .11
B.5.1 Purposes and structure.11
B.5.2 Static requirements.12
B.5.2.1 Roles .12
B.5.2.2 Service classes .12
B.5.2.2.1 Protocol classes - Regimes.12
B.5.2.2.2 Functional units.13
B.5.2.2.3 Service elements .13
B.5.2.3 Handling capabilities.13
B.5.2.4 Protocol Data Units (PDUs).14
B.5.2.4.1 Association PDUs.14
B.5.2.4.1.1 Association PDUs/Association
establishment.14
B.5.2.4.2 Access PDUs.14
B.5.2.4.2.1 Access PDUs/Access establishment.14
B.5.2.4.2.2 Access PDUs/Access end .14
B.5.2.4.3 Transfer PDUs.15
B.5.2.4.3.1 Transfer PDUs/File directory .15
B.5.2.4.3.2 Transfer PDUs/Load service.15
B.5.2.4.3.3 Transfer PDUs/Save service .15
B.5.2.4.3.4 Transfer PDUs/Rename service.15
B.5.2.4.3.5 Transfer PDUs/Delete service .15
B.5.2.4.3.6 Transfer PDUs/Typed_Data service.16
B.5.2.4.4 Mass Transfer PDUs .16
B.5.2.4.4.1 Mass Transfer PDUs/Write service .16
B.5.2.5 PDU parameters.17
B.5.2.5.1 Parameters of association PDUs.17
B.5.2.5.1.1 Association establishment request
parameters.17
B.5.2.5.1.2 Association establishment response
parameters.19
B.5.2.5.1.3 Association release parameters .20

Page 4
I-ETS 300 490-1: September 1996
B.5.2.5.1.4 Association abort parameters . 21
B.5.2.5.2 Parameters of access PDUs. 22
B.5.2.5.2.1 Access establishment request
parameters. 22
B.5.2.5.2.2 Access establishment response
parameters. 25
B.5.2.5.2.3 End access request parameters . 26
B.5.2.5.2.4 End access response parameters . 27
B.5.2.5.3 Parameters of transfer PDUs. 28
B.5.2.5.3.1 File directory parameters . 28
B.5.2.5.3.2 File load parameters . 29
B.5.2.5.3.3 File save parameters. 31
B.5.2.5.3.4 File rename parameters. 32
B.5.2.5.3.5 File delete parameters . 34
B.5.2.5.3.6 Typed Data parameters . 35
B.5.2.5.3.7 Write parameters . 36
B.5.2.5.3.8 Write End parameters. 37
Annex C (normative): Profile ICS proforma . 39
C.1 Additional questions. 40
C.1.1 Profile specific reason parameter values . 40
C.1.2 Profile specific access user data field parameter values . 41
C.1.3 Profile specific names for navigation services . 43
Annex D (informative): Bibliography . 44
History. 45

Page 5
I-ETS 300 490-1: September 1996
Foreword
Part 1 of this Interim European Telecommunication Standard (I-ETS) has been produced by the Terminal
Equipment (TE) Technical Committee of the European Telecommunications Standards Institute (ETSI).
An ETSI standard may be given I-ETS status either because it is regarded as a provisional solution ahead
of a more advanced standard, or because it is immature and requires a "trial period". The life of an I-ETS
is limited to three years after which it can be converted into an ETS, have it's life extended for a further
two years, be replaced by a new version, or be withdrawn.
This is the first part of an I-ETS which comprises three parts as follows:
"Terminal Equipment (TE); File transfer over the Integrated Services Digital Network (ISDN);
Conformance testing specification:
Part 1: Profile Implementation Conformance Statement (ICS) proforma for the EUROFILE
profile (ETS 300 383);
Part 2: Profile Test Specification Summary (PTS-Summary) for the EUROFILE profile ETS 300 383);
Part 3: Profile Specific Test Specification (PSTS) for the EUROFILE profile (ETS 300 383).
Proposed announcement date
Date of adoption of this I-ETS: 30 August 1996
Date of latest announcement of this I-ETS (doa): 31 December 1996

Page 6
I-ETS 300 490-1: September 1996
Blank page
Page 7
I-ETS 300 490-1: September 1996
1 Scope
Part 1 of this Interim European Telecommunication Standard (I-ETS) provides a Profile Implementation
Conformance Statement (Profile ICS) proforma for ETS 300 383 [4], in compliance with the relevant
requirements and in accordance with the relevant guidance, given in ISO/IEC DIS 9646-7 [2].
2 Normative references
Part 1 of this I-ETS incorporates by dated or undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply to this part of the I-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 075 (1994): "Terminal Equipment (TE); Processable data, File
transfer".
[2] ISO/IEC DIS 9646-7 (1993): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 7:
Implementation Conformance Statements".
[3] ITU-T Recommendation T.51 (1993): "Coded character sets for telematic
services".
[4] ETS 300 383 (1995): "Integrated Services Digital Network (ISDN); File transfer
over the ISDN EUROFILE transfer profile".
[5] I-ETS 300 491-1 (1995): "Terminal Equipment (TE); Conformance testing for file
transfer over the Integrated Services Digital Network (ISDN); Part 1: ETS 300
075 Protocol Implementation Conformance Statement (PICS) proforma".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this part of the I-ETS, the definitions supplied in ISO/IEC DIS 9646-7 [2],
ETS 300 075 [1] and ETS 300 383 [4] apply.
3.2 Abbreviations
For the purposes of this part of the I-ETS, the following abbreviations apply:
BK Basic Kernel
ICS Implementation Conformance Statement
ISDN Integrated Services Digital Network
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
Profil Sts Profile Status
Proto Sts Protocol Status
RL Requirement List
Spt Support
SS or Sym. Service Symmetrical Service
Sts Status
SUT System Under Test
TDU Telesoftware Data Unit
TE Terminal Equipment
TTCN Tree and Tabular Combined Notation
4 Conformance requirement concerning profile ICS
The supplier of a profile implementation which is claimed to conform to ETS 300 383 [4] shall complete a
copy of the Protocol Implementation Conformance Statement (PICS) proforma provided in

Page 8
I-ETS 300 490-1: September 1996
I-ETS 300 491-1 [5], annex A and the profile specific ICS proforma provided in annex C of this part of the
I-ETS. The supplier shall fill in the information necessary to identify both the supplier and the
implementation. It shall disregard all requirements described in annex B to this part of the I-ETS.

Page 9
I-ETS 300 490-1: September 1996
Annex A (normative): PICS proforma
Only one PICS proforma shall be used in this Profile ICS. It refers to the PICS proforma of
I-ETS 300 491-1 [5].
The supplier of a profile implementation which is claimed to conform to ETS 300 383 [4] shall complete a
copy of the PICS proforma provided in I-ETS 300 491-1 [5], annex A and shall provide the information
necessary to identify both the supplier and the implementation.

Page 10
I-ETS 300 490-1: September 1996
Annex B (normative): Profile Requirement List (RL) for ETS 300 383
This Profile RL refers to I-ETS 300 491-1 [5].
B.1 Requirements
The following requirements are described in clause B.5, tables B.1 to B.49:
B.1 Implicit roles . 12
B.2 Roles . 12
B.3 Service classes . 12
B.4 Regimes . 12
B.5 Functional units : services. 13
B.6 Service elements. 13
B.7 Negotiation capabilities in symmetrical service. 14
B.8 PDU/Association establishment . 14
B.9 PDU/Access establishment. 14
B.10 PDU/Access end . 14
B.11 PDU/Directory service. 15
B.12 PDU/Load service . 15
B.13 PDU/Save service . 15
B.14 PDU/Rename service. 15
B.15 PDU/Delete service. 15
B.16 PDU/Typed data service . 16
B.17 PDU/Write service. 16
B.18 Association establishment/Request parameters. 17
B.18.1 Application name parameter values . 18
B.18.2 Service class parameter values. 18
B.18.3 Identification parameter values. 18
B.19 Association establishment/Response_pos parameters . 19
B.20 Association establishment/Response_neg parameters . 19
B.20.1 Reason parameter values for response negative. 20
B.21 Association release/Response_pos parameters. 20
B.22 Association abort/Request parameters. 21
B.22.1 Reason parameter values for service provider. 21
B.22.2 Reason parameter values for service user. 21
B.23 Access establishment/Request parameters. 22
B.23.1 Function parameter details/Primitives handled. 23
B.23.2 User data details/First byte coding . 23
B.23.3 User data details/Second byte coding . 24
B.24 Access establishment/Response_pos parameters. 25
B.25 Access establishment/Response_neg parameters. 26
B.25.1 Reason parameter values for Response Negative. 26
B.26 End access/Request parameters. 26
B.26.1 Reason parameter values for service user. 27
B.27 End access/Response_pos parameters . 27
B.28 File directory/Request parameters . 28
B.29 File directory/Response_pos parameters . 28
B.30 File directory/Response_neg parameters . 28
B.30.1 Reason parameter values for Response Negative. 29
B.31 File load/Request parameters . 29
B.32 File load/Response_pos parameters . 30
B.33 File load/Response_neg parameters . 30
B.33.1 Reason parameter values for Response Negative. 30
B.34 File save/Request parameters . 31
B.35 File save/Response_pos parameters. 31
B.36 File save/Response_neg parameters . 31
B.36.1 Reason parameter values for Response Negative. 32
B.37 File rename/Request parameters. 32
B.38 File rename/Response_pos parameters. 33
B.39 File rename/Response_neg parameters. 33
B.39.1 Reason parameter values for Response Negative. 33
B.40 File delete/Request parameters . 34

Page 11
I-ETS 300 490-1: September 1996
B.41 File delete/Response_pos parameters.34
B.42 File delete/Response_neg parameters.34
B.42.1 Reason parameter values for Response Negative .35
B.43 Typed_Data/Request parameters.35
B.44 Write/Request parameters.36
B.45 Write/Response_pos parameters.36
B.45.1 Write/Response_pos block number parameter values .36
B.46 Write/Response_neg parameters.37
B.47 Write End/ Request parameters .37
B.48 Write End/Response_pos parameters.38
B.49 Write End/Response_neg parameters .38
B.49.1 Write End response negative result parameter values .38
B.49.2 Reason values for Response Negative.39
B.2 General options of the profile as a whole
The following clauses describe the changes from I-ETS 300 491-1 [5], annex A. They are additional
constraints and are conformant with ETS 300 383 [4].
B.3 A list of the specifications selected and combined in the profile
This clause describes all relevant specifications and profiles giving the basis for this annex. The following
ETSs and I-ETS are used:
- ETS 300 075 [1];
- ETS 300 383 [4];
- I-ETS 300 491-1 [5].
B.4 References to the provisional PICS proforma for ETS 300 075
The references used in the following tables are identical to those given in I-ETS 300 491-1 [5]. Associated
tables are described with same header text as in ETS 300 075 [1]. Tables without changes are not
contained in this annex.
B.5 Restrictions for PICS proforma
B.5.1 Purposes and structure
The purpose of this Profile RL is to provide requirements referring to I-ETS 300 491-1 [5] in respect to
ETS 300 383 [4]. References with A (e.g. A.6/5; table A.6, item number 5) reference I-ETS 300 491-1 [5],
annex A.
The Profile RL proforma is subdivided into divisions and subdivisions for the following categories of
information:
- implementation details;
- protocol details;
- overall conformance claim;
- static requirements:
1) roles;
2) major capabilities;
3) negotiation capabilities;
4) Protocol Data Units;
5) Protocol Data Units parameters.
The abbreviations used are those defined in I-ETS 300 491-1 [5].

Page 12
I-ETS 300 490-1: September 1996
B.5.2 Static requirements
B.5.2.1 Roles
Table B.1: Implicit roles
Item No. Role Ref. Protocol Profile
status status
Master 4.1.2.2.3 o.1 m
2 Slave 4.1.2.2.3 o.1 m
o.1 it is mandatory to support at least one of these options.
Table B.2: Roles
Item No. Role Ref. Protocol Profile
status status
Master 4.1.2.2.3 o.2 m
2 Slave 4.1.2.2.3 o.2 m
Sender 4.1.2.2.3 o.3 m
4 Receiver 4.1.2.2.3 o.3 m
o.2 it is mandatory to support at least one of these options.
o.3 it is mandatory to support at least one of these options.
B.5.2.2 Service classes
Table B.3: Service classes
Item No. Service class Ref. Protocol Profile
status status
Basic kernel 4.1.3.1.2.1 o.4 i
2 Symmetrical service 4.1.3.1.2.1 o.4 m
o.4 it is mandatory to support at least one of the two service classes.
B.5.2.2.1 Protocol classes - Regimes
Table B.4: Regimes
Item No. Regime Ref. Protocol Profile
status status
1 Association 4.1.2.3.2 m m
2 Access 4.1.2.3.3 c1 m
Transfer 4.1.2.3.4 m m
c1 IF symmetrical service supported THEN m ELSE n/a.

Page 13
I-ETS 300 490-1: September 1996
B.5.2.2.2 Functional units
Table B.5: Functional units: services
Item No. Service Ref. Protocol Profile
status status
File directory service 4.1.4.3 c2 m
2 Load service 4.1.4.4 c2 m
3 Save service 4.1.4.5 c2 m
Rename service 4.1.4.6 c2 o
5 Delete service 4.1.4.7 c2 o
Typed Data transfer 4.1.4.8 c2 o
7 Mass transfer service 4.1.5.1 m m
8 Exception report service 4.1.5.2 m m
c2 IF symmetrical service supported THEN o ELSE n/a.
B.5.2.2.3 Service elements
Table B.6: Service elements
Item No. Service Ref. Role: Master Role: Slave
Proto Profil Proto Profil
Sts Sts Sts Sts
T_ASSOCIATE 4.1.2.3.1 m m m m
2 T_RELEASE 4.1.2.3.1 m m m m
3 T_U_ABORT 4.1.2.3.1 c3 m m m
T_P_ABORT 4.1.2.3.1 c3 m c3 m
5 T_ACCESS 4.1.2.3.1 c3 m c3 m
T_END_ACCESS 4.1.2.3.1 c3 m c3 m
7 T_DIRECTORY 4.1.2.3.1 c4 m c4 m
8 T_LOAD 4.1.2.3.1 c4 m c4 m
T_SAVE 4.1.2.3.1 c4 m c4 m
10 T_RENAME 4.1.2.3.1 c5 o c5 o
T_DELETE 4.1.2.3.1 c5 o c5 o
12 T_TYPED_DATA 4.1.2.3.1 c5 o c5 o
1) 1) 2) 2)
13 T_WRITE 4.1.2.3.1 m m m m
1) 1) 2) 2)
T_WRITE_END 4.1.2.3.1 m m m m
15 T_U_EXCEPT 4.1.2.3.1 c3 m m m
T_P_EXCEPT 4.1.2.3.1 c5 m c5 m
c3 IF symmetrical service supported THEN m ELSE n/a.
c4 IF basic transfer mode used THEN n/a ELSE c5.
c5 IF symmetrical service supported THEN o ELSE n/a.
1)
Corresponding to a Request.
2)
Corresponding to a Response.
B.5.2.3 Handling capabilities
The supplier of the implementation shall provide information to describe the negotiation options available
in the protocol, and indicate those implemented, in the box below.
Those negotiation capabilities are only available in symmetrical service. The use of these services is
negotiated during the Access regime establishment.

Page 14
I-ETS 300 490-1: September 1996
Table B.7: Capabilities in symmetrical service
Item No. Service handled Ref. Role: Master Role: Slave
Proto Profil Proto Profile
Sts Sts Sts Sts
File directory service 4.1.4.1.2.2 n/a n/a c6 m
2 Load service 4.1.4.1.2.2 n/a n/a c6 m
Save service 4.1.4.1.2.2 n/a n/a c6 m
4 Rename service 4.1.4.1.2.2 n/a n/a o o
5 Delete service 4.1.4.1.2.2 n/a n/a o o
Typed Data service 4.1.4.1.2.2 o o o o
7 Exception report 4.1.4.1.2.2 o m o m
Basic Transfer Mode 4.1.4.1.2.6 o n/a o n/a
c6 IF Basic Transfer Mode is used THEN n/a ELSE o.
B.5.2.4 Protocol Data Units (PDUs)
B.5.2.4.1 Association PDUs
B.5.2.4.1.1 Association PDUs/Association establishment
Table B.8: PDU/Association establishment
Item No. PDU type Ref Protocol Profile
status status
1 T_ASSOCIATE Request 4.1.3.1.1 m m
T_ASSOCIATE Response 4.1.3.1.1 c7 m
c7 IF symmetrical service supported THEN m ELSE o.
B.5.2.4.2 Access PDUs
B.5.2.4.2.1 Access PDUs/Access establishment
Table B.9: PDU/Access establishment
Item No. PDU type Ref. Protocol Profile
status status
1 T_ACCESS Request 4.1.4.1.1 c8 m
T_ACCESS Response 4.1.4.1.1 c8 m
c8 IF A.6/5 THEN m ELSE n/a.
B.5.2.4.2.2 Access PDUs/Access end
Table B.10: PDU/Access end
Item No. PDU type Ref. Protocol Profile
status status
1 T_END_ACCESS Request 4.1.4.2.1 c9 m
2 T_END_ACCESS Response 4.1.4.2.1 c9 m
c9 IF A.6/6 THEN m ELSE n/a.
Page 15
I-ETS 300 490-1: September 1996
B.5.2.4.3 Transfer PDUs
B.5.2.4.3.1 Transfer PDUs/File directory
Table B.11: PDU/Directory service
Item No. PDU type Ref. Protocol Profile
status status
T_DIRECTORY Request 4.1.4.3.1 c10 m
2 T_DIRECTORY Response 4.1.4.3.1 c10 m
c10 IF A.6/7 THEN m ELSE n/a.
B.5.2.4.3.2 Transfer PDUs/Load service
Table B.12: PDU/Load service
Item No. PDU type Ref. Protocol Profile
status status
1 T_LOAD Request 4.1.4.4.1 c11 m
2 T_LOAD Response 4.1.4.4.1 c11 m
c11 IF A.6/8 THEN m ELSE n/a.
B.5.2.4.3.3 Transfer PDUs/Save service
Table B.13: PDU/Save service
Item No. PDU type Ref. Protocol Profile
status status
1 T_SAVE Request 4.1.4.5.1 c12 m
T_SAVE Response 4.1.4.5.1 c12 m
c12 IF A.6/9 THEN m ELSE n/a.
B.5.2.4.3.4 Transfer PDUs/Rename service
Table B.14: PDU/Rename service
Item No. PDU type Ref. Protocol Profile
status status
T_RENAME Request 4.1.4.6.1 c13 o
2 T_RENAME Response 4.1.4.6.1 c13 o
c13 IF A.6/10 THEN m ELSE n/a.
B.5.2.4.3.5 Transfer PDUs/Delete service
Table B.15: PDU/Delete service
Item No. PDU type Ref. Protocol Profile
status status
1 T_DELETE Request 4.1.4.7.1 c14 o
2 T_DELETE Response 4.1.4.7.1 c14 o
c14 IF A.6/11 THEN m ELSE n/a.

Page 16
I-ETS 300 490-1: September 1996
B.5.2.4.3.6 Transfer PDUs/Typed_Data service
Table B.16: PDU/Typed Data service
Item No. PDU type Ref. Protocol Profile
status status
T_TYPED_DATA Request 4.1.4.8.1 c15 o
c15 IF A.6/12 THEN m ELSE n/a.
B.5.2.4.4 Mass Transfer PDUs
B.5.2.4.4.1 Mass Transfer PDUs/Write service
Table B.17: PDU/Write service
Item No. PDU type Ref. Protocol Profile
status status
T_WRITE Request 4.1.5.1.1 m m
2 T_WRITE Response 4.1.5.1.1 o m

B.5.2.5 PDU parameters
B.5.2.5.1 Parameters of association PDUs
B.5.2.5.1.1 Association establishment request parameters
Table B.18: Association establishment/Request parameters
Item No. Parameter Ref. Proto Profil Values allowed by
Sts Sts
protocol profile
1 Called address 7.1.2.1.3 c16 o string of 1 - 254 bytes string of 1 - 254 bytes
Calling address 7.1.2.1.4 c16 o string of 1 - 254 bytes string of 1 - 254 bytes
3 Application name 7.1.2.1.5 m m see table B.18.1 '21'H + '4B'H ("!K")
Application response timeout 7.1.2.1.6 o o 0 0
1 s - 255 s 1 s - 255 s
5 Service Class 7.1.2.1.7 m m see table B.18.2 '10'B
6 Explicit confirmation 7.1.2.1.8 m m '08'H: explicit confirmation (default value) default: "00001000"B ("08"H)
"00"H: no explicit confirmation else: "????1???"B
7 Identification 7.1.2.1.9 c16 o see table B.18.3 see table B.18.3
8 Request identifier 7.1.2.1.10 c16 o "0" B: no identifier requested "0"B: no identifier requested
"1" B: identifier requested "1"B: identifier requested
User data 7.1.2.1.11 o o string of 1 - 254 bytes coded in accordance string of 1 - 254 bytes coded in
with ITU-T Recommendation T.51 [3] accordance with ITU-T
Recommendation T.51 [3]
c16 IF A.3/2 THEN o ELSE n/a.
Page 17
I-ETS 300 490-1: September 1996

Page 18
I-ETS 300 490-1: September 1996
Table B.18.1: Application name parameter values
Item No. Application name Ref. Proto Profil Values allowed by
Sts Sts
protocol profile
1 Non standardized name 7.1.2.1.5 o i first byte different from 21 H +
string of 0 - 15 bytes
Standardized applications 7.1.2.1.5 o m "21"H + string of 0 - 15 bytes "21"H + "4B"H
Table B.18.2: Service class parameter values
Item No. Service class Ref. Proto Profil Values allowed by
Sts Sts
protocol profile
1 Basic Kernel 7.1.2.1.7 o.5 i "01" B
2 Symmetrical Service 7.1.2.1.7 o.5 m "10" B "10"B
Basic Kernel and Symmetrical Service 7.1.2.1.7 o.5 i "11" B
o.5 it is mandatory to support at least one of these values.
Table B.18.3: Identification para
...