hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.3.7 Error Handling
| |
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.3.7.1 General
| For the Naf_Training API, HTTP error responses shall be supported as specified in clause 4.8 of 3GPP TS 29.501 [5]. Protocol errors and application errors specified in table 5.2.7.2-1 of 3GPP TS 29.500 [4] shall be supported for an HTTP method if the corresponding HTTP status codes are specified as mandatory for that HTTP method in table 5.2.7.1-1 of 3GPP TS 29.500 [4].
In addition, the requirements in the following clauses are applicable for the Naf_Training API.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.3.7.2 Protocol Errors
| No specific procedures for the Naf_Training service are specified.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.3.7.3 Application Errors
| The application errors defined for the Naf_Training service are listed in Table 6.3.7.3-1.
Table 6.3.7.3-1: Application errors
Application Error
HTTP status code
Description
Applicability
OVERLOAD
403 Forbidden
Indicates the AF is overloaded.
NOTE: Including a "ProblemDetails" data structure with the "cause" attribute in the HTTP response is optional unless explicitly mandated in the service operation clauses.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.3.8 Feature negotiation
| The optional features in table 6.3.8-1 are defined for the Naf_Training API. They shall be negotiated using the extensibility mechanism defined in clause 6.6 of 3GPP TS 29.500 [4].
Table 6.3.8-1: Supported Features
Feature number
Feature Name
Description
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.3.9 Security
| As indicated in 3GPP TS 33.501 [8] and 3GPP TS 29.500 [4], the access to the Naf_Training API may be authorized by means of the OAuth2 protocol (see IETF RFC 6749 [9]), based on local configuration, using the "Client Credentials" authorization grant, where the NRF (see 3GPP TS 29.510 [10]) plays the role of the authorization server.
If OAuth2 is used, an NF Service Consumer, prior to consuming services offered by the Naf_Training API, shall obtain a "token" from the authorization server, by invoking the Access Token Request service, as described in clause 5.4.2.2 of 3GPP TS 29.510 [10].
NOTE: When multiple NRFs are deployed in a network, the NRF used as authorization server is the same NRF that the NF Service Consumer used for discovering the Naf_Training service.
The Naf_Training API defines a single scope "naf-train" for the entire service, and it does not define any additional scopes at resource or operation level.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.3.10 HTTP redirection
| An HTTP request may be redirected to a different AF service instance when using direct or indirect communications (see 3GPP TS 29.500 [4]).
An SCP that reselects a different AF producer instance will return the NF Instance ID of the new AF producer instance in the 3gpp-Sbi-Producer-Id header, as specified in clause 6.10.3.4 of 3GPP TS 29.500 [4].
If an AF redirects a service request to a different AF using an HTTP "307 Temporary Redirect" or "308 Permanent Redirect" status code, the identity of the new AF towards which the service request is redirected shall be indicated in the "3gpp-Sbi-Target-Nf-Id" header of the HTTP "307 Temporary Redirect" or "308 Permanent Redirect" response as specified in clause 6.10.9.1 of 3GPP TS 29.500 [4].
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4 Naf_Inference Service API
| |
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.1 Introduction
| The Naf_Inference service shall use the Naf_Inference API.
The API URI of the Naf_Inference API shall be:
{apiRoot}/<apiName>/<apiVersion>
The request URIs used in HTTP requests from the NF service consumer towards the NF service producer shall have the Resource URI structure defined in clause 4.4.1 of 3GPP TS 29.501 [5], i.e.:
{apiRoot}/<apiName>/<apiVersion>/<apiSpecificResourceUriPart>
with the following components:
- The {apiRoot} shall be set as described in 3GPP TS 29.501 [5].
- The <apiName> shall be "naf-inference".
- The <apiVersion> shall be "v1".
- The <apiSpecificResourceUriPart> shall be set as described in clause 6.4.3.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.2 Usage of HTTP
| |
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.2.1 General
| If the AF is untrusted, support of HTTP/1.1 (IETF RFC 9112 [19], IETF RFC 9110 [20] and IETF RFC 9111[21] over TLS is mandatory and support of HTTP/2 (IETF RFC 9113 [11]) over TLS is recommended. TLS shall be used as specified in clause 12.3 and clause 13.1 of 3GPP TS 33.501 [8].
If the AF is trusted, HTTP/2, IETF RFC 9113 [11], shall be used as specified in clause 5.2 of 3GPP TS 29.500 [4].
HTTP/2, IETF RFC 9113 [11], shall be used as specified in clause 5 of 3GPP TS 29.500 [4].
HTTP/2 shall be transported as specified in clause 5.5 of 3GPP TS 29.500 [4].
The OpenAPI [6] specification of HTTP messages and content bodies for the Naf_Inference API is contained in Annex A.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.2.2 HTTP standard headers
| |
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.2.2.1 General
| See clause 5.2.2 of 3GPP TS 29.500 [4] for the usage of HTTP standard headers.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.2.2.2 Content type
| JSON, IETF RFC 8259 [12], shall be used as content type of the HTTP bodies specified in the present specification as specified in clause 5.4 of 3GPP TS 29.500 [4]. The use of the JSON format shall be signalled by the content type "application/json".
"Problem Details" JSON object shall be used to indicate additional details of the error in a HTTP response body and shall be signalled by the content type "application/problem+json", as defined in IETF RFC 9457 [13].
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.2.3 HTTP custom headers
| The mandatory HTTP custom header fields specified in clause 5.5.3.2 of 3GPP TS 29.500 [4] shall be supported, and the optional HTTP custom header fields specified in clause 5.5.3.3 of 3GPP TS 29.500 [4] may be supported.
In this Release of the specification, no specific custom headers are defined for the Naf_Inference API.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.3 Resources
| |
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.3.1 Overview
| This clause describes the structure for the Resource URIs and the resources and methods used for the service.
Figure 6.4.3.1-1 depicts the resource URIs structure for the Naf_Inference API.
Figure 6.4.3.1-1: Resource URI structure of the Naf_Inference API
Table 6.4.3.1-1 provides an overview of the resources and applicable HTTP methods.
Table 6.4.3.1-1: Resources and methods overview
Resource purpose/name
Resource URI (relative path after API URI)
HTTP method or custom operation
Description (service operation)
Inference Subscriptions
/subscriptions
POST
Creates a new Individual Inference Subscription resource.
Individual Inference Subscription
/subscriptions/{subscriptionId}
PUT
Updates an existing Individual Inference Subscription identified by subresource {subscriptionId}.
PATCH
Modifies an existing Individual Inference Subscription identified by subresource {subscriptionId}.
DELETE
Deletes an Individual Inference Subscription identified by subresource {subscriptionId}.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.3.2 Resource: Inference subscriptions
| |
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.3.2.1 Description
| The Inference Subscriptions resource represents all Inference subscriptions to the Naf_Inference service at a given AF. The resource allows an NF service consumer to create a new Individual Inference Subscription resource.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.3.2.2 Resource Definition
| Resource URI: {apiRoot}/naf-inference/<apiVersion>/subscriptions
This resource shall support the resource URI variables defined in table 6.4.3.2.2-1.
Table 6.4.3.2.2-1: Resource URI variables for this resource
Name
Data type
Definition
apiRoot
string
See clause 6.4.1
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.3.2.3 Resource Standard Methods
| |
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.3.2.3.1 POST
| This method shall support the URI query parameters specified in table 6.4.3.2.3.1-1.
Table 6.4.3.2.3.1-1: URI query parameters supported by the POST method on this resource
Name
Data type
P
Cardinality
Description
Applicability
n/a
This method shall support the request data structures specified in table 6.4.3.2.3.1-2 and the response data structures and response codes specified in table 6.4.3.2.3.1-3.
Table 6.4.3.2.3.1-2: Data structures supported by the POST Request Body on this resource
Data type
P
Cardinality
Description
InferEventSubsc
M
1
Contains the information required for the creation of a new Individual Inference Subscription resource.
"intGroupIds" and "supis" target identities on "inferAnaSub" attribute under this structure are not applicable to this API if the NF consumer is a NEF, i.e., the AF is an untrusted AF.
"exterGroupIds" and "gpsis" target identities on "inferAnaSub" attribute under this structure are not applicable to this API if the NF consumer is an NWDAF, i.e., the AF is a trusted AF.
Table 6.4.3.2.3.1-3: Data structures supported by the POST Response Body on this resource
Data type
P
Cardinality
Response
codes
Description
InferEventSubsc
M
1
201 Created
Contains the representation of the Individual Inference Subscription resource.
ProblemDetails
O
0..1
403 Forbidden
(NOTE 2)
NOTE 1: The mandatory HTTP error status code for the POST method listed in Table 5.5.7.1-1 of 3GPP TS 29.500 [4] also apply.
NOTE 2: Failure cases are described in clause 6.4.7.
Table 6.4.3.2.3.1-4: Headers supported by the 201 Response Code on this resource
Name
Data type
P
Cardinality
Description
Location
string
M
1
Contains the URI of the newly created resource, according to the structure: {apiRoot}/naf-inference/<apiVersion>/subscriptions/{subscriptionId}
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.3.2.4 Resource Custom Operations
| There are no resource custom operations defined for this resource in this release of the specification.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.3.3 Resource: Individual Inference Subscription
| |
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.3.3.1 Description
| The Individual Inference Subscription resource represents a single inference subscription to the Naf_Inference service at a given AF.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.3.3.2 Resource Definition
| Resource URI: {apiRoot}/naf-inference/<apiVersion>/subscriptions/{subscriptionId}
This resource shall support the resource URI variables defined in table 6.4.3.3.2-1.
Table 6.4.3.3.2-1: Resource URI variables for this resource
Name
Data type
Definition
apiRoot
string
See clause 6.4.1
subscriptionId
string
Identifies an inference subscription to the Naf_Inference service.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.3.3.3 Resource Standard Methods
| |
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.3.3.3.1 PUT
| This method shall support the URI query parameters specified in table 6.4.3.3.3.1-1.
Table 6.4.3.3.3.1-1: URI query parameters supported by the PUT method on this resource
Name
Data type
P
Cardinality
Description
n/a
This method shall support the request data structures specified in table 6.4.3.3.3.1-2 and the response data structures and response codes specified in table 6.4.3.3.3.1-3.
Table 6.4.3.3.3.1-2: Data structures supported by the PUT Request Body on this resource
Data type
P
Cardinality
Description
InferEventSubsc
M
1
Parameters to replace a subscription to an Individual Inference Subscription resource.
Table 6.4.3.3.3.1-3: Data structures supported by the PUT Response Body on this resource
Data type
P
Cardinality
Response codes
Description
InferEventSubsc
M
1
200 OK
Successful case.
The Individual Inference Subscription resource was modified successfully and a representation is returned.
"intGroupIds" and "supis" target identities on "inferAnaSub" attribute under this structure are not applicable to this API if the NF consumer is a NEF, i.e., the AF is an untrusted AF.
"exterGroupIds" and "gpsis" target identities on "inferAnaSub" attribute under this structure are not applicable to this API if the NF consumer is an NWDAF, i.e., the AF is a trusted AF.
n/a
204 No Content
Successful case.
The Individual Inference Subscription resource was modified successfully.
RedirectResponse
O
0..1
307 Temporary Redirect
Temporary redirection.
(NOTE 2)
RedirectResponse
O
0..1
308 Permanent Redirect
Permanent redirection.
(NOTE 2)
NOTE 1: The mandatory HTTP error status codes for the PUT method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply.
NOTE 2: The RedirectResponse data structure may be provided by an SCP (cf. clause 6.10.9.1 of 3GPP TS 29.500 [4]).
Table 6.4.3.3.3.1-4: Headers supported by the 307 Response Code on this resource
Name
Data type
P
Cardinality
Description
Location
string
M
1
Contains an alternative URI of the resource located in an alternative AF (service) instance towards which the request is redirected.
For the case where the request is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4].
3gpp-Sbi-Target-Nf-Id
string
O
0..1
Contains the identifier of the target NF (service) instance towards which the request is redirected.
Table 6.4.3.3.3.1-5: Headers supported by the 308 Response Code on this resource
Name
Data type
P
Cardinality
Description
Location
string
M
1
Contains an alternative URI of the resource located in an alternative AF (service) instance towards which the request is redirected.
For the case where the request is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4].
3gpp-Sbi-Target-Nf-Id
string
O
0..1
Contains the identifier of the target NF (service) instance towards which the request is redirected.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.3.3.3.2 PATCH
| This method shall support the URI query parameters specified in table 6.4.3.3.3.2-1.
Table 6.4.3.3.3.2-1: URI query parameters supported by the PATCH method on this resource
Name
Data type
P
Cardinality
Description
n/a
This method shall support the request data structures specified in table 6.4.3.3.3.2-2 and the response data structures and response codes specified in table 6.4.3.3.3.2-3.
Table 6.4.3.3.3.2-2: Data structures supported by the PATCH Request Body on this resource
Data type
P
Cardinality
Description
InferEventSubscPatch
M
1
Partial update of parameters to a subscription to an Individual Inference Subscription resource
Table 6.4.3.3.3.2-3: Data structures supported by the PATCH Response Body on this resource
Data type
P
Cardinality
Response
codes
Description
InferEventSubsc
M
1
200 OK
The Individual Inference Subscription resource was partial modified successfully and a representation of that resource is returned.
"intGroupIds" and "supis" target identities on "inferAnaSub" attribute under this structure are not applicable to this API if the NF consumer is a NEF, i.e., the AF is an untrusted AF.
"exterGroupIds" and "gpsis" target identities on "inferAnaSub" attribute under this structure are not applicable to this API if the NF consumer is an NWDAF, i.e., the AF is a trusted AF.
n/a
204 No Content
The Individual AF Inference Subscription resource was partial modified successfully.
RedirectResponse
O
0..1
307 Temporary Redirect
Temporary redirection.
(NOTE 2)
RedirectResponse
O
0..1
308 Permanent Redirect
Permanent redirection.
(NOTE 2)
NOTE 1: The mandatory HTTP error status codes for the PATCH method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply.
NOTE 2: The RedirectResponse data structure may be provided by an SCP (cf. clause 6.10.9.1 of 3GPP TS 29.500 [4]).
Table 6.4.3.3.3.2-4: Headers supported by the 307 Response Code on this resource
Name
Data type
P
Cardinality
Description
Location
string
M
1
Contains an alternative URI of the resource located in an alternative AF (service) instance towards which the request is redirected.
For the case where the request is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4].
3gpp-Sbi-Target-Nf-Id
string
O
0..1
Contains the identifier of the target NF (service) instance towards which the request is redirected.
Table 6.4.3.3.3.2-5: Headers supported by the 308 Response Code on this resource
Name
Data type
P
Cardinality
Description
Location
string
M
1
Contains an alternative URI of the resource located in an alternative AF (service) instance towards which the request is redirected.
For the case where the request is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4].
3gpp-Sbi-Target-Nf-Id
string
O
0..1
Contains the identifier of the target NF (service) instance towards which the request is redirected.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.3.3.3.3 DELETE
| This method shall support the URI query parameters specified in table 6.4.3.3.3.3-1.
Table 6.4.3.3.3.3-1: URI query parameters supported by the DELETE method on this resource
Name
Data type
P
Cardinality
Description
n/a
This method shall support the request data structures specified in table 6.4.3.3.3.3-2 and the response data structures and response codes specified in table 6.4.3.3.3.3-3.
Table 6.4.3.3.3.3-2: Data structures supported by the DELETE Request Body on this resource
Data type
P
Cardinality
Description
n/a
Table 6.4.3.3.3.3-3: Data structures supported by the DELETE Response Body on this resource
Data type
P
Cardinality
Response codes
Description
n/a
204 No Content
Successful case. The Individual Inference Subscription resource matching the subscriptionId was deleted.
RedirectResponse
O
0..1
307 Temporary Redirect
Temporary redirection.
(NOTE 2)
RedirectResponse
O
0..1
308 Permanent Redirect
Permanent redirection.
(NOTE 2)
NOTE 1: The mandatory HTTP error status code for the DELETE method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply.
NOTE 2: The RedirectResponse data structure may be provided by an SCP (cf. clause 6.10.9.1 of 3GPP TS 29.500 [4]).
Table 6.4.3.3.3.3-4: Headers supported by the 307 Response Code on this resource
Name
Data type
P
Cardinality
Description
Location
string
M
1
Contains an alternative URI of the resource located in an alternative AF (service) instance towards which the request is redirected.
For the case where the request is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4].
3gpp-Sbi-Target-Nf-Id
string
O
0..1
Identifier of the target NF (service) instance towards which the request is redirected.
Table 6.4.3.3.3.3-5: Headers supported by the 308 Response Code on this resource
Name
Data type
P
Cardinality
Description
Location
string
M
1
Contains an alternative URI of the resource located in an alternative AF (service) instance towards which the request is redirected.
For the case where the request is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4].
3gpp-Sbi-Target-Nf-Id
string
O
0..1
Identifier of the target NF (service) instance towards which the request is redirected.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.4 Custom Operations without associated resources
| There are no custom operations defined for this resource in this release of the specification.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.5 Notifications
| |
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.5.1 General
| Notifications shall comply to clause 6.4 of 3GPP TS 29.500 [4] and clause 4.6.4.3 of 3GPP TS 29.501 [5].
Table 6.4.5.1-1: Notifications overview
Notification
Callback URI
HTTP method or custom operation
Description
(service operation)
Inference Notification
{notifUri}
POST
Provides Information about observed events.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.5.5 Inference notification
| |
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.5.5.1 Description
| The Inference Event Notification is used by the AF to report one or several observed Inference Events to an NF service consumer that has subscribed to such Notifications via the Individual Inference Subscription resource.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.5.5.2 Target URI
| The Callback URI "{notifUri}" shall be used with the callback URI variables defined in table 6.4.5.5.2-1.
Table 6.4.5.5.2-1: Callback URI variables
Name
Definition
notifUri
String formatted as URI with the Callback Uri
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.5.5.3 Standard Methods
| |
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.5.5.3.1 POST
| This method shall support the request data structures specified in table 6.4.5.5.3.1-1 and the response data structures and response codes specified in table 6.4.5.5.3.1-1.
Table 6.4.5.5.3.1-2: Data structures supported by the POST Request Body
Data type
P
Cardinality
Description
InferNotif
M
1
Provides Information about observed events.
"intGroupIds" and "supis" target identities on "inferResults" attribute under this structure are not applicable to this API if the NF consumer is a NEF, i.e., the AF is an untrusted AF.
"exterGroupIds" and "gpsis" target identities on "inferResults" attribute under this structure are not applicable to this API if the NF consumer is an NWDAF, i.e., the AF is a trusted AF.
Table 6.4.5.5.3.1-3: Data structures supported by the POST Response Body
Data type
P
Cardinality
Response codes
Description
n/a
204 No Content
The receipt of the Notification is acknowledged.
RedirectResponse
O
0..1
307 Temporary Redirect
Temporary redirection, during event notification.
(NOTE 2)
RedirectResponse
O
0..1
308 Permanent Redirect
Permanent redirection, during event notification.
(NOTE 2)
NOTE: The mandatory HTTP error status codes for the POST method listed in Table 5.5.7.1-1 of 3GPP TS 29.500 [4] also apply.
NOTE 2: The RedirectResponse data structure may be provided by an SCP (cf. clause 6.10.9.1 of 3GPP TS 29.500 [4]).
Table 6.4.5.5.3.1-4: Headers supported by the 307 Response Code on this resource
Name
Data type
P
Cardinality
Description
Location
string
M
1
Contains an alternative URI representing the end point of an alternative NF consumer (service) instance towards which the notification should be redirected.
For the case where the request is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4].
3gpp-Sbi-Target-Nf-Id
string
O
0..1
Identifier of the target NF (service) instance towards which the notification request is redirected.
Table 6.4.5.5.3.1-5: Headers supported by the 308 Response Code on this resource
Name
Data type
P
Cardinality
Description
Location
string
M
1
Contains an alternative URI representing the end point of an alternative NF consumer (service) instance towards which the notification should be redirected.
For the case where the request is redirected to the same target via a different SCP, refer to clause 6.10.9.1 of 3GPP TS 29.500 [4].
3gpp-Sbi-Target-Nf-Id
string
O
0..1
Identifier of the target NF (service) instance towards which the notification request is redirected.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.6 Data Model
| |
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.6.1 General
| This clause specifies the application data model supported by the API.
Table 6.4.6.1-1 specifies the data types defined for the Naf_Inference service based interface protocol.
Table 6.4.6.1-1: Naf_Inference specific Data Types
Data type
Clause defined
Description
Applicability
InferAnaSub
6.4.6.2.4
Represents notification of an inference subscription per analytics id.
InferNotif
6.4.6.2.5
Represents notification of an inference subscription.
InferEventSubsc
6.4.6.2.2
Represents an inference subscription.
InferEventSubscPatch
6.4.6.2.3
Represents parameters to request the modification of an inference subscription.
InferResult
6.4.6.2.6
Represents inference results.
Table 6.4.6.1-2 specifies data types re-used by the Naf_Inference service based interface protocol from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the Naf_Inference service based interface.
Table 6.4.6.1-2: Naf_Inference re-used Data Types
Data type
Reference
Comments
Applicability
DelayEventNotif
3GPP TS 29.520 [18]
Indicates that the AF is not able to complete inference within the maximum response time.
AnalyticsMetadata
3GPP TS 29.520 [18]
Represents the types of analytics metadata information that can be requested.
AnalyticsMetadataInfo
3GPP TS 29.520 [18]
Contains analytics metadata information required for analytics aggregation.
DatasetStatisticalProperty
3GPP TS 29.520 [18]
Dataset statistical properties of the data used for inference.
DateTime
3GPP TS 29.571 [16]
Represents a date and time.
DurationSec
3GPP TS 29.571 [16]
Represents a time duration expressed in units of seconds.
EventFilter
3GPP TS 29.520 [18]
Identifies the filter for the subscribed event.
EventNotification
3GPP TS 29.520 [18]
Describes Notifications about events that occurred.
EventReportingRequirement
3GPP TS 29.520 [18]
Represents the analytics reporting requirement information.
ExternalGroupId
3GPP TS 29.571 [16]
External Group Identifier for a user group.
Gpsi
3GPP TS 29.571 [16]
The GPSI for a UE.
GroupId
3GPP TS 29.571 [16]
Identifies a group of UEs.
NwdafEvent
3GPP TS 29.520 [18]
Describes the NWDAF Events.
ReportingInformation
3GPP TS 29.523 [17]
Represents the type of reporting a subscription requires.
RedirectResponse
3GPP TS 29.571 [16]
Contains redirection related information.
Supi
3GPP TS 29.571 [16]
The SUPI for a UE.
SupportedFeatures
3GPP TS 29.571 [16]
Represents the list of supported features.
TimeWindow
3GPP TS 29.122 [22]
Represents a time window.
Uinteger
3GPP TS 29.571 [16]
Unsigned Integer, i.e. only value 0 and integers above 0 are permissible.
Uri
3GPP TS 29.571 [16]
Represents a URI.
VflTermCause
3GPP TS 29.520 [18]
Represents a cause of termination.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.6.2 Structured data types
| |
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.6.2.1 Introduction
| This clause defines the structures to be used in resource representations.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.6.2.2 Type InferEventSubsc
| Table 6.4.6.2.2-1: Definition of type InferEventSubsc
Attribute name
Data type
P
Cardinality
Description
Applicability
notifCorreId
string
M
1
The value of Notification Correlation ID in the corresponding notification.
notifUri
Uri
M
1
URI at which the NF service consumer requests to receive notifications.
suppFeats
SupportedFeatures
C
0..1
List of Supported features used as described in clause 5.10.8.
It shall be supplied by NF service consumer in the POST requests that request the creation of an Inference Subscriptions resource and shall be supplied by the AF in the reply of corresponding request.
inferAnaSubs
map(InferAnaSub)
M
1..N
Identifies the inference subscription information for the subscribed analytics ID(s).
The key of the map shall be set to the value of the "anaEvent" attribute in the InferAnaSub data structure.
inferResults
array(InferResult)
O
1..N
Represents inference results.
This attribute may be present only in the response message and if immediate reporting was requested via the "reportInfo" attribute.
reportInfo
ReportingInformation
O
0..1
Reporting requirement information of the inference subscription.
If omitted, the default values within the ReportingInformation data type apply.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.6.2.3 Type InferEventSubscPatch
| Table 6.4.6.2.3-1: Definition of type InferEventSubscPatch
Attribute name
Data type
P
Cardinality
Description
Applicability
notifUri
Uri
O
0..1
URI at which the NF service consumer requests to receive notifications.
notifCorreId
string
O
0..1
The value of Notification Correlation ID in the corresponding notification.
inferAnaSubs
map(InferAnaSub)
O
1..N
Contains the updated subscribed inference events.
The key of the map shall be set to the value of the "anaEvent" attribute in the InferAnaSub data structure.
reportInfo
ReportingInformation
O
0..1
Reporting requirement information of the inference subscription.
If omitted, the default values within the ReportingInformation data type apply.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.6.2.4 Type InferAnaSub
| Table 6.4.6.2.4-1: Definition of type InferAnaSub
Attribute name
Data type
P
Cardinality
Description
Applicability
anaEvent
NwdafEvent
M
1
Type of analytics for which inference is required.
eventFilter
EventFilter
O
0..1
Inference filter information.
exterGroupIds
array(ExternalGroupId)
C
1..N
Identifies the external group of UE(s) to which the inference applies.
(NOTE 1) (NOTE 2)
gpsis
array(Gpsi)
C
1..N
Each element identifies a GPSI of an UE to which the inference applies.
(NOTE 1) (NOTE 2)
intGroupIds
array(GroupId)
C
1..N
Each element represents an internal group identifier of the UEs to which the inference applies.
(NOTE 2)
supis
array(Supi)
C
1..N
Each element identifies a SUPI of an UE to which the inference applies.
(NOTE 2)
anaMeta
array(AnalyticsMetadata)
O
1..N
List of analytics metadata that are requested to be included in the response.
Only "NUM_OF_SAMPLES", "DATA_WINDOW", "DATA_STAT_PROPS" and “DATA_SOURCES” values are applicable.
dataStatProps
array(DatasetStatisticalProperty)
O
1..N
List of dataset statistical properties of the data to be used to perform inference.
timeWindows
array(TimeWindow)
O
1..N
The time periods for inference.
resTime
DateTime
O
0..1
Time when the local result is needed.
NOTE 1: The "exterGroupIds" and "gpsis" attributes are not applicable in this specification.
NOTE 2: Only one of "exterGroupIds", "gpsis", "intGroupIds", or "supis" attributes shall be provided.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.6.2.5 Type InferNotif
| Table 6.4.6.2.5-1: Definition of type InferNotif
Attribute name
Data type
P
Cardinality
Description
Applicability
notifCorreId
string
M
1
The value of Notification Correlation ID in the corresponding notification.
inferResults
array(InferResult)
M
1..N
Represents inference results.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.6.2.6 Type InferResult
| Table 6.4.6.2.6-1: Definition of type InferResult
Attribute name
Data type
P
Cardinality
Description
Applicability
inferRes
EventNotification
C
0..1
Represents inference results. (NOTE)
vflNotOnTimeInd
DelayEventNotif
C
0..1
Indicates that the AF is not able to provide the inference results within the maximum response time.
(NOTE)
termCause
VflTermCause
C
0..1
A cause for which the AF client will send no further notifications for this subscription to the event specified by "event" attribute. Its presence indicates that the AF requests the termination of the subscription to the event specified by "event" attribute. (NOTE)
NOTE: One of the "inferRes", "termCause" or "vflNotOnTimeInd" attributes shall be provided. The "ML_MODEL_TRAIN_FAILURE" value within the "delayCause" attribute in the "vflNotOnTimeInd" attribute is not applicable. The attributes within the "vflNotOnTimeInd" attribute here apply for VFL.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.6.3 Simple data types and enumerations
| |
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.6.3.1 Introduction
| This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.6.3.2 Simple data types
| The simple data types defined in table 6.4.6.3.2-1 shall be supported.
Table 6.4.6.3.2-1: Simple data types
Type Name
Type Definition
Description
Applicability
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.7 Error Handling
| |
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.7.1 General
| For the Naf_Inference API, HTTP error responses shall be supported as specified in clause 4.8 of 3GPP TS 29.501 [5]. Protocol errors and application errors specified in table 5.5.7.2-1 of 3GPP TS 29.500 [4] shall be supported for an HTTP method if the corresponding HTTP status codes are specified as mandatory for that HTTP method in table 5.5.7.1-1 of 3GPP TS 29.500 [4].
In addition, the requirements in the following clauses are applicable for the Naf_Inference API.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.7.2 Protocol Errors
| No specific procedures for the Naf_Inference service are specified.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.7.3 Application Errors
| The application errors defined for the Naf_Inference service are listed in Table 6.4.7.3-1.
Table 6.4.7.3-1: Application errors
Application Error
HTTP status code
Description
Applicability
OVERLOAD
403 Forbidden
Indicates the NF/AF is overloaded.
UE_LEFT_AREA
403 Forbidden
Indicates the UE has moved out of the serving area.
INFERENCE_REQS_NOT_MET
403 Forbidden
Indicates the inference requirements are not met.
NOT_AVAILABLE_FOR_VFL_PROCESS
403 Forbidden
Indicates the NF is not available for inference process anymore.
NOTE: Including a "ProblemDetails" data structure with the "cause" attribute in the HTTP response is optional unless explicitly mandated in the service operation clauses.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.8 Feature negotiation
| The optional features in table 6.4.8-1 are defined for the Naf_Inference API. They shall be negotiated using the extensibility mechanism defined in clause 6.6 of 3GPP TS 29.500 [4].
Table 6.4.8-1: Supported Features
Feature number
Feature Name
Description
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.9 Security
| As indicated in 3GPP TS 33.501 [8] and 3GPP TS 29.500 [4], the access to the Naf_Inference API may be authorized by means of the OAuth2 protocol (see IETF RFC 6749 [9]), based on local configuration, using the "Client Credentials" authorization grant, where the NRF (see 3GPP TS 29.510 [10]) plays the role of the authorization server.
If OAuth2 is used, an NF Service Consumer, prior to consuming services offered by the Naf_Inference API, shall obtain a "token" from the authorization server, by invoking the Access Token Request service, as described in 3GPP TS 29.510 [10], clause 5.4.2.2.
NOTE: When multiple NRFs are deployed in a network, the NRF used as authorization server is the same NRF that the NF Service Consumer used for discovering the Naf_Inference service.
The Naf_Inference API defines a single scope "naf-inference" for the entire service, and it does not define any additional scopes at resource or operation level.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.4.10 HTTP redirection
| An HTTP request may be redirected to a different AF service instance when using direct or indirect communications (see 3GPP TS 29.500 [4]).
An SCP that reselects a different AF producer instance will return the NF Instance ID of the new AF producer instance in the 3gpp-Sbi-Producer-Id header, as specified in clause 6.40.3.4 of 3GPP TS 29.500 [4].
If an AF redirects a service request to a different AF using an HTTP 307 Temporary Redirect or 308 Permanent Redirect status code, the identity of the new AF towards which the service request is redirected shall be indicated in the 3gpp-Sbi-Target-Nf-Id header of the HTTP 307 Temporary Redirect or 308 Permanent Redirect response as specified in clause 6.40.9.1 of 3GPP TS 29.500 [4].
Annex A (normative):
OpenAPI specification
A.1 General
This Annex specifies the formal definition of the API(s) defined in the present specification. It consists of OpenAPI specifications in YAML format.
This Annex takes precedence when being discrepant to other parts of the specification with respect to the encoding of information elements and methods within the API(s).
NOTE 1: The semantics and procedures, as well as conditions, e.g. for the applicability and allowed combinations of attributes or values, not expressed in the OpenAPI definitions but defined in other parts of the specification also apply.
Informative copies of the OpenAPI specification files contained in this 3GPP Technical Specification are available on a Git-based repository that uses the GitLab software version control system (see clause 5.3.1 of 3GPP TS 29.501 [5] and clause 5B of 3GPP TR 21.900 [7]).
A.2 Naf_VFLTraining API
openapi: 3.0.0
info:
title: Naf_VFLTraining Service API
version: 1.0.0
description: |
AF VFL Training Service.
© 2025, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
All rights reserved.
externalDocs:
description: >
3GPP TS 29.530 V19.0.0; 5G System; Application Function Artificial Intelligence/Machine Learning
(AI/ML) Services.
url: http://www.3gpp.org/ftp/Specs/archive/29_series/29.530/
servers:
- url: '{apiRoot}/naf-vfl-train/v1'
variables:
apiRoot:
default: https://example.com
description: apiRoot as defined in clause 4.4 of 3GPP TS 29.501.
security:
- {}
- oAuth2ClientCredentials:
- naf-vfl-train
paths:
/subscriptions:
post:
summary: Request the creation of a VFL Training Subscription.
operationId: CreateVflTrainSubsc
tags:
- VFL Training Subscriptions (Collection)
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/VflTrainingSubs'
responses:
'201':
description: >
Created. The VFL Training Subscription is successfully created and a representation of
the created Individual VFL Training Subscription resource shall be returned.
content:
application/json:
schema:
$ref: '#/components/schemas/VflTrainingSubs'
headers:
Location:
description: >
Contains the URI of the created Individual VFL Training Subscription resource.
required: true
schema:
type: string
'400':
$ref: 'TS29571_CommonData.yaml#/components/responses/400'
'401':
$ref: 'TS29571_CommonData.yaml#/components/responses/401'
'403':
$ref: 'TS29571_CommonData.yaml#/components/responses/403'
'404':
$ref: 'TS29571_CommonData.yaml#/components/responses/404'
'411':
$ref: 'TS29571_CommonData.yaml#/components/responses/411'
'413':
$ref: 'TS29571_CommonData.yaml#/components/responses/413'
'415':
$ref: 'TS29571_CommonData.yaml#/components/responses/415'
'429':
$ref: 'TS29571_CommonData.yaml#/components/responses/429'
'500':
$ref: 'TS29571_CommonData.yaml#/components/responses/500'
'502':
$ref: 'TS29571_CommonData.yaml#/components/responses/502'
'503':
$ref: 'TS29571_CommonData.yaml#/components/responses/503'
default:
$ref: 'TS29571_CommonData.yaml#/components/responses/default'
callbacks:
myNotification:
'{$request.body#/notifUri}':
post:
requestBody:
required: true
content:
application/json:
schema:
$ref: 'TS29520_Nnwdaf_VFLTraining.yaml#/components/schemas/VflTrainingNotify'
responses:
'204':
description: >
No Content. The VFL Training Notification is successfully received
and acknowledged.
'307':
$ref: 'TS29571_CommonData.yaml#/components/responses/307'
'308':
$ref: 'TS29571_CommonData.yaml#/components/responses/308'
'400':
$ref: 'TS29571_CommonData.yaml#/components/responses/400'
'401':
$ref: 'TS29571_CommonData.yaml#/components/responses/401'
'403':
$ref: 'TS29571_CommonData.yaml#/components/responses/403'
'404':
$ref: 'TS29571_CommonData.yaml#/components/responses/404'
'411':
$ref: 'TS29571_CommonData.yaml#/components/responses/411'
'413':
$ref: 'TS29571_CommonData.yaml#/components/responses/413'
'415':
$ref: 'TS29571_CommonData.yaml#/components/responses/415'
'429':
$ref: 'TS29571_CommonData.yaml#/components/responses/429'
'500':
$ref: 'TS29571_CommonData.yaml#/components/responses/500'
'502':
$ref: 'TS29571_CommonData.yaml#/components/responses/502'
'503':
$ref: 'TS29571_CommonData.yaml#/components/responses/503'
default:
$ref: 'TS29571_CommonData.yaml#/components/responses/default'
/subscriptions/{subscriptionId}:
parameters:
- name: subscriptionId
in: path
description: >
Represents the identifier of the Individual VFL Training Subscription
resource.
required: true
schema:
type: string
get:
summary: Retrieve an existing Individual VFL Training Subscription resource.
operationId: GetIndVflTrainSubsc
tags:
- Individual VFL Training Subscription (Document)
responses:
'200':
description: >
OK. The requested Individual VFL Training Subscription resource is returned.
content:
application/json:
schema:
$ref: '#/components/schemas/VflTrainingSubs'
'307':
$ref: 'TS29571_CommonData.yaml#/components/responses/307'
'308':
$ref: 'TS29571_CommonData.yaml#/components/responses/308'
'400':
$ref: 'TS29571_CommonData.yaml#/components/responses/400'
'401':
$ref: 'TS29571_CommonData.yaml#/components/responses/401'
'403':
$ref: 'TS29571_CommonData.yaml#/components/responses/403'
'404':
$ref: 'TS29571_CommonData.yaml#/components/responses/404'
'406':
$ref: 'TS29571_CommonData.yaml#/components/responses/406'
'429':
$ref: 'TS29571_CommonData.yaml#/components/responses/429'
'500':
$ref: 'TS29571_CommonData.yaml#/components/responses/500'
'502':
$ref: 'TS29571_CommonData.yaml#/components/responses/502'
'503':
$ref: 'TS29571_CommonData.yaml#/components/responses/503'
default:
$ref: 'TS29571_CommonData.yaml#/components/responses/default'
put:
summary: Request the update of an existing Individual VFL Training Subscription resource.
operationId: UpdateIndVflTrainSubsc
tags:
- Individual VFL Training Subscription (Document)
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/VflTrainingSubs'
responses:
'200':
description: >
OK. The Individual VFL Training Subscription resource is successfully updated and a
representation of the updated resource shall be returned in the response body.
content:
application/json:
schema:
$ref: '#/components/schemas/VflTrainingSubs'
'204':
description: >
No Content. The Individual VFL Training Subscription resource is successfully updated
and no content is returned in the response body.
'307':
$ref: 'TS29571_CommonData.yaml#/components/responses/307'
'308':
$ref: 'TS29571_CommonData.yaml#/components/responses/308'
'400':
$ref: 'TS29571_CommonData.yaml#/components/responses/400'
'401':
$ref: 'TS29571_CommonData.yaml#/components/responses/401'
'403':
$ref: 'TS29571_CommonData.yaml#/components/responses/403'
'404':
$ref: 'TS29571_CommonData.yaml#/components/responses/404'
'411':
$ref: 'TS29571_CommonData.yaml#/components/responses/411'
'413':
$ref: 'TS29571_CommonData.yaml#/components/responses/413'
'415':
$ref: 'TS29571_CommonData.yaml#/components/responses/415'
'429':
$ref: 'TS29571_CommonData.yaml#/components/responses/429'
'500':
$ref: 'TS29571_CommonData.yaml#/components/responses/500'
'502':
$ref: 'TS29571_CommonData.yaml#/components/responses/502'
'503':
$ref: 'TS29571_CommonData.yaml#/components/responses/503'
default:
$ref: 'TS29571_CommonData.yaml#/components/responses/default'
patch:
summary: Request the modification of an existing Individual VFL Training Subscription resource.
operationId: ModifyIndVflTrainSubsc
tags:
- Individual VFL Training Subscription (Document)
requestBody:
required: true
content:
application/merge-patch+json:
schema:
$ref: '#/components/schemas/VflTrainingSubsPatch'
responses:
'200':
description: >
OK. The Individual VFL Training Subscription resource is successfully modified and a
representation of the updated resource shall be returned in the response body.
content:
application/json:
schema:
$ref: '#/components/schemas/VflTrainingSubs'
'204':
description: >
No Content. The Individual VFL Training Subscription resource is successfully modified
and no content is returned in the response body.
'307':
$ref: 'TS29571_CommonData.yaml#/components/responses/307'
'308':
$ref: 'TS29571_CommonData.yaml#/components/responses/308'
'400':
$ref: 'TS29571_CommonData.yaml#/components/responses/400'
'401':
$ref: 'TS29571_CommonData.yaml#/components/responses/401'
'403':
$ref: 'TS29571_CommonData.yaml#/components/responses/403'
'404':
$ref: 'TS29571_CommonData.yaml#/components/responses/404'
'411':
$ref: 'TS29571_CommonData.yaml#/components/responses/411'
'413':
$ref: 'TS29571_CommonData.yaml#/components/responses/413'
'415':
$ref: 'TS29571_CommonData.yaml#/components/responses/415'
'429':
$ref: 'TS29571_CommonData.yaml#/components/responses/429'
'500':
$ref: 'TS29571_CommonData.yaml#/components/responses/500'
'502':
$ref: 'TS29571_CommonData.yaml#/components/responses/502'
'503':
$ref: 'TS29571_CommonData.yaml#/components/responses/503'
default:
$ref: 'TS29571_CommonData.yaml#/components/responses/default'
delete:
summary: Request the deletion of an existing Individual VFL Training Subscription resource.
operationId: DeleteIndVflTrainSubsc
tags:
- Individual VFL Training Subscription (Document)
responses:
'204':
description: >
No Content. The Individual VFL Training Subscription resource is successfully deleted.
'307':
$ref: 'TS29571_CommonData.yaml#/components/responses/307'
'308':
$ref: 'TS29571_CommonData.yaml#/components/responses/308'
'400':
$ref: 'TS29571_CommonData.yaml#/components/responses/400'
'401':
$ref: 'TS29571_CommonData.yaml#/components/responses/401'
'403':
$ref: 'TS29571_CommonData.yaml#/components/responses/403'
'404':
$ref: 'TS29571_CommonData.yaml#/components/responses/404'
'429':
$ref: 'TS29571_CommonData.yaml#/components/responses/429'
'500':
$ref: 'TS29571_CommonData.yaml#/components/responses/500'
'502':
$ref: 'TS29571_CommonData.yaml#/components/responses/502'
'503':
$ref: 'TS29571_CommonData.yaml#/components/responses/503'
default:
$ref: 'TS29571_CommonData.yaml#/components/responses/default'
components:
securitySchemes:
oAuth2ClientCredentials:
type: oauth2
flows:
clientCredentials:
tokenUrl: '{nrfApiRoot}/oauth2/token'
scopes:
naf-vfl-train: >
Enables to access all the resources and custom operations of the Naf_VFLTraining API.
schemas:
#
# STRUCTURED DATA TYPES
#
VflTrainingSubs:
description: >
Represents a VFL Training Subscription.
type: object
properties:
vflTrainSubs:
type: array
items:
$ref: 'TS29520_Nnwdaf_VFLTraining.yaml#/components/schemas/VflTrainingSub'
minItems: 1
notifUri:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Uri'
notifCorrId:
type: string
vflPreFlag:
type: boolean
description: >
Indicates the subscription is for preparation of VFL, when it is included and set to
"true". The default value is "false" if omitted.
reportingReqs:
$ref: 'TS29523_Npcf_EventExposure.yaml#/components/schemas/ReportingInformation'
trainReports:
type: array
items:
$ref: 'TS29520_Nnwdaf_VFLTraining.yaml#/components/schemas/VflTrainingNotify'
minItems: 1
suppFeat:
$ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures'
required:
- vflTrainSubs
VflTrainingSubsPatch:
description: >
Represents the requested modifications to a VFL Training Subscription.
type: object
properties:
vflTrainSubs:
type: array
items:
$ref: 'TS29520_Nnwdaf_VFLTraining.yaml#/components/schemas/VflTrainingSub'
minItems: 1
notifUri:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Uri'
notifCorrId:
type: string
reportingReqs:
$ref: 'TS29523_Npcf_EventExposure.yaml#/components/schemas/ReportingInformation'
# SIMPLE DATA TYPES
#
#
# ENUMERATIONS
#
# Data types describing alternative data types or combinations of data types:
#
A.3 Naf_VFLInference API
openapi: 3.0.0
info:
title: Naf_VFLInference
version: 1.0.0
description: |
Naf_VflInference API Service.
© 2025, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
All rights reserved.
externalDocs:
description: >
3GPP TS 29.530 V19.0.0; 5G System; Application Function Artificial Intelligence/Machine
Learning (AI/ML) Services
url: https://www.3gpp.org/ftp/Specs/archive/29_series/29.530/
servers:
- url: '{apiRoot}/naf-vflinference/v1'
variables:
apiRoot:
default: https://example.com
description: apiRoot as defined in clause 4.4 of 3GPP TS 29.501
security:
- {}
- oAuth2ClientCredentials:
- naf-vflinference
paths:
/subscriptions:
post:
summary: Create a new Individual VFL Inference Subscription resource.
operationId: CreateVFLInferenceSubcription
tags:
- Subscriptions (Collection)
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/VflInferSub'
responses:
'201':
description: Create a new Individual VFL Inference Subscription resource.
content:
application/json:
schema:
$ref: '#/components/schemas/VflInferSub'
headers:
Location:
description: >
Contains the URI of the newly created resource, according to the
structure
{apiRoot}/naf-vflinference/v1/subscriptions/{subscriptionId}.
required: true
schema:
type: string
'400':
$ref: 'TS29571_CommonData.yaml#/components/responses/400'
'401':
$ref: 'TS29571_CommonData.yaml#/components/responses/401'
'403':
$ref: 'TS29571_CommonData.yaml#/components/responses/403'
'404':
$ref: 'TS29571_CommonData.yaml#/components/responses/404'
'411':
$ref: 'TS29571_CommonData.yaml#/components/responses/411'
'413':
$ref: 'TS29571_CommonData.yaml#/components/responses/413'
'415':
$ref: 'TS29571_CommonData.yaml#/components/responses/415'
'429':
$ref: 'TS29571_CommonData.yaml#/components/responses/429'
'500':
$ref: 'TS29571_CommonData.yaml#/components/responses/500'
'502':
$ref: 'TS29571_CommonData.yaml#/components/responses/502'
'503':
$ref: 'TS29571_CommonData.yaml#/components/responses/503'
default:
$ref: 'TS29571_CommonData.yaml#/components/responses/default'
callbacks:
myNotification:
'{$request.body#/notifUri}':
post:
requestBody:
required: true
content:
application/json:
schema:
$ref: 'TS29520_Nnwdaf_VFLInference.yaml#/components/schemas/VflInferNotif'
responses:
'204':
description: No Content, Notification was succesfull
'307':
$ref: 'TS29571_CommonData.yaml#/components/responses/307'
'308':
$ref: 'TS29571_CommonData.yaml#/components/responses/308'
'400':
$ref: 'TS29571_CommonData.yaml#/components/responses/400'
'401':
$ref: 'TS29571_CommonData.yaml#/components/responses/401'
'403':
$ref: 'TS29571_CommonData.yaml#/components/responses/403'
'404':
$ref: 'TS29571_CommonData.yaml#/components/responses/404'
'411':
$ref: 'TS29571_CommonData.yaml#/components/responses/411'
'413':
$ref: 'TS29571_CommonData.yaml#/components/responses/413'
'415':
$ref: 'TS29571_CommonData.yaml#/components/responses/415'
'429':
$ref: 'TS29571_CommonData.yaml#/components/responses/429'
'500':
$ref: 'TS29571_CommonData.yaml#/components/responses/500'
'502':
$ref: 'TS29571_CommonData.yaml#/components/responses/502'
'503':
$ref: 'TS29571_CommonData.yaml#/components/responses/503'
default:
$ref: 'TS29571_CommonData.yaml#/components/responses/default'
/subscriptions/{subscriptionId}:
parameters:
- name: subscriptionId
in: path
description: String identifying a subscription to the Naf_VFLInference Service.
required: true
schema:
type: string
get:
summary: Retrieve an existing Individual VFL Inference Subscription resource.
operationId: GetIndVFLTrainSubsc
tags:
- Individual VFL Inference Subscription (Document)
responses:
'200':
description: >
OK. The requested Individual VFL Inference Subscription resource is returned.
content:
application/json:
schema:
$ref: '#/components/schemas/VflInferSub'
'307':
$ref: 'TS29571_CommonData.yaml#/components/responses/307'
'308':
$ref: 'TS29571_CommonData.yaml#/components/responses/308'
'400':
$ref: 'TS29571_CommonData.yaml#/components/responses/400'
'401':
$ref: 'TS29571_CommonData.yaml#/components/responses/401'
'403':
$ref: 'TS29571_CommonData.yaml#/components/responses/403'
'404':
$ref: 'TS29571_CommonData.yaml#/components/responses/404'
'406':
$ref: 'TS29571_CommonData.yaml#/components/responses/406'
'429':
$ref: 'TS29571_CommonData.yaml#/components/responses/429'
'500':
$ref: 'TS29571_CommonData.yaml#/components/responses/500'
'502':
$ref: 'TS29571_CommonData.yaml#/components/responses/502'
'503':
$ref: 'TS29571_CommonData.yaml#/components/responses/503'
default:
$ref: 'TS29571_CommonData.yaml#/components/responses/default'
put:
summary: Update an existing Individual VFL Inference Subscription
operationId: UpdateVFLInferenceSubcription
tags:
- Individual VFL Inference Subscription (Document)
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/VflInferSub'
responses:
'200':
description: >
The Individual VFL Inference Subscription resource was modified
successfully and a representation of that resource is returned.
content:
application/json:
schema:
$ref: '#/components/schemas/VflInferSub'
'204':
description: >
The Individual VFL Inference Subscription resource was modified successfully.
'307':
$ref: 'TS29571_CommonData.yaml#/components/responses/307'
'308':
$ref: 'TS29571_CommonData.yaml#/components/responses/308'
'400':
$ref: 'TS29571_CommonData.yaml#/components/responses/400'
'401':
$ref: 'TS29571_CommonData.yaml#/components/responses/401'
'403':
$ref: 'TS29571_CommonData.yaml#/components/responses/403'
'404':
$ref: 'TS29571_CommonData.yaml#/components/responses/404'
'411':
$ref: 'TS29571_CommonData.yaml#/components/responses/411'
'413':
$ref: 'TS29571_CommonData.yaml#/components/responses/413'
'415':
$ref: 'TS29571_CommonData.yaml#/components/responses/415'
'429':
$ref: 'TS29571_CommonData.yaml#/components/responses/429'
'500':
$ref: 'TS29571_CommonData.yaml#/components/responses/500'
'502':
$ref: 'TS29571_CommonData.yaml#/components/responses/502'
'503':
$ref: 'TS29571_CommonData.yaml#/components/responses/503'
default:
$ref: 'TS29571_CommonData.yaml#/components/responses/default'
patch:
summary: Partial update an existing Individual VFL Inference Subscription
operationId: PartialUpdateVFLInferenceSubcription
tags:
- Individual VFL Inference Subscription (Document)
requestBody:
required: true
content:
application/merge-patch+json:
schema:
$ref: '#/components/schemas/VflInferSubPatch'
responses:
'200':
description: >
The Individual VFL Inference Subscription resource was partial modified successfully
and a representation of that resource is returned.
content:
application/json:
schema:
$ref: '#/components/schemas/VflInferSub'
'204':
description: >
The Individual VFL Inference Subscription resource was partial modified
successfully.
'307':
$ref: 'TS29571_CommonData.yaml#/components/responses/307'
'308':
$ref: 'TS29571_CommonData.yaml#/components/responses/308'
'400':
$ref: 'TS29571_CommonData.yaml#/components/responses/400'
'401':
$ref: 'TS29571_CommonData.yaml#/components/responses/401'
'403':
$ref: 'TS29571_CommonData.yaml#/components/responses/403'
'404':
$ref: 'TS29571_CommonData.yaml#/components/responses/404'
'411':
$ref: 'TS29571_CommonData.yaml#/components/responses/411'
'413':
$ref: 'TS29571_CommonData.yaml#/components/responses/413'
'415':
$ref: 'TS29571_CommonData.yaml#/components/responses/415'
'429':
$ref: 'TS29571_CommonData.yaml#/components/responses/429'
'500':
$ref: 'TS29571_CommonData.yaml#/components/responses/500'
'502':
$ref: 'TS29571_CommonData.yaml#/components/responses/502'
'503':
$ref: 'TS29571_CommonData.yaml#/components/responses/503'
default:
$ref: 'TS29571_CommonData.yaml#/components/responses/default'
delete:
summary: Delete an existing Individual VFL Inference Subscription.
operationId: DeleteVFLInferenceSubcription
tags:
- Individual VFL Inference Subscription (Document)
responses:
'204':
description: >
No Content. The Individual VFL Inference Subscription matching the
subscriptionId was deleted.
'307':
$ref: 'TS29571_CommonData.yaml#/components/responses/307'
'308':
$ref: 'TS29571_CommonData.yaml#/components/responses/308'
'400':
$ref: 'TS29571_CommonData.yaml#/components/responses/400'
'401':
$ref: 'TS29571_CommonData.yaml#/components/responses/401'
'403':
$ref: 'TS29571_CommonData.yaml#/components/responses/403'
'404':
$ref: 'TS29571_CommonData.yaml#/components/responses/404'
'429':
$ref: 'TS29571_CommonData.yaml#/components/responses/429'
'500':
$ref: 'TS29571_CommonData.yaml#/components/responses/500'
'502':
$ref: 'TS29571_CommonData.yaml#/components/responses/502'
'503':
$ref: 'TS29571_CommonData.yaml#/components/responses/503'
default:
$ref: 'TS29571_CommonData.yaml#/components/responses/default'
components:
securitySchemes:
oAuth2ClientCredentials:
type: oauth2
flows:
clientCredentials:
tokenUrl: '{nrfApiRoot}/oauth2/token'
scopes:
naf-vflinference: Access to the Naf_VflInference API
schemas:
VflInferSub:
description: Represents a VFL Inference subscription.
type: object
properties:
notifCorrId:
type: string
description: >
String identifying the Notification Correlation ID in the corresponding
notification.
notifUri:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Uri'
reportingReqs:
$ref: 'TS29523_Npcf_EventExposure.yaml#/components/schemas/ReportingInformation'
suppFeats:
$ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures'
vflInferAnaSubs:
type: array
items:
$ref: 'TS29520_Nnwdaf_VFLInference.yaml#/components/schemas/VflInferAnaSub'
minItems: 1
description: >
Contains VFL inference subscription information for the subscribed analytics ID(s).
vflInferReq:
$ref: 'TS29520_Nnwdaf_VFLInference.yaml#/components/schemas/VflInferReq'
vflInferResults:
type: array
items:
$ref: 'TS29520_Nnwdaf_VFLInference.yaml#/components/schemas/VflInferResult'
minItems: 1
description: Represents intermediate VFL Inference result.
required:
- notifUri
- notifCorrId
- vflInferAnaSubs
VflInferSubPatch:
description: >
Represents parameters to request the modification of a VFL Inference
subscription.
type: object
properties:
notifUri:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Uri'
notifCorrId:
type: string
description: >
String identifying the Notification Correlation ID in the corresponding
notification.
reportingReqs:
$ref: 'TS29523_Npcf_EventExposure.yaml#/components/schemas/ReportingInformation'
vflInferAnaSubs:
type: array
items:
$ref: 'TS29520_Nnwdaf_VFLInference.yaml#/components/schemas/VflInferAnaSub'
minItems: 1
description: >
Contains updated VFL inference subscription information for the subscribed
analytics ID(s).
vflInferReq:
$ref: 'TS29520_Nnwdaf_VFLInference.yaml#/components/schemas/VflInferReq'
#
# ENUMERATIONS DATA TYPES
#
A.4 Naf_Training API
openapi: 3.0.0
info:
title: Naf_Training Service API
version: 1.0.0
description: |
AF Training Service.
© 2025, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
All rights reserved.
externalDocs:
description: >
3GPP TS 29.530 V19.0.0; 5G System; Application Function Artificial Intelligence/Machine Learning
(AI/ML) Services.
url: http://www.3gpp.org/ftp/Specs/archive/29_series/29.530/
servers:
- url: '{apiRoot}/naf-train/v1'
variables:
apiRoot:
default: https://example.com
description: apiRoot as defined in clause 4.4 of 3GPP TS 29.501.
security:
- {}
- oAuth2ClientCredentials:
- naf-train
paths:
/subscriptions:
post:
summary: Request the creation of a Training Subscription.
operationId: CreateTrainSubsc
tags:
- Training Subscriptions (Collection)
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/TrainEventsSubsc'
responses:
'201':
description: >
Created. The Training Subscription is successfully created and a representation of
the created Individual Training Subscription resource shall be returned.
content:
application/json:
schema:
$ref: '#/components/schemas/TrainEventsSubsc'
headers:
Location:
description: >
Contains the URI of the created Individual Training Subscription resource.
required: true
schema:
type: string
'400':
$ref: 'TS29571_CommonData.yaml#/components/responses/400'
'401':
$ref: 'TS29571_CommonData.yaml#/components/responses/401'
'403':
$ref: 'TS29571_CommonData.yaml#/components/responses/403'
'404':
$ref: 'TS29571_CommonData.yaml#/components/responses/404'
'411':
$ref: 'TS29571_CommonData.yaml#/components/responses/411'
'413':
$ref: 'TS29571_CommonData.yaml#/components/responses/413'
'415':
$ref: 'TS29571_CommonData.yaml#/components/responses/415'
'429':
$ref: 'TS29571_CommonData.yaml#/components/responses/429'
'500':
$ref: 'TS29571_CommonData.yaml#/components/responses/500'
'502':
$ref: 'TS29571_CommonData.yaml#/components/responses/502'
'503':
$ref: 'TS29571_CommonData.yaml#/components/responses/503'
default:
$ref: 'TS29571_CommonData.yaml#/components/responses/default'
callbacks:
TrainEventsNotif:
'{$request.body#/notifUri}':
post:
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/TrainEventsNotif'
responses:
'204':
description: >
No Content. The Training Notification is successfully received
and acknowledged.
'307':
$ref: 'TS29571_CommonData.yaml#/components/responses/307'
'308':
$ref: 'TS29571_CommonData.yaml#/components/responses/308'
'400':
$ref: 'TS29571_CommonData.yaml#/components/responses/400'
'401':
$ref: 'TS29571_CommonData.yaml#/components/responses/401'
'403':
$ref: 'TS29571_CommonData.yaml#/components/responses/403'
'404':
$ref: 'TS29571_CommonData.yaml#/components/responses/404'
'411':
$ref: 'TS29571_CommonData.yaml#/components/responses/411'
'413':
$ref: 'TS29571_CommonData.yaml#/components/responses/413'
'415':
$ref: 'TS29571_CommonData.yaml#/components/responses/415'
'429':
$ref: 'TS29571_CommonData.yaml#/components/responses/429'
'500':
$ref: 'TS29571_CommonData.yaml#/components/responses/500'
'502':
$ref: 'TS29571_CommonData.yaml#/components/responses/502'
'503':
$ref: 'TS29571_CommonData.yaml#/components/responses/503'
default:
$ref: 'TS29571_CommonData.yaml#/components/responses/default'
/subscriptions/{subscriptionId}:
parameters:
- name: subscriptionId
in: path
description: >
Represents the identifier of the Individual Training Subscription
resource.
required: true
schema:
type: string
get:
summary: Retrieve an existing Individual Training Subscription resource.
operationId: GetIndTrainSubsc
tags:
- Individual Training Subscription (Document)
responses:
'200':
description: >
OK. The requested Individual Training Subscription resource is returned.
content:
application/json:
schema:
$ref: '#/components/schemas/TrainEventsSubsc'
'307':
$ref: 'TS29571_CommonData.yaml#/components/responses/307'
'308':
$ref: 'TS29571_CommonData.yaml#/components/responses/308'
'400':
$ref: 'TS29571_CommonData.yaml#/components/responses/400'
'401':
$ref: 'TS29571_CommonData.yaml#/components/responses/401'
'403':
$ref: 'TS29571_CommonData.yaml#/components/responses/403'
'404':
$ref: 'TS29571_CommonData.yaml#/components/responses/404'
'406':
$ref: 'TS29571_CommonData.yaml#/components/responses/406'
'429':
$ref: 'TS29571_CommonData.yaml#/components/responses/429'
'500':
$ref: 'TS29571_CommonData.yaml#/components/responses/500'
'502':
$ref: 'TS29571_CommonData.yaml#/components/responses/502'
'503':
$ref: 'TS29571_CommonData.yaml#/components/responses/503'
default:
$ref: 'TS29571_CommonData.yaml#/components/responses/default'
put:
summary: Request the update of an existing Individual Training Subscription resource.
operationId: UpdateIndTrainSubsc
tags:
- Individual Training Subscription (Document)
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/TrainEventsSubsc'
responses:
'200':
description: >
OK. The Individual Training Subscription resource is successfully updated and a
representation of the updated resource shall be returned in the response body.
content:
application/json:
schema:
$ref: '#/components/schemas/TrainEventsSubsc'
'204':
description: >
No Content. The Individual Training Subscription resource is successfully updated
and no content is returned in the response body.
'307':
$ref: 'TS29571_CommonData.yaml#/components/responses/307'
'308':
$ref: 'TS29571_CommonData.yaml#/components/responses/308'
'400':
$ref: 'TS29571_CommonData.yaml#/components/responses/400'
'401':
$ref: 'TS29571_CommonData.yaml#/components/responses/401'
'403':
$ref: 'TS29571_CommonData.yaml#/components/responses/403'
'404':
$ref: 'TS29571_CommonData.yaml#/components/responses/404'
'411':
$ref: 'TS29571_CommonData.yaml#/components/responses/411'
'413':
$ref: 'TS29571_CommonData.yaml#/components/responses/413'
'415':
$ref: 'TS29571_CommonData.yaml#/components/responses/415'
'429':
$ref: 'TS29571_CommonData.yaml#/components/responses/429'
'500':
$ref: 'TS29571_CommonData.yaml#/components/responses/500'
'502':
$ref: 'TS29571_CommonData.yaml#/components/responses/502'
'503':
$ref: 'TS29571_CommonData.yaml#/components/responses/503'
default:
$ref: 'TS29571_CommonData.yaml#/components/responses/default'
patch:
summary: Request the modification of an existing Individual Training Subscription resource.
operationId: ModifyIndTrainSubsc
tags:
- Individual Training Subscription (Document)
requestBody:
required: true
content:
application/merge-patch+json:
schema:
$ref: '#/components/schemas/TrainEventsSubscPatch'
responses:
'200':
description: >
OK. The Individual Training Subscription resource is successfully modified and a
representation of the updated resource shall be returned in the response body.
content:
application/json:
schema:
$ref: '#/components/schemas/TrainEventsSubsc'
'204':
description: >
No Content. The Individual Training Subscription resource is successfully modified
and no content is returned in the response body.
'307':
$ref: 'TS29571_CommonData.yaml#/components/responses/307'
'308':
$ref: 'TS29571_CommonData.yaml#/components/responses/308'
'400':
$ref: 'TS29571_CommonData.yaml#/components/responses/400'
'401':
$ref: 'TS29571_CommonData.yaml#/components/responses/401'
'403':
$ref: 'TS29571_CommonData.yaml#/components/responses/403'
'404':
$ref: 'TS29571_CommonData.yaml#/components/responses/404'
'411':
$ref: 'TS29571_CommonData.yaml#/components/responses/411'
'413':
$ref: 'TS29571_CommonData.yaml#/components/responses/413'
'415':
$ref: 'TS29571_CommonData.yaml#/components/responses/415'
'429':
$ref: 'TS29571_CommonData.yaml#/components/responses/429'
'500':
$ref: 'TS29571_CommonData.yaml#/components/responses/500'
'502':
$ref: 'TS29571_CommonData.yaml#/components/responses/502'
'503':
$ref: 'TS29571_CommonData.yaml#/components/responses/503'
default:
$ref: 'TS29571_CommonData.yaml#/components/responses/default'
delete:
summary: Request the deletion of an existing Individual Training Subscription resource.
operationId: DeleteIndTrainSubsc
tags:
- Individual Training Subscription (Document)
responses:
'204':
description: >
No Content. The Individual Training Subscription resource is successfully deleted.
'307':
$ref: 'TS29571_CommonData.yaml#/components/responses/307'
'308':
$ref: 'TS29571_CommonData.yaml#/components/responses/308'
'400':
$ref: 'TS29571_CommonData.yaml#/components/responses/400'
'401':
$ref: 'TS29571_CommonData.yaml#/components/responses/401'
'403':
$ref: 'TS29571_CommonData.yaml#/components/responses/403'
'404':
$ref: 'TS29571_CommonData.yaml#/components/responses/404'
'429':
$ref: 'TS29571_CommonData.yaml#/components/responses/429'
'500':
$ref: 'TS29571_CommonData.yaml#/components/responses/500'
'502':
$ref: 'TS29571_CommonData.yaml#/components/responses/502'
'503':
$ref: 'TS29571_CommonData.yaml#/components/responses/503'
default:
$ref: 'TS29571_CommonData.yaml#/components/responses/default'
components:
securitySchemes:
oAuth2ClientCredentials:
type: oauth2
flows:
clientCredentials:
tokenUrl: '{nrfApiRoot}/oauth2/token'
scopes:
naf-train: >
Enables to access all the resources and custom operations of the Naf_Training API.
schemas:
#
# STRUCTURED DATA TYPES
#
TrainEventsSubsc:
description: Represents a Training Subscription.
type: object
properties:
trainEventSubs:
type: object
additionalProperties:
$ref: '#/components/schemas/EventSubsc'
minProperties: 1
description: >
Contains the subscribed training events. The key of the map shall be set to the
value of the "event" attribute in the EventSubsc data structure.
notifUri:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Uri'
notifCorreId:
type: string
reportingReqs:
$ref: 'TS29523_Npcf_EventExposure.yaml#/components/schemas/ReportingInformation'
eventNotifs:
type: array
items:
$ref: '#/components/schemas/EventNotif'
minItems: 1
suppFeat:
$ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures'
required:
- trainEventSubs
- notifUri
- notifCorreId
TrainEventsSubscPatch:
description: Represents the requested modifications to a Training Subscription.
type: object
properties:
trainEventSubs:
type: object
additionalProperties:
$ref: '#/components/schemas/EventSubsc'
minProperties: 1
description: >
Contains the updated subscribed training events. The key of the map shall be set to the
value of the "event" attribute in the EventSubsc data structure.
notifUri:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Uri'
notifCorreId:
type: string
reportingReqs:
$ref: 'TS29523_Npcf_EventExposure.yaml#/components/schemas/ReportingInformation'
EventSubsc:
description: Represents events training subscription.
type: object
properties:
event:
$ref: 'TS29520_Nnwdaf_EventsSubscription.yaml#/components/schemas/NwdafEvent'
useCaseCxt:
type: string
trainFilter:
$ref: 'TS29520_Nnwdaf_AnalyticsInfo.yaml#/components/schemas/EventFilter'
tgtUe:
$ref: 'TS29520_Nnwdaf_EventsSubscription.yaml#/components/schemas/TargetUeInformation'
repRatio:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Uinteger'
targetPeriod:
$ref: 'TS29122_CommonData.yaml#/components/schemas/TimeWindow'
inferInputData:
$ref: 'TS29520_Nnwdaf_MLModelProvision.yaml#/components/schemas/InputDataInfo'
timeModelNeeded:
$ref: 'TS29571_CommonData.yaml#/components/schemas/DateTime'
modelMonInfo:
$ref: '#/components/schemas/MlModelMonitorInfo'
accuLevel:
$ref: 'TS29520_Nnwdaf_EventsSubscription.yaml#/components/schemas/Accuracy'
required:
- event
MlModelMonitorInfo:
description: Represents an event training subscription.
type: object
properties:
modelMetric:
$ref: 'TS29520_Nnwdaf_MLModelProvision.yaml#/components/schemas/MLModelMetric'
accuThreshold:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Uinteger'
storedData:
$ref: 'TS29520_Nnwdaf_MLModelProvision.yaml#/components/schemas/InferenceDataForModelTrain'
TrainEventsNotif:
description: Represents a events training notification.
type: object
properties:
notifCorreId:
type: string
eventNotifs:
type: array
items:
$ref: '#/components/schemas/EventNotif'
minItems: 1
required:
- notifCorreId
- eventNotifs
EventNotif:
description: Represents an event training report.
type: object
properties:
event:
$ref: 'TS29520_Nnwdaf_EventsSubscription.yaml#/components/schemas/NwdafEvent'
vflNotOnTimeInd:
$ref: 'TS29520_Nnwdaf_MLModelTraining.yaml#/components/schemas/DelayEventNotif'
trainingInd:
type: boolean
description: >
Set to "true" to indicate that the ML model training is ongoing. Set to "false" to
indicate that the ML model training is done. Default value is "false" if omitted.
validityPeriod:
$ref: 'TS29122_CommonData.yaml#/components/schemas/TimeWindow'
spatialValidity:
$ref: 'TS29554_Npcf_BDTPolicyControl.yaml#/components/schemas/NetworkAreaInfo'
repRatio:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Uinteger'
accMLModel:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Uinteger'
termCause:
$ref: 'TS29520_Nnwdaf_VFLInference.yaml#/components/schemas/VflTermCause'
vflCorrId:
type: string
required:
- event
# SIMPLE DATA TYPES
#
#
# ENUMERATIONS
#
# Data types describing alternative data types or combinations of data types:
#
A.5 Naf_Inference API
openapi: 3.0.0
info:
title: Naf_Inference
version: 1.0.0
description: |
Naf_Inference API Service.
© 2025, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
All rights reserved.
externalDocs:
description: >
3GPP TS 29.530 V19.0.0; 5G System; Application Function Artificial
Intelligence/Machine Learning (AI/ML) Services.
url: https://www.3gpp.org/ftp/Specs/archive/29_series/29.530/
servers:
- url: '{apiRoot}/naf-inference/v1'
variables:
apiRoot:
default: https://example.com
description: apiRoot as defined in clause 4.4 of 3GPP TS 29.501
security:
- {}
- oAuth2ClientCredentials:
- naf-inference
paths:
/subscriptions:
post:
summary: Create a new Individual Inference Subscription resource.
operationId: CreateInferenceSubcription
tags:
- Subscriptions (Collection)
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/InferEventSubsc'
responses:
'201':
description: Create a new Individual Inference Subscription resource.
content:
application/json:
schema:
$ref: '#/components/schemas/InferEventSubsc'
headers:
Location:
description: >
Contains the URI of the newly created resource, according to the
structure
{apiRoot}/naf-inference/v1/subscriptions/{subscriptionId}.
required: true
schema:
type: string
'400':
$ref: 'TS29571_CommonData.yaml#/components/responses/400'
'401':
$ref: 'TS29571_CommonData.yaml#/components/responses/401'
'403':
$ref: 'TS29571_CommonData.yaml#/components/responses/403'
'404':
$ref: 'TS29571_CommonData.yaml#/components/responses/404'
'411':
$ref: 'TS29571_CommonData.yaml#/components/responses/411'
'413':
$ref: 'TS29571_CommonData.yaml#/components/responses/413'
'415':
$ref: 'TS29571_CommonData.yaml#/components/responses/415'
'429':
$ref: 'TS29571_CommonData.yaml#/components/responses/429'
'500':
$ref: 'TS29571_CommonData.yaml#/components/responses/500'
'502':
$ref: 'TS29571_CommonData.yaml#/components/responses/502'
'503':
$ref: 'TS29571_CommonData.yaml#/components/responses/503'
default:
$ref: 'TS29571_CommonData.yaml#/components/responses/default'
callbacks:
myNotification:
'{$request.body#/notifUri}':
post:
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/InferNotif'
responses:
'204':
description: No Content, Notification was successful
'307':
$ref: 'TS29571_CommonData.yaml#/components/responses/307'
'308':
$ref: 'TS29571_CommonData.yaml#/components/responses/308'
'400':
$ref: 'TS29571_CommonData.yaml#/components/responses/400'
'401':
$ref: 'TS29571_CommonData.yaml#/components/responses/401'
'403':
$ref: 'TS29571_CommonData.yaml#/components/responses/403'
'404':
$ref: 'TS29571_CommonData.yaml#/components/responses/404'
'411':
$ref: 'TS29571_CommonData.yaml#/components/responses/411'
'413':
$ref: 'TS29571_CommonData.yaml#/components/responses/413'
'415':
$ref: 'TS29571_CommonData.yaml#/components/responses/415'
'429':
$ref: 'TS29571_CommonData.yaml#/components/responses/429'
'500':
$ref: 'TS29571_CommonData.yaml#/components/responses/500'
'502':
$ref: 'TS29571_CommonData.yaml#/components/responses/502'
'503':
$ref: 'TS29571_CommonData.yaml#/components/responses/503'
default:
$ref: 'TS29571_CommonData.yaml#/components/responses/default'
/subscriptions/{subscriptionId}:
put:
summary: Update an existing Individual Inference Subscription
operationId: UpdateInferenceSubcription
tags:
- Individual Inference Subscription (Document)
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/InferEventSubsc'
parameters:
- name: subscriptionId
in: path
description: String identifying a subscription to the Naf_Inference Service.
required: true
schema:
type: string
responses:
'200':
description: >
The Individual Inference Subscription resource was modified
successfully and a representation of that resource is returned.
content:
application/json:
schema:
$ref: '#/components/schemas/InferEventSubsc'
'204':
description: >
The Individual Inference Subscription resource was modified
successfully.
'307':
$ref: 'TS29571_CommonData.yaml#/components/responses/307'
'308':
$ref: 'TS29571_CommonData.yaml#/components/responses/308'
'400':
$ref: 'TS29571_CommonData.yaml#/components/responses/400'
'401':
$ref: 'TS29571_CommonData.yaml#/components/responses/401'
'403':
$ref: 'TS29571_CommonData.yaml#/components/responses/403'
'404':
$ref: 'TS29571_CommonData.yaml#/components/responses/404'
'406':
$ref: 'TS29571_CommonData.yaml#/components/responses/406'
'429':
$ref: 'TS29571_CommonData.yaml#/components/responses/429'
'500':
$ref: 'TS29571_CommonData.yaml#/components/responses/500'
'502':
$ref: 'TS29571_CommonData.yaml#/components/responses/502'
'503':
$ref: 'TS29571_CommonData.yaml#/components/responses/503'
default:
$ref: 'TS29571_CommonData.yaml#/components/responses/default'
patch:
summary: Partial update an existing Individual Inference Subscription
operationId: PartialUpdateInferenceSubcription
tags:
- Individual Inference Subscription (Document)
requestBody:
required: true
content:
application/merge-patch+json:
schema:
$ref: '#/components/schemas/InferEventSubscPatch'
parameters:
- name: subscriptionId
in: path
description: String identifying a subscription to the Naf_Inference Service.
required: true
schema:
type: string
responses:
'200':
description: >
The Individual Inference Subscription resource was partial
modified successfully and a representation of that resource is returned.
content:
application/json:
schema:
$ref: '#/components/schemas/InferEventSubsc'
'204':
description: >
The Individual Inference Subscription resource was partial
modified successfully.
'307':
$ref: 'TS29571_CommonData.yaml#/components/responses/307'
'308':
$ref: 'TS29571_CommonData.yaml#/components/responses/308'
'400':
$ref: 'TS29571_CommonData.yaml#/components/responses/400'
'401':
$ref: 'TS29571_CommonData.yaml#/components/responses/401'
'403':
$ref: 'TS29571_CommonData.yaml#/components/responses/403'
'404':
$ref: 'TS29571_CommonData.yaml#/components/responses/404'
'406':
$ref: 'TS29571_CommonData.yaml#/components/responses/406'
'429':
$ref: 'TS29571_CommonData.yaml#/components/responses/429'
'500':
$ref: 'TS29571_CommonData.yaml#/components/responses/500'
'502':
$ref: 'TS29571_CommonData.yaml#/components/responses/502'
'503':
$ref: 'TS29571_CommonData.yaml#/components/responses/503'
default:
$ref: 'TS29571_CommonData.yaml#/components/responses/default'
delete:
summary: Delete an existing Individual Inference Subscription.
operationId: DeleteInferenceSubcription
tags:
- Individual Inference Subscription (Document)
parameters:
- name: subscriptionId
in: path
description: >
String identifying a subscription to the Naf_Inference Service.
required: true
schema:
type: string
responses:
'204':
description: >
No Content. The Individual Inference Subscription matching the
subscriptionId was deleted.
'307':
$ref: 'TS29571_CommonData.yaml#/components/responses/307'
'308':
$ref: 'TS29571_CommonData.yaml#/components/responses/308'
'400':
$ref: 'TS29571_CommonData.yaml#/components/responses/400'
'401':
$ref: 'TS29571_CommonData.yaml#/components/responses/401'
'403':
$ref: 'TS29571_CommonData.yaml#/components/responses/403'
'404':
$ref: 'TS29571_CommonData.yaml#/components/responses/404'
'429':
$ref: 'TS29571_CommonData.yaml#/components/responses/429'
'500':
$ref: 'TS29571_CommonData.yaml#/components/responses/500'
'502':
$ref: 'TS29571_CommonData.yaml#/components/responses/502'
'503':
$ref: 'TS29571_CommonData.yaml#/components/responses/503'
default:
$ref: 'TS29571_CommonData.yaml#/components/responses/default'
components:
securitySchemes:
oAuth2ClientCredentials:
type: oauth2
flows:
clientCredentials:
tokenUrl: '{nrfApiRoot}/oauth2/token'
scopes:
naf-inference: Access to the Naf_Inference API
schemas:
InferEventSubsc:
description: Represents an Inference subscription.
type: object
properties:
notifCorreId:
type: string
description: >
String identifying the Notification Correlation ID in the corresponding notification.
notifUri:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Uri'
suppFeats:
$ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures'
inferAnaSubs:
type: object
additionalProperties:
$ref: '#/components/schemas/InferAnaSub'
minItems: 1
description: >
Represents inference subscription per analytics Id. The key of the map shall
be set to the value of the "anaEvent" attribute in the InferAnaSub data
structure.
inferResults:
type: array
items:
$ref: '#/components/schemas/InferResult'
minItems: 1
description: Represents Inference result.
reportInfo:
$ref: 'TS29523_Npcf_EventExposure.yaml#/components/schemas/ReportingInformation'
required:
- notifUri
- notifCorreId
- inferAnaSubs
InferNotif:
description: Represents notifications on events that occurred.
type: object
properties:
notifCorreId:
type: string
description: >
String identifying the Notification Correlation ID in the corresponding notification.
inferResults:
type: array
items:
$ref: '#/components/schemas/InferResult'
minItems: 1
description: Represents inference results.
required:
- notifCorreId
- inferResults
InferEventSubscPatch:
description: Represents parameters to request the modification of an Inference subscription.
type: object
properties:
notifUri:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Uri'
notifCorreId:
type: string
description: >
String identifying the Notification Correlation ID in the corresponding notification.
inferAnaSubs:
type: object
additionalProperties:
$ref: '#/components/schemas/InferAnaSub'
minItems: 1
description: >
Represents inference subscription per analytics Id. The key of the map shall
be set to the value of the "anaEvent" attribute in the InferAnaSub data
structure.
reportInfo:
$ref: 'TS29523_Npcf_EventExposure.yaml#/components/schemas/ReportingInformation'
InferAnaSub:
description: Represents a subscription to a single event.
type: object
properties:
anaEvent:
$ref: 'TS29520_Nnwdaf_EventsSubscription.yaml#/components/schemas/NwdafEvent'
exterGroupIds:
type: array
items:
$ref: 'TS29571_CommonData.yaml#/components/schemas/ExternalGroupId'
minItems: 1
gpsis:
type: array
items:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Gpsi'
minItems: 1
intGroupIds:
type: array
items:
$ref: 'TS29571_CommonData.yaml#/components/schemas/GroupId'
minItems: 1
supis:
type: array
items:
$ref: 'TS29571_CommonData.yaml#/components/schemas/Supi'
minItems: 1
eventFilter:
$ref: 'TS29520_Nnwdaf_AnalyticsInfo.yaml#/components/schemas/EventFilter'
anaMeta:
type: array
items:
$ref: 'TS29520_Nnwdaf_EventsSubscription.yaml#/components/schemas/AnalyticsMetadata'
minItems: 1
dataStatProps:
type: array
items:
$ref: 'TS29520_Nnwdaf_EventsSubscription.yaml#/components/schemas/DatasetStatisticalProperty'
minItems: 1
timeWindows:
type: array
items:
$ref: 'TS29122_CommonData.yaml#/components/schemas/TimeWindow'
minItems: 1
resTime:
$ref: 'TS29571_CommonData.yaml#/components/schemas/DateTime'
required:
- anaEvent
oneOf:
- required: [exterGroupIds]
- required: [gpsis]
- required: [intGroupIds]
- required: [supis]
InferResult:
description: Represents Inference result per target UE.
type: object
properties:
inferRes:
$ref: 'TS29520_Nnwdaf_EventsSubscription.yaml#/components/schemas/EventNotification'
vflNotOnTimeInd:
$ref: 'TS29520_Nnwdaf_MLModelTraining.yaml#/components/schemas/DelayEventNotif'
termCause:
$ref: 'TS29520_Nnwdaf_VFLInference.yaml#/components/schemas/VflTermCause'
oneOf:
- required: [inferRes]
- required: [termCause]
- required: [vflNotOnTimeInd]
#
# ENUMERATIONS DATA TYPES
#
Annex B (informative):
Withdrawn API versions
B.1 General
This Annex lists withdrawn API versions of the APIs defined in the present specification. Clause 4.3.1.6 of 3GPP TS 29.501 [5] describes the withdrawal of API versions.
B.2 Naf_VFLTraining API
The API versions listed in table B.2-1 are withdrawn for the Naf_VFLTraining API.
Table B.2-1: Withdrawn API versions of the Naf_VFLTraining service
API version number
Remarks
B.3 Naf_VFLInference API
The API versions listed in table B.3-1 are withdrawn for the Naf_VFLInference API.
Table B.3-1: Withdrawn API versions of the Naf_VFLInference service
API version number
Remarks
B.4 Naf_Training API
The API versions listed in table B.4-1 are withdrawn for the Naf_Training API.
Table B.4-1: Withdrawn API versions of the Naf_Training service
API version number
Remarks
B.5 Naf_Inference API
The API versions listed in table B.5-1 are withdrawn for the Naf_Inference API.
Table B.5-1: Withdrawn API versions of the Naf_Inference service
API version number
Remarks
Annex C (normative):
ABNF grammar for 3GPP SBI HTTP custom headers
C.1 General
This Annex contains a self-contained set of ABNF rules, comprising the re-used rules from IETF RFCs, and the rules defined by the 3GPP custom headers defined in this specification (see clause 6.x.y.z).
This grammar may be used as input to existing tools to help implementations to parse 3GPP custom headers.
Annex D (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-08
CT3#142
C3-253650
Inclusion of agreed pCRs C3-253362, C3-253363, C3-253544,
C3-253546, C3-253547, C3-253548, C3-253549, C3-253550,
C3-253551, C3-253552, C3-253636, C3-253637, C3-253638
0.1.0
2025-09
CT#109
CP-252068
Presentation to TSG CT for information
1.0.0
2025-10
CT#143
C3-254474
Inclusion of agreed pCRs C3-254367, C3-254127, C3-254556,
C3-254384, C3-254369, C3-254269, C3-254386
1.1.0
2025-11
CT#144
C3-255656
Inclusion of agreed pCRs C3-255159, C3-255358, C3-255404,
C3-255405, C3-255504, C3-255507, C3-255508, C3-255526, C3-255527, C3-255602, C3-255635, C3-255636, C3-255647, C3-255654
1.2.0
2025-12
CT#110
CP-253020
Presentation to TSG CT for approval
2.0.0
2025-12
CT#110
CP-253020
Approved by TSG CT
19.0.0
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 1 Scope
| The present document specifies the Radio Frequency (RF) test methods and conformance requirements for Ambient IoT Base Station (BS) and Carrier-Wave (CW) node. These have been derived from, and are consistent with the conducted requirements in specification defined in TS 38.194 [23].
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 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.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] ITU-R SM.329
[23] 3GPP TS 38.194: "NR Ambient IoT Base Station (BS) and Carrier-Wave (CW) node radio transmission and reception"
[4] ITU-R M.1545
…
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 3 Definitions of terms, symbols and abbreviations
| This clause and its three (sub) clauses are mandatory. The contents shall be shown as "void" if the TS/TR does not define any terms, symbols, or abbreviations.
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 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].
Definition format (Normal)
<defined term>: <definition>.
example: text used to clarify abstract rules by applying them literally.
antenna connector: connector at the conducted interface of the BS type 1-C
active transmitter unit: transmitter unit which is ON, and has the ability to send modulated data streams that are parallel and distinct to those sent from other transmitter units to a BS type 1-C antenna connector
Base Station RF Bandwidth: RF bandwidth in which a base station transmits and/or receives single or multiple carrier(s) within a supported operating band
NOTE: In single carrier operation, the Base Station RF Bandwidth is equal to the BS channel bandwidth.
Base Station RF Bandwidth edge: frequency of one of the edges of the Base Station RF Bandwidth
basic limit: emissions limit relating to the power supplied by a single transmitter to a single antenna transmission line in ITU-R SM.329 [2] used for the formulation of unwanted emission requirements for FR1
BS channel bandwidth: RF bandwidth supporting a single A-IoT RF carrier with the transmission bandwidth configured in the uplink or downlink
NOTE 1: The BS channel bandwidth is measured in MHz and is used as a reference for transmitter and receiver RF requirements.
NOTE 2: It is possible for the BS to transmit to and/or receive from one or more UE bandwidth parts that are smaller than or equal to the BS transmission bandwidth configuration, in any part of the BS transmission bandwidth configuration.
BS type 1-C: NR base station operating at FR1 with requirements set consisting only of conducted requirements defined at individual antenna connectors
channel edge: lowest or highest frequency of the A-IoT carrier, separated by the BS channel bandwidth
maximum carrier output power: mean power level measured per carrier at the indicted interface, during the transmitter ON period in a specified reference condition
maximum total output power: mean power level measured within the operating band at the indicated interface, during the transmitter ON period in a specified reference condition
measurement bandwidth: RF bandwidth in which an emission level is specified
operating band: frequency range in which A-IoT operates (paired or unpaired), that is defined with a specific set of technical requirements
NOTE: The operating band(s) for a BS is declared by the manufacturer according to the designations in TS 38.194 [3], tables 5.1-1.
Radio Bandwidth: frequency difference between the upper edge of the highest used carrier and the lower edge of the lowest used carrier
rated carrier output power: mean power level associated with a particular carrier the manufacturer has declared to be available at the indicated interface, during the transmitter ON period in a specified reference condition
rated total output power: mean power level associated with a particular operating band the manufacturer has declared to be available at the indicated interface, during the transmitter ON period in a specified reference condition
requirement set: one of the A-IoT base station requirement's set as defined for BS type 1-C
single-band connector: antenna connector of the BS type 1-C supporting operation either in a single operating band only
transmitter OFF period: time period during which the BS transmitter is not allowed to transmit
transmitter ON period: time period during which the BS transmitter is transmitting data and/or reference symbols
transmitter transient period: time period during which the transmitter is changing from the OFF period to the ON period or vice versa
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
Symbol format (EW)
<symbol> <Explanation>
Percentage of the mean transmitted power emitted outside the occupied bandwidth on the assigned channel
BWChannel BS channel bandwidth
BWConfig Transmission bandwidth configuration, expressed in MHz, where BWConfig = NRB x SCS x 12 kHz
f Separation between the channel edge frequency and the nominal -3 dB point of the measuring filter closest to the carrier frequency
fmax f_offsetmax minus half of the bandwidth of the measuring filter
ΔFGlobal Global frequency raster granularity
ΔfOBUE Maximum offset of the operating band unwanted emissions mask from the downlink operating band edge
ΔfOOB Maximum offset of the out-of-band boundary from the uplink operating band edge
ΔFRaster Channel raster granularity
FC RF reference frequency on the channel raster
Foffset_high Frequency offset from FC_high to the upper Base Station RF Bandwidth edge, or from FC,block, high to the upper sub-block edge
Foffset_low Frequency offset from FC_low to the lower Base Station RF Bandwidth edge, or from FC,block, low to the lower sub-block edge
FDL_low The lowest frequency of the downlink operating band
FDL_high The highest frequency of the downlink operating band
Ffilter Filter centre frequency
Foffset Frequency offset from FC_high to the upper Base Station RF Bandwidth edge, or FC_low to the lower Base Station RF Bandwidth edge.
f_offset Separation between the channel edge frequency and the centre of the measuring filter
f_offsetmax The offset to the frequency ΔfOBUE outside the downlink operating band
FREF RF reference frequency
FDL_low The lowest frequency of the downlink operating band
FDL_high The highest frequency of the downlink operating band
FUL_low The lowest frequency of the uplink operating band
FUL_high The highest frequency of the uplink operating band
GBChannel Minimum guard band defined in TS 38.194 [3] clause 5.3.1.3
Iuant gNB internal logical interface between the implementation specific O&M function and the RET antennas and TMAs control unit function of the gNB
NRB Transmission bandwidth configuration, expressed in resource blocks
NREF NR Absolute Radio Frequency Channel Number (NR-ARFCN)
Pmax,c,AC Maximum carrier output power measured per antenna connector
Prated,c,AC The rated carrier output power per antenna connector
Prated,t,AC The rated total output power declared at the antenna connector
PREFSENS Conducted Reference Sensitivity power level
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 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 format (EW)
<ABBREVIATION> <Expansion>
ACLR Adjacent Channel Leakage Ratio
ACS Adjacent Channel Selectivity
AWGN Additive White Gaussian Noise
BS Base Station
BW Bandwidth
CP-OFDM Cyclic Prefix-OFDM
CW Continuous Wave
CW Carrier Wave
CW2D Carrier-wave, or carrier-wave node, to device
D2R Device to reader
FR Frequency Range
FRC Fixed Reference Channel
OOK On-off keying
GSCN Global Synchronization Channel Number
ITU‑R Radiocommunication Sector of the International Telecommunication Union
LNA Low Noise Amplifier
MR Medium Range
NR-ARFCN NR Absolute Radio Frequency Channel Number
OBUE Operating Band Unwanted Emissions
R2D Reader to device
RB Resource Block
REFSENS Reference Sensitivity
RF Radio Frequency
RMS Root Mean Square (value)
RS Reference Signal
RX Receiver
SCS Sub-Carrier Spacing
TX Transmitter
TT Test Tolerance
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4 General conducted test conditions and declarations
| |
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.1 Measurement uncertainties and test requirements
| |
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.1.1 General
| The requirements of this clause apply to all applicable tests in this specification, i.e. to all conducted tests defined for FR1. The frequency ranges FR1 are defined in clause 5.1 of TS 38.194 [3].
The minimum requirements are given in TS 38.194 [3] and the references therein. Test Tolerances for the conducted test requirements explicitly stated in the present document are given in annex C of the present document.
Test Tolerances are individually calculated for each test. The Test Tolerances are used to relax the minimum requirements to create test requirements.
When a test requirement differs from the corresponding minimum requirement, then the Test Tolerance applied for the test is non-zero. The Test Tolerance for the test and the explanation of how the minimum requirement has been relaxed by the Test Tolerance are given in annex C.
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.1.2 Acceptable uncertainty of Test System
| |
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.1.2.1 General
| The maximum acceptable uncertainty of the Test System is specified below for each test defined explicitly in the present specification, where appropriate. The maximum acceptable uncertainty of the Test System for test requirements included by reference is defined in the respective referred test specification.
The Test System shall enable the stimulus signals in the test case to be adjusted to within the specified tolerance and the equipment under test to be measured with an uncertainty not exceeding the specified values. All tolerances and uncertainties are absolute values, and are valid for a confidence level of 95 %, unless otherwise stated.
A confidence level of 95 % is the measurement uncertainty tolerance interval for a specific measurement that contains 95 % of the performance of a population of test equipment.
For RF tests, it should be noted that the uncertainties in clause 4.1.2 apply to the Test System operating into a nominal 50 ohm load and do not include system effects due to mismatch between the DUT and the Test System.
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.1.2.2 Measurement of transmitter
| Table 4.1.2.2-1: Maximum Test System uncertainty for transmitter tests
Clause
Maximum Test System Uncertainty
Derivation of Test System Uncertainty
6.2 Base Station output power
±0.7 dB, f ≤ 3 GHz
6.3.1 Transmit OFF power
±2.0 dB, f ≤ 3 GHz
6.3.2 Transmitter transient period
N/A
6.4.2 Frequency error
± 12 Hz
6.4.3 Modulation quality
± 1%
6.5.2 Occupied bandwidth
±2 kHz
6.5.3 Adjacent Channel Leakage power Ratio (ACLR)
ACLR: ±0.8 dB
6.5.4 Operating band unwanted emissions
±1.5 dB, f ≤ 3 GHz
6.5.5.5.1.1 Transmitter spurious emissions, Mandatory Requirements
9 kHz < f ≤ 4 GHz: ±2.0 dB
4 GHz < f ≤ 19 GHz: ±4.0 dB
19 GHz < f ≤ 26 GHz: ±4.5 dB
6.5.5.5.1.2 Transmitter spurious emissions, Protection of BS receiver
±3.0 dB
6.5.5.5.1.3 Transmitter spurious emissions, Additional spurious emission requirements
±2.0 dB for > -60 dBm, f ≤ 3 GHz
±2.5 dB, 3 GHz < f ≤ 4.2 GHz
±3.0 dB, 4.2 GHz < f ≤ 7.125 GHz (Note)
±3.0 dB for ≤ -60 dBm, f ≤ 3 GHz
±3.5 dB, 3 GHz < f ≤ 4.2 GHz
±4.0 dB, 4.2 GHz < f ≤ 7.125 GHz (Note)
6.5.5.2.4 Transmitter spurious emissions, Co-location
±3.0 dB
NOTE: Test system uncertainty values for 3 GHz < f ≤ 7.125 GHz apply for BS operates in licensed spectrum only.
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.1.2.3 Measurement of receiver
| Table 4.1.2.3-1: Maximum Test System Uncertainty for receiver tests
Clause
Maximum Test System Uncertainty
Derivation of Test System Uncertainty
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 7.2 Reference sensitivity level
| |
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.1.3 Interpretation of measurement results
| The measurement results returned by the Test System are compared - without any modification - against the test requirements as defined by the Shared Risk principle.
The Shared Risk principle is defined in Recommendation ITU-R M.1545 [4].
The actual measurement uncertainty of the Test System for the measurement of each parameter shall be included in the test report.
The recorded value for the Test System uncertainty shall be, for each measurement, equal to or lower than the appropriate figure in clause 4.1.2 of the present document.
If the Test System for a test is known to have a measurement uncertainty greater than that specified in clause 4.1.2, it is still permitted to use this apparatus provided that an adjustment is made as follows.
Any additional uncertainty in the Test System over and above that specified in clause 4.1.2 shall be used to tighten the test requirement, making the test harder to pass. For some tests e.g. receiver tests, this may require modification of stimulus signals. This procedure will ensure that a Test System not compliant with clause 4.1.2 does not increase the chance of passing a device under test where that device would otherwise have failed the test if a Test System compliant with clause 4.1.2 had been used.
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.2 Regional requirements
| Some requirements in the present document may only apply in certain regions either as optional requirements, or as mandatory requirements set by local and regional regulation. It is normally not stated in the 3GPP specifications under what exact circumstances the regional requirements apply, since this is defined by local or regional regulation.
Table 4.42-1 lists all requirements in the present specification that may be applied differently in different regions.
Table 4.42-1: List of regional requirements
Clause number
Requirement
Comments
5
Operating bands
Some A-IoT operating bands may be applied regionally.
6.2.1
Base station output power
Additional output power limits may be applied regionally.
6.5.2
Occupied bandwidth
The requirement may be applied regionally. There may also be regional requirements to declare the occupied bandwidth according to the definition in present specification.
6.5.3.5.3
Adjacent Channel Leakage Power Ratio
For Band n41 and n90 operation in Japan, absolute ACLR limits shall be applied to the sum of the absolute ACLR power over all antenna connectors for BS type 1-C.
6.5.4.5
Operating band unwanted emission
Category A or Category B operating band unwanted emission limits may be applied regionally.
For operation with shared spectrum channel access, the BS may have to comply with the applicable BS power limits established regionally, when deployed in regions where those limits apply and under the conditions declared by the manufacturer.
6.5.4.5.6.1
Operating band unwanted emissions:
Limits in FCC Title 47
The BS may have to comply with the additional requirements, when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer.
6.5.4.5.6.2
Operating band unwanted emission
Protection of DTT
The BS operating in Band n20 may have to comply with the additional requirements for protection of DTT, when deployed in certain regions.
6.5.4.5.7
Operating band unwanted emission,
For Band n41 and n90 operation in Japan, the operating band unwanted emissions limits shall be applied to the sum of the emission power over all antenna connectors for BS type 1-C.
6.5.5.5.1.1
Transmitter spurious emissions
Category A or Category B spurious emission limits, as defined in ITU-R Recommendation SM.329 [2], may apply regionally.
The emission limits for BS type 1-H specified as the basic limit + X (dB) are applicable, unless stated differently in regional regulation.
In addition, for operation with shared spectrum channel access, the BS may have to comply with the applicable spurious emission limits established regionally, when deployed in regions where those limits apply and under the conditions declared by the manufacturer.
6.5.5.5.1.3
Transmitter spurious emissions: additional requirements
These requirements may be applied for the protection of system operating in frequency ranges other than the BS operating band.
6.5.5.5.3
Transmitter spurious emissions
For Band n41 and n90 operation in Japan, the sum of the spurious emissions over all antenna connectors for BS type 1-C shall not exceed the basic limits.
7.5.5.2,
7.5.5.3
Receiver spurious emissions
The emission limits for BS type 1-H specified as the basic limit + X (dB) are applicable, unless stated differently in regional regulation.
For Band n41 and n90 operation in Japan, the sum of RX spurious emissions over all antenna connectors for BS type 1-C shall not exceed basic limits
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.3 BS configurations
| |
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.3.1 BS type 1-C
| |
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.3.1.1 Transmit configurations
| |
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.3.1.1.1 General
| Unless otherwise stated, the transmitter characteristics in clause 6 are specified at the BS antenna connector (test port A) with a full complement of transceivers for the configuration in normal operating conditions. If any external apparatus such as a TX amplifier, a filter or the combination of such devices is used, requirements apply at the far end antenna connector (test port B).
Figure 4.3.1.1.1-1: Transmitter test ports
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.3.1.1.2 Transmission with multiple transmitter antenna connectors
| Unless otherwise stated, for the tests in clause 6 of the present document, the requirement applies for each transmitter antenna connector in the case of transmission with multiple transmitter antenna connectors.
Transmitter requirements are tested at the antenna connector, with the remaining antenna connector(s) being terminated. If the manufacturer has declared the transmitter paths to be equivalent (D.32), it is sufficient to measure the signal at any one of the transmitter antenna connectors.
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.3.1.2 Receive configurations
| |
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.3.1.2.1 General
| Unless otherwise stated, the receiver characteristics in clause 7 are specified at the BS antenna connector (test port A) with a full complement of transceivers for the configuration in normal operating conditions. If any external apparatus such as a RX amplifier, a filter or the combination of such devices is used, requirements apply at the far end antenna connector (test port B).
Figure 4.3.1.2.1-1: Receiver test ports
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.3.1.2.2 Reception with multiple receiver antenna connectors, receiver diversity
| For the tests in clause 7 of the present document, the requirement applies at each receiver antenna connector for receivers with antenna diversity or in the case of multi-carrier reception with multiple receiver antenna connectors.
Receiver requirements are tested at the antenna connector, with the remaining receiver(s) disabled or their antenna connector(s) being terminated. If the manufacturer has declared the receiver paths to be equivalent (D.32), it is sufficient to apply the specified test signal at any one of the receiver antenna connectors.
For a BS type 1-C supporting multi-band operation, multi-band tests for ACS, blocking and intermodulation are performed with the interferer(s) applied to each antenna connector mapped to the receiver for the wanted signal(s), however only to one antenna connector at a time. Antenna connectors to which no signals are applied are terminated.
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.3.1.3 Duplexers
| The requirements of the present document shall be met with a duplexer fitted, if a duplexer is supplied as part of the BS. If the duplexer is supplied as an option by the manufacturer, sufficient tests should be repeated with and without the duplexer fitted to verify that the BS meets the requirements of the present document in both cases.
The following tests shall be performed with the duplexer fitted, and without it fitted if this is an option:
1) clause 6.2, base station output power, for the highest static power step only, if this is measured at the antenna connector;
2) clause 6.6, unwanted emissions; outside the BS transmit band;
3) clause 6.6.5.5.1.2, protection of the BS receiver;
4) clause 6.7, transmit intermodulation; for the testing of conformance, the carrier frequencies should be selected to minimize intermodulation products from the transmitters falling in receive channels.
The remaining tests may be performed with or without the duplexer fitted.
NOTE 1: When performing receiver tests with a duplexer fitted, it is important to ensure that the output from the transmitters does not affect the test apparatus. This can be achieved using a combination of attenuators, isolators and filters.
NOTE 2: When duplexers are used, intermodulation products will be generated, not only in the duplexer but also in the antenna system. The intermodulation products generated in the antenna system are not controlled by 3GPP specifications, and may degrade during operation (e.g. due to moisture ingress). Therefore, to ensure continued satisfactory operation of a BS, an operator will normally select NR-ARFCNs to minimize intermodulation products falling on receive channels. For testing of complete conformance, an operator may specify the NR-ARFCNs to be used.
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.3.1.4 Power supply options
| If the BS is supplied with a number of different power supply configurations, it may not be necessary to test RF parameters for each of the power supply options, provided that it can be demonstrated that the range of conditions over which the equipment is tested is at least as great as the range of conditions due to any of the power supply configurations.
This applies particularly if a BS contains a DC rail which can be supplied either externally or from an internal mains power supply. In this case, the conditions of extreme power supply for the mains power supply options can be tested by testing only the external DC supply option. The range of DC input voltages for the test should be sufficient to verify the performance with any of the power supplies, over its range of operating conditions within the BS, including variation of mains input voltage, temperature and output current.
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.3.1.5 Ancillary RF amplifiers
| The BS type 1-C requirements of the present document shall be met with the ancillary RF amplifier fitted. At tests according to clauses 6 and 7 for TX and RX respectively, the ancillary amplifier is connected to the BS by a connecting network (including any cable(s), attenuator(s), etc.) with applicable loss to make sure the appropriate operating conditions of the ancillary amplifier and the BS. The applicable connecting network loss range is declared by the manufacturer (D.35). Other characteristics and the temperature dependence of the attenuation of the connecting network are neglected. The actual attenuation value of the connecting network is chosen for each test as one of the applicable extreme values. The lowest value is used unless otherwise stated.
Sufficient tests should be repeated with the ancillary amplifier fitted and, if it is optional, without the ancillary RF amplifier to verify that the BS meets the requirements of the present document in both cases.
When testing, the following tests shall be repeated with the optional ancillary amplifier fitted according to the table below, where "x" denotes that the test is applicable:
Table 4.3.1.5-1: Tests applicable to ancillary RF amplifiers
Clause
TX amplifier only
RX amplifier only
TX/RX amplifiers combined (Note 1, 2)
Receiver tests
7.2
x
x
7.4
x
x
7.5
x
x
7.6
x
Transmitter tests
6.2
x
x
6.5.2
x
x
6.5.3
x
x
6.5.4
x
x
6.5.5
x
x
NOTE 1: Combining can be by duplex filters or any other network. The amplifiers can either be in RX or TX branch or in both. Either one of these amplifiers could be a passive network.
NOTE 2: Unless otherwise stated, BS with both TX and RX amplifiers are tested once with both amplifiers active for each test.
In base station output power test (clause 6.2) and reference sensitivity level test (clause 7.2) highest applicable attenuation value is applied.
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.4 Manufacturer declarations
| The following BS declarations listed in table 4.64-1, when applicable to the BS under test, are required to be provided by the manufacturer for the conducted requirements testing of the BS type 1-C.
Table 4.64-1 Manufacturer declarations for BS type 1-C conducted test requirements
Declaration identifier
Declaration
Description
BS type 1-C
D.1
BS requirements set
Declaration of one of the A-IoT base station requirement's set as defined for BS type 1-C.
x
D.3
Operating bands and frequency ranges
List of A-IoT operating band(s) supported by single-band connector(s) and/or multi-band connector(s) of the BS and if applicable, frequency range(s) within the operating band(s) that the BS can operate in.
Declarations shall be made per antenna connector for BS type 1-C.
x
D.4
Spurious emission category
Declare the BS spurious emission category as either category A or B with respect to the limits for spurious emissions, as defined in Recommendation ITU-R SM.329 [2].
x
D.5
Additional operating band unwanted emissions
The manufacturer shall declare whether the BS under test is intended to operate in geographic areas where the additional operating band unwanted emission limits defined in clause 6.6.4.5.6 apply.
x
D.6
Co-existence with other systems
The manufacturer shall declare whether the BS under test is intended to operate in geographic areas where one or more of the systems GSM850, GSM900, DCS1800, PCS1900, UTRA FDD, UTRA TDD, E-UTRA, PHS and/or NR operating in another band are deployed.
x
D.7
Co-location with other base stations
The manufacturer shall declare whether the BS under test is intended to operate co-located with Base Stations of one or more of the systems GSM850, GSM900, DCS1800, PCS1900, UTRA FDD, UTRA TDD, E-UTRA and/or NR operating in another band.
x
D.11
Maximum Base Station RF Bandwidth
Maximum Base Station RF Bandwidth in the operating band for single-band operation. Declared per supported operating band, per antenna connector for BS type 1-C.
x
D.14
A-IoT supported channel bandwidths and SCS
A-IoT supported SCS and channel bandwidths per supported SCS. Declared per supported operating band, per antenna connector for BS type 1-C.
x
D.21
Rated carrier output power (Prated,c,AC)
Conducted rated carrier output power, per single band connector.
Declared per supported operating band, per antenna connector for BS type 1-C.
x
D.22
Rated total output power (Prated,t,AC)
Conducted total rated output power.
Declared per supported operating band, per antenna connector for BS type 1-C.
x
D.32
Equivalent connectors
List of antenna connectors of BS type 1-C, which have been declared equivalent.
Equivalent connectors imply that the antenna connector of BS type 1-C, are expected to behave in the same way when presented with identical signals under the same operating conditions. All declarations made for the antenna connector of BS type 1-C, are identical and the transmitter unit and/or receiver unit driving the antenna connector of BS type 1-C are of identical design.
x
D.35
Connecting network loss range for BS testing with ancillary RF amplifiers
Declaration of the range of connecting network losses (in dB) for BS type 1-C testing with ancillary Tx RF amplifier only, or with Rx RF amplifier only, or with combined Tx/Rx RF amplifiers.
x
NOTE 5: This manufacturer may declare two values, one with a minimum of +6dB and the other with a minimum of +3dB.
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.5 Test configurations
| |
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.5.1 General
| The test configurations shall be constructed using the methods defined below, subject to the parameters declared by the manufacturer for the supported RF configurations as listed in clause 4.6. The test configurations to use for conformance testing are defined for each supported RF configuration in clauses 4.8.3 and 4.8.4.
The applicable test models for generation of the carrier transmit test signal are defined in clause 4.9.
NOTE: If required, carriers are shifted to align with the channel raster.
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.5.2 Test signal used to build Test Configurations
| The signal's channel bandwidth and subcarrier spacing used to build A-IoT Test Configurations shall be selected according to table 4.5.2-1.
Table 4.5.2-1: Signal to be used to build A-IoT TCs
TC signal
R2D channel BWchannel
200kHz
(Note 1)
400kHz
(Note 1)
600 kHz
(Note 1)
800 kHz
(Note 1)
characteristics
Subcarrier spacing
15kHz
NOTE 1: If this channel bandwidth is not supported, the narrowest supported channel bandwidth shall be used.
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.5.3 ATC1: Single carrier operation
| A-IoT support only single carrier operation. Test configuration can be as follows:
The purpose of the TC1 is to test A-IoT R2D carrier aspects.
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.5.3.1 ATC1 generation
| ATC1 is constructed using the following method:
- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth.
- Place an A-IoT R2D carrier within the Base Station RF Bandwidth.
- Set the power of A-IoT R2D carrier to the rated output power Prated,c,AC according to the manufacturer’s declaration.
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.6 Applicability of requirements
| |
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.6.1 General
| |
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.6.2 Requirement set applicability
| In table 4.6.2-1, the requirement applicability for each requirement set is defined. For each requirement, the applicable requirement clause in the specification is identified.
Table 4.6.2-1: Requirement set applicability
Requirement
1-C
BS output power
6.2
Transmit ON/OFF power
6.3
Transmitted signal quality
6.4
Occupied bandwidth
6.5.2
ACLR
6.5.3.5.3
Operating band unwanted
emissions
6.5.4.5.7
Transmitter spurious emissions
6.5.5.5.3
Reference sensitivity level
7.2
In-band selectivity and blocking
7.3
Out-of-band blocking
7.4
Receiver spurious emissions
7.5.5.2
Receiver intermodulation
7.6
Performance requirements
[ ]
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.6.3 Applicability of test configurations for single-band operation
| The applicable test configurations are specified in the tables below for each the supported RF configuration, which shall be declared according to clause 4.6. The generation and power allocation for each test configuration is defined in clause 4.7. This clause contains the test configurations for a BS capable of single carrier, in single band.
For a BS declared to be capable of single carrier operation only (D.16), a single carrier (SC) shall be used for testing.
Unless otherwise stated, single carrier configuration (SC) tests shall be performed using signal with narrowest supported channel bandwidth and the smallest supported sub-carrier spacing.
Table 4.6.3-1: Test configurations for a BS capable of single-carrier in a single band
BS test case
Contiguous spectrum capable BS
Base station output power
ATC1
Transmit ON/OFF power
ATC1
Frequency error
Occupied bandwidth
ATC1
Adjacent Channel Leakage power Ratio (ACLR)
ATC1
Operating band unwanted emissions
ATC1
Transmitter spurious emissions
ATC1
Reference sensitivity level
Adjacent Channel Selectivity (ACS)
ATC1
In-band blocking
ATC1
Out-of-band blocking
ATC1
Receiver spurious emissions
ATC1
Receiver intermodulation
ATC1
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.7 RF channels and test models
| |
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.7.1 RF channels
| For the single carrier testing many tests in this TS are performed with appropriate frequencies in the bottom, middle and top channels of the supported frequency range of the BS. These are denoted as RF channels B (bottom), M (middle) and T (top).
Unless otherwise stated, the test shall be performed with a single carrier at each of the RF channels B, M and T.
Many tests in this TS are performed with the maximum Base Station RF Bandwidth located at the bottom, middle and top of the supported frequency range in the operating band. These are denoted as BRFBW (bottom), MRFBW (middle) and TRFBW (top).
Unless otherwise stated, the test shall be performed at BRFBW, MRFBW and TRFBW defined as following:
- BRFBW: maximum Base Station RF Bandwidth located at the bottom of the supported frequency range in the operating band.
- MRFBW: maximum Base Station RF Bandwidth located in the middle of the supported frequency range in the operating band.
- TRFBW: maximum Base Station RF Bandwidth located at the top of the supported frequency range in the operating band.
Occupied bandwidth test in this TS is performed with the aggregated BS channel bandwidth located at the bottom, middle and top of the supported frequency range in the operating band. These are denoted as BBW Channel CA(bottom), MBW Channel CA (middle) and TBW Channel CA (top) for contiguous spectrum operation.
When a test is performed by a test laboratory, the position of B, M and T for single carrier, BRFBW, MRFBW and TRFBW for single band operation, BBW Channel CA, MBW Channel CA and TBW Channel CA for contiguous spectrum operation in each supported operating band, the position of BRFBW_T'RFBW and B'RFBW_TRFBW in the supported operating band combinations shall be specified by the laboratory. The laboratory may consult with operators, the manufacturer or other bodies.
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.7.2 Test models
| |
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.7.2.1 General
| The following clauses will describe the A-IoT test models needed for BS type 1-C.
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.7.2.2 FR1 test models
| The set-up of physical channels for transmitter tests shall be according to one of the A-IoT test models (A‑TM) below. A reference to the applicable test model is made within each test.
The following general parameters are used by all A-IoT test models:
- Duration is 1 radio frame (10 ms) for FDD
- The slots are numbered 0 to 102µ – 1 where µ is the numerology corresponding to the subcarrier spacing
- NRB is the maximum transmission bandwidth configuration seen in table 5.3.2-1 in TS 38.194 [3].
- Normal CP
- Virtual resource blocks of localized type
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.7.2.2.1 A-IoT test model 1.1 (A-TM1.1)
| This model shall be used for tests on:
- BS output power
- Transmit ON/OFF power
- Unwanted emissions
- Occupied bandwidth
- ACLR
- Operating band unwanted emissions
- Transmitter spurious emissions
- Transmitter intermodulation
- Receiver spurious emissions
Common physical channel parameters are defined in clause 4.7.2.2. Specific physical channel parameters for A-TM1.1 are defined in table 4.7.2.2.1-1.
Table 4.7.2.2.1-1: Specific physical channel parameters of A-TM1.1
Parameter
Value
# of PRBs PRDCH
NRB - 3
Modulation PRDCH
OOK-4
Starting RB location of PRDCH
3
Modulation of PRDCH
OOK-4
Starting RB location of PRDCH
0
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.