hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
33f63d4585416d30fe17818d1cefee31 | 28.895 | 5.1.4 Evaluation of potential solutions
| 5.X Use Case#Num: title
5.X.1 Description
5.X.2 Potential requirements
5.X.3 Potential solutions
5.X.4 Evaluation of potential solutions
|
33f63d4585416d30fe17818d1cefee31 | 28.895 | 6 Conclusions and recommendations
| Editor's note: this clause will contain conclusions and recommendations for corresponding use cases identified in clause 5.
Annex <X> (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2026-02
SA5#165
xxx
-
-
-
Initial skeleton
0.0.0
2026-02
SA5#16... |
4f7d6f670443862173b4248669f20e35 | 28.894 | 1 Scope
| The present document studies on charging aspects of satellite access Phase 4 based on the TS 22.261[2] and based on ongoing study with TR 23.700-19 [3]:
This study item is to investigate charging for IMS voice call over GEO via NB-IoT NTN connecting to EPC and charging for UE-satellite-UE communication related to ser... |
4f7d6f670443862173b4248669f20e35 | 28.894 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
-... |
4f7d6f670443862173b4248669f20e35 | 28.894 | 3 Definitions of terms, symbols and abbreviations
| |
4f7d6f670443862173b4248669f20e35 | 28.894 | 3.1 Terms
| For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
UE-Satellite-UE Communication: refers to a communication between UEs under the coverage of one or m... |
4f7d6f670443862173b4248669f20e35 | 28.894 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
4f7d6f670443862173b4248669f20e35 | 28.894 | 3.3 Abbreviations
| For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
EPC Evolved Packet Core
GEO Geostationary Orbit
IMS IP Multimedia Subsys... |
4f7d6f670443862173b4248669f20e35 | 28.894 | 4 Background
| |
4f7d6f670443862173b4248669f20e35 | 28.894 | 4.1 IMS voice using GEO satellite access
| In SA1 Rel-20, the following requirements for satellite access have been specified by SA1 in TS 22.261[2]:
- IMS voice using GEO satellite access: The 5G system with GEO satellite access shall be able to support IMS voice communication as defined in TS 22.228[4]. The 5G system with GEO satellite access shall be able t... |
4f7d6f670443862173b4248669f20e35 | 28.894 | 4.2 UE-SAT-UE communication via UPF only onboard satellite for non-IMS services
| The requirements for supporting UE-satellite-UE communication have been specified by SA1 in the TS 22.261[2]. The satellite communication market has requirements that support UE-satellite-UE communication for non-IMS services (e.g., 5G-LAN with IP and Ethernet PDU Session type) when UEs are accessing network via NGSO s... |
4f7d6f670443862173b4248669f20e35 | 28.894 | 5 Charging scenarios and key issues
| |
4f7d6f670443862173b4248669f20e35 | 28.894 | 5.1 Topic #1 Charging support for IMS voice call over NB-IoT NTN connecting to EPC via GEO
| |
4f7d6f670443862173b4248669f20e35 | 28.894 | 5.1.1 General description
| The IMS voice communication over GEO satellite access is supported in the 5G system as referenced in 3GPP TS 22.261 [2], clause 6.46.11, with mechanisms to optimize IMS voice (e.g., call setup, transmission overhead) and codecs considering transmission data rate, latency, and packet size.
|
4f7d6f670443862173b4248669f20e35 | 28.894 | 5.1.2 Use cases #1.1 End-User Charging for IMS Voice over GEO NB-IoT
| An operator provides GEO satellite access via NB-IoT NTN connected to EPC for IMS voice services and wants to charge an UE based on:
• voice session duration,
• data volume
Charging Party: Operator
Charged Party: UE
|
4f7d6f670443862173b4248669f20e35 | 28.894 | 5.1.3 Potential charging requirements
| REQ-CH_SAT_PH4_IMS-01: Charging for IMS voice calls over GEO via NB-IoT NTN connecting to EPC may be supported.
|
4f7d6f670443862173b4248669f20e35 | 28.894 | 5.1.4 Key issues
| Key issue #1.1: Identify the placement of the charging trigger function for IMS voice over GEO satellite access.
|
4f7d6f670443862173b4248669f20e35 | 28.894 | 5.1.5 Possible solutions
| |
4f7d6f670443862173b4248669f20e35 | 28.894 | 5.1.6 Evaluation
| |
4f7d6f670443862173b4248669f20e35 | 28.894 | 5.1.7 Conclusion
| ……
|
4f7d6f670443862173b4248669f20e35 | 28.894 | 5.2.3 Potential charging requirements
| REQ-CH_SAT_PH4_NONIMS-01: Charging for UE-satellite-UE communications related to non-IMS service via NGSO satellite access may be supported.
|
4f7d6f670443862173b4248669f20e35 | 28.894 | 5.2 Topic #2 Charging support for UE-satellite-UE communication related to non-IMS service via NGSO satellite access
| |
4f7d6f670443862173b4248669f20e35 | 28.894 | 5.2.1 General description
| UE-satellite-UE communication for non-IMS service (e.g., 5G-LAN) is required for UEs accessing the network via NGSO satellite access (TS 22.261 [2], clause 6.46.9).
|
4f7d6f670443862173b4248669f20e35 | 28.894 | 5.2.2 Use cases#2.1 Charging for in UE-satellite-UE communication related to Non-IMS service
| An operator supports NGSO satellite access for non-IMS service in UE-satellite-UE communications (e.g., 5G-LAN) could be charged based on:
• session establishment,
• Data Volume
• mobility events.
Charging Party: Operator
Charged Party: UE
|
4f7d6f670443862173b4248669f20e35 | 28.894 | 5.2.4 Key issues
| Key issue #2.1: Identify the placement of the charging trigger function resulting in chargeable events and new charging information for non-IMS service registration and communication in UE-satellite-UE via NGSO.
|
4f7d6f670443862173b4248669f20e35 | 28.894 | 5.2.5 Possible solutions
| |
4f7d6f670443862173b4248669f20e35 | 28.894 | 5.2.6 Evaluation
| |
4f7d6f670443862173b4248669f20e35 | 28.894 | 5.2.7 Conclusion
|
6. Conclusions and Recommendations
Annex <A> :
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2026-01
SA5#165
S5-260320
Initial skeleton
0.0.0
2026-02
SA5#165
S5-260320
S5-260583
S5-260578
S5-260579
S5-260580
S5-260581
S5-260582
S5-2605... |
151d974d78ca23f73c14869235bb33b2 | 33.704 | 1 Scope
| Current network security specifications mainly focus on how to protect connections between NFs, but lack consideration of how to provision and manage network security configurations to execute such security protections. It is important to study such abilities for network operators to improve the operational capabilitie... |
151d974d78ca23f73c14869235bb33b2 | 33.704 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
-... |
151d974d78ca23f73c14869235bb33b2 | 33.704 | 3 Definitions of terms, symbols and abbreviations
| Editor’s Note: This clause needs to be revisited when new terms, symbols and abbreviations mentioned in following clauses.
|
151d974d78ca23f73c14869235bb33b2 | 33.704 | 3.1 Terms
| For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
example: text used to clarify abstract rules by applying them literally.
|
151d974d78ca23f73c14869235bb33b2 | 33.704 | 3.2 Symbols
| Void.
|
151d974d78ca23f73c14869235bb33b2 | 33.704 | 3.3 Abbreviations
| For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
|
151d974d78ca23f73c14869235bb33b2 | 33.704 | 4 Overview of Security configuration provisioning
| Editor’s Note: This clause gives overview of security policy provisioning.
|
151d974d78ca23f73c14869235bb33b2 | 33.704 | 5 Use Cases
| Editor’s Note: This clause describes use cases as indicated in objectives of SID.
|
151d974d78ca23f73c14869235bb33b2 | 33.704 | 6 Security threats analysis
| Editor’s Note: This clause analyzes related security threats based on the above use cases.
|
151d974d78ca23f73c14869235bb33b2 | 33.704 | 7 Potential Security Requirements
| Editor’s Note: This clause provides potential security requirements based on threats analysis.
|
151d974d78ca23f73c14869235bb33b2 | 33.704 | 8 Conclusion
| Editor’s Note: This clause provides conclusion based on threats analysis and potential security requirements.
Annex <A> (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
02/2026
SA3#126
S3-260582
... |
a19bbe9866ffa1bdabe17c4056d7f862 | 33.531 | 1 Scope
| |
a19bbe9866ffa1bdabe17c4056d7f862 | 33.531 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
-... |
a19bbe9866ffa1bdabe17c4056d7f862 | 33.531 | 3 Definitions of terms, symbols and abbreviations
| |
a19bbe9866ffa1bdabe17c4056d7f862 | 33.531 | 3.1 Terms
| For the purposes of the present document, the terms given in TR 21.905 [1], 3GPP TS 33.122[4] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
|
a19bbe9866ffa1bdabe17c4056d7f862 | 33.531 | 3.2 Symbols
| Void.
|
a19bbe9866ffa1bdabe17c4056d7f862 | 33.531 | 3.3 Abbreviations
| For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
CAPIF Common API Framework
CCF CAPIF Core Function
|
a19bbe9866ffa1bdabe17c4056d7f862 | 33.531 | 4 CCF-specific security requirements and related test cases
| |
a19bbe9866ffa1bdabe17c4056d7f862 | 33.531 | 4.1 Introduction
| |
a19bbe9866ffa1bdabe17c4056d7f862 | 33.531 | 4.2 CCF-specific adaptations of security functional requirements and related test cases
| |
a19bbe9866ffa1bdabe17c4056d7f862 | 33.531 | 4.2.1 Introduction
| |
a19bbe9866ffa1bdabe17c4056d7f862 | 33.531 | 4.2.2 Security functional requirements on the CCF deriving from 3GPP specifications and related test cases
| |
a19bbe9866ffa1bdabe17c4056d7f862 | 33.531 | 4.2.3 Technical Baseline
| |
a19bbe9866ffa1bdabe17c4056d7f862 | 33.531 | 4.2.4 Operating Systems
| |
a19bbe9866ffa1bdabe17c4056d7f862 | 33.531 | 4.2.5 Web Servers
| |
a19bbe9866ffa1bdabe17c4056d7f862 | 33.531 | 4.2.6 Network Devices
| |
a19bbe9866ffa1bdabe17c4056d7f862 | 33.531 | 4.3 CCF-specific adaptations of hardening requirements and related test cases
| |
a19bbe9866ffa1bdabe17c4056d7f862 | 33.531 | 4.3.1 Introduction
| |
a19bbe9866ffa1bdabe17c4056d7f862 | 33.531 | 4.3.2 Technical baseline
| |
a19bbe9866ffa1bdabe17c4056d7f862 | 33.531 | 4.3.3 Operating systems
| |
a19bbe9866ffa1bdabe17c4056d7f862 | 33.531 | 4.3.4 Web servers
| |
a19bbe9866ffa1bdabe17c4056d7f862 | 33.531 | 4.3.5 Network devices
| |
a19bbe9866ffa1bdabe17c4056d7f862 | 33.531 | 4.3.6 Network functions in service-based architecture
| |
a19bbe9866ffa1bdabe17c4056d7f862 | 33.531 | 4.4 CCF-specific adaptations of basic vulnerability testing requirements and related test cases
| |
a19bbe9866ffa1bdabe17c4056d7f862 | 33.531 | 4.4.1 Introduction
| |
a19bbe9866ffa1bdabe17c4056d7f862 | 33.531 | 4.4.2 Port Scanning
| |
a19bbe9866ffa1bdabe17c4056d7f862 | 33.531 | 4.4.3 Vulnerability scanning
| |
a19bbe9866ffa1bdabe17c4056d7f862 | 33.531 | 4.4.4 Robustness and fuzz testing
|
Annex A (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2026-01
SA3#126
S3-260278
TS Skeleton
0.1.1
2026-02
SA3#126
S3‑260970
Updating editorial comment for S3-260278
0.1.2
2026-03
SA#111
SP-260169
Presented for informatio... |
86a6300283be276330d2d4a3974ce229 | 33.801-06 | 1 Scope
| The present document studies the requirements, architecture, services, and security of the lawful interception system as it pertains to 6G. The present document also addresses details regarding the following specific topic areas:
- ASN.1 usage, release schedule and protocols supported.
- Modularity of specification r... |
86a6300283be276330d2d4a3974ce229 | 33.801-06 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
-... |
86a6300283be276330d2d4a3974ce229 | 33.801-06 | 3 Definitions of terms, symbols and abbreviations
| |
86a6300283be276330d2d4a3974ce229 | 33.801-06 | 3.1 Terms
| For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
|
86a6300283be276330d2d4a3974ce229 | 33.801-06 | 3.2 Symbols
| Void.
|
86a6300283be276330d2d4a3974ce229 | 33.801-06 | 3.3 Abbreviations
| For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
LI Lawful Interception
|
86a6300283be276330d2d4a3974ce229 | 33.801-06 | 4 Key topics
| Editor’s Note: This clause contains all the key topics identified during the study.
|
86a6300283be276330d2d4a3974ce229 | 33.801-06 | 4.1 Key Topic 1: ASN.1 usage, release schedule and protocols
| |
86a6300283be276330d2d4a3974ce229 | 33.801-06 | 4.1.1 Key topic 1 details and discussion
| |
86a6300283be276330d2d4a3974ce229 | 33.801-06 | 4.1.1.1 ASN.1 Usage
| Clause 4.1 contains details and discussion regarding ASN.1 usage, release schedule, and protocols as they pertain to the evolution of 5G lawful interception to 6G lawful interception formats.
ASN.1 has been used within the 3GPP SA3-LI group as the preferred X and HI interface code solution for the past two generations... |
86a6300283be276330d2d4a3974ce229 | 33.801-06 | 4.1.1.2 ASN.1 Release Schedule
| SA3-LI has worked, historically, on a version based ASN.1 release schedule. This means that for example, 15 versions of ASN.1 available for deployment. This is concerning because small errors within the ASN.1 are not documented in a manner that would be clear to the implementer. Transitioning to a methodology like that... |
86a6300283be276330d2d4a3974ce229 | 33.801-06 | 4.1.1.3 ASN.1 Protocols
| Currently, SA3-LI supports the use of ASN.1, but also supports the use of sub-types such as XML, JSON, XSD, etc. While the use of such protocols encapsulated within ASN.1 have been codified, it may be necessary to support new and more frequent use cases. 3GPP should consider what guidance for use and what restrictions ... |
86a6300283be276330d2d4a3974ce229 | 33.801-06 | 4.1.1.4 ASN.1 Duplication in X and HI interfaces
| TS 33.128 [3] specifies separate ASN.1 coding for X2 and HI2 messages. However, when a HI2 message is generated based on a triggering equivalent X2 message, the two ASN.1 coding are just a duplication. SA3-LI should consider whether it is beneficial to specify a single ASN.1 coded message which could be applicable to b... |
86a6300283be276330d2d4a3974ce229 | 33.801-06 | 4.1.1.5 ASN.1 module split for separate LI capabilities
| Currently, TS 33.128 [3] includes into a single ASN.1 module all the definitions the LI capabilities specified in TS 33.128 [3]. This was probably the best choice at the beginning of the specification work for 5G but after years it has become a really huge module, difficult to handle and in which it is difficult to ide... |
86a6300283be276330d2d4a3974ce229 | 33.801-06 | 4.1.2 Potential requirements
| PR-4.1.2.A: SA3-LI shall only produce one version of ASN.1 per release. Interim versioning shall only be available in draft format, curated within 3GPP Forge, updated with CR additions post agreement. Finalized ASN.1 drop shall be captured in a new clause, e.g. within TS 33.128 [3] or its 6G equivalent, when it is decl... |
86a6300283be276330d2d4a3974ce229 | 33.801-06 | 4.1.3 Potential resolution strategy
| Editor’s Note: This clause will contain resolution strategies, either in e.g. Requirements, or otherwise as it relates to the key topic and potential requirements identified during the study.
|
86a6300283be276330d2d4a3974ce229 | 33.801-06 | 4.2 Key Topic 2: Mapping of data structures
| |
86a6300283be276330d2d4a3974ce229 | 33.801-06 | 4.2.1 Key topic 2 details and discussion
| |
86a6300283be276330d2d4a3974ce229 | 33.801-06 | 4.2.1.1 Basic information for LI in dedicated fields
| |
86a6300283be276330d2d4a3974ce229 | 33.801-06 | 4.2.1.1.1 LI-specific information in dedicated fields
| Clause 4.2 contains details and discussion regarding the mapping or encapsulation of various data elements in LI reporting.
Information is added by CSP’s LI systems to the captured data (e.g. communication contents) for the delivery to the LEMF of the LEA such that the delivered parts of the data are unequivocally re-... |
86a6300283be276330d2d4a3974ce229 | 33.801-06 | 4.2.1.1.2 Specific fields for basic information about the communication
| As LI data may be used in court as evidence, people that are not experts of telecommunication systems need to be able to get an accurate understanding of the basic circumstances of the telecommunication (e.g. who called whom). LI specifications help provide such clarity through mapping such information into dedicated f... |
86a6300283be276330d2d4a3974ce229 | 33.801-06 | 4.2.1.2 Reusing data structures for enhanced technical details
| For technical details (e.g. what frequencies were used at the RAN access), the information likely needs to be analysed by experts anyway to draw conclusion from this. Hence, to avoid extra work and keep the information up-to-date, such information could be passed through reusing the data structures of publicly availabl... |
86a6300283be276330d2d4a3974ce229 | 33.801-06 | 4.2.2 Potential requirements
| PR-4.X.2.YA: SA3-LI shall use dedicated fields for handling LI delivery, e.g. information required in TS 33.126 [2] clause 6.4.
PR-4.X.2.YB: SA3-LI shall map basic information on the circumstances of the communication into dedicated fields of the LI specification.
|
86a6300283be276330d2d4a3974ce229 | 33.801-06 | 4.2.3 Potential resolution strategy
| |
86a6300283be276330d2d4a3974ce229 | 33.801-06 | 4.2.3.1 Potential resolution strategy for providing basic information for LI in dedicated fields
| If ASN.1 usage and handover using ETSI TS 102 232‑1 [6] is continued, information could be mapped into existing dedicated fields of ETSI TS 102 232‑1 [6] potentially extended by additional data structures, where needed. A corresponding analysis could be conducted on a service-by-service basis for new 6G services.
|
86a6300283be276330d2d4a3974ce229 | 33.801-06 | 4.2.3.2 Potential resolution strategy for reusing data structured
| A generic structure for delivery of such information could consist of:
- Reference to the specification and its version.
- Information on the format type or definition language (e.g. JSON, ASN.1, XML, etc.).
- Reference to the data type or structure within the specification.
- "raw data".
|
86a6300283be276330d2d4a3974ce229 | 33.801-06 | 5 Solutions
| Editor’s Note: This clause contains the proposed solutions addressing the identified key topics.
|
86a6300283be276330d2d4a3974ce229 | 33.801-06 | 5.1 Mapping of resolution strategy to key topics
| Editor’s Note: This clause captures mapping between key topics and solutions.
Table 5.1-1: Mapping of solutions to key topics
Key Topic
Solutions
5.Y Strategy #Y: <Strategy Name>
5.Y.1 Introduction
Editor’s Note: Each strategy should list the key topic(s) being addressed.
5.Y.2 Strategy d... |
86a6300283be276330d2d4a3974ce229 | 33.801-06 | 6 Conclusions
| Editor’s Note: This section will highlight the agreed way forward on each key topic area as endorsed by SA3-LI.
Editor’s Note: This clause captures the conclusions of this study.
Annex A:
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2026-01
SA3#100-LI
S3i26... |
ecb1080365e85dba71ee08885f1352be | 38.720-01-01 | 1 Scope
| The present document is a technical report for NR Intra-band Carrier Aggregation Rel-20 for xDL/yUL including contiguous and non-contiguous spectrum under Rel-20 time frame. The purpose is to gather the relevant background information and studies to address NR Intra-band Carrier Aggregation requirements for the Rel-20 ... |
ecb1080365e85dba71ee08885f1352be | 38.720-01-01 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
-... |
ecb1080365e85dba71ee08885f1352be | 38.720-01-01 | 3 Definitions of terms, symbols and abbreviations
| |
ecb1080365e85dba71ee08885f1352be | 38.720-01-01 | 3.1 Terms
| For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
example: text used to clarify abstract rules by applying them literally.
|
ecb1080365e85dba71ee08885f1352be | 38.720-01-01 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.