Return-Path: <ovmsdev-bounces@lists.teslaclub.hk>
Received: from network-box.com ([unix socket])
	 by nbmailhq5 (Cyrus v2.3.16-Fedora-RPM-2.3.16-6_3.nb5.0.1) with LMTPA;
	 Tue, 20 Aug 2013 21:04:27 +0800
X-Sieve: CMU Sieve 2.3
Received: from nbmailhk1.network-box.com (unknown [10.8.18.9])
	by network-box.com (Postfix) with ESMTP id 67FAF210004B
	for <mark.johnson@network-box.com>; Tue, 20 Aug 2013 21:04:27 +0800 (HKT)
Received: from nbmailscanhq1.network-box.com (unknown [10.12.18.180])
	by nbmailhk1.network-box.com (Postfix) with ESMTP id 851877817D
	for <mark@webb-johnson.net>; Tue, 20 Aug 2013 21:04:28 +0800 (HKT)
Received: (qmail 5062 invoked from network); 20 Aug 2013 13:04:27 -0000
X-NetworkBox-HamSign: 0101;OUT;nbmailscanhq1;b1510a9b2a2cd88fa8a0dba6ef0a0530;
Received: from unknown (HELO markhk2.network-box.com) (10.12.18.80)
  by 10.12.18.180 with SMTP; 20 Aug 2013 13:04:27 -0000
Received: from [127.0.0.1] (markhk2 [127.0.0.1])
	by markhk2.network-box.com (Postfix) with ESMTP id 4055280052;
	Tue, 20 Aug 2013 21:04:27 +0800 (HKT)
X-Original-To: ovmsdev@lists.teslaclub.hk
Delivered-To: ovmsdev@lists.teslaclub.hk
Received: from nbmailscanhq1.network-box.com (unknown [10.12.18.180])
	by markhk2.network-box.com (Postfix) with ESMTP id E31DC80052
	for <ovmsdev@lists.teslaclub.hk>; Tue, 20 Aug 2013 21:04:25 +0800 (HKT)
Received: (qmail 5038 invoked from network); 20 Aug 2013 13:04:25 -0000
X-NetworkBox-HamSign: 0101; OUT; nbmailscanhq1;
	1dd99a9ad63352f14d24c03fbc8c7c66;
Received: from n219077002068.netvigator.com (HELO ?10.10.40.209?)
 (219.77.2.68)
	by 10.12.18.180 with ESMTPS (AES128-SHA encrypted);
	20 Aug 2013 13:04:25 -0000
From: Mark Webb-Johnson <mark@webb-johnson.net>
Message-Id: <2D6B1263-282D-4C24-AECD-A05AB4B28BAF@webb-johnson.net>
Date: Tue, 20 Aug 2013 21:04:06 +0800
To: OVMS Developers <ovmsdev@lists.teslaclub.hk>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
X-NetworkBox-BounceSign-nbhqhk: 0101;15937;61590dc1
X-Scanned-By-nbmailscanhq1: Virus scan performed by network-box
X-Scanned-By-nbmailscanhq1: Scanner file id is
	nbmailscanhq1-1377003865.252-5035-000
X-Scanned-By-nbmailscanhq1: No known viruses found in message
	(received+scanned in 0.07/0.07 secs)
X-Scanned-By-nbmailscanhq1: Spam-Check-Result: No,
	hits=0 required=7 tests= autolearn=no version=2.0
X-Spam-Status: No
Subject: [Ovmsdev] USSD Signaling
X-BeenThere: ovmsdev@lists.teslaclub.hk
X-Mailman-Version: 2.1.11
Precedence: list
Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk>
List-Id: OVMS Developers <ovmsdev.lists.teslaclub.hk>
List-Unsubscribe: <http://lists.teslaclub.hk/mailman/options/ovmsdev>,
	<mailto:ovmsdev-request@lists.teslaclub.hk?subject=unsubscribe>
List-Archive: <http://lists.teslaclub.hk/pipermail/ovmsdev>
List-Post: <mailto:ovmsdev@lists.teslaclub.hk>
List-Help: <mailto:ovmsdev-request@lists.teslaclub.hk?subject=help>
List-Subscribe: <http://lists.teslaclub.hk/mailman/listinfo/ovmsdev>,
	<mailto:ovmsdev-request@lists.teslaclub.hk?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0263373885592890735=="
Sender: ovmsdev-bounces@lists.teslaclub.hk
Errors-To: ovmsdev-bounces@lists.teslaclub.hk
X-NetworkBox-BounceSign-nbhqhk: 0101;15937;61590dc1
X-Scanned-By-nbmailscanhq1: Virus scan performed by network-box
X-Scanned-By-nbmailscanhq1: Scanner file id is
 nbmailscanhq1-1377003867.190-5047-000
X-Scanned-By-nbmailscanhq1: No known viruses found in message
 (received+scanned in 0.12/0.12 secs)
X-Scanned-By-nbmailscanhq1: Spam-Check-Result: No,
 hits=0 required=7 tests= autolearn=no version=2.0


--===============0263373885592890735==
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_0D489842-02B8-4563-B30F-BD723DD9DF17"


--Apple-Mail=_0D489842-02B8-4563-B30F-BD723DD9DF17
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


I've had a proposal from a M2M provider that is interesting, so thought =
I'd distribute it here, and get feedback.

A very low-level protocol in the GSM standard is called USSD. It =
involves the transmission of a single alpha-numeric message of up to =
about 120 characters. Our protocol messages would fit perfectly into it. =
The USSD protocol is routed at a very low level, and is a datagram-syle =
protocol (it may be discarded by the network if there is no cellular =
connectivity, kind of like UDP). The protocol is supposedly better able =
to make it through congested and low-signal areas than even SMS, and =
certainly much better than GPRS. Message transit times are faster than =
SMS at around 1 second (of course, depending on cellular coverage).

The interesting things about the protocol are than (a) it is free (or =
flat-rate, at least), and (b) it supports roaming. One SIM, flat rate, =
globally.

The M2M provider suggests that we buy SIMs from them with unlimited USSD =
plans. Once activated, the SIMs would work globally on hundreds of =
partner carriers, and would only support USSD (not SMS or GPRS data). =
The way it would work for OVMS would  be:

Every OVMS module would be provided with a USSD SIM already onboard. It =
would work globally.
The owner would go to the www.openvehicles.com website and create a =
vehicle record as normal, but also enter the serial number of the SIM.
When the OVMS module powers on, it would read the serial number from the =
SIM then send a single USSD message to us to request provisioning =
(vehicleid, server password, etc).
The OVMS server would send back a USSD message to provision the module =
in the car.
=46rom then onwards, USSD messages would be used to encapsulate our =
current OVMS protocol messages.
The USSD messages are bi-directionally gatewayed to the OVMS server via =
the M2M provider, over the Internet.
There would need to be some small changes to the encryption protocol we =
use.
The OVMS firmware could support this as a special operation mode - based =
on the prefix of the SIM inserted. So, it could work in normal SMS/GPRS =
mode as well as USSD mode (switched by the SIM in the module).

Cost wise, this would increase the cost of the module by less than US$10 =
(price of the SIM). A monthly flat-rate "unlimited" USSD plan would be =
around US$8-US$10 per month.

What do people think?

Regards, Mark


--Apple-Mail=_0D489842-02B8-4563-B30F-BD723DD9DF17
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><br></div><div>I've had a proposal from a M2M provider that is =
interesting, so thought I'd distribute it here, and get =
feedback.</div><div><br></div><div>A very low-level protocol in the GSM =
standard is called USSD. It involves the transmission of a single =
alpha-numeric message of up to about 120 characters. Our protocol =
messages would fit perfectly into it. The USSD protocol is routed at a =
very low level, and is a datagram-syle protocol (it may be discarded by =
the network if there is no cellular connectivity, kind of like =
UDP).&nbsp;The protocol is supposedly better able to make it through =
congested and low-signal areas than even SMS, and certainly much better =
than GPRS. Message transit times are faster than SMS at around 1 second =
(of course, depending on cellular =
coverage).</div><div><br></div><div>The interesting things about the =
protocol are than (a) it is free (or flat-rate, at least), and (b) it =
supports roaming. One SIM, flat rate, =
globally.</div><div><br></div><div>The M2M provider suggests that we buy =
SIMs from them with unlimited USSD plans. Once activated, the SIMs would =
work globally on hundreds of partner carriers, and would only support =
USSD (not SMS or GPRS data). The way it would work for OVMS would =
&nbsp;be:</div><div><br></div><div><ol class=3D"MailOutline"><li>Every =
OVMS module would be provided with a USSD SIM already onboard. It would =
work globally.</li><li>The owner would go to the <a =
href=3D"http://www.openvehicles.com">www.openvehicles.com</a> website =
and create a vehicle record as normal, but also enter the serial number =
of the SIM.</li><li>When the OVMS module powers on, it would read the =
serial number from the SIM then send a single USSD message to us to =
request provisioning (vehicleid, server password, etc).</li><li>The OVMS =
server would send back a USSD message to provision the module in the =
car.</li><li>=46rom then onwards, USSD messages would be used to =
encapsulate our current OVMS protocol messages.</li><li>The USSD =
messages are bi-directionally gatewayed to the OVMS server via the M2M =
provider, over the Internet.</li><li>There would need to be some small =
changes to the encryption protocol we use.</li><li>The OVMS firmware =
could support this as a special operation mode - based on the prefix of =
the SIM inserted. So, it could work in normal SMS/GPRS mode as well as =
USSD mode (switched by the SIM in the =
module).</li></ol></div><div><br></div><div>Cost wise, this would =
increase the cost of the module by less than US$10 (price of the SIM). A =
monthly flat-rate "unlimited" USSD plan would be around US$8-US$10 per =
month.</div><div><br></div><div>What do people =
think?</div><div><br></div><div>Regards, =
Mark</div><div><br></div></body></html>=

--Apple-Mail=_0D489842-02B8-4563-B30F-BD723DD9DF17--

--===============0263373885592890735==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
OvmsDev mailing list
OvmsDev@lists.teslaclub.hk
http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

--===============0263373885592890735==--
