hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.2.3 Transport protocol | |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.2.3.1 Introduction | SOAP [18] and HTTP [17] are used for delivering TV-Anytime XML data over the IP networks, since this combination is very well suited to the point-to-point, request-response nature of the TV-Anytime operations. The exact usage of SOAP and HTTP is given in the next two clauses. Figure 3 provides a semantic representation... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.2.3.2 SOAP | The following usage of SOAP [18] is mandated: • TV-Anytime metadata services will provide an HTTP binding, and may support other transport bindings where appropriate. • SOAP supports different messaging styles, but is most commonly used for remote procedure calls. TV-Anytime does not use remote procedure call messaging... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.2.3.3 Error codes | The first line of error reporting is governed by the SOAP specification [18]. SOAP fault reporting and fault codes will be returned for most invalid requests or any request where the intent of the caller cannot be determined. In a manner consistent with the SOAP processing rules, HTTP [17] status codes will be used for... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.2.4 NDR service capability description control | For each TV-Anytime Control_NDR operation that is provided, there is a corresponding operation, describe_control_NDR. This operation (an operation, X, and its corresponding describe_X operation) together form a port (see annex A). Since a port always has a single binding and endpoint, the URL of the operation, X, and i... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.3 NDR service discovery methods | NDR service discovery is the process by which a client establishes a URL where a TV-Anytime NDR service can be found. There are a number of ways this process can occur, but only the last method (clause 5.4) is addressed by the present document. |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.3.1 Non-standardized discovery | A number of methods exist for discovering the URLs of NDR services that are not standardized by TV-Anytime. The following list gives some examples: • the client might be pre-programmed with a set of URLs that refer to one or more NDR services. This will typically be useful in a vertical market, or tightly controlled ho... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.3.2 Client-initiated discovery using a bi-directional network | This mode of NDR service discovery involves using the bi-directional network to access a "Yellow Pages" of TV-Anytime NDR services. The mechanism is based upon W3C standards for web service discovery (UDDI [19] and WS-Inspection [21]), the use of which is standardized by TV-Anytime, according to the rules given in clau... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.4 NDR service discovery using web service discovery | The present document describes how standard web service discovery techniques can be used to allow PDRs and other TV-Anytime clients to discover TV-Anytime NDR services. The relevant standards are UDDI [19] and WS-Inspection [21] that enable different but complementary modes of discovery. A provider can choose to enable... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.4.1 Universal Description, Discovery and Integration (UDDI) | UDDI [19] allows PDRs, and other clients with Internet connectivity, to discover TV-Anytime NDR services without the client requiring any prior knowledge of the NDR service, nor any information from a unidirectional metadata service. NDR service providers may publish details of their TV-Anytime NDR service(s) to the UD... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.4.1.1 TV-Anytime web service tModel for NDR services | This tModel is used when a business publishes details of their bindingTemplate structures to indicate an NDR web service compliant with the present document. Clients issuing UDDI inquiry requests can use this tModel key to find only web services that are TV-Anytime NDR services. This following technical model represent... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.4.1.2 TV-Anytime categorization tModel for NDR services | These tModels allow an NDR service provider to categorize their services. The NDR service provider assigns the categories at the point of publication (see clause 5.4.1.3). This enables clients to issue more refined UDDI searches for NDR services. By categorizing an NDR service as richly and accurately as possible, an N... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.4.1.2.1 TV-Anytime serviceURL categorization system | The serviceURL tModel is used to represent the content delivery services (e.g. channels) for which this NDR service provides content recording. This serviceURL tModel is already defined in TS 102 822-2 [2]. Name: TV-Anytime-org:serviceURL. Description: Category system for the content services handled by an NDR service.... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.4.1.2.2 Other categorizations | The other categorizations provided by Universal Business Registry are not used for NDR Service discovery. |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.4.1.3 Publishing a TV-Anytime NDR service | A TV-Anytime NDR service provider can publish details of their service to any node in the UDDI Business Registry. The manner in which this is done will depend upon the operator of that node (see the UDDI specification [19]). An example of the publication process can be found in annex A. A businessService is created for... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.4.2 Web Services Inspection language (WS-Inspection) | A TV-Anytime web server may declare the presence of its NDR service using WS-Inspection [21]. This allows clients to discover service descriptions (i.e. WSDL implementation definitions) for the web services available on that website. The WS-Inspection file may also lead to the discovery of other types of web services, ... |
fc1117000424348cc5789fcc44424dbd | 102 822-9 | 5.5 NDR subscription | The "SubscriptionURL" in the control_NDR service capability description provides a way to access a server where the client can get information about the NDR service conditions such as storage capacity, recording allowance, storage duration and so on. In addition to this, the subscription server allows the client to sub... |
690e0896289bcd03d05e355c46187b3f | 102 821 | 1 Scope | The present document gives the specification for a general purpose distribution link suitable for multicasting data to many recipients using a uni-directional communications network. |
690e0896289bcd03d05e355c46187b3f | 102 821 | 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... |
690e0896289bcd03d05e355c46187b3f | 102 821 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax". |
690e0896289bcd03d05e355c46187b3f | 102 821 | 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. Not applicable. |
690e0896289bcd03d05e355c46187b3f | 102 821 | 3 Definitions, symbols, abbreviations and conventions | |
690e0896289bcd03d05e355c46187b3f | 102 821 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: AF Packet: collection of TAG Items with a header carrying a cohesive and self-contained block of data application: any DCP-based protocol (specified outside the scope of the present document) Application Framing (AF): layer of the DCP ... |
690e0896289bcd03d05e355c46187b3f | 102 821 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: Nx The value N is expressed in radix x. The radix of x is be decimal, thus 2A16 is the hexadecimal representation of the decimal number 42. ⎡⎤ x The smallest integral value numerically greater than x. Sometimes known as the "ceiling" function. ⎣⎦ x ... |
690e0896289bcd03d05e355c46187b3f | 102 821 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AF Application Framing CRC Cyclic Redundancy Check DCP Distribution and Communication Protocol DRM Digital Radio Mondiale FEC Forward Error Correction IP Internet Protocol LSb Least Significant bit LSB Least Significant Byte MSb Most Significa... |
690e0896289bcd03d05e355c46187b3f | 102 821 | 3.4 Conventions | The order of bits and bytes within each description use the following notation unless otherwise stated: • in figures, the bit or byte shown in the left hand position is considered to be first; • in tables, the bit or byte shown in the left hand position is considered to be first; • in byte fields, the Most Significant ... |
690e0896289bcd03d05e355c46187b3f | 102 821 | 4 General description | |
690e0896289bcd03d05e355c46187b3f | 102 821 | 4.1 System overview | The Distribution and Communication Protocol is specifically designed to permit reliable multicast communication from a central server to a number of receivers. Errors on the communications link(s) can be detected and corrected using a Reed-Solomon Forward Error Correction code. As a result the communications links empl... |
690e0896289bcd03d05e355c46187b3f | 102 821 | 4.2 System architecture | The application data is carried from the server to the receiver through a number of layers as shown in figure 1. The data at each layer is encapsulated in a series of packets. The TAG layer encapsulates the elementary arbitrary length data items, while the AF Layer combines the elementary data into a cohesive block of ... |
690e0896289bcd03d05e355c46187b3f | 102 821 | 4.2.1 TAG Items and AF packets and PFT fragments | A very brief overview of the structure of the data at the various layers is shown in figure 3. TAG Name TAG Length TAG Value TAG Item TAG Item TAG Item padding TAG Item AF Header Payload (TAG Packet) CRC PFT Header Payload PFT Header Payload PFT Header Payload TAG Item TAG Packet AF Packet PFT Fragments (if used) TAG P... |
690e0896289bcd03d05e355c46187b3f | 102 821 | 5 TAG Layer | The TAG Layer forms the interface between the application and the DCP. Within the TAG Layer, TAG Items encapsulate individual data items. TAG Items are combined to form in a TAG Packet to form a logically cohesive block of data to the application. Thus to define a new application it is merely necessary to define a seri... |
690e0896289bcd03d05e355c46187b3f | 102 821 | 5.1 TAG packet | A TAG Packet is the name given to a cohesive group of TAG Items that have some significance to the overall application. TAG Packets do not contain any synchronization or error correction and so will typically only exist within equipment. TAG Packet padding TAG Packet TAG Item TAG Item TAG Item <8 bytes Figure 4: TAG pa... |
690e0896289bcd03d05e355c46187b3f | 102 821 | 5.1.1 General rules | The application may determine whether the order of TAG Items within a TAG Packet has any significance. It is very strongly recommended that the order of TAG Items shall not be significant. The application may determine whether a single TAG Packet may contain multiple TAG Items with the same TAG Name value. Implementati... |
690e0896289bcd03d05e355c46187b3f | 102 821 | 5.2 TAG item | The structure of a single TAG Item is as shown in figure 5. Variable length TAG Name TAG Length TAG Value TAG Item padding Total length always a whole number of 8-bit bytes 4 bytes 4 bytes <8 bits Figure 5: TAG Item TAG Name: A four-byte name used to identify the data value carried in the TAG Item. TAG Length: A four-b... |
690e0896289bcd03d05e355c46187b3f | 102 821 | 5.2.1 Hierarchical TAG items - Coding example | If required by the application, a single TAG Item may encapsulate further TAG Items, as illustrated in figure 6. The depth of the hierarchy may be limited by the application if appropriate. TAG Name TAG Length TAG Value TAG Item TAG Item TAG Item TAG Name TAG Length TAG Value TAG Item padding TAG Item TAG Item TAG Item... |
690e0896289bcd03d05e355c46187b3f | 102 821 | 5.2.2 Special TAG items | Each application is largely free to define TAG Item names as appropriate, the only exception being that all names beginning with the ASCII "*" character, 42 (decimal) or 2A16, are reserved as control TAG Items. |
690e0896289bcd03d05e355c46187b3f | 102 821 | 5.2.2.1 Protocol type and revision, *ptr | It is highly recommended that every application using the DCP should declare a protocol type and revision in every TAG Packet using the *ptr TAG Item as shown in figure 8. 4 bytes 2 bytes 2 bytes TAG Value TAG Length TAG Name Protocol Name Minor Major * p r t 0016 0016 0016 4016 ASCII “*ptr” 64 bits 4 bytes 4 bytes Pro... |
690e0896289bcd03d05e355c46187b3f | 102 821 | 5.2.2.1.1 Revision numbering | Each application is permitted to use any revision numbering scheme as required, however it is highly recommended that the minor revisions are backwards compatible, thus an application implementing version 4.3 of protocol WXYZ should be able to decode versions 4.0, 4.1 and 4.2 in addition to 4.3, but may not necessarily... |
690e0896289bcd03d05e355c46187b3f | 102 821 | 5.2.2.2 Dummy padding, *dmy | To allow word alignment to be achieved when necessary, the *dmy TAG Item allows more than 8 padding bytes (of undefined data) to be inserted into a TAG Packet: if less than 8 bytes of padding are required, the TAG Packet Padding shall be used instead. Undefined data * d m y Length of TAG Value (in bits) Variable length... |
690e0896289bcd03d05e355c46187b3f | 102 821 | 6 Application Framing (AF) layer | The AF layer encapsulates a single TAG Packet in a simple structure that is suitable for passing between equipment connected via error-free links. Such links may be provided by existing networks, such as TCP/IP, or by the PFT Layer described in clause 7. |
690e0896289bcd03d05e355c46187b3f | 102 821 | 6.1 AF packet structure | The basic structure of an AF Packet is as shown in figure 9. Payload AF Header SYNC LEN SEQ AR PT CRC 2 bytes CF MAJ MIN 4 bytes 2 bytes 4 bits 3 bits 1 byte 1 byte 1 bit LEN bytes 10 bytes 2 bytes Figure 9: AF Layer SYNC: two-byte ASCII representation of "AF". LEN: length of the payload, in bytes. SEQ: sequence number... |
690e0896289bcd03d05e355c46187b3f | 102 821 | 6.2 Revision history | Table 1: Revision history Major revision Minor revision Date Changes 0116 0016 2003-01-28 Initial public release ETSI ETSI TS 102 821 V1.4.1 (2012-10) 14 |
690e0896289bcd03d05e355c46187b3f | 102 821 | 7 PFT layer | The optional Protection, Fragmentation and Transport, or PFT Layer provides, as its name suggests, three separate functions. The first is error protection using a Reed-Solomon code that can detect and correct individual bit errors and also rebuild entire lost packets. The second is fragmentation, splitting large packet... |
690e0896289bcd03d05e355c46187b3f | 102 821 | 7.1 PFT fragment structure | The structure of a PFT Fragment is as shown in figure 11. 14, 16, 18 or 20 bytes (depending on options) Payload HCRC Psync Pseq Findex Fcount FEC 16 bits 16 bits 24 bits 24 bits 1 bit 16 bits PFT Header Plen bytes Plen 14 bits Addr 1 bit RSk 8 bits RSz 8 bits Source 16 bits Dest 16 bits Optional RS header Optional tran... |
690e0896289bcd03d05e355c46187b3f | 102 821 | 7.2 Definitions | Throughout the following text, the following definitions shall apply. |
690e0896289bcd03d05e355c46187b3f | 102 821 | 7.2.1 Known values | • l is the total length of the original AF Packet, including the header and CRC. • kmax is the maximum value of k and has the value 207. • p is the number of bytes of Reed Solomon parity per chunk and has the value 48. • m is the maximum number of fragment losses per packet that the Reed Solomon is to be able to recove... |
690e0896289bcd03d05e355c46187b3f | 102 821 | 7.2.2 Calculated values | • c is the number of Reed Solomon chunks (fixed as zero if Reed Solomon not in use). • k is the data length of each chunk and is carried in the RSk field of the PFT Header (zero if Reed Solomon not used). • z is the number of zero-bytes added to the last Reed Solomon chunk and is carried in the RSz field of the PFT Hea... |
690e0896289bcd03d05e355c46187b3f | 102 821 | 7.3 Encoding | The following steps shall be completed in order to encode a single AF Packet. In the event that an option (e.g. Reed Solomon) is not enabled, that step is simply not performed. |
690e0896289bcd03d05e355c46187b3f | 102 821 | 7.3.1 Reed Solomon | The original packet is first broken down into c Reed Solomon Chunks of k bytes each - z zero-bytes of padding are added to the last chunk if necessary. The Reed Solomon parity bytes are then calculated and appended to each chunk, and the resulting RS Block is interleaved to form an RS Packet. This is shown diagrammatic... |
690e0896289bcd03d05e355c46187b3f | 102 821 | 7.3.2 Fragmentation | Fragmentation may be applied directly to an AF Packet or to a pre-processed RS Packet. The fragmentation splits the data from the original AF or RS Packet into a number of separate fragments. When carrying an interleaved Reed Solomon Packet, up to m of these fragments can be lost from each packet without losing data. T... |
690e0896289bcd03d05e355c46187b3f | 102 821 | 7.3.3 Transport addressing | The PFT Layer addressing fields Source and Dest are intended to be used to identify the sender (Source) and recipient (Dest) of a packet. The value FFFF16 shall be used to indicate "broadcast", all other values indicate a specific address. If a device is configured with specific source and/or destination addresses, it ... |
690e0896289bcd03d05e355c46187b3f | 102 821 | 7.4 Decoding process | Decoding the PFT Fragments is a four stage process. The four stages are, in order: • synchronize; • discard incorrectly addressed fragments (if transport addressing enabled); • de-fragment (if either Reed Solomon or Simple Fragmentation has been used); • Reed Solomon error detect and correct (if Reed Solomon enabled). |
690e0896289bcd03d05e355c46187b3f | 102 821 | 7.4.1 Synchronization | For streaming links (e.g. asynchronous serial or TCP/IP) the following process shall be used for synchronization of the incoming stream. Synchronization may also be applicable when reading a file. i) Detect the bit-pattern 01010000010001102 (504616) corresponding to the ASCII sync-word "PF" to find the start of a candi... |
690e0896289bcd03d05e355c46187b3f | 102 821 | 7.4.2 Transport addressing | Each PFT Fragment may contain a source and destination address. If present, the address fields shall be examined and if they do not match the configuration of the unit, the entire fragment shall be discarded. PFT Fragments which do not contain the optional Transport header shall never be discarded. |
690e0896289bcd03d05e355c46187b3f | 102 821 | 7.4.3 Defragmentation | Defragmentation is the reverse process to fragmentation. Memory management is kept simple since it is known that all fragments (except the last one) are the same size. The last fragment will be the same size or smaller than the preceding fragments. If Reed Solomon is not in use, every fragment need to be received corre... |
690e0896289bcd03d05e355c46187b3f | 102 821 | 7.4.4 Reed-Solomon decoding | Reed Solomon decoding is the reverse process to encoding. The length of the RS Packet can be calculated as follows, where: • f is the number of fragments produced from this packet, carried in the Fcount header field. • s is the size in bytes of the PFT fragments as carried in the Plen header field of all fragments exce... |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 1 Scope | The present document provides the test suite structure and test purpose specification for the ISO protocols specified in ISO 24102-4 [1] and ISO 24102-5 [2] in compliance with the relevant requirements, and in accordance with the relevant guidance given in EG 202 798 [i.1]. |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 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... |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ISO 24102-4:2013: "Intelligent transport systems -- Communications access for land mobiles (CALM) -- ITS station management -- Part 4: Station-internal management communications". [2] ISO 24102-5:2013: "Intelligent transpo... |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 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: "Intelligent Transport Systems (ITS); Testing; Framework for conformance and interoperability testing". |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 3 Definitions and abbreviations | |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ISO 24102-4 [1], ISO 24102-5 [2] and EG 202 798 [i.1] apply. |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ISO 24102-4 [1], ISO 24102-5 [2] and EG 202 798 [i.1] apply. ETSI ETSI TS 102 797-2 V1.2.1 (2014-06) 6 |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 4 Test suite structure | In general, the conformance test system architecture presented in the ITS testing framework EG 202 798 [i.1] extended as illustrated in figure 1 applies. Codec Figure 1: General conformance test system architecture for SUTs Such SUTs which support the "ITS station-internal Management Communications Protocol" (IICP) ISO... |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 5 Test purpose basics | |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 5.1 TP definition conventions | The TP definition is built according to the guidelines provided in the ITS testing framework EG 202 798 [i.1], applying a formalized language with pre-defined keywords for the behaviour description. |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 5.2 TP identifier naming conventions | The identifier of the TP is built according to tables 1 and 2 as recommended in the ITS testing framework EG 202 798 [i.1]. Table 1: TP naming convention for the ITS station-internal management communications protocol (IICP) specified in ISO 24102-4 [1] TP/<root>/<gr>/<x>/<nn> <root> = root IICP ITS station-Internal ma... |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 5.3 Rules for behaviour description | The description of the TP is built according to the guidelines provided in the ITS testing framework EG 202 798 [i.1]. |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 5.4 Sources of TP definitions | All TPs are specified according to ISO 24102-4 [1] and ISO 24102-5 [2]. ETSI ETSI TS 102 797-2 V1.2.1 (2014-06) 8 |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 5.5 TP proforma | EG 202 798 [i.1] proposes a TP proforma which is used in the present document. The fields of this proforma as used in the present document are explained in table 3. Table 3: TP proforma field description TP Header TP ID The TP ID is a unique identifier according to the TP naming conventions in tables 1 and 2. Test obje... |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 5.6 PICS mnemonics | The PICS mnemonics presented in tables 4 and 5 are used in the TP proforma. Table 4: PICS mnemonics for FSAP Mnemonic PICS item PICS_FSAP_ROLE_SP TS 102 797-1 [3] B.2/1 PICS_FSAP_ROLE_SU TS 102 797-1 [3] B.2/2 PICS_ITS_S_INW TS 102 797-1 [3] B.6/1 PICS_ROLE_HONLY TS 102 797-1 [3] B.5/1 PICS_ROLE_RH TS 102 797-1 [3] B.5... |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 6 TPs for IICP | |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 6.1 Management | |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 6.1.1 Valid behaviour tests | TP Id IICP/MGM/BV/01 Test objective Generation of ITS-SCUalive message after power on - no other ITS-SCU in the SUT Reference ISO 24102-4 [1], clauses 9.1 and 9.2 PICS Selection PICS_IICP_MGM Initial conditions with { the IUT having no knowledge about other ITS-SCUs in the SUT } Expected behaviour ensure that { when { ... |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 6.1.2 Invalid behaviour tests | TP Id IICP/MGM/BI/01 Test objective Reception of ITS-SCUalive (alive) message with address conflict Reference ISO 24102-4 [1], clauses 9.1 and 9.3 PICS Selection PICS_IICP_MGM Initial conditions with { the IUT having its own ITS-SCU-ID allocated } Expected behaviour ensure that { when { the IUT having received an ITS-S... |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 6.2 Communications | |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 6.2.1 Valid behaviour tests | TP Id IICP/COM/BV/01 Test objective Transmission of IIC-Request VCI-info to all types of ITS-SCUs Reference ISO 24102-4 [1], clause 8.2.1 and annex B.2.3 PICS Selection Initial conditions with { the IUT having its own ITS-SCU-ID allocated } Expected behaviour ensure that { when { the IUT having received the request to ... |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 6.2.2 Invalid behaviour tests | TP Id IICP/COM/BI/01 Test objective Reception of an ICC-Request message with invalid DestinationITS-SCU-ID (reserved) Reference ISO 24102-4 [1], clause 8.3.1 PICS Selection Initial conditions with { the IUT having its own ITS-SCU-ID allocated } Expected behaviour ensure that { when { the IUT having received an ICC-Requ... |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 7 TPs for FSAP | |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 7.1 Service provider | |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 7.1.1 Combined ITS-S host and ITS-S router | |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 7.1.1.1 Valid behaviour tests | TP Id FSAP/SP/HR/BV/01 Test objective Test of SAM format. Registration of ITS-S application for message distribution only (no session phase) with request of specific access technology Reference ISO 24102-5 [2], clauses 8.2.1, 8.2.4 and 8.2.5 PICS Selection PICS_FSAP_ROLE_SP AND PICS_ROLE_RH Initial conditions with { th... |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 7.1.1.2 Invalid behaviour tests | TP Id FSAP/SP/HR/BI/01 Test objective Registration of ITS-S application for message distribution only (no session phase) with request of specific but not available access technology Reference ISO 24102-5 [2], clauses 8.2.1, 8.2.4 and 8.2.5 PICS Selection PICS_FSAP_ROLE_SP AND PICS_ROLE_RH AND PICS_SUT_AT_CHG Initial co... |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 7.1.2 ITS-S host only | |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 7.1.2.1 Valid behaviour tests | TP Id FSAP/SP/HO/BV/01 Test objective Registration of ITS-S application for message distribution only (no session phase) with request of specific access technology available in an ITS-S router unit Reference ISO 24102-5 [2], clauses 8.2.1, 8.2.4, 8.2.5 and 8.5 PICS Selection PICS_FSAP_ROLE_SP AND (PICS_ROLE_HONLY OR (P... |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 7.1.2.2 Invalid behaviour tests | TP Id FSAP/SP/HO/BI/01 Test objective Registration of ITS-S application for message distribution only (no session phase) with request of specific but not available access technology Reference ISO 24102-5 [2], clauses 8.2.1, 8.2.4, 8.2.5 and 8.5 PICS Selection PICS_FSAP_ROLE_SP AND (PICS_ROLE_HONLY OR (PICS_ROLE_RH AND ... |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 7.1.3 ITS-S router only | |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 7.1.3.1 Valid behaviour tests | TP Id FSAP/SP/RO/BV/01 Test objective Registration of ITS-S application for message distribution only (no session phase) with request of specific access technology Reference ISO 24102-5 [2], clauses 8.2.1, 8.2.4, 8.2.5 and 8.5 PICS Selection PICS_FSAP_ROLE_SP AND (PICS_ROLE_RONLY OR (PICS_ROLE_RH AND PICS_ITS_S_INW)) I... |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 7.1.3.2 Invalid behaviour tests | TP Id FSAP/SP/RO/BI/01 Test objective Registration of ITS-S application for message distribution only (no session phase) with request of specific but not available access technology Reference ISO 24102-5 [2], clauses 8.2.1, 8.2.4, 8.2.5 and 8.5 PICS Selection PICS_FSAP_ROLE_SP AND (PICS_ROLE_RONLY OR (PICS_ROLE_RH AND ... |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 7.2 Service user | |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 7.2.1 Combined ITS-S host and ITS-S router | |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 7.2.1.1 Valid behaviour tests | TP Id FSAP/SU/HR/BV/01 Test objective Reception of SAM for message distribution only (no session phase) Reference ISO 24102-5 [2], clauses 8.3.1 and 8.3.4 PICS Selection PICS_FSAP_ROLE_SU AND PICS_ROLE_RH Initial conditions with { the IUT having received GCregClient, and having properly registered any ITS-S application... |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 7.2.1.2 Invalid behaviour tests | None. |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 7.2.2 ITS-S host only | |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 7.2.2.1 Valid behaviour tests | TP Id FSAP/SU/HO/BV/01 Test objective Reception of SAM with need for a session with need to send CTX Reference ISO 24102-5 [2], clauses 8.3.1, 8.3.4 and 8.5 PICS Selection PICS_FSAP_ROLE_SU AND (PICS_ROLE_HONLY OR (PICS_ROLE_RH AND PICS_ITS_S_INW)) AND PICS_SIP_W_CTX Initial conditions with { the IUT having received GC... |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 7.2.2.2 Invalid behaviour tests | None. ETSI ETSI TS 102 797-2 V1.2.1 (2014-06) 35 |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 7.2.3 ITS-S router only | |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 7.2.3.1 Valid behaviour tests | TP Id FSAP/SU/RO/BV/01 Test objective Reception of SAM Reference ISO 24102-5 [2], clauses 8.3.1, 8.3.4 and 8.5 PICS Selection PICS_FSAP_ROLE_SU AND (PICS_ROLE_RONLY OR (PICS_ROLE_RH AND PICS_ITS_S_INW)) Initial conditions with { the IUT having received GCregClient, and having properly registered any ITS-S application w... |
52d00dd4a40a1e89e1973f28d2e17040 | 102 797-2 | 7.2.3.2 Invalid behaviour tests | None. ETSI ETSI TS 102 797-2 V1.2.1 (2014-06) 36 History Document history V1.1.1 August 2012 Publication V1.2.1 June 2014 Publication |
1e822b5221901478fbbe7e343d02a55a | 102 771 | 1 Scope | The present document gives guidelines for the implementation of the Generic Stream Encapsulation (GSE) Protocol. The guidelines are intended to be recommended rules, advice and good practices for the usage of the GSE specifications defined in TS 102 606 [1], in order to assist systems integrators and equipment manufact... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.