id
stringlengths 5
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 214
values | working_group
stringclasses 30
values | url
stringlengths 67
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
33.721
|
Study on security aspects of 5G mobile metaverse services
|
TR
|
19.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.721/33721-j10.zip
| |
33.535
|
Authentication and Key Management for Applications (AKMA) based on 3GPP credentials in the 5G System (5GS)
|
TS
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.535/33535-j00.zip
| |
33.919
|
3G Security; Generic Authentication Architecture (GAA); System description
|
TR
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.919/33919-j00.zip
| |
33.790
|
Study on the security support for the next generation real time communication services phase 2
|
TR
|
19.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.790/33790-j10.zip
| |
33.916
|
Security Assurance Methodology (SECAM) for 3GPP network products
|
TR
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.916/33916-j00.zip
| |
33.927
|
Security Assurance Specification (SCAS); threats and critical assets in 3GPP virtualized network product classes
|
TR
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.927/33927-j00.zip
| |
33.107
|
3G security; Lawful interception architecture and functions
|
TS
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.107/33107-j00.zip
| |
33.924
|
Identity management and 3GPP security interworking; Identity management and Generic Authentication Architecture (GAA) interworking
|
TR
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.924/33924-j00.zip
| |
33.935
|
Study on detailed Long Term Key Update Process (LTKUP) detailed solutions
|
TR
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.935/33935-j00.zip
| |
33.936
|
Security Assurance Methodology (SECAM) for 3GPP virtualized network products
|
TR
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.936/33936-j00.zip
| |
33.938
|
3GPP Cryptographic Inventory
|
TR
|
19.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.938/33938-j10.zip
| |
33.713
|
Study on security aspects of Ambient Internet of Things (AIoT) Services in 5G
|
TR
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.713/33713-j00.zip
| |
33.928
|
ADMF logic for provisioning Lawful Interception (LI)
|
TR
|
19.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.928/33928-j10.zip
| |
34.124
|
Electromagnetic compatibility (EMC) requirements for mobile terminals and ancillary equipment
|
TS
|
19.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.124/34124-j00.zip
| |
33.980
|
Liberty Alliance and 3GPP security interworking; Interworking of Liberty Alliance Identity Federation Framework (ID-FF), Identity Web Services Framework (ID-WSF) and Generic Authentication Architecture (GAA)
|
TR
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.980/33980-j00.zip
| |
33.995
|
Study on security aspects of integration of Single Sign-On (SSO) frameworks with 3GPP operator-controlled resources and mechanisms
|
TR
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.995/33995-j00.zip
| |
34.131
|
Test Specification for C-language binding to (Universal) Subscriber Interface Module ((U)SIM) Application Programming Interface (API)
|
TS
|
19.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.131/34131-j00.zip
| |
34.109
|
Terminal logical test interface; Special conformance testing functions
|
TS
|
19.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.109/34109-j00.zip
| |
35.205
|
3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 1: General
|
TS
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.205/35205-j00.zip
|
This report is a description of the work undertaken by an ETSI SAGE Task Force on the design of the Milenage Algorithm Set: an example set of 3GPP Authentication and Key Generation Functions.
The 3GPP Authentication and Key Generation Functions are not standardized. An example set of these algorithms has been produced on request from 3GPP with the intent that it shall be offered to the UMTS operators, to utilise instead of developing their own. An ETSI SAGE Task Force has carried out this work.
The requirement specification from 3GPP stated that operator personalisation of the example set shall be possible and that the basic kernel shall be possible to replace.
The example set is based on the block cipher Rijndael, which at the time was one of the AES candidates and the specification describes how the 7 algorithms used in 3GPP authentication and key generation are scheduled around this basic kernel. The specification and associated test data for the example algorithm set is documented in three documents:
- A formal specification of both the modes and the example kernel [3]
- A detailed test data document, covering modes and the example kernel [4]
- A "black box" test data document [5]
A detailed summary of the evaluation is provided in a public evaluation report [6]
This report gives an overview of the overall work by the task force.
|
33.128
|
Security; Protocol and procedures for Lawful Interception (LI); Stage 3
|
TS
|
19.4.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.128/33128-j40.zip
| |
34.926
|
Electromagnetic compatibility (EMC); Table of international requirements for mobile terminals and ancillary equipment
|
TR
|
19.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.926/34926-j00.zip
| |
35.201
|
3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 1: f8 and f9 specification
|
TS
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.201/35201-j00.zip
| |
33.969
|
Study on security aspects of Public Warning System (PWS)
|
TR
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.969/33969-j00.zip
| |
35.202
|
3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 2: Kasumi specification
|
TS
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.202/35202-j00.zip
| |
35.204
|
3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 4: Design conformance test data
|
TS
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.204/35204-j00.zip
| |
35.203
|
3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 3: Implementors' test data
|
TS
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.203/35203-j00.zip
| |
33.700-22
|
Study on security aspects of Common API Framework (CAPIF) Phase3
|
TR
|
19.2.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.700-22/33700-22-j20.zip
| |
33.937
|
Study of mechanisms for Protection against Unsolicited Communication for IMS (PUCI)
|
TR
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.937/33937-j00.zip
| |
35.206
|
3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 2: Algorithm specification
|
TS
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.206/35206-j00.zip
| |
35.231
|
Specification of the TUAK algorithm set: A second example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 1: Algorithm specification
|
TS
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.231/35231-j00.zip
|
The present document and the other Technical Specifications in the series, TS 35.232 [15] and 35.233 [16] contain an example set of algorithms which could be used as the authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5* for 3GPP systems. All seven functions are operator-specifiable rather than being fully standardised and other algorithms could be envisaged.
|
33.501
|
Security architecture and procedures for 5G System
|
TS
|
19.4.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.501/33501-j40.zip
| |
35.215
|
Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 1: UEA2 and UIA2 specifications
|
TS
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.215/35215-j00.zip
| |
35.234
|
Specification of the MILENAGE-256 algorithm set; An example set of 256-bit 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5, f5* and f5**; Document 1: General
|
TS
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.234/35234-j00.zip
|
The present document contains a high level specification of the MILENAGE-256 algorithm set which constitutes an example set of 3GPP authentication and key generation functions with a 256-bit target security level.
The example set is based on the block cipher Rijndael-256-256 with 256-bit key and 256-bit block size [8, 14] (recall that the 128 bit Advanced Encryption Standard, AES-128, corresponds to Rijndael-128-128 [8]).
An optional-to-use function, f5**, was designed according to candidate solutions discussed in 3GPP SA3 [12], with the aim of countering certain replay attacks that can lead to traceability of subscribers [13]. When used, the optional function f5** replaces f5*.
The specification and associated test data for the example algorithm set is documented in two documents:
- A formal specification of the mode and the example kernel [2].
- A detailed test data document, covering mode and the example kernel [3].
A detailed summary of the evaluation is provided in a public evaluation report [4].
The present document provides an overview of the overall work.
|
35.235
|
Specification of the MILENAGE-256 algorithm set; An example set of 256-bit 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5, f5* and f5**; Document 2: algorithm specification
|
TS
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.235/35235-j00.zip
|
This document contains a detailed specification of the general framework for the MILENAGE-256 algorithm set, together with specification for the cryptographic kernel used to instantiate the algorithm set.
The main new requirement for the MILENAGE-256 algorithm set, compared to previous 3GPP authentication and key generation functions, is to provide a 256-bit target security level, mainly motivated by future proofing 3GPP networks in case larger scale quantum computers become practical in the future. While this level of security can already be provided by the previously defined TUAK algorithm set [10], having another algorithm set, based on a different cryptographic kernel, provides a fallback, in case of future advances in conventional (non-quantum-computing based) cryptanalysis of the hash-function Keccak, the kernel used in TUAK.
The framework for MILENAGE-256 largely mirrors that of the previously defined MILENAGE algorithm set [9], but with a few important differences as discussed later in the present document.
In terms of the cryptographic kernel, MILENAGE-256 requires the use of a kernel mapping 256-bit inputs to 256-bit outputs, under the control of a 256-bit secret key. The present document provides kernel based on direct use of the Rijndael-256-256 block cipher with 256-bit block and key size.
The reader may recall that Rijndael was the candidate algorithm selected by NIST as the Advanced Encryption Standard, though the option to use a 256-bit block size was not adopted as part of the NIST AES requirements [5].
The algorithm set is named MILENAGE-256 since the intention is to provide full 256-bit security, which requires the use of 256-bit keys. Nonetheless MILENAGE-256 supports both 128-bit and 256-bit keys, to facilitate the transition to 256-bit security. If MILENAGE-256 is employed in a context containing components that do not yet support 256-bit keys, 128-bit keys can initially be employed, though it is recommended that the implementation supports a mechanism for transitioning to 256-bit keys in the future.
Associated test data for the MILENAGE-256 example algorithm set appears in a partner document comprising detailed test data, covering modes and the example kernel, and general design conformance test data [3].
Provisions are further made so that operators who so desire can customise the algorithm set to different degrees, providing some level of separation/isolation between implementations used by different operators.
|
35.236
|
Specification of the MILENAGE-256 algorithm set; An example set of 256-bit 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5, f5* and f5**; Document 3: Implementors’ test data and design conformance test data
|
TS
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.236/35236-j00.zip
|
The present document provides test data (also known as test vectors) that implementors can use to help verify that their implementations are correct, according to the technical specifications of MILENAGE-256 algorithm set [2,3]. A reference implementation in C/C++ is also provided in the Annex.
|
35.246
|
Specification of the ZUC based 256-bits algorithm set: Specification of the 256-NEA6 encryption, the 256-NIA6 integrity, and the 256-NCA6 authenticated encryption algorithm for 5G; Document 1: algorithm specification
|
TS
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.246/35246-j00.zip
|
The present document contains the algorithm specification which could be used as the encryption and integrity protection function 256-NEA6, 256-NIA6 and the combined authenticated encryption 256-NCA6 protection function for 3GPP systems.
|
35.249
|
Specification of an example algorithm for f5** function for MILENAGE and Tuak; Algorithm specification and test data
|
TS
|
19.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.249/35249-j10.zip
|
The present document presents an optional security enhancement for the MILENAGE [5, 6, 12, 13] and Tuak example algorithm set [7, 14, 15] for the 3GPP authentication and key agreement functions. The enhancement addresses a subscriber traceability issue discovered by academic researchers [9] and is provided as an alternative anonymity key generation function f5** that, when enabled, replaces the f5* function of the aforementioned example algorithm sets. A functionally equivalent security enhancement is already included in the new MILENAGE-256 example algorithm set [8].
|
35.216
|
Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 2: SNOW 3G specification
|
TS
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.216/35216-j00.zip
| |
35.217
|
Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 3: Implementors' test data
|
TS
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.217/35217-j00.zip
| |
35.208
|
3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 4: Design conformance test data
|
TS
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.208/35208-j00.zip
| |
35.207
|
3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 3: Implementors' test data
|
TS
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.207/35207-j00.zip
| |
35.218
|
Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 4: Design conformance test data
|
TS
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.218/35218-j00.zip
| |
35.221
|
Specification of the 3GPP Confidentiality and Integrity Algorithms EEA3 & EIA3; Document 1: EEA3 and EIA3 specifications
|
TS
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.221/35221-j00.zip
| |
35.937
|
Specification of the MILENAGE-256 algorithm set; An example set of 256-bit 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5, f5* and f5**; Document 4: summary and results of design and evaluation
|
TR
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.937/35937-j00.zip
|
The present document contains a detailed summary of the work performed during the design and evaluation of MILENAGE-256 algorithm set. It contains results and findings from this work and should be read as a supplement to the specifications of the algorithms [3] and the general project report [2].
The example set is based on the block cipher Rijndael-256-256 with 256-bit key and block size [8, 24] (recall that the 128-bit Advanced Encryption Standard, AES-256, corresponds to Rijndael-128-256 [9], where the notation Rijndael-b-n is defined in clause 3.2 below).
An optional-to-use function, f5** with the aim of countering certain replay attacks that can lead to traceability of subscribers [20], was designed according to candidate solutions discussed in 3GPP TR 33.846 [12]. When used, the optional function f5** replaces f5*.
The specification and associated test data for the example algorithm set is documented in two documents:
- A formal specification of the mode and the example kernel [3]
- A test data document, covering mode and the example kernel [4]
|
35.222
|
Specification of the 3GPP Confidentiality and Integrity Algorithms EEA3 & EIA3; Document 2: ZUC specification
|
TS
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.222/35222-j00.zip
| |
35.223
|
Specification of the 3GPP Confidentiality and Integrity Algorithms EEA3 & EIA3; Document 3: Implementors' test data
|
TS
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.223/35223-j00.zip
| |
36.104
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception
|
TS
|
19.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.104/36104-j10.zip
|
The present document establishes the minimum RF characteristics and minimum performance requirements of E-UTRA, E-UTRA with NB-IoT or NB-IoT Base Station (BS).
|
35.232
|
Specification of the TUAK algorithm set: A second example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 2: Implementers’ test data
|
TS
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.232/35232-j00.zip
| |
35.233
|
Specification of the TUAK algorithm set: A second example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 3: Design conformance test data
|
TS
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.233/35233-j00.zip
| |
35.924
|
Specification of the 3GPP Confidentiality and Integrity Algorithms EEA3 & EIA3; Document 4: Design and Evaluation Report
|
TR
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.924/35924-j00.zip
| |
35.909
|
3G Security; Specification of the MILENAGE algorithm set: an example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 5: Summary and results of design and evaluation
|
TR
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.909/35909-j00.zip
| |
35.919
|
Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 5: Design and evaluation report
|
TR
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.919/35919-j00.zip
| |
35.935
|
Specification of the TUAK algorithm set: A second example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 5: Performance evaluation
|
TR
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.935/35935-j00.zip
| |
34.229-2
|
Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE) conformance specification; Part 2: Implementation Conformance Statement (ICS) specification
|
TS
|
19.2.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.229-2/34229-2-j20.zip
| |
35.936
|
Specification of the TUAK algorithm set: A second example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2 ,f3, f4, f5 and f5*; Document 6: Security assessment
|
TR
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.936/35936-j00.zip
| |
35.934
|
Specification of the TUAK algorithm set: A second example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 4: Report on the design and evaluation
|
TR
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.934/35934-j00.zip
| |
36.141
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) conformance testing
|
TS
|
19.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.141/36141-j00.zip
|
The present document specifies the Radio Frequency (RF) test methods and conformance requirements for E-UTRA, E-UTRA with NB-IoT or NB-IoT Base Stations (BS) operating either in the FDD mode (used in paired bands) or the TDD mode (used in unpaired bands). These have been derived from, and are consistent with the E-UTRA, E-UTRA with NB-IoT or NB-IoT Base Station (BS) specifications defined in [2].
|
36.113
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) and repeater ElectroMagnetic Compatibility (EMC)
|
TS
|
19.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.113/36113-j00.zip
| |
36.116
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Relay radio transmission and reception
|
TS
|
19.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.116/36116-j00.zip
| |
36.106
|
Evolved Universal Terrestrial Radio Access (E-UTRA); FDD repeater radio transmission and reception
|
TS
|
19.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.106/36106-j00.zip
| |
36.124
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Electromagnetic compatibility (EMC) requirements for mobile terminals and ancillary equipment
|
TS
|
19.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.124/36124-j00.zip
| |
36.111
|
Location Measurement Unit (LMU) performance specification; Network based positioning systems in Evolved Universal Terrestrial Radio Access Network (E-UTRAN)
|
TS
|
19.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.111/36111-j00.zip
| |
36.117
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Relay conformance testing
|
TS
|
19.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.117/36117-j00.zip
| |
36.108
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Satellite Access Node radio transmission and reception
|
TS
|
19.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.108/36108-j10.zip
| |
36.112
|
Location Measurement Unit (LMU) conformance specification; Network based positioning systems in Evolved Universal Terrestrial Radio Access Network (E-UTRAN)
|
TS
|
19.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.112/36112-j00.zip
| |
36.201
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE physical layer; General description
|
TS
|
19.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.201/36201-j00.zip
| |
36.171
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for Support of Assisted Global Navigation Satellite System (A-GNSS)
|
TS
|
19.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.171/36171-j10.zip
| |
36.102
|
Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception for satellite access
|
TS
|
19.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.102/36102-j10.zip
| |
36.143
|
Evolved Universal Terrestrial Radio Access (E-UTRA); FDD repeater conformance testing
|
TS
|
19.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.143/36143-j00.zip
| |
36.214
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer; Measurements
|
TS
|
19.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.214/36214-j00.zip
| |
34.229-3
|
Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE) conformance specification; Part 3: Abstract test suite (ATS)
|
TS
|
19.1.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.229-3/34229-3-j10.zip
| |
36.307
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements on User Equipments (UEs) supporting a release-independent frequency band
|
TS
|
19.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.307/36307-j10.zip
|
The present document specifies requirements for Rel-18 UEs supporting release independent features like:
- additional E-UTRA operating frequency bands on top of Rel-18 of TS 36.101 [2], TS 36.102 [6] and TS 36.133 [3];
- additional E-UTRA CA configurations (intra-band/inter-band) on top of Rel-18 of TS 36.101 [2] and TS 36.133 [3];
- additional operating bands and/or CA configurations for specific features (like UE category 0, M1, NB1);
- other release independent features (like 4Rx antenna port, high speed scenario, 8Rx antenna port, NB-IoT or eMTC operation over NTN).
|
36.216
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer for relaying operation
|
TS
|
19.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.216/36216-j00.zip
| |
36.302
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Services provided by the physical layer
|
TS
|
19.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.302/36302-j00.zip
| |
36.314
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements
|
TS
|
19.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.314/36314-j00.zip
| |
36.304
|
Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode
|
TS
|
19.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.304/36304-j00.zip
| |
36.305
|
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Stage 2 functional specification of User Equipment (UE) positioning in E-UTRAN
|
TS
|
19.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.305/36305-j00.zip
| |
36.322
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Link Control (RLC) protocol specification
|
TS
|
19.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.322/36322-j00.zip
| |
36.323
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification
|
TS
|
19.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.323/36323-j00.zip
| |
36.360
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-WLAN Aggregation Adaptation Protocol (LWAAP) specification
|
TS
|
19.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.360/36360-j00.zip
| |
36.355
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Positioning Protocol (LPP)
|
TS
|
19.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.355/36355-j00.zip
| |
36.306
|
Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio access capabilities
|
TS
|
19.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.306/36306-j00.zip
| |
36.181
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Satellite Access Node conformance testing
|
TS
|
19.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.181/36181-j10.zip
| |
36.361
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-WLAN Radio Level Integration Using Ipsec Tunnel (LWIP) encapsulation; Protocol specification
|
TS
|
19.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.361/36361-j00.zip
| |
36.401
|
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Architecture description
|
TS
|
19.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.401/36401-j00.zip
| |
36.410
|
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 general aspects and principles
|
TS
|
19.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.410/36410-j00.zip
| |
36.411
|
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 layer 1
|
TS
|
19.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.411/36411-j00.zip
| |
36.412
|
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 signalling transport
|
TS
|
19.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.412/36412-j00.zip
| |
36.421
|
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 layer 1
|
TS
|
19.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.421/36421-j00.zip
| |
36.414
|
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 data transport
|
TS
|
19.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.414/36414-j00.zip
| |
36.420
|
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 general aspects and principles
|
TS
|
19.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.420/36420-j00.zip
| |
36.321
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification
|
TS
|
19.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.321/36321-j00.zip
| |
36.422
|
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 signalling transport
|
TS
|
19.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.422/36422-j00.zip
| |
36.424
|
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 data transport
|
TS
|
19.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.424/36424-j00.zip
| |
36.440
|
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); General aspects and principles for interfaces supporting Multimedia Broadcast Multicast Service (MBMS) within E-UTRAN
|
TS
|
19.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.440/36440-j00.zip
| |
36.425
|
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 interface user plane protocol
|
TS
|
19.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.425/36425-j00.zip
| |
36.441
|
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Layer 1 for interfaces supporting Multimedia Broadcast Multicast Service (MBMS) within E-UTRAN
|
TS
|
19.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.441/36441-j00.zip
| |
26.956
|
Evaluation and Characterization of Beyond 2D Video Formats and Codecs
|
TR
|
19.0.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.956/26956-j01.zip
| |
36.442
|
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Signalling Transport for interfaces supporting Multimedia Broadcast Multicast Service (MBMS) within E-UTRAN
|
TS
|
19.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.442/36442-j00.zip
| |
36.445
|
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); M1 data transport
|
TS
|
19.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.445/36445-j00.zip
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.