EP1205078A2 - Systeme de gestion de reseau intelligent - Google Patents

Systeme de gestion de reseau intelligent

Info

Publication number
EP1205078A2
EP1205078A2 EP00951332A EP00951332A EP1205078A2 EP 1205078 A2 EP1205078 A2 EP 1205078A2 EP 00951332 A EP00951332 A EP 00951332A EP 00951332 A EP00951332 A EP 00951332A EP 1205078 A2 EP1205078 A2 EP 1205078A2
Authority
EP
European Patent Office
Prior art keywords
service
manager
comprises means
management
invocations
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.)
Withdrawn
Application number
EP00951332A
Other languages
German (de)
English (en)
Inventor
Richard Mcconnell
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Great Elm Group Inc
Original Assignee
Openwave Systems Inc
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Openwave Systems Inc filed Critical Openwave Systems Inc
Publication of EP1205078A2 publication Critical patent/EP1205078A2/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q3/00—Selecting arrangements
    • H04Q3/0016—Arrangements providing connection between exchanges
    • H04Q3/0062—Provisions for network management
    • 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
    • H04Q3/005—Personal communication services, e.g. provisions for portability of subscriber numbers

Definitions

  • the invention relates to an intelligent network management system.
  • Intelligent networks operate on the basis of removing "intelligence" from centralised systems and placing it in distributed computer nodes.
  • Another object is that the management system allows access to information transparently of the location of the software or hardware platform.
  • an network management system comprising:
  • a service control point for interfacing with a telecommunications signalling network and for interfacing with CORBA-based intelligent network services
  • a service data point for interfacing with the service control point; and a service management system for service and customer management.
  • the service control point comprises means for mapping signalling network protocol invocations to CORE A invocations.
  • the service control point comprises a service switching point simulator for receiving signalling network service requests and for sending responses to a signalling network.
  • the service switching point simulator comprises means for providing access to a plurality of clients as signalling network users.
  • the service control point comprises a service selection interaction manager comprising means for mapping invocations between a signalling network protocol and CORBA.
  • the service selection and interaction manager comprises a stack manager comprising means for monitoring incoming service requests and for translating them into associated invocations, and a service manager comprising means for managing said invocations.
  • the stack manager comprises means for managing a pool of signalling network objects allocated to service invocations.
  • the service manager comprises means for managing a service handler object for interacting with an application manager of the service control point.
  • the service selection and interaction manager comprises means for maintaining a table of service references and for accessing a service configuration file mapping service operation codes with service descriptions.
  • the service control point further comprises a service load disperser comprising means for performing load balancing of a pool of service servers on a per- in vocation basis.
  • the service load disperser comprises means for creating a service manager object for handling requests for services.
  • the service load disperser comprises means for registering the object reference of the service manager object with a CORBA names service.
  • the service data point comprises a database load disperser for interfacing between clients requiring database access and database access servers.
  • the database load disperser comprises means for creating an instance of a dummy object, for associating a loader object with it, and for registering the dummy object with a CORBA names service.
  • the loader object comprises means for executing a load- balancing algorithm when invoked.
  • the service management system comprises means for interfacing with an application manager of the service control point and for providing service management, customer management, and network management interfaces.
  • the service management system comprises a plurality of manager stations, each comprising for making invocations on the application manager according to user instructions.
  • each manager station comprises means for passing object references to the application manager, and the application manager comprises means for reporting alarm conditions using said object references.
  • Fig. 1 is a schematic representation of an intelligent network management system showing the manner in which it is connected to a telecommunication network;
  • Fig. 2 is a more detailed diagram showing the internal architecture of the management system
  • Fig. 3 is a diagram showing the architecture of a service switching point simulator of the system
  • Fig. 4 is a diagram showing the architecture of a service selection interaction manager
  • Fig. 5 is a diagram showing interaction for service selection/creation/invocation
  • Fig. 6 is a diagram showing the interfaces of a data load disperser
  • Fig. 7 is a diagram showing the management architecture of the system
  • Fig. 8 is a diagram showing a global view of a portability service in the system.
  • Fig. 9 is an information flow sequence diagram for a number portability service.
  • an intelligent network management system 1 of the invention is illustrated.
  • the system 1 is shown connected to a telecommunication network 2 comprising local exchanges 3, an intelligent peripheral (IP) 4, a trunk exchange 5, and a C 7 signalling network 6.
  • IP intelligent peripheral
  • the system 1 comprises a management interface 7.
  • a service creation environment (SCE) 8 is connected to an SCE interface 9.
  • the SCE 8 and the management interface 7 are connected to a service management system (SMS) 10, in turn connected to a service switching point (SCP) 11.
  • the SCP 11 is connected to a service data point (SDP) 12.
  • Both the SCP 11 and the SDP 12 are connected to the telecommunication network 2.
  • the interrupted lines represent signalling paths
  • the full lines in the system 1 represent management links
  • the full lines in the network 2 represent speech paths.
  • the system 1 provides an SS7 interface to CORBA-based intelligent network (IN) services, and also provides a service management interface, a customer management interface, and a network management interface.
  • I CORBA-based intelligent network
  • the SCP 11 interprets incoming SS7 messages and translates them into service invocations and controls execution of services, in this embodiment a number portability service.
  • the number portability service is one example of a service which is provisioned by the system 1, however, it is envisaged that many other types of services may be provisioned.
  • the SDP 12 provides access to a database for translation purposes and the SMS 10 provides management functions.
  • the SCP 11 comprises a service switching point (SSP) 15 for interaction with the signalling network 6.
  • SSP service switching point
  • the SCP 11 maps a telecommunication protocol, in this embodiment an INAP protocol, to CORBA.
  • INAP invocations are transferred to CORBA invocations in a CORBA environment having an Orbix TM names database 42.
  • the SSP 15 comprises a Service Switching Point Simulator (SSPS) 16 and an SS7 process 17.
  • SSPS Service Switching Point Simulator
  • the SS7 process 17 exports an INAP API to the SSPS 16, to allow the SSPS send INAP service requests to the remainder of the SCP 11.
  • the SSPS 16 is shown in more detail in Fig. 3.
  • An internal SS7 process 18 interfaces with the C7 signalling network 6, and INAP service requests are received by an SSPS receiver function 19 and logged to a Received File 20.
  • An SSPS sender function 21 sends INAP responses to the C7 signalling network 6 and logs the responses to a Sent File 22.
  • An SSPS analyser function 23 analyses the contents of the files 20 and 22 and maintains a status file 24.
  • the internal SS7 process 18 performs two related functions as follows: providing the SSPS 16 with an API to an ETSI INAP CS-1 message set and therefore send/receive SS7 messages to/from another stack in the network 2, and
  • the SSPS 16 provides sessions to a large number of clients by multiplexing connections and any number of clients can connect and initiate a session to the SS7 process and become an INAP user. In doing this, they receive a unique socket reference which can be used to receive and send INAP messages.
  • the SCP 11 also comprises a service selection/ interaction manager (SSIM) 30.
  • SSIM service selection/ interaction manager
  • This performs a very important function in mapping invocations between INAP and CORBA.
  • a detailed breakdown is shown in Fig. 4.
  • a stack manager 35 monitors incoming SSI service requests and translates them into associated invocations on a service manager 36. It also manages a pool of INAP Objects, which are allocated to service invocations.
  • Each INAP Object allows the following:
  • each INAP Object automatically reports any SS7 errors to an Application Manager 50, also shown in Fig. 2.
  • an Application Manager 50 also shown in Fig. 2.
  • a Service Handler Object implements the interface, and the main operations available in this interface are:
  • Service Handler Object reports any error conditions to the Application Manager 50, such as receiving requests for services that are not provisioned.
  • FIG. 5 the immediate actions following the service start-up and the transactions required for an ensuing service invocation are illustrated.
  • a Service Load Disperser (SLD) 40 is linked between incoming service requests and a pool of Service Servers 41 to facilitate load balancing on a per-invocation basis.
  • the first action of the SLD 40 is to create a SERVMANAGER object. This object handles requests for services and maintains a list of real server references relating to the backend objects contained in the Service Servers 41.
  • the SLD 40 registers the object reference of the SERVMANAGER object with the names database 42.
  • the SSIM 30 receives an INAP message, which is interpreted as a request for a service.
  • the SSIM 30 will search a Service Configuration File 43.
  • the Service Configuration File 43 cross-references the INAP operation code of all services against a textual description of the service (the information contained in this file is configured from the SMS interface).
  • the SSIM uses the textual description retrieved from the Service Configuration File 43 to interrogate the names database 42 and retrieve the object reference to the appropriate SERVMANAGER object. This leads to dependencies between the information stored in the Service Configuration File 43 and that in the names database 42.
  • the SSIM 30 uses the retrieved object reference to build a one-way invocation to the SERVMANAGER object requesting invocation of the service to handle the INAP request.
  • the Service Server 41 will begin service execution.
  • the forms of external management performed by the SSIM 30 are as follows: • SSP Regulation - If the SSPS 16 is making service requests that are causing the system 1 platform to overload or excessively queue service requests then it will make use of an INAP object to send a "Call Gap" message to the SSPS. This request will cause the SSPS to terminate service request for a defined period. This type of scenario would also require an application specific event to be raised to the application manager 50 after which the event would then be translated into a SMS 10 user interface alarm.
  • INAP object to send an Activity Test INAP message to the SSPS and checking for a response. Non-responsive SSPS's will be reported to the application manager 50, resulting in an alarm being sent to the SMS 10 interface 7.
  • the SLD 40 server is placed between the SSIM 30 and the Service Servers 41 to provide a service specific interface for the selection and execution of services.
  • the SERVMANAGER object provides an interface to the following functional entities:
  • Application Manager 50 increase/decrease of Service Servers 41.
  • Each Service Server (SS) 41 contains a single object allowing any CORBA client the ability for service execution. Each client builds an IDL or DII request in a format identical across all services. Each SS 41 can also use the IDL interface in the SERVMANAGER for the reporting of errors during service execution and IDL to the INAP Object for the sending and the receiving of SS7 messages.
  • the database load disperser (DLD) 55 is placed between the clients who require database access and the Database Access Servers 56 performing database operations.
  • a DBLOADER mstance is a specialised loader, which contains a list of object references associated with the real Database Access Servers 56.
  • the actual implementation requires the Database Load Disperser 55 to create an instance of a dummy object and associate a DBLOADER instance with it. This dummy object is then registered with the names database 42 following which it is deleted, in the DLD 55. Clients wishing to access the database can then use the names database 42 to retrieve the object reference of the dummy object.
  • the DLD 55 also provides an interface to the following functional entities:
  • the DLD 55 automatically reports alarms via IDL to the SSIM 30 so that services can be informed to use a backup database, (if one exists). Alarms will also be reported to the Application Manager 50 to facilitate operator intervention.
  • Each Database Access Server 56 contains a single object allowing any CORBA client to access database information. Each client builds an IDL or DII request in a format identical to that specified for SCP to SDP and SDP to SCP INAP transactions. Each DAS 56 can also use the IDL interface in the DBLOADER object for reporting errors when attempting database access.
  • the SMS 10 comprises an Application Specific Manager (ASM) 60 and an OrbixTM Manager 61.
  • ASM 60 comprises a number of separate components which include the following.
  • a Management Library 63 This is linked into applications which are designated to be part of the managed system.
  • a Component Management Interface 62 This process is the main concentration point for the management of CORBA applications.
  • the system 1 allows for three distinct areas of management, as follows.
  • Service Management Provided by using the management interfaces exported by the component management interface.
  • Customer Management Provided by a Service Manager component of the SMS 10 using a JDBC interface to the database to provide the following operations:
  • Activity measurement for example, the number of invocations, exceptions, connections, throughput and queue lengths. Performed on a per-process or per- interface basis.
  • Probes and Request tickets - allows information gathering on status and timings of particular invocations
  • Exception Notification and dimmer function allows reporting on exceptions.
  • the dimmer function provides the ability to associate conditions with exceptions and therefore only report on critical exceptions.
  • Thresholds allows threshold values to be associated with runtime attributes. Exceeding a threshold with a predefined time period will result in a notification being sent.
  • Diagnostics Monitoring - allows the viewing of diagnostic output.
  • Configuration Files - allows configuration information to be obtained from the predefined Orbix configuration files.
  • Dynamic Management ability to turn management functionality on and off.
  • Each manager station 70 (shown in Fig. 2) provides a JAVA-based GUI to allow operators to perform service, customer, and network management.
  • Each manager station 70 has an IDL based interface to the Application Manager 50, allowing the retrieval of management based information and the sending of management based commands.
  • This client will also need to present an interface to the Application Manager 50 to allow the reporting of alarm conditions.
  • the primary purpose of this component is to allow management of both the CORBA environment and the all application-specific elements.
  • Manager Station 70 When the Manager Station 70 is started it creates an instance of its alarm interface and passes it to the Application Manager 50, along with the operator's details.
  • Application Manager 50 will then verify the user's details and respond to the Manager Station 70 client indicating that the access is permitted or refused. If access is granted then the relevant Manger Station 70 instance will make IDL invocations on the Application Manager 50 as dictated by the user's actions. The Application Manager 50 may also report alarm conditions to all active Manager Stations 70 suing the object references passed in during initiation. When the user terminates their interface session then the Service Manager 70 will again inform the Application Manager 50 and reference to the associated object reference will be removed.
  • a simple number portability service is provided by the system 1 and a global view of this is illustrated in Fig. 8.
  • An information flow sequence diagram is given in Fig. 9. The service requires that there is availability of an initial information package or the dialling string from the originating party.
  • the TRANSLATE object then performs translation of the originating routing information to a new routing case.
  • the POR specifies that call routing should continue acting on the new routing case. This may appear to be a simplistic service, but number translation is at the heart of the most common IN service such as freephone, credit car, premium charge, UPT and VPN.
  • the SCF uses the Query function to lookup the actual routing case to be used for the dialled digits. This information is sent back in the Query_Res message. 3. The SCF sends a Connect message to the SSF with the destination routing address to be used.
  • the BCSM moves into the Routing PIC and acts on the routing address provided by the SCF.
  • the Originating half of the BCSM received an indication from the terminating half that the called party has answered.
  • the 0_Active PIC can then be entered.
  • the invention provides for seamless distribution of IN services, for the network 2.
  • an IN service may be moved to an adjunct processor without any code changes.
  • the object-oriented methodology is used, there are well-defined interfaces.
  • the system can transparently interwork across networks, operating systems, and programming languages.
  • the system 1 can avail of CORBA services such as increased speed and flexibility of development and also availability of horizontal facilities such as user interface, time operations, and data interchange.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer And Data Communications (AREA)
  • Telephonic Communication Services (AREA)

Abstract

Un système (1) de gestion de réseau intelligent est en liaison avec un réseau de signalisation C7 (6) pour constituer une interface aux services de réseau intelligent fondé sur CORBA. Un point de commande de services (PCS, 11) interprète les requêtes de service à l'arrivée et les traduit en appels de service. Un exemple de service est un service de portabilité de numéro. Le PCS (11) comprend un répartiteur de charge de services (RCS) (40) qui interagit avec plusieurs serveurs (41) de services. Un point de données de services (12) comprend un répartiteur de charge de bases de données (RCBD) (55) qui interagit avec plusieurs serveurs d'accès à des bases de données. Un système de gestion de services (SGS) (10) est en liaison avec le RCBD (55) et avec un gestionnaire d'applications (50) pour gérer les services, les clients et le réseau.
EP00951332A 1999-07-01 2000-06-29 Systeme de gestion de reseau intelligent Withdrawn EP1205078A2 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
IE990554 1999-07-01
IE990554 1999-07-01
PCT/EP2000/006266 WO2001003447A2 (fr) 1999-07-01 2000-06-29 Systeme de gestion de reseau intelligent

Publications (1)

Publication Number Publication Date
EP1205078A2 true EP1205078A2 (fr) 2002-05-15

Family

ID=11042095

Family Applications (1)

Application Number Title Priority Date Filing Date
EP00951332A Withdrawn EP1205078A2 (fr) 1999-07-01 2000-06-29 Systeme de gestion de reseau intelligent

Country Status (3)

Country Link
EP (1) EP1205078A2 (fr)
AU (1) AU6431100A (fr)
WO (1) WO2001003447A2 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FI20001111A (fi) * 2000-05-10 2001-11-11 Nokia Corp Hajautetun tietokantajärjestelmän keskitetty hallinta
CN100417272C (zh) * 2002-04-18 2008-09-03 中兴通讯股份有限公司 一种移动通讯系统间的号码可携带方法

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5737517A (en) * 1995-12-21 1998-04-07 Ericsson, Inc. Testing tools in an intelligent network system
DE69717248T2 (de) * 1996-10-25 2003-05-08 Nortel Networks Ltd., St.Laurent Übertragungsleitung zum verbinden von dienststeuerpunkten einer lastverteilungsgruppe für verkehrsverwaltungssteuerung
DE69825560T2 (de) * 1997-01-15 2005-08-18 British Telecommunications P.L.C. Intelligentes netzwerk mit einer verteilten dienststeuerungsfunktion
JP3369445B2 (ja) * 1997-09-22 2003-01-20 富士通株式会社 ネットワークサービスサーバ負荷調整装置、方法および記録媒体
US6061729A (en) * 1997-12-31 2000-05-09 Alcatel Usa Sourcing, L.P. Method and system for communicating service information in an advanced intelligent network
FR2773656B1 (fr) * 1998-01-15 2000-02-11 Alsthom Cge Alcatel Passerelle intelligente entre un point de controle de service, et un reseau de signalisation

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO0103447A3 *

Also Published As

Publication number Publication date
WO2001003447A2 (fr) 2001-01-11
AU6431100A (en) 2001-01-22
WO2001003447A3 (fr) 2001-07-19

Similar Documents

Publication Publication Date Title
EP1131730B1 (fr) Procede et appareil de fourniture de services de traitement d'appels en temps reel dans un reseau intelligent
US7216350B2 (en) Methods and apparatus for call service processing by instantiating an object that executes a compiled representation of a mark-up language description of operations for performing a call feature or service
US6393481B1 (en) Method and apparatus for providing real-time call processing services in an intelligent network
US6151390A (en) Protocol conversion using channel associated signaling
US5526415A (en) Integrated communication system with intelligent network and telecommunications management network
USH1837H (en) Generic telecommunications system and associated call processing architecture
USH1921H (en) Generic wireless telecommunications system
US6226373B1 (en) Intelligent service peripheral/intelligent peripheral
CA2338149A1 (fr) Appareil d'interface multiprotocole en un point de commande de services
JP2002522932A (ja) インテリジェント分散型ネットワークアーキテクチャのための方法およびシステム
US6587890B1 (en) Switch controller application programmer interface
US6314172B1 (en) Method and system for providing service information in an advanced intelligent network
US6341162B1 (en) Telecommunications intelligent network
US7403606B1 (en) General protocol for service control point
US6526050B1 (en) Programming call-processing application in a switching system
EP1205078A2 (fr) Systeme de gestion de reseau intelligent
US20020184353A1 (en) Remote administration and monitoring of a service component in a service logic execution environment
US6272213B1 (en) Method and system for service engineering in an advanced intelligent network
US7203180B2 (en) Initiating service logic
KR100322671B1 (ko) 유무선통신망에서 국제표준을 적용한 지능망시스템
Kubota et al. Distributed processing platform for telecommunication networks
Almkvist et al. Preserving Integrity inTelecommunication Networks Opened bythe Parlay Service Interface
CA2317417A1 (fr) Procede et dispositifs d'un systeme de commande de processus ou isolation des ressources vis-a-vis de l'application dans un systeme de commande de processus
MXPA01001277A (en) Method and system for an intelligent distributed network architecture

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: 20011215

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE

AX Request for extension of the european patent

Free format text: AL;LT;LV;MK;RO;SI

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20060103