Dataset Viewer
id
stringlengths 4
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 617
values | working_group
stringclasses 30
values | url
stringlengths 65
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
22.101
|
Service aspects; Service principles
|
TS
|
20.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.101/22101-k00.zip
|
This Technical Specification (TS) describes the Service Principles for PLMNs specified by 3GPP. Principles and requirements for interworking with WLAN are covered in TS 22.234 [35].
3GPP specifications provide integrated personal communications services. The system will support different applications ranging from narrow-band to wide-band communications capability with integrated personal and terminal mobility to meet the user and service requirements of the 21st century.
3GPP specifications allow the realisation of a new generation of mobile communications technology for a world in which personal communications services should allow person-to-person calling, independent of location, the terminal used, the means of transmission (wired or wireless) and the choice of technology. Personal communication services should be based on a combination of fixed and wireless/mobile services to form a seamless end-to-end service for the user.
3GPP specifications should be in compliance with the following objectives:
a) to provide a single integrated system in which the user can access services in an easy to use and uniform way in all environments;
b) to allow differentiation between service offerings of various serving networks and home environments;
c) to provide a wide range of telecommunications services including those provided by fixed networks and requiring user bit rates of up to 100 Mbit/s as well as services special to mobile communications. These services should be supported in residential, public and office environments and in areas of diverse population densities. These services are provided with a quality comparable with that provided by fixed networks such as ISDN and fixed broadband Internet access;
d) to provide services via hand held, portable, vehicular mounted, movable and fixed terminals (including those which normally operate connected to fixed networks), in all environments (in different service environments - residential, private domestic and different radio environments) provided that the terminal has the necessary capabilities;
e) to provide support of roaming users by enabling users to access services provided by their home environment in the same way even when roaming.
f) to provide audio, data, video and particularly multimedia services;
g) to provide for the flexible introduction of telecommunication services;
h) to provide within the residential environment the capability to enable a pedestrian user to access all services normally provided by fixed networks;
i) to provide within the office environment the capability to enable a pedestrian user to access all services normally provided by PBXs and LANs;
j) to provide a substitute for fixed networks in areas of diverse population densities, under conditions approved by the appropriate national or regional regulatory authority.
k) to provide support for interfaces which allow the use of terminals normally connected to fixed networks.
|
22.153
|
Multimedia priority service
|
TS
|
20.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.153/22153-k00.zip
|
The present document specifies the service requirements for Multimedia Priority Service (MPS).
The scope of this document is to specify those requirements of MPS necessary to provide an end-to-end service and to interwork with external networks where needed. Service interactions with external networks are considered within the scope of this document although these interactions may be specified in other standards.
|
22.179
|
Mission Critical Push to Talk (MCPTT); Stage 1
|
TS
|
20.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.179/22179-k00.zip
|
The present document provides the service requirements for operation of the MCPTT Service. MCPTT makes use of capabilities included in Group Communications System Enablers and Proximity Services, with additional requirements specific to the MCPTT Service. The MCPTT Service can be used for public safety applications and maritime safety applications and also for general commercial applications (e.g., utility companies, railways and maritime usage). The requirements in this specification do not apply to GSM or UMTS.
|
22.261
|
Service requirements for the 5G system
|
TS
|
20.3.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.261/22261-k30.zip
| |
22.268
|
Public Warning System (PWS) requirements
|
TS
|
20.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.268/22268-k00.zip
|
This Technical Specification defines the stage one description of the Public Warning System (PWS) Requirements. Stage one is the set of requirements seen primarily from the users’ and service providers’ points of view.
The scope of this TS covers the core requirements for the PWS that are sufficient to provide a complete service. This TS also covers subsystem additional requirements for the Earthquake and Tsunami Warning System (ETWS), the Commercial Mobile Alert System (CMAS), EU-ALERT, and Korean Public Alert System (KPAS).
This TS includes information applicable to network operators, service providers, terminal and network manufacturers, in case of deployment of PWS, ETWS, and or CMAS, EU-ALERT, and KPAS. PWS, ETWS, CMAS, EU-ALERT, and KPAS deployment depends on operator decision or national regulations.
|
22.280
|
Mission Critical Services Common Requirements (MCCoRe); Stage 1
|
TS
|
20.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.280/22280-k00.zip
|
The present document provides the service requirements that are common across two or more mission critical services, that is MCPTT, MCData and MCVideo. The mission critical services make use of capabilities included in Group Communications System Enablers and Proximity Services, with additional requirements specific to the MCPTT Service as specified in 3GPP TS 22.179 [1], MCVideo Service as specified in 3GPP TS 22.281 [2], and MCData Service as specified in 3GPP TS 22.282 [3]. The mission critical services can be used for public safety applications and maritime safety applications and also for general commercial applications (e.g., utility companies, railways and maritime usage). The requirements in this specification do not apply to GSM or UMTS.
|
22.870
|
Study on 6G Use Cases and Service Requirements
|
TR
|
0.3.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.870/22870-031.zip
|
The present document …
|
22.883
|
Feasibility Study on Energy Efficiency as service criteria Phase 2
|
TR
|
20.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.883/22883-k00.zip
|
The present document provides stage 1 use cases and potential requirements on the following aspects regarding enhancements on energy as service criteria.
• Information exposure of energy-related characteristics of the network for the communication service (i.e. energy consumption, energy supply mix, carbon footprint, energy capacity and availability conditions) to authorized users or authorized 3rd parties.
Potential dynamic adjustments of the delivered communication service from 5G system perspective (including service performance adjustments) resulting from the changes of energy-related characteristics of this service.
Note: Dynamic adjustments can be based on criteria such as network decision, user preference or agreement between authorized 3rd parties and network.
• Other aspects including security, charging and privacy for the scenarios above.
|
22.887
|
Feasibility Study on satellite access - Phase 4
|
TR
|
20.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.887/22887-k00.zip
|
The present document describes use cases and aspects related to enhancements of the 5G system over satellite, including:
• multi-orbit satellite access for multiple services
• resilient notification
• support for emergency communications and mission critical services using satellite access
• support IMS voice calls using GEO satellite access
• Broadcast services with satellite access for unregistered UEs
NOTE: In the present document, the terms GEO (geostationary) and GSO (geosynchronous) are equivalent, unless indicated otherwise
|
22.989
|
Study on Future Railway Mobile Communication System
|
TR
|
20.3.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.989/22989-k30.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.280
|
Common functional architecture to support mission critical services; Stage 2
|
TS
|
20.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.280/23280-k00.zip
|
This document specifies the common functional architecture, procedures and information flows needed to support mission critical services including the common services core architecture.
The corresponding service requirements are defined in 3GPP TS 22.179 [2], 3GPP TS 22.280 [3], 3GPP TS 22.281 [4] and 3GPP TS 22.282 [5].
The present document is applicable primarily to mission critical services using E-UTRAN access based on the EPC architecture defined in 3GPP TS 23.401 [17]. Certain MC service functions such as dispatch and administrative functions could also be supported via non-3GPP access networks but no additional functionality is specified to support non-3GPP access.
The common functional architecture to support mission critical services can be used for public safety applications and also for general commercial applications e.g. utility companies and railways.
|
23.281
|
Functional architecture and information flows to support Mission Critical Video (MCVideo); Stage 2
|
TS
|
20.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.281/23281-k00.zip
|
This document specifies the functional model, procedures and information flows needed for the mission critical video (MCVideo) service. Support for both MCVideo group streaming and MCVideo private streaming operating in on-network and off-network modes of operation is specified.
The corresponding service requirements are defined in 3GPP TS 22.280 [2], and 3GPP TS 22.281 [3].
The present document is applicable primarily to mission critical video service using E-UTRAN access based on the common functional architecture for mission critical services defined in 3GPP TS 23.280 [6] and the EPC architecture defined in 3GPP TS 23.401 [8].
The MCVideo service can be used for public safety applications and also for general commercial applications e.g. utility companies and railways.
|
23.283
|
Mission Critical Communication Interworking with Land Mobile Radio Systems
|
TS
|
20.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.283/23283-k00.zip
|
The objective of this technical specification is to specify interworking between MC systems and LMR systems that satisfy the MCPTT requirements in 3GPP TS 22.179 [3], MCCoRe requirements in 3GPP TS 22.280 [2] and the MCData requirements (SDS only) in 3GPP TS 22.282 [4].
The present document refers to an InterWorking Function (IWF). The structure and functionality of the IWF is out of scope of the present document. The definition of reference points between the IWF and MC systems and the interactions between the IWF and MC systems are in scope of the present document.
|
23.289
|
Mission Critical services over 5G System; Stage 2
|
TS
|
20.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.289/23289-k00.zip
|
The present document specifies the use of the 5G System (5GS) considering common functional architecture, procedures and information flows needed to support mission critical services encompassing the common services core architecture.
The corresponding service requirements applied in 3GPP TS 22.179 [11], 3GPP TS 22.280 [12], 3GPP TS 22.281 [13], 3GPP TS 22.282 [14] and 3GPP TS 22.289 [22] also apply here.
The corresponding MC service specific procedures and information flows are defined in 3GPP TS 23.280 [3], 3GPP TS 23.379 [6], 3GPP TS 23.281[4], 3GPP TS 23.282 [5] and 3GPP TS 23.283 [23].
The present document is applicable primarily to mission critical services using 3GPP access (5G NR and/or E-UTRA) and non-3GPP access (WLAN, Satellite and/or wireline) based on the 5GC architecture defined in 3GPP TS 23.501 [7], 3GPP TS 23.247 [15] and 3GPP TS 23.304 [17].
The common functional architecture to support mission critical services can be used for public safety applications and for general commercial applications e.g. utility companies and railways.
|
23.801-01
|
Study on Architecture for 6G System
|
TR
|
0.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.801-01/23801-01-000.zip
| |
23.700-04
|
Study on Core Network Enhanced Support for Artificial Intelligence (AI) / Machine Learning (ML); Phase2
|
TR
|
0.2.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-04/23700-04-020.zip
|
The present document …describes the potential 5G system enhancement for Artificial Intelligence (AI) / Machine Learning (ML) by covering the followings:
- whether and how to support the standardized transfer of standardized data over UP for UE data collection to meet the requirements (of which details are described in clause 4) for AI/ML for NR air interface operation with UE-side model training.
- whether and how to enhance the 5GC analytics to support efficient performance of user plane.
|
23.700-14
|
Study on Stage 2 for Integrated Sensing and Communication
|
TR
|
0.2.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-14/23700-14-020.zip
|
This Technical Report aims at investigating the function enhancement, end to end service operations and procedures to support Integrated Sensing and Communication with the considerations of a sub-set of use cases (e.g. commercial, automotive, public safety and emergency services) based on the requirements documented in TS 22.137 [2].
With that aim, the scope covers relevant system architecture design aspects including service authorization and revocation, discovery and selection of sensing entities/functions, sensing data collection and result exposure, and configuration parameters provisioning.
Potential privacy requirements if identified during the study will be considered for the study of the sensing architecture.
NOTE 1: Privacy protection and other security aspects will be coordinated with SA WG3, and the related impact to architecture enhancement will be based on SA WG3 conclusion.
NOTE 2: Charging and OAM aspects will be coordinated with SA WG5, and the related impact to architecture enhancement will be based on SA WG5 conclusion.
Editor's note: Any study work on Sensing in Q2 should be limited to common aspects for the study without any RAN specific or UE specific sensing modes. Any UE/RAN aspects will be aligned with TSG RAN after TSGs#108.
|
23.700-19
|
Study on Integration of satellite components in the 5G architecture; Phase 4
|
TR
|
0.2.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-19/23700-19-020.zip
|
The scope of this Technical Report is to study the following aspects:
- Support of IMS voice call over NB-IoT NTN via GEO satellite connecting to EPC.
- Enhancements for UE-SAT-UE communication with 5GS under NR NTN NGSO constellation with feeder link available.
|
23.700-30
|
Study on Architecture support of Ambient power-enabled Internet of Things (AIoT); Phase 2
|
TR
|
0.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-30/23700-30-000.zip
| |
23.700-35
|
Study on Service Enabler Architecture Layer (SEAL) Phase 4
|
TR
|
1.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-35/23700-35-100.zip
|
The scope of Technical Report is to study on potential enhancements to Service Enabler Architecture Layer (SEAL). In particular, the study reviews the existing SEAL specifications and architecture to identify any gaps or potential enhancements necessary to enable usage of SEAL for 3rd party applications, including aspects such as API abstraction, minimizing transformation of SEAL APIs, representation of SEAL architecture in relationship with the overall 3GPP system, and new deployment option.
|
23.700-37
|
Study on discreet listening and monitoring of mission critical services, Phase2
|
TR
|
0.2.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-37/23700-37-020.zip
|
The present document studies solutions to satisfy the requirements for discreet monitoring of mission critical services. It identifies enhancements to be included in the technical specifications for MC Common functional architecture (3GPP TS 23.280 [2]), MCPTT (3GPP TS 23.379 [3]), MCVideo (3GPP TS 23.281 [4]), MCData (3GPP TS 23.282 [5]), MC Interworking with LMR (3GPP TS 23.283 [6]), and Mission Critical services over 5G System (3GPP TS 23.289 [7]). The requirements for this study are taken from the Stage 1 requirements in 3GPP TS 22.280 [8].
|
23.700-51
|
Study on Application enabler for XR Services Phase 3
|
TR
|
0.2.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-51/23700-51-020.zip
|
The present document studies application enabling layer key issues, and solution recommendations to support XR services, including the QoS differentiation and policy control for non-3GPP tethered devices etc. Based on the specified solutions, identify potential enhancements to other enablement frameworks (e.g. SEAL/SEALDD, ADAES, PINAPP).
The study is based on the requirements defined in 3GPP TS 22.261 [2] and is dependent on the 5GC architecture supporting XRM services as specified in 3GPP TS 23.501 [3], 23.502 [4], and 23.503 [5].
|
23.700-52
|
Study on SEALDD phase 3
|
TR
|
0.2.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-52/23700-52-020.zip
|
The present document is to study on potential enhancements to Service Enabler Architecture Layer (SEAL) data delivery (DD). Specifically, the study is to address data delivery using network multicast/broadcast capability from both 4G and 5G, the SEAL-DD user plane (i.e., SEALDD-UU, SEALDD-S) aspects (e.g., protocol stack(s), user plane functionality description) and the data delivery of new application traffic pattern where the application layer interactions are non-continuous and each of the interactions may be independent with each other.
|
23.700-56
|
Study on system architecture enhancement for next generation real time communication; Phase 3
|
TR
|
0.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-56/23700-56-000.zip
| |
23.700-57
|
Study on Stage 2 for MMTel Phase 2
|
TR
|
0.2.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-57/23700-57-020.zip
|
The present document studies the following aspects:
- the solutions to solve the remaining issues in Rel-19 MMTel_APP WI, including:
i. support the enablement of MMTel calling with or without Data Channel using existing APIs provided by OMA and capture the gaps; and
ii. providing capabilities to Application to enable MMTel related value added service; and
- the application enablement aspects for MMTel service based on the specifications developed by SA2 in Rel-19 (NEF, NG_RTC_Ph2 WI).
|
23.700-65
|
Study on Short Message Service to Emergency Response Centre
|
TR
|
0.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-65/23700-65-000.zip
| |
23.700-67
|
Study on Energy Efficiency and Energy Saving; Phase2
|
TR
|
0.2.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-67/23700-67-020.zip
|
This Technical Report investigates the enhancements on 5GS to improve energy efficiency and energy saving in the network, taking the EnergyServ_Ph2 requirements in TS 22.261 [5] into consideration, for the following aspects:
- Whether and how to enhance the collection, determination and exposure of energy related information in the 5GS;
- Whether and how to support service adjustments for the UE to enable energy saving;
- Whether and how to support NF (re)selection and/or UP path adjustment based on energy related information.
|
22.104
|
Service requirements for cyber-physical control applications in vertical domains
|
TS
|
19.2.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.104/22104-j20.zip
|
The present document provides Stage 1 normative service requirements for 5G systems, in particular service requirements for cyber-physical control applications in vertical domains and requirements for auxiliary applications. In the context of the present document, cyber-physical systems are to be understood as systems that include engineered, interacting networks of physical and computational components; control applications are to be understood as applications that control physical processes. Examples for auxiliary applications are distributed sensing and asset monitoring.
Communication services supporting cyber-physical control applications need to be ultra-reliable and, in some cases, the end-to-end latency must be very low. Communication for cyber-physical control applications supports operation in various vertical domains, for instance industrial automation, Smart Grid .
The aspects addressed in the present document include:
- end-to-end service performance requirements and network performance requirements related to these end-to-end service performance requirements;
- support for Ethernet services specific to industrial/high performance use cases. Related Ethernet functionalities include, for example, those in IEEE 802.1Qbv;
- direct device connection and indirect network connection for cyber-physical applications.
|
23.700-83
|
Study on application layer support for AI/ML services Phase 2
|
TR
|
0.2.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-83/23700-83-020.zip
|
The present document is a technical report which identifies enhancements to the application enablement layer architecture, capabilities, and services to support AI/ML services at the application layer.
The aspects of the study include the continuation of the investigation of application enablement impacts, the application enablement layer architecture enhancements and solutions needed to provide assistance in AI/ML operations at the VAL layer as well as at the application enablement layer (e.g., SEAL ADAES, EDGEAPP).
The study takes into consideration the work done for AI/ML in 3GPP TS 23.436 [3] and 3GPP TS 23.482 [2] and can consider other AI/ML related works within 3GPP.
|
26.940
|
Study on Ultra Low Bit rate Speech Codecs
|
TR
|
0.2.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.940/26940-020.zip
|
This clause shall start on a new page.
[The present document develops recommendations for potential normative work on an ultra-low bit rate codec for the use case of IMS voice services over Geostationary Orbit (GEO) access.]
Editor’s Note:
3GPP SA1 has studied the use case IMS Voice Call Using GEO Access, and the results are documented in TR 22.887. Normative service requirements and KPIs on IMS voice call using GEO satellite access will be introduced in TS 22.261 at TSG#107. GEO satellites are on a 35,786 km distance from the earth, which noticeably impacts signal propagation delay (one way approx. 285ms), data rate, and channel conditions due to e.g. atmospheric attenuation. Compared to terrestrial links, this poses significant new challenges for the voice codecs and services:
The overall transmission data rate assumed for GEO satellite systems is very constrained due to e.g. high path loss, atmospheric attenuation, energy constraints for terminals etc.. In TR 22.887, a total transmission data rate of [1-3] kbit/s is assumed. This transmission data rate are lower than what current 3GPP protocol stacks and codecs can supports.
For GEO satellite access, the propagation delay (285ms) is much longer than for commonly used terrestrial links.
The GEO satellite link imposes different channel characteristics, e.g., due to atmospheric attenuation.
Currently, no 3GPP voice codec seems to support all the expected requirements for this use case. Considering bitrate alone, the lowest supported bitrate of any 3GPP codec is 4.75 kbit/s as provided by the narrow band AMR codec (TS 26.071). This makes it necessary to have a new feasibility study relating to ultra-low bitrate codecs suitable for voice using GEO access.
The primary focus of this study is to develop design constraints and performance requirements for a codec supporting use cases like IMS Voice Call over GEO and the resulting transmission parameters. The requirements can provide guidance on the evaluation of the candidate codecs during potential normative work.
1. General considerations
- Bitrate: TR 22.887 concludes that the transmission rates are lower than what current 3GPP protocol stacks and codecs can supports. Detailed analysis on available bitrate requires more study..
- Quality: Despite of the low bit rate, a good audio quality of the codec is of importance, to ensure a reasonable QoE. Detailed QoE requirements for such services are for study..
- Complexity and memory demands: Modern low bitrate codecs exhibit a large scale of complexity and memory demands. The codec is expected to be deployable on the processing capabilities as can be found in today’s smartphones. Exact complexity requirements are for study.
- Robustness to network conditions: the codec is expected to operate in typical network conditions (delay, loss, jitter, etc.). Details are for further study.
2. Functional requirements
- Speech transcoding functions: To achieve integration with the terrestrial voice communication system (4G/5G IMS architecture), it is necessary to consider tandeming with existing IMS voice codecs.
NOTE: Additional study areas or use cases, such as assessing the market potential and potential market-readiness of a new ULBC codec should be added with lower priority if time permits and once the exact requirements can be given.
It is expected that coordination with other working groups, e.g. SA2, CT1, RAN2 is needed in order to substantiate the design constraints of such a codec. However, it is not expected that this work creates any dependency for studies and normative in other working groups.
|
23.700-39
|
Study on logging and recording of mission critical services, Phase2
|
TR
|
0.2.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-39/23700-39-020.zip
|
The present document studies solutions to satisfy the requirements for logging and recording of mission critical services. It identifies enhancements to be included in the technical specifications for MC Common functional architecture (3GPP TS 23.280 [2]), MCPTT (3GPP TS 23.379 [3]), MCVideo (3GPP TS 23.281 [4]), MCData (3GPP TS 23.282 [5]), MC Interworking with LMR (3GPP TS 23.283 [6]), and Mission Critical services over 5G System (3GPP TS 23.289 [7]). The requirements for this study are taken from the Stage 1 requirements in 3GPP TS 22.280 [8].
|
21.801
|
Specification drafting rules
|
TR
|
19.0.0
|
SP
|
https://www.3gpp.org/ftp/Specs/archive/21_series/21.801/21801-j00.zip
|
The present document specifies rules for the structure and drafting of documents intended to become a 3GPP Technical Specification or Technical Report. These rules are intended to ensure that such documents are drafted in as uniform a manner as is practicable, irrespective of the technical content.
The present document is based on the ISO/IEC Directives, Part 3, but is a self-contained document that will be maintained as such.
These drafting rules complement the 3GPP Working Procedures.
|
21.900
|
Technical Specification Group working methods
|
TR
|
19.1.0
|
SP
|
https://www.3gpp.org/ftp/Specs/archive/21_series/21.900/21900-j10.zip
|
This document outlines the working methods to be used by the 3GPP Technical Specification Groups and their Working Groups and their Sub-Groups, and by the 3GPP Support Team in relation to document management, i.e. handling of specifications, updating procedures, Change Request procedures, version control mechanisms, specifications status information etc. It complements the rules and procedures defined for 3GPP. This document does not stipulate the details of the internal working of the TSG Sub-Groups. From the Technical Specification Group point of view, a task and responsibility is given to a Working Group directly answering to the Technical Specification Group. In practice, the work/task may be carried out in a subgroup of that Working Group.
1A References
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.801: "Specification drafting rules".
[2] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[3] 3GPP TS 21.101: "Technical Specifications and Technical Reports for a UTRAN-based 3GPP system".
[4] 3GPP TS 41.101: "Technical Specifications and Technical Reports for a GERAN-based 3GPP system".
[5] ITU-T Recommendation I.130: "Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN".
[6] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[7] IETF RFC 3629: "UTF-8, a transformation format of ISO 10646".
|
22.011
|
Service accessibility
|
TS
|
19.5.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.011/22011-j50.zip
|
The purpose of this TS is to describe the service access procedures as presented to the user.
Definitions and procedures are provided in this TS for international roaming, national roaming and regionally provided service. These are mandatory in relation to the technical realization of the Mobile Station (UE).
|
22.101
|
Service aspects; Service principles
|
TS
|
19.2.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.101/22101-j20.zip
| |
22.848
|
Feasibility Study on Interconnect of SNPN
|
TR
|
19.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.848/22848-j00.zip
|
The present document describes use cases and aspects related to interconnect of SNPNs as well as Scalable SNPN Interconnect with dynamic connections.
Potential service requirements are derived for these use cases and are consolidated in a dedicated chapter.
The report ends with recommendations regarding the continuation of the work.
NOTE: There is no requirement for a PLMN to enhance their interconnect with SNPNs or operate an identity provider.
|
22.115
|
Service aspects; Charging and billing
|
TS
|
19.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.115/22115-j00.zip
|
The present document describes the Service Aspects of charging and billing of the 3GPP System.
The present document is not intended to duplicate existing standards or standards being developed by other groups on these topics, and will reference these where appropriate. The present document will elaborate on the charging requirements described in the Charging Principles in 3GPP TS 22.101 Service Principles. It will allow the generation of accurate charging information to be used in the commercial and contractual relationships between the parties concerned.
|
22.125
|
Unmanned Aerial System (UAS) support in 3GPP
|
TS
|
19.2.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.125/22125-j20.zip
|
The present document identifies the requirements for operation of Uncrewed Aerial Vehicles (UAVs) via the 3GPP system.
This includes requirements for meeting the business, security, and public safety needs for the remote identification and tracking of UAS linked to a 3GPP subscription.
|
22.137
|
Integrated Sensing and Communication
|
TS
|
19.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.137/22137-j10.zip
|
The present document describes functional and performance requirements for 5G wireless sensing service.
The aspects addressed in this document include:
- Overview of sensing service and operation;
- Functional requirements for sensing;
- Performance requirements (KPIs) for sensing.
|
22.153
|
Multimedia priority service
|
TS
|
19.2.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.153/22153-j20.zip
| |
22.156
|
Mobile Metaverse Services
|
TS
|
19.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.156/22156-j10.zip
|
The present document provides Stage 1 normative service and performance requirements for diverse service enablers to enhance XR-based services. The term 'metaverse' in the title of the present document embraces the broader implications of AR and VR.
Service enablers considered in this document include:
- Localized mobile metaverse service functionality;
- Avatar-based real-time communication functionality;
- Digital asset management functionality;
- Operation efficiency, exposure, coordination of mobile metaverse services.
|
22.877
|
Study on roaming value added services
|
TR
|
19.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.877/22877-j00.zip
|
The present document describes use cases related to the following three Roaming Value-Added Services (RVAS) that are enabled by the PLMN for 5GS roaming:
• Welcome SMS
• Steering of Roaming (SoR) during the registration procedure
• Subscription-based routing to a particular core network (e.g., in a different country)
Potential requirements are derived for these three services and consolidated in a dedicated chapter. The report ends with recommendation regarding the continuation of the work.
NOTE: This document is not expected to introduce any changes to the security mechanisms between operators, and responsible groups will verify that 5GS security mechanisms are not negatively impacted by these requirements.
|
22.179
|
Mission Critical Push to Talk (MCPTT); Stage 1
|
TS
|
19.3.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.179/22179-j30.zip
| |
22.268
|
Public Warning System (PWS) requirements
|
TS
|
19.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.268/22268-j10.zip
| |
22.280
|
Mission Critical Services Common Requirements (MCCoRe); Stage 1
|
TS
|
19.7.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.280/22280-j70.zip
| |
22.369
|
Service requirements for Ambient power-enabled IoT
|
TS
|
19.3.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.369/22369-j30.zip
| |
22.837
|
Study on Integrated Sensing and Communication
|
TR
|
19.4.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.837/22837-j40.zip
|
The present document describes use cases and potential requirements for enhancement of the 5G system to provide sensing services addressing different target verticals/applications, e.g. autonomous/assisted driving, V2X, UAVs, 3D map reconstruction, smart city, smart home, factories, healthcare, maritime sector.
Use cases focus on NR-based sensing, while some use cases might make use of information already available in EPC and E-UTRA (e.g. cell/UE measurements, location updates). This study will not lead to impacts on EPC and E-UTRA. Some use cases could also include non-3GPP type sensors (e.g. Radar, camera).
The aspects addressed in the present document include collecting and reporting of sensing information, sensing related KPIs. Security, privacy, regulation and charging are additional topics of concern.
|
22.840
|
Study on Ambient power-enabled Internet of Things
|
TR
|
19.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.840/22840-j00.zip
|
The present document provides Stage 1 potential 5G service requirements for ambient power-enabled Internet of Things (i.e., Ambient IoT). In the context of the present document, an Ambient power-enabled IoT device is an IoT device powered by energy harvesting, being either battery-less or with limited energy storage capability (e.g., using a capacitor) and the energy is provided through the harvesting of radio waves, light, motion, heat, or any other suitable power source. An ambient IoT device is expected to have lower complexity, smaller size and reduced capabilities and lower power consumption than previously defined 3GPP IoT devices (e.g., NB-IoT/eMTC devices). Ambient IoT devices can be maintenance free and can have long life span (e.g., more than 10 years).
The aspects addressed in the present document include:
• Study use cases of ambient power-enabled IoT and identify potential service requirements, including:
▪ Security aspects, e.g., authentication and authorization, etc.
▪ Network selection, access control, connection, mobility and identification management
▪ Charging (e.g., per data volume, per message)
▪ Aspects related to stakeholder models (e.g., involving interactions in PLMNs, NPNs or other parties)
▪ Positioning
▪ Aspects on device life cycle management related to 3GPP system.
• Study traffic scenarios, device constraints (e.g., power consumption) and identify potential performance requirements and KPIs
• Gap analysis between the identified requirements for ambient power-enabled IoT and what is already defined by existing 3GPP requirements.
Note: How Ambient IoT device performs energy harvesting is out of scope of this technical report.
|
22.841
|
Study on Upper layer traffic steering, switching and split over dual 3GPP access
|
TR
|
19.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.841/22841-j00.zip
|
The scope of this TR is to document use cases, gap analysis and potential service requirements related to 5GS support of enhanced mechanisms for steering, splitting and switching of user data, pertaining to a UE data session, across two 3GPP networks. The following scenarios are covered, where only one single PLMN subscription is assumed:
• Single PLMN;
• PLMN and NPN;
• two PLMNs.
The two 3GPP networks may use same or different RAT, i.e. NR plus NR or E-UTRA, where NR RAT can be terrestrial or satellite NR access (including different staellite orbits, e.g., GEO/MEO/LEO).
For the PLMN plus PLMN / NPN scenarios, the two networks can be managed by the same operator or by different operators (assumed to have a business agreement among them). In both cases, it is assumed that a single PLMN subscription is used to access both networks (including the NPN).
Simultaneous connectivity over two 3GPP networks presumes UE support of proper capabilities (e.g., dual radio).
It is assumed that there are no impacts to normal inter-PLMN roaming scenarios.
Dual subscription scenarios are not in scope of this TR.
|
22.843
|
Study on on Additional capabilities of mobile networks for drone operations and managements
|
TR
|
19.2.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.843/22843-j20.zip
|
The present document provides additional use cases of UAV and identifies potential requirements to improve 5G system’s support of UAV applications, UAV operations and management, including:
• Provide additional information to the UAV operator/USS to execute pre-flight preparations and inflight operation (e.g, flight mission application, flight path recommendation, flight monitoring and control);
• Use 5G system to support enhancing the UAV flight/route management based on network capacity and QoS information along the planned route;
• Use 5G system to further enhance the safety and security of UAV operations, e.g. supporting UTM in UAV detection and DAA (Detect and Avoid);
• Identify potential new security, charging and regulatory requirements on 5GS, when used for UAS operation;
• Identify potential new requirements related to redundancy and reliability of command and control (C2) traffic for UAV.
For the identified use cases, a gap analysis is performed between potential new service requirements and existing 3GPP requirements and functionalities.
NOTE: This study investigates requirements for additional 5GS capabilities to assist UTM, with the assumption that liability and responsibility for UAV operation remain under the domain of the UTM/UAV operator.
NOTE: Potential overlaps with ongoing stage-2 work (on UAS), and other SA1 studies (e.g. FS_Sensing) have been considered and avoided.
|
23.437
|
Service Enabler Architecture Layer for Verticals (SEAL); Spatial map and Spatial anchors;
|
TS
|
20.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.437/23437-k00.zip
|
The present document specifies the application layer architecture, procedures and information flows necessary for spatial anchors management and spatial mapping management to support mobile metaverse services. It includes architectural requirements, application layer architecture fulfilling the architecture requirements and procedures to manage spatial anchors and spatial maps.
The normative work in the present document is based on the requirements as defined in 3GPP TS 22.156 [2] and related use cases in 3GPP TR 22.856 [3].
|
22.850
|
Study on 3GPP AI/ML Consistency Alignment
|
TS
|
0.3.0
|
SP
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.850/22850-030.zip
|
This study will investigate ongoing AI/ML work in TSG CT, TSG RAN and TSG SA Working Groups and identify instances of any potential misalignment and/or inconsistencies and provide information on any potential outcome to the respective WGs to resolve any issues with appropriate SA-level co-ordination as necessary.
The study is led by TSG SA in close collaboration and inputs from TSG CT and TSG RAN.
|
22.851
|
Study on Network Sharing Aspects
|
TR
|
19.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.851/22851-j10.zip
|
The present document investigates use cases and potential new requirements related to 3GPP system enhanced support of specific 5G network sharing deployment scenarios, in particular where there is no direct interconnection between the shared NG-RAN and participating operators’ core networks. It includes the following aspects:
- Mobility and service continuity, e.g., when moving from a non-shared 4G/5G network to a shared 5G network and vice versa, with focus on CN aspects.
- Potential security requirements.
- Charging requirements (e.g., based on traffic differentiation in specific network sharing geographical areas).
- User/service experience (e.g., maintain the communication latency for voice, and SMS) when accessing the shared network, including scenarios of home-routed traffic or local breakout.
- Other aspects, e.g., regulatory requirements, emergency services, PWS support.
|
22.856
|
Study on Localized Mobile Metaverse Services
|
TR
|
19.2.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.856/22856-j20.zip
|
The present document investigates specific use cases and service requirements for 5GS support of enhanced XR-based services, (as XR-based services are an essential part of "Metaverse" services considered in this study,) as well as potentially other functionality, to offer shared and interactive user experience of local content and services, accessed either by users in the proximity or remotely. In particular, the following areas are studied:
- Support of interactive XR media shared among multiple users in a single location, including:
- performance (KPI) aspects; e.g. latency, throughput, connection density
- efficiency and scalability aspects, for large numbers of users in a single location.
- the combination of haptics type of XR media and other non-haptics types of XR media.
- Identification of users and other digital representations of entities interacting within the Metaverse service.
- Acquisition, use and exposure of local (physical and digital) information to enable Metaverse services, including:
- acquiring local spatial/environmental information and user/UE(s) information (including viewing angle, position and direction);
- exposing local acquired spatial, environmental and user/UE information to 3rd parties to enable Metaverse services.
- Other aspects, such as privacy, charging, public safety and security requirements.
The study also investigates gaps between the identified new potential requirements and the requirements already specified for the 5G system.
It is acknowledged that there are activities related to the topic Metaverse outside of 3GPP, such as the W3C Open Metaverse Interoperability Group (OMI). These activities may be considered in the form of use cases and related contributions to this study, but there is no specific objective for this study to consider or align with external standardization activities.
A difference between this study and TR 22.847 " Study on supporting tactile and multi-modality communication services" is that Metaverse services would involve coordination of input data from different devices/sensors from different users and coordination of output data to different devices at different destinations to support the same task or application.
|
22.865
|
Study on satellite access - Phase 3
|
TR
|
19.2.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.865/22865-j20.zip
|
The present document describes use cases and aspects related to enhancements of the 5G system over satellite, including:
• Store and Forward (S&F) Satellite operation for delay-tolerant communication service
• UE-Satellite-UE communication
• GNSS independent operation
• Positioning enhancements for satellite access
Potential service requirements are derived for these use cases and are consolidated in a dedicated chapter.
The report ends with recommendations regarding the continuation of the work.
|
22.876
|
Study on AI/ML Model Transfer Phase2
|
TR
|
19.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.876/22876-j10.zip
|
The objective of this document is to study the use cases with potential functional and performance requirements to support efficient AI/ML operations using direct device connection for various applications e.g. auto-driving, robot remote control, video recognition, etc.
The aspects addressed in the document includes:
- Identify the use cases for distributed AI inference;
- Identify the use cases for distributed/decentralized model training;
- Gap analysis to existing 5GS mechanism to support the distributed AI inference and model training.
|
22.261
|
Service requirements for the 5G system
|
TS
|
19.11.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.261/22261-jb0.zip
| |
22.882
|
Study on Energy Efficiency as service criteria
|
TR
|
19.3.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.882/22882-j30.zip
|
The present document provides stage 1 use cases and potential 5G requirements on the following aspects regarding enhancements to Energy Efficiency of 5G network and application service enabler aspects:
- Defining and supporting energy efficiency criteria as part of communication service to user and application services;
- Supporting information exposure of systematic energy consumption or level of energy efficiency to vertical customers;
- Gap analysis between the identified potential requirements and existing 5GS requirements or functionalities;
- Potential requirements on security, charging and privacy aspects.
|
22.890
|
Study on supporting railway smart station services
|
TR
|
19.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.890/22890-j00.zip
|
The present document analyses use cases of smart railway station such as station operation monitoring and control, passenger supporting services and evolution use cases of business and performance applications currently included in TR22.989 in order to derive potential requirements.
|
22.916
|
Study on Network of Service Robots with Ambient Intelligence
|
TR
|
19.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.916/22916-j00.zip
|
The present document describes use cases and aspects related to efficient communications service and cooperative operation for a group of service robots including:
◦ exposure of information between application layer and communications layer;
◦ support of on-demand high priority communications;
◦ KPIs for large-scale group operation scenarios;
◦ support of scalable and efficient use of communication resources;
◦ requirements related to media applications specific for service robots; and
◦ aspects related to security, privacy and charging
that are relevant to support stable operation of service robots. This document also describes the existing service requirements and potential correlation with other studies.
|
22.989
|
Study on Future Railway Mobile Communication System
|
TR
|
19.4.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.989/22989-j40.zip
| |
23.003
|
Numbering, addressing and identification
|
TS
|
19.3.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.003/23003-j30.zip
|
The present document defines the principal purpose and use of different naming, numbering, addressing and identification resources (i.e. Identifiers (ID)) within the digital cellular telecommunications system and the 3GPP system.
IDs that are covered by this specification includes both public IDs, private IDs and IDs that are assigned to MSs/UEs. Many of the IDs are used temporary in the networks and are allocated and assigned by the operators and some other IDs are allocated and assigned on either global, regional and national level by an administrator. See ITU-T Recommendation E.101 [122].
NOTE: Allocation means the process of opening a numbering, naming or addressing resource in a plan for the purpose of its use by a telecommunication service under specified conditions. The allocation in itself does not yet give rights for any user, whether an operator, service provider, user or someone else, to use the resource. Assignment means authorization given to an applicant for the right of use of number, naming or addressing resources under specified conditions.
The present document defines:
0) the principal purpose and use of International Mobile station Equipment Identities (IMEI) within the digital cellular telecommunications system and the 3GPP system
a) an identification plan for public networks and subscriptions in the 3GPP systems;
b) principles of assigning telephone numbers to MSs in the country of registration of the MS;
c) principles of assigning Mobile Station (MS) roaming numbers to visiting MSs;
d) an identification plan for location areas, routing areas, and base stations in the GSM system;
e) an identification plan for MSCs, SGSNs, GGSNs, and location registers in the GSM/UMTS system;
f) principles of assigning international mobile equipment identities;
g) principles of assigning zones for regional subscription;
h) an identification plan for groups of subscribers to the Voice Group Call Service (VGCS) and to the Voice Broadcast Service (VBS); and identification plan for voice group calls and voice broadcast calls; an identification plan for group call areas;
i) principles for assigning Packet Data Protocol (PDP) addresses to mobile stations;
j) an identification plan for point-to-multipoint data transmission groups;
k) an identification plan for CN domain, RNC and service area in the UTRAN system.
l) an identification plan for mobile subscribers in the WLAN system.
m) addressing and identification for IMS Service Continuity
n) an identification plan together with principles of assignment and mapping of identities for the Evolved Packet System; and
o) addressing and identification for Proximity-based (ProSe) Services.
p) an identification for Online Charging System (OCS).
q) an identification plan together with principles of assignment and mapping of identities for the 5G System.
The present document specifies functions, procedures and information which apply to GERAN Iu mode. However, functionality related to GERAN Iu mode is neither maintained nor enhanced.
|
23.007
|
Restoration procedures
|
TS
|
19.2.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.007/23007-j20.zip
|
The data stored in location registers are automatically updated in normal operation; the main information stored in a location register defines the location of each mobile station and the subscriber data required to handle traffic for each mobile subscriber. The loss or corruption of these data will seriously degrade the service offered to mobile subscribers; it is therefore necessary to define procedures to limit the effects of failure of a location register, and to restore the location register data automatically. The present document defines the necessary procedures.
The basic principle is that restoration should be based on radio contact to avoid faulty data being spread in the system.
Subscriber data for supplementary services must also be correctly restored, although the impact on service of corruption of supplementary service data is less severe.
Procedures for supporting these functions are defined in 3GPP TS 29.002 [6] and 3GPP TS 29.060 [8].
The MAP operation "IMSI Attach" is used only in MAP version 1; in MAP version 2 the same function is performed by the MAP operation "Update Location Area". References in this specification to IMSI attach apply only to MAP version 1 network entities.
If the restoration of subscriber data in the VLR is triggered by Location Updating or IMSI Attach, the VLR retrieves subscriber data from the HLR by sending an "Update Location" request, which triggers one or more "Insert Subscriber Data" operations from the HLR. The "Update Location" request may also be used to send the LMSI to the HLR.
If the restoration of subscriber data in the VLR is triggered by a "Provide Roaming Number" request, the behaviour of the VLR depends on whether it is implemented according to MAP version 1 or MAP version 2. For MAP version 2, the VLR retrieves subscriber data from the HLR by sending a "Restore Data" request, which triggers one or more "Insert Subscriber Data" operations from the HLR. The "Restore Data" request is also used to send the LMSI to the HLR. For MAP version 1, the VLR retrieves subscriber data from the HLR by sending a "Send Parameters" request with parameter type "Subscriber Data", which cannot be used to send the LMSI to the HLR.
The VLR number and MSC number in the subscriber data in the HLR are updated by the "Update Location" procedure.
The GGSN (Gateway GPRS Support Node) is the point of PDN interconnection with the GSM PLMN supporting GPRS. The GGSN contains routing information for GPRS users with a PDP context active. The necessary procedures needed to restore GGSN data information after a restart are described in this document.
The SGSN (Serving GPRS Support Node) is the node that is serving the MS. The SGSN stores information regarding e.g. mobility management, routing and security. The necessary procedures needed to restore this SGSN information after a restart are described in this document.
The MME (Mobility Management Entity) is the node that is serving the UE when attached to E-UTRAN. The MME stores information regarding e.g. mobility management, routing and security. The necessary procedures needed to restore this MME information after a restart are described in this document.
A Type A LMU (Location Measurement Unit) is a network node, accessed over the GSM air interface, that is functionally similar to an MS. All requirements associated with a non-GPRS MS in this specification apply also to a Type A LMU except where specified otherwise.
|
23.008
|
Organization of subscriber data
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.008/23008-j00.zip
|
The present document provides details concerning information to be stored in the different entities storing data within a 3GPP network concerning mobile subscriber. A list of entities storing subscriber data is provided in clause 1.
Clause 2 contains all details concerning the definition of the parameters, often given by reference to other specifications, and where the parameter is to be stored.
Table 1 in clause 3 gives a summary overview and clause 4 identifies the reference information required for accessing the information.
In this specification, if there is no specific indication, the following principles apply:
- "SGSN" refers to an SGSN which may support the Gn and Gp interfaces or the S4 interface or both.
- "S4-SGSN" refers to an SGSN which only supports the S4 interface.
- "Gn/Gp-SGSN" refers to an SGSN which only supports the Gn and Gp interfaces.
|
23.015
|
Technical realization of Operator Determined Barring (ODB)
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.015/23015-j00.zip
|
The network feature Operator Determined Barring (ODB) allows a network operator or service provider to regulate access by subscribers to services (Circuit/Packet Oriented and Interworking WLAN), by the barring of certain categories of incoming or outgoing calls/ Packet Oriented Services or of roaming. Operator Determined Barring applies to all bearer services and teleservices except the Emergency Call teleservice and Emergency Bearer Services; the teleservice Short Message Point-to-Point is therefore subject to Operator Determined Barring in the same way as circuit-switched calls.
The application of specific categories of Operator Determined Barring to a subscription is controlled by the network operator or service provider, using administrative interaction at the HLR; this interface is not standardised.
|
23.041
|
Technical realization of Cell Broadcast Service (CBS)
|
TS
|
19.1.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.041/23041-j10.zip
|
The present document describes the Cell Broadcast short message service (CBS) for GSM and UMTS.
For GSM it defines the primitives over the Cell Broadcast Centre - Base Station System (CBC-BSS) interface and the message formats over the Base Station System - Mobile Station (BSS-MS) interface for Teleservice 23 as specified in 3GPP TS 22.003 [2].
For UMTS it defines the interface requirements for the Cell Broadcast Centre – UMTS Radio Network System (RNS) interface and the radio interface requirements for UMTS Radio Acces Networks to support CBS as specified in 3GPP TS 22.003 [2].
The present document also describes the Public Warning System (PWS) for GSM, UMTS, E-UTRAN, satellite E-UTRAN, NG‑RAN, and satellite NG-RAN, see 3GPP TS 22.268 [28].
|
23.122
|
Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode
|
TS
|
19.3.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.122/23122-j30.zip
|
The present document gives an overview of the tasks undertaken by the Core network protocols of a Mobile Station (MS) when in idle mode, that is, switched on but typically not having a dedicated channel allocated. It also describes the corresponding network functions. The idle mode functions are also performed by a GPRS MS as long as no dedicated channel is allocated to the MS. The conditions when the idle mode functions are performed by an MS in the UTRA RRC connected mode states are specified in 3GPP TS 25.331 [33]. The conditions when the idle mode functions are performed by an MS in the E-UTRAN are specified in 3GPP TS 36.304 [43]. The conditions when the idle mode functions are performed by an MS in the NG-RAN are specified in 3GPP TS 36.304 [43] and 3GPP TS 38.304 [61]. The conditions when the idle mode functions are performed by an MS in the NG-RAN RRC inactive state are specified in 3GPP TS 36.331 [42] and 3GPP TS 38.331 [65].
The present document defines the PLMN selection for a multi mode MS that supports both 3GPP and 3GPP2 systems. The common PLMN selection logic covers also PLMNs that are available in 3GPP2 system, but the present document makes no changes on the cdma2000® signalling towards networks that are available via 3GPP2 system.
The present document gives procedures for using the CSG cells, whenever such use is permitted.
The present document gives procedures for using the CAG cells, when the MS supports CAG.
The present document specifies the SNPN selection.
This 3GPP TS outlines how the requirements of the 22 series Technical Specifications (especially 3GPP TS 22.011 [9]) on idle mode operation shall be implemented. Further details are given in 3GPP TS 24.008 [23].
Clause 2 of this 3GPP TS gives a general description of the idle mode process. Clause 3 outlines the main requirements and technical solutions of those requirements. Clause 4 describes the processes used in idle mode. There is inevitably some overlap between these clauses.
NOTE: cdma2000® is a registered trademark of the Telecommunications Industry Association (TIA-USA).
The present document describes the procedures for control plane solution of steering of roaming in 5GS in annex C.
Annex C is applicable to the MS, the AMF, the UDM and the SOR-AF in the 5GS.
The present document does not consider GERAN Iu mode.
|
23.167
|
IP Multimedia Subsystem (IMS) emergency sessions
|
TS
|
19.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.167/23167-j10.zip
|
This document defines the stage 2 service description for emergency services in the IP Multimedia Core Network Subsystem (IMS), including the elements necessary to support IP Multimedia (IM) emergency services and IM emergency services for eCall. ITU‑T Recommendation I.130 [4] describes a three-stage method for characterisation of telecommunication services and ITU‑T Recommendation Q.65 [3] defines stage 2 of the method.
This document covers also the Access Network aspects that are crucial for the provisioning of IMS emergency services. Other 3GPP specifications that are related to the IMS emergency services are TS 23.228 [1] on IMS in general, including fixed broadband access aspects, TS 23.060 [2] describing GPRS (UTRAN): TS 23.401 [28] describing EPS (UTRAN and E-UTRAN); TS 23.402 [29] describing Non 3GPP access (WLAN) to EPC; TS 23.271 [5] that covers location services; TS 23.216 [31] and TS 23.237 [32] describing Single Radio Voice Call Continuity (SRVCC) and Dual Radio Voice Call Continuity (DRVCC) for IMS Emergency session, TS 23.292 [45] describing the use of IMS services when using CS access for the media bearer and TS 23.501 [48] and TS 23.502 [49] describing support of emergency services and location for 5GS. TS 25.301 [6] contains an overall description of the UMTS Terrestrial Radio Access Network; TS 36.300 [30] contains an overall description of the Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); and TS 38.300 [50] contains an overall description of the Next Generation Radio Access Network (NG-RAN). Other non-3GPP specifications that are related to the IMS emergency services include 3GPP2 cdma2000 HRPD IP‑CAN, as specified in 3GPP2 X.S0060 [25] when the UE is connected to a PDS core network and 3GPP2 X.S0057‑A [39] when the UE is connected to an EPC core network.
The emergency support in different IP-CANs is described in the Informative Annex E.
|
23.180
|
Mission critical services support in the Isolated Operation for Public Safety (IOPS) mode of operation
|
TS
|
19.1.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.180/23180-j10.zip
|
This document specifies the functional architecture, procedures and information flows needed to support mission critical services in the IOPS mode of operation. IOPS mode of operation allows an isolated 3GPP network to maintain a level of MC services in case the backhaul connection is lost. For example, for EPS the IOPS mode of operation is defined in 3GPP TS 23.401 [2].
The corresponding service requirements are defined in 3GPP TS 22.346 [9] and 3GPP TS 22.280 [11].
The present document is applicable to support mission critical services in the IOPS mode of operation for 3GPP access types, such as E-UTRAN or 5G.
The functional architecture to support mission critical services in the IOPS mode of operation can be used for public safety applications and also for general commercial applications, e.g. utility companies and railways, for the case of a backhaul failure.
|
23.203
|
Policy and charging control architecture
|
TS
|
19.2.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.203/23203-j20.zip
|
The present document specifies the overall stage 2 level functionality for Policy and Charging Control that encompasses the following high level functions for IP‑CANs (e.g. GPRS, Fixed Broadband, EPC, etc.):
- Flow Based Charging for network usage, including charging control and online credit control, for service data flows and application traffic;
- Policy control (e.g. gating control, QoS control, QoS signalling, etc.).
The present document specifies the Policy and Charging Control functionality for Evolved 3GPP Packet Switched domain, including both 3GPP accesses GERAN/UTRAN/E-UTRAN and Non-3GPP accesses, according to TS 23.401 [17] and TS 23.402 [18].
The present document specifies functionality for unicast bearers. Broadcast and multicast bearers, such as MBMS contexts for GPRS, are out of scope of the present document.
NOTE: For E-UTRAN access, the usage of functionalities covered in this specification for features such as MBMS, CIoT and V2X is described in TS 23.246 [6], TS 23.682 [42] and TS 23.285 [48], respectively.
|
23.204
|
Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2
|
TS
|
19.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.204/23204-j10.zip
|
The present document specifies the new capabilities and enhancements needed to support SMS over a generic IP Connectivity Access Network (IP-CAN) using IMS capabilities (TS 23.228 [9]). These include (but are not limited) to:
1 Enhancements to the HSS;
2 Communication between the SMS-GMSC/SMS-IWMSC and the HSS;
3 Authentication of service usage and registration;
4 Transfer of UE Terminated SMS, UE Originated SMS, and Delivery reports;
5 Mechanisms to handle SMS when there is more than one IP connection active with the UE, etc.
6 Mechanisms to handle MT-SMS without MSISDN to IMS UE, and SMS between IMS UEs that support MSISDN-less SMS operation.
The document also specifies the capabilities and enhancements needed to support the service level interworking for the Short Message service as defined in the TS 23.040 [2] and in this specification and the Instant Messaging service as defined in OMA-TS-SIMPLE_IM-V1_0 [12]. The features supported from the IM specification are limited to the exchange of short or large immediate messages in pager mode.
NOTE: The page-mode immediate message as defined in TS 24.247[14] is considered as a subset of OMA-TS-SIMPLE-IM-V1_0 [12].
The document also specifies the capabilities and enhancements needed to support service level interworking for the Short Message service, as defined in the TS 23.040 [2] and in this specification and the OMA CPM service as defined in OMA-TS-CPM_Conv_Fnct-V1_0 [17]. The features supported from the CPM specification are the exchange of short or large immediate messages in pager mode, as well as session-based messaging.
The service requirements are described in TS 22.340 [18].
|
23.222
|
Common API Framework for 3GPP Northbound APIs
|
TS
|
19.6.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.222/23222-j60.zip
|
The present document specifies the architecture, procedures and information flows necessary for the CAPIF. The aspects of this specification include identifying architecture requirements for the CAPIF (e.g. registration, discovery, identity management) that are applicable to any service APIs when used by northbound entities, as well as any interactions between the CAPIF and the service APIs themselves. The common API framework applies to both EPS and 5GS, can be hosted within a PLMN or SNPN, and is independent of the underlying 3GPP access (e.g. E-UTRA, NR).
|
23.228
|
IP Multimedia Subsystem (IMS); Stage 2
|
TS
|
19.3.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.228/23228-j30.zip
|
This document defines the stage-2 service description for the IP Multimedia Core Network Subsystem (IMS), which includes the elements necessary to support IP Multimedia (IM) services. ITU‑T Recommendation I.130 [4] describes a three-stage method for characterisation of telecommunication services and ITU‑T Recommendation Q.65 [3] defines stage 2 of the method.
This document does not cover the Access Network functionality except as they relate to provision of IM services, these aspects are covered in the normative Annexes.
This document identifies the mechanisms to enable support for IP multimedia applications. In order to align IP multimedia applications wherever possible with non-3GPP IP applications, the general approach is to adopt non-3GPP specific IP based solutions.
|
23.247
|
Architectural enhancements for 5G multicast-broadcast services
|
TS
|
19.2.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.247/23247-j20.zip
|
The present document specifies architectural enhancements to the 5G system using NR to support multicast and broadcast communication services, complying to the requirements in TS 22.146 [2], TS 22.246 [3] and TS 22.261 [4]. This document encompasses support for functions such as how to deliver multicast and broadcast communications including support within certain location areas, mobility, MBS session management, policy control and QoS, and support for features e.g. group message delivery.
The present document also covers interworking with E-UTRAN and EPC based eMBMS for Public Safety (e.g. MCX services).
|
23.255
|
Application layer support for Uncrewed Aerial System (UAS); Functional architecture and information flows;
|
TS
|
19.5.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.255/23255-j50.zip
|
The present document specifies the functional architecture, procedures and information flows for UAS application enabler layer. This specification includes the capabilities of the application layer support for UAS that are necessary to ensure efficient use and deployment of UAS over 3GPP systems. The UAS application enabler capabilities applies to both EPS and 5GS.
|
23.256
|
Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2
|
TS
|
19.3.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.256/23256-j30.zip
|
The present document specifies architecture enhancements for supporting Uncrewed Aerial Systems (UAS) connectivity, identification and tracking, according to the use cases and service requirements defined in TS 22.125 [5].
The following functions are specified:
- UAV Identification, authentication and authorization.
- UAV 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).
- handling of unauthorized UAVs and revocation of authorization.
|
23.272
|
Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2
|
TS
|
19.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.272/23272-j10.zip
|
This document defines the Stage 2 architecture and specification for the CS Fallback and for SMS over SGs for EPS or CS Fallback and SMS over S102. The scope of this document includes the architecture enhancements for functionality to enable fallback from E-UTRAN access to UTRAN/GERAN CS domain access and to CDMA 1x RTT CS domain access, and functionality to reuse of voice and other CS-domain services (e.g. CS UDI video / LCS / USSD) by reuse of the CS domain. The functionality specified to support SMS over SGs does not trigger any CS Fallback to UTRAN/GERAN. The functionality specified to support SMS over S102 does not trigger any CS Fallback to CDMA 1xRTT CS domain.
In addition this specification includes an SMS in MME architecture option for SMS services only. This functionality does not trigger any CS Fallback and does not require SGs.
The architecture enhancements to support CS fallback to CDMA 1x RTT CS domain access for UEs with single and dual receiver configurations are specified in Annex B.
In this Release of the specification no mechanisms are specified to support CS Fallback to both UTRAN/GERAN and CDMA 1xRTT in the same PLMN. So, even when a UE has the capability to support both CS Fallback to UTRAN/GERAN CS domain and CS Fallback to CDMA 1xRTT CS domain in a given PLMN, the PLMN implements only one of the two.
|
23.434
|
Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows
|
TS
|
19.6.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.434/23434-j60.zip
|
The present document specifies the functional architecture for service enabler architecture layer (SEAL) and the procedures, information flows and APIs for each service within SEAL in order to support vertical applications over the 3GPP system. The present document is applicable to vertical applications using E-UTRAN or NR access based on the EPS or 5GS architecture defined in 3GPP TS 23.401 [9], 3GPP TS 23.246 [17], 3GPP TS 23.468 [16], 3GPP TS 23.501 [10], and 3GPP TS 23.247 [39]. To ensure efficient use and deployment of vertical applications over 3GPP systems this specification for SEAL services includes the group management, configuration management, location management, identity management, key management, network resource management, notification management, network slice capability enablement, data delivery and application data analytics enablement.
|
23.435
|
Procedures for Network Slice Capability Exposure for Application Layer Enablement Service
|
TS
|
19.3.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.435/23435-j30.zip
|
The present document specifies the procedures and information flows necessary for Network Slice Capability Exposure for Application Layer Enablement on the basis of SEAL.
|
23.281
|
Functional architecture and information flows to support Mission Critical Video (MCVideo); Stage 2
|
TS
|
19.7.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.281/23281-j70.zip
| |
23.282
|
Functional architecture and information flows to support Mission Critical Data (MCData); Stage 2
|
TS
|
19.7.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.282/23282-j70.zip
|
This document specifies the functional architecture, procedures and information flows needed to support the Mission Critical Data (MCData) services. MCData is a suite of services which utilizes the common functional architecture defined in 3GPP TS 23.280 [5] to support MC services over LTE including the common services core.
MCData services suite consists of the following sub-services:
- short data service (SDS);
- file distribution (FD);
- data streaming (DS); and
NOTE: Procedures for DS are not covered in the current specification.
- IP connectivity.
MCData features include:
- conversation management;
- transmission and reception control;
- communication release; and
- enhanced status.
The corresponding service requirements are defined in 3GPP TS 22.282 [3] and 3GPP TS 22.280 [2].
The present document is applicable primarily to MCData service using E-UTRAN access based on the EPC architecture defined in 3GPP TS 23.401 [4]. Certain application functions of the MCData service could also be supported via non-3GPP access networks but no additional functionality is specified to support non-3GPP access.
The MCData service can be used for public safety applications and also for general commercial applications e.g. utility companies and railways.
|
23.283
|
Mission Critical Communication Interworking with Land Mobile Radio Systems
|
TS
|
19.3.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.283/23283-j30.zip
| |
23.288
|
Architecture enhancements for 5G System (5GS) to support network data analytics services
|
TS
|
19.3.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.288/23288-j30.zip
|
The present document defines the Stage 2 architecture enhancements for 5G System (5GS) to support network data analytics services in 5G Core network.
|
23.289
|
Mission Critical services over 5G System; Stage 2
|
TS
|
19.6.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.289/23289-j60.zip
| |
23.304
|
Proximity based Services (ProSe) in the 5G System (5GS)
|
TS
|
19.4.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.304/23304-j40.zip
|
The present document specifies the Stage 2 of the Proximity based Services (ProSe) features in 5GS. 5G ProSe features consist of: 5G ProSe Direct Discovery, 5G ProSe Direct Communication, 5G ProSe UE-to-Network Relay, 5G ProSe UE-to-UE Relay and 5G ProSe Intermediate UE-to-Network Relay.
5G ProSe Direct Discovery identifies that 5G ProSe-enabled UEs are in proximity using NR.
5G ProSe Direct Communication enables establishment of communication paths between two or more 5G ProSe-enabled UEs that are in direct communication range using NR.
5G ProSe UE-to-Network Relay enables indirect Layer-2 and Layer-3 single-hop communication and Layer-3 multi-hop communication between the 5G network and 5G ProSe-enabled UEs (e.g. for 5G ProSe-enabled UEs that are out of coverage of the network).
Editor's note: Support for Multi-hop Layer-2 UE-to-Network relaying will be aligned with RAN WGs' progress/decision.
5G ProSe UE-to-UE Relay enables indirect Layer-2 and Layer-3 single-hop communication and Layer-3 multi-hop communication between two 5G ProSe End UEs.
5G ProSe Intermediate UE-to-Network Relay enables Layer-3 multi-hop communication between a 5G Remote UE and a 5G ProSe UE-to-Network Relay.
Security aspects of ProSe in 5GS are defined in TS 33.503 [29].
|
23.316
|
Wireless and wireline convergence access support for the 5G System (5GS)
|
TS
|
19.2.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.316/23316-j20.zip
|
The present document defines the enhancements to Stage 2 system architecture, procedure and flows, Policy and Charging Control for the 5G System defined in TS 23.501 [2], TS 23.502 [3] and TS 23.503 [4] in order to support wireline access network and Fixed Wireless Access. The specifications defined in TS 23.501 [2], TS 23.502 [3] and TS 23.503 [4] apply to the wireline access network and Fixed Wireless Access.
|
23.369
|
Architecture support for Ambient power-enabled Internet of Things; Stage 2
|
TS
|
19.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.369/23369-j00.zip
|
The present document specifies architectural enhancements to the 5G system to support Ambient power-enabled Internet of Things, complying to the requirements in TS 22.369 [2] applicable to the AIoT Device types, traffic types, use cases and connectivity topologies defined in TS 38.300 [5].
|
23.379
|
Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2
|
TS
|
19.7.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.379/23379-j70.zip
|
This document specifies the functional architecture, procedures and information flows needed to support the mission critical push to talk (MCPTT) service. The MCPTT service utilizes the common functional architecture to support MC services over LTE including the common services core defined in 3GPP TS 23.280 [16].Support for both MCPTT group calls and MCPTT private calls operating in on-network and off-network modes of operation is specified.
The corresponding service requirements are defined in 3GPP TS 22.179 [2] and 3GPP TS 22.280 [17].
The present document is applicable primarily to MCPTT voice service using E-UTRAN access based on the EPC architecture defined in 3GPP TS 23.401 [8]. Certain application functions of the MCPTT service such as dispatch and administrative functions could also be supported via non-3GPP access networks but no additional functionality is specified to support non-3GPP access.
The MCPTT service requires preferential handling compared to normal telecommunication services e.g. in support of police or fire brigade including the handling of prioritised MCPTT calls for emergency and imminent threats.
The MCPTT service can be used for public safety applications and also for general commercial applications e.g. utility companies and railways.
In the present document, MCPTT calls between MCPTT users on different MCPTT systems are considered.
|
23.380
|
IMS Restoration Procedures
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.380/23380-j00.zip
|
The present document specifies the procedures required in 3GPP IMS to handle a S-CSCF or a P-CSCF service interruption scenario with minimum impact to the service to the end user.
NOTE: IMS Restoration Procedures covering service interruption of other network elements are not defined in this version of the specification.
|
23.392
|
Application enablement aspects for MMTel
|
TS
|
19.1.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.392/23392-j10.zip
|
The present document specifies the application layer architecture and procedures to support the MMTel service, and also specifies the service enabler layer capability exposure procedures and related APIs for enablement aspects of MMTel service
This work takes into consideration the existing stage 1 and stage 2 work within 3GPP related to MMTel service specified in 3GPP TS 22.261 [2], 3GPP TS 23.228 [3] and 3GPP TS 26.114 [4].
|
23.401
|
General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access
|
TS
|
19.3.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.401/23401-j30.zip
|
The present document defines the Stage 2 service description for the Evolved 3GPP Packet Switched Domain - also known as the Evolved Packet System (EPS) in this document. The Evolved 3GPP Packet Switched Domain provides IP connectivity using the Evolved Universal Terrestrial Radio Access Network (E-UTRAN).
The specification covers both roaming and non-roaming scenarios and covers all aspects, including mobility between E-UTRAN and pre-E-UTRAN 3GPP radio access technologies, policy control and charging, and authentication.
The Radio Access Network functionality is documented only to the extent necessary to describe the overall system. TS 36.300 [5] contains the overall description of the Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN).
ITU-T Recommendation I.130 [3] describes a three-stage method for characterisation of telecommunication services, and ITU-T Recommendation Q.65 [4] defines Stage 2 of the method.
TS 23.402 [2] is a companion specification to this specification.
An Evolved Packet System architecture optimised for the support of Cellular IoT (Internet of Things) applications is also defined in this document.
The Evolved Packet System also provides support for the E-UTRAN to control a Dual Connectivity radio connection that uses a combination of E-UTRA and another radio access technology (e.g. NR). TS 36.300 [5] contains the overall description for Dual Connectivity.
Enhancements to support interworking of EPS with 5GS are captured in TS 23.501 [83] and TS 23.502 [84].
|
23.433
|
Service Enabler Architecture Layer for Verticals (SEAL); Data Delivery enabler for vertical applications
|
TS
|
19.6.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.433/23433-j60.zip
|
The present document specifies the application enabling layer platform architecture, capabilities and services to efficiently support storage and delivery for the application content/data for vertical applications as part of SEAL services specified in 3GPP TS 23.434 [4].
This work takes into consideration the existing stage 1 and stage 2 work within 3GPP related to data delivery and 3GPP system user plane aspects specified in 3GPP TS 22.261 [2] and 3GPP TS 23.501 [5].
|
23.273
|
5G System (5GS) Location Services (LCS); Stage 2
|
TS
|
19.3.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.273/23273-j30.zip
|
The present document specifies the stage 2 of the service-based architecture used for location services in the 5G system, and corresponding Network Functions (NFs), NF services and procedures, to meet the service requirements defined in TS 22.261 [3] and TS 22.071 [2].
Location Services specified in the present document include regulatory location services and commercial location services. The architecture and signalling procedures in NG-RAN are defined in TS 38.305 [9].
|
23.436
|
Functional architecture and information flows for Application Data Analytics Enablement Service
|
TS
|
19.4.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.436/23436-j40.zip
|
The present document specifies the procedures, information flows and APIs necessary for Application Data Analytics Enablement SEAL Service.
|
23.280
|
Common functional architecture to support mission critical services; Stage 2
|
TS
|
19.7.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.280/23280-j70.zip
| |
23.437
|
Service Enabler Architecture Layer for Verticals (SEAL); Spatial map and Spatial anchors;
|
TS
|
19.2.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.437/23437-j20.zip
| |
23.438
|
Service Enabler Architecture Layer for Verticals (SEAL); Digital assets
|
TS
|
19.1.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.438/23438-j10.zip
|
The present document specifies the application layer architecture, procedures and information flows necessary for digital asset service to support mobile metaverse services. It includes architectural requirements, application layer architecture fulfilling the architecture requirements and procedures to manage digital assets.
The normative work in the present document is based on the requirements as defined in 3GPP TS 22.156 [2].
NOTE: In the current release of this specification, the digital asset type is limited to digital avatar. Other types of digital asset are for the consideration of future release.
|
23.482
|
Functional architecture and information flows for AIML Enablement Service
|
TS
|
19.2.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.482/23482-j20.zip
|
The present document specifies the procedures and information flows necessary for AIML Enablement SEAL Service.
|
23.501
|
System architecture for the 5G System (5GS)
|
TS
|
19.4.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.501/23501-j40.zip
|
The present document defines the Stage 2 system architecture for the 5G System. The 5G System provides data connectivity and services.
This specification covers both roaming and non-roaming scenarios in all aspects, including interworking between 5GS and EPS, mobility within 5GS, QoS, policy control and charging, authentication and in general 5G System wide features e.g. SMS, Location Services, Emergency Services.
ITU‑T Recommendation I.130 [11] describes a three-stage method for characterisation of telecommunication services and ITU‑T Recommendation Q.65 [12] defines Stage 2 of the method.
TS 23.502 [3] contains the stage 2 procedures and flows for 5G System and it is a companion specification to this specification.
TS 23.503 [45] contains the stage 2 Policy Control and Charging architecture for 5G System and it is a companion specification to this specification.
|
23.502
|
Procedures for the 5G System (5GS)
|
TS
|
19.4.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.502/23502-j40.zip
|
The present document defines the Stage 2 procedures and Network Function Services for the 5G system architecture which is described in the TS 23.501 [2] and for the policy and charging control framework which is described in TS 23.503 [20].
|
End of preview. Expand
in Data Studio
README.md exists but content is empty.
- Downloads last month
- 226
Size of downloaded dataset files:
2.1 MB
Size of the auto-converted Parquet files:
2.1 MB
Number of rows:
19,096