hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 0 SIM is not present | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 1 SIM is present and accessible | Facility Response Parameter:
Facility selector
word
256: GSM Support
Function
word
54
Annex A (informative): GSM Supplementary Services Message flow
A.1 Restrict SS information
This Message Flow chart describes the flow for restriction of SS information.
Application MS Network
| facility_req(funct = 256) | ... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 1 Scope | The present document specifies the third version of the Integrated Services Digital Network (ISDN) - Global System for Mobile communications (GSM) Public Land Mobile Network (PLMN) signalling interface. The present document is applicable to the interconnection of PLMN and ISDN.
The ISUP interface defined is the trunk s... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 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.
• Fo... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply:
3PTY Three-Party
ACM Address Complete Message
AoC Advice of Charge
CB Call Barring
CCBS Completion of Calls to Busy Subscriber
CCNR Completion of Calls on No Reply
CD Call Deflection
CFB Call Forwarding Busy
CFNR Call Forwarding No Reply
CFNRc... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 4 General principles | The gateway exchanges in both networks behave like international incoming or outgoing gateways in the relevant cases as described in EN 300 356-1 [1] to EN 300 356-20 [19], with the exceptions indicated within the present document. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5 Exceptions and clarifications for basic call | |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.1 Formats and codes | The formats and codes specified in EN 300 356‑1 [1] with the exceptions and clarifications described in the table in annex D shall be applicable. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2 Basic call signalling procedures | The basic call procedures of EN 300 356-1 [1] apply with the following exceptions and clarifications. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.1 Signalling procedures for connection type allowing fallback | The gateway in the preceding network (PLMN or ISDN) shall perform fallback according to the procedures defined in EN 300 356-1 [1] when the succeeding network does not support fallback. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.2 Echo control procedure | The enhanced echo control procedure according to EN 300 356-1 [1] is not supported. Instead the simple echo control procedure described in EN 300 356-1 [1] is applicable.
According to GSM 03.50 [21], for speech and 3,1 kHz audio connection types an acoustic echo control shall be provided in the MS. The PLMN may provide... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.3 Calls from the PLMN to the fixed network | |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.3.1 Gateway in the PLMN | The Initial Address Message (IAM) sent by the gateway in the PLMN shall be coded taking into account the following exceptions and clarifications. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.3.1.1 Initial address message | Called party number
The called party number parameter may contain a Mobile Station Roaming Number (MSRN).
- Internal network number indicator:
0 if the MSRN is included;
1 otherwise.
The use of the internal network number indicator is an option.
User service information
The IAM shall always include a user service infor... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.4 Calls from the fixed network to the PLMN | |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.4.1 Gateway in the fixed network | |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.4.1.1 Initial address message | Called party number
The called party number parameter contains the MSISDN or MSRN:
- Internal network number indicator:
0 if MSRN is included;
1 if MSISDN is included.
NOTE: The value of the internal network number indicator is set in the exchange having the relevant knowledge, and is passed transparently through the f... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.4.2 Gateway in the PLMN | |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.4.2.1 Address complete message | Significant delays may be incurred while interrogating location registers and while paging the terminating MS.
Due to the possible delays involved in setting up mobile calls, the PLMN needs to take special action to ensure that timer T7 (awaiting address complete timer) does not expire.
For this reason, whenever a call... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6 Exceptions and clarifications for supplementary services | Supplementary services are used according to EN 300 356‑1 [1] to EN 300 356‑20 [19]. When considering supplementary services, there exists a symmetry about this interface although the ISDN services may not be the same as the PLMN services. For each service supported by EN 300 356‑2 [2] to EN 300 356‑20 [19] or GSM 03.8... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1 Considerations on ISDN supplementary services | |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1 Handling of number parameters related to supplementary services | The following text applies when referenced for the appropriate parameters.
Number parameters related to supplementary services sent across the ISDN-PLMN interface shall have the following coding of the nature of address indicator.
National significant number (000 0011) shall be used in the following cases:
- for a numb... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.1 Calling Line Identification Presentation/Restriction (CLIP/CLIR) supplementary services | EN 300 356‑3 [3] and EN 300 356‑4 [4] apply with the exceptions below:
Calling party number and generic number
Handling of calling party number and the appropriate generic number shall be made according to subclause 6.1.1.
For mobile originated calls the calling line identity is mapped into the calling party number par... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.2 Connected Line Identification Presentation/Restriction (COLP/COLR) supplementary services | EN 300 356‑5 [5] and EN 300 356‑6 [6] apply with the exceptions below:
Connected number and generic number
Handling of connected number and the appropriate generic number shall be made according to subclause 6.1.1. For mobile terminated calls the connected line identity is to be mapped into the connected number paramet... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.3 Terminal Portability (TP) supplementary service | EN 300 356‑7 [7] applies.
NOTE: Terminal Portability is supported by the protocol, however the service is not provided for the GSM access. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.4 User-to-User Signalling (UUS) supplementary service | EN 300 356‑8 [8] applies.
NOTE: The maximum length of the user-user parameter of the setup message at the GSM access is restricted to 35 octets. When a GSM PLMN receives a longer user-to-user information element in the IAM message the User-to-user information element will be discarded without indication. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.5 Closed User Group (CUG) supplementary service | EN 300 356‑9 [9] applies. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.6 Subaddressing (SUB) supplementary service | EN 300 356‑10 [10] applies. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.7 Malicious Call Identification (MCID) supplementary service | EN 300 356‑11 [11] applies with the exceptions below:
Calling party number and generic number
Handling of calling party number and the appropriate generic number shall be made according to subclause 6.1.1.
NOTE: Malicious Call Identification is supported by the protocol, however the service is not provided for the GSM ... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.8 Conference call, add-on (CONF) supplementary service | EN 300 356‑12 [12] applies with the exception below:
Notification messages may be sent from the ISDN to the PLMN according to GSM 03.84 [23].
NOTE: Conference call is supported by the protocol, however the service is not provided for the GSM access. The corresponding service in GSM is the multiparty service defined by ... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.9 Explicit Call Transfer (ECT) supplementary service | EN 300 356‑14 [13] applies with the exceptions below:
Call Transfer Number
Handling of call transfer number shall be made according to subclause 6.1.1. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.10 Diversion supplementary services (Call Forwarding Unconditional (CFU)/Call Forwarding on Busy (CFB)/Call Forwarding on No Reply (CFNR)/Call Deflection (CD)) | EN 300 356‑15 [14] applies with the exceptions below:
Original called number, redirecting number and redirection number
Handling of original called number, redirecting number and redirection number shall be made according to subclause 6.1.1. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.11 Call Hold (HOLD) supplementary service | EN 300 356‑16 [15] applies. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.12 Call Waiting (CW) supplementary service | EN 300 356‑17 [16] applies. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.13 Completion of Calls to Busy Subscriber (CCBS) supplementary service | EN 300 356‑18 [17] applies with the exception below:
If the GMSC has the knowledge that the CCBS service is not supported the diagnostics in the Release message will be set to indicate "CCBS not possible" (for cause values 17 or 34). |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.14 Completion of Calls on No Reply (CCNR) supplementary service | EN 300 356‑20 [19] applies with the exception below:
NOTE: Completion of Calls on No Reply is supported by the protocol, however the service is not provided for the GSM access. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.15 Three party (3PTY) supplementary service | EN 300 356‑19 [18] applies with the exceptions below:
Notification messages may be sent from the ISDN to the PLMN according to GSM 03.84 [23].
NOTE: Three party is supported by the protocol, however the service is not provided for the GSM access. The 3PTY service can be a part of the multiparty service as defined by th... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.2 Considerations on GSM unique supplementary services | |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.2.1 Call Forwarding on Mobile Subscriber Not Reachable (CFNRc) supplementary service | EN 300 356‑15 [14] applies with the exceptions below:
Original Called Number, Redirecting Number and Redirection Number
Handling of original called number, redirecting number and redirection number shall be made according to subclause 6.1.1. For calls that have been redirected (because of mobile subscriber not reachabl... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.2.2 Advice of Charge (AoC) supplementary service | No impact on the ISDN-PLMN- interface. The service is described in GSM 03.86 [24]. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.2.3 Call Barring (CB) supplementary service | No impact on the ISDN-PLMN interface. The service is described in GSM 03.88 [25]. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.2.4 Unstructured Supplementary Service Data (USSD) | No impact on the ISDN-PLMN interface. The service is described in GSM 03.90 [26]. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.2.5 Calling Name Presentation supplementary service (CNAP) | No impact on the ISDN-PLMN interface. The service is described in GSM 03.96 [33]. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.2.6 Multiple Subscriber Profile (MSP) supplementary service | No impact on the ISDN-PLMN interface. The service is described in GSM 02.97 [34]. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.2.7 Multi Party (MPTY) supplementary service | The service is described in ETS 300 545 [26].
Notification messages of the MPTY supplementary service may be mapped on the ISDN-PLMN interface into notification messages of the ISDN Conference call (CONF) supplementary service defined in EN 300 356-12 [12]. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 7 Message Transfer Part (MTP) protocol requirements | The Message Transfer Part (MTP) protocol shall conform to the requirements in ETS 300 008 [31] with the appropriate value for the Network Indicator (NI).
It is preferred that NI value 10 (national network) is used within GSM networks as in the fixed national network. Based on national agreement, any NI value may be app... |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 1 Scope | The purpose of this document is to describe the project plan for the Mobile Station Execution Environment (MEXE) work item standardisation.
This document is a ‘living document’ and permanently updated by PT SMG. Proposals for change shall be forwarded to PT SMG, where the latest version can be obtained any time. The ME... |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 1.1 References | |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 1.2 Abbreviations | MNCRS WG4 Mobile Network Computer Reference Standard Working Group 4 |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 2 General Considerations for MEXE | |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 2.1 Support tools for specification work | ETSI FTP Server (docboc.etsi.fr or docbox.etsi.org):
SMG4 /../SMG/SMG4/WI_mexe .
Email distribution list: SMG4_mexe@list.etsi.fr (Subscription for contributors from SMG1, SMG4, SMG9 and SMG10, instructions on how to subscribe in Tdoc SMG4 97p488) |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 2.2 Decisions at SMG | Workitem Rapporteur
John Candish (NORTEL); email: jfc@nortel.com |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 2.2.1 SMG#22 | SMG#22 agreed to establish a small project team that elaborated a workitem description backed by a feasibility study on mobile station application execution environment. |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 2.2.2 SMG#23 | SMG#23 agreed the workitem description and the feasibility study conditionally. The condition is that the relationship between the SMG work and the WAP consortium can be clarified before WAP is taken into account. |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 2.2.3 SMG#24 (bis) | SMG4 is mandated to communicate directly to MNCRS and WAP, provided that the WAP consortium is open for new members. A LS had been sent to WAP from SMG#24bis, although some concerns were expressed afterwards. |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 2.2.4 SMG#25 | It was noted that preceding SMG's had agreed co-operation with WAP under condition of open participation rights for interested parties.
SMG#25 asked SMG4 to organise a technical review meeting of the WAP papers. which was convened as a MExE Workshop on 27-28 April in Sophia Antipolis hosted by ETSI. |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 3 Co-operation with other groups | |
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 full... |
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.e... |
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 ... |
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, embedd... |
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 evolvab... |
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 gro... |
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 woul... |
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 ( ... |
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.
• Fo... |
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].
Po... |
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 Stand... |
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 gro... |
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 ... |
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).
Fi... |
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 ... |
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 t... |
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" befor... |
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 s... |
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 ... |
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 Des... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.