物联网工程中英文对照外文翻译文献
中英文对照外文翻译
(文档含英文原文和中文翻译)
Android: A Programmer’s Guide
1 What Is Android
1.1 Key Skills & Concepts
● History of embedded device programming
● Explanation of Open Handset Alliance
● First look at the Android home screen
It can be said that, for a while, traditional desktop application developers have been spoiled. This is not to say that traditional desktop application development is easier than other forms of develop ment. However, as traditional desktop application developers, we have had the ability to create alm ost any kind of application we can imagine. I am including myself in this grouping because I got my start in desktop programming.
One aspect that has made desktop programming more accessible is that we have had the ability to interact with the desktop operating system, and thus interact with any underlying hardware, pretty
freely (or at least with minimal exceptions). This kind of freedom to program independently, how ever, has never really been available to the small group of programmers who dared to venture int o the murky waters of cell phone development.
NOTE ：I refer to two different kinds of developers in this discussion: traditional desktop applicati on developers, who work in almost any language and whose end product, applications, are built to run on any “desktop” operating system; and Android developers, J ava developers who develop for the Android platform. This is not for the purposes of saying one is by any means better or wors e than the other. Rather, the distinction is made for purposes of comparing the development styles and tools of desktop operating system environments to the mobile operating system environment
1.2 Brief History of Embedded Device Programming
For a long time, cell phone developers comprised a small sect of a slightly larger group of developers known as embedded device developers. Seen as a less “glamorous” sibling to desktop—and later web—development, embedded device development typically got the proverbial short end of the stick as far as hardware and operating system features, because embedded device manufacturers were notoriously stingy on feature support.
Embedded device manufacturers typically needed to guard their hardware secrets closely, so they gave embedded device developers few libraries to call when trying to interact with a specific device. Embedded devices differ fro m desktops in that an embedded device is typically a “computer on a chip.” For example, consider your standard television remote control; it is not really seen as an overwhelming achievement of technological complexity. When any button is pressed, a chip interprets the signal in a way that has been programmed into the device. This allows the device to know what to expect from the input device (key pad), and how to respond to those commands (for example, turn on the television). This is a simple form of embedded device programming. However, believe it or not, simple devices such as these are definitely related to the roots of early cell phone devices and development.
Most embedded devices ran (and in some cases still run) proprietary operating systems. The reason for choosing to create a proprietary operating system rather than use any consumer system was really a product of necessity. Simple devices did not need very robust and optimized operating systems.
As a product of device evolution, many of the more complex embedded devices, such as early PDAs, household security systems, and GPSs, moved to somewhat standardized operating system platforms about five years ago. Small-footprint operating systems such as Linux, or even an embedded version of Microsoft Windows, have become more prevalent on many embedded devices. Around this time in device evolution, cell phones branched from other embedded devices onto their own path. This branching is evident when
you examine their architecture.
Nearly since their inception, cell phones have been fringe devices insofar as they run on proprietary software—software that is owned and controlled by the manufacturer, and is almost always considered to be a “closed” system. The practice of manufacturers using proprietary operating systems began more out of necessity than any other reason. That is, cell phone manufacturers typically used hardware that was completely developed in-house, or at least hardware that was specifically developed for the purposes of running cell phone equipment. As a result, there were no openly available, off-the-shelf software packages or solutions that would reliably interact with their hardware. Since the manufacturers also wanted to guard very closely their hardware trade secrets, some of which could be revealed by allowing access to the software level of the device, the common practice was, and in most cases still is, to use completely proprietary and closed software to run their devices. The downside to this is that anyone who wanted to develop applications for cell phones needed to have intimate knowledge of the proprietary environment within which it was to run. The solution was to purchase expensive development tools directly from the manufacturer. This isolated many of the “homebrew” develo pers.
NOTE：A growing culture of homebrew developers has embraced cell phone application development. The term “homebrew” refers to the fact that these developers typically do not work for a cell phone development company and generally produce small, one-off products on their own time.
Another, more compelling “necessity” that kept cell phone development out of the hands of the everyday developer was the hardware manufacturers’ solution to the “memory versus need” dilemma. Until recently, cell phones did little more than execute and receive phone calls, track your contacts, and possibly send and receive short text messages; not really the “Swiss army knives” of technology they are today. Even as late as 2002, cell phones with cameras were not commonly found in the hands of consumers.
By 1997, small applications such as calculators and games (Tetris, for example) crept their way onto cell phones, but the overwhelming function was still that of a phone dialer itself. Cell phones had not yet become the multiuse, multifunction personal tools they are today. No one yet saw the need for Internet browsing, MP3 playing, or any of the multitudes of functions we are accustomed to using today. It is possible that the cell phone manufacturers of 1997 did not fully perceive the need consumers would have for an all-in-one device. However, even if the need was present, a lack of device memory and storage capacity was an even bigger obstacle to overcome. More people may have wanted their devices to be all-in-one tools, but manufacturers still had to climb the memory hurdle.
To put the problem simply, it takes memory to store and run applications on any device, cell phones included. Cell phones, as a device, until recently did not have the amount of memory available to them that would facilitate the inclusion of “extra” programs. Within the last two years, the price of memory has reached very low levels. Device manufacturers now have the ability to include more memory at lower prices. Many cell phones now have more standard memory than the average PC had in the mid-1990s. So, now that we have the need, and the memory, we can all jump in and develop cool applications for cell phones around the world, right? Not exactly.
Device manufacturers still closely guard the operating systems that run on their devices. While a few have opened up to the point where they will allow some Java-based applications to run within a small environment on the phone, many do not allow this. Even the systems that do allow some Java apps to run do not allow the kind of access to the “core” system that standard desktop developers are accustomed to having.
1.3 Open Handset Alliance and Android
This barrier to application development began to crumble in November of 2007 when Google, under the Open Handset Alliance, released Android. The Open Handset Alliance is a group of hardware and software developers, including Google, NTT DoCoMo, Sprint Nextel, and HTC, whose goal is to create a more open cell phone environment. The first product to be released under the alliance is the mobile device operating system, Android.
With the release of Android, Google made available a host of development tools and tutorials to aid would-be developers onto the new system. Help files, the platform software development kit (SDK), and even a developers’ community can be found at Google’s Android website, This site should be your starting point, and I highly encourage you to visit the site.
NOTE ：Google, in promoting the new Android operating system, even went as far as to create a $10 million contest looking for new and exciting Android applications.
While cell phones running Linux, Windows, and even PalmOS are easy to find, as of this writing, no hardware platforms have been announced for Android to run on. HTC, LG Electronics, Motorola, and Samsung are members of the Open Handset Alliance, under which Android has been released, so we can only hope that they have plans for a few Android-based devices in the near future. With its release in November 2007, the system itself is still in a software-only beta. This is good news for developers because it gives us a rare advance look at a future system and a chance to begin developing applications that will
run as soon as the hardware is released.
NOTE：This strategy clearly gives the Open Handset Alliance a big advantage over other cell phone operating system developers, because there could be an uncountable number of applications available immediately for the first devices released to run Android.
Introduction to Android
Android, as a system, is a Java-based operating system that runs on the Linux 2.6 kernel. The system is very lightweight and full featured. Android applications are developed using Java and can be ported rather easily to the new platform. If you have not yet downloaded Java or are unsure about which version you need, I detail the installation of the development environment in Chapter 2. Other features of Android include an accelerated 3-D graphics engine (based on hardware support), database support powered by SQLite, and an integrated web browser.
If you are familiar with Java programming or are an OOP developer of any sort, you are likely used to programmatic user interface (UI) development—that is, UI placement which is handled directly within the program code. Android, while recognizing and allowing for programmatic UI development, also supports the newer, XML-based UI layout. XML UI layout is a fairly new concept to the average desktop developer. I will cover both the XML UI layout and the programmatic UI development in the supporting chapters of this book.
One of the more exciting and compelling features of Android is that, because of its architecture, third-party applications—including those that are “home grown”—are executed with the same system priority as those that are bundled with the core system. This is a major departure from most systems, which give embedded system apps a greater execution priority than the thread priority available to apps created by third-party developers. Also, each application is executed within its own thread using a very lightweight virtual machine.
Aside from the very generous SDK and the well-formed libraries that are available to us to develop with, the most exciting feature for Android developers is that we now have access to anything the operating system has access to. In other words, if you want to create an application that dials the phone, you have access to the phone’s dialer; if you want to create an application that utilizes the phone’s internal GPS (if equipped), you have access to it. The potential for developers to create dynamic and intriguing applications is now wide open.
On top of all the features that are available from the Android side of the equation, Google has thrown in
some very tantalizing features of its own. Developers of Android applications will be able to tie their applications into existing Google offerings such as Google Maps and the omnipresent Google Search. Suppose you want to write an application that pulls up a Google map of where an incoming call is emanating from, or you want to be able to store common search results with your contacts; the doors of possibility have been flung wide open with Android.
Chapter 2 begins your journey to Android development. You will learn the how’s and why’s of using specific development environments or integrated development environments (IDE), and you will download and install the Java IDE Eclipse.
2 Application: Hello World
2.1 Key Skills & Concepts
●Creating new Android projects
●Working with Views
●Using a TextView
●Modifying the main.xml file
●Running applications on the Android Emulator
In this chapter, you will be creating your first Android Activity. This chapter examines the application-building process from start to finish. I will show you how to create an Android project in Eclipse, add code to the initial files, and run the finished application in the Android Emulator. The resulting application will be a fully functioning program running in an Android environment.
Actually, as you move through this chapter, you will be creating more than one Android Activity. Computer programming tradition dictates that your first application be the typical Hello World! application, so in the first section you will create a standard Hello World! application with just a blank background and the “Hello World!” text. Then, for the sake of enabling you to get to know the language better, the next section explains in detail the files automatically created by Android for your Hello World! application. You will create two iterations of this Activity, each using different techniques for displaying information to the screen. You will also create two different versions of a Hello World! application that will display an image that delivers the “Hello World!” message. This will give you a good introduction to the controls and inner workings of Android.
NOTE：You will often see “application” and “Activity” used interchangeably. The difference between the two is that an application can be composed of multiple Activities, but one application must have at least
one Activity. Each “window” or screen of your application is a separate Activity. Therefore, if you create a fairly simple application with only one screen of data (like the Hello World! application in this chapter), that will be one Activity. In future chapters you will create applications with multiple Activities.
To make sure that you get a good overall look at programming in Android, in Chapter 6 you will create both of these applications in the Android SDK command-line environment for Microsoft Windows and Linux. In other words, this chapter covers the creation process in Eclipse, and Chapter 6 covers the creation process using the command-line tools. Therefore, before continuing, you should check that your Eclipse environment is correctly configured. Review the steps in Chapter 3 for setting the PATH statement for the Android SDK. You should also ensure that the JRE is correctly in your PATH statement.
TIP：If you have configuration-related issues while attempting to work with any of the command-line examples, try referring to the configuration steps in Chapters 2 and 3; and look at the Android SDK documentation.
2.2 Creating Your First Android Project in Eclipse
To start your first Android project, open Eclipse. When you open Eclipse for the first time, it opens to an empty development environment (see Figure 5-1), which is where you want to begin. Your first task is to set up and name the workspace for your application. Choose File | New | Android Project, which will launch the New Android Project wizard.
CAUTION Do not select Java Project from the New menu. While Android applications are written in Java, and you are doing all of your development in Java projects, this option will create a standard Java application. Selecting Android Project enables you to create Android-specific applications.If you do not see the option for Android Project, this indicates that the Android plugin for Eclipse was not fully or correctly installed. Review the procedure in Chapter 3 for installing the Android plugin for Eclipse to correct this.
2.3 The New Android Project wizard creates two things for you
A shell application that ties into the Android SDK, using the android.jar file, and ties the project into the Android Emulator. This allows you to code using all of the Android libraries and packages, and also lets you debug your applications in the proper environment.
Your first shell files for the new project. These shell files contain some of the vital application blocks upon which you will be building your programs. In much the same way as creating a Microsoft .NET application in Visual Studio generates some Windows-created program code in your files, using the Android Project wizard in Eclipse generates your initial program files and some Android-created code. In
addition, the New Android Project wizard contains a few options, shown next, that you must set to initiate your Android project. For the Project Name field, for purposes of this example, use the title HelloWorldText. This name sufficiently distinguishes this Hello World! project from the others that you will be creating in this chapter.In the Contents area, keep the default selections: the Create New Project in Workspace radio button should be selected and the Use Default Location check box should be checked. This will allow Eclipse to create your project in your default workspace directory. The advantage of keeping the default options is that your projects are kept in a central location, which makes ordering, managing, and finding these projects quite easy. For example, if you are working in a Unix-based environment, this path points to your $HOME directory.
If you are working in a Microsoft Windows environment, the workspace path will be C:/Users/
3 Application Fundamentals
Android applications are written in the Java programming language. The compiled Java code — along with any data and resource files required by the application — is bundled by the aapt tool into an Android package, an archive file marked by an .apk suffix. This file is the vehicle for distributing the application and installing it on mobile devices; it's the file users download to their devices. All the code in a single .apk file is considered to be one application.
In many ways, each Android application lives in its own world:
1. By default, every application runs in its own Linux process. Android starts the process when any of the application's code needs to be executed, and shuts down the process when it's no longer needed and system resources are required by other applications.
2. Each process has its own virtual machine (VM), so application code runs in isolation from the code of all other applications.
3. By default, each application is assigned a unique Linux user ID. Permissions are set so that the application's files are visible only to that user and only to the application itself — although there are ways to export them to other applications as well.
It's possible to arrange for two applications to share the same user ID, in which case they will be able to see each other's files. To conserve system resources, applications with the same ID can also arrange to run in the same Linux process, sharing the same VM.
3.1 Application Components
A central feature of Android is that one application can make use of elements of other applications (provided those applications permit it). For example, if your application needs to display a scrolling list of images and another application has developed a suitable scroller and made it available to others, you can call upon that scroller to do the work, rather than develop your own. Application have four types of components:
(1)Activities
An activity presents a visual user interface for one focused endeavor the user can undertake. For example, an activity might present a list of menu items users can choose from or it might display photographs along with their captions. A text messaging application might have one activity that shows a list of contacts to send messages to, a second activity to write the message to the chosen contact, and other activities to review old messages or change settings. Though they work together to form a cohesive user interface, each activity is independent of the others. Each one is implemented as a subclass of the Activity base class.
An application might consist of just one activity or, like the text messaging application just mentioned, it may contain several. What the activities are, and how many there are depends, of course, on the application and its design. Typically, one of the activities is marked as the first one that should be presented to the user when the application is launched. Moving from one activity to another is accomplished by having the current activity start the next one.
Each activity is given a default window to draw in. Typically, the window fills the screen, but it might be smaller than the screen and float on top of other windows. An activity can also make use of additional windows — for example, a pop-up dialog that calls for a user response in the midst of the activity, or a window that presents users with vital information when they select a particular item on-screen.
The visual content of the window is provided by a hierarchy of views — objects derived from the base View class. Each view controls a particular rectangular space within the window. Parent views contain and organize the layout of their children. Leaf views (those at the bottom of the hierarchy) draw in the rectangles they control and respond to user actions directed at that space. Thus, views are where the activity's interaction with the user takes place.
For example, a view might display a small image and initiate an action when the user taps that image. Android has a number of ready-made views that you can use — including buttons, text fields, scroll bars, menu items, check boxes, and more.
A view hierarchy is placed within an activity's window by the Activity.setContentView() method. The content view is the View object at the root of the hierarchy. (See the separate User Interface document for more information on views and the hierarchy.)
(2)Services
A service doesn't have a visual user interface, but rather runs in the background for an indefinite period of time. For example, a service might play background music as the user attends to other matters, or it might fetch data over the network or calculate something and provide the result to activities that need it. Each service extends the Service base class.
A prime example is a media player playing songs from a play list. The player application would probably have one or more activities that allow the user to choose songs and start playing them. However, the music
playback itself would not be handled by an activity because users will expect the music to keep playing even after they leave the player and begin something different. To keep the music going, the media player activity could start a service to run in the background. The system would then keep the music playback service running even after the activity that started it leaves the screen.
It's possible to connect to (bind to) an ongoing service (and start the service if it's not already running). While connected, you can communicate with the service through an interface that the service exposes. For the music service, this interface might allow users to pause, rewind, stop, and restart the playback.
Like activities and the other components, services run in the main thread of the application process. So that they won't block other components or the user interface, they often spawn another thread for time-consuming tasks (like music playback). See Processes and Threads, later.
(3)Broadcast receivers
A broadcast receiver is a component that does nothing but receive and react to broadcast announcements. Many broadcasts originate in system code — for example, announcements that the timezone has changed, that the battery is low, that a picture has been taken, or that the user changed a language preference. Applications can also initiate broadcasts — for example, to let other applications know that some data has been downloaded to the device and is available for them to use.
An application can have any number of broadcast receivers to respond to any announcements it considers important. All receivers extend the BroadcastReceiver base class.
Broadcast receivers do not display a user interface. However, they may start an activity in response to the information they receive, or they may use the NotificationManager to alert the user. Notifications can get the user's attention in various ways — flashing the backlight, vibrating the device, playing a sound, and so on. They typically place a persistent icon in the status bar, which users can open to get the message.
(4)Content providers
A content provider makes a specific set of the application's data available to other applications. The data can be stored in the file system, in an SQLite database, or in any other manner that makes sense. The content provider extends the ContentProvider base class to implement a standard set of methods that enable other applications to retrieve and store data of the type it controls. However, applications do not call these methods directly. Rather they use a ContentResolver object and call its methods instead. A ContentResolver can talk to any content provider; it cooperates with the provider to manage any interprocess communication that's involved.
See the separate Content Providers document for more information on using content providers. Whenever there's a request that should be handled by a particular component, Android makes sure that the application process of the component is running, starting it if necessary, and that an appropriate instance of the component is available, creating the instance if necessary.
3.2 Activating components: intents
Content providers are activated when they're targeted by a request from a ContentResolver. The other three components —activities, services, and broadcast receivers —are activated by asynchronous messages called intents. An intent is an Intent object that holds the content of the message. For activities and services, it names the action being requested and specifies the URI of the data to act on, among other things. For example, it might convey a request for an activity to present an image to the user or let the user edit some text. For broadcast receivers, the
Intent object names the action being announced. For example, it might announce to interested parties that the camera button has been pressed.
红外数据通信技术外文翻译文献
红外数据通信技术外文翻译文献(文档含中英文对照即英文原文和中文翻译) Infrared Remote Control System Abstract Red outside data correspondence the technique be currently within the scope of world drive extensive usage of a kind of wireless conjunction technique, drive numerous hardware and software platform support. Red outside the transceiver product have cost low, small scaled turn, the baud rate be quick, point to point SSL, be free from electromagnetism thousand Raos
etc. characteristics, can realization information at dissimilarity of the product fast, convenience, safely exchange and transmission, at short distance wireless deliver aspect to own very obvious of advantage. Along with red outside the data deliver a technique more and more mature, the cost descend, red outside the transceiver necessarily will get at the short distance communication realm more extensive of application. The purpose that design this system is transmit customer’s operation information with infrared rays for transmit media, then demodulate original signal with receive circuit. It use coding chip to modulate signal and use decoding chip to demodulate signal. The coding chip is PT2262 and decoding chip is PT2272. Both chips are made in Taiwan. Main work principle is that we provide to input the information for the PT2262 with coding keyboard. The input information was coded by PT2262 and loading to high frequent load wave whose frequent is 38 kHz, then modulate infrared transmit dioxide and radiate space outside when it attian enough power. The receive circuit receive the signal and demodulate original information. The original signal was decoded by PT2272, so as to drive some circuit to accomplish customer’s operation demand. Keywords: Infrared dray；Code；Decoding；LM386；Red outside transceiver 1 Introduction 1.1 research the background and significance Infrared Data Communication Technology is the world wide use of a wireless connection technology, by the many hardware and software platforms supported. Is a data through electrical pulses and infrared optical pulse switch between the wireless data transceiver technology.
土木工程类专业英文文献及翻译
PA VEMENT PROBLEMS CAUSED BY COLLAPSIBLE SUBGRADES By Sandra L. Houston,1 Associate Member, ASCE (Reviewed by the Highway Division) ABSTRACT: Problem subgrade materials consisting of collapsible soils are com- mon in arid environments, which have climatic conditions and depositional and weathering processes favorable to their formation. Included herein is a discussion of predictive techniques that use commonly available laboratory equipment and testing methods for obtaining reliable estimates of the volume change for these problem soils. A method for predicting relevant stresses and corresponding collapse strains for typical pavement subgrades is presented. Relatively simple methods of evaluating potential volume change, based on results of familiar laboratory tests, are used. INTRODUCTION When a soil is given free access to water, it may decrease in volume, increase in volume, or do nothing. A soil that increases in volume is called a swelling or expansive soil, and a soil that decreases in volume is called a collapsible soil. The amount of volume change that occurs depends on the soil type and structure, the initial soil density, the imposed stress state, and the degree and extent of wetting. Subgrade materials comprised of soils that change volume upon wetting have caused distress to highways since the be- ginning of the professional practice and have cost many millions of dollars in roadway repairs. The prediction of the volume changes that may occur in the field is the first step in making an economic decision for dealing with these problem subgrade materials. Each project will have different design considerations, economic con- straints, and risk factors that will have to be taken into account. However, with a reliable method for making volume change predictions, the best design relative to the subgrade soils becomes a matter of economic comparison, and a much more rational design approach may be made. For example, typical techniques for dealing with expansive clays include: (1) In situ treatments with substances such as lime, cement, or fly-ash; (2) seepage barriers and/ or drainage systems; or (3) a computing of the serviceability loss and a mod- ification of the design to "accept" the anticipated expansion. In order to make the most economical decision, the amount of volume change (especially non- uniform volume change) must be accurately estimated, and the degree of road roughness evaluated from these data. Similarly, alternative design techniques are available for any roadway problem. The emphasis here will be placed on presenting economical and simple methods for: (1) Determining whether the subgrade materials are collapsible; and (2) estimating the amount of volume change that is likely to occur in the 'Asst. Prof., Ctr. for Advanced Res. in Transp., Arizona State Univ., Tempe, AZ 85287. Note. Discussion open until April 1, 1989. To extend the closing date one month,
英文文献翻译
中等分辨率制备分离的 快速色谱技术 W. Clark Still,* Michael K a h n , and Abhijit Mitra Departm(7nt o/ Chemistry, Columbia Uniuersity,1Veu York, Neu; York 10027 ReceiLied January 26, 1978 我们希望找到一种简单的吸附色谱技术用于有机化合物的常规净化。这种技术是适于传统的有机物大规模制备分离，该技术需使用长柱色谱法。尽管这种技术得到的效果非常好，但是其需要消耗大量的时间，并且由于频带拖尾经常出现低复原率。当分离的样本剂量大于1或者2g时，这些问题显得更加突出。近年来，几种制备系统已经进行了改进，能将分离时间减少到1-3h，并允许各成分的分辨率ΔR f≥（使用薄层色谱分析进行分析）。在这些方法中，在我们的实验室中，媒介压力色谱法1和短柱色谱法2是最成功的。最近，我们发现一种可以将分离速度大幅度提升的技术，可用于反应产物的常规提纯，我们将这种技术称为急骤色谱法。虽然这种技术的分辨率只是中等（ΔR f≥），而且构建这个系统花费非常低，并且能在10-15min内分离重量在的样本。4 急骤色谱法是以空气压力驱动的混合介质压力以及短柱色谱法为基础，专门针对快速分离，介质压力以及短柱色谱已经进行了优化。优化实验是在一组标准条件5下进行的，优化实验使用苯甲醇作为样本，放在一个20mm*5in.的硅胶柱60内，使用Tracor 970紫外检测器监测圆柱的输出。分辨率通过持续时间（r）和峰宽（w,w/2）的比率进行测定的（Figure 1），结果如图2-4所示，图2-4分别放映分辨率随着硅胶颗粒大小、洗脱液流速和样本大小的变化。
土木工程外文翻译
转型衰退时期的土木工程研究 Sergios Lambropoulosa[1], John-Paris Pantouvakisb, Marina Marinellic 摘要 最近的全球经济和金融危机导致许多国家的经济陷入衰退，特别是在欧盟的周边。这些国家目前面临的民用建筑基础设施的公共投资和私人投资显著收缩，导致在民事特别是在民用建筑方向的失业。因此，在所有国家在经济衰退的专业发展对于土木工程应届毕业生来说是努力和资历的不相称的研究，因为他们很少有机会在实践中积累经验和知识，这些逐渐成为过时的经验和知识。在这种情况下，对于技术性大学在国家经济衰退的计划和实施的土木工程研究大纲的一个实质性的改革势在必行。目的是使毕业生拓宽他们的专业活动的范围，提高他们的就业能力。 在本文中，提出了土木工程研究课程的不断扩大，特别是在发展的光毕业生的潜在的项目，计划和投资组合管理。在这个方向上，一个全面的文献回顾，包括ASCE体为第二十一世纪，IPMA的能力的基础知识，建议在其他：显著增加所提供的模块和项目管理在战略管理中添加新的模块，领导行为，配送管理，组织和环境等；提供足够的专业训练五年的大学的研究；并由专业机构促进应届大学生认证。建议通过改革教学大纲为土木工程研究目前由国家技术提供了例证雅典大学。 1引言 土木工程研究（CES）蓬勃发展，是在第二次世界大战后。土木工程师的出现最初是由重建被摧毁的巨大需求所致，目的是更多和更好的社会追求。但是很快，这种演变一个长期的趋势，因为政府为了努力实现经济发展，采取了全世界的凯恩斯主义的理论，即公共基础设施投资作为动力。首先积极的结果导致公民为了更好的生活条件（住房，旅游等）和增加私人投资基础设施而创造机会。这些现象再国家的发展中尤为为明显。虽然前景并不明朗（例如，世界石油危机在70年代），在80年代领先的国家采用新自由主义经济的方法（如里根经济政策），这是最近的金融危机及金融危机造成的后果（即收缩的基础设施投资，在技术部门的高失业率），消除发展前途无限的误区。 技术教育的大学所认可的大量研究土木工程部。旧学校拓展专业并且新的学校建成，并招收许多学生。由于高的职业声望，薪酬，吸引高质量的学校的学生。在工程量的增加和科学技术的发展，导致到极强的专业性，无论是在研究还是工作当中。结构工程师，液压工程师，交通工程师等，都属于土木工程。试图在不同的国家采用专业性的权利，不同的解决方案，，从一个统一的大学学历和广泛的专业化的一般职业许可证。这个问题在许多其他行业成为关键。国际专业协会的专家和机构所确定的国家性检查机构，经过考试后，他们证明不仅是行业的新来者，而且专家通过时间来确定进展情况。尽管在很多情况下，这些证书虽然没有国家接受，他们赞赏和公认的世界。 在试图改革大学研究（不仅在土木工程）更接近市场需求的过程中，欧盟确定了1999博洛尼亚宣言，它引入了一个二能级系统。第一级度（例如，一个三年的学士）是进入
通信工程项目毕业材料外文翻译
用于多跳认知无线电网络的分布式网络编码控制信道 Alfred Asterjadhi等著 1 前言 大多数电磁频谱由政府机构长期指定给公司或机构专门用于区域或国家地区。由于这种资源的静态分配，许可频谱的许多部分在许多时间和/或位置未使用或未被充分利用。另一方面，几种最近的无线技术在诸如IEEE802.11，蓝牙，Zigbee之类的非许可频段中运行，并且在一定程度上对WiMAX进行操作;这些技术已经看到这样的成功和扩散，他们正在访问的频谱- 主要是2.4 GHz ISM频段- 已经过度拥挤。为了为这些现有技术提供更多的频谱资源，并且允许替代和创新技术的潜在开发，最近已经提出允许被许可的设备（称为次要用户）访问那些许可的频谱资源，主要用户未被使用或零星地使用。这种方法通常被称为动态频谱接入（DSA），无线电设备发现和机会性利用未使用或未充分利用的频谱带的能力通常称为认知无线电（CR）技术。 DSA和CR最近都引起了无线通信和网络界的极大关注。通常设想两种主要应用。第一个是认知无线接入（CW A），根据该认知接入点，认知接入点负责识别未使用的许可频谱，并使用它来提供对次用户的接入。第二个应用是我们在这个技术中研究的应用，它是认知自组织网络（CAN），也就是使用 用于二级用户本身之间通信的无许可频谱，用于诸如点对点内容分发，环境监控，安全性等目的，灾难恢复情景通信，军事通信等等。 设计CAN系统比CW A有更多困难，主要有两个原因。第一是识别未使用的频谱。在CW A中，接入点的作用是连接到互联网，因此可以使用简单的策略来推断频谱可用性，例如查询频谱调节器在其地理位置的频谱可用性或直接与主用户协商频谱可用性或一些中间频谱经纪人另一方面，在CAN中，与频谱调节器或主要用户的缺乏直接通信需要二级用户能够使用检测技术自己识别未使用的频谱。第二个困难是辅助用户协调媒体访问目的。在CW A中存在接入点和通常所有二级用户直接与之通信（即，网络是单跳）的事实使得直接使用集中式媒体接入控制（MAC）解决方案，如时分多址（TDMA）或正交频分多址（OFDMA）。相反，预计CAN将跨越多跳，缺少集中控制器;而对于传统的单通道多跳自组织网络而言，这个问题的几个解决方案是已知的，因为假设我们处理允许设备访问的具有成
土木工程岩土类毕业设计外文翻译
姓名： 学号： 10447425 X X 大学 毕业设计（论文）外文翻译 （2014届） 外文题目Developments in excavation bracing systems 译文题目开挖工程支撑体系的发展 外文出处Tunnelling and Underground Space Technology 31 (2012) 107–116 学生XXX 学院XXXX 专业班级XXXXX 校内指导教师XXX 专业技术职务XXXXX 校外指导老师专业技术职务 二○一三年十二月
开挖工程支撑体系的发展 1.引言 几乎所有土木工程建设项目（如建筑物，道路，隧道，桥梁，污水处理厂，管道，下水道）都涉及泥土挖掘的一些工程量。往往由于由相邻的结构，特性线，或使用权空间的限制，必须要一个土地固定系统，以允许土壤被挖掘到所需的深度。历史上，许多挖掘支撑系统已经开发出来。其中，现在比较常见的几种方法是：板桩，钻孔桩墙，泥浆墙。 土地固定系统的选择是由技术性能要求和施工可行性（例如手段，方法）决定的，包括执行的可靠性，而成本考虑了这些之后，其他问题也得到解决。通常环境后果（用于处理废泥浆和钻井液如监管要求）也非常被关注（邱阳、1998）。 土地固定系统通常是建设项目的较大的一个组成部分。如果不能按时完成项目，将极大地影响总成本。通常首先建造支撑，在许多情况下，临时支撑系统是用于支持在挖掘以允许进行不断施工，直到永久系统被构造。临时系统可以被去除或留在原处。 打桩时，因撞击或振动它们可能会被赶入到位。在一般情况下，振动是最昂贵的方法，但只适合于松散颗粒材料，土壤中具有较高电阻（例如，通过鹅卵石）的不能使用。采用打入桩系统通常是中间的成本和适合于软沉积物（包括粘性和非粘性），只要该矿床是免费的鹅卵石或更大的岩石。 通常，垂直元素（例如桩）的前安装挖掘工程和水平元件（如内部支撑或绑回）被安装为挖掘工程的进行下去，从而限制了跨距长度，以便减少在垂直开发弯矩元素。在填充情况下，桩可先设置，从在斜坡的底部其嵌入悬挑起来，安装作为填充进步水平元素（如搭背或土钉）。如果滞后是用来保持垂直元素之间的土壤中，它被安装为挖掘工程的进行下去，或之前以填补位置。 吉尔- 马丁等人（2010）提供了一个数值计算程序，以获取圆形桩承受轴向载荷和统一标志（如悬臂桩）的单轴弯矩的最佳纵筋。他们开发的两种优化流程：用一个或两个直径为纵向钢筋。优化增强模式允许大量减少的设计要求钢筋的用量，这些减少纵向钢筋可达到50％相对传统的，均匀分布的加固方案。 加固桩集中纵向钢筋最佳的位置在受拉区。除了节约钢筋，所述非对称加强钢筋图案提高抗弯刚度，通过增加转动惯量的转化部分的时刻。这种增加的刚性可能会在一段时间内增加的变形与蠕变相关的费用。评估相对于传统的非对称加强桩的优点，对称，钢筋桩被服务的条件下全面测试来完成的，这种试验是为了验证结构的可行性和取得的变形的原位测量。 基于现场试验中，用于优化的加强图案的优点浇铸钻出孔（CIDH）在巴塞罗那的
计算机网络-外文文献-外文翻译-英文文献-新技术的计算机网络
New technique of the computer network Abstract The 21 century is an ages of the information economy, being the computer network technique of representative techniques this ages, will be at very fast speed develop soon in continuously creatively, and will go deep into the people's work, life and study. Therefore, control this technique and then seem to be more to deliver the importance. Now I mainly introduce the new technique of a few networks in actuality live of application. keywords Internet Network System Digital Certificates Grid Storage 1. Foreword Internet turns 36, still a work in progress Thirty-six years after computer scientists at UCLA linked two bulky computers using a 15-foot gray cable, testing a new way for exchanging data over networks, what would ultimately become the Internet remains a work in progress. University researchers are experimenting with ways to increase its capacity and speed. Programmers are trying to imbue Web pages with intelligence. And work is underway to re-engineer the network to reduce Spam (junk mail) and security troubles. All the while threats loom: Critics warn that commercial, legal and political pressures could hinder the types of innovations that made the Internet what it is today. Stephen Crocker and Vinton Cerf were among the graduate students who joined UCLA professor Len Klein rock in an engineering lab on Sept. 2, 1969, as bits of meaningless test data flowed silently between the two computers. By January, three other "nodes" joined the fledgling network.
土木工程外文翻译.doc
项目成本控制 一、引言 项目是企业形象的窗口和效益的源泉。随着市场竞争日趋激烈，工程质量、文明施工要求不断提高，材料价格波动起伏，以及其他种种不确定因素的影响，使得项目运作处于较为严峻的环境之中。由此可见项目的成本控制是贯穿在工程建设自招投标阶段直到竣工验收的全过程，它是企业全面成本管理的重要环节，必须在组织和控制措施上给于高度的重视，以期达到提高企业经济效益的目的。 二、概述 工程施工项目成本控制，指在项目成本在成本发生和形成过程中，对生产经营所消耗的人力资源、物资资源和费用开支，进行指导、监督、调节和限制，及时预防、发现和纠正偏差从而把各项费用控制在计划成本的预定目标之内，以达到保证企业生产经营效益的目的。 三、施工企业成本控制原则 施工企业的成本控制是以施工项目成本控制为中心，施工项目成本控制原则是企业成本管理的基础和核心，施工企业项目经理部在对项目施工过程进行成本控制时，必须遵循以下基本原则。 3.1 成本最低化原则。施工项目成本控制的根本目的，在于通过成本管理的各种手段，促进不断降低施工项目成本，以达到可能实现最低的目标成本的要求。在实行成本最低化原则时，应注意降低成本的可能性和合理的成本最低化。一方面挖掘各种降低成本的能力，使可能性变为现实；另一方面要从实际出发，制定通过主观努力可能达到合理的最低成本水平。 3.2 全面成本控制原则。全面成本管理是全企业、全员和全过程的管理，亦称“三全”管理。项目成本的全员控制有一个系统的实质性内容，包括各部门、各单位的责任网络和班组经济核算等等，应防止成本控制人人有责，人人不管。项目成本的全过程控制要求成本控制工作要随着项目施工进展的各个阶段连续 进行，既不能疏漏，又不能时紧时松，应使施工项目成本自始至终置于有效的控制之下。 3.3 动态控制原则。施工项目是一次性的，成本控制应强调项目的中间控制，即动态控制。因为施工准备阶段的成本控制只是根据施工组织设计的具体内容确
5G无线通信网络中英文对照外文翻译文献
5G无线通信网络中英文对照外文翻译文献(文档含英文原文和中文翻译)
翻译： 5G无线通信网络的蜂窝结构和关键技术 摘要 第四代无线通信系统已经或者即将在许多国家部署。然而，随着无线移动设备和服务的激增，仍然有一些挑战尤其是4G所不能容纳的，例如像频谱危机和高能量消耗。无线系统设计师们面临着满足新型无线应用对高数据速率和机动性要求的持续性增长的需求，因此他们已经开始研究被期望于2020年后就能部署的第五代无线系统。在这篇文章里面，我们提出一个有内门和外门情景之分的潜在的蜂窝结构，并且讨论了多种可行性关于5G无线通信系统的技术，比如大量的MIMO技术，节能通信，认知的广播网络和可见光通信。面临潜在技术的未知挑战也被讨论了。 介绍 信息通信技术（ICT）创新合理的使用对世界经济的提高变得越来越重要。无线通信网络在全球ICT战略中也许是最挑剔的元素，并且支撑着很多其他的行业，它是世界上成长最快最有活力的行业之一。欧洲移动天文台（EMO）报道2010年移动通信业总计税收1740亿欧元,从而超过了航空航天业和制药业。无线技术的发展大大提高了人们在商业运作和社交功能方面通信和生活的能力无线移动通信的显著成就表现在技术创新的快速步伐。从1991年二代移动通信系统(2G)的初次登场到2001年三代系统（3G）的首次起飞，无线移动网络已经实现了从一个纯粹的技术系统到一个能承载大量多媒体内容网络的转变。4G无线系统被设计出来用来满足IMT-A技术使用IP面向所有服务的需求。在4G系统中，先进的无线接口被用于正交频分复用技术（OFDM），多输入多输出系统（MIMO）和链路自适应技术。4G无线网络可支持数据速率可达1Gb/s的低流度，比如流动局域无线访问，还有速率高达100M/s的高流速，例如像移动访问。LTE系统和它的延伸系统LTE-A，作为实用的4G系统已经在全球于最近期或不久的将来部署。 然而，每年仍然有戏剧性增长数量的用户支持移动宽频带系统。越来越多的
土木工程专业外文文献及翻译
（ 二 〇 一 二 年 六 月 外文文献及翻译 题 目： About Buiding on the Structure Design 学生姓名： 学 院：土木工程学院 系 别：建筑工程系 专 业：土木工程(建筑工程方向) 班 级：土木08-4班 指导教师：
英文原文： Building construction concrete crack of prevention and processing Abstract The crack problem of concrete is a widespread existence but again difficult in solve of engineering actual problem, this text carried on a study analysis to a little bit familiar crack problem in the concrete engineering, and aim at concrete the circumstance put forward some prevention, processing measure. Keyword:Concrete crack prevention processing Foreword Concrete's ising 1 kind is anticipate by the freestone bone, cement, water and other mixture but formation of the in addition material of quality brittleness not and all material.Because the concrete construction transform with oneself, control etc. a series problem, harden model of in the concrete existence numerous tiny hole, spirit cave and tiny crack, is exactly because these beginning start blemish of existence just make the concrete present one some not and all the characteristic of quality.The tiny crack is a kind of harmless crack and accept concrete heavy, defend Shen and a little bit other use function not a creation to endanger.But after the concrete be subjected to lotus carry, difference in temperature etc. function, tiny crack would continuously of expand with connect, end formation we can see without the
变电站_外文翻译_外文文献_英文文献_变电站的综合概述
英文翻译 A comprehensive overview of substations Along with the economic development and the modern industry developments of quick rising, the design of the power supply system become more and more completely and system. Because the quickly increase electricity of factories, it also increases seriously to the dependable index of the economic condition, power supply in quantity. Therefore they need the higher and more perfect request to the power supply. Whether Design reasonable, not only affect directly the base investment and circulate the expenses with have the metal depletion in colour metal, but also will reflect the dependable in power supply and the safe in many facts. In a word, it is close with the economic performance and the safety of the people. The substation is an importance part of the electric power system, it is consisted of the electric appliances equipments and the Transmission and the Distribution. It obtains the electric power from the electric power system, through its function of transformation and assign, transport and safety. Then transport the power to every place with safe, dependable, and economical. As an important part of power’s transport and control, the transformer substation must change the mode of the traditional design and control, then can adapt to the modern electric power system, the development of modern industry and the of trend of the society life. Electric power industry is one of the foundations of national industry and national economic development to industry, it is a coal, oil, natural gas, hydropower, nuclear power, wind power and other energy conversion into electrical energy of the secondary energy industry, it for the other departments of the national economy fast and stable development of the provision of adequate power, and its level of development is a reflection of the country's economic development an important indicator of the level. As the power in the industry and the importance of the national economy, electricity transmission and distribution of electric energy used in these areas is an indispensable component.。Therefore, power transmission and distribution is critical. Substation is to enable superior power plant power plants or power after adjustments to the lower load of books is an important part of power transmission. Operation of its functions, the capacity of a direct impact on the size of the lower load power, thereby affecting the industrial production and power consumption.Substation system if a link failure, the system will protect the part of action. May result in power outages and so on, to the production and living a great disadvantage. Therefore, the substation in the electric power system for the protection of electricity reliability,
土木工程外文文献翻译
专业资料 学院： 专业：土木工程 姓名： 学号： 外文出处：Structural Systems to resist (用外文写) Lateral loads 附件：1.外文资料翻译译文；2.外文原文。
附件1：外文资料翻译译文 抗侧向荷载的结构体系 常用的结构体系 若已测出荷载量达数千万磅重，那么在高层建筑设计中就没有多少可以进行极其复杂的构思余地了。确实，较好的高层建筑普遍具有构思简单、表现明晰的特点。 这并不是说没有进行宏观构思的余地。实际上，正是因为有了这种宏观的构思，新奇的高层建筑体系才得以发展，可能更重要的是：几年以前才出现的一些新概念在今天的技术中已经变得平常了。 如果忽略一些与建筑材料密切相关的概念不谈，高层建筑里最为常用的结构体系便可分为如下几类： 1.抗弯矩框架。 2.支撑框架，包括偏心支撑框架。 3.剪力墙，包括钢板剪力墙。 4.筒中框架。 5.筒中筒结构。 6.核心交互结构。 7. 框格体系或束筒体系。 特别是由于最近趋向于更复杂的建筑形式，同时也需要增加刚度以抵抗几力和地震力，大多数高层建筑都具有由框架、支撑构架、剪力墙和相关体系相结合而构成的体系。而且，就较高的建筑物而言，大多数都是由交互式构件组成三维陈列。 将这些构件结合起来的方法正是高层建筑设计方法的本质。其结合方式需要在考虑环境、功能和费用后再发展，以便提供促使建筑发展达到新高度的有效结构。这并
不是说富于想象力的结构设计就能够创造出伟大建筑。正相反，有许多例优美的建筑仅得到结构工程师适当的支持就被创造出来了，然而，如果没有天赋甚厚的建筑师的创造力的指导，那么，得以发展的就只能是好的结构，并非是伟大的建筑。无论如何，要想创造出高层建筑真正非凡的设计，两者都需要最好的。 虽然在文献中通常可以见到有关这七种体系的全面性讨论，但是在这里还值得进一步讨论。设计方法的本质贯穿于整个讨论。设计方法的本质贯穿于整个讨论中。 抗弯矩框架 抗弯矩框架也许是低，中高度的建筑中常用的体系，它具有线性水平构件和垂直构件在接头处基本刚接之特点。这种框架用作独立的体系，或者和其他体系结合起来使用，以便提供所需要水平荷载抵抗力。对于较高的高层建筑，可能会发现该本系不宜作为独立体系，这是因为在侧向力的作用下难以调动足够的刚度。 我们可以利用STRESS，STRUDL 或者其他大量合适的计算机程序进行结构分析。所谓的门架法分析或悬臂法分析在当今的技术中无一席之地，由于柱梁节点固有柔性，并且由于初步设计应该力求突出体系的弱点，所以在初析中使用框架的中心距尺寸设计是司空惯的。当然，在设计的后期阶段，实际地评价结点的变形很有必要。 支撑框架 支撑框架实际上刚度比抗弯矩框架强，在高层建筑中也得到更广泛的应用。这种体系以其结点处铰接或则接的线性水平构件、垂直构件和斜撑构件而具特色，它通常与其他体系共同用于较高的建筑，并且作为一种独立的体系用在低、中高度的建筑中。
通信工程移动通信中英文对照外文翻译文献
中英文翻译 附件1：外文资料翻译译文 通用移动通信系统的回顾 1.1 UMTS网络架构 欧洲/日本的3G标准，被称为UMTS。 UMTS是一个在IMT-2000保护伞下的ITU-T 批准的许多标准之一。随着美国的CDMA2000标准的发展，它是目前占主导地位的标准，特别是运营商将cdmaOne部署为他们的2G技术。在写这本书时，日本是在3G 网络部署方面最先进的。三名现任运营商已经实施了三个不同的技术：J - PHONE 使用UMTS，KDDI拥有CDMA2000网络，最大的运营商NTT DoCoMo正在使用品牌的FOMA（自由多媒体接入）系统。 FOMA是基于原来的UMTS协议，而且更加的协调和标准化。 UMTS标准被定义为一个通过通用分组无线系统（GPRS）和全球演进的增强数据
技术（EDGE）从第二代GSM标准到UNTS的迁移，如图。这是一个广泛应用的基本原理，因为自2003年4月起，全球有超过847万GSM用户，占全球的移动用户数字的68％。重点是在保持尽可能多的GSM网络与新系统的操作。 我们现在在第三代（3G）的发展道路上，其中网络将支持所有类型的流量：语音，视频和数据，我们应该看到一个最终的爆炸在移动设备上的可用服务。此驱动技术是IP协议。现在，许多移动运营商在简称为2.5G的位置，伴随GPRS的部署，即将IP骨干网引入到移动核心网。在下图中，图2显示了一个在GPRS网络中的关键部件的概述，以及它是如何适应现有的GSM基础设施。 SGSN和GGSN之间的接口被称为Gn接口和使用GPRS隧道协议（GTP的，稍后讨论）。引进这种基础设施的首要原因是提供连接到外部分组网络如，Internet或企业Intranet。这使IP协议作为SGSN和GGSN之间的运输工具应用到网络。这使得数据服务，如移动设备上的电子邮件或浏览网页，用户被起诉基于数据流量，而不是时间连接基础上的数据量。3G网络和服务交付的主要标准是通用移动通信系统，或UMTS。首次部署的UMTS是发行'99架构，在下面的图3所示。 在这个网络中，主要的变化是在无线接入网络（RAN的）CDMA空中接口技术的引进，和在传输部分异步传输模式作为一种传输方式。这些变化已经引入，主要是为了支持在同一网络上的语音，视频和数据服务的运输。核心网络保持相对不变，主要是软件升级。然而，随着目前无线网络控制器使用IP与3G的GPRS业务支持节点进行通信，IP协议进一步应用到网络。 未来的进化步骤是第4版架构，如图4。在这里，GSM的核心被以语音IP技术为基础的IP网络基础设施取代。 海安的发展分为两个独立部分：媒体网关（MGW）和MSC服务器（MSS）的。这基本上是打破外连接的作用和连接控制。一个MSS可以处理多个MGW，使网络更具有扩展性。 因为现在有一些在3G网络的IP云，合并这些到一个IP或IP/ ATM骨干网是很有意义的（它很可能会提供两种选择运营商）。这使IP权利拓展到整个网络，一直到BTS(基站收发信台)。这被称为全IP网络，或推出五架构，如图五所示。在HLR/ VLR/VLR/EIR被推广和称为HLR的子系统（HSS）。 现在传统的电信交换的最后残余被删除，留下完全基于IP协议的网络运营，并