vb航空公司管理系统

界面使用了XpEngine 控件美化了, 据得还不错,截下几张图片看看

the following information comes from 3q2008.com

Ticket Servers for Network Traffic Prioritization
Cory C. Beard1,3 and Victor S. Frost2
For broadband packet networks to be widely useful to society, they must dynamically
recognize some network flows, like those that deal with disaster response, military operations,
or emergencies as having greater importance than others. This paper proposes
an architecture of geographically distributed ticket servers that issue importance tickets
that indicate the priority that a flow should be given in the current dynamic network
context. Any type of user or flow can be given priority, depending on the user needs and
the context. User agents contact ticket servers using an agent communication language;
then a ticket server intelligent agent determines how valuable of a ticket to issue. Use
of ticket servers and agent communication enables quick adaptation to dynamic context
changes and provides user feedback so that high priority communication activities can
be conducted effectively.
KEYWORDS: Priority; ticket servers; resource management; emergency management.
1. INTRODUCTION

the following information comes from 3q2008.com

Modern broadband data networks are being designed to integrate all types of
multimedia traffic. More important, however, they are designed to integrate and
support the activities of all types of users. As networks become more and more
useful to society, new types of users and user applications emerge, and people will
increasingly rely upon these networks to be available and reliable.
The user type of particular interest in this paper is the National Security/
Emergency Preparedness (NS/EP) user. Recent terrorist events in the United States
on September 11, 2001, have shown that telecommunication networks provide
tremendous value to society in response to disasters. However, these events have
also shown what is common with disaster response—that tremendous stress is
placed on these networks. In New York City, most notably the stress was on
1Computer Science/Electrical Engineering, University of Missouri-Kansas City, 5100 Rockhill Road,
Kansas City, Missouri 64110. E-mail: beardc@umkc.edu
2Electrical Engineering and Computer Science, University of Kansas, Lawrence, Kansas 66045. E-mail:
frost@eecs.ukans.edu

the following information comes from 3q2008.com

3To whom correspondence should be addressed.
151
1064-7570/03/0600-0151/0 C_2003 Plenum Publishing Corporation
152 Beard and Frost
wireless networks and the public switched telephone network (PSTN). The stress
came both from damaged facilities and network demand up to 400% more than
normal [1].
Of particular interest for this paper are multimedia communications and
applications over the public Internet. Aside from isolated problems with web
sites of news organizations, the Internet performed admirably after the events
of September 11 [2]. But it is anticipated that as convergence of voice and data
services occurs over the Internet in the near future, the same problems experienced
by telephone and wireless networks will increasingly be seen on the public
Internet.

the following information comes from 3q2008.com

NS/EP users currently use the public Internet for outreach, information sharing,
and electronic mail. However, use of the public Internet for mission-critical
activities is currently modest [3, 4]. Instead of using the public Internet for critical
functions, the NS/EP community depends more on specialized PSTN services,
like the Government Emergency Telecommunication Services (GETS) [4], and on
dedicated TCP/IP networks. The reliability and security of the public Internet is
considered inadequate for mission-critical functions, even though several applications
have been identified that could make valuable use of the public Internet [5],
such as coordination of response teams, applications to assess extent of damage,
and medical information and image exchange.

the following information comes from 3q2008.com

This paper specifically addresses the issue of network resource availability
for NS/EP network communications. It is common in NS/EP contexts for the
availability of network resources to be severely restricted in the aftermath of a major
event [6–9]. In some cases, demand on traditional telecommunications networks
has reached five times normal levels during the first day of an event [10]. Much
of the traffic demand, however, is for lower priority uses, such as people outside
a disaster area calling to see the status of loved ones [11]. Also, user behavior
can hamper disaster response. For example, with the Alfred P. Murrah Federal
Building Bombing in Oklahoma City in 1995, out-of-town media called emergency
operations centers and demanded to stay on the line until they could get information
([9], p. 356). Overloaded circuits also made it very difficult for off-duty emergency
workers to call the emergency command center when they received a page to come
help with the emergency.

the following information comes from 3q2008.com

Serving priority users in NS/EP situations involves providing a so-called
“emergency lane” for priority traffic [12] where important resource requests are
given priority access to network resources. This can be realized in many ways,
for example through using dedicated resources, policies to limit resource usage
by low priority users [13], or preemption of low priority users when no free capacity
is available. No such mechanisms are currently implemented in the public
Internet [3], however, although requirements for these mechanisms have been de-
fined in Recommendations by the ITU for the International Emergency Preference
Scheme (IEPS) [14] and International Emergency Multimedia Service (IEMS)
Ticket Servers for Network Traffic Prioritization 153
[15]. Substantial work has also been conducted by the Internet Emergency PreparednessWorking

the following information comes from 3q2008.com

Group of the Internet Engineering Task Force (IETF) [16, 17].
When resources are scarce, those users and user applications that are of
higher value or importance should be given greater access to resources (i.e., noncongested

the following information comes from 3q2008.com

network access). During congestion that occurs in normal conditions,
those of greater importance to network operators would be those which have
greater revenue-generating capability. During exceptional conditions like emergencies
or disasters, however, users and user applications of greatest importance
would likely be those which address danger to life and property. A mechanism
for prioritizing user traffic would therefore be valuable in both normal and exceptional
operating contexts. This work proposes a mechanism for doing just that.
Traffic management mechanisms to preferentially handle priority traffic are being
developed elsewhere [13–16]; this work addresses how those priority flows are
first identified and authorized.
1.1. Requirements

the following information comes from 3q2008.com

Exceptional conditions can occur suddenly and the context in which the network
would be operating would be highly dynamic. Effective administration of
priorities in such circumstances should meet the following requirements:
1. Dynamic context awareness—Users and user applications should be evaluated
in light of the current dynamic context. This would include not only
consideration of the presence of a crisis, but also phases of relief efforts
(i.e., search and rescue, medical relief, economic relief, etc.). During normal
operations, context awareness would entail knowledge of network
loading and traffic engineering constraints.
2. Ability for any user to potentially be considered high priority—A simple
approach to administering priorities would be to assign static priorities
based on user identity. This would not be sufficient during a crisis, however.
Network resource allocation should more closely match the E-911
paradigm where any user at any time could be experiencing or observing
an event which would warrant a high priority request for network
resources. Stories from recent disasters have talked about members of the
general public who were very useful at coordinating and observing disaster
response.

the following information comes from 3q2008.com

3. Transference of priorities across multiple network domains—Priority assignments
should be consistent across the multiple domains that a traffic
flow traverses. Users should not be required to obtain priorities separately
for each domain, nor should the differences in priority assignments
be significant between domains. While most of such capabilities would
likely be developed through contractual and trust arrangements between

the following information comes from 3q2008.com

航空公司管理信息系统的设计摘要
一个正常营运的航空公司需要管理所拥有的飞机、航线的设置、客户的信息等，更重要的还要提供票务管理。面对各种不同种类的信息，需要合理的数据库结构来保存数据信息以及有效的程序结构支持各种数据操作的执行。
本设计讲述如何建立一个航空公司管理信息系统。一般而言，航空公司的管理信息系统应该包括人事、工资管理模块 。
1 系统设计
1.1 系统功能分析
系统开发的总体任务是实现各种信息的系统化、规范化和自动化。
系统功能分析是在系统开发的总体任务的基础上完成。本例子中的航空公司管理信息系统需要完成功能主要有：
l 舱位信息的输入和修改，包括舱位等级编号、舱位等级名称、提供的各种服务类别，以及备注信息等。
l 客机信息的输入、修改和查询，包括客机编号、客机型号、购买时间、服役时间、经济舱座位数量、公务舱座位数量、头等舱座位数量以及备注信息等。
l 航线信息的输入、修改和查询，包括航线编号、出发城市、到达城市、航班日期、出发时间、到达时间、客机编号、经济舱价格、公务舱价格、头等舱价格和备注信息等。
l 客户等级信息的输入、修改，包括客户等级编号、客户等级名称、折扣比例和备注信息等。
l 客户信息的输入、修改和查询，包括客户编号、客户姓名、客户性别、身份证号码、联系电话、客户类型和备注信息等。
l 订票信息的输入、查询和修改，包括订票编号、客户编号、客户姓名、客户类型、折扣比例、航线编号、出发城市、到达城市、出发时间、舱位类型、票价、结算金额和备注信息等。
1.2 系统功能模块设计
对上述各项功能进行集中、分块，按照结构化程序设计的要求，得到如图9-1所示的系统功能模块图。