hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 5.2.1 Overview and example for search | REQ-DIP-5.2.1-01: The DIP shall provide the search query, which allows to search for catalogued attribute-related metadata in the semantic repository, optionally filtered by specific metadata. REQ-DIP-5.2.1-02: The search request shall be implemented as HTTP GET request according to clause 9.3.1 of IETF RFC 9110 [15]. ... |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 5.2.2 Input parameters for search | REQ-DIP-5.2.2-01: The search query shall contain the parameter assetType, which represents the type of the catalogued asset to search for. REQ-DIP-5.2.2-02: Within the scope of the present document, the value of assetType shall be fixed to the value "attribute". ETSI ETSI TS 119 478 V1.1.1 (2026-01) 19 REQ-DIP-5.2.2-03... |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 5.2.3 Output parameters for search | REQ-DIP-5.2.3-01: The output of the search query shall be an attributes object. REQ-DIP-5.2.3-02: An attributes object shall contain an array of attribute objects, which contain attribute-related metadata. REQ-DIP-5.2.3-03: Each attribute object shall contain a specific attributeIdentifier element. • REQ-DIP-5.2.3-03-0... |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 5.3 Find Data Services for Attributes (retrieve) | |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 5.3.1 Overview and example for retrieve | REQ-DIP-5.3.1-01: The DIP shall provide the retrieve query, which allows to lookup data services in the DSD for the verification or retrieval of attributes within a given Member State. REQ-DIP-5.3.1-02: The retrieve request shall be implemented as HTTP GET request according to clause 9.3.1 of IETF RFC 9110 [15]. EXAMPL... |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 5.3.2 Input parameters for retrieve | REQ-DIP-5.3.2-01: The retrieve query shall have as input parameters the following two parameters: queryType and attributeIdentifier. • REQ-DIP-5.3.2-01-01: The queryType element shall specify the type of the query and shall in the scope of the present document be equal to the fixed value "dataServices". • REQ-DIP-5.3.2... |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 5.3.3 Output parameters for retrieve | REQ-DIP-5.3.3-01: The output of the retrieve query shall be a dataServices object. REQ-DIP-5.3.3-02: The dataServices object shall contain an array of dataService elements, which shall contain data service-related metadata as specified in the following. REQ-DIP-5.3.3-03: The dataService object shall contain the followi... |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 5.4 Use of HTTP and response format selection | REQ-DIP-5.4-01: The DIP shall support query requests using the HTTP GET method as defined in clause 9.3.1 of IETF RFC 9110 [15]. REQ-DIP-5.4-02: The DIP shall support the Accept header according to clause 12.5.1 of IETF RFC 9110 [15] to allow that clients specify their preferences regarding the response media type. REQ... |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 6 Authentic Source Interface | |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 6.1 Authentic Source Interface based on HTTP / OAuth | |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 6.1.1 I2 (Verify) | |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 6.1.1.1 Verify Request | REQ-ASIP-6.1.1.1-01: The (I2) Verify interface based on HTTP / OAuth shall use the HTTP POST method as defined in clause 9.3.3 of IETF RFC 9110 [15], as described in the following and specified in the OpenAPI specification in Annex B. ETSI ETSI TS 119 478 V1.1.1 (2026-01) 25 REQ-ASIP-6.1.1.1-02: The POST /verify shall ... |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 6.1.1.2 Verify Response | REQ-ASIP-6.1.1.2-01: The ASIP shall return the result of a /verify call in a verifyResponse object, which structure shall be as specified in this clause. REQ-ASIP-6.1.1.2-02: The verifyResponse object may contain an attributeVerificationResults element. • REQ-ASIP-6.1.1.2-02-01 [CONDITIONAL]: If present, the attributeV... |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 6.1.2 I3 (Retrieve) | |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 6.1.2.1 Retrieve Request | REQ-ASIP-6.1.2.1-01: The (I3) Retrieve interface based on HTTP / OAuth shall use the HTTP POST method as defined in clause 9.3.3 of IETF RFC 9110 [15], as described in the following and specified in the OpenAPI specification in Annex B. REQ-ASIP-6.1.2.1-02: The POST /retrieve shall contain a retrieveRequest object, whi... |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 6.1.2.2 Retrieve Response | REQ-ASIP-6.1.2.2-01: The ASIP shall return the result of a /retrieve call in a retrieveResponse object, which shall be structured as specified in this clause. REQ-ASIP-6.1.2.2-02 [CONDITONAL]: If the retrieve request was successful, the retrieveResponse object shall contain an attributes property. • REQ-ASIP-6.1.2.2-02... |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 6.1.3 I4 (Authorize) | |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 6.1.3.1 Overview and general requirements | REQ-AZSP-6.1.3.1-01: The authorization of requests for verification and retrieval in the HTTP based authentic source interface according to IETF RFC 9110 [15], as specified in clauses 6.1.1 and 6.1.2 above, shall be realized with the OAuth 2.0 based authorization framework according to IETF RFC 6749 [6] using the autho... |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 6.1.3.2 Dynamic Client Registration (IETF RFC 7591) | REQ-AZSP-6.1.3.2-01: The authorization server shall support dynamic client registration with a sealed software statement according to clause 3.1.1 of IETF RFC 7591 [10]. REQ-TSP-6.1.3.2-01: The (qualified) trust service provider shall use an X.509 based certificate according to IETF RFC 5280 [5], which supports the cre... |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 6.1.3.3 Authorization Code Flow (IETF RFC 6749) | The overall process for the issuance of an electronic attestation using the authorization code flow according to clause 4.1 of IETF RFC 6749 [6] is depicted in the informative Figure 3 below. ETSI ETSI TS 119 478 V1.1.1 (2026-01) 32 Figure 3: Overall process with authorization code flow using IETF RFC 6749 [6] (informa... |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 6.1.3.4 Security considerations for the Authorization Server | REQ-AZSP-6.1.3.4-01: The authorization server shall take into account the security considerations related to OAuth 2.0 from IETF RFC 6819 [7], IETF RFC 7636 [11], IETF RFC 9700 [19] and the FAPI 2.0 Security Profile [28]. REQ-AZSP-6.1.3.4-02: The authorization server shall be operated in a trustworthy environment, whic... |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 6.2 Authentic Source Interface based on ISO 15000 | |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 6.2.1 Overview | The following clauses specify the general protocol binding for the authentic source interface in clause 6.2.2, which is based on the relevant parts of the ISO 15000 standard, which includes ISO 15000-2 [23] and ISO 15000-3 [24]. REQ-ASIP-6.2.1-01: The (I2) Verify interface based on ISO 15000 shall be as specified in cl... |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 6.2.2 Protocol Binding | REQ-ASIP-6.2.2-01: All messages in the authentic source interface based on ISO 15000 shall be exchanged using the OASIS ebXML Messaging Protocol Binding for RegRep Version 1.0 [26], which defines the use of ISO 15000-2 [23] as message exchange protocol for ISO 15000-3 [24] (RegRep) exchanges. REQ-ASIP-6.2.2-02: For int... |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 6.2.3 I2 (Verify) | |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 6.2.3.1 Verify Request | REQ-ASIP-6.2.3.1-01: The verification request shall be an XML document rooted in query:QueryRequest. • REQ-ASIP-6.2.3.1-01-01: The query:QueryRequest shall have an attribute named id with a UUID value according to [18]. • REQ-ASIP-6.2.3.1-01-02: The query:QueryRequest shall have the following six named rim:Slot child e... |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 6.2.3.2 Verify Response | |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 6.2.3.2.1 Successful Verify Response | REQ-ASIP-6.2.3.2.1-01: The successful verification response providing an immediate result shall be an XML document rooted in a query:QueryResponse element with status set to the value urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Success. REQ-ASIP-6.2.3.2.1-02: The XML document shall have an attribute named reques... |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 6.2.3.2.2 Failure Error Response | REQ-ASIP-6.2.3.2.2-01: The failure error response shall be an XML document rooted in query:QueryResponse where the status attribute shall be set to urn:oasis:names:tc:ebxml- regrep:ResponseStatusType:Failure. REQ-ASIP-6.2.3.2.2-02: The XML document shall have an attribute named requestId, which shall be set to the valu... |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 6.2.3.2.3 Deferred Response | REQ-ASIP-6.2.3.2.3-01 [CONDITIONAL]: If the outcome of processing of the verification request is not immediately available, a rim:QueryResponse shall be returned with a value urn:oasis:names:tc:ebxml- regrep:ResponseStatusType:Unavailable for the status attribute instead of urn:oasis:names:tc:ebxml-regrep:ResponseStatu... |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 6.2.4 I3 (Retrieve) | |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 6.2.4.1 Overview | The I3 (Retrieve) protocol is a variant of the I2 (Verify) protocol specified in clause 6.2.3 above. REQ-ASIP-6.2.4.1-01: The specification defined in clause 6.2.3 shall apply, except where specified in the following clauses. NOTE: Clause 6.2.4.2 specifies the Retrieve Request and clause 6.2.4.3 specifies the Retrieve ... |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 6.2.4.2 Retrieve Request | REQ-ASIP-6.2.4.2-01: The verification request shall be an XML document rooted in query:QueryRequest and shall have an attribute named id with a UUID value in the URN Namespace [18]. • REQ-ASIP-6.2.4.2-01-01: The verification request shall have the same six named rim:Slot child elements as the Verify Request as specifie... |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 6.2.4.3 Retrieve Response | |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 6.2.4.3.1 Successful Retrieve Response | REQ-ASIP-6.2.4.3.1-01: The successful retrieve response providing an immediate result shall be an XML document rooted in a query:QueryResponse element with status set to the value urn:oasis:names:tc:ebxml- regrep:ResponseStatusType:Success and shall have an attribute named requestId set to the value of the id attribute... |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 6.2.4.3.2 Failure Error Response | REQ-ASIP-6.2.4.3.2-01: The failure error response shall follow the specification for verify failure error response, as specified above in clause 6.2.3.2.2. |
2c9a44e5be53958d48a58da224ac0b39 | 119 478 | 6.2.4.3.3 Deferred Response | REQ-ASIP-6.2.4.3.3-01: The deferred error response shall follow the specification for verify deferred response, as specified above in clause 6.2.3.2.3. ETSI ETSI TS 119 478 V1.1.1 (2026-01) 45 Annex A (normative): OpenAPI Specification for Discover Interface REQ-DIP-A-01: The DIP shall provide the Discover Interface as... |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 1 Scope | The present document specifies the Application Protocols for R1 Services. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 2 References | |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 3 Definition of terms, symbols and abbreviations | |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 3.1 Terms | For the purposes of the present document, the following terms apply: API Consumer: Service Consumer consuming one or more services using APIs NOTE: The Service Consumer role is introduced in R1GAP [5]. API Producer: Service Producer that offers its services for consumption via APIs NOTE: The Service Producer role is in... |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 3.2 Symbols | Void. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AEF API Expsoing Function AI Artificial Intelligence AI/ML Artificial Intelligence/Machine Learning AIML Artificial Intelligence/Machine Learning AP Application Protocol APF API Producing Function API Application Programming Interface ETSI ETS... |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 4 Application protocol for the R1 services | |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 4.1 Introduction | The present document contains a realization for the procedures identified in R1GAP [5]. It is based on transport protocols as defined in R1TP [7]. This definition of the R1 Application Protocols (R1AP) defined in the present document is based on the 3GPP service framework for network functions specified in ETSI TS 129 ... |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 4.2 Version conventions for the present document | The version number of the present document follows the "xx.yy" versioning scheme. There could be implications for the interoperability between rApps and R1 service API implementations in SMO/Non-RT RIC framework that are based on different versions of the present document. An incremented "xx" version field of the prese... |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 5 RESTful R1 service APIs | |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 5.1 Overview | The design of the RESTful R1 service APIs is based on the procedures and requirements defined in R1UCR [6] and R1GAP [5], and on the protocol design framework as specified in ETSI TS 129 501 [1]. The API version of a service API includes a pre-release version (e.g. "-alpha.1") if the service API is under development. T... |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 5.2 Versioning of RESTful R1 service APIs | Each RESTful R1 service API is versioned independently. The API version number defined in the present document contains three numerical fields following a MAJOR.MINOR.PATCH pattern, and may contain a pre-release version field, according to SemVer [11]. The API version number held by an implementation may additionally i... |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 5.3 URI structure and supported content formats | This clause specifies the URI prefix and the supported content formats applicable to the RESTful R1 service APIs. All resource URIs of the APIs shall have the following prefix: {apiRoot}/<apiName>/<apiVersion>/ The request URIs used in HTTP requests from the API Consumer towards the API Producer shall have the resource... |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 5.4 General considerations for RESTful R1 service APIs | |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 5.4.1 Usage of HTTP header fields | HTTP headers are components of the headers section of the HTTP request and response messages. The usage of HTTP header fields shall follow the definitions in ETSI GS NFV-SOL 013 [4], clause 4.2. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 5.4.2 Handling of large query results | The handling of large query results shall be supported by RESTful R1 service APIs as specified in ETSI GS NFV-SOL 013 [4], clause 5.4.2. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 5.4.3 Error reporting | In RESTful interfaces, application errors are mapped to HTTP errors. Since HTTP error information is generally not enough to discover the root cause of the error, additional application specific error information is typically delivered in the message content based on the ProblemDetails data type. HTTP error responses s... |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6 Service management and exposure services | |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1 Service registration API | |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.1 Introduction | This API allows the API Consumer to manage registrations of service APIs based on the procedures for "Registration of services" defined in R1GAP [5]. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.2 API version | For the service registration API as specified in the present document, the MAJOR version field shall be 1, the MINOR version field shall be 2 and the PATCH version field shall be 0 (see ETSI TS 129 501 [1] for a definition of the version fields). Consequently, the <apiVersion> URI path segment shall be set to "v1". |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.3 Resource structure and methods | The request URIs used in HTTP requests from the API Consumer towards the API Producer shall have the resource URI structure as defined for the CAPIF_Publish_Service_API (see ETSI TS 129 222 [9], Figure 8.2.2.1-1 in clause 8.2.2). Table 6.1.3-1 lists the individual resources defined for the API, the applicable HTTP meth... |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.4 Service Operations | |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.4.1 Register service API | |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.4.1.1 Operation definition | A Service Producer uses the Register service API operation as API Consumer to register with the API Producer service APIs for services it is capable of producing. The operation is based on HTTP POST. ETSI ETSI TS 104 231 V8.0.0 (2026-03) 25 Figure 6.1.4.1.1-1: Register service API operation The service operation is as ... |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.4.1.2 Referenced procedures | 6.1.4.1.2.1 Register service procedure The Register service API operation illustrated in Figure 6.1.4.1.1-1 is based on the Register service procedure defined in R1GAP [5]. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.4.2 Update registered service API | |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.4.2.1 Operation definition | A Service Producer uses the Update registered service API operation as API Consumer to update a complete service API registration with the API Producer. The operation is based on HTTP PUT. Figure 6.1.4.2.1-1: Update registered service API operation The service operation is as follows: 1) The API Consumer shall send an ... |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.4.2.2 Referenced procedures | 6.1.4.2.2.1 Update service registration procedure The Update registered service API operation illustrated in Figure 6.1.4.2.1-1 is based on the Update service registration procedure defined in R1GAP [5]. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.4.3 Deregister service API | |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.4.3.1 Operation definition | A Service Producer uses the Deregister service API operation as API Consumer to deregister a service with the API Producer. The operation is based on HTTP DELETE. Figure 6.1.4.3.1-1: Deregister service API operation The service operation is as follows: 1) To deregister a service, The API Consumer shall send an HTTP DEL... |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.4.3.2 Referenced procedures | 6.1.4.3.2.1 Deregister service procedure The Deregister service API operation illustrated in Figure 6.1.4.3.1-1 is based on the Deregister service procedure defined in R1GAP [5]. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.4.4 Partially update registered service API | |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.4.4.1 Operation definition | A Service Producer uses the Partially update registered service API operation as API Consumer to partially update a service API registration with the API Producer. The operation is based on HTTP PATCH. ETSI ETSI TS 104 231 V8.0.0 (2026-03) 27 Figure 6.1.4.4.1-1: Partial update registered service API operation The servi... |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.4.4.2 Referenced procedures | 6.1.4.4.2.1 Update service registration procedure The Update registered service API operation illustrated in Figure 6.1.4.2.1-1 is based on the Update service registration procedure defined in R1GAP [5]. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.4.5 Query service APIs | |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.4.5.1 Operation definition | The API Consumer uses the Query service APIs operation to retrieve the service API descriptions that are registered with the API Producer. The operation is based on HTTP GET. Figure 6.1.4.5.1-1: Query service API operation The service operation is as follows: 1) The API Consumer shall send an HTTP GET request to the AP... |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.4.5.2 Referenced procedures | 6.1.4.5.2.1 Query register service procedure The Query service APIs operation illustrated in Figure 6.1.4.5.1-1 is based on the query registered service procedure defined in R1GAP [5]. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.5 Resources | |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.5.1 Overview | This clause defines the resources for the service registration API based on ETSI TS 129 222 [9]. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.5.2 Resource: "APF published APIs" | |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.5.2.0 Description | This resource is defined in ETSI TS 129 222 [9], clause 8.2 with the following URI: {apiRoot}/published-apis/<apiVersion>/{apfId}/service-apis By consuming this API, an rApp takes the role of the APF (API publishing function). In addition to the provisions in ETSI TS 129 222 [9], clause 8.1, the following shall apply: ... |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.5.2.1 Resource Standard Methods | 6.1.5.2.1.1 POST This method shall support the URI query parameters, request data, response data structures and response codes specified in ETSI TS 129 222 [9], clause 8.2.2.2.3.1. 6.1.5.2.1.2 GET This method shall support the URI query parameters, request data structures, response data structures, and response codes s... |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.5.2.2 Resource Custom Operations | None. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.5.3 Resource: "Individual APF published API" | |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.5.3.0 Description | This resource is defined in ETSI TS 129 222 [9], clause 8.2.2.3 with the following URI: {apiRoot}/published-apis/<apiVersion>/{apfId}/service-apis/{serviceApiId} By consuming this API, an rApp takes the role of the APF (API publishing function). In addition to the provisions in ETSI TS 129 222 [9], clause 8.2, the foll... |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.5.3.1 Resource Standard Methods | 6.1.5.3.1.1 PUT This method shall support the URI query parameters, request data structures, response data structures and response codes specified in ETSI TS 129 222 [9], clause 8.2.2.3.3.2. 6.1.5.3.1.2 DELETE This method shall support the URI query parameters, request data, response data structures and response codes ... |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.5.3.2 Resource Custom Operations | None. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.6 Custom operations without associated resources | None. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.7 Notifications | None |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.8 Data model | |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.8.1 General | The application data model is defined in ETSI TS 129 222 [9], clause 8.2.4. In additions, the adaptations specified in clause B.3 apply to this API. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.8.2 Structured data types | None. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.8.3 Simple data types and enumerations | None. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.8.4 Re-used data types | The re-used data types are defined in clause B.3. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.8.5 Service-specific registration information | None. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.9 Error Handling | |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.9.1 General | HTTP error handling is applicable for this API as specified in ETSI TS 129 222 [9], clause 7.7. ETSI ETSI TS 104 231 V8.0.0 (2026-03) 30 |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.9.2 Protocol Errors | Protocol error handling shall be supported as specified in ETSI TS 129 222 [9], clause 8.1.5.2. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.1.9.3 Application Errors | Application error handling shall be supported as specified in ETSI TS 129 222 [9], clause 8.2.5.3. |
662b7254f1dd44e3e532d423d3335866 | 104 231 | 6.2 Service discovery API |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.