OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRDIG   03.02.03 10:04l 316 Lines 9325 Bytes #999 (0) @ WW
BID : 818-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jan 29, 5/6
Path: DB0FHN<DB0RGB<OK0PPL<RZ6HXA<SP7MGD<VK7AX<ZL2BAU<ZL3VML
Sent: 030202/0911Z @:ZL3VML.#80.NZL.OC #:58660 [Chch-NZ] FBB7.00i $:818-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To  : APRDIG@WW

Subject: APRS-IS Sysops - Potential Bottleneck Identified - Part 2
From: "AE5PL Lists" <HamLists@ametx.com>
Date: Wed, 29 Jan 2003 20:31:05 -0600
X-Message-Number: 34

You might be saying, "Ok, what does this have to do with my server?"
Throttling is a very common practice with businesses, universities, and
ISP's.  They use it to "protect" the pipe going into the Internet from
any one user or customer monopolizing the bandwidth.  If you have a
cable modem and the provider says "128k guaranteed into the Internet, 1m
from the Internet", you can rest assured that some throttling mechanism
is in place.  DSL tends to be a little less subject to throttling
because they can configure the DSL "modem" to physically operate at the
"guaranteed" speed instead of using throttling.  If you are using
"donated" bandwidth at a university or business, it is quite possible
that they are using some form of throttling which you should become
familiar with.

With an average bandwidth utilization of 10k per connection on a full
APRS-IS feed, 10 of these connections will fill (and, due to inherent
protocol overhead, probably exceed) a 128k pipe.  And once throttling
begins to occur, its effect on the APRS-IS data stream appears to
increase exponentially.  If you are an APRS-IS sysop, I am asking that
you look at your pipe to the Internet and determine if your connection
is running at or near the maximum bandwidth allowed.  If you are, please
restrict connections until you fall well under where throttling or
maximum bandwidth utilization will occur.  If your server is pushing the
limit in relation to throttling or bandwidth on your connection with the
Internet (look at both directions), your server may be contributing to
the degradation of data integrity on APRS-IS.

For more information on the effects of throttling and/or running at
maximum bandwidth, please email me at pete@ae5pl.net.  I will be glad to
go into further detail regarding the TCP/IP protocol, but I am not sure
it would be a relevant discussion for this sig.

73,

Pete Loveall AE5PL
pete@ae5pl.net

----------------------------------------------------------------------

Subject: RE: New spec - working notes
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Thu, 30 Jan 2003 02:33:46 -0000
X-Message-Number: 35

Significant update, see simple scenario at the bottom for an overview of how
this should work.  I especially need input from backbone types on
implementing heard-by lists and such.


N1VG format working notes

Message Header Format

bits: 1        7         8          8
-------------------------------------------------------------
| ext_flag | length | msg_type | ext_type | message body... |
-------------------------------------------------------------


ext_flag - A '1' in this field indicates a 16-bit message ID.
length - Length of message, inclusive of message ID.
msg_type - The message ID if ext_flag = 0, otherwise the low byte of the
message ID
ext_type - High byte of message ID.  Only present if ext_flag = 1.

This message type scheme allows for 65,792 message types (256 standard and
65,536 extended).
8-bit message IDs are reserved for common, standard messages.  16-bit IDs
are used for less-frequently used messages and experimental message types.

0-byte messages are supported for instances where the presence
of the message type alone conveys the required information.

No CRC is included, as a reliable transport layer is assumed.

All numbers are little-endian.  Signed integers use two's complement
notation.

---

MSG #00 - Message Group Sequence

[Sequence] 16 bits

The message group sequence optionally associates multiple message parts with
a single sequence number.  The sequence number starts at 1 and is
incremented each time the originating station has new information to
transmit.  A message group may not contain more than one of the same message
type unless otherwise noted.  If a datagram-oriented transport is used,
message groups may be split across datagrams, but each datagram must carry
the Message Group Sequence message.

---

MSG #01 - Originating Station

[Callsign] 6 bytes
[SSID] 8 bits
[Sequence] 16 bits
[Network] 8 bits

This message type is intended to prefix messages which originated with other
stations.  Messages may be collected and grouped together for transmission
by a digipeater using this mechanism, or it may be used to identify messages
when carried over a backbone network.  In the case of a stream-oriented
transport such as TCP, all following messages are assumed to originate at
the specified station until another Originating Station identification
message is received.  For datagram-oriented transports like unconnected
AX.25 and UDP, the scope of the identification message extends only to the
end of the underlying datagram.

A Message Group Sequence may follow an Originating Station message to
indicate the start of a new message sequence.  The callsign, SSID, and
originating network values are carried over to the new message group.  This
may be used for transmitting a multiple-sequence history for a given
station.

If the originating station did not provide a sequence number, the sequence
field is set to null (ASCII 0).

Callsign - The originating station's callsign, right-padded with nulls
(ASCII 0).
SSID - The SSID of the originating station.
Sequence - See Message Group Sequence.  A sequence of 0 indicates no
associated group.
Network - Identification of the originating network.

Currently defined network IDs:

00 - Primary VHF channel (144.39 in the US)
01 - APRS-IS backbone
02 - UHF backbone

// More input on this?


---

MSG #02 - Path Trace

[Callsign] 6 bytes 
[SSID] 8 bits
<repeated 0 or more times>

To request a path trace, a station may include an empty Path Trace message.
Any station the message passes through should add its own callsign and SSID
to the Path Trace message.  A Path Trace may be added by any station along
the path, whether the originating station requested it or not.


Example:

01 05 (Request a path trace)

---

MSG #03 - Heard-By List

[Network] 8 bits
<repeated 0 or more times>

A station receiving a message from another network must add the receiving
network's ID to the list.  This message type should only be present in
message groups that have passed through a network gateway.


MSG #04 - Position

[Latitude] 32 bits
[Longitude] 32 bits
[Alititude] 24 bits

Positions reference the WGS84 datum using decimal degrees.  Coordinates are
represented by 32-bit unsigned integers as follows:

Integer longitude = (longitude + 180) * 2^23
Integer latitude = (latitude + 90) * 2^24


Altitude is in centimeters above WGS84 ellipsoid, stored as a 24-bit signed
integer.


Example:

0C 01 06 81 F5 7C 5E BA C9 1D 7C 47 00 (34.959 N, 120.424 W, 183.0 meters)

---

MSG #05 - Timestamp

[Time] 32 bits

Times are in seconds elapsed since 1 Jan 1970 00:00:00.0 UTC (UNIX format).


Example:

05 02 6E 3E 38 3E (Wed, 29 Jan 2003 20:49:50 UTC)

---

MSG #06 - Freeform Comment

[Text] Up to 126 characters, not zero-delimited

The purpose of the comment is to provide a free-form text field associated
with the originating station.


Example:

05 03 41 42 43 44 (ABCD)

---

MSG #07 - Course and Speed

[Course] 16 bits (degrees)
[Speed] 16 bits (cm/sec)

Speeds are in centimeters per second.  Course is in degrees relative to true
north.


Example:

05 04 C3 00 AE 08 (195 degrees at 80 km/hr)

--

MSG #xx - Satellite Keplerian element

[Sat ID] 24 bits (NORAD catalog number)
[Epoch time] 64 bits (double float)
[ndot] 32 bits - ndot/2 drag parameter (single float)
[nddot] 32 bits - n double dot/6 drag parameter (single float)
[bstar] 32 bits - Bstar drag parameter (single float)
[elset] 16 bits - Element set number
[inclination] 32 bits - orbital inclination (single float)
[ra] 32 bits - Right ascension (single float)
[eccentricity] 32 bits - orbital eccentricity (single float)
[aop] 32 bits - argument of perigee (single float)
[ma] 32 bits - mean anomaly (single float)
[mm] 64 bits - mean motion (double float)
[rev] 16 bits - revolution number

All values are the same as those in standard NORAD TLEs, taking into account
implied decimals and exponents.


Example Scenario:

Tracker X1AA -> VHF:
 Position
 Timestamp
 Course/Speed
 Trace Path

Tracker X2AB -> VHF:
 Sequence 45
 Position
 Timestamp
 Weather
 
Digipeater D1AA -> VHF:
 Originating Station X1AA Sequence 0 Network 0:
 Position
 Timestamp
 Course/Speed
 Trace Path: D1AA
 Originating Station X2AB Sequence 45 Network 0:
 Position
 Timestamp
 Weather

IGATE G1ATE -> APRS-IS:
 Originating Station X1AA Sequence 0 Network 0:
 Position
 Timestamp
 Course/Speed
 Trace Path: D1AA G1ATE // (do we need network IDs here?)
 Heard-By: 01 // (ok, maybe we only need to put this on outbound gateways)
 Originating Station X2AB Sequence 45 Netowrk 0:
 Position
 Timestamp
 Weather
 Heard-By: 01
 




Errata
------

----------------------------------------------------------------------

Subject: Re: APRS-IS Sysops - Potential Bottleneck Identified - Part 2
From: "Pat Karp" <pkarp@conwaycorp.net>
Date: Wed, 29 Jan 2003 20:53:19 -0600
X-Message-Number: 36

Thanks Pete.
    Very interesting stuff!

----------------------------------------------------------------------



Read previous mail | Read next mail


 16.11.2026 14:19:54lGo back Go up