id stringlengths 5 12 | title stringlengths 8 250 | type stringclasses 2
values | version stringclasses 560
values | working_group stringclasses 30
values | url stringlengths 67 81 | scope stringlengths 0 65.7k |
|---|---|---|---|---|---|---|
32.725 | Telecommunication management; Configuration Management (CM); Repeater network resources Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition | TS | 7.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.725/32725-710.zip | The present document provides the NRM-specific part related to the Repeater Network Resources IRP NRM [1] of the XML file format definition for the Bulk Configuration Management IRP IS [2].
The main part of this XML file format definition is provided by 3GPP TS 32.615 [3].
Bulk CM XML file formats are based on XML [4], XML Schema [5] [6] [7] and XML Namespace [8] standards.
This File Format Definition specification is related to 3GPP TS 32.722 V9.0.X. |
32.722 | Telecommunication management; Configuration Management (CM); Repeater network resources Integration Reference Point (IRP); information Service (IS) | TS | 7.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.722/32722-700.zip | The present document is part of an Integration Reference Point (IRP) named "Repeater Network Resources IRP", through which an "IRPAgent" (typically an Element Manager or Network Element) can communicate Configuration Management information to one or several "IRPManagers" (typically Network Managers) concerning Repeater resources. The "Repeater Network Resources IRP" comprises a set of specifications defining Requirements, a protocol neutral Network Resource Model (NRM) and corresponding Solution Set(s).
The present document specifies the protocol neutral Repeater Network Resources IRP: Network Resource Model.
It reuses relevant parts of the generic NRM in TS 32.622 [10] and 32.642 [5], either by direct reuse or sub-classing, and in addition to that defines Repeater specific Information Object Classes.
The Configuration Management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs – as described in the Introduction clause above. An important aspect of such a split is that the Network Resource Models (NRMs) defined in different IRPs containing NRMs are consistent, and that NRMs supported by an IRPAgent implementation can be accessed as one coherent model through one IRP Information Service (IS).
To summarize, the present document has the following main purpose: to define the applied Repeater specific NRM, based on the generic NRM in 3GPP TS 32.622 [10].
In order to access the information defined by this NRM, an IRP IS is needed, such as the Basic CM IRP IS (3GPP TS 32.602[11]) or the Bulk CM IRP IS (3GPP TS 32.612 [12]). However, which IS that is applicable is outside the scope of the present document. |
32.732 | Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 7.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.732/32732-730.zip | The present document is part of an Integration Reference Point (IRP) named IMS Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning IMS resources. The IMS NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the protocol neutral IMS NRM IRP: Information Service (IS). It reuses relevant parts of the Generic NRM IRP: IS in 3GPP TS 32.622 [9], either by direct reuse or sub-classing, and in addition to that defines IMS specific Information Object Classes.
Finally, in order to access the information defined by this NRM, an Interface IRP is needed, such as the Basic CM IRP in 3GPP TS 32.602 [10]. However, which Interface IRP that is applicable is outside the scope of the present document. |
32.731 | Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 7.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.731/32731-700.zip | The present document defines, in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: IMS Network Resource Model (NRM) IRP. |
32.721 | Telecommunication management; Configuration Management (CM); Repeater network resources Integration Reference Point (IRP); Requirements | TS | 7.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.721/32721-710.zip | The present document defines, in addition to the requirements defined in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2] and 3GPP TS 32.600 [3], the requirements for the present Repeater network resources IRP. |
32.735 | Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition | TS | 7.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.735/32735-750.zip | The present document provides the NRM-specific part related to the IMS NRM IRP [1] of the XML file format definition for the Bulk Configuration Management IRP IS [2].
The main part of this XML file format definition is provided by 3GPP TS 32.615 [3].
Bulk CM XML file formats are based on XML [4], XML Schema [5] [6] [7] and XML Namespace [8] standards.
This File Format Definition specification is related to 3GPP TS 32.732 V9.1.X. |
32.733 | Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 7.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.733/32733-730.zip | The purpose of this IMS NRM IRP: CORBA Solution Set is to define the mapping of the IRP Information Service (see TS 32.732 [3]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.732. |
32.742 | Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 7.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.742/32742-701.zip | The present document is part of an Integration Reference Point (IRP) named "Signalling Transport Network (STN) network resources IRP", through which an "IRPAgent" (typically an Element Manager or Network Element) can communicate Configuration Management information to one or several "IRPManagers" (typically Network Managers) concerning Signalling Transport resources. This IRP comprises a set of specifications defining Requirements, a protocol neutral Network Resource Model (NRM) and corresponding Solution Set(s).
The present document specifies the protocol neutral STN resources IRP NRM. It reuses relevant parts of the generic NRM in TS 32.622 [6], either by direct reuse or sub-classing, and in addition to that defines Signalling Transport specific Managed Object Classes.
The Configuration Management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs - as described in the Introduction clause above. An important aspect of such a split is that the NRMs defined in different IRPs containing NRMs are consistent, and that NRMs supported by an IRPAgent implementation can be accessed as one coherent model through one IRP Information Service (IS).
To summarize, the present document has the following main purpose: to define the applied Signalling Transport Network specific NRM, based on the generic NRM in 3GPP TS 32.622 [6].
In order to access the information defined by this NRM, an IRP IS is needed, such as the Basic CM IRP: IS (TS 32.602 [7]) or the Bulk CM IRP: IS (TS 32.612 [8]). However, which IS is applicable is outside the scope of this document.
Finally, regarding the support of the State Management IRP: IS (TS 32.672 [3]), all NRMs of one release shall support the same State Management IRP version. |
32.741 | Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 7.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.741/32741-710.zip | The present document defines , in addition to the requirements defined in [1], [2] and [3], the requirements for the Signalling Transport Network (STN) interface NRM IRP. |
32.745 | Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition | TS | 7.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.745/32745-710.zip | The present document provides the NRM-specific part related to the STN Network Resources IRP NRM in 32.742 [1] of the XML file format definition for the Bulk Configuration Management IRP IS (TS 32.612 [2]).
The main part of this XML file format definition is provided by 3GPP TS 32.615 [3].
Bulk CM XML file formats are based on XML [4], XML Schema [5] [6] [7] and XML Namespace [8] specifications.
This File Format Definition specification is related to 3GPP TS 32.742 V9.0.X. |
32.811 | Telecommunication management; Itf-N performance criteria: Requirements | TR | 7.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.811/32811-700.zip | The present document provides the overall performance criteria for all Integration Reference Point (IRP) specifications produced by 3GPP.
Relevant IRP overview and high-level definitions are provided in 3GPP TS 32.101 [1], 32.102 [2] and 32.150 [3]. |
32.812 | Telecommunication management; Itf-N Implementation Conformance Statement (ICS) template | TR | 7.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.812/32812-700.zip | The present document provides a template for Itf-N Implementation Conformance Statement (ICS) implementation conformance test. It defines the structure and table format for the ICS on the IS and CORBA SS level.
The intention is that:
a) For each IRP IS and CORBA SS specification version, for which an operator wishes to purchase an implementation of, a specific ICS document should be produced following the template herein (where each generic subclause number should be replaced by real numbers reflecting the structure in that IRP specification), and
b) For each Itf-N product offered or provided to support one or more IRP specifications, the vendor should fill in each applicable field of the tables in the ICS document(s) relevant for that/those IRP specifications and provide it to the customer. |
32.810 | Telecommunication management; Information model Integration Reference Point (IRP) Study | TR | 7.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.810/32810-700.zip | The present document is focused on studying IRP Information Modelling to increase the interoperability of IRP based systems. The documents comprising conceptual overview, business case, Use Cases and Requirements. The findings and proposals of the study may be used to help generate new Technical Specifications (TS) and/or enhance existing Technical Specifications. |
32.806 | Telecommunication management; Application guide for use of Integration Reference Points (IRPs) on peer-to-peer (p2p) interface | TR | 7.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.806/32806-700.zip | The present document shows how P2P horizontal interfaces can be added to the existing Telecommunication Management (TM) architecture and how existing Integration Reference Points (IRPs) can be applied to this architecture. |
32.809 | Telecommunication management; Feasibility study of XML-based (SOAP/HTTP) IRP solution sets | TR | 7.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.809/32809-700.zip | This present document is for the requested 3GPP Release 7 Work Item “XML-based (SOAP/HTTP) IRP Solution Set".
The purpose of the present document is to give TSG SA5 some arguments, through a survey work, about the need to specify a new Solution Set for all Interfaces, Network Resource Models and Data Definition IRPs based on XML-based (SOAP/HTTP) technology, as additional choice to CORBA and CMIP Solution Sets.
This document is intended to gather all information in order to provide a survey work on XML-based (SOAP/HTTP) Solution Set, based on the following sections:
(1) XML-based Solution Set technical introduction
(2) Business Status: Reasons
(3) Standardization Status
(4) Vendor Status
(4) Performance status:
(5) Economic Status |
33.105 | 3G Security; Cryptographic algorithm requirements | TS | 7.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.105/33105-700.zip | |
32.743 | Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 7.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.743/32743-720.zip | The present document maps the IRP information model in 32.742 [4] to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.742 V9.0.X. |
33.102 | 3G security; Security architecture | TS | 7.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.102/33102-710.zip | This specification defines the security architecture, i.e., the security features and the security mechanisms, for the third generation mobile telecommunication system.
A security feature is a service capability that meets one or several security requirements. The complete set of security features address the security requirements as they are defined in "3G Security: Threats and Requirements" (TS 21.133 [1]) and implement the security objectives and principles described in TS 33.120 [2]. A security mechanism is an element that is used to realise a security feature. All security features and security mechanisms taken together form the security architecture.
An example of a security feature is user data confidentiality. A security mechanism that may be used to implement that feature is a stream cipher using a derived cipher key.
This specification defines 3G security procedures performed within 3G capable networks (R99+), i.e. intra-UMTS and UMTS-GSM. As an example, UMTS authentication is applicable to UMTS radio access as well as GSM radio access provided that the serving network node and the MS are UMTS capable. Interoperability with non-UMTS capable networks (R98-) is also covered.
GSM security functions are defined in the TS 43.020 [36].
NOTE: The usage of the authentication management field (AMF) is specified in Annex H and applies for the third (UMTS), fourth (LTE) and fifth (5G system) generation of mobile telecommunication systems. |
33.106 | 3G security; Lawful interception requirements | TS | 7.0.1 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.106/33106-701.zip | |
33.107 | 3G security; Lawful interception architecture and functions | TS | 7.7.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.107/33107-770.zip | |
33.203 | 3G security; Access security for IP-based services | TS | 7.9.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.203/33203-790.zip | The scope for this technical specification is to specify the security features and mechanisms for secure access to the IM subsystem (IMS) for the 3G mobile telecommunication system.
Since the scope also encompasses the use of these security features and mechanisms for secure access to IMS in the context of fixed broadband networks and 3GPP2 networks, Annex L and Annex S specify how the material in the main body and other normative Annexes of this document apply to the fixed broadband networks and 3GPP2 networks respectively.
The IMS supports IP Multimedia applications such as video, audio and multimedia conferences. SIP, Session Initiation Protocol, was chosen as the signalling protocol for creating and terminating Multimedia sessions, cf. RFC 3261 [6]. This specification only deals with how the SIP signalling is protected between the subscriber and the IMS, how the subscriber is authenticated and how the subscriber authenticates the IMS. |
33.141 | Presence service; Security | TS | 7.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.141/33141-710.zip | |
33.108 | 3G security; Handover interface for Lawful Interception (LI) | TS | 7.10.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.108/33108-7a0.zip | The present document specifies the handover interfaces for Lawful Interception (LI) of Packet-Data Services, Circuit Switched Services, Multimedia Services within the UMTS network and Evolved Packet System (EPS). The handover interface in this context includes the delivery of Intercept Related Information (IRI) through the Handover Interface 2 (HI2) and Content of Communication (CC) through the Handover Interface 3 (HI3) to the Law Enforcement Monitoring Facility (LEMF). |
32.814 | Telecommunication management; UTRAN and GERAN Key Performance Indicators (KPI) | TR | 7.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.814/32814-700.zip | The present document details a proposal to create Key Performance Indicators for UTRAN and GERAN networks, using performance measurements defined in the 32.4xx series specifications (any exceptions are noted in the KPI definitions).
The KPIs detailed in sections 4 & 5 are an output from the CO-OP initiative (A co-operative effort by eight network equipment providers) [8].
The KPIs detailed in section 6 are an example of an alternative high level KPI definition method that does not rely on standardised counter definitions. A draft KPI template is also described.
The KPI definitions in this Technical Report are intended as input to 3GPP for information and further study in the possible creation of a 3GPP Technical Specification. |
33.110 | Key establishment between a Universal Integrated Circuit Card (UICC) and a terminal | TS | 7.5.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.110/33110-750.zip | |
33.220 | Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) | TS | 7.11.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.220/33220-7b0.zip | |
33.221 | Generic Authentication Architecture (GAA); Support for subscriber certificates | TS | 7.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.221/33221-710.zip | |
33.204 | 3G Security; Network Domain Security (NDS); Transaction Capabilities Application Part (TCAP) user security | TS | 7.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.204/33204-720.zip | |
33.234 | 3G security; Wireless Local Area Network (WLAN) interworking security | TS | 7.5.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.234/33234-750.zip | |
33.222 | Generic Authentication Architecture (GAA); Access to network application functions using Hypertext Transfer Protocol over Transport Layer Security (HTTPS) | TS | 7.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.222/33222-730.zip | |
33.259 | Key establishment between a UICC hosting device and a remote device | TS | 7.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.259/33259-720.zip | |
33.310 | Network Domain Security (NDS); Authentication Framework (AF) | TS | 7.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.310/33310-710.zip | |
33.210 | Network Domain Security (NDS); IP network layer security | TS | 7.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.210/33210-730.zip | |
33.246 | 3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS) | TS | 7.6.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.246/33246-760.zip | The Technical Specification covers the security procedures of the Multimedia Broadcast/Multicast Service (MBMS) for 3GPP systems (UTRAN, GERAN and E-UTRAN). MBMS is a 3GPP system network bearer service over which many different applications could be carried. The actual method of protection may vary depending on the type of MBMS application. |
33.803 | Coexistence between TISPAN and 3GPP authentication schemes | TR | 7.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.803/33803-700.zip | The present document studies from a security point of view the coexistence between TISPAN authentication methods (as specified in TISPAN release 1) and existing 3GPP authentication schemes, i.e. both the IMS AKA (as specified in TS 33.203 [5] and TS 24.229 [4]) and the early IMS security (as specified in TR 33.978 [6]). This document also aims to provide solutions to handle potential compatibility issues. These issues are listed in detail in section 5 of this document.
This document is meant to ensure that the same IMS core network entities can be used to support both 3GPP and TISPAN authentication schemes. In this context, rules are developed how an x‑CSCF can decide from a registration request which authentication scheme to apply. If these rules are not adhered to compatibility problems may arise. |
33.919 | 3G Security; Generic Authentication Architecture (GAA); System description | TR | 7.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.919/33919-720.zip | |
33.920 | SIM card based Generic Bootstrapping Architecture (GBA); Early implementation feature | TR | 7.5.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.920/33920-750.zip | The present document describes which change requests are to be implemented in addition to the Release 6 specifications TS 33.220 [1], TS 29.109 [2], and TS 24.109 [3] to enable the usage of 2G GBA. |
33.905 | Recommendations for Trusted Open Platforms | TR | 7.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.905/33905-700.zip | |
33.980 | Liberty Alliance and 3GPP security interworking; Interworking of Liberty Alliance Identity Federation Framework (ID-FF), Identity Web Services Framework (ID-WSF) and Generic Authentication Architecture (GAA) | TR | 7.6.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.980/33980-760.zip | |
33.978 | Security aspects of early IP Multimedia Subsystem (IMS) | TR | 7.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.978/33978-700.zip | The present document documents an interim security solution for early IMS implementations that are not fully compliant with the IMS security architecture specified in TS 33.203 [2]. For security reasons, the provisions in this TR only apply to IMS procedures used over the 3GPP PS domain. |
34.109 | Terminal logical test interface; Special conformance testing functions | TS | 7.4.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.109/34109-740.zip | |
34.114 | User Equipment (UE) / Mobile Station (MS) Over The Air (OTA) antenna performance; Conformance testing | TS | 7.0.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.114/34114-700.zip | The present document describes the test procedure for the radiated performances measurements of the 3G/2G user equipment/mobile stations (UE/MS) in active mode in both the uplink and the downlink. The FDD UE test procedure is based on the test method developed as a result of COST 273 Sub-Working Group (SWG) 2.2 members’ contributions. Background work has also been made in the former COST259 project. The TDD UE test procedure is based on the test method developed as a result of CCSA TC9 WG1 members’ contributions. Background work has been made in the former CCSA TC9 project.
The measurement procedure explained in this document applies to UE/MS used under the “speech mode” conditions that correspond to predefined positions for voice application when the handset is held close to the user’s head. This method is also applicable to free space measurements for UE/MS devices. The data transfer position (free space) explained in this document applies when the UE is used away from the user’s head. For LME and LEE devices free space configuration without head and hand phantoms is applicable. Free space measurements are applicable to devices used in the data transfer position that consist of the laptop mounted equipment (LME) plug-in UEs and laptop embedded equipment (LEE) UEs.
The tests apply to UEs and laptops using single or multiple receive antennas. For GSM technology this is applicable to all MSs and for 3G technology this is applicable to “one antenna” UEs and “RxDiversity” UEs.
The testing methodology applies to any single or multi-mode (GSM / UMTS / TD-SCDMA) terminals.
The radio tests considered here are:
1. The measurement of the Total Radiated Power (TRP)
2. The measurement of the Total Radiated Sensitivity (TRS)
The test procedure described in this document measures the performance of the transmitter and the receiver, including the antenna and also the effects of the user.
The major parts of this test procedure are based on the 3-D pattern measurement method. It has been considered necessary to define some items and components in the test procedure in detail, such as test channels and phantom set-ups, in order to make the testing in different laboratories harmonized. The procedure is, however, not limited to some specific antenna chambers or positioners. |
34.121-1 | User Equipment (UE) conformance specification; Radio transmission and reception (FDD); Part 1: Conformance specification | TS | 7.6.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.121-1/34121-1-760.zip | The present document specifies the UTRA measurement procedures for the conformance test of the user equipment (UE) that contain transmitting characteristics, receiving characteristics and performance requirements in addition to requirements for support of RRM (Radio Resource Management) in FDD mode. In addition it specifies conformance testing of RRM requirements for support of E-UTRA when the UE operates in UTRA mode.
NOTE: Conformance testing of RRM requirements for support of UTRA when the UE operates in E-UTRA mode are specified in TS 36.521-3 [38].
The requirements are listed in different clauses only if the corresponding parameters deviate. More generally, tests are only applicable to those mobiles that are intended to support the appropriate functionality. To indicate the circumstances in which tests apply, this is noted in the "definition and applicability" part of the test.
For example only Release 5 and later UE declared to support HSDPA shall be tested for this functionality. In the event that for some tests different conditions apply for different releases, this is indicated within the text of the test itself. |
34.122 | Terminal conformance specification; Radio transmission and reception (TDD) | TS | 7.6.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.122/34122-760.zip | This present document specifies the measurement procedure for the conformance test of the mobile station that contain transmitting characteristics, receiving characteristics and performance requirements in addition to requirements for support of RRM (Radio Resource Management) in both UTRATDD modes. The two options are the 3,84 Mcps TDD Option and 1,28 Mcps TDD Option, respectively.
The requirements are listed in different clauses only if the corresponding parameters deviate. More generally, tests are only applicable to those mobiles that are intended to support the appropriate functionality. To indicate the circumstances in which tests apply, this is noted in the “definition and applicability” part of the test.
For example only release 5 and later UE declared to support HSDPA shall be tested for this functionality. In the event that for some tests different conditions apply for different releases, this is indicated within the text of the test itself. |
34.123-1 | User Equipment (UE) conformance specification; Part 1: Protocol conformance specification | TS | 7.1.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.123-1/34123-1-710.zip | The present document specifies the protocol conformance testing for the 3rd Generation User Equipment (UE).
This is the first part of a multi-part test specification. The following information can be found in this part:
- the overall test structure;
- the test configurations;
- the conformance requirement and reference to the core specifications;
- the test purposes; and
- the description of the tests’ procedures, the specific test requirements and the messages exchanged.
The following information relevant to the tests described in the present document can be found in accompanying specifications:
- the default setting of the test parameters [9];
- the applicability of each test case and the Implementation Conformance Statement (ICS) pro-forma [11].
Note: The present document does not contain any tests on the USIM, or the interface between the UE and the USIM. These tests are documented elsewhere.
The present document is valid for UE implemented according to 3GPP releases starting from Release 1999 up to the Release indicated on the cover page of the present document. |
34.123-2 | User Equipment (UE) conformance specification; Part 2: Implementation conformance statement (ICS) proforma specification | TS | 7.1.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.123-2/34123-2-710.zip | The present document provides the Implementation Conformance Statement (ICS) proforma for 3rd Generation User Equipment (UE), in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646-7 [2] and ETS 300 406 [3].
The present document also specifies a recommended applicability statement for the test cases included in TS 34.123-1. These applicability statements are based on the features implemented in the UE.
Special conformance testing functions can be found in 3GPP TS 34.109 [45] and the common test environments are included in 3GPP TS 34.108 [44].
The present document is valid for UE implemented according to 3GPP releases starting from Release 1999 up to the Release indicated on the cover page of the present document. |
34.131 | Test Specification for C-language binding to (Universal) Subscriber Interface Module ((U)SIM) Application Programming Interface (API) | TS | 7.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.131/34131-700.zip | |
34.171 | Terminal conformance specification; Assisted Global Positioning System (A-GPS); Frequency Division Duplex (FDD) | TS | 7.2.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.171/34171-720.zip | The present document specifies the measurement procedures for the conformance test of the minimum performance requirements for FDD mode of UTRA user equipment (UE) where the only Assisted Global Navigation Satellite System (A-GNSS) supported is Assisted Global Positioning System (A-GPS) L1 C/A. The procedures for UEs that support other or additional A-GNSSs are specified in 3GPP TS 34.172 [18].
Tests are only applicable to those mobiles that are intended to support the appropriate functionality. To indicate the circumstances in which tests apply, this is noted in the "definition and applicability" part of the test. |
34.229-2 | Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE) conformance specification; Part 2: Implementation Conformance Statement (ICS) specification | TS | 7.3.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.229-2/34229-2-730.zip | |
34.229-3 | Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE) conformance specification; Part 3: Abstract test suite (ATS) | TS | 7.2.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.229-3/34229-3-720.zip | |
34.124 | Electromagnetic compatibility (EMC) requirements for mobile terminals and ancillary equipment | TS | 7.5.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.124/34124-750.zip | |
34.902 | Derivation of test tolerances for multi-cell Radio Resource Management (RRM) conformance tests | TR | 7.1.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.902/34902-710.zip | The present document specifies a method used to derive Test Tolerances for multi-cell Radio Resource Management tests, and establishes a system for relating the Test Tolerances to the measurement uncertainties of the Test System.
The present document is applicable to Release 99 up to the release indicated on the front page of the present Terminal conformance specifications. |
35.201 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 1: f8 and f9 specification | TS | 7.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.201/35201-700.zip | |
35.202 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 2: Kasumi specification | TS | 7.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.202/35202-700.zip | |
35.203 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 3: Implementors' test data | TS | 7.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.203/35203-700.zip | |
35.204 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 4: Design conformance test data | TS | 7.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.204/35204-700.zip | |
35.205 | 3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 1: General | TS | 7.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.205/35205-700.zip | This report is a description of the work undertaken by an ETSI SAGE Task Force on the design of the Milenage Algorithm Set: an example set of 3GPP Authentication and Key Generation Functions.
The 3GPP Authentication and Key Generation Functions are not standardized. An example set of these algorithms has been produced on request from 3GPP with the intent that it shall be offered to the UMTS operators, to utilise instead of developing their own. An ETSI SAGE Task Force has carried out this work.
The requirement specification from 3GPP stated that operator personalisation of the example set shall be possible and that the basic kernel shall be possible to replace.
The example set is based on the block cipher Rijndael, which at the time was one of the AES candidates and the specification describes how the 7 algorithms used in 3GPP authentication and key generation are scheduled around this basic kernel. The specification and associated test data for the example algorithm set is documented in three documents:
- A formal specification of both the modes and the example kernel [3]
- A detailed test data document, covering modes and the example kernel [4]
- A "black box" test data document [5]
A detailed summary of the evaluation is provided in a public evaluation report [6]
This report gives an overview of the overall work by the task force. |
35.206 | 3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 2: Algorithm specification | TS | 7.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.206/35206-700.zip | |
35.207 | 3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 3: Implementors' test data | TS | 7.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.207/35207-700.zip | |
35.208 | 3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 4: Design conformance test data | TS | 7.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.208/35208-700.zip | |
35.215 | Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 1: UEA2 and UIA2 specifications | TS | 7.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.215/35215-700.zip | |
35.216 | Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 2: SNOW 3G specification | TS | 7.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.216/35216-700.zip | |
35.217 | Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 3: Implementors' test data | TS | 7.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.217/35217-710.zip | |
35.218 | Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 4: Design conformance test data | TS | 7.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.218/35218-710.zip | |
35.909 | 3G Security; Specification of the MILENAGE algorithm set: an example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 5: Summary and results of design and evaluation | TR | 7.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.909/35909-700.zip | |
35.919 | Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 5: Design and evaluation report | TR | 7.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.919/35919-700.zip | |
34.926 | Electromagnetic compatibility (EMC); Table of international requirements for mobile terminals and ancillary equipment | TR | 7.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.926/34926-700.zip | |
41.033 | Lawful Interception requirements for GSM | TR | 7.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/41_series/41.033/41033-700.zip | This Technical Report describes the interface requirements of a mechanism which will deliver intercept from GSM mobile stations, including both speech and data product.
The stage 1 description of Lawful Interception will be specified in 3GPP TS 42.033.
The stage 2 description of Lawful Interception will be specified in 3GPP TS 43.033. |
41.101 | Technical Specifications and Technical Reports for a GERAN-based 3GPP system | TS | 7.4.0 | SP | https://www.3gpp.org/ftp/Specs/archive/41_series/41.101/41101-740.zip | |
42.033 | Lawful Interception; Stage 1 | TS | 7.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/42_series/42.033/42033-700.zip | This Technical Specification 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 this specification to encompass all of them. The purpose of this specification 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 this specification general reference was made to the European Union Council Resolution, January 1995: "International Requirements for the Lawful Interception of Telecommunications". |
34.121-2 | User Equipment (UE) conformance specification; Radio transmission and reception (FDD); Part 2: Implementation Conformance Statement (ICS) | TS | 7.6.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.121-2/34121-2-760.zip | The present document provides the Implementation Conformance Statement (ICS) proforma for 3rd Generation User Equipment (UE), in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646-7 [2] and ETS 300 406 [3].
The present document also specifies a recommended applicability statement for the test cases included in TS 34.121-1. These applicability statements are based on the features implemented in the UE.
Special conformance testing functions can be found in 3GPP TS 34.109 [19] and the common test environments are included in 3GPP TS 34.108 [18] and 3GPP TS 36.508 [29].
The present document is valid for UE implemented according to 3GPP releases starting from Release 99 up to the Release indicated on the cover page of the present document. |
34.108 | Common test environments for User Equipment (UE); Conformance testing | TS | 7.2.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.108/34108-720.zip | The present document contains definitions of reference conditions and test signals, default parameters, reference radio bearer configurations used in radio bearer interoperability testing, common radio bearer configurations for other test purposes, common requirements for test equipment and generic set-up procedures for use in UE conformance tests. |
42.043 | Support of Localised Service Area (SoLSA); Service description; Stage 1 | TS | 7.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/42_series/42.043/42043-700.zip | |
42.056 | GSM Cordless Telephony System (CTS), Phase 1; Service description; Stage 1 | TS | 7.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/42_series/42.056/42056-700.zip | |
33.918 | Generic Authentication Architecture (GAA); Early implementation of Hypertext Transfer Protocol over Transport Layer Security (HTTPS) connection between a Universal Integrated Circuit Card (UICC) and a Network Application Function (NAF) | TR | 7.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.918/33918-700.zip | The present document gives guidance on how to perform an early implementation of HTTPS connections between a UICC-based application and a Network Application Function in the Generic Authentication Architecture (GAA). |
42.068 | Voice Group Call Service (VGCS); Stage 1 | TS | 7.9.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/42_series/42.068/42068-790.zip | |
43.013 | Discontinuous Reception (DRX) in the GSM system | TS | 7.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.013/43013-700.zip | |
43.020 | Security related network functions | TS | 7.3.1 | S3 | https://www.3gpp.org/ftp/Specs/archive/43_series/43.020/43020-731.zip | |
43.022 | Functions related to Mobile Station (MS) in idle mode and group receive mode | TS | 7.2.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.022/43022-720.zip | |
43.026 | Multiband operation of GSM / DCS 1800 by a single operator | TR | 7.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.026/43026-700.zip | |
43.030 | Radio network planning aspects | TR | 7.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.030/43030-700.zip | |
43.033 | 3G security; Lawful Interception; Stage 2 | TS | 7.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/43_series/43.033/43033-700.zip | The present document gives the stage 2 description of Lawful Interception within a PLMN for circuit switched systems and GPRS. It does not address the interface between the PLMN and the LEA lawful intercepted product and related information collection functions. This is outside the scope of the GSM standard.
The structure of the present document is as follows:
- clause 4 covers the architecture of the interception system;
- clause 5 describes how interception is activated, deactivated and interrogated within the interception system;
- clause 6 describes how the system is provisioned, defines events at which interception takes place and what kind of information is generated at each event;
- clause 7 provides brief descriptions of various intercept cases;
- clause 8 reviews security requirements for access to the interception system;
- annex A provides information flows to illustrate when intercepted traffic and related data is generated;
- annex B describes an interception system for GPRS. The annex is subdivided into 5 sections that are identical in structure to clauses 4 through 8, but applicable to a GPRS clause rather than a GSM circuit switched system. |
43.045 | Technical realization of facsimile group 3 transparent | TS | 7.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/43_series/43.045/43045-700.zip | |
43.050 | Transmission planning aspects of the speech service in the GSM Public Land Mobile Network (PLMN) system | TS | 7.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/43_series/43.050/43050-710.zip | |
43.051 | GSM/EDGE Overall description; Stage 2 | TS | 7.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.051/43051-700.zip | |
43.052 | GSM Cordless Telephony System (CTS), Phase 1; Lower Layers of the CTS Radio Interface, Stage 2 | TS | 7.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.052/43052-700.zip | |
43.010 | GSM Public Land Mobile Network (PLMN) connection types | TS | 7.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/43_series/43.010/43010-700.zip | |
43.058 | Characterisation, test methods and quality assessment for handsfree Mobile Stations (MSs) | TR | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/43_series/43.058/43058-700.zip | |
42.069 | Voice Broadcast Service (VBS); Stage 1 | TS | 7.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/42_series/42.069/42069-700.zip | |
41.031 | Fraud Information Gathering System (FIGS); Service requirements; Stage 0 | TR | 7.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/41_series/41.031/41031-700.zip | |
43.055 | Dual Transfer Mode (DTM); Stage 2 | TS | 7.6.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.055/43055-760.zip | |
43.064 | General Packet Radio Service (GPRS); Overall description of the GPRS radio interface; Stage 2 | TS | 7.13.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.064/43064-7d0.zip | |
43.005 | Technical performance objectives | TS | 7.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.005/43005-700.zip | |
43.069 | Voice Broadcast Service (VBS); Stage 2 | TS | 7.7.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/43_series/43.069/43069-770.zip | |
43.073 | Support of Localised Service Area (SoLSA); Stage 2 | TS | 7.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/43_series/43.073/43073-700.zip | |
43.129 | Packet-switched handover for GERAN A/Gb mode; Stage 2 | TS | 7.3.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.129/43129-730.zip | |
43.068 | Voice Group Call Service (VGCS); Stage 2 | TS | 7.10.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/43_series/43.068/43068-7a0.zip | |
43.901 | Feasibility Study on generic access to A/Gb interface | TR | 7.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.901/43901-700.zip | |
43.902 | Enhanced Generic Access Networks (EGAN) study | TR | 7.0.1 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.902/43902-701.zip | |
44.001 | Mobile Station - Base Station System (MS - BSS) interface; General aspects and principles | TS | 7.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/44_series/44.001/44001-700.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.