ISO 22418:2018 pdf free
ISO 22418:2018 pdf free.Intelligent transport systems一Fast service announcement protocol (FSAP)
The purpose of SrvIniP is to invite a peer ITS-SU by means of a “Fast Service Announcement Message” (FSAM) to use an ITS service which is uniquely identified by an ITS application identifier (ITS-AID) specified in ISO 17419; ITS-AID points to an ITS application object.
NOTE 1 Usage of some allocated ITS-AID values may not be meaningful in FSAM.
Acceptance of such an invitation typically results in a session, where the two peer ITS-S applications exchange data. However, a session is not necessarily needed, i.e. the service may be provided completely by the FSAM. Thus FSAM provides also the means to periodically broadcast information from ITS
broadcast services.
Three operational options of SrvIniP are specified. The distinction originally was motivated by the two ITS application objects
1) ITS application class[1] and
2) ITS application, and was extended
3) to allocate private communication channels to individual ItS station units (ITS-SUs).
Option one, originally designed for ITS application classes (DSRC-like SrvIniP)[1], is illustrated in Figure 1. FSAM is sent by a service advertiser ItS station to invite for a service initialization phase.
FSRM is sent by a service user ITS station to acknowledge FSAM. Successful SrvIniP is given by the first successful REQW or REQN of the service provider.
NOTE 2 In [1], BST corresponds functionally to FSAM, and VST corresponds functionally to FSRM.
NOTE 3 The concept of application classes was introduced in [1]. Distinction of classes was done with an identifier of ASN.1 type DSRCappl icat ionEntityID. The difference between an ITS application class and an ItS application is, that for an ITS application class several contexts exist. Each context itself can be referred to as an ITS application.
– requests, either with or without an expected response, typically are sent by the service provider,but may also be sent by the service user, and
– responses typically are sent by the service user, but may also be sent by the service provider,
dependent on the specification of the ItS application.
NOTE 4 Rules on which data are sent by a service provider or by a service user apply strictly for [1]. In general,for ITS there are no such rules.
NOTE 5 As specified in ISO 21217:2014, the service user and service client instances of an ITS application are referred to as ITS-S application processes; ITS-S application processes residing in the “Applications” entity are referred to as ITS-S applications.ISO 22418 pdf download.
