id
stringlengths 5
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 214
values | working_group
stringclasses 30
values | url
stringlengths 67
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
25.878
|
RL timing adjustment
|
TR
|
5.1.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.878/25878-510.zip
|
The purpose of the present document is to help the TSG RAN WG3 group to specify the changes to existing specifications, needed for the introduction of the Radio Link Timing Adjustment worktask., as proposed in [1].
The document describes the agreed requirements related to the worktask, the different areas that were studied, the agreements that were made, and it identifies the affected specifications with related Change Requests. It also describes the schedule of the worktask.
The present document is a 'living' document, i.e. it is permanently updated and presented to all TSG-RAN meetings.
|
25.879
|
Separation of resource reservation and radio link activation
|
TR
|
5.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.879/25879-500.zip
|
The purpose of the present document is to help the TSG RAN WG3 group to specify the changes to existing specifications, needed for the introduction of the Separation of resource reservation and radio link activation worktask, as proposed in [1].
The document describes the agreed requirements related to the worktask, the different areas that were studied, the agreements that were made, and it identifies the affected specifications with related Change Requests. It also describes the schedule of the worktask.
The present document is a 'living' document, i.e. it is permanently updated and presented to all TSG-RAN meetings.
|
25.880
|
Re-arrangement of Iub transport bearers
|
TR
|
5.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.880/25880-500.zip
|
Based on [1], the objective of this work item is to introduce a new procedure in the NBAP to enable the Node B to indicate the request for switching the transport bearers and a Communication Control Port from one physical termination point to another. The purpose of the present document is to help the TSG RAN WG3 group to specify the changes to the existing NBAP specification.
It is intended to gather all information in order to trace the history and the status of the Work Task in RAN WG3. It is not intended to replace contributions and Change Requests, but only to list conclusions and make reference to agreed contributions and CRs. When solutions are sufficiently stable, the CRs can be issued.
It identifies the affected specifications with related Change Requests.
It also describes the schedule of the Work Task.
The present document is a 'living' document, i.e. it is permanently updated and presented to all TSG-RAN meetings.
|
25.881
|
Improvement of Radio Resource Management (RRM) across RNS and RNS/BSS
|
TR
|
5.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.881/25881-500.zip
|
This document is for part of the Rel 5 study item “Improvement of RRM across RNS and RNS/BSS”.
This study report describes the techniques to improve the RRM across RNS and RNS/BSS. It also deals with the feasibility of the techniques which are described in this document and their benefits.
|
25.882
|
1,28 Mcps TDD option base station classification
|
TR
|
5.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.882/25882-500.zip
|
The present document is a Technical Report on Release 5 work item “Base Station Classification for 1,28 Mcps TDD option.
|
25.883
|
Direct Transport Bearers Between SRNC and Node-B
|
TR
|
5.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.883/25883-500.zip
|
The purpose of the present document is to help the TSG RAN WG3 group to study aspects of the direct Node-B to SRNC transport bearers in preparation for a WI on this topic, as proposed in [1].
As requested by TSG-RAN, the document describes the identified consequences of the direct transport bearers, and classifies these main consequences as benefits or drawbacks.
Since the consequences might be different for an ATM and IP TNL, these different TNL’s are handled separately.
This document is a ‘living’ document, i.e. it is permanently updated and presented to all TSG-RAN meetings.
|
25.884
|
Iur Neighbouring cell reporting efficiency optimisation
|
TR
|
5.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.884/25884-500.zip
|
The purpose of the present document is to help the TSG RAN WG3 group to specify the changes to existing specifications, needed for the introduction of the Neighbouring Cells Reporting Optimization worktask., as proposed in [1].
The document describes the agreed requirements related to the worktask, the different areas that were studied, the agreements that were made, and it identifies the affected specifications with related Change Requests. It also describes the schedule of the worktask.
The present document is a 'living' document, i.e. it is permanently updated and presented to all TSG-RAN meetings.
|
25.933
|
IP transport in UTRAN
|
TR
|
5.4.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.933/25933-540.zip
|
The purpose of the present document is to help the TSG RAN WG3 group to specify the changes to existing specifications, needed for the introduction of "IP Transport" option in the UTRAN for Release 5. It is intended to gather all information in order to trace the history and the status of the Work Task in RAN WG3. It is not intended to replace contributions and Change Requests, but only to list conclusions and make reference to agreed contributions and CRs. When solutions are sufficiently stable, the CRs can be issued.
It describes agreed requirements related to the Work Task, and split the Work Task into "Study Areas" in order to group contributions in a consistent way.
It identifies the affected specifications with related Change Requests.
It also describes the schedule of the Work Task.
The present document is a "living" document, i.e. it is permanently updated and presented to all TSG-RAN meetings.
|
25.945
|
RF requirements for low chip rate TDD option
|
TR
|
5.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.945/25945-520.zip
|
This technical Report identifies the RF Radio Transmission/Reception and Radio Resource Management requirements for the 1.28 Mcps UTRA TDD option, including the commonalties and differences. Furthermore, the impact on the RF system Scenarios and BS conformance testing is also identified.
|
25.952
|
TDD Base Station (BS) classification
|
TR
|
5.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.952/25952-520.zip
|
This document is a Technical Report on Release 5 work item “TDD Base Station Classification”.
|
25.991
|
Feasibility study on the mitigation of the effect of common pilot channel (CPICH) interference at the user equipment
|
TR
|
5.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.991/25991-510.zip
|
The present document assesses the feasibility of mitigating the effect of CPICH interference at the UE. The report includes performance evaluation of this feature using radio network level simulations and link level simulations, and complexity evaluation.
|
25.994
|
Measures employed by the UMTS Radio Access Network (UTRAN) to overcome early User Equipment (UE) implementation faults
|
TR
|
5.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.994/25994-500.zip
|
The present document clarifies recommended measures which may be adopted by UTRAN to enable inter-working to be obtained between network and various early User Equipment (UE) implementations of the 3GPP specification. If possible, the 3GPP core specifications should be updated accordingly.
|
25.995
|
Measures employed by the UMTS Radio Access Network (RAN) to cater for legacy User Equipment (UE) which conforms to superseded versions of the RAN interface specification
|
TR
|
5.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.995/25995-500.zip
|
The present document clarifies recommended measures employed by the UTRAN to cater for legacy User Equipment (UE) which conforms to superseded versions of the RAN interface specification. If possible, the 3GPP core specifications should be updated accordingly.
|
27.103
|
Wide Area Network Synchronization
|
TS
|
5.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/27_series/27.103/27103-500.zip
|
This specification provides a definition of a Wide Area Synchronization protocol. The synchronization protocol is based upon current synchronization industry standards.
The present document covers Wide Area Network Synchronization between current and future mobile communication end-user devices, desktop applications and server-based information servers. This is a living document and, as such, it will evaluate new technologies (e.g. XML) for inclusion as they become readily available.
|
27.901
|
Report on Terminal Interfaces - An Overview
|
TR
|
5.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/27_series/27.901/27901-500.zip
|
The present document discusses external and internal interfaces of a terminal, with the exception of the radio and USIM interfaces. The focus of the study has been on external interfaces, to identify where existing industry standards can be used and whether there would be a need for specifications to be produced within 3GPP.
|
31.048
|
Security mechanisms for the (U)SIM application toolkit; Test specification
|
TS
|
5.1.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.048/31048-510.zip
|
The present document covers the minimum characteristics considered as necessary in order to provide compliance to 3GPP TS 23.048 " Security Mechanisms for the (U)SIM application toolkit; Stage 2" [6].
The present document describes the technical characteristics and methods of test for testing the Security Mechanisms for the (U)SIM application toolkit. It specifies the following parts:
- test applicability
- test environment description
- tests format
- test area reference
- conformance requirements
- Test Area Files
- test procedure
- test coverage
- a description of the associated testing tools that shall be used.
|
32.200
|
Telecommunication management; Charging management; Charging principles
|
TS
|
5.9.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.200/32200-590.zip
|
The present document describes the principles of charging and billing for the provision of service and services by a 3G‑system.
The present document elaborates on the charging requirements described in the Charging Principles in 3GPP TS 22.101 [1]. It allows the generation of accurate charging information to be used in the commercial and contractual relationships between the parties concerned. The present document is not intended to duplicate existing standards or standards being developed by other groups on these topics, and references these where appropriate.
The Charging Data Records (CDRs) generated by the network elements of the 3G network, are required for a number of telecom management activities including, but not limited to, the following:
• the billing of home subscribers, either directly or via service providers, for network utilisation charges;
- the settlement of accounts for traffic carried or services performed by fixed network operators and other operators;
- the settlement of accounts with other PLMNs for roaming traffic via the transferred account procedure;
- statistical analysis of service usage;
- as archival information in dealing with customer service and billing complaints.
In addition to the information collected from network elements, network management functions are required for the administration of charging data.
The present document is part of a series of documents specifying charging functionality in UMTS networks. The UMTS charging architecture and principles are specified in the present document which provides an umbrella for other charging documents that specify the structure and content of the CDRs and the interface protocol that is used to transfer them to the collecting node. The CDRs used in the Circuit Switched (CS) domain are specified in document3GPP TS 32.205 [5]. The CDRs content and transport within the PS domain are described in3GPP TS 32.215 [6] document, while CDRs used for application services are defined in document3GPP TS 32.235 [17].
The relationship among these charging specifications is illustrated in figure 1.1.
Figure 1.1: Charging Documents Structure
For the purpose of the present document, the charging data is considered to be generated and collected by charging functions in the network elements.
Charging data fields are collected and CDRs generated by the network elements for transfer to the billing system. For the packet switched domain, the CDRs are first sent to the Charging Gateway Function (CGF) for storage and further processing. The CGF may be a distinct network element or may be integrated into the packet domain network elements themselves.
The objectives of the present document are:
- to describe principles of charging in a 3G network;
- to provide a description of the charging architecture; and
- to provide the descriptions of events and triggers for the generation of Charging Data Records (CDRs).
|
32.205
|
Telecommunication management; Charging management; Charging data description for the Circuit Switched (CS) domain
|
TS
|
5.9.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.205/32205-590.zip
|
The GSM and UMTS PLMNs support a wide range of circuit based services. In order to enable operators the ability to provide a commercially viable service there is a need to provide charging functions.
The present document is part of a series of documents specifying charging functionality in UMTS networks. The UMTS charging architecture and principles are specified in TS 32.200 [22] which provides an umbrella for other charging documents that specify the structure and content of the CDRs and the interface protocol that is used to transfer them to the collecting node.
The present document specifies the structure and the contents of the CDRs that are collected by the relevant network elements for circuit switched services in 2G (GSM) and 3G (UMTS) networks. It also defines the syntax for the transfer of these CDRs from the collecting nodes to billing post-processing systems using standard file transfer protocols.
The CDRs content and transport within the PS domain are described in TS 32.215 [23] document, while CDRs used for application services are defined in document TS 32.235 [24].
The relationship among these charging specifications is illustrated in figure 1.
Figure 1: Charging Documents Structure
The interface definitions of GSM 12.05 are maintained for 2G, in order to assure backward compatibility to earlier GSM releases.
The charging architecture and principles that the present document is based on are specified in TS 32.200 [22].
All references, abbreviations, definitions, descriptions, principles and requirements that are common to charging in UMTS domains or subsystems are provided in the umbrella TS 32.200 [22]. To avoid unnecessary duplications, they are not repeated in the present document unless it is essential.
|
32.215
|
Telecommunication management; Charging management; Charging data description for the Packet Switched (PS) domain
|
TS
|
5.9.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.215/32215-590.zip
|
The GSM and UMTS PLMN support a wide range of packet based services by means of the General Packet Radio Service (GPRS), as defined in 3GPP TS 22.060 [1] and 3GPP TS 23.060 [2]. In order to enable operators the ability to provide a commercially viable service, there is a need to provide charging functions. For GPRS these functions include the generation of Charging Data Records (CDRs) by the Serving GPRS Support Node (SGSN) and the Gateway GPRS Support Node (GGSN) as well as the transport of these CDRs to a Billing System (BS) through a Charging Gateway Function (CGF).
The present document is part of a series of documents specifying charging functionality in UMTS networks. The UMTS charging architecture and principles are specified in document TS 32.200 [3] which provides an umbrella for other charging documents that specify the structure and content of the CDRs and the interface protocol that is used to transfer them to the collecting node. The CDRs content and transport within the PS domain are described in the present document. The CDRs used in the Circuit Switched (CS) domain are specified in document TS 32.205 [4] while CDRs used for application services are defined in document TS 32.235 [5]. The present document structure is depicted in figure 1.
Figure 1: Charging Documents Structure
All references, abbreviations, definitions, descriptions, principles and requirements that are common to charging in UMTS domains or subsystems are provided in the umbrella document [3]. To avoid unnecessary duplications, they are not repeated in the present document unless it is essential.
|
32.225
|
Telecommunication management; Charging management; Charging data description for the IP Multimedia Subsystem (IMS)
|
TS
|
5.11.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.225/32225-5b0.zip
|
The present document covers both online and offline charging for the IMS. For clarity, the terms Offline Charging and Online charging as applied to the IMS are defined here in clause 3. These definitions are the same as listed in TS 32.200 [2].
The IMS charging architecture details, requirements, definitions and principles are listed in TS 32.200 [2] and therefore are not repeated here.
In the present document the charging data triggers, message content and format are specified along with the transport of these messages using the Diameter protocol. Details about charging message flows and the definitions of the Diameter AVPs are also included in the present document. This information is divided into two main clauses: Online Charging and Offline Charging.
|
32.235
|
Telecommunication management; Charging management; Charging data description for application services
|
TS
|
5.5.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.235/32235-550.zip
|
The present document is part of a series of documents specifying charging functionality in UMTS network with application services. The UMTS core network charging principles are specified in document TS 32.200 [2], which provides an umbrella for other charging documents that specify the structure and content of the CDRs and the interface protocol that is used to transfer them to the collecting node. The document structure is defined in figure 1. The CDR content and transport for application services are described in the present document especially for MMS. As the basis and reference for this work is taken the functional description of the MMS specified for stage 1 in TS 22.140[3] and stage 2 in TS 23.140 [4].
Figure 1 Charging Document Structure
All references, abbreviations, definitions, descriptions, principles and requirements that are common are defined in the 3GPP Vocabulary [1] and specialised to charging in UMTS domains or subsystems are provided in the umbrella document [2].
|
32.301-1
|
Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): requirements
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.301-1/32301-1-200.zip
|
The purpose of Notification IRP is to define an interface through which an IRPManager can subscribe to an IRPAgent for receiving notifications. This document is the « Requirements » of Notification IRP. It defines, for the purpose of subscribing to an IRPAgent for receiving notifications, the basic requirements that shall be fulfilled on Itf-N.
How IRPManager discovers the IRPAgent’s address or reference (so that IRPManager can invoke an operation) is outside the scope of the present document.
|
32.301-2
|
Telecommunication management; Configuration Management (CM); Part 2: Notification Integration Reference Point (IRP): Information Service
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.301-2/32301-2-200.zip
|
The purpose of Notification IRP is to define an interface through which an IRPManager can subscribe to an IRPAgent for receiving notifications. This document is the « Information Service » of Notification IRP. It defines, for the purpose of subscribing to an IRPAgent for receiving notifications, the information observable and controlled by management system’s client and it also specifies the semantics of the interactions used to carry this information. It also defines the information common to all notifications which is called the notificationHeader.
An IRPAgent supporting this IRP IS may emit one or multiple categories of notifications, such as alarms (as specified in Alarm IRP : Information Service [1]) and others. This IRP IS defines a mechanism that IRPManager can use to determine the categories of notifications supported by an IRPAgent. It also defines a mechanism (subscribe and unsubscribe operations) that IRPManager can use to specify the categories of notifications IRPAgent should emit to IRPManager during subscription. It also defines a mechanism (getSubscriptionIds operation) that IRPManager can use to check which categories of notifications it has subscribed to. IRPManager can set and change filter criteria applicable during the life-cycle of a subscription. IRPManager can also exercise flow-control on IRPAgent’s emission of notifications (suspendSubscription and resumeSubscription operations).
Using different managerReference, an IRPManager can subscribe several times. It will result in multiple subscriptions. As far as IRPAgent is concerned, notifications are sent to multiple "places".
Using the same managerReference, an IRPManager can subscribe several times specifying different categories of notifications.
This IRP IS does not specify information that is carried in some but not all notifications. That kind of information is specified in other IRP ISs involved. For example, perceivedSeverity is a piece of information specific for notifications carrying alarm information. This information is not defined in the present document but in Alarm IRP : Information Service [1].
How IRPManager discovers the IRPAgent’s address or reference (so that IRPManager can invoke an operation) is outside the scope of the present document.
|
32.800
|
Telecommunication management; Management level procedures and interaction with UTRAN
|
TR
|
5.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.800/32800-500.zip
|
The principle objective of the present document is to provide supporting information for the O&M standardisation of a (multi-vendor) UTRAN network. The actual specification work relating to the O&M interface between Network and Network Manager can be found in [9], [10] and [11] and for the Iub interface in [1]. For this reason the present document may contain information or working assumptions which are not a direct part of the specifications, but are essential to the progress and informed decision making.
|
32.802
|
Telecommunication management; User Equipment Management (UEM) feasibility study
|
TR
|
5.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.802/32802-510.zip
|
The scope of the present document is a Release 5 feasibility study that evaluate aspects of User Equipment Management (UEM) which would be beneficial to standardise post-Release-5. For Release 5 the present document does not have a factual impact on other 3GPP Work Items (WIs).
User Equipment (UE) includes both the USIM and Mobile Equipment (ME) domains and so it is emphasised that the scope of UEM includes both the USIM and ME domains.
The present document is focussed on the UEM interface to the UE Over-The-Air (OTA). There is a potential direct interface between the UE Managers and the UE; for example, a user may be able to upgrade the operating system in its UE by taking it to the UE manufacturer's service centre. This direct interface is outside the scope of the present document .
The user interface will be important in delivering UEM. However, the user interface is both outside the scope of the present document and outside the scope of the standardisation of UEM.
|
34.943
|
Analysis of difference between FDD and 1.28 Mcps TDD and corresponding effect on terminal conformance test in radio access stratum protocol aspects
|
TR
|
5.0.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.943/34943-500.zip
|
The present document analyzes the differences of Uu/Iub interface between 1.28Mcps TDD and FDD, and the effect on UE conformance testing for 3rd Generation Terminals.
The actual test case descriptions will be contained in other documents.
|
42.019
|
Subscriber Identity Module Application Programming Interface (SIM API); Stage 1
|
TS
|
5.1.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/42_series/42.019/42019-510.zip
|
The present document defines the stage one description of the Subscriber Identity Module Application Programming Interface (SIM API) internal to the SIM. Stage one is an overall service description, and does not deal with the implementation details of the API.
The present document includes information applicable to network operators, service providers and terminal, SIM, switch and database manufacturers.
The present document contains the core requirements which are sufficient to provide a complete service.
It is highly desirable however, that technical solutions for a SIM API should be sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in the present document may implement requirements which are considered outside the scope of the present document. This additional functionality may be on a network-wide basis, nation-wide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the core requirements of the service.
|
43.019
|
Subscriber Identity Module Application Programming Interface (SIM API) for Java Card; Stage 2
|
TS
|
5.6.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/43_series/43.019/43019-560.zip
|
The present document defines the stage two description of the Subscriber Identity Module Application Programming Interface (SIM API) internal to the SIM.
This stage two describes the functional capabilities and the information flow for the SIM API implemented on the Java Card 2.1 API specification [6].
The present document includes information applicable to network operators, service providers and SIM, server and database manufacturers.
|
21.133
|
3G security; Security threats and requirements
|
TS
|
4.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/21_series/21.133/21133-410.zip
|
This specification takes notice of the Security Principles and Objectives as set out in [1]. It contains an evaluation of perceived threats to 3GPP and produces subsequently a list of security requirements to address these threats.
As teleservices and applications will not, in general, be standardised, it is difficult to predict their exact nature. Therefore, this specification considers all security threats and aims at listing generic security requirements that shall be applicable irrespective of the actual services offered. The list of threats and requirements may however need to be updated as the 3GPP system evolves.
The threat analysis performed relies to a large extent on previous experiences with 2G systems, in particular GSM, and takes into account known problems from that area.
The security requirements listed in this specification shall be used as input for the choice of security features and the design of the 3GPP security architecture as specified in [2].
The structure of this technical specification is as follows:
clause 2 lists the references used in this specification;
clause 3 lists the definitions and abbreviations used in this specification;
clause 4 contains a reference to the general objectives for 3G security;
clause 5 contains an overview of the context in which the security architecture of 3G is designed;
clause 6 contains a list of identified security threats to 3G, and gives some results from the threat analyses that have been performed;
clause 7 contains an overview of the risk assessment resulting from the threat analyses performed
clause 8 contains the resulting list of security requirements for 3G and indicates how these requirements relate to the threats and the security objectives .
Finally, Annex A gives some more detailed information on threats and risks connected to so called false base station attacks.
|
23.908
|
Technical report on Pre-Paging
|
TR
|
4.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.908/23908-400.zip
|
The purpose of the present document is to study:
1. The potential applications of Pre-paging in GSM/UMTS networks.
2. The impact of Pre-paging on the GSM/UMTS specifications.
3. The interaction of Pre-paging with the work carried out by SMG2 and SMG3 on Classmarks for UMTS (i.e. Service Classmark and Terminal classmark).
It is a requirement of the report that the Pre-paging mechanism does not require an upgrade of the MAP application context version.
|
23.909
|
Technical report on the Gateway Location Register
|
TR
|
4.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.909/23909-400.zip
|
The present document describes the use of a Gateway Location Register within the UMTS Core Network as a means of reducing the amount of MAP signalling traffic associated with location management carried over inter-PLMN links for roaming users.
One of the requirements of the present document is to describe a network architecture where the presence of a GLR within a UMTS PLMN is not visible to either a second generation PLMN (i.e. GSM release 98 or earlier) or a 3G PLMN (i.e. GSM Release 99 or later). So the objective of this report is that changes to GSM specified interfaces or procedures will not be needed in order to:
- integrate a GLR into a UMTS PLMN;
- allow interworking between a GLR-enabled UMTS network and a GSM or UMTS network without a GLR.
The present document will be restricted to the study of the case where the GLR supports one VPLMN only. A separate TR will be required if support of multiple VPLMNs by the GLR is to be studied.
The present document will study support of multiple HPLMNs by the GLR.
|
23.911
|
Technical report on Out-of-band transcoder control
|
TR
|
4.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.911/23911-400.zip
|
The purpose of the present document is to study:
1. The feasibility of out-of-band transcoder control in UMTS/IMT-2000 networks.
2. The impact of out-of-band transcoder control on the UMTS/IMT-2000 specifications.
The present document introduces one enhanced in-band transcoder control procedure and four out‑of‑band transcoder control procedures that might be adaptable for transcoder control in UMTS/IMT-2000 networks. Then compare each procedure from various point of views to seek the most feasible procedure.
|
23.912
|
Technical report on Super-Charger
|
TR
|
4.1.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.912/23912-410.zip
|
The present document describes the use of Super-Charger mechanism within UMTS to reduce the signalling traffic associated with mobility. This document provides a technical proposal and example uses of the Super-Charger concept but also identifies issues that require further study. Finally, this document highlights the advantages and disadvantages, and identifies the UMTS Technical Specifications that would require enhancing to support this functionality.
|
23.930
|
Iu principles
|
TR
|
4.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.930/23930-400.zip
|
This report identifies the requirements on the Iu and studies relevant principles to guide further standardisation of the related interface(s).
The different instances of the UMTS radio access currently identified are the following:
UMTS radio access network (URAN)
UMTS Terrestrial Radio Access Network (UTRAN)
Broadband Radio Access Network (BRAN)
UMTS satellite radio access network
|
25.832
|
Manifestations of Handover and SRNS relocation
|
TR
|
4.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.832/25832-400.zip
|
The present document identifies a number of handover and SRNS Relocation scenarios for UTRAN. It is intended to reflect and clarify the requirements on UTRAN, and to assist in the development of procedures and capabilities.
|
25.834
|
UTRA TDD low chip rate option; Radio protocol aspects
|
TR
|
4.1.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.834/25834-410.zip
|
The present document describes the services provided by the physical layer and the layer 2/3 functionality for support of the 1.28 Mcps low chip rate option of UTRA TDD. Based on the protocol structure existing for UTRA TDD / FDD, it is identified which modifications will be required in order to enable the layer 1 characteristics and key features of the low chip rate option.
|
25.836
|
Node B synchronization for TDD
|
TR
|
4.1.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.836/25836-410.zip
|
This TR describes the solution recommended to enable the synchronisation of NodeBs in UTRA TDD beyond that included in Rel. 99.
|
25.838
|
Node B Synchronisation for TDD (Iub/Iur aspects)
|
TR
|
4.1.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.838/25838-410.zip
|
The purpose of the present document is to help the TSG RAN WG3 group to specify the changes to existing WG3 specifications, needed for the introduction of the “Node B Synchronisation for TDD”. It is intended to gather all information in order to trace the history and the status of the Work Task in RAN WG3. It is not intended to replace contributions and Change Requests, but only to list conclusions and make reference to agreed contributions and CRs. When solutions are sufficiently stable, the CRs can be issued.
This TR describes agreed requirements related to the Work Task, and split the Work Task into “Study Areas” in order to group contributions in a consistent way.
It identifies the affected specifications with related Change Requests.
It also describes the schedule of the Work Task.
This document is a ‘living’ document, i.e. it is permanently updated and presented to all TSG-RAN meetings.
|
25.840
|
Terminal power saving features
|
TR
|
4.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.840/25840-400.zip
|
The present document is the Technical Report of the Release 4 work item “Terminal Power Saving Features”.
|
25.841
|
DSCH power control improvement in soft handover
|
TR
|
4.1.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.841/25841-410.zip
|
This document is the Technical Report for the DSCH power control improvement in soft handover, part of the Release 4 work item "DSCH power control improvement in soft handover”.
|
25.843
|
1.28 Mcps TDD UE Radio Access Capabilities
|
TR
|
4.1.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.843/25843-410.zip
|
The present document describes the UE radio access capabilities for 1,28 Mcps TDD, identifies the commonalties and explains the differences to 3,84 Mcps TDD.
|
25.844
|
Radio acces bearer support enhancements
|
TR
|
4.3.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.844/25844-430.zip
|
The present document is a technical report that summarises the work on the UTRAN Release 2000 work item "Radio Access Bearer Support Enhancements". The work items comprises of five areas of study:
1) Robust header compression
2) PDCP multiplexing
3) Variable Iu frame formats and unequal error protection over Uu
4) Channel type switching per logical channel
5) Header removal
Each study area includes the requirements of the proposed feature, a description of the basic mechanism and a discussion of the issues involved. A recommended solution is provided and impacts to other RAN WGs are analysed.
|
25.847
|
UE positioning enhancements
|
TR
|
4.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.847/25847-400.zip
|
The present document identifies possible UE positioning enhancements and new methods for UTRA TDD and FDD for Release 4. It builds the basis for evaluation and comparison of these methods and enhancements. The report also covers the impacts on Layer1 and UTRAN interfaces.
Finally, CRs to the affected specifications should be created based on this TR.
|
25.848
|
Physical Layer Aspects of UTRA High Speed Downlink Packet Access
|
TR
|
4.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.848/25848-400.zip
| |
25.849
|
DSCH power control improvement in soft handover
|
TR
|
4.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.849/25849-400.zip
|
The present document is for part of the Release 4 work item "DSCH power control improvement in soft handover".
|
25.850
|
UE positioning in UTRAN Iub/Iur protocol aspects
|
TR
|
4.3.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.850/25850-430.zip
|
The present document helps the TSG RAN WG3 group to specify the changes to existing specifications, needed for the introduction of the UE positioning in UTRAN for Release 2000.
Based on [1], standard location services are defined as the:
- cell coverage based positioning method;
- OTDOA method with network configurable idle periods; and
- network assisted GPS method.
Since cell coverage based positioning method in WG3 group is already standardised the present document will cover the Iub/Iur protocol aspects for OTDOA method with network configurable idle periods and network assisted GPS method.
It is intended to gather all information in order to trace the history and the status of the Work Task in RAN WG3. It is not intended to replace contributions and Change Requests, but only to list conclusions and make reference to agreed contributions and CRs. When solutions are sufficiently stable, the CRs can be issued.
It describes agreed requirements related to the Work Task, and split the Work Task into “Study Areas” in order to group contributions in a consistent way.
It identifies the affected specifications with related Change Requests.
It also describes the schedule of the Work Task.
The present document is a "living" document, i.e. it is permanently updated and presented to all TSG-RAN meetings.
|
25.851
|
RAB Quality of Service (QoS) Renegotiation over Iu
|
TR
|
4.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.851/25851-400.zip
|
The present document provides the current status of the work item “RAB Quality of Service Renegotiation over Iu” within 3GPP TSG RAN WG3. It describes the requirements, discusses the renegotiation procedure, and identifies the affected specifications. If information needs to be communicated to groups outside of TSG RAN WG3, it is recorded in this document.
The document is a ‘living’ document, i.e. it is continuously updated and presented to all TSG-RAN meetings.
|
25.853
|
Delay budget within the access stratum
|
TR
|
4.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.853/25853-400.zip
|
The present document evaluates the delay components introduced within the Access Stratum to provide guidelines useful both to provider for the dimensioning of a network and to manufacturers for the design of node elements. While the analysis of the possible delay sources is performed in an exhaustive way, the evaluation of single and global delay figures is limited to the case of Real Time services.
The estimation of Non Real Time service delays is not in scope of Release 99 and, therefore, it will not be considered in the present version of the Technical Report.
The figures of the present document sow possible scenarios and shall not be interpreted as requirements for a specific UTRAN implementation.
|
25.928
|
1,28 Mcps functionality for UTRA TDD physical layer
|
TR
|
4.0.1
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.928/25928-401.zip
|
The present document describes the 1.28Mcps functionality for UTRA TDD physical layer, identifies commonalties and explains the differences to the 3.84Mcps chip rate. Suggestions for alignment will be provided too.
|
25.934
|
AAL2 QoS optimization
|
TR
|
4.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.934/25934-400.zip
|
The present document clarifies:
• the issue to be improved under the work task,
• requirements for the solution from UTRAN transport network configuration point of view,
• solution to solve the issue,
• backward compatibility mechanism between Release 4 and Release 99 specifications for the solution, and
• what Change request is needed to reflect the solution to enhance Release 99 specifications to Release 4 specifications.
|
25.935
|
RRM optimisation
|
TR
|
4.1.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.935/25935-410.zip
| |
25.936
|
Handover for realtime services from PS-domain
|
TR
|
4.0.1
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.936/25936-401.zip
|
The purpose of the present document is to help the relevant 3GPP groups to specify the changes to existing specifications, needed for the introduction of the “Handover for real-time services from PS domain” Building Block for Release 2000.
The purpose of this R00 work task is to define the relocation procedure to be used when real time services are supported in the PS domain.
The intention with this work item is to provide support for services such as voice over IP and multimedia over IP.
This TR focuses on the requirements for the solution. Possible solutions have been further studied and they are also described in this TR for comparison and evaluation against the requirements. In doing this work, RAN3 has identified some areas of study that are not primarily under RAN3’s responsibility. These are mentioned here so that work can be coordinated with the other 3GPP groups.
Changes to the signalling protocols in UTRAN and CN interfaces have also been studied at a high level.
This document is a ‘living’ document, i.e. it is permanently updated and presented to all TSG-RAN meetings.
|
25.937
|
UTRAN TDD low chiprate
|
TR
|
4.1.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.937/25937-410.zip
|
The work item "Low chip rate TDD Iub/Iur protocol aspects" is a Building Block which has been agreed at TSG RAN#8 as described in contribution [1]. Its parent feature is "Low chip rate TDD" which has been agreed at TSG-RAN#6 and updated at RAN#7. The purpose of the work item "Low chip rate TDD Iub/Iur protocol aspects" is to update the Iub/Iur interface protocol specifications and related overview specifications in RAN WG3 in support of the several aspects of the feature "Low chip rate TDD".
The purpose of the present document is to help the TSG RAN WG3 group to specify the changes to existing specifications, needed for the introduction of the low chip rate TDD option in the UTRAN for Rel.4. It is intended to gather all information in order to trace the history and the status of the Work Task in RAN WG3. It is not intended to replace contributions and Change Requests, but only to list conclusions and make reference to agreed contributions and CRs. When solutions are sufficiently stable, the CRs can be issued.
It describes agreed requirements related to the Work Task, and split the Work Task into "Study Areas" in order to group contributions in a consistent way.
It identifies the affected specifications with related Change Requests.
It also describes the schedule of the Work Task.
The present document is a "living" document, i.e. it is permanently updated and presented to all TSG-RAN meetings.
|
25.944
|
Channel coding and multiplexing examples
|
TR
|
4.1.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.944/25944-410.zip
|
The present document describes examples of channel coding and multiplexing for physical channels of FDD mode and TDD mode.
|
25.946
|
RAB Quality of Service (QoS) Negotiation over Iu
|
TR
|
4.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.946/25946-400.zip
|
The present document gives a presentation of the current status of the Work Item “RAB Quality of Service Negotiation over Iu” within TSG RAN WG3.
It describes requirements, additional studies needed, and agreements reached so far for the Work Item.
It identifies the affected specifications.
It also describes the schedule of the Work Task.
If information needs to be communicated to groups outside of TSG RAN WG3, this is also indicated.
The document is a ‘living’ document, i.e. it is continuously updated and presented to all TSG-RAN meetings.
|
25.950
|
UTRA High Speed Downlink Packet Access (HSDPA)
|
TR
|
4.0.1
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.950/25950-401.zip
|
The present document describes several techniques, which facilitate high-speed downlink packet access. Furthermore, it describes how these concepts should be integrated into the overall architecture of UTRA. The techniques should be applicable to streaming, interactive and background services.
|
25.953
|
TrFO/TFO
|
TR
|
4.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.953/25953-400.zip
|
The present document provides the current status of the work item “Transcoder Free Operation” within 3GPP TSG RAN WG3.
The purpose of this Rel4 Work Task is to define necessary enhancements of specifications under RAN WG3 control to support the procedures specified within the parent Building Block “Out of Band Transcoder Control”.
|
25.954
|
Migration to modification procedure
|
TR
|
4.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.954/25954-400.zip
|
The present document clarifies:
• rational to introduce transport bearer modification procedure on Iub, Iur, and Iu,
• requirement for the solution of transport bearer modification,
• study area in order to introduce the modification procedure,
• way to solve the study area , and
• Change request needs to be given in order to enhance Release 99 specification to Release 4 specification for the work task.
|
26.901
|
Adaptive Multi-Rate Wideband (AMR-WB) speech codec; Feasibility study report
|
TR
|
4.0.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.901/26901-401.zip
|
The present document presents the outcome of the Feasibility Study Phase of wideband Adaptive Multi-rate codec. Clauses 4 to 6 provide an overview and background for introducing AMR wideband. Clause 7 provides a review of relevant standardization activities. Feasibility aspects such as codec performance, speech coding bit-rates, implementation complexity and transmission delay are discussed in clauses 8 and 9. Clause 10 outlines the target timeplan for AMR-WB codec development, testing, selection and standardization. Clauses 11, 12 and 13 conclude with a summary of the risks and recommendations.
|
26.912
|
Codec for Circuit switched Multimedia Telephony Service; Quantitative performance evaluation of H.324 Annex C over 3G
|
TR
|
4.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.912/26912-400.zip
|
The present document is meant to function as guidance in the work of other 3GPP work groups or work items. Such work may include conclusion on how to achieve detailed Stage 1 service requirements or suggestion of a set of recommended RAB parameters giving satisfactory user-to-user quality for a circuit switched multimedia service using 3G-324M.
|
27.903
|
Discussion of synchronization standards
|
TR
|
4.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/27_series/27.903/27903-400.zip
|
The present document provides information on existing synchronization protocols. It summarizes proprietary and standard protocols relevant to current and future mobile communication devices.
The present document covers only synchronization between end-user devices, desktop applications, and server-based information services. It does not refer to replication or synchronization between enterprise databases.
|
29.198-04
|
Open Service Access (OSA) Application Programming Interface (API); Part 4: Call control Service Capability Feature (SCF)
|
TS
|
4.11.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04/29198-04-4b0.zip
|
The present document is Part 4 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.127 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Call Control Service Capability Feature (SCF) aspects of the interface. All aspects of the Call Control SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CN WG5, ETSI TISPAN and The Parlay Group, in co-operation with a number of JAIN™ Community member companies.
|
31.110
|
Numbering system for telecommunication IC card applications
|
TS
|
4.1.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.110/31110-410.zip
|
The present document describes the numbering system for Application IDentifiers (AID) for 3G telecommunication Integrated Circuits (IC) card applications.
The numbering system described in the present document provides a means for an application and related services offered by a provider to identify if a given card contains the elements required by its application and related services.
An AID is used to address an application in the card. It consists of a Registered application provider IDentifier (RID) and a Proprietary application Identifier eXtension (PIX).
The present document describes the coding of the PIX.
|
33.103
|
3G security; Integration guidelines
|
TS
|
4.2.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.103/33103-420.zip
|
This technical specification defines how elements of the 3G-security architecture are to be integrated into the following entities of the system architecture.
- Home Environment Authentication Centre (HE/AuC)
- Serving Network Visited Location Register (VLR/SGSN)
- Radio Network Controller (RNC)
- Mobile station User Identity Module (UIM)
- Mobile Equipment (ME)
This specification is derived from 3G "Security architecture". [1]
The structure of this technical specification is a series of tables, which describe the security information and cryptographic functions to be stored in the above entities of the 3G system.
For security information, this is in terms of multiplicity, lifetime, parameter length and whether mandatory or optional.
For the cryptographic functions, the tables also include an indication of whether the implementation needs to be standardised or can be proprietary.
The equivalent information for the alternative Temporary Key proposal is included in an appendix to this document.
|
33.120
|
Security Objectives and Principles
|
TS
|
4.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.120/33120-400.zip
|
The present document gives the objectives and principles of 3GPP security.
The principles state what is to be provided by 3G security as compared to the security of second generation systems. The principles will also ensure that 3G security can secure the new services and new service environments offered by 3G systems.
The objectives give general, high level requirements for 3GPP security which will be expanded upon in 3G TS 21.133 [1].
The priorities for the implementation of 3GPP security are also given.
|
33.901
|
Criteria for cryptographic Algorithm design process
|
TR
|
4.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.901/33901-400.zip
|
This report discusses the possibilities for acquisition of the cryptographic algorithms that has to be standardised in UMTS. The focus is on the encryption function used in the data confidentiality mechanism and the message authentication function used in the signalling data integrity mechanism.
First certain aspects of the process and desired results for an algorithm specification and their pro's and cons will be given. These aspects will include the possible design strategies, the evaluation strategies, the possibilities for distribution of the algorithms and the options for the liability and responsibility for the algorithm.
Then a number of the most realistic scenarios for the algorithm specification will be presented. These scenarios will be used as a basis to make a final choice for the specification process for cryptographic algorithms in third generation mobile systems. Finally, a preferred procedure will be described.
|
33.902
|
Formal Analysis of the 3G Authentication Protocol
|
TR
|
4.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.902/33902-400.zip
|
This report contains formal analyses of the authentication and key agreement (AKA) protocol specified in 3G TS 33.102. These analyses are carried out using various means of formal logic suitable for demonstrating security and correctness properties of the AKA protocol.
The structure of this technical specification is as follows:
clause 2 lists the references used in this specification;
clause 3 lists the definitions and abbreviations used in this specification;
clause 4 refers to the main body of this report. The main body is only referred to because it is not available in Word-, but only in pdf-format. The corresponding .pdf-documents are attached to this document.
|
33.908
|
3G Security; General report on the design, specification and evaluation of 3GPP standard confidentiality and integrity algorithms
|
TR
|
4.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.908/33908-400.zip
|
This technical report is a description of the work undertaken by SAGE Task Force for the design of the standard 3GPP Confidentiality and Integrity Algorithms (SAGE TF 3GPP), and to formally approve the release of these algorithms to 3GPP.
With regard to the design of the algorithms, the scope of the present document is confined to a description of the design criteria, the design methodology and an outline of the content and structure of the specification and test data documents.
The standard 3GPP Confidentiality and Integrity Algorithms are based on a Block Cipher named KASUMI. The algorithms specification and associated test data are documented in the Specification of the 3GPP Confidentiality and Integrity Algorithms which consists of the following four documents:
- Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 1: f8 and f9 specifications (TS 35.201).
- Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 2: KASUMI algorithm specification (TS 35.202).
- Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 3: Implementors' test data (TS 35.203).
- Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 4: Design conformance test data (TS 35.204).
With regard to the evaluation of the algorithm, the scope of this report is restricted to a description of the evaluation criteria, the method of evaluation and the main conclusions from the evaluation that led to the Task Force approving the specification. A detailed summary of conclusions of the evaluation is provided in a public evaluation report [3] produced by the Task Force.
|
33.909
|
3G Security; Report on the design and evaluation of the MILENAGE algorithm set; Deliverable 5: An example algorithm for the 3GPP authentication and key generation functions
|
TR
|
4.0.1
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.909/33909-401.zip
|
This public report contains a detailed summary of the work performed during the design and evaluation of the 3GPP Authentication Functions denoted as the MILENAGE algorithm set. It contains all results and findings from this work and should be read as a supplement to the specifications of the algorithms in ref. [3] and the general project report, ref. [4].
|
41.061
|
General Packet Radio Service (GPRS); GPRS ciphering algorithm requirements
|
TS
|
4.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/41_series/41.061/41061-400.zip
|
This TS constitutes a requirements specification for a cryptographic algorithm which is used to protect General Packet Radio Services (GPRS) as specified by GSM 02.60.
This TS is intended to provide the ETSI Security Algorithms Group of Experts (SAGE) with the information it requires in order to design and deliver a technical specification for such an algorithm.
The specification covers the intended use of the algorithm and use of the algorithm specification, technical requirements on the algorithm, requirements on the algorithm specification and test data, and quality assurance requirements on both the algorithm and its documentation. The specification also outlines the background to the production of this specification.
|
42.009
|
Security aspects
|
TS
|
4.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/42_series/42.009/42009-410.zip
|
Bearer and Teleservices, as respectively defined in GSM 02.02 and GSM 02.03, are the objects which the GSM PLMN operators offer to their customers. Besides these basic telecommunications services, features which aim at up‑grading these basic services need also to be offered. Due to the use of radiocommunications in a PLMN, which are of a special nature compared to classical distribution transmission techniques used in the fixed networks, such a category of features is related to security aspects.
In a GSM PLMN, both the users and the network operator have to be protected against undesirable intrusion of third parties. However, measures should be provided for in order to insure maximum protection of the rights of the individuals concerns. As a consequence, a security feature is either a supplementary service to Tele or Bearer services, which can be selected by the subscriber, or a network function involved in the provision of one or several telecommunication services.
The purpose of the present document is to define the security features which are to be available in a GSM PLMN, together with the associated levels of protection. The present document is only concerned with those security features which aim at the up‑grading of the security in a GSM PLMN. In particular, end‑to‑end security is outside the scope of the present document.
The implementation aspects of security features are described in GSM 03.20.
|
42.017
|
Subscriber Identity Module (SIM); Functional characteristics
|
TS
|
4.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/42_series/42.017/42017-400.zip
|
The present document defines the functional characteristics and requirements of the Subscriber Identity Module (SIM) for use in Digital Cellular Telecommunications System (GSM) applications. All references to GSM shall apply equally to any band specified for GSM unless otherwise stated.
The SIM is the entity that contains the identity of the subscriber. When placed in a Mobile Equipment (ME), together they become a Mobile Station (MS) which may then register onto a GSM network.
The primary function of the SIM in conjunction with a GSM network is to authenticate the validity of an MS when accessing the network. In addition it provides a means to authenticate the user and may also store other subscriber-related information or applications. Subscription entitlements are stored not in the SIM, but in the network.
If the SIM functionality is incorporated into a multi-application card, the GSM application may be used in other telecommunication applications.
In addition, SIMs are permitted to contain non-GSM functionality. In the case of multi-application cards, the present document defines just the GSM application.
|
50.059
|
Enhanced Data rates for GSM Evolution (EDGE); Project scheduling and open issues for EDGE
|
TR
|
4.0.1
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/50_series/50.059/50059-401.zip
|
The purpose of the present document is to describe the schedules of the Enhanced Data rate for GSM Evolution (EDGE) standardisation process and to view it's current state and open issues that are still under discussion. It also lists the new standards and necessary amendments to the GSM/DCS phase 2+ specifications for the technical realisation of the function.
|
51.011
|
Specification of the Subscriber Identity Module - Mobile Equipment (SIM-ME) interface
|
TS
|
4.15.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/51_series/51.011/51011-4f0.zip
|
The present document defines the interface between the Subscriber Identity Module (SIM) and the Mobile Equipment (ME) for use during the network operation phase of GSM as well as those aspects of the internal organization of the SIM which are related to the network operation phase. This is to ensure interoperability between a SIM and an ME independently of the respective manufacturers and operators. The concept of a split of the Mobile Station (MS) into these elements as well as the distinction between the GSM network operation phase, which is also called GSM operations, and the administrative management phase are described in the 3GPP TS 42.017 [6]. The requirements for the physical characteristics of the SIM, the electrical signals and the transmission protocols are all defined in accordance with the 3GPP TS 31.101 [55] except when stated otherwise in the present document.
The present document defines:
‑ the model which shall be used as a basis for the design of the logical structure of the SIM;
‑ the security features;
‑ the interface functions;
‑ the commands;
‑ the contents of the files required for the GSM application;
‑ the application protocol.
The present document does not specify any aspects related to the administrative management phase. Any internal technical reallocation of either the SIM or the ME are only specified where these reflect over the interface. It does not specify any of the security algorithms which may be used.
The present document defines the SIM/ME interface for GSM Phase 2. While all attempts have been made to maintain phase compatibility, any issues that specifically relate to Phase 1 should be referenced from within the relevant Phase 1 specification.
|
51.014
|
Specification of the SIM Application Toolkit for the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface
|
TS
|
4.5.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/51_series/51.014/51014-450.zip
|
The present document defines the interface between the Subscriber Identity Module (SIM) and the Mobile Equipment (ME), and mandatory ME procedures, specifically for "SIM Application Toolkit".
The present document refers in its majority to the ETSI TS 102 223 [37] "Card Application Toolkit", which describes the generic aspects of application toolkits within the SIM.SIM Application Toolkit is a set of commands and procedures for use during the network operation phase of GSM, in addition to those defined in TS 51.011 [20].
Specifying the interface is to ensure interoperability between a SIM and an ME independently of the respective manufacturers and operators. The concept of a split of the Mobile Station (MS) into these elements as well as the distinction between the GSM network operation phase, which is also called GSM operations, and the administrative management phase are described in TS 42.017 [3].
The present document defines:
- the commands;
- the application protocol;
- the mandatory requirements on the SIMand ME for each procedure.
Unless otherwise stated, references to GSM also apply to DCS 1800.
The present document does not specify any aspects related to the administrative management phase. Any internal technical realization of either the SIMor the ME are only specified where these reflect over the interface. This standard does not specify any of the security algorithms which may be used.
Within the context of this document, the term "terminal" used in TS 102 223 [37] refers to the Mobile Equipment (ME).
Within the context of this document, the term "UICC" used in TS 102 223 [37] refers to the SIM card.
Within the context of this document, the term "NAA" used in TS 102 223 [37] refers to the SIM application.
|
51.017
|
Subscriber Identity Module (SIM) test specification
|
TS
|
4.2.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/51_series/51.017/51017-420.zip
|
The present document provides the Conformance Test Specification for the Subscriber Identity Module defined in 3GPP TS 51.011 [1], TS 11.012[8] and TS 11.018[9].
|
01.01
|
Technical Specifications and Technical Reports for a GERAN-based 3GPP system
|
TS
|
8.20.0
|
SP
|
https://www.3gpp.org/ftp/Specs/archive/01_series/01.01/0101-8k0.zip
|
The present document identifies the 3GPP system specifications for Release 1999. The specifications and reports of 3GPP Release 1999 have a major version number 3 (i.e. 3.x.y). The listed Specifications are required to build a system based on GERAN radio technology.
|
01.04
|
Abbreviations and acronyms
|
TR
|
8.0.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/01_series/01.04/0104-800.zip
|
This ETSI Technical Report (TR) provides the abbreviations and acronyms to be used throughout the GSM specifications.
All abbreviations are presented in the singular, but are equally applicable to the plural.
|
01.31
|
Fraud Information Gathering System (FIGS); Service requirements; Stage 0
|
TR
|
8.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/01_series/01.31/0131-800.zip
| |
01.33
|
Lawful Interception requirements for GSM
|
TR
|
8.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/01_series/01.33/0133-800.zip
| |
01.61
|
General Packet Radio Service (GPRS); GPRS ciphering algorithm requirements
|
TS
|
8.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/01_series/01.61/0161-800.zip
| |
02.09
|
Security aspects
|
TS
|
8.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.09/0209-810.zip
|
Bearer and Teleservices, as respectively defined in GSM 02.02 and GSM 02.03, are the objects which the GSM PLMN operators offer to their customers. Besides these basic telecommunications services, features which aim at up‑grading these basic services need also to be offered. Due to the use of radiocommunications in a PLMN, which are of a special nature compared to classical distribution transmission techniques used in the fixed networks, such a category of features is related to security aspects.
In a GSM PLMN, both the users and the network operator have to be protected against undesirable intrusion of third parties. However, measures should be provided for in order to insure maximum protection of the rights of the individuals concerns. As a consequence, a security feature is either a supplementary service to Tele or Bearer services, which can be selected by the subscriber, or a network function involved in the provision of one or several telecommunication services.
The purpose of the present document is to define the security features which are to be available in a GSM PLMN, together with the associated levels of protection. The present document is only concerned with those security features which aim at the up‑grading of the security in a GSM PLMN. In particular, end‑to‑end security is outside the scope of the present document.
The implementation aspects of security features are described in GSM 03.20.
|
02.17
|
Subscriber Identity Module (SIM); Functional characteristics
|
TS
|
8.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.17/0217-800.zip
|
The present document defines the functional characteristics and requirements of the Subscriber Identity Module (SIM) for use in Digital Cellular Telecommunications System (GSM) applications. All references to GSM shall apply equally to any band specified for GSM unless otherwise stated.
The SIM is the entity that contains the identity of the subscriber. When placed in a Mobile Equipment (ME), together they become a Mobile Station (MS) which may then register onto a GSM network.
The primary function of the SIM in conjunction with a GSM network is to authenticate the validity of an MS when accessing the network. In addition it provides a means to authenticate the user and may also store other subscriber-related information or applications. Subscription entitlements are stored not in the SIM, but in the network.
If the SIM functionality is incorporated into a multi-application card, the GSM application may be used in other telecommunication applications.
In addition, SIMs are permitted to contain non-GSM functionality. In the case of multi-application cards, the present document defines just the GSM application.
|
02.19
|
Subscriber Identity Module Application Programming Interface (SIM API); Stage 1
|
TS
|
8.1.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.19/0219-810.zip
|
This Technical Specification defines the stage one description of the Subscriber Identity Module Application Programming Interface (SIM API) internal to the SIM. Stage one is an overall service description, and does not deal with the implementation details of the API.
This TS includes information applicable to network operators, service providers and terminal, SIM, switch and database manufacturers.
This TS contains the core requirements which are sufficient to provide a complete service.
It is highly desirable however, that technical solutions for a SIM API should be sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in this TS may implement requirements which are considered outside the scope of this TS. This additional functionality may be on a network-wide basis, nation-wide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the core requirements of the service.
|
02.33
|
Lawful Interception (LI); Stage 1
|
TS
|
8.0.1
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.33/0233-801.zip
|
The present document provides the stage 1 description for a lawful interception function to be implemented in a given GSM PLMN in order for a network operator to be able to fulfil national lawful requirements. It shall be noted that national variation may exist but it is not the intention for the present document to encompass all of them. The purpose of the present document is to cover the options which may be selectable according to national regulations or as required by the GSM PLMN operator in co-operation with their suppliers.
In the preparation of the present document general reference was made to the European Union Council Resolution, January 1995: "International Requirements for the Lawful Interception of Telecommunications".
|
02.43
|
Support of Localised Service Area (SoLSA); Service description; Stage 1
|
TS
|
8.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.43/0243-800.zip
|
This technical specification, specifies a mechanism, which can be used as a platform for providing special tariffs and/or special set of service features for certain subscribers within a regionally restricted area or areas.
The motivation for this concept is to create means for network operators to build new service and tariff packages, which take into account subscriber groups and their needs.
The localised service area is both an optional network feature and an optional UE feature. Usage and implementation of the different SoLSA service features may vary according to operator's service packages.
This feature is not intended to replace the existing method of cell selection, cell indication and handover.
“Support of Localised service area (SoLSA)” is renamed Phase 2+ item “Support of Home Area Priority”
Note: The present document covers description for GERAN support only. UTRAN support will be added in latter releases.
|
02.48
|
Security mechanisms for the SIM Application Toolkit; Stage 1
|
TS
|
8.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.48/0248-800.zip
|
The present document provides standardised security mechanisms in conjunction with the SIM Application Toolkit for the interface between a GSM PLMN Entity and a SIM.
The security mechanisms which are specified are independent of applications.
The present document describes the functional requirements of the security mechanisms with the implementation detail of these mechanisms being described in the stage 2 specification (GSM 03.48).
The present document is the result of a feasibility study carried out on this topic, contained in GSM 11.15.
|
02.53
|
Tandem Free Operation (TFO); Service description; Stage 1
|
TS
|
8.0.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.53/0253-801.zip
|
The present document specifies the stage 1 description for the Tandem Free Operation (TFO) feature which provides the capability to avoid using two GSM speech codecs in mobile to mobile speech calls. The primary aim is to realise improvements in speech quality. The TFO mode of operation could also be used to reduce inter-Mobile services Switching Center (MSC) transmission bandwidth requirements.
In analogy with ITU-T Recommendations I.130 [1], Stage 1 is an overall service description, from the service subscriber's and user's standpoints, that views the network as a single entity which provides services to the user.
|
02.56
|
GSM Cordless Telephony System (CTS), Phase 1; Service description; Stage 1
|
TS
|
8.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.56/0256-801.zip
|
The scope of the present document is to describe the Service aspects of a GSM Cordless Telephony System (CTS), which provides the possibility for users of GSM terminals to have cordless access to a fixed network, such as PSTN/ISDN or a radio network such as GSM.
Due to the time constraints to have a first specification ready for market needs, a phased approach is necessary. The first phase aims primarily at an application supporting the speech teleservice (including DTMF support) in a residential single cell environment. The focus is on the requirements necessary to elaborate the radio interface and the security aspects for such an application.
To not prevent or impede the evolution of CTS to additional services and functions, later phases may have to be considered when now defining the means to fulfil the above mentioned requirements for the first phase of CTS. Therefore, additional support on the CTS radio interface for later phase services (e.g. SMS, subscriber authentication and GSM supplementary services), is included already in CTS Phase 1, provided that such services are clearly defined. Other expected services and functions in later phases are included in annex A.
The standardisation of the physical layers of the GSM-CTS fixed network interface is not in the scope of the present document. However, consideration may need to be given to communication of application data between CTS and PLMN via the fixed network.
|
02.68
|
Voice Group Call Service (VGCS); Stage 1
|
TS
|
8.2.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.68/0268-821.zip
|
The present document specifies the stage one description of the Voice Group Call Service (VGCS) which allows speech conversation of a predefined group of service subscribers in half duplex mode on the radio link taking into account multiple mobile service subscribers involved in the VGCS call per cell.
The VGCS is applicable to all mobile stations in a certain network and area which have the technical capability and the corresponding subscription, respectively, to participate in a VGCS call.
NOTE: It is not considered as requirement that normal GSM phase 2+ mobile stations will be able to be used for this service.
The service is described from the service subscriber's and user's point of view; in particular:
- the procedure for normal operation with successful outcome;
- the action to be taken in exceptional circumstances;
- the interaction with other GSM services and features.
The present document does not deal with the Man-Machine Interface (MMI) requirements, but makes reference to the appropriate Global System for Mobile Communications (GSM) specifications.
The present document defines a teleservice of the digital cellular telecommunications system GSM. Any interaction with other services and/or networks not dealt with in clauses 7 or 8 are outside the scope of the present document.
|
02.69
|
Voice Broadcast Service (VBS); Stage 1
|
TS
|
8.2.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.69/0269-820.zip
|
The present document specifies the stage one description of the Voice Broadcast Service (VBS) which allows the distribution of speech (or other signals which can be transmitted via the speech codec), generated by a service subscriber, into a predefined geographical area to all or a group of service subscribers located in this area.
The Voice Broadcast Service (VBS) is applicable to all mobile stations in a certain network and area which have the technical capability and the respective subscription to receive a VBS call.
NOTE: It is not considered as requirement that normal GSM Phase 2+ mobile stations will be able to be used for this service.
The service is described from the service subscriber's and user's point of view; in particular:
- the procedure for normal operation with successful outcome;
- the action to be taken in exceptional circumstances;
- the interaction with other GSM services and features.
The present document does not deal with the Man-Machine Interface (MMI) requirements, but makes reference to the appropriate Global System for Mobile communications (GSM) specifications.
The present document defines a teleservice of the digital cellular telecommunication system GSM. Any interaction with other services and/or networks not dealt within clauses 8 or 9 are outside the scope of the present document.
|
02.76
|
Noise Suppression for the AMR
|
TS
|
8.0.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.76/0276-801.zip
|
The present document specifies the stage 1 description for the Noise Suppression feature for the AMR codec which enhances the input speech signal corrupted by acoustic noise. In analogy with CCITT Recommendations I.130†[1], Stage 1 is an overall service description, from the service subscriber’s and user’s standpoints, that views the network as a single entity which provides services to the user.
|
02.95
|
Support of Private Numbering Plan (SPNP); Service description; Stage 1
|
TS
|
8.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.95/0295-800.zip
|
The present document specifies the stage 1 description of Support of Private Numbering Plan (SPNP), which enables a subscriber to use a Private Numbering Plan (PNP) for communication across one or more networks with mobile and fixed users. The subscriber may belong to one or more (up to 9 maximum) Private Numbering Plans. The subscriber may also, subject to subscription, have access to the Public Numbering Plan. The structure and content of each PNP are defined by a PNP Manager, although these are out of the scope of the present document.
The service is described from the service subscriber's and user's points of view; in particular:
- the procedures for normal operation with successful outcome;
- the action to be taken in exceptional circumstances;
- the interaction with other GSM supplementary services.
The present document does not deal with the Man-Machine Interface (MMI) requirements, but makes reference to the appropriate Global System for Mobile communications (GSM) specifications.
The charging principles applied to Support of Private Numbering Plan (SPNP) are outside of the scope of the present document.
Any interactions with other services and/or networks not dealt with in subclause 4.1 and clauses11 to 13 are outside the scope of the present document.
|
03.05
|
Technical performance objectives
|
TR
|
8.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.05/0305-800.zip
|
The present document contains technical performance objectives that should be met for the fixed infrastructure of GSM PLMNs. Concerning transmission delay for the PLMN in clause 4, the requirements should also be met by GSM Mobile Stations (MS)s.
These performance design objectives are applicable to all implementations at all points in the growth cycle up to the maximum size. These reference loads and performance objectives may be used by manufacturers in designing GSM PLMNs and by Administrations or Recognised Private Operating Agencies (RPOA)s in evaluating a specific design or for comparing different designs for potential use in the Administration's or RPOA's intended implementation.
|
03.10
|
GSM Public Land Mobile Network (PLMN) Connection Types
|
TS
|
8.3.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.10/0310-830.zip
|
A GSM PLMN may be described by a limited set of access interfaces (refer to 3GPP TS 04.02 and 02.01) and a limited set of GSM PLMN connection types to support the telecommunication services described in the 3GPP 02-series of specifications. This Global System for Mobile communications Technical Specification (TS) identifies and defines these connection types in so far as they relate to the particular network capabilities for a GSM PLMN.
The basic lower layer capabilities of a GSM PLMN are represented by a set of GSM PLMN connection types. The definition of a set of GSM PLMN connection types provides the necessary input to identify network capabilities of a GSM PLMN. In addition to describing network capabilities of a GSM PLMN, the identification of connection types facilitates the specification of network-to-network interfaces. It may also assist in the allocation of network performance parameters.
This specification should be considered in conjunction with other 3GPP specifications with particular reference to 3GPP TS 01.02, 02.01, 22.002, 02.03, 03.01, 23.002, 04.02 and 04.03.
This specification provides a bridge between the service specification in the 3GPP TS 02 and 22-series of specifications and the more detailed specifications such as the 3GPP TS 03, 04, 23, 24, 27 and 29 series. As such, it establishes a framework for the specification and understanding of the more detailed specifications. It is therefore not a specification against which detailed conformance testing can be performed. However, it shall be considered mandatory for the understanding of the more detailed specifications and used to resolve issues of conflict in these specifications.
From GSM R99 onwards the following services are no more required to be provided by a GSM PLMN:
• the dual Bearer Services “alternate speech/data” and “speech followed by data”
• the dedicated services for PAD and Packet access
• the single asynchronous and synchronous Bearer Services (BS 21..26, BS 31..34)
If a PLMN network still provides these services it has to fulfil the specification of GSM R98.
|
03.13
|
Discontinuous Reception (DRX) in the GSM System
|
TS
|
8.0.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.13/0313-800.zip
|
The present document provides a system wide view of the operation of discontinuous reception on the GSM system.
The support of DRX is mandatory in GSM PLMNs.
The detailed coding and procedural details are defined in the relevant Technical Specifications dealing with the specific interfaces that are involved, for instance GSM 08.08 and GSM 04.08. Reference is also made to the framing on the air interface which is defined in Technical Specification GSM 05.02.
The present document gives an overview of the implementation of discontinuous reception DRX within the GSM system, the actions required at MSC, BSS, and MS, the support of the facility via the air interface, and some operational aspects of the facility.
|
03.19
|
Subscriber Identity Module Application Programming Interface (SIM API) for Java Card
|
TS
|
8.5.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.19/0319-850.zip
|
The present document defines the stage two description of the Subscriber Identity Module Application Programming Interface (SIM API) internal to the SIM.
This stage two describes the functional capabilities and the information flow for the SIM API implemented on the Java Card 2.1 API specification [6].
The present document includes information applicable to network operators, service providers and SIM, server and database manufacturers.
|
03.20
|
Security-related network functions
|
TS
|
8.6.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.20/0320-860.zip
|
This Technical Specification specifies the network functions needed to provide the security related service and functions specified in GSM 02.09.
This specification does not address the cryptological algorithms that are needed to provide different security related features. This topic is addressed in annex C. Wherever a cryptological algorithm or mechanism is needed, this is signalled with a reference to annex C. The references refers only to functionalities, and some algorithms may be identical or use common hardware.
|
03.22
|
Functions related to Mobile Station (MS) in idle mode and group receive mode
|
TS
|
8.7.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.22/0322-870.zip
|
The present document gives an overview of the tasks undertaken by a GSM Mobile Station (MS) when in idle mode, that is, switched on but not having a dedicated channel allocated, e.g. not making or receiving a call, or when in group receive mode, that is, receiving a group call or broadcast call but not having a dedicated connection. It also describes the corresponding network functions. The idle mode functions are also performed by a GPRS MS as long as no dedicated channel is allocated to the MS. The idle mode functions are also performed by a CTS MS as long as the CTS MS is in manual mode GSM only or in automatic mode under PLMN coverage.
NOTE: The term GSM MS is used for any type of MS supporting one, or combinations, of the frequency bands specified in GSM 05.05.
The present document outlines how the requirements of the GSM 02 series Technical Specifications (especially GSM 02.11) on idle mode operation shall be implemented. Further details are given in GSM 04.08 and GSM 05.08.
Clause 2 of the present document gives a general description of the idle mode process. Clause 3 outlines the main requirements and technical solutions of those requirements. Clause 4 describes the processes used in idle mode. There is inevitably some overlap between these clauses. Clause 5 describes the cell change procedures for a MS in group receive mode.
1a References
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
[2] GSM 02.01: "Digital cellular telecommunications system (Phase 2+); Principles of telecommunications services supported by a GSM Public Land Mobile Network (PLMN)".
[3] GSM 02.02: "Digital cellular telecommunication system (Phase 2+); Bearer Services (BS) supported by a GSM Public Land Mobile Network (PLMN)".
[4] GSM 02.03: "Digital cellular telecommunications system (Phase 2+); Teleservices supported by a GSM Public Land Mobile Network (PLMN)".
[5] GSM 02.04: "Digital cellular telecommunications system (Phase 2+); General on supplementary services".
[6] GSM 02.06: "Digital cellular telecommunications system (Phase 2+); Types of Mobile Stations (MS)".
[7] GSM 02.07: "Digital cellular telecommunications system (Phase 2+); Mobile Station (MS) features".
[8] GSM 02.09: "Digital cellular telecommunications system (Phase 2+); Security aspects".
[9] GSM 02.11: "Digital cellular telecommunications system (Phase 2+); Service accessibility".
[10] GSM 02.16: "Digital cellular telecommunications system (Phase 2+); International Mobile station Equipment Identities (IMEI)".
[11] GSM 02.17: "Digital cellular telecommunications system (Phase 2+); Subscriber identity modules Functional characteristics".
[12] GSM 02.24: "Digital cellular telecommunications system (Phase 2+); Description of Charge Advice Information (CAI)".
[13] GSM 02.30: "Digital cellular telecommunications system (Phase 2+); Man‑Machine Interface (MMI) of the Mobile Station (MS)".
[14] GSM 02.40: "Digital cellular telecommunications system (Phase 2+); Procedures for call progress indications".
[15] GSM 02.41: "Digital cellular telecommunications system (Phase 2+); Operator determined barring".
[16] GSM 02.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services ‑ Stage 1".
[17] GSM 02.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services ‑ Stage 1".
[18] GSM 02.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 1".
[19] GSM 02.84: "Digital cellular telecommunications system (Phase 2+); MultiParty (MPTY) supplementary services ‑ Stage 1".
[20] GSM 02.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services ‑ Stage 1".
[21] GSM 02.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services ‑ Stage 1".
[22] GSM 02.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services ‑ Stage 1".
[23] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification".
[24] GSM 05.02: "Digital cellular telecommunications system (Phase 2+); Multiplexing and multiple access on the radio path".
[25] GSM 05.08: "Digital cellular telecommunications system (Phase 2+); Radio subsystem link control".
[26] GSM 02.60: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Service description Stage 1".
[27] GSM 03.60: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Service description Stage 2".
[28] GSM 03.64: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Overall description of the GPRS Radio Interface; Stage 2".
[29] GSM 02.56: "Digital cellular telecommunications system (Phase 2+); GSM Cordless Telephony System (CTS); Service Description; Stage 1.
[30] GSM 03.56: "Digital cellular telecommunications system (Phase 2+); GSM Cordless Telephony System (CTS); CTS Architecture Description; Stage 2.
[31] 3GPP TS 23.122: " Non-Access-Stratum functions related to Mobile Station (MS) in idle mode".
[32] 3GPP TS 24.008: " Mobile radio interface layer 3 specification; Core Network Protocols - Stage 3".
1b Definitions and abbreviations
Abbreviations used in the present document are listed in GSM 01.04.
Selected PLMN This is the PLMN that has been selected according to subclause 3.1, either manually or automatically.
Available PLMN This is a PLMN where the MS has found a cell that satisfies conditions (ii) and (iv) of subclause 3.2.1.
Home PLMN (HPLMN) See 3GPP TS 23.122.
Registered PLMN (RPLMN) This is the PLMN on which certain LR outcomes have occurred (see 3GPP TS 23.122).
Equivalent PLMN A PLMN contained in the stored list of equivalent PLMNs. These PLMNs are considered equivalent to the selected PLMN regarding PLMN selection, cell selection, cell re-selection and handover (see 3GPP TS 23.122).
Registration This is the process of camping on a cell of the PLMN and doing any necessary LRs.
Camped on a cell The MS (ME if there is no SIM) has completed the cell selection/reselection process and has chosen a cell from which it plans to receive all available services. Note that the services may be limited, and that the PLMN may not be aware of the existence of the MS (ME) within the chosen cell.
Current serving cell This is the cell on which the MS is camped.
Suitable Cell This is a cell on which an MS may camp. It must satisfy criteria defined in subclause 3.2.1. For an MS in group receive mode, the suitable cell is determined by the criteria defined in subclause 5.2.3.
Acceptable Cell This is a cell that the MS may camp on to make emergency calls. It must satisfy criteria defined in sub clause 3.2.2.
Group call A communication in which several MSs can receive, but at most one may be allowed to transmit on a radio channel. Examples of group calls are those established for the voice group call service (VGCS, see GSM 03.68).
Broadcast call A communication in which several MSs can receive, but only the originator of the call is allowed to transmit on the radio channel. Examples of the broadcast call are those established for the voice broadcast service (VBS, see GSM 03.69).
Group receive mode State of the MS when it is engaged in a group or broadcast call as a listener.
GPRS MS An MS capable of GPRS services is a GPRS MS.
CTS MS An MS capable of CTS services is a CTS MS.
Location Registration (LR) An MS which is IMSI attached to non-GPRS services only performs location registration by the Location Updating procedure. A GPRS MS which is IMSI attached to GPRS services or to GPRS and non-GPRS services performs location registration by the Routing Area Update procedure only when in a network of network operation mode I. Both procedures are performed independently by the GPRS MS when it is IMSI attached to GPRS and non-GPRS services in a network of network operation mode II or III (see GSM 03.60).
Localised Service Area (LSA) A localised service area consists of a cell or a number of cells. The cells constituting a LSA may not necessarily provide contiguous coverage.
SoLSA exclusive access Cells on which normal camping is allowed only for MS with Localised Service Area (LSA) subscription.
Registration Area A registration area is an area in which mobile stations may roam without a need to perform location registration. The registration area corresponds to location area (LA) for performing location updating procedure and it corresponds to routing area for performing the routing area update procedure.
The PLMN to which a cell belongs (PLMN identity) is given in the system information transmitted on the BCCH (MCC + MNC part of LAI).
|
03.26
|
Multiband operation of GSM/DCS 1800 by a single operator
|
TR
|
8.0.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.26/0326-800.zip
|
The purpose of the present document is to describe the functionality of a Multiband GSM/DCS Network operated by a single operator and the Multiband GSM/DCS Mobile Station (MS). It also describes the necessary amendments to the GSM/DCS phase 2 specifications for the technical realization of the function.
The resulting Amendment Requests (AR) and Change Requests (CR) necessary for Multiband Operation are listed in annex A.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.