Re: [dispatch] SIP and GSM/UMTS with OpenBTS

Jim Forster <jim.forster@rangenetworks.com> Fri, 07 February 2014 18:56 UTC

Return-Path: <jim.forster@rangenetworks.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58EF21AC7F1 for <dispatch@ietfa.amsl.com>; Fri, 7 Feb 2014 10:56:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.302
X-Spam-Level:
X-Spam-Status: No, score=-2.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kcc8c8a_42sw for <dispatch@ietfa.amsl.com>; Fri, 7 Feb 2014 10:56:24 -0800 (PST)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0236.outbound.protection.outlook.com [207.46.163.236]) by ietfa.amsl.com (Postfix) with ESMTP id 79AD91A0459 for <dispatch@ietf.org>; Fri, 7 Feb 2014 10:56:23 -0800 (PST)
Received: from BL2PR03MB404.namprd03.prod.outlook.com (10.141.91.149) by BL2PR03MB401.namprd03.prod.outlook.com (10.141.91.145) with Microsoft SMTP Server (TLS) id 15.0.868.8; Fri, 7 Feb 2014 18:56:22 +0000
Received: from BL2PR03MB404.namprd03.prod.outlook.com ([10.141.91.149]) by BL2PR03MB404.namprd03.prod.outlook.com ([10.141.91.149]) with mapi id 15.00.0868.013; Fri, 7 Feb 2014 18:56:21 +0000
From: Jim Forster <jim.forster@rangenetworks.com>
To: Gullik Webjörn <gullik.webjorn@corevalue.se>
Thread-Topic: [dispatch] SIP and GSM/UMTS with OpenBTS
Thread-Index: AQHPIj0OkF9riHfhQ0Se4gDBfVRQX5qmz3RggAAosQCAAAyAAIAAASOQgAA3AICAAALFAIAAAFCAgAAAZICAAAdQgIAALnKAgAAO2QCAAjuzgIAAGAoAgABPewA=
Date: Fri, 07 Feb 2014 18:56:20 +0000
Message-ID: <FF33B7D3-32BD-461E-B6E3-38109D87A5EF@rangenetworks.com>
References: <040E1A40-BC55-4CFC-834A-FC958DEFDE25@rangenetworks.com> <949EF20990823C4C85C18D59AA11AD8B12A6DE@FR712WXCHMBA11.zeu.alcatel-lucent.com> <60884D2D-1CC8-4A21-97BE-2ACCB49C351D@rangenetworks.com> <7723B448-642F-4138-89DD-379ACC7FA593@rangenetworks.com> <E1FE4C082A89A246A11D7F32A95A17826DFCD495@US70UWXCHMBA02.zam.alcatel-lucent.com> <F5DA260C-32C9-4D92-9169-2026983BFC47@gmail.com> <E1FE4C082A89A246A11D7F32A95A17826DFCD852@US70UWXCHMBA02.zam.alcatel-lucent.com> <77E6DEC0-BCE1-4607-B52C-A4B6761A4B17@gmail.com> <00C069FD01E0324C9FFCADF539701DB3BBF23E22@sc9-ex2k10mb1.corp.yaanatech.com> <CAHBDyN5-O3pNury3RUNzstGHO8NCq6pV3ewHt_Yrxjd1k-if5Q@mail.gmail.com> <948FB37B-F2D4-4462-8B29-D03FDF65215F@rangenetworks.com> <00C069FD01E0324C9FFCADF539701DB3BBF241C5@sc9-ex2k10mb1.corp.yaanatech.com> <AD3958C3-CAA4-44DD-BEEF-0B0F6895F447@westhawk.co.uk> <52F4E9A4.5000203@corevalue.se>
In-Reply-To: <52F4E9A4.5000203@corevalue.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [61.12.100.227]
x-forefront-prvs: 011579F31F
x-forefront-antispam-report: SFV:NSPM; SFS:(10019001)(6009001)(189002)(199002)(51704005)(76796001)(81542001)(50986001)(74366001)(93136001)(63696002)(74876001)(76786001)(46102001)(36756003)(47976001)(80022001)(87266001)(66066001)(94946001)(65816001)(74706001)(69226001)(53806001)(74662001)(33656001)(92726001)(59766001)(54356001)(86362001)(94316002)(92566001)(74502001)(31966008)(87936001)(83716003)(81686001)(81816001)(82746002)(85306002)(81342001)(85852003)(77982001)(83322001)(93516002)(54316002)(80976001)(4396001)(2656002)(83072002)(47446002)(49866001)(56776001)(47736001)(95416001)(51856001)(56816005)(90146001)(79102001)(76482001); DIR:OUT; SFP:1102; SCL:1; SRVR:BL2PR03MB401; H:BL2PR03MB404.namprd03.prod.outlook.com; CLIP:61.12.100.227; FPR:FEFAF5D8.AF1435A7.B9E417B7.44EDEB61.202C4; InfoNoRecordsMX:1; A:1; LANG:en;
Content-Type: multipart/signed; boundary="Apple-Mail=_4725560E-F4E5-4370-B26E-4FC6BF78C112"; protocol="application/pgp-signature"; micalg="pgp-sha1"
MIME-Version: 1.0
X-OriginatorOrg: rangenetworks.com
Cc: "dispatch@ietf.org" <dispatch@ietf.org>
Subject: Re: [dispatch] SIP and GSM/UMTS with OpenBTS
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Feb 2014 18:56:26 -0000

>>> Interesting.  But, the 4G/LTE network is an IP internet of sorts.
>>> The SIP/IMS components do not need to be in the radio network,
>>> and thus not at the locations where the power is constrained.
>> One of the nice properties of an openBTS install in a remote location is that it
>> can still function as a local 'pbx' at times when the internet link is down. This turns out to
>> be fabulously useful in a crisis. If you delegate all the logic out to a cloud service that stops being true.
>> 
>> Tim.
> I agree violently, the challenge here is to design the distributed protocol(s) add-ons that would enable
> building a sip/GSM network out of hundreds or more autonomous BTS's.
> 
> Gullik

I agree mostly with both of you:

 * Standalone/disconnected OpenBTS's have good value in emergency response or remote work environments.  Turn it on phones in the footprint can call each other; no backhaul or Core Network.  In some cases that are connected, over a thin link, there is a great bandwidth savings, and reliability improvement, by having a local switch.  I believe the Antarctic research station paid for its OpenBTS in a few months of operation, due to savings in satellite bandwidth over the GSM standard approach with the BSC/MSC on the other side of the satellite link. Plus, solar storms would knock out the link and and disable even local calls.

 * There are indeed challenges (and value) in large networks

I still owe the list a diagram which would facilitate understanding and discussion.

  -- JIm