WO2001074092A2 - Plateforme a point de communication intelligent - Google Patents
Plateforme a point de communication intelligent Download PDFInfo
- Publication number
- WO2001074092A2 WO2001074092A2 PCT/US2001/004857 US0104857W WO0174092A2 WO 2001074092 A2 WO2001074092 A2 WO 2001074092A2 US 0104857 W US0104857 W US 0104857W WO 0174092 A2 WO0174092 A2 WO 0174092A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- icp
- layer
- applications
- messages
- interface
- Prior art date
Links
- 230000011664 signaling Effects 0.000 title claims abstract description 49
- 238000000034 method Methods 0.000 claims abstract description 71
- 238000004891 communication Methods 0.000 claims abstract description 35
- 238000012545 processing Methods 0.000 claims abstract description 16
- 238000012546 transfer Methods 0.000 claims description 16
- 101000597193 Homo sapiens Telethonin Proteins 0.000 claims 3
- 102100035155 Telethonin Human genes 0.000 claims 3
- 229920001940 conductive polymer Polymers 0.000 claims 2
- 238000009616 inductively coupled plasma Methods 0.000 claims 2
- 230000008569 process Effects 0.000 abstract description 53
- 238000005259 measurement Methods 0.000 abstract description 4
- 101100346893 Arabidopsis thaliana MTPA2 gene Proteins 0.000 description 31
- 101150006417 MTP3 gene Proteins 0.000 description 31
- 101100346892 Arabidopsis thaliana MTPA1 gene Proteins 0.000 description 21
- 101150069989 MTP2 gene Proteins 0.000 description 21
- 101100098774 Rattus norvegicus Tap2 gene Proteins 0.000 description 21
- 238000007726 management method Methods 0.000 description 14
- 230000006870 function Effects 0.000 description 10
- 238000010586 diagram Methods 0.000 description 7
- 102100035352 2-oxoisovalerate dehydrogenase subunit alpha, mitochondrial Human genes 0.000 description 6
- 102100032008 Solute carrier family 40 member 1 Human genes 0.000 description 6
- 101710111423 Solute carrier family 40 member 1 Proteins 0.000 description 6
- 230000009471 action Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 238000013523 data management Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 238000010200 validation analysis Methods 0.000 description 2
- 101001028764 Arabidopsis thaliana Mitochondrial phosphate carrier protein 2, mitochondrial Proteins 0.000 description 1
- 230000005856 abnormality Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000036541 health Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000005192 partition Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 229920001098 polystyrene-block-poly(ethylene/propylene) Polymers 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/0016—Arrangements providing connection between exchanges
- H04Q3/0025—Provisions for signalling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
- H04M7/1205—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
- H04M7/126—Interworking of session control protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/0016—Arrangements providing connection between exchanges
- H04Q3/0029—Provisions for intelligent networking
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/0016—Arrangements providing connection between exchanges
- H04Q3/0029—Provisions for intelligent networking
- H04Q3/0045—Provisions for intelligent networking involving hybrid, i.e. a mixture of public and private, or multi-vendor systems
Definitions
- This invention relates generally to the Common Channel Signaling System 7 (SST network technology and, more particularly, to a host signaling processing platform that allows multiple SS7 applications to have visibility to SS7 network traffic while also having the ability to control SS7 network traffic.
- SST network Common Channel Signaling System 7
- the SS7 network is the backbone of the world's telecommunications networks. Service providers across the globe rely on the SS7 network to implement setup, routing, and control of a call, as well as to provide residential, business, and government customers advanced services such as 800 and 900 calling, caller ID, local number portability, and calling card verification. Without the SS7 network, the world's telecommunications networks would not function as we know it today.
- SS7 is a means to exchange information between nodes (switching systems, network data bases, or operator service systems) in a signaling network where messages are not carried over voice circuits but instead utilize separate links to convey the signaling information.
- Traditional interoffice signaling uses in-band signals to convey signaling information.
- Communications on an SS7 network falls into two distinct categories, command and control signals and network traffic. However, general voice traffic is carried in-band on voice channels. Command and control signals are carried out-of-band and are used to manage the network traffic,
- the SS7 network is comprised of a number of different types of signaling nodes, including Service Switching Points (SSPs) , Signaling Transfer Points (STPs) , and Service Control Points (SCPs) .
- SSPs Service Switching Points
- STPs Signaling Transfer Points
- SCPs Service Control Points
- SSPs originate, manage, and terminate calls.
- SCPs act as centralized databases that validate, authorize and answer service requests from SSPs, such as how to route an 800 number call.
- STP ' s route SS7 messages between SSPs, SCPs, and other STPs.
- the SS7 Network uses six types of signaling data links to connect the various nodes.
- the link specific functions and associated types of nodes with which they interact are described as follows:
- a LINKS (Access Links) carry the primary traffic of the network in the SS7 configuration.
- B-LINKS Bridge Links
- C LINKS (Cross Links) interconnect STP mated pairs together and are used primarily for administrative traffic . They can also carry message traffic if needed.
- D LINKS (Diagonal Links) interconnect STPs of different hierarchical levels which are primary and secondary signaling transfer points (i.e., regional STP to local STP) .
- E LINKS Extended Links
- F LINKS (Fully Associated Links) connect SSPs to other SSPs and are used for associated signaling between the two. These SSPs must be adjacent nodes.
- the present invention attempts to solve these problems. Accordingly, the present invention describes a system and method for providing a basic set of core services that will allow multiple SS7 based applications to be developed and deployed.
- the present invention includes an Intelligent Communication Point (ICP) Platform which is managed by a Graphical User Interface (GUI) known as the Intelligent Communication Manager (ICM) .
- GUI Graphical User Interface
- ICM Intelligent Communication Manager
- multiple ICP Platforms can be managed by the ICM.
- the ICP can reside on a computer that contains one or more Central Processing
- CPUs Centralized System
- a real-time operating system is deployed on the computer and provides, not only high availability support, but also supports the hot swap standards .
- Figure 1 is a block diagram of signaling end point connections in an SS7 network
- Figure 2 is an overview of the ICP Platform
- Figure 3 is a block diagram of SS7 network link routing
- Figure 4 is a functional diagram of the ICP Platform
- Figure 5 is a block diagram of the configuration data flow
- Figure 6 is a block diagram of the provisioning data flow
- FIG. 7 is a block diagram of the processing data flow.
- the ICP Platform is not an end point in the network, but rather an invisible node that sits in front of a Signaling End Point (SEP) , which may be, for example, a Signaling Transfer Point (STP) , Service Switching Point (SSP) , or Service Control Point (SCP) . All SS7 links are routed into the ICP and are then routed out to the SS7 network.
- SEP Signaling End Point
- STP Signaling Transfer Point
- SSP Service Switching Point
- SCP Service Control Point
- All SS7 links are routed into the ICP and are then routed out to the SS7 network.
- the ICP Platform design can be broken down into five parts; SS7 links cards and SS7 stack, interface to the ICM, platform core services, software and hardware control/status, and the application region.
- the ICP Platform contains multiple Tl/El link cards. AE SS7 links from an SSP are routed into the ICP and then out to the SS7 network. Each link card supports multiple links and processes Message Transfer Part (MTP) layers I and 2, while the CPU host card supports the ICP core services, applications, and MTP layer 3.
- MTPl defines the physical, electrical, and functional characteristics for the digital signaling link.
- MTP2 ensures accurate end-to-end transmission of a message across a signaling link.
- MTP2 implements flow control, message sequence validation, and error checking. When an error occurs on a signaling link, the message (or set of messages) is retransmitted.
- MTP2 which resides on the link cards, has a failsafe mode. When MTP3 fails, MTP2 will automatically route traffic between the SEP and the SS7 network .
- MTP3 provides message routing between signaling points in the SS7 Network and routes traffic away from failed links and signaling points. In addition, MTP3 controls traffic when congestion occurs.
- the ICP Platform two links are required to achieve the usage of one normal link. The ICP sits between an SSP and SS7 network and literally breaks the link into two links. These two links are considered to be one link pair. All SS7 traffic coming in one link will be routed out of the ICP through the other link of the link pair ( Figure 3) . If the ICP fails due to hardware or software failures, these link pairs close allowing the SS7 traffic to pass through the ICP as if the ICP was not in the network. The link pairs can also be manually closed while still allowing the ICP to have visibility to the SS7 traffic flowing through the link pairs. In addition, link cards route non-SS7 traffic on open DS-0 data lines directly to the other port without going through the ICP.
- the ICP Platform is managed by the ICM.
- the ICP interface is the bridge for communications between the ICP and the ICM. Through this interface software, the ICM user can gain access to the ICP core services and application software. The interface allows the user to bring the ICP into service, bring up and down application software, retrieve ICP core service data such as logs and events, retrieve application specific data, and configure/status the ICP hardware/software.
- the ICP Platform provides a set of core services for the developers of the applications to use when designing the application, including Logging Data, Process Events, Peg Counting, and the SS7 message interface (Figure 30), Logging Data services allow the applications to collect data which can be passed to the ICM for display to the customer.
- Process Event service is a method in which alarms can be raised to inform customers of an event that may or may not be critical . Each event is marked with a severity level which indicates to the user whether the event needs attention or not .
- Peg Counting services are tied in with the traffic metering and measurement (TMM) and bookkeeping processes .
- the SS7 message interface service allows applications to have access to SS7 traffic flowing through the ICP.
- the ICP processes all SS7 traffic according to rules. These rules define the actions as to how the SS7 message is going to be processed.
- Customers can implement rules that will act as a SS7 Firewall to protect the SEP (refer to the pending SS7 Firewall System patent, dated September 7, 1999) .
- Applications can receive SS7 traffic by implementing application rules that pass the message from the stack up through to the application, or can send out SS7 messages through an ICP SS7 API (Application Programming Interface) .
- the platform manager is responsible for starting core services and applications. In the event of a software failure, the platform manager will attempt to restart the failed software along with raising events to the ICM and closing the link pairs so that SS7 traffic is not disrupted.
- the manager software will send status of the software and overall ICP health to the ICM through the ICP interface software.
- the hardware and the SS7 stack configuration are handled by System Management Software. Through the rise of a configuration file stored on the ICM, the System Management Software programs the hardware interfaces such as the SS7 link cards and configures the SS7 stack software. Status of the hardware and state of the paired links (open or closed) are sent to the ICM through the ICP interface software.
- LNPC Local Number Portability Cache
- APIs Application Programming Interfaces
- figure I represents the end point connections in a SS7 network.
- Reference numeral 10 designates a signaling end point (SEP) which may be, for example, a Signaling Transfer Point (STP) , Service Switching Point (SSP) or Service Control Point (SCP) and reference numeral 12 designates signaling transfer points (STPs) .
- STP Signaling Transfer Point
- SSP Service Switching Point
- SCP Service Control Point
- reference numeral 12 designates signaling transfer points (STPs) .
- traffic flows on data links 14 between STPs and SEPs .
- FIG. 2 illustrates the placement of the ICP. Platform 200 within the SS7 network.
- the TCP Platform 200 is not an end point in the SS7 network but rather an invisible node that sits in front of an SEP 210/220, which may be for example, an STP, SSP or an SCP.
- All SS7 data links 14 are routed into the ICP Platform 200 and are then routed out to the SS7 network.
- the SS7 network includes redundant DS-1 or DS-OA links 14, which are high speed serial links.
- ICP Platform 200 processing distribution is driven by the signaling protocol stack as shown in Figure 2.
- the MTP1/MPT2 230/240 layer has a number of link cards (El/Tl) .
- the MTP1/MTP2 230/240 layer is loosely coupled with the
- MTP3 250 layer allowing MTP1/MTP2 230/240 to reside on the link cards and MTP3 250 to reside on the single board computer.
- MTPl 230 defines the physical, electrical, and functional characteristics for the digital signaling link.
- MTP2 240 which resides on the link cards, has a failsafe mode. When MTP3 250 fails, MTP2 240 will automatically route traffic back down and out to the SEP. MTP2 240 ensures accurate end-to-end transmission of a message across a signaling link 14. In addition, MTP2 240 implements flow control, message sequence validation, and error checking.
- the MTP3 250 layer can interface with multiple MTP2
- Peripheral Component Interconnect cPCI
- bus Peripheral Component Interconnect
- MTP3 250 manages the Message Signaling Unit (MSU) /Link association and has end to end management message coordination. MTP3 250 also provides, message routing between signaling points 210/220 in the SS7
- MTP3 250 controls traffic when congestion occurs.
- the Core Services 260 layer supports various support services and signaling processes to distribute traffic upwards to the Applications 270 layer and accept downward message routing requests.
- the Core Services 260 layer contains various subsystems and processes within these subsystems that developers of applications can use when designing applications.
- the Applications 270 layer contains all the applications that are implemented above the Core Services 260 layer.
- the Applications 270 layer supports various applications that can monitor, modify, or create messages. Each application can process its own set of messages, use its own rules and can be independent of other applications in general. In addition, one or more of the application processes may be running at a given time to load-share the work.
- the MTP3 250 stack may reside on the CPU card, or on the I/O card.
- a heartbeat signal 310 is maintained between MTP2 240 and MTP3 250. Loss of the heartbeat 310, indicating a failure of the CPU cards in the MTP3 250 layer, results in a failsafe mode (closed mode) . During a failsafe mode, message traffic is passed up only to MTP2
- the MSU 300 is then delivered to Core Services
- the Platform Control Subsystem (PCSS) 311 has data provisioning capability and is also responsible for the management of all the other subsystems. In particular it starts and stops all the other processes in a controlled manner.
- the Signaling Subsystem (SGSS) 312 routes and distributes SS7 messages . This Subsystem processes every message that passes through the ICP Platform 200 However, since Fill-in Signal Unit (FISU) messages do not pass up to the ICP platform 200, they are not processed by the SGSS
- the Interface Subsystem (IFSS) 313 is responsible for the external system interface.
- the ICP System has the capability to interface with multiple Intelligent components
- ICMs Communications Managers
- the IFSS 313 provides the network interface required for all these conditions.
- the Accounting Subsystem (ACSS) 314 is responsible for collecting the Traffic Metering and Measurement (TMM) data and statistic messages from subsystems that generate these messages.
- the Recording Subsystem (RCSS) 315 is responsible for collecting event and log messages for all other subsystems . Event messages are accumulated over a short period of time while the events are buffered and duplicates are filtered out.
- the various processes in the Data Management Subsystem (DMSS) 316 provide functions for data storage and retrieval, data synchronization, data distribution, data partition management, etc.
- the Utility Subsystem (UTSS) 317 contains library routines that are developed for re-use by all subsystem processes.
- the Intelligent Communication Manager (ICM) 320 a control and management device, is connected via the TCP/IP link 330 to the ICP Platform 200 for storage and display of logs, alerting, programming control policy rules, providing simple visibility, configuration, and other operational features of the ICP Platform 200.
- ICM Intelligent Communication Manager
- the TCP/IP link 330 provides Communication including, but not limited to, File Transfer Protocol (FTP) Services and Internet Services between the ICP 200 and the
- the ICP Platform 200 has the capability to view data traversed on MTP2 data links 14 and signaling units, except the Fill-in Signal Unit (FISU) .
- the ICP Platform 200 can view all MSUs 300, i.e., network management, traffic routing, test and upper layer protocols on MTP3 250 and can decode all Integrated Service Digital
- ISDN ISDN User Part
- ICP Platform 200 can also communicate within an enterprise network with various hosts for providing management, configuration, and reporting functions .
- the ICP Platform 200 is a fully active datalink layer
- Network layer control messages such as re-alignment messages, are transferred autonomously from node to node, e.g., from the SEP 210 to the SEP 220, within the SS7 network.
- the ICP Platform 200 manages these messages and coordinates control between the end nodes 210/220. This allows end nodes to operate as masters of MTP2 240, while communicating directly to the ICP Platform 200.
- MTP3 MSUs 300 are transferred end-to-end making the ICP Platform 200 appear invisible to each SEP
- the ICP Platform 200 is a full MTP2 signaling link terminal . It also manages MTP3 management messages between nodes 210 and 220. Additionally, it manages coordination of MTP3 traffic management, link management, and route management messages to synchronize MTP2 events between the two links. Functionally, the ICP Platform 200 consists of
- SS7 I/O logic which contains MTP1/MTP2 230/240, and MTP3 250 SS7 stacks, located on the I/O card.
- the function of the stacks process MSUs 300 for MTP3 250.
- the stacks process MSUs 300 for MTP3 250.
- ICP Platform 200 contains MTP3 control logic located on the
- CPU card These functions work independently of each other and provide a higher level visibility by processing signaling units into MSUs 300 and MSUs into protocol data units (PDUs) (layer 4 and above of the seven layer OSI network model) .
- PDUs protocol data units
- FIG. 4 illustrates a functional diagram of the Intelligent Communications Point (ICP) Platform 200.
- SS7 traffic 400 flows in and out the Signaling Subsystem 312
- SGSS SS7
- MTP1/MTP2 230/240 and MTP3 layer 250 SS7 messages are distributed to the processes in the Application Subsystem 270 (APSS) .
- the APSS 270 sends ISUP messages to the SGSS 312 and in some cases the actions that it wants the SGSS 312 to carry out, such as start/stop sending MSU 300, and block an SS7 message.
- the ICP Platform 200 combines call state monitoring, line control, and transaction state control for implementing access and service control functions.
- the ICP Platform 200 may be implemented with commercially available components as will be understood by those skilled in the art. While not shown, it is understood that the ICP Platform 200 is controlled by computer programming instructions stored in memory within the ICP Platform 200 and potentially other components of the system connected to the ICP Platform 200.
- PCSS 311 The Platform Control Subsystem (PCSS) 311 is responsible for the management of all other subsystems. PCSS 311 processes, which include the Platform Control
- the Platform Control Process is ordinarily the first process to start on the ICP Platform 200 and manages all other processes running on the ICP
- the Rule Provisioning Process manages the process configuration profile and the application rule repository. This process receives updates from the IFSS
- Provisioning Process is responsible for SS7 Node provisioning. This process will receive updates from the IFSS 313 and will make updates to the SS7 stack, using vendor provided programming interfaces.
- the Signaling Subsystem (SGSS) 312 which is part of the core cervices layer 260, contains the ISDN User Part (ISUP) process 410, the Signaling Connection Control Point (SCCP) process 420, the Signaling Network Management 430 (SNM) and the Signaling Network Testing 430 (SNT) . All ISUP process 410 and SCCP process 420 traffic can be processed through a SS7 firewall to enforce control policy rules . Management messages such as realignment messages are controlled by the ICP Platform's 200 control message manager application.
- the ISUP process 410 contained in the SGSS 312 is responsible for receiving and forwarding ISUP messages between the MTP3 layer 250 and the Application Layer 270.
- This process maintains connectivity to the Application Layer 270 process and determines readiness of the ISUP message processing capability, and decodes and encodes the
- the ISUP process 410 distributes messages to the Application Layer 270 processes, discards message response if timeout occurs, and takes default action if message response timeout occurs.
- the SCCP process 420 is responsible for receiving and forwarding SCCP messages between the MTP3 layer 250 and the
- the SCCP process 420 provides communications between signaling nodes 210 and 220 and provides specialized routing and management functions necessary to support routing to partitioned and/or duplicate databases. In addition, this process returns messages back to MTP3 250 when message is checked OK.
- the SNM/SNT process 430 is responsible for receiving and forwarding SNM/SNT, and in particular the Link Status Signal Unit (LSSU) messages and any other messages that the ISUP process 410 and SCCP 420 process can not process.
- SNM/SNT process 430 generates Traffic Metering and Measurement (TMM) data and generates events to report LSSU data.
- TMM Traffic Metering and Measurement
- the APSS 270 sends MSUs 300 to the ICM 320 through the
- TMM data is generated by both the APSS 270 and the SGSS 312.
- Statistics are only generated by the APSS 270 and are sent to the ICM 320 through the Accounting Subsystem 314 (ACSS) . Every subsystem generates events and logs that are sent to the ICM 320 through the Recording Subsystem (RCSS) 315.
- RCSS Recording Subsystem
- the ICM 320 provides configuration data for the ICP
- configuration data is sent to the PCSS 311 through the
- the PCSS 311 updates the database with platform configuration through the DMSS 316.
- SS7 node configuration is sent to the UTSS 317.
- UTSS 317 interfaces with the SS7 stack (vendor software portion) to change stack configuration.
- the ICM 320 provides rules to the APSS 270 and SGSS 312, which use the rules to determine message distribution and processing. Rules are first passed to the Platform Control Subsystem 311 (PCSS) which updates the database at the Data Management Subsystem 316
- DMSS DMSS
- rules are first passed from the IFSS 313 to the PCSS 311 which updates the database at the DMSS 316.
- the APSS 270 and the SGSS 312 then read the rules as needed.
- the ICM 320 also sends the rule switching command (CMD) to the PCSS 311 which is processed and used in the same way as the rules .
- CMD rule switching command
- FIG. 7 illustrates SS7 traffic 400 distribution and supporting data flow in the system.
- SS7 traffic 400 flows in and out the SGSS 312.
- ISUP and MSU messages are distributed to the processes in the APSS 270.
- the APSS 270 sends ISUP messages to the SGSS 312.
- the APSS 270 sends
- TMM data is generated by both the APSS 270 and the SGSS 312 and is sent to the ICM 320 through the ACSS 314.
- Statistics are generated by the
- APSS 270 and are sent to the ICM 320 through the ACSS 314.
- Every subsystem generates event and log data that are sent to the ICM 320 through the RCSS 315.
- the present invention can take many forms and embodiments.
- the embodiments shown herein are intended to illustrate rather than to limit the invention, it being appreciated that variations may be made without departing from the spirit of the scope of the invention.
- the algorithms and process functions performed by the system may be organized into any number of different modules or computer programs for operation on one or more processors or workstations within the system. Different configurations of computers and processors for the system are contemplated.
- the programs used to implement the methods and processes of the system may be implemented in any appropriate programming language and run in cooperation with any hardware device.
- the system may be used for service providers, Internet Service Providers, enterprises, and may other entities utilizing SS7 signaling devices.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Telephonic Communication Services (AREA)
Abstract
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU2001245276A AU2001245276A1 (en) | 2000-03-28 | 2001-02-15 | Intelligent communications point platform |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/536,958 US6850482B1 (en) | 2000-03-28 | 2000-03-28 | System and method for data traffic redirection |
US09/537,016 | 2000-03-28 | ||
US09/536,541 US6668051B1 (en) | 2000-03-28 | 2000-03-28 | Intelligent communications point platform |
US09/536,958 | 2000-03-28 | ||
US09/536,541 | 2000-03-28 | ||
US09/537,016 US6625273B1 (en) | 2000-03-28 | 2000-03-28 | System and method for a local number portability cache |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2001074092A2 true WO2001074092A2 (fr) | 2001-10-04 |
WO2001074092A3 WO2001074092A3 (fr) | 2002-01-17 |
Family
ID=27415220
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2001/004857 WO2001074092A2 (fr) | 2000-03-28 | 2001-02-15 | Plateforme a point de communication intelligent |
Country Status (2)
Country | Link |
---|---|
AU (1) | AU2001245276A1 (fr) |
WO (1) | WO2001074092A2 (fr) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11330098B1 (en) | 2020-11-06 | 2022-05-10 | Sevis Systems, Llc | System and method for enabling trusted caller identity and spoofed call prevention |
US12126763B2 (en) | 2020-11-06 | 2024-10-22 | Sevis Systems, Llc | System and method for enabling trusted caller identity and spoofed call prevention |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1999035773A1 (fr) * | 1998-01-07 | 1999-07-15 | Mci Worldcom, Inc. | Plate-forme a canaux supports virtuels permettant de traiter des demandes de service reçues sous la forme de donnees de canaux |
-
2001
- 2001-02-15 AU AU2001245276A patent/AU2001245276A1/en not_active Abandoned
- 2001-02-15 WO PCT/US2001/004857 patent/WO2001074092A2/fr active Application Filing
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1999035773A1 (fr) * | 1998-01-07 | 1999-07-15 | Mci Worldcom, Inc. | Plate-forme a canaux supports virtuels permettant de traiter des demandes de service reçues sous la forme de donnees de canaux |
Non-Patent Citations (1)
Title |
---|
SEVCIK M ET AL: "CUSTOMERS IN DRIVER'S SEAT: PRIVATE INTELLIGENT NETWORK CONTROL POINT" ISS '95. WORLD TELECOMMUNICATIONS CONGRESS. (INTERNATIONAL SWITCHING SYMPOSIUM). ADVANCED SWITCHING TECHNOLOGIES FOR UNIVERSAL TELECOMMUNICATIONS AT THE BEGINNING OF THE 21ST. CENTURY. BERLIN, APR. 23 - 28, 1995, PROCEEDINGS OF THE INTERNATIONAL SWIT, vol. 2 SYMP. 15, 23 April 1995 (1995-04-23), pages 41-44, XP000495622 ISBN: 3-8007-2093-0 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11330098B1 (en) | 2020-11-06 | 2022-05-10 | Sevis Systems, Llc | System and method for enabling trusted caller identity and spoofed call prevention |
US12126763B2 (en) | 2020-11-06 | 2024-10-22 | Sevis Systems, Llc | System and method for enabling trusted caller identity and spoofed call prevention |
Also Published As
Publication number | Publication date |
---|---|
WO2001074092A3 (fr) | 2002-01-17 |
AU2001245276A1 (en) | 2001-10-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6668051B1 (en) | Intelligent communications point platform | |
US6226373B1 (en) | Intelligent service peripheral/intelligent peripheral | |
US6151390A (en) | Protocol conversion using channel associated signaling | |
US5757895A (en) | Extracting and processing data derived from a common channel signalling network | |
US6333931B1 (en) | Method and apparatus for interconnecting a circuit-switched telephony network and a packet-switched data network, and applications thereof | |
US6493353B2 (en) | Communications signaling gateway and system for an advanced service node | |
US6028914A (en) | System and method for monitoring performance statistics in a communications network | |
US6175618B1 (en) | ANI based routing | |
US5862334A (en) | Mediated access to an intelligent network | |
US6411681B1 (en) | Traffic track measurements for analysis of network troubles | |
US6308276B1 (en) | SS7 firewall system | |
CA2289515A1 (fr) | Simulateur servant a simuler un reseau intelligent | |
USH1964H1 (en) | Resource management sub-system of a telecommunications switching system | |
Kuhn et al. | Common channel signaling networks: Past, present, future | |
JPH04229798A (ja) | 呼処理方法 | |
EP1169817A4 (fr) | Dispositif peripherique et procede pour l'interconnexion de points de signalisation ss7 (sps) utilisant ce dispositif | |
EP1159816B1 (fr) | Protection des reseaux contre les signaux non intentionnels, frauduleux et/ou malintentionnes et systeme a cet effet | |
WO2001074092A2 (fr) | Plateforme a point de communication intelligent | |
EP0998829B1 (fr) | Peripherique de service intelligent/peripherique intelligent | |
WO2000054468A2 (fr) | Systeme et procede assurant une interoperabilite entre des reseaux commutes par circuits et des reseaux par paquets | |
US7573899B2 (en) | Adaptor module | |
Goldberg et al. | Common channel signaling interface for local exchange carrier to interexchange carrier interconnection | |
CA2205386C (fr) | Extraction et traitement de donnees provenant d'un reseau de signalisation par canal semaphore | |
EP1034485A1 (fr) | Plate-forme de services a acces virtuel amelioree | |
WO1999030474A1 (fr) | Plate-forme de services a acces virtuel entre bande large et bande restreinte |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A2 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A2 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
AK | Designated states |
Kind code of ref document: A3 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A3 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 69(1)EPC, FORM 1205A EPO DATED12.02.03 |
|
122 | Ep: pct application non-entry in european phase | ||
NENP | Non-entry into the national phase in: |
Ref country code: JP |