Trillium 3G Wireless Software White Paper | Radisys
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Data Networks
Second Ed ition Data Networks DIMITRI BERTSEKAS Massachusetts Institute of Technology ROBERT GALLAGER Massachusetts Institute ofTechnology PRENTICE HALL, Englewood Cliffs, New Jersey 07632 2 Node A Node B Time at B --------- Packet 0 Point-to-Point Protocols and Links 2.1 INTRODUCTION This chapter first provides an introduction to the physical communication links that constitute the building blocks of data networks. The major focus of the chapter is then data link control (i.e., the point-to-point protocols needed to control the passage of data over a communication link). Finally, a number of point-to-point protocols at the network, transport, and physical layers are discussed. There are many similarities between the point-to-point protocols at these different layers, and it is desirable to discuss them together before addressing the more complex network-wide protocols for routing, flow control, and multiaccess control. The treatment of physical links in Section 2.2 is a brief introduction to a very large topic. The reason for the brevity is not that the subject lacks importance or inherent interest, but rather, that a thorough understanding requires a background in linear system theory, random processes, and modem communication theory. In this section we pro vide a sufficient overview for those lacking this background and provide a review and perspective for those with more background. 37 38 Point-to-Point Protocols and Links Chap. 2 In dealing with the physical layer in Section 2.2, we discuss both the actual com munication channels used by the network and whatever interface modules are required at the ends of the channels to transmit and receive digital data (see Fig 2.1). -
Miot Location in Roaming Version 1.0 20 May 2020
GSM Association Confidential - Full, Rapporteur, Associate and Affiliate Members Official Document NG.120 - MIoT Location in Roaming MIoT Location in Roaming Version 1.0 20 May 2020 This is a Non-binding Permanent Reference Document of the GSMA Security Classification: Confidential - Full, Rapporteur, Associate and Affiliate Members Access to and distribution of this document is restricted to the persons permitted by the security classification. This document is confidential to the Association and is subject to copyright protection. This document is to be used only for the purposes for which it has been supplied and information contained in it must not be disclosed or in any other way made available, in whole or in part, to persons other than those permitted under the security classification without the prior written approval of the Association. Copyright Notice Copyright © 2020 GSM Association Disclaimer The GSM Association (“Association”) makes no representation, warranty or undertaking (express or implied) with respect to and does not accept any responsibility for, and hereby disclaims liability for the accuracy or completeness or timeliness of the information contained in this document. The information contained in this document may be subject to change without prior notice. Antitrust Notice The information contain herein is in full compliance with the GSM Association’s antitrust compliance policy. V1.0 Page 1 of 37 GSM Association Confidential - Full, Rapporteur, Associate and Affiliate Members Official Document NG.120 - MIoT Location -
USSD Gateway Technical Guide
Oracle® Communications Network Charging and Control USSD Gateway Technical Guide Release 12.0.0 December 2017 Copyright Copyright © 2017, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error- free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. -
High-Level Data Link Control
ELEC3030 (EL336) Computer Networks S Chen High-Level Data Link Control • This class of data link layer protocols includes High-level Data Link Control (HDLC), Link Access Procedure Balanced (LAPB) for X.25, Link Access Procedure for D-channel (LAPD) for ISDN, and Logic Link Control (LLC) for FDDI • The frame format is: Flag Address Control Data FCS Flag Note that address and control bits 8 8 8 variable 16 8 can be extended to 16 bits, so bit position 12 3 4 5 6 7 8 N(S)=send sequence number N(R)=receive sequence number that sequence number is 7-bit Information: 0 N(S) P/F N(R) S=supervisory function bits P/F • Frame flag: 01111110, so bit Supervisory: 1 0 S N(R) M=unumbered function bits stuffing is used Unumbered: 1 1 M P/F M P/F=poll/final bit • Address: For multipoint operation, it is used to identify the terminal that transmits or receives the frame and, in point-to-point link, it is used to distinguish Commands from Responses (2nd bit for C/R: 0/1). The address is now extended to 16 bits (1st bit indicates long/short 16/8 bits) • Checksum: FCS contains the remainder of a 16-bit CRC calculation of the frame. It may be extended to 32 bits, using a 32-bit CRC • Control: Three types of frames, I, S and U frames. The old protocol uses a sliding window with 3-bit sequence number and the maximum window size is N = 7. The control field is now extended to 16 bits with 7-bit sequence number 60 ELEC3030 (EL336) Computer Networks S Chen HDLC (continue) • I-frames: carry user data. -
Security for the Core Network of Third Generation Mobile Systems
Security for the core network of third generation mobile systems GUNTER HORN, DIRK KROSELBERG Siemens AG, Corporate Technology, D-81730 Muenchen, Germany STEFANPUTZ T-Mobil, P.O. Box 300463, D-53184 Bonn, Germany ROLAND SCHMITZ T-Nova Technology Centre, D-64307 Darmstadt, Germany Keywords: UMTS, MAP Security, Multimedia domain, SIP, IPSec, IKE, Key Management Abstract: This contribution gives a survey of the present standardisation activities by 3GPP (3'd Generation Partnership Project1) in the area of security for signalling in the core network of third generation mobile systems. We give an overview of the protocols that need to be secured, present the basic principles behind the overall security architecture and describe the key management and format of secured messages, as far as they have already been finalised. In particular, we address core network security aspects of the 3GPP multimedia domain. 1 3GPP was formed by regional standards organisations from Europe, Asia and North America to produce specifications for a third generation mobile system named UMTS which is designed to evolve from GSM core network. There is a competing effort known as 3GPP2 with partners from North America and Asia. The original version of this chapter was revised: The copyright line was incorrect. This has been corrected. The Erratum to this chapter is available at DOI: 10.1007/978-0-387-35413-2_36 R. Steinmetz et al. (eds.), Communications and Multimedia Security Issues of the New Century © IFIP International Federation for Information Processing 2001 298 1. THREATS TO CORE NETWORK SECURITY FOR MOBILE RADIO NETWORKS The core network of mobile radio systems is the part of the network which is independent of the radio interface technology of the mobile terminal. -
Teleware BT Proposition
Private Mobile eXchange ™ PMX ™ GSM Mobile Switching Centre Product Highlights – IP softMSC 3GPP switching compliant Distributed Network Architecture Multiple processing units & redundancy, GSM Compliant ‘A’ Interface - IP High Availability, Scalability & Flexibility Multiple Vendor Radio Access Networks MSC, GMSC, HLR, VLR Central HLR (Network) supported MAP-C, MAP-D, MAP-E, MAP-F Call forwarding (conditional, unconditional), call waiting, call hold, call transfer IP: SS7 over SIGTRAN and SIP support TDM: SS7 over TDM via Gateway Calling party based routing, Intelligent call routing GTT translations, STP supported Caller Id; CLIP/CLIR Support for SMS (MT/MO) Connected Line Id; COLP/COLR Explicit/Implicit IMSI detach & VLR purge Operator determined barring GPRS & EDGE support (Gr over SS7) E.164 support CSD Support - secure phones + PSTN Gateway Support for Lawful Call intercept Optional built-in SMSC, AuC and EIR function SIP RFC 3261 Support Optional voicemail, conferencing and external WAP, multi-media message entity platforms Call Detail Recoding Optional Media Termination Point [Transcoding SOS: Default or LA originated intelligent routing outbound & Inbound] of emergency calls Enterprise Support Highlights Full PBX network node support Optional: Push-To-Talk – PMR replacement Translation table, Inbound & Outbound Private Mobile Office – Personal Number, Personal Assistant, Unified Messaging, Call recording, Extensive Routing Tables conferencing, IVR incl. Call Queuing etc Business Confidential Product -
Mobile Application Part Interface (MAPI) Specification
Mobile Application Part Interface (MAPI) Specification Mobile Application Part Interface (MAPI) Specification Version 1.1 Edition 7.20141001 Updated October 25, 2014 Distributed with Package openss7-1.1.7.20141001 Copyright c 2008-2014 Monavacon Limited All Rights Reserved. Abstract: This document is a Specification containing technical details concerning the imple- mentation of the Mobile Application Part Interface (MAPI) for OpenSS7. It contains recommendations on software architecture as well as platform and system applicability of the Mobile Application Part Interface (MAPI). It provides abstraction of the Mobile Application Part (MAP) interface to these components as well as providing a basis for Mobile Application Part control for other Mobile Application Part protocols. Brian Bidulock <[email protected]> for The OpenSS7 Project <http://www.openss7.org/> Published by: OpenSS7 Corporation 1469 Jefferys Crescent Edmonton, Alberta T6L 6T1 Canada Copyright c 2008-2014 Monavacon Limited Copyright c 2001-2008 OpenSS7 Corporation Copyright c 1997-2000 Brian F. G. Bidulock All Rights Reserved. Unauthorized distribution or duplication is prohibited. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [GNU Free Documentation License], page 405. Permission to use, copy and distribute this documentation without modification, for any purpose and without fee or royalty is hereby granted, provided that both the above copyright notice and this permission notice appears in all copies and that the name of OpenSS7 Corporation not be used in advertising or publicity pertaining to distribution of this documentation or its contents without specific, written prior permission. -
International Civil Aviation Organization
Guidance for the Implementation of National IP Networks INTERNATIONAL CIVIL AVIATION ORGANIZATION PROJECT RLA/06/901 GUIDANCE FOR THE IMPLEMENTATION OF NATIONAL DIGITAL NETWORKS THAT USE THE IP PROTOCOL, TO SUPPORT CURRENT AND FUTURE AERONAUTICAL APPLICATIONS Project RLA/06/901 Page 1 Guidance for the Implementation of National IP Networks The designations employed and the presentation of material in this publication do not imply the expression of any opinion whatsoever on the part of ICAO concerning the legal status of any country, territory, city or area or of its authorities, or concerning the delimination of its frontiers or boundaries. Project RLA/06/901 Page 2 Guidance for the Implementation of National IP Networks TABLE OF CONTENTS i. Table of Contents..................................................................................................................... 3 ii. Background.............................................................................................................................. 4 General Decision-Making Considerations ............................................................................... 5 Business ......................................................................................................................... 5 Industrial Support........................................................................................................... 5 Security Policies............................................................................................................. 5 Implementation ............................................................................................................. -
3GPP TS 29.002 V3.14.0 (2002-09) Technical Specification
3GPP TS 29.002 V3.14.0 (2002-09) Technical Specification 3rd Generation Partnership Project; Technical Specification Group Core Network; Mobile Application Part (MAP) specification (Release 1999) R GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS rd TM The present document has been developed within the 3 Generation Partnership Project (3GPP ) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification. TM Specifications and reports for implementation of the 3GPP system should be obtained via the 3GPP Organisational Partners' Publications Offices. Release 1999 2 3GPP TS 29.002 V3.14.0 (2002-09) Keywords GSM. UMTS, MAP, SS7, network 3GPP Postal address 3GPP support office address 650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Internet http://www.3gpp.org Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. © 2002, 3GPP Organizational Partners (ARIB, CWTS, ETSI, T1, TTA, TTC). All rights reserved. 3GPP Release 1999 3 3GPP TS 29.002 V3.14.0 (2002-09) Contents Foreword ..........................................................................................................................................................25 -
Chapter 5 Peer-To-Peer Protocols and Data Link Layer
Chapter 5 Peer-to-Peer Protocols and Data Link Layer PART I: Peer-to-Peer Protocols Peer-to-Peer Protocols and Service Models ARQ Protocols and Reliable Data Transfer Flow Control Timing Recovery TCP Reliable Stream Service & Flow Control Chapter 5 Peer-to-Peer Protocols and Data Link Layer PART II: Data Link Controls Framing Point-to-Point Protocol High-Level Data Link Control Link Sharing Using Statistical Multiplexing Chapter Overview z Peer-to-Peer protocols: many protocols involve the interaction between two peers z Service Models are discussed & examples given z Detailed discussion of ARQ provides example of development of peer-to-peer protocols z Flow control, TCP reliable stream, and timing recovery z Data Link Layer z Framing z PPP & HDLC protocols z Statistical multiplexing for link sharing Chapter 5 Peer-to-Peer Protocols and Data Link Layer Peer-to-Peer Protocols and Service Models Peer-to-Peer Protocols zzz zzz z Peer-to-Peer processes execute layer-n protocol to provide service to n + 1 peer process n + 1 peer process layer-(n+1) z Layer-(n+1) peer calls SDU SDU layer-n and passes PDU Service Data Units n peer process n peer process (SDUs) for transfer z Layer-n peers exchange Protocol Data Units (PDUs) to effect transfer n – 1 peer process n – 1 peer process z Layer-n delivers SDUs to destination layer-(n+1) peer zzz zzz Service Models z The service model specifies the information transfer service layer-n provides to layer-(n+1) z The most important distinction is whether the service is: z Connection-oriented z Connectionless z Service model possible features: z Arbitrary message size or structure z Sequencing and Reliability z Timing, Pacing, and Flow control z Multiplexing z Privacy, integrity, and authentication Connection-Oriented Transfer Service z Connection Establishment z Connection must be established between layer-(n+1) peers z Layer-n protocol must: Set initial parameters, e.g. -
Request for Comments on the Draft Outline for The
International Telecommunication Union QUESTION 18/2 Strategy for migration of mobile networks to IMT-2000 and beyond ITU-D STUDY GROUP 2 RAPPORTEUR FOR QUESTION 18/2 IMT-2000 for developing countries” IMT-2000 “Mid-Term Guidelines (MTG) on the smooth transition of existing mobile networks to IMT-2000 for developing countries” “Mid-Term Guidelines (MTG) on the smooth transition of existing mobile networks to Guidelines (MTG) on the smooth transition of existing “Mid-Term QUESTION 18/2 International Telecommunication Printed in Switzerland Union Geneva, 2005 Photo credits: ITU Photo Library ITU-D THE STUDY GROUPS OF ITU-D The ITU-D Study Groups were set up in accordance with Resolutions 2 of the World Telecommunication Development Conference (WTDC) held in Buenos Aires, Argentina, in 1994). For the period 2002-2006, Study Group 1 is entrusted with the study of seven Questions in the field of telecommunication development strategies and policies. Study Group 2 is entrusted with the study of eleven Questions in the field of development and management of telecommunication services and networks. For this period, in order to respond as quickly as possible to the concerns of developing countries, instead of being approved during the WTDC, the output of each Question is published as and when it is ready. For further information Please contact: Ms Fidélia AKPO Telecommunication Development Bureau (BDT) ITU Place des Nations CH-1211 GENEVA 20 Switzerland Telephone: +41 22 730 5439 Fax: +41 22 730 5484 E-mail: [email protected] Placing orders for ITU publications Please note that orders cannot be taken over the telephone. -
Mobile Application Part (MAP)
3GPP2 X.S0004-000-E v 6.0 Date: July 2007 Mobile Application Part (MAP) INTRODUCTION COPYRIGHT 3GPP2 and its Organizational Partners claim copyright in this document and individual OPs may copyright and issue documents or standards publications in individual Organizationial Partner’s name based on this document. Requests for reproduction of this document should be directed to the 3GPP2 Secretariat at [email protected]. Requests to reproduce individual Organizationial Part- ner’s documents should be directed to that Organizational Partner. See www.3gpp2.org for more information. X.S0004-000-E 1 2 Revision History 3 4 Revision Date Remarks 5 (IS-41) 0 February 1988 Initial publication. 6 7 (IS-41) A January 1991 8 9 (IS-41) B December 1991 10 (IS-41) C February 1996 11 12 TIA/EIA-41-D December 1997 Initial ANSI publication. 13 X.S0004-000-E v1.0 March 2004 Initial publication with new part 14 X.S0004-500 ••• 590-E v1.0 structure. 15 X.S0004-700 ••• 790-E 16 17 X.S0004-000-E v2.0 July 2005 Version 2.0. 18 X.S0004-400-E July 2005 Initial publication with new part 19 X.S0004-600 ••• 691-E structure. 20 21 X.S0004-000-E v3.0 October 2005 Version 3.0. 22 X.S0004-691-E v2.0 October 2005 Addition of Annex F: RECOVERY 23 FROM SCCP SEGMENTATION 24 FAILURE. 25 26 X.S0004-000-E v4.0 May 2006 Version 4.0. 27 X.S0004-200 and 290-E May 2006 Initial ANSI publication with new 28 part structure.