SE516244C2 - Internet SS7 gateway - Google Patents

Abstract

The present invention relates to a device between a unit connected to the Internet and a node in an intelligent network, where the device is provided with means for converting a signal from the node in the intelligent network into a compatible signal for the unit coupled to the Internet and vice versa. The invention also comprises a method for connecting an information server to a node in an intelligent network via the Internet.

Description

20 25 30 516 244 2 via MML signaling (Man-Machine Language) A serious disadvantage of this type of connection is that it is slow and that MML signaling cannot be used to utilize a variety of standard services implemented in the SCP.

DESCRIPTION OF THE INVENTION In recent times. end users have gained increasing influence that This means that they control IN services. end users create a need for this control to take place as quickly and user-friendly as possible. With known technology this is not satisfied which is a problem. The object of the present invention is thus to solve the above-mentioned problems by connecting a World Wide Web, WWW, to a Service Control Point, SCP, an intelligent network by using SS7 signaling, more specifically Intelligent Network Application Protocol, INAP.

The WWW device to which a user can 'be connected' via, for example, a personal computer is in turn connected to the SCP in the intelligent network via a so-called Internet SS7 Gateway.

This Gateway enables the user to connect to a network node via, for example, the Internet / WWW.

The gateway. communicates with SCP'N 'over SS7 links genonl to use INAP. The connection to the Internet is made via Transmission Control Protocol / Internet Protocol, TCP / IP, by using a suitable protocol such as X.25 or Ethernet. The Internet SS7 Gateway emulates a Service Switching Point, SSP, or a Service Data Point, SDP, into a Service Control Point (SCP). The gateway supports the same INAP functionality as a man »now 10 15 20 25 516 244 3 normal SCP / SDP. As the Internet SS7 Gateway acts as a Service Switching Point, SSP takes advantage of the INAP operations that enable the user to change / update their parameters in the IN services. As it functions as an SDP, it uses a so-called Update / retrieve function to update the parameters in the IN services.

The object of the present invention is to make it possible through a so-called Internet SS7 Gateway to communicate with the SCP in an intelligent network from a WWW device via INAP.

An advantage of the present invention is that through direct contact between a WWW unit and the SCP. in the intelligent network via SS7 links fast execution is obtained.

Another advantage of the present invention is that the same interface as with Dual Ione Multi DTMF-Erequency, signaling to the SCP is used, which means that all predefined services controlled by DTMF signaling can be used.

A further advantage of the present invention is that services can be triggered from the WWW unit.

The invention will now be described in more detail by means of preferred embodiments and with reference to the accompanying drawings.

DESCRIPTION OF THE FIGURES Figure 1 shows a network topology in which the invention is implemented. 10 15 20 25 516 244 4 Figure 2 shows an internal structure in the SS7 link and in the Internet link.

Figure 3 shows the first part of a flow chart that step by step indicates how a client can connect to a node in an intelligent network via the Internet.

Figure 4 shows a first embodiment of the continuation of the flow chart in Figure 3.

Figure 5 shows a second embodiment of the continuation of the flow chart in Figure 3.

Figure 6 shows a third embodiment of the continuation of the flow chart in Figure 3.

Figure 7 shows a fourth embodiment of the continuation of the flow chart in Figure 3.

PREFERRED EMBODIMENTS In Figure 1 we see an example of a network topology in which the invention is implemented. A user is connected to the internet via the WWW browser shown in the figure.

The user can also connect to the internet via another standalone application with corresponding features.

The application can be written. in the programming language C, Java, Smalltalk, Basic or any other programming language. Between the Service Control Point, SCP, and the Internet, there is an inventive Internet SS7 Gateway; The purpose of the Internet SS7 Gateway is to convert the programming language from the Internet into a language that SCP can handle and vice versa.

In Figure 1, four logical entities can be identified. A first entity includes the client, such as a WWW browser. A second entity corresponding function. A third entity includes the inventive Internet SS7 Gateway which may also be called the Inter Working Unit, IWU. Entities two and three can, as this figure shows, be arranged in the same physical machine but can also be arranged in separate physical machines. A fourth and final entity includes a node in the intelligent network, for example the SCP.

Between the above-mentioned entities there are arranged three interfaces, hereinafter referred to as II, I2, I3 calculated from the WWW client. The client initially uses Hyper Text Transfer Protocol, HTTP, to retrieve an access page on the server.

The page can then be manipulated, for example by entering a user ID and a password. Now either HTTP or Common Gateway Interface, CGI, can be used depending on how the server side is implemented. As a return on the User ID and password, a page or a number of Java classes can be sent to the client via HTTP. None of the dialogue so far interferes with the IWU but only interface II is affected.

At interface I2, an interface protocol is included between the inventive IWU and the server. The communication between the IWU and the user application, for example the WWW, includes messages of, for example, the Socket socket type. communication is a process-to-process communication at a higher level of abstraction. When a message is sent to the WWW, the structure of the message is converted into strings of characters. The message parameters included in are separated in an appropriate way, \\ l II for example with so-called characters in the programming language C. The WWW application, or any other application with a corresponding function includes the WWW server or a device with. 10 15 20 25 30 516 244 6 connected between the IWU and the client, can use the same structure on the internal messages as the IWU, but it is not forced to do so.

The IWU is closely linked to the application it is intended to serve. A message can include, for example, instructions on which message transmission should start, how the message should be sent and how many characters should be received. The message may also include information on how to receive the characters. This information passes the I2 interface, that is, between the WWW server and the IWU.

In the IWU, there may be a number of predefined messages that the IWU can receive from the SCP. to Incoming messages The IWU is checked to see if they belong to the predefined messages. In the predefined messages, the value of most parameters is determined.

An incoming message is considered accepted as its parameters correspond to the parameters in the predefined message. The incoming message is then considered as an internal message type message and the remaining parameters are used for this' conversation.

When applications of WWW type are used, there is the possibility to implement internal functions. To save bandwidth and to increase performance, the WWW application can ask the client for both PUI and PIN at the same time and then send these to the IWU together and simultaneously. The IWU will in turn first send the PUI to the SCP, then wait for a message from the SCP regarding the PIN, then the IWU will send the PIN code to the SCP and then the IWU will receive a message from the SCP ' As for the PIN code, the IWU sends a message to the WWW application. 10 15 20 25 30 516 244 '7 The same structure is used in the management of the services. WWW application. has knowledge of 'what information is required to, for example, change the PIN code. The WWW application collects the required information and sends it to the IWU, which in turn processes the information and completes the operation.

A typical example of the WWW application's functionality is that when sending a new PIN code, ie when changing it, the PIN code does not need to be sent twice to the IWU to verify the code. The verification that the PIN code is correctly entered can just as easily be done in the WWW application. Thus, the number of communications can be greatly reduced between the two parties.

In each dialogue where the IWU is involved, the state of the dialogue is analyzed. The permit is in most cases the most recent message sent from the IWU and is used to check if an incoming message is acceptable. When a message is received, its condition is checked. For most states, only a specific message is from the WWW application. or the SCP. acceptable. This has to do with the fact that after the initiation of the dialogue between the SCP and the WWW, the WWW application only answers special questions.

By checking that the correct message is obtained, we avoid errors and complicate for unauthorized users to infringe.

The IWU can use time slots to handle messages partly from the SCP and partly from the WWW application.

The IWU checks for messages from the SCP during a given time interval. If there are messages in the queue, these will be processed. Then the IWU checks for messages from 10 15 20 25 516 244 8 WWW application during a given time interval. If there are messages in the queue, these are processed. This is a simple but definitely not an optimal solution.

The IWU can also check messages partly from the SCP and partly from the WWW application at the same time. This can be done by having an operating system, for example UNIX, with associated hardware, built-in functions that allow the IWU to work with both queues at the same time. One way is to use a function in UNIX called the socket. This function allows the IWU function to simultaneously wait for messages from both the IN node and the information server.

In figure 2 we see an internal architecture, in which the SS7 signal and the signal from the internet are shown. The different types of SS7 signals are well known to a person skilled in the art and should not be described in more detail.

The various protocols included in the connection between the Internet and an application connected to it should also not need to be described in more detail, as it is also well known to a person skilled in the art.

The Internet SS7 Gateway can be said to function as a bridge or link between the SCP and a WWW-like application connected to the Internet.

In Figure 3, we see a first part of a flow chart that indicates how a user arranged with, for example, a computer can conceivably connect to an SCP in an intelligent network via the Internet.

Initially, a client may use, for example, HTTP to request an access page on an information server to an IN node. The server can be, for example, a WWW server. The server may be connected to the internet.

In the next step, the information server sends the authorization formalities to the client, which may include questions about the client's user identity and Pass Word.

In the next step, the client enters his user identity and associated password which is sent to the information server.

Here there are at least two different ways to choose from, then this information must be sent to the information server.

A first way is to use HTTP and a second way is to use the Common Gateway Interface, CGI.

Common Gateway Interface is a de facto standard for so-called gateway programs to interface with information servers such as the WWW. This standard is of course well known to a person skilled in the art and should therefore not need to be commented on further.

In the next step, the information server checks the password and user identity. If the user identity and password match, the client will have access to the requested application, otherwise the client will of course not have access, after which the client can be given a number of new attempts to access the application.

In the event that the above process has taken place and that the client is authorized, the next step follows. In this step, the information server sends a menu of various operations that can be performed in the application.

In the next step, the client selects one of the available operations. At this stage, a communication is started between the client on one side and the IN> node on the other side via the previously mentioned IWU. Here are a number of different possible alternatives for how this communication is set up in practice.

The IWU may be a separate physical device or included in the information server. Assuming that the information server and the IWU are arranged together, there are at least the following three options.

In a first alternative, one can imagine communicating via CGI from the client via the information server. This means that a so-called IWU binary reads an ordinary text string from the standard input that the information server provides it with. The IWU then returns messages to the client via the default information server. The protocol between output and via the information server and the IWU could thus be normal so-called file descriptors (stdin / stdout) implemented in UNIX.

This option is represented in Figure 4. In a first stage, the information server sends to the CGI input parameters the program, the above-mentioned stdin, stdout and the environment variables.

In the next step, the CGI program communicates with the IN node via SS7 implementation using socket communication.

In the next step, the CGI program returns the output parameters via the information server to the client, which in cases where the parameters are of value to the user is presented to him.

A second alternative could be that the client sets up a socket directly against the IWU (for example in the programming language Java and thus completely disconnects the server 10 15 20 25, The third 516 244 ll from the dialog) after the initial dialogue with the information the server. Thus, the protocol from the IWU against the client would be sockets. Another possibility would be to use standard Unix Remote Procedure Call, RPC, or some other machine-to-machine interface_ Regardless of which abstraction level is selected, TCP / IP or 'UDP / IP' is used as a so-called low-level protocol. X.25 may also be considered suitable as a protocol.

This option is represented in Figure 7. The IWU obtains input parameters from the client through any of the above-mentioned machine-to-machine protocols. In the next step, the IWU communicates with. SS7 implementation by using socket communication.

The output parameters are then returned from the IWU to the client, after which these parameters can be visualized at the client.

A third alternative is that the IWU process is included in an information server where the server's behavior is expanded with the IWU's behavior. The communication can then take place through direct internal process calls, ie direct communication between the IWU and the information server, by using the built-in functions of the selected platform to transfer information between two functions (processes) within the same machine. This communication then takes place at the so-called method call level or possibly wire communication depending on the design of the servers. the alternative is represented in Figure 6. In a first step, the information server sends input parameters to the IWU by using the above-mentioned communication at the method call level. Thereafter, the IWU communicates the part of the server 10 15 20 25 516 244 12 with the SS7 implementation by using socket communication. In the next step, the output parameters are returned from the IWU part of the server to the "core" server, which in turn sends these to the client. These can, as in the other cases, be made visible to the user if he or she has any benefit from it.

The information server and the IWU can be arranged in two separate machines or processes in the same nmskin. Figure 5 shows a flow chart for this embodiment. In a first step, the information server sends input parameters to the IWU using a process-to-process communication protocol or a machine-to-machine communication protocol. For example, RPC can be used as a protocol and for this, for example, TCP / IP, UDP / IP or X.25 can be used as a carrier of the protocol.

The IWU then communicates with the SS7 implementation by using, for example, socket communication or some other corresponding process-to-process communication.

The SS7 implementation then returns the output parameters to the IWU, which in turn, after processing, sends these to the information server. Then the output parameters are passed on to the client. The output parameters can then be visualized for the user. This option is shown in Figure 6.

The invention is of course not limited to the embodiments described above and shown in the drawing, but can be modified within the scope of the appended claims.

Claims (15)

10 15 20 25 516 244 13 PATENT REQUIREMENTS Device for interconnecting a device connected to the Internet and a node in an intelligent network (IN), characterized in that the device is provided with means for emulating one (SPP) to a Service Control Point or a Service Data Point (SCP). Service Switching Point (SDP) of the intelligent network by converting a signal from Comite Consultatif International Telegrgphique et Telephonique Signal-System No. 7, CCITT-SS7 from the node of the intelligent network to a compatible signal for the device connected to the Internet and vice versa. Device according to claim 1, characterized in that the means for converting the signals is a program code written in a computer language. Device according to Claim 2, characterized in that the data language is C, JAVA, Smalltalk, Pascal, Fortran or Basic. Device according to claim 1, characterized in that the unit connected to the Internet is an information server. Device according to claim 4, characterized in that the information server is a World Wide Web unit, a so-called WWW unit. Device according to claim 1, characterized in that the CCITT-SS7 signal is Intelligent Network Application Protocol, INAP. Device according to claim 1, characterized in that the signal from the WWW unit is of the type Transmission Control Protocol / Internet Protocol, TCP / IP. Device according to claim 1, characterized in that the node in the intelligent network is a Service Control Point, SCP. 10 15 20 25 516 244 14 Device according to one of the preceding claims, characterized in that Dual Tone Multi Frequency, DTMF signaling to the node is used. Device according to Claim 9, characterized in that predefined services controlled by the DTMF signaling are used. 11. ll. Method for connecting an information server to a node in an intelligent network via the Internet, characterized in that between the information server and the node in the intelligent network a so-called Inter Working Unit, IWU, is arranged as (SPP) or a Service ( SCP) emulates a Service Switching Point Data Point (SDP) to a Service Control Point of the intelligent network, -that the IWU transforms a signal from the information server into a signal from Comite Consultatif International Telegraphique et Telephonique Signal-System No. 7, CCITT-SS7 in the intelligent network, and that the IWU transforms a signal from the node in the intelligent network to a suitable signal for the information server. Method according to claim 11, characterized in that the information server is a WWW application. Method according to claim 11, characterized in that the node. in the intelligent network is a Service Control Point, SCP. Method according to claim 13, characterized in that the signal from the SCP is INAP. Method according to claim 12, characterized in that the signal from the WWW application is TCP / IP.