hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
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... |
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 t... |
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 dif... |
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... |
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 ... |
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... |
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. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.6 Mobile IP in UMTS | |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.6.1 Mobile IP | A single generic mobility handling mechanism that allows roaming between all types of access networks would allow the user to conveniently move between fixed and mobile networks, between public and private as well as between PLMN’s with different access technologies. The ongoing work in IETF Mobile IP working group [MI... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.6.2 A staged introduction of Mobile IP in the UMTS CN | Three steps, which are discussed more in detail further down, have been identified. Briefly, these are:
1. 1. Step 1 represents a minimum configuration for an operator, who wishes to offer the mobile IP service. The current GPRS structure is kept and handles the mobility within the PLMN, while MIP allows user to roam b... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.6.2.1 Step 1 – Offering Mobile IP service | Mobile IP has the benefit of being access system independent, which allows users to roam from one environment to another, between fixed and mobile, between public and private as well as between different public systems. Assuming a minimal impact on the GPRS standard and on networks whose operators do not wish to suppo... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.6.2.2 Step 2 – Intermediate GPRS-Mobile IP system | One way to implement a GPRS backbone is to co-locate the SGSN and GGSN, as depicted in Figure 6 10 . This might be favourable for operators with a strong interest in utilising standard IP (IETF) networks as far as possible and does not require any changes in the current GPRS protocol architecture.
In step 1, the assump... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.6.2.3 Step 3 – Using Mobile IP for Intra System Mobility | The third and last step is to let Mobile IP handle all intra system mobility, including all handovers between GGSN’s or IGSN’s. This is depicted in Figure 711, where the IGSN represents an integrated SGSN/GGSN. The Gn and Gp interfaces may optionally be kept to handle roaming customers, whose terminals do not support M... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.6.3 Roaming | Depending on the capabilities of a visited network, two roaming schemes can be identified; GPRS roaming and MIP roaming. With GPRS roaming, we mean roaming via the Gp interface and the use of a GGSN in the home network, which is necessary when the visited network does not offer any FA’s. In those cases where the visite... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.7 Iu reference point | |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.7.1 General | As a first step, UMTS will be based on the GSM/GPRS network, i.e. one circuit switched and one packet oriented domain. Due to the differences of the domains, the Iu reference point will be realised by two Iu instances, one for each domain. This enables each domain to develop according to their specific characteristics.... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.7.3 Iu reference point – User plane towards IP domain | • Any problems within the UTRAN which cause loss of data addressed to a UE shall be indicated to the 3G-SGSN to maintain the conformance of the data volume counted by the 3G-SGSN with the successfully transferred data volume. It is FFS whether this mechanism provides a degree of conformance required for volume dependen... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.8 Dualmode operation (GSM/UMTS) | |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.8.1 Will dualmode terminals also support GPRS? | |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.8.1.1 Handovers between GSM/GPRS class A and UMTS terminals | In the following some problems and suggestions to solve the problems are made concerning the case where UMTS must support handovers from GSM to UMTS and/or UMTS to GSM for mobile stations with CS and PS service capability (GPRS class A). |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.8.1.2 Handover from GSM to UMTS | This type of handover could be needed, e.g., due to traffic reasons in a congested GSM network. In GSM the control for CS connection remains in the MSC from which the call was originated. This is called anchoring. Figure 8 12 illustrates the situation before the HO into UMTS (i.e., to UMTS UTRAN).
Figure 8Figure 12. Be... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.8.1.3 Handover from UMTS to GSM | Figure 10 14 illustrates the situation before the HO; anchoring is assumed in UMTS CN. This type of handover could be needed, e.g., due to limited coverage of UMTS.
Figure 10 Figure 14 Before HO from UMTS to GSM.
This type of handovers are seen as important especially in the first stages of UMTS due to limited covera... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.8.1.4 Suggestions | From the discussion above one can suggest that to support handovers between UMTS and GSM for class A type of mobiles:
4. UMTS MM must support some distinction between CS and PS services in the registration related procedures. An example is a dedicated update/cancel only to PS services in UMTS. This is likely to affect ... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.9 Anchor concept | UMTS Mobility Management (UMM) for release 99 shall use packet anchoring at the GGSN, providing this meets the QoS requirements, including those for real time services.
Disassociation of SRNS relocation and PS session transfer should be evaluated for release 99 |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.9.1 Introduction to the concept of anchoring communications in GPRS | GPRS is being developed to include Quality of Service, this includes real time aspects. At present within GSM/GPRS the Core Network part of inter SGSN RA update procedure- is used to maintain communications within the network for a change of SGSN. GPRS will need development to support real time QoS requirements, the... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.9.2.1 Requirements for the anchor SGSN | The requirements for the support of the SGSN anchor concept are discussed below
GPRS: With added QoS
To date GPRS has used a number of different QoS Criteria, however the GPRS (and UMTS) community have been looking at enhancing this to enable better support for real-time type features. The current Core Network GPRS in... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.9.2.2 Developments of GSM/GPRS for the SGSN based anchor | To enable the SGSN anchor concept to be supported the following developments will be needed to the contemporary GSM/GPRS network: these should be linked in to the overall UMTS developments:
a) Support for GPRS/UMTS QoS during SGSN change (inter SGSN RA update). Modification of the contemporary inter SGSN RA update mec... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.9.3 The non-Anchor SGSN concept | The non-anchor SGSN concept may be viewed as the method currently used within GPRS (R97) for a change of SGSN. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.9.3.1 Current GPRS operation | Current GPRS does not use an anchor SGSN (the SGSN used at PDP context activation may not be used by the MS during the lifetime of this PDP context).
The main reason is that, while in Circuit Switched GSM the call duration is very short, the PDP context duration may be very long (and the user be very far away from the ... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.9.3.2 Developments of GSM/GPRS for the non-SGSN based anchor | To satisfy the identified requirements for GSM/GPRS/UMTS R99, the following developments will be needed to the contemporary GSM/GPRS network:
a) Support for GPRS/UMTS QoS mechanisms during inter SGSN RA update, this will involve continued linkage of the GGSN with the inter SGSN RA Update.
The current mechanisms for int... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.9.4 Analysis and comparison of the “anchor SGSN” and “non-anchor SGSN” concepts | The following aspects need to be considered when considering inter SGSN RA update concepts for GPRS/UMTS:
• Support of QoS requirements (e.g. transfer delay (for real time traffic), reliability (ability to handle correctly traffic requiring a high reliability), service interruption (for real time traffic)
• Relationshi... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.9.5 Support of QoS requirements | Transfer delay
Both the network and radio paths create delay within GPRS/UMTS communications. The non-anchor mechanism always crosses three GPRS nodes during communications (RNC, current SGSN, GGSN). The “anchor SGSN” architecture uses the same 3 nodes until an SGSN RA update occurs, then a new node (the drift SGSN)... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.9.5.1 Service interruption at SRNS relocation | With the anchor SGSN architecture service interruption may exist during the change over of path from old RNC to new RNC, mechanisms such as parallel paths could be used to prevent or minimise this. The anchor SGSN would acts as the anchor for multiple PDP contexts (potentially to different GGSN which could be located... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.9.5.2 Network resources used | As shown in Figure 1216, the non-anchor SGSN architecture requires less nodes and transmission resources than the anchor SGSN architecture. However, the impacts upon the network resources in terms of signalling, buffering and processing load requirements need to be addressed. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.9.5.3 Quality of service requirements | The optimum mechanism to satisfy the service requirements need to be considered, for example for a non real time, long duration packet session the anchor SGSN may not be optimum. Alternatively, for a real-time short duration packet session the non-anchor concept may not satisfy the QoS requirements at SRNS relocatio... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.9.5.4 Support for Class A (GSM/GPRS) and UMTS Simultaneous Mode operation | Within GSM/GPRS the mechanisms used within the MS and the network to support Class B/C operation are different to those required for Class A. Simultaneous mode is required within UMTS (R99) which will place requirements to the GSM/.GPRS/UMTS R99 standards. The impacts on the network and MS usage and control of radio ... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.9.5.5 Mobility Management | For MM point of view, interworking with 2G-SGSN has to be considered. A non-anchor SGSN architecture makes it easy since the GGSN is the anchor point in both 2G-GPRS and UMTS networks. The concepts chosen for UMTS and GSM/GPRS for R99 need to be compatible.
In the case SGSN anchor concept is introduced in R99 GPRS, sev... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.9.5.6 Comparison of developments needed within the standards for GSM/GPRS/UMTS R99 | • R99 will include the support of QoS within GSM/GPRS and UMTS.
• Class A operation and UMTS simultaneous mode will be required for R99.
• The anchor SGSN concept would include the specification of drift SGSN and packet forwarding mechanisms.
• The non-anchor concept may need enhancement to satisfy the QoS concepts and... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.10 Quality of service | • Application/End to end QoS
• QoS Segments (e.g. Radio, UTRAN, CN, Internet)
• QoS Mapping (between different segments/layers)
• Radio Access Bearers
• Resource management
• Interfaces/APIs between Application, TE, MT
• Charging of QoS aware applications |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.11 Others | |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.11.1 GPRS/IP support for Multi-media service | The following developments are needed within IP/GPRS to support the expected multi-media requirements of UMTS (note this list is not exhaustive):
QoS for GPRS: To enable real-time ‘streaming’ developments.
Adoption of IP Telephony, H.323 and equivalent PSTN/Internet technologies: To support the control and interworking... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.11.2 Separation of switching and control | Proposed Architecture
In this section the concept of a logically Separated Call Control (SCC) server is introduced. Currently CC is integrated with each of the MSCs in a network. Here it is suggested (and shown in figure 18) that a single CC function is implemented which is logically separated from the switch. The phys... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.11.2.1 Benefits | The separation of switching and control functions offers the following benefits:
Architectural Flexibility: The separation of bearer from the control allows flexibility in locating the desired functions.(functions could either be centralised or distributed). For instance, the switching and call control functions perfor... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.11.2.2 Drawbacks | Separation of switching and control means defining the interfaces between the various control functions (such as cal control, mobility management, session control, etc.) and the switching functions (i.e., switching matrix). For example in the case of a GSM MSC, this would mean defining an open interface between the MSC... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.12 New Handover functionalities | The radio access network has to be capable of connecting to a variety of existing core networks. This leads to a requirement that the UTRAN will be allowed to connect with evolved forms of existing CNs. There will be the need to support new Handover functionalities between UMTS and 2G systems.
The support of multimedi... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.13 Reduction of UMTS signalling | |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.13.1 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 | 5.13.1.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 | 5.13.2 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 eliminati... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.14 Transcoder Control | In order to improve voice quality for mobile-to-mobile calls (MS-MS calls) in GSM Phase 2+ networks, Tandem Free Operation (TFO) using in-band signalling has been specified. The equivalent function in Japan's PDC (Personal Digital Cellular) network is known as Transcoder Bypass, which has been specified to make use of ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.