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
|
|---|---|---|---|---|---|---|
49.995
|
General Packet Radio Service (GPRS); Interworking between modified Public Land Mobile Network (PLMN) supporting GPRS and legacy GPRS mobiles
|
TR
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/49_series/49.995/49995-i00.zip
|
This report describes issues relating to the GPRS specifications, which lead to the specifications being modified after the placement of GPRS compliant mobiles into the market place.
Where possible the present report clarifies any recommended measures which may be adopted by the GPRS infrastructure to enable interworking to be obtained between the GPRS infrastructure and legacy Mobile Station (MS) implementations of the GPRS specifications.
For each issue this report also defines the time after which all new GPRS mobiles are required to meet the modified specifications.
The lifetime of the herein described measures together with their potential impact on optimal network performance is out of the scope of the present document.
|
48.071
|
Location Services (LCS); Serving Mobile Location Centre - Base Station System (SMLC-BSS) interface; Layer 3 specification
|
TS
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/48_series/48.071/48071-i00.zip
|
The present document contains the coding of information necessary for support of location service operation on the SMLC-BSS interface layer 3.
Clause 2 gives the functional definitions and contents of messages for location service operations. Clause 3 gives the general format and coding for messages used for location service and the format and coding of information elements used for location service operations.
|
48.103
|
Base Station System - Media GateWay (BSS-MGW) interface; User plane transport mechanism
|
TS
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/48_series/48.103/48103-i00.zip
|
The present document specifies the User Plane data transport protocols used between BSSs and the Core Network (MGWs) across the A interface. The main purpose of the present document is the AoIP description, however for the sake of completeness the AoTDM case is described as well.
Figure 1.1: CS core network logical architecture
Note that the present document does not preclude any Core Network Session Control Protocol implementation (BICC or SIP-I).
|
51.013
|
Test specification for Subscriber Identity Module (SIM) Application Programming Interface (API) for Java Card
|
TS
|
18.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/51_series/51.013/51013-i00.zip
|
The present document covers the minimum characteristics considered necessary in order to provide compliance to 3GPP TS 43.019 [7].
The present document describes the technical characteristics and methods of test for testing the SIM API for Java CardTM (3GPP TS 43.019 [7]) implemented in the Subscriber Identity Modules (SIMs) for GSM. It specifies the following parts:
- test applicability;
- test environment description;
- tests format;
- test area reference;
- conformance requirements;
- test auite files;
- test procedure;
- test coverage; and
- a description of the associated testing tools that shall be used.
|
51.021
|
Base Station System (BSS) equipment specification; Radio aspects
|
TS
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/51_series/51.021/51021-i00.zip
|
The present document specifies the Radio Frequency (RF) test methods and conformance requirements for GSM 400, GSM 700, T-GSM 810, GSM 900, ER-GSM 900 and DCS 1800, PCS 1900, GSM 850, MXM 850 and MXM 1900 Base Station Systems (BSS)s. These have been derived from, and are consistent with, the core GSM specifications specified in the requirements reference subclause of each test with the exception that requirements expressed as a reference to regulatory documents (e.g. FCC) have not been included in the present document.
The present document is applicable to BSS meeting the requirements of either GSM Phase 2 or GSM Phase 2+. Unless otherwise stated, all tests are applicable to BSS meeting Phase 2 and/or Phase 2+ GSM requirements, because the requirements of the Phase 2 and Phase 2+ core GSM specifications which are referenced in the test are consistent. Most differences between Phase 2 and Phase 2+ requirements represent Phase 2+ features which are optional for the BSS to support.
Conformance requirements may be tested to verify all aspects of the performance of a BSS. These minimum requirements are intended to be used by manufacturers and operators to allow conformance and acceptance testing to be performed in a consistent manner; the tests to be performed should be agreed between the parties.
In some tests there are separate requirements for micro‑BTS and BTS. If there is no separate requirement for a micro‑BTS, the requirements for the BTS apply to a micro‑BTS.
In Rel-7, higher symbol rate is introduced for EGPRS2-B. EGPRS2-A and all other channels use normal symbol rate. For definition of normal and higher symbol rate see 3GPP TS 45.004. All tests and requirements apply to both symbol rates except otherwise stated in the test.
In some tests there are separate requirements for multicarrier BTS, that apply for all classes of multicarrier BTS (Wide Area, Medium Range and Local Area, cf. [22]) unless otherwise stated. If there is no separate requirement for a multicarrier BTS class, the requirement designated for BTS and normal BTS apply to that multicarrier BTS class.
In Rel-12, BTS operating in the ER-GSM 900 band is introduced. In some tests there are separate requirements for BTS operating in the ER-GSM 900 band. If there is no separate requirement, the requirements for normal BTS apply.
In Rel-13, BTS support of a low-complexity, low data throughput service in environments experiencing high propagation attenuation as indoors in basements etc. is introduced. This service, based on EGPRS, with extended coverage is called EC-GSM-IoT. The requirements for EGPRS apply in case no specific requirement is explicitly stated for EC-GSM-IoT.
In the present document, the reference point for RF connections (except for the measurement of mean transmitted RF carrier power) is the antenna connector, as defined by the manufacturer. The present document does not apply to repeaters or RF devices which may be connected to an antenna connector of a BSS, except as specified in subclause 4.10.
|
49.031
|
Location Services (LCS); Base Station System Application Part LCS Extension (BSSAP-LE)
|
TS
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/49_series/49.031/49031-i00.zip
|
The present document specifies procedures and information coding that are needed to define and support the BSSAP LCS Extension (BSSAP-LE). The BSSAP-LE message set is applicable to the following GSM interfaces defined in 3GPP TS 43.059:
- Lb interface (BSC-SMLC).
- Lp interface (SMLC-SMLC).
The present document defines message formats and encoding for BSSAP-LE and the particular subsets of it that are applicable to each of the above interfaces. The present document also defines the support for BSSAP-LE message transfer on each of these interfaces using either ITU-T and ANSI versions of SS7 MTP or IETF M3UA/SCTP and SCCP. Additional requirements for the above interfaces that are applicable to BSSAP-LE are also defined – e.g. usage of BSSAP (as defined in 3GPP TS 24.008 and 48.008) on the Lb interface.
|
52.008
|
Telecommunication management; GSM subscriber and equipment trace
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/52_series/52.008/52008-i00.zip
|
The present document specifies the Trace facility for GSM where it refers to:
- subscriber tracing (tracing of International Mobile Subscriber Identity (IMSI));
- equipment tracing (tracing of International Mobile station Equipment Identity (IMEI)).
It does not cover:
- types of trace which relate more to network elements than to individual subscribers e.g. tracing events within a Base Station System (BSS), and so on;
- tracing of all possible parties in e.g. a multi-party call, (although multiple calls related to the IMSI specified in the trace type field are traceable).
It also refers only to tracing activated from the OSF and not to that activated by means of local Man Machine Interface (MMI).
|
51.010-4
|
Mobile Station (MS) conformance specification; Part 4: Subscriber Identity Module (SIM) application toolkit conformance test specification
|
TS
|
18.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/51_series/51.010-4/51010-4-i00.zip
|
The present document describes the technical characteristics and methods of test for testing the SIM Application Toolkit implemented in Mobile Stations (MS) for the Pan European digital cellular communications system and Personal Communication Systems (PCS) operating in the 450 MHz, 480 MHz, 700 MHz, 750 MHz, 850 MHz, 900 MHz, 1 800 MHz and 1 900 MHz frequency band (GSM 400, GSM 700, GSM 750, GSM 850, GSM 900, DCS 1 800 and PCS 1 900) within the European digital cellular telecommunications system, in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646‑7 [19] and ETS 300 406 [20].
The present document is valid for MS implemented according to GSM Phase2+ R96, or R97, or R98, or R99.
The present document covers the minimum characteristics considered necessary in order to provide sufficient performance for mobile equipment and to prevent interference to other services or to other users, and to the PLMNs.
It does not necessarily include all the characteristics which may be required by a user or subscriber, nor does it necessarily represent the optimum performance achievable.
The present document is part of the GSM-series of technical specifications. The present document neither replaces any of the other GSM technical specifications or GSM related ETSs or ENs, nor is it created to provide full understanding of (or parts of) the GSM 400, GSM 700, GSM 850, GSM 900, DCS1800 and PCS1900 systems . The present document lists the requirements, and provides the methods of test for testing the SIM Application Toolkit implemented in a MS for conformance to the GSM standard.
For a full description of the system, reference should be made to all the GSM technical specifications or GSM related ETSs or ENs. Clause 2 provides a complete list of the GSM technical specifications, GSM related ETSs, ENs, and ETRs, on which this conformance test specifications is based.
If there is a difference between this present conformance document, and any other GSM technical specification or GSM related ETS or EN, or 3GPP TS, then the other GSM technical specification or GSM related ETS or EN or 3GPP TS shall prevail.
Normative requirements for the SIM and SIM Application Toolkit are only specified up to Rel-4. The present document is only available in this release for allowing maintenance of test cases. The core features related to those test cases remain applicable only to the releases in which they have been specified.
|
49.008
|
Application of the Base Station System Application Part (BSSAP) on the E interface
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/49_series/49.008/49008-i00.zip
|
The present document describes the subset of Base Station System Application Part (BSSAP) messages and procedures, defined in 3GPP TS 48.006 and 3GPP TS 48.008, which is used on the E‑interface. A general description can be found in 3GPP TS 23.002 and 3GPP TS 23.009.
For the initiation and execution of handover between MSCs a subset of BSSMAP procedures are used. For the subsequent control of resources allocated to the Mobile Station (MS) BSSMAP procedures are used. DTAP is used for the transfer of connection management and mobility management messages between the MS and the controlling MSC.
|
51.026
|
Base Station System (BSS) equipment specification; Part 4: Repeaters
|
TS
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/51_series/51.026/51026-i00.zip
|
The present document describes the Radio Frequency (RF) tests for GSM repeaters (frequency bands according to clause 4.1) which receive, amplify, and retransmit a received Mobile Station (MS) signal in the GSM MS transmit band and simultaneously receive, amplify and retransmit a received Base Transceiver Station (BTS) RF signal in the GSM BTS transmit band.
The present document is applicable to repeaters meeting the requirements of either GSM Phase 2 or GSM Phase 2+. Unless otherwise stated, all tests are applicable to repeaters meeting Phase 2 and/or Phase 2+ GSM requirements, because the requirements of the Phase 2 and Phase 2+ core GSM specifications which are referenced in the test are consistent. Most differences between Phase 2 and Phase 2+ requirements represent Phase 2+ features which are optional for the BSS to support.
|
55.217
|
3G Security; Specification of the A5/3 encryption algorithms for GSM and ECSD, and the GEA3 encryption algorithm for GPRS; Document 2: Implementors' test data
|
TS
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/55_series/55.217/55217-i00.zip
|
The present document specifies mplementors' test data for the A5/3 and GEA3 specification. 0A 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 Task Force Specification: "Specification of the A5/3 encryption algorithms for GSM and EDGE, and the GEA3 encryption algorithm for GPRS; Document 2: Implementors' test data". Note: Reference [2] is available via http://portal.etsi.org/dvbandca/home.asp and is subject to licensing conditions described at this site. 0B Definitions, symbols and abbreviations 0B.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and in the 3GPP Task Force Specification [2] apply. A term defined in the latter document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. 0B.2 Symbols For the purposes of the present document, the symbols defined in the 3GPP Task Force Specification [2] apply. 0B.3 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 [2] and in the 3GPP Task Force Specification [2] apply. An abbreviation defined in the latter document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. 0C Technical provisions The technical provisons of the current document are contained in the 3GPP Task Force Specification [2]. Annex A: Change history Change history Date TSG # TSG Doc. CR Rev Subject/Comment Old New 2002-05 - - - - ETSI SAGE first publication SAGE V1.0 2002-07 - - - - Agreed at SA WG3 #24 for presentation to TSG SA #17 for approval. Converted into 3GPP TS format (TS 55.217) (Technically equivalent to SAGE V1.0) SAGE V1.0 1.0.0 2002-09 SP-17 SP-020506 - - Approved for Release 6 - version 6.0.0 1.0.0 6.0.0 2002-12 SP-18 SP-020721 001 - EGPRS algoritm 6.0.0 6.1.0 2007-12 SP-38 SP-070776 002 - Conversion to pointer to export controlled document 6.1.0 7.1.0 2008-12 SP-42 - - - Upgrade to Release 8 7.1.0 8.0.0 2009-12 SP-46 - - - Upgrade to Release 9 8.0.0 9.0.0 Note: Version 7.0.0 is a "readme" file placeholder with no technical content. 2011-03 SP-51 -- -- -- Upgrade to Release 10 9.0.0 10.0.0 2012-09 - - - - Update to Rel-11 version (MCC) 10.0.0 11.0.0 2014-09 - - - - Update to Rel-12 version (MCC) 11.0.0 12.0.0 2016-01 - - - - Update to Rel-13 version (MCC) 12.0.0 13.0.0 2017-03 SA#75 - - - Promotion to Release 14 without technical change 13.0.0 14.0.0 2018-06 - - - - Update to Rel-15 version (MCC) 14.0.0 15.0.0 2020-07 - - - - Update to Rel-16 version (MCC) 15.0.0 16.0.0 2022-03 - - - - Update to Rel-17 version (MCC) 16.0.0 17.0.0 2024-03 - - - - Update to Rel-18 version (MCC) 17.0.0 18.0.0
|
55.218
|
3G Security; Specification of the A5/3 encryption algorithms for GSM and ECSD, and the GEA3 encryption algorithm for GPRS; Document 3: Design conformance test data
|
TS
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/55_series/55.218/55218-i00.zip
|
The present document specifies the A5/3 and GEA3 specification. 0A 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 Task Force Specification: "Specification of the A5/3 encryption algorithms for GSM and ECSD, and the GEA3 encryption algorithm for GPRS; Document 3: Design and conformance test data". Note: Reference [2] is available via http://portal.etsi.org/dvbandca/home.asp and is subject to licensing conditions described at this site. 0B Definitions, symbols and abbreviations 0B.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and in the 3GPP Task Force Specification [2] apply. A term defined in the latter document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. 0B.2 Symbols For the purposes of the present document, the symbols defined in the 3GPP Task Force Specification [2] apply. 0B.3 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 [1] and in the 3GPP Task Force Specification [2] apply. An abbreviation defined in the latter document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. 0C Technical provisions The technical provisons of the current document are contained in the 3GPP Task Force Specification [2]. Annex A: (informative) Change history Change history Date TSG # TSG Doc. CR Rev Subject/Comment Old New 2002-05 - - - - ETSI SAGE first publication SAGE V1.0 2002-07 - - - - Agreed at SA WG3 #24 for presentation to TSG SA #17 for approval. Converted into 3GPP TS format (TS 55.218) (Technically equivalent to SAGE V1.0) SAGE V1.0 1.0.0 2002-09 SP-17 SP-020506 - - Approved for Release 6 - version 6.0.0 1.0.0 6.0.0 2002-12 SP-18 SP-020721 001 - EGPRS algoritm 6.0.0 6.1.0 2007-12 SP-38 SP-070776 002 - Conversion to pointer to export controlled document 6.1.0 7.1.0 2008-12 SP-42 - - - Upgrade to Release 8 7.1.0 8.0.0 2009-12 SP-46 - - - Upgrade to Release 9 8.0.0 9.0.0 Note: Version 7.0.0 is a "readme" file placeholder with no technical content. 2011-03 - - - - Update to Rel-10 version (MCC) 9.0.0 10.0.0 2012-09 - - - - Update to Rel-11 version (MCC) 10.0.0 11.0.0 2014-09 - - - - Update to Rel-12 version (MCC) 11.0.0 12.0.0 2016-01 - - - - Update to Rel-13 version (MCC) 12.0.0 13.0.0 2017-03 SA#75 - - - Promotion to Release 14 without technical change 13.0.0 14.0.0 2018-06 - - - - Update to Rel-15 version (MCC) 14.0.0 15.0.0 2020-07 - - - - Update to Rel-16 version (MCC) 15.0.0 16.0.0 2022-03 - - - - Update to Rel-17 version (MCC) 16.0.0 17.0.0 2024-03 - - - - Update to Rel-18 version (MCC) 17.0.0 18.0.0
|
55.226
|
3G Security; Specification of the A5/4 Encryption Algorithms for GSM and ECSD, and the GEA4 Encryption Algorithm for GPRS
|
TS
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/55_series/55.226/55226-i00.zip
|
This specification of the A5/4 encryption algorithms for GSM and ECSD, and of the GEA4 encryption algorithm for GPRS has been derived from TS 55.516 [1]: Specification of the A5/3 Encryption Algorithms for GSM and ECSD, and the GEA3 Encryption Algorithm for GPRS. The only essential change is the change of external key length input from 64 bits to 128 bits.
This document should be read in conjunction with the entire specification of the A5/3 and GEA3 algorithms:
- Specification of the A5/3 Encryption Algorithms for GSM and ECSD, and the GEA3 Encryption Algorithm for GPRS. Document 1: A5/3 and GEA3 Specifications.
- Specification of the A5/3 Encryption Algorithms for GSM and ECSD, and the GEA3 Encryption Algorithm for GPRS. Document 2: Implementors’ Test Data.
- Specification of the A5/3 Encryption Algorithms for GSM and ECSD, and the GEA3 Encryption Algorithm for GPRS. Document 3: Design Conformance Test Data.
The normative part of the specification of the block cipher (KASUMI) on which the A5/3, A5/4, GEA3 and GEA4 algorithms are based can be found in TS 35.202 [5].
|
55.205
|
Specification of the GSM-MILENAGE algorithms: An example algorithm set for the GSM Authentication and Key Generation Functions A3 and A8
|
TS
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/55_series/55.205/55205-i00.zip
|
The present document contains an example set of algorithms which may be used as the GSM authentication and key generation functions A3 and A8. (It is not mandatory that the particular algorithms specified in this document are used - the A3 and A8 functions are operator-specifiable rather than being fully standardised).
Section 3 (normative) introduces the algorithms and describes their input and output parameters. Section 4 (normative) defines the algorithms. Section 5 (informative) describes an alternative algorithm that some operators may prefer. Section 6 (informative) provides test data.
|
55.242
|
Specification of the GIA4 integrity algorithm for General Packet Radio Service (GPRS); Implementers' test data
|
TS
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/55_series/55.242/55242-i00.zip
|
The present document defines the implementers test data of the 3GPP integrity algorithm GIA4.
|
55.243
|
Specification of the GIA4 integrity algorithm for General Packet Radio Service (GPRS); Design conformance test data
|
TS
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/55_series/55.243/55243-i00.zip
|
The present document defines the Design conformance test data for the 3GPP integrity algorithm GIA4.
|
55.251
|
Specification of the GEA5 and GIA5 encryption algorithms for General Packet Radio Service (GPRS); GEA5 and GIA5 algorithm specification
|
TS
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/55_series/55.251/55251-i00.zip
|
The present document defines the technical details of the 3GPP confidential algorithm GEA5 and the 3GPP integrity algorithm GIA5.
|
52.402
|
Telecommunication management; Performance Management (PM); Performance measurements - GSM
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/52_series/52.402/52402-i00.zip
|
The present document describes the TMN model for the administration of measurements and the collection of measurement result data in a GSM system. It also includes the measurement definitions for GSM. The concept and functional requirements for performance management in wireless GSM and UMTS systems is set out in TS 32.401 [31].
|
55.236
|
Specification of A8_V MILENAGE Algorithm: An example algorithm for the key generation function A8_V
|
TS
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/55_series/55.236/55236-i00.zip
|
The present document contains an example algorithm which may be used as the VSTK key generation function A8_V as described in TS 43.020 [4]. (It is not mandatory that the particular algorithm specified in this document is used - the A8_V function is operator-specifiable rather than being fully standardised.)
Clause 4 introduces the algorithm and describes the input and output parameters. Clause 5 defines the algorithm. Clause 6 provides test data.
|
55.216
|
3G Security; Specification of the A5/3 encryption algorithms for GSM and ECSD, and the GEA3 encryption algorithm for GPRS; Document 1: A5/3 and GEA3 specifications
|
TS
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/55_series/55.216/55216-i00.zip
|
The present document specifies the A5/3 and GEA3 specification. 0A 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 Task Force Specification: "Specification of the A5/3 encryption algorithms for GSM and ECSD, and the GEA3 encryption algorithm for GPRS; Document 1: A5/3 and GEA3 specification" version 1.1, 2002-05-30 Note: Reference [2] is available via http://portal.etsi.org/dvbandca/home.asp and is subject to licensing conditions described at this site. 0B Definitions, symbols and abbreviations 0B.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and in the 3GPP Task Force Specification [2] apply. A term defined in the latter document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. 0B.2 Symbols For the purposes of the present document, the symbols defined in the 3GPP Task Force Specification [2] apply. 0B.3 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 [2] and in the 3GPP Task Force Specification [2] apply. An abbreviation defined in the latter document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. 0C Technical provisions The technical provisons of the current document are contained in the 3GPP Task Force Specification [2]. Annex D (informative): Change history Change history Date TSG # TSG Doc. CR Rev Subject/Comment Old New 2002-05 - - - - ETSI SAGE first publication SAGE V1.0 2002-07 - - - - Agreed at SA WG3 #24 for presentation to TSG SA #17 for approval. Converted into 3GPP TS format as TS 55.216 (Technically equivalent to SAGE V1.0) SAGE V1.0 1.0.0 2002-09 SP-17 SP-020506 - - Approved for Release 6 - version 6.0.0 1.0.0 6.0.0 2002-12 SP-18 SP-020721 001 - EGPRS algoritm 6.0.0 6.1.0 2003-09 SP-19 SP-030490 002 - Clarification on the usage of the Key length 6.1.0 6.2.0 2007-12 SP-38 SP-070776 003 - Conversion to pointer to export controlled document Note: Version 7.0.0 is a "readme" file placeholder with no technical content. 6.2.0 7.1.0 2008-12 SP-42 - - Ugrade to Release 8 7.1.0 8.0.0 2009-12 - - - - Update to Rel-9 version (MCC) 8.0.0 9.0.0 2011-03 - - - - Update to Rel-10 version (MCC) 9.0.0 10.0.0 2012-09 - - - - Update to Rel-11 version (MCC) 10.0.0 11.0.0 2014-09 - - - - Update to Rel-12 version (MCC) 11.0.0 12.0.0 2016-01 - - - - Update to Rel-13 version (MCC) 12.0.0 13.0.0 2017-03 SA#75 - - - Promotion to Release 14 without technical change 13.0.0 14.0.0 2018-06 - - - - Update to Rel-15 version (MCC) 14.0.0 15.0.0 2020-07 - - - - Update to Rel-16 version (MCC) 15.0.0 16.0.0 2022-03 - - - - Update to Rel-17 version (MCC) 16.0.0 17.0.0 2024-03 - - - - Update to Rel-18 version (MCC) 17.0.0 18.0.0
|
52.021
|
Network Management (NM) procedures and messages on the A-bis interface
|
TS
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/52_series/52.021/52021-i00.zip
|
The present document addresses the network management messages and procedures across the A-bis interface, which is defined as Qx in GSM. The information model included here defines the objects and how they are addressed for purposes of operations and maintenance activities.
There is a requirement for the A-bis interface to be open to allow interoperation between BTSs of different manufacturers working to the same BSC. The present document addresses this requirement from O&M point of view, which allows this interworking to take place. It shows the split of NM functions between BSC and BTS. The procedures and coding of the messages are specified in detail. In practice, in addition to the present document it is necessary that the content of manufacturer-dependent information fields be specified to fulfill the functionality.
It is essential for operation that a BSC can handle the functions used by all its BTSs. Therefore, all items in the present document are considered mandatory unless otherwise indicated in the present document.
|
55.252
|
Specification of the GEA5 encryption and GIA5 integrity algorithms for General Packet Radio Service (GPRS); Implementers' test data
|
TS
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/55_series/55.252/55252-i00.zip
|
The present document defines the implementers test data of the 3 GPP encryption algorithm GEA5 and integrity algorithm GIA5.
|
55.253
|
Specification of the GEA5 encryption and GIA5 integrity algorithms for General Packet Radio Service (GPRS); Design conformance test data
|
TS
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/55_series/55.253/55253-i00.zip
|
The present document defines the design conformance test data of the 3GPP encryption algorithm GEA5 and integrity algorithm GIA5.
|
55.241
|
Specification of the GIA4 integrity algorithm for General Packet Radio Service (GPRS); GIA4 specification
|
TS
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/55_series/55.241/55241-i00.zip
|
The present document defines the technical details of the 3GPP integrity algorithm GIA4.
|
55.919
|
3G Security; Specification of the A5/3 encryption algorithms for GSM and ECSD, and the GEA3 encryption algorithm for GPRS; Document 4: Design and evaluation report
|
TR
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/55_series/55.919/55919-i00.zip
|
This Technical Report has been prepared by the ETSI SAGE GSM A5/3 Task Force, and gives a detailed report on the design and evaluation of the A5/3 encryption algorithms for GSM and ECSD, and of the GEA3 encryption algorithm for GPRS (including EGPRS).
|
21.917
|
Release 17 Description; Summary of Rel-17 Work Items
|
TR
|
17.0.1
|
SP
|
https://www.3gpp.org/ftp/Specs/archive/21_series/21.917/21917-h01.zip
|
The present document provides a summary of each Release 17 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.
The present document presents the "initial state" of the Features introduced in Release 17, i.e. as they are by the time of publication of the present document. Each Feature is subject to be later modified or enhanced, over several years, by the means of Change Requests (CRs). It is therefore recommended to retrieve all the CRs which relate to the given Feature, as explained in Annex C, to further outline a feature at a given time.
|
22.826
|
Study on communication services for critical medical applications
|
TR
|
17.2.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.826/22826-h20.zip
|
The present document focuses on 5G communication services targeting the critical medical applications and enabling wireless connectivity between those applications and medical devices.
Those communication services are often submitted to (but not limited to) very low latency, high reliability, and high availability requirements and may be operated on a shared network infrastructure that also provides resources to other less demanding communication services.
|
22.829
|
Enhancement for Unmaned Aerial Vehicles (UAVs)
|
TR
|
17.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.829/22829-h10.zip
|
The present document provides use cases and analysis of UAV capabilities that may require enhanced 3GPP support.
|
22.832
|
Study on enhancements for cyber-physical control applications in vertical domains
|
TR
|
17.4.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.832/22832-h40.zip
|
The present document identifies further Stage 1 potential 5G service requirements for cyber-physical control applications in vertical domains.
The present document provides specific use cases to provide clarity and to motivate the additional service requirements. Relative to the Rel-16 baseline, there are more specific requirements or additional requirements for closely-related additional functionality in order to improve the applicability of 5G systems to vertical domains.
The aspects addressed are:
- Industrial Ethernet integration, which includes time synchronization, different time domains, integration scenarios, and support for time-sensitive networking (TSN);
- Non-public networks, non-public networks as private slices, and further implications on security for non-public networks;
- Network operation and Maintenance in 5G non-public networks for cyber-physical control applications in vertical domains; Enhanced QoS monitoring, communication service and networks diagnostics; Communication service interface between application and 5G systems, e.g. information to the network for setting up communication services for cyber-physical control applications and corresponding monitoring;
- Network performance requirements for cyber-physical control applications in vertical domains;
- Positioning with focus on the vertical dimension for Industrial IoT;
- Device-to-device/ProSe communication for cyber-physical applications in vertical domains.
|
22.836
|
Study on asset tracking use cases
|
TR
|
17.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.836/22836-h10.zip
|
The present document describes asset tracking use cases and identifies new potential service requirements as well as new KPIs to be supported by 5G communication services for asset tracking.
|
22.842
|
Study on Network Controlled Interactive Service (NCIS) in the 5G System (5GS)
|
TR
|
17.2.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.842/22842-h20.zip
|
With the expectation that 5G consumer UEs, existing or some new form devices (e.g. VR/AR devices, robot, etc.) being used for different use cases in a number of different environments, e.g. entertainment in home party or bar, or education in office, becomes interested for supporting data sharing and data exchanging between users, thus, it is necessary to investigate new use cases and requirements, like lower latency, higher throughput, higher reliability, higher resource/power efficiency etc, for such interactive services.
The objective of this TR is to study the use cases and to derive potential service requirements to provide users with interactive services, including:
- New use cases and new requirements for Interactive Services
- Gap Analyses between requirements and existing eMBB service requirements / existing ProSe requirements
- After the use cases have been identified, service requirements and KPIs will be studied including QoS, operator control, charging, etc.
|
22.866
|
Enhanced relays for energy efficiency and extensive coverage
|
TR
|
17.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.866/22866-h10.zip
|
The present document examines several use cases with respective KPIs in different domains (e.g. inHome, SmartCities, SmartFarming, SmartFactories, Smart Energy, Public Safety, Logistics) and identifies new potential requirements for relays for energy efficiency and extensive coverage.
|
22.827
|
Study on Audio-Visual Service Production
|
TR
|
17.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.827/22827-h10.zip
|
This Technical Report describes relevant use-cases and proposes respective potential service requirements for 5G systems to support production of audio-visual (AV) content and services.
Previous work assessed certain aspects for local applications (e.g. ultra-reliable low-latency and time synchronization demands.) This study addresses implications for 3GPP from wide-area media production and additional local applications. Topics to be studied include demanding locally-distributed production scenarios or ad-hoc deployments of high-bandwidth networks providing increased mobility and coverage and lowest streaming latencies.
Investigation is considered for example:
- provision of pre-defined bandwidth capacity, end-to-end latency and other QoS requirements for e.g. larger live music events or high-quality cinematic video production;
- time synchronisation among all devices (cameras, microphones, in-ear monitors etc.), optionally using a production-based master clock or time code generator, which is broadcasted;
- coverage-related issues dealing with nomadic and ad-hoc production deployments, future ways for electronic news gathering, usage of airborne equipment and support for higher ground speeds of up to 400 km/h;
- interoperability issues related to existing audio-visual production standards and protocols;
- dependability assurance and related topics (network isolation, QoS monitoring etc.).
|
22.831
|
Study on Support for Minimization of service Interruption
|
TR
|
17.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.831/22831-h10.zip
|
The present document concerns the possibility of minimizing service interruption when it occurs. This technical report gathers and analyses scenarios in which interruption to communication service arises to derive potential service requirements out of these scenarios. The study will address applicable local regulatory requirements. Gaps between what can be supported by the 3GPP system and the derived potential service requirements will be identified.
|
22.834
|
Study on support for devices with multiple Universal Subscriber Identity Modules (USIMs)
|
TR
|
17.2.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.834/22834-h20.zip
|
The present document examines several use cases in support of UE with multiple USIMs (MUSIM UE) provided by same or different MNOs and identifies new potential service requirements for emergency services and normal services among USIMs.
|
22.854
|
Feasibility Study on Multimedia Priority Service (MPS) Phase 2
|
TR
|
17.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.854/22854-h10.zip
|
The present document studies voice, data transport, and video use cases and identifies potential requirements for Multimedia Priority Service (MPS). It identifies where updates are needed to TR 22.953[3] and TS 22.153 [2] to account for current and anticipated MPS User needs for priority voice, data, and video communication capabilities.
The present document provides use cases and the associated potential new stage 1 requirements beyond those documented in TR 22.953 [3]. Example use cases include:
• MPS for Voice: MPS for MMTEL voice and voice teleconferencing invoked from a subscribed UE, and MPS for MMTEL voice teleconferencing invoked from a voice server by the host,
• MPS for Data Transport Service (DTS): MPS DTS communications invoked from a subscribed UE, a subscribed IoT device, and from an enterprise network, and
• MPS for Video: MPS for MMTEL video, MMTEL video conferencing, and streaming video invoked from a subscribed UE and MPS for video teleconferencing invoked from a video server by the host.
The present document also include security considerations.
NOTE: Both MPS users and Mission Critical users can use common mechanisms defined in MCData and MCVideo for group-based communication with priority. However, both MPS and Mission Critical users have some unique requirements to also use an operator’s individual subscription-based commercial services (voice, video, data) with priority.
|
22.889
|
Study on Future Railway Mobile Communication System (FRMCS)
|
TR
|
17.4.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.889/22889-h40.zip
|
The present document analyses FRMCS Use cases, system principles of FRMCS and Interworking between GSM-R and FRMCS in order to derive potential requirements.
|
23.700-12
|
Study on enhanced IP Multimedia Subsystem (IMS) to 5GC integration Phase 2; CT WG4 aspects
|
TR
|
17.1.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-12/23700-12-h10.zip
|
The aim of this Technical Report is to study and specify potential enhancements to the IMS architecture to enable IMS FE to integrate with the 5GC network functions to enable IMS applications to directly leverage the features and capabilities of 5GC.
The specific capabilities of 5GC included in this study:
- How can IMS utilize services provided by 5GC NFs other than PCF, such as HSS/UDM and AMF.
- How can localized routing of IMS media and signalling traffic be leveraged.
|
23.700-07
|
Study on enhanced support of Non-Public Networks (NPN)
|
TR
|
17.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-07/23700-07-h00.zip
|
3GPP Rel-16 added 5GS support for Non-Public Networks based on stage 1 service requirements in TS 22.261 [2]. The scope of this Technical Report is to study further enhancements to the 5GS to fulfil the not yet supported stage 1 service requirements for Non-Public Networks in TS 22.261 [2] and requirements described in e.g. TS 22.263 [3].
The following aspects are in scope of the study:
1. Study enhancements to enable support for SNPN along with subscription / credentials owned by an entity separate from the SNPN.
2. Study how to support UE onboarding and provisioning for non-public networks.
3. Study enhancements to the 5GS for NPN to support service requirements for production of audio-visual content and services e.g. for service continuity.
4. Study the possibility for customizations or optimizations of 5GS when used for NPN considering different deployment scenarios, e.g. when the NPN is deployed and managed with the support of PLMN, when the NPN is deployed for different coverage and device density.
5. Study the need for additional exposure capabilities due to support for NPN.
6. Study support for SNPN and PLMN sharing the same NG-RAN, if anything missing from Rel-16.
7. Study support for voice/IMS emergency services for SNPN.
|
23.700-11
|
Study on enhanced IP Multimedia Subsystem (IMS) to 5GC integration Phase 2; CT WG3 aspects
|
TR
|
17.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-11/23700-11-h00.zip
|
The aim of this Technical Report is to study and specify potential enhancements to the IMS architecture to enable IMS FE to integrate with the 5GC network functions to enable IMS applications to directly leverage the features and capabilities of 5GC.
The specific capabilities of 5GC included in this study include the PCC functionality required to resolve the key issue related to:
- Network Slicing and IMS
- Routing of IMS traffic via a localized UPF
|
23.700-20
|
Study on enhanced support of Industrial Internet of Things (IIoT) in the 5G System (5GS)
|
TR
|
17.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-20/23700-20-h00.zip
|
Study enhancements to the 5G System that would enable enhanced support of IEEE TSN Time Sensitive Communication to support deterministic applications.
|
23.700-40
|
Study on enhancement of network slicing; Phase 2
|
TR
|
17.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-40/23700-40-h00.zip
|
GSMA 5GJA has introduced in document NG.116 [3] the concept of Generic Network Slice Template (GST) from which several Network Slice Types (NESTs) can be derived by assigning values to applicable attributes defined in the GST.
This study aims at identifying the gaps that need to be filled in providing support in the specifications owned by SA WG2 for the Generic Network Slice Template (GST) attributes.
|
23.700-93
|
Study on access traffic steering, switch and splitting support in the 5G System (5GS) architecture; Phase 2
|
TR
|
17.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-93/23700-93-h00.zip
|
This Technical Report investigates following aspects for UEs that can establish a MA PDU Session to 5GC over both 3GPP and non-3GPP accesses:
- Whether and how to support additional steering mode(s), with potential PMF extensions if needed.
- Whether and how to support additional steering functionality(ies). Proposed solutions shall be based on IETF protocols or extension of such protocols (i.e. QUIC/MP-QUIC).
- Whether and how to support multi-access PDU session with one 3GPP access leg over EPC and the other access leg over non-3GPP access 5GS.
|
23.700-10
|
Study on enhanced IP Multimedia Subsystem (IMS) to 5GC integration Phase 2; CT WG1 aspects
|
TR
|
17.1.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-10/23700-10-h10.zip
|
The aim of this Technical Report is to study and specify potential enhancements to the 5G System to enable IMS FE to integrate with the 5GC network functions to enable IMS applications to directly leverage the features and capabilities of 5GC.
The specific capabilities of 5GC included in this study:
- In regard to 5GC network slicing; what enhancements (if any) are necessary for UE and 5G core network to efficiently support devices and networks with multiple slices and different services offered by the IMS network per slice?
- How to route IMS traffic via a localized UPF.
- How to place IMS application server in localized environments.
- How can IMS utilize services provided by 5GC NFs other than PCF and HSS.
|
23.745
|
Study on application layer support for Factories of the Future in 5G network
|
TR
|
17.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.745/23745-h00.zip
|
The present document is a technical report which identifies the application architecture aspects to support Factories of the Future in 5G network, and corresponding architectural solutions. The study includes identifying architecture requirements that are necessary to ensure efficient use and deployment of application layer support for Factories of the Future in 5G network.
The study takes into consideration the existing work including stage 1 requirements in 3GPP TS 22.261 [2] and 3GPP TS 22.104 [3], and provides recommendation for normative work.
|
23.700-24
|
Study on support of the 5G MSG (Message) Service
|
TR
|
17.1.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-24/23700-24-h10.zip
|
The present document studies solutions to satisfy the requirements for MSGin5G Service (message service for MIoT over 5G System). This TR will study the application architecture needed to support MSGin5G service over 5G system, based on the stage 1 requirements specified in 3GPP TS 22.262 [2].
|
23.700-91
|
Study on enablers for network automation for the 5G System (5GS); Phase 2
|
TR
|
17.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-91/23700-91-h00.zip
|
The purpose of this Technical Report is to study enhancements for analytics and NWDAF for the following objectives:
- Remaining key issues from Release 16: UE driven analytics; How to ensure that slice SLA is guaranteed; Which data from UPF can be used by NWDAF (e.g. applications, other user data characteristics);
- NWDAF architecture enhancements: Multiple NWDAF Instances in one PLMN including hierarchies, roles and inter-NWDAF instance cooperation;
- NWDAF features enhancement: Enabling real-time or near real-time NWDAF communication, including mechanism for data collection; Service MOS based NWDAF-Assisted UP Optimization; Minimization of the load generated by NWDAF data collection;
- New Use Cases/key issues: Interaction between NWDAF and ML Model & Training Service owned by the operator.
|
23.737
|
Study on architecture aspects for using satellite access in 5G
|
TR
|
17.2.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.737/23737-h20.zip
|
The scope of this Technical Report is to study:
- The identification of impact areas of satellite integration in the 5GS, when considering TR 22.822 [2] use cases.
- The identification of solutions to adjust the 5G system for the impact impacts areas for the reference use cases:
- Roaming between terrestrial and satellite networks.
- 5G Fixed Backhaul between Satellite Enabled NR-RAN and the 5G Core.
- The resolution of RAN & CN inter-related issues.
|
23.744
|
Study on location enhancements for mission critical services
|
TR
|
17.1.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.744/23744-h10.zip
|
The present document identifies the impact of location requirements from stage 1 that have yet to be realized within the stage 2 MC services architecture, and to propose solutions and enhancements where needed to fulfil these requirements.
Based on any gaps found between stage 1 service level requirements and existing MC location architecture, the present document consists of a technical report that includes: identification of key issues and gaps with the existing location architecture as specified in 3GPP TS 23.379 [6], 3GPP TS 23.280 [7], 3GPP TS 23.281 [8], and 3GPP TS 23.282 [9]; associated solutions for enhancements to existing MC location architecture; and corresponding evaluations and conclusions.
The location enhancements considered in the present document are limited to MC services over EPS.
|
23.758
|
Study on application architecture for enabling Edge Applications
|
TR
|
17.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.758/23758-h00.zip
|
The present document is a technical report capturing the study on application architecture for enabling edge applications over 3GPP networks. The aspects of the study include identifying architecture requirements (e.g. discovery of edge services, authentication of the clients), supporting application layer functional model and corresponding solutions to enable the deployment of applications on the edge of 3GPP networks, with no impact to edge-unaware applications on the UE and minimal impact to edge-aware applications on the UE.
The study takes into consideration the work done for edge computing in 3GPP TS 23.501 [2] and other related work outside 3GPP.
|
23.761
|
Study on system enablers for devices having multiple Universal Subscriber Identity Modules (USIM)
|
TR
|
17.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.761/23761-h00.zip
|
Editor's note: This clause will describe the scope for this study item.
With the growing usage of Multi-USIM devices in the market 3GPP is considering system enhancements that would allow better support of such devices.
This study item will address the objectives listed in the WID (SP-190248).
|
23.764
|
Study on enhancements to application layer support for V2X services
|
TR
|
17.1.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.764/23764-h10.zip
|
The present document is a technical report which identifies the enhancements to the application architecture to support V2X services specified in 3GPP TS 23.286 [7].
The study takes into consideration the existing stage 1 and stage 2 work within 3GPP related to V2X enhancements in 3GPP TS 22.185 [2], 3GPP TS 22.186 [3], 3GPP TS 23.285 [6] and 3GPP TS 23.287 [8], as well as V2X application requirements defined outside 3GPP.
This document will provide recommendations for normative work.
|
23.774
|
Study on mission critical services over 5G multicast broadcast system
|
TR
|
17.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.774/23774-h00.zip
|
The present document is a study of potential new/enhanced capabilities for mission critical communication services utilizing MBMS, to be provided in 5G, and points out key issues, identifies use cases, evaluates potential solutions, proposes enhancements and optimizations and identify requirements applicable to the work in SA6 and/or in other groups.
|
23.776
|
Study on architecture enhancements for 3GPP support of advanced Vehicle-to-Everything (V2X) services; Phase 2
|
TR
|
17.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.776/23776-h00.zip
|
The objective of this Technical Report is to investigate 5G System enhancements based on what has been specified in Rel-16, for enhanced support of V2X operation for pedestrian UEs (i.e. UEs for Vulnerable Road Users), e.g. V2X communication with power efficiency, according to vehicular services requirements defined in TS 22.185 [2] and TS 22.186 [3].
|
23.748
|
Study on enhancement of support for Edge Computing in 5G Core network (5GC)
|
TR
|
17.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.748/23748-h00.zip
|
The Technical Report studies and performs evaluations of potential architecture enhancements to support Edge Computing (EC) in the 5G Core network (5GC). Specifically, two objectives are included:
Objective 1: To study the potential system enhancements for enhanced Edge Computing support, including:
- Discovery of IP address of application server deployed in Edge Computing environment;
NOTE 1: This study will not consider application layer solutions.
- 5GC enhancements to support for seamless change of application server serving the UE;
- How to efficiently (with a low delay) provide local application servers with information on e.g. the QoS condition of the data path;
- Supporting for traffic steering in N6-LAN deployed in Edge Computing environment, including support for end-user traffic sent to the central N6 interface to the DN after having been processed by local application server(s);
NOTE 2: The output of the traffic steering related study should cover common N6-LAN deployment, considering the additional features for N6-LAN deployed in Edge Computing environment.
- Supporting PSA change when the application server does not support notifications of UE IP address change;
- Supporting I-SMF insertion or reselection based on AF request to route the traffic to application server deployed in Edge Computing environment.
Objective 2: To provide deployment guidelines for typical Edge Computing use cases, e.g. URLLC, V2X, AR/VR/XR, UAS, 5GSAT, and CDN etc, including:
- Deployment guidelines based on the existing Rel-15/16 Edge Computing enablers, such as LADN, in TS 23.501 [2] and TS 23.502 [3];
- Additional deployment guidelines related to any 5GS Edge Computing enhancements defined as part of the first objective.
|
23.794
|
Study on enhanced IP Multimedia Subsystem (IMS) to 5GC integration
|
TR
|
17.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.794/23794-h00.zip
|
The aim of this Technical Report is to study and specify potential enhancements to the IMS architecture to enable IMS FE to integrate with the 5GC network functions to enable IMS applications to directly leverage the features and capabilities of 5GC.
The specific capabilities of 5GC included in this study:
- In regard to 5GC network slicing; what enhancements (if any) are necessary for IMS to efficiently support devices and networks with multiple slices and different IMS services per slice?
- Should (and How does) IMS leverage the 5GC's support for localized routing of traffic and placement of IMS elements? How do such optimizations impact IMS media bearers, IMS signalling bearers, and IMS functions? How is service continuity provided in presence of localized routing?
- Whether and how can IMS applications and network functions utilize the service based capabilities and service based interfaces of the 5GC (for interactions between the IMS and the 5GC)? Which 5GC functions should be interfaced with IMS using service based interfaces?
|
23.754
|
Study on supporting Unmanned Aerial Systems (UAS) connectivity, Identification and tracking
|
TR
|
17.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.754/23754-h10.zip
|
This study item shall address the following system enablers for supporting Unmanned Aerial Systems Connectivity, Identification, and Tracking:
- a mechanism for Unmanned Aerial Vehicles (UAV) controller and UAV(s) identification and tracking in the 3GPP system;
- this includes how the 3GPP system can provide support for UAV to ground identification (e.g. to authorized third parties such as police devices);
- a mechanism to support UAV controller and UAV(s) authorization and authentication by UTM;
- a mechanism to handle unauthorized UAVs and revocation of authorization (e.g. lack of connectivity to carry the UAV command and control messages, denied registration, etc.) that enables the system to keep track of and control UAV(s).
|
23.755
|
Study on application layer support for Unmanned Aerial Systems (UAS)
|
TR
|
17.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.755/23755-h00.zip
|
The present document is a technical report which identifies the application architecture aspects to support UAS, and corresponding architectural solutions. The study includes identifying architecture requirements that are necessary to ensure efficient use and deployment of UAS services and applications over 3GPP systems.
The study takes into consideration the existing stage 1 work within 3GPP related to UAS in 3GPP TS 22.125 [3], 3GPP TS 22.281 [5] and 3GPP TS 22.282 [6]. The study also takes into consideration the related system architecture developed by SA2 in 3GPP TR 23.754 [16]. The recommendations from the study include architecture solutions that may be considered for normative work.
|
23.757
|
Study on architectural enhancements for 5G multicast-broadcast services
|
TR
|
17.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.757/23757-h00.zip
|
This Technical Report studies and evaluates architectural enhancements to the 5G System to address the following objective.
Objective A: Enabling general MBS services over 5GS.
Support general multicast and broadcast communication services, e.g. transparent IPv4/IPv6 multicast delivery, IPTV, software delivery over wireless, group communications and IoT applications, V2X applications, public safety.
|
23.752
|
Study on system enhancement for Proximity based Services (ProSe) in the 5G System (5GS)
|
TR
|
17.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.752/23752-h00.zip
|
The objective of this Technical Report is to identify and evaluate architecture enhancements of 5G System design needed to support proximity based services based on SA WG1 requirements defined in TS 22.278 [2], TS 22.261 [3] and TS 22.115 [4] and determine which of the solutions can proceed to normative specifications.
|
24.811
|
Study on the support for minimization of service interruption
|
TR
|
17.1.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.811/24811-h10.zip
|
The present document is to study the stage 2 and the stage 3 aspects for service requirements defined by SA WG1 under SA1 work item MINT (Minimization of Service Interruption), as specified in 3GPP TS 22.011 [2] and 3GPP TS 22.261 [3].
|
24.821
|
Study on PLMN selection for satellite access
|
TR
|
17.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.821/24821-h00.zip
|
This technical report studies the key issues and the respective solutions related to the support for network selection procedure that accommodates 5G systems using satellite radio access networks. The objective is to:
- identify the specifics of the satellite access networks with respect to the legacy 3GPP access networks that are relevant to the PLMN selection procedure; and
- consider the need to modify the legacy PLMN selection procedure to address the identified specifics.
|
26.803
|
Study on 5G Media Streaming Extensions for Edge Processing
|
TR
|
17.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.803/26803-h00.zip
|
The present document is a study of use cases for multimedia processing in the edge and the potential 5G media streaming architecture extensions to enable them.
|
26.805
|
Study on Media Production over 5G NPN Systems
|
TR
|
17.0.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.805/26805-h01.zip
|
The present document identifies standardization needs and potential standards gaps when using 5G Systems for media production. More specifically the following aspects are addressed in this document:
- To identify the relevant media production use cases (professional, semi-professional, production, contribution), based on existing use-cases from TR 22.827 as well as requirements from TS 22.263, that may benefit from 5G System functionalities. This includes collaboration use cases between media producers and 5G System operators.
- To develop one or several reference media production architectures and to map the variety of different media and control flows (such as uplink video, return video, tally, etc) involved in media production onto 5G System delivery components.
- To identify relevant QoS requirements for media production workflows, including required bit rates, loss rates, formats, latencies and jitter, and to identify their impact on the relevant KPIs for media production workflows (reliability, mean-time-between failure, service-level agreements, etc.).
- To identify relevant 5G System features like NPNs, Network Slicing, QoS classes, network event reporting and assistance, etc. that are useful for media production, and to clarify their usage for media production.
- To identify the suitability of existing media production content delivery protocols, codecs and service layers for 5G System usage, evaluate benefits and gaps, and recommend profiles or extensions in collaboration with organizations that develop and deploy existing protocols and codecs.
- To study media device and network orchestration solutions (such as AMWA NMOS), and their integration/interactions with the 5G exposure framework.
- To collaborate with relevant other 3GPP groups and external organizations (VSF, 5G-MAG, EBU, etc.) on media-related aspects of Media Production use cases.
- To identify potential normative work on media level for media production use cases in 5G Systems.
The document primarily focuses on the usage of 5G Systems including NPNs (both Standalone NPN and Public Network Integrated NPN).
|
26.862
|
Immersive Teleconferencing and Telepresence for Remote Terminals (ITT4RT) Use Cases, Requirements and Potential Solutions
|
TR
|
17.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.862/26862-h00.zip
|
The present document collects information regarding the “support of Immersive Teleconferencing and Telepresence for Remote Terminals” (ITT4RT) in 3GPP MTSI. The primary scope of the present document is the documentation of the following aspects:
- Core use cases and requirements for ITT4RT
- Architectures for ITT4RT
- Potential Solutions for ITT4RT not specified in TS 26.114 or TS 26.223
- Example Signalling flows for ITT4RT
- Selected Solutions as pointer to the TS 26.114 or TS 26.223
|
28.545
|
Management and orchestration; Fault Supervision (FS)
|
TS
|
17.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.545/28545-h00.zip
|
The present document specifies use cases and requirements for fault supervision of 5G networks and network slicing.
|
28.807
|
Study on management of Non-Public Networks (NPN)
|
TR
|
17.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.807/28807-h00.zip
|
The present document describes use cases, potential requirements and solutions (from the perspective of services based management architecture) for the management aspects of non-public networks. The present document provides conclusions and recommendations on the next steps for the standardization.
|
28.809
|
Study on enhancement of management data analytics
|
TR
|
17.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.809/28809-h00.zip
|
The present document studies the enhancements of MDA (Management Data Analytics).
In this TR, the MDA use cases and the corresponding potential requirements are identified and documented, and their possible solutions with analytics input and output (report) are developed and evaluated.
The study also captures the MDA functionality and service framework, MDA process, MDA role in management loop and management aspects of MDA.
Moreover, the TR provides recommendations for the normative specifications work in full alignment with SA5 5G Services Based Management Architecture (SBMA).
|
28.811
|
Management and orchestration; Study on Network Slice Management Enhancement
|
TR
|
17.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.811/28811-h00.zip
|
The present document considers the following issues:
- The potential network slice information model and management service enhancements to support cross-operator network slice management use case.
- The potential new management capabilities to support end to end network slicing.
- The potential new management capabilities to support security management of network slice.
|
28.813
|
Management and orchestration; Study on new aspects of Energy Efficiency (EE) for 5G
|
TR
|
17.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.813/28813-h00.zip
|
The present document investigates the opportunities for defining new Energy Efficiency (EE) KPIs and new Energy Saving (ES) solutions. It identifies and documents key issues related to energy efficiency and energy saving, documents and evaluates potential solutions, and provides recommendations for the normative work.
|
28.815
|
Study on charging aspects of edge computing
|
TR
|
17.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.815/28815-h00.zip
|
The present document studies the charging aspects of Edge Computing based on:
- architecture, procedures and information flows for enabling Edge Applications over 3GPP network specified in TS 23.558 [4].
- capabilities for 5GS to support edge computing specified in TS 23.501 [3], TS 23.502 [9] and TS 23.503 [10] incorporating enhancements from TR 23.748 [11] conclusions.
The ETSI ISG MEC framework is also considered.
The charging aspects encompasses:
- End user charging when accessing edge applications enabled over 3GPP networks.
- Inter-Provider charging by considering the different business roles (i.e. ASP, ECSP and MNO).
The investigation includes different charging scenarios with potential business requirements, alternative solutions with potential impact on charging architecture, charging functions and charging procedures.
|
28.808
|
Study on management and orchestration aspects of integrated satellite components in a 5G network
|
TR
|
17.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.808/28808-h00.zip
|
The scope of the present document is:
- to identify the main key issues associated with business roles, service and network management and orchestration of a 5G network with integrated satellite component(s) (whether as NG-RAN or non-3GPP access, or for transport), and
- to study the associated solutions.
The present document aims at minimising the impacts and complexity of satellite integration in the existing business models and in management and orchestration aspects of the current 5G networks.
|
28.810
|
Study on concept, requirements and solutions for levels of autonomous network
|
TR
|
17.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.810/28810-h00.zip
|
The present document describes the background, concept, definition and classification of network autonomy levels, typical scenarios for managing network and service which need autonomous support, the potential requirement and solutions and recommendation for the way forward in normative work.
|
28.812
|
Telecommunication management; Study on scenarios for Intent driven management services for mobile networks
|
TR
|
17.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.812/28812-h10.zip
|
The present document describes, intent driven management concept, intent driven management scenarios, and recommendation for the way forward on standardization expression of the intent in normative phase. The relation with other automation mechanisms is also addressed in this study.
The present document considers below dimensions when studying Intent driven management. For each dimension the scope is narrowed down to a certain aspect:
1) Users; The study covers the Technical (NOP, NEP) and Techno-Business (CSP)
2) Networks; The study covers the 5G and 4G
3) Operated System; The study covers the Co-ordinated and Complex systems
4) Infrastructure Automation; The study covers more Autonomous and less Automatic
5) Language; The scope covers more declarative and less Imperative
|
28.814
|
Management and orchestration; Study on enhancements of edge computing management
|
TR
|
17.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.814/28814-h00.zip
|
The present document studies the potential use cases, requirements, and solutions for the management of edge computing architecture and requirement defined by TS 23.558 [2] and TS 23.501 [4]. The document provides conclusions and recommendations on the next steps in the standardization.
|
28.816
|
Charging management; Study on charging aspects of Cellular Internet Of Things in the 5G System (5GS CIoT)
|
TR
|
17.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.816/28816-h00.zip
|
The present document investigates charging enhancements on 5G data connectivity domain charging, control plane data transfer domain charging and Monitoring Events charging for 5GS CIoT for the corresponding functionalities based on TS 23.501 [3], TS 32.251 [4], TS 32.255 [6], TS 32.253 [7] and TS 32.278 [8]:
- Control Plane CIoT 5GS Optimisation
- Non-IP Data Delivery (NIDD)
- Support for Monitoring Events
- Support of rate control of user data, including small data rate control
- Category M UEs differentiation
- Exception report
|
28.817
|
Management and orchestration; Study on access control for management service
|
TR
|
17.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.817/28817-h00.zip
|
The present document studies access control for management services produced by 3GPP management system.
The document investigates use cases related to access control, proposed requirements on 3GPP management system and possible solutions to support access control.
The document also provides recommendation for the normative specifications work.
|
28.818
|
Study on YANG PUSH
|
TR
|
0.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.818/28818-010.zip
|
This document investigates the possibility, the possible advantages and possible drawbacks of introducing YANG-Push [2],[3] as a 3GPP protocol for CM, FM, PM and Heartbeat.
|
28.822
|
Charging management; Study on charging aspect of 5G LAN-type services
|
TR
|
17.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.822/28822-h00.zip
|
The present document studies the charging aspects of 5G LAN-type service based on TS 23.501 [6] and TS 23.502 [7] specifications:
- Charging scenarios and potential requirements for 5G LAN-type service.
- The possible charging aspects for 5G VN group management and 5G VN group communication, including the impact on charging architecture, charging functions and charging procedures.
The stage 1 charging requirements from TS 22.261 [5] Release 16 on 5G LAN-type service topic are considered in this study.
|
28.825
|
Management and orchestration; Study on management aspects of 5G network sharing
|
TR
|
17.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.825/28825-h00.zip
|
The present document studies on concept, use cases and potential requirements related to the management aspects of MOCN network sharing, and the potential solutions for 5G network sharing management architecture.
|
29.820
|
Study on Best Practice of PFCP
|
TR
|
17.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.820/29820-h00.zip
|
The present document identifies the scenarios where the PFCP interoperability needs to be further enhanced for existing function and specifies the corresponding requirements, identifies the key issues which impact the PFCP interoperability, analyses potential solutions to address the key issues.
PFCP used in 4G (e.g. on Sxa, Sxb, Sxc interfaces) and 5G (e.g. on N4, N16a interfaces) are both within scope of the study.
|
29.829
|
Service-based support for SMS in 5GC
|
TR
|
17.1.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.829/29829-h10.zip
|
The present document identifies the SMS transfer in 5G network based on service-based interfaces, which allow SMSF and UDM to only support the SBI based interfaces in 5GC and avoid resorting to legacy MAP and Diameter interfaces within the PLMN and across PLMNs including roaming scenarios, identifies the key issues that are related to support of Service-based interfaces in 5GC, analyses potential solutions to address the key issues.
|
29.821
|
Study on restoration of profiles related to UDR
|
TR
|
17.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.821/29821-h00.zip
|
The present document identifies impacts to services offered to subscribers served by 5GC in case profiles at UDR are corrupted, lost, or became inconsistent, and addresses how the impact can be minimized. The document will focus on the following aspects:
- Clarify the necessity on defining procedures for 5GC to allow NFs, e.g. AMF, SMF, SMSF, NEF, PCF, AUSF to trigger correction and synchronization of temporary data within the UDR in case any corruption, loss, or inconsistency of data in UDR takes place, along with how NFs detect such case;
- Whether similar issue needs to be addressed between other NFs;
- Provide candidate solution(s) to solve the issue; and
- Evaluate the candidate solution(s) and recommend any changes to specifications if identified.
|
29.835
|
Study on Port Allocation Alternatives for New 3GPP Interfaces
|
TR
|
17.1.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.835/29835-h10.zip
|
The present document studies alternative proposals for the port number allocations to the new 3GPP interfaces and applications. The study will focus on, but is not limited to following three alternatives:
- 3GPP allocating port numbers from the Dynamic/Private Port number range [49152 - 65535]. See clause 6 in IETF RFC 6335 [2];
- Operators allocating port numbers from either the User Port number range [1024-49151] or the Dynamic/Private Port number range [49152 - 65535]. See clause 6 in IETF RFC 6335 [2];
- DNS based solution, where port numbers are allocated from the User Port number range [1024-49151] or the Dynamic/Private Port number range [49152 - 65535]. See clause 6 in IETF RFC 6335 [2].
The primary focus of this study is on protocols only used for network internal services, i.e. when the protocol is only used in a single network with no interconnection with other networks or the public Internet. The solutions proposed in the study however could also be used in scenarios in which the protocol is used across multiple networks, e.g. in roaming case or between the RAN and the core network supported by different operator networks.
|
32.846
|
Charging management; Study on charging aspects of Proximity-based Services (ProSe) in 5GS
|
TR
|
17.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.846/32846-h00.zip
|
The present document studies on charging aspects of Proximity-based Services in 5GS based on TS 23.304 [11].
The charging aspects related to the Proximity-based Services in 5GS are covered within the scope:
- Charging architecture, for supporting charging of ProSe Direct Discovery and Direct Communication related to Public Safety and commercial proximity service.
- Charging principles, scenarios and potential requirements related to the ProSe service in 5GS.
- Potential charging solutions for the Proximity-based Services in 5GS.
|
33.818
|
Security Assurance Methodology (SECAM) and Security Assurance Specification (SCAS) for 3GPP virtualized network products
|
TR
|
17.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.818/33818-h10.zip
|
The present document studies the SECAM (Security Assurance Methodology) and SCAS (Security Assurance Specification) for 3GPP virtualised network products based on SECAM and SCAS defined in TR 33.916 [2]. It makes thorough gap analysis between current SECAM/SCAS work in TR 33.916 [2] and SECAM/SCAS work for 3GPP virtualised network products. It also identifies, defines ToE and roles of SECAM/SCAS for 3GPP virtualised network products according to deployment scenarios and decoupling ways. Based on the identified ToE and roles, the present document details the needed change or additional work to current security assurance methodology for the creation, evaluation procedure of related SCAS documents, etc. It studies new threats of the identified ToE and identifies the additional security requirements of the ToE, or/and identifies existing relevant/supporting requirements specified in ETSI NFV specifications or the equivalent. The present document also provides potential new SECAM/SCAS proposals and points out the impact to existing SECAM/SCAS documents (including TR 33.916 [2], TR 33.926 [3], TS 33.117 [4], etc.).
NOTE: SECAM/SCAS of 3GPP virtualised network products in the present document considers only the scenario that 3GPP VNF deployed in the virtual machines.
|
33.857
|
Study on enhanced security support for Non-Public Networks (NPN)
|
TR
|
17.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.857/33857-h10.zip
|
The aim of the present document is to study the security aspects for any potential enhancements based on the outcome of the study in TR 23.700-07 [3]. For each of the objectives in the scope of the study in TR 23.700-07 [3], the security aspects that are to be covered in the present document are as follows:
- Enhancements to Support SNPN along with credentials owned by an entity separate from the SNPN
- Study potential solutions for authentication using credentials owned by an entity separate from the SNPN
- UE Onboarding and remote provisioning of non-USIM credentials
- Identify security Key Issues relating to UE Onboarding and remote provisioning with non-USIM credentials
- Identify methods by which the UE can be verified as "uniquely identifiable and verifiably secure"
- Critically review the security aspects of the proposed solutions in TR 23.700-07 [3] and make recommendations for security improvements where required.
- Study potential solutions for the secure provisioning of non-USIM credentials taking into account different deployment scenarios.
NOTE 1: The term USIM in this context denotes the IMSI accompanied by AKA credentials (i.e. for primary authentication with the PLMN).
- Support of IMS voice and emergency services for SNPN:
- Analyse potential security impacts from supporting IMS voice and IMS services in SNPNs. In Rel-16 SNPNs do not support IMS emergency services but for Rel-17 its expected that the enabling of IMS and IMS services for SNPNs is to be studied.
NOTE 2: Key issue 2 in TR 23.700-07 [3] is assumed to not require any study from a security perspective.
|
33.839
|
Study on security aspects of enhancement of support for edge computing in the 5G Core (5GC)
|
TR
|
17.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.839/33839-h10.zip
|
The present document studies the security enhancements on the support for Edge Computing in the 5G Core network define in TR 23.748 [3], and application architecture for enabling Edge Applications defined in TR 23.758 [4] and TS 23.558 [2].
Potential security requirements are provided and possible security enhancements to 5GS and edge application architecture are proposed that meet these security requirements.
NOTE: The user consent for exposure of information to Edge Applications is addressed in TR 33.867 [20].
|
33.847
|
Study on security aspects of enhancement for proximity based services in the 5G System (5GS)
|
TR
|
17.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.847/33847-h10.zip
|
The present document studies the security and privacy aspects of proximity based services (including public safety and commercial proximity services) in the 5G system. It ensures that the security solutions are aligned with the work in TR 23.752 [2], TS 22.278 [3] and TS 22.261 [4]. The present document covers the following issues:
- Security and privacy key issues, threats and potential requirements of proximity based services in 5G system.
- Potential security solutions to cover these potential requirements.
Both roaming and non-roaming scenarios are considered.
|
33.850
|
Study on security aspects of enhancements for 5G Multicast-Broadcast Services (MBS)
|
TR
|
17.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.850/33850-h00.zip
|
The present document studies the security of 5G multicast-broadcast services based on FS_5MBS study in TR 23.757 [2]. Potential security requirements are identified and possible security solutions are proposed to address these security requirements.
|
33.853
|
Study on key issues and potential solutions for integrity protection of the User Plane (UP)
|
TR
|
17.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.853/33853-h00.zip
|
The present document studies the key issues and potential solutions for integrity protecting the user plane, including potential enhancements needed to support UP IP up to the full data rate, in the following combinations as defined in 3GPP TR 38.801 [2] (clause 7.2):
- Option 1 - eUTRA with EPC
- Option 2 - NR standalone with 5G Core
- Option 3 - EPC based Dual Connectivity of eUTRA and NR RAT
- Option 4 - 5G Core based Dual Connectivity (NR master - eUTRA secondary)
- Option 5 - 5G Core with eUTRA
- Option 7 - 5G Core based Dual Connectivity (eUTRA master - NR secondary)
The present document does not detail key issues, solutions, evaluations, conclusions and recommendations for GERAN and UTRAN.
|
33.854
|
Study on security aspects of Uncrewed Aerial Systems (UAS)
|
TR
|
17.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.854/33854-h10.zip
|
The present document contains a study on the security aspects of Uncrewed Aerial Systems (UASs). TS 22.125 [2] contains the service requirements for UAS while TR 23.754 [3] is studying aspects like the UAS connectivity, identification and tracking and TR 23.755 [4] studies UAV services and application layer features. The security study of the present document provides key issue including security threat and potential requirements related to the work in these other specifications and develops and analyses solutions to these key issues. Finally the study provides some conclusions for potential normative work.
|
33.845
|
Study on storage and transport of 5G Core (5GC) security parameters for Authentication Credential Repository Processing Function (ARPF) authentication
|
TR
|
17.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.845/33845-h00.zip
|
The present document details the following:
- The security assumptions relating to security communication in 5G.
- The security assumptions related to protecting subscriber privacy.
- The home network parameters that are relevant to securing the communication in 5G and protecting subscriber privacy.
- Key Issues, threats and requirements relevant to securing the communication in 5G and protecting subscriber privacy.
- Solutions that potentially resolve the key issues described.
The present document does not describe the storage of security parameters in the UE or the serving network or the transportation of secure information between the home network and the serving network.
|
33.846
|
Study on authentication enhancements in the 5G System (5GS)
|
TR
|
17.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.846/33846-h00.zip
|
The scope of the present document is the following:
- key issues, potential security requirements and solutions of how to enhance the authentication process to ensure the security of session anchor keys in case the long-term key is leaked.
- key issues, potential security requirements and solutions of how to mitigate the linkability attacks.
- key issues, potential security requirements and solutions of how to mitigate the impacts of potential DDoS threats due to concealing the SUPI.
- key issues, potential security requirements and solution of how to mitigate the leaking of SQN values during AKA re-synchronisation.
|
33.851
|
Study on security for enhanced support of Industrial Internet of Things (IIoT)
|
TR
|
17.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.851/33851-h10.zip
|
The present document studies the security impact of time sensitive communication aspects in Industrial IoT based on FS_IIoT study in TR 23.700-20 [4] and the architecture described in 3GPP TS 23.501 [3].
|
33.864
|
Study on the security of Access and Mobility Management Function (AMF) re-allocation
|
TR
|
17.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.864/33864-h00.zip
|
The present document aims at addressing the case for the indirect reroute procedure for UE registration. The intention is to enable deployment scenarios with stricter slice isolation requirements on the core network, for example where the AMFs are unable to communicate with each other.
The aim of the present document is to:
- Collect the potential requirements related to the AMF re-allocation procedure.
- Study the potential enhancements to the security mechanisms in order to fulfil the requirements for the AMF re-allocation.
|
33.824
|
Study on Security for Next Radio (NR) Integrated Access and Backhaul (IAB)
|
TR
|
17.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.824/33824-h00.zip
|
The present document:
- Describes potential security threats and vulnerabilities that are applicable to the enhanced IAB architecture specified in the TS 38.300 [3], TS 38.331 [8], TS 38.321 [9] and TS 38.340 [10].
- Identifies potential security requirements for those potential security threats and vulnerabilities.
- Proposes candidate solutions to ensure that the enhanced IAB architecture specified in the 3GPP TS 38.300 [3], TS 38.331 [8], TS 38.321 [9] and TS 38.340 [10] does not introduce security vulnerabilities in the 5G system providing a secure connection for the UEs connecting to the NR through IAB node(s).
- Concludes with the solutions that should be included in a future normative phase.
|
33.867
|
Study on user consent for 3GPP services
|
TR
|
17.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.867/33867-h10.zip
|
The scope of present document is to identify and evaluate the requirements and solutions to support user consent for 3GPP services while complying with user privacy considerations.
The details are as follows:
- Review TR 33.849 [3] with regards to the concept of user consent for 3GPP users, and identify what types of data collection and conditions under which the support of the user consent is required; then update them if needed.
- Identify target usage scenarios and trust domains.
- Analyse potential security threats and requirements for conditions under which user sensitive data are collected without user consent, and when user consent indication is not protected.
- Identify potential solutions to address the above security requirements.
NOTE 1: Principles, regulations, and definitions related to privacy, which are recognized differently in each different country or area, are taken into account when deriving the concept of user consent for 3GPP users.
NOTE 2: Even where solutions exist to obtain user consent, collection and exposure of user sensitive data should be minimized and only be allowed where critical to the operation of the related feature.
|
33.862
|
Study on security aspects of the Message Service for MIoT over the 5G System (MSGin5G)
|
TR
|
17.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.862/33862-h10.zip
|
The present document studies the security aspects on the support of the 5GMSG Service defined in TR 23.700-24 [2], determines key issues of potential security requirements and proposed possible security solutions to meet these security requirements.
|
33.866
|
Study on security aspects of enablers for Network Automation (eNA) for the 5G system (5GS) Phase 2
|
TR
|
17.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.866/33866-h00.zip
|
The present document studies the security aspects of enablers for network automation for the 5G system based on the outcome of TR 23.700-91 [1]. More specifically, the present document identifies security issues, requirements and corresponding potential security solutions related to the following objectives:
- UE data collection protection to fulfil the NWDAF functionalities including privacy consideration, data authenticity, data integrity, and accessibility aspects requirements.
- Detection of cyber-attacks and anomaly events supported by NWDAF and its related functions, specifically to identify parameters provided by UE and NFs, which can help to detect attacks and abnormal behaviours;
- Protection of data transferring (e.g. privacy consideration) in the inter-NWDAF/NWDAF instances.
NOTE: The user consent for UE data collection is not addressed in the present document, it will be discussed in TR 33.867 [2].
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.