Bibliographic record
Abstract
The telecom industry has an aspiration of moving to an Internet core for all of its services. Even cellular networks, with billions of end points, are moving to an Internet core. This poses a number of challenges, especially with ever-increasing content traffic. This talk will present these challenges and some efforts at Bell Labs to deal with them. Some of these challenges are issues with Mobile IP, increased complexity of routers, and the need to deal with increasing opex expenses. Here are some solutions Bell labs is working on to enable migration of telecom networks to an Internet core. • Making Mobility a core part of the Internet: Mobile IP is a patch on the original IP design. Traffic sent to a mobile client is first sent to a home agent, which in turn tunnels it to the client in its current location. This design should be fixed to avoid triangulation. Bell Labs has designed a new protocol to deal with this issue. In our new approach, a mobile host gets an address locally (using a lightweight DHCP). Then this address, along with the host's unique ID, gets advertised on the network. • Router designs: The networking community is looking at approaches to open up routers so that third parties can add new features. Bell Labs has developed an approach called softrouter in which routers are disaggregated into simple forwarding elements and shared control elements. This approach enables the easy addition of new functions to the IP networks. • Self-management: Opex is beginning to dominate the total cost of ownership of networks, resulting in a high cost of service to the end-user. This is getting worse with the deployment of femto cells in homes and increasingly complex services. To change this trend, we need extensive automation of the deployment, configuration and optimization of networks. Scalability requires decentralized solutions where discovery and network integration tasks are performed with locally available information under local control. This is in contrast to the mostly centralized network management systems used today. Bell Labs has an extensive program in this area. This research uses various mathematical approaches such as linear programming and genetic programming.
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 imitationNot 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.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.002 | 0.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.002 | 0.001 |
| Scholarly communication | 0.003 | 0.004 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.002 | 0.004 |
| Insufficient payload (model declined to judge) | 0.148 | 0.097 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
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".