windy/msgexchange-api
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Files
1451f866403f3b92f02a43bfbbc6e59fa74567be
msgexchange-api/SIS_AODB_RMS-V0.1.md
T
zhiqiang feng 1451f86640 add unisys msg doc
2026-09-02 20:08:54 +08:00

11522 lines
687 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# AODB 和 RMS 接口规范
> **英文标题：** Interface Specification between AODB and RMS
> **项目：** CDIA T2 Project（信息系统集成工程）
> **文件版本：** 0.1
> **签发日期：** 2011 年 7 月 27 日
> **原始文件：** `SIS_AODB_RMS-V0.1.pdf`
## 文档信息
| 项目 | 内容 |
|---|---|
| Project / 项目 | CDIA T2 Project |
| Document Title / 文档标题 | Interface Specification between AODB and RMS / AODB 与 RMS 接口规范 |
| Author / 作者 | Unisys |
| Reviewed By / 审阅者 | Sury Chavali |
| 文件名 | `SIS_AODB_RMS.doc` |
| 说明 | 本文档描述 CDIA T2 项目中 AODB 与 RMS 子系统之间的接口。 |
## 修订历史
| 版本 | 范围 | 类型 | 日期 | 作者 | 说明 |
|---|---|---|---|---|---|
| 0.1 | 全文 | Draft | 27 JUL 11 | Unisys | Initial version |
> **保密提示：** 原始文档标注为 Unisys 专有资料，包含敏感且具有竞争性的内容。本 Markdown 版本仅用于原文件内容的结构化整理，不改变其保密属性。
---
## 目录
- [1 Introduction/简介](#sec-1)
- [1.1 Purpose/目的](#sec-1-1)
- [1.2 Scope/范围](#sec-1-2)
- [1.3 Definitions, Acronyms and Abbreviations/定义和缩写](#sec-1-3)
- [1.4 References/参考书目](#sec-1-4)
- [1.5 General Assumptions/假设](#sec-1-5)
- [1.6 Application Processing Clarifications/应用程序处理澄清](#sec-1-6)
- [1.6.1 Communications related/ 通信相关](#sec-1-6-1)
- [1.6.2 Operations related/ 运营相关](#sec-1-6-2)
- [1.6.3 Message content / 消息内容](#sec-1-6-3)
- [1.6.4 Resource Limitations / 资源限制](#sec-1-6-4)
- [1.6.5 Special Flight handling/特殊航班处理](#sec-1-6-5)
- [2 Interface Details/接口细节](#sec-2)
- [2.1 Interface Overview/接口总览](#sec-2-1)
- [2.2 Physical Link/物理链接](#sec-2-2)
- [2.3 RMS Prerequisite Software/RMS 前提软件](#sec-2-3)
- [2.4 Online Protocol/实时处理协议](#sec-2-4)
- [2.4.1 Connection Management/连接管理](#sec-2-4-1)
- [2.4.2 Application Protocol/应用程序协议](#sec-2-4-2)
- [2.5 Batch Protocol/批处理协议](#sec-2-5)
- [2.6 Data Item Classification/数据项分类](#sec-2-6)
- [2.6.1 Static Data Items/静态数据项](#sec-2-6-1)
- [2.6.2 Summary of Data items from AODB to RMS/数据项从 AODB 到 RMS](#sec-2-6-2)
- [2.6.3 Data items from RMS to AODB/数据项从 RMS 到 AODB](#sec-2-6-3)
- [2.7 Message Flow/消息流](#sec-2-7)
- [2.8 Generic Message Formats/消息格式](#sec-2-8)
- [2.8.1 Meta Data Section/ Meta 数据段](#sec-2-8-1)
- [2.8.2 Message Body Section/消息主体段](#sec-2-8-2)
- [3 AODB to RMS Event Details/AODB 到 RMS 事件](#sec-3)
- [3.1 AODB country codes event/ AODB 国家代码事件](#sec-3-1)
- [3.1.1 Event Attributes/事件属性](#sec-3-1-1)
- [3.1.2 Event Message Format/事件消息格式](#sec-3-1-2)
- [3.1.3 Event Message Sample/事件消息例子](#sec-3-1-3)
- [3.2 AODB airport codes event/ AODB 机场代码事件](#sec-3-2)
- [3.2.1 Event Attributes/事件属性](#sec-3-2-1)
- [3.2.2 Event Message Format/事件消息格式](#sec-3-2-2)
- [3.2.3 Event Message Sample/事件消息例子](#sec-3-2-3)
- [3.3 AODB airline codes event/ AODB 航空公司代码事件](#sec-3-3)
- [3.3.1 Event Attributes/事件属性](#sec-3-3-1)
- [3.3.2 Event Message Format/事件消息格式](#sec-3-3-2)
- [3.3.3 Event Message Sample/事件消息例子](#sec-3-3-3)
- [3.4 AODB aircraft codes event/ AODB 飞机代码事件](#sec-3-4)
- [3.4.1 Event Attributes/事件属性](#sec-3-4-1)
- [3.4.2 Event Message Format/事件消息格式](#sec-3-4-2)
- [3.4.3 Event Message Sample/事件消息例子](#sec-3-4-3)
- [3.5 AODB registration codes event/ AODB 注册码事件](#sec-3-5)
- [3.5.1 Event Attributes/事件属性](#sec-3-5-1)
- [3.5.2 Event Message Format/事件消息格式](#sec-3-5-2)
- [3.5.3 Event Message Sample/事件消息例子](#sec-3-5-3)
- [3.6 AODB organization codes event/ AODB 机构代码事件](#sec-3-6)
- [3.6.1 Event Attributes/事件属性](#sec-3-6-1)
- [3.6.2 Event Message Format/事件消息格式](#sec-3-6-2)
- [3.6.3 Event Message Sample/事件消息例子](#sec-3-6-3)
- [3.7 AODB flight type codes event/ AODB 航班类型代码事件](#sec-3-7)
- [3.7.1 Event Attributes/事件属性](#sec-3-7-1)
- [3.7.2 Event Message Format/事件消息格式](#sec-3-7-2)
- [3.7.3 Event Message Sample/事件消息例子](#sec-3-7-3)
- [3.8 AODB terminal codes event/ AODB 航站楼代码事件](#sec-3-8)
- [3.8.1 Event Attributes/事件属性](#sec-3-8-1)
- [3.8.2 Event Message Format/事件消息格式](#sec-3-8-2)
- [3.8.3 Event Message Sample/事件消息例子](#sec-3-8-3)
- [3.9 AODB gate codes event/ AODB 登机门代码事件](#sec-3-9)
- [3.9.1 Event Attributes/事件属性](#sec-3-9-1)
- [3.9.2 Event Message Format/事件消息格式](#sec-3-9-2)
- [3.9.3 Event Message Sample/事件消息例子](#sec-3-9-3)
- [3.10 AODB stand codes event/ AODB 机位代码事件](#sec-3-10)
- [3.10.1 Event Attributes/事件属性](#sec-3-10-1)
- [3.10.2 Event Message Format/事件消息格式](#sec-3-10-2)
- [3.10.3 Event Message Sample/事件消息例子](#sec-3-10-3)
- [3.11 AODB check in counter codes event/ AODB 值机柜台代码事件](#sec-3-11)
- [3.11.1 Event Attributes/事件属性](#sec-3-11-1)
- [3.11.2 Event Message Format/事件消息格式](#sec-3-11-2)
- [3.11.3 Event Message Sample/事件消息例子](#sec-3-11-3)
- [3.12 AODB carousel codes event/ AODB 传送转盘代码事件](#sec-3-12)
- [3.12.1 Event Attributes/事件属性](#sec-3-12-1)
- [3.12.2 Event Message Format/事件消息格式](#sec-3-12-2)
- [3.12.3 Event Message Sample/事件消息例子](#sec-3-12-3)
- [3.13 AODB chute codes event/ AODB 行李传送带代码事件](#sec-3-13)
- [3.13.1 Event Attributes/事件属性](#sec-3-13-1)
- [3.13.2 Event Message Format/事件消息格式](#sec-3-13-2)
- [3.13.3 Event Message Sample/事件消息例子](#sec-3-13-3)
- [3.14 AODB resource status event/ AODB 资源状态事件](#sec-3-14)
- [3.14.1 Event Attributes/事件属性](#sec-3-14-1)
- [3.14.2 Event Message Format/事件消息格式](#sec-3-14-2)
- [3.14.3 Event Message Sample/事件消息例子](#sec-3-14-3)
- [3.15 AODB reference data response to RMS event / AODB 参考数据应答 RMS 事件](#sec-3-15)
- [3.15.1 Event Attributes/事件属性](#sec-3-15-1)
- [3.15.2 Event Message Format/事件消息格式](#sec-3-15-2)
- [3.15.3 Event Message Sample/事件消息例子](#sec-3-15-3)
- [3.16 AODB daily flight schedule event/ AODB 日航班计划事件](#sec-3-16)
- [3.16.1 Event Attributes/事件属性](#sec-3-16-1)
- [3.16.2 Event Message Format/事件消息格式](#sec-3-16-2)
- [3.16.3 Event Message Sample/事件消息例子](#sec-3-16-3)
- [3.17 AODB daily schedule response to RMS event/ AODB 日计划应答 RMS 事件](#sec-3-17)
- [3.17.1 Event Attributes/事件属性](#sec-3-17-1)
- [3.17.2 Event Message Format/事件消息格式](#sec-3-17-2)
- [3.17.3 Event Message Sample/事件消息例子](#sec-3-17-3)
- [3.18 AODB adhoc flight event/ AODB adhoc 航班事件](#sec-3-18)
- [3.18.1 Event Attributes/事件属性](#sec-3-18-1)
- [3.18.2 Event Message Format/事件消息格式](#sec-3-18-2)
- [3.18.3 Event Message Sample/事件消息例子](#sec-3-18-3)
- [3.19 AODB flight aircraft type event/ AODB 航班机型事件](#sec-3-19)
- [3.19.1 Event Attributes/事件属性](#sec-3-19-1)
- [3.19.2 Event Message Format/事件消息格式](#sec-3-19-2)
- [3.19.3 Event Message Sample/事件消息例子](#sec-3-19-3)
- [3.20 AODB flight actual time event/ AODB 航班实际时间事件](#sec-3-20)
- [3.20.1 Event Attributes/事件属性](#sec-3-20-1)
- [3.20.2 Event Message Format/事件消息格式](#sec-3-20-2)
- [3.20.3 Event Message Sample/事件消息例子](#sec-3-20-3)
- [3.21 AODB flight boarding time event/ AODB 航班登机时间事件](#sec-3-21)
- [3.21.1 Event Attributes/事件属性](#sec-3-21-1)
- [3.21.2 Event Message Format/事件消息格式](#sec-3-21-2)
- [3.21.3 Event Message Sample/事件消息例子](#sec-3-21-3)
- [3.22 AODB flight chocks time event/ AODB 航班轮挡时间事件](#sec-3-22)
- [3.22.1 Event Attributes/事件属性](#sec-3-22-1)
- [3.22.2 Event Message Format/事件消息格式](#sec-3-22-2)
- [3.22.3 Event Message Sample/事件消息例子](#sec-3-22-3)
- [3.23 AODB flight type event/ AODB 航班类型事件](#sec-3-23)
- [3.23.1 Event Attributes/事件属性](#sec-3-23-1)
- [3.23.2 Event Message Format/事件消息格式](#sec-3-23-2)
- [3.23.3 Event Message Sample/事件消息例子](#sec-3-23-3)
- [3.24 AODB flight check in counter event/ AODB 航班值机柜台事件](#sec-3-24)
- [3.24.1 Event Attributes/事件属性](#sec-3-24-1)
- [3.24.2 Event Message Format/事件消息格式](#sec-3-24-2)
- [3.24.3 Event Message Sample/事件消息例子](#sec-3-24-3)
- [3.25 AODB flight carousel event/ AODB 航班行李转盘事件](#sec-3-25)
- [3.25.1 Event Attributes/事件属性](#sec-3-25-1)
- [3.25.2 Event Message Format/事件消息格式](#sec-3-25-2)
- [3.25.3 Event Message Sample/事件消息例子](#sec-3-25-3)
- [3.26 AODB flight chute event/ AODB 航班行李传送带事件](#sec-3-26)
- [3.26.1 Event Attributes/事件属性](#sec-3-26-1)
- [3.26.2 Event Message Format/事件消息格式](#sec-3-26-2)
- [3.26.3 Event Message Sample/事件消息例子](#sec-3-26-3)
- [3.27 AODB flight cancel event/ AODB 航班取消事件](#sec-3-27)
- [3.27.1 Event Attributes/事件属性](#sec-3-27-1)
- [3.27.2 Event Message Format/事件消息格式](#sec-3-27-2)
- [3.27.3 Event Message Sample/事件消息例子](#sec-3-27-3)
- [3.28 AODB flight estimated time event/ AODB 航班预计时间事件](#sec-3-28)
- [3.28.1 Event Attributes/事件属性](#sec-3-28-1)
- [3.28.2 Event Message Format/事件消息格式](#sec-3-28-2)
- [3.28.3 Event Message Sample/事件消息例子](#sec-3-28-3)
- [3.29 AODB flight delete event/ AODB 航班删除事件](#sec-3-29)
- [3.29.1 Event Attributes/事件属性](#sec-3-29-1)
- [3.29.2 Event Message Format/事件消息格式](#sec-3-29-2)
- [3.29.3 Event Message Sample/事件消息例子](#sec-3-29-3)
- [3.30 AODB flight diverted event/ AODB 航班转场事件](#sec-3-30)
- [3.30.1 Event Attributes/事件属性](#sec-3-30-1)
- [3.30.2 Event Message Format/事件消息格式](#sec-3-30-2)
- [3.30.3 Event Message Sample/事件消息例子](#sec-3-30-3)
- [3.31 AODB flight finals time event/ AODB 航班最终时间事件](#sec-3-31)
- [3.31.1 Event Attributes/事件属性](#sec-3-31-1)
- [3.31.2 Event Message Format/事件消息格式](#sec-3-31-2)
- [3.31.3 Event Message Sample/事件消息例子](#sec-3-31-3)
- [3.32 AODB flight indicator event/ AODB 航班标识事件](#sec-3-32)
- [3.32.1 Event Attributes/事件属性](#sec-3-32-1)
- [3.32.2 Event Message Format/事件消息格式](#sec-3-32-2)
- [3.32.3 Event Message Sample/事件消息例子](#sec-3-32-3)
- [3.33 AODB flight returned event/ AODB 航班返航事件](#sec-3-33)
- [3.33.1 Event Attributes/事件属性](#sec-3-33-1)
- [3.33.2 Event Message Format/事件消息格式](#sec-3-33-2)
- [3.33.3 Event Message Sample/事件消息例子](#sec-3-33-3)
- [3.34 AODB flight gate event/ AODB 航班登机门事件](#sec-3-34)
- [3.34.1 Event Attributes/事件属性](#sec-3-34-1)
- [3.34.2 Event Message Format/事件消息格式](#sec-3-34-2)
- [3.34.3 Event Message Sample/事件消息例子](#sec-3-34-3)
- [3.35 AODB flight last call time event/ AODB 航班最后通知时间事件](#sec-3-35)
- [3.35.1 Event Attributes/事件属性](#sec-3-35-1)
- [3.35.2 Event Message Format/事件消息格式](#sec-3-35-2)
- [3.35.3 Event Message Sample/事件消息例子](#sec-3-35-3)
- [3.36 AODB flight maximum passengers event/ AODB 航班最大旅客数事件](#sec-3-36)
- [3.36.1 Event Attributes/事件属性](#sec-3-36-1)
- [3.36.2 Event Message Format/事件消息格式](#sec-3-36-2)
- [3.36.3 Event Message Sample/事件消息例子](#sec-3-36-3)
- [3.37 AODB flight handling agent/ AODB 航班 服务代理事件](#sec-3-37)
- [3.37.1 Event Attributes/事件属性](#sec-3-37-1)
- [3.37.2 Event Message Format/事件消息格式](#sec-3-37-2)
- [3.37.3 Event Message Sample/事件消息例子](#sec-3-37-3)
- [3.38 AODB flight planned stands event/ AODB 航班计划机位事件](#sec-3-38)
- [3.38.1 Event Attributes/事件属性](#sec-3-38-1)
- [3.38.2 Event Message Format/事件消息格式](#sec-3-38-2)
- [3.38.3 Event Message Sample/事件消息例子](#sec-3-38-3)
- [3.39 AODB flight registration event/ AODB 航班注册号事件](#sec-3-39)
- [3.39.1 Event Attributes/事件属性](#sec-3-39-1)
- [3.39.2 Event Message Format/事件消息格式](#sec-3-39-2)
- [3.39.3 Event Message Sample/事件消息例子](#sec-3-39-3)
- [3.40 AODB flight routing event/ AODB 航班航线事件](#sec-3-40)
- [3.40.1 Event Attributes/事件属性](#sec-3-40-1)
- [3.40.2 Event Message Format/事件消息格式](#sec-3-40-2)
- [3.40.3 Event Message Sample/事件消息例子](#sec-3-40-3)
- [3.41 AODB flight turnaround event/ AODB 航班经停事件](#sec-3-41)
- [3.41.1 Event Attributes/事件属性](#sec-3-41-1)
- [3.41.2 Event Message Format/事件消息格式](#sec-3-41-2)
- [3.41.3 Event Message Sample/事件消息例子](#sec-3-41-3)
- [3.42 AODB flight terminal event/ AODB 航班航站楼事件](#sec-3-42)
- [3.42.1 Event Attributes/事件属性](#sec-3-42-1)
- [3.42.2 Event Message Format/事件消息格式](#sec-3-42-2)
- [3.42.3 Event Message Sample/事件消息例子](#sec-3-42-3)
- [3.43 AODB flight VIP passengers event/ AODB 航班 VIP 旅客事件](#sec-3-43)
- [3.43.1 Event Attributes/事件属性](#sec-3-43-1)
- [3.43.2 Event Message Format/事件消息格式](#sec-3-43-2)
- [3.43.3 Event Message Sample/事件消息例子](#sec-3-43-3)
- [3.44 AODB error to RMS event/ AODB 发向 RMS 的错误事件](#sec-3-44)
- [3.44.1 Event Attributes/事件属性](#sec-3-44-1)
- [3.44.2 Event Message Format/事件消息格式](#sec-3-44-2)
- [3.44.3 Event Message Sample/事件消息例子](#sec-3-44-3)
- [4 RMS to AODB Event Details/RMS 到 AODB 事件](#sec-4)
- [4.1 RMS flight check in counter event/ RMS 航班值机柜台事件](#sec-4-1)
- [4.1.1 Event Attributes/事件属性](#sec-4-1-1)
- [4.1.2 Event Message Format/事件消息格式](#sec-4-1-2)
- [4.1.3 Event Message Sample/事件消息例子](#sec-4-1-3)
- [4.2 RMS flight carousel event/ RMS 航班行李转盘事件](#sec-4-2)
- [4.2.1 Event Attributes/事件属性](#sec-4-2-1)
- [4.2.2 Event Message Format/事件消息格式](#sec-4-2-2)
- [4.2.3 Event Message Sample/事件消息例子](#sec-4-2-3)
- [4.3 RMS flight gate event/ RMS 航班登机门事件](#sec-4-3)
- [4.3.1 Event Attributes/事件属性](#sec-4-3-1)
- [4.3.2 Event Message Format/事件消息格式](#sec-4-3-2)
- [4.3.3 Event Message Sample/事件消息例子](#sec-4-3-3)
- [4.4 RMS flight planned stand event/ 事件](#sec-4-4)
- [4.4.1 Event Attributes/事件属性](#sec-4-4-1)
- [4.4.2 Event Message Format/事件消息格式](#sec-4-4-2)
- [4.4.3 Event Message Sample/事件消息例子](#sec-4-4-3)
- [4.5 RMS flight chute event/ RMS 航班行李传送带事件](#sec-4-5)
- [4.5.1 Event Attributes/事件属性](#sec-4-5-1)
- [4.5.2 Event Message Format/事件消息格式](#sec-4-5-2)
- [4.5.3 Event Message Sample/事件消息例子](#sec-4-5-3)
- [4.6 RMS reference data request event/ RMS 参数请求事件](#sec-4-6)
- [4.6.1 Event Attributes/事件属性](#sec-4-6-1)
- [4.6.2 Event Message Format/事件消息格式](#sec-4-6-2)
- [4.6.3 Event Message Sample/事件消息例子](#sec-4-6-3)
- [4.7 RMS daily schedule request event/ RMS 日航班计划请求事件](#sec-4-7)
- [4.7.1 Event Attributes/事件属性](#sec-4-7-1)
- [4.7.2 Event Message Format/事件消息格式](#sec-4-7-2)
- [4.7.3 Event Message Sample/事件消息例子](#sec-4-7-3)
- [4.8 RMS error to AODB event/ RMS 发送给 AODB 的错误信息事件](#sec-4-8)
- [4.8.1 Event Attributes/事件属性](#sec-4-8-1)
- [4.8.2 Event Message Format/事件消息格式](#sec-4-8-2)
- [4.8.3 Event Message Sample/事件消息例子](#sec-4-8-3)
- [5 AODB Exception Handling/AODB异常处理](#sec-5)
- [5.1 Application Errors/应用程序错误](#sec-5-1)
- [5.2 Connection Failures/连接失败](#sec-5-2)
- [5.3 System Operations Logging/系统操作日志](#sec-5-3)
- [6 RMS Exception Handling/RMS 异常处理](#sec-6)
- [6.1 Application Errors/应用程序错误](#sec-6-1)
- [6.2 Connection Failures/连接失败](#sec-6-2)
- [6.3 System Operations Logging/系统操作日志](#sec-6-3)
---
<!-- 原 PDF 第 10 页 -->
<a id="sec-1"></a>
## 1 Introduction/简介
<a id="sec-1-1"></a>
### 1.1 Purpose/目的
As part of the CDIA T2 Project various airport systems like BHS, FIDS, RMS need to
interact and exchange information with the central Airport Operations Database
(AODB). This document contains the details of the interface between AODB and RMS.
This will act as basis for software development of the AODB to RMS interface by
Unisys and RMS to AODB interface by RMS . RMS is the resource allocation and
management system for the CDIA T2 Project.
作为 CDIA T2 项目各个机场系统的一部分，如 BHS，FIDS，RMS 需要与机场的运营数
据库（AODB）连接进行数据交换。本文档描述AODB与RMS之间的接口详细情况，作
为Unisys开发AODB与RMS接口软件以及RMS 开发RMS与AODB接口软件的基础。
RMS是 CDIA T2 项目的资源分配和管理系统。
The main purpose of the interface is to send schedules, flight operational data and
reference data from AODB to RMS to setup the basic data needed for resource
allocation in the airport. Using same interface AODB will receive resource allocations
from RMS and distribute it to other Airport systems as appropriate.
本 AODB-RMS接口主要是从 AODB 向RMS提供计划数据、航班运营数据以及参考数
据，从而为机场的资源分配提供所需的数据。使用同样的接口，AODB 将从 RMS 接收
资源分配并相应发布到机场其它系统。
<a id="sec-1-2"></a>
### 1.2 Scope/范围
This document covers the following items in the AODB <-> RMS interface:
本文档描述的AODB <->RMS接口主要包括：
 Identify Data items to be exchanged between AODB and RMS
确定AODB与RMS间交换的数据项。
 Message formats to facilitate exchange of above data items
以上数据交换的报文格式。
 Application process Flows including normal, error / exception situations
应用系统处理流程包括正常、错误/例外情况。
 Connectivity including protocol, events, triggers etc
连接的协议、事件、触发器等。
<a id="sec-1-3"></a>
### 1.3 Definitions, Acronyms and Abbreviations/定义和缩写
```text
SNO Definition/Acronym Description
缩写 描述
1. CDIA Chengdu Shuangliu International Airport
成都双流国际机场
SNO Definition/Acronym Description
缩写 描述
2. GOIS Ground Operational Information System
地面操作信息系统
3. T2 Terminal 2 at CDIA
成都双流国际机场第二航站楼
4. UCL Unisys China Ltd
Unisys 中国有限公司
5. Unisys Unisys China Ltd
Unisys 中国有限公司
6. WBS Work breakdown structure
工作分解结构
7. AODB Airport Operations Database. Central repository of
all the airports operational data.
机场运营的数据库. 机场操作运行的所有数据的中
央数据库.
8. IATA International Air Transport Association
国际航空运输协会
9. CIIMS Central Integrated Information Management
System
中央集成信息管理系统
10. RMS Resource Management System
资源管理系统
```
<a id="sec-1-4"></a>
### 1.4 References/参考书目
```text
SNO Document Issuer Date
文档 发行者 日期
1. NA
```
<a id="sec-1-5"></a>
### 1.5 General Assumptions/假设
1. This document is prepared based on the Chengdu Airport Interface Specification
(SIS) provided by Unisys to RMS , the initial RMS AODB Interface Specification
submitted by RMS (RMS system vendors) as well as subsequent discussions
between Unisys and RMS recorded in the comments document.
本文档的准备是基于 Unisys 和RMS系统供应商提供的初始 RMS AODB 接口文档，
由 RMS(RMS系统供应商)提供的初始的RMS AODB 接口描述以及后续 Unisys 和
RMS 系统供应商在备注文档中的记录。
2. Any changes to data items or interfaces agreed upon will affect the scope and
contents of this document.
任何对已经达成一致的数据项或者接口的修改将影响本文档的范围和内容。
<!-- 原 PDF 第 12 页 -->
<a id="sec-1-6"></a>
### 1.6 Application Processing Clarifications/应用程序处理澄清
<a id="sec-1-6-1"></a>
#### 1.6.1 Communications related/ 通信相关
1. CIIMS event codes are identified in Event attributes as sender <subsystem> +
<event type> for e.g. AODBSCHD. Routing Event ID for CIIMS API is the same as
the CIIMS Event Code mentioned in this document. RMS will use these codes
while sending messages to AODB via CIIMS. Same way AODB will use these while
sending messages to RMS via CIIMS.
CIIMS 事件码在发送事件属性时的标识为<子系统>+<事件类型>如 AODBSCHD。
CIIMS API 的路由事件 ID 与本文档中的 CIIMS 事件码相同。RMS在通过 CIIMS 向
AODB发送报文时使用这些代码。同样AODB通过 CIIMS 向RMS发送事件时也使用
这些代码。
2. Both AODB and RMS will support basic operational GUI to view messages
exchanged in either side of the interface. This is so that RMS can show what
messages were sent, when to AODB and also what messages were received when
from AODB. The same interface logic applies when AODB sends/receives
messages from RMS. RMS will provide a log file that will show messages sent and
received by RMS from AODB. There will be no GUI from RMS side with which to
view the log file, however Unisys viewer can be used for same.
AODB与RMS都支持在自己的系统中使用基本的操作 GUI 查看接口报文。所以RMS
可以显示发送给 AODB 的报文，也可以查看从AODB接受的报文。AODB从RMS接
受/发送报文的接口逻辑也是一样的。RMS 将提供日志文件显示收发的消息。RMS
方不会有 GUI 查看日志。但是 Unisys 查看器可以实现该功能。
<a id="sec-1-6-2"></a>
#### 1.6.2 Operations related/ 运营相关
1. For all data items marked as AODB as originator in this document (be it reference
data, schedules or operational data), subsystems should be able to treat the latest
data from AODB as best and overwrite their existing local data. Any local data edits
for these data items made within the subsystems themselves, are not expected to
be sent back to AODB. So it is suggested in the interest of overall airport
operations coordination, functions for local data edit in subsystems are disabled
completely and used only in emergency cases when AODB/CIIMS are not
available.
对本文档中所有AODB发起的数据项（参考数据、航班计划和运营数据），子系统应
该使用从AODB接收的最新数据覆盖本地的原数据，不希望将任何在本地修改过的这
些数据发回给AODB，为了整个机场运行的协调性，我们建议在子系统中完全禁止本
地修改数据的功能，仅当 AODB/CIIMS 不可用的紧急情况时才使用。
2. For all data items marked as RMS as originator in this document (only for flight
operational data) it is likely that the AODB daily schedule contains the same data.
RMS should be able to process these data items and update its system locally. If
such data items cause any logic conflict within RMS, then these are expected to be
handled manually within scope of RMS using appropriate error mechanisms.
对本文档中所有RMS发起的所有数据项有可能在AODB日航班计划中也包括。RMS
可以处理这些数据项并在本地系统中更新。如果这些数据项引起RMS系统的冲突，
应该在RMS范围中使用相应的错误机制进行手工处理。
<a id="sec-1-6-3"></a>
#### 1.6.3 Message content / 消息内容
<!-- 原 PDF 第 13 页 -->
1. All XML tags can be categorized into three types:
所有的 XML 标签可以分为三类：
a. M = Mandatory, means the TAG will always be present with a proper non-
empty value. This is used for mandatory fields like FLID.
M＝必需。表示该标签必须存在且包含一个非空值。用于必需的字段如 FLID。
b. P = Present, means the TAG will always be present but can contain an empty
value. This is used for normal data fields which can also be unallocated. For
e.g. if an ESTT TAG has an empty value, it is valid and means the previous
estimated time value is being deleted.
P＝存在。表示该标签一直存在但可以包含空值。用于可以接触指派的普通字
段。例如，如果 ESTT 标签为空，是合法的，表示预计时间被删除了。
c. O = Optional, means the TAG will be present only when there is data value
for the data item corresponding to that TAG in AODB.
O＝可选项。表示该标签字段只有在 AODB 中存在对应值时才会存在。
<a id="sec-1-6-4"></a>
#### 1.6.4 Resource Limitations / 资源限制
Below are the existing AODB enforced resource limitations. These would be changed
as and when the requirement changes in CDIA.
下面描述的是AODB已有的强制资源限制，随着 CDIA 需求的变化而改变。
SNO Flight Resource Limitation and Description
航班资源 限制和描述
1. Stands/停机位 Maximum 1 current stand per flight
每个航班最多拥有一个当前停机位
Maximum 9 planned stands per flight
每个航班最多拥有九个计划停机位
Any number of actual stand movements
per flight.
每个航班可以有任意数量的实际停机位移
动。
2. Boarding Gates/登机门 Maximum 99 per flight including
domestic, international and mixed. Each
Gate has one Gated time, one Boarding
Open, one Boarding Close and one
Gate Close timings
包含国内，国际或混合航班的每个航班最
多拥有99个登机门。每个登机门具有一
个登机门已分配，一个登机开始，一个登
机结束和一个登机门关闭的时间项。
3. Check In Counters/值机柜台 Maximum 99 limit per flight. Each
Counter has one Counter Open and one
Counter Close Timings
对于每个航班没有限制。每个值机柜台拥
有一个柜台开启和一个关闭的时间项。
Each Counter will also support
<!-- 原 PDF 第 14 页 -->
SNO Flight Resource Limitation and Description
航班资源 限制和描述
maximum 3 defined classes and they
will be F (First), C (Business) and Y
(Economy). An undefined class X will
also be supported. Counter can be
opened and closed separately for these
4 classes for a flight.
每个值机 柜台将 最大 支持 3个定义 的等
级，它们将是F（头等），C（商务）和Y
（经济）。一个未定义的等级X也会被支
持。对一个航班柜台可以为这4个等级分
别地开启和关闭。
4. Baggage Carousel (Arrivals)/行李转盘 Maximum 99 per flight including
（到港） domestic, international and mixed. Each
Carousel has one Carousel Open, one
Carousel Close, one First Bag and one
Last Bag timings.
包含国内，国际或混合航班的每个航班最
多拥有99个行李转盘。每个行李转盘拥
有一个转盘开启，一个转盘关闭，一个首
行李和一个末行李时间项。
Only supported for arrivals
只支持到港航班
Each Carousel will also support
maximum 3 defined classes and they
will be F (First), C (Business) and Y
(Economy). An undefined class X will
also be supported. Carousel can be
opened and closed separately for these
4 classes for a flight.
每个行李提取转盘将最大支持3个定义的
等级，它们将是F（头等），C（商务）
和Y（经济）。一个未定义的等级X也会
被支持。对一个航班行李提取转盘可以为
这4个等级分别地开启和关闭。
5. Flight Routing (Steps)/航线 6 airports excluding current station CTU
除了当前站成都以外的六个机场
6. Code shares (for a Master Flight)/代码共 A master can have any number of code
享 shares.
一个主航班可以拥有多个代码共享航班
号。
Code share can have only one master.
代码共享只能拥有一个主航班。
7. Code share resources / 代码共享资源 Code share can have following data
fields separate from Master Flight. All
other data fields are shared with Master
Flight.
代码共享航班可以有下列与主航班分离的
<!-- 原 PDF 第 15 页 -->
SNO Flight Resource Limitation and Description
航班资源 限制和描述
字段。所有其它数据字段都与主航班共
享。
Check in Counter Data / 值机柜台数据
Passenger Count Data / 旅客数量数据
8. Flight Number Field/航班号字段 12 characters including operator code,
flight number and suffix.
除了承运人代码外的包含前缀/后缀的12
位字符。
<a id="sec-1-6-5"></a>
#### 1.6.5 Special Flight handling/特殊航班处理
1. Code shares are treated as separate flights in AODB.
在AODB中，代码共享航班被当作独立的航班进行处理。
a. A separate XML flight record will be sent for each code share defined in AODB.
会为每一个在 AODB 中定义的共享代码航班发送一个 XML 航班记录。
b. In AODB some fields (like estimated time, aircraft type) are shared between
master flight and code share, while others are independent fields (like counter
allocation data/passenger counts).
在 AODB 中，有些字段（如预计时间，航空器类型）在主航班和代码共享航班
是共享的。而其它字段是独立的字段（如柜台分配数据、乘客数量等）。
c. Separate FLOP flight events will be sent for code share as well as master flight,
irrespective of whether shared fields or independent fields are being updated in
AODB.
对于主航班和代码共享航班，FLOP 航班事件会被独立地发送，不管是共享字段
被更新或是独立的字段被更新。
d. If a master flight is deleted in AODB all its code shares will be deleted first. So
AODB will send FDEL event for code shares first and will send same for master
flight. If the sequence is out of order, RMS will raise an EROR to AODB.
如果要在 AODB 中删除一个主航班，它的共享航班要首先被删除。也就是
AODB 将为代码共享航班的删除发送 FDEL 事件然后为主航班发送同样的消息。
如果不按这个顺序的话，RMS将向 AODB 发送一个 EROR 消息。
2. Mixed flights
混合航班
a. Mixed flights (passing through a domestic segment in China and then an
international segment) will be treated as single flight records in AODB with flight
indicator set to M. Flight schedules will be sent as one record.
在 AODB 中，混合航班（在国内有一段然后是一段国际）会被当作一个航班记
录，它的航班标识被设为 M。航班计划会被作为一个记录发送。
b. All flight events FLOP will be sent from AODB for the single flight record.
Similarly AODB expects events for mixed flights against a single FLID reported
by AODB in the schedule event.
所有航班事件 FLOP 将针对一个航班记录从 AODB 发送。同样的，AODB 认为
混合航班事件针对于在计划事件中由 AODB 发送的一个 FLID。
<!-- 原 PDF 第 16 页 -->
c. Subsystems which need to treat the domestic and international segments of a
mixed flight separately need to include special handling logic to process mixed
flights.
对于需要分别处理混合航班国内和国际部分的子系统则需要包含特殊的逻辑来处
理混合航班。
3. ”return to base” departure flights
“返回基地”离港航班
a. Difference from air return is that new adhoc flights will not be added and
original flight is assumed to have been delayed.
与空返不同的是不会添加新航班，原航班被认为是已经被延误。
b. If CDIA operator sets Ground return flag, AODB will send a „G‟ code
indicating its ground return.
如果 CDIA 操作员设置地返标记，AODB 将发送一个“G”代码标识它的
地返。
c. In this (unlike Air returns documented below), the flight number does not
change.
在地返时（不像下面所描述的空返），航班号不发生变化。
4. “return from air” departure flights
“从空中返回”离港航班
TBD
5. Diverted flights / 备降航班
a. If a scheduled arrival flight to CTU gets diverted elsewhere, CDIA will
reset the STA/ETA and set the diverted status in AODB.
如果一个计划降落在 CTU 的航班备降到其它地方，CDIA 将设置 STA/ETA
并且在 AODB 中设置备降状态。
b. If a scheduled arrival flight to another airport is diverted towards CTU,
CDIA will treat this as an adhoc arrival into CTU.
如果一个计划降落在其它机场的航班备降到 CTU，CDIA 将其作为新增到
港航班处理。
i. A new adhoc arrival with original flight‟s flight type and diverted
status set, will be created in AODB.
在 AODB 中，一个新的到港航班将被创建。它的航班类型与原航
班类型相同，备降状态被设置。
ii. A new adhoc departure with flight type indicating diversion and
diverted status set will be created in AODB.
在 AODBzhong，一个新的离港航班将被创建。航班类型指示它是
一个备降航班并且备降标识被设置。
c. If a scheduled departure from CTU, is diverted elsewhere post departure.
如果一个计划从 CTU 离港的航班在出发后备降到别的地方。
i. Diverted status will be set in AODB, which triggers a diverted
message.
在 AODB 中设置其备降状态，这将出发一个备降消息。
<!-- 原 PDF 第 17 页 -->
<a id="sec-2"></a>
## 2 Interface Details/接口细节
<a id="sec-2-1"></a>
### 2.1 Interface Overview/接口总览
1. AODB and RMS will use the CIIMS send API which implement through JDBC
Adapter to send events to each other. Refer CIIMS SDK Programmer Reference
Manual document for CIIMS API details.
AODB 和 RMS 使用通过 JDBC Adapter 实现的 CIIMS 发送 API 来相互发送事件。
CIIMS API 详情参考 CIIMS SDK 程序员参考手册文档。
2. An event is typically associated with one data item like ETA, ETD etc.
一个事件一般是与一个数据项相关，如 ETA，ETD 等。
3. Events are delivered as XML formatted messages. The same message format
could be reused to deliver different event types, across different subsystems.
Refer section below on general message formats.
事件发送使用 XML 格式报文。在不同的子系统中的不同的事件类型可以重复使用同
样的报文格式。参考下文的一般报文格式部分。
4. AODB and RMS will use the CIIMS receive API which implement through JDBC
Adapter to receive events. AODB 和 RMS 使用通过 JDBC Adapter 实现的 CIIMS
接收 API
5. Error handling is to be done at an application level.
错误处理在应用层实现。
6. Unisys will prepare a RMS specific configuration profile to CIIMS during the
integration phase. This profile will detail out RMS specific events, event attributes
like Acknowledgment, Expiry, and Priority etc. Inputs for creating such a profile
can be gathered from the various events described in this document.
Unisys 在集成阶段时会准备一个 RMS 与 CIIMS 的详细配置文件。该文件详细描述
RMS 的事件，事件属性如确认、有效期和优先级等。该文件根据本文档描述的各种
事件产生。
<a id="sec-2-2"></a>
### 2.2 Physical Link/物理链接
1. AODB and RMS will not have any direct physical link.
AODB 与 RMS 之间不存在任何直接的物理链接。
2. AODB and RMS will exchange XML messages via the CIIMS middleware.
AODB 与 RMS 通过 CIIMS 中间件交换 XML 报文。
3. RMS, AODB and CIIMS will run as separate software subsystems and will be
connected to the CDIA GOIS backbone Ethernet LAN to realize physical line
communication.
RMS、AODB 和 CIIMS 是各自独立的子系统，都联入 CDIA GOIS 骨干以太网实现
物理上的通讯。
<a id="sec-2-3"></a>
### 2.3 RMS Prerequisite Software/RMS 前提软件
<!-- 原 PDF 第 18 页 -->
SNO Software Component Provided By
软件部件 提供者
1. RMS Development OS = RMS
2. RMS Development Language / Compiler = RMS
3. JVM = JRE 1.6 or higher RMS
4. JDBC Adapter including relevant CIIMS Java SDK Unisys
5. CIIMS Simulator and test harness Unisys
<a id="sec-2-4"></a>
### 2.4 Online Protocol/实时处理协议
In online mode RMS and AODB will be connected to CIIMS middleware to exchange
messages. All interfaces between RMS and CIIMS will be governed by RMS
configuration profile submitted to CIIMS. This includes parameters like Message Expiry,
Acknowledgement Options, Logging Options, and Message Filters etc. The relevant
parameters indicated in this document under various events are just pointers for setting
up RMS/AODB configuration profile in CIIMS.
实时模式时，AODB 与RMS通过 CIIMS 中间件连接交换报文。所有RMS与 CIIMS 之间
的通信使用RMS提交给 CIIMS 的配置文件管理，包括参数如报文有效期、确认选项、报
文优先级、日志选项、报文过滤等。该配置文件中的不同事件的相关参数仅适用于设置
CIIMS 的RMS/AODB 的配置。
<a id="sec-2-4-1"></a>
#### 2.4.1 Connection Management/连接管理
<a id="sec-2-4-1-1"></a>
##### 2.4.1.1 Connection/连接
<a id="sec-2-4-1-1-1"></a>
###### 2.4.1.1.1 RMS Connections / RMS 连接
RMS will depend on JDBC Adapter for communication with CIIMS. JDBC Adapter will
maintain two connections to CIIMS as follows:
RMS 与 CIIMS 的连接使用 JDBC Adapter。JDBC Adapter 与 CIIMS 的连接有 2 种：
1. A connection to send messages from RMS to RMS via CIIMS.
RMS 通过 CIIMS 向RMS发送报文的连接。
2. A connection to receive RMS messages from CIIMS.
从 CIIMS 接收RMS报文的连接。
JDBC Adapter will use the CIIMS API return codes to determine a successful
connection with CIIMS.
JDBC Adapter 使用 CIIMS API 返回码判断与 CIIMS 的连接是否成功。
JDBC Adapter will ensure the connection with CIIMS is maintained on a 24x7 basis and
if the connection fails due to any error the JDBC Adapter will reconnect to CIIMS
automatically (after waiting for a configurable wait interval).
JDBC Adapter 将保证与 CIIMS 的连接是 24×7 的，任何原因引起的连接中断，该
JDBC Adapter 应该自动与 CIIMS 重新连接（在指定的重试时间间隔后）。
<!-- 原 PDF 第 19 页 -->
<a id="sec-2-4-1-1-2"></a>
###### 2.4.1.1.2 AODB Connections/AODB 连接
AODB will depend on JDBC Adapter for communication with CIIMS. JDBC Adapter will
maintain two connections to CIIMS as follows:
AODB 与 CIIMS 的连接使用 JDBC Adapter。 JDBC Adapter 与 CIIMS 的连接有 2 种：
1. A connection to send messages from AODB to RMS via CIIMS.
AODB 通过 CIIMS 向RMS发送报文的连接。
2. A connection to receive RMS messages from CIIMS.
从 CIIMS 接收RMS报文的连接。
JDBC Adapter will use the CIIMS API return codes to determine a successful
connection with CIIMS.
JDBC Adapter 使用 CIIMS API 返回码判断与 CIIMS 的连接是否成功。
JDBC Adapter will ensure the connection with CIIMS is maintained on a 24x7 basis and
if the connection fails due to any error the JDBC Adapter will reconnect to CIIMS
automatically (after waiting for a configurable wait interval).
JDBC Adapter 将保证与 CIIMS 的连接是 24×7 的，任何原因引起的连接中断，该
JDBC Adapter 应该自动与 CIIMS 重新连接（在指定的重试时间间隔后）。
<a id="sec-2-4-1-2"></a>
##### 2.4.1.2 Keep Alive/保持连接
<a id="sec-2-4-1-2-1"></a>
###### 2.4.1.2.1 RMS Keep Alive / RMS 保持连接
RMS will depend on SQL connection for keep alive on the database connection.
RMS将依靠 SQL 连接保持与数据库连接。
RMS will depend on the JDBC Adapter for sending keep alive to CIIMS. Each JDBC
Adapter connection will monitor the last access time to CIIMS and also retrieve the
connection time out value from CIIMS. If the JDBC Adapter finds there was no
communication with CIIMS for a long period and the connection with CIIMS will expire
soon, the JDBC Adapter will send a keep alive to CIIMS to retain the connection.
RMS将依靠 JDBC Adapter 发送 keep alive 到 CIIMS。每个 JDBC Adapter 连接会监控
与 CIIMS 最后的访问时间并从 CIIMS 中读取连接超时的值，如果 JDBC Adapter 发现与
CIIMS 长时间没有通信而且与 CIIMS 的连接将要过期， JDBC Adapter 要向 CIIMS 发送
一个保持连接来保留链接。
<a id="sec-2-4-1-2-2"></a>
###### 2.4.1.2.2 AODB Keep Alive
AODB will depend on SQL connection for keep alive on the Oracle SQL database
connection.
AODB 将依靠 SQL 连接保持与 Oracle SQL 数据库连接。
AODB will depend on the JDBC Adapter for sending keep alive to CIIMS. Each JDBC
Adapter connection will monitor the last access time to CIIMS and also retrieve the
<!-- 原 PDF 第 20 页 -->
connection time out value from CIIMS. If the JDBC Adapter finds there was no
communication with CIIMS for a long period and the connection with CIIMS will expire
soon, the JDBC Adapter will send a keep alive to CIIMS to retain the connection.
AODB 将依靠 JDBC Adapter 发送 keep alive 到 CIIMS。每个 JDBC Adapter 连接会监
控与 CIIMS 最后的访问时间并从 CIIMS 中读取连接超时的值，如果 JDBC Adapter 发现
与 CIIMS 长时间没有通信而且与 CIIMS 的连接将要过期， JDBC Adapter 要向 CIIMS 发
送一个保持连接来保留链接。
<a id="sec-2-4-1-3"></a>
##### 2.4.1.3 Disconnection/断开连接
<a id="sec-2-4-1-3-1"></a>
###### 2.4.1.3.1 RMS Disconnection / RMS 断开连接
RMS will manage database connection/disconnection internally.
AODB 将在内部管理数据库连接/断开连接。
RMS will depend on JDBC Adapter for gracefully disconnecting from CIIMS whenever
a software shutdown is requested or when critical errors are encountered.
AODB 将依赖 JDBC Adapter 优雅地从 CIIMS 断开连接，无论何时需要关闭软件或遇到
关键的错误。
<a id="sec-2-4-1-3-2"></a>
###### 2.4.1.3.2 AODB Disconnection / AODB 断开连接
AODB will manage database connection/disconnection internally.
AODB 将在内部管理数据库连接/断开连接。
AODB will depend on JDBC Adapter for gracefully disconnecting from CIIMS whenever
a software shutdown is requested or when critical errors are encountered.
AODB 将依赖 JDBC Adapter 优雅地从 CIIMS 断开连接，无论何时需要关闭软件或遇到
关键的错误。
<a id="sec-2-4-2"></a>
#### 2.4.2 Application Protocol/应用程序协议
<a id="sec-2-4-2-1"></a>
##### 2.4.2.1 Message Acknowledgments/消息响应
Following modes of acknowledgment are supported in the interface:
接口支持以下的确认模式。
<a id="sec-2-4-2-1-1"></a>
###### 2.4.2.1.1 Between RMS and CIIMS/RMS 与 CIIMS 之间
For events RMS want to ensure the message sent has been successfully delivered to
AODB, it has to set the acknowledge parameter in the RMS CIIMS configuration file for
these events. After sending these events, RMS will wait for a CIIMS acknowledgment.
要确保RMS的事件在给AODB的报文中发送成功，需要在RMS CIIMS配置文件中对这些
事件设置确认参数。事件发送后，RMS会等待CIIMS的确认。
<a id="sec-2-4-2-1-2"></a>
###### 2.4.2.1.2 Between AODB and CIIMS/AODB 与 CIIMS 之间
<!-- 原 PDF 第 21 页 -->
Whenever AODB sends out messages to RMS (as a part of broadcast event to one or
more subsystems in airport network), AODB will not wait for a CIIMS acknowledgment
to ensure the message has been successfully delivered to RMS. So the AODB CIIMS
JDBC Adapter does not support the acknowledgment feature.
当 AODB 向RMS发送报文时（向机场网络中一个或多个子系统发送的广播事件的一部
分），AODB 不会等待 CIIMS 的发送RMS成功确认。所以 JDBC Adapter 不支持确认报
文特性。
<a id="sec-2-4-2-1-3"></a>
###### 2.4.2.1.3 Between RMS and AODB / RMS 与 AODB 之间
There will be no other explicit application level acknowledgments between RMS and
AODB. Once a message is received from RMS/AODB by AODB/RMS, the message
will be processed locally. If the message gets lost thereafter or encounters an error
while processing, manual operator intervention will be required to fix the problem.
在RMS 与 AODB 之间没有其他明确的应用级的确认。当 AODB/RMS收到RMS/AODB
的报文时，报文将在本地进行处理。如果其后处理中报文丢失或出现错误，需要操作员
手工改正问题。
<a id="sec-2-4-2-2"></a>
##### 2.4.2.2 Message Processing/消息处理
<a id="sec-2-4-2-2-1"></a>
###### 2.4.2.2.1 RMS Incoming message processing/RMS 接收报文处理
JDBC Adapter in receive mode will be an independent program executing on its own
parallel context with the only job of retrieving messages intended for RMS from CIIMS
and storing them into the CMINMSGS table.
JDBC Adapter在接收模式时，是一个独立的程序，运行自己的并行处理程序，只接收从
CIIMS接收发给RMS的报文，并存储在CMINMSGS表中。
RMS application will implement a polling mechanism to look for fresh messages in the
CMINMSGS table and execute relevant RMS specific business logic processing based
on message content.
RMS应用系统执行一个轮询机制来检查CMINMSGS表中的新报文，然后根据报文内容执
行相关的RMS业务处理流程。
<a id="sec-2-4-2-2-2"></a>
###### 2.4.2.2.2 RMS Outgoing message processing/RMS发送报文处理
RMS application will include necessary mechanisms to generate out going messages
to the COUTMSGS interface table, based on agreed interface business logic between
RMS and AODB.
RMS应用系统有一个产生发送报文到COUTMSGS接口表的机制，是基于RMS与AODB
业务处理的协议接口。
JDBC Adapter in send mode will be an independent program executing on its own
parallel context with the only job of reading RMS messages from COUTMSGS table
and sending them out to CIIMS.
<!-- 原 PDF 第 22 页 -->
JDBC Adapter在发送模式时，是一个独立的程序，运行自己的并行处理程序，只从
COUTMSGS表中读取RMS的报文，并发送给CIIMS。
Message sent from RMS will not implement CIIMS message acknowledgements.
从RMS发送的消息将不执行CIIMS报文的确认。
<a id="sec-2-4-2-2-3"></a>
###### 2.4.2.2.3 AODB Incoming message processing/AODB 接收报文处理
JDBC Adapter in receive mode will be an independent program executing on its own
parallel context with the only job of retrieving messages intended for AODB from CIIMS
and storing them into the CMINMSGS table.
JDBC Adapter在接收模式时，是一个独立的程序，运行自己的并行处理程序，只接收从
CIIMS接收发给AODB的报文，并存储在CMINMSGS表中。
AODB application will implement a polling mechanism to look for fresh messages in the
CMINMSGS table and execute relevant AODB specific business logic processing
based on message content.
AODB应用系统执行一个轮询机制来检查CMINMSGS表中的新报文，然后根据报文内容
执行相关的AODB业务处理流程。
<a id="sec-2-4-2-2-4"></a>
###### 2.4.2.2.4 AODB Outgoing message processing/AODB 发送报文处理
AODB application will include necessary mechanisms to generate out going messages
to the COUTMSGS interface table, based on agreed interface business logic between
RMS and AODB.
AODB应用系统有一个产生发送报文到COUTMSGS接口表的机制，是基于RMS与AODB
业务处理的协议接口。
JDBC Adapter in send mode will be an independent program executing on its own
parallel context with the only job of reading AODB messages from COUTMSGS table
and sending them out to CIIMS.
JDBC Adapter在发送模式时，是一个独立的程序，运行自己的并行处理程序，只从
COUTMSGS表中读取AODB的报文，并发送给CIIMS。
Message sent from AODB will not implement CIIMS message acknowledgements.
从AODB发送的消息将不执行CIIMS报文的确认。
<a id="sec-2-4-2-3"></a>
##### 2.4.2.3 Message Buffering/消息缓冲
<a id="sec-2-4-2-3-1"></a>
###### 2.4.2.3.1 RMS Side/RMS 端
RMS will save all outgoing messages to its copy of COUTMSGS interface table. JDBC
Adapter in send mode will be responsible for submitting the message to CIIMS until
CIIMS can return a successful sent return code on the send call.
<!-- 原 PDF 第 23 页 -->
RMS 将所有发出的消息拷贝到它的COUTMSGS接口表中。JDBC Adapter在发送模式
时，负责提交发送的报文给CIIMS直到CIIMS返回成功发送返回码。
JDBC Adapter in receive mode will be responsible for clearing the message from the
CIIMS queues once the message has been successfully saved in the RMS copy of
CMINMSGS interface table.
在接收的报文成功存储在RMS本地的CMINMSGS接口表中后，RMS负责清除CIIMS队列
的报文。
<a id="sec-2-4-2-3-2"></a>
###### 2.4.2.3.2 AODB Side/AODB 端
AODB will save all outgoing messages to its copy of COUTMSGS interface table.
JDBC Adapter in send mode will be responsible for submitting the message to CIIMS
until CIIMS can return a successful sent return code on the send call.
AODB将所有发出的消息拷贝到它的COUTMSGS接口表中。JDBC Adapter在发送模式
时，负责提交发送的报文给CIIMS直到CIIMS返回成功发送返回码。
JDBC Adapter in receive mode will be responsible for clearing the message from the
CIIMS queues once the message has been successfully saved in the AODB copy of
CMINMSGS interface table.
在接收的报文成功存储在AODB本地的CMINMSGS接口表中后，AODB负责清除CIIMS
队列的报文。
<a id="sec-2-4-2-3-3"></a>
###### 2.4.2.3.3 CIIMS Side
Once a sender gets a successful send code from CIIMS SDK, CIIMS is expected to
keep all XML messages (from RMS or from AODB) safely, in correct order across
CIIMS restarts until the messages can be retrieved successfully by the recipient(s) or
until the messages expire.
发送程序一旦从 CIIMS SDK 接收到一个成功发送码，CIIMS 要保证所有 XML 报文（从
RMS或从 AODB 来的）在 CIIMS 重启前的安全和正确的顺序，直到该报文被接收者调
用成功或是该报文过期。
<a id="sec-2-5"></a>
### 2.5 Batch Protocol/批处理协议
No batch mode protocol is expected in the RMS and AODB interface.
RMS和AODB接口中没有批处理模式协议。
<a id="sec-2-6"></a>
### 2.6 Data Item Classification/数据项分类
<a id="sec-2-6-1"></a>
#### 2.6.1 Static Data Items/静态数据项
```text
SNO Static Data Mode of Entry
静态数据 方式
1. Flight Indicator Manual configuration in respective systems. This can be
航班标识 International (I), Domestic(D), Mixed (M) or Regional(R).
在各自的系统中手工配置。可以是国际（I）、国内（D）、混合
（M）、区域（R）。
2. Movement Manual configuration in respective systems. This can be
Indicator Arrival(A), Departure(D).
移动标识 在各自的系统中手工配置。可以是到达（A）、离港（D）。
3. Flight classes Manual configuration in respective systems.
航班分类 在各自的系统中手工配置。
F = First class/头等
C = Business class/商务
Y = Economy class/经济
X = No specific class/不定
```
<a id="sec-2-6-2"></a>
#### 2.6.2 Summary of Data items from AODB to RMS/数据项从 AODB 到 RMS
```text
SNO Data Item Description
数据项 描述
1. Reference data This typically refers to standard reference tables like airport
参考数据 codes, aircrafts types, registrations, airlines codes, flight types,
organizations, gate codes, stand codes, counter codes and
carousel codes etc that are static in nature. Resource status
changes will also be communicated as an update to the
resource reference data.
典型的标准参考数据表如机场代码、机型、注册号、航空公司代
码、航班类型、机构、登机门代码、机位代码、柜台代码和行李
转盘代码等静态数据。资源状态的改变也象资源参考数据的修改
一样通信。
RMS will use this for setting its own internal reference tables and
also validating other schedule and flight operational data sent
from AODB.
RMS 会 使 用 这 些 参 考 数 据 设 置 自 己 内 部 的 参 考 数 据表 ， 检 查
AODB发送时刻表和航班操作数据。
2. Daily schedule Will contain the next day and current day flight schedules, one
日时刻表 record per flight but entire day‟s flights in a single XML message.
Includes code share flights.
包括第二天和当天的日航班时刻表。一个航班一条记录，一个
XML 报文包括全天的航班日记录，包括代码共享航班。
RMS will use this all modules to setup flight data before doing
resource allocations.
RMS将使用所有这些数据来建立航班数据，之后进行行李传送带
分配。
3. Flight operational As a flight is being operated various data items related to the
data flight will change in AODB. RMS needs some of this information
SNO Data Item Description
数据项 描述
航班运行数据 for its internal operation. AODB will send these as separate
events, with a flight identifier and a data item body.
一个航班运行时大量的数据项会引起AODB相关航班数据的改
动。RMS需要一些相关的信息进行内部操作。AODB会单独发送
这些事件，使用航班ID和数据项。
RMS will use this for updating attributes related to a flight that
was sent as part of the daily schedule.
RMS使用这些数据更新相关航班的属性并作为航班时刻表的一部
分来发送。
All types of flight data like resource allocations, timings etc will
be covered in this.
所有类型的航班数据如资源分配、时间等都包括在内。
```
<a id="sec-2-6-3"></a>
#### 2.6.3 Data items from RMS to AODB/数据项从 RMS 到 AODB
```text
SNO Data Item Description
数据项 描述
1. Flight resource Being the main resource allocation and management system for
allocations the entire airport, RMS will be the primary source for operational
航班资源分配 data related to resource allocations namely gates, stands, check
in counters and carousels.
RMS 作为整个机场的资源分配管理系统，RMS 将是资源运行消
息源，资源包括登机门、停机位、值机柜台和行李转盘。
```
<a id="sec-2-7"></a>
### 2.7 Message Flow/消息流
NONE / 无
<a id="sec-2-8"></a>
### 2.8 Generic Message Formats/消息格式
All the messages would use the XML formatted structure as standardized by the
document type definition (DTD) referred in this document.
所有的消息将使用 XML 格式作为标准.
Message Meta Data Information about the message itself. To remain same across all
消息 Meta 数据 types of messages. This would be placed between the <META>
</META> tags
消息信息 自身 . 对 于所有 类型的消 息保持 不变 . 它 将放在 <META>
</META> 标签之间
Message Body Content of the message. For a single message type, the structure of
the body would be same across all subsystems. This is listed in
<!-- 原 PDF 第 26 页 -->
消息主体 individual message format sections.
消息内容。对于单条消息类型，主体结构对于所有的子系统都是一致
的。
<a id="sec-2-8-1"></a>
#### 2.8.1 Meta Data Section/ Meta 数据段
```text
XML Tag Description Format O/M Values
标签 描述 格式 值
META Identifies message meta data section. - M This starts a section and
Occurs once per message encloses message meta
指定消息meta数据章节.在每个消息中 data as below
出现一次 这指示了段落的开始，包
含以下数据
SNDR Sender subsystem name Char(3-4) M AODB or RMS
发送子系统名称
SEQN A sequence number set by sender for Number(6) M 1 – 999999.
tracking, debugging and Controlled by Sender
acknowledgement checking.
Wraps around
由发送者定义的序列号，用于跟踪，测
试消息。
DTTM Date and time when the message was Char(14) M YYYYMMDDHHMMSS
sent
消息发送的时间
TYPE Type of message sent. Char(4) M Described in individual
发送的消息类型 message formats
在各个消息格式中指定
STYP Subtype of message sent Char(4) M Described in individual
消息子类型 message formats
在各个消息格式中指定
```
<a id="sec-2-8-2"></a>
#### 2.8.2 Message Body Section/消息主体段
```text
Based on the data items to be exchanged between AODB and RMS, following basic
XML message formats will be supported in the message body:
基于AODB 和 RMS交换的数据项, 支持以下的XML消息格式:
SNO Message Type Message Type Description
消息类型 描述
1. ARPT Airports reference data from AODB
来自AODB的机场参考数据
2. AIRL Airlines reference data from AODB
来自AODB的航空公司参考数据
3. AIRC Aircrafts reference data from AODB
来自AODB的飞行器参考数据
SNO Message Type Message Type Description
消息类型 描述
4. REGN Registrations reference data from AODB
来自AODB的注册号参考数据
5. ORGN Organizations reference data from AODB
来自AODB的组织参考数据
6. FLTL Flight type reference data from AODB
来自AODB的航班类型参考数据
7. SLST Parking stand code reference data from AODB
来自AODB的停机位代码参考数据
8. GLST Gate code reference data from AODB
来自AODB的登机门代码参考数据
9. BLST Carousel code reference data from AODB
来自AODB的行李转盘代码参考数据
10. CLST Check in counter reference data from AODB
来自AODB的值机柜台代码参考数据
11. CHLT Chute reference data from AODB
来自AODB的行李传送带参考数据
12. SCHD Daily schedule from AODB including all flight information to be
operated the next day or current day.
从AODB发来的包含有下一天或当天所有航班运营需要的日计划。
13. FLOP Flight operational message containing specific field level
information for a flight. Individual fields will be addressed as
separate events. This will be the basic message for all individual
flight field information like flight data/timings update, resource
allocations, routing change etc
航班运营消息包含有针对一个航班的某一字段级的信息。不同字
段将被作为不同的事件。这对所有各个航班字段信息如航班数
据、时间更新、资源分配、航线变更等将是基本的消息。
AODB will use this to send all flight updates to RMS.
AODB将使用这个消息向RMS发送所有航班更新。
RMS will use this to send resource allocations to AODB.
RMS将使用这个消息向AODB资源分配信息。
14. RQFD A daily flight request to cater for RMS to solicit daily flight
information for a given time period within current operational
period from AODB.
为RMS定制的一个日航班请求以便从AODB的当前运营时间段内
获得制定时间段的日航班信息。
15. EROR Sent by either system to indicate an errors
由两个系统发送，用以指示错误。
16. RQRD A reference data request to cater for RMS to update its reference
data by soliciting information from AODB.
为RMS定制的参考数据请求用以从AODB获得信息来更新它的参
考数据
```
<a id="sec-3"></a>
## 3 AODB to RMS Event Details/AODB 到 RMS 事件
<a id="sec-3-1"></a>
### 3.1 AODB country codes event/ AODB 国家代码事件
<a id="sec-3-1-1"></a>
#### 3.1.1 Event Attributes/事件属性
```text
Message Code AODBCOUL
消息代码
Event Description This event occurs whenever any country code reference
事件描述 data is to be sent to subsystems from AODB.
当 AODB 向子系统发送任何国家代码数据时，产生该事
件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered in specific cases as below:
频率 非计划的，特定的情况下触发：
A country code reference data download in list mode is
expected to be rolled out during installation and system
configuration.
在系统安装和配置启动时，国家代码数据以列表模式下载
时。
A country code reference data download in list mode
can also be generated any time the operator decides to
distribute it from AODB to all subsystems or a given
subsystem.
在操作员由 AODB 向所有的或某个子系统以列表模式发
布国家代码时。
A country code reference data download in list mode
can also be generated to a specific subsystem any time
the operator decides to request it from the subsystem.
在操作员响应子系统的请求而向该系统以列表模式发送国
家代码时。
A country code reference data in incremental mode can
also be sent out to all subsystems whenever country
code reference data fields are updated in AODB.
AODB 中国家代码数据字段更新，向所有子系统以增量模
式发送国家代码时。
Data Range When sent from AODB in list mode one country code
数据范围 reference data XML will contain entire list of all country
codes in AODB.
当 AODB 以列表模式发送时，一个 XML 报文包括 AODB
中所有的国家代码。
When sent from AODB in incremental mode one country
code reference data XML will contain only one country
code (the one that was updated) in AODB. But the single
record will have a complete snapshot of all fields related
to that record.
当 AODB 以增量模式发送时，一个 XML 报文只包括
AODB 中的一个国家代码（修改的那个）。该记录包括国
家代码所有的字段。
Data Count One or more country code reference data records in one
数据数 XML as explained above.
如上所述，一个 XML 报文包括一个或多个国家代码数
据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority Normal
优先级 正常
Expiry 480 minutes
过期 480 分钟
Message Fragmentation Although large messages are expected it will not cross
消息分段 the maximum limit of 10MB supported by CIIMS, so no
fragmentation required.
根据估计最大报文不会超过 CIIMS 支持的 10MB 的上
限，所以不需要分段。
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments None
注释 无
Processing Exceptions RMS will ignore the following fields in the message
处理例外 RMS将忽略消息中下列字段
COUN
RMS is currently able to process and store only the first
region that the country belongs to. This means any rules
using region can only use the first region code set in
AODB.
RMS只能存储国家中的第一个区域。这表示任何区域相
关的规则AODB中只能使用第一个区域代码。
```
<a id="sec-3-1-2"></a>
#### 3.1.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M COUL
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(3-4) M DNLD = It is a download
data section. from AODB/从AODB下载
消息发送的子类型. Meta Data段的一部 RESP = It is a response
分. to a subsystem request/
响应子系统的请求
ADD = Add new record/
增加新记录
UPD = Update old
record/更新旧记录
DEL = Delete old record/
删除旧记录
RECS No of records contained in XML Number(1-4) M 0 – 9999
XML中包括的记录数
COUL Identifies start of one country record. - O This starts a new section
Repeats for each country record. and encloses the details
一条国家代码记录的开始标志。在每条 of a country. This section
记录中重复出现。 will be absent if RECS =
0
是新段落的起点，将国家
的明细括起来。如果
RECS＝0则无该部分。
COUC Country code Char(2-3) M
国家代码
COUN Country name Char(1-30) M
国家名称
CNMC Country name in Chinese Char(1-30) M
国家中文名称
REGC Region codes Char(1-6) P Will refer to region codes
区域码 reference table to be
decided by CDIA. There
could be multiple regions
since a country can
belong to more than one
region. An empty TAG
means data not available.
根据成都机场区域码数据
表决定。可以有多个区域
码，因为一个国家可以属
于多个区域。空标签表示
无可用数据。
```
<a id="sec-3-1-3"></a>
#### 3.1.3 Event Message Sample/事件消息例子
<!-- 原 PDF 第 31 页 -->
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20031010090311</DTTM>
<TYPE>COUL</TYPE>
<STYP>DNLD</STYP>
</META>
<RECS>1</RECS>
<COUL>
<COUC>PRC</COUC>
<COUN>PEOPLES REPUBLIC OF CHINA</COUN>
<CNMC>中国</CNMC>
<REGC>ASIA</REGC>
<REGC>GCHINA</REGC>
</COUL>
</MSG>
```
<a id="sec-3-2"></a>
### 3.2 AODB airport codes event/ AODB 机场代码事件
<a id="sec-3-2-1"></a>
#### 3.2.1 Event Attributes/事件属性
```text
Message Code AODBARPT
消息代码
Event Description This event occurs whenever any airport code reference
事件描述 data is to be sent to subsystems from AODB.
当 AODB 向子系统发送任何机场代码参考数据时，产生
该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered in specific cases as below:
频率 非计划的，特定的情况下触发：
An airport code reference data download in list mode is
expected to be rolled out during installation and system
configuration.
在系统安装和配置启动时，机场代码参考数据以列表模式
下载时。
An airport code reference data download in list mode
can also be generated any time the operator decides to
distribute it from AODB to all subsystems or a given
subsystem.
在操作员由 AODB 向所有的或某个子系统以列表模式发
布机场代码时。
An airport code reference data download in list mode
can also be generated to a specific subsystem any time
the operator decides to request it from the subsystem.
在操作员响应子系统的请求而向该系统以列表模式发送机
场代码时。
An airport code reference data in incremental mode can
also be sent out to all subsystems whenever airport
code reference data fields are updated in AODB.
AODB 中机场代码参考数据字段更新，向所有子系统以增
量模式发送机场代码时。
Data Range When sent from AODB in list mode one airport code
数据范围 reference data XML will contain entire list of all airport
codes in AODB.
当 AODB 以列表模式发送时，一个 XML 报文包括 AODB
中所有的机场代码。
When sent from AODB in incremental mode one airport
code reference data XML will contain only one airport
code (the one that was updated) in AODB. But the single
record will have a complete snapshot of all fields related
to that record.
当 AODB 以增量模式发送时，一个 XML 报文只包括
AODB 中的一个机场代码（修改的那个）。该记录包括机
场代码所有的字段。
Data Count One or more airport code reference data records in one
数据数 XML as explained above.
如上所述，一个 XML 报文包括一个或多个机场代码参考
数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority Normal
优先级 正常
Expiry 480 minutes
过期 480 分钟
Message Fragmentation Although large messages are expected it will not cross
消息分段 the maximum limit of 10MB supported by CIIMS, so no
fragmentation required.
根据估计最大报文不会超过 CIIMS 支持的 10MB 的上
限，所以不需要分段。
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments None
注释 无
Processing Exceptions RMS will ignore the following fields in the message
处理例外 RMS将忽略消息中的下列字段
ANAM, ACTY, ICCD, BDIS, ATYP, HAUL
```
<a id="sec-3-2-2"></a>
#### 3.2.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M ARPT
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(3-4) M DNLD = It is a download
data section. from AODB/从AODB下载
消息发送的子类型. Meta Data段的一部 RESP = It is a response
分. to a subsystem request/
响应子系统的请求
ADD = Add new record/
增加新记录
UPD = Update old
record/更新旧记录
DEL = Delete old record/
删除旧记录
RECS No of records contained in XML Number(1-4) M 0 – 9999
XML中包括的记录数
ARPT Identifies start of one airport record. - O This starts a new section
Repeats for each airport record. and encloses the details
一条机场代码记录的开始标志。在每条 of an airport. This section
记录中重复出现。 will be absent if RECS =
0
是新段落的起点，将机场
的明细括起来。如果
RECS＝0则无该部分。
ITCD The IATA standard airport code Char(3) M
IATA标准的机场代码
ICCD The ICAO standard airport code Char(4) P An empty TAG indicates
ICAO标准的机场代码 data not available
空标签表示无可用数据。
ANAM The airport name Char(1-30) M Full name of airport
机场名称 机场全名
ANMC The airport name in Chinese Char(1-30) M Chinese name
机场中文名称 中文名
BDIS Distance from current base airport Number(1-12) P Unit in Kilometers. An
Chengdu empty TAG indicates
data not available
XML Tag Description Format Req Values
当前基地机场距成都的距离 单位为公里。空标签表示
无可用数据。
CTRY Country code to which airport belongs Char(2-3) M Will refer to country
机场所属的国家代码 codes reference table to
be decided by CDIA
根据成都机场国家代码参
考数据表决定
ACTY City code to which airport belongs Char(3) M Will refer to city codes
机场所属的城市代码 reference table to be
decided by CDIA
根据成都机场城市码数据
表决定
ATYP Domestic or international with respect Char(1) M D = Domestic/国内
to current airport I = International/国际
当前机场国内国际标识
HAUL Long haul or short haul with respect to Char(1) P S = Short/短途
current airport L = Long/长途
当前机场长短程标识 An empty TAG indicates
data not available
空标签表示无可用数据。
```
<a id="sec-3-2-3"></a>
#### 3.2.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>ARPT</TYPE>
<STYP>DNLD</STYP>
</META>
<RECS>3</RECS>
<ARPT>
<ITCD>SHA</ITCD>
<ICCD>SHHA</ICCD>
<ANAM>SHANGHAI HONGQIAO INTL AIRPORT</ANAM>
<ANMC>上海红瞧国际机场</ANMC>
<BDIS>1200</BDIS>
<CTRY>PRC</CTRY>
<ACTY>SHA</ACTY>
<ATYP>D</ATYP>
<HAUL>S</HAUL>
</ARPT>
<ARPT>
<ITCD>MEL</ITCD>
<ICCD>AMML</ICCD>
<ANAM>MELBOURNE TULLMARINE</ANAM>
<ANMC>墨尔本</ANMC>
<BDIS>4500</BDIS>
<CTRY>AUS</CTRY>
<ACTY>MEL</ACTY>
<ATYP>I</ATYP>
<HAUL>L</HAUL>
</ARPT>
<ARPT>
<ITCD>CTU</ITCD>
<ICCD>CTUK</ICCD>
<ANAM>CHENGDU CAPITAL AIRPORT</ANAM>
<ANMC>成都成都国际机场</ANMC>
<BDIS>1900</BDIS>
<CTRY>PRC</CTRY>
<ACTY>BJS</ACTY>
<ATYP>D</ATYP>
<HAUL>S</HAUL>
</ARPT>
</MSG>
```
<a id="sec-3-3"></a>
### 3.3 AODB airline codes event/ AODB 航空公司代码事件
<a id="sec-3-3-1"></a>
#### 3.3.1 Event Attributes/事件属性
```text
Message Code AODBAIRL
消息代码
Event Description This event occurs whenever any airline code reference
事件描述 data is to be sent to subsystems from AODB.
当 AODB 向子系统发送任何航空公司代码参考数据时，
产生该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered in specific cases as below:
频率 非计划的，特定的情况下触发：
An airline code reference data download in list mode is
expected to be rolled out during installation and system
configuration.
在系统安装和配置启动时，航空公司代码参考数据以列表
模式下载时。
An airline code reference data download in list mode can
also be generated any time the operator decides to
distribute it from AODB to all subsystems or a given
subsystem.
在操作员由 AODB 向所有的或某个子系统以列表模式发
布航空公司代码时。
An airline code reference data download in list mode can
also be generated to a specific subsystem any time the
operator decides to request it from the subsystem.
在操作员响应子系统的请求而向该系统以列表模式发送航
空公司代码时。
An airline code reference data in incremental mode can
also be sent out to all subsystems whenever airline code
reference data fields are updated in AODB.
AODB 中航空公司代码参考数据字段更新，向所有子系统
以增量模式发送航空公司代码时。
Data Range When sent from AODB in list mode one airline code
数据范围 reference data XML will contain entire list of all airline
codes in AODB.
当 AODB 以列表模式发送时，一个 XML 报文包括 AODB
中所有的航空公司代码。
When sent from AODB in incremental mode one airline
code reference data XML will contain only one airline
code (the one that was updated) in AODB. But the single
record will have a complete snapshot of all fields related
to that record.
当 AODB 以增量模式发送时，一个 XML 报文只包括
AODB 中的一个航空公司代码（修改的那个）。该记录包
括航空公司代码所有的字段。
Data Count One or more airline code reference data records in one
数据数 XML as explained above.
如上所述，一个 XML 报文包括一个或多个航空公司代码
参考数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority Normal
优先级 正常
Expiry 480 minutes
过期 480 分钟
Message Fragmentation Although large messages are expected it will not cross
消息分段 the maximum limit of 10MB supported by CIIMS, so no
fragmentation required.
根据估计最大报文不会超过 CIIMS 支持的 10MB 的上
限，所以不需要分段。
Encoding UTF 8
编码
Time Beijing local time
时间 北京时间
Comments None
注释 无
```
<a id="sec-3-3-2"></a>
#### 3.3.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M AIRL
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(3-4) M DNLD = It is a download
data section. from AODB/从AODB下载
消息发送的子类型. Meta Data段的一部 RESP = It is a response
分. to a subsystem request/
响应子系统的请求
ADD = Add new record/
增加新记录
UPD = Update old
record/更新旧记录
DEL = Delete old record/
删除旧记录
RECS No of records contained in XML Number(1-4) M 0 – 9999
XML中包括的记录数
AIRL Identifies start of one airline record. - O This starts a new section
Repeats for each airline record. and encloses the details
一条航空公司代码记录的开始标志。在 of an airline. This section
每条记录中重复出现。 will be absent if RECS =
0
是新段落的起点，将航空
公司的明细括起来。如果
RECS＝0则无该部分。
ITOP The IATA operator code Char(2-3) M
IATA承运人代码
ICOP The ICAO operator code Char(3) M
ICAO承运人代码
ONAM Full name of the operator Char(1-30) M
航空公司全名
ONMC Chinese name of airline operator Char(1-30) M
航空公司中文名
CTRY Country code to which airline belongs Char(2-3) P Will refer to country
航空公司所属国家代码 codes reference table to
be decided by CDIA. An
empty TAG means data
XML Tag Description Format Req Values
not available.
根据成都机场国家代码参
考数据表决定。空标签表
示无可用数据。
TRML Default operating terminal for airline. Char(1-5) P Will refer to terminal
This includes two parameters: codes reference table to
航空公司的默认运营航站楼。这含有2 be decided by CDIA. An
个参数。 empty TAG means data
not available.
MVIN = Char(1) Movement indicator,
only “A” and “D” are acceptable values. 根据成都机场航站楼代码
/ 运行标识,可接受的值只有“A” 和 “D” 参考数据表决定。空标签
表示无可用数据。
FLIN = Char(1) Flight Indicator, only “I”
and “D” are acceptable values. / 航班 When there is no terminal
国际国内标志,可接受的值只有“I” 和 “D” specified for a airline, an
empty tag will be sent
and the two parameters
values will be empty
strings.
当没有为一个航空公司指
定航展楼的时候，一个空
的标签会被发送，同时它
的两个参数值也为空字符
串。
OGRP Name of operator group to which Char(1-30) P There could be multiple
airline belongs operator groups since an
航空公司所属承运人组名称 airline can belong to
more than one airline
operator group. An empty
TAG means data not
available.
可以有多个承运人组，因
为一个航空公司可以属于
多个承运人组。空标签表
示无可用数据。
SUBC Identifies start of one airline - O This starts a new section
subcompany record. Repeats for each and encloses the details
airline subcompany record. of an airline subcompany.
一条航空公司子公司代码记录的开始标 This section will be
志。在每条记录中重复出现。 absent if there is no
subcompany for this
airline.
是新段落的起点，将航空
公司的子公司的明细括起
来。如果这个航空公司没
有子公司那么这部分将不
出现。
CODE Subcompany code Char(1-10) M
子公司代码
NAME Subcompany name Char(1-30) M
XML Tag Description Format Req Values
子公司名称
NAMC Subcompany name in alternative Char(1-30) M
language
子公司中文名称
```
<a id="sec-3-3-3"></a>
#### 3.3.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>AIRL</TYPE>
<STYP>DNLD</STYP>
</META>
<RECS>3</RECS>
<AIRL>
<ITOP>UA</ITOP>
<ICOP>UAL</ICOP>
<ONAM>UNITED AIRLINES</ONAM>
<ONMC>UNITED 航空公司</ONMC>
<CTRY>USA</CTRY>
<TRML MVIN=”” FLIN=””></TRML>
<OGRP>STAR ALLIANCE</OGRP>
<SUBC>
<CODE>001</CODE>
<NAME>First Subcompany</NAME>
<NAMC>第一子公司</NAMC>
</SUBC>
<SUBC>
<CODE>002</CODE>
<NAME>Second Subcompany</NAME>
<NAMC>第二子公司</NAMC>
</SUBC>
</AIRL>
<AIRL>
<ITOP>AA</ITOP>
<ICOP>AAL</ICOP>
<ONAM>AMERICAN AIRLINES</ONAM>
<ONMC>美国航空公司</ONMC>
<CTRY>USA</CTRY>
<TRML MVIN=”A” FLIN=”I”>T2</TRML>
<OGRP>ONE WORLD</OGRP>
</AIRL>
<AIRL>
<ITOP>CX</ITOP>
<ICOP>CPA</ICOP>
<ONAM>CATHAY PACIFIC</ONAM>
<ONMC>香港航空公司</ONMC>
<CTRY>HKG</CTRY>
<TRML MVIN=”A” FLIN=”I”>T3A</TRML>
<TRML MVIN=”D” FLIN=”I”>T3B</TRML>
<OGRP>ONE WORLD</OGRP>
<OGRP>CHINA WORLD</OGRP>
</AIRL>
</MSG>
```
<a id="sec-3-4"></a>
### 3.4 AODB aircraft codes event/ AODB 飞机代码事件
<a id="sec-3-4-1"></a>
#### 3.4.1 Event Attributes/事件属性
```text
Message Code AODBAIRC
消息代码
Event Description This event occurs whenever any aircraft code reference
事件描述 data is to be sent to subsystems from AODB.
当 AODB 向子系统发送任何飞机代码参考数据时，产生
该事件。
Single Recipient No
接收者
Frequency Unscheduled, triggered in specific cases as below:
频率 非计划的，特定的情况下触发：
An aircraft code reference data download in list mode is
expected to be rolled out during installation and system
configuration.
在系统安装和配置启动时，飞机代码参考数据以列表模式
下载时。
An aircraft code reference data download in list mode
can also be generated any time the operator decides to
distribute it from AODB to all subsystems or a given
subsystem.
在操作员由 AODB 向所有的或某个子系统以列表模式发
布飞机代码时。
An aircraft code reference data download in list mode
can also be generated to a specific subsystem any time
the operator decides to request it from the subsystem.
在操作员响应子系统的请求而向该系统以列表模式发送飞
机代码时。
An aircraft code reference data in incremental mode can
also be sent out to all subsystems whenever aircraft
code reference data fields are updated in AODB.
AODB 中飞机代码参考数据字段更新，向所有子系统以增
量模式发送飞机代码时。
Data Range When sent from AODB in list mode one aircraft code
数据范围 reference data XML will contain entire list of all aircraft
codes in AODB.
当 AODB 以列表模式发送时，一个 XML 报文包括 AODB
中所有的飞机代码。
When sent from AODB in incremental mode one aircraft
code reference data XML will contain only one aircraft
code (the one that was updated) in AODB. But the single
record will have a complete snapshot of all fields related
to that record.
当 AODB 以增量模式发送时，一个 XML 报文只包括
AODB 中的一个飞机代码（修改的那个）。该记录包括飞
机代码所有的字段。
Data Count One or more aircraft code reference data records in one
数据数 XML as explained above.
如上所述，一个 XML 报文包括一个或多个飞机代码参考
数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority Normal
优先级 正常
Expiry 480 minutes
过期 480 分钟
Message Fragmentation Although large messages are expected it will not cross
消息分段 the maximum limit of 10MB supported by CIIMS, so no
fragmentation required.
根据估计最大报文不会超过 CIIMS 支持的 10MB 的上
限，所以不需要分段。
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments None
注释 无
Processing Exceptions RMS will ignore the following fields in the message
处理例外 RMS将忽略消息中下列字段
DESC, CHAP, MFWT, MTWT, MHTM, MABR.
MHTM is the handling by aircraft type but RMS will
ignore this and require CDIA to use a system level
handling time for aircrafts within RMS.
MHTM被处理机型但RMS将忽略这个标签，需要CDIA在
RMS中使用系统级别的航空器处理时间。
```
<a id="sec-3-4-2"></a>
#### 3.4.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M AIRC
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(3-4) M DNLD = It is a download
data section. from AODB/从AODB下载
消息发送的子类型. Meta Data段的一部 RESP = It is a response
分. to a subsystem request/
响应子系统的请求
ADD = Add new record/
增加新记录
UPD = Update old
record/更新旧记录
DEL = Delete old record/
删除旧记录
RECS No of records contained in XML Number(1-4) M 0 – 9999
XML中包括的记录数
AIRC Identifies start of one Aircraft record. - O This starts a new section
Repeats for each aircraft record. and encloses the details
一条飞机代码记录的开始标志。在每条 of one aircraft type. This
记录中重复出现。 section will be absent if
RECS = 0
是新段落的起点，将飞机
的明细括起来。如果
RECS＝0则无该部分。
ITAT The IATA code for aircraft type Char(3) M
飞机类型的IATA代码
ICAT The ICAO code for aircraft type Char(3-4) M
飞机类型的ICAO代码
DESC Full description of the aircraft type Char(1-30) M
飞机类型的全描述
CDSC Chinese description of the aircraft type Char(1-30) M
飞机类型的中文描述
CHAP Aircraft noise chapter code Char(1-4) P Reference data to be
飞机的噪音等级代码 decided by CDIA. An
empty TAG means data
not available.
XML Tag Description Format Req Values
根据成都机场代码参考数
据表决定。空标签表示无
可用数据。
MAXP Maximum passengers aircraft can Number(1-3) P 0 – 999. An empty TAG
carry means data not available.
最大载客数量 空标签表示无可用数据。
MFWT Maximum freight weight Number(1-9,2) P Unit in kilograms. An
最大载重 empty TAG means data
not available.
单位公斤。空标签表示无
可用数据。
MTWT Maximum takeoff weight Number(1-9,2) P Unit in kilograms. An
最大起飞重量 empty TAG means data
not available.
单位公斤。空标签表示无
可用数据。
ALEN Aircraft length Number(1-9,2) P Unit in meters. An empty
机长 TAG means data not
available.
单位米。空标签表示无可
用数据。
WSPN Aircraft Wing span Number(1-9,2) P Unit in meters. An empty
翼展 TAG means data not
available.
单位米。空标签表示无可
用数据。
MHTM Minimum handling time Number(1-6,2) P Unit in minutes. An empty
最小处理时间 TAG means data not
available.
单位分钟。空标签表示无
可用数据。
MABR Maximum air bridges that can be Number(1) P An empty TAG means
connected to this aircraft data not available.
可连接的最大登机桥数 空标签表示无可用数据。
```
<a id="sec-3-4-3"></a>
#### 3.4.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>AIRC</TYPE>
<STYP>DNLD</STYP>
</META>
<RECS>1</RECS>
<AIRC>
<ITAT>312</ITAT>
<ICAT>A310</ICAT>
<DESC>AIRBUS 310- 100 / 200</DESC>
<CDSC>AIRBUS中文310- 100 / 200</CDSC>
<CHAP>3</CHAP>
<MAXP>241</MAXP>
<MFWT>31730</MFWT>
<MTWT>138600</MTWT>
<ALEN>33.8</ALEN>
<WSPN>30</WSPN>
<MHTM>40</MHTM>
<MABR>2</MABR>
</AIRC>
</MSG>
```
<a id="sec-3-5"></a>
### 3.5 AODB registration codes event/ AODB 注册码事件
<a id="sec-3-5-1"></a>
#### 3.5.1 Event Attributes/事件属性
```text
Message Code AODBREGN
消息代码
Event Description This event occurs whenever any registration code
事件描述 reference data is to be sent to subsystems from AODB.
当 AODB 向子系统发送任何注册码数据时，产生该事
件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered in specific cases as below:
频率 非计划的，特定的情况下触发：
A registration code reference data download in list mode
is expected to be rolled out during installation and
system configuration.
在系统安装和配置启动时，注册码数据以列表模式下载
时。
A registration code reference data download in list mode
can also be generated any time the operator decides to
distribute it from AODB to all subsystems or a given
subsystem.
在操作员由 AODB 向所有的或某个子系统以列表模式发
布注册码时。
A registration code reference data download in list mode
can also be generated to a specific subsystem any time
the operator decides to request it from the subsystem.
在操作员响应子系统的请求而向该系统以列表模式发送注
册码时。
A registration code reference data in incremental mode
can also be sent out to all subsystems whenever
registration code reference data fields are updated in
AODB.
AODB 中注册码数据字段更新，向所有子系统以增量模式
发送注册码时。
Data Range When sent from AODB in list mode one registration code
数据范围 reference data XML will contain entire list of all
registration codes in AODB.
当 AODB 以列表模式发送时，一个 XML 报文包括 AODB
中所有的注册码。
When sent from AODB in incremental mode one
registration code reference data XML will contain only
one registration code (the one that was updated) in
AODB. But the single record will have a complete
snapshot of all fields related to that record.
当 AODB 以增量模式发送时，一个 XML 报文只包括
AODB 中的一个注册码（修改的那个）。该记录包括注册
码所有的字段。
Data Count One or more registration code reference data records in
数据数 one XML as explained above.
如上所述，一个 XML 报文包括一个或多个注册码数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority Normal
优先级 正常
Expiry 480 minutes
过期 480 分钟
Message Fragmentation Although large messages are expected it will not cross
消息分段 the maximum limit of 10MB supported by CIIMS, so no
fragmentation required.
根据估计最大报文不会超过 CIIMS 支持的 10MB 的上
限，所以不需要分段。
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments None
注释
Processing Exceptions RMS will ignore the following fields in the message
处理例外 RMS将忽略消息中下列字段
OWID, MFWT, MTWT
```
<a id="sec-3-5-2"></a>
#### 3.5.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M REGN
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(3-4) M DNLD = It is a download
data section. from AODB/从AODB下载
消息发送的子类型. Meta Data段的一部 RESP = It is a response
分. to a subsystem request/
响应子系统的请求
ADD = Add new record/
增加新记录
UPD = Update old
record/更新旧记录
DEL = Delete old record/
删除旧记录
RECS No of records contained in XML Number(1-4) M 0 – 9999
XML中包括的记录数
REGN Identifies start of one registration - O This starts a new section
record. Repeats for each registration and encloses the details
record. of one registration type.
一条注册码记录的开始标志。在每条记 This section will be
录中重复出现。 absent if RECS = 0
是新段落的起点，将注册
的明细括起来。如果
RECS＝0则无该部分。
RNUM Registration Number Number(1-10) M
注册号码
ITAT The IATA code for aircraft type Char(3) M Will refer to the aircraft
飞机类型的IATA代码 type reference data to be
decided by CDIA.
根据成都机场飞机类型数
据表决定。
OWID Organization ID of owner of aircraft Number(1-9) P Will refer to the
飞机所属机构ID organization reference
data to be decided by
CDIA. An empty TAG
indicates data not
available.
根据成都机场机构数据表
XML Tag Description Format Req Values
决定。空标签表示无可用
数据。
ACAL Aircraft owner‟s airline code Char(2-3) P IATA airline code. Will
飞机所属航空公司代码 refer to the airline
reference data to be
decided by CDIA. An
empty TAG indicates
data not available.
IATA航空公司代码。根据
成都机场航空公司数据表
决定。空标签表示无可用
数据。
MAXP Maximum passengers this particular Number(1-3) P 0 – 999. An empty TAG
registration can carry, overrides the means data not available.
value in the aircraft type. 空标签表示无可用数据。
实际注册的最大载客数，优先于飞机类
型的值
MFWT Maximum freight weight for this Number(1-9,2) P Unit in kilograms. An
particular registration, overrides the empty TAG means data
value in the aircraft type. not available.
实际注册的最大载重量，优先于飞机类 单位公斤。空标签表示无
型的值 可用数据。
MTWT Maximum takeoff weight for this Number(1-9,2) P Unit in kilograms. An
particular registration, overrides the empty TAG means data
value in the aircraft type. not available.
实际注册的最大起飞重量，优先于飞机 单位公斤。空标签表示无
类型的值 可用数据。
```
<a id="sec-3-5-3"></a>
#### 3.5.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>REGN</TYPE>
<STYP>DNLD</STYP>
</META>
<RECS>2</RECS>
<REGN>
<RNUM>A40LF</RNUM>
<ITAT>312</ITAT>
<OWID>52156</OWID>
<ACAL>CA</ACAL>
<MAXP>200</MAXP>
<MFWT></MFWT>
<MTWT></MTWT>
</REGN>
<REGN>
<RNUM>A6AIN</RNUM>
<ITAT>320</ITAT>
<OWID>521526</OWID>
<ACAL>CZ</ACAL>
<MAXP></MAXP>
<MFWT></MFWT>
<MTWT></MTWT>
</REGN>
</MSG>
```
<a id="sec-3-6"></a>
### 3.6 AODB organization codes event/ AODB 机构代码事件
<a id="sec-3-6-1"></a>
#### 3.6.1 Event Attributes/事件属性
```text
Message Code AODBORGN
消息代码
Event Description This event occurs whenever any organization code
事件描述 reference data is to be sent to subsystems from AODB.
当 AODB 向子系统发送任何机构代码参考数据时，产生
该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered in specific cases as below:
频率 非计划的，特定的情况下触发：
An organization code reference data download in list
mode is expected to be rolled out during installation and
system configuration.
在系统安装和配置启动时，机构代码参考数据以列表模式
下载时。
An organization code reference data download in list
mode can also be generated any time the operator
decides to distribute it from AODB to all subsystems or a
given subsystem.
在操作员由 AODB 向所有的或某个子系统以列表模式发
布机构代码时。
An organization code reference data download in list
mode can also be generated to a specific subsystem
any time the operator decides to request it from the
subsystem.
在操作员响应子系统的请求而向该系统以列表模式发送机
构代码时。
An organization code reference data in incremental
mode can also be sent out to all subsystems whenever
organization code reference data fields are updated in
AODB.
AODB 中机构代码参考数据字段更新，向所有子系统以增
量模式发送机构代码时。
Data Range When sent from AODB in list mode one organization
数据范围 code reference data XML will contain entire list of all
organization codes in AODB.
当 AODB 以列表模式发送时，一个 XML 报文包括 AODB
中所有的机构代码。
When sent from AODB in incremental mode one
organization code reference data XML will contain only
one organization code (the one that was updated) in
AODB. But the single record will have a complete
snapshot of all fields related to that record.
当 AODB 以增量模式发送时，一个 XML 报文只包括
AODB 中的一个机构代码（修改的那个）。该记录包括机
构代码所有的字段。
Data Count One or more organization code reference data records
数据数 in one XML as explained above.
如上所述，一个 XML 报文包括一个或多个机构代码参考
数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority Normal
优先级 正常
Expiry 480 minutes
过期 480 分钟
Message Fragmentation Although large messages are expected it will not cross
消息分段 the maximum limit of 10MB supported by CIIMS, so no
fragmentation required.
根据估计最大报文不会超过 CIIMS 支持的 10MB 的上
限，所以不需要分段。
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments An airline is treated as an organization in AODB,
注释 however the organization list from AODB will not contain
airline operator records. Airline operator records will be
sent as part airline code reference data.
在AODB中，一个航空公司被认做一个机构。AODB的机
构列表不包括航空公司承运人记录。航空公司承运人记录
作为航空公司代码的一部分。
Processing Exceptions RMS will ignore the following fields in the message
处理例外 RMS将忽略消息中下列字段
ONAM
Any category specified in OCAT will be ignored other
than following
OCAT中指定的类别中除了下列类型都会被忽略
 Passenger Handlers identified with OCAT value
“PAXAGT”
旅客代理由 OCAT 的“PAXAGT”表示
 Maintenance Handlers identified with OCAT value
“MNTAGT”
维护代理由 OCAT 的“MNTAGT”表示
 Ground Handlers identified with OCAT value
“GNDAGT”
地服代理由 OCAT 的“GNDAGT”表示
These OCAT values are specific codes in AODB and
operator is not expected to amend these, only
descriptions for these codes can be amended which
should not impact the AODB-RMS interface w.r.t
processing above values.
这个OCAT值在AODB中指定，操作员不应修改这些值，
只有它们的描述可以被修改，并且不应影响AODB-RMS
接口对该值的处理。
```
<a id="sec-3-6-2"></a>
#### 3.6.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M ORGN
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(3-4) M DNLD = It is a download
data section. from AODB/从AODB下载
消息发送的子类型. Meta Data段的一部 RESP = It is a response
分. to a subsystem request/
响应子系统的请求
ADD = Add new record/
增加新记录
UPD = Update old
record/更新旧记录
DEL = Delete old record/
删除旧记录
XML Tag Description Format Req Values
RECS No of records contained in XML Number(1-4) M 0 – 9999
XML中包括的记录数
ORGN Identifies start of one organization - O This starts a new section
record. Repeats for each organization and encloses the details
record. of one organization. This
一条机构代码记录的开始标志。在每条 section will be absent if
记录中重复出现。 RECS = 0
是新段落的起点，将机构
的明细括起来。如果
RECS＝0则无该部分。
OGID Organization Identifier Number(1-9) M Unique AODB Id
机构标识 associated with the
organization
在AODB中唯一
ONAM Full name of organization Char(1-40) M
机构的全名
ONMC Chinese name of organization Char(1-40) M
机构的中文名
OCAT Organization category. Char(1-30) P Will be set based on the
机构种类 organization category
setup by CDIA. E.g.
categories include
„PASSENGER
HANDLER‟, „RAMP
HANDLER‟ etc but this
will be defined by CDIA.
There could be multiple
organization categories
since an organization can
belong to more than one
organization category. An
empty TAG means data
not available.
根据成都机场机构代码参
考数据表决定。如，种类
包括“旅客处理”，“机
坪处理”等，都由成都机
场定义。可以有多个机构
种类代码，因为一个机构
可以属于多个机构种类。
空标签表示无可用数据。
```
<a id="sec-3-6-3"></a>
#### 3.6.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>ORGN</TYPE>
<STYP>DNLD</STYP>
</META>
<RECS>2</RECS>
<ORGN>
<OGID>423423</OGID>
<ONAM>China Eastern Holding Company</ONAM>
<ONMC>中国东方有限公司</ONMC>
<OCAT>RAMP HANDLER</OCAT>
</ORGN>
<ORGN>
<OGID>477923</OGID>
<ONAM>ServisAir Private Limited</ONAM>
<ONMC>美国SERVISAIR有限公司</ONMC>
<OCAT>RAMP HANDLER</OCAT>
<OCAT>PAX HANDLER</OCAT>
</ORGN>
</MSG>
```
<a id="sec-3-7"></a>
### 3.7 AODB flight type codes event/ AODB 航班类型代码事件
<a id="sec-3-7-1"></a>
#### 3.7.1 Event Attributes/事件属性
```text
Message Code AODBFLTL
消息代码
Event Description This event occurs whenever any flight type code
事件描述 reference data is to be sent to subsystems from AODB.
当 AODB 向子系统发送任何航班类型代码参考数据时，
产生该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered in specific cases as below:
频率 非计划的，特定的情况下触发：
A flight type code reference data download in list mode
is expected to be rolled out during installation and
system configuration.
在系统安装和配置启动时，航班类型代码参考数据以列表
模式下载时。
A flight type code reference data download in list mode
can also be generated any time the operator decides to
distribute it from AODB to all subsystems or a given
subsystem.
在操作员由 AODB 向所有的或某个子系统以列表模式发
布航班类型代码时。
A flight type code reference data download in list mode
can also be generated to a specific subsystem any time
the operator decides to request it from the subsystem.
在操作员响应子系统的请求而向该系统以列表模式发送航
班类型代码时。
A flight type code reference data in incremental mode
can also be sent out to all subsystems whenever flight
type code reference data fields are updated in AODB.
AODB 中航班类型代码参考数据字段更新，向所有子系统
以增量模式发送航班类型代码时。
Data Range When sent from AODB in list mode one flight type code
数据范围 reference data XML will contain entire list of all flight
type codes in AODB.
当 AODB 以列表模式发送时，一个 XML 报文包括 AODB
中所有的航班类型代码。
When sent from AODB in incremental mode one flight
type code reference data XML will contain only one flight
type code (the one that was updated) in AODB. But the
single record will have a complete snapshot of all fields
related to that record.
当 AODB 以增量模式发送时，一个 XML 报文只包括
AODB 中的一个航班类型代码（修改的那个）。该记录包
括航班类型代码所有的字段。
Data Count One or more flight type code reference data records in
数据数 one XML as explained above.
如上所述，一个 XML 报文包括一个或多个航班类型代码
参考数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority Normal
优先级 正常
Expiry 480 minutes
过期 480 分钟
Message Fragmentation Although large messages are expected it will not cross
消息分段 the maximum limit of 10MB supported by CIIMS, so no
fragmentation required.
根据估计最大报文不会超过 CIIMS 支持的 10MB 的上
限，所以不需要分段。
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments None
注释 无
Processing Exceptions RMS will ignore the following fields in the message
处理例外 RMS将忽略消息中下列字段
FDES, FCML, CTYP
```
<a id="sec-3-7-2"></a>
#### 3.7.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M FLTL
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(3-4) M DNLD = It is a download
data section. from AODB/从AODB下载
消息发送的子类型. Meta Data段的一部 RESP = It is a response
分. to a subsystem request/
响应子系统的请求
ADD = Add new record/
增加新记录
UPD = Update old
record/更新旧记录
DEL = Delete old record/
删除旧记录
RECS No of records contained in XML Number(1-4) M 0 – 9999
XML中包括的记录数
FLTL Identifies start of one flight type record. - O This starts a new section
Repeats for each flight type record. and encloses the details
一条航班类型代码记录的开始标志。在 of one flight type. This
每条记录中重复出现。 section will be absent if
RECS = 0
是新段落的起点，将航班
类型的明细括起来。如果
RECS＝0则无该部分。
FTYP Single character code for flight type Char(1) M
单字符的航班类型
CTYP The CAAC/ATC equivalent flight type Char(1-3) P An empty TAG means
CAAC/ATC等值航班类型 data not available.
空标签表示无可用数据。
FDES The textual description for flight type Char(1-30) M
航班类型文字描述
FDSC Fight type description in Chinese Char(1-30) M
航班类型中文描述
FCML Can be used for commercial Flight? Char(1) O Y = Use for commercial/
XML Tag Description Format Req Values
是否用于商业航班？ 是
N = Cannot be used/否
```
<a id="sec-3-7-3"></a>
#### 3.7.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>FLTL</TYPE>
<STYP>DNLD</STYP>
</META>
<RECS>2</RECS>
<FLTL>
<FTYP>J</FTYP>
<CTYP>SCH</CTYP>
<FDES>SCHEDULED FLT</FDES>
<FDSC>定期航班</FDSC>
<FCML>Y</FCML>
</FLTL>
<FLTL>
<FTYP>I</FTYP>
<CTYP></CTYP>
<FDES>DIPLOMATIC USE</FDES>
<FDSC>外交航班</FDSC>
<FCML>N</FCML>
</FLTL>
</MSG>
```
<a id="sec-3-8"></a>
### 3.8 AODB terminal codes event/ AODB 航站楼代码事件
<a id="sec-3-8-1"></a>
#### 3.8.1 Event Attributes/事件属性
```text
Message Code AODBTLST
消息代码
Event Description This event occurs whenever any terminal code reference
事件描述 data is to be sent to subsystems from AODB.
当 AODB 向子系统发送任何航站楼代码参考数据时，产
生该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered in specific cases as below:
频率 非计划的，特定的情况下触发：
A terminal code reference data download in list mode is
expected to be rolled out during installation and system
configuration.
在系统安装和配置启动时，航站楼代码参考数据以列表模
式下载时。
A terminal code reference data download in list mode
can also be generated any time the operator decides to
distribute it from AODB to all subsystems or a given
subsystem.
在操作员由 AODB 向所有的或某个子系统以列表模式发
布航站楼代码时。
A terminal code reference data download in list mode
can also be generated to a specific subsystem any time
the operator decides to request it from the subsystem.
在操作员响应子系统的请求而向该系统以列表模式发送航
站楼代码时。
A terminal code reference data in incremental mode can
also be sent out to all subsystems whenever terminal
code reference data fields are updated in AODB.
AODB 中航站楼代码参考数据字段更新，向所有子系统以
增量模式发送航站楼代码时。
Data Range When sent from AODB in list mode one terminal code
数据范围 reference data XML will contain entire list of all terminal
codes in AODB.
当 AODB 以列表模式发送时，一个 XML 报文包括 AODB
中所有的航站楼代码。
When sent from AODB in incremental mode one
terminal code reference data XML will contain only one
terminal code (the one that was updated) in AODB. But
the single record will have a complete snapshot of all
fields related to that record.
当 AODB 以增量模式发送时，一个 XML 报文只包括
AODB 中的一个航站楼代码（修改的那个）。该记录包括
航站楼代码所有的字段。
Data Count One or more terminal code reference data records in
数据数 one XML as explained above.
如上所述，一个 XML 报文包括一个或多个航站楼代码参
考数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority Normal
优先级 正常
Expiry 480 minutes
过期 480 分钟
Message Fragmentation Although large messages are expected it will not cross
消息分段 the maximum limit of 10MB supported by CIIMS, so no
fragmentation required.
根据估计最大报文不会超过 CIIMS 支持的 10MB 的上
限，所以不需要分段。
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments None
注释 无
Processing Exceptions RMS will ignore the following fields in the message
处理例外 RMS将忽略消息中下列字段
TNAM, TCAT, TPAX
```
<a id="sec-3-8-2"></a>
#### 3.8.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M TLST
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(3-4) M DNLD = It is a download
data section. from AODB/从AODB下载
消息发送的子类型. Meta Data段的一部 RESP = It is a response
分. to a subsystem request/
响应子系统的请求
ADD = Add new record/
增加新记录
UPD = Update old
record/更新旧记录
DEL = Delete old record/
删除旧记录
RECS No of records contained in XML Number(1-4) M 0 – 9999
XML中包括的记录数
TLST Identifies start of one terminal record. - O This starts a new section
Repeats for each terminal record. and encloses the details
一条航站楼代码记录的开始标志。在每 of a terminal. This section
条记录中重复出现。 will be absent if RECS =
0
是新段落的起点，将航站
XML Tag Description Format Req Values
楼的明细括起来。如果
RECS＝0则无该部分。
TCOD Code for this terminal Char(1-5) M
该航站楼的代码
TNAM Terminal name / description Char(1-30) M
航站楼名称/描述
TNMC Terminal name / description Chinese Char(1-30) M
航站楼中文名称/描述
TCAT Terminal category Char(1) M I = International/国际
航站楼种类 D = Domestic/国内
M = Mixed/混合
TPAX Is this a passenger terminal? Char(1) P Y = Passenger terminal/
是否旅客航站楼？ 是
N = Non passenger
terminal/否
```
<a id="sec-3-8-3"></a>
#### 3.8.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>TLST</TYPE>
<STYP>DNLD</STYP>
</META>
<RECS>1</RECS>
<TLST>
<TCOD>T2A</TCOD>
<TNAM>TERMINAL T1</TNAM>
<TNMC>T1航站楼</TNMC>
<TCAT>D</TCAT>
<TPAX>Y</TPAX>
</TLST>
</MSG>
```
<a id="sec-3-9"></a>
### 3.9 AODB gate codes event/ AODB 登机门代码事件
<a id="sec-3-9-1"></a>
#### 3.9.1 Event Attributes/事件属性
```text
Message Code AODBGLST
消息代码
Event Description This event occurs whenever any gate code reference
事件描述 data is to be sent to subsystems from AODB.
当 AODB 向子系统发送任何登机门代码参考数据时，产
生该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered in specific cases as below:
频率 非计划的，特定的情况下触发：
A gate code reference data download in list mode is
expected to be rolled out during installation and system
configuration.
在系统安装和配置启动时，登机门代码参考数据以列表模
式下载时。
A gate code reference data download in list mode can
also be generated any time the operator decides to
distribute it from AODB to all subsystems or a given
subsystem.
在操作员由 AODB 向所有的或某个子系统以列表模式发
布登机门代码时。
A gate code reference data download in list mode can
also be generated to a specific subsystem any time the
operator decides to request it from the subsystem.
在操作员响应子系统的请求而向该系统以列表模式发送登
机门代码时。
A gate code reference data in incremental mode can
also be sent out to all subsystems whenever gate code
reference data fields are updated in AODB.
AODB 中登机门代码参考数据字段更新，向所有子系统以
增量模式发送登机门代码时。
Data Range When sent from AODB in list mode one gate code
数据范围 reference data XML will contain entire list of all gate
codes in AODB.
当 AODB 以列表模式发送时，一个 XML 报文包括 AODB
中所有的登机门代码。
When sent from AODB in incremental mode one gate
code reference data XML will contain only one gate code
(the one that was updated) in AODB. But the single
record will have a complete snapshot of all fields related
to that record.
当 AODB 以增量模式发送时，一个 XML 报文只包括
AODB 中的一个登机门代码（修改的那个）。该记录包括
登机门代码所有的字段。
Data Count One or more gate code reference data records in one
数据数 XML as explained above.
如上所述，一个 XML 报文包括一个或多个登机门代码参
考数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority Normal
优先级 正常
Expiry 480 minutes
过期 480 分钟
Message Fragmentation Although large messages are expected it will not cross
消息分段 the maximum limit of 10MB supported by CIIMS, so no
fragmentation required.
根据估计最大报文不会超过 CIIMS 支持的 10MB 的上
限，所以不需要分段。
Encoding UTF 8
编码
Time Beijing local time
时间 北京时间
Comments None
注释 无
```
<a id="sec-3-9-2"></a>
#### 3.9.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M GLST
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(3-4) M DNLD = It is a download
data section. from AODB/从AODB下载
消息发送的子类型. Meta Data段的一部 RESP = It is a response
分. to a subsystem request/
响应子系统的请求
ADD = Add new record/
增加新记录
UPD = Update old
record/更新旧记录
DEL = Delete old record/
删除旧记录
RECS No of records contained in XML Number(1-4) M 0 – 9999
XML中包括的记录数
GLST Identifies start of one gate record. - O This starts a new section
Repeats for each gate record. and encloses the details
一条登机门代码记录的开始标志。在每 of a gate. This section
XML Tag Description Format Req Values
条记录中重复出现。 will be absent if RECS =
0
是新段落的起点，将登机
门的明细括起来。如果
RECS＝0则无该部分。
GCOD Code for this gate Char(1-8) M Must be unique for a
登机门代码 terminal
必须唯一
GTNM Gate name / description Char(1-30) M
登机门名称/描述
GNMC Gate name / description Chinese Char(1-30) M
登机门中文名称/描述
GCAT Gate category Char(1) M I = International/国际
登机门种类 D = Domestic/国内
GTML Terminal code for this gate Char(1-5) P Will reference terminal
登机门的航站楼代码 code reference data in
AODB. Will be empty
TAG if no data available.
根据AODB航站楼代码参
考数据表决定。空标签表
示无可用数据。
PIER Pier code for this gate Char(1-8) O Will reference pier code
登机门的指廊代码 reference data in AODB.
Will be absent TAG if no
data available.
根据AODB指廊代码参考
数据表决定。无可用数据
则不显示此标签。
```
<a id="sec-3-9-3"></a>
#### 3.9.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>GLST</TYPE>
<STYP>DNLD</STYP>
</META>
<RECS>1</RECS>
<GLST>
<GCOD>G17</GCOD>
<GTNM>Gate for CA</GTNM>
<GNMC>Gate for CA中文</GNMC>
<GCAT>D</GCAT>
<GTML>T1</GTML>
<PIER>C</PIER>
</GLST>
</MSG>
```
<a id="sec-3-10"></a>
### 3.10 AODB stand codes event/ AODB 机位代码事件
<a id="sec-3-10-1"></a>
#### 3.10.1 Event Attributes/事件属性
```text
Message Code AODBSLST
消息代码
Event Description This event occurs whenever any stand code reference
事件描述 data is to be sent to subsystems from AODB.
当 AODB 向子系统发送任何机位代码参考数据时，产生
该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered in specific cases as below:
频率 非计划的，特定的情况下触发：
A stand code reference data download in list mode is
expected to be rolled out during installation and system
configuration.
在系统安装和配置启动时，机位代码参考数据以列表模式
下载时。
A stand code reference data download in list mode can
also be generated any time the operator decides to
distribute it from AODB to all subsystems or a given
subsystem.
在操作员由 AODB 向所有的或某个子系统以列表模式发
布机位代码时。
A stand code reference data download in list mode can
also be generated to a specific subsystem any time the
operator decides to request it from the subsystem.
在操作员响应子系统的请求而向该系统以列表模式发送机
位代码时。
A stand code reference data in incremental mode can
also be sent out to all subsystems whenever stand code
reference data fields are updated in AODB.
AODB 中机位代码参考数据字段更新，向所有子系统以增
量模式发送机位代码时。
Data Range When sent from AODB in list mode one stand code
数据范围 reference data XML will contain entire list of all stand
codes in AODB.
当 AODB 以列表模式发送时，一个 XML 报文包括 AODB
中所有的机位代码。
When sent from AODB in incremental mode one stand
code reference data XML will contain only one stand
code (the one that was updated) in AODB. But the single
record will have a complete snapshot of all fields related
to that record.
当 AODB 以增量模式发送时，一个 XML 报文只包括
AODB 中的一个机位代码（修改的那个）。该记录包括机
位代码所有的字段。
Data Count One or more stand code reference data records in one
数据数 XML as explained above.
如上所述，一个 XML 报文包括一个或多个机位代码参考
数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority Normal
优先级 正常
Expiry 480 minutes
过期 480 分钟
Message Fragmentation Although large messages are expected it will not cross
消息分段 the maximum limit of 10MB supported by CIIMS, so no
fragmentation required.
根据估计最大报文不会超过 CIIMS 支持的 10MB 的上
限，所以不需要分段。
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments None
注释 无
Processing Exceptions RMS will ignore the following fields in the message
处理例外 RMS将忽略消息中下列字段
STNM, MABS, FEPU
RMS requires SCOD to be unique across entire airport
not just within terminal.
RMS要求SCOD全机场唯一，而不只针对航站楼。
RMS can support maximum STGP length of 8
characters. Any data from AODB longer than 8, this will
be truncated in RMS. This may impact Rule creation if
any rules use the STGP parameter.
RMS可以支持STGP最长8位字符。从AODB来的任何长
于8位的数据将被RMS截去超长部分。这可能会影响规则
创建，如果规则使用STGP参数的话。
```
<a id="sec-3-10-2"></a>
#### 3.10.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M SLST
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(3-4) M DNLD = It is a download
data section. from AODB/从AODB下载
消息发送的子类型. Meta Data段的一部 RESP = It is a response
分. to a subsystem request/
响应子系统的请求
ADD = Add new record/
增加新记录
UPD = Update old
record/更新旧记录
DEL = Delete old record/
删除旧记录
RECS No of records contained in XML Number(1-4) M 0 – 9999
XML中包括的记录数
SLST Identifies start of one stand record. - O This starts a new section
Repeats for each stand record. and encloses the details
一条机位代码记录的开始标志。在每条 of a stand. This section
记录中重复出现。 will be absent if RECS =
0
是新段落的起点，将机位
的明细括起来。如果
RECS＝0则无该部分。
SCOD Stand code for this stand Char(1-8) M Must be unique for a
该机位的代码 terminal
必须唯一
STNM Stand name Char(1-30) M
机位名称
SNMC Stand name Chinese Char(1-30) M
机位中文名称
STGP Stand group code of this stand Char(1-30) P An empty TAG will be
该机位的机位组代码 sent if no data available
空标签表示无可用数据。
SWID Width of the stand Number(1-9,2) P Units meters. An empty
机位宽度 TAG will be sent if no
data available
XML Tag Description Format Req Values
单位米。空标签表示无可
用数据。
SHGT Length of the stand Number(1-9,2) P Units meters. An empty
机位长度 TAG will be sent if no
data available
单位米。空标签表示无可
用数据。
STML Terminal code Char(1-5) P Will reference terminal
航站楼代码 code reference data in
AODB.
根据AODB中的航站楼代
码参考数据。
MABS Maximum number airbridges that can Number(1) P Default is 1. An empty
be attached on this stand TAG will be sent if no
该机位可以连接的最大的登机桥数 data available
默认为1。空标签表示无
可用数据。
DIGT Default gate for international flights for Char(1-8) P Will reference gate code
this stand reference data in AODB.
该机位默认的国际航班登机门 An empty TAG will be
sent if no data available
根据AODB中的登机门代
码参考数据。空标签表示
无可用数据。
DDGT Default gate for domestic flights for this Char(1-8) P Will reference gate code
stand reference data in AODB.
该机位默认的国内航班登机门 An empty TAG will be
sent if no data available
根据AODB中的登机门代
码参考数据。空标签表示
无可用数据。
REMT Is this a remote stand, contact stand or Char(1) M Y = Remote/远
a bucket area stand? N = Contact (default)/近
是否远机位，近机位或停机区？ （默认）
A = Area stand/停机区
FEPU Does this stand have a fixed electric Char(1) P Y or N. Default N. An
power unit? empty TAG will be sent if
该机位是否有固定的电源？ no data available
Y或N。默认是N。空标签
表示无可用数据。
```
<a id="sec-3-10-3"></a>
#### 3.10.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>SLST</TYPE>
<STYP>DNLD</STYP>
</META>
<RECS>1</RECS>
<SLST>
<SCOD>S209</SCOD>
<STNM>South Stand 209</STNM>
<SNMC>南方机位209</SNMC>
<STGP>T1 SOUTH</STGP>
<SWID></SWID>
<SHGT></SHGT>
<STML>T1</STML>
<MABS>2</MABS>
<DIGT></DIGT>
<DDGT></DDGT>
<REMT>N</REMT>
<FEPU></FEPU>
</SLST>
</MSG>
```
<a id="sec-3-11"></a>
### 3.11 AODB check in counter codes event/ AODB 值机柜台代码事件
<a id="sec-3-11-1"></a>
#### 3.11.1 Event Attributes/事件属性
```text
Message Code AODBCLST
消息代码
Event Description This event occurs whenever any check in counter code
事件描述 reference data is to be sent to subsystems from AODB.
当 AODB 向子系统发送任何值机柜台代码参考数据时，
产生该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered in specific cases as below:
频率 非计划的，特定的情况下触发：
A check in counter code reference data download in list
mode is expected to be rolled out during installation and
system configuration.
在系统安装和配置启动时，值机柜台代码参考数据以列表
模式下载时。
A check in counter code reference data download in list
mode can also be generated any time the operator
decides to distribute it from AODB to all subsystems or a
given subsystem.
在操作员由 AODB 向所有的或某个子系统以列表模式发
布值机柜台代码时。
A check in counter code reference data download in list
mode can also be generated to a specific subsystem
any time the operator decides to request it from the
subsystem.
在操作员响应子系统的请求而向该系统以列表模式发送值
机柜台代码时。
A check in counter code reference data in incremental
mode can also be sent out to all subsystems whenever
check in counter code reference data fields are updated
in AODB.
AODB 中值机柜台代码参考数据字段更新，向所有子系统
以增量模式发送值机柜台代码时。
Data Range When sent from AODB in list mode one check in counter
数据范围 code reference data XML will contain entire list of all
check in counter codes in AODB.
当 AODB 以列表模式发送时，一个 XML 报文包括 AODB
中所有的值机柜台代码。
When sent from AODB in incremental mode one check
in counter code reference data XML will contain only one
check in counter code (the one that was updated) in
AODB. But the single record will have a complete
snapshot of all fields related to that record.
当 AODB 以增量模式发送时，一个 XML 报文只包括
AODB 中的一个值机柜台代码（修改的那个）。该记录包
括值机柜台代码所有的字段。
Data Count One or more check in counter code reference data
数据数 records in one XML as explained above.
如上所述，一个 XML 报文包括一个或多个值机柜台代码
参考数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority Normal
优先级 正常
Expiry 480 minutes
过期 480 分钟
Message Fragmentation Although large messages are expected it will not cross
消息分段 the maximum limit of 10MB supported by CIIMS, so no
fragmentation required.
根据估计最大报文不会超过 CIIMS 支持的 10MB 的上
限，所以不需要分段。
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments None
注释
Processing Exceptions RMS will ignore the following fields in the message
处理例外 RMS将忽略消息中下列字段
CTNM, CCAT
RMS requires CCOD to be unique across entire airport
not just within terminal.
RMS要求CCOD全机场唯一而不只针对航站楼唯一。
Since CCAT is ignored RMS expects Checkin groups to
be manually created in Rule editor to specify categories
for allocation.
由于CCAT被RMS忽略了，所以需要在规则编辑器中手动
创建值机柜台组来指定类型来分配。
```
<a id="sec-3-11-2"></a>
#### 3.11.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M CLST
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(3-4) M DNLD = It is a download
data section. from AODB/从AODB下载
消息发送的子类型. Meta Data段的一部 RESP = It is a response
分. to a subsystem request/
响应子系统的请求
ADD = Add new record/
增加新记录
UPD = Update old
record/更新旧记录
DEL = Delete old record/
删除旧记录
RECS No of records contained in XML Number(1-4) M 0 – 9999
XML中包括的记录数
CLST Identifies start of one check in counter - O This starts a new section
record. Repeats for each check in and encloses the details
counter record. of a check in counter.
一条值机柜台代码记录的开始标志。在 This section will be
每条记录中重复出现。 absent if RECS = 0
XML Tag Description Format Req Values
是新段落的起点，将值机
柜台的明细括起来。如果
RECS＝0则无该部分。
CCOD Code for this check in counter Char(1-8) M Must be unique for a
值机柜台代码 terminal
必须唯一
CTNM Check in counter name / description Char(1-30) M
值机柜台名称/描述
CNMC Check in counter name / description Char(1-30) M
Chinese
值机柜台中文名称/描述
CCAT Check in counter category Char(1) M I = International/国际
值机柜台种类 D = Domestic/国内
CTML Terminal code for this check in counter Char(1-5) P Will reference terminal
值机柜台的航站楼代码 code reference data in
AODB. Will be empty
TAG if no data available.
根据成都机场航站楼代码
参考数据表决定。空标签
表示无可用数据。
CTRA Field to identify if this is a Transfer Char(1) P Y = Transfer Counter / 中
counter 转柜台
判断这个是不是中转柜台的字段 N = Not Transfer
Counter. / 非中转柜台
Will be empty TAG if no
data available.
空标签表示无可用数据。
```
<a id="sec-3-11-3"></a>
#### 3.11.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>CLST</TYPE>
<STYP>DNLD</STYP>
</META>
<RECS>1</RECS>
<CLST>
<CCOD>C11</CCOD>
<CTNM>Desk 11 North side</CTNM>
<CNMC>北方柜台十一</CNMC>
<CCAT>D</CCAT>
<CTML>T2A</CTML>
<CTRA>Y</CTRA>
</CLST>
</MSG>
```
<a id="sec-3-12"></a>
### 3.12 AODB carousel codes event/ AODB 传送转盘代码事件
<a id="sec-3-12-1"></a>
#### 3.12.1 Event Attributes/事件属性
```text
Message Code AODBBLST
消息代码
Event Description This event occurs whenever any carousel code
事件描述 reference data is to be sent to subsystems from AODB.
当 AODB 向子系统发送任何传送转盘代码参考数据时，
产生该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered in specific cases as below:
频率 非计划的，特定的情况下触发：
A carousel code reference data download in list mode is
expected to be rolled out during installation and system
configuration.
在系统安装和配置启动时，传送转盘代码参考数据以列表
模式下载时。
A carousel code reference data download in list mode
can also be generated any time the operator decides to
distribute it from AODB to all subsystems or a given
subsystem.
在操作员由 AODB 向所有的或某个子系统以列表模式发
布传送转盘代码时。
A carousel code reference data download in list mode
can also be generated to a specific subsystem any time
the operator decides to request it from the subsystem.
在操作员响应子系统的请求而向该系统以列表模式发送传
送转盘代码时。
A carousel code reference data in incremental mode can
also be sent out to all subsystems whenever carousel
code reference data fields are updated in AODB.
AODB 中传送转盘代码参考数据字段更新，向所有子系统
以增量模式发送传送转盘代码时。
Data Range When sent from AODB in list mode one carousel code
数据范围 reference data XML will contain entire list of all carousel
codes in AODB.
当 AODB 以列表模式发送时，一个 XML 报文包括 AODB
中所有的传送转盘代码。
When sent from AODB in incremental mode one
carousel code reference data XML will contain only one
carousel code (the one that was updated) in AODB. But
the single record will have a complete snapshot of all
fields related to that record.
当 AODB 以增量模式发送时，一个 XML 报文只包括
AODB 中的一个传送转盘代码（修改的那个）。该记录包
括传送转盘代码所有的字段。
Data Count One or more carousel code reference data records in
数据数 one XML as explained above.
如上所述，一个 XML 报文包括一个或多个传送转盘代码
参考数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority Normal
优先级 正常
Expiry 480 minutes
过期 480 分钟
Message Fragmentation Although large messages are expected it will not cross
消息分段 the maximum limit of 10MB supported by CIIMS, so no
fragmentation required.
根据估计最大报文不会超过 CIIMS 支持的 10MB 的上
限，所以不需要分段。
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments None
注释 无
Processing Exceptions RMS will ignore the following fields in the message
处理例外 RMS将忽略消息中下列字段
BTNM, BCAT
RMS requires BCOD to be unique across entire airport
not just within terminal.
RMS要求BCOD全机场唯一而不只是航站楼内。
Since BCAT is ignored RMS expects Carousel groups to
be manually created in Rule editor to specify categories
for allocation.
由于RMS忽略BCAT，RMS要求手动在规则编辑器中创建
行李提取转盘组一边指定分配类别。
```
<a id="sec-3-12-2"></a>
#### 3.12.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M BLST
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(3-4) M DNLD = It is a download
data section. from AODB/从AODB下载
消息发送的子类型. Meta Data段的一部 RESP = It is a response
分. to a subsystem request/
响应子系统的请求
ADD = Add new record/
增加新记录
UPD = Update old
record/更新旧记录
DEL = Delete old record/
删除旧记录
RECS No of records contained in XML Number(1-4) M 0 – 9999
XML中包括的记录数
BLST Identifies start of one carousel record. - O This starts a new section
Repeats for each carousel record. and encloses the details
一条传送转盘代码记录的开始标志。在 of a carousel. This
每条记录中重复出现。 section will be absent if
RECS = 0
是新段落的起点，将传送
转盘的明细括起来。如果
RECS＝0则无该部分。
BCOD Code for this carousel Char(1-8) M Must be unique for a
传送转盘的代码 terminal
必须唯一
BTNM Carousel name / description Char(1-30) M
传送转盘名称/描述
BNMC Carousel name / description Chinese Char(1-30) M
传送转盘中文名称/描述
BCAT Carousel Category Char(1) M I = International/国际
传送转盘种类 D = Domestic/国内
BTML Terminal code for this carousel Char(1-5) P Will reference terminal
传送转盘的航站楼代码 code reference data in
AODB. Will be empty
TAG if no data available.
根据成都机场航站楼代码
参考数据表决定。空标签
表示无可用数据。
```
<a id="sec-3-12-3"></a>
#### 3.12.3 Event Message Sample/事件消息例子
<!-- 原 PDF 第 73 页 -->
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>BLST</TYPE>
<STYP>DNLD</STYP>
</META>
<RECS>1</RECS>
<BLST>
<BCOD>B11</BCOD>
<BTNM>Belt for night flights</BTNM>
<BNMC>Belt for night flights中文</BNMC>
<BCAT>D</BCAT>
<BTML>T2</BTML>
</BLST>
</MSG>
```
<a id="sec-3-13"></a>
### 3.13 AODB chute codes event/ AODB 行李传送带代码事件
<a id="sec-3-13-1"></a>
#### 3.13.1 Event Attributes/事件属性
```text
Message Code AODBCHLT
消息代码
Event Description This event occurs whenever any chute code reference
事件描述 data is to be sent to subsystems from AODB.
当 AODB 向子系统发送任何行李传送带代码参考数据
时，产生该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered in specific cases as below:
频率 非计划的，特定的情况下触发：
A chute code reference data download in list mode is
expected to be rolled out during installation and system
configuration.
在系统安装和配置启动时，行李传送带代码参考数据以列
表模式下载时。
A chute code reference data download in list mode can
also be generated any time the operator decides to
distribute it from AODB to all subsystems or a given
subsystem.
在操作员由 AODB 向所有的或某个子系统以列表模式发
布行李传送带代码时。
A chute code reference data download in list mode can
also be generated to a specific subsystem any time the
operator decides to request it from the subsystem.
在操作员响应子系统的请求而向该系统以列表模式发送行
李传送带代码时。
A chute code reference data in incremental mode can
also be sent out to all subsystems whenever chute code
reference data fields are updated in AODB.
AODB 中行李传送带代码参考数据字段更新，向所有子系
统以增量模式发送行李传送带代码时。
Data Range When sent from AODB in list mode one chute code
数据范围 reference data XML will contain entire list of all chute
codes in AODB.
当 AODB 以列表模式发送时，一个 XML 报文包括 AODB
中所有的行李传送带代码。
When sent from AODB in incremental mode one chute
code reference data XML will contain only one chute
code (the one that was updated) in AODB. But the single
record will have a complete snapshot of all fields related
to that record.
当 AODB 以增量模式发送时，一个 XML 报文只包括
AODB 中的一个行李传送带代码（修改的那个）。该记录
包括行李传送带代码所有的字段。
Data Count One or more chute code reference data records in one
数据数 XML as explained above.
如上所述，一个 XML 报文包括一个或多个行李传送带代
码参考数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority Normal
优先级 正常
Expiry 480 minutes
过期 480 分钟
Message Fragmentation Although large messages are expected it will not cross
消息分段 the maximum limit of 10MB supported by CIIMS, so no
fragmentation required.
根据估计最大报文不会超过 CIIMS 支持的 10MB 的上
限，所以不需要分段。
Encoding UTF 8
编码
Time Beijing local time
时间 北京时间
Comments None
注释
```
<a id="sec-3-13-2"></a>
#### 3.13.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M CHLT
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(3-4) M DNLD = It is a download
data section. from AODB/从AODB下载
消息发送的子类型. Meta Data段的一部 RESP = It is a response
分. to a subsystem request/
响应子系统的请求
ADD = Add new record/
增加新记录
UPD = Update old
record/更新旧记录
DEL = Delete old record/
删除旧记录
RECS No of records contained in XML Number(1-4) M 0 – 9999
XML中包括的记录数
CHLT Identifies start of one chute record. - O This starts a new section
Repeats for each chute record. and encloses the details
一条行李传送带代码记录的开始标志。 of a chute. This section
在每条记录中重复出现。 will be absent if RECS =
0
是新段落的起点，将行李
传送带的明细括起来。如
果RECS＝0则无该部分。
CCOD Code for this chute Char(1-8) M Must be unique for a
行李传送带代码 terminal
必须唯一
CHNM Chute name / description Char(1-30) M
行李传送带名称/描述
CNMC Chute name / description Chinese Char(1-30) M
行李传送带中文名称/描述
CTML Terminal code for this chute Char(1-5) P Will reference terminal
行李传送带的航站楼代码 code reference data in
AODB. Will be empty
TAG if no data available.
根据成都机场航站楼代码
参考数据表决定。空标签
表示无可用数据。
CCAT Chute category Char(1) M I = International/国际
XML Tag Description Format Req Values
传送带种类 D = Domestic/国内
```
<a id="sec-3-13-3"></a>
#### 3.13.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>CHLT</TYPE>
<STYP>DNLD</STYP>
</META>
<RECS>1</RECS>
<CHLT>
<CCOD>C11</CCOD>
<CHNM>Chute 11 North side</CTNM>
<CNMC>北方行李传送带十一</CNMC>
<CTML>T3A</CTML>
<CCAT>D</CCAT>
</CHLT>
</MSG>
```
<a id="sec-3-14"></a>
### 3.14 AODB resource status event/ AODB 资源状态事件
<a id="sec-3-14-1"></a>
#### 3.14.1 Event Attributes/事件属性
```text
Message Code AODBRSTA
消息代码
Event Description This event occurs whenever any AODB resource status
事件描述 is updated in AODB.
当 AODB 中任何的 AODB 资源状态改变时，产生该事
件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered by resource status data update
频率 in AODB.
非计划的，AODB 中资源状态数据改变时触发。
Reasons for resource status data update include:
资源状态改变的原因有：
Any resource is marked as disabled for a given period of
time in AODB.
在 AODB 中任何资源在给定的时间内标为无法使用时。
Any disabled resource is marked enabled cancelling the
previous disabled status entry.
任何不可用的资源标为可用，取消之前不可用状态时。
In list mode a disabled resource can also be sent to
subsystems in response to a resource status request.
在列表模式，一个不可用的资源可以在子系统请求资源状
态时发送到子系统。
Data Range Applicable to all resources (or facilities) defined by
数据范围 CDIA.
适用于成都机场定义的所有资源（或设施）。
Data Count Single resource status data record in single XML
数据数 message.
一个 XML 报文中包括一个资源数据。
Multiple records will be sent in single XML message
when AODB is responding to an RQRD message from
subsystems.
当 AODB 响应子系统的 RQRD 报文时，一个 XML 报文
包括多个记录。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments 1. Resources are default assumed as enabled.
注释 资源默认为可用。
2. When a resource is being disabled for a given
period of time with start and end date time, a
disabled indicator with an associated time period
can be sent. After the period ends, the resource
is assumed enabled default and a new enable
message will not be sent.
当一个资源在一个时间段内不可用时，可以发送
一个带有起始、结束日期时间时间段的不可用标
志。时间到期后，资源默认为可用并且将不发送
新的可用消息。
3. If the end time of the period is not predictable,
the end time tag could be omitted. Systems
receiving this message should treat this status
as lasting forever until a new status event
comes for this resource.
4. 如果时间段的终止时间无法预测，终止时间标签
可以被忽略。收到本消息的系统应当认为这个状
态将永远持续下去，直到为本资源发来了新的状
态事件。When a previous disabled period
needs to be enabled, an enabled indicator with
start date/time will be sent. No end date time
needs to be sent because being enabled is
default status.
当前一个不可用期限要激活，会发送一个带有起
始日期时间的可用标志。不需要发送结束日期时
间，由于缺省状态就是可用的。
Processing Exceptions NONE
处理例外
```
<a id="sec-3-14-2"></a>
#### 3.14.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M RSTA
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(4) M DNLD = It is a download
data section. from AODB/从AODB中下
消息发送的子类型. Meta Data段的一部 载
分. RESP = It is a response
to a subsystem request/
对子系统请求的响应
RECS No of records contained in XML Number(1-4) M 0 – 9999
XML中包括的记录数。
RSTA Identifies start of the Resource status - M This section can repeat
section. multiple times when
表明资源状态部分的起点 AODB is responding to a
resource status request
from subsystems
响应子系统请求资源状态
时，该部分可以重复多次
RTYP Type of resource Char(4) M BELT = Baggage Belt/行
资源类型 李带
CNTR = Check In
Counter/值机柜台
GATE = Gate/登机门
XML Tag Description Format Req Values
STND = Stand/机位
RSID The identifier of the resource Char(1-8) M Depending on type of
资源标识 resource as above, this
will containing the unique
resource identifier for e.g.
gate number or counter
number, carousel
number, stand number
etc
根据前面的资源类型，可
以包括单独的资源类型标
识如登机门号或柜台号，
传送带号，机位号。
STAT Indicate current status Char(1) M E = Enabled/可用
指明当前状态 D = Disabled/不可用
RDST Start date/time for disabling/enabling Char(11) M DDMONYYHHMM
the resource. Local time 24 hr format.
不可用/可用资源的开始日期/时间 当地时间24小时格式
RDET End date/time for disabling/enabling Char(11) O DDMONYYHHMM
the resource. Local time 24 hr format.
不可用/可用资源的结束日期/时间 当地时间24小时格式
RRMK Remarks with reason for disabling the Char(1-40) O Free text
resource. 自由格式文本
资源不可用的原因注释
```
<a id="sec-3-14-3"></a>
#### 3.14.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>RSTA</TYPE>
<STYP>DNLD</STYP>
</META>
<RECS>1</RECS>
<RSTA>
<RTYP>GATE</RTYP>
<RSID>G101</RSID>
<STAT>D</STAT>
<RDST>13JAN052200</RDST>
<RDET>20MAY052359</RDET>
<RRMK>DOOR JAMMED</RRMK>
</RSTA>
</MSG>
```
<a id="sec-3-15"></a>
### 3.15 AODB reference data response to RMS event / AODB 参考数据应答 RMS 事件
<a id="sec-3-15-1"></a>
#### 3.15.1 Event Attributes/事件属性
```text
Message Code AODBRESPRMSRQRD
消息代码
Event Description This is sent by AODB in response to an RQRD event
事件描述 from RMS.
这是 AODB 发送的对 RMS 发送的 RQRD 的响应。
Single Recipient Yes
接收者 是
Frequency Unscheduled and always sent as an automatic response
频率 to a reference data request from RMS.
非计划的，是 RMS 发送的参考数据请求的自动回复
Data Range Controlled by RMS request
数据范围 由 RMS 请求控制
Data Count Multiple reference data records in single XML message.
数据数 Number will depend on reference data in CDIA and also
upon RMS request.
一条 XML 报文包括多条参考数据记录。
条数根据成都机场的定义和 RMS 请求而定。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority Normal
优先级 正常
Expiry 480 minutes
过期 4
Message Fragmentation 480 minutes
消息分段 480 分钟
Encoding None
编码 无
Time UTF 8
时间
Comments Beijing local time
注释 北京当地时间
```
<a id="sec-3-15-2"></a>
#### 3.15.2 Event Message Format/事件消息格式
```text
The response event message formats from AODB to RMS request for reference data
will exactly be the same as described in below table based on the nature of request
from RMS. Except the subtype STYP will be RESP.
AODB响应RM参考数据请求的报文格式与RM的请求相同。只是子类型STYP改为
RESP。
RMS request subtype STYP in AODB response format
RMSRQRD reference
COUL Refer AODBCOUL
ARPT Refer AODBARPT
AIRL Refer AODBAIRL
AIRC Refer AODBAIRC
REGN Refer AODBREGN
ORGN Refer AODBORGN
FLTL Refer AODBFLTL
TLST Refer AODBTLST
SLST Refer AODBSLST
GLST Refer AODBGLST
CLST Refer AODBCLST
BLST Refer AODBBLST
CHLT Refer AODBCHLT
RSTA Refer AODBRSTA
```
<a id="sec-3-15-3"></a>
#### 3.15.3 Event Message Sample/事件消息例子
See above section and refer to corresponding samples as above.
参考前面部分及其对应例子。
<a id="sec-3-16"></a>
### 3.16 AODB daily flight schedule event/ AODB 日航班计划事件
<a id="sec-3-16-1"></a>
#### 3.16.1 Event Attributes/事件属性
```text
Message Code AODBSCHD
消息代码
Event Description This event occurs when AODB has to deliver daily
事件描述 schedules to various other airport systems
当 AODB 向机场中其他各个系统发送日航班计划时发生
该事件。
Single Recipient No
接收者 无
Frequency A next day daily schedule is expected to be rolled out
频率 every night around 2000 containing flight records for
next „x‟ hours (48 typically).
每天晚上 20：00 左右开始发布若干小时（通常 48）内的
日计划时刻表。
A confirmed daily schedule is expected to be rolled out
every night around 2200 containing fight records for next
„x‟ hours (48 typically).
每天晚上 22：00 左右开始发布若干小时（通常 48）内已
确认的日计划时刻表。
A daily schedule can also be generated any time the
operator decides to distribute it from AODB to all
subsystems or a given subsystem.
在操作员由 AODB 向所有的或某个子系统发布日计划时
刻表时。
A daily schedule can also be generated to a specific
subsystem any time the operator decides to request it
from the subsystem.
在操作员响应子系统的请求而向该系统发送日计划时刻表
时。
Data Range When sent from AODB (unsolicited by a subsystem) a
数据范围 daily schedule XML will contain next „x‟ hour flights. This
is not decided by CDIA but typically expected as 48
hours.
当从 AODB 发送日计划时刻表时（非子系统请求的），
XML 包括若干小时内的航班日时刻表。这不是由成都机
场定，通常是 48 小时。
When solicited from subsystem side, a daily schedule
XML containing records for the date range requested by
the subsystem will be returned. Validation will be
performed that the requested date range does not
exceed the „x‟ hour window.
当子系统请求时，XML 中包括的日计划时刻表范围是子
系统请求的数据。会对请求的日期范围进行有效性检查，
是否超过规定的若干小时。
Data Count Multiple daily flight records in single XML message.
数据数 Number will depend on daily flights in CDIA.
在一条 XML 报文中包括多条日航班记录。数量根据机场
的日航班数而定。
Data Conversion None
数据转换 无
Sort Sequence All departure flights occur before arrival flights since the
排列序列号 arrival flights only contain turnaround link information.
所有离港航班都先于到港航班，由于只有到港航班含有起
降匹配连接信息。
All code share flights will be sent after their master
records to ensure the master records are already
present whole processing.
所有的代码共享航班跟在主航班后，确保处理时主航班记
录已经存在。
Otherwise daily flight records in the XML will not be
sorted in any particular order.
其它 XML 中的日航班记录无一定的顺序。
Acknowledgment None
确认 无
Priority Normal
优先级 正常
Expiry 480 minutes
过期 480 分钟
Message Fragmentation Although large messages are expected it will not cross
消息分段 the maximum limit of 10MB supported by CIIMS, so no
fragmentation required.
根据估计最大报文不会超过 CIIMS 支持的 10MB 的上
限，所以不需要分段。
Encoding UTF 8
编码
Time Beijing local time
时间 北京时间
Comments 1. A daily schedule from AODB will not have flights
注释 delayed from previous day. It is up to the
subsystems to retain the delayed flights in its
database and clear out other old flights if
necessary. But the operational data for these
flights will be sent in current day.
AODB中的日计划时刻表不包括前一天的延误航班。
在子系统的数据库中保留这些延误航班并根据需要清
除那些旧航班数据。当天这些航班的操作数据会发
送。
2. Daily schedule XML message is designed to
contain a complete snapshot of all the latest
data available in AODB. So the optional fields
(O/P) will be filled depending on whether
relevant data item is available in AODB or not.
This is to ensure any subsystem can get a
complete snapshot of all flight data in AODB.
日计划时刻表的XML报文包括AODB中完整的有效数
据。其中的可选字段是否有值根据AODB的数据而
定。这样就保证了所有子系统可以得到AODB中所有
日计划航班的全部数据。
3. Some of fields in daily schedule XML might not
be used by a specific subsystem, in which case
the subsystem should ignore such fields, though
it will be sent as part of the standard message
format.
有些字段在某个子系统中没用，此时该子系统可以忽
略该字段。
4. For all optional fields not sent in the latest daily
schedule, it means such information is not
present in AODB, so the subsystems should
delete such information, if already present in
their systems locally.
如果在完整的日计划时刻表中未发送那些可选字段则
表明AODB该信息不存在了。如果子系统中已有这些
字段，则应该删除。
```
<a id="sec-3-16-2"></a>
#### 3.16.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M SCHD
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(4) M DNLD – Indicates this is
data Section. a scheduled message
消息发送的子类型. Meta Data段的一部 download from AODB./从
分. AODB中下载时刻表信息
RESP – Indicates this is
generated in response to
a daily schedule request
event from the
subsystem./响应子系统的
请求而发送的日计划时刻
表。
ADFT – Indicates this is
an adhoc flight (1 flight
record only)/表示是一个
adhoc航班（仅一个航班
记录）
SCHD Identifies start of the daily flight data. - M This starts a section and
Occurs once per message encloses several flight
标识一个日航班数据的开始。一个报文 records
一个。 是新段落的起点，将几个
航班的明细括起来。
RECS No of flight records contained Number(1-4) M 0 – 9999
包括的航班数
FLTR Identifies start of one flight record. At O This starts a section and
least one flight record is required per encloses details of one
daily schedule message. This section flight element. Will be
repeats for each flight record absent if RECS = 0.
标识一条航班记录的开始。每个日计划 是新段落的起点，将航班
时刻表至少有一条航班记录。每条航班 的明细括起来。如果
记录中重复出现。 RECS＝0则无该部分。
FLID Unique AODB ID for identifying a flight Number(1-12) M
一个航班在AODB中的唯一ID
XML Tag Description Format Req Values
ALCD Airline code Char(2-3) M IATA operator code
航空公司代码 IATA操作代码
ALSC Airline subcompany code Char(1-10) O
航空公司子公司代码
FLNO Flight number Char(1-12) M
航班号
MVIN Movement indicator Char(1) M A – Arrival/到达
运行标识 D – Departure/离港
SODT Scheduled operation date / time of Char(11) M DDMONYYHHMM
flight. STA in case of arrival and STD Local time 24 hr format
in case of departure
当地时间24小时格式
航班计划日期/时间。STA到达，STD离
港。
FLTY Flight type like passenger, cargo, Char(1) M Reference table to be
military, VIP etc decided by CDIA. AODB
航班类型如客机、货机、军用、VIP等 will send all flights of all
types by default and the
subsystems are expected
to accept/ignore full/part
of the schedule, based
on their requirements.
由成都机场相关数据表
定。AODB将默认发送所
有类型的航班，子系统根
据需要接受/忽略全部/部
分时刻表。
FLIN Flight indicator Char(1) M D – Domestic/国内
航班标识 I – International/国际
M – Mixed/混合
R – Regional/地区
ROUT Identifies start of one routing record. At Number(1) M This starts a new section
least one routing record is required per and encloses the routing
flight. This section repeats for each details of flight.
flight step. Includes a parameter called 是新段落的起点，将航班
RTNO to identify the route number 的航线明细括起来。
标识一个航线的开始。每个航班至少有
一条航线。每个航段中重复出现。包括
一个RTNO参数表示航段数。
APCD This is the previous airport for arrivals Char(3) M IATA airport code
and next airport for departures IATA机场代码
前一个到达机场和下个离港机场
SCAT The scheduled date time of arrival at Char(11) O DDMONYYHHMM
this stop Local time 24 hr format.
本站计划到达日期时间 This will be absent for
starting point of an arrival
flight.
当地时间24小时格式。一
XML Tag Description Format Req Values
个航班起点则无该项。
SCDT The scheduled date time of departure Char(11) O DDMONYYHHMM
from this stop Local time 24 hr format.
本站计划离港日期时间 This will be absent for
last stop of flight
当地时间24小时格式
终点站则无该项。
ACFT Aircraft type used in this flight Char(3) M IATA aircraft type
航班使用的机型 IATA机型
RENO Registration or tail number of flight Char(1-10) O
航班注册号或尾号
TAOP Turnaround operator when it leaves Char(2-3) O IATA operator code.
current airport Present only for arrivals.
离开当前机场时起降匹配连接航班的承 IATA承运人代码。仅到达
运人 时有效。
TAFL Turnaround flight number when it Char(1-12) O Present only for arrivals.
leaves current airport 仅到达时有效。
离开当前机场时起降匹配连接航班的航
班号
TAID Unique AODB ID of the turnaround Number(1-12) O
flight
中转航班唯一的AODB ID
TRML Terminal where the flight operates Char(1-5) O
航班航站楼
MAXP Maximum passengers that this flight Number(1-3) O 0 – 999
can carry
该航班最大载客数
CSOP Operator code of master flight if this is Char(2-3) O IATA operator code
a code share flight IATA操作代码
共享航班的主航班承运人代码
CSFT Flight number of master flight if this is a Char(1-12) O
code share flight
共享航班的主航班号
ESTT Estimated time of flight. This will point Char(11) O DDMONYYHHMM
to ETA for Arrivals and ETD for Local time 24 hr format
departures
当地时间24小时格式
航班预计时间。由航班到达ETA和离港
ETD计算出。
ACTT Actual time of flight. This will point to Char(11) O DDMONYYHHMM
ATA for Arrivals and ATD for Local time 24 hr format
departures
当地时间24小时格式
航班实际时间。由航班到达ATA和离港
ATD计算出。
CHDT Has a parameter CHNO to identify the Number(1) O This starts a chute
chute number associated with flight section and includes
which has multiple chute allocations. chute specific information
XML Tag Description Format Req Values
This data repeats for each chute of a as below. This section
flight. will be absent if no
有多行李传送带的航班带参数CHNO表 chutes assigned for flight.
示相关的行李传送带号。在一个航班的 行李传送带的开始，包括
每条传送带中重复出现。 传送带的相关信息。若航
班未分配传送带则无该部
分。
CHUT This is the baggage chute allocated for Char(1-8) M
a departure flight.
离港航班的行李传送带位置
CCLS Chute class Char(1) M Following class codes will
行李传送带等级 be supported:
支持如下等级代码
F = First class/头等
C = Business class/商务
Y = Economy class/经济
X = No specific class/全
部
If more than one class
can be used for chute
allocationon a single
chute, CHDT will be
repeated for each class.
如果一个行李传送带可被
用于多个等级的行李传送
带分配，那么CHDT将为
每个等级重复一次。
PCBT Planned time for chute start usage for Char(11) M DDMONYYHHMM
flight Local time 24 hr format
航班行李转盘计划开始使用时间 当地时间24小时格式
PCET Planned time for chute end usage for Char(11) M DDMONYYHHMM
flight Local time 24 hr format
航班行李转盘计划结束使用时间 当地时间24小时格式
CBTM Actual Time when the flight started Char(11) O DDMONYYHHMM
using the chute Local time 24 hr format
航班实际开始使用行李传送带的时间 当地时间24小时格式
CETM Actual Time when the flight stopped Char(11) O DDMONYYHHMM
using the chute Local time 24 hr format
航班实际使用行李传送带的结束时间 当地时间24小时格式
CTYP Domestic or International indicator of Char(1) M D – Domestic/国内
chute resource I – International/国际
行李传送带资源的国内国际标识
GTDT This indicates the start of gate related Number(1) O This starts a new section
data for a flight record. This includes a and includes gate
parameter GTNO to identify the gate specific information as
record number for a flight with multiple below. This section will
XML Tag Description Format Req Values
gates. This data repeats for each gate be absent if no gates
of a flight. assigned for flight.
表示航班登机门数据的开始，航班有多 新段落的开始，包括登机
登机门时会带参数GTNO表示登机门 门的相关信息。若航班未
号。每个登机门数据中重复出现。 分配登机门则无该部分。
GATE Gate number assigned to this flight Char(1-8) M Gate code reference
航班分配的登机门号 table to be decided by
CDIA
根据成都机场的登机门数
据决定。
PGOT Planned time for gate open for flight Char(11) M DDMONYYHHMM
Local time 24 hr format
当地时间24小时格式
PGCT Planned time for gate close for flight Char(11) M DDMONYYHHMM
Local time 24 hr format
当地时间24小时格式
GOTM Time when the flight was gated Char(11) O DDMONYYHHMM
登机门开始时间 Local time 24 hr format
当地时间24小时格式
GCTM Time when the gate was closed Char(11) O DDMONYYHHMM
登机门关闭时间 Local time 24 hr format
当地时间24小时格式
GTYP Domestic or international indicator of Char(1) M D – Domestic/国内
gate resource I – International/国际
登机门资源国内国际标识
STND Current parking stand allocated to this Char(1-8) O Stand code reference
flight table to be decided by
该航班当前停机位位置 CDIA. When there are
multiple planned stands
and the flight has not
arrived yet, this will
contain the first planned
stand. Subsequently
whenever the flight
chocks on to a stand, this
field will contain latest
chock on stand.
机位代码根据成都机场数
据决定。计划多机位且航
班未到达时，该域包括计
划中的第一个机位。航班
停于机位后，该域包括机
位最后的上轮挡。
PSDT This indicates the start of planned Number(1) O This is start of
stands data for a flight record. This information for one stand
includes a parameter PSNO to identify and the section could
the planned stand sequence number repeat for multiple
for a flight with multiple planned planned stands.
XML Tag Description Format Req Values
stands. One record will have data for Maximum 9 planned
one planned stand. stands are expected per
航班计划机位数据的开始。多机位航班 flight.
带有参数PSNO表示计划的机位号。一 是一个机位信息的开始，
个计划机位有一个记录。 多机位可重复。每个航班
最多有9个计划机位。
PSST This is the actual parking stand for Char(1-8) M Stand code reference
current planned stand record table to be decided by
当前计划机位记录的实际停机位 CDIA.
根据成都机场机位表数据
决定。
STST Start time of stand allocation for the Char(11) O DDMONYYHHMM
flight. Local time 24 hr format.
航班机位分配的开始时间 当地时间24小时格式
STET End time of stand allocation for the Char(11) O DDMONYYHHMM
flight. Local time 24 hr format.
航班机位分配的结束时间 当地时间24小时格式
CKDT This indicates the start of check in Number(1-2) O This starts a new section
counter related data for a flight record. and includes check in
This includes a parameter CKNO to specific information as
identify the check In counter record below
number for a flight with multiple check 是一个新段落的开始，包
in counters. One record will have data 括相关值机柜台的信息。
for one check in counter assignment
and will repeat for each counter
assignment.
航班相关的值机柜台数据的开始。多值
机柜台航班带有参数CKNO表示值机柜
台号。一个值机柜台有一个记录，每个
柜台重复出现。
CHKC Check in counter number assigned to Char(1-8) M Check in counter
this departure flight reference table to be
离港航班的值机柜台号。 decided by CDIA.
根据成都机场的柜台号数
据决定。
CCLS Check in counter class Char(1) M Following class codes will
值机柜台等级 be supported:
支持如下等级代码
F = First class/头等
C = Business class/商务
Y = Economy class/经济
X = No specific class/无
特定等级
If more than one class
can be opened for
checkin on a single
counter, CKDT will be
XML Tag Description Format Req Values
repeated for each class.
如果一个值机柜台可为多
于一个舱位服务的话，
CKDT 将为每个等级重复
一遍。
PCOT Planned time for check in for flight Char(11) M DDMONYYHHMM
该航班计划的值机时间 Local time 24 hr format
当地时间24小时格式
PCCT Planned time for check close for flight Char(11) M DDMONYYHHMM
该航班计划的值机关闭时间 Local time 24 hr format
当地时间24小时格式
COTM Time when check in was open for flight Char(11) O DDMONYYHHMM
航班值机开始时间 Local time 24 hr format
当地时间24小时格式
CCTM Time when check in was closed for Char(11) O DDMONYYHHMM
flight Local time 24 hr format
航班值机关闭时间 当地时间24小时格式
CTYP Domestic or International indicator of Char(1) M D – Domestic/国内
check in counter resource I – International/国际
值机柜台资源的国内国际标识
PHAG Passenger handling agent for flight Number(1-9) O Organization id of
航班旅客处理柜员 passenger handling
agent. Reference codes
to be decided by CDIA.
旅客处理柜员的机构ID。
参考代码由国际成都机场
定义。
CNCL Cancellation date time. Only present if Char(11) O DDMONYYHHMM
the flight is cancelled Local time 24 hr format
取消日期时间。仅在航班取消时出现。 当地时间24小时格式
DELY Delay information. This includes three Char(1-80) O Delay code reference
parameters to DELY tag and delay data to be decided by
remarks within the tags. CDIA. This section is
延误信息。在DELY标签后有三个参 optional but when
数。 present CODE
mandatory. The DELY
CODE = Char(1-3), the delay code/1-3 tag will repeat for all
字符，延误码 delays recorded in AODB
STRT = Char(11) DDMONYYHHMM, for current flight.
When delay started/延误开始时间 延误码由成都机场相关数
DURA = HHMM. How long/时间长度 据决定。该部分可选，出
现CODE时必选。AODB
中当前航班的所有延误记
录中重复出现。
REMC Flight free text remarks Char(1-80) O
航班自由文本注释
XML Tag Description Format Req Values
CLDT This indicates the start of carousel Number(1) O This starts a new section
related data for a flight record. This and includes carousel
includes a parameter CLNO to identify specific information as
the carousel record number for a flight below
with multiple carousels. 新段落的开始，包括传送
航班的行李传送转盘数据的开始。有多 转盘的相关信息。
传送转盘的航班带有参数CLNO表示传
送转盘的记录号。
BELT Baggage belt number for arrival flights Char(1-8) M Carousel codes
到达航班的行李传送带号 reference table to be
decided by CDIA.
由成都机场数据决定。
BCLS Baggage carousel class Char(1) M Following class codes will
行李传送转盘等级 be supported:
支持如下等级代码
F = First class/头等
C = Business class/商务
Y = Economy class/经济
X = No specific class/全
部
If more than one class
can be used for carousel
allocation on a single
belt, CLDT will be
repeated for each class.
如果一个行礼转盘被分配
给多个等级服务，那么
CLDT 将 为 每 个 等 级 重 复
一次。
PCOT Planned time for carousel start usage Char(11) M DDMONYYHHMM
for flight Local time 24 hr format
航班行李传送转盘计划开始时间。 当地时间24小时格式
PCCT Planned time for carousel end usage Char(11) M DDMONYYHHMM
for flight Local time 24 hr format
航班行李传送转盘计划结束时间 当地时间24小时格式
FBAG Date and time when the first bag was Char(11) O DDMONYYHHMM
placed on this belt for an arrival flight Local time 24 hr format
到达航班第一件行李放置传送带的日期 当地时间24小时格式
时间。
LBAG Date and time when the last bag Char(11) O DDMONYYHHMM
leaves this belt for an arrival flight Local time 24 hr format
到达航班最后一件行李离开传送带的日 当地时间24小时格式
期时间
BTYP Domestic or international indicator of Char(1) M D – Domestic/国内
belt resource I – International/国际
传送带资源的国内国际标识
XML Tag Description Format Req Values
BOTM Boarding open time for the departure Char(11) O DDMONYYHHMM
flight Local time 24 hr format
离港航班登机开始时间 当地时间24小时格式
LACL Time for last call of departure flight Char(11) O DDMONYYHHMM
离港航班最后通知时间 Local time 24 hr format
当地时间24小时格式
FINT Finals Time. This is set when an arrival Char(11) O DDMONYYHHMM
flight is approaching and confirms Local time 24 hr format
landing, say 10 minutes prior to arrival.
当地时间24小时格式
Typically used to confirm resources
committed for the flight in the airport.
最终时间。当到达航班将要到达，确认
降落时设定，比如降落前10分钟。一般
用于确认航班在机场的资源使用确认。
CHOT This identifies the start of chocks time Number(1) O This section contains
data section. This includes a information for one ON or
parameter CSNO Number(1) to OFF chocks. This
indicate the stand sequence number repeats for each such
against which this chocks time is being stand move and includes
reported (Note this is not chocks data for stand to stand
sequence but stand sequence) moves as well as stand
轮挡时间数据部分的开始标识。带有参 to hangar moves.
数CSNO 号（1）表示该轮挡时间报告 该部分包括一个上下轮挡
时对应的机位号（非轮挡号而是机位 信息。在每个机位移动数
号） 据中重复出现。机位移动
包括机位到机位的和机位
到机库的。
CHTM Chocks time. On chocks or off chocks Char(11) M DDMONYYHHMM
is determined by chocks indicator Local time 24 hr format
CHID below
当地时间24小时格式
轮挡时间。下面的CHID表示上下轮挡
CHID Chocks indicator Char(2-3) M OFF or ON
轮挡标识 上或下
CHST The chocks stand against which the Char(1-8) M Actual stand number
chocks time is reported by VDGS 实际的机位号
VDGS报告的轮挡时间对应的轮挡机位
APPT Approved time for departures Char(11) O DDMONYYHHMM
批准的离港时间 Local time 24 hr format
当地时间24小时格式
EGSR Engine start request for departures Char(11) O DDMONYYHHMM
离港时引擎发动请求 Local time 24 hr format
当地时间24小时格式
EGST Engine start time for departures Char(11) O DDMONYYHHMM
离港引擎发动时间 Local time 24 hr format
当地时间24小时格式
FHAG Field (or Ground) Handling agent for Number(1-9) O Organization id of field
XML Tag Description Format Req Values
flight. handling agent.
航班的机坪（或外场）处理代理 Reference codes to be
decided by CDIA.
机坪处理代理的机构代
码。参考成都机场的相关
代码
MHAG Maintenance Handling agent for flight. Number(1-9) O Organization id of
航班维护处理代理 maintenance handling
agent. Reference codes
to be decided by CDIA.
维护处理代理的机构代
码。参考成都机场的相关
代码
VIPP VIP passengers. This will be present Number(1-3) O Number of VIP
when there are VIP passengers on that passengers in current
flight flight
VIP旅客。当航班中有VIP旅客时出现 当前航班的VIP旅客数
VIPR VIP flight ranking flag Number(1) P A single digit number to
VIP航班等级标志 be decided by CDIA to
indicate VIP ranking. 0
means not VIP.
一个单一数字表示VIP的
等级。具体数字将由CDIA
决定。0表示不是VIP航
班。
An empty TAG means
the existing VIP rating
value is being deleted.
空表示VIP级别值被删除
FDIV Contains a descriptive reason as to Char(1-30) O Free text diversion
why the flight has been diverted. Has reason.
two parameters called DDES and 自由文本格式
DDIR. DDES is to indicate the divert
Parameter DDES =
related airport. DDIR is to indicate the
Char(3)
divert direction (from or to the airport
specified in DDES). IATA airport code of
airport diverted to or
航班转场的原因描述。带有两个参数
airport diverted from.
DDES和DDIR。DDES表示航班转场相
关的机场。DDIR表示转场方向（从或 转场到的机场或从这个机
到DDES指定的机场）。 场转场到成都，使用IATA
机场代码
Parameter DDIR =
Char(2-4)
Divert direction. Valid
values are TO and
FROM
备降的方向，合法的值为
“TO”和“FROM”。
An empty parameter
XML Tag Description Format Req Values
DDES=”” means the
existing flight diverted
indicator value is being
unset.
FRET Contains a descriptive reason as to Char(1-30) O Free text reason for
why the flight has returned. Has a returned flight.
parameter called REID to indicate if it 原因格式是文本
is an air or ground return.
Parameter REID =
包括一个航班返航原因的描述。带有
Char(1)
REID参数表示是返航或是地面返航。
G = Ground return/地面返
航
A = Air return/返航
ABTM This identifies start of Air bridge time Number(2) O Parameter ASNO =
data section. Has a parameter called Number(2) Sequence
ASNO to indicate the sequence of the number of attach/detach
airbridge attach/detach operation. operation.
ASNO is operation sequence i.e. each 参数ASNO=Number(2)是
attach/detach will be sequentially 靠桥/离桥操作的序列号。
identified.
This section repeats for
这个标签标识了登机桥时间数据部分的 each attach/detach
开始。有一个参数ASNO，它指得是登 operation that has been
机桥靠桥/离桥操作的序列。 performed against a
ASNO是操作顺序号，也就是说每个靠 flight.
桥/离桥都将被顺序的标识出。 这个部分针对一个航班执
行的每个靠桥、离桥动作
进行重复。
ABDG This is the airbridge resource involved Char(1-8) M Refers to the list of
in the attach/detach operation Airbridges set up by
这个靠桥、离桥动作所涉及的登机桥资 CDIA as reference data
源 in AODB.
参考CDIA在AODB中建立
起来的登机桥列表参考数
据。
ABOP This identifies if the current operation is Char(1) M A – Attach/连接
an attach or a detach D – Detach/断开
这个标签标识出当前操作是靠桥还是离
桥操作。
AOTM This is the actual airbridge operation Char(11) M DDMONYYHHMM
time Local time 24 hr format.
这个标签是实际登机桥操作时间 当地时间24小时格式
FLAB Contains a descriptive reason as to Char(1-30) O Descriptive text for
why the flight‟s landing has been aborting landing.
aborted. Has a parameter called ARES 原因格式是文本
to indicate the actual reason code for
Parameter ARES =
aborting.
Char(1)
包括一个航班着陆中止原因的描述。带
O = Overshot indicator
有ARES参数表示中止的原因码。
set as aircraft cannot
land in give runway/飞机
XML Tag Description Format Req Values
无法在指定的跑道降落
G = Go Around indicator
set, aircraft circles
around/飞机绕场
SRVT Identifies the start of a section and Char(3) O Starts a new section.
includes details for one service. Repeats for each service
新段落的开始，包括一个服务的明细。 being reported. All
service details are
included within one
messages
一个新段落的开始。每个
报告的服务中重复出现。
在一个报文中包括所有的
服务明细。
SRTC Service transaction code Char(1-4) M Service type. Reference
服务交易码 data to be decided by
CDIA.
服务类型。由成都机场定
义。
SRQT Service quantity Number(1-2) P Indicates number for
服务数量 service units used
使用的服务单位数
SRST Service start time Char(11) P DDMONYYHHMM
服务开始时间 Local time 24 hr format.
当地时间24小时格式
SRET Service end time Char(11) P DDMONYYHHMM
服务结束时间 Local time 24 hr format.
当地时间24小时格式
SRPR Service provider Number(1-9) P Organization ID of the
服务提供者 prime company providing
service. Reference data
to be decided by CDIA.
提供服务主公司的机构代
码。由成都机场定义。
VIPF Identifies the start of a section and Char(3) O Starts a new section.
includes details for one VIP. Repeats for each VIP
一个新段落的开始包括一个VIP的明 person associated with
细。 this flight.
新段落的开始。航班的每
个VIP旅客中重复出现。
VPCD VIP Personnel Code Char(1-10) M
VIP个人代码
VFES VIP Entourage Size Number(1-3) O
VIP随从人员数量
VIPT Details of transactions associated with Char(3) O Starts a new section.
a VIP. Repeats for each VIP
VIP关联交易的明细。 person associated with
XML Tag Description Format Req Values
this flight.
新段落的开始。航班每个
VIP旅客中重复出现。
VSCD VIP Service Code Char(10) M
VIP服务码
VTQY VIP Quantity Number(1-12) P
VIP数量
VTST VIP Service Start Date Time Char(11) P DDMONYYHHMM
VIP服务开始日期时间 Local time 24 hr format
当地时间24小时格式
VTET VIP Service End Date Time Char(11) P DDMONYYHHMM
VIP服务结束日期时间 Local time 24 hr format
当地时间24小时格式
LBNO No of local bags checked in for Number(1-3) O
departure flights
离港航班本地值机行李件数
LBWT Total local checked in bag weight for Number(1-9,2) O In kilograms
departure flights 单位公斤
离港航班本地值机行李总重量
PAXC Total number of passengers on the Number(1-3) O
flight
航班旅客总数
ERUT Identifies start of one entire flight Number(1) M This starts a new section
routing. At least two routing records and encloses the entire
are expected for normal flights and routing details of flight.
atleast three routing records are 一个新段落的开始，含有
required for flights transiting CTU. This 航班完整航线的细节信
section repeats for each such route
息。
record. Includes a parameter called
RTNO to identify the route number
一条完整航线记录的开始。每个一般航
班需要至少两 条航线记 录 。而对于在
CTU过站的航班则最少三条航段记录。
每个航段中重复出现该部分。带有参数
RTNO表示航段号。
This TAG is different from ROUT in
that the entire flight route is included.
For normal flights this means CTU is
also included as part of ERUT and for
transit flights the entire route including
route before arrival in CTU and route
after departure from CTU are included
as part of both arrival and departure
flights. Further RTNO is ordered in
such a way that it represents the actual
route of the flight in ascending order
from its origin to its destination with
XML Tag Description Format Req Values
CTU as part of the route. For e.g. if a
flight flies MEL-SHA-CTU-HRB, there
will be two flights in AODB. MEL-SHA-
CTU Arrival and CTU-HRB Departure.
In this case the ROUT tag for Arrival
flight will only have MEL-SHA in that
order, while ERUT will have MEL-SHA-
CTU-HRB in that order. Similarly the
ROUT tag for Departure flight will only
have HRB, while ERUT will have MEL-
SHA-CTU-HRB in that order.
这个标签和ROUT标签是有区别的，在
这个标签里包含的航线是完整航线。对
于一般航班而言，这意味着CTU也将被
包含在航线之中，成为ERUT的一部
分。对于在CTU的过站航班，整个航线
含有在成都到港之前的航线和从成都离
港以后的航线。到港航班和离港航班将
同时使用这个完整航线。此外，RTNO
是用实际航线按升序排列的，从起始机
场到最终目的机场。CTU应是该航线的
一部分。举例来讲，一个航班飞MEL-
SHA-CTU-HRB，在AODB中会有两个
航班。MEL-SHA-CTU到港航班和
CTU-HRB离港航班。在这种情况下，
ROUT标签中只有MEL-SHA，而ERUT
将有MEL-SHA-CTU-HRB。同样的，离
港航班的ROUT标签只有HRB，而
ERUT则将有MEL-SHA-CTU-HRB。
APCD Airport related to this route. Char(3) M IATA airport code
这个航段相关的机场。 IATA机场代码
SCAT The scheduled date time of arrival at Char(11) O DDMONYYHHMM
this stop Local time 24 hr format.
这一站计划到达日期时间 This will be absent for first
step of the flight route.
当地时间24小时格式
对航班起点站无该字段。
SCDT The scheduled date time of departure Char(11) O DDMONYYHHMM
from this stop Local time 24 hr format.
这一计划离港日期时间 This will be absent for last
step of the flight route.
当地时间24小时格式
对航班终点站无该字段。
```
<a id="sec-3-16-3"></a>
#### 3.16.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>122143</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>SCHD</TYPE>
<STYP>DNLD</STYP>
</META>
<SCHD>
<RECS>2</RECS>
<FLTR>
<FLID>121112312</FLID>
<ALCD>UA</ALCD>
<FLNO>UA724</FLNO>
<MVIN>D</MVIN>
<SODT>15DEC031723</SODT>
<FLTY>P</FLTY>
<FLIN>I</FLIN>
<ROUT RTNO=”1”>
<APCD>ORD</APCD>
<SCAT>15DEC031125</SCAT>
<SCDT>15DEC031315</SCDT>
</ROUT>
<ROUT RTNO=”2”>
<APCD>MSP</APCD>
<SCAT>15DEC031325</SCAT>
<SCDT></SCDT>
</ROUT>
<ACFT>747</ACFT>
<RENO>YK2729</RENO>
<TAOP>UA</TAOP>
<TAFL>UA723</TAFL>
<TRML>1</TRML>
<MAXP>320</MAXP>
<ESTT>15DEC031807</ESTT>
<CHDT CHNO=”1”>
<CHUT>CH0021</CHUT>
<CCLS>X</CCLS>
<PCBT>15DEC031530</PCBT>
<PCET>15DEC031830</PCET>
<CBTM>15DEC031520</CBTM>
<CETM>15DEC031900</CETM>
<CTYP>D</CTYP>
</CHDT>
<CHDT CHNO=”2”>
<CHUT>CH0025</CHUT>
<CCLS>X</CCLS>
<PCBT>15DEC031530</PCBT>
<PCET>15DEC031830</PCET>
<CBTM>15DEC031525</CBTM>
<CETM>15DEC031900</CETM>
<CTYP>D</CTYP>
</CHDT>
<GTDT GTNO=”1”>
<GATE>G28</GATE>
<PGOT>15DEC031805</PGOT>
<PGCT>15DEC031925</PGCT>
<GOTM>15DEC031825</GOTM>
<GTYP>D</GTYP>
</GTDT>
<STND>S209</STND>
<CKDT CKNO=”1”>
<CHKC>01</CHKC>
<CCLS>X</CCLS>
<PCOT>15DEC031515</PCOT>
<PCCT>15DEC031725</PCCT>
<COTM>15DEC031525</COTM>
<CTYP>D</CTYP>
</CKDT>
<CKDT CKNO=”2”>
<CHKC>17</CHKC>
<CCLS>X</CCLS>
<PCOT>15DEC031515</PCOT>
<PCCT>15DEC031725</PCCT>
<COTM>15DEC031415</COTM>
<CTYP>I</CTYP>
</CKDT>
<PHAG>1273322</PHAG>
<DELY CODE=”YY” STRT=”15DEC031605” DURA=”0200”>Flight Delayed
</DELY>
<REMC>Catering Delay</REMC>
<BOTM>15DEC031645</BOTM>
<LACL>15DEC031755</LACL>
<ERUT RTNO=”1”>
<APCD>CTU</APCD>
<SCDT>15DEC031723</SCDT>
</ERUT>
<ERUT RTNO=”2”>
<APCD>ORD</APCD>
<SCAT>15DEC031125</SCAT>
<SCDT>15DEC031315</SCDT>
</ERUT>
<ERUT RTNO=”3”>
<APCD>MSP</APCD>
<SCAT>15DEC031325</SCAT>
</ERUT>
</FLTR>
<FLTR>
<FLID>121112513</FLID>
<ALCD>CA</ALCD>
<FLNO>CA002</FLNO>
<MVIN>A</MVIN>
<SODT>15DEC031620</SODT>
<FLTY>P</FLTY>
<FLIN>D</FLIN>
<ROUT RTNO=”1”>
<APCD>CAN</APCD>
<SCAT></SCAT>
<SCDT>15DEC031340</SCDT>
</ROUT>
<ACFT>767</ACFT>
<RENO>A23B27</RENO>
<TRML>1</TRML>
<MAXP>180</MAXP>
<CSOP>CZ</CSOP>
<CSFT>CZ101</CSFT>
<ACTT>15DEC031630</ACTT>
<STND>R211</STND>
<PHAG>221203</PHAG>
<CLDT CLNO=”1”>
<BELT>B01</BELT>
<BCLS>X</BCLS>
<PCOT>15DEC031730</PCOT>
<PCCT>15DEC031830</PCCT>
<FBAG>15DEC031645</FBAG>
<LBAG>15DEC031745</LBAG>
<BTYP>D</BTYP>
</CLDT>
<ERUT RTNO=”1”>
<APCD>CAN</APCD>
<SCDT>15DEC031340</SCDT>
</ERUT>
<ERUT RTNO=”2”>
<APCD>CTU</APCD>
<SCAT>15DEC031620</SCAT>
</ERUT>
</FLTR>
</SCHD>
</MSG>
```
<!-- 原 PDF 第 101 页 -->
<a id="sec-3-17"></a>
### 3.17 AODB daily schedule response to RMS event/ AODB 日计划应答 RMS 事件
<a id="sec-3-17-1"></a>
#### 3.17.1 Event Attributes/事件属性
```text
Message Code AODBRESPRMSRQFD
消息代码
Event Description This is sent by AODB in response to an RQFD event
事件描述 from RMS.
从 AODB 发送，响应 RMS 的 RQFD 事件。
Single Recipient Yes
接收者 是
Frequency Unscheduled and always sent as an automatic response
频率 to a daily schedule request from RMS.
非计划的，自动响应 RMS 日计划时刻表请求。
Data Range Controlled by RMS request
数据范围 由 RMS 请求控制
Data Count Multiple daily schedule records in single XML message.
数据数 Number will depend on daily schedule flights in CDIA
and also upon RMS request.
一条 XML 报文包括多条日计划时刻表记录。具体条数根
据成都机场每日航班数及 RMS 的请求。
Data Conversion None
数据转换 无
Sort Sequence Refer to daily schedule AODBSCHD
排列序列号 参考日计划时刻表 AODBSCHD
Acknowledgment None
确认 无
Priority Normal
优先级 正常
Expiry 480 minutes
过期 480 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments Refer to daily schedule AODBSCHD
注释 参考日计划时刻表AODBSCHD
```
<a id="sec-3-17-2"></a>
#### 3.17.2 Event Message Format/事件消息格式
```text
Refer format under AODBSCHD event. The format is the same as AODBSCHD event,
except the message subtype in the meta header section will be set to RESP.
参考AODBSCHD事件格式。格式与AODBSCHD事件相同，只有meta头部分的信息子类
型为RESP。
```
<a id="sec-3-17-3"></a>
#### 3.17.3 Event Message Sample/事件消息例子
Refer sample under AODBSCHD event except the STYP will be set to RESP.
参考AODBSCHD事件的例子，只有STYP为RESP。
<a id="sec-3-18"></a>
### 3.18 AODB adhoc flight event/ AODB adhoc 航班事件
<a id="sec-3-18-1"></a>
#### 3.18.1 Event Attributes/事件属性
```text
Message Code AODBADFT
消息代码
Event Description This event occurs when the operator creates an adhoc /
事件描述 unscheduled flight in AODB and AODB has to notify the
same to various other airport systems.
当操作员在 AODB 中建立一个 adhoc/非计划航班，并通
知机场中其他的各系统时，产生该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered by adhoc flight creation in
频率 AODB.
非计划的，在 AODB 建立 adhoc 航班时触发。
Reasons for adhoc flight creation include:
建立 adhoc 航班的原因有：
A new flight not in previously published daily schedule is
received from an external system like ATC.
从外部系统如 ATC 中收到一个航班计划中未计划的新航
班。
A new flight not in previously published daily schedule is
created manually in AODB.
在 AODB 中手工建立一个航班计划中未计划的新航班。
When part of a unique flight key field (airline code, flight
number, flight date, flight time, arrival/departure
indicator) changes, AODB will indicate the update by a
flight delete event AODBFDEL, followed by new flight
event AODBADFT. The unique AODB flight identifier in
the two events may/may not be the same. Subsystems
should be able to process this sequence.
当一个独立航班的一些键值字段（航空公司代码，航班
号，航班日期，航班时间，到达/离港标志）改变时，
AODB 会在发出航班删除事件 AODBFDEL 后触发新航班
事件 AODBADFT 来指名修改这些信息。在这两种事件
中，唯一的 AODB 航班标识可能不一样。子系统可以处
理该序列。
Data Range Adhoc events are sent out only if a flight is created with
数据范围 scheduled operational date within the current operational
window of „x‟ hours (typically next 48 hours).
Adhoc 事件仅当航班建立的计划操作日期在当前操作窗口
内的若干小时（通常是 48 小时内）中发出。
If current date is 14Mar06 and an Adhoc flight is created
for 18Mar06 in AODB, this will not result in any adhoc
flight event since only flights in the 48 hour daily
schedules window are sent. Such adhoc flight will
appear in the daily schedule of 17Mar06.
如果当前日期是 06 年 3 月 14 日，Adhoc 航班在 AODB
中建立的日期是 06 年 3 月 18 日，则不会产生任何的
adhoc 航班事件，因为只有在 48 小时计划内的航班才会
发送。该 adhoc 航班会在 06 年 3 月 17 日的航班计划中
出现。
Data Count Single daily flight record in single XML message.
数据数 一个 XML 报文中包括一个航班数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 480 minutes
过期 480 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments Adhoc flight XML message format is designed to be
注释 same as daily schedule message format. Refer to
comments under the daily schedule message format
AODBSCHD.
Adhoc航班的XML报文格式设计成与航班日计划报文格式
相同。参考航班日计划报文格式AODBSCHD。
```
<a id="sec-3-18-2"></a>
#### 3.18.2 Event Message Format/事件消息格式
```text
Refer format under AODBSCHD event. The format is the same as AODBSCHD event,
except the message subtype in the meta header section will be set to ADFT.
参考AODBSCHD事件格式。该事件格式与AODBSCHD事件格式相同，只是报文的信息
头部分的子类型为ADFT。
```
<a id="sec-3-18-3"></a>
#### 3.18.3 Event Message Sample/事件消息例子
Refer sample under AODBSCHD event except the STYP will be set to ADFT.
参考AODBSCHD事件例子。只是STYP置为ADFT。
<a id="sec-3-19"></a>
### 3.19 AODB flight aircraft type event/ AODB 航班机型事件
<a id="sec-3-19-1"></a>
#### 3.19.1 Event Attributes/事件属性
```text
Message Code AODBACFT
消息代码
Event Description This event occurs whenever a flight‟s aircraft type is
事件描述 updated in AODB.
当 AODB 中一个航班的机型修改时，发生该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered by flight aircraft update in
频率 AODB.
非计划的，AODB 中航班机型改变时触发。
Reasons for aircraft update include:
机型改变的原因有：
An aircraft update for a flight is received from an external
system like ATC.
从外部系统如 ATC 收到航班机型更新信息。
An aircraft update for a flight is made manually in AODB.
在 AODB 中手工修改一个航班的机型。
A flight‟s registration number is changed which indirectly
causes an aircraft type update.
航班注册号改变直接引起机型变化。
Data Range This is sent out only if the flight aircraft type is changed
数据范围 for a flight which is scheduled for operation within the
current operational window of „x‟ hours (typically next 48
hours).
机型数据修改事件仅当航班建立的计划操作日期在当前操
作窗口内的若干小时（通常是 48 小时内）中发出。
Data Count Single flight aircraft record in single XML message.
数据数 一条 XML 报文中包括一条航班机型数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments None
注释 无
```
<a id="sec-3-19-2"></a>
#### 3.19.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M FLOP
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(4) M ACFT
data section.
消息发送的子类型. Meta Data段的一部
分.
FLOP Identifies start of the operational data. - M This starts a section.
操作数据的开始标识 一个新段落的开始
FLID Unique AODB ID for identifying a flight Number(1-12) M
AODB中唯一的航班ID
FFID Friendly flight Id for easy identification. Char(20-32) M Formed by concatenating
航班ID别名，便于辨别 following fields of
AODBSCHD message in
order namely
ALCD, FLNO, MVIN,
SODT, FLIN
格式为AODBSCHD报文
中相关的字段顺序，
ALCD, FLNO, MVIN,
SODT, FLIN
ACFT Aircraft type used in this flight Char(3) M IATA aircraft type
航班使用的机型 IATA机型码
```
<a id="sec-3-19-3"></a>
#### 3.19.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>FLOP</TYPE>
<STYP>ACFT</STYP>
</META>
<FLOP>
<FLID>121112312</FLID>
<FFID>CA-CA101-A-12DEC031345-D</FFID>
<ACFT>747</ACFT>
</FLOP>
</MSG>
```
<a id="sec-3-20"></a>
### 3.20 AODB flight actual time event/ AODB 航班实际时间事件
<a id="sec-3-20-1"></a>
#### 3.20.1 Event Attributes/事件属性
```text
Message Code AODBACTT
消息代码
Event Description This event occurs whenever the flight‟s actual time is
事件描述 updated in AODB.
当 AODB 中一个航班的实际时间修改时，发生该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered by flight actual time update in
频率 AODB.
非计划的，AODB 中航班实际时间改变时触发。
Reasons for actual time update include:
实际时间改变的原因有：
An actual time update for a flight is received from an
external system like ATC.
从外部系统如 ATC 收到航班实际时间更新信息。
An actual time update for a flight is made manually in
AODB.
在 AODB 中手工修改一个航班的实际时间。
Data Range This is sent out only if the actual time is changed for a
数据范围 flight which is scheduled for operation within the current
operational window of „x‟ hours (typically next 48 hours).
实际时间数据修改事件仅当航班建立的计划操作日期在当
前操作窗口内的若干小时（通常是 48 小时内）中发出。
Data Count Single flight actual time record in single XML message.
数据数 一条 XML 报文中包括一条航班实际时间数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments None
注释 无
```
<a id="sec-3-20-2"></a>
#### 3.20.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M FLOP
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(4) M ACTT
data section.
消息发送的子类型. Meta Data段的一部
分.
FLOP Identifies start of the operational data. - M This starts a section.
操作数据的开始标识 一个新段落的开始
FLID Unique AODB ID for identifying a flight Number(1-12) M
AODB中唯一的航班ID
FFID Friendly flight Id for easy identification. Char(20-32) M Formed by concatenating
航班ID别名，便于辨别 following fields of
AODBSCHD message in
order namely
ALCD, FLNO, MVIN,
XML Tag Description Format Req Values
SODT, FLIN
格式为AODBSCHD报文
中相关的字段顺序，
ALCD, FLNO, MVIN,
SODT, FLIN
ACTT Actual time of flight. This will point to Char(11) P DDMONYYHHMM
ATA for arrivals and ATD for Local time 24 hr format.
departures
An empty TAG means
航班实际时间。ATA表示到达，ATD表 the existing actual time
示离港。 value is being deleted.
当地时间24小时格式
空表示实际时间清除
```
<a id="sec-3-20-3"></a>
#### 3.20.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>FLOP</TYPE>
<STYP>ACTT</STYP>
</META>
<FLOP>
<FLID>121112312</FLID>
<FFID>CA-CA101-A-12DEC031345-D</FFID>
<ACTT>15DEC031807</ACTT>
</FLOP>
</MSG>
```
<a id="sec-3-21"></a>
### 3.21 AODB flight boarding time event/ AODB 航班登机时间事件
<a id="sec-3-21-1"></a>
#### 3.21.1 Event Attributes/事件属性
```text
Message Code AODBBOTM
消息代码
Event Description This event occurs whenever a flight‟s boarding time is
事件描述 updated in AODB.
当 AODB 中一个航班的登机时间修改时，发生该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered by flight boarding time update in
频率 AODB.
非计划的，AODB 中航班登机时间改变时触发。
Reasons for flight boarding time update include:
登机时间改变的原因有：
A boarding time update for a flight is received from DCS.
从 DCS 收到航班登机时间更新信息。
A boarding time update is made manually in AODB.
在 AODB 中手工修改一个航班的登机时间。
Data Range This is sent out only if the flight boarding time is changed
数据范围 for a flight which is scheduled for operation within the
current operational window of „x‟ hours (typically next 48
hours).
登机时间数据修改事件仅当航班建立的计划操作日期在当
前操作窗口内的若干小时（通常是 48 小时内）中发出。
Data Count Single flight boarding time record in single XML
数据数 message.
一条 XML 报文中包括一条航班登机时间数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments Sent only for departure flights
注释 仅对离港航班
Processing Exceptions RMS will not perform any validation on whether boarding
处理例外 time is in future and set status to boarding once this
event is received. Boarding status will be reset if empty
time is received.
RMS不会执行校验登机时间是否在将来并收到这个事件
时将状态设为登机一次。如果收到空的时间会重设登机状
态。
```
<a id="sec-3-21-2"></a>
#### 3.21.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M FLOP
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(4) M BOTM
data section.
消息发送的子类型. Meta Data段的一部
分.
FLOP Identifies start of the operational data. - M This starts a section.
操作数据的开始标识 一个新段落的开始
FLID Unique AODB ID for identifying a flight Number(1-12) M
AODB中唯一的航班ID
FFID Friendly flight Id for easy identification. Char(20-32) M Formed by concatenating
航班ID别名，便于辨别 following fields of
AODBSCHD message in
order namely
ALCD, FLNO, MVIN,
SODT, FLIN
格式为AODBSCHD报文
中相关的字段顺序，
ALCD, FLNO, MVIN,
SODT, FLIN
BOTM Boarding open time for the departure Char(11) P DDMONYYHHMM
flight Local time 24 hr format.
离港航班登机开始时间 An empty TAG means
the existing boarding time
is being blanked out
当地时间24小时格式
空表示登机时间清除。
```
<a id="sec-3-21-3"></a>
#### 3.21.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>FLOP</TYPE>
<STYP>BOTM</STYP>
</META>
<FLOP>
<FLID>121112312</FLID>
<FFID>CA-CA101-A-12DEC031345-D</FFID>
<BOTM>15DEC031645</BOTM>
</FLOP>
</MSG>
```
<a id="sec-3-22"></a>
### 3.22 AODB flight chocks time event/ AODB 航班轮挡时间事件
<a id="sec-3-22-1"></a>
#### 3.22.1 Event Attributes/事件属性
```text
Message Code AODBCHOT
消息代码
Event Description This event occurs whenever the flight‟s chocks time data
事件描述 is updated in AODB.
当 AODB 中一个航班的轮挡时间修改时，发生该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered by flight chocks time data
频率 update in AODB.
非计划的，AODB 中航班轮挡时间改变时触发。
Reasons for chocks time data update include:
航班轮挡时间数据修改的原因有：
An on chocks time is received from VDGS/OMMS
indicating the flight has entered a parking stand.
从 VDGS/OMMS 中收到上轮挡时间，表示航班进入了停
机位。
An off chocks time is received from VDGS/OMMS
indicating the flight has left a parking stand.
从 VDGS/OMMS 中收到下轮挡时间，表示航班离开了停
机位。
Above information about chocks time data is entered
manually in AODB.
在 AODB 中手工输入以上的轮挡时间数据。
Data Range This is sent out only if the chocks time data is changed
数据范围 for a flight which is scheduled for operation within the
current operational window of „x‟ hours (typically next 48
hours).
轮挡时间数据事件仅当航班建立的计划操作日期在当前操
作窗口内的若干小时（通常是 48 小时内）中发出。
Data Count Single flight chocks time record in single XML message.
数据数 一个 XML 报文中包括一个航班轮挡时间数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments 1. The chocks time data and sequence number is
注释 based on the actual stand movement made by
aircraft and as received by VDGS and can be
different from the one planned using RMS.
轮挡时间数据和序列号是根据飞机在机位实际的移动
时间，从VDGS收到，与RMS中使用的计划数可以不
同。
2. See AODBPSDT for stand planning logic.
参考AODBPSDT的机位计划。
```
<a id="sec-3-22-2"></a>
#### 3.22.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M FLOP
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(4) M CHOT
data section.
消息发送的子类型. Meta Data段的一部
分.
FLOP Identifies start of the operational data. - M This starts a section.
操作数据的开始标识 一个新段落的开始
FLID Unique AODB ID for identifying a flight Number(1-12) M
AODB中唯一的航班ID
FFID Friendly flight Id for easy identification. Char(20-32) M Formed by concatenating
航班ID别名，便于辨别 following fields of
AODBSCHD message in
order namely
ALCD, FLNO, MVIN,
SODT, FLIN
格式为AODBSCHD报文
中相关的字段顺序，
ALCD, FLNO, MVIN,
XML Tag Description Format Req Values
SODT, FLIN
CHOT This identifies the start of chocks time Number(1) M This section contains
data section. This includes a information for one ON or
parameter CSNO Number(1) to OFF chocks. This is sent
indicate the stand sequence number once separately for each
against which this chocks time is being such stand move and
reported (Note this is not chocks includes data for stand to
sequence but stand sequence) stand moves as well as
轮挡时间数据部分的开始，包括参数 stand to hangar moves.
CSNO 号（1）表示报告的轮挡时间对 该部分包括一个上轮挡或
应的机位序列号（注意是机位序列号非 下轮挡信息。在每个机位
轮挡序列号） 移动数据中重复出现。机
位移动包括机位到机位的
和机位到机库的。
CHTM Chocks time. On chocks or off chocks Char(11) P DDMONYYHHMM
is determined by chocks indicator Local time 24 hr format
CHID below
当地时间24小时格式
轮挡时间。上下轮挡由下面的CHID表
An empty TAG means
示。
the existing chocks time
value is being deleted.
空表示已有的轮挡时间删
除。
CHID Chocks indicator Char(2-3) M OFF or ON
轮挡标识 下或上
CHST The chocks stand against which the Char(1-8) M Actual stand number
chocks time is reported 实际的机位号
报告的轮挡时间对应的轮挡机位
```
<a id="sec-3-22-3"></a>
#### 3.22.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>FLOP</TYPE>
<STYP>CHOT</STYP>
</META>
<FLOP>
<FLID>121112312</FLID>
<FFID>CA-CA101-A-12DEC031345-D</FFID>
<CHOT CSNO=”1”>
<CHTM>15DEC031350</CHTM>
<CHID>ON</CHID>
<CHST>S211</CHST>
</CHOT>
</FLOP>
</MSG>
```
<a id="sec-3-23"></a>
### 3.23 AODB flight type event/ AODB 航班类型事件
<a id="sec-3-23-1"></a>
#### 3.23.1 Event Attributes/事件属性
```text
Message Code AODBFLTY
消息代码
Event Description This event occurs whenever the flight type is updated in
事件描述 AODB.
当 AODB 中一个航班类型修改时，发生该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered by flight type update in AODB.
频率 非计划的，AODB 中航班类型改变时触发。
Reasons for flight type update include:
航班类型修改的原因有：
A flight type change for a flight is received from an
external system like ATC.
从外部系统如 ATC 中收到航班类型改变的信息。
A flight type change for a flight is made manually in
AODB.
在 AODB 中手工修改航班类型。
Data Range This is sent out only if the data related to flight type is
数据范围 changed for a flight which is scheduled for operation
within the current operational window of „x‟ hours
(typically next 48 hours).
航班类型修改事件仅当航班建立的计划操作日期在当前操
作窗口内的若干小时（通常是 48 小时内）中发出。
Data Count Single flight type record in single XML message.
数据数 一个 XML 报文中包括一个航班类型数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments None
注释 无
```
<a id="sec-3-23-2"></a>
#### 3.23.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M FLOP
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(4) M FLTY
data section.
消息发送的子类型. Meta Data段的一部
分.
FLOP Identifies start of the operational data. - M This starts a section.
操作数据的开始标识 一个新段落的开始
FLID Unique AODB ID for identifying a flight Number(1-12) M
AODB中唯一的航班ID
FFID Friendly flight Id for easy identification. Char(20-32) M Formed by concatenating
航班ID别名，便于辨别 following fields of
AODBSCHD message in
order namely
ALCD, FLNO, MVIN,
SODT, FLIN
格式为AODBSCHD报文
中相关的字段顺序，
ALCD, FLNO, MVIN,
SODT, FLIN
FLTY Flight type like passenger, cargo, Char(1) M Reference table to be
military, VIP etc decided by CDIA.
航班类型如客机、货机、军机、VIP等 AODBAODB will send all
flight type updates of all
types by default and the
subsystems are expected
to accept/ignore, based
on their requirements.
参考代码表由成都机场定
义。AODB默认发送所有
航班类型的改变，子系统
根据需要接受/忽略。
```
<a id="sec-3-23-3"></a>
#### 3.23.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>173243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>FLOP</TYPE>
<STYP>FLTY</STYP>
</META>
<FLOP>
<FLID>121112312</FLID>
<FFID>CA-CA101-A-12DEC031345-I</FFID>
<FLTY>C</FLTY>
</FLOP>
</MSG>
```
<a id="sec-3-24"></a>
### 3.24 AODB flight check in counter event/ AODB 航班值机柜台事件
<a id="sec-3-24-1"></a>
#### 3.24.1 Event Attributes/事件属性
```text
Message Code AODBCKDT
消息代码
Event Description This event occurs whenever a flight‟s check in counter
事件描述 related data is updated in AODB.
当 AODB 中一个航班的值机柜台相关数据修改时，发生
该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered by flight‟s check in counter data
频率 update in AODB.
非计划的，AODB 中航班值机柜台数据改变时触发。
Reasons for check in counter data update include:
值机柜台数据修改的原因有：
Flight‟s counter(s) is assigned/de-assigned and sent by
RMS.
航班的值机柜台在 RMS 中分配/重分配并发送后。
Flight counter open time is set and sent by DCS.
DCS 设置并发送值机柜台开放时间。
Flight counter close time is set and sent by DCS.
DCS 设置并发送值机柜台关闭时间。
Any of above counter data for a flight is updated
manually in AODB.
在 AODB 手动修改上述航班值机柜台数据。
Data Range This is sent out only if the check in counter data is
数据范围 changed for a flight which is scheduled for operation
within the current operational window of „x‟ hours
(typically next 48 hours).
Latest snapshot of all check in counter related data for a
flight is included.
航班值机柜台事件仅当航班建立的计划操作日期在当前操
作窗口内的若干小时（通常是 48 小时内）中发出。
包括一个航班中所有相关的值机柜台数据。
Data Count One or more flight check in counter records in single
数据数 XML message.
一个 XML 报文中包括一个或多个航班值机柜台数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments Sent only for departure flights
注释 仅对离港航班
Processing Exceptions RMS will reject this message if received from AODB.
处理例外 RMS如果从AODB收到这消息将拒绝
But if such data is specified in daily schedule message
RMS will process.
如果这些数据来自日计划，RMS将处理。
This message retained here only because RMSCKDT is
referring to this event for formats.
这个消息在这里只是便于RMSCKDT参考它的事件格式。
```
<a id="sec-3-24-2"></a>
#### 3.24.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M FLOP
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(4) M CKDT
data section.
消息发送的子类型. Meta Data段的一部
分.
FLOP Identifies start of the operational data. - M This starts a section.
操作数据的开始标识 一个新段落的开始
FLID Unique AODB ID for identifying a flight Number(1-12) M
AODB中唯一的航班ID
FFID Friendly flight Id for easy identification. Char(20-32) M Formed by concatenating
航班ID别名，便于辨别 following fields of
AODBSCHD message in
order namely
ALCD, FLNO, MVIN,
SODT, FLIN
格式为AODBSCHD报文
中相关的字段顺序，
ALCD, FLNO, MVIN,
SODT, FLIN
CKDT This indicates the start of check in Number(1-2) P This starts a new section
counter related data for a flight record. and includes check in
This includes a parameter CKNO to counter specific
identify the check in counter record information as below. An
number for a flight with multiple check empty TAG <CKDT
in counters. One record will have data CKNO=“0”></CKDT> will
for one check in counter assignment be sent for a flight with
and will repeat for each counter previous counter
assignment. allocations to signify
航班值机柜台数据的开始标志。包括一 there are no counter
个参数CKNO表示多值机柜台航班的值 allocations now.
机柜台号。一条记录是一个值机柜台的 一个新段落的开始，包括
数据，在每个分配的柜台中重复出现。 值机柜台的信息。空值
<CKDT
CKNO=“0”></CKDT>表
示航班曾经分配了值机柜
台而现在未分配。
CHKC Check in counter number assigned to Char(1-8) M Check in counter
this departure flight reference table to be
离港航班分配的值机柜台号 decided by CDIA.
值机柜台数据表由成都机
场定义
CCLS Check in counter class Char(1-3) M Following class codes will
值机柜台等级 be supported:
支持如下等级代码
XML Tag Description Format Req Values
F = First class/头等
C = Business class/商务
Y = Economy class/经济
X = No specific class/全
部
If more than one class
can be opened for
checkin on a single
counter, CKDT will be
repeated for each class.
如果一个值机柜台可以为
多个等级的旅客开放，那
么CKDT会为每个等级重
复一次。
PCOT Planned time for check in for flight Char(11) M DDMONYYHHMM
航班计划的值机开始时间 Local time 24 hr format
当地时间24小时格式
PCCT Planned time for check close for flight Char(11) M DDMONYYHHMM
航班计划的值机关闭时间 Local time 24 hr format
当地时间24小时格式
COTM Time when check in was open for flight Char(11) O DDMONYYHHMM
航班开始值机时间 Local time 24 hr format
当地时间24小时格式
CCTM Time when check in was closed for Char(11) O DDMONYYHHMM
flight Local time 24 hr format
航班值机关闭时间 当地时间24小时格式
CTYP Domestic or international indicator of Char(1) M D – Domestic/国内
Check In counter resource I – International/国际
值机柜台资源的国内国际标识
```
<a id="sec-3-24-3"></a>
#### 3.24.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>FLOP</TYPE>
<STYP>CKDT</STYP>
</META>
<FLOP>
<FLID>121112312</FLID>
<FFID>CA-CA101-D-12DEC031345-D</FFID>
<CKDT CKNO=”1”>
<CHKC>01</CHKC>
<CCLS>X</CCLS>
<PCOT>15DEC031515</PCOT>
<PCCT>15DEC031725</PCCT>
<COTM>15DEC031525</COTM>
<CTYP>D</CTYP>
</CKDT>
<CKDT CKNO=”2”>
<CHKC>17</CHKC>
<CCLS>F</CCLS>
<PCOT>15DEC031515</PCOT>
<PCCT>15DEC031725</PCCT>
<COTM>15DEC031415</COTM>
<CTYP>D</CTYP>
</CKDT>
</FLOP>
</MSG>
```
<a id="sec-3-25"></a>
### 3.25 AODB flight carousel event/ AODB 航班行李转盘事件
<a id="sec-3-25-1"></a>
#### 3.25.1 Event Attributes/事件属性
```text
Message Code AODBCLDT
消息代码
Event Description This event occurs whenever a flight‟s carousel related
事件描述 data is updated in AODB.
当 AODB 中一个航班的行李转盘修改时，发生该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered by flight‟s carousel data update
频率 in AODB.
非计划的，AODB 中航班行李转盘数据改变时触发。
Reasons for carousel data update include:
行李转盘数据修改的原因有：
Flight‟s carousel(s) is assigned/de-assigned and sent by
RMS.
航班的行李转盘在 RMS 中分配/重分配并发送后。
Flight carousel first bag is set and sent by FIDS/OMMS.
FIDS/OMMS 设置发送航班行李转盘的第一件行李。
Flight carousel last bag is set and sent by FIDS/OMMS.
FIDS/OMMS 设置发送航班行李转盘的最后一件行李。
Any of above carousel data for a flight is updated
manually in AODB.
在 AODB 手动修改上述航班行李转盘数据。
Data Range This is sent out only if the carousel data is changed for a
数据范围 flight which is scheduled for operation within the current
operational window of „x‟ hours (typically next 48 hours).
Latest snapshot of all carousel related data for a flight is
included.
航班行李转盘事件仅当航班建立的计划操作日期在当前操
作窗口内的若干小时（通常是 48 小时内）中发出。
包括一个航班中所有相关的行李转盘数据。
Data Count One or more flight carousel records in single XML
数据数 message.
一个 XML 报文中包括一个或多个航班行李转盘数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments Sent only for arrival flights
注释 仅对到达航班
Processing Exceptions RMS will reject this message if received from AODB.
处理例外 RMS如果从AODB收到这消息将拒绝
But if such data is specified in daily schedule message
RMS will process.
如果这些数据来自日计划，RMS将处理。
This message retained here only because RMSCLDT is
referring to this event for formats.
这个消息在这里只是便于RMSCLDT参考它的事件格式。
```
<a id="sec-3-25-2"></a>
#### 3.25.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M FLOP
XML Tag Description Format Req Values
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(4) M CLDT
data section.
消息发送的子类型. Meta Data段的一部
分.
FLOP Identifies start of the operational data. - M This starts a section.
操作数据的开始标识 一个新段落的开始
FLID Unique AODB ID for identifying a flight Number(1-12) M
AODB中唯一的航班ID
FFID Friendly flight Id for easy identification. Char(20-32) M Formed by concatenating
航班ID别名，便于辨别 following fields of
AODBSCHD message in
order namely
ALCD, FLNO, MVIN,
SODT, FLIN
格式为AODBSCHD报文
中相关的字段顺序，
ALCD, FLNO, MVIN,
SODT, FLIN
CLDT This indicates the start of carousel Number(1) P This starts a new section
related data for a flight record. This and includes carousel
includes a parameter CLNO to identify specific information as
the carousel record number for a flight below. An empty TAG
with multiple carousels. <CLDT CLNO=“0”>
航班行李转盘数据的开始标志。包括一 </CLDT> will be sent for
个参数CLNO表示多行李转盘航班的行 a flight with previous
carousel allocations to
李转盘号
signify there are no
carousel allocations now.
一个新段落的开始，包括
行李转盘的信息。空值
<CLDT CLNO=“0”>
</CLDT>表示航班曾经分
配了行李转盘而现在未分
配。
BELT Baggage belt number for arrival flights Char(1-8) M Carousel codes
到达航班的行李传送带号 reference table to be
decided by CDIA.
行李转盘代码表由成都机
场定义。
BCLS Baggage carousel class Char(1) M Following class codes will
行李转盘等级 be supported:
支持如下等级代码
F = First class/头等
C = Business class/商务
Y = Economy class/经济
XML Tag Description Format Req Values
X = No specific class/全
部
If more than one class
can be used for carousel
allocationon a single belt,
CLDT will be repeated for
each class.
如果一个行李转盘可被用
于多个等级的行李转盘分
配 ， 那 么 CLDT 将 为 每 个
等级重复一次。
PCOT Planned time for carousel start usage Char(11) M DDMONYYHHMM
for flight Local time 24 hr format
航班行李转盘计划开始使用时间 当地时间24小时格式
PCCT Planned time for carousel end usage Char(11) M DDMONYYHHMM
for flight Local time 24 hr format
航班行李转盘计划结束使用时间 当地时间24小时格式
FBAG Date and time when the first bag was Char(11) O DDMONYYHHMM
placed on this belt for an arrival flight Local time 24 hr format
到达航班第一件行李放置传送带的日期 当地时间24小时格式
时间
LBAG Date and time when the last bag Char(11) O DDMONYYHHMM
leaves this belt for an arrival flight Local time 24 hr format
到达航班最后一件行李离开传送带的日 当地时间24小时格式
期时间
BTYP Domestic or international indicator of Char(1) M D – Domestic/国内
belt resource I – International/国际
传送带资源的国内国际标识
```
<a id="sec-3-25-3"></a>
#### 3.25.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>FLOP</TYPE>
<STYP>CLDT</STYP>
</META>
<FLOP>
<FLID>121112312</FLID>
<FFID>CA-CA101-A-12DEC031345-D</FFID>
<CLDT CLNO=”1”>
<BELT>B01</BELT>
<BCLS>X</BCLS>
<PCOT>12DEC031330</PCOT>
<PCCT>12DEC031430</PCCT>
<BTYP>D</BTYP>
</CLDT>
</FLOP>
</MSG>
```
<a id="sec-3-26"></a>
### 3.26 AODB flight chute event/ AODB 航班行李传送带事件
<a id="sec-3-26-1"></a>
#### 3.26.1 Event Attributes/事件属性
```text
Message Code AODBCHDT
消息代码
Event Description This event occurs whenever a flight‟s chute related data
事件描述 is updated in AODB.
当 AODB 中一个航班的行李传送带修改时，发生该事
件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered by flight‟s chute data update in
频率 AODB.
非计划的，AODB 中航班行李传送带改变时触发。
Reasons for chute data update include:
行李传送带改变的原因有：
Flight‟s chute(s) is assigned/de-assigned and sent by
BHS.
从 BHS 收到航班行李传送带分配/重分配信息。
Flight chute start usage time is set and sent by BHS.
BHS 设置发送航班行李传送带开始时间。
Flight chute end usage time is set and sent by BHS.
BHS 设置发送航班行李传送带结束时间。
Any of above chute data for a flight is updated manually
in AODB.
在 AODB 中手工修改一个航班上述的行李传送带数据。
Data Range This is sent out only if the chute data is changed for a
数据范围 flight which is scheduled for operation within the current
operational window of „x‟ hours (typically next 48 hours).
Latest snapshot of all chute related data for a flight is
included.
行李传送带数据修改事件仅当航班建立的计划操作日期在
当前操作窗口内的若干小时（通常是 48 小时内）中发
出。
包括一个航班相关的行李传送带所有的数据。
Data Count One or more flight chute records in single XML
数据数 message.
一条 XML 报文中包括一条或多条航班行李传送带数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京时间
Comments Sent only for departure flights.
注释 Sent only on “normal sortation” of flights done by RMS.
"Early", "rush" and "late" chutes used for the flight is not
reported since these are normally the same for all/many
flights.
仅对离港航班。仅在RMS中航班为“正常分类”时发
送。“提早”、“紧急”，“延后”的航班行李传送带不
会报告，因为对所有/很多航班而言与正常的相同。
Processing Exceptions RMS will reject this message if received from AODB.
处理例外 RMS如果从AODB收到这消息将拒绝
But if such data is specified in daily schedule message
RMS will process.
如果这些数据来自日计划，RMS将处理。
This message retained here only because RMSCHDT is
referring to this event for formats.
这个消息在这里只是便于RMSCHDT参考它的事件格式。
```
<a id="sec-3-26-2"></a>
#### 3.26.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M FLOP
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(4) M CHDT
data section.
XML Tag Description Format Req Values
消息发送的子类型. Meta Data段的一部
分.
FLOP Identifies start of the operational data. - M This starts a section.
操作数据的开始标识 一个新段落的开始
FLID Unique AODB ID for identifying a flight Number(1-12) M
AODB中唯一的航班ID
FFID Friendly flight Id for easy identification. Char(20-32) M Formed by concatenating
航班ID别名，便于辨别 following fields of
AODBSCHD message in
order namely
ALCD, FLNO, MVIN,
SODT, FLIN
格式为AODBSCHD报文
中相关的字段顺序，
ALCD, FLNO, MVIN,
SODT, FLIN
CHDT Has a parameter CHNO to identify the Number(1) P This starts a chute
chute number associated with flight section and includes
which has multiple chute allocations. chute specific information
This data repeats for each chute of a as below. An empty TAG
flight. <CHDT
分配了多行李传送带的航班带有参数 CHNO=“0”></CHDT> will
CHNO表示传送带号。航班的每个传送 be sent for a flight with
previous chute
带中重复出现。
allocations to signify
there are no chute
allocations now.
一个行李传送带段落的开
始包括传送带的详情。空
标签<CHDT
CHNO=“0”></CHDT>表
示航班已分配但现在未分
配。
CHUT This is the baggage chute allocated for Char(1-8) M
a departure flight.
离港航班分配的行李传送带
CCLS Chute class Char(1) M Following class codes will
行李传送带等级 be supported:
支持如下等级代码
F = First class/头等
C = Business class/商务
Y = Economy class/经济
X = No specific class/全
部
If more than one class
can be used for chute
allocationon a single
chute, CHDT will be
XML Tag Description Format Req Values
repeated for each class.
如果一个行李传送带可被
用于多个等级的行李传送
带分配，那么CHDT将为
每个等级重复一次。
PCBT Planned time for chute start usage for Char(11) M DDMONYYHHMM
flight Local time 24 hr format
航班行李转盘计划开始使用时间 当地时间24小时格式
PCET Planned time for chute end usage for Char(11) M DDMONYYHHMM
flight Local time 24 hr format
航班行李转盘计划结束使用时间 当地时间24小时格式
CBTM Actual Time when the flight started Char(11) O DDMONYYHHMM
using the chute Local time 24 hr format
航班实际开始使用传送带时间 当地时间24小时格式
CETM Actual Time when the flight stopped Char(11) O DDMONYYHHMM
using the chute Local time 24 hr format
航班实际结束使用传送带时间 当地时间24小时格式
CTYP Domestic or International indicator of Char(1) M D – Domestic/国内
chute resource I – International/国际
传送带资源的国内国际标志
```
<a id="sec-3-26-3"></a>
#### 3.26.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20031215090311</DTTM>
<TYPE>FLOP</TYPE>
<STYP>CHDT</STYP>
</META>
<FLOP>
<FLID>121112312</FLID>
<FFID>CA-CA101-D-15DEC031925-D</FFID>
<CHDT CHNO=”1”>
<CHUT>CH0021</CHUT>
<CCLS>X</CCLS>
<PCBT>15DEC031530</PCBT>
<PCET>15DEC031830</PCET>
<CBTM>15DEC031520</CBTM>
<CETM>15DEC031900</CETM>
<CTYP>D</CTYP>
</CHDT>
<CHDT CHNO=”2”>
<CHUT>CH0025</CHUT>
<CCLS>X</CCLS>
<PCBT>15DEC031530</PCBT>
<PCET>15DEC031830</PCET>
<CBTM>15DEC031525</CBTM>
<CETM>15DEC031900</CETM>
<CTYP>D</CTYP>
</CHDT>
</FLOP>
</MSG>
```
<a id="sec-3-27"></a>
### 3.27 AODB flight cancel event/ AODB 航班取消事件
<a id="sec-3-27-1"></a>
#### 3.27.1 Event Attributes/事件属性
```text
Message Code AODBCNCL
消息代码
Event Description This event occurs whenever a flight is cancelled in
事件描述 AODB.
当 AODB 中一个航班取消时，发生该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered by flight cancel update in AODB.
频率 非计划的，AODB 中航班取消时触发。
Reasons for cancel update include:
取消的原因有：
Flight cancel received from an external system like ATC.
从外部系统如 ATC 收到航班取消信息。
Flight cancel updated manually in AODB.
在 AODB 中手工取消一个航班。
Data Range This is sent out only if the flight cancellation is changed
数据范围 for a flight which is scheduled for operation within the
current operational window of „x‟ hours (typically next 48
hours).
航班取消事件仅当航班建立的计划操作日期在当前操作窗
口内的若干小时（通常是 48 小时内）中发出。
Data Count Single flight cancellation record in single XML message.
数据数 一条 XML 报文中包括一条航班取消记录。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments 1. This only signifies cancel of the flight but the
注释 flight record itself is still present with “Cancelled”
status in AODB.
仅表示航班取消，航班记录在AODB中依然存在，带
有“取消”标志。
2. If the cancellation update is reversed in AODB,
AODB sends the following event.
如果在AODB中对取消进行撤销，AODB将发送下面
的事件
a. One event to notify the cancellation
update has been UNDONE. This is
using empty cancel TAG and event
code AODBCNCL.
一个事件表示取消修改撤销。使用一个
空取消标签和AODBCNCL事件代码。
```
<a id="sec-3-27-2"></a>
#### 3.27.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M FLOP
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(4) M CNCL
data section.
消息发送的子类型. Meta Data段的一部
分.
FLOP Identifies start of the operational data. - M This starts a section.
操作数据的开始标识 一个新段落的开始
FLID Unique AODB ID for identifying a flight Number(1-12) M
AODB中唯一的航班ID
FFID Friendly flight Id for easy identification. Char(20-32) M Formed by concatenating
航班ID别名，便于辨别 following fields of
AODBSCHD message in
XML Tag Description Format Req Values
order namely
ALCD, FLNO, MVIN,
SODT, FLIN
格式为AODBSCHD报文
中相关的字段顺序，
ALCD, FLNO, MVIN,
SODT, FLIN
CNCL Cancellation date time. Char(11) P DDMONYYHHMM
取消的日期时间 Local time 24 hr format.
An empty TAG means
undo cancellation of a
previously cancelled
flight.
当地时间24小时格式
空表示上一个取消撤销。
```
<a id="sec-3-27-3"></a>
#### 3.27.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>FLOP</TYPE>
<STYP>CNCL</STYP>
</META>
<FLOP>
<FLID>121112312</FLID>
<FFID>CA-CA101-A-12DEC031345-I</FFID>
<CNCL>15DEC031722</CNCL>
</FLOP>
</MSG>
```
<a id="sec-3-28"></a>
### 3.28 AODB flight estimated time event/ AODB 航班预计时间事件
<a id="sec-3-28-1"></a>
#### 3.28.1 Event Attributes/事件属性
```text
Message Code AODBESTT
消息代码
Event Description This event occurs whenever the flight‟s estimated time is
事件描述 updated in AODB.
当 AODB 中一个航班的预计时间修改时，发生该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered by flight‟s estimated time update
频率 in AODB.
非计划的，AODB 中航班预计时间改变时触发。
Reasons for estimated time update include:
预计时间改变的原因有：
An estimated time update for a flight is received from an
external system like ATC.
从外部系统如 ATC 收到航班预计时间更新信息。
An estimated time update for a flight is made manually in
AODB.
在 AODB 中手工修改一个航班的预计时间。
Data Range This is sent out only if the flight estimated time is
数据范围 changed for a flight which is scheduled for operation
within the current operational window of „x‟ hours
(typically next 48 hours).
预计时间数据修改事件仅当航班建立的计划操作日期在当
前操作窗口内的若干小时（通常是 48 小时内）中发出。
Data Count Single flight estimated time record in single XML
数据数 message.
一条 XML 报文中包括一条航班预计时间数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments None
注释 无
```
<a id="sec-3-28-2"></a>
#### 3.28.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M FLOP
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(4) M ESTT
data section.
消息发送的子类型. Meta Data段的一部
分.
FLOP Identifies start of the operational data. - M This starts a section.
操作数据的开始标识 一个新段落的开始
FLID Unique AODB ID for identifying a flight Number(1-12) M
AODB中唯一的航班ID
FFID Friendly flight Id for easy identification. Char(20-32) M Formed by concatenating
航班ID别名，便于辨别 following fields of
AODBSCHD message in
order namely
ALCD, FLNO, MVIN,
SODT, FLIN
格式为AODBSCHD报文
中相关的字段顺序，
ALCD, FLNO, MVIN,
SODT, FLIN
ESTT Estimated time of flight. This will point Char(11) P DDMONYYHHMM
to ETA for arrivals and ETD for Local time 24 hr format.
departures
An empty TAG means
航班预计时间。ETA表示到达，ETD表 the existing estimated
示离港。 time value is being
deleted.
当地时间24小时格式。
空表示预计时间删除。
```
<a id="sec-3-28-3"></a>
#### 3.28.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>FLOP</TYPE>
<STYP>ESTT</STYP>
</META>
<FLOP>
<FLID>121112312</FLID>
<FFID>CA-CA101-A-12DEC031345-D</FFID>
<ESTT>15DEC031807</ESTT>
</FLOP>
</MSG>
```
<a id="sec-3-29"></a>
### 3.29 AODB flight delete event/ AODB 航班删除事件
<a id="sec-3-29-1"></a>
#### 3.29.1 Event Attributes/事件属性
```text
Message Code AODBFDEL
消息代码
Event Description This event occurs whenever a flight is deleted physically
事件描述 in AODB.
当 AODB 中一个航班物理删除时，发生该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered by flight delete in AODB.
频率 非计划的，AODB 中航班删除时触发。
Reasons for delete include:
删除原因有：
Flight delete received from an external system like ATC.
从外部系统如 ATC 收到航班删除信息。
Flight deleted manually in AODB. This typically happens
if the operator created an incorrect flight record by
mistake and deletes it.
在 AODB 中手工删除航班。通常是当操作员建立航班错
误时删除。
When part of a unique flight key field (airline code, flight
number, flight date, flight time, arrival/departure
indicator) changes, AODB will indicate the update by a
flight delete event AODBFDEL, followed by new flight
event AODBADFT. The unique flight identifier in the two
events may/may not be the same. Subsystems should
be able to process this sequence.
当一个航班的唯一关键字段（航空公司代码，航班号，航
班日期，航班时间，到达/离港标识）修改时，AODB 会
在 新 航 班 事 件 AODBADFT 后 ， 发 出 航 班 删 除 事 件
AODBFDEL 指示。在两个事件中的唯一航班 ID 可能不一
样。子系统可以处理该顺序。
Data Range This is sent out only if flight deleted is scheduled for
数据范围 operation within the current operational window of „x‟
hours (typically next 48 hours).
航班删除事件仅当航班建立的计划操作日期在当前操作窗
口内的若干小时（通常是 48 小时内）中发出。
Data Count Single flight delete record in single XML message.
数据数 一条 XML 报文中包括一条航班删除记录。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments 1. The flight record is removed forever from AODB.
注释 航班从AODB中永久删除。
```
<a id="sec-3-29-2"></a>
#### 3.29.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M FLOP
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(4) M FDEL
data section.
消息发送的子类型. Meta Data段的一部
分.
FLOP Identifies start of the operational data. - M This starts a section.
操作数据的开始标识 一个新段落的开始
FLID Unique AODB ID for identifying a flight Number(1-12) M
AODB中唯一的航班ID
FFID Friendly flight Id for easy identification. Char(20-32) M Formed by concatenating
航班ID别名，便于辨别 following fields of
AODBSCHD message in
order namely
ALCD, FLNO, MVIN,
SODT, FLIN
格式为AODBSCHD报文
中相关的字段顺序，
ALCD, FLNO, MVIN,
SODT, FLIN
XML Tag Description Format Req Values
FDEL XML Tag indicating flight is deleted - P Always an empty TAG
表示航班删除 with no data and no
parameters
永远是个空值，没有数据
没有参数。
```
<a id="sec-3-29-3"></a>
#### 3.29.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>FLOP</TYPE>
<STYP>FDEL</STYP>
</META>
<FLOP>
<FLID>121112312</FLID>
<FFID>CA-CA101-A-12DEC031345-D</FFID>
<FDEL></FDEL>
</FLOP>
</MSG>
```
<a id="sec-3-30"></a>
### 3.30 AODB flight diverted event/ AODB 航班转场事件
<a id="sec-3-30-1"></a>
#### 3.30.1 Event Attributes/事件属性
```text
Message Code AODBFDIV
消息代码
Event Description This event occurs whenever the flight‟s diverted indicator
事件描述 is updated in AODB.
当 AODB 中一个航班的转场标志修改时，发生该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered by flight‟s diverted indicator
频率 update in AODB.
非计划的，AODB 中航班转场标志改变时触发。
Reasons for flight‟s diverted indicator update include:
转场标志改变的原因有：
Whenever an arrival flight bound for the Chengdu airport
is diverted to a new destination.
到达成都机场的航班转场到新目的地。
If a new arrival (diverted from some other city) comes to
Chengdu it will be treated as an Adhoc flight and AODB
will send an AODBADFT in that case.
如果一个新到达（从其他城市转场来）成都的航班被当做
一个 Adhoc 航班，AODB 将发送 AODBADFT 事件。
Data Range This is sent out only if the flight diverted indicator is
数据范围 changed for a flight which is scheduled for operation
within the current operational window of „x‟ hours
(typically next 48 hours).
转场标志修改事件仅当航班建立的计划操作日期在当前操
作窗口内的若干小时（通常是 48 小时内）中发出。
Data Count Single flight diverted indicator record in single XML
数据数 message.
一个 XML 报文中包括一个航班转场标志数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments None
注释 无
Processing Exceptions Divert information will be shown in “Server Warnings” of
处理例外 RMS for manual stand allocation correction.
在RMS的”server warnings”中会显示备降信息，以便手动
改正停机位分配。
```
<a id="sec-3-30-2"></a>
#### 3.30.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M FLOP
data section.
消息发送类型。Meta Data段的一部
XML Tag Description Format Req Values
分。
STYP Subtype of message sent. Part of meta Char(4) M FDIV
data section.
消息发送的子类型. Meta Data段的一部
分.
FLOP Identifies start of the operational data. - M This starts a section.
操作数据的开始标识 一个新段落的开始
FLID Unique AODB ID for identifying a flight Number(1-12) M
AODB中唯一的航班ID
FFID Friendly flight Id for easy identification. Char(20-32) M Formed by concatenating
航班ID别名，便于辨别 following fields of
AODBSCHD message in
order namely
ALCD, FLNO, MVIN,
SODT, FLIN
格式为AODBSCHD报文
中相关的字段顺序，
ALCD, FLNO, MVIN,
SODT, FLIN
FDIV Contains a descriptive reason as to Char(1-30) P Free text diversion
why the flight has been diverted. Has reason.
two parameters called DDES and 自由文本格式
DDIR. DDES is to indicate the divert
Parameter DDES =
related airport. DDIR is to indicate the
Char(3)
divert direction (from or to the airport
specified in DDES). IATA airport code of
airport diverted to or
航班转场的原因描述。带有两个参数
airport diverted from.
DDES和DDIR。DDES表示航班转场相
关的机场。DDIR表示转场方向（从或 转场到的机场或从这个机
到DDES指定的机场）。 场转场到成都，使用IATA
机场代码
Parameter DDIR =
Char(2-4)
Divert direction. Valid
values are TO and
FROM
备降的方向，合法的值为
“TO”和“FROM”。
An empty parameter
DDES=”” means the
existing flight diverted
indicator value is being
unset.
空参数DDES=””表示已有
的航班转场标志清除
```
<a id="sec-3-30-3"></a>
#### 3.30.3 Event Message Sample/事件消息例子
<!-- 原 PDF 第 138 页 -->
The following flight deverted from CTU to HKG.
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>FLOP</TYPE>
<STYP>FDIV</STYP>
</META>
<FLOP>
<FLID>121112312</FLID>
<FFID>CA-CA101-A-12DEC031345-D</FFID>
<FDIV DDES=”HKG” DDIR=”TO”>INCLEMENT WEATHER</FDIV>
</FLOP>
</MSG>
```
The following flight deverted from SHA to CTU.
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>FLOP</TYPE>
<STYP>FDIV</STYP>
</META>
<FLOP>
<FLID>121112313</FLID>
<FFID>CA-CA102-A-12DEC031345-D</FFID>
<FDIV DDES=”SHA” DDIR=”FROM”>INCLEMENT WEATHER</FDIV>
</FLOP>
</MSG>
```
<a id="sec-3-31"></a>
### 3.31 AODB flight finals time event/ AODB 航班最终时间事件
<a id="sec-3-31-1"></a>
#### 3.31.1 Event Attributes/事件属性
```text
Message Code AODBFINT
消息代码
Event Description This event occurs whenever the flight‟s finals time (H10)
事件描述 is updated in AODB.
当 AODB 中一个航班的最终时间（H10）修改时，发生该
事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered by flight finals time update in
频率 AODB.
非计划的，AODB 中航班最终时间改变时触发。
Reasons for finals time update include:
航班最终时间修改的原因有：
A finals time update for a flight is received from an
external system like ATC.
从外部系统如 ATC 中收到航班最终时间更新信息。
A finals time update for a flight is made manually in
AODB.
在 AODB 中手工修改航班最终时间。
Data Range This is sent out only if the finals time is changed for a
数据范围 flight which is scheduled for operation within the current
operational window of „x‟ hours (typically next 48 hours).
航班最终时间修改事件仅当航班建立的计划操作日期在当
前操作窗口内的若干小时（通常是 48 小时内）中发出。
Data Count Single flight finals time record in single XML message.
数据数 一个 XML 报文中包括一个航班最终时间数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments Sent only for arrival flights.
注释 仅对到达航班
```
<a id="sec-3-31-2"></a>
#### 3.31.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M FLOP
XML Tag Description Format Req Values
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(4) M FINT
data section.
消息发送的子类型. Meta Data段的一部
分.
FLOP Identifies start of the operational data. - M This starts a section.
操作数据的开始标识 一个新段落的开始
FLID Unique AODB ID for identifying a flight Number(1-12) M
AODB中唯一的航班ID
FFID Friendly flight Id for easy identification. Char(20-32) M Formed by concatenating
航班ID别名，便于辨别 following fields of
AODBSCHD message in
order namely
ALCD, FLNO, MVIN,
SODT, FLIN
格式为AODBSCHD报文
中相关的字段顺序，
ALCD, FLNO, MVIN,
SODT, FLIN
FINT Finals Time. This is set when an arrival Char(11) P DDMONYYHHMM
flight is approaching and confirms Local time 24 hr format
landing, say 10 minutes prior to arrival.
An empty TAG means
Typically used to confirm resources
the existing finals time
committed for the flight in the airport.
value is being deleted.
最终时间。在到达航班快到并确认着陆
当地时间24小时格式。空
时设置，比如说到达前10分钟。通常用
表示已有的最终时间删除
于航班在机场资源提交的确认。
```
<a id="sec-3-31-3"></a>
#### 3.31.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>FLOP</TYPE>
<STYP>FINT</STYP>
</META>
<FLOP>
<FLID>121112312</FLID>
<FFID>CA-CA101-A-15JAN041345-D</FFID>
<FINT>15FEB041330</FINT>
</FLOP>
</MSG>
```
<a id="sec-3-32"></a>
### 3.32 AODB flight indicator event/ AODB 航班标识事件
<a id="sec-3-32-1"></a>
#### 3.32.1 Event Attributes/事件属性
```text
Message Code AODBFLIN
消息代码
Event Description This event occurs whenever the flight indicator is
事件描述 updated in AODB.
当 AODB 中一个航班的标识修改时，发生该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered by flight indicator update in
频率 AODB.
非计划的，AODB 中航班标识改变时触发。
Reasons for flight indicator update include:
航班标识改变的原因：
A flight indicator change for a flight is received from an
external system like ATC.
从外部系统如 ATC 收到一个航班标识修改的信息。
A flight indicator changes for a flight because of a
routing update.
航班航线修改使得航班标识变化。
A flight indicator change for a flight is made manually in
AODB without changing routing.
航班航线未改变，在 AODB 中手工修改航班标识。
Data Range This is sent out only if the data related to flight indicator
数据范围 is changed for a flight which is scheduled for operation
within the current operational window of „x‟ hours
(typically next 48 hours).
航班标识修改事件仅当航班建立的计划操作日期在当前操
作窗口内的若干小时（通常是 48 小时内）中发出。
Data Count Single flight indicator record in single XML message.
数据数 一个 XML 报文中包括一个航班标识数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京时间
Comments 1. Whenever there is a routing change it may also
注释 trigger flight indicator change event, based on
the new routing. For e.g. if a flight operating in a
domestic route is changed to an international
route, the flight indicator will change.
当航班航线修改时可能触发航班标识修改事件。如，
一个航班由国内航线该为国际航线，航班标识会发生
改变。
2. The AODBFLIN in such cases will be sent prior
to sending the AODBROUT event.
在这种情况下AODBFLIN事件比AODBROUT事件先
发送。
```
<a id="sec-3-32-2"></a>
#### 3.32.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M FLOP
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(4) M FLIN
data section.
消息发送的子类型. Meta Data段的一部
分.
FLOP Identifies start of the operational data. - M This starts a section.
操作数据的开始标识 一个新段落的开始
FLID Unique AODB ID for identifying a flight Number(1-12) M
AODB中唯一的航班ID
FFID Friendly flight Id for easy identification. Char(20-32) M Formed by concatenating
航班ID别名，便于辨别 following fields of
AODBSCHD message in
order namely
ALCD, FLNO, MVIN,
SODT, FLIN
格式为AODBSCHD报文
中相关的字段顺序，
ALCD, FLNO, MVIN,
SODT, FLIN
XML Tag Description Format Req Values
FLIN Flight Indicator Char(1) M D – Domestic/国内
航班标识 I – International/国际
M – Mixed/混合
R – Regional/地区
```
<a id="sec-3-32-3"></a>
#### 3.32.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>173243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>FLOP</TYPE>
<STYP>FLIN</STYP>
</META>
<FLOP>
<FLID>121112312</FLID>
<FFID>CA-CA101-A-12DEC031345-I</FFID>
<FLIN>I</FLIN>
</FLOP>
</MSG>
```
<a id="sec-3-33"></a>
### 3.33 AODB flight returned event/ AODB 航班返航事件
<a id="sec-3-33-1"></a>
#### 3.33.1 Event Attributes/事件属性
```text
Message Code AODBFRET
消息代码
Event Description This event occurs whenever the flight‟s returned
事件描述 indicator is updated in AODB.
当 AODB 中一个航班的返航标志修改时，发生该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered by flight‟s returned indicator
频率 update in AODB.
非计划的，AODB 中航班返航标志改变时触发。
Reasons for flight‟s returned indicator update include:
返航标志改变的原因有：
Whenever a departure flight aborts take off and returns
back to stand and AODB operator marks the flight as
returned.
当一个离港航班中止起飞返回机位，AODB 操作员将该航
班标为返航。
If the flight returns after take-off it will be regarded as
return from airborne and AODB will send an AODBADFT
in that case. It is expected that AODB operator will also
remark the old flight as a „Return from airborne‟.
如果航班在起飞后返航，则认做是升空返航，AODB 将发
送 AODBADFT 事件。AODB 操作员将原航班标为升空返
航。
Data Range This is sent out only if the flight returned indicator is
数据范围 changed for a flight which is scheduled for operation
within the current operational window of „x‟ hours
(typically next 48 hours).
返航标志数据修改事件仅当航班建立的计划操作日期在当
前操作窗口内的若干小时（通常是 48 小时内）中发出。
Data Count Single flight returned indicator record in single XML
数据数 message.
一个 XML 报文中包括一个航班返航标志数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments None
注释 无
```
<a id="sec-3-33-2"></a>
#### 3.33.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M FLOP
data section.
消息发送类型。Meta Data段的一部
分。
XML Tag Description Format Req Values
STYP Subtype of message sent. Part of meta Char(4) M FRET
data section.
消息发送的子类型. Meta Data段的一部
分.
FLOP Identifies start of the operational data. - M This starts a section.
操作数据的开始标识 一个新段落的开始
FLID Unique AODB ID for identifying a flight Number(1-12) M
AODB中唯一的航班ID
FFID Friendly flight Id for easy identification. Char(20-32) M Formed by concatenating
航班ID别名，便于辨别 following fields of
AODBSCHD message in
order namely
ALCD, FLNO, MVIN,
SODT, FLIN
格式为AODBSCHD报文
中相关的字段顺序，
ALCD, FLNO, MVIN,
SODT, FLIN
FRET Contains a descriptive reason as to Char(1-30) P Free text reason for
why the flight has returned. Has a returned flight.
parameter called REID to indicate if it 自由文本格式
is an air or ground return.
Parameter REID =
航班返航的原因描述。带有参数REID表
Char(1)
示航班是升空返航或是地面返航。
G = Ground return/地面返
航
A = Air return/升空返航
An empty TAG means
the existing flight
returned indicator value
is being unset.
空表示航班返航标志清
除。
```
<a id="sec-3-33-3"></a>
#### 3.33.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>FLOP</TYPE>
<STYP>FRET</STYP>
</META>
<FLOP>
<FLID>121112312</FLID>
<FFID>CA-CA101-A-12DEC031345-D</FFID>
<FRET REID=”G”>EXIT DOOR FAULT</FRET>
</FLOP>
</MSG>
```
<a id="sec-3-34"></a>
### 3.34 AODB flight gate event/ AODB 航班登机门事件
<a id="sec-3-34-1"></a>
#### 3.34.1 Event Attributes/事件属性
```text
Message Code AODBGTDT
消息代码
Event Description This event occurs whenever a flight‟s gate related data
事件描述 is updated in AODB.
当 AODB 中一个航班的登机门修改时，发生该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered by flight‟s gate data update in
频率 AODB.
非计划的，AODB 中航班登机门改变时触发。
Reasons for gate data update include:
登机门改变的原因有：
Flight‟s gate(s) is assigned/de-assigned and sent by
RMS.
从 RMS 系统收到航班登机门分配/不分配信息。
Flight gate open time is set and sent by DCS.
DCS 设置发送登机门开放时间
Flight gate close time is set and sent by DCS.
DCS 设置发送登机门关闭时间
Any of above gate data for a flight is updated manually
in AODB.
在 AODB 中手工修改一个航班上述的登机门信息。
Data Range This is sent out only if the flight gate data is changed for
数据范围 a flight which is scheduled for operation within the
current operational window of „x‟ hours (typically next 48
hours).
Latest snapshot of all gate related data for a flight is
included.
登机门数据修改事件仅当航班建立的计划操作日期在当前
操作窗口内的若干小时（通常是 48 小时内）中发出。
包括一个航班所有的登机门相关数据。
Data Count One or more flight gate records in single XML message.
数据数 一条 XML 报文中包括一条或多条航班登机门数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments None
注释 无
Processing Exceptions RMS will reject this message if received from AODB.
处理例外 RMS如果从AODB收到这消息将拒绝
But if such data is specified in daily schedule message
RMS will process.
如果这些数据来自日计划，RMS将处理。
This message retained here only because RMSGTDT is
referring to this event for formats.
这个消息在这里只是便于RMSGTDT参考它的事件格式。
```
<a id="sec-3-34-2"></a>
#### 3.34.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M FLOP
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(4) M GTDT
data section.
消息发送的子类型. Meta Data段的一部
分.
FLOP Identifies start of the operational data. - M This starts a section.
操作数据的开始标识 一个新段落的开始
FLID Unique AODB ID for identifying a flight Number(1-12) M
AODB中唯一的航班ID
FFID Friendly flight Id for easy identification. Char(20-32) M Formed by concatenating
following fields of
XML Tag Description Format Req Values
航班ID别名，便于辨别 AODBSCHD message in
order namely
ALCD, FLNO, MVIN,
SODT, FLIN
格式为AODBSCHD报文
中相关的字段顺序，
ALCD, FLNO, MVIN,
SODT, FLIN
GTDT This indicates the start of gate related Number(1) P This starts a new section
data for a flight record. This includes a and includes gate
parameter GTNO to identify the gate specific information as
record number for a flight with multiple below. An empty TAG
gates. This data repeats for each gate <GTDT
of a flight. GTNO=“0”></GTDT> will
一个航班登机门数据的开始。包括参数 be sent for a flight with
GTNO表示多登机门航班的登机门号。 previous gate allocations
to signify there are no
每个登机门中重复出现。
gate allocations now.
新段落的开始包括登机门
的信息。空标签<GTDT
GTNO=“0”></GTDT>表
示航班已分配的登机门取
消了。
GATE Gate number assigned to this flight Char(1-8) M Gate code reference
航班分配的登机门号 table to be decided by
CDIA.
登机门代码参考数据由成
都机场定义
PGOT Planned time for gate open for flight Char(11) M DDMONYYHHMM
航班登机门的计划开启时间 Local time 24 hr format
当地时间24小时格式
PGCT Planned time for gate close for flight Char(11) M DDMONYYHHMM
航班登机门的计划关闭时间 Local time 24 hr format
当地时间24小时格式
GOTM Time when the flight was gated Char(11) O DDMONYYHHMM
登机门开放时间 Local time 24 hr format
Absent if no gate open
time assigned for flight.
当地时间24小时格式。空
表示航班未分配登机门开
放时间
GCTM Time when the gate was closed Char(11) O DDMONYYHHMM
登机门关闭时间 Local time 24 hr format
Absent if no gate open
time assigned for flight.
当地时间24小时格式。空
表示航班未分配登机门关
XML Tag Description Format Req Values
闭时间
GTYP Domestic or international indicator of Char(1) M D – Domestic/国内
gate resource I – International/国际
登机门资源的国内国际标志
```
<a id="sec-3-34-3"></a>
#### 3.34.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>FLOP</TYPE>
<STYP>GTDT</STYP>
</META>
<FLOP>
<FLID>121112312</FLID>
<FFID>CA-CA101-A-12DEC031345-D</FFID>
<GTDT GTNO=”1”>
<GATE>G28</GATE>
<PGOT>15DEC031805</PGOT>
<PGCT>15DEC031925</PGCT>
<GOTM>15DEC031825</GOTM>
<GTYP>D</GTYP>
</GTDT>
<GTDT GTNO=”2”>
<GATE>G33</GATE>
<PGOT>15DEC031805</PGOT>
<PGCT>15DEC031925</PGCT>
<GTYP>I</GTYP>
</GTDT>
<GTDT GTNO=”3”>
<GATE>G23</GATE>
<PGOT>15DEC031805</PGOT>
<PGCT>15DEC031925</PGCT>
<GTYP>D</GTYP>
</GTDT>
</FLOP>
</MSG>
```
<!-- 原 PDF 第 150 页 -->
<a id="sec-3-35"></a>
### 3.35 AODB flight last call time event/ AODB 航班最后通知时间事件
<a id="sec-3-35-1"></a>
#### 3.35.1 Event Attributes/事件属性
```text
Message Code AODBLACL
消息代码
Event Description This event occurs whenever a flight‟s last call time is
事件描述 updated in AODB.
当 AODB 中一个航班的最后通知时间修改时，发生该事
件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered by flight last call time update in
频率 AODB.
非计划的，AODB 中航班最后通知时间改变时触发。
Reasons for flight last call time update include:
最后通知时间改变的原因有：
A last call time update for a flight is received from DCS.
从 DCS 收到航班最后通知时间修改信息。
A last call time update is made manually in AODB.
在 AODB 中手工修改最后通知时间。
Data Range This is sent out only if the flight last call time is changed
数据范围 for a flight which is scheduled for operation within the
current operational window of „x‟ hours (typically next 48
hours).
最后通知时间数据修改事件仅当航班建立的计划操作日期
在当前操作窗口内的若干小时（通常是 48 小时内）中发
出。
Data Count Single flight last call time record in single XML message.
数据数 一条 XML 报文中包括一条航班最后通知时间数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments Sent only for departure flights
注释 仅对离港航班
Processing Exceptions RMS will not perform any validation on whether last call
处理例外 time is in future and set status to Last call once this
event is received. Last call status will be reset if empty
time is received.
RMS将不执行校验最后通知时间是不是在未来并在收到
消息时设置最后通知状态一次。在收到空时间后最后通知
状态将被重设。
```
<a id="sec-3-35-2"></a>
#### 3.35.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M FLOP
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(4) M LACL
data section.
消息发送的子类型. Meta Data段的一部
分.
FLOP Identifies start of the operational data. - M This starts a section.
操作数据的开始标识 一个新段落的开始
FLID Unique AODB ID for identifying a flight Number(1-12) M
AODB中唯一的航班ID
FFID Friendly flight Id for easy identification. Char(20-32) M Formed by concatenating
航班ID别名，便于辨别 following fields of
AODBSCHD message in
order namely
ALCD, FLNO, MVIN,
SODT, FLIN
格式为AODBSCHD报文
中相关的字段顺序，
ALCD, FLNO, MVIN,
SODT, FLIN
LACL Time for last call of departure flight Char(11) P DDMONYYHHMM
离港航班的最后通知时间 Local time 24 hr format.
当地时间24小时格式
An empty TAG means
the existing last call time
is being blanked out
空表示最后通知时间清除
```
<a id="sec-3-35-3"></a>
#### 3.35.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>FLOP</TYPE>
<STYP>LACL</STYP>
</META>
<FLOP>
<FLID>121112312</FLID>
<FFID>CA-CA101-A-12DEC031345-D</FFID>
<LACL>15DEC031755</LACL>
</FLOP>
</MSG>
```
<a id="sec-3-36"></a>
### 3.36 AODB flight maximum passengers event/ AODB 航班最大旅客数事件
<a id="sec-3-36-1"></a>
#### 3.36.1 Event Attributes/事件属性
```text
Message Code AODBMAXP
消息代码
Event Description This event occurs whenever the flight‟s maximum
事件描述 passenger count is updated in AODB.
当 AODB 向子系统发送任何最大旅客数数据时，产生该
事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered by flight maximum passenger
频率 count update in AODB.
非计划的，AODB 中航班的最大旅客数更改时触发：
Reasons for maximum passenger count update include:
最大旅客数更改的原因有：
Flight‟s aircraft or registration number is changed in
AODB, causing the maximum passengers on the flight to
change.
AODB 中航班使用的机型或注册号变化，引起航班的最大
旅客数更改。
A maximum passenger count is input manually in AODB
without an aircraft or registration number change.
AODB 中航班使用的机型或注册号未发生变化的情况下，
手工修改航班的最大旅客数。
Data Range This is sent out only if the maximum passenger count is
数据范围 changed for a flight which is scheduled for operation
within the current operational window of „x‟ hours
(typically next 48 hours).
最大旅客数事件仅当航班建立的计划操作日期在当前操作
窗口内的若干小时（通常是 48 小时内）中发出。
Data Count Single flight maximum passenger count record in single
数据数 XML message.
一个 XML 报文中包括一个航班最大旅客数数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments None
注释 无
```
<a id="sec-3-36-2"></a>
#### 3.36.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M FLOP
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(4) M MAXP
data section.
消息发送的子类型. Meta Data段的一部
分.
FLOP Identifies start of the operational data. - M This starts a section.
一条操作数据的开始标志 一个部分的开始
XML Tag Description Format Req Values
FLID Unique AODB ID for identifying a flight Number(1-12) M
AODB中一个航班唯一
FFID Friendly flight Id for easy identification. Char(20-32) M Formed by concatenating
航班ID别名，便于识别 following fields of
AODBSCHD message in
order namely
ALCD, FLNO, MVIN,
SODT, FLIN
格式为AODBSCHD报文
中的字段顺序ALCD,
FLNO, MVIN, SODT,
FLIN
MAXP Maximum passengers that this flight Number(1-3) P 0 – 999
can carry An empty TAG means
该航班的最大载客数 the existing maximum
passenger count value is
being deleted.
空表示最大载客数值被删
除
```
<a id="sec-3-36-3"></a>
#### 3.36.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>FLOP</TYPE>
<STYP>MAXP</STYP>
</META>
<FLOP>
<FLID>121112312</FLID>
<FFID>CA-CA101-A-15JAN041345-D</FFID>
<MAXP>130</MAXP>
</FLOP>
</MSG>
```
<a id="sec-3-37"></a>
### 3.37 AODB flight handling agent/ AODB 航班 服务代理事件
<a id="sec-3-37-1"></a>
#### 3.37.1 Event Attributes/事件属性
```text
Message Code AODBHNAG
消息代码
Event Description This event occurs whenever the flight‟s handling agent
事件描述 data is updated in AODB.
当 AODB 中一个航班的服务代理修改时，发生该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered by flight handling agent data
频率 update in AODB.
非计划的，AODB 中航班服务代理数据改变时触发。
Reasons for handling agent data update include:
服务代理数据修改的原因有：
A new contract is signed for servicing a flight causing its
field (or ground) handing agent or passenger handling
agent or maintenance handling agent, for a given day to
change.
签订新的航班服务合同后，导致它的机坪（或地面）服务
代理或旅客服务代理或维护服务代理在某天改变。
Field (or Ground) handling agent or passenger handling
agent or maintenance handling agent is updated for a
flight manually in AODB.
AODB 中手工修改机坪（或地面）服务代理或旅客服务代
理或维护服务代理。
Data Range This is sent out only if the handling agent data is
数据范围 changed for a flight which is scheduled for operation
within the current operational window of „x‟ hours
(typically next 48 hours).
服务代理事件仅当航班建立的计划操作日期在当前操作窗
口内的若干小时（通常是 48 小时内）中发出。
Data Count Single flight‟s field (or ground) handling agent data
数据数 record and passenger handling agent record and
maintenance handling agent record in single XML
message.
在一个 XML 报文中包括一个机坪（或地面）服务代理和
旅客服务代理和维护服务代理。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments CDIA may choose any of the below three handling agent
注释 fields in AODB to influence subsystem business logic
like RMS. For e.g. all CA flights might prefer particular
field handling agent located near the east side of airport
and so would want a stand allocated on that side. So
CDIA will input such field handling agent for CA flights in
the field handling agent field specified below in AODB.
These 3 fields when sent to subsystems, will act as one
of the hints to influence subsystems‟ business logic.
成都机场可以选择AODB中三个服务代理中的任何一个来
改变子系统子系统中的业务逻辑，如RMS。例如，所有
CA的航班由靠近机场东部的那个机坪服务代理，所以想
在那一侧分到机位。成都机场在AODB中可以为CA指定
这样的机坪服务代理字段。这3个字段发送到子系统中，
成为影响子系统运行的隐含因素。
```
<a id="sec-3-37-2"></a>
#### 3.37.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M FLOP
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(4) M HNAG
data section.
消息发送的子类型. Meta Data段的一部
分.
FLOP Identifies start of the operational data. - M This starts a section.
操作数据的开始标识 一个新段落的开始
FLID Unique AODB ID for identifying a flight Number(1-12) M
AODB中唯一的航班ID
FFID Friendly flight Id for easy identification. Char(20-32) M Formed by concatenating
航班ID别名，便于辨别 following fields of
AODBSCHD message in
order namely
ALCD, FLNO, MVIN,
SODT, FLIN
格式为AODBSCHD报文
中相关的字段顺序，
ALCD, FLNO, MVIN,
SODT, FLIN
FHAG Field (or Ground) Handling agent for Number(1-9) P Organization id of field
flight that affects. handling agent.
该航班的机坪（或外场）服务代理 Reference codes to be
decided by CDIA. An
XML Tag Description Format Req Values
empty TAG means the
existing field handling
agent value is being
deleted.
机坪服务代理的机构代
码。参考代码将由成都机
场决定。空表示已有的代
理值删除。
PHAG Passenger Handling agent for flight Number(1-9) P Organization id of
航班的旅客服务代理 passenger handling
agent. Reference codes
to be decided by CDIA.
旅客服务代理的机构代
码。参考代码将由成都机
场决定。
MHAG Maintenance Handling agent for flight. Number(1-9) O Organization id of
航班的维护服务代理 maintenance handling
agent. Reference codes
to be decided by CDIA.
维护服务代理的机构代
码。参考代码将由成都机
场决定。
```
<a id="sec-3-37-3"></a>
#### 3.37.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>FLOP</TYPE>
<STYP>HNAG</STYP>
</META>
<FLOP>
<FLID>121112312</FLID>
<FFID>CA-CA101-A-12DEC031345-D</FFID>
<FHAG>234523</FHAG>
<PHAG>22313</PHAG>
<MHAG>234523</MHAG>
</FLOP>
</MSG>
```
<!-- 原 PDF 第 158 页 -->
<a id="sec-3-38"></a>
### 3.38 AODB flight planned stands event/ AODB 航班计划机位事件
<a id="sec-3-38-1"></a>
#### 3.38.1 Event Attributes/事件属性
```text
Message Code AODBPSDT
消息代码
Event Description This event occurs whenever the planned stand data is
事件描述 updated in AODB.
当 AODB 中一个航班的计划机位修改时，发生该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered by flight planned stand data
频率 update in AODB.
非计划的，AODB 中航班计划机位数据改变时触发。
Reasons for planned stand data update include:
计划机位数据修改的原因有：
Planned stands allocation for confirmed parking stands
for a flight are received from RMS.
从 RMS 收到航班计划机位位置确认信息。
Stands allocation updates for unconfirmation of
previously confirmed parking stands for a flight are
received from RMS.
从 RMS 收到航班计划机位位置已确认信息改为未确认信
息。
Allocation timing updates for confirmed parking stands
for a flight are received from RMS.
从 RMS 收到航班确认停机位时间更改信息。
All above information is updated manually in AODB.
在 AODB 手动修改上述航班数据。
Data Range This is sent out only if the data related to flight planned
数据范围 stand data is changed for a flight which is scheduled for
operation within the current operational window of „x‟
hours (typically next 48 hours).
航班的计划机位事件仅当航班建立的计划操作日期在当前
操作窗口内的若干小时（通常是 48 小时内）中发出。
Data Count One or more planned stand data records in single XML
数据数 message. Each planned stand will include full snapshot
of latest parking information for flight.
一个 XML 报文中包括一个或多个航班行李转盘数据。每
个计划机位包括一个航班中所有相关的机位数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments 1. A chocks time update from AODB will not trigger a
注释 planned stand update.
AODB中轮挡时间的修改不会触发计划机位的更新。
2. Planned stands will be sent separately for arrivals
and departures as per the stand planning logic
explained below.
到达和离港的计划机位会分开发送，每个机位计划如下。
Processing Exceptions RMS will reject this message if received from AODB.
处理例外 RMS如果从AODB收到这消息将拒绝
But if such data is specified in daily schedule message
RMS will process.
如果这些数据来自日计划，RMS将处理。
This message retained here only because RMSPSDT is
referring to this event for formats.
这个消息在这里只是便于RMSPSDT参考它的事件格式。
Planned stand allocation policy for CDIA will be as follows
成都机场的计划机位分配策略如下
a. A rotation (or link or turnaround) is treated as combination of an arrival flight and
a departure flight sharing same aircraft.
转场（或连接或经停）航班认做是一个到达和离港结合的航班，共享一架飞机。
b. In case of an aircraft needing multiple stands parking, all stand movements will
be planned and recorded against the arrival flight except the very last movement.
当一架飞机需要停靠多机位时，要计划并记录该到达航班的所有机位移动，除了非常
前面的移动。
c. The last movement will be planned for both arrival and its turnaround departure.
到达和经停离港的最后移动要做计划。
d. The actual recording of the last movement will be “On Chocks” for arrival flight
and “Off chocks” for the turnaround departure.
到达航班最后移动的实际记录为“上轮挡”，经停离港的为“下轮挡”。
e. In AODB, for an aircraft still to arrive, the “current stand” will be the first planned
stand. Subsequently each time an “On Chocks” event comes for a flight (because
the aircraft moves to a stand), the “current stand” will be updated to reflect the
latest stand for which the On Chocks event arrived.
在 AODB 中，到达航班要到达时，“当前机位”是第一计划的机位。然后，当航班每
个“上轮挡”事件发生时（飞机滑至机位），“当前机位”更新为上轮挡事件的最后
机位。
f. The above can be explained using the following examples.
参考下面例子。
Note: This is for illustration actual formats to be based on XML.
注意：以下演示根据 XML 的实际格式
Case 1: Single Stand Used by Turn Around
例 1：经停航班使用单个机位
It is expected CA101 will arrive on Stand 11 at 1030 and depart as
CA102 from same Stand at 1330.
CA101 将在 10：30 降落停靠 11 号机位，13：30 在同一机位使用航班号 CA102 离港。
So RMS will send following planned stand information to AODB.
RMS 将发送以下计划机位信息给 AODB：
Planned Stands Against CA101
CA101 Arr Stand = S11 STST=1030 STET=1030
Planned Stands Against CA102
CA102 Dep Stand = S11 STST=1030 STET=1330
Assuming the flight is on time AODB (based on VDGS events) will
send the following Chocks Time events
When CA101 arrives
CA101 Arr Stand = S11 SeqNo = 1 Chock On Time = 1035
When the flight departs as CA102
CA102 Dep Stand = S11 SeqNo = 1 Chock Off Time = 1332
Case 2: Multiple Stand Moves Prior to Turn Around
例 2：经停航班使用多机位
It is expected CA101 will arrive on Stand 11 at 1030, unload, go
to remote stand 22 at 1145 and park till 1320, then go to contact
Stand 15 and depart as CA102 at 1445.
CA101 将在 10：30 降落停靠 11 号机位，卸货，11：45 滑至远机位 22 停至 13：20，
然后滑行到近机位 15 号使用航班号 CA102 在 14：45 离港。
So RMS will send following planned stand information to AODBAODB.
RMS 将发送以下计划机位信息给 AODB：
Planned Stands Against CA101
CA101 Arr Stand = S11 SeqNo = 1 STST=1030 STET=1145
CA101 Arr Stand = R22 SeqNo = 2 STST=1145 STET=1320
CA101 Arr Stand = S15 SeqNo = 3 STST=1320 STET=1320
Planned Stands Against CA102
CA102 Dep Stand = S15 SeqNo = 1 STST=1320 STET=1445
Assuming the flight is on time AODB (based on VDGS events) will
send the following Chocks Time events
When CA101 arrives and moves across stands
CA101 Arr Stand = S11 SeqNo = 1 Chock On Time = 1035
CA101 Arr Stand = S11 SeqNo = 1 Chock Off Time = 1140
CA101 Arr Stand = R22 SeqNo = 2 Chock On Time = 1145
CA101 Arr Stand = R22 SeqNo = 2 Chock Off Time = 1315
CA101 Arr Stand = S15 SeqNo = 3 Chock On Time = 1320
When the flight departs as CA102
CA102 Dep Stand = S15 SeqNo = 1 Chock Off Time = 1445
```
<a id="sec-3-38-2"></a>
#### 3.38.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M FLOP
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(4) M PSDT
data section.
消息发送的子类型. Meta Data段的一部
分.
FLOP Identifies start of the operational data. - M This starts a section.
操作数据的开始标识 一个新段落的开始
FLID Unique AODB ID for identifying a flight Number(1-12) M
AODB中唯一的航班ID
FFID Friendly flight Id for easy identification. Char(20-32) M Formed by concatenating
航班ID别名，便于辨别 following fields of
AODBSCHD message in
order namely
ALCD, FLNO, MVIN,
SODT, FLIN
格式为AODBSCHD报文
中相关的字段顺序，
ALCD, FLNO, MVIN,
SODT, FLIN
PSDT This indicates the start of planned Number(1) P This is start of
stands data for a flight record. This information for one stand
includes a parameter PSNO to identify and the section could
the planned stand sequence number repeat for multiple
for a flight with multiple planned planned stands.
stands. One record will have data for Maximum 9 planned
one planned stand. stands are expected per
航班计划机位数据的开始标志。包括一 flight. An empty TAG
个参数PSNO表示多计划机位航班的机 <PSDT
PSNO=“0”></PSDT>
位号。每条记录包括一个计划机位数
here indicates there are
据。
no planned stand
allocations for flight
XML Tag Description Format Req Values
currently.
是一个机位信息的开始，
多个机位可以重复出现。
每个航班最多9个计划机
位。空标签<PSDT
PSNO=“0”></PSDT>表示
当前航班未分配计划机
位。
PSST This is the actual parking stand for Char(1-8) M Stand code reference
current planned stand record table to be decided by
当前计划机位记录的实际停机位 CDIA.
机位代码参考数据表由成
都机场定义
STST Start time of stand allocation for the Char(11) O DDMONYYHHMM
flight. Local time 24 hr format.
航班分配机位的开始时间 当地时间24小时格式
STET End time of stand allocation for the Char(11) O DDMONYYHHMM
flight. Local time 24 hr format.
航班分配机位的结束时间 当地时间24小时格式
```
<a id="sec-3-38-3"></a>
#### 3.38.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>FLOP</TYPE>
<STYP>PSDT</STYP>
</META>
<FLOP>
<FLID>121112312</FLID>
<FFID>CA-CA101-A-12DEC031345-D</FFID>
<PSDT PSNO=”1”>
<PSST>S211</PSST>
<STST>15DEC021330</STST>
<STET>15DEC021415</STET>
</PSDT>
<PSDT PSNO=”2”>
<PSST>R211</PSST>
<STST>15DEC021415</STST>
<STET>15DEC021515</STET>
</PSDT>
<PSDT PSNO=”3”>
<PSST>S209</PSST>
<STST>15DEC021515</STST>
<STET>15DEC021645</STET>
</PSDT>
</FLOP>
</MSG>
```
<a id="sec-3-39"></a>
### 3.39 AODB flight registration event/ AODB 航班注册号事件
<a id="sec-3-39-1"></a>
#### 3.39.1 Event Attributes/事件属性
```text
Message Code AODBRENO
消息代码
Event Description This event occurs whenever a flight‟s registration
事件描述 number is updated in AODB.
当 AODB 中一个航班的注册号修改时，发生该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered by flight registration number
频率 update in AODB.
非计划的，AODB 中航班注册号改变时触发。
Reasons for registration number update include:
注册号改变的原因有：
A registration update for a flight is received from an
external system like ATC.
从外部系统如 ATC 收到航班注册号更新信息。
A registration update for a flight is made manually in
AODB.
在 AODB 中手工修改一个航班的注册号。
A flight‟s aircraft type is changed which indirectly causes
a registration number update.
航班机型改变直接引起注册号的更改。
Data Range This is sent out only if the flight registration number is
数据范围 changed for a flight which is scheduled for operation
within the current operational window of „x‟ hours
(typically next 48 hours).
注册号数据修改事件仅当航班建立的计划操作日期在当前
操作窗口内的若干小时（通常是 48 小时内）中发出。
Data Count Single flight registration record in single XML message.
数据数 一条 XML 报文中包括一条航班注册号数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments None
注释 无
```
<a id="sec-3-39-2"></a>
#### 3.39.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M FLOP
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(4) M RENO
data section.
消息发送的子类型. Meta Data段的一部
分.
FLOP Identifies start of the operational data. - M This starts a section.
操作数据的开始标识 一个新段落的开始
FLID Unique AODB ID for identifying a flight Number(1-12) M
AODB中唯一的航班ID
FFID Friendly flight Id for easy identification. Char(20-32) M Formed by concatenating
航班ID别名，便于辨别 following fields of
AODBSCHD message in
order namely
ALCD, FLNO, MVIN,
SODT, FLIN
格式为AODBSCHD报文
中相关的字段顺序，
ALCD, FLNO, MVIN,
SODT, FLIN
RENO Registration or tail Number of flight Char(1-10) P An empty TAG means
航班注册号或尾号 the existing registration
value is being blanked
out
XML Tag Description Format Req Values
空表示注册号清除。
```
<a id="sec-3-39-3"></a>
#### 3.39.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>FLOP</TYPE>
<STYP>RENO</STYP>
</META>
<FLOP>
<FLID>121112312</FLID>
<FFID>CA-CA101-A-12DEC031345-D</FFID>
<RENO>T5561</RENO>
</FLOP>
</MSG>
```
<a id="sec-3-40"></a>
### 3.40 AODB flight routing event/ AODB 航班航线事件
<a id="sec-3-40-1"></a>
#### 3.40.1 Event Attributes/事件属性
```text
Message Code AODBROUT
消息代码
Event Description This event occurs whenever the data related to flight
事件描述 routing is updated in AODB.
当 AODB 中一个航班的航线修改时，发生该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered by flight routing update in
频率 AODB.
非计划的，AODB 中航班航线改变时触发。
Reasons for routing update include:
航线改变的原因有：
A routing change for a flight is received from an external
system like ATC.
从外部系统如 ATC 收到航班航线更新信息。
A routing change for a flight is made manually in AODB.
在 AODB 中手工修改一个航班的航线。
Routing timings are updated for a flight (like previous /
next step time) without changing the routing itself.
航班航线未改但航线时间变化（如前/后站时间）
Data Range This is sent out only if the data related to flight routing is
数据范围 changed for a flight which is scheduled for operation
within the current operational window of „x‟ hours
(typically next 48 hours).
航线数据修改事件仅当航班建立的计划操作日期在当前操
作窗口内的若干小时（通常是 48 小时内）中发出。
Data Count One or more routing records in single XML message.
数据数 Each routing event will include full snapshot of latest
routing for flight.
一条 XML 报文中包括一条或多条航班航线数据。每个航
线事件包括航班所有的航线数据
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments 1. Whenever there is a routing change it may also
注释 trigger flight indicator change event, based on
the new routing. For e.g. if a flight operating in a
domestic route is changed to an international
route, the flight indicator will change.
当航线改变时，可能触发航班标识改变事件。如航班
由国内航线改为国际航线，航班标识会变。
2. For multi leg flights routing contents will be as
follows:
多航段航线内容如下：
a. For departures ROUT will be sent
AODB such that RTNO =1 corresponds
to the next immediate departure stop,
RTNO = 2 corresponds to the second
next departure stop and so on.
离港ROUT在AODB中发送RTNO＝1表示第
一个离港站，RTNO＝2表示第二个离港站，
以此类推。
b. For arrivals ROUT will be sent by AODB
such that RTNO =1 corresponds to the
previous immediate arrival station,
RTNO = 2 corresponds to the second
previous arrival stop and so on.
到达ROUT在AODB中发送RTNO＝1表示第
一个到达站，RTNO＝2表示第二个到达站，
依此类推。
c. To get to flight final destination or flight
initial origin subsystems will look at the
last ROUT element or ROUT element
with maximum RTNO.
航班的终点或是起点，从 ROUT 的最后参数
或最大 RTNO 号中查找。
Processing Exceptions RMS can only support 4 route records for route event.
处理例外 So RMS will accept the 4 most relevant routing records.
For a departure this will be the first 4, while for an arrival
it will be the last 4.
RMS只能支持4个航站。所以RMS支持最相关的4个航线
记录。对于离港是前四个，对于到港时后四个。
RMS will ignore SCAT/SCDT tags in ROUT section
RMS将忽略ROUT部分中的SCAT/SCDT标签。
```
<a id="sec-3-40-2"></a>
#### 3.40.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M FLOP
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(4) M ROUT
data section.
消息发送的子类型. Meta Data段的一部
分.
FLOP Identifies start of the operational data. - M This starts a section.
操作数据的开始标识 一个新段落的开始
FLID Unique AODB ID for identifying a flight Number(1-12) M
AODB中唯一的航班ID
FFID Friendly flight Id for easy identification. Char(20-32) M Formed by concatenating
航班ID别名，便于辨别 following fields of
AODBSCHD message in
order namely
ALCD, FLNO, MVIN,
SODT, FLIN
格式为AODBSCHD报文
中相关的字段顺序，
ALCD, FLNO, MVIN,
XML Tag Description Format Req Values
SODT, FLIN
ROUT Identifies start of one routing record. At Number(1) M This starts a new section
least one routing record is required per and encloses the routing
flight. This section repeats for each details of flight.
flight step. Includes a parameter called 一个新段落的开始，将一
RTNO to identify the route number 个航班航线信息括起来。
一条航线记录的开始。每个航班需要至
少一条航线记录。每个航段中重复出现
该部分。带有参数RTNO表示航段。
APCD This is the previous airport for arrivals Char(3) M IATA airport code
and next airport for departures IATA机场代码
航班前一个到达机场和下一个离港机场
SCAT The scheduled date time of arrival at Char(11) O DDMONYYHHMM
this stop Local time 24 hr format.
本站计划到达日期时间 This will be absent for
starting point of an arrival
flight.
当地时间24小时格式
对航班起点站无该字段。
SCDT The scheduled date time of departure Char(11) O DDMONYYHHMM
from this stop Local time 24 hr format.
本站计划离港日期时间 This will be absent for
last stop of flight
当地时间24小时格式
对航班终点站无该字段。
```
<a id="sec-3-40-3"></a>
#### 3.40.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>FLOP</TYPE>
<STYP>ROUT</STYP>
</META>
<FLOP>
<FLID>121112312</FLID>
<FFID>CA-CA101-A-12DEC031345-D</FFID>
<ROUT RTNO=”1”>
<APCD>CTU</APCD>
<SCAT></SCAT>
<SCDT>15DEC031340</SCDT>
</ROUT>
</FLOP>
</MSG>
```
<a id="sec-3-41"></a>
### 3.41 AODB flight turnaround event/ AODB 航班经停事件
<a id="sec-3-41-1"></a>
#### 3.41.1 Event Attributes/事件属性
```text
Message Code AODBTAOP
消息代码
Event Description This event occurs whenever the flight turnaround
事件描述 information is updated in AODB.
当 AODB 中一个航班的经停信息修改时，发生该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered by flight turnaround information
频率 in AODB.
非计划的，AODB 中航班经停信息改变时触发。
Reasons for flight turnaround information update
include:
航班经停信息修改的原因有：
An unlinked arrival / departure flight is manually linked in
AODB.
将一个不连接的到达/离港航班在 AODB 手工连接起来。
A linked arrival / departure flight is manually unlinked in
AODB.
将一个连接的到达/离港航班在 AODB 中手工分离。
Flight‟s aircraft is updated for either the arrival or
departure portion of a turnaround in AODB causing a
link break.
AODB 中到达或离港航班使用的飞机更新引起连接断开。
Flight‟s registration number is updated for either the
arrival or departure portion of a turnaround in AODB
causing a link break.
AODB 中到达或离港航班的注册号更新引起连接断开。
Either the arrival or departure portion of a turnaround is
cancelled in AODB causing a link break.
AODB 中到达或离港航班取消引起连接断开。
Either the arrival or departure portion of a turnaround is
deleted in AODB causing a link break.
AODB 中到达或离港航班删除引起连接断开。
Data Range This is sent out only if the data related to flight
数据范围 turnaround information is changed for a flight which is
scheduled for operation within the current operational
window of „x‟ hours (typically next 48 hours).
经停航班的相关数据更新事件仅当航班建立的计划操作日
期在当前操作窗口内的若干小时（通常是 48 小时内）中
发出。
Data Count Single flight turnaround information record in single XML
数据数 message.
一个 XML 报文中包括一个经停航班信息数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments 1. Sent only for arrival flights
注释 仅对到达航班
2. In case other events like aircraft update,
registration update, cancellation, deletion etc
cause a turnaround link break, the break link will
be sent first.
在其他事件如飞机更换、注册号修改、取消、删除等
引起的经停连接断开时，将先发送断开连接事件。
```
<a id="sec-3-41-2"></a>
#### 3.41.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M FLOP
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(4) M TAOP
data section.
消息发送的子类型. Meta Data段的一部
分.
FLOP Identifies start of the operational data. - M This starts a section.
操作数据的开始标识 一个新段落的开始
FLID Unique AODB ID for identifying a flight Number(1-12) M
XML Tag Description Format Req Values
AODB中唯一的航班ID
FFID Friendly flight Id for easy identification. Char(20-32) M Formed by concatenating
航班ID别名，便于辨别 following fields of
AODBSCHD message in
order namely
ALCD, FLNO, MVIN,
SODT, FLIN
格式为AODBSCHD报文
中相关的字段顺序，
ALCD, FLNO, MVIN,
SODT, FLIN
TAOP Turnaround operator when it leaves Char(2-3) P IATA operator code. An
current airport empty TAG means the
离开机场时经停承运人。 existing turnaround link
for an arrival is broken
and the arrival is no more
linked to any departure.
IATA承运人代码。空表示
该到达航班的经停连接断
开没有离港航班了。
TAFL Turnaround flight number when it Char(1-12) P An empty TAG means
leaves current airport the existing turnaround
离开机场时的经停航班号 link for an arrival is
broken and the arrival is
no more linked to any
departure.
空表示该到达航班的经停
连接断开没有离港航班
了。
TAID Unique AODB ID of the turnaround Number(1-12) P An empty TAG means
flight the existing turnaround
经停航班唯一的AODB ID link for an arrival is
broken and the arrival is
no more linked to any
departure.
空表示该到达航班的经停
连接断开没有离港航班
了。
```
<a id="sec-3-41-3"></a>
#### 3.41.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>173243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>FLOP</TYPE>
<STYP>TAOP</STYP>
</META>
<FLOP>
<FLID>121112312</FLID>
<FFID>CA-CA101-A-12DEC031345-D</FFID>
<TAOP>CA</TAOP>
<TAFL>CA201</TAFL>
<TAID>6213345</TAID>
</FLOP>
</MSG>
```
<a id="sec-3-42"></a>
### 3.42 AODB flight terminal event/ AODB 航班航站楼事件
<a id="sec-3-42-1"></a>
#### 3.42.1 Event Attributes/事件属性
```text
Message Code AODBTRML
消息代码
Event Description This event occurs whenever the flight terminal is
事件描述 updated in AODB.
当 AODB 中一个航班的航站楼改变时，发生该事件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered by flight terminal update in
频率 AODB.
非计划的，AODB 中航班航站楼改变时触发。
Reasons for flight terminal update include:
航班航站楼修改的原因有：
A flight terminal change for a flight is made manually in
AODB.
在 AODB 中手工修改一个航班的航站楼。
Data Range This is sent out only if the data related to flight terminal
数据范围 is changed for a flight which is scheduled for operation
within the current operational window of „x‟ hours
(typically next 48 hours).
航班航站楼相关数据修改事件仅当航班建立的计划操作日
期在当前操作窗口内的若干小时（通常是 48 小时内）中
发出。
Data Count Single flight terminal record in single XML message.
数据数 在一个 XML 报文中包括一条航班航站楼记录
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments None
注释 无
```
<a id="sec-3-42-2"></a>
#### 3.42.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M FLOP
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(4) M TRML
data section.
消息发送的子类型. Meta Data段的一部
分.
FLOP Identifies start of the operational data. - M This starts a section.
操作数据的开始标识 一个新段落的开始
FLID Unique AODB ID for identifying a flight Number(1-12) M
AODB中唯一的航班ID
FFID Friendly flight Id for easy identification. Char(20-32) M Formed by concatenating
航班ID别名，便于辨别 following fields of
AODBSCHD message in
order namely
ALCD, FLNO, MVIN,
SODT, FLIN
格式为AODBSCHD报文
中相关的字段顺序，
ALCD, FLNO, MVIN,
SODT, FLIN
TRML Terminal from which the flight will Char(1-5) P Terminal codes to be
operate decided by CDIA. An
航班的运营的航站楼 empty TAG means the
terminal value originally
assigned is being deleted
now i.e. flight has no
XML Tag Description Format Req Values
terminal assigned.
航站楼代码由成都机场定
义。空表示原航站楼删除
即航班未分配航站楼。
```
<a id="sec-3-42-3"></a>
#### 3.42.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>173243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>FLOP</TYPE>
<STYP>TRML</STYP>
</META>
<FLOP>
<FLID>121112312</FLID>
<FFID>CA-CA101-A-12DEC031345-D</FFID>
<TRML>T2</TRML>
</FLOP>
</MSG>
```
<a id="sec-3-43"></a>
### 3.43 AODB flight VIP passengers event/ AODB 航班 VIP 旅客事件
<a id="sec-3-43-1"></a>
#### 3.43.1 Event Attributes/事件属性
```text
Message Code AODBVIPP
消息代码
Event Description This event occurs whenever the flight‟s VIP passenger
事件描述 data is updated in AODB.
当 AODB 中一个航班的 VIP 旅客数据修改时，发生该事
件。
Single Recipient No
接收者 无
Frequency Unscheduled, triggered by flight VIP passenger data
频率 update in AODB.
非计划的，AODB 中航班 VIP 旅客数据改变时触发。
Reasons for VIP passenger data update include:
VIP 旅客数据修改的原因：
VIP passengers are assigned to a flight causing the VIP
passenger count or the VIP ranking of the flight to
change.
航班 VIP 旅客数变化或航班的 VIP 等级更改。
Data Range This is sent out only if the VIP passenger data is
数据范围 changed for a flight which is scheduled for operation
within the current operational window of „x‟ hours
(typically next 48 hours).
航班 VIP 旅客事件仅当航班建立的计划操作日期在当前操
作窗口内的若干小时（通常是 48 小时内）中发出。
Data Count Single flight VIP passenger data record in single XML
数据数 message.
一个 XML 报文中包括一个航班 VIP 旅客数据记录。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments None
注释 无
Processing Exceptions RMS will ignore VIPP
处理例外 RMS将忽略VIPP
```
<a id="sec-3-43-2"></a>
#### 3.43.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M FLOP
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(4) M VIPP
data section.
消息发送的子类型. Meta Data段的一部
分.
XML Tag Description Format Req Values
FLOP Identifies start of the operational data. - M This starts a section.
操作数据的开始标识 一个新段落的开始
FLID Unique AODB ID for identifying a flight Number(1-12) M
AODB中唯一的航班ID
FFID Friendly flight Id for easy identification. Char(20-32) M Formed by concatenating
航班ID别名，便于辨别 following fields of
AODBSCHD message in
order namely
ALCD, FLNO, MVIN,
SODT, FLIN
格式为AODBSCHD报文
中相关的字段顺序，
ALCD, FLNO, MVIN,
SODT, FLIN
VIPP VIP passengers. This will be present Number(1-3) P Number of VIP
when there are VIP passengers on that passengers in current
flight flight. An empty TAG
VIP旅客。当航班中有VIP旅客时出现。 means the existing VIP
passenger count value is
being deleted.
当前航班的VIP旅客数。
空表示已有的VIP旅客数
删除。
VIPR VIP flight ranking flag Number(1) P A single digit number to
VIP航班等级标志 be decided by CDIA to
indicate VIP ranking. 0
means not VIP.
一个单一数字表示VIP的
等级。具体数字将由CDIA
决定。0表示不是VIP航
班。
An empty TAG means
the existing VIP rating
value is being deleted.
空表示VIP级别值被删除
```
<a id="sec-3-43-3"></a>
#### 3.43.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>FLOP</TYPE>
<STYP>VIPP</STYP>
</META>
<FLOP>
<FLID>121112312</FLID>
<FFID>CA-CA101-A-12DEC031345-D</FFID>
<VIPP>2</VIPP>
<VIPR>3</VIPR>
</FLOP>
</MSG>
```
<a id="sec-3-44"></a>
### 3.44 AODB error to RMS event/ AODB 发向 RMS 的错误事件
<a id="sec-3-44-1"></a>
#### 3.44.1 Event Attributes/事件属性
```text
Message Code AODBERORRMS
消息代码
Event Description This is triggered whenever AODB needs to send an
事件描述 error message to RMS.
当 AODB 需要向 RMS 发送错误信息事件时发生。
Single Recipient Yes
接收者 是
Frequency Unscheduled, triggered by error handling in AODB.
频率 非计划的，AODB 发生错误时触发。
Reasons for error event send include:
错误事件原因有：
AODB finds an error in the input
message/format/content from RMS.
AODB 从 RMS 中发现输入的报文/格式/内容错误。
AODB cannot logically process the message from RMS
due to business logic conflict.
AODB 收到的 RMS 报文无法处理，与商业流程冲突。
AODB cannot process the message from RMS due to
internal AODB error.
由于内部错误，AODB 无法处理收到的 RMS 报文。
Data Range Not Applicable.
数据范围 不适用
Data Count Single error record in single XML message. Multiple
数据数 errors are conveyed as separate events.
一个 XML 报文中包括一条错误记录。多个错误分开成多
个事件。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments None
注释 无
Processing Exceptions RMS will ignore the following fields in the message
处理例外 RMS将忽略消息中下列字段
RSND
```
<a id="sec-3-44-2"></a>
#### 3.44.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M EROR
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(4) M NONE
data section.
消息发送的子类型. Meta Data段的一部
分.
EROR Identifies start of the error reporting - M This starts a section.
data. 一个段落的开始
错误报告数据的开始标志
SEQS Sequence number from the meta data Number(1-6) M Copy SEQN field from
of RMS source message where error source message
was found 从原报文中复制SEQN字
RMS中meta数据存在错误字段的顺序 段
号
TYPS Message type from the meta data of Char(4) M Copy TYPE field from
RMS source message where error was source message
found 从原报文中复制TYPE字
RMS中meta数据存在错误字段的报文 段
类型
STYS Message sub type from the meta data Char(4) M Copy STYP field from
of RMS source message where error source message
was found 从原报文中复制STYP字
RMS中meta数据存在错误字段的报文 段
XML Tag Description Format Req Values
子类型
ETEX This is a descriptive text indicating Char(1-200) M
error
错误的文字描述
RSND This is a flag to indicate whether to Char(1) M Y or N
request an automatic resend of the
message or not
是否请求一个自动重发标识
```
<a id="sec-3-44-3"></a>
#### 3.44.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>AODB</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>EROR</TYPE>
<STYP>NONE</STYP>
</META>
<EROR>
<SEQS>123123</SEQS>
<TYPS>FLOP</TYPS>
<STYS>GTDT</STYS>
<ETEX>Error updating DB incorrect stand value</ETEX>
<RSND>N</RSND>
</EROR>
</MSG>
```
<!-- 原 PDF 第 180 页 -->
<a id="sec-4"></a>
## 4 RMS to AODB Event Details/RMS 到 AODB 事件
<a id="sec-4-1"></a>
### 4.1 RMS flight check in counter event/ RMS 航班值机柜台事件
<a id="sec-4-1-1"></a>
#### 4.1.1 Event Attributes/事件属性
```text
Message Code RMSCKDT
消息代码
Event Description This is triggered whenever RMS needs to send flight
事件描述 check in counter assignments including timing changes
to AODB.
当 RMS 中一个航班的值机柜台相关数据修改时（包括时
间修改），发生该事件。
Single Recipient Yes
接收者 是
Frequency Unscheduled, triggered by check in counter assignment
频率 in RMS.
非计划的，RMS 中航班值机柜台数据改变时触发。
Reasons for check in counter assignment include:
值机柜台数据修改的原因有：
RMS operator confirms a check in counter allocation
within RMS.
RMS 操作员在 RMS 中确认了一个值机柜台分配。
RMS operator unconfirms a previously confirmed check
in counter allocation within RMS.
RMS 操作员在 RMS 中取消了一个值机柜台之前的确认。
RMS operator manually changes the counter occupancy
timings for previously confirmed counter allocations for a
flight.
RMS 操作员手动改变一个已经确认的值机柜台的占用时
间。
RMS system automatically changes the counter
occupancy timings for previously confirmed counter
allocations for a flight.
RMS 系统自动为一个已经确认的值机柜台修改柜台占用
时间。
Data Range This is sent out only if the flight check in counter data is
数据范围 changed for a flight within RMS operational window
(which may/may not map to typical AODB window of 48
hours)
航班值机柜台事件仅当航班建立的计划操作日期在 RMS
当前操作窗口内的若干小时（可能也可能不和 AODB 通
常的 48 小时时间窗匹配）中发出。
Latest snapshot of all check in counter related data for a
flight should be included.
包括一个航班中所有相关的值机柜台数据。
Data Count One or more flight check in counter assignment records
数据数 in single XML message.
一个 XML 报文中包括一个或多个航班值机柜台数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments 1. All check in counter assignments for a flight are
注释 to be sent with each change. This is so that any
check in counter message from RMS will
contain complete snapshot of all check in
counters currently confirmed for that flight in
RMS.
每一次修改都会发送航班的整个值机柜台分配。
也就是说RMS发送的消息将包括航班分配的整个
快照。
2. If all check in counters get unconfirmed still a
message is needed to indicate that the flight has
no confirmed check in counter.
如果所有值机柜台都被取消确认，一个消息会被
发送，标志该航班没有确认的柜台。
3. Check in counter assignments for a mixed flight
will be communicated in same check in counter
message. Each such assignment will identify the
D/I allocation of resource.
一个混合航班的值机柜台将在同一个值机柜台消
息中。每个分配将带有D/I标识分配的资源。
4. RMS will send counter separate events for
master and code share.
RMS将为主航班和代码共享分别发送事件。
5. RMS will support a single character for class
based allocations in CCLS field for Counters i.e.
if a counter can accept any class passenger an
X needs to be used instead of combination like
FC etc
RMS将根据CCLS字段支持一个字符的等级。例
如，一个柜台可以支持任何等级的旅客，使用X
而不是如FC这样的组合。
```
<a id="sec-4-1-2"></a>
#### 4.1.2 Event Message Format/事件消息格式
```text
Refer format under AODBCKDT event. The format is the same as AODBCKDT event,
except the message sender SNDR in the meta header section will be set to RMS.
Further the optional fields COTM and CCTM will not be sent by RMS since RMS is the
not source for these values.
参见AODBCKDT事件的格式。格式与AODBCKDT事件相同，除了头部的发送者SNDR
被设置为RMS。COTM和CCTM字段不会被RMS发送由于RMS不是这些值的源。
```
<a id="sec-4-1-3"></a>
#### 4.1.3 Event Message Sample/事件消息例子
Refer sample under AODBCKDT event, except the SNDR will be set to RMS and the
fields COTM, CCTM will be absent in the message sent from RMS.
参见AODBCKDT事件的例子出了SNDR将是RMS并且RMS发送的消息不会有COTM和
CCTM标签。
<a id="sec-4-2"></a>
### 4.2 RMS flight carousel event/ RMS 航班行李转盘事件
<a id="sec-4-2-1"></a>
#### 4.2.1 Event Attributes/事件属性
```text
Message Code RMSCLDT
消息代码
Event Description This is triggered whenever RMS needs to send flight
事件描述 carousel assignments including timing changes to
AODB.
当 RMS 中一个航班的行李提取转盘相关数据修改时（包
括时间修改），发生该事件。
Single Recipient Yes
接收者 是
Frequency Unscheduled, triggered by carousel assignment in RMS.
频率 非计划的，RMS 中航班行李提取转盘数据改变时触发。
Reasons for carousel assignment include:
行李提取转盘数据修改的原因有：
RMS operator confirms a carousel allocation within
RMS.
RMS 操作员在 RMS 中确认了一个行李提取转盘分配。
RMS operator unconfirms a previously confirmed
carousel allocation within RMS.
RMS 操作员在 RMS 中取消了一个行李提取转盘之前的确
认。
RMS operator manually changes the carousel
occupancy timings for previously confirmed carousel
allocations for a flight.
RMS 操作员手动改变一个已经确认的行李提取转盘的占
用时间。
RMS system automatically changes the carousel
occupancy timings for previously confirmed carousel
allocations for a flight.
RMS 系统自动为一个已经确认的行李提取转盘修改行李
提取转盘占用时间。
Data Range This is sent out only if the flight carousel data is changed
数据范围 for a flight within RMS operational window (which
may/may not map to typical AODB window of 48 hours)
Latest snapshot of all carousel related data for a flight
should be included.
航班行李提取转盘事件仅当航班建立的计划操作日期在
RMS 当 前 操 作 窗 口 内 的 若 干 小 时 （ 可 能 也 可 能 不 和
AODB 通常的 48 小时时间窗匹配）中发出。
Data Count One or more flight carousel assignment records in single
数据数 XML message.
包括一个航班中所有相关的行李提取转盘数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments 1. All carousel assignments for a flight are to be
注释 sent with each change. This is so that any
carousel message from RMS will contain
complete snapshot of all carousels currently
confirmed for that flight in RMS.
每一次修改都会发送航班的整个行李提取转盘分
配。也就是说RMS发送的消息将包括航班分配的
整个快照。
2. If all carousels get unconfirmed still a message
is needed to indicate that the flight has no
confirmed carousel.
如果所有行李提取转盘都被取消确认，一个消息
会被发送，标志该航班没有确认的行李提取转
盘。
3. Carousel assignments for a mixed flight will be
communicated in same carousel message. Each
such assignment will identify the D/I allocation of
resource.
一个混合航班的行李提取转盘将在同一个行李提
取转盘消息中。每个分配将带有D/I标识分配的资
源。
4. RMS will send separate carousel events for
master and code share.
RMS将为主航班和代码共享分别发送事件。
5. RMS does not support class based allocation for
carousels. Since BCLS field is mandatory RMS
will always send X in this field.
RMS不支持行李提取转盘按等级分配。由于
BCLS是强制字段，RMS永远发X在这个字段。
```
<a id="sec-4-2-2"></a>
#### 4.2.2 Event Message Format/事件消息格式
```text
Refer format under AODBCLDT event. The format is the same as AODBCLDT event,
except the message sender SNDR in the meta header section will be set to RMS.
Further the optional fields FBAG and LBAG will not be sent by RMS since RMS is the
not source for these values.
参见AODBCLDT事件的格式。格式与AODBCLDT事件相同，除了头部的发送者SNDR被
设置为RMS。FBAG和LBAG字段不会被RMS发送由于RMS不是这些值的源。
```
<a id="sec-4-2-3"></a>
#### 4.2.3 Event Message Sample/事件消息例子
Refer sample under AODBCLDT event, except the SNDR will be set to RMS and the
fields FBAG, LBAG will be absent in the message sent from RMS.
参见AODBCLDT事件的例子出了SNDR将是RMS并且RMS发送的消息不会有FBAG和
LBAG标签。
<a id="sec-4-3"></a>
### 4.3 RMS flight gate event/ RMS 航班登机门事件
<a id="sec-4-3-1"></a>
#### 4.3.1 Event Attributes/事件属性
```text
Message Code RMSGTDT
消息代码
Event Description This is triggered whenever RMS needs to send flight
事件描述 gate assignments including timing changes to AODB.
当 RMS 中一个航班的行李提取转盘相关数据修改时（包
括时间修改），发生该事件。
Single Recipient Yes
接收者 是
Frequency Unscheduled, triggered by gate assignment in RMS.
频率 非计划的，RMS 中航班登机门分配改变时触发。
Reasons for gate assignment include:
登机门数据修改的原因有：
RMS operator confirms a gate allocation within RMS.
RMS 操作员在 RMS 中确认了一个登机门分配。
RMS operator unconfirms a previously confirmed gate
allocation within RMS.
RMS 操作员在 RMS 中取消了一个登机门之前的确认。
RMS operator manually changes the gate occupancy
timings for previously confirmed gate allocations for a
flight.
RMS 操作员手动改变一个已经确认的登机门的占用时
间。
RMS system automatically changes the gate occupancy
timings for previously confirmed gate allocations for a
flight.
RMS 系统自动为一个已经确认的登机门修改登机门占用
时间。
Data Range This is sent out only if the flight gate data is changed for
数据范围 a flight within RMS operational window (which may/may
not map to typical AODB window of 48 hours).
Latest snapshot of all gate related data for a flight should
be included.
航班登机门事件仅当航班建立的计划操作日期在 RMS 当
前操作窗口内的若干小时（可能也可能不和 AODB 通常
的 48 小时时间窗匹配）中发出。
Data Count One or more flight gate assignment records in single
数据数 XML message.
包括一个航班中所有相关的登机门数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments 1. All gate assignments for a flight are to be sent
注释 with each change. This is so that any gate
message from RMS will contain complete
snapshot of all gates currently confirmed for that
flight in RMS.
每一次修改都会发送航班的整个登机门分配。也
就是说RMS发送的消息将包括航班分配的整个快
照。
2. If all gates get unconfirmed still a message is
needed to indicate that the flight has no
confirmed gates.
如果所有登机门都被取消确认，一个消息会被发
送，标志该航班没有确认的登机门。
3. All gate assignments for a mixed flight will be
communicated in same gate message. Each
such assignment will identify the D/I allocation of
resource.
一个混合航班的登机门将在同一个登机门消息
中。每个分配将带有D/I标识分配的资源。
4. When gate hierarchies are used to handle large
aircraft, RMS will send separate gate codes
known to AODB in the interface.
当登机门等级结构被用来处理大航空器的时候，
RMS将在接口中发送AODB理解的分别的登机门
代码。
5. RMS will send separate gate events for master
and code share.
RMS将为主航班和代码共享航班分别发送登机门
事件。
```
<a id="sec-4-3-2"></a>
#### 4.3.2 Event Message Format/事件消息格式
```text
Refer format under AODBGTDT event. The format is the same as AODBGTDT event,
except the message sender SNDR in the meta header section will be set to RMS.
Further the optional fields GOTM and GCTM will not be sent by RMS since RMS is the
not source for these values.
参见AODBGTDT事件的格式。格式与AODBGTDT事件相同，除了头部的发送者SNDR
被设置为RMS。GOTM和GCTM字段不会被RMS发送由于RMS不是这些值的源。
```
<a id="sec-4-3-3"></a>
#### 4.3.3 Event Message Sample/事件消息例子
<!-- 原 PDF 第 187 页 -->
Refer sample under AODBGTDT event, except the SNDR will be set to RMS and the
fields GOTM, GCTM will be absent in the message sent from RMS.
参见AODBGTDT事件的例子出了SNDR将是RMS并且RMS发送的消息不会有GOTM和
GCTM标签。
<a id="sec-4-4"></a>
### 4.4 RMS flight planned stand event/ 事件
<a id="sec-4-4-1"></a>
#### 4.4.1 Event Attributes/事件属性
```text
Message Code RMSPSDT
消息代码
Event Description This is triggered whenever RMS needs to send flight
事件描述 stand assignments including timing changes to AODB.
当 RMS 中一个航班的停机位相关数据修改时（包括时间
修改），发生该事件。
Single Recipient Yes
接收者 是
Frequency Unscheduled, triggered by stand assignment in RMS.
频率 非计划的，RMS 中航班停机位数据改变时触发。
Reasons for stand assignment include:
停机位数据修改的原因有：
RMS operator confirms a stand allocation for a flight
within RMS.
RMS 操作员在 RMS 中确认了一个停机位分配。
RMS operator unconfirms a previously confirmed stand
allocation for a flight within RMS.
RMS 操作员在 RMS 中取消了一个停机位之前的确认。
RMS operator manually changes the parking stand
occupancy timings for previously confirmed stand
allocations for a flight.
RMS 操作员手动改变一个已经确认的停机位的占用时
间。
RMS system automatically changes the parking stand
occupancy timings for previously confirmed stand
allocations for a flight.
RMS 系统自动为一个已经确认的停机位修改停机位占用
时间。
Data Range This is sent out only if the flight stand data is changed
数据范围 for a flight within RMS operational window (which
may/may not map to typical AODB window of 48 hours).
Latest snapshot of all planned stand allocation related
data for a flight should be included.
航班停机位事件仅当航班建立的计划操作日期在 RMS 当
前操作窗口内的若干小时（可能也可能不和 AODB 通常
的 48 小时时间窗匹配）中发出。
Data Count One or more flight planned stand allocation records in
数据数 single XML message.
包括一个航班中所有相关的停机位数据。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments 1. All planned stand assignments for a flight are to
注释 be sent with each change. This is so that any
planned stand message from RMS will contain
complete snapshot of all planned stands
currently confirmed for that flight in RMS.
每一次修改都会发送航班的整个停机位分配。也
就是说RMS发送的消息将包括航班分配的整个快
照。
2. If all planned stands get unconfirmed still a
message is needed to indicate that the flight has
no confirmed planned stands.
如果所有停机位都被取消确认，一个消息会被发
送，标志该航班没有确认的停机位。
3. Planned stand assignments for a mixed flight
will be communicated in same planned stand
message.
一个混合航班的停机位将在同一个停机位消息
中。每个分配将带有D/I标识分配的资源。
4. RMS will send separate planned stand events
for master and code share.
RMS将为主航班和代码共享分别发送事件。
5. Conflict zone defined using conflict rules will not
be sent to AODB from RMS. RMS can only send
the stand allocations as visible in the Gantt chart
not the virtual timings.
利用冲突规则定义的冲突区域不会被RMS发送给
AODB。RMS只能发送甘特图中的停机位分配而
不是虚拟时间。
```
<a id="sec-4-4-2"></a>
#### 4.4.2 Event Message Format/事件消息格式
```text
Refer format under AODBPSDT event. The format is the same as AODBPSDT event,
except the message sender SNDR in the meta header section will be set to RMS.
参见AODBPSDT事件的格式。格式与AODBPSDT事件相同，除了头部的发送者SNDR
被设置为RMS。
```
<a id="sec-4-4-3"></a>
#### 4.4.3 Event Message Sample/事件消息例子
Refer sample under AODBPSDT event, except the SNDR will be set to RMS.
参见AODBPSDT事件的例子除了SNDR将是RMS。
<a id="sec-4-5"></a>
### 4.5 RMS flight chute event/ RMS 航班行李传送带事件
<a id="sec-4-5-1"></a>
#### 4.5.1 Event Attributes/事件属性
```text
Message Code RMSCHDT
消息代码
Event Description This is triggered whenever RMS needs to send flight
事件描述 chute assignments to AODB.
当 RMS 需要向 AODB 发送航班行李传送带时触发。
Single Recipient Yes
接收者 是
Frequency Unscheduled, triggered by chute assignment in RMS.
频率 非计划的，在 RMS 发送航班行李传送带时触发。
Reasons for chute assignment include:
分配行李传送带的原因有：
RMS operator confirms a chute allocation within RMS.
RMS 操作员在系统中确认行李传送带的分配。
RMS operator unconfirms a previously confirmed chute
allocation within RMS.
RMS 操作员在系统中取消一个行李传送带分配的确认。
RMS operator changes the chute open/chute close
timings in RMS
RMS 操作员在系统中修改一个行李传送带的打开/关闭时
间。
Data Range This is sent out only if the flight chute data is changed
数据范围 for a flight which is scheduled for operation within the
current operational window of „x‟ hours (typically next 48
hours).
Latest snapshot of all chute related data for a flight
should be included.
Baggage status specific sort destination (e.g. for late
bags) are not reported to AODB from RMS since these
are not flight specific.
航班行李传送带修改事件仅当航班建立的计划操作日期在
当前操作窗口内的若干小时（通常是 48 小时内）中发
出。
包括一个航班行李传送带的所有数据。
行李状态的详细分类目的地（如迟到行李）不向 AODB
发送，因为这些不包括在航班明细里。
Data Count One or more flight chute assignment records in single
数据数 XML message.
一条 XML 报文中包括一个或多个航班行李传送带分配记
录。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment Yes
确认 是
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments 1. All chute assignments for a flight are to be sent
注释 with each change. This is so that any chute
message from RMS will contain complete
snapshot of all chutes currently confirmed for
that flight in RMS.
一个航班的所有行李传送带分配每次修改都会发送。
RMS中发送的任何传送带报文都包括当前航班确认的
所有行李传送带信息。
2. If all chutes get unconfirmed still a message is
needed to indicate that the flight has no
confirmed chute.
如果所有的行李传送带分配取消，还要再发送一条报
文表示航班无确认的行李传送带。
3. Chute assignments for a mixed flight will be
communicated in same chute message.
混合航班的行李传送带分配在同一条报文中发送。
4. RMS will send a single event when the same
chute is allocated for both master and code
share. AODB will internally copy it to both
master and code share records within AODB. If
RMS operator allocates a separate resource for
code shares (different from master flight), RMS
will separate events for code share flight which
will update the code share flight alone in AODB.
对主航班和代码共享航班，RMS只发送一条事件。
AODB自己在内部为主航班和代码共享航班复制信
息。若RMS为代码共享航班分配的传送带不同，
RMS单独发送代码共享航班的行李传送带事件。
```
<a id="sec-4-5-2"></a>
#### 4.5.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M FLOP
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(4) M CHDT
data section.
消息发送的子类型. Meta Data段的一部
分.
FLOP Identifies start of the operational data. - M This starts a section.
操作数据的开始标识 一个新段落的开始
FLID Unique AODB ID for identifying a flight Number(1-12) M
AODB中唯一的航班ID
FFID Friendly flight Id for easy identification. Char(20-32) M Formed by concatenating
航班ID别名，便于辨别 following fields of
AODBSCHD message in
order namely
ALCD, FLNO, MVIN,
SODT, FLIN
格式为AODBSCHD报文
中相关的字段顺序，
ALCD, FLNO, MVIN,
SODT, FLIN
CHDT Has a parameter CHNO to identify the Number(1) P This starts a chute
chute number associated with flight section and includes
which has multiple chute allocations. chute specific information
This data repeats for each chute of a as below. An empty TAG
flight. will be sent for a flight
分配了多行李传送带的航班带有参数 with previous chute
CHNO表示传送带号。航班的每个传送 allocations to signify
there are no chute
带中重复出现。
allocations now.
一个行李传送带段落的开
始包括传送带的详情。空
表示航班已分配但现在未
分配。
CHUT This is the baggage chute allocated for Char(1-8) M Chute code reference
XML Tag Description Format Req Values
a departure flight. table to be decided by
离港航班分配的行李传送带 CDIA
根据成都机场的行李传送
带参考数据表。
CCLS Chute class Char(1) M Following class codes will
行李传送带等级 be supported:
支持如下等级代码
F = First class/头等
C = Business class/商务
Y = Economy class/经济
X = No specific class/全
部
If more than one class
can be used for chute
allocationon a single
chute, CHDT will be
repeated for each class.
如果一个行李传送带可被
用于多个等级的行李传送
带分配，那么CHDT将为
每个等级重复一次。
PCBT Planned time for chute start usage for Char(11) M DDMONYYHHMM
flight Local time 24 hr format
航班行李转盘计划开始使用时间 当地时间24小时格式
PCET Planned time for chute end usage for Char(11) M DDMONYYHHMM
flight Local time 24 hr format
航班行李转盘计划结束使用时间 当地时间24小时格式
CBTM Actual Time when the flight started Char(11) O DDMONYYHHMM
using the chute Local time 24 hr format
航班实际开始使用传送带时间 当地时间24小时格式
CETM Actual Time when the flight stopped Char(11) O DDMONYYHHMM
using the chute Local time 24 hr format
航班实际结束使用传送带时间 当地时间24小时格式
CTYP Domestic or International indicator of Char(1) M D – Domestic/国内
chute resource I – International/国际
传送带资源的国内国际标志
```
<a id="sec-4-5-3"></a>
#### 4.5.3 Event Message Sample/事件消息例子
Refer sample under AODBCHDT event, except the SNDR will be set to RMS.
参见AODBCHDT事件的例子除了SNDR将是RMS。
<a id="sec-4-6"></a>
### 4.6 RMS reference data request event/ RMS 参数请求事件
<!-- 原 PDF 第 193 页 -->
<a id="sec-4-6-1"></a>
#### 4.6.1 Event Attributes/事件属性
```text
Message Code RMSRQRD
消息代码
Event Description This is sent whenever RMS wants a fresh copy of
事件描述 reference data like airlines, airports etc from AODB.
当 RMS 要从 AODB 中更新参数如航空公司、机场等时发
送该事件。
Single Recipient Yes
接收者 是
Frequency Unscheduled, triggered by RMS operator action to
频率 request a reference data download from AODB.
非计划的，RMS 操作员发出从 AODB 中下载参数时触
发。
Data Range NA
数据范围 无
Data Count Single reference data request record in single XML
数据数 message.
在一个 XML 报文中包括一条参数请求记录。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments RMS should send one outstanding reference data
注释 request at a time, as each request is responded by
AODB.
Since extracting and sending reference is an intense
operation that may impact normal operational
messages, RMS to ensure not too many outstanding
reference data request messages are sent continuously.
RMS一次发送一条参数请求，得到AODB的响应。
由于抽取发送参数是一种大数据量操作，有可能影响正常
的报文，RMS确保不连续发送大批的参数请求。
```
<a id="sec-4-6-2"></a>
#### 4.6.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M RQRD
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(4) M Type of reference data
data section. required by RMS.
消息发送的子类型. Meta Data段的一部 RMS请求的典型数据
分. COUL = Country codes/
国家代码
ARPT = Airport codes/机
场代码
AIRL = Airline codes/航空
公司代码
AIRC = Aircraft types/机
型
REGN = Registrations/机
号
ORGN = Organizations/
机构
FLTL = Flight types/航班
类型
TLST = Terminal codes/
航站楼代码
SLST = Stand codes/机
位代码
CLST = Counter codes/
柜台代码
GLST = Gate codes/登机
门代码
BLST = Carousel codes/
行李提取转盘代码
CHLT = Chute codes/行
李传送带代码
RSTA = Resource status/
资源状态
RQRD Identifies start of the request reference - M This starts a section. This
data information information. will be an empty TAG.
请求参数信息的开始 新段落的开始。是个空标
签。
RTYP Type of resource Char(4) O Specify resource type
资源类型 when the STYP is RSTA.
在STYP为RSTA时指定资
XML Tag Description Format Req Values
源类型。
```
<a id="sec-4-6-3"></a>
#### 4.6.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>RMS</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>RQRD</TYPE>
<STYP>AIRL</STYP>
</META>
<RQRD>
<RTYP>AIRL</RTYP>
</RQRD>
</MSG>
```
<a id="sec-4-7"></a>
### 4.7 RMS daily schedule request event/ RMS 日航班计划请求事件
<a id="sec-4-7-1"></a>
#### 4.7.1 Event Attributes/事件属性
```text
Message Code RMSRQFD
消息代码
Event Description This is sent whenever RMS wants a fresh copy of daily
事件描述 schedule from AODB.
当 RMS 要从 AODB 中更新日时刻表时发送该事件。
Single Recipient Yes
接收者 是
Frequency Unscheduled, triggered by RMS operator action to
频率 request a daily schedule download from AODB.
非计划的，RMS 操作员发出从 AODB 中下载日时刻表时
触发。
Data Range Facility to retrieve messages by date range is provided.
数据范围 根据请求的日期范围。
Data Count Single daily schedule request record in single XML
数据数 message.
一条 XML 报文中包括一条日时刻表请求记录。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments RMS should send one outstanding daily schedule
注释 request at a time, as each request is responded by
AODB.
Since extracting and sending daily schedule is an
intense operation that may impact normal operational
messages, RMS to ensure not too many outstanding
daily schedule request messages are sent continuously.
RMS一次发送一条参数请求，得到AODB的响应。
由于抽取发送参数是一种大数据量操作，有可能影响正常
的报文，RMS确保不连续发送大批的参数请求。
```
<a id="sec-4-7-2"></a>
#### 4.7.2 Event Message Format/事件消息格式
```text
XML Tag Description Format Req Values
TYPE Type of message sent. Part of meta Char(4) M RQFD
data section.
消息发送类型。Meta Data段的一部
分。
STYP Subtype of message sent. Part of meta Char(4) M NONE
data section.
消息发送的子类型. Meta Data段的一部
分.
RQFD Identifies start of the request flight - M This starts a section.
information. 新段落的开始
请求航班信息的开始标志
STDB Filter criteria indicating all daily Char(11) O DDMONYYHHMM
schedule records with schedule time of When more than one
operation (STA or STD) after or equal parameter is specified,
to this date time are to be retrieved. they will be treated with
请求日时刻表记录的筛选标准，只调用 AND condition.
大于或等于该日期（STA或STD）的记 When none of the
录。 parameters are specified,
XML Tag Description Format Req Values
AODB will return all of
current day‟s records (as
it would while generating
an unsolicited daily
schedule from AODB).
有多个参数时，认为是
“与”条件。
无参数时，AODB返回当
天所有的记录（就如同
AODB发送的日计划）。
STDE Filter criteria indicating all daily Char(11) O DDMONYYHHMM
schedule records with schedule time of
operation (STA or STD) before or
equal to this date time are to be
retrieved.
请求日时刻表记录的筛选标准，只调用
小于或等于该日期（STA或STD）的记
录。
ETDB Filter criteria indicating all daily Char(11) O DDMONYYHHMM
schedule records with estimated time
of operation (ETA or ETD) after or
equal to this date time are to be
retrieved.
请求日时刻表记录的筛选标准，只调用
大于或等于该日期（ETA或ETD）的记
录。
ETDE Filter criteria indicating all daily Char(11) O DDMONYYHHMM
schedule records with estimated time
of operation (ETA or ETD) before or
equal to this date time are to be
retrieved.
请求日时刻表记录的筛选标准，只调用
小于或等于该日期（ETA或ETD）的记
录。
```
<a id="sec-4-7-3"></a>
#### 4.7.3 Event Message Sample/事件消息例子
```xml
<?xml version="1.0" encoding="UTF-8"?>
<MSG xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation = “unisysaodbsis.xsd”>
<META>
<SNDR>RMS</SNDR>
<SEQN>1243</SEQN>
<DTTM>20021010090311</DTTM>
<TYPE>RQFD</TYPE>
<STYP>NONE</STYP>
</META>
<RQFD>
<STDB>12JAN041730</STDB>
</RQFD>
</MSG>
```
<a id="sec-4-8"></a>
### 4.8 RMS error to AODB event/ RMS 发送给 AODB 的错误信息事件
<a id="sec-4-8-1"></a>
#### 4.8.1 Event Attributes/事件属性
```text
Message Code RMSEROR
消息代码
Event Description This is triggered whenever RMS needs to send an error
事件描述 message to AODB.
当 RMS 需要向 AODB 发送一个错误信息时发生。
Single Recipient Yes
接收者 是
Frequency Unscheduled, triggered by error handling in RMS.
频率 非计划的，RMS 中错误处理时触发。
Reasons for error event send include:
错误事件发送的原因有：
RMS finds an error in the input message/format/content
from AODB.
RMS 从 AODB 中发现输入的报文/格式/内容错误。
RMS cannot logically process the message from AODB
due to business logic conflict.
RMS 收到 AODB 的报文无法处理，与商业流程冲突。
RMS cannot process the message from AODB due to
internal RMS error.
由于内部错误，RMS 无法处理收到的 AODB 报文。
Data Range Not Applicable.
数据范围 不适用
Data Count Single error record in single XML message. Multiple
数据数 errors are conveyed as separate events.
一个 XML 报文中包括一条错误记录。多个错误分开成多
个事件。
Data Conversion None
数据转换 无
Sort Sequence None
排列序列号 无
Acknowledgment None
确认 无
Priority High
优先级 高
Expiry 120 minutes
过期 120 分钟
Message Fragmentation None
消息分段 无
Encoding UTF 8
编码
Time Beijing local time
时间 北京当地时间
Comments None
注释 无
Processing Exceptions RMS cannot send AODB‟s TYPE/STYP/SEQN in the
处理例外 TYPS, STYS and SEQS fields respectively. So RMS will
send repeat of first 200 chars of erroneous AODB
message in ETEX. So the mandatory fields will be
preset to following in RMS EROR messages.
RMS不能在TYPS、STYS和SEQS字段发送AODB的
TYPE/STYP/SEQN。所以RMS将在发给AODB消息的
ETEX字段中发送前200个字符。所以强制字段在RMS
EROR消息如下：
TYPS = EROR
STYS = NONE
SEQS = 0
```
<a id="sec-4-8-2"></a>
#### 4.8.2 Event Message Format/事件消息格式
```text
Refer format under AODBERORRMS event. The format is the same as
AODBERORRMS event, except the message sender SNDR in the meta header section
will be set to RMS. Other header values like SEQS, TYPS will correspond to the source
message from AODB during processing of which the error was found.
参考AODBERORRMS事件格式。这个格式与AODBERORRMS事件相同，只是meta头
部分由SNDR换成RMS。其他的值如SEQS, TYPS对应AODB中错误发生的原报文。
```
<a id="sec-4-8-3"></a>
#### 4.8.3 Event Message Sample/事件消息例子
Refer sample under AODBERORRMS event, except the SNDR will be set to RMS. See
exceptions above.
参考AODBERORRMS事件格式，只是SNDR换成RMS。见上面的异常处理。
<!-- 原 PDF 第 200 页 -->
<a id="sec-5"></a>
## 5 AODB Exception Handling/AODB异常处理
<a id="sec-5-1"></a>
### 5.1 Application Errors/应用程序错误
```text
SNO Exception Type Handling Description
异常类型 处理描述
1. XML parse error Means the XML from RMS cannot be parsed correctly
XML 解析错误 either because of incorrect format or because of invalid
value in one of the TAGs (parsing matched against the
AODB published XSD)
表示由于错误格式或非法的TAG值（按照AODB发布的
XSD），无法正确解析RMS的XML。
Will send error to RMS
发送错误给RMS。
Will not process message
不处理报文。
2. Invalid Type Means XML can be parsed but the TYPE is not expected
非法类型 from RMS.
表示可以解析 XML，但RMS的 TYPE 非法。
Will send error to RMS
发送错误给RMS。
Will not process message
不处理报文。
3. Invalid Subtype Means XML can be parsed but the STYP is not expected
非法子类型 from RMS.
表示可以解析 XML，但RMS的 STYP 非法。
Will send error to RMS
发送错误给RMS。
Will not process message
不处理报文。
4. Invalid TAG Means XML can be parsed but some additional TAG not
非法标签 expected from RMS is encountered.
表示可以解析 XML，但RMS的一些附加标签非法。
Will send error to RMS
发送错误给RMS。
Will ignore the TAG and process rest of message
忽略该标签，处理其余的报文。
5. Invalid Value Means XML can be parsed but some TAG contains a
非法值 data value not expected by AODB (including not passing
XSD validation) or not passing the reference data
validation.
表示可以解析 XML，但一些标签的值 AODB 认为非法 (包
括无法通过 XSD 校验) 或无法通过参考数据的合法性检
SNO Exception Type Handling Description
异常类型 处理描述
查。
Will send error to RMS
发送错误给RMS。
Will not process message
不处理报文。
6. Business error Means XML can be parsed but AODB encountered a
业务错误 business logic problem processing the message.
表示可以解析XML，处理该报文时，AODB发生业务错
误。
Will send error to RMS
发送错误给RMS。
Will not process message
不处理报文。
7. Internal error Means AODB encountered an unexpected error problem
内部错误 processing the message.
AODB 处理报文时碰到意外错误。
Will send error to RMS
发送错误给RMS。
Will not process message
不处理报文。
```
<a id="sec-5-2"></a>
### 5.2 Connection Failures/连接失败
```text
SNO Failure Type Handling Description
失败类型 处理描述
1. Level 1 AODB disconnected from CIIMS (or AODB shutdown) for
1级 less than 120 minutes and restarted.
AODB与CIIMS断开（或AODB关机）小于120分钟并重启。
AODB will connect and receive buffered messages from
CIIMS.
AODB与CIIMS连接并接收缓冲的报文。
RMS will receive latest messages from CIIMS once AODB
is started.
AODB重启后，RMS接收CIIMS的最新报文。
No other error special handling is expected.
无其他错误特殊处理。
2. Level 2 AODB disconnected from CIIMS (or AODB shutdown) for
2级 more than 120 minutes but less than 480 minutes.
AODB与CIIMS断开（或AODB关机）大于120分钟但小于
480分钟。
AODB cannot send/receive all buffered messages from
CIIMS as some messages would have expired.
SNO Failure Type Handling Description
失败类型 处理描述
AODB无法发送/接收CIIMS所有的缓冲报文，一些报文会过
期。
Operator will disconnect RMS connection to CIIMS.
操作员断开RMS与CIIMS的连接。
Operator will clear all messages from RMS to AODB from
CIIMS queues.
操作员从CIIMS队列中清除所有RMS发送AODB的报文。
Operator will clear all messages from AODB to RMS from
CIIMS queues.
操作员从CIIMS队列中清除所有AODB发送RMS的报文。
Operator will connect AODB to CIIMS and send request for
latest flight resource allocations from AODB to RMS.
操作员连接AODB与CIIMS，从AODB向RMS发送最新的航
班资源分配请求。
Operator will connect RMS to CIIMS so RMS can respond
with latest flight resource allocations.
操作员连接RMS和CIIMS，RMS则可以响应最新的航班资源
分配信息。
Operator will send download request of latest flight
schedule from AODB to RMS.
操作员从AODB向RMS发送下载最新航班时刻表的请求。
Reference data messages have an expiry of 480 minutes
and hence do not need special handling.
参考数据报文有一个480分钟有效期，所以不需要特殊处
理。
3. Level 3 AODB disconnected from CIIMS (or AODB shutdown) for
3级 more than 480 minutes.
AODB与CIIMS断开（或AODB关机）大于480分钟。
Same as above. In addition operator will send download of
relevant reference data items from AODB to RMS.
同上。另外，操作员发送从AODB向RMS下载相关的参考数
据的请求。
```
<a id="sec-5-3"></a>
### 5.3 System Operations Logging/系统操作日志
AODB will have a separate interface with ITOMS system for logging critical events and
errors. These are covered in a different specification.
AODB与ITOMS系统有单独的接口来记录关键事件日志和错误。不在本文档范围。
<!-- 原 PDF 第 203 页 -->
<a id="sec-6"></a>
## 6 RMS Exception Handling/RMS 异常处理
<a id="sec-6-1"></a>
### 6.1 Application Errors/应用程序错误
```text
SNO Exception Type Handling Description
异常类型 处理描述
1. XML parse error Means the XML from AODB cannot be parsed correctly
XML 解析错误 either because of incorrect format or because of invalid
value in one of the TAGs (parsing matched against the
AODB published XSD)
表示由于错误格式或非法的TAG值（按照AODB发布的
XSD），无法正确解析AODB的XML。
Will send error to AODB
发送错误给AODB。
Will not process message for FLOP or other discrete
single record events.
不处理FLOP报文或其他零散的单个记录。
Will partially process non erroneous records for SCHD,
SCHD or other list record reference data events.
Erroneous records will be ignored.
部分处理没错误的SCHD记录或其他参考数据事件。
忽略错误记录。
Messages that do not validate successfully against the
AODB published XSD will be rejected entirely.
无法成功通过AODB发布的XSD校验的消息将被整体丢
弃。
2. Invalid Type Means XML can be parsed but the TYPE is not expected
非法类型 from AODB.
表示可以解析 XML，但 AODB 的 TYPE 非法。
Will send error to AODB
发送错误给AODB。
Will not process message
不处理报文。
3. Invalid Subtype Means XML can be parsed but the STYP is not expected
非法子类型 from AODB.
表示可以解析 XML，但 AODB 的 STYP 非法。
Will send error to AODB
发送错误给AODB。
Will not process message
不处理报文。
4. Invalid TAG Means XML can be parsed but some additional TAG not
非法标签 expected from AODB is encountered.
表示可以解析 XML，但AODB的一些附加标签非法。
SNO Exception Type Handling Description
异常类型 处理描述
Will send error to AODB
发送错误给AODB。
Will ignore the TAG and process rest of message
忽略该标签，处理其余的报文。
5. Invalid Value Means XML can be parsed but some TAG contains a
非法值 data value not expected by RMS (including not passing
XSD validation) or not passing the reference data
validation.
表示可以解析 XML，但一些标签的值RMS认为非法（包
括无法通过 XSD 校验）或无法通过参考数据合法性检
查。
Will send error to AODB
发送错误给AODB。
Will not process message for FLOP or other discrete
single record events.
不处理FLOP报文或其他零散的单个记录。
Will partially process non erroneous records for SCHD,
SCHD or other list record reference data events.
Erroneous records will be ignored.
部分处理没错误的SCHD记录或其他参考数据事件。
忽略错误记录。
6. Business error Means XML can be parsed but RMS encountered a
业务错误 business logic problem processing the message.
表示可以解析XML，但处理该报文时，RMS发生业务错
误。
Will send error to AODB
发送错误给AODB。
Will not process message
不处理报文。
7. Internal error Means RMS encountered an unexpected error problem
内部错误 processing the message.
RMS处理报文时碰到意外错误。
Will send error to AODB
发送错误给AODB。
Will not process message
不处理报文。
```
<a id="sec-6-2"></a>
### 6.2 Connection Failures/连接失败
```text
SNO Failure Type Handling Description
失败类型 处理描述
1. Level 1 RMS disconnected from CIIMS (or RMS shutdown) for less
1级 than 120 minutes and restarted.
SNO Failure Type Handling Description
失败类型 处理描述
RMS与CIIMS断开（或RMS关机）小于120分钟并重启。
RMS will connect and receive buffered messages from
CIIMS.
RMS与CIIMS连接并接收缓冲的报文。
AODB will receive latest messages from CIIMS once RMS
is started.
RMS重启后，AODB接收CIIMS的最新报文。
No other error special handling is expected.
无其他错误特殊处理。
2. Level 2 RMS disconnected from CIIMS (or RMS shutdown) for
2级 more than 120 minutes but less than 480 minutes. .
RMS与CIIMS断开（或RMS关机）大于120分钟但小于480分
钟。
RMS cannot send/receive all buffered messages from
CIIMS as some messages would have expired.
RMS无法发送/接收CIIMS所有的缓冲报文，一些报文会过
期。
Operator will clear all messages from AODB to RMS from
CIIMS queues.
操作员从CIIMS队列中清除所有AODB发送RMS的报文。
Operator will connect RMS to CIIMS so RMS can respond
with latest flight resource allocations.
操作员连接RMS和CIIMS，RMS则可以响应最新的航班资源
分配信息。
Operator will send download request of latest flight
schedule from AODB to RMS.
操作员从AODB向RMS发送下载最新航班时刻表的请求。
Reference data messages have an expiry of 480 minutes
and hence do not need special handling.
参考数据报文有一个480分钟有效期，所以不需要特殊处
理。
3. Level 3 RMS disconnected from CIIMS (or RMS shutdown) for
3级 more than 480 minutes.
RMS与CIIMS断开（或RMS关机）大于480分钟。
Same as above. In addition operator will send download of
relevant reference data items from AODB to RMS.
同上。另外，操作员发送从AODB向RMS下载相关的参考数
据的请求。
```
<a id="sec-6-3"></a>
### 6.3 System Operations Logging/系统操作日志
RMS should have its own logging system for logging critical events and errors.
RMS应有自己的日志系统来记录关键事件的日志和错误。
---
## 整理说明
本版本已移除原 PDF 的重复页眉、页脚与目录页，并将正文重排为连续的 Markdown 章节。为避免技术字段在转换时发生列错位，字段定义、消息格式及异常处理表保留为等宽文本；XML 报文样例则使用 XML 代码块。在非技术代码块的原始页面起始处保留了不可见的 HTML 注释页码，以便与 PDF 互相核对；跨页字段表和 XML 样例不会被分页标记中断。
<!-- 生成统计：正文 Markdown 标题 268 个；XML 样例 44 个；PDF 总页数 205 页。 -->
Reference in New Issue View Git Blame Copy Permalink