For Authors
Instructions to Authors
The Bell Labs Technical Journal welcomes submissions by members of the Lucent Technologies technical community. The Journal issues calls for papers on selected theme issues through company communication vehicles. Persons with inquiries about submissions may contact the editor at:
Frances A. GrimesEditor-in-Chief
Bell Labs Technical Journal
Lucent Technologies
Room 2F-233
600-700 Mountain Avenue
Murray Hill, New Jersey 07974
Tel: 908-582-8299
Fax: 908-582-1337
E-mail:
fagrimes@lucent.com
BELL LABS Technical Journal
Instructions to Authors
GENERAL
The Bell Labs Technical Journal publishes papers and letters on themes that have been decided upon by the Journal抯 Editorial Board. Once the Board has selected the themes for a given year, papers/letters for a particular issue are selected through a call for papers that is broadly publicized within Lucent Technologies?technical community at designated points in the year.
The Journal publishes original material; its contents are copyrighted by Lucent. It cannot publish a paper/letter that has been previously copyrighted or already submitted to others for publication, as in proceedings or transactions of organizations or other bodies. If a Journal manuscript is the same as, or approximates, a paper/letter that has been or will be copyrighted, then both its content and its graphics must be reworked.
The Journal抯 current policy requires that authors be members of Lucent抯 technical community. In special instances, however, authors from outside Lucent may co-author a paper/letter with Lucent authors. These special instances include situations in which the outside authors have a clear, formal relationship with Lucent work and Lucent authors (for example, internships and contractor or customer relationships).
SUBMISSION OF PAPERS
All papers/letters must be submitted in English. Authors who do not have a good command of English are advised to seek assistance from someone who has before submitting a manuscript.
Manuscripts must be submitted in Microsoft Word 2000 or higher.
When preparing the manuscript, authors should refer to a recent (2002 onwards) issue of the Journal and follow the detailed instructions given below.
After peer review, manuscripts that have been accepted for publication should be submitted to the Guest Editor for the issue. The Guest Editor will forward the manuscripts to:
Frances A. Grimes
Editor-in-Chief
Bell Labs Technical Journal
Lucent Technologies
Room 2F-233
600-700 Mountain Avenue
Murray Hill, New Jersey 07974
Tel: 908.582.8299 (phone)
Fax: 908.582.1337 (fax)
E-mail: fagrimes@lucent.com
MANUSCRIPT PREPARATION
Length
Papers should not normally exceed 7,000 words; letters should not exceed 1,750 words. Any manuscript that is too long will be returned to the corresponding (contact) author for redrafting within a suggested minimum wordage.
Typescript
Manuscripts should be in 10-point type with double spacing and 1-inch-wide left and right margins. Do not underline any headings. Do not use footnotes or endnotes.
Layout
The main body of the paper should be divided into unnumbered sections and each given an appropriate heading. Place main headings on a separate line in bold font at the left margin preceded by (head 1); place second-level headings on a separate line in bold font at the left margin preceded by (head 2); place each third-level heading at the beginning of the first line of the section it heads in bold font preceded by (head 3) and followed by a period.
Each level must have at least two heads (for example, head 1, head 2, head 3, head 3, head 2, head 1, head 2, head 2, head 2). Do not extend levels below the third level.
Manuscripts submitted to the Journal should conform as far as possible to the pattern prescribed below.
Title. This should explain the nature of the work in concise, specific terms. Avoid the use of 揷lever?titles that are characteristic of marketing and promotional literature.
Authors?names. Each author should have the customary forename, middle initial(s), and surname (for example, Susan B. Stevens, Vijay T. Doshi). Nicknames and other familiar or shortened forms of a proper name梖or example, Everett C. (揅huck? Mallory梐re not appropriate for the Journal. Give full contact information (location address, phone number, fax number, e-mail address) for each author. Note that authors are those who have substantially written the paper/letter. Others who have contributed in various ways should be recognized in the 揂cknowledgments?section.
Abstract. This must be informative, yet concise. In one paragraph of 150 words or fewer, the abstract should summarize the work and results, give its significance, and let the reader know why the work is important. As abstracts are often published as standalone pieces in journal abstracts or other publications, the abstract should be intelligible in itself. It should not contain numbered references.
Introduction. Include a clear description of the aims of the paper/letter (without summarizing the work itself) and a brief statement of previous relevant work with references.
Body. This contains the essential details of the work. Components of the body include: * A description of components or subjects
* Performance and test results
* A comparison with other solutions, emphasizing advantages, user needs, and features
* Other relevant data, including problems overcome, remaining problems, and possible future developments
Conclusion(s). This summarizes the paper without merely repeating the content of previous sections. A statement of future work is often merged with the conclusion.
Acknowledgment(s). Where applicable, acknowledge the contributions colleagues or associates have made to the work.
Trademarks and service marks. List the credits for trademarks and service marks used in the paper/letter that are not Lucent trademarks/service marks. (Lucent trademarks/service marks are indicated with the appropriate symbol upon each reference in the paper/letter. Trademarks and service marks of other companies/organizations are identified with an asterisk after the mark in the title, upon first reference in the abstract, upon first reference in the list of acronyms, and upon first reference in the paper/letter, with a note at the end of the paper/letter.)
References. The Journal抯 audiences are external to Lucent as well as internal, and any references used in the paper/letter should be accessible to all. Avoid making references to internal documents such as Technical Memorandums (TMs) and Internal Memorandums (IMs). These are proprietary unless they have been specially released.
The Journal uses a modified American Mathematical Society (AMS) style for references. Indicate references in the text by Arabic numbers in brackets [1] before any punctuation [2]. Each number should refer to only one reference. List the references in alphabetical order (see, for instance, the reference examples listed below) at the end of the paper. Give all the authors with their first and middle initials and their surnames. Do not use 揺t al.?as a substitute for authors?names. Abbreviate journal titles as listed in the AMS 揂bbreviations of Names of Serials,?available at http://www.ams.org/msnhtml/serials.pdf; if the journal is not included, give the title in full. Note carefully the style, order, and other particulars:
[1] D. C. Dowden, R. D. Gitlin, and R. L. Martin, 揘ext-Generation Networks,?Bell Labs Tech. J., 3:4 (1998), 3?4.
The journal article is in quotes (with initial caps for first and last words and all other words except articles, coordinating conjunctions, prepositions of four letters or fewer, and the to in infinitives) followed by a comma; the journal title is not in italics; the volume number is in regular type followed by a colon and the issue number in regular type and a comma; the year is in parentheses, followed by a comma and inclusive page numbers.
The reference list should include only those references that are actually cited within the paper/letter. Other references that are relevant to the paper/letter may be included in a separate list under a 揊urther Reading?heading.
The reference examples below give the style for a variety of reference types.
|
Example Description |
Reference Number(s) |
|
Article/paper |
[7, 8, 9, 13] |
|
Book |
[4, 17] |
|
Edited book |
[14, 19] |
|
Edited book with chapter by specific authors |
[22] |
|
Conference/proceedings |
[2, 6, 25, 26] |
|
Dissertation/thesis |
[5, 12] |
|
Internet draft |
[21] |
|
Patent |
[11] |
|
Report |
[23, 27] |
|
Request for comments |
[20] |
|
Standard/recommendation |
[1, 10, 24] |
|
URL |
[3, 15, 16, 18] |
[1] 3rd Generation Partnership Project 2, 揚hysical Layer Standard for CDMA2000 Spread Spectrum Systems桼elease A,?3GPP2 C.S0002-A, Feb. 8, 2002, http://www.3gpp2.org/Public_html/specs/C.S0002-A_v6.0.pdf.
[2] Y. Amir, D. Dolev, S. Kramer, and D. Malki, 揗embership Algorithms for Multicast Communication Groups,?Proc. 13th Internat. Conf. on Distributed Computing Systems (Pittsburgh, PA, 1993), pp. 551?60.
[3] R. C. Atwood, 揤itria Business Ware, Enabling Technologies Strategic Business Service,?May 1999, http://www/vitria.com/products/抴hitepapers/seyboldwp.html.
[4] G. Booch, Object-Oriented Analysis and Design, 2nd ed., Benjamin Cummings, Redwood City, CA, 1994, p. 263.
[5] D. M. Bozga, Verification Symbolique pour les Protocols de Communication, Ph.D. Thesis (in French), University of Grenoble, 1999.
[6] O. Buyukkokten, H. Garcia-Molina, and A. Paepcke, 揊ocused Web Searching with PDAs,?Proc. 9th Internat.. WWW Conference, (Amsterdam, The Netherlands, 2001); published in Computer Networks, 33, 213?30.
[7] D. C. Dowden, R. D. Gitlin, and R. L. Martin, 揘ext-Generation Networks,?Bell Labs Tech. J., 3:4 (1998), 3?4.
[8] G. Goldszmidt and Y. Yemini, 揇elegated Agents for Network Management,?IEEE Commun. Mag., 36:3 (1998) 66?0.
[9] G. J. Holzmann and A. Purl, 揂 Minimized Automaton Representation of Reachable States,?Internat. J. Software Tools for Technol. Transfer, 2: 3, Springer-Verlag (1999), 270?78.
[10] International Telecommunication Union, Telecommunication Standardization Sector, 揚acket-Based Multimedia Communication Systems,?ITU-T Rec. H.323, Feb. 1998, http://www.itu.int.
[11] D. Kahng, 揈lectric Field Controlled Semiconductor Device,?U. S. Patent 3,102,230 (1963).
[12] V. K. N. Lau, Variable-Rate Adaptive Channel Coding for Mobile Cellular Systems, Ph.D. Dissertation, University of Cambridge, 1997.
[13] V. K. N. Lau, 揤ariable-Rate Adaptive Channel Coding for CDMA桼everse Link?Bell Labs Tech. J. 5:4 (2000), 138?56.
[14] L. K. Lustig (ed.), Impact: A Compilation of Bell System Innovations in Science and Engineering, Bell Telephone Laboratories, Murray Hill, NJ, 1981.
[15] Media Gateway Control (Megaco) Working Group, 揗egaco Protocol,?IETF draft-ietf-megaco-protocol-08.txt, Apr. 2000, http://www.ietf.org/ids.by.wg/megaco.html.
[16] Microsoft Corporation, 揇COM Technical Overview,?Nov. 1996, http://msdn.microsoft.com/library/backgrnd/html/msdn_dcomtec.htm.
[17] J. D. Musa, A. Iannino, and K. Okumoto, Software Reliability: Measurement, Prediction, and Application, McGraw-Hill, New York, 1990.
[18] Object Management Group, http://www.omg.org.
[19] R. Orfali, Client/Server Programming with JAVA?and CORBA? 2nd ed. (D. Harkey, ed.), John Wiley, New York, 1998.
[20] C. Perkins (ed.), 揑P Mobility Support,?IETF RFC 3220, Jan. 2002, http://www.ietf.org/rfc/rfc3220.txt.
[21] C. Perkins and P. Calhoun, 揂AA Registration Keys for Mobile IP,?IETF Internet Draft, Feb. 2002, http://www.ietf.org/intetnet-drafts/draft-ietf-mobileip-aaa-key-09-txt.
[22] M. R. Phillips and T. E. Darcie, 揕ightwave Analog Video Transmission,?Optical Fiber Telecommunications, Vol. IIIA (I. P. Kaminow and T. L. Koch, eds.), Academic Press, San Diego, CA, 1997, pp. 523?59.
[23] W. Su and R. Giusto, Erratic Signals: Worldwide Handset Market Forecast and Analysis, Internat. Data Corp., Doc. No. 25417, 2001, pp. 12?4.
[24] Telecommunications Industry Association, 揅DMA 2000 Series,?TIA/EIA-IS-2000 Series, Electronic Industries Alliance, 1999.
[25] D. Wagner, B. Schneier, and J. Kelsey, 揅ryptanalysis of Cellular Message Encryption Algorithms,?Advances in Cryptology, CRYPTO ?7 Proc., Springer-Verlag, New York 1997.
[26] R. S. Windeler, J. L. Wagener, and D. J. DiGiovanni, 揝ilica-Air Microstructured Fibers: Properties and Applications,?Optical Fiber Commun. Conf. Tech. Digest (San Diego, CA, 1999), paper FGI.
[27] T. S. Winsome (ed.), Y2K Hit Results, GPO, Washington, DC, 2001.
Do not use links for URLs.
Abbreviations, acronyms, and terms. Alphabetically list the abbreviations/acronyms used in the text and follow each with its definition. In most instances, terms are defined within the text; in some cases, however, including them in the list of abbreviations and acronyms clarifies them for the reader. Note that the abbreviations/acronyms should be defined upon first use in the abstract and upon first use in the text. The abbreviation/acronym follows the definition, as in code division multiple access (CDMA). Avoid overloading the paper with abbreviations/acronyms. If an abbreviation/acronym is used only once or twice in the paper/letter, it can usually be omitted. Abbreviations/acronyms that are used only in figure or table legends are not included in the general list of abbreviations and acronyms.
Panels. These are used for information that parallels or amplifies material discussed in the body of the paper (see recent issues of the Journal for examples). Panels (used sparingly) should be placed in a separate file. Number panels consecutively using Arabic numbers. The 揂bbreviations, Acronyms, and Terms?list is designated as Panel 1 in each paper/letter. Do not use field codes or links with panels.
Figures and tables. Although each figure and table should be called out in the text, the figures and tables themselves should not be embedded in the text. Place figures and tables, along with their captions, in separate files. Submit figures in editable EPS (Adobe illustrator), PowerPoint, Word (native), or Excel format. (Please do not rasterize images into TIF or JPG files.) Number figures consecutively using Arabic numbers. Number tables consecutively using Roman numerals. Do not use field codes or links with figures or tables.
As figures and tables are often requested for separate use once the paper is published, be sure to include in each figure or table a legend to clarify acronyms and graphical designations and, if appropriate, to indicate trademarks. In writing a paper/letter, remember that it is not designed to be a viewgraph presentation. A paper of 7,000 words will support on average six to eight figures. Letters are limited to three figures.
Biographical information and photographs. Biographical information and a photo should be included for each author. Biographical information should include:
* Name (as the author wishes it to appear in the paper/letter)
* Current job title (for example, member of technical staff, department head, XYZ Department)
* Organization (for example, group/department, business unit)
* Location
* Current job responsibilities (briefly stated)
* Professional interests
* Professional honors/recognitions
* Degrees and field of study for each degree along with college/university (and location) at which each degree was received
The photo should be a head shot, preferably black and white (passport size, although the compositor will work with color and other sizes). For best results, the photo should have a plain background. Both electronic files (JPG, TIF, EPS) and hard copy are acceptable. A minimum resolution of 300 dpi is required for all photos.
PUBLICATION CLEARANCE
Current Lucent employees and also former Lucent employees who completed work that is the subject of a Journal paper/letter while employed at Lucent are required to have their work cleared for publication in the Journal. This is accomplished through a 揜equest for Public Release of Information?form (Form E-7227). The form requires the signature of each author抯 E-level manager, or his/her delegate. If appropriate, authors should also indicate on the form the name of the patent attorney who will review the paper/letter. Only one attorney need be indicated, even if the paper/letter has authors from different organizations.
Other authors will be required to execute a 揅opyright Transfer Agreement.?/P>
The Editor-in-Chief will request the 揜equest for Public Release of Information?form or the 揅opyright Transfer Agreement?from authors. Do not send in either form until it is requested.
PROOFS
Proofs will be sent to the lead author. These must be proofread carefully, corrected, and returned to the publisher within 48 hours of receipt. Authors?corrections at this point should be minimal. The publisher reserves the right to charge authors for excessive changes to the manuscript.
JOURNAL COPY/OFFPRINTS
Each author will be sent a copy of the Journal and 25 offprints of his/her paper/letter free of charge. Additional offprints can be ordered at current printing prices.
刊名字顺( Alphabetical List of Journals):
返回页首 