Backward Compatibility Sample Clauses

Backward Compatibility. (a) During the period beginning on the Effective Date and ending on the fifteenth (15th) anniversary of the Original Effective Date, to the extent that: (i) TSI makes a generally commercially available release (a “GA” release) of a version of TSI’s Rendezvous product that is not backward compatible with the immediately preceding GA version of Rendezvous; (ii) TSI replaces the TSI Product known as “Rendezvous” with another TSI Product as TSI’s flagship messaging product (the “Non-RV Flagship Product”) and the Non-RV Flagship Product does not constitute a successor product to Rendezvous (as described in Section 3.2), and such Non-RV Flagship Product is not backward compatible with the then-current GA version of Rendezvous as of the date of GA release of such Non-RV Flagship Product; or (iii) TSI makes successive GA release of a version of the Non-RV Flagship Product that is not backward compatible with the immediately preceding GA version of such Non-RV Flagship Product, then upon written notice from Reuters identifying with specificity such failure of backward compatibility and specifically referencing this Section 3.4 of this Agreement (the “BC Notice”), TSI shall use commercially reasonable efforts to enable backward compatibility between such products (whether by provision of a patch, a software tool or other mechanism) and provide such mechanism to Reuters as soon as commercially practicable. If TSI has not provided such mechanism for backward compatibility within ninety (90) days of the date of the BC Notice, then Reuters shall have the right, at any time prior to TSI providing such mechanism to Reuters (but no more than six (6) months from the date of the BC Notice), to request those portions of the Source Code for such non-backward compatible product that are necessary to enable backward compatibility, if Reuters does not already have possession of such Source Code, by written notice to TSI requesting such Source Code and specifically referencing this Section 3.4 of this Agreement. Upon receipt of such written notice, TSI shall promptly provide such Source Code to Reuters, and Reuters shall have the right to use such Source Code solely for the purpose of enabling such backward compatibility as described above, and subject to the restrictions set forth in subsection (b) below. Reuters shall have up to 12 months from the date of the BC Notice to attempt to correct the identified backward compatibility problem. For purposes of this Section 3.4, “backwar...

Backward Compatibility. Any subsequent Program will be backward compatible with the previous version of the Program provided by S-A under this Agreement.

Backward Compatibility. The Enhancement shall be backward-compatible, such that populating and broadcasting SV data containing Pseudo-LRN records will not be visible to User systems that have not performed the steps necessary to use the functionality afforded by the Enhancement. Because the Enhancement shall be backward-compatible, its mere deployment in the NPAC/SMS will not result in any obligatory changes to SOA or LSMS systems for Users not opting to use their SOA or LSMS for the functionality afforded by the Enhancement.

Backward Compatibility. Supplier shall cause each Software revision level, during the Software Warranty Period or such longer period not to exceed [***] as Mirror continuously maintains and pays for Software maintenance in accordance with this Agreement, to be backwards compatible with existing Software and the immediately preceding Software Patches made available to Mirror by Supplier.

Backward Compatibility. ‌ ODV is backward compatible in the sense that existing collections and configuration files created under previous ODV versions are fully supported.‌

Backward Compatibility. Transcrypt may sell PRODUCTS incorporating MOTOROLA analog trunking, or MOTOROLA proprietary 12 kBs encryption only to those customers who have purchased or are in the process of purchasing ASTRO(R) or APCO 25 compliant digital Infrastructure.

Backward Compatibility. ‌ We built a setup for evaluating backward compatibility of FlexRay traffic that includes key sharing sequences in the Fig. 13. Signaling during key exchange between the S12X nodes at 1Mbps Fig. 14. Signaling during key exchange between the TriCore nodes at 5Mbps TABLE IV‌ series FlexRay network [29]. Node count: 15 | Bit rate: 10 Mbit/s | Cycle duration: 5 ms Static segment Dynamic segment Duration 3.003 ms Duration 1.987 ms Frame 16 bytes Frame 2-254 bytes Static slot count 91 Minislot count 289 Static slot duration 33 µs Minislot duration 6.875 µs Fig. 15. FlexRay communication cycles including key sharing traffic symbol window within a network with nodes that do not implement this mechanism. Two EVB9S12XF512E develop- ment boards were used as standard nodes to implement classic FlexRay communication at 10 Mbit/s. The communication cycle was configured to include all FlexRay segments (static, dynamic, symbol window and network idle time). The key sharing sequence was generated and sent from the TriBoard environment using a bit rate of 5 Mbit/s. We monitored the overall communication as well as the status returned by communication controllers from the S12XF microcontrollers for protocol error detection. There are several use cases to consider for key sharing sequence transmission. First, we evaluated the case of sending the key sharing sequence in the symbol window segment without collisions with symbols sent by standard nodes, as illustrated in Figure 15. This generates a symbol window syntax error on the receiving nodes since the key sharing sequence does not fit any of the specification defied sym- bols. This error is not used in the FlexRay automatic error confinement mechanism and does not generate message loss or communication halt. It is reported to the application layer where specific measures can be implemented. So the actual behavior of detecting such errors is application-specific. A standard node sending one of the two predefined symbols allowed in the symbol window (MTS or WUDOP) while the key sharing operation is ongoing will lead to collisions and will also generate to a symbol window syntax error being reported by the communication controller. Additionally the key sharing operation will fail due to the unsuccessful execution of the protocol verification step. In such cases nodes implementing the key exchange can retry the operation after waiting for several cycles in which standard nodes can complete their symbol transmissions. We also inv...

Backward Compatibility. All scripts written for version 2.2 should still work with version 2.3, with the following exceptions: