Document Library

Sep 2009

DG11 Device Field and Lab Trial Guidelines 5.1 (5.99 MB)

This document contains a set of guidelines for the tests that should be performed in the course of
Field Trial and Lab Trial carried out on a Terminal Device.

Jun 2009

IR.87.1.0 - SIP-I Interworking Test Cases (0.88 MB)

This document should be read by organisations interested in executing SIP-I Interworking Tests.

Jun 2009

IR.86 IPX.1.0 - Test Execution Instructions (0.71 MB)

This document should be read by organisations interested in executing IPX Tests.

Oct 2009

LECG Report on Economic Benefits from Investment in Advanced Mobile Infrastructure and Services: the case of Thailand (0.21 MB)

Investment in advance mobile broadband networks is likely to privide to Thailand, an area that holds significant enonomic potential.

Oct 2009

IR.90.1.0 - RCS Interworking Guidelines (0.29 MB)

This document illustrates the inter-operator aspects of RCS (Rich Communication Suite). Aim is to minimize any interoperability issues when deploying RCS service between operators by making sure guidelines for deployment options are documented.

Nov 2009

IR.84.2.0 - Video Share Phase 2 Interoperability Specification (0.44 MB)

This document is the Phase 2 Service Specification for the terminal interoperable Real-Time Live Video Share service.

Aug 2009

IR.42.3.4 - Definition of Quality of Service parameters and their computation (0.20 MB)

This document defines QoS parameters and their computation.

Aug 2009

IR.79.1.2 - Image Share Interoperability Specification (0.23 MB)

This document describes the terminal interoperable Image (Live & Pre-stored) Share service. The terminal interoperable Image Share service allows users to share Images between them over PS connection with ongoing CS call, thus enhancing and enriching end-users voice communication.

Dec 2009

IR.67.4.0 - GSMA PRD IR.67 – DNS/ENUM Guidelines for Service (0.65 MB)

This document is intended to provide guidelines and technical information for those who need to set-up and/or maintain DNS servers for inter-Service Provider services.

Dec 2009

TD.13.8.0 - TADIG Code Naming Conventions (0.10 MB)

The TADIG Code consists of two fields, with a total length of five characters consisting of a three-character country code and a two-character operator (or company) ID.

The naming conventions used within this document are based on already existing TAP and RAP implementations, and the naming can therefore not always be referred to standards.