The BICONF Primitive Sample Clauses

The BICONF Primitive. The BICONF primitive was first introduced in [2] (it is a combination of two prim- itives named BINARY and CONFIRM, see [7] for more details). It was used as a primitive in [7, 76, 73, 77]. It deals with the case when there are only a small number of errors or no errors left in Bob’s string (▇▇▇▇▇ and ▇▇▇ ▇▇▇ not know that they are in this case). ▇▇▇▇▇ and ▇▇▇ begin by choosing the same randomly generated subset of bits from their strings. Then ▇▇▇▇▇ tells Bob the parity of her subset, and Bob checks whether his subset has the same parity. The primitive ends in case of identical parity, otherwise a binary search is performed to locate an error. If ▇▇▇▇▇’s string is different from Bob’s, the BICONF primitive will detect this with probability 1/2; if the two strings are identical, the primitive says so with probability 1. Therefore, if the primitive is executed sufficiently many times, say l times, with the same parities for ▇▇▇▇▇ and ▇▇▇, ▇▇▇▇▇ and ▇▇▇ will be rightly convinced that their strings are identical with probability at least 1 − 2—l.
The BICONF Primitive. In our protocol, after Pass t + 1, the average bit error rate p(t+1) (according to simulation) is so small that BICONF passes are enough to eliminate the remaining errors. The difference between BICONF pass and BICONF primitives is that if an error is found in some BICONF pass, other errors may be located by looking back to the parity check vectors of previous passes.

Related to The BICONF Primitive

  • The Supplier must 12.1.1 comply with the Buyer’s written instructions and this Call-Off Contract when Processing Buyer Personal Data 12.1.2 only Process the Buyer Personal Data as necessary for the provision of the G-Cloud Services or as required by Law or any Regulatory Body 12.1.3 take reasonable steps to ensure that any Supplier Staff who have access to Buyer Personal Data act in compliance with Supplier's security processes

  • The Web Services E-Verify Employer Agent agrees to, consistent with applicable laws, regulations, and policies, commit sufficient personnel and resources to meet the requirements of this MOU.

  • DISCLOSURE OF TBS ACCESS CODE TO THIRD PARTY (a) The Account Holder must exercise all care to ensure that the TBS Access Code is not disclosed to any person and shall take all steps to prevent forgery or fraud in connection with the use of his TBS Access Code and/or the operation of the TBS. If the TBS Access Code is disclosed to any person, the Account Holder must forthwith give the Bank written notice thereof, thereupon the Account Holder shall immediately cease to use the TBS Access Code. (b) Unless and until the Bank receives such written notice of disclosure, the Account Holder shall be fully liable and be bound by all transactions effected by the use of such TBS, with or without his consent or knowledge.

  • The Supplier shall (a) Process the Personal Data only in accordance with instructions from the Authority to perform its obligations under this Framework Agreement; (b) ensure that at all times it has in place appropriate technical and organisational measures to guard against unauthorised or unlawful Processing of the Personal Data and/or accidental loss, destruction, or damage to the Personal Data; (c) not disclose or transfer the Personal Data to any third party or Supplier Personnel unless necessary for the provision of the Goods and/or Services and, for any disclosure or transfer of Personal Data to any third party, obtain the prior written consent of the Authority (save where such disclosure or transfer is specifically authorised under this Framework Agreement); (d) take reasonable steps to ensure the reliability and integrity of any Supplier Personnel who have access to the Personal Data and ensure that the Supplier Personnel: (i) are aware of and comply with the Supplier’s duties under this Clause 24.5.2 and Clause 24.2 (Confidentiality); (ii) are informed of the confidential nature of the Personal Data and do not publish, disclose or divulge any of the Personal Data to any third party unless directed in writing to do so by the Authority or as otherwise permitted by this Framework Agreement; and (iii) have undergone adequate training in the use, care, protection and handling of personal data (as defined in the DPA); (e) notify the Authority within five (5) Working Days if it receives: (i) from a Data Subject (or third party on their behalf) a Data Subject Access Request (or purported Data Subject Access Request), a request to rectify, block or erase any Personal Data or any other request, complaint or communication relating to the Authority's obligations under the DPA; (ii) any communication from the Information Commissioner or any other regulatory authority in connection with Personal Data; or (iii) a request from any third party for disclosure of Personal Data where compliance with such request is required or purported to be required by Law; (f) provide the Authority with full cooperation and assistance (within the timescales reasonably required by the Authority) in relation to any complaint, communication or request made (as referred to at Clause 24.5.2(e), including by promptly providing: (i) the Authority with full details and copies of the complaint, communication or request; (ii) where applicable, such assistance as is reasonably requested by the Authority to enable the Authority to comply with the Data Subject Access Request within the relevant timescales set out in the DPA; and (iii) the Authority, on request by the Authority, with any Personal Data it holds in relation to a Data Subject; and (g) if requested by the Authority, provide a written description of the measures that the Supplier has taken and technical and organisational security measures in place, for the purpose of compliance with its obligations pursuant to this Clause 24.5.2 and provide to the Authority copies of all documentation relevant to such compliance including, protocols, procedures, guidance, training and manuals.

  • Innovative Scheduling Schedules which are inconsistent with the Collective Agreement provisions may be developed in order to improve quality of working life, support continuity of resident care, ensure adequate staffing resources, and support cost-efficiency. The parties agree that such innovative schedules may be determined locally by the Home and the Union subject to the following principles: (a) Such schedules shall be established by mutual agreement of the Home and the Union; (b) These schedules may pertain to full-time and/or part-time employees; (c) The introduction of such schedules and trial periods, if any, shall be determined by the local parties. Such schedules may be discontinued by either party with notice as determined through local negotiations; (d) Upon written agreement of the Home and the Union, the parties may agree to amend collective agreement provisions to accommodate any innovative unit schedules; (e) It is understood and agreed that these arrangements are based on individual circumstances and each agreement is made on a without prejudice or precedent basis. (f) It is understood and agreed that these arrangements can be utilized for temporary job postings for seasonal coverage (e.g. weekend workers, etc.).