hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
68dab94c69ac1bd0d619783f6f2664bc | 102 721-2 | 1 Scope | The present document specifies the S-MIM (S-band Mobile Interactive Multimedia) system in which a standardized S-band satellite mobile broadcast system is complemented by the addition of a return channel. The present document is part 2 of the multi-part deliverable and concerns the requirements for a forward link radio... |
68dab94c69ac1bd0d619783f6f2664bc | 102 721-2 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
68dab94c69ac1bd0d619783f6f2664bc | 102 721-2 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 102 721-1: "Satellite Earth Stations and Systems (SES); Air Interface for S-band Mobile Interactive Multimedia (S-MIM); Part 1: General System Architecture and Configurations". [2] ETSI TS 102 721-5: "Satellite Ear... |
68dab94c69ac1bd0d619783f6f2664bc | 102 721-2 | 2.1 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TS 102 584: "Digital Video Broadcasting (DVB); DVB-SH Implementation Guidelines". [i.2] ETSI EN 302 550 (all parts and sub-parts): "Satellite Ear... |
68dab94c69ac1bd0d619783f6f2664bc | 102 721-2 | 3 Definitions and abbreviations | |
68dab94c69ac1bd0d619783f6f2664bc | 102 721-2 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: 2 GHz MSS band: 1 980 MHz to 2 010 MHz (earth-to-space) and 2 170 MHz to 2 200 MHz (space-to-earth) frequency bands NOTE: These paired bands are assigned to MSS. architecture: abstract representation of a communications system NOTE: Th... |
68dab94c69ac1bd0d619783f6f2664bc | 102 721-2 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACK Acknowledgement APSK Amplitude and Phase Shift Keying BCH Broadcast Channel CCH Common Channel CGC Complementary Ground Component CU Channel Unit DCH Dedicated Channel DVB-SH Digital Video Broadcasting, Satellites services to Handhelds EIR... |
68dab94c69ac1bd0d619783f6f2664bc | 102 721-2 | 4 General Description | The Forward Link S-MIM protocol stack for access to SS1, SS2 and SS3 services is depicted in Figure 4.1. ETSI ETSI TS 102 721-2 V1.2.1 (2013-08) 8 USER PLANE MANAGEMENT PLANE CONTROL PLANE Coding, Modulation & Transmission Header Compression Encryption (LL) MPE Encapsulation & Addressing PHY Link Layer nrt-CCH UCC BCC ... |
68dab94c69ac1bd0d619783f6f2664bc | 102 721-2 | 4.1 Physical Layer | Several transport channels are provided in the Forward Link: • rt-DCH: real time Dedicated Channel. It shall be reserved to flows that correspond to services under SS3. • rt-CCH: real time Common Channel. It shall be reserved to unicast flows corresponding to SS1 and SS2 with real-time requirements. • nrt-CCH: non-real... |
68dab94c69ac1bd0d619783f6f2664bc | 102 721-2 | 5 Forward Link Radio Interface Requirements | |
68dab94c69ac1bd0d619783f6f2664bc | 102 721-2 | 5.1 Service Requirements | |
68dab94c69ac1bd0d619783f6f2664bc | 102 721-2 | 5.1.1 Service Segment 1 | Req-SR-10 The S-MIM system shall provide a radio interface in the forward link that addresses the services grouped under Service Segment 1 in TS 102 721-1 [1] for mobile terminals. Req-SR-20 This forward link radio interface shall comply with requirements of broadcast and interactive mobile services described in Table ... |
68dab94c69ac1bd0d619783f6f2664bc | 102 721-2 | 5.1.2 Service Segment 2 | Req-SR-30 The S-MIM system shall provide a radio interface in the forward link that addresses the services grouped under Service Segment 2 in TS 102 721-1 [1] for mobile terminals. Req-SR-40 This forward link radio interface shall comply with requirements of data acquisition mobile services described in Table 5.2. Tabl... |
68dab94c69ac1bd0d619783f6f2664bc | 102 721-2 | 5.1.3 Service Segment 3 | Req-SR-50 The S-MIM system shall provide a radio interface in the forward link that addresses the services grouped under Service Segment 3 in TS 102 721-1 [1]. Req-SR-60 This forward link radio interface shall comply with requirements of real-time (emergency) services described in Table 5.3. Table 5.3: Service Requirem... |
68dab94c69ac1bd0d619783f6f2664bc | 102 721-2 | 5.1.4 Signalling | Req-SR-70 The S-MIM system shall provide a radio interface in the forward link able to transport the S-MIM signalling tables defined in [3]. Req-SR-80 This forward link radio interface shall include in the signalling sufficient means to allow the S-MIM terminal to identify its managing hub, satellite beam and (if appli... |
68dab94c69ac1bd0d619783f6f2664bc | 102 721-2 | 5.1.5 Interaction between the Services | Req-SR-100 Services from all service segments shall be able to coexist at any given moment. Req-SR-110 Services corresponding to different service segments may be provided by: - a dedicated radio interface per service segment in the forward link. - a dedicated radio interface for any combination of service segments in ... |
68dab94c69ac1bd0d619783f6f2664bc | 102 721-2 | 5.1.6 Service Distribution | Req-SR-150 The satellite link shall distribute global content through the forward link radio interface. Req-SR-160 The FWD CGC, if present, shall repeat through its forward radio link the same global content distributed through the satellite link related to SS1 and SS2. Req-SR-170 The FWD CGC, if present, may distribut... |
68dab94c69ac1bd0d619783f6f2664bc | 102 721-2 | 5.2 System Requirements | |
68dab94c69ac1bd0d619783f6f2664bc | 102 721-2 | 5.2.1 Interface Requirements | Req-IR-10 The forward link radio interface shall interface to the S-MIM link layer specified in TS 102 721-5 [2]. ETSI ETSI TS 102 721-2 V1.2.1 (2013-08) 13 Req-IR-20 The link layer shall deliver MPEG-TS to the forward link radio interface for user, control and management data. Req-IR-30 All types of terminals shall in... |
68dab94c69ac1bd0d619783f6f2664bc | 102 721-2 | 5.2.2 Interoperability Requirements | Req-IOR-10 If DVB-SH is used as forward link radio interface, TDM or OFDM may be supported for the satellite link. Req-IOR-20 If DVB-SH is used as forward link radio interface, OFDM shall be supported for the terrestrial link. Req-IOR-30 The FWD CGC shall support MFN operation for the forward link in conjunction with t... |
68dab94c69ac1bd0d619783f6f2664bc | 102 721-2 | 5.2.3 Addressed Spectrum | Req-SpR-10 The forward link radio interface shall use frequencies below 3 GHz. Req-SpR-20 Specifically, the forward link radio interface shall operate in the 2 170 MHz to 2 200 MHz frequency band. Req-SpR-30 The following channelizations shall be supported in the forward link: 5 MHz. Req-SpR-40 The following channeliza... |
68dab94c69ac1bd0d619783f6f2664bc | 102 721-2 | 5.2.4 Operational Requirements | Req-OR-10 The terminals shall be able to receive in any valid sub-band of the forward link. Req-OR-20 CGCs shall operate in the whole frequency range available in the corresponding region. Req-OR-30 The forward link radio interface shall be able to operate with reduced coverage or performance in the absence of CGCs. Re... |
68dab94c69ac1bd0d619783f6f2664bc | 102 721-2 | 5.2.5 Design Requirements | The design requirements express guidelines to help the communications system design and specification. In particular, the design requirements will provide useful criteria to perform trade-offs in the specification and design of the communications system. Req-DR-10 Primarily, the forward link radio interface shall be de... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 1 Scope | The present document specifies the mandatory requirements for the Aeronautical Safety Services for the Family SL satellite network. |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 2 References | |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks in... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 3 Symbols and abbreviations | |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 3.1 Symbols | For the purposes of the present document, the symbols given in ETSI TS 102 744-1-4 [1], clause 3 apply. |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 102 744-1-4 [1], clause 3 apply. |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 4 Overview of Aeronautical Safety Services | |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 4.1 General | The Aeronautical Safety Service provides the following safety services simultaneously via a single channel unit on an aircraft to Class 6, Class 7 and Class 4 terminals: • ACARS • Prioritized IP data • Voice (two channels) The Aeronautical Safety Service is an application of the Family SL platform. ACARS and voice gate... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 4.2 Priority and Pre-emption | The Aeronautical Safety Service uses priority and pre-emption mechanisms provided within the Family SL infrastructure to ensure that required service availability is maintained during network congestion scenarios. |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 4.3 ACARS | The Aircraft Communications Addressing and Reporting System (ACARS) is a digital data-link system for the transmission of short, relatively simple messages between aircraft and ground stations via radio or satellite. ACARS messages have the following characteristics: Single block messages: • Short ACARS messages can be... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 4.4 Voice | The Aeronautical Safety voice service provides two channels of cockpit voice, call priority and pre-emption both at the UE and in network congestion scenarios. The AES is responsible for 'Intra-AES' pre-emption for both air-to-ground and ground-to-air calls. The Aeronautical Safety voice service can also provide Caller... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 4.5 Prioritized IP | The key characteristic of the prioritized IP service is the ability to request and deliver higher priority on the air interface between the RAN and the Aeronautical AES. The AES only offers such a service on cockpit Ethernet ports to ensure that cockpit service cannot be flooded by cabin IP traffic. Further, the USIM c... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5 ACARS Data Service | |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.1 Aeronautical Safety ACARS data service overview | This clause provides some information on the ACARS data service and the functional elements that together provide the Aeronautical Safety ACARS service. ETSI ETSI TS 102 744-4-2 V1.1.1 (2015-10) 11 A diagram showing peer-peer communications within the system is shown in Figure 5.1. Figure 5.1: ACARS Air and Ground Stac... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.2 AAGW Design Description | The use cases defined in Annex A prescribe the mandatory requirements for the Aeronautical Safety AES and AAGW providing the Aeronautical Safety ACARS data service capability. This clause provides an SDL description of an AAGW design that satisfies the normative requirements of the use cases in Annex A. Figure 5.2 prov... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3 Inter-ACARS Gateway Interface Description | |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.0 General | This clause specifies the interface between the ground gateway and its peer on the aircraft, known as the Inter-ACARS Gateway Interface or AIGI. |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.1 Connection to ACARS Ground Gateway interface | The parameters in Table 5.2 are required for accessing and tailoring the Aeronautical Safety ACARS service by the AAGW and are referenced throughout the rest of this clause. An indication on whether these parameters should be configurable by external means (i.e. ORT) is also given. ETSI ETSI TS 102 744-4-2 V1.1.1 (2015... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.2 AIGI Message Format | All AIGI messages between the AAGW and AGGW shall be encapsulated in UDP/IP. The UDP header already contains a checksum, and all AIGI messages will be sent one per UDP packet. No re-transmission request mechanism is implemented within this protocol to take advantage of error detection. An error in the ACARS message pay... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3 AIGI Message Definitions | |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.0 General | The following clause and its subclauses define the structure and content of AIGI messages. |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.1 Message Types | Table 5.3 defines all AIGI message types. Each AIGI message can contain aircraft position information if [position_reporting] is enabled. Messages with the name format of ac_xxxx_n indicate a message with no position reporting information present, i.e. [position_reporting] is disabled. Table 5.3: Message Type Identifie... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.2 Message ac_logon_rq (ac_logon_rq_n): Log-on request | |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.2.0 General | This message is sent by the AAGW during log-on. The ac_logon_rq_n message has the same contents as defined below with the exclusion of the location field. The message structure is defined in Figure 5.21 and the message contents are specified in Table 5.5. (MSB) Bit No (LSB) 8 7 6 5 4 3 2 1 message-type 0x01 ac_logon_rq... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.2.1 Transaction ID | The parameter transaction-id is a number is to be included in the content of all AIGI messages in order to track delayed message responses. The AAGW and AGGW maintain their own transaction ID numbers. The originator of a message transaction (a transaction being an originating message and response from its peer) populat... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.2.2 Location | The location field is common to all air to ground messages when [position_reporting] is enabled. The current aircraft location, altitude, heading and speed shall always be used for every air to ground message transmitted, i.e. if a message is retransmitted, the new aircraft location shall be provided. The message struc... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.2.3 Terminal type | The parameter terminal-type identifies the class of the Aeronautical Safety AES and whether alternative satellite services are supported as a fall back service. The message structure is defined in Figure 5.23 and the message contents are specified in Table 5.8. (MSB) Bit No (LSB) 8 7 6 5 4 3 2 1 cls rsv class terminal-... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.2.4 Logon Reason | The parameter logon-reason conveys the event that has initiated the Aeronautical Safety AES log-on request to the AGGW. The defined logon-reason codes are provided in Table 5.9. Table 5.9: logon-reason Parameter Definition Logon Reason Code Description 0x00 1st Log-on after Factory Settings Restart 0x01 1st Log-on afte... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.3 Message gw_logon_rp: log on response | |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.3.0 General | This message is sent by the AGGW during log-on. The message structure is defined in Figure 5.24 and the message contents are specified in Table 5.10. (MSB) Bit No (LSB) 8 7 6 5 4 3 2 1 message-type 0x41 gw_logon_rp Octet 1 transaction-id Octet 2 Octet 3 icao-address Octet 4 Octet 5 Octet 6 response Octet 7 session-id O... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.3.1 Response | The parameter response provides the Aeronautical Safety AES with some information regarding its attempt to log-on, whether it succeeded or failed and can influence further actions taken. The AAGW behaviour will follow the AIGI protocol as defined in the use cases in Annex A. Log-on failures shall be classed as either t... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.4 Message ac_logoff_rq (ac_logoff_rq_n): Log off request | |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.4.0 General | This message is sent by the AAGW. The ac_logoff_rq_n message has the same contents as defined below with the exclusion of the location field. The message is used to end a session with the AGGW. The message structure is defined in Figure 5.25 and the message contents are specified in Table 5.12. ETSI ETSI TS 102 744-4-2... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.4.1 Cause Code | The parameter cause-code provides a reason as to why the Aeronautical Safety AES has logged off of the AGGW. The defined logoff cause codes are provided in Table 5.13. Table 5.13: cause-code Parameter Definition Cause code Meaning 0000 nnnn Reserved as used by alternative satellite link on terrestrial ACARS interface 0... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.5 Message gw_logoff_ack: Log-off acknowledgement | This message is sent by the AGGW. The message is used to acknowledge that a log-off request message has been received. The message structure is defined in Figure 5.26 and the message contents are specified in Table 5.14. (MSB) Bit No (LSB) 8 7 6 5 4 3 2 1 message-type 0x42 gw_logoff_ack Octet 1 transaction-id Octet 2 O... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.6 Message gw_logoff_notify: log off notification | |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.6.0 General | This message is sent by the AGGW to terminate a connection with the AAGW. The message structure is defined in Figure 5.27 and the message contents are specified in Table 5.15. (MSB) Bit No (LSB) 8 7 6 5 4 3 2 1 message-type 0x43 gw_logoff_notify Octet 1 transaction-id Octet 2 Octet 3 icao-address Octet 4 Octet 5 Octet ... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.6.1 Reason | The parameter reason provides the Aeronautical Safety AES with some information regarding why the AGGW issued the log-off notification. The AAGW behaviour will follow the AIGI protocol as defined in the use case in clause A.14. The setting of configuration item ac_r5 (see clause 5.3.3.11) will ensure that in cases wher... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.7 Message ac_acars_msg (ac_acars_msg_n): Single block ACARS message | This message is sent by the AAGW. The ac_acars_msg_n message has the same contents as defined below with the exclusion of the location field. The message is used to by the AAGW to send a single block ACARS message to the ground. The message structure is defined in Figure 5.28 and the message contents are specified in T... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.8 Message gw_acars_ack: Acknowledgement of ACARS message receipt | This message is sent by the AGGW. It is used to confirm delivery of the message. The AAGW will re-send the message (once) if this message is not received. The re-transmission timeout of the CMU (180 s) is too long to ensure delivery within the latency bounds of RCP240. The message structure is defined in Figure 5.29 an... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.9 Message gw_acars_msg: Single block ACARS message | This message is sent by the AGGW. The message is used to by the ground (ACARS) gateway to send a single block ACARS message to the aircraft. The message structure is defined in Figure 5.30 and the message contents are specified in Table 5.19. (MSB) Bit No (LSB) 8 7 6 5 4 3 2 1 message-type 0x45 gw_acars_msg Octet 1 tra... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.11 Message gw_conf: Update of AAGW configurable parameters | |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.11.0 General | This message is sent by the AGGW. The message is used to configure the AAGW, and is sent after an AES has logged on. The AAGW does not store this data over an Aeronautical Safety AES power cycle. The message structure is defined in Figure 5.32 and the message contents are specified in Table 5.21. ETSI ETSI TS 102 744-4... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.11.1 AGGW Configuration Items | The configuration items in Table 5.22 are used by the AGGW and are provided here for completeness in defining the AIGI protocol. Table 5.22: AGGW Configuration Items Configuration Item Description Default Min Max gw_t1 Timeout period in seconds on return link message reception. After receiving any message in the return... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.13 Message ac_keepalive (ac_keepalive_n): keep-alive | This message is sent by the AAGW. The ac_keepalive_n message has the same contents as defined below with the exclusion of the location field. The message is used as a keep-alive to test that the link between the AAGW and the AGGW is operational. The message structure is defined in Figure 5.34 and the message contents a... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.14 Message gw_keepalive_ack: keep-alive acknowledgement | This message is sent by the AGGW. The message is used by the aircraft gateway to confirm that the link to the AGGW is operational. The message structure is defined in Figure 5.35 and the message contents are specified in Table 5.25. (MSB) Bit No (LSB) 8 7 6 5 4 3 2 1 message-type 0x47 gw_keepalive_ack Octet 1 transacti... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.15 Message gw_keepalive: keep-alive | This message is sent by the AGGW. The message is used by the ground gateway to test that the link to the AAGW is operational. The message structure is defined in Figure 5.36 and the message contents are specified in Table 5.26. (MSB) Bit No (LSB) 8 7 6 5 4 3 2 1 message-type 0x48 gw_keepalive Octet 1 transaction-id Oct... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.17 Message gw_csp_ping: ping | This message is sent by the AGGW. The message is used by the ground gateway to test that the link to the AAGW is operational. The sending of this message is triggered by the CSP. The message structure is defined in Figure 5.38 and the message contents are specified in Table 5.28. (MSB) Bit No (LSB) 8 7 6 5 4 3 2 1 mess... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.18 Message ac_csp_ping_ack (ac_csp_ping_ack_n): ping acknowledgement | This message is sent by the AAGW. The ac_csp_ping_ack_n message has the same contents as defined below with the exclusion of the location field. The message is used to confirm the link between gateways is operational. The response of this message is forwarded to the CSP. The message structure is defined in Figure 5.39 ... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.19 Message gw_test_msg: AIGI Traffic Test | This message is sent by the AGGW. The message is used to confirm the link between gateways is operational and to put a traffic load on the AIGI protocol. The message structure is defined in Figure 5.40 and the message contents are specified in Table 5.30. ETSI ETSI TS 102 744-4-2 V1.1.1 (2015-10) 57 (MSB) Bit No (LSB) ... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.20 Message ac_test_ack (ac_test_ack_n): AIGI Traffic Test Acknowledgement | This message is sent by the AAGW. The ac_test_ack_n message has the same contents as defined below with the exclusion of the location field. The message is used to acknowledge the AIGI test message sent by the AGGW. The message is used to confirm the link between gateways is operational and to put a traffic load on the... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.21 Message ac_msg_nak (ac_msg_nak_n): Invalid AGGW message | This message is sent by the AAGW. The ac_msg_nak_n message has the same contents as defined below with the exclusion of the location field. The message is used to indicate that an originating message received from the AGGW was invalid. This message will only be sent by the AAGW in place of an expected message pair resp... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.3.3.22 Message gw_msg_nak | This message is sent by the AGGW in response to any message received from an AAGW, within an ocean region that the AGGW is serving, that is not contained in the AGGW's AES Logon table. The message structure is defined in Figure 5.43 and the message contents are specified in Table 5.33. ETSI ETSI TS 102 744-4-2 V1.1.1 (... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.4 Provisions for ACARS Authentication | The AES shall be upgradeable to add in the future a security mechanism for the ACARS messages such that authentication of the ACARS messages in both directions is achieved. The AES shall have appropriate hardware provisions such that an upgrade would be limited to adding an additional Universal Integrated Circuit Card ... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 5.5 Prioritized Access to the Family SL Network | The Aeronautical Safety AES shall have prioritized access to the Family SL network in the event of a Family SL SAS switch. (A Family SL SAS switch may occur due to planned maintenance activities or in the event of a failure in the ground network). In the event of a Family SL SAS switch, all user terminals will attempt ... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 6 Prioritized IP Data Service | The Aeronautical Safety Service shall support a prioritized cockpit IP service. This will provide the ability to request and deliver higher priority IP data on the air interface between the RAN and the AES. This shall be supported via both background and streaming class PDP context(s) and will be governed by the use of... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7 Aeronautical Safety Voice service | |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.0 General | This clause provides a description of operation for voice services over Family SL in support of Aeronautical Safety Services. |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.1 Key Features | The key features of the Aeronautical Safety AES Voice Service are listed below and elaborated further in the following clauses: 1) All ground-to-air cockpit calls are delivered to the Aeronautical Safety AES using a single number for the aircraft that is based on the ICAO 24 bit address. 2) Air-to-ground calls are deli... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.2 Second Voice Channel | The Family SL network is a 3GPP system which means the MSC can only provide one voice call per device. The second channel of voice is provided via the PS infrastructure using Voice over IP (VoIP). This solution utilizes the existing system infrastructure, whereby additional voice calls are forwarded to a VoIP subsystem... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.3 Priority and Pre-emption | Four levels of priority are required in the AES for both ground-to-air and air-to-ground calls for the voice service, and this priority is presented to the cockpit for display to the pilot. Furthermore, should an incoming voice call be at a higher level of priority, and both circuits between the AES and the cockpit aud... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4 Aeronautical Safety AES Voice Requirements | |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4.0 General | To provide the two channels of voice capability, with priority and pre-emption, the AES shall implement session management and control functionality between the CS and PS domains. For the VoIP domain, the AES shall also implement a User Agent in the VoIP Service Domain which is essentially providing a Private Branch Ex... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4.1 Parameters | The parameters in Table 7.1 are required for accessing and tailoring voice services by the AES PBX and are referenced throughout the rest of this clause. An indication on whether these parameters should be configurable by external means (i.e. ORT) is also given. ETSI ETSI TS 102 744-4-2 V1.1.1 (2015-10) 63 Table 7.1: A... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4.2 Number of Concurrent Calls | The AES PBX shall support a minimum of two concurrent voice calls (one call placed via the CS domain and an additional call placed through the PS domain). |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4.3 Support for Short Code Dialling | The AES PBX shall support Short Code Dialling in both service domains. |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4.4 Call Routing, Voice Priority and Pre-emption | |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4.4.0 General | When a call is placed from a cockpit interface connected to the AES PBX, then the AES PBX shall first check whether the CS Domain can be used to place the call. Only if the CS Domain is not available shall the call be placed via the PS Domain over VoIP. Ground-to-air (mobile terminated) calls shall initially be present... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4.4.1 AES CS Protocol Requirements for eMLPP | On successful CS attachment, the Aeronautical Safety AES shall proceed to invoke the "Register eMLPP" procedure towards the MSC as specified in ETSI TS 123 067 [7]. If the Aeronautical Safety AES is unable to complete this process, a suitable fault should be raised. Failure to successfully register the eMLPP capability... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4.4.2 Priority Signalling | In order for the Aeronautical Safety AES to make decisions regarding pre-emption of in-progress calls, it needs to know the priority of those in-progress calls as well as those calls attempting to be established. In the CS domain, signalling of priority is achieved by using the native 3G CS priority mechanism of Multi-... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4.4.3 AES Priority and Pre-emption | The AES has the responsibility of making pre-emption decisions for both incoming ground-to-air and outgoing air-to- ground calls. For air-to-ground calls, the AES knows the priority of any in-progress calls and the call being initiated and so can make these decisions locally. For ground-to-air calls, the AES shall extr... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4.5 VoIP Context Management Requirements | |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4.5.1 Primary PDP Context Establishment | On start-up, the AES PBX shall check that the Aeronautical Safety AES has attached to the PS Domain and if so, proceed to activate a Primary Background PDP Context towards the APN [apn_name] dedicated to the provision of IP transport to the VoIP Service Domain. On successful activation of the PDP Context, the AES PBX s... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4.5.2 Secondary PDP Context Definition | A secondary Streaming PDP Context linked to the Primary Background PDP context referred to in clause 7.4.5.1 shall be defined but only activated when a call is being placed via the VoIP service domain. The Traffic Flow Template (TFT) for the secondary Streaming PDP context shall be defined such that only the RTP voice ... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4.5.3 Secondary PDP Context Activation and Deactivation | The AES PBX shall keep track of the status of VoIP calls being set up and cleared: When the first call is set up in the VoIP Service Domain, the AES PBX shall activate the Secondary PDP Context with a requested Guaranteed Bitrate as specified in clause 7.4.7.2 prior to sending a SIP Invite to the SIP server. Whenever a... |
0631f58241bbe967a7794ca8443f7e04 | 102 744-4-2 | 7.4.6 SIP Protocol Requirements |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.