hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
c87765bd88910b968f2a46607f719dbf | 26.836 | 5.1 General
| Editor’s note: This clause documents the evaluation of QUIC-based media delivery protocols against existing architectures and protocols defined in the RTC System. The evaluation is conducted in terms of architectural aspects including supported functional features as well as performance aspects, based on the applicatio... |
c87765bd88910b968f2a46607f719dbf | 26.836 | 5.2 Application scenarios
| Editor’s note: This clause describes potential application scenarios for RTC using QUIC-based media delivery protocols.
|
c87765bd88910b968f2a46607f719dbf | 26.836 | 5.2.1 Introduction
| 5.2.x Scenario#x: <scenario name>
Editor’s note: Each individual subsequent clause describes possible RTC service scenarios.
|
c87765bd88910b968f2a46607f719dbf | 26.836 | 5.3 Architectural and functional evaluation
| Editor’s note: Documentation of potential impacts, advantages and disadvantages of integrating QUIC-based technologies into the RTC media delivery architecture (as defined in TS 26.506), 5G Core Network architecture (as defined in TS 23.501), as well as on UE implementations. This includes an analysis of the advantages... |
c87765bd88910b968f2a46607f719dbf | 26.836 | 5.3.1 Protocol#1: <protocol name>
| |
c87765bd88910b968f2a46607f719dbf | 26.836 | 5.3.1.1 Potential architectural enhancements
| Editor’s note: Documents how each identified QUIC-based media delivery protocol is applicable to the application scenarios. Then identify the potential architectural enhancements to implement the QUIC-based media delivery protocol into RTC system.
|
c87765bd88910b968f2a46607f719dbf | 26.836 | 5.3.1.2 Advantages and disadvantages for application scenarios
| Editor’s note: Documents advantages and disadvantages of integrating QUIC-based media delivery protocols into the RTC System for each application scenario.
|
c87765bd88910b968f2a46607f719dbf | 26.836 | 5.3.2 Summary
| |
c87765bd88910b968f2a46607f719dbf | 26.836 | 5.4 Performance evaluation
| Editor’s note: The performance evaluation utilizes the test framework described in TR 26.934 ("Test platform for media delivery technologies").
|
c87765bd88910b968f2a46607f719dbf | 26.836 | 5.4.1 Performance metrics
| Editor’s note: Definition of appropriate performance metrics for evaluation of QUIC-based media delivery protocols.
|
c87765bd88910b968f2a46607f719dbf | 26.836 | 5.4.2 Evaluated protocols
| |
c87765bd88910b968f2a46607f719dbf | 26.836 | 5.4.2.1 Protocol#1: <protocol name>
| |
c87765bd88910b968f2a46607f719dbf | 26.836 | 5.4.2.1.1 General
| |
c87765bd88910b968f2a46607f719dbf | 26.836 | 5.4.2.1.2 Evaluation conditions
| |
c87765bd88910b968f2a46607f719dbf | 26.836 | 5.4.2.1.3 Evaluation results
| Editor’s note: Documentation of the results obtained using the test framework defined in TR 26.934.
|
c87765bd88910b968f2a46607f719dbf | 26.836 | 5.5 Evaluation summary
| Editor’s note: Documents the overall evaluation as the summary. This includes advantages and disadvantages on RTC system, benefits for application scenarios, and performance evaluation result.
|
c87765bd88910b968f2a46607f719dbf | 26.836 | 6 Integration of the QUIC-based media delivery protocols into the RTC System
| |
c87765bd88910b968f2a46607f719dbf | 26.836 | 6.1 General
| Editor’s note: This clause documents potential integration scenarios. This clause is expected to be addressed if any of the QUIC-based media delivery protocols documented in clause 4 are found to be beneficial for RTC, based on the evaluation in clause 5.
|
c87765bd88910b968f2a46607f719dbf | 26.836 | 6.2 Candidate solutions
| Editor’s note: This clause documents potential solutions.
|
c87765bd88910b968f2a46607f719dbf | 26.836 | 6.3 Summary of the solutions
| Editor’s note: This clause summarizes the proposed solutions and potential normative work related to the solutions. This can include evaluation / comparison of solutions.
|
c87765bd88910b968f2a46607f719dbf | 26.836 | 7 Conclusions and recommendations
| Editor’s note: This clause provides the conclusions of this study and recommendations.
Annex A (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2026-02
SA4#135
S4-260076
Initial version, technical report skeleton
0.0.1
2026-02
SA4#135
S4-... |
c87765bd88910b968f2a46607f719dbf | 26.836 | 4.2.31 WebTransport
| |
c87765bd88910b968f2a46607f719dbf | 26.836 | 4.2.31.1 Introduction
| WebTransport is a modern web API and protocol framework that enables secure, low‑latency, bidirectional communication between browsers or web apps and servers. WebTransport is designed to cover use cases where the WebSocket API is too limited (single, ordered, reliable byte stream over TCP) and where the WebRTC Data Ch... |
c87765bd88910b968f2a46607f719dbf | 26.836 | 4.2.31.2 Features
| WebTransport provides a session-based communication model supporting multiple independent unidirectional and bidirectional streams, ensuring reliable and ordered delivery of byte streams. It also allows for unreliable delivery using QUIC datagrams. The API exposes readable/writable streams and datagrams to developers,... |
c87765bd88910b968f2a46607f719dbf | 26.836 | 4.2.31.3 Benefits and limitations
| Benefits:
- Leverage benefits of QUIC within the standard web security model (origin-based access control, secure contexts) providing browser support. The W3C WebTransport API [33] exposes the capabilities of QUIC through a high-level, stream-oriented JavaScript interface aligned with the Web Streams paradigm, offeri... |
c87765bd88910b968f2a46607f719dbf | 26.836 | 4.2.31.4 Current applications
| MOQT can be layered on top of WebTransport (see clause 4.2.3).
WebTransport implementations over QUIC (HTTP/3) are available both for clients and servers:
- Google Chrome and Microsoft Edge browsers implement client-side W3C WebTransport API [33] over QUIC.
- Many open-source server-side implementations exist. Some ... |
c87765bd88910b968f2a46607f719dbf | 26.836 | 4.2.1 Media over QUIC Transport (MOQT)
| |
c87765bd88910b968f2a46607f719dbf | 26.836 | 4.2.1.2.1 Introduction
| Below is a non-exhaustive summary of MOQT's key features. For further details, refer to draft-ietf-moq-transport [18].
|
c87765bd88910b968f2a46607f719dbf | 26.836 | 4.2.1.2.2 Object-based data model
| MOQT’s data model represents each MOQT schedulable unit of content as an Object within a named Track, organized into Groups and Subgroups. Objects are identified by an Object ID within a Group/Subgroup and carry metadata including Track Alias, Group ID, Object IDs, Publisher Priority, and optional extension headers.
A... |
c87765bd88910b968f2a46607f719dbf | 26.836 | 4.2.1.2.3 Publish/Subscribe workflow
| MOQT’s publish/subscribe workflow enables publishers to make media Tracks available within designated namespaces, allowing subscribers to select only the namespaces and Tracks they need.
Publishers are endpoints that handle subscriptions by sending requested Objects from the requested Track; the initial publisher of a... |
c87765bd88910b968f2a46607f719dbf | 26.836 | 4.2.1.2.4 Data transport over streams and datagrams
| Objects are transmitted either on QUIC streams (reliable, ordered) or as QUIC DATAGRAM frames (unreliable, unordered) as defined in IETF RFC 9221 [14].
Grouping mutually dependent Objects together in a QUIC stream can provide operational advantages, such as improved prioritization. This is achieved by using Subgroups ... |
c87765bd88910b968f2a46607f719dbf | 26.836 | 4.2.1.2.5 Relay behaviour and scalability
| MOQT Relays support both fan-in and fan-out: they can ingest tracks from multiple publishers (fan-in), acquire Tracks once and serve many subscribers (fan-out), thereby facilitating scalable distribution in a manner analogous to Content Delivery Networks (CDNs). Furthermore, relays function as policy enforcement points... |
c87765bd88910b968f2a46607f719dbf | 26.836 | 4.2.1.4 Related Internet Drafts in the IETF MOQ WG
| The MOQ WG also develops container formats that specify encapsulation of MOQT data and media streaming formats operating over MOQT that specify media packaging as well as signalling mechanisms for negotiation between MOQT endpoints. These formats include:
- Low Overhead Media Container (LOC) [21]. LOC is a low-overhea... |
c87765bd88910b968f2a46607f719dbf | 26.836 | 4.2.1.5 Current applications
| - Several open-source implementations of the IETF draft exist. A non-exhaustive list is given below:
- Google’s production-ready implementation supports MOQT: https://github.com/google/quiche
- Meta provides an experimental MOQT Relay and live encoder/player designed to work with it:
- Relay: https://github.com/face... |
c87765bd88910b968f2a46607f719dbf | 26.836 | 4.2.3 WebTransport
| |
c87765bd88910b968f2a46607f719dbf | 26.836 | 4.2.3.4 Current applications
| MOQT can be layered on top of WebTransport.
WebTransport implementations over QUIC (HTTP/3) are available both for clients and servers:
- Google Chrome and Microsoft Edge browsers implement client-side W3C WebTransport API [33] over QUIC.
- Many open-source server-side implementations exist. Some examples:
- Google... |
c87765bd88910b968f2a46607f719dbf | 26.836 | 4.2.13 Media over QUIC Transport (MOQT)
| |
c87765bd88910b968f2a46607f719dbf | 26.836 | 4.2.13.1 Introduction
| Media over QUIC Transport (MOQT) [18] is a publish/subscribe-based binary data transport protocol that is under development by the IETF Media Over QUIC Working Group [30] since 2023, designed to run either directly over QUIC [9] or via WebTransport [20]. Although the protocol was originally created for media applicatio... |
c87765bd88910b968f2a46607f719dbf | 26.836 | 4.2.13.2 Features
| |
c87765bd88910b968f2a46607f719dbf | 26.836 | 4.2.13.2.1 Introduction
| Below is a non-exhaustive summary of MOQT's key features. For further details, refer to draft-ietf-moq-transport [18].
|
c87765bd88910b968f2a46607f719dbf | 26.836 | 4.2.13.2.2 Object-based data model
| MOQT’s data model represents each MOQT schedulable unit of content as an Object within a named Track, organized into Groups and Subgroups. Objects are identified by an Object ID within a Group/Subgroup and carry metadata including Track Alias, Group ID, Object IDs, Publisher Priority, and optional extension headers.
A... |
c87765bd88910b968f2a46607f719dbf | 26.836 | 4.2.13.2.3 Publish/Subscribe workflow
| MOQT’s publish/subscribe workflow enables publishers to make media Tracks available within designated namespaces, allowing subscribers to select only the namespaces and Tracks they need.
Publishers are endpoints that handle subscriptions by sending requested Objects from the requested Track; the initial publisher of a... |
c87765bd88910b968f2a46607f719dbf | 26.836 | 4.2.13.2.4 Data transport over streams and datagrams
| Objects are transmitted either on QUIC streams (reliable, ordered) as defined in RFC 9000 [9] or as QUIC datagramsDATAGRAM frames (unreliable, unordered) as defined in IETF RFC 9221 [14].
Grouping mutually dependent Objects together in a QUIC stream can provide operational advantages, such as improved prioritization. ... |
c87765bd88910b968f2a46607f719dbf | 26.836 | 4.2.13.2.5 Relay behaviour and scalability
| MOQT Relays support both fan-in and fan-out: they can ingest tracks from multiple publishers (fan-in), acquire Tracks once and serve many subscribers (fan-out), thereby facilitating scalable distribution in a manner analogous to Content Delivery Networks (CDNs). Furthermore, rRelays function as policy enforcement point... |
c87765bd88910b968f2a46607f719dbf | 26.836 | 4.2.13.3 Benefits and limitations
| Benefits:
- Leverage the features of QUIC for real-time media delivery (e.g., multiple streams, prioritization) and provides means for integration to a CDN infrastructure.
- Convergence to a single media delivery protocol suitable from ingest to distribution simplifies workflows for service providers and enables a un... |
c87765bd88910b968f2a46607f719dbf | 26.836 | 4.2.13.4 Related Internet Drafts in the IETF MOQ WG
| The IETF Media Over QUIC Working Group is also developings container formats that specify encapsulation of MOQT data and media streaming formats operating over MOQT that specify media packaging as well as signalling mechanisms for negotiation between MOQT endpoints. These formats include:
- Low Overhead Media Containe... |
c87765bd88910b968f2a46607f719dbf | 26.836 | 4.2.13.5 Current applications
| - Several open-source implementations of the IETF draft exist. A non-exhaustive list is given below:
- Google’s production-ready implementation supports MOQT: https://github.com/google/quiche
- Meta provides an experimental MOQT Relay and live encoder/player designed to work with it:
- Relay: https://github.com/face... |
b385b9083e05269d84c02cc96e437a4d | 26.892 | 1 Scope
| Editor’s Note: To be completed
|
b385b9083e05269d84c02cc96e437a4d | 26.892 | 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.
-... |
b385b9083e05269d84c02cc96e437a4d | 26.892 | 3 Definitions of terms and abbreviations
| |
b385b9083e05269d84c02cc96e437a4d | 26.892 | 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].
|
b385b9083e05269d84c02cc96e437a4d | 26.892 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
|
b385b9083e05269d84c02cc96e437a4d | 26.892 | 3.2 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].
|
b385b9083e05269d84c02cc96e437a4d | 26.892 | 4 Background
| |
b385b9083e05269d84c02cc96e437a4d | 26.892 | 4.1 Existing capabilities in 3GPP
| |
b385b9083e05269d84c02cc96e437a4d | 26.892 | 4.1.1 TS 26.143 SDR messaging capabilities
| SDR images have been used before the rapid adoption of HDR content chains. This was inevitable since HDR images provide viewing experiences that are far enhanced than traditional SDR imaging, and hence HDR still image technologies are already specified by 3GPP TS 26.143 [2]. As a baseline however, 3GPP TS 26.143 [2] su... |
b385b9083e05269d84c02cc96e437a4d | 26.892 | 4.1.2 TS 26.143 HDR messaging capabilities
| 3GPP TS 26.143 [2] supports still image content in HDR High Efficiency Image Format (HEIC), which extends SDR support with High Dynamic Range (HDR) capabilities. HDR images conforming to container formats with either the 'heic' brand [5] or the 'MiHB' brand [6] are supported. The contained elementary bitstream conforms... |
b385b9083e05269d84c02cc96e437a4d | 26.892 | 5 Scenarios
| |
b385b9083e05269d84c02cc96e437a4d | 26.892 | 5.1 Scenario #1: HDR images
| |
b385b9083e05269d84c02cc96e437a4d | 26.892 | 5.1.1 Overview
| |
b385b9083e05269d84c02cc96e437a4d | 26.892 | 5.1.2 Review of existing formats
| |
b385b9083e05269d84c02cc96e437a4d | 26.892 | 5.1.2.1 Android Ultra HDR
| Android uses a format called "Ultra HDR" [13] which makes HDR images work on variety of devices by building on top of the standard JPEG format.
Ultra HDR combines two things into one file [13]:
1. Standard Image: A normal SDR JPEG that any device can show.
2. Gain Map: that tells compatible devices how to b... |
b385b9083e05269d84c02cc96e437a4d | 26.892 | 5.1.2.2 HDR still images (Apple)
| HDR still images [11] in this case are treated as a complete system workflow, i.e. the operating system handles the displaying the image correctly on different screens.
Editor’s Note: to be completed.
|
b385b9083e05269d84c02cc96e437a4d | 26.892 | 5.2 Scenario #2: Live images
| |
b385b9083e05269d84c02cc96e437a4d | 26.892 | 5.2.1 Overview
| This user experience presents as a standard still image in a photo gallery, but it holds a layer that converts a still capture into a short clip. By interacting e.g. pressing on the photo, the user is shown the atmosphere surrounding the shot providing context to a memory that a standard static picture does not provide... |
b385b9083e05269d84c02cc96e437a4d | 26.892 | 5.2.2 Review of existing formats
| |
b385b9083e05269d84c02cc96e437a4d | 26.892 | 5.2.2.1 Google Android motion picture
| |
b385b9083e05269d84c02cc96e437a4d | 26.892 | 5.2.2.1.1 Overview
| The Motion Photo format [16] encapsulates a still image and a video recording into a single file container. This format follows the Motion Photo Format 1.0 specification [16].
|
b385b9083e05269d84c02cc96e437a4d | 26.892 | 5.2.2.1.2 File Structure
| The format uses a primary image container (JPEG, HEIC, or AVIF [16]) to host both media elements:
1. Primary Image: The standard image data appears at the beginning of the file, ensuring backward compatibility with standard image viewers.
2. Embedded Video: An MP4 video stream [17] is appended to the end of t... |
b385b9083e05269d84c02cc96e437a4d | 26.892 | 5.2.2.1.3 Metadata and Presentation
| The format relies on XMP (Extensible Metadata Platform) [18] for definition and playback:
• Container XMP: Specifies the presence and location of the embedded video data within the file structure.
• Behavior: The MicroVideo attribute (value 1) identifies the file as a motion photo. Offset data indicates the b... |
b385b9083e05269d84c02cc96e437a4d | 26.892 | 5.2.2.2 Apple Live Photos
| Editor’s Note: to be completed.
Editor’s Note: Gather resources on source and coded content, content generation.
|
b385b9083e05269d84c02cc96e437a4d | 26.892 | 6 Conclusions and proposed next steps
| |
b385b9083e05269d84c02cc96e437a4d | 26.892 | 6.1 Conclusions for scenario #x.1:
|
Annex A:
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2026-02
SA4#135
S4-260267
-
-
-
Skeleton
0.0.1
2026-02
SA4#135
S4-260397
-
-
-
Implemented S4-260383 HDR Images, S4-260391 Live Images
0.1.0
... |
b385b9083e05269d84c02cc96e437a4d | 26.892 | 5.1 Scenario #x.y:
| |
b385b9083e05269d84c02cc96e437a4d | 26.892 | 5.1.2 Review of previous work
| |
6cd412fc32459ef0c631fbc3fb42466b | 28.570 | 1 Scope
| The present document …
|
6cd412fc32459ef0c631fbc3fb42466b | 28.570 | 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.
-... |
6cd412fc32459ef0c631fbc3fb42466b | 28.570 | 3 Definitions of terms, symbols and abbreviations
| |
6cd412fc32459ef0c631fbc3fb42466b | 28.570 | 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.
|
6cd412fc32459ef0c631fbc3fb42466b | 28.570 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
6cd412fc32459ef0c631fbc3fb42466b | 28.570 | 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>
Annex A (informative):
Change history
Ch... |
f7d81ca94b78c87dd36a4bef3dcaf5b8 | 28.896 | 1 Scope
| The present document …
|
f7d81ca94b78c87dd36a4bef3dcaf5b8 | 28.896 | 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.
-... |
f7d81ca94b78c87dd36a4bef3dcaf5b8 | 28.896 | 3 Definitions of terms, symbols and abbreviations
| |
f7d81ca94b78c87dd36a4bef3dcaf5b8 | 28.896 | 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.
|
f7d81ca94b78c87dd36a4bef3dcaf5b8 | 28.896 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
f7d81ca94b78c87dd36a4bef3dcaf5b8 | 28.896 | 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>
Annex <X> (informative):
Change history
Chan... |
33f63d4585416d30fe17818d1cefee31 | 28.895 | 1 Scope
| The present document …
|
33f63d4585416d30fe17818d1cefee31 | 28.895 | 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.
-... |
33f63d4585416d30fe17818d1cefee31 | 28.895 | 3 Definitions of terms, symbols and abbreviations
| |
33f63d4585416d30fe17818d1cefee31 | 28.895 | 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.
|
33f63d4585416d30fe17818d1cefee31 | 28.895 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
33f63d4585416d30fe17818d1cefee31 | 28.895 | 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>
|
33f63d4585416d30fe17818d1cefee31 | 28.895 | 4 Concepts and background
| Editor's note: this clause will contain concepts and background related to the management of ISAC.
|
33f63d4585416d30fe17818d1cefee31 | 28.895 | 4.1 Reference management architecture for sensing service
| 3GPP management system for 5G-Advanced incorporates Integrated Sensing and Communication (ISAC) to support vertical applications such as UAV tracking and smart transportation. It introduces the Sensing Function (SF)[d], composed of Control (SCF)[d] and Processing (SPF) sub-functions[d], with gNB serving as Sensing Enti... |
33f63d4585416d30fe17818d1cefee31 | 28.895 | 5 Use Cases
| Editor's note: this clause will contain use cases, potential requirements, and potential solutions related to the management of ISAC.
|
33f63d4585416d30fe17818d1cefee31 | 28.895 | 5.1 Use Case#1: Selection of Sensing Entities for sensing services
| |
33f63d4585416d30fe17818d1cefee31 | 28.895 | 5.1.1 Description
| Wireless sensing in a mobile network is a technology enabler to acquire information about characteristics of an environment and/or objects within the environment, that uses radio frequency to determine a distance (range), an angle, or instantaneous linear velocity of objects, etc., [1]
To enable sensing services in a ... |
33f63d4585416d30fe17818d1cefee31 | 28.895 | 5.1.2 Potential requirements
| PREQ-Sensing-Entity-information-1: The 3GPP management system should be able to configure information on Sensing Entities related to support for sensing services.
PREQ-Sensing-Entity-information-2: The 3GPP management system should be able to provide sensing related information on sensing entities to responsible nodes... |
33f63d4585416d30fe17818d1cefee31 | 28.895 | 5.1.3 Potential solutions
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.