3GPP2

TSG-N
TITLE:
WNP phase
SOURCE:
Xiaolan Tang
ZTE Corporation
61#,Gongqingtuan Rd,Nanjing,China,210012

Tel : +86 25 2870574

Fax : +86 25 2870591
Email : tang.xiaolan@mail.zte.com.cn

ABSTRACT
The existing Interim Standard IS-756-A has provided recommendations for supporting
wireless service provider portability, including portability of MobileDirectoryNumbers
[MDNs].This contribution further provides recommendations for supporting wireless
portability from non-CDMA networks(such as PSTN and GSM network) to CDMA
network.,making using of the WIN functions.

RECOMMENDATION:

The proposed text be accepted as WNP phase .

ZTE Corporation grants a free, irrevocable license to 3GPP2 and its Organizational Partners
to incorporate text or other copyrightable material contained in the contribution and any
modifications thereof in the creation of 3GPP2 publications; to copyright and sell in
Organizational Partner's name any Organizational Partner's standards publication even
though it may include all or portions of this contribution; and at the Organizational Partner's
sole discretion to permit others to reproduce in whole or in part such contribution or the
resulting Organizational Partner's standards publication. ZTE Corporation is also willing to
grant licenses under such contributor copyrights to third parties on reasonable, nondiscriminatory terms and conditions for purpose of practicing an Organizational Partners
standard which incorporates this contribution.
This document has been prepared by ZTE Corporation to assist the development of
specifications by 3GPP2. It is proposed to the Committee as a basis for discussion and is
not to be construed as a binding proposal on ZTE Corporation. ZTE Corporation
specifically reserves the right to amend or modify the material contained herein and nothing
herein shall be construed as conferring or offering licenses or rights with respect to any
intellectual property of ZTE Corporation other than provided in the copyright statement
above.

ASSUMPTIONS
The following items are basic understandings used during the development of this
document:
a. MobileDirectoryNumbers [MDNs] are the only wireless service providers E.164
numbering resource that may be ported (e.g., Temporary Local Directory Numbers
[TLDNs], Remote Feature Control [RFC] ports, Roamer Ports are not ported).
b. IS826 is supported by the CDMA network and SCP is one part of the network.
c. This Number Portability document considers only circuit mode calls.
d. Short Message Service (SMS) has not been addressed in this document.
e. Feature interaction support (e.g., Calling Name Presentation [CNAP]) has not
been addressed in this document.
f. WNP impacts on message accounting (e.g., TIA/EIA-124 IS-124)
recommendations have not been addressed supported in this document.
g. WNP impacts to interface standards (e.g., TIA/EIA-93 IS-93) have not been
addressed supported in this document.
h. Only limited location portability is supported consistent with ANSI.T1.660. The
designation of portable numbers 1 may vary between systems. Establishing the
geographical areas within which Number Portability (NP) must be supported is
beyond the scope of this document.
i. TIA/EIA/IS-751
MobileStationIdentity
(MSID)
(i.e.,
InternationalMobileStationIdentity [IMSI] or MobileIdentificationNumber [MIN])
is not portable.
j. Public Switched Telephone Network (PSTN) directory numbers may be portable.
k. The HLR operations (i.e., messages) have not been modified to support WNP. No
new parameters, new parameter fields or new parameter values have been added
to existing HLR operations and no support is provided for HLR initiated Number
Portability queries.
l. Call looping should be avoided. However, no mechanism is provided by this
standard to accomplish that objective.
m. In a Number Portability environment the MobileIdentificationNumber (MIN) and
MobileDirectoryNumber (MDN) may be different.
n. This standard does not require the HLR to distinguish vacant numbers from
numbers which have ported out, implementation specific HLR operations(e.g.,
signaling optimizations, forwarding number validation) may need to be modified
so that service is not hampered. The required modifications are not addressed in
this document.

1 INTRODUCTION

1.1 OBJECTIVE
This contribution provides recommendations for supporting wireless
portability from non-CDMA networks(such as PSTN and GSM network) to
CDMA network.,making using of the WIN functions.

1.2 SCOPE
This document specifies the wireless network impacts of Number Portability(NP),
specifically network portability. In this document, network portability is the ability of
end users to retain the same directory numbers(DNs) whenever the end users change
from non-CDMA network(such as PSTN network and GSM network) to CDMA
network.

1.3 ORGNIZATION

FUNCTIONAL OVERVIEW

2.1 NORMATIVE REFERENCE

2.2 INFORMATIVE REFERENCE
2.3 FEATURE DEFINITIONS
Incoming Call Capability
The call routing to the NP users original DN is transferred to the new DN in CDMA
network.
Outgoing Call Capability(Optional)
The call originated by NP user is presented as from the original DN via CNIP at the
called party
Period of Validity
The validity of orignal DN of NP user will be retained for a certain period of time(eg. 3
months)
Announcement(Optional)
An announcement is played to the calling party to notify the NP users new DN when
the orignal DN is dialed

2.4 SYMBOLS AND ABBREVIATIONS

IMSI
NP
WNP
CFU

International Mobile Station Identity

Number Portability
Wireless Number Portability
Call Forward Unconditional
3

SSP
SCP
IP

Service Switch Point

Service Control Point
Intelligent Peripheral

2.5 NETWORK REFERENCE MODEL

Figure 1 Network Reference Model

AC Authentication Center
BS Base Station
EIR Equipment Identity Register
HLR Home Location Register
IP

Intelligent Peripheral

ISDN Integrated Services Digital Network

MC Message Center
MS Mobile Station
MSC Mobile Switching Center
PSTN Public Switched Telephone Network
SCP Service Control Point
SME Short Message Entity
SN Service Node
VLR Visitor Location Register

AUTOMATIC ROAMING INFORMATION FLOWS

3.1 PRESUPPOSITION
User has his original DN A in non-CDMA network, who changes to CDMA network
and uses DN B. That is to say A is a number in PSTN network or GSM network, and B
is a number in CDMA network. To apply NP service, the followings should to be done:
1. CFU to number B is set in the users profile of number A;
2. Set B as a WIN service number. Therefore Calling triggers
Origination_Attempt_Authorized and Calling_Routing_Address_Available are
armed in Bs profile; Called triggers Initial_Termination, Location,
Called_Routing_Address_Available and T_Answer, T_Disconnect are armed in Bs
associated HLR;
3. Store users orignal number A in the SCP associated to number B, and select the
optional features.
User cancles the NP service using the following steps:
1. Cancel CFU feature in the users profile of number A;
2. Disarm the triggers in Bs profile and its associated HlR;
3. Remove the NP information of B from its associated SCP.

3.2 NP INCOMING CALL

GMSC(GSM)
IAI

GMSC/SSP

HLR

SCP

Serving MSC

a
LOCREQ[MSCID,BILLID,DGTSDIAL,TRIGTYPE,TRANSCAP,WINCAP]
b
locreq[MSCID,MIN,TRIGADDRLIST]
c
ANLYZD[MSCID,BILLID,DGTSDIAL,TRIGTYPE,DMH_REDIND,REDNUMDIG]
d
SEIZERES[SRFCAPA,PLIND]
e
seizeres[TLDN]
f
CONNRES[DSTDGTS]
g
call setup
h
INSTREQ
i
SRFDIR[ANNLIST]
j
play announcement
k
srfdir
l
anlyzd
m
call release
n
instreq
o
LOCREQ[MSCID,BILLID,DGTSDIAL,TRIGTYPE,TRANSCAP,WINCAP]
p
locreq[MSCID,MIN]
q
ANLYZD[MSCID,BILLID,DGTSDIAL,ROUTINF,TRIGTYPE]
r
anlyzd
s
call setup
t

Figure 2 NP incoming call

a.

b.
c.

d.

IP

A call routed to NP users original DN is forward by the non-CDMA network (in

this case, it is GSM network) to CDMA network with an IAI. The IAI carries both
the NP users original DN and new DN and indicates that the call is a forward call.
The GMSC/SSP detects the Mobile_Termination trigger and sends a LOCREQ to
the HLR associated with the MS.
The HLR sends locreq to the GMSC/SSP with the TRIGADDRLIST parameter to
indicate the Initial_Termination, Location, Called_Routing_Address_Available
and T_Answer, T_Disconnect triggers to be armed.
The GMSC/SSP detects the Initial_Termination trigger and sends an ANLYZD to
the SCP indicated in the TRIGADDRLIST parameter. The TRIGTYPE parameter
is set to indicate the Initial_Termination trigger was detected. The
6

DMH_REDIND parameter is set to indicate the call is a forward call. The

REDNUM parameter carries the NP users original DN.
Parameters

Usage

Type

MSCID

OriginatingMSCMSCID.

BILLID

BillingID.Usedtorelatequeriesforthiscall.

DGTSDIAL

Thecalleddirectorynumber.

MSID

CalledMSMSID.

TRIGTYPE

Indicatesthetriggerencountered.

DMH_REDIND

Indicatesthecallisaforwardcall

REDNUM

CarriestheNPusersoriginalDN

e.

The SCP determines that the users NP service is active and an announcement is
required to be played to notify the users original DN. The SCP sends a SEIZRES
to an IP requesting the resource.
f. When the IP receives the SEIZRES, it allocates a TLDN to the appropriate
resource. The TLDN is returned to the SCP in the seizres.
g. The SCP sends a CONNRES to the GMSC/SSP with instructions to set up a call
leg to the IP.
h. The GMSC/SSP sets up the call leg to the IP.
i. When the call is detected at the IP, the IP sends an INSTREQ to the SCP
requesting call processing instructions.
j. The SCP sends an SRFDIR to the IP with the EXESCR parameter indicating the
users old DN to play.
k. The IP plays the announcement indicated by the EXESCR parameter.
l. The IP sends an srfdir to the SCP. The SCRRESULT parameter indicates the
announcement was played.
m. The SCP sends an anlyzdto the GMSC/SSP. The DMH_SVCID parameter is set
to indicate that NP service was invoked.
n. The Serving MSC releases the call leg to the IP.
o. The SCP sends an instreq to the IP to conclude the SCP-IP conversation.
p. The GMSC/SSP detects the Location trigger and sends a LOCREQ to the HLR.
The TRIGTYPE parameter is set to indicate the Location trigger was encountered.
q. The HLR determines the MS is served by the GMSC/SSP and returns a locreq
indicating a local termination.
r. The GMSC/SSP prepares to terminate the call.
The MSC detects the
Called_Routing_Address_Available trigger and sends an ANLYZD to the SCP
associated with this trigger. The REDIND parameter is set to indicate CD Local.

Parameters

Usage

MSCID

OriginatingMSCMSCID.

MSID

ServedMSMSID.

MDN

Mobiledirectorynumber.Includeifavailable.

BILLID

BillingID.Usedtorelatequeriesforthiscall.

RoutingInfo:

Callroutinginformation:

[DSTDGTS]

Type

DestinationDigits.Thenetworkaddressofthe

destination.
[CARDGTS]

CarrierDigits.Interexchangecarrierforcall

setup.Includeifapplicable.
[ROUTDGTS]

RoutingDigits.Specialroutinginstructions.

Includeifapplicable.
REDIND

DMH_RedirectionIndicator.Reasonfor

extendingtheincomingcall.
TRIGTYPE

Indicatesthetriggerencountered.

TOD

TimeOfDay.Thecurrenttime(UTC).

TDO

TimeDateOffset.Thetimeoffsetoflocalcivil

time.

s.
t.

The SCP sends an anlyzdto the GMSC/SSP.

The GMSC/SSP pages and alerts the MS. The MS answers.

3.3 NP OUTGOING CALL

SCP

SSP

ORREQ[BILLID,DIGITS DIALED,ESN,MSCID,TRANCAPA,TRIGTYOE,WINCAPA]
a
orreq[DMH_SRVID]

ANLYZDREQ[BILLID,DIGITS DIALED,MSCID,TRANCAPA,TRIGTYPE,WINCAPA]
c
anlyzdreq[DISPLAYTXT]
call setup
TANSWER

d
e
f

call release
TDISCONNECT

g
h

tdisconnect

Figure 3 NP outgoing call

a.

b.

c.

d.

e.
f.

An call originated by the NP user with dialed digits is received by the Serving
MSC. The Serving MSC detects the Origination_Attempt_Authorized trigger and
sends an ORREQ to the SCP associated with this trigger.
The SCP determines the user has NP active and the users account balance is
positive. The SCP sends an orreq to the Serving MSC to indicate that call
processing shall continue. The DMH_SVCID parameter is set to indicate that NP
was invoked.
The Serving MSC analyzes the dialed digits and prepares to route the call. The
MSC detects the Calling_Routing_Address_Available trigger and sends an
ANLYZD to the SCP associated with this trigger.
The SCP determines that call processing shall continue and that the MS does not
have to be informed of the users account balance at this time. The SCP sends an
anlyzd to the Serving MSC. The DISPLAYTEXT parameter indicates the users
original DN.
Parameters

Usage

Type

DISPLAYTEXT

UsersoriginalDNinnonCDMAnetwork

The Serving MSC extends the MS originated call. The CNIP carried is set to the
NP users original DN indicated by the parameter DISPLAYTEXT.
The call is answered by the called party. The Serving MSC detects the O_Answer
trigger and sends an OANSWER to the SCP associated with this trigger.
9

g.
h.
i.

The (calling) MS ends the call.

The Serving MSC detects the O_Disconnect trigger and sends an
ODISCONNECT to the SCP associated with this trigger.
The SCP sends an tdisconnect to the Serving MSC. The DMH_SVCID
parameter is set to indicate NP was invoked.

4 SIGNAL PROTOCOL
Refer to IS826.

5 SIGNAL PROCEDURE
Refer to IS826.

10