| Electronic Components Datasheet Search |
|
ISDN Datasheet(PDF) 3 Page - Texas Instruments |
|
|
|||||||||||||||||||||||||||||
ISDN Datasheet(HTML) 3 Page - Texas Instruments |
|
3 / 14 page ![]() 10 Architectural Description 11 INTRODUCTION This description defines the software required to implement the ISDN Basic Rate Interface on the HPC family of micro- controllers including the HPC16400 which has onboard hardware specifically designed for Data Communication and ISDN applications The software consists of the following main parts shown in overview in Figure 11 HPC Executive providing an operating environment and services for the ISDN software and for additional applica- tion software written by OEM users of the HPC IO Drivers interfacing to the DMAHDLC controllers on the HPC16400 and to the TP3420 ‘‘S’’ Interface Device Data Link Layer Software implementing the CCITT Q921 and X25 link access procedures (LAPD and LAPB) Network Layer Software implementing the Protocol Con- trol Procedures defined in the CCITT Q931 standard Demonstration Call Control Module allowing a develop- ment engineer at a terminal to make and receive ISDN phone calls which exercise the above software Tracer Module allowing a development engineer at a ter- minal to monitor the operation of the above software Management Entity Module 12 SOFTWARE ARCHITECTURAL PRINCIPLES 121 Modular Multitasking Environment Eack layer or function is written as a separate software task Intertask communications and the interface between tasks and IO drivers is by means of mail messages and sema- phores which are managed by the multi-tasking HPC Exec- utive This modular design and well defined intertask interface make it easy for users to interface application-dependent software to the modules provided The services of the HPC Executive (mail semaphores timers memory management) facilitate the writing of software tasks and IO drivers These services are available to all tasks and to interrupt-lev- el drivers 122 Event-Driven State-Machine Architecture Telecommunication software typically involves many invo- cations of the same code (one per call one per logical con- nection etc) and requires a particular software architecture tasks must be structured as event-driven state machines Each task has one or more mailboxes and operates by pick- ing up mail one message at a time from the mail queue and processing the message to completion before returning for the next mail message Each ‘‘entity’’ within a task (each call each logical connec- tion etc) has a state block indicating its current state After picking up a mail message the task identifies the entity in- volved in the message accesses the state block for that entity processes the message based on the state of the entity and finally sets the state block to the new state of the entity TLDD10077 – 2 FIGURE 11 HPC16400 Software for ISDN 2 |
|
|
Link URL |
| Does ALLDATASHEET help your business so far? [ DONATE ] |
About Alldatasheet | Advertisement | Contact us | Privacy Policy | Link to Datasheet | Link Exchange | Manufacturer List All Rights Reserved©Alldatasheet.com |
| Russian : Alldatasheetru.com | Korean : Alldatasheet.co.kr | Spanish : Alldatasheet.es | French : Alldatasheet.fr | Italian : Alldatasheetit.com Portuguese : Alldatasheetpt.com | Polish : Alldatasheet.pl | Vietnamese : Alldatasheet.vn Indian : Alldatasheet.in | Mexican : Alldatasheet.com.mx | British : Alldatasheet.co.uk | New Zealand : Alldatasheet.co.nz |
|
Family Site : ic2ic.com |
icmetro.com |