Users Manual

ALL

EFFECTIVITY

Page 5-37

22 Apr 2019

23-15-49

SYSTEM DESCRIPTION, INSTALLATION, AND MAINTENANCE MANUAL

ASPIRE-400

(e) Spot beam ID for the spot beams listed on the global beam common channel.

(f) Position (latitude, longitude) of the vertices for each spot beam listed on the

global beam common channel to 1-degree resolution.

(g) UTC Network time.

(h) Context IDs in use.

(i) USIM status.

(j) Stack State.

(k) PS session byte/packet counters.

(l) Demodulator signal condition.

(m) Call status reports.

B. Safety Channel Card Management (Side A)

(1) Only the ACD can request creation or deletion of PDP Contexts on the Safety Channel

Card. It does so for both the contexts needed by ACD and those needed by the AISD.

(2) The SDU prevents any direct control of PDP context activation from the AIS domain. Only

those contexts permitted by the Secure ORT will be activated by the ACD.

(3) Primary PDP Contexts are each mapped to its own TPTOE session (a proprietary

protocol).

(4) Secondary PDP Contexts are embedded within their parent Primary PDP.

(5) Control of Circuit switched voice is over a separate Serial Voice control link.

(6) When ORT enabled, the ACD enables outbound caller ID on the Safety Channel Card.

(7) The ACD processor enables Tunneled PPP Transport over Ethernet (TPToE) on the

Safety Channel Card via BCL over the serial control interface, specifying the TPToE ACD

destination address.

(8) The ACD processor sends the following configuration information related to Satellite

operation to the Safety Channel Card:

(a) GSM UE Access Class 14 activation

(b) Support of extended L-band.

(9) The ACD:

(a) Permits IP Header Compression on a per context basis for the AISD.

(b) Provides access to the following safety channel cards spontaneous reports the

SB-Safety CS Supplementary service status.

C. Non-Safety Channel Card Management (Side B)

(1) The ACD has a serial control path to the non-safety Channel Card for:

(a) Initial configuration

(b) Bite management

NOTE: Specific context establishment and service configuration is under the

control of the APP.

DRAFT

3rd rvw Draft as of:

29 January, 2020