WO1996009729A1 - A method to structure call processing and a call processing switching system for telephony - Google Patents
A method to structure call processing and a call processing switching system for telephony Download PDFInfo
- Publication number
- WO1996009729A1 WO1996009729A1 PCT/SE1995/001027 SE9501027W WO9609729A1 WO 1996009729 A1 WO1996009729 A1 WO 1996009729A1 SE 9501027 W SE9501027 W SE 9501027W WO 9609729 A1 WO9609729 A1 WO 9609729A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- session
- record
- data
- call
- objects
- Prior art date
Links
Classifications
-
- 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/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/54508—Configuration, initialisation
- H04Q3/54525—Features introduction
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13057—Object-oriented software
Definitions
- the present invention refers to a data structure for call processing and particularly to a data structuring in a traffic controlling process for a telecommunication application.
- EP-0 470 415 A2 describes a method to supply a number of application processors in a telephony system access to call related information in a common database.
- the information is tagged and stored temporarily as a record m the database as long as the communication lasts.
- the information is particularly directed for being directly viewed on a display terminal for supervision in an operator controlled switching system.
- a first object according to the present invention is to combine the hal -call principle with a generic protocol between the executing half-calls and including a session comprising a session scope and a traffic case scope which are using memory functions m which different records are storing pointers to a local memory function, the pointers being combined with a tag element by means of which locally stored data will be uniquely identified and in spite of not being real global data may still be utilized as global data during the duration of a specific session in which period the particular records exist.
- a second object according to the present invention is that the specific session scope is using a session record for storing pointers to executing objects of the call and from which record it will be possible to find all other objects within the session, if the tag elements under which the objects are stored are known, other data objects being stored in a transaction record refer ⁇ enced session record or of a traffic case record.
- a third object according to the present invention is that the traffic case scope is having a similar structure as the session scope and the traffic case record being referenced from the session record and the traffic case record being created to store executing objects of a call.
- a fourth object according to the present invention is that the transaction record is storing data objects belonging to the traffic case.
- a fifth object according to the present invention is that the tag element is being realized by an integer number uniquely assigned to each executing object or data object being stored.
- Figure 1 is an illustration of a session having a session controller, SC, handling several traffic cases including for each traffic case a respective originating call, OC, in communication with other traffic cases including a respective terminating call, TC;
- SC session controller
- Figure 2 demonstrates a session controller, SC, using, according to the method and system of the present invention, a session record to store references to executing objects and a transaction record to store references to data objects
- Figure 3 demonstrates collections according to the method and system of the present invention to store a traffic case object within an originating call, OC;
- Figure 4 is an demonstration of objects controlling the data flow in a session
- Figure 5 demonstrates an example when data for a charging basis is extracted from a session
- Figure 6 shows in a simple example the relation between created managed objects
- Figure 7 shows the complete static view according to the simple example of Fig. 6 ,-
- Figure 8 is a simple flow chart of call data collection in a Transaction Record during call processing.
- Figure 9 is a simple flow chart of specification of data to include in an output .
- a common way to structure software in a call processing switching system for telephony is to divide the control of the call into two halves, a Half-Call A and a Half-Call B.
- the software which controls a Half-Call is executing in a process called a Session.
- a session can handle one or several Traffic Cases simultaneously (for example in a multi call situation) .
- the Traffic Case defines the functionality and data that handles a call in a Session. Note also that a three party call is handled by two Traffic Cases in a Session, one for each call leg.
- the Session Scope is controlled by the Baseiiow Session Controller, SC.
- the main task for the session controller is to act as a command interpreter against the Access Protocol , ACP and make a service analysis on these commands (Messages) . This includes then, for instance, initiating and terminating new Traffic Cases, distributing information from the Access Protocol to the correct Traffic Case, initiating new services, etc.
- Every Traffic Case within the Session is controlled by one baseflow.
- a baseflow may be either an Originating Call, OC or a Terminating Call, TC.
- the main task for this baseflow is to take care of the basic call handling. This includes for example establishing/disconnecting a call (including handling of the Telecommunication Service Protocol. TSP, between the call halves) , ordering establishment/disconnection of connections (for example a speech connection) , and ordering address information analysis, etc.
- An Executing Object * ⁇ 11 execute in the session, e. g., control objects, protocol c ⁇ cts, re s ource obj -cts etc.
- a pure Data Object will contain recei -d for example from a Teleservice Protocol Message. It shall also be possible to make an output of this type of data for charging or statistic purposes.
- the two types >f Objects have different semantics and are stored in different records in the Session. Such a record is referred to a: a Session Record and is used to store pointers to protocol objects and resource objects instantiated by control and resource objects within the Session.
- the Objects stored in a Session Record are common for the whole Session.
- a Transaction Record For storing pure Data Objects is used a Transaction Record.
- the Transaction Record also named call record
- the Transaction Record is used to store pointers to pure Data Objects instantiated by control, protocol, and resource objects within the Session or a Traffic Case executing in the Session.
- a users view of a Session Record is referred to a Session Record View and gives the user an interface to the Session Record on a high abstraction level .
- a users view of a Transaction Record is referred to as the Transaction Record View and gives the user an interface to the Transaction Record on a high abstraction level.
- Traffic Case Record is a record where pointers to Objects belonging to a Traffic Case are stored. Only pointers to Protocol Objects and Resource Objects are stored in this record. For storing pure Data Objects a Transaction Record should be used.
- a users view of a Traffic Case Record is referred to a Traffic Case Record View and gives the user an interface to the Session Record on a high abstraction level .
- Figure 1 is a generalized view of a session scope, which is controlled by the session controller SC.
- the session controller is acting as a command interpreter against the access protocol ACP, which is the generic term used for the subscriber or network accesses.
- ACP access protocol
- the session contains one or several traffic cases, and here the particular session contains two traffic cases which are both of the OC type (originating call) .
- Each one of the two traffic cases of type OC is established by means of the respective traffic case to another traffic case of type TC (terminating call) through a handling telecommunication service protocol, TSP.
- a session record which shall be used for storing a pointer, PTR, to each executing object, for example to a so called session agent.
- the session record, SR is by means of other pointers the root for the data structure in each session.
- the data objects of the whole session is found in the transaction record by means of their respective pointers, PTR.
- Each entry in the session record is having a particular name or key, TAG, which makes it possible to locate any object within the session scope if the particular system operator knows the particular name or TAG.
- FIG. 3 is a generalized view of a traffic case scope, here containing an originating call type, OC, but a terminating call type, TC, would have the corresponding structure.
- This scope has to be introduced if the application has a need to execute an arbitrary number of parallel traffic cases in the session.
- the structure of the traffic case scope is thus similar to that of the session scope.
- For each traffic case in a session there is created a traffic case record to store executing objects. Like in the session record is used a name or TAG and a pointer PTR.
- the traffic case record is accordingly referenced from the session record.
- To store data objects belonging to the traffic case is consequently used a transaction record, TR, creating a table for the data objects at this traffic case level.
- Every user of a session or traffic case record has an own view object through which the stored executing objects or data objects may be accessed.
- Figure 4 demonstrates in greater detail the data flow through a session executing an originating call, OC.
- the data flow starts when some data is received by an access agent or the input agent .
- the received data is converted to an AXE internal representation.
- the converted data is then stored in the transaction record, TR.
- TR The data object is stored with a tag.
- the tag is an integer that is reserved for this particular data object.
- Other users e.g. an Application Analysis, needing the data object can fetch it from the transaction record by means of the tag and by utilizing a transaction record view object, TR_View.
- TR_View a transaction record view object
- the above example also illustrates when data is sent by the output agent to the other Half-Call via the telecommunication service protocol, TSP. Data is sent in a parameter which besides the data contains the tag which identifies it.
- a data object is stored in the transaction record (a synonym for transaction record is also call record) .
- the transaction record, TR is as already stated always accessed via a view object.
- the view object gives the user a high level interface to TR, which will be further described below.
- Each data object that is stored in the transaction record is semantically identified by a name or key referred to as the TAG.
- the TAG is an integer, in an exemplifying embodiment a 16 bit word, which has been reserved for one particular data object.
- the view object has two main tasks. The first is to present a customized interface towards the TR. Each user of the TR should have a dedicated interface to the contents in the TR. The second task is to act as a handle object towards the TR, the handle ensures that TR is not removed until all handles are deleted.
- View objects are also used to access the contents of the other two types of record that exist, the session record and the traffic case record.
- one task of the view object is to provide the user with a customized interface on a high abstraction level towards a record.
- the customizing means that the interface gives the users access only to the objects needed to be accessed, which may be only a part of the total contents in a record.
- the second major task of the view objects towards the transaction record and the traffic case record is that they act a handles. As long as a record has a handle it can not be deleted. When the last handle towards a record is removed the record and all its content is also removed from the local memory storage. It is apparent that this creates a very convenient local memory storage managemen .
- the call record output mechanism already mentioned is used to output parts of the content of a transaction record for post ⁇ processing. It should be kept in mind that the contents of the session record and a traffic case record and a transaction record are existent only during the duration of that particular session and will disappear when the session is terminated.
- the output mechanism is built around a number of managed objects containing tag lists. In the operation of a telecommunication system there is for instance a need to collect charging data to be able to correctly bill the different subscribers.
- Figure 5 is exemplified what may take place in a session.
- a control object "Charging" has opened an object Cro_Type. This particular Cro_Type object contains a Tag list, fetched from the data base, denoting the data objects to be extracted from the transaction record.
- Cro_Type is then ordered to compile a report consisting of the data objects identified by the tag list which is stored in the data base.
- the control object then uses the Cro_Type interface to order it to collect the data during the existence of the particular session.
- the data may be packed in a data area which then will be sent to a post-processing node. Consequently a charging basis due to increased services may be changed at any moment by simple modification of the tag list without interfering at all with the existing system having a structure according to the present invention.
- the effective result of this is that even if the contents of the different sessions are defined as local data, it is possible to simultaneously make use of desired parts of the content as if it constitutes global data.
- a difference between local and global data is for example that the latter by necessity has normally to be allocated in predetermined memory locations to be able to be accessed by other users.
- CroServiceTemplate contains one attribute, possible TAGs, denoting which data is possible to extract from the transaction record, TR, for a particular service, for example in this context a "Basic Call” or a "Three Party Call”.
- the second managed object type is CroType, which is used for specification of a certain output type. Every instance of CroType is connected to one or more instances of CroServiceTemplate. The union f data in these CroServiceTemplates determines what data is possible to output for a speci ic CroType.
- the third and last management object type is CroCustomerTemplate, which is a managed object holding the information of which data to extract for a specific customer in a specific output type, CroTy .
- Figure 6 demonstrates a small example having the conditions:
- CroType 1 CroType 2
- CroServiceTemplate Basic Call containing the Tags 1, 2, 5 and 8.
- CroType 1 designed such that it will be able to output data related to both services
- CroType 2 designed such that it will be able to output data related to the Basic Call.
- Figure 6 is visualized the basic structure and the relation between the created managed object.
- CroCust ⁇ merTemplate is required for each customer and CroType to make the output mechanism "Call Record Output", CRO, able to perform outputs of all CroTypes to all customers.
- CRO All Record Output
- Figure 7 is demonstrated the resulting structure.
- Customer A requires all possible Tags from CroType 1 and Tag no. 1 and 2 from CroType 2 and customer B requires all Tags with lower number than 8 from all CroTypes.
- a final part of the data flow in Figure 4 describes when the data shall be sent to the other Half-Call.
- the Half-Calls communicate by means of the Telecommunication Service Protocol, TSP.
- TSP carries self-identifying parameters.
- a parameter contains a data object and is identified by a Tag.
- the receiver can determine what data is received by looking at the Tag.
- the Tag which is used to identify a parameter on the TSP is the same Tag used to identify a data stored in TR.
- FIG 8 is summarized by a number of steps in a simple flow chart of a call data collection in a Transaction Record during call processing.
- a processing is started in a step 100.
- a message is received over an external protocol. It is received in a protocol agent within a dynamic process within the system.
- the data is converted from an externa representation to an internal representation.
- a Data Object is created within this dynamic process. This Data Object then contains the internal representa ⁇ tion of the received data.
- the Data Object is stored under a unique tag element in a transaction record.
- During call processing data is fetched in a fourth step 104 from the transaction record using a transaction record view object then utilizing the tag element to get the correct pointer PTR to retrieve the specified data.
- the function call record output is called in a fifth step 105.
- This function accesses the database to find out which data to output. As a result the function gets a list of tag elements.
- the wanted data is collected from TR in step 104 and put into an output buffer. This buffer may then be output to an external media. The data may later be post-processed in order to for instance produce billing information etc.
- FIG. 9 is shown by means of three steps a simple flow chart a specification of data to be included in an output.
- the procedure starts in a step 200.
- the service provider or any other operator administrating the system decides which data to output for different call types.
- These different output types are specified in a second step 202 by filling in templates with lists of tags to output.
- these templates are stored in the database by for example entering the list of tags by means of a separate terminal and/or a keyboard. These entered list of tags are later accessed during the call processing.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Exchange Systems With Centralized Control (AREA)
- Telephonic Communication Services (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Computer And Data Communications (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP8510794A JPH10505983A (ja) | 1994-09-19 | 1995-09-12 | 呼出し処理を構成する方法および電話システム用呼出し処理交換システム |
AU35802/95A AU691667B2 (en) | 1994-09-19 | 1995-09-12 | A method to structure call processing and a call processing switching system for telephony |
MX9701999A MX9701999A (es) | 1994-09-19 | 1995-09-12 | Un metodo para estructurar el procesamiento de llamadas y un sistema de conmutacion de procesamientode llamadas para telefonia. |
EP95932985A EP0782811A1 (en) | 1994-09-19 | 1995-09-12 | A method to structure call processing and a call processing switching system for telephony |
NO971162A NO971162L (no) | 1994-09-19 | 1997-03-13 | Fremgangsmåte for å strukturere anropsprosessering i et telesystem |
FI971143A FI971143A (fi) | 1994-09-19 | 1997-03-18 | Menetelmä puhelunkäsittelyn struktuoimiseksi ja puhelunkäsittelykeskusjärjestelmä puhelinliikennettä varten |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
SE9403130-9 | 1994-09-19 | ||
SE9403130A SE503394C2 (sv) | 1994-09-19 | 1994-09-19 | Förfarande för att strukturera anropsbearbetning samt växelsystem för telefoni med koppelbearbetning |
Publications (1)
Publication Number | Publication Date |
---|---|
WO1996009729A1 true WO1996009729A1 (en) | 1996-03-28 |
Family
ID=20395285
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/SE1995/001027 WO1996009729A1 (en) | 1994-09-19 | 1995-09-12 | A method to structure call processing and a call processing switching system for telephony |
Country Status (11)
Country | Link |
---|---|
EP (1) | EP0782811A1 (ko) |
JP (1) | JPH10505983A (ko) |
KR (1) | KR100364217B1 (ko) |
CN (1) | CN1082320C (ko) |
AU (1) | AU691667B2 (ko) |
CA (1) | CA2197983A1 (ko) |
FI (1) | FI971143A (ko) |
MX (1) | MX9701999A (ko) |
NO (1) | NO971162L (ko) |
SE (1) | SE503394C2 (ko) |
WO (1) | WO1996009729A1 (ko) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0470415A2 (en) * | 1990-08-09 | 1992-02-12 | Siemens Rolm Communications Inc. (a Delaware corp.) | Call tagging user information in a telephonic environment |
EP0524089A1 (fr) * | 1991-07-16 | 1993-01-20 | Alcatel N.V. | Structure de logiciel pour système de traitement de données, notamment pour système de télécommunications |
EP0524077A1 (fr) * | 1991-07-16 | 1993-01-20 | Alcatel N.V. | Structure de logiciel pour système de traitement d'informations |
US5218632A (en) * | 1991-10-16 | 1993-06-08 | Telefonaktiebolaget L M Ericsson | Flexible call detail recording system |
-
1994
- 1994-09-19 SE SE9403130A patent/SE503394C2/sv not_active IP Right Cessation
-
1995
- 1995-09-12 KR KR1019970701705A patent/KR100364217B1/ko not_active IP Right Cessation
- 1995-09-12 AU AU35802/95A patent/AU691667B2/en not_active Ceased
- 1995-09-12 CA CA 2197983 patent/CA2197983A1/en not_active Abandoned
- 1995-09-12 JP JP8510794A patent/JPH10505983A/ja active Pending
- 1995-09-12 EP EP95932985A patent/EP0782811A1/en not_active Withdrawn
- 1995-09-12 CN CN95195156A patent/CN1082320C/zh not_active Expired - Fee Related
- 1995-09-12 WO PCT/SE1995/001027 patent/WO1996009729A1/en not_active Application Discontinuation
- 1995-09-12 MX MX9701999A patent/MX9701999A/es not_active Application Discontinuation
-
1997
- 1997-03-13 NO NO971162A patent/NO971162L/no not_active Application Discontinuation
- 1997-03-18 FI FI971143A patent/FI971143A/fi unknown
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0470415A2 (en) * | 1990-08-09 | 1992-02-12 | Siemens Rolm Communications Inc. (a Delaware corp.) | Call tagging user information in a telephonic environment |
EP0524089A1 (fr) * | 1991-07-16 | 1993-01-20 | Alcatel N.V. | Structure de logiciel pour système de traitement de données, notamment pour système de télécommunications |
EP0524077A1 (fr) * | 1991-07-16 | 1993-01-20 | Alcatel N.V. | Structure de logiciel pour système de traitement d'informations |
US5218632A (en) * | 1991-10-16 | 1993-06-08 | Telefonaktiebolaget L M Ericsson | Flexible call detail recording system |
Also Published As
Publication number | Publication date |
---|---|
CN1158205A (zh) | 1997-08-27 |
CA2197983A1 (en) | 1996-03-28 |
KR100364217B1 (ko) | 2003-02-11 |
EP0782811A1 (en) | 1997-07-09 |
JPH10505983A (ja) | 1998-06-09 |
NO971162L (no) | 1997-05-15 |
SE503394C2 (sv) | 1996-06-03 |
FI971143A (fi) | 1997-05-19 |
CN1082320C (zh) | 2002-04-03 |
AU3580295A (en) | 1996-04-09 |
MX9701999A (es) | 1997-06-28 |
SE9403130D0 (sv) | 1994-09-19 |
AU691667B2 (en) | 1998-05-21 |
NO971162D0 (no) | 1997-03-13 |
SE9403130L (sv) | 1996-03-20 |
FI971143A0 (fi) | 1997-03-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US5579384A (en) | Telecommunications network service central management system interfacing with protocol specific regional stations providing services to subscribers | |
JPH0497645A (ja) | インテリジェントネットワークにおけるscpのサービス制御方式 | |
WO1994000945A1 (en) | Call distributor | |
AU4637000A (en) | Telecommunications network resource handling arrangement and method | |
KR100343342B1 (ko) | 일군의데이터로부터의데이터추출방법및장치 | |
US5365581A (en) | Telephonic switching system with automatic port assignment capability and method | |
JPH05204853A (ja) | データ処理システム、特に電気通信システム用ソフトウェア構造 | |
AU691341B2 (en) | A flexible call record mechanism | |
AU691667B2 (en) | A method to structure call processing and a call processing switching system for telephony | |
EP0873029A1 (en) | An SCP interface | |
AU691974B2 (en) | Simplified multi-call processing | |
US6282202B1 (en) | Method for internal communication in a telecommunications system | |
US6151317A (en) | Control type or service independent building block | |
Capellmann et al. | Using high-level Petri nets in the field of intelligent networks | |
CA2200177A1 (en) | A flexible call record mechanism | |
MXPA97002003A (en) | A flexi call registration mechanism | |
MXPA97001999A (en) | A method for structuring the processing of calls and a transmission system of processing calls for telefo | |
JPH03250335A (ja) | サービスプロセス間データ対応管理方式 | |
JPS6362497A (ja) | 加入者デ−タ管理方式 | |
JPH09244938A (ja) | データベース管理システム | |
GB2341953A (en) | Communication between two computer programs via a generic interface | |
JP2001077810A (ja) | 通信ネットワークにおける付加サービス提供システム |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 95195156.4 Country of ref document: CN |
|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AU CA CN FI JP KR MX NO |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): AT BE CH DE DK ES FR GB GR IE IT LU MC NL PT SE |
|
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 1995932985 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2197983 Country of ref document: CA |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1019970701705 Country of ref document: KR |
|
WWE | Wipo information: entry into national phase |
Ref document number: PA/a/1997/001999 Country of ref document: MX |
|
WWE | Wipo information: entry into national phase |
Ref document number: 971143 Country of ref document: FI |
|
WWP | Wipo information: published in national office |
Ref document number: 1995932985 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 1019970701705 Country of ref document: KR |
|
WWG | Wipo information: grant in national office |
Ref document number: 1019970701705 Country of ref document: KR |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: 1995932985 Country of ref document: EP |