hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.8.3 Service flows | Automatic initiation of Emergency Voice Communication
Upon activation of the railway emergency alert, the FRMCS System automatically initiates voice communication.
FRMCS Users that are part of an active railway emergency alert shall be included in the voice communication.
The railway emergency voice communication does ... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.8.4 Post-conditions | The railway emergency voice communication is active. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.8.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.4.8-001]
Following a railway emergency alert the FRMCS System shall be able to automatically initiate a railway emergency voice communication.
A
22.280
R-5.6.2.4.1-013
[R-6.4.8-002]
The railway emergency voice communication does n... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.9 Use case: Termination of railway emergency voice communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.9.1 Description | Based on operational rules, the configuration determines whether a FRMCS user within an ongoing railway emergency alert can put on hold, leave, or join an ongoing railway emergency voice communication.
During a railway emergency alert, only entitled Controllers are able to terminate the railway emergency voice communic... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.9.2 Pre-conditions | The railway emergency voice communication is ongoing. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.9.3 Service flows | In the case a FRMCS
user no longer meets the conditions of the railway emergency alert and if there is an ongoing railway emergency voice communication, the FRMCS user will remain in the ongoing railway emergency voice communication.
On hold
Based on configuration, a FRMCS user is able to put the railway emergency voic... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.9.4 Post-conditions | A FRMCS user has left or joined the railway emergency voice communication, or the railway emergency voice communication is terminated. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.9.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.4.9-001]
In the case a FRMCS User no longer meets the conditions of railway emergency voice communication, the FRMCS system shall remove the FRMCS user from the ongoing railway emergency voice communication.
A
22.280
R-5.3-XXX
R-5... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.10 Use case: Initiation of Data communication during railway emergency alert | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.10.1 Description | Based on operational rules, additional information about the emergency can be exchanged using data communication. A system or a FRMCS User is able to send the additional information (e.g. text, voice prompts). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.10.2 Pre-conditions | The railway emergency alert is active. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.10.3 Service flows | A FRMCS User, Controller or an External System is able to send additional information (e.g. text, voice prompts).
All the FRMCS Users shall receive the additional information.
The existence of data communications and the read/unread status are indicated to all FRMCS users involved in the related Railway emergency alert... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.10.4 Post-conditions | Data communication is initiated. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.10.5 Potential requirements and gap analysis | Independently on any actions between the user and the end user device, the additional information provided by data communication is presented to the user.
The user shall be able to send additional information by data communication using simple user actions e.g. by selecting predefined messages.
Reference Number
Require... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.11 Use case: Service interworking and service continuation with GSM-R | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.11.1 Description | For migration purposes, the service interworking and service continuation between the GSM-R system and FRMCS System for railway emergency alerts and railway emergency voice communication needs to be defined.
Service interworking between FRMCS and GSM-R shall not require any changes in the GSM-R system specifications.
D... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.11.2 Pre-conditions | None. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.11.3 Service flows | Mobile FRMCS User attached to GSM-R
When the mobile FRMCS User is attached to the GSM-R system and is initiating a Railway Emergency Call, the GSM-R system, (in parallel to processing the railway emergency call internally according to GSM-R definitions), routes the Railway Emergency Call to the FRMCS System, which requ... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.11.4 Post-conditions | None. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.11.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.4.11-001]
The FRMCS System shall provide the necessary means to allow FRMCS Users to be reachable from a legacy GSM-R system. Interworking between FRMCS and GSM-R should not require any changes on GSM-R network side
A/T
22.179
Cov... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.12 Use case: Interface to train borne recorder | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.12.1 Description | The FRMCS Equipment shall provide information about railway emergency communication to the train borne recorder or other equipment via a dedicated interface. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.12.2 Pre-conditions | The FRMCS Equipment is switched on. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.12.3 Service flows | The following events on the FRMCS Equipment related to the railway emergency communication is provided to the train borne recorder:
- Initiation of the railway emergency alert
- Reception of the railway emergency alert
- Leaving of the railway emergency alert
- Termination of the railway emergency alert
- Initiation of... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.12.4 Post-conditions | User actions related to the railway emergency communication have been provided to the train borne recorder. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.4.12.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.4.12-001]
FRMCS Equipment shall provide a dedicated interface for train borne recording purposes
A
N/A
Interface for train borne recorder is outside scope of 3GPP.
[R-6.4.12-002]
FRMCS Equipment shall provide following information... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.5 Use case: Automatic Train Protection (ATP) support by the FRMCS System | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.5.1 Description | For Automatic Train Protection (ATP) the train transmits its information (such as current location, current speed, etc.) to a radio block centre (RBC). As soon as a connection has been established between a train, a radio block centre and a train centre, the train sends its position and speed information periodically. ... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.5.2 Pre-conditions | It is assumed the current position of the train and its speed is provided by the Location Service as defined in 9.4.
It is assumed that there is a bearer of suitable QoS established between the train the radio block centre and the train control centre. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.5.3 Service flows | Via the bearer of suitable QoS the train provides its related information, e.g. train number, location, to the RBC. Via this bearer the train can request movement authority from the RBC and the RBC can grant this to the train. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.5.4 Post-conditions | A train Driver controls the speed of the train according to movement authority. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.5.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.5-001]
The FRMCS System shall be able to provide the necessary QoS for a data bearer to be used for the Automatic Train Protection (ATP) used for e.g. movement authority messages or emergency brake messages.
A/T
TS 22.282
(MCData)... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.6 Trackside Maintenance Warning System communication related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.6.1 Introduction | Generally, trackside maintenance occur during daily train operation. For safety reasons trackside maintenance staff need to be informed about approaching trains entering the area of maintenance. Thus, the intention of a trackside warning system is to inform trackside staff about the approaching train.
Trackside warning... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.6.2 Use case: Initiation of a trackside maintenance warning system communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.6.2.1 Description | The FRMCS User (sensors of the warning system entity) shall be able to initiate data communication to the FRMCS Equipment of trackside maintenance staff and/or trackside warning indication entities (FRMCS User) in the applicable area/track.
When a train approaches that FRMCS User (FRMCS Equipment of the trackside maint... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.6.2.2 Pre-conditions | The FRMCS Users as part of the warning system and the FRMCS Users as part of the maintenance crew are authorised to initiate the trackside maintenance warning system communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.6.2.3 Service flows | The FRMCS Users (trackside maintenance warning system) and FRMCS User (trackside workers in the applicable area) initiate the trackside maintenance warning system communication to the receiving side.
A secure data communication application is used for the trackside maintenance warming system communication. The communic... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.6.2.4 Post-conditions | The FRMCS Users are part of the (warning system) communication are able to exchange data. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.6.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.6.2-001]
The FRMCS System shall be able to initiate data communication for Trackside Maintenance Warning System to FRMCS Users upon a request from a functional identity entitled to raise such communication.
A
22.282
Covered by R-5... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.6.3 Use case: Termination of a trackside maintenance warning system communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.6.3.1 Description | FRMCS Users are able to terminate data communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.6.3.2 Pre-conditions | The data (trackside maintenance warning system) communication is ongoing. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.6.3.3 Service flows | The FRMCS User terminates the trackside maintenance warning system communication with the receiving trackside worker applications. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.6.3.4 Post-conditions | The data communication has been released disconnected. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.6.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.6.3-001]
The FRMCS System shall be able to terminate the Trackside Maintenance Warning System data communication upon a request received from the functional identity that initiated the Trackside Maintenance Warning System data com... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7 Pushed Real Time Video streaming | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7.1 Introduction | In this chapter the use cases related to real time video streaming are described, the following use cases are identified
• Initiation of a real time video streaming
• Termination of a real time video streaming |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7.2 Description | The video image quality depends on the application needs, e.g. lip reading, pattern detection.
Video based supervision for rail operational purposes requires also the support of Real time video capabilities from the FRMCS System. Multiple recipients are able to use the real time video for different purposes.
The FRMCS ... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7.3 Use case: Initiation of a real time video streaming | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7.3.1 Description | Video is streamed between FRMCS Users or FRMCS Equipment. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7.3.2 Pre-conditions | The streaming FRMCS User or FRMCS Equipment has registered to a functional identity that is authorised to initiate a real time video stream.
Note: Successful registration of a functional identity authorised to stream video implies the FRMCS Equipment is able to support streaming video (e.g. camera available)
The receiv... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7.3.3 Service flows | The initiating FRMCS User requests a real time video streaming to another FRMCS User.
The video streaming requests the QoS class which matches to the application category of VIDEO or CRITICAL VIDEO within the FRMCS System, depending on the application needs.
The video quality requested to the FRMCS System by the FRMCS ... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7.3.4 Post-conditions | Depending on the QoS offered, the FRMCS Application or a FRMCS User decide if video streaming is set up. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.7.3-001]
Depending on the information associated with the functional identity used by the initiator, the FRMCS System shall setup the real time video streaming to one or more FRMCS User(s) identified by functional identities that ... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7.4 Use case: Termination of a real time video communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7.4.1 Description | The FRMCS User is able to terminate a real time video communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7.4.2 Pre-conditions | There is an ongoing real time video data communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7.4.3 Service flows | The FRMCS Applications or FRMCS Users involved terminate the real time video data communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7.4.4 Post-conditions | The real time video data communication is terminated. The FRMCS Application or the FRMCS User is informed about the termination. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.7.4.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.7.4-001]
Upon request from the streaming or receiving FRMCS User, the FRMCS System shall be able to terminate the real time video streaming.
A
TS 22.281
(MCVideo)
This is covered in requirement R-5.2.8-001 clause 5.2.8. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8 Public emergency call related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.1 Introduction | FRMCS Users have to indicate events that endanger public safety or emergency that requires the public safety involvement. For this reason, the FRMCS System is able to route the emergency call based on the current position of the initiating FRMCS User. The initiation of an emergency call has no dependency on the registr... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.2 Use case: Initiation of a public emergency call | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.2.1 Description | If enabled by the FRMCS System, an FRMCS User is able to report an emergency to an officer of the Public Safety Answering Point (PSAP) that will be responsible of bringing assistance or organizing response. The second scenario addresses the call back of a PSAP officer to the originator of the public emergency call whic... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.2.2 Pre-conditions | The underlying transport of the FRMCS System supports emergency calls and the FRMCS System allows FRMCS Users to make use of emergency calls. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.2.3 Service flows | The FRMCS User or a public user initiates the public emergency call voice communication by dialling a public emergency call number.
The voice communication is recorded by the voice recording and access application.
The arbitration is managed by the arbitration application. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.2.4 Post-conditions | The PSAP officer has received the public emergency call. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.8.2-001]
The FRMCS System shall be able to allow or inhibit the processing of public emergency numbers.
A
TS 22.280
TS 22.280 sub-clause 6.16 Requirement [R-6.16-001]
[R-6.8.2-002]
In case public emergency call setup is allowed, t... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.3 Use case: Termination of a public emergency call | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.3.1 Description | Both the initiating user, FRMCS User or a public user, and the PSAP officer shall be able to terminate the public emergency call voice communication.
The PSAP officer shall be able to put on hold the public emergency communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.3.2 Pre-conditions | The public emergency call is ongoing. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.3.3 Service flows | PSAP officer on hold
A PSAP officer shall be able to put the public emergency call on hold.
After the PSAP officer has put the voice communication on hold, the communication remains in the FRMCS System, and the PSAP officer is able to be part of the communication again.
Termination
The FRMCS User or a public user, and/... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.3.4 Post-conditions | The public emergency call voice communication is terminated. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.3.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
No requirements.
Note: Procedures for normal emergency call behaviour applies if a call is allowed to be established. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.4 Use case: Call back the public emergency call initiator | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.4.1 Description | The PSAP officer shall be able to establish the communication towards the FRMCS user or a public user, who previously initiated the public emergency call (e.g. in the case the initial call was dropped). |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.4.2 Pre-conditions | The public emergency call initiator is reachable via FRMCS System or a public network.
The FRMCS System is connected to the Public Safety Answering Point. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.4.3 Service flows | The PSAP officer initiates the voice communication by using the subscriber identity or the device identity of the previous calling user, FRMCS User or a public user, of a public emergency call. The QoS class of the communication is managed by the QoS class application. The voice communication requests the QoS class whi... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.4.4 Post-conditions | The call-back of the public emergency call is ongoing. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.8.4.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
No requirements.
Normal emergency call service behaviour applies if a call is allowed to be established. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.9 Data communication for possession management related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.9.1 Introduction | In this chapter the use cases related to possession management data communication are described, the following use cases are identified:
• Initiation of a possession management data communication
• Termination of a possession management data communication
• Service interworking and service continuation with GSM-R |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.9.2 Use case: Initiation of a possession management data communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.9.2.1 Description | The application supports the processes involved in taking possession of an area of railway infrastructure for engineering purposes (for example for track maintenance). This application is intended to allow track side workers to remotely take control of infrastructure elements to perform safe engineering works on those ... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.9.2.2 Pre-conditions | The initiator (Controller(s), trackside maintenance personnel, ground system) is authorised to initiate the possession management data communication. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.9.2.3 Service flows | The FRMCS Equipment initiates the possession management data communication towards the track possession management system. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.9.2.4 Post-conditions | The communication for possession management has been established.
Application messages can be exchanged between the possession management application and the possession management system. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.9.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.9.2-001]
The FRMCS System shall be able to support the transfer of messages to/from an authorised FRMCS Equipment identity, FRMCS User identity or functional identity with a QoS, priority and setup time as defined in clause 12.10 ... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.10 Recording of communication | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.10.1 Introduction | In this chapter the use cases related to recording and access are described, the following use cases are identified
• Recording |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.10.2 Use case: Recording | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.10.2.1 Description | The FRMCS System is able to provide means to record communication and communication related information for voice, video and data services. The means of recording include FRMCS User identities, functional identities and location information of all involved users.
Which communication is applicable for recording is confi... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.10.2.2 Pre-conditions | A communication is configured to be recorded. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.10.2.3 Service flows | Recording of the communication starts when the particular communication becomes initiated.
The recording stops when the communication is terminated. |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.10.2.4 Post-conditions | The recorded communication is stored and ready for post-analysis |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.10.2.5 Potential requirements and gap analysis | Reference Number
Requirement text
Application / Transport
SA1 spec covering
Comments
[R-6.10.2-001]
The FRMCS System shall provide the means to record communication and communication related information to an external system. That encompasses voice, video and data services.
A
22.280
On-Network: 6.15.4-001 - 010
Off-Net... |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.11 Remote control of engines communication related use cases | |
349ca2cc0adaee1226ea2ffcee1cba56 | 22.989 | 6.11.1 Introduction | In this chapter the use cases related to remote control of engines communication are described, the following use cases are identified
• Initiation of a remote control of engines communication
• Termination of a remote control of engines communication |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.