hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 3.1 Co-operation with MNCRS-WG4: | Close working contact with MNCRS-WG4 should be established. Initially SMG4 shall contact MNCRS-WG4 informing them of SMG’s proposed MEXE activities. SMG4 proposes that the work with MNCRS-WG4 is organised as follows:
SMG4 works with MNCRS-WG4 to produce an ETSI technical report on the additions required to Java to fully enable Java with GSM capabilities. It is envisaged that MNCRS-WG4 would then complete the necessary additions to Java standards. The technical report shall be actively maintained, in order that the Java standards can be kept up-to-date with new developments in GSM/UMTS.
Chairman of MNCRS-WG4: John Dykstra, Nortel (jdykstra@nortel.com, phone: +1-612-9328749)
Liaison officer to MNCRS: Jyrki Yli-Nokari, Nokia (jyrki.yli-nokari@nmp.nokia.com, phone: +358 400 834437)
Point of Contact in SMG4: Sverre Slotte, Nokia (sverre@research.nokia.com, phone: +358 9 4376 6208) |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 3.2 Co-operation with JavaSoft: | JavaSoft, as the body with overall responsibility for Java, should be kept informed of SMG’s work with MNCRS-WG4. It is expected that the MNCRS group would forward the GSM specific additions on JAVA to JavaSoft for endorsement.. |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 3.3 Co-operation with other Java bodies: | As the need arises. |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 3.4 Co-operation with the WAP Consortium: | It is evident that a relationship with the WAP Consortium needs to be established as soon as possible in order to co-ordinate MEXE work and to avoid discontinuities between the two.
A LS has been sent from SMG#23, SMG#24, SMG#24bis and SMG#25.
There is a liaison officer named to SMG: Jonas Branden, jonas.branden@ecs.ericsson.se |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 4 Deliverables on MExE | |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 4.1 MExE service definition (stage 1), GSM 02.57 | Responsible Body: SMG1
Draft GSM 02.57
Rapporteur
Mark Cataldo, Lucent
approved at SMG#25
Scope of this document is the high level requirements for the MExE work item. The stage1 document will be restricted to cover the high level requirement but not imply an architecture or a realisation. The major input to the stage 1 is the requirements in the feasibility study. Though the requirements are independent of any technology, the SMG work will focus on the two complementary technologies identified in the feasibility study, i.e. WAP and JAVA. At the same time it is recognised that some work, e.g. on WAP is carried out outside SMG.
The requirements will be presented from the perspective of the user, network operator and the third part service provider. (The third party SP is understood as being a body that is not a GSM network operator but still offering services to subscribers with a MExE terminal)
High level charging requirements will be covered in the stage 1. Responsible for detailed elaboration future after stage 1 approval would be MoU SERG, CAGE2+ and SMG6.
High level Security requirements will be covered in the stage 1. Responsible for detailed elaboration future after stage 1 approval would be SMG10. |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 4.2 GSM enhanced Java environment | Responsible Body: SMG4
Draft GSM 03.57
Contact person
Mr. John Candish
to be presented for information at SMG#27
to be approved at SMG#28
Scope of the deliverable will be:
1. Identify the necessary additions to the JAVA APIs to fully support GSM capabilities.
2. Propose the GSM reference profiles (e.g. personal, embedded JAVA and JAVA card) and the capabilities to be added as minimum capability set..
3. Propose a reference architecture of a mexe capable terminal, considering any possiible relationships with WAP architecture, JAVA environment in the terminal, JAVA Card within the SIM card the SIM Toolkit, possible and possible GSM bearers.
4. Describe the additional functions in sufficient detail. |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 4.3 New specification: Support of multiple MExE technologies in GSM/UMTS | Responsible Body: SMG4
07.57
Contact person
Mr. John Candish
presented for information at SMG#27
approved at SMG#28
Scope of the deliverable:
Identify and propose a solution for the issues raised by the support of multiple mexe technologies in GSM/UMTS. In particular this means the specification of a common and evolvable protocol for terminal capability negotiation. The protocol itself will have to incorporate a version handling mechanism. Software download is envisaged as a negotiable capability of the protocol.
The need for this specification will be assessed and determined during the course of the year. |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 5 Project Plan for MExE | |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 5.1 Scope of SMG meetings on MExE | Date
Meeting
Scope
[expected] Input
[expected]Output
E mail distribution of proposed stage 1
Joint SMG1, SMG4, SMG9 Ad hoc on requirements
Feasibility study, Requirements from other areas On the MOVE, etc.
Stage 1 first draft
12-16 Jan 1998
SMG1 (Sophia Antipolis) + joint SMG1 & 4 adhoc
Review stage 1, mandate MExE group for finalization
Stage 1 draft from workshop
Stage 1
Send output for information to SMG6 and MoU CAGE2+, SMG10.
28-30 Jan 1998
mexe-adhoc
(Nokia/Helsinki)
Ad hoc on architecture
and transport mechanisms
WAP standard (if available)
JAVA API standards
First draft TR .
9-13 Feb 1998
SMG4
Review output of mexe adhoc group.
Review reply from MNCRS
dto.
Second draft.
25-27 Feb 1998
mexe stage 1 SMG1/4 adhoc (if required)
Finalise stage 1
Draft stage 1 from SMG 1
Finalised Stage 1
16-20/03/98
SMG#25
Approval of MEXE stage1
Stage 1
Stage 1 description
27-29 April 1998
MExE Workshop
Review of WAP documentation against SMG requirements
MExE Stage 1, WAP specifications
LS to SMG and WAP Forum
…..
15/05/98
SMG4
Stage 2
Initial MExE Stage 2
Draft MExE Stage 2
22-26/06/98
SMG#26
Status of MExE work item
LS from MExE Workshop
Decision on co-operation with WAP
???
Decision on whether 07.57 required?
12-16/10/98
SMG#27
MEXE stage2
provided for information
Produce API specification, reference models, Profile of API
Output to JavaSoft, LS to SMG4 to check output.
Javasoft endorses the JAVA language extensions. (WAP extensions?)
28/9-02/10/98
SMG4
Progress on MExE Stage 2 and Java(/WAP?) Requirements
30/11-04/12/98
SMG4
Check final output of MNCRS, approve MExE Stage 2.
MExE Stage 3 decision.
Final output from MNCRS, MExE Stage 2.
Formal endorsement of JAVA GSM extensions
08-12/02/99
SMG#28
Approval of MExE Stage 2
MExE Stage 2
Formal endorsement of JAVA GSM extensions. |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 5.2 Major Milestones for MExE (to be derived by PT SMG) | Planned Date
Milestone
Status
1
26/11/97
Kick-off MExE at SMG4
2
20/03/98
SMG#25: Approval of GSM 02.57 MExE stage 1
3
26/06/98
4
12-16/10/98
SMG#27: GSM 03.57 MExE stage 2 presented for information
5
08-12/02/99
SMG#28: Approval of GSN 03.57 MExE Stage 2 |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 5.3 Overview on meetings with relevance for MExE | ANNEX B Lists of Outstanding Issues and technical decisions for MExE
B.1 List of outstanding issues and action points for MExE
Item
Status
Subject
[Solution] | [/ Due party/ due date]
9711-1
open
Type approval testing/ voluntary tests for MExE conforming terminals
9711-5
open
Clarify how the final output standard would fit into the ISO model
9801-1
closed
02.57: Provide input to 02.57 with regard to JAVA Card on the SIM with SIM Toolkit
SMG9 delegates, see 02.57 version 1.0.0
9801-2
closed
02.57: Elaborate on different level of trusted applications
, see 02.57 version 1.0.0
9801-3
closed
02.57: Review Requirements for Mobile Middleware and APIs in UMTS
all/next meeting, see 02.57 version 1.0.0
9801-4
closed
02.57: Elaborate on language and characterset considerations
, see 02.57 version 1.0.0
9801-5
closed
02.57: Elaborate requirements for subscriptions
, see 02.57 version 1.0.0
B.2 List of major decisions for MExE
9802-1
see 02.57 version 1.0.0
History
Document history
Note: Explicit changes in this document are not shown with revision marks
26/06/98
v 3.0.0
19/01/2000
V7.0.0 approved SMG#26
Rapporteur: Mark Cataldo, ETSI / PT12 (SMG).
Email: mark.cataldo@etsi.fr Ph:+33.4.92 94 4349 Fax:+33.4.93 65 28 17 |
f762b14e5c522e02d691e67ffda2480a | 11.10-3 | 1 Scope | The present document specifies the Abstract Test Suites (ATS) and partial IXIT proforma for the Network Layer (Layer 3) at the mobile radio interface of the GSM or DCS (Phase 2+) mobile stations (MS) conforming to the ENs for Layer 3, cell selection, Enhanced Full Rate Speech, Multi-band, GSM-R band (R-GSM) and ASCI ( the voice group call service (VGCS), voice broadcast service (VBS), enhanced Multi-Level Precedence and Pre-emption service (eMLPP), User-to-user Signalling (UUS) service and the Follow Me service) for the digital cellular telecommunications systems.
This EN is valid for MS implemented according Phase2 or Phase2+ R96, or R97, or R98, or R99, or R00.
The ISO standards for the methodology of conformance testing and the TTCN language are used as the basis for the test specifications. |
f762b14e5c522e02d691e67ffda2480a | 11.10-3 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number.
• For a Phase2+ Release 2000 MS, references to GSM documents are to version 9.x.y, when available.
• For a Phase2+ Release 1999 MS, references to GSM documents are to version 8.x.y, when available.
• For a Phase2+ Release 1998 MS, references to GSM documents are to version 7.x.y, when available.
• For a Phase2+ Release 1997 MS, references to GSM documents are to version 6.x.y, when available.
• For a Phase2+ Release 1996 MS, references to GSM documents are to version 5.x.y,. when available.
• For a Phase2 MS, references to GSM documents are to version 4.x.y.
[1] ISO/IEC 9646‑1: "Information Technology-OSI- Conformance Testing Methodology and Framework, Part 1: General Concepts".
[2] ISO/IEC 9646‑2: "Information Technology-OSI- Conformance Testing Methodology and Framework, Part 2: Abstract Test Suite Specification".
[3] ISO/IEC 9646‑3: "Information Technology-OSI- Conformance Testing Methodology and Framework, Part 3: The Tree and Tabular Combined Notation".
[4] ISO/IEC 9646‑5: "Information Technology-OSI- Conformance Testing Methodology and Framework, Part 5: Requirements on test laboratories and clients for the conformance assessment process".
[5] ISO/IEC 8824: "Information Technology-OSI- Specification of Abstract Syntax Notation One (ASN.1)".
[6] ISO/IEC 8825: "Information Technology-OSI- Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN.1)".
[7] ITU‑T Recommendation Q.773: "Specifications of Signalling System No.7; Transaction capabilities formats and encoding".
[8] ETS 300 287: "Integrated Services Digital Network (ISDN); Signalling System No.7, Transaction Capabilities Application Part (TCAP) version 2".
[9] ETS 300 406 (January 1995): "Methods for Testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology".
[10] GSM 02.02: "Digital cellular telecommunication system (see Note 1); Bearer Services (BS) supported by a GSM Public Land Mobile Network (PLMN)".
[10a] 3G TS 22.002: “Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN) (see Note 2) ”
[11] GSM 02.03: "Digital cellular telecommunication system (see Note 1); Teleservices supported by a GSM Public Land Mobile Network (PLMN)".
[11a] 3G TS 22.003: “Circuit Teleservices supported by a Public Land Mobile Network (PLMN) (see Note 2)”
[12] GSM 02.06: "Digital cellular telecommunication system (see Note 1); Types of Mobile Stations (MS)".
[13] GSM 02.07: "Digital cellular telecommunication system (see Note 1); Mobile Station (MS) features".
[14] GSM 02.30: "Digital cellular telecommunication system (see Note 1); Man-Machine Interface (MMI) of the Mobile Station (MS)".
[14a] 3G TS 22.030: “Man-Machine Interface (MMI) of the User Equipment (UE) (see Note 2)”
[15] GSM 02.67: "Digital cellular telecommunications system (Phase 2+); enhanced Multi-Level Precedence and Pre-emption service (eMLPP) – stage 1"
[15a] 3G TS 22.067:”Enhanced Multi‑Level Precedence and Pre‑emption service (eMLPP) ‑ Stage 1 (see Note 2)”
[16] GSM 02.68: "Digital cellular telecommunications system (Phase 2+); Voice Group Call Service – stage 1"
[17] GSM 02.69: "Digital cellular telecommunications system (Phase 2+); Voice Broadcast Service – stage 1"
[18] GSM 03.03: "Digital cellular telecommunication system (see Note 1); Numbering, addressing and identification".
[18a] 3G TS 23.003: “Numbering, Addressing and Identification (see Note 2)”
[19] GSM 03.09: "Digital cellular telecommunications system (see Note 1); Handover procedures".
[19a] 3G TS 23.009: “Handover procedures (see Note 2)”
[20] GSM 03.10: "Digital cellular telecommunications system (see Note 1); GSM Public Land Mobile Network (PLMN) connection types".
[21] GSM 03.11: "Digital cellular telecommunication system (see Note 1); Technical realization of supplementary services".
[21a] 3G TS 23.011 “Technical Realization of Supplementary Services – General aspects (see Note 2)”
[22] GSM 03.12: "Digital cellular telecommunications system (see Note 1); Location registration procedures".
[22a] 3G TS 23.012 “Location management procedures (see Note 2)”
[23] GSM 03.14: "Digital cellular telecommunications system (see Note 1); Support of Dual Tone Multi-Frequency signalling (DTMF) via the GSM system".
[23a] 3G TS 23.014: “Support of Dual Tone Multi Frequency (DTMF) signalling (see Note 2)”
[24] GSM 03.22: "Digital cellular telecommunication system (see Note 1); Functions related to Mobile Station (MS) in idle mode".
[25] GSM 03.40: "Digital cellular telecommunication system (see Note 1); Technical realization of the Short Message Service (SMS) Point to Point (PP)".
[25a] 3G TS 23.040: “Technical realization of Short Message Service (see Note 2)”
[26] GSM 03.41: "Digital cellular telecommunication system (see Note 1); Technical realization of Short Message Service Cell Broadcast (SMSCB)".
[26a] 3G TS 23.041: “Technical realization of Cell Broadcast service (see Note 2)”
[27] GSM 03.67: "Digital cellular telecommunications system (Phase 2+); enhanced Multi-Level Precedence and Pre-emption service (eMLPP) – stage 2"
[27a] 3G TS 23.067: “Enhanced Multi-level precedence and Pre-emption service (e|MLPP) – Stage 2 (see Note 2)”
[28] GSM 03.68: "Digital cellular telecommunications system (Phase 2+); Voice Group Call Service – stage 2"
[29] GSM 03.69: "Digital cellular telecommunications system (Phase 2+); Voice Broadcast Service – stage 2"
[30] GSM 04.01: "Digital cellular telecommunications system (see Note 1); Mobile Station - Base Station System (MS - BSS) interface General aspects and principles".
[31] GSM 04.03: "Digital cellular telecommunications system (see Note 1); Mobile Station - Base Station System (MS - BSS) interface Channel structures and access capabilities".
[32] GSM 04.04: "Digital cellular telecommunication system (see Note 1); layer 1 General requirements".
[33] GSM 04.05: "Digital cellular telecommunication system (see Note 1); Data Link (DL) layer General aspects".
[34] GSM 04.06: "Digital cellular telecommunication system (see Note 1); Mobile Station - Base Station System (MS - BSS) interface Data Link (DL) layer specification".
[35] GSM 04.07: "Digital cellular telecommunication system (see Note 1); Mobile radio interface signalling layer 3 General aspects".
[35a] 3G TS 24.007: “Mobile Radio Interface Signalling Layer 3 – general Aspects (see Note 2)”
[36] GSM 04.08: "Digital cellular telecommunication system (see Note 1); Mobile radio interface layer 3 specification".
[36a] 3G TS 24.008: “Mobile radion interface Layer 3 specification; Core network Protocols – Stage 3 (see Note 2)”
[37] GSM 04.10: "Digital cellular telecommunication system (see Note 1); Mobile radio interface layer 3 Supplementary services specification General aspects".
[37a] 3G TS 24.010: “Mobile radio Interface Layer 3 – Supplementary Services Specification – General Aspects (see Note 2)”
[38] GSM 04.11: "Digital cellular telecommunication system (see Note 1); Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface".
[38a] 3G TS 24.011: “Point-to-Point (PP) Short Message Service (SMS) Support on Mobile Radio Interface (see Note 2)”
[39] GSM 04.12: "Digital cellular telecommunication system (see Note 1); Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface".
[39a] 3G TS 24.012: “Short Message Service Cell Broadcast (SMSCB) Support on the Mobile Radio interface (see Note 2)”
[40] GSM 04.67: "Digital cellular telecommunications system (Phase 2+); enhanced Multi-Level Precedence and Pre-emption service (eMLPP) Stage 3"
[40a] 3G TS 24.067: “Enhanced Multi-level Precedence and Pre-emption service (eMLPP) – stage 3 (see Note 2)”
[41] GSM 04.68: "Digital cellular telecommunications system (Phase 2+); Group Call Control (GCC) protocol
[42] GSM 04.69: "Digital cellular telecommunications system (Phase 2+); Broadcast Call Control (BCC) protocol
[43] GSM 04.80: "Digital cellular telecommunication system (see Note 1); Mobile radio interface layer 3 supplementary services specification; Formats and coding".
[43a] 3G TS 24.080: “Mobile Radio Layer 3 Supplementary Service specification – Formats and coding (see Note 2)”
[44] GSM 04.81: "Digital cellular telecommunication system (see Note 1); Line identification supplementary services - Stage 3".
[44a] 3G TS 24.081: “Line identification Supplementary Service – Stage 3 (see Note 2)”
[45] GSM 04.82: "Digital cellular telecommunication system (see Note 1); Call Forwarding (CF) supplementary services - Stage 3".
[45a] 3G TS 24.082: “Call Forwrding Supplementary Service – Stage 3 (see Note 2)”
[46] GSM 04.83: "Digital cellular telecommunication system (see Note 1); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 3".
[46a] 3G TS 24.083: “Call Waiting (CW) and Call Hold (HOLD) Supplementary Service – Stage 3 (see Note 2)”
[47] GSM 04.84: "Digital cellular telecommunication system (see Note 1); MultiParty (MPTY) supplementary services - Stage 3".
[47a] 3G TS 24.084: “Multiparty (MPTY) Supplementary Service – stage 3 (see Note 2)”
[48] GSM 04.85: "Digital cellular telecommunications system (see Note 1); Closed User Group (CUG) supplementary services - Stage 3".
[48a] 3G TS 24.085: “Closed User Group (CUG) Supplementary Service – Stage 3 (see Note 2)”
[49] GSM 04.86: "Digital cellular telecommunication system (see Note 1); Advice of Charge (AoC) supplementary services - Stage 3".
[49a] 3G TS 24.086: “Advice of Charge (AoC) Supplementary Service – Stage 3 (see Note 2)”
[50] GSM 04.88: "Digital cellular telecommunication system (see Note 1); Call Barring (CB) supplementary services - Stage 3".
[50a] 3G TS 24.088: “Call Barring (CB) Supplementary Service – Stage 3 (see Note 2)”
[51] GSM 04.90: "Digital cellular telecommunication system (see Note 1); Unstructured supplementary services operation - Stage 3".
[51a] 3G TS 24.090: “Unstructured Supplementary Service Data (USSD) – Stage 3 (see Note 2)”
[52] GSM 05.01: "Digital cellular telecommunications system (see Note 1); Physical layer on the radio path General description".
[53] GSM 05.02: "Digital cellular telecommunication system (see Note 1); Multiplexing and multiple access on the radio path".
[54] GSM 05.03: "Digital cellular telecommunication system (see Note 1); Channel coding".
[55] GSM 05.04: "Digital cellular telecommunication system (see Note 1); Modulation".
[56] GSM 05.05: "Digital cellular telecommunication system (see Note 1); Radio transmission and reception".
[57] GSM 05.08: "Digital cellular telecommunication system (see Note 1); Radio subsystem link control".
[58] GSM 05.10: "Digital cellular telecommunication system (see Note 1); Radio subsystem synchronization".
[59] GSM 07.01: "Digital cellular telecommunication system (see Note 1); General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)".
[59a] 3G TS 27.001: “General on Terminal Adaptation Functions (TAF) for Mobile stations (MS) (see Note 2)”
[60] GSM 08.08: "Digital cellular telecommunications system (see Note 1); Mobile-services Switching Centre - Base Station System (MSC - BSS) interface Layer 3 specification".
[61] GSM 08.58: "Digital cellular telecommunications system (see Note 1); Base Station Controller - Base Transceiver Station (BSC - BTS) interface Layer 3 specification".
[62] GSM 09.02: "Digital cellular telecommunication system (see Note 1); Mobile Application Part (MAP) specification".
[62a] 3G TS 29.002: “Mobile Application Part (MAP) (see Note 2)”
[63] GSM 11.10‑1 Version 9.0.0 : "Digital cellular telecommunications system (); Mobile Station (MS) conformance specification; Part 1: Conformance specification".
[64] GSM 11.10-2: “Digital cellular telecommunications system (see Note 1); Mobile Station (MS) conformance specification; Part 2: Protocol Implementation Conformance Statement (PICS) Proforma specification”.
[65] GSM 11.11: "Digital cellular telecommunications system (see Note 1); Mobile Equipment (SIM ‑ ME) interface".
[66] 3G TS 22.087: "User-to-User Signalling (UUS); Service description, Stage 1 (see Note 2)".
[67] 3G TS 22.094: "Follow Me Service description; Stage 1 (see Note 2)".
[68] 3G TS 23.087: "User-to-User Signalling (UUS) Supplementary Service; Stage 2 (see Note 2)".
[69] 3G TS 23.094: "Follow-Me (FM) - Stage 2 (see Note 2)".
[70] 3G TS 24.087: “User-to-User Signalling (UUS) Supplementary Service; Stage 3 (see Note 2)”.
[71] GSM 04.18: “Radio Resource Control Protocol (see Note 1)”
Note 1: Read Phase 2 or Phase 2+ as necessary.
Note 2: Read Release 1999 or further as necessary |
f762b14e5c522e02d691e67ffda2480a | 11.10-3 | 3 Definitions and abbreviations | 3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
Abstract Test Suite (ATS): refer to ISO/IEC 9646‑1 [1].
Implementation Under Test (IUT): refer to ISO/IEC 9646‑1 [1].
Partial Protocol Implementation eXtra Information for Testing (IXIT): refer to ISO/IEC 9646‑1 [1].
Point of Controls and Observations (PCO): refer to ISO/IEC 9646‑1 [1].
Protocol Implementation Conformance Statement (ICS): refer to ISO/IEC 9646‑1 [1].
System Under Test (SUT): refer to ISO/IEC 9646‑1 [1]. |
f762b14e5c522e02d691e67ffda2480a | 11.10-3 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply:
ATS Abstract Test Suite
BI Invalid Behaviour tests
BO Inopportune Behaviour tests
BV Valid Behaviour tests
CA CApability tests
EDP-N Event Detection Point - Notification
EDP-R Event Detection Point - Request
EN European Telecommunication Standard
FE Functional Entity
FSM Finite State Machine
ICS Implementation Conformance Statement
IUT Implementation Under Test
IXIT Implementation eXtra Information for Testing
PDU Protocol Data Unit
SUT System Under Test
TP Test Purpose
TSS Test Suite Structure |
f762b14e5c522e02d691e67ffda2480a | 11.10-3 | 4 Test Suite Structure (TSS) | |
f762b14e5c522e02d691e67ffda2480a | 11.10-3 | 4.1 Test suite naming convention | The test group identifier for each group and subgroup is built according to the scheme in figure 1.
Identifier: L3<c><g>
<c> = category: RGSM R-GSM test suite
ASCI ASCI test suite
L3 Layer 3
EFR Enhanced Full Rate
DB Dual Band
CS Cell Selection
<g> = group: eMLPP eMLPP test group
VGCS_VBS VGCS/VBS test group
CellSelection cell selection and re-selection test group
Signalling signalling test group
UUS User-to-User signalling test group
FM Follow Me test group
General General cases
Initial Test Initial test
IdleMode Idle Mode
BiBo Invalid and Inopportune Behaviour test
RR Radio Ressource
MM Mobility Management
CC Call Control
StructureProc Structure procedure
EGSMSignalling EGSM Signalling
SS Supplementary Service
SMS Short Message Service
EFR Enhanced Full Rate
MultiBandMsRpt Multi Band MS Report
DualBand Dual Band
Figure 1: Test group identifier naming convention scheme |
f762b14e5c522e02d691e67ffda2480a | 11.10-3 | 4.2 Suite Overview | Figure 2 shows the structure of the test suites in the present document.
ATSs
L3
Phase 2
CS
Phase 2
EFR
Phase 2
DB
Phase 2
RGSM
R96
ASCI
R96
UUS & FM
R00
Figure 2: Test suite structure of the L3 tests |
f762b14e5c522e02d691e67ffda2480a | 11.10-3 | 4.3 Test groups | Each test group corresponds to a subclause in the GSM 11.10-1. |
f762b14e5c522e02d691e67ffda2480a | 11.10-3 | 4.4 Test Step Structure | |
f762b14e5c522e02d691e67ffda2480a | 11.10-3 | 4.4.1 Preambles | The preamble is defined for each test case. |
f762b14e5c522e02d691e67ffda2480a | 11.10-3 | 4.4.2 Postambles | After each test case the IUT shall be brought to the state as defined in the postamble for each test case. |
f762b14e5c522e02d691e67ffda2480a | 11.10-3 | 5 Test Purposes (TP) | For each conformance requirement a Test Purpose (TP) is defined. The test purposes are specified in the ATS Dynamic part (annex A and C). |
f762b14e5c522e02d691e67ffda2480a | 11.10-3 | 5.1 TP and test case naming convention | In order clearly to map the conformance requirements specified in the EN 300 607‑1 and TTCN test cases in the ATS, the clause numbers in the EN 300 607‑1 are used as test case names.
The identifier of each TP is identical to the name of the implemented TTCN test case.
"Test Purpose Identifier" = "Test Case Name" = TPI = TC_NN_A_B_C_D_E, where NN, A, B, C, D and E are digits used in the corresponding clause numbers of EN 300 607‑1. For example, the test case name TC_26_14_1_2 is the TTCN specification corresponding to the conformance requirements and the test case in the clause 26.14.1.2 in the EN 300 607‑1. TC_26_10_2_1R is the TTCN specification corresponding to the conformance requirements and the test case of the R-GSM part in the clause 26.10.2.1 in the EN 300 607‑1.
In case where the clause has been implemented in more than one test case sub numbering has been introduced.. |
f762b14e5c522e02d691e67ffda2480a | 11.10-3 | 6 Abstract test method and test configurations | The distributed test method applies to the L3 MS testing. The test method uses a lower tester and a Man‑Machine Interface (MMI) as an upper tester at the SUT. |
f762b14e5c522e02d691e67ffda2480a | 11.10-3 | 6.1 Test system model | The model of the L3 test system is based on the original protocol architecture at the air interface. The test system consists conceptually of a lower tester LT, the L3 test programme (executable test suite), a L2 radio link emulator, a management functional unit, the L1 service provider and a TRx set (see figure 1).
Figure 3: Test system and distributed test method
The LT provides the test environment and for test execution and the means of control and observation at the L3 lower service boundary within the test system.
The L3 TTCN test specification uses the three LT interfaces to communicate with the MS, the system under test, and with the other parts of the test system:
- Interface to the L2 emulator via the PCO;
- Interface to the management functional unit via TTCN test suite operations;
- Interface to the MS Man-Machine Interface (MMI) via a test operator. |
f762b14e5c522e02d691e67ffda2480a | 11.10-3 | 6.2 Test Method | The PCO in the LT is defined as L2 SAP (SAP 0 + 3). The PCO has two FIFO queues (data buffers) to store all sending and receiving test events. The L2 primitives in the ATS which constitute mainly the interface to the L2 emulator are specified via the L2 primitives. In order to simulate multicell testing as required in some test cases, the defined primitives are able to address individual cells of the test system and the logic channels of each cell for the L3 message exchanges. The L2 emulator together with the underlying L1 and the TRx set support all message exchanges via correct radio links.
The management function unit has three management functions:
• L2 and L1 management;
• Channel management;
• TRx management;
The interface to the management function unit is presented in the ATS via a set of test suite operations. The major functions of the test suite management operations are:
• To load configuration parameters necessary for the test system.
• To control and get the necessary values of radio resources/ channels for tests.
The SUT (MS) has a more or less standardized MMI, such as keys, digital display, tones, etc. The ATS uses such kind of functions to provoke some procedures or to observe simple results at the SUT side. A human operator is needed during the test. The test system shall have an interface to the human operator to enable the test co-ordination.
Annex A (normative):
Partial IXIT proforma
Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that users of the present document may freely reproduce the PIXIT proforma in this annex so that it can be used for its intended purposes and may further publish the completed PIXIT.
A.0 Introduction
This partial IXIT proforma contained in the present document, after augmented by the Test Realizer, is proposed to be provided to the client for completion, when the related Abstract Test Suite is to be used against client's Implementation Under Test (IUT).
Text in italics is comments for guidance for the production of a IXIT, and is not to be included in the actual IXIT.
The completed IXIT will normally be used in conjunction with the completed ICS, as it adds precision to the information provided by the ICS.
A.1 Identification Summary
This table is completed by the test laboratory. The item "Contract References" is optional.
Table 1: Identification Summary
IXIT Reference Number
Test Laboratory Name
Date of Issue
Issued to (name of client)
Contract References
A.2 Abstract Test Suite Summary
In the following table the test laboratory provides the version number of the protocol specification and the version number of ATS which are used in the conformance testing.
Table 2: ATS Summary
Protocol Specification
EN 300 557
Version of Protocol Specification
TSS & TP Specification
EN 300 607‑1
Version of TSS & TP Specification
ATS Specification
EN 300 607‑3
Version of ATS Specification
Abstract Test Method
Distributed Test Method
A.3 Test Laboratory
A.3.1 Test Laboratory Identification
The test laboratory provides the following information.
Table 3: Test Laboratory Identification
Name of Test Laboratory
Postal Address
Office address
e-mail address
Telephone Number
FAX Number
A.3.2 Accreditation status of the test service
The test laboratory provides the following information.
Table 4: Accreditation status of the test service
Accreditation status
Accreditation Reference
A.3.3 Manager of Test Laboratory
The test laboratory provides the information about the manager of test laboratory in the following table.
Table 5: Manager of Test Laboratory
Name of Manager of Test Laboratory
e-mail address
Telephone Number
FAX Number
E-mail Address
A.3.4 Contact person of Test Laboratory
The test laboratory provides the information about the contact person of test laboratory in the following table.
Table 6: Contact person of Test Laboratory
Name of Contact of Test Laboratory
e-mail address
Telephone Number
FAX Number
E-mail Address
A.3.5 Means of Testing
In the table below, the test laboratory provides a statement of conformance of the Means Of Testing (MOT) to the reference standardized ATS, and identifies all restrictions for the test execution required by the MOT beyond those stated in the reference standardized ATS.
Table 7: Means of Testing
Means of Testing
A.3.6 Instructions for Completion
In this table, the test laboratory provides any specific instructions necessary for completion and return of the proforma from the client.
Table 8: Instruction for Completion
Instructions for Completion
A.4 Client
A.4.1 Client Identification
The client provides the identification in the following table.
Table 9: Client Identification
Name of Client
Postal Address
Office Address
Telephone Number
FAX Number
A.4.2 Client Test Manager
In this table the client provides information about the test manager.
Table 10: Client Test Manager
Name of Client Test Manager
Telephone Number
FAX Number
E-mail Address
A.4.3 Client Contact person
In this table the client provides information about the test contact person.
Table 11: Client Contact person
Name of Client contact person
Telephone Number
FAX Number
E-mail Address
A.4.4 Test Facilities Required
In the following table, the client records the particular facilities required for testing, if a range of facilities is provided by the test laboratory.
Table 12: Test Facilities Required
Test Facilities Required
A.5 System Under Test
A.5.1 SUT Information
The client provides information about the SUT in the table below.
Table 13: SUT Information
System Name
System Version
SCS Reference
Machine Configuration
Operating System Identification
IUT Identification
ICS Reference for the IUT
A.5.2 Limitations of the SUT
In the table below, the client provides information explaining if any of the abstract tests cannot be executed.
Table 14: Limitation of the SUT
Limitations of the SUT
A.5.3 Environmental Conditions
In the table below the client provides information about any tighter environmental conditions for the correct operation of the SUT.
Table 15: Environmental Conditions
Environmental Conditions
A.6 Ancillary Protocols
This clause is completed by the client in conjunction with the test laboratory.
In the following tables, the client identifies relevant information concerning each ancillary protocol in the SUT other than the IUT itself. One table for one ancillary protocol.
Based on the MOT the test laboratory should create question proforma for each ancillary protocol in the blank space following each table. The information required is dependent on the MOT and the SUT, and covers all the addressing, parameter values, timer values and facilities (relevant to ENs) as defined by the ICS for the ancillary protocol.
A.6.1 Ancillary Protocols 1
Table 16: Ancillary Protocol 1
Protocol Name
EN 300
Version number
ICS Reference (optional)
IXIT Reference (optional)
PCTR Reference (optional)
A.6.2 Ancillary Protocols 2
Table 17: Ancillary Protocol 2
Protocol Name
EN 300
Version number
ICS Reference (optional)
IXIT Reference (optional)
PCTR Reference (optional)
A.7 Protocol Layer Information for L3 of Mobile Station
A.7.1 Information provided for test purposes by the MS supplier
Item
Description
Type/Allowed values
Supported Value
Release
TSPC_24DataF
2.4 k full rate data mode supported – must be TRUE if TSPC_24DataH = TRUE
BOOLEAN
Phase 2
TSPC_24DataH
2.4 k half rate data mode supported
BOOLEAN
Phase 2
TSPC_48DataF
4.8 k full rate data mode supported– must be TRUE if TSPC_48DataH = TRUE
BOOLEAN
Phase 2
TSPC_48DataH
4.8 k half rate data mode supported
BOOLEAN
Phase 2
TSPC_96Data
9.6 k full rate data mode supported
BOOLEAN
Phase 2
TSPC_Feat_A51
ciphering algorithm A5/1 supported
BOOLEAN
Phase 2
TSPC_Feat_A52
ciphering algorithm A5/2 supported
BOOLEAN
Phase 2
TSPC_AddCharSet
A, B, C, D chars supported
BOOLEAN
Phase 2
TSPC_AddInfo_PseudoSynch
Pseudo synchronized supported
BOOLEAN
Phase 2
TSPC_AlertInd
alerting indication to the user supported
BOOLEAN
Phase 2
TSPC_SvcOnTCH
at least one service on traffic channel supported
BOOLEAN
Phase 2
TSPC_SMS
at least one short message service supported
BOOLEAN
Phase 2
TSPC_SS
at least one supplementary service supported
BOOLEAN
Phase 2
TSPC_AutoAutoMode
automatically enter automatic selection of PLMN mode supported
BOOLEAN
Phase 2
TSPC_BasCharSet
Chars 0‑9, *, # supported
BOOLEAN
Phase 2
TSPC_CalledNumDisp
called number display supported
BOOLEAN
Phase 2
TSPC_DCS
testing DCS1 800
BOOLEAN
Phase 2
TSPC_DetachOnPwrDn
detach on power down supported
BOOLEAN
Phase 2
TSPC_DetachOnSIMRmv
detach on SIM remove supported
BOOLEAN
Phase 2
TSPC_DispRcvSMS
display of received SMS supported
BOOLEAN
Phase 2
TSPC_DualRate
dual rate channel types supported
BOOLEAN
Phase 2
TSPC_EGSM
both standard (PGSM) and extended GSM band supported
BOOLEAN
Phase 2
TSPC_EmgOnly
the only circuit switched basic service is emergency call
BOOLEAN
Phase 2
TSPC_followOnReq
follow-on request procedure supported
BOOLEAN
Phase 2
TSPC_HalfRateData
at least one half rate data supported
BOOLEAN
Phase 2
TSPC_HalfRateSpeech
half rate speech mode supported
BOOLEAN
Phase 2
TSPC_InCallMod
In-Call modification supported
BOOLEAN
Phase 2
TSPC_NoimmConn
at least one service not support immediate connection
BOOLEAN
Phase 2
TSPC_Feat_FND
FND feature supported
BOOLEAN
Phase 2
TSPC_NonCallSS
non call related supplementary service supported
BOOLEAN
Phase 2
TSPC_MTsvc
at least one MT circuit switched basic service supported
BOOLEAN
Phase 2
TSPC_MOsvc
at least one MO circuit switched basic service supported
BOOLEAN
Phase 2
TSPC_PGSM
only standard GSM band supported
BOOLEAN
Phase 2
TSPC_RefusalCall
refusal of call supported
BOOLEAN
Phase 2
TSPC_ReplaceSMS
replace SMS supported
BOOLEAN
Phase 2
TSPC_ReplyProc
(SMS) reply procedures supported
BOOLEAN
Phase 2
TSPC_RFAmp
RF amplification supported
BOOLEAN
Phase 2
TSPC_SDCCHOnly
only SDCCH supported
BOOLEAN
Phase 2
TSPC_Serv_SS_AoCC
Advice of Charge (Charging) SS supported
BOOLEAN
Phase 2
TSPC_Serv_SS_BAIC
Barring of All Incoming Calls SS supported
BOOLEAN
Phase 2
TSPC_Serv_SS_BI
BI SS supported
BOOLEAN
Phase 2
TSPC_Serv_SS_BICRoam
Barring of Incoming Calls when Roaming Outside the Home PLMN Country SS supported
BOOLEAN
Phase 2
TSPC_Serv_SS_BAOC
Barring of all Outgoing Calls SS supported
BOOLEAN
Phase 2
TSPC_Serv_SS_BOIC
Barring of Outgoing International Calls SS supported
BOOLEAN
Phase 2
TSPC_Serv_SS_BOICexHC
Barring of Outgoing International Calls except those directed to the Home PLMN Country SS supported
BOOLEAN
Phase 2
TSPC_Serv_SS_CFB
Call Forwarding on Mobile Subscriber Busy SS supported
BOOLEAN
Phase 2
TSPC_Serv_SS_CFNRy
Call Forwarding on No Reply SS supported
BOOLEAN
Phase 2
TSPC_Serv_SS_CFNRc
Call Forwarding on Mobile Subscriber Not Reachable SS supported
BOOLEAN
Phase 2
TSPC_Serv_SS_CFU
Call Forwarding Unconditional SS supported
BOOLEAN
Phase 2
TSPC_Serv_SS_HOLD
Call Hold SS supported
BOOLEAN
Phase 2
TSPC_Serv_SS_MPTY
multiparty SS supported
BOOLEAN
Phase 2
TSPC_Serv_SS_unstruct
USSD supported
BOOLEAN
Phase 2
TSPC_Serv_TS11
telephony supported
BOOLEAN
Phase 2
TSPC_Serv_TS12
emergency call supported
BOOLEAN
Phase 2
TSPC_Serv_TS21
SMS MT/PP supported
BOOLEAN
Phase 2
TSPC_Serv_TS22
SMS MO/PP supported
BOOLEAN
Phase 2
TSPC_Serv_TS23
SMS cell broadcast supported
BOOLEAN
Phase 2
TSPC_Serv_TS61
alternate speech and G3 fax (TS61) supported
BOOLEAN
Phase 2
TSPC_Serv_TS62
automatic G3 fax (TS62) supported
BOOLEAN
Phase 2
TSPC_Serv_BS21
data circuit duplex async 300 bit/s supported
BOOLEAN
Phase 2
TSPC_Serv_BS22
data circuit duplex async 1 200 bit/s supported
BOOLEAN
Phase 2
TSPC_Serv_BS23
data circuit duplex async 1 200/75 bit/s supported
BOOLEAN
Phase 2
TSPC_Serv_BS24
data circuit duplex async 2 400 bit/s supported
BOOLEAN
Phase 2
TSPC_Serv_BS25
data circuit duplex async 4 800 bit/s supported
BOOLEAN
Phase 2
TSPC_Serv_BS26
data circuit duplex async 9 600 bit/s supported
BOOLEAN
Phase 2
TSPC_Serv_BS31
data circuit duplex sync 1 200 bit/s supported
BOOLEAN
Phase 2
TSPC_Serv_BS32
data circuit duplex sync 2 400 bit/s supported
BOOLEAN
Phase 2
TSPC_Serv_BS33
data circuit duplex sync 4 800 bit/s supported
BOOLEAN
Phase 2
TSPC_Serv_BS34
data circuit duplex sync 9 600 bit/s supported
BOOLEAN
Phase 2
TSPC_Serv_BS41
PAD access 300 bit/s supported
BOOLEAN
Phase 2
TSPC_Serv_BS42
PAD access 1 200 bit/s supported
BOOLEAN
Phase 2
TSPC_Serv_BS43
PAD access 1 200/75 bit/s supported
BOOLEAN
Phase 2
TSPC_Serv_BS44
PAD access 2 400 bit/s supported
BOOLEAN
Phase 2
TSPC_Serv_BS45
PAD access 4 800 bit/s supported
BOOLEAN
Phase 2
TSPC_Serv_BS46
PAD access 9 600 bit/s supported
BOOLEAN
Phase 2
TSPC_Serv_BS51
packet access 2 400 bit/s supported
BOOLEAN
Phase 2
TSPC_Serv_BS52
packet access 4 800 bit/s supported
BOOLEAN
Phase 2
TSPC_Serv_BS53
packet access 9 600 bit/s supported
BOOLEAN
Phase 2
TSPC_Serv_BS61
alternate speech/data (BS61) supported
BOOLEAN
Phase 2
TSPC_Serv_BS81
speech followed data (BS81) supported
BOOLEAN
Phase 2
TSPC_SMSStatusRepCap
SMS status report capabilities supported
BOOLEAN
Phase 2
TSPC_StoreRcvSMSME
Storage of received SMS in ME supported
BOOLEAN
Phase 2
TSPC_StoreRcvSMSSIM
Storage of received SMS in SIM supported
BOOLEAN
Phase 2
TSPC_SIMRmv
SIM removable without power down supported
BOOLEAN
Phase 2
TSPC_SwitchOnOff
switch on/off supported
BOOLEAN
Phase 2
TSPC_TranspDataOnly
only transparent data service supported
BOOLEAN
Phase 2
TSPC_CC
CC protocol for at least one BC supported
BOOLEAN
Phase 2
TSPC_TeleSvc
at least one teleservice supported
BOOLEAN
Phase 2
TSPC_EFR
Set to TRUE for EFR MS which supports any EFR features and FALSE otherwise
BOOLEAN
Phase 2
TSPC_EFR_Speech_v2
Set to TRUE for EFR MS which supports EFR Speech Version 2 and FALSE otherwise
BOOLEAN
Phase 2
TSPC_EFR_Speech_v3
Set to TRUE for EFR MS which supports EFR Specch Version 3 and FALSE otherwise
BOOLEAN
Phase 2
TSPC_EFR_EmgCallBcap
Set to TRUE if received ESETUP message contains bearer capability IE, otherwise FALSE
BOOLEAN
Phase 2
TSPC_FullRateSpeech
full rate speech mode supported – must be TRUE if TSPC_HalfRateSpeech = TRUE
BOOLEAN
Phase 2
TSPC_FullRateOnly
only full rate channel type supported
BOOLEAN
Phase 2
TSPC_StoredListCellSel
Stored List Cell Selection supported
BOOLEAN
Phase 2
TSPC_RGSM
both standard and R- GSM band supported
BOOLEAN
R96
TSPC_VGCS_Listening
VGCS listening supported
BOOLEAN
R96
TSPC_VGCS_Talking
VGCS talking supported
BOOLEAN
R96
TSPC_VGCS_Originating
VGCS call originating supported
BOOLEAN
R96
TSPC_VBS_Listening
VBS listening supported
BOOLEAN
R96
TSPC_VBS_Originating
VBS call originating supported
BOOLEAN
R96
TSPC_Reduced_Monitoring
Reduced monitoring on NCH supported
BOOLEAN
R96
TSPC_MonitorPCH_GroupTransmitMode
Monitor PCH in group transmit mode supported
BOOLEAN
R96
TSPC_Serv_SS_eMLPP
eMLPP service supported
BOOLEAN
R96
TSPC_Serv_SS_CallWaiting
Call waiting SS supported
BOOLEAN
R96
TSPC_Serv_SS_UUS
User-to-User Signalling
BOOLEAN
R00
TSPC_Serv_SS_ImpUUS1
Implicit UUS1
BOOLEAN
R00
TSPC_Serv_SS_Send_UUS1_ALERTING
Sending of implicit UUS1 in the ALERTING message
BOOLEAN
R00
TSPC_Serv_SS_Send_UUS1_CONNECT
Sending of implicit UUS1 in the ALERTING message
BOOLEAN
R00
TSPC_Serv_SS_FollowMe
Follow Me
BOOLEAN
R00
TSPC_Serv_UTDI
User-to-Dispatcher Information
BOOLEAN
R00
TSPC_Serv_Compr_UTDI
Compressed User-to-Dispatcher
BOOLEAN
R00
TSPX_TE_stopbit
Terminal Equipment configuration number stop bits. default value : '0'B, 1 bit
BITSTRING[1]
Phase 2
TSPX_TE_databit
Terminal Equipment configuration number data bits. '0'B, 7bits, '1'B, 8bits - default value : '1'B, 8 bits
BITSTRING[1]
Phase 2
TSPX_TE_FLCT
Terminal Equipment flow control. Type of flow control. 0-outband flow control, 1-inband flow control, 2-no flow control. default : 0, outband flow control
0, 1, 2
Phase 2
TSPX_TE_parity
Terminal Equipment configuration parity. 000=odd, 010=even, 011=none, 100=forced to 0, 101=forced to 1. default : '001'B, no parity
BITSTRING[3]
Phase 2
TSPX_BS_21_itc1
Information Transfer Capability value supported for BS21(async data 300bit/s). default value : '001'B, Unrestricted Digital Information
BITSTRING[3]
Phase 2
TSPX_BS_21_more_itc
more than one Information Transfer Capability value supported by BS21(async data 300bit/s). default value : FALSE, only one itc
BOOLEAN
Phase 2
TSPX_BS_21_T_NT
both Transparent and Non-Transparent supported by BS21(async data 300bit/s). default value : FALSE, not support both transparent and non transparent modes
BOOLEAN
Phase 2
TSPX_BS_21_ce
BS21(async data 300bit/s). Connection Element value used in MO call and if the answer to TSPX_BS_21_T_NT is FALSE, the manufacturer must precise which mode is supported by the MS. default value : '00'B, transparent mode
BITSTRING[2]
Phase 2
TSPX_BS_21_sacp
BS21(async data 300bit/s). Signalling Access Protocol value used in MO call. default value : '001'B, I440/450
BITSTRING[3]
Phase 2
TSPX_BS_21_itc2
other Information Transfer Capability value supported by BS21(async data 300bit/s), it shall be different from the previous one if the answer to TSPX_BS_21_more_itc is TRUE. default value :'001'B, Unrestricted Digital Information
BITSTRING[3]
Phase 2
TSPX_BS_22_itc1
Information Transfer Capability value supported by BS22(async data 1200bit/s). default value : '010'B, 3.1kHz audio, exPLMN
BITSTRING[3]
Phase 2
TSPX_BS_22_more_itc
more than one Information Transfer Capability value supported by BS22(async data 1200bit/s). default value : FALSE, only one itc
BOOLEAN
Phase 2
TSPX_BS_22_T_NT
both Transparent and Non-Transparent supported by BS22(async data 1200bit/s). default value : FALSE, not support both transparent and non transparent modes
BOOLEAN
Phase 2
TSPX_BS_22_ce
BS22(async data 1200bit/s) Connection Element value used in MO call and if the answer to TSPX_BS_22_T_NT is FALSE, the manufacturer must precise which mode is supported by the MS. default value : '01'B, non transparent
BITSTRING[2]
Phase 2
TSPX_BS_22_sacp
BS22(async data 1200bit/s) Signalling Access Protocol value used in MO call. default value : '001'B, I440/450
BITSTRING[3]
Phase 2
TSPX_BS_22_itc2
other Information Transfer Capability value supported by BS22(async data 1200bit/s), it shall be different from the previous one if the answer to TSPX_BS_22_more_itc is TRUE. default value : '010'B, 3.1kHz audio, exPLMN
BITSTRING[3]
Phase 2
TSPX_BS_23_itc
Information Transfer Capability value supported by BS23(async 1200/75 bit/s). default value : '010'B, 3.1kHz audio, exPLMN
BITSTRING[3]
Phase 2
TSPX_BS_23_T_NT
both Transparent and Non-Transparent supported for BS23(async 1200/75 bit/s). default value : FALSE, not support both transparent and non transparent modes
BOOLEAN
Phase 2
TSPX_BS_23_ce
BS23(async 1200/75 bit/s) Connection Element value used in MO call. default value : '00'B, transparent
BITSTRING[2]
Phase 2
TSPX_BS_23_sacp
BS23(async 1200/75 bit/s) Signalling Access Protocol value used in MO call. default value : '001'B, I440/450
BITSTRING[3]
Phase 2
TSPX_BS_24_itc1
Information Transfer Capability value supported by BS24(async 2400 bit/s). default value : '010'B, 3.1kHz audio, exPLMN
BITSTRING[3]
Phase 2
TSPX_BS_24_more_itc
more than one Information Transfer Capability value supported by BS24(async 2400 bit/s). default value : FALSE, only one itc
BOOLEAN
Phase 2
TSPX_BS_24_T_NT
both Transparent and Non-Transparent supported by BS24(async 2400 bit/s). default value : FALSE, not support both transparent and non transparent modes
BOOLEAN
Phase 2
TSPX_BS_24_ce
BS24(async 2400 bit/s) Connection Element value used in MO call and if the answer to TSPX_BS_24_T_NT is FALSE, the manufacturer must precise which mode is supported by the MS. default value : '00'B, transparent
BITSTRING[2]
Phase 2
TSPX_BS_24_sacp
BS24(async 2400 bit/s) Signalling Access Protocol value used in MO call. default value : '001'B, I440/450
BITSTRING[3]
Phase 2
TSPX_BS_24_itc2
other Information Transfer Capability value supported by BS24(async 2400 bit/s), it shall be different from the previous one if the answer to TSPX_BS_24_more_itc is TRUE. default value : '010'B, 3.1kHz audio, exPLMN
BITSTRING[3]
Phase 2
TSPX_BS_25_itc1
Information Transfer Capability value supported by BS25(async 4800 bit/s). default value : '001'B, Unrestricted Digital Information
BITSTRING[3]
Phase 2
TSPX_BS_25_more_itc
more than one Information Transfer Capability value supported by BS25(async 4800 bit/s). default value : FALSE, only one itc
BOOLEAN
Phase 2
TSPX_BS_25_T_NT
both Transparent and Non-Transparent supported by BS25(async 4800 bit/s). default value : FALSE, not support both transparent and non transparent modes
BOOLEAN
Phase 2
TSPX_BS_25_ce
BS25(async 4800 bit/s) Connection Element value used in MO call and if the answer to TSPX_BS_25_T_NT is FALSE, the manufacturer must precise which mode is supported by the MS. default value : '00'B, transparent
BITSTRING[2]
Phase 2
TSPX_BS_25_sacp
BS25(async 4800 bit/s) Signalling Access Protocol value used in MO call. default value : '001'B, I440/450
BITSTRING[3]
Phase 2
TSPX_BS_25_itc2
other Information Transfer Capability value supported by BS25(async 4800 bit/s), it shall be different from the previous one if the answer to TSPX_BS_25_more_itc is TRUE. default value : '001'B, Unrestricted Digital Information
BITSTRING[3]
Phase 2
TSPX_BS_26_itc1
Information Transfer Capability value supported by BS26(async 9600 bit/s). default value : '010'B, 3.1kHz audio, exPLMN
BITSTRING[3]
Phase 2
TSPX_BS_26_more_itc
more than one Information Transfer Capability value supported by BS26(async 9600 bit/s). default value : FALSE, only one itc
BOOLEAN
Phase 2
TSPX_BS_26_T_NT
both Transparent and Non-Transparent supported by BS26(async 9600 bit/s). default value : FALSE, not support both transparent and non transparent modes
BOOLEAN
Phase 2
TSPX_BS_26_ce
BS26(async 9600 bit/s) Connection Element value used in MO call and if the answer to TSPX_BS_26_T_NT is FALSE, the manufacturer must precise which mode is supported by the MS. default value : '00'B, transparent
BITSTRING[2]
Phase 2
TSPX_BS_26_sacp
BS26(async 9600 bit/s) Signalling Access Protocol value used in MO call. default value : '001'B, I440/450
BITSTRING[3]
Phase 2
TSPX_BS_26_itc2
other Information Transfer Capability value supported by BS26, it shall be different from the previous one if the answer to TSPX_BS_26_more_itc is TRUE. default value : '010'B, 3.1kHz audio, exPLMN
BITSTRING[3]
Phase 2
TSPX_BS_31_more_itc
more than one Information Transfer Capability value supported by BS31(sync data 1200 bit/s). default value : FALSE, only one itc
BOOLEAN
Phase 2
TSPX_BS_31_more_sacp
more than one Signalling Access Protocol value supported by BS31(sync data 1200 bit/s). default value : FALSE, only one sacp
BOOLEAN
Phase 2
TSPX_BS_31_itc1
Information Transfer Capability value supported by BS31(sync data 1200 bit/s). default value : '001'B, Unrestricted Digital Information
BITSTRING[3]
Phase 2
TSPX_BS_31_sacp1
Signalling Access Protocol value supported by BS31(sync data 1200 bit/s). default value : '001'B, I440/450
BITSTRING[3]
Phase 2
TSPX_BS_31_itc2
other Information Transfer Capability value supported by BS31(sync data 1200 bit/s), it shall be different from the previous one if the answer to TSPX_BS_31_more_itc is TRUE. default value : '001'B, Unrestricted Digital Information
BITSTRING[3]
Phase 2
TSPX_BS_31_sacp2
other Signalling Access Protocol value supported by BS31(sync data 1200 bit/s), it shall be different from the previous one if the answer to TSPX_BS_31_more_Signalling Access Protocol is TRUE. default value : '001'B, I440/450
BITSTRING[3]
Phase 2
TSPX_BS_32_itc1
Information Transfer Capability value supported by BS32(sync data 2400 bit/s). default value : '010'B, 3.1kHz audio, exPLMN
BITSTRING[3]
Phase 2
TSPX_BS_32_more_itc
more than one Information Transfer Capability value supported by BS32(sync data 2400 bit/s). default value : FALSE, only one itc
BOOLEAN
Phase 2
TSPX_BS_32_more_sacp
more than one Signalling Access Protocol value supported by BS32(sync data 2400 bit/s). default value : FALSE, only one sacp
BOOLEAN
Phase 2
TSPX_BS_32_sacp1
Signalling Access Protocol value supported by BS32(sync data 2400 bit/s). default value : '110'B, X.32
BITSTRING[3]
Phase 2
TSPX_BS_32_X32_T_NT
BS 32(sync data 2400 bit/s) both Transparent and Non-Transparent supported for X32 3.1kHz. default value : FALSE, not support both transparent and non transparent modes
BOOLEAN
Phase 2
TSPX_BS_32_X32_ce
BS32(sync data 2400 bit/s). If the answer to TSPX_BS_32_X32_T_NT is FALSE, the manufacturer must precise which mode is supported by the MS. Connection Element default value : '01'B, non transparent
BITSTRING[2]
Phase 2
TSPX_BS_32_itc2
other Information Transfer Capability value supported by BS32(sync data 2400 bit/s), it shall be different from the previous one if the answer to TSPX_BS_32_more_itc is TRUE. default value : '010'B, 3.1kHz audio, exPLMN
BITSTRING[3]
Phase 2
TSPX_BS_32_sacp2
other Signalling Access Protocol value supported by BS32(sync data 2400 bit/s), it shall be different from the previous one if the answer to TSPX_BS_32_more_sacp is TRUE. default value : '110'B, X.32
BITSTRING[3]
Phase 2
TSPX_BS_33_itc1
Information Transfer Capability value supported by BS33 (sync data 4800 bit/s). default value : '001'B, Unrestricted Digital Information
BITSTRING[3]
Phase 2
TSPX_BS_33_more_itc
more than one Information Transfer Capability value supported by BS33(sync data 4800 bit/s). default value : FALSE, only one itc
BOOLEAN
Phase 2
TSPX_BS_33_more_sacp
more than one Signalling Access Protocol value supported by BS33(sync data 4800 bit/s). default value : FALSE, only one sacp
BOOLEAN
Phase 2
TSPX_BS_33_sacp1
Signalling Access Protocol value supported by BS33(sync data 4800 bit/s). default value : '010'B, X.21
BITSTRING[3]
Phase 2
TSPX_BS_33_X32_T_NT
BS 33(sync data 4800 bit/s) both Transparent and Non-Transparent supported for X32 3.1kHz. default value : FALSE, not support both transparent and non transparent modes
BOOLEAN
Phase 2
TSPX_BS_33_X32_ce
BS33(sync data 4800 bit/s). If the answer to TSPX_BS_33_X32_T_NT is FALSE, the manufacturer must precise which mode is supported by the MS. Connection Element default value : '00'B, transparent
BITSTRING[2]
Phase 2
TSPX_BS_33_itc2
other Information Transfer Capability value supported by BS33(sync data 4800 bit/s), it shall be different from the previous one if the answer to TSPX_BS_33_more_itc is TRUE. default value : '001'B, Unrestricted Digital Information
BITSTRING[3]
Phase 2
TSPX_BS_33_sacp2
other Signalling Access Protocol value supported by BS33(sync data 4800 bit/s), it shall be different from the previous one if the answer to TSPX_BS_33_more_sacp is TRUE. default value : '010'B, X.21
BITSTRING[3]
Phase 2
TSPX_BS_34_itc1
Information Transfer Capability value supported by BS34(sync data 9600 bit/s). default value : '010'B, 3.1kHz audio, exPLMN
BITSTRING[3]
Phase 2
TSPX_BS_34_more_itc
more than one Information Transfer Capability value supported by BS34(sync data 9600 bit/s). default value : FALSE, only one itc
BOOLEAN
Phase 2
TSPX_BS_34_more_sacp
more than one Signalling Access Protocol value supported by BS34(sync data 9600 bit/s). default value : FALSE, only one sacp
BOOLEAN
Phase 2
TSPX_BS_34_sacp1
Signalling Access Protocol value supported by BS34(sync data 9600 bit/s). default value : '001'B, I440/450
BITSTRING[3]
Phase 2
TSPX_BS_34_X32_T_NT
BS 34(sync data 9600 bit/s) both Transparent and Non-Transparent supported for X32 3.1kHz. default value : FALSE, not support both transparent and non transparent modes
BOOLEAN
Phase 2
TSPX_BS_34_X32_ce
BS34(sync data 9600 bit/s). If the answer to TSPX_BS_34_X32_T_NT is FALSE, the manufacturer must precise which mode is supported by the MS. Connection Element default value : '00'B, transparent
BITSTRING[2]
Phase 2
TSPX_BS_34_itc2
other Information Transfer Capability value supported by BS34(sync data 9600 bit/s), it shall be different from the previous one if the answer to TSPX_BS_34_more_itc is TRUE. default value : '010'B, 3.1kHz audio, exPLMN
BITSTRING[3]
Phase 2
TSPX_BS_34_sacp2
other Signalling Access Protocol value supported by BS34(sync data 9600 bit/s), it shall be different from the previous one if the answer to TSPX_BS_34_more_sacp is TRUE. default value : '001'B, I440/450
BITSTRING[3]
Phase 2
TSPX_BS_41_T_NT
BS41(PAD access 300 bit/s) both Transparent and Non-Transparent supported . default value : FALSE, not support both
BOOLEAN
Phase 2
TSPX_BS_41_ce
Connection Element value used in BS41(PAD access 300 bit/s) MO call. default value : '00'B, transparent
BITSTRING[2]
Phase 2
TSPX_BS_42_T_NT
BS42(PAD access 1200 bit/s) both Transparent and Non-Transparent supported . default value : FALSE, not support both transparent and non transparent modes
BOOLEAN
Phase 2
TSPX_BS_42_ce
Connection Element value used in BS42(PAD access 1200 bit/s) MO call. default value : '00'B, transparent
BITSTRING[2]
Phase 2
TSPX_BS_43_T_NT
BS43(PAD access 1200/75 bit/s) both Transparent and Non-Transparent supported . default value : FALSE, not support both transparent and non transparent modes
BOOLEAN
Phase 2
TSPX_BS_43_ce
Connection Element value used in BS43(PAD access 1200/75 bit/s) MO call. default value : '00'B, transparent
BITSTRING[2]
Phase 2
TSPX_BS_44_T_NT
BS44(PAD access 2400 bit/s) both Transparent and Non-Transparent supported . default value : FALSE, not support both transparent and non transparent modes
BOOLEAN
Phase 2
TSPX_BS_44_ce
Connection Element value used in BS44(PAD access 2400 bit/s) MO call. default value : '00'B, transparent
BITSTRING[2]
Phase 2
TSPX_BS_45_T_NT
BS45(PAD access 4800 bit/s) both Transparent and Non-Transparent supported . default value : FALSE, not support both transparent and non transparent modes
BOOLEAN
Phase 2
TSPX_BS_45_ce
Connection Element value used in BS45(PAD access 4800 bit/s) MO call. default value : '00'B, transparent
BITSTRING[2]
Phase 2
TSPX_BS_46_T_NT
BS46(PAD access 9600 bit/s) both Transparent and Non-Transparent supported . default value : FALSE, not support both transparent and non transparent modes
BOOLEAN
Phase 2
TSPX_BS_46_ce
Connection Element value used in BS46(PAD access 9600 bit/s) MO call. default value : '00'B, transparent
BITSTRING[2]
Phase 2
TSPX_BS_61_S
synchronous data supported by BS 61(alternate speech/data) . default value : TRUE, synchronous mode
BOOLEAN
Phase 2
TSPX_BS_61_S_more_ur
more than one user rate for synchronous data service supported by BS61(alternate speech/data). default value : FALSE, only ine user rate
BOOLEAN
Phase 2
TSPX_BS_61_S_ur1
user rate value supported for synchronous data service of BS61(alternate speech/data). default value : '0100'B, 4.8 kbit/s
BITSTRING[4]
Phase 2
TSPX_BS_61_S_ur2
another user rate value supported for synchronous data service of BS61(alternate speech/data). it shall be different from the previous one if the answer to TSPX_BS_61_S_more_ur is TRUE. default value : '0100'B, 4.8 kbit/s
BITSTRING[4]
Phase 2
TSPX_BS_61_A
asynchronous data service supported by BS61(alternate speech/data) . default value : TRUE, asynchronous
BOOLEAN
Phase 2
TSPX_BS_61_A_ur1
user rate value supported for asynchronous data service of BS61(alternate speech/data). default value : '0101'B, 9.6 kbit/s
BITSTRING[4]
Phase 2
TSPX_BS_61_A_ur1_T_NT
both Transparent and Non-Transparent supported for the rate TSPX_BS_61_A_ur1 of BS61(alternate speech/data). default value : FALSE, not support both transparent and non transparent modes
BOOLEAN
Phase 2
TSPX_BS_61_A_ur1_ce
BS61(alternate speech/data). If the answer to TSPX_BS_61_A_ur1_T_NT is FALSE, the manufacturer must precise which mode is supported by the MS. Connection Element default value : '00'B, transparent
BITSTRING[2]
Phase 2
TSPX_BS_61_A_more_ur
more than one user rate for asynchronous data service supported by BS61(alternate speech/data). default value : FALSE, only one user rate
BOOLEAN
Phase 2
TSPX_BS_61_A_ur2
another user rate value supported for asynchronous data service of BS61(alternate speech/data).. it shall be different from the previous one if the answer to TSPX_BS_61_A_more_ur is TRUE. default value : '0101'B, 9.6 kbit/s
BITSTRING[4]
Phase 2
TSPX_BS_61_A_ur2_T_NT
BS61(alternate speech/data). both Transparent and Non-Transparent supported for the rate TSPX_BS_61_A_ur2 of BS61. default value : FALSE, not support both transparent and non transparent modes
BOOLEAN
Phase 2
TSPX_BS_81_S
synchronous data supported by BS 81(speech followed by data). default value : TRUE, synchronous mode
BOOLEAN
Phase 2
TSPX_BS_81_S_more_ur
more than one user rate for synchronous data service supported by BS81(speech followed by data). default value : FALSE, only one user rate
BOOLEAN
Phase 2
TSPX_BS_81_S_ur1
user rate value supported for synchronous data service of BS81(speech followed by data). default value : '0101'B, 9.6 kbit/s
BITSTRING[4]
Phase 2
TSPX_BS_81_S_ur2
another user rate value supported for synchronous data service of BS81(speech followed by data). it shall be different from the previous one if the answer to TSPX_BS_81_S_more_ur is TRUE. default value : '0101'B, 9.6 kbit/s
BITSTRING[4]
Phase 2
TSPX_BS_81_A
asynchronous data service supported by BS81(speech followed by data). default value : TRUE, asynchronous mode
BOOLEAN
Phase 2
TSPX_BS_81_A_ur1
user rate value supported for asynchronous data service of BS81(speech followed by data). default value : '0100'B, 4.8 kbit/s
BITSTRING[4]
Phase 2
TSPX_BS_81_A_ur1_T_NT
both Transparent and Non-Transparent supported for the rate TSPX_BS_81_A_ur1 of BS81(speech followed by data). default value : FALSE, not support both transparent and non transparent modes
BOOLEAN
Phase 2
TSPX_BS_81_A_ur1_ce
BS81(speech followed by data). if the answer to TSPX_BS_81_A_ur1_T_NT is FALSE, the manufacturer must precise which mode is supported by the MS. Connection Element default value : '01'B, non transparent
BITSTRING[2]
Phase 2
TSPX_BS_81_A_more_ur
more than one user rate for asynchronous data service supported by BS81(speech followed by data). default value : FALSE, only one user rate
BOOLEAN
Phase 2
TSPX_BS_81_A_ur2
another user rate value supported for asynchronous data service of BS81(speech followed by data). it shall be different from the previous one if the answer to TSPX_BS_81_A_more_ur is TRUE. default value : '0100'B, 4.8 kbit/s
BITSTRING[4]
Phase 2
TSPX_BS_81_A_ur2_T_NT
both Transparent and Non-Transparent supported for the rate TSPX_BS_81_A_ur2 of BS81(speech followed by data). default value : FALSE, not support both transparent and non transparent modes
BOOLEAN
Phase 2
TSPX_TS_61_T_NT
both Transparent and Non-Transparent supported for TS61(alternate speech and G3 fax). default value : FALSE, not support both transparent and non transparent modes
BOOLEAN
Phase 2
TSPX_TS_61_ce
TS61(alternate speech and G3 fax). if the answer to TSPX_TS_61_T_NT is FALSE, the manufacturer must precise which mode is supported by the MS. Connection Element default value : '01'B, non transparent
BITSTRING[2]
Phase 2
TSPX_TS_61_ur1
user rate for TS61(alternate speech and G3 fax). default value : '0101'B, 9.6 kbit/s
BITSTRING[4]
Phase 2
TSPX_TS_61_more_ur
more than one user rate supported for TS61(alternate speech and G3 fax). default value : FALSE, only one user rate
BOOLEAN
Phase 2
TSPX_TS_61_ur2
another user rate for TS61(alternate speech and G3 fax), it shall be different from the previous one if the answer to TSPX_TS_61_more_ur is TRUE. default value : '0101'B, 9.6 kbit/s
BITSTRING[4]
Phase 2
TSPX_TS_62_T_NT
both Transparent and Non-Transparent supported for TS62(automatic G3 fax). default value : FALSE, not support both transparent and non transparent modes
BOOLEAN
Phase 2
TSPX_TS_62_ce
TS62(automatic G3 fax). if the answer to TSPX_TS_62_T_NT is FALSE, the manufacturer must precise which mode is supported by the MS. Connection Element default value : '00'B, transparent
BITSTRING[2]
Phase 2
TSPX_TS_62_ur1
user rate for TS62(automatic G3 fax). default value : '0100'B, 4.8 kbit/s
BITSTRING[4]
Phase 2
TSPX_TS_62_more_ur
more than one user rate supported by TS62(automatic G3 fax). default value : FALSE, only one user rate
BOOLEAN
Phase 2
TSPX_TS_62_ur2
another user rate for TS62(automatic G3 fax), it shall be different from the previous one if the answer to TSPX_TS_62_more_ur is TRUE. default value : '0100'B, 4.8 kbit/s
BITSTRING[4]
Phase 2
TSPX_DTMF
call control capabilities: value '1'B means MS supports DTMF
BITSTRING[1]
Phase 2
TSPX_modF
any non signalling full rate channel mode for TC_26_6_4_1
BITSTRING[8]
Phase 2
TSPX_modH
any non signalling half channel mode for TC_26_6_4_1
BITSTRING[8]
Phase 2
TSPX_anymod
Any supported channel mode value except signalling and Full rate speech.
BITSTRING[8]
Phase 2
TSPX_CKSNA
cipher key sequence number GSM 04.08, 10.5.1.2
BITSTRING[3]
Phase 2
TSPX_CKSNB
cipher key sequence number GSM 04.08, 10.5.1.2
BITSTRING[3]
Phase 2
TSPX_CKSNC
cipher key sequence number GSM 04.08, 10.5.1.2
BITSTRING[3]
Phase 2
TSPX_CKSNDef
default cipher key sequence number GSM 04.08, 10.5.1.2
BITSTRING[3]
Phase 2
TSPX_RfPwrCap
RF power capability
GSM: '000'B Class1 to '100'B Class 5
DCS: '000'B Class1 to '010'B Class 3
BITSTRING[3]
Phase 2
TSPX_RevLevel
Revision level of classmark 1 – '00'B Phase 1, '01'B Phase 2
BITSTRING[2]
Phase 2
TSPX_CiphAlgA5_1
Default Algorithm - A5/1 algorithm: NB '0'B : available, '1'B: not available
BITSTRING[1]
Phase 2
TSPX_CiphAlgA5_2
A5/2 algorithm: '1'B : available, '0'B: not available
BITSTRING[1]
Phase 2
TSPX_CiphAlgA5_3
A5/3 algorithm: '1'B : available, '0'B: not available
BITSTRING[1]
Phase 2
TSPX_CiphAlgA5_4
A5/4 algorithm: '1'B : available, '0'B: not available
BITSTRING[1]
Phase 2
TSPX_CiphAlgA5_5
A5/5 algorithm: '1'B : available, '0'B: not available
BITSTRING[1]
Phase 2
TSPX_CiphAlgA5_6
A5/6 algorithm: '1'B : available, '0'B: not available
BITSTRING[1]
Phase 2
TSPX_CiphAlgA5_7
A5/7 algorithm: '1'B : available, '0'B: not available
BITSTRING[1]
Phase 2
TSPX_pSyncCap
pseudo synchronization capability, '0'B: not present '1'B: present
BITSTRING[1]
Phase 2
TSPX_SSscrnInd
SS screen indicator – GSM 04.80
BITSTRING[2]
Phase 2
TSPX_SMCap
Support of mobile terminated point to point short messages , '0'B: not present '1'B: present
BITSTRING[1]
Phase 2
TSPX_frqCap
EGSM frequency capability. DCS: reserved, GSM: '0'B not support extension band, '1'B support extension band
BITSTRING[1]
Phase 2
TSPX_ClsMk3
classmark 3 indicator, '0'B no addition capability info, '1'B additional capability info in class mark 3
BITSTRING[1]
Phase 2
TSPX_ESIND
Controlled Early Classmark Sending option imlementation – default =0, not implemented
BITSTRING[1]
Phase 2
TSPX_RfPwrCapAmp
RF power capability with external RF amplifier
GSM: '000'B Class1 to '100'B Class 5
DCS: '000'B Class1 to '010'B Class 3
BITSTRING[3]
Phase 2
TSPX_DTMFInd
DTMF indication to user supported
BOOLEAN
Phase 2
TSPX_IMEI
IMEI of the MS.
HEXSTRING
Phase 2
TSPX_IMEISV
IMEISV of the MS.
Used in: TC_26_6_8_5, TC_26_7_3_1
HEXSTRING
Phase 2
TSPX_TC1M
timer value for GSM timer TC1M (for SMS)
INTEGER
Phase 2
TSPX_MaxCPDataRetx
max. number of CP data retransmissions for SMS
INTEGER
Phase 2
TSPX_ Immconn
Immediate connect for telephony supported ?
BOOLEAN
Phase 2
TSPX_Uupd
user-user protocol discriminator for TC_26_8_3
BITSTRING[8]
Phase 2
TSPX_UuInfo
user-user information for TC_26_8_3
OCTETSTRING
Phase 2
TSPX_UIC
VGCS uplink identity code
BITSTRING[6]
R96
TSPX_T_Term
Max. wait time for termination of a MO call after sending TERMINATION REQUEST
INTEGER (ms)
R96
A.7.2 MMI information
Description
Release
How is the Accumulated Call Meter (ACM) on the SIM read ?
NOTE: Used in Operation OO_ACMIncCHK and OO_ACMReading.
Phase 2
How is the ACM on the SIM reset to zero, and ACMmax set to 2 units?
NOTE: Used in Operation OO_ACMSetting.
Phase 2
How is power amplification added to the mobile and removed?
NOTE: Used in Operation OO_AddPwrAmp and OO_RemvPwrAmp.
Phase 2
What alerting indication is given by the mobile?
NOTE: Used in Operation OO_AltIndCHK.
Phase 2
How is the called party number displayed on the mobile?
NOTE: Used in Operation OO_CalledNumCHK and OO_CalledPtyNumCHK.
Phase 2
How is a call placed on Hold?
NOTE: Used in Operation OO_CallHold.
Phase 2
How is the presence of short messages checked in the mobile and how are they displayed?
NOTE: Used in Operation OO_CheckAllSMPresentBut4th and OO_CheckMessageDisplayed and OO_DisplaySMAndSendReplySM and OO_ReadSMAndRemove and OO_RecallAndDisplaySM.
Phase 2
How is the presence of Cell Broadcast short messages in the mobile checked?
NOTE: Used in Operation OO_CheckCBSMReceived.
Phase 2
How is it checked whether the memory capacity of the SIM has been exceeded?
NOTE: Used in Operation OO_CheckMCEFOnSIM and OO_CheckMCEFOnSIMUnset.
Phase 2
How and where is the SIM inserted and removed?
NOTE: Used in Operation OO_ConnectSIMSimulator and OO_SIMIns and OO_SIM2Ins and OO_SIM3Ins and OO_SIMRmv.
Phase 2
Does the MS have an 'END' key? If not, what method is used to replace its function?
NOTE: Used in Operation OO_DepressEndKey.
Phase 2
How is a number entered in order to make an outgoing call?
NOTE: Used in Operation OO_DiallCalledNum.
Phase 2
How is a reply to a received short message sent?
NOTE: Used in Operation OO_DisplaySMAndSendReplySM.
Phase 2
How is it checked which DTMF character has been sent?
NOTE: Used in Operation OO_DTMFIndCHK.
Phase 2
How is the message store of the MS emptied?
NOTE: Used in OO_EmptyMessageStorage.
Phase 2
How is a password on the MS entered?
NOTE: Used in Operation OO_EnterPswd.
Phase 2
How is an incoming call answered?
NOTE: Used in Operation OO_HookOff.
Phase 2
For each service on the MS which requires the MS to be connected to an interface on other equipment (e.g. a computer), how is that interface set up for the purpose?
NOTE: Used in Operation OO_IFsetup.
Phase 2
How is an In-Call modification initiated on the MS?
NOTE: Used in Operation OO_InCallMod.
Phase 2
For each mobile originating basic service supported by the MS, how is the MS configured to make an outgoing call on that service?
NOTE: Used in Operation OO_InitCall.
Phase 2
How is the MS to configured accept standard MMI sequences for the initiation of supplementary services?
NOTE: Used in Operation OO_InitSS
Phase 2
How is the MS checked whether it is in the normal service state (idle, updated).
NOTE: Used in Operation OO_InServiceCHK and OO_PressKeyWhenInService.
Phase 2
How is a Multi-Party call initiated on the MS.
NOTE: Used in Operation OO_MptyCall
Phase 2
How is the MS configured to store received Class 1 short messages in the mobile equipment (rather than in the SIM)?
NOTE: Used in Operation OO_MSSetupStoreClass1SMInMEMemory.
Phase 2
How is the list of available PLMNs checked?
NOTE: Used in Operation OO_PLMNsCHK.
Phase 2
How is the PLMN selection mode switched to automatic selection.
NOTE: Used in operation OO_PLMNselModeAuto.
Phase 2
How is the PLMN selection mode switched to manual selection.
NOTE: Used in operation OO_PLMNselModeMan.
Phase 2
How is the power source for the MS removed and replaced. (Note, this is not the same as switching the Mobile on and off using the on/off switch.)
NOTE: Used in operation OO_PowerUp and OO_PowerDown.
Phase 2
How is a short message removed from the message store?
NOTE: Used in operation OO_ReadSMAndRemove.
Phase 2
When in manual PLMN selection mode, how is a PLMN selected?
NOTE: Used in OperationOO_SelPLMN
Phase 2
How is a short message sent from the MS?
NOTE: Used in operation OO_SendMOShortMessage.
Phase 2
How is an SMS COMMAND message sent to delete the last short message sent?
NOTE: Used in OO_SendSMSCOMMANDDe.
Phase 2
How is an SMS COMMAND message sent enquiring about the last short message sent?
NOTE: Used in OO_SendSMS_COMMANDEnq
Phase 2
How is Call Refusal set on the MS?
NOTE: Used in Operation OO_SetRefuseCall.
Phase 2
How is a DTMF digit sent?
NOTE: Used in operation OO_ShortKeyDepr.
Phase 2
How is it checked whether a supplementary service result is correct?
NOTE: Used in Operation OO_SSresultCHK
Phase 2
How is the MS switched on and off?
NOTE: Used in operation OO_SwitchOn and OO_SwitchOff.
Phase 2
How is a call cleared?
NOTE: Used in operation OO_TermCall.
Phase 2
How does the ASCI MS indicate to the user that an user action is needed for showing the desire of talking?
NOTE: Used in operation OO_CheckAsciUserTalkInd.
R96
How is a desire of talking from the user set at the ASCI MS?
NOTE: Used in operation OO_AsciUserDesireTalking.
R96
How does the MS indicate a received notification for a group or broadcast call? How is the call reference indicated?
NOTE: Used in operation OO_CheckNotifInd
R96
How is a rejection of a group or broadcast call set at the MS when the new group or broadcast call has been indicated?
NOTE: Used in operation OO_RejecAsciCall
R96
How does the MS indicate a rejection to an intended request of the user?
NOTE: Used in operation OO_CheckAsciReject
R96
How does the MS indicate a received paging information for an MT call when it is in group receive mode or group transmit mode
NOTE: Used in operation OO_CheckPagingInfoIndication
R96
How is a rejection of an MT call set at the MS when it is in group receive mode or group transmit mode and has indicated a paging for the MT call?
NOTE: Used in operation OO_RejectMTCall
R96
How does the MS indicate the downlink channel is muted?
NOTE: Used in operation OO_DownlinkMuted
R96
How is the MS set to be ready for a VGCS configuration or for a VBS configuration?
NOTE: Used in operation OO_Ifsetup_Asci
R96
How is a VGCS or a VBS call at the MS initiated?
NOTE: Used in operation OO_Initcall_Asci
R96
How is a VGCS or a VBS fast call at the MS initiated?
NOTE: Used in operation OO_InitImmediateCall_Asci
R96
How does the MS join a notified VGCS or a VBS call?
NOTE: Used in operation OO_Join_AsciCall
R96
How does the MS end an uplink access in a VGCS call?
NOTE: Used in operation OO_VGCS_QuitUplinkAccess
R96
How does the MS request an uplink access in a VGCS call?
NOTE: Used in operation OO_VGCS_RequestUplinkAccess
R96
How is a priority level set at the MS for an attemp VGCS or VBS call?
NOTE: Used in operation OO_SelectPriorityLevel
R96
How is a VGCS or VBS listening stopped?
NOTE: Used in operation OO_StopAsciListening
R96
How does the MS indicate that a call has been automatically answered?
NOTE: Used in operation OO_CheckCallAutoAnswered
R96
How is implicit USS1 activated ?
NOTE: Used in operation OO_ActivateImplicitUUS1
R00
How does the MS display a UUS string ?
NOTE: Used in operation OO_CheckUUSDisplay
R00
How does the MS display the Follow Me responses received from the network ?
NOTE: Used in operation OO_CheckUssdDisplay
R00
How is the User-to-Dispatcher activated?
NOTE: Used in operation OO_ActivateUTDI
R00
A.7.3 Test house specified parameters
Item
Description
Type/Allowed values
Value chosen
Release
TSPX_AltNb
use alternative neighbour cells description. default : FALSE
BOOLEAN
Phase 2
TSPX_CphAlgA
ciphering algorithm identifier – '000' A5/1 to '110' A5/7
OCTETSTRING [1]
Phase 2
TSPX_CphAlgB
ciphering algorithm identifier – '000' A5/1 to '110' A5/7
OCTETSTRING [1]
Phase 2
TSPX_CphAlgC
ciphering algorithm identifier – '000' A5/1 to '110' A5/7
OCTETSTRING [1]
Phase 2
TSPX_CphAlgD
ciphering algorithm identifier – '000' A5/1 to '110' A5/7
OCTETSTRING [1]
Phase 2
TSPX_CphAlgE
ciphering algorithm identifier – '000' A5/1 to '110' A5/7
OCTETSTRING [1]
Phase 2
TSPX_CphAlgDef
default ciphering algorithm identifier – '000' A5/1 to '110' A5/7
OCTETSTRING [1]
Phase 2
TSPX_NoOfHoAccA
number of handover access bursts, value range 10 - 20 TC_26_6_5_1(M=1, 8) TC_26_6_5_2(M=1,8) TC_26_6_5_4_1 TC_26_10_2_4_1 TC_26_10_2_4_2 TC_26_12_2_1(M=1,4,7,11) TC_26_12_2_2(M=1,4,7,8,11)
TC_26_11_2_2_1 TC_26_11_5_1 TC_26_11_5_2
INTEGER
Phase 2
TSPX_NoOfHoAccB
number of handover access bursts, value range 10 - 20 TC_26_6_5_1(M=2) TC_26_6_5_2(M=6,9) TC_26_12_2_1(M=2,5,8,13) TC_26_12_2_2(M=2,5,9)
TC_26_11_2_2_1
INTEGER
Phase 2
TSPX_NoOfHoAccC
number of handover access bursts, value range 10 - 20 TC_26_6_5_1(M=3) TC_26_6_5_2(M=7) TC_26_12_2_1(M=3,6,9,15) TC_26_12_2_2(M=3,6,10)
TC_26_11_2_2_1
INTEGER
Phase 2
TSPX_NoOfHoAccD
number of handover access bursts, value range 5 - 10 TC_26_6_5_1(M=4, 7) TC_26_6_5_2(M=2) TC_26_12_2_1(M=10)
INTEGER
Phase 2
TSPX_NoOfHoAccE
number of handover access bursts, value range 5 - 10 TC_26_6_5_1(M=5) TC_26_6_5_2(M=5) TC_26_12_2_2(M=12)
INTEGER
Phase 2
TSPX_NoOfHoAccF
number of handover access bursts, value range 5 - 10 TC_26_6_5_1(M=6) TC_26_6_5_2(M=10) TC_26_12_2_1(M=14)
INTEGER
Phase 2
TSPX_NoOfHoAccG
number of handover access bursts, value range 2 – 5 TC_26_6_5_2_3
INTEGER
Phase 2
TSPX_NoOfHoAccH
number of handover access bursts, value range 2 - 5 TC_26_6_5_2_4
INTEGER
Phase 2
TSPX_NoOfHoAccI
number of handover access bursts, value range 2 - 5 TC_26_10_2_4_1
INTEGER
Phase 2
TSPX_HoRefA
Hand over reference,
GSM 04.08, 10.5.2.15 TC_26_6_5_1(M=1) TC_26_6_5_2(M=1) TC_26_6_5_4_1 TC_26_10_2_4_2 TC_26_12_2_1(M=1,11) TC_26_12_2_2(M=1)
TC_26_11_5_1 TC_26_11_5_2
BITSTRING [8]
Phase 2
TSPX_HoRefB
Hand over reference,
GSM 04.08, 10.5.2.15 TC_26_6_5_1(M=2, 8) TC_26_6_5_2(M=2) TC_26_12_2_1(M=2,12)
TC_26_11_2_2_1
BITSTRING [8]
Phase 2
TSPX_HoRefC
Hand over reference,
GSM 04.08, 10.5.2.15 TC_26_6_5_1(M=3) TC_26_6_5_2(M=3) TC_26_12_2_1(M=3,13) TC_26_12_2_2(M=3,6,10)
TC_26_11_2_2_1
BITSTRING [8]
Phase 2
TSPX_HoRefD
Hand over reference,
GSM 04.08, 10.5.2.15 TC_26_6_5_1(M=4) TC_26_6_5_2(M=4) TC_26_12_2_1(M=4,14)
BITSTRING [8]
Phase 2
TSPX_HoRefE
Hand over reference,
GSM 04.08, 10.5.2.15 TC_26_6_5_1(M=5) TC_26_6_5_2(M=5) TC_26_12_2_1(M=5,15)
BITSTRING [8]
Phase 2
TSPX_HoRefF
Hand over reference,
GSM 04.08, 10.5.2.15 TC_26_6_5_1(M=6) TC_26_6_5_2(M=6) TC_26_12_2_1(M=6)
BITSTRING [8]
Phase 2
TSPX_HoRefG
Hand over reference,
GSM 04.08, 10.5.2.15 TC_26_6_5_1(M=7) TC_26_6_5_2(M=7) TC_26_12_2_1(M=7)
BITSTRING [8]
Phase 2
TSPX_HoRefH
Hand over reference,
GSM 04.08, 10.5.2.15 TC_26_6_5_2(M=8) TC_26_12_2_1(M=8)
BITSTRING [8]
Phase 2
TSPX_HoRefI
Hand over reference,
GSM 04.08, 10.5.2.15 TC_26_6_5_2(M=9) TC_26_12_2_1(M=9)
BITSTRING [8]
Phase 2
TSPX_HoRefJ
Hand over reference,
GSM 04.08, 10.5.2.15 TC_26_6_5_2(M=10) TC_26_12_2_1(M=10)
BITSTRING [8]
Phase 2
TSPX_HSN
Hopping sequence number
value range: 0 – 63 (0=Cyclic Hopping)
INTEGER
Phase 2
TSPX_IMSI
IMSI of the MS – Phase 2 Test SIM value - 001010123456063
HEXSTRING
Phase 2
TSPX_Ki
default authentication key used in testing
BITSTRING
Phase 2
TSPX_MAIO
mobile allocation index offset, value range: 0 - 63
INTEGER
Phase 2
TSPX_MaxRetrans
Max-Retrans –Maximum number of re-transmissons of Channel Requests as defined in System Information (values 1, 2, 4 or 7 re-transmissions)
INTEGER
Phase 2
TSPX_MSTxpwrMax
maximum output power from MS GSM 05.05, 4.1.1
0..31
Phase 2
TSPX_PwrlvlA
MS power level, value between 2 to 15 GSM 05.05, 4.1.1
INTEGER
Phase 2
TSPX_PwrlvlB
MS power level, value between 2 to 15 GSM 05.05, 4.1.1
INTEGER
Phase 2
TSPX_PwrlvlC
MS power level, value between 2 to 15 GSM 05.05, 4.1.1
INTEGER
Phase 2
TSPX_PwrlvlD
MS power level, value between 2 to 15 GSM 05.05, 4.1.1
INTEGER
Phase 2
TSPX_RANDA
challenge RAND
BITSTRING [128]
Phase 2
TSPX_RANDB
challenge RAND
BITSTRING [128]
Phase 2
TSPX_RANDC
challenge RAND
BITSTRING [128]
Phase 2
TSPX_RANDDef
default challenge RAND
BITSTRING [128]
Phase 2
TSPX_SDCCH4SubA
TDMA offset of SDCCH/4 subchannel
BITSTRING[2]
Phase 2
TSPX_SDCCH4SubB
TDMA offset of SDCCH/4 subchannel
BITSTRING[2]
Phase 2
TSPX_SDCCH4SubC
TDMA offset of SDCCH/4 subchannel
BITSTRING[2]
Phase 2
TSPX_SDCCH4SubDef
TDMA offset of default SDCCH/4 subchannel
BITSTRING[2]
Phase 2
TSPX_SDCCH8SubA
TDMA offset of SDCCH/8 subchannel
BITSTRING[3]
Phase 2
TSPX_SDCCH8SubB
TDMA offset of SDCCH/8 subchannel
BITSTRING[3]
Phase 2
TSPX_SDCCH8SubC
TDMA offset of SDCCH/8 subchannel
BITSTRING[3]
Phase 2
TSPX_SDCCH8SubD
TDMA offset of SDCCH/8 subchannel
BITSTRING[3]
Phase 2
TSPX_SDCCH8SubE
TDMA offset of SDCCH/8 subchannel
BITSTRING[3]
Phase 2
TSPX_SDCCH8SubF
TDMA offset of SDCCH/8 subchannel
BITSTRING[3]
Phase 2
TSPX_SDCCH8SubG
TDMA offset of SDCCH/8 subchannel
BITSTRING[3]
Phase 2
TSPX_SDCCH8SubDef
TDMA offset of default SDCCH/8 subchannel
BITSTRING[3]
Phase 2
TSPX_TimadvA
timing advance in bit periods
INTEGER
Phase 2
TSPX_TimadvB
timing advance in bit periods
INTEGER
Phase 2
TSPX_TimadvC
timing advance in bit periods
INTEGER
Phase 2
TSPX_TmSltA
time slot, GSM 04.08 10.5.2.5
BITSTRING [3]
Phase 2
TSPX_TmSltB
time slot, GSM 04.08 10.5.2.5
BITSTRING [3]
Phase 2
TSPX_TmSltC
time slot, GSM 04.08 10.5.2.5
BITSTRING [3]
Phase 2
TSPX_TmSltD
time slot, GSM 04.08 10.5.2.5
BITSTRING [3]
Phase 2
TSPX_TmSltE
time slot, GSM 04.08 10.5.2.5
BITSTRING [3]
Phase 2
TSPX_TmSltF
time slot, GSM 04.08 10.5.2.5
BITSTRING [3]
Phase 2
TSPX_TmSltG
time slot, GSM 04.08 10.5.2.5
BITSTRING [3]
Phase 2
TSPX_TmSltDef
default time slot, GSM 04.08 10.5.2.5
BITSTRING [3]
Phase 2
TSPX_TmSltNotZero
time slot, arbitrarily value, but not zero.
BITSTRING [3]
Phase 2
TSPX_TmSltNotZero1
time slot, arbitrarily value, but not zero and not TSPX_TmSltNotZero
BITSTRING [3]
Phase 2
TSPX_Txint
Tx-Integer, no of slots to spread transmission (values 3,4,5,6,7,8,9,10,11,12,14,16, 20,25,32 or 50)
INTEGER
Phase 2
TSPX_TscA
training sequence code, GSM 04.08 10.5.2.5
BITSTRING [3]
Phase 2
TSPX_TscB
training sequence code, GSM 04.08 10.5.2.5
BITSTRING [3]
Phase 2
TSPX_TscC
training sequence code, GSM 04.08 10.5.2.5
BITSTRING [3]
Phase 2
TSPX_TscD
training sequence code, GSM 04.08 10.5.2.5
BITSTRING [3]
Phase 2
TSPX_TscE
training sequence code, GSM 04.08 10.5.2.5
BITSTRING [3]
Phase 2
TSPX_TscF
training sequence code, GSM 04.08 10.5.2.5
BITSTRING [3]
Phase 2
TSPX_TscG
training sequence code, GSM 04.08 10.5.2.5
BITSTRING [3]
Phase 2
TSPX_TscDef
default training sequence code, GSM 04.08 10.5.2.5
BITSTRING [3]
Phase 2
TSPX_T3122
value of timer T3122, HEXSTRING[2]
HEXSTRING [2]
Phase 2
TSPX_TCHcarrierA_ho
the value can be choosen arbitrarily from cell allocation of cell A (GSM), but not BCCH carrier .possible value is : 10, 17, 26, 34, 42, 45, 46, 52, 59, 66, 73, 74, 75, 76, 108, 114
INTEGER
Phase 2
TSPX_TCHcarrierA_hod
the value can be choosen arbitrarily from cell allocation of cell A (DCS), but not BCCH carrier . possible value is : 734,741,754,759,762,766,767,773,775,779,782,791,798,829,832,844
INTEGER
Phase 2
TSPX_TCHcarrierB
TCH and SDCCH channel frequency number of cell B (GSM)
INTEGER
Phase 2
TSPX_TCHcarrierBd
TCH and SDCCH channel frequency number of cell B (DCS)
INTEGER
Phase 2
TSPX_TCHcarrierB_ho
the value can be choosen arbitrarily from cell allocation of cell B (GSM), but not BCCH carrier . possibles value is : 14,18,22,24,30,31,38,60,66,73,74,75,76,108,114
INTEGER
Phase 2
TSPX_TCHcarrierB_hod
not BCCH carrier of cell B. the value can be choosen arbitrarily from cell allocation of cell B (DCS), which is (739,743,746,749,756,758,761,771,779,782,791,798,829,832,844)
INTEGER
Phase 2
TSPX_TCHcarrierB2_ho
Choosen arbitrarly from cell allocation B for GSM HO cases, but not BCCH carrier!
INTEGER
Phase 2
TSPX_TCHcarrierB2_hod
Choosen arbitrarly from cell allocation B for DCS HO cases, but not BCCH carrier!
INTEGER
Phase 2
TSPX_TCHHSubA
TDMA offset of half rate subchannel
BITSTRING[1]
Phase 2
TSPX_TCHHSubDef
TDMA offset of default half rate subchannel
BITSTRING[1]
Phase 2
TSPX_TMSI
TMSI of the MS used in test
OCTETSTRING[4]
Phase 2
TSPX_TMSI1
another TMSI used in test which shall differ from TSPX_TMSI,
TSPX_TMSI + '01'O
TSPX_TMSI + '02'O
TSPX_TMSI + '03'O
OCTETSTRING[4]
Phase 2
TSPX_k
timing of cell A before cell B k bit periods for TC_26_6_5_1_?, TC_26_6_5_2_?, TC_26_6_5_4_?, TC_26_6_5_3_?.
INTEGER
Phase 2
TSPX_y
timing advance for TC_26_6_5_4_?, TC_26_6_5_3_? TC_26_6_5_5_?,. the values of TSPX_k (or TSPX_k1) and TSPX_y shall be 0 < (2*TSPX_k + TSPX_y) MOD 256 < 60.
INTEGER
Phase 2
TSPX_k1
timing of cell A before cell B k bit periods for TC_26_6_5_5
INTEGER
Phase 2
TSPX_k2
timing of cell A before cell B k bit periods for TC_26_6_5_6
INTEGER
Phase 2
TSPX_y2
timing advance for TC_26_6_5_6, value range : 11 - 62.
INTEGER
Phase 2
TSPX_k3
timing of cell A before cell B k bit periods for TC_26_6_5_7
INTEGER
Phase 2
TSPX_y3
timing advance for TC_26_6_5_7
INTEGER
Phase 2
TSPX_nPara
the n'th ChReq for TC_26_6_1_2, shall be choose to [1..8], MAXRETRANS for TC_26_6_1_2 is 7 (See 11.10 for more explaination).
INTEGER
Phase 2
TSPX_kPara
the k'th ChReq for TC_26_6_1_2 (range 4…8)
INTEGER
Phase 2
TSPX_rPara
the r'th ChReq for TC_26_6_1_2 (range 4…8)
INTEGER
Phase 2
TSPX_i1Para
for TC_26_1_2(TSPX_nPara-3) < TSPX_i1Para <= TSPX_nPara
INTEGER
Phase 2
TSPX_i2Para
for TC_26_1_2
0 < TSPX_i2Para <= (TSPX_kPara-3)
INTEGER
Phase 2
TSPX_i3Para
for TC_26_1_2(TSPX_rPara-3) < TSPX_i3Para <= TSPX_rPara
INTEGER
Phase 2
TSPX_n1Para
the n'th ChReq for TC_26_6_1_3 (range 1…8)
INTEGER
Phase 2
TSPX_i4Para
for TC_26_6_1_3 (TSPX_n1Para-3) < TSPX_i4Para <= TSPX_n1Para
INTEGER
Phase 2
TSPX_xPara
t3122 for TC_26_6_1_3 (range 5…255)
INTEGER
Phase 2
TSPX_AGBLKS1
BS-AG-BLKS-RES for TC_26_6_2_3_1, TC_26_6_2_1_1
INTEGER
Phase 2
TSPX_PAMFRMS1
BS-PA-MFRMS for TC_26_6_2_3_1 (shall not be set to 9), TC_26_6_2_1_1
INTEGER
Phase 2
TSPX_CcchConf1
CCCH configuration for TC_26_6_2_3_1, TC_26_6_2_1_1
BITSTRING[3]
Phase 2
TSPX_PgSubch
paging subchannel for TC_26_6_2_3_1
INTEGER
Phase 2
TSPX_AGBLKS2
BS-AG-BLKS-RES for TC_26_6_2_3_2 (range 0…2), TC_26_6_2_1_2
INTEGER
Phase 2
TSPX_PAMFRMS2
BS-PA-MFRMS for TC_26_6_2_3_2, TC_26_6_2_1_2
INTEGER
Phase 2
TSPX_CcchConf2
CCCH configuration for TC_26_6_2_3_2, TC_26_6_2_1_2
BITSTRING[3]
Phase 2
TSPX_AGBLKS3
BS-AG-BLKS-RES for TC_26_6_2_4, TC_26_6_2_2, TC_26_6_2_1_3
INTEGER
Phase 2
TSPX_PAMFRMS3
BS-PA-MFRMS for TC_26_6_2_4, TC_26_6_2_2, TC_26_6_2_1_3
INTEGER
Phase 2
TSPX_CcchConf3
CCCH configuration for TC_26_6_2_4, TC_26_6_2_2, TC_26_6_2_1_3
BITSTRING[3]
Phase 2
TSPX_AGBLKS4
BS-AG-BLKS-RES for TC_26_6_2_5
INTEGER
Phase 2
TSPX_PAMFRMS4
BS-PA-MFRMS for TC_26_6_2_5
INTEGER
Phase 2
TSPX_CcchConf4
CCCH configuration for TC_26_6_2_5 (shall be in the set ('010', '100', '110'))
BITSTRING[3]
Phase 2
TSPX_Chtp1
channel type and TDMA offset for TC_26_6_13_1, any value supported by the MS
BITSTRING[5]
Phase 2
TSPX_ChMod1
channel mode for TC_26_6_13_1, any value for the channel type of TSPX_Chtp1
BITSTRING[8]
Phase 2
TSPX_Maio1
Mobile allocation index offset hopping parameter for TC_26_6_13_1, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma1, default : 2
INTEGER
Phase 2
TSPX_Ma1
mobile allocation (GSM 04.08 10.5.2.21) for TC_26_6_13_1, its value shall indicate number of frequencies between 1 and 17. default : '010101'O
OCTETSTRING[3]
Phase 2
TSPX_Hsn1
hopping sequence number for TC_26_6_13_1. default: 1
INTEGER
Phase 2
TSPX_Maio2
Mobile allocation index offset hopping parameter for TC_26_6_13_1, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma2, default : 8
INTEGER
Phase 2
TSPX_Ma2
mobile allocation for TC_26_6_13_1, its value shall indicate number of frequencies between 1 and 17. default :'01362A5'O
OCTETSTRING[3]
Phase 2
TSPX_Hsn2
hopping sequence number for TC_26_6_13_1, default : 6
INTEGER
Phase 2
TSPX_Maio3
Mobile allocation index offset hopping parameter for TC_26_6_13_1, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma3, default : 14
INTEGER
Phase 2
TSPX_Ma3
mobile allocation for TC_26_6_13_1, its value shall indicate number of frequencies between 1 and 17. default :'01FFFA'O
OCTETSTRING[3]
Phase 2
TSPX_Hsn3
hopping sequence number for TC_26_6_13_1, default : 0
INTEGER
Phase 2
TSPX_Chtp2
channel type for TC_26_6_13_2, any value supported by the MS
BITSTRING[5]
Phase 2
TSPX_ChMod2
channel mode for TC_26_6_13_2
BITSTRING[8]
Phase 2
TSPX_Maio4
Mobile allocation index offset hopping parameter for TC_26_6_13_2, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma4, default : 3
INTEGER
Phase 2
TSPX_Ma4
mobile allocation for TC_26_6_13_2, its value shall indicate number of frequencies between 1 and 17. default : '001141'O
OCTETSTRING[3]
Phase 2
TSPX_Hsn4
hopping sequence number for TC_26_6_13_2, default : 0
INTEGER
Phase 2
TSPX_Maio5
Mobile allocation index offset hopping parameter for TC_26_6_13_2, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma5, default : 9
INTEGER
Phase 2
TSPX_Ma5
mobile allocation for TC_26_6_13_2, its value shall indicate number of frequencies between 1 and 17. default : '01ABCB'O
OCTETSTRING[3]
Phase 2
TSPX_Hsn5
hopping sequence number for TC_26_6_13_2, default : 16
INTEGER
Phase 2
TSPX_Chtp3
channel type for TC_26_6_13_3, any value supported by the MS
BITSTRING[5]
Phase 2
TSPX_Maio6
Mobile allocation index offset hopping parameter for TC_26_6_13_3, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma6, default : 4
INTEGER
Phase 2
TSPX_Ma6
mobile allocation for TC_26_6_13_3, its value shall indicate number of frequencies between 1 and 17. default :'006248'O
OCTETSTRING[3]
Phase 2
TSPX_Hsn6
hopping sequence number for TC_26_6_13_3, default : 4
INTEGER
Phase 2
TSPX_Maio7
Mobile allocation index offset hopping parameter for TC_26_6_13_3, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma7, default : 10
INTEGER
Phase 2
TSPX_Ma7
mobile allocation for TC_26_6_13_3, its value shall indicate number of frequencies between 2 and 17. default : '009AFB'O
OCTETSTRING[3]
Phase 2
TSPX_Chtp4
channel type for TC_26_6_13_3, any value supported by the MS
BITSTRING[5]
Phase 2
TSPX_Maio8
Mobile allocation index offset hopping parameter for TC_26_6_13_3, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma8, default : 1
INTEGER
Phase 2
TSPX_Ma8
mobile allocation for TC_26_6_13_3, its value shall indicate number of frequencies between 2 and 17. default : '002800'O
OCTETSTRING[3]
Phase 2
TSPX_Hsn8
hopping sequence number for TC_26_6_13_3, default : 40
INTEGER
Phase 2
TSPX_Maio9
Mobile allocation index offset hopping parameter for TC_26_6_13_3, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma9, default : 15
INTEGER
Phase 2
TSPX_Ma9
mobile allocation for TC_26_6_13_3, its value shall indicate number of frequencies between 2 and 17. default : '01FFFB'O
OCTETSTRING[3]
Phase 2
TSPX_Hsn9
hopping sequence number for TC_26_6_13_3, default : 8
INTEGER
Phase 2
TSPX_Chtp5
SDDCH8 subchannel immediately assigned in TC_26_6_13_4
BITSTRING[5]
Phase 2
TSPX_Maio10
Mobile allocation index offset hopping parameter for TC_26_6_13_4, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma10, default : 5
INTEGER
Phase 2
TSPX_Ma10
mobile allocation for TC_26_6_13_4, its value shall indicate number of frequencies between 1 and 17. default : '01D082'O
OCTETSTRING[3]
Phase 2
TSPX_Hsn10
hopping sequence number for TC_26_6_13_4, default: 0
INTEGER
Phase 2
TSPX_Maio11
Mobile allocation index offset hopping parameter for TC_26_6_13_4, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma11, default : 11
INTEGER
Phase 2
TSPX_Ma11
mobile allocation for TC_26_6_13_4, its value shall indicate number of frequencies between 2 and 17. default : '00CFF3'O
OCTETSTRING[3]
Phase 2
TSPX_Chtp6
channel type of a non existing channel in the Assignment Command for TC_26_6_13_4
BITSTRING[5]
Phase 2
TSPX_Maio12
Mobile allocation index offset hopping parameter for TC_26_6_13_4, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma12, default : 1
INTEGER
Phase 2
TSPX_Ma12
mobile allocation for TC_26_6_13_4, its value shall indicate number of frequencies between 1 and 17. default : '010100'O
OCTETSTRING[3]
Phase 2
TSPX_Hsn12
hopping sequence number for TC_26_6_13_4, default : 39
INTEGER
Phase 2
TSPX_Maio13
Mobile allocation index offset hopping parameter for TC_26_6_13_4, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma13, default : 6
INTEGER
Phase 2
TSPX_Ma13
mobile allocation for TC_26_6_13_4, its value shall indicate number of frequencies between 1 and 17. default : '00E690'O
OCTETSTRING[3]
Phase 2
TSPX_Hsn13
hopping sequence number for TC_26_6_13_4, default: 42
INTEGER
Phase 2
TSPX_Chtp7
channel type for TC_26_6_13_5
BITSTRING[5]
Phase 2
TSPX_ChMod4
channel mode for TC_26_6_13_5
BITSTRING[8]
Phase 2
TSPX_Maio14
Mobile allocation index offset hopping parameter for TC_26_6_13_5, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma14, default : 4
INTEGER
Phase 2
TSPX_Ma14
mobile allocation for TC_26_6_13_5, its value shall indicate number of frequencies between 1 and 17. default : '004A28'O
OCTETSTRING[3]
Phase 2
TSPX_Hsn14
hopping sequence number for TC_26_6_13_5, default : 50
INTEGER
Phase 2
TSPX_Maio15
Mobile allocation index offset hopping parameter for TC_26_6_13_5, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma15, default : 12
INTEGER
Phase 2
TSPX_Ma15
mobile allocation for TC_26_6_13_5, its value shall indicate number of frequencies between 1 and 16. default : '00FF79'O
OCTETSTRING[3]
Phase 2
TSPX_Hsn15
hopping sequence number for TC_26_6_13_5, default : 33
INTEGER
Phase 2
TSPX_Maio16
Mobile allocation index offset hopping parameter for TC_26_6_13_5, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma16, default : 2
INTEGER
Phase 2
TSPX_Ma16
mobile allocation for TC_26_6_13_5, its value shall indicate number of frequencies between 1 and 16. default : '001110'O
OCTETSTRING[3]
Phase 2
TSPX_Hsn16
hopping sequence number for TC_26_6_13_5, default : 21
INTEGER
Phase 2
TSPX_Chtp8
channel type for TC_26_6_13_6
BITSTRING[5]
Phase 2
TSPX_ChMod5
channel mode for TC_26_6_13_6
BITSTRING[8]
Phase 2
TSPX_Maio17
Mobile allocation index offset hopping parameter for TC_26_6_13_6, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma17, default : 7
INTEGER
Phase 2
TSPX_Ma17
mobile allocation for TC_26_6_13_6, its value shall indicate number of frequencies between 1 and 17. default : '00E6A1'O
OCTETSTRING[3]
Phase 2
TSPX_Hsn17
hopping sequence number for TC_26_6_13_6, default : 22
INTEGER
Phase 2
TSPX_Maio18
Mobile allocation index offset hopping parameter for TC_26_6_13_6, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma18, default : 13
INTEGER
Phase 2
TSPX_Ma18
mobile allocation for TC_26_6_13_6, its value shall indicate number of frequencies between 1 and 16. default : '00FFF9'O
OCTETSTRING[3]
Phase 2
TSPX_Hsn18
hopping sequence number for TC_26_6_13_6, default : 9
INTEGER
Phase 2
TSPX_Maio19
Mobile allocation index offset hopping parameter for TC_26_6_13_6, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma19, default : 3
INTEGER
Phase 2
TSPX_Ma19
mobile allocation for TC_26_6_13_6, its value shall indicate number of frequencies between 1 and 16. default : '001111'O
OCTETSTRING[3]
Phase 2
TSPX_Hsn19
hopping sequence number for TC_26_6_13_6, default : 44
INTEGER
Phase 2
TSPX_Chtp9
channel type for TC_26_6_13_7
BITSTRING[5]
Phase 2
TSPX_ChMod6
channel mode for TC_26_6_13_7
BITSTRING[8]
Phase 2
TSPX_Maio20
Mobile allocation index offset hopping parameter for TC_26_6_13_7, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma20, default : 8
INTEGER
Phase 2
TSPX_Ma20
mobile allocation for TC_26_6_13_7, its value shall indicate number of frequencies between 1 and 17. default : '016699'O
OCTETSTRING[3]
Phase 2
TSPX_Hsn20
hopping sequence number for TC_26_6_13_7, default : 30
INTEGER
Phase 2
TSPX_Maio21
Mobile allocation index offset hopping parameter for TC_26_6_13_7, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma21, default : 14
INTEGER
Phase 2
TSPX_Ma21
mobile allocation for TC_26_6_13_7, its value shall indicate number of frequencies between 1 and 17. default : '01FEFB'O
OCTETSTRING[3]
Phase 2
TSPX_Chtp10
channel type for TC_26_6_13_7
BITSTRING[5]
Phase 2
TSPX_Maio22
Mobile allocation index offset hopping parameter for TC_26_6_13_7, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma22, default : 4
INTEGER
Phase 2
TSPX_Ma22
mobile allocation for TC_26_6_13_7, its value shall indicate number of frequencies between 1 and 16. default : '006241'O
OCTETSTRING[3]
Phase 2
TSPX_Hsn22
hopping sequence number for TC_26_6_13_7, default : 11
INTEGER
Phase 2
TSPX_Maio23
Mobile allocation index offset hopping parameter for TC_26_6_13_7, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma23, default : 11
INTEGER
Phase 2
TSPX_Ma23
mobile allocation for TC_26_6_13_7, its value shall indicate number of frequencies between 1 and 16. default : '00FF1B'O
OCTETSTRING[3]
Phase 2
TSPX_Hsn23
hopping sequence number for TC_26_6_13_7, default : 60
INTEGER
Phase 2
TSPX_Chtp11
SDCCH8 subchannel immediately assigned, TC_26_6_13_8
BITSTRING[5]
Phase 2
TSPX_ChMod7
channel mode for TC_26_6_13_8
BITSTRING[8]
Phase 2
TSPX_Maio24
Mobile allocation index offset hopping parameter for TC_26_6_13_8, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma24, default : 9
INTEGER
Phase 2
TSPX_Ma24
mobile allocation for TC_26_6_13_8, its value shall indicate number of frequencies between 1 and 17. default : '00E6E9'O
OCTETSTRING[3]
Phase 2
TSPX_Hsn24
hopping sequence number for TC_26_6_13_8, default : 7
INTEGER
Phase 2
TSPX_Maio25
Mobile allocation index offset hopping parameter for TC_26_6_13_8, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma25, default : 15
INTEGER
Phase 2
TSPX_Ma25
mobile allocation for TC_26_6_13_8, its value shall indicate number of frequencies between 1 and 17. default : '01FFFB'O
OCTETSTRING[3]
Phase 2
TSPX_Chtp12
channel type of a non-existing channel in the Assignment Command for TC_26_6_13_8
BITSTRING[5]
Phase 2
TSPX_Maio26
Mobile allocation index offset hopping parameter for TC_26_6_13_8, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma26, default : 5
INTEGER
Phase 2
TSPX_Ma26
mobile allocation for TC_26_6_13_8, its value shall indicate number of frequencies between 1 and 16. default : '009168'O
OCTETSTRING[3]
Phase 2
TSPX_Hsn26
hopping sequence number for TC_26_6_13_8, default : 9
INTEGER
Phase 2
TSPX_Maio27
Mobile allocation index offset hopping parameter for TC_26_6_13_8, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma27, default : 1
INTEGER
Phase 2
TSPX_Ma27
mobile allocation for TC_26_6_13_8, its value shall indicate number of frequencies between 1 and 16. default : '004080'O
OCTETSTRING[3]
Phase 2
TSPX_Hsn27
hopping sequence number for TC_26_6_13_8, default : 38
INTEGER
Phase 2
TSPX_Chtp13
channel type for TC_26_6_13_9
BITSTRING[5]
Phase 2
TSPX_Tm3
Timer for TC_26_6_13_9, value between 60 ‑100
INTEGER
Phase 2
TSPX_Maio28
Mobile allocation index offset hopping parameter for TC_26_6_13_9, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma28, default : 10
INTEGER
Phase 2
TSPX_Ma28
mobile allocation for TC_26_6_13_9, its value shall indicate number of frequencies between 1 and 17. default : '00EE7A'O
OCTETSTRING[3]
Phase 2
TSPX_Hsn28
hopping sequence number for TC_26_6_13_9, default : 11
INTEGER
Phase 2
TSPX_Maio29
Mobile allocation index offset hopping parameter for TC_26_6_13_9, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma29, default : 6
INTEGER
Phase 2
TSPX_Ma29
mobile allocation for TC_26_6_13_9, its value shall indicate number of frequencies between 1 and 17. default : '00F070'O
OCTETSTRING[3]
Phase 2
TSPX_Chtp14
channel type for TC_26_6_13_10
BITSTRING[5]
Phase 2
TSPX_Maio30
Mobile allocation index offset hopping parameter for TC_26_6_13_10, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma30, default : 11
INTEGER
Phase 2
TSPX_Ma30
mobile allocation for TC_26_6_13_10, its value shall indicate number of frequencies between 1 and 17. default : '017F69'O
OCTETSTRING[3]
Phase 2
TSPX_Hsn30
hopping sequence number for TC_26_6_13_10, default : 62
INTEGER
Phase 2
TSPX_Maio31
Mobile allocation index offset hopping parameter for TC_26_6_13_10, its value between 0 and (the number of frequencies) ‑1, which is defined in TSPX_Ma31, default : 1
INTEGER
Phase 2
TSPX_Ma31
mobile allocation for TC_26_6_13_10, its value shall indicate number of frequencies between 1 and 17. default : '000101'O
OCTETSTRING[3]
Phase 2
TSPX_MOBscSvcA
any supported MO basic service
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MOBscSvcB
any supported MO basic service
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MOBscSvcC
any supported MO basic service
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MOBscSvcD
any supported MO basic service
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MOBscSvcE
any supported MO basic service
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MOBscSvcF
any supported MO basic service
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MOBscSvcG
any supported MO basic service
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MOBscSvcH
any supported MO basic service
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MOBscSvcI
any supported MO basic service
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MOBscSvcJ
any supported MO basic service
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MT_DualModSvc
any supported MT dual mode service
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MT_NonSptSvc
any not supported MT basic service
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MTBscSvcA
any supported MT basic service
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MTBscSvcB
any supported MT basic service
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MTBscSvcC
any supported MT basic service
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MTBscSvcD
any supported MT basic service
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MTBscSvcE
any supported MT basic service
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MTBscSvcF
any supported MT basic service
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MTBscSvcG
any supported MT basic service
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MTBscSvcH
any supported MT basic service
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MTBscSvcI
any supported MT basic service
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MTBscSvcJ
any supported MT basic service
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MTNIC_BscSvcA
any supported MT basic service without immediate connection
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MTNIC_BscSvcB
any supported MT basic service without immediate connection
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MTNIC_BscSvcC
any supported MT basic service without immediate connection
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MTNIC_BscSvcD
any supported MT basic service without immediate connection
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MTNIC_BscSvcE
any supported MT basic service without immediate connection
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MTNIC_BscSvcF
any supported MT basic service without immediate connection
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MTNIC_BscSvcG
any supported MT basic service without immediate connection
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MTNIC_BscSvcH
any supported MT basic service without immediate connection
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MTNIC_BscSvcI
any supported MT basic service without immediate connection
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MTNIC_BscSvcJ
any supported MT basic service without immediate connection
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_Telephony_Rate
channel rate for TS11 (telephony), default value : "F"
"F", "H"
Phase 2
TSPX_MOChRateA
channel rate for TSPX_MOBscSvcA, default value : "F"
"F", "H"
Phase 2
TSPX_MOChRateB
channel rate for TSPX_MOBscSvcB, default value : "F"
"F", "H"
Phase 2
TSPX_MOChRateC
channel rate for TSPX_MOBscSvcC, default value : "F"
"F", "H"
Phase 2
TSPX_MOChRateD
channel rate for TSPX_MOBscSvcD, default value : "F"
"F", "H"
Phase 2
TSPX_MOChRateE
channel rate for TSPX_MOBscSvcE, default value : "F"
"F", "H"
Phase 2
TSPX_MOChRateF
channel rate for TSPX_MOBscSvcF, default value : "F"
"F", "H"
Phase 2
TSPX_MOChRateG
channel rate for TSPX_MOBscSvcG, default value : "F"
"F", "H"
Phase 2
TSPX_MOChRateH
channel rate for TSPX_MOBscSvcH, default value : "F"
"F", "H"
Phase 2
TSPX_MOChRateI
channel rate for TSPX_MOBscSvcI, default value : "F"
"F", "H"
Phase 2
TSPX_MOChRateJ
channel rate for TSPX_MOBscSvcJ, default value : "F"
"F", "H"
Phase 2
TSPX_MTChRateA
channel rate for TSPX_MTBscSvcA, default value : "F"
"F", "H"
Phase 2
TSPX_MTChRateB
channel rate for TSPX_MTBscSvcB, default value : "F"
"F", "H"
Phase 2
TSPX_MTChRateC
channel rate for TSPX_MTBscSvcC, default value : "F"
"F", "H"
Phase 2
TSPX_MTChRateD
channel rate for TSPX_MTBscSvcD, default value : "F"
"F", "H"
Phase 2
TSPX_MTChRateE
channel rate for TSPX_MTBscSvcE, default value : "F"
"F", "H"
Phase 2
TSPX_MTChRateF
channel rate for TSPX_MTBscSvcF, default value : "F"
"F", "H"
Phase 2
TSPX_MTChRateG
channel rate for TSPX_MTBscSvcG, default value : "F"
"F", "H"
Phase 2
TSPX_MTChRateH
channel rate for TSPX_MTBscSvcH, default value : "F"
"F", "H"
Phase 2
TSPX_MTChRateI
channel rate for TSPX_MTBscSvcI, default value : "F"
"F", "H"
Phase 2
TSPX_MTChRateJ
channel rate for TSPX_MTBscSvcJ, default value : "F"
"F", "H"
Phase 2
TSPX_MTNIC_ChRateA
channel rate for TSPX_MTNIC_BscSvcA, default value : "F"
"F", "H"
Phase 2
TSPX_MTNIC_ChRateB
channel rate for TSPX_MTNIC_BscSvcB, default value : "F"
"F", "H"
Phase 2
TSPX_MTNIC_ChRateC
channel rate for TSPX_MTNIC_BscSvcC, default value : "F"
"F", "H"
Phase 2
TSPX_MTNIC_ChRateD
channel rate for TSPX_MTNIC_BscSvcD, default value : "F"
"F", "H"
Phase 2
TSPX_MTNIC_ChRateE
channel rate for TSPX_MTNIC_BscSvcE, default value : "F"
"F", "H"
Phase 2
TSPX_MTNIC_ChRateF
channel rate for TSPX_MTNIC_BscSvcF, default value : "F"
"F", "H"
Phase 2
TSPX_MTNIC_ChRateG
channel rate for TSPX_MTNIC_BscSvcG, default value : "F"
"F", "H"
Phase 2
TSPX_MTNIC_ChRateH
channel rate for TSPX_MTNIC_BscSvcH, default value : "F"
"F", "H"
Phase 2
TSPX_MTNIC_ChRateI
channel rate for TSPX_MTNIC_BscSvcI, default value : "F"
"F", "H"
Phase 2
TSPX_MTNIC_ChRateJ
channel rate for TSPX_MTNIC_BscSvcJ, default value : "F"
"F", "H"
Phase 2
TSPX_EmgCallRate
Rate for the basic service supported for MO emergency calls
"F", "H"
Phase 2
TSPX_MO_NonCallSS
any supported MO non-call releated supplementary service
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MO_BscSvc_SMS
any supported MO SMS calls
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MO_DualModSvc
any supported MO dual mode call
"C_Telephony", "C_EmgCallSRV", "C_AltSpchG3", "C_AutoG3", "C_300cda", "C_1200cda", "C_120075cda", "C_2400cda", "C_4800cda", "C_2400cds", "C_4800cds", "C_PAD300", "C_PAD1200", "C_PAD120075", "C_PAD2400", "C_PAD4800", "C_PAD9600", "C_Pkt2400", "C_Pkt4800", "C_Pkt9600", "C_AltSpchData", "C_SpchData"
Phase 2
TSPX_MO_DualModRate
Rate for the supported MO dual mode call in TSPX_MO_DualModSvc
"F", "H"
Phase 2
TSPX_Vcallref_Active1
VGCS/VBS call reference active
BITSTRING[27]
Group ID 1 on test SIM
R96
TSPX_Vcallref_Active2
VGCS/VBS call reference active
BITSTRING[27]
Group ID 4 on test SIM
R96
TSPX_Vcallref_Active3
VGCS/VBS call reference active
BITSTRING[27]
Group ID 20 on test SIM
R96
TSPX_Vcallref_Active4
VGCS/VBS call reference active
BITSTRING[27]
Group ID 30 on test SIM
R96
TSPX_Vcallref_Active5
VGCS/VBS call reference active
BITSTRING[27]
Group ID 50 on test SIM
R96
TSPX_Vcallref_NotActive
VGCS/VBS call reference non-active
BITSTRING[27]
Group ID 48 on test SIM
R96
Annex B (normative):
PCTR Proforma
Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that users of the present document may freely reproduce the PCTR proforma in this annex so that it can be used for its intended purposes and may further publish the completed PCTR.
PROTOCOL Conformance Test Report (PCTR)
Global System for Mobile Communication, GSM, User-Network Access
Layer 3 Signalling Functions
Test Candidate
Name :
SUT name
Model :
model
H/W version :
hw
S/W version :
sw
Serial No. :
serienr
Client
Name :
Street / No. :
Postal Code / City:
Country :
This Test Report shall not be reproduced except in full without the written permission of TEST LAB REFERENCE, and shall not be quoted out of context.
Annex C (normative): Layer 3 Abstract Test Suite
This ATS is a normative part of the present document. The graphic form (TTCN . GR) and machine processable (TTCN .MP) files of the ATS are referred to GSM 11.10-3, version 4.t.0
Annex D (normative): Enhanced Full Rate Abstract Test Suite
This ATS is a normative part of the present document. The graphic form (TTCN . GR) and machine processable (TTCN .MP) files of the ATS are referred to GSM 11.10-3, version 4.t.0.
Annex E (informative): Cell Selection Abstract Test Suite
This ATS is an informative part of the present document. The graphic form (TTCN .GR) and machine processable (TTCN .MP) files of the ATS are referred to GSM 11.10-3, version 4.t.0.
Annex F (informative): Dual band Abstract Test Suite
This ATS is an informative part of the present document. The graphic form (TTCN .GR) and machine processable (TTCN .MP) files of the ATS are referred to GSM 11.10-3, version 4.t.0.
Annex G (normative): RGSM Abstract Test Suite
This ATS has been produced using the Tree and Tabular Combined Notation (TTCN) according to ISO/IEC 9646‑3 [3].
The ATS was developed on a separate TTCN software tool and therefore the TTCN tables are not completely referenced in the contents table. The ATS itself contains a test suite overview part which provides additional information and references.
G.1 The TTCN Graphical form (TTCN.GR)
The TTCN.GR representation of the ATS is contained in an Adobe Portable Document Format™ file (rgsm‑500.PDF contained in archive en_30060703v090000o0.ZIP) which accompanies the present document (Part 3).
G.2 The TTCN Machine Processable form (TTCN.MP)
The TTCN.MP representation corresponding to the ATS for is contained in an ASCII file (rgsm‑500.mp contained in archive en_30060703v090000o0.ZIP) which accompanies the present document (Part 3).
Annex H (normative):
ASCI Abstract Test Suite
This ATS has been produced using the Tree and Tabular Combined Notation (TTCN) according to ISO/IEC 9646‑3 [3].
The ATS contains groups for VGCS/VBS, eMLPP, UUS and Follow Me services. The ATS was developed on a separate TTCN software tool and therefore the TTCN tables are not completely referenced in the contents table. The ATS itself contains a test suite overview part which provides additional information and references.
These ATS are conform to R96 specifications
H.1 The TTCN Graphical form (TTCN.GR)
The TTCN.GR representation of the ATS is contained in an Adobe Portable Document Format™ file (asci-900.PDF contained in archive en_30060703v090000o0.ZIP) which accompanies the present document (Part 3).
H.2 The TTCN Machine Processable form (TTCN.MP)
The TTCN.MP representation corresponding to the ATS for is contained in an ASCII file (asci‑900.mp, contained in archive en_30060703v090000o0.ZIP) which accompanies the present document (Part 3).
History
Document history
V9.0.0
June 2000 |
fed31ee936becb3fd670e1e6e2ae795e | 10.76 | 1 Scope | The purpose of this document is to describe the schedule of the standardisation process for the Noise Suppression feature for the Adaptive Multi Rate Codec and to define open issues that are still under discussion. It also lists the new standards and necessary amendments to the GSM/DCS phase 2+ specifications for the technical realisation of the function.
The new standards and Change Requests (CR) necessary for this feature are listed in clause 9. |
fed31ee936becb3fd670e1e6e2ae795e | 10.76 | 2 References | References may be made to:
a) specific versions of publications (identified by date of publication, edition number, version number, etc.), in which case, subsequent revisions to the referenced document do not apply; or
b) all versions up to and including the identified version (identified by "up to and including" before the version identity); or
c) all versions subsequent to and including the identified version (identified by "onwards" following the version identity); or
d) publications without mention of a specific version, in which case the latest version applies.
A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. |
fed31ee936becb3fd670e1e6e2ae795e | 10.76 | 2.1 Normative references | [1] GSM 02.76: " Digital cellular telecommunications system (Phase 2+); Noise Suppression for the AMR Codec; Service Description; Stage 1" |
fed31ee936becb3fd670e1e6e2ae795e | 10.76 | 2.2 Informative references | |
fed31ee936becb3fd670e1e6e2ae795e | 10.76 | 3 Definitions, symbols and abbreviations | |
fed31ee936becb3fd670e1e6e2ae795e | 10.76 | 3.1 Definitions | [TBD] |
fed31ee936becb3fd670e1e6e2ae795e | 10.76 | 3.2 Symbols | [TBD] |
fed31ee936becb3fd670e1e6e2ae795e | 10.76 | 3.3 Abbreviations | GSM abbreviations pertinent to this feature are contained within 02.76 [1]. The abbreviations used within other GSM standards documents will be included within GSM 01.04. |
fed31ee936becb3fd670e1e6e2ae795e | 10.76 | 4 General | |
fed31ee936becb3fd670e1e6e2ae795e | 10.76 | 4.1 Outline Description of the Feature | See Stage 1 [1] and [TBD] document(s) for a general description of the Adaptive Multi Rate (AMR) Codec Noise Suppression Feature.
In brief, this feature enhances the quality of GSM speech calls by suppressing, where appropriate, background noise in the input speech signal, if and only if the AMR codec is utilised in support of the call. |
fed31ee936becb3fd670e1e6e2ae795e | 10.76 | 4.2 Support of Specification Work | This document is a “living document” and is currently controlled by SMG11. Proposals for change shall be forwarded to SMG11 (editor direct contact details are on the last page) This document should always reflect the latest status of work.
Latest versions of the material are intended to be made available to interested parties within SMG. Specification and Change Request rapporteurs should ensure the latest versions of their material is made available for review and comment by the following mechanisms:
1. ETSI FTP Server (docboc.etsi.fr or docbox.etsi.org) in
/Tech-Org/smg/Document/smg11/smg11_amr_ns -
2. The draft specifications. (Once specifications are approved see /Tech‑Org/smg/Document/smg/specs/Phase2pl/
where all current approved specifications are maintained)
3. Email distribution list: SMG11-NS@LIST.ETSI.FR |
fed31ee936becb3fd670e1e6e2ae795e | 10.76 | 5 Requirements | See [1]. |
fed31ee936becb3fd670e1e6e2ae795e | 10.76 | 6 Functional Description | See [TBD]. |
fed31ee936becb3fd670e1e6e2ae795e | 10.76 | 7 Technical Realisation and Amendments | |
fed31ee936becb3fd670e1e6e2ae795e | 10.76 | 7.1 Documentation Structure Overview | This section to define the documentation by standardisation phase. [TBD]
Permanent documents used within the AMR Noise Suppression Selection Phase are listed below. These are available on the ETSI FTP site (see Section 4.2 for the address). The most recent SMG11 temporay document numbers are given..
Stage 1 Service Description 02.76 (TD353/99)
Design Constraints (TD369/99)
Selection Phase Deliverables (TD370/99)
Selection Rules (TD368/99)
Processing Functions for the Selection Tests (TD354/99)
Selection Test Plan (TD356/99)
The list of permanent documents for the Characterisation Phase is TBD. |
fed31ee936becb3fd670e1e6e2ae795e | 10.76 | 8 Approvals Timeframe | Annex 1 contains the project plan for this feature. The intention is to complete standardisation of this feature so that it becomes part of Release '99.
SMG plenary (SMG26) mandated SMG11 to study the standardisation of an optional Noise Suppression function for the AMR codec.
It is envisaged that standardisation will involve the generation of a new standard and (possibly) the generation of CRs to existing GSM specifications. |
fed31ee936becb3fd670e1e6e2ae795e | 10.76 | 8.1 Approvals within STCs | SMG11 Approval of Draft Stage 1 Specification at SMG11 #11 (7-11 June 1999)
SMG1 Presentation of Draft Stage 1 Specification for information, Q3 1999
Presentation of further specifications and allied information [TBD] |
fed31ee936becb3fd670e1e6e2ae795e | 10.76 | 9 Specifications for Noise Suppression for the AMR Codec | |
fed31ee936becb3fd670e1e6e2ae795e | 10.76 | 9.1 New Specifications | Not Complete!
New specifications
GSM No.
02.76
Title
Noise Suppression for the AMR Codec; Service Description; Stage 1
Prime rsp STC
SMG11
2ndary rsp STC(s)
SMG1
Presented for info at SMG"
#28
Approved at SMG"
Comments
GSM No.
Title:
Prime rsp. STC:
2ndary rsp. STC(s):
presented for information at SMG#
approved at SMG#
Comments |
fed31ee936becb3fd670e1e6e2ae795e | 10.76 | 9.2 Change Requests to Existing Specifications | [TBD] |
fed31ee936becb3fd670e1e6e2ae795e | 10.76 | 10 Backwards Compatibility | The additions and changes caused by the work item covering Noise Suppression for the AMR Codec shall not cause backward compatibility problems with GSM phase 2 or phase 2+ equipment.
Annex 1 Project Plan (Draft)
•
•
PHASE, TASK or DEADLINE
PROVISIONAL DATE
Declaration of intention to submit a candidate
CLOSED
Agree Test Methodology or methodologies
SMG11 #9 - COMPLETED
Access to AMR C code
SMG#28 - COMPLETED
Finalise Design Constraints
Before the start of SMG11#10 - COMPLETED
Final Estimate of total cost
SMG11#11 - COMPLETED
Formal commitment to propose a candidate
During SMG11 #11 - COMPLETED
Requirements set and...
- approved by SMGll
- approved by SMG
SMG11 #11 - COMPLETED
SMG #29 - COMPLETED
Final commitment from proponents to provide funding
SMG#29 - COMPLETED
Final List of experimental conditions
Joint SQ/AMR-NS Meeting 27-29 July
Freeze Selection Rules
August 10th (with possible exception re. new proposals for using subjective SNR improvement measures - deadline August 15th)
Host, Listening, and Noise labs Identified.
Associated contracts finalised
August 20th
Host labs have access to material (speech and noise)
August 20th
Freeze Test Plan
September 3rd
Host Labs complete pre-processing of material
September 10th
ETSI receive candidates' executables
September 10th
Candidates send required cross checking data to cross-checking organisation (so that it is received no later than 3 days later)
October 1st
Candidates send processed material to host labs (so that it is received no later than 3 days later)
October 8th
Host Labs send 1st set of material to test houses (so that it is received no later than 3 days later)
October 15th
Host Labs send final set of material to test houses (so that it is received no later than 3 days later)
October 22nd
ETSI receives all remaining deliverables from candidates
November 15th
Run selection test
Results on reflector on December 3rd
Select a solution
• approved by SMG11
• approved by SMG
SMG11 (December 6-10)
SMG#31 (February 14-168)
Optimisation
Schedule and scope Tto be decided
Verification
Schedule and scope Tto be decided
Final drafting of standard and CRs
Schedule and scope Tto be decided
Approval of standards and CRs
• SMG11
• SMG
SMG11 (24-28 January)
SMG#30 (February 14-168)
Characterisation Testing
Scehdule and scope Tto be decided (and is subject to the availability of funding)
History
Document history
V0.0.1
August 1998
First Draft
V.o.o.2
January 1999
2nd Draft
V.0.0.3
January 1999
3rd Draft with updated work plan
V.0.0.4
February 1999
4th Draft with updated work plan
V.0.0.5
March 1999
5th Draft with updated work plan
V.0.0.6
April 1999
Editorial changes
V0.0.7
June 1999
Updated work plan and associated dates
V0.0.8
August 1999
Updated work plan and associated dates
Editor:
Steve Aftelak
Motorola
Tel: +44 1793 566261
Fax: +44 1793 566225
Email: aftelaks@ecid.cig.mot.com |
98cec70948a9ed6e47800b36dc5c104a | 11.18 | 1 Scope | The present document defines the aspects of the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface which are based on 1.8V technology to be used in the Mobile Station (MS). It specifies the electrical and logical requirements necessary for the operation of the 1.8V SIM - ME interface where it differs from GSM 11.11 [1]. For all aspects of the SIM - ME interface which are not covered by the present document, GSM 11.11 [1] applies. |
98cec70948a9ed6e47800b36dc5c104a | 11.18 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number.
• For this Release 1998 document, references to GSM documents are for Release 1998 versions (version 7.x.y).
[1] GSM 11.11: "Digital cellular telecommunications system (Phase 2+); Specification of the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface".
[2] GSM 11.12 (ETS 300 641): "Digital cellular telecommunications system (Phase 2); Specification of the 3V Subscriber Identity Module - Mobile Equipment (SIM - ME) interface". |
98cec70948a9ed6e47800b36dc5c104a | 11.18 | 3 Definitions, abbreviations and symbols | |
98cec70948a9ed6e47800b36dc5c104a | 11.18 | 3.1 Definitions | For the purposes of the present document, the following definitions apply.
1.8V technology SIM: A SIM operating at 1.8V ± 10% and 3V ± 10%.
1.8V technology ME: An ME operating the SIM - ME interface at 1.8V ± 10% according to the present document and 3V ± 10% according to GSM 11.12 [2].
1.8V only ME: An ME only operating the SIM - ME interface at 1.8V ± 10% according to the present document. |
98cec70948a9ed6e47800b36dc5c104a | 11.18 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply:
ATR Answer To Reset
CLK Clock
IC Integrated Circuit
I/O Input/Output
ME Mobile Equipment
MS Mobile Station
RST Reset
SIM Subscriber Identity Module |
98cec70948a9ed6e47800b36dc5c104a | 11.18 | 3.3 Symbols | For the purposes of the present document, the following symbols apply.
tF fall time
tR rise time
VIH Input Voltage (high)
VIL Input Voltage (low)
VOH Output Voltage (high)
VOL Output Voltage (low) |
98cec70948a9ed6e47800b36dc5c104a | 11.18 | 4 1.8V technology | |
98cec70948a9ed6e47800b36dc5c104a | 11.18 | 4.1 1.8V technology SIM | The SIM shall operate on both 3V ± 10% according to GSM 11.12 [2], and on 1.8V ± 10% according to the present document. If the ME supplies 3V to the SIM, both the ME and the SIM shall operate according to GSM 11.12 (ETS 300 641) [2]. The logical operation of the 1.8V technology SIM shall be as defined in GSM 11.11 [1]. The 1.8V technology SIM shall not give an ATR if operated at a supply voltage of 1.4V or below.
A 1.8V technology SIM may operate at 5V. If the 1.8V technology SIM operates at 5V it shall meet the electrical specifications as defined in GSM 11.11 [1].
Clock stop mode shall be supported by the SIM. The SIM shall indicate "Clock Stop Allowed" in the file characteristics of the status information as specified in GSM 11.11 [1]. |
98cec70948a9ed6e47800b36dc5c104a | 11.18 | 4.2 1.8V technology impact | When supplied with the supply voltage as specified in the present document the SIM shall be operated with a clock frequency of 1 to 4 MHz. |
98cec70948a9ed6e47800b36dc5c104a | 11.18 | 4.3 1.8V technology SIM Identification | The 1.8V technology SIM shall contain an identification. The identification is coded on bits 5-7 in byte 14 of the status information as follows:
Table 0: SIM Supply Voltage Indication
SIM Supply Voltage
Bit 7
Bit 6
Bit 5
5V only SIM
0 (RFU) 1
0 (RFU) 1
0 (RFU) 1
3V Technology SIM
0 (RFU) 1
0 (RFU) 1
1
1.8V Technology SIM
0 (RFU) 1
1
1
Future Class
1
1
1
NOTE 1 The bits marked (RFU) are set to ‘0’ and reserved for future use in the SIMs. The coding schemes relies on the fact that RFU bits are set to ‘0’.
The procedure for deriving the identification bit shall be performed by the ME immediately after the Answer To Reset (ATR) and before issuing any other command. The procedure consists of the two commands "SELECT GSM" and "STATUS/GET RESPONSE" |
98cec70948a9ed6e47800b36dc5c104a | 11.18 | 4.4 1.8V technology ME | The 1.8V technology ME shall initially activate the SIM with 1.8V according to this specification.
If the ME detects a 1.8V technology SIM, the ME may operate the SIM at 1.8V according to this specification. If the ME detects a 3V SIM, the ME shall switch to 3V operation as defined in GSM 11.12 [2] using the procedure as defined in subclause 4.7. If switching is performed, it shall take place before issuing any further commands as defined in paragraph 4.3.
If a faulty ATR is received at 1.8V, the ME shall initiate the error handling procedure described in GSM 11.11 [1] with the supply voltage remaining at 1.8V. If the error handling does not result in an errorless ATR, the ME shall activate the SIM at 3V. Activation at 3V shall be performed in accordance with GSM 11.12 [2].
If no ATR is received at 1.8V, the ME shall deactivate the SIM and activate it at 3V according to GSM 11.12 [2]. If a correct ATR is not received at 3V or the ME detects a 5V only SIM the ME shall reject the SIM without issuing any further commands.
If a 1.8V technology ME detects a SIM that indicates a future class the ME shall not activate that SIM at 3V. |
98cec70948a9ed6e47800b36dc5c104a | 11.18 | 4.5 1.8V Only ME | The 1.8V only ME activates the SIM at 1.8V.
If the ME is able to detect a 3V technology SIM according to the procedure in subclause 4.3, or if the procedure cannot be completed, the ME shall deactivate and reject the SIM immediately (maximum of 5s) without issuing any further command.
If an ATR is corrupted or not received by the ME, error handling according to sub clause 5.10 of GSM 11.11 [1] shall apply. |
98cec70948a9ed6e47800b36dc5c104a | 11.18 | 4.6 Activation and deactivation | The ME shall connect, activate and deactivate the SIM in accordance with the operating procedures specified in GSM 11.11 [1] taking into account the electrical characteristics specified in clause 5 of the present document. In particular, Vcc is powered when it has a value between 1,62 V and 1,98 V. |
98cec70948a9ed6e47800b36dc5c104a | 11.18 | 4.7 Supply voltage switching | MEs supporting both 1,8V and 3V operation may switch between the two supply voltages. Switching shall always be performed by deactivating the SIM and activating it at the new supply voltage. Activation and deactivation of the SIM with 3V shall be according to GSM 11.12 [2], whereas activation and deactivation of the SIM with 1,8V shall be according to the present document. |
98cec70948a9ed6e47800b36dc5c104a | 11.18 | 4.8 Cross compatibility | Cross compatibility means that the ME supports 1,8V and 3V operation. This is, however, optional for the ME. In case of the 1,8V technology ME, cross compatibility is provided, whereas, a 1,8V only ME requires a 1,8V technology SIM for operation. However, the 1,8V technology SIM (see definitions and subclause 4.1) ensures cross compatibility. |
98cec70948a9ed6e47800b36dc5c104a | 11.18 | 5 Electrical specifications of the SIM - ME interface | The electrical specification given in the present document covers the supply voltage range from 1,62V to 1,98V. The supply voltage range from 2,7V to 3,3V is specified in GSM 11.12 [2]. For each state (VOH, VIH, VIL and VOL) a positive current is defined as flowing out of the entity (ME or SIM) in that state. Vpp is not supported by the 1,8V technology ME or the 1,8V technology SIM.
When the SIM is in idle state the current consumption of the card shall not exceed 200 µA at 1 MHz at +25°C. When the SIM is in clock stop mode the current consumption shall not exceed 100 µA at +25 °C.
The ME shall source the maximum current as defined in table 4. It shall also be able to counteract spikes in the current consumption of the card up to a maximum charge of 12 nAs with no more than 400 ns duration and an amplitude of at most 60 mA, ensuring that the supply voltage stays in the specified range.
The clock duty cycle shall be between 40 % and 60 % of the period during stable operation. A clock cycle is defined at 50% of Vcc from rising to rising edge or falling to falling edge. When switching clock frequencies MEs shall ensure that no pulse is shorter than 100 ns which is 40 % of the shortest allowed period.
The ME need not provide contact C6 (Vpp). Contact C6 shall not be connected in the ME if provided.
Table 1: Electrical characteristics of I/O under normal operating conditions
Symbol
Conditions
Minimum
Maximum
Unit
VIH
IIHmax = ± 20 µA (Note 2)
0,7 x Vcc
Vcc+0,3
V
VIL
IILmax = + 1 mA
- 0,3
0,2 x Vcc
V
VOH (Note 1)
IOHmax = + 20 µA
0,7 x Vcc
Vcc (Note 3)
V
VOL
IOLmax = - 1mA
0 (Note 3)
0,3
V
tR tF
Cin = Cout = 30 pF
1
µs
NOTE 1: It is assumed that a pull-up resistor is used on the interface device (recommended value: 20 k ).
NOTE 2: During static conditions (idle state) only the positive value can apply. Under dynamic operating conditions (transmissions) short term voltage spikes on the I/O line may cause a current reversal.
NOTE 3: To allow for overshoot the voltage on I/O shall remain between -0,3V and Vcc+0,3V during dynamic operation.
Table 2: Electrical characteristics of Clock (CLK) under normal operating conditions
Symbol
Conditions
Minimum
Maximum
Unit
VOH
IOHmax = + 20 µA
0,7 x Vcc
Vcc (Note )
V
VOL
IOLmax = - 20 µA
0 (Note )
0,2 x Vcc
V
tR tF
Cin = Cout = 30 pF
50
ns
NOTE: To allow for overshoot the voltage on CLK should remain between -0,3V and Vcc+0,3V during dynamic operations.
Table 3: Electrical characteristics of RESET (RST) under normal operating conditions
Symbol
Conditions
Minimum
Maximum
Unit
VOH
IOHmax = + 20 µA
0,8 x Vcc
Vcc (Note)
V
VOL
IOLmax = -200 µA
0 (Note)
0,2 x Vcc
V
tR tF
Cin = Cout = 30 pF
400
µs
NOTE: To allow for overshoot the voltage on RST should remain between -0,3V and Vcc +0,3V during dynamic operations.
Table 4: Electrical characteristics of Vcc under normal operating conditions
Symbol
Minimum
Maximum
Unit
Vcc
1,62
1,98
V
Icc
4 (Note)
mA
NOTE: The supply current at 1,8V refers to a clock frequency of 4 MHz.
Annex A (informative):
Change history
This annex lists all change requests approved for this document since the the present document was approved by ETSI SMG.
SMG#
SMG
tdoc
SMG9
tdoc
VERS
CR
RV
PH
CAT
SUBJECT
Resulting
Version
s28
P-99-180
98p188
2.0.0
R98
Approval of final draft by SMG
7.0.0
History
Document history
V7.0.1
July 1999
Publication |
71e1f5e836af6acf69f6cf1aeaf24ba6 | 11.10-2 | 1 Scope | The present document provides the Protocol Implementation Conformance Statement (PICS) proforma for Global System for Mobile Stations (MSs), operating in the 900 MHz and 1 800 MHz frequency band (GSM 900 and DCS 1 800) within the European digital cellular telecommunications system (Phase 2), in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646‑7 [3] and ETS 300 406 [1]. |
71e1f5e836af6acf69f6cf1aeaf24ba6 | 11.10-2 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] ETSI ETS 300 406 (January 1995): "Methods for testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology".
[2] (void)
[3] ISO/IEC 9646‑7 (1995): "Information technology - Open systems interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements".
[4] to [56] (void)
[57] 3GPP TS 51.010-2 version 4 (Release 4): "Mobile Station (MS) conformance specification; Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification". |
71e1f5e836af6acf69f6cf1aeaf24ba6 | 11.10-2 | 3 Definitions and abbreviations | (void) |
71e1f5e836af6acf69f6cf1aeaf24ba6 | 11.10-2 | 4 Requirements | The requirements of the present document are provided in 3GPP TS 51.010-2 [57].
Annex A (normative):
(void)
Annex B (informative):
Change history
ETSI Document history
December 1995
v4.14.0
Public Enquiry PE 97: 1995-12-04 to 1996-03-29
May 1996
v4.15.0
Vote V 103: 1996-05-20 to 1996-07-26
Change history
Date
TSG #
TSG Doc.
CR
Rev
Subject/Comment
Old
New
2001-08
GP-06
GP-011474
A047
Inclusion of pointer to the maintained specification.
Conversion to 3GPP TS format.
4.15.0
4.16.0 |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 1 Scope | The present document covers issues related to the evolution of the GSM platform towards UMTS with the overall goal of fulfilling the UMTS service requirements, the support of the UMTS role model, support of roaming and support of new functionality, signalling systems and interfaces. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number.
[1] ETSI TC-SMG UMTS TS 22-.001: "Services Principles"
[2] ETSI TC-SMG GSM TS 0323.002
[3] ETSI TC-SMG GSM TS 0323.060
[4] ETSI TC-SMG GSM 11.14
[5] ETSI TC-SMG GSM 30.01
[6] ETSI TC-SMG GSM TS 23.001.
[7] TG.3x6.
[8] UMTSYY.01, UE-UTRAN Radio Interface Protocol Architecture – Stage 2
[9] UMTSYY.03, Description of UE states and Procedures in Connected Mode |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 3 Definitions and abbreviations | |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 3.1 Definitions | Editors note : Reference to Definition document required.
For the purposes of the present document, the [following] terms and definitions [given in ... and the following] apply.
<defined term>: <definition>.
example: text used to clarify abstract rules by applying them literally. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply:
<ACRONYM> <Explanation> |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 4 UMTS Concepts | Section 8 contains concepts that are considered as stable within SMG12 and no further input is expected but it should also be noted that consensus could not be reached on their use within UMTS. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 4.1 Reduction of UMTS signalling | |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 4.1.1 GLR Concept | The benefits of the Gateway Location Register (GLR) are:
• reduction in signalling traffic between networks.
• potential enhancements to mobile terminated call handling |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 4.1.1.1 Overview of the GLR Concept | The GLR is a node between the VLR and the HLR, which may be used to optimise the handling of subscriber location data across network boundaries.
In Figure 1, the GLR interacts with HLRa and VLRb for roamers on Network B. The GLR is part of the roaming subscriber's Home Environment. When a subscriber to HLRa is roaming on Network B the GLR plays the role of an HLR towards VLRb and the role of a VLR towards HLRa. The GLR handles any location change between different VLR service areas in the visited network without involving HLRa.
Figure 1: GLR Overview
The sequence of events when the subscriber roams to network B is as follows:
• VLRb sends the registration message to HLRa via the GLR, (i.e. HLRa stores the GLR's SCCP address and the GLR stores VLRb's SCCP address).
• HLRa returns the subscriber profile data
• The subscriber profile is stored in the GLR and VLRb
As the roaming subscriber moves between VLRs in network B, then the GLR is updated, but no message is sent to HLRa, therefore the number of messages between Network A and Network B is reduced. The reduction in signalling traffic is a significant benefit when the two networks are far apart, e.g. between Europe and Japan. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 4.1.1.2 Applications of the GLR | In addition to reducing the amount of mobility related signalling between networks, the GLR's function might also be extended to other aspects. These include the following:
• Enhancements for mobile terminated call handling
• Support for the Virtual Home Environment of a roaming subscriber
• Reduction of CAMEL signalling traffic between the visited and home network
• Hiding local variations in signalling between networks
• Further study is needed on these issues |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 4.1.2 Super-Charger | The signalling load associated with subscriber roaming can be high when either the MSC/VLR areas are small or the subscriber travels significantly. The Super-Charger concept aims to optimise signalling associated with subscriber data management by retaining subscription data in previously visited VLRs, where possible.
The benefits of the Super-Charger concept are:
• Reduction of signalling traffic for subscribers located in the home PLMN,
• Reduction of signalling traffic between the visited PLMN and the home PLMN,
• No new network nodes are required,
• Applicable to a wide range of protocol used for the transfer of data. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 4.1.2.1 Overview of the Super-Charger Concept | The concept of the Super-Charged network is described with examples from GSM mobility management. However, Super-Charger can be applied to other scenarios and protocols. This is a further study.
Super-Charger retains subscriber data stored in VLRs after the subscriber has moved to a location area served by a different VLR. The HLR performs the insertion of subscriber data to the VLR serving the location area to which the subscriber has roamed. The subscriber data stored at previously visited VLRs shall not be maintained while the subscriber is located in a location area serviced by a different VLR.
When the subscriber moves to a location area served by a VLR that has retained the subscriber’s subscription data, the VLR shall indicate to the HLR whether subscriber data is required. If the VLR indicates that subscription data is not required but the user’s subscription data has changed the HLR shall send the new subscription data to the VLR. Figure x 2 shows an example message flow in a Super-Charged network.
To ensure data consistency for super-charged VLRs a sequence numbering method can be used. A sequence number is added to the subscriber data record. This sequence number is incremented whenever the subscriber data record is changed for any reason. The sequence number is sent to the VLR in ISD. For non-super-charged VLRs this can be ignored. For super-charged VLRs it is stored and returned to the HLR in subsequent UpdateLocation messages. The HLR can then compare this sequence number with the value currently stored in the HLR to determine if the cached data is still valid.
With the Super-Charger activated subscriber information is no longer deleted from the VLR database when a mobile station moves from the location area served by the VLR. This results in the continuous growth of the VLR database size. Consequently, a new VLR data management system is required so that the VLR can handle newly arrived mobile stations. Two options for subscriber data management systems are:
• subscriber data for subscribers that are not currently served by the VLR shall be deleted periodically using a VLR audit system and/or,
• subscriber data for subscribers that are not currently served by the VLR shall be deleted dynamically to make room for the newly arrived subscribers.
Figure 2: Example message flow in a Super-Charged network. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 4.1.3 Turbo Charger | The signalling load associated with subscriber roaming can be high when either the location areas are small or the subscriber travels significantly. The Turbo-Charger concept aims to optimise signalling associated with subscriber data management by assigning one MSC/VLR to perform the Call Control and Mobility Management functions while the subscriber remain attached or until signalling routes require further optimisation.
The benefits of the Turbo-Charger concept are:
• the substantial reduction in signalling traffic for subscribers located in the home PLMN,
• the substantial reduction in signalling traffic between the visited PLMN and the home PLMN,
• no new network nodes are required,
• applicable to a wide range of protocol used for the transfer of data.
The disadvantages of the turbo-charger concept are:
• Connections are required from the access network to be fully meshed to all MSCs in the turbo-charger area. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 4.1.3.1 Overview of the Turbo-Charger Concept | A Turbo-Charged network constitutes a network architecture designed to reduce mobility management costs and provide automatic load-sharing between MSC/VLRs.
The architectural philosophy is to equally divide the subscribers between the available MSC/VLRs, irrespective of their location. In the context of GSM, this could be achieved by placing a routing function (e.g. evolved STP) between the BSC and the pool of MSC/VLRs. The purpose of the routing function is to route A-interface messages to the MSC/VLR that is serving the mobile station. The solution requires the MS to store a discriminate that can be used to identify the serving MSC/VLR and for routing to be applied on this discriminate on the connection between the MSC/VLR and access network. A TMSI partitioning scheme could be utilised. This scheme allocates a sub-set of the TMSI range to each MSC/VLR, Figure 3. The A-interface messages are then routed to the right MSC based on the TMSI. This could be done by a routing function external to the access network implying no access network modification (see figure 3). If a TMSI partitioning scheme is used then new SIM cards are not required.
The temporary identity used for paging (TMSI) must be unique within all the MSCs in the turbocharger area. This implies that there must be a mechanism to ensure that this requirement is met for turbocharged MSCs (e.g. TMSI partitioning).
Two mechanism to provide load-sharing are envisaged, random load-sharing and dynamic load-sharing.
Random load-sharing requires the routing function to randomly assign a MSC/VLR to serve a particular mobile station when it first comes in to the network. Regardless of where the mobile is the same MSC/VLR will always serve it provided the mobile remains in the area served by all the turbocharged MSC/VLRs linked by the routing function.
In large metropolitan areas where subscribers are served by multiple MSC/VLRs, some MSC/VLRs may be very busy while others are not fully utilised. Dynamic load-sharing requires the implementation of an intelligent router. Since the routing function routes all A-interface traffic, it can participate in load-sharing and balancing based on the current loading of each MSC however linkage between MSC load and the routing algorithm would be required.
In the case of a Turbo-Charged network where the network is sub-divided into large regions, further optimisation can be achieved by adding the Super-Charger functionality.
Figure 3: Example of GSM Turbo-Charger Network Architecture
In the context of UMTS, the routing function becomes a feature of the RNC.
Figure 4: Example of UMTS Turbo-Charger Network Architecture |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 4.1.4 Relationship between GLR and TurboCharger | The GLR and TurboCharger are two independent schemes for reducing the amount of MAP traffic generated in UMTS networks.
• The GLR works by reducing traffic between PLMNs associated with Location Updates. This is achieved by "caching" the roaming subscriber's data in the visited network
• The TurboCharger works by eliminating the need to perform location updates. The same VLR can hold a subscriber's data for the duration of his attachment to the network.
A TurboCharged network requires that each MSC/VLR can physically connect to all RNCs. Therefore TurboCharging may be best suited to areas of the network characterised by dense geographic coverage. On the other hand, the GLR function is independent of the network density.
The network structure shows that the GLR and a TurboCharged area within the same PLMN are independent. In fact, it shows benefits from using the two techniques in the same network. The Turbo-Charger reduces the location registration signals between the MSC/VLR and GLR:
• There is no new update location signal between MSC/VLR and GLR if roamer moves inside of the Region A.
• There is no new update location signal between GLR and HLR if roamer moves between regions.
Figure 4bis. [editor's note: to be deleted] |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5 Key issues | {Editors note: These key issues have arisen from the scenario work, it is agreed within SA 2 that the focus should be on solving these key issues, Once these issues have become relatively stable, they are moved to 23.121 or removed from this document}. Study of these items is ongoing. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.1 Core network transport | • L1 and L2 technologies
• Signalling protocols
• How to use ATM?
• Nx64k transport |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.2 Core network layer 3 | 5.2.1 Common Communication Channel
A common communication channel (name to be defined) provides nodes of the Core Network the ability to reach every RNC of the UTRAN. This communication channel can be used for application like SMS cell broadcast or location services (LCS).
This communication mechanism would use e.g. an IP routing functionality of the 3G-SGSN. The according protocol stack is outlined in figure 5.
Figure 5: Protocol Stack of the Common Communication Channel
The placeholder Xx should be replaced by the according reference points of the applications e.g. Bc for cell broadcast.
The following issues until now are identified and have to be solved:
1. IP Routing functionality in the 3G-SGSN,
2. An appropriated layer 3 protocol has to be chosen (TCP or UDP) per application,
3. Addressing of the Application and Application node by the RNC(s),
4. Addressing (dynamic or static) of the application (e.g. CBC) on the RNC(s).
• L3 technologies
• GTP vs. IP-in-IP tunneling
In UMTS/GPRS, it should be possible for operators to use different packet switching protocol (e.g. ATM-SVC) under single GTP standard.
Between GSNs GTP uses UDP/IP (or TCP/IP) for addressing regardless whether IP routing or ATM-SVC switching is used. The use of ATM-SVC will not impact on GTP standardisation
User IP
GTP
UDP / TCP
IP Addressing of SGSN/GGSN
Operator’s selection ATM-SVC Routing capability
Figure 6 |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.3 Benefits of the Gs interface applied to UMTS | The Gs interface defined within GSM/GPRS provides a number of benefits to a GSM/GPRS operator [03.60]. These include: combined attach/detach procedures, combined location/routing area updates, paging of CS connection via the SGSN, identification procedures, MM information procedures. The main aims of these include saving of GSM/GPRS radio resources, harmonised security procedures and reduction of MS battery consumption.
As GSM operators roll out GPRS and as the numbers of mobiles increase the benefits of the Gs interface to the network operator will increase as the percentage of GPRS enabled mobiles grows. GSM/GPRS operators with mature networks will also be looking to roll out UMTS using evolved CN infrastructure, they will also be looking to apply the benefits of the Gs interface reaped for GSM to UMTS. Many of the capabilities of the Gs interface will be applicable to UMTS (such as combined updates, combined attach and MS/Ue information procedures), this will save on radio resource usage. The presence of the MSC-GSN interface will also offer the opportunity for developments to ease seamless service support between CS and PS platforms (such as SoLSA and Camel).
In the future, network operators who have incorporated Gs functionality into their networks will be looking to connect UTRAN to their GSM/GPRS Core Networks with minimal changes (excepting those for service development, network and radio optimisation, network evolution and flexibility), thus the Gs interface should be maintained and enhanced for UMTS.
The Gs interface also offers opportunities for suppliers and operators regarding integrated MSC/GSN products (which may support internal proprietary Gs functionality as well as standardised MSC-GSN functionality). Operator’s networks which have separated MSC/GSN nodes will be able to add integrated nodes into their GSM/GPRS/UMTS networks (and vice versa), depending upon the MM solutions developed for UMTS this could enable combined updates to be performed between (Gs supporting) integrated and separated nodes. If the Gs interface is not present operators will not be able to optimise resource between (integrated or separated) nodes. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.3.1 Periodic updates | |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.3.1.1 Why do we have Periodic updates | Periodic updates are within the network to increase the efficiency of the CN while also increasing the quality of service perceived by calling parties to mobiles. The periodic timer is set within the CN node to a figure which enables absent mobiles to have their (VLR based) information removed after the timer expires. People calling mobiles which are registered as ‘detached’ (either implicitly or via periodic expiry) will receive faster treatment of the call in the CFNRc case or ‘Not been possible to connect your call’ RANN case as the mobile is not paged by the network. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.3.1.2 Support of periodic updates in UMTS | One of the current proposals for SRNS relocation [1, incl.: section 9.3.4, 2] propose that when in CMM connected mode (PMM idle) or PMM connected (CMM idle) the relevant location/routing updates to the (idle) CN are performed while in RRC connected mode.
For periodic updates the UE may be RRC connected (know to the UTRAN as ‘active’) when the (UE based) periodic timer is due to expire, the (idle) CN node will also have a timer about to expire and be ready to detach the UE.
If the methodology of [1, Section 9.3.4] is followed a location update will be performed within the same RRC connection to the (MM idle state) CN node to re-set the periodic timer. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.3.1.3 Impact upon UMTS | The impact upon UMTS of this is that the UTRAN, UE and one CN node have an active session (‘xMM connected) in place with accurate knowledge of the (periodic) attached/detached status of the UE. It is a waste of (valuable) radio resource for the UE to perform a LA/RA update purely to reset the periodic timer in the (idle) CN node: this also contradicts working assumption [1, section 11].
As UMTS is envisaged as a mass market system supporting very large numbers of mobiles within the network, many of these could potentially have very long (i.e. all day) duration (but low packet volume) Packet sessions (as per GPRS). It is folly to consider additionally loading the radio resource to update the (periodic) detach status of the mobile on the CN side of the radio interface when elements on the CN side of the radio interface already know the status of the mobile. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.4 Authentication | |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.5 Management of ciphering keys | |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.5.1 Cipher Mode Control – 2MM concept | The assumptions in this section is based upon the assumption that ciphering in performed between UE and RNC.
It is assumed that in UMTS the ciphering key and the allowed ciphering algorithms are supplied by CN domains to the UTRAN usually in the beginning of the connection. Receipt of the ciphering command message at the UTRAN will cause the generation of a radio interface ciphering command message and, if applicable, invoke the encryption device and start data stream ciphering. The CN domain is noted if the ciphering is executed successfully in the radio interface and the selected ciphering algorithm.
When new connection is established from other CN domain, which is not having any connection to the UE, the new CN domain also supplies the ciphering key and the ciphering algorithms allowed to use to UTRAN in the beginning of the connection. This is due to the fact CN domains are independent from each other. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.5.1.1 One ciphering key used in UTRAN | If it is assumed that only one ciphering key and one ciphering algorithm are used for all connections, this leads to a situation, in which there are two ciphering keys supplied from CN domains and only one of them is used.
To handle this situation, UTRAN must select either one of the ciphering keys. If there are no differences between the ciphering requirements1 requested by two CN domains then, e.g., the first ciphering key and the algorithm is maintained (see Figure 3 7).
Figure 3Figure 7. One ciphering key use in the UTRAN
As a result of the selection of the ciphering key between two different CN domains (if both CN domains have active connection(s) to the UE) either one or both of the CN domains do not know the present ciphering key used for the connection(s). Only UTRAN and UE know the present ciphering key used.
Further, if the case described in figure 1 is still considered and if after the MSC connection is released, but before SGSN connection is released, a new connection from MSC is established, the MSC may initiate a new authentication resulting in a new MSC ciphering key supplied to UTRAN. In this case, the UTRAN may follow the same key selection approach as it used previously, i.e., the first ciphering key is maintained2. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.5.1.2 Multiple ciphering keys used in UTRAN | It may be required to use more than one ciphering key for different radio access bearer, e.g., user plane bearers associated to one CN domain are ciphered by the ciphering key supplied by the associated CN domain. However, in the control plane only one ciphering key is used and therefore in the control plane there must be co-ordination between ciphering keys supplied by CN domains.
The co-ordination in the control plane is similar to what is presented for one ciphering key used in UTRAN option (ch. 2.1). In the control plane, UTRAN must select either one of the ciphering keys supplied from CN domains if both CN domains are active. The change of the used ciphering key in the control plane during active RRC connection is for further study. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.5.1.3 Serving RNC relocation and ciphering | In GSM, when inter-BSC handover is performed, MSC sends the ciphering key and allowed algorithms to the target BSC in the BSSMAP HANDOVER REQUEST message. In GPRS, because the SGSN performs the ciphering, the inter-BSC handover does not cause any need for the ciphering key management.
For UMTS, the GSM approach is not applicable on the serving RNC (SRNC) relocation, because CN domains do not necessary know the present ciphering key(s) used as it is described in the chapter 2.
It is recommended that the ciphering key(s) or a relevant information indicating used ciphering key(s) is transferred in the transparent UTRAN information field from the source RNC to the target RNC in the RANAP SRNC RELOCATION REQUIRED and RANAP SRNC RELOCATION REQUEST messages (see Figure 48.). In this way the present ciphering key(s) is transferred to the target RNC.
Figure 4Figure 8. The ciphering key transfer in SRNC relocation procedure (one ciphering key) |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.5.2 UMTS-GSM handover | In the handover from UMTS to GSM, the ciphering key cannot be transferred transparently like it is proposed for UMTS. The CN has to build the BSSMAP HO REQUEST message, having the ciphering key from the MSC. 2G-SGSN receives its ciphering key from the old 3G-SGSN via Gn-interface as it is done in GPRS.
If the ciphering keys used in UMTS are different compared to GSM, e.g., the ciphering key length is different, both MSC and SGSN ciphering keys must be changed in UMTS-GSM handover. This type of interoperation is left for further study in this paper. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.5.3 Interworking with 2g-MSC | In GSM, the A-interface BSSMAP [2] supports a transparent field in the BSSMAP HO REQUIRED and HO REQUEST messages, which allows to utilise the proposed solution also for GSM CN connected to the UTRAN. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.