ISO/TS 21219-9:2016 高度道路交通システム—輸送プロトコル専門家グループ、第2世代（TPEG2）を介した交通および旅行情報（TTI）—パート9：サービスおよびネットワーク情報（TPEG2-SNI） | ページ 6

3.1

guide to the service tables

GST

basic service (3.10) information such as service structure, service timing and content description (3.4) , etc.

3.2

fast tuning GST

FT-GST

directory of the applications (3.11) and content (3.12) of the service (3.10) that indicates in which components the relevant information can be found

Note 1 to entry: This contains the minimum set of information required for the acquisition of application data.

3.3

time schedule GST

TS-GST

indicates the operation times of selected service components (3.16)

3.4

content description GST

CD-GST

optional table that gives the textual descriptions of selected service components (3.16)

3.5

geographical coverage GST

GC-GST

optional table that defines the spatial range of selected service components (3.16)

3.6

service component reset GST

SCR-GST

optional table that is used by the service provider (3.14) to delete application-specific data older than a certain moment

3.7

conditional access information reference GST

CAI-GST

optional table that is used by the service provider (3.14) to indicate which service component (3.16) carries the CAI application data required to decode encrypted service components

3.8

versioning of TPEG applications GST

VER-GST

mandatory table that is used by the service provider (3.14) to indicate which version of the application specification the service component (3.16) complies to

3.9

number of messages within a TPEG service component

NOM-SIT

optional table that is used to transmit the number of messages currently available for each service component (3.16)

3.10

service

collection of different information streams [ applications (3.11) ] logically bound together and delivered from a service provider (3.14) to the end user

3.11

application

stream of information that by itself provides a benefit to (i.e. can be “applied by”) the end user

3.12

content

information inside an application (3.11)

Note 1 to entry: A service (3.10) may contain several instances of the same application type, each containing different content. Within an application, different content is labelled with a unique content ID (COID) specified by the originator of the content.

3.13

application instance

actual data stream containing content (3.12) as defined by an application (3.11)

3.14

service provider

organization that provides information a [ service (3.10) ] to end users and manages the content (3.12) of its service and decides whether a service is encrypted or not

Note 1 to entry: A service provider that generates the content of a service is called a service originator. A service provider that carries content generated by another originator is called the carrier. There is only one service originator of content, but there may be more than one service carrier.

3.15

content originator

original provider of an application instance (3.13)

Note 1 to entry: The content originator may distribute the application (3.11) data to different service providers (3.14) . In some cases, the service provider generates its own application data and is therefore also the content originator.

3.16

service component

information stream [ application (3.11) ] that is part of a service (3.10)

Note 1 to entry: A TPEG stream is logically divided into parts known as service components. Each service component carries an application instance (3.13) . A service component is effectively a “channel” within the multiplex of a TPEG stream. Each stream comprises a number of these “channels” which are identified by the component identifier in TPEG2-SFW and linked to the COID and AID in the TPEG2-SNI application.

3.17

service identification

worldwide unique identifier for a service (3.10)

Note 1 to entry: It consists of three elements called SID A, SID-B, SID-C (cf. subclause 0). These are allocated as described in ISO/TS 18234-2.

3.18

content identification

COID

identifier that is unique within a given application (3.11) and used to specify its content (3.12)

Note 1 to entry: The COID is defined by the originator of the content and is unique within a specific application. It is used for labelling the content of a component.

3.19

application and content identification

ACID

worldwide unique identifier that defines the content (3.12) of a service (3.10)

Note 1 to entry: The ACID is composed of the originator service identification (SID-A, SID-B, SID-C) (3.17), the content identification (COID) (3.18) and the application identification (AID) (3.20) .

3.20

application identification

AID

identifier that specifies how to process TPEG content (3.12) and route information to the appropriate application decoder

Note 1 to entry: Each TPEG application has a unique number, which identifies the application (3.11) according to Clause 5. The application identification is part of the TPEG specification and is defined as and when new applications are developed.

3.21

service component identification

SCID

unique identifier that defines a service component within a service (3.10)

Note 1 to entry: The SCID is chosen by the carrier service provider and identifies a component, which itself has an ACID comprising originator SID, COID and AID. The same number may be used in a different service or, in the same service at a later time to identify a completely different combination of originator SID, COID and AID.

3.22

service table

table containing basic service information, such as service structure, service timing and content description (3.4) , etc.