Files
2026-03-26 21:00:51 +08:00

171 lines
8.6 KiB
JSON
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
{
"description": "3GPP technical specifications and study reports index",
"documents": [
{
"id": "22280-j50",
"file": "docs/22280-j50/22280-j50.doc",
"spec": "3GPP TS 22.280 V19.5.0",
"type": "Technical Specification",
"title": "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Mission Critical Services Common Requirements (MCCoRe); Stage 1 (Release 19)",
"release": "Release 19",
"keywords": [
"MCPTT",
"MCData",
"MCVideo",
"mission critical",
"public safety",
"maritime"
],
"summary": "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",
"_mtime": 1774526763.1365554
},
{
"id": "22369-j20",
"file": "docs/22369-j20/22369-j20.docx",
"spec": "",
"type": "",
"title": "",
"release": "Release 1",
"keywords": [
"ambient IoT",
"energy harvesting",
"battery-less",
"ambient power",
"IoT"
],
"summary": "The present document describes service and performance requirements for ambient power-enabled Internet of Things (i.e. Ambient IoT) . In the context of the present document, Ambient 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 power source that could be seen suitable. An A mbient IoT device has low complexity, small size and lower capabilities and lower power consumption than previously defi",
"_mtime": 1774526763.4285553
},
{
"id": "22837-j40",
"file": "docs/22837-j40/22837-j40.docx",
"spec": "",
"type": "",
"title": "",
"release": "Release 1",
"keywords": [
"sensing",
"V2X",
"UAV",
"smart city",
"smart home",
"healthcare",
"maritime",
"NR",
"E-UTRA",
"5G"
],
"summary": "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.",
"_mtime": 1774526764.1485553
},
{
"id": "22840-j00",
"file": "docs/22840-j00/22840-j00.docx",
"spec": "",
"type": "",
"title": "",
"release": "Release 1",
"keywords": [
"ambient IoT",
"energy harvesting",
"battery-less",
"ambient power",
"5G",
"IoT"
],
"summary": "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 low er complexity, small er size and reduced capabilities and lower power consum",
"_mtime": 1774526766.1005547
},
{
"id": "22841-j00",
"file": "docs/22841-j00/22841-j00.docx",
"spec": "",
"type": "",
"title": "",
"release": "Release 1",
"keywords": [
"PLMN",
"NPN",
"satellite",
"GEO",
"MEO",
"LEO",
"NR",
"E-UTRA",
"5G",
"5GS"
],
"summary": "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, split ting and switch ing 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",
"_mtime": 1774526766.9005547
},
{
"id": "22843-j20",
"file": "docs/22843-j20/22843-j20.docx",
"spec": "",
"type": "",
"title": "",
"release": "Release 1",
"keywords": [
"UAV",
"5G",
"QoS",
"security"
],
"summary": "The present document provides additional use cases of UAV and identifies potential requirements to improve 5G systems 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 o",
"_mtime": 1774526761.9005556
},
{
"id": "22848-j00",
"file": "docs/22848-j00/22848-j00.docx",
"spec": "",
"type": "",
"title": "",
"release": "Release 1",
"keywords": [
"PLMN",
"NPN",
"SNPN",
"interconnect"
],
"summary": "The present document describes use cases and aspec t s rela t ed t o 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: T here is no requirement for a PLMN to enhance their interconnect with SNPNs or operate an identity provider.",
"_mtime": 1774526762.3485556
},
{
"id": "22851-j10",
"file": "docs/22851-j10/22851-j10.docx",
"spec": "",
"type": "",
"title": "",
"release": "Release 1",
"keywords": [
"interconnect",
"network sharing",
"NG-RAN",
"mobility",
"charging",
"5G",
"security"
],
"summary": "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 s",
"_mtime": 1774526762.6245556
},
{
"id": "22890-j00",
"file": "docs/22890-j00/22890-j00.doc",
"spec": "3GPP TR 22.890 V19.0.0",
"type": "Technical Report",
"title": "Study on Supporting of Railway Smart Station Services",
"release": "Release 19",
"keywords": [
"railway",
"smart station",
"station monitoring",
"passenger services",
"railway IoT",
"5G railway"
],
"summary": "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.",
"_mtime": 1774528383.0923867
}
]
}