MétaCan
Menu
Back to cohort
Record W2020639336 · doi:10.1109/ccece.2008.4564576

A preliminary study of factors affecting the performance of a Playback Attack Detector

2008· article· en· W2020639336 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.
venuePublished in a venue whose home country is Canada.

Bibliographic record

VenueConference proceedings - Canadian Conference on Electrical and Computer Engineering · 2008
Typearticle
Languageen
FieldComputer Science
TopicSpeech Recognition and Synthesis
Canadian institutionsUniversity of New Brunswick
Fundersnot available
KeywordsComputer scienceUtterancePhraseProcess (computing)Channel (broadcasting)DetectorSpeaker verificationSpeech recognitionSpeaker recognitionArtificial intelligenceComputer networkTelecommunications

Abstract

fetched live from OpenAlex

A playback attack refers to the situation when an intruder plays back a recording of a true client uttering his or her pass phrase in order to bypass a speaker verification system. Playback attacks are effective and easy to implement, thus, posing a serious threat to the security of a pass-phrase protected speaker verification system. A Playback Attack Detector (PAD) has been proposed to safeguard the speaker verification systems against playback attacks. The proposed PAD capitalizes on the hypothesis that due to the random nature of speech production process, distinctions can always be found between any two utterances. Thus, if little distinction is found between two utterances, it is likely that one utterance is the playback of the other. In this paper, the proposed PAD algorithm is summarized. The design and the collection process of a database used to evaluate the effects of different factors (e.g. client, pass phrase, playback speaker, communication channel, and number of stored recordings) on the PAD's performance is detailed. Experimental procedures used for performance evaluation are described and results are presented.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.834
Threshold uncertainty score0.826

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.035
GPT teacher head0.211
Teacher spread0.175 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it