hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 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 referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 3 Definition of terms, symbols and abbreviations | |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 3.1 Terms | For the purposes of the present document, the following terms apply: agile: software lifecycle model that is characterized by the division of tasks into short phases of work and frequent reassessment and adaptation of plans artifact: digital evidence generated as a part of the development process and not for the sole p... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 3.2 Symbols | Void. |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACM Association for Computing Machinery AFCEA Armed Forces Communications and Electronics Association AFIPS American Federation of Information Processing Societies AI Artificial Intelligence ANSSI Agence nationale de la sécurité des systèmes d... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 4 Evolution of the Security by Design Ecosystem | |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 4.1 Introduction | The challenges of information security emerged early. David Kahn in his reference book "The Code Breakers" [i.35] describes many of them over the millennia. GCHQ's (United Kingdom's Government Communications Headquarters) authorized history points to the extensive use of cryptography by spymaster Francis Walsingham dur... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 4.2 Achieving and Assessing Security by Design | The present document is intended as a resource for software development organizations, end users, and compliance authorities who seek to answer the question "is this software (or the software delivered by this vendor or service provider) Secure by Design (SbD)?" This has long been a difficult question, and it is more c... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.0 Structure of the SSDIF | |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.0.1 Objectives and methods | Secure by Design encompasses what developers regard as "design" as well as security of implementation and security of default configuration. The objective of Secure by Design is that systems and particularly software be "sufficiently secure" to meet the needs of the end users/organizations that rely on them and that th... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.0.2 SSDIF Development Groups | Not all software development organizations possess the same degree of technical expertise or complexity. As such, processes will differ across software development organizations in concert with their characteristics. This need for differentiation by available resources, including SMEs, and organizational maturity is re... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.0.3 SSDIF Roles | The SSDIF identifies specific roles that support the Secure by Design lifecycle and are responsible for the identified practices and actions. These roles are listed in Table 5.0-3, below. Table 5.0-3: List of SSDIF Roles Role Type Role Description CISO Team Responsible for policies, standards, configuration, and operat... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.0.4 Assessment and Evidence | For evaluation and legal purposes, software development organizations need to demonstrate that their products are "Secure by Design (SbD)." This does not mean that the software is vulnerability-free - there is no such thing. For purposes of the present document, secure-by-design means that the software development orga... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.0.5 Use of Artificial Intelligence and Machine Learning | The use of Artificial Intelligence and Machine Learning (AI/ML) is an important consideration for software development and software security. There are four domains for application of AI/ML in secure software development: 1) The components under development may incorporate AI/ML components whose security is assured. As... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.1 Essential 1: Secure Software Design | |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.1.0 Overview | Secure software design begins with a set of security objectives that the software satisfies and a set of security threats that the software should resist. Although specific systems - especially systems targeted at specific applications or customers - may have very specific objectives, most commercial products and onlin... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.1.1 SSDIF Essential 1 Tasks - Secure Software Design | Task ID PO.1.2 Identify and document all security requirements for organization-developed software to meet and maintain the requirements over time. CSC Safeguard; SAFECode practices 16.1, 16.2; N/A SSDIF PO.1.2 DG Specific Actions DG 1/2/3: The organisation 1. shall establish a documented secure development process (in... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.2 Essential 2: Secure Development | |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.2.0 Overview | Software development, encompassing coding, testing, rollout to customers, and maintenance throughout the lifecycle, has historically been the source of most product vulnerabilities. At a high level, all secure development processes are similar and encompass the practices enumerated in the SSDF. However, the details of ... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.2.1 SSDIF Essential 2 Tasks - Secure Development | Task ID PO.2.1 Create new roles and alter responsibilities for existing roles as needed to encompass all parts of the SDLC. Periodically review and maintain the defined roles and responsibilities, updating them as needed. CSC Safeguard; SAFECode practices 16.1; N/A SSDIF PO.2.1 DG Specific Actions DG 1/2/3: The organis... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.3 Essential 3: Secure Default Configuration | |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.3.0 Overview | Software products frequently include myriad configuration settings and options that system administrators may use to enable or disable features or adjust product behaviour. Although users can adjust those settings, many will fail to do so. Experience has shown that many users and administrators accept default settings.... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.3.1 SSDIF Essential 3 Tasks - Secure Default Configuration | Task ID PW.9.1 Define a secure baseline by determining how to configure each setting that has an effect on security or a security-related setting so that the default settings are secure and do not weaken the security functions provided by the platform, network infrastructure, or services. CSC Safeguard; SAFECode practi... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.4 Essential 4: Supply Chain Security | |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.4.0 Overview | The term "supply chain security" refers to the challenge to Secure by Design that is posed by software development organizations' use of software that they did not themselves create (often referred to as "third party code") Such software should have been developed with the full panoply of SbD requirements for the syste... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.4.1 SSDIF Essential 4 Tasks - Supply Chain Security | Task ID PO.1.3 Communicate requirements to all third parties who will provide commercial software components to the organization for reuse by the organization's own software. [Formerly PW.3.1] CSC Safeguard; SAFECode practices 16.4; Manage security risk inherent in use of third party components SSDIF PO.1.3 DG Specific... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.5 Essential 5: Code Integrity | |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.5.0 Overview | Secure design and development practices enable a software development organization to produce software that addresses potential threats once it is in use, but the software development organization also plays a role in ensuring that the software that end users/organizations rely on is the software that they intended to ... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.5.1 SSDIF Essential 5 Tasks - Code Integrity | Task ID PO.1.1 Identify and document all security requirements for the organization's software development infrastructures and processes, and maintain the requirements over time. CSC Safeguard; SAFECode practices 1.1, 2.1, 3.1, 4.1, 5.1, 6.1, 7.1, 8.1, 11.1, 12.3, 15.2, 16.1, 17.4, 18.1: N/A SSDIF PO.1.1 DG Specific Ac... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.6 Essential 6: Vulnerability Disclosure and Remediation | |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.6.0 Overview | Vulnerability response and remediation are part of any secure development process. Software that is perfect and vulnerability-free is infeasible except in very limited circumstances. Development teams should implement processes to accept reports of product vulnerabilities, investigate the reports, and remedy the vulner... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.6.1 SSDIF Essential 6 Tasks - Vulnerability Disclosure and Remediation | Task ID RV.1.1 Gather information from software acquirers, users, and public sources on potential vulnerabilities in the software and third-party components that the software uses and investigate all credible reports. CSC Safeguard; SAFECode practices 7.2, 7.2, 7.3, 16.2; Create and Manage a Vulnerability Response Proc... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 1 Scope | The present document defines the technical requirements necessary to implement the inter-working between Terrestrial Flight Telecommunications System (TFTS) and Global System for Mobile Communications (GSM) digital cellular communication networks. This inter-working will enable users of GSM mobile phones to place and r... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • Fo... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AS Aircraft Station AT Avionics Termination ATEI Aircraft Termination Equipment Identity CC Credit Card CCM Call Control Management CCS Cabin Communications System CFB Call Forward Busy CFNRc Call Forward Not Reachable CFNRy Call Forward No Re... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 4 Overview | |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 4.1 General | The Terrestrial Flight Telecommunications Systems (TFTS) [1], [2], [3], [4] is a digital cellular radio technology, which offers communication services to aeronautical passengers. The scope of the original ETS 300 326, specifies functionality and services which enable calls to be placed in the air-to-ground direction o... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 4.2 Service definition | |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 4.2.1 Services supported | The service defined will enable users of GSM mobile terminals, to receive voice calls on-board an aircraft, via the TFTS system and airborne avionics equipment. This service will help address one of the remaining limitations on the mobility offered by GSM services, due to the restrictions that have been put in place by... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 4.2.1.1 Ground to air calling | The service will enable users of GSM mobile phones to use the TFTS system as a replacement for the mobile handset when flying. To receive calls on-board, the passenger and GSM user shall first make a one-off subscription to the service. This is achieved by establishing an association between the user's MSISDN number an... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 4.2.1.2 Air to ground calling | To ensure that a subscribed user is currently authorized to make mobile originated roaming calls, the user is also required to register before placing air to ground calls. On registering, the GLR obtains information from the GSM user's HLR, regarding the class of service offered. This will indicate that the user is sub... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 4.2.1.3 Short message service | |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 4.2.1.3.1 Ground to air messaging | The system shall support the receipt of GSM short messages (SMS) by GSM users when registered onboard aircraft. SMS messages destined for the GSM user shall be automatically transferred to the TFTS system and the handset on- board the aircraft. A credit card swipe shall be required to authenticate the user before the m... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 4.2.1.3.2 Air to ground messaging | The system may evolve to support air to ground SMS messaging. A ground to air message may be implemented by initiating a call set-up. The GSS/GLR shall then initiate a page channel with the AT, to receive the SMS message. |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 4.2.1.4 Fax and data services | The specification will evolve to support GSM fax and data services. This will be dependent on the development of TFTS fax and data services. ETSI TS 101 281 V1.1.1 (1998-07) 10 |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 4.2.2 System architecture | An overview of the system architecture required to achieve inter-working between GSM and TFTS networks is shown in figure 1. The solution provides a signalling path between GSM and the TFTS Gateway Location Register (GLR), using GSM Mobile Applications Part (MAP) [9]. Call switching and transmission between GSM and TFT... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5 Functional specification | |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.1 Cabin communications system | |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.1.1 General | The Cabin Communications System (CCS) provides the interface between the TFTS system and the passenger and connects the ground to air call. To enable GSM calls to be delivered to a passenger on-board the aircraft, the main functions performed by the CCS are: a) to enable the passenger to register or de-register to rece... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.1.2 Passenger registration | |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.1.2.1 Registration messages | Although the system may evolve to provide a variety of methods for the passenger to register to receive calls, initially passenger registration shall be carried out by requesting a magnetic card swipe. This shall initiate a call control SETUP message to the GSS, which if released successfully from the ground shall indi... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.1.2.2 Registration buffer | If a passenger attempts to register when WOW is enabled and TFTS is unavailable (on the ground and outside of coverage), the CCS shall accept the registration and store in a buffer. These messages shall be sent in sequence to the ground, once WOW is disabled AND TFTS is available. |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.1.2.3 Call alert routing to handset | In order for the ground to air call alert message to be directed to the correct handset, two methods are specified, to provide flexibility for specific implementations. The first method is that an handset identifier number be included in the passenger registration SETUP message. The handset identifier may be included i... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.1.2.4 CCS register of passengers | The CCS may be required to retain a record of passengers who have registered successfully. The register would store the magnetic stripe card number used to register and the handset from which registration took place, together with a Class of Service status indication. The Class of Service indication will be determined ... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.1.3 Ground to air call alert | Notification of a ground to air call (and ground-to-air SMS delivery) is received by the CCS as a PAGE request message (ARINC). The format of this message is shown in table 3. Table 3: Ground to air page alert data format Element Type Reference Length Type of Page MF Table 5 1 binary CC Number MF note 1 40 Handset Iden... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.1.4 Call connect to GSS | On accepting a call, the CCS initiates a normal call control SETUP, to the routing number provided in the ground to air call alert PAGE message. The routing number is provided from the call alert page message in the format ETS 300 326 subclause 10.11.8.5.3.4. The CCS shall convert this number to the format specified in... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.1.5 Ground-to-air SMS delivery | On receipt of the ground-to-air PAGE message containing the SMS message the CCS shall alert the passenger via the handset displaying their mobile number (or text message if appropriate) and on confirmation from the passenger of their willingness to accept the message display the SMS message. In doing so the CCS shall e... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.2 Avionics termination | |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.2.1 General | The following functionality is required for the AT, in addition to ETS 300 326-2 [2] and ARINC Characteristic 752 [4] and ARINC Characteristic 746 [5]: a) Location Management; b) Passenger Registration Message Handling (normal call SETUP); c) Incoming Call Page Handling and Credit Card Number format conversion. Locatio... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.2.2 Location management | The AT shall send a Location Update (LU) to the GLR whenever a new GS or GSC is selected. The initiation of an LU should be based on a configurable parameter requiring LU on either change of GS or change of GSC, which can be determined from the GSIC. ETSI TS 101 281 V1.1.1 (1998-07) 16 |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.2.2.1 Location registration/update | When an initial GS/GSC is selected (ETS 300 326-2 [2] subclause 8.10.6), the Radio Resource Management (RRM) shall send a request for LU to the Call Control Management (CCM). On receipt of the LU the CCM shall initiate a call SETUP (ETS 300 326-2 [2] subclause 10.11.4.2. This call SETUP message shall contain "called pa... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.2.2.2 Location de-registration | When the AT approaches the limit of the current selected GS and there are no surrounding GS available which satisfy the handover criteria, the AT shall initiate Location Deregistration. The procedure shall follow that defined in subclause 5.2.2.1. ETSI TS 101 281 V1.1.1 (1998-07) 17 |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.2.2.3 TFTS ground to air availability notification | In the event of a failed Location Update, an ECL message shall be initiated by the AT and passed to the CCS. This message is a modified TFTS Available message (ARINC 746 attachment 11). The ECL message is organized so that there are three message types: EVENT REPORT, GET and SET. A new TFTS Ground to Air Availability M... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.2.3 Passenger registration message handling | A Passenger Registration or De-Registration message shall be received from the CCS as a normal call control SETUP message. On receipt, the CCM entity shall request the establishment of radio resources as ETS 300 326-2 [2] subclause 10.11.4.2. When the indicated radio resources are established CCM shall forward the SETU... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.2.4 Incoming call page handling | The AT shall monitor all GS on the scanning receiver such that the current selected GS is scanned alternately with each of the other GS in the current list: - Current_GS; - GS1; - Current_GS; - GS2; - Current_GS; - GS3 ... etc. This shall ensure the AT is capable of receiving a SYSTEM INFORMATION 6 (ETS 300 326-2 [2]) ... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.3 Ground station system | |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.3.1 General | The functionality carried out by the GSS includes: a) receive passenger registration and location update SETUP messages from the AS; b) generate passenger registration and location update messages and forward to GLR; c) page AS and transfer incoming call alert page data from GLR to AS; d) generate ground to air call ro... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.3.2 GSS architecture | Physical requirements for GSS to GLR communications are not prescribed by the present document and therefore any suitable data transmission media and protocols may be utilized in the implementation. Information on data networking requirements is therefore only provided for information. The present document does however... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.3.3 GSS to GLR communications | Physical requirements for GSS to GLR communications are not prescribed by this Technical Specification and therefore any suitable data transmission media and protocols may be utilized in the implementation. Information on data networking requirements is therefore only provided for information. The present document does... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.3.3.1 Message routing options and link management - X.25 networks | Where X.25 public data networks are used to provide data transmission between GSC and GLR, it is possible to provide different networking configuration, to gain efficiencies in data transmission costs. A point to point connection is used where a single Telecom Operator's GSC has to be connected internationally to the G... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.3.3.1.1 Link management - GSS to GLR | A dedicated virtual circuit is used for messages sent from GSC to the GLR. Virtual circuits can be established to more than one GLR where necessary. This is an "on-demand" access, that is to say, if the link is not opened, the GSC opens it, and keeps it opened until a timer expires (Timer is restarted each time there i... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.3.3.1.2 Link management - GLR to GSS | A dedicated incoming access is reserved at the GSC side, on a per GLR basis. It is opened on request from each GLR. It is not the role of the GSC to clear this link when no more transactions are needed. Call setup The X25 call setup is sent by the corresponding service provider's GLR. The call packet user data field co... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.3.4 Registration and location management | The GSS receives both passenger registration/de-registration and AS LU messages from the AS as call control SETUP messages (subclause 5.1.2.1). The information contained in these messages is formatted into a common Registration/LU Request message and forwarded to the GLR. No record of registered AS or passengers is ret... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.3.5 Incoming call page message handling | |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.3.5.1 Receipt of incoming call alert | When a mobile terminating call is received by the GSM user's HLR, routing information is requested from the GLR and subsequently from the GSS. The message from the GLR to the GSM performs the following: - alerts the GSS of the incoming call; - provides the GSS with details of target AS, passenger and handset; - request... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.3.5.2 Mechanism to page AS | In order to efficiently use radio resources and optimize the page delivery time, an algorithm is required in the GSS to deliver page requests on a regular pattern. See subclause 5.2.4. This algorithm is not defined within the scope of the present document. However, the design objective of the algorithm is to maximize t... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.3.6 Call connection | The GSS provides a routing number to the GLR, which is an DDI number on the GSS PBX. This call is received by the GSC which responds to GSM with and ALERTING message and in-band ringing tone. When the passenger accepts the incoming call, a call is established by the CCS in the normal manner, from air to ground. The rou... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.3.7 Call forwarding | In the event that the call cannot be completed, due to a TFTS state listed in table 13, the GSS shall hold the incoming call and requests call forwarding information from the GLR. This shall be achieved by sending a Get New Number message formatted according table 14. Table 13: TFTS to GSM Call state translation TFTS S... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.3.8 Administration | The GSS creates administration records for each registration/LU message. System reference numbers are included in all GSS initiated messages. ETSI TS 101 281 V1.1.1 (1998-07) 24 |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.4 Gateway location register | |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.4.1 General | The Gateway Location Register (GLR) provides an interface between TFTS and GSM networks and carries out the following primary functions: a) Location Management; b) Registration Management; c) GSM Visited Location Register; d) Call Handling; e) Signalling and Message Translation; f) Data management; g) GSM Visited MSC f... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.4.2 Location management | The GLR stores a register of aircraft permitted to receive calls from GSM. Each aircraft provides a LU to the GLR when it changes GS/GSC. The register of aircraft stores the current GS/GSC for each aircraft, to enable ground to air calls to be delivered to the correct GS/GSC. Messaging required to establish an AS locat... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.4.3 Registration management | |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.4.3.1 Registration | Passenger registration messages are sent from the CCS to the GLR, as a SETUP message to the GSS and then as a GSS generated message to the GLR. The message is carried on an X.25 network connection from the GSS to the GLR which is established either as a switched or permanent virtual circuit. The X.25 session includes a... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.4.3.2 De-registration | Passengers who have registered to receive calls can be de-registered from TFTS in a number of ways: a) All passengers registered on an aircraft are de-registered once X% of the registered passengers have de- registered, by registering on a GSM network (switching on GSM handset). This global de-registration would only o... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.4.4 Call handling | |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.4.4.1 Incoming call | When an incoming call request is received by the home network, the HLR requests call routing information from the GLR, which shall be registered and function as the associated VLR for the mobile subscriber. The GLR shall in turn request routing information from the GSS. This is carried out by a Call Alert Page Request ... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.4.4.2 Call forwarding | GSM call conditions Call Forwarding Unconditional (CFU) and Call Forwarding Not Reachable (CFNRc) are generally handled by the HLR. However, in the case of delivering a call to an aircraft, it is possible that the subscriber shall become not reachable during the time that the call control is being handed over to the GS... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.4.5 Signalling and message translation | The GLR carries out communication management of both X.25, for the GSS to GLR interface, and MAP communications for the GLR to HLR interface and SMS GMSC to GLR interface. In most cases, the GLR carries out message translation between GSS and HLR/SMS GMSC originated messages. The translation may be required on each ind... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.4.6 Data management | In addition to the standard VLR profile information required to allow subscribers to inter-work between the two systems, the minimum subscriber data required is detailed in table 18. Table 18: GLR data elements Information source Information element Status of data GSS GSIC (GCC+GSN) Static X.25 Network User Address Sta... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 5.4.7 SMS handling | The GLR shall act as a GSM Visited MSC (VMSC) for the purposes of delivering SMS messages to passengers who have registered to receive their SMS messages on board aircraft. The complete SMS User Data field (i.e. the content of the TCAP messages) shall be delivered across the network to the CCS using the same mechanism ... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 6 Information flows | For all of the following call flows, dashed lines have been used to highlight commands which may not be required due to a specific implementation. Particularly, these relate to previously established X.25 connections. |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 6.1 Aircraft system location registration/de-registration | CCS AT GSS GLR HLR ARINC 746 ETS 300 326 GSS-GLR MAP Location Update SETUP X.25 SVC X.25 EST DISCONNECT CLOSE SVC Call Proceeding LU Request LU Request Response Figure 5: Location update call flow ETSI TS 101 281 V1.1.1 (1998-07) 28 |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 6.2 Passenger registration/de-registration | CCS AT GSS GLR HLR ARINC 746 ETS 300 326 GSS-GLR MAP Passenger Registration/De-registration SETUP X.25 SVC X.25 EST DISCONNECT CLOSE SVC Call Proceeding Passenger Registration Request Passenger Registration Request Response SETUP SRI for SM (M SISDN) SRI for SM Rsp (IMSI) Update Location (IM SI, LR) Insert Sub data (Da... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 6.3 Call delivery | CCS AT GSS GLR HLR ARINC 746 ETS 300 326 GSS-GLR MAP Call Delivery X.25 SVC PRN (IMSI) Call Alert PAGE Request Call Alert Page Response SRN (DDI) X.25 EST Call Alert PAGE PAGE Channel EST PAGE Data Transfer PAGE Data Transfer Call Alert PAGE PAGE Channel EST PAGE Channel Release PAGE Channel Release SET UP Call SETUP f... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 6.4 Call forwarding | CCS AT GSS GLR HLR ARINC 746 ETS 300 326 GSS-GLR MAP Call Forwarding X.25 SVC Get New Number Response Get New Number X.25 EST Call SETUP from GSM Close SVC Figure 8: Call forwarding - Call flow |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 6.5 Ground-to-air SMS | CCS AT GSS GLR SMS GMSC ARINC 746 ETS 300 326 GSS-GLR MAP SMS ground-to-air X.25 SVC Forward_Short_Message Call Alert PAGE Request (SMS User Data X.25 EST Call Alert PAGE PAGE Channel EST PAGE Data Transfer (1) PAGE Data Transfer (1) Call Alert PAGE PAGE Channel EST PAGE Channel Release PAGE Channel Release PAGE Data T... |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 7 Timers and counters | |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 7.1 Timers | T_HO Default 15 s T_PW Default 20 s T_LU Default 60 s T_PLU Default 1800 s (30 minutes) T_AGS Default 30 s |
87ac7c4dc576e7bd6bf748dd5d75dbd2 | 101 281 | 7.2 Counters | N_LU Default 2 ETSI TS 101 281 V1.1.1 (1998-07) 31 Annex A (informative): Modified ARINC 746 ECL messages A.1 TFTS availability The TFTS status should be indicated to the CTU through the use of an information element within an Event Report message or, in response to a Get message. The Information element can provide on... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.