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

Michael Hammer <michael.hammer@yaanatech.com> Thu, 06 February 2014 02:39 UTC

Return-Path: <michael.hammer@yaanatech.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 5E2291A0277 for <dispatch@ietfa.amsl.com>; Wed, 5 Feb 2014 18:39:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.436
X-Spam-Level:
X-Spam-Status: No, score=-2.436 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, 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 hpgbi9DuMIfa for <dispatch@ietfa.amsl.com>; Wed, 5 Feb 2014 18:39:36 -0800 (PST)
Received: from email1.corp.yaanatech.com (webmail10.yaanatech.com [63.128.177.10]) by ietfa.amsl.com (Postfix) with ESMTP id 567581A0207 for <dispatch@ietf.org>; Wed, 5 Feb 2014 18:39:36 -0800 (PST)
Received: from SC9-EX2K10MB1.corp.yaanatech.com ([fe80::149d:c2e1:8065:2a47]) by ex2k10hub1.corp.yaanatech.com ([::1]) with mapi id 14.03.0123.003; Wed, 5 Feb 2014 18:39:35 -0800
From: Michael Hammer <michael.hammer@yaanatech.com>
To: "jim.forster@rangenetworks.com" <jim.forster@rangenetworks.com>, "mary.ietf.barnes@gmail.com" <mary.ietf.barnes@gmail.com>
Thread-Topic: [dispatch] SIP and GSM/UMTS with OpenBTS
Thread-Index: AQHPIj0OkF9riHfhQ0Se4gDBfVRQX5qmz3RggAAosQCAAAyAAIAAASOQgAC9HICAAALFAIAAAFCA//96B5CAAI2tgIAALnMA//+H5WA=
Date: Thu, 06 Feb 2014 02:39:34 +0000
Message-ID: <00C069FD01E0324C9FFCADF539701DB3BBF241C5@sc9-ex2k10mb1.corp.yaanatech.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>
In-Reply-To: <948FB37B-F2D4-4462-8B29-D03FDF65215F@rangenetworks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.17.100.48]
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="SHA1"; boundary="----=_NextPart_000_022F_01CF22BA.C23C0AD0"
MIME-Version: 1.0
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 02:39:38 -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.

But, I'll mind my own suggestion and not go there.

Michael Hammer
Principal Engineer
michael.hammer@yaanatech.com
Mobile: +1 408-202-9291
500 Yosemite Drive Suite 120
Milpitas, CA 95035 USA


-----Original Message-----
From: Jim Forster [mailto:jim.forster@rangenetworks.com] 
Sent: Wednesday, February 05, 2014 8:46 PM
To: Mary Barnes
Cc: Michael Hammer; dispatch@ietf.org
Subject: Re: [dispatch] SIP and GSM/UMTS with OpenBTS

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