Introductions and Agenda Review

The WNPSC agenda was approved.

JIP

The JIP is used to identify the originating switch for billing purposes. The use of JIP is described in ATIS T1S1.6 Technical Requirements No. 2 (TR2), dated April 1999, for Number Portability Switching Systems, and Technical Report No. 3 (TR3), dated April 1999, for Number Portability Database and Global Title Translation. Per TR2, REQ 3300 states the ISUP JIP parameter shall be included in the IAM for all line and private trunk call originations; and REQ 3400 states: "when feature interactions result in a separately billed call segment, the ISUP JIP parameter shall be generated or replaced with the JIP of the switch". Per Appendix C of TR2, TR45.2 has classified REQ 3300 and 3400 as "not applicable". Per Appendix D of TR2, PCS 1900 has classified REQ 3300 and 3400 as "for futher study".

Brian commented that Sprint PCS was interested in having the JIP perimeter standardized. It is standard in the wireline community and they would like it standardized in the wireless community.

Joe Benhibeb gave a presentation to the WNPSC on how JIP is used. On the wireline side, the JIP is used to differentiate the originating office in a number portability environment. This is important because charges may vary between service providers. In a wireless number portability environment, the wireless carriers may be activating the terminal days before the wireline carrier will disconnect service. This is referred to as the "mixed service period". Without a JIP, it may be impossible to identify which telephone made the call during the mixed service period. The JIP is the local routing number, LRN or NPA NXX, assigned to the originating switch.

There are other uses of JIP. If a terminating mobile carrier want to identify an originating carrier in the context of calling party pays, the JIP could be useful here as well. Jim said the JIP would be non-reliable unless all carriers were mandated to use out of band signaling.

ACTION ITEM: Find out if and how wireline carriers are using JIP. Is wireline populating JIP with the LRN and/or NPA-NXX? Are wireline carriers including it in the IAM message? Are they using it when it is sent? Wireless carriers should verify the need for JIP with their billing SMEs and find out from their TR45.2 representatives why the JIP requirements were classified as not applicable.

Brian suggested that we issue a single contribution be sent to the standards bodies. Anna suggested that the LNPAWG should send the contribution. Anna will bring JIP up at the LNPAWG this month to understand the status on the wireline side. At the LNPAWG, wireline carriers confirmed that they were using the JIP.

Wireless Number Portability Report – Writing Assignments

Writing assignments were made. A draft of each section is due to Anne by Feb. 21^st. See attached Table of Contents for writing assignments.

The LNP National Operations Conference call will address unlocated toll on ported numbers. It was described in scenarios where there is a UNE provider but the Intra LATA toll provider can only identify the facility-based provider.

Nineteen states have petitioned the FCC for more authority to established number conservation measures. Eleven states have been granted additional authority by the FCC. Other are expected to receive additional authority. Wireless carriers need to evaluate their LSMS and SCP platforms to be sure they do not have capacity problems because the number of TNs that we will have to store for number pooling in a 1.4 environment is escalating.

Neustar indicated they had a list of carriers that we could use to send notices to in order to schedule NPAC certification testing. It would give us an idea of who is ready.

Since the LNPAWG is scheduling over the WNPSC we would like to suggest to Charles and Shelly that we meet on Wednesday afternoon if the wireless wireline integration issues could be scheduled with a hard start following the WNPSC. There was consensus to have this discussion with Charles and Shelly.

This was discussed at the LNPWG. The LNPAWG agreed that integration issues would be scheduled on Wednesday afternoons. This will enhance wireless participation, since it does not conflict with WNPSC on Monday afternoons and is amenable to wireless participation during LNPAWG Slow Horse, PIM and integration issue discussions.

Members of the Inter-Carrier Communications subcommittee request that the WNPSC look at developing standard times for wireless to wireless complex ports.

ACTION ITEM: Is there a need to determine maximum timers for complex ports for pre-port communication? Between now and the next meeting determine your company position and be prepared to develop a WNPSC position.