hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
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... |
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 ... |
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... |
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 Tes... |
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 fr... |
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.
• Fo... |
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 operati... |
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].... |
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 ... |
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 ... |
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 rece... |
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 SI... |
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) ens... |
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 no... |
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 rele... |
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.
• Fo... |
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... |
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.
• Fo... |
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 ... |
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 signall... |
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.
... |
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 differen... |
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 Manageme... |
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... |
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 elimi... |
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. a... |
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 sa... |
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.... |
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 UTR... |
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 (i... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.