hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.3.6.2.7 Type: EventNotif
| Table 6.3.6.2.7-1: Definition of type EventNotif
Attribute name
Data type
P
Cardinality
Description
Applicability
event
NwdafEvent
M
1
Contains the identifier of the analytics to which the training notification is related.
vflNotOnTimeInd
DelayEventNotif
O
0..1
Contains information indicating that the... |
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.3.6.3 Simple data types and enumerations
| |
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.3.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.3.6.3.2 Simple data types
| The simple data types defined in table 6.3.6.3.2-1 shall be supported.
Table 6.3.6.3.2-1: Simple data types
Type Name
Type Definition
Description
Applicability
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.3.6.4 Data types describing alternative data types or combinations of data types
| There are no data types describing alternative data types or combinations of data types defined for this API in this release of the specification.
|
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.3.6.5 Binary data
| |
21583c06c9a14c098fd1bd4da409262a | 29.530 | 6.3.6.5.1 Binary Data Types
| Table 6.3.6.5.1-1: Binary Data Types
Name
Clause defined
Content type
|
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 H... |
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"... |
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 authori... |
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.... |
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.50... |
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... |
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 de... |
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... |
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 a... |
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 ... |
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
Id... |
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-... |
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.... |
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... |
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 ... |
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 Inform... |
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 ... |
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 notificat... |
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 correspondi... |
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
... |
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... |
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 ... |
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... |
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 author... |
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.... |
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.
-... |
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 r... |
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, ... |
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 Channe... |
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 r... |
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... |
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
±... |
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 eac... |
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 lo... |
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,... |
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) bein... |
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, re... |
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(... |
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 do... |
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 an... |
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 su... |
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
... |
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.... |
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
... |
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 declar... |
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
... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.