Electrical computers and digital processing systems: multicomput – Computer network managing
Reexamination Certificate
1998-06-23
2001-12-11
Harrell, Robert B. (Department: 2152)
Electrical computers and digital processing systems: multicomput
Computer network managing
C709S224000, C709S246000
Reexamination Certificate
active
06330598
ABSTRACT:
FIELD OF THE INVENTION
The present invention relates generally to telecommunications and, more particularly, to a global service management system for an advanced intelligent network.
BACKGROUND OF THE INVENTION
Advanced Intelligent Network (AIN) systems are presently being employed by telecommunications companies including the Regional Bell Operating Companies (RBOCs) to provide advanced subscription services to subscribers. Examples of advanced subscription services include the ability to route a call to a customer-defined location based on the zip code of the calling party; and the ability to enable a customer to restrict or prevent calls to predefined numbers specified by (and under the control of) the customer.
In the present system architecture, the switching network comprises a number of end offices equipped to communicate under the Signaling System 7 (SS7) protocol. In AIN nomenclature, these end offices are termed Signal Switching Points (SSPs). The switching network also includes Signal Transfer Points (STPs), which are packet switching devices implemented to communicate messages between SSPs and Signal Control Points (SCPs). SCPs are commercially available, special purpose computing equipment associated with a predetermined geographic area and including substantial databases identifying those subscribers and the AIN services subscribers have requested (e.g., call waiting, etc.).
When a call is initiated, it is routed to an end office such as an SSP. If the SSP identifies a “trigger” associated with the call (i.e., a prefix identifying the call as one subject to an AIN service subscription by virtue of the calling or receiving subscriber's service contract), it develops a query containing certain information and requesting instruction on processing the call. The query is routed to an STP which, after conducting certain processing steps irrelevant here, forwards the processed query to an appropriate one of a number of SCPs (identified by an identifier in the query) for directions on how to process the call. The SCP addresses its database and replies to the processed query received from the STP, thereby ensuring the call is processed per the subscriber's predefined service requirements.
In the typical architecture, a plurality of SCPs are employed. These SCPs are typically located in two or more locations and assigned to service different subscribers. (In some instances, multiple SCPs have the capability to service the same subscribers thereby providing redundancy in case of failure). The operation of the SCPs are typically managed by one or more network element managers. Network element managers are computers provided by the vendor(s) of the SCPs. Each SCP vendor provides its own network element manager to manage its SCPs. Thus, if a given telecommunications company purchases SCPs from more than one vendor, it will have more than one network element manager. Typically, network element managers from different vendors are not adapted to communicate with one another and operate pursuant to different protocols.
In order to add new subscribers or services to the AIN, or to update the package of existing services for a given subscriber, it is necessary to update the databases of one or more of the SCPs in service. If a given telecommunications company employs SCPs from different vendors, it will be required to process such updates differently depending upon the SCP being addressed. In other words, vendor A's SCPs will have to be addressed differently than vendor B's SCPs. This disparity interjects confusion, delay, and added cost into the service provisioning process.
Some telecommunications companies have sought to address this problem by discarding the network element managers provided by the vendors of the SCPs and substituting one or more of their own, in-house developed, network element managers. Such an approach provides uniformity between network element managers employed by the telecommunications company, but is disadvantageous in that it removes the vendor designed network element managers (which are particularly designed for managing the SCPs with which they are sold) from the system.
As the telecommunications industry has advanced and new user-defined services have become available (e.g., screening calls from user defined numbers, etc.), it has become more and more desirable to provide users with ready access to their subscription service data. Due to the proliferation of personal computers, the internet has become a significant vehicle for such access. However, although the services which permit a user to change its subscription package and/or to modify the parameters of the services within the package via personal computer or touch tone phone are gaining popularity, these services can be confusing to modify because they provide users with little or no information concerning the status of requested service changes until such services are actually implemented by the AIN system. For example, if a user has requested that a call screening service be modified to exclude phone calls from the 312 and the 202 area codes as of the following Monday, until Monday arrives the user typically has no way of knowing what its service package will consist of on that day unless it keeps a written record and/or remembers its instructions to the system. Thus, in this example, if the user decides to make further changes to the subject service prior to Monday, the user may encounter confusion as to the status of the user defined service.
REFERENCES:
patent: 5212789 (1993-05-01), Rago
patent: 5247571 (1993-09-01), Kay et al.
patent: 5386467 (1995-01-01), Ahmad
patent: 5392402 (1995-02-01), Robrock, II
patent: 5418844 (1995-05-01), Morrisey et al.
patent: 5436957 (1995-07-01), McConnell
patent: 5517562 (1996-05-01), McConnell
patent: 5524146 (1996-06-01), Morrisey et al.
patent: 5541917 (1996-07-01), Farris
patent: 5546574 (1996-08-01), Grosskopf et al.
patent: 5553130 (1996-09-01), Turner
patent: 5566235 (1996-10-01), Hetz
patent: 5570410 (1996-10-01), Hooshiari
patent: 5579318 (1996-11-01), Reuss et al.
patent: 5579384 (1996-11-01), Seymour
patent: 5581610 (1996-12-01), Hooshiari
patent: 5583920 (1996-12-01), Wheeler, Jr.
patent: 5594789 (1997-01-01), Seazholtz et al.
patent: 5619562 (1997-04-01), Maurer et al.
patent: 5629974 (1997-05-01), Rajala et al.
patent: 5644619 (1997-07-01), Farris et al.
patent: 5651053 (1997-07-01), Mitchell
patent: 5664102 (1997-09-01), Faynberg
patent: 5706286 (1998-01-01), Reiman et al.
patent: 5864614 (1999-01-01), Farris et al.
patent: 5890156 (1999-03-01), Rekieta et al.
patent: 5937412 (1999-08-01), Kohli et al.
patent: 5991803 (1999-11-01), Glitho et al.
patent: 6018567 (2000-01-01), Dulman
patent: 6101182 (2000-08-01), Sistanizadeh et al.
patent: 6161128 (2000-12-01), Smyk
Aitken, D.J., “Experiences of Implementation using Advanced Intelligent Network Release 1 Architecture”, 1992, Eighth International Conference on Software Engineering for Telecommunication System Services, pp. 19-26.
Beckwith Scott Alan
Curtis John D
Ginter Ronald Joseph
Layman Mark Wade
Mather Steven Louis
Ameritech Corporation
Brinks Hofer Gilson & Lione
Harrell Robert B.
Romero Almari
LandOfFree
Global service management system for an advanced intelligent... does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Global service management system for an advanced intelligent..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Global service management system for an advanced intelligent... will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-2571444