曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
packets in transit on the connection. The maximum connection of the SNS users, an IS0 8208 DCE entity in the satellite
relcare &lay is the standard s ~ d s~cificationfo r sub.etwa* Eceives ISO 8208 CALL REQUEST picket
the connection release phase; it is not intended to limit in any fmm the ISO 8208 .Thiis is fomarded to ths IWP.
way the future use of optional facilities, user data fields, or The IWF fornards this packet to UK BPPmP~ateS SNDPX address fields. entity. This SSNDPX entity forwards this packet as a
7.2.3 RELIABILIOTFY S ERVICE
7.2.3.1 Reliability of service is determined by the system
architecture, by the physical layer bit error rate, and by the
average rate of "collisions" on R channels. There is no
specification on the rate of R channel collisions. However, the
system performance specifications for both speed of service
and reliability of service are based on an average R channel
occupancy factor (i.e. the ratio of occupied R channel slots to
the total number of R channel slots during a given interval) of
approximately 0.15. Higher R channel occupancies are
permitted, provided that all of the applicable performance
standards are met.
7.2.3.2 The standard reliability of service parameter for
the transfer of a single DATA packet is residual error
probability, which is the probability that an attempt to
transfer a single DATA packet is not entirely successful. It is
based on a standard reference DATA packet containing
128 octets of subnetwork user data. The undetected error
probability for AMSS packet data service is expected to be
less than 3 x 1C7 for standard reference DATA packets
CONNECTION REQUEST SNPDU to the remote SSNDPX.
When the remote SSNDPX receives this SNPDU, it forwards
this to the IWF as an IS0 8208 INCOMING CALL packet.
The IWF forwards this packet to the appropriate IS0 8208
DCE entity. The IS0 8208 DCE entity forwards this packet to
the peer IS0 8208 DTE entity. The IS0 8208 DTE forwards
this connection request to the receiving SNS user. After the
receiving SNS user has accepted this connection request, the
IS0 8208 DTE entity forwards an IS0 8208 CALL
ACCEPTED packet to the peer IS0 8208 DCE entity. The IS0
8208 DCE entity forwards this packet to the IWF. The IWF
forwards this packet to the appropriate SSNDPX entity. This
SSNDPX entity forwards this packet as a CONNECTION
CONFIRM SNPDU to the peer SSNDPX entity. When the
remote SSNDPX entity receives this SNPDU, it forwards this
as an ISO 8208 CALL CONNECTED pack1 to the The
IWF forwards this packet to the appropriate IS0 8208 DCE
entity. This IS0 8208 DCE entity forwards this packet to the
peer IS0 8208 DTE entity. When the IS0 8208 DTE entity
receives this packet, it informs the originating SNS user about
the establishment of a connection to the remote SNS user.
7.3.2.3 A connection between two SNS users consists of
a series of logical channels. Each logical channel is selected
Annex 10 - Aeronautical Telecommun3eadons volume zzz
based on the established rule by the receiving entity.
Therefore, these logical channels may not have the same
number. Figure A-17 of this guidance material shows an
example of connection establishment between three pairs of
SNS users.
7.3.2.4 Throughput negotiation
Since the GES has the knowledge of available throughput
based on the throughputs that have been assigned to the
existing subnetwork connections (SNCs), it should assign the
throughput classes for each direction of data transmission. The
recommended actions by the GHS ge given in 7.3.6.1 and
7.3.7.1 of this guidance material.
7.3.3 CONNECTIONRE LEASE
7.3.3.1 SSNDPX
To avoid unnecessary releases at the SSM)PG caused by
residual DATA/IN'TERRUPT SNPDUs from the SSNDPA, the
SSNDPA waits until all DAT-UPT SNPDUs in
transmission and pertaining to that connection have been
transmitted before forwarding a CONNECTION RELEASED
or a CONNECTION RELEASE COMPLETE SNPDU to the
7.3.4.3 Flow control procedure
7.3.4.3.1 Memory management mechanisms are
implementation dependent. In order to minimize the possibility
of memory overnow and the consequent loss of data, the
satellite subnetwork layer provides flow control, which may be
invoked by the AES, the GES, or the subnetwork user. The
SSNDPX uses start-stop flow control, while the DCE uses IS0
8208 window flow control. IS0 8208 RECEIVE READY and
RECEIVE NOT READY packets are produced locally; they
are never transferred across the subnetwork. If the SSNDPX
remains in the "flow control not ready" state for 60 seconds,
the subnetwork initiates a reset of the connection, regardless of
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
附件10--航空电信an10_v3_1ed_amend_75(142)
