The Seven Rules of JIP

1
The Seven Rules of JIP

• Stuart Goldman
• NIIF Co-Chair
• T1S1.3 Chair
• sgoldman_at_lucent.com

2
The Value of JIP

• With the evolution to Local Number Portability
  between wireline and wireless service, as well as
  the proliferation of wireless roaming service,
  the calling directory number no longer can be
  relied upon to accurately reflect the
  geographical location of the calling party.
• Fortunately, the industry can use the Signaling
  System 7 Initial Address Message Jurisdiction
  Information Parameter (JIP) to convey more
  representative location information.
• The ATIS NIIF has taken the lead in developing
  consistent industry rules for JIP, and has been
  working with other forums such as T1S1, OBF,
  TR-45, etc. to reach industry wide agreements.

3
The NIIF Seven Rules of JIP

• This is still very much a work in progress.
• The NIIF met just last week.
• What I am reporting is the most current status as
  well as what I believe to be the most likely
  outcome. I could easily be wrong on both counts,
  so nothing presented here should be viewed as
  official guidance.

4
T1S1 ISUP IAM JIP

• A long time ago, when T1S1 was developing the SS7
  protocol, it seemed like a good idea to include
  an optional parameter in the Initial Address
  Message (IAM) that could convey some geographic
  information about the location of the calling
  party, which might be of value for correct rating
  and routing.
• The Jurisdiction Information Parameter was
  created as a six digit field, thus the level of
  information was on the order of NPA/Office Code.
• When the Number Portability application came
  along and subscribers could port their Directory
  Numbers, it seemed like a good idea for T1S1 to
  require that Number Portability capable offices
  include the JIP on ALL calls.

5
T1S1 ISUP IAM JIP

• In the SS7 ISUP procedures, parameters can be
  mandatory or optional,
• If a mandatory parameter is not received, the
  call is aborted.
• If an optional parameter is not received, the
  call continues.
• The Number Portability TRQ specified that the
  JIP, while an optional parameter and not
  mandatory, was never-the-less always required.
  (That makes it clear, right?)

6
T1S1 Definition of JIP

• 2.1.10C Jurisdiction information
• An originating exchange may optionally include
  the Jurisdiction Information parameter13 in the
  Initial Address Message. If included, the
  Jurisdiction Information parameter shall contain
  six digits representing the geographic location
  (NPA-NXX) of the call origination.
• Intermediate exchanges shall pass a Jurisdiction
  Information parameter unchanged from an incoming
  Initial Address Message to an outgoing Initial
  Address Message. If an intermediate exchange
  receives an Initial Address Message without a
  Jurisdiction Information parameter, and if the
  exchange is provisioned such that (for calls
  received on the incoming trunk group) a
  Jurisdiction Information parameter may be
  optionally included in the outgoing Initial
  Address Message. The exchange shall populate a
  Jurisdiction Information parameter with an
  NPA-NXX associated with incoming trunk group.
  When an intermediate exchange receives a call
  over a trunk group with in-band signaling, the
  exchange may optionally include a Jurisdiction
  Information parameter in the outgoing Initial
  Address Message. The exchange shall populate a
  Jurisdiction Information parameter with an
  NPA-NXX associated with incoming trunk group.

7
Modified T1S1 SS7 ISUP

• At the request of the NIIF and the OBF
  leadership, T1S1.3 agreed last month to modify
  T1.113 (SS7 ISUP)
• Original text of footnote
• 13 As the Jurisdiction Information parameter is
  an optional parameter in ISDN-UP, service
  standards will determine when the parameter is to
  be included in an IAM and how the contents of the
  parameter are to be used.
• Proposed text change to footnote
• 13 Although the Jurisdiction Information
  parameter is an optional parameter in ISDN-UP,
  the parameter will always be included in the IAM.
  Service standards will determine how the contents
  of the parameter are to be used.

8
Rules for Populating JIP

• Rule 1
• JIP should be populated in the IAMs of all
  wireline and wireless originating calls where
  technically feasible.

9
Rules for Populating JIP

• Rule 2
• JIP should be populated with an NPA-NXX that is
  assigned in the LERG to the originating
  wireline/wireless switch.

10
Rules for Populating JIP

• Rule 3
• The NIIF does not recommend proposing that the
  JIP parameter be mandatory since calls missing
  any mandatory parameter will be aborted. However,
  the NIIF strongly recommends that the JIP be
  populated on all calls where technologically
  possible.

11
Rules for Populating JIP

•  
• Rule 4.     
• Where technically feasible if the originating
  wireline/wireless switch serves multiple
  states/LATAs, then the switch should support
  multiple JIPs such that the JIP used for a given
  call can be populated with an NPA-NXX that is
  specific to both the switch as well as the state
  and LATA of the caller.
• This has generated concern at TIA TR-45.

12
Rules for Populating JIP

•  
• Rule 4.      This has generated concern at TIA
  TR-45. They have suggested
• Where technically feasible, if the originating
  wireline switch serves multiple states/LATAs,
  then the switch should support multiple JIPs such
  that the JIP used for a given call can be
  populated with an NPA-NXX that is specific to
  both the switch as well as the state and LATA of
  the caller
• Where technically feasible, wireless MSCs should
  assign JIP on a MSC basis. For wireless callers
  this should be based on the originating MSC This
  applies as well to cases where the subscriber is
  served remotely.
• The NIIF has called a meeting of the interested
  parties to address this proposal.

13
Rules for Populating JIP

• Rule 5     
• Where the originating switch cannot signal JIP it
  is desirable that the subsequent switch in the
  call path populate the JIP using a data fill
  default associated with the incoming route. The
  value of the data fill item is an NPA-NXX
  associated with the originating wireline/wireless
  switch and reflective of its location.

14
Rules for Populating JIP

•  
• Rule 6     
• When call forwarding occurs, the forwarded from
  DN (Directory Number) field will be populated,
  the JIP will be changed to a JIP associated with
  the forwarded from DN and the new called DN will
  be inserted in the IAM.
•  

15
Rules for Populating JIP

• Rule 7
• As per T1.TRQ2, the JIP should be reset when a
  new billable call leg is created. The issue of
  whether this should be construed to also apply in
  the case of wireless call redirection to roaming
  subscribers using a TLDN or MSRN (Temporary Local
  Directory Number /Mobile Subscriber Roaming
  Number) is pending input from the wireless
  community.
•  
•  

16
Next Steps

• Reach industry agreement on rules
• Publish
• Industry awareness
•  And just when you thought you could see light at
  the end of the tunnel, it may indeed be another
  train. In this case, Lucent proposed an issue at
  last weeks NIIF meeting regarding the rules for
  JIP when VoIP technology is involved in the call.
  The Issue has been accepted and the OBF has been
  alerted.
• Stay tuned!

VoIP
PSTN