EP1025712A1 - Gestion d'interactions entre dispositifs dans des reseaux de telecommunications - Google Patents

Gestion d'interactions entre dispositifs dans des reseaux de telecommunications

Info

Publication number
EP1025712A1
EP1025712A1 EP98904268A EP98904268A EP1025712A1 EP 1025712 A1 EP1025712 A1 EP 1025712A1 EP 98904268 A EP98904268 A EP 98904268A EP 98904268 A EP98904268 A EP 98904268A EP 1025712 A1 EP1025712 A1 EP 1025712A1
Authority
EP
European Patent Office
Prior art keywords
service
feature
platform
features
feature data
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
EP98904268A
Other languages
German (de)
English (en)
Inventor
Michael John Crowther
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.)
British Telecommunications PLC
Original Assignee
British Telecommunications PLC
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 British Telecommunications PLC filed Critical British Telecommunications PLC
Priority to EP98904268A priority Critical patent/EP1025712A1/fr
Publication of EP1025712A1 publication Critical patent/EP1025712A1/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/0029—Provisions for intelligent networking
    • H04Q3/0041—Provisions for intelligent networking involving techniques for avoiding interaction of call service features
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42136—Administration or customisation of services
    • H04M3/4217—Managing service interactions

Definitions

  • the present invention relates to telecommunications networks, and in particular to the management of service interaction on telecommunications networks.
  • a method of operating a telecommunications network which includes a plurality of interconnected service platforms, and in which a plurality of the said service platforms each include a respective feature interaction controller, the method including: a) transmitting, from a feature interaction controller in a first service platform to a feature interaction controller in a second service platform, service feature data which relates to a service feature which is active at the first service platform, which service feature data identifies one or more other service features which have known interworking properties in relation to the said service feature, b) in the feature interaction controller at the second service platform, processing the said service feature data and detecting thereby any conflicts between the service features active at the first service platform and other service features which are active at the second service platform; and c) when any conflict is detected in step (b), modifying the operation of service features at the second platform and/or at the first platform in the course of a call which is processed by the both the first and second service platforms.
  • the present inventor has found that a crucial aspect of feature interaction relates to non-local interactions when for example, a feature which is provided at an originating exchange for a call clashes with a feature present on the destination exchange.
  • the present invention uses signalling between different platforms to share data on active service features, and processes all the relevant data, including data from other platforms, to ensure effective control of any potential interaction problems.
  • the data exchanged by the platforms is termed by the inventor "Feature Interworking Indicators" (Fll) .
  • Fll Feature Interworking Indicators
  • the service platforms may include, for example, customer premises equipment (CPE) - e.g. a personal computer having a telephony interface, core network switches including digital main switching units (DMSU's) or digital local exchanges (DLE's), and service control points (SCP's) .
  • CPE customer premises equipment
  • DMSU's digital main switching units
  • DLE's digital local exchanges
  • SCP's service control points
  • the service feature data includes a feature instance reference which uniquely identifies a specific instance of a service feature.
  • This preferred aspect of the invention allows the second platform to track and manage individual instances of a service feature, and makes possible correlation with possible later references to the same service feature.
  • the service feature data includes a feature precedence indicator for the service feature.
  • the service feature data includes persistence data.
  • Persistence data indicates whether a service feature may be active later in a call.
  • the first platform transmits service feature data both for features which are already active at the first platform, and for pending features which may be invoked depending upon the result of step (b).
  • the service feature data includes an active/pending indicator.
  • This aspect of the invention maximises the flexibility of the interaction management process by allowing the first platform to signal data on features it intends to invoke provided that there is no interaction problem at the second platform.
  • the service feature data identifies nominated partner features and/or nominated rival features.
  • Partner features are other features which the relevant service feature is known to interwork successfully with. Conversely, rival features are other features which are known to conflict with the relevant feature.
  • the first platform can speed identification and resolution of conflicts at the second platform. Moreover, this approach allows the resolution of conflicts between features in circumstances where merely assigning precedence values is not sufficient to overcome the problem.
  • Other options which may be included in the service feature data include a service feature reference giving access to interworking information which is stored elsewhere in the network.
  • the data may also include information about the past history of a feature.
  • the initial service feature data is transmitted from the first platform to the second platform before the second platform has started running any service feature in the relevant call context.
  • the second service platform transmits service feature data to the first service platform and both the first and second platforms process service feature data to detect any conflicts.
  • service feature data is transmitted in both directions between the platforms and may, for example, be transmitted backwards from a downstream platform towards an originating exchange, for example when new information about active features arises during the course of a call.
  • the feature interaction management process can then be fully distributed between the platforms.
  • a service platform for use in a telecommunications system, the service platform including: a) service logic for implementing a service feature function b) a feature interaction controller arranged to process service feature data and to detect any conflicts between service features, and c) a service feature data interface which is connected to the feature interaction controller and which is arranged to be connected to the telecommunications network to receive, via the network, service feature data for a service feature which is active or pending at a second service platform which is remote from the said service platform, which service feature data identifies one or more other service features which have known interworking properties in relation to the said service feature.
  • a method of operating a service platform in a telecommunications network comprising: a)stor ⁇ ng, for a service feature, service feature data which identify one or more other service features which have known interworking properties in relation to the said service feature, b)when a new service feature is to be invoked at the service platform, and when at least one existing service feature is already active or pending at the service platform, reading the service feature data for one of the said new service feature and the existing service feature c)compar ⁇ ng the identity of the other of the new service feature and the existing service feature with the service features which are identified in the said service feature data, d)mod ⁇ fy ⁇ ng the operation of the said service platform depending on the presence or absence of the said identity in the said service feature data
  • service feature data which identifies other service features which have known interworking properties facilitates rapid identification and resolution of any interworking problems. Although it is preferred that this should be carried out in accordance with the non-local interaction control of the first aspect of the invention, it is not limited to use in this way, and may be used in the context of otherwise conventional local interaction control processes.
  • a telecommunications system comprising: a) a telecommunications network; b) a first service platform which is connected to the telecommunications network and which includes: first service logic for implementing a service feature function, a first feature interaction controller arranged to process service feature data and to detect any conflicts between service features, and a first service feature data interface which is connected to the feature interaction controller and is arranged to output service feature data onto the network; c) a second service platform which is connected to the telecommunications network and which includes: second service logic for implementing a service feature function, a second service feature data interface which is connected to the network, and a second feature interaction controller which is connected to the second service feature data interface and which is arranged to process both locally originating service feature data and service feature data which is received from the first service platform via the network and via the second service feature data interface and to detect thereby any conflict between service features.
  • Figure 1 is a schematic of a network embodying the present invention
  • Figure 2 is a schematic showing the architecture of a switch for use in the network of Figure 1 :
  • Figures 3a and 3b illustrate the format of network signalling suitable for carrying feature interaction indicators (Fll)
  • Figure 4 is a diagram showing a first example of Fll information flows between platforms
  • Figure 5 is a flow diagram showing the operation of a feature interaction controller in a first embodiment
  • Figure 6 is a flow diagram showing the operation of a feature interaction controller in a second embodiment. DESCRIPTION OF EXAMPLES
  • a telecommunications network includes a first service platform 1 and a second service platform 2.
  • each service platform is a digital local exchange (DLE) which is connected to the core UK telecommunications network
  • DLE digital local exchange
  • the service platforms use a call chain software architecture, as described in detail in the paper by H. M. Blair, "Attacking product complex ⁇ ty:broadband call control for Vision O.N.E " , XIV International Switching Symposium, 1 992.
  • Functions which are implemented by the service platforms are carried out using software modules known as "segments" .
  • Different segments communicate with each other via a standard signalling interface. The functioning of the different segments is coordinated by a user segment. The user segment detects when a user has a feature provisioned.
  • the user segment then invokes an instance of the or each feature segment required to implement the relevant service features.
  • Feature segments are linked into different positions in the chain depending on how they work with other features.
  • Each feature segment can absorb or pass downstream events which come from the access segment.
  • the user segments each include a respective feature interaction controller (FIC) .
  • FIC feature interaction controller
  • the FIC blocks the invocation of features which would conflict with features which already part of a call chain.
  • Each FIC accesses service feature data which is stored in a respective local database.
  • each FIC receives and transmits feature interworking indicators (Fll) via a signalling interface 3,4 to the other FIC.
  • Fll feature interworking indicators
  • FIG. 2 shows the physical architecture of a switch which is suitable for use in implementing the present invention.
  • the switch is based on a design developed by Siemens AG and described in the paper "Control Architecture for ATM based Switching Systems" , Nick Skaperda , IEEE GlobeCom'92.
  • This switch use an ATM switching network 21 .
  • a subscriber line unit (SLU) 22 connects both narrowband and broadband subscriber terminals to the switching network.
  • An ATM overlay network 23 is connected via an Access Unit 24 and an STM (Synchronous Transfer Mode) network 25 is connected via an Interworking Unit (IWU) 26.
  • the switch logic is implemented by a number of general processing elements (GP) 27 and a control processor (CP) which are connected to the switching network via an ATM multiplexer 28.
  • GP general processing elements
  • CP control processor
  • the user segment including the FIC, is implemented on one of the general processing elements 27, or on a cluster of such processing elements.
  • the general processing elements are, for example, DEC Alpha processors running the UNIX operating system.
  • Each software module or segment is implemented as an independently scheduled process provided by the UNIX operating system.
  • UNIX also provides for inter-process communication.
  • the use of a portable operating system such as UNIX effectively makes the call control processes and the feature interaction control features independent of the underlying processor architecture, and makes it straightforward to implement these processes on different platforms.
  • the information flows on the Fll channel allow the first service platform to provide the other service platform with interworking information relating to the service instances which are local to the transmitting service platform.
  • the FIC in the receiving service platform uses this information in order to control the operation of any of its own services which are operating in the same call context as the transmitting service platform. In particular it may cancel or delay the operation of service features which would give rise to a conflict with features on the originating platform.
  • the Fll information may be used to choose a service variant that can interwork successfully with the existing feature context.
  • the originating service platform transmits Fll relating to service features which have not yet been invoked, but which will be invoked if the receiving service platform surrenders its opportunity to invoke its services.
  • the Fll data includes the following elements: a)CALL CONTEXT. This includes a call reference or some other identifying reference such as a Transaction Identity. This data is used to associate the Fll with any other service instances which may be relevant.
  • the call reference may be included implicitly in an existing call control signalling message, b) FEATURE PRECEDENCE.
  • Feature Precedence is defined in ITU Rec. Q1 21 4 (Madrid Jan 1 995) section 4.2.4. Its use has previously been proposed for local resolution of interworking problems. Whenever two or more service features are in conflict, then the feature with the higher precedence is invoked, and the feature which has lower precedence is not invoked.
  • Feature Interaction Manager a Feature Interaction Manager
  • the FIC includes the functionality of an FIM as defined in the above ITU standard.
  • the FIC processes Feature Precedence data for both local and remote service features.
  • the Fll data includes: a)CALL CONTEXT - as defined above. b) LOCAL SERVICE INSTANCE. This reference allows correlation with any later operations which refer to the same feature instance. c) PERSISTENCE INDICATOR. If the feature is completed there will be no more Flls for this feature. If the feature is not completed then there may be further Flls which indicate the results of event trigger processing. d) ACTIVE/PENDING INDICATOR. Active indicates that the information refers to a feature which is already active in the feature context. Pending indicates that the information refers to a feature which would run if the receiving service platform were to surrender its opportunity to invoke conflicting service features.
  • the Fll data includes: a) CALL CONTEXT - as defined above.
  • SERVICE FEATURE REFERENCE F This reference may be used to access interworking data which is stored locally at the platform, or is stored elsewhere in the network.
  • NOMINATED PARTNER FEATURES This identifies other features with which service feature F is known to interwork successfully. These other service features may be named individually, or ALL features may be designated as partner features.
  • NOMINATED RIVAL FEATURES This identifies other features with which service feature F is known to interfere, or which interfere with service feature F.
  • an initial Fll is sent from an originating service platform to a receiving service platform before the receiving service platform has started running any services in the relevant feature context.
  • This Fll is interpreted by the receiving service platform as meaning that the feature has started running in the originating service platform.
  • the initial Fll may appropriately be included in the first call progress/service control signalling message which relates to the feature context.
  • a service platform can source an Fll from the time it detects that a feature instance F will be run until the time that it passes control to another service platform.
  • the Fll sourced from the originating service platform, or any Fll received from another service platform are sent to any other service platforms which are known to be involved in the same feature context as F.
  • Flls may be sent backwards in the direction of the call originator.
  • the Fll may be sent immediately upon detection of a particular feature instance at the transmitting service platform, or may be transmitted at a later time when an association with a further service platform is set up.
  • the Fll is incorporated within ISUP (ISDN User Part) and INAP (Intelligent Network Application Part) signalling.
  • ISUP signalling the ISUP remote operations parameter is used.
  • This parameter defined in ITU draft Q.763 section 3.48 is an optional parameter of many ISUP messages.
  • Figure 3 shows the standard format of an ISUP message. This includes a mandatory fixed part 31 , a mandatory variable part 32 and an optional part 33.
  • the remote operations parameter is included in the optional part 33.
  • Figure 3b shows the format of the parameter.
  • the initial octet of this parameter is set to 0001 0001 to indicate that the parameter relates to the remote operations protocol.
  • the remainder of the parameter contains one or more components as defined in Q.763 section 3.48 of the ITU standard.
  • Fll information is carried by an invoke component which carries a Featurelnteractionlndication operation. This operation is formally defined in Appendix A.1 below.
  • CS.1 capability set 1
  • many operations can include a Servicelnteractionlndicators field, as defined in ITU Q.1 21 9 section 2.1 .3.
  • the content of this field is defined as in FeaturelnteractionlndicationArg shown in Appendix A.2 below.
  • Figure 4 illustrates information flows between platforms, showing the C7 signalling messages, the values of the Feature Interaction Indications (Fll) which are carried by those messages and the actions which are taken by the call control software in the switching systems.
  • Fll Feature Interaction Indications
  • the exchange of Fll data enables a service, Personal Numbering (PN), which is based at an originating SSP to interwork correctly with another service, Diversion Immediate, which is based at a terminating exchange 43.
  • PN Personal Numbering
  • Diversion Immediate which is based at a terminating exchange 43.
  • Signalling between the originating SSP 41 and an SCP 42 uses C7 Intelligent Network Application Part (INAP) .
  • INAP Intelligent Network Application Part
  • Signalling between originating and terminating local exchanges uses C7 ISDN user part (ISUP) .
  • ISUP ISDN user part
  • transit exchanges have been omitted for clarity.
  • explicit precedence data is used, as in the first implementation discussed above.
  • the first actions related to interaction management are taken by the SCP. It inserts an Fll parameter into the first call progress signalling message m l which it sends to the SSP after invoking the PN service feature.
  • the C7 INAP Connect message m2 then carries a Serviceinteractionlndications field with the following value (defined using ASN.1 value notation) :
  • the SSP functions of the originating local exchange now store this information for local feature interaction management purposes and for passing on to other service platforms involved in this call.
  • the action requested by the SCP was to route the current call to a new destination number, which involves sending an ISUP Initial Address Message (IAM) rm3 to the local exchange serving that number.
  • IAM ISUP Initial Address Message
  • the C7 ISUP Initial Address Message (IAM) m3 carries a Remote Operations parameter, the first octet encoded with the value "00010001 ' to indicate the remote operations protocol.
  • the remaining octets carry a single Remote Operations Service Element (ROSE) component.
  • ROSE Remote Operations Service Element
  • the terminating local exchange On receiving the lAM, stores the Fll data for local feature interaction management purposes and for passing on to any other service platforms involved in the call.
  • the User Transaction Segment module of the exchange's call processing software determines that the destination line has the Diversion Immediate (Dl) service feature provisioned and examines local feature interaction data to determine whether there are service features active which would interact with this feature.
  • the Dl service feature is not invoked and linked into the call chain, and the Personal numbering service is correctly delivered to its user.
  • FIG. 5 is a flow diagram showing the steps carried out by the feature interaction controller in this example.
  • Diversion Immediate is provisioned at the destination exchange.
  • the lAM is received from the originating SCP.
  • the Fll data is read from the lAM.
  • the Fll data includes a feature precedence value for the Personal Numbering feature which is active at the originating SCP.
  • the Fll data is stored for further processing.
  • the feature interaction controller determines whether there is any conflict between the feature identified in the Fll data, and the Diversion Immediate feature. If there is not, then both Personal Numbering and Diversion Immediate are linked into the call chain (step 5.6).
  • the feature interaction controller reads the precedence values for the relevant features (step 5.7) .
  • the values are compared, and one only of the features is invoked and linked into the call chain, depending on the results of the comparison (steps 5.9, 5.10) .
  • the services involved are again Personal Numbering and Diversion Immediate.
  • the Fll signalling and the feature interaction control processes use nominated rival features, as in the third implementation outlined above.
  • the SCP inserts an Fll parameter into the first call progress signalling message which it sends to the SSP after invoking the personal numbering (PN) service feature.
  • the SSP functions of the originating local exchange now store this information for local feature interaction management purposes and for passing on to other service platforms involved in this call.
  • the action requested by the SCP was to route the current call to a new destination number, which involves sending an ISUP Initial Address Message (lAM) to the local exchange serving that number.
  • lAM ISUP Initial Address Message
  • the C7 ISUP Initial Address Message (lAM) carries a Remote Operations parameter, the first octet encoded with the value "0001 0001 'B to indicate the remote operations protocol.
  • the remaining octets carry a single Remote Operations Service Element (ROSE) component.
  • ROSE Remote Operations Service Element
  • the terminating local exchange On receiving the lAM, the terminating local exchange stores the Fll data for local feature interaction management purposes and for passing on to any other service platforms involved in the call.
  • the User Transaction Segment module of the exchange's call processing software determines that the destination line has the Diversion Immediate (Dl) service feature provisioned and examines local feature interaction data to determine whether there are service features active which would interact with this feature.
  • This local data now includes the Fll data received from the originating local exchange, so the terminating local exchange is able to compare each of the rival Featureldentifiers associated with the features active in the current call with the Featureldentifier of the provisioned feature Diversion Immediate. There is a match, so the Dl service feature is not invoked and linked into the call chain, and the Personal numbering service is correctly delivered to its user.
  • FIG. 6 illustrates the operation of the Feature Interaction Controller at the terminating exchange in this example.
  • Dl is provisioned at the exchange.
  • the lAM message is received from the originating SCP.
  • the Feature Interaction Controller reads the Fll data from the lAM.
  • the Fll data includes a list of nominated rival service features
  • the Fll data is stored for further processing
  • the Feature Interaction Controller carries out a search to determine if the provisioned feature, Dl, matches any of the rival features listed in the Fll data. If no match is found, then both PN and Dl might be invoked and linked in the call chain (step 6.6) . However, in the present example, Dl is found in the list of rival features Accordingly, the operation of the Dl feature is inhibited and only PN is invoked and linked in the call chain (step 6.7) .
  • Featurelnteractionlndication Arg : : SEQUENCE ⁇ contextID OCTET STRING (SIZE(ContextlDLength)) OPTIONAL,
  • the context ID may be implied by local call references fiiElements Fll Elements
  • the featurelD is only necessary if the operation doesn't contain sufficient - information for interaction management, but the information can be looked up
  • this information can be used for interaction management if a precedence
  • NominatedFeatures : : SEQUENCE OF FeaturelD
  • FeaturelD : : OCTET STRING (SIZE(FeaturelDLength))
  • these may be locally defined by network operator/service provider, or the
  • personalNumberingHistoryArg : : SEQUENCE ⁇ originalDialledNumber OCTET STRING (SIZE(minDigitsLength..maxDigitsLength))

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)

Abstract

Dans un système de télécommunications, diverses plates-formes de service comportent des contrôleurs d'interaction entre dispositifs. Lorsqu'il fonctionne, un contrôleur d'interaction entre dispositifs d'une plate-forme transmet au contrôleur d'interaction entre dispositifs d'une autre plate-forme des données relatives à la caractéristique du service qui fonctionne sur la plate-forme de transmission. Le contrôleur d'interaction entre dispositifs de la seconde plate-forme utilise alors les données en provenance de la première plate-forme pour détecter et commander des comportements d'interaction non locaux. Par exemple, le contrôleur d'interaction entre dispositifs peut bloquer le fonctionnement d'un dispositif de service donné de la seconde plate-forme si elle est susceptible d'être en conflit avec un ou plusieurs services déjà en fonctionnement sur l'autre plate-forme.
EP98904268A 1997-02-14 1998-02-12 Gestion d'interactions entre dispositifs dans des reseaux de telecommunications Withdrawn EP1025712A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP98904268A EP1025712A1 (fr) 1997-02-14 1998-02-12 Gestion d'interactions entre dispositifs dans des reseaux de telecommunications

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
EP97300990 1997-02-14
EP97300990 1997-02-14
PCT/GB1998/000431 WO1998036583A1 (fr) 1997-02-14 1998-02-12 Gestion d'interactions entre dispositifs dans des reseaux de telecommunications
EP98904268A EP1025712A1 (fr) 1997-02-14 1998-02-12 Gestion d'interactions entre dispositifs dans des reseaux de telecommunications

Publications (1)

Publication Number Publication Date
EP1025712A1 true EP1025712A1 (fr) 2000-08-09

Family

ID=8229220

Family Applications (1)

Application Number Title Priority Date Filing Date
EP98904268A Withdrawn EP1025712A1 (fr) 1997-02-14 1998-02-12 Gestion d'interactions entre dispositifs dans des reseaux de telecommunications

Country Status (3)

Country Link
EP (1) EP1025712A1 (fr)
AU (1) AU6221598A (fr)
WO (1) WO1998036583A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2503809B (en) 2008-12-04 2014-07-23 Metaswitch Networks Ltd Telephone call processing

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5337351A (en) * 1992-02-28 1994-08-09 Nec America, Inc. Feature interaction arbitrator
US5404396A (en) * 1993-08-27 1995-04-04 Telefonaktiebolaget Lm Ericsson Feature interaction manager

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
AU6221598A (en) 1998-09-08
WO1998036583A1 (fr) 1998-08-20

Similar Documents

Publication Publication Date Title
US7039173B2 (en) Management of performance of intelligent network services
US5551035A (en) Method and apparatus for inter-object communication in an object-oriented program controlled system
US8279862B2 (en) Centralized service control for a telecommunication system
US6259776B1 (en) System for controlling telecommunication overload traffic
EP0730805A1 (fr) Agencement pour partager un code de central telephonique
HU221399B1 (en) Method for processing calls, telecommunication system, telecommunication computer system and processor
KR20010022744A (ko) 전화 번호 이식성을 부여하는, 전화망에서의 호출명 전송 관리
RU2156036C2 (ru) Способ освобождения ненужных магистралей от телефонного вызова
EP0405829B1 (fr) Architecture de système de logiciel orientée vers l'objet
US5917901A (en) Telecommunications system
WO1998036583A1 (fr) Gestion d'interactions entre dispositifs dans des reseaux de telecommunications
WO1999065254A1 (fr) Systeme flexible d'acheminement d'appels
US20050163113A1 (en) Signaling point code sharing in exchanges
KR100325386B1 (ko) 넘버.세븐 신호망에서의 신호연결 제어부 메시지 루팅 방법
US6754327B1 (en) Standalone ACD system with native signaling system 7 capability
CA2218263C (fr) Architecture d'un systeme de telecommunications
JP3331947B2 (ja) ネットワーク通信システムおよびその制御用記憶媒体
EP1161826A1 (fr) Agencement du plan de numerotation pour un systeme de telecommunications extensible
KR100600327B1 (ko) 데이터베이스를 공유하는 복수의 서비스제어시스템에서부하분담 호처리시 중복출호 방지 및 장애처리 방법
KR100330179B1 (ko) 교환 시스템에서 출중계호에 대한 지능망 처리 방법
KR100350314B1 (ko) 넘버 세븐 신호망에서 신호 메시지 루팅 실패시의 처리 방법
US7277535B2 (en) Controlling connection processing
KR100205041B1 (ko) 논리적 지시자를 이용한 공통선신호망 링크세트 자원 제어 방법
KR100288062B1 (ko) 공통선 신호방식(Ｎｏ.7) 신호연결제어부(ＳＣＣＰ)의 자국 신호점 지정-해제 방법
JPH11501494A (ja) トラヒック管理制御用の中継点に接続されたサービス制御点の負荷分散グループ

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

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): DE ES FR GB IT NL SE

17Q First examination report despatched

Effective date: 20020325

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