Security
Page No.
REQUIREMENT SPECIFICATION
Public
1 (16)
Prepared
Document responsible/Approved
Göran Engström
Stefan Andersson
Date
Rev
2004-02-24
C
Linked to object
No.
LZBA 506 403/4
Primary Rate Access,
Layer 1-3
Contents
Page
4
4.1
Primary Rate Access
Scope
2
2
4.2
Normative references
2
4.3
Layer 1 - Physical interface
3
4.4
Layer 2 - Data link protocol
3
4.5
Layer 3 - Signalling protocol
4
4.5.1
EN 300 403-1
4
4.5.2
Q.850
12
4.5.3
EN 300 196-1
14
Appendix A: Functional changes compared to TINS edition 4
14
A.1
EN 300 403-1
14
A.2
EN 300 403-1
15
5
Document history
16
TeliaSonera Sweden
Networks & Production, Fixed Networks Development
Security
Page No.
REQUIREMENT SPECIFICATION
Public
2 (16)
Prepared
Document responsible/Approved
Göran Engström
Stefan Andersson
Date
Rev
2004-02-24
C
Linked to object
No.
LZBA 506 403/4
4
PRIMARY RATE ACCESS
4.1
SCOPE
This specification defines the user-network interface applicable to terminal equipment
to be connected to primary rate accesses of Telia’s ISDN. Reference is made to the
European Telecommunication Standards. Only deviations from the standards and
clarifications are listed in this document.
4.2
NORMATIVE REFERENCES
ETS 300 011-1 (May 00)
ETS 300 402-2 (Nov. 95)
Primary Rate User Network Interface. Layer 1
specification
Data link layer. General protocol specification
EN 300 403-1 (Nov. 99)
Signalling network layer for circuit-mode basic call
control. Protocol specification
SS 63 63 49 (Sept. 89)
Customer Premises Network, CPN Connection of CPNs
to the public telecommunication network
SS 63 63 50 (Sept. 89)
Customer Premises Network, CPN Design of physical
communications lines and sockets in CPNs
Q.850 (May 98)
Usage of Cause and Location in the Digital Subscriber
Signalling System No. 1 and the Signalling System No. 7
ISDN User Part.
EN 300 196-1 (July 00)
Integrated Services Digital Network (ISDN); Generic
functional protocol for the support of supplementary
services; Digital Subscriber Signalling System No. One
(DSS1) protocol; Part 1: Protocol specification
Security
Page No.
REQUIREMENT SPECIFICATION
Public
3 (16)
Prepared
Document responsible/Approved
Göran Engström
Stefan Andersson
Date
Rev
2004-02-24
C
No.
LZBA 506 403/4
4.3
LAYER 1 - PHYSICAL INTERFACE
Terminal equipment shall be conformant with ETS 300 011. The following options
are applicable:

Both interface presentation alternatives, the balanced interface pair type (120
ohm) and the coaxial type (75 ohm), shall be able to apply at the interface. It
is an advantage if there is a possibility to configure (e.g. strap) between the
two alternatives on the same card.

the TE may be connected by:
1) plug and jack according to ISO 10173 or
2) hard wiring;

The CRC-4 procedure specified in ETS 300 167 shall be applied including
the Cyclic Redundance Check (CRC) error reporting using bit E in the CRCmultiframe. Bit 1 in time slot 0 shall either be used for the CRC-4 procedure,
or permanently be set to binary ONE.
Note:
Two Swedish Standards concerning Customer Premises Network, CPN, are partly
applicable to the customer cable network. These standards describe the requirements
on "Connection of CPNs to the public telecommunication network" and "Design of
physical communications lines and sockets in CPNs". These standards are:
- SVENSK STANDARD SS 63 63 49
- SVENSK STANDARD SS 63 63 50
4.4
LAYER 2 - DATA LINK PROTOCOL
Terminal equipment shall be conformant with ETS 300 125.
Only point-to-point data link connection is applicable. This implies that layer 3
information shall always be sent in I-frames.
The TEI value shall be set to 0. TEI management procedures are not applicable.
For more detailed information about layer 2, see LZBA 506 403/6B; "ISDN User Network Interface; Data Link Layer Specification".
Linked to object
Security
Page No.
REQUIREMENT SPECIFICATION
Public
4 (16)
Prepared
Document responsible/Approved
Göran Engström
Stefan Andersson
Date
Rev
2004-02-24
C
No.
LZBA 506 403/4
4.5
LAYER 3 - SIGNALLING PROTOCOL
The following characteristics of Telia ISDN primary rate access should be taken into
account (e.g. optional procedures that are not supported).
4.5.1
EN 300 403-1
4.5.1.1
DISCONNECT message (EN 300 403-1, clause 3.1.5)
As a subscription option the DISCONNECT messages from the network towards user
B includes a progress information element #8 ‘Inband tones and announcements
available’ and a Congestion tone is generated during 30 seconds.
4.5.1.2
RESUME and SUSPEND messages on point-to-point
(EN 300 403-1, clause 3.1.11)
If a RESUME message is received by the network on a point-to-point configuration,
this message will be ignored.
If a SUSPEND message is received by the network on a point-to-point configuration,
the network will respond, either by sending a SUSPEND REJECT message or by
sending a STATUS message. The call will remain in the active state.
4.5.1.3
SETUP message
(EN 300 403-1, clause 3.1.14)
The information element “Date/Time” is not supported.
If only three octets is received in the following information elements, it will be treated
as information element content error.
Calling Party Number
Calling Party Subaddress
Called Party Subaddress
Low Layer compatibility
High Layer compatibility
4.5.1.4
Bearer capability information element (EN 300 403-1
clause 4.5.5)
1) The bit information transfer rate (octets 4, bits 5 to 1) for Multirate (64 kbit/s rate)
is supported. But transfer of n*64 channels is not supported.
2) Octet 3 “Information transfer capability”:
11000 Video – At the reception of this code point, the call will be rejected with
cause “Bearer capability not implemented”.
3) Octet 5 “User information”
Linked to object
Security
Page No.
REQUIREMENT SPECIFICATION
Public
5 (16)
Prepared
Document responsible/Approved
Göran Engström
Stefan Andersson
Date
Rev
2004-02-24
C
No.
LZBA 506 403/4
00010 “Rec. G.711 μ-law” is not defined.
01000 “CCITT standardized rate adaption V.120” is not defined.
4) Octet 5a “User rate”
10011 “28,8 kbit/s rec. V.110” is not defined.
10100 “24 kbit/s rec. V.110” is not defined.
5) Octet 5d “Modem type”
011110 “Rec. V34” is not defined.
6) Any value is accepted in octet 5a and 5d. Defined values are stated in
EN 300 403-1
4.5.1.5
Call state information element
(EN 300 403-1, clause 4.5.7)
Octet 3 “Call state value”
The following network states are only valid for Basic access in point-to-multipoint
configuration:
N15
N17
N22
Suspend Request
Resume Request
Call Abort
Octet 3 “Global Interface state values” are only valid for point-to-point configuration.
4.5.1.6
Called party number information element
(EN 300 403-1, clause 4.5.8)
1) Type of number (octet 3): the "abbreviated number" is not supported.
2) Numbering plan identification (octet 3): the telex and national standard
numbering plans are not supported.
3) Number digits: the # character may be used to indicate completion of number (i.e.
sending complete indication).
4) Numbering plan identification (octet 3) : ‘Unknown’ will be treated as E.164.
4.5.1.7
Sub-address information element (EN 300 403-1,
clause 4.5.9 and 4.5.11)
The contents of the Called and Calling party sub-address information elements are
transparent to the network. The network will only check that these information
elements do not exceed 23 octets in length (i.e. contents do not exceed 20 octets).
Linked to object
Security
Page No.
REQUIREMENT SPECIFICATION
Public
6 (16)
Prepared
Document responsible/Approved
Göran Engström
Stefan Andersson
Date
Rev
2004-02-24
C
No.
LZBA 506 403/4
4.5.1.8
Calling party number information element
(EN 300 403-1, clause 4.5.10)
Numbering plan: the telex numbering plan is not supported.
4.5.1.9
Date/time information element
(EN 300 403-1, clause 4.5.15)
Will be coded in 7 octets (i.e. the octet for seconds is not sent).
4.5.1.10 High Layer compatibility (EN 300 403-1, clause 4.5.17)
Octet 4 “High Layer characteristics identification”:
1100010 “Audiographic conference” is not defined
1101000 “Multimedia services” is not defined.
1) Independent of the coding standard, octets 4 and 4a (if present) are transported
transparently by the network, provided that the rest of octet 3 is correctly coded.
4.5.1.11 Low layer compatibility (EN 300 403-1, clause 4.5.19)
Octet 5a “User rate”:
10011 “28,8 kbit/s Rec. V.110” is not defined.
4.5.1.12 Network-specific facilities information element (EN 300
403-1 Clause 4.5.21)
Network-specific facility information element is not supported.
4.5.1.13 Notification indicator information element (EN 300
403-1 clause 4.5.22)
1) When the notification indicator is generated by the AXE and when received from
the local user the maximum length is 3 octets. When the Notification indicator is
received from another exchange it will be transported transparently to the local user
and its maximum length is 255 octets.
2) Octet 3 ‘Notification description’ may have the following values:
0000000 User suspended
0000001 User resumed
0000011 Discrimination for BER encoded notification ext. (Note 1)
0000100 Call completion delay (Note 2)
1000010 Conference established
1000011 Conference disconnected
1000100 Other party added
Linked to object
Security
Page No.
REQUIREMENT SPECIFICATION
Public
7 (16)
Prepared
Document responsible/Approved
Göran Engström
Stefan Andersson
Date
Rev
2004-02-24
C
No.
LZBA 506 403/4
1000101 Isolated
1000110 Reattached
1000111 Other Party isolated
1001000 Other party reattached
1001001 Other party split
1001010 Other party disconnected
1001011 Conference floating (Note 2)
1100000 Call is a waiting call
1101000 Diversion is activated
1101001 Call transferred, alerting
1101010 Call transferred, active
1101011 Call is queued (Note 2)
1111001 Remote hold
1111010 Remote retrieval
1111011 Call is diverting
Note 1: It will be treated as information element content error if received from the
user. It will never be generated by the AXE, but will be transported transparently if
received from another exchange.
Note 2: This value will never be generated by the AXE, but will be transported
transparently if received from another exchange or from the user.
4.5.1.14 Transit network selection (EN 300 403-1 Annex C)
Transit network selection information element
(EN 300 403-1, clause 4.5.29)
The network does not support transit network selection procedures. The Transit
network selection information element is not supported.
4.5.1.15 Non mandatory information element contents error
When a message is received which has one or more non-mandatory information
elements with invalid contents no further action besides will be taken, acting on
information elements having valid contents.
4.5.1.16 B-channel selection – Originating (EN 300 403-1
clause 5.1.2)
If for a circuit-switched call the Channel identification information element in the
SETUP message indicates "No B-channel" then the call will be rejected using a
RELEASE COMPLETE message with cause #79 "Service or option not
implemented". If the Channel identification information element in the SETUP
message indicates "The channel identified is the D-channel", then the call will be
rejected using a RELEASE COMPLETE message with cause #6 "Channel
unacceptable".
Linked to object
Security
Page No.
REQUIREMENT SPECIFICATION
Public
8 (16)
Prepared
Document responsible/Approved
Göran Engström
Stefan Andersson
Date
Rev
2004-02-24
C
No.
LZBA 506 403/4
4.5.1.17 Overlap sending (EN 300 403-1, clause 5.1.3)
The Sending complete information element, if received, is interpreted as the sending
of the complete called party number, but never as an indication of the complete
Keypad information element.
Note. For Keypad signalling “#” is used to indicate end of message.
4.5.1.18 Call Establishment at the Destination Interface
(EN 300 403-1, clause 5.2)
Data link connections may be established by the TA, TE or NT2 as soon as a TEI is
assigned (either locally or by automatic assignment procedure), and will be retained
indefinitely in case of point-to-point data links.
In case of point-to-multipoint configuration, the data link will be released 10 seconds
after all layer 3 connections for that data link have been cleared.
4.5.1.19 Incoming call and Overlap receiving (EN 300 403-1
clause 5.2.1 and 5.2.4)
Overlap receiving procedures can be applied by the network on a point-to-point
configuration (depending on whether the number length is known or not), whereas enbloc receiving procedures will always be applied on point-to-multipoint
configurations.
Reception of a SETUP ACKNOWLEDGE on a point-to-multipoint configuration will
imply sending of a STATUS message with cause #97 "message type non-existent or
not implemented" by the network. Reception of a SETUP ACKNOWLEDGE on a
point-to-point configuration after a sending complete has been sent imply sending of a
STATUS message with cause #111 "Protocol error, unspecified" by the network.
4.5.1.20 SETUP message delivered by broadcast data link
(EN 300 403-1, clause 5.2.3.2)
If a faulty coding of the Channel identification information element is present in the
first response message from a user, then the call will be cleared.
Note. The user should send Channel identification information element only in the
first message towards the network. A second message including a Channel
identification will cause a STATUS message from the network.
Linked to object
Security
Page No.
REQUIREMENT SPECIFICATION
Public
9 (16)
Prepared
Document responsible/Approved
Göran Engström
Stefan Andersson
Date
Rev
2004-02-24
C
No.
LZBA 506 403/4
4.5.1.21 In-Band Tones and Announcements (EN 300 403-1,
clause 5.4)
For some applications, it is desirable to allow the completion of the transmission path
(from the called user to the calling user) associated with a bearer service prior to
receiving call acceptance.
In particular, the completion of the backward direction of transmission path prior to
receipt of a CONNECT message from the called user may be desirable to allow the
called user to provide internally-generated tones and announcements that are sent inband to the calling user prior to answer by the called user.
To apply this procedure is a subscription option.
On receipt of a message containing an indication that in-band information is being
provided, the network connects the backward side of the transmission path upon
receiving an ALERTING message or a PROGRESS message containing progress
indicator #8 "in-band information or appropriate pattern is now available", or progress
indicator #1 "call is not end-to-end ISDN: further call progress information may be
available in-band", respectively.
4.5.1.22 Restart procedure (EN 300 403-1, clause 5.5)
This clause is a clarification of 5.5 in EN 300 403-1. The following Restart
procedures will be followed:
a) If a RESTART message is received in any other global call state than the Restart
Null state, the RESTART message will be handled according to the procedures
defined in clauses 5.8.3.2 and 5.8.4.
b) If a RESTART ACKNOWLEDGE is received by the network in the Restart state,
the RESTART ACKNOWLEDGE message will be handled according to the
procedures defined in the clauses 5.8.3.2 and 5.8.4. A RESTART ACKNOWLEDGE
message received in the Restart Null state will be ignored.
c) If an entity not supporting the Restart procedures receives a message using the
global call reference, the handling is defined in clause 5.8.3.2.
d) If a RESTART ACKNOWLEDGE message is received by the network in response
to a RESTART message indicating that only a subset of the specified B-channels is
restarted, the B-channel(s) which have not been returned to the idle condition will be
placed in maintenance condition, i.e. out-of-service (see also case e).
e) B-channel(s) or interface may be returned to idle condition from the maintenance
condition, and therefore available for reuse, by means of a Protocol Restart procedure
initiated by the user.
In case that a Protocol Restart is initiated by the user, actions as described in clause
5.5.2 will be followed by the network.
Linked to object
Security
Page No.
REQUIREMENT SPECIFICATION
Public
10 (16)
Prepared
Document responsible/Approved
Göran Engström
Stefan Andersson
Date
Rev
2004-02-24
C
No.
LZBA 506 403/4
f) If a RESTART ACKNOWLEDGE message is received by the network in response
to a RESTART message indicating one or more B-channel(s) that were not specified
in the RESTART message, then the network will initiate a Protocol Restart procedure
for those B-channels.
g) If a RESTART ACKNOWLEDGE message is received by the network with the
Restart indicator information element coded as "all interfaces" or "single interface",
whereas one or more specific B-channels were included in the RESTART sent by
network, then a new Protocol Restart procedure will be initiated by the network on
that interface.
h) If a RESTART ACKNOWLEDGE message is received by the network in response
to a RESTART message and restarted B-channel(s) are explicitly specified (by including a Channel identification information element), and the D-channel indicator field
is coded as "The channel identified is the D-channel" or, if the Channel identification
information element is repeated and the first of them has the D-channel indicator
field coded as "The channel identified is the D-channel", no action will be taken on
these B-channels but a STATUS message will be returned with cause #82 "identified
channel does not exist" indicating in the diagnostic field the channel(s) that could not
be handled.
i) If a RESTART message is received by the network containing B-channel(s) not
allocated to the access, those B-channels will be acknowledged by the network as
restarted. This applies also to the case when the RESTART message received by the
network specifies "single interface" or "all interfaces", and not all B-channels have
been allocated to the access. In this case, after all the allocated B-channels have been
returned to the idle condition, the network will respond with a RESTART
ACKNOWLEDGE message specifying "single interface".
4.5.1.23 Timer values
T301
T302
T303
T304
T305
T306
T307
T308
T309
T310
T312
T314
T316
T317
T322
3 min
10 s
4s
20 s
30 s
30 s
180 s
4s
90 s
30 s
T303+2 s
4s
2 min
60 s
4s
(EN 300 403-1, clause 9.1)
Linked to object
Security
Page No.
REQUIREMENT SPECIFICATION
Public
11 (16)
Prepared
Document responsible/Approved
Göran Engström
Stefan Andersson
Date
Rev
2004-02-24
C
No.
LZBA 506 403/4
4.5.1.24 Segmentation procedures (EN 300 403-1, Annex H)
1) Segmentation procedures may be used on the basis of bilateral agreement between
the network and the user.
The network will always accept segmented information if received from the user.
Furthermore, when sending the FACILITY message towards user exceeding the
maximum layer 2 frame length will always be segmented by the network.
4.5.1.25 Procedures for establishment of bearer connection
prior to call acceptance (EN 300 403-1, Annex K)
1) This option is supported by the network as a subscription option.
The transmission path in the backward direction is completed on receipt of a SETUP
ACNOWLEDGE, CALL PROCEEDING or an ALERTING message including a
Progress indicator information element with Progress indicator set to 8.
Linked to object
Security
Page No.
REQUIREMENT SPECIFICATION
Public
12 (16)
Prepared
Document responsible/Approved
Göran Engström
Stefan Andersson
Date
Rev
2004-02-24
C
No.
LZBA 506 403/4
4.5.2
Q.850
Differences compared to Q.850 Usage of Cause and Location in the Digital
Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN User Part:
1) Diagnostic information is not generated for cause #1, #2, #3, #16, #21, #29, #50,
#58, #69, #88.
2) Diagnostic information is only generated to the local user for cause#57, #65, #102.
3) The following wording is recommended to be used together with the cause value, if
an ETSI/ITU cause is presented to the user, and if this is to be presented in Swedish:
Cause #1
Cause #2
Cause #3
‘Vakant nummer’
(Reserved)
‘Spärr, förbindelse till destinationen finns ej’
Cause #4
Cause #5
Cause #6
Cause #7
(ISUP)
(ISUP) ‘Felslaget trunk prefix’
‘Ogiltig kanal’
’Samtalet kopplas i befintlig kanal’
Cause #8
Cause #9
‘Samtalet har avbrutits’
(ISUP) ‘Samtalet avbrutet, kanalen reserverad’
Cause #10-15
Cause #16
Cause #17
Cause #18
(Reserved)
‘Normal nedkoppling’
‘Upptaget’
‘Mottagarens terminal är ej ansluten eller svarar ej’
Cause #19
Cause #20
Cause #21
Cause #22
Cause #23
Cause #24
Cause #25
Cause #26
Cause #27
Cause #28
Cause #29
Cause #30
Cause #31
Cause #32-33
Cause #34
Cause #35-37
Cause #38
Cause #39
Cause #40
Cause #41
‘Inget svar från användaren’
‘Abonnenten kan ej nås’
‘Avvisat koppel’
‘Abonnenten har nummerändrat’
(ISUP)
(Reserved)
(ISUP)
’Samtalet ej tilldelat’
‘Abonnentens terminal är ur funktion’
‘Felaktigt nummerformat eller ofullständigt B-nummer’
‘Tilläggstjänsten finns ej eller är ej abonnerad’
‘Svar på statusförfrågan’
‘Normal, ospecificerad’
(Reserved)
‘Spärr, ingen kanal tillgänglig’
(Reserved)
‘Tekniskt fel i nätet’
’Permanent förbindelse ur funktion’
’Permanent förbindelse fungerar’
‘Tillfälligt fel’
Linked to object
Security
Page No.
REQUIREMENT SPECIFICATION
Public
13 (16)
Prepared
Document responsible/Approved
Göran Engström
Stefan Andersson
Date
Rev
2004-02-24
C
No.
LZBA 506 403/4
Cause #42
Cause #43
Cause #44
Cause #45
Cause #46
Cause #47
Cause #48
Cause #49
Cause #50
Cause #51-52
Cause #53
Cause #54
Cause #55
Cause #56
Cause #57
Cause #58
Cause #59-61
Cause #62
Cause #63
Cause #64
Cause #65
Cause #66
Cause #67-68
Cause #69
Cause #70
Cause #71-78
Cause #79
Cause #80
Cause #81
Cause #82
Cause #83
Cause #84
Cause #85
Cause #86
Cause #87
Cause #88
Cause #89
Cause #90
Cause #91
Cause #92-94
Cause #95
Cause #96
Cause #97
Cause #98
Cause #99
Cause #100
Cause #101
Cause #102
Cause #103
‘Spärr, nätet överbelastat’
‘Del av informationen ej överförd’
‘Önskad kanal ej tillgänglig’
(Reserved)
‘Prioriterat samtal blockerat’
‘Resurs ej tillgänglig’
(Reserved)
’Begärd kvalité ej tillgänglig’
‘Tjänsten är ej abonnerad’
(Reserved)
(ISUP) ‘Spärr för utgående samtal inom CUG’
(Reserved)
(ISUP) ‘Spärr för inkommande samtal inom CUG’
(Reserved)
‘Bärartjänsten ej tillåten eller ej abonnerad’
‘Bärartjänst tillfälligt oåtkomlig’
(Reserved)
‘Inkonsekvent information’
‘Tjänsten ej tillgänglig, ospecificerat’
(Reserved)
‘Bärartjänsten ej implementerad’
‘Kanaltypen ej implementerad’
(Reserved)
‘Terminalen på destinationen stödjer ej tjänsten’
‘Terminalen på destinationen stödjer endast 56 Kbit/s’
(Reserved)
‘Tjänsten finns ej’
(Reserved)
‘Felaktig samtalsreferens’
‘Önskad kanal existerar ej’
‘Felaktig identitet angiven för parkerat samtal’
‘Samtalsidentiteten upptagen’
‘Det finns inget parkerat samtal’
‘Samtal med denna identitet borttaget’
‘Användaren är inte medlem i CUG’
‘Abonnentens terminal är ej kompatibel’
(Reserved)
(ISUP) ‘CUG finns ej’
‘Felaktigt val av transitnät’
(Reserved)
‘Felaktigt meddelande, ospecificerat’
‘Protokollfel, obligatoriskt informationselement saknas’
‘Protokollfel, meddelandetyp existerar ej’
‘Protokollfel, meddelande i fel samtalsläge eller meddelandetyp
existerar ej’
‘Protokollfel, informationselement existerar ej’
‘Protokollfel, data i informationselement felaktigt’
‘Protokollfel, meddelande i fel samtalsläge’
‘Protokollfel, tidsutlösning’
(ISUP) ‘Parametern existerar ej’
Linked to object
Security
Page No.
REQUIREMENT SPECIFICATION
Public
14 (16)
Prepared
Document responsible/Approved
Göran Engström
Stefan Andersson
Date
Rev
2004-02-24
C
No.
LZBA 506 403/4
Cause #104-109
Cause #110
Cause #111
Cause #112-126
Cause #127
4.5.3
(Reserved)
(ISUP) ‘Meddelande med fel parameter’
‘Protokollfel, ospecificerat’
(Reserved)
‘Samtrafik med annat nät, ospecificerat’
EN 300 196-1
No differences identified.
APPENDIX A: FUNCTIONAL CHANGES COMPARED TO
TINS EDITION 4
A.1
EN 300 403-1
The references in 4.2 have been updated according to the latest ETSI references.
Below are the technical changes between TINS edition 4 and edition 4.4 listed.
1. In clause 4.5.1.1 (new 4.5.1.4) has clarifications been made in first, third and
fourth paragraph and second paragraph has been removed.
2. The clarification is changed regarding disconnect in clause 4.5.1.11(new 4.5.1.1).
3. Clause 4.5.1.22 and 4.5.1.26 has been removed as no deviation exist anymore is
new text inserted to clarify Telia ISDN compared to ETSI.
4. Clause 4.5.2 has been changed regarding cause values.
Linked to object
Security
Page No.
REQUIREMENT SPECIFICATION
Public
15 (16)
Prepared
Document responsible/Approved
Göran Engström
Stefan Andersson
Date
Rev
2004-02-24
C
Linked to object
No.
LZBA 506 403/4
A.2
EN 300 403-1
Editorial corrections according to EN 300 403-1, between TINS edition 4 and edition 4.4.
Old clause
4.5.1.1
4.5.1.2
4.5.1.3
4.5.1.4
4.5.1.5
4.5.1.6
4.5.1.7
New clause
4.5.1.4
4.5.1.6
4.5.1.8
4.5.1.7
4.5.1.10
4.5.1.13
4.5.1.14
4.5.1.8
4.5.1.12
4.5.1.9
4.5.1.10
4.5.1.11
4.5.1.12
4.5.1.13
4.5.1.14
4.5.1.15
4.5.1.24
4.5.1.25
4.5.1.1
4.5.1.16
4.5.1.17
4.5.1.18
4.5.1.19
4.5.1.16
4.5.1.17
4.5.1.18
4.5.1.19
4.5.1.20
4.5.1.21
4.5.1.22
4.5.1.15
4.5.1.20
4.5.1.21
4.5.1.22
4.5.1.23
4.5.1.24
4.5.1.25
4.5.1.26
4.5.1.27
4.5.1.28
4.5.1.29
4.5.1.2
4.5.1.3
Removed
4.5.1.4
4.5.1.5
4.5.1.9
Removed
4.5.1.10
4.5.1.11
4.5.1.23
Heading
EN 300 403-1 Clause 4.5.5
EN 300 403-1 Clause 4.5.8
EN 300 403-1 Clause 4.5.10
EN 300 403-1 Clause 4.5.11
EN 300 403-1 Clause 4.5.17
EN 300 403-1 Clause 4.5.22
EN 300 403-1 Annex C
EN 300 403-1 Clause 4.5.29
EN 300 403-1 Annex E
EN 300 403-1 Clause 4.5.21
EN 300 403-1 Annex H
EN 300 403-1 Annex K
EN 300 403-1 Clause 3.1.5
EN 300 403-1 Clause 5.1.2
EN 300 403-1 Clause 5.1.3
EN 300 403-1 Clause 5.2
EN 300 403-1 Clause 5.2.1
EN 300 403-1 Clause 5.2.4
EN 300 403-1 Clause 5.2.3.2
EN 300 403-1 Clause 5.4
EN 300 403-1 Clause 5.5
Non mandatory information element
contents error
EN 300 403-1 Clause 3.1.11
EN 300 403-1 Clause 3.1.14
EN 300 403-1 Clause 4.3
EN 300 403-1 Clause 4.5.5
EN 300 403-1 Clause 4.5.7
EN 300 403-1 Clause 4.5.15
EN 300 403-1 Clause 4.5.16
EN 300 403-1 Clause 4.5.17
EN 300 403-1 Clause 4.5.19
Timer values EN 300 403-1 Clause 9.1
Security
Page No.
REQUIREMENT SPECIFICATION
Public
16 (16)
Prepared
Document responsible/Approved
Göran Engström
Stefan Andersson
Date
Rev
2004-02-24
C
Linked to object
No.
LZBA 506 403/4
5
DOCUMENT HISTORY
Revision
Date
Amendments
A
1998-12-15
New version
B
2000-04-26
C
2004-02-24
In clause 4.4 a reference has been added to the new chapter 6 B
(LZBA 506 403/6B). In addition, some editorial changes have been
made.
References in clause 4.2 has been updated. Clause 4.5 and Appendix
A has been updated.
Editorial change in clause 4.5.
New company name was inserted.
New document template was used.