Real Time Sampling of Utilization at Ericsson Test Plants

Total Page:16

File Type:pdf, Size:1020Kb

Real Time Sampling of Utilization at Ericsson Test Plants LiU-ITN-TEK-A--10/035--SE Real time sampling of utilization at Ericsson Test Plants Marky Egebäck Sebastian Lindqvist 2010-06-10 Department of Science and Technology Institutionen för teknik och naturvetenskap Linköping University Linköpings Universitet SE-601 74 Norrköping, Sweden 601 74 Norrköping LiU-ITN-TEK-A--10/035--SE Real time sampling of utilization at Ericsson Test Plants Examensarbete utfört i kommunikations- och transportsystem vid Tekniska Högskolan vid Linköpings universitet Marky Egebäck Sebastian Lindqvist Handledare Torbjörn Wikström Examinator Di Yuan Norrköping 2010-06-10 Upphovsrätt Detta dokument hålls tillgängligt på Internet – eller dess framtida ersättare – under en längre tid från publiceringsdatum under förutsättning att inga extra- ordinära omständigheter uppstår. Tillgång till dokumentet innebär tillstånd för var och en att läsa, ladda ner, skriva ut enstaka kopior för enskilt bruk och att använda det oförändrat för ickekommersiell forskning och för undervisning. Överföring av upphovsrätten vid en senare tidpunkt kan inte upphäva detta tillstånd. All annan användning av dokumentet kräver upphovsmannens medgivande. För att garantera äktheten, säkerheten och tillgängligheten finns det lösningar av teknisk och administrativ art. Upphovsmannens ideella rätt innefattar rätt att bli nämnd som upphovsman i den omfattning som god sed kräver vid användning av dokumentet på ovan beskrivna sätt samt skydd mot att dokumentet ändras eller presenteras i sådan form eller i sådant sammanhang som är kränkande för upphovsmannens litterära eller konstnärliga anseende eller egenart. För ytterligare information om Linköping University Electronic Press se förlagets hemsida http://www.ep.liu.se/ Copyright The publishers will keep this document online on the Internet - or its possible replacement - for a considerable time from the date of publication barring exceptional circumstances. The online availability of the document implies a permanent permission for anyone to read, to download, to print out single copies for your own use and to use it unchanged for any non-commercial research and educational purpose. Subsequent transfers of copyright cannot revoke this permission. All other uses of the document are conditional on the consent of the copyright owner. The publisher has taken technical and administrative measures to assure authenticity, security and accessibility. According to intellectual property law the author has the right to be mentioned when his/her work is accessed as described above and to be protected against infringement. For additional information about the Linköping University Electronic Press and its procedures for publication and for assurance of document integrity, please refer to its WWW home page: http://www.ep.liu.se/ © Marky Egebäck, Sebastian Lindqvist Abstract This master’s thesis has been written within the field of Electrical Engineering at the De- partment of Science and Technology, Linköping University. The work has been carried out at Ericsson’s site in Linköping during the spring of 2010. The purpose of this master thesis was to construct a model which could capture and present the utilization rate of test equipment at a telecom company in general. Since this field has not been studied very much in the past, it was decided to study a model from the production industry and try to reuse some of the basic ideas from this model. From this generic model a recommendation is given as to how the model could be used by implementing a Common Utilization Tool, which could be used to store, configure and present utilization data from all types of equipment in Ericsson’s test environment. This common uti- lization tool will use measurement modules that will both collect and classify the state of the equipment and deliver the result to a common database. To this Common Utilization Tool a measurement module has been implemented which samples Base Station Controllers (BSC) in Ericsson’s test environment state; used, unused and down. This implementation is also validated against real measured data from testers to conclude if the results are accurate. i Acknowledgments We would like to express our deepest gratitude to our supervisors Torbjörn Wickström at Er- icsson AB, David Gundlegård and Di Yuan at the Department of Science and Technology in Linkoping’s university. Without your knowledge, support and helping hand we would never been able to complete this thesis. A special thanks to Thomas Thunell, Anders Hollstedt, Jonas Madsen and the rest of the ATD Team for answering all our LTE Util Tool and THC questions. Without you guys the work with the BSC utilization module, which is a big part of our work, would not have been preformed as smoothly. We would also like to thank the rest of the people who helped us create the BSC utiliza- tion module; Ulf Arkad, Tomi Ojala Carlbergh, Jens Lindberg and Samka Nyberg. Another person that we would like to thank is Liz Foxbrook for greatly improving the lan- guage in the report. Last but not least we would like to thank the people at our section and department that has given us so much support and encouragement during the work of this thesis. Linköping, May 2010. Marky Egebäck and Sebastian Lindqvist iii Contents 1 Introduction 1 1.1 Background.......................................1 1.2 Purpose.........................................2 1.3 Objectives........................................2 1.4 Method.........................................2 1.5 Scope..........................................3 1.6 Confidentiality.....................................3 1.7 Outline.........................................3 1.8 The GSM Organization................................3 1.9 Testing.........................................4 1.10 Ericsson test environment - BETE..........................5 2 Frame of reference7 2.1 OEE - Overall equipment efficiency..........................7 2.1.1 Availability Efficiency.............................8 2.1.2 Operational Efficiency.............................8 2.1.3 Rate Efficiency.................................9 2.1.4 Quality Efficiency...............................9 2.1.5 Applications of OEE..............................9 2.1.6 Limitations of OEE..............................9 2.2 Performance Management............................... 10 2.3 Sampling theory.................................... 11 2.3.1 Sampling methods............................... 12 2.3.2 Sampling period................................ 12 2.3.2.1 Normal distribution......................... 12 2.3.2.2 Binomial distribution........................ 14 2.4 Measurement process.................................. 15 2.4.1 Measures.................................... 15 2.4.2 Activities in the measurement process.................... 15 2.4.2.1 Establish and sustain measurement commitment......... 15 2.4.2.2 Plan the measurement process................... 15 2.4.2.3 Perform the measurement process................. 16 2.4.2.4 Evaluate measurement....................... 16 2.4.3 The measurement information model..................... 16 v vi Contents 3 GSM 19 3.1 GSM specifications................................... 20 3.1.1 GSM Phases.................................. 20 3.1.2 Services in GSM................................ 21 3.2 GSM Network Architecture.............................. 21 3.2.1 Radio Subsystem................................ 22 3.2.2 Mobile Station................................. 22 3.2.3 Base Station Subsystem............................ 23 3.2.4 Network and Switching Subsystem...................... 24 3.2.5 Mobile Switching Center (Mobile Services Switching Center)....... 24 3.2.6 SMSC...................................... 25 3.3 GSM Areas....................................... 25 3.4 Databases and Registers................................ 25 3.4.1 Home-location-register (HLR)......................... 25 3.4.2 Visitor-location-register (VLR)........................ 26 3.5 Operations Support Subsystem............................ 26 3.5.1 Operations And Maintenance Center..................... 26 3.5.1.1 Telecommunications management network............ 26 3.5.2 Authentication Center............................. 27 3.5.3 EIR....................................... 28 3.6 Radio interface..................................... 28 3.6.1 Logical Channels................................ 29 3.6.1.1 Traffic Channels........................... 30 3.6.1.2 Control Channels.......................... 30 3.6.1.3 GSM Mapping............................ 31 3.7 Protocols in GSM.................................... 32 3.8 Addressing and localization in GSM......................... 33 3.8.1 International Mobile Subscriber Identity (IMSI)............... 34 3.8.2 Temporary mobile subscriber identity (TMSI)................ 34 3.8.3 Local Mobile Subscriber Identity (LMSI).................. 34 3.8.4 Mobile Station (or Subscriber) ISDN Number (MSISDN)......... 34 3.8.5 The Mobile Station Roaming Number (MSRN)............... 34 3.8.6 International mobile station equipment identity (IMEI).......... 34 3.9 Data services...................................... 34 3.9.1 GPRS...................................... 34 3.9.1.1 SGSN................................. 35 3.9.1.2 GGSN................................. 35 3.9.1.3 Location managemnet........................ 36 3.9.2 EDGE...................................... 36 4 GSM Evolutions 37 4.1 WCDMA........................................ 37 4.1.1 System and network architecture of WCDMA................ 37 4.2 LTE........................................... 39 4.2.1
Recommended publications
  • 02-03 Korthet
    2 ERICSSON IN BRIEF 1999 - : In November, itu established wcdma as the standard for g mobile systems under the name imt Direct Spread. The decision was welcomed by Erics- son, which can now offer its operator customers all three major versions of this standard. : In terms of number of employees, the takeover of Qualcomm’s infrastructure division was Ericsson’s largest acquisition during , provid- ing Ericsson with a complete product portfolio of second- and third-generation mobile systems. It also accelerated the pace of work in the standardiza- tion area, which was appreciated by the industry as a whole, particularly by the operators. : Ericsson acquired the American companies Torrent and TouchWave and the Danish company Telebit a/s to further strengthen its position in the market for ip and datacom solutions. : In December, Ericsson and Microsoft announced that they would cooperate in the devel- opment and marketing of total solutions for wire- less Internet access. The parties will establish a ERICSSON’S MISSION is jointly owned company to market and supply to understand its mobile e-mail solutions. Ericsson will be the customers’ opportunities majority owner in the new company. and needs, and to provide : During , Ericsson achieved major communication solutions successes with engine, a solution for migrating better than any circuit-switched fixed telecommunications net- competitor. works to a next-generation network that can handle circuit-switched and ip-based, packet-linked traf- IN DOING SO, Ericsson fic. bt in the U.K., kpn in the Netherlands, Telia shall generate a in Denmark and Telefónica in Spain chose engine competitive economic during the year.
    [Show full text]
  • Glossary of Acronyms
    Glossary of Acronyms This glossary provides short definitions of a range of abbreviations· and acronyms in use within the cordless telecommunications field; many of the terms are defined in greater detail within this volume. ACCH associated control channel ACELP algebraic code-excited linear prediction, vocoder ACK acknowledgement protocol ACTE Approval Committee for Telecommunication Equipment ACW address code word ADM adaptive delta modulation ADPCM adaptive differential pulse-code modulation AGC automatic gain control AIN advanced intelligent network ALT automatic link transfer AM access manager AMPS American Mobile Phone System - US cellular standard API application programming interface ARA alerting/registration area ARI access rights identifier ARIB Association of Radio Industries and Businesses (Japan) ARQ automatic repeat request ATIS Alliance for Telecommunications Industry Solutions (USA) AWGN additive white Gaussian noise B echo balance return loss B channel user information bearer channel, 64 kb s-l, in ISDN BABT British Approvals Board for Telecommunications BCCH broadcast channel BCT business cordless telephone BER bit error ratio BMC/BMD burst mode controller/device BPSK binary phase shift keying, modulation BRA ISDN basic rate access BS basestation - the fixed radio component of a cordless link, single-channel or multichannel; term also used in cellular radio Glossary of Acronyms 507 BS6833 a standard for digital cordless telephones allowing for proprietary air interfaces (mainly specifying telephony-related aspects) (UK)
    [Show full text]
  • End-Of-Life Treatment of Radio Base Station Transceivers in Europe, Japan and the USA – a Life Cycle Assessment Study
    End-of-Life treatment of Radio Base Station transceivers in Europe, Japan and the USA – a Life Cycle Assessment study Anna Grunewald Jessica Gustavsson Stockholm 991210 TRITA-KTH-IM 1999:22 Lith-IKP-ING-EX--99/19--SE Preface This study was initiated by Ericsson Radio Systems AB and carried out as a co-operation between Ericsson Radio Systems AB, Linköping Institute of Technology and the Royal Institute of Technology in Stockholm during the summer and autumn of 1999. First of all, we would like to thank our supervisors during the project, Susanne Lundberg at Ericsson Radio Systems AB, Jörgen Furuhjelm at Linköping Institute of Technology and Lennart Nilson at the Royal Institute of Technology for valuable help and guidance throughout the project. We would also like to express our gratitude to Jens Malmodin, Richard Trankell and Elaine Weidman at Ericsson Radio Systems AB and to Fjalar Kommonen at FFK Ltd for all their help. One of the most difficult tasks in this study was to develop probable logistic scenarios for the take-back of discarded transceivers. We would like to take this opportunity to thank amongst others Rickard Slettmyr and Mattias Sundstedt at Ericsson Radio Systems AB and Mikael Hietarinta at Nippon Ericsson for taking time to help us with this. Finally, we would like to thank our contact persons at the involved recycling companies, who have provided valuable information to the study; Kazuo Suzuki at Total Environmental Recycling Management, Mike Ogle and Darrel Stoecklin at United Recycling Industries Inc., Johan Zwart at MIREC B.V., Lennart Edvinsson at Ragn-Sells Elektronikåtervinning AB, Anders Axelsson and Sune Nordström at AB Arv Andersson, Sören Brännström and Theo Lehner at Boliden AB, Lars Cronquist at Gotthard Aluminium AB and Christer Forsgren at SAKAB.
    [Show full text]
  • Design Options of Store-Oriented Software Ecosystems: an Investigation of Business Decisions ∗
    Design Options of Store-Oriented Software Ecosystems: An Investigation of Business Decisions ∗ Bahar Jazayeri1, Olaf Zimmermann2, Gregor Engels1, Jochen K¨uster3, Dennis Kundisch1, Daniel Szopinski1 1 Paderborn University, Germany fbahar.jazayeri,gregor.engels,dennis.kundisch,[email protected] 2 University of Applied Sciences of Eastern Switzerland, Switzerland [email protected] 3 Bielefeld University of Applied Sciences, Germany [email protected] Abstract. Nowadays companies like Apple create ecosystems of third- party providers and users around their software platforms. Often online stores like Apple App Store are created to directly market third-party solutions. We call such ecosystems store-oriented software ecosystems. While the architecture of these ecosystems is mainly derived from busi- ness decisions of their owners, ecosystems with greatly different archi- tectural designs have been created. This diversity makes it challenging for future ecosystem providers to understand which architectural design is suitable to fulfill certain business decisions. In turn, opening a plat- form becomes risky while endangering intellectual property or scarifying quality of services. In this paper, we identify three main design options of store-oriented software ecosystems by classifying existing ecosystems based on similarities in their business decisions. We elaborate on the design options, discuss their main contributions, and provide exemplary ecosystems. Our work provides aspiring ecosystem providers with the reusable knowledge of existing ecosystems and helps them to take more informed architectural decisions and reduce risks in future. Keywords: Software ecosystems, Reusable designs, Variabilities 1 Introduction Software ecosystems have become an emerging architectural approach for many companies to grow. The term software ecosystem is inspired from ecological ecosystems that are the result of an interplay between organisms as well as interactions with a physical environment [1].
    [Show full text]
  • Cross-Platform Environment for Application Life Cycle Management
    International Journal “Information Theories and Applications”, Vol. 24, Number 2, © 2017 177 CROSS-PLATFORM ENVIRONMENT FOR APPLICATION LIFE CYCLE MANAGEMENT Elena Chebanyuk, Oleksii Hlukhov Abstract: “Application Lifecycle Management (ALM) integrates and governs the planning, definition, design, development, testing, deployment, and management phases throughout the application lifecycle” [OMG, 2006]. This paper is devoted to designing of ALM for supporting all software development processes. A review of papers, making strong contribution for improving software development life cycle processes is represented. This review touches three branches of investigation, namely papers, related to: (1) improving of communication processes between stakeholders; (2) increasing effectiveness of some operations in software development life cycle processes; (3) developing fundamental methods and tools for performing different operations related to several software development life cycle. Then comparative analysis of such ALM environments as Visual Studio, Team Foundation Server, FusionForge, TeamForge, IBM Rational Team Concert, IBM Rational Software Architect, and IBM Rational Functional Tester, is performed. Comparison of different ALM environments’ functionality lets to formulate requirements for designing cross-platform ALM environment. Then the conceptual schema of cross-platform ALM based on Eclipse environment is proposed. All plugins’ functionalities were properly tested. Collaboration of plugins for supporting several software development tasks
    [Show full text]
  • Collabnet Subversion Edge User Guide 2 | Subversion Edge | TOC
    CollabNet Subversion Edge User Guide 2 | Subversion Edge | TOC Contents Welcome to CollabNet Subversion Edge.............................................................................7 Set up Subversion Edge .......................................................................................................8 Install Subversion Edge ...........................................................................................................................8 Install Subversion Edge on Windows...........................................................................................8 Install Subversion Edge on Linux................................................................................................9 Install Subversion Edge on Solaris.............................................................................................10 Configure the server...............................................................................................................................12 Configure general server settings...............................................................................................12 Configure advanced server settings............................................................................................13 Configure authentication settings...............................................................................................13 Configure a proxy server............................................................................................................14 Configure the mail server...........................................................................................................14
    [Show full text]
  • IKAN ALM and Collabnet Teamforge Where Development, Testing and Operations Meet Table of Contents
    IKAN ALM and Collabnet TeamForge Where Development, Testing and Operations meet Table of contents Executive summary ..............................................................................................................................................3 Problem statement ...............................................................................................................................................4 Solution Description ............................................................................................................................................4 TeamForge and IKAN ALM ...........................................................................................................................5 Versioning .......................................................................................................................................................5 TeamForge Tracker ........................................................................................................................................6 Integrated Build and Deploy Process .......................................................................................................7 Notification .....................................................................................................................................................7 Short description of IKAN ALM ..........................................................................................................................8 Lifecycle ...........................................................................................................................................................8
    [Show full text]
  • News Alert 4 January, 2012
    www.pwc.co m/in Sharing insights News Alert 4 January, 2012 No ‘business connection’ constituted in India for sale of GSM systems; payment for embedded software held as not in the nature of ‘royalty’ – Delhi High Court affirms decision of Income-tax Appellate Tribunal (Special Bench) in case of Ericsson AB, Sweden In brief taxable as ‘royalty’, either under the provisions of the Income-tax Act, 1961 (the Act) or under the India-Sweden Double Taxation Avoidance Agreement (the tax In a recent decision, in the case of Ericsson Radio Systems A.B. Sweden 1 (EAB), the treaty). Delhi High Court (HC) has upheld the Income-tax Appellate Tribunal (the Tribunal) Special Bench Ruling in case of Motorola Inc. v. DCIT 2 by holding that Facts EAB did not have a ‘business connection’ in India and that consideration/payment for supply of software (embedded in the telecommunication GSM system) is not • EAB is a company incorporated in Sweden. For the financial years (FYs) 1996- 97 and 1997-98 (relevant years), it was engaged in the business of manufacture 1 DIT v. Ericsson Radio System AB [TS-769-HC-2011 (DEL)] 2 Motorola Inc. v. DCIT [2005] 95 ITD 269 (Del) 1 PwC News Alert January 2012 and sale of telecommunication GSM systems (comprising equipment and • On appeal, the Commissioner of Income-tax (Appeals) (CIT(A)) granted partial software) to various cellular operators the world over, including in India. relief to EAB. Against the order of the CIT (A), the Revenue and EAB preferred an appeal to the Tribunal. These appeals and cross- appeals, along with • During the year under consideration, EAB entered into contracts with various appeals of other tax payers, namely Nokia and Motorola, were referred to the Indian cellular operators (ICOs) for supply of GSM systems.
    [Show full text]
  • Teamforge 6.2 Administration Guide 2 | Teamforge 6.2 | TOC
    TeamForge 6.2 Administration Guide 2 | TeamForge 6.2 | TOC Contents TeamForge system administrator how-tos..........................................................................7 Install CollabNet TeamForge 6.2..............................................................................................................7 Plan your CollabNet TeamForge 6.2 installation.........................................................................7 Set up networking for your TeamForge box ................................................................................8 Install CollabNet TeamForge 6.2 on Red Hat..............................................................................9 Install CollabNet TeamForge 6.2 on CentOS.............................................................................48 Install CollabNet TeamForge 6.2 on SuSE.................................................................................87 Install TeamForge on VMware or ESXi...................................................................................129 Upgrade to TeamForge 6.2 Patch ........................................................................................................132 Plan your upgrade to TeamForge 6.2........................................................................................132 Upgrade to TeamForge 6.2 on Red Hat....................................................................................133 Upgrade to TeamForge 6.2 on CentOS....................................................................................168
    [Show full text]
  • A T T Dt Ti D a T T Dt Ti D Automated Testing and Devops for Continuous
    AtAutoma tdTted Testi ng and DevOps for Continuous Delivery Dan Gahafer July 2012 A Combat Support Agency What is DevOps? • The integration of software development with operations to enable the rapid delivery of new capabilities • Increase release frequency while reducing risk by: – Collaborating across organization – Reducing change scope – Increasing release coordination – Automating!!! Deploy is the new Build 2 A Combat Support Agency Role of Test • Despite the name, Test is not excluded Testers & Developer Sys Admins & Testers • Without integrated Test, DevOps will fail! • Test expands and adapts to support this constant motion – integrated with development and operations teams – graduate to scriptable test cases – support automation Better, faster, more comprehensive coverage 3 A Combat Support Agency Continuous Improvement Agile Software Continuous Continuous Development Integration Delivery Software Forge Jenkins Puppet Forge.mil CDP 4 A Combat Support Agency Distributed Dev Challenge TODAY: • Siloed development environments Shared Asset • Expensive and time consuming start-up Libraries & Repositories • Limit ed exposure, sh ari ng, or re-use Tester • Duplication of effort Developer Developer Shared Test & Development Certifier Tools/Services/Environments User GOAL: • Agile development and testing • Cross-program sharing: software and services • Early and continuous collaboration • Integrated approach to development life cycle • Extensible platform to support delivery of partner capabilities 5 A Combat Support Agency Application Delivery • Requirements Management • Source Code Management Code • Continuous Integration Build TtTest • Cloud / Environment Management • Configuration Management • Package Management 6 A Combat Support Agency Managing Chaos 7 A Combat Support Agency Continuous Delivery Principles – Software development should be a fast, repeatable process. – Versioning does not apply just to code, but to (almost) everything needed to build, deploy, test and release.
    [Show full text]
  • Collabnet Teamforge 5.4 Site Administrator Guide
    CollabNet TeamForge 5.4 Site Administrator Guide OpenTopic | TOC | 3 Contents Legal ®ne print.....................................................................................................................................................9 CollabNet, Inc. Trademark and Logos.....................................................................................................9 Highlights of CollabNet TeamForge 5.4 ...........................................................................................................11 Chapter 1: Manage users..............................................................................13 Create a new user account......................................................................................................................14 Create a user group.................................................................................................................................14 Add a user to a user group......................................................................................................................15 Find a user..............................................................................................................................................15 Edit a user account.................................................................................................................................15 Change multiple user accounts...............................................................................................................16 Reset the admin account password.........................................................................................................16
    [Show full text]
  • Teamforge 7.1 Administration Guide | Contents | 2
    TeamForge 7.1 Administration Guide | Contents | 2 Contents TeamForge system administrator how-tos.............................................................6 Install CollabNet TeamForge 7.1........................................................................................................................6 Plan your CollabNet TeamForge 7.1 installation.....................................................................................6 Set up networking for your TeamForge server........................................................................................7 Install CollabNet TeamForge 7.1 on Red Hat/CentOS............................................................................7 Install CollabNet TeamForge 7.1 on SuSE............................................................................................58 Install TeamForge on VMware Player or VMware ESXi................................................................... 107 Upgrade to TeamForge 7.1.............................................................................................................................. 111 Plan your upgrade to TeamForge 7.1.................................................................................................. 111 Upgrade to TeamForge 7.1 on Red Hat/CentOS................................................................................. 112 Upgrade to TeamForge 7.1 on SuSE................................................................................................... 182 Upgrade to CollabNet TeamForge 7.1 on a virtual
    [Show full text]