WO1997020439A1 - Telecommunications switch having a universal applications program interface for stantardized interactive call processing communications - Google Patents
Telecommunications switch having a universal applications program interface for stantardized interactive call processing communications Download PDFInfo
- Publication number
- WO1997020439A1 WO1997020439A1 PCT/US1996/018959 US9618959W WO9720439A1 WO 1997020439 A1 WO1997020439 A1 WO 1997020439A1 US 9618959 W US9618959 W US 9618959W WO 9720439 A1 WO9720439 A1 WO 9720439A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- ppl
- event
- switch
- message
- predetermined
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/58—Arrangements providing connection between main exchange and sub-exchange or satellite
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/12—Protocol engines
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q11/00—Selecting arrangements for multiplex systems
- H04Q11/04—Selecting arrangements for multiplex systems for time-division multiplexing
- H04Q11/0407—Selecting arrangements for multiplex systems for time-division multiplexing using a stored programme control
- H04Q11/0414—Details
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/42—Circuit arrangements for indirect selecting controlled by common circuits, e.g. register controller, marker
- H04Q3/54—Circuit arrangements for indirect selecting controlled by common circuits, e.g. register controller, marker in which the logic circuitry controlling the exchange is centralised
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/42—Circuit arrangements for indirect selecting controlled by common circuits, e.g. register controller, marker
- H04Q3/54—Circuit arrangements for indirect selecting controlled by common circuits, e.g. register controller, marker in which the logic circuitry controlling the exchange is centralised
- H04Q3/542—Logic circuits or arrangements therefor
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/42—Circuit arrangements for indirect selecting controlled by common circuits, e.g. register controller, marker
- H04Q3/54—Circuit arrangements for indirect selecting controlled by common circuits, e.g. register controller, marker in which the logic circuitry controlling the exchange is centralised
- H04Q3/545—Circuit arrangements for indirect selecting controlled by common circuits, e.g. register controller, marker in which the logic circuitry controlling the exchange is centralised using a stored programme
- H04Q3/54575—Software application
- H04Q3/54583—Software development, e.g. procedural, object oriented, software generation, software testing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/58—Arrangements providing connection between main exchange and sub-exchange or satellite
- H04Q3/62—Arrangements providing connection between main exchange and sub-exchange or satellite for connecting to private branch exchanges
- H04Q3/625—Arrangements in the private branch exchange
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/03—Protocol definition or specification
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13003—Constructional details of switching devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13034—A/D conversion, code compression/expansion
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/1305—Software aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13056—Routines, finite state machines
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/1309—Apparatus individually associated with a subscriber line, line circuits
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13093—Personal computer, PC
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13096—Digital apparatus individually associated with a subscriber line, digital line circuits
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13103—Memory
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13106—Microprocessor, CPU
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13176—Common channel signaling, CCS7
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13204—Protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13216—Code signals, frame structure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/1322—PBX
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13299—Bus
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/1332—Logic circuits
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/1334—Configuration within the switch
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13405—Dual frequency signaling, DTMF
Definitions
- the present invention relates generally to the field of telecommunications and, more specifically, to a universal applications program interface (API) for standardized interactive call control processing with a programmable telecommunication switch and a host computer supporting various telecommunications applications.
- API applications program interface
- Programmable telecommunication switches are used in a wide variety of applications such as voice messaging, telemarketing services and the like.
- a computer that runs a telecommunications application program.
- a customer may programmable switch is usually controlled by a host device, which is typically a either purchase a commercially available application program that is compatible with the host and switch hardware or may elect to write a custom program.
- a programmable switch is connected to a public telephone network by one or more analog trunks or digital spans (e.g., a Tl span) which are terminated at the switch.
- the switch may also terminate one or more "lines" which are connected to devices such as telephone sets. Communication over any given trunk, span or line is carried out in accordance with an assigned signalling protocol.
- Each of the signalling protocols requires predetermined host-to-switch call control processing protocols to be established, each protocol including the exchange of one or more constant messages.
- communications switches must be capable of supporting extremely large number of these specific host- to-switch command messages and associated protocols.
- each signalling protocol has associated with it one or more different message sets stored and indexed at the host as well as at the switch. The message sets and resulting host-to-switch protocol are also dependent upon specific telecommunications applications requirements, such as the amount and type of information an apphcation requires for it to appropriately control the switch to support a particular signalling protocol.
- conventional programmable switches may be connected between the public telephone network and other devices such as a voice messaging system. Because such devices may perform specialized functions and are not intended to connect directly to the public telephone network, they do not typically adhere to standard signalling protocols. Thus, for a user to be able to control the programmable switch in such a fashion that proper communication is maintained both, with the public telephone network and with other devices connected to the switch, complex and va ⁇ ed API signalling protocol requirements must be satisfied.
- Conventional communications switches implement numerous specific sets of API messages to support these va ⁇ ed requirements As a result of the implementation of constant messages and the various telecommunications applications and signalling protocol requirements, there has been no standardization of the interface between the host applications and the telecommunications switch. This has led to increased cost in developing the necessary hardware and software to support specific API protocols to satisfy host applications requirements as well as signalling protocol requirements for each trunk, span, and line.
- the present invention is a standardized host-to-switch application program interface (API) for performing call control processing, capable of being customized to meet telecommunications application and network signalling protocol requirements.
- the universal API comprises one or more generic messages having programmable fields for transmitting commands, status, and data between the host application and the switch.
- the present invention further comprises a programmable telecommunication switch that provides a user with the ability to define a desired API protocol, either "standard" or custom in nature, for performing any desired switching functions.
- the present invention includes a protocol development environment which enables a user to define a separate finite state machine for each port provided by the switch.
- Each finite state machine may be independently defined by combining a series of elementary processing steps, called atomic functions, into primitives, which are in turn combined with states and events to define the desired state machine.
- Such state machines may include atomic functions configured to generate predetermined messages under predetermined conditions and containing predetermined information.
- Such state machines may further include the ability to respond to state events that include the receipt of generic API messages configured to provide the state machine with information from the host application.
- the present invention may serve as a development tool for creating customized API protocols having customized standard messages supporting telecommunications applications such as personal communications services (PCS), 800/900 service, voice mail, telemarketing, among others.
- PCS personal communications services
- the present invention may also be used to control or manage a wide variety of communications services within a programmable switch through the transfer of the generic API messages, including conferencing, voice recorded announcements, tone generation, tone reception, call progress analysis, voice recognition, voice compression and fax encoding/decoding.
- the universal API of the present invention may be implemented to achieve communications internal to the switch as well.
- the standardized messages of the universal API may be used to support communications between any software layer within the switch.
- the generic message structure of the present invention enables additional call processing features to be added to the telecommunications switch that the host can initiate without implementing additional content-specific API messages dedicated to that feature.
- This enables the creation of customized API message protocols that can grow beyond the limitations of specific messages for specific features and functions.
- Another advantage of the generic message structure of the present invention is that it provides the commonality and flexibility necessary to be a standardized interface for application development. This significantly reduces the complexity of the host/switch communications interface and eliminates the cost of supporting an interface composed of numerous specialized messages.
- Another advantage of the present invention is that it provides the user with the ability to transmit and receive information to all software layers of the switch using standardized messages. Significantly, this eliminates the burden of having to store large numbers of distinct messages for managing dissimilar functions performed by the same or different software layers of the switch. Thus, the large message sets stored and indexed in conventional switches is eliminated by the present invention.
- Another advantage of the present invention is the increased degree of interaction with the host that can be achieved simply by introducing at various processing points an atomic function that sends and receives data into numerous locations in the switch.
- Another advantage of the present invention is that it enables a user to create multiple network signalling protocols by creating separate state machines to address each variation of a signalling protocol.
- the universal API may be programmed to achieve the necessary communications to support each of these protocol-specific state machines.
- the structure of the messages comprising the host-to-switch interface may remain unchanged despite the multiple signalling protocols supported by the switch.
- Figure 1 is a block diagram of a programmable telecommunications switch which may be programmed by a user in accordance with a preferred embodiment of the present invention
- Figure 2 is diagram which depicts the layers of software used to control the switch of Figure 1 ;
- FIGS 3A and 3B depict some of the specific features and functions associated with each of the software layers depicted in Figure 2;
- Figure 4 is a block diagram of a finite state machine development environment constructed in accordance with a preferred embodiment of the present invention
- Figure 5 is a block diagram illustrating the structure and contents of a generic
- FIG. 6 is a block diagram of a PPL Event Indication Acknowledgement and PPL Event Request Acknowledgment message of the present invention.
- Figures 7A and 7B are a state diagram of a finite state machine for providing call control processing utilizing the universal API of the present invention to support a highly interactive host telecommunications application requirement;
- Figure 7C is an interface diagram of the universal API supporting the call control processing illustrated in Figures 7A and 7B;
- Figures 7D and 7E are a diagram of the finite state machine of Figures 7A and 7B in which each series of atomic functions is defined as a primitive;
- Figures 7F and 7G are tables showing the co ⁇ espondence between the atomic functions, primitives and states of Figures 7A-7E;
- Figures 8A and 8B are a state diagram of a finite state machine for providing call control processing utilizing the universal API of the present invention to support a limited interactive host telecommunications application requirement;
- Figure 8C is an interface diagram of the host-to-switch API generated by the cal control processing illustrated in Figures 8 A and 8B;
- Figures 8D and 8E are a diagram of the finite state machine of Figures 8A and 8B in which each series of atomic functions is defined as a primitive;
- Figures 8F and 8G are tables showing the correspondence between the atomic functions, primitives and states of Figures 8A-8E;
- Figure 9 is a functional block diagram illustrating an exemplary process flow to create a PPL Event Indication message;
- Figure 10 is a block diagram of the message buffer created by an Layer 4 PPL processor during the creation of the PPL Event Indication message of Figure 9; and Figure 11 is a functional block diagram illustrating an exemplary process flow to create a PPL Event Request message.
- FIG. 1 shows a commercially available personal computer (PC) 102 which includes a PC central processing unit (CPU) 104 and a hard disk drive 106 interconnected by a PC input/output (I/O) bus 108 and a PC power bus 109.
- PC personal computer
- the 102 is preferably a PC-AT , sold by International Business Machines (IBM), or a compatible thereof. Other personal computers having more memory or more powerful CPUs than the PC-AT may also be used.
- the PC 102 preferably operates under an application-oriented operating system, such as DOS or UNIX .
- the PC 102 consists of a chassis or housing in which a motherboard is mounted, along with the disk drive 106 and other optional assemblies such as floppy disk drives, modems and the like.
- the PC CPU 104 is mounted on the motherboard. which includes a series of edge connectors into which other boards (cards) may be inserted and thereby connected to the PC I/O and power busses 108 and 109.
- a programmable telecommunication switch 110 resides within the PC 102.
- a CPU/matrix card 112 is inserted into one of the slots on the motherboard and thus connected to the busses 108 and 109.
- the CPU/matrix card 112 is interconnected with a digital (Tl) line card 114, a digital (El) line card 115, a digital signal processing (DSP) card 116, a packet engine card 117, an analog (universal) line card 118 and a terminator card 119 by four busses: a high level data link control (HDLC) or interprocessor bus 120; a time division multiplex (TDM) bus 122; a line card (LC) status/control bus 124; and a timing/control bus 126.
- a battery/ring voltage bus 128 supplies battery voltage (48VDC) and ringing voltage (109VAC) to the analog line card 118.
- the terminator card 119 serves to physically terminate busses 120, 122, 124, 126 and 128.
- the line cards 114, 115 and 118 and the DSP card 116 are all connected to and receive their basic operating power from the PC power bus 109. Although only one digital (Tl) line card 114, one digital (El) line card 115 and one analog line card 118 are depicted, it should be understood that additional line cards of any type may be added subject to two physical limitations: (1) the maximum switching capacity of the CPU/matrix card 112, and (2) the physical space within the chassis of the PC 102.
- An external host 130 which may comprise a separate personal computer, workstation or other computer, may optionally be connected via a communication channel 132 to the CPU/matrix card 112.
- the CPU/matrix card 112 preferably includes a conventional RS-232 compatible interface for connecting the channel 132.
- the external host 130 preferably operates under an application-oriented operating system.
- the switch 110 can reside on a passive backplane (no PC CPU 104 or disk 106 present) from which its receives electrical power and be controlled by the external host 130.
- the present invention may be implemented in other processing platforms such as the expandable telecommunications switch disclosed in copending patent application, serial number 08/207,931 , titled Expandable Telecommunications System, assigned to the assignee of the present application and which is hereby incorporated by reference in its entirety.
- An external battery/ring voltage supply 131 is connected via a path 133 to the terminator card 119.
- Supply 131 may comprise, for example, a commercially available power supply.
- digital (El) line card 115 the DSP card 116 and the packet engine card 117
- Details regarding the construction of the various cards shown in Figure 1 are set forth in U.S. Patent No. 5,321 ,744, titled Programmable Telecommunications Switch for Personal Computer, assigned to the assignee of the present application and which is hereby incorporated by reference in its entirety.
- Digital (El) line card 115 is preferably constructed using similar hardware to that disclosed for Tl line card 114, except for differences in conventional circuitry which allow line card 115 to terminate El spans as opposed to Tl spans.
- Figure 2 is a layer model of the software used to control the programmable switch 110 of Figure 1.
- the lefthand column of Figure 2 shows seven layers defined in the Open Systems Interconnection (OSI) reference model.
- the righthand column of Figure 2 shows five layers used to control switch 2 and their general correspondence to the OSI model.
- OSI Open Systems Interconnection
- the Application Layer 5. which co ⁇ esponds generally with the Application layer of the OSI model, represents application software which typically runs on either the PC CPU 104 or the external host 130.
- Application Layer 5 software may be used to implement any of a number of desired telecommunications services such as toll free (800) service, voice mail, automatic call distribution (ACD), to name but a few.
- Application Layer 5 may communicate with any other layer of the programmable switch through the application program interface (API) of the present invention.
- API application program interface
- the API manages communications over communication channel 132.
- the API manages call control processing communications over PC I/O bus 108.
- Call Management Layer 104 which corresponds generally with the Presentation, Session and Transport layers of the OSI model, represents software which runs on the CPU/matrix card 12.
- Call Management Layer 4 is responsible for performing centralized call processing functions and providing a common interface to Application Layer 5 regardless of the type or types of network signalling protocols which may be used within the switch 102. Typically, Call Management Layer 4 performs functions which are required following call setup.
- Network Signalling Protocol Layer 3 co ⁇ esponds generally with the Network layer of the OSI model.
- Network Signalling Protocol Layer 3 runs either on the CPU/matrix card 112 or on line cards which include their own microprocessors, such as line cards 114 or 115 or packet engine card 117, and is responsible for in and out-of-band network signalling supervision as well as network protocol level control of incoming and outgoing calls.
- Link Layer 2 co ⁇ esponds generally with the Data Link layer of the OSI model.
- Link Layer 2 software runs on the CPU/matrix card 112, the line cards which include their own microprocessors, the DSP card 1 16 or the packet engine card 1 17 (each of which includes its own microprocessor) and is responsible for the detection as well as physical transfer of network signalling information across a network or line interface. Finally, the Physical Layer 1 co ⁇ esponds to the Physical layer of the OSI model. Line cards 114. 115 and 118 provide physical Tl , El and analog electrical interfaces, respectively, to the switch 110.
- Figures 3A and 3B are a tabular listing of representative features and functions provided by each of the software Layers 2-5 of Figure 2.
- the present invention may be used as a development tool to develop suitable software to implement any of the features and functions shown in Figures 3A and 3B.
- Illustrative examples of the use of the present invention in the context of each of Layers 2-5 are set forth in U.S. Patent No. 5,426,694, assigned to the assignee of the present invention, herein incorporated by reference in its entirety.
- Figure 4 is an overall block diagram of a finite state machine development environment, constructed in accordance with a prefe ⁇ ed embodiment of the present invention, which enables a customer or user to create and define finite state machines for performing desired telecommunications functions, controlled by one or more applications through the universal API of the present invention.
- the term state refers to a number which represents the cu ⁇ ent "context" for a particular channel or port.
- normal states can be wait states (i.e. , a SEIZE ACK state, a condition in which further action is suspended until the occu ⁇ ence of a particular event) or stable states (i.e. , a conversation is taking place).
- Internal states are used to test conditions and effectively operate as decision branches. Normal and internal states may be specified by a customer or user, in accordance with present invention, to define a finite state machine for performing a desired function. Blocking states are generated automatically by the present invention and are used, on a channel-by-channel basis, in connection with the management of off-board resources.
- An event is a number which identifies a condition which is accepted by a particular state. Data may be associated with an event.
- An atomic fiinction is one which performs an elementary task such as setting a timer.
- User-specified data may be associated with an atomic function.
- a primitive is a predetermined sequence of atomic functions which is invoked upon the occu ⁇ ence of a particular event. Users may create or define primitives from a library of available atomic functions. In a prefe ⁇ ed embodiment, each primitive may contain up to 20 atomic functions.
- a state/event table defines the valid events for a particular state and the primitive which is invoked upon the occu ⁇ ence of each such event.
- a state/event table may contain up to 100 states and up to 20 events per state.
- a primitive table defines the primitives which are used by a state/event table.
- a primitive table may contain up to 200 primitives.
- a protocol is defined as the association of various types of tables, the least of which is a state/event table and primitive table, and is identified by a protocol ID (a number).
- An API protocol is defined as the host-to-switch control protocol between host applications and software layers of the switch.
- a program protocol language (PPL) is a programmable environment for managing network signalling protocols and communications services.
- a data block such as those denoted by reference numbers 40a, 40n, is assigned for each channel (port) 0...n of the switch.
- Each data block 40a, 40n contains the following information pertaining to its respective channel: the cu ⁇ ent state of the channel; a pointer to an active state/event table; a pointer to an active primitive table; a pointer to an assigned state/event table; and a pointer to an assigned primitive table.
- the active state/event table and active primitive table pointers are pointing, as indicated by the phantom lines, to tables which are associated with a resident protocol 0, denoted by reference number 442a.
- the assigned state/event table and assigned primitive table pointers for channel 0 are pointing to tables which are associated with a dynamically loaded, customer-defined protocol 1 , denoted by reference number 444a.
- resident protocols l ...n 442b, 442c
- downloaded, customer-defined protocols n-(- l...m 444b, 444c
- the resident protocols 442a-442c represent preprogrammed or "standard” protocols, which are typically provided by a manufacturer with a switch.
- customer-defined protocols n + l ...m are created by a customer or user and may be completely "custom” or "proprietary” in nature.
- a layer dependent atomic function library 446 is connected to provide information to a state machine engine 448.
- State machine engine 448 is also connected to receive the active state/event table pointer and active primitive table pointer from each of data blocks 440a-440n. Also, as denoted by reference number 450, utilities are provided for layer dependent environment support.
- the function of the state machine engine 448 is to drive each channel in accordance with its assigned protocol, which is defined by the assigned state/event table and assigned primitive table. Upon the occu ⁇ ence of a valid event for a normal state, a primitive is invoked in accordance with the entries in the assigned state/event table. The state machine engine 448 uses the atomic function library 446 to perform the atomic functions represented by the invoked primitive.
- the state machine engine 448 will drive through any necessary internal states, automatically generating appropriate blocking states, until the channel once again reaches a normal state. At that time, processing by the state machine engine 448 is complete until the occu ⁇ ence of another valid event.
- Each channel is initially assigned one of the customer-defined protocols or one of the preprogrammed protocols. This is accomplished by the transmission of an API message from the Application Layer 5 to the Call Management Layer 4, which in turn issues an appropriate message to Layer 3 which may also be configured in accordance with the API of the present invention.
- the assigned state/event table pointer and assigned primitive table pointer point to the protocol which was last assigned.
- a customer may assign a desired one of the available protocols by simply specifying the appropriate pointers in each data block.
- the present invention advantageously permits the customer to assign, on a channel-by-channel basis, a desired protocol from among multiple protocols resident within a single switch.
- each channel always has a valid protocol (e.g., one of the resident protocols 442a-442c) assigned to it.
- the active state/event table and active primitive table pointers which are provided to the state machine engine 448, point to the protocol which is cu ⁇ ently controlling the channel.
- the protocol assigned to a particular channel is not necessarily permanent and may be dynamically changed in real time in response to the occu ⁇ ence of a specified event, as described in detail in connection with Figure 7.
- the atomic functions provided by the library 446 represent elementary functions, customers or users are advantageously able to implement desired changes in protocols without substantial, or possibly any, changes to the underlying code.
- the environment support utilities are provided to simplify protocol development for the customer or user.
- the utilities provide ready-to-use resource management functions (e.g. , timers) which greatly simplify the state machine logic required to implement desired protocols. Different utilities are preferably provided for each software layer since the resources required by each layer may be different.
- call processing control communications between the Application Layer 5, typically residing on external host 130, and the other layers of switch 102 illustrated in Figure 2 is conducted though the transfer of generic messages of the universal API of the present invention.
- a single message type, refe ⁇ ed to as the PPL Event Request message is used to transfer all call control processing commands and data from the host application (Layer 5) to the telecommunications switch (all other software layers).
- a single message, refe ⁇ ed to as the PPL Event Indication message is used to transfer all call control processing status and data from the telecommunications switch to the host applications.
- the programmable switch of the present invention enables a user to define and assign a desired applications program interface protocol, either "standard" or custom in nature, for performing various switching functions to accommodate any of the above requirements.
- a PPL Event Request message is sent from the host to the switch to initiate a host event on a PPL component with optional ICB data.
- the PPL Event Request message is the only call control processing message passed from the host to the switch and, in the prefe ⁇ ed embodiment, having the format of message 500 illustrated in Figure 5.
- the PPL Event Request message comprises a number of fields and subfields, each of which is described below.
- PPL Event Request message includes a frame byte 502 having a constant value identifying it as the first byte of a frame.
- Message length field 504 contains the length of the particular PPL Event Request message. This is necessary due to the ability of the generic API messages of the present invention to include optional fields, changing the length of the message. Typically the length field value does not include the frame byte 502.
- a message type field 506 contains a constant value identifying the particular message as a PPL Event Request message.
- the message type field is constant for all PPL Event Request messages.
- Sequence number field 508 is a specific numeric identifier assigned to each PPL Event Request message that is generated by the host application. This value is used to distinguish between different PPL Event Request messages transmitted from the host to the switch. For example, when the host acknowledges the receipt of a PPL Event Request message, it includes the sequence number in its acknowledgement to identify which of the PPL Event Request messages is associated with the status information contained within the acknowledgement.
- PPL component ID 510 is a one word field that identifies which PPL component implemented in the switch is referenced by a particular PPL Event Request message 500.
- the universal API of the present invention provides the ability to perform multiple levels of addressing.
- an address element field 514 is provided to identify which instantiation(s) of that PPL component state machine is(are) being referenced.
- the PPL Event Request message provides the ability to include any number of address element fields 514, and thus may simultaneously communicate with multiple instantiations of a single PPL component state machine.
- the total number of address element fields 514 included in a PPL Event Request message is provided in address element count field 512.
- address element field 514 contains a number of subfields for further identifying which state machine instantiation is to receive the PPL Event Request message.
- an address element type field 516 is provided to reference the hierarchial components of the switch that may contain or be associated with the desired state machine instantiation. In the above example of an El PPL state machine instantiation, the address element type field 516 indicates which span and channel the state machine instantiation is associated with.
- An address information subfield 520 provides specific addresses for each of the hierarchial components indicated in the address element type field 516. Since the addressing information contained in field 520 varies in accordance with the type of device addressed, the length of the AE field 514 may vary and thus is provided in length subfield 518.
- the PPL event ID field 522 provides the switch with a user-defined PPL event ID that the switch recognizes as being associated with the particular request.
- the recipient PPL component maps the unique PPL event ID to a PPL event that is unique to that PPL component.
- Each PPL Event Request message may also contain one or more data fields in the form of information control blocks (ICB)s. ICBs are defined for each PPL component based upon the software layer and the communications protocol supported by that PPL component. Thus, any signalling information may be passed between the host and switch using the generic, programmable messages of the present invention. Also referring to Figure 5, a PPL Event Indication message is sent from the switch to the host by a PPL component to report an event at the ports to the host with optional ICB data.
- ICB information control blocks
- the PPL Event Indication message is the only call control processing message passed from the switch to the host and in the prefe ⁇ ed embodiment, has the same format as the PPL Event Request message illustrated in Figure 5. Except as noted below, the fields of the PPL Event Indication message are identical to and perform the same functions as, the analogous fields of the PPL Event Request message discussed above.
- the address element field(s) indicate which instantiation of a particular state machine is actually invoking the atomic function that generates the PPL event indication message.
- the PPL event ID field 522 is a specific value representing the occu ⁇ ence of a specific event in the switch that results in the PPL Event Indication message being sent from the PPL component state machine As noted, this is managed with an atomic function that is programmed to send the particular PPL Event Indication message in response to the occu ⁇ ence of a particular event, the PPL Event ID included in the message being programmed by the user.
- the PPL components can be layer specific, function specific, interface specific, protocol specific, or channel specific. This enables a host Layer 5 telecommunications application to be as interactive as desired or necessary, accessing each layer of the switch and managing each PPL component regardless of where the component is located. An application can therefore use the universal API interface to manage any PPL component. This provides a consistent and predictable means for managing every PPL component in the switch, regardless of what level of processing is being performed, ranging from, for example, a very detailed signalling analysis, to network signalling, to high-level call routing, to call management connection functions
- the manner in which the data is identified and passed to the host includes the implementation of one or more atomic functions configured to store and retrieve data of a certain type to specific memory locations in conjunction with one or more atomic functions that generate a gene ⁇ c PPL Event Indication providing the host with all previously stored data
- atomic functions may be configured to pass data in the PPL Event Indication message.
- a separate atomic function may be implemented to transfer specific types of data in a PPL event indication message. The short-hand notation for depicting the PPL Event Request and the PPL
- Event Indication messages is shown in on the bottom of Figure 5.
- the telecommunications switch responds to the PPL Event Request with a PPL Event Request Response message having the format of message 600.
- the host applications responds to the PPL Event Indication message with a PPL Event Indication Acknowledge message, also having the format illustrated in Figure 6.
- Generic acknowledgement message 600 includes a frame byte 602, length byte 604, message type 606, and sequence number 608, all of which perform the same function as the co ⁇ esponding fields in the PPL Event Request message 500.
- a status field 610 provides the recipient with message- specific status information. The short-hand notation for depicting the PPL Event
- the first example illustrates a universal API for managing host-to- switch communications when the telecommunications switch is controlled by a highly interactive host application Layer 5 to perform interactive voice announcements.
- the second example illustrates a universal API for managing host-to-switch communications when the host application Layer 5 has limited interaction with the telecommunications switch to perform the same function.
- a state is depicted as a circle
- an atomic function is depicted as a rectangular box
- an event is represented by a word abbreviation located along a path leading out of a state.
- Information shown in parentheses in an atomic function represents arguments or data that are associated with that function. Reference numbers are provided below in parentheses when necessary to avoid confusion with other numeric descriptors.
- Figures 7A-7B illustrate an example of an application of the present invention in Call Processing Layer 4 with a high level of interaction required by the host application layer 5.
- the present invention is used to implement a protocol for providing host application decisionmaking throughout the performance of an interactive voice response to an incoming call.
- the protocol begins with the associated channel (channel 1) in normal state
- the atomic function af35 is performed. As noted in its descriptor, the Layer 4 PPL event
- L4PPLev is received from network signalling protocol layer 3 (L3), reporting that it has detected an incoming call (SETUP NDICATION) .
- the number 50 in the parenthetical preceding the message descriptor is the PPL event ID assigned to that event by the Layer 4 PPL.
- the PPL component state machine in Figure 7A leaves idle state 702 and performs atomic function aD5 (704).
- Atomic function af35 (704) operates to notify the host application (Layer 5) of the event, assigning to the event a PPL event ID of 1.
- the host application interprets this PPL event ID (the number 1) as a notification of an incoming call.
- atomic function 35 (704) generates a PPL Event Indication message 701 to notify the host of the incoming call.
- This PPL Event Indication message has the following format:
- the PPL component ID indicates the Layer 4 PPL component (L4PPL)
- the instantiation of the Layer 4 PPL component state machine addressed by this message is the instantiation associated with channel 1 (chl)
- the PPL event ID (1) indicates that an incoming message has been received while the PPL component state machine has been in the idle state NSO.
- the arguments associated with atomic function af35 (704) specify a Layer 4 PPL event ID.
- atomic function af35 is a PPL Send Event Indication message atomic function, used whenever a PPL Event Indication message is to be sent to the host Layer 5, each message having arguments for indicating the unique PPL event ID associated with the occu ⁇ ence of a different event.
- the host responds with a PPL Event Indication Acknowledge message 703 having the general format:
- sequence number is the sequence number provided in the PPL Event Indication message 701
- status indicates the status of the associated PPL event indication message.
- PPL Event Indication Acknowledge messages all indicate that the immediately previous PPL Event Indication message was successfully received.
- the Layer 4 PPL component state machine After the telecommunications switch provides the host with notification of an incoming call utilizing the PPL Event Indication message of the present invention, the Layer 4 PPL component state machine enters normal state NS 1 , which is a WAIT state 706, during which the Layer 4 PPL component waits for the host application to respond to the notification.
- the host sends a Layer 5 PPL Event Request message 705 (see Figure 7C) with an event ID of 1 , indicating that it is requesting that the switch proceed with the call received on channel 1.
- Message 705 has the following format:
- a PPL Event Request message having a PPL Event ID of 1 is interpreted by the Layer 4 PPL component state machine as an event. As illustrated in Figure 7A, the receipt of this PPL Event Request message is assigned by the Layer 4 PPL component state machine a Layer 4 unique PPL event ID of 501 , indicating that a Layer 5 PPL Event Request (with a PPL Event ID of 1) has occu ⁇ ed.
- the Layer 4 PPL component state machine performs 5 atomic functions: atomic function af60 (708), atomic function af62 (710), atomic function afl40 (712), atomic function af212 (714) and atomic function af50 (716).
- Atomic function af60 is an atomic function that generates a generic PPL Event Request Acknowledge message in accordance with the present invention. This atomic function af60 may be used whenever a PPL component of the switch is to acknowledge the receipt of a PPL Event Request message.
- the argument number 16 represents an acknowledgement status that the PPL Event Request message was successfully received.
- This atomic function af60 (708) generates the PPL Event Request Acknowledge message 707, having the same general format as the PPL Event Indication Acknowledge message described above.
- the PPL Event Request Acknowledge message 707 indicates that the above incoming message has been successfully received.
- Atomic functions af62 (710) and atomic function afl40 (712), serve, respectively, to send a connect message (to answer the call) to Layer 3 and to send a message to allocate a DSP resource for interactive digit string collection.
- Atomic function af212 (714) plays an opening announcement to the caller. As shown, there are two arguments to af212: an announcement ID and an announcement control option. af212 (714) was selected to play an opening announcement.
- Atomic function af50 (716) is performed to set a timer to wait for a selected period of time for receipt of incoming digits, entered in response to the announcement played by atomic function af212 (714).
- the first argument indicates that the multi-purpose timer to be used for performing this function is timerl .
- the second argument indicates the number of 1000 ms units the timer is to count.
- the second argument is 10, indicating that timerl will count for 10 seconds.
- atomic function af50 (716) enables timerl to expire in 10 seconds, during which time the Layer 4 PPL component enters normal state S2, which is WAIT state 718, wherein the PPL state machine waits for a digit to be detected on channel 1.
- atomic function af35 (720) is performed to inform the host that no digits were received.
- the receipt of a PPLevTIMERl message is assigned a PPL event ID of 191 by Layer 4 PPL component.
- atomic function 35 generates the PPL Event Indication message of the present invention.
- a PPL Event ID of 4 is included in the PPL Event Indication message, indicating that there has been a failure to detect digits on the selected channel.
- the format of this PPL Event Indication message is, therefore:
- atomic function af47 (722) is performed. The receipt of this message is assigned a unique PPL Event ID of 66.
- the Layer 4 PPL component state machine leaves wait state S2 (718) and performs atomic function af47 (722).
- Atomic function af47 disables the PPL multipurpose timer (timerl) selected by atomic function af50 (716), as indicated in the argument to the atomic function.
- Atomic function af53 (724) stores the received digits in a selected general purpose register.
- af53 (724) stores the received digit in general purpose register 1.
- atomic function af36 (726) is an atomic function configured to send a PPL Event Indication message with the contents of a selected general purpose register (argument 2), with a PPL event ID (argument 1).
- atomic function a£36 (726) sends the contents of the general purpose register 1 to the Layer 5 host application as a PPL Event Indication message 709 having an Event ID of 2.
- PPL Event Indication message 709 has the format
- L4PPL is the PPL component ID
- chl is the address element
- 2 is the PPL event ID
- "digit" is the received digit.
- This PPL Event Indication message exemplifies the capability of the universal API of the present invention to transfer data as well as commands utilizing a single generic PPL Event Indication message format.
- the host responds with a PPL Event Indication Acknowledgement message 711 , indicating that the PPL Event Indication message 709 was successfully received.
- Atomic function afl47 (728) is then performed to cancel digit reception by disconnecting the DTMF receiver from channel 1.
- the Layer 4 PPL component state machine then enters state S4 which is a
- WAIT state 730 wherein the Layer 4 PPL component state machine will wait indefinitely for the host application Layer 5 to direct the Layer 4 PPL component state machine how to respond to the digit that was received.
- the host application may send the Layer 4 PPL component any one of 3 different responses, having PPL Event ID 504, 505, and 506.
- PPL Event Request message 713 having a PPL event ID of 4 is received by the Layer 4 PPL component state machine, ((504)PPLevL5_EVENT_REQ_4) the Layer 4 PPL component state machine assigns a Layer 4 unique PPL event ID 504 to it, indicating that Layer 5 provided a PPL Event Request message having a PPL event ID of 4.
- PPL Event Request message 711 directs the Layer 4 PPL component state machine to play a specific outgoing announcement.
- the format of PPL Event Request message 713 is:
- PPL Event Req (L4PPL, chl , 4) wherein the PPL component ID indicates that the message is directed towards the Layer 4 PPL component (L4PPL), the address element indicates that channel 1 is the channel by which the communication is occurring (chl), and the PPL event ID (4) indicates that a specific additional outgoing announcement is to be played on the identified channel.
- Atomic function af60 (732) is an atomic function that generates a generic PPL Event Request Acknowledge message in accordance with the present invention.
- atomic function af60 is used whenever a PPL component is to acknowledge the receipt of a PPL Event Request message.
- the argument number 16 represents an acknowledgement status that the PPL Event Request message was successfully received.
- This atomic function generates the PPL Event Request Acknowledge message 764, having the general format desc ⁇ bed above.
- Atomic function afl40 serves to allocate a DSP resource for interactive digit stnng collection to channel 1.
- Atomic function af212 (736) plays an additional outgoing announcement on channel 1.
- An announcement ID of 3 is indicated by the first argument; no options were selected according to the second argument.
- Atomic function af50 (738) is performed to set timerl to wait for a 10 seconds for receipt of incoming digits.
- the PPL component enters state S5 (740) to wait for the incoming digit for the selected period of time.
- Atomic function af212 (736) was selected to play an outgoing announcement.
- Atomic function af50 (738) is performed to set a timer to wait for a selected penod of time for receipt of incoming digits, entered in response to the announcement played by atomic function af212 (736).
- atomic function af212 (736) sets timerl to expire in 10 seconds.
- the Layer 4 PPL component state machine enters state S5, which is a WAIT state 740 wherein the state machine waits for digits to be received.
- the host may have alternatively responded with either a PPL Event Request having a PPL event ID of 5 or 6 indicating to the Layer 4 PPL Component to perform other functions not shown. In both cases, the PPL component state machine performs atomic function af60 (731,733, respectively), indicating that the respective PPL Event Request message was successfully received.
- Atomic function af35 (742) is performed to inform the host that no digits were received within the allotted time.
- atomic functions a05 are configured to generate a PPL Event Indication message in accordance with the present invention.
- a PPL Event ID of 4 is included in the PPL Event Indication message by atomic function af35 (742), indicating that there has been a failure to detect digits on the selected channel.
- the format of this PPL Event Indication message is:
- atomic function af35 (742) is performed to inform the host that no digits were received by generating the PPL Event Indication message of the present invention with a PPL Event ID of 4, the format of which is:
- next event to occur while the Layer 4 PPL component state machine is in wait for digit state 740 is the receipt of a message indicating that digits have been detected on channel 1, ((66)L4PPLevDSP_RESULT_DIGITS), atomic functions af47 (744), af53 (746) and a 6(748) are performed to disable the PPL multipurpose timer (timerl) previously selected, sto ⁇ ng the received digits in a selected general purpose register, and sending a PPL Event Indication Message 717, respectively.
- atomic function af36 is an atomic function configured to send a PPL Event Indication message with the contents of general purpose register 1 with a PPL event ID of 3.
- atomic function af36 sends the contents of the general purpose register 1 to the Layer 5 host application as a PPL Event Indicauon message 717 havmg an Event ID of 3 PPL Event Indication message 717 has the format:
- L4PPL is the PPL component ID
- chl is the address element
- 3 is the PPL event ID
- "digit" is the received digit.
- This event ID indicates that the returned digit is in response to an af212 atomic function playing an outgoing announcement having at announcement ID of 3.
- the host responds with a PPL Event Indicauon Acknowledgement message 719, indicating that the PPL Event Indication message 711 was successfully received.
- each sequence of atomic functions shown in Figures 7A-7B has been defined as a p ⁇ mitive.
- each p ⁇ mitive provides a shorthand way to identify a desired sequence of atomic functions to invoke.
- the table of Figure 7D lists in tabular format the sequence of atomic functions for each p ⁇ miuve.
- Figure 7E is a state/event table that defines the relationships between the states, events and pnmitives of Figure 7D.
- a customer wishing to create the protocol depicted in Figures 7A- 7B would need only define the tables shown in Figure 76D and 7E. Those tables would then be downloaded to the switch 102 ( Figure 1) through a se ⁇ es of messages from the host device.
- the host application Layer 5 has limited interaction with the telecommunications switch while performing these functions Specifically, the telecommunications switch is configured to automatically respond to the digits that are entered.
- the Layer 4 PPL state machine includes internal states responsive to prompts internally generated dunng digit collection These aspects of the switch replace the atomic functions generating PPL Event Indication messages to the host providing the received digit, and the subsequent wait states wherein the switch waits for the host to supply it with a PL Event Request message.
- Figures 8A-8B illustrate an example of an application of the present invention in Call Processing Layer 4 with a limited level of interaction required by the host application Layer 5 to implement a protocol for providing limited host application decisionmaking in the performance of an interactive voice response to an incoming call.
- the protocol begins with the associated channel (channel 1) in normal state SO, which is the IDLE state 702 Upon the occu ⁇ ence of the event of layer 3 transmitting to layer 4 a setup message ((50)L4PPLevL3_SETUP_INDICATION)), the PPL component state machine in Figure 8A leaves idle state 802 and performs atomic function aD5 (804).
- Atomic function af35 (804) operates to notify the host application (Layer 5) of the event, assigning to the event a PPL event ID of 1.
- the host application interprets this PPL event ID value of 1 as a notification of an incoming call.
- atomic function 35 (804) generates a PPL Event Indication message 801 to notify the host of the incoming call.
- This PPL Event Indication message has the same format as PPL Event Indication message 701 , and indicates that the channel 1 instantiation of the Layer 4 PPL component state machine addressed by this message received an incoming message while the Layer 4 PPL component state machine was in the idle state.
- the host responds with a PPL Event Indication Acknowledge message 702 having the general format described above, indicating that the previous PL Event Indication message was successfully received.
- the Layer 4 PPL component state machine After the telecommunications switch provides the host with notification of an incoming call utilizing the PPL Event Indication message of the present invention, the Layer 4 PPL component state machine enters normal state S 1 , which is the WAIT state 706, dunng which the Layer 4 PPL component waits for the host application to respond to the notification.
- the host sends a Layer 5 PPL Event Request message 705 with an event ID of 1 , indicating that it is requesting that the switch proceed with the call received on channel 1.
- This message has the format desc ⁇ bed above, indicating that an incoming message has been received on channel 1 for that instantiation of the Layer 4 PPL component while the Layer 4 PPL component state machine has been in the idle state.
- This PPL Event Request message is identified by the Layer 4 PPL component state machine as a PPL event and is assigned a Layer 4 unique PPL event ID of 501 , indicating that a Layer 5 PPL Event Request (1) has occu ⁇ ed.
- the Layer 4 PPL component state machine performs 5 atomic functions: atomic function af ⁇ O (808), atomic function af62 (810), atomic function afl40 (812), atomic function af212 (814) and atomic function af50 (816).
- atomic function af60 is used whenever a PPL component is to acknowledge the receipt of a PPL Event Request message.
- the argument number 16 represents an acknowledgement status that the PPL Event Request message was successfully received.
- This atomic function af60 (808) generates the PPL Event
- Atomic functions af62 (810), afl40 (812), af212 (814) and af50 (816) perform the same function as the analogous atomic functions descnbed above with reference to Figure 7A.
- Atomic function af50 (816) enables timerl to expire during which time the Layer 4 PPL component enters normal state S2, which is WAIT state 818, wherein the PPL state machine waits for a digit to be detected on channel 1.
- atomic function aD5 (820) is performed.
- next event to occur while the Layer 4 PPL component state machine is in wait state 818 is the receipt of a message indicating that digits have been detected on channel 1 .
- ((66)L4PPLevDSP_RESULT_DIGITS) atomic functions af47 (822), af53 (824), and af47 (828) are performed.
- These atomic functions performs similar functions to the analogous atomic functions described above with reference to Figures 7A and 7B. Note that an atomic function analogous to af36 (726) is not invoked. Thus, the received digit is not provided to the host application.
- Atomic function af28 (829) is performed to test the value of the digit stored in the general purpose register used in atomic function af63 (824) to store the received digit.
- the Layer 4 PPL component state machine enters internal state IS3 which is a TEST state 830, wherein the Layer 4 PPL component state machine tests the value of the digit that was received and stored in general purpose register 1.
- the tested digit may have any one of 3 different values, each generating an internal event having PPL Event ID 200, 201 , and 202.
- the Layer 4 PPL component state machine assigns a Layer 4 unique PPL event ID 200 to it to indicate that the internal event having a PPL event ID of 0 was received.
- the Layer 4 PPL component state machine performs 3 atomic functions afl40 (834), af212 (836) and atomic function af50 (838), each of which perform functions similar to the analogous atomic functions described above with reference to Figures 7A and 7B. Note that an atomic function analogous to af60 (732) is not performed since the switch tests the incoming digit itself, and does not wait for a host generated PPL Event Request message. Therefore, no acknowledgement is required to be generated.
- the Layer 4 PPL component state machine then enters normal state NS4, which is a WAIT state 840 wherein the state machine again waits for digits to be received. If no digits are received, the next event is the expiration of timerl((191)
- the protocol performs an atomic function af35 (842) to inform the host that no digits were received within the allotted time. Processing then continues with a series of atomic functions not shown where, under host ampliation control through the implementation of the universal API of the present invention, the telecommunications switch performs various functions in response to the failure to detect digits on channel 1.
- atomic functions afl47 (844), af53 (846) are performed. These atomic functions perform similar functions to the analogous atomic functions described above with reference to Figures 7 A and 7B. Further, atomic function af28 (847) is performed to test the value of the now second received digit stored in general purpose register 1. A function analogous to atomic function aO ⁇ (748) is not performed, thereby not providing the host with a PPL Event Indication message.
- each sequence of atomic functions shown in Figures 8A-8B has been defined as a primitive.
- each primitive provides a shorthand way to identify a desired sequence of atomic functions to invoke.
- the table of Figure 8F lists in tabular format the sequence of atomic functions for each primitive.
- Figure 8F is a state/event table that defines the relationships between the states, events and primitives of Figure 8D.
- a customer wishing to create the protocol depicted in Figures 8A- 8B would need only define the tables shown in Figure 8D and 8E. Those tables would then be downloaded to the switch 102 ( Figure 1) through a series of messages from the host device.
- a Layer 4 PPL component 901 is executed as part of a Layer 4 PPL processor 902. As noted above, there may be multiple instantiations of a PPL component operating simultaneously, each of which has an associated state machine and tables.
- Layer 4 PPL processor 902 also includes a Layer 4 PPL message processor 1102 for receiving and processing internal PPL Event Request messages 1106.
- Each PPL processor such as Layer 4 PPL processor 902 may contain any number of PPL components. In the exemplary embodiment shown in Figures 9 and 11, the Layer 4 PPL processor 902 contains a single Layer 4 PPL component 901.
- Figure 9 illustrates the process flow related to the invocation and execution of an atomic function to create a PPL Event Indication message.
- Figure 9 illustrates the functions preformed in relation to the processing of atomic function af35 (704) of primitive #1 (750) to create PPL Event Indication message 701.
- Atomic function af35 (704) is part of the Layer 4 PPL component 901.
- Layer 4 PPL processor 902 resides on CPU/matrix card 112 in the illustrative embodiment discussed above, and invokes atomic functions in accordance with the state/event and primitive tables to perform various functions, including the functions discussed above with reference to the Call Management Layer 4 in Figure 2.
- Call Management Layer 4 is responsible for performing centralized call processing functions and providing a common interface to Application Layer 5.
- the functions performed by the Layer 4 PPL processor 902 are implemented in a publicly available, proprietary operating system refe ⁇ ed to as PSOS, available from Integrated Systems, Inc. , Santa Clara, California, USA.
- PSOS Public Switched System
- the present invention may be implemented in any commonly known software program and in any software language now or later developed.
- the Layer 4 PPL processor 902 invokes atomic functions that generate internal representations of the PPL Event Indication message.
- the internal message is passed to a communications processor 906, also residing on the CPU/matrix card 112, for translation into a PPL Event Indication message of the universal API of the present invention.
- Layer 4 PPL processor 902 executes a primitive of a PPL component state machine, it invokes each of the atomic functions associated with that primitive, as indicated by the primitive table 780 discussed above.
- atomic function af35 (704) is the only atomic function included in primitive #1 (750).
- atomic function 35 is a PPL Send Event Indication atomic function used whenever a PPL Event Indication is to be sent to the host, each occu ⁇ ence of the atomic function having a different PPL event ID to indicate the occu ⁇ ence of a different event.
- Layer 4 PPL processor 902 allocates a message buffer 1050 to "attach" to the internal representation of the PPL Event Indication message 904 generated by the atomic function af35 (704).
- the message buffer is used by the PSOS operating system to store the necessary information for creation of the PPL Event Indication message 701. A pointer to that message buffer is obtained through the PSOS operating system when the buffer is allocated.
- the universal API of the present invention may be implemented to manage communications between any two instantiations of any PPL components residing in the same or different PPL processors.
- the source and destination ID fields are loaded with the PPL component ID. Otherwise, the source and destination ID fields are loaded with the processor virtual ID, and the message type field 1058 is used by the destination PPL component or application to direct the message to the appropriate instantiation of the desired PPL component residing in the destination PPL processor.
- the message type field 1058 contains a unique message type identifier that is associated with a specific PPL component.
- the Layer 4 PPL processor 902 also loads a PPL event ID into the associated field 1056 of the message buffer, the event ID identified in the PPL primitive table 780 provided to atomic function af35 (704).
- atomic function af35 (704) indicates the detection of an incoming call during idle state SO, and is assigned a PPL event ID of 1.
- An ICB count field 1062 is loaded with the number of trailing ICB data fields 1064, if any.
- the Layer 4 PPL processor 902 transfers the data buffer 1050 to the PPL Event Indication message 904. This is accomplished by invoking a function that attaches the allocated buffer 1050 to the PPL Event Indication message 904 by providing the communications processor 906 with a pointer to the data buffer 1050.
- the communications processor 906 reformats the API messages of the present invention from the internal representation usable by the PPL processor 902 to the format shown in Figure 5 for transmission to the host application.
- Communications processor 906 performs well known translating operations typical of message handling communications processors, and is considered to be well known in the art. Communications processor 906 then transmits the PPL Event Indication message 701 to an applications program located in host computer 130 via the API interface 908.
- Figure 11 illustrates the process flow related to the receipt and processing of a PPL Event Request message.
- Figure 11 illustrates the functions related to the processing of PPL Event Request message 705 received at wait state Sl (706), invoking primitive 2 atomic functions as shown in primitive table 780.
- the communications processor 1006 performs the inverse operation of that performed above with respect to the PPL Event Indication message. That is, the communications processor 1006 receives the API version of the PPL Event Request message 705 over API 1008 and translates it into an internal PSOS PPL Event Request message 1106. Communications processor 1006 transmits the PPL Event Request message 1106 to the Layer 4 PPL processor 1002.
- a Layer 4 PPL message processor 1102 receives and processes the internal PPL Event Request message 1106 and generates a distinct Layer 4 PPL event for the Layer 4 PPL state machine engine 1104.
- the Layer 4 PPL message processor 1102 converts the PPL event ID 522 of message 705 into a Layer 4 unique PPL event ID for the Layer 4 PPL state machine 1104 by adding a layer 5 event request base value of 500 to the PPL event ID.
- the Layer 4 PPL message processor 1102 adds a base value of 500 to the PPL Event Request message PPL event ID of 1 to result in a Layer 4 unique PPL event ID of 501.
- a pointer is derived to the selected channel's PPL data based upon the address element value in the message that contained a logical span and channel ID.
- the Layer 4 PPL message processor 1102 converts the logical address into a physical address, i.e.., a physical time slot in switch 102.
- the PPL state machine engine is invoked, typically as a function call, with the channel pointer for the PPL component instantiation data block and a pointer to the data block associated with the PPL Event Request message 1106 that was received from the communications processor 1006.
- the Layer 4 PPL component state machine engine 1104 processes the Layer 4 unique PPL event ID, searching the state/event table 790 for that PPL Event ID for the present state. If a matching event is found, the state machine engine 1104 invokes the identified primitive in the state/event table, retrieving from primitive table 780 the atomic functions associated with the primitive ID.
- the Layer 4 PPL component state machine engine 1104 processes PPL event 501, locating the PPL Event ID of 501 for the present state Sl (706) in the state/event table 790 and invoking the atomic functions associated with primitive #2.
- the PPL state machine engine 1104 enters the state indicated in the Layer 4 PPL state/event table 790 after processing all the atomic functions associated with primitive 2.
- ppl_event psos_msg.ppl_data_buff ® ppl_event + ppl_L5_event_req_base
- embodiments of the present invention can be implemented in hardware, software or a combination thereof.
- the various components and steps would be implemented in hardware and/or software to perform the functions of the present invention.
- Any presently available or future developed computer software language and/or hardware components can be employed in such embodiments of the present invention.
- the pseudo-code discussed above can be especially useful for creating the software embodiments.
Abstract
Description
Claims
Priority Applications (8)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
IL12143496A IL121434A (en) | 1995-11-30 | 1996-11-27 | Telecommunication system |
JP9520634A JPH10513633A (en) | 1995-11-30 | 1996-11-27 | Telecommunications switch with universal application program interface for standard interactive call processing communication |
DE69623931T DE69623931T2 (en) | 1995-11-30 | 1996-11-27 | TELECOMMUNICATION SYSTEM WITH A UNIVERSAL APPLICATION PROGRAM INTERFACE FOR STANDARDIZED INTERACTIVE CALL PROCESSING MESSAGES |
EP96940891A EP0807358B1 (en) | 1995-11-30 | 1996-11-27 | Telecommunications switch having a universal applications program interface for stantardized interactive call processing communications |
CA002211780A CA2211780C (en) | 1995-11-30 | 1996-11-27 | Telecommunications switch having a universal applications program interface for standardized interactive call processing communications |
BR9606820A BR9606820A (en) | 1995-11-30 | 1996-11-27 | Telecommunications system and switch universal application program interface and processes for protocol development and for communication between two levels of a programmable telecommunications switch system |
AU10844/97A AU718827B2 (en) | 1995-11-30 | 1996-11-27 | Telecommunications switch having a universal applications program interface for stantardized interactive call processing communications |
AT96940891T ATE225110T1 (en) | 1995-11-30 | 1996-11-27 | TELEPHONE SWITCHING SYSTEM HAVING A UNIVERSAL APPLICATION PROGRAM INTERFACE FOR STANDARDIZED INTERACTIVE CALL PROCESSING MESSAGES |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US08/566,414 | 1995-11-30 | ||
US08/566,414 US5826030A (en) | 1995-11-30 | 1995-11-30 | Telecommunication switch having a universal API with a single call processing message including user-definable data and response message each having a generic format |
Publications (1)
Publication Number | Publication Date |
---|---|
WO1997020439A1 true WO1997020439A1 (en) | 1997-06-05 |
Family
ID=24262788
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US1996/018959 WO1997020439A1 (en) | 1995-11-30 | 1996-11-27 | Telecommunications switch having a universal applications program interface for stantardized interactive call processing communications |
Country Status (11)
Country | Link |
---|---|
US (4) | US5826030A (en) |
EP (1) | EP0807358B1 (en) |
JP (1) | JPH10513633A (en) |
KR (1) | KR19980701797A (en) |
AT (1) | ATE225110T1 (en) |
AU (1) | AU718827B2 (en) |
BR (1) | BR9606820A (en) |
CA (1) | CA2211780C (en) |
DE (1) | DE69623931T2 (en) |
IL (1) | IL121434A (en) |
WO (1) | WO1997020439A1 (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1999065253A1 (en) * | 1998-06-08 | 1999-12-16 | Excel Switching Corporation | Programming call-processing application in a switching system |
EP1072145A1 (en) * | 1998-04-09 | 2001-01-31 | Voice Technologies Group Inc. | Virtual phone generic configurable interface |
DE10112974B4 (en) * | 2000-03-17 | 2005-10-20 | Zarlink Semiconductor Inc | Multi-frequency tone detector |
CN100358302C (en) * | 2004-12-06 | 2007-12-26 | 华为技术有限公司 | Method for testing network element interface by state apparatus |
CN100396061C (en) * | 2003-07-05 | 2008-06-18 | 华为技术有限公司 | A method for controlling asynchronous operation by using state machine |
Families Citing this family (73)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6651102B2 (en) * | 1995-12-20 | 2003-11-18 | Nb Networks | Systems and methods for general purpose data modification |
US5793954A (en) * | 1995-12-20 | 1998-08-11 | Nb Networks | System and method for general purpose network analysis |
US6493761B1 (en) * | 1995-12-20 | 2002-12-10 | Nb Networks | Systems and methods for data processing using a protocol parsing engine |
IL119914A (en) * | 1996-12-25 | 2000-06-29 | Emultek Ltd | Device for implementing hierarchical state charts and methods and apparatus useful therefor |
SE510162C2 (en) * | 1997-01-14 | 1999-04-26 | Ericsson Telefon Ab L M | A method and communication station for controlling message transmission in a mobile communication system |
US6286050B1 (en) | 1997-01-27 | 2001-09-04 | Alcatel Usa Sourcing, L.P. | System and method for monitoring and management of telecommunications equipment using enhanced internet access |
US6119173A (en) * | 1997-01-27 | 2000-09-12 | Alcatel Usa Sourcing, L.P. | System and method for communications and process management in a distributed telecommunications switch |
US6052455A (en) * | 1997-11-13 | 2000-04-18 | Northern Telecom Limited | Universal data structure for use with a concurrent state machine space in a telecommunications network |
US6122356A (en) * | 1997-11-13 | 2000-09-19 | Northern Telecom Limited | Concurrent state machine space in a telecommunications network |
US6003041A (en) * | 1998-01-05 | 1999-12-14 | Gateway 2000, Inc. | Method and managing multiple channel maps from multiple input devices in a multimedia system |
US6424934B2 (en) | 1998-05-18 | 2002-07-23 | Solidum Systems Corp. | Packet classification state machine having reduced memory storage requirements |
US6587890B1 (en) | 1998-06-12 | 2003-07-01 | Mci Communications Corporation | Switch controller application programmer interface |
US6480597B1 (en) | 1998-06-12 | 2002-11-12 | Mci Communications Corporation | Switch controller for a telecommunications network |
US7929516B2 (en) * | 1998-06-12 | 2011-04-19 | Mci Communications Corporation | Intelligent services network using a switch controller |
US7142650B1 (en) | 1998-06-12 | 2006-11-28 | Mci Communication Corporation | System and method for resource management |
US6724767B1 (en) * | 1998-06-27 | 2004-04-20 | Intel Corporation | Two-dimensional queuing/de-queuing methods and systems for implementing the same |
US6735773B1 (en) | 1998-06-27 | 2004-05-11 | Intel Corporation | Method and apparatus for issuing commands to a network processor configured to provide a plurality of APIs |
US6604136B1 (en) * | 1998-06-27 | 2003-08-05 | Intel Corporation | Application programming interfaces and methods enabling a host to interface with a network processor |
US6603768B1 (en) | 1998-06-27 | 2003-08-05 | Intel Corporation | Multi-protocol conversion assistance method and system for a network accelerator |
US6657959B1 (en) | 1998-06-27 | 2003-12-02 | Intel Corporation | Systems and methods for implementing ABR with guaranteed MCR |
US6728249B2 (en) | 1998-06-27 | 2004-04-27 | Intel Corporation | System and method for performing cut-through forwarding in an ATM network supporting LAN emulation |
US6356950B1 (en) * | 1999-01-11 | 2002-03-12 | Novilit, Inc. | Method for encoding and decoding data according to a protocol specification |
US6594685B1 (en) * | 1999-04-14 | 2003-07-15 | Excel Switching Corporation | Universal application programming interface having generic message format |
IL146539A0 (en) * | 1999-05-18 | 2002-07-25 | Solidum Systems Corp | Packet classification state machine |
US6349405B1 (en) | 1999-05-18 | 2002-02-19 | Solidum Systems Corp. | Packet classification state machine |
US6565443B1 (en) | 1999-09-14 | 2003-05-20 | Innovative Gaming Corporation | System and method for verifying the contents of a mass storage device before granting access to computer readable data stored on the device |
US7346075B1 (en) * | 2000-02-25 | 2008-03-18 | International Business Machines Corporation | Portable networking interface method and apparatus for distributed switching system |
SG92686A1 (en) * | 2000-03-09 | 2002-11-19 | Kent Ridge Digital Labs | An atm handoff process |
US6829630B1 (en) * | 2000-11-24 | 2004-12-07 | Xerox Corporation | Mechanisms for web-object event/state-driven communication between networked devices |
WO2002056547A1 (en) * | 2000-12-27 | 2002-07-18 | Fujitsu Limited | Switched routing device and switched routing system |
US6907046B1 (en) * | 2001-03-07 | 2005-06-14 | Sprint Communications Company L.P. | Communication system and device that provides service independent communication bridging |
US20020161907A1 (en) * | 2001-04-25 | 2002-10-31 | Avery Moon | Adaptive multi-protocol communications system |
CA2357444A1 (en) * | 2001-09-13 | 2003-03-13 | Armadillo Networks Inc. | System and methods for automatic negotiation in distributed computing |
US20030059015A1 (en) * | 2001-09-21 | 2003-03-27 | Mello Eber | Call server allowing calls with multiple participants and multiple services independently of the number of participants |
US7395343B1 (en) * | 2002-02-26 | 2008-07-01 | Cisco Technology, Inc. | Network tunneling method and apparatus |
EP1357763A1 (en) * | 2002-04-23 | 2003-10-29 | Hewlett-Packard Company | Adaptor module |
JP3607687B2 (en) * | 2002-04-26 | 2005-01-05 | 株式会社東芝 | Data transmission / reception system and data transmission / reception method |
US7266182B2 (en) * | 2002-06-14 | 2007-09-04 | International Business Machines Corporation | Method and system for implementing a telephony services feature using voice XML |
US7752293B1 (en) * | 2002-07-30 | 2010-07-06 | Cisco Technology, Inc. | Command processing in a telecommunications network |
US7428218B2 (en) * | 2002-08-01 | 2008-09-23 | Teradyne, Inc. | Flexible approach for representing different bus protocols |
US6873695B2 (en) * | 2002-09-09 | 2005-03-29 | International Business Machines Corporation | Generic service component for voice processing services |
US7720948B2 (en) | 2003-11-12 | 2010-05-18 | International Business Machines Corporation | Method and system of generically specifying packet classification behavior |
US20050114540A1 (en) * | 2003-11-12 | 2005-05-26 | International Business Machines Corporation | Method and system of generically specifying congestion control and a voidance behavior |
WO2005052759A2 (en) | 2003-11-24 | 2005-06-09 | Ebay Inc. | Business language schema design framework |
US7844639B2 (en) | 2003-11-24 | 2010-11-30 | Ebay Inc. | Backward compatibility in database schemas |
US7554974B2 (en) * | 2004-03-09 | 2009-06-30 | Tekelec | Systems and methods of performing stateful signaling transactions in a distributed processing environment |
US7653681B2 (en) * | 2005-01-14 | 2010-01-26 | International Business Machines Corporation | Software architecture for managing a system of heterogenous network processors and for developing portable network processor applications |
CN101164317A (en) * | 2005-02-24 | 2008-04-16 | Lg电子株式会社 | Packet structure and packet transmission method of network control protocol |
US7856094B2 (en) | 2005-03-21 | 2010-12-21 | Tekelec | Methods, systems, and computer program products for providing telecommunications services between a session initiation protocol (SIP) network and a signaling system 7 (SS7) network |
US20060282838A1 (en) * | 2005-06-08 | 2006-12-14 | Rinku Gupta | MPI-aware networking infrastructure |
US7760708B2 (en) | 2005-07-08 | 2010-07-20 | Tekelec | Methods, systems, and computer program products for triggering SIP nodes to include SS7 routing information in response messages including information requested by SS7 nodes |
US8050253B2 (en) * | 2006-01-09 | 2011-11-01 | Tekelec | Methods, systems, and computer program products for decentralized processing of signaling messages in a multi-application processing environment |
US7907619B2 (en) * | 2006-12-19 | 2011-03-15 | International Business Machines Corporation | Method, system and program product for adapting to protocol changes |
US8059667B2 (en) * | 2007-01-31 | 2011-11-15 | Tekelec | Methods, systems, and computer program products for applying multiple communications services to a call |
US8213440B2 (en) | 2007-02-21 | 2012-07-03 | Tekelec Global, Inc. | Methods, systems, and computer program products for using a location routing number based query and response mechanism to route calls to IP multimedia subsystem (IMS) subscribers |
US20080198996A1 (en) * | 2007-02-21 | 2008-08-21 | Tekelec | Methods, systems, and computer program products for using a location routing number based query and response mechanism to effect advanced routing |
US8073127B2 (en) * | 2007-02-21 | 2011-12-06 | Tekelec | Methods, systems, and computer program products for using a location routing number based query and response mechanism to effect subscriber cutover |
US8730970B2 (en) | 2007-02-23 | 2014-05-20 | Tekelec Global, Inc. | Methods systems, and computer program products for providing voicemail routing information in a network that provides customized voicemail services |
WO2008130709A2 (en) * | 2007-04-20 | 2008-10-30 | Tekelec | Systems, methods, and computer program products for providing service interaction and mediation in a communications network |
FR2929474B1 (en) * | 2008-03-28 | 2010-07-30 | Groupe Ecoles Telecomm | MULTI-LAYER HIERARCHISED COMPUTING ARCHITECTURE |
GB2460467A (en) * | 2008-05-30 | 2009-12-02 | Symbian Software Ltd | Specifying a finite state machine by a set of instructions and a set of parameters which are stored in different files. |
WO2009149133A2 (en) * | 2008-06-02 | 2009-12-10 | Tekelec | Methods, systems, and computer readable media for providing next generation network (ngn)-based end user services to legacy subscribers in a communications network |
WO2010060087A2 (en) | 2008-11-24 | 2010-05-27 | Tekelec | Systems, methods, and computer readable media for location-sensitive called-party number translation in a telecommunications network |
US9712341B2 (en) | 2009-01-16 | 2017-07-18 | Tekelec, Inc. | Methods, systems, and computer readable media for providing E.164 number mapping (ENUM) translation at a bearer independent call control (BICC) and/or session intiation protocol (SIP) router |
WO2010083509A2 (en) | 2009-01-16 | 2010-07-22 | Tekelec | Methods, systems, and computer readable media for centralized routing and call instance code management for bearer independent call control (bicc) signaling messages |
WO2011035050A2 (en) | 2009-09-16 | 2011-03-24 | Tekelec | Methods, systems, and computer readable media for providing foreign routing address information to a telecommunications network gateway |
US8516130B2 (en) * | 2011-06-30 | 2013-08-20 | Harman International Industries, Incorporated | Using non-AVB application layer interface and message to establish a connection over an AVB network |
US9009354B2 (en) * | 2012-12-20 | 2015-04-14 | Sap Se | Services and management layer for diverse data connections |
CN103441990B (en) * | 2013-08-09 | 2016-03-30 | 中国人民解放军理工大学 | The automatic estimating method of protocol state machine based on state fusion |
CN104333540B (en) * | 2014-10-22 | 2018-02-13 | 国电南瑞科技股份有限公司 | A kind of substation automation system communication protocol dynamic implementation method |
US10141855B2 (en) | 2017-04-12 | 2018-11-27 | Accion Systems, Inc. | System and method for power conversion |
US10728392B1 (en) | 2019-03-20 | 2020-07-28 | InContact Inc. | Method and system for managing availability states of a user to communicate over multiple communication platforms |
WO2020236961A1 (en) | 2019-05-21 | 2020-11-26 | Accion Systems, Inc. | Apparatus for electrospray emission |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0555997A2 (en) * | 1992-02-10 | 1993-08-18 | AT&T Corp. | Apparatus and methods for implementing protocols |
US5426694A (en) * | 1993-10-08 | 1995-06-20 | Excel, Inc. | Telecommunication switch having programmable network protocols and communications services |
US5455827A (en) * | 1994-02-23 | 1995-10-03 | Harris Corporation | Multi-processing and direct routing of signalling protocols in voice communication channels |
EP0680186A1 (en) * | 1994-04-28 | 1995-11-02 | Koninklijke KPN N.V. | Method and device for exchanging messages between systems based on different protocol versions |
Family Cites Families (26)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4523308A (en) * | 1982-09-29 | 1985-06-11 | Stromberg-Carlson Corporation | Telephone concentrator switch arrangement |
US4527012B1 (en) * | 1983-01-31 | 1994-12-13 | Redcom Laboraties Inc | Communications switching system with modular switching communicatons peripheral and host computer |
US5060140A (en) * | 1986-01-16 | 1991-10-22 | Jupiter Technology Inc. | Universal programmable data communication connection system |
US4787062A (en) * | 1986-06-26 | 1988-11-22 | Ikos Systems, Inc. | Glitch detection by forcing the output of a simulated logic device to an undefined state |
US4768150A (en) * | 1986-09-17 | 1988-08-30 | International Business Machines Corporation | Application program interface to networking functions |
JP2802088B2 (en) * | 1989-02-06 | 1998-09-21 | 株式会社日立製作所 | Protocol selection switching method |
JPH03123244A (en) * | 1989-10-06 | 1991-05-27 | Matsushita Electric Ind Co Ltd | Communication equipment |
CA2010591C (en) * | 1989-10-20 | 1999-01-26 | Phillip M. Adams | Kernels, description tables and device drivers |
US5323452A (en) * | 1990-12-18 | 1994-06-21 | Bell Communications Research, Inc. | Visual programming of telephone network call processing logic |
US5265239A (en) * | 1991-04-08 | 1993-11-23 | Ardolino Anthony A | Method for remotely accessing service programs of a local processing system supporting multiple protocol stacks and multiple device drivers |
US5317568A (en) * | 1991-04-11 | 1994-05-31 | Galileo International Partnership | Method and apparatus for managing and facilitating communications in a distributed hetergeneous network |
US5572675A (en) * | 1991-05-29 | 1996-11-05 | Alcatel N.V. | Application program interface |
JPH0563749A (en) * | 1991-09-02 | 1993-03-12 | Hitachi Ltd | Multi-protocol communication controller |
US5321744A (en) * | 1992-09-29 | 1994-06-14 | Excel, Inc. | Programmable telecommunication switch for personal computer |
US6134304A (en) * | 1992-11-10 | 2000-10-17 | Telefonaktiebolaget Lm Ericsson | General analysis system |
US6044407A (en) * | 1992-11-13 | 2000-03-28 | British Telecommunications Public Limited Company | Interface for translating an information message from one protocol to another |
GB2274230B (en) * | 1993-01-07 | 1996-05-15 | Digital Equipment Int | Communication systems |
US5537417A (en) * | 1993-01-29 | 1996-07-16 | International Business Machines Corporation | Kernel socket structure for concurrent multiple protocol access |
US5581738A (en) * | 1993-06-07 | 1996-12-03 | Xilinx, Inc. | Method and apparatus for back-annotating timing constraints into simulation models of field programmable gate arrays |
US5414833A (en) * | 1993-10-27 | 1995-05-09 | International Business Machines Corporation | Network security system and method using a parallel finite state machine adaptive active monitor and responder |
US5555415A (en) * | 1994-01-10 | 1996-09-10 | Metasphere, Inc. | Object oriented event message dispatching subsystem and method utilizing a disposition matrix |
US5627876A (en) * | 1994-06-10 | 1997-05-06 | Uniden America Corporation | Call priority override in a land mobile radio system |
US5668810A (en) * | 1995-04-26 | 1997-09-16 | Scientific-Atlanta, Inc. | Data transmission protocol method and apparatus |
US5638371A (en) * | 1995-06-27 | 1997-06-10 | Nec Usa, Inc. | Multiservices medium access control protocol for wireless ATM system |
US6028924A (en) * | 1996-06-13 | 2000-02-22 | Northern Telecom Limited | Apparatus and method for controlling processing of a service call |
US5872919A (en) * | 1997-05-07 | 1999-02-16 | Advanced Micro Devices, Inc. | Computer communication network having a packet processor with an execution unit which is variably configured from a programmable state machine and logic |
-
1995
- 1995-11-30 US US08/566,414 patent/US5826030A/en not_active Expired - Lifetime
-
1996
- 1996-11-27 WO PCT/US1996/018959 patent/WO1997020439A1/en active IP Right Grant
- 1996-11-27 BR BR9606820A patent/BR9606820A/en not_active Application Discontinuation
- 1996-11-27 EP EP96940891A patent/EP0807358B1/en not_active Expired - Lifetime
- 1996-11-27 KR KR1019970705194A patent/KR19980701797A/en not_active Application Discontinuation
- 1996-11-27 CA CA002211780A patent/CA2211780C/en not_active Expired - Fee Related
- 1996-11-27 AU AU10844/97A patent/AU718827B2/en not_active Ceased
- 1996-11-27 AT AT96940891T patent/ATE225110T1/en not_active IP Right Cessation
- 1996-11-27 IL IL12143496A patent/IL121434A/en not_active IP Right Cessation
- 1996-11-27 JP JP9520634A patent/JPH10513633A/en active Pending
- 1996-11-27 DE DE69623931T patent/DE69623931T2/en not_active Expired - Lifetime
-
1998
- 1998-10-07 US US09/168,130 patent/US6119187A/en not_active Expired - Lifetime
-
1999
- 1999-03-26 US US09/277,469 patent/US6134618A/en not_active Expired - Lifetime
-
2000
- 2000-06-26 US US09/603,367 patent/US6311238B1/en not_active Expired - Lifetime
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0555997A2 (en) * | 1992-02-10 | 1993-08-18 | AT&T Corp. | Apparatus and methods for implementing protocols |
US5426694A (en) * | 1993-10-08 | 1995-06-20 | Excel, Inc. | Telecommunication switch having programmable network protocols and communications services |
US5546453A (en) * | 1993-10-08 | 1996-08-13 | Excel, Inc. | Telecommunication switch having programmable network protocols and communications services |
US5455827A (en) * | 1994-02-23 | 1995-10-03 | Harris Corporation | Multi-processing and direct routing of signalling protocols in voice communication channels |
EP0680186A1 (en) * | 1994-04-28 | 1995-11-02 | Koninklijke KPN N.V. | Method and device for exchanging messages between systems based on different protocol versions |
Non-Patent Citations (4)
Title |
---|
ATSUSHI ITO ET AL: "TRANSFORMATION TECHNIQUE BETWEEN SPECIFICATION IN SDL AND SPECIFICATION IN MESSAGE SEQUENCE CHARTS FOR DESIGNING PROTOCOL SPECIFICATIONS", INTERNATIONAL CONFERENCE ON COMMUNICATIONS - PAPER 317.2, vol. 1, 14 June 1992 (1992-06-14) - 18 June 1992 (1992-06-18), CHICAGO (US), pages 442 - 447, XP000326907 * |
BOUMEZBEUR R ET AL: "SPECIFYING TELEPHONE SYSTEMS IN LOTOS", IEEE COMMUNICATIONS MAGAZINE, vol. 31, no. 8, 1 August 1993 (1993-08-01), NEW YORK (US), pages 38 - 45, XP000393761 * |
RUMEN STAINOV: "DYNAMIC PROTOCOL CONFIGURATION FOR MULTIMEDIA NETWORKS", MICROPROCESSING AND MICROPROGRAMMING, vol. 38, no. 1 / 05, 1 September 1993 (1993-09-01), AMSTERDAM (NL), pages 741 - 748, XP000383837 * |
TSCHUDIN C: "FLEXIBLE PROTOCOL STACKS", COMPUTER COMMUNICATIONS REVIEW, vol. 21, no. 4, 1 September 1991 (1991-09-01), NEW YORK (US), pages 197 - 205, XP000234937 * |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1072145A1 (en) * | 1998-04-09 | 2001-01-31 | Voice Technologies Group Inc. | Virtual phone generic configurable interface |
EP1072145A4 (en) * | 1998-04-09 | 2004-11-10 | Intel Corp | Virtual phone generic configurable interface |
WO1999065253A1 (en) * | 1998-06-08 | 1999-12-16 | Excel Switching Corporation | Programming call-processing application in a switching system |
US6526050B1 (en) | 1998-06-08 | 2003-02-25 | Excel Switching Co. | Programming call-processing application in a switching system |
DE10112974B4 (en) * | 2000-03-17 | 2005-10-20 | Zarlink Semiconductor Inc | Multi-frequency tone detector |
CN100396061C (en) * | 2003-07-05 | 2008-06-18 | 华为技术有限公司 | A method for controlling asynchronous operation by using state machine |
CN100358302C (en) * | 2004-12-06 | 2007-12-26 | 华为技术有限公司 | Method for testing network element interface by state apparatus |
Also Published As
Publication number | Publication date |
---|---|
JPH10513633A (en) | 1998-12-22 |
US6134618A (en) | 2000-10-17 |
CA2211780C (en) | 2006-06-06 |
IL121434A (en) | 2000-11-21 |
CA2211780A1 (en) | 1997-06-05 |
US6311238B1 (en) | 2001-10-30 |
IL121434A0 (en) | 1998-01-04 |
AU1084497A (en) | 1997-06-19 |
ATE225110T1 (en) | 2002-10-15 |
US5826030A (en) | 1998-10-20 |
BR9606820A (en) | 1997-12-30 |
AU718827B2 (en) | 2000-04-20 |
EP0807358B1 (en) | 2002-09-25 |
EP0807358A1 (en) | 1997-11-19 |
DE69623931T2 (en) | 2003-05-28 |
KR19980701797A (en) | 1998-06-25 |
US6119187A (en) | 2000-09-12 |
DE69623931D1 (en) | 2002-10-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP0807358B1 (en) | Telecommunications switch having a universal applications program interface for stantardized interactive call processing communications | |
US6088749A (en) | Universal API with generic call processing message having user-defined PPL event ID and generic response message for communications between telecommunications switch and host application | |
EP0724804B1 (en) | Telecommunication switch having programmable network protocols and communications services | |
JP3007907B2 (en) | A communication switching mechanism that provides programmable communication services | |
US5291479A (en) | Modular user programmable telecommunications system with distributed processing | |
US20030115358A1 (en) | Unified interprocess communication | |
JP3067803B2 (en) | Programmable communication switching processor for personal computer. | |
US6636519B1 (en) | Network access method and network access server therefor | |
KR19980070451A (en) | Distributed Protocol Server | |
US7263701B2 (en) | Interprocess communication method and apparatus | |
US6594685B1 (en) | Universal application programming interface having generic message format | |
US6920143B1 (en) | Computer telephony system using multiple hardware platforms to provide telephony services | |
Luderer et al. | A virtual circuit switch as the basis for distributed systems | |
WO1999035568A2 (en) | Isolation of resources from application in a process control system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 96192846.8 Country of ref document: CN |
|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AL AU BB BG BR CA CN CZ EE GE HU IL IS JP KP KR LK LR LT LV MG MK MN MX NO NZ PL RO SG SI SK TR TT UA UZ VN AM AZ BY KG KZ MD RU TJ TM |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): KE LS MW SD SZ UG AT BE CH DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN ML MR NE SN TD TG |
|
ENP | Entry into the national phase |
Ref document number: 2211780 Country of ref document: CA Ref document number: 2211780 Country of ref document: CA Kind code of ref document: A Ref document number: 1997 520634 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1019970705194 Country of ref document: KR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1996940891 Country of ref document: EP |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWP | Wipo information: published in national office |
Ref document number: 1996940891 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 1019970705194 Country of ref document: KR |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: 1019970705194 Country of ref document: KR |
|
WWG | Wipo information: grant in national office |
Ref document number: 1996940891 Country of ref document: EP |