IETF Logo Mail Archive

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

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Mon, 10 February 2014 18:43 UTC

Return-Path: <keith.drage@alcatel-lucent.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 74E271A07FC for <dispatch@ietfa.amsl.com>; Mon, 10 Feb 2014 10:43:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] 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 Jyolm9-wbNxD for <dispatch@ietfa.amsl.com>; Mon, 10 Feb 2014 10:43:51 -0800 (PST)
Received: from hoemail2.alcatel.com (hoemail2.alcatel.com [192.160.6.149]) by ietfa.amsl.com (Postfix) with ESMTP id 03C5B1A055A for <dispatch@ietf.org>; Mon, 10 Feb 2014 10:43:50 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by hoemail2.alcatel.com (8.13.8/IER-o) with ESMTP id s1AIhml2004592 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 10 Feb 2014 12:43:49 -0600 (CST)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s1AIhlVl013287 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 10 Feb 2014 19:43:47 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.26]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Mon, 10 Feb 2014 19:43:47 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Tim Panton new <thp@westhawk.co.uk>
Thread-Topic: [dispatch] SIP and GSM/UMTS with OpenBTS
Thread-Index: AQHPIj0OkF9riHfhQ0Se4gDBfVRQX5qmz3RggAAosQCAAAyAAIAAASOQgAA3AICAAALFAIAAAFCAgAAAZICAAAdQgIAALnKAgAZ4SwCAAJlyIIAAPqkAgAASvbA=
Date: Mon, 10 Feb 2014 18:43:46 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B12F7CE@FR712WXCHMBA11.zeu.alcatel-lucent.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>
In-Reply-To: <2B05935E-EB65-4B36-ABD3-09DE9921F8A7@westhawk.co.uk>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.41]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
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: Mon, 10 Feb 2014 18:43:53 -0000

I am not assuming a specific solution - what we are all trying to find out is how much of 3GPP GERAN is actually being used, and what identities relate to what.

So you will have a UICC - because it is a 3GPP GERAN access network, but will not have any roaming that relates to the UICC, or the identities on that UICC.

But as far as I can see from the architecture given, the service is limited to a single BTS. That means that (for the solution you identify below) an operator with multiple BTSs will assign their users to a single BTS and the collation of charging/accounting will have to be from each individual BTS, back to some central entity (not shown). 

You will not be running the 3GPP mobility management protocols between BTS.

Keith Drage

 

> -----Original Message-----
> From: Tim Panton new [mailto:thp@westhawk.co.uk] 
> Sent: 10 February 2014 18:28
> To: DRAGE, Keith (Keith)
> Cc: Jim Forster; Mary Barnes; dispatch@ietf.org
> Subject: Re: [dispatch] SIP and GSM/UMTS with OpenBTS
> 
> 
> On 10 Feb 2014, at 17:56, DRAGE, Keith (Keith) 
> <keith.drage@alcatel-lucent.com> wrote:
> 
> > If I follow this diagram correctly, you claim to have 
> collapsed the HLR into your BTS. Your BTS apparently have no 
> communication shown with each other. This means you each 
> subscriber is limited to a single BTS with no roaming between them.
> 
> I think you are assuming a specific solution to a specific problem. 
> Many ITSPs allow SIP  registrations to a DID/account to come 
> from dynamic IPs. So the necessary 'communication' can be 
> implemented via the ITSP's normal functions. So when a user 
> moves from the BTS in village A to the BTS  in village B 
> their DID travels with them.
> 
> Sure you wouldn't get the ability for an arbitrary GSM SIM to 
> roam into the network and be billed to their home network. 
> 
> But realistically that sort of roaming isn't really a 
> technical problem, it is predominantly a legal/commercial one.
> 
> Tim.

v2.23.0 | Report a Bug | By Email