hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
de4351bc6585aa9d49d11017627c9c5f | 26.958 | 9.2.3.1 Introduction
| This clause describes a typical rendering process close to the implementation presented in [aa]. Different variants and optimizations exist and are being used.
|
de4351bc6585aa9d49d11017627c9c5f | 26.958 | 9.2.3.2 Optional spatial binning
| Each 3D Gaussian projects to a 2D ellipse characterized by its center and covariance matrix .. We compute an axis-aligned bounding box for each ellipse by extracting the contour (typically with ) from using either eigen-decomposition or direct bounds computation.
Each Gaussian is then assigned to all overlapping ... |
de4351bc6585aa9d49d11017627c9c5f | 26.958 | 9.2.3.3 Front-to-back ordering
| To achieve correct alpha blending, Gaussians within each tile must be sorted by depth in front-to-back order. We quantize the depth values to fixed-width integer keys:
where is a scaling factor that maps the depth range to the integer key space. We then perform a stable least-significant-digit (LSD) radix sort per ... |
de4351bc6585aa9d49d11017627c9c5f | 26.958 | 9.2.3.4 Per-pixel fused evaluation and optional early termination
| For each pixel within a tile, we iterate through the depth-sorted Gaussian indices. For each Gaussian that passes the ellipse membership test:
we compute the Gaussian weight and opacity in a fused manner to minimize memory bandwidth consumption. We then accumulate the color and transmittance using the over ope... |
de4351bc6585aa9d49d11017627c9c5f | 26.958 | 9.2.3.5 Numerical precision and robustness
| All accumulation operations use float32 (32-bit floating point) precision with alpha values clamped to the range .. The transmittance is biased away from zero to avoid denormal floating-point numbers, which may significantly degrade performance. The depth scaling factor must be chosen to preserve correct near-to-far ... |
de4351bc6585aa9d49d11017627c9c5f | 26.958 | 10 High level media data workflows
| [Editor’s note: Placeholder for the description of the workflows]
|
de4351bc6585aa9d49d11017627c9c5f | 26.958 | 10.1 All-in-client configuration
| |
de4351bc6585aa9d49d11017627c9c5f | 26.958 | 10.2 Client-server configuration
| |
de4351bc6585aa9d49d11017627c9c5f | 26.958 | 11 Mapping to the 3GPP services
| [Editor’s note: Placeholder for the description of the 3GPP services used]
|
de4351bc6585aa9d49d11017627c9c5f | 26.958 | 11.1 All in UE configuration
| |
de4351bc6585aa9d49d11017627c9c5f | 26.958 | 11.2 Client-server configuration
| |
de4351bc6585aa9d49d11017627c9c5f | 26.958 | 12 Related activities and products and services
| [Editor’s note: Placeholder for the description of the products and services]
|
de4351bc6585aa9d49d11017627c9c5f | 26.958 | 12.1 Standardization activities
| |
de4351bc6585aa9d49d11017627c9c5f | 26.958 | 12.2 Services
| |
de4351bc6585aa9d49d11017627c9c5f | 26.958 | 12.3 Software and products
| With the increase in popularity of 3DGS, software and products related to 3DGS generation and rendering have proliferated. Some of these tools started out as 3D scanning or photogrammetry tools, but have added support for 3DGS generation, rendering, post-processing, etc. Below some popular consumer software and product... |
de4351bc6585aa9d49d11017627c9c5f | 26.958 | 13.1 Capture
| |
de4351bc6585aa9d49d11017627c9c5f | 26.958 | 13.2 Transmission
| 13.3 Rendering
|
affe0eaa2ccdfa49563b3572db760863 | 28.893 | 1 Scope
| The present document studies the charging aspects of sensing and communication based on the charging requirements specified in SA1 TS 22.137[2] and the progress in SA2 study from Rel-19 and Rel-20.
The following items are studied:
- Identify business models and use cases for supporting ISAC.
- Identify charging scen... |
affe0eaa2ccdfa49563b3572db760863 | 28.893 | 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.
-... |
affe0eaa2ccdfa49563b3572db760863 | 28.893 | 3 Definitions of terms, symbols and abbreviations
| |
affe0eaa2ccdfa49563b3572db760863 | 28.893 | 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].
Sensing Service: Capability to collect and provide information about object and/or characteristics ... |
affe0eaa2ccdfa49563b3572db760863 | 28.893 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
affe0eaa2ccdfa49563b3572db760863 | 28.893 | 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].
AGV Automated Guided Vehicle
API Application Programming Interface
gNB N... |
affe0eaa2ccdfa49563b3572db760863 | 28.893 | 4 Background
| |
affe0eaa2ccdfa49563b3572db760863 | 28.893 | 4.1 General
| As defined in TS 22.137 [2], Integrated Sensing and Communication (ISAC) combines sensing and communication capabilities to support various use cases such as commercial, automotive, public safety, and emergency services. The 3GPP system architecture for ISAC has been studied in TR 23.700-14 [3], which covers architectu... |
affe0eaa2ccdfa49563b3572db760863 | 28.893 | 4.2 Business Roles
| Integrated Sensing and Communication involves the following business roles:
ISAC-MNO: Provides ISAC services.
ISAC-SC: Consumes ISAC services.
|
affe0eaa2ccdfa49563b3572db760863 | 28.893 | 5 Scenarios and key issues
| |
affe0eaa2ccdfa49563b3572db760863 | 28.893 | 5.1 Topic 1: Charging for sensing service
| |
affe0eaa2ccdfa49563b3572db760863 | 28.893 | 5.1.1 Use cases
| |
affe0eaa2ccdfa49563b3572db760863 | 28.893 | 5.1.1.1 Use case 1: Converged charging based on service request and sensing results
| As concluded in TR 23.700-14 [3], the sensing service consumer consumes the sensing service by sending the sensing service request and receiving sensing results from core network.
Sensing result may contain for example presence and position of the object, Sensing QoS information, Sensing timestamp and others.
Charge... |
affe0eaa2ccdfa49563b3572db760863 | 28.893 | 5.1.2 Potential charging requirements
| REQ-SENSING_CH_SERVICE-01: The 5G system should support converged charging for sensing service based on service request and sensing results.
|
affe0eaa2ccdfa49563b3572db760863 | 28.893 | 5.1.3 Key issues
| |
affe0eaa2ccdfa49563b3572db760863 | 28.893 | 5.1.3.1 Key issue 1
| The following key issues are identified considering REQ-SENSING_CH_SERVICE-01:
- Key Issue #1a: Identification of the placement of Charging Trigger Function, charging information and the main interactions with the NFs to support converged charging for sensing service based on service request and sensing results.
|
affe0eaa2ccdfa49563b3572db760863 | 28.893 | 5.1.4 Possible solutions
| |
affe0eaa2ccdfa49563b3572db760863 | 28.893 | 5.1.4.1 Solution 1
| |
affe0eaa2ccdfa49563b3572db760863 | 28.893 | 5.1.5 Evaluation
| |
affe0eaa2ccdfa49563b3572db760863 | 28.893 | 5.1.6 Conclusion
| |
affe0eaa2ccdfa49563b3572db760863 | 28.893 | 5.2 Topic 2: Converged Charging Integrated Sensing and Communication (ISAC) Applications
| |
affe0eaa2ccdfa49563b3572db760863 | 28.893 | 5.2.1 General description and assumptions
| Integrated Sensing and Communication (ISAC) enables sensing capabilities (e.g., positioning, velocity measurement, environmental monitoring) integrated with 5G communication services as defined in TR 22.837 [4] and TS 22.137 [5].
Converged charging enables billing for combined sensing and communication usage, integrat... |
affe0eaa2ccdfa49563b3572db760863 | 28.893 | 5.2.1.1 Use Case 1: Autonomous Vehicle Environment Awareness Converged Charging Support
| An ISAC-enabled UE in a vehicle receives information of obstacles and measured velocities (per TS 22.137 [5] Table 6.2-1) in real-time, for navigation within a dedicated network slice (TS 23.501 [8] Clause 5.15).
The same UE subscription may be charged for:
• Sensing data services
Charging Party: MNO
Charged ... |
affe0eaa2ccdfa49563b3572db760863 | 28.893 | 5.2.1.2 Use Case 2: Private Network Slice supporting ISAC
| An ISAC-enabled UE either in an UAVs, AGVs and other vehicles performs indoor positioning and collision avoidance (per TR 22.837 [4]) within a private 5G network slice, coordinating with gNBs for cooperative sensing.
The Slice Owner may be charged for:
• Slice-specific creation, configuration and number of simult... |
affe0eaa2ccdfa49563b3572db760863 | 28.893 | 5.2.1.3 Use Case 3: Smart City Environmental Monitoring Converged Charging Support
| An ISAC-enabled network deployment, which is available from the MNO, monitors environmental parameters (e.g., rainfall monitoring and flooding per TR 22.837 [4] Clause 5.4) across gNBs and UEs in a public safety slice (TS 23.501 [8] Clause 5.15), aggregating data for alerts exposed to the Public Safety Provider via API... |
affe0eaa2ccdfa49563b3572db760863 | 28.893 | 6 Conclusions and recommendations
|
Annex <XA> :
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2026-01
SA5#165
S5-260586
Initial skeleton
0.0.0
2026-02
SA5#165
S5-260302 S5-260572 S5-260573 S5-260574 S5-260575 S5-260576 S5-260577 S5-260585
Add skeleton
Add scope
Add the backgro... |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 1 Scope
| The present document …
|
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-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.
-... |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 3 Definitions of terms, symbols and abbreviations
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 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.
Knowledge: structured and... |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 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].
<ABBREVIATION> <Expansion>
|
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 4 Overview
| Editor's note: This clause will provide an overview of 6G management capabilities and features.
|
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 5 6G Management Architecture Principles
| Editor's note: This clause will contain the common 6G management architecture principles identified for the study.
The overarching design goal of 6G management architecture aims to achieve highly autonomous networks with following motivations:
• Facilitate business growth and improve user experience.
• Impro... |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6 6G Management Scenarios
| Editor's note: This clause will contain brief description of management scenarios for 3GPP 6G networks and the related requirements to enable the management scenarios.
Editor's note: Drafting guidelines for the requirements and management scenarios in this clause: The requirements should be formulated as requirements ... |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1 Identified 6G Management Scenarios
| Editor's note: This clause will contain identified 6G management scenarios and the related requirements.
6.1.1 <Management Scenario Category#1>
|
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1.1.1 Management Scenario#1: Mobile service delivery and assurance for specific events
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1.1.1.1 Description
| This management scenario focus on the scenarios for 6G OAM systems supporting mobile service delivery and assurance for specific events. Following uses the Large-scale music festival scenario as an example, in which an opening ceremony and subsequent live performances are supported across multiple geographically distri... |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1.2.1 Management scenarios#1: OAM-centric issues for Individual Service Complaint Handling
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1.2.1.1 Description
| With the advent of 6G, networks are expected to achieve unprecedented levels of intelligence, enabling them to autonomously manage and resolve individual service complaints. An individual service complaint refers to a customer or consumer expressing dissatisfaction with network services, such as unstable gaming latency... |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1.3.1 Management scenarios#1: Network issues handling
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1.3.1.1 Description
| Network issues, including network performance and fault management are the critical concern for operators. These issues may affect the normal operation of the network and the quality of service. The operators need to ensure that network issues can be automatically identified, and network services can recover automatica... |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1.4 Management Scenario for Energy Saving and Energy Efficiency
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1.4.1 Management Scenario #1: RAN energy saving
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1.4.1.1 Description
| Energy saving and efficiency is a key focus for 6G, as networks are expected to support exponentially higher data rates and device densities. For 6G network evolution, the network energy efficiency optimization still plays an important role in operator network management. Operators are aiming at decreasing power consum... |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1.4.1.2 Potential Requirements
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1.4.2 Management Scenario #2: Carbon emission control to reduce carbon emission
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1.4.2.1 Description
| Besides the energy saving management, the attention on reduction of carbon emission is raised in the communication industry for 6G. The operators can power base stations using energy supplies where energy is produced using renewable or non-renewable energy sources, and with varying carbon emission factors. There is the... |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1.4.2.2 Potential Requirements
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1.5 Management Architecture for 6G
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1.5.1 Management Scenario #1: Cloud Aspects of Management and Orchestration
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1.5.1.1 Description
| The 6G management system needs to evolve to support NF Deployments in 5G (for Network Slices and Sub-Networks) and 6G networks. For 5G, existing specifications have to be enhanced to enable these deployments.
|
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1.6 Data Management Framework (DMFW)
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1.6.1 Management Scenario #1: Data Management Framework in the Management System
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1.6.1.1 Description
| With the evolution of 6G mobile networks, operators are required to manage a highly distributed and complex network. This environment spans core and radio access networks including those comprising cloud implementations, multiple layers of edge computing, and a wide range of network slices. These domains continually ge... |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1.7 Autonomous Agent
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1.7.1 Management Scenario #1: Autonomous agent within 3GPP management system
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1.7.1.1 Description
| 1. General description
6G networks introduce new capabilities that significantly broaden the scope of network including services such as ISAC, which introduce more diverse managed entities and more complex operating environments. These scenarios greatly increase the heterogeneity and operational complexity of 6G netwo... |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1.7.2 Management Scenario #2: Use case for management exposure to agents external to 3GPP system
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1.7.2.1 Description
| The 3GPP SA1 Rel-20 study (TR 22.870) has identified use cases for 6G related to application scenarios, roles, service requirements, and associated management needs of AI Agents including support for AI Agents that are external to the 3GPP management system.
Such Agents may require to access the management services pr... |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1.8.1 Management scenario#1: Systematic Root Cause Analysis and End-to-End Observability
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1.8.1.1 Description
| This management scenario describes how a causality context, established at the point of initiation of a management action and propagated across all participating domains, enables two complementary capabilities: systematic root cause analysis and end-to-end observability. The causality context is carried alongside manag... |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1.9 Intent Driven Management
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1.9.1 Management Scenario #1: Efficient intent handling by inputting intent before the events
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.1.9.1.1 Description
| When a sports match is held in a certain area, a large number of people gather around the stadium, and traffic becomes highly concentrated locally. A mobile network operator uses intent-driven operations to optimize radio service delivery in that area—e.g., to maintain user experience while also minimizing base station... |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.2 Management Scenarios for Support of 6G Services
| Editor's note: This clause will contain management scenarios for support of Use Cases for 6G service captured in SA1 TR 22.870, and the related requirements identified.
Editor's note: The management-scenario categories in clause 6.2.x level follow the SA1 UC grouping as place holders and may be updated by future cont... |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.2.1 System and Operation Aspects
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.2.1.1 Management Scenario #1: Management support for the use case on 6G network digital twin
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.2.1.1.1 Description
| This use case describes the management support for the use case on Network Digital Twin (NDT) in the 6G network defined in 3GPP TR 22.870 [3]. Autonomous Networks is a key objective of the 6G management system, aiming for efficient and low-intervention network operation. NDT is critical to supporting the realization of... |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.2.1.2 Management Scenario #2: Cloud native management scenario
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.2.1.2.1 Description
| To achieve objective of 6G resiliency use case in clause 5.6.3 of TR 22.870 [3], the 3GPP management system should follow cloud native principles to design and achieve management capabilities, for instance, adapt the decoupling characteristics of cloud-nativeness, and support elastic scaling and independent upgrading o... |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.2.2 AI
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.2.3 Integrated Sensing and Communication
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.2.4 Ubiquitous Connectivity
| According to 3GPP TR 22.870 [3], Ubiquitous Connectivity in 6G is defined as a full-space, full-time and full-scenario connectivity capability, aiming to provide continuous digital services with high quality and high reliability to users globally. Ubiquitous Connectivity is no longer limited to the extension of terrest... |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.2.4.1 Management Scenario #1: Management of TN-NTN Interworking
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.2.4.1.1 Description
| In 6G, Ubiquitous Connectivity is jointly supported by terrestrial networks (TN) and non-terrestrial networks (NTN), including multi-orbit satellites (VLEO, LEO, MEO, GSO), High Altitude Platform Systems (HAPS), and Unmanned Aerial Vehicles (UAV), as described in TR 22.870[3], TR 23.801[y] and TR 38.914[z]. These netwo... |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.2.4.1.2 Potential Requirements
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.2.5 Immersive Communication
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.2.6 Massive Communication
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.2.7 Further Use Cases on Industry and Verticals
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 6.2.8 Other Use Cases
| |
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 7 Management Features
| Editor's note: This clause will contain the identified management features to enable the 6G management scenarios in clause 6 and the related potential Key Issues. The Mapping table in Annex A will reflect the relation between the management scenarios and Key Issues.
|
bea87ebb68eb2846b39ff0938bc6c034 | 32.801-01 | 7.1 Data Management Framework (DMFW)
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.