1. Trang chủ
  2. » Thể loại khác

...C08. Interface.pdf

12 39 0

Đang tải... (xem toàn văn)

Tài liệu hạn chế xem trước, để xem đầy đủ mời bạn chọn Tải xuống

THÔNG TIN TÀI LIỆU

Thông tin cơ bản

Định dạng
Số trang 12
Dung lượng 294,37 KB

Nội dung

ETSI WIDEBAND CDMA STANDARD FOR THE UTRA FDD AIR INTERFACE by Nicky Jee-Ngai Yuen Electrical Engineering 563 Wireless Personal Telecommunications Systems ETSI WIDEBAND CDMA STANDARD FOR THE UTRA FDD AIR INTERFACE Submitted to Dr. P. Takis Mathiopoulos The University of British Columbia by Nicky Jee-Ngai Yuen The University of British Columbia March 30 2001 ii ABSTRACT “ETSI Wideband CDMA Standard for the UTRA FDD Air Interface” by Nicky Yuen The core requirements for the IMT-2000 air interface technology to be used in Third Generation (3G) wireless systems are: 1) up to 2 Mbps data rate for local area coverage, 2) up to 384 kbps data rate for wide area coverage, 3) highly efficient utilization of the spectrum in contrast to current 1G and 2G systems, and 4) capability to support various multimedia information sources on an ongoing basis. The radio access technology that was finally proposed in January of 1998 to meet these criteria was W-CDMA. W-CDMA is based on Direct Sequence CDMA technology, with a chip rate of 4.096 Mcps. It is designed to be flexible to accommodate third generation services as well as to be adaptable to current GSM systems. This paper presents a background to 3G systems, some key features and technologies of the W-CDMA FDD air interface, and a description of the physical channel and frame structure. iii LIST OF ILLUSTRATIONS Table 1. Key Parameters of W-CDMA 4 Table 2. Physical Channel Format .9 Figure 1. ITU Spectrum Allocation .3 Figure 2. Hierarchical Cell Structure for Smooth Handovers .6 Figure 3. Physical Channel Structure .9 Figure 4. Uplink DPDCH/DPCCH Structures 10 Figure 5. Uplink DPCH Spreading/Modulation 11 Figure 6. Random Access Scheme 12 Figure 7. Uplink PRACH Structure .12 Figure 8. Data Part of PRACH 13 Figure 9. Downlink Spreading/Modulation 14 Figure 10. Downlink DPCH .15 Figure 11. Primary and Secondary CCPCHs 16 Figure 12. Synchronization Channel 17 Figure 13. Test Route .18 Figure 14. Average BER Performance with Variable Chip Rate 20 iv LIST OF ABBREVIATIONS BCCH Broadcast Control Channel BER .Bit Error Rate BPSK . Binary Phase Shift Keying BTS .Base Transceiver Station CDMA .Code Division Multiple Access CCPCH Common Control Physical Channel DLPCH Downlink Physical Channel DPCCH .Dedicated Physical Control Channel DPCH .Dedicated Physical Channel DPDCH . Dedicated Physical Data Channel DS-CDMA Direct Sequence CDMA ETSI .European Telecommunications Standards Institute FACH Forward Access Channel FDD N gôn ngữ C # T rần V ăn T èo tvteo@agu.edu.vn 01/06/2006 N g ôn n g ữ C # G iao diện (Interface) n n n N hư m ột hợ p đồng, đảm bảo hoạt động tốt theo hoạch định G iống class ng gồm toàn hàm trừ u tư ợ ng K hi m ột class thiết đặt (im plem ent) m ột giao diện phải thi cơng tất hàm giao diện • • • • • • T hiết đặt m ột giao diện T ruy xuất hàm giao diện O verride m ộ t thiết đặt giao diện D ùng giao diện thông số T hiết đặt kế thừ a giao diện T hiết đặt lại giao diện 01/06/2006 N g ôn n g ữ C # T hiết đặt m ột giao diện n Cú pháp: [access-modifier] interface interface-name [:base-list] { n n n n interface body } T ên giao diện nên bắt đầu chử I hoa C ác thành viên phần thân bao gồm : m ethods, property, events, indexers K hông thể a: hằng, m ục tin, tác tử , constructor, destructor, kiểu liệu C ác thành viên a từ khóa: abstract abstract,, public public,, protected,, internal protected internal,, private private,, virtual virtual,, override override 01/06/2006 N g ôn n g ữ C # T hiết đặt m ột giao diện interface IStorable public void Write( object obj ){ { Console.WriteLine( obj ); void Read( ); } void Write( object obj); public int Status { int Status { get ; set ;} get { return Status; } }//End interface Istorable set { Status = value; } public class Document : IStorable{ } public void Read( ){ private int Status; Console.WriteLine( “T hi công h àm R ead cù a IS torable” ); } 01/06/2006 }//End class Document N g ôn n g ữ C # T hiết đặt m ột giao diện n T h iết đặt lú c nhiều g iao diện interface ICompressible public void Write( object o b j ){… } { public int S ta tu s {… } //T h i cô n g g ia o d iệ n IC o m p re ssib le void Compress ( ); public void C o m p re ss( ) {… } void Decompress ( ); public void D e co m p re ss( ) {… } }//End interface ICompressible public class Document : IStorable , ICompressible private int Status; } //End class Document { //Thi cô n g g ia o d iệ n IS to b le public void R ead( ){… } 01/06/2006 N g ôn n g ữ C # T hiết đặt m ột giao diện n P h ố i hợ p lú c nhiều g iao diện v m rộ n g public void Write( object o b j ){… } interface IStorableCompressible : public int S ta tu s {… } IStorable , ICompressible // ICompressible { public void C o m p re ss( ) {… } void LogSavedBytes( ); }//End interface IStorableCompressible public class Document : IStorableCompressible public void D e co m p re ss( ) {… } // M rộ n g void L og S av edB ytes( ) {… } private int Status; { // Istorable public void R ead( ){… } 01/06/2006 } // End class Document N g ôn n g ữ C # T ruy xuất hàm G iao diện n T ru y xuất thàn h v iên củ a giao diện IS torable g iố ng thành viên lớ p D ocum ent Document doc = new Document ( ); doc.Status = -1; doc.Read( ); n K h ô ng thể tạo thể giao d iện m ột cách trự c tiếp  T ạo thể giao d iện cách ép (casting) đ ố i tư ợ ng D ocum en t v ề k iểu giao diện IS torable 01/06/2006 N g ôn n g ữ C # //T ạo thể bàng cách ép IStorable iStor = (IStorable)doc; iStor.Status = 0; iStor.Read( ); T ruy xuất hàm G iao diện n T o án tử is: • Cú pháp: expression is type • K iểm tra xem expression (kiểu liệu qui chiếu) ép an tồn kiểu type không n T o án tử as: if( doc is IStorable ) IStorable iStor = (IStorable) doc; Document doc = new Document ( ); • Cú pháp: expression as type • K iểm tra xem expression ép an tồn kiểu type khơng N ếu hợ p lệ trả type N gư ợ c lại trả null 01/06/2006 Document doc = new Document ( ); N g ôn n g ữ C # IStorable iStor = doc as IStorable; if ( iStor != null ) iStor.Read( ); T ruy xuất hàm G iao diện n Interface Abstract • A b stract thiết đặt m ột Interface n ên cũ n g phải thi công tất thành viên củ a Interface • Đ ợ c phép ánh xạ hàm củ a Interface th àn h h àm trừ u tư ợ ng interface IStorable{ abstract class AbsClass : IStorable{ void Read ( ); public abstract void Read ( ); void Write (object obj); public abstract void Write (object obj); } 01/06/2006 } N g ôn n g ữ C # O verride thiết đặt G iao diện public class Note : Document interface IStorable{ void Read ( ); { void Write (object obj); public override void Read ( ){ } //End IStorable … … … … public class Document : IStorable{ } public virtual void Read ( ) public void Write (object obj){ {… … … } … … … … public void Write (object obj) } {… } } //End Note } //End Document 01/06/2006 N g ôn n g ữ C # 10 T hiết đặt G iao diện tư ng m inh interface IStorable{ public class Document : IStorable, ITalk{ void Read ( ); //Thi công IStorable void Write (object obj); public virtual void R ead ( ){… } } //End IStorable public void Write (object obj){… } interface ITalk{ //Thi công ITalk void Read( ); void IT alk R ead ( ){… … } void Talk( ); public void T alk ( ){… … } } } //End Note Document doc = new Document( ); ITalk iTal = doc as ITalk; doc.Read ( ); if( iTal != null) 01/06/2006 N g ôn n g ữ C # iTal.Read( ); 11 Q&A 01/06/2006 N g ôn n g ữ C # 12 Lab 3.1.7 Troubleshooting a Serial Interface Objective • Configure a serial interface on two routers. • Use show commands to troubleshoot connectivity issues. Background/Preparation A DHCP client uses IP broadcasts to find the DHCP server. However, these broadcasts are not forwarded by routers, so in the case of the remote LAN, the workstations will not be able to locate the DHCP server. The router must be configured with the ip helper-address command to enable forwarding of these broadcasts, as unicast packets, to the specific server. Routing between the remote router and the campus router is done using a static route between the remote router and gateway router, and a default route between the gateway router and remote router. Cable a network similar to the one in the diagram above. Any router that meets the interface requirements displayed on the above diagram may be used. This includes the following and any of their possible combinations: • 800 series routers • 1600 series routers 1 - 6 CCNA 4: WAN Technologies v 3.0 - Lab 3.1.7 Copyright  2003, Cisco Systems, Inc. • 1700 series routers • 2500 series routers • 2600 series routers Please refer to the chart at the end of the lab to correctly identify the interface identifiers to be used based on the equipment in the lab. The configuration output used in this lab is produced from 1721 series routers. Any other router used may produce slightly different output. Conduct the following steps on each router unless specifically instructed otherwise. Start a HyperTerminal session as. Note: Refer to the erase and reload instructions at the end of this lab. Perform those steps on all routers in this lab assignment before continuing. Step 1 Configure the routers Configure all of the following according to the chart: • The hostname • The console • The virtual terminal • The enable passwords If there is a problem completing this, refer to the Network Address Translation (NAT) configuration lab. Step 2 Configure the Paris interface as listed Configure the Paris router serial interface as follows: Paris(config)#interface serial 0 Paris(config-if)#ip address 192.168.15.2 255.255.255.0 Paris(config-if)#clockrate 56000 Paris(config-if)#no shutdown Paris(config-if)#exit Paris(config)#exit Step 3 Configure the London interface as listed Configure the London router serial interface as follows: London(config)#interface serial 0 London(config-if)#ip address 192.168.15.1 255.255.255.0 London(config-if)#no shutdown London(config-if)#exit London(config)#exit Step 4 Save the configuration London#copy running-config startup-config Paris#copy running-config startup-config Step 5 Enter the command show interface serial 0 (refer to interface chart) on London London#show interface serial 0 2 - 6 CCNA 4: WAN Technologies v 3.0 - Lab 3.1.7 Copyright  2003, Cisco Systems, Inc. This will show the details of interface serial 0. Answer the following questions: a. Serial 0 is _____________, line protocol is _____________. b. What type of problem is indicated in the last statement? __________________________________________________________________________ c. Internet address is ________________________________ d. Encapsulation ____________________________________ Step 6 Enter the command show interface serial 0 (refer to interface chart) on Paris Paris#show interface serial 0 This will show the details of interface serial 0. Answer the following questions: a. Serial 0 is ___________________, line protocol is___________________. b. Internet address is ___________________. c. Encapsulation William Stallings Data and Computer Communications Chapter 6 The Data Communications Interface Asynchronous and Synchronous Transmission ❚ Timing problems require a mechanism to synchronize the transmitter and receiver ❚ Two solutions ❙ Asynchronous ❙ Synchronous Asynchronous ❚ Data transmitted on character at a time ❙ 5 to 8 bits ❚ Timing only needs maintaining within each character ❚ Resync with each character Asynchronous (diagram) Asynchronous - Behavior ❚ In a steady stream, interval between characters is uniform (length of stop element) ❚ In idle state, receiver looks for transition 1 to 0 ❚ Then samples next seven intervals (char length) ❚ Then looks for next 1 to 0 for next char ❚ Simple ❚ Cheap ❚ Overhead of 2 or 3 bits per char (~20%) ❚ Good for data with large gaps (keyboard) Synchronous - Bit Level ❚ Block of data transmitted without start or stop bits ❚ Clocks must be synchronized ❚ Can use separate clock line ❙ Good over short distances ❙ Subject to impairments ❚ Embed clock signal in data ❙ Manchester encoding ❙ Carrier frequency (analog) Synchronous - Block Level ❚ Need to indicate start and end of block ❚ Use preamble and postamble ❙ e.g. series of SYN (hex 16) characters ❙ e.g. block of 11111111 patterns ending in 11111110 ❚ More efficient (lower overhead) than async Synchronous (diagram) Line Configuration ❚ Topology ❙ Physical arrangement of stations on medium ❙ Point to point ❙ Multi point ❘ Computer and terminals, local area network ❚ Half duplex ❙ Only one station may transmit at a time ❙ Requires one data path ❚ Full duplex ❙ Simultaneous transmission and reception between two stations ❙ Requires two data paths (or echo canceling) Traditional Configurations [...]...Interfacing „ Data processing devices (or data terminal equipment, DTE) do not (usually) include data transmission facilities „ Need an interface called data circuit terminating equipment (DCE) ƒ e.g modem, NIC „ DCE transmits bits on medium „ DCE communicates data and control info with DTE ƒ Done over interchange circuits ƒ Clear interface standards required Characteristics of Interface „ Mechanical... conductor and up the other Differential signaling Value depends on direction of voltage Tolerates more noise and generates less (Unbalanced, e.g RS-232 uses single signal line and ground) ƒ Data encoding depends on data rate ƒ Basic rate 192kbps uses pseudoternary ƒ Primary rate uses alternative mark inversion (AMI) and B8ZS or HDB3 ƒ ƒ ƒ ƒ ƒ ƒ Foreground Reading „ Stallings chapter 6 „ Web pages from... Specification „ (See table in Stallings chapter 6) Local and Remote Loopback Procedural Specification „ E.g Asynchronous private line modem „ When turned on and ready, modem (DCE) asserts DCE ready „ When DTE ready to send data, it asserts Request to Send ƒ Also inhibits receive mode in half duplex „ Modem responds when ready by asserting Clear to send „ DTE sends data „ When data arrives, local modem asserts... Receive Line Signal Detector and delivers data Dial Up Operation (1) Dial Up Operation (2) Dial Up Operation (3) Null Modem ISDN Physical Interface Diagram ISDN Physical Interface „ Connection between terminal equipment (c.f DTE) and network terminating equipment (c.f DCE) „ ISO 8877 „ Cables terminate in matching connectors with 8 contacts „ Transmit/receive carry both data and control ISDN Electrical Specification... Functional ƒ Data, control, timing, grounding „ Procedural ƒ Sequence of events V.24/EIA-232-F „ ITU-T v.24 „ Only specifies functional and procedural ƒ References other standards for electrical and mechanical „ EIA-232-F (USA) ƒ ƒ ƒ ƒ ƒ RS-232 Mechanical ISO 2110 Electrical v.28 Functional v.24 Procedural v.24 Mechanical Specification Electrical Specification „ MINIREVIEW Brain angiogenesis in developmental and pathological processes: regulation, molecular and cellular communication at the neurovascular interface Hye Shin Lee 1,2 , Jiyeon Han 1,2 , Hyun-Jeong Bai 1,2 and Kyu-Won Kim 1,2,3 1 Neurovascular Coordination Research Center, College of Pharmacy, Seoul National University, Korea 2 Research Institute of Pharmaceutical Science, Seoul National University, Korea 3 Department of Molecular Medicine and Biopharmaceutical Sciences, Seoul National University, Korea Development of the brain vasculature Blood vessels form via two distinct processes: vasculo- genesis and angiogenesis. Vasculogenesis involves the proliferation and differentiation of mesoderm-derived angioblasts into endothelial cells [1]. Before the heart even begins to beat, the primary vascular plexus is formed throughout the body by vasculogenesis [2]. The extracerebral vascular plexus is established by vasculo- genesis within the brain vasculature [2]. Early in embryogenesis, angioblasts invade the head region and form the perineural vascular plexus, which ultimately covers the entire neural tube [3]. After the primary vas- cular plexus is formed by vasculogenesis, a more com- plex vascular network is established via angiogenesis (i.e. the production of vessel branches from pre-exist- ing vessels). Indeed, the vascular network of the brain is predominantly formed by angiogenesis. During this Keywords astrocyte; barriergenesis; blood–brain barrier; brain angiogenesis; endothelial cell; neuron; neurovascular interface; pericyte; perivascular macrophage; smooth muscle cell Correspondence K W. Kim, Neurovascular Coordination Research Center, College of Pharmacy, Seoul National University, Seoul 151-742, Korea Fax: +82 2 885 1827 Tel: +82 2 880 6988 E-mail: qwonkim@plaza.snu.ac.kr (Received 19 February 2009, revised 6 May 2009, accepted 10 June 2009) doi:10.1111/j.1742-4658.2009.07174.x The vascular network of the brain is formed by the invasion of vascular sprouts from the pia mater toward the ventricles. Following angiogenesis of the primary vascular network, brain vessels experience a maturation pro- cess known as barriergenesis, in which the blood–brain barrier is formed. In this minireview, we discuss the processes of brain angiogenesis and bar- riergenesis, as well as the molecular and cellular mechanisms underlying brain vessel formation. At the molecular level, angiogenesis and barriergen- esis occur via the coordinated action of oxygen-responsive molecules (e.g. hypoxia-inducible factor and Src-suppressed C kinase substrate ⁄ AKAP12) and soluble factors (e.g. vascular endothelial growth factor and angiopoie- tin-1), as well as axon guidance molecules and neurotrophic factors. At the cellular level, we focus on neurovascular cells, such as pericytes, astrocytes, vascular smooth muscle cells, neurons and brain macrophages. Each cell type plays a unique role, and works with other types to maintain environ- mental homeostasis and to respond to certain stimuli. Taken together, this minireview emphasizes the importance of the coordinated action of mole- cules and cells at the neurovascular interface, with regards to the regulation of angiogenesis and barriergenesis. Abbreviations Ang-1, angiopoietin-1; AQP4, aquaporin4; BBB, blood–brain barrier; BDNF, brain-derived neurotrophic factor; CNS, central nervous system; HIF, hypoxia-inducible factor; NGF, nerve growth factor; NT, neurotrophins; SEMA, semaphorin; Week 1  Chapter 1: Windows Forms and the User Interface  Chapter 2: Configuring Controls 1 Chapter 1: Windows Forms and the User Interface  Lesson 1: Adding and configuring Windows Forms  Adding Forms to the project  Properties of Windows Forms  Creating non-rectangular Windows Forms  Lesson 2: Managing control layout with container controls Slide 2 Adding Forms to the project  At design time  To add a new Form: right-click to the project shown in Solution Explorer, select Add\Windows Form  To add a existing Form: right-click to the project shown in Solution Explorer, select Add\Existing Item (choose file .cs)  At run time  Form1 myForm; myForm = new Form1(); myForm.Show(); Chapter 1 - Lesson 1: Adding and configuring Windows Forms Slide 3 Properties of Windows Forms  Note: p.11 p.9 p.11 Chapter 1 - Lesson 1: Adding and configuring Windows Forms Slide 4 Properties of Windows Forms (cont.)  AcceptButton property  CancelButton Property p.11 p.10 Chapter 1 - Lesson 1: Adding and configuring Windows Forms Slide 5 Create a non-rectangular form (p.15)  For advanced visual effects  To create a non-rectangular form:  In Form_Load event, change the Region property  Create a new instance of the GraphicsPath class (in System.Drawing.Drawing2D namespace)  Create the new Region from it Chapter 1 - Lesson 1: Adding and configuring Windows Forms A GraphicsPath represents a series of connected lines and curves A GraphicsPath may be composed of any number of figures, like ellipse Slide 6 Example: Create a non-rectangular form GraphicsPath myPath = new GraphicsPath(); // Adds an ellipse to the graphics path that inscribes // the rectangle defined by the form's width and height myPath.AddEllipse(0, 0, this.Width, this.Height); // Creates a new Region from the GraphicsPath Region myRegion = new Region(myPath); // Sets the form's Region property to the new region this.Region = myRegion; Chapter 1 - Lesson 1: Adding and configuring Windows Forms Exercise 1,2 p.16,p.17 Slide 7 Managing control layout with container controls  Container controls  Panel control  GroupBox control  TabControl control  SplitContainer control  FlowLayoutPanel control  TableLayoutPanel control  Exercise: Practice with Container Controls (p.35-38) Chapter 1 - Lesson 2: Managing control layout with container controls Slide 8  Panel control (p.26)  Scrollable control  Supports horizontal and vertical scroll bars  No caption Chapter 1 - Lesson 2: Managing control layout with container controls Slide 9  GroupBox control (p.25)  Does not provide scrollbars  Have a caption (Text property)  The most common use: grouping RadioButton controls Chapter 1 - Lesson 2: Managing control layout with container controls Slide 10 [...]... Creating and Configuring command and text controls Slide 21 Button control (cont.)  Button control: Mouse events: MouseDown (p.64)  Demo p.64 Some other controls are the same  Chapter 2 - Lesson 2: Creating and Configuring command and text controls Slide 22 TextBox control (p.73)  TextBox control properties  Exercise 5, 6 Module 1 Chapter 2 - Lesson 2: Creating and Configuring command and text... Controls in Windows Forms Slide 17 Smart Tags (p.56)  Some controls expose their most common tasks through smart tags When present, smart tags appear as small boxes in the upper right-hand corner of the control A Combo box with a smart tag Chapter 2 - Lesson 1: Configuring Controls in Windows Forms Slide 18 Document Outline Window  Document Outline Window (p.57)    Displays all of

Ngày đăng: 05/11/2017, 03:40