id
stringlengths 5
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 222
values | working_group
stringclasses 30
values | url
stringlengths 67
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
37.898
|
Rel-19 High power UE (power class 1.5 or 2) for Dual Connectivity (DC) combinations of LTE band(s) and NR band(s)
|
TR
|
1.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.898/37898-100.zip
|
The present document is one of four technical reports for Rel-19 High power UE (power class 1.5 or 2) for Dual Connectivity (DC) combinations of LTE band(s) and NR band(s) under Rel-19 time frame. The purpose is to gather the relevant background information and studies to address relevant requirements for the Rel-19 EN-DC HPUE band combinations requested by proponents and captured in the WID.
|
38.101-1
|
NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone
|
TS
|
19.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.101-1/38101-1-j20.zip
|
The present document establishes the minimum RF requirements for NR User Equipment (UE) operating on frequency Range 1.
|
38.101-2
|
NR; User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone
|
TS
|
19.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.101-2/38101-2-j10.zip
|
The present document establishes the minimum RF requirements for NR User Equipment (UE) operating on frequency Range 2.
|
38.101-3
|
NR; User Equipment (UE) radio transmission and reception; Part 3: Range 1 and Range 2 Interworking operation with other radios
|
TS
|
19.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.101-3/38101-3-j20.zip
|
The present document establishes the minimum RF requirements for NR User Equipment (UE) Interworking operation with other radios. This includes but is not limited to additional requirements for carrier aggregation or NR dual connectivity between Range 1 and Range 2 and additional requirements due to NR non-standalone (NSA) operation mode with E-UTRA.
|
38.101-5
|
NR; User Equipment (UE) radio transmission and reception; Part 5: Satellite access Radio Frequency (RF) and performance requirements
|
TS
|
19.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.101-5/38101-5-j10.zip
|
The present document establishes the minimum RF and performance requirements for NR User Equipment (UE) supporting satellite access operation.
The Mobile VSAT communicating with non-GSO is not considered in this release.
|
38.104
|
NR; Base Station (BS) radio transmission and reception
|
TS
|
19.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.104/38104-j10.zip
|
The present document establishes the minimum RF characteristics and minimum performance requirements of NR and NB-IoT operation in NR in-band Base Station (BS).
|
38.106
|
NR repeater radio transmission and reception
|
TS
|
19.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.106/38106-j10.zip
|
The present document establishes the minimum RF characteristics of RF repeater and network controlled repeater. For network controlled repeater (NCR), requirements for NCR-Fwd and NCR-MT apply. In this version of the specification mixed type NCR are not considered.
|
38.108
|
NR; Satellite Access Node radio transmission and reception
|
TS
|
19.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.108/38108-j10.zip
|
The present document establishes the minimum RF characteristics and minimum performance requirements of NR and NB-IoT operation in NTN NR in-band Satellite Access Node (SAN).
NOTE: Minimum requirements for NB-IoT operation in NTN NR guardband are not specified and guardband operation is SAN implementation specific.
|
38.115-1
|
NR; Repeater conformance testing - Part 1: Conducted conformance testing
|
TS
|
19.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.115-1/38115-1-j10.zip
|
The present document specifies the Radio Frequency (RF) test methods and conformance requirements for RF repeater type 1-C, network controlled repeater type (NCR) 1-C and 1-H. These have been derived from, and are consistent with the conducted requirements for repeater type 1-C, network controlled repeater type 1-C and 1-H in NR repeater specification defined in TS 38.106 [2].
RF repeater type 1-C and NCR type 1-C only have conducted requirements so they require compliance to this specification only.
NCR type 1-H has both conducted and radiated requirements so it requires compliance to this specification and TS 38.115-2 [3].
RF repeater type 2-O andNCR type 2-O have only radiated requirements so they require compliance to TS 38.115-2 [3] only.
|
38.133
|
NR; Requirements for support of radio resource management
|
TS
|
19.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.133/38133-j10.zip
|
The present document specifies requirements for support of Radio Resource Management for the FDD and TDD modes of New Radio (NR). These requirements include requirements on measurements in NR and the UE as well as requirements on node dynamical behaviour and interaction, in terms of delay and response characteristics.
|
38.141-1
|
NR; Base Station (BS) conformance testing Part 1: Conducted conformance testing
|
TS
|
19.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.141-1/38141-1-j10.zip
|
The present document specifies the Radio Frequency (RF) test methods and conformance requirements for NR and NB-IoT operation in NR in-band Base Station (BS) Type 1-C and Type 1-H. These have been derived from, and are consistent with the conducted requirements for BS Type 1-C and BS Type 1-H in NR BS specification defined in TS 38.104 [2].
A BS type 1-C only has conducted requirements so it requires compliance to this specification only.
A BS type 1-H has both conducted and radiated requirements so it requires compliance to the applicable requirements of this specification and TS 38.141-2 [3].
BS type 1-O and BS type 2-O have only radiated requirements so they require compliance to TS 38.141-2 [3] only.
|
38.141-2
|
NR; Base Station (BS) conformance testing Part 2: Radiated conformance testing
|
TS
|
19.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.141-2/38141-2-j10.zip
|
The present document specifies the Radio Frequency (RF) test methods and conformance requirements for NR Base Station (BS) type 1-H, BS type 1-O and BS type 2-O. These have been derived from, and are consistent with the radiated requirements for BS type 1-H, BS type 1-O and BS type 2-O in BS specification defined in TS 38.104 [2].
A BS type 1-C only has conducted requirements so it does not require compliance to this specification.
A BS type 1-H has both conducted and radiated requirements so it requires compliance to the applicable requirements of this specification and TS 38.141-1 [3].
BS type 1-O and BS type 2-O have only radiated requirements so they require compliance to this specification only.
|
38.161
|
NR; User Equipment (UE) TRP (Total Radiated Power) and TRS (Total Radiated Sensitivity) requirements; Range 1 Standalone and Range 1 Interworking operation with other radios
|
TS
|
19.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.161/38161-j00.zip
|
The present document establishes the TRP (Total Radiated Power) and TRS (Total Radiated Sensitivity) requirements for NR UEs operating on Range 1 Standalone and Range 1 Interworking operation with other radios.
|
38.171
|
NR; Requirements for support of Assisted Global Navigation Satellite System (A-GNSS)
|
TS
|
19.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.171/38171-j00.zip
|
The present document establishes the minimum requirements for both UE based and UE assisted FDD or TDD A-GNSS terminals which have NG-RAN access via gNB (in SA NR, NR-DC or NE-DC NR operation mode [2]) or via ng-eNB (in EN-DC operation mode [2]) and which are supporting A-GNSS in 5GS via LPP [3] between UE and LMF as described in TS 38.305 [17].
|
38.174
|
NR; Integrated Access and Backhaul (IAB) radio transmission and reception
|
TS
|
19.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.174/38174-j10.zip
|
The present document establishes the minimum RF characteristics, minimum radio resource management (RRM) requirements, RRM test cases and minimum performance requirements of NR Integrated access and backhaul (IAB).
|
38.176-1
|
NR; Integrated Access and Backhaul (IAB) conformance testing; Part 1: Conducted conformance testing
|
TS
|
19.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.176-1/38176-1-j10.zip
|
The present document establishes the minimum RF characteristics and minimum performance requirements of NR Integrated access and backhaul (IAB).
The present document specifies the Radio Frequency (RF) test methods and conformance requirements for NR Integrated access and backhaul (IAB) type 1-H. These have been derived from, and are consistent with the conducted requirements for NR Integrated access and backhaul (IAB) type 1-H in NR Integrated access and backhaul specification defined in TS 38.174 [2].
An IAB type 1-H has both conducted and radiated requirements so it requires compliance to the applicable requirements of the present document and TS 38.176-2 [3].
IAB type 1-O and IAB type 2-O have only radiated requirements so they require compliance to TS 38.176-2 [3] only.
|
38.176-2
|
NR; Integrated Access and Backhaul (IAB) conformance testing; Part 2: Radiated conformance testing
|
TS
|
19.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.176-2/38176-2-j10.zip
|
The present specifies document the Radio Frequency (RF) test methods and conformance requirements for NR Integrated access and backhaul: IAB type 1-H, IAB type 1-O and IAB type 2-O. These have been derived from, and are consistent with the radiated requirements for IAB type 1-H, IAB type 1-O and IAB type 2-O in BS specification defined in TS 38.174 [2].
A IAB type 1-H has both conducted and radiated requirements, so it requires compliance to the applicable requirements of the present document and TS 38.176-1 [3].
IAB type 1-O and IAB type 2-O have only radiated requirements, so they require compliance to the present document only.
|
38.181
|
NR; Satellite Access Node conformance testing
|
TS
|
19.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.181/38181-j00.zip
|
The present document specifies the Radio Frequency (RF) test methods and conformance requirements for NR Satellite Access Node (SAN) type 1-H, SAN type 1-O and SAN type 2-O. The document also specifies the RF test methods and conformance requirements for NB-IoT operation in NTN NR in-band SAN type 1-H and SAN type 1-O. These have been derived from and are consistent with the conducted requirements for SAN type 1-H and radiated requirement for SAN type 1-H, SAN type 1-O and SAN type 2-O in NR SAN specification defined in TS 38.108 [2].
|
38.191
|
NR; Ambient IoT device radio transmission and reception
|
TS
|
0.0.1
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.191/38191-001.zip
|
The present document establishes the minimum RF characteristics for Ambient IoT device.
|
38.194
|
NR; Ambient IoT Base Station (BS) and Carrier-Wave (CW) node radio transmission and reception
|
TS
|
0.0.1
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.194/38194-001.zip
|
This clause shall start on a new page.
The present document establishes the minimum RF characteristics and minimum performance requirements of Ambient IoT Base Station (BS) and Carrier-Wave (CW) node.
|
38.201
|
NR; Physical layer; General description
|
TS
|
19.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.201/38201-j00.zip
|
The present document provides a general description of the physical layer of NR radio interface. The present document also describes the document structure of the 3GPP physical layer specifications, i.e. TS 38.200 series.
|
38.211
|
NR; Physical channels and modulation
|
TS
|
19.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.211/38211-j00.zip
|
The present document describes the physical channels and signals for 5G-NR.
|
38.212
|
NR; Multiplexing and channel coding
|
TS
|
19.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.212/38212-j00.zip
|
The present document specifies the coding, multiplexing and mapping to physical channels for 5G NR.
|
38.213
|
NR; Physical layer procedures for control
|
TS
|
19.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.213/38213-j00.zip
|
The present document specifies and establishes the characteristics of the physical layer procedures for control operations in 5G-NR.
|
38.214
|
NR; Physical layer procedures for data
|
TS
|
19.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.214/38214-j00.zip
|
The present document specifies and establishes the characteristics of the physicals layer procedures of data channels for 5G-NR.
|
38.215
|
NR; Physical layer measurements
|
TS
|
19.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.215/38215-j00.zip
|
The present document describes the physical layer measurements for NR.
|
38.291
|
NR; Ambient IoT Physical layer
|
TS
|
19.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.291/38291-j00.zip
|
This document specifies the physical layer of Ambient IoT.
|
38.307
|
NR; Requirements on User Equipments (UEs) supporting a release-independent frequency band
|
TS
|
19.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.307/38307-j10.zip
|
The present document specifies requirements for Rel-P UEs supporting release independent features like:
- additional NR operating bands and power classes on top of Rel-P of TS 38.101-1/-2/-3/-4 [2-5] and TS 38.133 [6];
Furthermore, for Rel-P UEs supporting satellite access operation, the present document specifies requirements supporting release independent features like:
- additional NR operating bands on top of Rel-P of TS 38.101-5 [8] and TS 38.133 [6].
Note that Rel-P represents the present release of this specification as defined in section 3.2.
|
38.391
|
Ambient IoT Medium Access Control (MAC) protocol
|
TS
|
0.0.2
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.391/38391-002.zip
|
The present document specifies the Medium Access Control (MAC) protocol of Ambient IoT.
|
38.508-1
|
5GS; User Equipment (UE) conformance specification; Part 1: Common test environment
|
TS
|
19.0.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.508-1/38508-1-j00.zip
|
The present document defines the test environment for the 5G System.
This specification covers all aspects, including NG-RAN, 5GC and interworking between 5GS and EPS used for conformance tests of User Equipment (UE).
|
38.508-2
|
5GS; User Equipment (UE) conformance specification; Part 2: Common Implementation Conformance Statement (ICS) proforma
|
TS
|
19.0.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.508-2/38508-2-j00.zip
|
The present document provides the Implementation Conformance Statement (ICS) proforma for 5G New Radio (NR) User Equipment (UE), in compliance with the relevant requirements.
Special conformance testing functions can be found in 3GPP TS 38.509 [12] and 3GPP TS 36.509 [14] and the common test environments are included in 3GPP TS 38.508-1 [11] and 3GPP TS 36.508 [13].
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.521-1
|
NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 1: Range 1 standalone
|
TS
|
19.0.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.521-1/38521-1-j00.zip
| |
38.521-3
|
NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 3: Range 1 and Range 2 Interworking operation with other radios
|
TS
|
19.0.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.521-3/38521-3-j00.zip
|
The present document specifies the measurement procedures for the conformance test of the user equipment (UE) that contain RF characteristics for carrier aggregation between Range 1 and Range 2 and additional requirements for EN-DC, NE-DC and NGEN-DC.
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 "definition and applicability" part of the test.
For example only Release 15 and later UE declared to support 5G-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.522
|
NR; User Equipment (UE) conformance specification; Applicability of radio transmission, radio reception and radio resource management test cases
|
TS
|
19.0.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.522/38522-j00.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
|
19.1.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.523-1/38523-1-j10.zip
|
The present document specifies the protocol conformance testing for the 3GPP UE connecting to the 5G System (5GS) via its radio interface(s).
The following information can be found in the present document (first part of a multi-part test specification):
- the overall test structure;
- the test configurations;
- the conformance requirement and references to the core specifications;
- the test purposes; and
- a brief description of the test procedure, the specific test requirements and short message exchange table.
The applicability of the individual test cases is specified in the ICS proforma specification (3GPP TS 38.523‑2 [2]). The Test Suites are specified in part 3 (3GPP TS 38.523‑3 [3]).
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-2
|
5GS; User Equipment (UE) conformance specification; Part 2: Applicability of protocol test cases
|
TS
|
19.1.2
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.523-2/38523-2-j12.zip
|
The present document provides the applicability of protocol test cases proforma for 5G New Radio (NR) User Equipment (UE), in compliance with the relevant requirements.
The present document specifies the recommended applicability statement for the test cases included in 3GPP TS 38.523-1 [2] and 3GPP TS 38.523-3 [3]. These applicability statements are based on the features implemented in the UE.
Special conformance testing functions can be found in 3GPP TS 38.509 [5] and 3GPP TS 36.509 [7] and the common test environments are included in 3GPP TS 38.508-1 [4] and 3GPP TS 36.508 [6].
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.719-00-00
|
Rel-19 SUL configurations and CA band combinations with SUL(s)
|
TR
|
0.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.719-00-00/38719-00-00-020.zip
|
The present document is a technical report for SUL configurations and CA band combinations with SUL(s) under Rel-19 time frame. The purpose is to gather the relevant background information and studies in order to address NR SUL for the Rel-19 bands/band combinations in Table 1-1 to Table 1-2.
Table 1-1: Release 19 SUL bands
Band number
UL
DL
Duplex mode
Table 1-2: Release 19 SA SUL band combinations
SA SUL band combination
REL independent from
|
38.719-01-01
|
Rel-19 NR intra-band CA combinations
|
TR
|
0.5.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.719-01-01/38719-01-01-050.zip
|
The present document is a technical report for NR Intra-band Carrier Aggregation Rel-19 for xDL/yUL including contiguous and non-contiguous spectrum under Rel-19 time frame. The purpose is to gather the relevant background information and studies to address NR Intra-band Carrier Aggregation requirements for the Rel-19 band combinations in Table 1-1, Table 1-2, Table 1-3 and Table 1-4.
|
38.719-02-01
|
Rel-19 NR inter-band CA/DC configurations including inter band CA for 2 different bands DL with up to 2 different bands UL
|
TR
|
0.6.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.719-02-01/38719-02-01-060.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-19 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-19 band combinations.
This TR contains the RF requirements of band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
38.719-03-01
|
Rel-19 NR inter-band CA/DC configurations including inter band CA for 3 different bands DL with x different bands UL(x=1,2)
|
TR
|
0.6.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.719-03-01/38719-03-01-060.zip
|
The present document is a technical report for power class 3 NR inter-band CA and DC configurations including inter-band CA for 3 different bands DL with x different bands UL (x=1,2) under Rel-19 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-19 band combinations.
This TR contains the RF requirements of band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
38.743
|
Study on enhancements for Artificial Intelligence (AI)/Machine Learning (ML) for NG-RAN
|
TR
|
19.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.743/38743-j00.zip
|
The present document provides the description and investigation of new AI/ML based use cases, i.e., Network Slicing and Coverage and Capacity Optimization, and its corresponding solutions, and initial analysis of Rel-18 leftovers.
|
38.744
|
Study on Artificial Intelligence (AI)/Machine Learning (ML) for mobility in NR
|
TR
|
1.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.744/38744-100.zip
|
The present document …
|
38.746
|
High power UE (power class 1.5 or 2) for NR Inter-band Carrier Aggregation (CA)/Dual Connectivity (DC) with/without Supplementary Uplink (SUL) with high power on TDD band(s)
|
TR
|
0.4.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.746/38746-040.zip
|
The present document is one of four technical reports for High power UE (power class 1.5 or 2) for NR Inter-band Carrier Aggregation (CA)/Dual Connectivity (DC) with/without Supplementary Uplink (SUL) with high power on TDD band(s) under Rel-19 timeframe. The objective is to gather the relevant background information and studies in order to complete the band-combination specific requirements for the newly requested band combinations for power class 2 and power class 1.5 UE. Table 1-1 lists the band combinations covered by this TR with three power class cases for uplink.
Table 1-1 High power UE (power class 1.5 or 2) inter-band CA/DC and SUL band combinations
#
Band combination List
Power class cases for uplink
1
High power UE (power class 1.5 or 2) for NR Inter-band Carrier Aggregation (CA)/Dual connectivity (DC) with/without Supplementary uplink (SUL) with high power on TDD band(s)
Note: Including PC3 FDD/TDD+ PC3 TDD case
PC2 inter-band CA/DC:
1UL(TDD): PC2 on TDD band
2UL (TDD+TDD): PC3 or PC2 on TDD band
2UL (FDD+TDD): PC3 on FDD band, PC3 or PC2 on TDD band
PC1.5 inter-band CA/DC:
1UL(TDD): PC 1.5 on TDD band
2UL (TDD+TDD): PC3, PC2 or PC1.5 on TDD band
2UL (FDD+TDD): PC3 on FDD band, PC1.5 on TDD band
PC2 SUL band combinations with or without CA:
SUL: PC3 or PC2 on SUL band
NUL(TDD): PC2 on TDD band
PC1.5 SUL band combinations with or without CA:
SUL: PC3 or PC2 on SUL band
NUL(TDD): PC1.5 on TDD band
NUL = Normal Uplink in contrast to SUL.
|
38.749
|
Protection of Earth Exploration Satellite Service (EESS)
|
TR
|
19.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.749/38749-j00.zip
|
The present document is a technical report for the protection of Earth Exploration Satellite Service (EESS) in Rel-19 according to WRC-23 conclusion. It covers the A-MPR/MPR simulation evaluations for protection of the EESS -5dBm/200MHz in the frequency bands 23.6-24 GHz, analysis on A-MPR needed to comply with the regulatory requirements and NS values aligned with the WRC-23 outcome.
|
38.750
|
High power UE (power class 2) for NR Inter-band Carrier Aggregation (CA)/Dual Connectivity (DC) with high power on FDD band(s)
|
TR
|
1.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.750/38750-100.zip
|
The present document is one of four technical reports for High power UE (power class 1.5 or 2) for NR intra-band Carrier Aggregation (CA) or NR inter-band CA/Dual connectivity (DC) band combinations with/without NR SUL (supplementary uplink) under Rel-19 time frame. The objective is to gather the relevant background information and studies in order to complete the band-combination specific requirements for the newly requested band combinations for power class 2 UE. Table 1-1 lists the band combinations covered by this TR.
Table 1-1 High power UE (power class 2) for NR Inter-band CA/DC with high power on FDD band(s)
#
Band combination List
Power class cases for uplink
1
High power UE (power class 2) for NR Inter-band Carrier Aggregation (CA)/Dual connectivity (DC) with high power on FDD band(s)
Note: Including PC3 FDD+ PC3 FDD
1UL(FDD): PC2 on FDD band
2UL (FDD+FDD): PC3 on FDD band
|
38.753
|
Study on spatial channel model for demodulation performance requirements for NR
|
TR
|
1.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.753/38753-100.zip
|
The present document contains the findings of the Study on spatial channel model for demodulation performance requirements for NR.
|
38.755
|
Study on NR FR1 DL fragmented carriers
|
TR
|
19.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.755/38755-j00.zip
|
The present document is a technical report for study of NR FR1 DL Fragmented Carriers.
|
38.762
|
Multiple Input Multiple Output (MIMO) Over-the-Air (OTA) dynamic test methodology for FR1 UEs
|
TR
|
0.4.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.762/38762-040.zip
|
The present document is a technical report for the Multiple Input Multiple Output (MIMO) Over-the-Air (OTA) dynamic test methodology for NR FR1 UEs developed in the work item TRP_TRS_MIMO_OTA_Ph3.
In Rel-16, Rel-17, and Rel-18, the static MIMO OTA test methodology for NR UEs was developed and enhanced. This TR targets to define dynamic test methodology and radiated metrics for multi-antenna reception performance of NR FR1 UEs.
|
38.768
|
Low NR band carrier aggregation via switching
|
TR
|
1.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.768/38768-100.zip
|
<Editor’s note: capture the work item description in this clause>
|
38.769
|
Study on solutions for Ambient IoT (Internet of Things) in NR
|
TR
|
19.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.769/38769-j00.zip
|
The overall objective of the SI is to study a harmonized air interface design with minimized differences (where necessary) for Ambient IoT to enable the following devices:
- ~1 µW peak power consumption, has energy storage, initial sampling frequency offset (SFO) up to 10X ppm, neither R2D nor D2R amplification in the device. The device’s D2R transmission is backscattered on a carrier wave provided externally.
- ≤ a few hundred µW peak power consumption has energy storage, initial sampling frequency offset (SFO) up to 10X ppm, both R2D and/or D2R amplification in the device. The device’s D2R transmission may be generated internally by the device, or be backscattered on a carrier wave provided externally.
Referring to the definitions in [2, TR 38.848], this is done in the context of:
- Deployment scenario 1 (indoor-to-indoor) with Topology 1, and indoor microcell basestation.
- Deployment scenario 2 (indoor-to-outdoor) with Topology 2 and indoor UE as intermediate node under network control, and outdoor macrocell basestation.
The spectrum considered is FR1 licensed spectrum in FDD, which can be in-band to NR, in guard-band to NR/LTE, or in standalone band(s). The traffic types considered are DO-DTT and DT, focusing on indoor inventory and indoor command representative use cases. The study also assesses whether the harmonized air interface can address the DO-A use case.
Study of the design of energy harvesting signal/waveform is out of scope in Rel-19.
|
38.771
|
Study on NR frequency range 2 (FR2) OTA (Over the Air) testing Phase 3
|
TR
|
0.4.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.771/38771-040.zip
|
The objectives for FR2-1 OTA testing for UEs with simultaneous transmission with multi-panel (STxMP) are as follows.
- Study and define RF testing methodology for FR2 non-handheld UE that can transmit simultaneously with multi-panel
- Define the measurement setup and test procedure for configured transmitted power requirements for simultaneous transmission to multiple directions
- Selecting proper AoA pairs for verification perspective
- Target PC1/PC5 devices as the 1st priority.
- Develop the related preliminary uncertainty assessments for the test methodology
- FR2 test methods for multi-Rx chain DL reception defined in TR 38.871 should be used as the baseline.
- 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.774
|
Radio Frequency (RF) requirements for Low-Power Wake-up Signal and Receiver
|
TR
|
0.4.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.774/38774-040.zip
|
The present document is a Technical Report for Rel-19 Radio Frequency (RF) requirements for Low-Power Wake-up Signal and Receiver (LP-WUS/WUR). The purpose is to gather the relevant background information and analysis to address RF requirements for LP-WUS/WUR.
This TR contains discussions and agreements for LP-WUS/WUR RF. The actual RF requirements are added to the corresponding technical specifications.
|
38.787
|
User Equipment (UE) radio transmission and reception for NR Sidelink supporting intra-band CA in ITS band
|
TR
|
19.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.787/38787-j00.zip
|
The present document is a technical report on sidelink evolution services in Rel-19. The purpose is to specify radio solutions that are necessary to support sidelink power class 2/3 in non-contiguous and PC2 contiguous intra band SL CA in ITS spectrum.
|
38.792
|
High power UE (power class 1.5) for NR Inter-band Carrier Aggregation (CA)/Dual connectivity (DC) with high power on both FDD and TDD bands
|
TR
|
0.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.792/38792-020.zip
|
The present document is a technical report for UE requirements for PC1.5 inter-band UL CA and DC with HPUE in both FDD and TDD bands under Rel-19 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.793
|
Requirements for simultaneous Rx/Tx band combinations for NR CA/DC, NR SUL and LTE/NR DC
|
TR
|
0.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.793/38793-010.zip
|
The present document is a technical report for simultaneous Rx/Tx band combinations in Rel-18. The TR includes ...
|
38.794
|
High power UE (power class 1.5 or 2) for NR Intra-band Carrier Aggregation (CA) with high power on FDD or TDD band
|
TR
|
0.0.1
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.794/38794-001.zip
|
The present document is a technical report for release 19 High power UE (power class 1.5 or 2) for NR intra-band Carrier Aggregation (CA) or NR inter-band CA/Dual connectivity (DC) band combinations with/without NR SUL (supplementary uplink).
|
38.795
|
Rel-19 High power UE (power class 1.5, and 2) for NR FR1 TDD single band for handheld/FWA UEs and high power UE operation (power class 1) for FWVM (fixed-wireless/vehicle-mounted) use case in a single NR TDD band
|
TR
|
0.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.795/38795-010.zip
|
The present document is a technical report for release 19 basket WI Rel-19 High power UE (power class 1.5 and 2) for NR FR1 TDD/FDD single band, and high power UE operation (power class 1) for fixed-wireless/vehicle-mounted use cases in a single NR band. The purpose is to complete the band specific requirements for the newly requested and uncompleted Rel-18 requests bands for TDD band with PC1.5/2 for the different device types, FDD band with PC2 for the different device types and PC1 only for FWVM
|
38.796
|
Rel-19 High power UE (power class 2) for NR FR1 FDD single band for handheld/FWA UEs and high power UE operation (power class 1) for FWVM (fixed-wireless/vehicle-mounted) use case in a single NR FDD band
|
TR
|
0.5.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.796/38796-050.zip
|
The present document is a technical report for release 19 basket WI Rel-19 High power UE (power class 1.5 and 2) for NR FR1 TDD/FDD single band, and high power UE operation (power class 1) for fixed-wireless/vehicle-mounted use cases in a single NR band. The purpose is to complete the band specific requirements for the newly requested and uncompleted Rel-18 requests bands for FDD band with PC2 for the different device types and PC1 only for FWVM.
|
38.799
|
Study on Additional Topological Enhancements for NR
|
TR
|
19.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.799/38799-j00.zip
|
The present document is related to the study item "Study on additional topological enhancements for NR" [1].
|
38.863
|
Non-terrestrial networks (NTN) related RF and co-existence aspects
|
TR
|
19.0.1
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.863/38863-j01.zip
|
The present document covers the RF and co-existence aspects of the work item “Solutions for NR to support non-terrestrial networks (NTN)” [2]
The objectives for the study are the following:
- Study and specify adjacent channel co-existence scenarios of Non-terrestrial networks (NTN).
- Study and specify needed generic RF core requirements for the network and the UE such that adjacent channel co-existence scenarios are met.
NOTE: Satellite operation is used as complementarily to Terrestrial Network operation, and in separate location when satellite operates in an adjacent channel/band of terrestrial network. For instance, NTN satellite UE is assumed to connect and transmit to the satellite when it is outside a Terrestrial Network operating in an adjacent channel/band. The satellite beam might still overlap the terrestrial network.
|
38.870
|
Enhanced Over-the-Air (OTA) test methods for NR FR1 Total Radiated Power (TRP) and Total Radiated Sensitivity (TRS)
|
TR
|
19.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.870/38870-j10.zip
|
The present document is a technical report for enhanced Over-the-Air (OTA) test methods for NR FR1 Total Radiated Power (TRP) and Total Radiated Sensitivity (TRS), for NR standalone (SA) and NR non-standalone (NSA) operation mode.
This TR targets to define a full set of OTA test methods to cover different UE features for TRP and TRS measurement. The performance metric of radiated power and sensitivity for different UE types or UE features is not limited to TRP and TRS.
|
38.901
|
Study on channel model for frequencies from 0.5 to 100 GHz
|
TR
|
19.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.901/38901-j00.zip
|
The present document captures the findings of the study item, "Study on channel model for frequency spectrum above 6 GHz" [2] and from further findings of:
- the study item, "Study on New Radio Access Technology [22]",
- the study item "Study on Channel Modeling for Indoor Industrial Scenarios [23]",
- the study item "New SID: Study on channel modelling enhancements for 7-24GHz for NR [24]",
- and the study item "Study on channel modelling for Integrated Sensing And Communication (ISAC) for NR [26]".
The channel models in the present document address the frequency range 0.5-100 GHz. The purpose of this TR is to help TSG RAN WG1 to properly model and evaluate the performance of physical layer techniques using the appropriate channel model(s). Therefore, the TR will be kept up-to-date via CRs in the future.
This document relates to the 3GPP evaluation methodology and covers the modelling of the physical layer of both Mobile Equipment and Access Network of 3GPP systems.
This document is intended to capture the channel model(s) for frequencies from 0.5GHz up to 100GHz.
|
38.905
|
NR; Derivation of test points for radio transmission and reception User Equipment (UE) conformance test cases
|
TR
|
19.0.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.905/38905-j00.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.908
|
Protection of fixed satellite service (FSS) UL within 6425 to 7125 MHz
|
TR
|
19.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.908/38908-j10.zip
|
The present document is a technical report to capture the background on new BS EIRP mask requirement for band n104 for protection of fixed satellite service (FSS) UL within 6425-7125MHz and how to conduct the conformance testing for the compliance of the new BS EIRP mask requirement.
|
38.914
|
Study on 6G Scenarios and requirements
|
TR
|
0.1.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.914/38914-010.zip
|
The present document reports on the scenarios and requirements for 6G Radio, which can be used as not only guidance to the technical work in 3GPP RAN WGs but also input for ITU-R when developing IMT-2030 technical performance requirements.
The objectives of the study item are:
• investigate a candidate set of items for minimum TPRs based on the Recommendation ITU-R M.2160, and, where applicable, the associated target values and key assumptions for the identified minimum TPRs.
◦ The outcome is expected to be shared by LS with ITU-R WP5D, as suitable, and used as a baseline for the subsequent study 6G in RAN
• Identify typical and practical deployment scenarios defined by attributes such as carrier frequency, inter-site distance, user density, maximum mobility speed, and other relevant factors.
• Develop 3GPP requirements for 6G Radio for improvement of existing services and for new services.
• Determine the applicability of legacy services to 6G Radio, and define radio requirements for these, as appropriate.
• Develop 3GPP requirements for 6G Radio for these practical deployment scenarios to ensure substantial gains in all relevant bands: overall performance, user experience, TCO reduction including at least:
◦ Ensure appropriate set of functionalities, minimize the adoption of multiple options for the same functionality, avoid excessive configurations, excessive UE capabilities and UE capabilities reporting
◦ Energy efficiency and energy saving: both for network and device
◦ Enhanced spectral efficiency
◦ Enhanced overall coverage, focus on cell-edge performance and UL coverage
◦ Wider channel bandwidth (at least 200MHz) support for 6G deployments at least above 2 GHz, around 7 GHz
◦ Re-use of existing 5G mid-band (~3.5GHz) site grid for 6G deployments in at least around 7 GHz and targeting comparable coverage to 5G mid-band
◦ Target scalable and forward compatible design for diverse device types
◦ Improved spectrum utilization and operations taking into account diverse spectrum allocations
◦ Aim at using common 6G Radio design, which meets mobile broadband service requirements as high priority, to also meet vertical needs
◦ Aim at a harmonized 6G Radio design for TN and NTN, including their integration
◦ System simplification, including reducing configuration complexity, enabling more efficient Cell/UE management, etc.
• Define a time plan and steer work as appropriate for the RAN WGs during the 6G WG SI to deliver high-level decisions at least on the following areas:
◦ Fundamental 6G radio design aspects: waveform, numerology, channel coding, etc…
◦ Overall high-level aspects of 5G to 6G migration
◦ RAN architecture and interfaces, including RAN-Core interface
◦ Coordination of 6G AI/ML framework
|
38.922
|
Study on International Mobile Telecommunications (IMT) parameters for 4400 - 4800 MHz, 7125 - 8400 MHz and 14800 - 15350 MHz
|
TR
|
19.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.922/38922-j10.zip
|
The present document is a technical report for the study item on IMT parameters for 4400 to 4800 MHz, 7125 to 8400 MHz and 14800 to 15350 MHz frequency ranges [2]. It covers the study on transmitter and receiver characteristics for both NR BS and NR UE, and related parameters, including co-existence studies, AAS antenna models, and responses to the ITU-R W5PD’s requests as well as three additional questions received in [3].
Findings and evaluations captured in this technical report are based on the Rel-18 version of the NR specifications, unless otherwise stated.
Related LS replies for each of the frequency ranges in question were sent out to ITU-R W5PD in [4, 5, 6].
|
21.101
|
Technical Specifications and Technical Reports for a UTRAN-based 3GPP system
|
TS
|
18.1.0
|
SP
|
https://www.3gpp.org/ftp/Specs/archive/21_series/21.101/21101-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 UTRAN radio technology.
|
21.111
|
USIM and IC card requirements
|
TS
|
18.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/21_series/21.111/21111-i00.zip
|
This document defines the requirements of the USIM (Universal Subscriber Identity Module) and the IC card for 3G (UICC). These are derived from the service and security requirements defined in TS 22.100 [1] and TS 22.101 [2]. The USIM is a 3G application on an IC card. It inter-operates with a 3G terminal and provides access to 3G services. This document is intended to serve as a basis for the detailed specification of the USIM and the UICC, and the interface to the 3G terminal.
|
21.201
|
Technical Specifications and Technical Reports for an Evolved Packet System (EPS) based 3GPP system
|
TS
|
18.1.0
|
SP
|
https://www.3gpp.org/ftp/Specs/archive/21_series/21.201/21201-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 the Evolved Packet System.
The high-level architecture of such a system is defined in 3GPP TS 23.002 [2] (figure 1b).
|
21.202
|
Technical Specifications and Technical Reports relating to the Common IP Multimedia Subsystem (IMS)
|
TS
|
18.0.0
|
SP
|
https://www.3gpp.org/ftp/Specs/archive/21_series/21.202/21202-i00.zip
|
The present document identifies the 3GPP Technical Specifications and Technical Reports specifically relating to the Common IP Multimedia Subsystem (IMS) maintained by 3GPP. Standards organizations adopting the Common IP Multimedia Subsystem (IMS) might not need to use all listed specifications.
|
21.205
|
Technical Specifications and Technical Reports for a 5G based 3GPP system
|
TS
|
18.1.0
|
SP
|
https://www.3gpp.org/ftp/Specs/archive/21_series/21.205/21205-i10.zip
|
The present document identifies the 3GPP Technical Specifications required to build a 5G system. It also lists relevant Technical Reports.
|
21.905
|
Vocabulary for 3GPP Specifications
|
TR
|
18.0.0
|
SP
|
https://www.3gpp.org/ftp/Specs/archive/21_series/21.905/21905-i00.zip
|
The purpose of this report is to identify specialist technical terms used within the 3GPP project for the purposes of specifying service requirements. The motivations for this are:
- To ensure that editors use terminology that is consistent across specifications.
- To provide a reader with convenient reference for technical terms that are used across multiple documents.
- To prevent inconsistent use of terminology across documents.
This document is a collection of terms, definitions and abbreviations related to the baseline documents defining 3GPP objectives and systems framework. This document provides a tool for further work on 3GPP technical documentation and facilitates their understanding.
The terms, definitions and abbreviations as given in this document are either imported from existing documentation (ETSI, ITU or elsewhere) or newly created by 3GPP experts whenever the need for precise vocabulary was identified.
|
21.918
|
Release 18 Description; Summary of Rel-18 Work Items
|
TR
|
18.0.0
|
SP
|
https://www.3gpp.org/ftp/Specs/archive/21_series/21.918/21918-i00.zip
|
The present document provides a summary of each Release 18 Feature or, whenever needed, of each significant Work Item.
The information provided in the present document is limited to an overview of each Feature, explaining briefly its purpose and the main lines of the system's behaviour to execute the Feature.
|
22.001
|
Principles of circuit telecommunication services supported by a Public Land Mobile Network (PLMN)
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.001/22001-i01.zip
|
The present document covers the definition of the circuit telecommunication services supported by a PLMN. The purpose of the present document is to provide a method for the characterization and the description of these telecommunication services.
TS 22.101 describes overall service principles of a PLMN.
|
22.002
|
Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN)
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.002/22002-i01.zip
|
The present document defines a set of Circuit Bearer Services to be provided to PLMN subscribers by a PLMN itself and in connection with other networks. This TS should also be used as a reference for defining the corresponding required mobile network capabilities.
|
22.003
|
Circuit Teleservices supported by a Public Land Mobile Network (PLMN)
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.003/22003-i01.zip
|
This Technical Specification (TS) describes and defines a recommended set of Circuit Teleservices to be supported by a PLMN in connection with other networks as a basis for defining the network capabilities required.
|
22.004
|
General on supplementary services
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.004/22004-i01.zip
|
The purpose of the present document is to define a recommended set of supplementary services to the Teleservices and Bearer services which will be supported by a PLMN in connection with other networks as a basis for the definition of the network capabilities required.
Supplementary services not covered in 3GPP TS 22.004 cannot be introduced unilaterally in any PLMN if they require modification of the signalling Specifications.
Technical realization of supplementary services is described in 3GPP TS 23.011 [19] and 24.010 [21].
|
22.016
|
International Mobile station Equipment Identities (IMEI)
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.016/22016-i01.zip
|
The present document defines the principal purpose and use of International Mobile station Equipment Identities (IMEI).
3GPP TS 23.003 describes the technical manner of numbering, addressing and identification.
|
22.022
|
Personalisation of Mobile Equipment (ME); Mobile functionality specification
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.022/22022-i01.zip
|
The present document provides functional specifications of five features to personalise Mobile Equipment (ME) for GSM and 3G systems. These features are called:
‑ Network personalisation;
‑ Network subset personalisation;
‑ Service Provider (SP) personalisation;
‑ Corporate personalisation;
‑ SIM/USIM personalisation (SIM for GSM systems or USIM for 3G systems).
The present document specifies requirements for MEs which provide these personalisation features.
|
22.024
|
Description of Charge Advice Information (CAI)
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.024/22024-i01.zip
|
The charging supplementary service is described in TS 22.086 [2]. These services are designed to supply to a mobile user sufficient information to allow a real‑time estimate to be made of the bill which will eventually be levied in the home PLMN on the Mobile Station (MS) subscriber.
In the case of certain MS uses, for example a mobile payphone, this estimate could be subject to further processing (e.g. to present the charges in currency, rather than units, this may include an additional mark up). This additional processing is not described in this document in order to avoid constraining the evolution of the MS product in this area.
This document gives an overall view of how this supplementary service shall operate both in the PLMN and within the MS. Text given in this document is required to define functionality and is not intended to constrain implementation.
|
22.030
|
Man-Machine Interface (MMI) of the User Equipment (UE)
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.030/22030-i01.zip
|
The present document defines the requirements for and gives guidelines on the MMI on the User Equipment (UE). This includes the requirements of the user procedures for call control and supplementary service control, the requirements on the physical input media and the output, such as indications and displayed information.
Some clauses of the present document include the requirements that are applicable only to UE connected to CS Domain. See 3GPP TS 22.101 [18]; for overall service principles and 3GPP TS 22.001 [19] for Circuit telecommunication services.
|
22.031
|
3G Security; Fraud Information Gathering System (FIGS); Service description; Stage 1
|
TS
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.031/22031-i00.zip
|
This Technical Specification specifies the stage 1 description of the Fraud Information Gathering System (FIGS) feature which provides the means for the HPLMN to monitor the activities of its subscribers in a VPLMN.
The purpose of this network feature is to enable the HPLMN to monitor the activities of its subscribers while they are roaming. The VPLMN collects information about a defined set of activities on monitored subscribers and sends this information back to the HPLMN. This enables the HPLMN to clear certain types of calls and so stop fraudulent use of the GSM system.
This specification enables 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 subscribers producing large unpaid bills.
HPLMNs may also choose to monitor the activities of its subscribers within the HPLMN.
|
22.032
|
Immediate Service Termination (IST); Service description; Stage 1
|
TS
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.032/22032-i00.zip
|
This Technical Specification specifies the stage 1 description of the Immediate Service Termination (IST) service which provides the means for the HPLMN to terminate all the activities of an HPLMN subscriber in a VPLMN.
The purpose of this network feature is to enable the HPLMN to control the activities of its subscribers, particularly while they are roaming. If the HPLMN decides (based upon information received via Fraud Information Gathering System (FIGS) or other systems) that a roaming subscriber is behaving in a fraudulent or suspicious manner, the HPLMN can terminate all activities of the subscriber, including calls (including transferred and diverted calls) that are in progress.
This procedure can also be used to terminate all the activities of a subscriber when the subscription has ended.
The primary aim is to enable service providers/network operators to use IST to reduce the amount of money that they lose because of roaming fraud.
|
22.034
|
High Speed Circuit Switched Data (HSCSD); Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.034/22034-i01.zip
|
The present document specifies the Stage 1 description of High Speed Circuit Switched Data (HSCSD). HSCSD is a feature that introduce General Bearer Services and a multislot mechanism is used for user rates that can be achieved with one or more TCH/F. Multislot also defines a flexible use of air interface resources which makes efficient and flexible use of higher user rates feasible.
The Multislot mechanism is only applicable to GERAN.
At UTRAN radio access parameters used for GBS user data are specified at TS 23.107.
|
22.038
|
(U)SIM Application Toolkit (USAT); Service description; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.038/22038-i01.zip
|
This 3GPP Technical Specification defines the stage one description of the USIM application Toolkit (USAT). Stage one is an overall service description, primarily from the subscriber’s and serving environment's points of view, and does not deal with the details of the human interface itself.
This TS includes information applicable to network operators, serving environments and terminal, switch and database manufacturers.
This TS contains the core requirements for a USIM application Toolkit (USAT) which are sufficient to provide a complete service.
It is highly desirable however, that technical solutions for a USIM application Toolkit (USAT) are sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in this TS may implement requirements which are considered outside the scope of this TS. This additional functionality may be on a network-wide basis, nation-wide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the core requirements of the service.
Figure 1: Scope of this TS
As indicated in Figure 1, the scope of this TS encompasses the USAT functionality in the UE (comprising USIM and ME) and the interaction with the PLMN environment. The USAT Server is not necessarily a separate entity as shown in the figure; nodes providing USAT services may also exist within the PLMN. The functionalities of the USAT servers (such as charging aspects, security level classification etc.) are not covered by this specification.
The requirements are considered to be applicable to both GSM and UMTS systems.
|
22.041
|
Operator Determined Barring (ODB)
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.041/22041-i01.zip
|
The present document describes the network feature Operator Determined Barring (ODB).
This allows the network operator or service provider to regulate, by means of an exceptional procedure, access by the subscribers to services (both Circuit and Packet Oriented),, by the barring of certain categories of outgoing or incoming calls/Packet Oriented Services or of roaming. ODB shall take effect immediately and shall terminate ongoing calls and bar future calls/Packet Oriented Services.
The purpose of this network feature is to be able to limit the service provider's financial exposure to new subscribers, or to those who have not promptly paid their bills. It may only be applied to the service provider's own subscribers.
|
22.042
|
Network Identity and TimeZone (NITZ); Service description; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.042/22042-i01.zip
|
The present document describes the feature Network Identity and Timezone (NITZ).
This feature provides the means for serving PLMNs to transfer current identity, time, Daylight Saving Time and the local timezone to Mobile Stations (MS)s, and for the MSs to store and use this information. This enhances roaming by permitting accurate indication of PLMN identities that are either newer than the Mobile Equipment (ME) or have changed their name since the ME was sold. Additionally time, Daylight Saving Time and timezone information can be utilised by MEs as desired.
|
22.053
|
Tandem Free Operation (TFO); Service description; Stage 1
|
TS
|
18.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.053/22053-i00.zip
|
The present document specifies the stage 1 description for the Tandem Free Operation (TFO) feature which provides the capability to avoid tandeming speech codecs in mobile to mobile speech calls. The primary aim is to realise improvements in speech quality. The TFO mode of operation could also be used to reduce inter-Mobile services Switching Center (MSC) transmission bandwidth requirements.
In analogy with ITU-T Recommendations I.130 [1], Stage 1 is an overall service description, from the service subscriber's and user's standpoints, that views the network as a single entity which provides services to the user.
|
22.057
|
Mobile Execution Environment (MExE); Service description; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.057/22057-i01.zip
|
This TS defines the stage one description of the Mobile Execution Environment (MExE). Stage one is an overall service description, primarily from the subscriber’s and service providers’ points of view, and does not deal with the details of the human interface itself.
This 3GPP TS includes information applicable to network operators, service providers and terminal, switch and database manufacturers.
This 3GPP TS contains the core requirements for a Mobile Execution Environment (MExE) which are sufficient to provide a complete service.
It is highly desirable however, that technical solutions for a Mobile Execution Environment (MExE) should be sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in this 3GPP TS may implement requirements which are considered outside the scope of this 3GPP TS. This additional functionality may be on a network-wide basis, nation-wide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the core requirements of the service.
Figure 1: Scope of this 3GPP TS
As indicated in Figure 1, the scope of this 3GPP TS encompasses the MExE functionality in the UE, interaction with the MExE service environment. The MExE service environment is not necessarily restricted to the PLMN, and nodes providing MExE services (i.e. MExE servers) may also exist outside the PLMN. Aspects of the support provided by MExE servers within the MExE service environment (such as charging aspects, security level classification etc.) are covered by this specification, but not the MExE servers themselves.
|
22.060
|
General Packet Radio Service (GPRS); Service description; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.060/22060-i01.zip
|
This TS defines the stage one description of the General Packet Radio Service (GPRS). Stage one is an overall service description, primarily from the service subscriber's and user's points of view, but does not deal with the details of the human interface itself. This TS includes information applicable to network operators, service providers and terminal, switch and data base manufacturers.
This TS contains the core requirements for the packet switched networks specified by 3GPP which are sufficient to provide a complete service. It defines a set of bearer services that provide packet mode transmission within the PLMN and interwork with external networks.
The term GPRS shall be used in this document to refer the GPRS service offered via GERAN and UTRAN and the PS Domain of the 3G PLMN.
The GPRS shall not prevent the user's operation of other 3GPP services.
|
22.066
|
Support of Mobile Number Portability (MNP); Service description; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.066/22066-i01.zip
|
This TS defines the stage one description of the Support of Mobile Number Portability between networks in the same country as well as North America cross-sector portability (i.e.,. number portability between fixed and 3GPP system). Stage one is an overall service description, primarily from the service subscriber's and user's points of view, but does not deal with the details of the human interface itself.
Mobile Number Portability (MNP) is applicable only to those telecommunication services identified by an MSISDN.
This specification includes information applicable to network operators, service providers and terminal, switch and database manufacturers.
This specification contains the core requirements for the Support of Mobile Number Portability between network operators in the same country as well as North America cross-sector portability which are sufficient to provide a complete service.
Other cross-sector portability options (e.g. number portability between fixed and mobile networks outside the North American Region) are outside the scope of this technical specification. It is highly desirable however, that technical solutions for MNP should be sufficiently flexible to allow for possible enhancements, e.g. cross-sector number portability, and MNP between analogue and digital mobile networks. Additional functionalities not documented in this specification may implement requirements which are considered outside the scope of this specification. This additional functionality may be on a network-wide basis, nation-wide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the core requirements of the service.
Porting between Service Providers (i.e. service provider portability) which does not involve a change of Network Operator is outside the scope of this specification.
The relationship between Service Providers and Network Operators is outside the scope of this specification.
The relationship between a Service Provider and subscriber is outside the scope of this specification. The interface between the User Equipment (UE) and any external applications are outside the scope of this specification. Charging principles are outside the scope of this specification except where explicitly stated in the text.
|
22.067
|
enhanced Multi Level Precedence and Pre-emption service (eMLPP); Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.067/22067-i01.zip
|
The present document specifies the stage 1 description of the enhanced Multi‑Level Precedence and Pre‑emption Service (eMLPP). This service has two parts: precedence and pre‑emption. Precedence involves assigning a priority level to a call in combination with fast call set‑up. Pre‑emption involves the seizing of resources, which are in use by a call of a lower precedence, by a higher level precedence call in the absence of idle resources. Pre‑emption can also involve the disconnection of an on‑going call of lower precedence to accept an incoming call of higher precedence.
The eMLPP service is provided as a network operator's option to a domain of a network. The domain can be the whole network or a subset of the network. The eMLPP service applies to all network resources in the domain that is in common use. The eMLPP service is applicable to all mobile stations in the domain with all or some mobile stations having a respective subscription assigning precedence according to the eMLPP service.
eMLPP is a supplementary service and shall be provided to a subscriber for all basic services subscribed to and for which eMLPP applies.
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 services and features.
The present document does not deal with the Man‑Machine Interface (MMI) requirements, but makes reference to the appropriate specifications.
The present document is applicable to teleservices 1x and 6x and to all bearer services used in a mobile network if eMLPP is provided. Any interaction with other services and/or networks not dealt with in clauses 8 or 9 are outside the scope of the present document.
|
22.071
|
Location Services (LCS); Service description; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.071/22071-i01.zip
|
This document provides the Stage One description of Location Services (LCS). A Stage One description provides an overall service description, primarily from the service subscriber's and user's points of view, but not dealing with the details of the Man Machine Interface (MMI). This TS includes information applicable to network operators, service providers and terminal, base station system, switch, and data base manufacturers.
NOTE: Location Services may be considered as a network provided enabling technology consisting of standardized service capabilities which enable the provision of location-based applications. These applications 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 this specification. However, clarifying examples of how the functionality being specified may be used to provide specific location services is included in various sections of the specification.
This document provides core requirements to an extent sufficient to derive a complete definition of location services at the service level. However, the present document also provides additional requirements which may suggest in a non-normative manner certain ways the system may be implemented to support location services.
LCS can be offered without subscription to basic telecommunication services. LCS is available to the following categories of LCS clients:
Value Added Services LCS Clients – use LCS to support various value-added services. These clients can include UE subscribers as well as non-subscribers to other services.
PLMN Operator LCS Clients – use LCS to enhance or support certain O&M related tasks, supplementary services, IN related services and bearer services and teleservices.
Emergency Services LCS Clients – use LCS to enhance support for emergency calls from subscribers.
Lawful Intercept LCS Clients – use LCS to support various legally required or sanctioned services.
LCS is applicable to any target UE whether or not the UE supports LCS, but with restrictions on choice of positioning method or notification of a location request to the UE user when LCS or individual positioning methods, respectively, are not supported by the UE.
LCS is being developed in phases with enhancements added in 3GPP releases.
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.
|
22.072
|
Call Deflection (CD) service description; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.072/22072-i01.zip
|
Call Deflection (CD) enables the served mobile subscriber to respond to an incoming call offered by the network by requesting redirection of this call to another number specified in the response. The CD supplementary service can only be invoked before the connection is established by the served mobile subscriber, i.e. in response to the offered call, or during the period that the served subscriber is being informed of the call. The served subscriber’s ability to originate calls is unaffected by the CD supplementary service.
|
22.076
|
Noise suppression for the AMR codec; Service description; Stage 1
|
TS
|
18.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.076/22076-i00.zip
|
The present document specifies the stage 1 description for the Noise Suppression feature for the AMR codec which enhances the input speech signal corrupted by acoustic noise. In analogy with ITU-T Recommendations I.130 [1], Stage 1 is an overall service description, from the service subscriber's and user's standpoints, that views the network as a single entity which provides services to the user.
|
22.078
|
Customised Applications for Mobile network Enhanced Logic (CAMEL); Service description; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.078/22078-i01.zip
|
This standard specifies the stage 1 description for the CAMEL feature (Customised Applications for Mobile network Enhanced Logic) which provides the mechanisms to support services consistently independently of the serving network. The CAMEL features shall facilitate service control of operator specific services external from the serving PLMN. The CAMEL feature is a network feature and not a supplementary service. It is a tool to help the network operator to provide the subscribers with the operator specific services even when roaming outside the HPLMN.
If an IPLMN or VPLMN supports CAMEL Phase 4, it shall also provide the functionality of all previous CAMEL phases.
Phase 4 network signalling shall support interworking with CAMEL Phases 3 and 2.
The CAMEL feature is applicable
- To mobile originated and mobile terminated call related activities;
- To supplementary service invocations;
- To SMS MO, to GPRS sessions and PDP contexts, to the control of HLR subscriber data, to the control of network signalling load.
The mechanism described addresses especially the need for information exchange among the VPLMN, HPLMN and the CAMEL Service Environment (CSE) for support of such operator specific services. Any user procedures for operator specific services are outside the scope of this standard.
This specification describes the interactions between the functions of the VPLMN, HPLMN, IPLMN and the CSE.
The second phase of CAMEL enhances the capabilities of phase 1 where the following capabilities have been added:
- Additional event detection points;
- Interaction between a user and a service using announcements, voice prompting and information collection via in band interaction or USSD interaction;
- Control of call duration and transfer of Advice of Charge Information to the mobile station;
- The CSE can be informed about the invocation of the supplementary services ECT, CD and MPTY;
- For easier post-processing, charging information from a serving node can be integrated in normal call records.
The third phase of CAMEL enhances the capabilities of phase 2. The following capabilities are added:
- Support of facilities to avoid overload;
- Capabilities to support Dialled Services;
- Capabilities to handle mobility events, such as (Not-)reachability and roaming;
- Control of GPRS sessions and PDP contexts;
- Control of mobile originating SMS through both circuit switched and packet switched serving network entities.
- Interworking with SoLSA. (Support of Localised Service Area). Support for this interworking is optional.
- The CSE can be informed about the invocation of the supplementary services CCBS.
Detailed information is given in the respective sections.
The fourth phase of CAMEL enhances the capabilities of phase 3. The following capabilities are added:
- CAMEL support for Optimal Routeing of circuit-switched mobile-to-mobile calls;
- The capability for the CSE to create additional parties in an existing call;
- The capability for the CSE to create a new call unrelated to any other existing call;
- Capabilities for the enhanced handling of call party connections;
- The capability for the CSE to control sessions in the IP Multimedia Subsystem.
- Enhanced CSE capability for Dialled Services.
- The capability to report basic service changes during ongoing call.
- The CSE capability to select between preferred and less preferred bearer service.
- The capability for the CSE to control trunk originated calls.
- The capability for the CSE to request additional dialled digits.
With CAMEL Phase 4, it is possible that only a limited subset of the new functionalities is supported, in addition to the complete support of CAMEL Phase 3.
|
22.079
|
Support of Optimal Routeing (SOR); Service definition; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.079/22079-i01.zip
|
This Stage 1 description of the first phase of Support of Optimal Routing (SOR):
- compiles the basic service requirements for SOR;
- describes the interactions for Supplementary Services (SS) in order to cater for SOR;
- refers to modifications to network features required by SOR.
This specification does not address the following:
- There is no need for optimisation of the routing of calls originally directed to a fixed network subscriber, because the physical address of a fixed network terminating line cannot differ from its logical address.
- SOR in non-PLMNs is not a subject of this TS, but might be possible by bilateral arrangement between PLMN operators and those non-PLMN operators.
The purpose of SOR is to reduce the number of unnecessary inter-PLMN call legs.
The first phase of SOR applies to:
- OR for the benefit of the B party i.e. Mobile terminated calls with late call forwarding to the home or visited country (scenarios 1 and 2),
and optionally;
- OR for the benefit of the A party, e.g. Mobile to mobile calls where both mobile subscribers are in the same country (scenarios 3 to 10).
The complete set of scenarios included in the phase 1 of OR is presented in the paragraph for normal procedures. All other scenarios are excluded from Phase 1 of OR.
Note that Optimal Routing is applicable to national roaming situations, that is to calls directed to a mobile subscriber roaming in her home country, but registered in a PLMN different from her HPLMN.
All further call scenarios, including multiple call forwarding, are left to subsequent phases of SOR. Subsequent phases of SOR shall be backwards compatible with this first phase.
|
22.081
|
Line Identification supplementary services; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.081/22081-i01.zip
|
The present document describes the Supplementary Services belonging to the group Line Identification Supplementary Services.
The general aspects, including definitions and recommended provision, of the description of the Supplementary Services are given in 3GPP TS 22.004.
The group of Line Identification Supplementary Services is divided into the following four Supplementary Services:
CLIP - Calling line identification presentation (clause 1);
CLIR - Calling line identification restriction (clause 2);
COLP - Connected line identification presentation (clause 3);
COLR - Connected line identification restriction (clause 4).
Definition of line identity: The line identity is made up of a number of information units:
- the subscriber's national ISDN/MSISDN number (MSISDN number is the number stored in the VLR);
- the country code;
- optionally, subaddress information. The PLMN cannot be responsible for the content of this subaddress. (For definition of the subaddress see ITU-T Recommendation E.164 [3] subclause 11.2).
In a full ISDN environment, the line identity shall include all the address information necessary to unambiguously identify a subscriber.
The calling line identity is the line identity of the calling party.
The connected line identity is the line identity of the connected party.
If for the line identity of the calling party or the connected party additional line identification is received (additional calling party/connected party number) in a PLMN this additional line identification shall be used for the presentation purpose of the line identification presentation services.
Definition of Presentation and Screening Indicators: In addition to or instead of the line identity, the network may give a Presentation Indicator (PI) and/or a Screening Indicator (SI) to the served subscriber. The following information may be given:
- Presentation Indicator showing:
a) presentation allowed, or
b) presentation restricted, or
c) number not available due to interworking;
If Presentation Indicator is set to "Presentation Restricted", then the MS can get additional information on the Cause of no CLI, if provided by the network.
The Cause of no CLI value may be one of the following :
- Unavailable
- reject by user
- interaction with other services
- coin line / pay phone
- Screening Indicator showing:
a) user provided, verified and passed, or
b) user provided, not screened, or
c) network provided.
If the line identity is that of a PLMN subscriber, then:
the national number and the country code shall always be provided by the network;
the subaddress shall only be included if it is provided by the user (or user equipment);
the screening indicator shall indicate "network provided".
|
22.082
|
Call Forwarding (CF) Supplementary Services; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.082/22082-i01.zip
|
This specification describes the supplementary services belonging to the group CALL OFFERING SUPPLEMENTARY SERVICES.
The general aspects, including definitions and recommended provision, of the description of the supplementary services are given in specification 3TS 22.004.
The group of supplementary services CALL OFFERING SUPPLEMENTARY SERVICES is divided into four different supplementary services:
- Call forwarding unconditional (section 1);
- Call forwarding on mobile subscriber busy (section 2);
- Call forwarding on no reply (section 3);
- Call forwarding on mobile subscriber not reachable (section 4).
Indication of active Call forwarding supplementary service.
An indication that a Call forwarding service is currently active and operative on a number will be given to the forwarding party each time an outgoing call is made. There will be one indication for Unconditional call forwarding and another common indication for the Conditional call forwarding services.
Note on the use of the forwarded-to number at registration.
If the forwarded-to number is a number in the HPLMN country, it may be entered by the served mobile subscriber in three different formats, independent of her actual location, according to the schemes:
1) National (significant) number.
2) National (trunk) prefix plus national (significant) number.
3) International prefix*, country code, national (significant) number.
Scheme 3) Storage of numbers in this format is mandatory for all PLMN operators.
If the forwarded-to number is a number in a country other than the HPLMN country, it shall be entered by the served mobile subscriber, independent of her actual location, according to the following scheme:
- International prefix (NOTE), country code, national (significant) number.
NOTE: The MMI for entering of international prefix is defined in 22.030.
The maximum forwarded-to number length is 28 digits.
Principles for interaction with the Barring of Outgoing Calls supplementary services.
Numbers allowed to call according to the Barring of Outgoing call service condition are allowed as forwarded-to numbers for the served mobile subscriber.
Numbers not allowed to call according to the Barring of Outgoing call service condition are not allowed as forwarded-to numbers for the served mobile subscriber.
For Unconditional Call Forwarding the forwarded leg is treated as an outgoing call from the HPLMN country.
For the Conditional Call Forwarding services the forwarded leg is treated as an outgoing call from the LPLMN (HPLMN or VPLMN) country.
Principles for interaction with the Barring of Incoming Calls supplementary services.
When Barring of all incoming calls is active for the served mobile subscriber - no Call forwarding services are allowed for her.
When Barring of all incoming calls when roaming outside the HPLMN country is active and operative - i.e. the served mobile subscriber is roaming outside the HPLMN country, the Conditional Call Forwarding services are not allowed.
|
22.083
|
Call Waiting (CW) and Call Holding (HOLD); Supplementary Services; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.083/22083-i01.zip
|
The present document describes the Supplementary Services belonging to the group Call Completion Supplementary Services.
The general aspects, including definitions and recommended provision, of the description of Supplementary Services are given in specification TS 22.004 [2].
The group of Call Completion Supplementary Services is divided into the following two Supplementary Services:
- Call waiting (clause 1);
- Call hold (clause 2).
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.