Revisiting G & S’s Protocol Sample Clauses

Revisiting G & S’s Protocol. This section depicts the review of G & S’s authentication protocol for EI-based vehicle to grid communication. In this protocol, the three entities namely, user Ui having a mobile gadget with equipped internet, a charging station CSj, and a electricity service provider ESP, interact to validate the Ui’s authenticity so that the latter could get the recharging services from CSj. The G & S’s protocol [12] contains two phases 1) user registration 2) mutual authentication.
AutoNDA by SimpleDocs

Related to Revisiting G & S’s Protocol

  • Construction Change Directives 1.1.1, 3.4.2, 3.11, 3.12.8, 4.2.8, 7.1.1, 7.1.2, 7.1.3, 7.3, 9.3.1.1 Construction Schedules, Contractor’s 3.10, 3.11, 3.12.1, 3.12.2, 6.1.3, 15.1.6.2

  • Data Universal Number System (DUNS) number Requirement Grantee will provide their valid DUNS number contemporaneous with execution of this Agreement.

  • Review Protocol A narrative description of how the Claims Review was conducted and what was evaluated.

  • Protocol The attached Protocol shall be an integral part of this Agreement.

  • Signaling protocol The Parties will interconnect their networks using SS7 signaling where Technically Feasible and available as defined in GR 905 Telcordia Standards including ISDN User Part (ISUP) for trunk signaling and TCAP for CCS-based features in the Interconnection of their networks. All Network Operations Forum (NOF) adopted standards shall be adhered to. Where available, CenturyLink signaling services to link its Signaling Transfer Points (STPs) for CLEC switches which connect to CenturyLink’s STPs via “A” links or for CLEC’s STPs to connect to CenturyLink’s STPs via “D” links which are dedicated to the transport of signaling for local Interconnection, may be ordered from the CenturyLink Tariff.

  • Updates and Upgrades Contractor grants to the Department a non-exclusive, non-transferable license to use upgrades and updates provided by Contractor during the term of the Contract. Such upgrades and updates are subject to the terms of the Contract. The Department shall download, distribute, and install all updates as released by Contractor during the length of the Contract, and Contractor strongly suggests that the Department also downloads, distributes, and installs all upgrades as released by Contractor during the length of the Contract. Contractor shall use commercially reasonable efforts to provide the Department with work-around solutions or patches to reported software problems that may affect the Department’s use of the software during the length of the Contract.

  • Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • Payment Scheduling The earliest possible Scheduled Payment Date for each Xxxxxx will be designated within the portion of the Site through which the Service is offered when you are scheduling the payment. Therefore, the Service will not permit you to select a Scheduled Payment Date less than the earliest possible Scheduled Payment Date designated for each Xxxxxx. When scheduling payments you must select a Scheduled Payment Date that is no later than the actual Due Date reflected on your Xxxxxx statement unless the Due Date falls on a non-Business Day. If the actual Due Date falls on a non-Business Day, you must select a Scheduled Payment Date that is at least one (1) Business Day before the actual Due Date. Scheduled Payment Dates must be prior to any late date or grace period. Depending on the method of payment, your Eligible Transaction Account may be debited prior to the Scheduled Payment Date. For example, if the selected method of payment is a draft, the draft arrives earlier than the Scheduled Payment Date due to expedited delivery by the postal service, and the Xxxxxx immediately deposits the draft, your Eligible Transaction Account may be debited earlier than the Scheduled Payment Date.

  • Change Control Procedure 34.1 In the event that either Party desires any change the terms of this Agreement or any Contract which may materially impact on the timings, scope, Specification or Charges of the Goods or Services, or the scope of either parties’ obligations under this Agreement or the relevant Contract, or which the relevant Party otherwise reasonably determines warrants the use of this change control procedure, the following procedures will apply: (a) the Party requesting the change will deliver a “Change Request” (in the form (or substantially in the same form) contained in Schedule 5 to this Agreement) which describes: (i) the nature of the change; (ii) the reason for the change; (iii) the effect that the requested change will have on the scope or Specification for the Goods or Services; and (iv) any change to the Charges and the Term. (b) Upon receipt of a Change Request, the receiving Party’s authorised representative will contact his/ her counterpart within 5 working days to discuss and agree the Change Request. The parties will negotiate the proposed changes to the Agreement and/or affected Contract in good faith and agree a timeline in which to finalise the Change Notice. (c) Neither party is obliged to agree to a Change Request, but if the parties do agree to implement such a Change Request, the appropriate authorised representatives of both parties will sign the Change Request which will be effective from the date set out in the Change Request. (d) If there is any conflict between the terms and conditions set out in the Agreement or any Contract and the Change Request, then the terms and conditions set out in the most recent fully executed Change Request will apply. (e) The Supplier shall neither be relieved of its obligations to supply the Goods and/or Services in accordance with the terms and conditions of this Agreement or any Contract, nor be entitled to an increase in the Charges as the result of: (i) a General Change in Law; or (ii) a Specific Change in Law where the effect of that Specific Change in Law on the Goods and/or Services is reasonably foreseeable at the Commencement Date of this Agreement, or, where the Change Request relates to a Contract, the applicable Contract Commencement Date. 34.2 The Parties agree that any variations to the Agreement or any Contract to reflect non- material changes (including for example a change to the name/contact details of a Party’s representative) may be agreed in writing and shall not be required to be made in accordance with the procedure in this clause 34, provided always that UKRI shall, in their absolute discretion, decide whether a proposed change is non-material for these purposes.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!