MCMC MTSFB TC T007:2014

TECHNICAL CODE

SPECIFICATION FOR SHORT RANGE DEVICES (SRD)

First Revision

Developed by Registered by

Registered date: 18 December 2014

© Copyright 2014 MCMC MTSFB TC T007:2014

DEVELOPMENT OF TECHNICAL CODES

The Communications and Multimedia Act 1998 (‘the Act’) provides for Technical Standards Forum designated under section 184 of the Act or the Malaysian Communications and Multimedia Commission (‘the Commission’) to prepare a technical code. The technical code prepared pursuant to section 185 of the Act shall consist of, at least, the requirement for network interoperability and the promotion of safety of network facilities.

Section 96 of the Act also provides for the Commission to determine a technical code in accordance with section 55 of the Act if the technical code is not developed under an applicable provision of the Act and it is unlikely to be developed by the Technical Standards Forum within a reasonable time.

In exercise of the power conferred by section 184 of the Act, the Commission has designated the Malaysian Technical Standards Forum Bhd (‘MTSFB’) as a Technical Standards Forum which is obligated, among others, to prepare the technical code under section 185 of the Act.

A technical code prepared in accordance with section 185 shall not be effective until it is registered by the Commission pursuant to section 95 of the Act.

For further information on the technical code, please contact:

Malaysian Communications and Multimedia Commission (MCMC) Off Persiaran Multimedia 63000 Darul Ehsan

Tel: +60 3 8688 8000 Fax: +60 3 8688 1000 http://www.skmm.gov.my

OR

Malaysian Technical Standards Forum Bhd (MTSFB) 4805-2-2, Block 4805, Persiaran Flora CBD Perdana 2 Cyber 12 63000, Cyberjaya Selangor Darul Ehsan MALAYSIA

Tel: +60 3 8322 1441/1551 Fax: +60 3 8322 0115 http://www.mtsfb.org.my

i MCMC MTSFB TC T007:2014

CONTENTS

Page

Committee Representation ...... iii

Foreword ...... iv

1. Scope ...... 1

2. Normative references ...... 1

3. Abbreviation...... 1

4. Requirements ...... 2

4.1 General requirements ...... 2

4.2 Technical requirements ...... 3

Annex A Normative references ...... 8

Table 1 Technical requirements for Short Range Devices (SRD) ...... 4

ii MCMC MTSFB TC T007:2014

Committee Representation

Wireless Terminal Working Group under the Malaysian Technical Standards Forum Bhd (MTSFB) which developed this Technical Code consists of representatives from the following organisations:

Maxis Communications Berhad MIMOS Berhad Nokia (M) Sdn Bhd SIRIM QAS International Sdn Bhd Berhad

iii MCMC MTSFB TC T007:2014

FOREWORD

This technical code for the Specification for Short Range Devices (SRD) (‘this Technical Code’) was developed pursuant to section 185 of the Act 588 by the Malaysian Technical Standards Forum Berhad (MTSFB) via its Wireless Terminal Working Group.

This Technical Code was developed for the purpose of certifying communications equipment under the Communications and Multimedia (Technical Standards) Regulations 2000.

This Technical Code is the first revision of SKMM WTS SRD Rev. 1.01:2007, Technical Specification for Short Range Device.

This Technical Code cancels and replaces SKMM WTS SRD Rev. 1.01:2007.

This Technical Code shall continue to be valid and effective until reviewed or cancelled.

iv MCMC MTSFB TC T007:2014

SPECIFICATION FOR SHORT RANGE DEVICES (SRD)

1. Scope

This Technical Code defines the technical requirements for SRD transmitters and receivers operating in the frequencies as defined in the relevant Standard Radio System Plans (SRSPs) and the Class Assignments issued by MCMC.

SRD may be fixed, mobile or portable stations that come with a radio frequency output connector and dedicated antenna or an integral antenna. Its applications include (but not limited to) short range communication (SRC), remote control, security, wireless microphone, wireless local area network (WLAN), industrial, scientific and medical (ISM), radio frequency identification (RFID) and wireless CCTV. The devices may employ different types of modulation and power requirement which may include data, video and voice application.

2. Normative references

The normative references in Annex A are indispensable for the application of this Technical Code. For dated references, only the edition cited applies. For undated references, the latest edition of the normative references (including any amendments) applies.

The devices shall be tested for compliance with the applicable technical requirements stipulated in Clause 4 and Table 1 of this Technical Code. The test methods and conditions mentioned in Table 1 shall be applicable to the device under test.

3. Abbreviation

For the purposes of this Technical Code, the following abbreviation applies.

AC Alternating Current CCTV Closed-circuit Television DC Direct Current EIRP Effective Isotropic Radiated Power ERP Effective Radiated Power ETSI European Telecommunications Standards Institute FCC Federal Communications Commission IEC International Electrotechnical Commission ISM Industrial, Scientific and Medical RFID Radio Frequency Identification Device RLAN Radio Local Area Network SRSP Standard Radio System Plan SRD Short Range Devices

1 MCMC MTSFB TC T007:2014

SRC Short Range Communication WLAN Wireless Local Area Network

4. Requirements

4.1 General requirements

SRD shall be designed to meet the following basic requirements: a) The device shall not cause interference with other authorised radio-communication services, and be able to tolerate any interference caused by other radio-communication services, electrical or electronic equipment. b) The device shall not be constructed with any external or readily accessible control which permits the adjustments of its operation in a manner that is inconsistent with this Technical Code.

4.1.1 Power supply requirements

The equipment may be AC or DC powered. For AC powered equipment, the operating voltage shall be 240 V +5 %, -10 % and frequency 50 Hz ± 1 % in according to MS 406 or 230 V ± 10 % and frequency 50 Hz ± 1 % in according to MS IEC 60038 whichever is current.

Where external power supply is used, e.g. AC adaptor, it shall not affect the capability of the equipment to meet this Technical Code. Adaptor must be pre-approved by the relevant regulatory body before it can be used with the equipment.

4.1.2 Power supply cord and mains plug requirements

The equipment shall be fitted with a suitable and appropriate approved power supply cord and mains plug. Both are regulated products and must be pre-approved by the relevant regulatory body before it can be used with the equipment.

The power supply cord shall be certified in according to: a) MS 140; or b) BS 6500; or c) IEC 60227-5; or d) IEC 60245-4.

The main plug shall be certified in according to: a) 13 A fused plugs: MS 589: Part 1 or BS 1363: Part 1; or b) 2.5 A, 250 V, flat non-rewirable two-pole plugs: MS 1578 or BS EN 50075.

2 MCMC MTSFB TC T007:2014

4.1.3 Marking requirements

The equipment shall be marked with the following information: a) supplier/manufacturer’s name or identification mark; b) supplier/manufacturer’s model or type reference; and c) other markings as required by the relevant standards.

The markings shall be legible, indelible and readily visible. All information on the marking shall be either in “Bahasa Melayu” or English Language.

4.2 Technical requirements

The SRD shall be designed to operate within the specified frequency bands and comply with the maximum Field Strength/RF Output Power and Transmitter & Receiver Spurious Emissions given in Table 1. It shall fulfill the relevant requirements of this Technical Code on all the permitted frequencies which it is intended to operate

3 MCMC MTSFB TC T007:2014

Table 1: Technical requirements for Short Range Devices (SRD)

Authorized Frequency Bands / Max. Field Strength / Transmitter & Test SRD Applications Remarks Frequencies RF Output Power Receiver Reference Spurious Emissions 1. 3 kHz - 195 kHz 50 mW (EIRP) Security device 2. 3155 kHz - 3400 kHz 13.5 dBμA/m at 10 m SRC device MS 300 330-1 MS 300 330-1 100 mW (EIRP) SRC device 3. 6765 kHz - 6795 kHz 500 mW (EIRP) ISM device 4. 9 kHz - 315 kHz 30 dBμA/m at 10 m EN 302 195 EN 302 195 Active medical implant device 5. 10200 kHz - 11000 kHz 10 mW (EIRP) SRC device MS 300 330-1 MS 300 330-1 100 mW (EIRP) SRC device & RFID 6. 13553 kHz - 13567 kHz 500 mW (EIRP) ISM device 100 mW (EIRP) SRC device 7. 26.957 MHz - 27.283 MHz 500 mW (EIRP) MS 300 220-1 MS 300 220-1 ISM device 8. 26.95728 MHz - 27.28272 MHz 50 mW (ERP) Wireless microphone device 9. 26.965 MHz - 27.275 MHz MS 300 220-1 MS 300 220-1 Remote controlled device 10. 40 MHz 50 mW (ERP)

11. 40.435 MHz - 40.925 MHz Wireless microphone device 500 mW (ERP) MS 300 220-1/ MS 300 220-1/ ISM device 12. 40.66 MHz - 40.7 MHz 1 W (ERP) FCC Part 15 FCC Part 15 SRC device

4 MCMC MTSFB TC T007:2014

Table 1: Technical requirements for Short Range Devices (SRD) (continued)

Transmitter & Authorized Frequency Bands / Max. Field Strength / Receiver Test SRD Applications Remarks Frequencies RF Output Power Spurious Reference Emissions 13. 47 MHz 50 mW (EIRP) Remote controlled device 14. 49 MHz MS 300 220-1/ MS 300 220-1/ 50 nW (ERP) EN 301 357 EN 301 357 SRC device 15. 87.5 MHz - 108 MHz 50 mW (EIRP) Wireless microphone device 16. 182.025 MHz - 182.975 MHz MS 300 220-1/ MS 300 220-1/ 17. 183.025 MHz - 183.475 MHz FCC Part 15 FCC Part 15 50 mW (EIRP) Wireless microphone device 18. 217.025 MHz - 217.975 MHz MS 300 220-1 MS 300 220-1 19. 218.025 MHz - 218.475 MHz 20. 228.0063 MHz - 228.9937 MHz Security device Security device 21. 303 MHz - 320 MHz 50 mW (EIRP) MS 300 220-1 MS 300 220-1 Remote controlled device 22. 400 MHz - 402 MHz Security device 23. 402 MHz - 405 MHz 25 μW (EIRP) EN 301 839-1 EN 301 839-1 Active medical implant device MS 300 220-1 MS 300 220-1 Security device and remote 50 mW (ERP) controlled device 24. 433 MHz - 435 MHz 100 mW (ERP) MS 300 220-1 MS 300 220-1 SRC device 100 mW (EIRP) RFID MS 300 220-1 MS 300 220-1 Wireless microphone device 25. 510 MHz - 798 MHz 50 mW (ERP)

5 MCMC MTSFB TC T007:2014

Table 1: Technical requirements for Short Range Devices (SRD) (continued)

Authorized Frequency Max. Field Strength / Transmitter & Receiver Test Reference SRD Applications Remarks Bands / Frequencies RF Output Power Spurious Emissions 26. 868.1 MHz 50 mW (ERP) Security device SRC device 27. 869 MHz - 870 MHz 500 mW (ERP) Security device RFID MS 300 220-1 MS 300 220-1 RFID interrogator below 2W (ERP) is subject to Class Assignment (CA) 2 W (ERP) / 28. 919 MHz - 923 MHz RFID and up to 4W (ERP) is 4 W (ERP) subject to an Apparatus Assignment (AA) as per MCMC SRSP-530 RFID. 29. 1880 MHz - 1900 MHz 250 mW (EIRP) EN 300 176 EN 300 176 SRC device SRC device, RFID, CCTV MS 300 440-1 access device and MS 300 440-1 wireless microphone 30. 2400 MHz - 2500 MHz 500 mW (EIRP) device MS 300 328/ MS 300 328/ FCC Part 15 FCC Part 15 ISM and SRC device §15.209 §15.247 31. 4940 MHz - 4990 MHz 1 W (EIRP) MS 300 440-1 MS 300 440-1 CCTV access device For government use only SRC device and CCTV 1 W (EIRP) MS 300 440-1 MS 300 440-1 access device MS 301 893/ MS 301 893/ SRC device operating 32. 5150 MHz - 5350 MHz under this provision shall FCC Part 15 FCC Part 15 1 W (EIRP) SRC device (RLAN) implement DFS function §15.407 (b) §15.407 in the frequency range 5.250 GHz – 5.350 GHz.

6 MCMC MTSFB TC T007:2014

Table 1: Technical requirements for Short Range Devices (SRD) (continued)

Authorized Frequency Bands / Max. Field Strength / Transmitter & Receiver Test SRD Applications Remarks Frequencies RF Output Power Spurious Emissions Reference SRC device operating 1 W (EIRP) MS 300 440-1 MS 300 440-1 SRC device under this provision shall implement Dynamic 33. 5470 MHz - 5650 MHz MS 301 893 Frequency Selection 1 W (EIRP) MS 301 893 SRC device (RLAN) (DFS) & Transmit Power Control (TPC) 34. 5650 MHz - 5725 MHz 1 W (EIRP) EN 300 440-1 EN 300 440-1 CCTV access device 500 mW (EIRP) MS 300 440-1/ ISM device MS 300 440-1/ FCC Part 15 § 35. 5725 MHz - 5875 MHz SRC device and CCTV 1 W (EIRP) FCC Part 15 §15.209 15.247 or access device 15.407 500 mW (EIRP) MS 300 440-1/ ISM device MS 300 440-1/ 36. 24 GHz - 24.25 GHz FCC Part 15 §15.209; 1 W (EIRP) FCC Part 15 SRC device §15.249 (d) 37. 57 GHz - 64 GHz 10 W (EIRP) EN 302 567 EN 302 567 SRC device 61 GHz - 61.5 GHz 500 mW (EIRP) EN 305 550-1/ EN 305 550-1/ 38. ISM device FCC Part 15 FCC Part 15 50 mW (ERP) EN 305 550-1 EN 305 550-1 Security device 39. 76 GHz - 77 GHz EN 301 091-1/ EN 301 091-1/ Short range radio 5 W (EIRP) FCC Part 15 §15.253 FCC Part 15 determination 500 mW (EIRP) ISM device 40. 122 GHz - 123 GHz 1 W (EIRP) SRC device EN 305 550-1 EN 305 550-1 500 W (EIRP) ISM device 41. 244 GHz - 246 GHz 1 W (EIRP) SRC device

Note: The Malaysian Standards cited in this table are adopted from ETSI standards which can be publicly accessed through the ETSI website located at http://www.etsi.org

7 MCMC MTSFB TC T007:2014

Annex A

Normative references

BS 1363: Part 1 13 A plugs, socket-outlets, adaptors and connection units – Part 1: Specification for rewirable and non-rewirable 13 A fused plugs

BS 6500 Electric cables. Flexible cords rated up to 300/500 V, for use with appliances and equipment intended for domestic, office and similar environments

BS EN 50075 Specification for flat non-wirable two-pole plugs 2.5 A 250 V, with cord, for the connection of Class II-equipment for household and similar purposes

ETSI EN 300 176 Digital Enhanced Cordless Telecommunications (DECT); Approval test specification;

ETSI EN 301 091 Electromagnetic compatibility and Radio spectrum Matters (ERM); Road Transport and Traffic Telematics (RTTT); Technical characteristics and test methods for radar equipment operating in the 76 GHz to 77 GHz band

ETSI EN 301 357 Electromagnetic compatibility and Radio spectrum Matters (ERM); Technical characteristics and test methods for analogue cordless wideband audio devices using integral antennas operating in the CEPT recommended 863 MHz to 865 MHz frequency range

ETSI EN 301 839-1 Electromagnetic compatibility and Radio spectrum Matters (ERM); Short Range Devices (SRD); Ultra Low Power Active Medical Implants (ULP-AMI) and Peripherals (ULP-AMI-P) operating in the frequency range 402 MHz to 405 MHz; Part 1: Technical characteristics and test methods

ETSI EN 302 195 Electromagnetic compatibility and Radio spectrum Matters (ERM); Radio equipment in the frequency range 9 kHz to 315 kHz for Ultra Low Power Active Medical Implants (ULP-AMI) and accessories; Part 1: Technical characteristics and test methods

ETSI EN 302 567 Broadband Radio Access Networks (BRAN); 60 GHz Multiple-Gigabit WAS/RLAN Systems; Harmonized EN covering the essential requirements of article 3.2 of the R&TTE Directive

ETSI EN 305 550-1 Electromagnetic compatibility and Radio spectrum Matters (ERM); Short Range Devices (SRD); Radio equipment to be used in the 40 GHz to 246 GHz frequency range; Part 1 : Technical characteristics and test methods

FCC Part 15 Federal Communications Commission Part 15 – Radio Frequency Devices

8 MCMC MTSFB TC T007:2014

IEC 60245-4 Rubber insulated cables – Rated voltages up to and including 450/750 V – Part 4: Cords and flexible cables

IEC 60227-5 Polyvinyl chloride insulated cables of rated voltages up to and including 450/750 V – Part 5: Flexible cables (cords)

MS 300 220-1 Electromagnetic compatibility and Radio spectrum Matters (ERM); Short Range Devices (SRD); Radio Equipment to be used in the 25 MHz to 1000 MHz frequency range with the power levels ranging up to 500 mW – Part 1: Technical characteristics and test method

MS 300 330-1 Electromagnetic compatibility and Radio spectrum Matters (ERM); Short Range Devices (SRD); Radio equipment in the frequency rang 9 kHz to 25 MHz and inductive loop systems in the frequency range 9 kHz to 30 MHz – Part 1: Technical characteristics and test methods

MS 300 328 Electromagnetic compatibility and Radio spectrum Matters (ERM); wideband transmission systems; Data transmission equipment operating in the 2.4 GHz ISM band and using spread spectrum modulation techniques; Harmonised EN covering essential requirements under article 3.2 of the R&TTE Directives

MS 300 440-1 Electromagnetic compatibility and Radio spectrum Matters (ERM); Short Range Devices (SRD); Radio equipment to be used in the 1 GHz to 40 GHz frequency range – Part 1: Technical characteristics and test methods

MS 301 893 Broadband Radio Access Networks (BRAN); 5 GHz high performance RLAN; Harmonized EN covering the essential requirements of article 3.2 of the R&TTE Directive

MS 140 Specification for insulated flexible cords and cables

MS 589: Part 1 Specification for 13 A plugs, socket outlets, adaptors and connection units – Part 1: Specification for rewirable and non-rewirable 13 A fused plugs

MS 1578 Specification for flat non-rewirable two-pole plugs, 2.5 A, 250 V, with cord, for the connection of class II-Equipment for household and similar purposes

MCMC SRSP - 534 Requirements for wireless local area networks (WLAN) systems WLAN operating in the frequency band 5150 MHz to 5350 MHz

MCMC SRSP - 530 Requirement for Radio Frequency Identification Device operating in the RFID frequency band from 919 MHz to 923 MHz

MS IEC 60038 IEC Standard voltages

MS IEC 60950-1 Information Technology equipment – Safety

MS IEC CISPR 22 Information Technology Equipment – Radio disturbance characteristics – Limits and methods of measurement

9 MCMC MTSFB TC T007:2014

Annex B (Informative)

Amendments

Amendments to SKMM WTS SRD Rev. 1.01:2007 Page Clause Items Amended Cover - The document has been renumbered as “MCMC MTSFB TC T007:2014”.

The document has adopted new cover page.

i - Explanatory note on the development of Technical Codes has been included.

4 4.2 The following frequencies have been included: (Table 1) (a) 3155 kHz – 3400 kHz (SRC device) (b) 9 kHz – 315 kHz (active medical implant device) (c) 10 200 kHz – 11 000 kHz (SRC device) (d) 40.435 MHz – 40.925 MHz (wireless microphone device) (e) 402 MHz – 405 MHz (active medical implant device) (f) 1880 MHz – 1900 MHz (SRC device) (g) 4940 MHz – 4990 MHz (CCTV access device for government use) (h) 5470 MHz – 5650 MHz (SRC device) (i) 5650 MHz – 5725 MHz (CCTV access device) (j) 57 GHz – 64 GHz (SRC device)

References to ETSI standards have been replaced with their equivalent Malaysian Standards if available.

8 Annex A The normative references have been updated.

10 MCMC MTSFB TC T007:2014

Acknowledgements

Members of the Wireless Terminal Working Group

Dr. Wahidah Binti Hashim (Chairman) MIMOS Berhad Mr. Najib Fadil Bin Mohd Bisri (Vice Chairman) Telekom Malaysia Berhad Mrs. Khairunnisa Binti Ab. Halim (Secretary) SIRIM QAS International Sdn Bhd Mr. Mohd Isa Bin Razhali Maxis Communications Berhad Mrs. Aida Razana Binti Omar / SIRIM QAS International Sdn Bhd Mrs. Hafizah Binti Zainal Abiddin / Mrs. Nurhafenah Binti Abdul Jalil / Mrs. Rabiah Binti Ruhan

MCMC MTSFB TC T008:2014

TECHNICAL CODE

SPECIFICATION FOR INTEGRATED SERVICES DIGITAL NETWORK (ISDN) USING BASIC ACCESS

First Revision

Developed by Registered by

Registered date: 18 December 2014

© Copyright 2014

MCMC MTSFB TC T008:2014

DEVELOPMENT OF TECHNICAL CODES

The Communications and Multimedia Act 1998 (‘the Act’) provides for Technical Standards Forum designated under section 184 of the Act or the Malaysian Communications and Multimedia Commission (‘the Commission’) to prepare a technical code. The technical code prepared pursuant to section 185 of the Act shall consist of, at least, the requirement for network interoperability and the promotion of safety of network facilities.

Section 96 of the Act also provides for the Commission to determine a technical code in accordance with section 55 of the Act if the technical code is not developed under an applicable provision of the Act and it is unlikely to be developed by the Technical Standards Forum within a reasonable time.

In exercise of the power conferred by section 184 of the Act, the Commission has designated the Malaysian Technical Standards Forum Bhd (‘MTSFB’) as a Technical Standards Forum which is obligated, among others, to prepare the technical code under section 185 of the Act.

A technical code prepared in accordance with section 185 shall not be effective until it is registered by the Commission pursuant to section 95 of the Act.

For further information on the technical code, please contact:

Malaysian Communications and Multimedia Commission (MCMC) Off Persiaran Multimedia 63000 Cyberjaya Selangor Darul Ehsan MALAYSIA

Tel: +60 3 8688 8000 Fax: +60 3 8688 1000 http://www.skmm.gov.my

OR

Malaysian Technical Standards Forum Bhd (MTSFB) 4805-2-2, Block 4805, Persiaran Flora CBD Perdana 2 Cyber 12 63000, Cyberjaya Selangor Darul Ehsan MALAYSIA

Tel: +60 3 8322 1441/1551 Fax: +60 3 8322 0115 http://www.mtsfb.org.my

i MCMC MTSFB TC T008:2014

CONTENTS Committee Representation ...... iiv FOREWORD ...... v

Section A Introduction ...... 1 1. Scope ...... 1 2. Normative References ...... 1 3. Abbreviations ...... 2 4. General requirements ...... 3 4.1 Design of Equipment ...... 3 4.3 Interoperability ...... 5 5. Electromagnetic Compatibility & Electrical Safety Requirements ...... 5

Section B Basic User-Network Interface – Layer 1 Specification (ITU-T Recommendation I.430 11/1995) ...... 6

Section C ISDN User-Network Interface – Data Link Layer (ITU-T Recommendation Q.921 09/1997 & Amendment 1 06/2000) ...... 14

Section D Network layer requirements based on EN 300 403-1 11/99, Integrated Services Digital Network (ISDN): Digital Subscriber Signaling System No. One (DSS1) protocol: Signaling network layer for circuit-mode basic call control; Part 1: Protocol Specification [ITU-T Recommendation Q.931 (1993), modified]...... 20 1. Introduction ...... 20 2. Supporting Information ...... 20 3. National Option Selections and Clarifications ...... 21 3.1 Layer One Protocol for Basic Call Control (DSS1) ...... 21 3.2 Layer Two Protocol for Basic Call Control (DSS1) ...... 21 3.3 Layer Three Protocol for Basic Call Control (DSS1) ...... 21 4. Terminal Characteristics Related To Access Signaling ...... 26 5. Terminal Adaptors ...... 26 5.1 Circuit Mode Bearer Services ...... 26

ii MCMC MTSFB TC T008:2014

Section E Digital Transmission System on Metallic Local Lines for ISDN Basic Rate Access (ITU-T Recommendation G.961 03/1993) ...... 27

Tables

1 General layer 1 requirements ...... 6 2 Functional characteristics ...... 7 3 Interface procedures ...... 8 4 Layer 1 maintenance ...... 9 5 Electrical characteristics ...... 10 6 Power feeding ...... 12 7 Interface connector contact assignments ...... 13 8 Frame structure for peer-to-peer communication ...... 14 9 Elements of procedure and formats of field for data link layer peer-to-peer communication ...... 14 10 Elements for layer-to-layer communication...... 15 11 Procedures for use by the data link layer ...... 16 12 Annexes and Appendices ...... 18 13 Appendices ...... 21 14 Digital transmission system on metallic local lines for ISDN basic rate access ...... 27 15 Core requirements for a system using 2B1Q line code (ITU-T Rec. Q.961 Appendix II) ... 28 16 Extension functions of the system using 2B1Q line code (Annex A to ITU-T Rec. Q.961 Appendix II) ...... 31

Figure 1 Reference Configurations for ISDN User-Network Interface (Figure 1/I.430) ...... 2

Annexes

A Normative references ...... 32 B Technical Guidelines of ISDN Supplementary Service ...... 33 C Addendum/Corrigendum ...... 1

iii MCMC MTSFB TC T008:2014

Committee Representation

The Fixed Terminal Working Group under the Malaysian Technical Standards Forum Bhd (MTSFB) which developed this Technical Code consists of representatives from the following organisations:

NEC Corporation of Malaysia Sdn.Bhd. SIRIM QAS International Sdn Bhd Telekom Malaysia Berhad TIME dotcom Berhad AJV Holding Sdn Bhd Epson Malaysia Packet One Networks Sdn Bhd Panasonic Malaysia Panasonic System Networks

iv MCMC MTSFB TC T008:2014

FOREWORD

This Technical Code for the Specification for Integrated Services Digital Network (ISDN) Using Basic Access (BA) (First Revision) (‘this Technical Code’) was developed pursuant to section 185 of the Act 588 by the Malaysian Technical Standards Forum Bhd (MTSFB) via its Fixed Terminal Working Group.

This Technical Code was developed for the purpose of certifying communications equipment under the Communications and Multimedia (Technical Standards) Regulations 2000.

This Technical Code cancels and replaces Technical Specification for Connecting to the Integrated Services Digital Network (ISDN) using Basic Access, SKMM FTS ISDN-BA Rev. 1.01:2007.

This Technical Code shall continue to be valid and effective until reviewed or cancelled.

v MCMC MTSFB TC T008:2014

THIS PAGE IS INTENTIONALLY LEFT BLANK

vi

SPECIFICATION FOR INTERGRATED SERVICES DIGITAL NETWORK (ISDN) USING BASIC ACCESS (BA)

Section A

Introduction

1. Scope

1.1. This Technical Code identifies the minimum technical requirements for connecting to the Integrated Services Digital Network (ISDN) at the S/T interface using Basic Access (BA). It also identifies the requirements for the digital transmission system at the network side of the Network Termination (NT1) forming part of the ISDN BA.

1.2. ISDN BA equipment connected to the S/T interface (see Figure 1) shall have e it h e r Terminal Equipment Type 1 (TE1) or Terminal Adaptor (TA) function incorporated. For such equipment, suppliers shall demonstrate that it has been tested to comply with the requirements defined in Section A, B, C and D of this Specification.

Section B – Physical layer requirements based on ITU-T Rec. I.430, Basic Rate User- Network - Interface Layer 1 Specification Section C – Link Access Procedure on the D-channel, LAPD based on ITU-T Rec. Q.921, ISDN User-Network Interface - Data Link Layer Specification Section D – Network layer requirements based on EN 300 403-1 11/99, Integrated Services Digital Network (ISDN): Digital Subscriber Signaling System No. One (DSS1) protocol: Signaling network layer for circuit-mode basic call control; Part 1: Protocol Specification [ITU-T Recommendation Q.931 (1993), modified].

1.3 If the ISDN BA equipment has the NT1 function built-in, suppliers shall demonstrate that it has been tested to comply with the requirements defined in Section A, B, C, D as well as Section E.

1.4. If the NT1 function is standalone, suppliers shall demonstrate that the NT1 equipment has been tested to comply with the requirements defined in Section A and E. Section E defines the digital transmission system at the network side of the NT1, and is based on the ITU-T Rec. G.961. The digital transmission system shall use line codes and transmission methods given in Appendix II of the ITU-T Rec. G.961. References to ETSI ETR 080 are given for information only. The TE side of the NT1 shall conform to the network requirements of the ITU-T Rec. I.430.

2. Normative references

The normative references as in Annex A are indispensable for the application of this Technical Specification. For dated references, only the edition cited applies. For undated references, the latest edition of the normative references (including any amendments) applies.

MCMC MTSFB TC T008:2014

Figure 1. Reference Configurations for ISDN User-Network Interface (Figure 1/I.430)

3. Abbreviations

The use of the term TE within the Specification refers to a TE1, a TA or a Network Termination 2 (NT2).

The following notations are used in this Specification :

CR Conformance Requirement defines features and functions that must be supported at minimum. M Mandatory requirement is where the TE implementation shall conform to those clauses in that section relating to the operation of Layer 1, Layer 2 and Layer 3 protocol in the TE. O Optional requirement means it is optional whether TE implements that function but if function is implemented, it shall conform to the clauses in that section relating to the operation of the TE Layer 1, Layer 2 and Layer 3 protocol.

However, the use of optional functions is possible only if the network operators have implemented these options in their networks. NA Not Applicable is where the requirements specified in that section on the TE shall not be applicable for attachment. GID The section provides General Information and Definitions. TE1 ISDN-capable terminal equipment e.g.: Digital phone and digital fax TE2 Non-ISDN equipment e.g: Analogue phone and the RS-232 serial port on computer TA Terminal adapter that interface the TE2 devices with ISDN network NT1 Network terminator that reside between telco’s network and customer equipment NT2 An intelligent device that can perform switching function e.g: PABX and Local Area Network (LAN)

2 MCMC MTSFB TC T008:2014

4. General requirements

4.1 Design of Equipment CR

Power supply a) For AC powered TE, the operating voltage shall be Note 1 rated/ marked at 230V or 240V in line with the country's nominal voltage and frequency in accordance to MS IEC 60038. If the product is rated with multiple or a range of voltages, voltage range between 230V (+10%,-6%) shall be included. Testing shall be conducted based on 230V (+10%,-6%) or 240V and other relevant voltages, if the product is marked with multiple or a range of voltages

b) Product shall be rated/ marked at 50Hz and testing shall be conducted at 50Hz. If the product is marked at 50/60Hz or 50-60Hz then testing shall be conducted either at 50Hz or 60Hz, whichever is more unfavourable

c) Where external power supply is used, e.g AC adaptor, it shall not affect the capacity of the equipment to meet this specification. Adaptor must be pre- approved by the relevant regulatory body before it can be used with the equipment.

NOTE: Either one of these options shall be applied.

Identification of Equipment shall be marked with: equipment a) supplier’s or manufacturer’s name or identification M mark b) supplier’s or manufacturer’s model or type reference M The markings shall be legible, indelible and readily visible M

Keypad Dialling a) Keypads used in equipment for dialling shall be M alphanumeric keypads and the relationships between the letters and the digits shall comply with ITU-T Rec E.161 as shown in Figure 2. b) The associated letters shall not impair the legibility M of the digit (§ 3.1.1, ITU-T Rec. E.161). c) The `tactile identifier on the “5” button shall be M provided (§ 3.6, ITU-T Rec. E.161).

3 MCMC MTSFB TC T008:2014

1 2 3 ABC DEF

4 5 6 GHI JKL MNO

7 8 9 PQRS TUV WXYZ

* 0 #

Figure 2. Alphanumeric Keypad Layout (ITU-T Rec. E. 161)

4.2 Interface

4.2.1 Network Interface

Connector 2 wire or RJ45 Feed voltage 48 V to 110 V d.c Line Coding 2B1Q Impedance 120 Ω (RJ45) Switch type 3

4.2.2 Analogue Interface

When provided, the equipment has the TA function for connecting analogue equipment at the R interface as shown Figure 1.

Connector RJ 11 jack or RJ45 jack Note 2 Feed voltage ≤ 40 V DC Note 2 Line extension Interworking with loop resistance up to 500 Ω Note 2 MFPB receiver a) Level range: 0 dBm to -26 dBm Note 2 b) Signal detection: min 40ms Note 2 c) Interdigit pause : min 40ms Note 2 d) Frequency deviation: ± 1.8% Note 2 Ringing current transmit a) Frequency: 24Hz Note 2 b) Periodicity for normal ringing: 0.4s (on), 0.2s (off), 0.4s Note 2 (on), 2.0s (off) c) Periodicity for duplex/distinctive ringing: 1.2s (on), 3.0s Note 2 (off) d) Voltage: ≤ 75V Note 2 Dial tone transmit 425 Hz continuous tone Note 2

4 MCMC MTSFB TC T008:2014

Busy tone transmit a) 425 Hz Note 2 b) Periodicity: 0.75 s (on), 0.75 s (off) Note 2 Output level Analogue output signal level shall not exceed -6 dBm Note 2 averaged over any 10s period A/D/A companding Digital telephones and other customer equipment providing acoustic interfaces to the digital bit stream shall comply with ITU-T G.711 (A-law).

NOTE: Requirement is ‘NA’ if TE does not have TA function for connecting analogue equipment to the R interface.

4.3 Interoperability

TE1 and TA are dynamically interoperable if they implement a common and compatible set of features, functions and options and can demonstrate satisfactory mutual communication in a real network architecture environment as performance test conditions are varied and exercised. It is mandatory that the TE1 and TA be tested with the respective Service Provider to ensure interoperability. The general reference model for interoperability is shown in Figure 1.

5. Electromagnetic Compatibility & Electrical Safety Requirements

5.1 The equipment shall comply with the limits for conducted disturbance at the mains terminals and telecommunication ports, and the limits for radiated disturbance defined in the IEC CISPR 22.

5.2 The equipment shall comply with the IEC 60950-1 safety standard1. The requirements in IEC 60950-1 that are applicable to the equipment [e.g. class of equipment, type of telecommunication network voltage (TNV) circuit and types of components shall be identified and complied with.

1 The safety standard includes, among others, protection of telecommunications network service personnel and users of other equipment connected to the network from hazards in the equipment.

5 MCMC MTSFB TC T008:2014

Section B

Basic User-Network Interface – Layer 1 Specification (ITU-T Recommendation I.430 11/1995)

Table 1. General layer 1 requirements

ITU-T Rec. ETSI Title CR Remarks I.430 TBR 3

General 1 – GID Service characteristics 2 – – Heading Services required from the 2.1 – M A balance metallic transmission physical medium medium for each direction of transmission capable of supporting 192 kbit/s Service provided to layer 2 2.2 – – Primitives between layer 1 and 2.3 – M the other entities Modes of operation 3 – GID Point-to-point operation 3.1 – M Point-to-multipoint operation 3.2 – M Types of wiring configuration 4 – GID Point-to-point configuration 4.1 – Note Point-to-multipoint configuration 4.2 – Note Wiring polarity integrity 4.3 – M Location of the interfaces 4.4 – GID NT and TE associated wiring 4.5 – M NOTE: Either one of these wiring configuration shall be applied.

6 MCMC MTSFB TC T008:2014

Table 2. Functional characteristics

ITU-T ETSI Title CR Remarks Rec. I.430 TBR 3 Functional characteristics 5 – GID Heading Interface functions 5.1 – – Heading B-.1.1 – M For each direction of transmission, provides two independent 64 kbit/s channels for use as B-channels Bit timing 5.1.2 – M Provides bit timing at 192 kbit/s Octet timing 5.1.3 – O Provides 8 kHz octet timing Frame alignment 5.1.4 – M Provides information to enable NT and TE to recover the TDM channels D-channel 5.1.5 – M For each direction of transmission, provides one D- channel at a bit rate of 16 kbit/s D-channel access procedure 5.1.6 – M For procedures relating to D- channel access see Clause 6.1. Power feeding 5.1.7 – GID Refer to Clause 9 Deactivation 5.1.8 – M Refer to Clause 6.2 Activation 5.1.9 – M Refer to Clause 6.2 Interchange circuits 5.2 – M Two interchange circuits, one for each direction of transmission shall be used to transfer digital signals across the interface. Connected/disconnected indication 5.3 – M The criterion used is the appearance/disappearance of power. TEs powered across the interface 5.3.1 – M TEs not powered across the 5.3.2 – M interface Indication of connection status 5.3.3 – M Frame structure 5.4 – M In both direction of transmission, the bits shall be grouped into frames of 48 bits each. Line code 5.5 9.3.2 M Figure 4/I.430 Timing considerations 5.6 – M A TE shall derive its timing from the signal received from NT and use this derived timing to synchronise its transmitted signal.

7 MCMC MTSFB TC T008:2014

Table 3. Interface procedures

ITU-T Rec. ETSI Title CR Remarks I.430 TBR 3 Interface procedures 6 – – Heading D-channel access procedure 6.1 9.4.1 M Interframe (layer 2) time fill 6.1.1 9.4.1.1 M Interframe time fill in the NT to TE direction is HDLC flags. D-echo channel 6.1.2 – NA Network requirement D-channel monitoring 6.1.3 – M Priority mechanism 6.1.4 9.4.1.2 M The use of priority class 2 is not a requirement under TBR 3. Collision detection 6.1.5 9.4.1.3 M Priority system 6.1.6 – M An example of how the priority system may be implemented. Activation/deactivation 6.2 9.4.2 – Heading Definitions 6.2.1 – – Heading TE states 6.2.1.1 9.4.2.1 M PS2 is not a requirement under TBR 3. Loss of local power or absence of power from PS1 may be used for determining the connection status. NT states 6.2.1.2 – NA Activate primitives 6.2.1.3 – M Deactivate primitives 6.2.1.4 – M Management primitives 6.2.1.5 – O Valid primitive sequences 6.2.1.6 – NA Signals 6.2.2 9.4.2.2 M Activation/deactivation procedure 6.2.3 9.4.2.3 M for TEs Activation/deactivation for NTs 6.2.4 – NA Timer values 6.2.5 9.4.2.3.2 O Timer 3 < 30 s Activation times 6.2.6 – – Heading TE activation times 6.2.6.1 9.4.2.4 M NT activation times 6.2.6.2 – NA Deactivation times 6.2.7 9.4.2.5 M Frame alignment procedures 6.3 9.4.3 M

8 MCMC MTSFB TC T008:2014

Table 3. Interface procedures (continued)

ITU-T ETSI Title CR Remarks Rec. I.430 TBR 3 Frame alignment procedure in the 6.3.1 9.4.3 M Loss of frame alignment is assumed direction NT to TE Note 1 when a time period equivalent to 2 (“n” in the case of TBR 3) 48-bit frames has elapsed without having detected valid pairs of line code violations obeying the  14-bit criterion as described in § 5.4.2.2. Frame alignment may be assumed to occur when 3 (“m” in the case of TBR 3) consecutive pairs of line code violations obeying the  14-bit criterion have been detected. Frame alignment in the direction TE 6.3.2 – NA to NT

Multiframing 6.3.3 9.4.4 O The use of Q-channel and S- channel is Note 2 optional. The use of S-channel is optional. S-channel structuring algorithm 6.3.4 – O

Idle channel code on the B- 6.4 9.4.5 M channels

NOTES: 1. In TBR 3, “n” is a value between 2 to 20, and “m” is a value between 3 and 100. There is no requirement for “m” and “n” to remain constant under all circumstances of loss and recovery of frame alignment. The recommended values for “m” and “n” are 5. 2. Under TBR 3, when the TE receives an FA bit which is binary ZERO, it shall send a binary ZERO in the corresponding FA bit position of the frame transmitted to the NT. No requirement applies when the FA bit received is a binary ONE.

Table 4. Layer 1 maintenance

ITU-T ETSI Title CR Remarks Rec. I.430 TBR 3 Layer 1 maintenance 7 – Heading Provision for operational and maintenance functions between 7.1 – O terminal and NT1

9 MCMC MTSFB TC T008:2014

Table 5. Electrical characteristics

ITU-T Rec. ETSI Title CR Remarks I.430 TBR 3 Bit rate 8.1 9.2.1 M 192 kbit/s < ± 100 ppm Jitter and bit-phase relationship 8.2 9.2.2 – Heading between TE input and output Test configurations 8.2.1 9.2.2.1 GID Timing extraction jitter 8.2.2 9.2.2.2 M ± 7% 9.2.2.3Not Total phase deviation input to 8.2.3 M -7% to +15% output e 1

NT jitter characteristics 8.3 – NA Termination of the line 8.4 – NA Transmitter output characteristics 8.5 9.2.3 – Heading Transmitter output impedance 8.5.1 – GID NT transmitter output impedance 8.5.1.1 – NA TE transmitter output impedance 8.5.1.2 9.2.3 M Test load impedance 8.5.2 – M 50  Pulse shape and amplitude 8.5.3 9.2.4 Headin Figure 13/I.430 (binary ZERO) g 750 mV Within the threshold as given in figure 9.5 (TBR 3) / Figure 13/I.430 Pulse unbalance 8.5.4 9.2.5 M  5%

Voltage on other test loads (TE 8.5.5 9.2.6.1 M 400  load and only) 9.2.6.2 5.6  load 10 kHz  f  300 kHz :  54 dB Unbalance about earth 8.5.6 M – 300 kHz < f  1 MHz : min. value decreasing from 54 dB at 20 dB/decade Longitudinal conversion loss – 9.2.7 – 10 kHz  f  300 kHz : (LCL) of the transmitter output  54 dB Receiver input characteristics 8.6 – – Heading Receiver input impedance 8.6.1 – – Heading

TE receiver input impedance 8.6.1.1 9.2.8 M As specified in § 8.5.1.2/I.430

NT receiver input impedance 8.6.1.2 – NA Receiver sensitivity – Noise and 8.6.2 9.2.9 M distortion immunity TEs 8.6.2.1 9.2.9 M NTs for short passive bus 8.6.2.2 – NA NTs for point-to-point and short 8.6.2.3 – NA passive

10 MCMC MTSFB TC T008:2014

Table 5. Electrical characteristics (continued)

ITU-T ETSI Title CR Remarks Rec. I.430 TBR 3 NTs for extended passive bus 8.6.2.4 – NA NTs for point-to-point configuration 8.6.2.5 – NA NT receiver input delay 8.6.3 – NA characteristics 10 kHz  f  300 kHz :  54 dB Unbalance about earth 8.6.4 – M 300 kHz < f  1 MHz : min. value decreasing from 54 dB at 20 dB/decade Longitudinal Conversion Loss (LCL) of receiver inputs – – 9.2.10 – 10 kHz  f  300 kHz :  54 dB Isolation from external voltages 8.7 – GID Interconnecting media 8.8 – M characteristics Standard ISDN basic access TE 8.9 9.1.4 M cord Longitudinal output voltage 8.10 – GID Electromagnetic compatibility (EMC) 8.11 – Note 2

NOTES: 1. The limitation applies for input bit rates of 192 kbit/s ± 1 ppm. 2. EMC requirements are specified in § 3 of this Specification.

11 MCMC MTSFB TC T008:2014

Table 6. Power feeding

ITU-T Rec. ETSI Title CR Remarks I.430 TBR 3 Power feeding 9 9.5 – Heading Reference configuration 9.1 – M The use of leads c, d, e and f is mandatory. Functions specified at the access 9.1.1 9.5.1 M 9.1.1 i) is mandatory. leads Provision of power sources and 9.1.2 – O PS3 is not used. sinks Power feeding voltage 9.1.3 – M Basic voltage range is 34 V to 42 V from the power source. Power available from NT 9.2 – O Heading Power source 1 normal and 9.2.1 – O restricted mode Voltage NT from power source 1 9.2.2 – O Voltage of power source 2 9.2.3 – O Short circuit protection 9.2.4 – M Power available at TE 9.3 – O Heading Power consumption unit 9.3.1 – O Power source 1 - Phantom 9.3.2 – O powering Power source 2 - Optional third 9.3.3 – O pair PS1 current transient 9.4 9.5.2 M Applicable to TE drawing from power source 1 TE power consumption 9.5 – GID Heading Power source 1 9.5.1 9.5.3 M Applicable when power sink 1 is implemented Power source 2 9.5.2 Note 1 M Applicable when power sink 2 is implemented Galvanic isolation 9.6 9.5.4 Note M Isolation shall be a minimum of 1 M 2 when measured at 500 V d.c. Limitations on power source and 9.7 9.5.5 GID sink during transient condition Current/time limitations for TEs 9.7.1 – – Heading Terminals powered from power 9.7.1.1 9.5.5.1 O Applicable when power sink 1 is source 1 implemented Terminals powered from power 9.7.1.2 Note 1 O Applicable when power sink 2 is source 2 implemented Power source switchover time 9.7.2 – O Applicable when switchover is (PS1 or PS2) implemented Other TE requirements 9.7.3 9.5.5.2 – Heading Minimum TE start up current from 9.7.3.1 9.5.5.2.1 O Applicable when power sink 1 is power source 1 implemented

12 MCMC MTSFB TC T008:2014

Table 6. Power feeding (continued)

ITU-T ETSI Title CR Remarks Rec. I.430 TBR 3

Minimum TE start up current from 9.7.3.2 Note 1 O Applicable when power sink 2 is power source 2 implemented

Verification 9.7.3.3 – GID Test circuit given in Clause I.6

Protection against short term 9.7.3.4 9.5.5.2. M interruptions 2

Behaviour at switch-over 9.7.3.5 9.5.5.2. O Applicable when switch-over is 3 implemented

Effective capacitance at the PS1 or 9.7.3.6 – GID PS2 input to the TE TE behaviour at low input voltage 9.7.3.7 – GID Other power source requirements 9.7.4 – O PS1 direct current unbalance 9.8 – GID TE requirements 9.8.1 9.5.5.3 O NT requirements 9.8.2 – NA Additional requirements for an 9.9 – NA auxiliary power supply (APS) Additional requirements for NT1 restricted mode source for 9.10 – NA compatibility with an APS

NOTES: 1.Under TBR 3, PS2 is not supported. 2.Under TBR 3, for galvanic connection to earth, the direct current between PS1 and any earth connection on the TE shall not exceed 100A.

Table 7. Interface connector contact assignments

ITU-T ETSI Title CR Remarks Rec. I.430 TBR 3

Interface connector contact 10 9.1 M Contacts a, b, g and h are not used. assignments Note

NOTE. The use of contacts a, b, g and h for PS2 and PS3 is outside the scope of TBR 3.

13 MCMC MTSFB TC T008:2014

Section C

ISDN User-Network Interface – Data Link Layer (ITU-T Recommendation Q.921 09/1997 & Amendment 1 06/2000)

Table 8. Frame structure for peer-to-peer communication

ITU-T Rec. ETSI Title CR Remarks Q.921 TBR 3 General 1 – GID Frame structure for peer-to-peer 2 10.1 GID Heading communication General 2.1 10.1.1 M Flag sequence 2.2 10.1.2 M Address field 2.3 10.1.3 M Control field 2.4 10.1.4 M Information field 2.5 10.1.5 M Transparency 2.6 10.1.6 M FCS field 2.7 10.1.7 M Format convention 2.8 10.1.8 – Invalid frames 2.9 10.1.9 M Note Frame abort 2.10 – M Not a TBR 3 requirement

NOTE. TBR 3 includes a frame which contains a TEI that is not assigned to the TE as invalid.

Table 9. Elements of procedure and formats of field for data link layer peer-to-peer communication

ITU-T Rec. ETSI Title CR Remarks Q.921 TBR 3 Elements of procedure and formats of field for data link layer 3 10.2 – Heading peer-to- peer communication General 3.1 10.2.1 GID Address field format 3.2 10.2.2 M Address field variables 3.3 10.2.3 – Control field formats 3.4 10.2.4 M Control field parameters and 3.5 10.2.5 M associated state variables Poll/Final (P/F) bit 3.5.1 10.2.5.1 M Multiple frame operation - 3.5.2 10.2.5.2 – variables and sequence numbers Unacknowledged operation - 3.5.3 – GID One parameter is defined, N201 (see variables and parameters 5.9.3).

14 MCMC MTSFB TC T008:2014

Table 9. Elements of procedure and formats of field for data link layer peer-to-peer communication (continued)

ITU-T ETSI Title Rec. CR Remarks Q.921 TBR 3 Frame types 3.6 10.2.6 – Heading Commands and responses 3.6.1 10.2.6.1 M Refer to Table 5/Q.921 Note Information (I) command 3.6.2 10.2.6.2 M Set Asynchronous Balanced Mode 3.6.3 10.2.6.3 M Extended (SABME) command Disconnect (DISC) command 3.6.4 10.2.6.4 M Unnumbered Information (UI) 3.6.5 10.2.6.5 M command Receive Ready (RR) 3.6.6 10.2.6.6 M command/response Reject (REJ) command/response 3.6.7 10.2.6.7 M Receive Not Ready (RNR) 3.6.8 10.2.6.8 M command/response Unnumbered Acknowledgement 3.6.9 10.2.6.9 M (UA) response Disconnected Mode (DM) response 3.6.10 10.2.6.1 M 0 Frame Reject (FRMR) response 3.6.11 – M Note Exchange Identification (XID) 3.6.12 – M Note command/response

NOTE. TBR 3 does not support FRMR response and XID command/response.

Table 10. Elements for layer-to-layer communication

ITU-T ETSI Title Rec. CR Remarks Q.921 TBR 3

Elements for layer-to-layer 4 – GID communication

15 MCMC MTSFB TC T008:2014

Table 11. Procedures for use by the data link layer

ITU-T Rec. ETSI Title CR Remarks Q.921 TBR 3 Definition of peer-to-peer 5 – GID procedures for the data link layer Procedures for the use of P/F bit 5.1 – – Heading

Unacknowledged information 5.1.1 10.4.1 M transfer

Acknowledged multiple frame 5.1.2 10.6 and M information transfer 10.7 Procedure for unacknowledged 5.2 10.4 – Note 1 information transfer Terminal Endpoint Identifier (TEI) 5.3 10.5 – management procedures General 5.3.1 10.5.1 M Note 2 TEI assignment procedure 5.3.2 10.5.2 M Note 2 TEI check procedure 5.3.3 – – Heading Use of TEI check procedure 5.3.3.1 – NA

Operation of the TEI check 5.3.3.2 10.5.3 M Note 3 procedure TEI removal procedure 5.3.4 10.5.4 M Note 3 TEI identity verify procedure 5.3.5 10.5.5 O Note 3 Formats and codes 5.3.6 10.5.6 – Note 3 Initialisation of data link layer 5.4 – NA Note 4 parameters Procedure for establishment and 5.5 10.6 – Heading release of multiple frame operation

Establishment of multiple frame 5.5.1 10.6.1 M operation Information transfer 5.5.2 10.4, 10.7 M Refer to Clauses 5.2, 5.6 and 5.7 and 10.8

Termination of multiple frame 5.5.3 10.6.2 – operation TEI-assigned state 5.5.4 – M

Collision of unnumbered 5.5.5 10.6.3 – commands and responses Unsolicited DM response and 5.5.6 – M SABME or DISC command

Procedure for information 5.6 10.7 M transfer in multiple frame operation

Re-establishment of multiple 5.7 10.8 – frame operation

16 MCMC MTSFB TC T008:2014

Table 11. Procedures for use by the data link layer (continued)

ITU-T ETSI Title Rec. CR Remarks TBR 3 Q.921

Exception condition reporting and 5.8 10.9 GID recovery Note 5 List of system parameters 5.9 10.10 GID

Timer T200 5.9.1 10.10.1 M The default value shall be 1 s.

Max number of retransmissions 5.9.2 10.10.2 M The default value shall be 3. (N200)

Max number of octets in an 5.9.3 10.10.3 M The default value shall be 260 octets. information field (N201)

Max number of transmission of the 5.9.4 10.10.4 M The default value shall be 3. TEI identity request message (N202)

Max number of outstanding I 5.9.5 10.10.5 M For a SAP supporting basic access frames (k) signaling, the value is 1.

Timer T201 5.9.6 – NA Network requirement

Timer T202 5.9.7 10.10.6 M The default value shall be 2 s.

Timer T203 5.9.8 – O The default value is 10 s. – – 10.10.7 GID Layer 2 response time Note 6 Data link monitor function 5.10 – O

NOTES: 1. ‘NA’ if TE is an ISPBX and supports configuration using only a single point-to-point data link. 2. ‘NA’ if TE supports configuration using only a single point-to-point data link. Requirements are applicable if TE is ISPBX. 3. ‘NA’ if TEI assignment procedure is ‘NA’. 4. The data link layer parameters shall be initialised to default values. 5. TBR 3 considers the receipt of an invalid N(R) as the only condition for frame rejection. 6. The maximum time between receipt of an incoming frame, and generation of a response shall not exceed (a) 500 ms if operating in a point-to-point signaling connection; and (b) 200 ms for TEs in point- to-multipoint configuration.

17 MCMC MTSFB TC T008:2014

Table 12. Annexes and Appendices

ITU-T Rec. ETSI TBR Title CR Remarks Q.921 3 Provision for point-to-point data Annex A 10.3 M For single point-to-point signaling link connection connection at layer 3, TEI value 0 shall be used in combination with SAPI 0. TEI management procedures are not applicable. An SDL representation of the point-to- point procedures of data Annex B – – link layer SDL representation of the Annex C – – broadcast procedures of the data link layer State transition table of the point- to- point procedures of the data Annex D – – link layer Provision of multi-selective reject Annex E – GID option Protocol Implementation Conformance Statement (PICS) Annex F – GID to Recommendation Q.921 for Basic Rate (User-side) Protocol Implementation Conformance Statement (PICS) Annex G – GID to Recommendation Q.921 for Basic Rate (Network-side) Protocol Implementation Conformance Statement (PICS) Annex H – NA to Recommendation Q.921 for Primary Rate (User-side) Protocol Implementation Conformance Statement (PICS) Annex I – NA to Recommendation Q.921 for Primary Rate (Network-side) Inter-exchange signaling data Annex J – GID Applicability and additions to frame link layer protocol in Private (Q.921 structure, elements of procedures, Integrated Services Networks Amend-ment formats of fields, elements for layer- (PISNs) 1) to-layer communication, peer-to-peer procedures to accommodate PISN inter-exchange requirements Retransmission of REJ response Appendix I – NA frame

18 MCMC MTSFB TC T008:2014

Table 12. Annexes and Appendices (continued)

ITU-T ETSI Title Rec. CR Remarks TBR 3 Q.921 Occurrence of MDL-ERROR- INDICATION within the basic states Appendix – M & actions to be taken by the II management entity Optional basic access deactivation Appendix – NA May be used by network side system procedures III management to control deactivation of access Automatic negotiation of data link Appendix – NA layer parameters IV Inter-exchange signaling data link Appendix – GID Occurrence of the MDL-ERROR layer protocol in PISNs V (Q.921 indication primitive in the data link Amend- layer protocol for the support of Inter- ment 1) exchange signaling in PISNs

19 MCMC MTSFB TC T008:2014

Section D

Network layer requirements based on EN 300 403-1 11/99, Integrated Services Digital Network (ISDN): Digital Subscriber Signaling System No. One (DSS1) protocol: Signaling network layer for circuit-mode basic call control; Part 1: Protocol Specification [ITU-T Recommendation Q.931 (1993), modified]

1. Introduction

This section contains clarification and recommended option selections for the ETSI ISDN standards and technical reports related to basic call control procedures of ISDN basic and primary access signaling. This document covers the basic call control of layers 1, 2 and 3. The aim of this document is to avoid unnecessary options and vagueness in ISDN implementations and to ensure the interoperability of ISDN networks and terminal equipment in Malaysia. This requirement has to be followed when implementing access-signaling protocol i.e. Digital Subscriber Signaling System No. 1 (DSS1).

2. Supporting Information

2.1 Integrated Services Digital Network (ISDN): Standards Guide (ETR 076 – December 1996, Fourth Edition)

2.2 Integrated Services Digital Network (ISDN): Customer Access Maintenance (ETR 001 August 1990)

2.3 Integrated Services Digital Network: User –Network interface layer 3 Specifications for basic call control (ETS 300 102-1 12/90)

2.4 Integrated Services Digital Network (ISDN): Digital Subscriber Signaling System No.(DSS1) protocol: Data link layer; Part 2: General protocol specification [ITU-T Recommendation Q.921 (1993), modified] (ETS 300 402-2 11/95).

2.5 Integrated Services Digital Network (ISDN):Digital Subscriber Signaling System No.One (DSS1) protocol: Signaling network layer for circuit-mode basic call control; Part 1: Protocol Specification [ITU-T Recommendation Q.931 (1993), modified] ) (ETS 300 403-1 11/95)

2.6 Integrated Services Digital Network (ISDN): Digital Subscriber Signaling System No.One (DSS1) protocol: Signaling network layer for circuit-mode basic call control; Part 1: Protocol Specification [ITU-T Recommendation Q.931 (1993), modified] (EN 300 403-1 11/99).

2.7 Integrated Services Digital Network (ISDN): Digital Subscriber Signaling System No.One (DSS1) Protocol: Signaling Network Layer For Circuit-Mode Basic Call Control: Part 2: Specification and Description Language (SDL) Diagrams (ETS 300 403-2 11/95).

2.8 Integrated Services Digital Network (ISDN) : Application Of The Bearer Capability (BC), High Layer Compatibility (HLC) and Low Layer Compatibility (LLC) Information Elements By Terminals Supporting ISDN Services (ETR 018 11/95)

2.9 ISDN User –Network Interface Layer 3 Specification for basic call control (ITU-T Q.931 3/93)

2.10 Technical Guidelines of ISDN Supplementary Services (Functional Protocol)

20 MCMC MTSFB TC T008:2014

3. National Option Selections and Clarifications

3.1 Layer One Protocol for Basic Call Control (DSS1)

The DSS1 basic call layer one protocol for the basic access is contained in the standard ETS 300 012 (10/98) and for the primary rate access in the standard ETS 300 011 (3/98)

The ETSI technical report ETR 001(8/90) defines the maintenance requirement for basic and primary access.

3.2 Layer Two Protocol for Basic Call Control (DSS1)

The DSS1 basic call layer two protocol for the basic and primary access is contained in the standard ETS 300 402-1 (11/95).

It is recommended that a reset of layer 3 always reset layer 2 in ISDN-terminal equipment. If layer 3 can be reset without resetting layer 2, an ISDN terminal which is reset during the active phase of a call, may lose control over that call.

3.3 Layer Three Protocol for Basic Call Control (DSS1)

The DSS1 layer three protocol for basic call control is contained in the base standard ETS 300 102-1 (12/90), ITU-T Q.931 (3/93), ETS 300 403-1 (11/95) and EN 300 403-1 (11/99). ). The EN 300 403-1 (11/99) is a main standard for DSSI Layer 3 implementation.

When implementing the DSS1 layer three protocol in Malaysia network, the following guidelines are recommended to be taken into account (The main numbering refers to the ITU-T Q.931 (3/93), this standard had been adopted and extended by EN 300 403-1 (11/99).

Table 13. Appendices

Clause No. Clause Description Recommendation

OVERVIEW OF CALL SDL diagrams in the standard ETS 300 403-2 (11/95) are 2 CONTROL recommended to be used as informative. The transport of low layer compatibility information element (LLC) to the calling user is supported on the ISDN end-to-end connections. 3.1.3 CONNECT The date/time information element is recommended to be sent by the network. The use of Keypad facility information element is defined in EN 300 INFORMATION 122-1 (6/98), "Integrated Services Digital Network (ISDN); Generic 3.1.6 keypad protocol for the support of supplementary services; Digital Subscriber Signaling System No. One (DSS1) protocol; Part 1: Protocol Specification ".

21 MCMC MTSFB TC T008:2014

Table 13. Appendices (continued)

Clause No. Clause Description Recommendation

Annex E (network specific facility selection) and Annex C (transit network selection) are not applicable. Transit network selection is implemented in the DSS1 signaling by using operator codes in the called number digits (operator code + called party number).

The use of Keypad facility information element is defined in EN 300 3.1.14 SETUP 122-1 (6/98).

Two bearer capability information elements are supported (EN 300 403-1 (11/99), subclause 5.11).

Two high layer compatibility information elements are supported (EN 300 403-1(11/99), subclause 5.12) General message 4 format and information elements coding 4.4 MESSAGE TYPE No national message types are defined. 4.5.1.1 (EN Information elements Network specific facilities, Transit network 300 403-1 Codeset 0 selection and Escape for extension are not applicable. 11/99) 4.5.2 Extension of codesets No information elements belonging to codeset 6 (national) are defined. 4.5.7 Call state Only CCITT standardized coding is used. Type of number: Code point showing "subscriber number" shall be used from network to user.

4.5.8 Called party number The code point used in connection with the supplementary services Direct Dialing In (DDI) and Multiple Subscriber Number (MSN) is specified in a separate document for ISDN supplementary services Technical Guidelines of ISDN Supplementary Services(Functional Protocol)

Calling party number The use of the fields is subject to a separate document for ISDN 4.5.10 supplementary services Technical Guidelines of ISDN Supplementary Services(Functional Protocol) Coding standard: Codepoints showing “CCITT standardized coding” and "National standard" may be used. 4.5.12 Cause

No national cause values are defined. 4.5.13 Channel identification Coding standard: CCITT standardized coding is always used 4.5.15 Date/time The date/time indicated is local date / time Network specific Not applicable. 4.5.21 facilities 4.5.22 Progress indicator Coding standard: CCITT standardized coding is always used.

22 MCMC MTSFB TC T008:2014

Table 13. Appendices (continued)

Clause No. Clause Description Recommendation

Not applicable. 4.5.29 Transit network selection Transit network selection is implemented in the DSS1 signaling by using operator codes in the called number digits (operator code + called party number) Optional extensions to the basic protocol and exceptions that apply in CIRCUIT-SWITCHED the case of supplementary services are not subject to this guideline 5 CALL CONTROL document. PROCEDURES An INFORMATION message received in the Release Request State shall be ignored.

The network shall recognize both the sending complete information 5.1.1 Call request element and the "#" character.

5.1.3 Overlap sending In case (a) the dial tone option with Progress Indicator #8 is applied

Not applicable. Transit network selection is implemented in the DSS1 signaling 5.1.10 Transit network selection by using operator codes in the called number digits (operator code + called party number).

It is recommended for the basic access that a timer is implemented on the network side in order to ensure that layer 2 is released if during a time period, (e.g. 10-15 seconds) no layer 3 connections are present on the data link. CALL ESTABLISHMENT AT In special cases, e.g. NT2, data link connections may be 5.2 THE DESTINATION established as soon as TEI is assigned (either locally or by the INTERFACE automatic assignment procedure), and may be retained indefinitely.

It is recommended that a reset of layer 3 always reset layer 2 in ISDN-terminal equipment. If layer 3 can be reset without resetting layer 2, an ISDN terminal which is reset during the active phase of a call, may lose control over that call. The network shall have the knowledge that a single-point 5.2.1 Incoming call configuration exists, and that information is entered at the time of configuration of the access.

SETUP message Only options 1) "channel is indicated, no acceptable alternative" and 5.2.3.1 delivered by point-to- 4) "no B channel available" are used. point data link

In overlap receiving the network cannot in all cases determine that sufficient call setup information has been received, and the Sending complete information element is not required (Refer to 5.2.4 Overlap receiving Technical Guidelines of ISDN Supplementary Services (Functional Protocol), DDI).

23 MCMC MTSFB TC T008:2014

Table 13. Appendices (continued)

Clause No. Clause Description Recommendation

Notification of Concerning the first subsection a) the normal call handling interworking at the procedures shall be applied at the terminating exchange (i.e. the 5.2.6 terminating interface terminating exchange shall only through-connect after a CONNECT message has been received from the called user).

In case the private exchange has diverted the speech call it is recommended that the Calling party is informed of the diversion (with an announcement) if the private exchange sends the call acceptance message (CONNECT) towards the Calling party before the call acceptance message has been received from the diverted connection. This in-band information is given immediately after the call 5.2.7 Call accept acceptance message sending.

Note: Establishment of the bearer connection prior to call acceptance is described in ETS 300 403-1 Annex K. If this procedure is applied then the inband information is given prior the call acceptance message sending. Clearing when In order to receive the inband information it is recommended that 5.3.4.1 tones/announcements the user connects to the B-channel on receipt of the provided DISCONNECT message with progress indicator No. 8. 5.3.4bis (EN Absence of response In case a B-channel is placed in a maintenance condition, the actions 300 403-1 to be taken are described in subclause 5.5. 11/99) during call clearing When the call identity is used, it is recommended for the terminals to 5.6.1 Call suspension use IA5-coded characters. When the call identity is used, it is recommended for the terminals to 5.6.2 Call suspended use IA5- coded characters. The network shall preserve the call identity along with a clearing 5.6.5 Call resume errors cause during the period of timer T307.

Information element out The network is not required to process information elements 5.8.5.1 of sequence received out of sequence

Duplicated information The BC (Bearer Capability) and HLC (High Layer Compatibility) 5.8.5.2 elements information elements may be duplicated in the SETUP message (EN 300 403-1 (11/99), subclause 5.11 and 5.12).

Non-mandatory Information elements exceeding the maximum length shall not be 5.8.7.2 information element truncated and processed except the call identity information element.

content error

It is recommended that the network transmits a STATUS ENQUIRY 5.8.9 Data link failure message when layer 2 is re-established.

Signaling procedures for Supported on ISDN end-to-end connections (i.e. the network signaling 5.11 bearer capability system is ISUP). selection

24 MCMC MTSFB TC T008:2014

Table 13. Appendices (continued)

Clause No. Clause Description Recommendation

Signaling procedures for Supported on ISDN end-to-end connections (i.e. the network signaling 5.12 high layer compatibility system is ISUP). selection Timers in the network Timer No. 302 : Time-out value is 5s 9.1 side Timer No. 301 : Time-out value is 3 min. 9.2 Timers in the user side

Compatibility and Annex B address checking Codings of BC, HLC and LLC are subject to the ETR 018 (11/95). B.1 INTRODUCTION

Called party number (whole subscriber number) is always included in the SETUP message from the network to user in point-to- multipoint configurations.

COMPATIBILITY CHECKING WITH Compatibility checking with addressing information should be used in B.3.1 ADDRESSING terminals, since otherwise it may restrict the use of several terminals INFORMATION in the same access or the use of multi-service terminals. (Further information can be found in the supplementary services guideline document Technical Guidelines of ISDN Supplementary Services (Functional Protocol), e.g. Multiple Subscriber Number supplementary service). B.4 INTERWORKING WITH When a Progress indicator information element #1 or #3 is sent to EXISTING NETWORKS the terminal equipment, the network will not send the High layer or Low layer compatibility information elements to the terminal equipment. The terminal equipment should in this case use compatibility checking only with Addressing Information and Bearer Capability. When the High layer and/or Low layer information elements are sent to the terminal equipment, the terminal equipment shall use them in the compatibility checking. Annex C Transit network selection Not applicable.

Annex D Extensions for Not applicable. symmetric call operation Annex E Network specific facility Not applicable. selection Annex F D-channel backup Not applicable. procedures Annex J Low layer compatibility The transport of LLC to the calling user is only supported on the ISDN negotiation end-to-end connections. Annex I Definition of causes Applicable after taking into account the national selections values (concerning cause values, messages etc.) made in this guideline document.

25 MCMC MTSFB TC T008:2014

4. Terminal Characteristics Related to Access Signaling

Terminal characteristics related to access signaling and used for type approval purposes are contained in standards ETS 300 085(12/90), ETS 300 087 (4/94), ETS 300 104 (6/94), NET 003 (9/95), NET 005 (9/95), I-ETS 300 245-1 (2/96), TBR 003 (11/95), TBR 003/A1 (2/98), TBR 004 (11/95), TBR 004/A1 (2/98), TBR 008(9/94), TBR 008(10/98), TBR 008/C2 (2/2001) and the corresponding CTRs.

5. Terminal Adaptors

5.1 Circuit Mode Bearer Services

Terminal adaptor functions and associated access signaling requirements for circuit mode bearer services are contained in the standard ETS 300 103 (12/90).

26 MCMC MTSFB TC T008:2014

Section E

Digital Transmission System on Metallic Local Lines for ISDN Basic Rate Access (ITU-T Recommendation G.961 03/1993)

Table 14. Digital transmission system on metallic local lines for ISDN basic rate access

ITU-T ETSI ETR Title Rec. 080 CR Remarks G.961 General 1 1 to 3 GID Functions 2 4 M Bit timing shall be derived from the clock received by the NT1 from LT. 8 kHz octet timing is derived from frame alignment. Remote power feeding is supported. Transmission Medium 3 5 GID The transmission medium is the local line distribution network. System Performance 4 6 GID Transmission method 5 7 M Duplex transmission on 2-wire metallic local lines shall be achieved through the use of Echo Cancellation (ECH). Activation / Deactivation 6 8 – Heading General 6.1 8.1 GID Physical representation of signals 6.2 8.2 M The signals used in the DTS are in accordance with the requirements for a system using 2B1Q line code as given in Appendix II/ G.961. Operation and Maintenance 7 9 – Heading Operation and maintenance functions 7.1 9.1 GID

CL channel 7.2 9.2 M Power Feeding 8 10 – Heading General 8.1 10.1 GID Power feeding options 8.2 10.2 M Power feeding of NT1 (to TE) under normal conditions will be provided by the AC mains power. O A restricted condition will be entered into when AC mains power at the NT1 fails. Power feeding and recovery methods 8.3 – GID DLL resistance 8.4 10.3 GID Wetting current 8.5 10.4 O The NT1 shall sink a current of at least 200µA in its operating voltage range.

27 MCMC MTSFB TC T008:2014

Table 14. Digital transmission system on metallic local lines for ISDN basic rate access (continued)

ITU-T ETSI ETR Title Rec. 080 CR Remarks G.961 LT aspects 8.6 10.5 M The NT1 shall be able to work with DC input voltages of  95 V coming from the DLL. Power requirements of NT1 and 8.7 10.6 – Heading regenerator Power requirements of NT1 8.7.1 10.6.1 M Power requirements of regenerator 8.7.2 10.6.2 NA Current transient limitation 8.8 10.7 M < 1 mA/µs Environmental Conditions 9 11 GID

Table 15. Core requirements for a system using 2B1Q line code (ITU-T Rec. Q.961 Appendix II)

ITU-T ETSI ETR Title Rec. 080 CR Remarks G.961 Line code II.1 A.1 M The line code shall be 2B1Q (2 binary, 1 quaternary). Line baud rate II.2 A.2 M The line symbol rate is 80 kbauds. Clock tolerance II.2.1 – Heading NT1 clock tolerance II.2.1.1 A.2.1 M ±100 ppm NT1 shall operate with the received signal baud rate in the range of 80 kbaud ±5 ppm. LT clock tolerance II.2.1.2 A.2.2 GID ±5 ppm REG clock tolerance – A.2.3 GID Frame structure II.3 A.3 M Figure II.2/G.961 Frame length II.3.1 A.3.1 M 120 quaternary Bit allocation in direction LT-NT1 II.3.2 A.3.2 M Figures II.1/G.961 and II.2/G.961 Bit allocation in direction NT1-LT II.3.3 A.3.3 M Figures II.1/G.961 and II.2/G.961 Frame word II.4 A.4 M Frame alignment procedure II.5 A.5 M The time limits specified in II.10 shall be met. Multiframe II.6 A.6 M A multiframe is used to enable the allocation of the CL-channel bits over more than one frame.

28 MCMC MTSFB TC T008:2014

Table 15. Core requirements for a system using 2B1Q line code (ITU-T Rec. Q.961 Appendix II) (continued)

Title ITU-T ETSI ETR CR Remarks Rec. 080 G.961

CL-channel II.8 A.8 M The bit rate for the CL-channel is 4 kbit/s. Bit rate II.8.1 A.8.1 M Structure II.8.2 A.8.2 M Figure II.3/G.961 Protocol and procedures II.8.3 A.8.3 M Figure II.3/G.961 Error monitoring functions II.8.3.1 A.8.3.1 M

Other CL- channel functions II.8.3.2 A.8.3.2 M Far end block error (FEBE) bit. II.8.3.2.1 A.8.3.2.1 M mandatory The ACT bit, mandatory II.8.3.2.2 A.8.3.2.2 M The DEA bit, mandatory II.8.3.2.3 A.8.3.2.3 M NT1 power status bits II.8.3.2.4 A.8.3.2.4 O NT1 test mode indicator (NTM) bit II.8.3.2.5 A.8.3.2.5 O Cold-start-only (CSO) bit II.8.3.2.6 A.8.3.2.6 O DLL-only-activation (UOA) bit II.8.3.2.7 A.8.3.2.7 O S/T-interface-activity-indicator (SAI) II.8.3.2.8 A.8.3.2.8 O bit Alarm indicator bit (AIB) II.8.3.2.9 A.8.3.2.9 O Network indicator bit (NIB) for II.8.3.2.10 A.8.3.2.10 M The NT1 shall always set this bit to network use binary ONE in SN3. Reserved bits II.8.3.2.11 A.8.3.2.11 M Embedded operations channel II.8.3.3 A.8.3.3 M (EOC) functions Scrambling II.9 A.9 M Start-up and control II.10 A.10 Note M The NT1 shall be able to support both cold-start and warm-start. Signals used for start-up and control II.10.1 A.10.1 M Timers II.10.2 A.10.2 M Description of the start-up procedure II.10.3 A.10.3 M Heading State transition table for the NT1 II.10.4 A.10.4 M State transition table for the LT II.10.5 A.10.5 GID Activation times II.10.6 A.10.6 M

29 MCMC MTSFB TC T008:2014

Table 15. Core requirements for a system using 2B1Q line code (ITU-T Rec. Q.961 Appendix II) (continued)

ITU-T ETSI ETR Rec. Title 080 CR Remarks G.961 Jitter II.11 A.11 M Input signal jitter tolerance II.11.1 A.11.1 M Figure II.10/G.961 NT1 output jitter limitations II.11.2 A.11.2 M LT input signal jitter tolerance II.11.3 A.11.3 GID LT output jitter and synchronisation II.11.4 A.11.4 GID Test conditions for jitter measurement II.11.5 A.11.5 GID Transmitter output characteristics of II.12 A.12 M Load impedance of 135 ohms NT1 and LT resistive over a frequency band of 0 Hz to 160 kHz Pulse amplitude II.12.1 A.12.1 M 2.5 V (Figure II.11/G.961) Pulse shape II.12.2 A.12.2 M The transmitted pulse shall have the shape specified in Figure II.11/G.961. The pulse mask for the four quaternary symbols shall be obtained by multiplying the normalized pulse mask shown in Figure II.11 by 2.5 V, 5/6 V, –5/6 V or –2.5 V. Signal power II.12.3 A.12.3 M Between 13.0 dBm and 14.0 dBm over the frequency band from 0 Hz to 80 kHz Power spectral density II.12.4 A.12.4 M Figure II.12/G.961 Transmitter linearity II.12.5 A.12.5 M Transmitter/receiver termination II.13 A.13 – Heading Impedance II.13.1 A.13.1 M 135  Return loss II.13.2 A.13.2 M Figure II.14/G.961 Longitudinal conversion loss II.13.3 A.13.3 M Figure II.15/G.961

NOTE: The use of cold-start-only transceivers is outside the scope of ETR 080.

30 MCMC MTSFB TC T008:2014

Table 16. Extension functions of the system using 2B1Q line code (Annex A to ITU-T Rec. Q.961 Appendix II)

ITU-T ETSI ETR Title Rec. 080 CR Remarks G.961 Introduction A.II.1 I-1 GID NT1 power status bits A.II.2 I-2 O NT1 test mode indicator (NTM) bit A.II.3 I-3 O Cold-start-only (CSO) bit A.II.4 I-4 O DLL-only -activation (UOA) bit A.II.5 I-5 O S/T-interface-activity-indicator (SAI) A.II.6 I-6 O bit Alarm indicator bit (AIB) A.II.7 I-7 O Longitudinal output voltage A.II.8 – GID NT1 maintenance modes A.II.9 – O NT1 Quiet Mode A.II.9.1 – O Insertion Loss Measurement Test A.II.9.2 – O NT1 Quiet Mode and Insertion Loss A.II.9.3 – O Measurement Test trigger signal Dc signaling format A.II.9.4 – O Low frequency ac signaling format A.II.9.5 – O

31 MCMC MTSFB TC T008:2014

Annex A (Normative)

Normative References

Erratum1 (02/2003) to ITU-T ISDN User-Network Interface Layer 3 Specification for Basic Call Rec. Q.931 Control

ETR 080 Nov 96 Digital transmission system on metallic local lines

ETSI TBR 3 Nov 95 Attachment requirements for terminal equipment to connect to an ISDN using ISDN basic access

ETSI TBR 3 A1 Dec 97 This amendment A1 modifies the TBR 3 (1995)

IEC 60950-1: 2001 Information Technology Equipment – Safety

IEC CISPR 22: 2003-04 Information Technology Equipment – Radio disturbance characteristics – Limits and methods of measurement

ITU-T Rec. I.430 (11/95) Basic User-Network Interface – Layer 1 Specification

ITU-T Rec. Q.921 (09/97) ISDN User-Network Interface – Data Link Layer Specification

ITU-T Rec. Q.921 ISDN User-Network Interface – Data Link Layer Specification Amendment 1 (02/2000) Amendment 1

[ITU-T Recommendation Integrated Services Digital Network (ISDN): Digital Subscriber Q.931 (1993), modified] (EN Signaling System No. One (DSS1) protocol: Signaling network layer 300 403-1 11/99) for circuit-mode basic call control; Part 1: Protocol Specification

ITU-T Rec. Q.931 ISDN User-Network Interface Layer 3 Specification for Basic Amendment 1 (05/98) Call Control Amendment 1 Extensions for the support of digital multiplexing equipment

ITU-T Rec. G.961 03/93 Digital Transmission System on Metallic Local Lines for ISDN Basic Rate Access

NOTES:

ETSI European Telecommunications Standards Institute ETR ETSI Technical Report IEC International Electro-technical Commission ITU-T International Telecommunication Union – Telecommunication Sector TBR Technical Basis for Regulation

32 MCMC MTSFB TC T008:2014

Annex B (Informative)

TECHNICAL GUIDELINES OF ISDN SUPPLEMENTARY SERVICE

B1 Introduction

This section contains clarifications and recommended option selections for the ETSI ISDN standards related to ISDN supplementary services. This document covers the implementation of ISDN supplementary services using functional protocol. The aim of this document is to avoid unnecessary options and vagueness in ISDN implementations and to ensure the interoperability of ISDN networks and terminal equipment in Malaysia.

B2 Supporting Information

B2.1 Integrated Services Digital Network (ISDN); Multiple Subscriber Number (MSN) supplementary service; Service Description (ETS 300 050, October 1991)

B2.2 Integrated Services Digital Network (ISDN); Multiple Subscriber Number (MSN) supplementary service; Functional capabilities and information flows (ETS 300 051, October 1991)

B2.3 Integrated Services Digital Network (ISDN); Multiple Subscriber Number (MSN) supplementary service; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 052-1, October 1991)

B2.4 Integrated Services Digital Network (ISDN); Terminal Portability (TP) supplementary service; Service Description (ETS 300 053, October 1991)

B2.5 Integrated Services Digital Network (ISDN); Terminal Portability (TP) supplementary service; Functional capabilities and information flows (ETS 300 054, October 1991)

B2.6 Integrated Services Digital Network (ISDN); Terminal Portability (TP) supplementary service; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 055-1, October 1991)

B2.7 Integrated Service Digital Network (ISDN); Call Waiting (CW) supplementary service; Service Description (ETS 300 056, October 1991) and Amendment A1 (September 1996)

B2.8 Integrated Services Digital Network (ISDN); Call Waiting (CW) supplementary service; Functional capabilities and information flows (ETS 300 057, May 1992)

B2.9 Integrated Services Digital Network (ISDN); Call Waiting (CW) supplementary service; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 058-1, October 1991)

B2.10 Integrated Services Digital Network (ISDN); Sub-addressing (SUB) supplementary service; Service Description (ETS 300 059, October 1991)

B2.11 Integrated Services Digital Network (ISDN); Sub-addressing (SUB) supplementary service; Functional capabilities and information flows (ETS 300 060, October 1991)

33 MCMC MTSFB TC T008:2014

B2.12 Integrated Services Digital Network (ISDN); Sub-addressing (SUB) supplementary service; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 061-1, October 1991)

B2.13 Integrated Services Digital Network (ISDN); Direct Dialing In (DDI) supplementary service; Service Description (ETS 300 062, October 1991)

B2.14 Integrated Services Digital Network (ISDN); Direct Dialling In (DDI) supplementary service; Functional capabilities and information flows (ETS 300 063, October 1991)

B2.15 Integrated Services Digital Network (ISDN); Direct Dialing In (DDI) supplementary service; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 064-1, October 1991)

B2.16 Integrated Services Digital Network (ISDN); Calling Line Identification Presentation (CLIP) supplementary service; Service description (ETS 300 089, January 1992)

B2.17 Integrated Services Digital Network (ISDN); Calling Line Identification Restriction (CLIR) supplementary service; Service description (ETS 300 090, January 1992)

B2.18 Integrated Services Digital Network (ISDN); Calling Line Identification Presentation (CLIP) and Calling Line Identification Restriction (CLIR) supplementary services; Functional capabilities and information flows (ETS 300 091, March 1992)

B2.19 Integrated Services Digital Network (ISDN); Calling Line Identification Presentation (CLIP) supplementary service; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 092-1, March 1992), Amendment A1 (April 1993) and Amendment A2 (November 1994)

B2.20 Integrated Services Digital Network (ISDN); Calling Line Identification Restriction (CLIR) supplementary service; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 093-1, March 1992)

B2.21 Integrated Services Digital Network (ISDN); Connected Line Identification Presentation (COLP) supplementary service; Service description (ETS 300 094, January 1992)

B2.22 Integrated Services Digital Network (ISDN); Connected Line Identification Restriction (COLR) supplementary service; Service description (ETS 300 095, January 1992)

B2.23 Integrated Services Digital Network (ISDN); Connected Line Identification Presentation (COLP) and Connected Line Identification Restriction (COLR) supplementary services; Functional capabilities and information flows (ETS 300 096, May 1992)

B2.24 Integrated Services Digital Network (ISDN); Connected Line Identification Presentation (COLP) supplementary service; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 097-1, March 1992) and Amendment A1 (November 1994)

B2.25 Integrated Services Digital Network (ISDN); Connected Line Identification Restriction (COLR) supplementary service; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 098-1, May 1992)

B2.26 Integrated Services Digital Network (ISDN); Malicious Call Identification (MCID) supplementary service; Service description (ETS 300 128, May 1992)

B2.27 Integrated Services Digital Network (ISDN); Malicious Call Identification (MCID) supplementary service; Functional capabilities and information flows (ETS 300 129, May 1992)

34 MCMC MTSFB TC T008:2014

B2.28 Integrated Services Digital Network (ISDN); Malicious Call Identification (MCID) supplementary service; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 130-1, May 1992)

B2.29 Integrated Services Digital Network (ISDN); Closed User Group (CUG) supplementary service; Service description (ETS 300 136, March 1992)

B2.30 Integrated Services Digital Network (ISDN); Closed User Group (CUG) supplementary service; Functional capabilities and information flows (ETS 300 137, May 1992)

B2.31 Integrated Services Digital Network (ISDN); Closed User Group (CUG) supplementary service; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 138-1, May 1992) and Amendment A1 (January 1996)

B2.32 Integrated Services Digital Network (ISDN); Call Hold (HOLD) supplementary service; Service description (ETS 300 139, March 1992)

B2.33 Integrated Services Digital Network (ISDN); Call Hold (HOLD) supplementary service; Functional capabilities and information flows (ETS 300 140, May 1992)

B2.34 Integrated Services Digital Network (ISDN); Call Hold (HOLD) supplementary service; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 141- 1, May 1992) including Corrigendum (August 1993)

B2.35 Integrated Services Digital Network (ISDN); Advice of Charge: charging information at call set- up time (AOC-S) supplementary service; Service description (ETS 300 178, October 1992)

B2.36 Integrated Services Digital Network (ISDN); Advice of Charge: charging information during the call (AOC-D) supplementary service; Service description (ETS 300 179, October 1992)

B2.37 Integrated Services Digital Network (ISDN); Advice of Charge: charging information at the end of the call (AOC-E) supplementary service; Service description (ETS 300 180, October 1992)

B2.38 Integrated Services Digital Network (ISDN); Advice of Charge (AOC) supplementary service; Functional capabilities and information flows (ETS 300 181, April 1993)

B2.39 Integrated Services Digital Network (ISDN); Advice of Charge (AOC) supplementary service; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 182-1, April 1993)

B2.40 Integrated Services Digital Network (ISDN); Three-Party (3PTY) supplementary service; Service description (ETS 300 186, July 1993)

B2.41 Integrated Services Digital Network (ISDN); Three-Party (3PTY) supplementary service; Functional capabilities and information flows (ETS 300 187, August 1993)

B2.42 Integrated Services Digital Network (ISDN); Three-Party (3PTY) supplementary service; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 188-1, August 1993)

B2.43 Integrated Services Digital Network (ISDN); Supplementary Service Interactions; Digital Subscriber Signaling System No. one (DSS1) protocol, Part 1: Protocol specification (ETS 300 195- 1, February 1995)

35 MCMC MTSFB TC T008:2014

B2.44 Integrated Services Digital Network (ISDN); Generic functional protocol for the support of supplementary services; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 196-1, August 1993) and Amendment A1 (May 1995)

B2.45 Integrated Services Digital Network (ISDN); Call Forwarding Busy (CFB) supplementary service; Service description (ETS 300 199, December 1994)

B2.46 Integrated Services Digital Network (ISDN); Call Forwarding Unconditional (CFU) supplementary service; Service description (ETS 300 200, December 1994)

B2.47 Integrated Services Digital Network (ISDN); Call Forwarding No Reply (CFNR) supplementary service; Service description (ETS 300 201, December 1994) and Amendment A1 (September 1996)

B2.48 Integrated Services Digital Network (ISDN); Call Forwarding Busy (CFB) supplementary service; Functional capabilities and information flows (ETS 300 203, December 1994)

B2.49 Integrated Services Digital Network (ISDN); Call Forwarding Unconditional (CFU) supplementary service; Functional capabilities and information flows (ETS 300 204, December 1994)

B2.50 Integrated Services Digital Network (ISDN); Call Forwarding No Reply (CFNR) supplementary service; Functional capabilities and information flows (ETS 300 205, December 1994)

B2.51 Integrated Services Digital Network (ISDN); Diversion supplementary services; Digital Subscriber Signaling No. one (DSS1) protocol (ETS 300 207-1, December 1994) and Corrigendum (June 1995)

B2.52 Integrated Services Digital Network (ISDN); User-to-user signaling (UUS) supplementary service; Service description (ETS 300 284, March 1996)

B2.53 Integrated Services Digital Network (ISDN); User-to-user signaling (UUS) supplementary service; Functional capabilities and information flows (ETR 285, March 1996)

B2.54 Integrated Services Digital Network (ISDN); User-to-user signaling (UUS) supplementary service; Digital Subscriber Signaling one (DSS1) protocol (ETS 300 286-1, February 1993)

B2.55 Integrated Services Digital Network (ISDN); Explicit Call Transfer (ECT) supplementary service; Service description (EN 300 367, V1.2.1, October 1998)

B2.56 Integrated Services Digital Network (ISDN); Explicit Call Transfer (ECT) supplementary service; Functional capabilities and information flows (EN 300 368, V1.2.2, December 1998)

B2.57 Integrated Services Digital Network (ISDN); Explicit Call Transfer (ECT) supplementary service; Digital Subscriber Signaling one (DSS1) protocol (EN 300 369-1, V1.2.4, October 1998)

36 MCMC MTSFB TC T008:2014

B3. National Option Selections and Clarifications

B3.1 Generic functional protocol for the support of supplementary services

The supplementary services of this specification are based on the functional protocol. Therefore, the public network shall support the generic part of the functional protocol according to ETS 300 196-1 [44].

Only those functions need to be implemented, which are required to support the selected supplementary services. Network options of ETS 300 196-1 are left as implementation options, unless stated otherwise in the Sub clauses relating to the individual supplementary services. Should any conflict arise between ETS 300 196-1 and the specifications in Sub clause 3.2 to 3.16, then the text of the individual supplementary services shall be taken as definitive.

B3.2 Multiple Subscriber Number (MSN)

B3.2.1 Definition

The Multiple Subscriber Number (MSN) supplementary service provides the possibility for assigning multiple numbers to a single public or private access.

NOTE: This allows e.g.:

1) A calling user to select, via the public network, one or multiple distinct terminals out of multiple choices; 2) To identify the terminal to the network for the application of other supplementary services.

B3.2.2 Service Description

The service description (stage 1 description) for the MSN supplementary service is contained in the standard ETS 300 050 [1].

The following gives the recommended guidelines for the implementation of the MSN supplementary service in the Malaysian network.

Clause 5 and sub clause 6.2.3 The multiple subscriber number provided by the calling party shall be the full ISDN subscriber number.

The called party number to be transmitted to the user's installation shall comprise the full ISDN subscriber number Sub clause 6.1 The maximum number of MSNs per access shall be 16 Sub clause 7.2 The MSN supplementary service can apply at an access to a private ISDN (e.g. when the public network does not know what equipment is connected to the access). Clause 8 Supplementary services can be individually assigned to each MSN number. Sub clause 8.9 Subscription to the DDI supplementary service and the MSN supplementary service is mutually exclusive.

37 MCMC MTSFB TC T008:2014

Additional requirement

On outgoing calls, when the screening of the calling party number is successful, the CLI to be recorded in the charging record shall be the MSN number provided by the calling party. If the number screening is unsuccessful, the default ISDN number of the access shall be recorded in the charging record.

B3.2.3 Functional Capabilities and Information Flows

The functional capabilities and information flows (stage 2 description) for the MSN supplementary service are contained in the standard ETS 300 051 [2]. The stage 2 description can be taken as informative. The implementation of the MSN supplementary service in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

B3.2.4 Digital Subscriber Signaling System No. One (DSS1) Protocol

The DSS1 protocol (stage 3 description) for the MSN supplementary service is contained in the standard ETS 300 052-1 [3].

The following gives the recommended guidelines for the implementation of the MSN supplementary service in the Malaysian network.

Sub clause 6.2 If the access has the MSN supplementary service, the network may use the information in the calling party number information element to identify the calling terminal, and, if necessary, the appropriate basic or supplementary service. Sub clause 9.2.1 The type of number indicated in the Called party number information element sent to the user shall be coded as "subscriber number" and the full appropriate number shall be sent.

The "numbering plan identification" field of the Called party number information element shall be coded "ISDN/telephony numbering plan" (ITU-T Recommendation E.164). Sub clause 9.3.1 All the coding options provided in this sub clause shall be implemented in the network.

It is recommended that the type of number indicated in the Calling party number information element sent to the network shall be coded as "subscriber number" and the full appropriate number shall be sent.

B3.3 Terminal Portability (TP)

B3.3.1 Definition

The Terminal Portability (TP) supplementary service allows a user to move a terminal from one socket to another within one given basic access during the active state of a call. It also allows a user to move a call from one terminal to another terminal within one given basic access during the active phase of the call.

38 MCMC MTSFB TC T008:2014

B3.3.2 Service Description

The service description (stage 1 description) for the TP supplementary service is contained in the standard ETS 300 053 [4].

The following gives the recommended guidelines for the implementation of the TP supplementary service in the Malaysian network.

Sub clause 8.1.2 At call suspension request, the cumulative information (i.e. total charge incurred up to the moment when the call is suspended) shall be given.

On resumption of the call, the sending of charging information shall start again and the updated cumulative charging information shall be given.

If the call is cleared while the call is suspended at the calling user's access, and if the calling user attempts to resume the call within the timer, then, advice of charge information shall be given to the user at the time of the resume attempt. Sub clause 8.1.3 If the call is cleared while the call is suspended at the calling user's access, and if the calling user attempts to resume the call within the timer, then advice of charge information can be given to the user at the time of the resume attempt

B3.3.3 Functional Capabilities and Information Flows

The functional capabilities and information flows (stage 2 description) for the TP supplementary service are contained in the standard ETS 300 054 [5]. The stage 2 description can be taken as informative. The implementation of the TP supplementary service in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

B3.3.4 Digital Subscriber Signaling System No. One (DSS1) Protocol

The DSS1 protocol (stage 3 description) for the TP supplementary service is contained in the standard ETS 300 055-1 [6]. The TP supplementary service is implemented in the Malaysian network without national definitions or exceptions.

B3.4 Call Waiting (CW)

B3.4.1 Definition

The Call Waiting (CW) supplementary service allows a user to be informed of an incoming call (as per basic call procedures) with an indication that no interface information channel is available. The user then has the choice of accepting, rejecting or ignoring the waiting call (as per basic call procedures).

39 MCMC MTSFB TC T008:2014

B3.4.2 Service Description

The service description (stage 1 description) for the CW supplementary service is contained in the standard ETS 300 056 [7].

The following gives the recommended guidelines for the implementation of the CW supplementary service in the Malaysian network.

Clause 3 and sub clause 6.1 No specific time-out T2 will be used for no answer situation. Basic call timer shall apply in this case. Clause 5 On the primary rate access, only notifications for the CW supplementary service are supported.

The maximum number of calls that the network must be able to handle (e.g. active, held, alerting, waiting) on the basic access is six (6). Sub clause 6.1 The network will support the subscription option presented in Table 1.

The network will support value two (2) for the network provider option in Table 2. This is specified for all ISDN numbers on the basic access Sub clause 7.1 In interworking cases with non-ISDNs, no special in-band indication will be provided to the calling user.

B3.4.3 Functional Capabilities and Information Flows

The functional capabilities and information flows (stage 2 description) for the CW supplementary service are contained in the standard ETS 300 057 [8]. The stage 2 description can be taken as informative. The implementation of the CW supplementary service in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

B3.4.4 Digital Subscriber Signaling System No. One (DSS1) Protocol

The DSS1 protocol (stage 3 description) for the CW supplementary service is contained in the standard ETS 300 058-1 [9].

The following gives the recommended guidelines for the implementation of the CW supplementary service in the Malaysian network.

Sub clauses 9.5.1.1, 9.5.2, 9.6.1 and 9.6.2, and In the network side the basic call timer T301 is clauses 13 and 14 used

40 MCMC MTSFB TC T008:2014

B3.5 Sub addressing (SUB)

B3.5.1 Definition

The Sub addressing (SUB) supplementary service allows the called (served) user to expand his addressing capacity beyond the one given by the ISDN number.

B3.5.2 Service Description

The service description (stage 1 description) for the SUB supplementary service is contained in the standard ETS 300 059 [10].

The following gives the recommended guidelines for the implementation of the SUB supplementary service in the Malaysian network.

Sub clause 5.1 The 20 octets maximum size of is applied

B3.5.3 Functional Capabilities and Information Flows

The functional capabilities and information flows (stage 2 description) for the SUB supplementary service are contained in the standard ETS 300 060 [11]. The stage 2 description can be taken as informative. The implementation of the SUB supplementary service in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

B3.5.4 Digital Subscriber Signaling System No. One (DSS1) Protocol

The DSS1 protocol (stage 3 description) for the SUB supplementary service is contained in the standard ETS 300 061-1 [12].

The following gives the recommended guidelines for the implementation of the SUB supplementary service in the Malaysian network.

Clause 5, note 2 The 20 octets maximum size of the sub address is applied.

B3.6 Direct Dialing In (DDI)

B3.6.1 Definition

The DDI supplementary service enables a user to call directly via a public ISDN a user on a private ISDN by using the public ISDN numbering plan.

41 MCMC MTSFB TC T008:2014

B3.6.2 Service Description

The service description (stage 1 description) for the DDI supplementary service is contained in the standard ETS 300 062 [13].

The following gives the recommended guidelines for the implementation of the DDI supplementary service in Malaysian network.

Clause 5 The number of digits is defined on a per subscriber basis Sub clauses 8.5.1 and 8.5.3 A special arrangement for not screening the user provided number may be applied. For network wide operation ISUP version 2 is required Sub clause 8.12 If the DDI supplementary service is provided to the served user of the MCID supplementary service, then the MCID supplementary service shall be provided globally for the whole access. The network option on provision for specific ISDN numbers forming part of the DDI supplementary service is not supported. Sub clause 8.13 The subscription to the DDI supplementary service and the Multiple Subscriber Number (MSN) supplementary service is mutually exclusive

B3.6.3 Functional Capabilities and Information Flows

The functional capabilities and information flows (stage 2 description) for the DDI supplementary service are contained in the standard ETS 300 063 [14]. The stage 2 description can be taken as informative. The implementation of the DDI supplementary service in Malaysian network shall be based on the stage 1 and stage 3 descriptions.

B3.6.4 Digital Subscriber Signaling System No. One (DSS1) Protocol

The DSS1 protocol (stage 3 description) for the DDI supplementary service is contained in the standard ETS 300 064-1 [15].

The following gives the recommended guidelines for the implementation of the DDI supplementary service in Malaysian network.

Sub clause 6.1, note The subscription to the DDI supplementary service and the Multiple Subscriber Number (MSN) supplementary service is mutually exclusive.

B3.7 Calling Line Identification Presentation (CLIP) and Calling Line Identification Restriction (CLIR)

B3.7.1 Definition

The CLIP supplementary service provides the called party with the possibility of receiving identification of the calling party.

The CLIR supplementary service enables the calling party to prevent presentation of its ISDN number to the called party.

42 MCMC MTSFB TC T008:2014

B3.7.2 Service Description

CLIP:

The service description (stage 1 description) for the CLIP supplementary service is contained in the standard ETS 300 089 [16].

The following gives the recommended guidelines for the implementation of the CLIP supplementary service in Malaysian network.

Sub clauses 6.1, 6.2.3.1, 7.2, 8.9 In case of two calling party number delivery option a special and 8.13 arrangement for not screening the user provided number may be applied. For network wide operation ISUP version 2 is required. Sub clause 7.1 The CLIP supplementary service is always applicable when interworking to non-ISDN has occurred.

The calling line identity can be provided to called user in the ISDN if the identity has been received and it is known that presentation is not restricted.

On calls to or via non-ISDN, the originating network may restrict calling line identity from being forwarded to the destination network when the CLIR supplementary service is applicable (see also ETS 300 090, sub clause 7.1). Sub clause 8.5.2 Technical capabilities to provide override category service have to be available in Malaysian network Annex A The two calling party number delivery option is applicable. For network wide operation ISUP version 2 is required.

CLIR:

The service description (stage 1 description) for the CLIR supplementary service is contained in the standard ETS 300 090 [17].

The following gives the recommended guidelines for the implementation of the CLIR supplementary service in the Malaysian network.

Clause 3, and sub clauses 6.2.3.2 Technical capabilities to provide override category service have (note 1) and 8.5.1 to be available in the Malaysian network Sub clause 6.1 Both subscription options, permanent mode and temporary mode (defaults: presentation restricted and presentation not restricted), are offered Sub clause 7.1 On calls to or via non-ISDNs, it cannot be assured that a restriction indication can be carried to the destination network. The originating network in Malaysia may restrict any information identifying the calling user from being forwarded to the destination network when the CLIR supplementary service is applicable

43 MCMC MTSFB TC T008:2014

B3.7.3 Functional Capabilities and Information Flows

The functional capabilities and information flows (stage 2 description) for the CLIP and CLIR supplementary services are contained in the standard ETS 300 091 [18]. The stage 2 description can be taken as informative. The implementation of the CLIP and CLIR supplementary services in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

B3.7.4 Digital Subscriber Signaling System No. One (DSS1) Protocol

CLIP:

The DSS1 protocol (stage 3 description) for the CLIP supplementary service is contained in the standard ETS 300 092-1 [19].

The following gives the recommended guidelines for the implementation of the CLIP supplementary service in the Malaysian network.

Sub clauses 6.2 and 9.4 In case of two calling party number delivery option a special arrangement for not screening the user provided number may be applied. For networkwide operation ISUP version 2 is required. Sub clause 9.2.1 It is recommended for the coding of the calling party information element sent by the calling user:

-The "numbering plan identification" field shall be coded "ISDN/Telephony numbering plan".

In case DDI is not activated for the same access:

- The "type of number" field shall be coded "subscriber number" and the full ISDN subscriber number shall be sent.

In case DDI is activated for the same access:

- The "type of number" field shall be coded "unknown" and only the extension number of the calling party shall be sent. The network then completes the calling party number by adding the national number of the access to the calling party number information element. Sub clause 9.3.1 Networks in Malaysia may accept a full ISDN number in a Calling party number information element with the addition of a prefix or escape digits to the number digits field and the type of number field set to "National Number Sub clause 9.5.1 and The coding of the calling party information element sent by the destination Table 1, note 7 local exchange:

- The "numbering plan identification" field shall be coded "ISDN/Telephony numbering plan";

- The "type of number" field shall be coded "unknown", and the number is organized according to the network dialing plan.

44 MCMC MTSFB TC T008:2014

Clause 11 The following option is according to the network rules and operations in Malaysia:

- The network shall send the Calling party number information element according to sub clause 9.5.1, fifth paragraph and shall include no Calling party sub address information element.

Annex B The two Calling party number information elements delivery option is applicable. For network wide operation ISUP version 2 is required

CLIR:

The DSS1 protocol (stage 3 description) for the CLIR supplementary service is contained in the standard ETS 300 093-1 [20]. The following gives the recommended guidelines for the implementation of the CLIR supplementary service in the Malaysian network.

Clause 11 On calls to or via non-ISDNs, the originating network may restrict calling line identity from being forwarded to the destination network when the CLIR supplementary service is applicable.

B3.8 Connected Line Identification Presentation (COLP) and Connected Line Identification Restriction (COLR)

B3.8.1 Definition

The COLP supplementary service provides the calling party with the possibility to receive identification of the connected party.

The COLR supplementary service enables the connected party to prevent presentation of its ISDN number to the calling party.

B3.8.2 Service Description

COLP:

The service description (stage 1 description) for the COLP supplementary service is contained in the standard ETS 300 094 [21].

The following gives the recommended guidelines for the implementation of the COLP supplementary service in the Malaysian network.

Sub clauses 6.1, 6.2.3.1, 7.2, 8.9 A special arrangement for not screening the user provided number and 8.13 may be applied. For networkwide operation ISUP version 2 is required. Sub clause 7.1 The use of the COLP supplementary service can be guaranteed only when the call is end-to end ISDN. Sub clauses 8.5.4 and 8.10 Technical capabilities to provide override category service have to be available in the Malaysian network

45 MCMC MTSFB TC T008:2014

COLR:

The service description (stage 1 description) for the COLR supplementary service is contained in the standard ETS 300 095 [22].

The following gives the recommended guidelines for the implementation of the COLR supplementary service in the Malaysian network.

Clause 3, and sub clauses Technical capabilities to provide override category service have to 6.2.3.2,8.5.3 and 8.10 be available in the Malaysian network Sub clause 6.1 Both subscription options, permanent mode and temporary mode (defaults: presentation restricted and presentation not restricted), are offered. Sub clause 7.1 Destination network in Malaysia may restrict any information identifying the connected party from being returned to the originating network when the COLR supplementary service has been invoked

B3.8.3 Functional Capabilities and Information Flows

The functional capabilities and information flows (stage 2 description) for the COLP and COLR supplementary services are contained in the standard ETS 300 096 [23]. The stage 2 description can be taken as informative. The implementation of the COLP and COLR supplementary services in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

B3.8. Digital Subscriber Signaling System No. One (DSS1) Protocol

COLP:

The DSS1 protocol (stage 3 description) for the COLP supplementary service is contained in the standard ETS 300 097-1 [24].

The following gives the recommended guidelines for the implementation of the COLP supplementary service in the Malaysian network.

Sub clauses 6.3 and 9.4 A special arrangement for not screening the user provided number may be applied. For network wide operation ISUP version 2 is required Sub clause 9.2.1 It is recommended for the coding of the connected party information element sent by the connected user:

- The "numbering plan identification" field shall be coded "ISDN/Telephony numbering plan";

- The "type of number" field shall be coded "subscriber number" and the full ISDN subscriber number shall be sent. Sub clause 9.3.1 Networks in Malaysia may accept a full ISDN number in a Connected party number information element with the addition of a prefix or escape digits to the number digits field and the type of number field set to "National Number

46 MCMC MTSFB TC T008:2014

Sub clause 9.5.1 and Table 1, The coding of the connected party information element sent by the note 7 originating local exchange: - The "numbering plan identification" field shall be coded "ISDN/Telephony numbering plan"; - The "type of number" field shall be coded "unknown", and the number is organized according to the network dialing plan

COLR:

The DSS1 protocol (stage 3 description) for the COLR supplementary service is contained in the standard ETS 300 098-1 [25].

The following gives the recommended guidelines for the implementation of the COLR supplementary service in the Malaysian network.

Clause 11 Destination network in Malaysia may restrict any information identifying the connected party from being returned to the originating network when the COLR supplementary service has been invoked

B3.9 Malicious Call Identification (MCID)

B3.9.1 Definition

The MCID supplementary service enables a user to request that the source of an incoming call is identified and registered by the network.

B3.9.2 Service Description

The service description (stage 1 description) for the MCID supplementary service is contained in the standard ETS 300 128 [26].

The following gives the recommended guidelines for the implementation of the MCID supplementary service in the Malaysian network.

Clause 5 The network will support the registration of calling party sub address. Sub clauses 5, 6.1 and 6.2.3 The network will not support the automatic invocation of the service on unanswered calls. Sub clause 6.2.3 The network will not support the continuation of the call to be presented after the calling user has cleared. Sub clause 7.1 When interworking between the PSTN and the ISDN occurs and if the number of the calling user is not available, the network will support the option of registering information about the routing of the call.

The option in the note is not supported.

47 MCMC MTSFB TC T008:2014

Sub clause 8.9 The network will not provide the service for specific ISDN numbers forming part of the DDI supplementary service Sub clauses 8.10.1, 8.10.2 The network will support the registration of the last diverting user and 8.10.3 Sub clause 8.11 The network will not support the registration of the called phone number

B3.9.3 Functional Capabilities and Information Flows

The functional capabilities and information flows (stage 2 description) for the MCID supplementary service are contained in the standard ETS 300 129 [27]. The stage 2 description can be taken as informative. The implementation of the MCID supplementary service in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

B3.9.4 Digital Subscriber Signaling System No. One (DSS1) Protocol

The DSS1 protocol (stage 3 description) for the MCID supplementary service is contained in the standard ETS 300 130-1 [28].

The following gives the recommended guidelines for the implementation of the MCID supplementary service in the Malaysian network.

Clause 3 The call information shall include the calling party sub address, if provided by the calling user

B3.10 Closed User Group (CUG)

B3.10.1 Definition

The CUG supplementary service enables users to form groups to and from which access is restricted. A specific user may be a member of one or more closed user groups. Members of a specific closed user group can communicate among themselves but not, in general, with users outside the group.

B3.10.2 Service Description

The service description (stage 1 description) for the CUG supplementary service is contained in the standard ETS 300 136 [29].

The following gives the recommended guidelines for the implementation of the CUG supplementary service in the Malaysian network.

Sub clause 6.1 The maximum number of closed user groups which can be allocated to an individual user is 75. All the subscription options defined in this Sub clause are supported

48 MCMC MTSFB TC T008:2014

B3.10.3 Functional Capabilities and Information Flows

The functional capabilities and information flows (stage 2 description) for the CUG supplementary service are contained in the standard ETS 300 137 [30]. The stage 2 description can be taken as informative. The implementation of the CUG supplementary service in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

B3.10.4 Digital Subscriber Signaling System No. One (DSS1) Protocol

The DSS1 protocol (stage 3 description) for the CUG supplementary service is contained in the standard ETS 300 138-1 [31].

The following gives the recommended guidelines for the implementation of the CUG supplementary service in the Malaysian network.

Sub clause 6.1 All the subscription options defined in this Sub clause are supported. Sub clause 9.2.4.1 b) The return error component shall be retained along with the ETS 300 403-1 cause.

B3.11 Call Hold (HOLD)

B3.11.1 Definition

The HOLD supplementary service allows a user to interrupt communications on an existing call and then subsequently, if desired, re-establish communications.

B3.11.2 Service Description

The service description (stage 1 description) for the HOLD supplementary service is contained in the standard ETS 300 139 [32].

The following gives the recommended guidelines for the implementation of the HOLD supplementary service in the Malaysian network.

Clause 5 On the primary rate access, only notifications for the HOLD supplementary service are supported. Sub clause 6.2.3.1 The network may support the option: A call can be placed on hold after the call has been offered to the called user.

The sending of notifications to the remote user is supported. Sub clause 6.2.3.2 The sending of notifications to the remote user is supported Sub clause 7.1, note If a remote user is a PSTN user, the notifications about the hold request or retrieve request of the call to that user are not supported. The last sentence of the note is not applicable

49 MCMC MTSFB TC T008:2014

B3.11.3 Functional Capabilities and Information Flows

The functional capabilities and information flows (stage 2 description) for the HOLD supplementary service are contained in the standard ETS 300 140 [33]. The stage 2 description can be taken as informative. The implementation of the HOLD supplementary service in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

B3.11.4 Digital Subscriber Signaling System No. One (DSS1) Protocol

The DSS1 protocol (stage 3 description) for the HOLD supplementary service is contained in the standard ETS 300 141-1 [34].

The following gives the recommended guidelines for the implementation of the HOLD supplementary service in the Malaysian network.

Clause 9, and Sub clauses The user A at the originating side can hold a call in the Call 9.1.1, 9.2.1 and 9.4.1 Delivered state (U4).

B3.12 Advice of Charge (AOC)

B3.12.1 Definition

Advice of Charge (AOC) is a group of supplementary services allowing the served user to be informed of usage-based charging information.

The AOC group of supplementary services includes the following:

AOC-S Advice of Charge, charging information at call set-up time; AOC-D Advice of Charge, charging information during the call; AOC-E Advice of Charge, charging information at the end of a call.

B3.12.2 Service Description

AOC-S:

The service description (stage 1 description) for the AOC-S supplementary service is contained in the standard ETS 300 178 [35].

The following gives the recommended guidelines for the implementation of the AOC-S supplementary service in the Malaysian network.

Clause 5 The AOC-S supplementary service is applicable only in relation to time tariff setting at call establishment and time tariff changes Sub clause 8.16 No charging information for the use of the Three-Party supplementary service can be sent to the served user

50 MCMC MTSFB TC T008:2014

AOC-D:

The service description (stage 1 description) for the AOC-D supplementary service is contained in the standard ETS 300 179 [36].

The following gives the recommended guidelines for the implementation of the AOC-D supplementary service in the Malaysian network.

Sub clause 6.2.3 The value of the timer t shall be 10 seconds Sub clause 8.15 The cumulative charging information is given in all the described cases: at the suspension request, on the resumption of the call, and if the call is terminated while the call is suspended at the calling user's access and the calling user attempts to resume the call within the timer. Sub clause 8.16 No charging information for the use of the Three-Party supplementary service can be sent to the served user. Annex A, Sub clause A.2.1 The Malaysian network may not include some charges, e.g. charges incurred by the use of some supplementary services, in the subtotal charges and/or the total charges Annex A, Sub clause A.3 Charging information (AOC) can be given in currency units or metering pulses according to access arrangements.

AOC-E:

The service description (stage 1 description) for the AOC-E supplementary service is contained in the standard ETS 300 180 [37].

The following gives the recommended guidelines for the implementation of the AOC-E supplementary service in the Malaysian network.

Sub clause 8.4 After a call has been transferred and the transferring user is charged for that transferred part of the call, and the AOC-E supplementary service has been invoked for that call, then the charging information shall be sent to the transferring user when the call is terminated. Sub clauses 8.10.1, 8.10.2 Forwarding user: and 8.10.3 When a call is forwarded and the forwarding user is charged for the forwarded part of the call, then the charging information shall be sent to the forwarding user when the call is terminated provided that the served user has subscribed to the AOC-E supplementary service with the value of the subscription option set to "for all calls automatically Sub clause 8.15 If the call is terminated while the call is suspended at the calling user's access, and if the calling user attempts to resume the call within the timer, then advice of charge information shall be given to that user at the time of the resume attempt Sub clause 8.16 No charging information for the use of the Three-Party supplementary service can be sent to the served user

51 MCMC MTSFB TC T008:2014

Annex A, Sub clause The Malaysian network may not include some charges, e.g. charges A.2.1 incurred by the use of some supplementary services, in the subtotal charges and/or the total charges Annex A, Sub clause A.3 Charging information (AOC) can be given in currency units or metering pulses according to access arrangements

B3.12.3 Functional Capabilities and Information Flows

The functional capabilities and information flows (stage 2 description) for the AOC supplementary service are contained in the standard ETS 300 181 [38]. The stage 2 description can be taken as informative. The implementation of the AOC supplementary service in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

B3.12.4 Digital Subscriber Signaling System No. One (DSS1) Protocol

The DSS1 protocol (stage 3 description) for the AOC supplementary service is contained in the standard ETS 300 182-1 [39]. The AOC supplementary service is implemented in the Malaysian network without national definitions or exceptions.

B3.13 Three Party (3PTY)

B3.13.1 Definition

The 3PTY supplementary service enables a user to establish, participate in and control, a three- way conversation, i.e. a simultaneous communication involving the served user and two remote parties.

B3.13.2 Service Description

The service description (stage 1 description) for the 3PTY supplementary service is contained in the standard ETS 300 186 [40].

The following gives the recommended guidelines for the implementation of the 3PTY supplementary service in the Malaysian network.

Sub clause 6.2.3.1 Establishing a three-way conversation that would include calls which are not intended for speech communication is not prevented Sub clauses 8.1.1, 8.1.2 No charging information for the use of the Three-Party supplementary and 8.1.3 service can be sent to the served user. Sub clause 8.16 A remote party in a three-way conversation can invoke the 3PTY supplementary service in order to make their connection to the three-way conversation a part of another three-way conversation controlled by that remote party

A remote party in a three-way conversation can invoke the 3PTY supplementary service in order to make their connection to the three-way conversation a part of another three-way conversation controlled by that remote party

52 MCMC MTSFB TC T008:2014

B3.13.3 Functional Capabilities and Information Flows

The functional capabilities and information flows (stage 2 description) for the 3PTY supplementary service are contained in the standard ETS 300 187 [41]. The stage 2 description can be taken as informative. The implementation of the 3PTY supplementary service in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

B3.13.4 Digital Subscriber Signaling System No. One (DSS1) Protocol

The DSS1 protocol (stage 3 description) for the 3PTY supplementary service is contained in the standard ETS 300 188-1 [42]. The 3PTY supplementary service is implemented in the Malaysian network without national definitions or exceptions.

B3.14 Call Forwarding (CFB, CFU, CFNR)

B3.14.1 Definition

The Call Forwarding supplementary services comprise the following services: -Call Forwarding Busy (CFB); -Call Forwarding Unconditional (CFU); -Call Forwarding No Reply (CFNR).

The CFB supplementary service enables a served user to have the network redirect to another user calls which are addressed to the served user´s ISDN number and meet busy.

The CFU supplementary service enables a served user to have the network redirect to another user calls which are addressed to the served user´s ISDN number.

The CFNR supplementary service enables a served user to have the network redirect to another user call which are addressed to the served user´s ISDN number, and for which the connection is not established within a defined period of time.

B3.14.2 Service Description

CFB:

The service description (stage 1 description) for the CFB supplementary service is contained in the standard ETS 300 199 [45].

The following gives the recommended guidelines for the implementation of the CFB supplementary service in the Malaysian network.

Clause 5 and Sub clause 6.2.3 The maximum number for call diversions is 5 for each call.

Sub clause 7.1 Once a call has been forwarded to a non-ISDN network the indication call forwarded is used.

Once a call arrives at an ISDN network from a non-ISDN network with the indication forwarded call the call forwarding counter will be set to one, if no other value for the call forwarding counter is supplied.

53 MCMC MTSFB TC T008:2014

Sub clause 8.17 Forwarding any UUI or request for UUS may be restricted to forwarding users who subscribe to the relevant parts of the UUS supplementary service.

CFU:

The service description (stage 1 description) for the CFU supplementary service is contained in the standard ETS 300 200 [46].

The following gives the recommended guidelines for the implementation of the CFU supplementary service in the Malaysian network.

Clause 5 and Sub clause 6.2.3 The maximum number for call diversions is 5 for each call. Sub clause 7.1

Once a call has been forwarded to a non-ISDN network the indication call forwarded is used.

Once a call arrives at an ISDN network from a non-ISDN network with the indication forwarded call the call forwarding counter will be set to one, if no other value for the call forwarding counter is supplied. Sub clause 8.17 Forwarding any UUI or request for UUS may be restricted to forwarding users who subscribe to the relevant parts of the UUS supplementary service.

CFNR:

The service description (stage 1 description) for the CFNR supplementary service is contained in the standard ETS 300 201 [47].

The following gives the recommended guidelines for the implementation of the CFNR supplementary service in the Malaysian network.

Clause 5 and Sub clause 6.2.3 The maximum number for call diversions is 5 for each call. Sub clause 6.1 The value of 30 seconds will be used for the no reply timer Sub clauses 6.2.3.1 and 6.3.3 The method b) is used. The call to the served user will be cleared when the CFNR supplementary service is invoked. If the forwarded call cannot be completed the call shall be terminated Sub clause 7.1 Once a call has been forwarded to a non-ISDN network the indication call forwarded is used.

Once a call arrives at an ISDN network from a non-ISDN network with the indication forwarded call the call forwarding counter will be set to one, if no other value for the call forwarding counter is supplied.

54 MCMC MTSFB TC T008:2014

Sub clause 8.17 Forwarding any UUI or request for UUS may be restricted to forwarding users who subscribe to the relevant parts of the UUS supplementary service.

If the calling user requests service 1 and indicates that it is not required on the call, then if the called user has explicitly accepted the request, the request for the call forwarding no reply supplementary service will be rejected and the call shall not be forwarded. Annex A The following service provider option in the note is supported: the request for the call forwarding no reply supplementary service will be rejected and the call will not be forwarded

B3.14.3 Functional Capabilities and Information Flows

CFB:

The functional capabilities and information flows (stage 2 description) for the CFB supplementary services are contained in the standard ETS 300 203 [48]. The stage 2 description can be taken as informative. The implementation of the CFB supplementary service in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

CFU:

The functional capabilities and information flows (stage 2 description) for the CFU supplementary services are contained in the standard ETS 300 204 [49]. The stage 2 description can be taken as informative. The implementation of the CFU supplementary service in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

CFNR:

The functional capabilities and information flows (stage 2 description) for the CFNR supplementary services are contained in the standard ETS 300 205 [50]. The stage 2 description can be taken as informative. The implementation of the CFNR supplementary service in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

B3.14.4 Digital Subscriber Signaling System No. One (DSS1) Protocol

The DSS1 protocol (stage 3 description) for the Call Forwarding supplementary services is contained in the standard ETS 300 207-1 [51].

The following gives the recommended guidelines for the implementation of the Call Forwarding supplementary services in the Malaysian network.

55 MCMC MTSFB TC T008:2014

Clause 5 The diversion supplementary services are provided on a per ISDN number basis.

The call forwarding services can be subscribed collectively for all the basic services to which the user(s) subscribes Sub clause 6.1 The subscription options listed in the table 1 are provided.

In the table 2 the following network provider option values are applicable:

-served user call is cleared on invocation of diversion; -maximum number of diversions for a single call is 5; -call forwarding on no reply timer value is 20 s; -partial rerouting is provided at the T reference point Sub clause 9.1.1.1 The forwarding exchange shall verify the forwarded-to number only for a limited set of numbers; the minimum requirement is that emergency numbers are not accepted as forwarded to numbers Sub clauses 9.2.3.1 The type of the number shall be set to "unknown" and the number is organized and 9.2.5.1 according to the network dialing plan. Sub clause 9.2.4.4.1 The value of T-CFNR is 20 s and clause 13 Sub clause 9.2.4.4.1 The network provider option "served user call retention on invocation of diversion" is "clear call on invocation" Sub clauses 10.4.1 If a diverted call is presented from a private network to the public network, then and 10.5.1 the public network is required to check the redirecting number from the SETUP message. The number shall be checked against the numbering space of the private network. In case of a mismatch the redirecting number shall be replaced by the default number associated with the private network.

It is recommended for the coding of the redirecting number information sent by the private network: - The "numbering plan identification" field shall be coded "ISDN/Telephony numbering plan". In case DDI is not activated for the same access: - The "type of number" field shall be coded "subscriber number" and the full ISDN subscriber number shall be sent.

In case DDI is activated for the same access: - The "type of number" field shall be coded "unknown" and only the extension number of the redirecting number shall be sent. The network then completes the redirecting number by adding the national number of the access to the redirecting number information. Sub clause 10.5.1 The public network shall clear the call towards the private network on acceptance of the call rerouting request

56 MCMC MTSFB TC T008:2014

B3.15 User-to-User Signaling (UUS)

B3.15.1 Definition

The UUS supplementary service enables a user to send/receive a limited amount of information to/from another user over the signaling channel in association with a call to the other user. This information shall be passed transparently (i.e. without modification of contents) through the network. The network shall not interpret or act upon this information.

The user can transfer UUI in different phases of the call depending on the service(s) to which the user subscribes. These services are: a) Service 1 - User-to-user information exchanged during the set-up and clearing phases of a call/connection, by transporting the User-to-user information element within call/connection control messages b) Service 2 - User-to user information exchanged from the sender’s point of view during call/connection establishment, between the ALERTING and CONNECT messages, within USER INFORMATION messages; and c) Service 3 - User-to-user information exchanged while a call/connection is in the Active state, within USER INFORMATION messages.

B3.15.2 Service Description

The service description (stage 1 description) for the UUS supplementary service is contained in the standard ETS 300 284 [52].

The following gives the recommended guidelines for the implementation of the UUS supplementary service in the Malaysian network.

Clause 5 Service provider option for service 2, UUI sent by the calling user prior to receiving the acceptance of the call by the called user may be delivered to the called user after the call has been established, is supported.

Note on limitation of UUI to only 32 octets during an interim period of time is not applicable for the Malaysian network. Sub clause 6.1 Service provider option about provision of one or any combination of services is supported. Service provider option about withdrawal separately per service is supported. Sub clause 6.2.1.3 Service provider option about activation of service 3 by the called user after the connection has been established is supported Sub clause 6.3.3 In case of excessive UUI length the sending user shall be informed Clause 7 Service provider option about explicit acceptance, if the remote user replies with UUI to explicit request sent to an ISDN only supporting implicit requests, is supported. Sub clauses 8.10.1, Forwarding any UUI or request for UUS may be restricted to forwarding users 8.10.2 and 8.10.3 who subscribe to the relevant parts of the UUS supplementary service

57 MCMC MTSFB TC T008:2014

Sub clause 8.10.3 If the calling user requests service 1 and indicates that it is not required on the call, then if the called user has explicitly accepted the request, the request for the call forwarding no reply supplementary service will be rejected and the call shall not be forwarded. Annex A The following service provider option in the note is supported: the request for the call forwarding no reply supplementary service will be rejected and the call will not be forwarded.

B3.15.3 Functional Capabilities and Information Flows The functional capabilities and information flows (stage 2 description) for the UUS supplementary service are contained in the standard ETR 285 [53]. The stage 2 description can be taken as informative. The implementation of the UUS supplementary service in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

B3.15.4 Digital Subscriber Signaling System No. One (DSS1) Protocol

The DSS1 protocol (stage 3 description) for the UUS supplementary service is contained in the standard ETS 300 286-1 [54].

The following gives the recommended guidelines for the implementation of the UUS supplementary service in the Malaysian network.

Sub clause 6.1 Any combination of the following possibilities can be provided separately or globally: -service 1 implicit, or service 1 implicit together with service 1 explicit; -service 2; -service 3. Sub clauses 9.2.2.1 and The calling network shall accept the first two USER INFORMATION 9.2.2.2 messages from the calling user and the calling network shall deliver them to the called user after the calling and called network have entered the Active (N10) call state. Sub clause 9.2.2.2 The calling network shall send a STATUS message with cause #43 to the calling user when discarding the USER INFORMATION message.

The called network shall send a STATUS message with cause #43 to the called user when discarding the USER INFORMATION message Sub clause 9.3.1.2.1 During the Active (U10) call state, the calling user or the called user can activate service 3 Sub clause 9.3.2.2 The sending network shall send a STATUS message with cause #43 to the sending user when discarding the USER INFORMATION message.

58 MCMC MTSFB TC T008:2014

B3.16 Explicit Call Transfer (ECT)

B3.16.1 Definition

The ECT supplementary service enables a user (user A) to transform two of that user’s calls (an active call and a held call), each of which can be an incoming call or an outgoing call, into a new call between user B and user C.

B3.16.2 Service Description

The service description (stage 1 description) for the ECT supplementary service is contained in the standard ETS 300 367 [55].

The following gives the recommended guidelines for the implementation of the ECT supplementary service in the Malaysian network.

Clause 5 and Sub clause 6.2.3 The service provider option, that the ECT supplementary service can be invoked after user C has been informed of the call (i.e. an outgoing call from A to user C, where the connection has not yet been established), is supported Sub clause 8.1.3 When the call is transferred and the transferring user is charged for the transferred part of the call, then the charging information shall be sent to the transferring user when the transferred call is terminated provided that the served user has activated the AOC-E supplementary service for that call

B3.16.3 Functional Capabilities and Information Flows

The functional capabilities and information flows (stage 2 description) for the ECT supplementary service are contained in the standard ETS 300 368 [56]. The stage 2 description can be taken as informative. The implementation of the ECT supplementary service in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

59 MCMC MTSFB TC T008:2014

B3.16.4 Digital Subscriber Signaling System No. One (DSS1) Protocol

The DSS1 protocol (stage 3 description) for the ECT supplementary service is contained in the standard ETS 300 369-1 [57].

The following gives the recommended guidelines for the implementation of the ECT supplementary service in the Malaysian network.

Clause 5 and Sub clause 9.2.5 The network option to allow the invocation of the ECT service when one of the calls is an outgoing call in the Call delivered (alerting) state is supported. Sub clause 9.2 The explicit linkage procedure is supported Sub clause 10.3 The “mechanism to avoid looping of uncontrolled circuits” is supported by the public network. If the loop prevention procedure cannot decide whether the resulting connection would result in a loop, the call transfer is completed. The time supervision for the loop prevention procedure is 2 seconds

B3.17 Supplementary Service Interactions

The public network shall support protocol interaction between the various supplementary services according to ETS 300 195-1 [43]. Network options of ETS 300 195-1 are left as implementation options, unless stated otherwise in the Sub clauses relating to the individual supplementary services. Should any conflict arise between ETS 300 195-1 and the specifications in Sub clause 3.2 to 3.16, then the text of the individual supplementary services shall be taken as definitive.

TE1 - ISDN-capable terminal equipment e.g.: Digital phone and digital fax

TE2 - Non-ISDN equipment e.g: Analogue phone and the RS-232 serial port on computer

TA - Terminal adapter that interface the TE2 devices with ISDN network

NT1 - Network terminator that reside between telco’s network and customer equipment

NT2 - An intelligent device that can perform switching function e.g: PABX and Local Area Network (LAN)

60

Annex C (Informative)

Amendments

Amendments to SKMM FTS ISDN-BA Rev. 1.01:2007 Page Clause Items Amended Cover - The document has adopted new numbering system and cover page. It has been renumbered as “MCMC MTSFB TC T008:2014”.

i - Explanatory note on the development of Technical Codes has been included.

1 1.2 Reference for Section D has been replaced with EN 300 403-1 11/99.

1 2 New clause on normative references has been included.

3 4.1 Power supply requirements have been revised based on the Information Booklet 2012 Edition, Approval of Electrical Equipment, issued by the Energy Commission.

4 4.1 Alphanumeric keypad layout has been included. (Figure 2)

4 4.2.1 New clause on network interface has been included.

4 4.2.2 Connector specification has been revised to be either RJ11 or RJ45.

- - Old clause 2.3 on characteristics of telephone has been removed.

5 4.3 New clause on interoperability requirement has been included.

20 Section D Network layer requirements have been revised based on EN 300 403-1 11/99, Integrated Services Digital Network (ISDN): Digital Subscriber Signaling System No. One (DSS1) protocol: Signaling network layer for circuit-mode basic call control; Part 1: Protocol Specification [ITU-T Recommendation Q.931 (1993), modified].

32 Annex A The normative references have been updated.

33 Annex B Technical guidelines of ISDN supplementary service have been included.

61

SKMM MTSFB TC T001:2013

Acknowledgements

Members of Fixed Terminal Working Group

Mr Abd. Hamid Mustafa (Chairman) Telekom Malaysia Berhad Mr Ahmad Faizan Pardi (Vice Chairman) SIRIM QAS International Sdn Bhd Mrs Nur Rashidah Abas Azmi (Secretary) Telekom Malaysia Berhad Mr Shahadan Man AJV Holding Sdn. Bhd. Mr Zulkhairi Zainal Abidin Epson Malaysia Mr Tan Keok Kuang NEC Corporation of Malaysia Sdn. Bhd Mr Khairul Akmal Zahri Packet One Networks Sdn. Bhd. Mr Syed Ahmad Anas Packet One Networks Sdn. Bhd. Mr Sam Choong Panasonic Malaysia Mr Pang Chieng Yong Panasonic Malaysia Mr Mohd Ackmal Abd. Samad Panasonic System Networks Mrs Hafizah Zainal Abiddin SIRIM QAS International Sdn Bhd Mrs Nurhafenah Abdul Jalil SIRIM QAS International Sdn Bhd Mr Zul Jaafar SIRIM QAS International Sdn Bhd Mr Amin Hapis Khairan Telekom Malaysia Berhad Mr Anuar Wahab Telekom Malaysia Berhad Mrs Badariah Zainal Telekom Malaysia Berhad Mr Md Azmi Karnain Telekom Malaysia Berhad Mr Mohd Syaukiazahar Telekom Malaysia Berhad Mr Muhd Hadzir Abu Hassan Telekom Malaysia Berhad Mrs Nor Maizatul Syima Telekom Malaysia Berhad Mrs Nur Faliza Yaakup Telekom Malaysia Berhad Mr Rahmat Fauzi Zainal Telekom Malaysia Berhad Mrs Raja Nor Suha Telekom Malaysia Berhad Mrs Rosliza Abu Bakar Telekom Malaysia Berhad Mrs Suriyati Rahim Telekom Malaysia Berhad Ms Wan Nur Hanani Telekom Malaysia Berhad Mr Othman Sidek TIME dotCom Berhad

62 MCMC MTSFB TC T009:2014

TECHNICAL CODE

SPECIFICATION FOR INTEGRATED SERVICES DIGITAL NETWORK (ISDN) USING PRIMARY RATE ACCESS

First Revision

Developed by Registered by

Registered date: 18 December 2014

© Copyright 2014

MCMC MTSFB TC T009:2014

DEVELOPMENT OF TECHNICAL CODES

The Communications and Multimedia Act 1998 (‘the Act’) provides for Technical Standards Forum designated under section 184 of the Act or the Malaysian Communications and Multimedia Commission (‘the Commission’) to prepare a technical code. The technical code prepared pursuant to section 185 of the Act shall consist of, at least, the requirement for network interoperability and the promotion of safety of network facilities.

Section 96 of the Act also provides for the Commission to determine a technical code in accordance with section 55 of the Act if the technical code is not developed under an applicable provision of the Act and it is unlikely to be developed by the Technical Standards Forum within a reasonable time.

In exercise of the power conferred by section 184 of the Act, the Commission has designated the Malaysian Technical Standards Forum Berhad (‘MTSFB’) as a Technical Standards Forum which is obligated, among others, to prepare the technical code under section 185 of the Act.

A technical code prepared in accordance with section 185 shall not be effective until it is registered by the Commission pursuant to section 95 of the Act.

For further information on the technical code, please contact:

Malaysian Communications and Multimedia Commission (MCMC) Off Persiaran Multimedia 63000 Cyberjaya Selangor Darul Ehsan MALAYSIA

Tel: +60 3 8688 8000 Fax: +60 3 8688 1000 http://www.skmm.gov.my

OR

Malaysian Technical Standards Forum Bhd (MTSFB) 4805-2-2, Block 4805, Persiaran Flora CBD Perdana 2 Cyber 12 63000, Cyberjaya Selangor Darul Ehsan MALAYSIA

Tel: +60 3 8322 1441/1551 Fax: +60 3 8322 0115 http://www.mtsfb.org.my

i MCMC MTSFB TC T009:2014

CONTENTS

Committee Representation ...... iv Foreword ...... v

Section A Introduction………………………………………………………………………………………………………. 1 1. Scope ...... 1 2. Normative references ...... 2 3. Abbreviations...... 2 4. General requirements ...... 3 4.1 Design of Equipment ...... 3 4.2 Interface ...... 4 4.3 Interoperability ...... 4 5. Electromagnetic Compatibility & Electrical Safety Requirements ...... 4

Section B Primary Rate User-Network Interface – Layer 1 Specification (ITU-T Recommendation I.431 03/1993 & Amendment 1 06/1997) ...... 5

Section C ISDN User-Network Interface – Data Link Layer (ITU-T Recommendation Q.921 09/1997 & Amendment 1 06/2000) ...... 7

Section D Network layer requirements based on EN 300 403-1 11/99, Integrated Services Digital Network (ISDN): Digital Subscriber Signaling System No. One (DSS1) protocol: Signaling network layer for circuit-mode basic call control; Part 1: Protocol Specification [ITU-T Recommendation Q.931 (1993), modified]...... 12 1 Introduction ...... 12 2 Supporting Information ...... 12 3 National Option Selections and Clarifications ...... 13 4. Terminal Characteristics Related To Access Signaling ...... 18 5. Terminal Adaptors ...... 18 5.1 Circuit Mode Bearer Services ...... 18

ii MCMC MTSFB TC T009:2014

Tables

1 Frame structure for peer-to-peer communication ...... 7 2 Elements of procedure and formats of field for data link layer peer-to-peer communication………………………………………………………………………………...... 7 3 Elements for layer-to-layer communication ...... 9 4 Procedures for use by the data link layer ...... 9 5 Annexes and Appendices ...... 10 6 Appendices...... 13

Figures 1 Reference Configuration for Multiple Connections (Figure 1/I.412) ...... 1 2 Alphanumeric Keypad Layout (ITU-T Rec. E. 161)...... 4

Annexes

A Normative references ...... 19 B Technical Guidelines of ISDN Supplementary Service ...... 20 C Addendum/Corrigendum ...... 48

iii MCMC MTSFB TC T009:2014

Committee Representation

The Fixed Terminal Working Group under the Malaysian Technical Standards Forum Bhd (MTSFB) which developed this Technical Code consists of representatives from the following organisations:

NEC Corporation of Malaysia Sdn. Bhd. SIRIM QAS International Sdn Bhd Telekom Malaysia Berhad TIME dotCom Berhad

iv MCMC MTSFB TC T009:2014

FOREWORD

This technical code for the Specification for Integrated Services Digital Network (ISDN) using Primary Rate Access (First Revision) (‘this Technical Code’) was developed pursuant to section 185 of the Act 588 by the Malaysian Technical Standards Forum Bhd (MTSFB) via its Fixed Terminal Working Group.

This Technical Code was developed for the purpose of certifying communications equipment under the Communications and Multimedia (Technical Standards) Regulations 2000.

This Technical Code cancels and replaces Technical Specification for Connecting to the Integrated Services Digital Network (ISDN) using Primary Rate Access, SKMM FTS ISDN-PA Rev. 1.01:2007.

This Technical Code shall continue to be valid and effective until reviewed or cancelled.

v MCMC MTSFB TC T009:2014

THIS PAGE IS INTENTIONALLY LEFT BLANK

vi MCMC MTSFB TC T009:2014

SPECIFICATION FOR INTERGRATED SERVICES DIGITAL NETWORK (ISDN) USING PRIMARY RATE ACCESS

Section A

Introduction

1. Scope

1.1 This Specification identifies the minimum technical requirements for connecting to the Integrated Services Digital Network (ISDN) at the T interface, using Primary Rate Access (PRA).

Figure 1. Reference Configuration for Multiple Connections (Figure 1/I.412)

1.2 The ISDN PRA equipment connected to the T interface (see Figure 1) shall have the Network Termination 2 ( NT2) function. Suppliers shall demonstrate that the equipment has been tested to comply with the requirements defined in Section A, B, C and D of this Specification.

Section B – Physical layer requirements based on ITU-T Rec. I.431, Primary Rate User- Network Interface  Layer 1 Specification

Section C – Link Access Procedure on the D-channel, LAPD based on ITU-T Rec. Q.921, ISDN User-Network Interface  Data Link Layer Specification

Section D – Network layer requirements based on EN 300 403-1 11/99, Integrated Services Digital Network (ISDN): Digital Subscriber Signaling System No. One (DSS1) protocol: Signaling network layer for circuit-mode basic call control; Part 1: Protocol Specification [ITU-T Recommendation Q.931 (1993), modified].

1

MCMC MTSFB TC T009:2014

2. Normative references

The following normative references are indispensable for the application of this Specification. For dated references, only the edition cited applies. For undated references, the latest edition of the normative references (including any amendments) applies.

See Annex A.

3. Abbreviations

The use of the term Terminal Equipment (TE) within the Specification refers to a Terminal Equipment Type 1 (TE1), a Terminal Adaptor (TA) or a NT2.

The following notations are used in the Specification:

CR Conformance Requirement defines features and functions that must be supported at minimum.

M Mandatory requirement is where the TE implementation shall conform to those clauses in that section relating to the operation of Layer 1, Layer 2 and Layer 3 protocol in the TE.

O Optional requirement means it is optional whether TE implements that function but if function is implemented, it shall conform to the clauses in that section relating to the operation of the TE Layer 1, Layer 2 and Layer 3 protocol.

However, the use of optional functions is possible only if the network operators have implemented these options in their networks.

NA Not Applicable is where the requirements specified in that section on the TE shall not be applicable for attachment.

GID The section provides General Information and Definitions.

TE1 ISDN-capable terminal equipment e.g.: Digital phone and digital fax

TE2 Non-ISDN equipment e.g: Analogue phone and the RS-232 serial port on computer

TA Terminal adapter that interfaces the TE2 devices with ISDN network

NT1 Network terminator that resides between telco’s network and customer equipment

NT2 An intelligent device that can perform switching function e.g: PABX and Local Area Network (LAN)

2

MCMC MTSFB TC T009:2014

4. General requirements

4.1 Design of Equipment CR

Note 1 Power supply a) For AC powered TE, the operating voltage shall be rated/ marked at 230V or 240V in line with the country's nominal voltage and frequency in accordance to MS IEC 60038. If the product is rated with multiple or a range of voltages, voltage range between 230V (+10%,-6%) shall be included. Testing shall be conducted based on 230V (+10%,-6%) or 240V and other relevant voltages, if the product is marked with multiple or a range of voltages.

b) Product shall be rated/ marked at 50Hz and testing shall be conducted at 50Hz. If the product is marked at 50/60Hz or 50- 60Hz then testing shall be conducted either at 50Hz or 60Hz, whichever is more unfavorable.

c) Where external power supply is used, e.g AC adaptor, it shall not affect the capacity of the equipment to meet this specification. Adaptor must be pre-approved by the relevant regulatory body before it can be used with the equipment.

Note i) Either one of these options shall be applied.

M Identification of Equipment shall be marked with: equipment a) supplier’s or manufacturer’s name or identification mark M b) supplier’s or manufacturer’s model or type reference M The markings shall be legible, indelible and readily visible M Keypad Dialing a) Keypads used in equipment for dialing shall be alphanumeric keypads and the relationships between the letters and the digits shall comply with ITU-T Rec E.161 as shown in Figure 2. M b) The associated letters shall not impair the legibility of the digit (§ 3.1.1, ITU-T Rec. E.161). M c) The `tactile identifier on the “5” button shall be provided (§ 3.6, ITU-T Rec. E.161).

3

MCMC MTSFB TC T009:2014

1 2 3 ABC DEF

4 5 6 GHI JKL MNO

7 8 9 PQRS TUV WXYZ

* 0 #

Figure 2. Alphanumeric Keypad Layout (ITU-T Rec. E. 161)

4.2 Interface

4.2.1 Network Interface

Connector - Coaxial cable or RJ45 Line Coding - HDB3 Impedance - 120Ω (RJ45) or 75Ω (coaxial cable) Framing - Multi frame CRC Switch Type - NET 5

4.3 Interoperability

TE1 and TA are dynamically interoperable if they implement a common and compatible set of features, functions and options and can demonstrate satisfactory mutual communication in a real network architecture environment as performance test conditions are varied and exercised. It is mandatory that the TE1 and TA be tested with the respective Service Provider to ensure interoperability. The general reference model for interoperability is shown in Figure 1.

5. Electromagnetic Compatibility & Electrical Safety Requirements

5.1 The equipment shall comply with the limits for conducted disturbance at the main terminals and telecommunication ports, and the limits for radiated disturbance are defined in the IEC CISPR 22.

5.2 The equipment shall comply with the IEC 60950-1 safety standard1. The requirements in IEC 60950-1 that are applicable to the equipment [e.g. class of equipment, type of telecommunication network voltage (TNV) circuit and types of components shall be identified and complied with.

1 The safety standard includes, among others, protection of telecommunications network service personnel and users of other equipment connected to the network from hazards in the equipment.

4

MCMC MTSFB TC T009:2014

Section B

Primary Rate User-Network Interface – Layer 1 Specification (ITU-T Recommendation I.431 03/1993 & Amendment 1 06/1997)

ITU-T Rec. ETSI Title Remarks I.431 TBR 4 Introduction 1 - GID Supports user-network interface at 2048 kbit/s Primary rate access at the T Type of configuration 2 - M reference point shall support the point-to-point configuration only. Electrical characteristics are defined in ITU-T Rec. G.703. Functional characteristics 3 M Heading M – B-channel (64 kbit/s) O – H0-channel O – H1-channel M – D-channel (64 kbit/s) Summary of functions (Layer 1) 3.1 – M – Bit timing M – Octet timing M – Frame alignment O – Power feeding M – Maintenance M – CRC procedure

Interchange circuits 3.2 – M Two interchange circuits, one for each direction, are used for the transmission of digital signals Activation/deactivation 3.3 – M Active at all times Operational functions 3.4 – M Heading

Definitions of signals at the 3.4.1 9.5.1 GID interface

Definitions of state tables at 3.4.2 – GID network and user sides

Layer 1 states on the user side 3.4.3 9.5.2 M of the interface

Layer 1 states at the network 3.4.4 – NA Network side side of the interface Definition of primitives 3.4.5 – M State tables 3.4.6 9.5.3 M Table 2/I.431 is applicable Interface at 1544 kbit/s 4 – NA

5

MCMC MTSFB TC T009:2014

ITU-T ETSITB Title Rec. CR Remarks R 4 I.431 Interface at 2048 kbit/s 5 – – Heading Electrical characteristics 5.1 9.2 M a) 120  symmetrical pair 9.3 interface b) ITU-T Rec. G.703 section 6 Frame structure 5.2 9.4 M Note 1 Timing considerations 5.3 M Jitter 5.4 9.3.3 M Tolerable longitudinal voltage 5.5 9.3.4 M Output signal balance 5.6 – M f=1 MHz;  40 dB 1 MHz < f  30 MHz; decreasing from 40 dB at 20 dB/decade Impedance towards ground 5.7 9.2.2 M 10 Hz < f  1 MHz; > 1000  9.3.5 Interface procedures 5.8 9.5.5 M Maintenance at the interface 5.9 9.5.4 M On the user side Connector 6 – M ISO/IEC standards and permanent wiring are permitted 120  ± 20%, 200 kHz - 1 MHz Interface wiring impedance 7 – M 120  ± 10%, 1 MHz Two symmetrical pair connections shall be provided. No power feeding is available in either direction. Power feeding to the NT 8 – O Provision of power using a separate pair of wires, is optional. Timeslot assignment for interfaces Annex – Note having only H0 channels A 2 Timeslot assignment for 2048 Annex – Note kbits/s interface having H11 B 3 channel

NOTES: i) H-channels may not be supported depending on local implementation. ii) ‘M’ if H0 channels are supported. iii) ‘M’ if H11 channels are supported. iv) The use of optional functions is possible only if the network operators have implemented these options in their networks.

6

MCMC MTSFB TC T009:2014

Section C

ISDN User-Network Interface – Data Link Layer (ITU-T Recommandation Q.921 09/1997 & Amendment 1 06/2000)

Table 1. Frame structure for peer-to-peer communication

ITU-T ETSI Title Rec. TBR 4 CR Remarks Q.921 General 1 – GID Frame structure for peer-to-peer 2 10.1 GID Heading communication General 2.1 10.1.1 M Flag sequence 2.2 10.1.2 M Address field 2.3 10.1.3 M Control field 2.4 10.1.4 M Information field 2.5 10.1.5 M Transparency 2.6 10.1.6 M FCS field 2.7 10.1.7 M Format convention 2.8 10.1.8 – Invalid frames 2.9 10.1.9 M Note Frame abort 2.10 – M Not a TBR 4 requirement

NOTE. TBR 4 includes a frame, which contains a TEI that is not assigned to the TE as invalid.

Table 2. Elements of procedure and formats of field for data link layer peer-to-peer communication

ITU-T ETSI Title Rec. CR Remarks TBR 4 Q.921 Elements of procedure and 3 10.2 – Heading formats of field for data link layer peer-to- peer communication General 3.1 10.2.1 GID Address field format 3.2 10.2.2 M Address field variables 3.3 10.2.3 – Note 1

7

MCMC MTSFB TC T009:2014

Table 2. Elements of procedure and formats of field for data link layer peer-to-peer communication (continued)

ITU-T ETSI Title Rec. CR Remarks TBR 4 Q.921 Control field formats 3.4 10.2.4 M Control field parameters and 3.5 10.2.5 M associated state variables Poll/Final (P/F) bit 3.5.1 10.2.5.1 M Multiple frame operation – 3.5.2 10.2.5.2 M variables and sequence numbers Unacknowledged operation – One parameter is defined, N201 3.5.3 GID variables and parameters (see 5.9.3). Frame types 3.6 10.2.6 – Heading Commands and responses 10.2.6.1 3.6.1 M Refer to Table 5/Q.921 Note 3 Information (I) command 3.6.2 10.2.6.2 M Set Asynchronous Balanced Mode Extended (SABME) 3.6.3 10.2.6.3 M command Disconnect (DISC) command 3.6.4 10.2.6.4 M Unnumbered Information (UI) 3.6.5 10.2.6.5 M command Receive Ready (RR) 3.6.6 10.2.6.6 M command/response Reject (REJ) command/response 3.6.7 10.2.6.7 M Receive Not Ready (RNR) 3.6.8 10.2.6.8 M command/response Unnumbered Acknowledgement 3.6.9 10.2.6.9 M (UA) response Disconnected Mode (DM) 3.6.10 10.2.6.10 M response Frame Reject (FRMR) response 3.6.11 – M Note 2 Exchange Identification (XID) 3.6.12 – NA Note 2 command/response

NOTES: i) Value ‘0’ is allocated to TEI. Other values are not used in PRA. ii) TBR 4 does not support FRMR response and XID command/response.

8

MCMC MTSFB TC T009:2014

Table 3. Elements for layer-to-layer communication

Title ITU-T ETSI CR Remarks Rec. TBR 4 Q.921

Elements for layer-to-layer 4 – GID communication

Table 4. Procedures for use by the data link layer

ITU-T ETSI Title Rec. CR Remarks TBR 4 Q.921 Definition of peer-to-peer 5 – GID procedures for the data link layer Procedures for the use of P/F bit 5.1 – – Heading Unacknowledged information 5.1.1 10.4.1 M NA to PRA transfer Acknowledged multiple frame 10.6 information transfer 5.1.2 and M 10.7 Procedure for unacknowledged 5.2 10.4 – NA to PRA information transfer TEI management procedures 5.3 10.5 – NA to PRA Initialization of data link layer 5.4 – NA Note 1 parameters Procedure for establishment and release of multiple frame 5.5 10.6 – operation Procedure for information transfer 5.6 10.7 GID in multiple frame operation Re-establishment of multiple 5.7 – – frame operation Exception condition reporting and 10.9 Multiple TEI assignment is not 5.8 GID recovery Note 2 applicable. List of system parameters 5.9 10.10 M Timer T200 5.9.1 10.10.1 M The default value shall be 1 s. Max number of retransmissions 5.9.2 10.10.2 M The default value shall be 3. (N200) Max number of octets in an The default value shall be 260 5.9.3 10.10.3 M information field (N201) octets.

9

MCMC MTSFB TC T009:2014

Table 4. Procedures for use by the data link layer (continued)

ITU-T ETSI Title Rec. CR Remarks TBR 4 Q.921 Max number of transmission of the TEI identity request message 5.9.4 10.10.4 M NA to PRA (N202) Max number of outstanding I For a SAP supporting primary rate 5.9.5 10.10.5 M frames (k) signaling, the value is 7. Timer T201 5.9.6 – NA NA to PRA Timer T202 5.9.7 10.10.6 M NA to PRA Timer T203 5.9.8 – O The default value is 10 s. – 10.10.7 – GID Layer 2 response time Note 3 Data link monitor function 5.10 – O

NOTES: i) The data link layer parameters shall be initialized to default values. Ii) TBR 4 considers the receipt of an invalid N(R) as the only condition for frame rejection. iii) The maximum time between receipt of an incoming frame and generation of a response shall not exceed 500 ms, operating in a point-to-point signaling connection.

Table 5. Annexes and Appendices

ITU-T ETSI Title Rec. CR Remarks TBR 4 Q.921 Provision for point-to-point data For single point-to-point signaling link connection Annex connection at layer 3, TEI value 0 10.3 M A shall be used in combination with SAPI 0. An SDL representation of the Annex point- to-point procedures of data – – B link layer SDL representation of the Annex broadcast procedures of the data – GID C link layer State transition table of the point- Annex to- point procedures of the data – – D link layer

10

MCMC MTSFB TC T009:2014

Table 5. Annexes and Appendices (continued)

ITU-T ETSI Title Rec. CR Remarks TBR 4 Q.921

Annex – GID Provision of multi-selective reject E option Protocol Implementation Conformance Statement (PICS) Annex – GID to Recommendation Q.921 for F Basic Rate (User-side) Protocol Implementation Conformance Statement (PICS) Annex – GID to Recommendation Q.921 for G Basic Rate (Network-side) Protocol Implementation Conformance Statement (PICS) Annex – GID to Recommendation Q.921 for H Primary Rate (User-side) Protocol Implementation Conformance Statement (PICS) Annex I – GID to Recommendation Q.921 for Primary Rate (Network-side) Inter-exchange signaling data Applicability and additions to frame link layer protocol in Private Annex J structure, elements of procedures, Integrated Services Networks (Q.921 formats of fields, elements for layer- – GID (PISNs) Amend- to-layer communication, peer-to-peer ment 1) procedures to accommodate PISN inter-exchange requirements Retransmission of REJ response Appendix – O frame I Occurrence of MDL-ERROR- INDICATION within the basic Appendix – GID states & actions to be taken by II the management entity Optional basic access May be used by network side system Appendix deactivation procedures – NA management to control deactivation III of access Automatic negotiation of data link Appendix – O layer parameters IV Inter-exchange signaling data link Appendix Occurrence of the MDL-ERROR layer protocol in PISNs V (Q.921 indication primitive in the data link – GID Amend- layer protocol for the support of Inter- ment 1) exchange signaling in PISNs

11

MCMC MTSFB TC T009:2014

Section D

Network layer requirements based on EN 300 403-1 11/99, Integrated Services Digital Network (ISDN): Digital Subscriber Signaling System No. One (DSS1) protocol: Signaling network layer for circuit-mode basic call control; Part 1: Protocol Specification [ITU-T Recommendation Q.931 (1993), modified]

1 Introduction

This section contains clarification and recommended option selections for the ETSI ISDN standards and technical reports related to basic call control procedures of ISDN basic and primary access signaling. This document covers the basic call control of layers 1, 2 and 3. The aim of this document is to avoid unnecessary options and vagueness in ISDN implementations and to ensure the interoperability of ISDN networks and terminal equipment in Malaysia. This requirement has to be followed when implementing access-signaling protocol i.e. Digital Subscriber Signaling System No. 1 (DSS1).

2 Supporting Information

2.1 Integrated Services Digital Network (ISDN): Standards Guide (ETR 076 - December 1996, Fourth Edition)

2.2 Integrated Services Digital Network (ISDN): Customer Access Maintenance (ETR 001 August 1990)

2.3 Integrated Services Digital Network: User –Network interface layer 3 Specifications for basic call control (ETS 300 102-1 12/90)

2.4 Integrated Services Digital Network (ISDN): Digital Subscriber Signaling System No. 1 (DSS1) protocol: Data link layer; Part 2: General protocol specification [ITU-T Recommendation Q.921 (1993), modified] (ETS 300 402-2 11/95).

2.5 Integrated Services Digital Network (ISDN): Digital Subscriber Signaling System No. One (DSS1) protocol: Signaling network layer for circuit-mode basic call control; Part 1: Protocol Specification [ITU-T Recommendation Q.931 (1993), modified]) (ETS 300 403-1 11/95)

2.6 Integrated Services Digital Network (ISDN): Digital Subscriber Signaling System No. One (DSS1) protocol: Signaling network layer for circuit-mode basic call control; Part 1: Protocol Specification [ITU-T Recommendation Q.931 (1993), modified] (EN 300 403-1 11/99).

2.7 Integrated Services Digital Network (ISDN): Digital Subscriber Signaling System No. One (DSS1) Protocol: Signaling Network Layer For Circuit-Mode Basic Call Control: Part 2: Specification and Description Language (SDL) Diagrams (ETS 300 403-2 11/95).

2.8 Integrated Services Digital Network (ISDN) : Application Of The Bearer Capability (BC), High Layer Compatibility (HLC) and Low Layer Compatibility (LLC) Information Elements By Terminals Supporting ISDN Services (ETR 018 11/95)

2.9 ISDN User –Network Interface Layer 3 Specification for basic call control (ITU-T Q.931 3/93)

2.10 Technical Guidelines of ISDN Supplementary Services (Functional Protocol)

12

MCMC MTSFB TC T009:2014

3 National Option Selections and Clarifications

3.1 Layer One Protocol for Basic Call Control (DSS1)

The DSS1 basic call layer one protocol for the basic access is contained in the standard ETS 300 012 (10/98) and for the primary rate access in the standard ETS 300 011 (3/98)

The ETSI technical report ETR 001(8/90) defines the maintenance requirement for basic and primary access.

3.2 Layer Two Protocol for Basic Call Control (DSS1)

The DSS1 basic call layer two protocol for the basic and primary access is contained in the standard ETS 300 402-1 (11/95).

It is recommended that a reset of layer 3 always reset layer 2 in ISDN-terminal equipment. If layer 3 can be reset without resetting layer 2, an ISDN terminal which is reset during the active phase of a call, may lose control over that call.

3.3 Layer Three Protocol for Basic Call Control (DSS1)

The DSS1 layer three protocol for basic call control is contained in the base standard ETS 300 102-1 (12/90), ITU-T Q.931 (3/93), ETS 300 403-1 (11/95) and EN 300 403-1 (11/99). ). The EN 300 403-1 (11/99) is a main standard for DSSI Layer 3 implementation.

When implementing the DSS1 layer three protocol in Malaysia network, the following guidelines are recommended to be taken into account (The main numbering refers to the ITU-T Q.931 (3/93), this standard had been adopted and extended by EN 300 403-1 (11/99).

Table 6. Appendices

Clause No. Clause Description Recommendation

OVERVIEW OF CALL SDL diagrams in the standard ETS 300 403-2 2 CONTROL (11/95) are recommended to be used as informative. The transport of low layer compatibility information element (LLC) to the calling user is supported on the ISDN end-to-end 3.1.3 CONNECT connections. The date/time information element is recommended to be sent by the network. The use of Keypad facility information element is defined in EN 300 122-1 (6/98), "Integrated Services Digital Network (ISDN); Generic keypad protocol for the support of 3.1.6 INFORMATION supplementary services; Digital Subscriber Signaling System No. One (DSS1) protocol; Part 1: Protocol Specification ".

13

MCMC MTSFB TC T009:2014

Table 6. Appendices (continued)

Clause No. Clause Description Recommendation Annex E (network specific facility selection) and Annex C (transit network selection) are not applicable. Transit network selection is implemented in the DSS1 signaling by using operator codes in the called number digits (operator code + called party number).

3.1.14 SETUP The use of Keypad facility information element is defined in EN 300 122-1 (6/98). Two bearer capability information elements are supported (EN 300 403-1 (11/99), subclause 5.11).

Two high layer compatibility information elements are supported (EN 300 403-1(11/99), subclause 5.12) General message 4 format and information elements coding 4.4 Message type No national message types are defined. No information elements belonging to codeset 6 (national) are 4.5.2 Extension of codesets defined.

4.5.7 Call state Only CCITT standardized coding is used.

Type of number: Codepoint showing "subscriber number" shall be used from network to user. The codepoint used in connection with the supplementary services Direct Dialing In (DDI) and 4.5.8 Called party number Multiple Subscriber Number (MSN) is specified in a separate document for ISDN supplementary services Technical Guidelines of ISDN Supplementary Services(Functional Protocol) The use of the fields is subject to a separate document for 4.5.10 Calling party number ISDN supplementary services Technical Guidelines of ISDN Supplementary Services(Functional Protocol) Coding standard: Codepoints showing “CCITT standardized coding” and "National standard" may be used. 4.5.12 Cause No national cause values are defined.

4.5.13 Channel identification Coding standard: CCITT standardized coding is always used. 4.5.15 Date/time The date/time indicated is local date / time. 4.5.21 Network specific facilities Not applicable. Coding standard: CCITT standardized coding is always used. 4.5.22 Progress indicator

14

MCMC MTSFB TC T009:2014

Table 6. Appendices (continued)

Clause No. Clause Description Recommendation Not applicable. 4.5.29 Transit network selection Transit network selection is implemented in the DSS1 signaling by using operator codes in the called number digits (operator code + called party number). Optional extensions to the basic protocol and exceptions that apply in the case of supplementary services are not subject to Circuit-switched call 5 this guideline document. control procedures An INFORMATION message received in the Release Request State shall be ignored. The network shall recognize both the sending complete 5.1.1 Call request information element and the "#" character. In case (a) the dial tone option with Progress Indicator #8 is 5.1.3 Overlap sending applied Not applicable. 5.1.10 Transit network selection Transit network selection is implemented in the DSS1 signaling by using operator codes in the called number digits (operator code + called party number). It is recommended for the basic access that a timer is implemented on the network side in order to ensure that layer 2 is released if during a time period, (e.g. 10-15 seconds) no layer 3 connections are present on the data link.

In special cases, e.g. NT2, data link connections may be Call establishment at the established as soon as TEI is assigned (either locally or by 5.2 destination interface the automatic assignment procedure), and may be retained indefinitely.

It is recommended that a reset of layer 3 always reset layer 2 in ISDN-terminal equipment. If layer 3 can be reset without resetting layer 2, an ISDN terminal which is reset during the active phase of a call, may lose control over that call. The network shall have the knowledge that a single-point 5.2.1 Incoming call configuration exists, and that information is entered at the time of configuration of the access. SETUP message Only options 1) "channel is indicated, no acceptable 5.2.3.1 delivered by point-to- alternative" and 4) "no B channel available" are used. point data link In overlap receiving the network cannot in all cases determine that sufficient call setup information has been received, and the Sending complete information element is not 5.2.4 Overlap receiving required (Refer to Technical Guidelines of ISDN Supplementary Services (Functional Protocol), DDI).

15

MCMC MTSFB TC T009:2014

Table 6. Appendices (continued)

Clause No. Clause Description Recommendation Receipt of CALL Timer 304 is only used on point-to-point data links, as 5.2.5.2 PROCEEDING and overlap receiving is applicable only on point-to-point ALERTING connections. Concerning the first subsection a) the normal call handling Notification of procedures shall be applied at the terminating exchange 5.2.6 interworking at the (i.e. the terminating exchange shall only through-connect terminating interface. after a CONNECT message has been received from the called user). In case the private exchange has diverted the speech call it is recommended that the Calling party is informed of the diversion (with an announcement) if the private exchange sends the call acceptance message (CONNECT) towards the Calling party before the call acceptance message has been received from the diverted connection. This in-band 5.2.7 Call accept information is given immediately after the call acceptance message sending.

Note: Establishment of the bearer connection prior to call acceptance is described in ETS 300 403-1 Annex K. If this procedure is applied then the inband information is given prior the call acceptance message sending. In order to receive the inband information it is Clearing when recommended that the user connects to the B-channel 5.3.4.1 tones/announcements on receipt of the DISCONNECT message with progress provided indicator No. 8. 5.3.4bis (EN 300 Absence of response In case a B-channel is placed in a maintenance condition, 403-1 during call clearing the actions to be taken are described in subclause 5.5. 11/99) When the call identity is used, it is recommended for the 5.6.1 Call suspension terminals to use IA5-coded characters. When the call identity is used, it is recommended for the 5.6.2 Call suspended terminals to use IA5- coded characters. The network shall preserve the call identity along with a 5.6.5 Call resume errors clearing cause during the period of timer T307. Information element out The network is not required to process information 5.8.5.1 of sequence elements received out of sequence. The BC (Bearer Capability) and HLC (High Layer Duplicated information Compatibility) information elements may be duplicated in the 5.8.5.2 elements SETUP message (EN 300 403-1 (11/99), subclause 5.11 and 5.12).

16

MCMC MTSFB TC T009:2014

Table 6. Appendices (continued)

Clause No. Clause Description Recommendation Non-mandatory Information elements exceeding the maximum length shall 5.8.7.2 information element not be truncated and processed except the call identity content error information element. It is recommended that the network transmits a STATUS 5.8.9 Data link failure ENQUIRY message when layer 2 is re-established. 5.11 Signaling procedures for Supported on ISDN end-to-end connections (i.e. the network bearer capability signaling system is ISUP) selection 5.12 Signaling procedures for Supported on ISDN end-to-end connections (i.e. the network high layer compatibility signaling system is ISUP) selection 8 Circuit-mode multirate (64 kbit/s base rate) Not Applicable procedures 9.1 Timers in the network Timer No. 302 : Time-out value is 5s side 9.2 Timers in the user side Timer No. 301 : Time-out value is 3 min. Annex B Compatibility and

address checking B.1 Introduction Codings of BC, HLC and LLC are subject to the ETR 018 (11/95). B.3.1 Compatibility checking Called party number (whole subscriber number) is with addressing always included in the SETUP message from the network information to user in point-to-multipoint configurations. Compatibility checking with addressing information should be used in terminals, since otherwise it may restrict the use of several terminals in the same access or the use of multi- service terminals. (Further information can be found in the supplementary services guideline document Technical Guidelines of ISDN Supplementary Services (Functional Protocol), e.g. Multiple Subscriber Number supplementary service). B.4 Interworking with When a Progress indicator information element #1 or #3 is existing networks sent to the terminal equipment, the network will not send the High layer or Low layer compatibility information elements to the terminal equipment. The terminal equipment should in this case use compatibility checking only with Addressing Information and Bearer Capability. When the High layer and/or Low layer information elements are sent to the terminal equipment, the terminal equipment shall use them in the compatibility checking.

17

MCMC MTSFB TC T009:2014

Table 6. Appendices (continued)

Clause No. Clause Description Recommendation Transit network ANNEX C Not applicable. selection Extension for symmetric ANNEX D Not applicable call operation Network specific facility ANNEX E Not Applicable selection D-channel backup ANNEX F Not Applicable procedures Low layer compatibility The transport of LLC to the calling user is only supported on ANNEX J negotiation the ISDN end-to-end connections.

4. Terminal Characteristics Related To Access Signaling

Terminal characteristics related to access signaling and used for type approval purposes arecontained in standards ETS 300 085(12/90), ETS 300 087 (4/94), ETS 300 104 (6/94), NET 003 (9/95), NET 005 (9/95), I-ETS 300 245-1 (2/96), TBR 003 (11/95), TBR 003/A1 (2/98), TBR 004 (11/95), TBR 004/A1 (2/98), TBR 008(9/94), TBR 008(10/98), TBR 008/C2 (2/2001) and the corresponding CTRs.

5. Terminal Adaptors

5.1 Circuit Mode Bearer Services

Terminal adaptor functions and associated access signaling requirements for circuit mode bearer services are contained in the standard ETS 300 103 (12/90).

18

MCMC MTSFB TC T009:2014

Annex A (Normative)

Normative references

Erratum1 (02/2003) to ISDN User-Network Interface Layer 3 Specification for Basic Call Control ITU-T Rec. Q.931

ETR 080 Nov 96 Digital transmission system on metallic local lines

ETSI TBR 3 Nov 95 Attachment requirements for terminal equipment to connect to an ISDN using ISDN basic access

ETSI TBR 3 A1 Dec 97 This amendment A1 modifies the TBR 3 (1995)

IEC 60950-1: 2001 Information Technology Equipment – Safety

IEC CISPR 22: 2003-04 Information Technology Equipment – Radio disturbance characteristics – Limits and methods of measurement

ITU-T Rec. I.430 (11/95) Basic User-Network Interface – Layer 1 Specification

ITU-T Rec. Q.921 (09/97) ISDN User-Network Interface – Data Link Layer Specification

ITU-T Rec. Q.921 ISDN User-Network Interface – Data Link Layer Specification Amendment 1 Amendement 1 (02/2000)

[ITU-T Recommandation Integrated Services Digital Network (ISDN): Digital Subscriber Q.931 (1993), modified] (EN Signaling System No. One (DSS1) protocol: Signaling network layer 300 403-1 11/99) for circuit-mode basic call control; Part 1: Protocol Specification

ITU-T Rec. Q.931 ISDN User-Network Interface Layer 3 Specification for Basic Amendement 1 (05/98) Call Control Amendment 1 Extensions for the support of digital multiplexing equipment

ITU-T Rec. G.961 03/93 Digital Transmission System on Metallic Local Lines for ISDN Basic Rate Access

NOTES:

ETSI European Telecommunications Standards Institute ETR ETSI Technical Report IEC International Electro-technical Commission ITU-T International Telecommunication Union – Telecommunication Sector TBR Technical Basis for Regulation

19

MCMC MTSFB TC T009:2014

Annex B (Informative)

Technical Guidelines of ISDN Supplementary Service

B1. Introduction

This document contains clarifications and recommended option selections for the ETSI ISDN standards related to ISDN supplementary services. This document covers the implementation of ISDN supplementary services using functional protocol. The aim of this document is to avoid unnecessary options and vagueness in ISDN implementations and to ensure the interoperability of ISDN networks and terminal equipment in Malaysia.

B2. Supporting Information

B2.1 Integrated Services Digital Network (ISDN); Multiple Subscriber Number (MSN) supplementary service; Service Description (ETS 300 050, October 1991)

B2.2 Integrated Services Digital Network (ISDN); Multiple Subscriber Number (MSN) supplementary service; Functional capabilities and information flows (ETS 300 051, October 1991)

B2.3 Integrated Services Digital Network (ISDN); Multiple Subscriber Number (MSN) supplementary service; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 052-1, October 1991)

B2.4 Integrated Services Digital Network (ISDN); Terminal Portability (TP) supplementary service; Service Description (ETS 300 053, October 1991)

B2.5 Integrated Services Digital Network (ISDN); Terminal Portability (TP) supplementary service; Functional capabilities and information flows (ETS 300 054, October 1991)

B2.6 Integrated Services Digital Network (ISDN); Terminal Portability (TP) supplementary service; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 055-1, October 1991)

B2.7 Integrated Service Digital Network (ISDN); Call Waiting (CW) supplementary service; Service Description (ETS 300 056, October 1991) and Amendment A1 (September 1996)

B2.8 Integrated Services Digital Network (ISDN); Call Waiting (CW) supplementary service; Functional capabilities and information flows (ETS 300 057, May 1992)

B2.9 Integrated Services Digital Network (ISDN); Call Waiting (CW) supplementary service; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 058-1, October 1991)

B2.10 Integrated Services Digital Network (ISDN); Sub-addressing (SUB) supplementary service; Service Description (ETS 300 059, October 1991)

B2.11 Integrated Services Digital Network (ISDN); Sub-addressing (SUB) supplementary service; Functional capabilities and information flows (ETS 300 060, October 1991)

20

MCMC MTSFB TC T009:2014

B2.12 Integrated Services Digital Network (ISDN); Sub-addressing (SUB) supplementary service; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 061-1, October 1991)

B2.13 Integrated Services Digital Network (ISDN); Direct Dialing In (DDI) supplementary service; Service Description (ETS 300 062, October 1991)

B2.14 Integrated Services Digital Network (ISDN); Direct Dialling In (DDI) supplementary service; Functional capabilities and information flows (ETS 300 063, October 1991)

B2.15 Integrated Services Digital Network (ISDN); Direct Dialing In (DDI) supplementary service; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 064-1, October 1991)

B2.16 Integrated Services Digital Network (ISDN); Calling Line Identification Presentation (CLIP) supplementary service; Service description (ETS 300 089, January 1992)

B2.17 Integrated Services Digital Network (ISDN); Calling Line Identification Restriction (CLIR) supplementary service; Service description (ETS 300 090, January 1992)

B2.18 Integrated Services Digital Network (ISDN); Calling Line Identification Presentation (CLIP) and Calling Line Identification Restriction (CLIR) supplementary services; Functional capabilities and information flows (ETS 300 091, March 1992)

B2.19 Integrated Services Digital Network (ISDN); Calling Line Identification Presentation (CLIP) supplementary service; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 092-1, March 1992), Amendment A1 (April 1993) and Amendment A2 (November 1994)

B2.20 Integrated Services Digital Network (ISDN); Calling Line Identification Restriction (CLIR) supplementary service; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 093-1, March 1992)

B2.21 Integrated Services Digital Network (ISDN); Connected Line Identification Presentation (COLP) supplementary service; Service description (ETS 300 094, January 1992)

B2.22 Integrated Services Digital Network (ISDN); Connected Line Identification Restriction (COLR) supplementary service; Service description (ETS 300 095, January 1992)

B2.23 Integrated Services Digital Network (ISDN); Connected Line Identification Presentation (COLP) and Connected Line Identification Restriction (COLR) supplementary services; Functional capabilities and information flows (ETS 300 096, May 1992)

B2.24 Integrated Services Digital Network (ISDN); Connected Line Identification Presentation (COLP) supplementary service; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 097-1, March 1992) and Amendment A1 (November 1994)

B2.25 Integrated Services Digital Network (ISDN); Connected Line Identification Restriction (COLR) supplementary service; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 098-1, May 1992)

B2.26 Integrated Services Digital Network (ISDN); Malicious Call Identification (MCID) supplementary service; Service description (ETS 300 128, May 1992)

21

MCMC MTSFB TC T009:2014

B2.27 Integrated Services Digital Network (ISDN); Malicious Call Identification (MCID) supplementary service; Functional capabilities and information flows (ETS 300 129, May 1992)

B2.28 Integrated Services Digital Network (ISDN); Malicious Call Identification (MCID) supplementary service; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 130-1, May 1992)

B2.29 Integrated Services Digital Network (ISDN); Closed User Group (CUG) supplementary service; Service description (ETS 300 136, March 1992)

B2.30 Integrated Services Digital Network (ISDN); Closed User Group (CUG) supplementary service; Functional capabilities and information flows (ETS 300 137, May 1992)

B2.31 Integrated Services Digital Network (ISDN); Closed User Group (CUG) supplementary service; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 138-1, May 1992) and Amendment A1 (January 1996)

B2.32 Integrated Services Digital Network (ISDN); Call Hold (HOLD) supplementary service; Service description (ETS 300 139, March 1992)

B2.33 Integrated Services Digital Network (ISDN); Call Hold (HOLD) supplementary service; Functional capabilities and information flows (ETS 300 140, May 1992)

B2.34 Integrated Services Digital Network (ISDN); Call Hold (HOLD) supplementary service; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 141-1, May 1992) including Corrigendum (August 1993)

B2.35 Integrated Services Digital Network (ISDN); Advice of Charge: charging information at call set-up time (AOC-S) supplementary service; Service description (ETS 300 178, October 1992)

B2.36 Integrated Services Digital Network (ISDN); Advice of Charge: charging information during the call (AOC-D) supplementary service; Service description (ETS 300 179, October 1992)

B2.37 Integrated Services Digital Network (ISDN); Advice of Charge: charging information at the end of the call (AOC-E) supplementary service; Service description (ETS 300 180, October 1992)

B2.38 Integrated Services Digital Network (ISDN); Advice of Charge (AOC) supplementary service; Functional capabilities and information flows (ETS 300 181, April 1993)

B2.39 Integrated Services Digital Network (ISDN); Advice of Charge (AOC) supplementary service; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 182-1, April 1993)

B2.40 Integrated Services Digital Network (ISDN); Three-Party (3PTY) supplementary service; Service description (ETS 300 186, July 1993)

B2.41 Integrated Services Digital Network (ISDN); Three-Party (3PTY) supplementary service; Functional capabilities and information flows (ETS 300 187, August 1993)

B2.42 Integrated Services Digital Network (ISDN); Three-Party (3PTY) supplementary service; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 188-1, August 1993)

22

MCMC MTSFB TC T009:2014

B2.43 Integrated Services Digital Network (ISDN); Supplementary Service Interactions; Digital Subscriber Signaling System No. one (DSS1) protocol, Part 1: Protocol specification (ETS 300 195- 1, February 1995)

B2.44 Integrated Services Digital Network (ISDN); Generic functional protocol for the support of supplementary services; Digital Subscriber Signaling System No. one (DSS1) protocol (ETS 300 196-1, August 1993) and Amendment A1 (May 1995)

B2.45 Integrated Services Digital Network (ISDN); Call Forwarding Busy (CFB) supplementary service; Service description (ETS 300 199, December 1994)

B2.46 Integrated Services Digital Network (ISDN); Call Forwarding Unconditional (CFU) supplementary service; Service description (ETS 300 200, December 1994)

B2.47 Integrated Services Digital Network (ISDN); Call Forwarding No Reply (CFNR) supplementary service; Service description (ETS 300 201, December 1994) and Amendment A1 (September 1996)

B2.48 Integrated Services Digital Network (ISDN); Call Forwarding Busy (CFB) supplementary service; Functional capabilities and information flows (ETS 300 203, December 1994)

B2.49 Integrated Services Digital Network (ISDN); Call Forwarding Unconditional (CFU) supplementary service; Functional capabilities and information flows (ETS 300 204, December 1994)

B2.50 Integrated Services Digital Network (ISDN); Call Forwarding No Reply (CFNR) supplementary service; Functional capabilities and information flows (ETS 300 205, December 1994)

B2.51 Integrated Services Digital Network (ISDN); Diversion supplementary services; Digital Subscriber Signaling No. one (DSS1) protocol (ETS 300 207-1, December 1994) and Corrigendum (June 1995)

B2.52 Integrated Services Digital Network (ISDN); User-to-user signaling (UUS) supplementary service; Service description (ETS 300 284, March 1996)

B2.53 Integrated Services Digital Network (ISDN); User-to-user signaling (UUS) supplementary service; Functional capabilities and information flows (ETR 285, March 1996)

B2.54 Integrated Services Digital Network (ISDN); User-to-user signaling (UUS) supplementary service; Digital Subscriber Signaling one (DSS1) protocol (ETS 300 286-1, February 1993)

B2.55 Integrated Services Digital Network (ISDN); Explicit Call Transfer (ECT) supplementary service; Service description (EN 300 367, V1.2.1, October 1998)

B2.56 Integrated Services Digital Network (ISDN); Explicit Call Transfer (ECT) supplementary service; Functional capabilities and information flows (EN 300 368, V1.2.2, December 1998)

B2.57 Integrated Services Digital Network (ISDN); Explicit Call Transfer (ECT) supplementary service; Digital Subscriber Signaling one (DSS1) protocol (EN 300 369-1, V1.2.4, October 1998)

23

MCMC MTSFB TC T009:2014

B3. National Option Selections and Clarifications

B3.1 Generic functional protocol for the support of supplementary services

The supplementary services of this specification are based on the functional protocol. Therefore, the public network shall support the generic part of the functional protocol according to ETS 300 196-1 [44].

Only those functions need to be implemented, which are required to support the selected supplementary services. Network options of ETS 300 196-1 are left as implementation options, unless stated otherwise in the Sub clauses relating to the individual supplementary services. Should any conflict arise between ETS 300 196-1 and the specifications in Sub clause 3.2 to 3.16, then the text of the individual supplementary services shall be taken as definitive.

B3.2 Multiple Subscriber Number (MSN)

B3.2.1 Definition

The Multiple Subscriber Number (MSN) supplementary service provides the possibility for assigning multiple numbers to a single public or private access.

NOTE: This allows e.g.:

1) A calling user to select, via the public network, one or multiple distinct terminals out of multiple choices; 2) To identify the terminal to the network for the application of other supplementary services.

B3.2.2 Service Description

The service description (stage 1 description) for the MSN supplementary service is contained in the standard ETS 300 050 [1].

The following gives the recommended guidelines for the implementation of the MSN supplementary service in the Malaysian network.

Clause 5 and sub clause 6.2.3 The multiple subscriber number provided by the calling party shall be the full ISDN subscriber number.

The called party number to be transmitted to the user's installation shall comprise the full ISDN subscriber number Sub clause 6.1 The maximum number of MSNs per access shall be 16. Sub clause 7.2 The MSN supplementary service can apply at an access to a private ISDN (e.g. when the public network does not know what equipment is connected to the access) Clause 8 Supplementary services can be individually assigned to each MSN number. Sub clause 8.9 Subscription to the DDI supplementary service and the MSN supplementary service is mutually exclusive

24

MCMC MTSFB TC T009:2014

Additional requirement

On outgoing calls, when the screening of the calling party number is successful, the CLI to be recorded in the charging record shall be the MSN number provided by the calling party. If the number screening is unsuccessful, the default ISDN number of the access shall be recorded in the charging record

B3.2.3 Functional Capabilities and Information Flows

The functional capabilities and information flows (stage 2 description) for the MSN supplementary service are contained in the standard ETS 300 051 [2]. The stage 2 description can be taken as informative. The implementation of the MSN supplementary service in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

B3.2.4 Digital Subscriber Signaling System No. One (DSS1) Protocol

The DSS1 protocol (stage 3 description) for the MSN supplementary service is contained in the standard ETS 300 052-1 [3].

The following gives the recommended guidelines for the implementation of the MSN supplementary service in the Malaysian network.

Sub clause 6.2 If the access has the MSN supplementary service, the network may use the information in the calling party number information element to identify the calling terminal, and, if necessary, the appropriate basic or supplementary service Sub clause 9.2.1 The type of number indicated in the Called party number information element sent to the user shall be coded as "subscriber number" and the full appropriate number shall be sent.

The "numbering plan identification" field of the Called party number information element shall be coded "ISDN/telephony numbering plan" (ITU-T Recommendation E.164). Sub clause 9.3.1 All the coding options provided in this sub clause shall be implemented in the network.

It is recommended that the type of number indicated in the Calling party number information element sent to the network shall be coded as "subscriber number" and the full appropriate number shall be sent.

B3.3 Terminal Portability (TP)

B3.3.1 Definition

The Terminal Portability (TP) supplementary service allows a user to move a terminal from one socket to another within one given basic access during the active state of a call. It also allows a user to move a call from one terminal to another terminal within one given basic access during the active phase of the call.

25

MCMC MTSFB TC T009:2014

B3.3.2 Service Description

The service description (stage 1 description) for the TP supplementary service is contained in the standard ETS 300 053 [4].

The following gives the recommended guidelines for the implementation of the TP supplementary service in the Malaysian network.

Sub clause 8.1.2 At call suspension request, the cumulative information (i.e. total charge incurred up to the moment when the call is suspended) shall be given.

On resumption of the call, the sending of charging information shall start again and the updated cumulative charging information shall be given.

If the call is cleared while the call is suspended at the calling user's access, and if the calling user attempts to resume the call within the timer, then, advice of charge information shall be given to the user at the time of the resume attempt. Sub clause 8.1.3 If the call is cleared while the call is suspended at the calling user's access, and if the calling user attempts to resume the call within the timer, then advice of charge information can be given to the user at the time of the resume attempt

B3.3.3 Functional Capabilities and Information Flows

The functional capabilities and information flows (stage 2 description) for the TP supplementary service are contained in the standard ETS 300 054 [5]. The stage 2 description can be taken as informative. The implementation of the TP supplementary service in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

B3.3.4 Digital Subscriber Signaling System No. One (DSS1) Protocol

The DSS1 protocol (stage 3 description) for the TP supplementary service is contained in the standard ETS 300 055-1 [6]. The TP supplementary service is implemented in the Malaysian network without national definitions or exceptions.

B3.4 Call Waiting (CW)

B3.4.1 Definition

The Call Waiting (CW) supplementary service allows a user to be informed of an incoming call (as per basic call procedures) with an indication that no interface information channel is available. The user then has the choice of accepting, rejecting or ignoring the waiting call (as per basic call procedures).

26

MCMC MTSFB TC T009:2014

B3.4.2 Service Description

The service description (stage 1 description) for the CW supplementary service is contained in the standard ETS 300 056 [7].

The following gives the recommended guidelines for the implementation of the CW supplementary service in the Malaysian network.

Clause 3 and sub clause 6.1 No specific time-out T2 will be used for no answer situation. Basic call timer shall apply in this Case. Clause 5 On the primary rate access, only notifications for the CW supplementary service are supported.

The maximum number of calls that the network must be able to handle (e.g. active, held, alerting, waiting) on the basic access is six (6). Sub clause 6.1 The network will support the subscription option presented in Table 1.

The network will support value two (2) for the network provider option in Table 2. This is specified for all ISDN numbers on the basic access. Sub clause 7.1 In interworking cases with non-ISDNs, no special in-band indication will be provided to the calling user.

B3.4.3 Functional Capabilities and Information Flows

The functional capabilities and information flows (stage 2 description) for the CW supplementary service are contained in the standard ETS 300 057 [8]. The stage 2 description can be taken as informative. The implementation of the CW supplementary service in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

B3.4.4 Digital Subscriber Signaling System No. One (DSS1) Protocol

The DSS1 protocol (stage 3 description) for the CW supplementary service is contained in the standard ETS 300 058-1 [9].

The following gives the recommended guidelines for the implementation of the CW supplementary service in the Malaysian network.

Sub clauses 9.5.1.1, 9.5.2, 9.6.1 and 9.6.2, and In the network side the basic call timer T301 is clauses 13 and 14 used.

27

MCMC MTSFB TC T009:2014

B3.5 Sub addressing (SUB)

B3.5.1 Definition

The Sub addressing (SUB) supplementary service allows the called (served) user to expand his addressing capacity beyond the one given by the ISDN number.

B3.5.2 Service Description

The service description (stage 1 description) for the SUB supplementary service is contained in the standard ETS 300 059 [10].

The following gives the recommended guidelines for the implementation of the SUB supplementary service in the Malaysian network.

Sub clause 5.1 The 20 octets maximum size of is applied.

B3.5.3 Functional Capabilities and Information Flows

The functional capabilities and information flows (stage 2 description) for the SUB supplementary service are contained in the standard ETS 300 060 [11]. The stage 2 description can be taken as informative. The implementation of the SUB supplementary service in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

B3.5.4 Digital Subscriber Signaling System No. One (DSS1) Protocol

The DSS1 protocol (stage 3 description) for the SUB supplementary service is contained in the standard ETS 300 061-1 [12].

The following gives the recommended guidelines for the implementation of the SUB supplementary service in the Malaysian network.

Clause 5, note 2 The 20 octets maximum size of the sub address is applied.

B3.6 Direct Dialing In (DDI)

B3.6.1 Definition

The DDI supplementary service enables a user to call directly via a public ISDN a user on a private ISDN by using the public ISDN numbering plan.

28

MCMC MTSFB TC T009:2014

B3.6.2 Service Description

The service description (stage 1 description) for the DDI supplementary service is contained in the standard ETS 300 062 [13].

The following gives the recommended guidelines for the implementation of the DDI supplementary service in Malaysian network.

Clause 5 The number of digits is defined on a per subscriber basis. Sub clauses 8.5.1 and 8.5.3 A special arrangement for not screening the user provided number may be applied. For network wide operation ISUP version 2 is required. Sub clause 8.12 If the DDI supplementary service is provided to the served user of the MCID supplementary service, then the MCID supplementary service shall be provided globally for the whole access. The network option on provision for specific ISDN numbers forming part of the DDI supplementary service is not supported. Sub clause 8.13 The subscription to the DDI supplementary service and the Multiple Subscriber Number (MSN) supplementary service is mutually exclusive.

B3.6.3 Functional Capabilities and Information Flows

The functional capabilities and information flows (stage 2 description) for the DDI supplementary service are contained in the standard ETS 300 063 [14]. The stage 2 description can be taken as informative. The implementation of the DDI supplementary service in Malaysian network shall be based on the stage 1 and stage 3 descriptions.

B3.6.4 Digital Subscriber Signaling System No. One (DSS1) Protocol

The DSS1 protocol (stage 3 description) for the DDI supplementary service is contained in the standard ETS 300 064-1 [15].

The following gives the recommended guidelines for the implementation of the DDI supplementary service in Malaysian network.

Sub clause 6.1, note The subscription to the DDI supplementary service and the Multiple Subscriber Number (MSN) supplementary service is mutually exclusive

B3.7 Calling Line Identification Presentation (CLIP) and Calling Line Identification Restriction (CLIR)

B3.7.1 Definition

The CLIP supplementary service provides the called party with the possibility of receiving identification of the calling party.

The CLIR supplementary service enables the calling party to prevent presentation of its ISDN number to the called party.

29

MCMC MTSFB TC T009:2014

B3.7.2 Service Description

CLIP:

The service description (stage 1 description) for the CLIP supplementary service is contained in the standard ETS 300 089 [16].

The following gives the recommended guidelines for the implementation of the CLIP supplementary service in Malaysian network.

Sub clauses 6.1, 6.2.3.1, In case of two calling party number delivery option a special arrangement for 7.2, 8.9 and 8.13 not screening the user provided number may be applied. For network wide operation ISUP version 2 is required. Sub clause 7.1 The CLIP supplementary service is always applicable when interworking to non-ISDN has occurred.

The calling line identity can be provided to called user in the ISDN if the identity has been received and it is known that presentation is not restricted.

On calls to or via non-ISDN, the originating network may restrict calling line identity from being forwarded to the destination network when the CLIR supplementary service is applicable (see also ETS 300 090, sub clause 7.1). Sub clause 8.5.2 Technical capabilities to provide override category service have to be available in Malaysian network. Annex A The two calling party number delivery option is applicable. For network wide operation ISUP version 2 is required.

CLIR:

The service description (stage 1 description) for the CLIR supplementary service is contained in the standard ETS 300 090 [17].

The following gives the recommended guidelines for the implementation of the CLIR supplementary service in the Malaysian network. Clause 3, and sub clauses Technical capabilities to provide override category service have to be 6.2.3.2 (note 1) and 8.5.1 available in the Malaysian network. Sub clause 6.1 Both subscription options, permanent mode and temporary mode (defaults presentation restricted and presentation not restricted), are offered. Sub clause 7.1 On calls to or via non-ISDNs, it cannot be assured that a restriction indication can be carried to the destination network. The originating network in Malaysia may restrict any information identifying the calling user from being forwarded to the destination network when the CLIR supplementary service is applicable

30

MCMC MTSFB TC T009:2014

B3.7.3 Functional Capabilities and Information Flows

The functional capabilities and information flows (stage 2 description) for the CLIP and CLIR supplementary services are contained in the standard ETS 300 091 [18]. The stage 2 description can be taken as informative. The implementation of the CLIP and CLIR supplementary services in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

B3.7.4 Digital Subscriber Signaling System No. One (DSS1) Protocol

CLIP:

The DSS1 protocol (stage 3 description) for the CLIP supplementary service is contained in the standard ETS 300 092-1 [19].

The following gives the recommended guidelines for the implementation of the CLIP supplementary service in the Malaysian network.

Sub clauses 6.2 and 9.4 In case of two calling party number delivery option a special arrangement for not screening the user provided number may be applied. For network wide operation ISUP version 2 is required. Sub clause 9.2.1 It is recommended for the coding of the calling party information element sent by the calling user:

-The "numbering plan identification" field shall be coded "ISDN/Telephony numbering plan".

In case DDI is not activated for the same access:

- The "type of number" field shall be coded "subscriber number" and the full ISDN subscriber number shall be sent.

In case DDI is activated for the same access:

- The "type of number" field shall be coded "unknown" and only the extension number of the calling party shall be sent. The network then completes the calling party number by adding the national number of the access to the calling party number information element. Sub clause 9.3.1 Networks in Malaysia may accept a full ISDN number in a Calling party number information element with the addition of a prefix or escape digits to the number digits field and the type of number field set to "National Number". Sub clause 9.5.1 and The coding of the calling party information element sent by the destination Table 1, note 7 local exchange:

- The "numbering plan identification" field shall be coded "ISDN/Telephony numbering plan";

- The "type of number" field shall be coded “unknown", and the number is organized according to the network dialing plan.

31

MCMC MTSFB TC T009:2014

Clause 11 The following option is according to the network rules and operations in Malaysia: - The network shall send the Calling party number information element according to sub clause9.5.1 fifth paragraph and shall include no Calling party sub address information element. Annex B The two Calling party number information elements delivery option is applicable. For network wide operation ISUP version 2 is required.

CLIR:

The DSS1 protocol (stage 3 description) for the CLIR supplementary service is contained in the standard ETS 300 093-1 [20]. The following gives the recommended guidelines for the implementation of the CLIR supplementary service in the Malaysian network.

Clause 11 On calls to or via non-ISDNs, the originating network may restrict calling line identity from being forwarded to the destination network when the CLIR supplementary service is applicable.

B3.8 Connected Line Identification Presentation (COLP) and Connected Line Identification Restriction (COLR)

B3.8.1 Definition

The COLP supplementary service provides the calling party with the possibility to receive identification of the connected party.

The COLR supplementary service enables the connected party to prevent presentation of its ISDN number to the calling party.

B3.8.2 Service Description

COLP:

The service description (stage 1 description) for the COLP supplementary service is contained in the standard ETS 300 094 [21].

The following gives the recommended guidelines for the implementation of the COLP supplementary service in the Malaysian network.

Sub clauses 6.1, 6.2.3.1, 7.2, 8.9 and 8.13 A special arrangement for not screening the user provided number may be applied. For network wide operation ISUP version 2 is required. Sub clause 7.1 The use of the COLP supplementary service can be guaranteed only when the call is end-to end ISDN. Sub clauses 8.5.4 and 8.10 Technical capabilities to provide override category service have to be available in ;the Malaysian network

32

MCMC MTSFB TC T009:2014

COLR:

The service description (stage 1 description) for the COLR supplementary service is contained in the standard ETS 300 095 [22].

The following gives the recommended guidelines for the implementation of the COLR supplementary service in the Malaysian network.

Clause 3, and sub clauses Technical capabilities to provide override category service have 6.2.3.2, 8.5.3 and 8.10 to be available in the Malaysian network Sub clause 6.1 Both subscription options, permanent mode and temporary mode (defaults: presentation restricted and presentation not restricted), are offered. Sub clause 7.1 Destination network in Malaysia may restrict any information identifying the connected party from being returned to the originating network when the COLR supplementary service has been invoked.

B3.8.3 Functional Capabilities and Information Flows

The functional capabilities and information flows (stage 2 description) for the COLP and COLR supplementary services are contained in the standard ETS 300 096 [23]. The stage 2 description can be taken as informative. The implementation of the COLP and COLR supplementary services in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

B3.8.4 Digital Subscriber Signaling System No. One (DSS1) Protocol

COLP:

The DSS1 protocol (stage 3 description) for the COLP supplementary service is contained in the standard ETS 300 097-1 [24].

The following gives the recommended guidelines for the implementation of the COLP supplementary service in the Malaysian network.

Sub clauses 6.3 and 9.4 A special arrangement for not screening the user provided number may be applied. For network wide operation ISUP version 2 is required.

Sub clause 9.2.1 It is recommended for the coding of the connected party information element sent by the connected user:

- The "numbering plan identification" field shall be coded "ISDN/Telephony numbering plan";

- The "type of number" field shall be coded "subscriber number" and the full ISDN subscriber number shall be sent.

33

MCMC MTSFB TC T009:2014

Sub clause 9.3.1 Networks in Malaysia may accept a full ISDN number in a Connected party number information element with the addition of a prefix or escape digits to the number digits field and the type of number field set to "National Number". Sub clause 9.5.1 and The coding of the connected party information element sent by the Table 1, note 7 originating local exchange: - The "numbering plan identification" field shall be coded "ISDN/Telephony numbering plan"; - The "type of number" field shall be coded "unknown", and the number is organized according to the network dialing plan.

COLR:

The DSS1 protocol (stage 3 description) for the COLR supplementary service is contained in the standard ETS 300 098-1 [25].

The following gives the recommended guidelines for the implementation of the COLR supplementary service in the Malaysian network.

Clause 11 Destination network in Malaysia may restrict any information identifying the connected party from being returned to the originating network when the COLR supplementary service has been invoked.

B3.9 Malicious Call Identification (MCID)

B3.9.1 Definition

The MCID supplementary service enables a user to request that the source of an incoming call is identified and registered by the network.

B3.9.2 Service Description

The service description (stage 1 description) for the MCID supplementary service is contained in the standard ETS 300 128 [26].

The following gives the recommended guidelines for the implementation of the MCID supplementary service in the Malaysian network.

Clause 5 The network will support the registration of calling party sub address. Sub clauses 5, 6.1 The network will not support the automatic invocation of the service on and 6.2.3 unanswered calls. Sub clause 6.2.3 The network will not support the continuation of the call to be presented after the calling user has cleared. Sub clause 7.1 When interworking between the PSTN and the ISDN occurs and if the number of the calling user is not available, the network will support the option of registering information about the routing of the call.

The option in the note is not supported.

34

MCMC MTSFB TC T009:2014

Sub clause 8.9 The network will not provide the service for specific ISDN numbers forming part of the DDI supplementary service. Sub clauses 8.10.1, The network will support the registration of the last diverting user. 8.10.2 and 8.10.3 Sub clause 8.11 The network will not support the registration of the called free phone number

B3.9.3 Functional Capabilities and Information Flows

The functional capabilities and information flows (stage 2 description) for the MCID supplementary service are contained in the standard ETS 300 129 [27]. The stage 2 description can be taken as informative. The implementation of the MCID supplementary service in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

B3.9.4 Digital Subscriber Signaling System No. One (DSS1) Protocol

The DSS1 protocol (stage 3 description) for the MCID supplementary service is contained in the standard ETS 300 130-1 [28].

The following gives the recommended guidelines for the implementation of the MCID supplementary service in the Malaysian network.

Clause 3 The call information shall include the calling party sub address, if provided by the calling user.

B3.10 Closed User Group (CUG)

B3.10.1 Definition

The CUG supplementary service enables users to form groups to and from which access is restricted. A specific user may be a member of one or more closed user groups. Members of a specific closed user group can communicate among themselves but not, in general, with users outside the group.

B3.10.2 Service Description

The service description (stage 1 description) for the CUG supplementary service is contained in the standard ETS 300 136 [29].

The following gives the recommended guidelines for the implementation of the CUG supplementary service in the Malaysian network.

Sub clause 6.1 The maximum number of closed user groups which can be allocated to an individual user is 75. All the subscription options defined in this Sub clause are supported.

35

MCMC MTSFB TC T009:2014

B3.10.3 Functional Capabilities and Information Flows

The functional capabilities and information flows (stage 2 description) for the CUG supplementary service are contained in the standard ETS 300 137 [30]. The stage 2 description can be taken as informative. The implementation of the CUG supplementary service in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

B3.10.4 Digital Subscriber Signaling System No. One (DSS1) Protocol

The DSS1 protocol (stage 3 description) for the CUG supplementary service is contained in the standard ETS 300 138-1 [31].

The following gives the recommended guidelines for the implementation of the CUG supplementary service in the Malaysian network.

Sub clause 6.1 All the subscription options defined in this Sub clause are supported. Sub clause 9.2.4.1 b) The return error component shall be retained along with the ETS 300 403-1 cause.

B3.11 Call Hold (HOLD)

B3.11.1Definition

The HOLD supplementary service allows a user to interrupt communications on an existing call and then subsequently, if desired, re-establish communications.

B3.11.2 Service Description

The service description (stage 1 description) for the HOLD supplementary service is contained in the standard ETS 300 139 [32].

The following gives the recommended guidelines for the implementation of the HOLD supplementary service in the Malaysian network.

Clause 5 On the primary rate access, only notifications for the HOLD supplementary service are supported. Sub clause 6.2.3.1 The network may support the option: A call can be placed on hold after the call has been offered to the called user.

The sending of notifications to the remote user is supported. Sub clause 6.2.3.2 The sending of notifications to the remote user is supported. Sub clause 7.1, note If a remote user is a PSTN user, the notifications about the hold request or retrieve request of the call to that user are not supported. The last sentence of the note is not applicable.

36

MCMC MTSFB TC T009:2014

B3.11.3 Functional Capabilities and Information Flows

The functional capabilities and information flows (stage 2 description) for the HOLD supplementary service are contained in the standard ETS 300 140 [33]. The stage 2 description can be taken as informative. The implementation of the HOLD supplementary service in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

B3.11.4 Digital Subscriber Signaling System No. One (DSS1) Protocol

The DSS1 protocol (stage 3 description) for the HOLD supplementary service is contained in the standard ETS 300 141-1 [34]. The following gives the recommended guidelines for the implementation of the HOLD supplementary service in the Malaysian network. Clause 9, and Sub clauses 9.1.1, 9.2.1 and 9.4.1

The user A at the originating side can hold a call in the Call Delivered state (U4).

B3.12 Advice of Charge (AOC)

B3.12.1 Definition

Advice of Charge (AOC) is a group of supplementary services allowing the served user to be informed of usage-based charging information.

The AOC group of supplementary services includes the following:

AOC-S Advice of Charge, charging information at call set-up time; AOC-D Advice of Charge, charging information during the call; AOC-E Advice of Charge, charging information at the end of a call.

B3.12.2 Service Description

AOC-S:

The service description (stage 1 description) for the AOC-S supplementary service is contained in the standard ETS 300 178 [35].

The following gives the recommended guidelines for the implementation of the AOC-S supplementary service in the Malaysian network.

Clause 5 The AOC-S supplementary service is applicable only in relation to time tariff setting at call establishment and time tariff changes. Sub clause 8.16 No charging information for the use of the Three-Party supplementary service can be sent to the served user.

37

MCMC MTSFB TC T009:2014

AOC-D:

The service description (stage 1 description) for the AOC-D supplementary service is contained in the standard ETS 300 179 [36].

The following gives the recommended guidelines for the implementation of the AOC-D supplementary service in the Malaysian network.

Sub clause 6.2.3 The value of the timer t shall be 10 seconds. Sub clause 8.15 The cumulative charging information is given in all the described cases: at the suspension request, on the resumption of the call, and if the call is terminated while the call is suspended at the calling user's access and the calling user attempts to resume the call within the timer Sub clause 8.16 No charging information for the use of the Three-Party supplementary service can be sent to the served user. Annex A, Sub clause A.2.1 The Malaysian network may not include some charges, e.g. charges incurred by the use of some supplementary services, in the subtotal charges and/or the total charges. Annex A, Sub clause A.3 Charging information (AOC) can be given in currency units or metering pulses according to access arrangements

AOC-E:

The service description (stage 1 description) for the AOC-E supplementary service is contained in the standard ETS 300 180 [37].

The following gives the recommended guidelines for the implementation of the AOC-E supplementary service in the Malaysian network.

Sub clause 8.4 After a call has been transferred and the transferring user is charged for that transferred part of the call, and the AOC-E supplementary service has been invoked for that call, then the charging information shall be sent to the transferring user when the call is terminated. Sub clauses 8.10.1, 8.10.2 Forwarding user: and 8.10.3 When a call is forwarded and the forwarding user is charged for the forwarded part of the call, then the charging information shall be sent to the forwarding user when the call is terminated provided that the served user has subscribed to the AOC-E supplementary service with the value of the subscription option set to "for all calls automatically". Sub clause 8.15 If the call is terminated while the call is suspended at the calling user's access, and if the calling user attempts to resume the call within the timer, then advice of charge information shall be given to that user at the time of the resume attempt. Sub clause 8.16 No charging information for the use of the Three-Party supplementary service can be sent to the served user.

38

MCMC MTSFB TC T009:2014

Annex A, Sub clause A.2.1 The Malaysian network may not include some charges, e.g. charges incurred by the use of some supplementary services, in the subtotal charges and/or the total charges. Annex A, Sub clause A.3 Charging information (AOC) can be given in currency units or metering pulses according to access arrangements.

B3.12.3 Functional Capabilities and Information Flows

The functional capabilities and information flows (stage 2 description) for the AOC supplementary service are contained in the standard ETS 300 181 [38]. The stage 2 description can be taken as informative. The implementation of the AOC supplementary service in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

B3.12.4 Digital Subscriber Signaling System No. One (DSS1) Protocol

The DSS1 protocol (stage 3 description) for the AOC supplementary service is contained in the standard ETS 300 182-1 [39]. The AOC supplementary service is implemented in the Malaysian network without national definitions or exceptions.

B3.13 Three Party (3PTY)

B3.13.1 Definition

The 3PTY supplementary service enables a user to establish, participate in and control, a three- way conversation, i.e. a simultaneous communication involving the served user and two remote parties.

B3.13.2 Service Description

The service description (stage 1 description) for the 3PTY supplementary service is contained in the standard ETS 300 186 [40].

The following gives the recommended guidelines for the implementation of the 3PTY supplementary service in the Malaysian network.

Sub clause 6.2.3.1 Establishing a three-way conversation that would include calls which are not intended for speech communication is not prevented. Sub clauses 8.1.1, 8.1.2 No charging information for the use of the Three-Party supplementary service and 8.1.3 can be sent to the served user. Sub clause 8.16 A remote party in a three-way conversation can invoke the 3PTY supplementary service in order to make their connection to the three-way conversation a part of another three-way conversation controlled by that remote party.

B3.13.3 Functional Capabilities and Information Flows

The functional capabilities and information flows (stage 2 description) for the 3PTY supplementary service are contained in the standard ETS 300 187 [41]. The stage 2 description can be taken as informative. The implementation of the 3PTY supplementary service in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

39

MCMC MTSFB TC T009:2014

B3.13.4 Digital Subscriber Signaling System No. One (DSS1) Protocol

The DSS1 protocol (stage 3 description) for the 3PTY supplementary service is contained in the standard ETS 300 188-1 [42]. The 3PTY supplementary service is implemented in the Malaysian network without national definitions or exceptions.

B3.14 Call Forwarding (CFB, CFU, CFNR)

B3.14.1B Definition

The Call Forwarding supplementary services comprise the following services: -Call Forwarding Busy (CFB); -Call Forwarding Unconditional (CFU); -Call Forwarding No Reply (CFNR).

The CFB supplementary service enables a served user to have the network redirect to another user calls which are addressed to the served user´s ISDN number and meet busy.

The CFU supplementary service enables a served user to have the network redirect to another user calls which are addressed to the served user´s ISDN number. The CFNR supplementary service enables a served user to have the network redirect to another user call which are addressed to the served user´s ISDN number, and for which the connection is not established within a defined period of time.

B3.14.2 Service Description

CFB:

The service description (stage 1 description) for the CFB supplementary service is contained in the standard ETS 300 199 [45].

The following gives the recommended guidelines for the implementation of the CFB supplementary service in the Malaysian network.

Clause 5 and Sub clause 6.2.3 The maximum number for call diversions is 5 for each call. Sub clause 7.1 Once a call has been forwarded to a non-ISDN network the indication call forwarded is used.

Once a call arrives at an ISDN network from a non-ISDN network with the indication forwarded call the call forwarding counter will be set to one, if no other value for the call forwarding counter is supplied. Sub clause 8.17 Forwarding any UUI or request for UUS may be restricted to forwarding users who subscribe to the relevant parts of the UUS supplementary service.

40

MCMC MTSFB TC T009:2014

CFU:

The service description (stage 1 description) for the CFU supplementary service is contained in the standard ETS 300 200 [46].

The following gives the recommended guidelines for the implementation of the CFU supplementary service in the Malaysian network.

Clause 5 and Sub clause 6.2.3 The maximum number for call diversions is 5 for each call. Sub clause 7.1 Once a call has been forwarded to a non-ISDN network the indication call forwarded is used.

Once a call arrives at an ISDN network from a non-ISDN network with the indication forwarded call the call forwarding counter will be set to one, if no other value for the call forwarding counter is supplied. Sub clause 8.17 Forwarding any UUI or request for UUS may be restricted to forwarding users who subscribe to the relevant parts of the UUS supplementary service.

CFNR:

The service description (stage 1 description) for the CFNR supplementary service is contained in the standard ETS 300 201 [47].

The following gives the recommended guidelines for the implementation of the CFNR supplementary service in the Malaysian network.

Clause 5 and Sub clause 6.2.3 The maximum number for call diversions is 5 for each call. Sub clause 6.1 The value of 30 seconds will be used for the no reply timer. Sub clauses 6.2.3.1 and 6.3.3 The method b) is used. The call to the served user will be cleared when the CFNR supplementary service is invoked. If the forwarded call cannot be completed the call shall be terminated. Sub clause 7.1 Once a call has been forwarded to a non-ISDN network the indication call forwarded is used.

Once a call arrives at an ISDN network from a non-ISDN network with the indication forwarded call the call forwarding counter will be set to one, if no other value for the call forwarding counter is supplied.

41

MCMC MTSFB TC T009:2014

Sub clause 8.17 Forwarding any UUI or request for UUS may be restricted to forwarding users who subscribe to the relevant parts of the UUS supplementary service.

If the calling user requests service 1 and indicates that it is not required on the call, then if the called user has explicitly accepted the request, the request for the call forwarding no reply supplementary service will be rejected and the call shall not be forwarded. Annex A The following service provider option in the note is supported: the request for the call forwarding no reply supplementary service will be rejected and the call will not be forwarded.

B3.14.3 Functional Capabilities and Information Flows

CFB:

The functional capabilities and information flows (stage 2 description) for the CFB supplementary services are contained in the standard ETS 300 203 [48]. The stage 2 description can be taken as informative. The implementation of the CFB supplementary service in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

CFU:

The functional capabilities and information flows (stage 2 description) for the CFU supplementary services are contained in the standard ETS 300 204 [49]. The stage 2 description can be taken as informative. The implementation of the CFU supplementary service in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

CFNR:

The functional capabilities and information flows (stage 2 description) for the CFNR supplementary services are contained in the standard ETS 300 205 [50]. The stage 2 description can be taken as informative. The implementation of the CFNR supplementary service in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

B3.14.4 Digital Subscriber Signaling System No. One (DSS1) Protocol

The DSS1 protocol (stage 3 description) for the Call Forwarding supplementary services is contained in the standard ETS 300 207-1 [51].

The following gives the recommended guidelines for the implementation of the Call Forwarding supplementary services in the Malaysian network.

Clause 5 The diversion supplementary services are provided on a per ISDN number basis.

The call forwarding services can be subscribed collectively for all the basic services to which the user(s) subscribes.

42

MCMC MTSFB TC T009:2014

Sub clause 6.1 The subscription options listed in the table 1 are provided.

In the table 2 the following network provider option values are applicable:

-served user call is cleared on invocation of diversion; -maximum number of diversions for a single call is 5; -call forwarding on no reply timer value is 20 s; -partial rerouting is provided at the T reference point. Sub clause 9.1.1.1 The forwarding exchange shall verify the forwarded-to number only for a limited set of numbers; the minimum requirement is that emergency numbers are not accepted as forwarded to numbers Sub clauses 9.2.3.1 and The type of the number shall be set to "unknown" and the number is 9.2.5.1 organized according to the network dialing plan. Sub clause 9.2.4.4.1 and The value of T-CFNR is 20 s. clause 13 Sub clause 9.2.4.4.1 The network provider option "served user call retention on invocation of diversion" is "clear call on invocation" Sub clauses 10.4.1 and If a diverted call is presented from a private network to the public network, 10.5.1 then the public network is required to check the redirecting number from the SETUP message. The number shall be checked against the numbering space of the private network. In case of a mismatch the redirecting number shall be replaced by the default number associated with the private network.

It is recommended for the coding of the redirecting number information sent by the private network: The "numbering plan identification" field shall be coded "ISDN/Telephony numbering plan". In case DDI is not activated for the same access: The "type of number" field shall be coded "subscriber number" and the full ISDN subscriber number shall be sent.

In case DDI is activated for the same access: -The "type of number" field shall be coded "unknown" and only the extension number of the redirecting number shall be sent. The network then completes the redirecting number by adding the national number of the access to the redirecting number information. Sub clause 10.5.1 The public network shall clear the call towards the private network on acceptance of the call rerouting request.

43

MCMC MTSFB TC T009:2014

B3.15 User-to-User Signaling (UUS)

B3.15.1 Definition

The UUS supplementary service enables a user to send/receive a limited amount of information to/from another user over the signaling channel in association with a call to the other user. This information shall be passed transparently (i.e. without modification of contents) through the network. The network shall not interpret or act upon this information.

The user can transfer UUI in different phases of the call depending on the service(s) to which the user subscribes. These services are:

a) Service 1 - User-to-user information exchanged during the set-up and clearing phases of a call/connection, by transporting the User-to-user information element within call/connection control messages; b) Service 2 - User-to user information exchanged from the sender’s point of view during call/connection establishment, between the ALERTING and CONNECT messages, within USER INFORMATION messages; and c) Service 3 - User-to-user information exchanged while a call/connection is in the Active state, within USER INFORMATION messages.

B3.15.2 Service Description

The service description (stage 1 description) for the UUS supplementary service is contained in the standard ETS 300 284 [52].

The following gives the recommended guidelines for the implementation of the UUS supplementary service in the Malaysian network.

Clause 5 Service provider option for service 2, UUI sent by the calling user prior to receiving the acceptance of the call by the called user may be delivered to the called user after the call has been established, is supported.

Note on limitation of UUI to only 32 octets during an interim period of time is not applicable for the Malaysian network. Sub clause 6.1 Service provider option about provision of one or any combination of services is supported. Service provider option about withdrawal separately per service is supported. Sub clause 6.2.1.3 Service provider option about activation of service 3 by the called user after the connection has been established is supported. Sub clause 6.3.3 In case of excessive UUI length the sending user shall be informed. Clause 7 Service provider option about explicit acceptance, if the remote user replies with UUI to explicit request sent to an ISDN only supporting implicit requests, is supported.

44

MCMC MTSFB TC T009:2014

Sub clauses 8.10.1, Forwarding any UUI or request for UUS may be restricted to forwarding users 8.10.2 and 8.10.3 who subscribe to the relevant parts of the UUS supplementary service. Sub clause 8.10.3 If the calling user requests service 1 and indicates that it is not required on the call, then if the called user has explicitly accepted the request, the request for the call forwarding no reply supplementary service will be rejected and the call shall not be forwarded. Annex A The following service provider option in the note is supported: the request for the call forwarding no reply supplementary service will be rejected and the call will not be forwarded.

B3.15.3 Functional Capabilities and Information Flows

The functional capabilities and information flows (stage 2 description) for the UUS supplementary service are contained in the standard ETR 285 [53]. The stage 2 description can be taken as informative. The implementation of the UUS supplementary service in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

B3.15.4 Digital Subscriber Signaling System No. One (DSS1) Protocol

The DSS1 protocol (stage 3 description) for the UUS supplementary service is contained in the standard ETS 300 286-1 [54].

The following gives the recommended guidelines for the implementation of the UUS supplementary service in the Malaysian network.

Sub clause 6.1 Any combination of the following possibilities can be provided separately or globally: -service 1 implicit, or service 1 implicit together with service 1 explicit; -service 2; -service 3. Sub clauses 9.2.2.1 The calling network shall accept the first two USER INFORMATION messages and 9.2.2.2 from the calling user and the calling network shall deliver them to the called user after the calling and called network have entered the Active (N10) call state. Sub clause 9.2.2.2 The calling network shall send a STATUS message with cause #43 to the calling user when discarding the USER INFORMATION message.

The called network shall send a STATUS message with cause #43 to the called user when discarding the USER INFORMATION message. Sub clause 9.3.1.2.1 During the Active (U10) call state, the calling user or the called user can activate service 3. Sub clause 9.3.2.2 The sending network shall send a STATUS message with cause #43 to the sending user when discarding the USER INFORMATION message.

45

MCMC MTSFB TC T009:2014

B3.16 Explicit Call Transfer (ECT)

B3.16.1 Definition

The ECT supplementary service enables a user (user A) to transform two of that user’s calls (an active call and a held call), each of which can be an incoming call or an outgoing call, into a new call between user B and user C.

B3.16.2 Service Description

The service description (stage 1 description) for the ECT supplementary service is contained in the standard ETS 300 367 [55].

The following gives the recommended guidelines for the implementation of the ECT supplementary service in the Malaysian network.

Clause 5 and Sub The service provider option, that the ECT supplementary service can be clause 6.2.3 invoked after user C has been informed of the call (i.e. an outgoing call from A to user C, where the connection has not yet been established), is supported. Sub clause 8.1.3 When the call is transferred and the transferring user is charged for the transferred part of the call, then the charging information shall be sent to the transferring user when the transferred call is terminated provided that the served user has activated the AOC-E supplementary service for that call.

B3.16.3 Functional Capabilities and Information Flows

The functional capabilities and information flows (stage 2 description) for the ECT supplementary service are contained in the standard ETS 300 368 [56]. The stage 2 description can be taken as informative. The implementation of the ECT supplementary service in the Malaysian network shall be based on the stage 1 and stage 3 descriptions.

B3.16.4 Digital Subscriber Signaling System No. One (DSS1) Protocol

The DSS1 protocol (stage 3 description) for the ECT supplementary service is contained in the standard ETS 300 369-1 [57].

The following gives the recommended guidelines for the implementation of the ECT supplementary service in the Malaysian network.

Clause 5 and Sub clause 9.2.5 The network option to allow the invocation of the ECT service when one of the calls is an outgoing call in the Call delivered (alerting) state is supported. Sub clause 9.2 The explicit linkage procedure is supported. Sub clause 10.3 The “mechanism to avoid looping of uncontrolled circuits” is supported by the public network. If the loop prevention procedure cannot decide whether the resulting connection would result in a loop, the call transfer is completed. The time supervision for the loop prevention procedure is 2 seconds.

46

MCMC MTSFB TC T009:2014

B3.17 Supplementary Service Interactions

The public network shall support protocol interaction between the various supplementary services according to ETS 300 195-1 [43]. Network options of ETS 300 195-1 are left as implementation options, unless stated otherwise in the Sub clauses relating to the individual supplementary services. Should any conflict arise between ETS 300 195-1 and the specifications in Sub clause 3.2 to 3.16, then the text of the individual supplementary services shall be taken as definitive.

47

MCMC MTSFB TC T009:2014

Annex C (Normative)

Amendments

Amendments to SKMM FTS ISDN-PA Rev. 1.01:2007 Page Clause Items Amended Cover - The document has adopted new numbering system and cover page. It has been renumbered as “MCMC MTSFB TC T009:2014”.

i - Explanatory note on the development of Technical Codes has been included.

1 1.2 Reference for Section D has been replaced with EN 300 403-1 11/99.

2 2 New clause on normative references has been included.

2 3 The abbreviations have been updated.

3 4.1 Power supply requirements have been revised based on the Information Booklet 2012 Edition, Approval of Electrical Equipment, issued by the Energy Commission.

4 4.1 Alphanumeric keypad layout has been included. (Figure 2)

4 4.2.1 New clause on network interface specifications has been included.

- - Old clause 2.2 on analogue interface has been removed.

- - Old clause 2.3 on characteristics of telephone has been removed.

4 4.3 New clause on interoperability requirement has been included.

12 Section D Network layer requirements have been revised to be based on EN 300 403-1 11/99, Integrated Services Digital Network (ISDN): Digital Subscriber Signaling System No. One (DSS1) protocol: Signaling network layer for circuit-mode basic call control; Part 1: Protocol Specification [ITU-T Recommendation Q.931 (1993), modified].

19 Annex A The normative references have been updated.

20 Annex B Technical guidelines of ISDN supplementary service have been included.

48

MCMC MTSFB TC T009:2014

Acknowledgements

Members of Fixed Terminal Working Group

Mr Abd. Hamid Mustafa (Chairman) Telekom Malaysia Berhad Mr Ahmad Faizan Pardi (Vice Chairman) SIRIM QAS International Sdn Bhd Mrs Nur Rashidah Abas Azmi (Secretary) Telekom Malaysia Berhad Mr Shahadan Man AJV Holding Sdn. Bhd. Mr Zulkhairi Zainal Abidin Epson Malaysia Mr Tan Keok Kuang NEC Corporation of Malaysia Sdn. Bhd Mr Khairul Akmal Zahri Packet One Networks Sdn. Bhd. Mr Syed Ahmad Anas Packet One Networks Sdn. Bhd. Mr Sam Choong Panasonic Malaysia Mr Pang Chieng Yong Panasonic Malaysia Mr Mohd Ackmal Abd. Samad Panasonic System Networks Mrs Hafizah Zainal Abiddin SIRIM QAS International Sdn Bhd Mrs Nurhafenah Abdul Jalil SIRIM QAS International Sdn Bhd Mr Zul Jaafar SIRIM QAS International Sdn Bhd Mr Amin Hapis Khairan Telekom Malaysia Berhad Mr Anuar Wahab Telekom Malaysia Berhad Mrs Badariah Zainal Telekom Malaysia Berhad Mr Md Azmi Karnain Telekom Malaysia Berhad Mr Mohd Syaukiazahar Telekom Malaysia Berhad Mr Muhd Hadzir Abu Hassan Telekom Malaysia Berhad Mrs Nor Maizatul Syima Telekom Malaysia Berhad Mrs Nur Faliza Yaakup Telekom Malaysia Berhad Mr Rahmat Fauzi Zainal Telekom Malaysia Berhad Mrs Raja Nor Suha Telekom Malaysia Berhad Mrs Rosliza Abu Bakar Telekom Malaysia Berhad Mrs Suriyati Rahim Telekom Malaysia Berhad Ms Wan Nur Hanani Telekom Malaysia Berhad Mr Othman Sidek TIME dotCom Berhad

49

MCMC MTSFB TC T010:2014

TECHNICAL CODE

SPECIFICATION FOR ASYMMETRIC DIGITAL SUBSCRIBER LINE (ADSL) TRANSCEIVERS

First Revision

Developed by Registered by

Registered date: 18 December 2014

© Copyright 2014

MCMC MTSFB TC T010:2014

DEVELOPMENT OF TECHNICAL CODES

The Communications and Multimedia Act 1998 (‘the Act’) provides for Technical Standards Forum designated under section 184 of the Act or the Malaysian Communications and Multimedia Commission (‘the Commission’) to prepare a technical code. The technical code prepared pursuant to section 185 of the Act shall consist of, at least, the requirement for network interoperability and the promotion of safety of network facilities.

Section 96 of the Act also provides for the Commission to determine a technical code in accordance with section 55 of the Act if the technical code is not developed under an applicable provision of the Act and it is unlikely to be developed by the Technical Standards Forum within a reasonable time.

In exercise of the power conferred by section 184 of the Act, the Commission has designated the Malaysian Technical Standards Forum Bhd (MTSFB) as a Technical Standards Forum which is obligated, among others, to prepare the technical code under section 185 of the Act.

A technical code prepared in accordance with section 185 shall not be effective until it is registered by the Commission pursuant to section 95 of the Act.

For further information on the technical code, please contact:

Malaysian Communications and Multimedia Commission (MCMC) Off Persiaran Multimedia 63000 Cyberjaya Selangor Darul Ehsan MALAYSIA

Tel: +60 3 8688 8000 Fax: +60 3 8688 1000 http://www.mcmc.gov.my

OR

Malaysian Technical Standards Forum Bhd (MTSFB) 4805-2-2, Block 4805, Persiaran Flora CBD Perdana 2 Cyber 12 63000, Cyberjaya Selangor Darul Ehsan MALAYSIA

Tel: +60 3 8322 1441/1551 Fax: +60 3 8322 0115 http://www.mtsfb.org.my

i MCMC MTSFB TC T010:2014

CONTENTS

Committee Representation ...... iv Foreword …………… ...... v 1. Scope ...... 1 2. Normative references ...... 2 3. Abbreviations ...... 2 4. General Application Reference Models ...... 3 5. Requirements ...... 5 5.1 General requirements ...... 5 5.1.1 Power supply requirements ...... 5 5.1.2 Power supply cord and mains plug requirements ...... 5 5.1.3 Marking requirements ...... 6 5.2 Interoperability ...... 6 5.3 Safety and health requirements ...... 6 5.4 Electromagnetic compatibility (EMC) requirements ...... 6 5.5 Lightning and Surge protection requirements ...... 6 Section A Asymmetric Digital Subscriber Line (ADSL) Transceivers ...... 8 Section B Splitterless Asymmetric Digital Subscriber Line (ADSL) Transceivers ...... 12 Section C Asymmetric Digital Subscriber Line Transceivers 2 (ADSL2) ...... 15 Section D Splitterless Asymmetric Digital Subscriber Line Transceivers 2...... 19 Section E Asymmetric Digital Subscriber Line (ADSL) Transceivers – Extended Bandwidth (ADSL2+) ...... 21 Section F ADSL Interoperability Test Plan ...... 24

Tables 1 Premises Distribution Network Alternatives and Capabilities ...... 5 2 ADSL Transceivers ...... 8 3 Splitterless ADSL Transceivers ...... 12 4 ADSL Transceivers 2 ...... 15 5 Splitterless ADSL Transceivers 2 ...... 19 6 ADSL Transceivers – Extended Bandwidth ...... 21 7 ADSL Interoperability Test Plan ...... 24

ii MCMC MTSFB TC T010:2014

Figures 1 Generic application reference model for remote deployment with splitter ...... 3 2 Generic application reference model for splitterless remote deployment ...... 3 3 Data service application model ...... 4 4 Voice over data service application model ...... 4 5 General reference model for interoperability ...... 7

Annexes A Normative references ...... 26 B Amendments ...... 27

iii MCMC MTSFB TC T010:2014

Committee Representation

The Fixed Terminal Working Group under the Malaysian Technical Standards Forum Bhd (MTSFB) which developed this Technical Code consists of representatives from the following organisations:

AJV Holding Sdn Bhd AZ-Technology Sdn Bhd D Link Corporation Sdn Bhd Panasonic Malaysia SIRIM QAS International Sdn Bhd Telekom Malaysia Berhad TIME dotCom Berhad

iv MCMC MTSFB TC T010:2014

FOREWORD

This technical code for the Specification for Asymmetric Digital Subscriber Line (ADSL) Transceivers (First Revision) (‘this Technical Code’) was developed pursuant to section 185 of the Act 588 by the Malaysian Technical Standards Forum Bhd (MTSFB) via its Fixed Terminal Working Group.

This Technical Code was developed for the purpose of certifying communications equipment under the Communications and Multimedia (Technical Standards) Regulations 2000.

This Technical Code cancels and replaces Technical Specification for Asymmetric Digital Subscriber Line (ADSL) Transceivers, SKMM FTS ADSL Rev. 1.01.2007.

This Technical Code shall continue to be valid and effective until reviewed or cancelled.

v MCMC MTSFB TC T010:2014

THIS PAGE IS INTENTIONALLY LEFT BLANK

vi MCMC MTSFB TC T010:2014

SPECIFICATION FOR ASYMMETRIC DIGITAL SUBSCRIBER LINE (ADSL) TRANSCEIVERS

1. Scope

1.1 This Technical Code defines the physical layer characteristics of the Asymmetrical Digital Subscriber Line (ADSL) transceivers. The purpose of the specification is to ensure proper inter- working of ADSL transceivers at the customer end (ATU-R) and network operator end (ATU-C) in terms of interaction, electrical characteristics and ADSL interoperability. It defines a variety of frame bearers in connection with or without an underlying service. For example: a) ADSL transmission simultaneously on the same pair with voice band service; and b) ADSL transmission without any underlying service, optimized for deployment with ADSL over voice band service in the same binder cable.

1.2 ADSL Transceivers shall be designed for multi-mode operation, supporting one or more of the following ADSL Transceivers standards: a) ADSL Transceivers (ITU-T Rec. G.992.1) outlined in Section A; b) Splitterless ADSL Transceivers (ITU-T Rec. G.992.2) outlined in Section B; c) ADSL2 Transceivers (ITU-T Rec. G.992.3) outlined in Section C; d) Splitterless ADSL2 Transceivers (ITU-T Rec. G.992.4) outlined in Section D; e) ADSL2+ Transceivers – Extended Bandwidth (ITU-T Rec. G.992.5) outlined in Section E; and f) ADSL Interoperability Test Plan (DSL Forum Technical Report TR-067) Section F.

1.3 ADSL Transceivers, supporting the ADSL2, Splitterless ADSL2 or ADSL2+ standards shall be backward compatible and capable of interacting with network equipment which supports only the ADSL and Splitterless ADSL standards.

1.4 The ADSL interoperability test plan facilitates ADSL over POTS and ISDN CPE/DSLAM interoperability testing. This test plan embodies operators’ definitions of ADSL interoperability (between one DSLAM and one CPE at a time). The test plan focuses on physical layer testing, and also validation and verification of selected higher layer functionality. The test plan defines dynamic interoperability (performance) as expected by leading carriers, specifying simulated network conditions under which interoperability is required. The performance points in this test plan are based on ATU-C equipment, capable of providing the maximum allowable power.

ATU-C equipment unable to provide this transmit power is considered to be out of the scope of this interoperability test plan.

This test plan defines tests for various physical layer functionalities and some higher layer functionalities.

1 MCMC MTSFB TC T010:2014

2. Normative references

The following normative references are indispensable for the application of this Technical Code. For dated references, only the edition cited applies. For undated references, the latest edition of the normative references (including any amendments) applies.

See Annex A.

3. Abbreviations

ADSL Asymmetrical Digital Subscriber Line

AOC ADSL Overhead Control

ATM Asynchronous Transfer Mode

ATU ADSL Transceiver Unit

ATU-C ATU at Central Office

ATU-R ATU at Remote End

BMAP Broadband Modem Access Protocol

CPE Customer Premises Equipment

DSL Digital Subscriber Line

DSLAM Digital Subscriber Line Access Multiplexer

EOC Embedded Operation Channel

FEXT Far End Cross(X) Talk

IEEE Institute of Electrical Electronics Engineers

ISDN Integrated Services Digital Network

ISP Internet Standard Protocol

ITU International Telecommunication Union

NIC Network Interface Card

PDN Premises Distribution Network

POTS Plain Old Telephone Service

PPPoE Point-to-point Over Ethernet

STM Synchronous Transfer Mode

TCM Time-Compression Multiplexing

2 MCMC MTSFB TC T010:2014

4. General Application Reference Models

4.1 Standardizing requirements for ADSL Transceivers is carried out at the U interface points of the application reference models shown in Figures 1 to 4.

Figure 1. Generic application reference model for remote deployment with splitter

Figure 2. Generic application reference model for splitterless remote deployment

3 MCMC MTSFB TC T010:2014

Figure 3. Data service application model

Figure 4. Voice over data service application model

Notes: i) U-C and U-R interfaces are fully defined in this Technical Specification. ii) V-C interface may consist of interfaces to one or more ATM switching systems. iii) High-pass (HP) filters, which are part of the splitters, may be integrated into the ATU-x; if so, U-C2 and U-R2 will become the same as U-C and U-R interfaces, respectively. iv) Due to asymmetry of signals on the line, transmitted signals shall be distinctively specified at the U-R and U-C reference points. v) T/S may interface to in-building Ethernet, ATM25, USB, IEEE-1394 or home phone-line network (HomePNA).

4 MCMC MTSFB TC T010:2014

4.2 The Premises Distribution Network (PDN) defines the technology for connecting subscribers’ equipment (e.g. PCs) with the ADSL transceivers (ATU-R). This PDN may be provided as an Ethernet interface, ATM25, USB, IEEE-1394 or a HomePNA backbone. The selection depends mainly on subscribers’ mix of services and network or service providers’ preference in the ATU-R interfaces. Table 1 shows the PDN alternatives and their capabilities.

Table 1. Premises Distribution Network Alternatives and Capabilities

PDN ATM25 Ethernet HomePNA USB IEEE-1394 Bandwidth 25 Mbps 10/100 Mbps 10 Mbps+ 12 Mbps 400 Mbps (half-duplex) (half-duplex) Reach 50 m (Cat 5) 100 m (Cat 3) 500 feet in- 5m 4.6 m house (shielded) (shielded) phone wiring Installation PC NIC Most PCs PC NIC Included Included with require NIC with PCs PCs Protocol Native ATM, PPP via PPPoE, PPP via PPP via PPP, RFC BMAP, bridging BMAP BMAP 1483 PPPoE, tunnelling bridging * Throughput to ADSL loop is limited by the ADSL data rate

5. Requirements

5.1 General requirements

5.1.1 Power supply requirements

5.1.1.1 For AC powered TE, the operating voltage shall be rated/ marked at 230V or 240V in line with the country's nominal voltage and frequency in accordance to MS IEC 60038. If the product is rated with multiple or a range of voltages, voltage range between 230V (+10%,-6%) shall be included. Testing shall be conducted based on 230V (+10%,-6%) or 240V and other relevant voltages, if the product is marked with multiple or a range of voltages.

5.1.1.2 Product shall be rated/ marked at 50Hz and testing shall be conducted at 50Hz. If the product is marked at 50/60Hz or 50-60Hz then testing shall be conducted either at 50Hz or 60Hz, whichever is more unfavorable.

5.1.1.3 Where external power supply is used, e.g. AC adaptor, it shall not affect the capacity of the equipment to meet this specification. Adaptor must be pre-approved by the relevant regulatory body before it can be used with the equipment.

5.1.2 Power supply cord and mains plug requirements

The equipment shall be fitted with a suitable and appropriate approved power supply cord and mains plug. Both are regulated products and must be pre-approved by the relevant regulatory body before it can be used with the equipment.

5 MCMC MTSFB TC T010:2014

The power supply cord shall be certified according to: a) MS 140; or b) BS 6500; or c) IEC 60227-5; or d) IEC 60245-4.

The mains plug shall be certified according to: a) 13 A fused plugs: MS 589: Part 1 or BS 1363: Part 1; or b) 2.5 A, 250 V, flat non-rewirable two-pole plugs: MS 1578 or BS EN 50075.

5.1.3 Marking requirements

The requirements shall be marked with the following information: a) Supplier/manufacturer’s name or identification mark; b) Supplier/manufacturer’s model or type reference; and c) Other markings as required by the relevant standards.

The marking shall be legible, indelible and readily visible. All information on the marking shall be either in Malay or English Language.

5.2 Interoperability

ATU-R Transceiver and ATU-C are dynamically interoperable if they implement a common and compatible set of features, functions and options and can demonstrate satisfactory mutual communication in a real network architecture environment as performance test conditions are varied and exercised. It is mandatory that the ATU-R be tested with the respective Internet Service Provider (ISP) to ensure interoperability. The general reference model for interoperability is shown in Figure 5.

5.3 Safety and health requirements

The equipment shall comply with the safety requirements defined in MS IEC 60950-1. The supplier shall submit full type test report to MS IEC 60950-1 or equivalent standards.

5.4 Electromagnetic compatibility (EMC) requirements

The equipment shall comply with the EMC emissions requirements as defined in the MS CISPR 22 or equivalent standards. The requirements shall cover radiated and conducted emission.

5.5 Lightning and Surge protection requirements

Primary and secondary lightning and surge protection shall be provisioned with 6kV and 3kA in accordance with ITU-T K.21.

6 MCMC MTSFB TC T010:2014

Figure 5. General reference model for interoperability

5.6 Internet Protocol Requirements (IPv6)

It is mandatory that the ATU-R be tested with the respective Internet Service Provider (ISP) to ensure IPv6 interoperability.

7 MCMC MTSFB TC T010:2014

Section A

Asymmetric Digital Subscriber Line (ADSL) Transceivers (ITU-T Recommandation G.992.1)

Table 2. ADSL Transceivers

ITU-T TITLE Rec. CR Remarks G.992.1 Scope 1 GID - System reference modal 1.1 GID - Objectives 1.2 GID - References 2 GID - Definitions 3 GID - Abbreviations 4 GID - Reference models 5 GID - ATU-C transmitter reference 5.1 GID - models ATU-C transmitter reference 5.2 M ATM mode of transportation shall be models supported. Transport capacity 6 GID - Transport of STM data 6.1 NA - Transport of ATM data 6.2 M - ADSL system overheads and total 6.3 M Full overhead framing mode shall be bit rates supported. Reduced overhead framing mode in optional. ATU-C Functional Characteristics 7 GID - STM transmission protocol specific 7.1 GID - functionalities ATM transport protocol specific 7.2 GID The provision of ATM transport mode functionalities is network dependent. Network timing reference 7.3 - Framing 7.4 GID Scramblers 7.5 GID - Forward error correction 7.6 GID - Tone ordering 7.7 GID - Constellation encoder (Treillis code 7.8 GID - version) Constellation encoder (No trellis 7.9 GID - coding)

8 MCMC MTSFB TC T010:2014

Table 2. ADSL Transceivers (Continued)

ITU-T TITLE Rec. CR Remarks G.992.1 Gain scaling 7.10 GID - Modulation 7.11 GID - Cyclic prefix 7.12 GID - Transmitter dynamic range 7.13 GID - ATU-C downstream transmitter 7.14 GID - spectral masks Dual bit mapping and rate 7.15 GID - conversion (Annex C only) FEXT bit mapping (Annex C only) 7.16 GID - ATU-R Functional Characteristics 8 M Framing modes for ATM transport shall be supported STM transmission protocol specific 8.1 NA - functionalities ATM transport protocol specific 8.2 M - functionalities Network timing reference 8.3 O - Framing 8.4 M - Scramblers 8.5 M - Forward error correction 8.6 M - Tone ordering 8.7 M - Constellation encoder - Trellis 8.8 M - version Constellation encoder - Uncoded 8.9 M - version Gain scaling 8.10 M - Modulation 8.11 M - Cyclic prefix 8.12 M - Transmitter dynamic range 8.13 M - ATU-R upstream transmitter 8.14 M - spectral response Dual bit mapping and rate 8.15 NA - conversion (Annex C only) FEXT bit mapping (Annex C only) 8.16 NA - EOC operations and maintenance 9 NA -

9 MCMC MTSFB TC T010:2014

Table 2. ADSL Transceivers (Continued)

ITU-T TITLE Rec. CR Remarks G.992.1 Clear EOC 9.1 O - Embedded operations channel 9.2 M Shall comply with requirements for (EOC) requirements communication between the ATU-C and ATU-R for in-service and out-of- service maintenance. In-service performance monitoring 9.3 M - and surveillance Initialization 10 M - Overview 10.1 M - Handshake - ATU-C 10.2 GID - Handshake - ATU-R 10.3 O - Transceiver training - ATU-C 10.4 M - Transceiver training - ATU-R 10.5 M - Channel analysis (ATU-C) 10.6 M - Channel analysis (ATU-R) 10.7 M - Exchange - ATU-C 10.8 M - Exchange - ATU-R 10.9 M - AOC on-line adaptation and 11 M - reconfiguration The ADSL overhead control (AOC) 11.1 M - channel Specific requirements for an ADSL Annex A M - system operating in the frequency band above POTS Specific requirements for an ADSL Annex B NA - system operating in the frequency band above ISDN as defined in ITU-T Rec. G.961 Appendices I and II Specific requirements for an ADSL Annex C NA - system operating in the same cable as ISDN as defined in ITU-T Rec. - G.961 Appendix III ATU-C and ATU-R state diagrams Annex D GID - POTS and ISDN-BA Splitters Annex E GID - Type 1 - European E.1 GID If applicable, POTS splitter shall comply with the requirements specified in SKMM FTS PSTN Impedance Matching E.1.1 GID -

10 MCMC MTSFB TC T010:2014

Table 2. ADSL Transceiver (Continued)

ITU-T TITLE Rec. CR Remarks G.992.1 Return loss E.1.2 GID - Insertion loss E.1.3 GID - Insertion loss distortion E.1.4 GID - Isolation E.1.5 GID - Signal power E.1.6 GID - Ringing E.1.7 GID - Unbalance about earth E.1.8 GID - Frequencies and levels for pulse E.1.9 NA - metering Type 2 – North America E.2 NA - Type 3 – ADSL above ISDN (ITU-T E.3 NA - G.961 Appendix I or II) Type 4 – Type for Japan E.4 NA - ATU-x Classification and Annex F GID - Performance for Region A (Other than Europe) ATU-x Classification and Annex G GID - Performance for Region B (Europe) ATM Layer to Physical Layer Appendix GID - Logical Interface I Dynamic (on-line) Rate Adaptation Appendix GID - II Compatibility with other customer Appendix GID - premise equipment III Bibliography Appendix GID - IV

11 MCMC MTSFB TC T010:2014

Section B

Splitterless Asymmetric Digital Subscriber Line (ADSL) Transceivers (ITU-T Recommendation G.992.2)

Table 3. Splitterless ADSL Transceivers

ITU-T TITLE Rec. CR Remarks G.992.2 Scope 1 GID - References 2 GID - Definitions and abbreviations 3 GID - Reference models 4 GID Support of ATM is required. ADSL transceivers (ATU-R) shall support bearer channel AS0 downstream and LS0 upstream. Transport capacity 5 M - ATU interfaces 6 - - ATU interface for ATM transport 6.1 M - ATU PMD to TC Logical Interface 6.2 GID - ATU Functional Characteristics 7 - - ATM Transport Protocol Specific 7.1 M - Functionalities Network Timing Reference 7.2 O - Framing 7.3 M - Scrambler 7.4 M - Reed Solomon Forward Error 7.5 M - Correction Interleaver 7.6 M - Tone ordering 7.7 M - Constellation encoder 7.8 M - Gain scaling 7.9 M - Modulation 7.10 M - Cyclic prefix 7.11 M - Transmitter dynamic range 7.12 M - Embedded operations - - (EOC) EOC introduction 8.1 M - EOC message encoding 8.2 M -

12 MCMC MTSFB TC T010:2014

Table 3. Splitterless ADSL Transceivers (Continued)

ITU-T TITLE Rec. CR Remarks G.992.2 EOC message description 8.3 M - EOC Protocol 8.4 M - Clear EOC 8.5 O - ADSL overhead channel (AOC) 9 - - The ADSL overhead control (AOC) 9.1 O - channel introduction AOC message encoding 9.2 M - Bit swap operation 9.3 O - AOC protocol 9.4 M - In-service performance monitoring 10 GID - and surveillance ADSL line related primitives 10.1 M - ATM data path related primitives 10.2 M - Other ADSL indicators, parameters 10.3 M - and signals Test parameters 10.4 M - Other failures and parameters 10.5 M - Initialization 11 - - Overview 11.1 M - Handshake – ATU-C 11.2 GID - Handshake – ATU-R 11.3 M - Handshake power levels 11.4 M - Escape from Handshake to Fast 11.5 O - Retrain Power Levels in Transceiver 11.6 M - Training, Channel Analysis and Exchange Transceiver training – ATU-C 11.7 M - Transceiver training – ATU-R 11.8 M - Channel analysis (ATU-C) 11.9 M - Channel analysis (ATU-R) 11.10 M - Exchange – ATU-C 11.11 M - Exchange – ATU-R 11.12 M - Fast retrain Non-overlapped 12 O - Power management 13 O - Spectrum Operation Annex A M -

13 MCMC MTSFB TC T010:2014

Table 3. Splitterless ADSL Transceivers (Continued)

ITU-T Rec. TITLE G.992.2 CR Remarks

Overlapped Spectrum Operation Annex B M ADSL above POTS co-existing in Annex C GID - the same binder as TCM-ISDN DSL System Performance for North Annex D GID - America System Performance for Europe Annex E GID - - Appendix GID - I Guide to scenarios for the Appendix GID - implementation of the various II procedures in Recommendations G.994.1 and G.992.2 Compatibility with other Customer Appendix O - Premises Equipment III

14 MCMC MTSFB TC T010:2014

Section C

Asymmetric Digital Subscriber Line Transceivers 2 (ADSL2) (ITU-T Recommendation G.992.3)

Table 4. ADSL Transceivers 2

ITU-T TITLE Rec. CR Remarks G.992.3 Scope 1 GID - References 2 GID - Definitions 3 GID - Abbreviations 4 GID - Reference models 5 GID Application models may include: 1. Generic application reference model for remote deployment with splitter 2. Generic application reference model for splitterless remote deployment 3. Data service application model 4. Data with POTS service application model 5. Data with ISDN service application model 6. Voice over data service application model Transport Protocol Specific 6 - - Transmission Convergence (TPS- TC) function Transport capabilities 6.1 M - Interface signals and primitives 6.2 M - Control parameters 6.3 M - Data plane procedures 6.4 M - Management plane procedures 6.5 O - Initialization procedure 6.6 M - On-line reconfiguration. 6.7 M - Power management mode 6.8 M - Physical Media Specific 7 - - Transmission Convergence (PMS- TC) function Transport capabilities 7.1 M - Additional functions 7.2 M -

15 MCMC MTSFB TC T010:2014

Table 4. ADSL Transceivers 2 (Continued)

ITU-T CR Remarks TITLE Rec. G.992.3 Block interface signals and primitives 7.3 M - Block diagram and internal reference 7.4 M - point signals Control parameters 7.5 M - Frame structure 7.6 M - Data plane procedures 7.7 M - Control plane procedures 7.8 M - Management plane procedures 7.9 M - Initialization procedures 7.10 M - On-line reconfiguration 7.11 M - Power management mode 7.12 M - Physical media dependent function 8 - - Transport capabilities 8.1 M - Additional functions 8.2 M - Block interface signals and primitives 8.3 M - Control parameters 8.5 M - Constellation encoder for data symbols 8.6 M - Constellation encoder for 8.7 M - synchronization and L2 exit symbols Modulation 8.8 M - Transmitter dynamic range 8.9 M - Transmitter spectral masks 8.10 M - Control plane procedures 8.11 M - Management plane procedures 8.12 M - Initialization procedures 8.13 M - Short initialization procedures 8.14 O - Loop diagnostics mode procedures 8.15 M - On-line reconfiguration of the PMD 8.16 M - function Power management in the PMD 8.17 M - function Management Protocol Specific 9 GID - Transmission Convergence (MPS-TC) functions Transport functions 9.1 M - Additional functions 9.2 M -

16 MCMC MTSFB TC T010:2014

Table 4. ADSL Transceivers 2 (Continued)

ITU-T TITLE Rec. CR Remarks G.992.3 Block interface signals and primitives 9.3 M - Management plane procedures 9.4 M - Power management 9.5 M - Dynamic behavior 10 M - Initialization 10.1 M - On-line Reconfiguration (OLR) 10.2 M - Power management 10.3 M - Specific requirements for an ADSL Annex A M - system operating in the frequency band above POTS Specific requirements for an ADSL Annex B NA - system operating in the frequency band above ISDN as defined in ITU- T Rec. G.961 Appendices I and II Specific requirements for an ADSL Annex C NA - system operating in the same cable as ISDN as defined in ITU-T Rec. G.961 Appendix III ATU-C and ATU-R state diagrams Annex D GID - POTS and ISDN Basic Access Annex E GID - Splitters Type 1 – POTS splitter – Europe E.1 O - Type 2 – POTS splitter – North E.2 O - America

Type 3 – ISDN (ITU-T Rec. G.961 E.3 NA - Appendix I or II) Splitter – Europe Type 4 – POTS splitter – Japan E.4 O - ATU-x performance requirements for region A (North America) ATU-x performance requirements for Annex G O - region B (Europe) Specific requirements for a Annex H NA - synchronized symmetrical DSL (SSDSL) system operating in the same cable binder as ISDN as defined in ITU-T Rec. G.961 Appendix III

17 MCMC MTSFB TC T010:2014

Table 4. ADSL Transceivers 2 (Continued)

TITLE ITU-T CR Remarks Rec. G.992.3 All digital mode ADSL with Improved Annex I O - spectral compatibility with ADSL over POTS All Digital Mode ADSL with improved Annex J NA - spectral compatibility with ADSL over ISDN TPS-TC functional descriptions Annex K GID - STM Transmission Convergence K.1 NA - (STM-TC) function ATM Transmission Convergence K.2 M - (ATM-TC) function Packet transmission convergence K.3 O - function (PTM-TC) ATM layer to physical layer logical Appendix I GID - interface Compatibility with other customer Appendix GID - premises equipment II The impact of primary protection Appendix GID - devices on line balance III Bibliography Appendix GID - IV

18 MCMC MTSFB TC T010:2014

Section D

Splitterless Asymmetric Digital Subscriber Line Transceivers 2 (Splitterless ADSL2) (ITU-T Recommendation G.992.4)

Table 5. Splitterless ADSL Transceivers 2

ITU-T TITLE Rec. CR Remarks G.992.4 Scope 1 GID - References 2 GID - Definitions 3 GID - Abbreviations 4 GID - Reference models 5 GID Application models may include: 1. Generic application reference model for splitterless remote deployment 2. Data service application model 3. Data with POTS service application model 4. Voice over data service application model Transport Protocol Specific 6 M - Transmission Convergence (TPS- TC) function Physical Media Specific 7 M - Transmission Convergence (PMS- TC) function Physical media dependent 8 M - function Management Protocol Specific 9 M - Transmission Convergence (MPS- TC) functions Control Protocol Specific 10 - Further study by ITU-T Transmission Convergence (CPS- TC) functions Dynamic behavior 11 M -

Specific requirements for an ADSL Annex A M - system operating in the frequency band above POTS

19 MCMC MTSFB TC T010:2014

Table 5. Splitterless ADSL Transceivers 2 (Continued)

ITU-T TITLE Rec. CR Remarks G.992.4 Specific requirements for an ADSL Annex C NA - system operating in the same cable as ISDN as defined in ITU-T Rec. G.961 Appendix III ATU-C and ATU-R state diagrams Annex D GID - POTS and ISDN-BA splitters Annex E GID - ATU-x performance requirements for Annex F - Further study by ITU-T region A (North America) - Annex G - Intentionally left blank - Annex H - Intentionally left blank All digital mode ADSL with Annex I O - improved spectral compatibility with ADSL over POTS - Annex J - Intentionally left blank TPS-TC functional descriptions Annex K M -

20 MCMC MTSFB TC T010:2014

Section E

Asymmetric Digital Subscriber Line (ADSL) Transceivers – Extended Bandwidth (ADSL2+) (ITU-T Recommendation G.992.5)

Table 6. ADSL Transceivers – Extended Bandwidth

ITU-T TITLE Rec. CR Remarks G.992.5 Scope 1 GID - References 2 GID - Definitions 3 GID - Abbreviations 4 GID - Reference models 5 GID Application models may include: 1. Generic application reference model for remote deployment with splitter 2. Generic application reference model for splitterless remote deployment 3. Data service application model 4. Data with POTS service application model 5. Data with ISDN service application model 6. Voice over data service application model Transport Protocol Specific 6 M - Transmission Convergence (TPS- TC) function Physical Media Specific 7 M - Transmission Convergence (PMS- TC) function Physical media dependent function 8 - - Transport capabilities 8.1 M - Additional functions 8.2 M - Block interface signals and primitives 8.3 M - Block diagram and internal reference 8.4 M - point signals Control parameters 8.5 M - Constellation encoder for data 8.6 M - symbols

21 MCMC MTSFB TC T010:2014

Table 6. ADSL Transceivers – Extended Bandwidth (Continued)

ITU-T Rec. TITLE G.992.5 CR Remarks

Constellation encoder for 8.7 M - synchronization and L2 exit symbols Modulation 8.8 M - Transmitter dynamic range 8.9 3 M - Transmitter spectral masks 8.10 M - Control plane procedures 8.11 M - Management plane procedures 8.12 M - Initialization procedures 8.13 M - Short initialization procedures 8.14 O - Loop diagnostics mode procedures 8.15 M - On-line reconfiguration of the PMD 8.16 M - function Power management in the PMD 8.17 M - function Management Protocol Specific 9 GID - Transmission Convergence (MPS- TC) functions Transport functions Block interface 9.1 M - signals and primitives 9.3 M Refer to § 9.3/G.992.3 Additional functions 9.2 M - Management plane procedures 9.4 M - Power management 9.5 M - Dynamic behavior 10 M - Specific requirements for an ADSL Annex A M - system operating in the frequency band above POTS Specific requirements for an ADSL Annex B NA - system operating in the frequency band above ISDN as defined in ITU- T Rec. G.961 Appendices I and II Specific requirements for an ADSL Annex C NA - system operating in the same cable as ISDN as defined in ITU-T Rec. G.961 Appendix III ATU-C and ATU-R state diagrams Annex D GID - POTS and ISDN-BA splitters Annex E GID - ATU-x performance requirements for Annex F - Further study by ITU-T region A (North America)

22 MCMC MTSFB TC T010:2014

Table 6. ADSL Transceivers – Extended Bandwidth (Continued)

ITU-T Rec. TITLE G.992.5 CR Remarks

ATU-x performance requirements for Annex G - Further study by ITU-T region B (Europe) Specific requirements for a Annex H - Further study by ITU-T synchronized symmetrical DSL (SSDSL) system operating in the same cable binder as ISDN as Defined in ITU-T Rec. G.961 Appendix III All digital mode ADSL with Annex I O - Improved spectral compatibility With ADSL over POTS All Digital Mode ADSL with improved Annex J NA - spectral compatibility with ADSL over ISDN TPS-TC functional descriptions Annex K M - - Annex L - - Specific requirements for an ADSL Annex M O - system with extended upstream bandwidth, operating in the frequency band above POTS 1. ATM layer to physical layer logical Appendix I GID - interface Compatibility with other customer Appendix II GID - premises equipment The impact of primary protection Appendix III GID - devices on line balance PSD template to be used in capacity Appendix IV GID - calculations with in-band transmit spectrum shaping Bibliography Appendix V GID -

23 MCMC MTSFB TC T010:2014

Section F

ADSL Interoperability Test Plan (DSL Forum Technical Report TR-067)

Table 7. ADSL Interoperability Test Plan

Title TR-067 CR Remarks Equipment features

DSLAM 6.1 M Refer to Table 6.1.1:DSLAM Features (Informative) CPE 6.2 M Refer to Table 6.2.1:CPE Features Tables (Informative) Expected results 6.3 M The results columns of Table 6.1.1 and 6.2.1 shall be completed to indicate whether each feature is included with the DSLAM or CPE transceivers. Test configurations The test configuration is based on type of Transceivers. Refer to Appropriate figures in Clause 7.0.

Physical layer test cases

ADSL functionality tests 8.1 M 9 individual tests – 9 must be passed Sudden applications of RFI 8.2 M A test that more closely replicates the very rapid increases in amplitude of RFI that occur on real circuits. DSL noise spikes/surges 8.3 M 10 individual tests – 10 must be passed tests (recovery or retrain after noise condition) Stress test 8.4 M 1 individual test – 1 must be passed Electrical compatibility tests 8.5 M 4 individual tests – 4 must be passed Higher layer test cases

Layer ATM connectivity tests 9.1 M 9 individual tests – 8 must be passed (all except Test 9.1.5) 3 Ethernet or USB interface 9.2 M 42 individual tests – 42 must be passed RFC 2684 [10] bridged mode RFC 2516 [11] PPPoE end- 9.3 M 1 individual tests – 1 must be passed to-end connectivity test RFC 2364 [12] PPPoA end- 9.4 M 1 individual tests – 1 must be passed to-end connectivity test RFC 2684 [10] end-to-end 9.5 M 1 individual tests – 1 must be passed connectivity test Usability test 9.6 M 1 individual tests – 1 must be passed

24 MCMC MTSFB TC T010:2014

Table 7. ADSL Interoperability Test Plan (Continued)

Physical layer test cases for system using G.992.1 (ADSL Interoperability Test Plan, TR-067)

North American Test set Annex A.1 M Applicable for ADSL over POTS

European Test set Annex A.2 M Applicable for ADSL over POTS Specific Test Set-up Annex B.1 GID Applicable for ADSL over ISDN Information European Test set Annex B.2 O Applicable for ADSL over ISDN Physical layer test cases Annex C GID Applicable for ADSL co-exist with TCM-ISDN for system using G.992.1

NOTES:

i) System Under Test (SUT) shall comply either Annex A.1 or Annex A.2. ii) The following notations are used in the Specification:  CR - Conformance requirement defines features and functions that must be supported at minimum.  M - Mandatory requirements  Optional requirement, which become mandatory when features and functions are supported.  NA - Not Applicable  GID - General Information and Definitions

25 MCMC MTSFB TC T010:2014

Annex A (Normative)

Normative references

BS EN 50075 Flat non-wireable two pole plugs 2.5 A 250 V with cord for the connection of class II- Equipment for household and similar propose

BS 1363:Part 1 13A plugs, socket outlets, adaptors and connection units

BS 6500 Flexible cords rated up to 300, 500 V for use with appliances and equipment intended for domestic offices and similar environments

DSL FORUM TR-067 ADSL Interoperability Test Plan

IEC 60227-5 Polyvinyl chloride insulated cables of rated voltages up to and including 450/750 V – Part 5: Flexible cables (cords)

IEC 60245-4 Rubber insulated cables – Rated voltages up to and including 450/750 V – Part 4: Cords and flexible cables

ITU-T Rec. G.992.2 Splitterless Asymmetric Digital Subscriber Line (ADSL) Transceivers

ITU-T Rec. G.992.3 Asymmetric Digital Subscriber Line Transceivers 2 (ADSL2)

ITU-T Rec. G.992.4 Splitterless Digital Subscriber Line Transceivers 2 (Splitterless ADSL2)

ITU-T Rec. G.992.5 Asymmetric Digital Subscriber Line (ADSL) Transceivers – Extended Bandwidth (ADSL2+)

MS CISPR 22 Information Technology Equipment – Radio disturbance characteristics – Limits and methods of measurement

MS IEC 60038 IEC Standard Voltages

MS IEC 60950-1 Information Technology Equipment – Safety

MS 140 Specification for insulated flexible cords and cables

MS 589:Part 1 Specification for 13A plugs, socket – outlets, adaptors and connection units : Part 1: Specification for rewirable and non-rewirable 13A plugs

MS 1578 Specification for flat non-rewirable two-pole plus, 2.5 A, 250 V, with cord, for the connection of class II – Equipment for household and similar

purposes

26 MCMC MTSFB TC T010:2014

Annex B (Informative)

Amendments

Amendments to SKMM FTS ADSL Rev. 1.01:2007 Page Clause Items Amended Cover - The document has adopted new numbering system and cover page. It has been renumbered as “MCMC MTSFB TC T010:2014”.

i - Explanatory note on the development of Technical Codes has been included.

2 2 New clause on normative references has been included.

2 3 The abbreviations have been updated.

5 5.1.1 Power supply requirements have been revised based on the Information Booklet 2012 Edition, Approval of Electrical Equipment, issued by the Energy Commission.

6 - Old clause 5.2 on compliance standards for ADSL transceivers have been removed.

6 5.2 Interoperability requirements have been updated to mandate testing requirement with the respective Internet Service Provider.

6 5.5 New clause on lightning and surge protection requirements has been included.

7 5.5 Figure 5 on the general reference model for interoperability has (Figure 5) been updated.

7 5.6 New clause on IPv6 requirements has been included.

26 Annex A The normative references have been updated.

27 MCMC MTSFB TC T010:2014

Acknowledgements

Members of Fixed Terminal Working Group

Mr Abd. Hamid Mustafa (Chairman) Telekom Malaysia Berhad Mr Ahmad Faizan Pardi (Vice Chairman) SIRIM QAS International Sdn Bhd Mrs Nur Rashidah Abas Azmi (Secretary) Telekom Malaysia Berhad Mr Shahadan Man AJV Holding Sdn. Bhd. Mr Zulkhairi Zainal Abidin Epson Malaysia Mr Tan Keok Kuang NEC Corporation of Malaysia Sdn Bhd Mr Khairul Akmal Zahri Packet One Networks Sdn. Bhd. Mr Syed Ahmad Anas Packet One Networks Sdn. Bhd. Mr Sam Choong Panasonic Malaysia Mr Pang Chieng Yong Panasonic Malaysia Mr Mohd Ackmal Abd. Samad Panasonic System Networks Mrs Hafizah Zainal Abiddin SIRIM QAS International Sdn Bhd Mrs Nurhafenah Abdul Jalil SIRIM QAS International Sdn Bhd Mr Zul Jaafar SIRIM QAS International Sdn Bhd Mr Amin Hapis Khairan Telekom Malaysia Berhad Mr Anuar Wahab Telekom Malaysia Berhad Mrs Badariah Zainal Telekom Malaysia Berhad Mr Md Azmi Karnain Telekom Malaysia Berhad Mr Mohd Syaukiazahar Telekom Malaysia Berhad Mr Muhd Hadzir Abu Hassan Telekom Malaysia Berhad Mrs Nor Maizatul Syima Telekom Malaysia Berhad Mrs Nur Faliza Yaakup Telekom Malaysia Berhad Mr Rahmat Fauzi Zainal Telekom Malaysia Berhad Mrs Raja Nor Suha Telekom Malaysia Berhad Mrs Rosliza Abu Bakar Telekom Malaysia Berhad Mrs Suriyati Rahim Telekom Malaysia Berhad Ms Wan Nur Hanani Telekom Malaysia Berhad Mr Othman Sidek TIME dotCom Berhad

MCMC MTSFB TC T011:2014

TECHNICAL CODE

SPECIFICATIONS ON COMMON TEST SUITE FOR DIGITAL BROADCAST SERVICE RECEIVER

Developed by Registered by

Registered date: 18 December 2014

© Copyright 2014

MCMC MTSFB TC T011:2014

DEVELOPMENT OF TECHNICAL CODES

The Communications and Multimedia Act 1998 (‘the Act’) provides for Technical Standards Forum designated under section 184 of the Act or the Malaysian Communications and Multimedia Commission (“the Commission”) to prepare a technical code. The technical code prepared pursuant to section 185 of the Act shall consist of, at least, the requirement for network interoperability and the promotion of safety of network facilities.

Section 96 of the Act also provides for the Commission to determine a technical code in accordance with section 55 of the Act if the technical code is not developed under an applicable provision of the Act and it is unlikely to be developed by the Technical Standards Forum within a reasonable time.

In exercise of the power conferred by section 184 of the Act, the Commission has designated the Malaysian Technical Standards Forum Berhad (MTSFB) as a Technical Standards Forum which is obligated, among others, to prepare the technical code under section 185 of the Act.

A technical code prepared in accordance with section 185 shall not be effective until it is registered by the Commission pursuant to section 95 of the Act.

For further information on the technical code, please contact:

Malaysian Communications and Multimedia Commission (MCMC) Off Persiaran Multimedia 63000 Cyberjaya Selangor Darul Ehsan MALAYSIA

Tel: +60 3 8688 8000 Fax: +60 3 8688 1000 http://www.skmm.gov.my

OR

Malaysian Technical Standards Forum Berhad (MTSFB) 4805-2-2, Blok 4805, Persiaran Flora CBD Perdana 2, Cyber 12 63000 Cyberjaya Selangor Darul Ehsan MALAYSIA

Tel: +60 3 8322 1441/1551 Fax: +60 3 8322 0115 http://www.mtsfb.org.my

i MCMC MTSFB TC T011:2014

CONTENTS

Committee Representation ...... v Foreword ...... vi 1. Scope ...... 1 2. Normative References ...... 1 3. Abbreviations ...... 1 4. Requirements ...... 3 4.1 RF ...... 3 4.2 SI/PSI ...... 3 4.3 OAD ...... 3 4.4 HbbTV ...... 3 5. Malaysia DVB-T2 RF Performance Test Suite Ver1.0 ...... 4 5.1 Revision History ...... 4 5.2 Evaluation Details ...... 4 5.3 Evaluation Results ...... 4 5.4 Malaysia DVB-T2 RF Modes and Performance Figure ...... 5 5.4.1 RF Profile for Malaysia ...... 5 5.4.2 Performance Figures for Malaysia ...... 6 5.5 Test Instrument Set Up ...... 8 5.6 Test Category ...... 10 5.6.1 Carrier to Noise Ratio (C/N) Performance on Gaussian Channel ...... 10 5.6.2 C/N Performance on 0dB Echo Channel ...... 11 5.6.3 Minimum Receiver Signal Input Levels on Gaussian Channel ...... 12 5.6.4 Minimum Integrated Receiver Decoder (IRD) Signal Input Levels on 0db Echo Channel ...... 13 5.6.5 Maximum Receiver Signal Input Levels ...... 14 5.6.6 Immunity to "Digital" Signals in Other Channels ...... 15 5.6.7 Immunity to Co-Channel Interference from Analogue TV Signals ...... 17 5.6.8 Immunity to Adjacent Channel Interference from Analogue TV Signals ...... 19 5.6.9 Performance in Time-Varying Channels 10Hz Doppler (5Hz after Automatic Frequency Control (AFC)) 20μs 0dB Echo...... 21 5.6.10 Synchronisation for Varying Echo Power Levels in Single Frequency Networks (SFN) ...... 23 5.6.11 C/(N+I) Performance in SFN for more than one echo ...... 25 5.6.12 C/(N+I) Performance in Single Frequency Networks inside the Guard Interval (GI) ...... 27 5.6.13 C/(N+I) Performance in SFN outside the Guard Interval ...... 29 6. Malaysia DVB-T2 SI/PSI Conformance Test Suite Ver1.0 ...... 31 6.1 Revision History ...... 31 6.2 Evaluation Details ...... 31 6.3 Evaluation Results ...... 31 6.4 Test Category ...... 32 6.4.1 Basic SI/PSI Test ...... 32 6.4.1.1 Service Installation and Information ...... 32

ii MCMC MTSFB TC T011:2014

6.4.1.2 Event Information ...... 33 6.4.1.3 Codec Information ...... 35 6.4.1.4 Audio and Subtitle Language ...... 36 6.4.1.5 Results of Basic SI/PSI Test ...... 38 6.4.2 Logical Channel Numbering (LCN) Test ...... 38 6.4.2.1 Decoding of LCN descriptors ...... 39 6.4.2.2 Foreign Services ...... 41 6.4.2.3 No LCN Descriptor ...... 42 6.4.2.4 Regional Broadcast Management ...... 43 6.4.2.5 Results of LCN Test ...... 44 6.4.3 Network Evolution ...... 45 6.4.3.1 Service Addition and Deletion ...... 46 6.4.3.2 Clash LCN Resolution ...... 48 6.4.3.3 Multiplex Addition and Deletion ...... 51 6.4.3.4 Service and Event Updates ...... 53 6.4.3.5 Results of Network Evolution Test ...... 56 6.4.4 Character Test ...... 56 6.4.4.1 Event p/f ...... 57 6.4.4.2 Event Schedule ...... 60 6.4.4.3 Event p/f (Huffman Encoding) ...... 62 6.4.4.4 Event Schedule (Huffman Encoding) ...... 65 6.4.4.5 Huffman Encoding (Malay) ...... 66 6.4.4.6 Huffman Encoding (ESC character) ...... 67 6.4.4.7 No Table Definition ...... 68 6.4.4.8 Latin Table 05 - ISO-8859-9 ...... 69 6.4.4.9 Results of Character Test ...... 70 6.4.5 Active Format Descriptor (AFD) Test ...... 70 6.4.5.1 AFD...... 71 6.4.5.2 Results of AFD Test ...... 73 6.4.6 Multiple Physical Layer...... 74 6.4.6.1 Multiple Physical Layer Pipes ...... 75 6.4.6.2 Results of Multiple-PLP Test ...... 77 6.4.7 Self Declaration ...... 77 6.4.7.1 Results of Declaration ...... 77 6.4.7.2 Notes - T2Xpress Settings ...... 78 7. Malaysia (MYS) SI/PSI Test Requirement ...... 79 7.1 Frequency Range ...... 79 7.2 Service Installation ...... 79 7.3 Video Decoding ...... 80 7.4 Audio Decoding ...... 80 7.5 Subtitling ...... 81 7.6 Time and Data Information ...... 81 7.7 EIT Presentation ...... 81 7.8 Audio and Subtitle Language Support ...... 82 7.9 Logical Channel Numbering ...... 82 7.10 Network Evolution ...... 83

iii MCMC MTSFB TC T011:2014

7.11 Time Exclusive Services ...... 84 8. Malaysia DVB-T2 Over Air Download (OAD) Test Suite Ver1.0...... 85 8.1 Revision history ...... 85 8.2 Evaluation details ...... 85 8.3 Evaluation Results ...... 85 8.4 Test Description ...... 86 8.5 Results of OAD Test ...... 87 8.6 Test Environment ...... 88 8.7 Transport Stream Structure ...... 89 8.7.1 Transport Stream (option 1) ...... 89 8.7.2 Transport Stream (option 2) ...... 90 9. Malaysia Hybrid Broadcast TV (HBBTV) Test Suite Ver1.0 ...... 91 9.1 Revision history ...... 91 9.2 Evaluation details ...... 91 9.3 Evaluation results ...... 91 9.4 Test Suite ...... 91 9.4.1 HbbTV 0.9 ...... 91 9.4.1.1 Results ...... 100 9.4.2 Dynamic Adaptive Streaming over HTTP (DASH) ...... 100 9.4.2.1 Results ...... 101 9.4.3 Recording ...... 101 9.4.3.1 Results ...... 101 9.4.4 Marlin Digital Rights Management (DRM)...... 101 9.4.4.1 Results ...... 102 9.4.5 Event Information Table (EIT) ...... 102 9.4.5.1 Results ...... 102 9.5 References ...... 103 Acknowledgements ...... 104

iv MCMC MTSFB TC T011:2014

Committee Representation

The Multimedia Terminal Working Group (MMT WG) under the Malaysian Technical Standards Forum Berhad (MTSFB) which supervised the development of this Technical Code consists of representatives from the following organizations:

Al Hijrah Media Corporation (TV Alhijrah) Asian Networks (M) Sdn Bhd (ABNxcess) Dolby Laboratories Inc. Eastool Solution Sdn Bhd Fraunhofer IIS Guillemard Engineering Services Hanitek Sdn Bhd LG Electronics (M) Sdn Bhd Malaysian Technical Standards Forum Berhad (MTSFB) Berhad MyTV Broadcasting Sdn Bhd Panasonic AVC Networks Kuala Lumpur Malaysia Sdn Bhd Radio Television Malaysia (RTM) Rohde & Schwarz Malaysia Sdn Bhd Samsung Malaysia Electronics (SME) Sdn Bhd Sharp (M) Sdn Bhd SIRIM QAS International Sdn Bhd Sony EMCS (M) Sdn Bhd Toshiba (M) Sdn Bhd

The Testing Material Sub Working Group of the Multimedia Terminal Working Group (MMT WG) which developed this Technical Code consists of representatives from the following organizations:

Al Hijrah Media Corporation (TV Alhijrah) Dolby Laboratories Inc. Hanitek Sdn Bhd LG Electronics (M) Sdn Bhd Malaysian Technical Standards Forum Berhad (MTSFB) Media Prima Berhad MyTV Broadcasting Sdn Bhd Panasonic AVC Networks Kuala Lumpur Malaysia Sdn Bhd Radio Television Malaysia (RTM) Rohde & Schwarz Malaysia Sdn Bhd Samsung Malaysia Electronics (SME) Sdn Bhd Sharp (M) Sdn Bhd SIRIM QAS International Sdn Bhd Sony EMCS (M) Sdn Bhd Toshiba (M) Sdn Bhd

v MCMC MTSFB TC T011:2014

FOREWORD

This technical code for the Specifications on Common Test Suite for Digital Terrestrial Television Broadcast Service Receiver (‘this Technical Code’) was developed by the Testing Material Sub Working Group of the Multimedia Terminal Working Group under the Malaysian Technical Standards Forum Berhad (MTSFB) in accordance with Section 185 of the Communications and Multimedia Act 1998.

This Technical Code was developed to specify the common test suite for digital terrestrial television broadcast service receivers for the purpose of certifying the devices under the Communications and Multimedia (Technical Standards) Regulations 2000.

This Technical Code shall continue to be valid and effective until reviewed or cancelled.

vi MCMC MTSFB TC T011:2014

SPECIFICATIONS ON COMMON TEST SUITE FOR DIGITAL TERRESTRIAL TELEVISION BROADCAST SERVICE RECEIVER

1. Scope

This Technical Code describes the test methods for the digital terrestrial television broadcast receivers in complying with the SKMM MTSFB TC T004: 2013 - Specification for Digital Terrestrial Television Broadcast Service Receivers, SKMM MTSFB TC G001: 2013 - Compression Table of Service Information (SI) Descriptions for Digital Terrestrial Television Broadcast Service and SKMM MTSFB TC G002: 2013 - Middleware Profile for Digital Terrestrial Television Broadcast Service. The receivers may include Integrated Digital Televisions (IDTVs), Set Top Boxes (STBs) and other types of stand-alone receivers for the reception of digital terrestrial television broadcast service in Malaysia.

2. Normative References

The following normative references are indispensable for the application of this Technical Code. For dated references, only the edition cited applies. For undated references, the latest edition of the normative reference (including any amendments) applies.

SKMM MTSFB TC T004: 2013, Specification for Digital Terrestrial Television Broadcast Service Receiver

SKMM MTSFB TC G001: 2013, Compression Table of Service Information (SI) Descriptions for Digital Terrestrial Television Broadcast Service

SKMM MTSFB TC G002: 2013, Middleware Profile for Digital Terrestrial Television Broadcast Service

Television Digital Terrestre Hibrida

Test Suite for HbbTV Specification Version 2, 1 October 2014

TNT 2.0 Terminal Specification V1.1, July 2012

3. Abbreviations

For the purposes of this Technical Code, the following abbreviation applies.

AAC Advanced Audio Coding AFC Automatic Frequency Control AFD Active Format Descriptor AIT Application Information Table API Application Protocol Interface AVC Advanced Video Coding C/N Carrier to Noise Ratio CSS Cascading Style Sheets DASH Dynamic Adaptive Streaming over HTTP DRM Digital Rights Management DSM-CC Digital Storage Media Command and Control EIT Event Information Table

1 MCMC MTSFB TC T011:2014

EIT [p/f] Information on the current event (p:present) and next event (f:following) in the EIT EPG Electronic Program Guide FEC Forward Error Correction FFT Fast Fourier Transforms GI Guard Intervals HbbTV Hybrid Broadcast Broadband Television HE-AAC High Efficiency Advanced Audio Coding HTML HyperText Markup Language HTTP HyperText Transfer Protocol IDTV Integrated Digital Television iDTV Integrated Digital Television (receiver) IRD Integrate Receiver Decoder ISSY Input Stream SYnchronizer LCN Logical Channel Number MISO Multiple Input Single Output MPD Minimum Product Distance MPEG Moving Picture Experts Group MPLP Multiple Physical Layer Pipe OAD Over Air Download OFDM Orthogonal Frequency Division Multiplexing OIPF Open IPTV Forum OUI Organizationally Unique Identifier PAPR Peak to Average Power Ratio PLP Physical Layer Pipes PSI Program Service Information QAM Quadrature Amplitude Modulation QEF Quasi Error Free RF Radio Frequency RUT Receiver Under Test SFN Single Frequency Network SI Service Information SISO Single Input Single Output SSU System Software Update STB Set Top Box TS Transport Stream UTF Universal Transformation Format UHF Ultra High Frequency URL Uniform Resource Locator VHF Very High Frequency VSB Vestigial Sideband XML eXtensible Markup Language

2 MCMC MTSFB TC T011:2014

4. Requirements

4.1 RF

The receiver shall comply and pass the RF tests as specified in the Malaysia DVB-T2 RF Performance Test Suite Ver1.0

4.2 SI/PSI

The receiver shall comply and pass the tests as specified in Malaysia DVB-T2 SI/PSI Conformance Test Suite Ver1.0

4.3 OAD

The receiver shall comply and pass the OAD tests as specified in the Malaysia DVB-T2 Over Air Download (OAD) Test Suite Ver1.0

4.4 HbbTV

The receiver shall comply and pass the HBBTV tests as specified in the Malaysia Hybrid Broadcast TV (HbbTV) Test Suite Ver1.0

3 MCMC MTSFB TC T011:2014

5. Malaysia DVB-T2 RF Performance Test Suite Ver1.0

5.1 Revision History

No Date Description Version Remark 1 2014-06-03 First official release v1.0

5.2 Evaluation Details

Receiver Under Test (RUT) RUT Device Type (iDTV/ Set top box) RUT Firmware Version

5.3 Evaluation Results

Section Test Category Result Remarks 1.0 C/N Performance on Gaussian channel (dB) 2.0 C/N Performance on 0dB echo channel (dB) Minimum receiver signal input levels on 3.0 Gaussian channel (dBm) Minimum IRD Signal Input Levels on 0dB echo 4.0 channel 5.0 Maximum receiver signal input levels (dBm) 6.0 Immunity to "digital" signals in Other Channels Immunity to Co-Channel Interference from 7.0 Analogue TV Signals Immunity to Adjacent Channel Interference 8.0 From Analogue TV Signals Performance in Time-Varying Channels 10Hz 9.0 Doppler (5Hz after AFC) 20μs 0dB echo Synchronisation for varying echo power levels 10.0 in SFN (dB) C/(N+I) Performance in Single Frequency 11.0 Networks for more than one echo (dB) C/(N+I) Performance in Single Frequency 12.0 Networks inside the guard interval (dB) C/(N+I) Performance in Single Frequency 13.0 Networks outside the guard interval (dB) OVERALL RESULT

4 MCMC MTSFB TC T011:2014

5.4 Malaysia DVB-T2 RF Modes and Performance Figure

5.4.1 RF Profile for Malaysia

Identifier MS 1 MS 2 MS 3 MS 4 Overall FFT Size 32K 32K 32K 32K GI 1/8 19/256 1/128 1/8 SISO/MISO SISO SISO SISO SISO PAPR TR TR TR TR Bandwidth 8MHz 8MHz 8MHz 7MHz Carrier Mode Extended Extended Extended Normal Pilot Pattern PP2 PP4 PP7 PP2 L1 Modulation 64 QAM 64 QAM 64 QAM 64 QAM Data Symbols per Frame (Ldata) 43 61 59 43 OFDM Symbols per Frame (Lf) 44 62 60 44 Frame Duration (ms) 178 239 217 203 Frames Per SuperFrame 2 2 2 2 PLP #0 PLP Type 1 1 1 1 Time Interleaver Type (TIME_IL_Type) 0 0 0 0 Modulation 256 QAM 256 QAM 256 QAM 256 QAM Rate 3/4 3/5 2/3 3/4 FEC Type 64 LDPC 64 LDPC 64 LDPC 64 LDPC Rotated QAM Yes Yes Yes FEC blocks per interleaving Frame 135 200 200 132 Full channel (Trial mode) TI blocks per frame (N_TI) 2 3 3 2 Frame_Interval (I_JUMP) 1 1 1 1 TIME_IL_LENGTH 2 3 3 2 Approx. Time Interleaving Length (ms) 89 81 72 101 Data Rate (Mbit/s) 36.9256 32.49116 39.8165 31.5919

5 MCMC MTSFB TC T011:2014

5.4.2 Performance Figures for Malaysia

Test Identifier MS 1 MS 2 MS 3 MS 4 Section Section Description Performance Figure C/N Performance on Gaussian 1.0 A.1 22.9 18.9 19.7 22.9 channel (dB) C/N Performance on 0dB echo 2.0 A.2 28.0 22.6 23.9 28.0 channel (dB) Minimum receiver signal input 3.0 A.3 levels on Gaussian channel -76.2 -80.2 -79.3 -76.9 (dBm) Minimum IRD Signal Input 4.0 A.4 -71.1 -76.5 -75.1 -71.8 Levels on 0dB echo channel Receiver noise figure on A.5 1 6.0 6.0 6.0 6.0 Gaussian channel Maximum receiver signal input 5.0 A.6 -35 -35 -35 -35 levels (dBm) Immunity to "digital" signals in Other Channels Digital ACI N+/-1 C/I (dB) -28.0 -28.0 -28.0 -28.0 6.0 A.7 Digital ACI N+/-2 C/I (dB) -38.0 -38.0 -38.0 -38.0 Digital ACI N+9 C/I (dB) -28.0 -28.0 -28.0 -28.0 Immunity to Co-Channel Interference from Analogue TV Signals 7.0 A.8 PAL B/G CCI C/I (dB) 7.0 3.0 5.0 7.0 Immunity to Adjacent Channel Interference From Analogue TV Signals PAL B/G ACI C/I N+/-1 (dB) -33.0 -33.0 -33.0 -33.0 8.0 A.9 PAL B/G ACI C/I N+/-2 (dB) -44.0 -44.0 -44.0 -44.0 PAL B/G ACI C/I N+9 (dB) -44.0 -44.0 -44.0 -44.0 Performance in Time-Varying 9.0 A.10 Channels 10Hz Doppler (5Hz 3 3 3 3 after AFC) 20μs 0dB echo Synchronisation for varying 10.0 A.11 31.0 26.1 28.1 31.0 echo power levels in SFN (dB) C/(N+I) Performance in Single 11.0 A.12 Frequency Networks for more 28.0 22.6 23.9 28.0 than one echo (dB) C/(N+I) Performance in Single 12.0 A.13 Frequency Networks inside the 28.0 22.6 23.9 28.0 guard interval (dB)

1 No testing is required as this is purely calculation based

6 MCMC MTSFB TC T011:2014

Test Identifier MS 1 MS 2 MS 3 MS 4 Section Section Description Performance Figure Echo Echo Echo Echo Echo Echo Echo Echo Delay level Delay level Delay level Delay level (μs) (dBc) (μs) (dBc) (μs) (dBc) (μs) (dBc) -532 -12.0 -133 -9.5 -608 -12.0 -525 -11.5 -120 -9.0 -600 -11.5

C/(N+I) -510 -10.5 See Note 1 -90 -7.5 -580 -10.5 Performance -490 -9.0 -60 -5.0 -560 -9.0 in Single Frequency -475 -7.5 -30 -2.0 -540 -7.0 13.0 A.14 Networks -448 -2.0 -266 -2 -28 -2.0 -512 -2.0 outside the guard 448 -2.0 266 -2 28 -2.0 512 -2.0 interval (dB) 475 -7.5 30 -2.0 540 -7.0 490 -9.0 60 -5.0 560 -9.0 510 -10.5 See Note 1 90 -7.5 580 -10.5 525 -11.5 120 -9.0 600 -11.5 532 -12.0 133 -9.5 608 -12.0

Note 1: There is no allowance for echo outside guard for 19/256 PP4 in Nordig due to 19/256 guard (266s) being very close to the Nyquist limit for PP4 (298.67s). Nordig defines the max delay for echo outside guard to be 57/64*Nyquist which is equal to the guard interval of 266sec for 19/256 PP4.

7 MCMC MTSFB TC T011:2014

5.5 Test Instrument Set Up

Applicable Test Instrument Set Up Section

Figure A

1.0

2.0

3.0

4.0 5.0

9.0 10.0

Figure B

6.0

8 MCMC MTSFB TC T011:2014

Applicable Test Instrument Set Up Section

Figure C

7.0

8.0

Figure D

11.0

12.0

13.0

9 MCMC MTSFB TC T011:2014

5.6 Test Category

5.6.1 Carrier to Noise Ratio (C/N) Performance on Gaussian Channel

Section: 1.0 Test Case: C/N Performance on Gaussian channel. Receiver shall have at least the quasi error free (QEF) performance for the C/N ratios given in the Performance Figure outlined in Annex A of the SKMM MTSFB Requirement: TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver. Purpose: To test the required C/N for QEF reception in Gaussian channel. The required C/N for QEF reception in Gaussian channel shall be lesser than Expectation: the figures specified in Annex A of the SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver. Test Instrument Figure A Set Up: Set up the equipment based on the modes outlined in Annex A of the SKMM 1 MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Calibration Broadcast Service Receiver. (Start with MS 1) Requirement: 2 Ensure that the receiver signal input level (wanted signal) is set to -50dBm. 3 Perform a channel search (tune) on frequency 666MHz. 1 Adjust and measure the C/N for the range of frequencies and T2 modes defined below for QEF reception. Test Outline: 2 Remark The performance requirement is based on 30 seconds error free video.

C/N

Centre Frequency 474.0 570.0 666.0 762.0 858.0 (MHz)

Result: MS 1

MS 2 X X X X

MS 3 X X X X Modes MS 4 X X X X X

** Remark - If 'Failed', please indicate the level of failure (dB) Conformity: Passed Failed Not Tested 1 Remark: 2 3

Note: Attach graph (if any)

X Indicates no test needed

10 MCMC MTSFB TC T011:2014

5.6.2 C/N Performance on 0dB Echo Channel

Section: 2.0 Test Case: C/N Performance on 0dB echo channel. Requirement: Receiver shall have at least the QEF performance for the C/N ratios given in the Performance Figure outlined in Annex A of the SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver. Purpose: To test the required C/N for QEF reception in 0dB echo channel. Expectation: The required C/N for QEF reception in 0dB echo channel shall be lesser than the figures specified in Annex A of the SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver. Test Instrument Figure A Set Up: Set up the equipment based on the modes outlined in Annex A of the SKMM 1 MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver. (Start with MS 1)

Calibration 2 Ensure that the fading simulator is set at 0dB echo profile with a delay of Requirement: 1.95µs, 0 degree phase offset from channel centre and 0dB attenuation on the second path. 3 Ensure that the receiver signal input level (wanted signal) is set to -50dBm. 4 Perform a channel search (tune) on frequency 666MHz. 1 Adjust and measure the C/N for the range of T2 modes defined below for QEF reception in 0dB echo channel. Test Outline: 2 Remark The performance requirement is based on 30 seconds error free video.

Modes C/N MS 1 Result: MS 2 MS 3 MS 4 X

** Remark - If 'Failed', please indicate the level of failure (dB)

Conformity: Passed Failed Not Tested 1 Remark: 2 3

Note: Attach graph (if any)

X Indicates no test needed

11 MCMC MTSFB TC T011:2014

5.6.3 Minimum Receiver Signal Input Levels on Gaussian Channel

Section 3.0 Test Case Minimum receiver signal input levels on Gaussian channel.

The receiver shall provide QEF reception for the minimum signal levels (Pmin) for 8MHz Extended bandwidth as given in the Performance Figure outlined in Requirement Annex A of the SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver.

(Pmin = -105.1 dBm + NF [dB] + C/N [dB]) To verify the sensitivity of the receiver on Gaussian channel over the supported Purpose frequency range. The sensitivity shall be equal or better for all measured frequencies (channels) Expectation and for all modes specified in Annex A of the SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver. Test Instrument Figure A Set Up 1 Set up the equipment based on the modes outlined in Annex A of the SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver. (Start with MS 1) Calibration 2 Obtain the receiver signal (wanted signal) input level by taking Requirement consideration of the attenuation from the attenuator and cables. 3 Perform a channel search (tune) on frequency 666MHz, with the wanted signal level set to -50dBm. 1 Increase the received signal input level from low to higher value until QEF reception is achieved. This will be the minimum receiver signal input level. Test Outline 2 Repeat the test for the range of frequencies and T2 modes defined below. 3 Remark The performance requirement is based on 30 seconds error free video.

C/N

Centre Frequency (MHz) 474.0 570.0 666.0 762.0 858.0 MS 1

Result MS 2 X X X X

MS 3 X X X X Modes MS 4 X X X X X

** Remark - If 'Failed', please indicate the level of failure (dB) Conformity Passed Failed Not Tested 1 Remark 2 3

Note: Attach graph (if any)

X Indicates no test needed

12 MCMC MTSFB TC T011:2014

5.6.4 Minimum Integrated Receiver Decoder (IRD) Signal Input Levels on 0db Echo Channel

Section 4.0 Test Case Minimum IRD signal input levels on 0dB echo channel.

The receiver shall provide QEF reception for the minimum signal levels (Pmin) for 8MHz Extended bandwidth as given in the Performance Figure outlined in Annex Requirement A of the SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver. (Pmin = -105.1 dBm + NF [dB] + C/N [dB]) Purpose To verify the sensitivity of the receiver on frequency selective channel. The minimum signal level shall be equal or lower in dBm for all modes specified Expectation in Annex A of the SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver. Test Instrument Figure A Set Up 1 Set up the equipment based on the modes outlined in Annex A of the SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver. (Start with MS 1) 2 Ensure that the fading simulator is set at 0dB echo profile with a delay of Calibration 1.95µs, 0 degree phase offset from channel centre and 0dB attenuation on Requirement the second path. 3 Obtain the receiver signal (wanted signal) input level by taking consideration of the attenuation from the attenuator and cables. 4 Perform a channel search (tune) on frequency 666MHz with the wanted signal level set to -50dBm. 1 Increase the received signal input level from low to higher value until QEF reception is achieved. This will be the minimum receiver signal input level.

Test Outline 2 Repeat the test for the range of T2 modes defined below. Remark 3 1. The performance requirement is based on 30 seconds error free video. 2. 0dB echo profile must be activated when measuring the power level.

Minimum input signal levels

0db echo (μs) 10 26 133 224 253 426 MS 1 X X X Result X X X MS 2 MS 3 X X X X Modes MS 4 X X X X X X

** Remark - If 'Failed', please indicate the level of failed (dB)

Conformity Passed Failed Not Tested 1 Remark 2 3

Note: Attach graph (if any)

X Indicates no test needed

13 MCMC MTSFB TC T011:2014

5.6.5 Maximum Receiver Signal Input Levels

Section 5.0 Test Case Maximum receiver signal input levels. The receiver shall provide QEF reception for DVB-T and DVB-T2 signals up to the Requirement level specified in Annex A of SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver. Purpose To test that the receiver is able to handle high power RF signals. The reception shall be QEF for input level higher than or equal to the level for all Expectation modes specified in Annex A of SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver. Test Instrument Figure A Set Up Set up the equipment based on the modes outlined in Annex A of the SKMM 1 MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver. (Start with MS 1) Calibration Requirement 2 Obtain the receiver signal (wanted signal) input level by taking consideration of the attenuation from the attenuator and cables. 3 Perform a channel search (tune) on frequency 666MHz. 1 Increase the received signal input level until QEF reception is achieved. Ensure that the receiver is able to output the content of the TS source as the receiver signal level increases.

Test Outline 2 Repeat the test for the range of T2 modes defined below. 3 Remark The performance requirement is based on 30 seconds error free video with the receiver input signal level calculated as a function of attenuation.

Modes Maximum input signal levels MS 1

Result MS 2 MS 3 MS 4 X ** Remark - If 'Failed', please indicate the level of failure (dBm)

Conformity Passed Failed Not Tested 1 Remark 2 3

Note: Attach graph (if any)

X Indicates no test needed

14 MCMC MTSFB TC T011:2014

5.6.6 Immunity to "Digital" Signals in Other Channels

Section 6.0 Test Case Immunity to "digital" signals in Other Channels. The receiver shall permit an interfering DVB-T or DVB-T2 signal for the supported frequencies outlined in Annex A of the SKMM MTSFB TC T004:2013 - Requirement Specification for Digital Terrestrial Television Broadcast Service Receiver with a minimum interference to signal level ratio (I/C) while maintaining QEF reception. To verify the QEF reception for digital signal interference on adjacent or other Purpose channels. The wanted DVB-T2 signal shall be QEF for the interference signal levels Expectation specified for all modes outlined in Annex A of the SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver. Test Instrument Figure B Set Up 1 Set up the equipment based on the modes outlined in Annex A of the SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver. (Start with MS 1) 2 Perform a channel search (tune) on frequency 666MHz, with the interferer switched off. 3 With Channel B or the interferer signal level set to -20dBm, decrease the Calibration receiver signal input level (Channel A or the wanted signal) until QEF is Requirement obtained. 4 Remark 1. Require the interferer to operate at DVB-T2 extended mode for worst case testing. 2. Ensure that the interferer signal does not have too high shoulders to avoid out-of-band emissions in the reception of the wanted signal. Use a band pass filter on the interference signal if necessary. 1 Select the frequencies for Channel A and Channel B based on the required values indicated in the Result Table.

Test Outline 2 The difference in signal level shall be measured at QEF reception. 3 Remark The performance requirement is based on 30 seconds error free video.

15 MCMC MTSFB TC T011:2014

Centre Frequency (MHz) - C/I 666MHz Interferer Centre Frequency 650 658 674 (MHz) 682 738

MS 1

MS 2

MS 3 Modes MS 4 X X X X X Result

Centre Frequency (MHz) - C/I 786MHz Interferer Centre Frequency 770 778 794 (MHz) 802 858

MS 1

MS 2

MS 3 Modes MS 4 X X X X X

** Remark - If 'Failed', please indicate the level of failure (dB) Conformity Passed Failed Not Tested 1 Remark 2 3

Note: Attach graph (if any)

X Indicates no test needed

16 MCMC MTSFB TC T011:2014

5.6.7 Immunity to Co-Channel Interference from Analogue TV Signals

Section 7.0 Test Case Immunity to Co-Channel Interference from Analogue TV Signals. The receiver shall perform better than the RF figure specified in Annex A of the SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Requirement Broadcast Service Receiver when the signal is exposed to interference from a co-channel G/PAL signal including video with teletext, FM audio and a NICAM sub carrier while maintaining QEF reception. To verify the QEF reception for DVB-T2 receiver when there is a co-channel Purpose interference from analogue TV. The received signal shall have a 30s error free video for DVB-T2 modes with C/I Expectation equal or better than the requirement. Test Instrument Figure C Set Up 1 Set up the equipment based on the modes outlined in Annex A of the SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver. (Start with MS 1) 2 Ensure the following: 1. 10% modulation depth for vision carrier. 2. NICAM signal level is at -20dB and +5.85MHz relative to the vision carrier. 3. Insert 12 lines of teletext. 3 Set the analogue TV source with the following requirements: Calibration 1. The analogue TV source and DVB-T2 modulator shall be connected to Requirement the same reference signal (10MHz). 2. The analogue TV source shall have 0Hz centre frequency offset from the digital TV source. 3. The analogue TV source should not have too high out-of-band emissions to avoid interference to other frequencies. 4. Use a colour bar 75% as the input for PAL signal. 5. FM sound carrier can be modulated at a deviation of 1kHz - 50kHz tone, and the level set at -13dB relative to the vision carrier. 4 Calibrate the C/I level (Att C and Att I). 5 Ensure that the receiver signal input level (wanted signal) is set to -50dBm. 1 Execute the test for the range of the frequencies and modes outlined in the Result Table. 2 Increase the C/I from low value to higher value until the QEF measurement Test Outline is achieved. 3 Remark The performance requirement is based on 30 seconds error free video.

17 MCMC MTSFB TC T011:2014

C/I

Centre Frequency (MHz) 666 MS 1 Result MS 2

MS 3 Modes MS 4 X

** Remark - If 'Failed', please indicate the level of failure (dB) Conformity Passed Failed Not Tested 1 Remark 2 3

Note: Attach graph (if any)

X Indicates no test needed

18 MCMC MTSFB TC T011:2014

5.6.8 Immunity to Adjacent Channel Interference from Analogue TV Signals

Section 8.0 Test Case Immunity to Adjacent Channel Interference From Analogue TV Signals. The receiver shall perform better than the RF figure specified in Annex A of the SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Requirement Broadcast Service Receiver when the signal is exposed to interference from adjacent G/PAL signal including video with teletext, FM audio and a NICAM sub carrier while maintaining QEF reception. To verify the QEF reception for DVB-T2 receiver when there is adjacent channel Purpose interference from analogue TV. The received signal shall have a 30s error free video for DVB-T2 modes with C/I Expectation equal or better than the requirement. Test Instrument Figure C Set Up 1 Set up the equipment based on the modes outlined in Annex A of the SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver. (Start with MS 1) 2 Ensure the following: 1. 10% modulation depth for vision carrier. 2. NICAM signal level is at -20dB and +5.85MHz relative to the vision carrier. 3. Insert 12 lines of teletext. Calibration 3 Set the analogue TV source with the following requirements: Requirement 1. The analogue TV source and DVB-T2 modulator shall be connected to the same reference signal (10MHz). 2. The analogue TV source shall have a centre frequency value from the digital TV source (indicated in the Result Table below). 3. The analogue TV source should not have too high out-of-band emissions to avoid interference to other frequencies. 4. Use a colour bar 75% as the input for PAL signal. 5. FM sound carrier can be modulated at a deviation of 1kHz - 50kHz tone, and the level set at -13dB relative to the vision carrier. 4 Calibrate the C/I level (Att C and Att I).

5 Ensure that the receiver input level for analogue TV (unwanted signal) is set to -25dBm (defined as the R.M.S value of the vision carrier at peaks of the modulated envelope). 1 Execute the test for the range of the frequencies and modes outlined in the Result Table. 2 Increase the C/I from high value to lower value until the QEF measurement Test Outline is achieved. This should be achieved by keeping the level of the unwanted signal and decreasing the level of the wanted signal. 3 Remark The performance requirement is based on 30 seconds error free video.

19 MCMC MTSFB TC T011:2014

Centre Frequency (MHz) - 666MHz C/I Interferer Centre Frequency (MHz) 650 658 674 682 738 MS 1

MS 2

MS 3 Modes MS 4 X X X X X Result

Centre Frequency (MHz) - 786MHz C/I Interferer Centre Frequency (MHz) 770 778 794 802 858 MS 1

MS 2

MS 3 Modes MS 4 X X X X X

** Remark - If 'Failed', please indicate the level of failure (dB) Conformity Passed Failed Not Tested 1 Remark 2 3

Note: Attach graph (if any)

X Indicates no test needed

20 MCMC MTSFB TC T011:2014

5.6.9 Performance in Time-Varying Channels 10Hz Doppler (5Hz after Automatic Frequency Control (AFC)) 20μs 0dB Echo

Section 9.0 Performance in Time-Varying Channels 10Hz Doppler (5Hz after AFC) 20μs 0dB Test Case echo. The receiver shall be able to operate with all signal time variations. The increase in required C/N for QEF reception shall be less than the RF figures specified in Requirement Annex A of the SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver, corresponding to a Doppler shift of +/- 10Hz (5Hz after AFC) compared to a 0dB echo with a delay of 20μs. To verify the QEF reception for DVB-T2 receiver on a channel where time Purpose variation exists. The increase in the required C/N shall be less than the RF figures specified in Annex A of the SKMM MTSFB TC T004:2013 - Specification for Digital Expectation Terrestrial Television Broadcast Service Receiver for 0dB 20μs echo from frequency separation 1Hz to 10Hz. Test Instrument Figure A Set Up 1 Set up the equipment based on the modes outlined in Annex A of the SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver. (Start with MS 1) 2 Ensure that the fading simulator is set at 0dB echo profile with a delay of 20µs, 0 degree phase offset from channel centre and 0dB attenuation on the second path (for 1Hz frequency separation). Calibration 3 Configure the following: Requirement 1. Path 1: Static, 0dB attenuation, and 0μs delay. 2. Path 2: Pure Doppler, 0dB attenuation, and 20μs delay. 4 Ensure that the receiver signal input level (wanted signal) is set to -50dBm (with no noise applied). 5 Perform a channel search (tune) on frequency 666MHz. 1 Execute the test for the range of the frequencies and modes outlined in the Result Table. 2 Increase the C/I from low value to higher value until the QEF measurement Test Outline is achieved. 3 Remark The performance requirement is based on 30 seconds error free video.

21 MCMC MTSFB TC T011:2014

Centre Frequency C/N (MHz) 666MHz Frequency Separation Max difference Pass/ 1 5 10 (Hz) dB Fail Result MS 1

MS 2

MS 3 Modes MS 4 X X X X X

** Remark - If 'Failed', please indicate the level of failure (dB) Conformity Passed Failed Not Tested 1 Remark 2 3

Note: Attach graph (if any)

X Indicates no test needed

22 MCMC MTSFB TC T011:2014

5.6.10 Synchronization for Varying Echo Power Levels in Single Frequency Networks (SFN)

Section 10.0 Test Case Synchronization for varying echo power levels in SFN. The required C/N value for QEF reception as specified in Annex A of the SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver shall be obtained when the channel contains two Requirement paths with relative delay from 1.95μs up to 0.95 x GI length and the relative power levels of the two paths are dynamically varying including 0dB echo level crossing. To verify the SFN synchronization when the amplitude of the echo compared Purpose to the amplitude of the direct signal varies in a function of time. The receiver shall maintain SFN synchronization and the C/N value shall not exceed the specified value outlined in Annex A of the SKMM MTSFB TC Expectation T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver when the amplitude of the echo signal varies in time. Test Instrument Set Figure A Up 1 Set up the equipment based on the modes outlined in Annex A of the SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver. (Start with MS 1) 2 Set up the fading simulator as follows, disconnecting and re-connecting the wanted signal after the echo delay is changed between each test. 1. Path 1 (direct): 0dB attenuation, 0μs delay. Calibration 2. Path 2 (1st echo): 0dB attenuation and delay value from the Result Requirement Table. 3. Path 3 (2nd echo): 1dB attenuation and delay value from the Result Table with 0.1Hz frequency separation. 3 Ensure that the receiver signal input level (wanted signal) is set to - 50dBm (with no noise applied). 4 Perform a channel search (tune) on frequency 666MHz. 1 Increase the C/N from low to higher value until QI reception is achieved. 2 Repeat the test for the range of echo delay values and T2 modes defined in the Result Table below. 3 Remark 1. The performance requirement is based on 30 seconds error free Test Outline video. 2. The QI reception shall be obtained when the channel contains two paths with relative delay from 1.95µs up to 0.95 x GI length and the relative power levels of the two paths are dynamically varying (inclusive of 0dB echo level crossing). 3. FRY input signal to the receiver shall be disconnected when changing the echo delay.

23 MCMC MTSFB TC T011:2014

C/N

0db echo (is) 10 26 133 224 253 426 MS 1 X X X Result X X X MS 2 MS 3 X X X X Modes MS 4 X X X X X X

** Remark - If 'Failed', please indicate the level of failure (dB) Conformity Passed Failed Not Tested 1 Remark 2 3

Note: Attach graph (if any)

X Indicates no test needed

24 MCMC MTSFB TC T011:2014

5.6.11 C/(N+I) Performance in SFN for more than one echo

Section 11.0 Test Case C/(N+I) Performance in SFN for more than one echo. The required C/N value for QI reception as specified in Annex A of SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Requirement Service Receiver shall be obtained when the channel contains two static paths with relative delay from 1.95μs up to 0.95 x GI length, independently of the relative amplitudes and phases of the two paths. To verify the SFN synchronization of the receiver when two echo signals are Purpose present. The receiver shall synchronize all combinations defined in the result table, with the C/N values not exceeding the required C/N figured defined outlined in Annex Expectation A of the SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver. Test Instrument Figure D Set Up 1 Set up the equipment based on the modes outlined in Annex A of the SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver. (Start with MS 1) 2 Set up the fading simulator as follows, disconnecting and re-connecting the wanted signal after the echo delay is changed between each test 1. Path 1 (static): 0dB attenuation, 0μs delay and 0 degree phase. Calibration 2. Path 2 (Pre echo): Follow the values specified in the table below (with 0 Requirement degree phase). 3. Path 3 (Post echo): Follow the values specified in the table below (with 0 degree phase). 3 Ensure that the receiver signal input level (wanted signal) is set to -50dBm (with no noise applied). 4 Perform a channel search (tune) on frequency 666MHz. 1 Increase the C/N from low to higher value until QI reception is achieved. 2 Repeat the test for the range of echo delay values and T2 modes defined in the Result Table below. Test Outline 3 Remark 1. The performance requirement is based on 30 seconds error free video. 2. FRY input signal to the receiver shall be disconnected when changing the echo delay.

25 MCMC MTSFB TC T011:2014

Modes MS 1 MS 2 MS 3 MS 4 Path 2 Pre -200.1μs -120.1μs -13.1μs X Relative Delay echo Difference Path 3 Post +200.0μs +120.0μs +13.0μs X echo Path 2 Pre Path 3 Post C/N echo echo 0 0 X 3 3 X 6 6 X 9 9 X 12 2 X 15 15 X 18 18 X

21 21 X Result

15 0 X

(dB)

15 3 X 15 6 X 15 9 X

Attenuation 15 12 X 15 18 X 15 21 X 0 15 X 3 15 X 6 15 X 9 15 X 12 15 X 18 15 X 21 15 X ** Remark - If 'Failed', please indicate the level of failure (dB)

Conformity Passed Failed Not Tested 1 Remark 2 3

Note: Attach graph (if any)

X Indicates no test needed

26 MCMC MTSFB TC T011:2014

5.6.12 C/(N+I) Performance in Single Frequency Networks inside the Guard Interval (GI)

Section 12.0 Test Case C/(N+I) Performance in SFN inside the guard interval. The required C/N value for QI reception as specified in Annex A of the SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Requirement Service Receiver shall be obtained when the channel contains two static paths with relative delay from 1.95μs up to 0.95 x GI length, independently of the relative amplitudes and phases of the two paths. Purpose To verify the required C/N for echoes in SFN inside the guard interval. The receiver shall synchronize in all echo attenuation and delay combinations defined in the result table, with the C/N values for 0dB echo not exceeding the Expectation required C/N figures outlined in Annex A of the SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver. Test Instrument Figure D Set Up 1 Set up the equipment based on the modes outlined in Annex A of the SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver. (Start with MS 1)

Calibration 2 Ensure that the fading simulator is set at 0dB echo profile with a delay of Requirement 1.95µs, 0 degree phase offset from channel centre and 0dB attenuation on the second path. 3 Ensure that the receiver signal input level (wanted signal) is set to -50dBm. 4 Perform a channel search (tune) on frequency 666MHz. 1 Apply noise and increase the C/N from low to higher value until QI reception is achieved. 2 Repeat the test for the range of echo values and T2 modes defined in the Result Table below. 3 Remark Test Outline 1. The performance requirement is based on 30 seconds error free video. 2. FRY input signal to the receiver shall be disconnected when changing the echo delay and attenuation level. 3. The delay of the echo shall be maintained constant during the changes of attenuation.

27 MCMC MTSFB TC T011:2014

Delay(µs) -426 -224 -1.95 1.95 224 426 Attenuation (dB) 0 20 0 20 0 20 0 20 0 20 0 20 Mode X X X MS 1

Delay(µs) -253 -133 -1.95 1.95 133 253

Result Attenuation (dB) 0 20 0 20 0 20 0 20 0 20 0 20 Mode X X X MS 2

Delay(µs) -26 -10 -1.95 1.95 10 26 Attenuation (dB) 0 20 0 20 0 20 0 20 0 20 0 20 Mode MS 3 X X X

** Remark - If 'Failed', please indicate the level of failure (dB) Conformity Passed Failed Not Tested 1 Remark 2 3

Note: Attach graph (if any)

X Indicates no test is needed

28 MCMC MTSFB TC T011:2014

5.6.13 C/(N+I) Performance in SFN outside the Guard Interval

Section 13.0 Test Case C/(N+I) Performance in SFN outside the guard interval. For echoes outside the guard interval, QI reception shall be possible with echo Requirement levels up to the values outlined in Annex A of the SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver. Purpose To verify the SFN synchronization in SFN for echoes outside guard interval. The echo levels shall be equal or higher compared to the FRY figures outlined in Expectation Annex A of the SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver. Test Instrument Figure D Set Up 1 Set up the equipment based on the modes outlined in Annex A of the SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver. (Start with MS 1) 2 Configure the echo signal with channel simulator relative delay difference Calibration set at 448µs. Requirement 3 Set the echo level to 0 dB. 4 Ensure that the receiver signal input level (wanted signal) is set to -50dBm. 5 Perform a channel search (tune) on frequency 666MHz. 1 Decrease the echo level from high to lower value until QEF reception is achieved. 2 Repeat the test for the range of echo values and T2 modes defined in the Test Outline Result Table below. 3 Remark 1. The performance requirement is based on 30 seconds error free video.

29 MCMC MTSFB TC T011:2014

MS 1 MS 2 MS 3 MS 4 Echo Echo Echo Echo Echo Echo Echo Echo Delay level Delay level Delay level Delay level (μs) (dBc) (μs) (dBc) (μs) (dBc) (μs) (dBc) -532 X X -133 -608 X

-525 X X -120 -600 X

-510 X X -90 -580 X

-490 X X -60 -60 X

Result -475 X X -30 -540 X

Modes -448 -266 -28 -512 X

448 266 28 512 X

475 X X 30 540 X

490 X X 60 560 X

510 X X 90 580 X

525 X X 120 600 X

532 X X 133 608 X

** Remark - If 'Failed', please indicate the level of failure (dB) Conformity Passed Failed Not Tested 1 Remark 2 3

Note: Attach graph (if any)

X Indicates no test is needed

30 MCMC MTSFB TC T011:2014

6. Malaysia DVB-T2 SI/PSI Conformance Test Suite Ver1.0

6.1 Revision History

No Date Description Version Remark 1 2014-06-03 First official release v1.0

6.2 Evaluation Details

Receiver Under Test (RUT) RUT Device Type (iDTV/Set top box) RUT Firmware Version

6.3 Evaluation Results

Total Test Test Category Pass Fail Not Tested Item 1.0 Basic SI/PSI 2.0 Logical Channel Numbering 3.0 Network Evolution 4.0 Character Test 5.0 Active Format Description 6.0 Multiple Physical Layer Pipes (MPLP) 7.0 Declaration Results Total

Test Approved by Stamp Signature

31 MCMC MTSFB TC T011:2014

6.4 Test Category

6.4.1 Basic SI/PSI Test

Description Test Streams : Stream Configuration :

This test contains the following sections: MYS_SIPSI_1a.ts Modulation Type : DVB-T2 Channel Frequency : 474 MHz - 858 MHz Section 1.1 : Service Installation & Information Note : Bandwidth : 8 MHz Section 1.2 : Event Information The Test Streams are available with the Mode : 32K Section 1.3 : Codec Information Communication and Multimedia Certification Guard Interval : 1/128 Section 1.4 : Audio & Subtitle Language Section, SIRIM QAS International Sdn Bhd Modulation : 256 QAM Note : Cell Identifier : 0 Reference Document (Ref.): SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver.

6.4.1.1 Service Installation and Information

Section 1.1 : Service Installation and Information No. Test Instruction Expectation Ref. Result Remarks 1.1.1 Play out MYS_SIPSI_1a.ts and perform Observe the service name and LCN numbering for each receiver full scan. service in the service list and ensure they are correctly arranged in an ascending order as below: Enter each service and ensure that all of them are accessible via numerical keys. LCN 208 : TV1_SD 3.2.11.1 Confirm the correct service name and LCN 209 : TV2_HD LCN numbering in each service. LCN 210 : TV3_HD LCN 211 : TV4_SD LCN 212: TV5_Radio LCN 213: TV6_Radio

32 MCMC MTSFB TC T011:2014

Section 1.1 : Service Installation and Information No. Test Instruction Expectation Ref. Result Remarks 1.1.2 Check clock information. Thursday 12th April 21:00:00. 3.2.13

6.4.1.2 Event Information

Section 1.2 : Event Information No. Test Instruction Expectation Ref. Result Remarks 1.2.1 Play out MYS_SIPSI_1a.ts and Service Name TV1_SD perform receiver full scan. 1.2.2 Event start and Thursday 12th April

end time 21:00:00 - 21:30:00 (30 minutes). Using numerical keys, press '208' to 1.2.3 enter service LCN 208 TV1_SD. Event name TV1_SD Present Event

1.2.4 Access the banner and check the Short Event Short Event Description for TV1_SD present (now) event information. Description Present Event. 1.2.5 Extended Extended Event Description for TV1_SD Note: Event Present Event: TV1_SD has a parental The event description may optionally Description rating of 9 years and its genre is 3.2.12 be truncated by receiver when the classified as Movie/Drama or Adult 3.2.12.1 character length exceeds the allocated Movie/Drama. area for display of event description. 1.2.6 Rating 9 years 1.2.7 Next, access the banner again and Service Name TV1_SD check the following (next) event 1.2.8 Event start and Thursday 12th April information. end time 21:30:00 - 22:00:00 (30 minutes).

1.2.9 Note: Event name TV1_SD Following Event The event description may optionally 1.2.10 be truncated by receiver when the Short Event Short Event Description for TV1_SD Description Following Event.

33 MCMC MTSFB TC T011:2014

Section 1.2 : Event Information No. Test Instruction Expectation Ref. Result Remarks 1.2.11 character length exceeds the allocated Extended Extended Event Description for TV1_SD area for display of event description. Event Following Event: TV1_SD has a parental Description rating of 15 years and its genre is classified as News/ Current Affairs or Documentary. 1.2.12 Rating 15 years

1.2.13 Using numerical keys, press '209' to Service Name TV2_HD

enter service LCN 209 TV2_HD.

1.2.14 Access the banner and check the Event start and Thursday 12th April 2012 3.2.12 present (now) event information. end time 21:00:00 - 21:30:00 (30 minutes). 3.2.12.1 1.2.15 Event name TV2_HD Present Event 1.2.16 Note: The event description may Short Event Short Event Description for TV2_HD optionally be truncated by receiver Description Present Event. when the character length exceeds the 1.2.17 allocated area for display of event Extended Extended Event Description for TV2_HD description. Event Present Event: TV2_HD has a parental Description rating of 11 years and its genre is classified as Show/ Game Show or Variety Show.

34 MCMC MTSFB TC T011:2014

6.4.1.3 Codec Information

Section 1.3 : Codec Information No. Test Instruction Expectation Ref. Result Remarks 1.3.1 Play out MYS_SIPSI_1a.ts and perform Video The 576i (16:9) MPEG-4 AVC MP@L3 SD 3.2.3 receiver full scan. Component “Flowers" video shall be presented. 3.2.3.1 3.2.3.2 1.3.2 Using numerical keys, press '208' to Audio "Guitar Solo" audio shall be selectable 3.2.4 enter service LCN 208 TV1_SD. Component when the audio selection is set to English. 3.2.4.1

1.3.3 Using numerical keys, press '209' to Video The 1080i MPEG-4 AVC MP@L4 HD 3.2.3 enter service LCN 209 TV2_HD. Component "Village" video shall be presented. 3.2.3.1 3.2.3.2 1.3.4 Using numerical keys, press '210' to Video The 720p MPEG-4 AVC MP@L4 HD 3.2.3 enter service LCN 210 TV3_HD. Component "Park" video shall be presented. 3.2.3.1 3.2.3.2 1.3.5 Using numerical keys, press '211' to Video The 576i (4:3) MPEG-4 AVC MP@L3 SD 3.2.3 enter service LCN 211 TV4_SD. Component "Bridge" video shall be presented. 3.2.3.1 3.2.3.2 1.3.6 Play out ChID_voices_swp_ddp_DVB_ Audio Audio alternates between each channel h264_25fps.trp and perform receiver full Component should be presented. 3.2.4

scan. Enter Service Dolby Labs Test 3.2.4.1 Stream Note: Audio presentation is optional.

35 MCMC MTSFB TC T011:2014

6.4.1.4 Audio and Subtitle Language

Section 1.4 : Audio and Subtitle Language No. Test Instruction Expectation Ref. Result Remarks 1.4.1 Play out MYS_SIPSI_1a.ts and Audio "Keyboard" audio shall be selectable when 3.2.4 perform receiver full scan. the audio selection is set to Bahasa 3.2.4.1 Melayu (MSA). 3.2.6.2 Enter Service TV_SD 1.4.2 Firstly, perform the following setting: Subtitle Bahasa Melayu subtitles, “SIPSI Test. Enable Subtitles Subtitle 1, number…” shall be selectable 3.2.5 when the subtitle selection is set to 3.2.6.1 Bahasa Melayu (MSA). 1.4.3 Note 1: All subtitles presented are in Audio "Bell rings" audio shall be selectable when 3.2.4 English. the audio selection is set to Chinese 3.2.4.1 (ZHO). 3.2.6.2 1.4.4 Note 2: If subtitles do not display due Subtitle Chinese subtitles, “SIPSI Test. Subtitle 2, to PTS-PCR difference, then subtitle number…", shall be selectable when the 3.2.5 tests can be considered a PASS. subtitle selection is set to Chinese (ZHO). 3.2.6.1 1.4.5 Please indicate in Remarks if this is the Audio "Drum Solo" audio shall be selectable 3.2.4 case, and also ensure to make self- when the audio selection is set to Tamil 3.2.4.1 declaration in section 7.1 regarding the (TAM). 3.2.6.2 Display of Subtitles 1.4.6 Subtitle Tamil subtitles, “SIPSI Test. Subtitle 3, number…” shall be selectable when the 3.2.5 subtitle selection is set to Tamil (TAM). 3.2.6.1

1.4.7 Audio "Guitar Solo" audio shall be selectable 3.2.4 when the audio selection is set to English. 3.2.4.1 3.2.6.2

36 MCMC MTSFB TC T011:2014

Section 1.4 : Audio and Subtitle Language No. Test Instruction Expectation Ref. Result Remarks 1.4.8 Subtitle English subtitles, "SIPSI Test. Subtitle 0, 3.2.5 number…", shall be selectable when the 3.2.6.1 subtitle selection is set to English. 1.4.9 Audio Receiver shall present any of the following audio components when the audio selection is set to other languages besides Bahasa Melayu, English, Chinese and 3.2.4 Tamil: 3.2.4.1

3.2.6.2 English (ENG) - "Guitar Solo" Bahasa Melayu (MSA) - "Keyboard" Chinese (ZHO) - "Bell rings" Tamil (TAM) - "Drum Solo" 1.4.10 Subtitle Receiver shall present any of the following subtitle components when the subtitle selection is set to other languages besides Bahasa Melayu, English, Chinese and Tamil: 3.2.5 3.2.6.1 English (ENG) Subtitles Bahasa Melayu (MSA) Subtitles Chinese (ZHO) Subtitles Tamil (TAM) Subtitles 1.4.11 Enter Service TV2_HD. Audio "Birds" audio shall be selectable when the audio selection is set to Original Audio 3.2.4 Firstly, perform the following settings : (QAA). 3.2.4.1

- Enable Subtitles

37 MCMC MTSFB TC T011:2014

6.4.1.5 Results of Basic SI/PSI Test

Results of Basic SI/PSI Test Number of Passes Number of Fails Number of Not Tested Total test items

6.4.2 Logical Channel Numbering (LCN) Test

Description Test Streams : Stream Configuration :

This test contains the following sections: MYS_SIPSI_2.1a.ts Modulation Type : DVB-T2 MYS_SIPSI_2.1b.ts Channel Frequency : 474 MHz - 858 MHz Section 2.1 : Decoding of LCN descriptors MYS_SIPSI_2.3.ts Bandwidth : 8 MHz 2.1.1 LCN V1 Descriptors FGN_SIPSI_2.2.ts Mode : 32K 2.1.2 LCN V2 Descriptors FGN_SIPSI_2.3.ts Guard Interval : 1/128 Section 2.2 : Foreign Services MYS_SIPSI_2.4.ts Modulation : 256 QAM Section 2.3 : No LCN Descriptor Cell Identifier : 0 Section 2.4 : Regional Broadcast Management Note: Note : Note : In the case of simultaneous playing of two streams, the Reference Document (Ref.) : SKMM MTSFB TC The Test Streams are available with the streams should be played out at different frequencies. T004:2013 - Specification for Digital Terrestrial Communication and Multimedia Certification For example, one stream is played out at 474 MHz and Television Broadcast Service Receiver. Section, SIRIM QAS International Sdn Bhd the other is played out at 858 MHz.

38 MCMC MTSFB TC T011:2014

6.4.2.1 Decoding of LCN descriptors

Section 2.1 : Decoding of LCN descriptors Test No. Instructions Expectations Ref. Result Remarks Category 2.1.1 LCN V1 Play out Total of 6 services shall be visible in the service list and shall be in descriptors MYS_SIPSI_2.1a.ts ascending order as below: and perform receiver auto scan. LCN 010 MYS_TV 1 LCN 031 MYS_TV 4.1/MYS_TV 4.2 LCN 561 MYS_Radio 9 LCN 800++ MYS_TV 4.1/MYS_TV 4.2 LCN 800++ MYS_TV 6 LCN 800++ Service with no LCN

Confirm that receiver shall be able to access each service normally via numeric button and service list.

Using numerical keys, press '102' to enter service LCN 102 3.2.11.2 MYS_Radio 8. 3.2.11.4 'Drum Solo' audio shall be presented. 3.2.19

This service is hidden and can only be selected using direct key entry.

Using numerical keys, press '031' to enter service LCN 031 MYS_TV 4.1/ or MYS_TV 4.2. 'Bridge' video and 'Keyboard' audio shall be presented.

Select 'Service with no LCN' service. LCN 800++ shall be assigned to this service.

'Bridge' video and 'Guitar Solo' audio shall be presented.

39 MCMC MTSFB TC T011:2014

Section 2.1 : Decoding of LCN descriptors Test No. Instructions Expectations Ref. Result Remarks Category 2.1.2 LCN V2 Play out Total of 6 services shall be visible in the service list and shall be in descriptors MYS_SIPSI_2.1b.ts ascending order as below: and perform receiver auto scan. LCN 005 TV5 LCN 055 TV55_A LCN 166 Radio 5 LCN 800++ TV 55_B LCN 800++ TV 132 LCN 800++ Service with no LCN

Service with LCN 300 is hidden and shall not appear in the service list.

Confirm that receiver is able to access each service normally via 3.2.11.3 numerical keys. 3.2.11.4 3.2.19 Using numerical keys, press '300' to enter service LCN 300 Radio7. This service is hidden and can only be selected using direct key entry.

'Drum Solo' audio shall be presented.

Using numerical keys, press '055' to enter service LCN 055 TV55_A. 'Bridge' video and 'Keyboard' audio shall be presented.

Select 'Service with no LCN' service.

LCN 800++ shall be assigned to this service. 'Bridge' video and 'Guitar Solo' audio shall be presented.

40 MCMC MTSFB TC T011:2014

6.4.2.2 Foreign Services

Section 2.2 : Foreign Services Test No. Instructions Expectations Ref. Result Remarks Category 2.2.1 Foreign Play out Total of 12 services shall be visible in the service list and shall be an Service MYS_SIPSI_2.1b.ts ascending order as below: and FGN_SIPSI_2.2.ts LCN 005 TV 5 simultaneously and LCN 055 TV 55_A/TV 55_B perform receiver's LCN 166 Radio 5 auto scan method. LCN 800++ TV 55_A/TV 55_B LCN 800++ TV 132 LCN 800++ Service with no LCN Note: Please refer to LCN 800++ SI Television 100 the stream LCN 800++ TV Service 101 configuration LCN 800++ TV Service 102 method as stated LCN 800++ MI Television 201 above LCN 800++ MI Television 202 3.2.11.4 LCN 800++ LL Television 300 3.2.19

Confirm that receiver is able to access to each service normally via numerical keys and service list.

Service with LCN 300 is hidden and shall not appear in the service list. Confirm that receiver is able to access each service normally via numerical keys.

Using numerical keys, press '300' to enter service LCN 300 Radio7. This service is hidden and can only be selected using direct key entry. 'Drum Solo' audio shall be presented.

Confirm that all of the foreign services are assigned with channel number 800++.

41 MCMC MTSFB TC T011:2014

6.4.2.3 No LCN Descriptor

Section 2.3 : No LCN Descriptor Test No. Instructions Expectations Ref. Result Remarks Category 2.3.1 No LCN Play out Total of 12 services shall be visible in the service list and shall be an Descriptor MYS_SIPSI_2.3.ts ascending order as below: and FGN_SIPSI_2.3.ts LCN 001 TV 5 simultaneously and LCN 002 TV 55_A perform receiver's LCN 003 Radio 5 auto scan method. LCN 004 Radio 7 LCN 005 TV 55_B 3.2.11.4 LCN 006 TV 132 LCN 007 SI Television 100 3.2.19 LCN 008 TV Service 101 LCN 009 TV Service 102 LCN 010 MI Television 201 LCN 011 MI Television 202 LCN 012 LL Television 300

Confirm that receiver is able to access each service normally via numerical keys and service list.

42 MCMC MTSFB TC T011:2014

6.4.2.4 Regional Broadcast Management

Section 2.4 : Regional Broadcast Management Test No. Instructions Expectations Ref. Result Remarks Category 2.4.1 Regional Play out Total of 9 services shall be visible in the service list and shall be Broadcast MYS_SIPSI_2.4.ts in ascending order as below for the Central Region channel list Management and perform receiver (ID:0x0001) auto scan. LCN 001 MY_TV 1 1. Select the channel LCN 005 MY_TV 15 list for Central LCN 007 MY_TV 2 Region LCN 033 MY_HDTV 4 (ID : 0x0001) in the LCN 155 MYTV_10 3.2.11.5 receiver's LCN 431 MY Radio 6 3.2.19 LCN 611 MY_TV 5 LCN 701 MY_TV 7 LCN 800++ MY_TV 8

Confirm that receiver is able to access each service normally via numerical keys and service list

Note: Data type service is optional.

43 MCMC MTSFB TC T011:2014

Section 2.4 : Regional Broadcast Management Test No. Instructions Expectations Ref. Result Remarks Category 2. Perform receiver Total of 9 services shall be visible in the service list and shall be auto scan again in ascending order as below for the Southern Region channel list and select the (ID:0x0002) channel list for Southern region LCN 002 MY_TV 2 (ID : 0x0002) in the LCN 006 MY_TV 15 receiver's channel LCN 010 MY_TV 1 list menu. LCN 036 MY_HDTV 4 LCN 105 MYTV_10 3.2.11.5

LCN 437 MY_Radio 6 3.2.19 LCN 617 MY_TV 5 LCN 770 MY_TV 7 LCN 800++ MY_TV 8

Confirm that receiver is able to access each service normally via numerical keys and service list.

Note: Data type service is optional.

6.4.2.5 Results of LCN Test

Results of LCN Test Number of Passes Number of Fails Number of Not Tested Total test items

44 MCMC MTSFB TC T011:2014

6.4.3 Network Evolution

Description Test Streams : Stream Configuration :

This test contains the following sections: MYS_SIPSI_3.1a.ts Modulation Type : DVB-T2 MYS_SIPSI_3.1a_addition.ts Channel Frequency : 474 MHz - 858 MHz Section 3.1 : Service Addition and Deletion MYS_SIPSI_3.1a_deletion.ts Bandwidth : 8 MHz Section 3.2 : Clash LCN Resolution MYS_SIPSI_3.2a.ts Mode : 32K Section 3.3 : Multiplex Addition and Deletion MYS_SIPSI_3.2b.ts Guard Interval : 1/128 Section 3.4 : Service and Event Updates MYS_SIPSI_3.2a_02.ts Modulation : 256 QAM MYS_SIPSI_3.2b_01.ts Cell Identifier : 0 MYS_SIPSI_3.2b_02.ts MYS_SIPSI_3.3a.ts

MYS_SIPSI_3.3a_mux.ts

MYS_SIPSI_3.3b_mux.ts MYS_SIPSI_3.5.ts

Note : Note : Note: Reference Document (Ref.): SKMM MTSFB TC The Test Streams are available with the In the case of simultaneous playing of two streams, T004:2013 - Specification for Digital Terrestrial Communication and Multimedia Certification the streams should be played out at different Television Broadcast Service Receiver. Section, SIRIM QAS International Sdn Bhd frequencies. For example, one stream is played out at 474 MHz and the other is played out at 858 MHz.

45 MCMC MTSFB TC T011:2014

6.4.3.1 Service Addition and Deletion

Section 3.1 : Service Addition and Deletion No. Instruction Expectation Ref. Result Remarks 3.1.1 Play out MYS_SIPSI_3.1a.ts A total of 4 services shall be presented as follows in ascending order: and perform receiver auto scan. LCN 005 MY_TV Channel 1 LCN 013 MY_ Radio Channel 5 LCN 166 MY_TV Channel 11 LCN 180 MY_TV Channel 17

Confirm that receiver shall be able to access to each service normally via numerical keys and service list. 3.1.2 Stop MYS_SIPSI_3.1a.ts and At interval 0::121, same services shall be displayed in the service list as play out Ref. 3.1.1. MYS_SIPSI_3.1a_addition.ts 3.1.3 Network update shall start within the interval 121::240. at the same frequency as Receiver shall automatically undergo network update and update the before. 3.2.11.6 service list.

Note : Do not perform auto A total of 6 services shall be presented in the service list as follows in scan ascending order:

LCN 005 MY_TV Channel 1 LCN 013 MY_ Radio Channel 5 LCN 166 MY_TV Channel 11 LCN 180 MY_TV Channel 17 LCN 290 MY_Radio Channel 32 LCN 351 MYS_TV Channel 106

Confirm that receiver shall be able to access to each service normally via numerical keys and service list.

46 MCMC MTSFB TC T011:2014

Section 3.1 : Service Addition and Deletion No. Instruction Expectation Ref. Result Remarks 3.1.4 Next, stop A total of 4 services shall be presented as follows in ascending order: MYS_SIPSI_3.1a_addition.ts and play out LCN 005 MY_TV Channel 1 MYS_SIPSI_3.1a.ts again. LCN 013 MY_ Radio Channel 5 Perform receiver auto scan. LCN 166 MY_TV Channel 11 LCN 180 MY_TV Channel 17

Confirm that receiver shall be able to access to each service normally via numerical keys and service list. 3.1.5 Stop MYS_SIPSI_3.1a.ts and At interval 0::121, same services shall be displayed in the service list as play out Ref. 3.1.4. MYS_SIPSI_3.1a_deletion.ts 3.1.6 Network update shall start within the interval 121::240. at the same frequency as 3.2.11.6 Receiver shall automatically undergo network update and update the before service list.

Note : Do not perform auto Confirm that 2 services are deleted from the service list and the scan remaining service presented in the service list are as follows in ascending order:

LCN 005 MY_TV Channel 1 LCN 013 MY_ Radio Channel 5

Confirm that receiver is able to access each service normally via numerical keys and service list.

47 MCMC MTSFB TC T011:2014

6.4.3.2 Clash LCN Resolution

Section 3.2 : Clash LCN Resolution No. Instruction Expectation Ref. Result Remarks 3.2.1 Play out MYS_SIPSI_3.2a.ts Total of 9 services shall be visible in the service list and shall be an and MYS_SIPSI_3.2b.ts ascending order as below: simultaneously and perform receiver auto scan method. LCN 100 Service_TV1_SD LCN 101 Service_TV2_SD LCN 102 Service_TV3_SD LCN 103 Service_Radio1 LCN 104 Service_Radio2 LCN 111 SD Service 1 LCN 222 SD Service 1_muxB LCN 333 SD Service 2_muxB LCN 444 SD Service 2 3.2.11.6

Confirm that receiver shall be able to access to each service normally via numerical keys and service list.

Using numerical keys, press '222' to enter LCN 222 SD Service 1_muxB.

'Bridge' video and 'Bell Ring' audio shall be presented.

Commence following test from LCN 222 SD Service 1_muxB.

48 MCMC MTSFB TC T011:2014

Section 3.2 : Clash LCN Resolution No. Instruction Expectation Ref. Result Remarks 3.2.2 Stop the streams and play out Perform receiver method of network configuration update. MYS_SIPSI_3.2a_02.ts and Ensure the following services shall be listed : MYS_SIPSI_3.2b_01.ts simultaneously at the same LCN 100 Service_TV1_SD frequency as before. LCN 101 Service_TV2_SD LCN 102 Service_TV3_SD Set power of Set the power of LCN 103 Service_Radio1 multiplex to be such that LCN 104 Service_Radio2 MYS_SIPSI_3.2b_01.ts > LCN 111 SD Service 1 MYS_SIPSI_3.2a_02.ts LCN 222 SD Service 1_muxB LCN 333 SD Service 2_muxB Note: Do not perform receiver LCN 444 SD Service 2 auto scan. LCN 555 Service_Radio10 3.2.11.6 LCN 666 Service_TV7_SD LCN 800++ SD_Service 2_muxA

Using numerical keys, press '333', '555', and '666', and ensure the following components are available in the services :

In LCN 333, 'Bell Ring' audio and 'Bridge' video shall be presented.

In LCN 555, 'Keyboard' audio and 'Flowers' video shall be presented.

In LCN 666, 'Keyboard' audio and 'Flowers' video shall be presented.

49 MCMC MTSFB TC T011:2014

Section 3.2 : Clash LCN Resolution No. Instruction Expectation Ref. Result Remarks 3.2.3 Stop the streams and play out Perform receiver method of network configuration update. MYS_SIPSI_3.2a_02.ts and Ensure that the following is displayed : MYS_SIPSI_3.2b_02.ts simultaneously at the same LCN 100 Service_TV1_SD frequency as before. LCN 101 Service_TV2_SD LCN 102 Service_TV3_SD Note : LCN 103 Service_Radio1 Do not perform receiver auto LCN 104 Service_Radio2 scan. LCN 222 SD Service 1_muxB LCN 444 SD Service 2 3.2.11.6 Please refer to the stream LCN 555 Service_Radio10 configuration method as stated LCN 666 Service_TV7_SD above LCN 800++ SD Service 2_muxA

Ensure that the below services are removed :

1. LCN 111 SD Service 1

2. LCN 333 SD Service 2_muxB

50 MCMC MTSFB TC T011:2014

6.4.3.3 Multiplex Addition and Deletion

Section 3.3 : Multiplex Addition and Deletion No. Instruction Expectation Ref. Result Remarks 3.3.1 Static Multiplex Addition A total of 6 services shall be presented as follows in ascending order: Play out MYS_SIPSI_3.3a.ts LCN 001 - TV1 and perform receiver auto scan. LCN 002 - TV2 LCN 003 - TV3 LCN 004 - TV4 LCN 005 - TV5 LCN 006 - Radio6 3.2.11.6 Confirm that receiver shall be able to access to each service normally via numerical keys and service list.

Using numerical keys, press '001' to enter LCN 001 TV1. 'Flowers' video and 'Guitar Solo' audio shall be presented.

Commence following test from LCN001 TV1. 3.3.2 Stop MYS_SIPSI_3.3a and play Perform receiver method of network configuration update. out MYS_SIPSI_3.3a_mux.ts (Note: Do not perform receiver autoscan.) and MYS_SIPSI_3.3b_mux.ts simultaneously. A total of 10 services shall be presented as follows in ascending order:

LCN 001 - TV1 LCN 002 - TV2 LCN 003 - TV3 3.2.11.6 LCN 004 - TV4 LCN 005 - TV5 LCN 006 - Radio6 LCN 100 - TV11 LCN 200 - TV_12 LCN 501 - TV_15 LCN 502 - Radio 17

51 MCMC MTSFB TC T011:2014

Section 3.3 : Multiplex Addition and Deletion No. Instruction Expectation Ref. Result Remarks

Confirm that receiver shall be able to access to each service normally via numerical keys and service list.

Using numerical keys, press '001' to enter LCN 001 TV1. 'Flowers' video and 'Guitar Solo' audio shall be presented. 3.3.3 Multiplex Deletion/Addition A total of 6 services shall be presented as follows in ascending order: Next, stop above streams and play out MYS_SIPSI_3.3a.ts at LCN001 - TV1 frequency 474 MHz and LCN002 - TV2 perform auto scan. LCN 003 - TV3 LCN 004 - TV4 3.2.11.6 LCN 005 - TV5 LCN 006 - Radio6

Confirm that receiver shall be able to access to each service normally via numerical keys and service list. 3.3.4 Stop MYS_SIPSI_3.3a.ts and A total of 6 services shall be presented as follows in ascending order: change the frequency to 858MHz. LCN001 - TV1 LCN002 - TV2

LCN 003 - TV3 Perform receiver method of LCN 004 - TV4 3.2.11.6 service update. LCN 005 - TV5 LCN 006 - Radio6

Confirm that receiver shall be able to access to each service normally via numerical keys and service list.

52 MCMC MTSFB TC T011:2014

6.4.3.4 Service and Event Updates

Section 3.4 : Service and Event Updates No. Instruction Expectation Ref. Result Remarks 3.4.1 Play out MYS_SIPSI_3.5.ts and Using numerical keys, press '120' to enter LCN120 TV Channel 120. perform receiver auto scan. At interval 0::60s, 'Village' video with 'Keyboard' audio shall be presented.

Ensure no juddering or erroneous effects in components during presentation. 3.2.2.1

At interval 61::180s, audio and video shall stop. Receiver may optionally freeze the last image of the video during this interval.

Note: Receiver shall handle clean transitions into and out of the active and inactive states during the interval 60-61s.

53 MCMC MTSFB TC T011:2014

Section 3.4 : Service and Event Updates No. Instruction Expectation Ref. Result Remarks 3.4.2 Using numerical keys, press '131' to enter LCN131 TV Service 131.

At interval 0::60s, no components shall be presented.

At interval 61::180s, 'Park' video with 'Bell rings' audio shall be presented.

Ensure no juddering or erroneous effects in components during presentation.

Note: Receiver shall handle clean transitions into and out of the active and inactive states during the interval 60-61s. 3.2.2.1 Using numerical keys, press '131' to enter LCN131 TV Service 131. At interval 0::60s, no components shall be presented.

At interval 61::180s, 'Park' video with 'Bell rings' audio shall be presented.

Ensure no juddering or erroneous effects in components during presentation.

Note: Receiver shall handle clean transitions into and out of the active and inactive states during the interval 60-61s.

54 MCMC MTSFB TC T011:2014

Section 3.4 : Service and Event Updates No. Instruction Expectation Ref. Result Remarks 3.4.3 Using numerical keys, press '555' to enter LCN555 Channel 266.

Press ‘Info' key to view 'Now' and 'Next' event information at banner and optionally at other user interface.

Ensure the event information is as in expectations below and take note of the changes of this information at interval 61s.

At interval 0::60s, present event information are as follows:

Event Name : News at TV1 Event Start/End Time: 9 April, 5:30 PM - 6:30 PM Event Description: News programme on air. 3.2.12.1 Rating: Not defined

At interval 61s, receiver shall detect version change in event p/f and event p/f information shall be updated accordingly.

Present event information during interval 61::180s shall be presented as follows:

Event Name : Movie programme Event Start/End Time: 9 April, 6:30 PM - 8:00 PM Event Description: Movie programme on air. Rating: Not defined

55 MCMC MTSFB TC T011:2014

6.4.3.5 Results of Network Evolution Test

Results of Network Evolution Test Number of Passes Number of Fails Number of Not Tested Total test items

6.4.4 Character Test

Description Test Streams : Stream Configuration :

This test contains the following sections: MYS_CHAR_4a.ts Modulation Type : DVB-T2 MYS_CHAR_4b.ts Channel Frequency : 474 MHz - 858 MHz Section 4.1 : Event p/f MYS_CHAR_4c.ts Bandwidth : 8 MHz Section 4.2 : Event Schedule MYS_CHAR_4d.ts Mode : 32K Section 4.3 : Event p/f (Huffman Encoding) MYS_CHAR_4e.ts Guard Interval : 1/128 Section 4.4 : Event Schedule (Huffman Encoding) MYS_CHAR_4f.ts Modulation : 256 QAM Section 4.5 : Huffman Encoding (Malay) Cell Identifier : 0 Section 4.6 : Huffman Encoding (ESC character) Note : Section 4.7 : No Table Definition The Test Streams are available with the Section 4.8 : Latin Table 05 ISO-8859-9 Communication and Multimedia Certification Section, SIRIM QAS International Sdn Bhd Note : Reference Document (Ref.): SKMM MTSFB TC T004:2013 - Specification for Digital Terrestrial Television Broadcast Service Receiver.

56 MCMC MTSFB TC T011:2014

6.4.4.1 Event p/f

Section 4.1 : Event p/f No. Test instructions Checkpoints Expectations Ref. Result Remarks 4.1.1 Play out stream Ensure all services are LCN 100 Test 1: Normal Encoding Character LCN 101 MYS_CHAR_4a.ts populated correctly as in Test 2: Normal Encoding Character LCN 102 Test 3: and perform expectation. Ensure services Normal Encoding Character receiver auto scan are accessible via numerical method. keys. Confirm correct Enter each service. service name and LCN numbering in each service. 4.1.2 Using numerical Ensure all present event Event Name "Event 1: Combination of long event keys, press '100' to descriptions are presented name which consists many letter and enter service LCN as in expectations in the number ranges 12abc" 100 Test 1: Normal EPG. Encoding Character. Note: Some truncation might occur. 4.1.3 Short Event "Short Event Description: In 1987, Access the banner Description statistics show that 43 percent of people 3.2.8 and guide to view in the world aged between 18 to 35 the present (now) smoke 25 cigarettes per day. This is event information. bad news."

4.1.4 Access the following Extended "Extended Description: Cigarettes events on the Event contain a chemical called carcinogen banner. Description which could endanger the human lungs. Not only does this endanger the smokers, this could be harmful to others as well for they are inhaling the smoke through second hand smoking."

Note: Some truncation might occur.

57 MCMC MTSFB TC T011:2014

Section 4.1 : Event p/f No. Test instructions Checkpoints Expectations Ref. Result Remarks 4.1.5 Ensure all following events Short Event "Short Event Description: Zebras have are presented as in Description many black stripes. It is said that they expectations in the EPG come from a species of the African horse family." 4.1.6 Extended "Extended Event Description: They are Event united by their distinctive black and Description white stripes which come in different patterns and are unique to each individual."

Note: Some truncation might occur. 4.1.7 Using numerical Ensure all present event Event Name "Event 1 : Character Test" keys, press '101' to descriptions are presented enter service as in expectations in the LCN101 EPG. 3.2.8 4.1.8 Test 2: Normal Short Event "CAPITAL ALPHABET: Encoding Character. Description ABCDEFGHIJKLMNOPQRSTUVWXYZ Numbers: 0123456789. abcdefghijklmnopqrstuvwxyz" 4.1 .9 Access the banner Extended “SIX OF THE WOMEN QUIETLY GAVE and guide to view Event BACK PRIZES TO THE JUDGE. THE the present (now) Description JUDGE QUICKLY GAVE BACK SIX event information. PRIZES TO THE WOMEN. Six of the women quietly gave back prizes to the Access the following judge. The judge quickly gave back six events on the prizes to the women.” banner Note: Some truncation might occur.

58 MCMC MTSFB TC T011:2014

Section 4.1 : Event p/f No. Test instructions Checkpoints Expectations Ref. Result Remarks 4.1.10 Ensure all following events Event Name "Event 2:CharacterTest123" 4.1.11 are presented as in Short Event "THE BOY WORE A RED SHIRT. HE expectations in the EPG. Description WAS SEEN STROLLING IN THE ZOO WHILE FEEDING THE FLAMINGOS AND DUCKLINGS. HE WAS WITH HIS FAMILY WHEN SUDDENLY AN UNPREDICTED WEATHER OCCURRED. IT STARTED DRIZZLING BEFORE A HEAVY DOWNPOUR CAME." 4.1.12 Extended "The boy wore a red shirt. He was seen Event strolling in the zoo while feeding the Description flamingos and ducklings. He was with his family when suddenly an unpredicted weather occurred. It started 3.2.8 drizzling before a heavy downpour came." Note: Some truncation might occur. Using numerical Ensure all present event Event Name "Event 1 : Test NBSP and SHY code in 4.1.13 keys, press '102' to descriptions are presented description" 4.1.14 enter service as in expectations in the Short Event "NBSP : word abc word abc word abc LCN102 Test 3: EPG Description word abc word abc word abc word abc Normal Encoding word abc word abc word abc word abc Character. word abc word abc word abc word abc word abc SHY : worddef worddef" Access the banner and guide to view Pass Criteria’s: the present (now) 1. For NBSP, the line may only be event information. broken after word “abc” such that “word abc” is kept together.

59 MCMC MTSFB TC T011:2014

Section 4.1 : Event p/f No. Test instructions Checkpoints Expectations Ref. Result Remarks

2. For SHY, the word should be broken at the [SHY] Character position when the line needs to wrap and display a hyphenation Character “-”, when no line wrap occurs then the [SHY] is not presented. Receivers not implementing SHY are likely to display a single line.

6.4.4.2 Event Schedule

Section 4. 2 : Event Schedule No. Test instructions Checkpoints Expectations Ref. Result Remarks 4.2.1 Using numerical Ensure EPG is accessible. EPG is able to be presented when Guide key is keys, press '101' to pressed. enter service LCN 101 Test 2: Normal Encoding Character.

Press the Guide 3.2.8 button to access the 3.2.12.2 EPG information. 4.2.2 Toggle keys to Ensure 7 days of EPG are 7 days of Event Schedule shall be presented. If less continue to next day displayed. than 7 days of Event Schedule is accessed, this test event schedule and shall fail. previous days.

60 MCMC MTSFB TC T011:2014

Section 4. 2 : Event Schedule No. Test instructions Checkpoints Expectations Ref. Result Remarks 4.2.3 Check the service Ensure services are correct. All services shall be populated in the EPG with the same names on the EPG. details as in expectations in Section 4.1.1 4.2.4 Toggle up, down, Ensure EPG is interactive No erroneous effects occur during different key press. left, right keys with different key press. 4.2.5 Select Event 3 in Ensure correct Event Event Name "Event 3 : Characters Row A-B-C" LCN 101. Names, Event Description, 4.2.6 and Event Start and End Short Event "¡¢£€¥§¤‘“«←↑→↓°±²³×µ¶·÷’”»¼½¾¿" Description Times are presented as in 4.2.7 expectation. Extended " " Event Description 4.2.8 Select Event 4 in Ensure correct Event Event Name "Event 4 : Characters Row D-E" 3.2.8 LCN 101 Names, Event Description, 3.2.12.2 4.2.9 Short Event "―¹®©™♪¬¦⅛⅜⅝⅞ΩÆÐᵃĦIJĿŁØŒ ÞŦ and Event Start and End ⁰ Description Ŋʼn" Times are presented as in 4.2.10 expectation Extended "Event information is not available." Event Description 4.2.11 Select Event 5 in Ensure correct Event Event Name "Event 5 : Characters Row F" LCN 101 Names, Event Description, 4.2.12 and Event Start and End Short Event "ĸæđðħıijŀłøœßþŧŋ" Times are presented as in Description 4.2.13 expectation Extended "Event information is not available." Event Description

61 MCMC MTSFB TC T011:2014

6.4.4.3 Event p/f (Huffman Encoding)

Section 4. 3 : Event p/f (Huffman Encoding) No. Test instructions Checkpoints Expectations Ref. Result Remarks 4.3.1 Play out stream Ensure all services are MYS_CHAR_4b.ts populated correctly as in and perform receiver expectation. Ensure services auto scan method. are accessible via numerical Enter each service. keys. Confirm correct service name and LCN numbering in each service.

4.3.2 Using numerical Ensure all present event Event Name "Event 1 : Combination of long event keys, press '100' to descriptions are presented name which consists many letter and enter service LCN as in expectations in the number ranges 12abc" 100 banner and the EPG 4.3.3 Test 1: Huffman Short Event "Short Event Description: In 1987, Encoding Character. Description statistics show that 43 percent of people 3.2.8 in the world aged between18 to 35 smoke 25 cigarettes per day. This is bad news."

4.3.4 Access the banner Extended "Extended Description: Cigarettes and guide to view Event contain a chemical called carcinogen the present (now) Description which could endanger the human lungs. event information. Not only does this endanger the smokers, this could be harmful to others as well for they are inhaling the smoke Access the following through second hand smoking." events on the

banner. Note: Some truncation might occur.

62 MCMC MTSFB TC T011:2014

Section 4. 3 : Event p/f (Huffman Encoding) No. Test instructions Checkpoints Expectations Ref. Result Remarks 4.3.5 Ensure all following events Short Event "Short Event Description: Zebras have are presented as in Description many black stripes. It is said that they expectations in the banner come from a species of the African horse and the EPG family."

4.3.6 Extended "Extended Event Description: They are Event united by their distinctive black and white Description stripes which come in different patterns and are unique to each individual."

Note: Some truncation might occur. 4.3.7 Using numerical Ensure all present event Event Name "Event 1 : Character Test" keys, press '101' to descriptions are presented enter service as in the banner and the LCN101 EPG. 3.2.8 4.3.8 Test 2: Huffman Short Event "CAPITAL ALPHABET: Encoding Character. Description ABCDEFGHIJKLMNOPQRSTUVWXYZ Numbers: 0123456789. abcdefghijklmnopqrstuvwxyz."

4.3.9 Access the banner Extended “SIX OF THE WOMEN QUIETLY GAVE and guide to view Event BACK PRIZES TO THE JUDGE. THE the present (now) Description JUDGE QUICKLY GAVE BACK SIX event information. PRIZES TO THE WOMEN. Six of the women quietly gave back prizes to the Access the following judge. The judge quickly gave back six events on the prizes to the women.” banner Note: Some truncation might occur.

63 MCMC MTSFB TC T011:2014

Section 4. 3 : Event p/f (Huffman Encoding) No. Test instructions Checkpoints Expectations Ref. Result Remarks 4.3.10 Ensure all following events Event Name "Event 2 : CharacterTest123" are presented as in 4.3.11 Short Event "THE BOY WORE A RED SHIRT. HE expectations in the banner Description WAS SEEN STROLLING IN THE ZOO and the EPG WHILE FEEDING THE FLAMINGOS AND DUCKLINGS. HE WAS WITH HIS FAMILY WHEN SUDDENLY AN UNPREDICTED WEATHER OCCURRED." 3.2.8 4.3.12 Extended "The boy wore a red shirt. He was seen Event strolling in the zoo while feeding the Description flamingos and ducklings. He was with his family when suddenly an unpredicted weather occurred. It started drizzling before a heavy downpour came."

Note: Some truncation might occur.

4.3.13 Using numerical Ensure all present event Event Name "Huffman English" keys, press '102' to descriptions are presented enter service as in expectations in the LCN102 banner and the EPG 4.3.14 Test 3: Huffman Short Event "This is a verification test for English Encoding Character. Description Huffman Encoding. If this text appears, 3.2.8 then the encoding is successful." Access the banner and guide to view the present (now) event information.

64 MCMC MTSFB TC T011:2014

6.4.4.4 Event Schedule (Huffman Encoding)

Section 4. 4 : Event Schedule (Huffman Encoding) No. Test instructions Checkpoints Expectations Ref. Result Remarks

4.4.1 Using numerical Ensure EPG is accessible. EPG is able to be presented when Guide key is keys, press '101' to pressed. enter. Service LCN 101

Test 2: Huffman Encoding Character.

Press the Guide button to access the EPG information

4.4.2 Select Event 3 in LCN Ensure correct Event Event Name "Event 3 : Huffman EPG 1" 101. Names, Event Description, 3.2.8 4.4.3 and Event Start and End Short Event "Zebras have many black stripes. It is Description said that they come from a species of the Times are presented as in African horse family. This text should expectation. display in the EPG with Huffman Encoding implemented."

4.4.4 Select Event 4 in LCN Event Name "Event 4 : Huffman EPG 2" 101. 4.4.5 Short Event "In 1987, statistics show that 43 percent Description of people in the world aged between 18 to 35 smoke 25 cigarettes per day. This text should display in the EPG with Huffman Encoding implemented."

65 MCMC MTSFB TC T011:2014

Section 4. 4 : Event Schedule (Huffman Encoding) No. Test instructions Checkpoints Expectations Ref. Result Remarks 4.4.6 Select Event 5 in LCN Event Name "Event 5 : Huffman EPG 3" 101. 4.4.7 Short Event "The boy wore a red shirt. He was seen Description strolling in the zoo while feeding the 3.2.8 flamingos and ducklings. This text should display in the EPG with Huffman Encoding implemented."

6.4.4.5 Huffman Encoding (Malay)

Section 4. 5 : Huffman Encoding (Malay) No. Test instructions Checkpoints Expectations Ref. Result Remarks 4.5.1 Play out stream Ensure all services are LCN 100 Huffman Malaysia Service MYS_CHAR_4c.ts populated correctly as in and perform receiver expectation. Ensure auto scan method. services are accessible via Enter service. numerical keys. Confirm correct service name and LCN numbering in each service. 4.5.2 Using numerical keys, Ensure all present event Event Name "Huffman Bahasa Malaysia" 3.2.8 press '100' to enter descriptions are presented 4.5.3 service LCN 100 as in expectations in the Short Event "Ikuti berita yang memaparkan banner and the EPG. Description perkembangan terkini dan semasa Test 1: Huffman termasuk berita ekonomi dan kewangan. Malaysia Service. Rancangan khas khusus untuk tontonan anda persembahan daripada TV6. Berhibur dengan kumpulan muzik tempatan dengan pilihan lagu-lagu." Note: Some truncation might occur.

66 MCMC MTSFB TC T011:2014

Section 4. 5 : Huffman Encoding (Malay) No. Test instructions Checkpoints Expectations Ref. Result Remarks 4.5.4 Access the banner Extended "Istimewa Bersama Zaidi Zainal yang and guide to view the Event menyampaikan lagu-lagu popularnya. present (now) event Description Saksikan Rentak Juara 2010 Konsert information. Peringkat Akhir untuk hiburan semua hanya di TV6. Nikmati klip-klip video tempatan pilihan peminat yang terdiri daripada pelbagai kaum dan etnik." Note: Some truncation might occur.

6.4.4.6 Huffman Encoding (ESC character)

Section 4.6 : Huffman Encoding (ESC character) No. Test instructions Checkpoints Expectations Ref. Result Remarks 4.6.1 Play out stream Ensure all services are LCN 100 Huffman Malaysia Service MYS_CHAR_4f.ts populated correctly as in and perform expectation. Ensure services are accessible via Enter service. 3.2.8 numerical keys. Confirm correct service name and LCN numbering in each service. 4.6.2 Using numerical keys, Ensure all present event Event Name "Huffman Bahasa Malaysia" press '100' to enter descriptions are presented service LCN 100 as in expectations in the 3.2.8 banner and the EPG. 4.6.3 Test 1: Huffman Short Event "RM10 adalah bersamaan dengan £2.05 Malaysia Service. Description atau ¥278.34"

67 MCMC MTSFB TC T011:2014

Section 4.6 : Huffman Encoding (ESC character) No. Test instructions Checkpoints Expectations Ref. Result Remarks 4.6.4 Access the banner Ensure all following events Event Name "Huffman English" and guide to view the are presented as in present (now) event expectations in the banner information. and the EPG. 4.6.5 Access the following Short Event "RM10 adalah bersamaan dengan £2.05 events on the banner. Description atau ¥278.34"

6.4.4.7 No Table Definition

Section 4. 7: No Table Definition No. Test instructions Checkpoints Expectations Ref. Result Remarks 4.7.1 Play out stream Ensure all services are LCN 100 Test 1: No Table Defined MYS_CHAR_4d.ts populated correctly as in and perform receiver expectation. Ensure auto scan method. services are accessible via Enter service. numerical keys. Confirm 3.2.8 correct service name and LCN numbering in each service.

4.7.2 Using numerical keys, Ensure all present event Event Name "Event 1 : No Table Defined" press '100' to enter descriptions are presented service LCN 100 as in expectations in the 3.2.8 banner and the EPG.

68 MCMC MTSFB TC T011:2014

Section 4. 7: No Table Definition No. Test instructions Checkpoints Expectations Ref. Result Remarks 4.7.3 Test 1: No Character Short Event "ABC EFGHI LMNOPQ STUVWXY Table. Access the Description 0123 5 9abcdefghi klmnopqrstuvwxy banner and guide to z. '() +,-. : view the present ¡¢£€¥§¤‘“«←↑→↓°±²³×µ¶·÷’”»¼½¾¿ 3.2.8 (now) event ―¹®©™♪¬¦⅛⅝⅞ΩÆÐᵃĦIJĿŁØ information. Œ⁰ ÞŦŊʼnĸæđðħıijŀłøœßþŧŋ"

6.4.4.8 Latin Table 05 - ISO-8859-9

Section 4. 8: Latin Table 05 - ISO-8859-9 No. Test instructions Checkpoints Expectations Ref. Result Remarks 4.8.1 Play out stream Ensure all services are LCN 100 Test 1: Character Table 05 (ISO-8859-9) MYS_CHAR_4e.ts populated correctly as in and perform receiver expectation. Ensure services auto scan method. are accessible via numerical Enter service. keys. Confirm correct service name and LCN numbering in each service 4.8.2 Using numerical keys, Ensure all present event Short Event "!"#$%&'()*+,./0123456789:;<=>?@ press '100' to enter descriptions are presented as Description ABCDEFGHIJKLMNOPQRSTUVW 3.2.8 service LCN 100 Test in expectations in the banner. XYZ[\]^_`abcdefghijklmnopqrstuvwx 1: Character Table 05 yz{|}~¡¢£¤¥§¨©×«¬®¯°±²³´µ¶·¸¹°»¼ (ISO-8859-9). ½¾¿ ÆÇÈÉÊËÌÍÎÏĞÑÒÓÔ

ÕÖ×ØÙÚÛÜİŞßàáâãåæçèéêëìíîïğñ Access the banner òóôõö÷øùúûüışÿ" and guide to view the present (now) event information.

69 MCMC MTSFB TC T011:2014

6.4.4.9 Results of Character Test

Results of Character Test Number of Passes Number of Fails Number of Not Tested Total test items

6.4.5 Active Format Descriptor (AFD) Test

This test contains the following sections: Test Streams : Stream Configuration :

Section 5.1 : AFD Test MYS_AFD.ts Modulation Type : DVB-T2 Channel Frequency : 474 MHz - 858 MHz Bandwidth : 8 MHz Note : Note : Cell Identifier : 0 Reference Document (Ref.): SKMM MTSFB TC The Test Streams are available with the Guard Interval : 1/128 T004:2013 - Specification for Digital Terrestrial Communication and Multimedia Certification Mode : 32K Television Broadcast Service Receiver. Section, SIRIM QAS International Sdn Bhd Modulation : 256 QAM

70 MCMC MTSFB TC T011:2014

6.4.5.1 AFD

Section 5.1 : AFD No. Test instructions Checkpoints Expectations Ref. Result Remarks 5.1.1 Play out stream Ensure all services LCN 100 AFD (1000) MYS_AFD.ts and appear in the service LCN 200 AFD (1011) perform receiver list. LCN 300 AFD (1001) auto scan method Note: Configure the receiver screen setting to display the video as coded frame.

5.1.2 Enter service 'AFD Observe that the video 4:3 Display 16:9 Display (1000)' by pressing is displayed 100. accordingly. Video as in Figure 5.1a shall Video as in Figure 5.1b shall 3.2.3.5 be presented : be presented : Note : For a 16:9 iDTV or STB connected to a

16:9 display, it shall follow Figure 5.1b.

For an STB connected to a 4:3 display, it shall

follow Figure 5.1a Figure 5.1b Figure 5.1a

71 MCMC MTSFB TC T011:2014

Section 5.1 : AFD No. Test instructions Checkpoints Expectations Ref. Result Remarks 5.1.3 Enter service 'AFD Observe that the video Video as in Figure 5.1c shall Video as in Figure 5.1d shall (1011)' by pressing is displayed be presented : be presented : 200. accordingly.

Note : For a 16:9 iDTV or STB connected to a 3.2.3.5 16:9 display, it shall follow Figure 5.1d.

For an STB connected to a 4:3 display, it shall Figure 5.1c Figure 5.1d follow Figure 5.1c.

5.1.4 Enter service 'AFD Observe that the video Video as in Figure 5.1e shall Video as in Figure 5.1f shall be (1001)' by pressing is displayed be presented : presented : 300. accordingly.

Note : For a 16:9 iDTV or STB connected to a 3.2.3.5 16:9 display, it shall follow Figure 5.1f.

For an STB connected Figure 5.1f to a 4:3 display, it shall Figure 5.1e follow Figure 5.1e.

72 MCMC MTSFB TC T011:2014

6.4.5.2 Results of AFD Test

Results of AFD Test Number of Passes Number of Fails Number of Not Tested Total test items

73 MCMC MTSFB TC T011:2014

6.4.6 Multiple Physical Layer

This test contains the Test Streams : Stream Configuration : following sections : Playback Settings: MYS_MPLP_HD.ts Section 6.1 : Multiple MYS_MPLP_SD.ts Modulation Type : DVB-T2 Physical Layer Pipes Guard Interval : 1/128 MYS_MPLP_Radio.ts Channel Frequency : 474 MHz - 858 MHz

Mode : 32K

Note : Bandwidth : 8 MHz Note : Modulation : 64 QAM Reference Document The Test Streams are (Ref.) : SKMM MTSFB available with the Recommended PLP Parameters: TC T004:2013 - Communication and Numbers of PLPs 3 Specification for Digital Multimedia Stream MYS_MPLP_HD.ts MYS_MPLP_SD.ts MYS_MPLP_Radio.ts Terrestrial Television Certification Section, PLP ID 0 1 2 Broadcast Service SIRIM QAS Group 1 1 1 Receiver International Sdn Bhd PLP Type 2 2 2 Modulation 256 QAM 64 QAM 16 QAM Code Rate 4/5 4/5 4/5 FEC Type 64K 64K 64K Baseband Mode HEM HEM HEM BUFS 1,517.14 476.313 476.313 Design Delay 674.934 674.934 674.934 ISSY Long Long Long Time Interleaver type 0 0 0 Time Interleaver type 3 3 3 Interleaver frame 1 1 1 1st Frame 0 0 0 In band signalling Disabled Disabled Disabled Constellation Rotation YES YES YES Number of Blocks 84 28 28

*Note : T2Xpress file configuration setting is provided in the test stream folder as a reference setting

74 MCMC MTSFB TC T011:2014

6.4.6.1 Multiple Physical Layer Pipes

Section 6.1 : Multiple Physical Layer Pipes No. Test instructions Expectations Ref. Result Remarks 6.1.1 Ensure L1 Post Scrambling Total of 9 services shall be visible in the service list and shall be in is disabled. ascending order as below:

Play out streams LCN 001 MPLP HD Service 1 MYS_MPLP_HD.ts, LCN 002 MPLP HD Service 2 MYS_MPLP_SD.ts, and LCN 003 MPLP HD Service 3 MYS_MPLP_Radio.ts and perform receiver auto scan LCN 004 MPLP SD Service 1 method. LCN 005 MPLP SD Service 2 LCN 006 MPLP SD Service 3 LCN 007 MPLP Radio Service 1 3.2.10.5 LCN 008 MPLP Radio Service 2 LCN 009 MPLP Radio Service 3 3.2.10.6

Confirm that receiver shall be able to access to each service normally via numerical keys and service list.

Enter each service and ensure video and audio components are available. For Radio service types, only audio components shall be available.

Note: This is a functional test and as such it is acceptable if artefacts are observed when the stream loops around.

75 MCMC MTSFB TC T011:2014

Section 6.1 : Multiple Physical Layer Pipes No. Test instructions Expectations Ref. Result Remarks 6.1.2 Ensure L1 Post Scrambling Total of 9 services shall be visible in the service list and shall be an is enabled. ascending order as below:

Play out streams LCN 001 MPLP HD Service 1 MYS_MPLP_HD.ts, LCN 002 MPLP HD Service 2 MYS_MPLP_SD.ts, and LCN 003 MPLP HD Service 3 MYS_MPLP_Radio.ts and perform receiver auto scan LCN 004 MPLP SD Service 1 method. LCN 005 MPLP SD Service 2 LCN 006 MPLP SD Service 3 LCN 007 MPLP Radio Service 1 3.2.10.5 LCN 008 MPLP Radio Service 2 LCN 009 MPLP Radio Service 3 3.2.10.6

Confirm that receiver shall be able to access to each service normally via numerical keys and service list.

Enter each service and ensure video and audio components are available. For Radio service types, only audio components shall be available.

Note : This is a functional test and as such it is acceptable if artefacts are observed when the stream loops around

76 MCMC MTSFB TC T011:2014

6.4.6.2 Results of Multiple-PLP Test

Results of Multiple-PLP Test Number of Passes Number of Fails Number of Not Tested Total test items

6.4.7 Self Declaration

This section is to declare that this receiver confirms to the Malaysia Specification for the following.

No Section Section name Result 7.1 3.2.4 Decoding of Audio 7.2 3.2.5 Display of Subtitles 7.3 3.2.15 Outputs 7.4 3.2.16 Remote Control 7.5 3.2.17 Maintenance & Upgrade: Summary

6.4.7.1 Results of Declaration

Results of Declaration Number of Passes Number of Fails Number of Not Tested Total test items

77 MCMC MTSFB TC T011:2014

6.4.7.2 Notes - T2Xpress Settings

Number of PLPs 3 Stream MYS_MPLP_HD.ts MYS_MPLP_SD.ts MYS_MPLP_Radio.ts PLP ID 0 1 2 Group 1 1 1 PLP Type 2 2 2 Modulation 256 QAM 64 QAM 16 QAM Code Rate 4/5 4/5 4/5 FEC Type 64K 64K 64K Baseband Mode HEM HEM HEM BUFS 1,517.14 476.313 476.313 Design Delay 674.934 674.934 674.934 ISSY Long Long Long Time interleaver type 0 0 0 Time interleaver length 3 3 3 Interleaver frame 1 1 1 1st Frame 0 0 0 In band signalling Disabled Disabled Disabled Constellation Rotation YES YES YES Number of Blocks 84 28 28

78 MCMC MTSFB TC T011:2014

7. Malaysia (MYS) SI/PSI Test Requirement

This document contains the general Test Requirements derived from the Malaysian Specification and covers all the mandatory test items that are required in the test suite. This document is categorized into multiple sections covering test elements which are mandated in the Specification.

7.1 Frequency Range

Sec Category Purpose and Outcome Ref Classification 1 Frequency Range 1.1 Channel Purpose : 3.2.10.4 Mandatory Bandwidth To ensure the channels are captured within the frequency range specified in the Malaysia Specification, as defined below:

Bandwidth : 7 MHz VHF III : 174 - 230 MHz

Bandwidth : 8 MHz UHF IV & V : 470 - 860 MHz

Outcome : When tuning is performed, receiver shall be able to capture all the services correctly with the above configuration. 1.2 Operating Purpose: 3.2.10.5 Mandatory Modes To ensure the operating modes in the 3.2.10.6 Malaysia Specification are fulfilled. (These include MPLP and L1 Post Scrambling functionalities.)

Outcome : When tuning is performed, receiver shall be able to capture all the services signalled with the parameters set as in the Malaysia Specification.

7.2 Service Installation

Sec Category Purpose and Outcome Ref Classification 2 Service Installation 2.1 Automatic Purpose: 3.2.11.1 Mandatory Tuning To ensure receiver is able to perform automatic tuning and installed all the services.

Outcome: Captured services are successfully presented in the service list.

79 MCMC MTSFB TC T011:2014

7.3 Video Decoding

Sec Category Purpose and Outcome Ref Classification 3 Video Decoding 3.1 Video Purpose: 3.2.3 Mandatory Resolution, Video To ensure that the receiver shall support and 3.2.3.1 Aspect ratio and display video resolution, aspect ratio and 3.2.3.2 Profile profile as below:

i. 1080i/25Hz; 16:9 ; AVC HP@L4 ii. 720p/50Hz; 16:9 ; AVC HP@L4 iii. 576i/25Hz; 4:3 & 16:9 ; AVC MP@L3

Outcome: The receiver shall correctly present the video component in the supported resolutions as specified above. 3.2 Active Format Purpose: 3.2.3.5 Mandatory Description (AFD) To ensure Active Format Description (AFD) is supported as mentioned in the Malaysia Specification.

General Outcome: Receiver shall be able to process the AFD information and display the correct AFD.

7.4 Audio Decoding

Sec Category Purpose and Outcome Ref Classification 4 Audio Decoding 4.1 Audio Purpose: 3.2.4 Mandatory Formats To ensure that the receivers are able to 3.2.4.1 support the following audio requirements as defined in the Malaysia Specification:

i. MPEG-4 HE-AAC v2L2 (Stereo) ii. MPEG-4 HE-AAC multi-channel

Outcome: The audio formats as defined above shall be decoded correctly by the receiver.

80 MCMC MTSFB TC T011:2014

7.5 Subtitling

Sec Category Purpose and Outcome Ref Classification 5 Subtitling 5.1 Subtitle Purpose: 3.2.5 Mandatory Support To ensure the receiver is able to decode DVB subtitles according to the Malaysia Specification.

Outcome: The receiver shall be able to display the subtitles correctly as signalled in the stream.

7.6 Time and Data Information

Sec Category Purpose and Outcome Ref Classification 6 Time and Data Information 6.1 Time and Purpose : 3.2.13 Mandatory Date Information To ensure receiver shall display the time and date information carried in the relevant SI tables.

Outcome : The receiver shall be able to display the information on the screen correctly.

7.7 EIT Presentation

Sec Category Purpose and Outcome Ref Classification 7 EIT Presentation 7.1 Event Purpose: 3.2.12 Mandatory Information To ensure that the receiver is able to present 3.2.12.1 (Present and the event Information based on the EIT p/f Following) tables as mentioned in the Malaysia Specification.

Outcome: The receiver shall display the content of the event Information correctly in the ‘Now/Next’ screen guide. 7.2 Event Purpose : 3.2.12.2 Mandatory Schedule To ensure the receiver is able to display 7 days of EPG information

Outcome: The event schedule presented for 7 days contains complete information.

81 MCMC MTSFB TC T011:2014

Sec Category Purpose and Outcome Ref Classification 7 EIT Presentation 7.3 Character Purpose : 3.2.8 Mandatory Transmission To ensure the receiver is able to support the Character Sets specified in Malaysia Specification.

Outcome : The receiver is able to display the correct characters signalled in the PSI tables which are related to the character transmission.

7.8 Audio and Subtitle Language Support

Sec Category Purpose and Outcome Ref Classification 8 Audio and Subtitle Language Support 8.1 Multiple Purpose: 3.2.6 Mandatory Subtitle Language To ensure the receiver is able to support Support multiple subtitles within the same service.

Outcome: The receiver shall be able to present the correct subtitle languages according to user settings. 8.2 Multiple Audio Purpose : 3.2.6 Mandatory Language To ensure the receiver is able to support Support multiple audio languages within the same service.

Outcome : The receiver shall be able to present the correct audio languages according to user settings.

7.9 Logical Channel Numbering

Sec Category Purpose and Outcome Ref Classification 9 Logical Channel Numbering 9.1 LCN Version Purpose: 3.2.11.2 Mandatory 1 To ensure receivers are able to process the 3.2.11.4 LCN Version 1 descriptor. 3.2.19

Outcome: The receiver shall be able to solve duplicate and conflicted LCN conditions and access hidden services via numerical keys with the usage of the LCN Version 1 descriptor.

82 MCMC MTSFB TC T011:2014

Sec Category Purpose and Outcome Ref Classification 9 Logical Channel Numbering 9.2 LCN Version Purpose: 3.2.11.3 Mandatory 2 To ensure receivers are able to process the 3.2.11.4 LCN Version 2 descriptor. 3.2.19

Outcome: The receiver shall be able to solve duplicate and conflicted LCN conditions, access hidden services via numerical keys, and select preferred channel list with the usage of the LCN Version 2 descriptor. 9.3 Regional Purpose: 3.2.11.5 Mandatory Broadcast To ensure receivers are able to collate all 3.2.19 Management channel lists and the services are presented based on preferred channel list.

Outcome: Services with correct logical channel number are presented.

7.10 Network Evolution

Sec Category Purpose and Outcome Ref Classification 10 Network Evolution 10.1 Service Purpose: 3.2.11.6 Mandatory Addition/ To ensure receiver is able to perform service Deletion addition and deletion when network scan is performed.

Outcome: The added services shall be presented in the service list. The deleted services shall not be available to user. 10.2 Multiplex Purpose: 3.2.11.6 Mandatory Reconfiguration To ensure the receiver shall automatically detect configuration changes to the network, such as addition of new multiplexes.

Outcome: Services from newly added multiplex shall populate the service list after network scanning. 10.3 Clash Purpose: 3.2.11.6 Mandatory Resolution To ensure the receiver is able to behave according to the Malaysian Specification in the case of clash resolution.

Outcome: The receiver shall give precedence to the service belonging to the multiplex with the best RF when as LCN Conflict is detected.

83 MCMC MTSFB TC T011:2014

Sec Category Purpose and Outcome Ref Classification 10 Network Evolution 10.4 Event p/f Purpose : 3.2.12.1 Mandatory Transitions To ensure receiver is able to perform event p/f transitions with version updates.

Outcome : Receiver shall display the event p/f information according to the version updates.

7.11 Time Exclusive Services

Sec Category Purpose and Outcome Ref Classification 11 Time Exclusive Services 11.1 Transition Purpose: 3.2.2.1 Mandatory between active To ensure the receiver is able to handle and inactive transition between the active and inactive state states of time exclusive service orderly.

Outcome: Receiver shall present clean transition into and out of the service presentation.

84 MCMC MTSFB TC T011:2014

8. Malaysia DVB-T2 Over Air Download (OAD) Test Suite Ver1.0

8.1 Revision history

No Date Description Version Remark 1 2014-06-03 First official release v1.0

8.2 Evaluation details

Receiver Under Test (RUT) RUT Device Type (iDTV/Set top box) RUT Firmware Version

8.3 Evaluation Results

No. Test Descriptions Result Remarks 1. Stream with SSU matches target receiver (Valid OUI) and model tested. Note: Higher package version 2. Stream with SSU does not match target receiver (Invalid OUI). 3. Stream with SSU matches target receiver (Valid OUI) and but with different model tested. Note: Higher package version 4. Stream with SSU matches target receiver (Valid OUI) and model tested. Note: Same package version 5. Interruption while OAD downloading/updating OVERALL RESULTS

85 MCMC MTSFB TC T011:2014

8.4 Test Description

Test Test Test Description Environment Test Procedure Expected Behaviour Result Remarks ID (TS name, etc.) 1 Stream with SSU Modulate TS1 1. Check the receiver base software version in Receiver shall be capable matches target receiver (any frequency the menu system and place receiver to the to download OAD data (Valid OUI) and model is ok, i.e. shipping condition (e.g. Factory Reset). completely and update tested. 650MHz) 2. Play stream and perform installation. the new software version 3. Perform receiver mechanism to initiate OAD correctly. Note: Higher package download (e.g. Put receiver into standby). version Note: The OAD download shall not be initiated from the system menu. 2 Stream with SSU does Modulate TS2 1. Check the receiver base software version in Receiver shall not detect not match target (any frequency the menu system and place receiver to the any OAD data and receiver (Invalid OUI). is ok, i.e. shipping condition (e.g. Factory Reset). prompt any software 650MHz) 2. Play stream and perform installation. update notification 3. Perform receiver mechanism to initiate OAD Software version in download (e.g. Put receiver into standby). receiver system menu shall remain the same. Note: The OAD download shall not be initiated from the system menu. 3 Stream with SSU Modulate TS3 1. Check the receiver base software version in Receiver shall not detect matches target receiver (any frequency the menu system and place receiver to the any OAD data and (Valid OUI) and but is ok, i.e. shipping condition (e.g. Factory Reset). prompt any software with different model 650MHz) 2. Play stream and perform installation. update notification. tested. 3. Perform receiver mechanism to initiate OAD Software version in download (e.g. Put receiver into standby). receiver system menu Note: Higher package shall remain the same. version Note: The OAD download shall not be initiated from the system menu.

86 MCMC MTSFB TC T011:2014

Test Test Test Description Environment Test Procedure Expected Behaviour Result Remarks ID (TS name, etc.) 4 Stream with SSU Modulate TS4 1. Check the receiver base software version in Receiver shall not detect matches target receiver (any frequency the menu system and place receiver to the any OAD data and (Valid OUI) and model is ok, i.e. shipping condition (e.g. Factory Reset). prompt any software tested. 650MHz) 2. Play stream and perform installation. update notification. 3. Perform receiver mechanism to initiate OAD Software version in Note: download (e.g. Put receiver into standby). receiver system menu Same package version shall remain the same. 5 Interruption while OAD Modulate TS1 1. Check the receiver base software version in Receiver shall restart downloading/updating (any frequency the menu system and place receiver to the OAD downloading until i.e. unplug power cord is ok, i.e. shipping condition (e.g. Factory Reset). completion and update 650MHz) 2. Play stream and perform installation. the new software version Note: 3. Perform receiver mechanism to initiate OAD correctly. Stream with SSU download (e.g. Put receiver into standby). matches target receiver 4. While receiver is downloading the OAD, (Valid OUI) and model unplug the power cord of the receiver. with higher package 5. Then, plug in the power cord again and version tested. confirm the receiver is operational. 6. Perform receiver mechanism to initiate OAD download (e.g. put receiver into standby).

Note: The OAD download shall not be initiated from the system menu.

8.5 Results of OAD Test

Results of OAD Test: Number of Passes Number of Fails Number of Not Tested Total test items

87 MCMC MTSFB TC T011:2014

8.6 Test Environment

No Name TS Description

1 TS1 1. TS1 contains valid target receiver OUI in PMT and the OAD data for the target receiver in DSM-CC. 2. OAD data includes higher package version than the base version.

3 TS3 1. TS3 contains invalid OUI, which does not match the target receiver and model type. 2. OAD data includes higher package version than the base version.

4 TS4 1. TS4 contains valid OUI, which matches the target receiver but does not match the model type. 2. OAD data includes higher package version than the base version.

5 TS4 1. TS5 includes valid OUI which matches the target receiver and model type. 2. OAD data includes same package version than the base version.

Note: It is the responsibility of each manufacturer to create their own transport streams.

88 MCMC MTSFB TC T011:2014

8.7 Transport Stream Structure

8.7.1 Transport Stream (option 1)

PMT Service ID: yyyy DSM-CC Type B (Type: 0 x 0b) PID: zzzz Data Broadcast ID: 0 x 000a (SSU) OUI: 0 x 00015a (Digital Video Broadcasting (DVB)) Update type: 0 x1 (Standard Update Carousel via Broadcast) DSM-CC PID: zzzz Download Info Indication (DII) Download Data Block (DDB) Download Server Initiate (DSI) Compatibility Descriptor System hardware Specifier Type: 0 x 01 (IEEE OUI) OUI: xxxxxxxx (Registered Receiver) Model: xxxxxxxx Version: xxxxxxxx System Software Specifier Type: 0 x 01 (IEEE OUI) OUI: xxxxxxxx (Registered Receiver) Model: xxxxxxxx Version: xxxxxxxx Sub-Descriptor (Note: Optional and for private use) INT Network ID: xxxxxx Network Name: xxxxxxx Linkage Descriptor Transport Stream ID: xxxxxx Original Network Stream ID: xxxxxx Service ID: xxxxxx Linkage Type: 0 x 09 (SSU) OUI: 0 x 00015a (Digital Video Broadcasting (DVB))

89 MCMC MTSFB TC T011:2014

8.7.2 Transport Stream (option 2)

PMT Service ID: yyyy DSM-CC Type B (Type: 0 x 0b) PID: zzzz Data Broadcast ID: 0 x 000a (SSU) OUI: xxxxxxxx (Registered Receiver) Update type: 0 x 1 (Standard Update Carousel via Broadcast) DSM-CC PID: zzzz Download Info Indication (DII) Download Data Block (DDB) Download Server Initiate (DSI) Compatibility Descriptor System hardware Specifier Type: 0 x 01 (IEEE OUI) OUI: xxxxxxxx (Registered Receiver) Model: xxxxxxxx Version: xxxxxxxx System Software Specifier Type: 0 x 01 (IEEE OUI) OUI: xxxxxxxx (Registered Receiver) Model: xxxxxxxx Version: xxxxxxxx Sub-Descriptor (Note: Optional and for private use) INT Network ID: xxxxxx Network Name: xxxxxxx Linkage Descriptor Transport Stream ID: xxxxxx Original Network Stream ID: xxxxxx Service ID: xxxxxx Linkage Type: 0 x 09 (SSU) OUI: xxxxxxxx (Registered Receiver)

90 MCMC MTSFB TC T011:2014

9. Malaysia Hybrid Broadcast TV (HBBTV) Test Suite Ver1.0

9.1 Revision history

No Date Description Version Remark 1 2014-06-03 First official release v1.0

9.2 Evaluation details

Receiver Under Test (RUT) RUT Device Type (iDTV/Set top box) RUT Firmware Version

9.3 Evaluation results

No Test Suite Test Case Passed Failed Not Tested Remark 1.0 HbbTV 0.9 2.0 DASH 3.0 Recording 4.0 Marlin DRM 5.0 EIT 6.0 References

9.4 Test Suite

9.4.1 HbbTV 0.9

No Test Case Title Result Remark 1 00000020 Test for running PRESENT application after service selection (Service Bound) 2 00000030 Test for running AUTOSTART application after service selection (Not Service Bound) 3 00000040 Test for running PRESENT application after service selection (Not Service Bound) 4 00000050 Test for running DISABLED application after service selection (Not Service Bound) 5 00000060 Test for KILLED application after service selection (Not Service Bound) 6 00000070 Test for NOT SIGNALLED application after service selection (Not Service Bound) 7 00000110 AIT changes while no broadcast related application is running, AUTOSTART application from DSMCC signalled, part 1 8 00000130 Service selection with AUTOSTART application from broadband, part 1 (success)

91 MCMC MTSFB TC T011:2014

No Test Case Title Result Remark 9 00000160 AIT changes while no broadcast related application is running, multiple AUTOSTART applications signalled, broadband and broadcast, part 1 10 00000170 AIT changes while no broadcast related application is running, multiple AUTOSTART applications signalled, broadband and broadcast, part 2 11 00000190 AIT changes while no broadcast related application is running, multiple AUTOSTART applications signalled, broadband, part 1 12 00000200 AIT changes while no broadcast related application is running, multiple AUTOSTART applications, broadband signalled, part 2 13 00000210 AIT changes while no broadcast related application is running, AUTOSTART application signalled on broadband and broadcast, part 1 14 00000220 AIT changes while no broadcast related application is running, AUTOSTART application signalled on broadband and broadcast, part 2 15 00000240 AIT changes while no broadcast related application is running, AUTOSTART application signalled on broadcast (higher priority) and broadband, part 1 16 00000250 AIT changes while no broadcast related application is running, AUTOSTART application signalled on broadcast (higher prio) and broadband, part 2 (failure) 17 00000260 AIT update with no AUTOSTART applications, broadband and broadcast, part 3 18 00000270 AIT changes while broadcast related application is running, application still signalled 19 00000280 AIT changes while broadcast related application is running, application signalled with KILL 20 00000290 AIT changes while broadcast related application is running, application not signalled 21 00000300 AIT changes while no broadcast related application is running, AUTOSTART application from HTTP signalled 22 00000310 Application exits 23 00000320 Triggering Channel Change Succeeded Event when transitioning from Broadcast Related to Broadcast Independent state 24 00000330 Broadcast Independent Applications created from an HTML page accessed over HTTP 25 00000340 A broadcast-independent application transitioning to a broadcast-related application shall not be killed if all specified conditions are met 26 00000350 A broadcast-independent application transitioning to a broadcast-related application shall be killed if the first of the specified conditions are not met

92 MCMC MTSFB TC T011:2014

No Test Case Title Result Remark 27 00000360 A broadcast-independent application transitioning to a broadcast-related application shall be killed if the second of the specified conditions are not met 28 00000370 A broadcast-independent application transitioning to a broadcast-related application shall be killed if the third of the specified conditions are not met 29 00000380 A broadcast-independent application transitioning to a broadcast-related application shall be killed if the fourth of the specified conditions are not met 30 00000400 Broadcast Independent Applications created from an XML AIT over HTTP and with no boundary defined 31 00000440 Broadcast Independent Applications started from a Broadcast Related application 32 00000450 Transition of an Application from Broadcast Related to Broadcast Independent state using Set Channel 33 00000460 A broadcast-independent application transitioning to a broadcast-related application shall be killed if the fifth of the specified conditions are not met 34 00000570 User input - VK_BACK 35 00000580 User input - VK_0 36 00000590 User input - VK_1 37 00000600 User input - VK_2 38 00000610 User input - VK_3 39 00000620 User input - VK_4 40 00000630 User input - VK_REWIND 41 00000640 User input - VK_RED 42 00000650 User input - VK_GREEN 43 00000660 User input - VK_YELLOW 44 00000670 User input - VK_BLUE 45 00000680 User input - VK_UP 46 00000690 User input - VK_DOWN 47 00000700 User input - VK_LEFT 48 00000710 User input - VK_RIGHT 49 00000720 User input - VK_ENTER 50 00000730 User input - VK_5 51 00000740 User input - VK_6 52 00000750 User input - VK_7 53 00000760 User input - VK_8 54 00000770 User input - VK_9 55 00000780 User input - VK_STOP 56 00000790 User input - VK_PLAY 57 00000800 User input - VK_PAUSE

93 MCMC MTSFB TC T011:2014

No Test Case Title Result Remark 58 00000810 User input - VK_PLAY_PAUSE 59 00000820 User input - VK_FAST_FWD 60 00000830 User input - CSS3 directional focus navigation - VK_UP 61 00000840 User input - CSS3 directional focus navigation - VK_DOWN 62 00000850 User input - CSS3 directional focus navigation - VK_LEFT 63 00000860 User input - CSS3 directional focus navigation - VK_RIGHT 64 00000910 User input - Javascript navigation - VK_UP 65 00000920 User input - Javascript navigation - VK_DOWN 66 00000930 User input - Javascript navigation - VK_LEFT 67 00000940 User input - Javascript navigation - VK_RIGHT 68 00000950 User input - Navigation priority - VK_RIGHT 69 00000960 User input - Navigation priority - VK_UP 70 00000970 User input - Navigation priority - VK_DOWN 71 00000980 User input - Navigation priority - VK_LEFT 72 00000990 Access to resources inside the boundary of an application loaded from carousel 73 00001000 Loading a document outside the boundary of an application loaded via HTTP 74 00001010 Loading a document from outside the application boundary including a document from within the application domain 75 00001020 Access to resources within the Application domain via XMLHttpRequest 76 00001030 Access to resources outside the application domain via XmlHttpRequest 77 00001040 Access to "trusted" API from within an iframe loaded from inside the application domain 78 00001050 Block access to trusted API from document outside the application domain 79 00001060 Access to trusted APIs from a document inside the application boundary of a trusted application loaded via HTTP 80 00001150 Access to trusted API from a document outside the application domain (app loaded via HTTP) 81 00001160 Access to trusted API from a document outside the application domain (app loaded via carousel) 82 00001170 Access to trusted API from a document inside the application domain (app loaded via carousel) 83 00001180 Access to carousel via XMLHttpRequest (app loaded via carousel)

94 MCMC MTSFB TC T011:2014

No Test Case Title Result Remark 84 00001190 Access to resources outside the application domain via XMLHttpRequest 85 00001200 Access to trusted API from a document inside the application domain (app loaded via carousel) 86 00001210 Blocking access to trusted API from a document outside the application domain (app loaded via carousel) 87 00001410 Status value is 404 when trying to access non-existing DSM-CC objects with XMLHttpRequest 88 00001420 When accessing DSM-CC objects with XMLHttpRequest, statusText will return an empty string 89 00001450 Calls to getAllResponseHeaders() return an empty string when accessing DSM-CC objects with XMLHttpRequest 90 00001460 When accessing a DSM-CC File object with XMLHttpRequest, responseText returns the content of the requested file 91 00001470 When accessing a DSM-CC Directory object with XMLHttpRequest, responseText returns a comma- separated list of objects in the directory 92 00001480 When accessing a DSM-CC File object with ".xml" extension with XMLHttpRequest, responseXML returns an XML document object 93 00001490 When accessing a DSM-CC Directory object with XMLHttpRequest, responseXML returns null 94 00001500 When accessing a DSM-CC Stream Event object with XMLHttpRequest, responseXML returns null 95 00001520 Test of minimum terminal capabilities. Supported proportional font 96 00001530 Test of minimum terminal capabilities. Supported proportional font 97 00001540 Test of minimum terminal capabilities. Supported proportional font 98 00001550 Test of minimum terminal capabilities. Supported proportional font 99 00001560 Test of minimum terminal capabilities. Supported non- proportional font 100 00001570 Test of minimum terminal capabilities. Supported non- proportional font 101 00001580 Test of minimum terminal capabilities. Supported non- proportional font 102 00001680 State of a video/broadcast object when it is instantiated 103 00001710 Change of state of a video/broadcast object when the bindToCurrentChannel() method is called while it is in the unrealized state 104 00001720 Change of state of a video/broadcast object when the release() method is called while it is in the unrealized state

95 MCMC MTSFB TC T011:2014

No Test Case Title Result Remark 105 00001730 Change of state of a video/broadcast object when the stop() method is called while it is in the unrealized state 106 00001810 Change of state of a video/broadcast object when the nextChannel() method is called while it is in the presenting state 107 00001820 Change of state of a video/broadcast object when the prevChannel() method is called while it is in the presenting state 108 00001830 Change of state of a video/broadcast object when the bindToCurrentChannel() method is called while it is in the presenting state 109 00001840 Change of state of a video/broadcast object when the release() method is called while it is in the presenting state 110 00001850 Change of state of a video/broadcast object when the stop() method is called while it is in the presenting state 111 00001900 Change of state of a video/broadcast object when the bindToCurrentChannel() method is called while it is in the stopped state 112 00001910 Change of state of a video/broadcast object when the release() method is called while it is in the stopped state 113 00001920 Change of state of a video/broadcast object when the stop() method is called while it is in the stopped state 114 00001940 video/broadcast object presentation - presenting state 115 00001950 video/broadcast object presentation - stopped state 116 00001970 Change of state of a video/broadcast object when the setChannel() method is called (with a null parameter) while it is in the unrealized state 117 00002000 Change of state of a video/broadcast object when the setChannel() method is called (with a correct parameter) while it is in the presenting state 118 00002010 Change of state of a video/broadcast object when the setChannel() method is called (with a null parameter) while it is in the presenting state 119 00002020 Change of state of a video/broadcast object when the setChannel() method is called (with a correct parameter) while it is in the stopped state 120 00002030 Change of state of a video/broadcast object when the setChannel() method is called (with a null parameter) while it is in the stopped state 121 00002230 AV Object Overlap (Partial overlap of object with a higher Z index) 122 00002240 AV Object Overlap (Partial overlap of object with a lower Z index) 123 00002250 AV Object Overlap (Total overlap of object with a higher Z index)

96 MCMC MTSFB TC T011:2014

No Test Case Title Result Remark 124 00002260 AV Object Overlap (Total overlap of object with a lower Z index) 125 00002270 AV Object Scaling (1/8; Video Res 1280x720; 16:9) 126 00002280 AV Object Scaling (1/8; Video Res 640x720; 16:9) 127 00002290 AV Object Scaling (1/8; Video Res 720x576; 16:9) 128 00002300 AV Object Scaling (1/8; Video Res 352x288; 4:3) 129 00002310 AV Object Scaling (2/13; Video Res 1280x720; 16:9) 130 00002320 AV Object Scaling (2/13; Video Res 640x720; 16:9) 131 00002330 AV Object Scaling (2/13; Video Res 720x576; 16:9) 132 00002340 AV Object Scaling (2/13; Video Res 352x288; 4:3) 133 00002350 AV Object Scaling (x2; Video Res 1280x720) 134 00002360 AV Object Scaling (x2; Video Res 640x720) 135 00002370 AV Object Scaling (x2; Video Res 720x576) 136 00002380 AV Object Scaling (x2; Video Res 352x288) 137 00002390 AV Object Scaling (1/2x1/4; Video Res 1280x720) 138 00002400 AV Object Scaling (1/2x1/4; Video Res 640x720) 139 00002410 AV Object Scaling (1/2x1/4; Video Res 720x576) 140 00002420 AV Object Scaling (1/2x1/4; Video Res 352x288) 141 00002430 Terminal stores cookies with an expiry date in persistent memory 142 00002440 Cookies expire at the correct time 143 00002510 Test of support for MP4 File Format streamed over HTTP; 1280x720p@25, 16:9 144 00002520 Test of support for MP4 File Format streamed over HTTP; 352x288i@25, 4:3 145 00002530 Test of support for MPEG-2 TS streamed over HTTP; 1280x720p@25, 16:9 146 00002540 Test of support for MPEG-2 TS streamed over HTTP; 352x288i@25, 4:3 147 00002590 Test of High Bitrate Streaming; MP4 File Format 148 00002610 Test that terminal ignores any AIT signalling present in MPEG-2 TS streamed over HTTP 149 00002630 Test of support for AVC_SD_25; 720x576p@25, 16:9 150 00002640 Test of support for AVC_SD_25; 544x576p@25, 16:9 151 00002650 Test of support for AVC_SD_25; 480x576p@25, 16:9 152 00002660 Test of support for AVC_SD_25; 352x576p@25, 16:9 153 00002670 Test of support for AVC_SD_25; 352x288p@25, 16:9 154 00002680 Test of support for AVC_SD_25; 720x576i@25, 16:9 155 00002690 Test of support for AVC_SD_25; 544x576i@25, 16:9 156 00002700 Test of support for AVC_SD_25; 480x576i@25, 16:9 157 00002710 Test of support for AVC_SD_25; 352x576i@25, 16:9

97 MCMC MTSFB TC T011:2014

No Test Case Title Result Remark 158 00002720 Test of support for AVC_SD_25; 352x288i@25, 16:9 159 00002730 Test of support for AVC_SD_25; 720x576p@25, 4:3 160 00002740 Test of support for AVC_SD_25; 544x576p@25, 4:3 161 00002750 Test of support for AVC_SD_25; 480x576p@25, 4:3 162 00002760 Test of support for AVC_SD_25; 352x576p@25, 4:3 163 00002770 Test of support for AVC_SD_25; 352x288p@25, 4:3 164 00002780 Test of support for AVC_SD_25; 720x576i@25, 4:3 165 00002790 Test of support for AVC_SD_25; 544x576i@25, 4:3 166 00002800 Test of support for AVC_SD_25; 480x576i@25, 4:3 167 00002810 Test of support for AVC_SD_25; 352x576i@25, 4:3 168 00002820 Test of support for AVC_SD_25; 352x288i@25, 4:3 169 00002830 Test of support for AVC_HD_25; 1280x720p@25, 16:9 170 00002840 Test of support for AVC_HD_25; 960x720p@25, 16:9 171 00002850 Test of support for AVC_HD_25; 640x720p@25, 16:9 172 00002860 Test of support for AVC_HD_25; 1280x720i@25, 16:9 173 00002870 Test of support for AVC_HD_25; 960x720i@25, 16:9 174 00002880 Test of support for AVC_HD_25; 640x720i@25, 16:9 175 00002890 Test of support for AVC_HD_25; 1920x1080p@25, 16:9 176 00002900 Test of support for AVC_HD_25; 1440x1080p@25, 16:9 177 00002910 Test of support for AVC_HD_25; 1280x1080p@25, 16:9 178 00002920 Test of support for AVC_HD_25; 960x1080p@25, 16:9 179 00002930 Test of support for AVC_HD_25; 1920x1080i@25, 16:9 180 00002940 Test of support for AVC_HD_25; 1440x1080i@25, 16:9 181 00002950 Test of support for AVC_HD_25; 1280x1080i@25, 16:9 182 00002960 Test of support for AVC_HD_25; 960x1080i@25, 16:9 183 00002970 Test of support for AVC_HD_25; 1280x720p@50, 16:9 184 00002980 Test of support for AVC_HD_25; 960x720p@50, 16:9 185 00002990 Test of support for AVC_HD_25; 640x720p@50, 16:9 186 00003000 Test of support for HE-AAC; Mono, AV Content, Streamed over HTTP 187 00003010 Test of support for HE-AAC; Stereo, AV Content, Streamed over HTTP 188 00003020 Test of support for HE-AAC; Multichannel, AV Content, Streamed over HTTP 189 00003030 Test of support for AAC; Mono, AV Content, Streamed over HTTP 190 00003040 Test of support for AAC; Stereo, AV Content, Streamed over HTTP 191 00003050 Test of support for AAC; Multichannel, AV Content, Streamed over HTTP

98 MCMC MTSFB TC T011:2014

No Test Case Title Result Remark 192 00003060 Test of support for AC-3; Mono, AV Content, Streamed over HTTP 193 00003070 Test of support for AC-3; Stereo, AV Content, Streamed over HTTP 194 00003080 Test of support for AC-3; Multichannel, AV Content, Streamed over HTTP 195 00003120 Test of support for HE-AAC; Mono, Audio Only (Radio) Content, Streamed over HTTP 196 00003130 Test of support for HE-AAC; Stereo, Audio Only (Radio) Content, Streamed over HTTP 197 00003140 Test of support for HE-AAC; Multichannel, Audio Only (Radio) Content, Streamed over HTTP 198 00003180 Test of support for MP3; Mono, Audio Only (Radio) Content, Streamed over HTTP 199 00003190 Test of support for MP3; Stereo, Audio Only (Radio) Content, Streamed over HTTP 200 00003400 Test of downmixing Multichannel HE-AAC (AV Content) Streamed over HTTP 201 00003410 Test of downmixing Multichannel AAC (AV Content) Streamed over HTTP 202 00003420 Test of downmixing Multichannel AC-3 (AV Content) Streamed over HTTP 203 00003460 Test of interpretation of audio metadata when downmixing Multichannel AC-3 (AV Content) Streamed over HTTP 204 00003540 AV Object Seeking Within Buffer (MP4 Forward 5s) 205 00003560 AV Object Seeking Outside Buffer (MP4 Forward) 206 00003580 AV Object Seeking Outside Buffer (MP4 Backward) 207 00003600 AV Object Seeking Within Buffer (MP4 Backward 5s) 208 00003630 AV Streaming Tests: AV Object (Pause) 209 00003640 AV Streaming Tests: AV Object (Stop) 210 00003650 Test for onPlayStateChanged event when transitioning from Play to Pause 211 00003660 Test for onPlayStateChanged event when transitioning from Play to Stop 212 00003670 Test for onPlayStateChanged event when transitioning from Paused to Playing 213 00003680 Test for onPlayStateChanged event when transitioning from Paused to Stop 214 00003690 Test for onPlayStateChanged event when transitioning from Stop to Play 215 00003700 Test for onPlayStateChanged event when transitioning from Stopped to Pause 216 00003710 the application.privateData.currentChannel after application start

99 MCMC MTSFB TC T011:2014

No Test Case Title Result Remark 217 00003730 the application.privateData.currentChannel after channel selection by application 218 00003740 CreateApplication with parameters in URL 219 00003750 CreateApplication with hash in URL 220 00003760 video.currentChannel after channel selection by application 221 00003780 video.currentChannel after application start 222 00003790 EIT p/f 223 00003800 Letter Gothic font rendering width 224 00003810 Line-height CSS style 225 00003820 Tiresias font rendering width 226 00003830 OIPF capabilities: hasCapability() 227 00003840 OIPF Capabilities: extra decodes 228 00003850 OIPF Configuration: preferredAudioLanguage 229 00003860 OIPF Configuration: preferredSubtitleLanguage 230 00003870 OIPF Configuration: countryId 231 00003880 StreamEvent reference DVB URL 232 00003890 StreamEvent reference event description file 233 00003920 Invalid video playback: A/V format 234 00003930 Invalid video playback: cannot connect 235 00003940 Invalid video playback: video not found 236 00003950 Playback of video without content-range support 237 00003960 Video playtime 238 00003970 Video queue 239 00003980 Seek in broadband video playback 240 00003990 Video/mp4 keeps aspect ratio 241 00004000 Video/broadcast keeps aspect ratio

9.4.1.1 Results

Results Passed Failed Not Tested Total test items

9.4.2 Dynamic Adaptive Streaming over HTTP (DASH)

No Test Case Title Result Remark 1 org.hbbtv_DA540290 Simple DASH A/V stream

100 MCMC MTSFB TC T011:2014

No Test Case Title Result Remark DASH A/V stream with two video 2 org.hbbtv_DA540310 representations Support for stopping DASH encoded 3 org.hbbtv_DA541210 clear content streamed over HTTP

9.4.2.1 Results

Results Passed Failed Not Tested Total test items

9.4.3 Recording

No Test Case Title Result Remark Recording of broadband MP4 1 fr.hdforum_93463000 content not permitted Recording of broadband MP2 TS 2 fr.hdforum_93463010 content not permitted Recording of broadband MP4 DASH 3 fr.hdforum_93463020 content not permitted

9.4.3.1 Results

Results Passed Failed Not Tested Total test items

9.4.4 Marlin Digital Rights Management (DRM)

No Test Case Title Result Remark 1 Verify signalling of Marlin DRM capability fr.hdforum_93440002 to HbbTV application 2 Support of live encrypted streaming with fr.hdforum_93440102 key rotation and static MPD for Marlin Terminals 3 Support for normal playback of DASH fr.hdforum_93440146 encoded protected content streamed over HTTP - Marlin Terminals

101 MCMC MTSFB TC T011:2014

9.4.4.1 Results

Results Passed Failed Not Tested Total test items

9.4.5 Event Information Table (EIT)

No Test Case Title Result Remark EIT P/F - video/broadcast object can 1 org.hbbtv_E1210020 decode all required UTF-8 characters EIT Schedule - MetadataSearch object 2 org.hbbtv_E1210030 can decode all required UTF-8 characters

9.4.5.1 Results

Results Passed Failed Not Tested Total test items

102 MCMC MTSFB TC T011:2014

9.5 References

No Test Case Title Remark 1 HbbTV 0.9 Validates products against HbbTV 1.1.1 Release by HbbTV consortium 2 TNT 2.0 Designed to check conformance to the TNT 2.0 Terminal Specification. 1. Tests to check conformance with the HbbTV 1.2.1 profile of DASH 2. Tests to check DRM conformance for both Marlin & Microsoft PlayReady when integrated with HbbTV 3 TDT Hibrida This test suite comprises of test cases covering 1. Device certification validation 2. Supported Audio codecs, including 5.1 surround sound 3. Aspect ratio conformance 4. Video seeking

103 MCMC MTSFB TC T011:2014

Acknowledgements

Members of the Multimedia Terminal Working Group under the Malaysian Technical Standards Forum Berhad (MTSFB)

Jaafar Hj. Mohamad Abu Bakar (Chairman) Hanitek Sdn Bhd Syaida Syarafina binti Sohaimi (Secretary) SIRIM QAS International Sdn Bhd Hafizal Ariffin/ Al Hijrah Media Corporation (TV Alhijrah) Suffian Yahya Tan Chin Aik Asian Broadcasting Networks (M) Sdn Bhd Leong Yan Yoong/ Dolby Laboratories Inc. Panna Dey Er Yong Hwa/ Eastool Solution Sdn Bhd Sam Choong/ Yap Chuang Hing Sharad Sadhu/ Fraunhofer IIS Toni Fiedler Ir. Abu Fatah Sanusi/ Guillemard Engineering Services Ir. Mohd Jaafar Mohd Daud Affendi Mohamed/ LG Electronics (M) Sdn Bhd Heng Lay Peng/ Lee Jiun Huei/ Lui Yuh Yi Hamzah Burok/ Malaysian Technical Standards Forum Berhad Muhammad Zakwan Mohd Zaki/ (MTSFB) Norazlina Dato Ghazali Dr Ahmad Zaki/ Media Prima Berhad Sukumar Lechmanan Mazlan Haji Mahdi/ MyTV Broadcasting Sdn Bhd Mustafa Kamal/ Zul bin Deresid Biswas Raj a/l R.P Rajan/ Panasonic AVC Networks Kuala Lumpur Pang Chieng Yong/ Malaysia Sdn Bhd Vemalarajah Thyagarajah Magli Alias Radio Television Malaysia (RTM) Aw Eng Soon/ Rohde & Schwarz Malaysia Sdn Bhd Mohd Rizal Lim/ Tan Beng Sen Jonathan Yong Samsung Malaysia Electronics (SME) Sdn Bhd Chin Ket Ming/ Sharp (M) Sdn Bhd Parthiban Sappiah Abd. Muttalib V. H Usman/ SIRIM QAS International Sdn Bhd Aida Razana Omar/ Hafizah Zainal Abidin/ Nurhafenah Abdul Jalil/

104 MCMC MTSFB TC T011:2014

Yuzie Aznita Mat Yasin Chin Ket Ming/ Sony EMCS (M) Sdn Bhd Jonathon Yong/ Muzaffar Fakhruddin/ Stephen Anthony Cleary Leong Sung Boon/ Toshiba (M) Sdn Bhd Sim Yat Koon/ Yasuhiro Ota

Members of the Testing Material Sub Working Group of the Multimedia Terminal Working Group (MMT WG) under the Malaysian Technical Standards Forum Berhad (MTSFB)

Muzaffar Fakhruddin (Team Leader) Sony EMCS (M) Sdn Bhd Yuzie Aznita Mat Yasin (Secretary) SIRIM QAS International Sdn Bhd Hafizal Ariffin/ Al Hijrah Media Corporation (TV Alhijrah) Suffian Yahya Leong Yan Yoong/ Dolby Laboratories Inc. Panna Dey Jaafar Hj. Mohamad Abu Bakar Hanitek Sdn Bhd Affendi Mohamed/ LG Electronics (M) Sdn Bhd Heng Lay Peng/ Lui Yuh Yi Hamzah Burok/ Malaysian Technical Standards Forum Berhad Muhammad Zakwan Mohd Zaki/ (MTSFB) Norazlina Dato Ghazali Sukumar Lechmanan Media Prima Berhad Hezal Zainal Abidin/ MyTV Broadcasting Sdn Bhd Mazlan Mahdi Vemalarajah Thyagarajah Panasonic AVC Networks Kuala Lumpur Malaysia Sdn Bhd Ahmad Afandi/ Radio Television Malaysia (RTM) Magli Alias Mohd Rizal Lim Rohde & Schwarz Malaysia Sdn Bhd Zainuddin Md Zainon Samsung Malaysia Electronics (SME) Sdn Bhd Parthiban Sappiah Sharp (M) Sdn Bhd Abd. Muttalib V. H Usman/ SIRIM QAS International Sdn Bhd Fauziah Fadzil/ Khairunnisa Ab. Halim/ Syaida Syarafina Sohaimi Stephen Anthony Cleary Sony EMCS (M) Sdn Bhd Leong Sung Boon/ Toshiba (M) Sdn Bhd Sani Yahya

105