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 |
|---|---|---|---|---|---|---|
25.430 | UTRAN Iub Interface: general aspects and principles | TS | 4.4.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.430/25430-440.zip | |
25.432 | UTRAN Iub interface: signalling transport | TS | 4.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.432/25432-400.zip | |
25.434 | UTRAN Iub interface data transport and transport signalling for Common Transport Channel data streams | TS | 4.4.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.434/25434-440.zip | |
25.431 | UTRAN Iub interface Layer 1 | TS | 4.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.431/25431-400.zip | |
25.435 | UTRAN Iub interface user plane protocols for Common Transport Channel data streams | TS | 4.6.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.435/25435-460.zip | |
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.442 | UTRAN implementation-specific O&M transport | TS | 4.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.442/25442-400.zip | |
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.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.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.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.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.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.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.921 | Guidelines and principles for protocol description and error handling | TR | 4.8.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.921/25921-480.zip | The present document provides a guideline for protocol specification of UMTS stage 2 and 3 including the usage of formal languages and rules for error handling. The present document covers control-plane and user-plane protocols specified in TSG-RAN such as RRC, RLC, RANAP, RNSAP, NBAP, PCAP, and SABP. |
25.922 | Radio resource management strategies | TR | 4.4.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.922/25922-440.zip | The present document shall describe RRM strategies supported by UTRAN specifications and typical algorithms.
This report is a release independent report. This means that the latest release applicable to 3GPP is the reference that this TR is defined upon, and contains information on all previous releases. Actual release where a given example applies is indicated in the relevant section. |
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.931 | UTRAN functions, examples on signalling procedures | TR | 4.5.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.931/25931-450.zip | |
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.935 | RRM optimisation | TR | 4.1.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.935/25935-410.zip | |
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.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.942 | Radio Frequency (RF) system scenarios | TR | 4.2.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.942/25942-420.zip | |
25.943 | Deployment aspects | TR | 4.2.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.943/25943-420.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.945 | RF requirements for low chip rate TDD option | TR | 4.2.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.945/25945-420.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.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.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.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. |
25.956 | Universal Terrestrial Radio Access (UTRA) repeater planning guidelines and system analysis | TR | 4.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.956/25956-400.zip | |
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.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.993 | Typical examples of Radio Access Bearers (RABs) and Radio Bearers (RBs) supported by Universal Terrestrial Radio Access (UTRA) | TR | 4.2.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.993/25993-420.zip | |
26.071 | Mandatory speech CODEC speech processing functions; AMR speech Codec; General description | TS | 4.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.071/26071-400.zip | |
26.073 | ANSI-C code for the Adaptive Multi Rate (AMR) speech codec | TS | 4.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.073/26073-410.zip | |
26.077 | Minimum performance requirements for Noise Suppresser; Application to the Adaptive Multi-Rate (AMR) speech encoder | TS | 4.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.077/26077-400.zip | |
26.090 | Mandatory Speech Codec speech processing functions; Adaptive Multi-Rate (AMR) speech codec; Transcoding functions | TS | 4.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.090/26090-400.zip | |
26.091 | Mandatory Speech Codec speech processing functions; Adaptive Multi-Rate (AMR) speech codec; Error concealment of lost frames | TS | 4.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.091/26091-400.zip | |
26.074 | Mandatory speech codec speech processing functions; Adaptive Multi-Rate (AMR) speech codec test sequences | TS | 4.0.1 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.074/26074-401.zip | |
26.094 | Mandatory speech codec speech processing functions; Adaptive Multi-Rate (AMR) speech codec; Voice Activity Detector (VAD) | TS | 4.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.094/26094-400.zip | |
26.092 | Mandatory speech codec speech processing functions; Adaptive Multi-Rate (AMR) speech codec; Comfort noise aspects | TS | 4.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.092/26092-400.zip | |
26.102 | Mandatory speech codec; Adaptive Multi-Rate (AMR) speech codec; Interface to Iu, Uu and Nb | TS | 4.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.102/26102-410.zip | |
26.110 | Codec for circuit switched multimedia telephony service; General description | TS | 4.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.110/26110-410.zip | |
26.104 | ANSI-C code for the floating-point Adaptive Multi-Rate (AMR) speech codec | TS | 4.5.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.104/26104-450.zip | |
26.115 | Echo control for speech and multimedia services | TS | 4.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.115/26115-400.zip | |
26.103 | Speech codec list for GSM and UMTS | TS | 4.4.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.103/26103-440.zip | |
26.101 | Mandatory speech codec speech processing functions; Adaptive Multi-Rate (AMR) speech codec frame structure | TS | 4.2.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.101/26101-420.zip | |
26.111 | Codec for circuit switched multimedia telephony service; Modifications to H.324 | TS | 4.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.111/26111-400.zip | |
26.131 | Terminal acoustic characteristics for telephony; Requirements | TS | 4.2.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.131/26131-420.zip | |
26.093 | Mandatory speech codec speech processing functions Adaptive Multi-Rate (AMR) speech codec; Source controlled rate operation | TS | 4.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.093/26093-400.zip | |
26.132 | Speech and video telephony terminal acoustic test specification | TS | 4.3.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.132/26132-430.zip | |
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.234 | Transparent end-to-end Packet-switched Streaming Service (PSS); Protocols and codecs | TS | 4.5.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.234/26234-450.zip | |
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.001 | General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS) | TS | 4.14.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.001/27001-4e0.zip | |
26.233 | Transparent end-to-end Packet-switched Streaming service (PSS); General description | TS | 4.2.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.233/26233-420.zip | The present document contains a general description of a transparent packet-switched streaming service in 3GPP-defined networks. In particular, it defines the usage scenarios, overall high-level end-to-end service concept, and lists terminal related functional components. It also lists any identified service interworking requirements. |
27.002 | Terminal Adaptation Functions (TAF) for services using asynchronous bearer capabilities | TS | 4.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.002/27002-400.zip | |
26.978 | Results of the Adaptive Multi-Rate (AMR) noise suppression selection phase | TR | 4.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.978/26978-400.zip | |
27.003 | Terminal Adaptation Functions (TAF) for services using synchronous bearer capabilities | TS | 4.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.003/27003-410.zip | |
26.975 | Performance characterization of the Adaptive Multi-Rate (AMR) speech codec | TR | 4.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.975/26975-410.zip | |
26.911 | Codec(s) for Circuit-Switched (CS) multimedia telephony service; Terminal implementor’s guide | TR | 4.2.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.911/26911-420.zip | |
27.005 | Use of Data Terminal Equipment - Data Circuit terminating Equipment (DTE - DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS) | TS | 4.2.1 | C1 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.005/27005-421.zip | |
27.007 | AT command set for User Equipment (UE) | TS | 4.7.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.007/27007-470.zip | |
27.103 | Wide Area Network Synchronization | TS | 4.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.103/27103-400.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 | 4.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.901/27901-410.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. |
27.010 | Terminal Equipment to User Equipment (TE-UE) multiplexer protocol | TS | 4.2.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.010/27010-420.zip | |
27.060 | Packet domain; Mobile Station (MS) supporting Packet Switched services | TS | 4.3.1 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.060/27060-431.zip | |
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.007 | General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN) | TS | 4.14.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.007/29007-4e0.zip | |
29.010 | Information element mapping between Mobile Station - Base Station System (MS - BSS) and Base Station System - Mobile-services Switching Centre (BSS - MSC); Signalling Procedures and the Mobile Application Part (MAP) | TS | 4.8.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.010/29010-480.zip | |
29.011 | Signalling Interworking for supplementary services | TS | 4.0.1 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.011/29011-401.zip | |
28.062 | Inband Tandem Free Operation (TFO) of speech codecs; Service description; Stage 3 | TS | 4.6.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.062/28062-460.zip | |
29.016 | General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface network service specification | TS | 4.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.016/29016-410.zip | |
29.060 | General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface | TS | 4.11.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.060/29060-4b0.zip | |
29.013 | Signalling interworking between ISDN supplementary services; Application Service Element (ASE) and Mobile Application Part (MAP) protocols | TS | 4.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.013/29013-410.zip | |
29.018 | General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification | TS | 4.5.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.018/29018-450.zip | |
29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | TS | 4.10.1 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.061/29061-4a1.zip | |
29.119 | GPRS Tunnelling Protocol (GTP) specification for Gateway Location Register (GLR) | TS | 4.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.119/29119-400.zip | |
29.120 | Mobile Application Part (MAP) specification for Gateway Location Register (GLR) | TS | 4.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.120/29120-400.zip | |
29.163 | Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks | TS | 1.9.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.163/29163-190.zip | The present document specifies the principles of interworking between the 3GPP IM CN subsystem and BICC/ISUP based legacy CS networks, in order to support IM basic voice, data and multimedia calls.
The present document addresses the areas of control and user plane interworking between the IM CN subsystem and CS networks through the network functions, which include the MGCF and IM-MGW. For the specification of control plane interworking, areas such as the interworking between SIP and BICC or ISUP are detailed in terms of the processes and protocol mappings required for the support of both IM originated and terminated voice and multimedia calls.
Other areas addressed encompass the transport protocol and signalling issues for negotiation and mapping of bearer capabilities and QoS information.
The present document specifies the interworking between 3GPP profile of SIP (as detailed according to 3GPP TS 24.229 [9]) and BICC or ISUP, as specified in ITU-T Recommendations Q.1902.1 to Q.1902.6 [30] and ITU-T Q761 to Q764 [4] respectively.
The present document also specifies the interworking between circuit switched multimedia telephony service, as described in 3GPP TS 26.110 [78] 3GPP TS 26.111 [79], and ITU-T Recommendation H.324 [81] and packet switched multimedia services, as described in 3GPP TS 26.114 [104], in particular and the interworking between the 3GPP profile of SIP and the inband control protocols for multimedia communication as specified in ITU-T Recommendations H.245 [82] and H.324 Annex K [81].
The present document addresses two interworking scenarios with respect to the properties of the CS network:
- The CS network does not use any 3GPP specific additions.
- The CS network uses 3GPP specific additions. |
29.198-01 | Open Service Access (OSA) Application Programming Interface (API); Part 1: Overview | TS | 4.3.8 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-01/29198-01-438.zip | The present document is the first part of the 3GPP Specification defining the Application Programming Interface (API) for Open Service Access (OSA), and provides an overview of the content and structure of the various parts of this specification, and of the relation to other standards documents.
The OSA-specifications define an architecture that enables service 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.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008. |
29.078 | Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase X; CAMEL Application Part (CAP) specification | TS | 4.9.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.078/29078-490.zip | The present document specifies the CAMEL Application Part (CAP) supporting the fourth phase of the network feature Customized Applications for Mobile network Enhanced Logic. CAP is based on a sub-set of the ETSI Core INAP CS-2 as specified by ETSI EN 301 140‑1 [26]. Descriptions and definitions provided by ETSI EN 301 140‑1 [26] are directly referenced by this standard in the case no additions or clarifications are needed for the use in the CAP. |
29.108 | Application of the Radio Access Network Application Part (RANAP) on the E-interface | TS | 4.4.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.108/29108-440.zip | |
29.198-02 | Open Service Access (OSA) Application Programming Interface (API); Part 2: Common data definitions | TS | 4.8.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-02/29198-02-480.zip | The present document is Part 2 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.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Common Data definitions of the OSA. The Common Data definitions contain data-types that are common across the rest of the OSA API. All aspects of the Common Data are defined here, these being:
- Data definitions;
- IDL Description of the data types;
- WSDL Description of the data types;
- Reference to the Java™ API description of the data types.
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008. |
29.198-05 | Open Service Access (OSA) Application Programming Interface (API); Part 5: User interaction Service Capability Feature (SCF) | TS | 4.10.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-05/29198-05-4a0.zip | This document is Part 5 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.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the User Interaction (UI) Service Capability Feature (SCF) aspects of the interface. All aspects of the User Interaction 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
• WSDL Description of the interfaces
• Reference to the Java™ API 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 CT WG5, ETSI TISPAN and The Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008. |
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. |
29.198-07 | Open Service Access (OSA) Application Programming Interface (API); Part 7: Terminal capabilities Service Capability Feature (SCF) | TS | 4.5.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-07/29198-07-450.zip | The present document is part 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.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Terminal Capabilities Service Capability Feature (SCF) aspects of the interface. All aspects of the Terminal Capabilities 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
• WSDL 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 CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies. |
29.198-08 | Open Service Access (OSA) Application Programming Interface (API); Part 8: Data session control Service Capability Feature (SCF) | TS | 4.9.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-08/29198-08-490.zip | The present document is Part 8 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.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Data Session Control Service Capability Feature (SCF) aspects of the interface. All aspects of the Data Session 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
• WSDL 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 CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008. |
29.198-11 | Open Service Access (OSA) Application Programming Interface (API); Part 11: Account management Service Capability Feature (SCF) | TS | 4.6.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-11/29198-11-460.zip | The present document is Part 11 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.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Account Management Service Capability Feature (SCF) aspects of the interface. All aspects of the Account Management 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
• WSDL 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 CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008. |
29.198-06 | Open Service Access (OSA) Application Programming Interface (API); Part 6: Mobility Service Capability Feature (SCF) | TS | 4.6.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-06/29198-06-460.zip | The present document is Part 6 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.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Mobility Service Capability Feature (SCF) aspects of the interface. All aspects of the Mobility 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
• WSDL Description of the interfaces
• Reference to the Java™ API 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 CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies. |
29.202 | Signalling System No. 7 (SS7) signalling transport in core network; Stage 3 | TS | 4.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.202/29202-430.zip | |
29.205 | Application of Q.1900 series to bearer independent Circuit Switched (CS) core network architecture; Stage 3 | TS | 4.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.205/29205-430.zip | |
29.198-03 | Open Service Access (OSA) Application Programming Interface (API); Part 3: Framework | TS | 4.9.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-03/29198-03-490.zip | The present document is Part 3 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.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Framework aspects of the interface. All aspects of the Framework are defined in the present document, these being:
• Sequence Diagrams;
• Class Diagrams;
• Interface specification plus detailed method descriptions;
• State Transition diagrams;
• Data definitions;
• IDL Description of the interfaces.
• WSDL Description of the interfaces
• Reference to the Java™ API 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 CT WG5, ETSI TISPAN and The Parlay Group, in co-operation with a number of JAIN™ Community member companies. |
29.198-12 | Open Service Access (OSA) Application Programming Interface (API); Part 12: Charging Service Capability Feature (SCF) | TS | 4.6.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-12/29198-12-460.zip | The present document is Part 12 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.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Charging Service Capability Feature (SCF) aspects of the interface. All aspects of the Charging 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
• WSDL Description of the interfaces
• Reference to the Java™ API 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 CT WG5, ETSI TISPAN and the Parlay Group, in co-operation a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008. |
29.998-01 | Open Service Access (OSA); Application Programming Interface (API) mapping for OSA; Part 1: General issues on API mapping | TR | 4.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-01/29998-01-400.zip | The present document is suggesting a mapping of the Application Programming Interface (API) for Open Service Access (OSA) onto CAMEL Application Part (CAP) operations and Mobile Application Part (MAP) operations, and provides an overview of the content and structure of the various parts of the present document. The mapping of the OSA API to the CAP and relevant MAP operations is considered informative and not normative.
The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2]. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.