hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
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 ... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.15 Support of multimedia services | One of the most important requirements for UMTS is the capability of supporting multimedia services.
The following principles should guide and apply to the support of multimedia services in UMTS:
• Multimedia services in relation to UMTS should be standardised and handled according to emerging multimedia standards. SMG... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.16 Support of services requiring variable bit rate | • If a number of applications use VBR data flows then packet transfer mode on the radio and network side has to be considered in order to make efficient use of resources.
• If packet transfer is allowed on the radio side, a finer degree of location management is/may be needed for radio resource optimisation (if only t... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.18 GSM and UMTS cells in the same registration area | The concept of GSM and UMTS cells in the same registration area was introduced in order to minimize location update signaling when changing between GSM and UMTS systems. Especially, the lack of UMTS coverage, e.g. in-building coverage in urban or suburban areas, can lead mobiles frequently changing between GSM and UMTS... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.18.1 Open issues | The following open issues, opportunities and challenges have been identified concerning this concept:
a) Security.
In UMTS both MS authentication and network authentication is planned to be implemented. Some solutions have been proposed for MS authentication, ciphering and integrity check during change from GSM to UMTS... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 5.19.1 Introduction | Within release 99 it is a working assumption that existing and future multimedia protocols can be supported by the UMTS CC/SM as application layer protocols. Where terminals support voice over both CS and PS domains, MT calls currently would require separate MSISDNs. It is desirable to allow the use of a single MSISD... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 6 Interoperability between GSM and UMTS | • Transparency [from a users perspective] of roaming and handover
• Re-use of existing subscription profiles
Note: This list is not exhaustive and is FFS.
This allows easier management and deployment of a new UMTS network.
UMTS is a system supporting handovers between GSM and UMTS in both directions. To support these h... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 6.1 Circuit Switched Handover and Roaming Principles | Introduction of a UMTS Core Network necessitates the inter-connection with legacy systems to allow inter-PLMN roaming and handover.
For ease of convergence with the existing networks and the introduction of dual mode handsets, roaming and handover to/from UMTS should be performed in the simplest manner that requires as... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 6.2 Packet Switched Handover and Roaming Principles | The introduction of a UMTS core Network as described in section 11.1 illustrates the requirement for inter-connection with the legacy GSM system to allow inter-PLMN roaming and handover.
Even though there is no current GPRS deployment, the operator may decide to deploy a GPRS network prior to the deployment of a UMTS n... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 6.2.1 Implications | The active PDP context resides in the same GGSN even after a handover between GSM and UMTS (both directions). This corresponds in principle to the anchor concept on the circuit switched side, but note that whereas packet sessions are long lived, the anchor MSC remains only for the duration of a CS call (typically much ... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 6.2.2 Signalling procedures | The signalling procedures shows how handover UMTS <-> GSM GPRS can be done. The parameters carried by each message is not complete and shall be seen as examples of important information carried be the messages.
The signalling sequences shows the case when the UMTS 3G_SGSN and the GPRS 2G_SGSN are located in separate “p... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 7 Network Migration And Evolution | The installed base of GSM networks will be very comprehensive at the time of the UMTS roll out. These GSM networks will co-operate very closely with and in many cases be partly integrated into the overall UMTS network. Thus network migration and evolution is a very fundamental aspect to consider when standardising UMTS... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 7.1 Network Migration Scenarios | A number of principally different network migration scenarios can be envisioned, e.g.:
• GSM to GSM release 99 (GSM operator with no UMTS licence and no UMTS roaming/handover agreements).
• GSM to GSM release 99 with support for dual mode ‘UMTS visitors’ (GSM operator with no UMTS licence but with UMTS roaming/handove... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 8 Protocol Architecture | |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 8.1 IU Signalling Bearer Requirements for IP Domain | |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 8.1.1 Connectionless and Connection Oriented Services | Connection-oriented and connection-less IU Signalling Bearers are required. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 8.1.2 Dynamic Bandwidth Allocation | The IU Signalling Bearer shall support rapid and flexible allocation and de-allocation of IU transport resources. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 8.1.3 Reliable Transfer | The IU Signalling Bearer shall provide reliable delivery of signalling data. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 8.1.4 Flow Control | The IU Signalling Bearer shall provide throttling mechanisms to adapt to intermittent congestion in the UTRAN or Core Network. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 8.1.5 Redundancy and Load Sharing | To handle detected failures and signalling data congestion, the IU Signalling Bearer shall be capable of dynamically routing over alternate routes that minimise delay. If the delay metrics over alternative routes are identical, the IU Signalling Bearer shall be capable of spreading traffic over the identical paths, th... |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 8.1.6 Large Pdu Size | To support large transactions, it is important for the IU Signalling Bearer to provide a Signalling Data Unit size, large enough to allow for all signalling messages to be transferred without fragmentation. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 8.1.7 Signalling Bearer Management | To support supervision of IU Signalling Bearers, mechanisms for managing IU Signalling Bearers shall be used to provide status information to the RANAP for individual UE(s). The signalling bearer shall also maintain a consistent UE Activation State in the access and the core network. |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 8.1.8 Transport Media Independence | The IU Signalling Bearer shall be independent of the underlying transport media (e.g. ATM). |
6e5fdf15efa25f132d2e779f583f3558 | 23.920 | 9 History | Document history
V1.0.0
June 1999
Creation of document from 23.20, all sections except 7
V2.0.0
June 1999
Some editorial changes in order to prepare the document for the approval by the TSG SA, June 1999 meeting
V3.0.0
July 1999
Template changed, clauses and sub-clauses numbering corrected, administrative clauses added... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 1 Scope | The present document identifies the parameters of the access stratum part of the UE radio access capabilities. Furthermore, some reference configurations of these values are defined. The intention is that these configurations will be used for test specifications. |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 2 References | [1] 3GPP TS 25.323: "Packet Data Convergence Protocol (PDCP) protocol". |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply:
UE User Equipment
UMTS Universal Mobile Telecommunication System
UTRAN UMTS Terrestrial Radio Access Network |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4 UE radio access capability parameters | In the following the UE radio capability parameters are defined. In addition the relevant RRC configuration parameters are shown when applicable. When using the RRC configuration parameters, UTRAN needs to respect the UE capabilities. Only parameters for which there is a need to set different values for different UEs a... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.1 PDCP parameters | Header compression algorithm supported
Defines whether header compression algorithms will be supported by the UE. If it will be supported it will be the RFC 2507 as specified in 3GPP TS 25.323. |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.2 BMC parameters | No UE radio access capability parameters identified. |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.3 RLC parameters | NOTE: It is FFS whether some of the RLC functions should be considered as UE capabilities.
Total RLC AM buffer size
The total buffer size across all RLC AM entities puts requirements on memory.
UTRAN controls that the UE capability can be fulfilled through the following parameters:
1. The number of RLC AM entities conf... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.4 MAC parameters | No capability parameters identified. |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.5 PHY parameters | |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.5.1 Transport channel parameters in downlink | Maximum sum of number of bits of all transport blocks being received at an arbitrary time instant
NOTE: "Being received" refers to all bits in the active TFC within the TFCS over all simultaneous transport channels received by the UE. "Arbitrary time instant" means that the time instant corresponding to the highest sum... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.5.2 Transport channel parameters in uplink | Maximum sum of number of bits of all transport blocks being transmitted at an arbitrary time instant
NOTE: "Being transmitted" refers to all bits in the active TFC within the TFCS over all simultaneous transport channels transmitted by the UE. "Arbitrary time instant" means that the time instant corresponding to the hi... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.5.3 FDD Physical channel parameters in downlink | Maximum number of DPCH/PDSCH codes to be simultaneously received
Defines the number of codes the UE is capable of receiving in parallel. For DPCH in soft/softer handover, each DPCH is only calculated once in this capability. The capability does not include codes used for S-CCPCH.
Maximum number of physical channel bits... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.5.4 FDD physical channel parameters in uplink | Maximum number of DPDCH bits per 10 ms
This capability combines the 'Max number of DPDCH' and 'Minimum SF' capabilities into one capability. Note that no flexibility is lost due to this, as multiple DPDCH is only used for SF=4, i.e. when the number of DPDCH bits exceed a certain value.
The number of DPDCH channel bits ... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.5.5 TDD physical channel parameters in downlink | Maximum number of timeslots per frame
Defines the maximum number of timeslots per frame that the UE can receive.
Maximum number of physical channels per frame
This parameter defines how many physical channels can be received during one frame. The distribution of the received physical channels on the received timeslots ... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.5.6 TDD physical channel parameters in uplink | Maximum Number of timeslots per frame
Defines the maximum number of timeslots per frame that the UE can transmit.
Maximum number of physical channels per timeslot
Defines the maximum number physical channels transmitted in parallel during one timeslot.
Minimum SF
Defines the minimum SF supported by the UE.
Support of P... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.5.7 RF parameters | UE power class
The value is fixed per UE and is not related to any configuration parameter.
Radio frequency bands
Defines the uplink and downlink frequency bands supported by the UE.
Configuration parameters are UTRA RF Channel numbers for uplink and downlink, which are part of Frequency info.
Tx/Rx frequency separatio... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.6 Multi-mode related parameters | Support of UTRA FDD/TDD
Defines whether UTRA FDD and/or TDD are supported.
There is no explicit configuration parameter. |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.7 Multi-RAT related parameters | Support of GSM
Defines whether GSM is supported or not.
There is no explicit configuration parameter.
Support of multi-carrier
Defines whether multi-carrier is supported or not.
There is no explicit configuration parameter. |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.8 LCS related parameters | Standalone location method(s) supported
Defines if a UE can measure its location by some means unrelated to UTRAN (e.g. if the UE has access to a standalone GPS receiver).
OTDOA UE based method supported
Defines if a UE supports the OTDOA UE based schemes.
Network Assisted GPS support
Defines if a UE supports either of... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 4.9 Measurement related capabilities | Need for downlink compressed mode
Defines whether the UE needs compressed mode in the downlink in order to perform inter-frequency or inter-RAT measurements. There are separate parameters for measurements on each UTRA mode, on each RAT, and in each frequency band.
Need for uplink compressed mode
Defines whether the UE ... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 5 Possible UE radio access capability parameter settings | |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 5.1 Value ranges | Table 5.1: UE radio access capability parameter value ranges
UE radio access capability parameter
Value range
PDCP parameters
Header compression algorithm supported
Yes/No
RLC parameters
Total RLC AM buffer size
2,10,50,100,150,500,1000 kBytes
Maximum number of AM entities
3,4,5,6,8,16,32
PHY parameters
Transport chann... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 5.2 Reference UE radio access capability combinations | Based on required UE radio access capabilities to support reference RABs as defined in clause 6, this clause lists reference UE Radio Access capability combinations. Subclause 5.2.1 defines reference combinations of UE radio access capability parameters common for UL and DL. Subclause 5.2.2 and 5.2.3 define reference c... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 5.2.2 Combinations of UE Radio Access Parameters for DL | Table 5.2.2.1: UE radio access capability parameter combinations, DL parameters
Reference combination of UE Radio Access capability parameters in DL
32kbps class
64kbps class
128kbps class
384kbps class
768kbps class
2048kbps class
Transport channel parameters
Maximum sum of number of bits of all transport blocks being... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 5.2.3 Combinations of UE Radio Access Parameters for UL | Table 5.2.3.1: UE radio access capability parameter combinations, UL parameters
Reference combination of UE Radio Access capability parameters in UL
32kbps class
64kbps class
128kbps class
384kbps class
768kbps class
Transport channel parameters
Maximum sum of number of bits of all transport blocks being transmitted at... |
a81d9bd99016b59710681951aa0bdd87 | 25.926 | 6 Usage of UE radio access capabilities | NOTE: The rationale for the parameter combination settings will be explained here. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.