Patent Document

BACKGROUND OF THE INVENTION 
     1. Field of the Invention 
     This invention relates generally to telecommunications and more specifically, to switches of a telecommunications network that transport and process the Charge Number, Calling Party Number, and Presentation Indicator elements of Automatic Number Identification information to deliver Caller ID information across the network. 
     2. Related Art 
     A typical telecommunications network comprises multiple telecommunication switches located throughout a geographical area. FIG. 1 illustrates such a typical telecommunications environment. An originating party 102 utilizes a telephone 104 to place a call. The call is routed to an origination switch 108 on a transmission line referred to as the originating trunk. The originating trunk is one of many transmission lines coming into the origination switch 108 from the same geographical location as the telephone 104. These transmission lines including the originating trunk is referred to as an origination trunk group 106. After processing an incoming call, the switch transmits the call to a destination switch 114. The call is transmitted over a transmission line (referred to as the intermatching trunk) to the destination switch 114. Similar to the originating trunk, a terminating trunk 110 is one of a group of trunks connecting the destination switch 114 to a local exchange carrier (LEC), public branch exchange (PBX) or a caller identification (ID) box 116, which is, in turn, connected to a receiving telephone 118. Thus the Caller ID information is available before the first ring and a receiving party 120 can know the telephone number of the originating party 102 before actually picking up the telephone receiver to answer the incoming call. 
     At times, the originating party 102 may not want the receiving party to have the Caller ID information for privacy reasons. Therefore the origination switch 108 must transport a Presentation Indicator (PI) across the network to the destination switch 114. The PI indicates whether the originating party&#39;s 120 telephone number may be presented, via Caller ID, to the receiving party 120 (&#34;Address Presentation Allowed&#34;) or must remain private (&#34;Address Presentation Restricted&#34;). The PI is defaulted to the &#34;Address Presentation Allowed&#34; setting, but may be set to &#34;Address Presentation Restricted&#34; by the originating party 102 before placing the call. This is usually done by dialing a certain prefix (e.g., &#34;*67&#34;) before placing the call. 
     Automatic Number Identification (ANI) information is encoded on every incoming call, which box 116 can decipher. ANI information is comprised of the Calling Party Number (CgPN) parameter, the Charge Number (ChgN) parameter, and PI information. The CgPN is the information that identifies the number of the originating party and the ChgN is the actual telephone number charged for that particular phone call. In normal home dialing, these two parameters are identical. However, when dealing with a Private Branch Exchange (PBX (i.e., several business lines in a building), the ChgN may be the owner of the services, and thus not the same as the CgPN who is the subscriber of the services behind the PBX. 
     There are many switch and trunk group types, each having their own configurations and protocols with different message formats for transmitting switch signaling and voice data. Types include: (a) Signaling System Seven/Integrated Services Digital Network User Part (SS7/ISUP) which is a phone out-of-band signaling protocol system that allows a greater bandwidth by separating the phone signaling (supervising, alerting, and addressing functions) and voice data; (b) Integrated Services Digital Network/ Primary Rate Interface (ISDN/PRI), which is an out-of-band 1,544,000 bits/sec network that combines voice, data, signaling, etc., and operates on a T-1 line; and (c) Per Trunk Signaling (PTS) Inband which is a tone signaling system that passes within the same band as voice data. The origination trunk group 106 and termination trunk group 110 may be the same or different trunk types, thus effecting Caller ID delivery. 
     The different protocols for the above mentioned trunk group types are well known in the art. For example, the SS7/ISUP trunk type uses an Initial Address Message (IAM) to send the ChgN, CgPN, and the PI as parameters in the message from the origination switch 108 to the termination switch 114. The format of this message is defined in American National Standards Institute, Inc. (ANSI) ISUP Issue 1, T1.113-1988 (which is incorporated herein by reference). A typical IAM format is shown below in Table 1: 
     
                       TABLE 1______________________________________Parameter             Type   Length______________________________________Message Type          F      1Nature of Connection Indicators                 F      1Forward Call Indicators                 F      2Calling Party&#39;s Category                 F      1User Service Information                 V      3-nCalled Party Number   V       2-11Access Transport      O      3-nBusiness Group        O      9-nCall Reference        O      8Calling Party Number  O       5-12Charge Number         O       3-14Circuit Assignment Map                 O      6Generic Address       O       6-13Generic Digits        O      4-nForward Call Special Information                 O      3Multiple Business Group                 O      9Network Specific Facility                 O      3-nOperator Information  O      9-nSoftware Indicator    O      3Supplementary Line Information                 O      3-nNetwork Transport     O      5-nOriginating Line Information                 O      3Redirection Information                 O      3-4Transit Network Selection                 O      5-6______________________________________ 
    
     A typical CgPN parameter, which includes the Presentation Indicator as a subparameter, format is shown below in Table 2: 
     
                       TABLE 2______________________________________Byte  7      6      5     4     3    2    1    0______________________________________1     Parity Nature of Address Indicator2     Spare  Numbering Plan PI      SCREENING3     D2                D14     D4                D3:     :                 :n-1   D(m-2)            D(m-3)n     Dm (or filler)    D(m-1)______________________________________ 
    
     The CgPN parameter includes some of the following data elements: 
     Parity--This field is a parity indicator which shall be coded as follows: 
     
         ______________________________________0              Even number of Dm digits;1              Odd number of Dm digits;______________________________________ 
    
     Nature of Address Indicator--this field defines the type of data identifying the call originator; 
     PI--the Address Presentation Restricted Indicator specifies whether the originating address may be disclosed or must be kept confidential. Coding is as follows: 
     
         ______________________________________00         Address presentation allowed (default);01         Address presentation restricted;10         Address unavailable due to interworking;11         Spare/Reserved;______________________________________ 
    
     D1 to Dm--These subfields are digits representing the value of the calling party number type specified in the indicator field. Each digit (0 to 9) occupies 4 bits, encoded in BCD format. 
     The typical Charge Number Parameter format is shown below in Table 3: 
     
                       TABLE 3______________________________________Byte  7       6       5    4     3    2    1    0______________________________________1     Parity  Nature of Address Indicator2     Spare   Numbering Plan Reserved3     D2                 D14     D4                 D3:     :                  :n-1   D(m-2)             D(m-3)n     Dm (or filler)     D(m-1)______________________________________ 
    
     Similarly, the ISDN/PRI trunk group type uses a SETUP message containing the appropriate data elements to delivery ANI information. Also, PTS/Inband trunk types implement a variety of protocols to delivery of ANI information. These vary according to manufacturer and are also well known in the art. 
     Current implementations for Caller ID delivery map the ChgN parameter to the CgPN parameter and deliver that information to the receiving party 120 as the CgPN. This mapping is done at the origination switch 108 and thus limits the information available at the destination switch 114 and consequently to the receiving party 120. 
     The Federal Communications Commission (FCC) has recently required that Local Exchange Carriers (LECs) (i.e., local telephone service companies) and Interexchange Carriers (IXCs) (i.e., long distance telephone service companies) to transmit the CgPN and honor the PI, where the information is available, for all SS7/ISUP calls. Therefore there is a need to comply with these orders but still provide the ability to map the ChgN to the CgPN. Furthermore, there is a need, to allow different telephone subscribers to choose different Caller ID delivery options based on the data available, the PI, and the origination/termination trunk group types without impacting current implementations for billing and switch call processing. 
     SUMMARY OF THE INVENTION 
     The present invention is directed to a system and method for transporting the Calling Party Number, Charge Number, and Presentation Indicator elements of Automatic Number Identification across a telecommunications network. The system receives a Presentation Indicator along with a Charge Number and/or Calling Party number from an origination trunk group. The Presentation Indicator is set by the originating (calling) party at the origination trunk group. The availability of the Charge Number and/or the Calling Party Number is a function of the type of origination trunk group. A message is then formatted according to the specific type of termination trunk group, the Presentation Indicator set by the originating party, and the termination trunk group parameter delivery options selected by the receiving party (subscriber). Thus, Caller ID information can be delivered to the receiving party in their subscribed format. 
     The present invention maintains the flexibility to map the Charge Number to the Calling Party Number and adds additional flexibility when delivering Calling Party Number and Charge Number information to the termination trunk group. This flexibility includes allowing the termination trunk subscriber to selectively honor or ignore the Presentation Indicator, providing conditional Charge Number delivery, and providing conditional Calling Party Number delivery. New parameters added to the termination trunk group screening tables allow the present invention to provide the delivery option functionality. The system and the corresponding method performs the above without any impact to telephone call billing systems or any other switch call processing and complies with current FCC orders to deliver the Calling Party Number and honor the Presentation Indicator on SS7/ISUP calls when available. 
     Further features and advantages of the invention, as well as the structure and operation of various embodiments of the invention, are described in detail below with reference to the accompanying diagrams. 
    
    
     BRIEF DESCRIPTION OF THE FIGURES 
     The present invention will be described with reference to the accompanying drawings, wherein: 
     FIG. 1. is a block diagram of a conventional telecommunications environment; 
     FIG. 2. is a block diagram of an exemplary computer system useful for implementing the present invention; 
     FIG. 3. is a flowchart representing the overall preferred operation of the present invention; 
     FIG. 4. is a flowchart representing the preferred operation of delivery option A of the present invention and is a continuation of FIG. 3; 
     FIG. 5. is a flowchart representing the preferred operation of delivery option B of the present invention and is a continuation of FIG. 3; 
     FIG. 6. is a flowchart representing the preferred operation of delivery option C of the present invention and is a continuation of FIG. 3; 
     FIG. 7. is a flowchart representing the preferred operation of delivery option D of the present invention and is a continuation of FIG. 3; and 
     FIG. 8. is a flowchart representing the preferred operation of delivery option E of the present invention and is a continuation of FIG. 3. 
    
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS 
     Overview 
     The present invention is directed to a system and method for enabling a telecommunications network to transport the Charge Number (ChgN) and Calling Party Number (CgPN) parameters of the Automatic Number Identification (ANI) information, when available, and the Presentation Indicator (PI) from an origination trunk group to a termination trunk group. The present invention allows for mapping of the ChgN to the CgPN at the termination trunk group and subscriber selected Caller ID delivery options. These termination trunk group options include: (a) Honor the PI for CgPN delivery; (b) Deliver the CgPN regardless of the PI; (c) Prevent CgPN delivery in all cases; (d) Conditional ChgN Delivery; and (e) Conditional CgPN Delivery. These options are stored in the destination switch 114 database. Furthermore the PI can be set to &#34;Address Presentation Allowed&#34; or &#34;Address Presentation Restricted.&#34; The present invention&#39;s system and method for delivering Caller ID information based on the ANI parameters from the different trunk group types, the setting of the PI, and the subscriber delivery options is described herein. 
     The chosen embodiment of the present invention is computer software executing within a computer system. FIG. 2 shows an exemplary computer system. The computer system 202 includes one or more processors, such as a processor 204. The processor 204 is connected to a communication bus 206. 
     The computer system 202 also includes a main memory 208, preferably random access memory (RAM, and a secondary memory 210. The secondary memory 210 includes, for example, a hard disk drive 214 and/or a removable storage drive 216, representing a floppy disk drive, a magnetic tape drive, a compact disk drive, etc. The removable storage drive 216 reads from and/or writes to a removable storage unit 218 in a well known manner. 
     Removable storage unit 218, also called a program storage device or a computer program product, represents a floppy disk magnetic tape, compact disk etc. The removable storage unit 218 includes a computer usable storage medium having stored therein computer software and/or data. 
     Computer programs (also called computer control logic) are stored in main memory 208 and/or the secondary memory 210. Such computer programs, when executed, enable the computer system 202 to perform the functions of the present invention as discussed herein. In particular, the computer programs, when executed, enable the processor 204 to perform the functions of the present invention. Accordingly, such computer programs represent controllers of the computer system 202. 
     In another embodiment, the invention is directed to a computer program product comprising a computer readable medium having control logic (computer software) stored therein. The control logic, when executed by the processor 204, causes the processor 204 to perform the functions of the invention as described herein. 
     In another embodiment, the invention is implemented primarily in hardware using, for example, a hardware state machine. Implementation of the hardware state machine so as to perform the functions described herein will be apparent to persons skilled in the relevant arts. 
     Implementation of the Invention 
     FIG. 3, is a switch call processor representing the overall preferred operation of the present invention within the switch call processing environment 130. Switch call processor 302 begins at step 304 with control passing immediately to step 312. In step 312 a screening table for the termination trunk group is referenced to determine the appropriate information the origination trunk group should place in its message to the termination trunk group. If the termination trunk group screening table indicates that mapping the ChgN to the CgPN should be done, as in conventional implementations, then step 314 is performed, which maps the ChgN to the CgPN, formulates a message (in an appropriate format for the termination trunk group 110 type) with the ChgN coded as the CgPN, sets the PI to &#34;Address Presentation Allowed,&#34; and transports the message to the termination trunk group. 
     In step 316, the destination switch 114 does not screen the PI and then step 318 determines termination trunk group is a SS7/ISUP type. If so, step 320 is performed to consult the SS7/ISUP attribute table to gather information to complete the call and ANI delivery. If the termination trunk group is not a SS7/ISUP type, step 322 determines if the destination switch 114 is a PRI/ISDN type. If so, step 324 is performed to consult the PRI/ISDN attribute table to gather information to complete the call and ANI delivery. If the destination switch 114 is not a PRI/ISDN type, step 328 determines if the destination switch 114 is a PTS/Inband type. If so, step 328 is performed to consult the PTS/Inband attribute to gather information to complete the call and ANI delivery. If the destination switch 114 is not a PTS/Inband type, step 330 simply completes the call because ANI delivery is not applicable for trunk group types other than the ISUP/SS7, PRI/ISDN, or PTS/Inband types. 
     Referring again to step 312, if the termination trunk group screening table indicates that mapping the ChgN to the CgPN should not be done as in current implementations, then step 340 is performed, which determines if the termination trunk group parameter, set according to the receiving party 120 subscription selection, is set to an option A--&#34;Honor the PI for CgPN delivery,&#34; according to the first option feature of the present invention. If so, step 342 is performed as described below. If the termination trunk group parameter is not set to delivery option A, step 350 determines if it is set to delivery option B--&#34;Deliver the CgPN regardless of the PI,&#34; according to the second option feature of the present invention. If so, step 352 is performed as described below. If the termination trunk group parameter is not set to delivery option B, step 360 determines if it is set to delivery option C--&#34;Prevent CAP delivery in all cases,&#34; according to the third option feature of the present invention. If so, step 362 is performed as described below. If the termination trunk parameter is not set to delivery option C, step 370 determines if it is set to delivery option D--&#34;Conditional ChgN Delivery,&#34; according to the fourth option feature of the present invention. If so, step 372 is performed as described below. If the termination trunk group parameter is not set to option D, step 380 determines if it is set to E--&#34;Conditional CgPN Delivery,&#34; according to the fifth option feature of the present invention. If so, step 382 is performed as described below. If step 380 determines that the termination trunk group parameter is not set to delivery option E, then none of the delivery options were selected and the switch will use existing processing beginning with step 316 and progressing as described above. 
     As stated previously, the formation of the message to be transported to the termination trunk group is dependent on the termination trunk group type. Similarly, the ANI information will depend on the delivery option selected by the receiving party 120 and the PI set by the originating party 102. Below is a description of the continuation of switch call processing for options A (step 342), B (step 352), C (step 362), D (step 372), and E (step 382) as illustrated by FIGS. 4, 5, 6, 7 and 8 respectively, in accordance with the present invention. 
     Option A--&#34;Honor the PI for CgPN Delivery&#34; 
     The switch call processor 302, having determined at step 340 that delivery option A was selected by the receiving party 120 subscriber, proceeds to step 342. Referring to FIG. 4, step 342 passes control to step 410. Step 410 determines whether the originating party 102 set the PI to &#34;Address Presentation Allowed.&#34; If so, step 318 determines if the termination trunk group is a SS7/ISUP type. If so, step 320 is performed to consult the SS7/ISUP attribute table to formulate an IAM (Initial Address Message) to the destination switch 114 with the CgPN parameter included as received by the origination switch 108. Then step 430 delivers the message to the destination switch 114. If the termination trunk group is not a SS7/ISUP type, step 322 determines if the destination switch 114 is a PRI/ISDN type. If so, step 324 is performed to consult the PRI/ISDN attribute table to formulate a SETUP message to the destination switch 114 with the CgPN included. Then step 430 delivers the message to the destination switch 114. If the termination trunk group is not a PRI/ISDN type, step 326 determines if the termination trunk group is a PTS/Inband type. If so, step 328 is performed to consult the PTS/Inband attribute to formulate a message, following the appropriate protocol for that trunk group, to the destination switch 114 with the CgPN included. Then step 430 delivers the message as ANI information to the destination switch 114. If the termination trunk group is not a PTS/Inband type, step 330 simply completes the call because ANI delivery is not applicable for trunk group types other than ISUP/SS7, PRI/ISDN, or PTS/Inband types. 
     If step 410 determines the originating party 102 did not set the PI to &#34;Address Presentation Allowed,&#34; step 420 determines if the PI is set to &#34;Address Presentation Restricted.&#34; If so, switch call processor 302 again proceeds to step 318. Step 318 determines if the termination trunk group is a SS7/ISUP type. If so, step 320 is performed to consult the SS7/ISUP attribute table to formulate an IAM to the destination switch 114 with the CgPN parameter included as received by the origination switch 108 but with the Calling Party number itself (D1-Dm) excluded. See Table 2. Then step 440 delivers the message to the destination switch 114. If the termination trunk group is not a SS7/ISUP type, step 322 determines if the termination trunk group is a PRI/ISDN type. If so, step 324 is performed to consult the PRI/ISDN attribute table to formulate a SETUP message to the destination switch 114 with the CgPN parameter excluded. Then step 440 delivers the message to the destination switch 114. If the termination trunk group is not a PRI/ISDN type, step 326 determines if the termination trunk group is a PTS/Inband type. If so, step 328 is performed to consult the PTS/Inband attribute to formulate a message, following the appropriate protocol for that trunk group, to the destination switch 114 with the CgPN excluded. Then step 440 delivers the message as ANI information to the destination switch 114. If the termination trunk group is not a PTS/Inband type, step 330 simply completes the call because ANI delivery is not applicable for trunk group types other than ISUP/SS7, PRI/ISDN, or PTS/Inband types. 
     If step 420 determines the originating party 102 did not set the PI to &#34;Address Presentation Restricted,&#34; the switch call processor 302, in step 450, will formulate an IAM to the destination switch 114 with the CgPN parameter as received from the origination switch 108 for a SS7/ISUP termination trunk group type; formulate a SETUP message to the destination switch 114 with the appropriate Data Elements for a PRI/ISDN termination trunk group type; or follow the appropriate protocol for the termination trunk group type and generate a message with the ChgN included for a PTS/Inband termination trunk group type. 
     Option B--&#34;Deliver the CgPN Regardless of the PI&#34; 
     The switch call processor 302, having determined at step 350 that delivery option B was selected by the receiving party 120 subscriber, proceeds to step 352. Referring to FIG. 5, step 352 passes control to step 510. Step 510 determines whether the originating party 102 set the PI to &#34;Address Presentation Allowed.&#34; If so, step 318 determines if the termination trunk group is a SS7/ISUP type. If so, step 320 is performed to consult the SS7/ISUP attribute table to formulate an IAM to the destination switch 114 with the CgPN parameter included as received by the origination switch 108. Then step 430 delivers the message to the destination switch 114. If the termination trunk group is not a SS7/ISUP type, step 322 determines if the destination switch 114 is a PRI/ISDN type. If so, step 324 is performed to consult the PRI/ISDN attribute table to formulate a SETUP message to the destination switch 114 with the CgPN parameter included. Then step 430 delivers the message to the destination switch 114. If the termination trunk group is not a PRI/ISDN type, step 326 determines if the termination trunk group is a PTS/Inband type. If so, step 328 is performed to consult the PTS/Inband attribute to formulate a message, following the appropriate protocol for that trunk group, to the destination switch 114 with the CgPN included. Then step 430 delivers the message as ANI information to the destination switch 114. If the termination trunk group is not a PTS/Inband type, step 330 simply completes the call because ANI delivery is not applicable for trunk group types other than ISUP/SS7, PRI/ISDN, or PTS/Inband types. 
     If step 510 determines the originating party 102 did not set the PI to &#34;Address Presentation Allowed,&#34; step 520 determines if the PI is set to &#34;Address Presentation Restricted.&#34; If so, switch call processor 302 again proceeds to step 318. Step 318 determines if the termination trunk group is a SS7/ISUP type. If so, step 320 is performed to consult the SS7/ISUP attribute table to formulate an IAM to the destination switch 114 with the CgPN parameter included (with the Calling Party Number itself (D1-Dm)) as received by the origination switch 108. Then step 430 delivers the message to the destination switch 114. If the termination trunk group is not a SS7/ISUP type, step 322 determines if the termination trunk group is a PRI/ISDN type. If so, step 324 is performed to consult the PRI/ISDN attribute table to formulate a SETUP message to the destination switch 114 with the CgPN parameter included. Then step 430 delivers the message to the destination switch 114. If the termination trunk group is not a PRI/ISDN type, step 326 determines if the termination trunk group is a PTS/Inband type. If so, step 328 is performed to consult the PTS/Inband attribute to formulate a message, following the appropriate protocol for that trunk group, to the destination switch 114 with the CgPN included. Then step 430 delivers the message as ANI information to the destination switch 114. If the termination trunk group is not a PTS/Inband type, step 330 simply completes the call because ANI delivery is not applicable for trunk group types other than ISUP/SS7, PRI/ISDN, or PTS/Inband types. 
     If step 520 determines the originating party 102 did not set the PI to &#34;Address Presentation Restricted,&#34; the switch call processor 302, instep 540, will formulate an IAM to the destination switch 114 with the CgPN parameter as received from the origination switch 108 for a SS7/ISUP termination trunk group type; formulate a SETUP message to the destination switch 114 with the appropriate Data Elements for a PRI/ISDN termination trunk group type; or follow the appropriate protocol for the termination trunk group type and generate a message with the ChgN included for a PTS/Inband termination trunk group type. 
     Option C--&#34;Prevent CgPN Delivery&#34; 
     The switch call processor 302, having determined at step 360 that delivery option C was selected by the receiving party 120 subscriber, proceeds to step 362. Referring to PIG. 6, step 362 passes control to step 610. Step 610 determines whether the originating party 102 set the PI to &#34;Address Presentation Allowed.&#34; If so, step 318 determines if the termination trunk group is a SS7/ISUP type. If so, step 320 is performed to consult the SS7/ISUP attribute table to formulate an IAM to the destination switch 114 without the CgPN parameter included as received by the origination switch 108. Then step 440 delivers the message to the destination switch 114. If the termination trunk group is not a SS7/ISUP type, step 322 determines if the destination switch 114 is a PRI/ISDN type. If so, step 324 is performed to consult the PRI/ISDN attribute table to formulate a SETUP message to the destination switch 114 without the CgPN parameter included. Then step 440 delivers the message to the destination switch 114. If the termination trunk group is not a PRI/ISDN type, step 326 determines if the termination trunk group is a PTS/Inband type. If so, step 328 is performed to consult the PTS/Inband attribute to formulate a message, following the appropriate protocol for that trunk group, to the destination switch 114 without the CgPN included. Then step 440 delivers the message as ANI information to the destination switch 114. If the termination trunk group is not a PTS/Inband type, step 330 simply completes the call because ANI delivery is not applicable for trunk group types other than ISUP/SS7, PRI/ISDN, or PTS/Inband types. 
     If step 610 determines the originating party 102 did not set the PI to &#34;Address Presentation Allowed,&#34; step 620 determines if the PI is set to &#34;Address Presentation Restricted. &#34; If so, switch call processor 302 again proceeds to step 318. Step 318 determines if the termination trunk group is a SS7/ISUP type. If so, step 320 is performed to consult the SS7/ISUP attribute table to formulate an IAM to the destination switch 114 without the CgPN parameter included. Then step 440 delivers the message to the destination switch 114. If the termination trunk group is not a SS7/ISUP type, step 322 determines if the termination trunk group is a PRI/ISDN type. If so, step 324 is performed to consult the PRI/ISDN attribute table to formulate a SETUP message to the destination switch 114 without the CgPN parameter included. Then step 440 delivers the message to the destination switch 114. If the termination trunk group is not a PRI/ISDN type, step 326 determines if the termination trunk group is a PTS/Inband type. If so, step 328 is performed to consult the PTS/Inband attribute to formulate a message, following the appropriate protocol for that trunk group, to the destination switch 114 without the CgPN included. Then step 440 delivers the message as ANI information to the destination switch 114. If the termination trunk group is not a PTS/Inband type, step 330 simply completes the call because ANI delivery is not applicable for trunk group types other than ISUP/SS7, PRI/ISDN, or PTS/Inband types. 
     If step 620 determines the originating party 102 did not set the PI to &#34;Address Presentation Restricted,&#34; the switch call processor 302, in step 640, will formulate an IAM to the destination switch 114 with the CgPN parameter as received from the origination switch 108 for a SS7/ISUP termination trunk group type; formulate a appropriate e to the destination switch 114 with the appropriate Data Elements for a PRI/ISDN termination trunk group type; or follow the appropriate protocol for the termination trunk group type and generate a message with the ChgN included for a PTS/Inband termination trunk group type. 
     Option D--&#34;Conditional ChgN Delivery&#34; 
     The switch call processor 302, having determined at step 370 that delivery option D was selected by the receiving party 120 subscriber, proceeds to step 372. Referring to FIG. 7, step 372 passes control to step 710. Step 710 determines whether the originating party 102 set the PI to &#34;Address Presentation Allowed.&#34; If so, step 318 determines if the termination trunk group is a SS7/ISUP type. If so, step 320 is performed to consult the SS7/ISUP attribute table to formulate an IAM with the Charge Number, if it is available, placed in the ChgN parameter. Else, if the ChgN is not available, the Calling Party Number will be included in the CgPN parameter. Then step 730 delivers the message to the destination switch 114 with either the ChgN parameter or the CgPN parameter, but never both. If the termination trunk group is not a SS7/ISUP type, step 322 determines if the destination switch 114 is a PRI/ISDN type. If so, step 324 is performed to consult the PRI/ISDN attribute table to formulate a SETUP message with the Charge Number, if it is available, placed in the CgPN parameter. Else, if the ChgN is not available, the Calling Party Number will be included in the CgPN parameter. Then step 740 delivers the message to the destination switch 114 with one of the parameters filled but never both. If the termination trunk group is not a PRI/ISDN type, step 326 determines if the termination trunk group is a PTS/Inband type. If so, step 328 is performed to consult the PTS/Inband attribute to formulate a message, following the appropriate protocol for that trunk group, to the destination switch 114 with the ChgN, if available, included. Else, if the ChgN is not available, the CgPN will be included. Then step 750 delivers the message as ANI information to the destination switch 114 with either the ChgN or CgPN but never both. If the termination trunk group is not a PTS/Inband type, step 330 simply completes the call because ANI delivery is not applicable for trunk group types other than ISUP/SS7, PRI/ISDN, or PTS/Inband types. 
     If step 710 determines the originating party 102 did not set the PI to &#34;Address Presentation Allowed,&#34; step 720 determines if the PI is set to &#34;Address Presentation Restricted.&#34; If so, switch call processor 302 again proceeds to step 318. Step 318 determines if the termination trunk group is a SS7/ISUP type. If so, step 320 is performed to consult the SS7/ISUP attribute table to formulate an IAM with the Charge Number, if it is available, placed in the ChgN parameter. Else, if the ChgN is not available, the Calling Party Number will not be included in the CgPN parameter. Then step 730 delivers the message to the destination switch 114. If the termination trunk group is not a SS7/ISUP type, step 322 determines if the destination switch 114 is a PRI/ISDN type. If so, step 324 is performed to consult the PRI/ISDN attribute table to formulate a SETUP message with the Charge Number, if it is available, placed in the CgPN parameter. Else, if the ChgN is not available, the Calling Party Number will not be included in the CgPN parameter. Then step 740 delivers the message to the destination switch 114. If the termination trunk group is not a PRI/ISDN type, step 326 determines if the termination trunk group is a PTS/Inband type. If so, step 328 is performed to consult the PTS/Inband attribute to formulate a message, following the appropriate protocol for that trunk group, to the destination switch 114 with the ChgN, if available, included. Else, if the ChgN is not available, the CgPN will not be included. Then step 750 delivers the message as ANI information to the destination switch 114. If the termination trunk group is not a PTS/Inband type, step 330 simply completes the call because ANI delivery is not applicable for trunk group types other than ISUP/SS7, PRI/ISDN, or PTS/Inband types. 
     If step 720 determines the originating party 102 did not set the PI to &#34;Address Presentation Restricted,&#34; the switch call processor 302, in step 760, will formulate an IAM to the destination switch 114 with the CgPN parameter as received from the origination switch 108 for a SS7/ISUP termination trunk group type; formulate a SETUP message to the destination switch 114 with the appropriate Data Elements for a PRI/ISDN termination trunk group type; or follow the appropriate protocol for the termination trunk group type and generate a message with the ChgN included for a PTS/Inband termination trunk group type. 
     Option E--&#34;Conditional CgPN Delivery&#34; 
     The switch call processor 302, having determined at step 380 that delivery option E was selected by the receiving party 120 subscriber, proceeds to step 382. Referring to FIG. 8, step 382 passes control to step 810. Step 810 determines whether the originating party 102 set the PI to &#34;Address Presentation Allowed.&#34; If so, step 318 determines if the termination trunk group is a SS7/ISUP type. If so, step 320 is performed to consult the SS7/ISUP attribute table to formulate an IAM with the Calling Party Number, if it is available, placed in the CgPN parameter. Else, if the CgPN is not available, the Charge Number will be included in the ChgN parameter. Then step 830 delivers the message to the destination switch 114 with either the CgPN parameter or the ChgN parameter, but never both. If the termination trunk group is not a SS7/ISUP type, step 322 determines if the destination switch 114 is a PRI/ISDN type. If so, step 324 is performed to consult the PRI/ISDN attribute table to formulate a SETUP message with the Calling Party Number, if it is available, placed in the CgPN parameter. Else, if the CgPN is not available, the ChgN will be included in the CgPN parameter. Then step 840 delivers the message to the destination switch 114 with either the CgPN or ChgN placed in the CgPN parameter, but never both. If the termination trunk group is not a PRI/ISDN type, step 326 determines if the termination trunk group is a PTS/Inband type. If so, step 328 is performed to consult the PTS/Inband attribute to formulate a message, following the appropriate protocol for that trunk group, to the destination switch 114 with the CgPN, if available, included. Else, if the CgPN is not available, the ChgN will be included. Then step 850 delivers the message as ANI information to the destination switch 114 with either the CgPN or ChgN but never both. If the termination trunk group is not a PTS/Inband type, step 330 simply completes the call because ANI delivery is not applicable for trunk group types other than ISUP/SS7, PRI/ISDN, or PTS/Inband types. 
     If step 810 determines the originating party 102 did not set the PI to &#34;Address Presentation Allowed,&#34; step 820 determines if the PI is set to &#34;Address Presentation Restricted.&#34; If so, switch call processor 302 again proceeds to step 318. Step 318 determines if the termination trunk group is a SS7/ISUP type. If so, step 320 is performed to consult the SS7/ISUP attribute table to formulate an IAM with the Charge Number, if it is available, placed in the ChgN parameter. Else, if the ChgN is not available, the Calling Party Number will not be included in the CgPN parameter. Then step 860 delivers the message to the destination switch 114. If the termination trunk group is not a SS7/ISUP type, step 322 determines if the destination switch 114 is a PRI/ISDN type. If so, step 324 is performed to consult the PRI/ISDN attribute table to formulate a SETUP message with the Charge Number, if it is available, placed in the CgPN parameter. Else, if the ChgN is not available, the Calling Party Number will not be included in the CgPN parameter. Then step 870 delivers the message to the destination switch 114. If the termination trunk group is not a PRI/ISDN type, step 326 determines if the termination trunk group is a PTS/Inband type. If so, step 328 is performed to consult the PTS/Inband attribute to formulate a message, following the appropriate protocol for that trunk group, to the destination switch 114 with the ChgN, if available, included. Else, if the ChgN is not available, the CgPN will not be included. Then step 880 delivers the message as ANI information to the destination switch 114. If the termination trunk group is not a PTS/Inband type, step 330 simply completes the call because ANI delivery is not applicable for trunk group types other than ISUP/SS7, PRI/ISDN, or PTS/Inband types. 
     If step 820 determines the originating party 102 did not set the PI to &#34;Address Presentation Restricted,&#34; the switch call processor 302, in step 890, will formulate an IAM to the destination switch 114 with the CgPN parameter as received from the origination switch 108 for a SS7/ISUP termination trunk group type; formulate a SETUP message to the destination switch 114 with the appropriate Data Elements for a PRI/ISDN termination trunk group type; or follow the appropriate protocol for the termination trunk group type and generate a message with the ChgN included for a PTS/Inband termination trunk group type. 
     While various embodiments of the present invention have been described above, it should be understood that they have been presented by way of example, and not limitation. It will be apparent to persons skilled in the relevant art that various changes in form and detail can be made therein without departing from the spirit and scope of the invention. Thus the present invention should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.

Technology Category: h