TAP YIPL

home *** CD-ROM | disk | FTP | other *** search

/ TAP YIPL / TAP_and_YIPL_Collection_CD.iso / PHREAK / SYSINFO / DDSN.TXT < prev next >

Wrap

Text File | 2000-02-16 | 35.9 KB | 696 lines

/////////////////////////////////////////////////////////////////////////// // // // DDSN Intelligent Network // // // // A full rundown of our LinkLine (0800) and LoCall (0345) Services // // // // Presented in full By Keltic Phr0st // // // /////////////////////////////////////////////////////////////////////////// "...the most sophisticated network of its type ouside North America." Steve Webster, BT ; DDSN Development Team FOREWORD ======== This article shook me up very badly after reading it. At the time I'd been working extensively on a Unix Box in 896, and abusing the fuck out of P****** for global calls in 892. Not only this, but a host of other activities, which are probably nestling on some AMA tape somewhere, waiting to be looked at... <Gulp> . Its not all doom and gloom though - AMA has yet to pinpoint Blue Boxing for some reason, and in so far this would seem to be the only real 'safe' method of putting your calls away for free alongside cellular, I reccomend you start to view it in a new light. Anyway, after that suitably apocalyptic snippet, here we go. ///// ///// ///// ///// ///// ///// ///// ///// ///// ///// INTRODUCTION ============ In 1983, British Telecom identified a major market potential for automatic freephone and premium rate services. An Analogue Network, with extended register translation and call charging facilities overlayed on the PSTN was proposed as an interim solution. The analogue derived services network, consisting of eight fully-interconnected switching nodes, was brought into limited public service in April 1985 and full public service in July 1985. The LinkLine 0800 service permits calling customers to make calls free of charge while callers to LinkLine 0345 service numbers are charged at the local call rate irrespective of distance. The balance of the call charge is billed to the called customer known as the Service Provider (SP). In keeping with its buisness modernisation programmes, British Telecom awarded a contract to AT&T for the supply and installation of a digital derived services network (DDSN), comprising 5ESS-PRX digital switches to be implemented in two distinct phases: Phase 1, which was completed in 1988, involved the supply of eight digital units, utilising CCITT No. 7 common-channel signalling, as replacements for their analogue units (Figure 1). In addition, two new digital units were provided in London. Figure 1 : Digital Derived Services Network Interconnection ┌─────┐ ┌─────┐ │ DLE │ │ DLE │ └──┬──┘ └──┬──┘ │ ╔═══════════════════════════════════════════════╗ │ ┌──┴───┐ ║ SP DIGITAL DERIVED SP ║ ┌───┴──┐ │ DMSU │ ║ ┬ SERVICES NETWORK ┬ ║ │ DMSU │ └──┬───┘ ║ │ │ ║ └───┬──┘ │ ║ │ │ ║ │ │ ║ │ │ ║ │ │ ║ ┌───┴───┐ ┌───┴───┐ ║ │ └────────┤ DDSSC ├───────────────────────────┤ DDSSC ├────────┘ ║ └───┬──┬┘ └┬──┬───┘ ║ ║ │ │ ┌───┘ │ ║ ║ │ └─────────────────────────│───┐ │ ║ ║ │ │ │ │ ║ ║ │ ┌─────────────────────────┘ │ │ ║ ║ ┌───┴──┴┐ ┌┴──┴───┐ ║ ┌────────┤ DDSSC ├───────────────────────────┤ DDSSC ├────────┐ │ ║ └───┬───┘ └───┬───┘ ║ │ │ ║ │ (Only 4 centres │ ║ │ │ ║ │ shown for clarity) │ ║ │ ┌──┴───┐ ║ │ │ ║ ┌───┴──┐ │ AMSU │ ║ ┴ ┴ ║ │ AMSU │ └──┬───┘ ║ SP SP ║ └───┬──┘ │ ║ ║ │ │ ╚═══════════════════════════════════════════════╝ │ ┌──┴──┐ ┌──┴──┐ │ ALE │ │ ALE │ └─────┘ EXISTING PUBLIC SWICHED └─────┘ TELEPHONE NETWORK AMSU Analogue Main Switching Unit ALE Analogue Local Exchange DDSSC Digital Derived Services Switching Centre DLE Digital Local Exchange DMSU Digital Main Switching Unit SP Service Provider Phase 2 makes provision for an advanced freephone service using an intelligent network architecture. INTELLIGENT NETWORK CONCEPT =========================== In a traditional telecommunications network, call control 'intelligence' resides in the call processing software in its switching nodes. One disadvan- tage of this approach for some services is that customer-specific data has to be replicated in each node. As features become more sophisticated, then system complexity increases. In the DDSN Intelligent Network, specialised customer feature and routing information is held centrally in a network database which can be accessed by all switching nodes using dedicated datalinks and common-channel signalling (Figure 2). These signalling datalinks are used to pass requests for call handling information to the database and return instructions to the originating switching node. Figure 2 : Network DataBase Concept ┌──────────┐ │ NETWORK │ /│ DATABASE │\ / └──────────┘ \ ACCESS TO/FROM ALL DDSN SWITCHES / | \ / | \ ┌────────┐ | \ ┌────────┐ │ DDSN ├──────────────────────────────────┤ DDSN │ │ SWITCH │ │ SWITCH │ └───┬──┬─┘ └┬──┬────┘ │ └─────────────────┐┌──────────────────┘ │ │ ┌│┘ │ │ ││ │ │ ┌────────────────┘└───────────────────┐ │ ┌───┴──┴─┐ ┌─┐ ┌┴──┴────┐ │ DDSN ├─────────────────│────────────────┤ DDSN │ │ SWITCH │ │ │ │ SWITCH │ └────────┘ └┬┘ └────────┘ │ │ SPEECH AND SIGNALLING An Intelligent network centralised call management fucntion allows an economical implementation of advanced features, simplifies administration of complex services and assures optimum use of network-wide, rather than switch-based, resources. DDSN INTELLIGENT NETWORK ARCHITECTURE ===================================== Three network elements are concerned with call processing for service providers with advanced features: o Action Control Point (ACP) o Network Control Point (NCP) o Network Services Complex (NSC) The network architecture is illustrated in Figure 3, and the role of each of the elements will become apparent as the call processing aspects are explained. Figure 3 : DDSN Intelligent Network Architecture ┌─────┐ ┌─────┐ ┌─────┐ │ NSC │ │ NSC │ │ NSC │ └─┬─┬─┘ └──┬──┘ └──┬──┘ C T │ │ 7 T ├──────────────┐ ┌────────────┤ N T │ C7NA │ │ C7NA │ A │ │┌─────────────│──┘ │ │ │ ││ └──────────────┐│ ┌┴─┴─────────┴┴─┐ ┌─┴┴────────────┐ ──T──T──T─┤ ├─────────C7NA───────────┤ ├─T───T───T── │ ACP/STEP/HOST ├───T───────T────────T───┤ ACP / STEP │ ───C7BT───┤ ├─────────C7BT───────────┤ ├───C7BT───── (PSTN) └┬─┬─┬───────┬┬┬┘ └┬┬┬───────┬─┬─┬┘ (PSTN) C V C ││└──────────C7BT──────────────┐ C V C │ O │ │└───────VOICE TRUNKS─────────┐│ │ O │ 7 I 7 └────────────C7NA────────────┐││ 7 I 7 │ C │ ┌────────────C7BT────────────│││ │ C │ N E B │┌───────VOICE TRUNKS────────│││ N E B │ │ │ ││┌──────────────────────────│││ │ │ │ A T T │││ │││ A T T │ R │ │││ │││ │ R │ │ U │ │││ │││ │ U │ │ N │ │││ │││ │ N │ │ K │ │││ │││ │ K │ │ S │ │││ │││ │ S │ ┌┴─┴─┴───────┴┴┴┐ ┌┴┴┴───────┴─┴─┴┐ ──T──T──T─┤ ├───T───────T────────T───┤ ├─T───T───T── │ ACP │ │ ACP / HOST │ ───C7BT───┤ ├─────────C7BT───────────┤ ├───C7BT───── (PSTN) └───────────────┘ └────────────┬─┬┘ (PSTN) C T 7 T N T ─T─T─T─ = VOICE TRUNKS A │ │ │ ┌─┴─┴─┐ ACP ACTION CONTROL POINT │ NSC │ STEP SIGNAL TRANSFER AND END POINT └─────┘ C7BT CCITT #7 SIGNALLING (BT) NCP NETWORK CONTROL POINT NSC NETWORK SERVICES COMPLEX C7NA C7 NORTH AMERICAN (Only four switching nodes are shown for simplicity) Action Control Point -------------------- The Action Control Points (ACPs) are the 5ESS-PRX Switching Nodes, which serve as transit and terminating nodes for DDSN traffic. All ACPs are fully interconnected by digital line systems and CCITT #7 (BT) common channel signalling. The CCITT #7 (BT) signalling links are used exclusively for setting up speech paths both within the DDSN and between the DDSN and the PSTN. A Second totally independent common channel signalling network, utilising a proprietary form of #7 signalling (C7 North American), is used for transporting non-circuit related signalling methods between the ACPs and the Network Control Points (NCPs). This network is used only for advanced feature calls. Two of the ACPs have been nominated as a signal transfer and end point (STEP) and funnel the signalling traffic from the remaining ACPs to the NCPs. ACPs load share the C7NA signalling messages across both STEPs in the ACP-to-NCP direction, and the NCPs load share the signalling messages across both STEPs in the reverse direction. Network Control Point --------------------- The Network Control Point (NCP) constitutes the core of the intelligent network and holds the data defining the treatment for specific advanced feature calls. NCPs are always provided in mated pairs. Each NCP consists of a duplex processor, duplicated hard discs for data storage, tape drives and interfaces to the other network elements through a Local Area Network. This network, called the Common Network Interface, consists of the signalling terminals for the C7NA links from the STEP nodes and two peripheral controllers which communicate with the duplex processor. The common network interface ring (Figure 4) is automatically reconfigured under fault conditions to isolate the faulty section. Figure 4 : Common Network Interface Ring ┌──────────┐ ┌──────────┐ │ ACP/STEP │ │ ACP/STEP │ └──┬────┬──┘ ┌──────┐ └──┬────┬──┘ ┌──│────│─┐ ┌────────────────┤ ├──────────<──────┐ │ │ ├─────────┘ │ │ RPCN │ │ │ │ │ │ 7 │ ┌─────────────┤ ├─────────>────┐ │ │ │ │ │ N │ │ └───┬──┘ │ │ │ │ │ │ A ┌┴──┴┐ │ │ │ │ │ │ C └─────┤ LN │ │ │ │ │ │ │ 7 └┬──┬┘ │ │ │ C │ │ N │ │ │ │ │ 7 │ │ A │ │ ┌─────┴─────┐ │ │ N │ │ │ ┌┴──┴┐ │ CENTRAL │ ┌┴──┴┐ A C │ └──────────┤ LN │ │ PROCESSOR │ │ LN ├─────┘ 7 │ └┬──┬┘ └─────┬─────┘ └┬──┬┘ N │ │ │ │ │ │ A │ │ │ │ │ │ │ │ │ │ │ ┌┴──┴┐ │ │ SIGNALLING │ │ │ │ LN ├──────────┘ └─ LINKS │ │ RING 1 ┌───┴──┐ └┬──┬┘ │ └────<────────┤ ├──────────────┘ │ │ │ RPCN │ │ └────────>───────┤ ├─────────────────┘ RING 0 └──────┘ LN LINK NODE RPCN RING PERIPHERAL CONTROLLER NODE Advanced freephone call handling data is duplicated both within and and between each NCP in the mated pair. Call routing queries from the ACPs are balanced between the two NCPs by designating specific dialled codes to each NCP, and the decision on which NCP to query is taken at the ACP where the call entered the DDSN network. Although data is held on both NCPs, the secondary NCP is only accessed if the primary is not available. Under these conditions, the remaining NCP is capable of handling 100% of the load. This architecture virtually guarantees 100% service availability. Automatic network management controls initiated by the NCP maintain the integrity of the intelligent network under overload conditions by sending code gapping messages instructing the ACPs to throttle back on the number of queries being forwarded to the NCP and defining the treatment for failed calls. Network Services Complex ------------------------ The Network services complex (NSC) provides the capability to give callers standard or customised interactive spoken information pertaining to the number called, such as, call prompting, courtesy response and call queing announcements. During or after a call prompting announcement the caller may communicate with the NSC by keying-in appropriate digits on an MF keyphone or keypad. The NSC can collect up to 15 digits which it forwards, via its host ACP, to the NCP via a C7NA common channel signalling link. Initially, two NSCs loaded with the same announcements have been provided in the DDSN intelligent network and are co-located with the NCPs. Each NSC can handle 60 simultaneous calls and provide up to 2000 different announcements which are stored on triplicated moving head discs. In the even of an NSC failure, calls requiring these features are routed to the remaining NSC. The NSC architecture is given in Figure 5. Figure 5 : Network Services Complex Architecture ┌───────────────┐ │ ACP / HOST │ └───┬───────┬───┘ T C │ 7 T N │ A T │ ┌────────────┐ ┌───┴───────┴───┐ │ SIGNALLING │ │ TIME-SLOT ├────────────────────────────────────┤ LINK │ │ INTERCHANGE ├────────────────────┐ │ TERMINAL │ └───┬───────┬───┘ │ └──────┬─────┘ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ └──────────────┐ │ │ │ │ │ ┌──────┴──────┐ │ ┌─────────────────────┬───┴───────────────┤ PROCESSOR │ │ │ │ │ └─────────────┘ ┌─┴──────┴──┐ │ │ │ DATA │ │ │ │ STORAGE │ │ │ │ UNITS │ │ │ └─────┬─────┘ ┌──┴─────┴─┐ ┌───┴───┐ │ TONE │ │ DISCS │ │ RECEIVER │ └───────┘ │ UNITS │ └──────────┘ ADVANCED FEATURES ================= The DDSN Intelligent Network will permit a range of new features to be offered as Advanced LinkLine to LinkLine service providers. These include (Advanced LinkLine feature name is in brackets) : o Time and Day Routing - The routing of calls can be made dependant on the time of day, day of week and week of the year. (TimeLink / DayLink) o Call Allocator - This provides the capability to route incoming calls proportionally to a number of service provider destinations and / or announcements. (DistributionLink) o Call Queuing - This provides queues for calls at the originating ACP when all available lines to a service provider destination are engaged. An announcement informs the caller of the call status. (QueueLink) o Call Barring - This feature allows service providers to define the treatment of a particular Advanced LinkLine number based on where the call origniated in the PSTN. (AreaLink) o Alternative Destination on Busy - When a busy condition is encountered and no queuing is define, an alternative destination may be chosen automatically. (BusyLink) o Call Prompter - Announcements will prompt callers to enter digits on their telephone set in order to realise caller interactive routing. (SelectLink) o Courtesy Response - If no destination can be reached, for example, due to an unattended office, a pre-defined standard or customised announcement may be played. (CourtesyLink) o Command Routing - This feature allows the service provider to instruct British Telecom to redirect calls to a preset alternate set of destinations. This is intended for emergency and other contingency situations. (CommandLink) CALL ROUTING PLANS ================== The true power of intelligent network call processing is not solely its list of advanced features, but combinations of the feature set which can be defined to meet a service provider's own unique telecommunications needs and, consequently, buisness requirements. An example of a simple call routing plan is shown in Figure 6. The data defining the call treatment(s) for a service provider are held in the NCP database in a service provider record. Figure 6 : Combining service features DIAL PULSE ▄▄▄▄▄▄▄▄ NO RESPONSE ▀ ▄▄▄▄ ▀ ┌───────────────────────█░░█ │ OPERATOR SELECTLINK │ ╔════════════════════════════════╗ │ ║ "KEY 1 FOR COMMERCIAL LOANS, ║ │ ▄▄▄▄▄▄▄▄ ║ KEY 2 FOR CONSUMER LOANS..." ║ │ DIGIT #1 ▀ ▄▄▄▄ ▀ ╚════════════════════════════╤═══╝ ├───────────────────────█░░█ │ COMMERCIAL └ ─ │ LOANS │ │ DAYLINK AREALINK ┌┴──┴────┐ ▄▄▄▄▄▄▄▄ ┌──────┐ MON - FRI ┌───────┐ LONDON │ WHAT │ DIGIT #2 ▀ ▄▄▄▄ ▀ ───>───┤ WHAT ├───────────┤ WHAT ├────────┤ MF ├──────────────────█░░█ │ DAY? │ │ AREA? │ │ DIGIT? │ CONSUMER └──┬───┘ └──┬────┘ └───┬────┘ LOANS │ │ │ │ │ │ │ │ │ ▄▄▄▄▄▄▄▄ │ │ │ DIGIT #3 ▀ ▄▄▄▄ ▀ │ │ ALL └───────────────────────█░░█ │ │ OTHER OTHER │ │ │ │ │ │ │ │ ▄▄▄▄▄▄▄▄ │ │ ▀ ▄▄▄▄ ▀ │ └─────────────────────────────────────────█░░█ │ BRISTOL │ BRANCH │ │ SATURDAY │ AND ╔══════════════════╗ │ SUNDAY ║ "ALL OFFICES ARE ║ └──────────────────╢ CLOSED FOR THE ║ ║ WEEKEND..." ║ ╚══════════════════╝ COURTESYLINK SERVICE ADMINISTRATION ====================== Service Administration for Advanced LinkLine features is handled by the network subscriber transaction, administration and recording system (NETSTAR), which has on-line access to the NCPs. NETSTAR provides user friendly access to the NCP advanced feature database to modify, create or delete service provider call routing plans via dedicated or dialup/dialback links to VDUs. An NCP can have only one active call routing plan for any service provider number, but additional plans may be prepared and held in NETSTAR for transmission to, and activation at, the NCP when required. NETSTAR holds security backup copies of all call routing plans and NCP operating parameters. CALL PROCESSING =============== Derivation of the Calling Subscriber Geography (CSG) ---------------------------------------------------- All 0800 and 0345 calls are routed via a DMSU to a DDSN action control point (ACP) (Figure 7). During Call set-up, the ACP requests additional set-up information to be sent via the C7BT Link. This cause the calling line identity (CLI) to be forwarded from the first exchange in the call path with C7BT signalling. Figure 7 : Access to the Digital Derived Services Network PSTN DDSN ┌──────────────┴────────────────┐┌──────────────────────┴─────────────────────┐ ┌───────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ │ DLE ├────C7BT───┤ ├────C7BT───┤ ├────C7BT───┤ │ │ or │ │ DMSU │ │ 5ESS-PRX │ │ 5ESS-PRX │ │ E-ALE ├─T─T─T─T─T─┤ ├─T─T─T─T─T─┤ (ACP) ├─T─T─T─T─T─┤ (ACP) │ └───────┘ ┌─────────┤ │ │ │ │ │ ┌───────┐ │ └──────────┘ └────┬─────┘ └────┬─────┘ │ AMSU/ ├─┘ │ │ │ +ALE │ │ │ └───────┘ │ │ ┴ ┴ SP SP * ALE may be via a digital concentrator centre exchange E-ALE : Enhanced analogue Local Exchange (C7BT signalling capability) If a call is originated from a local exchange with C7BT signalling, a full calling line identity (FCLI) is returned to the ACP. The FCLI includes the caller's national number group (NNG) code, or all figure numbering (AFN) code in the case of a director area. If the call is originated from an analogue local exchange (ALE), then a partial calling line identity (PCLI) is derived by the first digital exchange in the call path. This will normally be a DMSU, but in cases where an ALE is parented on a digital concentrator centre exchange (DCCE), the DCCE generates the PCLI. A PCLI must comprise sufficient information to uniquely identify the digital entry point to the PSTN used by that ALE. This information includes the region, area and unit identity portions of the network nodal identity plus the telephony process number and route numbers used by the call processing software of the digital exchange. Whe a PCLI or FCLI is received by a DDSN action control point, the call processing software searches through a set of look-up tables for a comparison with the CLI sent. This search will result in the calling subscriber geography (CSG) being identified. Figures 8 and 9 illustrate the CLI and CSG derivation process. Figure 8 : CLI derivation ┌───────┐ ┌────────────┐ ┌────────────┐ ┌────────────┐ │ DLE ├─<─────────┐ DMSU │ │ 5ESS-PRX ├─────────┤ 5ESS-PRX │ │ E-ALE │ │ │ │ │ (ACP) │ │ (ACP) │ └───────┘ │ │ │ │ │ │ │ │ ├────────────<───────────┐ │ │ │ │ │ │ │ │ │ │ │ ┌───────┐ │ │ │ │ REQUEST │ │ │ │ ALE │ ?─────────┘ │ │ CLI │ │ │ └───────┘ └────────────┘ └────────────┘ └────────────┘ Figure 9 : CSG derivation ┌───────┐ ┌────────────┐ ┌────────────┐ ┌────────────┐ │ FCLI ───>─────────┐ DMSU │ │ 5ESS-PRX ├─────────┤ 5ESS-PRX │ │ DLE │ │ │ │ │ (ACP) │ │ (ACP) │ └───────┘ │ │ │ FCLI │ │ │ │ │ ├────────────>────────CLI/CSG │ │ │ │ │ │ PCLI │ TABLES │ │ │ ┌───────┐ │ │ │ │ │ │ │ │ │ ALE │PCLI─>─────┘ │ │ CSG │ │ │ └───────┘ └────────────┘ └────────────┘ └────────────┘ Global Title Translation ------------------------ Call processing for service providers with basic features is handled within the DDSN switching nodes. To differentiate between calls to SPs with advanced and basic features, the ACP checks for the existence of a translation for the number dialled. If a translation exists, the call is routed to the specified network termination. If the translation does not exist, call handling instructions are returned from the NCP database in response to a query message from the originating ACP. A number of query messages are neccesary for some types of call; the initial query is therefore termed QRY1. The process is illustrated in Figures 10 and 11. Figure 10 : DDSN ┌─────────────────┐ Intelligent Network call │ INCOMING CALL │ Processing (Call not │ FROM PSTN │ requiring NSC and no │ DIGITS RECEIVED │ network controls active) │ AT ORIGINATING │ ( OR (0) 345 DEFGHJ ) │ ACP │ │ (0)800 345800 │ └───────┬─────────┘ GTT : GLOBAL ┌───────┴─────────┐ TITLE │ ACP REQUESTS │ TRANSLATION │ ADDITIONAL │ ( SEE FIGURE 8 ) │ SET-UP INFO │ │ VIA C7BT LINK │ └───────┬─────────┘ ┌───────┴─────────┐ │ FCLI OR PCLI │ ( SEE FIGURE 8 ) │ FORWARDED TO │ ┌─────────────────┐ │ ACP │ │ ORIGINATING ACP │ └───────┬─────────┘ │ DEALS. │ ┌───────┴─────────┐ YES │ CALL SETUP │ │ TRANSLATION HELD├──────>─────┤ NORMALLY USING │ │ AT ACP │ │ C7BT LINK │ └───────┬─────────┘ └─────────────────┘ NO ┌────────────────┐ NO ┌───────┴─────────┐ YES │ SEND QRY1 │ ┌───────────<───┤ IS 0800-345 ├───>────────┤ MESSAGE TO NCP │ │ │ DEFINED IN GTT? │ │ VIA C7NA │ │ └─────────────────┘ │ LINK │ ┌─────────────────┐ └───────┬────────┘ │ │ SEND A FINAL │ ┌───────┴────────┐ │ │ TREATMENT OF │ NO │ IS A PLAN HELD │ ├───────────────┤'VACANT CODE' TO ├─────<──────┤ AT NCP FOR 800 │ │ │ ACP │ │ 345800? │ │ └─────────────────┘ └───────┬────────┘ │ YES ┌──────────┴──────────┐ │ │ NCP DETERMINES │ │ │ CALL TREATMENT. │ ┌──────────┴────────────────┐ │ BILLING AND ROUTING │ │ 'VACANT CODE' │ │ DETAILS TO ACP │ │ NUMBER UNOBTAINABLE TONE │ │ VIA C7NA │ │ RETURNED │ └──────────┬──────────┘ └───────────────────────────┘ ┌──────────┴──────────┐ │ ORIGINATING NCP │ │ SETS UP CALL USING │ │ C7BT LINK │ └─────────────────────┘ Figure 11 : ACP Communication with NCP ┌─────────────┐ │ (ACP 1) │ │ TRANSLATION │ │ NOT HELD │ │ ─ │ │ │ ┌──────────────────┐ │ 0800 DEF │ │ NCP │ │ IN GTT │ ├────┬─────────────┤ │ = │ ┌─────────────┐ │ C │ ┌─────────┐│ │ │ │ (ACP 2) ┌───┤ │ N │ │ SP ││ │ SEND QRY1 ──>───C7NA───>─────────────┤ S ├─>─C7NA─>───┤ I ├>─┤ RECORD ││ │ TO NCP │ │ │ T │ │ R │ └────┬────┘│ ├─────────────┤ │ │ E │ │ I │ │ │ │ BILLING ──<───C7NA───<─────────────┤ P ├─<─C7NA─<───┤ N ├<──────┘ │ │ INSTRUCTIONS│ └─────────┴───┘ │ G │ PROCESSOR │ │ + │ ┌─────────────┐ └────┴─────────────┘ │ ROUTE │ │ (ACP n) │ │ MESSAGE │ │ CALL SET-UP │ │ OR │ │COMPLETED TO │ │ FINAL ───────C7BT───────┤ SERVICE ├──────────── SP │ TREATMENT │ │ PROVIDER │ └─────────────┘ └─────────────┘ ACP 1 = ACP receiving call from PSTN ACP 2 = ACP with directly connected NCP ACP n = The ACP on which the SP is terminated The QRY1 message includes: a) 10 digit dialled number, which excludes any leading 0 but includes a trailing 0 as padding if only 9 digits long. b) Calling subscriber geography (CSG). c) The ACP which originated the query. This is used to reference a table in the NCP which defines the capabilities of the ACP,; for example, whether it has an NSC. d) The destination of the query. The route message includes a network code of up to 10 digits which is used by the ACP to route the call to its destination. This is normally a service provider (SP) line, but can be an NSC announcement. A final treatment command is sent to the ACP when the NCP cannot route a call normally. The final treatment command results in either a tone or an announcement being returned to the caller. Calls Requiring an NSC ---------------------- As not all ACPs are hosts to an NSC, a call which requires an NSC at some point during the call treatment must be setup in two parts. After the QRY1 Message, the call is routed to an ACP/HOST, using C7BT in the normal manner, where a voice trunk to the NSC is allocated. This action is termed a 'service assist' if the NSC is required as intermediate step in the call treatment (SelectLink) or a 'hand-off' if the NSC is required to play an announcement as the final routing conclusion (CourtesyLink). During a service assist or a hand-off, the ACP/HOST then queries the NCP a second time (QRY2) with details of the NCP and call number used for the QRY1 message. The call treatment now continues with a list of commands being sent from the NCP to the NSC. This could be to play an announcement and collect digits from the caller. NCP/NSC communication takes place via the C7NA links with any digits collected being returned to the NCP to determine the final disposition of the call. CALL LOGGING ============ In response to a query message from the originating ACP, the NCP returns a billing command instructing the ACP what details to record; the ACP acknowledges receipt of the instructions to the NCP. On answer, the terminating exchange sends a message to the originating ACP giving either 'answer / no charge' or 'answer / charge' depending on which LinkLine (0800/0345) is defined. On Call termination, the ACP records the details of the call in an automatic message accounting (AMA) record. The originating ACP normally controls the call and is responsible for generating an automatic message accounting record. These records are periodically polled by an on-line data collector which validates them before passing them to an off-line charge raising system which calculates call charges in preparation for the production of the service provider's bill. Where a 'hand-off' has occurred, the ACP/HOST takes over control of the call for supervisory and logging purposes. OPERATIONS AND MAINTENNANCE =========================== The Multi-Function Operations System (MFOS) is central to the operations and maintennance fucntions for the DDSN intelligent network. These functions include: o On-line access to the ACPs/NCPs/NSCs o Alarm Collection and Monitoring o Collection and analysis of traffic data o Real time Network management Connection between the multi-function operations system processors, the network elements and the users is achieved using a virtual circuit switch for flexibility. ///// ///// ///// ///// ///// ///// ///// ///// ///// /////