JPH1023481A - Service providing system for intelligent network system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To improve productivity, maintenance and reliability of a system by easily connecting a new service substitution function (SSF) to its own service control function (SCF) without changing a program for the SCF. SOLUTION: When a domain conversion means (a domain conversion manager (DCM) 10 and drivers 6 to 8) for converting the communication protocols of respective SSFs into a single protocol is arranged between a service logic execution manager (SLEM) 11 in the SCF 1 and respective SSFs 2 to 5, the SLEM 11 can be designed as a common program not depending upon a specific SSF, the design of an SSF depending upon a specific SCF is made unnecessary and SSFs and SCFs for plural vendors can easily be connected. Since a message is converted by using a data base 9, message conversion can be executed only by rewriting the data base 9 without changing a program in the DCM 10 even at the time of changing or adding respective parameters included in messages or the like for respective SSFs.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a service providing system in an intelligent network system, and more particularly to a service switching function (hereinafter referred to as "SS") for a telephone exchange or the like.
F.) also provides a service providing method in an intelligent network system that realizes a service control function (hereinafter, also referred to as “SCF”) that does not depend on the service control function.

[0002]

2. Description of the Related Art Conventionally, in an intelligent network system of this kind, an ITU-T (International
l Telecommunication Union-Telecommunication Standa
RDization Sector, International Telecommunication Union-Telecommunication Standardization Sector)
INAP as application layer protocol between
Is defined, but because this definition is not very strict, similar but partially different messages and parameters are provided for each SSF vendor, and depending on the ITU-T Communication may be performed between the SSF and the SCF using a protocol that does not conform to the recommendation.

[0003]

In a conventional intelligent network system, a plurality of existing SSF vendors as described above, and even a new SSF vendor appearing after the system design of the SCF, is required to be compatible with the SCF. Since the service logic execution manager (hereinafter also referred to as “SLEM”) and the functional entity access manager (hereinafter also referred to as “FEAM”) are not designed, especially when providing an intelligent network system to a new market, multiple There is a problem that the connection between the SSF provided by the vendor and the SCF is difficult.

[0004] Accordingly, the present invention has been made in view of the above-described problems, and provides a service providing method in an intelligent network system that can easily connect a new SSF to its own SCF without changing the SCF program. The purpose is to provide.

[0005] According to the service providing method in the intelligent network system of the present invention, addition or modification of support messages of various SSF vendors can be performed without changing the SLEM program in the SCF, thereby improving system productivity and maintenance. Performance and reliability can be significantly improved.

[0006]

In order to achieve the above object, the present invention provides an intelligent network system including a service control function (SCF) and a plurality of service switching functions (SSF). ) Includes area conversion means (6, 7, 8 and 10 in FIG. 1) for absorbing a difference in communication protocol between a plurality of service switching functions (SSF) connected to the service control function (SCF). And providing a service providing method in an intelligent network system.

In the service providing method in the intelligent network system according to the present invention, the service control function (SCF) includes the service control function (SC).
F) different communication protocols of a plurality of service switching functions (SSF) connected to the service control function (SCF) and a service logic execution manager (SLE) in the service control function (SCF).
It is characterized in that a single protocol required by M) is mutually converted by driving a database.

As described above, according to the service providing system in the intelligent network system of the present invention, the service logic execution manager (SLEM) in the service control function (SCF) and the plurality of service switching functions (S) are provided.
Between the service logic execution manager (SLEM) and the specific service exchange by providing domain conversion means for converting different communication protocols of the plurality of service exchange functions (SSF) into a single protocol between the service logic execution manager (SLEM) and the service logic execution manager (SLEM). It becomes possible to design as a common program that does not depend on the function (SSF). Conversely, the service switching function (SSF) does not need to be designed depending on a specific service control function (SCF). The provided service switching function (SSF) and service control function (SCF) can be easily connected.

Further, according to the service providing method in the intelligent network system of the present invention, the message conversion is performed by driving the database using the database in which the message conversion rules are defined.
Even if there is an INAP message for each service exchange function (SSF) or a change or addition of each parameter included in the message, an area conversion manager (DC) which is an area conversion means.
M) can be dealt with only by rewriting the database without changing the program, and the change of the database can be generally easily performed as compared with the change of the program. Performance can be improved.

[0010]

Next, embodiments of the present invention will be described with reference to the drawings.

FIG. 1 is a block diagram showing a configuration of an embodiment of the present invention.

Referring to FIG. 1, the best mode of the present invention is a service control function (SCF) 1 and a plurality of service switching functions (SSF) 2, 3, connected to the SCF 1.
In an intelligent network system including 4, 5, ..., the SCF 1 is configured as follows. Although FIG. 1 shows that there are four or more SSFs, a case where two or more SSFs are connected to the SCF 1 is suitable as an embodiment of the present invention.

The SCF 1 is composed of the SSFs 2, 3, 4, 5,.
A function entity access manager (FEAM) 15 for exchanging messages 16 directly according to a protocol dependent on each SSF, a service logic execution manager (SLEM) 11 for exchanging messages according to a single protocol, and called from the SLEM 11. Service logic processing programs (SLP) 12, 13,
14, and so on. In FIG. 1, the SLP
Is shown as having three or more, but the presence of one or more SLPs is suitable as an embodiment of the present invention.

The FEAM 15 is provided for each of the SSFs 2, 3, 4,
5. Drivers that directly communicate with SSF
Communication drivers (hereinafter, simply referred to as “drivers”) 6, 7, 8 prepared according to the lower layer protocol below the presentation layer in the OSI hierarchical model of the OSI, and SSF2, 3 through the drivers 6, 7, 8 An area conversion manager (DCM) 10 for communicating with the application layer with 4, 5, ...,
And a database 9 for storing message conversion rules when the DCM 10 performs message conversion. Although FIG. 1 shows three drivers, one or more drivers are suitable as an embodiment of the present invention.

Here, the DCM 10 includes drivers 6, 7,
8 is normalized and passed to the SLEM 11 for each different SSF coming up from SSF.
For communication from the LEM 11 to the SSF, the driver 6 converts the normalized message according to the SSF,
Hand over to 7 and 8.

In FIG. 1, the DCM 10 and the database 9 are a part of the FEAM 15, but these are taken out of the FEAM 15 and the FEAM 15 and the SLE
You may make it arrange | position between M11.

Next, the operation of the embodiment of the present invention will be described.

First, an operation at the time of receiving a message according to the embodiment of the present invention will be described. FIG. 2 is a flowchart showing a flow of processing of the DCM 10 when receiving a message from the SSFs 2, 3, 4, 5,... Shown in FIG.

Referring to FIGS. 1 and 2, when a message is received from the drivers 6, 7, and 8, the DCM 10
Is the source SS included in the message to know from which SSF the message is
Information indicating F is acquired (step 201), and the message conversion rule corresponding to the source SSF is read from the database 9 using the acquired information indicating the source SSF as a key (step 202).

Thereafter, it is determined whether or not a call processing memory prepared for each call and used as a work area has been allocated to manage the call being processed by the SLEM 11 (step 203).

If it is determined that the call processing memory does not exist (NO in step 203), it is determined whether the received message is a calling message (step 20).
4) If it is a call message (YE at step 204)
S) The call processing memory is captured (step 205), and if it is not a call message (NO in step 204), the received message is discarded (step 207).

After the call processing memory is supplemented in step 205, the result of the acquisition of the call processing memory is checked (step 206). If the acquisition of the call processing memory fails due to lack of resources or the like (NO in step 206) ), The received message is discarded (step 207).

When the supplement of the call processing memory is successful (YES in step 206) or when it is determined in step 203 that the call processing memory exists (YES in step 203), it is included in the received message. Various parameters are normalized according to the message conversion rules read out in step 202 and stored in the call processing memory (step 208).

When the conversion of the message is completed, SLEM
Then, control is passed to 11 (step 209), and service execution is continued.

Next, an operation at the time of transmitting a message according to the embodiment of the present invention will be described. FIG. 3 is a flowchart showing the flow of processing of the DCM 10 when transmitting a message from the SCF 1 shown in FIG.

Referring to FIGS. 1 and 3, SLEM1
When the DCM 10 receives the message from the client 1, the DCM 10 obtains information indicating the destination SSF of the message (step 301), and uses the obtained information indicating the destination SSF as a key to store a message conversion rule for the destination SSF in the database 9. (Step 302).

Thereafter, the transmission message is transmitted to step 302.
Destination SSF according to the message conversion rule read in
(Step 303), and designates the destination SSF address and sends it to the drivers 6, 7, and 8 (Step 304).

[0028]

Next, in order to more specifically describe the above-described embodiment of the present invention, an embodiment of the present invention will be described in detail with reference to the drawings.

FIG. 4 is a block diagram showing the configuration of one embodiment of the present invention.

Referring to FIG. 4, one embodiment of the present invention is:
SCF401 and No. 7 SSF402 connected by the common line signal system and TCP
/ SSF403, 404 connected by IP protocol
And The application layer protocol between each of the SSFs 402, 403, 404 and the SCF 401 is defined in ITU-T Recommendation Q.3. It complies with the 1218 INAP, but each SSF has its own extensions or restrictions.

The SCF 401 is No. 1 as a lower layer protocol. No. 7 and TCP / IP, the No. 7 common line signal driver 405 and the TCP / IP driver 40 so that the respective protocols can be handled.
6 are prepared.

Drivers 405, 406 and DCM 40
7 operate as individual processes, and communicate with each other. The inter-process communication message includes the abstract syntax notation 1 of the ITU-T recommendation.
According to (ASN.1), DCM407 and each SSF40
2, 403, and 404, the format of the INAP message transmitted and received is converted.

Further, the DCM 407 is provided in the database 40.
SLAP of the INAP message normalized by referring to FIG.
409 as an inter-process communication message.

FIG. 5 shows the database 408 shown in FIG.
Is schematically shown. As shown in FIG. 5, the message conversion rule database 408 includes a domain management table 501, a domain message correspondence table 502, a domain parameter correspondence table 503, and a parameter conversion rule table 504.

The domain management table 501 includes address information of the SSF included in the lower layer protocol between the drivers 405 and 406 and each SSF, that is, a point code (PC) and a subsystem number (SSN), a TCP / IP in the No. 7 protocol. In the protocol, based on the IP address and TCP port number,
In the SCF 401, a domain number uniquely assigned to each SSF can be obtained.

The domain message correspondence table 502 indicates that SS
Conversion of the internal / external display of the message number can be performed for each F.

The domain parameter correspondence table 503 allows conversion of internal / external display of parameter numbers for each domain.

The parameter conversion rule table 504 can define rules for parameter conversion in the internal / external format.

Next, the operation of one embodiment of the present invention will be described.

First, referring to FIGS. 2, 4 and 5,
The operation of the DCM 407 when receiving a message from the SSF 402, 403, 404 will be described.

When a message is received from the driver 405 or 406, the DCM 407 determines which S
In order to know whether the message is from the SF, a message protocol and information included in the lower layer protocol (for the No. 7 protocol, the point code (PC) and the subsystem number (SSN) of the transmission source, T
IP address and TC for CP / IP protocol
P port number) and the domain management table 5 based on the
01 and obtain a domain number (step 20).
1). Subsequently, using the obtained domain number as a key, the domain message correspondence table 502, the domain parameter correspondence table 503, and the parameter conversion rule table 504 defining the message conversion rules are stored in the database 408.
Is read out (step 202).

Thereafter, it is determined whether or not a call processing memory prepared as a work area for each call and allocated as a work area is allocated to manage the call being processed by the SLEM 409 (step 203).

If it is determined that the call processing memory does not exist (NO in step 203), it is determined whether the received message is a calling message (step 20).
4) If it is a call message (YE at step 204)
S) The call processing memory is captured (step 205), and if it is not a call message (NO in step 204), the received message is discarded (step 207).

After the call processing memory is supplemented in step 205, the result of capturing the call processing memory is checked (step 206). If the acquisition of the call processing memory fails due to lack of resources, etc. (NO in step 206) ), The received message is discarded (step 207).

If the call processing memory is successfully acquired (YES in step 206) or if it is determined in step 203 that the call processing memory exists (YES in step 203), the domain determined in step 201 Store the number in the call processing memory. Then, the message number included in the received message is read out in step 202 in the domain message correspondence table 5
02 is converted to a system internal message number. Subsequently, similarly, each parameter number included in the received message is converted into an internal parameter number based on the domain parameter correspondence table 503 read in step 202. In addition, the contents of each parameter are
2 is normalized based on the message conversion rule table 504 read out and stored in the call processing memory (step 20).
8).

When the message conversion is completed, control is passed to SLEM 409 using the received message number and the pointer to the call processing memory as parameters (step 20).
9) Continue service execution.

Next, referring to FIG. 3, FIG. 4 and FIG.
The operation of the DCM 407 when transmitting a message from the SCF 401 will be described.

Upon receiving the message from SLEM 409, DCM 407 reads the domain number stored in the call processing memory (step 301). Then, using the obtained domain number as a key, a domain message correspondence table 502 in which a message conversion rule is defined,
The domain parameter correspondence table 503 and the parameter conversion rule table 504 are read from the database 408 (step 302).

Thereafter, regarding the transmission message, the domain message correspondence table 502 read out in step 302
To the message number for the destination SSF, the domain parameter correspondence table 503 to the internal parameter number for the destination SSF, and the parameter conversion rule table 504 for the parameter itself for the destination SSF. Edit (step 303). Then, the domain management table 501 is converted into a destination SSF address and a protocol by indexing using the domain number as a key, and transmitted to the corresponding driver 405 or 406 for each protocol (step 304).

In the above-described embodiments and examples, when a message is transmitted or received, step 202 or 30 is performed.
Accessed the database in which message conversion rules were defined in step 2.
The same effect can be obtained by reading the tables from the database all at once when the M407 is initialized and configuring the conversion rule table in the internal memory of the DCM 407.

[0051]

As described above, according to the present invention,
Since the service control function (SCF) is provided with an area conversion means for absorbing a difference in communication protocol between the plurality of service switching functions (SSF), the service switching function (SSF) provided by a plurality of vendors and the service are provided. Connection with the control function (SCF) can be easily performed.

Further, according to the present invention, since the conversion of the communication protocol is performed by driving the database, the change of the message between the service switching function (SSF) and the service control function (SCF) for changing the service is performed. Can be easily handled without changing the program of the service control function (SCF), and the system change can be speeded up and the reliability can be improved.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration of an embodiment of the present invention.

FIG. 2 is a flowchart illustrating an operation at the time of receiving a message according to the embodiment of the present invention.

FIG. 3 is a flowchart for explaining an operation at the time of transmitting a message according to the embodiment of the present invention.

FIG. 4 is a block diagram showing a configuration of one embodiment of the present invention.

FIG. 5 is a diagram schematically illustrating a configuration of a database according to an embodiment of the present invention.

[Explanation of symbols]

1. Service Control Function (SCF: Service Control Func)
Option) 2, 3, 4, 5, ... Service exchange function (SSF: Serv)
ice Switching Function) 6, 7, 8 Low layer protocol communication driver 9 Database 10 Domain conversion manager (DCM: Domain Conversio)
n Manager) 11 Service logic execution manager (SLEM: Servic)
e Logic Execution Manager) 12, 13, 14, ... Service Logic Program (SLP) 15 Functional Entity Access Manager (FEA)
M: Functional EntityAccess Manager) 16 Message 401 Service Control Function (SCF: Service Control)
Function) 402, 403, 404 Service exchange function (SSF:
Service Switching Function) 405 No. 7 common line signal driver 406 TCP / IP driver 407 Domain conversion manager (DCM: Domain Convers
ion Manager) 408 Database 409 Service Logic Execution Manager (SLEM: Serv)
ice Logic ExecutionManager) 410 Functional Entity Access Manager (FEA)
M: Functional Entity Access Manager) 501 Domain management table 502 Domain message correspondence table 503 Domain parameter correspondence table 504 Parameter conversion rule table

Claims (4)

[Claims] An intelligent network system including a service control function (SCF) and a plurality of service switching functions (SSF), wherein the service control function (SCF) is connected to a plurality of service control functions (SCF). A service providing method in an intelligent network system, comprising a domain conversion unit for absorbing a difference in a communication protocol between service switching functions (SSF). 2. The service control function (SCF) includes a plurality of service exchange functions (SSFs) connected to the service control function (SCF) and different communication protocols, and a service in the service control function (SCF). 2. A service providing method in an intelligent network system according to claim 1, wherein a single protocol requested by a logical execution manager (SLEM) is mutually converted by a database. 3. The method according to claim 1, wherein the area conversion means is provided in a functional entity access manager (FEAM) of the service control function (SCF).
Or a service provision method in the intelligent network system according to 2. 4. A service logic execution manager (SLE) of the service control function (SCF).
M) and the functional entity access manager (FEA)
3. The service providing method in the intelligent network system according to claim 1, wherein the service providing method is provided between the service provider and the service provider.