Software Cluster Connection (SwCluC)

Returns a handle of a Resource Entry in a Resource Entry Group Tags: atp.Status=draft

Returns the Id of the connected Software Cluster for a Notifier Handle of a Provide Resource Entry or a Provide Handle of a Require Resource Entry Tags: atp.Status=draft

Returns the Id of the connected Software Cluster for a Notifier Handle of a Provide Resource Entry or a Provide Handle of a Require Resource Entry Tags: atp.Status=draft

Returns the Id of the connected Software Cluster for a Notifier Handle of a Provide Resource Entry or Provide Handle of a Require Resource Entry Tags: atp.Status=draft

Returns the number of actually used - and thereby connected - handle sets Tags: atp.Status=draft

Returns the number of actually used - and thereby connected - handle sets. Tags: atp.Status=draft

Returns the value of the Subscribed Interface Validity Marker. Tags: atp.Status=draft

SwCluC_Xcc_Init is intended to allocate and initialize system resources used by the Software Cluster Connection. It initializes interface memory which might be needed to be read by other Software Clusters but it is not allowed to do any read access to memory of any another Software Cluster. Tags: atp.Status=draft

SwCluC_Xcc_Init2 is intended to allocate and initialize system resources used by the Software Cluster Connection. It can execute initializations which require a read access to interface memory of another Software Clusters. Tags: atp.Status=draft

SwCluC_OsProxy_Init is intended to allocate and initialize system resources used by the Os Proxy linked to this specific socked Tags: atp.Status=draft

SwCluC_NvMProxy_Init is intended to allocate and initialize system resources used by the Nv MProxy linked to this specific socked. Tags: atp.Status=draft

SwCluC_DcmProxy_Init is intended to allocate and initialize system resources used by the Dcm Proxy linked to this specific socked. Tags: atp.Status=draft

SwCluC_DemProxy_Init is intended to allocate and initialize system resources used by the Dem Proxy linked to this specific socked. Tags: atp.Status=draft

SwCluC_FiMProxy_Init is intended to allocate and initialize system resources used by the FiM Proxy linked to this specific socked. Tags: atp.Status=draft

SwCluC_LdComProxy_Init is intended to allocate and initialize system resources used by the LdComProxy linked to this specific socked. Tags: atp.Status=draft

SwCluC_ComProxy_Init is intended to allocate and initialize system resources used by the ComProxy linked to this specific socked. Tags: atp.Status=draft

This callback function indicates that the signal of the primitive data item/event is ready for reception. It is an implementation of a <ComUser_CbkRxAck> callback. Tags: atp.Status=draft

This callback function indicates that COM has received a signal and parsed it as "invalid". It is an implementation of a <ComUser_CbkInv> callback. Tags: atp.Status=draft

This callback function indicates that the aliveTimeout after the last successful reception of the signal of the data item/event has expired (data element outdated). It is an implementation of a <ComUser_CbkRxTOut> callback. Tags: atp.Status=draft

This callback function indicates that the signal of the data item/event is already handed over by COM to the PDU router. It is an implementation of a <ComUser_CbkTxAck> callback. Tags: atp.Status=draft

This callback function indicates that an error occurred when the signal of the data item/event was handed over by COM to the PDU router. It is an implementation of a <ComUser_CbkTx Err> callback. Tags: atp.Status=draft

This callback function indicates that the timeout of TransmissionAcknowledgementRequest for sending the signal of the data item/event has expired. It is an implementation of a <ComUser_ CbkTxTOut> callback. Tags: atp.Status=draft

This function is called to provide the received data of an I-PDU segment (N-PDU) to the upper layer. Each call to this function provides the next part of the I-PDU data. The size of the remaining data is written to the position indicated by bufferSizePtr. Tags: atp.Status=draft

This function is called to acquire the transmit data of an I-PDU segment (N-PDU). Each call to this function provides the next part of the I-PDU data unless retry->TpDataState is TP_ DATARETRY. In this case the function restarts to copy the data beginning at the offset from the current position indicated by retry->TxTpDataCnt. The size of the remaining data is written to the position indicated by availableDataPtr Tags: atp.Status=draft

Indication of a received PDU from a lower layer communication interface module. Tags: atp.Status=draft

Called after an I-PDU has been received via the TP API, the result indicates whether the transmission was successful or not. Tags: atp.Status=draft

Within this API, the upper layer module (called module) shall check whether the available data fits into the buffer size reported by PduInfoPtr->SduLength. If it fits, it shall copy its data into the buffer provided by PduInfoPtr->SduDataPtr and update the length of the actual copied data in PduInfoPtr->SduLength. If not, it returns E_NOT_OK without changing PduInfoPtr. Tags: atp.Status=draft

The lower layer communication interface module confirms the transmission of a PDU, or the failure to transmit a PDU. Tags: atp.Status=draft

This function is called after a Signal has been transmitted via the TP-API on its network. Tags: atp.Status=draft

This function is called at the start of receiving an N-SDU. The N-SDU might be fragmented into multiple N-PDUs (FF with one or more following CFs) or might consist of a single N-PDU (SF). The service shall provide the currently available maximum buffer size when invoked with TpSdu Length equal to 0. Tags: atp.Status=draft

This function informs the NvM proxy of the SwCluC about the end of the NvM_ReadAll job.

This function is called to acquire the transmit data of an I-PDU segment (N-PDU). Each call to this function provides the next part of the I-PDU data unless retry->TpDataState is TP_ DATARETRY. In this case the function restarts to copy the data beginning at the offset from the current position indicated by retry->TxTpDataCnt. The size of the remaining data is written to the position indicated by availableDataPtr Tags: atp.Status=draft

Indication of a received PDU from a lower layer communication interface module. Tags: atp.Status=draft

Called after an I-PDU has been received via the TP API, the result indicates whether the transmission was successful or not. Tags: atp.Status=draft

Within this API, the upper layer module (called module) shall check whether the available data fits into the buffer size reported by PduInfoPtr->SduLength. If it fits, it shall copy its data into the buffer provided by PduInfoPtr->SduDataPtr and update the length of the actual copied data in PduInfoPtr->SduLength. If not, it returns E_NOT_OK without changing PduInfoPtr. Tags: atp.Status=draft

The lower layer communication interface module confirms the transmission of a PDU, or the failure to transmit a PDU. Tags: atp.Status=draft

Type of the Software Cluster's ID value Tags: atp.Status=draft

Type for the global ID value of a resource Tags: atp.Status=draft

Type to code control flags for the connection process. Bit 0..14 are reserved. Tags: atp.Status=draft

Type to code the properties of a resource. Bit 0..5 are reserved. Tags: atp.Status=draft

Type to code the type of a resource Tags: atp.Status=draft

Type for the global ID value of a resource Tags: atp.Status=draft

Type for the guard value of a resource Tags: atp.Status=draft

Index type to address the immutable and modifiable interface table Tags: atp.Status=draft

Index type to address a set of handles in the immutable and modifiable interface table Tags: atp.Status=draft

Generic function pointer type according C default type for functions Tags: atp.Status=draft

Tags: atp.Status=draft

⌊ DRAFT g The Binary Manifest of the Software Clus- ter Connection shall provide exactly one instance of the Binary Manifest Header 1 const SwCluC_BManif_HeaderType SwCluC_BManif_Header = 2 { <initialization> };

⌊ DRAFT g The header file SwCluC_BManif.h shall export the declaration of the Binary Manifest Header 1 extern const SwCluC_BManif_HeaderType SwCluC_BManif_Header;

⌊ DRAFT g The element Preamble of the Binary Mani- fest Header shall be set to the value 0x41524350464C4558 .

⌊ DRAFT g The element ManifestMajorVersion of the Binary Manifest Header shall be set to the value 0x01 .

⌊ DRAFT g The element ManifestMinorVersion of the Binary Manifest Header shall be set to the value 0x01 .

⌊ DRAFT g The element SwClusterId of the Binary Man- ifest Header shall be set to the value of the configuration parameter SwCluC- SoftwareClusterId of the selected SwCluCDefinition .

⌊ DRAFT g The element MachineId of the Binary Mani- fest Header shall be set to the value of the configuration parameter SwCluC- MachineId of the selected SwCluCDefinition .

⌊ DRAFT g The element SwClusterType of the Binary Manifest Header shall be set according to the value of the configuration param- eter SwCluCSoftwareClusterType of the selected SwCluCDefinition with the following encoding: • HOST_SWCL : 0x00 • APPLICATIVE_SWCL : 0x01 • SUBSTITUTION_SWCL : 0xFF

⌊ DRAFT g The bit SWCLUC_BMANIF_DISABLE_ON_ECU_ CONNECTION in the element ConnectorControlFlags of the Binary Mani- fest Header shall be set if the SwCluCBManifOnBoardConnectorControl is set to DISABLE_ON_ECU_CONNECTOR . Otherwise, the bit is not set (value 0).

⌊ DRAFT g The element NoOfInterfaceDescriptors of the Binary Manifest Header shall be set to the number of SwCluCBManif- ProvideResourceEntry + number of SwCluCBManifRequireResourceEntry containers in the configuration.

⌊ DRAFT g The element NoOfOfferedInterfaceHandles of the Binary Manifest Header shall be set to the number of offered handles.

⌊ DRAFT g The element NoOfSubscribedInterfaceHan- dles of the Binary Manifest Header shall be set to the number of handles in the Subscribed Interface .

⌊ DRAFT g The Binary Manifest of the Software Clus- ter Connection shall provide the header file SwCluC_BManif.h .

⌊ DRAFT g The header file SwCluC_BManif.h shall include all header files configured in SwCluCBManifHeaderInclude s in the containers SwCluCBManifProvideResourceEntryGroup and SwCluCBManifRequireRe- sourceEntryGroup .

⌊ DRAFT g If the SwCluCBManifDescriptorTreatment is set to EMBED_DESCRIPTORS the Binary Manifest of the Software Cluster Connection shall provide exactly one instance of the Interface Descriptor Table composed out of the following column arrays: 1 / * descriptor table column for resource properties * / 2 const SwCluC_BManif_ResourcePropertiesType SwCluC_BManif_ResourcePropertiesDescriptorColumn[ SWCLUC_BMANIF_NO_OF_DESCRIPTORS] = { <initialization> }; 3 4 / * descriptor table column for resource type Ids * / 5 const SwCluC_BManif_ResourceTypeIdType SwCluC_BManif_ResourceTypeIdDescriptorColumn[ SWCLUC_BMANIF_NO_OF_DESCRIPTORS] = { <initialization> }; 6 7 / * descriptor table column for global resource Ids * / 8 const SwCluC_BManif_GlobalResourceIdType SwCluC_BManif_GlobalResourceIdDescriptorColumn[ SWCLUC_BMANIF_NO_OF_DESCRIPTORS] = { <initialization> }; 9 10 / * descriptor table column for guard values * / 11 const SwCluC_BManif_ResourceGuardValueType SwCluC_BManif_ResourceGuardValueDescriptorColumn[ SWCLUC_BMANIF_NO_OF_DESCRIPTORS] = { <initialization> }; 12 13 / * descriptor table column for offered interface table index * / 14 const SwCluC_BManif_TableIndexType SwCluC_BManif_OfferedInterfaceIndexDescriptorColumn[ SWCLUC_BMANIF_NO_OF_DESCRIPTORS] = { <initialization> }; 15 16 / * descriptor table column for number of handles in offered interface table * / 17 const SwCluC_BManif_HandleIndexType SwCluC_BManif_OfferedInterfaceNoOfHandlesDescriptorColumn[ SWCLUC_BMANIF_NO_OF_DESCRIPTORS] = { <initialization> }; 18 19 / * descriptor table column for subscribed interface table index * / 20 const SwCluC_BManif_TableIndexType SwCluC_BManif_SubscribedInterfaceIndexDescriptorColumn[ SWCLUC_BMANIF_NO_OF_DESCRIPTORS] = { <initialization> }; 21 22 / * descriptor table column for number of handles in subscribed interface table * / 23 const SwCluC_BManif_HandleIndexType SwCluC_BManif_SubscribedInterfaceNoOfHandlesDescriptorColumn[ SWCLUC_BMANIF_NO_OF_DESCRIPTORS] = { <initialization> }; 24 25 / * descriptor table column for number of handle sets in subscribed interface table * / 26 const SwCluC_BManif_HandleIndexType SwCluC_BManif_SubscribedInterfaceNoOfHandleSetsDescriptorColumn[ SWCLUC_BMANIF_NO_OF_DESCRIPTORS] = { <initialization> };

⌊ DRAFT g For each SwCluCBManifProvideResourceEn- try and SwCluCBManifRequireResourceEntry in a Software Cluster 's con- figuration, the Binary Manifest of the Software Cluster Connection shall provide one row in the Interface Descriptor Table .

⌊ DRAFT g The rows in the Interface Descriptor Ta- ble shall be sorted in ascending order of resource type Ids and rows with equal re- source type Ids shall be sorted in turn in ascending order of global resource Ids.

⌊ DRAFT g The bit SWCLUC_BMANIF_PROVIDED_RESOURCE in the element of the 'resource properties' column shall be set, if the row belongs to a SwCluCBManifProvideResourceEntry . Otherwise the bit SWCLUC_BMANIF_PROVIDED_RESOURCE shall not be set.

⌊ DRAFT g The bit SWCLUC_BMANIF_MANDATORY_RE- SOURCE in the element of the 'resource properties' column shall be set, if the row be- longs to a SwCluCBManifRequireResourceEntry where the SwCluCBManifIs- Mandatory is true . Otherwise the bit SWCLUC_BMANIF_MANDATORY_RESOURCE shall not be set.

⌊ DRAFT g The element in the 'resource type Id' column shall be set to the SwCluCBManifResourceId of the applicable SwCluCBManifRe- sourceType .

⌊ DRAFT g The element in the 'global resource Id' column shall be set to the attribute value globalResourceId of the referenced CpSoft- wareClusterResource as given via SwCluCBManifResourceRef . If the refer- ence SwCluCBManifResourceRef is not set, the element in the global resource Id column shall be set to 0.

⌊ DRAFT g The element in the 'guard value' column shall be set to the SwCluCBManifResourceGuardValue of the SwCluCBManif- ProvideResourceEntry / SwCluCBManifRequireResourceEntry container in the configuration.

⌊ DRAFT g The element in the 'offered interface table index' column shall be set to the index of the Offered Interface where the first offered handle for this resource is allocated. In case the resource has no offered handle the value is set to NO_TABLE_ENTRY .

⌊ DRAFT g The element in the 'number of handles in offered interface table' column shall be set to number of offered handles for this resource. In case the resource has no offered handle, the value is set to 0.

⌊ DRAFT g The element in the 'subscribed interface table in- dex' column shall be set to the index of the Subscribed Interface where the first subscribed handle for this resource is allocated. In case the resource has no sub- scribed handle the value is set to NO_TABLE_ENTRY .

⌊ DRAFT g The element in the 'number of handles in sub- scribed interface table' column shall be set to number of subscribed handles for this resource. In case the resource has no subscribed handle, the value is set to 0.

⌊ DRAFT g The element in the 'number of handle sets in sub- scribed interface table' column shall be set to the SwCluCBManifMaxNumberOfNo- tifierSets if the applicable SwCluCBManifResourceType has set SwCluCB- ManifMultipleNotifierSupport to MULTIPLE_NOTIFIER_SETS . Otherwise the value is set to 0.

⌊ DRAFT g The Binary Manifest of the Software Clus- ter Connection shall provide exactly one instance of the Offered Interface Handle Column 1 const SwCluC_BManif_HandleType SwCluC_BManif_OfferedInterfaceHandleColumn[ SWCLUC_BMANIF_NO_OF_OFFERED_HANDLES] = { <initialization> };

⌊ DRAFT g The Binary Manifest of the Software Clus- ter Connection shall allocate and initialize the number of handles in the Of- fered Interface according to [SWS_SwCluC_00088].

⌊ DRAFT g The Binary Manifest of the Software Clus- ter Connection shall provide exactly one instance of the Subscribed Inter- face Default Handle Column 1 const SwCluC_BManif_HandleType SwCluC_BManif_SubscribedInterfaceDefaultHandleColumn[ SWCLUC_BMANIF_NO_OF_SUBSCRIBED_HANDLES] = { <initialization> };

⌊ DRAFT g The Binary Manifest of the Software Cluster Connection shall allocate and initialize the number of handles in the Subscribed Interface Default Handle Column according to [SWS_SwCluC_00088].

⌊ DRAFT g The Binary Manifest of the Software Clus- ter Connection shall provide exactly one instance of the Subscribed Inter- face Handle Column 1 const SwCluC_BManif_HandleType SwCluC_BManif_SubscribedInterfaceHandleColumn[ SWCLUC_BMANIF_NO_OF_SUBSCRIBED_HANDLES] = { <initialization> };

⌊ DRAFT g The Binary Manifest of the Software Clus- ter Connection shall allocate and initialize the number of handles in the Subscribed Interface Handle Column according to [SWS_SwCluC_00088].

⌊ DRAFT g The Binary Manifest of the Software Clus- ter Connection shall provide exactly one instance of the Subscribed Inter- face Connected SwClusterId Column 1 const SwCluC_BManif_SwClusterIdType SwCluC_BManif_SubscribedInterfaceConnectedSwClusterIdColumn[ SWCLUC_BMANIF_NO_OF_SUBSCRIBED_HANDLES] = { <initialization> };

⌊ DRAFT g The Binary Manifest of the Software Cluster Connection shall allocate and initialize the number of handles in the Subscribed Interface Connected SwClusterId Column according to [SWS_SwCluC_00088].

⌊ DRAFT g The Binary Manifest of the Software Clus- ter Connection shall provide exactly one instance of the Immutable Tables Checksum 1 const uint32 SwCluC_BManif_ImmutableTablesChecksum = <initialization>;

⌊ DRAFT g The Immutable Tables Checksum shall be set to the value of the configuration parameter SwCluCBManifImmutableTa- blesChecksum .

⌊ DRAFT g The Binary Manifest of the Software Clus- ter Connection shall provide exactly one instance of the Total Manifest Checksum 1 const uint32 SwCluC_BManif_TotalManifestChecksum = <initialization>;

⌊ DRAFT g Initially (before the connection process), the Total Manifest Checksum shall be set to the value of the configuration pa- rameter SwCluCBManifTotalManifestChecksum .

⌊ DRAFT g The Binary Manifest of the Software Clus- ter Connection shall provide exactly one instance of the Subscribed Inter- face Validity Marker 1 const uint32 SwCluC_BManif_SubscribedInterfaceValidityMarker = < initialization>;

⌊ DRAFT g Initially, and after a completed connection pro- cess, the Subscribed Interface Validity Marker shall be set to the value of the configuration parameter SwCluCBManifSubscribedInterfaceValidity- Marker .

⌊ DRAFT g The elements • ResourcePropertiesDescriptorColumnPtr • ResourceTypeDescriptorColumnPtr • GlobalResourceIdDescriptorColumnPtr • ResourceGuardValueDescriptorColumnPtr • OfferedInterfaceIndexDescriptorColumnPtr • OfferedInterfaceNoOfHandlesDescriptorColumnPtr • SubscribedInterfaceIndexDescriptorColumnPtr • SubscribedInterfaceNoOfHandlesDescriptorColumnPtr • SubscribedInterfaceNoOfHandleSetsDescriptorColumnPtr • OfferedInterfaceHandleColumnPtr • SubscribedInterfaceHandleDefaultColumnPtr • SubscribedInterfaceHandleColumnPtr • SubscribedInterfaceConnectedSwClusterIdColumnPtr of the Binary Manifest Header shall reference the according array of the Inter- face Descriptor Table if the SwCluCBManifDescriptorTreatment is set to EMBED_DESCRIPTORS . Otherwise the elements are initialized to NULL_PTR .

⌊ DRAFT g The Software Cluster Connector shall con- nect a required resource with a provided resource, if all of the following conditions are fulfilled: • the machine Id of the Software Cluster providing the resource and the ma- chine Id of the Software Cluster (s) requesting the resource are identical • the global resource Id of provided resource and required resource(s) are equal • the global resource Id is not 0 • the resource type Id of provided resource and required resource is equal • the guard value of provided resource and required resource is equal • the number of Provide Handles of provided resource and required resource is equal • the number of Notifier Handles of provided resource and required resource is equal • in case Notifier Handles exist, the provided resource has a Notifier Handle Sets available for the required resource

⌊ DRAFT g The Software Cluster Connector shall copy the Subscribed Interface Default Handle Column entries to the Subscribed Interface Handle Column , and set the related en- tries in the Subscribed Interface Connected SwClusterId Column to SWCLUC_BMANIF_UNCONNECTED for • all Provide Handles of any required resources, for which no connect was ap- plied AND • all Notifier Handles of any provided resources, for which no connect was applied

⌊ DRAFT g In case the provided resource supports multiple Notifier Handle Sets , the Software Cluster Connector shall sort the No- tifier Handle Sets in ascending order of Software Cluster Id of the according re- quired resource(s), and place them in the Subscribed Interface Handle Col- umn of the providing Software Cluster , starting at the second handle.

⌊ DRAFT g In case the provided resource supports multiple Notifier Handle Sets , the Software Cluster Connector shall write as first entry the actual number of used Notifier Handle Sets in the Subscribed In- terface Handle Column .

⌊ DRAFT g In case the provide resource supports multiple Notifier Handle Sets , and less required resources are connected, the Soft- ware Cluster Connector shall fill the remaining handles in the Subscribed Interface Handle Column with the default values from the Subscribed In- terface Default Handle Column of the Software Cluster providing the re- source.

⌊ DRAFT g The Software Cluster Connector shall de- tect, if the ManifestMajorVersion and ManifestMinorVersion numbers given in the Binary Manifest Header are compatible to the Software Cluster Con- nector 's implementation. In case of any incompatible version number, the connection process for this specific machine shall be aborted.

⌊ DRAFT g The Software Cluster Connector shall de- tect, if the Software Cluster Ids of all Software Clusters belonging to same ma- chine are not unique. In this case, the connection process for this specific machine shall be aborted

⌊ DRAFT g The Software Cluster Connector shall de- tect, if for a Software Cluster any mandatory required resource is not provided by any other Software Cluster . In this case, the connection process for this specific Software Cluster shall be aborted.

⌊ DRAFT g The Software Cluster Connector shall de- tect, if for a machine a resource with the identical resource type id and identical global resource Id is provided twice by Software Clusters , none of which is a Substi- tution Software Cluster . In this case, the connection process for this specific machine shall be aborted.

⌊ DRAFT g In case the resource does not support multiple noti- fier sets, but uses Notifier Handles , the Software Cluster Connector shall detect if for a machine a resource with the identical resource type id and identical global resource Id is required more than one time. In this case, the connection process for this specific machine shall be aborted.

⌊ DRAFT g In case the resource does support multiple notifier sets, the Software Cluster Connector shall detect if for a machine a resource with the identical resource type id and identical global resource Id is required more often as notifier sets are available. In this case, the connection process for this specific machine shall be aborted.

⌊ DRAFT g In case a resource is provided by the Substitu- tion Software Cluster , the Software Cluster Connector shall connect all Software Clusters requiring the resource, except the Substitution Software Cluster itself, to the resource of the Substitution Software Cluster . This happens, regardless if another Software Cluster provides the resource as well. Nevertheless, the matching criteria defined in [SWS_SwCluC_00043] apply.

⌊ DRAFT g In case a resource is required by a Substitution Software Cluster , the Software Cluster Connector shall connect this re- quired resource only to provided resources of Software Clusters not being a Substitution Software Cluster . Nevertheless, the matching criteria defined in [SWS_SwCluC_00043] apply.

⌊ DRAFT g If the bit SWCLUC_BMANIF_DISABLE_ON_ECU_ CONNECTION in the ConnectorControlFlags of the Binary Manifest Header of the Host Software Cluster is set, the Software Cluster Connection On-board for this machine is not executed.

⌊ DRAFT g The functions SwCluC_BManif_GetH- andle , SwCluC_BManif_GetConSwClusterId , and SwCluC_BManif_Get- NoOfHandleSets , according to [SWS_SwCluC_10020], [SWS_SwCluC_10021], [SWS_SwCluC_10022], [SWS_SwCluC_10023], [SWS_SwCluC_10032], and [SWS_SwCluC_10033], shall each be implemented as a C-function-like macro.

⌊ DRAFT g <Resource Entry Group> is the shortName of either the SwCluCBManifProvideResourceEntryGroup or SwCluCBManifRe- quireResourceEntryGroup .

⌊ DRAFT g <Resource Entry> is the shortName of ei- ther the SwCluCBManifProvideResourceEntry or SwCluCBManifRequireRe- sourceEntry .

⌊ DRAFT g <Handle> is the shortName of either the SwCluCBManifProvideHandle or SwCluCBManifNotifierHandle of the SwCluCBManifResourceType , referenced by SwCluCBManifProvideRe- sourceEntryGroup or SwCluCBManifRequireResourceEntryGroup .

⌊ DRAFT g <handleType> is either • the referenced ImplementationDataType , if the SwCluCBManifHandleIm- pleTypeRef is defined for a Provide Handle of Notifier Handle . OR • uint32 , if the SwCluCBManifHandleImpleTypeRef is not defined, and SwCluCBManifNativeHandleType is set to VALUE OR • void * , if the SwCluCBManifHandleImpleTypeRef is not defined, and SwCluCBManifNativeHandleType is set to DATA_REFERENCE OR • SwCluC_BManif_VoidFncPtrType , if the SwCluCBManifHandleImple- TypeRef is not defined, and SwCluCBManifNativeHandleType is set to FUNCTION_REFERENCE

⌊ DRAFT g The function SwCluC_BManif_GetHandle ac- cording to [SWS_SwCluC_10020] shall exist for each SwCluCBManifProvide- Handle and SwCluCBManifNotifierHandle defined for each SwCluCBMan- ifProvideResourceEntry and SwCluCBManifRequireResourceEntry in a SwCluCBManifProvideResourceEntryGroup and SwCluCBManifRequireRe- sourceEntryGroup .

⌊ DRAFT g The function SwCluC_BManif_GetConSwClus- terId according to [SWS_SwCluC_10021] shall exist • for each SwCluCBManifNotifierHandle defined for each SwCluCBMan- ifProvideResourceEntry in a SwCluCBManifProvideResourceEntry- Group AND • for each SwCluCBManifProvideHandle defined for each SwCluCBManifRe- quireResourceEntry in a SwCluCBManifRequireResourceEntryGroup .

⌊ DRAFT g The function SwCluC_BManif_GetHandle ac- cording to [SWS_SwCluC_10022] shall exist for each SwCluCBManifProvide- Handle and SwCluCBManifNotifierHandle defined for each SwCluCBManif- ProvideResourceEntryGroup and SwCluCBManifRequireResourceEntry- Group .

⌊ DRAFT g The function SwCluC_BManif_GetConSwClus- terId according to [SWS_SwCluC_10023] shall exist • for each SwCluCBManifNotifierHandle defined for a SwCluCBManif- ProvideResourceEntryGroup AND • for each SwCluCBManifProvideHandle defined for a SwCluCBManifRe- quireResourceEntryGroup .

⌊ DRAFT g The function SwCluC_BManif_GetNoOfHan- dleSets according to [SWS_SwCluC_10032] shall exist for each SwCluCBMan- ifProvideResourceEntry in a SwCluCBManifProvideResourceEntryGroup where the parameter SwCluCBManifMultipleNotifierSupport is set to MULTI- PLE_NOTIFIER_SETS .

⌊ DRAFT g The function SwCluC_BManif_GetNoOfHan- dleSets according to [SWS_SwCluC_10033] shall exist for each SwCluCBMan- ifProvideResourceEntryGroup where the parameter SwCluCBManifMulti- pleNotifierSupport is set to MULTIPLE_NOTIFIER_SETS .

⌊ DRAFT g The definition SWCLUC_BMANIF_NO_OF_ENTRIES according to [SWS_SwCluC_01000] shall exist for each SwCluCBManifProvideRe- sourceEntryGroup .

⌊ DRAFT g The definition SWCLUC_BMANIF_NO_OF_NOTIFIER_SETS according to [SWS_SwCluC_01002] shall exist for each SwCluCBManifProvideRe- sourceEntry in a SwCluCBManifProvideResourceEntryGroup where the parameter SwCluCBManifMultipleNotifierSupport is set to MULTI- PLE_NOTIFIER_SETS .

⌊ DRAFT g The element ImmutableTablesChecksumPtr of the Binary Manifest Header shall reference the Immutable Tables Checksum .

⌊ DRAFT g The element TotalManifestChecksumPtr of the Binary Manifest Header shall reference the Total Manifest Checksum .

⌊ DRAFT g The element SubscribedInterfaceValidi- tyMarkerPtr of the Binary Manifest Header shall reference the Subscribed Interface Validity Marker .

⌊ DRAFT g In the Host Software Cluster , the Soft- ware Cluster Base Configuration Check of the Software Cluster Con- nection shall create one Provide Resource Entry for each configured SwCluCBaseConfigurationCheck , and add it to the Binary Manifest .

⌊ DRAFT g In the Applicative Software Cluster , the Software Cluster Base Configuration Check of the Software Cluster Connection shall create one mandatory Require Resource Entry for each con- figured SwCluCBaseConfigurationCheck , and add them to the Binary Mani- fest .

⌊ DRAFT g The SwCluCBManifResourceGuardValue of the Resource Entrys of [SWS_SwCluC_00075] and [SWS_SwCluC_00076] shall be calculated out of the given multi line strings in SwCluCAutoBaseConfigDescrip- tor and SwCluCUserBaseConfigDescriptor .

⌊ DRAFT g The Binary Manifest of the Software Clus- ter Connection shall use the <feature> = BMANIF according to [SWS_- MemMap_00040] of document [8].

⌊ DRAFT g The Binary Manifest of the Software Clus- ter Connection shall map the Binary Manifest Header to a constant, 32 bit aligned memory section named CONST_IMMUTABLE_HEADER .

⌊ DRAFT g The Binary Manifest of the Software Clus- ter Connection shall map the immutable columns of all tables to a constant, 32 bit aligned memory section named CONST_IMMUTABLE_COLUMNS . The immutable columns are: • all columns of the Interface Descriptor Table • Offered Interface Handle Column • Subscribed Interface Default Handle Column

⌊ DRAFT g The Binary Manifest of the Software Clus- ter Connection shall map the modifiable columns to a constant, 32 bit aligned memory section named CONST_MODIFIABLE_COLUMNS The modifiable columns are • Subscribed Interface Handle Column • Subscribed Interface Connected SwClusterId Column .

⌊ DRAFT g The Binary Manifest of the Software Clus- ter Connection shall map the Immutable Tables Checksum to a constant, 32 bit aligned memory section named CONST_IMMUTABLE_TABLES_CHECKSUM .

⌊ DRAFT g The Binary Manifest of the Software Clus- ter Connection shall map the Total Manifest Checksum to a constant, 32 bit aligned memory section named CONST_TOTAL_TABLES_CHECKSUM .

⌊ DRAFT g The Binary Manifest of the Soft- ware Cluster Connection shall map the Subscribed Interface Va- lidity Marker to a constant, 32 bit aligned memory section named CONST_SUBSCRIBED_TABLES_MARKER .

of the generated Binary Man- ifest . This includes • the cpSoftwareCluster reference to the given CpSoftwareCluster • the softwareClusterId of the given CpSoftwareCluster • the metaDataField s for IMMUTABLE_TABLES_CHECKSUM and SUB- SCRIBED_INTERFACE_VALIDITY_MARKER • a provideResource s for each Provide Resource Entry • a requireResource s for each Require Resource Entry • a resourceDefinition s for each Resource Type

⌊ DRAFT g Number of offered and subscribed handles, de- pending on the resource direction Provide Handle Notifier Handle SINGLE_NOTIFIER_SET One handle in the Subscribed Interface per defined SwCluCBManifNotifierHan- dle The handles are initialized with the SwCluCBManifDefaultNoti- fierSymbol s in the given order. The Software Cluster Ids are set to SWCLUC_BMANIF_UNCONNECTED MULTIPLE_NOTIFIER_SETS Provided Resource One handle in the Offered Interface per defined SwCluCBManifProvideHandle The handles are initialized with the SwCluCBManifProvideSymbol s in the given order. One handle in the Subscribed Interface per defined SwCluCBManifNotifierHan- dle multiplied by SwCluCBManifMaxNum- berOfNotifierSets plus one The first handle is initialized to 0. The remaining handles are initialized with consecutive sets of SwCluCBManifDefaultNoti- fierSymbol s in the given order. The Software Cluster Ids are set to SWCLUC_BMANIF_UNCONNECTED . Required Resource One handle in the Subscribed Interface per defined SwCluCBManifProvideHandle The handles are initialized with the SwCluCBManifDefaultPro- videSymbol s in the given order. One handle in the Offered Interface per defined SwCluCBManifNotifierHan- dle The handles are initialized with the SwCluCBManifNotifierSym- bol s in the given order. Table 7.1: Number of offered and subscribed handles, depending on the resource direction

⌊ DRAFT g In case the provided resource supports multi- ple Notifier Handle Sets , the Software Cluster Connector shall write as first entry in the Subscribed Interface Connected SwClusterId Column the value 0xFE .

The reserved bits 5 .. 0 in the element of the 'resource prop- erties' column shall be set to 0

[SWS_SwCluC_00095]

⌊ DRAFT g These requirements are not applicable to this spec- ification.

⌊ DRAFT g Symbolic name: SWCLUC_BMANIF_NO_OF_ENTRIES_<Resource Entry Group> Value: Number of Resource Entry s in the according Resource Entry Group Comments: n.a.

⌊ DRAFT g Symbolic name: SWCLUC_BMANIF_MAX_NO_OF_NOTIFIER_SETS_ <Resource Entry Group>_<Resource Entry> Value: Maximum number of notifier sets for the according Provide Resource En- try Comments: n.a.

⌊ DRAFT g The Proxy Module shall support that id values, re- quired to access the BSW service API of the Host Software Cluster , can change, without reconfiguration or rebuild of the Applicative Software Cluster using the BSW service.

⌊ DRAFT g The High Proxy shall provide the applicable Stan- dardized AUTOSAR Interfaces once per configured EcucPartition . In doing so, the APIs are provided with the orignal Mip , at the EcucPartition where the SwCluCNativeBswApi is set to true . For all the other BSW API instances, the Mip is replaced by <Mip>_<shortName of EcucPartition> .

⌊ DRAFT g The High Proxy shall create one partition specific Service Software Component per configured EcucPartition , with the name <Mip> _<EcucPartition shortName> .

⌊ DRAFT g The High Proxy shall provide the Ports belonging to a specific CpSoftwareClusterServiceResource , at the partition specific Service Software Component, to which the using SwComponentPrototype is mapped to.

⌊ DRAFT g The High Proxy shall implement a 'reasonable' be- havior for a service resource, if the connection to the resource provider does not exist. In any case, the OUT arguments of functions shall return a 'neutral' value, or the value which can be assumed after a reset. The functional behavior should be like the state directly after a reset, before further activity occured.

⌊ DRAFT g To resolve the ECU Configuration dependency, the Proxy Module implementation shall define a Vendor Specific Module Definition [10], where the ECU Configuration container and parameters are used to configure the in- terface towards the user of the substituted BSW Module.

⌊ DRAFT g The Proxy Module implementation shall define an EcucContainerDef , which defines a mapping between • the EcucContainerDef (s) identifying the module user channel in the StMD of substituted BSW Module AND • the CpSoftwareClusterServiceResource representing the user channel in the software cluster resource pool. The EcucForeignReferenceDef shall be named SwCluCResourceRef .

⌊ DRAFT g The Proxy Module implementation shall define, for each different Proxy Module, an EcucEnumerationParamDef named SwCluCProx- yGeneration<Mip> , with the literal s • PROXY_DISABLED , to disable the according Proxy Module code and AUTOSAR model generation • HIGH_PROXY , to enable the according High Proxy Module code and AUTOSAR model generation • LOW_PROXY , to enable the according Low Proxy Module code and AUTOSAR model generation

⌊ DRAFT g The Proxy Module implementation of the Soft- ware Cluster Connection shall put one Resource Entry , for each associated CpSoftwareClusterServiceResource , into the Binary Manifest .

⌊ DRAFT g The NvM High Proxy code, and related AUTOSAR model descriptions, shall only be created, if the configuration parameter SwCluCProx- yGenerationNvM is set to HIGH_PROXY .

⌊ DRAFT g The NvM High Proxy shall provide the header file NvM.h .

⌊ DRAFT g The NvM High Proxy shall provide the symbolic name values for NvBlocks, for NvM users in the Applicative Software Clus- ter .

⌊ DRAFT g The NvM Proxy shall support that the BlockIds of the NvM of Host Software Cluster can change, without reconfiguration or rebuild of the Applicative Software Cluster using these NV blocks.

⌊ DRAFT g The NvM Proxy shall support that the NV block length used in the Applicative Software Cluster can be <= the NV block length configured in the NvM of the Host Software Cluster . In case NV block length in Applicative Software Cluster is smaller, the NV block is filled with default val- ues. The default fill value of a single byte is defined by the configuration parameter SwCluCNvMProxyNvBlockFillValue .

⌊ DRAFT g The NvM Proxy shall support that the NV block length used in the Applicative Software Cluster can be changed (in the range 0 <= NV block length configured in NvM), without reconfiguration or rebuild of the Host Software Cluster .

⌊ DRAFT g In case a NV block configured in the NvM High Proxy is not connected to any NvM Low Proxy, the NvM High Proxy shall initialize the Nv RAM Block, with the default values given by NvMRomBlockDataAddress and / or NvMInitBlockCallback .

⌊ DRAFT g In case a NV block configured in the NvM Low Proxy is not connected to any NvM High Proxy, the NvM Low Proxy implementation shall ensure that the content of the NV block is not modified by the NvM Low Proxy.

⌊ DRAFT g The NvM High Proxy shall support the optional con- figuration of a NvM_SingleBlockCallbackFunction , according to [ECUC_NvM_- 00562], [ECUC_NvM_00506] and [ECUC_NvM_00559].

⌊ DRAFT g The NvM High Proxy shall support the optional configuration of a NvM_PNJF_{Block} port for NvMNotifyJobFinished notification.

⌊ DRAFT g The NvM Low Proxy shall provide an instance of a NvM_SingleBlockCallbackFunction per configured NV block ( SwCluCNvM- ProxyNvBlock ) in the NvM Low Proxy.

⌊ DRAFT g In case it is configured in the NvM High Proxy, the NvM Proxy shall invoke the NvM_SingleBlockCallbackFunction or JobFin- ished operation, when the according instance of the NvM Low Proxy is called.

⌊ DRAFT g In case a NV block configured in the NvM High Proxy is not connected to any NvM Low Proxy, the function NvM_GetErrorSta- tus of the NvM High Proxy shall still return E_OK , and the request result is set to NVM_REQ_RESTORED_FROM_ROM .

⌊ DRAFT g In case a NV block configured in the NvM High Proxy is not connected to any NvM Low Proxy, the functions • NvM_SetDataIndex • NvM_GetDataIndex • NvM_SetBlockProtection • NvM_SetRamBlockStatus • NvM_SetBlockLockStatus • NvM_CancelJobs • NvM_ReadBlock • NvM_WriteBlock • NvM_RestoreBlockDefaults • NvM_EraseNvBlock • NvM_InvalidateNvBlock • NvM_ReadPRAMBlock • NvM_WritePRAMBlock • NvM_RestorePRAMBlockDefaults of the NvM High Proxy shall return E_NOT_OK .

⌊ DRAFT g The NvM High Proxy shall support the optional configuration of a NvM_InitBlockCallbackFunction , according to [ECUC_NvM_- 00561], [ECUC_NvM_00116] and [ECUC_NvM_00559].

⌊ DRAFT g The NvM High Proxy shall support the optional configuration of a NvM_PNIB_{Block} port for NvMNotifyInitBlock notification.

⌊ DRAFT g The NvM High Proxy shall support the optional configuration of a NvM_ReadRamBlockFromNvm , according to [ECUC_NvM_00521].

⌊ DRAFT g The NvM High Proxy shall support the optional configuration of a NvM_WriteRamBlockToNvm , according to [ECUC_NvM_00520].

⌊ DRAFT g The NvM High Proxy shall support the optional con- figuration of a NvM_PM_{Block} port for NvMMirror notification.

⌊ DRAFT g The NvM High Proxy shall create one partition spe- cific Service Software Component per configured EcucPartition , with the name NvM_<EcucPartition shortName> .

⌊ DRAFT g The NvM High Proxy shall provide the Ports be- longing to a specific Nv Block • NvM_PS_{Block} • NvM_PAdmin_{Block} • NvM_PNIB_{Block} • NvM_PNJF_{Block} • NvM_PM_{Block} at the partition specific Service Software Component, to which the using SwCompo- nentPrototype is mapped.

⌊ DRAFT g In case it is configured in the NvM High Proxy, the NvM Proxy shall invoke the NvM_InitBlockCallbackFunction or InitBlock op- eration, when the according instance of the NvM Low Proxy is called.

⌊ DRAFT g In case it is configured in the NvM High Proxy, the NvM Proxy shall invoke the NvM_ReadRamBlockFromNvm function or ReadRam- BlockFromNvM operation, when the according instance of the NvM Low Proxy is called.

⌊ DRAFT g In case it is configured in the NvM High Proxy, the NvM Proxy shall invoke the NvM_WriteRamBlockToNvm function or WriteRam- BlockToNvM operation, when the according instance of the NvM Low Proxy is called.

⌊ DRAFT g The NvM High Proxy shall provide the functions for single block requests • NvM_SetDataIndex • NvM_GetDataIndex • NvM_SetBlockProtection • NvM_GetErrorStatus • NvM_SetRamBlockStatus • NvM_SetBlockLockStatus • NvM_CancelJobs • NvM_ReadBlock • NvM_WriteBlock • NvM_RestoreBlockDefaults • NvM_EraseNvBlock • NvM_InvalidateNvBlock • NvM_ReadPRAMBlock • NvM_WritePRAMBlock • NvM_RestorePRAMBlockDefaults for NvM users in the Applicative Software Cluster .

⌊ DRAFT g The NvM High Proxy shall provide the functions for single block requests, according to [SWS_SwCluC_02103], once per configured SwCluCNvMBaseSocket . In doing so, the APIs are provided with the original Mip NvM at the EcucPartition , where the SwCluCNativeBswApi is set to true . For all the other SwCluCNvMBaseSocket instances, the Mip NvM is replaced by NvM_ <shortName of EcucPartition> .

⌊ DRAFT g The NvM Low Proxy shall provide an instance of a NvM_InitBlockCallbackFunction per configured NV block ( SwCluCNvMProx- yNvBlock ) in the NvM Low Proxy.

⌊ DRAFT g The NvM Low Proxy shall provide an instance of a NvM_ReadRamBlockFromNvm per configured NV block ( SwCluCNvMProxyNvBlock ) in the NvM Low Proxy.

⌊ DRAFT g The NvM Low Proxy shall provide an instance of a NvM_WriteRamBlockToNvm per configured NV block ( SwCluCNvMProxyNvBlock ) in the NvM Low Proxy.

⌊ DRAFT g The NvM Low Proxy shall provide the entry func- tions for single block requests, according to [SWS_SwCluC_02103], once per config- ured SwCluCNvMBaseSocket at the EcucPartition configured by SwCluCNvM- BaseSocket . SwCluCProxyEcucPartitionRef . In case the SwCluCNvMProxyUsedSatelliteRef is set, the EcucPartition shall be changed, before the NVM API is called.

⌊ DRAFT g The callback instances according to [SWS_SwCluC_02111], [SWS_SwCluC_02127], [SWS_SwCluC_02128], and [SWS_SwCluC_02129], are provided • at the EcucPartition referenced by SwCluCNvMProxyNvBlock . SwCluC- NvMProxyNvBlockEcucPartitionRef , if a SwCluCNvMBaseSocket is di- rectly available at this EcucPartition OR • at the EcucPartition of the SwCluCNvMBaseSocket referenced by the SwCluCNvMBaseSocket - via SwCluCNvMProxyUsedSatelliteRef , which is on the EcucPartition given by SwCluCNvMProxyNvBlock . SwCluCNvM- ProxyNvBlockEcucPartitionRef . In this case, the EcucPartition shall be changed, before the callback in the High Proxy is called.

⌊ DRAFT g The functions • NvM_ReadBlock • NvM_WriteBlock • NvM_RestoreBlockDefaults of the NvM High Proxy shall only accept single block requests, where the pointer to the RAM data block is set to NULL_PTR . Otherwise, E_NOT_OK is returned, and the request is discarded.

⌊ DRAFT g If development error detection is enabled for NvM High Proxy, the APIs • NvM_SetDataIndex • NvM_GetDataIndex • NvM_SetBlockProtection • NvM_GetErrorStatus • NvM_SetRamBlockStatus • NvM_SetBlockLockStatus • NvM_CancelJobs • NvM_ReadBlock • NvM_WriteBlock • NvM_RestoreBlockDefaults • NvM_EraseNvBlock • NvM_InvalidateNvBlock • NvM_ReadPRAMBlock • NvM_WritePRAMBlock • NvM_RestorePRAMBlockDefaults shall report the DET error NVM_E_UNINIT , when NVM High Proxy is not yet initialized.

⌊ DRAFT g If development error detection is enabled for NvM High Proxy, the APIs • NvM_SetDataIndex • NvM_GetDataIndex • NvM_SetBlockProtection • NvM_GetErrorStatus • NvM_SetRamBlockStatus • NvM_SetBlockLockStatus • NvM_CancelJobs • NvM_ReadBlock • NvM_WriteBlock • NvM_RestoreBlockDefaults • NvM_EraseNvBlock • NvM_InvalidateNvBlock • NvM_ReadPRAMBlock • NvM_WritePRAMBlock • NvM_RestorePRAMBlockDefaults shall report the DET error NVM_E_PARAM_BLOCK_ID , when the passed BlockId is out of range of the BlockIds configured in the NvM High Proxy.

⌊ DRAFT g If development error detection is enabled for NvM High Proxy, the APIs • NvM_ReadBlock • NvM_WriteBlock • NvM_RestoreBlockDefaults shall report the DET error NVM_E_PARAM_ADDRESS , when a RAM block address dif- ferent than NULL_PTR is passed.

⌊ DRAFT g Development Error Types of SwCluC NvM Proxy The development error types defined for the SwCluC NvM Proxy are listed in table Table 7.4.

⌊ DRAFT g The NvM Low Proxy implementation shall describe the NV blocks provided to NvM High Proxies via NvBlockNeeds , derived from the Cp- SoftwareClusterServiceResource . resourceNeeds .

⌊ DRAFT g The NvM Low Proxy shall provide, for each SwCluCNvMBaseSocket , a SwCluC_NvMProxy_Init API, to initialize the NvM High Proxy of an Applicative Software Cluster . This shall be one element of the service resource SwCluCNvMBaseSocket .

⌊ DRAFT g The NvM Low Proxy code, and related AUTOSAR model descriptions, shall only be created, if the configuration parameter SwCluCProx- yGenerationNvM is set to LOW_PROXY .

[SWS_SwCluC_02147] Upstream requirements: SRS_SwCluC_00206 ⌈The NvM High Proxy of a specific Application Software Cluster shall en- able the configuration ID check, if the parameter NvMDynamicConfigura- tion is set to TRUE in this Application Software Cluster.⌋ Note: The parameter NvMDynamicConfiguration is set in the NvM module config- uration of the respective Application Software Cluster. Like in the configuration of the NvM module in the Host Software Cluster, the block ID 1 is reserved for the Configuration ID block in each Application Software Cluster. This Configuration ID block to contain the stored NVRAM configuration ID. module

[SWS_SwCluC_02149] Upstream requirements: SRS_SwCluC_00206 ⌈The NvM High Proxy of a specific Application Software Cluster shall im- plement the Configuration ID block as redundant type with CRC32.⌋

[SWS_SwCluC_02150] Upstream requirements: SRS_SwCluC_00206 ⌈The job of the function NvM_WriteBlock for the Configuration ID block shall write the compiled NVRAM configuration ID to the stored NVRAM configura- tion ID (in the Configuration ID blocks) of this Application Software Cluster.⌋

[SWS_SwCluC_02151] Upstream requirements: SRS_SwCluC_00206 ⌈The job of the function NvM_WritePRAMBlock for the Configuration ID block shall write the compiled NVRAM configuration ID to the stored NVRAM configu- ration ID (in the Configuration ID blocks) of this Application Software Cluster.⌋

[SWS_SwCluC_02152] Upstream requirements: SRS_SwCluC_00206 ⌈The NvM_ReadRamBlockFromNvm call for the Configuration ID block shall validate the configuration ID by comparing the stored NVRAM configuration ID of this Application Software Cluster vs. the compiled NVRAM configuration ID of this Application Software Cluster.⌋

[SWS_SwCluC_02161] Unconnected-behavior of NvM_SingleBlockCallbackFunction Upstream requirements: SRS_SwCluC_00206, SRS_SwCluC_00213 ⌈TheNvM_SingleBlockCallbackFunction of NvM Low Proxy shall return E_NOT_OK, if the corresponding NV Block is not connected to an instance in the NvM High Proxy.⌋ module

[SWS_SwCluC_02162] Unconnected-behavior of NvM_InitBlockCallbackFunction Upstream requirements: SRS_SwCluC_00206, SRS_SwCluC_00213 ⌈TheNvM_InitBlockCallbackFunction of NvM Low Proxy shall return E_NOT_OK, if the corresponding NV Block is not connected to an instance in the NvM High Proxy.⌋

[SWS_SwCluC_02163] Unconnected-behavior of NvM_ReadRamBlockFromNvm Upstream requirements: SRS_SwCluC_00206, SRS_SwCluC_00213 ⌈TheNvM_ReadRamBlockFromNvm of NvM Low Proxy shall return E_NOT_OK, if the corresponding NV Block is not connected to an instance in the NvM High Proxy.⌋

[SWS_SwCluC_02164] Unconnected-behavior of NvM_WriteRamBlockToNvm Upstream requirements: SRS_SwCluC_00206, SRS_SwCluC_00213 ⌈TheNvM_WriteRamBlockToNvm of NvM Low Proxy shall return E_NOT_OK, if the corresponding NV Block is not connected to an instance in the NvM High Proxy.⌋

⌊ DRAFT g The OS High Proxy code, and related AUTOSAR model descriptions, shall only be created, if the configuration parameter SwCluCProx- yGenerationOs is set to HIGH_PROXY .

⌊ DRAFT g The OS LOW Proxy code, and related AUTOSAR model descriptions, shall only be created, if the configuration parameter SwCluCProx- yGenerationOs is set to LOW_PROXY .

⌊ DRAFT g The Os Proxy shall support the execution of Os- Tasks from an Applicative Software Cluster , in the context of the Host Software Cluster .

⌊ DRAFT g The Os Proxy shall support a socket mechanism to hook several Applicative Software Clusters onto the Host Software Cluster .

⌊ DRAFT g The Os High Proxy interfaces shall be described with the parameters, and according containers, as defined in Os EcucModuleDef .

⌊ DRAFT g The Os Proxy interfaces shall be configured as a service resource, with the parameters as defined in the SwCluCOsProxy container.

⌊ DRAFT g The Os High Proxy shall provide the header file Os.h and Os_Cfg.h .

⌊ DRAFT g The Os High Proxy shall provide a proxy Os- Task , to which events from the Applicative Software Cluster can be mapped, during the design of an Applicative Software Cluster .

⌊ DRAFT g The Os High Proxy shall provide a set of Os- Task specific APIs that are required by the Applicative Software Cluster : • ActivateTask • ChainTask • TerminateTask

⌊ DRAFT g If SwCluCOsProxyOsTask . SwCluCOsProxy- TaskActivation . PASS_TASK_ACTIVATION is set for a specific OsTask , the API ActivateTask called for this OS task shall trigger a task activation in the Host Software Cluster .

⌊ DRAFT g The API for ChainTask shall be implemented as macro with a return statement in the Applicative Software Cluster , to be used in the context of the task body, and will end the execution of the proxy task.

⌊ DRAFT g The API for TerminateTask shall be imple- mented as macro with a return statement in the Applicative Software Cluster , to be used in the context of the task body, to be able to end the proxy tasks execution.

⌊ DRAFT g The Os High Proxy shall provide default han- dles for resources, in case a connection to the host system could not be established successfully between Applicative Software Cluster and the Host Software Cluster . The default implementation shall be a neutral behavior, with the return value E_OK , to support "standard status" from OS.

⌊ DRAFT g The Os High Proxy shall have a service re- source SwCluCOsProxyOsTask , for each OsTask required in the Applicative Software Cluster . For this resource, an entry in the Binary Manifest shall be created, to be able to link the task to its OsLowProxy implementation in the Host Software Cluster . Since the content of the OsTask is created by the RTE, this API shall be used and registered as service resource. It is recommended that this resource is marked with the mandatory flag ( SwCluCBManifIsMandatory ).

⌊ DRAFT g The Os High Proxy shall contain a required ser- vice resource SwCluCOsProxyOsTaskDispatcher . The Proxy-OsTask shall be called in that context. For this resource, an entry in the Binary Manifest shall be created, to be able to link it to the OsLowProxy dispatcher in the Host Software Cluster . It is recommended that this resource is marked with the mandatory flag ( SwCluCBManifIsMandatory ).

⌊ DRAFT g The Os High Proxy shall contain a required ser- vice resource SwCluCOsProxyFunctionDispatcher . This function dispatcher is used to call functions in context of the Host Software Cluster . For this resource, an entry in the Binary Manifest shall be created, to be able to link it to the OsLow- Proxy dispatcher in the Host Software Cluster .

⌊ DRAFT g The Os High Proxy shall contain a required ser- vice resource SwCluCOsProxyOsBaseSocket . This collects all hooks needed to be linked to the Host Software Cluster . It also contains Applicative Software Cluster local Os specific functions for StartOs, initialize and shutdown. It should also cover the local IOC , if present. It is recommended that this resource is marked with the mandatory flag ( SwCluCBManifIsMandatory ).

⌊ DRAFT g Since a Applicative Software Cluster can contain several OS Applications , the Os High Proxy shall be able to provide a local IOC implementation for the cluster internal communication paths between OS Applications . The link to the Host Software Cluster shall be established as part of the SwCluCOsProxyOsBaseSocket service resource.

⌊ DRAFT g The Os High Proxy shall require a service re- source SwCluCOsProxyOsApplication , which is used in the Applicative Software Cluster , and needs to be matched to the Host Software Cluster .

⌊ DRAFT g The Os High Proxy shall require a service re- source SwCluCOsProxyOsResource , which is used in the Applicative Soft- ware Cluster , and needs to be matched to the Host Software Cluster .

⌊ DRAFT g The Os High Proxy shall require a service re- source SwCluCOsProxyOsSpinlock , which is used in the Applicative Soft- ware Cluster , and needs to be matched to the Host Software Cluster .

⌊ DRAFT g The Os High Proxy shall provide the following APIs for the Applicative Software Cluster : • GetResource • ReleaseResource • SuspendOSInterrupts • ResumeOSInterrupts • GetSpinlock • ReleaseSpinlock • GetApplicationID Each of these APIs corresponds to a service resource in the Os Low Proxy. There will be an entry in the Binary Manifest , to require these service resources, which are described here: SwCluCOsProxy .

⌊ DRAFT g The Os High Proxy shall NOT support the fol- lowing APIs for the Applicative Software Cluster . • StartScheduleTable • StopScheduleTable • Schedule • DisableAllInterrupts • EnableAllInterrupts • SuspendAllInterrupts • ResumeAllInterrupts

⌊ DRAFT g The configuration of the Os High Proxy for a complete Applicative Software Cluster shall be specified with a set of ECUC- parameters defined here: SwCluCOsProxy .

⌊ DRAFT g If SwCluCOsProxyOsTask . SwCluCOsProxy- TaskActivation . OMIT_TASK_ACTIVATION is set for a specific OsTask , the API ActivateTask called for this OS task returns without effect.

⌊ DRAFT g The Os High Proxy shall support the implemen- tation of a task body of the proxy OsTask , with the TASK() macro.

⌊ DRAFT g The Os Low Proxy shall only be provided by the Host Software Cluster .

⌊ DRAFT g The configuration of the Os Low Proxy for a com- plete Host Software Cluster shall be specified with a set of ECUC-parameters defined here: SwCluCOsProxy . The configuration of the Os Low Proxy shall be de- rived from the implemented configuration for the Os in the Host Software Clus- ter .

⌊ DRAFT g The Os Low Proxy shall provide a socket for the Os High Proxys of the Applicative Software Clusters . For each Applicative Software Cluster , a corresponding service resource SwClu- COsProxyOsBaseSocket and configuration shall be provided.

⌊ DRAFT g The Os Low Proxy shall provide for each SwCluCOsProxyOsBaseSocket a SwCluC_OsProxy_Init API, to initialize the Os High Proxy of an Applicative Software Cluster . This shall be one element of the service resource SwCluCOsProxyOsBaseSocket .

⌊ DRAFT g The Os Low Proxy shall provide an API to start the Os High Proxy of an Applicative Software Cluster . This shall be one element of the service resource SwCluCOsProxyOsBaseSocket .

⌊ DRAFT g The Os Low Proxy shall provide an API to shut- down the Os High Proxy of an Applicative Software Cluster . This shall be one element of the service resource SwCluCOsProxyOsBaseSocket .

⌊ DRAFT g The Os Low Proxy shall be able to provide an API to connect IOC from Os High Proxy of an Applicative Software Clus- ter . This shall be one element of the service resource SwCluCOsProxyOsBas- eSocket .

⌊ DRAFT g The Os Low Proxy shall provide a task dis- patcher, to call the connected Os High Proxy from Applicative Software Cluster .

⌊ DRAFT g The Os Low Proxy shall provide a service resource SwCluCOsProxyOsTaskDispatcher, for each Applicative Software Clusters configuration that the system shall be prepared for.

⌊ DRAFT g The Os Low Proxy shall provide a service re- source SwCluCOsProxyOsTask , for each Applicative Software Clusters task configuration that the system shall be prepared for. For this resource, an en- try in the Binary Manifest shall be created, to be able to link it to the Os High Proxy task in the Host Software Cluster .

⌊ DRAFT g The Os Low Proxy shall provide a function dis- patcher, to call the connected Os High Proxy from Applicative Software Cluster , to trigger general function calls.

⌊ DRAFT g The Os Low Proxy shall provide a service re- source SwCluCOsProxyOsFunctionDispatcher , for each Applicative Soft- ware Clusters configuration that the system shall be prepared for.

⌊ DRAFT g The Os Low Proxy shall provide a service re- source SwCluCOsProxyOsApplication , for each OsApplication that is con- figured in the Host Software Cluster , and prepared for use in Applicative Software Clusters .

⌊ DRAFT g The Os Low Proxy shall provide a service re- source SwCluCOsProxyOsResource , for each OsResource used in Applicative Software Clusters .

⌊ DRAFT g The Os Low Proxy shall provide a service re- source SwCluCOsProxyOsSpinlock , for each OsSpinlock used in Applicative Software Clusters .

⌊ DRAFT g The Os Low Proxy shall provide a basic service implementation for the following APIs, to be used and connected with an Applica- tive Software Cluster : • GetResource • ReleaseResource • SuspendOSInterrupts • ResumeOSInterrupts • ReleaseResource • GetSpinlock • ReleaseSpinlock • GetApplicationID These APIs shall be provided with a corresponding service resource from SwClu- COsProxy .

⌊ DRAFT g The Os Low Proxy shall provide default handles for resources, in case a connection could not be established successfully between Applicative Software Cluster and the Host Software Cluster .

The Os Low Proxy shall have a service resource SwClu- COsProxyOsTaskDispatcher , for each task dispatcher provided in the Host Software Cluster . For this resource, an entry in the Binary Manifest shall be created, to be able to link the task dispatcher to its Os High Proxy implementation in the Applicative Software Cluster .

The Os Low Proxy shall have a service resource SwClu- COsProxyFunctionDispatcher , for each function dispatcher provided in the Host Software Cluster . For this resource, an entry in the Binary Manifest shall be created, to be able to link the function dispatcher to its Os High Proxy implementa- tion in the Applicative Software Cluster .

The Os Low Proxy shall create one partition specific Ser- vice Software Component per configured EcucPartition for the dispatcher, with the name SwCluC_Dispatcher_<EcucPartition shortName> .

The Os Low Proxy shall create one RunnableEntity per configured SwCluCOsProxyOsTaskDispatcher container in the partition specific Service Software Component according [SWS_SwCluC_02272]. The EcucPartition is determined by the parameter SwCluCOsProxyEcucParti- tionRef , if configured or alternatively by the EcucPartition to which the related OsTask belongs. The attributes of the RunnableEntity shall be set as following: • minimumStartInterval is set to the parameter value SwCluCOsProxyMin- imumStartInterval • symbol is set to the name of the task dispatcher's C-function used for implemen- tation of [SWS_SwCluC_02270] • canBeInvokedConcurrently is set to false

The Os Low Proxy shall create one BackgroundE- vent per configured SwCluCOsProxyDispatcherBackgroundEvent con- tainer in the partition specific Service Software Component according [SWS_SwCluC_02272]. The attributes of the BackgroundEvent shall be set as following: • shortName is set according the container's shortName • startOnEvent is set to the RunnableEntity according [SWS_SwCluC_02273] related to the owning SwCluCOsProxyOsTaskDis- patcher container. • disabledMode (s) are created according the SwCluCOsProxyDisabledMod- eInstanceRef (s) where for each different PPortPrototype an RPortPro- totype is created at the owing Service Software Component according [SWS_SwCluC_02272] and used as contextPort .

The Os Low Proxy shall create one TimingEvent per configured SwCluCOsProxyDispatcherTimingEvent container in the partition specific Service Software Component according [SWS_SwCluC_02272]. The attributes of the TimingEvent shall be set as following: • shortName is set according the container's shortName • startOnEvent is set to the RunnableEntity according [SWS_SwCluC_02273] related to the owning SwCluCOsProxyOsTaskDis- patcher container • period value is set according the SwCluCOsProxyTimingEventPeriod pa- rameter • disabledMode (s) are created according the SwCluCOsProxyDisabledMod- eInstanceRef (s) where for each different PPortPrototype an RPortPro- totype is created at the owing Service Software Component according [SWS_SwCluC_02272] and used as contextPort .

The Os Low Proxy shall create one SwcMod- eSwitchEvent per configured SwCluCOsProxyDispatcherModeSwitchEvent container in the partition specific Service Software Component according [SWS_SwCluC_02272]. The attributes of the SwcModeSwitchEvent shall be set as following: • shortName is set according the container's shortName • startOnEvent is set to the RunnableEntity according [SWS_SwCluC_02273] related to the owning SwCluCOsProxyOsTaskDis- patcher container • activation value is set according the SwCluCOsProxyDispatcherActiva- tion parameter • mode s are created according the SwCluCOsProxyModeInstanceRef (s) where for each different PPortPrototype an RPortPrototype is created at the owing Service Software Component according [SWS_SwCluC_02272] and used as contextPort . • disabledMode (s) are created according the SwCluCOsProxyDisabledMod- eInstanceRef (s) where for each different PPortPrototype an RPortPro- totype is created at the owing Service Software Component according [SWS_SwCluC_02272] and used as contextPort .

The Os Low Proxy shall create one ExternalTrigge- rOccurredEvent per configured SwCluCOsProxyDispatcherExternalTrig- gerOccurredEvent container in the partition specific Service Software Com- ponent according [SWS_SwCluC_02272]. The attributes of the ExternalTrigge- rOccurredEvent shall be set as following: • shortName is set according the container's shortName • startOnEvent is set to the RunnableEntity according [SWS_SwCluC_02273] related to the owning SwCluCOsProxyOsTaskDis- patcher container • trigger is set according the SwCluCOsProxyTriggerInstanceRef where for each different PPortPrototype an RPortPrototype is created at the owing Service Software Component according [SWS_SwCluC_02272] and used as contextRPort . • disabledMode (s) are created according the SwCluCOsProxyDisabledMod- eInstanceRef (s) where for each different PPortPrototype an RPortPro- totype is created at the owing Service Software Component according [SWS_SwCluC_02272] and used as contextPort .

[SWS_SwCluC_02278]

[SWS_SwCluC_02279]

[SWS_SwCluC_02284] SwCluCBManifProvideResourceEntryGroup for SwCluCOsProxyOsTask ⌈For the Os Low Proxy, there shall be a SwCluCBManif- ProvideResourceEntryGroup, whose SwCluCBManifResourceTypeRef shall refer to a SwCluCBManifResourceType that contains one SwCluCBManifNoti- fierHandle, with SwCluCBManifNativeHandleType set to FUNCTION_REFER- ENCE. The SwCluCBManifMultipleNotifierSupport shall be set to MULTIPLE_- NOTIFIER_SETS.⌋

[SWS_SwCluC_02285] Semantics of SwCluCOsProxyMaxNumberOfCallee Upstream requirements: SRS_SwCluC_00214 ⌈For each SwCluCOsProxyOsTask, the Os Low Proxy shall put a SwCluCBMan- ifProvideResourceEntry into the binary manifest. If the proxy task’s SwCluCOsProxyOsTaskDispatcher has SwCluCOsProxy- MaxNumberOfCallee set to a value bigger than 1, the provide entry shall be placed in the SwCluCBManifProvideResourceEntryGroup defined in

⌊ DRAFT g The Dcm High Proxy shall provide the header file Dcm.h .

⌊ DRAFT g The Dcm High Proxy shall support the con- figuration of DataServices_{Data} RPortPrototype s for synchronous ClientServerInterface DataServices_{Data} for a SwCluCDcmProxyDi- agnosticData referencing via SwCluCDcmProxyDataRef a DcmDspData or a DcmDspPidService01 .

⌊ DRAFT g The Dcm High Proxy shall support the con- figuration of DataServices_{Data} RPortPrototype s for asynchronous ClientServerInterface DataServices_{Data} without parameter Error- Code .

⌊ DRAFT g The Dcm High Proxy shall support the con- figuration of DataServices_{Data} RPortPrototype s for asynchronous ClientServerInterface DataServices_{Data} with parameter ErrorCode .

⌊ DRAFT g In case the SwCluCDcmProxyDiagnosticData channel related to a DataServices_{Data} PortPrototype s is connected, the Dcm Proxy shall invoke the • ReadData operation , when the corresponding Xxx_ReadData API is called in the Dcm Low Proxy , OR • WriteData operation , when the corresponding Xxx_WriteData API is called in the Dcm Low Proxy , OR • ReadDataLength operation , when the corresponding Xxx_ReadDataL- ength API is called in the Dcm Low Proxy , OR • ConditionCheckRead operation , when the corresponding Xxx_Condi- tionCheckRead API is called in the Dcm Low Proxy , OR • GetScalingInformation operation , when the corresponding Xxx_- GetScalingInformation API is called in the Dcm Low Proxy , OR • ReturnControlToEcu operation , when the corresponding Xxx_Return- ControlToEcu API is called in the Dcm Low Proxy , OR • ResetToDefault operation , when the corresponding Xxx_ResetToDe- fault API is called in the Dcm Low Proxy , OR • FreezeCurrentState operation , when the corresponding Xxx_Freeze- CurrentState API is called in the Dcm Low Proxy , OR • ShortTermAdjustment operation , when the corresponding Xxx_Short- TermAdjustment API is called in the Dcm Low Proxy . In that case, IN arguments ( Data (if applicable), OpStatus (if applicable), control- Mask (if applicable) and ControlStateInfo (if applicable)) are passed to the client, and OUT arguments ( Data (if applicable), ScalingInfo (if applicable), ErrorCode (if applicable)) and application errors are transferred back to the caller of the Dcm Low Proxy .

⌊ DRAFT g In case the operation s in the DataSer- vices_{Data} ClientServerInterface do not have a controlMask argu- ment configured, the value is discarded without checking the passed control- MaskLength .

⌊ DRAFT g In case the operation s in the DataSer- vices_{Data} ClientServerInterface do not have an ErrorCode argument configured, the default value DCM_POS_RESP is transferred back to the caller of the Dcm Low Proxy in case the caller returned E_OK .

⌊ DRAFT g In case the DataServices_{Data} RPortPro- totype is unconnected, the application error E_NOT_OK and the Error- Code DCM_E_REQUESTOUTOFRANGE is transferred back to the caller of the Dcm Low Proxy .

⌊ DRAFT g In case the passed DataLength , ScalingIn- foLength , or controlMaskLength (if applicable, see [SWS_SwCluC_02305]) of the caller of the Dcm Low Proxy do not match the configured data size in the Dcm configuration in the Applicative Software Cluster , the application error E_NOT_OK and the ErrorCode DCM_E_REQUESTOUTOFRANGE is transferred back to the caller of the Dcm Low Proxy . No data , scalingInfo or controlMask values shall be transferred in this case.

⌊ DRAFT g The Dcm High Proxy shall support the configu- ration of DataServices_{Data} RPortPrototype s for SenderReceiverInter- face / NvDataInterface DataServices_{Data} .

⌊ DRAFT g The Dcm High Proxy shall support the configu- ration of DataServices_{Data} PPortPrototype s for SenderReceiverInter- face / NvDataInterface DataServices_{Data} .

⌊ DRAFT g The Dcm High Proxy shall support the config- uration of DataServices_{Data} PRPortPrototype s for SenderReceiverIn- terface / NvDataInterface DataServices_{Data} .

⌊ DRAFT g In case the SwCluCDcmProxyDiagnosticData channel related to a DataServices_{Data} PortPrototype s is connected, the Dcm Proxy shall • read the dataElement / nvData , when the corresponding Xxx_ReadData API is called in the Dcm Low Proxy , OR • write the dataElement / nvData , when the corresponding Xxx_WriteData API is called in the Dcm Low Proxy . In that case IN argument Data (if applicable) is sent to the receiver, and OUT argument Data (if applicable) is transferred back to the caller of the Dcm Low Proxy .

⌊ DRAFT g In case the DataServices_{Data} Sender- ReceiverInterface / NvDataInterface is configured, the default value DCM_POS_RESP as ErrorCode is transferred back to the caller of the Dcm Low Proxy for any connected RPortPrototype and any connected or unconnected PPortPrototype or PRPortPrototype .

⌊ DRAFT g In case the DataServices_{Data} RPortPro- totype , PPortPrototype or PRPortPrototype is unconnected, the return value E_NOT_OK and the ErrorCode DCM_E_REQUESTOUTOFRANGE is transferred back to the caller of the Dcm Low Proxy .

⌊ DRAFT g In case the passed DataLength of the caller of the Dcm Low Proxy does not match the configured data size in the Dcm configuration in the Applicative Software Cluster , the return value E_NOT_OK and the ErrorCode DCM_E_REQUESTOUTOFRANGE is transferred back to the caller of the Dcm Low Proxy . No data shall be transferred in this case.

⌊ DRAFT g The Dcm High Proxy shall support the configu- ration of DataServices_{DID} RPortPrototype s for SenderReceiverInter- face DataServices_{DID} .

⌊ DRAFT g The Dcm High Proxy shall support the configu- ration of DataServices_{DID} PPortPrototype s for SenderReceiverInter- face DataServices_{DID} .

⌊ DRAFT g The Dcm High Proxy shall support the configu- ration of DataServices_{DID} PRPortPrototype s for SenderReceiverInter- face DataServices_{DID} .

⌊ DRAFT g In case the SwCluCDcmProxyDiagnosticData channel related to a DataServices_{DID} PortPrototype s is connected, the Dcm Proxy shall • read the dataElement , when the corresponding Xxx_ReadData API is called in the Dcm Low Proxy , OR • write the dataElement , when the corresponding Xxx_WriteData API is called in the Dcm Low Proxy , In that case, IN argument Data (if applicable) is sent to the receiver and OUT argument Data (if applicable) is transferred back to the caller of the Dcm Low Proxy .

⌊ DRAFT g In case the DataServices_{DID} Sender- ReceiverInterface is configured, the default value DCM_POS_RESP as Error- Code is transferred back to the caller of the Dcm Low Proxy for any connected RPortPrototype and any connected or unconnected PPortPrototype or PR- PortPrototype .

⌊ DRAFT g In case the DataServices_{DID} RPortPro- totype is unconnected, the return value E_NOT_OK and the ErrorCode DCM_E_REQUESTOUTOFRANGE is transferred back to the caller of the Dcm Low Proxy .

⌊ DRAFT g In case the passed DataLength of the caller of the Dcm Low Proxy does not match the configured data size in the Dcm configuration in the Applicative Software Cluster , the return value E_NOT_OK and the ErrorCode DCM_E_REQUESTOUTOFRANGE is transferred back to the caller of the Dcm Low Proxy . No data shall be transferred in this case.

⌊ DRAFT g The Dcm High Proxy shall support the configu- ration of IOControlRequest_{DID} RPortPrototype s for SenderReceiverIn- terface IOControlRequest_{DID} .

⌊ DRAFT g The Dcm High Proxy shall support the configu- ration of IOControlResponse_{DID} RPortPrototype s for SenderReceiver- Interface IOControlResponse_{DID} .

⌊ DRAFT g In case the SwCluCDcmProxyDiagnostic- Data channel, related to a IOControlRequest_{DID} and IOControlRe- sponse_{DID} sender-receiver port, is connected, the Dcm Proxy shall: • calculate the underControl , IOOperationRequest and controlState data elements, according to [SWS_Dcm_01435], [SWS_Dcm_00682], [SWS_- Dcm_01436], [SWS_Dcm_01437], [SWS_Dcm_01438], [SWS_Dcm_01275], [SWS_Dcm_01277] AND • return the IOOperationResponse , according to [SWS_Dcm_01439], [SWS_- Dcm_01440], and [SWS_Dcm_01441], when the corresponding Xxx_Read- Data , Xxx_WriteData , Xxx_ReturnControlToEcu , Xxx_ResetToDe- fault , Xxx_FreezeCurrentState , or Xxx_ShortTermAdjustment API is called in the Dcm Low Proxy .

⌊ DRAFT g The Dcm High Proxy shall support the configuration of RoutineServices_{RoutineName} RPortPrototype s for ClientServerInterface RoutineServices_{RoutineName} .

⌊ DRAFT g In case the SwCluCDcmProxyRoutineControl channel related to a RoutineServices_{RoutineName} RPortPrototype s is connected, the Dcm Proxy shall invoke the • Start operation , when the corresponding Xxx_Start API is called in the Dcm Low Proxy , OR • StartConfirmation operation , when the corresponding Xxx_StartCon- firmation API is called in the Dcm Low Proxy , OR • Stop operation , when the corresponding Xxx_Stop API is called in the Dcm Low Proxy , OR • StopConfirmation operation , when the corresponding Xxx_StopConfir- mation API is called in the Dcm Low Proxy , OR • RequestResults operation , when the corresponding Xxx_RequestRe- sults API is called in the Dcm Low Proxy , OR • RequestResultsConfirmation operation , when the corresponding Xxx_- RequestResultsConfirmation API is called in the Dcm Low Proxy , In this case, INOUT arguments ( dataInOut (if applicable)) are used to transfer the individual dataIn signals to the client, and to transfer back the individual dataOut signals as joint array to the caller of the Dcm Low Proxy . The configuration of the operation s in the ClientServerInterface s is according to the Dcm configura- tion of the Applicative Software Cluster . Additionally, IN arguments OpSta- tus (if applicable) and ConfirmationStatus (if applicable) are passed to the client, and OUT arguments ErrorCode (if applicable) and application errors are trans- ferred back to the caller of the Dcm Low Proxy .

⌊ DRAFT g In case the RoutineSer- vices_{RoutineName} RPortPrototype is unconnected, the return value E_NOT_OK and the ErrorCode DCM_E_REQUESTOUTOFRANGE (if applicable) is transferred back to the caller of the Dcm Low Proxy .

⌊ DRAFT g In case the passed DataLength of the caller of the Dcm Low Proxy does not match the configured data size in the Dcm configuration in the Applicative Software Cluster , the return value E_NOT_OK and the ErrorCode DCM_E_REQUESTOUTOFRANGE is transferred back to the caller of the Dcm Low Proxy . No data shall be transferred in this case.

⌊ DRAFT g The Dcm High Proxy shall support the configu- ration of ServiceRequestManufacturerNotification_{Name} RPortProto- type s for ClientServerInterface ServiceRequestManufacturerNotifi- cation_{Name} .

⌊ DRAFT g The Dcm High Proxy shall support the con- figuration of ServiceRequestSupplierNotification_{Name} RPortProto- type s for ClientServerInterface ServiceRequestSupplierNotifica- tion_{Name} .

⌊ DRAFT g In case the SwCluCDcmProxySer- viceRequestNotification channel related to a ServiceRequestManu- facturerNotification_{Name} or ServiceRequestSupplierNotifica- tion_{Name} RPortPrototype s is connected, the Dcm Proxy shall invoke the • Confirmation operation , when the corresponding Xxx_Confirmation API is called in the Dcm Low Proxy , OR • Indication operation , when the corresponding Xxx_Indication API is called in the Dcm Low Proxy . In this case, IN arguments [ SID (if applicable), ReqType (if applicable), Connec- tionId (if applicable), ConfirmationStatus (if applicable), ProtocolType (if applicable), TesterSourceAddress (if applicable), RequestData (if applicable), DataSize (if applicable)] are passed to the client and OUT arguments [ ErrorCode (if applicable)] and application errors are transferred back to the caller of the Dcm Low Proxy .

⌊ DRAFT g In case the ServiceRequestManufac- turerNotification_{Name} or ServiceRequestSupplierNotifica- tion_{Name} RPortPrototype is unconnected, the return value E_NOT_OK and the ErrorCode DCM_E_REQUESTOUTOFRANGE (if applicable) is transferred back to the caller of the Dcm Low Proxy .

⌊ DRAFT g The Dcm High Proxy code, and related AUTOSAR model descriptions, shall only be created if the configuration parame- ter SwCluCProxyGenerationDcm is set to HIGH_PROXY .

⌊ DRAFT g The Dcm Low Proxy code, and related AUTOSAR model descriptions, shall only be created if the configuration parame- ter SwCluCProxyGenerationDcm is set to LOW_PROXY .

⌊ DRAFT g The Dcm High Proxy shall create one partition specific Service Software Component per configured EcucPartition , with the name Dcm_<EcucPartition shortName> .

⌊ DRAFT g The Dcm High Proxy shall provide the Ports be- longing to a specific interface connection at the partition specific Service Software Component, at the given EcucPartition of the proxy channel, configured via • SwCluCDcmProxyDiagnosticData . SwCluCProxyEcucPartitionRef OR • SwCluCDcmProxyRoutineControl . SwCluCProxyEcucPartitionRef OR • SwCluCDcmProxyServiceRequestNotification . SwCluCProxyEcuc- PartitionRef

⌊ DRAFT g The Dcm Low Proxy shall provide an instance of a Xxx_ReadData function per configured SwCluCDcmProxyDiagnosticData con- tainer in the Dcm Low Proxy , if the diagnostic data element read access is enabled.

⌊ DRAFT g The Xxx_ReadData function shall be named SwCluC_DcmProxy_ReadData_<DDSN> , where <DDSN> is the shortName of the SwCluCDcmProxyRoutineControl container.

⌊ DRAFT g The diagnostic data element read ac- cess for a SwCluCDcmProxyDiagnosticData is enabled, if: • SwCluCDcmProxyDataRef references a DcmDspData AND the corresponding DcmDspDid has a DcmDspDidRead configured in its related DcmDspDidInfo OR • SwCluCDcmProxyDataRef references a DcmDspDid , which has a DcmDsp- DidRead configured in its related DcmDspDidInfo OR • SwCluCDcmProxyDataRef references a DcmDspPidService01 OR • SwCluCDcmProxyDataRef references a DemDataElementClass

⌊ DRAFT g The Dcm Low Proxy shall provide an instance of a Xxx_WriteData function per configured SwCluCDcmProxyDiagnosticData container in the Dcm Low Proxy , if the diagnostic data element write ac- cess is enabled.

⌊ DRAFT g The Xxx_WriteData function shall be named SwCluC_DcmProxy_WriteData_<DDSN> , where <DDSN> is the shortName of the SwCluCDcmProxyRoutineControl container.

⌊ DRAFT g The diagnostic data element write ac- cess for a SwCluCDcmProxyDiagnosticData is enabled, if: • SwCluCDcmProxyDataRef references a DcmDspData AND the corresponding DcmDspDid has a DcmDspDidWrite configured in its related DcmDspDidInfo OR • SwCluCDcmProxyDataRef references a DcmDspDid , which has a DcmDsp- DidWrite configured in its related DcmDspDidInfo

⌊ DRAFT g The Dcm Low Proxy shall provide an instance of a Xxx_ReadDataLength function per configured SwCluCDcmProxyDiagnostic- Data container in the Dcm Low Proxy , if the diagnostic data element read data length access is enabled.

⌊ DRAFT g The Xxx_ReadDataLength function shall be named SwCluC_DcmProxy_ReadDataLength_<DDSN> , where <DDSN> is the shortName of the SwCluCDcmProxyRoutineControl container.

⌊ DRAFT g The diagnostic data element read data length access for a SwCluCDcmProxyDiagnosticData is enabled, if: • SwCluCDcmProxyDataRef references a DcmDspData AND the corresponding DcmDspDid has a DcmDspDidRead configured in its related DcmDspDidInfo AND • the DcmDspDataType is set to UINT8_DYN .

⌊ DRAFT g The Dcm Low Proxy shall provide an instance of a Xxx_ConditionCheckRead function per configured SwCluCDcmProxyDiag- nosticData container in the Dcm Low Proxy , if the diagnostic data element condition check read access is enabled.

⌊ DRAFT g The Xxx_ConditionCheckRead function shall be named SwCluC_DcmProxy_ConditionCheckRead_<DDSN> , where <DDSN> is the shortName of the SwCluCDcmProxyRoutineControl container.

⌊ DRAFT g The diagnostic data element condition check read access for a SwCluCDcmProxyDiagnosticData is enabled, if: • SwCluCDcmProxyDataRef references a DcmDspData AND the corresponding DcmDspDid has a DcmDspDidRead configured in its related DcmDspDidInfo AND • the parameter DcmDspDataConditionCheckReadFncUsed is set to true .

⌊ DRAFT g The Dcm Low Proxy shall provide an instance of a Xxx_GetScalingInformation function per configured SwCluCDcmProxyDiag- nosticData container in the Dcm Low Proxy , if the diagnostic data element scaling information access is enabled.

⌊ DRAFT g The Xxx_GetScalingInformation function shall be named SwCluC_DcmProxy_GetScalingInformation_<DDSN> , where <DDSN> is the shortName of the SwCluCDcmProxyRoutineControl container.

⌊ DRAFT g The diagnostic data element scaling information access for a SwCluCDcmProxyDiagnosticData is enabled, if: • SwCluCDcmProxyDataRef references a DcmDspData AND • the corresponding DcmDspDataScalingInfoSize is configured in its related DcmDspDataInfo .

⌊ DRAFT g The Dcm Low Proxy shall provide an instance of a Xxx_ReturnControlToECU function per configured SwCluCDcmProxyDiag- nosticData container in the Dcm Low Proxy , if the diagnostic data element return control to ECU is enabled.

⌊ DRAFT g The Xxx_ReturnControlToECU function shall be named SwCluC_DcmProxy_ReturnControlToECU_<DDSN> , where <DDSN> is the shortName of the SwCluCDcmProxyRoutineControl container.

⌊ DRAFT g The diagnostic data element return control to ECU for a SwCluCDcmProxyDiagnosticData is enabled, if: • SwCluCDcmProxyDataRef references a DcmDspData AND • the corresponding DcmDspDid has a DcmDspDidControl configured in its re- lated DcmDspDidInfo AND • the parameter DcmDspDidFreezeCurrentState is set to true .

⌊ DRAFT g The Dcm Low Proxy shall provide an instance of a Xxx_ResetToDefault function per configured SwCluCDcmProxyDiagnostic- Data container in the Dcm Low Proxy , if the diagnostic data element reset to default is enabled.

⌊ DRAFT g The Xxx_ResetToDefault function shall be named SwCluC_DcmProxy_ResetToDefault_<DDSN> , where <DDSN> is the shortName of the SwCluCDcmProxyRoutineControl container.

⌊ DRAFT g The diagnostic data element reset to default for a SwCluCDcmProxyDiagnosticData is enabled, if: • SwCluCDcmProxyDataRef references a DcmDspData AND • the corresponding DcmDspDid has a DcmDspDidControl configured in its re- lated DcmDspDidInfo AND • the parameter DcmDspDidResetToDefault is set to true .

⌊ DRAFT g The Dcm Low Proxy shall provide an instance of a Xxx_FreezeCurrentState function per configured SwCluCDcmProxyDiag- nosticData container in the Dcm Low Proxy , if the diagnostic data element freeze current state is enabled.

⌊ DRAFT g The Xxx_FreezeCurrentState function shall be named SwCluC_DcmProxy_FreezeCurrentState_<DDSN> , where <DDSN> is the shortName of the SwCluCDcmProxyRoutineControl container.

⌊ DRAFT g The diagnostic data element freeze current state for a SwCluCDcmProxyDiagnosticData is enabled, if • SwCluCDcmProxyDataRef references a DcmDspData AND • the corresponding DcmDspDid has a DcmDspDidControl configured in its re- lated DcmDspDidInfo AND • the parameter DcmDspDidFreezeCurrentState is set to true .

⌊ DRAFT g The Dcm Low Proxy shall provide an instance of a Xxx_ShortTermAdjustment function per configured SwCluCDcmProxyDiag- nosticData container in the Dcm Low Proxy , if the diagnostic data element short term adjustment is enabled.

⌊ DRAFT g The Xxx_ShortTermAdjustment function shall be named SwCluC_DcmProxy_ShortTermAdjustment_<DDSN> , where <DDSN> is the shortName of the SwCluCDcmProxyRoutineControl container.

⌊ DRAFT g The diagnostic data element short term adjustment for a SwCluCDcmProxyDiagnosticData is enabled, if • SwCluCDcmProxyDataRef references a DcmDspData AND • the corresponding DcmDspDid has a DcmDspDidControl configured in its re- lated DcmDspDidInfo AND • the parameter DcmDspDidShortTermAdjustment is set to true .

⌊ DRAFT g The Xxx_ReadData function of Dcm Low Proxy shall return E_NOT_OK and the ErrorCode DCM_E_REQUESTOUTOFRANGE , if the cor- responding diagnostic data proxy is not connected to an instance in the Dcm High Proxy . No data is returned in this case.

⌊ DRAFT g The Xxx_WriteData function of Dcm Low Proxy shall return E_NOT_OK and the ErrorCode DCM_E_REQUESTOUTOFRANGE , if the corresponding diagnostic data proxy is not connected to an instance in the Dcm High Proxy .

⌊ DRAFT g The Xxx_ReadDataLength function of Dcm Low Proxy shall return E_NOT_OK , if the corresponding diagnostic data proxy is not connected to an instance in the Dcm High Proxy .

⌊ DRAFT g The Xxx_ConditionCheckRead function of Dcm Low Proxy shall return E_NOT_OK , if the corresponding diagnostic data proxy is not connected to an instance in the Dcm High Proxy .

⌊ DRAFT g The Xxx_GetScalingInformation function of Dcm Low Proxy shall return E_NOT_OK , if the corresponding diagnostic data proxy is not connected to an instance in the Dcm High Proxy .

⌊ DRAFT g The Xxx_ReturnControlToECU function of Dcm Low Proxy shall return E_NOT_OK , if the corresponding diagnostic data proxy is not connected to an instance in the Dcm High Proxy .

⌊ DRAFT g The Xxx_ResetToDefault function of Dcm Low Proxy shall return E_NOT_OK , if the corresponding diagnostic data proxy is not connected to an instance in the Dcm High Proxy .

⌊ DRAFT g The Xxx_FreezeCurrentState function of Dcm Low Proxy shall return E_NOT_OK , if the corresponding diagnostic data proxy is not connected to an instance in the Dcm High Proxy .

⌊ DRAFT g The Xxx_ShortTermAdjustment function of Dcm Low Proxy shall return E_NOT_OK , if the corresponding diagnostic data proxy is not connected to an instance in the Dcm High Proxy .

⌊ DRAFT g The Dcm High Proxy shall create for each SwCluCDcmProxyBaseSocket a required resource entry in the Binary Mani- fest .

⌊ DRAFT g The Dcm High Proxy shall create for each di- agnostic data proxy - configured via SwCluCDcmProxyDiagnosticData con- tainer - a provided resource entry in the Binary Manifest .

⌊ DRAFT g The Dcm High Proxy shall create for each rou- tine control proxy - configured via SwCluCDcmProxyRoutineControl con- tainer - a provided resource entry in the Binary Manifest .

⌊ DRAFT g The Dcm High Proxy shall create for each ser- vice request notification proxy - configured via SwCluCDcmProxySer- viceRequestNotification container - a provided resource entry in the Binary Manifest .

⌊ DRAFT g The Dcm Low Proxy shall create for each di- agnostic data proxy - configured via SwCluCDcmProxyDiagnosticData con- tainer - a required resource entry in the Binary Manifest .

⌊ DRAFT g The Dcm Low Proxy shall create for each rou- tine control proxy - configured via SwCluCDcmProxyRoutineControl con- tainer - a required resource entry in the Binary Manifest .

⌊ DRAFT g The Dcm Low Proxy shall create for each ser- vice request notification proxy - configured via SwCluCDcmProxySer- viceRequestNotification container - a required resource entry in the Binary Manifest .

⌊ DRAFT g The Dcm Low Proxy shall create for each SwCluCDcmProxyBaseSocket a provided resource entry in the Binary Mani- fest .

⌊ DRAFT g The Dcm Low Proxy shall provide an instance of a Xxx_Start function per configured SwCluCDcmProxyRoutineControl container in the Dcm Low Proxy .

⌊ DRAFT g The Xxx_Start function shall be named SwCluC_DcmProxy_Start_<RCSN> , where <RCSN> is the shortName of the SwCluCDcmProxyRoutineControl container.

⌊ DRAFT g The Xxx_Start function of Dcm Low Proxy shall return E_NOT_OK and the ErrorCode DCM_E_REQUESTOUTOFRANGE , if the cor- responding routine control proxy is not connected to an instance in the Dcm High Proxy .

⌊ DRAFT g The Dcm Low Proxy shall provide an instance of a Xxx_StartConfirmation function per configured SwCluCDcmProxyRou- tineControl container in the Dcm Low Proxy .

⌊ DRAFT g The Xxx_StartConfirmation function shall be named SwCluC_DcmProxy_StartConfirmation_<RCSN> , where <RCSN> is the shortName of the SwCluCDcmProxyRoutineControl container.

⌊ DRAFT g The Xxx_StartConfirmation function of Dcm Low Proxy shall return E_NOT_OK , if the corresponding routine control proxy is not connected to an instance in the Dcm High Proxy .

⌊ DRAFT g The Dcm Low Proxy shall provide an instance of a Xxx_Stop function per configured SwCluCDcmProxyRoutineControl container in the Dcm Low Proxy .

⌊ DRAFT g The Xxx_Stop function shall be named SwCluC_DcmProxy_Stop_<RCSN> , where <RCSN> is the shortName of the SwCluCDcmProxyRoutineControl container.

⌊ DRAFT g The Xxx_Stop function of Dcm Low Proxy shall return E_NOT_OK and the ErrorCode DCM_E_REQUESTOUTOFRANGE , if the corre- sponding routine control proxy is not connected to an instance in the Dcm High Proxy .

⌊ DRAFT g The Dcm Low Proxy shall provide an instance of a Xxx_StopConfirmation function per configured SwCluCDcmProxyRou- tineControl container in the Dcm Low Proxy .

⌊ DRAFT g The Xxx_StopConfirmation function shall be named SwCluC_DcmProxy_StopConfirmation_<RCSN> , where <RCSN> is the shortName of the SwCluCDcmProxyRoutineControl container.

⌊ DRAFT g The Xxx_StopConfirmation function of Dcm Low Proxy shall return E_NOT_OK if the corresponding routine control proxy is not connected to an instance in the Dcm High Proxy .

⌊ DRAFT g The Dcm Low Proxy shall provide an instance of a Xxx_RequestResults function per configured SwCluCDcmProxyRoutineCon- trol container in the Dcm Low Proxy .

⌊ DRAFT g The Xxx_RequestResults function shall be named SwCluC_DcmProxy_RequestResults_<RCSN> , where <RCSN> is the shortName of the SwCluCDcmProxyRoutineControl container.

⌊ DRAFT g The Xxx_RequestResults function of Dcm Low Proxy shall return E_NOT_OK and the ErrorCode DCM_E_REQUESTOUTOFRANGE , if the corresponding routine control proxy is not connected to an instance in the Dcm High Proxy .

⌊ DRAFT g The Dcm Low Proxy shall provide an instance of a Xxx_RequestResultsConfirmation function per configured SwCluCDcmProx- yRoutineControl container in the Dcm Low Proxy .

⌊ DRAFT g The Xxx_RequestResultsConfirmation function shall be named SwCluC_DcmProxy_RequestResultsConfirmation_<RCSN> , where <RCSN> is the shortName of the SwCluCDcmProxyRoutineControl con- tainer.

⌊ DRAFT g The Xxx_RequestResultsConfirmation function of Dcm Low Proxy shall return E_NOT_OK , if the corresponding rou- tine control proxy is not connected to an instance in the Dcm High Proxy .

⌊ DRAFT g The Dcm Low Proxy shall provide an instance of a Xxx_Indication function per configured SwCluCDcmProxyServiceRequest- Notification container in the Dcm Low Proxy .

⌊ DRAFT g The Xxx_Indication function shall be named SwCluC_DcmProxy_Indication_<SRNSN> , where <SRNSN> is the short- Name of the SwCluCDcmProxyServiceRequestNotification container.

⌊ DRAFT g The Xxx_Indication function of Dcm Low Proxy shall return E_NOT_OK and the ErrorCode DCM_E_REQUESTOUTOFRANGE , if the corresponding routine control proxy is not connected to an instance in the Dcm High Proxy .

⌊ DRAFT g The Dcm Low Proxy shall provide an in- stance of a Xxx_Confirmation function per configured SwCluCDcmProxySer- viceRequestNotification container in the Dcm Low Proxy .

⌊ DRAFT g The Xxx_Confirmation function shall be named SwCluC_DcmProxy_Confirmation_<SRNSN> , where <SRNSN> is the short- Name of the SwCluCDcmProxyServiceRequestNotification container.

⌊ DRAFT g The Xxx_Confirmation function of Dcm Low Proxy shall return E_NOT_OK and the ErrorCode DCM_E_REQUESTOUTOFRANGE , if the corresponding routine control proxy is not connected to an instance in the Dcm High Proxy .

⌊ DRAFT g The interface function instance for the diagnos- tic data proxy , routine control proxy and service request notifi- cation proxy , according to [SWS_SwCluC_02350], [SWS_SwCluC_02353], [SWS_SwCluC_02356], [SWS_SwCluC_02359], [SWS_SwCluC_02362], [SWS_SwCluC_02365], [SWS_SwCluC_02368], [SWS_SwCluC_02371], [SWS_SwCluC_02374], [SWS_SwCluC_02400], [SWS_SwCluC_02403], [SWS_SwCluC_02406], [SWS_SwCluC_02409], [SWS_SwCluC_02412], [SWS_SwCluC_02415], are provided either: • at the EcucPartition , referenced by – SwCluCDcmProxyDiagnosticData . SwCluCProxyEcucPartitionRef OR – SwCluCDcmProxyRoutineControl . SwCluCProxyEcucPartitionRef OR – SwCluCDcmProxyServiceRequestNotification . SwCluCProxyE- cucPartitionRef OR • if a SwCluCDcmProxyBaseSocket is directly available, at its EcucPartition OR • at the EcucPartition of the SwCluCDcmProxyBaseSocket , referenced by the SwCluCDcmProxyBaseSocket - via SwCluCDcmProxyUsedSatel- liteRef , applicable for the EcucPartition requested above. In this case, the EcucPartition shall be changed, before the callback in the High Proxy is called.

⌊ DRAFT g The Dcm Low Proxy shall provide, for each SwCluCDcmProxyBaseSocket , a SwCluC_DcmProxy_Init API, to initialize the Dcm High Proxy of an Applicative Software Cluster . This shall be one element of the service resource SwCluCDcmProxyBaseSocket .

⌊ DRAFT g Development Error Types of SwCluC Dcm Proxy The development error types defined for the SwCluC Dcm Proxy are listed in table Table 7.7.

⌊ DRAFT g The LdCom High Proxy code, and related AUTOSAR model descriptions, shall only be created, if the configuration parameter SwCluCProxyGenerationLdCom is set to HIGH_PROXY .

⌊ DRAFT g The LdCom Low Proxy code, and related AUTOSAR model descriptions, shall only be created, if the configuration parameter SwCluCProxyGenerationLdCom is set to LOW_PROXY .

⌊ DRAFT g The LdCom Proxy shall support that the Ld- ComIPdu Ids of the LdCom of the Host Software Cluster can change, without reconfiguration or rebuild of the Applicative Software Cluster using these Ld- ComIPdu s.

⌊ DRAFT g The LdCom Proxy shall support the invocation of LdCom API from an Applicative Software Cluster in context of the Host Software Cluster .

⌊ DRAFT g The LdCom Proxy shall support the invocation of LdCom Callback APIs from the Host Software Cluster in context of the Ap- plicative Software Cluster .

⌊ DRAFT g The LdCom High Proxy shall provide the header file LdCom.h .

⌊ DRAFT g The LdCom High Proxy shall provide the sym- bolic name values for the LdComIPdu IDs, for LdCom users in the Applicative Software Cluster .

⌊ DRAFT g The LdCom High Proxy shall provide the func- tion w.r.t transmission request of a LdComIPdu • LdCom_Transmit required by the Applicative Software Cluster

⌊ DRAFT g If the LdCom High Proxy is not connected to the LdCom Low Proxy , the function • LdCom_Transmit of the LdCom High Proxy shall return E_NOT_OK .

⌊ DRAFT g The LdCom High Proxy shall provide the func- tion for transmission request of a signal, according to [SWS_SwCluC_02506], once per configured SwCluCLdComProxyBaseSocket . At the EcucPartition , where the SwCluCNativeBswApi is set to true , the API is provided with the original Mip LdCom . For all other SwCluCLdComProxyBaseSocket instances, the Mip LdCom is replaced by LdCom_<EcucPartition.ShortName> .

⌊ DRAFT g The LdCom High Proxy shall support the <Ld- ComUser_LdComCbkRxIndication> notification callback, configured via the Ld- ComUserCallbackName (See [ECUC_LdCom_00023]) parameter, where the LdCo- mUserCallbackType (See [ECUC_LdCom_00025]) is set to LDCOM_RX_INDICA- TION

⌊ DRAFT g The LdCom High Proxy shall support the op- tional <LdComUser_LdComCbkTxConfirmation> notification callback, configured via the LdComUserCallbackName (See [ECUC_LdCom_00023]) parameter, where the LdComUserCallbackType (See [ECUC_LdCom_00025]) is set to LDCOM_TX_- CONFIRMATION

⌊ DRAFT g The LdCom High Proxy shall support the op- tional <LdComUser_LdComCbkTriggerTransmit> notification callback, configured via the LdComUserCallbackName (See [ECUC_LdCom_00023]) parameter, where the LdComUserCallbackType (See [ECUC_LdCom_00025]) is set to LDCOM_TX_- TRIGGER_TRANSMIT

⌊ DRAFT g The LdCom High Proxy shall support the <Ld- ComUser_LdComCbkCopyRxData> notification callback, configured via the LdCo- mUserCallbackName (See [ECUC_LdCom_00023]) parameter, where the LdCo- mUserCallbackType (See [ECUC_LdCom_00025]) is set to LDCOM_TP_COPY_- RX_DATA

⌊ DRAFT g The LdCom High Proxy shall support the <Ld- ComUser_LdComCbkStartOfReception> notification callback configured via the LdComUserCallbackName (See [ECUC_LdCom_00023]) parameter where the LdComUserCallbackType (See [ECUC_LdCom_00025]) is set to LDCOM_RX_- START_OF_RECEPTION

⌊ DRAFT g The LdCom High Proxy shall support the <Ld- ComUser_LdComCbkTpRxIndication> notification callback, configured via the Ld- ComUserCallbackName (See [ECUC_LdCom_00023]) parameter, where the LdCo- mUserCallbackType (See [ECUC_LdCom_00025]) is set to LDCOM_TP_RX_INDI- CATION

⌊ DRAFT g The LdCom High Proxy shall support the <Ld- ComUser_LdComCbkTpTxConfirmation> notification callback, configured via the LdComUserCallbackName (See [ECUC_LdCom_00023]) parameter, where the Ld- ComUserCallbackType (See [ECUC_LdCom_00025]) is set to LDCOM_TP_TX_- CONFIRMATION

⌊ DRAFT g The LdCom High Proxy shall support the <Ld- ComUser_LdComCbkCopyTxData> notification callback, configured via the LdCo- mUserCallbackName (See [ECUC_LdCom_00023]) parameter, where the LdCo- mUserCallbackType (See [ECUC_LdCom_00025]) is set to LDCOM_TP_COPY_- TX_DATA

⌊ DRAFT g The LdCom Low Proxy shall provide the header file SwCluC_LdComProxy_Cbk.h .

⌊ DRAFT g The LdCom Low Proxy shall provide the entry function for transmission requests, according to [SWS_SwCluC_02506], once per configured SwCluCLdComProxyBaseSocket at the EcucPartition configured by SwCluCLdComProxyBaseSocket . SwCluCProxyEcucPartitionRef .

⌊ DRAFT g The LdCom Low Proxy shall provide for each SwCluCLdComProxyBaseSocket a SwCluC_LdComProxy_Init API, to initial- ize the LdCom High Proxy of an Applicative Software Cluster .

⌊ DRAFT g The LdCom Low Proxy shall provide an instance of all SwCluC_LdComProxy_LdComCbkRxIndication notification callbacks, con- figured via the LdComUserCallbackName (See [ECUC_LdCom_00023]) parameter, with LdComUserCallbackType (See [ECUC_LdCom_00025]) set to LDCOM_RX_- INDICATION .

⌊ DRAFT g The LdCom Low Proxy shall provide an instance of all LdComCbkTxConfirmation notification callbacks, configured via the LdCo- mUserCallbackName (See [ECUC_LdCom_00023]) parameter, with LdComUser- CallbackType (See [ECUC_LdCom_00025]) set to LDCOM_TX_CONFIRMATION .

⌊ DRAFT g The LdCom Low Proxy shall provide an instance of all LdComCbkTriggerTransmit notification callbacks, configured via the LdCo- mUserCallbackName (See [ECUC_LdCom_00023]) parameter, with LdComUser- CallbackType (See [ECUC_LdCom_00025]) set to LDCOM_TX_TRIGGER_TRANS- MIT .

⌊ DRAFT g The LdCom Low Proxy shall provide an instance of all LdComCbkCopyRxData notification callbacks, configured via the LdComUser- CallbackName (See [ECUC_LdCom_00023]) parameter, with LdComUserCall- backType (See [ECUC_LdCom_00025]) set to LDCOM_TP_COPY_RX_DATA .

⌊ DRAFT g The LdCom Low Proxy shall provide an instance of all LdComCbkStartOfReception notification callbacks, configured via the LdCo- mUserCallbackName (See [ECUC_LdCom_00023]) parameter, with LdComUser- CallbackType (See [ECUC_LdCom_00025]) set to LDCOM_RX_START_OF_RECEP- TION .

⌊ DRAFT g The LdCom Low Proxy shall provide an instance of all LdComCbkTpRxIndication notification callbacks, configured via the LdCo- mUserCallbackName (See [ECUC_LdCom_00023]) parameter, with LdComUser- CallbackType (See [ECUC_LdCom_00025]) set to LDCOM_TP_RX_INDICATION .

⌊ DRAFT g The LdCom Low Proxy shall provide an instance of all LdComCbkTpTxConfirmation notification callbacks, configured via the Ld- ComUserCallbackName (See [ECUC_LdCom_00023]) parameter, with the LdCo- mUserCallbackType (See [ECUC_LdCom_00025]) set to LDCOM_TP_TX_CONFIR- MATION .

⌊ DRAFT g The LdCom Low Proxy shall provide an instance of all SwCluC_LdComProxy_LdComCbkCopyTxData notification callbacks, config- ured via the LdComUserCallbackName (See [ECUC_LdCom_00023]) parameter, with the LdComUserCallbackType (See [ECUC_LdCom_00025]) set to LDCOM_- TP_COPY_TX_DATA .

⌊ DRAFT g The notification callback instances accord- ing to [SWS_SwCluC_02520], [SWS_SwCluC_02521], [SWS_SwCluC_02522], [SWS_SwCluC_02523], [SWS_SwCluC_02524], [SWS_SwCluC_02525], [SWS_SwCluC_02526], [SWS_SwCluC_02527] and [SWS_SwCluC_02528] are provided • at the EcucPartition of the SwCluCLdComProxyBaseSocket , referenced by the SwCluCLdComProxyBaseSocket - via SwCluCLdComProxyUsedSatel- liteRef .

⌊ DRAFT g If the LdCom Low Proxy is not connected to the LdCom High Proxy , the notification callback functions • SwCluC_LdComProxy_LdComCbkStartOfReception • SwCluC_LdComProxy_LdComCbkCopyRxData • SwCluC_LdComProxy_LdComCbkCopyTxData of the LdCom Low Proxy shall return BUFREQ_E_NOT_OK .

⌊ DRAFT g If the LdCom Low Proxy is not connected to the LdCom High Proxy , the notification callback function • SwCluC_LdComProxy_LdComCbkTriggerTransmit of the LdCom Low Proxy shall return E_NOT_OK .

⌊ DRAFT g If the LdCom Low Proxy is not connected to the LdCom High Proxy , the notification callback functions • SwCluC_LdComProxy_LdComCbkRxIndication • SwCluC_LdComProxy_LdComCbkTpRxIndication • SwCluC_LdComProxy_LdComCbkTxConfirmation • SwCluC_LdComProxy_LdComCbkTpTxConfirmation of the LdCom Low Proxy shall return without effect.

⌊ DRAFT g If the development error detection is enabled for the LdCom High Proxy , the API • LdCom_Transmit shall report the DET error LDCOM_E_UNINIT , in case the LdCom High Proxy is not initialized.

⌊ DRAFT g If the development error detection is enabled for the LdCom High Proxy , the API • LdCom_Transmit shall, when invoked with a NULL_PTR , report the DET error LD- COM_E_PARAM_POINTER .

⌊ DRAFT g If the <LdComUser_LdComCbkRxIndication> notification callback is configured in the LdCom High Proxy (via the LdComUser- CallbackName (See [ECUC_LdCom_00023]) parameter, where the LdComUser- CallbackType (See [ECUC_LdCom_00025]) is set to LDCOM_RX_INDICATION ), all the configured <LdComUser_LdComCbkRxIndication> callbacks shall be invoked, when the associated instance of the SwCluC_LdComProxy_LdComCbkRxIndica- tion from the LdCom Low Proxy is called.

⌊ DRAFT g If the <LdComUser_LdComCbkTxConfirma- tion> notification callback is configured in the LdCom High Proxy (via the Ld- ComUserCallbackName (See [ECUC_LdCom_00023]) parameter, where the LdCo- mUserCallbackType (See [ECUC_LdCom_00025]) is set to LDCOM_TX_CONFIR- MATION ), the configured <LdComUser_LdComCbkTxConfirmation> callback shall be invoked. when the associated instance of the SwCluC_LdComProxy_LdComCbk- TxConfirmation from the LdCom Low Proxy is called.

⌊ DRAFT g If the <LdComUser_LdComCbkTriggerTrans- mit> notification callback is configured in the LdCom High Proxy (via the LdComUserCallbackName (See [ECUC_LdCom_00023]) parameter, where the LdComUserCallbackType (See [ECUC_LdCom_00025]) is set to LDCOM_TX_- TRIGGER_TRANSMIT ), the configured <LdComUser_LdComCbkTriggerTransmit> callback shall be invoked, when the associated instance of the SwCluC_Ld- ComProxy_LdComCbkTriggerTransmit from the LdCom Low Proxy is called.

⌊ DRAFT g If the <LdComUser_LdComCbkCopyRxData> no- tification callback is configured in the LdCom High Proxy (via the LdComUserCall- backName (See [ECUC_LdCom_00023]) parameter, where the LdComUserCall- backType (See [ECUC_LdCom_00025]) is set to LDCOM_TP_COPY_RX_DATA ), the configured <LdComUser_LdComCbkCopyRxData> callback shall be invoked, when the associated instance of the SwCluC_LdComProxy_LdComCbkCopyRxData from the LdCom Low Proxy is called.

⌊ DRAFT g If the <LdComUser_LdComCbkStartOfRecep- tion> notification callback is configured in the LdCom High Proxy (via the LdComUserCallbackName (See [ECUC_LdCom_00023]) parameter, where the LdComUserCallbackType (See [ECUC_LdCom_00025]) is set to LDCOM_RX_- START_OF_RECEPTION ), the configured <LdComUser_LdComCbkStartOfRecep- tion> callback shall be invoked, when the associated instance of the SwCluC_Ld- ComProxy_LdComCbkStartOfReception from the LdCom Low Proxy is called.

⌊ DRAFT g If the <LdComUser_LdComCbkTpRxIndica- tion> notification callback is configured in the LdCom High Proxy (via the Ld- ComUserCallbackName (See [ECUC_LdCom_00023]) parameter, where the LdCo- mUserCallbackType (See [ECUC_LdCom_00025]) is set to LDCOM_TP_RX_INDI- CATION ), the configured <LdComUser_LdComCbkTpRxIndication> callback shall be invoked, when the associated instance of the SwCluC_LdComProxy_LdComCbk- TpRxIndication from the LdCom Low Proxy is called.

⌊ DRAFT g If the <LdComUser_LdComCbkTpTxConfirma- tion> notification callback is configured in the LdCom High Proxy (via the LdComUserCallbackName (See [ECUC_LdCom_00023]) parameter, where the LdComUserCallbackType (See [ECUC_LdCom_00025]) is set to LDCOM_TP_- TX_CONFIRMATION ), the configured <LdComUser_LdComCbkTpTxConfirmation> callback shall be invoked, when the associated instance of the SwCluC_Ld- ComProxy_LdComCbkTpTxConfirmation from the LdCom Low Proxy is called.

⌊ DRAFT g If the <LdComUser_LdComCbkCopyTxData> no- tification callback is configured in the LdCom High Proxy (via the LdComUserCall- backName (See [ECUC_LdCom_00023]) parameter, where the LdComUserCall- backType (See [ECUC_LdCom_00025]) is set to LDCOM_TP_COPY_TX_DATA ), the configured <LdComUser_LdComCbkCopyTxData> callback shall be invoked, when the associated instance of the SwCluC_LdComProxy_LdComCbkCopyTxData from the LdCom Low Proxy is called.

⌊ DRAFT g The Com High Proxy shall create, for each SwCluCLdComProxyBaseSocket , a required resource entry in the Binary Man- ifest .

⌊ DRAFT g The LdCom Low Proxy shall create for each SwCluCLdComProxyBaseSocket a provided resource entry in the Binary Man- ifest .

⌊ DRAFT g Development Error Types of SwCluC LdCom Proxy The development error types defined for the SwCluC LdCom Proxy are listed in table Table 7.6.

⌊ DRAFT g The LdCom Proxy shall support that the LdCo- mUserCbkHandleId of LdComUserIPdu s configured in LdCom users of the Ap- plicative Software Cluster can change, without reconfiguration or rebuild of the Host Software Cluster .

⌊ DRAFT g The LdCom Low Proxy shall provide in its Ld- ComUserModuleCnf containers the LdComUserCbkHandleId values for the config- ured LdComUserIPdu s, according to its internal implementation requirements (e.g. to address the LdCom Low Proxy 's data structures).

⌊ DRAFT g The LdCom base socket shall implement the connection of the related callback functions • SwCluC_LdComProxy_LdComCbkStartOfReception • SwCluC_LdComProxy_LdComCbkCopyRxData • SwCluC_LdComProxy_LdComCbkCopyTxData • SwCluC_LdComProxy_LdComCbkTriggerTransmit • SwCluC_LdComProxy_LdComCbkRxIndication • SwCluC_LdComProxy_LdComCbkTpRxIndication • SwCluC_LdComProxy_LdComCbkTxConfirmation • SwCluC_LdComProxy_LdComCbkTpTxConfirmation

⌊ DRAFT g The LdCom High Proxy shall create for each LdComIPdu configured in LdCom a required resource entry in the Binary Man- ifest . Where the EcucPartition of the LdComIPdu 's Pdu given via Pdu . EcucPduDefaultPartitionRef or Pdu . EcucPduDedicatedPartition . EcucP- duDedicatedPartitionRef are relevant to denote the EcucPartition .

⌊ DRAFT g The LdCom Low Proxy shall create, for each LdComUserIPdu configured in a SwCluCLdComProxyBaseSocket . LdComUser- ModuleCnf , a provided resource entry in the Binary Manifest .

⌊ DRAFT g The Com High Proxy code, and related AUTOSAR model descriptions, shall only be created, if the configuration param- eter SwCluCProxyGenerationCom is set to HIGH_PROXY .

⌊ DRAFT g The Com Low Proxy code, and related AUTOSAR model descriptions, shall only be created, if the configuration param- eter SwCluCProxyGenerationCom is set to LOW_PROXY .

⌊ DRAFT g The Com Proxy shall support that the ComHan- dleId of ComSignal s configured in Com of the Host Software Cluster can change, without reconfiguration or rebuild of the Applicative Software Cluster using these ComSignal s.

⌊ DRAFT g The Com Proxy shall support that the ComHan- dleId of ComSignalGroup s resp. ComGroupSignal s configured in the Com of the Host Software Cluster can change, without reconfiguration or rebuild of the Applicative Software Cluster using these ComSignalGroup s.

⌊ DRAFT g The Com Proxy shall support the invocation of Com APIs from an Applicative Software Cluster in context of the Host Software Cluster .

⌊ DRAFT g The Com Proxy shall support the invocation of Com callbacks from the Host Software Cluster in context of the Applicative Software Cluster .

⌊ DRAFT g The Com High Proxy shall provide the header file Com.h .

⌊ DRAFT g The Com High Proxy shall provide the symbolic name values for the ComSignal s, for Com users in the Applicative Software Cluster .

⌊ DRAFT g The Com High Proxy shall provide the symbolic name values for the ComSignalGroup s resp. ComGroupSignal s, for Com users in the Applicative Software Cluster .

⌊ DRAFT g The Com High Proxy shall provide the functions for transmission requests of ComSignal s and ComSignalGroup s • Com_SendSignal • Com_SendDynSignal • Com_SendSignalGroup • Com_SendSignalGroupArray • Com_SendSignalWithMetaData • Com_SendDynSignalWithMetaData • Com_SendSignalGroupWithMetaData • Com_SendSignalGroupArrayWithMetaData required by the Com users in the Applicative Software Cluster .

⌊ DRAFT g The Com High Proxy shall provide the functions for reception requests of a ComSignal and ComSignalGroup • Com_ReceiveSignal • Com_ReceiveDynSignal • Com_ReceiveSignalGroup • Com_ReceiveSignalGroupArray • Com_ReceiveSignalWithMetaData • Com_ReceiveDynSignalWithMetaData • Com_ReceiveSignalGroupWithMetaData • Com_ReceiveSignalGroupArrayWithMetaData required by the Com users in the Applicative Software Cluster

⌊ DRAFT g The Com High Proxy shall provide the functions for invalidation requests of a ComSignal and ComSignalGroup • Com_InvalidateSignal • Com_InvalidateSignalGroup required by the Com users in the Applicative Software Cluster

⌊ DRAFT g If the Com High Proxy is not connected to the Com Low Proxy , the functions w.r.t transmission requests of ComSignal s and Com- SignalGroup s • Com_SendSignal • Com_SendDynSignal • Com_SendSignalGroup • Com_SendSignalGroupArray • Com_SendSignalWithMetaData • Com_SendDynSignalWithMetaData • Com_SendSignalGroupWithMetaData • Com_SendSignalGroupArrayWithMetaData of the Com High Proxy shall return COM_SERVICE_NOT_AVAILABLE .

⌊ DRAFT g If the Com High Proxy is not connected to the Com Low Proxy , the functions w.r.t reception requests of ComSignal s and ComSig- nalGroup s • Com_ReceiveSignal • Com_ReceiveDynSignal • Com_ReceiveSignalGroup • Com_ReceiveSignalGroupArray • Com_ReceiveSignalWithMetaData • Com_ReceiveDynSignalWithMetaData • Com_ReceiveSignalGroupWithMetaData • Com_ReceiveSignalGroupArrayWithMetaData • Com_ReceiveSignalWithMetaData • Com_ReceiveDynSignalWithMetaData of the Com High Proxy shall return COM_SERVICE_NOT_AVAILABLE .

⌊ DRAFT g If the Com High Proxy is not connected to the Com Low Proxy , the functions w.r.t invalidation requests of ComSignal s and Com- SignalGroup s • Com_InvalidateSignal • Com_InvalidateSignalGroup of the Com High Proxy shall return COM_SERVICE_NOT_AVAILABLE .

⌊ DRAFT g The Com High Proxy shall provide the functions for transmission request of a signal(group)s, according to [SWS_SwCluC_02609], once per configured SwCluCComProxyBaseSocket . At the EcucPartition where the SwCluCNativeBswApi is set to true , For all other SwCluCComProxyBas- eSocket instances, the Mip Com is replaced by Com_<EcucPartition.Short- Name> .

⌊ DRAFT g The Com High Proxy shall provide the functions for reception request of a signal(group)s, according to [SWS_SwCluC_02610], once per configured SwCluCComProxyBaseSocket . At the EcucPartition where the SwCluCNativeBswApi is set to true , the API is provided with the original Mip Com . For all the other SwCluCComProxyBaseSocket instances, the Mip Com is replaced by Com_<EcucPartition.ShortName> .

⌊ DRAFT g The Com High Proxy shall provide the functions for invalidation request of a signal(group)s, according to [SWS_SwCluC_02611], once per configured SwCluCComProxyBaseSocket . At the EcucPartition where the SwCluCNativeBswApi is set to true , the API is provided with the original Mip Com . For all the other SwCluCComProxyBaseSocket instances, the Mip Com is replaced by Com_<EcucPartition.ShortName> .

⌊ DRAFT g The Com High Proxy shall support the optional <ComUser_CbkRxAck> notification callback configured via the ComUserCallback- Name (See [ECUC_Com_10036]) parameter where the ComUserCallbackType (See [ECUC_Com_10034]) is set to COM_RX_ACK .

⌊ DRAFT g The Com High Proxy shall support the optional invalid <ComUser_CbkInv> notification callback configured via the ComUserCall- backName (See [ECUC_Com_10036]) where the ComUserCallbackType (See [ECUC_Com_10034]) is set to COM_RX_INV .

⌊ DRAFT g The Com High Proxy shall support the optional <ComUser_CbkRxTOut> timeout notification callback configured via the ComUser- CallbackName (See [ECUC_Com_10036]) where the ComUserCallbackType (See [ECUC_Com_10034]) is set to COM_RX_TOUT .

⌊ DRAFT g The Com High Proxy shall support the optional <ComUser_CbkTxAck> notification callback configured via the ComUserCallback- Name (See [ECUC_Com_10036]) where the ComUserCallbackType (See [ECUC_- Com_10034]) is set to COM_TX_ACK .

⌊ DRAFT g The Com High Proxy shall support the optional <ComUser_CbkTxErr> error notification callback configured via the ComUserCall- backName (See [ECUC_Com_10036]) where the ComUserCallbackType (See [ECUC_Com_10034]) is set to COM_TX_ERR .

⌊ DRAFT g The Com High Proxy shall support the optional <ComUser_CbkTxTOut> timeout notification callback configured via the ComUser- CallbackName (See [ECUC_Com_10036]) where the ComUserCallbackType (See [ECUC_Com_10034]) is set to COM_TX_TOUT .

⌊ DRAFT g The Com Low Proxy shall provide the header file SwCluC_ComProxy_Cbk.h .

⌊ DRAFT g The Com Low Proxy shall provide the en- try function for transmission, reception and invalidation requests of ComSig- nal(Group)s, according to [SWS_SwCluC_02609], [SWS_SwCluC_02610] and [SWS_SwCluC_02611], once per configured SwCluCComProxyBaseSocket , at the EcucPartition configured by SwCluCComProxyBaseSocket . SwCluCProxyE- cucPartitionRef . In case the SwCluCComProxyUsedSatelliteRef is set, the EcucPartition shall be changed, before the Com API is called.

⌊ DRAFT g The Com Low Proxy shall provide for each SwCluCComProxyBaseSocket a SwCluC_ComProxy_Init API, to initialize the Com High Proxy of an Applicative Software Cluster .

⌊ DRAFT g The Com Low Proxy shall provide an instance of all SwCluC_ComProxy_CbkRxAck notification callbacks, configured via the Co- mUserCallbackName (See [ECUC_Com_10036]) parameter, with the ComUser- CallbackType (See [ECUC_Com_10034]) set to COM_RX_ACK .

⌊ DRAFT g The Com Low Proxy shall provide an instance of all SwCluC_ComProxy_COMCbkInv notification callbacks, configured on each Com- Signal(Group) via the ComUserCallbackName (See [ECUC_Com_10036]) parame- ter, with the ComUserCallbackType (See [ECUC_Com_10034]) set to COM_RX_- INV .

⌊ DRAFT g The Com Low Proxy shall provide an instance of all SwCluC_ComProxy_COMCbkRxTOut timeout notification callbacks configured on each ComSignal(Group), via the ComUserCallbackName (See [ECUC_Com_- 10036]), with the ComUserCallbackType (See [ECUC_Com_10034]) set to COM_- RX_TOUT .

⌊ DRAFT g The Com High Proxy shall provide an instance of all <ComUser_CbkTxAck> notification callbacks, configured via the ComUser- CallbackName (See [ECUC_Com_10036]), with the ComUserCallbackType (See [ECUC_Com_10034]) set to COM_TX_ACK .

⌊ DRAFT g The Com High Proxy shall provide an instance of all <ComUser_CbkTxErr> notification callbacks, configured via the ComUser- CallbackName (See [ECUC_Com_10036]), with the ComUserCallbackType (See [ECUC_Com_10034]) set to COM_TX_ERR .

⌊ DRAFT g The Com High Proxy shall provide an instance of all <ComUser_CbkTxTOut> notification callbacks, configured via the ComUser- CallbackName (See [ECUC_Com_10036]), with the ComUserCallbackType (See [ECUC_Com_10034]) set to COM_TX_TOUT .

⌊ DRAFT g The notification callback instances accord- ing to [SWS_SwCluC_02626], [SWS_SwCluC_02627], [SWS_SwCluC_02628], [SWS_SwCluC_02629], [SWS_SwCluC_02630], [SWS_SwCluC_02631] and [SWS_SwCluC_02632] are provided • at the EcucPartition of the SwCluCComProxyBaseSocket referenced by the SwCluCComProxyBaseSocket - via SwCluCComProxyUsedSatel- liteRef . In this case, the EcucPartition shall be changed, before the call- back in the High Proxy is called.

⌊ DRAFT g If the Com Low Proxy is not connected to the Com High Proxy , the callback functions • SwCluC_ComProxy_CbkRxAck • SwCluC_ComProxy_COMCbkInv • SwCluC_ComProxy_COMCbkRxTOut • SwCluC_ComProxy_COMCbkTAck • SwCluC_ComProxy_COMCbkTErr • SwCluC_ComProxy_COMCbkTxTOut of the Com Low Proxy shall return shall return without effect.

⌊ DRAFT g If the development error detection is enabled for the Com High Proxy , the APIs • Com_SendSignal • Com_SendDynSignal • Com_SendSignalGroup • Com_SendSignalGroupArray • Com_SendSignalWithMetaData • Com_SendDynSignalWithMetaData • Com_SendSignalGroupWithMetaData • Com_SendSignalGroupArrayWithMetaData • Com_ReceiveSignal • Com_ReceiveDynSignal • Com_ReceiveSignalGroup • Com_ReceiveSignalGroupArray • Com_ReceiveSignalWithMetaData • Com_ReceiveDynSignalWithMetaData • Com_ReceiveSignalGroupWithMetaData • Com_ReceiveSignalGroupArrayWithMetaData • Com_ReceiveSignalWithMetaData • Com_ReceiveDynSignalWithMetaData • Com_InvalidateSignal • Com_InvalidateSignalGroup shall report the DET error COM_E_UNINIT , in case the Com High Proxy is not ini- tialized.

⌊ DRAFT g If the development error detection is enabled for the Com High Proxy , the APIs • Com_SendSignal • Com_SendDynSignal • Com_SendSignalGroup • Com_SendSignalGroupArray • Com_SendSignalWithMetaData • Com_SendDynSignalWithMetaData • Com_SendSignalGroupWithMetaData • Com_SendSignalGroupArrayWithMetaData • Com_ReceiveSignal • Com_ReceiveDynSignal • Com_ReceiveSignalGroup • Com_ReceiveSignalGroupArray • Com_ReceiveSignalWithMetaData • Com_ReceiveDynSignalWithMetaData • Com_ReceiveSignalGroupWithMetaData • Com_ReceiveSignalGroupArrayWithMetaData • Com_ReceiveSignalWithMetaData • Com_ReceiveDynSignalWithMetaData • Com_InvalidateSignal • Com_InvalidateSignalGroup shall, when invoked with a NULL_PTR , report the DET error COM_E_PARAM_POINTER .

⌊ DRAFT g If the development error detection is enabled for the Com High Proxy , the APIs • Com_SendSignal • Com_SendDynSignal • Com_SendSignalGroup • Com_SendSignalGroupArray • Com_SendSignalWithMetaData • Com_SendDynSignalWithMetaData • Com_SendSignalGroupWithMetaData • Com_SendSignalGroupArrayWithMetaData • Com_ReceiveSignal • Com_ReceiveDynSignal • Com_ReceiveSignalGroup • Com_ReceiveSignalGroupArray • Com_ReceiveSignalWithMetaData • Com_ReceiveDynSignalWithMetaData • Com_ReceiveSignalGroupWithMetaData • Com_ReceiveSignalGroupArrayWithMetaData • Com_ReceiveSignalWithMetaData • Com_ReceiveDynSignalWithMetaData • Com_InvalidateSignal • Com_InvalidateSignalGroup shall, when invoked with a wrong parameter, report the DET error COM_E_PARAM .

⌊ DRAFT g If the <ComUser_CbkRxAck> notification call- back is configured in the Com High Proxy (via the ComUserCallbackName (See [ECUC_Com_10036]), where the respective ComUserCallbackType (See [ECUC_- Com_10034]) is set to COM_RX_ACK ) the configured <ComUser_CbkRxAck> callback shall be invoked when the associated SwCluC_ComProxy_CbkRxAck instance of the Com Low Proxy is called.

⌊ DRAFT g If the invalid <ComUser_CbkInv> notification call- back is configured in the Com High Proxy (via the ComUserCallbackName (See [ECUC_Com_10036]), where the respective ComUserCallbackType (See [ECUC_- Com_10034]) is set to COM_RX_INV ) the configured <ComUser_CbkInv> callback shall be invoked when the associated SwCluC_ComProxy_CbkInv instance of the Com Low Proxy is called.

⌊ DRAFT g If the <ComUser_CbkRxTOut> notification call- back is configured in the Com High Proxy (via the ComUserCallbackName (See [ECUC_Com_10036]), where the respective ComUserCallbackType (See [ECUC_- Com_10034]) is set to COM_RX_TOUT ) the configured <ComUser_CbkRxTOut> call- back shall be invoked when the associated SwCluC_ComProxy_CbkRxTOut instance of the Com Low Proxy is called.

⌊ DRAFT g If the <ComUser_CbkTxAck> notification call- back is configured in the Com High Proxy (via the ComUserCallbackName (See [ECUC_Com_10036]), where the respective ComUserCallbackType (See [ECUC_- Com_10034]) is set to COM_TX_ACK ) the configured <ComUser_CbkTxAck> callback shall be invoked when the associated instance of the Com Low Proxy is called.

⌊ DRAFT g If the <ComUser_CbkTxErr> notification call- back is configured in the Com High Proxy (via the ComUserCallbackName (See [ECUC_Com_10036]), where the respective ComUserCallbackType (See [ECUC_- Com_10034]) is set to COM_TX_ERR ) the configured <ComUser_CbkTxErr> callback shall be invoked when the associated SwCluC_ComProxy_COMCbkTErr instance of the Com Low Proxy is called.

⌊ DRAFT g If the <ComUser_CbkTxTOut> timeout notifica- tion callback is configured in the Com High Proxy (via the ComUserCallback- Name (See [ECUC_Com_10036]), where the respective ComUserCallbackType (See [ECUC_Com_10034]) is set to COM_TX_TOUT ) the configured <ComUser_Cbk- TxTOut> callback shall be invoked when the associated SwCluC_ComProxy_COM- CbkTxTOut instance of the Com Low Proxy is called.

⌊ DRAFT g The Com Low Proxy shall create for each SwCluCComProxyBaseSocket a provided resource entry in the Binary Manifest .

⌊ DRAFT g The Com High Proxy shall create for each SwCluCComProxyBaseSocket a required resource entry in the Binary Mani- fest .

⌊ DRAFT g The function Com_ReceiveSignalGroup pro- vided by the Com High Proxy shall • invoke the Com_ReceiveSignalGroupArray API to fetch the data as uint8 array representation, AND • perform a transformation on the uint8 array to output the original data which will be passed to the RTE in the Applicative Software Cluster .

⌊ DRAFT g The function Com_ReceiveSignalGroupWith- MetaData provided by the Com High Proxy shall • invoke the Com_ReceiveSignalGroupArrayWithMetaData API to fetch the data as uint8 array representation, AND • perform a transformation on the uint8 array to output the original data which will be passed to the RTE in the Applicative Software Cluster .

⌊ DRAFT g Development Error Types of SwCluC Com Proxy The development error types defined for the SwCluC Com Proxy are listed in table Table 7.5.

⌊ DRAFT g The Com Low Proxy shall provide in its Co- mUserModuleCnf containers the ComUserCbkHandleId values for the configured ComUserSignal s and ComUserSignalGroup s, according to its internal implemen- tation requirements (e.g. to address the Com Low Proxy 's data structures).

⌊ DRAFT g The Com Proxy shall support that the ComUser- CbkHandleId of ComUserSignal s resp. ComUserSignalGroup s configured in Com users of the Applicative Software Cluster can change, without recon- figuration or rebuild of the Host Software Cluster .

⌊ DRAFT g The Com base socket shall implement the con- nection of the related callback functions • SwCluC_ComProxy_CbkRxAck • SwCluC_ComProxy_COMCbkInv • SwCluC_ComProxy_COMCbkRxTOut • SwCluC_ComProxy_COMCbkTAck • SwCluC_ComProxy_COMCbkTErr • SwCluC_ComProxy_COMCbkTxTOut

⌊ DRAFT g The Com High Proxy shall create for each Com- Signal and ComSignalGroup configured in Com a required resource entry in the Binary Manifest . Where the ComMainFunctionRx . ComMainRxPartitionRef and ComMainFunctionTx . ComMainTxPartitionRef are relevant to denote the EcucPartition .

⌊ DRAFT g The Com Low Proxy shall create for each Co- mUserSignal and ComUserSignalGroup configured in a SwCluCComProxyBas- eSocket . ComUserModuleCnf a provided resource entry in the Binary Mani- fest .

[SWS_SwCluC_02665] Serialization in Com_SendSignalGroup Status: DRAFT Upstream requirements: SRS_SwCluC_00211, SRS_SwCluC_00202 ⌈The function Com_SendSignalGroup provided by the Com High Proxy shall • perform a transformation from the original data passed from the RTE in Appli- cation Software Cluster to the uint8 array, AND • invoke the Com_SendSignalGroupArray API to send the data as uint8 array representation. ⌋

[SWS_SwCluC_02666] Serialization in Com_SendSignalGroupWithMetaData Status: DRAFT Upstream requirements: SRS_SwCluC_00211, SRS_SwCluC_00202 ⌈The function Com_SendSignalGroupWithMetaData provided by the Com High Proxy shall • perform a transformation from the original data passed from the RTE in Appli- cation Software Cluster to the uint8 array, AND • invoke the Com_SendSignalGroupArrayWithMetaData API to send the data as uint8 array representation. ⌋ module

[SWS_SwCluC_02669] Guard value calculation for ComSignal Upstream requirements: SRS_SwCluC_00211 ⌈The Com Proxy shall use the following attributes from an ComSignal for the guard value calculation • ComSignalEndianness • ComSignalType module • ComSignalLength • ComBitSize ⌋

[SWS_SwCluC_02670] Guard value calculation for ComSignalGroup Upstream requirements: SRS_SwCluC_00211 ⌈The Com Proxy shall use the following attributes from an ComSignalGroup for the guard value calculation • ComSignalGroupArrayAccess • From any ComGroupSignal of a ComSignalGroup – ComSignalEndianness – ComSignalType – ComSignalLength – ComBitSize ⌋

⌊ DRAFT g The Dem High Proxy shall provide the header file Dem.h .

⌊ DRAFT g The Dem High Proxy shall provide the symbolic name values of DemEventId s for Diagnostic Monitor s in the Applicative Software Cluster .

⌊ DRAFT g The Dem High Proxy shall provide the functions for Diagnostic Monitor s reporting Diagnostic Event s • Dem_ClearPrestoredFreezeFrame • Dem_PrestoreFreezeFrame • Dem_ResetEventDebounceStatus • Dem_ResetEventStatus • Dem_SetEventDisabled • Dem_SetEventStatus in the Applicative Software Cluster .

⌊ DRAFT g The Dem High Proxy shall provide the functions for Diagnostic Info of Diagnostic Event s • Dem_GetDTCOfEvent • Dem_GetDebouncingOfEvent • Dem_GetEventAvailable • Dem_GetEventExtendedDataRecordEx • Dem_GetEventFreezeFrameDataEx • Dem_GetEventUdsStatus • Dem_GetFaultDetectionCounter • Dem_GetMonitorStatus in the Applicative Software Cluster .

⌊ DRAFT g The Dem High Proxy shall support the optional configuration of a <Module>_DemGetFaultDetectionCounter<ForEvent> call- back, according to [ECUC_Dem_00630] and [ECUC_Dem_00631].

⌊ DRAFT g The Dem High Proxy shall support the optional configuration of a <Module>_DemInitMonitorFor<EventName> callback, accord- ing to [ECUC_Dem_00632] and [ECUC_Dem_00601].

⌊ DRAFT g The Dem High Proxy shall support the optional configuration of a <Module>_DemTriggerOnMonitorStatus callback, according to [ECUC_Dem_00936] and [ECUC_Dem_00937].

⌊ DRAFT g The Dem High Proxy shall support the optional configuration of a <Module>_DemClearEventAllowed<ForCondition> callback, according to [ECUC_Dem_00607] and [ECUC_Dem_00609].

⌊ DRAFT g The Dem High Proxy shall create one partition spe- cific Service Software Component per configured EcucPartition , with the name Dem_<EcucPartition shortName> .

⌊ DRAFT g The Dem High Proxy shall provide the ports belonging to a specific interface connection at the partition specific Service Soft- ware Component, to which the using SwComponentPrototype is mapped.

⌊ DRAFT g In case a Diagnostic Event configured in the Dem High Proxy is not connected to any Dem Low Proxy , the functions / opera- tions • Dem_ClearPrestoredFreezeFrame / ClearPrestoredFreezeFrame • Dem_PrestoreFreezeFrame / PrestoreFreezeFrame • Dem_ResetEventDebounceStatus / ResetEventDebounceStatus • Dem_ResetEventStatus / ResetEventStatus • Dem_SetEventDisabled / SetEventDisabled • Dem_SetEventStatus / SetEventStatus • Dem_SetEventStatusWithMonitorData / SetEventStatusWithMoni- torData • Dem_SetWIRStatus / SetWIRStatus of the Dem High Proxy shall return E_NOT_OK .

⌊ DRAFT g In case a Diagnostic Event configured in the Dem High Proxy is not connected to any Dem Low Proxy , the Dem High Proxy shall return DEM_E_NO_DTC_AVAILABLE and the value 0 for the DTCOfEvent ar- gument, when Dem_GetDTCOfEvent / GetDTCOfEvent is called.

⌊ DRAFT g In case a Diagnostic Event configured in the Dem High Proxy is not connected to any Dem Low Proxy , the Dem High Proxy shall return E_NOT_OK and the value 0 for the DebouncingState argument, when Dem_GetDebouncingOfEvent / GetDebouncingOfEvent is called.

⌊ DRAFT g In case a Diagnostic Event configured in the Dem High Proxy is not connected to any Dem Low Proxy , the Dem High Proxy shall return E_NOT_OK and the value FALSE for the AvailableStatus argu- ment, when Dem_GetEventAvailable / GetEventAvailable is called.

⌊ DRAFT g In case a Diagnostic Event configured in the Dem High Proxy is not connected to any Dem Low Proxy , the Dem High Proxy shall return E_NOT_OK and the value 0 for the Bufsize argument, when Dem_GetEventExtendedDataRecordEx / GetEventExtendedDataRecordEx is called. The Bufsize argument stays unmodified.

⌊ DRAFT g In case a Diagnostic Event configured in the Dem High Proxy is not connected to any Dem Low Proxy , the Dem High Proxy shall return E_NOT_OK and the value 0 for the Bufsize argument, when Dem_- GetEventFreezeFrameDataEx / GetEventFreezeFrameDataEx is called. The Bufsize argument stays unmodified.

⌊ DRAFT g In case a Diagnostic Event configured in the Dem High Proxy is not connected to any Dem Low Proxy , the Dem High Proxy shall return E_NOT_OK and the value 0 for the UDSStatusByte argu- ment, when Dem_GetEventUdsStatus / GetEventUdsStatus is called.

⌊ DRAFT g In case a Diagnostic Event configured in the Dem High Proxy is not connected to any Dem Low Proxy , the Dem High Proxy shall return E_NOT_OK and the value 0 for the FaultDetectionCounter argu- ment, when Dem_GetFaultDetectionCounter / GetFaultDetectionCounter is called.

⌊ DRAFT g In case a Diagnostic Event configured in the Dem High Proxy is not connected to any Dem Low Proxy , the Dem High Proxy shall return E_NOT_OK and the value 0 for the MonitorStatus argument, when Dem_GetMonitorStatus / GetMonitorStatus is called.

⌊ DRAFT g The Dem Low Proxy shall provide the entry func- tions for Diagnostic Event reporting and info, according to [SWS_SwCluC_02702] and [SWS_SwCluC_02702], once per configured SwCluCDemProxyBaseSocket at the EcucPartition configured by SwCluCDemProxyBaseSocket . SwCluCProx- yEcucPartitionRef . In case the SwCluCDemProxyUsedSatelliteRef is set, the EcucPartition shall be changed, before the Dem API is called.

⌊ DRAFT g The Dem High Proxy shall provide the ports be- longing to a specific Diagnostic Event • Event_{Name} • EventStatus_{Name} at the partition specific Service Software Component, to which the using SwCompo- nentPrototype is mapped.

⌊ DRAFT g The Dem High Proxy shall provide the DiagnosticMonitor_MonitorData_{Name} port for each specific Di- agnostic Event , where DemEventReportingType is set to STAN- DARD_REPORTING_WITH_MONITOR_DATA at the partition specific Service Software Component, to which the using SwComponentPrototype is mapped.

⌊ DRAFT g The Dem High Proxy shall provide the CB- ClrEvt_{Name} port for each specific Diagnostic Event , where DemCallback- ClearEventAllowed is configured at the partition specific Service Software Com- ponent, to which the using SwComponentPrototype is mapped.

⌊ DRAFT g The Dem High Proxy shall provide the CB- FaultDetectCtr_{Name} port for each specific Diagnostic Event , where Dem- CallbackGetFDC is configured at the partition specific Service Software Component, to which the using SwComponentPrototype is mapped.

⌊ DRAFT g The Dem High Proxy shall provide the CBInitEvt_{Name} port for each specific Diagnostic Event , where DemCall- backInitMForE is configured at the partition specific Service Software Component, to which the using SwComponentPrototype is mapped.

⌊ DRAFT g The Dem Low Proxy shall provide, for each SwCluCDemProxyBaseSocket , a SwCluC_DemProxy_Init API, to initialize the Dem High Proxy of an Applicative Software Cluster . This shall be one element of the service resource SwCluCDemProxyBaseSocket .

⌊ DRAFT g The Dem Low Proxy shall provide an instance of a <Module>_DemGetFaultDetectionCounter<ForEvent> per configured Di- agnostic Event ( SwCluCDemProxyDiagnosticEvent ), in the Dem Low Proxy , if DemDebounceAlgorithmClass is set to DebounceMonitorInternal.

⌊ DRAFT g The Dem Low Proxy shall provide an instance of a <Module>_DemInitMonitorFor<EventName> per configured Diagnostic Event ( SwCluCDemProxyDiagnosticEvent ), in the Dem Low Proxy .

⌊ DRAFT g The Dem Low Proxy shall provide an instance of a <Module>_DemTriggerOnMonitorStatus per configured Diagnostic Event ( SwCluCDemProxyDiagnosticEvent ), in the Dem Low Proxy .

⌊ DRAFT g The Dem Low Proxy shall provide an instance of a <Module>_DemClearEventAllowed<ForCondition> per configured Diag- nostic Event ( SwCluCDemProxyDiagnosticEvent ), in the Dem Low Proxy .

⌊ DRAFT g The Dem Low Proxy implementation shall de- scribe the Diagnostic Events s provided to Dem High Proxy s via Diagnos- ticEventNeeds and DiagnosticEventInfoNeeds , derived from the CpSoft- wareClusterServiceResource . resourceNeeds .

⌊ DRAFT g In case a Diagnostic Event configured in the Dem Low Proxy is not connected to any Dem High Proxy , the callback functions • <Module>_DemGetFaultDetectionCounter<ForEvent> • <Module>_DemClearEventAllowed<ForCondition> of the Dem High Proxy shall return E_NOT_OK .

⌊ DRAFT g In case a Diagnostic Event configured in the Dem Low Proxy is not connected to any Dem High Proxy , the callback functions • <Module>_DemInitMonitorFor<EventName> • <Module>_DemTriggerOnMonitorStatus of the Dem High Proxy shall return E_OK .

⌊ DRAFT g The Dem High Proxy shall provide the function Dem_SetEventStatusWithMonitorData , for Diagnostic Monitor s reporting Diagnostic Event s with monitor data in the Applicative Software Clus- ter .

⌊ DRAFT g The Dem High Proxy shall support the optional configuration of a <Module>_DemTriggerOnEventData callback, according to [ECUC_Dem_00606] and [ECUC_Dem_00608].

⌊ DRAFT g The Dem High Proxy shall support the optional configuration of a <Module>_DemTriggerOnEventUdsStatus callback, according to [ECUC_Dem_00628] and [ECUC_Dem_00629].

⌊ DRAFT g The Dem High Proxy shall provide the function Dem_SetWIRStatus , for Diagnostic Monitor s reporting Diagnostic Event s in the Applicative Software Cluster .

⌊ DRAFT g The Dem High Proxy shall provide the EventStatus_{Name} port for each specific Diagnostic Event at the partition specific Service Software Component, to which the using SwComponentPrototype is mapped.

⌊ DRAFT g The Dem High Proxy shall provide the CB- DataEvt_{Name} port for each specific Diagnostic Event , where DemCall- backEventDataChanged is configured at the partition specific Service Software Component, to which the using SwComponentPrototype is mapped.

⌊ DRAFT g The Dem High Proxy shall provide the CBEven- tUdsStatusChanged_{EventName}_{CallbackName} port for each specific Di- agnostic Event , where DemCallbackEventUdsStatusChanged is configured at the partition specific Service Software Component, to which the using SwComponent- Prototype is mapped.

⌊ DRAFT g The Dem High Proxy shall provide the CBMon- itorStatusChanged_{EventName}_{CallbackName} port for each specific Di- agnostic Event , where DemCallbackMonitorStatusChanged is configured at the partition specific Service Software Component, to which the using SwComponent- Prototype is mapped.

⌊ DRAFT g The Dem High Proxy shall create for each SwCluCDcmProxyBaseSocket a required resource entry in the Binary Mani- fest .

⌊ DRAFT g The Dem High Proxy shall create for each di- agnostic event proxy - configured via SwCluCDemProxyDiagnosticEvent container - a required resource entry in the Binary Manifest .

⌊ DRAFT g The Dem Low Proxy shall create, for each SwCluCDcmProxyBaseSocket , a provided resource entry in the Binary Mani- fest .

⌊ DRAFT g The Dem Low Proxy shall create for, each diag- nostic event proxy - configured via SwCluCDemProxyDiagnosticEvent con- tainer -, a provided resource entry in the Binary Manifest .

⌊ DRAFT g The Dem High Proxy code, and related AUTOSAR model descriptions, shall only be created, if the configuration param- eter SwCluCProxyGenerationDem is set to HIGH_PROXY .

⌊ DRAFT g The Dem Low Proxy code, and related AUTOSAR model descriptions, shall only be created, if the configuration param- eter SwCluCProxyGenerationDem is set to LOW_PROXY .

⌊ DRAFT g Development Error Types of SwCluC Dem Proxy The development error types defined for the SwCluC Dem Proxy are listed in table Table 7.8.

⌊ DRAFT g If development error detection is enabled for Dem High Proxy , the APIs • Dem_ClearPrestoredFreezeFrame • Dem_PrestoreFreezeFrame • Dem_ResetEventDebounceStatus • Dem_ResetEventStatus • Dem_SetEventDisabled • Dem_SetEventStatus • Dem_GetDTCOfEvent • Dem_GetDebouncingOfEvent • Dem_GetEventAvailable • Dem_GetEventExtendedDataRecordEx • Dem_GetEventFreezeFrameDataEx • Dem_GetEventUdsStatus • Dem_GetFaultDetectionCounter • Dem_GetMonitorStatus • Dem_SetEventStatusWithMonitorData • Dem_SetWIRStatus shall report the DET error DEM_E_UNINIT , when Dem High Proxy is not yet initial- ized.

⌊ DRAFT g The Cross Cluster Communication of the Software Cluster Connection shall implement a Cross Software Cluster Communication Plug-In according to document [9].

⌊ DRAFT g The Vendor Specific Module Definition (see document [10]) of the Software Cluster Connection shall provide a defi- nition of the container RteRipsPluginProps as a subContainer of the container SwCluCXcc with the shortName RteRipsPluginProps .

⌊ DRAFT g The Cross Cluster Communication of the Software Cluster Connection shall implement the RTE Implementation Plug-In functionality for a Communication Graph , if • a FlatInstanceDescriptor references the Communication Graph AND • and the rtePluginProps . associatedCrossSwClusterComRtePlugin ref- erences the RteRipsPluginProps container of this Cross Cluster Com- munication implementation.

⌊ DRAFT g The Cross Cluster Communication of the Software Cluster Connection shall put one Resource Entry for each associ- ated Communication Graph into the Binary Manifest .

⌊ DRAFT g The SwCluCBManifResourceRef of the Re- source Entry shall reference the CpSoftwareClusterCommunicationRe- source which is mapped by the PortElementToCommunicationResourceMap- ping to the Communication Graph .

⌊ DRAFT g The SwCluCBManifResourceGuardValue of the Resource Entry shall be calculated out of the following properties: • data range • resolution • physical meaning • encoding • structure in memory

⌊ DRAFT g The Cross Cluster Communication of the Software Cluster Connection shall provide one constant default parameter in- stance for each assigned Parameter Communication Graph , which contains NO PPortPrototype .

⌊ DRAFT g The default value instance shall be mapped to a CALPRM memory section, according to document [8].

⌊ DRAFT g The default value instance shall be initialized ac- cording to the ParameterRequireComSpec . initValue , in the RPortPrototype at the CompositionSwComponentType of the rootSoftwareComposition of the Ecu Extract .

⌊ DRAFT g If the corresponding resource in the Binary Man- ifest is connected, the Rte_Rips_Prm shall return the value of the connected pa- rameter.

⌊ DRAFT g If the corresponding resource in the Binary Man- ifest is NOT connected, the Rte_Rips_Prm shall return the value of the default pa- rameter instance of [SWS_SwCluC_03006].

⌊ DRAFT g For each assigned Parameter Communication Graph , which contains the PPortPrototype , the Cross Cluster Communica- tion of the Software Cluster Connection shall make the parameter in- stance , according to [SWS_Rte_80130], accessible for other Software Cluster s, via a Resource Entry in the Binary Manifest .

⌊ DRAFT g If the implementation of a Cross Cluster Com- munication requires some basic infrastructure from the Host Software Clus- ter , it shall use the means of the SwCluCXccBaseSocket configuration to link to the resource pool.

⌊ DRAFT g The Cross Cluster Communication of the Software Cluster Connection shall put one Resource Entry for each asso- ciated SwCluCXccBaseSocket into the Binary Manifest .

⌊ DRAFT g The Cross Cluster Communication shall provide a Complex Driver Software Component on each EcucPartition where a mode switch port needs to be provided. This component is later called mode proxy component .

⌊ DRAFT g The Cross Cluster Communication shall provide a provided mode switch port on each mode proxy component where a mode switch port needs to be provided.

⌊ DRAFT g The Cross Cluster Communication shall provide the AssemblySwConnector s between the provided mode switch ports and the required mode switch ports at the software components requiring the mode.

⌊ DRAFT g The Cross Cluster Communication shall provide a mode switch notification runnable with an OsTaskExecution- Event , for each mode on each partition where a mode switch notification is configured. The RunnableEntity shall define a ModeSwitchPoint .

⌊ DRAFT g When the mode switch notification runnable is executed, it shall write the actual on-transition value via Rte_Switch to the RTE.

⌊ DRAFT g The Cross Cluster Communication shall sig- nal the current on-transition value to other Software Clusters , before the mode switch according to [SWS_Rte_02665] starts.

⌊ DRAFT g The Cross Cluster Communication of the Host Software Cluster shall implement a mode manager for each mode which needs to be provided by an Applicative Software Cluster .

⌊ DRAFT g The Cross Cluster Communication of the Host Software Cluster shall enqueue the current on-transition values sig- naled by Applicative Software Cluster , via the related mode manager . ([SWS_SwCluC_03023])

⌊ DRAFT g The Cross Cluster Communication of the Host Software Cluster shall notify the Applicative Software Cluster , when a mode switch tasks starts.

⌊ DRAFT g The Cross Cluster Communication of the Host Software Cluster shall notify the Cross Cluster Communication of the Applicative Software Cluster , when all mode switch tasks run to end.

⌊ DRAFT g In case the Applicative Software Cluster provides the mode, the Cross Cluster Communication of the Host Software Cluster shall notify the Cross Cluster Communication of the Applicative Software Cluster , when mode switch tasks run to end.

⌊ DRAFT g In case the Applicative Software Cluster provides the mode, the Cross Cluster Communication of the Applicative Software Cluster notifies the RTE via Rte_Rips_DequeueModeSwitch , when a mode switch task known by this RTE runs to end. The Cross Cluster Communi- cation has to guarantee that the last call of Rte_Rips_DequeueModeSwitch is not done before the last on-entry ExecutableEntity in the whole clustered system terminated.

⌊ DRAFT g The Cross Cluster Communication shall provide a Complex Driver Software Component on each EcucPartition , where mode switch task are configured. This component is later called mode proxy com- ponent .

⌊ DRAFT g The Cross Cluster Communication shall provide RunnableEntity s to detect the start and end of any mode switch task, which is related to mode communication cross Software Clusters .

⌊ DRAFT g The Cross Cluster Communication shall provide the AssemblySwConnector s between the provided mode switch ports of the mode proxy component and the required mode switch ports at the soft- ware components requiring the mode, if the mode is required by the Host Software Cluster .

⌊ DRAFT g The Cross Cluster Communication of the Software Cluster Connection shall normalize the numerical values of attributes, before using them for the SwCluCBManifResourceGuardValue calculation, in such a way that compatible numerical values according to [TPS_GST_02501] result in the identical guard value.

⌊ DRAFT g The Cross Cluster Communication shall use the following attributes for the SwCluCBManifResourceGuardValue calculation for a Data Communication Graph : • PPortPrototype . providedInterface • RPortPrototype . requiredInterface • CpSoftwareClusterCommunicationResource . comProps . sendIndica- tion – in case of SenderReceiverInterface  VariableDataPrototype . type  VariableDataPrototype . swDataDefProps  SenderReceiverInterface . invalidationPolicy . handleIn- valid (if existing for the VariableDataPrototype , else dontIn- validate applies) – in case of NvDataInterface  VariableDataPrototype . type  VariableDataPrototype . swDataDefProps – in case of ParameterInterface  ParameterDataPrototype . type  ParameterDataPrototype . swDataDefProps Additionally, attributes of VariableDataPrototype / ParameterDataPro- totype . type according to [SWS_SwCluC_03035] and [SWS_SwCluC_03036] apply.

⌊ DRAFT g The Cross Cluster Communication shall use the following attributes for the referenced ApplicationDataType for the SwCluCB- ManifResourceGuardValue calculation: • in case the AutosarDataPrototype . type refers to a ApplicationPrimi- tiveDataType – ApplicationPrimitiveDataType . category – ApplicationPrimitiveDataType . swDataDefProps • in case the AutosarDataPrototype . type refers to a ApplicationArray- DataType – ApplicationArrayDataType . dynamicArraySizeProfile (if exist- ing) – ApplicationArrayDataType . element – ApplicationArrayElement . type – ApplicationArrayElement . arraySizeSemantics (if existing, else fixedSize applies) – ApplicationArrayElement . arraySizeHandling (if existing) – ApplicationArrayElement . maxNumberOfElements • in case the AutosarDataPrototype . type refers to a ApplicationRecord- DataType – ApplicationRecordDataType . element s {ordered} – ApplicationRecordElement . type – ApplicationRecordElement . isOptional (if existing, else false ap- plies) Additionally, the attributes of the mapped ImplementationDataType according to [SWS_SwCluC_03036] and the attributes of SwDataDefProps according to [SWS_SwCluC_03037] apply.

⌊ DRAFT g The Cross Cluster Communication shall use the following attributes for the referenced or mapped ImplementationDataType for the SwCluCBManifResourceGuardValue calculation: • in case the AutosarDataPrototype . type refers to an Implementation- DataType of category TYPE_REFERENCE or the ApplicationDataType ac- cording to [SWS_SwCluC_03036] is mapped to an ImplementationDataType of category TYPE_REFERENCE – ImplementationDataType . swDataDefProps in case the AutosarDataPrototype . type refers to an Implementation- DataType of category VALUE or the ApplicationDataType according to [SWS_SwCluC_03036] is mapped to an ImplementationDataType of cate- gory VALUE – ImplementationDataType . swDataDefProps • in case the AutosarDataPrototype . type refers to an Implementation- DataType of category ARRAY or the ApplicationDataType according to [SWS_SwCluC_03036] is mapped to an ImplementationDataType of cate- gory ARRAY – ImplementationDataType . dynamicArraySizeProfile (if existing) – ImplementationDataType . swDataDefProps – ImplementationDataType . subElement – ImplementationDataTypeElement . arraySizeSemantics (if exist- ing, else fixedSize applies) – ImplementationDataTypeElement . arraySizeHandling (if existing) – ImplementationDataTypeElement . swDataDefProps • in case AutosarDataPrototype . type refers to an Implementation- DataType of category STRUCTURE or the ApplicationDataType according to [SWS_SwCluC_03036] is mapped to an ImplementationDataType of cat- egory STRUCTURE – ImplementationDataType . swDataDefProps – ImplementationDataType . isStructWithOptionalElement (if exist- ing, else false applies) – ImplementationDataType . subElement {ordered} – ImplementationDataTypeElement . arraySizeSemantics (if exist- ing, else fixedSize applies) – ImplementationDataTypeElement . arraySizeHandling (if existing) – ImplementationDataTypeElement . swDataDefProps Additionally, the attributes of SwDataDefProps according to [SWS_SwCluC_03037] apply.

⌊ DRAFT g The Cross Cluster Communication shall use the following attributes for the given SwDataDefProps for the SwCluCBManifRe- sourceGuardValue calculation: • SwDataDefProps . additionalNativeTypeQualifier (if existing) • SwDataDefProps . swImplPolicy (if existing, else standard applies) • SwDataDefProps . invalidValue (if existing) • SwDataDefProps . unit (if existing, else CompuMethod . unit applies) • SwDataDefProps . dataConstr (if existing) • SwDataDefProps . compuMethod (if existing) • SwDataDefProps . swTextProps (if existing) • SwDataDefProps . baseType (if existing) • SwDataDefProps . swValueBlockSize (if existing) • SwDataDefProps . swValueBlockSizeMult (if existing) • SwDataDefProps . valueAxisDataType (if existing) • SwDataDefProps . implementationDataType (if existing) Here, the prioritization of SwDataDefProps attributes according to [constr_- 1015] applies. Only the most prior SwDataDefProps attributes are considered. Additionally, the attributes of Unit , CompuMethod , DataConstr , and BaseType according to [SWS_SwCluC_03038], [SWS_SwCluC_03039], [SWS_SwCluC_03042], [SWS_SwCluC_03043], and [SWS_SwCluC_03044] apply.

⌊ DRAFT g The Cross Cluster Communication shall use the following attributes for the given Unit for the SwCluCBManifResourceGuard- Value calculation: • Unit . factorSiToUnit (if existing, else 1 applies) • Unit . offsetSiToUnit (if existing, else 0 applies) • Unit . physicalDimension (if existing, else [SWS_SwCluC_03041] applies) Additionally, the attributes of PhysicalDimension according to [SWS_SwCluC_03040] and [SWS_SwCluC_03041] apply.

⌊ DRAFT g In case no Unit is given for the SwCluCBMan- ifResourceGuardValue calculation, the Cross Cluster Communication shall use the following attribute values: • Unit . factorSiToUnit = 1 • Unit . offsetSiToUnit = 0 • Unit . physicalDimension according to [SWS_SwCluC_03041] Additionally, the attributes of PhysicalDimension according to [SWS_SwCluC_03041] apply.

⌊ DRAFT g The Cross Cluster Communication shall use the following attributes for the given PhysicalDimension for the SwCluCBMani- fResourceGuardValue calculation: • PhysicalDimension . shortName • PhysicalDimension . currentExp (if existing, else 0 applies) • PhysicalDimension . lengthExp (if existing, else 0 applies) • PhysicalDimension . luminousIntensityExp (if existing, else 0 applies) • PhysicalDimension . massExp (if existing, else 0 applies) • PhysicalDimension . molarAmountExp (if existing, else 0 applies) • PhysicalDimension . temperatureExp (if existing, else 0 applies) • PhysicalDimension . timeExp (if existing, else 0 applies)

⌊ DRAFT g In case no PhysicalDimension is given, the Cross Cluster Communication shall use the following attribute values for the SwCluCBManifResourceGuardValue calculation: • PhysicalDimension . shortName = NoDimension • PhysicalDimension . currentExp = 0 • PhysicalDimension . lengthExp = 0 • PhysicalDimension . luminousIntensityExp = 0 • PhysicalDimension . massExp = 0 • PhysicalDimension . molarAmountExp = 0 • PhysicalDimension . temperatureExp = 0 • PhysicalDimension . timeExp = 0

⌊ DRAFT g The Cross Cluster Communication shall use the following attributes for the given CompuMethod for the SwCluCBManifRe- sourceGuardValue calculation: • CompuMethod . unit • in case the CompuMethod . category is IDENTICAL – it is treated like a CompuMethod where the category is LINEAR where the CompuMethod . compuPhysToInternal . compuScale yield the con- version int = N 0 + N 1  phys D 0 if N 0  0 && N 1  1 && D 0  0 • in case the CompuMethod . category is LINEAR – CompuMethod . compuPhysToInternal . compuScale OR – CompuMethod . compuInternalToPhys . compuScale where the compuInternalToPhys coefficients are converted to equivalent compuPhysToInternal coefficients.  CompuScale . compuNumerator . v s {ordered}  CompuScale . compuDenominator . v • in case the CompuMethod . category is SCALE_LINEAR – CompuMethod . compuPhysToInternal . compuScale s – CompuMethod . compuPhysToInternal . compuDefaultValue (if exist- ing) OR – CompuMethod . compuInternalToPhys . compuScale s – CompuMethod . compuInternalToPhys . compuDefaultValue (if exist- ing)  CompuScale . upperLimit  CompuScale . lowerLimit  CompuScale . compuNumerator . v s {ordered}  CompuScale . compuDenominator . v • in case the CompuMethod . category is RAT_FUNC with 2 compuNumerator coefficients and 1 compuDenominator coefficient – this case is treated like a CompuMethod where the category is LINEAR • in case the CompuMethod . category is RAT_FUNC not matching the LINEAR case – CompuMethod . compuPhysToInternal . compuScale – CompuMethod . compuPhysToInternal . compuDefaultValue (if exist- ing) AND – CompuMethod . compuInternalToPhys . compuScale – CompuMethod . compuInternalToPhys . compuDefaultValue (if exist- ing)  CompuScale . upperLimit  CompuScale . lowerLimit  CompuScale . compuInverseValue . vf (if existing)  CompuScale . compuNumerator . v s {ordered}  CompuScale . compuDenominator . v {ordered} • in case the CompuMethod . category is SCALE_RAT_FUNC – CompuMethod . compuPhysToInternal . compuScale s – CompuMethod . compuPhysToInternal . compuDefaultValue (if exist- ing) AND – CompuMethod . compuInternalToPhys . compuScale s – CompuMethod . compuInternalToPhys . compuDefaultValue (if exist- ing)  CompuScale . upperLimit  CompuScale . lowerLimit  CompuScale . compuInverseValue . vf (if existing)  CompuScale . compuNumerator . v s {ordered}  CompuScale . compuDenominator . v {ordered} • in case the CompuMethod . category is TEXTTABLE – CompuMethod . compuInternalToPhys . compuScale s – CompuMethod . compuInternalToPhys . compuDefaultValue (if exist- ing)  CompuScale . upperLimit  CompuScale . lowerLimit  CompuScale . compuInverseValue . vf (if existing)  CompuScale . compuConst . vt • in case the CompuMethod . category is BITFIELD_TEXTTABLE – CompuMethod . compuInternalToPhys . compuScale s – CompuMethod . compuInternalToPhys . compuDefaultValue (if exist- ing)  CompuScale . upperLimit  CompuScale . lowerLimit  CompuScale . mask  CompuScale . compuInverseValue . vf (if existing)  CompuScale . compuConst . vt • in case the CompuMethod . category is SCALE_LINEAR_AND_TEXTTABLE – CompuMethod . compuInternalToPhys . compuScale s – CompuMethod . compuInternalToPhys . compuDefaultValue (if exist- ing)  CompuScale . upperLimit  CompuScale . lowerLimit  CompuScale . mask  CompuScale . compuInverseValue . vf (if existing)  CompuScale . compuConst . vt (if existing)  CompuScale . compuNumerator . v s {ordered} (if existing)  CompuScale . compuDenominator . v (if existing) • in case the CompuMethod . category is SCALE_RATIONAL_AND_TEXTTABLE – CompuMethod . compuPhysToInternal . compuScale s – CompuMethod . compuPhysToInternal . compuDefaultValue (if exist- ing) AND – CompuMethod . compuInternalToPhys . compuScale s – CompuMethod . compuInternalToPhys . compuDefaultValue (if exist- ing)  CompuScale . upperLimit  CompuScale . lowerLimit  CompuScale . mask  CompuScale . compuInverseValue . vf (if existing)  CompuScale . compuConst . vt (if existing)  CompuScale . compuNumerator . v s {ordered} (if existing)  CompuScale . compuDenominator . v {ordered} (if existing) • in case the CompuMethod . category is TAB_NOINTP – CompuMethod . compuInternalToPhys . compuScale s – CompuMethod . compuInternalToPhys . compuDefaultValue (if exist- ing)  CompuScale . upperLimit  CompuScale . lowerLimit  CompuScale . compuInverseValue . vf (if existing)  CompuScale . compuConst . vt (if existing) Additionally, the attributes of Unit according to [SWS_SwCluC_03038], [SWS_SwCluC_03039] apply.

⌊ DRAFT g The Cross Cluster Communication shall use the following attributes for the given DataConstr for the SwCluCBManifResource- GuardValue calculation: • DataConstr . dataConstrRule . physConstrs . upperLimit (if existing) • DataConstr . dataConstrRule . physConstrs . lowerLimit (if existing) • DataConstr . dataConstrRule . physConstrs . monotony (if existing) • DataConstr . dataConstrRule . physConstrs . maxGradient (if existing) • DataConstr . dataConstrRule . physConstrs . maxDiff (if existing) • DataConstr . dataConstrRule . internalConstrs . upperLimit (if existing, else based on baseTypeEncoding and baseTypeSize the technical upper limit is taken) • DataConstr . dataConstrRule . internalConstrs . lowerLimit (if existing, else based on baseTypeEncoding and baseTypeSize the technical lower limit is taken) • DataConstr . dataConstrRule . internalConstrs . monotony (if existing, else noMonotony ) • DataConstr . dataConstrRule . internalConstrs . maxGradient (if exist- ing) • DataConstr . dataConstrRule . internalConstrs . maxDiff (if existing)

⌊ DRAFT g The Cross Cluster Communication shall use the following attributes for the given SwBaseType for the SwCluCBManifResource- GuardValue calculation: • SwBaseType . baseTypeEncoding • SwBaseType . baseTypeSize • SwBaseType . byteOrder • SwBaseType . nativeDeclaration • SwBaseType . memAlignment (if existing, else 0 applies)

⌊ DRAFT g The Cross Cluster Communication shall use the following attributes for the SwCluCBManifResourceGuardValue calculation for a Mode Communication Graph : • PPortPrototype . providedInterface • RPortPrototype . requiredInterface • ModeDeclarationGroupPrototype . type • ModeDeclarationGroup . category • ModeDeclarationGroup . initialMode • ModeDeclarationGroup . modeDeclaration s • ModeDeclarationGroup . onTransitionValue (in case ModeDeclara- tionGroup . category == EXPLICIT_ORDER ) • ModeDeclarationGroup . modeUserErrorBehavior (if existing) • ModeDeclarationGroup . modeManagerErrorBehavior (if existing) • ModeDeclarationGroup . modeTransition s (if existing) for each ModeDec- laration the following attributes apply: – ModeDeclaration . shortName – ModeDeclaration . value (in case ModeDeclarationGroup . category == EXPLICIT_ORDER ) for each ModeErrorBehavior the following attributes apply: – ModeErrorBehavior . errorReactionPolicy – ModeErrorBehavior . defaultMode (if existing) for each ModeTransition the following attributes apply: – ModeTransition . exitedMode – ModeTransition . enteredMode

⌊ DRAFT g The Cross Cluster Communication shall use the following attributes for the SwCluCBManifResourceGuardValue calculation for a Trigger Communication Graph : • PPortPrototype . providedInterface • RPortPrototype . requiredInterface • Trigger . swImplPolicy (if existing, else standard applies)

⌊ DRAFT g The Cross Cluster Communication shall use the following attributes for the SwCluCBManifResourceGuardValue calculation for a Client Server Communication Graph : • PPortPrototype . providedInterface • RPortPrototype . requiredInterface – ClientServerOperation . argument s {ordered}  ArgumentDataPrototype . type  ArgumentDataPrototype . direction – ClientServerOperation . possibleError . errorCode (if existing, else one errorCode = 0 is applied) Additionally, attributes of ArgumentDataPrototype . type according to [SWS_SwCluC_03035] and [SWS_SwCluC_03036] apply.

⌊ DRAFT g The Cross Cluster Communication shall provide a Complex Driver Software Component, on each EcucPartition where a trigger port needs to be provided. This component is later called trigger proxy component .

⌊ DRAFT g The Cross Cluster Communication shall provide a provided trigger port , on each trigger proxy component .

⌊ DRAFT g The Cross Cluster Communication shall provide the AssemblySwConnector s between the provided trigger ports and the required trigger ports , at the software components requiring the trigger.

⌊ DRAFT g The Cross Cluster Communication shall provide a trigger notification runnable with an OsTaskExecutionEvent , for each trigger on each partition a trigger notification is configured. The RunnableEntity shall define a ExternalTriggeringPoint .

⌊ DRAFT g When the trigger notification runnable is executed, it shall raise the trigger via Rte_Trigger to the RTE.

⌊ DRAFT g The Cross Cluster Communication shall sig- nal to other Software Clusters that a trigger was raised.

⌊ DRAFT g The Cross Cluster Communication shall, at the Software Cluster providing the trigger, add a Provided Resource En- try and, at Software Clusters requiring the trigger, an according Require Re- source Entry in the Binary Manifest .

⌊ DRAFT g The Cross Cluster Communication shall add at the Software Cluster providing the mode a Provided Resource Entry , and at any Software Cluster requiring the trigger an according Require Resource Entry in the Binary Manifest .

⌊ DRAFT g The Cross Cluster Communication of the Host Software Cluster shall implement a trigger source for each trigger, which needs to be provided by an Applicative Software Cluster .

⌊ DRAFT g The Cross Cluster Communication of the Host Software Cluster shall raise the triggers signaled by Applicative Software Clusters , via the related trigger source . ([SWS_SwCluC_03058])