CNIP Feature Development Ver.1.0 February 27,2002 KDDI Corporation

1. CNIP Feature DevelopmentVer.1.0February 27,2002KDDI Corporation

2. Survey Purpose • Calling Number Indentification Presentation(CNIP) feature is blocked for both outbound(KDDI subs) and inbound(SKT/Hutchison subs) today. • Upon interoperability confirmation, KDDI likes to provide CNIP to outbound roamers as well as inbound roamers, based on your requests, to increase traffic and customer satisfaction. in the roaming environment, not a few incoming calls are not answered since, • time difference between home and serve countries (zzzz....) • non-stop intensive business meetings (like us !)CNIP allows customers to call back later by identifying who called you. • While traffic increase is expected, operators have to confirm in advance that CNIP activation won't generate lots of mis-dialed calls to domestic numbers conflicting with displayed numbers. • Fill the survey sheet attached, and send it back to me. Thank you for your cooperation !!

3. Network Diagram for Inbound Roamer Other Market KDDI GW CNB* HLR TSI MSS MSS INTL GW INTL GW Inbound Roamer ISUP (Voice interconnection) IS41 (Signaling interconnection) CNB: It stands for international Converter Box.

4. CNIP Feature for Inbound Roamer (1) Current CNIP Implementation Other Market KDDI GW 1) REGNOT RR CNB HLR TSI 3) REGNOT RR (CNIP=Not Authorized) 2) CNIP Override MSS MSS INTL GW INTL GW KDDI overrides CNIP field in CFI parameter to bar CNIP feature of Inbound roamer. Even if that inbound roamer is allowed CNIP feature by home carrier, his CNIP status is set to “Not Authorized” in the serving MSS.

5. CNIP Feature for Inbound Roamer (2) Planning CNIP Implementation Other Market KDDI TSI GW 2) ROUTREQ(CPNS=“A”) CNB HLR 2) ROUTREQ (CPNS=“A”: Presentation Allowed) “A” is displayed. MSS MSS INTL GW INTL GW Inbound Roamer KDDI can pass the received CNIP field to the serving MSS just by changing the override table in CNB. Therefore, the inbound roamer will be able to receive CNIP service. Then, when the inbound roamer is allowed CNIP feature by home carrier and the call is terminated to inbound roamer, the received Calling Party Number String (Nature of Number = Presentation Allowed) in ROUTREQ will be displayed on the phone.

6. CNIP Feature for Inbound Roamer (3) • KDDI CNIP Feature Implementation: • KDDI Switch Implementation • Calling Party Number displayed on phone is based on “Calling Party Number String1” in ROUTREQ. • In only case that “Nature of Number” of “Calling Party Number String1” is set to “Presentation Allowed”, Calling Party Number is displayed. • If “Nature of Number” of “Calling Party Number String” is set to “National”, “0” is added at the beginning of Calling Party at the serving MSC. • (Example: 13001234567 ---> modified to “013001234567”) • If “Calling Party Number String1” parameter is NOT received in ROUTREQ, NO number is displayed on phone even if “Calling Party Number” is received in ISUP through international GW. • (“Calling Party Number” in ISUP is discarded in CNIP feature.) • If the calling number calculated with “Calling Party Number String1” is more than 16 digits, KDDI switch will release the call. • KDDI CNB Implementation • CNIP override function can be turned on or off for each home operator. • Do you want KDDI to change our implementation so that the inbound roamer can receive CNIP feature in Japan?

7. Network Diagram for KDDI O/B Roamer KDDI Other Market GW CNB* HLR TSI MSS MSS INTL GW INTL GW KDDI O/B Roamer ISUP (Voice interconnection) IS41 (Signaling connection) CNB: It stands for international Converter Box.

8. CNIP Feature for KDDI O/B Roamer (1) Current CNIP Implementation KDDI Other Market 2) CNIP Override TSI GW CNB 1)REGNOT RR （CNIP=X) 2) REGNOT RR (CNIP=Not Authorized) HLR MSS MSS INTL GW INTL GW KDDI always overrides CNIP field in CFI parameter to bar CNIP feature of KDDI O/B roamer. GW 1) REGNOT RR

9. CNIP Feature for KDDI O/B Roamer (2) Planning CNIP Implementation Other Market KDDI TSI GW 2) ROUTREQ (CPNS=“A”) CNB HLR 3) ROUTREQ (CPNS=“A” : Presentation Allowed) “A” is displayed. 1) LOCREQ 4) ISUP (CPN=“B” :Presentation Allowed MSS MSS INTL GW INTL GW KDDI O/B Roamer KDDI can pass the original CNIP field to the serving MSS just by changing the override table in CNB. Therefore, the KDDI O/B roamer will be able to receive CNIP service. Then, when the KDDI O/B roamer is allowed CNIP feature and the call is terminated to KDDI O/B roamer, the received Calling Party Number String (Nature of Number = Presentation Allowed) in ROUTREQ or Calling Party Number (Nature of Number) in ISUP will be displayed on the phone. KDDI always overrides CNIP field in CFI parameter to bar CNIP feature of KDDI O/B roamer. GW 1) REGNOT RR

10. CNIP Feature for KDDI O/B Roamer (3) • CNIP Feature Implementation for KDDI O/B Roamer: • KDDI CNB Implementation • CNIP override function cannot be turn on or off for each serving operator, i.e. all or nothing. • Question on Switch Implementation of other carrier: • Which Calling Party Number is displayed on phone either “Calling Party Number String” in ROUTREQ or “Calling Party Number” in ISUP? • In only case that “Nature of Number” of “Calling Party Number String” in ROUTREQ or “Calling Party Number” in ISUP is set to “Presentation Allowed”, is Calling Party Number displayed? • Do you have the special implementation for CNIP feature to cause the confusion of KDDI O/B Roamer? • To provide CNIP service for KDDI O/B roamer in other markets, KDDI would like to know your implementation and determine whether or not it’s possible.

11. Survey Sheet