DOCSLIB.ORG

External SS/USSD Interface

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
External SS/USSD Interface External SS/USSD interface Vadim Yanitskiy <[email protected]> Talk structure Introduction into Supplementary Services and USSD What is Supplementary Services and USSD? What is so special about SS/USSD? How does it work in commercial networks? How does it work in the Osmocom CNI? Basic configuration examples DEMO Introduction into USSD What is USSD? Unstructured Supplementary Services Data Usually, USSD requests look like: *FOO*BAR# or *#ZOO# e.g. *#100# in both OsmoMSC and OpenBSC Common use cases: Information check applications e.g. account balance, own MSISDN e.g. news, weather, horoscope, etc. Activation / deactivation of (paid) network services Subscriber notifications, advertisements Introduction into Supplementary Services Supplementary Services: Call related (pdisc = GSM48_PDISC_CC) Advice of Charge information multi-party calls call hold Call independent (pdisc = GSM48_PDISC_NC_SS) call waiting service (de)activation call forwarding management What is SS/USSD? A structured kind of call independent Supplementary Services Similar to SMS, but real-time communication is assumed Up to 160 octets payload length Introduction into SS/USSD What is so special about USSD? Cost efficiency uses existing network’s protocols … thus no extensions / upgrades required existing (free / commercial) USSD gateways Fast and responsive the real-time capability enables fast and responsive services Interactive the session-based property enables interactive (menu-based) applications Introduction into USSD Interesting facts: The *FOO*BAR# or *#ZOO# format is not mandatory for USSD-requests! the only restriction (by GSM TS 04.80) is default 7-bit GSM alphabet … thus balance.mno.com and msisdn.mno.com are valid USSD requests some old Nokia phones allow composing such ASCII requests ;) USSD message coding is based on MAP (Mobile Application Protocol) MAP is an SS7 protocol, 3GPP TS 29.002, ~1k pages … thus every phone does MAP message encoding / decoding USSD can be (optionally) used as a transport for WAP! see "WAP over GSM USSD" by WAP Forum Ltd. SS/USSD in commercial networks SS/USSD in commercial networks SS/USSD message encapsulation is different: A-interface: according to GSM TS 04.80 D-interface: TCAP/MAP (BEGIN, CONTINUE, END) re-encapsulation happens at MSC (see 3GPP TS 09.11) A MO SS/USSD session can be handled by: an external entity (e.g. USSD gateway) MSC, VLR, HLR internally A MT SS/USSD session can be initiated by: an external entity (e.g. USSD gateway) MSC, VLR, HLR internally SS/USSD in the Osmocom CNI (before) OsmoNiTB (still) & OsmoMSC (before): All SS/USSD requests are terminated at libmsc (the MSC part) Own number request (hard-coded *#100#) only Adding support of new codes requires: modification the source code (libmsc/ussd.c), (re)compilation of the source code, restarting the network (if active), ⇒ too complicated for end user :/ External USSD interface We have external interfaces for: SMS (via SMPP) voice calls (via MNCC) External USSD interface? (OS#1597) Which protocol should be used? MAP is assumed by the specs., but: there is no stable Osmocom implementation of MAP, complex protocol… SMPP has some provisions for USSD, but: not session-oriented nature… GSUP? GSUP? What is GSUP? Generic Subscriber Update Protocol Osmocom-specific non-standard protocol Aimed to keep protocol complexity out of its users: OsmoHLR, OsmoMSC, OsmoSGSN. GSUP → MAP conversation is assumed Advantages: Easy to use Easy to extend Easy to convert to MAP Disadvantages: Not session-oriented :( but can be extended! SS/USSD in the Osmocom CNI (OsmoHLR) SS/USSD in the Osmocom CNI (MAP) Current state of GSUP implementation Session management (TCAP emulation): The following new IEs were introduced: OSMO_GSUP_SESSION_STATE_IE (BEGIN, CONTINUE, END), OSMO_GSUP_SESSION_ID_IE (i.e. unique session ID). we can distinguish between several concurrent SS/USSD sessions we can manage the state of particular SS/USSD session: initiate a new one reuse the existing one terminate the existing one Current state of GSUP implementation USSD payload support: The following new messages were introduced: OSMO_GSUP_MSGT_PROC_SS_REQUEST, OSMO_GSUP_MSGT_PROC_SS_ERROR, OSMO_GSUP_MSGT_PROC_SS_RESULT. The following IEs were introduced: OSMO_GSUP_SS_INFO_IE USSD - GSUP / MAP message conversation A message coming from MS to MSC (or vice versa): A message coming from MSC to HLR (or vice versa): A message coming from HLR to USSD GW (or vice versa): Current work around GSUP implementation Message flow example: Mobile initiated USSD-session Status of the current implementation What is already done: libosmocore GSM 04.80 API improvment: Support of optional FACILITY IE in RELEASE_COMPLETE Raw USSD payload access DCS decoding OsmoMSC: Subscriber connection ref-counting GSUP message coding & forwarding Counters for USSD events Transaction management OsmoHLR: internal & external handler support SS/USSD message parsing prefix-based routing Status of the current implementation Future plans: Further libosmocore GSM 04.80 API improvements ability to parse separate message parts better way to handle decoding errors "Structured" SS message support: call forwarding configuration waiting call configuration … etc. SS version negotiation TTCN-3 test coverage OsmoMSC (OS#2931) single MO USSD request & response single MT USSD notification MO / MT USSD during a voice call MS-initiated RELEASE OsmoHLR (OS#3439) non-existing route (error handling) IUSE (internal handler) tests: own MSISDN own IMSI EUSE (external handler) tests: connection error handling routing tests HLR configuration example hlr gsup bind ip 127.0.0.1 ... ! External USSD handling entities euse foo-00-00-00-00-00-00 euse bar-00-00-00-00-00-00 euse zoo-00-00-00-00-00-00 ... ! Prefix-based routes ussd route prefix *#100# internal own-msisdn ussd route prefix *#101# internal own-imsi ussd route prefix *100* external foo-00-00-00-00-00-00 ussd route prefix *999*1 external bar-00-00-00-00-00-00 ... ! Default "gateway" for all unmatched USSD-requests ussd default-route external zoo-00-00-00-00-00-00 Questions? Thanks! References: 3GPP TS 04.10 "Supplementary Services Specification" 3GPP TS 04.80 "Formats and coding of Supplementary Services" GSM TS 09.02 "Mobile Application Part (MAP) specification" Section 11 "Supplementary services related services" Section 7.6.4 "Supplementary services parameters" Section 7.6.3 "Subscriber management parameters" Section 7.6.1 "Common parameters" "GSM MSC/VLR Unstructured Supplementary Service Data(USSD) Service" by Egemen Taskin https://osmocom.org/issues/1597 .
Load more

Recommended publications
  • Ussd Gateway
    USSD GATEWAY Create mobile campaigns and services for any mobile phone with Panacea Mobile’s USSD Gateway. WHAT IS USSD? Unstructured Supplementary Service Data (USSD) allows you to display a plain text message, typically a menu or instructions, on any GSM phone to which users can then respond. A USSD session begins when a user makes a phone call to a USSD string (e.g. *120*912#) on their mobile phone. TRY IT NOW Access the Panacea Mobile USSD info portal by dialing the following number on your mobile phone: *120*912# FEATURES Build Campaigns Store Session Data Create surveys, mobile portals, competitions and more All user responses are saved and can even be reused using the online campaign builder. in the current session to give users a personalised experience. Integrate Your Services Set your campaign to fetch text from your web services Earn Revenue and push back user responses. Set up paid content services and earn revenue with premium rated USSD strings. Create Responses Redirect users to different nodes (pages) or trigger an Detailed Reporting SMS, email or web call based on their responses. View total sessions, impressions, costs and revenue as well as user responses and detailed individual session info. FREQUENTLY How much does it cost? Does your USSD Gateway have APIs? You get one free sub-string for your account Yes, our entire USSD service is built on APIs, ASKED and 500 free sessions every month! You can so you can manage your USSD campaigns QUESTIONS buy additional sub-strings for a once off cost and retrieve the data on your own server.
    [Show full text]
  • USSD Gateway
    USSD Gateway The Unstructured Supplementary Service Data The handset recognizes those numbers and for- (USSD) Server allows a user to interact directly wards the request to the Homisco USSD Gate- with network-based functions from their GSM way server instead of initializing a normal call or mobile phone. a data call. No additional application, phone menu or SIM menu is needed for the Homisco The USSD Server provides the framework for a USSD Gateway to function, as USSD is sup- rich set of subscriber capabilities and services, ported by nearly every GSM handset. including subscriber account management, bal- ance inquiry, callback, messaging, voting, short The Homisco USSD Server currently supports quiz applications and interactive chat. the following capabilities: Account Top-Up - allows users to add funds to their mo- The USSD Server provides the framework for a bile account rich set of subscriber capabilities and services including subscriber account management, bal- Balance Inquiry – users can retrieve their current ac- count balance and expiration date with USSD messaging ance inquiry, callback, messaging, voting, short quiz applications, and interactive chat. Bonus Inquiry – users can receive their account bonus or promotion status USSD can minimize the use of voice-channel Voting – a user can submit a vote through USSD and resources by reducing user interaction with In- receive confirmation of receipt teractive Voice Response (IVR) applications. It Call Me – a user can send a USSD Call Me request mes- provides rapid session-based short message sage to another user and receive confirmation of receipt response. It can improve the user experience by Notify Me - a user can submit a USSD request to be speeding transaction response as compared alerted when a selected mobile registers on the system with latency delays common with typical store- Self Care - a user can change various parameters of their and-forward Short Message Service (SMS).
    [Show full text]
  • 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
    [Show full text]
  • Dirty Use of USSD Codes in Cellular Networks
    Dirty use of USSD codes in cellular . networks Ravishankar Borgaonkar Security in Telecommunications, Technische Universität Berlin TelcoSecDay, Heidelberg, 12th March 2013 ✆ USSD in mobile communication ☠ USSD network attacks ☠ Andriod Attacks Agenda USSD codes and services in mobile telephony Attacks in USSD network infrastructure Attacks on smartphones (end-users) SecT / TU-Berlin 2 / 35 ✆ USSD in mobile communication ☠ USSD network attacks ☠ Andriod Attacks USSD Basics technology - features - applications What is USSD in mobile telephony? a messaging service between mobile phones and an application server in the network but data is transferred in real time as a session (no SMSC-store and forward) faster than SMS and interactive service supported by all mobiles - feature phones to smartphones why USSD? to increase ARPU (Average Revenue Per User) SecT / TU-Berlin 3 / 35 ✆ USSD in mobile communication ☠ USSD network attacks ☠ Andriod Attacks USSD Applications Services Services based on USSD protocol: interactive data services (News, Sports etc) pre-paid phone top-up and balance queries mobile banking and money services access to social services such as Twitter, Facebook SecT / TU-Berlin 4 / 35 ✆ USSD in mobile communication ☠ USSD network attacks ☠ Andriod Attacks USSD Applications Toilet thinking Motivation stories Airtel Money in India, really? An interesting document playing with NFC protocol on Android with Collin SecT / TU-Berlin 5 / 35 ✆ USSD in mobile communication ☠ USSD network attacks ☠ Andriod Attacks GSM architecture GSM cellular
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • 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
    [Show full text]
  • 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.
    [Show full text]
  • 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
    [Show full text]
  • Ussi Product Brochure (Rev 1.0)
    USSi Gateway USSD for IP Multimedia Subsystem data networks PHrotectsides ExtendsHides Frees-upHides ComplexityInvestment ComplexityUSSD to ComplexityNetwork ofin Mobile USSD 4G/5Gof Mobile Networks Resourcesof Mobile Network Network Network Why USSi Gateway? USSD is the primary channel that 2G/3G customers use to What is USSi Gateway? consume essential USSD services like: Pharos’ USSD over IP Multimedia Subsystem (USSi) Gateway • Customer Self-Care: data bundle purchases, price-plan changes, bridges your existing SS7 mobile network with the rest of the VAS subscriptions internet-connected world; without you needing to make any • Airtime Management: airtime loans, balance enquiry, top-ups, changes to your existing USSD applications/services. credit transfers • Call Request and Set-up: please-call-me back, prepaid roaming The gateway is a SIP-to-MAP protocol convertor that enables callback smartphone-using subscribers to seamlessly use existing USSD services over 4G/5G. It eliminates the need to switch subscribers • m-Commerce: mobile money, banking over to 2G/3G network to use USSD, which frees-up network • Infotainment: news, sports signalling and radio resources. As a result, it provides customers with a similar responsive USSD user experience to that provided Today’s 4G/LTE and tomorrow’s 5G data networks, however, do by 2G/3G. not come with native USSD support! On top of this, USSi Gateway extends the investment in and As a temporary workaround to enable 4G/5G customers to use lifespan of your existing SS7-based USSD services and USSD, operators switch customers over to their circuit-switched infrastructure because it allows you to provide a fluid USSD networks; and switch them back to their data networks after they experience to all subscribers, regardless of their handset radio finish using USSD (CSFB).
    [Show full text]
  • USSD Gateway for 2G/3G Networks Product Brief Overview
    USSD Gateway For 2G/3G Networks Product brief Overview Modulo’s Unstructured Supplementary Services Data (USSD) Gateway is a network element that connects between the mobile signaling network (SS7) and HTTP-based Value-Added Service Applications. USSD applications can create new revenue streams for the mobile operator and its business clients. USSD can be used for real-time charging, content delivery, polling and surveys, banking services and more. The USSD Gateway allows subscribers to send USSD messages in order to receive information and services from the operator. USSD messages are session-based, meaning they require an online continuous connection. This makes USSD messaging much faster than SMS messages (no Store-and- Forward). Our simple and easy RESTful HTTP API allows any web developer to easily create new USSD applications for the mobile network. Solution Features Full Compliance with both Phase 1 & Phase 2 USSD standards A simple and easy to use Restful HTTP API, which allows for the development of additional USSD services by any web developer. High speed message transfer Highly scalable architecture Allows easy creation of menu-based services Modulo Communications Systems Ltd. 14 Imber St. Petah Tikva 49514, ISRAEL Tel. +972 72 274 4000 Fax. +972 3 774 1114 http://www.modulo.co.il USSD Gateway For 2G/3G Networks Product brief Use Cases CHECKING BALANCE AND PAYING PHONE BILL / RECHARGING PREPAID CONTENT PORTAL CONDUCTING POLLS Modulo Communications Systems Ltd. 14 Imber St. Petah Tikva 49514, ISRAEL Tel. +972 72 274 4000 Fax. +972 3 774 1114 http://www.modulo.co.il USSD Gateway For 2G/3G Networks Product brief ADDITIONAL USE CASES Changing Device Settings Polling Banking: Account Management Chatting Shopping And more… The HTTP API feature in Modulo’s USSD Gateway creates infinite possibilities for new USSD-based services to be developed.
    [Show full text]
  • 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.
    [Show full text]