Functional Architecture for the Data Communication System(44)_航空信息_民用航空_通用航空

曝光台注意防骗网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者

performed for the entire route of flight that is within U.S. domestic airspace. [from ERAM SADD, Section 4.2.2]

[S1]: No changes are anticipated.

[S2]: The TJS will be modified to accept aircraft provided wind vector information, state data, and intent data in order to enhance trajectory prediction. In addition, the TJS will accept FMS Trajectory information to improve trajectory prediction. The TJS will 'also' control aircraft subscriptions (data subset selection and update rate).

[S3]: The TJS will be modified to extend prediction accuracy from current 30 minutes to future 2 hours.

Note: In [S3], the time horizon for a given prediction accuracy for the TJS must be extended from 30 minutes to 2 hours. Additional airborne environmental data (state data) may need to be provided to TJS and/or WDP.

Embedded Elements
Element Detail Notes
Port 2.1.1.4.0.2 TJS.IFP_Port

1.0

Port 2.1.1.4.0.1 TJS.FLS_Port

1.0

2.1.1.1 Interface Proxies (IFP)
Type:  Object
Status:  Proposed. Version 1.0. Phase 1.0.
Package: 2.0 Ground Data Processing (GDP)     Keywords:
Detail:  Created on 5/10/2006. Last modified on.11/29/2006.
GUID:  {A089ED4E-32B5-4315-B286-1EE238668AD3}

The IFP function provides separate proxies to handle inputs and outputs for each external facility. Each proxy determines what, when, and the message format that is sent for each interface. Input messages are validated syntactically prior to calling on other functions to complete the request (e.g., when a flight plan is amended, IFP checks the existence of the flight and the presence of the required fields for the specific amendments and the adherence to the prescribed field’s ranges then FLS is called to amend the flight). [from ERAM SADD, Section 4.2.2]

[S1][A2][A3]: The IFP will be modified to support data exchange with external CPDC function. The following types of data is needed by the CPDC:
- User Eligibility Information
- Current/Next Data Authority Information
- Flight Object Data (needed to perform aircraft-to-flight plan correlation at CPDC aircraft dialog start)

Note: There are actually two (2) IFPs: IFP-A (talks to non-ERAM world) and IFP-B (talks to ERAM components)

Connections
Connector Source Target Notes
Realisation
Source -> Destination
ConnSource.Scope= Public
ConnSource.Role
ConnSource.RoleNote
Element.Name=
2.1.1.1 Interface Proxies (IFP)
Element.Type=
Object
  ConnTarget.Scope= Public
ConnTarget.Role=

ConnTarget.RoleNote=
Element.Name=
PPR.3.1.2.4 [S2] Decision Support Tools
Element.Type=
Requirement


Realisation
Source -> Destination
ConnSource.Scope= Public
ConnSource.Role
ConnSource.RoleNote
Element.Name=
2.1.1.1 Interface Proxies (IFP)
Element.Type=
Object
  ConnTarget.Scope= Public
ConnTarget.Role=

ConnTarget.RoleNote=
Element.Name=
PPR.3.1.2.7 [S2] Aircraft Decision Support Tools
Element.Type=
Requirement