Provided are a system and method for interworking service capability features (SCFs) and protocols in an open service gateway. The system includes service capability features that generate and process various protocol messages, and a protocol stack that enables an interwork with a communications network. The protocol stack includes: one or more units that maintain various protocols, a unit that performs data connection and transmits and processes messages, and a unit that manages the various protocols. In the protocol stack, protocol identifiers that differentiate the protocols from one another, and message identifiers that differentiate service capability features from one another are stored in the unit that manages the various protocols.

Patent
   7680131
Priority
Dec 20 2004
Filed
Sep 09 2005
Issued
Mar 16 2010
Expiry
Dec 14 2028
Extension
1192 days
Assg.orig
Entity
Small
0
14
EXPIRED
1. A system for interworking service capability features and protocols in an open service gateway, the system comprising:
a computer including:
the service capability features generating and processing various protocol messages; and
a protocol stack enabling an interwork between the open service gateway and a plurality of communications networks of different types, wherein the protocol stack includes protocol identifiers which differentiate the protocols from one another, and message identifiers which differentiate the service capability features from one another, and wherein the service capability features have different ranges of the message identifier.
11. A method of interworking service capability features and protocols in an open service gateway, the method comprising:
(a) receiving a protocol message which includes a protocol identifier and a message identifier, the protocol identifier differentiating the protocols from one another and the message identifier differentiating the service capability features from one another, the service capability features of the open service gateway interfacing with a plurality of communication networks of different types through a protocol stack, wherein the service capability features have different ranges of the message identifier;
(b) decoding the received protocol message by a computer;
(c) checking the protocol identifier included in the protocol message, and transmitting the protocol message to a unit for maintaining a protocol corresponding to the protocol identifier; and
(d) checking the message identifier included in the protocol message, and providing the protocol message to a corresponding service capability feature.
6. A method of interworking service capability features and protocols in an open service gateway, the method comprising:
(a) requesting a service by a computer to be provided from an open application server to a service capability feature in the open service gateway, wherein a protocol stack enables the open service gateway to interface with a plurality of communications networks of different types, the protocol stack including a message identifier and a protocol identifier, the service capability features having different ranges of the message identifier;
(b) generating a protocol message required to accomplish the service, and encoding the protocol message to include the message identifier which differentiates the service capability feature from other service capability features;
(c) transmitting the encoded protocol message to a unit for maintaining a protocol corresponding to the service capability features; and
(d) allocating the protocol identifier to the transmitted protocol message, the protocol identifier differentiating the protocols from one another.
2. The system of claim 1, wherein the protocol stack comprises:
one or more units maintaining various types of protocols;
a first unit performing data connection, and transmitting and processing a message; and
a second unit managing the various types of protocols,
wherein the protocol identifiers and the message identifiers are stored in the second unit managing the various types of protocols.
3. The system of claim 2, wherein the protocol stack is an SS No. 7 protocol stack,
the first unit performing data connection, and transmitting and processing messages is a message transfer part, and
the second unit managing the various types of protocols is a signal connection control part.
4. The system of claim 1, wherein the protocol identifiers are subsystem numbers, and
the message identifiers of different ranges are allocated to the service capability features.
5. The system of claim 4, wherein the protocol messages are distributed to corresponding the unit maintaining protocols using the subsystem numbers, and
the service capability features are detected and distributed using the corresponding message identifiers.
7. The method of claim 6, wherein in the step (a), when a service request is a new session, a corresponding message identifier to the service capability feature is allocated.
8. The method of claim 6, wherein the ranges of message identifiers allocated to the service capability features are different from one another.
9. The method of claim 6, wherein the protocol identifier is a number of sub-system which maintains the corresponding protocol.
10. A computer recording medium having embodied thereon a computer program for the method of claim 6.
12. The method of claim 11, wherein if it is determined in the step (d) that the protocol message includes the message identifier, the protocol message is provided to a network event processing service capability feature.
13. The method of claim 11, wherein the protocol identifier is a number of sub-system which maintains the corresponding protocol.

This application claims the priority of Korean Patent Application No. 10-2004-0108980, filed on Dec. 20, 2004, in the Korean Intellectual Property Office, the disclosure of which are incorporated herein in its entirety by reference.

1. Field of the Invention

The present invention relates to a system and method for interworking Service Capability Features (SCFs) and protocols in an open service gateway.

2. Description of the Related Art

An open service gateway is indispensable to a next-generation open network that enables a service to be provided using a standard open Application Program Interface (API) regardless of whether the network is a wired network, a wireless network, or an Internet Protocol (IP) network. The open service gateway abstracts various network control functions such as call control, call monitoring, charging, providing of location information, and providing of presence information, and provides the result of abstraction as SCFs. To provide the result of abstraction as the SCFs, the SCFs must be interworked with protocols. Systems for providing communications network services have recently been developed to operate dependently upon a single specific network. In contrast, the open service gateway system is designed to provide communications services via an identical open API in various types of networks, not a single network.

The open service gateway is capable of abstracting and providing functions of various networks such as a wireless communications network, a wire communications network, and an IP network. Therefore, an application service provider can provide services using the open API without special knowledge of a network. An interwork with each communications network requires a protocol stack that matches each communications network and can process a message. There are representative protocols such as a Wireless Intelligent Network (WIN), a Mobile Application Part (MAP), an Intelligent Network Application Part (INAP), a Camel Application Part (CAP), and a Session Initiation Protocol (SIP). All the protocols, except the SIP that is an Internet protocol, are application parts of an SS No. 7 protocol stack. Each SCF provided from the open service gateway interworks with some or all of the above protocols, and therefore, it is necessary to detect and transmit an SCF matching a protocol message.

The present invention provides a system and method for effectively mapping protocols to adequate Service Capability Features (SCFs) by processing protocol messages according to a data structure for distribution of protocols.

According to one aspect of the present invention, there is provided a system for interworking service capability features and protocols in an open service gateway including: the service capability features generating and processing various protocol messages; and a protocol stack enabling an interwork with a communications network, wherein the protocol stack includes protocol identifiers which differentiate protocols from one another, and message identifiers which differentiate the service capability features from one another.

According to another aspect of the present invention, there is provided a method of interworking service capability features and protocols in an open service gateway including: (a) requesting a service to be provided from an open application server to a service capability feature in the open service gateway; (b) generating a protocol message required to accomplish the service, and encoding the protocol message to include a message identifier which differentiates the service capability feature from other service capability features; (c) transmitting the encoded protocol message to a unit for maintaining a protocol corresponding to the service capability feature; and (d) allocating a protocol identifier to the transmitted protocol message, the protocol identifier differentiating protocols from one another.

According to yet another aspect of the present invention, there is provided a method of interworking service capability features and protocols in an open service gateway including: (a) receiving a protocol message which includes a protocol identifier and a message identifier, the protocol identifier differentiating protocols from one another and the message identifier differentiating service capability features from one another; (b) decoding the received protocol message; (c) checking the protocol identifier included in the protocol message, and transmitting the protocol message to a unit for maintaining a protocol corresponding to the protocol identifier; and (d) checking the message identifier included in the protocol message, and providing the protocol message to a corresponding service capability feature.

Accordingly, it is possible to effectively distribute protocol messages to SCFs.

The above and other aspects and advantages of the present invention will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings in which:

FIG. 1 illustrates a network structure in which a service is provided using an open service gateway according to an embodiment of the present invention;

FIG. 2 is a block diagram of an interwork between Service Capability Features (SCFs) in the open service gateway of FIG. 1 with an SS No. 7 protocol stack according to an embodiment of the present invention;

FIG. 3 is an information table required for distribution of protocol messages according to an embodiment of the present invention;

FIG. 4 is a flowchart of a method of processing a protocol service request transmitted from an application server in an open service gateway according to an embodiment of the present invention; and

FIG. 5 is a flowchart of a method of distributing protocol messages received via a communications network to SCFs in an open service gateway according to an embodiment of the present invention.

Hereinafter, exemplary embodiments of a system and method for interworking Service Capability Features (SCFs) and protocols in an open service gateway according to the present invention will be described in detail with reference the accompanying drawings.

FIG. 1 illustrates a network structure in which an open service gateway 2 abstracts functions of each network and provides the result of abstraction as an open Application Program Interface (API), and an open application server 1 for application service logic provides a service through the API.

Referring to FIG. 1, the open service gateway 2 provides a mobile network protocol, a wired network protocol, and an Internet Protocol (IP) network protocol for interworking with each network. The network structure of FIG. 1 enables an application service provider to provide application services without special knowledge of network, irrespective of the type of network.

FIG. 2 is a block diagram of an interwork between SCFs in the open service gateway 2 and an SS No. 7 protocol stack according to an embodiment of the present invention. Referring to FIG. 2, the open service gateway 2 abstracts network functions and provides the result of abstraction as the SCFs. Each SCF provides functions such as call control, call monitoring, location information management, presence information management, and terminal state management. Each SCF must interwork with a network protocol required to perform a function to be provided.

FIG. 2 illustrates the SS No. 7 protocol stack that supports a wire/wireless network protocol, but the present invention is not limited to the SS No. 7 protocol stack. The SS No. 7 protocol stack includes an Intelligent Network Application Part (INAP) 3, a Wireless Intelligent Network (WIN) 4, a Mobile Application Part (MAP) 5, a Transaction Capability Application Part (TCAP) 6, a Signaling Connection Control Part (SCCP) 7, and a Message Transfer Part (MTP) 8 of levels 1 through 3. The MTP 8 performs connection of a signal data, and transmits and processes a signal message. The SCCP 7 enables logic signal connection in a network to be controlled, and the signal data to be transmitted. The TCAP 6 is an SCCP user interface. The INAP 3, the WIN 4, and the MAP 5 are TCAP user interfaces, and interwork directly with the SCFs. In the SS No. 7 protocol stack, the SCCP 7 manages the INAP 3, the WIN 4, and the MAP 5, and a unique SubSystem Number (SSN) is allocated to each of the INAP 3, the WIN 4, and the MAP 5 so that they can be distinguished from other protocols. Also, the SCFs of the open service gateway 2 use a Message Identifier (MID) that falls within the predetermined range of MID, thereby enabling protocol messages to be transmitted to the corresponding SCFs.

FIG. 3 is an information table required for protocol message distribution according to an embodiment of the present invention. Referring to FIG. 3, the INAP 3, the WIN 4, and the MAP 5 which are user parts of the TCAP 6 are differentiated from one another using different SSNs, and MIDs of different ranges are allocated to SCFs, respectively.

The SSNs are defined by the SCCP 7, and protocols are differentiated from one another using different SSNs corresponding to the functions of user parts of the SCCP 7. Referring to FIG. 3, identifiers 0×31, 0×32, and 0×33 are allocated to the INAP 3, the WIN 4, and the MAP 5, respectively, thereby differentiating protocols from one another in an open service gateway supporting multiple protocols.

When receiving of signal messages from the open application server 1 of FIG. 1, the SCCP 7 distributes the signal messages to sub-systems which maintain corresponding protocols in a gateway, of the open service gateway according the SSNs. When a protocol interworks with several SCFs, an SCF that transmits the signal message must be detected. In this case, the SCF can be detected by checking the range of MID allocated to each SCF. In other words, it is possible to distribute the signal messages to the adequate sub-systems using the SSN and the MID of the protocol messages used by the SCCP 7.

FIG. 4 is a flowchart of a method in which a service capability feature (SCF) receives a request from the open application server 1 of FIG. 1 and processes it using a related protocol according to an embodiment of the present invention. Conversely, FIG. 5 is a flowchart of a method of transmitting a protocol message received via a network to a corresponding SCF according to an embodiment of the present invention.

Referring to FIG. 4, the open application server 1 of FIG. 1 requests the SCF to provide a protocol-related service, e.g., a call control service, an event monitoring service, and so on, through an open API (S410).

Next, it is determined whether the request for the service is a request for the start of a new session or a request for a previous session (S420). If the request for the service is the request for the previous session, previously allocated MID is used. If the request for the service is the request for a new session, new MID is allocated (S430). The new MID is selected within the range of MID matching the type of the SCF according to the information table illustrated in FIG. 3. Next, a protocol message required to accomplish the service in the SCF is generated, and encoded to include the MID (S440). Next, SSN is allocated to the encoded message and the encoded message is transmitted to a sub-system which maintains a related protocol (S450).

If the sub-system sends the encoded message by a predetermined protocol to the TCAP 6 of FIG. 2, the TCAP 6 maps it to dialogue ID and transmits the result of mapping to the SCCP 7. The SCCP 7 checks the range of the dialogue ID of the encoded message, maps the encoded message to the SSN, encodes the SSN, and sends the encoded message to a signal point of other station or server (S460).

FIG. 5 is a flowchart of a method of distributing protocol messages that are generated by a communications network as reply messages for protocol requests or report messages for the result of network event monitoring, to corresponding SCFs in the open service gateway 2 of FIG. 1, according to an embodiment of the present invention.

Referring to FIG. 5, when receiving of the protocol messages, the SCCP 7 of FIG. 2 decodes or encodes them in an SS No. 7 protocol stack (S510). Next, the SCCP 7 checks an SSN corresponding to each protocol, and the TCAP 6 converts the SSNs into dialogue ID and classifies and sends the protocol messages to the INAP 3, the WIN 4, or the MAP 5 (S520).

Each sub-system checks the MID included in each protocol message (S530), and detects a related SCF and transmits the protocol message using the information table of FIG. 3 (S540). If there is a protocol message, the range of MID of which is not specified in the information table, the protocol message is a protocol message describing the result of network message monitoring, not a replay message to a request for a protocol made in an SCF, and therefore, the protocol message is transmitted to an SCF that processes a network event (S550). The protocol messages transmitted in operation S540 are distributed to and processed in the corresponding SCFs (S560).

The present invention can be embodied as a computer readable code in a computer readable medium. The computer readable medium may be any recording apparatus capable of storing data that is read by a computer system, e.g., a read-only memory (ROM), a random access memory (RAM), a compact disc (CD)-ROM, a magnetic tape, a floppy disk, an optical data storage device, and so on. The computer readable medium can be distributed among computer systems that are interconnected through a network, and the present invention may be stored and implemented as a computer readable code in the distributed system.

In a system and method for interworking Service Capability Features (SCFs) and protocols in an open service gateway according to the present invention, the protocol messages received via a communications network to corresponding SCFs can be effectively distributed by defining information required for protocol distribution in the open service gateway, generating and processing a protocol message in a related SCF when a request for service is transmitted from an open application server.

While this invention has been particularly shown and described with reference to exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.

Kim, Sang Hyun, Lee, Byung Sun, Choi, Young Il, Chung, Ki Sook, Ku, Yeon Heon, Jun, Kyung Pyo

Patent Priority Assignee Title
Patent Priority Assignee Title
6415151, Jul 06 1998 Siemens Aktiengesellschaft Method and mobile radio telephone network for handling a packet data service
6856676, Oct 15 1998 Alcatel System and method of controlling and managing voice and data services in a telecommunications network
6947541, Apr 26 1999 Nokia Siemens Networks Oy Enhancing an intelligent network service
6980639, Mar 09 2000 LG-ERICSSON CO , LTD INAP processing method for communication between SSP and TCAP
7272133, Aug 12 2002 Intellectual Ventures II LLC Method and system for implementing standard applications on an intelligent network service control point through an open services gateway
20030087633,
20030126584,
20030206562,
20040242186,
20050111650,
KR1020010001133,
KR1020030012507,
KR1020040001247,
KR20030068105,
////////
Executed onAssignorAssigneeConveyanceFrameReelDoc
Jul 13 2005CHUNG, KI SOOKElectronics and Telecommunications Research InstituteASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS 0169910976 pdf
Jul 13 2005KU, YEON HEONElectronics and Telecommunications Research InstituteASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS 0169910976 pdf
Jul 13 2005KIM, SANG HYUNElectronics and Telecommunications Research InstituteASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS 0169910976 pdf
Jul 14 2005LEE, BYUNG SUNElectronics and Telecommunications Research InstituteASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS 0169910976 pdf
Jul 14 2005JUN, KYUNG PYOElectronics and Telecommunications Research InstituteASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS 0169910976 pdf
Aug 03 2005CHOI, YOUNG ILElectronics and Telecommunications Research InstituteASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS 0169910976 pdf
Sep 09 2005Electronics and Telecommunications Research Institute(assignment on the face of the patent)
Mar 14 2014Electronics and Telecommunications Research InstituteINTELLECTUAL DISCOVERY CO , LTD LICENSE SEE DOCUMENT FOR DETAILS 0324560991 pdf
Date Maintenance Fee Events
Oct 19 2010ASPN: Payor Number Assigned.
Aug 16 2013M2551: Payment of Maintenance Fee, 4th Yr, Small Entity.
Oct 30 2017REM: Maintenance Fee Reminder Mailed.
Apr 16 2018EXP: Patent Expired for Failure to Pay Maintenance Fees.


Date Maintenance Schedule
Mar 16 20134 years fee payment window open
Sep 16 20136 months grace period start (w surcharge)
Mar 16 2014patent expiry (for year 4)
Mar 16 20162 years to revive unintentionally abandoned end. (for year 4)
Mar 16 20178 years fee payment window open
Sep 16 20176 months grace period start (w surcharge)
Mar 16 2018patent expiry (for year 8)
Mar 16 20202 years to revive unintentionally abandoned end. (for year 8)
Mar 16 202112 years fee payment window open
Sep 16 20216 months grace period start (w surcharge)
Mar 16 2022patent expiry (for year 12)
Mar 16 20242 years to revive unintentionally abandoned end. (for year 12)