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
|
|---|---|---|---|---|---|---|
32.842
|
Telecommunication management; Study on network management of virtualized networks
|
TR
|
13.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.842/32842-d10.zip
|
The present document studies the network management of virtualized 3GPP specified core networks based on the architectural framework in ETSI GS NFV-MAN 001 [2]. It studies the network management of mobile networks that include virtualized core networks functions.
It also identifies the potential impacts on the existing 3GPP management architecture and to propose potential solutions for the network management of fully virtualized networks and mixed networks.
The objectives of this study are:
- Study the use cases and concepts for the network management of virtualized networks, which are applicable to 3GPP, taking into account the relevant use cases from ETSI.
- Analyse and classify the network management scenarios when all instances of 3GPP-defined network elements in a subsystem/domain are virtualized according to the architectural framework in ETSI GS NFV-MAN 001 [2] (i.e. in fully virtualized networks).
- Identify the requirements for potential solutions for the network management of virtualized networks when all instances of 3GPP-defined network elements in a subsystem/domain are virtualized according to the architectural framework in ETSI GS NFV-MAN 001 [2] (i.e. in fully virtualized networks).
- Analyse and classify the network management scenarios when some instances of 3GPP-defined network elements in a subsystem/domain are virtualized according to the architectural framework in ETSI GS NFV-MAN 001 [2] (i.e. in mixed networks).
- Identify the requirements for potential solutions for the network management of virtualized networks when some instances of 3GPP-defined network elements in a subsystem/domain are virtualized according to the architectural framework in ETSI GS NFV-MAN 001 [2] (i.e. in mixed networks). Study whether or not a single management system for mixed networks is required.
- Identify the potential impacts on the existing 3GPP Management reference model.
- Analyse the existing 3GPP Management reference model, interfaces, protocols and procedures to determine what can be re-used, adapted or extended and whether new IRPs are needed for network management of virtualized networks.
- Propose enhancements or extensions to the 3GPP Management reference model, if an impact is foreseen.
- If needed, solution(s) for a single management system for mixed networks should be studied.
- Provide recommendations for the standardization of the network management of fully virtualized networks and mixed networks, based on the result of the analysis and the potentially identified impacts, enhancements or extensions.
|
32.843
|
Telecommunication management; Charging management; Study on Inter-Public-Land-Mobile-Network (PLMN) Packet Switched (PS) domain online charging
|
TR
|
13.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.843/32843-d00.zip
|
The present document studies PS domain Online Charging in a roaming context, when the Gateway node implementing the IP access to the PDN for data traffic, pertains to the VPLMN, whereas the Online Charging System (OCS) pertains to the HPLMN.
The study will focus, in a first phase, on high level scenarios for Flow Based Charging, relying on defined TS 23.203 [207] PCC roaming architectures with Gy crossing PLMNs, in order to investigate the following aspects:
- Information availability in both PLMNs
- Inter-PLMN connection mechanisms for Diameter messages
- Impacts on Inter-operator charging
- Whether a "proxy OCS" is needed
The two following configurations will be addressed:
- Gy between OCS residing in HPLMN and PCEF located in PGW VPLMN, for Local Breakout Roaming configuration defined by TS 23.401 [208] and TS 23.203 [207].
- Gy between OCS residing in HPLMN and PCEF located in IP-Edge fixed broadband access owned by a Convergent fixed-mobile VPLMN, for Non Seamless WLAN Offload (NSWO) 3GPP UEs traffic defined by annex S of TS 23.203 [207].
During this first phase, the study will also investigate a basic set of Online Charging features and parameters, to be used in an inter-PLMN situation.
Based on conclusions and recommendations for the first phase, the second phase of the study will address the inter-PLMN Gyn Reference Point for the support of Application Based Charging.
|
32.849
|
Study on Charging aspects of Roaming End-to-end scenarios with VoLTE IMS and interconnecting networks
|
TR
|
13.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.849/32849-d00.zip
|
The objective of this study item is to document missing elements and information with regard to the roaming architecture for Voice over IMS with Local Breakout.
The present document collects and evaluates end-to-end roaming scenarios under different aspects of charging. The main scenarios presented will include mobile originating calls with and without the use of the loopback mechanism and mobile terminating call scenarios.
It will analyse operator requirements in consideration of the roaming scenarios and the existing Charging specifications
The conclusions are presented in a further clause with assumptions made and proposed further proceedings on that issues.
|
32.850
|
Study on determination of completeness of charging information in IMS
|
TR
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.850/32850-200.zip
| |
32.855
|
Study on OAM support for Licensed Shared Access (LSA)
|
TR
|
1.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.855/32855-100.zip
| |
32.861
|
Telecommunication management; Study on application and partitioning of Interface N (Itf-N)
|
TR
|
13.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.861/32861-d00.zip
|
The present document examines IRP requirements selected from existing IRPs' requirement and identifies one or more subsets of these requirements. It also studies the grouping of IRP functionality to recommend which functionality is needed in a network management context to satisfy every given subset of requirements.
|
32.862
|
Study on Key Quality Indicators (KQIs) for service experience
|
TR
|
1.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.862/32862-100.zip
| |
32.863
|
Telecommunication management; Fixed Mobile Convergence (FMC) metadefinitions for measurements and Key Performance Indicators (KPIs)
|
TR
|
13.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.863/32863-d00.zip
|
The present document defines the metadata for Performance Management (PM) performance measurements (KPIs/counters). The definition would enforce consistency in description/definition of all standardized performance measurements (counters/KPIs) by various SDOs and organizations (or Multi-SDO) involved in the Management of Converged Networks [6]. This consistency would facilitate encoding and decoding of performance measurements (counters/KPIs) exchanged (via management protocols) and/or stored in (database or files).
The metadata related to PM operations/notifications is not part of this PM measurement metadata.
The present document takes into account the recommendations from the Fixed Mobile Convergence (FMC) model repertoire [2] developed by the Multi-SDO JWG on Model Alignment.
|
32.901
|
Telecommunication management; Study on User Data Convergence (UDC) information model handling and provisioning: Example use cases
|
TR
|
13.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.901/32901-d00.zip
| |
33.102
|
3G security; Security architecture
|
TS
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.102/33102-d00.zip
| |
33.105
|
3G Security; Cryptographic algorithm requirements
|
TS
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.105/33105-d00.zip
| |
33.106
|
3G security; Lawful interception requirements
|
TS
|
13.4.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.106/33106-d40.zip
| |
33.107
|
3G security; Lawful interception architecture and functions
|
TS
|
13.8.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.107/33107-d80.zip
| |
33.108
|
3G security; Handover interface for Lawful Interception (LI)
|
TS
|
13.7.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.108/33108-d70.zip
| |
33.110
|
Key establishment between a Universal Integrated Circuit Card (UICC) and a terminal
|
TS
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.110/33110-d00.zip
| |
33.116
|
Security Assurance Specification (SCAS) for the MME network product class
|
TS
|
1.3.1
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.116/33116-131.zip
| |
33.117
|
Catalogue of general security assurance requirements
|
TS
|
1.4.1
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.117/33117-141.zip
| |
33.141
|
Presence service; Security
|
TS
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.141/33141-d00.zip
| |
33.179
|
Security of Mission Critical Push To Talk (MCPTT) over LTE
|
TS
|
13.12.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.179/33179-dc0.zip
|
The present document specifies the security architecture, procedures and information flows needed to protect the mission critical push to talk (MCPTT) service. The architecture includes mechanisms for authentication, protection of MCPTT signalling and protection of MCPTT media. Security for both MCPTT group calls and MCPTT private calls operating in on-network and off-network modes of operation is specified.
The functional architecture for MCPTT is defined in 3GPP TS 23.179 [2], the corresponding service requirements are defined in 3GPP TS 22.179 [3].
The MCPTT service can be used for public safety applications and also for general commercial applications e.g. utility companies and railways. As the security model is based on the public safety environment, some security features may not be applicable to MCPTT for commercial purposes.
|
33.187
|
Security aspects of Machine-Type Communications (MTC) and other mobile data applications communications enhancements
|
TS
|
13.0.1
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.187/33187-d01.zip
| |
33.203
|
3G security; Access security for IP-based services
|
TS
|
13.4.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.203/33203-d40.zip
| |
33.204
|
3G Security; Network Domain Security (NDS); Transaction Capabilities Application Part (TCAP) user security
|
TS
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.204/33204-d00.zip
| |
33.210
|
Network Domain Security (NDS); IP network layer security
|
TS
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.210/33210-d00.zip
| |
33.220
|
Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA)
|
TS
|
13.2.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.220/33220-d20.zip
| |
33.221
|
Generic Authentication Architecture (GAA); Support for subscriber certificates
|
TS
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.221/33221-d00.zip
| |
33.222
|
Generic Authentication Architecture (GAA); Access to network application functions using Hypertext Transfer Protocol over Transport Layer Security (HTTPS)
|
TS
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.222/33222-d00.zip
| |
33.223
|
Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) Push function
|
TS
|
13.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.223/33223-d10.zip
| |
33.224
|
Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) push layer
|
TS
|
13.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.224/33224-d10.zip
| |
33.234
|
3G security; Wireless Local Area Network (WLAN) interworking security
|
TS
|
13.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.234/33234-d10.zip
| |
33.246
|
3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS)
|
TS
|
13.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.246/33246-d10.zip
| |
33.259
|
Key establishment between a UICC hosting device and a remote device
|
TS
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.259/33259-d00.zip
| |
33.303
|
Proximity-based Services (ProSe); Security aspects
|
TS
|
13.5.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.303/33303-d50.zip
| |
33.310
|
Network Domain Security (NDS); Authentication Framework (AF)
|
TS
|
13.2.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.310/33310-d20.zip
| |
33.320
|
Security of Home Node B (HNB) / Home evolved Node B (HeNB)
|
TS
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.320/33320-d00.zip
| |
33.328
|
IP Multimedia Subsystem (IMS) media plane security
|
TS
|
13.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.328/33328-d10.zip
| |
33.401
|
3GPP System Architecture Evolution (SAE); Security architecture
|
TS
|
13.5.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.401/33401-d50.zip
| |
33.402
|
3GPP System Architecture Evolution (SAE); Security aspects of non-3GPP accesses
|
TS
|
13.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.402/33402-d10.zip
| |
33.832
|
Study on IMS Enhanced Spoofed Call Prevention and Detection
|
TR
|
0.3.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.832/33832-030.zip
|
The present document evaluates the IETF STIR working group active drafts for use in 3GPP networks for spoofed call detection and make recommendations on what aspects of IETF STIR active drafts should be incorporated into 3GPP IMS security specifications.
Additionally 3GPP technology specific aspects not considered or addressed in the IETF STIR Working Group will be identified and studied such as service interactions and deployment scenarios including (but not limited to):
• * Roaming
• * Business line trunking/PBX
• * CS to IMS transition scenarios
|
33.833
|
Study on security issues to support Proximity Services (ProSe)
|
TR
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.833/33833-d00.zip
|
The present document contains a study of the security aspects of Proximity Services (ProSe) and an evaluation of possible technical solutions needed to support such services. The Stage 1 requirements for these services are defined in TS 22.278 [2] and TS 22.115 [3]. These requirements include a list of general requirements on ProSe Security, Authorization and Privacy (TS 22.278 [2] clause 9.4), which are taken into consideration when developing the security key issues, security requirements and security solutions in the present document.
Different possible Stage 2 solutions for Proximity Services are studied in TR 23.703 [4].
Normative provisions/requirements are included in the present specification solely for the purposes of studying solutions and are not to be considered as implying normative requirements on 3GPP entities.
NOTE: Lawful Interception (LI) aspects are not covered in this document.
|
33.849
|
Study on subscriber privacy impact in 3GPP
|
TR
|
1.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.849/33849-110.zip
| |
33.860
|
Study on Enhanced General Packet Radio Service (EGPRS) access security enhancements with relation to cellular Internet of Things (IoT)
|
TR
|
13.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.860/33860-d10.zip
|
The present document contains a study of the EGPRS access security in relation to cellular IoT, and an evaluation of possible technical security enhancements needed to support such services. Different possible deployment scenarios for Cellular IoT, and related stage 2 solutions are being studied in TR 45.820 [2].
The scope of this study is limited to investigate the feasibility of improving the access security aspects of Gb mode. In more detail, the scope includes:
1) Investigate potential security threats, such as man in the middle attacks.
2) Investigate potential security enhancements between the UE and SGSN to mitigate said threats.
3) Define what security procedures and security algorithms that are recommended to be used by for Cellular IoT devices in Gb mode. This may be procedures and algorithms already specified in earlier 3GPP releases or it could be new procedures and algorithms being introduced as part of this feasibility study.
4) The potential security enhancements as part of this study item should aim at minimising the impacts to the GPRS core network.
|
33.863
|
Study on battery efficient security for very low throughput Machine Type Communication (MTC) devices
|
TR
|
1.2.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.863/33863-120.zip
| |
33.872
|
Study on security enhancements to Web Real Time Communication (WebRTC) access to IP Multimedia Subsystem (IMS)
|
TR
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.872/33872-d00.zip
|
The present document contains a study on security issues following the potential modifications of the IMS architecture and stage 2 procedures as required by the support of eWebRTCi (Enhancements to WEBRTC interoperability).
In particular, the present document focuses on:
• Support for end to end WebRTC security, subject to regulatory constraints, that avoids conversion between WebRTC and IMS security protocols , including the feasibility of end to end security aspects
• Third-party WebRTC access in the case where the 3rd party allocates IMS identities from a block where the associated subscription corresponds to a class of users supported by the WebRTC environment (e.g., enterprise associates) rather than a single end user
|
33.879
|
Study on security enhancements for Mission Critical Push To Talk (MCPTT) over LTE
|
TR
|
13.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.879/33879-d10.zip
|
The present document contains a study of the security aspects of the Mission-Critical Push-To-Talk (MCPTT) service and its interaction with the network. This includes an analysis of the threats to the service, the security requirements to mitigate those threats and an evaluation of possible technical solutions designed to meet the security requirements of the service.
The Stage 1 requirements for the service are defined in TS 22.179 [2]. An evaluation of Stage 2 architectural solutions for MCPTT is performed in TR 23.779 [3] and TS 23.179 [10]. This study will include consideration of relevant 3GPP specifications, particularly for ProSe (TS 33.303 [4], TS 23.303 [5]) and GCSE (TS 23.468 [6]).
The focus of the present document is to support public-safety use cases of MCPTT. Commercial scenarios are not specifically considered and some features may not be applicable to them.
|
33.889
|
Study on security aspects of Machine-Type Communications (MTC) architecture and feature enhancements
|
TR
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.889/33889-d00.zip
|
The present document captures requirements, solution alternatives, evaluations and conclusions for the SA2-led Rel-13 Features:
• GROUPE (Group based Enhancements) [4],
• MONTE (Monitoring Enhancements) [5] and
• AESE (Architecture Enhancements for Service Capability Exposure [3].
The present document captures the conclusions of the study on security and privacy implications for the requirements identified in Stage 1 and Stage 2 specifications for the above mentioned Rel-13 MTC features.
Based on the outcome of the present document, any new normative text will be incorporated in TS 33.187 [2] and/or suitable existing SA3 specifications.
Editor’s Note: SA3 is supposed to work only on security solutions for architectural solutions that are covered in SA2 Rel-13 TRs TR 23.769[4], TR 23.789[5], TR 23.708 [3].
|
33.897
|
Study on isolated E-UTRAN operation for public safety; Security aspects
|
TR
|
13.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.897/33897-d10.zip
|
The present document contains the results of a Stage 2 study and evaluation of possible 3GPP security solutions in support of Isolated E-UTRAN Operation for Public Safety (IOPS). The solutions are based on the Stage 1 requirements in 3GPP TS 22.346 [2], the architectural enhancements to support IOPS presented in the Stage 2 study report 3GPP TR 23.797 [3] and resulting informative Annex K in 3GPP TS 23.401 [10]. For the current release of specification the solution in 3GPP TS 23.401 [10] is based on a Local EPC with no backhaul.
The present document identifies key issues, security threats, deduces security requirements and presents proposed security solutions for IOPS.
Throughout this Technical Report the terms 'IOPS network' and 'Isolated E-UTRAN' are used synonymously.
|
33.905
|
Recommendations for Trusted Open Platforms
|
TR
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.905/33905-d00.zip
| |
33.916
|
Security Assurance Methodology (SECAM) for 3GPP network products
|
TR
|
1.3.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.916/33916-130.zip
| |
33.919
|
3G Security; Generic Authentication Architecture (GAA); System description
|
TR
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.919/33919-d00.zip
| |
33.924
|
Identity management and 3GPP security interworking; Identity management and Generic Authentication Architecture (GAA) interworking
|
TR
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.924/33924-d00.zip
| |
33.926
|
Security Assurance Specification (SCAS) threats and critical assets in 3GPP network product classes
|
TR
|
13.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.926/33926-d10.zip
| |
33.937
|
Study of mechanisms for Protection against Unsolicited Communication for IMS (PUCI)
|
TR
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.937/33937-d00.zip
| |
33.969
|
Study on security aspects of Public Warning System (PWS)
|
TR
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.969/33969-d00.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
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.980/33980-d00.zip
| |
33.995
|
Study on security aspects of integration of Single Sign-On (SSO) frameworks with 3GPP operator-controlled resources and mechanisms
|
TR
|
13.0.1
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.995/33995-d01.zip
| |
34.108
|
Common test environments for User Equipment (UE); Conformance testing
|
TS
|
13.1.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.108/34108-d10.zip
| |
34.109
|
Terminal logical test interface; Special conformance testing functions
|
TS
|
13.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.109/34109-d00.zip
| |
34.121-1
|
User Equipment (UE) conformance specification; Radio transmission and reception (FDD); Part 1: Conformance specification
|
TS
|
13.2.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.121-1/34121-1-d20.zip
| |
34.121-2
|
User Equipment (UE) conformance specification; Radio transmission and reception (FDD); Part 2: Implementation Conformance Statement (ICS)
|
TS
|
13.1.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.121-2/34121-2-d10.zip
| |
34.123-1
|
User Equipment (UE) conformance specification; Part 1: Protocol conformance specification
|
TS
|
13.1.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.123-1/34123-1-d10.zip
| |
34.123-2
|
User Equipment (UE) conformance specification; Part 2: Implementation conformance statement (ICS) proforma specification
|
TS
|
13.1.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.123-2/34123-2-d10.zip
| |
34.123-3
|
User Equipment (UE) conformance specification; Part 3: Abstract test suite (ATS)
|
TS
|
13.4.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.123-3/34123-3-d40.zip
| |
34.124
|
Electromagnetic compatibility (EMC) requirements for mobile terminals and ancillary equipment
|
TS
|
13.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.124/34124-d00.zip
| |
34.131
|
Test Specification for C-language binding to (Universal) Subscriber Interface Module ((U)SIM) Application Programming Interface (API)
|
TS
|
13.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.131/34131-d00.zip
| |
34.229-1
|
Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE) conformance specification; Part 1: Protocol conformance specification
|
TS
|
13.5.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.229-1/34229-1-d50.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
|
13.5.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.229-2/34229-2-d50.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
|
13.5.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.229-3/34229-3-d50.zip
| |
34.926
|
Electromagnetic compatibility (EMC); Table of international requirements for mobile terminals and ancillary equipment
|
TR
|
13.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.926/34926-d00.zip
| |
35.203
|
3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 3: Implementors' test data
|
TS
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.203/35203-d00.zip
| |
35.202
|
3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 2: Kasumi specification
|
TS
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.202/35202-d00.zip
| |
35.201
|
3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 1: f8 and f9 specification
|
TS
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.201/35201-d00.zip
| |
35.204
|
3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 4: Design conformance test data
|
TS
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.204/35204-d00.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
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.205/35205-d00.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
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.206/35206-d00.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
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.207/35207-d00.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
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.208/35208-d00.zip
| |
35.215
|
Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 1: UEA2 and UIA2 specifications
|
TS
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.215/35215-d00.zip
| |
35.216
|
Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 2: SNOW 3G specification
|
TS
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.216/35216-d00.zip
| |
35.217
|
Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 3: Implementors' test data
|
TS
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.217/35217-d00.zip
| |
35.218
|
Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 4: Design conformance test data
|
TS
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.218/35218-d00.zip
| |
35.221
|
Specification of the 3GPP Confidentiality and Integrity Algorithms EEA3 & EIA3; Document 1: EEA3 and EIA3 specifications
|
TS
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.221/35221-d00.zip
| |
35.222
|
Specification of the 3GPP Confidentiality and Integrity Algorithms EEA3 & EIA3; Document 2: ZUC specification
|
TS
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.222/35222-d00.zip
| |
35.223
|
Specification of the 3GPP Confidentiality and Integrity Algorithms EEA3 & EIA3; Document 3: Implementors' test data
|
TS
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.223/35223-d00.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
|
13.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.231/35231-d10.zip
| |
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
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.232/35232-d00.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
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.233/35233-d00.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
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.909/35909-d00.zip
| |
35.919
|
Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 5: Design and evaluation report
|
TR
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.919/35919-d00.zip
| |
35.924
|
Specification of the 3GPP Confidentiality and Integrity Algorithms EEA3 & EIA3; Document 4: Design and Evaluation Report
|
TR
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.924/35924-d00.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
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.934/35934-d00.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
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.935/35935-d00.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
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.936/35936-d00.zip
| |
36.101
|
Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception
|
TS
|
13.25.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.101/36101-dp0.zip
| |
36.104
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception
|
TS
|
13.14.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.104/36104-de0.zip
| |
36.106
|
Evolved Universal Terrestrial Radio Access (E-UTRA); FDD repeater radio transmission and reception
|
TS
|
13.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.106/36106-d00.zip
| |
36.111
|
Location Measurement Unit (LMU) performance specification; Network based positioning systems in Evolved Universal Terrestrial Radio Access Network (E-UTRAN)
|
TS
|
13.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.111/36111-d00.zip
| |
36.112
|
Location Measurement Unit (LMU) conformance specification; Network based positioning systems in Evolved Universal Terrestrial Radio Access Network (E-UTRAN)
|
TS
|
13.0.1
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.112/36112-d01.zip
| |
36.113
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) and repeater ElectroMagnetic Compatibility (EMC)
|
TS
|
13.3.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.113/36113-d30.zip
| |
36.116
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Relay radio transmission and reception
|
TS
|
13.0.1
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.116/36116-d01.zip
| |
36.117
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Relay conformance testing
|
TS
|
13.0.1
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.117/36117-d01.zip
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.