EP0850545A1 - Systeme environnemental operationnel pour des applications de services d'un reseau de telecommunication - Google Patents
Systeme environnemental operationnel pour des applications de services d'un reseau de telecommunicationInfo
- Publication number
- EP0850545A1 EP0850545A1 EP96930159A EP96930159A EP0850545A1 EP 0850545 A1 EP0850545 A1 EP 0850545A1 EP 96930159 A EP96930159 A EP 96930159A EP 96930159 A EP96930159 A EP 96930159A EP 0850545 A1 EP0850545 A1 EP 0850545A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- service application
- call
- service
- monitoring system
- check
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
Classifications
-
- 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/0428—Integrated services digital network, i.e. systems for transmission of different types of digitised signals, e.g. speech, data, telecentral, television signals
- H04Q11/0435—Details
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/0016—Arrangements providing connection between exchanges
- H04Q3/0029—Provisions for intelligent networking
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13533—Indexing scheme relating to selecting arrangements in general and for multiplex systems multivendor and hybrid, e.g. public/private, networks, inc. international
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13545—Indexing scheme relating to selecting arrangements in general and for multiplex systems monitoring of signaling messages, intelligent network
Definitions
- the intelligent network is intended to enable a network operator to introduce new services quickly and easily, without having to intervene in the system program systems in each network node.
- the interventions mentioned are therefore restricted in an IN to as few central network nodes as possible, so-called service control points SCP, which are equipped at a central point with the appropriate application software for the new services, the so-called service applications, and then in a kind of "remote control" enable the individual network nodes to carry out the new services.
- the aforementioned remote-controlled network nodes of the IN are also referred to as service access nodes or service switching points SSP. They are connected to a service control point SCP directly or via a signaling network such as the CCS7 signaling network.
- a service management point SMP is used to administer the IN services by the network operator, the service provider and the service subscriber.
- a call to a service of the intelligent network can first be routed from a normal, ie from a network node not remotely controlled by the SCP, to a service switching point SSP.
- the service switching determines based on the dialed number and / or the service code Point, which service control point SCP contains the service application corresponding to this service and then sends a request to this service control point as to how it should handle the call.
- the SCP After the SCP has examined the request, it sends a response to the service switching point, which contains information that it needs for further handling of the call.
- the Service Control Point SCP requires an error-free (hardware / software) computer platform, since the service applications must have the same high availability as the other components in the basic network (SSP and other switching centers). For this reason, today the service applications are developed by software specialists from network suppliers and systematically tested with great effort. The network operator can only modify these service applications at the designated points (customizing). Examples of such service applications are:
- a service application goes into an inactive loop (endless loop), in which no more meaningful function runs.
- a service application periodically exchanges messages with the basic network or with other SCP functions, but without carrying out a useful network function (active loop). There is also a risk of system overload for other, uninvolved service applications.
- the invention is based on the object of giving network operators or third parties (for example software houses) the opportunity to implement their service ideas directly and without going through the network supplier, and at the same time to ensure that faulty service implementations implemented in this way Applications have no negative effects.
- FIGS 2 to 5 serve to illustrate the exemplary embodiment.
- the fault-tolerant execution environment in the SCP should recognize the following serious logical software error classes in the service applications as quickly as possible and immediately end the handling of the calls or other network functions by the faulty service application as required:
- FIG. 2 shows an SCP architecture which comprises an execution environment system FAU according to the invention.
- a corresponding architecture can be used for the SMP.
- the process environment system FAU provides the service applications SAP with a fail-safe application programming interface API.
- the API provides a network operator and / or a third party with a system of function modules for programming an individual SAP.
- the FAU and the API are detailed by the system supplier, i.e. stable, tested and thus perform the functions represented by the API (viewed individually) error-free.
- the process includes the following features or process steps: 1) If an activated (ie in operation) service application reaches a state in which it is waiting for one or more network input events, these expected events (for example network messages to be received according to a known IN application protocol such as INAP or AIN) together with their identifier in a so-called event list IER of the FAU. If the service application mentioned leaves this waiting state, the events corresponding to this state are removed from the event list IER by the FAU.
- these expected events for example network messages to be received according to a known IN application protocol such as INAP or AIN
- Context changes include, for example:
- - procedure call including remote procedure call (RPC), - sending / processing of an internal, external message,
- RPC remote procedure call
- the context change events are normally recognized by the underlying operating system and dealt with in the runtime environment system in relation to the relevant service applications.
- the context change timestamp enables the FAU to assess the activity of a SAP.
- a time stamp of the last network input event received by the base network or of the network output event output to the base network, the meaning of which will become clear later, is also stored by the runtime environment system.
- NEZ One event counter NEZ is kept in the workflow environment system for each network output event. All possible network output events and their maximum number are given for a given Basic network protocol (e.g. according to the international standards INAP, AIN) well defined.
- Basic network protocol e.g. according to the international standards INAP, AIN
- the process environment system periodically triggers an Application Activity Test AAT.
- the adjustable time period is recorded in the runtime environment system as a time stamp tn.
- FIG. 4 shows the process running in the runtime environment system for recognizing the logical errors mentioned in the service applications.
- the triggering event of the method is the periodic Application Activity Test AAT.
- the list IER of network input events for a specific call is first examined in tests. If it is not empty, it is checked whether all entered network input events are logically correct. This test is derived from knowledge of the standardized basic network protocol (e.g. INAP, AIN).
- a check is also carried out to determine whether the base network can send these network input events at all (if the call was ended prematurely by the base network, this transmission is not possible, for example).
- a network activity test NAT is carried out using a known method, using one for this standardized test transaction is carried out (eg as part of the INAP, AIN protocol). If it is determined that the call is still active in the basic network, the call processing in the service application is continued.
- process environment system must also carry out additional conventional checks, for example checking the correct structure and syntax of all network events and their compatibility with the call handling in the basic network. This is done using known methods, that do not require further explanation here. In the event of errors or inconsistencies of this type, the call handling in the relevant service application is terminated by the process environment system.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Computer And Data Communications (AREA)
Abstract
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP96930159A EP0850545A1 (fr) | 1995-09-15 | 1996-09-03 | Systeme environnemental operationnel pour des applications de services d'un reseau de telecommunication |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP95114576 | 1995-09-15 | ||
EP95114576 | 1995-09-15 | ||
PCT/EP1996/003865 WO1997010683A1 (fr) | 1995-09-15 | 1996-09-03 | Systeme environnemental operationnel pour des applications de services d'un reseau de telecommunication |
EP96930159A EP0850545A1 (fr) | 1995-09-15 | 1996-09-03 | Systeme environnemental operationnel pour des applications de services d'un reseau de telecommunication |
Publications (1)
Publication Number | Publication Date |
---|---|
EP0850545A1 true EP0850545A1 (fr) | 1998-07-01 |
Family
ID=8219619
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP96930159A Ceased EP0850545A1 (fr) | 1995-09-15 | 1996-09-03 | Systeme environnemental operationnel pour des applications de services d'un reseau de telecommunication |
Country Status (3)
Country | Link |
---|---|
US (1) | US6496861B1 (fr) |
EP (1) | EP0850545A1 (fr) |
WO (1) | WO1997010683A1 (fr) |
Families Citing this family (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE19844825A1 (de) * | 1998-09-30 | 2000-04-13 | Alcatel Sa | Verfahren, Dienststeuerungseinheit, Dienstvermittlungsstelle und Kombinationsknoten zum Bereitstellen von Telekommunikationsdiensten |
US6647420B2 (en) * | 2001-01-18 | 2003-11-11 | Reynolds And Reynolds Holdings, Inc. | Enterlink for providing a federated business to business system that interconnects applications of multiple companies |
US7231433B1 (en) | 2000-01-19 | 2007-06-12 | Reynolds And Reynolds Holdings, Inc. | Enterlink for providing a federated business to business system that interconnects applications of multiple companies |
US6693898B1 (en) * | 2000-02-01 | 2004-02-17 | Lucent Technologies, Inc. | Call control model for a packet-based intelligent telecommunications network |
US6766482B1 (en) | 2001-10-31 | 2004-07-20 | Extreme Networks | Ethernet automatic protection switching |
US7757242B2 (en) * | 2006-05-26 | 2010-07-13 | International Business Corporation | Apparatus, system, and method for asynchronous outbound transaction event processing into an SAP application using service oriented architecture |
US7917651B2 (en) * | 2006-05-26 | 2011-03-29 | International Business Machines Corporation | Apparatus, system, and method for asynchronous complex inbound transactions from SAP applications using service oriented architecture |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4617663A (en) | 1983-04-13 | 1986-10-14 | At&T Information Systems Inc. | Interface testing of software systems |
JPH06502941A (ja) * | 1990-07-20 | 1994-03-31 | テンプル ユニヴァーシティ―オブ ザ コモンウエルス システム オブ ハイヤー エデュケーション | 異種オペレーティングシステムを有する高レベル仮想コンピュータのシステム |
JP2734465B2 (ja) * | 1991-04-10 | 1998-03-30 | 三菱電機株式会社 | ネットワーク用入出力装置 |
US5237684A (en) * | 1991-08-12 | 1993-08-17 | International Business Machines Corporation | Customized and versatile event monitor within event management services of a computer system |
US5488648A (en) | 1993-08-17 | 1996-01-30 | Telefonaktiebolaget L M Ericsson | Behavior monitoring and analyzing system for stored program controlled switching system |
JPH09512970A (ja) * | 1994-04-21 | 1997-12-22 | ブリティッシュ・テレコミュニケーションズ・パブリック・リミテッド・カンパニー | 通信ネットワーク用サービス作成装置 |
US5956489A (en) * | 1995-06-07 | 1999-09-21 | Microsoft Corporation | Transaction replication system and method for supporting replicated transaction-based services |
US5751964A (en) * | 1995-09-12 | 1998-05-12 | International Business Machines Corporation | System and method for automatic determination of thresholds in network management |
US6338088B1 (en) * | 1995-11-02 | 2002-01-08 | British Telecommunications Public Limited Company | Service creation apparatus for a communications network |
-
1996
- 1996-09-03 EP EP96930159A patent/EP0850545A1/fr not_active Ceased
- 1996-09-03 US US09/043,253 patent/US6496861B1/en not_active Expired - Fee Related
- 1996-09-03 WO PCT/EP1996/003865 patent/WO1997010683A1/fr active Application Filing
Non-Patent Citations (1)
Title |
---|
See references of WO9710683A1 * |
Also Published As
Publication number | Publication date |
---|---|
WO1997010683A1 (fr) | 1997-03-20 |
US6496861B1 (en) | 2002-12-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
DE69228819T2 (de) | Konfigurations- und Betriebsverfahren eines Telekommunikationsgeräts | |
DE69837010T2 (de) | System und verfahren zum steuern des zugriffs auf eine vermittlungsdatenbank | |
EP0743595B1 (fr) | Système de communication avec des moyens pour l'echange de logiciel | |
DE19681682B4 (de) | Telekommunikationsnetz-Verwaltungssystem | |
DE3879071T2 (de) | Verwaltung einer defekten Hilfsquelle in einem Multiplex-Kommunikationssystem. | |
DE69932567T2 (de) | Redundante Anrufverarbeitung | |
DE3879072T2 (de) | Expertsystem zur Verarbeitung von Fehlern in einem Multiplex-Kommunikationssystem. | |
DE602005004334T2 (de) | Nms zur Verarbeitung von Multi-Server Ereignissen | |
DE69829759T2 (de) | Verteilung von nachrichten zu dienststeuereinrichtungen | |
DE69733543T2 (de) | Verfahren zum Anbieten von wenigstens einem Dienst an Fernmeldenetzbenutzern | |
DE69732221T2 (de) | Verfahren zum Anbieten von einem Dienst an Fernmeldenetzbenutzern | |
EP0825524A1 (fr) | Procédé pour nommer des objets | |
DE69833026T2 (de) | Verfahren und system zur automatischen überprüfung der bereitstellung von fernmeldediensten | |
EP0973342A2 (fr) | Procédé et système de communication pour le traitement d'alarmes par un réseau de gestion comportant plusieurs niveaux de gestion | |
DE69421178T2 (de) | Fehlertolerantes dienstleistungsanbietungsgerät zur verwendung in einem telekommunikationssystem | |
EP0959588A2 (fr) | Elément de réseau avec le dispositif de commande et la méthode de contrÔle | |
EP0915435A2 (fr) | Procédé pour stocker en sécurité des données variables | |
DE69322857T2 (de) | Management in telecom und offenen systemen | |
DE10000825A1 (de) | Verfahren, Vermittlungsstelle, Gebührenrechner, Gebührenabrechnungsrechner und Programm-Module zur Verarbeitung von Gebührendaten für Telekommunikations-Dienstleistungen | |
DE69731182T2 (de) | Nachrichtenverfahren zwischen einer Dienstvermittlungsstelle und einer Dienstkontrolleinrichtung in einem Fernmeldenetz | |
DE69825560T2 (de) | Intelligentes netzwerk mit einer verteilten dienststeuerungsfunktion | |
EP0850545A1 (fr) | Systeme environnemental operationnel pour des applications de services d'un reseau de telecommunication | |
EP1198143A2 (fr) | Système de gestion de réseau | |
DE60101999T2 (de) | Dienstenentwicklungsumgebung | |
EP1371236A1 (fr) | Procede de reacheminement selectif et collectif de messages dans un reseau de gestion de telecommunications |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 19980304 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): DE FR GB IT |
|
17Q | First examination report despatched |
Effective date: 20001228 |
|
APBR | Date of receipt of statement of grounds of appeal recorded |
Free format text: ORIGINAL CODE: EPIDOSNNOA3E |
|
APBX | Invitation to file observations in appeal sent |
Free format text: ORIGINAL CODE: EPIDOSNOBA2E |
|
APBZ | Receipt of observations in appeal recorded |
Free format text: ORIGINAL CODE: EPIDOSNOBA4E |
|
APBT | Appeal procedure closed |
Free format text: ORIGINAL CODE: EPIDOSNNOA9E |
|
APAA | Appeal reference recorded |
Free format text: ORIGINAL CODE: EPIDOS REFN |
|
APAF | Appeal reference modified |
Free format text: ORIGINAL CODE: EPIDOSCREFNE |
|
APBN | Date of receipt of notice of appeal recorded |
Free format text: ORIGINAL CODE: EPIDOSNNOA2E |
|
APBR | Date of receipt of statement of grounds of appeal recorded |
Free format text: ORIGINAL CODE: EPIDOSNNOA3E |
|
APAF | Appeal reference modified |
Free format text: ORIGINAL CODE: EPIDOSCREFNE |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED |
|
18R | Application refused |
Effective date: 20060319 |
|
APBT | Appeal procedure closed |
Free format text: ORIGINAL CODE: EPIDOSNNOA9E |