Current ANSI-41 Interface Reference Points in C#.NET

Decoding Quick Response Code in C#.NET Current ANSI-41 Interface Reference Points

Table 43 shows the interface reference points specified in the ANSI-41 network reference model The Z interface was added to support the NPDB This interface represents the signaling communications required to provide the number portability functions The D1, N1, and X interfaces were added to support the OTASP These interfaces represent the signaling communications required to provide the OTASP functions The Pi interface was added to support signaling between the wireless network and a PPDN to support wireless packet-switched data services In reality, PPDN interconnectivity typically requires an IWF, although it may not be necessary to support packet-switched functions This is

Downloaded from Digital Engineering Library @ McGraw-Hill (wwwdigitalengineeringlibrarycom) Copyright 2004 The McGraw-Hill Companies All rights reserved Any use is subject to the Terms of Use as given at the website

Part 1:

why the IWF uses the same Pi interface as direct connectivity between the PPDN and MSC The IWF is shown with a separate connection to the PPDN to enable it to connect to other network elements beside the MSC In fact, the IWF is defined to enable connectivity to any wireless network element The Pi interface is not standardized, but was added to show the potential future need to standardize this interface and to acknowledge existing vendor solutions that provide implementationdependent solutions to this function today TABLE 43 Current Interface Reference Points in ANSI-41 and the Most Current Standard Where They Are Addressed (Interfaces in Bold Represent Interfaces Standardized in ANSI-41)

Interface A interface Ai interface B interface C interface D interface Di interface D1 interface E interface F interface G interface H interface M1 interface M2 interface M3 interface N interface N1 interface Pi interface Q interface Um interface1 Functional Entities Using the Interface BS MSC MSC PSTN MSC VLR MSC HLR HLR VLR MSC ISDN VLR OTAF MSC MSC MSC EIR VLR VLR HLR AC MC SME MC MC SME SME MC HLR HLR OTAF MSC PPDN, PPDN IWF MC MSC MS BS Where Addressed (Most Current Standard) ANSI/TIA/EIA-634 ANSI/TIA/EIA-93 ANSI-41-E ANSI-41-E ANSI-41-E ANSI/TIA/EIA-93 TIA/EIA/IS-725 ANSI-41-E not standardized not standardized ANSI-41-E ANSI-41-E ANSI-41-E ANSI-41-E ANSI-41-E TIA/EIA/IS-725 not standardized ANSI-41-E ANSI/TIA/EIA-691, ANSI/TIA/EIA-95, ANSI/TIA/EIA-136 not standardized TIA/EIA/IS-756

Note that other radio interface standards exist, but these specifications are most representative of the technology supported by ANSI-41

Downloaded from Digital Engineering Library @ McGraw-Hill (wwwdigitalengineeringlibrarycom) Copyright 2004 The McGraw-Hill Companies All rights reserved Any use is subject to the Terms of Use as given at the website

4:

The current ANSI-41 network reference model also supports wireless intelligent network (WIN) functionality and is specified in TIA/EIA TSB100 The following functional entities were added to support WIN:

Intelligent peripheral (IP, not to be confused with Internet protocol) Service control point (SCP) Service node (SN)

Note that these functional entities were originally specified in the Bellcore Advanced Intelligent Network (AIN) specification for wire-line intelligent network (IN) functionality in the late 1980s These functional entities provide the distributed network intelligence required to support the IN call models, trigger points, and call treatment to provide new and efficient services to subscribers Since WIN functionality requires many of the same characteristics of the wire-line IN network reference model, it made sense to include these same functional entities in the ANSI-41 network reference model Figure 48 shows the additions to the ANSI-41 network reference model to support WIN capabilities Although WIN functionality is explicitly specified in TIA/EIA/IS-771, and not ANSI-41, it is worth mentioning due to its close relationship to, and involvement in, the ANSI-41-based MSC and HLR Intelligent Peripheral The intelligent peripheral (IP) is a functional entity that performs special resource management functions required to treat a call in a specific way For example, a voice-mail system can be considered an IP, as are systems that provide voice announcements, interactive voice and response systems, and digit-collection systems IP is a very broad term, so a wide variety of services and devices, used to manage the resources to treat certain calls in special ways, may be considered intelligent peripherals in this model Service Control Point The service control point (SCP), in the broadest sense, is a functional entity that performs real-time database and transaction processing

Downloaded from Digital Engineering Library @ McGraw-Hill (wwwdigitalengineeringlibrarycom) Copyright 2004 The McGraw-Hill Companies All rights reserved Any use is subject to the Terms of Use as given at the website