hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.35.4.2 attachedDeviceUpdateResponseConfirm (successful case) | This response is triggered by the AttachedDeviceUpdateRequestIndication. The SCL primitive shall comply with the following. Table 10.444: attachedDeviceUpdateResponseConfirm (successful case) SCL primitive: attachedDeviceUpdateResponseConfirm Primitive attribute Mandatory/Optional Description primitiveType M ATTACHEDDE... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.35.4.3 attachedDeviceUpdateResponseConfirm (unsuccessful case) | This response is triggered by the AttachedDeviceUpdateRequestIndication. The SCL primitive shall comply with the following. Table 10.445: attachedDeviceUpdateResponseConfirm (unsuccessful case) SCL primitive: attachedDeviceUpdateResponseConfirm Primitive attribute Mandatory/Optional Description primitiveType M ATTACHED... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.35.5.1 attachedDeviceDeleteRequestIndication | The procedure is used to delete a <attachedDevice> resource. The SCL primitive shall comply with the following. Table 10.446: Applicability of the primitive Primitive applicability Applicable interfaces mIa dIa mId Issuer N/A N/A D/GSCL Receiver N/A N/A NSCL Table 10.447: attachedDeviceDeleteRequestIndication SCL Primi... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.35.5.2 attachedDeviceDeleteResponseConfirm (successful case) | This response is triggered by the AttachedDeviceDeleteRequestIndication. The SCL primitive shall comply with the following. Table 10.448: attachedDeviceDeleteResponseConfirm (successful case) SCL primitive: attachedDeviceDeleteResponseConfirm Primitive attribute Mandatory/Optional Description primitiveType M ATTACHEDDE... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.35.5.3 attachedDeviceDeleteResponseConfirm (unsuccessful case) | This response is triggered by the AttachedDeviceDeleteRequestIndication. The SCL primitive shall comply with the following. Table 10.449: attachedDeviceDeleteResponseConfirm (unsuccessful case) SCL primitive: attachedDeviceDeleteResponseConfirm Primitive attribute Mandatory/Optional Description primitiveType M ATTACHED... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.36.3.1 notificationChannelsRetrieveRequestIndication | This primitive is used to retrieve an scls collection Resource. The SCL primitive shall comply with the following. Table 10.451: Applicability of the primitive Primitive applicability Applicable interfaces mIa dIa mId Issuer Application Application SCL Receiver Local SCL Local SCL Hosting SCL Table 10.452: notification... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.36.3.2 notificationChannelsRetrieveResponseConfirm (successful case) | Confirms the retrieval of an notificationChannels Resource. The SCL primitive shall comply with the following. Table 10.453: notificationChannelsRetrieveResponseConfirm (successful case) SCL primitive: notificationChannelsRetrieveResponseConfirm Primitive attribute Mandatory/Optional Description primitiveType M NOTIFIC... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.36.3.3 notificationChannelsRetrieveResponseConfirm (unsuccessful case) | This response is triggered by the notificationChannelsRetrieveRequestIndication. The SCL primitive shall comply with table 10.454. Table 10.454: notificationChannelsRetrieveResponseConfirm (unsuccessful case) SCL primitive: notificationChannelsRetrieveResponseConfirm Primitive attribute Mandatory/Optional Description p... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.37.2.1 notificationChannelCreateRequestIndication | This request is used to create a new <notificationChannel> resource in a Service Capability Layer. The SCL primitive shall comply with the following. Table 10.456: Applicability of the primitive Primitive applicability Applicable interfaces mIa dIa mId Issuer Application Application on D' SCL Receiver Local SCL Local S... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.37.2.2 notificationChannelCreateResponseConfirm (successful case) | It confirms the creation of a new <notificationChannel> resource in a Service Capability Layer. The SCL primitive shall comply with the following. Table 10.458: NotificationChannelCreateResponseConfirm (successful case) SCL primitive: NotificationChannelCreateResponseConfirm Primitive attribute Mandatory/Optional Descr... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.37.2.3 notificationChannelCreateResponseConfirm (unsuccessful case) | This response is triggered by the notificationChannelCreateRequestIndication primitive. The SCL primitive shall comply with the following. Table 10.459: NotificationChannelCreateResponseConfirm (unsuccessful case) SCL primitive: notificationChannelCreateResponseConfirm Primitive attribute Mandatory/Optional Description... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.37.3.1 notificationChannelRetrieveRequestIndication | This request is used for retrieving the content of an <notificationChannel> resource. The SCL primitive shall comply with the following. Table 10.460: Applicability of the primitive Primitive applicability Applicable interfaces mIa dIa mId Issuer Application Application on D' SCL Receiver local SCL Local SCL local SCL ... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.37.3.2 notificationChannelRetrieveResponseConfirm (successful case) | This response is triggered by the notificationChannelRetrieveRequestIndication primitive. The SCL primitive shall comply with the following. Table 10.462: NotificationChannelRetrieveResponseConfirm (successful case) SCL primitive: notificationChannelRetrieveResponseConfirm Primitive attribute Mandatory/Optional Descrip... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.37.3.3 notificationChannelRetrieveResponseConfirm (unsuccessful case) | This response is triggered by the NotificationChannelRetrieveRequestIndication primitive. The SCL primitive shall comply with the following. Table 10.463: NotificationChannelRetrieveResponseConfirm (unsuccessful case) SCL primitive: notificationChannelRetrieveResponseConfirm Primitive attribute Mandatory/Optional Descr... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.37.5.1 notificationChannelDeleteRequestIndication | The procedure is used to delete an <notificationChannel> resource. The SCL primitive shall comply with the following. Table 10.464: Applicability of the primitive Primitive applicability Applicable interfaces mIa dIa mId Issuer Application Application on D' SCL Receiver local SCL local SCL Hosting SCL Table 10.465: Not... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.37.5.2 notificationChannelDeleteResponseConfirm (successful case) | This response is triggered by the notificationChannelDeleteRequestIndication primitive. The SCL primitive shall comply with the following. Table 10.466: NotificationChannelDeleteResponseConfirm (successful case) SCL primitive: notificationChannelDeleteResponseConfirm Primitive attribute Mandatory/Optional Description p... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.37.5.3 notificationChannelDeleteResponseConfirm (unsuccessful case) | This response is triggered by the notificationChannelDeleteRequestIndication primitive. The SCL primitive shall comply with the following. Table 10.467: NotificationChannelDeleteResponseConfirm (unsuccessful case) SCL primitive: NotificationChannelDeleteResponseConfirm Primitive attribute Mandatory/Optional Description... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.37.6.1 notificationChannelCreateRequestIndication | A CREATE where the targetID the URI returned as the longPollingURI element in the attribute channelData of the corresponding notificationChannel resource, shall be rejected. The longPollingURI is created together with notificationChannel with channelType LONG_POLLING. The receiver shall: 1) "Create an unsuccessful Resp... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.37.6.2 notificationChannelRetrieveRequestIndication | This request is used for performing a long poll. The SCL primitive shall comply with the following. Table 10.468: Applicability of the primitive Primitive applicability Applicable interfaces mIa dIa mId Issuer Application Application on D' SCL Receiver Local SCL Local SCL local SCL ETSI ETSI TS 102 921 V1.3.1 (2014-09)... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.37.6.3 notificationChannelRetrieveResponseConfirm (successful case) | This response is triggered by the notificationChannelRetrieveRequestIndication primitive. The SCL primitive shall comply with the following. Table 10.470: notificationChannelRetrieveResponseConfirm (successful case) SCL primitive: notificationChannelRetrieveResponseConfirm Primitive attribute Mandatory/Optional Descrip... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.37.6.4 notificationChannelRetrieveResponseConfirm (unsuccessful case) | This response is triggered by the notificationChannelRetrieveRequestIndication primitive. The SCL primitive shall comply with table 10.471. Table 10.471: NotificationChannelRetrieveResponseConfirm (unsuccessful case) SCL primitive: notificationChannelRetrieveResponseConfirm Primitive attribute Mandatory/Optional Descri... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.37.6.5 notificationChannelUpdateRequestIndication | A UPDATE where the targetID the URI returned as the longPollingURI element in the attribute channelData of the corresponding notificationChannel resource, shall be rejected. The receiver shall: 1) "Create an unsuccessful ResponseConfirm" with statusCode STATUS_METHOD_NOT_ALLOWED. 2) "Send ResponseConfirm primitive". |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.37.6.6 notificationChannelDeleteRequestIndication | A DELETE where the targetID the URI returned as the longPollingURI element in the attribute channelData of the corresponding notificationChannel resource, shall be rejected. The longPollingURI shall only be deleted when the corresponding notificationChannel is deleted. The receiver shall: 1) "Create an unsuccessful Res... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.37.7.1 notificationChannelCreateRequestIndication | A UPDATE where the targetID the URI returned as the contactURI element returned in the notificationChannel resource, shall be rejected. The receiver shall: 1) "Create an unsuccessful ResponseConfirm" with statusCode STATUS_METHOD_NOT_ALLOWED. 2) "Send ResponseConfirm primitive". |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.37.7.2 notificationChannelNotifyRequestIndication | This request is used for receiving a notify request of an <notificationChannel> resource. The SCL primitive shall comply with the following. Table 10.472: Applicability of the primitive Primitive applicability Applicable interfaces mIa dIa mId Issuer Application Application SCL Receiver SCL SCL local SCL Table 10.473: ... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.37.7.3 notificationChannelNotifyResponseConfirm (successful case) | This response is triggered by the notificationChannelNotifyRequestIndication primitive. The SCL primitive shall comply with the following. Table 10.474: NotificationChannelNotifyResponseConfirm (successful case) SCL primitive: notificationChannelNotifyResponseConfirm Primitive attribute Mandatory/Optional Description p... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.37.7.4 notificationChannelRetrieveResponseConfirm (unsuccessful case) | This response is triggered by the NotificationChannelRetrieveRequestIndication primitive. The SCL primitive shall comply with the following. Table 10.475: NotificationChannelNotifyResponseConfirm (unsuccessful case) SCL primitive: notificationChannelRetrieveResponseConfirm Primitive attribute Mandatory/Optional Descrip... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.37.7.5 notificationChannelUpdateRequestIndication | A UPDATE where the targetID the URI returned as the contactURI element returned in the notificationChannel resource, shall be rejected. The receiver shall: 1) "Create an unsuccessful ResponseConfirm" with statusCode STATUS_METHOD_NOT_ALLOWED. 2) "Send ResponseConfirm primitive". |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.37.7.6 notificationChannelDeleteRequestIndication | A DELETE where the targetID the URI returned as the longPollingURI element in the attribute channelData of the corresponding notificationChannel resource, shall be rejected. The longPollingURI shall only be deleted when the corresponding notificationChannel is deleted. The receiver shall: 1) "Create an unsuccessful Res... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.37.7.7 notificationChannel statemachine | notificationChannel ACTIVE PAUSED POLLING INACTIVE entry/start T1 entry/start T2 entry/start T3 T1 GET longPollingURI/restart T1 GET longPollingURI/restart T1 [POST contactURI]/send response on longPollling req T2 POST contactURI/block waiting for poll POST contactURI/block waiting for poll Figure 10.2 ETSI ETSI TS 102... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.38.3.1 discoveryRetrieveRequestIndication | discoveryRetrieveRequestIndication is a request to perform Resource Discovery on the Hosting SCL. The request is addressed to <sclBase>/discovery of the Hosting SCL. A hosting SCL indicated in the table may be a local SCL as well. The primitive shall comply with the following. Table 10.476: Applicability of the primiti... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.38.3.2 discoveryRetrieveResponseConfirm (successful case) | DiscoveryRetrieveResponseConfirm is the response to a request to perform resource discovery in an SCL. A successful case is a case where the discovery procedure was successfully completed, regardless of whether or not a resource matching the filer criteria was discovered. The SCL primitive shall comply with the followi... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.38.3.3 discoveryRetrieveResponseConfirm (unsuccessful case) | This is in response to a request to perform resource discovery in an SCL. An unsuccessful case is a case where the discovery procedure was not successfully completed. The SCL primitive shall comply with the following. Table 10.480: DiscoveryRetrieveResponseConfirm (unsuccessful case) SCL primitive: discoveryRetrieveRes... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.39.5.1 DELETE method (remove an attribute or part of an attribute) | PartialAccessor addresses an attribute In this case the statusCode as shown in the table below shall be returned. The response shall not include a representation. Table 10.481: StatusCodes in partial delete response for attributes Presence in update request Presence in response statusCode Action M *any value* STATUS_ME... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 10.39.5.2 UPDATE method (update an attribute or part of an attribute) | General In the update, the request shall include the new representation of the attribute or element. PartialAccessor addresses an attribute The hosting SCL shall check if the provided value is acceptable according to internal policies. If the value is accepted, the server shall use the provided value in the resource re... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 11.1 Assumptions | The data types described in the present clause are based on sequences of characters, referred as "characters" in the following data type descriptions. Different character encodings are supported. The character-encoding may be UTF-8 or UTF-16. The minimum size of data types is of one character. The maximum size of data ... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 11.2 Basic data types | The M2M system shall support Resources and mIa, dIa and mId reference points according to the following basic data types derived by XSD definitions defined in annex B. The type and values shall be supported according to the description given in table 11.1. Table 11.1: Basic data types TypeName xsd type Examples Descrip... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 11.3 Enumeration types | The M2M system shall support the following enumeration data types. Table 11.2: Enumeration types TypeName Values Description CmdType Predefined values: "RESET" "REBOOT" "UPLOAD" "DOWNLOAD" "SCHEDULEDOWNLOAD" "SCHEDULEINFORM" "SCHEDULEDUCHANGE" Enumeration of the type of management commands ChannelType Predefined values... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 11.4 Complex data types | The M2M system shall support the following complex data types derived by data types as described in clause 2.3. Content Content of a content instance. This shall be coded in two ways. • as a base64Binary with a contentType attribute: - This is used in the canonical XML representation of the contentInstance resource. - ... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 11.5 Resource Attributes | The M2M system shall support the following Attributes. The type and values shall be supported according to the description given in table 11.36. The default column specifies the default value of the attribute as set by hosting SCL in the resource representation, if the CREATE or UPDATE request did not include a value f... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 11.6 Primitive Attributes | The M2M system shall support the following primitive Attributes. The type and values shall be supported according to the description given in table 11.38. Table 11.38: Primitive attributes Name Type Default Description requestingEntity AnyURI In case the issuer is an SCL, this shall be the URI of the <scl> resource. Th... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 12 Security Message Definitions | |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 12.1 PANA AVPs | Following vendor-specific PANA AVPs are defined in the present document. These AVPs shall include the Vendor-Id field in the AVP header and set its value to 13019 (IANA-assigned Private Enterprise Number for ETSI). |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 12.1.1 M2M-Usage-Type AVP | Table 12.1: M2M-Usage-Type AVP Description This AVP indicates the context of the PANA message Value type Enumerated Value One-octet enumeration with the following values: 1 = "M2M Bootstrapping" 2 = "M2M Erase" 3 = "M2M Connection Setup" 4 = "M2M Connection Tear-down" 0, and 5 to 255 = Reserved for future use |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 12.1.2 M2M-Bootstrap-Result AVP | Table 12.2: M2M- Bootstrap-Result AVP Description This AVP indicates the result of bootstrap procedure Value type Enumerated Value One-octet enumeration with the following values: 0 = "Success" 1 = "Failure" 2 to 255 = Reserved for future use. NOTE: Value 0 ("Success") shall not be used if the PANA Result-Code AVP indi... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 12.1.3 M2M-Connection-Result AVP | Table 12.3: M2M-Connection-Result AVP Description This AVP indicates the result of connection procedure Value type Enumerated Value One-octet enumeration with the following values: 0 = "Success" 1 = "Failure" 2 to 255 = Reserved for future use NOTE: Value 0 ("Success") shall not be used if the PANA Result-Code AVP indi... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 12.1.4 M2M-Node-ID AVP | Table 12.4: M2M-Node-ID AVP Description This AVP carries an M2M Node Identifier value Value type Binary Value 16-octet value ETSI ETSI TS 102 921 V1.3.1 (2014-09) 324 |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 12.1.5 M2M-MSBF-ID AVP | Table 12.5: M2M-MSBF-ID AVP Description This AVP carries an MSBF Identifier value. Value type Variable Value Type-specific value according to the following one-octet Types: 0 = "FQDN". Type field followed by the FQDN value (a NULL-terminating String) 1 = "IPv4 address". Type field followed by IPv4 address value (Unsign... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 12.1.6 M2M-NSCL-ID AVP | Table 12.6: M2M-NSCL-ID AVP Description This AVP carries an NSCL Identifier value Value type String Value NULL-terminated string e.g. the sclBase URI of the NSCL |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 12.1.7 M2M-SP-ID AVP | Table 12.7: M2M-SP-ID AVP Description This AVP carries an M2M Service Provider Identifier value Value type String Value An FQDN in the form of a NULL-terminated String |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 12.1.8 M2M-Connection-ID AVP | Table 12.8: M2M Connection-ID AVP Description This AVP carries an M2M Connection Identifier value Value type Binary Value 4-octet value |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 12.1.9 M2M-Encr-Encap AVP | Table 12.9: M2M Encr-Encap AVP Description This AVP carries one or more AVPs in encrypted form Value type Composite Value Two-octet Nonce counter value. Starts from 1 and monotonically incremented each time this AVP is sent/received Variable-length octets carrying the encrypted AVPs using the AES-CTR algorithm with the... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 12.2 Security Resource Attributes | The security resource attributes starting shall be supported for D/G M2M Nodes, MSBF and MAS supporting the M2M Service Bootstrapping Parameter Delivery Procedure (used in the GBA-Based M2M Service Bootstrapping Procedure and the M2M Service Bootstrapping Procedure using TLS over TCP) and/or the M2M Service Connection ... |
b53e4107bff8ee134633a34c5c5a7069 | 102 921 | 12.3 Security Primitive Attributes | The security primitive attributes shall be supported for D/G M2M Nodes, MSBF and MAS supporting the M2M Service Bootstrapping Parameter Delivery Procedure in clause 6.4 (used in the GBA-Based M2M Service Bootstrapping Procedure in clause 6.2.1 and the M2M Service Bootstrapping Procedure using TLS over TCP in clause 6.3... |
1bd7e2750b22a6f68c494c60a7a94a4d | 102 917-3 | 1 Scope | The present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for the test specifications for the channel congestion control algorithms operating in the 5,9 GHz range as specified in TS 102 687 [i.2] in compliance with the relevant requir... |
1bd7e2750b22a6f68c494c60a7a94a4d | 102 917-3 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
1bd7e2750b22a6f68c494c60a7a94a4d | 102 917-3 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 102 724: "Intelligent Transport Systems (ITS); Harmonized Channel Specifications for Intelligent Transport Systems operating in the 5 GHz frequency band". [2] ETSI TS 102 917-1: "Intelligent Transport Systems (ITS)... |
1bd7e2750b22a6f68c494c60a7a94a4d | 102 917-3 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI EG 202 798 (V1.1.1): "Intelligent Transport Systems (ITS); Testing; Framework for conformance and interoperability testing". [i.2] ETSI TS 102 68... |
1bd7e2750b22a6f68c494c60a7a94a4d | 102 917-3 | 3 Definitions and abbreviations | |
1bd7e2750b22a6f68c494c60a7a94a4d | 102 917-3 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ISO/IEC 9646-7 [5], and TS 102 724 [1] apply. |
1bd7e2750b22a6f68c494c60a7a94a4d | 102 917-3 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ISO/IEC 9646-1 [4], ISO/IEC 9646-7 [5], and TS 102 724 [1] apply. |
1bd7e2750b22a6f68c494c60a7a94a4d | 102 917-3 | 4 ATS conventions | Test purposes of the present document address the channel congestion control algorithms operating in the 5,9 GHz range. The definitions and procedures as defined in ITS testing framework in EG 202 798 [i.1] have been applied. |
1bd7e2750b22a6f68c494c60a7a94a4d | 102 917-3 | 4.1 Test Architecture | The test architecture defined in TS 102 917-2 [3] clause 4 applies. |
1bd7e2750b22a6f68c494c60a7a94a4d | 102 917-3 | 4.2 ATS structure | |
1bd7e2750b22a6f68c494c60a7a94a4d | 102 917-3 | 4.2.1 Test case grouping | The ATS structure is based on the Test Purposes for channel congestion control algorithms operating in the 5,9 GHz range as defined in TS 102 917-2 [3]. ETSI ETSI TS 102 917-3 V1.1.1 (2013-01) 7 |
1bd7e2750b22a6f68c494c60a7a94a4d | 102 917-3 | 4.2.2 Test case identifiers | The test case names are built up according to the following scheme: "<TC>"_"<Group index>"_"<TC number>" NOTE: This naming scheme provides a 1-1 correspondence of TP identifiers as defined in TS 102 917-2 [3] and test case names. The TP identifier of TC_xxx_01 is TP_xxx_01. The test cases have been divided according to... |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 1 Scope | The present document describes the technical characteristics and methods of testing the improved receiver performance for professional mobile stations 8 Watt (cab radio and EDOR) and 2 Watt professional small mobile station (GPH, OPH and OPS), for the Pan European digital cellular communications system and Personal Com... |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 2 References | |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks in... |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TR 101 748 [i.1] and the following apply: EDOR ETCS Data Only Radio ETCS European Train Control System GPH General Purpose Handheld OPH Operational Purpose Handheld OPS Operational Purpose Handheld for Shunting |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 4 Receiver characteristics for 8 Watt mobiles | |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 4.0 General | In this clause receiver measurements are described, for professional mobile stations equipped with a permanent antenna connector only. Wherever in this clause, for FACCH tests, the SS is required to send a Layer 3 message not requiring a Layer 3 response from the professional MS the message can be a TEST INTERFACE mess... |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 4.1 Reference sensitivity | The reference sensitivity is the signal level at the professional MS receiver input at which a certain BER and FER shall be achieved. The requirements and this test apply to professional MS supporting speech. For tests using ARFCN ranges values in the table 1 shall be used. ETSI ETSI TS 102 933-2 V2.1.1 (2015-06) 8 Tab... |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 4.2 Blocking with CW interfering Signals | |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 4.2.1 Blocking and spurious response - speech channels | |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 4.2.1.1 Definition and applicability | Blocking is a measure of the ability of the receiver to receive a modulated wanted input signal in the presence of an unwanted input signal, on frequencies other than those of the spurious responses or the adjacent channels, without exceeding a given degradation. The requirements and this test apply to professional MS ... |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 4.2.1.2 Conformance requirement | 1) The blocking characteristics of the receiver are specified separately for in-band and out-of-band performance and shall be as identified in ETSI TS 102 933-1 [3], clause 7.1. The reference sensitivity performance as specified in table 1 of ETSI TS 100 910 [2] shall be met when the following signals are simultaneousl... |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 4.2.1.3 Test purpose | 1) To verify that the in band blocking performance is met without exceeding the total number of allowed in band spurious responses. An allowance is made for the statistical significance of the test. 2) To verify that at selected out-of-band frequencies, the out-of-band blocking performance is met without exceeding the ... |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 4.2.1.4 Method of test | |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 4.2.1.4.1 Initial conditions | A call is set up according to the generic call set up procedure, except the BCCH frequency list shall be empty, on a TCH with an arbitrary ARFCN in the range supported by the professional MS. The power control level is set to maximum power. The SS transmits Standard Test Signal C1 on the traffic channel (TCH frequency ... |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 4.2.1.4.2 Procedure | a) The SS produces a static wanted signal and a static interfering signal at the same time. The amplitude of the wanted signal is set to -100 dBm. b) The unwanted signal is a C.W. signal (Standard test signal IO) of frequency FB. It is applied in turn on the subset of frequencies calculated in step c) in the overall ra... |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 4.2.1.5 Test requirements | The error rate measured in this test shall not exceed the test limit error rate values given in table 3. This shall apply under normal test voltage and ambient temperature, and with the interfering signal at any frequency in the range specified. Table 3: Limits for blocking Channel Type of measurement Test limit error ... |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 4.2.2 Blocking and spurious response - control channels | |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 4.2.2.1 Definition and applicability | Blocking is a measure of the ability of the receiver to receive a modulated wanted input signal in the presence of an unwanted input signal, on frequencies other than those of the spurious responses or the adjacent channels, without exceeding a given degradation. The requirements and this test apply to professional MS ... |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 4.2.2.2 Conformance requirement | 1) The blocking characteristics of the receiver are specified separately for in-band and out-of-band performance and shall be as identified in ETSI TS 102 933-1 [3], clause 7.1. The reference sensitivity performance as specified in table 1 of ETSI TS 100 910 [2] shall be met when the following signals are simultaneousl... |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 4.2.2.3 Test purpose | 1) To verify that the in band blocking performance is met without exceeding the total number of allowed in band spurious responses. An allowance is made for the statistical significance of the test. 2) To verify that at selected out-of-band frequencies, the out-of-band blocking performance is met without exceeding the ... |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 4.2.2.4 Method of test | |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 4.2.2.4.1 Initial conditions | A call is set up according to the generic call set up procedure, except the BCCH frequency list shall be empty, on a TCH with an arbitrary ARFCN in the range supported by the professional MS. The power control level is set to maximum power. The SS transmits Standard Test Signal C1 on the traffic channel (TCH frequency ... |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 4.2.2.4.2 Procedure | a) The SS sends a Layer 3 message which does not require a Layer 3 response from the professional MS. Due to interfering signals, the professional MS may not be able to acknowledge the Layer 2 frame. Frame erasures are indicated by repeated L2 frames. b) The SS is set to produce a TUhigh wanted signal and a static inte... |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 4.2.2.5 Test requirements | The error rate measured in this test shall not exceed the test limit error rate given in table 5. This shall apply under normal test voltage and ambient temperature, and with the interfering signal at any frequency in the range specified. ETSI ETSI TS 102 933-2 V2.1.1 (2015-06) 14 Table 5: Limits for blocking Channel T... |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 4.3 Blocking with Broadband interfering Signals | |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 4.3.1 Blocking and spurious response - speech channels | |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 4.3.1.1 Definition and applicability | Blocking is a measure of the ability of the receiver to receive a modulated wanted input signal in the presence of an unwanted broadband input signal, on frequencies other than those of the spurious responses or the adjacent channels, without exceeding a given degradation. The requirements and this test apply to profes... |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 4.3.1.2 Conformance requirement | 1) The blocking characteristics of the receiver are specified in ETSI TS 102 933-1 [3], clause 7.1.2. The reference sensitivity performance as specified in table 1 of ETSI TS 100 910 [2] shall be met when the following signals are simultaneously input to the receiver: - a useful signal at frequency f0, as specified in ... |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 4.3.1.3 Test purpose | To verify that the broadband blocking performance is met without any exception of out of band spurious responses. NOTE: Not all of the possible out-of-band frequencies for broadband interferers are tested as this results in excessive test time and inapplicable test setup. However, an aggregation of broadband signals sp... |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 4.3.1.4 Method of test | |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 4.3.1.4.1 Initial conditions | A call is set up according to the generic call set up procedure, except the BCCH frequency list shall be empty, on a TCH as specified in ETSI TS 102 933-1 [3], clause 7.1.2, table 11, ARFCN 970. The power control level is set to maximum power (PCL2) but may be relaxed to PCL10 to limit constraint on test setup. The SS ... |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 4.3.1.4.2 Procedure | a) The SS produces a static wanted signal and a broadband interfering signal at the same time. There is no correlation in the modulation between the signals. The amplitude of the wanted signal is set to -101 dBm/200 kHz. b) The unwanted signal is an aggregation of two 5 MHz BW LTE signals (E-TM1.1) set respectively on ... |
252768747589ce69c1e0e2dfd7e6abfc | 102 933-2 | 4.3.1.5 Test requirements | The error rate measured in this test shall not exceed the test limit error rate values given in table 6. This shall apply under normal test voltage and ambient temperature, and with the interfering signal at the frequency specified. Table 6: Limits for blocking Channel Type of measurement Test limit error rate % Minimu... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.