id
stringlengths 4
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 612
values | working_group
stringclasses 30
values | url
stringlengths 65
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
24.559 | Application Data Analytics Enablement Service (ADAES); Stage 3 | TS | 18.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.559/24559-i10.zip | |
24.571 | 5G System (5GS); Control plane Location Services (LCS) procedures; Stage 3 | TS | 18.7.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.571/24571-i70.zip | |
24.572 | 5G System (5GS); User plane Location Services (LCS) protocols and procedures; Stage 3 | TS | 18.4.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.572/24572-i40.zip | |
24.575 | 5G System; Multicast/Broadcast UE pre-configuration Management Object (MO) | TS | 18.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.575/24575-i30.zip | The present document specifies UE pre-configuration for multicast/broadcast services (MBS) in order to receive the data of multicast communication services and broadcast communication services as specified in 3GPP TS 23.247 [3].
The present document defines a management object (MO) that can be used to configure the UE with parameters related to reception of data of multicast communication services and broadcast communication services.
The MO is compatible with the OMA Device Management (DM) protocol specifications, version 1.2 and upwards, and is defined using the OMA DM device description framework (DDF) as described in the Enabler Release Definition OMA-ERELD-DM-V1_2 [8].
The MO consists of nodes and leaves conveying UE pre-configuration parameters used for multicast communication service and broadcast communication service selection and data reception. |
24.577 | Aircraft-to-Everything (A2X) services in 5G System (5GS) protocol aspects; Stage 3 | TS | 18.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.577/24577-i20.zip | |
24.578 | Aircraft-to-Everything (A2X) services in 5G System (5GS); UE policies | TS | 18.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.578/24578-i10.zip | The present document defines User Equipment (UE) policies that are used to configure the UE for aircraft-to-Everything (A2X) services in 5G System (5GS) based on the architectural requirements defined in 3GPP TS 23.256 [2].
The protocol aspects for A2X services in 5G System (5GS) are described in 3GPP TS 24 577 [3]. |
24.581 | Mission Critical Video (MCVideo) media plane control; Protocol specification | TS | 18.5.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.581/24581-i50.zip | The present document specifies the media plane control and transmission control protocols and interactions with the media needed to support Mission Critical Video (MCVideo) service.
The MCVideo service and its associated media plane control protocols can be used for public safety applications and also for general commercial applications (e.g., utility companies and railways).
The present document is applicable to User Equipment (UE) supporting MCVideo client, and MCVideo server supporting media distribution function and transmission control server. |
24.582 | Mission Critical Data (MCData) media plane control; Protocol specification | TS | 18.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.582/24582-i20.zip | The present document specifies the media plane control protocols and interactions with the media needed to support Mission Critical Data (MCData) services, which are IP Connectivity, Short Data Service (SDS) and File Distribution (FD).
Mission critical communication services are services that require preferential handling compared to normal telecommunication services, e.g. in support of police or fire brigade.
The MCData service and its associated media plane control protocols can be used for public safety applications and also for general commercial applications (e.g., utility companies and railways).
The present document is applicable to User Equipment (UE) supporting MCData client functionality and to servers in the MCData system. |
24.583 | Application layer support for Personal IoT Network (PINAPP); Stage 3 | TS | 18.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.583/24583-i10.zip | The present document specifies the protocols and the associated procedures for application layer support for Personal IoT Network (PINAPP) as specified in 3GPP TS 23.542 [2] for:
a) PIN application communication among PIN peers (over the PIN-2, PIN-3, and PIN-4 interfaces); and
b) PIN application communication between the PIN peer and the PIN server (over the PIN-6, PIN-7, and PIN-10 interfaces).
The present specification also defines the message format, message contents, error handling and system parameters applied by the protocols for PINAPP.
NOTE: PIN-5 interface is out of the scope of the present document. |
24.587 | Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3 | TS | 18.8.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.587/24587-i80.zip | |
24.588 | Vehicle-to-Everything (V2X) services in 5G System (5GS); User Equipment (UE) policies; Stage 3 | TS | 18.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.588/24588-i30.zip | The present document defines User Equipment (UE) policies that are used to configure the UE for Vehicle-to-Everything (V2X) services in 5G System (5GS) based on the architectural requirements defined in 3GPP TS 23.287 [2].
The protocol aspects for V2X services in 5G System (5GS) are described in 3GPP TS 24.587 [3]. |
24.604 | Communication Diversion (CDIV) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.604/24604-i00.zip | The present document specifies the stage 3, Protocol Description of the Communications Diversion (CDIV) supplementary services, based on stage one and two of the ISDN Communication diversion supplementary services. It provides the protocol details in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP).
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to support the CDIV supplementary service. |
24.605 | Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.605/24605-i00.zip | The present document specifies the stage three Protocol Description of the Conference (CONF) service based on stage one and two of the ISDN CONF supplementary service. It provides the protocol details in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP).
The present document specifies centralized conferencing, using a conference focus, distributed conferencing is out of scope.
The present document does not cover the cases of :
a) cascading conference services; and
b) the support of the PSTN/ISDN conference service hosted in the PSTN.
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to support the CONF supplementary service. |
24.606 | Message Waiting Indication (MWI) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.606/24606-i00.zip | The present document specifies the stage three Protocol Description of the Message Waiting Indication (MWI) service, based on stage one and two of the ISDN MWI supplementary services. It provides the protocol details in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP).
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to support the MWI supplementary service. |
24.607 | Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.607/24607-i00.zip | The present document specifies the stage three (protocol description) of the Originating Identification Presentation (OIP) supplementary service and the Originating Identification Restriction (OIR) supplementary services, based on stage one and two of the ISDN CLIP [4] and CLIR [5] supplementary service. It provides the protocol details in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP).
NOTE: It can be noted that the behaviour described in this the present document does not take into account other behaviours that is specified in other applications and care needs to be taken when designing the filters etc. when two or more applications are involved in a session. |
24.608 | Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.608/24608-i00.zip | The present document specifies the stage three protocol description of the Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) services, based on stage one and two of the ISDN COLP [3] and COLR [4] supplementary services. It provides the protocol details in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP). |
24.610 | Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.610/24610-i00.zip | The present document specifies the stage three Protocol Description of the Communication Hold (HOLD) services, based on stages one and two of the ISDN Hold (HOLD) supplementary services. It provides the protocol details in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP).
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to support the HOLD supplementary service. |
24.611 | Anonymous Communication Rejection (ACR) and Communication Barring (CB) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.611/24611-i00.zip | The present document specifies the stage three, Protocol Description of the Anonymous Communication Rejection (ACR) and Communication Barring (CB) supplementary service, based on stage one and two of the ISDN supplementary service Anonymous Call Rejection (ACR), Incoming Communication Barring (ICB) and Outgoing Communication Barring (OCB). It provides the protocol details in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP).
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to support the ACR and CB supplementary services. |
24.615 | Communication Waiting (CW) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol Specification | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.615/24615-i00.zip | The present document specifies the stage 3, Protocol Description of the Communication Waiting (CW) service, based on stage 1 and stage 2 of the ISDN call waiting supplementary services. It provides the protocol details in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP).
The Communication Waiting (CW) service enables a user to be informed, that very limited resources are available for an incoming communication. The user then has the choice of accepting, rejecting or ignoring the waiting call (as per basic call procedures).
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to support the CW supplementary service. |
24.616 | Malicious Communication Identification (MCID) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.616/24616-i00.zip | The present document specifies the stage three Protocol Description of the Malicious Call Communication Identification (MCID) service based on the stage one and two of ISDN Malicious Call Identification supplementary service. It provides the protocol details in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP). The MCID service will store session related information independent of the service requested.
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to support the MCID supplementary service. |
24.623 | Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating Supplementary Services | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.623/24623-i00.zip | The present document defines a protocol used for manipulating data related to supplementary services. The protocol is based on the eXtensible Markup Language (XML) Configuration Access Protocol (XCAP) RFC 4825 [8]. A new XCAP application usage is defined for the purpose of manipulating the supplementary services data. The common XCAP related aspects that are applicable to supplementary services are specified in the present document. The protocol allows authorized users to manipulate service‑related data either when they are connected to IMS or when they are connected to non‑IMS networks (e.g. the public Internet).
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to support XCAP application usage for manipulating data related to supplementary services. |
24.628 | Common Basic Communication procedures using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.628/24628-i00.zip | The present document describes the stage three protocol for basic communication procedures common to several services in the IP Multimedia (IM) Core Network (CN) subsystem when at least one Application Server (AS) is included in the communication. The common procedures are based on stage three specifications for supplementary services.
The present document contains examples of signalling flows for the common basic communication procedures.
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to support the common basic communication procedures. |
24.629 | Explicit Communication Transfer (ECT) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.629/24629-i00.zip | The present document specifies the stage three (protocol description) of the Explicit Communication transfer (ECT) supplementary service, based on stage one and two of the ISDN ECT supplementary service. It provides the protocol details in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP).
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to support the ECT supplementary service. |
24.642 | Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.642/24642-i00.zip | The present document specifies the stage three Protocol Description of the Completion of Communications to Busy Subscriber (CCBS) service, the Completion of Communications on no Reply (CCNR) service, and Completion of Communications on not Logged-in (CCNL) service, based on stage one and two of the ISDN supplementary services. It provides the protocol details in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP).
The Completion of Communications to Busy Subscriber CCBS service enables user A, encountering a busy destination B, to have the communication completed without having to make a new communication attempt when the destination B becomes not busy.
The Completion of Communications on No Reply CCNR supplementary service enables user A, encountering a destination B which does not answer the communication (No Reply), to have the communication completed without having to make a new communication attempt when the destination becomes not busy after having initiated an activity.
The Completion of Communications on Not Logged-in CCNL supplementary service enables user A, encountering a destination B which is not registered with the IMS network, to have the communication completed without having to make a new communication attempt when the destination becomes registered.
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to support the CCBS and CCNR supplementary services. |
24.647 | Advice Of Charge (AOC) using IP Multimedia (IM) Core Network (CN) subsystem | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.647/24647-i00.zip | The present document specifies the stage three Protocol Description of the Advice Of Charge (AOC) service, based on stage 1 and 2 of the ISDN Supplementary Service Advice Of Charge for all calls (permanent mode). It provides the protocol details in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP).
Three AOC services exist:
a) Charging information at communication set-up time (AOC-S)
The AOC-S service enables a user to receive information about the charging rates at communication set-up time and also to receive further information during the communication if there is a change of charging rates.
b) Charging information during the communication (AOC-D)
The AOC-D service enables a user to receive information on the recorded charges for a communication during the active phase of the communication.
c) Charging information at the end of the communication (AOC-E)
The AOC-E service enables a user to receive information on the recorded charges for a communication when the communication is terminated.
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to support the AOC supplementary services. |
24.654 | Closed User Group (CUG) using IP Multimedia (IM) Core Network (CN) subsystem, Protocol Specification | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.654/24654-i00.zip | The present document specifies the stage three Protocol Description of the Closed User Group (CUG) service, based on stage one and two of the ISDN Communication diversion supplementary services. It provides the protocol details in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP).
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to support the CUG supplementary service. |
24.930 | Signalling flows for the session setup in the IP Multimedia core network Subsystem (IMS) based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 | TR | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.930/24930-i00.zip | The present document gives examples of the session setup in the IM CN subsystem based on SIP and SDP.
These signalling flows provide detailed signalling flows, which expand on the overview information flows provided in 3GPP TS 23.228 [2]. The flows focus on a basic session setup, i.e. no flows will be provided for topology hiding, for sessions with IBCF involved or for sessions having certain features. |
24.969 | Business trunking; Next Generation Corporate Network (NGCN) - Next Generation Network (NGN) interfaces implementation guide | TR | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.969/24969-i00.zip | The purpose of the present document is to give an implementation guide to the relevant Common IMS specifications and functions used in the interconnection of a Next Generation Corporate Network site (NGCN site) to the NGN.
The present document addresses control plane signalling (usage of SIP and SDP protocols, required SIP headers) as well as other interconnecting aspects like security, numbering/naming/addressing and user plane issues such as transport protocol, media and codecs actually covered in a widespread set of 3GPP and ETSI TISPAN specifications, as seen from the perspective of an NGCN site.
Advice-of-charge aspects are addressed as far as SIP signalling is concerned.
The present document is based on 3GPP TS 24.229 [12]. |
25.101 | User Equipment (UE) radio transmission and reception (FDD) | TS | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.101/25101-i00.zip | The present document establishes the minimum RF characteristics of the FDD mode of UTRA for the User Equipment (UE). |
25.102 | User Equipment (UE) radio transmission and reception (TDD) | TS | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.102/25102-i00.zip | This document establishes the minimum RF characteristics of all three options of the TDD mode of UTRA. The three options are the 3.84 Mcps, 1.28 Mcps and 7.68 Mcps options respectively. The requirements are listed in different subsections only if the parameters deviate. |
25.104 | Base Station (BS) radio transmission and reception (FDD) | TS | 18.0.1 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.104/25104-i01.zip | This document establishes the Base Station minimum RF characteristics of the FDD mode of UTRA. |
25.105 | Base Station (BS) radio transmission and reception (TDD) | TS | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.105/25105-i00.zip | This document establishes the minimum RF characteristics of all three options of the TDD mode of UTRA. The three options are the 3.84 Mcps, 1.28 Mcps and 7.68 Mcps options respectively. The requirements are listed in different subsections only if the parameters deviate. |
25.106 | UTRA repeater radio transmission and reception | TS | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.106/25106-i00.zip | The present document establishes the minimum radio frequency performance of UTRA FDD repeaters. |
25.111 | Location Measurement Unit (LMU) performance specification; User Equipment (UE) positioning in UTRAN | TS | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.111/25111-i00.zip | The present document establishes the Location Measurement Unit (LMU) minimum RF characteristics of the FDD mode of UTRA. |
25.113 | Base station (BS) and repeater electromagnetic compatibility (EMC) | TS | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.113/25113-i00.zip | The present document covers the assessment of base stations, repeaters and associated ancillary equipment in respect of Electromagnetic Compatibility (EMC).
The present document specifies the applicable test conditions, performance assessment and performance criteria for base stations, repeaters and associated ancillary equipment in one of the following categories:
- base stations for the FDD mode of UTRA meeting the requirements of TS 25.104 [1], with conformance demonstrated by compliance to TS 25.141 [3].
- base stations for both options of the TDD mode of UTRA meeting the requirements of TS 25.105 [2], with conformance demonstrated by compliance to TS 25.142 [4]. The two options are the 3,84 Mcps and 1,28 Mcps options respectively. The requirements are listed in different subsections only if the parameters deviate.
- repeaters for the FDD mode of UTRA meeting the requirements of TS 25.106 [10], with conformance demonstrated by compliance to TS 25.143 [11].
Technical requirements related to the antenna port of base stations or repeaters are not included in the present document. These are found in the relevant product standards [1], [2], [3], [4], [10], [11].
The environment classification used in the present document refers to the residential, commercial and light industrial environment classification used in IEC 61000-6-1 [5] and IEC 61000-6-3 [6].
The EMC requirements have been selected to ensure an adequate level of compatibility for apparatus at residential, commercial and light industrial environments. The levels, however, do not cover extreme cases which may occur in any location but with low probability of occurrence. |
25.116 | UTRA repeater radio transmission and reception (LCR TDD) | TS | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.116/25116-i00.zip | The present document establishes the minimum RF characteristics of LCR TDD Repeater. |
25.123 | Requirements for support of radio resource management (TDD) | TS | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.123/25123-i00.zip | This Technical Specification specifies requirements for support of Radio Resource Management for TDD. These requirements include requirements on measurements in UTRAN and the UE as well as requirements on node dynamic behaviour and interaction, in terms of delay and response characteristics. |
25.133 | Requirements for support of radio resource management (FDD) | TS | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.133/25133-i00.zip | The present document specifies requirements for support of Radio Resource Management for FDD. These requirements include requirements on measurements in UTRAN and the UE as well as requirements on node dynamical behaviour and interaction, in terms of delay and response characteristics. |
25.141 | Base Station (BS) conformance testing (FDD) | TS | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.141/25141-i00.zip | The present document specifies the Radio Frequency (RF) test methods and conformance requirements for UTRA Base Stations (BS) operating in the FDD mode. These have been derived from, and are consistent with the UTRA Base Station (BS) specifications defined in [1].
The present document establishes the minimum RF characteristics of the FDD mode of UTRA for the Base Station (BS). |
25.142 | Base Station (BS) conformance testing (TDD) | TS | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.142/25142-i00.zip | The present document specifies the Radio Frequency (RF) test methods and conformance requirements for UTRA Base Stations (BS) operating in the TDD mode. These have been derived from, and are consistent with, the UTRA base station (BS) specifications defined in 3GPP TS 25.105 [1]. The document covers all three options of the TDD mode, which are the 3,84 Mcps (incorporating MBSFN IMB), the 1,28 Mcps and the 7.68 Mcps options respectively. The requirements are listed in different subsections only if the parameters deviate.
In this TS, the reference point for RF connections (except for the measurement of mean transmitted RF carrier power) is the antenna connector, as defined by the manufacturer. This TS does not apply to repeaters or RF devices which may be connected to an antenna connector of a BS. |
25.143 | UTRA repeater conformance testing | TS | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.143/25143-i00.zip | The present document specifies the Radio Frequency (RF) test methods and Minimum Requirements for UTRA FDD Repeaters. These have been derived from, and are consistent with the UTRA FDD Repeater specifications defined in TS 25.106.
This document establishes the minimum RF characteristics of the UTRA FDD Repeater. |
25.153 | UTRA repeater conformance testing (LCR TDD) | TS | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.153/25153-i00.zip | The present document specifies the Radio Frequency (RF) test methods and Minimum Requirements for LCR TDD Repeaters. These have been derived from, and are consistent with the LCR TDD Repeater specifications defined in TS 25.116.
This document establishes the minimum RF characteristics of the LCR TDD Repeater. |
25.171 | Requirements for support of Assisted Global Positioning System (A-GPS); Frequency Division Duplex (FDD) | TS | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.171/25171-i00.zip | The present document establishes the minimum performance requirements for A-GPS for FDD mode of UTRA for the User Equipment (UE). |
25.172 | Requirements for support of Assisted Galileo and Additional Navigation Satellite Systems (A-GANSS) Frequency Division Duplex (FDD) | TS | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.172/25172-i00.zip | The present document establishes the minimum performance requirements for A-GANSS for FDD mode of UTRA for the User Equipment (UE) that supports A-GANSS. It includes the minimum performance requirements for both UE‑based and UE‑assisted A‑GANSS. The minimum performance requirements also include combinations of A-GPS and A-GANSS. |
25.173 | Requirements for support of Assisted Galileo and Additional Navigation Satellite Systems (A-GANSS) Time Division Duplex (TDD) | TS | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.173/25173-i00.zip | The present document establishes the minimum performance requirements for A-GANSS for TDD mode of UTRA for the User Equipment (UE) that supports A-GANSS. It includes the minimum performance requirements for both UE‑based and UE‑assisted A‑GANSS. The minimum performance requirements also include combinations of A-GPS and A-GANSS. |
25.201 | Physical layer - general description | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.201/25201-i00.zip | The present document describes a general description of the physical layer of the UTRA radio interface. The present document also describes the document structure of the 3GPP physical layer specifications, i.e. TS 25.200 series. The TS 25.200 series specifies the Uu point for the 3G mobile system, and defines the minimum level of specifications required for basic connections in terms of mutual connectivity and compatibility. |
25.202 | 7.68 Mcps Time Division Duplex (TDD) option; Overall description: Stage 2 | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.202/25202-i00.zip | The present document is the overall technical specification for the support of the 7.68Mcps TDD option in UTRA. |
25.211 | Physical channels and mapping of transport channels onto physical channels (FDD) | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.211/25211-i00.zip | The present document describes the characteristics of the Layer 1 transport channels and physicals channels in the FDD mode of UTRA. The main objectives of the document are to be a part of the full description of the UTRA Layer 1, and to serve as a basis for the drafting of the actual technical specification (TS). |
25.212 | Multiplexing and channel coding (FDD) | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.212/25212-i00.zip | The present document describes the characteristics of the Layer 1 multiplexing and channel coding in the FDD mode of UTRA. |
25.213 | Spreading and modulation (FDD) | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.213/25213-i00.zip | The present document describes spreading and modulation for UTRA Physical Layer FDD mode. |
25.214 | Physical layer procedures (FDD) | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.214/25214-i00.zip | The present document specifies and establishes the characteristics of the physicals layer procedures in the FDD mode of UTRA. |
25.215 | Physical layer; Measurements (FDD) | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.215/25215-i00.zip | The present document contains the description and definition of the measurements for FDD done at the UE and network in order to support operation in idle mode and connected mode. |
25.221 | Physical channels and mapping of transport channels onto physical channels (TDD) | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.221/25221-i00.zip | The present document describes the characteristics of the physicals channels and the mapping of the transport channels to physical channels in the TDD mode of UTRA. |
25.222 | Multiplexing and channel coding (TDD) | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.222/25222-i00.zip | The present document describes multiplexing, channel coding and interleaving for UTRA Physical Layer TDD mode. |
25.223 | Spreading and modulation (TDD) | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.223/25223-i00.zip | The present document describes spreading and modulation for UTRA Physical Layer TDD mode. |
25.224 | Physical layer procedures (TDD) | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.224/25224-i00.zip | The present document describes the Physical Layer Procedures in the TDD mode of UTRA. |
25.225 | Physical layer; Measurements (TDD) | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.225/25225-i00.zip | The present document contains the description and definition of the measurements done at the UE and network in TDD mode in order to support operation in idle mode and connected mode. |
25.300 | Universal Terrestrial Radio Access Network (UTRAN); General description; Stage 2 | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.300/25300-i00.zip | The present document provides an overview and overall description of the UTRA radio interface functionalities from Release 12 onwards which are not covered by the Technical Specifications TS 25.308 [2] or TS 25.319 [3]. |
25.301 | Radio interface protocol architecture | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.301/25301-i00.zip | The present document shall provide an overview and overall description of the UE-UTRAN radio interface protocol architecture as agreed within the 3GPP TSG RAN working group 2. Details of the radio protocols will be specified in companion documents. |
25.302 | Services provided by the physical layer | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.302/25302-i00.zip | The present document is a technical specification of the services provided by the physical layer of UTRA to upper layers. |
25.303 | Interlayer procedures in Connected Mode | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.303/25303-i00.zip | The present document describes all procedures that assign, reconfigure and release radio resources. Included are e.g. procedures for transitions between different states and substates, handovers and measurement reports. The emphasis is on showing the combined usage of both peer-to-peer messages and interlayer primitives to illustrate the functional split between the layers, as well as the combination of elementary procedures for selected examples. The peer-to-peer elementary procedure descriptions and interlayer dependencies are described in the related protocol descriptions /1, 2, 3/ and they are thus not within the scope of the present document.
The interlayer procedures and interlayer dependencies in the present document are informative. |
25.304 | User Equipment (UE) procedures in idle mode and procedures for cell reselection in connected mode | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.304/25304-i00.zip | The present document specifies the Access Stratum (AS) part of the Idle Mode procedures applicable to a UE. The non-access stratum (NAS) part of Idle mode procedures and processes is specified in [5].
The present document also specifies cell selection and reselection processes applicable to UEs in connected mode. Invocation of these processes is described in [4].
The present document specifies the model for the functional division between the NAS and AS in a UE.
The present document applies to all UEs that support at least UTRA, including multi-RAT UEs as described in 3GPP specifications, in the following cases:
- When the UE is camped on a UTRA cell;
- When the UE is searching for a cell to camp on;
NOTE: The details for those cases are described in the specifications of the other RAT.
The present document presents also examples of inter-layer procedures related to the idle mode processes and describes idle mode functionality of a multi-RAT UTRA/GSM/E-UTRA UE.
The present document also specifies how idle-mode and reselection procedures are affected by the provision of MBMS services. |
25.305 | Stage 2 functional specification of User Equipment (UE) positioning in UTRAN | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.305/25305-i00.zip | The present document specifies the stage 2 of the UE Positioning function of UTRAN, which provides the mechanisms to support the calculation of the geographical position of a UE. UE position knowledge can be used for example in support of Radio Resource Management functions, location-based services for operators, subscribers and third party service providers. The purpose of this stage 2 specification is to define the UTRAN UE Positioning architecture, functional entities and operations to support positioning methods. This description is confined to the UTRAN Access Stratum. It does not define nor describe how the results of the UE position calculation can be utilised in the Core Network (e.g. LCS) or in UTRAN (e.g. RRM).
UE Positioning may be considered as a network provided enabling technology consisting of standardised service capabilities, which enable the provision of location applications. The application(s) may be service provider specific. The description of the numerous and varied possible location applications which are enabled by this technology are outside the scope of the present document. However, clarifying examples of how the functionality being described may be used to provide specific location services may be included.
This stage 2 specification covers the UTRAN positioning methods, state descriptions, and message flows to support UE Positioning. |
25.306 | UE Radio Access capabilities | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.306/25306-i00.zip | The present document identifies the parameters of the access stratum part of the UE radio access capabilities. Furthermore, some reference configurations of these values are defined. The intention is that these configurations will be used for test specifications. |
25.307 | Requirements on User Equipments (UEs) supporting a release-independent frequency band | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.307/25307-i00.zip | The present document specifies requirements on UEs supporting a frequency band that is independent of release. |
25.308 | High Speed Downlink Packet Access (HSDPA); Overall description; Stage 2 | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.308/25308-i00.zip | The present document is a technical specification of the overall support of High Speed Downlink Packet Access in UTRA. |
25.319 | Enhanced uplink; Overall description; Stage 2 | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.319/25319-i00.zip | The present document is a technical specification of the overall support of FDD, TDD Enhanced Uplink in UTRA. |
25.321 | Medium Access Control (MAC) protocol specification | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.321/25321-i00.zip | The present document specifies the MAC protocol.
The specification describes:
- MAC architecture;
- MAC entities;
- channel structure;
- services provided to upper layers;
- MAC functions;
- services expected from the physical layer;
- elements for layer-to-layer communication including primitives between MAC and RLC;
- elements for peer-to-peer communication;
- protocol data units, formats and parameters;
- elementary procedures. |
25.322 | Radio Link Control (RLC) protocol specification | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.322/25322-i00.zip | The present document specifies the Radio Link Control protocol for the UE-UTRAN radio interface.
Features for the current Release:
- Transparent mode.
- Unacknowledged mode.
- Acknowledged mode. |
25.323 | Packet Data Convergence Protocol (PDCP) specification | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.323/25323-i00.zip | The present document provides the description of the Packet Data Convergence Protocol (PDCP). |
25.324 | Broadcast/Multicast Control (BMC) | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.324/25324-i00.zip | The present document provides the description of the Broadcast/Multicast Control Protocol (BMC). This protocol adapts broadcast and multicast services on the radio interface. |
25.327 | High Speed Packet Access (HSPA); Requirements on User Equipments (UEs) supporting a release-independent frequency band and multi-carrier configuration | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.327/25327-i00.zip | The present document specifies requirements on UEs supporting a DB-DC-HSDPA, 4C-HSDPA, and 8C-HSDPA configuration that is independent of release. TSG-RAN has agreed that the standardisation of new configurations may be independent of a release. However, in order to implement a UE that conforms to a particular release but supports a configuration that is specified in a later release, it is necessary to specify some extra requirements.
For example, Band I-XI combination for DB-DC-HSDPA (referred to as DB-DC-HSDPA configuration 4 in [2]) is contained in the Release 10 specifications. In order to implement a UE conforming to Release 9 but supporting this configuration, it is necessary for the UE to additionally conform to some parts of the Release 10 specifications, such as the radio frequency and radio resource management requirements for the configuration.
Similarly, 4C-HSDPA configuration I-3 is contained in the Release 11 specification [3]. In order to implement a UE conforming to Release 10, but supporting this configuration, it is necessary for the UE to additionally conform to some parts of the Release 11 specifications. |
25.331 | Radio Resource Control (RRC); Protocol specification | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.331/25331-i00.zip | The present document specifies the Radio Resource Control protocol for the UE-UTRAN radio interface.
The scope of the present document also includes:
- the information to be transported in a transparent container between source RNC and target RNC in connection with SRNC relocation;
- the information to be transported in a transparent container between a target RNC and another system. |
25.346 | Introduction of the Multimedia Broadcast/Multicast Service (MBMS) in the Radio Access Network (RAN); Stage 2 | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.346/25346-i00.zip | The present document is a technical specification of the overall support of Multimedia Broadcast Multicast Service in UTRA. |
25.367 | Mobility procedures for Home Node B (HNB); Overall description; Stage 2 | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.367/25367-i00.zip | This document provides a high level description of the mobility procedures applicable to Home NodeB support in the current Release. Where appropriate, the reasons behind the agreements are provided. Throughout this document, unless otherwise stated, the UE is assumed to be a current Release UE that supports the Closed Subscriber Group (CSG) feature, whether it is actually a member of a CSG or not. A UE that does not support the CSG feature is not required to support any of the procedures stated in this document. |
25.401 | UTRAN overall description | TS | 18.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.401/25401-i00.zip | The present document describes the overall architecture of the UTRAN, including internal interfaces and assumptions on the radio and Iu interfaces. |
25.402 | Synchronisation in UTRAN Stage 2 | TS | 18.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.402/25402-i00.zip | The present document constitutes the stage 2 specification of different synchronisation mechanisms in UTRAN and on Uu. |
25.410 | UTRAN Iu interface: General aspects and principles | TS | 18.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.410/25410-i00.zip | The present document is an introduction to the 3GPP TS 25.41x series of Technical Specifications that define the Iu interface for the interconnection of Radio Network Controller (RNC) component of the UMTS Terrestrial Radio Access Network (UTRAN) to the Core Network of the UMTS system. |
25.411 | UTRAN Iu interface layer 1 | TS | 18.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.411/25411-i00.zip | The present document specifies the standards allowed to implement Layer 1 on the Iu interface.
The specification of transmission delay requirements and O&M requirements are not in the scope of the present document.
In the following ‘Layer 1’ and ‘Physical Layer’ are assumed to be synonymous. |
25.412 | UTRAN Iu interface signalling transport | TS | 18.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.412/25412-i00.zip | The present document specifies the standards for Signalling Transport to be used across Iu Interface. Iu Interface is a logical interface between the RNC and the UTRAN Core Network. The present document describes how the RANAP signalling messages are transported over Iu. |
25.413 | UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling | TS | 18.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.413/25413-i00.zip | The present document specifies the radio network layer signalling protocol called Radio Access Network Application Part (RANAP) for the Iu interface. RANAP supports the functions of Iu interface by signalling procedures defined in this document. RANAP is developed in accordance to the general principles stated in TR 23.930 [1], TS 25.410 [2] and TS 25.401 [3]. |
25.414 | UTRAN Iu interface data transport and transport signalling | TS | 18.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.414/25414-i00.zip | The present document specifies the standards for user data transport protocols and related signalling protocols to establish user plane transport bearers over the UTRAN Iu interface. |
25.415 | UTRAN Iu interface user plane protocols | TS | 18.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.415/25415-i00.zip | The present document defines the Radio Network Layer user plane protocol being used over the Iu interface. |
25.419 | UTRAN Iu-BC interface: Service Area Broadcast Protocol (SABP) | TS | 18.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.419/25419-i00.zip | The present document specifies the Service Area Broadcast Protocol (SABP) between the Cell Broadcast Centre (CBC) and the Radio Network Controller (RNC). It fulfils the CBC - RNC communication requirements specified in TS 23.041 [5] and is defined over the Iu-BC – reference point. |
25.420 | UTRAN Iur interface general aspects and principles | TS | 18.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.420/25420-i00.zip | The present document is an introduction to the TSG RAN TS 25.42x series of UMTS Technical Specifications that define the Iur Interface. It is a logical interface for the interconnection of two Radio Network Controller (RNC) components of the UMTS Terrestrial Radio Access Network (UTRAN) for the UMTS system. |
25.421 | UTRAN Iur interface layer 1 | TS | 18.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.421/25421-i00.zip | The present document specifies the standards allowed to implement Layer 1 on the Iur interface. The specification of transmission delay requirements and O&M requirements are not in the scope of this document.
In the following ‘Layer 1’ and ‘Physical Layer’ are assumed to be synonymous. |
25.422 | UTRAN Iur interface signalling transport | TS | 18.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.422/25422-i00.zip | The present document specifies the standards for Signalling Transport to be used across Iur Interface. Iur Interface is a logical interface between the two RNC of the UMTS Terrestrial Radio Access Network (UTRAN) for the UMTS system. The present document describes how the RNSAP signalling messages are transported between the two RNCs. |
25.423 | UTRAN Iur interface Radio Network Subsystem Application Part (RNSAP) signalling | TS | 18.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.423/25423-i00.zip | The present document specifies the radio network layer signalling procedures of the control plane between RNCs in UTRAN, between RNC in UTRAN and BSS in GERAN Iu mode and between BSSs in GERAN Iu mode. |
25.424 | UTRAN Iur interface data transport & transport signalling for Common Transport Channel data streams | TS | 18.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.424/25424-i00.zip | The present document shall provide a specification of the UTRAN RNC-RNC (Iur) interface Data Transport and Transport Signalling for Common Transport Channel data streams. |
25.425 | UTRAN Iur interface user plane protocols for Common Transport Channel data streams | TS | 18.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.425/25425-i00.zip | The present document shall provide a description of the UTRAN RNS-RNS (Iur) interface user plane protocols for Common Transport Channel data streams as agreed within the TSG-RAN working group 3. |
25.426 | UTRAN Iur and Iub interface data transport & transport signalling for DCH data streams | TS | 18.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.426/25426-i00.zip | The present document specifies the transport bearers for the DCH/E-DCH data streams on UTRAN Iur and Iub interfaces. The corresponding Transport Network Control plane is also specified. The physical layer for the transport bearers is outside the scope of the present document. |
25.427 | UTRAN Iub/Iur interface user plane protocol for DCH data streams | TS | 18.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.427/25427-i00.zip | The present document shall provide a description of the UTRAN Iur and Iub interfaces user plane protocols for Dedicated Transport Channel data streams as agreed within the TSG-RAN working group 3. |
25.430 | UTRAN Iub Interface: general aspects and principles | TS | 18.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.430/25430-i00.zip | The present document is an introduction to the TSG RAN TS 25.43x series of UMTS Technical Specifications that define the Iub Interface. The Iub interface is a logical interface for the interconnection of Node B and Radio Network Controller (RNC) components of the UMTS Terrestrial Radio Access Network (UTRAN) for the UMTS system. |
25.431 | UTRAN Iub interface Layer 1 | TS | 18.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.431/25431-i00.zip | The present document specifies the standards allowed to implement Layer 1 on the Iub interface.
The specification of transmission delay requirements and O&M requirements is not in the scope of this document.
In the following ‘Layer 1’ and ‘Physical Layer’ are assumed to be synonymous. |
25.432 | UTRAN Iub interface: signalling transport | TS | 18.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.432/25432-i00.zip | The present document specifies the signalling transport related to NBAP signalling to be used across the Iub Interface. The Iub interface is a logical interface for the interconnection of Node B and Radio Network Controller (RNC) components of the UMTS Terrestrial Radio Access Network (UTRAN) for the UMTS system. The radio network control signalling between these nodes is based on the Node B application part (NBAP). |
25.433 | UTRAN Iub interface Node B Application Part (NBAP) signalling | TS | 18.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.433/25433-i00.zip | The present document specifies the radio network layer signalling protocol called Node B Application Part (NBAP) specification to be used for Control Plane over Iub Interface. |
25.434 | UTRAN Iub interface data transport and transport signalling for Common Transport Channel data streams | TS | 18.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.434/25434-i00.zip | The present document shall provide a specification of the UTRAN RNC-Node B (Iub) interface Data Transport and Transport Signalling for Common Transport Channel data streams. |
25.435 | UTRAN Iub interface user plane protocols for Common Transport Channel data streams | TS | 18.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.435/25435-i00.zip | The present document provides a description of the UTRAN RNC-Node B (Iub) interface user plane protocols for Common Transport Channel data streams as agreed within the TSG-RAN working group 3.
NOTE: By Common Transport Channel one must understand RACH, FACH/PCH, DSCH, USCH [FDD – and 1.28Mcps TDD -, E-DCH for CELL_FACH and Idle] and HS-DSCH. |
25.442 | UTRAN implementation-specific O&M transport | TS | 18.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.442/25442-i00.zip | The present document specifies the transport of implementation specific O&M signalling between Node B and the Management Platform in case that the transport is routed via the RNC. |
25.444 | Iuh data transport | TS | 18.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.444/25444-i00.zip | The present document specifies the standards for user data transport protocols between the HNB and HNB-GW/CN. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.