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

Jim Forster <jim.forster@rangenetworks.com> Thu, 06 February 2014 01:46 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 D7C201A0137 for <dispatch@ietfa.amsl.com>; Wed, 5 Feb 2014 17:46:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 hUOvCiVJEiyE for <dispatch@ietfa.amsl.com>; Wed, 5 Feb 2014 17:46:31 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1blp0181.outbound.protection.outlook.com [207.46.163.181]) by ietfa.amsl.com (Postfix) with ESMTP id C27821A0194 for <dispatch@ietf.org>; Wed, 5 Feb 2014 17:46:30 -0800 (PST)
Received: from BL2PR03MB404.namprd03.prod.outlook.com (10.141.91.149) by BL2PR03MB402.namprd03.prod.outlook.com (10.141.91.146) with Microsoft SMTP Server (TLS) id 15.0.868.8; Thu, 6 Feb 2014 01:46:28 +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; Thu, 6 Feb 2014 01:46:27 +0000
From: Jim Forster <jim.forster@rangenetworks.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Thread-Topic: [dispatch] SIP and GSM/UMTS with OpenBTS
Thread-Index: AQHPIj0OkF9riHfhQ0Se4gDBfVRQX5qmz3RggAAosQCAAAyAAIAAASOQgAA3AICAAALFAIAAAFCAgAAAZICAAAdQgIAALnKA
Date: Thu, 06 Feb 2014 01:46:26 +0000
Message-ID: <948FB37B-F2D4-4462-8B29-D03FDF65215F@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>
In-Reply-To: <CAHBDyN5-O3pNury3RUNzstGHO8NCq6pV3ewHt_Yrxjd1k-if5Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [114.69.245.154]
x-forefront-prvs: 0114FF88F6
x-forefront-antispam-report: SFV:NSPM; SFS:(10019001)(6009001)(199002)(189002)(2656002)(81542001)(80976001)(66066001)(93136001)(81342001)(63696002)(92726001)(59766001)(74502001)(47976001)(74662001)(77982001)(80022001)(47736001)(49866001)(65816001)(83322001)(31966008)(81686001)(87266001)(4396001)(54356001)(74366001)(76482001)(79102001)(76796001)(46102001)(51856001)(94316002)(50986001)(33656001)(93516002)(83716003)(86362001)(90146001)(74876001)(36756003)(92566001)(56816005)(81816001)(87936001)(53806001)(82746002)(47446002)(56776001)(76786001)(74706001)(69226001)(94946001)(83072002)(54316002)(85306002)(85852003)(95416001); DIR:OUT; SFP:1102; SCL:1; SRVR:BL2PR03MB402; H:BL2PR03MB404.namprd03.prod.outlook.com; CLIP:114.69.245.154; FPR:FEABF214.AC3E9F01.81D59D7B.8AF5E278.20401; InfoNoRecordsA:1; MX:1; LANG:en;
Content-Type: multipart/signed; boundary="Apple-Mail=_B724CE4B-3D09-4F84-9D21-4030379F2D76"; 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: Thu, 06 Feb 2014 01:46:34 -0000

Mary, all,

Lots to read and consider.  I'll be offline for 12 hours as we drive to Delhi.

> I don't necessarily think 3GPP is out of scope in that I think it's very important that if IETF decides that we will be documenting or even defining protocol elements to support OpenBTS, it needs to be clear why 3GPP Call control/SIP specifications aren't being used. 

Umm, one possible reason but I need to read and think, would be the question of whether 3GPP Call control/SIP is in some ways tied to 4G/LTE in some way.  OpenBTS puts 2G/3G phones on the Internet.

> In offline in discussions with the proponents, it's my understanding that OpenBTS is being used in very specific environments where there is no full MSC deployments (i.e., remote locations that have no deployed IMS networks).  The intent isn't to replicate a full IMS system, but rather to provide basic connectivity to the Internet and use SIP in a non-IMS context to complete the calls.   So, I think more detail about this context would be very helpful.

Yes, that's correct.  No full MSC; in fact only Asterix or Freeswitch or Yate, usually embedded in the same device as the RF and signaling.

The goal was and is to make really small, low power, devices that can be deployed where classic systems don't fit, usually because they cost too much and take too much power.  Small islands, Antarctic research stations, the jungle of Paupua Indonesia, etc. 

This very reduced system, which might possibly be called IMS Lite for 2G/3G phones, seems to be very useful to people that want to make calls and send SMS in those places.  It's not clear (largely because of my ignorance) how a full IMS benefits those scenarios, while the simple OpenBTS translation/gateway of 2G & 3G calls to SIP is a package that people want.  Well, to be clear, people with phones don't care what protocols are used, they care about other aspects, like power and cost.

> I think it would really help if there were some diagrams showing what IMS protocols are being used.

Well, I can certainly provide some diagrams that show how the system works.

>  My understanding is that current implementations have various ways in which they are interworking the Radio Layer Call Control messages to SIP messages.  I think the motivation is to improve interop by defining a consistent "mapping" if you will.

Correct.

>  It's not clear to me how exactly registration is being handled - perhaps mapping some of the Radio Layer mobility management messages.   My understanding is that there can be no change to the existing messages from the cell phone to the BTS for obvious reasons, so all the interworking needs to happen in the BTS.  

Correct.

  -- Jim