hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2.5.5.1 Test description and applicability | The purpose of this test case is to test the partially update registered service API as specified in R1AP [4], clause 6.1.4.4. The expected outcome is successful validation of the response from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2.5.5.2 Test entrance criteria | 1) The test simulator has functionality to initiate the Partially update registered service procedure as defined in R1GAP [1]. 2) A service API registration exists in DUT and the serviceApiId and the apfId are known to test simulator. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 24 3) The schema of the ServiceAPIDescriptionPa... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2.5.5.3 Test methodology | 5.2.5.5.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. 5.2.5.5.3.2 Procedure Step 1 The test simulator as an API Consumer initiates a HTTP request to partially update a registered service API identified by the apfId and the serviceApiId. Step 2 T... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 5.2.5.5.4 Expected result | The test is considered passed if Step 6 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 6 SME Service Discovery service test cases | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 6.1 Conformance test cases for rApp | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 6.1.1 General | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 6.1.1.1 Device under test requirements | The rApp that acts as Device Under Test (DUT) in the test scenarios of this clause can be a function that is under development, or it can be a finalized commercial product. The requirements on the DUT for these tests are that it can handle the SME service discovery service, and the purpose of the test scenarios is to v... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 6.1.1.2 Test simulator capabilities | The test simulator has the capabilities as required for a SMO/Non-RT RIC framework. In addition, it has the following capabilities: • Recording of received HTTP requests and responses and analysing them regarding conformance to the R1 service definitions. • Controlled initiation of procedures with configurable URIs and... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 6.1.2 Discover service API as API Consumer test scenario | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 6.1.2.1 Query service (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 6.1.2.1.1 Test description and applicability | The purpose of this test case is to test the Query service APIs operation as specified in R1AP [4], clause 6.2.4.1. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 6.1.2.1.2 Test entrance criteria | 1) The DUT has functionality to initiate the Discover services procedure. 2) A set of service API registrations exist in the test simulator. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 6.1.2.1.3 Test methodology | 6.1.2.1.3.1 Initial conditions 1) The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. 6.1.2.1.3.2 Procedure Step 1 The DUT as an API Consumer initiates a HTTP request to query service APIs. Step 2 At the test simulator the contents of the received HTTP request are recorded. ... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 6.1.2.1.4 Expected result | The test is considered passed if Step 3 validation has passed. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 26 |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 6.2 Conformance test cases for SMO/Non-RT RIC framework | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 6.2.1 General | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 6.2.1.1 Device under test requirements | The SMO/Non-RT RIC framework that acts as Device Under Test (DUT) in the test scenarios of this clause can be a function that is under development, or it can be a finalized commercial product. The requirements on the DUT for these tests are that it can handle the SME service discovery service, and the purpose of the te... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 6.2.1.2 Test simulator capabilities | The test simulator has the capabilities as specified in clause 4.3.2. In addition, it has the following capabilities: 1) Recording of received HTTP requests and responses and analysing them regarding conformance to the R1 service definitions. 2) Controlled initiation of procedures with configurable URIs and payload for... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 6.2.2 Service discovery API as API Producer test scenario | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 6.2.2.1 Query service (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 6.2.2.1.1 Test description and applicability | The purpose of this test case is to test the Query service APIs as specified in R1AP [4], clause 6.2.4.1. The expected outcome is successful validation of the response from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 6.2.2.1.2 Test entrance criteria | 1) The DUT has functionality to initiate the Discover services procedure. 2) A set of service API registrations exist in the test simulator. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 6.2.2.1.3 Test methodology | 6.2.2.1.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. 6.2.2.1.3.2 Procedure Step 1 The test simulator as an API Consumer initiates a HTTP request to query service APIs that are registered by the apfId. Step 2 The DUT receives the HTTP request. S... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 6.2.2.1.4 Expected result | The test is considered passed if Step 6 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7 SME Service Subscription service test cases | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.1 Conformance test cases for rApp | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.1.1 General | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.1.1.1 Device under test requirements | The rApp that acts as DUT in the test scenarios of this clause can be a function that is under development, or it can be a finalized commercial product. The requirements on the DUT for these tests are that it can handle the SME service subscription service, and the purpose of the test scenarios is to validate that it c... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.1.1.2 Test simulator capabilities | The test simulator has the capabilities as required for a SMO/Non-RT RIC framework. In addition, it has the following capabilities: • Recording of received HTTP requests and responses and analysing them regarding conformance to the R1 service definitions. • Controlled initiation of procedures with configurable URIs and... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.1.2 Service events subscription API as API Consumer test scenario | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.1.2.1 Subscribe service events (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.1.2.1.1 Test description and applicability | The purpose of this test case is to test the Events subscription service API as specified in R1AP [4], clause 6.3.4.1. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.1.2.1.2 Test entrance criteria | The DUT has functionality to initiate the Subscribe service availability procedure as defined in R1GAP [1], clause 5.1.4. NOTE: The DUT provides the events subscription structure as defined in R1AP [4], clause 6.3.3. The service event being subscribed to can be a standard or non-standard R1 service event. ETSI ETSI TS ... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.1.2.1.3 Test methodology | 7.1.2.1.3.1 Initial conditions 1) The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. 2) The subscriberId is known to DUT. 7.1.2.1.3.2 Procedure Step 1 The DUT as an API Consumer initiates a HTTP request to subscribe to service event notifications. Step 2 At the test simulat... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.1.2.1.4 Expected result | The test is considered passed if Step 3 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.1.2.2 Unsubscribe service events (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.1.2.2.1 Test description and applicability | The purpose of this test case is to test the unsubscribe service API as specified in R1AP [4], clause 6.3.4.2. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.1.2.2.2 Test entrance criteria | 1) The DUT has functionality to initiate the Unsubscribe service availability procedure as defined in R1GAP [1], clause 5.1.4. 2) A subscription exists and the subscriberId and subscriptionId are known to the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.1.2.2.3 Test methodology | 7.1.2.2.3.1 Initial conditions The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. 7.1.2.2.3.2 Procedure Step 1 The DUT as an API Consumer initiates a HTTP request to unsubscribe from service event notifications identified by the subscriberId and subscriptionId. Step 2 At th... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.1.2.2.4 Expected result | The test is considered passed if Step 3 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.2 Conformance test cases for SMO/Non-RT RIC framework | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.2.1 General | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.2.1.1 Device under test requirements | The SMO/Non-RT RIC framework that acts as DUT in the test scenarios of this clause can be a product that is under development, or it can be a finalized commercial product. The requirements on the DUT for these tests are that it can handle the SME service events subscription service, and the purpose of the test scenario... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.2.1.2 Test simulator capabilities | The test simulator has the capabilities as specified in clause 4.3.2. In addition, it has the following capabilities: 1) Recording of received HTTP requests and responses and analysing them regarding conformance to the R1 service definitions. 2) Controlled initiation of procedures with configurable URIs and payload for... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.2.2 Service events subscription API as API Producer test scenario | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.2.2.1 Service events subscription (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.2.2.1.1 Test description and applicability | The purpose of this test case is to test the Events subscription service API as specified in R1AP [4], clause 6.3.4.1. The expected outcome is successful validation of the response from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.2.2.1.2 Test entrance criteria | The test simulator has functionality to initiate the Subscribe service availability procedure as defined in R1GAP [1], clause 5.1.4. NOTE: The test simulator provides the events subscription structure as defined in R1AP [4], clause 6.3.3. The service being subscribed to can be a standard or non-standard R1 service. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.2.2.1.3 Test methodology | 7.2.2.1.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 30 7.2.2.1.3.2 Procedure Step 1 The test simulator as an API Consumer initiates a HTTP request to subscribe to service event notifications. Step 2 The DU... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.2.2.1.4 Expected result | The test is considered passed if Step 7 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.2.2.2 Unsubscribe service events (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.2.2.2.1 Test description and applicability | The purpose of this test case is to test the Unsubscribe service API as specified in R1AP [4], clause 6.3.4.2. The expected outcome is successful validation of the response from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.2.2.2.2 Test entrance criteria | 1) The test simulator has functionality to initiate the Unsubscribe service availability procedure as defined in R1GAP [1], clause 5.1.4. 2) A subscription exists and the subscriberId and subscriptionId are known to the test simulator. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.2.2.2.3 Test methodology | 7.2.2.2.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. 7.2.2.2.3.2 Procedure Step 1 The test simulator as an API Consumer initiates a HTTP request to unsubscribe from service event notifications identified by the subscriberId and subscriptionId. S... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.2.2.2.4 Expected result | The test is considered passed if Step 6 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.2.2.3 Notification service (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.2.2.3.1 Test description and applicability | The purpose of this test case is to test the notification service API as specified in R1AP [4], clause 6.3.4.3. The expected outcome is successful validation of the event notification from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.2.2.3.2 Test entrance criteria | 1) The DUT has functionality to initiate the Notify service availability changes procedure as defined in R1GAP [1], clause 5.1.4. 2) A subscription exists in the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.2.2.3.3 Test methodology | 7.2.2.3.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. 7.2.2.3.3.2 Procedure Step 1 The DUT as an API producer initiates the sending of a HTTP POST request. Step 2 At the test simulator the contents of the received HTTP request are recorded. Step ... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 7.2.2.3.4 Expected result | The test is considered passed if Step 3 validation has passed. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 32 |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8 DME Data registration service test cases | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.1 Conformance test cases for rApp | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.1.1 General | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.1.1.1 Device under test requirements | The rApp that acts as DUT in the test scenarios of this clause can be a function that is under development, or it can be a finalized commercial product. The requirements on the DUT for these tests are that it can handle the Data registration service, and the purpose of the test scenarios is to validate that it conforms... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.1.1.2 Test simulator capabilities | The test simulator has the capabilities as required for a SMO/Non-RT RIC framework. In addition, it has the following capabilities: • Recording of received HTTP requests and responses and analysing them regarding conformance to the R1 service definitions. • Controlled initiation of procedures with configurable URIs and... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.1.2 Data registration API as API consumer test scenario | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.1.2.1 Register DME type (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.1.2.1.1 Test description and applicability | The purpose of this test case is to test the Register DME type in Data registration API as specified in R1AP [4], clause 7.1. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.1.2.1.2 Test entrance criteria | The DUT has functionality to initiate the Register DME type procedure as defined in R1GAP [1]. NOTE: The DUT provides the service API description as defined in R1AP [4]. The service being registered can be a standard or non-standard R1 service. 8.1.2.1.3 Test methodology 8.1.2.1.3.1 Initial conditions The test simulato... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.1.2.1.4 Expected result | The test is considered passed if Step 3 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.1.2.2 Deregister DME type (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.1.2.2.1 Test description and applicability | The purpose of this test case is to test the Deregister DME type in Data registration API as specified in R1AP [4], clause 7.1. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.1.2.2.2 Test entrance criteria | 1) The DUT has functionality to initiate the Deregister DME type procedure as defined in R1GAP [1], clause 5.2.2.2. 2) A DME type exists in test simulator and the registrationId is known to the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.1.2.2.3 Test methodology | 8.1.2.2.3.1 Initial conditions The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. 8.1.2.2.3.2 Procedure Step 1 The DUT as an API Consumer initiates a HTTP request to Deregister DME type. Step 2 At the test simulator the contents of the received HTTP request are recorded. St... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.1.2.2.4 Expected result | The test is considered passed if Step 3 validation has passed. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 34 |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.1.2.3 Query DME type (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.1.2.3.1 Test description and applicability | The purpose of this test case is to test the Query DME type in Data registration API as specified in R1AP [4], clause 7.1.4.4. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.1.2.3.2 Test entrance criteria | 1) The DUT has functionality to initiate the query DME type registration procedure as defined in R1GAP [1], clause 5.2.2.2. 2) A DME type exists in test simulator and the registrationId is known to the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.1.2.3.3 Test methodology | 8.1.2.3.3.1 Initial conditions The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. 8.1.2.3.3.2 Procedure Step 1 The DUT as an API Consumer initiates a HTTP request to query a DME type. Step 2 At the test simulator the contents of the received HTTP request are recorded. Step ... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.1.2.3.4 Expected result | The test is considered passed if Step 3 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.1.2.4 Update DME type (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.1.2.4.1 Test description and applicability | The purpose of this test case is to test the Update DME type in Data registration API as specified in R1AP [4], clause 7.1.4.3. The expected outcome is successful validation of the request from the DUT. 8.1.2.4.2 Test entrance criteria 1) The DUT has functionality to initiate the Update DME type registration procedure ... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.1.2.4.3 Test methodology | 8.1.2.4.3.1 Initial conditions The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. 8.1.2.4.3.2 Procedure Step 1 The DUT as an API Consumer initiates a HTTP request to update a DME type identified by the registrationId and DmeTypeRelatedCapabilities. Step 2 At the test simula... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.1.2.4.4 Expected result | The test is considered passed if Step 3 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2 Conformance test cases for SMO/Non-RT RIC framework | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.1 General | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.1.1 Device under test requirements | The SMO/Non-RT RIC framework that acts as DUT in the test scenarios of this clause can be a function that is under development, or it can be a finalized commercial product. The requirements on the DUT for these tests are that it can handle the Data registration service, and the purpose of the test scenarios is to valid... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.1.2 Test simulator capabilities | The test simulator has the capabilities as required for a rApp. In addition, it has the following capabilities: • Recording of received HTTP requests and responses and analysing them regarding conformance to the R1 service definitions. • Controlled initiation of procedures with configurable URIs and payload formulated ... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2 Data registration API as API Producer test scenario | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.1 Register DME type (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.1.1 Test description and applicability | The purpose of this test case is to test the Register DME type in Data registration API as specified in R1AP [4], clause 7.1. The expected outcome is successful validation of the request from the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.1.2 Test entrance criteria | The test simulator has functionality to initiate the Register DME type procedure as defined in R1GAP [1]. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.1.3 Test methodology | 8.2.2.1.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. 8.2.2.1.3.2 Procedure Step 1 The test simulator as an API Consumer initiates a HTTP request to register a DmeTypeRelatedCapabilities. Step 2 The DUT receives the HTTP request. Step 3 The DUT ... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.1.4 Expected result | The test is considered passed if Step 7 validation has passed. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.2 Deregister DME type (positive case) | |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.2.1 Test description and applicability | The purpose of this test case is to test the Deregister DME type in Data registration API as specified in R1AP [4]. The expected outcome is successful validation of the request from the DUT. ETSI ETSI TS 104 229 V3.0.0 (2026-02) 37 |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.2.2 Test entrance criteria | 1) The test simulator has functionality to initiate the Deregister DME type procedure as defined in R1GAP [1], clause 5.2.2.2. 2) A DME type exists in test simulator and the registrationId is known to the DUT. |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.2.3 Test methodology | 8.2.2.2.3.1 Initial conditions The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. 8.2.2.2.3.2 Procedure Step 1 The test simulator as an API Consumer initiates a HTTP request to Deregister DME type. Step 2 The DUT receives the HTTP request. Step 3 The DUT does the following... |
2e6894662525cba6f1eb97c4ec9e419d | 104 229 | 8.2.2.2.4 Expected result | The test is considered passed if Step 6 validation has passed. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.