DOCSLIB.ORG

Μitron 4.0 Specification (Ver. 4.03.00) TEF024-S001-04.03.00/En July 2010 Copyright © 2010 by T-Engine Forum

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

μITRON 4.0 Specification Ver. 4.03.00 TEF024-S001-04.03.00/en July 2010 μITRON 4.0 Specification (Ver. 4.03.00) TEF024-S001-04.03.00/en July 2010 Copyright © 2010 by T-Engine Forum. This “μITRON 4.0 Specification (Ver. 4.03.00)” was originally released by TRON ASSOCIATION which has been integrated into T-Engine Forum since January 2010. The same specification now has been released by T-Engine Forum as its own specification without modification of the content after going through the IPR procedures. T-Engine Forum owns the copyright of this specification. Permission of T-Engine Forum is necessary for copying, republishing, posting on servers, or redistribution to lists of the contents of this specification. The contents written in this specification may be changed without a prior notice for improvement or other reasons in the future. About this specification, please refer to follows; Publisher T-Engine Forum The 28th Kowa Building 2-20-1 Nishi-gotanda Shinagawa-Ward Tokyo 141-0031 Japan TEL：+81-3-5437-0572 FAX：+81-3-5437-2399 E-mail：[email protected] TEF024-S001-04.03.00/en µITRON4.0 Specification Ver. 4.03.00 Supervised by Ken Sakamura Edited and Published by TRON ASSOCIATION µITRON4.0 Specification (Ver. 4.03.00) The copyright of this specification document belongs to TRON Association. TRON Association grants the permission to copy the whole or a part of this specification document and to redistribute it intact without charge or at cost. However, when a part of this specification document is redistributed, it must clearly state (1) that it is a part of the µITRON4.0 Specification document, (2) which part was taken, and (3) the method to obtain the whole specification document. See Section 6.1 for more information on the conditions for using this specification and this specification document. Any questions regarding this specification and this specification document should be directed to the following: ITRON Specification Study Group, TRON Association Katsuta Building 5F 3-39, Mita 1-chome, Minato-ku, Tokyo 108-0073, JAPAN TEL: +81-3-3454-3191 FAX: +81-3-3454-3224 § TRON is the abbreviation of "The Real-time Operating system Nucleus." § ITRON is the abbreviation of "Industrial TRON." § µITRON is the abbreviation of "Micro Industrial TRON." § BTRON is the abbreviation of "Business TRON." § CTRON is the abbreviation of "Central and Communication TRON." § TRON, ITRON, µITRON, BTRON, CTRON, and T-Kernel do not refer to any specific product or products. Copyright(C)2007 by TRON ASSOCIATION µITRON4.0 Specification Ver. 4.03.00 A Word from the Project Leader Twenty-two years have passed since the ITRON Sub-Project was established as a part of the TRON Project: a real-time operating system specification for embedded systems. In this period, since the T-Engine Project commenced in 2001, activities for the standardization of a leading-edge real-time OS within the TRON Project have moved on to the T-Kernel Series as the next-generation ITRON Specification. However, that the conventional µITRON-specification OS remains the most used OS for embedded systems in Japan is an undeniable fact. This is because the technological advantages of the ITRON Specifications such as real- time response, compactness to maximize the efficiency of system resources, flexible adaptability in specification, and open architecture policy are strongly supported. While this is very pleasing to ITRON's exponents, migration to the T-Kernel is believed to be crucial for supporting the increasingly advanced and complex functions of large-scale embedded systems. From here, we will seek to expand the "TRON Community" formed by the developers and users of both ITRON and the T-Kernel while promoting migration to the T-Kernel. The revisions leading to this version, 4.03, were carried out for this purpose. One objective was to make ease the comprehensibility of parts that were difficult to understand without making large changes to the specification itself. Another objective was to create a mechanism that facilitates migration from µTRON to the T-Kernel. Activities towards the former objective included accommodating users by listing the descriptions on implementation-defined items scattered throughout the specification. A Basic Profile has been introduced specifically for the latter objective. The Basic Profile specifies the service calls that have the same functionality in µITRON3.0, µITRON4.0, and the T-Kernel. Middleware or applications that operate within this profile can be easier to port from µTRON to the T-Kernel. In these ways, the µITRON4.0 Specification Ver. 4.03 is expected to achieve the apparently contradictory goals of further improving the services for current users of µITRON while at the same time providing a good bridge to the T-Kernel. December, 2006 Ken Sakamura Project Leader, TRON Project i µITRON4.0 Specification Ver. 4.03.00 Organization of the Specification Document This document is the specification of the µITRON4.0 (or the µITRON4.0 Real-Time Kernel) C-Language API Specification. The version number of specification is printed on the cover and the top-right of each page. The organization of this document is as follows. In Chapter 1, a summary of the TRON Project and the ITRON Sub-Project and design policies of the ITRON Specifications are introduced. The position of the µITRON4.0 Specification is also described. This chapter describes the background information of the µITRON4.0 Specification and is not the main body of the µITRON4.0 Specification. In Chapter 2, the common rule of the µITRON4.0 Specification and the software components that are standardized to be consistent with the µITRON4.0 Specification is described. In Chapter 3, the various concepts and the common definitions for various features of the µITRON4.0 Specification are shown. In Chapter 4, each feature of the µITRON4.0 Specification is described. In Chapter 5, the additional specifications are described. In Chapter 6, the reference information, such as the maintenance of specification and reference documents, is described. In Chapter 7, the lists and other information that may be helpful in reading this specification is shown. These lists are the contents of Chapter 2 to Chapter 5, as seen from a different point of view. Chapter 6 and Chapter 7 are not the main body of the µITRON4.0 Specification. ii µITRON4.0 Specification Ver. 4.03.00 Description Format of the Specification Document The following description format is used in this specification document. [Standard Profile] The specifications of the Standard Profile of the µITRON4.0 Specification are described here. The scope of functionalities that the Standard Profile requires to support, the rule that is not applied to the Standard Profile but is included in the functional descriptions of the services calls and static APIs which the Standard Profile requires to support, and the rule that is not described in the µITRON4.0 Specification but applied to the Standard Profile are described here. [Supplemental Information] Supplemental explanations of items difficult to understand are described here to avoid misunderstanding. This is not the main body of the µITRON4.0 Specification. [Differences from the µITRON3.0 Specification] The differences of the µITRON4.0 Specification from the µITRON3.0 Specification and their reasons are described here. The major differences and modifications from the µITRON3.0 Specification are mainly described, but not the additions or clarification made in the µITRON4.0 Specification. This is not the main body of the µITRON4.0 Specification. [Rationale] The reasons for the specification decision are described here, when further explanations are necessary. This is not the main body of the µITRON4.0 Specification. The functional descriptions of service calls and static APIs in Chapter 4 use the format described below. The functional description of each service call or static API is started with the following header. API Name API Description Profile "API Name" is a service call or a static API name. "API description" is a simple statement about the functionality of this service call or static API. If [S] is placed at the "Profile" field, the Standard Profile requires support for the service call or static API. [B] stands for the Basic Profile. iii µITRON4.0 Specification Ver. 4.03.00 [Static API] This shows the description format of a static API in the system configuration file. [C Language API] This shows the invocation format of a service call in the C Language. [Parameter] This lists all of the parameters for this service call or static API. It also includes a simple description, the data type, and the name of each parameter. [Return Parameter] This lists all of the return parameters for this service call. It also includes a simple description, the data type, and the name of each return parameter. [Error Code] This lists all of the main error codes that this service call returns. It also includes a simple description of the cause of each error code. However, the main error codes that many service calls may return due to the same cause are not described for each service call (see Section 2.1.6). [Functional Description] This describes the functionality of this service call or static API. Italic characters within the names of service calls and constants represent other characters. For example, cre_yyy (yyy are italic characters) can be cre_tsk, cre_sem, cre_flg, and so on. For some parameters, such as object attributes or service call operational modes where specific values are chosen, the following format is used: [x] x may or may not be specified x | y Bitwise OR expression x || y Logical OR expression For example, ((TA_HLNG || TA_ASM) | [TA_ACT]) can take one of the following four values. TA_HLNG TA_ASM (TA_HLNG | TA_ACT) (TA_ASM | TA_ACT) iv µITRON4.0 Specification Ver.
Recommended publications
  • Sistemi Operativi Real-Time Marco Cesati Lezione R13 Sistemi Operativi Real-Time – II Schema Della Lezione

    Sistemi Operativi Real-Time Marco Cesati Lezione R13 Sistemi Operativi Real-Time – II Schema Della Lezione

    Sistemi operativi real-time Marco Cesati Lezione R13 Sistemi operativi real-time – II Schema della lezione Caratteristiche comuni VxWorks LynxOS Sistemi embedded e real-time QNX eCos Windows Linux come RTOS 15 gennaio 2013 Marco Cesati Dipartimento di Ingegneria Civile e Ingegneria Informatica Università degli Studi di Roma Tor Vergata SERT’13 R13.1 Sistemi operativi Di cosa parliamo in questa lezione? real-time Marco Cesati In questa lezione descriviamo brevemente alcuni dei più diffusi sistemi operativi real-time Schema della lezione Caratteristiche comuni VxWorks LynxOS 1 Caratteristiche comuni degli RTOS QNX 2 VxWorks eCos 3 LynxOS Windows Linux come RTOS 4 QNX Neutrino 5 eCos 6 Windows Embedded CE 7 Linux come RTOS SERT’13 R13.2 Sistemi operativi Caratteristiche comuni dei principali RTOS real-time Marco Cesati Corrispondenza agli standard: generalmente le API sono proprietarie, ma gli RTOS offrono anche compatibilità (compliancy) o conformità (conformancy) allo standard Real-Time POSIX Modularità e Scalabilità: il kernel ha una dimensione Schema della lezione Caratteristiche comuni (footprint) ridotta e le sue funzionalità sono configurabili VxWorks Dimensione del codice: spesso basati su microkernel LynxOS QNX Velocità e Efficienza: basso overhead per cambi di eCos contesto, latenza delle interruzioni e primitive di Windows sincronizzazione Linux come RTOS Porzioni di codice non interrompibile: generalmente molto corte e di durata predicibile Gestione delle interruzioni “separata”: interrupt handler corto e predicibile, ISR lunga
  • V850 Series Development Environment Pamphlet

    V850 Series Development Environment Pamphlet

    To our customers, Old Company Name in Catalogs and Other Documents On April 1st, 2010, NEC Electronics Corporation merged with Renesas Technology Corporation, and Renesas Electronics Corporation took over all the business of both companies. Therefore, although the old company name remains in this document, it is a valid Renesas Electronics document. We appreciate your understanding. Renesas Electronics website: http://www.renesas.com April 1st, 2010 Renesas Electronics Corporation Issued by: Renesas Electronics Corporation (http://www.renesas.com) Send any inquiries to http://www.renesas.com/inquiry. Notice 1. All information included in this document is current as of the date this document is issued. Such information, however, is subject to change without any prior notice. Before purchasing or using any Renesas Electronics products listed herein, please confirm the latest product information with a Renesas Electronics sales office. Also, please pay regular and careful attention to additional and different information to be disclosed by Renesas Electronics such as that disclosed through our website. 2. Renesas Electronics does not assume any liability for infringement of patents, copyrights, or other intellectual property rights of third parties by or arising from the use of Renesas Electronics products or technical information described in this document. No license, express, implied or otherwise, is granted hereby under any patents, copyrights or other intellectual property rights of Renesas Electronics or others. 3. You should not alter, modify, copy, or otherwise misappropriate any Renesas Electronics product, whether in whole or in part. 4. Descriptions of circuits, software and other related information in this document are provided only to illustrate the operation of semiconductor products and application examples.
  • Compact, Low-Cost, but Real-Time Distributed Computing for Computer Augmented Environments

    Compact, Low-Cost, but Real-Time Distributed Computing for Computer Augmented Environments

    Compact, Low-Cost, but Real-Time Distributed Computing for Computer Augmented Environments Hiroaki Takada and Ken Sakamura Department of Information Science, Faculty of Science, University of Tokyo 7-3-1, Hongo, Bunkyo-ku, Tokyo 113, Japan Abstract We have been conducting a research and development project, called the TRON Project, for realizingthe computer augmented environments. The final goal of the project is to realize highly functionally distributed systems (HFDS) in which every kind of objects around our daily life are augmented with embedded computers, be connected with networks, and cooperate each other to provide better living environments for human beings. One of the key technologies towards HFDS is the realization methods of compact and low-cost distributed computing systems with dependability and real-time property. In this paper, the overview of the TRON Project are introduced and various research and development activities for realizing HFDS, especially the subprojects on a standard real- time kernel specification for small-scale embedded systems Figure 1: Computerized Living Environment called ITRON and on a low-cost real-time LAN called "ITRON bus, are described. We also describe the future A typical example of “computing everywhere” envi- directions of the project centered on the TRON-concept ronment is the TRON-concept Intelligent House, which Computer Augmented Building, which is a pilot realization was built experimentally in 1989 (Figure 2). The purpose of HFDS and being planned to be built. was to create a testbed for future intensively computerized living spaces. The house with 330 m2 of floor space was 1 Introduction equipped with around 1000 computers, sensors, and actu- ators, which were loosely connected to form a distributed Recent advances in microprocessor technologies have computing system.
  • Japanese Semiconductor Industry Conference

    Japanese Semiconductor Industry Conference

    Japanese Semiconductor Industry Conference April 11-12, 1988 Hotel Century Hyatt Tokyo, J^an Dataoyest nn aaxraiaiwof JED IneOun&BradstRetCorpofation 1290 Ridder Plark Drive San Jose, CaUfonm 95131-2398 (408) 437-8000 Telex: 171973 Fax: (408) 437-0292 Sales/Service Offices: UNITED KINGDOM FRANCE EASTERN U.S. Dataquest UK Limited Damquest SARL Dataquest Boston 13th Floor, Ceittiepoint Tour Gallieni 2 1740 Massachusetts Ave. 103 New Oxford Street 36, avenue GaUieni Boxborough, MA 01719 London WCIA IDD 93175 Bagnolet Cedex (617) 264-4373 England France Tel«: 171973 01-379-6257 (1)48 97 31 00 Fax: (617) 263-0696 Tfelex: 266195 Tfelex: 233 263 Fax: 01-240-3653 Fax: (1)48 97 34 00 GERMANY JAPAN KOREA Dataquest GmbH Dataquest Js^an, Ltd. Dataquest Korea Rosenkavalierplatz 17 Tkiyo Ginza Building/2nd Floor 63-1 Chungjung-ro, 3Ka D-8000 Munich 81 7-14-16 Ginza, Chuo-ku Seodaemun-ku ^^fest Germany Tbkyo 104 Japan Seoul, Korea (089)91 10 64 (03)546-3191 (02)392-7273-5 Tfelex: 5218070 Tfelex: 32768 Telex: 27926 Fax: (089)91 21 89 Fax: (03)546-3198 Fax: (02)745-3199 The content of this report represents our interpretation aiKl analysis of information generally avail­ able to the public or released by responsible indivi(bials in the subject companies, but is not guaranteed as to accuracy or comfdeteness. It does not contain material provided to us in confidence t^ our clients. This information is not furnished in connection with a sale or offer to sell securities, or in coimec- tion with the solicitation of an offer to buy securities.
  • COMPUTER ABBREVIATIONS [Copyright: TECHNOART Co

    COMPUTER ABBREVIATIONS [Copyright: TECHNOART Co

    COMPUTER ABBREVIATIONS [Copyright: TECHNOART Co. Ltd.] References: Magazines: Nikkei Electronics, Nikkei Microdevices, Nikkei Mechanical, etc. News papers: Nikkei Industrial Journal, Dempa Journal White papers: IEEE, IEC, SMPTE, Internet Websites, format specifications, etc. Others: encyclopedias, instruction booklets, catalogues, product spec., etc. ABBREVIATION DERIVATION OF ABBREVIATION 3D DDI 3 Dimensional Device Driver Interface 4GL 4th generation language A3D Aural 3D ABI application binary interface ABS air bearing surface ACSM Application Control State Machine ADB Apple Desktop Bus ADE automatic design engineering AIF application integration feature AOAC always on/always connected APIC Advanced Programmable Interrupt Controller APM Advanced Power Management APNIC Asia Pacific Network Information Center ARC Advanced RISC Computing ATMS Automated Traffic Management Systems AT-UD Unimodem Diagnostics Command AWT Abstract Window Toolkit BAR base address register BBS bulletin board system bcc blind carbon copy BCL bias compensation layer BIPS billion instructions per second BIS boot integrity services BLOB Binary Large Object BML Broadcast Markup Language BNF Backup Naur Form BPR business process reengineering BSDL Boundary Scan Description Language BTL backplane transceiver logic BTRON Business TRON C&C computer and communication CBQ class-based queuing CDA Compound Document Architecture CDB Command Description Block CDC Connected Device Configuration CDDI copper distributed data interface CDF Channel Definition Format CDFF Common
  • Ken Sakamura

    Ken Sakamura

    2014 TRON Symposium. 30th Anniversary TRON Project 30th Anniversary and Its Future Outlook Embedded systems technology to support the utilization of the IoT big data and future plan for T-Engine Ken Sakamura Professor, Graduate School of Interdisciplinary Studies, The University of Tokyo Director of YRP Ubiquitous Networking Laboratory Chair of T-Engine Forum / uID Center 2014 TRON Symposium. 30th Anniversary ① TRON Project The Real-time Operating system Nucleus The 30th anniversary in 2014 One of the longest lasting projects related to Japanese computing Copyright © 2014 by Ken SAKAMURA 2 2014 TRON Symposium. 30th Anniversary What is TRON? RTOS for system control, and has different basic architecture from Windows and Linux RTOS: Real-Time Operating System Copyright © 2014 by Ken SAKAMURA 3 2014 TRON Symposium. 30th Anniversary TRON RTOS Is Embedded in Many Things “HAYABUSA” (MUSES-C), an asteroid explorer “IKAROS, ” Interplanetary Kite-craft Accelerated by Radiation Of the Sun 4 2014 TRON Symposium. 30th Anniversary TRON Project’s Root Is in Embedded Systems 5 2014 TRON Symposium. 30th Anniversary ② 30 Years of TRON Copyright © 2014 by Ken SAKAMURA 6 2014 TRON Symposium. 30th Anniversary Started in 1984 Copyright © 2014 by Ken SAKAMURA 7 2014 TRON Symposium. 30th Anniversary Historical Background at the Time Copyright © 2014 by Ken SAKAMURA 8 I4004 by Intel (1971) 2014 TRON Symposium. 30th Anniversary Alto by Xerox (1973) 2014 TRON Symposium. 30th Anniversary 2014 TRON Symposium. 30th Anniversary ③ Future Design Copyright © 2014 by Ken SAKAMURA 11 2014 TRON Symposium. 30th Anniversary How the Society Will Change Based on Newly Available Computers? Copyright © 2014 by Ken SAKAMURA 12 2014 TRON Symposium.
  • U.S. Government Publishing Office Style Manual

    U.S. Government Publishing Office Style Manual

    Style Manual An official guide to the form and style of Federal Government publishing | 2016 Keeping America Informed | OFFICIAL | DIGITAL | SECURE [email protected] Production and Distribution Notes This publication was typeset electronically using Helvetica and Minion Pro typefaces. It was printed using vegetable oil-based ink on recycled paper containing 30% post consumer waste. The GPO Style Manual will be distributed to libraries in the Federal Depository Library Program. To find a depository library near you, please go to the Federal depository library directory at http://catalog.gpo.gov/fdlpdir/public.jsp. The electronic text of this publication is available for public use free of charge at https://www.govinfo.gov/gpo-style-manual. Library of Congress Cataloging-in-Publication Data Names: United States. Government Publishing Office, author. Title: Style manual : an official guide to the form and style of federal government publications / U.S. Government Publishing Office. Other titles: Official guide to the form and style of federal government publications | Also known as: GPO style manual Description: 2016; official U.S. Government edition. | Washington, DC : U.S. Government Publishing Office, 2016. | Includes index. Identifiers: LCCN 2016055634| ISBN 9780160936029 (cloth) | ISBN 0160936020 (cloth) | ISBN 9780160936012 (paper) | ISBN 0160936012 (paper) Subjects: LCSH: Printing—United States—Style manuals. | Printing, Public—United States—Handbooks, manuals, etc. | Publishers and publishing—United States—Handbooks, manuals, etc. | Authorship—Style manuals. | Editing—Handbooks, manuals, etc. Classification: LCC Z253 .U58 2016 | DDC 808/.02—dc23 | SUDOC GP 1.23/4:ST 9/2016 LC record available at https://lccn.loc.gov/2016055634 Use of ISBN Prefix This is the official U.S.
  • Μitron4.0 Specification (Ver

    Μitron4.0 Specification (Ver

    µITRON4.0 Specification Ver. 4.00.00 ITRON Committee, TRON ASSOCIATION Supervised by Ken Sakamura Edited by Hiroaki Takada Copyright (C) 1999, 2002 by TRON ASSOCIATION, JAPAN µITRON4.0 Specification (Ver. 4.00.00) The copyright of this specification document belongs to the ITRON Committee of the TRON Association. The ITRON Committee of the TRON Association grants the permission to copy the whole or a part of this specification document and to redistribute it intact without charge or with a distribution fee. However, when a part of this specification document is redistributed, it must clearly state (1) that it is a part of the µITRON4.0 Specification document, (2) which part it was taken, and (3) the method to obtain the whole specifi- cation document. See Section 6.1 for more information on the conditions for using this specification and this specification document. Any questions regarding this specification and this specification document should be directed to the following: ITRON Committee, TRON Association Katsuta Building 5F 3-39, Mita 1-chome, Minato-ku, Tokyo 108-0073, JAPAN TEL: +81-3-3454-3191 FAX: +81-3-3454-3224 § TRON is the abbreviation of “The Real-time Operating system Nucleus.” § ITRON is the abbreviation of “Industrial TRON.” § µITRON is the abbreviation of “Micro Industrial TRON.” § BTRON is the abbreviation of “Business TRON.” § CTRON is the abbreviation of “Central and Communication TRON.” § TRON, ITRON, µITRON, BTRON, and CTRON do not refer to any specific product or products. µITRON4.0 Specification Ver. 4.00.00 A Word from the Project Leader Fifteen years have passed since the ITRON Sub-Project started as a part of the TRON Project: a real-time operating system specification for embedded equipment control.
  • Analysis of a Hardware-Based Real-Time Kernel

    Analysis of a Hardware-Based Real-Time Kernel

    MÄLARDALEN UNIVERSITY, DEPARTMENT OF SCIENCE, DESIGN AND TECHNOLOGY Analysis of a Hardware- Based Real-Time Kernel Improving Embedded Systems Performance Author: Nils Forsberg ([email protected]) Supervisor: Lennart Lindh Examiner and Supervisor: Moris Behnam 5/5/2014 An evaluation of how to improve embedded and real-time systems performance. I Abstract Embedded systems rely on faster microprocessors and system optimizations to improve their performance. These enhancements are becoming marginal, and so it is interesting to look at other alternatives. This thesis examines the use of a hardware-based kernel called Sierra as an accelerator for software-based real-time operating systems. The software RTOS focused upon is FreeRTOS, and it is compared to Sierra in regards to performance to see if there is actually any improvement to be gained. This proves true, as Sierra is several times faster than FreeRTOS in regards to most of the functionality measured. In order to find out how difficult it would be to perform such acceleration a comparison of the systems is also included, encompassing their architecture, features and functionality. It is showed that the systems are similar in these properties, meaning acceleration would be possible. This information was used in an analysis that shows how to perform the acceleration. The work of implementing system acceleration is not in the scope of this thesis, but the result is presented as a suggestion, or manual, for future work in this vein. II Sammanfattning Inbäddade system förlitar sig på snabbare mikroprocessorer och optimeringar för att nå bättre prestanda resultat. Dessa förbättringar ger allt mindre resultat, och det är därför intressant att hitta alternativ.
  • Run-Time Management for Future Mpsoc Platforms

    Run-Time Management for Future Mpsoc Platforms

    Run-time management for future MPSoC platforms Citation for published version (APA): Nollet, V. (2008). Run-time management for future MPSoC platforms. Technische Universiteit Eindhoven. https://doi.org/10.6100/IR633897 DOI: 10.6100/IR633897 Document status and date: Published: 01/01/2008 Document Version: Publisher’s PDF, also known as Version of Record (includes final page, issue and volume numbers) Please check the document version of this publication: • A submitted manuscript is the version of the article upon submission and before peer-review. There can be important differences between the submitted version and the official published version of record. People interested in the research are advised to contact the author for the final version of the publication, or visit the DOI to the publisher's website. • The final author version and the galley proof are versions of the publication after peer review. • The final published version features the final layout of the paper including the volume, issue and page numbers. Link to publication General rights Copyright and moral rights for the publications made accessible in the public portal are retained by the authors and/or other copyright owners and it is a condition of accessing publications that users recognise and abide by the legal requirements associated with these rights. • Users may download and print one copy of any publication from the public portal for the purpose of private study or research. • You may not further distribute the material or use it for any profit-making activity or commercial gain • You may freely distribute the URL identifying the publication in the public portal.
  • Economic Impact of Technology Standards

    Economic Impact of Technology Standards

    Economic Impact of Technology Standards The past and the road ahead September 2017 Authors: Jorge Padilla, John Davies and Aleksandra Boutin compasslexecon.com This report was commissioned by Qualcomm Incorporated. All opinions expressed here are those of the authors, who are all employees of Compass Lexecon: Jorge Padilla, John Davies and Aleksandra Boutin, supported by Anubhav Mohanty and Sabire Ipek Demir. Executive Summary COMpass LEXECON Economic Impact of Technology Standards The past and the road ahead Executive Summary 1.1 This report examines the economic impact of technology others in the ITC sector. Furthermore, this approach is standards - which enable components from different spreading, not least because other industries are adopting suppliers to work together - on innovation, competition and wireless technologies in the ‘Internet of Things’. thus consumer choice and welfare. Such standards exist in 1.6 The mobile telephony industry has seen an impressive rate of all industries but are particularly important in Information growth and innovation, as well as a dynamic market structure and Communications Technology. We show that the way in in which new entrants continue to arise to challenge existing which these standards are developed and governed can have suppliers. Between 1994 and 2013, the number of devices profound implications for the pace of innovation and intensity sold each year rose 62 times or 20.1% per year on average. of competition. The cost of mobile subscriptions relative to maximum data 1.2 We present evidence that industries such as mobile speed has decreased 99% (approx. 40% per year) between telephony, which are based on open standards agreed through 2005 and 2013.
  • Modeling Creativity

    Modeling Creativity

    TOM DE SMEDT — MODELING CREATIVITY Faculteit Letteren en Wijsbegeerte Departement Taalkunde Modeling Creativity CASE STUDIES IN PYTHON Computermodellen van Creativiteit: Gevalstudies in de Python-programmeertaal Proefschrift voorgelegd tot het behalen van de graad van doctor in de Kunsten aan de Universiteit Antwerpen te verdedigen door Tom De Smedt PROMOTOR Prof. dr. Walter Daelemans CLiPS Computational Linguistics Group Universiteit Antwerpen CO-PROMOTOR Lucas Nijs EMRG Experimental Media Research Group St. Lucas University College of Art & Design, Antwerpen Antwerpen, 2013 1 TOM DE SMEDT — MODELING CREATIVITY Cover artwork: SELF-REPLICATION (Tom De Smedt & Ludivine Lechat) The fonts in the book are Computer Modern, Helvetica Neue, Arial and Courier New. The text was written in Google Docs. The layout was processed in LibreOffice. The illustrations were done in NodeBox. Computer Modern, LibreOffice and NodeBox are free and open source. Print: Silhouet, Maldegem © 2013 Tom De Smedt 2013 Uitgeverij UPA University Press Antwerp UPA is an imprint of ASP nv (Academic and Scientific Publishers nv) Ravensteengalerij 28 B-1000 Brussels Tel. +32 (0)2 289 26 50 Fax +32 (0)2 289 26 59 E-mail: [email protected] www.upa-editions.be ISBN 978 90 5718 260 0 NUR 984 / 616 / 656 Legal deposit D/2013/11.161/016 All rights reserved. No part of this book may be reproduced or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of the author. 2 TOM DE SMEDT — MODELING CREATIVITY Modeling Creativity CASE STUDIES IN PYTHON Tom De Smedt “Enough!” he said, hoarse with indignation.