ISO 24102-6:2018 高度道路交通システム—陸上移動体の通信アクセス（CALM）— ITSステーション管理—パート6：経路と流れの管理 | ページ 6

3.1

anchor node

logical node contained in an ITS-S path which, when instantiated, has a locator known by the source node

3.2

destination node

communication end point of an ITS-S path

Note 1 to entry: In multicast operation, there can be many distinct destination nodes.

3.3

ITS-S egress anchor node

second (last) anchor node contained in an ITS-S path

3.4

ITS-S ingress anchor node

first anchor node contained in an ITS-S path

3.5

ITS-S anchor segment

segment of an ITS-S path that starts at an ITS-S ingress anchor node and ends up at an ITS-S egress anchor node

3.6

ITS-S capability

uniquely addressable protocol or functionality that is part of an ITS-S Managed Service Entity

Note 1 to entry: Examples of ITS-S capabilities in the ITS station facilities layer are generic ITS-S facilities layer services specified in ISO/TS 17429 (Communication Profile Handler, Facilities Services Handler, Content Subscription Handler), the position and time service defined in ISO/TS 21176 ¹ , the security service defined in ISO/TS 21177 ² ; examples of ITS-S capabilities in the ITS-S networking and transport layer are IPv6 functionalities defined in ISO 21210 (IPv6 neighbour discovery, IPv6 forwarding, IPv6 mobility support, …), the fast service announcement protocol defined in ISO 22418 ³ , etc.

3.7

ITS-S communication profile

ITS-SCP

parameterized ITS-S communication protocol stack (set of protocols composing all the ITS station layers) that allows communication end points to communicate with one another

3.8

ITS-S flow

identifiable sequence of packets of a given ITS-S flow type transmitted between a source node and a destination node

3.9

ITS-S flow identifier

FlowID

identifier, being unique within an ITS station unit, that identifies an ITS-S flow

3.10

ITS-S flow type

set of characteristics describing a data flow

Note 1 to entry: Flow types could be pre-assigned, well known and recorded with some authority registry or defined by the applications following a number of conventions

3.11

ITS-S flow type identifier

FlowTypeID

identifier being unique within the ITS station that identifies an ITS-S flow type

3.12

ITS-S path

directed sequence of nodes connected by links starting at a source node, traversing a communication interface of the source ITS-S, an ITS-S ingress anchor node and an ITS-S egress anchor node, ending at a destination node

Note 1 to entry: In some circumstances, the ITS-S ingress anchor node and the ITS-S egress anchor nodes might be collapsed with the destination node (i.e. the roles of the ITS-S ingress anchor node and the ITS-S egress anchor node are played by the destination node).

Note 2 to entry: For bidirectional communications, two such ITS-S paths exist, i.e. one starting at each communication end point. Note further that there could be multiple ITS-S paths between a source and its destination.

3.13

ITS-S path identifier

PathID

identifier of a given ITS-S path being unique within an ITS station

3.14

ITS-S managed service entity

MSE

uniquely addressable entity in an ITS-S layer comprised of a set of related ITS-S capabilities

Note 1 to entry: Examples of ITS-S managed service entities are: a communication module in the ITS-S access technologies layer (M5, cellular, etc.), a protocol suite in the ITS-S networking and transport layer (IPv6, FNTP, GeoNetworking, 6LoWPAN, etc.), the generic facilities MSE at the ITS-S facilities layer.

3.15

locator

identifier of the topological location of a node in a communication network

Note 1 to entry: A locator of an ITS station is the identifier of an ITS-S ingress anchor node (an ITS station has as many locators as there are ITS-S ingress anchor nodes to which it is attached).

3.16

registered ITS-S flow

ITS-S flow that has been allocated an ITS-S FlowID

3.17

source node

communication end point that creates packets for transmission to peer entities