MétaCan
Menu
Back to cohort
Record W2112953924 · doi:10.1109/glocom.1993.318387

Frame relay interworking with asynchronous transfer mode

2002· article· en· W2112953924 on OpenAlexaff
R. Pretty, Marc-André Morin

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldEngineering
TopicIPv6, Mobility, Handover, Networks, Security
Canadian institutionsBell (Canada)
Fundersnot available
KeywordsAsynchronous Transfer ModeFrame RelayComputer scienceFrame (networking)ATM adaptation layerRelayComputer networkAsynchronous communicationService (business)Transfer (computing)Interface (matter)InteroperabilityVendorTelecommunicationsOperating system

Abstract

fetched live from OpenAlex

FR/ATM interworking is expected to play a significant role in the evolution of frame relay (FR) and asynchronous transfer mode (ATM) services. Two separate phases for the evolution of FR to ATM anticipated are: (a) frame relay carriage over ATM infrastructure (b) FR/ATM service interworking to carriers, the first phase represents economic savings in deploying frame relay services, and the second phase, a business opportunity in offering new services in support of the emerging applications. To address both phases, a common interworking architecture is being standardized in CCITT, ANSI and industry FR and ATM. The specifications agreed to so far are described in the second half of the paper. To ensure carriers can offer end-to-end FR/ATM services in a multi-vendor environment, additional specifications are still required, notably in OA&M (i.e: support for the FR local management interface) and traffic descriptor/enforcement relationship mapping. These technical issues have been identified by standards bodies and resolution is expected by the end of 1993.>

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.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.003
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.012
Threshold uncertainty score0.042

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0020.003
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0000.001
Bibliometrics0.0010.001
Science and technology studies0.0010.001
Scholarly communication0.0020.002
Open science0.0020.002
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0120.006

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.008
GPT teacher head0.178
Teacher spread0.170 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations2
Published2002
Admission routes1
Has abstractyes

Explore more

Same topicIPv6, Mobility, Handover, Networks, SecurityFrench-language works237,207