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

Michael Hammer <michael.hammer@yaanatech.com> Sat, 15 February 2014 03:00 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 C6C7E1A0035 for <dispatch@ietfa.amsl.com>; Fri, 14 Feb 2014 19:00:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level:
X-Spam-Status: No, score=-1.848 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_64=0.6, RP_MATCHES_RCVD=-0.548, 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 qekRBN1t6wGr for <dispatch@ietfa.amsl.com>; Fri, 14 Feb 2014 19:00:03 -0800 (PST)
Received: from email1.corp.yaanatech.com (webmail10.yaanatech.com [63.128.177.10]) by ietfa.amsl.com (Postfix) with ESMTP id A10341A0031 for <dispatch@ietf.org>; Fri, 14 Feb 2014 19:00:03 -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; Fri, 14 Feb 2014 19:00:10 -0800
From: Michael Hammer <michael.hammer@yaanatech.com>
To: "keith.drage@alcatel-lucent.com" <keith.drage@alcatel-lucent.com>, "kheimerl@cs.berkeley.edu" <kheimerl@cs.berkeley.edu>
Thread-Topic: [dispatch] SIP and GSM/UMTS with OpenBTS
Thread-Index: AQHPIj0OkF9riHfhQ0Se4gDBfVRQX5qmz3RggAAosQCAAAyAAIAAASOQgAC9HICAAALFAIAAAFCA//96B5CAAI2tgIAALnMAgAZ4WICAAOAQAIAACMEAgAAEaACAAAXeAIAAJYeAgAFsZwCAANo2FIABtI+AgAAqBQCAACCxgIAADyCAgAACJnGAAOhFAIAAKcuQgACWDICAAJQCgP//jmOg
Date: Sat, 15 Feb 2014 03:00:00 +0000
Message-ID: <00C069FD01E0324C9FFCADF539701DB3BBF2EF32@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> <93B4EA30-0734-439E-A129-B3B91B077720@rangenetworks.com> <949EF20990823C4C85C18D59AA11AD8B12F6C3@FR712WXCHMBA11.zeu.alcatel-lucent.com> <2B05935E-EB65-4B36-ABD3-09DE9921F8A7@westhawk.co.uk> <949EF20990823C4C85C18D59AA11AD8B12F7CE@FR712WXCHMBA11.zeu.alcatel-lucent.com> <949EF20990823C4C85C18D59AA11AD8B12FA06@FR712WXCHMBA11.zeu.alcatel-lucent.com> <DE4C1B56-0D67-4210-9FFA-EC0BC866E081@westhawk.co.uk> <201402121601.s1CG1q0W4835781@shell01.TheWorld.com> <39B5E4D390E9BD4890E2B3107900610112662068@ESESSMB301.ericsson.se> <017BBEA0-CDBE-453D-9E98-77F470BC9181@rangenetworks.com> <949EF20990823C4C85C18D59AA11AD8B1319E6@FR712WXCHMBA11.zeu.alcatel-lucent.com> <00b801cf28d0$3c39c000$b4ad4000$@schmid.xxx> <201402132328.s1DNS0U64926205@shell01.TheWorld.com> <CACyT-3=RKqvhGB-WLmWH0tGHCTEzH=Ej22sa+U-3vGN4AbTndg@mail.gmail.com> <00C069FD01E0324C9FFCADF539701DB3BBF2B24F@sc9-ex2k10mb1.corp.yaanatech.com> <CACyT-3=X5FZV8MTNHtNO7-zNyZt=90Jrsk7W6M1sOB+2VOXm9Q@mail.gmail.com> <949EF20990823C4C85C18D59AA11AD8B132F29@FR712WXCHMBA11.zeu.alcatel-lucent.com>
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B132F29@FR712WXCHMBA11.zeu.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.17.100.96]
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="SHA1"; boundary="----=_NextPart_000_03B3_01CF29CF.DB150270"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dispatch/183MdxbxmqTmG1C6rNg2xHYc1F4
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: Sat, 15 Feb 2014 03:00:10 -0000

Correct.  I was just suggesting the possibility of giving phones a direct
packet connection and then let them run a P2P app on top.

However, if this is for lame 2G feature phones, then that might not be
possible.

 

Michael Hammer

Principal Engineer

 <mailto:michael.hammer@yaanatech.com> michael.hammer@yaanatech.com

Mobile: +1 408-202-9291

500 Yosemite Drive Suite 120

Milpitas, CA 95035 USA

 

From: DRAGE, Keith (Keith) [mailto:keith.drage@alcatel-lucent.com] 
Sent: Friday, February 14, 2014 8:44 PM
To: Kurtis Heimerl; Michael Hammer
Cc: dispatch@ietf.org
Subject: RE: [dispatch] SIP and GSM/UMTS with OpenBTS

 

GPRS is not a control layer in the way I understand it - it is a mechanism
for providing IP transport, essentially the equivalent functionality of
mobile IP.

 

Keith

 

  _____  

From: dispatch [mailto:dispatch-bounces@ietf.org] On Behalf Of Kurtis
Heimerl
Sent: 14 February 2014 16:54
To: Michael Hammer
Cc: dispatch@ietf.org
Subject: Re: [dispatch] SIP and GSM/UMTS with OpenBTS

One could use GPRS as a control layer for SIP, but a key property here is
our ability to support existing phones, which couldn't use such a layer. 

 

On Sat, Feb 15, 2014 at 1:08 AM, Michael Hammer
<michael.hammer@yaanatech.com> wrote:

OK, let me add some protocol perspective.  Cut and paste courtesy of
Wikipedia:

****

The Um interface is the air interface
<http://en.wikipedia.org/wiki/Air_interface>  for the GSM
<http://en.wikipedia.org/wiki/GSM>  mobile telephone standard. It is the
interface between the mobile station
<http://en.wikipedia.org/wiki/Mobile_phone>  (MS) and the Base transceiver
station <http://en.wikipedia.org/wiki/Base_transceiver_station>  (BTS). It
is called Um because it is the mobile analog to the U interface
<http://en.wikipedia.org/wiki/U_interface>  of ISDN
<http://en.wikipedia.org/wiki/ISDN> . Um is defined in the GSM 04.xx and
05.xx series of specifications. Um can also support GPRS
<http://en.wikipedia.org/wiki/GPRS>  packet-oriented communication.

Um layers[edit
<http://en.wikipedia.org/w/index.php?title=Um_interface&action=edit&section=
1> ]

The layers of GSM are initially defined in GSM 04.01 Section 7 and roughly
follow the OSI model <http://en.wikipedia.org/wiki/OSI_model> . Um is
defined in the lower three layers of the model.


Network Layer (L3)[edit
<http://en.wikipedia.org/w/index.php?title=Um_interface&action=edit&section=
7> ]


The Um network layer <http://en.wikipedia.org/wiki/Network_layer>  is
defined in GSM 04.07 and 04.08 and has three sublayers. A subscriber
terminal must establish a connection in each sublayer before accessing the
next higher sublayer.

1.	Radio Resource
<http://en.wikipedia.org/wiki/Radio_Resource_Management>  (RR). This
sublayer manages the assignment and release of logical channels on the radio
link. It is normally terminated in the BSC
<http://en.wikipedia.org/wiki/Base_station_controller> . 
2.	Mobility Management
<http://en.wikipedia.org/wiki/Mobility_management>  (MM). This sublayer
authenticates users and tracks their movements from cell to cell. It is
normally terminated in the VLR
<http://en.wikipedia.org/wiki/GSM_core_network#Visitor_Location_Register>
or HLR
<http://en.wikipedia.org/wiki/GSM_core_network#Home_Location_Register> . 
3.	Call Control <http://en.wikipedia.org/wiki/Call_control>  (CC). This
sublayer connects telephone calls and is taken directly from ITU-T Q.931
<http://en.wikipedia.org/wiki/Q.931> . GSM 04.08 Annex E provides a table of
corresponding paragraphs in GSM 04.08 and ITU-T Q.931 along with a summary
of differences between the two. The CC sublayer is terminated in the MSC
<http://en.wikipedia.org/wiki/Mobile_switching_centre_server> . 

The access order is RR, MM, CC. The release order is the reverse of that. 

Note that none of these sublayers terminate in the BTS itself. The standard
GSM BTS operates only in layers 1 and 2.

***

So, the implementation appears to move the MSC to the BTS, along with a
Q.931 to SIP GW, such as:

ETSI TS 183 036 V3.4.1 (2011-02) Telecommunications and Internet converged
Services and Protocols for Advanced Networking (TISPAN);

ISDN/SIP interworking; Protocol specification

 

Not sure how that saves battery, but that is an implementation question we
don't need to answer.

 

Note also that since Um supports GPRS, could the BTS not also support a
packet relay for higher layer P2P SIP call control?

 

Just asking.

 

Michael Hammer

Principal Engineer

michael.hammer@yaanatech.com

Mobile: +1 408-202-9291

500 Yosemite Drive Suite 120

Milpitas, CA 95035 USA

 

From: dispatch [mailto:dispatch-bounces@ietf.org] On Behalf Of Kurtis
Heimerl
Sent: Friday, February 14, 2014 12:27 AM
To: Dale R. Worley


Cc: dispatch@ietf.org
Subject: Re: [dispatch] SIP and GSM/UMTS with OpenBTS

 

OpenBTS is an instance of an Um->SIP gateway. After this implementation,
we've become aware that a broader view of the relative correctness of our
design would be valuable...  and that's why this thread exists. We'd like
the IETF to help standardize this gateway model and make sure that the
decisions that were made are reasonable, scalable, and intelligent. 

 

At least that's my perception on why we're here. Jim may have another. 

 

On Fri, Feb 14, 2014 at 8:28 AM, Dale R. Worley <worley@ariadne.com> wrote:

> From: "Ralph A. Schmid, dk5ras" <ralph@schmid.xxx>

(Is there a reason you insert so many blank lines?)


> So imagine a village, a few hundred people living there, most of
> them owning mobile phones for communication when they travel to the
> town for work or for trading goods - but at home those phones are
> useless.

> So somebody is able to spent a few thousand dollars, puts an antenna
> onto some tree, flips the switch, and a few hundred phones can (and
> do) log on.

> Now more and more of those low-cost networks grow up, and people
> want to connect them. Internet is available in some places, cheap to
> buy and install WiFi-links are established, the whole thing evolves,
> some simple structure grows.

This story makes sense to me.  The question seems to be how to
interwork the GSM radio call-control protocol with SIP, so that a set
of these base stations can operate as an integrated system.  You'd
want some sort of SIP registrar/proxy to operate as an ITSP, and all
of the base stations make SIP connections with it.

The next step is for someone to start designing this use of SIP.  No
doubt a lot of interesting questions will arise, and you may need to
design some SIP extensions.  But until you've got the design started
and can discuss the design decisions, you're not in a position to talk
about what SIP extensions are needed.

Dale


_______________________________________________
dispatch mailing list
dispatch@ietf.org
https://www.ietf.org/mailman/listinfo/dispatch