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
|
|---|---|---|---|---|---|---|
38.522 | NR; User Equipment (UE) conformance specification; Applicability of radio transmission, radio reception and radio resource management test cases | TS | 18.7.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.522/38522-i70.zip | The present document specifies the recommended applicability statement and completion status for the test cases included in 3GPP TS 38.521-1 [1], TS 38.521-2 [2], TS 38.521-3 [3], TS 38.521-4 [4], TS 38.521-5 [12] and TS 38.533 [5]. These applicability statements are based on the features implemented in the UE.
Special conformance testing functions can be found in 3GPP TS 38.509 [6] and the common test environments are included in 3GPP TS 38.508-1 [7]. Common implementation conformance statement (ICS) proforma can be found in 3GPP TS 38.508-2 [8].
The present document is valid for UE implemented according to 3GPP releases starting from Release 15 up to the Release indicated on the cover page of the present document. |
38.523-1 | 5GS; User Equipment (UE) conformance specification; Part 1: Protocol | TS | 18.3.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.523-1/38523-1-i30.zip | |
38.523-2 | 5GS; User Equipment (UE) conformance specification; Part 2: Applicability of protocol test cases | TS | 18.3.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.523-2/38523-2-i30.zip | |
38.523-3 | 5GS; User Equipment (UE) conformance specification; Part 3: Protocol Test Suites | TS | 18.3.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.523-3/38523-3-i30.zip | The present document specifies the protocol and signalling conformance testing in TTCN-3 for the 3GPP UE connecting to the 5G System (5GS) via its radio interface(s).
The following TTCN test specification and design considerations can be found in the present document:
- the test system architecture;
- the overall test suite structure;
- the test models and ASP definitions;
- the test methods and usage of communication ports definitions;
- the test configurations;
- the design principles and assumptions;
- TTCN styles and conventions;
- the partial PIXIT proforma;
- the test suites.
The Test Suites designed in the document are based on the test cases specified in prose in 3GPP TS 38.523‑1 [8]. The applicability of the individual test cases is specified in 3GPP TS 38.523‑2 [9].
The present document is valid for TTCN development for 5GS UE conformance test according to 3GPP Releases starting from Release 15 up to the Release indicated on the cover page of the present document. |
38.533 | NR; User Equipment (UE) conformance specification; Radio Resource Management (RRM) | TS | 18.7.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.533/38533-i70.zip | The present document specifies the measurement procedures for the conformance test of the user equipment (UE) that contain requirements for support of RRM (Radio Resource Management) as part of the 5G New Radio (5G-NR). The present document covers NR Range 1, NR Range 2 and Interworking.
The requirements are listed in different clauses only if the corresponding parameters deviate. More generally, tests are only applicable to those mobiles that are intended to support the appropriate functionality. To indicate the circumstances in which tests apply, this is noted in the "test applicability" part of the test.
For example, only Release 15 and later UE declared to support NR shall be tested for this functionality. In the event that for some tests different conditions apply for different releases, this is indicated within the text of the test itself. |
38.551 | NR; User Equipment (UE) Multiple Input Multiple Output (MIMO) Over-the-Air (OTA) performance; Conformance testing | TS | 18.3.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.551/38551-i30.zip | The present document establishes the Multiple Input Multiple Output (MIMO) Over-the-Air (OTA) performance requirements for NR UEs operating on frequency Range 1 and frequency range 2, for NR standalone (SA) and NR non-standalone (NSA) operation mode. The corresponding test methodologies are also presented in the Annex of this Technical Specification. |
38.561 | NR; User Equipment (UE) conformance specification; UE TRP (Total Radiated Power) and TRS (Total Radiated Sensitivity) requirements and test methodologies for FR1 (NR SA and EN-DC) | TS | 18.3.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.561/38561-i30.zip | The present document specifies details of conformance testing of UE TRP (Total Radiated Power) and TRS (Total Radiated Sensitivity) requirements and test methodologies for FR1 (NR SA and EN-DC). |
38.718-00-02 | NR Carrier Aggregation band combinations with two SUL cells | TR | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.718-00-02/38718-00-02-i00.zip | The present document is a technical report on NR carrier aggregation band combinations with two SUL cells under Rel-18 timeframe. The purpose is to gather the relevant background information and studies in order to address carrier aggregation band combinations with two SUL cells for the Rel-18 band combinations in Table 1-1 and Table 1-2. |
38.718-01-01 | Rel-18 NR intra band Carrier Aggregation for xCC DL/yCC UL including contiguous and non-contiguous spectrum (x>=y) | TR | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.718-01-01/38718-01-01-i00.zip | The present document is a technical report for NR Intra-band Carrier Aggregation Rel-18 for xDL/yUL including contiguous and non-contiguous spectrum under Rel-18 time frame. The purpose is to gather the relevant background information and studies to address NR Intra-band Carrier Aggregation requirements for the Rel-18 band combinations in Table 1-1, Table 1-2, Table 1-3 and Table 1-4. |
38.718-02-01 | NR inter-band Carrier Aggregation/Dual connectivity for 2 bands DL with x bands UL (x=1,2) | TR | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.718-02-01/38718-02-01-i00.zip | The present document is a technical report for power class 3 NR inter-band CA and DC for 2 bands DL with up to 2 bands UL under Rel-18 time frame. The purpose is to gather the relevant background information and studies in order to address NR inter-band CA and DC for 2 bands DL with up to 2 bands UL for the Rel-18 band combinations.
This TR contains the RF requirements of band specific combination part. The actual requirements are added to the corresponding technical specifications. |
38.718-03-01 | NR inter-band Carrier Aggregation/Dual Connectivity for 3 bands DL with x bands UL(x=1,2) | TR | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.718-03-01/38718-03-01-i00.zip | The present document is a technical report for power class 3 NR inter-band CA and DC for 3 bands DL with up to 2 bands UL under Rel-18 time frame. The purpose is to gather the relevant background information and studies in order to address NR inter-band CA and DC for 3 bands DL with up to 2 bands UL for the Rel-18 band combinations.
This TR contains the RF requirements of band specific combination part. The actual requirements are added to the corresponding technical specifications. |
38.741 | Non-Terrestrial Networks (NTN) L-/S-band for NR | TR | 18.5.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.741/38741-i50.zip | The present document is a technical report for the work item of the NTN L-S-band. |
38.751 | UE RF requirement for NR frequency range 2 (FR2) multi-Rx chain DL reception | TR | 18.3.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.751/38751-i30.zip | The objectives for NR frequency range 2 (FR2) multi-Rx chain DL reception from RF perspective are as follows.
- Introduce necessary requirement(s) for enhanced FR2-1 UEs with simultaneous DL reception with two different QCL TypeD RSs on single component carrier with up to 4 layer DL MIMO
- Enhanced RF requirements:
- Specify RF requirements, mainly spherical coverage requirements, for devices with simultaneous reception from different directions with different QCL TypeD RSs
- The legacy spherical coverage requirement for reception from a single direction will be kept
- PC3 will be prioritized, other power classes should be considered after the PC3 requirements framework is finalized |
38.761 | Measurements of Multiple Input Multiple Output (MIMO) Over-the-Air (OTA) performance of User Equipment (UE) | TR | 18.3.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.761/38761-i30.zip | The present document is a Technique Report for Measurements of Multiple Input Multiple Output (MIMO) Over-the-Air (OTA) performance of User Equipment (UE). It includes analysis and measurement results of MIMO OTA in Frequency Range 1 and Frequency Range 2, such as verification of channel models, lab alignment activities, etc.. |
38.786 | User Equipment (UE) radio transmission and reception for NR sidelink evolution | TR | 18.2.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.786/38786-i20.zip | The present document is a technical report for NR sidelink evolution services in Rel-18. The purpose is to specify radio solutions that are necessary for NR to support sidelink services working on unlicensed spectrums. |
38.822 | NR; User Equipment (UE) feature list | TR | 18.0.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.822/38822-i00.zip | The present document provides the list of UE features for NR. For each NR UE feature, the corresponding field name of UE capability, as specified in TS 38.331 [2], TS 37.355 [9] and TS 38.355 [23] is also captured in this document. The Release 15 UE feature list described in clause 4 reflects the status of Release 15 in June 2019 and has not been maintained after this date. The Release 16 UE feature list described in clause 5 reflects the status of Release 16 in December 2022 and has not been maintained after this date. The Release 17 UE feature list described in clause 6 reflects the status of Release 17 in June 2023 and has not been maintained after this date. The Release 18 UE feature list described in clause 7 reflects the status of Release 18 in March 2025 and has not been maintained after this date. |
38.835 | Study on XR enhancements for NR | TR | 18.0.1 | R2 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.835/38835-i01.zip | The present document is intended to capture the output of the study item on XR Enhancements for NR [10], which aims at investigating power saving and capacity enhancements techniques tailored for XR services, as well as means to provide XR-awareness in RAN.
This study follows a series of earlier studies conducted in 3GPP by SA1 [2], SA4 [5] [6] [7] and RAN1 [8]. It is complemented by work in SA2 [12], SA4 [11] and SA6 [4]. |
38.843 | Study on Artificial Intelligence (AI)/Machine Learning (ML) for NR air interface | TR | 18.0.0 | R1 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.843/38843-i00.zip | The application of AI/ML to wireless communications has been thus far limited to implementation-based approaches, both, at the network and the UE sides. A study on enhancement for data collection for NR and ENDC (FS_NR_ENDC_data_collect) has examined the functional framework for RAN intelligence enabled by further enhancement of data collection through use cases, examples etc. and identify the potential standardization impacts on current NG-RAN nodes and interfaces. In SA WG2 AI/ML related study, a network functionality NWDAF (Network Data Analytics Function) was introduced in Rel-15 and has been enhanced in Rel-16 and Rel-17.
This study explores the benefits of augmenting the air-interface with features enabling improved support of AI/ML. The 3GPP framework for AI/ML is studied for air-interface corresponding to each target use case regarding aspects such as performance, complexity, and potential specification impact.
Through studying a few carefully selected use cases, assessing their performance in comparison with traditional methods and the associated potential specification impacts that enable their solutions, this study lays the foundation for future air-interface use cases leveraging AI/ML techniques.
Sufficient use cases are targeted to enable the identification of a common AI/ML framework, including functional requirements of AI/ML architecture, which could be used in subsequent projects. The study also serves identifying areas where AI/ML could improve the performance of air-interface functions.
The study serves identifying what is required for an adequate AI/ML model characterization and description establishing pertinent notation for discussions and subsequent evaluations. Various levels of collaboration between the gNB and UE are identified and considered.
Evaluations to exercise the attainable gains of AI/ML based techniques for the use cases under consideration are carried out with the corresponding identification of KPIs with the goal to have a better understanding of the attainable gains and associated complexity requirements.
Finally, specification impact are assessed in order to improve the overall understanding of what would be required to enable AI/ML techniques for the air-interface.
The central objective of this project is to study the 3GPP framework for AI/ML for air-interface corresponding to each target use case regarding aspects such as performance, complexity, and potential specification impact.
The use cases to focus include:
- CSI feedback enhancement
- Spatial-frequency domain CSI compression using two-sided AI model
- Time domain CSI prediction using UE sided model
- Beam management
- Spatial-domain Downlink beam prediction for Set A of beams based on measurement results of Set B of beams
- Temporal Downlink beam prediction for Set A of beams based on the historic measurement results of Set B of beams
- Positioning accuracy enhancements
- Direct AI/ML positioning
- AI/ML assisted positioning
Note: the selection of use cases for this study solely targets the formulation of a framework to apply AI/ML to the air-interface for these and other use cases. The selection itself does not intend to provide any indication of the prospects of any future normative project.
This study also introduces AI/ML model terminology and description to identify common and specific characteristics for framework investigations, namely to:
- Characterize the defining stages of AI/ML related algorithms and associated complexity:
- Model generation, e.g., model training (including input/output, pre-/post-process, online/offline as applicable), model validation, model testing, as applicable
- Inference operation, e.g., input/output, pre-/post-process, as applicable
- Identify various levels of collaboration between UE and gNB pertinent to the selected use cases, e.g.,
- No collaboration: implementation-based only AI/ML algorithms without information exchange [for comparison purposes]
- Various levels of UE/gNB collaboration targeting at separate or joint ML operation.
- Characterize lifecycle management of AI/ML model: e.g., model training, model deployment, model inference, model monitoring, model updating
- Dataset(s) for training, validation, testing, and inference
- Identify common notation and terminology for AI/ML related functions, procedures and interfaces
- Note: the work done for FS_NR_ENDC_data_collect is considered when appropriate
For the use cases under consideration:
1) Performance benefits of AI/ML based algorithms for the agreed use cases are evaluated:
- Methodology based on statistical models (from TR 38.901 and TR 38.857 [positioning]), for link and system level simulations.
- Extensions of 3GPP evaluation methodology for better suitability to AI/ML based techniques should be considered as needed.
- Whether field data are optionally needed to further assess the performance and robustness in real-world environments should be discussed as part of the study.
- Need for common assumptions in dataset construction for training, validation and test for the selected use cases.
- Consider adequate model training strategy, collaboration levels and associated implications
- Consider agreed-upon base AI model(s) for calibration
- AI model description and training methodology used for evaluation should be reported for information and cross-checking purposes
- KPIs: Determine the common KPIs and corresponding requirements for the AI/ML operations. Determine the use-case specific KPIs and benchmarks of the selected use-cases.
- Performance, inference latency and computational complexity of AI/ML based algorithms should be compared to that of a state-of-the-art baseline
- Overhead, power consumption (including computational), memory storage, and hardware requirements (including for given processing delays) associated with enabling respective AI/ML scheme, as well as generalization capability should be considered.
2) Potential specification impact, specifically for the agreed use cases and for a common framework, is assessed:
- PHY layer aspects, e.g., (RAN1)
- Considering aspects related to, e.g., the potential specification of the AI Model lifecycle management, and dataset construction for training, validation and test for the selected use cases
- Use case and collaboration level specific specification impact, such as new signalling, means for training and validation data assistance, assistance information, measurement, and feedback
- Protocol aspects, e.g., (RAN2) - RAN2 only starts the work after there is sufficient progress on the use case study in RAN1
- Considering aspects related to, e.g., capability indication, configuration and control procedures (training/inference), and management of data and AI/ML model, per RAN1 input
- Collaboration level specific specification impact per use case
- Interoperability and testability aspects, e.g., (RAN4) - RAN4 only starts the work after there is sufficient progress on use case study in RAN1 and RAN2
- Requirements and testing frameworks to validate AI/ML based performance enhancements and ensuring that UE and gNB with AI/ML meet or exceed the existing minimum requirements if applicable
- Considering the need and implications for AI/ML processing capabilities definition
Note 1: Specific AI/ML models are not expected to be specified and are left to implementation. User data privacy needs to be preserved.
Note 2: The study on AI/ML for air interface is based on the current RAN architecture and new interfaces shall not be introduced. |
38.844 | Study on Efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidth | TR | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.844/38844-i00.zip | The present document is the Technical Report of the Study Item on Efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths, approved at TSG RAN #89-e [2]. The purpose of this document is to capture and document the outcome of the objectives stated in the SID. |
38.846 | Study on simplification of band combination specification | TR | 18.1.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.846/38846-i10.zip | The present document is a technical report for simplification of band combination specification for NR and LTE. The purpose of this TR is to further optimize and improve the working procedure for specifying band combination. A technical report will be created to collect the rules of band combination during the timescale of Rel-18 so as to improve the efficiency of band combination specifying and the quality of specifications. The dependency and applicability for RF requirements among different features for the same spectrum combination to reduce the redundant tests will also be investigated in the TR. The valid rules and valuable guidelines for requesting and specifying band combinations in Rel-17 TR 38.862 [7] are captured in the TR. |
38.848 | Study on Ambient IoT (Internet of Things) in RAN | TR | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/38_series/38.848/38848-i00.zip | The present document reports on the feasibility of meeting the design targets for relevant use cases of a new 3GPP IoT technology, on the basis of suitable deployment scenarios in a 3GPP system, which relies on ultra-low complexity devices with ultra-low power consumption for very-low end IoT applications. It intends to provide a clear differentiation, i.e. addressing use cases and scenarios that cannot otherwise be fulfilled based on existing 3GPP LPWA IoT technology.
In terms of energy storage, the study considers the following device characteristics:
- Pure batteryless devices with no energy storage capability at all, and completely dependent on the availability of an external source of energy.
- Devices with limited energy storage capability that do not need to be replaced or recharged manually. |
38.849 | Introduction of 6GHz NR unlicensed operation | TR | 18.5.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.849/38849-i50.zip | The present document is a technical report for Work Item on New Radio (NR) Access Technology, covering introduction of lower 6GHz NR unlicensed operation for Europe (NR_6GHz_unlic_EU) and in the 5925-7125 MHz range for other regions (NR_6GHz_unlic_full). |
38.850 | Rel-18 High power UE (power class 2) for FR1 NR FDD band in UL of NR inter-band CA/DC combinations with y bands downlink (y=2,3,4,5,6) and x bands uplink (x=1) | TR | 18.1.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.850/38850-i10.zip | The present document is a technical report for Rel-18 High power UE (power class 2) for FR1 NR FDD band in UL of NR inter-band CA/DC combinations with y bands downlink (y=2,3,4,5,6) and x bands uplink (x=1) under Rel-18 time-frame. The purpose is to gather the relevant background information and studies in order to complete the band combination specific requirements for the newly requested band combinations. |
38.854 | NR support for high speed train scenario in frequency range 2 (FR2) | TR | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.854/38854-i00.zip | The present document is a technical report for Rel-17 NR support for high speed train scenario in FR2. |
38.858 | Study on evolution of NR duplex operation | TR | 18.2.0 | R1 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.858/38858-i20.zip | The present document captures the results and findings from the study item "Study on Evolution of NR Duplex Operation " [2]. The purpose of this TR is to document the follows for evolution of NR duplex operation:
- applicable and relevant deployment scenarios.
- evaluation methodology and assumptions.
- possible schemes/enhancements, feasibility and performance evaluation results of subband non-overlapping full duplex and dynamic/flexible TDD.
- summary of the regulatory aspects that have to be considered for deploying the identified duplex enhancements in TDD unpaired spectrum.
This activity involves the Radio Access work area of the 3GPP studies and has potential impacts both on the Mobile Equipment and Access Network of the 3GPP systems.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] RP-213591, New SI: Study on evolution of NR duplex operation.
[3] 3GPP TR 38.901: "Study on channel model for frequencies from 0.5 to 100 GHz".
[4] 3GPP TR 36.843: "Study on LTE Device to Device Proximity Services; Radio Aspects".
[5] 3GPP TR 38.802: "Study on New Radio Access Technology Physical Layer Aspects".
[6] 3GPP TR 36.873: "3D channel model for LTE".
[7] 3GPP TR 36.814: "Further advancements for E-UTRA physical layer aspects".
[8] 3GPP TR 36.889: "Study on Licensed-Assisted Access to Unlicensed Spectrum".
[9] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone".
[10] 3GPP TS 38.101-2: "NR; User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone".
[11] Report ITU-R M.2412: "Guidelines for evaluation of radio interface technologies for IMT-2020".
[12] RP-180524, Summary of calibration results for IMT-2020 self evaluation.
[13] 3GPP TR 38.830: "Study on NR coverage enhancements".
[14] R1-2304212, Summary on SLS calibration results for NR duplex evolution
[15] R1-2307274, On evaluations for NR duplex evolution, Apple
[16] R1-2307083, SBFD evaluation results, CATT
[17] R1-2307192, Evaluation on NR duplex evolution, CMCC
[18] R1-2307324, Evaluation of NR duplex evolution, Ericsson
[19] R1-2308336, Discussion on evaluation and methodologies on evolution of NR duplex operation, Huawei, HiSilicon
[20] R1-2306695, Discussion on evaluations on NR duplex evolution, InterDigital, Inc.
[21] R1-2306885, Study on Evaluation for NR duplex evolution, LG Electronics
[22] R1-2306814, Discussion on evaluation of NR duplex evolution, MediaTek Inc.
[23] R1-2306400, Discussion for Evaluation on NR duplex evolution, New H3C Technologies Co., Ltd.
[24] R1-2306874, On the evaluation methodology for NR duplexing enhancements, Nokia, Nokia Shanghai Bell
[25] R1-2307571, Discussion on evaluation on NR duplex evolution, OPPO
[26] R1-2307922, On Deployment scenarios and evaluation Methodology for NR duplex evolution, Qualcomm Incorporated
[27] R1-2306642, Discussion on evaluation on NR duplex evolution, Spreadtrum Communications, BUPT, New H3C
[28] R1-2307674, Discussion on evaluation for NR duplex evolution, Samsung
[29] R1-2307817, Evaluation of NR duplex evolution, Sharp
[30] R1-2306906, SBFD System Level Simulation Results, Sony
[31] R1-2307381, Discussion on evaluation on NR duplex evolution, Xiaomi
[32] R1-2306981, Prototype and Simulation Results for SBFD, ZTE
[33] R1-2306746, Evaluation on NR duplex evolution, vivo
[34] R1-2308001, LLS for evaluation of coverage performance in TDD and SBFD systems, CEWiT
[35] R1-2308101, Evaluation on NR duplex operation, China Unicom, Huawei, HiSilicon
[36] R1-2307471, Discussion on evaluation on NR duplex evolution, NTT DOCOMO, INC.
[37] R1-2307330, Discussion on evaluation on NR duplex evolution, Panasonic
[38] R1-2307159, Evaluation on NR duplex evolution, Fujitsu
[39] R1-2306835, Evaluations on NR Duplex Evolution, Intel Corporation
[40] R1-2307084, Discussion on subband non-overlapping full duplex, CATT
[41] R1-2307325, Subband non-overlapping full duplex, Ericsson
[42] R1-2307619, Field test for dynamic/flexible TDD, China Telecom, ZTE
[43] R1-2306983, Discussion of enhancements on dynamic/flexible TDD, ZTE, China Telecom
[44] R1-2307326, Potential enhancements of dynamic TDD, Ericsson
[45] R1-2305035, SBFD System Level Simulation Results, Sony
[46] R4-2214376, Reply LS on interference modelling for duplex evolution, Samsung, CMCC, Qualcomm
[47] R4-2220244, WF for the feasibility from BS aspect, Samsung
[48] R4-2300690, Further considerations on SBFD BS RF aspects, Nokia, Nokia Shanghai Bell
[49] R4-2305917, WF on implementation feasibility of SBFD: Co-channel Co-site/inter-site interference, Ericsson
[50] R4-2219633, BS RF feasibility considerations, Ericsson
[51] ECC Report 281, Analysis of the suitability of the regulatory technical conditions for 5G MFCN operation in the 3400-3800 MHz band, approved 6 July 2018. Online available: https://docdb.cept.org/download/3419
[52] ECC Recommendation(20)03, Frame structures to facilitate cross-border coordination of TDD MFCN in the frequency band 3400-3800 MHz, approved 23 October 2020. Online available: https://docdb.cept.org/download/1738
[53] ECC Report 331, Efficient usage of the spectrum at the border of CEPT countries between TDD MFCN in the frequency band 3400- 3800 MHz, approved 05 November 2021. Online available: https://docdb.cept.org/download/3515
[54] ECC Decision(11)06, Harmonised frequency arrangements and least restrictive technical conditions (LRTC) for mobile/fixed communications networks (MFCN) operating in the band 3400-3800 MHz, amended 26 October 2018. Online available: https://docdb.cept.org/download/1531
[55] FCC-21-32, "FCC Opens 100 Megahertz of Mid-Band Spectrum for 5G," March 2021. Online available: https://www.fcc.gov/document/fcc-opens-100-megahertz-mid-band-spectrum-5g-0
[56] FCC, "Part 27 – Miscellaneous Wireless Communications Services," last amended on August 7, 2023. Online available: https://www.ecfr.gov/current/title-47/chapter-I/subchapter-B/part-27
[57] FCC, "Part 96 – Citizens Broadband Radio Service," last amended on August 7, 2023. Online available: https://www.ecfr.gov/current/title-47/chapter-I/subchapter-D/part-96
[58] FCC-20-22, "Expanding Flexible Use of the 3.7 to 4.2 GHz Band," March 3, 2020. Online available: https://www.fcc.gov/document/fcc-expands-flexible-use-c-band-5g-0
[59] OnGo Alliance, "CBRS Coexistence Technical Specifications," OnGo-TS-2001 V4.1.0, March 8, 2022. Online available: https://ongoalliance.org/wp-content/uploads/2022/03/OnGo-TS-2001_v4.1.0_-Published-March-08-2022.pdf
[60] ISED, "Decision on the Technical and Policy Framework for the 3650-4200 MHz Band and Changes to the Frequency Allocation of the 3500-3650 MHz Band," May 2021. Online available: https://ised-isde.canada.ca/site/spectrum-management-telecommunications/en/spectrum-allocation/3650-4200-mhz/decision-technical-and-policy-framework-3650-4200-mhz-band-and-changes-frequency-allocation-3500
[61] MSIT, "Ministry of Science and ICT Announcement No. 2018-235," May 4, 2018. Online available: https://www.msit.go.kr/bbs/view.do?sCode=user&mId=123&mPid=122&bbsSeqNo=96&nttSeqNo=1381869
[62] MSIT, "Enforcement Decree Of The Radio Waves Act," June 7, 2023. Online available: https://www.law.go.kr/lsSc.do?section=&menuId=1&subMenuId=15&tabMenuId=81&eventGubun=060101&query=%EC%A0%84%ED%8C%8C%EB%B2%95+%EC%8B%9C%ED%96%89%EB%A0%B9#undefined
[63] Radio Spectrum Management, “Technical Arrangement of the 3.5 GHz Band,” June 2019. Online available: https://www.rsm.govt.nz/assets/Uploads/documents/consultations/2019-technical-arrangements-of-the-3-5-ghz-band/2babbb72ec/technical-arrangements-of-the-3-5-ghz-band-discussion-document.pdf
[64] 3GPP TR 36.942: "Radio Frequency (RF) system scenarios".
[65] 3GPP TS 38.213: "NR;Physical layer procedures for control".
[66] 3GPP TR 38.803: "Study on new radio access technology: Radio Frequency (RF) and co-existence aspects".
[67] R4-2216404, SBFD gNB Radio and antenna considerations, Ericsson
[68] R4-2301885, BS RF feasibility considerations, Ericsson
[69] R4-2321079, Simulation results for SBFD coexistence, CMCC |
38.859 | Study on expanded and improved NR positioning | TR | 18.1.0 | R1 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.859/38859-i10.zip | The present document captures the findings of the study item "Study on Expanded and Improved NR Positioning" [7]. The purpose of this technical report is to document the requirements, additional scenarios, evaluations, and technical proposals treated during the study and provide a way forward toward normative work on expanded enhancements to NR positioning in TSG RAN WGs. |
38.863 | Non-terrestrial networks (NTN) related RF and co-existence aspects | TR | 18.6.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.863/38863-i60.zip | |
38.864 | Study on network energy savings for NR | TR | 18.1.0 | R1 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.864/38864-i10.zip | The present document captures the findings from the study item of "Study on network energy savings for NR" [2].
The study includes how to model network energy consumption especially for a base station, and evaluations of network energy saving gains as well as impact to network and user performance, by reusing existing KPI whenever applicable or new KPIs as needed. The study is also to identify techniques on gNB and UE side that can improve the network energy savings in various domains, potentially with UE feedback/assistance information and information exchange over network interfaces.
The study prioritizes idle/empty and low/medium load scenarios, allow different loads among carriers and neighbor cells, allows legacy UEs to be able to continue accessing a network implementing Rel-18 network energy savings techniques, with the possible exception of techniques developed specifically for greenfield deployments. The study does not include aspects related to IAB. |
38.865 | Study on further NR RedCap UE complexity reduction | TR | 18.0.0 | R1 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.865/38865-i00.zip | This document captures the findings from the study item "Study on further NR RedCap UE complexity reduction" [2].
The study concerns potential solutions for reducing UE complexity further compared to the RedCap UE type introduced in Rel-17 [3], providing NR support for low-tier devices between existing LPWA UEs and Rel-17 RedCap UEs to further expand the market for RedCap use cases with relatively low cost, low energy consumption, and low data rate requirements, targeting 10 Mbps peak rate.
The study focuses on UE bandwidth reduction to 5 MHz and/or UE peak rate reduction to 10 Mbps, possibly in combination with relaxed UE processing timeline. The scope of the study includes support for FR1 bands for FDD and TDD and coexistence with Rel-15/16/17 UEs. The scope of the study does not include LPWA use cases. |
38.867 | Study on NR Network-controlled Repeaters | TR | 18.0.0 | R1 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.867/38867-i00.zip | The present document captures the findings from the study item "Study on NR Network-controlled Repeaters" [2].
The SI includes the study and identification of side control information (i.e., beamforming information, Timing information, information on UL-DL TDD configuration, ON-OFF information and power control information) for network-controlled repeaters and corresponding L1/L2 signaling (including its configuration) to carry the side control information. The scope of the study also includes the study on the aspects (i.e., identification and authorization) of network-controlled repeater management
The study on NR network-controlled repeaters is to focus on the following scenarios and assumptions:
- Network-controlled repeaters are inband RF repeaters used for extension of network coverage on FR1 and FR2 bands, while during the study FR2 deployments may be prioritized for both outdoor and O2I scenarios.
- For only single hop stationary network-controlled repeaters
- Network-controlled repeaters are transparent to UEs
- Network-controlled repeater can maintain the gNB-repeater link and repeater-UE link simultaneously
NOTE1: Cost efficiency is a key consideration point for network-controlled repeaters. |
38.869 | Study on low-power Wake-up Signal and Receiver for NR | TR | 18.0.0 | R1 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.869/38869-i00.zip | The present document is intended to capture the output of study item for " Study on low-power wake up signal and receiver for NR" [2].
The study includes investigations to
- the impact of low-power wake-up signal and receiver , including power saving benefit, coverage, system overhead impact, network energy impact and other related aspects.
- the receiver architecture for low-power wake-up receiver and provide analysis for power consumption, noise figure and etc.
- L1 designs and procedures changes needed to support the wake-up signal and evaluations for the link performances.
- higher layer protocol changes needed to support the wake-up signals
- related RAN4 impacts |
38.870 | Enhanced Over-the-Air (OTA) test methods for NR FR1 Total Radiated Power (TRP) and Total Radiated Sensitivity (TRS) | TR | 18.5.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.870/38870-i50.zip | |
38.871 | Study on NR frequency range 2 (FR2) Over-the-Air (OTA) testing enhancements | TR | 18.2.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.871/38871-i20.zip | The objectives for FR2-1 OTA testing for UEs with multi-panel reception and 4DL layer are as follows.
- Define a test methodology for RF/RRM/Demodulation requirements testing for devices that can receive simultaneously from multiple Angle of Arrival (AoA)
- The multiple AoA test setup should enable testing of up to 2 DL Layers with dual polarization for each angle
- For RRM, the target should be to allow testing of 4 AoAs with 2 simultaneously active AoAs
- Define a test methodology for up to 4 DL MIMO layer demodulation testing
- Smartphone form factor should be the first priority, other UE types should also be discussed as 2nd priority
- Develop the related preliminary uncertainty assessments for the test methodologies
- The tests shall take the test system reuse, test system complexity and test time into account to keep the whole test costs within a reasonable level. |
38.872 | Study on enhancement for 700/800/900MHz band combinations | TR | 18.4.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.872/38872-i40.zip | The present document is the technical report for the study on enhancement for 700/800/900MHz band combinations [2] and sub-1GHz NR band combinations [5] under R18 time frame. The purpose is to gather the relevant background information and studies in order to address the study on enhancement for 600/700/800/900MHz band combinations in Table 1-1.
Table 1-1: Band combinations in the SI
Configuration
Uplink configuration
CA_n8-n20-n28
CA_n8-n20, CA_n8-n28, CA_n20-n28
CA_n5-n8
CA_n5-n8
CA_n5-n28
CA_n5-n28
CA_n5A-n105A
CA_n5A-n105A
CA_n28A-n105A
single UL in either n28 or n105
CA_n26A-n28A
CA_n26A-n28A
CA_n5A-n28A-n105A
CA_n5A-n28A
CA_n5A-n28A-n105A
CA_n5A-n105A
CA_n5A-n28A-n105A
single UL in either n28 or n105 |
38.876 | Air-to-ground network for NR | TR | 18.2.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.876/38876-i20.zip | The present document covers the RF, RRM and co-existence aspects of the work item “Air-to-ground network for NR” [2]
The objectives for the study are the following:
- Study and evaluate adjacent channel co-existence for ATG scenarios.
- Study and specify RF core requirements for ATG network and the ATG UE such that ATG deployment are well supported.
- Study and specify RRM requirement supporting ATG network deployment and ATG UE mobility |
38.877 | Study on NR mmWave MB-BS | TR | 18.1.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.877/38877-i10.zip | The present document is the Technical Report for the Study Item on BS RF requirement evolution dealing with FR2 multi-band BS deployments. |
38.878 | NR demodulation performance evolution | TR | 18.4.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.878/38878-i40.zip | The present technical report documents the Phase I study outcome on the advanced receiver to cancel inter-user interference for MU-MIMO, with the detailed objectives as follows:
- Evaluate and specify advanced receiver to cancel inter-user interference for MU-MIMO
- Phase I: Study the performance gain, reference receiver assumption, interference modeling, testability, required signalling overhead, as well as impact on other WGs
- Further discuss reference receiver assumption with below candidates
- E-MMSE-IRC
- R-ML
- Target scenario: Focus on slot based transmission |
38.879 | Study on enhancement for Resiliency of gNB-CU-CP | TR | 18.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.879/38879-i00.zip | The present document provides descriptions of failure scenarios associated with the gNB-CU-CP based on current architecture for the NG-RAN. |
38.880 | UE requirements for 3Tx inter-band UL CA and EN-DC | TR | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.880/38880-i00.zip | The present document is a technical report for UE requirements for 3Tx inter-band UL CA and EN-DC under Rel-18 time-frame. The purpose is to gather the relevant background information and studies of these 3Tx band combinations.
This TR contains the RF requirements of band combination specific part. The actual requirements are added to the corresponding technical specifications. |
38.881 | Lower MSD for inter-band CA/EN-DC/DC combinations | TR | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.881/38881-i00.zip | The present document is a technical report for study of lower MSD for inter-band CA/EN-DC/DC combinations. |
38.882 | Study on requirements and use cases for network verified UE location for Non-Terrestrial-Networks (NTN) in NR | TR | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/38_series/38.882/38882-i00.zip | The present document analyses the regulatory requirements (e.g. accuracy, privacy, reliability, latency) in terms of UE location service for a set of use cases/services (i.e. emergency call, lawful intercept, public warning, charging/billing). It identifies the possible need for network-verified UE location specification support in Rel-18. |
38.884 | Study on enhanced test methods for Frequency Range 2 (FR2) NR User Equipment (UE) | TR | 18.2.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.884/38884-i20.zip | The objectives of this study are to enhance the FR2 RF testing methodology and to quantify the impact of the enhancements on the UE performance, as related to the polarization basis mismatch between the test equipment and UE and to add support for testing under extreme temperature conditions.
The development of testing methodology enhancements proceeds within the following scope:
- In general
- Target the testing and calibration aspects of the permitted methods for FR2 UE RF testing and the preliminary assessment of measurement uncertainty (Clause 5.2 and Annex B of TR38.810)
- The test methodologies and procedures shall be applicable for different device types and power classes with DUT size defined in the TR 38.810. Prioritize the study to PC3 for aspects related to DUT size, and limit the study to free space conditions
- The study item outcomes shall capture the efficacy of the enhancements
- Objectives related to regulatory test cases shall be prioritized
The detailed objectives are:
1. Define test methodology for high DL power and low UL power test cases
- Considering path loss reduction, measurement antenna gain improvement, DUT positioning improvement, and MU improvement
- Considering NFTF (defined in Clause 5.2 of TR38.810) and direct near field test methodologies as possible alternative methods
- Other approaches are not precluded
- Study preliminary assessment of measurement uncertainty of new alternative methods
2. Define solutions to minimize the impact of polarization basis mismatch between the TE and DUT on the RF testing
- Considering polarization basis mismatch between the test equipment and UE and UE implementations which may be impacted by this mismatch
- Study EIS test metric which can apply to different UE RF implementations considering downlink polarization sweep enhancement
- Limit the study of this objective to the permitted UE RF methods defined in Clause 5.2 of TR38.810
- Possible enhancements may be described as
- Downlink polarization sweeping by the test equipment (i.e. introducing an additional degree of freedom for polarization alignment of the measurement antenna)
- The use of circular polarization to perform measurements
- Coherent combining and demodulation of orthogonally polarized received signals in the test equipment
- Uplink polarization sweeping by the test equipment to search for the optimal polarization angle to receive and demodulate the signal transmitted by the UE
- Considering NFTF (defined in Clause 5.2 of TR38.810) test methodology for EIS measurement
- TPMI side condition method, where TPMI side conditions are applicable to Rel-16 (and higher) UEs
- Test mode to trigger TX diversity
- Other approaches are not precluded
3. Study testability enhancements to support the verification of RF requirements for inter-band (FR2+FR2) CA
- Work on inter-band DL CA is prioritized
- Whether the test setup shall be restricted to emulating the signal from the same direction for the aggregated bands shall be aligned with the UE RF architecture assumption taken in the work item on NR RF Requirement Enhancements for FR2 [UID 830189]
4. Support extreme temperature conditions for all applicable FR2 UE RF test cases
- Considering beam peak search, spherical coverage, and total radiated power procedures
- Limit the study of this objective to the permitted UE RF methods defined in Clause 5.2 of TR38.810
- Study preliminary impacts on system measurement uncertainty under extreme temperature conditions
5. Study testability enhancements to reduce test time
- Including RF test method enhancement with reduced test time, and possible test time saving approach for UE Demodulation test and RRM test
6. Study testability aspects for the introduction of the new band n262
- Considering the extension of frequency applicability of the permitted methods in TR38.810 from 43.5 GHz up to at least 48.2 GHz
- Considering the extension of frequency applicability of the test methodology enhancements in Objectives 1 through 5 above |
38.891 | User Equipment (UE) Further enhancements of NR RF requirements for frequency range 2 (FR2) for Rel-18 | TR | 18.1.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.891/38891-i10.zip | The present document captures finding of the study on FR2 UL 256QAM and beam correspondence for RRC_INACTIVE and initial access. The purpose of this TR is to study the performance gain and implementation aspects for FR2 UL 256QAM and to ensure good UE RACH msg1 performance and UL coverage in FR2 deployments by specifying the beam correspondence requirements for RRC_INACTIVE and initial access as defined in Work Item “NR RF requirements enhancement for frequency range 2 (FR2), Phase 3” [2]. |
38.892 | APT 600 MHz NR band | TR | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.892/38892-i00.zip | The present document is a technical report for the work item of APT 600 MHz NR band. |
38.893 | Study on UE support of regionally-defined subsets of an NR band | TR | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/38_series/38.893/38893-i00.zip | The present document captures the study on UE support of regionally-defined subsets of an NR band. In accordance with 3GPP specifications, a UE is required to support the entire frequency range of a band as defined by [2], [3], or [4]. However, it was found that for some bands, there may be regional regulatory restrictions to this frequency range in some countries. The scope of this study is to investigate the root causes that may require 3GPP specification changes to accommodate as well as to consider possible general solutions if needed. |
38.894 | Requirements for simultaneous Rx/Tx band combinations for NR CA/DC, NR SUL and LTE/NR DC | TR | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.894/38894-i00.zip | The present document is a technical report for requirements on simultaneous Rx/Tx band combinations for NR CA/DC, NR SUL and LTE/NR DC.
Requested FDD-TDD, TDD-TDD CA, SUL, MR-DC and NR-DC band combinations for evaluation of supporting simultaneous Rx/Tx capability/operation are provided in the table below.
Table 1: Band combinations for evaluation of simultaneous Rx/Tx
Band combination
Power Class
CA_n34A-n41A
PC3
CA_n39A-n41A
PC3
CA_n40A-n41A
PC3, PC2
CA_n7A-n40A
PC3 |
38.895 | High power UE (power class 1.5) for NR FR1 TDD single band | TR | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.895/38895-i00.zip | The present document is a technical report for release 18 basket WI High power UE (power class 1.5) for NR FR1 TDD single band. The purpose is to gather the relevant background information and studies in order to complete the band specific requirements for the newly requested bands for power class 1.5 UE under TDD mode. |
38.896 | High power for FR1 for FDD single band(s) with power class 2 | TR | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.896/38896-i00.zip | The present document is a technical report for High power UE (power class 2) for NR FR1 FDD single band under Rel-18 time-frame. The purpose is to gather the relevant background information and studies in order to complete the band specific requirements for the newly requested band combinations for power class 2 UE under FDD mode. |
38.897 | High power UE for NR TDD intra-band carrier aggregation in frequency range FR1 | TR | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.897/38897-i00.zip | The present document is a technical report for release 18 basket WI High power UE (power class 1.5 or 2) for intra-band Carrier Aggregation combinations of a single NR FR1 TDD band. |
38.898 | High power UE for FR1 for DC_R18_xBLTE_yBNR_zDLnUL with power class m (x= 1, 2, 3, 4; y=1, 2; m<3) | TR | 18.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.898/38898-i00.zip | The present document is a technical report for High power UE (power class m with 1<m<3) for a single FR1 band in UL of Dual Connectivity (DC) combinations of x bands (x=1,2,3, 4 for y=1 or x=1, 2 for y=2) LTE inter-band CA (xDL/1UL) and y bands NR inter-band CA (yDL/1UL) in the Rel-18 time frame. The purpose is to gather the relevant background information and studies to address relevant requirements for the Rel-18 EN-DC HPUE band combinations requested by proponents and captured in the WID. |
38.901 | Study on channel model for frequencies from 0.5 to 100 GHz | TR | 18.0.0 | R1 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.901/38901-i00.zip | |
38.903 | NR; Derivation of test tolerances and measurement uncertainty for User Equipment (UE) conformance test cases | TR | 18.7.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.903/38903-i70.zip | The present document specifies a general method used to derive Measurement Uncertainties and Test Tolerances for UE conformance tests. The acceptable uncertainties for each test case are documented and establish a system for relating the Test Tolerances to the measurement uncertainties of the Test System.
For UE radio transmitting and reception tests, only FR2 is considered in this document. For UE RRM and Demodulation tests, both FR1 and FR2 are considered in this document.
The test cases which have been analysed to determine Test Tolerances are included as .zip files.
The present document is applicable from Release 15 up to the release indicated on the front page of the present Terminal conformance specifications. |
38.905 | NR; Derivation of test points for radio transmission and reception User Equipment (UE) conformance test cases | TR | 18.7.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.905/38905-i70.zip | The present document specifies and contains the derivation of Test Points for NR RF test cases, thereby 3GPP TSG RAN WG5 will have a way of storing the input contributions provided. The test cases are described in TS38.521-1[2], TS38.521-2[3] and TS38.521-3[4],
The test cases which have been analysed to determine Test Points are included as .zip files.
The present document is applicable from Release 15 up to the release indicated on the front page of the present Terminal conformance specifications. |
38.912 | Study on New Radio (NR) access technology | TR | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/38_series/38.912/38912-i00.zip | This document is intended to gather all technical outcome of the study item "Next Generation New Radio (NR) Access Technology" (see Annex A).
This activity involves the Radio Access work area of the 3GPP studies and has impacts both on the Mobile Equipment and Access Network of the 3GPP systems. |
38.913 | Study on scenarios and requirements for next generation access technologies | TR | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/38_series/38.913/38913-i00.zip | This document is related to the technical report for this study item "Scenarios and Requirements for Next Generation Access Technologies" [1]. The objective of the study item is to identify the typical deployment scenarios associated with attributes such as carrier frequency, inter-site distance, user density, maximum mobility speed, etc, and to develop requirements for next generation access technologies for the identified deployment scenarios taking into account, but not limited to, the ITU-R discussion on IMT-2020 requirements.
This document contains scenarios and requirements for next generation access technologies, which can be used as not only guidance to the technical work to be performed in 3GPP RAN WGs, but also input for ITU-R to take into account when developing IMT-2020 technical performance requirements. |
38.918 | Study on 5G NR User Equipment (UE) full stack testing for Network Slicing | TR | 18.4.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.918/38918-i40.zip | The present document contains the findings of the Study on 5G NR UE full stack testing of network slicing and the proposed test procedures. |
38.921 | Study on International Mobile Telecommunications (IMT) parameters for 6.425 - 7.025 GHz, 7.025 - 7.125 GHz and 10.0 - 10.5 GHz | TR | 18.0.1 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.921/38921-i01.zip | The present document is a technical report for the study item on IMT parameters for 6.425-7.025GHz, 7.025-7.125GHz and 10.0-10.5GHz [2], covering the study on transmitter and receiver characteristics for both NR BS and NR UE, and related parameters for answering requests from ITU-R WP5D. |
41.031 | Fraud Information Gathering System (FIGS); Service requirements; Stage 0 | TR | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/41_series/41.031/41031-i00.zip | This Technical Report describes the requirements (at a stage 0 level) of the Fraud Information Gathering System (FIGS). FIGS provides the means for the HPLMN to monitor a defined set of subscriber activities.
The aim is to enable service providers/network operators to use FIGS, and service limitation controls such as Operator Determined Barring (ODB) and Immediate Service Termination (IST), to limit their financial exposure to large unpaid bills produced on subscriber accounts whilst the subscriber is roaming outside their HPLMN. HPLMNs may also choose to collect information on subscriber activities whilst their subscribers are within the HPLMN. |
41.101 | Technical Specifications and Technical Reports for a GERAN-based 3GPP system | TS | 18.1.0 | SP | https://www.3gpp.org/ftp/Specs/archive/41_series/41.101/41101-i10.zip | The present document identifies the 3GPP system specifications for Release 18. The specifications and reports of this Release have a major version number 18 (i.e. 18.x.y). The listed Specifications are required to build a system based on GERAN radio technology. |
42.043 | Support of Localised Service Area (SoLSA); Service description; Stage 1 | TS | 18.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/42_series/42.043/42043-i00.zip | This technical specification, specifies a mechanism, which can be used as a platform for providing special tariffs and/or special set of service features for certain subscribers within a regionally restricted area or areas.
The motivation for this concept is to create means for network operators to build new service and tariff packages, which take into account subscriber groups and their needs.
The localised service area is both an optional network feature and an optional UE feature. Usage and implementation of the different SoLSA service features may vary according to operator's service packages.
This feature is not intended to replace the existing method of cell selection, cell indication and handover.
“Support of Localised service area (SoLSA)” is renamed Phase 2+ item “Support of Home Area Priority”
Note: The present document covers description for GERAN support only. UTRAN support will be added in latter releases. |
42.056 | GSM Cordless Telephony System (CTS), Phase 1; Service description; Stage 1 | TS | 18.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/42_series/42.056/42056-i00.zip | The scope of the present document is to describe the Service aspects of a GSM Cordless Telephony System (CTS), which provides the possibility for users of GSM terminals to have cordless access to a fixed network, such as PSTN/ISDN or a radio network such as GSM.
Due to the time constraints to have a first specification ready for market needs, a phased approach is necessary. The first phase aims primarily at an application supporting the speech teleservice (including DTMF support) in a residential single cell environment. The focus is on the requirements necessary to elaborate the radio interface and the security aspects for such an application.
To not prevent or impede the evolution of CTS to additional services and functions, later phases may have to be considered when now defining the means to fulfil the above mentioned requirements for the first phase of CTS. Therefore, additional support on the CTS radio interface for later phase services (e.g. SMS, subscriber authentication and GSM supplementary services), is included already in CTS Phase 1, provided that such services are clearly defined. Other expected services and functions in later phases are included in annex A.
The standardisation of the physical layers of the GSM-CTS fixed network interface is not in the scope of the present document. However, consideration may need to be given to communication of application data between CTS and PLMN via the fixed network. |
42.068 | Voice Group Call Service (VGCS); Stage 1 | TS | 18.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/42_series/42.068/42068-i00.zip | The present document specifies the stage one description of the Voice Group Call Service (VGCS) which allows speech conversation of a predefined group of service subscribers in half duplex mode on the radio link taking into account multiple mobile service subscribers involved in the VGCS call per cell.
The VGCS is applicable to all mobile stations in a certain network and area which have the technical capability and the corresponding subscription, respectively, to participate in a VGCS call.
NOTE: It is not considered as requirement that normal GSM phase 2 mobile stations will be able to be used for this service.
The service is described from the service subscriber’s and user’s point of view; in particular:
- the procedure for normal operation with successful outcome;
- the action to be taken in exceptional circumstances;
- the interaction with other GSM services and features.
The present document does not deal with the Man-Machine Interface (MMI) requirements, but makes reference to the appropriate Global System for Mobile Communications (GSM) specifications.
The present document defines a teleservice of the digital cellular telecommunications system GSM. Any interaction with other services and/or networks not dealt with in clauses 7 or 8 are outside the scope of the present document. |
42.069 | Voice Broadcast Service (VBS); Stage 1 | TS | 18.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/42_series/42.069/42069-i00.zip | The present document specifies the stage one description of the Voice Broadcast Service (VBS) which allows the distribution of speech (or other signals which can be transmitted via the speech codec), generated by a service subscriber, into a predefined geographical area to all or a group of service subscribers located in this area.
The Voice Broadcast Service (VBS) is applicable to all mobile stations in a certain network and area which have the technical capability and the respective subscription to receive a VBS call.
NOTE: It is not considered as requirement that normal GSM Phase 2 mobile stations will be able to be used for this service.
The service is described from the service subscriber's and user's point of view; in particular:
- the procedure for normal operation with successful outcome;
- the action to be taken in exceptional circumstances;
- the interaction with other GSM services and features.
The present document does not deal with the Man-Machine Interface (MMI) requirements, but makes reference to the appropriate Global System for Mobile communications (GSM) specifications.
The present document defines a teleservice of the digital cellular telecommunication system GSM. Any interaction with other services and/or networks not dealt within clauses 8 or 9 are outside the scope of the present document. |
43.005 | Technical performance objectives | TS | 18.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.005/43005-i00.zip | The present document contains technical performance objectives that should be met for the fixed infrastructure of GSM PLMNs. Concerning transmission delay for the PLMN in clause 4, the requirements should also be met by GSM Mobile Stations (MS)s.
These performance design objectives are applicable to all implementations at all points in the growth cycle up to the maximum size. These reference loads and performance objectives may be used by manufacturers in designing GSM PLMNs and by Administrations or Recognised Private Operating Agencies (RPOA)s in evaluating a specific design or for comparing different designs for potential use in the Administration's or RPOA's intended implementation. |
43.010 | GSM Public Land Mobile Network (PLMN) connection types | TS | 18.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/43_series/43.010/43010-i00.zip | This specification is only applicable for a GERAN PLMN. In the 2nd generation is this a GSM PLMN. In the 3rd generation is this a PLMN that uses a GERAN as radio access network operating either in A/Gb mode or in Iu mode.
A PLMN may be described by a limited set of access interfaces (refer to 3GPP TS 24.002 and 22.001) and a limited set of PLMN connection types to support the telecommunication services described in the 3GPP 22-series of specifications. The present document identifies and defines these connection types in so far as they relate to the particular network capabilities for a PLMN.
The basic lower layer capabilities of a PLMN are represented by a set of PLMN connection types. The definition of a set of PLMN connection types provides the necessary input to identify network capabilities of a PLMN. In addition to describing network capabilities of a PLMN, the identification of connection types facilitates the specification of network-to-network interfaces. It may also assist in the allocation of network performance parameters.
The present document should be considered in conjunction with other 3GPP specifications with particular reference to 3GPP TS 22.001, 22.002, 22.003, 23.002, 24.002 and 44.004.
The present document provides a bridge between the service specification in the 3GPP TS 22-series of specifications and the more detailed specifications such as the 3GPP TS 43, 44, 23, 24, 27 and 29 series. As such, it establishes a framework for the specification and understanding of the more detailed specifications. It is therefore not a specification against which detailed conformance testing can be performed. However, it shall be considered mandatory for the understanding of the more detailed specifications and used to resolve issues of conflict in these specifications.
From R99 onwards the following services are no longer required by a PLMN:
• the dual Bearer Services “alternate speech/data” and “speech followed by data”
• the dedicated services for PAD and Packet access
• the single asynchronous and synchronous Bearer Services (BS 21..26, BS 31..34)
From Release 4 onwards the following services are no longer required by a PLMN:
- the synchronous Bearer Service non-transparent (BS 30 NT).
- the Basic Packet access
- the Teleservice Facsimile non-transparent (TS 61/62 NT).
If a PLMN network still provides these services it has to fulfil the specification of former releases. |
43.013 | Discontinuous Reception (DRX) in the GSM system | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.013/43013-i00.zip | The present document provides a system wide view of the operation of discontinuous reception on the GSM system.
The support of DRX is mandatory in GSM PLMNs.
The detailed coding and procedural details are defined in the relevant Technical Specifications dealing with the specific interfaces that are involved, for instance GSM 08.08 and GSM 04.08. Reference is also made to the framing on the air interface which is defined in Technical Specification GSM 05.02.
The present document gives an overview of the implementation of discontinuous reception DRX within the GSM system, the actions required at MSC, BSS, and MS, the support of the facility via the air interface, and some operational aspects of the facility. |
43.020 | Security related network functions | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/43_series/43.020/43020-i00.zip | This Technical Specification specifies the network functions needed to provide the security related service and functions specified in 3GPP TS 42.009.
This specification does not address the cryptological algorithms that are needed to provide different security related features. This topic is addressed in annex C. Wherever a cryptological algorithm or mechanism is needed, this is signalled with a reference to annex C. The references refers only to functionalities, and some algorithms may be identical or use common hardware. |
43.022 | Functions related to Mobile Station (MS) in idle mode and group receive mode | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.022/43022-i00.zip | The present document gives an overview of the tasks undertaken by a GSM Mobile Station (MS) when in idle mode, that is, switched on but not having a dedicated channel allocated (e.g. not making or receiving a call), when in group receive mode, that is, receiving a voice group call or voice broadcast call but not having a dedicated connection or when in broadcast/multicast receive mode, that is, receiving an MBMS session but not having a dedicated channel allocated. It also describes the corresponding network functions. The idle mode functions are also performed by a GPRS MS as long as no dedicated channel is allocated to the MS. The idle mode functions are also performed by a CTS MS as long as the CTS MS is in manual mode GSM only or in automatic mode under PLMN coverage.
NOTE: The term GSM MS is used for any type of MS supporting one, or combinations, of the frequency bands specified in 3GPP TS 45.005.
The present document outlines how the requirements of the 3GPP TS 22 series Technical Specifications (especially 3GPP TS 22.011) on idle mode operation shall be implemented. Further details are given in 3GPP TS 44.018 and 3GPP TS 45.008.
Clause 2 of the present document gives a general description of the idle mode process. Clause 3 outlines the main requirements and technical solutions of those requirements. Clause 4 describes the processes used in idle mode. There is inevitably some overlap between these clauses. Clause 5 describes the cell change procedures for a MS in group receive mode. Clause 5a describes the cell change procedures for a MS in broadcast/multicast receive mode. |
43.026 | Multiband operation of GSM / DCS 1800 by a single operator | TR | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.026/43026-i00.zip | The purpose of the present document is to describe the functionality of a Multiband GSM/DCS Network operated by a single operator and the Multiband GSM/DCS Mobile Station (MS). It also describes the necessary amendments to the GSM/DCS phase 2 specifications for the technical realization of the function.
The resulting Amendment Requests (AR) and Change Requests (CR) necessary for Multiband Operation are listed in annex A. |
43.030 | Radio network planning aspects | TR | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.030/43030-i00.zip | The present document is a descriptive recommendation to be helpful in cell planning. |
43.045 | Technical realization of facsimile group 3 transparent | TS | 18.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/43_series/43.045/43045-i00.zip | The present document deals with the procedures allowing the technical realization of the Group 3 facsimile Service within the A/Gb mode PLMN using transparent Network support, according to the definition of Teleservice 61 and 62 specified in the 3GPP TS 22.003 [2]. |
43.050 | Transmission planning aspects of the speech service in the GSM Public Land Mobile Network (PLMN) system | TS | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/43_series/43.050/43050-i00.zip | The present document describes the transmission planning aspects pertaining to the speech service in the GSM PLMN system. Due to technical and economic factors, there cannot be full compliance with the general characteristics of international telephone connections and circuits recommended by the ITU‑T.
The present document gives guidance as to the precautions, measures and minimum requirements needed for successful interworking of the PLMN with the national and international PSTN. The present document identifies a number of routeing and network configurations. The objective is to reach a quality as close as possible to ITU‑T standards in order to safeguard the performance seen by PSTN customers.
The requirements stated for acoustics in dual mode GSM/3GPP handsets shall be interpreted as requirement on acoustics in the GSM mode. |
43.051 | GSM/EDGE Overall description; Stage 2 | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.051/43051-i00.zip | The present document defines the stage 2 service description for a GSM/EDGE Radio Access Network (GERAN). ITU‑T Recommendation I.130 describes a three-stage method for characterisation of telecommunication services, and CCITT Q.65 defines stage 2 of the method.
The present document illustrates how the services requested by a GSM/UMTS Core Network are realized by the GERAN.
The main focus of the present document is on functionality related to the Iu interfaces. The aim of the present document is not to describe functionality related to the A and Gb interfaces in details. There is no detailed description of the interfaces towards the core network and only references are given to the appropriate specifications. |
43.052 | GSM Cordless Telephony System (CTS), Phase 1; Lower Layers of the CTS Radio Interface, Stage 2 | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.052/43052-i00.zip | The present document gives an overall description of the lower layers of the radio interface for GSM based Cordless Telephony Systems (GSM-CTS).
The GSM-CTS system is intended to provide a cordless connection between the fixed network and GSM-based CTS Mobile Stations (CTS-MS) via a private CTS Fixed Part (CTS-FP).
Stage 1 is an overall description, from the service subscribers and user's standpoint, that view the network as a single entity which provides service to the user. GSM 02.56 contains the CTS Stage 1 service description.
GSM 03.56 is a Stage 2 document that describes the system architecture of the GSM Cordless Telephone Systems (GSM-CTS), i.e. the system elements, the system interfaces and the functional capabilities. |
43.055 | Dual Transfer Mode (DTM); Stage 2 | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.055/43055-i00.zip | The present document is a description of the practical implementation of GSM-GPRS class A mobiles and a basis for discussion on the changes and additions to the current specifications.
This work is part of the Release 99 Work Item "BSS co-ordination of Radio Resource allocation for class A GPRS services - GSM Radio Access (R99)" for which M Mouly of Nortel Networks is rapporteur. This work item was supported by Nortel, Motorola, Vodafone and Lucent.
In the following, GPRS refers to EGPRS, EGPRS2 and GPRS unless explicitly stated otherwise. |
43.058 | Characterisation, test methods and quality assessment for handsfree Mobile Stations (MSs) | TR | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/43_series/43.058/43058-i00.zip | The present document gives some guidelines to implement test methods and to evaluate the transmission quality of handsfree Mobile Stations (MSs). The normative characteristics and test methods for handsfree Mobile Stations (MSs are defined in GSM 03.50). The present document gives additional data.
It includes summaries of texts or contributions presented and discussed during the meetings of ad hoc group SMG2/03.50 on environmental conditions, speech processing and quality assessment for handsfree Mobile Station.
The items covered by this report are mainly.
- Environmental conditions for handsfree Mobile Stations.
- Speech processing techniques and consequences on delay.
- Speech quality assessment for handsfree implementing acoustic echo cancellation and noise reduction. |
43.059 | Functional stage 2 description of Location Services (LCS) in GERAN | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.059/43059-i00.zip | The present document specifies the stage 2 of the LoCation Services (LCS) feature in GERAN, which provides the mechanisms to support mobile location services for operators, subscribers and third party service providers.
The purpose of this stage 2 specification is to define the GERAN LCS architecture, functional entities and operations to support location methods. This description is confined to the aspects of LCS within the GERAN and does not define nor describe the LCS entities or operations within the Core Network.
Location Services 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 GERAN LCS functional model and entities, the location methods, state descriptions, and message flows. |
43.064 | General Packet Radio Service (GPRS); Overall description of the GPRS radio interface; Stage 2 | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.064/43064-i00.zip | The present document provides the overall description for lower-layer functions of the General Packet Radio Service (GPRS and EGPRS)) radio interface (Um). ). Within this TS the term GPRS refers to GPRS and EGPRS unless explicitly stated otherwise.
The overall description provides the following information:
- The services offered to higher-layer functions,
- The distribution of required functions into functional groups,
- A definition of the capabilities of each functional group,
- Service primitives for each functional group, including a description of what services and information flows are to be provided, and
- A model of operation for information flows within and between the functions.
The present document is applicable to the following GPRS Um functional layers:
- Radio Link Control functions,
- Medium Access Control functions, and
- Physical Link Control functions.
The present document describes the information transfer and control functions to be used across the radio (Um) interface for communication between the MS and the Network, see Figure 1.
3GPP TS 23.060 [3] describes the overall GPRS logical architecture and the GPRS functional layers above the Radio Link Control and Medium Access Control layer.
3GPP TS 24.007 [5] contains a description in general terms of the structured functions and procedures of this protocol and the relationship of this protocol with other layers and entities.
3GPP TS 44.018 [6] contains the definition of GPRS RLC/MAC procedures when operating on the Common Control Channel (CCCH).
3GPP TS 44.060 [7] contains the definition of RLC/MAC functions when operating on a Packet Data Channel (PDCH).
3GPP TS 44.064 [8] contains functional procedures for the Logical Link Control (LLC) layer above the RLC/MAC.
3GPP TS 45 series defines the Physical Link layer and Physical RF layer.
Figure 1: Scope of GPRS Logical Radio Interface Architecture |
43.068 | Voice Group Call Service (VGCS); Stage 2 | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/43_series/43.068/43068-i00.zip | The present document specifies the stage two description of the Voice Group Call Service (VGCS) which allows speech conversation of a predefined group of service subscribers in half duplex mode on the radio link taking into account multiple subscribers involved in the group call per cell. |
43.069 | Voice Broadcast Service (VBS); Stage 2 | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/43_series/43.069/43069-i00.zip | The present document specifies the stage 2 description of the Voice Broadcast Service (VBS) which allows the distribution of speech (or other signals which can be transmitted via the speech codec), generated by a service subscriber, into a predefined geographical area to all or a group of service subscribers located in this area. |
43.073 | Support of Localised Service Area (SoLSA); Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/43_series/43.073/43073-i00.zip | The present document specifies the stage 2 description of the SoLSA service, which gives the network operator the basis to offer subscribers or group of subscribers different services, different tariffs and different access rights depending on the geographical location of the subscriber, according to GSM 02.43. |
43.129 | Packet-switched handover for GERAN A/Gb mode; Stage 2 | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.129/43129-i00.zip | The present document defines the stage‑2 service description for packet switched handover in GERAN A/Gb mode and GAN mode. ITU-T Recommendation I.130 [8] describes a three-stage method for characterisation of telecommunication services, and ITU-T Recommendation Q.65 [9] defines stage 2 of the method. The present document refers to packet switched handover in GERAN A/Gb mode/GAN mode, and therefore focuses on the corresponding radio protocol enhancements to the packet switched domain only i.e. when services are provided through the Gb interface. |
43.130 | GSM/EDGE Iur-g interface; Stage 2 | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.130/43130-i00.zip | The present document provides an overview of the Iur-g interface. It describes the motivation, principles and functionality of this interface. It does not contain the detailed description, which it is included in the stage 3 Technical Specifications. |
43.246 | Multimedia Broadcast/Multicast Service (MBMS) in the GERAN; Stage 2 | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.246/43246-i00.zip | The present document is part of the Release 6 "Introduction of the Multimedia Broadcast Multicast Service (MBMS) in GERAN" work item and it is linked to the corresponding 3GPP TS 22.146: "Multimedia Broadcast/Multicast Service (MBMS); Stage 1" [3] and 3GPP TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description" [5].
The purpose of the present document is to provide a stage 2 description of the changes required in existing specifications for the "Introduction of the Multimedia Broadcast Multicast Service (MBMS) in GERAN" feature for Release 6. |
43.318 | Generic Access Network (GAN); Stage 2 | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.318/43318-i00.zip | The present document defines the stage 2 service description for a Generic Access Network (GAN) . It describes the GAN system concepts, documents the reference architecture, functional entities, network interfaces, and high-level procedures.
GAN supports two modes of operation:
- GAN A/Gb mode
- GAN Iu mode
GAN A/Gb mode supports an extension of GSM/GPRS mobile services that is achieved by tunnelling Non Access Stratum (NAS) protocols between the MS and the Core Network over an IP network and the A and Gb interfaces to the MSC and SGSN, respectively.
GAN Iu mode supports an extension of UMTS mobile services that is achieved by tunnelling Non Access Stratum (NAS) protocols between the user equipment (MS) and the Core Network over an IP network and the Iu-cs and Iu-ps interfaces to the MSC and SGSN, respectively.
Both GAN modes are complements to traditional GERAN/UTRAN/E-UTRAN radio access network coverage. |
43.901 | Feasibility Study on generic access to A/Gb interface | TR | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.901/43901-i00.zip | This document studies the feasibility of generic access to A/Gb interface. Specific areas of study are:
- Architecture to enable generic access.
- Access interface protocols required to provide connectivity to A/Gb interface and GSM/GPRS services.
- Security mechanisms to support generic access architecture.
- Determining feasibility for support of services currently supported through GERAN.
The focus of the study shall be on establishing the feasibility for supporting generic access in the home network case, while also identifying issues with extending the solution to the roaming scenarios. |
43.902 | Enhanced Generic Access Networks (EGAN) study | TR | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.902/43902-i00.zip | The present document contains the results of the feasibility study into the enhancements to Generic Access Networks or GAN. Considerations include overall requirements for enhancements, architectural requirements, evaluation of potential architectural solutions and alternative architectures.
The objective is to identify an architectural solution that best meets the requirements as specified in first section. The feasibility study shall also investigate mechanisms for selecting the most appropriate network domain to serve the user.
Existing solutions developed by the 3GPP should be reused as much as possible. |
43.903 | A-interface over IP study (AINTIP) | TR | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.903/43903-i00.zip | The present document contains the result from the study of introduction of support for A-interface over IP. High level areas that are studied are e.g. potential placement of transcoders in the core network, effective bandwidth utilisation at the A-interface, impact on call related messages, payload formats.
The following items shall be covered in the study:
- In the target solution it is wanted to transfer compressed speech as far as possible end-to-end to achieve efficient transport and speech quality. The possibility to free GERAN from handling all kind of transcoders shall be studied, and the architecture might place Codecs in the core network.
- Impacts/changes on current A-interface procedures resulting from placing transcoders in the core network as well as in the BSS shall be studied, e.g. impacts on the assignment and handover procedures.
- In addition to allow compressed speech over the A-interface the study shall provide further solution for effective bandwidth utilisation at the A interface, which means it shall describe multiplexing of RTP flows and how this will be negotiated between the BSS and CN nodes.
- The study shall describe a solution for "true end-to-end Codec negotiation", which considers on a call basis the preference/situation of the radio network.
- It shall be studied how call related messages have to be adapted, e.g. transfer of Codec related information, identification of calls/sessions.
- The study shall describe the wanted payload formats and other relevant user plane parameters like packetization time etc. |
44.001 | Mobile Station - Base Station System (MS - BSS) interface; General aspects and principles | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/44_series/44.001/44001-i00.zip | |
44.003 | Mobile Station - Base Station System (MS - BSS) Interface Channel Structures and Access Capabilities | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/44_series/44.003/44003-i00.zip | The present document defines limited sets of channel types, access capabilities and channel configurations at reference point Um (radio interface). |
44.004 | GSM/EDGE Layer 1; General Requirements | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/44_series/44.004/44004-i00.zip | The present document defines the service offered by the physical layer (3GPP TS 45‑series of Technical Specifications) of the MS‑BS interface (3GPP TS 45‑ and 44‑series of Technical Specifications). Its main objective is to be a guidance for the interface between the 3GPP Technical Specifications in the 45‑series and the 44‑series. It also specifies the format of signalling channels and the order of bit transmission.
As far as possible, the present document makes use of the layering principles of the Reference Model for Open System Interconnection (OSI) as contained in ITU-T Recommendations X.200 and X.210.
1a References
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.011: "Service accessibility".
[3] 3GPP TS 43.013: "Discontinuous Reception (DRX) in the GSM System".
[4] 3GPP TS 43.020: "Security-related network functions".
[5] Void.
[6] Void.
[7] 3GPP TS 44.003: "Mobile Station - Base Station System (MS - BSS) interface; Channel structures and access capabilities".
[8] 3GPP TS 44.005: "Data Link (DL) layer; General aspects".
[9] 3GPP TS 44.006: "Mobile Station - Base Station System (MS - BSS) interface; Data Link (DL) layer specification".
[10] Void.
[11] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol".
[12] Void.
[13] Void.
[14] 3GPP TS 44.012: "Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface".
[15] Void.
[16] Void.
[17] Void.
[17a] 3GPP TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol".
[18] Void.
[19] Void.
[20] Void.
[21] Void.
[22] Void.
[23] Void.
[24] Void.
[25] Void.
[26] Void.
[26a] Void.
[26b] Void.
[27] 3GPP TS 45.001: "Physical Layer on the Radio Path (General Description)".
[28] 3GPP TS 45.002: "Multiplexing and multiple access on the radio path".
[29] 3GPP TS 45.003: "Channel coding".
[30] Void.
[31] 3GPP TS 45.005: "Radio transmission and reception".
[32] 3GPP TS 45.008: "Radio subsystem link control".
[33] 3GPP TS 45.010: "Radio subsystem synchronization".
[34] Void.
[35] ITU-T Recommendation X.200: "Information technology; Open Systems Interconnection; Basic Reference Model: The basic model".
[36] ITU-T Recommendation X.210: "Information technology - Open systems interconnection - Basic Reference Model: Conventions for the definition of OSI services".
[37] 3GPP TS 48.058: "Base Station Controler - Base Transceiver Station (BCS-BTS) Interface Layer 3 Specification".
[38] 3GPP TR 45.902: "Flexible Layer One".
[39] 3GPP TS 43.064: "Overall description of the GPRS radio interface; Stage 2". |
44.005 | GSM/EDGE Data Link (DL) Layer; General aspects | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/44_series/44.005/44005-i00.zip | The present document describes in general terms the Link Access Procedures on the Dm channel, LAPDm. The application of this protocol to other channel types is for further study. Details are provided in 3GPP TS 44.006.
The purpose of LAPDm is to convey information between layer 3 entities across the GSM PLMN radio interface (MS to network interface) using the Dm channel.
NOTE 1: The term Dm channel is used for convenience to designate the collection of all the various signalling channels required in the GSM system. See also 3GPP TS 44.003.
The definition of LAPDm is based on the principles and terminology of:
‑ ITU-T Recommendations X.200 and X.210: the reference model for Open Systems Interconnection (OSI);
‑ ITU-T Recommendations Q.920 and Q.921: the specification of LAPD for the user‑network interface in ISDN;
‑ ITU-T Recommendation X.25 LAPB: user‑network interface for packet mode terminals; and
‑ ISO/IEC 3309 and ISO 4335: High‑level Data Link Control (HDLC) standards for frame structure and elements of procedures.
LAPDm is a protocol that operates at the data link layer of the OSI architecture. The relationship between the data link layer and other protocol layers is defined below.
NOTE 2: The interface between the mobile station and external terminal equipment/terminal adapters is defined in the Technical Specifications of the GSM 07‑series.
NOTE 3: The physical layer on the radio interface is defined in 3GPP TS 44.004 and layer 3 is defined in 3GPP TS 24.007, 3GPP TS 44.018, 3GPP TS 24.010 and 3GPP TS 24.011. Reference should be made to these Technical Specifications for the complete definitions of the protocols and procedures across the GSM PLMN radio interface.
NOTE 4: The term "data link layer" is used in the main text of the present document. However, mainly in figures and tables, the terms "layer 2" and "L2" are used abbreviations. Furthermore, in accordance with 3GPP TS 24.007 and 3GPP TS 44.018 the term "layer 3" is used to indicate the layer above the data link layer.
LAPDm is independent of the transmission bit rate. It requires physical channels with characteristics as defined in 3GPP TS 44.003.
Clause 2 below describes basic concepts used in the present document and 3GPP TS 44.006.
Clause 3 gives an overview description of LAPDm functions and procedures.
Clause 4 summarizes the services that the data link layer provides to layer 3 and the services that the data link layer requires from the physical layer.
Clause 5 provides an overview of the data link layer structure. |
44.006 | Mobile Station - Base Station System (MS - BSS) interface; Data Link (DL) layer specification | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/44_series/44.006/44006-i00.zip | The present document defines a data link layer protocol to be used for signalling, and possibly also for other applications, on the MS‑BS interface. |
44.012 | Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/44_series/44.012/44012-i00.zip | |
44.013 | Performance requirements on the mobile radio interface | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/44_series/44.013/44013-i00.zip | The present document specifies measurable performance requirements for signalling aspects of Mobile Stations (MS)s. To allow implementation flexibility it has been chosen to specify requirements on the whole Mobile Station rather than to specify requirements on each "OSI layer". As a consequence the performance requirements do not fit conveniently in specifications such as 3GPP TS 24.008 [4] and 3GPP TS 44.018 [4a] (layer 3 only) or 3GPP TS 44.006 [3] (layer 2 only).
The main aim of the present document is to provide the justification for testing of requirements that are not included in other GSM specifications. Where specific requirements are included in other GSM specifications they are not duplicated here.
MSs have to perform a wide variety of functions. As a consequence most performance measurements have to be made under a set of defined conditions: where necessary, these are included in the present document.
Where necessary certain assumptions are made about the interaction times between the mobile equipment and the SIM. If the (test) SIM does not respond within the assumed time then appropriate allowances shall be made.
Additionally, it is intended that the present document should contain sufficient requirements to enable some undefined network timers in 3GPP TS 24.008 [4] and 3GPP TS 44.018 [4a] to be calculated. |
44.014 | Individual equipment type requirements and interworking; Special GSM/EDGE conformance testing functions | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/44_series/44.014/44014-i00.zip | The present document specifies for Mobile Stations (MS), for the digital cellular communications system and Personal Communication Systems (PCS) operating in the 900 MHz and 1800 MHz band (GSM900 and DCS1800), standardized by 3rd Generation Partnership Project (3GPP), those ME functions which are required for conformance testing purposes only. However, except for the Electrical Man Machine Interface (EMMI) and the Multi-slot TCH Loops, they are required for every mobile station.
For conformance tests, functions are activated via the radio interface, test SIM or dedicated pins. These functions must be capable of being activated when a test SIM is present but must not function with any other (e.g. network) SIM present except where otherwise stated within the present document. In this state, the MS must be able to perform all functions specified in the present document; in addition however, the special conformance testing functions must be operational.
The special conformance testing functions of the ME are enabled by use of a dedicated Subscriber Identity Module (test SIM, see 3GPP TS 51.010-1 Annex 4). SIM, in general, is described in 3GPP TS 51.011. The ME recognizes the test SIM by the Administrative Data Field.
The present document applies to the public land mobile radio service in the GSM900 and DCS1800 systems, using constant envelope modulation and operating on radio frequencies in the 900 and 1800 MHz bands respectively with a channel separation of 200 kHz and carrying 8 full rate channels or 16 half rate channels per carrier according to the TDMA principle.
The present document is part of the 3GPP TS series of technical specifications. The present document neither replaces any of the other GSM technical specifications or GSM related TS, nor is it created to provide full understanding of (or parts of) the GSM900 and DCS1800 systems.
The present document applies to the unit which includes the hardware to establish a connection across the radio interface. |
44.018 | Mobile radio interface layer 3 specification; GSM/EDGE Radio Resource Control (RRC) protocol | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/44_series/44.018/44018-i00.zip | The present document specifies the procedures used at the radio interface (Reference Point Um, see 3GPP TS 24.002) for Radio Resource (RR) management.
Notation "Reserved sub-clause number" is used to indicate which sub-clauses of the specification were moved from this part of the standard to the other part when this standard was split between RAN and CN parts.
When the notations for "further study" or "FS" or "FFS" are present in this specification they mean that the indicated text is not a normative portion of this standard.
These procedures are defined in terms of messages exchanged over the control channels of the radio interface. The control channels are described in 3GPP TS 44.003.
The structured functions and procedures of this protocol and the relationship with other layers and entities are described in general terms in 3GPP TS 24.007. |
44.021 | Rate adaption on the Mobile Station - Base Station System (MS - BSS) interface | TS | 18.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/44_series/44.021/44021-i00.zip | The present document defines the rate adaptation functions to be used in PLMN Mobile Stations (MS)s for adapting terminal interface data rates to the Mobile Station - Base Station System (MS-BSS) interface data rates in accordance with 3GPP TS 43.010 [3].
The provision of these functions will depend on the services a particular station is designed to support.
NOTE 1: The present document should be considered together with 3GPP TS 48.020 [9] (Rate Adaptation on the BSS-MSC Interface) to give a complete description of PLMN rate adaptation.
NOTE 2: The Gb interface does not play any role in the scope of the present document although the term "A/Gb mode" is used. |
44.031 | Location Services (LCS); Mobile Station (MS) - Serving Mobile Location Centre (SMLC) Radio Resource LCS Protocol (RRLP) | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/44_series/44.031/44031-i00.zip | The present document contains the definition of the Radio Resource LCS Protocol (RRLP) to be used between the Mobile Station (MS) and the Serving Mobile Location Centre (SMLC).
Clause 2 defines the functionality of the protocol. Clause 3 describes the message structure, and Clause 4 the structure of components. Clause 5 contains the ASN.1 description of the components. |
44.035 | GSM/EDGE Location Services (LCS); Broadcast network assistance for Enhanced Observed Time Difference (E-OTD) and Global Positioning System (GPS) positioning methods | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/44_series/44.035/44035-i00.zip | The present document contains the content of messages necessary for support of MS Based location service operation on the mobile radio interface layer 3. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.